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 1734956 - avahi: FTBFS in Fedora rawhide/f31
Summary: avahi: FTBFS in Fedora rawhide/f31
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: avahi
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
 
Reported: 2019-07-31 17:14 UTC by Fedora Release Engineering
Modified: 2019-10-24 14:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-24 14:31:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2019-07-31 17:14 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2019-07-31 17:14 UTC, Fedora Release Engineering
no flags Details
state.log (609 bytes, text/plain)
2019-07-31 17:14 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2019-07-31 17:14:50 UTC
avahi failed to build from source in Fedora rawhide/f31

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix avahi 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,
avahi will be orphaned. Before branching of Fedora 32,
avahi 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-07-31 17:14:54 UTC
Created attachment 1595431 [details]
build.log

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

Comment 2 Fedora Release Engineering 2019-07-31 17:14:56 UTC
Created attachment 1595432 [details]
root.log

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

Comment 3 Fedora Release Engineering 2019-07-31 17:14:57 UTC
Created attachment 1595433 [details]
state.log

Comment 4 Rex Dieter 2019-07-31 21:11:36 UTC
This one's wierd, fails only on i686 with:

RPM build errors:
BUILDSTDERR:     Macro expanded in comment on line 88: %{version}.tar.gz
BUILDSTDERR:     Macro expanded in comment on line 161: %{name}-glib-devel = %{version}-%{release}
BUILDSTDERR:     Macro expanded in comment on line 190: %{name}-glib-devel = %{version}-%{release}
BUILDSTDERR:     line 285: It's not recommended to have unversioned Obsoletes: Obsoletes:        howl-libs
BUILDSTDERR:     line 295: It's not recommended to have unversioned Obsoletes: Obsoletes:        howl-devel
BUILDSTDERR:     Macro expanded in comment on line 607: %{_libdir}/girepository-1.0/Avahi-0.6.typelib
BUILDSTDERR:     Macro expanded in comment on line 608: %{_libdir}/girepository-1.0/AvahiCore-0.6.typelib
BUILDSTDERR:     Macro expanded in comment on line 614: %{_datadir}/gir-1.0/Avahi-0.6.gir
BUILDSTDERR:     Macro expanded in comment on line 615: %{_datadir}/gir-1.0/AvahiCore-0.6.gir
BUILDSTDERR:     File listed twice: /usr/lib/.build-id/4a/5b290ca8144dc49fcb3b7acdbcbcaaefead390
BUILDSTDERR:     File listed twice: /usr/lib/.build-id/cf/be5303c41e3602d139e0147f14489bbfe16aec
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
BUILDSTDERR:     create archive failed: cpio: write failed - Cannot allocate memory
Child return code was: 1
EXCEPTION: [Error()]

Comment 5 Ben Cotton 2019-08-13 17:00:03 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 18:45:15 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:23:32 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 Fedora Release Engineering 2019-09-29 04:24:23 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 9 Fedora Release Engineering 2019-10-06 04:22:38 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 10 Fedora Release Engineering 2019-10-13 04:22: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 11 Fedora Release Engineering 2019-10-20 04:22:35 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
will 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 not successfully rebuilt at least on 30 will be
retired regardless of the status of this bug.

[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 12 Jan Macku 2019-10-24 14:31:28 UTC
Builds for rawhide, f31 and f30 are now passing.

Build rawhide/f32: https://koji.fedoraproject.org/koji/taskinfo?taskID=38525875
Build f31:         https://koji.fedoraproject.org/koji/taskinfo?taskID=38526587
Build f30:         https://koji.fedoraproject.org/koji/taskinfo?taskID=38526912


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