Re: #1543046 wrongly marked as fixed for Wily
On Thu, Jul 7, 2016 at 9:13 PM, php fan wrote: > > 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. > Looks like this was just an oversight, and should make it into Wily before EOL. Good. > > 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"). > Not sure that's really even a bug anymore. But since it seemed to worry you, I tried a fresh Wily desktop install, fully updated and upgraded to Xenial. Not a problem for me, I was not able to recreate this bug: http://pastebin.ubuntu.com/18862815/ I tried it twice and both times, I was able to successfully upgrade from Wily to Xenial with no failed packages. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
On Fri, 8 Jul 2016 03:13:51 +0200 php fan wrote: > > 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"). @php4fan: I expected you to have understood, as of now, that this list, and all of the Ubuntu lists, are bound by the CoC. As such, putting you on moderation. Cheers, ..C.. pgpdF9Rxd4lPF.pgp Description: OpenPGP digital signature -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
Please stop... we don't need any type of bickering or arguing on the list, there's better ways to handle your difference of opinions. It's also not relevant to the original report. ThermalD falls under the purview of the Kernel team. I've poked this up to the Kernel team, and they'll take another look at it. Any progress on the bug itself will come from the Kernel team, on the bug itself. Lets leave the discussion of whether or not something was miscommunicated or misunderstood or similar off the list. You've come and told someone that the issue is not fixed, and I've sent it to the correct team accordingly for them to poke at it. -- Thomas Ubuntu Server Team Ubuntu Bug Triager Launchpad: ~teward On 07/08/2016 11:13 AM, php fan wrote: > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
You obviously misunderstood my reply to your question (which maybe I misunderstood in turn). You asked me: > What is the different between a team member and you on testing the bug? Which I interpreted as "why would you expect anybody from the QA team to test a bug more than you'd expect anybody else to"? I was replying to that, and I explicitly stressed: > (note, before you ban me, this is a "generic 'you'" and an hypothetic 'if') > If you don't care about helping Ubuntu QA, why are you in this list in the first place? [note an important difference between this question and mine: I asked "if you don't care *that much*", not "if you don't care", by which I meant "enough to run a one-command-line test to check whether the issue is actually fixed in Trusty"] I do care about helping Ubuntu QA. That's why I am in this list, and that's why I wrote to it to inform you that there's a bug that is incorrectly marked as fixed in Wily, which I thought was an issue that should be of interest to the QA team. I am surprised that a QA team member (not you) would rather spend their time explaining why it's not so important to correct the status of the bug, than spend a tiny fraction of that time to actually do it. 2016-07-08 14:33 GMT+02:00 Alberto Salvia Novella : > Alberto: > >> If you don't care about helping Ubuntu QA, why are you in this list in >> the first place? >> > > Oh men, I obviously should not answer messages like these. As they can > turn a good day into something worse. > > So I'm moving to the happy band, thank you. > > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
Alberto: If you don't care about helping Ubuntu QA, why are you in this list in the first place? Oh men, I obviously should not answer messages like these. As they can turn a good day into something worse. So I'm moving to the happy band, thank you. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
PHP Fan: Just that if you don't care that much I wonder why you are a member of the QA team in the first place. If you don't care about helping Ubuntu QA, why are you in this list in the first place? Take an example: (http://i35.servimg.com/u/f35/16/19/87/90/graph10.png) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: #1543046 wrongly marked as fixed for Wily
> What is the different between a team member and you on testing the bug? What's the difference between a team member and me in anything related to helping make ubuntu better? None, just that if you don't care that much I wonder why you are a member of the QA team in the first place (note, before you ban me, this is a "generic 'you'" and an hypothetic 'if'). As I said, the only reason I don't test the bug myself on Trusty (or Xenial, for that matter) is that I don't have a machine with Trusty. It seems unlikely that nobody in the QA team has a machine with Trusty.. 2016-07-08 5:44 GMT+02:00 Alberto Salvia Novella : > PHP Fan: > >> If I were a member of a QA team, I would test it on Trusty. >> > > What is the different between a team member and you on testing the bug? > > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
