How to remove a *sub*package at end of life ?
mschwendt at gmail.com
Mon Jun 10 13:04:47 UTC 2013
On Mon, 10 Jun 2013 14:55:33 +0200, Remi Collet wrote:
> Le 10/06/2013 14:46, Jiri Popelka a écrit :
> > Hi all,
> > up to F18 we've been shipping cups-php (PHP module) subpackage, but it's
> > not been required by any other package.
> > CUPS upstream dropped this module with cups-1.6 (since F19) so there's
> > been no cups-php anymore in F19.
> > This breaks F18 -> F19 updates when cups-php has been installed
> > (https://bugzilla.redhat.com/show_bug.cgi?id=971741).
> > What's the correct procedure here ?
> > Let user solve this by removing cups-php prior to update ?
> > - the yum error could be a puzzle for some users
> > Put Obsoletes cups-php; Provides cups-php into some other package ?
> > - update is ok, but user is unaware that the php module has gone
> > Some ideal solution which doesn't break update and notifies user that
> > CUPS PHP module no longer exists ?
> >From :
> "Make sure the package is properly Obsoleted/Provided
> by something if it is being replaced".
> If it is not being replaced, Obsoleted/Provided obviously don't apply.
> If some package "Provides: cups-php", imagine the nightmare for
> yum install cups-php
> And this will also avoid the "wanted" broken dep (if another package
> "really" need cups-php)
Typically, one adds only the Obsoletes tag with a maximum version, so the
obsolete package may return with a higher version.
| If a package supersedes/replaces an existing package without being
| a compatible enough replacement as defined in above, use only the
| Obsoletes from above.
Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.4-301.fc19.x86_64
loadavg: 0.09 0.15 0.13
More information about the devel