ti, 2005-05-03 kello 01:27 +0100, Paul Martin kirjoitti: > This FTBFS will go away when elinks 0.10.4-3 reaches "testing"... but > your patch means that there's going to be a bug raised because it will > then FTBFS into a nice-looking text file. > Filing an FTBFS on an "architecture: all" package that contains only a > plain text file, and then doing a zero-day NMU within 48 hours is not a > nice thing to do. It's not that important a package to warrant such > urgency.
Andreas opened the bug. I did the NMU. I meant to help things, not make them worse. Sorry about any confusion. Since this bug is release critical, one of two things needs to happen before sarge can release: either the bug is fixed or jargon-text is removed from sarge. I think the former is the better option. This is why I made the NMU. I uploaded it immediately because we are very close to freezing sarge, and this means that release critical bugs should be closed as quickly as possible. That is why the project is in a 0-day NMU period until the freeze. Removing the option that causes the build to fail with the version of jargon-text in sarge was the faster way to get the fixed jargon-text into sarge. I compared the versions before making the upload. I did not find the new version (the one in my NMU) to be terribly formatted, but I guess that is a matter of taste. > The correct long-term fix for this bug is to build-depend on the right > version of elinks (which ought to enter testing in a few days). If > elinks 0.10.4 doesn't enter testing, your NMU package will be the one in > sarge. Steve Langasek told me on IRC that it is unlikely that the new elinks will get into sarge in time. With my NMU, jargon-text could still stay in sarge (whether the formatting is good or not). With your MU, as far as I understand, jargon-text needs to be removed from sarge, since it can't be built with sarge tools. Since my NMU is not yet in sarge, your MU will overwrite my NMU at about 22:00 UTC today, when the next dinstall run happens. This means the bug won't be fixed in sarge. If you prefer my NMU over removal from sarge, you could mail debian-release today (well in advance of 22:00 UTC). Note that anything I say about package removal in this mail is based on my own understanding, it is not advice from release managers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
