Bug#131153: Broken cvs package in unstable, woody is fine (was Re: Bug#131153: caused by fix to #130595)
Jamie Wilkinson <firstname.lastname@example.org> writes:
> I don't know if anyone realises this, but it's plainly obvious
> by diffing -3 and -4 that this and #131357 and #131477 are
> caused by the fix for #130595.
Yes, and it was even more obvious to me, since i made the change in
CVS :-/. Unfortunately, the trivial stupid bug i went to fix came in
at a time when i was very bored and had some free time. It looked
like a trivial fix (and it was, really) and so i dove in. Now i'm
stuck with a release critical bug.
Despite being release critical, i'm not overly concerned; there is a
working version in woody already. I don't want to just revert my --
patch, because it's at least a step in the right direction. I need to
study the problem more carefully and fix it for real, and obviously
test it better this time.
Next weekend (not this weekend) i should have some time to work on
this. If you come up with a solution, please bring it to my attention
first; i welcome NMUs, but not some jerkoff NMUing my package with no
notice, for no real reason (i'm not a delinquent maintainer and woody
is fine WRT cvs), and with an incorrect fix.
Eric Gillespie, Jr. <*> email@example.com
"When everyone has to reinvent the wheel, many people invent