Hi Holger, Holger Wansing <hwansing@mailbox.org> writes: > I'm done with preparing these changings now. > > I have verified, that the results are as intended, for all packages apart from the s390-* ones: > > I'm still unable to get those 'foreign arch' packages to built with sbuild at all, unrelated from this usrmerge thing. > But the usrmerge changings for this packages are easy and will work, so IMO they are not a blocker. This is also my feeling. > How to proceed now? > Should I do an upload for all relevant packages now, or wait? Is "all relevant packages" team ones, or any udeb-producing package that didn't have usrmerged udebs? > Does anybody want to take a look first, or ... ? I've been ready to upload a usrmerged btrfs-progs udeb for ages, so I'll go ahead and do that now. My intent is to provide useful data on the udeb usrmerge with changes that only affect a subset of our users--and the overlap with the sid-using subset are those who are open to a documented degree of risk. The annual Python breakage begins next month, if I remember correctly, and my thinking is it's nice to stagger the introduction of the things that could break Debian, so before the 14th of November seems like a good time to me since it gives two weeks to unbreak or revert if undocumented gremlins are discovered. But it's also the case that Cyril would probably like to review pre-upload, I don't want to pressure, and I hope the results of my experiment will demonstrate the changes are low risk. Cheers, Nicholas
Attachment:
signature.asc
Description: PGP signature