I'd like to inform you about the following two changes to bugzilla:
openSUSE 10.3 =============
We have created a new product and opened it. Some of the bugs that will not be fixed for 10.2 are moved over to that product.
SUSE Linux 10.0 ===============
Our policy is to only fix security bugs for released products and we fix the occasional critical bugs. Security bugs are reported by the security team and with 10.1 out and 10.2 nearly finished, we're not fixing critical bugs anymore so we do not really need a public bugzilla here. We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
SUSE Linux 10.1 will stay open for now - and openSUSE 10.2 is the product we're working on,
Andreas
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
Two questions:
1. What exactly does non-public mean?
a) nobody can report bugs against 10.0 or b) nobody can view 10.0 bugs - this would be a very bad idea!
2. What makes you sure that nobody abuses 10.1, 10.2 or opensuse.org then? ;-))
Regards,
Christian Boltz
Christian Boltz opensuse@cboltz.de writes:
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
Two questions:
What exactly does non-public mean?
a) nobody can report bugs against 10.0 or
Only the Novell folks and some of our old beta testers can report bugs against it.
b) nobody can view 10.0 bugs - this would be a very bad idea!
I'll check whether this is possible.
- What makes you sure that nobody abuses 10.1, 10.2 or opensuse.org then? ;-))
10.0 and 10 are too similar - but yes, I cannot be sure ;-(
Andreas
Andreas Jaeger aj@suse.de writes:
Christian Boltz opensuse@cboltz.de writes:
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
Two questions:
What exactly does non-public mean?
a) nobody can report bugs against 10.0 or
Only the Novell folks and some of our old beta testers can report bugs against it.
b) nobody can view 10.0 bugs - this would be a very bad idea!
I'll check whether this is possible.
This is possible - and it's setup this way now. If something is not working as expected, please tell me.
To clarify: Everybody can still look at bugs reported against 10.0 - but entering is not possible anymore for the general public,
Andreas
On 2006-11-20 13:00, Andreas Jaeger wrote:
<snip> Our policy is to only fix security bugs for released products and we fix the occasional critical bugs. Security bugs are reported by the security team and with 10.1 out and 10.2 nearly finished, we're not fixing critical bugs anymore so we do not really need a public bugzilla here. We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
Would this be the reason why I am unable to read the bug report (100692) concerning opening ports on the external zone in the Yast firewall setup?
Darryl Gregorash raven@accesscomm.ca writes:
On 2006-11-20 13:00, Andreas Jaeger wrote:
<snip> Our policy is to only fix security bugs for released products and we fix the occasional critical bugs. Security bugs are reported by the security team and with 10.1 out and 10.2 nearly finished, we're not fixing critical bugs anymore so we do not really need a public bugzilla here. We do see some misuse especially with 10.0 where people report bugs against different products or ask for general help and have therefore decided to make it non-public tomorrow.
Would this be the reason why I am unable to read the bug report (100692) concerning opening ports on the external zone in the Yast firewall setup?
No - that bug was reported against SLES10 and is only open to Novell developers (no change here at all). Marking another as duplicate of this was a bad idea ;-(
Andreas
On 2006-11-25 04:24, Andreas Jaeger wrote:
Darryl Gregorash raven@accesscomm.ca writes:
Would this be the reason why I am unable to read the bug report (100692) concerning opening ports on the external zone in the Yast firewall setup?
No - that bug was reported against SLES10 and is only open to Novell developers (no change here at all). Marking another as duplicate of this was a bad idea ;-(
It was present at least in 9.3, and probably before then, but as I always used the sysconfig editor to configure firewall ports, I didn't discover it until someone reported it for 10.1, in suse-linux-e. Surprising that no one reported it until SLES10.
Does the "no change" remark mean its still not fixed in 10.2? :-(
Darryl Gregorash raven@accesscomm.ca writes:
On 2006-11-25 04:24, Andreas Jaeger wrote:
Darryl Gregorash raven@accesscomm.ca writes:
Would this be the reason why I am unable to read the bug report (100692) concerning opening ports on the external zone in the Yast firewall setup?
No - that bug was reported against SLES10 and is only open to Novell developers (no change here at all). Marking another as duplicate of this was a bad idea ;-(
It was present at least in 9.3, and probably before then, but as I always used the sysconfig editor to configure firewall ports, I didn't discover it until someone reported it for 10.1, in suse-linux-e. Surprising that no one reported it until SLES10.
Does the "no change" remark mean its still not fixed in 10.2? :-(
Yes :-(
Andreas
On 2006-11-26 00:12, Andreas Jaeger wrote:
Darryl Gregorash raven@accesscomm.ca writes:
Does the "no change" remark mean its still not fixed in 10.2? :-(
Yes :-(
Thanks.
Should I file another bug report? :-)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger wrote:
I'd like to inform you about the following two changes to bugzilla:
openSUSE 10.3
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
- -- Cheers, Carlos E. R.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Sunday 11 February 2007 06:51, Carlos E. R. wrote:
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger wrote:
I'd like to inform you about the following two changes to bugzilla:
openSUSE 10.3
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
I have to second your opinion. The problem is the policy or guys that mark bugs as duplicate.
For me, bug that is reported in restricted zone should not be announced publicly by marking some public bug as duplicate of restricted one. If it is really necessary, it would be probably better to do the same in opposite direction, mark restricted bug as public one.
That way whoever is user of restricted zone can look for a solution, and no info runs out of restricted zone.
On Sun, 11 Feb 2007, Rajko M. wrote:
On Sunday 11 February 2007 06:51, Carlos E. R. wrote:
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger wrote:
I'd like to inform you about the following two changes to bugzilla: openSUSE 10.3 =============
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
I have to second your opinion. The problem is the policy or guys that mark bugs as duplicate.
For me, bug that is reported in restricted zone should not be announced publicly by marking some public bug as duplicate of restricted one. If it is really necessary, it would be probably better to do the same in opposite direction, mark restricted bug as public one.
That way whoever is user of restricted zone can look for a solution, and no info runs out of restricted zone.
This is really the most annoying issue with bugzilla. There really should be a policy to create a not restricted bug for any bug marked as a duplicate of a restriced bug. Reference the restricted bug for those that have to keep the information such, but all information that may be public must be made public. That way community memember and other will be able to follow but bug and not create more bugs that have already been reported. I always do a search to make sure my bugs are not duplicates. The only problem is I am not able to verify restricted bugs, this creates more work for both as we are unable to verify bug and therefore create a new bug that creates work for Novell to check and then assign bug.
Please create a non-restricted bug and follow up an it in the open. Use reference bug only for restrited content.
Thanks,
-- Boyd Gerber gerberb@zenez.com ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E. R.:
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger wrote:
I'd like to inform you about the following two changes to bugzilla:
openSUSE 10.3
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
You can report it for now to this list or to me.
I will try to find some more official place (maybe some screening team can help out here ... )
I am not sure, if I can open the bug, but I have asked ....
thanks adrian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
You can report it for now to this list or to me.
Ok. What I did (before seeing your email) was forward an email to Q.A. contact of the bug - I assume that QA means "quality assurance"?
I will try to find some more official place (maybe some screening team can help out here ... )
I am not sure, if I can open the bug, but I have asked ....
Thank you!
Perhaps the bugzilla developers could add a feature not allowing to close a report as duplicate when the other one is restricted; ie, forcing to keep both open.
You see, I understand the need to keep some reports restricted; what I object to is to closing the non restricted report for that reason.
- -- Cheers, Carlos E. R.
On Sun, 11 Feb 2007, Adrian Schröter wrote:
I am not sure, if I can open the bug, but I have asked ....
This is just one specific bug. Wrt. the general issue I would like bugzilla.novell.com to warn whenever someone tries to mark an openSUSE bug a duplicate of a restricted one.
Thoughts?
Gerald
Hello,
Am Montag, 12. Februar 2007 schrieb Gerald Pfeifer:
On Sun, 11 Feb 2007, Adrian Schröter wrote:
I am not sure, if I can open the bug, but I have asked ....
This is just one specific bug. Wrt. the general issue I would like bugzilla.novell.com to warn whenever someone tries to mark an openSUSE bug a duplicate of a restricted one.
Such a warning is already in place. If you want to see how it looks like, have a look at http://www.cboltz.de/tmp/bugzilla-duplicate-permission-warning.png [1]
IMHO this warning is visible enough - but it seems it is often ignored :-(
Hmm, maybe it should really be made more visible. My proposal: blinking, fat, large red text, a chain of 20 "do you really want to do this?" pages (all captcha-protected if "yes" is selected) and a loud siren sound in the background so that everyone in the office knows what you are doing *SCNR*
Sidenote: This discussion is a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=155846 ;-)) (and I won't complain if someone reopens it)
Regards,
Christian Boltz, BBfH [2]
PS: It's also possible to mark single comments as private/novellonly (which is also done from time to time - maybe you already found some bugreports where some comment numbers seem to be missing) - so it would even be possible to have "open" bugreports with just the secret parts hidden.
[1] Before you ask: I have access to bugs for older SUSE Linux versions, but not for "novellonly" or SLE* bugs which are the major problem nowadays.
[2] Well, I guess you know BOfH - in BBfH, the second B means "Bugreporter" ;-)
On 2007-02-12 07:11, Christian Boltz wrote:
<snip> fat, large red text, a chain of 20 "do you really want to do this?" pages (all captcha-protected if "yes" is selected) and a loud siren sound in the background so that everyone in the office knows what you are doing *SCNR*
The 20th page should offer a choice of "no" or "no" :-)
On 2007-02-11 14:41, Adrian Schröter wrote:
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E. R.:
<snip>
I am not sure, if I can open the bug, but I have asked ....
Please do the same for my bug report on the Yast firewall allowed services problem for the external zone, https://bugzilla.novell.com/show_bug.cgi?id=214855
This bug has been around since 9.3, according to Marcus was first reported asbug 100692 for SLES 9 (or a version of that vintage), and is still alive in 10.2. 214855 was marked as a duplicate of 100692.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E. R.:
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
You can report it for now to this list or to me.
Ok. Another one.
Bug 257168
Closed as duplicate of bug 233122. This one is restricted, so I reopen it. "He" again closes as "RESOLVED INVALID".
!!!!! :-/
Novell, You really have to address this kind of issues, hire an ombudsman, or something.
- -- Cheers, Carlos E. R.
On Fri, Mar 23, 2007 at 09:58:38PM +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E. R.:
Whom do we contact when we have problems with Bugzilla, what is the procedure?
For instance, I reported time ago "bug 225631", which is now marked as duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the problem to? I do not want to reopen it myself, but I would like to see the conclussions of the problem, which are restricted.
You can report it for now to this list or to me.
Ok. Another one.
Bug 257168
Closed as duplicate of bug 233122. This one is restricted, so I reopen it. "He" again closes as "RESOLVED INVALID".
!!!!! :-/
Novell, You really have to address this kind of issues, hire an ombudsman, or something.
We already told sometime ago that we cannot release -debuginfo packages due to its excessive sizes... Its just too big.
The 10.2 update repo is already nearing to 4GB, it would be >50GB with debuginfos (at least, if not more).
The other bug is open now.
Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2007-03-23 at 23:45 +0100, Marcus Meissner wrote:
We already told sometime ago that we cannot release -debuginfo packages due to its excessive sizes... Its just too big.
Didn't know that.
The 10.2 update repo is already nearing to 4GB, it would be >50GB with debuginfos (at least, if not more).
The other bug is open now.
Thanks! :-)
[...]
Reading it, I understand that to investigate Bug 256363 some one should supply me with the correct kdelibs3-debuginfo (Comment #8 of Bug 233122).
The thing is that I discovered a big memory hole in kbabel, of 2 GiB size. I reported this, and was told to use ulimit -m 300000 to force it crash before it ate all available swap (this does not work, by the way).
In order to get a meaningful backtrace I should first install the corresponding debuginfo rpms: qt3, kdelibs3 and kdesdk3. But Yast complained and refused, because kdelibs3 has been updated and there is no corresponding update for -debuginfo.
So I again reported that, and instead of being told what the problem is, it was closed as duplicate or a restricted bug!
You can imagine how pissing is to be artificially blocked when trying to help solve a bug!
So, again, thank you for your help and clarification.
- -- Cheers, Carlos E. R.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-
Adrian Schröter -
Andreas Jaeger -
Boyd Lynn Gerber -
Carlos E. R. -
Christian Boltz -
Darryl Gregorash -
Gerald Pfeifer -
Marcus Meissner -
Rajko M.