Hi,
> > severity 481344 wishlist
> Sorry, I disagree with that. This change of cowdancer broke the support for
> chroot other than unstable and testing. This is not the idea of such a
> tool in my eyes..
> I e.g. use it for creating backports for a customer and therefore a working
> etch chroot is essential for this work. Since this change of cowdancer has
> a great impact of usability of many chroots this has to be a RC Bug and
> nothing else.
> Since I doesn't want to play BTS pingpong here, please raise the severity
> at least to serious.
You can always fall back to pbuilder.
cowbuilder initially has been designed so that it works best with same
cowdancer version inside and outside of chroot, so it has never really
worked well on all architectures. There have been changes in place to
allow cowdancer to work across different versions, and that is after
etch has been released.
0.45 adds version and integrity checking for .ilist files, so that
it's now possible to change something to fix .ilist file format.
.ilist format needs to be changed to allow things like co-existing of
64-bit and 32-bit applications within a chroot.
> > retitle 481344 provide cowdancer etch backport
> Mh.. .this has to be changed in the official archive.. not via
> backports...of course feel free to backport this to backports.org but
> please integrate something that made etch chroot's working again: maybe a
> fallback if the ilist stuff is not available as it was working in previous
> versions.
It can be done by adding backported cowdancer.
But it also could be done through building the cowdancer package and
installing inside chroot on-the-fly.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
