Bug 1067063 - mrepo unable to determine version createrepo
Summary: mrepo unable to determine version createrepo
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mrepo
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jessica Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-19 15:22 UTC by Romke van Dijk
Modified: 2020-11-30 15:00 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:00:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
changes the version checking logic for createrepo (1.14 KB, patch)
2014-02-19 15:22 UTC, Romke van Dijk
no flags Details | Diff

Description Romke van Dijk 2014-02-19 15:22:43 UTC
Created attachment 865115 [details]
changes the version checking logic for createrepo

Description of problem:
When running mrepo, I keep getting a warning that mrepo can not determine the version of createrepo. This causes some problems with the groupfile.

Version-Release number of selected component (if applicable):
mrepo.noarch                    0.8.7-2.el6

How reproducible:
Every time

Steps to Reproduce:
1. Run any mrepo command for example: /usr/bin/mrepo -vvvgu epel-x86_64


Actual results:
mrepo: epel-x86_64: Version of createrepo could not be found. Assuming newer than 0.4.6.

Expected results:
Not print the message

Additional info:
Line 816 to 821 causes this problem, if you dry run this code you get the following output:
AttributeError: 'module' object has no attribute '__version__'

The latest revision of mrepo has a different approce in determining the version:
     try:
            try:
                import createrepo
                createrepo_version = createrepo.__version__
                del createrepo
            except ImportError:
                import genpkgmetadata
                createrepo_version = genpkgmetadata.__version__
                del genpkgmetadata

This method fixes the problem. I attached a patch implementing this fix.

Comment 1 Ben Cotton 2020-11-05 16:51:29 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 2 Ben Cotton 2020-11-05 16:54:12 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-30 15:00:26 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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