On Tue, 2012-07-10 at 17:41 -0500, Rob Browning wrote: > Rob Browning <[email protected]> writes: > > > Also not ideal, but if it's allowed, I could just upload both amd64 and > > i386 (or just i386). So far murphy's the only place we seem to have > > this problem.
It would work, but it's not exactly ideal for future updates, particularly in stable... fwiw, the auto-exception was for 24.1+1-1; -2 currently has no such exception. The general policy thus far has been not to grant manual unblocks for source packages which are new for wheezy, although we could possibly be persuaded that there are cases where it makes sense. > So the build in the wheezy chroot, running on the i386 squeeze vm didn't > fail. The host kernel there was linux-image-2.6.32-5-686-bigmem > (2.6.32-45). Whether or not that was close enough to murphy's kernel, I > don't know. (From the murphy build log: "Kernel: Linux > 2.6.32-5-686-bigmem i386 (i686)".) > > At this point, I'm not sure what I should try next. Suggestions? My earlier remembering of one of the i386 buildds being a VM appears to have been mistaken; the most obvious difference is that one is an amd64 host whereas the other is i386. The buildd logs contain a list of all of the packages used during the build. It's often worth comparing those between a failing and successful build to see if there are any possibly relevant differences. Regards, Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
