Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1811087 - python-shortuuid fails to build: /usr/lib/python3.?/site-packages/shortuuid-1.0.0* not there
Summary: python-shortuuid fails to build: /usr/lib/python3.?/site-packages/shortuuid-1...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-shortuuid
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-03-06 15:01 UTC by Miro Hrončok
Modified: 2020-03-07 11:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-07 11:22:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2020-03-06 15:01:03 UTC 
python-shortuuid fails to build. This happens with Python 3.9.0a4, but also in regular rawhide.

RPM build errors:
    File not found: /builddir/build/BUILDROOT/python-shortuuid-1.0.0-1.fc33.x86_64/usr/lib/python3.9/site-packages/shortuuid-1.0.0*

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01291298-python-shortuuid/

For all our attempts to build python-shortuuid with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/python-shortuuid/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Comment 1 Miro Hrončok 2020-03-06 15:04:25 UTC 
As a side note:

> disable tests, no idea where pep8 went

pep8 went to die:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EC664CMAJKWYII6MDFGVMZOD3D6IJXGI/
https://bugzilla.redhat.com/show_bug.cgi?id=1667200

It was later orphaned and retired when nobody picked it up:

https://bugzilla.redhat.com/show_bug.cgi?id=1667200#c12
https://src.fedoraproject.org/rpms/python-pep8/c/fbde72d6fe032dccb7a6714fd23c3b0954a82414?branch=master
Comment 2 Peter Robinson 2020-03-06 15:28:03 UTC 
(In reply to Miro Hrončok from comment #0)
> python-shortuuid fails to build. This happens with Python 3.9.0a4, but also
> in regular rawhide.

I literally pushed a build and went to lunch, you never even gave me time to investigate, would you seriously stop reporting bugs the moment a single bloody failure happens!?!
Comment 3 Miro Hrončok 2020-03-06 16:02:05 UTC 
Maintainers do push broken updates and they don't even notice. We rebuild all Python packages with 3.9 as they are pushed and report failures as they are found.

To change the question, could you please stop pushing broken stuff and check if it build beforehand? I've noticed this is not the first time this happened. Note that the stuff you push affects other maintainers and other people.

Thank you.
Comment 4 Peter Robinson 2020-03-06 16:53:15 UTC 
I don't tell you how to run your process.

Was already working with upstream to deal with this.

https://github.com/skorokithakis/shortuuid/issues/46
Comment 5 Miro Hrončok 2020-03-06 17:03:20 UTC 
You literally told me how to run my process in the previous comment.

Could you please leave this report open as long as it fails to build, so we know it is taken care of and not a new failure?

Thanks.
Comment 6 Peter Robinson 2020-03-06 17:08:44 UTC 
> Could you please leave this report open as long as it fails to build, so we
> know it is taken care of and not a new failure?

While we're making suggestions could you maybe add a 24hr delay to give people a reasonable window to fix something before spamming them?
Note You need to log in before you can comment on or make changes to this bug.