Results 1 to 4 of 4

Thread: createrepo 0.9.9-10.1.2 broken in 13.1?

  1. #1

    Default createrepo 0.9.9-10.1.2 broken in 13.1?

    Hey folks,

    Tried installing the createrepo package with a stock 13.1 install, and receive the following error. Looks like there's a dependency on an older version of a python module that's since been renamed. Any suggestions for a quick fix?

    Problem: createrepo-0.9.9-10.1.2.x86_64 requires yum-metadata-parser, but this requirement cannot be provided
    uninstallable providers: yum-metadata-parser-1.1.2-126.1.3.x86_64[openSUSE-13.1-1.10]
    yum-metadata-parser-1.1.2-126.1.3.i586[repo-oss]
    yum-metadata-parser-1.1.2-126.1.3.x86_64[repo-oss]

    Breaking the dep, then generates the following error...

    createrepo /tmp
    Traceback (most recent call last):
    File "/usr/share/createrepo/genpkgmetadata.py", line 28, in <module>
    import createrepo
    File "/usr/lib64/python2.7/site-packages/createrepo/__init__.py", line 21, in <module>
    import yumbased
    File "/usr/lib64/python2.7/site-packages/createrepo/yumbased.py", line 19, in <module>
    import rpm

  2. #2

    Default Re: createrepo 0.9.9-10.1.2 broken in 13.1?

    On 01/31/2014 01:46 PM, ariens pecked at the keyboard and wrote:
    > Hey folks,
    >
    > Tried installing the createrepo package with a stock 13.1 install, and
    >


    Exactly HOW were you trying to install it? By compiling or from a stock
    repo?

    Ken

  3. #3

    Arrow Re: createrepo 0.9.9-10.1.2 broken in 13.1?

    # zypper in createrepo

    By stock 13.1, I meant that it's a VM image that contains only a base install plus networking, and a little SSHD config. All the default software repositories are available to zypper.

    I've got a feeling I've stumbled upon a major n00b trap... I've came across this error several times whilst installing several other packages as well (again--using zypper). php5-fpm, for one is also failing with a similar error about it needing a named packager/provider that cannot be provided. In that case php5-fpm requires smtp_daemon but it conflits with patterns-openSUSE-minimal_base-conflicts-13.1-13.6.1.x86_64

    Does the patterns-openSUSE-minimal_base-conflicts package prevent named providers from being installed? Perhaps to ensure forwards compatibility of requirements and dependencies?

    I've uninstalled the patterns-openSUSE-minimal_base-conflicts package, and everything's working as expected.

  4. #4

    Default Re: createrepo 0.9.9-10.1.2 broken in 13.1?

    On 01/31/2014 05:26 PM, ariens pecked at the keyboard and wrote:
    > # zypper in createrepo
    >
    > By stock 13.1, I meant that it's a VM image that contains only a base
    > install plus networking, and a little SSHD config. All the default
    > software repositories are available to zypper.
    >
    > I've got a feeling I've stumbled upon a major n00b trap... I've came
    > across this error several times whilst installing several other packages
    > as well (again--using zypper). php5-fpm, for one is also failing with a
    > similar error about it needing a named packager/provider that cannot be
    > provided. In that case php5-fpm requires smtp_daemon but it conflits
    > with patterns-openSUSE-minimal_base-conflicts-13.1-13.6.1.x86_64
    >
    > Does the patterns-openSUSE-minimal_base-conflicts package prevent named
    > providers from being installed? Perhaps to ensure forwards
    > compatibility of requirements and dependencies?
    >
    > I've uninstalled the patterns-openSUSE-minimal_base-conflicts package,
    > and everything's working as expected.
    >
    >


    You need to install the deps as well. When you choose to "break" the dep
    you will end up with problems. You are always better off finding out why
    there is a problem in the first place. Always make sure you have the
    four basic repos enabled.

    They are OSS, non-OSS and both update repos.

    I'm not sure what effect un-installing the minimal-base pattern does.

    Ken

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •