Re: Fwd: The grep disaster
> My mistake, it affected three people. I assume you mean the number of people who marked it as "it affects me" in Launchpad. The existence of the bug is confirmed in a few comments beyond reasonable doubt (you should be able to verify it yourself), hence it potentially affects at least everybody who has wily (and apparently Xenial) and hasn't tweaked it by manually installing other versions of grep. I hope you don't take the number of "affected" people on Launchpad as a reliable indicator (even if only in proportion) of the affected users in the real world. > Most people here isn't paid for the job, and they do it just for the willingness of helping. I KNOW. Perhaps I misused the word "job", I meant "mission" or "what you do as a...". I thought it had that meaning too. > It is actually fixed in upstream project, and also in Debian. Someone commented on the Launchpad issue that it regressed again. But then I don't know if it has been fixed again. Either way, that's precisely why I don't understand why it takes so long to have it fixed in Ubuntu. > It might as well be fixed in 16.04. According to the comments on Launchpad, it doesn't seem so. 2016-06-25 9:40 GMT+02:00 Marius Kotsbak : > It is actually fixed in upstream project, and also in Debian. It might as > well be fixed in 16.04. > 25. jun. 2016 04:29 skrev "Alberto Salvia Novella" >: > >> Alberto: >> >>> Moreover this particular bug affected only one known person. >>> >> >> My mistake, it affected three people. So probably it would be its >> description needed my latest update. >> >> (https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458) >> >> >> >> -- >> Ubuntu-quality mailing list >> Ubuntu-quality@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality >> >> -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Fwd: The grep disaster
It is actually fixed in upstream project, and also in Debian. It might as well be fixed in 16.04. 25. jun. 2016 04:29 skrev "Alberto Salvia Novella" : > Alberto: > >> Moreover this particular bug affected only one known person. >> > > My mistake, it affected three people. So probably it would be its > description needed my latest update. > > (https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458) > > > > -- > Ubuntu-quality mailing list > Ubuntu-quality@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Fwd: The grep disaster
Alberto: Moreover this particular bug affected only one known person. My mistake, it affected three people. So probably it would be its description needed my latest update. (https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Fwd: The grep disaster
PHP Fan: > As far as I understand, Launchpad is the place where all bugs are > tracked, no matter how important. Excuse my brief and mysterious way of writing. What I do myself if to set importance to all the confirmed bugs, so where to begin is always warranted to be known. On the other hand we cannot tell if a bug is more or less important when posted in this mailing list, so that's why we won't jump into those. PHP Fan: > Regardless of the effort of fixing the bug, is it that difficult to > roll back the package to a version that is not completely broken?? It would take mostly the same time to fix this bug than to revert the package to a previous version. The difference is that reverting usually breaks new things. PHP Fan: > Isn't that part of the job of a distribution's maintainers, and > especially of a team calling itself the "Quality" team, to take such > kind of actions? Most people here isn't paid for the job, and they do it just for the willingness of helping. Moreover this particular bug affected only one known person. So this is why it received that little attention, because just one person worldwide seems to be annoyed enough by it. Meanwhile: (https://goo.gl/MCR5Ht) (https://goo.gl/0ycxvw) C de-Avillez: > You may want to poke upstream about that. I think Carlos is right. Upstream could point directly to a patch, or even fix the bug themselves for you. In any case thanks for reporting. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Fwd: The grep disaster
> I am sorry we cannot help you more in this list than what we already do in Launchpad. [Which is basically nothing] Are you subtly implying that there's no point in writing to this mailing list about an issue just because it is already tracked on Launchpad? As far as I understand, Launchpad is the place where all bugs are tracked, no matter how important; on the other hand, I would expect this list to be the appropriate place for, among of course other things, discussing urgent action to be taken about some critical issue that renders some core part of the system completely unusable, for example. Like this one. Regardless of the effort of fixing the bug, which I understand is a long process and is tracked on Launchpad (where it seems that nothing is being done and nobody cares, like "let's just wait until it's fixed [again] upstream", but that's another story), is it that difficult to roll back the package to a version that is not completely broken, and release an update with it, until a fix is released which may be in ages?? Isn't that part of the job of a distribution's maintainers, and especially of a team calling itself the "Quality" team, to take such kind of actions? I may understand if you told me that even that is not as easy as it seems, or if you argued about good reasons for not doing that. But instead nobody seems to even consider that possibility; not only that, you keep replying as if I hadn't even ever mentioned it. 2016-06-25 1:33 GMT+02:00 Alberto Salvia Novella : > PHP Fan: > > No action has been taken to the present day to fix the issue. > > I am sorry we cannot help you more in this list than what we already do in > Launchpad. > > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Fwd: The grep disaster
PHP Fan: > No action has been taken to the present day to fix the issue. I am sorry we cannot help you more in this list than what we already do in Launchpad. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Fwd: The grep disaster
(I sent this reply to Alberto by mistake instead of the list) > I think you already said that before, indeed more than once. Not more than once. I did once, but it got completely ignored*, and then I had tried to send this very message but it got rejected. * EDIT: I correct myself: it was probably not ignored, but no action has been taken to the present day to fix the issue in Ubuntu, so it completely makes sense to raise the issue again to the attention of the QA team, the point being that such a thing cannot stay unfixed in the distribution for so long. > You may want to poke upstream about that. You are missing the point. Given the severity of the issue, until it is fixed upstream, the ubuntu package should be urgently rolled back to a workable version. I wonder how you people can even work in an environment where grep is broken. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
