Hello, Well, for the last 2 years you wouldn't have '/usr/bin/par' though due to the 'par' package actually putting in '/usr/bin/par2*' binaries. This was added for the case where: - You have current 'par' package installed (providing /usr/bin/par2* binaries) - You update and you actually now need the 'par2cmdline' package (providing /usr/bin/par2* binaries) If you're script was actually calling out to /usr/bin/par for the last few years, it wouldn't have existed on your system due to the package containing the 'par2cmdline' sources. Does this make sense, or do I misunderstand? Shall I go about this a different way? Thanks, Doug On Wed, May 22, 2019 at 3:16 PM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Wed, 2019-05-22 at 14:53 +0000, Doug Miller wrote:
- For the 'par' package: I believe the correct course of action is to revert to using the http://parchive.sourceforge.net/ source and generating the /usr/bin/par binary. Currently this version should be 1.1.
- For the 'par2cmdline' package: A new package called 'par2cmdline' should be built using the https://github.com/Parchive/par2cmdline source and generating the /usr/bin/par2* binaries. Currently this version should be 0.8.0.
In doing so, to make the transition easy if any packages are currently depending on the 'par' package, I've added "Provides: par = 0.8.0" and "Obsoletes: par < 0.8.0" to the 'par2cmdline' package.
This at least seems incorrect. If I have a script that calls out to /usr/bin/par, and I require par, then par2cmdline can't serve as a drop-in replacement (as it provides /usr/bin/par2*, but not /usr/bin/par)
Hence, provides/obsoletes seems incorrect here.
Cheers Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org