Bug#990066: unblock: distcc/3.3.2-10+deb10u1
On 19 juin 2021 08:40, Christian Marillat wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: maril...@debian.org > > Please unblock package distcc > > The Debian script update-distcc-symlinks who generate gcc/clang symlinks in > /usr/lib/distcc doesn't work with gcc cross compiler and clang. > > This bug has been "fixed" in 3.3.2-6 by installing the upstream python > script, but I reverted to the Debian perl script in 3.3.2-8 to not depends > on python3 without reopening/fixing bug #919704 Would be nice to know if this package is accepter in buster before the bullseye release. Christian
Información 2021 FOESCO
FOESCO informa Abierto el plazo de inscripción de CURSOS BONIFICABLES E-LEARNING dirigidos a empleados en activo o en situación de ERTE (Convocatoria JULIO 2021) Plazo de inscripción hasta el 30 de Junio Adjuntamos PDF con el listado de cursos disponibles. Para más información por favor respondan a este mismo correo electrónico o bien llamen al teléfono 910323794. Saludos cordiales. FOESCO Formación Estatal Continua. Departamento de Formación Bonificable. Tel: 910 323 794 (Horario de 9h a 15h y de 17h a 20h de Lunes a Viernes)
NEW changes in stable-new
Processing changes file: shim-helpers-arm64-signed_1+15.4+6~deb10u1_arm64-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: shim-helpers-amd64-signed_1+15.4+6~deb10u1_amd64.changes ACCEPT Processing changes file: shim-helpers-i386-signed_1+15.4+6~deb10u1_i386.changes ACCEPT
Bug#989695: pre-approval: mono/6.8.0.105+dfsg-3.1
Hi, On 10-06-2021 19:25, Andreas Beckmann wrote: > If you ACK this, I intend to 0-day NMU this to experimental because it > needs NEW processing. Please prod the ftp-masters to get this actually done. We don't have control over ftp-masters *and* I still need some days before I can actually look properly into this (I suspect strongly that other colleagues won't beat me to it). Therefor, I propose you already upload to experimental. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#990277: unblock: feature-check/0.2.2-7
Control: tags -1 moreinfo confirmed
On 2021-06-24 15:42:28 +0300, Peter Pentchev wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> This is a pre-approval request before I upload feature-check/0.2.2-7
> to unstable to fix an RC bug.
Please go ahead and remove the moreinfo tag once the new version is
available in unstable.
>
> [ Reason ]
> See #990276 (https://bugs.debian.org/990276): Version comparisons may
> return the wrong result.
>
> [ Impact ]
> If the feature-check command-line tool is used by other programs to
> make sure that an installed program has a recent enough version of
> a supported feature, the checks may fail for some versions containing
> non-numeric characters (pre-release, patch, etc).
>
> [ Tests ]
> The patches include additions to the feature-check unit-test suite that
> is run both at build time and as an autopkgtest.
>
> [ Risks ]
> Leaf package, not widely used yet; targeted fix, so hopefully
> any risks are very low.
>
> [ Checklist ]
> [x] all changes are documented in the d/changelog
> [x] I reviewed all changes and I approve them
> [x] attach debdiff against the package in testing
>
> unblock feature-check/0.2.2-7
> diff -Nru feature-check-0.2.2/debian/changelog
> feature-check-0.2.2/debian/changelog
> --- feature-check-0.2.2/debian/changelog 2020-10-26 11:14:52.0
> +0200
> +++ feature-check-0.2.2/debian/changelog 2021-06-24 15:33:07.0
> +0300
> @@ -1,3 +1,10 @@
> +feature-check (0.2.2-7) unstable; urgency=medium
> +
> + * Add the cmp-num and cmp-rest upstream patches to fix some version
> +string comparisons. Closes: #990276
> +
> + -- Peter Pentchev Thu, 24 Jun 2021 15:33:07 +0300
> +
> feature-check (0.2.2-6) unstable; urgency=medium
>
>[ Michael Hudson-Doyle ]
> diff -Nru feature-check-0.2.2/debian/patches/cmp-num.patch
> feature-check-0.2.2/debian/patches/cmp-num.patch
> --- feature-check-0.2.2/debian/patches/cmp-num.patch 1970-01-01
> 02:00:00.0 +0200
> +++ feature-check-0.2.2/debian/patches/cmp-num.patch 2021-06-24
> 15:30:21.0 +0300
> @@ -0,0 +1,46 @@
> +Description: Fix a 2 < 10 version int/string bug.
> +Origin: upstream;
> https://gitlab.com/ppentchev/feature-check/-/commit/ed0da5159562fa37cf32386a1baf2a1114562822
> +Bug-Debian: https://bugs.debian.org/990276
> +Author: Peter Pentchev
> +Last-Update: 2021-06-24
> +
> +--- a/perl5/feature-check.pl
> b/perl5/feature-check.pl
> +@@ -269,7 +269,7 @@
> + if ($na ne '') {
> + if ($nb ne '') {
> + if ($nb != $na) {
> +-return $na cmp $nb;
> ++return $na <=> $nb;
> + }
> + } else {
> + return 1;
> +--- a/t/04-simple.t
> b/t/04-simple.t
> +@@ -1,6 +1,6 @@
> + #!/usr/bin/perl
> + #
> +-# Copyright (c) 2018 Peter Pentchev
> ++# Copyright (c) 2018, 2021 Peter Pentchev
> + # All rights reserved.
> + #
> + # Redistribution and use in source and binary forms, with or without
> +@@ -89,6 +89,18 @@
> + ['base ge 3', 0],
> + ['base gt 3', 0],
> + ['base eq 3', 0],
> ++
> ++['base lt 10', 1],
> ++['base le 10', 1],
> ++['base ge 10', 0],
> ++['base gt 10', 0],
> ++['base eq 10', 0],
> ++
> ++['base lt 10.1', 1],
> ++['base le 10.1', 1],
> ++['base ge 10.1', 0],
> ++['base gt 10.1', 0],
> ++['base eq 10.1', 0],
> + );
> +
> + my %c = env_init;
> diff -Nru feature-check-0.2.2/debian/patches/cmp-rest.patch
> feature-check-0.2.2/debian/patches/cmp-rest.patch
> --- feature-check-0.2.2/debian/patches/cmp-rest.patch 1970-01-01
> 02:00:00.0 +0200
> +++ feature-check-0.2.2/debian/patches/cmp-rest.patch 2021-06-24
> 15:30:28.0 +0300
> @@ -0,0 +1,62 @@
> +Description: Fix a 3.0.beta2 < 3.0 version int/string bug.
> +Origin: upstream;
> https://gitlab.com/ppentchev/feature-check/-/commit/59e618baff6836f281697561f5a9cfa22ccd28df
> +Bug-Debian: https://bugs.debian.org/990276
> +Author: Peter Pentchev
> +Last-Update: 2021-06-24
> +
> +--- a/perl5/feature-check.pl
> b/perl5/feature-check.pl
> +@@ -282,7 +282,7 @@
> + if ($ra ne '') {
> + if ($rb ne '') {
> + if ($ra ne $rb) {
> +-return $ra <=> $rb;
> ++return $ra cmp $rb;
> + }
> + } else {
> + return 1;
> +--- a/t/04-simple.t
> b/t/04-simple.t
> +@@ -101,6 +101,42 @@
> + ['base ge 10.1', 0],
> + ['base gt 10.1', 0],
> + ['base eq 10.1', 0],
> ++
> ++['beta lt 1', 0],
> ++['beta le 1', 0],
> ++['beta eq 1', 0],
> ++['beta ge 1', 1],
> ++['beta gt 1', 1],
> ++
> ++['beta lt 3.0', 1],
> ++['beta le 3.0', 1],
> ++['beta eq 3.0', 0],
> ++['beta ge 3.0', 0],
> ++['beta gt 3.0', 0],
> ++
> ++['beta lt 3.0.beta1',
Processed: Re: Bug#990277: unblock: feature-check/0.2.2-7
Processing control commands: > tags -1 moreinfo confirmed Bug #990277 [release.debian.org] unblock: feature-check/0.2.2-7 Added tag(s) confirmed and moreinfo. -- 990277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990203: marked as done (unblock: cinnamon-screensaver/4.8.1-3)
Your message dated Fri, 25 Jun 2021 18:37:53 + with message-id and subject line unblock cinnamon-screensaver has caused the Debian Bug report #990203, regarding unblock: cinnamon-screensaver/4.8.1-3 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.) -- 990203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package cinnamon-screensaver [ Reason ] /etc/pam.d/cinnamon-screensaver was missed for a mistake in 4.8.1-1, 4.8.1-3 readd it [ Impact ] Impact is for new bullseye install, upgrade from version that still have the file (as conffile) should be null instead FWIK [ Tests ] I tested the new package install/upgrade and I not found issue [ Risks ] there should be no risk FWIK The diff: https://salsa.debian.org/cinnamon-team/cinnamon-screensaver/-/compare/debian%2F4.8.1-2...debian%2F4.8.1-3 unblock cinnamon-screensaver/4.8.1-3 --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
NEW changes in stable-new
Processing changes file: shim-helpers-amd64-signed_1+15.4+6~deb10u1_source.changes ACCEPT Processing changes file: shim-helpers-arm64-signed_1+15.4+6~deb10u1_source.changes ACCEPT Processing changes file: shim-helpers-i386-signed_1+15.4+6~deb10u1_source.changes ACCEPT
Bug#990319: unblock: intel-microcode/3.20210608.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package intel-microcode I would like to unblock the intel-microcode update currently in unstable, so that it will be available in Debian 11. Please note that the current plans are that a Debian 10 (buster) security update, intel-microcode/3.20210608.2~deb10u1, will be delivered to Debian stable in the next couple days through debian-security, in which case the version currently in Debian 11 "bullseye" would be *OLDER* than what would be available in buster-security and unstable. Also, please be warned that this update has the potential to cause regressions when compared to the previous version of the intel-microcode package. But do read the text below for the full rationale. Potential regressions: intel-microcode/3.20210608.2 restores a *LOT* of security updates to Skylake D0/R0, but it might cause boot problems on systems that have too old a microcode update *in BIOS*. I have been asking around to check if this still happens on the new microcode, but I haven't heard from anyone affected yet. Ubuntu and upstream reports about this: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31 https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890 intel-microcode/3.20210608.2 can also cause Intel WiFi connection issues on systems with Intel Wireless *on-board* and a specific family of processors (CoffeLake signature 0x906ea). There is hope that a newer release of iwlwifi-firmware (which is being arranged by the Debian security team, since it is *also* a security update to mitigate some of FragAttack) works around this issue. Upstream report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/56 Rationale for issuing it as a security-update to Debian buster, and the Debian bollseye unblock request: I have talked it over with the stable security team, and they're fully aware of the above regression potential. We considered several possible scenarios (including *not* updating the affected processors), and the security team prefers that we *do* issue the full microcode update, but warn users of the potential issues. The reason behind this decision is simple: we were forced to withold relevant operational and security updates from a much larger set of users, to avoid regressions on a much smaller set of users, and have done so for quite a while already. This situation cannot continue indefinitely. Anyway, once the buster-security update to intel-microcode/3.20210608.2~deb10u1 is out, switching bullseye to intel-microcode/3.20210608.2 is *NOT* going to add any regressions compared to Debian stable + security updates. I am filling this bug report before the security update is distributed just in case. IMPORTANT: I do recommend that we wait for at least 10 more days before possibly unblocking the migration of intel-microcode/3.20210608.2 to bullseye, anyway. That will allow for feedback from the security update to be acted upon. Here's the git diffstat (git diff attached, as usual): README.md | 14 ++-- changelog | 59 debian/changelog | 71 intel-ucode-with-caveats/06-4f-01 |binary intel-ucode/06-3f-02 |binary intel-ucode/06-3f-04 |binary intel-ucode/06-4e-03 |binary intel-ucode/06-55-03 |binary intel-ucode/06-55-04 |binary intel-ucode/06-55-05 |binary intel-ucode/06-55-06 |binary intel-ucode/06-55-07 |binary intel-ucode/06-55-0b |binary intel-ucode/06-56-03 |binary intel-ucode/06-56-04 |binary intel-ucode/06-56-05 |binary intel-ucode/06-5c-09 |binary intel-ucode/06-5c-0a |binary intel-ucode/06-5e-03 |binary intel-ucode/06-5f-01 |binary intel-ucode/06-6a-05 |binary intel-ucode/06-6a-06 |binary intel-ucode/06-7a-01 |binary intel-ucode/06-7a-08 |binary intel-ucode/06-7e-05 |binary intel-ucode/06-86-04 |binary intel-ucode/06-86-05 |binary intel-ucode/06-8a-01 |binary intel-ucode/06-8c-01 |binary intel-ucode/06-8c-02 |binary intel-ucode/06-8d-01 |binary intel-ucode/06-8e-09 |binary intel-ucode/06-8e-0a |binary intel-ucode/06-8e-0b |binary intel-ucode/06-8e-0c |binary intel-ucode/06-96-01 |binary intel-ucode/06-9c-00 |binary intel-ucode/06-9e-09 |binary intel-ucode/06-9e-0a |binary intel-ucode/06-9e-0b |binary intel-ucode/06-9e-0c |binary intel-ucode/06-9e-0d |binary
Bug#990315: buster-pu: package gcc-mingw-w64/21.3~deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Dear release team,
Would it be possible to upload the backported fix for gcc-mingw-w64’s
#989862 to Buster? The debdiff is attached; it’s a minimal, targeted
fix for gcov support.
Regards,
Stephen
-- System Information:
Debian Release: 10.10
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'),
(100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100,
'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 4.19.0-17-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
commit f319345c3caf1dedbfc87654e1853762af3b6d77
Author: Stephen Kitt
Date: Tue Jun 15 22:18:31 2021 +0200
Fix gcov handling
When gcov is supported in a cross-compiler setup, GCC assumes that
either the headers are present and shared with the host, or present
and set up in a sysroot, or absent. We have headers which aren’t
shared and aren’t in a sysroot, so we need to tell GCC where they are
*without* specifying them as an argument to --with-headers (the latter
must only be enabled).
Closes: #989862
LP: #1883933, #1920988
(cherry picked from commit 2ee26ff4f275384aa6173ada884929db4d2f1bbf)
diff --git a/debian/changelog b/debian/changelog
index 66834dc..7d18a47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+gcc-mingw-w64 (21.3~deb10u2) buster; urgency=medium
+
+ * Fix gcov handling: we need to tell GCC that we have headers, without
+telling it where, and then we need to correct its default assumption
+about where they are. Closes: #989862. LP: #1883933, #1920988.
+
+ -- Stephen Kitt Sat, 12 Jun 2021 18:54:10 +0200
+
gcc-mingw-w64 (21.3~deb10u1) buster; urgency=medium
* Upload to Buster.
diff --git a/debian/patches/gcov.patch b/debian/patches/gcov.patch
index 4400d53..4e6a83e 100644
--- a/debian/patches/gcov.patch
+++ b/debian/patches/gcov.patch
@@ -1,10 +1,17 @@
-Description: Add __gcov_exit for gcov fallback
+Description: Fix gcov build issues
Author: Stephen Kitt
When gcov is not supported on the target, gcc uses a fallback
do-nothing implementation. That’s missing a __gcov_exit()
implementation, causing linking errors.
+When gcov is supported in a cross-compiler setup, GCC assumes that
+either the headers are present and shared with the host, or present
+and set up in a sysroot, or absent. We have headers which aren’t
+shared and aren’t in a sysroot, so we need to tell GCC where they are
+*without* specifying them as an argument to --with-headers (the latter
+must only be enabled).
+
--- a/src/libgcc/libgcov-driver.c
+++ b/src/libgcc/libgcov-driver.c
@@ -30,6 +30,7 @@
@@ -15,3 +22,14 @@ implementation, causing linking errors.
#endif
#else /* inhibit_libc */
+--- a/src/gcc/configure.ac
b/src/gcc/configure.ac
+@@ -2268,7 +2268,7 @@
+ if test "x$with_build_sysroot" != "x"; then
+ target_header_dir="${with_build_sysroot}${native_system_header_dir}"
+ elif test "x$with_sysroot" = x; then
+-target_header_dir="${test_exec_prefix}/${target_noncanonical}/sys-include"
++target_header_dir="${test_exec_prefix}/${target_noncanonical}/include"
+ elif test "x$with_sysroot" = xyes; then
+
target_header_dir="${test_exec_prefix}/${target_noncanonical}/sys-root${native_system_header_dir}"
+ else
diff --git a/debian/patches/series1 b/debian/patches/series1
index 048c6bf..7a28c31 100644
--- a/debian/patches/series1
+++ b/debian/patches/series1
@@ -1,3 +1,4 @@
disable-multilib.patch
reproducible-sort.patch
bug-55930.patch
+gcov.patch
diff --git a/debian/patches/series2 b/debian/patches/series2
index 53bd6d3..4cce23c 100644
--- a/debian/patches/series2
+++ b/debian/patches/series2
@@ -1,5 +1,4 @@
reproducible-s-oscons.patch
-gcov.patch
wc-file-streams.patch
refactor-path-construction.patch
win-std-filesystem.patch
diff --git a/debian/rules b/debian/rules
index e9e4416..4bbb4d1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -187,9 +187,9 @@ CONFFLAGS = \
--libdir=/$(PF)/$(libdir) \
--enable-libstdcxx-time=yes \
--with-tune=generic
-# Tell GCC where the headers are (this enables gcov)
+# Tell GCC we have headers (this enables gcov)
CONFFLAGS += \
- --with-headers=/usr/$$target/include
+ --with-headers
# MinGW-w64 flags
# version-specific-runtime-libs puts target-specific libraries in
# /usr/lib/gcc rather than /usr/$(target)
