[opensuse-factory] How to add the same bug for another product
Hi, I want to submit a bug for opensuse 12.2 however before doing that I searched and found bnc#766762 is the same bug only for 12.1 so how do I add the bug for 12.2 without creating a duplicate Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012/09/06 15:55 (GMT+0200) Togan Muftuoglu composed:
Unless someone has already done so, just comment in the bug that it also applies to 12.2, adding any additional information that might be helpful in fixing it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Togan Muftuoglu <toganm@opensuse.org>:
Indeed, this is a feature bugzilla does not support; it's a one:one link only (bug:product). I'd actually recommend to 'move' the bug to 12.2 (or even 12.3), in the hopes the LXDE maintainers will pick it up. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/06/2012 04:51 PM, Dominique Leuenberger a.k.a DimStar wrote:
This is actually a bad thing there must be a way around it rather than just doing what you recommended and what I have done . Because now the bug does not exists for 12.1 when query, unless I use multiple products in the search I can see it under 12.2
I'd actually recommend to 'move' the bug to 12.2 (or even 12.3), in the hopes the LXDE maintainers will pick it up.
Well today has been not so productive so I decided to go easy and just moved it to 12.2 (for the time being) Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012/09/06 17:06 (GMT+0200) Togan Muftuoglu composed:
On 09/06/2012 04:51 PM, Dominique Leuenberger a.k.a DimStar wrote:
Yes but that would not show the bug is also valid for 12.2 when I do a querry against 12.2 only or ?
Indeed, this is a feature bugzilla does not support; it's a one:one link only (bug:product).
It's hardly unusual that a bug for a non-current version remains a bug in later version(s). I never query for a non-current version without simultaneously querying for subsequent version(s). If you want to narrow your search to an older version filed against, selecting bug creation and ending the date range at the release date of the following release version will probably catch what you're looking for if it exists. I find it annoying for a bug to get moved to a newer version before the version filed against has gone out of support. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Felix Miata <mrmazda@earthlink.net>:
I would say 'It depends'. If the bug is unlikely to get enough traction and warrant for an online update, leaving it on the previous release will not help. As such, moving it brings it 'back in the view'. Alternatively, 'duplicating' it to the new version is possible to of course (with the risk of it being marked as a duplicate...) As no clear guideline exists here on how we should use Bugzilla in this case, I'm afraid different users / maintainers adopted different views and ways of working. It might be worthy to discuss this and define a best-practice. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/06/2012 05:59 PM, Dominique Leuenberger a.k.a DimStar wrote:
Now since the original reporter comments are in place the bugowner would be able to see that the same applies to other versions of openSUSE as well, and hopefully fix it Which reminds me there are 598 open bugs against 11.4 and before closing them and making Carlos loose hair again how about finding a way to validate their existence in other version
Sounds good Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Togan Muftuoglu <toganm@opensuse.org>:
On 09/06/2012 05:59 PM, Dominique Leuenberger a.k.a DimStar wrote:
Feel like organizing a bug-rally weekend? In this particular case I would recommend moving bugs from 11.4 to 12.2 if they still exist. If they don't exist, they _might_ be verified against 12.1 (depends on how much man-power you can rally for this). If they don't exist in 12.1, you can ask Carlos to close it :) Evergreen does, to my knowledge, warrant for security fixes only. Such bugs would likely be picked up already. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/06/2012 06:12 PM, Dominique Leuenberger a.k.a DimStar wrote:
Any guidance how to do that actually I found these two pages on the wiki, <http://en.opensuse.org/openSUSE:Bug_Day> <http://en.opensuse.org/openSUSE:Open-Bugs-Day> which also shows how uptodate openSUSE is actually yada yada the latest, greatest, lacking uptodate documentation oh yes it is a wiki but maybe one should also set a doc-fix week also, Me wanders, why didn't I listen the guy who said it's debian you want nothing else Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
"Dominique Leuenberger a.k.a DimStar" <DimStar@openSUSE.org> writes:
It might be worthy to discuss this and define a best-practice.
I think the only sane way is to clone the bug and set product info accordingly; I think their is a subtle difference using the "Copy to new" button (at the beginning of a bug) or "Clone this bug" link (at teh end). Bugzilla automatically add Depends on/Blocks info (which you sometimes rather want to invert) and comments with the "old" bug number. Thus bugs are nicely chained together and the bug owner can easily work on them. I still do not understand why some reporters, developers or project managers do not like this approach and insist on just "updating" the version info. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Sep 10, 2012 at 05:03:50PM +0200, Karl Eichwalder wrote:
An argument might be to have only one bug ID reference in the package change log. And not multiple with diverging IDs. Here your chaining argument might apply. Do you have a nice example bug? Best would be one present in openSUSE and SUSE Linux Enterprise (SLE) and in multiple different versions. For example openSUSE 12.1, 12.2, Factory and SLE 11 SP 2. I prefer continious cross product package change log entries. The goal is to see only additions when moving to a newer release. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller <lmuelle@suse.com> writes:
An argument might be to have only one bug ID reference in the package change log. And not multiple with diverging IDs.
Yes and no, but often you fix a bug for the recent product and not for an older one such as 12.1 (which you then can properly close as "wontfix"). With our current approach, we often somehow lie... For example, it is no longer possible to properly say how many 11.4 were reported and how many we did not fix, etc.
I prefer continious cross product package change log entries. The goal is to see only additions when moving to a newer release.
I do not see this problem -- in case of trouble, cut-and-paste is your friend ;) (I know you are doing these special samba offerings, but that's not the defaulft case ;) ) -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/10/2012 05:03 PM, Karl Eichwalder wrote:
Thanks for pointing out "Clone this bug" feature, as if you hadn't told I would have missed it forever since the location of this feature is as if it doesn't want to be used, so maybe move this link to the upper top of the page where it makes more sense Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 12 Sep 2012 09:57:45 +0200 Togan Muftuoglu <toganm@opensuse.org> wrote:
so maybe move this link to the upper top of the page where it makes more sense
There is many important links on each bug report page. Interface absolutely needs improvement, and that is not just moving links around. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012/09/06 15:55 (GMT+0200) Togan Muftuoglu composed:
Unless someone has already done so, just comment in the bug that it also applies to 12.2, adding any additional information that might be helpful in fixing it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Togan Muftuoglu <toganm@opensuse.org>:
Indeed, this is a feature bugzilla does not support; it's a one:one link only (bug:product). I'd actually recommend to 'move' the bug to 12.2 (or even 12.3), in the hopes the LXDE maintainers will pick it up. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/06/2012 04:51 PM, Dominique Leuenberger a.k.a DimStar wrote:
This is actually a bad thing there must be a way around it rather than just doing what you recommended and what I have done . Because now the bug does not exists for 12.1 when query, unless I use multiple products in the search I can see it under 12.2
I'd actually recommend to 'move' the bug to 12.2 (or even 12.3), in the hopes the LXDE maintainers will pick it up.
Well today has been not so productive so I decided to go easy and just moved it to 12.2 (for the time being) Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012/09/06 17:06 (GMT+0200) Togan Muftuoglu composed:
On 09/06/2012 04:51 PM, Dominique Leuenberger a.k.a DimStar wrote:
Yes but that would not show the bug is also valid for 12.2 when I do a querry against 12.2 only or ?
Indeed, this is a feature bugzilla does not support; it's a one:one link only (bug:product).
It's hardly unusual that a bug for a non-current version remains a bug in later version(s). I never query for a non-current version without simultaneously querying for subsequent version(s). If you want to narrow your search to an older version filed against, selecting bug creation and ending the date range at the release date of the following release version will probably catch what you're looking for if it exists. I find it annoying for a bug to get moved to a newer version before the version filed against has gone out of support. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Felix Miata <mrmazda@earthlink.net>:
I would say 'It depends'. If the bug is unlikely to get enough traction and warrant for an online update, leaving it on the previous release will not help. As such, moving it brings it 'back in the view'. Alternatively, 'duplicating' it to the new version is possible to of course (with the risk of it being marked as a duplicate...) As no clear guideline exists here on how we should use Bugzilla in this case, I'm afraid different users / maintainers adopted different views and ways of working. It might be worthy to discuss this and define a best-practice. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Dominique Leuenberger a.k.a DimStar -
Felix Miata -
Karl Eichwalder -
Lars Müller -
Rajko -
Togan Muftuoglu