[Bug 859105] New: server:monitoring/nagios-plugins: Bug: Update Upstream URL to https://www.monitoring-plugins.org
https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c0 Summary: server:monitoring/nagios-plugins: Bug: Update Upstream URL to https://www.monitoring-plugins.org Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: schneemann@b1-systems.de ReportedBy: michael.friedrich@gmail.com QAContact: opensuse-communityscreening@forge.provo.novell.com CC: nix@opensuse.org Found By: --- Blocker: --- The nagios-plugins.org website has been compromised and the Nagios Plugins Development Team was required to move to a new host at https://www.monitoring-plugins.org whilst renaming their project to Monitoring Plugins. Full the story here: https://www.monitoring-plugins.org/archive/help/2014-January/006503.html I do not suggest to rename the package unless there's the requirement to do so, but update the project url and any (internal) references to source urls in order to stay safe. Kind regards, Michael -- 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#c1
Lars Vogdt
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c
Lars Vogdt
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c2
--- Comment #2 from Michael Friedrich
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c3
--- Comment #3 from Lars Vogdt
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. 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). 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. 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. -- 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
(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#c5
--- Comment #5 from Lars Vogdt
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c6
--- Comment #6 from Lars Vogdt
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#c7
--- Comment #7 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c8
--- Comment #8 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c9
--- Comment #9 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=859105
https://bugzilla.novell.com/show_bug.cgi?id=859105#c10
Lars Vogdt
participants (1)
-
bugzilla_noreply@novell.com