Bug 1395861

Summary: Enable MPG123 plugin
Product: [Fedora] Fedora Reporter: Yaakov Selkowitz <yselkowi>
Component: qmmp-plugin-packAssignee: Karel Volný <kvolny>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: kvolny, yselkowi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-24 14:49:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1394147    
Bug Blocks:    
Attachments:
Description Flags
Patch for rawhide none

Description Yaakov Selkowitz 2016-11-16 20:47:17 UTC
mpg123 has been moved into Fedora proper, which allows enabling the corresponding plugin in qmmp-plugin-pack and obsoletion of the -freeworld package from elsewhere.

Patch forthcoming.

Comment 1 Yaakov Selkowitz 2016-11-16 20:53:24 UTC
Created attachment 1221378 [details]
Patch for rawhide

Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=16479221

Comment 2 Karel Volný 2016-11-21 09:13:52 UTC
thanks for the heads-up

a few notes/questions:

- I'd add that in Rawhide, not as an update for older releases, so I find the version `if` superfluous

- I don't think it is necessary to add provides (nothing depends on it, does it?)

also, there's non zero chance that there may be some other restricted plugin in the future so the provides would cause a conflict if the other package gets revived

- OTOH, adding obsoletes for the old version is probably a good idea so that dnf knows what to do on system upgrade

sounds sane?

p.s. I have quite some backlog after holidays, don't expect me to react quickly - but feel free to ping me if it takes too long (> week)

Comment 3 Yaakov Selkowitz 2016-11-21 17:01:28 UTC
(In reply to Karel Volný from comment #2)
> - I'd add that in Rawhide, not as an update for older releases, so I find
> the version `if` superfluous

I recommend this for F25 as well, as mpg123 is already included therein and therefore there is no further reason for external repositories to continue to carry it.  Otherwise, the %if does make it easier to import this version update into F24 cleanly.
 
> - I don't think it is necessary to add provides (nothing depends on it, does
> it?)

It's part of providing a smooth upgrade path, following the similar change to audacious-plugins:

http://pkgs.fedoraproject.org/cgit/rpms/audacious-plugins.git/commit/?id=b582d9323b26ef5e42381add25251fcbb9c2a2dd

> also, there's non zero chance that there may be some other restricted plugin
> in the future so the provides would cause a conflict if the other package
> gets revived

That would have a newer version/release, which is why the Obsoletes and Provides should be (as they are here) versioned.

Comment 4 Karel Volný 2016-11-24 14:02:43 UTC
(In reply to Yaakov Selkowitz from comment #3)
> (In reply to Karel Volný from comment #2)
> > - I'd add that in Rawhide, not as an update for older releases, so I find
> > the version `if` superfluous
> 
> I recommend this for F25 as well, as mpg123 is already included therein and
> therefore there is no further reason for external repositories to continue
> to carry it.

this was discussed on that other repo's mailinglist - as it didn't make it into GA, it cannot be dropped from F25 ...

> Otherwise, the %if does make it easier to import this version
> update into F24 cleanly.

... of course, the update can depend on another update, but I find it unnecessary to make update just for this packaging change ... and if an update for F24/F25 will be released, we're already far past the branching points, so why to put into rawhide code that will never be used when I can adjust just the branches

> > - I don't think it is necessary to add provides (nothing depends on it, does
> > it?)
> 
> It's part of providing a smooth upgrade path, following the similar change
> to audacious-plugins:

hm, we even have a guideline for that:

https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages

I've discussed this with DNF contributor and he said that it would be better to use fixed versions in this case