[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#953657: marked as done (generate dependencies on libgcc-sN instead of libgccN)



Your message dated Thu, 12 Mar 2020 23:05:30 +0000
with message-id <E1jCWtO-0009uM-RN@fasolo.debian.org>
and subject line Bug#953657: fixed in glibc 2.30-2
has caused the Debian Bug report #953657,
regarding generate dependencies on libgcc-sN instead of libgccN
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 owner@bugs.debian.org
immediately.)


-- 
953657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953657
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.29-10
Tags: patch

Please generate dependencies on libgcc-sN instead of libgccN.


  * libc6: Depend on libgcc-sN instead of libgccN.

diff -Nru glibc-2.31/debian/rules.d/debhelper.mk glibc-2.31/debian/rules.d/debhelper.mk
--- glibc-2.31/debian/rules.d/debhelper.mk	2020-03-02 15:24:11.000000000 +0000
+++ glibc-2.31/debian/rules.d/debhelper.mk	2020-03-07 08:34:11.000000000 +0000
@@ -166,7 +166,7 @@
 	# Generate common substvars files.
 	: > tmp.substvars
 ifeq ($(filter stage1 stage2,$(DEB_BUILD_PROFILES)),)
-	echo 'libgcc:Depends=libgcc1 [!hppa !m68k], libgcc2 [m68k], libgcc4 [hppa]' >> tmp.substvars
+	echo 'libgcc:Depends=libgcc-s1 [!hppa !m68k], libgcc-s2 [m68k], libgcc-s4 [hppa]' >> tmp.substvars
 	echo 'libcrypt:Depends=libcrypt1' >> tmp.substvars
 	echo 'libcrypt-dev:Depends=libcrypt-dev' >> tmp.substvars
 endif

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-2
Done: Aurelien Jarno <aurel32@debian.org>

We believe that the bug you reported is fixed in the latest version of
glibc, 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 953657@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated glibc 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 23:47:03 +0100
Source: glibc
Architecture: source
Version: 2.30-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 953657
Changes:
 glibc (2.30-2) unstable; urgency=medium
 .
   * debian/rules.d/debhelper.mk: depends on libgcc-sN instead of libgccN.
     Closes: #953657.
   * debian/rules.d/build.mk: do not install <finclude/math-vector-fortran.h>
     for now as it is not multiarch safe.
Checksums-Sha1:
 11fcb9cc68443aa76492ed9cc10822d82fc0c586 8731 glibc_2.30-2.dsc
 577a3d99e56e37cbb4dd48ccdc07882cd1600814 841832 glibc_2.30-2.debian.tar.xz
 d4b9e00f102152d38dfa236b62e7d0e0ec5a622b 7703 glibc_2.30-2_source.buildinfo
Checksums-Sha256:
 19c2612533e66817c056584583e6c8f242b38c26760f3fb706ea7e7225222f20 8731 glibc_2.30-2.dsc
 d8b11490a64e3e091b197f3074427775e9ffd54da4eebc582fd8ee793d0b9409 841832 glibc_2.30-2.debian.tar.xz
 133843b53dbe8fb380eb89897981de031f542fa9edf9d6c13709f4ed9ec26247 7703 glibc_2.30-2_source.buildinfo
Files:
 5a837d4566b891c4051718042988a060 8731 libs required glibc_2.30-2.dsc
 6b193604dac3e17fb7bbb3d895d205fc 841832 libs required glibc_2.30-2.debian.tar.xz
 0f3ee12d82a664fae4c0a24cd46f1b67 7703 libs required glibc_2.30-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl5qvdIACgkQE4jA+Jno
M2t6vQ//Xi45sLEnlc0lwMwaMtmoUw3ThErkGFWBBZwXWSidB1x+AO+Of2AQuMpG
WipGFsfPSvX9x97zqcocjcu/0guoWhZ0fgexCcoS/8JKLC+nDnaqlLoANszDFBeS
59WpUz+YOgxvkoogI56TnBTVhg9hRK93t8ttktmLp8Do18vCl43f+k2nX3mIPMHs
e+COIjqf0W3qiQiFxnJcmeTXtanQry17EFzLLnwYFDK7QsIs7hi5WdWRqy/VnJ0g
5A29KjnnohWnSiswAsIRIovj9gX3SPbYh47+2b/tGZoEmsnoV3YhdKfC4FVkUmKl
YKkbTBuqJRJ56ovchgKVBPfqQWNJibFbhczpimIOp3msguPtG0BjvUPP6jEfAENQ
NFyPolwRtuvZyDI7jXqz59pqW8JfGtvIY4BK5DFLcgfd9G3E+gx6uR3y4/o3VUSz
JoOwlqxeM0sF3HSAaukEx3Kh5MO++ToVsndMYMphzQrpUxzKu2ww43rUaJjRm4la
Sj5FfP0YxnCPwiAA0pq6EmXayWiaisxG4GLggNhN/7hvoZV8jvu7I4x7XQSFtliw
eBmOyyg9dMd63zar+aLoGKbJH8Pt3OWCRqCZZ/tw8Fq0bL1RcOR1GiFmJSH+V1In
xWPLV64RffCj+f2ezyMEg3iBgXKo8bCp5ypEpg3lCD/1LwnFydA=
=gTls
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: