[Yum] How does yum consider a package "unique"?

Satoshi Yagi marseille07 at hotmail.com
Tue Jul 28 03:03:55 UTC 2015

It's kinda hard to describe, but my Fedora22 system at home has:


I didn't force the installation of these packages, but these co-exist just fine because (I presume) <name>.<arch> pair is different.

I understand that pkgid (checksum) of the package is unique, but that's unique for pretty much anything, yet yum understands to "upgrade" certain packages instead of installing side-by-side.

That was the gist of my question.  If it isn't <name>.<arch>, I'd like to know what it is.


> To: yum at lists.baseurl.org
> From: james-yum at and.org
> Date: Mon, 27 Jul 2015 10:57:33 -0400
> Subject: Re: [Yum] How does yum consider a package "unique"?
> Satoshi Yagi <marseille07 at hotmail.com> writes:
> > Hi,
> >
> > Looking at the explanation on filelists.xml.gz on this site http://www.slashroot.in/yum-repository-and-package-management-complete-tutorial,
> >
> > <package pkgid="deee52b24486906ee52576ee471b57061ccd5544" name="php-mbstring" arch="i386">
> >
> > My gut feeling is that yum uses name.arch combination to uniquely identify a package.  Could anyone confirm if this is correct?
>  It depends what you mean by "unique", but it's never just n.a.
>  In the above xml fragment, pkgid would be the most unique thing as
> that's the checksum of the package file (that's not completely unique
> though because you can have the same package file in two different
> repos.).
> -- 
> James Antill -- james at and.org
> _______________________________________________
> Yum mailing list
> Yum at lists.baseurl.org
> http://lists.baseurl.org/mailman/listinfo/yum
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.baseurl.org/pipermail/yum/attachments/20150727/4a4034f3/attachment.html>

More information about the Yum mailing list