Am Samstag, 13. Februar 2010 00:18:30 schrieb Eric Bélanger:
> I found the cause of this error. This error happens when the CacheDir
> is undefined. The chroot_mount function in mkarchroot then fails to
> create the cache_dir directory. It should be fixed by the commit to
> give cache_dir a default value.
Thanks, that explains a lot. I have put 0.9.1 into [testing] fixing this issue
and being a little more verbose when an action might take longer (like svn
commit)
--
Pierre Schmitz, https://users.archlinux.de/~pierre
02-13-2010, 02:10 AM
Pierre Schmitz
devtools 0.9.1
Am Samstag, 13. Februar 2010 00:18:30 schrieb Eric Bélanger:
> I found the cause of this error. This error happens when the CacheDir
> is undefined. The chroot_mount function in mkarchroot then fails to
> create the cache_dir directory. It should be fixed by the commit to
> give cache_dir a default value.
Thanks, that explains a lot. I have put 0.9.1 into [testing] fixing this issue
and being a little more verbose when an action might take longer (like svn
commit)
--
Pierre Schmitz, https://users.archlinux.de/~pierre
02-13-2010, 04:02 AM
Allan McRae
devtools 0.9.1
On 13/02/10 13:10, Pierre Schmitz wrote:
Am Samstag, 13. Februar 2010 00:18:30 schrieb Eric Bélanger:
I found the cause of this error. This error happens when the CacheDir
is undefined. The chroot_mount function in mkarchroot then fails to
create the cache_dir directory. It should be fixed by the commit to
give cache_dir a default value.
Thanks, that explains a lot. I have put 0.9.1 into [testing] fixing this issue
and being a little more verbose when an action might take longer (like svn
commit)
Is it possible to run the svn commit only once in archrelease instead of
after the rm and copy parts? We now get 5 messages per update to
arch-commits instead of three. That will take that list from ~200
messages a day to ~350. Not that this really matters...
02-13-2010, 04:12 AM
Pierre Schmitz
devtools 0.9.1
Am Samstag, 13. Februar 2010 06:02:39 schrieb Allan McRae:
> Is it possible to run the svn commit only once in archrelease instead of
> after the rm and copy parts? We now get 5 messages per update to
> arch-commits instead of three. That will take that list from ~200
> messages a day to ~350. Not that this really matters...
I also like to know how to do this in one transaction. Svn simply does not
want you to and complains about it. We have the same problem in db-move of db-
scripts.
--
Pierre Schmitz, https://users.archlinux.de/~pierre
02-13-2010, 04:43 AM
Allan McRae
devtools 0.9.1
This commit needs to be fixed:
http://projects.archlinux.org/devtools.git/commit/?id=7ce9cd69
It results in a lot of:
warning: directory permissions differ on etc/
when creating a chroot. "umask 0022" would be correct.
As an aside, the only way to current make a chroot with [testing]
enabled is to create one without testing, enable it and then upgrade
from there. Otherwise there are lots of conflicts when attempting to
install "base".
Allan
02-13-2010, 05:24 AM
Pierre Schmitz
devtools 0.9.1
Am Samstag, 13. Februar 2010 06:43:54 schrieb Allan McRae:
> This commit needs to be fixed:
> http://projects.archlinux.org/devtools.git/commit/?id=7ce9cd69
>
> It results in a lot of:
> warning: directory permissions differ on etc/
>
> when creating a chroot. "umask 0022" would be correct.
devtools 0.9.1
