Processing commands for cont...@bugs.debian.org:
> reassign 950747 libgphobos76 9-20190103-1
Bug #950747 [projectl] projectl: Projectl fails to run with current libgphobos76
Bug reassigned from package 'projectl' to 'libgphobos76'.
No longer marked as found in versions projectl/1.001.dfsg1-9.
Igno
Processing commands for cont...@bugs.debian.org:
> notfound 950550 10-20200204-1
Bug #950550 {Done: Matthias Klose } [libgcc1] libgcc1: upgrade
from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc
There is no source info for the package 'libgcc1' at version '10-20200204-1'
with architecture ''
LAST_UPDATED: Obtained from SVN: tags/gcc_9_2_0_release revision 274275
Native configuration is arm-unknown-linux-gnueabi
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes44
# of unsupported tests 5
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is s390x-ibm-linux-gnu
=== g++ tests ===
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is powerpc64le-unknown-linux-gnu
=== g++ t
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is i686-pc-linux-gnu
=== brig tests ===
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
Native configuration is arm-unknown-linux-gnueabihf
=== libatomic tests ===
Running target unix
=== libatomic Summary for unix ===
# of expected passes44
# of unsupported tests
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
Native configuration is arm-unknown-linux-gnueabi
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes44
# of unsupported tests 5
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is x86_64-pc-linux-gnu
=== brig tests ===
LAST_UPDATED: Obtained from SVN: tags/gcc_8_3_0_release revision 269117
Native configuration is arm-unknown-linux-gnueabi
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes44
# of unsupported tests 5
Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Upgrading libgcc1 to version >= 10 on a system breaks gcc-7, gcc-8 and
gcc-9 when using the gold linker, as gcc passes the wrong path to the
libgcc_s.so.1 library. All architectures are affected, example on amd64,
starting from a bullseye
Version: 10-20200204-1
On 2/5/20 9:55 AM, Aurelien Jarno wrote:
>>* Add breaks on libgcc-N-dev packages on arm64, s390x and sparc64.
>> Closes: #950550, #950579.
>
> This is not enough. All architectures are affected when using gold.
this bug doesn't have anything to do with gold. Closi
Your message dated Wed, 5 Feb 2020 11:07:33 +0100
with message-id <74404b38-7b56-84bd-3a4d-2dfb1ca8a...@debian.org>
and subject line Re: Bug#950550: libgcc1: upgrade from 1:9.2.1-25 to libgcc1
1:10-20200202-1 breaks gcc
has caused the Debian Bug report #950550,
regarding libgcc1: upgrade from 1:9.
Processing control commands:
> reopen -1
Bug #950550 {Done: Debian FTP Masters }
[libgcc1] libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add
control: reopen -1
control: severity -1 serious
control: found -1 gcc-10/10-20200202-1
control: found -1 gcc-10/10-20200204-1
On 2020-02-04 15:19, Debian FTP Masters wrote:
> Source: gcc-10
> Source-Version: 10-20200204-1
>
> We believe that the bug you reported is fixed in the latest version of
15 matches
Mail list logo
