Bug 480661 - Yum can't update the packaging pattern resulting from FPC renames
Yum can't update the packaging pattern resulting from FPC renames
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-19 13:23 EST by Nicolas Mailhot
Modified: 2014-01-21 18:07 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-19 15:36:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nicolas Mailhot 2009-01-19 13:23:05 EST
Multi-font packages have the following packagin pattern:

subpackages A B C depend on exact version-release of common subpackage

Last week FPC made us change the name of A B C subpackages. They're now a b c (with a obsoleting A, b obsoleting B, etc and common unchanged)

It seems however that yum is unable to update from old font packagesets to the new ones. I complains common=old version is required by one of the old subpackages

Examples:
* smc-fonts
  old: http://koji.fedoraproject.org/koji/buildinfo?buildID=77360
  new: http://koji.fedoraproject.org/koji/buildinfo?buildID=78960

* liberation-fonts
  old: http://koji.fedoraproject.org/koji/buildinfo?buildID=77796
  new: http://koji.fedoraproject.org/koji/buildinfo?buildID=79292

* google-droid-fonts
  old: http://nim.fedorapeople.org/fontpackages/
  new: http://koji.fedoraproject.org/koji/buildinfo?buildID=78920

maybe I'm missing something obvious

yum-3.2.21-2.fc11.noarch
Comment 1 Nicolas Mailhot 2009-01-19 13:26:51 EST
google-droid-fonts is a bad example, it's failing for other reasons
Comment 2 seth vidal 2009-01-19 13:52:39 EST
Can you list the complete error output you're seeing when it bails out?
Comment 4 James Antill 2009-01-19 15:13:11 EST
"""There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them."""

 What is the unfinished transaction?

 Also looking at liberation-fonts, why is the meta-package obsoleting the non-metapackages? This also means that there are two packages obsoleting one installed package ... how well we currently handle that (and what we do) is up in the air atm.
Comment 5 James Antill 2009-01-19 15:23:06 EST
Actually liberation is just broken, the main meta pkg has:

%define fontname liberation
Name:             %{fontname}-fonts
Requires:         %{name}-sans >= %{version}-%{release}
Requires:         %{name}-serif >= %{version}-%{release}
Requires:         %{name}-mono >= %{version}-%{release}
Obsoletes:        liberation-fonts-sans < %{version}-%{release}
Obsoletes:        liberation-fonts-serif < %{version}-%{release}
Obsoletes:        liberation-fonts-mono < %{version}-%{release}

%package -n %{fontname}-sans-fonts

...or to expand everything:

Requires:         liberation-fonts-sans >= %{version}-%{release}
[...]
%package -n liberation-sans-fonts

...which is just not going to work.
Comment 6 James Antill 2009-01-19 15:32:01 EST
I can't see anything wrong with smc-* but can you run:

 yum list smc\*
Comment 7 James Antill 2009-01-19 15:36:43 EST
Never mind ... smc has:


%define fontname        smc
Name:           %{fontname}-fonts

Obsoletes: %{name}-dyuthi < 04.1-3

...and on my box:

% yum list smc-fonts-dyuthi
smc-fonts-dyuthi.noarch                 04-6.fc9          fedora                
% rpmdev-vercmp smc-fonts-dyuthi-04-6.fc9 smc-fonts-dyuthi-04.1-3
0:smc-fonts-dyuthi-04-6.fc9 is newer

...three NaB for the price of 1!
Comment 8 Nicolas Mailhot 2009-01-19 15:52:43 EST
(In reply to comment #5)
> Actually liberation is just broken, the main meta pkg has:

Yes, Kaio needs more work, that's why I proposed smc as the better testcase

(In reply to comment #7)
> Never mind ... smc has:
> 
> 
> %define fontname        smc
> Name:           %{fontname}-fonts
> 
> Obsoletes: %{name}-dyuthi < 04.1-3
> 
> ...and on my box:
> 
> % yum list smc-fonts-dyuthi
> smc-fonts-dyuthi.noarch                 04-6.fc9         
> fedora                
> % rpmdev-vercmp smc-fonts-dyuthi-04-6.fc9 smc-fonts-dyuthi-04.1-3
> 0:smc-fonts-dyuthi-04-6.fc9 is newer

Unfortunately on my box it results in

smc-fonts-dyuthi.noarch                  04.1-2.fc11                   installed

rpmdev-vercmp smc-fonts-dyuthi-04.1-2.fc11 smc-fonts-dyuthi-04.1-3
0:smc-fonts-dyuthi-04.1-3 is newer
Comment 9 Nicolas Mailhot 2009-01-19 15:53:45 EST
$ rpm -qa |grep smc|grep fonts
smc-fonts-anjalioldlipi-04.1-2.fc11.noarch
smc-fonts-rachana-04.1-2.fc11.noarch
smc-fonts-raghumalayalam-04.1-2.fc11.noarch
smc-fonts-common-04.1-2.fc11.noarch
smc-fonts-suruma-04.1-2.fc11.noarch
smc-fonts-kalyani-04.1-2.fc11.noarch
smc-fonts-dyuthi-04.1-2.fc11.noarch
smc-fonts-meera-04.1-2.fc11.noarch
Comment 10 Nicolas Mailhot 2009-01-19 16:25:29 EST
Actually, there was another subtle bug in the spec file ⇒ CLOSING

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