On Tue, Jun 19, 2012 at 01:36:08PM -0500, Jonathan Nieder wrote: > Mark Brown wrote:
> > What makes you say this, and why are you filing a bug on the package? > > Please provide a description of whatever problem you think you are > > seeing and contact the release team (who are responsible for binnmus). > He's probably asking you to work around [1] by making a sourceful > upload at some time before the next release. So, after some discussion on IRC this isn't a workaround at all, it's the only available solution with out current infrastructure. > Doing that every time there is a binnmu sounds like a lot of work and > I think that it would be better to either solve the problem > systematically (by finding a way to make the changelogs the same on Yes, someone (ideally the multiarch people...) ought to implement support for this in the infrastructure - right now there's a noticable regression for packages like this. However, in the meantime it'd be good if we could avoid scheduling binnmus for affected packages and just request sourceful uploads instead (ideally if we can't fix it properly the binnmu infrastructure could notice and generate bug reports automatically). This seems to be the best option in terms of avoiding breakage for users. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
