[Yum] rpm.RPMTAG_SOURCERPM vs rpm.RPMTAG_SOURCEPACKAGE

[Ville Skyttä]

On Friday 06 March 2009, Ville Skyttä wrote:
> On Tue, Jan 27, 2009 at 2:26 PM, Panu Matilainen
>
> <pmatilai at laiskiainen.org> wrote:
> > On Mon, 26 Jan 2009, Ville Skyttä wrote:
> >> On Friday 23 January 2009, Panu Matilainen wrote:
> >>> Yup, what was there before was correct (and identical to what rpm
> >>> itself uses) - the existence of RPMTAG_SOURCERPM tag means it's a
> >>> binary, otherwise it's a source.
> >>
> >> I just remembered something that was the cause of a long since resolved
> >> rpmlint bug: RPMTAG_SOURCERPM is also empty for installed gpg-pubkey
> >> packages, so they would fall into the "it's a source" category above.
> >
> > Oh, yuck. Thanks for pointing that out, "fixed" now upstream by adding
> > RPMTAG_SOURCERPM to gpg-pubkeys on import.
>
> I hate to return to this, but the fix-on-import behavior means that
> gpg-pubkeys imported with older versions of rpm aren't affected, and
> continue to cause problems after upgrading to a later rpm version if
> the keys are not re-imported.  The attached patch makes
> pkgTupleFromHeader() take this into account, and fixes the problem for
> me.

Any news about this patch?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Don-t-treat-gpg-pubkeys-imported-with-rpm-4.6.0-as.patch
Type: text/x-patch
Size: 1020 bytes
Desc: not available
URL: <http://lists.baseurl.org/pipermail/yum/attachments/20090329/bf5aaf43/attachment.bin>