Mailinglist Archive: opensuse-packaging (174 mails)

< Previous Next >
Re: [opensuse-packaging] factory-auto will start checking bnc# visibility
Am Freitag, 22. November 2013, 15:44:59 schrieb Ruediger Meier:
On Friday 22 November 2013, Adrian Schröter wrote:
Am Freitag, 22. November 2013, 15:14:50 schrieb Ruediger Meier:
On Friday 22 November 2013, Andreas Jaeger wrote:
On 11/22/2013 03:00 PM, Ruediger Meier wrote:
On Thursday 21 November 2013, Adrian Schröter wrote:
Am Donnerstag, 21. November 2013, 14:16:48 schrieb Claudio
On Thu, Nov 21, 2013 at 1:04 PM, Stefan Behlert
<behlert@xxxxxxx> wrote:


This would mena that someone has to do this e.g. for all
referenced security bugs, all SLES/SLED bugs and much more.

Supposedly, the work for extracting a minimal description of
the bug into a public source would be small compared to
actually fixing the bug.

True, but this can be done directly in the .changes file. Some
description about the change had to be written there anyway.

If that description is not good enough openSUSE-Factory
maintainers can of course reject the package.

Well, IMO the maintainer can only objectively rate the
description if he also can't access the bnc.

But please keep in mind that openSUSE is currently using SUSE
bugzilla. I do not think want to double the effort to maintain
an own bug system and to sync the data always.
So we need some compromise here.

Of course we could also build in some OBS feature to track
some data elsewhere and jsut generate it inside when it got
built within a different context. But I think it will create
too much confusion for most people.

Actually I don't understand the problem completely. Are SLES
customers able to access all the bugs?

SLES customers report bugs to NTS which then open bugs - and
partners report directly to NTS. Both groups might include
private information. Partners for example have only access to the
bugs they reported,

So then it's even annoying for SLES customers to see all these
private references. Suse should track their private references
elsewhere as you mentioned.

You forget that openSUSE is using SUSE bugzilla. So openSUSE would
need to look for a new bug tracker ...

No, I don't care about about private bugs in bugzilla. I just don't want
to have them in submit messages, changelogs and patchinfo of openSUSE

Again, just removing information does not help anyone and will have bad
impact on the workforce in openSUSE Factory.
Could we agree that we may need to mark them differently, eg. with a different
tag so no one is loosing time trying to open it?

However, I am actually happy that we have only one. In most cases it
makes the collaboration much easier.

One thing would be nice. I'd like to have a blacklist in my bugzilla
preferences for all the "uninteresing" Classification, Product,
Component drop down lists. Maybe this would be a new bugzilla
feature ?!

well, I dunno in which situation this shall happen. Just because your account
is marked that you are an openSUSE use does not say you have not any other

Usually a good idea is store specific searches. That is at least what I do when
jumping between my different roles.


Adrian Schroeter
email: adrian@xxxxxxx

SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups