Control: severity -1 serious

On Mon, Sep 08, 2014 at 10:12:37PM -0400, Reinhard Tartler wrote:
> I wonder what's the status of this bug. The most recent email did not
> help to clarify, so I test-compiled wx3.0.patch as proposed in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749659#35, and can
> confirm that the package builds fine. However, I noticed this in
> configure.log:
> 
> checking for wx-config... /usr/bin/wx-config
> configure: Checking that the chosen version of wxWidgets is 2.8.x or
> 3.0.x
> Great, you're using wxWidgets 2.8.12!
> 
> I guess that is because the build dependencies needs updating. So I
> guess given that the proposed patch to the package is incomplete at
> best, I've removed the "patch" tag, as clearly more clarification is
> needed.
> 
> Olly, I noticed that you raised the severity of this bug to "Serious"
> without further explanation. Can you please elaborate here?

Justification was in the mail which updated the severity:

# blocks the on-going wxwidgets3.0 transition
severity 749659 serious
thanks

You can see that from the BTS if you click on the "Full text" link:

https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=30;bug=749659

https://wiki.debian.org/Teams/ReleaseTeam/Transitions says to use
severity serious once the transition starts, which it officially
did on 2014-05-27:

https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=24;bug=748169

> This situation claims that audacity should be removed from testing
> because of this issue. Is this really your intention?

Very much so - the wxwidgets3.0 transition is close to complete and
audacity is one of the stragglers:

https://release.debian.org/transitions/html/wxwidgets3.0.html

In fact, it's the only one still in testing, which is only because it
is on the list which autorm won't touch due to popcon score.

Of those, grass has an somewhat bogus build dependency (it really
wants to check the wxPython version, so should do that directly)
and 5 more the maintainer has said to remove.  Of the remaining 8,
most have a fix in progress.

> The wxwidgets transition tracking bug seems to be
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748169. Given that
> the transition did not start before the September 5, I think it is
> fair to assume that this transition is not going to happen for
> Debian/jessie, and that it is also appropriate to downgrade the
> severity of this bug.

I don't see where you get September from - the last update to that
bug was in August...

As above, it officially started back in May, though I've been working on
it since October last year.

> Please correct me and clarify if I got something wrong, but AFAIUI,
> there are no reason for pressing on this bug because jessie will ship
> with wxWidgets 2.8.  Martin, may I recommend you getting in touch with
> upstream about this patch?

I suppose the release team have the final say, but my intention is that
jessie will not ship with wxwidgets2.8.  It is a large and complex
library, and now unmaintained upstream.  Even before 3.0 was released,
2.8 was neglected - the last release was 2011-03-28.  So by the time
jessie releases, wx2.8 will be close to 4 years old.  By the EOL of
jessie (assuming no LTS), it'll be close to 6 years old.

And given (thanks to Martin's superlative efforts) we have a patch for
audacity, why are we even having this discussion?

Cheers,
    Olly


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to