Your message dated Mon, 25 Mar 2013 15:59:13 +0100 with message-id <[email protected]> and subject line Re: [Piuparts-devel] Bug#644626: Bug#644626: piuparts: Testing package data compression has caused the Debian Bug report #644626, regarding piuparts: Testing package data compression to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 644626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644626 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: piuparts Severity: wishlist Version: 0.41 We have recently seen failures #633782 and #644353 making the installer fail due to individual packages using bzip2 compression of the data part in the corresponding binary package. Would it be possible, and suitable, to have Piuparts implement an examination of the compression type used on a package? To prevent bugs like those mentioned, one would need to identify which compression types the bootstrapper supports in the installer at all times, and one would need to keep track of which dependencies are brought in by the installer. This latter information should be readily available already, or at least traceable, and the first piece of information is even simpler to register. We recently saw an emerging discussion on compression methods for packages, in a thread which certainly is relevant for the kind of grave bugs that I address here. Thus it seems relevant that the build infrastructure pay attention to this most disruptive source of errors. Best regards, Mats Erik Andersson
--- End Message ---
--- Begin Message ---Hi, On Samstag, 8. Oktober 2011, Mats Erik Andersson wrote: > > probably. but then it's also easy to setup a daily cronjob which runs > > debootstrap :-) jenkins.debian.net does this now... > > Also/but I think the correct solution is to setup automated d-i > > installation tests, (and not to add more functionality to piuparts which > > is basically outside of piuparts scope). jenkins.debian.net does this now... > > So I'm very tempted to close this bug as wontfix. Comments from other > > people reading this? > You are most probably correct in both these respects. thus closing this bug :-) cheers, Holger
--- End Message ---
