#1543046 wrongly marked as fixed for Wily

[php fan]

> And if it is not, then it would get marked "Won't Fix" when
> someone goes through and does post-EOL-release cleanup.

It sounds like that would be the right thing to do. If it's not going to be
fixed, let's at least avoid people the frustration, confusion, and possible
waste of time caused by having bullshit information on Launchpad.

Note also that, given that this bug was claimed to be fixed for Wily and it
isn't, I am quite skeptic that it's really fixed in Trusty too. If I were a
member of a QA team, I would test it on Trusty. There's a simple,
copy-pastable command to run to see whether or not the bug is fixed. I
would test it myself if I had any box with Trusty.



> and prepare your environments
> for upgrading to Xenial when Wily dies on the 28th.

Speaking of "preparing my environments" (that's funny btw: you shouldn't be
supposed to have to "prepare" anything at all for an upgrade), so is there
some "preparation" I can do to make sure that I don't brick my computer
with the upgrade as per issue 1551623? Or at least, some check I can do to
know whether my system is affected, so that I don't upgrade in that case?
(I'd rather have a "dead" Wily, dead as in "past the EOL", than a dead
system, dead as in "it doesn't boot").



2016-07-08 1:26 GMT+02:00 Thomas Ward <teward at ubuntu.com>:

> Hi, all!
>
> <snip>
>
> On 07/07/2016 07:14 PM, php fan wrote:
> >> Given that Wily is completely EOL in a few days,
> > What? Wily will become EOL before it's even safe to upgrade to Xenial?
> > (https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623)
> Wily will End of Life on July 28th.  This was sent over the
> announcements list by Adam Conrad earlier this morning (my time).  I
> don't have the link to the one on the general announcements list, but it
> also went over the security announce list, and that message is here for
> your review:
>
> https://lists.ubuntu.com/archives/ubuntu-security-announce/2016-July/003492.html
>
> >
> >> I doubt you're going to get any traction on this
> > Well, that doesn't mean that it makes sense to keep the status as "fix
> > released" when it is not fixed.
> >
> > I would change it myself but Launchpad doesn't let normal users change
> bug
> >  status when it is "fix released" (which is stupid, given that we do can
> > change it _to_ "fix released")
> >
> > (<remainder of original message snipped>)
>
> The reason it's marked "Fix Released" is because a package was released
> to the repository from the proposed repository which had the bug
> referenced in the changelog as addressing the issue, and in turn when it
> was released, it closed the bug.  That's an automatic process, and the
> automatic system isn't as smart as you or I.
>
> That being said, while we (any bug control member) could go and change
> the bug back to "Triaged" or "Confirmed" and poke that it never fixed
> it, I am not sure that this would get 'fixed' before then (note: I'm not
> intimately familiar with the package so I can't state that with any real
> authority).  And if it is not, then it would get marked "Won't Fix" when
> someone goes through and does post-EOL-release cleanup.  Given that it
> is possible it wouldn't get fixed, because Wily goes end of life in
> three weeks time, I would let this one go, and prepare your environments
> for upgrading to Xenial when Wily dies on the 28th.
>
>
> ------
> Thomas Ward
> Launchpad: ~teward
>
>