https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c1 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED CC| |lrupp@suse.com, | |schneemann@b1-systems.de Platform|Other |All Found By|--- |Customer AssignedTo|schneemann@b1-systems.de |lrupp@suse.com Severity|Major |Minor --- Comment #1 from Lars Vogdt 2014-01-19 02:15:10 CET --- Taking over. Thanks for the heads up. IMHO "compromised" may be the wrong wording in this special case, but I understand that the situation might not be easy to understand for a simple package maintainer. As long as the provided sources on both sides are the same, I currently see no urgent need to react here - therefor adopting severity. Might be time to think about the directory name for the plugins itself in the near future, too, but I like to wait until the discussion in the RedHat Bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1054340) is finished and/or the projects release new sources. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c2 --- Comment #2 from Michael Friedrich 2014-01-19 01:42:58 UTC --- Sorry for the offensive phrasing, I made the same mistake on the linked RHEL bug, and rephrased the text later on for other upstream maintainers. FreeBSD & OpenBSD changed their upstream URLs already. In terms of upgrading the package I do see the same problem as outlined here https://bugzilla.redhat.com/show_bug.cgi?id=1054340#c26 as the sources provided on nagios-plugins.org are different to what the SUSE package history is built on. User upgrading their packages trust these packages, and a newly formed upstream source is totally different. Especially since the new Nagios Plugin Development Team is unknown - no git commits, no further announcements other than taking over the project. And yet no evidence or proof how the nagios plugins project will continue. Though I welcome the idea to change packages and locations to a more generic version, and that's probably the same outcome as Fedora/RHEL will provide. Only the upgrade problematic should be handled properly, to keep the users safe. Nagios Enterprises has proven itself not to be trustworthy, nor predictable in their actions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c4 --- Comment #4 from Michael Friedrich 2014-01-19 14:17:43 UTC --- (In reply to comment #3)

(In reply to comment #2)

...

In terms of upgrading the package I do see the same problem as outlined here https://bugzilla.redhat.com/show_bug.cgi?id=1054340#c26 as the sources provided on nagios-plugins.org are different to what the SUSE package history is built on.

I agree that this will affect new package submissions.

But I currently doubt that our users will download tarballs from the included Url that our RPMs provide to re-built the plugins on their own again. That's why they installed the RPM. So this will not result in a package update for released versions.

No, that's only a matter of new package revisions or upstream releases imho.

The provided documentation on both sides in the meantime is identical (even on monitoring-plugins.org, the documentation mention the "Nagios Plugin Development Team", which might be considered an upstream bug now).

I'll forward them your note. The problem with that rename was like: 22:30 - chatting with Holger, checking nagios-plugins.org - hey, where did icinga/naemon/shinken mention and urls go? - interesting. it's not the webserver by holger serving nagios-plugins.org but a box owned by nagios inc - edit holger website - no change. - ok, they've copied the complete website 1:1 and hijacked the dns forwarder entries There was no prior notice, or private notification by Nagios Enterprises. They just did it, and are now trying to confuse everyone claiming that nagios-plugins.org acts like before. So there is plenty of work to do for the original team working towards 1.6 release, but now having fun to rename all their stuff in their sparetime.

Please note (from http://www.rpm.org/max-rpm/s1-rpm-build-creating-spec-file.html): "While the source line is used to provide the source filename to RPM, the URL line points to documentation for the software being packaged."

Our current nagios-plugins package (submitted to server:monitoring right now) contains: Url: http://monitoring-plugins.org/ Source0: nagios-plugins-%{version}.tar.bz2

So this bug might be considered fixed already.

Yep, since you're not using a complete URL for Source0, you're safe. Other spec files in the RHEL world do (I've modified repoforge already where I do help out).

But I hope the "new" Monitoring Plugin Development Team will provide new sources some day that might also change more than the points mentioned in the summary of this bug.

So I like to keep it open until this is done.

Yep that's a good idea. I think once a new release is ready, a new tarball name will be made available - and considerably a transitional package could be created then reflecting the new name, but satisfying remaining package dependencies. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c6 --- Comment #6 from Lars Vogdt 2014-01-24 15:24:35 CET --- (In reply to comment #5)

Problem: we currently use /usr/lib/nagios/plugins/ as base directory for all plugins. Going with the more universal "monitoring-plugins" approach, this should be reflected in the directory structure of the new package:

The way RPM updates are applied (first installing the new package content, afterward removing the old content that's left), prevents us from simply replacing the /usr/lib/nagios/plugins/ directory with a simple symlink for the moment. If we want to go that way (providing a symlink from /usr/lib/monitoring-plugins or /usr/lib/monitoring/plugins to /usr/lib/nagios/plugins), we need to have some "magic" at hand (like a %pre script that moves the files around and/or patches all(!) configuration files). In most cases, the rename of the package is not a big deal, but the move to a new directory for the plugins will produce a lot of problematic situations: * configurations of nagios, shinken, icinga define a $USER1$ variable * configuration of nrpe => each command/included file can have the path configured * other configs from 3rd party might also be affected * a customer may have additional files in the directory, that need to be migrated to a new directory, too (including the confusion of the customer if this is done "automatically") -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c8 --- Comment #8 from Bernhard Wiedemann 2014-03-28 13:00:15 CET --- This is an autogenerated message for OBS integration: This bug (859105) was mentioned in https://build.opensuse.org/request/show/228069 Factory / nagios-plugins -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c10 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #10 from Lars Vogdt 2014-07-24 10:25:09 CEST --- Closing this bug now, as monitoring-plugins 2.0 is available and the package has been renamed in server:monitoring (TODO: openSUSE:Factory, but this is on the way). The plugins are for now still using the /usr/lib/nagios/plugins/ directory, as changing this would affect many configurations and might become a maintenance nightmare as other plugins use the same directory for years now. Thanks for your great work on the plugins and ongoing support! JFYI: 1) old nagios-plugins The build of the old nagios-plugins package is disabled. The package should stay in server:monitoring for reference. 2) new nagios-core-plugins There is also a nagios-core-plugins package now in server:monitoring, but as the code there does not build because of compiler errors. I leave this package up to someone who wants to fix and maintain it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.