RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 593621 - hdr.dsFromHeader() fails with "SystemError" for gpg-pubkeys
Summary: hdr.dsFromHeader() fails with "SystemError" for gpg-pubkeys
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 628883
TreeView+ depends on / blocked
 
Reported: 2010-05-19 10:16 UTC by Panu Matilainen
Modified: 2010-11-10 21:32 UTC (History)
5 users (show)

Fixed In Version: rpm-4.8.0-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 593553
Environment:
Last Closed: 2010-11-10 21:32:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Panu Matilainen 2010-05-19 10:16:07 UTC
+++ This bug was initially created as a clone of Bug #593553 +++

rpm-python-4.8.0-14.fc13.x86_64 on current F-13:

import rpm
for hdr in rpm.TransactionSet().dbMatch("name", "gpg-pubkey"):
    print hdr.dsFromHeader()

Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
SystemError: NULL result without error in PyObject_Call

Slightly different message with rpm-python-4.4.2.3-18.el5 on CentOS 5:

Traceback (most recent call last):
  File "<stdin>", line 2, in ?
SystemError: error return without exception set

rpm-python bug?

This affects rpmlint (DocFilesCheck.py).  I wonder if I could just use hdr.dsOfHeader() instead of hdr.dsFromHeader() there, it doesn't seem to have the same problem (not to mention that even that doesn't have to be done for packages that don't have doc files...)

--- Additional comment from pmatilai on 2010-05-19 02:31:36 EDT ---

Sure it's an rpm-python bug, I'll look into it.

--- Additional comment from pmatilai on 2010-05-19 03:26:34 EDT ---

Fixed upstream now, pulling into Fedora shortly... Looking at rpm 4.4.x code, the actual rpmlint code works on Centos but breaks with the reproducer (its just the print blowing up), right?

hdr.dsOfHeader() and hds.dsFromHeader() are completly different things and can't be used interchangibly. dsOfHeader() returns basically
Provides: %{name} = %{version}-%{release}
whereas dsFromHeader() returns the actual requires/provides/obsoletes/conflicts dependencies.

Comment 3 Panu Matilainen 2010-06-01 09:29:14 UTC
Fixed in rpm-4.8.0-9.el6 now.

Comment 9 releng-rhel@redhat.com 2010-11-10 21:32:13 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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