Bug#1049993: gcc: add symlink for path with vendored-triple

2023-08-18 Thread Matthias Klose

On 18.08.23 04:27, YunQiang Su wrote:

Package: src:gcc-13
Version: 13.2.0-4

Can we consider adding a symlink from non-vendor triples to vendored triples?
For example:
  /usr/lib/gcc/x86_64-linux-gnu -> /usr/lib/gcc/x86_64-unknown-linux-gnu

LLVM guys complains about it:
 https://reviews.llvm.org/D158183#4596086



I don't think this is a good idea.  The triplets are organized to follow the 
multiarch triplets where possible (the one exception is i386). So unless you 
want to change the multiarch triplets, this is a no-go.


it would be much better to directly fetch the installation information from GCC, 
i.e.


  gcc -print-search-dirs
  gcc -print-multiarch



Bug#1050013: gcc-13: Please don't build the Ada, Go, D and M2 on LoongArch

2023-08-18 Thread zhangdandan

Package: gcc-13
Version: 13.2.0-2
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64

Dear gcc maintainers,

According to the status of the GCC upstream[1], the Ada, Go, D and M2 
modules
are not supported on the LoongArch architecture. Please don't build the 
Ada,
Go, D and M2 modules on the LoongArch architecture in the gcc-13 source 
package.


In the future, when the GCC upstream supports Ada, Go, D or M2 modules for
the LoongArch architecture, please help us to enable the corresponding 
support

in debian/rules.defs.

Please consider the patch attached.
For ease of viewing, I've added the patch in personal Debian GCC project[2].
Your opinions are welcome.

[1]: https://gcc.gnu.org/gcc-13/changes.html
[2]: 
https://salsa.debian.org/zhangdandan/gcc/-/commit/82f3b19df4d6ba97728a15fecc40f8c77cec02b5


thanks,
Dandan Zhang

Subject: [PATCH] Disable Ada, Go, D and M2 on LoongArch

---
 debian/rules.defs | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/debian/rules.defs b/debian/rules.defs
index 17ffb78..892b1e9 100644
--- a/debian/rules.defs
+++ b/debian/rules.defs
@@ -847,7 +847,7 @@ endif
 
 ifeq (,$(filter $(DEB_STAGE),stage1 stage2))
 # Ada 
-ada_no_cpus	:= m32r sh3 sh3eb sh4eb
+ada_no_cpus	:= loong64 m32r sh3 sh3eb sh4eb
 ada_no_cpus	+= arc
 ada_no_cpus	+= ia64
 ada_no_systems	:= 
@@ -1006,7 +1006,7 @@ ifneq (,$(findstring gccgo, $(PKGSOURCE)))
   with_libcc1 :=
 endif
 
-go_no_cpus := arc avr hppa
+go_no_cpus := arc avr hppa loong64
 go_no_cpus += m68k # See PR 79281 / PR 83314
 go_no_systems := kfreebsd
 ifneq (,$(filter $(distrelease),precise))
@@ -1064,7 +1064,7 @@ endif
 # D ---
 d_no_cross := yes
 d_no_snap :=
-d_no_cpus := alpha arc ia64 m68k sh4 s390 sparc64
+d_no_cpus := alpha arc ia64 loong64 m68k sh4 s390 sparc64
 d_no_systems := gnu kfreebsd-gnu
 
 ifneq ($(single_package),yes)
@@ -1261,7 +1261,7 @@ ifneq ($(with_base_only),yes)
 with_m2 := yes
   endif
 endif
-m2_no_archs = powerpc ppc64 sh4 kfreebsd-amd64 kfreebsd-i386 hurd-amd64 hurd-i386
+m2_no_archs = powerpc ppc64 sh4 kfreebsd-amd64 kfreebsd-i386 hurd-amd64 hurd-i386 loong64
 ifneq (,$(filter $(DEB_TARGET_ARCH),$(m2_no_archs)))
 with_m2 := disabled for cpu $(DEB_TARGET_ARCH)
 endif
-- 
2.39.2



Bug#1050013: gcc-13: Please don't build the Ada, Go, D and M2 on LoongArch

2023-08-18 Thread Matthias Klose

Control: tags -1 + moreinfo

please can you file upstream reports for each of these frontends?

On 18.08.23 13:07, zhangdandan wrote:

Package: gcc-13
Version: 13.2.0-2
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64

Dear gcc maintainers,

According to the status of the GCC upstream[1], the Ada, Go, D and M2 modules
are not supported on the LoongArch architecture. Please don't build the Ada,
Go, D and M2 modules on the LoongArch architecture in the gcc-13 source package.

In the future, when the GCC upstream supports Ada, Go, D or M2 modules for
the LoongArch architecture, please help us to enable the corresponding support
in debian/rules.defs.

Please consider the patch attached.
For ease of viewing, I've added the patch in personal Debian GCC project[2].
Your opinions are welcome.

[1]: https://gcc.gnu.org/gcc-13/changes.html
[2]: 
https://salsa.debian.org/zhangdandan/gcc/-/commit/82f3b19df4d6ba97728a15fecc40f8c77cec02b5


thanks,
Dandan Zhang





Processed: Re: Bug#1050013: gcc-13: Please don't build the Ada, Go, D and M2 on LoongArch

2023-08-18 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #1050013 [gcc-13] gcc-13: Please don't build the Ada, Go, D and M2 on 
LoongArch
Added tag(s) moreinfo.

-- 
1050013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processing of gcc-doc-defaults_27_source.changes

2023-08-18 Thread Debian FTP Masters
gcc-doc-defaults_27_source.changes uploaded successfully to localhost
along with the files:
  gcc-doc-defaults_27.dsc
  gcc-doc-defaults_27.tar.xz
  gcc-doc-defaults_27_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Processed: gcc-11-doc should not be shipped in trixie

2023-08-18 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 1023690
Bug #1050029 [src:gcc-11-doc] gcc-11-doc should not be shipped in trixie
1050029 was not blocked by any bugs.
1050029 was not blocking any bugs.
Added blocking bug(s) of 1050029: 1023690

-- 
1050029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1042960: marked as done (FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc')

2023-08-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Aug 2023 15:27:10 +
with message-id 
and subject line Bug#1042960: fixed in gcc-doc-defaults 5:27
has caused the Debian Bug report #1042960,
regarding FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 
3 package 'gcc-doc'
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 ow...@bugs.debian.org
immediately.)


-- 
1042960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc-base
Version: 12.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

gcc-doc-base currently fails to build from source on amd64. From my build log:

| dh_gencontrol -pgcc-doc-base -- -v12.2.0-1
| dh_gencontrol -i --remaining-packages
| dh_gencontrol: warning: No packages to build. Possible architecture mismatch: 
amd64, want: all alpha amd64 arm64 armel armhf i386 ia64 mips mipsel mipsn32 
mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 
mips64r6el powerpc ppc64 ppc64el s390 s390x sparc sparc64 x32 any
| make[1]: Leaving directory '/<>'
|dh_md5sums
|dh_builddeb
| dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 
package 'gcc-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/cpp-doc/DEBIAN/control' near line 3 
package 'cpp-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: error: parsing file 'debian/gfortran-doc/DEBIAN/control' near line 
3 package 'gfortran-doc':
|  'Version' field value '5:': nothing after colon in version number
| dh_builddeb: error: dpkg-deb --build debian/gcc-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/cpp-doc .. returned exit code 2
| dh_builddeb: error: dpkg-deb --build debian/gfortran-doc .. returned exit 
code 2
| dpkg-deb: building package 'gnat-doc' in '../gnat-doc_12.2.0-1_amd64.deb'.
| dpkg-deb: error: parsing file 'debian/gccgo-doc/DEBIAN/control' near line 3 
package 'gccgo-doc':
|  'Version' field value '5:': nothing after colon in version number
| dpkg-deb: building package 'gcc-doc-base' in 
'../gcc-doc-base_12.2.0-1_all.deb'.
| dh_builddeb: error: dpkg-deb --build debian/gccgo-doc .. returned exit code 2
| dh_builddeb: error: Aborting due to earlier error
| make: *** [debian/rules:117: binary] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
| 

| Build finished at 2023-08-03T10:53:37Z

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:27
Done: Dmitry Baryshkov 

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Baryshkov  (supplier of updated gcc-doc-defaults 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 13:56:04 +0300
Source: gcc-doc-defaults
Architecture: source
Version: 5:27
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Baryshkov 
Closes: 1042960
Changes:
 gcc-doc-defaults (5:27) unstable; urgency=medium
 .
   * d/control: remove -guest from Salsa URLs
   * d/rules: add riscv64 to go_archs to sync with gcc-defaults
   * d/rules: Build using GCC 13 (Closes: #1042960)
   * d/control: regen using GCC 13
Checksums-Sha1:
 4d5c2a170d28297f5319dcfe09e38c53306fcc13 2081 gcc-doc-defaults_27.dsc
 c24ec2fa96af1c8d7ff8d07cfc3ff87ec3cfd3c8 31708 gcc-doc-defaults_27.tar.xz
 7c52b0d6370792a873a7e6aa6f36d00cb7740090 6601 
gcc-doc-defaults_27_source.buildinfo
Checksums-Sha256:
 92f46038945b8a4dc9d9fb74d55f11dfc75c8c2b19f8560bacb77f62029de839 2081 
gcc-doc-defaults_27.dsc
 cde1c083594064b68ef669444ce1585f40e15d85507a7a62116861330dc08599 31708 
gcc-doc-defaults_27.tar.xz
 3da9a396131fc49f7c67cbf3abe1b30c5cf1fbbc094bb5eec49b51df64a94980 6601 
gcc-doc-defaults_27_source

gcc-doc-defaults_27_source.changes ACCEPTED into unstable

2023-08-18 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 13:56:04 +0300
Source: gcc-doc-defaults
Architecture: source
Version: 5:27
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Baryshkov 
Closes: 1042960
Changes:
 gcc-doc-defaults (5:27) unstable; urgency=medium
 .
   * d/control: remove -guest from Salsa URLs
   * d/rules: add riscv64 to go_archs to sync with gcc-defaults
   * d/rules: Build using GCC 13 (Closes: #1042960)
   * d/control: regen using GCC 13
Checksums-Sha1:
 4d5c2a170d28297f5319dcfe09e38c53306fcc13 2081 gcc-doc-defaults_27.dsc
 c24ec2fa96af1c8d7ff8d07cfc3ff87ec3cfd3c8 31708 gcc-doc-defaults_27.tar.xz
 7c52b0d6370792a873a7e6aa6f36d00cb7740090 6601 
gcc-doc-defaults_27_source.buildinfo
Checksums-Sha256:
 92f46038945b8a4dc9d9fb74d55f11dfc75c8c2b19f8560bacb77f62029de839 2081 
gcc-doc-defaults_27.dsc
 cde1c083594064b68ef669444ce1585f40e15d85507a7a62116861330dc08599 31708 
gcc-doc-defaults_27.tar.xz
 3da9a396131fc49f7c67cbf3abe1b30c5cf1fbbc094bb5eec49b51df64a94980 6601 
gcc-doc-defaults_27_source.buildinfo
Files:
 637e2f6e7d05c84182c8663a92559ae7 2081 contrib/doc optional 
gcc-doc-defaults_27.dsc
 de8b783fd2b95959a04244f73f6378af 31708 contrib/doc optional 
gcc-doc-defaults_27.tar.xz
 6a999cb86fe921d0212c491f6832a2f5 6601 contrib/doc optional 
gcc-doc-defaults_27_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFJBAEBCgAzFiEETHCElVyyY1bwuJV/izyKPgIpKNUFAmTM7SEVHGRiYXJ5c2hr
b3ZAZ21haWwuY29tAAoJEIs8ij4CKSjV8mEIAJJwd/6M5sF0zteIOeEeRQIS4Eb3
8pMMOFpEou2cqyZwLUkfXPRuaZJ3znVJB9I4BbYKdSQKBLcMet1v4yFh/Gg8uvG5
g130MkreN7ZU9NtwFSLQiXx6WHNbDFVPWDAPyCXPKvxc447Uagvqy4v9eBhwb9Bd
6g/9/w0+bm4pelTLY6GLiVD5I+1ajcMtrlkyJW7icmgTAoi2chFPL6KcVJH8OCM8
EIbD6vFhchtyK103puvcDvaKXCTRUW9l5a/DRlvDfNAGV5g/XeGMupasSM/pI7C+
wBlDASOot+vHCJNJAZb/nShtGJPgtJoYci52wgQLoDDf+rFMLfDTYYSPdPg=
=54ur
-END PGP SIGNATURE-



Bug#1050063: src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries

2023-08-18 Thread Paul Gevers

Source: gcc-11-cross-mipsen
Version: 5+c3
Severity: serious
Control: close -1 6+c1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:gcc-11-cross-mipsen has been trying to 
migrate for 35 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=gcc-11-cross-mipsen



OpenPGP_signature.asc
Description: OpenPGP digital signature


Processed: src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries

2023-08-18 Thread Debian Bug Tracking System
Processing control commands:

> close -1 6+c1
Bug #1050063 [src:gcc-11-cross-mipsen] src:gcc-11-cross-mipsen: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked as fixed in versions gcc-11-cross-mipsen/6+c1.
Bug #1050063 [src:gcc-11-cross-mipsen] src:gcc-11-cross-mipsen: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked Bug as done

-- 
1050063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processing of gcc-11-cross-mipsen_6+c1+nmu1_source.changes

2023-08-18 Thread Debian FTP Masters
gcc-11-cross-mipsen_6+c1+nmu1_source.changes uploaded successfully to localhost
along with the files:
  gcc-11-cross-mipsen_6+c1+nmu1.dsc
  gcc-11-cross-mipsen_6+c1+nmu1.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)