Mailinglist Archive: opensuse-project (382 mails)

< Previous Next >
Re: [opensuse-project] Re: bugs that are against 11.1
Hello,

Am Mittwoch, 16. Mai 2012 schrieb Andrew Joakimsen:
But then sometimes submitting logs is just silly.

I submitted a bug because there's package nagios-plugins-apt built
against openSUSE. This package is used to monitor the status of
apt-get updates on Debian distros. It can not install on openSUSE
through zypper due to a missing dependency of apt. But somehow I am
asked for y2logs!? Is this not enough:

Problem: nothing provides /usr/bin/apt-get needed by
nagios-plugins-apt-1.4.15-47.1.x86_64
Solution 1: do not install nagios-plugins-extras-1.4.15-47.1.x86_64
Solution 2: break nagios-plugins-apt by ignoring some of its
dependencies

Choose from above solutions by number or cancel [1/2/c] (c):

I assume you are talking about
https://bugzilla.novell.com/show_bug.cgi?id=761676

You are right - in this case, y2logs are not needed. Looks like Kun Kan
Zhang is trained on requesting logs for every YaST bug ;-) (and in 99%
of the cases, they are needed)

OTOH you as bugreporter also weren't perfect ;-)
Let me tell you could do better:
- report the bug against the correct component - it is clearly a bug in
the nagios-plugins package, not a YaST bug - therefore choosing
"YaST2" as component doesn't make too much sense. I'd choose one of
Network, Basesystem or Other.
- assign the bug directly to the package maintainer:
# osc maintainer openSUSE:Factory nagios-plugins
bugowner of server:monitoring/nagios-plugins :
schneemann AT b1-systems.de

Hint: you can still change the component and reassign the bug ;-)


Regards,

Christian Boltz
--
Womit erstellt ihr so eure Homepages?
mit vim *g*. Wobei es Leute gibt, die tatsächlich behaupten, das soll
auch mit diesem Betriebssystem - wie heißt es doch gleich - *äh* Emacs
gehen. <SCNR> [> Bernd Stäglich und Philipp Zacharias in suse-linux]

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

< Previous Next >