On 15.03.2010 23:04, Kurt Roeckx wrote: > On Fri, Mar 05, 2010 at 01:34:03PM +0100, Michael Vogt wrote: >> Package: buildd.debian.org >> Severity: normal >> >> The information in Packages-arch-specific says: >> %partimage: !ia64 !alpha !amd64 !kfreebsd-amd64 # >> 64-bit is br0ken >> >> But amd64 packages are availalbe via a binNMU. The changelog mentions >> some fixes and partimage builds fine (and is able to create images) >> on amd64. Is that a leftover? Or is it still broken and the amd64 >> version is there by accident? > > Once it's in installed state you can schedule binNMUs. So the > question is why it got in installed state in the first place. > > I have no idea if it works properly or not. If not, a bug should > be filed against both ftp.debian.org to request the removal and > partimage to make sure it doesn't get build and uploaded by > accident. > > If it now works properly we can remove the entry.
Hi everyone, so now that Kurt reassigned this bug to partimage and bumped it to serious(?), I wonder what to do about this. The package was switched to i386 only, by it's previous maintainer due to [1]. There were some 64 bit related fixes upstream, but I can't tell for sure if partimage will work in a mixed 32/64bit environment (e.g. backup with i386, restore with amd64). I'd suggest to remove the P-a-s entries and just see what happens. Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=268248 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
