Bug#895888: stretch-pu: package libipc-run-perl/0.94-1+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
libipc-run-perl 0.94-1 has a memory leak that causes some code at $work
to use all of the RAM on the machine. We would like to fix it in jessie
using the patch accepted upstream and released into sid and buster.
We have tested the patches internally and they resolve our issue.
--
bye,
pabs
https://wiki.debian.org/PaulWise
diff -Nru libipc-run-perl-0.94/debian/changelog libipc-run-perl-0.94/debian/changelog
--- libipc-run-perl-0.94/debian/changelog 2015-05-10 23:05:50.0 +0800
+++ libipc-run-perl-0.94/debian/changelog 2018-04-17 16:24:46.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.94-1+deb9u1) stretch; urgency=medium
+
+ * Backport upstream patch to fix memory leak
+
+ -- Paul Wise Tue, 17 Apr 2018 16:24:46 +0800
+
libipc-run-perl (0.94-1) unstable; urgency=low
[ Salvatore Bonaccorso ]
diff -Nru libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
--- libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch 1970-01-01 08:00:00.0 +0800
+++ libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch 2018-04-17 16:24:10.0 +0800
@@ -0,0 +1,31 @@
+From 5cd3a5b21bd00dbb2e54e58fec6b0349bf457bb0 Mon Sep 17 00:00:00 2001
+From: Konrad Bucheli
+Date: Tue, 27 Mar 2018 11:22:58 +0200
+Subject: [PATCH] Another Bugfix for memory leak [rt.cpan.org #57990] #86
+Origin: https://github.com/kbucheli/IPC-Run/commit/d706e65d0e5dab055d9b6c8d070330fdc7b1a883
+Bug: https://github.com/toddr/IPC-Run/issues/86
+
+---
+ lib/IPC/Run.pm | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/lib/IPC/Run.pm b/lib/IPC/Run.pm
+index 2436bc5..61cdb5f 100644
+--- a/lib/IPC/Run.pm
b/lib/IPC/Run.pm
+@@ -1135,6 +1135,12 @@ sub DESTROY {
+my IPC::Run $self = shift;
+POSIX::close $self->{DEBUG_FD} if defined $self->{DEBUG_FD};
+$self->{DEBUG_FD} = undef;
++
++ for my $kid ( @{$self->{KIDS}} ) {
++ for my $op ( @{$kid->{OPS}} ) {
++ delete $op->{FILTERS};
++ }
++ }
+ }
+
+ ##
+--
+2.17.0
+
diff -Nru libipc-run-perl-0.94/debian/patches/series libipc-run-perl-0.94/debian/patches/series
--- libipc-run-perl-0.94/debian/patches/series 2015-05-10 23:05:50.0 +0800
+++ libipc-run-perl-0.94/debian/patches/series 2018-04-17 16:24:20.0 +0800
@@ -1 +1,2 @@
hashbang.patch
+0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
signature.asc
Description: This is a digitally signed message part
Bug#895887: jessie-pu: package libipc-run-perl/0.92-1+deb8u1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
libipc-run-perl 0.92-1 has a memory leak that causes some code at $work
to use all of the RAM on the machine. We would like to fix it in jessie
using the patch accepted upstream and released into sid and buster.
We have tested the patches internally and they resolve our issue.
--
bye,
pabs
https://wiki.debian.org/PaulWise
diff -Nru libipc-run-perl-0.92/debian/changelog libipc-run-perl-0.92/debian/changelog
--- libipc-run-perl-0.92/debian/changelog 2012-09-01 01:21:38.0 +0800
+++ libipc-run-perl-0.92/debian/changelog 2018-04-17 16:16:38.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.92-1+deb8u1) jessie; urgency=medium
+
+ * Backport upstream patch to fix memory leak
+
+ -- Paul Wise Tue, 17 Apr 2018 16:16:38 +0800
+
libipc-run-perl (0.92-1) unstable; urgency=low
[ gregor herrmann ]
diff -Nru libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
--- libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch 1970-01-01 08:00:00.0 +0800
+++ libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch 2018-04-17 16:16:38.0 +0800
@@ -0,0 +1,31 @@
+From 5cd3a5b21bd00dbb2e54e58fec6b0349bf457bb0 Mon Sep 17 00:00:00 2001
+From: Konrad Bucheli
+Date: Tue, 27 Mar 2018 11:22:58 +0200
+Subject: [PATCH] Another Bugfix for memory leak [rt.cpan.org #57990] #86
+Origin: https://github.com/kbucheli/IPC-Run/commit/d706e65d0e5dab055d9b6c8d070330fdc7b1a883
+Bug: https://github.com/toddr/IPC-Run/issues/86
+
+---
+ lib/IPC/Run.pm | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/lib/IPC/Run.pm b/lib/IPC/Run.pm
+index 2436bc5..61cdb5f 100644
+--- a/lib/IPC/Run.pm
b/lib/IPC/Run.pm
+@@ -1135,6 +1135,12 @@ sub DESTROY {
+my IPC::Run $self = shift;
+POSIX::close $self->{DEBUG_FD} if defined $self->{DEBUG_FD};
+$self->{DEBUG_FD} = undef;
++
++ for my $kid ( @{$self->{KIDS}} ) {
++ for my $op ( @{$kid->{OPS}} ) {
++ delete $op->{FILTERS};
++ }
++ }
+ }
+
+ ##
+--
+2.17.0
+
diff -Nru libipc-run-perl-0.92/debian/patches/series libipc-run-perl-0.92/debian/patches/series
--- libipc-run-perl-0.92/debian/patches/series 2012-09-01 01:21:38.0 +0800
+++ libipc-run-perl-0.92/debian/patches/series 2018-04-17 16:08:26.0 +0800
@@ -1 +1,2 @@
hashbang.patch
+0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
signature.asc
Description: This is a digitally signed message part
Re: RFR: Britney - autopkgtest integration
Hi all, On 15-04-18 20:18, Paul Gevers wrote: > Just for reference, I started collecting relevant bugs in the > bts with the ci-t...@tracker.debian.org user¹ in the bts (bunk and > ginggs added a couple using the right usertags as well). It has been brought to my attention that the ci-t...@tracker.debian.org isn't a valid e-mail address and shouldn't be used. I have migrated all the user tags to the debian...@lists.debian.org user². Paul ² https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian...@lists.debian.org signature.asc Description: OpenPGP digital signature
Bug#888239: marked as done (stretch-pu: package nvidia-graphics-drivers-legacy-340xx/340.106-1~deb9u1)
Your message dated Tue, 17 Apr 2018 13:12:34 +0200 with message-id <2fe859a6-c3ee-e51d-0286-467ad7c66...@debian.org> and subject line Re: Bug#888239: stretch-pu: package nvidia-graphics-drivers-legacy-340xx/340.106-1~deb9u1 has caused the Debian Bug report #888239, regarding stretch-pu: package nvidia-graphics-drivers-legacy-340xx/340.106-1~deb9u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update the 340xx legacy nvidia driver in stretch with a new upstream version that brings spectre/meltdown mitigation fixes and related kernel support. Security updates for the non-free drivers have always been done via proposed-updates. The package is a plain rebuild from sid with no further changes needed and therefore contains also all the accumulated bugfixes from the package in sid (and some of them are already in nvidia-graphics-drivers in stretch, since we had a security update in the previous stretch point release). The proposed package is now also available in stretch-backports to allow further testing. The changelog stanza in addition to the attached diff (debian/ tree only, blobs excluded) will be --- debian/changelog (revision 7831) +++ debian/changelog (working copy) @@ -1,3 +1,9 @@ +nvidia-graphics-drivers-legacy-340xx (340.106-1~deb9u1) stretch; urgency=medium + + * Rebuild for stretch. + + -- Andreas Beckmann Wed, 24 Jan 2018 07:06:23 +0100 + nvidia-graphics-drivers-legacy-340xx (340.106-1) unstable; urgency=medium * New upstream legacy 340xx branch release 340.106 (2018-01-16). Andreas Index: debian/libgl1-nvidia-glx.prerm.in === --- debian/libgl1-nvidia-glx.prerm.in (.../tags/340.102-1)(revision 7831) +++ debian/libgl1-nvidia-glx.prerm.in (.../trunk) (revision 7831) @@ -1,13 +0,0 @@ -#!/bin/sh -set -e - - -if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ]; then - - update-alternatives --remove nvidia /usr/lib/#PRIVATE# - dpkg-trigger register-glx-alternative-nvidia - -fi - - -#DEBHELPER# Index: debian/nvidia-alternative.prerm.in === --- debian/nvidia-alternative.prerm.in (.../tags/340.102-1)(revision 7831) +++ debian/nvidia-alternative.prerm.in (.../trunk) (revision 7831) @@ -5,6 +5,7 @@ if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ]; then update-alternatives --remove nvidia /usr/lib/#PRIVATE# + dpkg-trigger --no-await register-glx-alternative-nvidia fi Index: debian/not-installed.in === --- debian/not-installed.in (.../tags/340.102-1)(revision 0) +++ debian/not-installed.in (.../trunk) (revision 7831) @@ -0,0 +1,37 @@ +.manifest +LICENSE +gl.h +glext.h +glx.h +glxext.h +libGL.la +#!armhf#libnvidia-tls.so.#VERSION# +libnvidia-wfb.so.#VERSION# +libvdpau.so.#VERSION# +libvdpau_trace.so.#VERSION# +makeself-help-script.sh +makeself.sh +mkprecompiled +nvidia-installer +nvidia-installer.1 +nvidia-modprobe +nvidia-modprobe.1 +nvidia-persistenced +nvidia-persistenced-init.tar.bz2 +nvidia-persistenced.1 +nvidia-settings +nvidia-settings.1 +nvidia-settings.desktop +nvidia-settings.png +nvidia-xconfig +nvidia-xconfig.1 +pci.ids +pkg-history.txt +tls_test +tls_test_dso.so + +libOpenCL.so.1.0.0 +nvidia.icd +nvidia-cuda-mps-control +nvidia-cuda-mps-control.1 +nvidia-cuda-mps-server Index: debian/changelog === --- debian/changelog(.../tags/340.102-1)(revision 7831) +++ debian/changelog(.../trunk) (revision 7831) @@ -1,3 +1,113 @@ +nvidia-graphics-drivers-legacy-340xx (340.106-1) unstable; urgency=medium + + * New upstream legacy 340xx branch release 340.106 (2018-01-16). + * Fixed CVE-2017-5753, CVE-2017-5715 (spectre), CVE-2017-5754 (meltdown). + https://nvidia.custhelp.com/app/answers/detail/a_id/4611 + (Closes: #886852) +* Improved compatibility with recent Linux kernels. + + [ Luca Boccassi ] + * Drop nvidia-drm-pci-init.patch and timer.patch, fixed upstream. + + -- Andreas Beckmann Wed, 17 Jan 2018 20:50:05 +0100 + +nvidia-graphics-drivers-legacy-340xx (340.104-4) unstable; urgency=medium + + [ Andreas Beckmann ] + * Bump Standards-Version to 4.1.3. No change
Bug#887559: jessie-pu: package nvidia-graphics-drivers/340.106-1
Followup-For: Bug #887559 Hi, uploaded according to the new (O)PU instructions. Updated source debdiff attached. Andreas ngd-340.106-1.diff.gz Description: application/gzip
Bug#894971: stretch-pu: package nvidia-graphics-drivers/384.130-1
Followup-For: Bug #894971 Hi, just uploaded according to the new PU instructions. Updated debdiff attached (some documentation updates). Andreas ngd-384.130-1.diff.gz Description: application/gzip
Bug#895935: jessie-pu: package patch/2.7.5-1+deb8u1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi OSRMs,
I'd like to fix CVE-2018-1000156 in patch for Jessie, which is an
arbitrary command execution in ed-style patches.
While it might be used for remote compromise, it would need a setup to
accept patches unconditionally. But then an attacker has an easy path
already to insert vulnerable code to source files or JavaScript
injection to HTML pages, etc. Hence it doesn't warrant a DSA on its
own, but would be good to fix in a point release.
Thanks for considering,
Laszlo/GCSdiff -Nru patch-2.7.5/debian/changelog patch-2.7.5/debian/changelog
--- patch-2.7.5/debian/changelog 2015-03-07 06:38:30.0 +
+++ patch-2.7.5/debian/changelog 2018-04-16 20:48:14.0 +
@@ -1,3 +1,10 @@
+patch (2.7.5-1+deb8u1) jessie; urgency=medium
+
+ * Fix CVE-2018-1000156: arbitrary command execution in ed-style patches
+(closes: #894993).
+
+ -- Laszlo Boszormenyi (GCS) Mon, 16 Apr 2018 20:48:14 +
+
patch (2.7.5-1) unstable; urgency=medium
* New upstream release.
diff -Nru patch-2.7.5/debian/control patch-2.7.5/debian/control
--- patch-2.7.5/debian/control 2015-03-07 06:33:14.0 +
+++ patch-2.7.5/debian/control 2018-04-16 20:48:14.0 +
@@ -2,7 +2,7 @@
Section: vcs
Priority: standard
Maintainer: Laszlo Boszormenyi (GCS)
-Build-Depends: debhelper (>= 7), ed
+Build-Depends: debhelper (>= 7), ed, autoconf, automake
Standards-Version: 3.9.6
Homepage: http://savannah.gnu.org/projects/patch/
Vcs-Git: git://git.debian.org/collab-maint/patch.git
diff -Nru patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch
--- patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch 1970-01-01 00:00:00.0 +
+++ patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch 2018-04-16 20:48:14.0 +
@@ -0,0 +1,237 @@
+From 123eaff0d5d1aebe128295959435b9ca5909c26d Mon Sep 17 00:00:00 2001
+From: Andreas Gruenbacher
+Date: Fri, 6 Apr 2018 12:14:49 +0200
+Subject: Fix arbitrary command execution in ed-style patches
+ (CVE-2018-1000156)
+
+* src/pch.c (do_ed_script): Write ed script to a temporary file instead
+of piping it to ed: this will cause ed to abort on invalid commands
+instead of rejecting them and carrying on.
+* tests/ed-style: New test case.
+* tests/Makefile.am (TESTS): Add test case.
+---
+ src/pch.c | 91 ---
+ tests/Makefile.am | 1 +
+ tests/ed-style| 41 +
+ 3 files changed, 108 insertions(+), 25 deletions(-)
+ create mode 100644 tests/ed-style
+
+diff --git a/src/pch.c b/src/pch.c
+index 0c5cc26..4fd5a05 100644
+--- a/src/pch.c
b/src/pch.c
+@@ -33,6 +33,7 @@
+ # include
+ #endif
+ #include
++#include
+
+ #define INITHUNKMAX 125 /* initial dynamic allocation size */
+
+@@ -2387,22 +2387,28 @@ do_ed_script (char const *inname, char c
+ static char const editor_program[] = EDITOR_PROGRAM;
+
+ file_offset beginning_of_this_line;
+-FILE *pipefp = 0;
+ size_t chars_read;
++FILE *tmpfp = 0;
++char const *tmpname;
++int tmpfd;
++pid_t pid;
++
++if (! dry_run && ! skip_rest_of_patch)
++ {
++ /* Write ed script to a temporary file. This causes ed to abort on
++ invalid commands such as when line numbers or ranges exceed the
++ number of available lines. When ed reads from a pipe, it rejects
++ invalid commands and treats the next line as a new command, which
++ can lead to arbitrary command execution. */
++
++ tmpfd = make_tempfile (&tmpname, 'e', NULL, O_RDWR | O_BINARY, 0);
++ if (tmpfd == -1)
++ pfatal ("Can't create temporary file %s", quotearg (tmpname));
++ tmpfp = fdopen (tmpfd, "w+b");
++ if (! tmpfp)
++ pfatal ("Can't open stream for file %s", quotearg (tmpname));
++ }
+
+-if (! dry_run && ! skip_rest_of_patch) {
+- int exclusive = *outname_needs_removal ? 0 : O_EXCL;
+- assert (! inerrno);
+- *outname_needs_removal = true;
+- copy_file (inname, outname, 0, exclusive, instat.st_mode, true);
+- sprintf (buf, "%s %s%s", editor_program,
+- verbosity == VERBOSE ? "" : "- ",
+- outname);
+- fflush (stdout);
+- pipefp = popen(buf, binary_transput ? "wb" : "w");
+- if (!pipefp)
+- pfatal ("Can't open pipe to %s", quotearg (buf));
+-}
+ for (;;) {
+ char ed_command_letter;
+ beginning_of_this_line = file_tell (pfp);
+@@ -2413,14 +2418,14 @@ do_ed_script (char const *inname, char const *outname,
+ }
+ ed_command_letter = get_ed_command_letter (buf);
+ if (ed_command_letter) {
+- if (pipefp)
+- if (! fwrite (buf, sizeof *buf, chars_read, pipefp))
++ if (tmpfp)
++ if (! fwrite (buf, sizeof *buf, chars_read, tmpfp))
+ write_fatal ();
+ if (ed_command_letter != 'd' && ed_command_l
Bug#895936: stretch-pu: package patch/2.7.5-1+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi SRMs,
I'd like to fix CVE-2018-1000156 in patch for Stretch, which is an
arbitrary command execution in ed-style patches.
While it might be used for remote compromise, it would need a setup to
accept patches unconditionally. But then an attacker has an easy path
already to insert vulnerable code to source files or JavaScript
injection to HTML pages, etc. Hence it doesn't warrant a DSA on its
own, but would be good to fix in a point release.
Thanks for considering,
Laszlo/GCSdiff -Nru patch-2.7.5/debian/changelog patch-2.7.5/debian/changelog
--- patch-2.7.5/debian/changelog 2015-03-07 06:38:30.0 +
+++ patch-2.7.5/debian/changelog 2018-04-16 20:48:43.0 +
@@ -1,3 +1,10 @@
+patch (2.7.5-1+deb9u1) stretch; urgency=medium
+
+ * Fix CVE-2018-1000156: arbitrary command execution in ed-style patches
+(closes: #894993).
+
+ -- Laszlo Boszormenyi (GCS) Mon, 16 Apr 2018 20:48:43 +
+
patch (2.7.5-1) unstable; urgency=medium
* New upstream release.
diff -Nru patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch
--- patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch 1970-01-01 00:00:00.0 +
+++ patch-2.7.5/debian/patches/Fix_arbitrary_command_execution_in_ed-style_patches.patch 2018-04-16 20:48:43.0 +
@@ -0,0 +1,237 @@
+From 123eaff0d5d1aebe128295959435b9ca5909c26d Mon Sep 17 00:00:00 2001
+From: Andreas Gruenbacher
+Date: Fri, 6 Apr 2018 12:14:49 +0200
+Subject: Fix arbitrary command execution in ed-style patches
+ (CVE-2018-1000156)
+
+* src/pch.c (do_ed_script): Write ed script to a temporary file instead
+of piping it to ed: this will cause ed to abort on invalid commands
+instead of rejecting them and carrying on.
+* tests/ed-style: New test case.
+* tests/Makefile.am (TESTS): Add test case.
+---
+ src/pch.c | 91 ---
+ tests/Makefile.am | 1 +
+ tests/ed-style| 41 +
+ 3 files changed, 108 insertions(+), 25 deletions(-)
+ create mode 100644 tests/ed-style
+
+diff --git a/src/pch.c b/src/pch.c
+index 0c5cc26..4fd5a05 100644
+--- a/src/pch.c
b/src/pch.c
+@@ -33,6 +33,7 @@
+ # include
+ #endif
+ #include
++#include
+
+ #define INITHUNKMAX 125 /* initial dynamic allocation size */
+
+@@ -2387,22 +2387,28 @@ do_ed_script (char const *inname, char c
+ static char const editor_program[] = EDITOR_PROGRAM;
+
+ file_offset beginning_of_this_line;
+-FILE *pipefp = 0;
+ size_t chars_read;
++FILE *tmpfp = 0;
++char const *tmpname;
++int tmpfd;
++pid_t pid;
++
++if (! dry_run && ! skip_rest_of_patch)
++ {
++ /* Write ed script to a temporary file. This causes ed to abort on
++ invalid commands such as when line numbers or ranges exceed the
++ number of available lines. When ed reads from a pipe, it rejects
++ invalid commands and treats the next line as a new command, which
++ can lead to arbitrary command execution. */
++
++ tmpfd = make_tempfile (&tmpname, 'e', NULL, O_RDWR | O_BINARY, 0);
++ if (tmpfd == -1)
++ pfatal ("Can't create temporary file %s", quotearg (tmpname));
++ tmpfp = fdopen (tmpfd, "w+b");
++ if (! tmpfp)
++ pfatal ("Can't open stream for file %s", quotearg (tmpname));
++ }
+
+-if (! dry_run && ! skip_rest_of_patch) {
+- int exclusive = *outname_needs_removal ? 0 : O_EXCL;
+- assert (! inerrno);
+- *outname_needs_removal = true;
+- copy_file (inname, outname, 0, exclusive, instat.st_mode, true);
+- sprintf (buf, "%s %s%s", editor_program,
+- verbosity == VERBOSE ? "" : "- ",
+- outname);
+- fflush (stdout);
+- pipefp = popen(buf, binary_transput ? "wb" : "w");
+- if (!pipefp)
+- pfatal ("Can't open pipe to %s", quotearg (buf));
+-}
+ for (;;) {
+ char ed_command_letter;
+ beginning_of_this_line = file_tell (pfp);
+@@ -2413,14 +2418,14 @@ do_ed_script (char const *inname, char const *outname,
+ }
+ ed_command_letter = get_ed_command_letter (buf);
+ if (ed_command_letter) {
+- if (pipefp)
+- if (! fwrite (buf, sizeof *buf, chars_read, pipefp))
++ if (tmpfp)
++ if (! fwrite (buf, sizeof *buf, chars_read, tmpfp))
+ write_fatal ();
+ if (ed_command_letter != 'd' && ed_command_letter != 's') {
+ p_pass_comments_through = true;
+ while ((chars_read = get_line ()) != 0) {
+- if (pipefp)
+- if (! fwrite (buf, sizeof *buf, chars_read, pipefp))
++ if (tmpfp)
++ if (! fwrite (buf, sizeof *buf, chars_read, tmpfp))
+ write_fatal ();
+ if (chars_read == 2 && strEQ (buf, ".\n"))
+ break;
+@@ -2433,13 +2438,49 @@ do_ed_script (char const *inname, char const *outname,
+ break;
+ }
+ }
+-if (!pipefp)
++if (!tmpfp)
+ return;
+
Bug#895943: transition: perl 5.26.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, perl 5.26.2-1 in experimental. It is binary compatible with 5.26.0 and 5.26.1 and therefore Provides all of perlapi-5.26.0, perlapi-5.26.1 and perlapi-5.26.2. However, as usual, four packages will need binNMUs once it enters unstable due to their strict versioned dependencies on the current perl version: libpar-packer-perl libdevel-cover-perl libclass-xsaccessor-perl libcommon-sense-perl These binNMUs will need the 'extra-depends' wanna-build feature to make sure the new perl is pulled in. Please let us know if/when it's OK to upload. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#895943: transition: perl 5.26.2
Control: tags -1 confirmed On 17/04/18 18:38, Niko Tyni wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > perl 5.26.2-1 in experimental. It is binary compatible with 5.26.0 and > 5.26.1 and therefore Provides all of perlapi-5.26.0, perlapi-5.26.1 > and perlapi-5.26.2. However, as usual, four packages will need binNMUs > once it enters unstable due to their strict versioned dependencies on > the current perl version: > > libpar-packer-perl > libdevel-cover-perl > libclass-xsaccessor-perl > libcommon-sense-perl > > These binNMUs will need the 'extra-depends' wanna-build feature to make > sure the new perl is pulled in. > > Please let us know if/when it's OK to upload. Please go ahead. Cheers, Emilio
Processed: Re: Bug#895943: transition: perl 5.26.2
Processing control commands: > tags -1 confirmed Bug #895943 [release.debian.org] transition: perl 5.26.2 Added tag(s) confirmed. -- 895943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895341: marked as done (release.debian.org: Mention in wanna-build.{md,html} that people should follow up on transition bugs for transition related requests)
Your message dated Tue, 17 Apr 2018 19:42:16 +0200
with message-id <270d9565-f6cb-3e17-45ae-7da1edd7f...@debian.org>
and subject line Re: Bug#895341: release.debian.org: Mention in
wanna-build.{md,html} that people should follow up on transition bugs for
transition related requests
has caused the Debian Bug report #895341,
regarding release.debian.org: Mention in wanna-build.{md,html} that people
should follow up on transition bugs for transition related requests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: wishlist
At the moment, "Please read wanna-build[1]" is a canned answer
from Debian contributors when people ask about how to request binNMUs.
However, sometimes people think that they need to request binNMUs for
packages involved in transitions and they might not mention "for a
transition" when they ask for help.
Therefore, it would probably be a help if we explicitly mentioned
transitions in our wanna-build document.
Thanks,
~Niels
[1] html: https://release.debian.org/wanna-build.html
txt: https://release.debian.org/wanna-build.md
--- End Message ---
--- Begin Message ---
On 10/04/18 07:23, Niels Thykier wrote:
> Package: release.debian.org
> Severity: wishlist
>
>
> At the moment, "Please read wanna-build[1]" is a canned answer
> from Debian contributors when people ask about how to request binNMUs.
> However, sometimes people think that they need to request binNMUs for
> packages involved in transitions and they might not mention "for a
> transition" when they ask for help.
>
> Therefore, it would probably be a help if we explicitly mentioned
> transitions in our wanna-build document.
https://salsa.debian.org/release-team/release.debian.org/commit/c3189d47a0493489b0d329708eb23447bbb9a5c3
commit c3189d47a0493489b0d329708eb23447bbb9a5c3
Author: Emilio Pozuelo Monfort
Date: Tue Apr 17 19:26:27 2018 +0200
wanna-build.md: mention transition bugs for binNMUs
https://bugs.debian.org/895341
Signed-off-by: Emilio Pozuelo Monfort
Cheers,
Emilio--- End Message ---
Uploading linux (4.15.17-1)
I intend to upload linux version 4.15.17-1 to unstable on Wednesday or Thursday of this week. Aside from the upstream stable updates, the pending changes include: - [armel] Configuration changes to shrink the kernel image and enable building it again - Disabling the error message during boot about missing regulatory.db - [armhf] Enable auto-loading of imx6q-cpufreq module where appropriate - Security fixes for ext4 and libsas - Bump ABI number to 3 Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Bug#895943: transition: perl 5.26.2
On Tue, Apr 17, 2018 at 06:44:50PM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 17/04/18 18:38, Niko Tyni wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > Hi, > > > > perl 5.26.2-1 in experimental. It is binary compatible with 5.26.0 and > > 5.26.1 and therefore Provides all of perlapi-5.26.0, perlapi-5.26.1 > > and perlapi-5.26.2. However, as usual, four packages will need binNMUs > > once it enters unstable due to their strict versioned dependencies on > > the current perl version: > > > > libpar-packer-perl > > libdevel-cover-perl > > libclass-xsaccessor-perl > > libcommon-sense-perl > > > > These binNMUs will need the 'extra-depends' wanna-build feature to make > > sure the new perl is pulled in. > > > > Please let us know if/when it's OK to upload. > > Please go ahead. Thanks, uploaded last night. -- Niko
