https://bugzilla.novell.com/show_bug.cgi?id=859105 https://bugzilla.novell.com/show_bug.cgi?id=859105#c3 --- Comment #3 from Lars Vogdt <lrupp@suse.com> 2014-01-19 03:03:46 CET --- (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. 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.