Your message dated Thu, 13 Feb 2020 02:00:21 -0500
with message-id <[email protected]>
and subject line Re: gcc-10: FTBFS due to missing parens in versioned break
has caused the Debian Bug report #951085,
regarding gcc-10: FTBFS due to missing parens in versioned break
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.)
--
951085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951085
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gcc-10
Version: 10-20200210-1
Severity: serious
gcc-10 is failing to build with the following error:
dpkg-gencontrol: error: error occurred while parsing Breaks field:
cryptsetup-initramfs << 2:2.2.2-3~,
dh_gencontrol: error: dpkg-gencontrol -plibgcc-s1 -ldebian/changelog
-Tdebian/libgcc-s1.substvars -Pdebian/.debhelper/libgcc-s1/dbgsym-root
-v10-20200210-1 -Vlibgcc:Version=10-20200210-1
-Vgcc:Version=10-20200210-1 -Vgcc:EpochVersion=1:10-20200210-1
-Vgcc:SoftVersion=10 -Vgdc:Version=10-20200210-1
-Vgm2:Version=10-20200210-1 -Vgnat:Version=10-20200210-1
-Vgnat:SoftVersion=10 -Vbinutils:Version=2.34 "-Vdep:libgcc=libgcc-s1
(>= \${gcc:Version})" "-Vdep:libgccdev=libgcc-10-dev (=
\${gcc:Version})" -Vdep:libgccbiarch= -Vdep:libgccbiarchdev=
"-Vdep:libc=libc6 (>= 2.11)" "-Vdep:libcdev=libc6-dev (>= 2.13-5)"
-Vdep:libcbiarch= -Vdep:libcbiarchdev= -Vdep:libunwinddev=
-Vdep:libcxxbiarchdev= -Vdep:libcxxbiarchdbg= -Vdep:libgnat=
"-Vbase:Breaks=gnat (<< 7)" "-Vlibgcc:Breaks=cryptsetup-initramfs <<
2:2.2.2-3~, " "-Vdep:gold=binutils-gold (>= 2.34)"
"-Vdep:libgomp=libgomp1 (>= \${gcc:Version})" "-Vdep:libitm=libitm1 (>=
\${gcc:Version})" "-Vdep:libatomic=libatomic1 (>= \${gcc:Version})"
"-Vdep:libasan=libasan6 (>= \${gcc:Version})" "-Vdep:liblsan=liblsan0
(>= \${gcc:Version})" "-Vdep:libtsan=libtsan0 (>= \${gcc:Version})"
"-Vdep:libubsan=libubsan1 (>= \${gcc:Version})"
"-Vdep:libqmath=libquadmath0 (>= \${gcc:Version})" -Vdep:libx32z=
"-Vdep:libcc1=libcc1-0 (>= \${gcc:Version})"
"-Vmultiarch:breaks=gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5
(<< 4.5.3-2)" "-Vgolang:Conflicts=golang-go (<< 2:1.3.3-1ubuntu2)"
-Vfortran:mod-version=gfortran-mod-15 -UPre-Depends -URecommends
-USuggests -UEnhances -UProvides -UEssential -UConflicts
-DPriority=optional -UHomepage -UImportant -UBuilt-Using
-DAuto-Built-Package=debug-symbols -DPackage=libgcc-s1-dbgsym
"-DDepends=libgcc-s1 (= \${binary:Version})" "-DDescription=debug
symbols for libgcc-s1"
-DBuild-Ids=b8c5e334209666a8039479266ddbf6322ef1d78b -DSection=debug
"-DReplaces=libgcc-s1-dbg (<< 9.2.1-21)" "-DBreaks=libgcc-s1-dbg (<<
9.2.1-21)" returned exit code 25
Full build log is at
<https://buildd.debian.org/status/fetch.php?pkg=gcc-10&arch=ppc64el&ver=10-20200210-1&stamp=1581374256&raw=0>
The issue appears to be in debian/rules.conf:
LIBGCC_BREAKS += cryptsetup-initramfs << 2:2.2.2-3~,
That versioned break needs parenthesis:
LIBGCC_BREAKS += cryptsetup-initramfs (<< 2:2.2.2-3~),
Thanks,
Andres
--- End Message ---
--- Begin Message ---
This bug was fixed in the 10-20200211-1 upload; closing.
--- End Message ---
