Skip to content

devpi upload uwsgi does not contain PKGINFO, skipping #524

Closed
Closed
devpi upload uwsgi does not contain PKGINFO, skipping#524

Description

@soliangxin
soliangxin
opened on Mar 22, 2018

An error occurred while using the command to upload the package downloaded by pypi official website

devpi upload --from-dir requirements
uwsgi-2.0.12.tar.gz: does not contain PKGINFO, skipping
uwsgi-2.0.13.1.tar.gz: does not contain PKGINFO, skipping

Ask how to solve this problem?

Activity

  1. RonnyPfannschmidt commented on Mar 22, 2018

    @RonnyPfannschmidt
    RonnyPfannschmidt
    on Mar 22, 2018
    Contributor

    it seems that those releases of uwsgi deliberately/accidentally left out the pkg-info - its included in the most recent ones - please evaluate if updating is a option for you

  2. soliangxin commented on Mar 22, 2018

    @soliangxin
    soliangxin
    on Mar 22, 2018
    Author

    Hello, this is the version I specified when installing third-party open source software. Is there a solution to this problem?

  3. fschulze commented on Mar 22, 2018

    @fschulze
    fschulze
    on Mar 22, 2018
    Contributor

    You can push from root/pypi to one of your indexes, no need to reupload:

    devpi push --index root/pypi uwsgi==2.0.12 your/index

  4. soliangxin commented on Mar 23, 2018

    @soliangxin
    soliangxin
    on Mar 23, 2018
    Author

    Hello, the built devpi server is not connected to the external network in the company's internal network. What should be done in this situation?

  5. fschulze commented on Mar 23, 2018

    @fschulze
    fschulze
    on Mar 23, 2018
    Contributor

    The only workaround I can think of at the moment is unpacking the source and upload from that

  6. petrovicboban commented on Apr 4, 2018

    @petrovicboban
    petrovicboban
    on Apr 4, 2018

    We had similar issue running devpi upload after python setup.py bdist_wheel. There was an error:

    package_name-cp27-cp27mu-linux_x86_64.whl: does not contain PKGINFO, skipping

    It's possibly related to change in metadata version:

    Metadata-Version: 2.1

    We've updated some packages, and it's fine:

    devpi-client==4.0.1
devpi-common==3.2.1
virtualenv==15.2.0

  7. jaraco commented on Apr 4, 2018

    @jaraco
    jaraco
    on Apr 4, 2018
    Contributor

    I encountered this issue when making Linux wheel of Pillow right after successfully making a macOS wheel of the same source dist.

  8. fschulze commented on Apr 5, 2018

    @fschulze
    fschulze
    on Apr 5, 2018
    Contributor

    I wonder what is happening here. Either there is a bug in distutils, or twine is doing something different than devpi upload. The latter would explain how such wheels ended up on PyPI at all.

  9. di commented on Apr 5, 2018

    @di
    di
    on Apr 5, 2018

    This is likely because the affected users have pkginfo<1.4.2, which cannot parse a Metadata 2.1 PKG-INFO file.

    The devpi client should pin pkginfo>=1.4.2 (currently it's pkginfo>=1.2b1).

    Anyone experiencing this problem should be able to resolve it by doing pip install -U pkginfo.

  10. henryborchers commented on Apr 9, 2018

    @henryborchers
    henryborchers
    on Apr 9, 2018

    Tried this and this fixed the problem for me.

  11. jaraco commented on Apr 10, 2018

    @jaraco
    jaraco
    on Apr 10, 2018
    Contributor

    Confirmed - I have pkginfo 1.4.1.

  12. fschulze
    closed this as completedin #527on Apr 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions