Bug 1736553 - python3-pyudev: FTBFS in Fedora rawhide/f31
Summary: python3-pyudev: FTBFS in Fedora rawhide/f31
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python3-pyudev
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: mulhern
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
 
Reported: 2019-08-01 18:53 UTC by Fedora Release Engineering
Modified: 2020-02-07 14:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-07 14:14:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (1.21 KB, text/plain)
2019-08-01 18:53 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2019-08-01 18:53 UTC, Fedora Release Engineering
no flags Details
state.log (487 bytes, text/plain)
2019-08-01 18:53 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2019-08-01 18:53:03 UTC
python3-pyudev failed to build from source in Fedora rawhide/f31

https://koji.fedoraproject.org/koji/taskinfo?taskID=36637320


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix python3-pyudev at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
python3-pyudev will be orphaned. Before branching of Fedora 32,
python3-pyudev will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2019-08-01 18:53:10 UTC
Created attachment 1598914 [details]
build.log

Comment 2 Fedora Release Engineering 2019-08-01 18:53:13 UTC
Created attachment 1598915 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2019-08-01 18:53:19 UTC
Created attachment 1598916 [details]
state.log

Comment 4 mulhern 2019-08-05 13:07:14 UTC
python3-pyudev is EPEL-only, so it shouldn't be expected to build in Fedora.

Comment 5 Ben Cotton 2019-08-13 17:11:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 6 Ben Cotton 2019-08-13 17:58:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 7 Fedora Release Engineering 2019-09-22 04:34:33 UTC
Dear Maintainer,

your package has not been built successfully in 31. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule

Comment 8 mulhern 2019-09-23 12:55:52 UTC
I believe that this should be retired. It is an EPEL only package,
the "real" package is python-pyudev and it is in a fine state.

The only reason to include an EPEL version of python-pyudev,
was to gain some features available in newer versions that
couldn't be found in the older version on RHEL7, called python-pyudev.

But I think that that really doesn't matter now, since nobody
is using this new stuff. Also, the naming is confusing.

I don't see how retiring this could break any dependencies.

Please do retire.

Thanks!

Comment 9 mulhern 2019-09-23 13:05:24 UTC
It turns out I can retire this package myself.

I will retire it this Friday unless I encounter any objections.

Comment 10 mulhern 2020-02-07 14:14:30 UTC
I haven't figured out how to retire, closing.


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