i keep several chroots alive: core, core/testing, extra, extra/testing. and that twice for each architecture. calling devtools archrelease foo-$CARCH works well for extra and extra/testing also in i686 (linux32) chroots. but how to deal with core chroots? for x86_64 i can run archrelease from outside the chroot. but this won't work for i686. so far i had manually tagged and scp'ed the pkg. how to to this now? moving all subversion related dependencies to core/devel could solve it that are not only a few packages, so it would blow up core a bit too much i think. any idea? btw: how's other devs experience with mkarchroot? is the creation trivial for x86_64 and linux32 i686 chroots? how do you keep the chroot empty or do create each time a new one? is there any advantage beside disc space over permanent chroots? -Andy