Bug 2341014 - pdfcrack: FTBFS in Fedora rawhide/f42
Summary: pdfcrack: FTBFS in Fedora rawhide/f42
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pdfcrack
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: pjp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F42FTBFS
TreeView+ depends on / blocked
 
Reported: 2025-01-22 21:17 UTC by Fedora Release Engineering
Modified: 2025-12-07 01:26 UTC (History)
1 user (show)

Fixed In Version: pdfcrack-0.21-1.fc43 pdfcrack-0.21-1.fc42
Clone Of:
Environment:
Last Closed: 2025-12-07 00:56:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (17.73 KB, text/plain)
2025-01-22 21:17 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2025-01-22 21:17 UTC, Fedora Release Engineering
no flags Details
state.log (1.63 KB, text/plain)
2025-01-22 21:17 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2025-01-22 21:17:14 UTC
pdfcrack failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix pdfcrack 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,
pdfcrack will be orphaned. Before branching of Fedora 43,
pdfcrack will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2025-01-22 21:17:17 UTC
Created attachment 2071573 [details]
build.log

Comment 2 Fedora Release Engineering 2025-01-22 21:17:18 UTC
Created attachment 2071574 [details]
root.log

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

Comment 3 Fedora Release Engineering 2025-01-22 21:17:20 UTC
Created attachment 2071575 [details]
state.log

Comment 4 Aoife Moloney 2025-02-26 13:41:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 5 Fedora Update System 2025-11-29 08:18:12 UTC
FEDORA-2025-2c54ea04ef (pdfcrack-0.21-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-2c54ea04ef

Comment 6 Fedora Update System 2025-11-29 08:18:13 UTC
FEDORA-2025-2ca134fb7f (pdfcrack-0.21-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-2ca134fb7f

Comment 7 Fedora Update System 2025-11-29 17:32:13 UTC
FEDORA-2025-2c54ea04ef has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2c54ea04ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2c54ea04ef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-11-29 17:51:49 UTC
FEDORA-2025-2ca134fb7f has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2ca134fb7f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2ca134fb7f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-12-07 00:56:51 UTC
FEDORA-2025-2c54ea04ef (pdfcrack-0.21-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-12-07 01:26:24 UTC
FEDORA-2025-2ca134fb7f (pdfcrack-0.21-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


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