On Thu, Feb 11, 2010 at 8:12 PM, Pierre Schmitz wrote:

Hi TUs and DEVs,

I just packaged a new set of devtools today. I'll put it into testing first; so please give it a try and let me know if there are any problems. And of course I'd appreciate if you could also drop a line if everything works as expected.

A warning for those who use makechrootpkg: the rw and union subdirs are no longer used and cannot be used with the new tools. Aufs is no longer needed.

For details see http://projects.archlinux.org/devtools.git/log/

The most noticeable changes are:

     Use the host's SRCDEST and PKGDEST if defined      Reset umask before touching the chroot.      make sure all files are owned by nobody before building      Move build and package logs to WORKDIR, otherwise it is lost      Create a working copy instead of using an union layer      Read pacman cache dir from pacman.conf or cli      Reduce verbosity to a sane minimum      simplify and optimize upload process      Replace expensive merge with delete and copy      Add missing -n option to getopt list for mkarchroot      abort if not all local source files are under version control

Greetings,

Pierre

--

Pierre Schmitz, https://users.archlinux.de/~pierre

I'm getting this error: creating clean working copy mkdir: cannot create directory `': No such file or directory

Am Freitag, 12. Februar 2010 06:42:32 schrieb Eric Bélanger:

My CacheDir line in pacman.conf was commented out

I missed that this var was optional. Fixed in http://projects.archlinux.org/devtools.git/commit/?id=9e14e8691d6b60d82ab553... I'll wait for some more feedback before releasing a new package. -- Pierre Schmitz, https://users.archlinux.de/~pierre

On Fri, Feb 12, 2010 at 12:23 AM, Eric Bélanger wrote:

On Thu, Feb 11, 2010 at 8:12 PM, Pierre Schmitz wrote:

...

Hi TUs and DEVs,

I just packaged a new set of devtools today. I'll put it into testing first; so please give it a try and let me know if there are any problems. And of course I'd appreciate if you could also drop a line if everything works as expected.

A warning for those who use makechrootpkg: the rw and union subdirs are no longer used and cannot be used with the new tools. Aufs is no longer needed.

For details see http://projects.archlinux.org/devtools.git/log/

The most noticeable changes are:

     Use the host's SRCDEST and PKGDEST if defined      Reset umask before touching the chroot.      make sure all files are owned by nobody before building      Move build and package logs to WORKDIR, otherwise it is lost      Create a working copy instead of using an union layer      Read pacman cache dir from pacman.conf or cli      Reduce verbosity to a sane minimum      simplify and optimize upload process      Replace expensive merge with delete and copy      Add missing -n option to getopt list for mkarchroot      abort if not all local source files are under version control

Greetings,

Pierre

--

Pierre Schmitz, https://users.archlinux.de/~pierre

I'm getting  this error:

creating clean working copy mkdir: cannot create directory `': No such file or directory

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.

Am Freitag, 12. Februar 2010 02:12:17 schrieb Pierre Schmitz:

A warning for those who use makechrootpkg: the rw and union subdirs are no longer used and cannot be used with the new tools. Aufs is no longer needed.

For details see http://projects.archlinux.org/devtools.git/log/

The new devtools will soon be in extra. You'll find a chagnelog at the url mentioned above. I just wanted to add some more info about the new rsync usage of makechrootpkg: * if you have any important files in your rw layer it is easier to back them up now using the old devtools. * You can remove the rw and union dirs; they are no longer used * In a worst case you will need up to 800 MB extra disk space for your chroot, as we now create a complete copy of your root install. The benefit is that there wont be any crashes or system freezes due to aufs and compiling will be faster as there is no overhead anymore. The initial sync will take some time though; depending on your hard drive performance. (e.g. one minute) -- Pierre Schmitz, https://users.archlinux.de/~pierre