Re: Re: [SUA 252-1] Updated nVidia driver packages

[Stephen Kitt]

On Fri, Feb 16, 2024 at 12:11:17PM +, Jonathan Wiltshire wrote:
> Is there a reason you don't have contrib and non-free enabled for most of
> those sources?

Perhaps the problem is that SUA 252-1 only mentions main:

> Upgrade Instructions
> 
> 
> You can get the updated packages by adding the stable-updates archive
> for your distribution to your /etc/apt/sources.list:
> 
>  deb https://deb.debian.org/debian bookworm-updates main
>  deb-src https://deb.debian.org/debian bookworm-updates main
> 
> You can also use any of the Debian archive mirrors.  See
> https://www.debian.org/mirrors/list for the full list of mirrors.

Anyone following the publishing instructions as-is won’t get the update.

On top of that, non-free doesn’t matter, nvidia-graphics-drivers is in
non-free-firmware.

Regards,

Stephen


pgpYtcP6tz3dI.pgp
Description: OpenPGP digital signature

Bug#1035539: unblock: binutils-mingw-w64/10.4

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package binutils-mingw-w64.

[ Reason ]
Version 10.4 includes a two-line upstream fix for a crash when
handling certain import libraries.

[ Impact ]
Users with affected libraries can’t use Bookworm’s binutils-mingw-w64
at all; this is a regression from Bullseye.

[ Tests ]
The reporter of https://bugs.debian.org/1029841 provided a test case;
see also https://sourceware.org/bugzilla/show_bug.cgi?id=30079

[ Risks ]
The fix is tiny:

diff --git a/ld/ldlang.c b/ld/ldlang.c
index 84a2914fc26..b5e0d026ae4 100644
--- a/upstream/ld/ldlang.c
+++ b/upstream/ld/ldlang.c
@@ -649,7 +649,8 @@ wild_sort (lang_wild_statement_type *wild,
 looking at the sections for this file.  */
 
   /* Find the correct node to append this section.  */
-  if (compare_section (sec->spec.sorted, section, (*tree)->section) < 0)
+  if (sec && sec->spec.sorted != none && sec->spec.sorted != by_none
+ && compare_section (sec->spec.sorted, section, (*tree)->section) < 0)
tree = &((*tree)->left);
   else
tree = &((*tree)->right);

The risk is minute.

[ 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 binutils-mingw-w64/10.4


Regards,

Stephen
diff -Nru binutils-mingw-w64-10.3/debian/changelog 
binutils-mingw-w64-10.4/debian/changelog
--- binutils-mingw-w64-10.3/debian/changelog2023-01-11 13:02:20.0 
+0100
+++ binutils-mingw-w64-10.4/debian/changelog2023-05-03 08:49:22.0 
+0200
@@ -1,3 +1,9 @@
+binutils-mingw-w64 (10.4) unstable; urgency=medium
+
+  * Apply upstream patch to fix an internal error. Closes: #1029841.
+
+ -- Stephen Kitt   Wed, 03 May 2023 08:49:22 +0200
+
 binutils-mingw-w64 (10.3) unstable; urgency=medium
 
   * Drop another failing codeview test.
diff -Nru binutils-mingw-w64-10.3/debian/patches/pr30079.patch 
binutils-mingw-w64-10.4/debian/patches/pr30079.patch
--- binutils-mingw-w64-10.3/debian/patches/pr30079.patch1970-01-01 
01:00:00.0 +0100
+++ binutils-mingw-w64-10.4/debian/patches/pr30079.patch2023-05-03 
08:49:22.0 +0200
@@ -0,0 +1,26 @@
+commit b7eab2a9d4f4e92692daf14b09fc95ca11b72e30
+Author: Michael Matz 
+Date:   Thu Feb 9 15:29:00 2023 +0100
+
+Fix PR30079: abort on mingw
+
+the early-out in wild_sort is not enough, it might still be
+that filenames are equal _and_ the wildcard list doesn't specify
+a sort order either.  Don't call compare_section then.
+
+Tested on all targets.
+
+diff --git a/ld/ldlang.c b/ld/ldlang.c
+index 84a2914fc26..b5e0d026ae4 100644
+--- a/upstream/ld/ldlang.c
 b/upstream/ld/ldlang.c
+@@ -649,7 +649,8 @@ wild_sort (lang_wild_statement_type *wild,
+looking at the sections for this file.  */
+ 
+   /* Find the correct node to append this section.  */
+-  if (compare_section (sec->spec.sorted, section, (*tree)->section) < 0)
++  if (sec && sec->spec.sorted != none && sec->spec.sorted != by_none
++&& compare_section (sec->spec.sorted, section, (*tree)->section) < 0)
+   tree = &((*tree)->left);
+   else
+   tree = &((*tree)->right);
diff -Nru binutils-mingw-w64-10.3/debian/patches/series 
binutils-mingw-w64-10.4/debian/patches/series
--- binutils-mingw-w64-10.3/debian/patches/series   2021-10-25 
10:49:54.0 +0200
+++ binutils-mingw-w64-10.4/debian/patches/series   2023-05-03 
08:46:34.0 +0200
@@ -3,3 +3,4 @@
 dont-run-objcopy.patch
 disable-flags.patch
 reproducible-import-libraries.patch
+pr30079.patch

Bug#1031930: nmu: binutils-mingw-w64_10.3, gdb-mingw-w64_12

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: Matthias Klose 

Dear release team,

Please binNMU binutils-mingw-w64 and gdb-mingw-w64:

nmu binutils-mingw-w64_10.3 . ANY . unstable . -m "Rebuild for outdated 
Built-Using"
nmu gdb-mingw-w64_12 . ANY . unstable . -m "Rebuild for outdated Built-Using"

Thanks,

Stephen

Bug#1025137: bullseye-pu: package g810-led/0.4.2-1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

g810-led has a security issue in stable; it leaves /dev/input/eventXX
device nodes world-readable and writable (CVE-2022-46338). The issue
is marked no-dsa, but I would like to provide a fix in the next
point-release. The fix is already in unstable (0.4.2-3).

The attached debdiff fixes the issue by patching the udev rules file:
the affected device nodes have their mode set to 660 instead of 666,
and uaccess is used to provide access to the user at the console. I
own relevant hardware and have verified the fix myself on a multi-user
system.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable

Regards,

Stephen
diff -Nru g810-led-0.4.2/debian/changelog g810-led-0.4.2/debian/changelog
--- g810-led-0.4.2/debian/changelog 2020-05-23 20:33:29.0 +0200
+++ g810-led-0.4.2/debian/changelog 2022-11-30 08:24:25.0 +0100
@@ -1,3 +1,11 @@
+g810-led (0.4.2-1+deb11u1) bullseye; urgency=medium
+
+  * Control device access with uaccess instead of making everything
+world-writable. Thanks to Xavi Drudis Ferran for the report!
+Closes:#1024998. (CVE-2022-46338.)
+
+ -- Stephen Kitt   Wed, 30 Nov 2022 08:24:25 +0100
+
 g810-led (0.4.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru g810-led-0.4.2/debian/patches/device-permissions.patch 
g810-led-0.4.2/debian/patches/device-permissions.patch
--- g810-led-0.4.2/debian/patches/device-permissions.patch  1970-01-01 
01:00:00.0 +0100
+++ g810-led-0.4.2/debian/patches/device-permissions.patch  2022-11-30 
08:23:44.0 +0100
@@ -0,0 +1,74 @@
+commit e2b486fd1bc21e0b784e1b4c959770772dfced24
+Author: Stephen Kitt 
+Date:   Mon Nov 28 21:05:05 2022 +0100
+
+Rely on uaccess to control device access
+
+The udev rules currently make supported device nodes world-readable
+and writable, which means that any process on the system can read
+traffic from keyboards including passwords etc. To avoid this, while
+still allowing the "controlling" user to run g810-led without being
+root, this patch adds a uaccess tag; this ensures that the user at the
+console has write access to the devices. The mode is also changed to
+660 to ensure that existing device nodes are fixed on upgrade.
+
+Thanks to Xavi Drudis Ferran for bringing this to my attention.
+
+Fixes: #293
+Signed-off-by: Stephen Kitt 
+
+diff --git a/udev/g810-led.rules b/udev/g810-led.rules
+index 90b743b..ea05726 100644
+--- a/udev/g810-led.rules
 b/udev/g810-led.rules
+@@ -1,25 +1,25 @@
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c336", MODE="666" RUN+="/usr/bin/g213-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c330", MODE="666" RUN+="/usr/bin/g410-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c33a", MODE="666" RUN+="/usr/bin/g413-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c342", MODE="666" RUN+="/usr/bin/g512-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c33c", MODE="666" RUN+="/usr/bin/g513-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c333", MODE="666" RUN+="/usr/bin/g610-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c338", MODE="666" RUN+="/usr/bin/g610-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c331", MODE="666" RUN+="/usr/bin/g810-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c337", MODE="666" RUN+="/usr/bin/g810-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c33f", MODE="666" RUN+="/usr/bin/g815-led -p 
/etc/g810-led/profile"
+-ACTION=="add", SUBSYSTEMS=="u

Bug#990315: buster-pu: package gcc-mingw-w64/21.3~deb10u1

[Stephen Kitt]

On Sun, 18 Jul 2021 18:35:52 +0100, "Adam D. Barratt"
 wrote:
> On Fri, 2021-06-25 at 15:08 +0200, Stephen Kitt wrote:
> > 
> > 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.
> 
> Please go ahead; sorry for the delay.

Done, thanks!

Regards,

Stephen


pgpDpnOxOJrMO.pgp
Description: OpenPGP digital signature

Bug#990315: buster-pu: package gcc-mingw-w64/21.3~deb10u1

[Stephen Kitt]

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)

Bug#989916: unblock: gcc-mingw-w64/24.2

[Stephen Kitt]

Control: tags -1 - moreinfo

Hi Graham,

On Wed, 16 Jun 2021 11:55:48 +0200, Graham Inggs  wrote:
> There's a typo in your changelog, the bug number should be #989862:
> 
> +gcc-mingw-w64 (24.2) unstable; 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: #989682. LP: #1883933, #1920988.
> +
> + -- Stephen Kitt   Sat, 12 Jun 2021 18:54:10 +0200

Oops, nice catch, thanks!

> Other than that, please go ahead and upload to unstable, and remove
> the moreinfo tag once it has built.

Done, and it’s built on all the release architectures.

Regards,

Stephen


pgpXT1EwgVyOr.pgp
Description: OpenPGP digital signature

Bug#989916: unblock: gcc-mingw-w64/24.2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

This is a pre-upload unblock request for gcc-mingw-w64, to fix a
regression affecting gcov support and profile-guided optimisation,
both of which are completely broken.

The proposed debdiff is attached.

unblock gcc-mingw-w64/24.2

Regards,

Stephen


-- System Information:
Debian Release: 10.9
  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-12-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, 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 332aa0b9869ab48e4a4d80710d89c58c60b33c07
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: #989682
LP: #1883933, #1920988

diff --git a/debian/changelog b/debian/changelog
index ace01f8..348b62a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+gcc-mingw-w64 (24.2) unstable; 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: #989682. LP: #1883933, #1920988.
+
+ -- Stephen Kitt   Sat, 12 Jun 2021 18:54:10 +0200
+
 gcc-mingw-w64 (24.1) unstable; urgency=medium
 
   * Update gcc-mingw-w64-base’s README.Debian with the switch to Dwarf2.
diff --git a/debian/patches/gcov.patch b/debian/patches/gcov.patch
index 4e9e610..5113282 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
 @@ -31,6 +31,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 eca45ad..89c05d4 100644
--- a/debian/patches/series1
+++ b/debian/patches/series1
@@ -1,2 +1,3 @@
 disable-multilib.patch
 reproducible-sort.patch
+gcov.patch
diff --git a/debian/patches/series2 b/debian/patches/series2
index 479f603..8c7122b 100644
--- a/debian/patches/series2
+++ b/debian/patches/series2
@@ -1,3 +1,2 @@
 reproducible-s-oscons.patch
-gcov.patch
 vmov-alignment.patch
diff --git a/debian/rules b/debian/rules
index fd0b6d7..b71f935 100755
--- a/debian/rules
+++ b/debian/rules
@@ -217,9 +217,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)

Bug#987485: unblock: jhead/1:3.04-6

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package jhead

It fixes a number of buffer overflows and related issues, applying
upstream fixes only.

The changelog is

jhead (1:3.04-6) unstable; urgency=medium

  * QA upload (Salzburg BSP).
  * CVE-2021-3496: check access boundaries in ProcessCanonMakerNoteDir().
Closes: #986923.
  * Check IPTC lengths. Closes: #968999.
  * Allocate extra room when reading JPEG sections to avoid overflows.
Closes: #972617.

 -- Stephen Kitt   Sat, 24 Apr 2021 14:59:38 +0200

and the debdiff is attached.

unblock jhead/1:3.04-6

Regards,

Stephen


-- System Information:
Debian Release: 10.9
  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-12-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, 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
diff --git a/debian/changelog b/debian/changelog
index 2584ce0..2198041 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+jhead (1:3.04-6) UNRELEASED; urgency=medium
+
+  * QA upload (Salzburg BSP).
+  * CVE-2021-3496: check access boundaries in ProcessCanonMakerNoteDir().
+Closes: #986923.
+  * Check IPTC lengths. Closes: #968999.
+  * Allocate extra room when reading JPEG sections to avoid overflows.
+Closes: #972617.
+
+ -- Stephen Kitt   Sat, 24 Apr 2021 13:59:35 +0200
+
 jhead (1:3.04-5) unstable; urgency=medium
 
   * QA upload.
diff --git a/debian/patches/allocate-extra.patch 
b/debian/patches/allocate-extra.patch
new file mode 100644
index 000..f060a3d
--- /dev/null
+++ b/debian/patches/allocate-extra.patch
@@ -0,0 +1,32 @@
+commit 5186ddcf9e35a7aa0ff0539489a930434a1325f4
+Author: Matthias 
+Date:   Fri Oct 23 10:17:20 2020 -0300
+
+Just allocate 20 bytes extra at the end of a section. Otherwise, we end
+up with a whole lot of little checks for structures that the file says
+are there but are unexpectedly cut off in fuzz tests
+
+--- a/jpgfile.c
 b/jpgfile.c
+@@ -170,7 +170,11 @@
+ 
+ Sections[SectionsRead].Size = itemlen;
+ 
+-Data = (uchar *)malloc(itemlen);
++// Allocate an extra 20 bytes more than needed, because sometimes 
when reading structures,
++// if the section erroneously ends before short structures that 
should be there, that can trip
++// memory checkers in combination with fuzzers.
++Data = (uchar *)malloc(itemlen+20);
++  
+ if (Data == NULL){
+ ErrFatal("Could not allocate memory");
+ }
+@@ -477,7 +481,7 @@
+  return FALSE;
+ }
+ 
+-ThumbLen = 0;
++ThumbLen = 0;
+ ThumbnailFile = NULL;
+ }
+ 
diff --git a/debian/patches/cve-2021-3496.patch 
b/debian/patches/cve-2021-3496.patch
new file mode 100644
index 000..1a7ce58
--- /dev/null
+++ b/debian/patches/cve-2021-3496.patch
@@ -0,0 +1,33 @@
+commit ca2973f4ce79279c15a09cf400648a757c1721b0
+Author: matthias wandel 
+Date:   Wed Apr 14 09:01:30 2021 -0300
+
+Fix another fuztest access too far beyond allocated bug
+
+--- a/makernote.c
 b/makernote.c
+@@ -64,7 +64,7 @@
+ unsigned OffsetVal;
+ OffsetVal = Get32u(DirEntry+8);
+ // If its bigger than 4 bytes, the dir entry contains an offset.
+-if (OffsetVal+ByteCount > ExifLength){
++if (OffsetVal+ByteCount > (unsigned)ExifLength || OffsetVal > 
65536){
+ // Bogus pointer offset and / or bytecount value
+ ErrNonfatal("Illegal value pointer for Exif maker tag %04x", 
Tag,0);
+ continue;
+@@ -119,6 +119,7 @@
+ }
+ }
+ if (Tag == 1 && Components > 16){
++if (ByteCount < 17 * sizeof(short)) continue; // Fuzztest -- not 
enough allocated.
+ int IsoCode = Get16u(ValuePtr + 16*sizeof(unsigned short));
+ if (IsoCode >= 16 && IsoCode <= 24){
+ ImageInfo.ISOequivalent = 50 << (IsoCode-16);
+@@ -126,6 +127,7 @@
+ }
+ 
+ if (Tag == 4 && Format == FMT_USHORT){
++if (ByteCount < 20 * sizeof(short)) continue; // Fuzztest -- not 
enough allocated.
+ if (Components > 7){
+ int WhiteBalance = Get16u(ValuePtr + 7*sizeof(unsigned 
short));
+ switch(WhiteBalance){
diff --git a/debian/patches/invalid-IPTC-lengths.patch 
b/debian/patches/invalid-IPTC-lengths.patch
n

Bug#986118: unblock: rocksndiamonds/4.2.2.1+dfsg-2

[Stephen Kitt]

Control: tags -1 -moreinfo

On Tue, 30 Mar 2021 13:33:55 +0200, Sebastian Ramacher 
wrote:
> On 2021-03-29 21:16:32, Stephen Kitt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Hi,
> > 
> > I’d like to upload an updated version of rocksndiamonds for Bullseye;
> > the only change is an updated German debconf translation. The patch is
> > attached.  
> 
> Looks good. Please remove the moreinfo tag once the new version is
> available in unstable.

Thanks, uploaded!

Regards,

Stephen


pgp7iby5gAeB9.pgp
Description: OpenPGP digital signature

Bug#986118: unblock: rocksndiamonds/4.2.2.1+dfsg-2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I’d like to upload an updated version of rocksndiamonds for Bullseye;
the only change is an updated German debconf translation. The patch is
attached.

Regards,

Stephen

unblock rocksndiamonds/4.2.2.1+dfsg-2

-- System Information:
Debian Release: 10.9
  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-12-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, 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
diff --git a/debian/changelog b/debian/changelog
index 0e40a74..5afb4af 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+rocksndiamonds (4.2.2.1+dfsg-2) unstable; urgency=medium
+
+  * Updated German debconf template translation, thanks to Helge
+Kreutzmann. Closes: #980877.
+
+ -- Stephen Kitt   Mon, 29 Mar 2021 21:14:16 +0200
+
 rocksndiamonds (4.2.2.1+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/po/de.po b/debian/po/de.po
index c99bd2b..5b26cfa 100644
--- a/debian/po/de.po
+++ b/debian/po/de.po
@@ -4,19 +4,19 @@
 #
 # Matthias Julius , 2007.
 # Thomas Mueller , 2009.
+# Helge Kreutzmann , 2021.
 msgid ""
 msgstr ""
-"Project-Id-Version: rocksndiamonds 3.2.2-12\n"
+"Project-Id-Version: rocksndiamonds 4.2.2.0+dfsg-1\n"
 "Report-Msgid-Bugs-To: rocksndiamo...@packages.debian.org\n"
 "POT-Creation-Date: 2020-12-25 21:14+0100\n"
-"PO-Revision-Date: 2009-09-05 08:48+0200\n"
-"Last-Translator: Thomas Mueller \n"
+"PO-Revision-Date: 2021-01-23 17:38+0100\n"
+"Last-Translator: Helge Kreutzmann \n"
 "Language-Team: German \n"
 "Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
 "Plural-Forms:  nplurals=2; plural=(n != 1);\n"
 
 #. Type: boolean
@@ -34,9 +34,8 @@ msgid ""
 "automatically downloaded from the Internet and installed locally."
 msgstr ""
 "Die Datendateien, die von rocksndiamonds benötigt werden, stehen unter "
-"keiner Lizenz, die eine Verteilung in einem Paket erlaubt. Wie auch immer, "
-"diese können automatisch aus dem Internet geladen und lokal installiert "
-"werden."
+"keiner Lizenz, die eine Verteilung in einem Paket erlaubt. Sie können jedoch "
+"automatisch aus dem Internet heruntergeladen und lokal installiert werden."
 
 #. Type: boolean
 #. Description
@@ -47,6 +46,10 @@ msgid ""
 "Legend of Zelda (2.1 MiB), Legend of Zelda II (12 MiB), rnd_jue (18 MiB), "
 "Snake Bite (6.3 MiB), Supaplex (7.2 MiB)."
 msgstr ""
+"Einige dieser Downloads sind recht groß: BD2K3 (4,5 MiB), BD "
+"Dream (11 MiB), Contributions 1995 - 2006 (6 MiB), Emerald Mine Club (44 "
+"MiB), Legend of Zelda (2,1 MiB), Legend of Zelda II (12 MiB), rnd_jue (18 "
+"MiB), Snake Bite (6,3 MiB), Supaplex (7,2 MiB)."
 
 #. Type: multiselect
 #. Description

Bug#984487: nmu: libzstd1 rdeps relying on 1.3.8

[Stephen Kitt]

On Fri, 5 Mar 2021 10:34:06 +0100, Sebastian Ramacher 
wrote:
> On 2021-03-04 07:06:05, Stephen Kitt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: binnmu
> > 
> > Dear release team,
> > 
> > libzstd1 used to provide an over-enthusiastic symbols file, which has
> > resulted in dependencies which are too relaxed. The library API isn’t
> > determined by its exported symbols, unfortunately, but by one of its
> > headers. See https://bugs.debian.org/969597 and
> > https://github.com/facebook/zstd/pull/2501 for details.
> > 
> > As a result, a (small) number of packages have picked up a dependency
> > on “libzstd1 (>= 1.3.8)” when it should be “(>= 1.4.0)” — they were
> > built with one of the 1.4 packages, but the symbols file declared some
> > of the 1.4 functions as available in 1.3.8 (which they were,
> > technically, but with a different API in some cases).  
> 
> Please explain. If they were available with a different API prior to
> 1.4, that sounds like an ABI break to me. In that case, the binNMUs
> would just hide the problem.

They weren’t intended to be available as part of the library API. libzstd
distinguishes two sets of functions: one intended for use by programs linked
with the dynamic library, another intended for use by programs linked
statically. Programs built in Debian abide by this rule and don’t use any
symbols they shouldn’t.

Unfortunately, the way the library is built means that “static-only” symbols
are still exported by the dynamic library (even though no dynamically-linked
program uses them). The symbols file appears to have been generated
mechanically, and as a result it includes symbols starting from the point
where they appeared in the library, and not when they officially became part
of the library’s API. The result is that programs built against libzstd 1.4.0
or later, using symbols added in 1.4.0, end up with a dependency on libzstd
1.3.8 or later, even though libzstd 1.3.8 doesn’t support the API they use.

The point of the binNMUs is to fix the latter, by ensuring that packages
depending on libzstd 1.4.0 or later really get an appropriate version of
libzstd. Without this, users can end up with broken packages if they only
partially upgrade their system.

I’m working on a longer-term fix with upstream, see
https://github.com/facebook/zstd/pull/2501 for details. I’ve already
substantially reduced the number of exported symbols (which were never part
of the external API and aren’t used by external users) in 1.4.9 upstream.

Arguably this is a soname breakage, but the case can also be made that it
isn’t: libzstd1 *is* backwards-compatible with all programs built against
older versions, even though some of its exported symbols changed their API
(they weren’t used in the incompatible versions). The invalid dependency
declaration is a consequence of Debian packaging only, IMO. The shlibs file
in the current package in unstable follows upstream’s instructions.

Regards,

Stephen


pgp1jnyQOuQJ6.pgp
Description: OpenPGP digital signature

Bug#984487: nmu: libzstd1 rdeps relying on 1.3.8

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

libzstd1 used to provide an over-enthusiastic symbols file, which has
resulted in dependencies which are too relaxed. The library API isn’t
determined by its exported symbols, unfortunately, but by one of its
headers. See https://bugs.debian.org/969597 and
https://github.com/facebook/zstd/pull/2501 for details.

As a result, a (small) number of packages have picked up a dependency
on “libzstd1 (>= 1.3.8)” when it should be “(>= 1.4.0)” — they were
built with one of the 1.4 packages, but the symbols file declared some
of the 1.4 functions as available in 1.3.8 (which they were,
technically, but with a different API in some cases).

To fix this, would it be possible to binNMU the following? The version
of libzstd1 no longer provides a symbols file and relies on shlibs to
provide the correct dependency.

nmu badger_2.2007.2-2 . ANY . unstable . -m "update libzstd1 dependency"
nmu burrow_1.2.1-2 . ANY . unstable . -m "update libzstd1 dependency"
nmu cadvisor_0.38.7+ds1-2 . ANY . unstable . -m "update libzstd1 dependency"
nmu garagemq_0.0~git20200204.15e6a9d+ds-3 . ANY . unstable . -m "update 
libzstd1 dependency"
nmu lammps_20210122~gita77bb+ds1-2 . ANY . unstable . -m "update libzstd1 
dependency"
nmu libarchive_3.4.3-2 . ANY . unstable . -m "update libzstd1 dependency"
nmu libdrpm_0.5.0-2 . ANY . unstable . -m "update libzstd1 dependency"
nmu mmllib_12-113e3+ds-3 . ANY . unstable . -m "update libzstd1 dependency"
nmu mysql-8.0_8.0.23-3 . ANY . unstable . -m "update libzstd1 dependency"
nmu rsymphony_3.2.3-4 . ANY . unstable . -m "update libzstd1 dependency"

Regards,

Stephen


-- System Information:
Debian Release: 10.8
  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-12-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, 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

Bug#975936: nmu: gcc-mingw-w64_24

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

Please schedule a binNMU for gcc-mingw-w64, for
https://release.debian.org/transitions/html/auto-isl.html

nmu gcc-mingw-w64_24 . ANY . unstable . -m "Rebuild for libisl transition."

Regards,

Stephen


-- System Information:
Debian Release: 10.6
  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-12-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)

Bug#942095: nmu: rebuild packages for binutils 2.33

[Stephen Kitt]

On Thu, 10 Oct 2019 10:51:47 +0200, Matthias Klose  wrote:
> also, binutils-mingw64 might need a sourceful upload.

A binNMU would have worked, but I had some changes queued up so I uploaded
them. There’s also binutils-djgpp now ;-).

Regards,

Stephen


pgpWHgyv7GT1D.pgp
Description: OpenPGP digital signature

Bug#932009: buster-pu: package gcab/1.2-3

[Stephen Kitt]

On Sat, 24 Aug 2019 10:21:24 +0100, "Adam D. Barratt"
 wrote:
> Thanks. Please go ahead.

Uploaded, thanks!

Regards,

Stephen


pgpWMHl7mSxUb.pgp
Description: OpenPGP digital signature

Bug#932009: buster-pu: package gcab/1.2-3

[Stephen Kitt]

On Fri, 26 Jul 2019 16:35:49 -0300, "Adam D. Barratt"
 wrote:
> On 2019-07-13 15:52, Stephen Kitt wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch  
> 
> I assumed you meant buster here and fixed that up.

Ah, yes, thanks!

> > Would it be possible to consider a stable update to gcab 1.2-3 (or its
> > equivalent as a stable upload)? It fixes a data corruption bug,
> > #913487; that’s the only change between 1.2-2, which is in Buster, and
> > 1.2-3, which is in Bullseye. The debdiff is as follows:
> > 
> > diff -Nru gcab-1.2/debian/changelog gcab-1.2/debian/changelog
> > --- gcab-1.2/debian/changelog   2018-12-22 12:37:31.0 +0100
> > +++ gcab-1.2/debian/changelog   2019-07-06 10:18:07.0 +0200
> > @@ -1,3 +1,10 @@
> > +gcab (1.2-3) unstable; urgency=medium  
> 
> While this is probably fine, please could we have a debdiff versioned as 
> 1.2-2+deb10u1 (or 1.2-3~deb10u1 if you prefer and it is exactly the same 
> content as -3), using a changelog distribution of "buster" and built / 
> prepared on buster?

Here goes:

diff -Nru gcab-1.2/debian/changelog gcab-1.2/debian/changelog
--- gcab-1.2/debian/changelog   2018-12-22 12:37:31.0 +0100
+++ gcab-1.2/debian/changelog   2019-08-23 21:30:08.00000 +0200
@@ -1,3 +1,16 @@
+gcab (1.2-3~deb10u1) buster; urgency=medium
+
+  * Rebuild for Buster.
+
+ -- Stephen Kitt   Fri, 23 Aug 2019 21:30:08 +0200
+
+gcab (1.2-3) unstable; urgency=medium
+
+  * Apply upstream patch to fix corruption when extracting.
+Closes: #931487. LP: #1835589.
+
+ -- Stephen Kitt   Sat, 06 Jul 2019 10:18:07 +0200
+
 gcab (1.2-2) unstable; urgency=medium
 
   * Avoid needing PATH_MAX, so we can build on Hurd. Closes: #888640;
diff -Nru gcab-1.2/debian/patches/overflow.patch 
gcab-1.2/debian/patches/overflow.patch
--- gcab-1.2/debian/patches/overflow.patch  1970-01-01 01:00:00.0 
+0100
+++ gcab-1.2/debian/patches/overflow.patch  2019-07-06 10:16:47.0 
+0200
@@ -0,0 +1,44 @@
+commit 5619f4cd2ca3108c8dea17ba656b5ce44a60ca29
+Author: Marc-André Lureau 
+Date:   Fri Jan 11 19:42:40 2019 +0400
+
+Revert "decomp: fix gcc warning strict-overflow"
+
+The warning doesn't happen with current build-sys.
+
+The overlapping behaviour is undefined with memcpy. memmove doesn't
+have the same semantic either than the loop. Let's revert!
+
+Fixes:
+https://gitlab.gnome.org/GNOME/gcab/issues/12
+
+This reverts commit e48074952743f53d8ac529d4debc421e7e0f6937.
+
+Signed-off-by: Marc-André Lureau 
+
+diff --git a/libgcab/decomp.c b/libgcab/decomp.c
+index 64d97f8..0c2b184 100644
+--- a/libgcab/decomp.c
 b/libgcab/decomp.c
+@@ -1015,9 +1015,7 @@ int LZXfdi_decomp(int inlen, int outlen, 
fdi_decomp_state *decomp_state) {
+ window_posn += match_length;
+ 
+ /* copy match data - no worries about destination wraps */
+-memcpy(rundest, runsrc, match_length);
+-rundest += match_length;
+-runsrc += match_length;
++while (match_length-- > 0) *rundest++ = *runsrc++;
+   }
+ }
+ break;
+@@ -1106,9 +1104,7 @@ int LZXfdi_decomp(int inlen, int outlen, 
fdi_decomp_state *decomp_state) {
+ window_posn += match_length;
+ 
+ /* copy match data - no worries about destination wraps */
+-memcpy(rundest, runsrc, match_length);
+-rundest += match_length;
+-runsrc += match_length;
++while (match_length-- > 0) *rundest++ = *runsrc++;
+   }
+ }
+ break;
diff -Nru gcab-1.2/debian/patches/series gcab-1.2/debian/patches/series
--- gcab-1.2/debian/patches/series  2018-12-22 12:37:31.0 +0100
+++ gcab-1.2/debian/patches/series  2019-07-06 10:17:15.0 +0200
@@ -2,3 +2,4 @@
 zalloc_integer_overflow.patch
 no-git-version.patch
 do-not-use-path-max.patch
+overflow.patch


Regards,

Stephen


pgpvK25EIJa_F.pgp
Description: OpenPGP digital signature

Bug#932009: buster-pu: package gcab/1.2-3

[Stephen Kitt]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

Would it be possible to consider a stable update to gcab 1.2-3 (or its
equivalent as a stable upload)? It fixes a data corruption bug,
#913487; that’s the only change between 1.2-2, which is in Buster, and
1.2-3, which is in Bullseye. The debdiff is as follows:

diff -Nru gcab-1.2/debian/changelog gcab-1.2/debian/changelog
--- gcab-1.2/debian/changelog   2018-12-22 12:37:31.0 +0100
+++ gcab-1.2/debian/changelog   2019-07-06 10:18:07.0 +0200
@@ -1,3 +1,10 @@
+gcab (1.2-3) unstable; urgency=medium
+
+  * Apply upstream patch to fix corruption when extracting.
+Closes: #931487. LP: #1835589.
+
+ -- Stephen Kitt   Sat, 06 Jul 2019 10:18:07 +0200
+
 gcab (1.2-2) unstable; urgency=medium
 
   * Avoid needing PATH_MAX, so we can build on Hurd. Closes: #888640;
diff -Nru gcab-1.2/debian/patches/overflow.patch 
gcab-1.2/debian/patches/overflow.patch
--- gcab-1.2/debian/patches/overflow.patch  1970-01-01 01:00:00.0 
+0100
+++ gcab-1.2/debian/patches/overflow.patch  2019-07-06 10:16:47.0 
+0200
@@ -0,0 +1,44 @@
+commit 5619f4cd2ca3108c8dea17ba656b5ce44a60ca29
+Author: Marc-André Lureau 
+Date:   Fri Jan 11 19:42:40 2019 +0400
+
+Revert "decomp: fix gcc warning strict-overflow"
+
+The warning doesn't happen with current build-sys.
+
+The overlapping behaviour is undefined with memcpy. memmove doesn't
+have the same semantic either than the loop. Let's revert!
+
+Fixes:
+https://gitlab.gnome.org/GNOME/gcab/issues/12
+
+This reverts commit e48074952743f53d8ac529d4debc421e7e0f6937.
+
+Signed-off-by: Marc-André Lureau 
+
+diff --git a/libgcab/decomp.c b/libgcab/decomp.c
+index 64d97f8..0c2b184 100644
+--- a/libgcab/decomp.c
 b/libgcab/decomp.c
+@@ -1015,9 +1015,7 @@ int LZXfdi_decomp(int inlen, int outlen, 
fdi_decomp_state *decomp_state) {
+ window_posn += match_length;
+ 
+ /* copy match data - no worries about destination wraps */
+-memcpy(rundest, runsrc, match_length);
+-rundest += match_length;
+-runsrc += match_length;
++while (match_length-- > 0) *rundest++ = *runsrc++;
+   }
+ }
+ break;
+@@ -1106,9 +1104,7 @@ int LZXfdi_decomp(int inlen, int outlen, 
fdi_decomp_state *decomp_state) {
+ window_posn += match_length;
+ 
+ /* copy match data - no worries about destination wraps */
+-memcpy(rundest, runsrc, match_length);
+-rundest += match_length;
+-runsrc += match_length;
++while (match_length-- > 0) *rundest++ = *runsrc++;
+   }
+ }
+ break;
diff -Nru gcab-1.2/debian/patches/series gcab-1.2/debian/patches/series
--- gcab-1.2/debian/patches/series  2018-12-22 12:34:22.0 +0100
+++ gcab-1.2/debian/patches/series  2019-07-06 10:17:15.0 +0200
@@ -2,3 +2,4 @@
 zalloc_integer_overflow.patch
 no-git-version.patch
 do-not-use-path-max.patch
+overflow.patch


Regards,

Stephen

-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: 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)

Bug#930715: release.debian.org: gcc-mingw-w64 Buster upload

[Stephen Kitt]

tag 930715 - moreinfo

On Thu, 20 Jun 2019 16:07:57 +0200, Ivo De Decker  wrote:
> Please note that you didn't use the correct usertag. Please do so in the
> future to avoid the bug getting missed.

Noted, thanks.

> On Wed, Jun 19, 2019 at 09:27:46AM +0200, Stephen Kitt wrote:
> > I uploaded an updated gcc-mingw-w64 package to unstable, 21.3, with a
> > fix for #928214. I’ve since been informed (by Paul Gevers, re
> > Mednafen) that gcc-8 8.3.0-7 won’t be migrating, which means
> > gcc-mingw-w64 21.3 won’t either.
> > 
> > Could I upload the package as 21.3~deb10u1 to testing-pu? The diff
> > between 21.2 and 21.3 is as follows:  
> 
> OK. Please go ahead with the 21.3~deb10u1 upload and set the distribution to
> 'buster' (not 'testing' or 'testing-proposed-updates') and remove the
> moreinfo tag from this bug once the upload has been accepted and built
> everywhere.

It’s now built everywhere:
https://buildd.debian.org/status/package.php?p=gcc-mingw-w64=buster

(Same on unstable after the i386 giveback).

Regards,

Stephen


pgpKnZR0G9DyF.pgp
Description: OpenPGP digital signature

Bug#930865: unblock: bochs/2.6.9+dfsg-3

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

Please unblock package bochs

It adds a couple of missing files which are required for some features
added for Buster. (#930770.)

diff --git a/debian/bochs.install b/debian/bochs.install
index 3574eb6..ba50552 100644
--- a/debian/bochs.install
+++ b/debian/bochs.install
@@ -6,6 +6,7 @@ usr/lib/bochs/plugins/libbx_biosdev.so*
 usr/lib/bochs/plugins/libbx_busmouse.so*
 usr/lib/bochs/plugins/libbx_cmos.so*
 usr/lib/bochs/plugins/libbx_dma.so*
+usr/lib/bochs/plugins/libbx_e1000.so*
 usr/lib/bochs/plugins/libbx_es1370.so*
 usr/lib/bochs/plugins/libbx_eth_*.so*
 usr/lib/bochs/plugins/libbx_extfpuirq.so*
@@ -33,6 +34,7 @@ usr/lib/bochs/plugins/libbx_svga_cirrus.so*
 usr/lib/bochs/plugins/libbx_unmapped.so*
 usr/lib/bochs/plugins/libbx_usb_*.so*
 usr/lib/bochs/plugins/libbx_vga.so*
+usr/lib/bochs/plugins/libbx_voodoo.so*
 usr/share/bochs/keymaps
 usr/share/man/man1/bochs.1.gz
 usr/share/man/man5/bochsrc.5.gz
diff --git a/debian/changelog b/debian/changelog
index 49ef391..03212f7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+bochs (2.6.9+dfsg-3) unstable; urgency=medium
+
+  * Ship the Voodoo and e1000 plugins; thanks to Christian Ehrhardt for
+the patch. Closes: #930770. LP: #1830094.
+
+ -- Stephen Kitt   Thu, 20 Jun 2019 10:37:44 +0200
+
 bochs (2.6.9+dfsg-2) unstable; urgency=medium
 
   * Discard .note.gnu.property section explicitly when building BIOS ROM


unblock bochs/2.6.9+dfsg-3

Regards,

Stephen

-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores)
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)

Bug#930715: release.debian.org: gcc-mingw-w64 Buster upload

[Stephen Kitt]

Package: release.debian.org
Severity: normal

Hi,

I uploaded an updated gcc-mingw-w64 package to unstable, 21.3, with a
fix for #928214. I’ve since been informed (by Paul Gevers, re
Mednafen) that gcc-8 8.3.0-7 won’t be migrating, which means
gcc-mingw-w64 21.3 won’t either.

Could I upload the package as 21.3~deb10u1 to testing-pu? The diff
between 21.2 and 21.3 is as follows:

diff --git a/debian/changelog b/debian/changelog
index a2de56d..dcef4a3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gcc-mingw-w64 (21.3) unstable; urgency=medium
+
+  * Configure LTO support correctly; thanks Alexey Izbyshev!
+Closes: #928214.
+
+ -- Stephen Kitt   Tue, 18 Jun 2019 08:59:34 +0200
+
 gcc-mingw-w64 (21.2) unstable; urgency=medium
 
   * Apply upstream dllimport fix for static data members.
diff --git a/debian/rules b/debian/rules
index 0b55196..e9e4416 100755
--- a/debian/rules
+++ b/debian/rules
@@ -202,8 +202,7 @@ CONFFLAGS += \
--enable-languages=$(languages)
 # LTO
 CONFFLAGS += \
-   --enable-lto \
-   --with-plugin-ld
+   --enable-lto
 # Thread-model-dependent
 CONFFLAGS += \
--enable-threads=$$threads \



The package is currently building in unstable, with a killed job on
i386 for some reason; it also builds fine in testing. I don’t yet have
a fix for #923698, the other RC bug against gcc-mingw-w64 — that will
have to wait for a point release (assuming the fix is approvable).

Regards,

Stephen

-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores)
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)

Bug#926994: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)

[Stephen Kitt]

Control: tags -1 - moreinfo

Le 13/04/2019 16:31, Ivo De Decker a écrit :

I had a look at the patches, and they seem like something that would be
acceptable for buster. Please go ahead with the upload to unstable and 
remove

the moreinfo tag from this bug once the builds are done.


The builds are done, but I see you beat me to it ;-).

Thanks,

Stephen

Bug#926994: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)

[Stephen Kitt]

Hi Ivo,

On Sat, 13 Apr 2019 13:22:01 +0200, Ivo De Decker  wrote:
> On Sat, Apr 13, 2019 at 10:26:04AM +0200, Stephen Kitt wrote:
> > I have a couple of fixes pending upload for gcc-mingw-w64, and I’m
> > wondering if they’d pass muster for Buster. The attached patches fix,
> > in order:
> > 
> > * #923214 — an ICE hit with external static data members
> > * #925172 — std::filesystem support is broken in the current Buster
> >   package
> > 
> > I’m requesting approval for these fixes before uploading them to
> > unstable. The candidate source package would contain only those fixes
> > plus the result of running "dch -r". Note that because of the way
> > gcc-mingw-w64 works, this would involve pulling gcc-8 8.3.0-6 (or
> > whatever version is in unstable when the package is built) in too.  
> 
> I haven't looked at the details of these patches yet, but I notice that this
> doesn't address #923698 (which you set to serious). What's your plan with
> that one?

I’m still working on it, it’s taking longer than I hoped to figure out what’s
broken. I thought it would be worth getting the fixes I do have into the
archive sooner rather than later, especially since #923214 prevents
meaningful testing in a number of cases!

Regards,

Stephen


pgp9_pWREFjbI.pgp
Description: OpenPGP digital signature

Bug#926994: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)

[Stephen Kitt]

It’s always better *with* the patches...

Stephen
From 4b854c788af23f01c01afbd35a3befb060536297 Mon Sep 17 00:00:00 2001
From: Stephen Kitt 
Date: Tue, 9 Apr 2019 09:01:55 +0200
Subject: [PATCH 1/2] Apply upstream dllimport fix for static data members

Closes: #923214
---
 debian/changelog|  7 +++
 debian/patches/gcc9-pr88568-2.patch | 40 +
 debian/patches/series2  |  3 +--
 3 files changed, 48 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/gcc9-pr88568-2.patch

diff --git a/debian/changelog b/debian/changelog
index d9b3631..e540504 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gcc-mingw-w64 (21.2) UNRELEASED; urgency=medium
+
+  * Apply upstream dllimport fix for static data members.
+Closes: #923214.
+
+ -- Stephen Kitt   Thu, 21 Mar 2019 10:45:08 +0100
+
 gcc-mingw-w64 (21.1) unstable; urgency=medium
 
   * Avoid attempting to strip plugins using the target strip; should fix
diff --git a/debian/patches/gcc9-pr88568-2.patch b/debian/patches/gcc9-pr88568-2.patch
new file mode 100644
index 000..3ad3568
--- /dev/null
+++ b/debian/patches/gcc9-pr88568-2.patch
@@ -0,0 +1,40 @@
+2019-03-05  Jakub Jelinek  
+
+	PR c/88568
+	* attribs.c (handle_dll_attribute): Don't clear TREE_STATIC for
+	dllimport on VAR_DECLs with RECORD_TYPE or UNION_TYPE DECL_CONTEXT.
+
+	* g++.dg/other/pr88568.C: New test.
+
+--- a/src/gcc/attribs.c	2019-01-10 11:44:07.122511397 +0100
 b/src/gcc/attribs.c	2019-03-05 13:59:51.745924578 +0100
+@@ -1691,8 +1691,11 @@ handle_dll_attribute (tree * pnode, tree
+ 	 a function global scope, unless declared static.  */
+ 	  if (current_function_decl != NULL_TREE && !TREE_STATIC (node))
+ 	TREE_PUBLIC (node) = 1;
+-	  /* Clear TREE_STATIC because DECL_EXTERNAL is set.  */
+-	  TREE_STATIC (node) = 0;
++	  /* Clear TREE_STATIC because DECL_EXTERNAL is set, unless
++	 it is a C++ static data member.  */
++	  if (DECL_CONTEXT (node) == NULL_TREE
++	  || !RECORD_OR_UNION_TYPE_P (DECL_CONTEXT (node)))
++	TREE_STATIC (node) = 0;
+ 	}
+ 
+   if (*no_add_attrs == false)
+--- a/src/gcc/testsuite/g++.dg/other/pr88568.C	2019-03-05 14:03:20.132509560 +0100
 b/src/gcc/testsuite/g++.dg/other/pr88568.C	2019-03-05 14:01:39.674155860 +0100
+@@ -0,0 +1,13 @@
++// PR c/88568
++// { dg-do compile }
++// { dg-require-dll "" }
++
++struct S {
++  __attribute__((dllimport)) static const char foo[];
++};
++
++int
++foo (int x)
++{
++  return S::foo[x];
++}
diff --git a/debian/patches/series2 b/debian/patches/series2
index 6f5002f..4f7963a 100644
--- a/debian/patches/series2
+++ b/debian/patches/series2
@@ -6,5 +6,4 @@ win-std-filesystem.patch
 hide-path-iostream-operators.patch
 filesystem_error-no-throw-copyable.patch
 overload-distance-and-advance.patch
-#update-path-compare-logic.patch
-#fix-filesystem-path-lexically_normal.patch
+gcc9-pr88568-2.patch
-- 
2.11.0

From e2b9e4ff772453fb81634b9715a83c83deb07d4a Mon Sep 17 00:00:00 2001
From: Stephen Kitt 
Date: Wed, 10 Apr 2019 18:01:26 +0200
Subject: [PATCH 2/2] Explicitly enable std::filesystem

... with the appropriate upstream patch.

Closes: #925172
---
 debian/changelog   |   2 +
 debian/g++-mingw-w64-i686.install.in   |   2 +-
 debian/g++-mingw-w64-x86-64.install.in |   2 +-
 debian/patches/series2 |   1 +
 .../set-shared_ptr-lock-policy-at-build-time.patch | 336 +
 debian/rules   |   8 +-
 6 files changed, 346 insertions(+), 5 deletions(-)
 create mode 100644 debian/patches/set-shared_ptr-lock-policy-at-build-time.patch

diff --git a/debian/changelog b/debian/changelog
index e540504..baee837 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,8 @@ gcc-mingw-w64 (21.2) UNRELEASED; urgency=medium
 
   * Apply upstream dllimport fix for static data members.
 Closes: #923214.
+  * Explicitly enable std::filesystem, with the appropriate upstream
+patch. Closes: #925172.
 
  -- Stephen Kitt   Thu, 21 Mar 2019 10:45:08 +0100
 
diff --git a/debian/g++-mingw-w64-i686.install.in b/debian/g++-mingw-w64-i686.install.in
index e2aea2e..f79b2aa 100644
--- a/debian/g++-mingw-w64-i686.install.in
+++ b/debian/g++-mingw-w64-i686.install.in
@@ -7,5 +7,5 @@ usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++-6.dll
 usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++.a
 usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++.dll.a
 usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++.dll.a-gdb.py
-#usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++fs.a
+usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libstdc++fs.a
 usr/lib/gcc/i686-w64-mingw32/@@VERSION@@*/libsupc++.a
diff --git a/debian/g++-mingw-w64-x86-64.install.in b/debian/g++-mingw-w64-x86-64.install.in
index 76b0ea4..544290e 100644
--- a/debian/g++-mingw-w64-x86-64.install.in
+++ b/debian/g++-mingw-w64-x86-64.

Bug#926994: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I have a couple of fixes pending upload for gcc-mingw-w64, and I’m
wondering if they’d pass muster for Buster. The attached patches fix,
in order:

* #923214 — an ICE hit with external static data members
* #925172 — std::filesystem support is broken in the current Buster
  package

I’m requesting approval for these fixes before uploading them to
unstable. The candidate source package would contain only those fixes
plus the result of running "dch -r". Note that because of the way
gcc-mingw-w64 works, this would involve pulling gcc-8 8.3.0-6 (or
whatever version is in unstable when the package is built) in too.

Regards,

Stephen

unblock gcc-mingw-w64/21.2

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
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)

Bug#926914: unblock: netrek-client-cow/3.3.1-4

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package netrek-client-cow, version 3.3.1-4 fixes a bug
which causes an endless loop in cross-builds (see #924291). The diff
is attached.

Regards,

Stephen

unblock netrek-client-cow/3.3.1-4

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
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)
>From df5828dec76e021606af958aaf84ba5c83da1e41 Mon Sep 17 00:00:00 2001
From: Stephen Kitt 
Date: Wed, 10 Apr 2019 17:34:46 +0200
Subject: [PATCH] Build mkkey using the build CC when cross-compiling

Closes: #924291
---
 debian/changelog   |  7 +++
 debian/control |  1 +
 debian/patches/cross-build-mkkey.patch | 18 ++
 debian/patches/series  |  1 +
 debian/rules   |  5 +
 5 files changed, 32 insertions(+)
 create mode 100644 debian/patches/cross-build-mkkey.patch

diff --git a/debian/changelog b/debian/changelog
index 379e899..7cac1c4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+netrek-client-cow (3.3.1-4) unstable; urgency=medium
+
+  * Team upload.
+  * Build mkkey using the build CC when cross-compiling. Closes: #924291.
+
+ -- Stephen Kitt   Wed, 10 Apr 2019 17:34:14 +0200
+
 netrek-client-cow (3.3.1-3) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/control b/debian/control
index 05880bd..6497278 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends:
  autotools-dev,
  debhelper (>= 9),
  libgmp-dev,
+ libgmp-dev:native,
  libimlib2-dev,
  libsdl-mixer1.2-dev,
  libsdl1.2-dev,
diff --git a/debian/patches/cross-build-mkkey.patch 
b/debian/patches/cross-build-mkkey.patch
new file mode 100644
index 000..128f9ed
--- /dev/null
+++ b/debian/patches/cross-build-mkkey.patch
@@ -0,0 +1,18 @@
+Description: Build mkkey correctly when cross-building
+Author: Stephen Kitt 
+
+There are two parts to this:
+* use BUILDCC (provided by debian/rules) to build;
+* only link libgmp to minimise the native build-dependencies.
+
+--- a/system.mk.in
 b/system.mk.in
+@@ -150,7 +150,7 @@
+   $(MAKE) newkey
+ 
+ mkkey: mkkey.c $(RANDOMOBJ) defs.h
+-  $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) $(MPINC) $(MPLIB) -o mkkey 
mkkey.c $(RANDOMOBJ) $(LIBRARIES)
++  $(BUILDCC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) $(MPINC) $(MPLIB) -o mkkey 
mkkey.c $(RANDOMOBJ) $(LMP)
+ 
+ randomize: randomize.c $(RANDOMOBJ) defs.h
+   $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) -o randomize randomize.c 
$(RANDOMOBJ) $(LIBRARIES)
diff --git a/debian/patches/series b/debian/patches/series
index 678e27d..f749c8b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 gcc5.patch
 possible-infinite-loop.patch
+cross-build-mkkey.patch
diff --git a/debian/rules b/debian/rules
index 418d565..c667701 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,6 +2,8 @@
 #export DH_VERBOSE=1
 export DEB_CFLAGS_MAINT_APPEND=-std=gnu89
 
+include /usr/share/dpkg/architecture.mk
+
 %:
dh $@ --with autotools_dev
 
@@ -11,6 +13,9 @@ override_dh_auto_configure:
--datadir=\$${prefix}/share/games \
--with-gmp
 
+override_dh_auto_build:
+   dh_auto_build -- BUILDCC=$(DEB_BUILD_GNU_TYPE)-gcc
+
 override_dh_auto_test:
 
 override_dh_auto_install:
-- 
2.11.0

Bug#924263: unblock: g810-led/0.3.3-2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package g810-led; version 0.3.3-2 adds a missing
dependency from the -dev package to the library package:

>From 0492d772f77d88acc02d31ef66901d6fb58e2253 Mon Sep 17 00:00:00 2001
From: Stephen Kitt 
Date: Sun, 10 Mar 2019 18:53:43 +0100
Subject: [PATCH] Add dependency from -dev to library package

Closes: #924191
---
 debian/changelog | 8 
 debian/control   | 3 ++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index fb23164..f32c51c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+g810-led (0.3.3-2) unstable; urgency=medium
+
+  * The development package needs to depend on the library package, add
+the appropriate dependency. Closes: #924191 (thanks to Andreas
+Beckmann).
+
+ -- Stephen Kitt   Sun, 10 Mar 2019 18:55:30 +0100
+
 g810-led (0.3.3-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 5232232..70a32a2 100644
--- a/debian/control
+++ b/debian/control
@@ -44,7 +44,8 @@ Package: libg810-led-dev
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: libg810-led0 (= ${binary:Version}),
+ ${shlibs:Depends}, ${misc:Depends}
 Description: Logitech keyboard LED configuration library (development)
  g810-led is a configuration tool for the LEDs on Logitech Gx10 gaming
  keyboards: G213, G410, G413, G512, G513, G610, G810, G910, and G Pro.
-- 
2.11.0



unblock g810-led/0.3.3-2

Thanks,

Stephen


-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
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)

Bug#892214: unblock: rocksndiamonds/4.0.1.3+dfsg-1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

rocksndiamonds currently has a manual block in Adam’s hints file,
related to #879667 which caused the package to end up in main and
contrib. The package has been rebuilt since (a binNMU first, and a
recent source upload), and rmadison tells me the current version is
only in contrib.

Would it be possible to lift the block?

Thanks,

Stephen

Bug#864236: unblock: wput/0.6.2+git20130413-5

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Sorry for leaving this to the last minute, but I’m wondering if the
lack of TLS support due to a missing build-dep qualifies as a security
fix.  If it does, please unblock package wput; the diff against the
version in testing is

diff --git a/debian/changelog b/debian/changelog
index befb782..133714f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+wput (0.6.2+git20130413-5) unstable; urgency=medium
+
+  * Actually build with TLS support (LP: #1678463).
+
+ -- Stephen Kitt <sk...@debian.org>  Mon, 05 Jun 2017 16:39:05 +0200
+
 wput (0.6.2+git20130413-4) unstable; urgency=medium
 
   * Switch to https: VCS URIs (see #810378).
diff --git a/debian/control b/debian/control
index f03e232..bdcfcda 100644
--- a/debian/control
+++ b/debian/control
@@ -3,6 +3,7 @@ Maintainer: Stephen Kitt <sk...@debian.org>
 Section: web
 Priority: optional
 Build-Depends: debhelper (>= 9),
+   libgcrypt20-dev,
libgnutls-openssl-dev,
autotools-dev
 Standards-Version: 3.9.8


unblock wput/0.6.2+git20130413-5

Regards,

Stephen

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200, 
'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#858780: unblock: lgogdownloader/3.1-2 (pre-upload request)

[Stephen Kitt]

Control: tag -1 - moreinfo

On Wed, 05 Apr 2017 06:38:00 +, Niels Thykier <ni...@thykier.net> wrote:
> Stephen Kitt:
> > unblock lgogdownloader/3.1-2
> > [...]  
> Ack, please go ahead.

Uploaded, thanks! (And I fixed the version in the unblock above.)

Regards,

Stephen


pgpmNfKrd0ZMh.pgp
Description: OpenPGP digital signature

Bug#858780: unblock: lgogdownloader/3.1-1 (pre-upload request)

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

This is a pre-upload unblock request for lgogdownloader. The version
currently in Stretch (and unstable) has a nasty bug (#857691) which
can make the whole package unusable in certain circumstances —
basically, lgogdownloader crashes with user accounts containing
downloadable content for games that the account doesn't own (which can
happen unfortunately).

Upstream have released a fix for this, and Simon McVittie has pushed
it to the package VCS. The resulting diff, were I to upload the
package to unstable, would be

diff --git a/debian/changelog b/debian/changelog
index bfbc456..9b5a3c4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+lgogdownloader (3.1-2) unstable; urgency=medium
+
+  [ Simon McVittie ]
+  * Team upload
+  * Backport patch from 3.2 fixing the ability to list games if a game
+has {'updates': null} (Closes: #857691)
+
+ -- Stephen Kitt <sk...@debian.org>  Sun, 26 Mar 2017 18:58:18 +0200
+
 lgogdownloader (3.1-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/patches/Fix-crash-in-Website-getGames.patch 
b/debian/patches/Fix-crash-in-Website-getGames.patch
new file mode 100644
index 000..a689162
--- /dev/null
+++ b/debian/patches/Fix-crash-in-Website-getGames.patch
@@ -0,0 +1,49 @@
+From: Sude <lgogdownloa...@gmail.com>
+Date: Fri, 20 Jan 2017 00:15:50 +0200
+Subject: Fix crash in Website::getGames
+
+JSON value for updates can be null in some cases. For example when user owns a 
dlc but not the base game.
+This caused a crash due to std::stoi throwing std::invalid_argument exception
+
+Origin: upstream, 3.2, commit:22f47de4fcd8cd7ecc2a89fbb25f94efb1b3f743
+---
+ src/website.cpp | 26 +-
+ 1 file changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/src/website.cpp b/src/website.cpp
+index 0803432..8ca4c8c 100644
+--- a/src/website.cpp
 b/src/website.cpp
+@@ -163,7 +163,31 @@ std::vector Website::getGames()
+ gameItem game;
+ game.name = product["slug"].asString();
+ game.id = product["id"].isInt() ? 
std::to_string(product["id"].asInt()) : product["id"].asString();
+-game.updates = product["updates"].isInt() ? 
product["updates"].asInt() : std::stoi(product["updates"].asString());
++
++if (product.isMember("updates"))
++{
++if (product["updates"].isNull())
++{
++/* In some cases the value can be null.
++ * For example when user owns a dlc but not the base 
game
++ * https://github.com/Sude-/lgogdownloader/issues/101
++ * Assume that there are no updates in this case */
++game.updates = 0;
++}
++else if (product["updates"].isInt())
++game.updates = product["updates"].asInt();
++else
++{
++try
++{
++game.updates = 
std::stoi(product["updates"].asString());
++}
++catch (std::invalid_argument& e)
++{
++game.updates = 0; // Assume no updates
++}
++}
++}
+ 
+ unsigned int platform = 0;
+ if (product["worksOn"]["Windows"].asBool())
diff --git a/debian/patches/series b/debian/patches/series
index 48af9e8..69eb314 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
+Fix-crash-in-Website-getGames.patch
 manpage-whatis.patch


Is this OK?

unblock lgogdownloader/3.1-1

Regards,

Stephen


-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#849567: nmu: gdb-mingw-w64_10.4

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

Please binNMU gdb-mingw-w64 now that gdb 7.12 is in testing:

nmu gdb-mingw-w64_10.4 . ANY . unstable . -m "Rebuild using gdb 7.12."

Thanks,

Stephen


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#833377: release.debian.org: boost1.61 transition

[Stephen Kitt]

Hi Emilio,

On Wed, Aug 03, 2016 at 07:10:03PM +0200, Emilio Pozuelo Monfort wrote:
> On 03/08/16 18:02, Dimitri John Ledkov wrote:
> > The abi is complex and depends on multiple things. We do not wish to
> > maintain same boost series (1.61) with multiple abi builds. Due to fixes
> > to the c++11 inline namespace abi tags in gcc-6 (as compared to gcc-5)
> > the ABI of boost-regexp changes when compiled with gcc-6.
> 
> Hmm, can you clarify this? I wasn't aware that rebuilding with g++-6 caused 
> ABI
> changes. Do you know if this affects other libraries? Surely we can workaround
> it in boost by doing the 1.61 transition at the same time, but what about 
> other
> libraries?

I get the impression virtual functions are handled differently. For
example, in htmlcxx (https://bugs.debian.org/811964), virtual
destructors used to result in symbols attached to the declaring class
(HTML::Exception::~Exception()), but with GCC 6 they result in symbols
attached to the concrete classes (Uri::Exception::~Exception()).

Regards,

Stephen (not a C++ expert)


signature.asc
Description: PGP signature

Bug#808845: nmu: gdb-mingw-w64_10.1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

I'd appreciate it if you could binNMU gdb-mingw-w64:

nmu gdb-mingw-w64_10.1 . ANY . unstable . -m "Rebuild with gdb 7.10."

Regards,

Stephen

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#807506: nmu: gcc-mingw-w64_16

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

Would it be possible to binNMU gcc-mingw-w64?

nmu gcc-mingw-w64_16 . ANY . unstable . -m "Rebuild with gcc-5 5.3.1-3."

Thanks in advance,

Stephen

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#807505: nmu: binutils-mingw-w64_6.5

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

Would it be possible to binNMU binutils-mingw-w64?

nmu binutils-mingw-w64_6.5 . ANY . unstable . -m "Rebuild with binutils 
2.25.90.20151209-1."

Thanks in advance,

Stephen

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#797316: nmu: binutils-mingw-w64_6.2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

Would it be possible to binNMU binutils-mingw-w64 to rebuild with the
new binutils 2.25.1?

nmu binutils-mingw-w64_6.2 . ALL . unstable . -m Rebuild with binutils 2.25.1.

Thanks in advance,

Stephen

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#787867: jessie-pu: package binutils-mingw-w64/5.2

[Stephen Kitt]

On Wed, 26 Aug 2015 21:59:36 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Fri, 2015-06-05 at 22:33 +0200, Stephen Kitt wrote:
  binutils-mingw-w64/5.2 in Jessie suffers from #787162: ld breaks with
  DLLs and libraries built with Visual Studio. This makes the mingw-w64
  toolchain in Jessie effectively useless for people working with such
  files.
  
  The attached patch fixes this (as has been confirmed by #787162's
  submitter). It's the upstream patch which is included in newer
  versions of binutils and is already available in Stretch.
 
 Please go ahead.

Done, thanks!

Regards,

Stephen


pgpY2nl5xXScs.pgp
Description: OpenPGP digital signature

Bug#787867: jessie-pu: package binutils-mingw-w64/5.2

[Stephen Kitt]

On Fri, 05 Jun 2015 22:33:15 +0200, Stephen Kitt sk...@debian.org wrote:
 binutils-mingw-w64/5.2 in Jessie suffers from #787162: ld breaks with
 DLLs and libraries built with Visual Studio. This makes the mingw-w64
 toolchain in Jessie effectively useless for people working with such
 files.
 
 The attached patch fixes this (as has been confirmed by #787162's
 submitter). It's the upstream patch which is included in newer
 versions of binutils and is already available in Stretch.
 
 Would it be OK to upload a fixed version of binutils-mingw-w64 to
 stable-proposed-updates?

Ping?

Regards,

Stephen


pgpI67ovI968d.pgp
Description: OpenPGP digital signature

Bug#791070: htmlcxx: library transition may be needed when GCC 5 is the default

[Stephen Kitt]

Hi Simon,

On Fri, 14 Aug 2015 10:21:20 +0100, Simon McVittie s...@debian.org wrote:
 On Fri, 07 Aug 2015 at 21:55:53 +0200, Stephen Kitt wrote:
  Some of the changed symbols are part of the API. I'm attaching a patch
  which allows the package to build, at least on amd64, and implements
  the transition as described above.
 
 My understanding is that this is OK to upload to unstable as per
 https://lists.debian.org/debian-release/2015/08/msg00426.html;
 and since your patch fixes a bug that has been RC for  7 days
 without maintainer response, you don't necessarily need to use a
 delayed queue either.
 
 I can NMU this for you if needed, but since you prepared the patch
 and you maintain the only reverse dependency, perhaps it's better if
 you do it.

Thanks for the info, I'll upload an NMU in the near future.

Regards,

Stephen


pgplG94OPBiSi.pgp
Description: OpenPGP digital signature

Bug#787867: jessie-pu: package binutils-mingw-w64/5.2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi,

binutils-mingw-w64/5.2 in Jessie suffers from #787162: ld breaks with
DLLs and libraries built with Visual Studio. This makes the mingw-w64
toolchain in Jessie effectively useless for people working with such
files.

The attached patch fixes this (as has been confirmed by #787162's
submitter). It's the upstream patch which is included in newer
versions of binutils and is already available in Stretch.

Would it be OK to upload a fixed version of binutils-mingw-w64 to
stable-proposed-updates?

Regards,

Stephen

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 3ea00d4..7c2f748 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+binutils-mingw-w64 (5.2+deb8u1) stable; urgency=medium
+
+  * Apply upstream fix to handle Visual Studio DLLs (Closes: #787162).
+
+ -- Stephen Kitt sk...@debian.org  Thu, 04 Jun 2015 07:17:38 +0200
+
 binutils-mingw-w64 (5.2) unstable; urgency=high
 
   * Rebuild against binutils 2.24.90.20141023-1 or later to fix
diff --git a/debian/patches/handle-visual-studio-dlls.patch b/debian/patches/handle-visual-studio-dlls.patch
new file mode 100644
index 000..fafcdab
--- /dev/null
+++ b/debian/patches/handle-visual-studio-dlls.patch
@@ -0,0 +1,31 @@
+From cdb602b17548eeebb5e700c507d734ea5f887a49 Mon Sep 17 00:00:00 2001
+From: Nick Clifton ni...@redhat.com
+Date: Fri, 27 Feb 2015 15:38:32 +
+Subject: [PATCH 1/1] Fixes a problem recognizing libraries created by Visual
+ Studio.
+
+	PR binutils/17910
+	* coffgen.c (_bfd_coff_internal_syment_name): Only check for
+	string length overflow when the string table length is actually
+	set.
+---
+
+diff --git a/bfd/coffgen.c b/bfd/coffgen.c
+index aa01559..83673d4 100644
+--- a/bfd/coffgen.c
 b/bfd/coffgen.c
+@@ -468,7 +468,10 @@ _bfd_coff_internal_syment_name (bfd *abfd,
+ 	  if (strings == NULL)
+ 	return NULL;
+ 	}
+-  if (sym-_n._n_n._n_offset = obj_coff_strings_len (abfd))
++  /* PR 17910: Only check for string overflow if the length has been set.
++	 Some DLLs, eg those produced by Visual Studio, may not set the length field.  */
++  if (obj_coff_strings_len (abfd)  0
++	   sym-_n._n_n._n_offset = obj_coff_strings_len (abfd))
+ 	return NULL;
+   return strings + sym-_n._n_n._n_offset;
+ }
+-- 
+1.9.4
+
diff --git a/debian/rules b/debian/rules
index 50ea330..0bee1e9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -32,6 +32,8 @@ unpack-stamp:
 	# Patch the testsuite (if necessary)
 	patch -d $(upstream_dir) -N -p2  debian/patches/testsuite-64-bit.patch || true
 	patch -d $(upstream_dir) -N -p2  debian/patches/testsuite-timeout.patch || true
+	# Handle Visual Studio DLLs (#787162, upstream PR binutils/17910)
+	patch -d $(upstream_dir) -p1  debian/patches/handle-visual-studio-dlls.patch
 	# On big-endian architectures, disable the windres tests (#754829)
 	if [ $$(dpkg-architecture -qDEB_HOST_ARCH_ENDIAN) = big ]; then \
 		rm -f $(upstream_dir)/binutils/testsuite/binutils-all/windres/windres.exp; \

Bug#783675: nmu: gcc-mingw-w64_15.1 and gnat-mingw-w64_15

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

The isl transition needs rebuilds of gcc-mingw-w64 and gnat-mingw-w64;
binNMUs are sufficient. Could the following be queued?

nmu gcc-mingw-w64_15.1 . ALL . -m Rebuild with isl 0.14.
nmu gnat-mingw-w64_15 . ALL . -m Rebuild with isl 0.14.

Thanks in advance,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429051629.9504.63930.report...@heffalump.sk2.org

Bug#779959: unblock: binutils-mingw-w64/5.2 (pre-upload)

[Stephen Kitt]

Control: tags -1 - moreinfo

On Sat, 7 Mar 2015 09:19:34 +0100, Ivo De Decker iv...@debian.org wrote:
 On Fri, Mar 06, 2015 at 09:35:54PM +0100, Stephen Kitt wrote:
  I would like to update binutils-mingw-w64, to rebuild against binutils
  2.25 with the security fixes for DSA-2013. The debdiff is as follows:
 
 Please go ahead and remove the moreinfo tag from this bug once the upload is
 in unstable.

Done, thanks!

Stephen


pgpMGW4PtdoPc.pgp
Description: OpenPGP digital signature

Bug#779959: unblock: binutils-mingw-w64/5.2 (pre-upload)

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

I would like to update binutils-mingw-w64, to rebuild against binutils
2.25 with the security fixes for DSA-2013. The debdiff is as follows:

diff --git a/debian/changelog b/debian/changelog
index ae48239..3ea00d4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+binutils-mingw-w64 (5.2) unstable; urgency=high
+
+  * Rebuild against binutils 2.24.90.20141023-1 or later to fix
+CVE-2014-8484, CVE-2014-8485, CVE-2014-8501, CVE-2014-8502,
+CVE-2014-8503, CVE-2014-8504, CVE-2014-8737, CVE-2014-8738 (Closes:
+#775165).
+
+ -- Stephen Kitt sk...@debian.org  Mon, 12 Jan 2015 22:32:41 +0100
+
 binutils-mingw-w64 (5.1) unstable; urgency=medium
 
   * Increase the testsuite timeout (the build fails on mipsel otherwise).
diff --git a/debian/control b/debian/control
index 823521d..e90012a 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: binutils-mingw-w64
 Section: devel
 Priority: extra
 Maintainer: Stephen Kitt sk...@debian.org
-Build-Depends: debhelper (= 7.0.50~), autotools-dev, binutils-source (= 
2.22), bison, flex, dejagnu
+Build-Depends: debhelper (= 7.0.50~), autotools-dev, binutils-source (= 
2.24.90.20141023-1), bison, flex, dejagnu
 Standards-Version: 3.9.5
 Homepage: http://www.gnu.org/software/binutils/
 Vcs-Git: git://anonscm.debian.org/collab-maint/binutils-mingw-w64.git


unblock binutils-mingw-w64/5.2

Regards,

Stephen

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150306203554.21635.87314.report...@heffalump.sk2.org

Bug#775665: unblock: mail-notification/5.4.dfsg.1-13

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package mail-notification 5.4.dfsg.1-13, which fixes
FTBFS #775620. The debdiff is as follows:

diff -Nru mail-notification-5.4.dfsg.1/debian/changelog 
mail-notification-5.4.dfsg.1/debian/changelog
--- mail-notification-5.4.dfsg.1/debian/changelog   2014-06-29 
19:14:36.0 +0200
+++ mail-notification-5.4.dfsg.1/debian/changelog   2015-01-18 
11:39:39.0 +0100
@@ -1,3 +1,9 @@
+mail-notification (5.4.dfsg.1-13) unstable; urgency=medium
+
+  * Build-depend on libebook1.2-dev (closes: #775620).
+
+ -- Stephen Kitt sk...@debian.org  Sun, 18 Jan 2015 11:39:34 +0100
+
 mail-notification (5.4.dfsg.1-12) unstable; urgency=medium
 
   * Merge patch from Ubuntu to stop linking with bsd-compat, which is no
diff -Nru mail-notification-5.4.dfsg.1/debian/control 
mail-notification-5.4.dfsg.1/debian/control
--- mail-notification-5.4.dfsg.1/debian/control 2014-04-11 06:53:04.0 
+0200
+++ mail-notification-5.4.dfsg.1/debian/control 2015-01-18 11:37:42.0 
+0100
@@ -12,6 +12,7 @@
gob2 (= 2.0.16),
intltool (= 0.35),
libdbus-glib-1-dev,
+   libebook1.2-dev,
libecal1.2-dev,
libgmime-2.6-dev,
libgnome-keyring-dev,


unblock mail-notification/5.4.dfsg.1-13

Thanks,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150118105236.15602.66957.report...@heffalump.sk2.org

Bug#775309: nmu: binutils-mingw-w64_5.1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

My earlier binNMU in wheezy-security wasn't appropriate, but
binutils-mingw-w64 still needs fixing in jessie and sid, and I'm
wondering whether to do sourceful uploads or request binNMUs.

If binNMUs are OK, there won't be any trouble with inappropriate
versions of binutils-source ending up being used in jessie; otherwise
I suppose I'll need to do a source upload to jessie-p-u (so it picks
up binutils 2.24.90.20141023-1 from jessie) as well as sid (which will
pick up binutils 2.25-3)...

nmu binutils-mingw-w64_5.1 . ALL . -m Rebuild for DSA-2013-2 (CVE-2014-8484, 
CVE-2014-8485, CVE-2014-8501, CVE-2014-8502, CVE-2014-8503, CVE-2014-8504, 
CVE-2014-8737, CVE-2014-8738).
nmu binutils-mingw-w64_5.1 . ALL . jessie-proposed-updates . -m Rebuild for 
DSA-2013-2 (CVE-2014-8484, CVE-2014-8485, CVE-2014-8501, CVE-2014-8502, 
CVE-2014-8503, CVE-2014-8504, CVE-2014-8737, CVE-2014-8738).

Regards,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150113220130.8629.6603.report...@heffalump.sk2.org

Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)

[Stephen Kitt]

Le 12/01/2015 08:15, Adam D. Barratt a écrit :

On Mon, 2015-01-12 at 06:47 +0100, Stephen Kitt wrote:

binutils was recently updated in wheezy-security and wheezy-p-u to fix
a number of security issues identified in DSA-3123-1; of these, a
number concern binutils-mingw-w64 as well, so it would be great if it
could be rebuilt in those suites... (It will pick up the patches from
binutils-source.)


We won't schedule binNMUs in -security for packages that DSAs haven't
been issued for, at least not without the security team's request /
agreement - it's just going to confuse everyone.


Right, I should have mentioned that Michael Gilbert suggested I file 
this after I asked what I should do about the DSA. I've asked the 
security team to confirm this request.


nmu binutils-mingw-w64_2 . ALL . -m Rebuild for DSA-3123-1 
(CVE-2014-8501, CVE-2014-8502, CVE-2014-8737, CVE-2014-8738).


For suites other than unstable, the suite name needs to be specified in
the call (the above will simply fail, as wanna-build won't find the
specified version in unstable).


Indeed, sorry about that:

nmu binutils-mingw-w64_2 . ALL . wheezy-proposed-updates . -m Rebuild 
for DSA-3123-1 (CVE-2014-8501, CVE-2014-8502, CVE-2014-8737, 
CVE-2014-8738).
nmu binutils-mingw-w64_2 . ALL . wheezy-security . -m Rebuild for 
DSA-3123-1 (CVE-2014-8501, CVE-2014-8502, CVE-2014-8737, 
CVE-2014-8738).


Regards,

Stephen


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/a428ebeb148799d27d20d73d579c7...@sk2.org

Bug#775165: DSA 3123-1 affects other binutils-derived packages

[Stephen Kitt]

Hi Michael,

Le 12/01/2015 04:21, Michael Gilbert a écrit :

On Sun, Jan 11, 2015 at 9:39 AM, Stephen Kitt wrote:
Is there any handling of Built-Using-marked packages by the security 
team, or

is it up to the affected maintainers to keep an eye on things?


It's not automated at all, so you'll need to ask the release team for a 
binnmu.


OK, I've filed this as #775165 but it needs an acknowledgement from the 
security team.



It would be useful for there to be automation, but someone would need
to take an interest in that.


Something to add to the endless to-do list ;-).

Thanks,

Stephen


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/c63a7a8826b1cd89694efd4ba6ba8...@sk2.org

Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)

[Stephen Kitt]

Hi Thijs,

On Mon, 12 Jan 2015 21:13:02 +0100, Thijs Kinkhorst th...@debian.org
wrote:
 On Mon, January 12, 2015 20:18, Ansgar Burchardt wrote:
  Note that the archive requires the source package to already be in the
  target suite (or a base suite in case of overlays like p-u or
  experimental). In particular this means you cannot schedule binNMUs for
  the security archive for source packages not present there.
 
 Thanks for the explanation. I'll add it to our documentation.
 
 Stephen: the last sentence makes it clear that we'll need a sourceful
 upload to security-master. Can you arrange for that?

Indeed, I'll do that within the next two-three hours.

Regards,

Stephen


pgpBI04muATbk.pgp
Description: OpenPGP digital signature

Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

binutils was recently updated in wheezy-security and wheezy-p-u to fix
a number of security issues identified in DSA-3123-1; of these, a
number concern binutils-mingw-w64 as well, so it would be great if it
could be rebuilt in those suites... (It will pick up the patches from
binutils-source.)

nmu binutils-mingw-w64_2 . ALL . -m Rebuild for DSA-3123-1 (CVE-2014-8501, 
CVE-2014-8502, CVE-2014-8737, CVE-2014-8738).

Thanks,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150112054703.31088.30314.report...@heffalump.sk2.org

Bug#773972: please binNMU packages to build with binutils 2.25

[Stephen Kitt]

Hi Matthias and the release team,

On Fri, 26 Dec 2014 14:58:26 +0100, Matthias Klose d...@debian.org wrote:
 please binNMU the following packages to build with binutils (= 2.25-3).
 
 ggcov, tulip, lush, binutils-arm-none-eabi, binutils-mingw-w64,
 binutils-z80, cross-binutils, openbios, openhackware.
 
 I'm unsure about binutils-mingw-w64. Stephen said that this package would
 require a sourceful upload.

Did I? Never mind, I just rebuilt binutils-mingw-w64 as-is in unstable and it
built fine, so a binNMU would be OK.

Regards,

Stephen


pgpS54r1See9a.pgp
Description: OpenPGP digital signature

Bug#773490: (pre-upload) unblock: gcc-mingw-w64/14.3

[Stephen Kitt]

Hi Jonathan,

On Fri, 19 Dec 2014 18:37:19 +, Jonathan Wiltshire j...@debian.org wrote:
 On Fri, Dec 19, 2014 at 12:39:56AM +0100, Stephen Kitt wrote:
  I would like to know if the following changes to gcc-mingw-w64 would
  be acceptable for Jessie, before uploading the package to unstable;
  they fix #773342, a serious bug filed against mingw32 (upgrading from
  Wheezy causes the package to lose its copyright file).
 
 Yes, with a small query:
 
  --- a/debian/rules
  +++ b/debian/rules
  @@ -254,6 +254,9 @@ binary-indep: build-indep
  dh_link -i
  dh_compress -i
  dh_fixperms -i
  +# This is the first version where we fix up the /usr/share/doc/mingw32 link
  +# Once this is in the archive we'll switch to a first_split_version-style 
  approach
  +   echo dir_to_symlink /usr/share/doc/mingw32 
  /usr/share/doc/gcc-mingw-w64-base $(deb_version)~ mingw32  
  debian/mingw32.maintscript
  dh_installdeb -i
 
 Is there a reason for not just creating debian/migw32.maintscript in the
 package? Why generate it as part of the build?

I generate it during the build because I don't know before then what version
I'll end up with (in Debian and in derivatives); the binary version is
generated using the version of gcc-4.9-source used for the build as well as
the version of gcc-mingw-w64. For the upload after this one I'll take into
account the version that actually ended up being used and do something more
permanent based on that.

Is that a valid reason?

One side-effect of this is that an upload to unstable right now would build
binary packages with a 4.9.2-8+14.3 version (except on mipsel which would get
4.9.2-5+14.3), so that mingw32 package would specify 4.9.2-8+14.3~ as the
version before which the directory-to-symlink transition needs handled;
whereas an upload to t-p-u would build 4.9.1-19+14.3 and specify
4.9.1-19+14.3~. I'm not worried about this for two reasons:
dpkg-maintscript-helper handles this well, and mingw32 will be dropped after
Jessie anyway.

  Note that this package builds using gcc-4.9-source, and allowing it to
  transition from unstable to Jessie would effectively mean pulling
  unstable's gcc-4.9 source into Jessie too. If necessary I can upload
  to unstable and upload again to t-p-u once the unstable package has
  aged enough.
 
 Let's go with your second plan please - fix in unstable and then upload to
 t-p-u later.

OK, thanks!

Regards,

Stephen


pgphAuXrh5O4v.pgp
Description: OpenPGP digital signature

Bug#773490: (pre-upload) unblock: gcc-mingw-w64/14.3

[Stephen Kitt]

Control: tag -1 - moreinfo

On Fri, 19 Dec 2014 19:51:25 +, Jonathan Wiltshire j...@debian.org wrote:
 You know what, we might as well skip unstable. Feel free to go ahead to
 t-p-u on the basis of the submitted patch, and remove the moreinfo tag.

Done, thanks!

Regards,

Stephen


pgp0hiIU5pLHm.pgp
Description: OpenPGP digital signature

Bug#773490: (pre-upload) unblock: gcc-mingw-w64/14.3

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I would like to know if the following changes to gcc-mingw-w64 would
be acceptable for Jessie, before uploading the package to unstable;
they fix #773342, a serious bug filed against mingw32 (upgrading from
Wheezy causes the package to lose its copyright file).

The debdiff is as follows:

diff --git a/debian/changelog b/debian/changelog
index 66f2f44..0a80887 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gcc-mingw-w64 (14.3) unstable; urgency=medium
+
+  * Properly replace /usr/share/doc/mingw32 with a symlink to
+/usr/share/doc/gcc-mingw-w64-base (Closes: #773342).
+
+ -- Stephen Kitt sk...@debian.org  Thu, 18 Dec 2014 07:23:13 +0100
+
 gcc-mingw-w64 (14.2) unstable; urgency=medium
 
   * Ensure README.Debian is installed in gcc-mingw-w64-base (Closes:
diff --git a/debian/control b/debian/control
index fa12406..9dda194 100644
--- a/debian/control
+++ b/debian/control
@@ -263,6 +263,7 @@ Description: GNU Compiler Collection for MinGW-w64 (base 
package)
 
 Package: mingw32
 Architecture: all
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, gcc-mingw-w64-i686, g++-mingw-w64-i686, 
mingw32-binutils
 Built-Using: gcc-4.9 (= ${gcc:Version})
 Description: Minimalist GNU win32 (cross) compiler (transition package)
diff --git a/debian/control.mingw32 b/debian/control.mingw32
index ac89b60..e0d93fa 100644
--- a/debian/control.mingw32
+++ b/debian/control.mingw32
@@ -1,5 +1,6 @@
 Package: mingw32
 Architecture: all
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, gcc-mingw-w64-i686, g++-mingw-w64-i686, 
mingw32-binutils
 Built-Using: gcc-4.9 (= ${gcc:Version})
 Description: Minimalist GNU win32 (cross) compiler (transition package)
diff --git a/debian/rules b/debian/rules
index 38a3782..4370d66 100755
--- a/debian/rules
+++ b/debian/rules
@@ -254,6 +254,9 @@ binary-indep: build-indep
dh_link -i
dh_compress -i
dh_fixperms -i
+# This is the first version where we fix up the /usr/share/doc/mingw32 link
+# Once this is in the archive we'll switch to a first_split_version-style 
approach
+   echo dir_to_symlink /usr/share/doc/mingw32 
/usr/share/doc/gcc-mingw-w64-base $(deb_version)~ mingw32  
debian/mingw32.maintscript
dh_installdeb -i
dh_gencontrol -i -- -v$(deb_version) 
-Vlocal:Version=$(deb_upstream_version) -Vgcc:Version=$(source_version) 
-Vsplit:Version=$(first_split_version)
dh_md5sums -i



Note that this package builds using gcc-4.9-source, and allowing it to
transition from unstable to Jessie would effectively mean pulling
unstable's gcc-4.9 source into Jessie too. If necessary I can upload
to unstable and upload again to t-p-u once the unstable package has
aged enough.

unblock gcc-mingw-w64/14.3

Regards,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141218233956.4841.86311.report...@heffalump.sk2.org

Bug#773314: nmu: gcc-mingw-w64_14.2 and gnat-mingw-w64_14

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

Matthias tells me he's planning on requesting a freeze exception for
gcc-4.9 4.9.2. If you grant his request, would it be at all possible
to rebuild gcc-mingw-w64? That would cause it to rebuild with the
then-current version of gcc-4.9 (so it should be done when gcc-4.9 has
the same version in unstable and testing...).

gnat-mingw-w64 is simply a split of gcc-mingw-w64 and should be
rebuilt at the same time.

nmu gcc-mingw-w64_14.2 . ALL . -m Rebuild with gcc 4.9.2.
nmu gnat-mingw-w64_14 . ALL . -m Rebuild with gcc 4.9.2.

Regards,

Stephen


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141216184439.24096.41205.report...@heffalump.sk2.org

Bug#771014: unblock: libevdev/1.3+dfsg-2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear releast team,

Please unblock package libevdev, which fixes the important Multi-Arch
bug #770294. The debdiff against version 1.3+dfsg-1 in testing is as
follows:

diff --git a/debian/changelog b/debian/changelog
index dd33877..edba505 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libevdev (1.3+dfsg-2) unstable; urgency=medium
+
+  * Mark libevdev2 as Multi-Arch: same (Closes: #770294); thanks to
+Andreas Beckmann for pointing out the issue!
+
+ -- Stephen Kitt sk...@debian.org  Tue, 25 Nov 2014 23:23:54 +0100
+
 libevdev (1.3+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 64dad28..da0ddfd 100644
--- a/debian/control
+++ b/debian/control
@@ -32,6 +32,7 @@ Description: wrapper library for evdev devices - development 
files
 
 Package: libevdev2
 Architecture: linux-any
+Multi-Arch: same
 Pre-Depends:
  ${misc:Pre-Depends}
 Depends:



unblock libevdev/1.3+dfsg-2

Thanks in advance,

Stephen

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141125224341.14403.13456.report...@heffalump.sk2.org

Bug#767430: Pre-upload unblock request: solaar/0.9.2+dfsg-4

[Stephen Kitt]

Hi Niels,

On Fri, 31 Oct 2014 07:34:23 +0100, Niels Thykier ni...@thykier.net wrote:
 On 2014-10-31 00:24, Stephen Kitt wrote:
  Package: release.debian.org
  Severity: normal
  User: release.debian@packages.debian.org
  Usertags: unblock
  
  Dear release team,
  
  The localisation teams have provided me with updated debconf templates
  for solaar, and the Portuguese team have even provided a full
  translation for the upstream binary. Would this be suitable for a
  Jessie unblock? I'm attaching the full patch, with important elements
  detailed as follows:
  
  [...]
  
  unblock solaar/0.9.2+dfsg-4
  
  (I haven't uploaded this to unstable yet; I'm waiting to find out if
  everything here is suitable.)
 
 I am happy to accept the presented debdiff via unstable at this point in
 the freeze.  Please upload it to unstable and let us know when it has
 been accepted.

Thanks, I've uploaded it and it's been accepted into unstable.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#767430: Pre-upload unblock request: solaar/0.9.2+dfsg-4

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

The localisation teams have provided me with updated debconf templates
for solaar, and the Portuguese team have even provided a full
translation for the upstream binary. Would this be suitable for a
Jessie unblock? I'm attaching the full patch, with important elements
detailed as follows:

$ git diff --stat debian/0.9.2+dfsg-3 
 debian/changelog|  21 ++
 debian/control  |  16 +-
 debian/patches/series   |   1 +
 debian/patches/translation-pt.patch | 482 
 debian/po/cs.po |  75 +
 debian/po/da.po |  76 +
 debian/po/de.po |  76 +
 debian/po/en.po |  70 ++--
 debian/po/fr.po |  79 +
 debian/po/it.po | 120 +++
 debian/po/nl.po |  86 +
 debian/po/pt.po |  80 +
 debian/po/pt_BR.po  |  77 +
 debian/po/ru.po |  79 +
 debian/po/templates.pot |  41 +--
 debian/rules|   1 +
 debian/solaar.templates |  39 ++-
 17 files changed, 1354 insertions(+), 65 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 2fa424f..2c62bd1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,24 @@
+solaar (0.9.2+dfsg-4) unstable; urgency=low
+
+  [ Stephen Kitt ]
+  * Add Portuguese translation (closes: #761589).
+
+  [ Christian Perrier ]
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project. Closes: #761939
+  * [Debconf translation updates]
+  * Russian (Yuri Kozlov).  Closes: #764788
+  * Italian (Beatrice Torracca).  Closes: #764939
+  * Danish (Joe Hansen).  Closes: #764964
+  * German (Chris Leick).  Closes: #765927
+  * Dutch; (Frans Spiesschaert).  Closes: #766057
+  * Portuguese (Paulo Tomé).  Closes: #766589
+  * Czech (Michal Simunek).  Closes: #766592
+  * Brazilian Portuguese (Adriano Rafael Gomes).  Closes: #766602
+  * French (Jean-Pierre Giraud).  Closes: #766722
+
+ -- Stephen Kitt sk...@debian.org  Wed, 29 Oct 2014 20:37:13 +0100
+
 solaar (0.9.2+dfsg-3) unstable; urgency=medium
 
   * According to the included meta-data, the SVG files are licensed
diff --git a/debian/control b/debian/control
index bbc1f14..e6bc4b7 100644
--- a/debian/control
+++ b/debian/control
@@ -20,9 +20,9 @@ Recommends: gir1.2-notify-0.7, consolekit (= 0.4.3) | 
systemd (= 44),
  python-dbus (= 1.1.0), upower
 Suggests: gir1.2-appindicator3-0.1, solaar-gnome3 (= ${source:Version})
 Description: Logitech Unifying Receiver peripherals manager for Linux
- Solaar is a Linux device manager for Logitech's Unifying Receiver peripherals.
- It is able to pair/unpair devices to the receiver, and for some devices read
- battery status.
+ Solaar is a Linux device manager for Logitech's Unifying Receiver wireless
+ peripherals. It is able to pair/unpair devices to the receiver, and for
+ some devices to read battery status.
 
 Package: solaar-gnome3
 Architecture: all
@@ -31,9 +31,9 @@ Depends: ${misc:Depends}, solaar (= ${source:Version}),
  gir1.2-appindicator3-0.1, gnome-shell (= 3.4) | unity (= 5.10),
  ${solaar:Gnome-Icon-Theme}
 Enhances: solaar
-Description: gnome-shell/Unity integration for Solaar
- Solaar is a Linux device manager for Logitech's Unifying Receiver peripherals.
- It is able to pair/unpair devices to the receiver, and for some devices read
- battery status.
+Description: GNOME Shell/Unity integration for Solaar
+ Solaar is a Linux device manager for Logitech's Unifying Receiver wireless
+ peripherals. It is able to pair/unpair devices to the receiver, and for
+ some devices to read battery status.
  .
- This metapackage ensures integration with gnome-shell/Unity.
+ This metapackage ensures integration with GNOME Shell/Unity.
diff --git a/debian/rules b/debian/rules
index 3c127b6..2526e9c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,6 +18,7 @@ override_dh_auto_build:
 
 override_dh_auto_clean:
./tools/clean.sh
+   debconf-updatepo
dh_auto_clean
 
 override_dh_auto_install:



unblock solaar/0.9.2+dfsg-4

(I haven't uploaded this to unstable yet; I'm waiting to find out if
everything here is suitable.)

Regards,

Stephen


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 2fa424f..2c62bd1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,24 @@
+solaar (0.9.2+dfsg

Bug#725154: pu: package oss-compat/2

[Stephen Kitt]

On Mon, 22 Sep 2014 23:53:32 +0200, Stephen Kitt sk...@debian.org wrote:
 On Mon, 22 Sep 2014 22:49:52 +0100, Adam D. Barratt
 a...@adam-barratt.org.uk wrote:
  On Sat, 2014-09-20 at 19:08 +0100, Adam D. Barratt wrote:
   Apologies for the long delay in getting back to you.
   
   On Wed, 2013-10-02 at 22:59 +0200, Stephen Kitt wrote:
On Wed, 02 Oct 2013 20:29:00 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Wed, 2013-10-02 at 07:52 +0200, Stephen Kitt wrote:
  oss-compat in stable suffers from two serious bugs:
* 660803, related to changes in kmod (and causing issues when
  installing Debian Edu wheezy);
* 718241, which was initially just a tracking bug for testing
  but also applies to wheezy.
  [...]
   Removing your own conffiles is icky, but I don't have any better
   solutions. Please go ahead, thanks.
  
  This was uploaded and I've flagged it for acceptance.
 
 Thanks!

And I still managed to mess this up :-(. The following patch fixes #762547
which was just filed against stable:

diff --git a/debian/changelog b/debian/changelog
index 57a79dd..c4b4e51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+oss-compat (2+deb7u2) wheezy; urgency=medium
+
+  * Give the correct destination when copying the new configuration
+file. (Closes: #762547.)
+
+ -- Stephen Kitt sk...@debian.org  Tue, 23 Sep 2014 10:40:38 +0200
+
 oss-compat (2+deb7u1) wheezy; urgency=low
 
   * Use softdep directives in the modprobe configuration. (Closes:
diff --git a/debian/postinst b/debian/postinst
index c129818..bd98468 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -33,7 +33,7 @@ case $1 in
 # Cleanup stable configuration link
 [ -L ${oldconffile} ]  rm -f ${oldconffile}
 # Wheezy configuration file (using install directives)
-[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 
88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux ${conffile}
+[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 
88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux ${curconffile}
 
 if lsmod | grep -q ^snd  ; then
   modprobe snd || true


Is it OK if I upload this?

Sorry about that,

Stephen


signature.asc
Description: PGP signature

Bug#725154: pu: package oss-compat/2

[Stephen Kitt]

On Tue, 23 Sep 2014 10:02:18 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On 2014-09-23 9:43, Stephen Kitt wrote:
  And I still managed to mess this up :-(. The following patch fixes 
  #762547
  which was just filed against stable:
 [...]
  Is it OK if I upload this?
 
 Please go ahead.

Done, thanks.

Stephen


signature.asc
Description: PGP signature

Bug#725154: pu: package oss-compat/2

[Stephen Kitt]

On Mon, 22 Sep 2014 22:49:52 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Sat, 2014-09-20 at 19:08 +0100, Adam D. Barratt wrote:
  Apologies for the long delay in getting back to you.
  
  On Wed, 2013-10-02 at 22:59 +0200, Stephen Kitt wrote:
   On Wed, 02 Oct 2013 20:29:00 +0100, Adam D. Barratt
   a...@adam-barratt.org.uk wrote:
On Wed, 2013-10-02 at 07:52 +0200, Stephen Kitt wrote:
 oss-compat in stable suffers from two serious bugs:
   * 660803, related to changes in kmod (and causing issues when
 installing Debian Edu wheezy);
   * 718241, which was initially just a tracking bug for testing but
 also applies to wheezy.
 [...]
  Removing your own conffiles is icky, but I don't have any better
  solutions. Please go ahead, thanks.
 
 This was uploaded and I've flagged it for acceptance.

Thanks!

Stephen


signature.asc
Description: PGP signature

Bug#732219: transition: libmikmod

[Stephen Kitt]

On Wed, 26 Mar 2014 00:18:39 +0100, Julien Cristau jcris...@debian.org
wrote:
 On Tue, Mar 25, 2014 at 23:27:33 +0100, Stephen Kitt wrote:
  On Tue, 18 Mar 2014 23:23:06 +0100, Stephen Kitt sk...@debian.org wrote:
   On Tue, 18 Mar 2014 07:57:06 +0100, Julien Cristau jcris...@debian.org
   wrote:
Thanks.  Feel free to upload to sid.
   
   Done, thanks.
  
  And the whole transition is over, thanks!
  
 Not quite.  tome/powerpc still depends on libmikmod2 (#742598).

Oops, I forgot to check non-free... Oh well. You'll know better than me what
should be done with this bug (re-open or leave closed), I'll leave it to you
if you don't mind...

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#732219: transition: libmikmod

[Stephen Kitt]

On Tue, 18 Mar 2014 07:57:06 +0100, Julien Cristau jcris...@debian.org
wrote:
 Thanks.  Feel free to upload to sid.

Done, thanks.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#732219: transition: libmikmod

[Stephen Kitt]

On Mon, 17 Mar 2014 09:46:59 +0100, Julien Cristau jcris...@debian.org
wrote:
 On Mon, Mar 17, 2014 at 00:15:18 +0100, Stephen Kitt wrote:
  I've made libmikmod-dev provide libmikmod2-dev in 3.3.5-2 and uploaded it
  to experimental. Should I file bugs (with patches...) for heroes and
  sdl-mixer1.2 now?
  
 Yes please.  Make them block this bug.

Done for sdl-mixer1.2 (#741986); heroes wasn't actually supposed to use
mikmod any more, and is orphaned, so I did a QA upload of it (also fixing a
couple of other bugs).

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#732219: transition: libmikmod

[Stephen Kitt]

Hi Julien,

On Sun, 16 Mar 2014 19:05:33 +0100, Julien Cristau jcris...@debian.org
wrote:
 On Sun, Dec 15, 2013 at 20:07:03 +0100, Stephen Kitt wrote:
  libmikmod changed its soname from 2 to 3, so upgrading it requires a
  transition. Unfortunately the current -dev package is versioned
  (libmikmod2-dev), so transitioning the reverse dependencies requires
  source changes. To avoid this in the future the new libmikmod source
  package builds libmikmod3 and libmikmod-dev.
  
 Please either build a libmikmod2-dev transitional package from the new
 version, or make libmikmod-dev provide libmikmod2-dev.  The latter would
 mean only heroes and sdl-mixer1.2 need source changes.

I've made libmikmod-dev provide libmikmod2-dev in 3.3.5-2 and uploaded it to
experimental. Should I file bugs (with patches...) for heroes and
sdl-mixer1.2 now?

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#740015: nmu: gcc-mingw-w64_12+exp1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

I'm not sure experimental binNMUs are appropriate, but if so I'd
appreciate a rebuild of gcc-mingw-w64 12+exp1 with gcc 4.9-20140218.

Thanks in advance,

Stephen


nmu gcc-mingw-w64_12+exp1 . ALL . -m Rebuild with gcc 4.9-20140218.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20140224233318.25912.71709.report...@heffalump.sk2.org

Bug#732219: transition: libmikmod

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

libmikmod changed its soname from 2 to 3, so upgrading it requires a
transition. Unfortunately the current -dev package is versioned
(libmikmod2-dev), so transitioning the reverse dependencies requires
source changes. To avoid this in the future the new libmikmod source
package builds libmikmod3 and libmikmod-dev.

The affected reverse dependencies are:
* alsaplayer-common
* bb
* gweled
* libclanapp-1.0
* libsdl-mixer1.2
* libsdl-sound1.2
* mikmod
* mpd
* tecnoballz
* uqm
* vavoom
* xscorch

All the affected source packages rebuild fine with a simple
s/libmikmod2-dev/libmikmod-dev/g in most cases. libsdl-mixer1.2 is a
little more complicated because libsdl-mixer1.2-dev depends on
libmikmod2-dev, so that needs changed too, and tecnoballz must wait
for that change before being rebuilt since it build-depends on both
libmikmod2-dev and libsdl-mixer1.2-dev.

Ben file:

title = libmikmod;
is_affected = .depends ~ libmikmod2 | .depends ~ libmikmod3;
is_good = .depends ~ libmikmod3;
is_bad = .depends ~ libmikmod2;


Regards,

Stephen


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131215190703.1167.22826.report...@heffalump.sk2.org

Bug#732219: transition: libmikmod

[Stephen Kitt]

Hi,

On Sun, 15 Dec 2013 20:07:03 +0100, Stephen Kitt sk...@debian.org wrote:
 libmikmod changed its soname from 2 to 3, so upgrading it requires a
 transition. Unfortunately the current -dev package is versioned
 (libmikmod2-dev), so transitioning the reverse dependencies requires
 source changes. To avoid this in the future the new libmikmod source
 package builds libmikmod3 and libmikmod-dev.

I forgot to mention that the updated package is in experimental and I'll be
uploading mikmod there too shortly.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#725154: pu: package oss-compat/2

[Stephen Kitt]

On Wed, 02 Oct 2013 20:29:00 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Wed, 2013-10-02 at 07:52 +0200, Stephen Kitt wrote:
  oss-compat in stable suffers from two serious bugs:
* 660803, related to changes in kmod (and causing issues when
  installing Debian Edu wheezy);
* 718241, which was initially just a tracking bug for testing but
  also applies to wheezy.
 
 --- a/debian/postinst
 +++ b/debian/postinst
 @@ -32,6 +32,8 @@ case $1 in
  fi
  # Cleanup stable configuration link
  [ -L ${oldconffile} ]  rm -f ${oldconffile}
 +# Wheezy configuration file (using install directives)
 +[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\ -f1) 
 = 88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux $
 
 Copy and paste failure?

Oh dear, thanks for catching that, let me get my brown paper bag...

I'm attaching the correct patch.

Regards,

Stephen
diff --git a/debian/changelog b/debian/changelog
index 533343f..57a79dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+oss-compat (2+deb7u1) wheezy; urgency=low
+
+  * Use softdep directives in the modprobe configuration. (Closes:
+#660803.)
+  * Remove oss-compat.conf when removing the package, so it doesn't load
+the OSS modules when configured but not installed. (Closes: #718241.)
+
+ -- Stephen Kitt sk...@debian.org  Wed, 02 Oct 2013 07:30:56 +0200
+
 oss-compat (2) unstable; urgency=low
 
   [ Stephen Kitt ]
diff --git a/debian/postinst b/debian/postinst
index e0fe783..c129818 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -32,6 +32,8 @@ case $1 in
 fi
 # Cleanup stable configuration link
 [ -L ${oldconffile} ]  rm -f ${oldconffile}
+# Wheezy configuration file (using install directives)
+[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux ${conffile}
 
 if lsmod | grep -q ^snd  ; then
   modprobe snd || true
diff --git a/debian/prerm b/debian/prerm
new file mode 100644
index 000..3cb73d4
--- /dev/null
+++ b/debian/prerm
@@ -0,0 +1,26 @@
+#!/bin/sh
+set -e
+
+case $1 in
+remove)
+	conffile=/etc/modprobe.d/oss-compat.conf
+	# If the installed file matches a known version, remove it
+	if [ -f ${conffile} ]; then
+	md5sum=$(md5sum ${conffile} | cut -d\  -f1)
+	# Wheezy version
+	md5wheezy=88222606b0a3ba8b0825c5000c754e6f
+	# Jessie version
+	md5jessie=cb772524a069ec273d7ca6db520388c1
+	if [ ${md5sum} = ${md5wheezy} -o ${md5sum} = ${md5jessie} ]; then
+		rm -f /etc/modprobe.d/oss-compat.conf
+	fi
+	fi
+	;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
diff --git a/linux b/linux
index 98c8b57..d24b108 100644
--- a/linux
+++ b/linux
@@ -1,3 +1,3 @@
-install snd-pcm modprobe --ignore-install snd-pcm $CMDLINE_OPTS  { modprobe --quiet snd-pcm-oss ; : ; }
-install snd-mixer modprobe --ignore-install snd-mixer $CMDLINE_OPTS  { modprobe --quiet snd-mixer-oss ; : ; }
-install snd-seq modprobe --ignore-install snd-seq $CMDLINE_OPTS  { modprobe --quiet snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
+softdep snd-pcm post: snd-pcm-oss
+softdep snd-mixer post: snd-mixer-oss
+softdep snd-seq post: snd-seq-midi snd-seq-oss


signature.asc
Description: PGP signature

Bug#725154: pu: package oss-compat/2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu

Hi,

oss-compat in stable suffers from two serious bugs:
  * 660803, related to changes in kmod (and causing issues when
installing Debian Edu wheezy);
  * 718241, which was initially just a tracking bug for testing but
also applies to wheezy.

The latter bug doesn't contain much rationale; basically the issue is
that oss-compat installs modprobe configuration to load OSS modules
automatically, and since this takes the form of a configuration file,
the modules are still loaded even when oss-compat is removed (but not
purged). This is undesirable in and of itself, but it also complicates
for future upgrades: anything causing an automatic removal of
oss-compat will be broken if it requires the modules not to load
(cf. osspd which now provides oss-compat; I'd like oss-compat in
jessie to recommend osspd).

The attached patch fixes these two bugs in wheezy in the same way as
in jessie; the relevant versions of the package have been in jessie
for a while.

Regards,

Stephen


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 533343f..57a79dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+oss-compat (2+deb7u1) wheezy; urgency=low
+
+  * Use softdep directives in the modprobe configuration. (Closes:
+#660803.)
+  * Remove oss-compat.conf when removing the package, so it doesn't load
+the OSS modules when configured but not installed. (Closes: #718241.)
+
+ -- Stephen Kitt sk...@debian.org  Wed, 02 Oct 2013 07:30:56 +0200
+
 oss-compat (2) unstable; urgency=low
 
   [ Stephen Kitt ]
diff --git a/debian/postinst b/debian/postinst
index e0fe783..ca1d9b5 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -32,6 +32,8 @@ case $1 in
 fi
 # Cleanup stable configuration link
 [ -L ${oldconffile} ]  rm -f ${oldconffile}
+# Wheezy configuration file (using install directives)
+[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux $
 
 if lsmod | grep -q ^snd  ; then
   modprobe snd || true
diff --git a/debian/prerm b/debian/prerm
new file mode 100644
index 000..3cb73d4
--- /dev/null
+++ b/debian/prerm
@@ -0,0 +1,26 @@
+#!/bin/sh
+set -e
+
+case $1 in
+remove)
+	conffile=/etc/modprobe.d/oss-compat.conf
+	# If the installed file matches a known version, remove it
+	if [ -f ${conffile} ]; then
+	md5sum=$(md5sum ${conffile} | cut -d\  -f1)
+	# Wheezy version
+	md5wheezy=88222606b0a3ba8b0825c5000c754e6f
+	# Jessie version
+	md5jessie=cb772524a069ec273d7ca6db520388c1
+	if [ ${md5sum} = ${md5wheezy} -o ${md5sum} = ${md5jessie} ]; then
+		rm -f /etc/modprobe.d/oss-compat.conf
+	fi
+	fi
+	;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
diff --git a/linux b/linux
index 98c8b57..d24b108 100644
--- a/linux
+++ b/linux
@@ -1,3 +1,3 @@
-install snd-pcm modprobe --ignore-install snd-pcm $CMDLINE_OPTS  { modprobe --quiet snd-pcm-oss ; : ; }
-install snd-mixer modprobe --ignore-install snd-mixer $CMDLINE_OPTS  { modprobe --quiet snd-mixer-oss ; : ; }
-install snd-seq modprobe --ignore-install snd-seq $CMDLINE_OPTS  { modprobe --quiet snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
+softdep snd-pcm post: snd-pcm-oss
+softdep snd-mixer post: snd-mixer-oss
+softdep snd-seq post: snd-seq-midi snd-seq-oss

Bug#725050: nmu: mail-notification_5.4.dfsg.1-8+b1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

mail-notification's last binNMU (for the Evolution 3.8 transition)
pulled in libgmime-2.6-dev 2.6.17-1, and the resulting package built
without GMime support thanks to #722609, because gmime-2.6.pc couldn't
be found (yay for configuration systems which build in spite of
missing build-dependencies).

I'd appreciate a binNMU now that the gmime bug is fixed!

nmu mail-notification_5.4.dfsg.1-8+b1 . ALL . -m Rebuild using fixed 
libgmime-2.6-dev.

Thanks in advance,

Stephen


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130930210848.4977.77149.report...@heffalump.sk2.org

Bug#702406: nmu: binutils-mingw-w64_2 to pick up fix for #688951

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

binutils recently added a fix for #688951 (CVE-2012-3509) which also
affects binutils-mingw-w64. The following binNMU will cause the fix to
be applied to binutils-mingw-w64:

nmu binutils-mingw-w64_2 . ALL . -m Rebuild against new binutils to pick up 
fix for #688951. Closes: #702402.

Thanks,

Stephen


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130306065219.14732.25641.report...@heffalump.sk2.org

Bug#699395: unblock: mednafen/0.8.D.3-6

[Stephen Kitt]

On Mon, 18 Feb 2013 18:44:12 +, Jonathan Wiltshire j...@debian.org wrote:
 On Thu, Jan 31, 2013 at 12:09:20AM +0100, Stephen Kitt wrote:
  Would it be possible to unblock mednafen? It fixes #699143 which I
  consider important (I replaced the version of libvorbisidec provided
  in the mednafen source code with a dependency on libvorbisidec-dev in
  Debian, but it doesn't work for audio CD playback).
 
 Unblocked. Please ensure the security team is aware of the embedded library
 (they may already be).

Thanks! I notified the security team at the end of January, and the
information has been added to
http://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=markup

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#699395: unblock: mednafen/0.8.D.3-6

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

Would it be possible to unblock mednafen? It fixes #699143 which I
consider important (I replaced the version of libvorbisidec provided
in the mednafen source code with a dependency on libvorbisidec-dev in
Debian, but it doesn't work for audio CD playback).

The debdiff is as follows:


diff -Nru mednafen-0.8.D.3/debian/changelog mednafen-0.8.D.3/debian/changelog
--- mednafen-0.8.D.3/debian/changelog   2012-06-18 01:01:23.0 +0200
+++ mednafen-0.8.D.3/debian/changelog   2013-01-29 23:41:52.0 +0100
@@ -1,3 +1,10 @@
+mednafen (0.8.D.3-6) unstable; urgency=low
+
+  * Build using the provided libvorbisidec source; mednafen doesn't work
+correctly with the version currently in Debian (closes: #699143).
+
+ -- Stephen Kitt st...@sk2.org  Tue, 29 Jan 2013 23:40:10 +0100
+
 mednafen (0.8.D.3-5) unstable; urgency=low
 
   * Use ${source:Package} with dpkg-query to retrieve only the package
diff -Nru mednafen-0.8.D.3/debian/patches/series 
mednafen-0.8.D.3/debian/patches/series
--- mednafen-0.8.D.3/debian/patches/series  2012-06-17 23:16:13.0 
+0200
+++ mednafen-0.8.D.3/debian/patches/series  2013-01-29 23:38:48.0 
+0100
@@ -1,3 +1,2 @@
-use-system-tremor.patch
 hardening-fixes.patch
 zlib-1.2.6-fix.patch
diff -Nru mednafen-0.8.D.3/debian/rules mednafen-0.8.D.3/debian/rules
--- mednafen-0.8.D.3/debian/rules   2012-06-17 23:16:13.0 +0200
+++ mednafen-0.8.D.3/debian/rules   2013-01-29 23:39:07.0 +0100
@@ -18,9 +18,6 @@
cp src/compress/minilzo.h src/compress/minilzo.h.orig
cp /usr/share/lzo/minilzo/*.[ch] src/compress
 
-   # Move bundled source code for external packages out of the way
-   mv src/tremor src/tremor.orig
-
dh_auto_build
 
 override_dh_auto_clean:
@@ -30,9 +27,6 @@
[ ! -f src/compress/minilzo.c.orig ] || mv src/compress/minilzo.c.orig 
src/compress/minilzo.c
[ ! -f src/compress/minilzo.h.orig ] || mv src/compress/minilzo.h.orig 
src/compress/minilzo.h
 
-   # Restore bundled source code
-   [ ! -d src/tremor.orig ] || mv src/tremor.orig src/tremor
-
dh_auto_clean
 
 override_dh_auto_configure:



unblock mednafen/0.8.D.3-6

Thanks in advance,

Stephen


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130130230920.821.93788.report...@heffalump.sk2.org

Bug#686547: unblock: calibre/0.8.64+dfsg-1

[Stephen Kitt]

On Fri, 18 Jan 2013 20:49:44 +, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Thu, 2013-01-17 at 00:22 +0100, Stephen Kitt wrote:
  And after discussion with Christian and -devel/-mentors, the updated
  package is available at
  http://www.sk2.org/calibre/calibre_0.8.51+dfsg1-0.1.dsc with the same
  contents, packaged as version 0.8.51+dfsg1-0.1 (what a surprise!).
 
 Assuming that the debdiff is (modulo the version number) the same as
 that in MID:20130109224238.ga20...@sk2.org, please go ahead; thanks.

It is indeed, thanks.

Christian, can you sponsor the upload?

Thanks,

Stephen


signature.asc
Description: PGP signature

Bug#686547: unblock: calibre/0.8.64+dfsg-1

[Stephen Kitt]

On Wed, 9 Jan 2013 23:42:38 +0100, Stephen Kitt st...@sk2.org wrote:
 On Wed, Dec 19, 2012 at 07:40:04PM +, Adam D. Barratt wrote:
  Anyone any interest in preparing a t-p-u for that?
 
 I've prepared a t-p-u candidate with all the above, based on Arno's
 previous t-p-u candidate. I just pulled in the fixes for #678686 and
 #674838 as applied by Martin in later versions of the package.
 
 Everything's available on http://www.sk2.org/calibre/ with the dsc at
 http://www.sk2.org/calibre/calibre_0.8.51+dfsg+wheezy1-1.1.dsc - I'm
 not (yet) a DD so I'd need a sponsor (Christian?) if the release team
 are OK with the package.

And after discussion with Christian and -devel/-mentors, the updated package
is available at http://www.sk2.org/calibre/calibre_0.8.51+dfsg1-0.1.dsc with
the same contents, packaged as version 0.8.51+dfsg1-0.1 (what a surprise!).

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#686547: unblock: calibre/0.8.64+dfsg-1

[Stephen Kitt]

Hi,

(Christian, I came across this while looking for RC bugs as part of my
TS.)

On Wed, Dec 19, 2012 at 07:40:04PM +, Adam D. Barratt wrote:
 On Wed, 2012-10-31 at 16:34 +0100, intrigeri wrote:
  Julien Cristau wrote (30 Sep 2012 13:10:55 GMT) :
   3) upload to tpu a fix for whatever issues are serious enough, not just
   #653328.
  
  Apart of #653328, only bugs of severity normal or minor were fixed
  since 0.8.51+dfsg-1.
  
  However, the fixes for #678686 (typo in package description) and
  #674838 (fonts-liberation path changed and the symbolic link is
  broken) look trivial, harmless, and useful enough to be worth
  including in Wheezy at this point.
  = Julien's third alternative makes sense to me.
 
 Anyone any interest in preparing a t-p-u for that?

I've prepared a t-p-u candidate with all the above, based on Arno's
previous t-p-u candidate. I just pulled in the fixes for #678686 and
#674838 as applied by Martin in later versions of the package.

Everything's available on http://www.sk2.org/calibre/ with the dsc at
http://www.sk2.org/calibre/calibre_0.8.51+dfsg+wheezy1-1.1.dsc - I'm
not (yet) a DD so I'd need a sponsor (Christian?) if the release team
are OK with the package.

The changelog is as follows:

calibre (0.8.51+dfsg+wheezy1-1.1) testing-proposed-updates; urgency=low

  * Non-maintainer upload.
  
  [ Arno Töll ]
  * Remove quick_start.epub from the tarball, do not install said file to the
calibre binary package. See #653328 for background. Upstream version
0.8.64 includes this file with a changed license again, so no change is
needed with respect to Debian. (Closes: #653328)
  
  [ Martin Pitt ]
  * debian/control: Fix upports typo. (Closes: #678686)
  * debian/control, debian/rules: ttf-liberation is no more, move to
fonts-liberation. Thanks to Kan-Ru Chen! (Closes: #674838)

 -- Stephen Kitt st...@sk2.org  Wed, 09 Jan 2013 08:12:30 +0100


The debdiff against the package in testing is as follows:

diff -Nru calibre-0.8.51+dfsg/debian/calibre.README.Debian 
calibre-0.8.51+dfsg+wheezy1/debian/calibre.README.Debian
--- calibre-0.8.51+dfsg/debian/calibre.README.Debian2012-05-14 
12:13:47.0 +0200
+++ calibre-0.8.51+dfsg+wheezy1/debian/calibre.README.Debian2013-01-09 
23:25:50.0 +0100
@@ -4,7 +4,7 @@
 Customizing LRF fonts
 -
 By default, the calibre package maps the LRF standard fonts to the the
-free Liberation fonts (package ttf-liberation):
+free Liberation fonts (package fonts-liberation):
 
   Swis721 BT Roman - LiberationSans-Regular.ttf
   Dutch801 Rm BT Roman - LiberationSerif-Regular.ttf
diff -Nru calibre-0.8.51+dfsg/debian/changelog 
calibre-0.8.51+dfsg+wheezy1/debian/changelog
--- calibre-0.8.51+dfsg/debian/changelog2012-05-14 12:13:47.0 
+0200
+++ calibre-0.8.51+dfsg+wheezy1/debian/changelog2013-01-09 
08:13:42.0 +0100
@@ -1,3 +1,20 @@
+calibre (0.8.51+dfsg+wheezy1-1.1) testing-proposed-updates; urgency=low
+
+  * Non-maintainer upload.
+  
+  [ Arno Töll ]
+  * Remove quick_start.epub from the tarball, do not install said file to the
+calibre binary package. See #653328 for background. Upstream version
+0.8.64 includes this file with a changed license again, so no change is
+needed with respect to Debian. (Closes: #653328)
+  
+  [ Martin Pitt ]
+  * debian/control: Fix upports typo. (Closes: #678686)
+  * debian/control, debian/rules: ttf-liberation is no more, move to
+fonts-liberation. Thanks to Kan-Ru Chen! (Closes: #674838)
+
+ -- Stephen Kitt st...@sk2.org  Wed, 09 Jan 2013 08:12:30 +0100
+
 calibre (0.8.51+dfsg-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru calibre-0.8.51+dfsg/debian/control 
calibre-0.8.51+dfsg+wheezy1/debian/control
--- calibre-0.8.51+dfsg/debian/control  2012-05-14 12:13:47.0 +0200
+++ calibre-0.8.51+dfsg+wheezy1/debian/control  2013-01-09 08:11:24.0 
+0100
@@ -57,7 +57,7 @@
  xdg-utils, 
  imagemagick,
  poppler-utils,
- ttf-liberation,
+ fonts-liberation,
  calibre-bin (= ${source:Version}),
  ${misc:Depends}
 Recommends: python-dnspython
@@ -107,7 +107,7 @@
  Calibre is primarily an e-book cataloging program. It manages your e-book
  collection for you. It is designed around the concept of the logical book,
  i.e. a single entry in the database that may correspond to e-books in several
- formats. It also upports conversion from a dozen different e-book formats to
+ formats. It also supports conversion from a dozen different e-book formats to
  LRF and EPUB. A graphical interface to the conversion software can be
  accessed easily by just clicking the Convert E-books button.
  .
diff -Nru calibre-0.8.51+dfsg/debian/rules 
calibre-0.8.51+dfsg+wheezy1/debian/rules
--- calibre-0.8.51+dfsg/debian/rules2012-05-14 12:13:47.0 +0200
+++ calibre-0.8.51+dfsg+wheezy1/debian/rules2013-01-09 08:11:56.0 
+0100
@@ -42,9 +42,9 @@
# remove hardcoded prs500 fonts, so that calibre

Re: Bug#690810: Pre-upload unblock approval: gcc-mingw-w64/8

[Stephen Kitt]

Hi,

On Wed, 17 Oct 2012 22:25:27 +0200, Stephen Kitt st...@sk2.org wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@packages.debian.org
 Usertags: unblock
 
 Hi,
 
 I've prepared a new version of gcc-mingw-w64, fixing the RC bug
 #690148 (/usr/share/doc/gcc-mingw32 used to be a directory but is now
 a symlink). While I'm at it I'd also like to add symlinks to the
 gcc-mingw32 package to fully replace the version in Squeeze, which
 would also fix #682257 (gcc-mingw32 provides i586-mingw32msvc-g++ but
 not amd64-mingw32msvc-g++).
 
 Would the added symlinks be acceptable for Wheezy, or should I limit
 myself to fixing the RC bug? The attached debdiff contains all the
 changes I have planned; the RC bug fix is in gcc-mingw32.postinst.

I don't want to badger anyone, but... Ping? (See
http://bugs.debian.org/690810 obviously for the debdiff.)

Thanks,

Stephen


signature.asc
Description: PGP signature

Bug#690810: Pre-upload unblock approval: gcc-mingw-w64/8

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I've prepared a new version of gcc-mingw-w64, fixing the RC bug
#690148 (/usr/share/doc/gcc-mingw32 used to be a directory but is now
a symlink). While I'm at it I'd also like to add symlinks to the
gcc-mingw32 package to fully replace the version in Squeeze, which
would also fix #682257 (gcc-mingw32 provides i586-mingw32msvc-g++ but
not amd64-mingw32msvc-g++).

Would the added symlinks be acceptable for Wheezy, or should I limit
myself to fixing the RC bug? The attached debdiff contains all the
changes I have planned; the RC bug fix is in gcc-mingw32.postinst.

Thanks in advance,

Stephen

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru gcc-mingw-w64-7/debian/changelog gcc-mingw-w64-8/debian/changelog
--- gcc-mingw-w64-7/debian/changelog	2012-08-08 08:21:59.0 +0200
+++ gcc-mingw-w64-8/debian/changelog	2012-10-17 07:49:17.0 +0200
@@ -1,3 +1,13 @@
+gcc-mingw-w64 (8) unstable; urgency=low
+
+  * Replace /usr/share/doc/gcc-mingw32 with a symlink when necessary
+(Closes: #690148).
+  * Provide amd64 compatibility symlinks in gcc-mingw32, preserving the
+functionality of the Squeeze version; add g++ compatibility symlink
+(Closes: #682257).
+
+ -- Stephen Kitt st...@sk2.org  Wed, 17 Oct 2012 07:49:14 +0200
+
 gcc-mingw-w64 (7) unstable; urgency=low
 
   * When upgrading from versions where /usr/share/doc/gcc-mingw-w64 is a
diff -Nru gcc-mingw-w64-7/debian/control gcc-mingw-w64-8/debian/control
--- gcc-mingw-w64-7/debian/control	2012-08-08 08:25:36.0 +0200
+++ gcc-mingw-w64-8/debian/control	2012-10-17 07:54:13.0 +0200
@@ -298,9 +298,13 @@
 Package: gcc-mingw32
 Architecture: all
 Depends: binutils-mingw-w64-i686,
+ binutils-mingw-w64-x86-64,
  gcc-mingw-w64-i686,
+ gcc-mingw-w64-x86-64,
  g++-mingw-w64-i686,
+ g++-mingw-w64-x86-64,
  gfortran-mingw-w64-i686,
+ gfortran-mingw-w64-x86-64,
  ${misc:Depends}
 Built-Using: gcc-4.6 (= ${gcc:Version})
 Conflicts: mingw32-binutils
@@ -310,9 +314,9 @@
  the GNU Compiler Collection (gcc).
  .
  This transition package replaces the old gcc-4.4.4-based gcc-mingw32
- package and allows building software using the old i586-mingw32msvc
- triplet. It also includes compatibility symlinks for i586-mingw32msvc
- binutils binaries.
+ package and allows building software using the amd64-mingw32msvc and
+ i586-mingw32msvc triplets. It also includes compatibility symlinks
+ for amd64-mingw32msvc and i586-mingw32msvc binutils binaries.
 
 Package: gcc-mingw-w64-base
 Architecture: any
diff -Nru gcc-mingw-w64-7/debian/control.gcc-mingw32 gcc-mingw-w64-8/debian/control.gcc-mingw32
--- gcc-mingw-w64-7/debian/control.gcc-mingw32	2012-08-08 08:15:05.0 +0200
+++ gcc-mingw-w64-8/debian/control.gcc-mingw32	2012-10-17 07:45:01.0 +0200
@@ -1,9 +1,13 @@
 Package: gcc-mingw32
 Architecture: all
 Depends: binutils-mingw-w64-i686,
+ binutils-mingw-w64-x86-64,
  gcc-mingw-w64-i686,
+ gcc-mingw-w64-x86-64,
  g++-mingw-w64-i686,
+ g++-mingw-w64-x86-64,
  gfortran-mingw-w64-i686,
+ gfortran-mingw-w64-x86-64,
  ${misc:Depends}
 Built-Using: gcc-4.6 (= ${gcc:Version})
 Conflicts: mingw32-binutils
@@ -13,6 +17,6 @@
  the GNU Compiler Collection (gcc).
  .
  This transition package replaces the old gcc-4.4.4-based gcc-mingw32
- package and allows building software using the old i586-mingw32msvc
- triplet. It also includes compatibility symlinks for i586-mingw32msvc
- binutils binaries.
+ package and allows building software using the amd64-mingw32msvc and
+ i586-mingw32msvc triplets. It also includes compatibility symlinks
+ for amd64-mingw32msvc and i586-mingw32msvc binutils binaries.
diff -Nru gcc-mingw-w64-7/debian/gcc-mingw32.links gcc-mingw-w64-8/debian/gcc-mingw32.links
--- gcc-mingw-w64-7/debian/gcc-mingw32.links	2012-07-02 19:55:06.0 +0200
+++ gcc-mingw-w64-8/debian/gcc-mingw32.links	2012-10-17 07:37:21.0 +0200
@@ -1,17 +1,17 @@
 usr/bin/i686-w64-mingw32-addr2line usr/bin/i586-mingw32msvc-addr2line
 usr/bin/i686-w64-mingw32-ar usr/bin/i586-mingw32msvc-ar
 usr/bin/i686-w64-mingw32-as usr/bin/i586-mingw32msvc-as
-usr/bin/i686-w64-mingw32-c++ usr/bin/i586-mingw32msvc-c++
-usr/bin/i686-w64-mingw32-gcc usr/bin/i586-mingw32msvc-cc
 usr/bin/i686-w64-mingw32-c++filt usr/bin/i586-mingw32msvc-c++filt
 usr/bin/i686-w64-mingw32-cpp usr/bin/i586-mingw32msvc-cpp
+usr/bin/i686-w64-mingw32-c++ usr/bin/i586-mingw32msvc-c++
 usr/bin/i686-w64-mingw32-dlltool usr/bin/i586-mingw32msvc-dlltool
 usr/bin/i686-w64

Re: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)

[Stephen Kitt]

On Mon, 15 Oct 2012 15:13:58 +0200, Philipp Kern pk...@debian.org wrote:
 On Mon, Oct 15, 2012 at 01:33:16AM +0200, Cyril Brulebois wrote:
  Stephen Kitt st...@sk2.org (14/10/2012):
   Now that gcc-4.6 4.6.3-12 is installed in unstable on all
   architectures, would it be possible to give gcc-mingw-w64 back on
   all buildds? This will cause it to be rebuilt using gcc-4.6
   4.6.3-12; since the latter's version ends up in the resulting binary
   packages' versions, a binNMU shouldn't be necessary...
   
 gb gcc-mingw-w64_7 . ALL
  a package which failed to build can be given back. That's really an
  alias for “please give it another chance to build (successfully)”. If
  you want to get a(n already successfully built) package rebuilt
  against a new set of packages, that's where binNMUs come into play.
 
 And if would've been cool if you could send a rationale for why the binNMU
 is needed (I simply don't know why one has to recompile against a new gcc,
 and there's no bug# reference) to debian-release@lists.d.o (Cc'ed).
 
 (binNMUs migrate automatically if present, hence it's also slightly relevant
 for wheezy release management.)

Thanks for all the info everyone! Had I known a binNMU was the appropriate
solution I would of course have filed a bug using reportbug with a
rationale...

Basically Matthias Klose asked me to update gcc-mingw-w64 to the latest
version of gcc-4.6 which fixes the kfreebsd-amd64 build bug (#637236). This
would also give us all the fixes in gcc-4.6 since the last gcc-mingw-w64
build (4.6.3-8), updates which warranted a freeze exception for gcc-4.6
(4.6.3-11 at least).

As Jonathan pointed out, there's an RC bug against gcc-mingw-w64 (#690148),
which I wasn't aware of because it got sent to the previous maintainer. I'll
fix that and do a sourceful upload.

Regards,

Stephen


signature.asc
Description: PGP signature

Re: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)

[Stephen Kitt]

Hi Jonathan,

On Mon, 15 Oct 2012 14:49:31 +0100, Jonathan Wiltshire j...@debian.org wrote:
 Surely it would be more efficient to do a maintainer upload fixing RC
 bug #690148, and you'll get the rebuilds for free?
 
 I started looking at this bug yesterday, the fix is easy but I did not
 have time to check all binary packages. Patch to follow if you want it.

If you've got the patch to hand I'd appreciate it. As you say the fix is
easy, but I won't have time to work on it this evening...

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#685478: unblock: gcc-mingw-w64/8

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package gcc-mingw-w64; the version in unstable fixes a
release-critical bug causing /usr/share/doc/gcc-mingw-w64 to be empty
when upgrading from versions before it became a symlink.

The package is over ten days old but hasn't build on kfreebsd-amd64 or
mips yet; I've asked for a giveback on the former (the build failure
is due to #637236 on gcc-4.6; repeating the build produces a correct
build eventually) and pinged the buildd admins concerning the latter.

The debdiff is as follows:

diff -Nru gcc-mingw-w64-6/debian/changelog gcc-mingw-w64-7/debian/changelog
--- gcc-mingw-w64-6/debian/changelog2012-05-05 18:31:42.0 +0200
+++ gcc-mingw-w64-7/debian/changelog2012-08-08 08:21:59.0 +0200
@@ -1,3 +1,10 @@
+gcc-mingw-w64 (7) unstable; urgency=low
+
+  * When upgrading from versions where /usr/share/doc/gcc-mingw-w64 is a
+directory, force its replacement with a symlink (Closes: #683617).
+
+ -- Stephen Kitt st...@sk2.org  Wed, 08 Aug 2012 08:21:56 +0200
+
 gcc-mingw-w64 (6) unstable; urgency=low
 
   * Handle the different split-package versions in Ubuntu and Debian.
diff -Nru gcc-mingw-w64-6/debian/gcc-mingw-w64.postinst 
gcc-mingw-w64-7/debian/gcc-mingw-w64.postinst
--- gcc-mingw-w64-6/debian/gcc-mingw-w64.postinst   1970-01-01 
01:00:00.0 +0100
+++ gcc-mingw-w64-7/debian/gcc-mingw-w64.postinst   2012-08-08 
08:10:09.0 +0200
@@ -0,0 +1,13 @@
+#!/bin/sh
+set -e
+
+# Replace documentation directory with symlink
+if [ -d /usr/share/doc/gcc-mingw-w64 ]  [ ! -L /usr/share/doc/gcc-mingw-w64 
]; then
+if rmdir /usr/share/doc/gcc-mingw-w64 2/dev/null; then
+ln -sf gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64
+fi
+fi
+
+#DEBHELPER#
+
+exit 0


unblock gcc-mingw-w64/8

Thanks,

Stephen


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)
Foreign Architectures: mingw64-i386

Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120821064246.26529.29529.report...@heffalump.sk2.org

Bug#685478: unblock: gcc-mingw-w64/8

[Stephen Kitt]

retitle 685478 unblock: gcc-mingw-w64/7
thanks

On Tue, 21 Aug 2012 08:42:46 +0200, Stephen Kitt st...@sk2.org wrote:
 unblock gcc-mingw-w64/8

Of course that's

unblock gcc-mingw-w64/7

Regards,

Stephen


signature.asc
Description: PGP signature

Re: Freeze exception for binutils-mingw-w64 (helps fix RC #662746)

[Stephen Kitt]

Hi KiBi,

On Sun, 8 Jul 2012 23:49:15 +0200, Cyril Brulebois k...@debian.org wrote:
 Stephen Kitt st...@sk2.org (05/07/2012):
  Just to clarify, this is a pre-upload request...
 
 yeah, it looks possible to install all 3 packages + the
 conflicted-against package in wheezy without apparent issues.
 
 Please upload to unstable and ping again once that's done.

Sorry, I jumped the gun a little - I uploaded binutils-mingw-w64/2 and filed
#680647 in the mean time.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#680647: unblock: binutils-mingw-w64/2

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package binutils-mingw-w64: it drops a erroneous
Conflicts relationship with mingw32-binutils, which is required to
allow mingw32-ocaml upgrades from squeeze using apt-get (see #662746
for details).

The diff is as follows:

diff --git a/debian/changelog b/debian/changelog
index e6866ff..056d74d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+binutils-mingw-w64 (2) unstable; urgency=low
+
+  * binutils-mingw-w64 doesn't conflict with mingw32-binutils so remove
+the relationship (helps with #662746).
+
+ -- Stephen Kitt st...@sk2.org  Wed, 04 Jul 2012 22:54:01 +0200
+
 binutils-mingw-w64 (1) unstable; urgency=low
 
   [ Stephen Kitt ]
diff --git a/debian/control b/debian/control
index 9ec7885..39dcbab 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,6 @@ Package: binutils-mingw-w64
 Architecture: all
 Depends: ${misc:Depends}, binutils-mingw-w64-i686, binutils-mingw-w64-x86-64
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Description: Cross-binutils for Win32 and Win64 using MinGW-w64
  MinGW-w64 provides a development and runtime environment for 32- and
  64-bit (x86 and x64) Windows applications using the Windows API and
@@ -25,7 +24,6 @@ Package: binutils-mingw-w64-i686
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Breaks: binutils-mingw-w64 ( 2.22-1+1)
 Replaces: binutils-mingw-w64 ( 2.22-1+1)
 Description: Cross-binutils for Win32 (x86) using MinGW-w64
@@ -39,7 +37,6 @@ Package: binutils-mingw-w64-x86-64
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Breaks: binutils-mingw-w64 ( 2.22-1+1)
 Replaces: binutils-mingw-w64 ( 2.22-1+1)
 Description: Cross-binutils for Win64 (x64) using MinGW-w64



unblock binutils-mingw-w64/2

Regards,

Stephen


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120707163215.31509.76559.report...@heffalump.sk2.org

Freeze exception for binutils-mingw-w64 (helps fix RC #662746)

[Stephen Kitt]

Dear release team,

I'd like to request a freeze exception for binutils-mingw-w64; it
currently (needlessly) conflits with mingw32-binutils, which prevents
apt-get from handling mingw32-ocaml upgrades properly (#662746).

The diff is as follows:

diff --git a/debian/changelog b/debian/changelog
index e6866ff..056d74d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+binutils-mingw-w64 (2) unstable; urgency=low
+
+  * binutils-mingw-w64 doesn't conflict with mingw32-binutils so remove
+the relationship (helps with #662746).
+
+ -- Stephen Kitt st...@sk2.org  Wed, 04 Jul 2012 22:54:01 +0200
+
 binutils-mingw-w64 (1) unstable; urgency=low
 
   [ Stephen Kitt ]
diff --git a/debian/control b/debian/control
index 9ec7885..39dcbab 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,6 @@ Package: binutils-mingw-w64
 Architecture: all
 Depends: ${misc:Depends}, binutils-mingw-w64-i686, binutils-mingw-w64-x86-64
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Description: Cross-binutils for Win32 and Win64 using MinGW-w64
  MinGW-w64 provides a development and runtime environment for 32- and
  64-bit (x86 and x64) Windows applications using the Windows API and
@@ -25,7 +24,6 @@ Package: binutils-mingw-w64-i686
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Breaks: binutils-mingw-w64 ( 2.22-1+1)
 Replaces: binutils-mingw-w64 ( 2.22-1+1)
 Description: Cross-binutils for Win32 (x86) using MinGW-w64
@@ -39,7 +37,6 @@ Package: binutils-mingw-w64-x86-64
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
 Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
 Breaks: binutils-mingw-w64 ( 2.22-1+1)
 Replaces: binutils-mingw-w64 ( 2.22-1+1)
 Description: Cross-binutils for Win64 (x64) using MinGW-w64


This is necessary but not sufficient to fix #662746, which is why I
don't close the bug in the changelog. (A full fix also requires adding
a Breaks/Replaces relationship to mingw-ocaml on older versions of
mingw32-ocaml.)

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120704222458.gh21...@sk2.org

Re: Freeze exception for binutils-mingw-w64 (helps fix RC #662746)

[Stephen Kitt]

On Thu, Jul 05, 2012 at 12:24:59AM +0200, Stephen Kitt wrote:
 I'd like to request a freeze exception for binutils-mingw-w64; it
 currently (needlessly) conflits with mingw32-binutils, which prevents
 apt-get from handling mingw32-ocaml upgrades properly (#662746).

Just to clarify, this is a pre-upload request...

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120704223524.gi21...@sk2.org

Bug#672820: transition: libcdio

[Stephen Kitt]

Hi,

On Mon, 14 May 2012 01:00:40 +0200, Julien Cristau jcris...@debian.org
wrote:
 On Mon, May 14, 2012 at 00:30:10 +0200, Nicolas Boullis wrote:
  ¹ I somehow missed the requirement to request transitions as bug reports 
  against the release.debian.org pseudo-package, and asked it about 2 
  months ago as a simple e-mail to debian-release@l.d.o, but my message 
  remained unanswered.
  
 Not really a requirement, but the bts makes tracking stuff easier.  In
 any case our backlog for transition requests is longer than two months
 right now, unfortunately.

As you (Julien) discovered, mednafen has a potential FTBFS related to its
construction of Built-Using (#677867). Given that the current package binNMU'd
correctly on all platforms except hurd-i386, I suppose I should wait until
the libcdio transition is over before uploading a fix, shouldn't I? The
reason I ask is since other packages are holding up the transition, I
wondered if fixing a potential FTBFS warranted an upload despite the
transition.

I've uploaded a new version of the experimental version of mednafen, with
only the fix for #677867, and that built correctly on hurd-i386.

Regards,

Stephen


signature.asc
Description: PGP signature

Re: wine preparation for wheezy

[Stephen Kitt]

On Mon, May 14, 2012 at 12:20:32PM +0200, Alexander Reichle-Schmehl wrote:
 On 14.05.2012 00:20, Michael Gilbert wrote:
 Stephen Kitt recently prepared a wine-gecko 1.1 package, which is now
 waiting in the NEW queue [1], [..]
 My biggest concern is the wine-gecko packages in NEW, and the
 currently very large NEW queue review delay [2].
 
 Problem solved.

Woohoo, thanks! Version 1.4 will be hitting NEW in the next few days
;-).

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120514172325.ga12...@sk2.org

Bug#624591: transition: libgmp3c2 → libgmp10

[Stephen Kitt]

On Sat, 30 Apr 2011 13:25:04 +0200, Julien Cristau jcris...@debian.org
wrote:
 - gcc-mingw32 (build-depends on mingw-w64, which depends on
   gcc-mingw-w64, which only exists on i386 and amd64; so all screwed up,
   somebody should file a bug)

I hadn't expected this to become urgent, I'll fix it this weekend (on both
the gcc-mingw32 and gcc-mingw-w64 sides).

Regards,

Stephen


signature.asc
Description: PGP signature

Re: nmu: Please binNMU binutils-mingw-w64 on i386

[Stephen Kitt]

Hi again,

On Fri, 29 Apr 2011 21:57:04 +0200, Stephen Kitt st...@sk2.org wrote:
 Since binutils is now up to 2.21.51.20110421-2, may I suggest
 
 nmu binutils-mingw-w64_0.1 . amd64 i386 . -m Rebuild for binutils
 2.21.51.20110421-2.

Sorry for the to-ing and fro-ing, I'll actually be uploading a new
binutils-mingw-w64 package shortly to fix #624545 and help fix #624591
(because of gcc-mingw32). So the binNMU would just be a waste...

Regards,

Stephen


signature.asc
Description: PGP signature

Re: nmu: Please binNMU binutils-mingw-w64 on i386

[Stephen Kitt]

Hi,

On Fri, 29 Apr 2011 16:36:08 +0200, Didier Raboud o...@debian.org wrote:
 binutils-mingw-w64 is lagging on i386. A binNMU  would solve this.
 
 This package applies a set of patches to the binutils source, and hence
 needs a binary rebuild at each new binutils upload. AFAIK there are no
 automatic tools to handle this.

Technically I don't think it's absolutely necessary to rebuild it every time
binutils is updated, especially now that Built-Using allows us to remain
GPL2-compliant without special fixes in the archive tools. It would be nice
though to have the same version on all architectures for which the package is
built!

 nmu binutils-mingw-w64_0.1 . i386 . -m Rebuild for binutils
 2.21.51.20110419-2.

Since binutils is now up to 2.21.51.20110421-2, may I suggest

nmu binutils-mingw-w64_0.1 . amd64 i386 . -m Rebuild for binutils 
2.21.51.20110421-2.

(I hope I got the syntax right.)

 (Note that I'm not the maintainer of binutils-mingw-w64, but just noticed it
 lagging, hence proposing the obvious solution.)

Thanks for looking out for the package!

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#598145: unblock: mednafen/0.8.D.3-1

[Stephen Kitt]

On Thu, Sep 30, 2010 at 07:52:36PM +0100, Adam D. Barratt wrote:
 On Mon, 2010-09-27 at 22:35 +0200, Stephen Kitt wrote:
  Should I remove the dependency?
 
 Packages producing different results depending on the cleanliness of the
 build environment are never great for reproducibility for security
 updates and the like.
 
 In this case I'm leaning towards preferring always building with jack to
 sometimes doing so (or explicitly telling the build system not to use
 jack even if it's available) and have unblocked the package.

Thanks!

Those are my thoughts exactly, I definitely agree that builds should
be reproducible.  In this particular instance I asked the question
because it was an extra change since the version in testing; had I
removed the dependency I would have disabled jack support in the call
to configure as you suggest (and re-enabled it for Wheezy).

Regards,

Stephen



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100930205126.gi25...@sk2.org

Bug#598145: unblock: mednafen/0.8.D.3-1

[Stephen Kitt]

On Mon, 27 Sep 2010 19:07:55 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Sun, 2010-09-26 at 22:48 +0200, Stephen Kitt wrote:
  Please unblock package mednafen; the latest version in unstable fixes
  a memory leak. I'm attaching the full diff between 0.8.D-1 (the
  version currently in testing) and 0.8.D.3-1 (the version in unstable),
  I believe it's reasonably short and easy to read; the only changes are
  some assembly fixes (for Mac OS X), gcc-4.5 build fixes, the memory
  leak, and an added dependency on libjack-dev.
 
 Why is the libjack-dev build-dependency now necessary, when it
 presumably wasn't before?  (At least, earlier versions have built
 successfully and nothing in the diff indicates a new use of jack).

It's not necessary, I simply noticed when rebuilding 0.8.D.2 that it was used
if present (dpkg-buildpackage and pbuilder produced packages with different
dependencies); since at the time I wasn't intending on requesting a freeze
exception, I added an explicit build-dependency. Mednafen has actually
supported jack since version 0.7.0!

Should I remove the dependency?

Regards,

Stephen



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100927223500.0a4a6...@sk2.org

Bug#598145: unblock: mednafen/0.8.D.3-1

[Stephen Kitt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception


Please unblock package mednafen; the latest version in unstable fixes
a memory leak. I'm attaching the full diff between 0.8.D-1 (the
version currently in testing) and 0.8.D.3-1 (the version in unstable),
I believe it's reasonably short and easy to read; the only changes are
some assembly fixes (for Mac OS X), gcc-4.5 build fixes, the memory
leak, and an added dependency on libjack-dev.

The changelog is as follows:

mednafen (0.8.D.3-1) unstable; urgency=low

  * New upstream version, fixing a significant memory leak.

 -- Stephen Kitt st...@sk2.org  Fri, 17 Sep 2010 07:18:16 +0200

mednafen (0.8.D.2-1) unstable; urgency=low

  * New upstream version.
  * Standards-Version 3.9.1, no change required.
  * Add build dependency on libjack-dev.

 -- Stephen Kitt st...@sk2.org  Thu, 05 Aug 2010 08:35:19 +0200

(I uploaded 0.8.D.3-1 to unstable rather than experimental because
0.8.D.2-1 was already in unstable, having been prepared just before
the freeze. I hadn't requested an exception then because the changes
in 0.8.D.1 and 0.8.D.2 don't affect the Debian package, at least not
for Squeeze.)

Regards,

Stephen


unblock mednafen/0.8.D.3-1

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-trunk-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/ChangeLog b/ChangeLog
index 2720f6c..90f3510 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,14 @@
+0.8.D.3:
+Fixed a significant memory leak in the video output code(the leak would increase every time fullscreen is toggled
+while Mednafen is running).
+
+0.8.D.2:
+NES: Fixed a crash on certain x86_64 platforms(Mac OS X), due to the sound filtering code dereferencing 32-bit registers instead of 64-bit registers as
+it should have.
+
+0.8.D.1:
+	Fixed a compilation error on gcc 4.5(thanks to hanno for pointing it out).
+
 0.8.D:
 	SMS:  Some state that wasn't being saved in save states now is, which should fix netplay desynch problems with SMS/GG games.
 
diff --git a/configure b/configure
index 643cd45..b94a128 100755
--- a/configure
+++ b/configure
@@ -4294,7 +4294,7 @@ $as_echo $ac_cv_safe_to_define___extensions__ 6; }
 
 
 
-MEDNAFEN_VERSION='0.8.D'
+MEDNAFEN_VERSION='0.8.D.3'
 MEDNAFEN_VERSION_NUMERIC=0x00080D
 
 ac_aux_dir=
diff --git a/configure.ac b/configure.ac
index 3153081..9709c6c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,7 +2,7 @@ AC_INIT([src/mednafen.cpp])
 AC_GNU_SOURCE
 AC_USE_SYSTEM_EXTENSIONS
 
-MEDNAFEN_VERSION='0.8.D'
+MEDNAFEN_VERSION='0.8.D.3'
 MEDNAFEN_VERSION_NUMERIC=0x00080D
 
 AC_CANONICAL_HOST
diff --git a/debian/changelog b/debian/changelog
index ecf2aea..568597f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+mednafen (0.8.D.3-1) unstable; urgency=low
+
+  * New upstream version, fixing a significant memory leak.
+
+ -- Stephen Kitt st...@sk2.org  Fri, 17 Sep 2010 07:18:16 +0200
+
+mednafen (0.8.D.2-1) unstable; urgency=low
+
+  * New upstream version.
+  * Standards-Version 3.9.1, no change required.
+  * Add build dependency on libjack-dev.
+
+ -- Stephen Kitt st...@sk2.org  Thu, 05 Aug 2010 08:35:19 +0200
+
 mednafen (0.8.D-1) unstable; urgency=low
 
   * New upstream version.
diff --git a/debian/control b/debian/control
index a88d391..2d84e76 100644
--- a/debian/control
+++ b/debian/control
@@ -3,8 +3,13 @@ Section: games
 Priority: optional
 Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
 Uploaders: Stephen Kitt st...@sk2.org
-Build-Depends: debhelper (= 5), autotools-dev, x11proto-core-dev, libgl1-mesa-dev | libgl-dev, zlib1g-dev | libz-dev, libsdl1.2-dev, libsamplerate0-dev, libsdl-net1.2-dev, libcdio-dev, libsndfile1-dev | libsndfile-dev, libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386]
-Standards-Version: 3.8.4
+Build-Depends: debhelper (= 5), autotools-dev, x11proto-core-dev,
+ libgl1-mesa-dev | libgl-dev, zlib1g-dev | libz-dev, libsdl1.2-dev,
+ libsamplerate0-dev, libsdl-net1.2-dev, libcdio-dev,
+ libsndfile1-dev | libsndfile-dev,
+ libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
+ libjack-dev
+Standards-Version: 3.9.1
 Homepage: http://mednafen.sourceforge.net
 Vcs-Git: git://git.debian.org/git/pkg-games/mednafen.git
 Vcs-Browser: http://git.debian.org/?p=pkg-games/mednafen.git
diff --git a/src/drivers/video.cpp b/src/drivers/video.cpp
index a6af6bc..a73e6f5 100644
--- a/src/drivers/video.cpp
+++ b/src/drivers/video.cpp
@@ -169,6 +169,12 @@ void KillVideo(void)
   HelpSurface = NULL;
  }
 
+ if(NetSurface)
+ {
+  SDL_FreeSurface(NetSurface);
+  NetSurface = NULL;
+ }
+
  if(cur_flags  SDL_OPENGL)
   KillOpenGL();
 
diff --git a/src/nes/sound/filter-amd64

Re: Possibility of getting an up-to-date version of Wine into Squeeze

[Stephen Kitt]

On Sun, Sep 05, 2010 at 03:06:35PM +0200, Andreas Barth wrote:
 * Andreas Barth (a...@not.so.argh.org) [100829 15:55]:
  * Andreas Barth (a...@not.so.argh.org) [100822 23:18]:
   * Stephen Kitt (li...@sk2.org) [100820 00:02]:
The version of Wine Squeeze is going to ship with (1.0.1) is nearly two 
years
old and for many users its use is greatly limited. The recently released
stable version, 1.2, has vastly improved support for a large number of
applications and games. I have prepared packages in the same style as 
the
current maintainer's, and a few people have tested them. I haven't had 
much
reaction from Ove but I do know he is aware of their existence; I 
haven't
consulted him regarding this particular request.
   
   Can we please see this version of wine in experimental first
  
  Any news on uploading wine to experimental?
 
 ping?

Sorry for the delay, I was waiting to see if Ove answered. I've had
packages ready on http://www.sk2.org/wine/ for a while, but they're
probably not ready for experimental (apart from the wine package, but
that needs wine-gecko).

As it stands, the packages build an updated gcc-mingw32 based on gcc
4.5.0, and a replacement runtime for mingw32-runtime based on
mingw-w64. This is where things get a bit complicated; Robert Millan's
packages based on mingw-w64 have been orphaned, but they pretended to
provide a build environment for mingw32msvc which doesn't match (or no
longer matches, I'm not sure) the upstream usage which is w64-mingw32
(with x86_64 and i686 variants, which would become amd64 and i586 or
i686 on Debian I guess). I could keep the existing targets and prepare
packages for experimental, but given that gcc 4.5 won't be in squeeze
(as I understand it), I thought it would be better to prepare a
complete set of w64-mingw32 packages, with proper build dependencies
on binutils-source and gcc-4.5-source. This would also help clearly
differenciate the mingw32 and mingw-w64 packages.

Thus the plan would be:
1. adopt mingw-w64 (I'll update #594371)
2. prepare binutils-mingw-w64 and gcc-4.5-mingw-w64 packages
3. update the mingw-w64 runtime (version 1.0 has been released)
4. update the wine-gecko 1.0.0 package
5. package wine-gecko 1.1.0 (this is required for wine-unstable 1.3.2)
6. update wine and wine-unstable

I do know that Ove has a wine-gecko (1.0.0) package which builds using
the existing mingw32-runtime, but it still needs an updated
gcc-mingw32. I don't know if wine-gecko 1.1.0 builds with
mingw32-runtime, but the official build instructions use mingw-w64. I
also know that Ove has worked on moving the wine packaging in a new
direction, so I wouldn't want to package wine against his wishes (but
my wine package hardly changes his existing packaging at all).

All in all it seems rather unrealistic to try hard now to get wine 1.2
into squeeze...

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100906212356.gc17...@sk2.org

Re: Possibility of getting an up-to-date version of Wine into Squeeze

[Stephen Kitt]

On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote:
 Den 21. aug. 2010 03:01, skrev Svante Signell:
 Please take this request seriously. Even if Squeeze is frozen,
 distributing the same version (1.0.x) of Wine as Lenny does not look
 good! People are trying to help out!
 
 I wouldn't hold much hope. These are the options:
 
 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did
 not solve all the problems with it, gcc-mingw32 would apparently
 have to be upgraded all the way to 4.5.0 to build a fully working
 package. Not sure if the release team will accept that, and even if
 they did, packaging Wine 1.2 for squeeze will, by now, be a rush job
 that may result in a package with serious problems.

Have you had a chance to take a look at my packages?  I took the time
to separate each patch out so that you'd be able to integrate them
into your git tree without to much trouble.

Note that building wine-gecko also requires an updated version of
mingw-w64 (used to produce an updated replacement for
mingw32-runtime).

You've convinced me as far as requiring wine-gecko is concerned,
which, given the new build environment involved, means pushing for
release in squeeze is unrealistic.

The one thing I do hope now is that you'll accept the various offers
of help you've received so that squeeze+1 can have a current version
of Wine when it comes out!

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100821085511.ga18...@sk2.org

Possibility of getting an up-to-date version of Wine into Squeeze

[Stephen Kitt]

Dear release team,

I know what the answer ought to be at this stage, but I thought I'd ask
anyway; is there any chance whatsoever that, should updated packages of Wine
be ready soon (and satisfy the usual quality requirements), they could be
accepted into Squeeze?

The version of Wine Squeeze is going to ship with (1.0.1) is nearly two years
old and for many users its use is greatly limited. The recently released
stable version, 1.2, has vastly improved support for a large number of
applications and games. I have prepared packages in the same style as the
current maintainer's, and a few people have tested them. I haven't had much
reaction from Ove but I do know he is aware of their existence; I haven't
consulted him regarding this particular request.

The changelog for my packages is as follows:

wine (1.2-0.1) unstable; urgency=low
  
  [ Stephen Kitt ]

  * Non-maintainer upload.
  * New upstream version. Closes: #585409, #589773.
- winebrowser correctly passes URLs via DDE. Closes: #491186.
  * Include ptrace speedup to avoid lag in Steamworks-based games.
  * Now that stable has debhelper 7, use it:
- use dh_lintian;
- add ${misc:Depends};
- drop dh_desktop.
  * Install new utilities into libwine-bin:
- attrib.exe;
- mshta.exe;
- ngen.exe;
- ping.exe;
- sc.exe.
  * Install new French and German translations of winemaker.1 into
libwine-dev.
  * Install new NLS file into libwine.
  * Remove obsolete build dependencies (dependencies no longer present in
stable). Closes: #578975.
  * Switch to 3.0 (quilt) source format and split existing patches.
  * Build on kfreebsd (thanks Tuco!). Closes: #591837.
  
  [ Ove Kaaven ]
  
  * Install function_grep.pl into libwine-dev, in /usr/share/wine, and
modify winedump accordingly. Closes: #555645.
  * Replace @SUFFIX@ with current suffix in preprocessed maintainer
scripts.
  * Add proper package suffixes to the installed reportbug control files.
  * Use wine-safe start /unix as the MIME handler for the
application/x-msdos-program type.

 -- Stephen Kitt st...@sk2.org  Thu, 05 Aug 2010 00:00:14 +0200


I realise this request utterly flies in the face of the minimal changes
requirement, I'm not even the maintainer of the package, and Wine doesn't
have any RC-bug filed against it; hence my initial comment. I'm at least
hoping I won't waste too much of anyone's time...

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010082215.2ebcb...@sk2.org

Migration of joystick to testing

[Stephen Kitt]

Hi,

My joystick package (hardly one of the important one in Debian, I know) is
ready for migration except that it hasn't been rebuilt for s390. I gather
there's an entry in Packages-arch-specific preventing such a rebuild, so
would it be possible to remove the s390 build from testing?

Thanks in advance,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100621221513.30619...@sk2.org

Re: Migration of joystick to testing

[Stephen Kitt]

On Mon, Jun 21, 2010 at 09:55:22PM +0100, Adam D. Barratt wrote:
 On Mon, 2010-06-21 at 22:15 +0200, Stephen Kitt wrote:
  My joystick package (hardly one of the important one in Debian, I know) is
  ready for migration except that it hasn't been rebuilt for s390. I gather
  there's an entry in Packages-arch-specific preventing such a rebuild, so
  would it be possible to remove the s390 build from testing?
 
 The outdated s390 packages need removing from unstable; the package will
 then be a candidate for migration and the s390 packages in testing will
 automatically be removed as part of the move.
 
 reportbug ftp.debian.org will guide you through creating a request for
 the removal from unstable; http://wiki.debian.org/ftpmaster_Removals is
 also a useful reference.

Great, thanks, I've just done that. The wiki page does indeed clarify
things!

Regards,

Stephen


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100621210224.gw14...@sk2.org