Changelog entry from a package that has just arrived in incoming:
gnucash (1.8.10-8) unstable; urgency=high
.
* high urgency upload because the fix for critical bug 291632 didn't get
into testing because of recompilation bugs, those later fixes were
uploaded with urgency low, and the package is still badly stuck.
People need the bug fix for 291632 and this will move it along. No
changes to the source.No, Thomas, this will NOT move it along. As I explained to you in response to your last message to debian-release, the missing builds have been awaiting fixes to our buildd capacity on a pair of architectures, and gnucash 1.8.10-7 was already in the Needs-Build queue on both of those architectures (as you could see from http://people.debian.org/~igloo/status.php?packages=gnucash, if you're not used to interpreting the pages on buildd.debian.org). The reason gnucash has not been built yet on arm or mipsel is because there is a backlog of over a hundred packages on each of these architectures. Re-uploading a package to provoke a buildd response is counterproductive, *particularly* when the package is already in Needs-Build on the missing architectures. Re-uploading doesn't change its position in the queue, but it *does* force buildds for all the other archs to needlessly rebuild the package. This is why the answer to your previous email was "please be patient". -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
