Your message dated Wed, 3 Mar 2021 19:34:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#984151: gnome-builder: ftbfs with GCC-11
has caused the Debian Bug report #984151,
regarding gnome-builder: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
984151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984151
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:gnome-builder
Version: 3.38.1-1
Severity: normal
Tags: sid bookworm
User: [email protected]
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gnome-builder_3.38.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
Ign:8 http://people.debian.org/~doko/gcc/gcc11 ./ Packages
Ign:8 http://people.debian.org/~doko/gcc/gcc11 ./ Packages
Ign:8 http://people.debian.org/~doko/gcc/gcc11 ./ Packages
Hit:8 http://people.debian.org/~doko/gcc/gcc11 ./ Packages
Fetched 300 kB in 3s (112 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
libzstd1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 319 kB of archives.
After this operation, 21.5 kB disk space will be freed.
Get:1 http://127.0.0.1:12990/debian sid/main amd64 libzstd1 amd64
1.4.8+dfsg-2.1 [319 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 319 kB in 0s (4418 kB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13755 files and directories currently installed.)
Preparing to unpack .../libzstd1_1.4.8+dfsg-2.1_amd64.deb ...
Unpacking libzstd1:amd64 (1.4.8+dfsg-2.1) over (1.4.8+dfsg-2) ...
Setting up libzstd1:amd64 (1.4.8+dfsg-2.1) ...
Processing triggers for libc-bin (2.31-9) ...
+------------------------------------------------------------------------------+
| Fetch source files |
+------------------------------------------------------------------------------+
Check APT
---------
Checking available source versions...
E: apt-cache returned no information about gnome-builder source
E: Are there any deb-src lines in your /etc/apt/sources.list?
+------------------------------------------------------------------------------+
| Cleanup |
+------------------------------------------------------------------------------+
Purging /build/gnome-builder-RhOxXA
Not cleaning session: cloned chroot in use
E: Failed to fetch source files
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: amd64
Build Type: binary
Build-Space: n/a
Build-Time: 0
Distribution: unstable
Fail-Stage: fetch-src
Host Architecture: amd64
Install-Time: 0
Job: gnome-builder_3.38.1-1
Machine Architecture: amd64
Package: gnome-builder
Package-Time: 0
Source-Version: 3.38.1-1
Space: n/a
Status: given-back
Version: 3.38.1-1
--------------------------------------------------------------------------------
Finished at 2021-03-01T20:45:02Z
Build needed 00:00:00, no disk space
E: Failed to fetch source files
DC-Status: Failed 59.294937267s
DC-Time-Estimation: 59.294937267 versus expected 294 (r/m: 3.958264795460417 ;
m: 59.294937267)
--- End Message ---
--- Begin Message ---
On 3/3/21 7:28 PM, Simon McVittie wrote:
> On Wed, 03 Mar 2021 at 16:12:48 +0000, Matthias Klose wrote:
>> The package fails to build in a test rebuild on at least amd64 with
>> gcc-11/g++-11, but succeeds to build with gcc-10/g++-10.
> ...
>> Checking available source versions...
>> E: apt-cache returned no information about gnome-builder source
>> E: Are there any deb-src lines in your /etc/apt/sources.list?
>
> This doesn't look like either gnome-builder's fault or gcc-11's fault.
closing. No, I can't retry packages for these archive test rebuilds.
--- End Message ---
