Bug#513183: mercurial: pre-approving and sponsoring a possible NMU upload to t-p-u to fix an important bug (#513183)

* Eddy Petrișor [Fri, 30 Jan 2009 17:54:03 +0200]: Hello release team, Hello, Eddy (and Mercurial maintainers). Here are my thoughts on the issue: - a patch for this should really get an ACK from the maintainers - if not, you should follow the usual procedures for NMUs for RC bugs,

Bug#513183: [Python-apps-team] Bug#513183: mercurial: pre-approving and sponsoring a possible NMU upload to t-p-u to fix an important bug (#513183)

Hi, Adeodato Simó wrote: * Eddy Petrișor [Fri, 30 Jan 2009 17:54:03 +0200]: Hello release team, Hello, Eddy (and Mercurial maintainers). Here are my thoughts on the issue: - a patch for this should really get an ACK from the maintainers I quickly look at your (Eddy) patch and I

Bug#513183: [Python-apps-team] Bug#513183: mercurial: pre-approving and sponsoring a possible NMU upload to t-p-u to fix an important bug (#513183)

No I haven't talked to them. Indeed, the quick fix I provided is not the right solution for upstream, but it looks like a good workaround for lenny since we're closer and closer to the release (now that D-I rc2 was announced). the problem ? Or even your patch ? (but I think they will prefer

Bug#513183: mercurial: pre-approving and sponsoring a possible NMU upload to t-p-u to fix an important bug (#513183)

Hello release team, Mercurial's hgk extension fails to start if the configuration files of another extension are still present after a package removal. This is bug #513183 - hgk fails to start when hg emits warnings. This happens under relatively common conditions (package of an extension is