Bug#1078158: marked as done (gcc-doc-defaults: switch to GCC 14)

Your message dated Fri, 27 Sep 2024 08:41:00 + with message-id and subject line Bug#1078158: fixed in gcc-doc-defaults 5:28 has caused the Debian Bug report #1078158, regarding gcc-doc-defaults: switch to GCC 14 to be marked as done. This means that you claim that the problem has been dealt

Bug#1082644: debuginfod-client-config.7: Some remarks and editorial changes for this man page

Package: libdebuginfod-common Version: 0.191-2 Severity: minor Tags: patch * What led up to the situation? Checking for defects with [test-]groff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page" [test-groff is a script in the repository for "groff"] (local copy and "troff" slight

Bug#1082624: gcc-14: Please add sparc64 to gcc-as-needed.diff

Package: gcc-14 Version: 14.2.0-5 Severity: normal Tags: patch X-Debbugs-Cc: debian-sp...@lists.debian.org sparc64 has some spurious library dependencies due to gcc-as-needed.diff currently only adding --as-needed to 32bit-only sparc builds, please append the attached patch to gcc-as-needed.diff

Processed: Re: Bug#1082125: vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$'

Processing control commands: > reassign -1 gcc-14 14.1.0-1 Bug #1082125 [src:vim] vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$' Bug reassigned from package 'src:vim' to 'gcc-14'. No longer marked as found in versions vim/

Re: Bug#1082125: vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$'

Control: reassign -1 gcc-14 14.1.0-1 Control: retitle -1 gcc-14: miscompiles code on s390x at -O2 Control: tag -1 upstream Control: severity -1 normal Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116799 On Wed, Sep 18, 2024 at 02:40:11PM GMT, James McCoy wrote: > On Wed, Sep

Bug#1082168: *-for-host: violates Multi-Arch: same

Source: gcc-defaults Version: 1.219 Tags: patch User: helm...@debian.org Usertags: rebootstrap Hi Matthias, I am sorry for having introduced another problem into the gcc packaging. As it turns out the *-for-host packages are not actually coinstallable at present even though they should be. Attemp

Bug#1078158: RFS: gcc-doc uploads

On Monday, September 16, 2024 1:54:32 PM MST Dmitry Baryshkov wrote: > Ack. I'm currently at the OSS EU & LPC, I will update the repo on > salsa closer to the weekend and ping you afterwards. > Just in case: I was thinking about adding the changes into the new > revision of the package (and then ma

Bug#1078158: RFS: gcc-doc uploads

Soren, On Mon, 16 Sept 2024 at 22:51, Soren Stoutner wrote: > On Monday, September 16, 2024 1:47:14 PM MST Dmitry Baryshkov wrote: > > gcc-14-doc has been uploaded by Bastian German (BTW, Bastian, thank > > you) and is currently waiting for the NEW processing. > > I don't know what are his plans

Bug#1078158: RFS: gcc-doc uploads

Dmitry, On Monday, September 16, 2024 1:47:14 PM MST Dmitry Baryshkov wrote: > gcc-14-doc has been uploaded by Bastian German (BTW, Bastian, thank > you) and is currently waiting for the NEW processing. > I don't know what are his plans for gcc-doc-defaults. OK. If you will push changes to Salsa

Bug#1078158: RFS: gcc-doc uploads

Soren, On Mon, 16 Sept 2024 at 22:38, Soren Stoutner wrote: > > Dmitry, > > Thanks for your quick answers below. > > Piuparts fails because of the following: > > The following packages have unmet dependencies: >cpp-doc : Depends: cpp-14-doc (>= 14.2.0-1~) but it is not installable >gcc-do

Bug#1078158: RFS: gcc-doc uploads

Dmitry, Thanks for your quick answers below. Piuparts fails because of the following: The following packages have unmet dependencies: cpp-doc : Depends: cpp-14-doc (>= 14.2.0-1~) but it is not installable gcc-doc : Depends: gcc-14-doc (>= 14.2.0-1~) but it is not installable gccgo-doc :

Bug#1078158: RFS: gcc-doc uploads

Soren, On Mon, 16 Sept 2024 at 22:27, Soren Stoutner wrote: > > Dmitry, > > debian/source/format lists this package as 3.0 (native). Is Debian the > upstream for this package? Yes, see how gcc-defaults handle the same case. > You should delete the debian/compat file as it is deprecated. > > In

Bug#1078158: RFS: gcc-doc uploads

Dmitry, debian/source/format lists this package as 3.0 (native). Is Debian the upstream for this package? You should delete the debian/compat file as it is deprecated. In debian/control you should build-depend on "debhelper (= 13)". You should add "Rules-Requires-Root: no” to debian/control (

Bug#1078158: RFS: gcc-doc uploads

Soren, On Mon, 16 Sept 2024 at 21:50, Soren Stoutner wrote: > > Dmitry, > > It looks like the Salsa repository does not contain your most recent changes. > When sponsoring packages I like to build from Git. Can you please push them > there? Oops. Pushed gcc-doc-defaults changes. > > On Monday,

Bug#1078158: RFS: gcc-doc uploads

Dmitry, It looks like the Salsa repository does not contain your most recent changes. When sponsoring packages I like to build from Git. Can you please push them there? On Monday, September 16, 2024 12:44:51 PM MST Soren Stoutner wrote: > Control: owner -1 ! > > Dmitry, > > I will take a l

Bug#1078158: RFS: gcc-doc uploads

Control: owner -1 ! Dmitry, I will take a look at sponsoring this. On Thursday, September 12, 2024 3:45:27 AM MST Dmitry Baryshkov wrote: > Hello, > > I'm looking for sponsors for the gcc-doc-defaults ([1]), gcc-13-doc > ([2]), gcc-14-doc ([3]) packages. > > Traditionally these uploads were h

Bug#1081898: src:gcc-11-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build

ation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reprodu

Bug#1081901: src:gcc-13-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build

ation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reprodu

Bug#1081902: src:gcc-14-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build

ation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reprodu

Bug#1081899: src:gcc-12-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build

ation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reprodu

Bug#1081445: downgrading, building sequentially is nice to have, but not a must

Control: severity -1 important Downgrading, building sequentially is nice to have, but not a must. And as you write, your fix just papers over a dependency issue. Please could you address this upstream, if it's really important for you?

Bug#1081448: gcc-14-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory

2024-08-25 23:29:35.0 + @@ -0,0 +1,13 @@ +# DP: Copy (not rename) tools in ADA_TOOLS to fix FTBFS bug in gcc-NN-cross + +--- a/src/gcc/ada/gcc-interface/Make-lang.in b/src/gcc/ada/gcc-interface/Make-lang.in +@@ -808,7 +808,7 @@ ada.all.cross: + for tool in $(ADA_TOOLS) ; do \

Processed: gcc-NN-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory

Processing commands for cont...@bugs.debian.org: > # still an issue in bookworm and trixie > clone 924325 -1 -2 -3 -4 Bug #924325 [src:gcc-8-cross] gcc-8-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory Bug 924325 cloned as bugs 1081445-1081448 > # closin

Bug#1079856: marked as done (creduce: Still depens on clang-format-17)

Your message dated Mon, 09 Sep 2024 17:49:19 + with message-id and subject line Bug#1079856: fixed in creduce 2.11.0~20240909-1 has caused the Debian Bug report #1079856, regarding creduce: Still depens on clang-format-17 to be marked as done. This means that you claim that the problem has

Bug#1081132: Small correction...

Dear Frank B. Brokken, you wrote: > The following source file (e.g., interface.cc) defines the module: > > module Module; > export int value; This must be: export module Module; export int value; -- Frank B. Brokken (+31) 6 5353 2509 PGP Key Fingerprint: DF32 1

Bug#1081132: g++-14: Modules compiled with --std=c++23 can't be used with --std=c++26 and v.v.

Package: g++-14 Version: 14.2.0-3 Severity: normal Dear Maintainer, * What led up to the situation? When trying to import a module in a C++ source file when --std=c++23 was specified when the module was compiled and --std=c++26 is specified when the source file is compiled the compiler shows

Bug#1081000: dwz: Fails with "DWARF CU type DW_UT_type unhandled" when building wpewebkit

On Fri, Sep 06, 2024 at 04:27:11PM +0200, Alberto Garcia wrote: > wpewebkit 2.44.4-1 fails to build in i386 with the following error: And the exact same error in amd64. Berto

Bug#1081000: dwz: Fails with "DWARF CU type DW_UT_type unhandled" when building wpewebkit

h_dwz for this upload, so if you want to reproduce this bug you need to re-enable it. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 6.1.0-23-amd64 (SMP w/128 CPU threads; PREEMPT) Locale: L

Bug#1076612: libquadmath0: wrongly assumes that the storage for __float128 arguments is aligned

-1 > > Severity: serious > > Tags: upstream fixed-upstream > > Control: affects -1 evolver libc6 > > Control: fixed -1 libquadmath0/14-20240429-1 Control: block 1075938 by > > -1 > > ... > > > Closing the bug as it is fixed in unstable. The version tracking

Bug#1076612: libquadmath0: wrongly assumes that the storage for __float128 arguments is aligned

bug as it is fixed in unstable. The version tracking > should do the rest for testing. The fixed version is earlier than the found version, which confused the BTS version tracking. Did you mean it the other way around? In any case, the BTS tells me now that this bug affects unstable and tri

Bug#1073925: marked as done (libstdc++-14-dev: Using multiple import statements generates an internal compiler error)

Your message dated Fri, 30 Aug 2024 19:57:10 +0200 with message-id and subject line Re: Bug#1073925: libstdc++-14-dev: Using multiple import statements generates an internal compiler error has caused the Debian Bug report #1073925, regarding libstdc++-14-dev: Using multiple import statements

Processed: Re: Bug#1073932: libstdc++-14-dev: 'using' specification results in compiler error when specifying -fmodules-ts

Processing control commands: > tags -1 + moreinfo Bug #1073932 [libstdc++-14-dev] libstdc++-14-dev: 'using' specification results in compiler error when specifying -fmodules-ts Added tag(s) moreinfo. -- 1073932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073932 Debian

Bug#1073932: libstdc++-14-dev: 'using' specification results in compiler error when specifying -fmodules-ts

on using the -fmodules-ts flag correctly completes. The following source file (between === lines) was compiled by calling: g++ --std=c++23 -Wall -fmodules-ts -freport-bug -c main.cc === #include #include int mai

Processed: Re: Bug#1073925: libstdc++-14-dev: Using multiple import statements generates an internal compiler error

Processing control commands: > tags -1 + moreinfo Bug #1073925 [libstdc++-14-dev] libstdc++-14-dev: Using multiple import statements generates an internal compiler error Added tag(s) moreinfo. -- 1073925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073925 Debian Bug Tracking Sys

Processed: bug 1077657 is forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 1077657 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116531 Bug #1077657 [g++-14-arm-linux-gnueabihf] g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O Set Bug forwarded-to-address to &#x

Bug#1073925: libstdc++-14-dev: Using multiple import statements generates an internal compiler error

ective (or ineffective)? First the system headers where compiled using the abovementioned commad. Then the compiled headers (like vector.gcm) were made available via the program's gcm.cache subdirectory. The program was compiled using g++ --std=c++23 -Wall -fmodules-ts -freport-bug

Bug#1077763: marked as done (gcc-14: An alignment request might be added before endbr on function entry.)

Your message dated Thu, 29 Aug 2024 10:16:59 +0200 with message-id <37428fa7-9627-4926-8948-0b28d63c7...@debian.org> and subject line fixed in 14.2.0-3 has caused the Debian Bug report #1077763, regarding gcc-14: An alignment request might be added before endbr on function entry. to be mar

Bug#1072245: marked as done (Gcc-14 crash when building with -std=c2x on sid)

Your message dated Thu, 29 Aug 2024 10:14:45 +0200 with message-id and subject line closing, no information in the bug given has caused the Debian Bug report #1072245, regarding Gcc-14 crash when building with -std=c2x on sid to be marked as done. This means that you claim that the problem has

Bug#1079856: creduce: Still depens on clang-format-17

Package: creduce Version: 2.11.0~20240312-1+b1 Severity: normal Hi The program depends on clang-format-17, even though it seems to use clang-format-18: $ grep -r clang-format /usr/share/creduce/perl /usr/share/creduce/perl/creduce_config.pm:CLANG_FORMAT => q{/usr/lib/llvm-18/bin/clang

Bug#1004184: gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el

Source: gcc-11 Followup-For: Bug #1004184 Control: fixed -1 gcc-14/14.1.0-1 I haven't yet confirmed that the output of an O1/O2 build is corrected when compiling on MIPS, but the relevant patches have arrived in gcc v14.1 and are packaged in Debian, so I'm updating the tags on this bug

Bug#1077492: marked as done (libasan8: missing symbols ___interceptor_shmctl and __interceptor_trampoline_shmctl)

Your message dated Sun, 18 Aug 2024 17:34:40 + with message-id and subject line Bug#1077492: fixed in gcc-14 14.2.0-3 has caused the Debian Bug report #1077492, regarding libasan8: missing symbols ___interceptor_shmctl and __interceptor_trampoline_shmctl to be marked as done. This means

Bug#1078158: gcc-doc-defaults: switch to GCC 14

On 2024-08-07 15:13:52 +0200, Andreas Beckmann wrote: > gcc-doc-defaults started to FTBFS when the default compiler has been > switched to GCC 14. Please update the doc package to GCC 14, too. But gcc-14-doc is not available in Debian yet. -- Vincent Lefèvre - Web: 100

[Bug lto/43659] -flto doesn't remember -fPIC

||176 CC||sjames at gcc dot gnu.org -- You are receiving this mail because: You reported the bug.

Processed: Re: Bug#1077657: Acknowledgement (g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O)

Processing control commands: > found -1 14.2.0-2 Bug #1077657 [g++-14-arm-linux-gnueabihf] g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O Marked as found in versions gcc-14/14.2.0-2. -- 1077657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077

Bug#1077657: Acknowledgement (g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O)

Control: found -1 14.2.0-2

Processed: Re: Bug#1078144: marked as done (gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found)

Processing control commands: > reopen -1 Bug #1078144 {Done: Matthias Klose } [src:gcc-14] gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need t

Bug#1078144: marked as done (gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found)

Control: reopen -1 keep it open, until everything can be built with the GNATBIND/GNATMAKE provided by tools configured in the toplevel directory.

Bug#1078144: marked as done (gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found)

Your message dated Sun, 11 Aug 2024 02:36:58 + with message-id and subject line Bug#1078144: fixed in gcc-14 14.2.0-2 has caused the Debian Bug report #1078144, regarding gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found to be marked as done. This means that you claim that the

Processed: Re: Bug#1078144: gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found

Processing control commands: > tags -1 + pending Bug #1078144 [src:gcc-14] gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found Added tag(s) pending. -- 1078144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078144 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#1078144: gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found

Control: tags -1 + pending On 09.08.24 15:14, zhangdandan wrote: Dear maintainers, On Wed, 7 Aug 2024 20:16:56 +0800 zhangdandan wrote: > gcc-14 provides gnatmake-14, without gnatmake. > The command gnatmake is used in gcc-14(14.2.0-1) > src/gcc/ada/Make-generated.in. > Please pay attenti

Bug#1078144: gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found

Dear maintainers, On Wed, 7 Aug 2024 20:16:56 +0800 zhangdandan wrote: > gcc-14 provides gnatmake-14, without gnatmake. > The command gnatmake is used in gcc-14(14.2.0-1) > src/gcc/ada/Make-generated.in. > Please pay attention to the above phenomenon. > Refer to gcc-13/gcc-12/gcc-11 on amd64,

Bug#1077776: marked as done (gcc-14 ftbfs on loong64 (illegal instruction))

Your message dated Thu, 8 Aug 2024 07:36:57 +0200 with message-id and subject line Re: gcc-14 ftbfs on loong64 (illegal instruction) has caused the Debian Bug report #106, regarding gcc-14 ftbfs on loong64 (illegal instruction) to be marked as done. This means that you claim that the problem

Bug#1078158: gcc-doc-defaults: switch to GCC 14

Source: gcc-doc-defaults Version: 5:27 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) gcc-doc-defaults started to FTBFS when the default compiler has been switched to GCC 14. Please update the doc package to GCC 14, too. Andreas

Bug#1078144: gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found

Source: gcc-14 Version: 14.2.0-1 Severity: important Tags: sid User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, Compiling the gcc-14 (14.2.0-1) failed for loong64 in the Debian Package Auto-Building environment. For loong64, build-depend on the gdc-14 and gnat-14 fro

Bug#1077776: gcc-14 ftbfs on loong64 (illegal instruction)

Hi doko, On Fri, 2 Aug 2024 02:35:23 +0200 Matthias Klose wrote: > Package: src:gcc-14 > Version: 14.2.0-1 > Severity: important > Tags: sid trixie > X-Debbugs-CC: debian-loonga...@lists.debian.org > > [...] > checking for libphobos support... yes > checking for loongarch64-linux-gnu-gcc... loon

[Bug middle-end/323] optimized code gives strange floating point results

#232 from Andrew Pinski --- *** Bug 116230 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

Bug#1057046: Removed package(s) from unstable

Version: 2.64+dfsg-1.1+rm Dear submitter, as the package autoconf2.64 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debia

Bug#1057046: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: autoconf2.64 | 2.64+dfsg-1.1 | source, all --- Reason --- RoQA; obsolete version -- Note that the package(s

Bug#1039531: marked as done (autoconf2.64: Keep out of testing)

Your message dated Sun, 04 Aug 2024 00:44:17 + with message-id and subject line Bug#1057046: Removed package(s) from unstable has caused the Debian Bug report #1039531, regarding autoconf2.64: Keep out of testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1077776: gcc-14 ftbfs on loong64 (illegal instruction)

Package: src:gcc-14 Version: 14.2.0-1 Severity: important Tags: sid trixie X-Debbugs-CC: debian-loonga...@lists.debian.org [...] checking for libphobos support... yes checking for loongarch64-linux-gnu-gcc... loongarch64-linux-gnu-gcc-14 checking whether the C compiler works... no configure: erro

Bug#1077763: gcc-14: An alignment request might be added before endbr on function entry.

Package: gcc-14 Version: 14.1.0-5 Severity: important Control: forwarded -1 https://gcc.gnu.org/PR116174 gcc-14 may add an alignment requesst before endbr with -fcf-protection=branch -O2. Upstream report has a testcase. This is just for tracking. Sebastian

Bug#1077715: gcc-13-cross-ports ftbfs building the loong64 cross compilers

Package: src:gcc-13-cross-ports Version: 16 Severity: serious Tags: sid trixie X-Debbugs-CC: debian-loonga...@lists.debian.org gcc-13-cross-ports ftbfs building the loong64 cross compilers: [...] collect2: error: ld returned 1 exit status make[7]: *** [Makefile:998: libgcc_s.so] Error 1 make[7]:

Bug#1065276: marked as done (please build loong64 packages)

Your message dated Thu, 1 Aug 2024 04:12:08 +0200 with message-id <9d8a1ee7-e58d-4a35-b86a-ed9b0cc33...@debian.org> and subject line loong64 packages available in unstable has caused the Debian Bug report #1065276, regarding please build loong64 packages to be marked as done. This means th

Bug#1077657: g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O

Package: g++-14-arm-linux-gnueabihf Version: 14.1.0-5 Severity: important Dear Maintainer, I have the following minimal program that does not compile on armhf with -O. It however *does* compile without the optimization flag, or with or without -O on amd64 and other architectures. (I'm maintaining

Bug#1077492: libasan8: missing symbols ___interceptor_shmctl and __interceptor_trampoline_shmctl

Package: libasan8 Version: 14.1.0-5 User: helm...@debian.org Usertags: rebootstrap The source package libasan.symbols.common declares symbols ___interceptor_shmctl and __interceptor_trampoline_shmctl, but the armhf binary package symbols file misses them. This is also evident from the build log ht

Processed: Re: Bug#735497 closed by Debian FTP Masters (Bug#1076502: Removed package(s) from unstable)

Processing control commands: > reopen -1 Bug #735497 {Done: Debian FTP Masters } [gcc-9,gcc-10,gcc-11] libgcc1: Can switch to use new Allow-Internal-Symbol-Groups for aeabi symbols 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Re: Bug#735497 closed by Debian FTP Masters (Bug#1076502: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 libgcc-s1 On Sun, 2024-07-28 at 15:30:09 +, Debian Bug Tracking System wrote: > Version: 9.5.0-6+rm > > Dear submitter, > > as the package gcc-9 has just been removed from the Debian archive > unstable we hereby close the associate

Bug#929777: Bug#1076503: Removed package(s) from unstable

On 2024-07-28 15:35:35 +, Debian FTP Masters wrote: > Version: 10.5.0-4+rm > > Dear submitter, > > as the package gcc-10 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We are sorry > that we couldn't dea

Bug#930430: Bug#1076502: Removed package(s) from unstable

Control: reopen -1 Control: reassign -1 libasan8 14.1.0-5 On 2024-07-28 15:27:28 +, Debian FTP Masters wrote: > Version: 9.5.0-6+rm > > Dear submitter, > > as the package gcc-9 has just been removed from the Debian archive > unstable we hereby close the associated bug repo

Processed: Re: Bug#1076502: Removed package(s) from unstable

Processing control commands: > reopen -1 Bug #930430 {Done: Debian FTP Masters } [libasan5] libasan5: AddressSanitizer breaks when LD_PRELOAD is defined 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need t

Bug#1076503: Removed package(s) from unstable

Version: 10.5.0-4+rm Dear submitter, as the package gcc-10 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1076503

Bug#1076503: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-10 | 10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x g++-10 | 10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x g++-10-multilib

Bug#1076503: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-10-aarch64-linux-gnu | 10.5.0-1cross2 | amd64, i386, ppc64el cpp-10-arm-linux-gnueabi | 10.5.0-1cross2 | amd64, arm64, i386, ppc64el cpp-10-arm-linux-gnueabihf | 10.5.0-1cross2 | amd64

Bug#1076503: Removed package(s) from unstable

Version: 10.5.0-2cross1+rm Dear submitter, as the package gcc-10-cross-mipsen has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see

Bug#1076503: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-10-mips-linux-gnu | 10.5.0-1cross1 | amd64, arm64, i386, ppc64el cpp-10-mips-linux-gnu | 10.5.0-2cross1 | mips64el cpp-10-mips64-linux-gnuabi64 | 10.5.0-1cross1 | amd64, arm64, i386

Bug#1076503: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-10-alpha-linux-gnu | 10.5.0-1cross2 | amd64, i386 cpp-10-hppa-linux-gnu | 10.5.0-1cross2 | amd64, i386 cpp-10-m68k-linux-gnu | 10.5.0-1cross2 | amd64, i386 cpp-10-powerpc-linux-gnu

Bug#1076502: Removed package(s) from unstable

Version: 9.5.0-6+rm Dear submitter, as the package gcc-9 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1076502

Bug#1076502: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-9 | 9.4.0-2+b1 | mips64el cpp-9 | 9.5.0-6+b2 | amd64, arm64, armel, armhf, i386, ppc64el, s390x g++-9 | 9.4.0-2+b1 | mips64el g++-9 | 9.5.0-6+b2 | amd64, arm64

Bug#1076502: Removed package(s) from unstable

Version: 29+rm Dear submitter, as the package gcc-9-cross has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1076502

Bug#1076502: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-9-aarch64-linux-gnu | 9.5.0-4cross1 | amd64, i386, ppc64el cpp-9-arm-linux-gnueabi | 9.5.0-4cross1 | amd64, arm64, i386, ppc64el cpp-9-arm-linux-gnueabihf | 9.5.0-4cross1 | amd64

Bug#1076502: Removed package(s) from unstable

Version: 9.3.0-8cross1+rm Dear submitter, as the package gcc-9-cross-mipsen has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see

Bug#1076502: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-9-mips-linux-gnu | 9.3.0-8cross1 | amd64, arm64, i386, mips64el, ppc64el cpp-9-mips64-linux-gnuabi64 | 9.3.0-8cross1 | amd64, arm64, i386, mips64el, ppc64el cpp-9-mips64el-linux

Bug#995916: marked as done (std::stoi, std::stol, std::stoul, ... broken on sh4)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #995916, regarding std::stoi, std::stol, std::stoul, ... broken on sh4 to be marked as done. This means that you claim that the

Bug#986629: marked as done (ICE in vect_init_pattern_stmt, at tree-vect-patterns.c:116 building adacontrol)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #986629, regarding ICE in vect_init_pattern_stmt, at tree-vect-patterns.c:116 building adacontrol to be marked as done. This means

Bug#983436: marked as done (i386-cpuinfo.h missing in gcc-10-plugin-dev)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #983436, regarding i386-cpuinfo.h missing in gcc-10-plugin-dev to be marked as done. This means that you claim that the problem has

Bug#979350: marked as done (gcc-10: compiling bug of code for https://github.com/Return-To-The-Roots/s25client)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #979350, regarding gcc-10: compiling bug of code for https://github.com/Return-To-The-Roots/s25client to be marked as done. This

Bug#978153: marked as done (libgphobos-10-dev: include/d/std/stdio.d (and rest of std/*) missing on PowerPC (eg. ppc64el) architectures only)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #978153, regarding libgphobos-10-dev: include/d/std/stdio.d (and rest of std/*) missing on PowerPC (eg. ppc64el) architectures only

Bug#976024: marked as done (g++-10 crashes for bitpacked enum class)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #976024, regarding g++-10 crashes for bitpacked enum class to be marked as done. This means that you claim that the problem has been

Bug#977638: marked as done (g++-10:s390x: Large classes of std::bitset and std::vector hash the same)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #977638, regarding g++-10:s390x: Large classes of std::bitset and std::vector hash the same to be marked as done. This means that

Bug#975142: marked as done (internal compiler error: ‘verify_type’ failed)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #975142, regarding internal compiler error: ‘verify_type’ failed to be marked as done. This means that you claim that the problem has

Bug#974781: marked as done (gcc-10: Please upgrade to llvm-toolchain-11)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #974781, regarding gcc-10: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has

Bug#973698: marked as done (g++-10: regresson in 10.2.0-16: internal compiler error: in tsubst_decl, at cp/pt.c:14666)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #973698, regarding g++-10: regresson in 10.2.0-16: internal compiler error: in tsubst_decl, at cp/pt.c:14666 to be marked as done

Bug#971547: marked as done (gcc-10: gm2 should be disabled for cross-builds in debian/rules.defs)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #971547, regarding gcc-10: gm2 should be disabled for cross-builds in debian/rules.defs to be marked as done. This means that you

Bug#963564: marked as done (gfortran: Internal error when processing pFUnit generated files with --coverage)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #963564, regarding gfortran: Internal error when processing pFUnit generated files with --coverage to be marked as done. This means

Bug#960643: marked as done (gdc-10: manpage and gdc --help doesn't mention -fmain)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #960643, regarding gdc-10: manpage and gdc --help doesn't mention -fmain to be marked as done. This means that you claim tha

Bug#963254: marked as done (gcc-10: d/rules.def, set AQ to :all for cross build)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #963254, regarding gcc-10: d/rules.def, set AQ to :all for cross build to be marked as done. This means that you claim that the

Bug#960248: marked as done (gdc-10 -flto -fno-weak crashes on some codes)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #960248, regarding gdc-10 -flto -fno-weak crashes on some codes to be marked as done. This means that you claim that the problem has

Bug#1069559: marked as done (g++-10: std::regex_constants::multiline (C++17) missing in -std=gnu++20)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #1069559, regarding g++-10: std::regex_constants::multiline (C++17) missing in -std=gnu++20 to be marked as done. This means that

Bug#1031822: marked as done (gcc-10: ICE in tsubst, at cp/pt.c:15310)

Your message dated Sun, 28 Jul 2024 15:35:35 + with message-id and subject line Bug#1076503: Removed package(s) from unstable has caused the Debian Bug report #1031822, regarding gcc-10: ICE in tsubst, at cp/pt.c:15310 to be marked as done. This means that you claim that the problem has been

Bug#1076502: Removed package(s) from unstable

Version: 27+rm Dear submitter, as the package gcc-9-cross-ports has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/10

  1   2   3   4   5   6   7   8   9   10   >