Bug 1006556 - Dubious Obsoletes
Summary: Dubious Obsoletes
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libircclient-qt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kaluža
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 846913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 19:53 UTC by Michael Schwendt
Modified: 2013-09-11 07:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-11 07:20:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Schwendt 2013-09-10 19:53:11 UTC
What is going on here? The renamed package is still in the collection and has been rebuilt even! Have you only forgotten to retire the package? Then please do so and fix the Obsoletes, too:
http://fedoraproject.org/wiki/Package_Renaming_Process

> bug 846913
> libircclient-qt is renamed to communi.
> This is a re-review request for a package rename.


libircclient-qt < 0:0.5.0-5  obsoleted by  libcommuni-0:2.2.0-1.fc20.i686

    libircclient-qt-0:0.5.0-8.fc20.i686  isn't obsoleted
    libircclient-qt-0:0.5.0-7.fc19.i686  isn't obsoleted
    libircclient-qt-0:0.5.0-6.fc18.i686  isn't obsoleted
    libircclient-qt-0:0.5.0-5.fc17.i686  isn't obsoleted
    libircclient-qt-0:0.5.0-4.fc17.i686  is oldest

libircclient-qt-devel < 0:0.5.0-5  obsoleted by  communi-0:1.2.1-2.fc19.i686
libircclient-qt-devel < 0:0.5.0-5  obsoleted by  libcommuni-devel-0:2.2.0-1.fc20.i686

    libircclient-qt-devel-0:0.5.0-8.fc20.i686  isn't obsoleted
    libircclient-qt-devel-0:0.5.0-7.fc19.i686  isn't obsoleted
    libircclient-qt-devel-0:0.5.0-6.fc18.i686  isn't obsoleted
    libircclient-qt-devel-0:0.5.0-5.fc17.i686  isn't obsoleted
    libircclient-qt-devel-0:0.5.0-4.fc17.i686  is oldest

Comment 1 Jan Kaluža 2013-09-11 07:20:59 UTC
I have retired libircclient-qt in rawhide and fixed the obsoletes in communi, but better check it. I think I did it right this time. For now I'm closing this bug, reopen if needed.


Note You need to log in before you can comment on or make changes to this bug.