Re: [opensuse] polluting the filesystem
On Sat, Mar 19, 2016 at 2:03 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2016-03-19 a las 13:14 -0600, Chris Murphy escribió:
On Sat, Mar 19, 2016 at 5:37 AM, Carlos E. R. <t> wrote:
As far as I'm concerned, the bugzilla is in "new" state, and no question was asked of me (or the bugzilla would be in "need info" state. And if the issue would be solved, then the bugzilla would be in "closed" state.
Its a bureaucracy :-)
13.1 went end-of-life over two months ago.
It is still under maintenance. Evergreen cycle, LTS. You must be new here.
I guess I'm just reading between the lines differently than you are, in a way that I think is practical and reasonable, while yours is impractical and unreasonable. https://en.opensuse.org/openSUSE:Evergreen 13.1 is EOL. It is not officially supported. The Evergreen community is small and needs user assistance to make it viable. "Since we are a small community doing Evergreen we would appreciate if users could join us in testing upcoming updates." And Everygreen provides "security and stability fixes". The bug you've referred to is, by your own admission an edge case, not a stability problem. There's no good reason to expect this bug to be fixed by the Evergreen team except incidentally. So feel free to pick up a shovel if you think it should be fixed in 13.1, but you might want to first see if it even is still broken.
Unless the asignee closes it for whatever reason, as far as I'm concerned the bug is valid and unsolved (his job, not mine). That's all that matters to me.
There is no evidence at all the assignee participates in Evergreen. Not everyone does. Participation is voluntary. And all sorts of bugs get fixed without bug reports getting closed. That's simply not how any bug reporting system works anywhere. Closing bug reports as fixed is a courtesy. It is not a practical standard operating procedure to know when every bug has been fixed. By your own admission you haven't even tested this recently: not in 18 months at least, with 13.1 current updates applied, let alone 13.2 or 42.x. So it's not even certain the bug is still reproducible with 13.1 with all updates applied. I don't know why you think it's someone else's job to do this testing in a community driven project. If you don't care about this problem, why should someone else care? -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-19 21:43, Chris Murphy wrote:
On Sat, Mar 19, 2016 at 2:03 PM, Carlos E. R.
13.1 went end-of-life over two months ago.
It is still under maintenance. Evergreen cycle, LTS. You must be new here.
I guess I'm just reading between the lines differently than you are, in a way that I think is practical and reasonable, while yours is impractical and unreasonable.
https://en.opensuse.org/openSUSE:Evergreen
13.1 is EOL. It is not officially supported. The Evergreen community is small and needs user assistance to make it viable. "Since we are a small community doing Evergreen we would appreciate if users could join us in testing upcoming updates." And Everygreen provides "security and stability fixes". The bug you've referred to is, by your own admission an edge case, not a stability problem. There's no good reason to expect this bug to be fixed by the Evergreen team except incidentally. So feel free to pick up a shovel if you think it should be fixed in 13.1, but you might want to first see if it even is still broken.
Again you misunderstand. I do not want it to be solved in 13.1.
By your own admission you haven't even tested this recently: not in 18 months at least, with 13.1 current updates applied, let alone 13.2 or 42.x. So it's not even certain the bug is still reproducible with 13.1 with all updates applied. I don't know why you think it's someone else's job to do this testing in a community driven project. If you don't care about this problem, why should someone else care?
Of course I have not tested it again in this time, as I was waiting for an official response. That's the procedure. I'm testing it now, in fact. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (2)
-
Carlos E. R. -
Chris Murphy