Bug 1999436 - [F36FTBFS]: bacula fails to build from source in Fedora Rawhide
Summary: [F36FTBFS]: bacula fails to build from source in Fedora Rawhide
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bacula
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1936597 F36FTBFS F37FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-08-31 08:03 UTC by Ondrej Dubaj
Modified: 2022-04-05 15:42 UTC (History)
5 users (show)

Fixed In Version: bacula-11.0.6-2.fc36 bacula-11.0.6-2.fc34 bacula-11.0.6-2.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-05 14:26:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ondrej Dubaj 2021-08-31 08:03:55 UTC
Your package fails to build with the newest autoconf-2.71, which was part of a recent wide Fedora change. More information about Fedora autoconf Change available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test. The easiest way to reproduce the problem is to execute a fedora scratch-build on your package. Thank you for cooperation!

Comment 1 Ben Cotton 2022-02-08 21:41:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Fedora Update System 2022-03-28 05:31:10 UTC
FEDORA-2022-bb8082a146 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb8082a146

Comment 3 Fedora Update System 2022-03-28 05:31:11 UTC
FEDORA-2022-879672892d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-879672892d

Comment 4 Fedora Update System 2022-03-28 05:31:11 UTC
FEDORA-2022-710742d988 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-710742d988

Comment 5 Fedora Update System 2022-03-29 01:22:32 UTC
FEDORA-2022-bb8082a146 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bb8082a146`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb8082a146

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

Comment 6 Fedora Update System 2022-03-29 01:31:37 UTC
FEDORA-2022-710742d988 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-710742d988`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-710742d988

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

Comment 7 Fedora Update System 2022-03-29 01:39:14 UTC
FEDORA-2022-879672892d has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-879672892d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-879672892d

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

Comment 8 Fedora Update System 2022-04-05 14:26:37 UTC
FEDORA-2022-bb8082a146 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-04-05 15:27:30 UTC
FEDORA-2022-879672892d has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-04-05 15:42:53 UTC
FEDORA-2022-710742d988 has been pushed to the Fedora 35 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.