Bug#889279: marked as done (stretch-pu: package quota/4.03-2+b1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2018 08:47:39 +0100
with message-id <20180226074739.GA15317@feivel>
and subject line Closing
has caused the Debian Bug report #889279,
regarding stretch-pu: package quota/4.03-2+b1
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.)


-- 
889279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889279
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

As reported in #888586 quotacheck may run into an endless loop because it fails
to honor the non-interactive flag and still asks a question while there is no
way to answer it. The proposed patch is already in Sid waiting to migrate to
testing.

I think we should update stable, too. Therefore this report. The proposed patch
is attached. Please tell me what you think.

Also, I'm undecided as to whether we should update Jessie which is almost EOL.
Any comment on that would be appreciated too.

Michael

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
commit 09f618d4ed6eee2f2eda3fe069e1de30a7c1e8a6
Author: Michael Meskes 
Date:   Sat Feb 3 09:46:32 2018 +0100

Prevent quotacheck from running into an endless loop.
See #888586 for details.

diff --git a/debian/changelog b/debian/changelog
index c186840..63f8d28 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+quota (4.03-2+deb9u1) stretch; urgency=medium
+
+  * Prevent quotacheck from running into an endless loop.
+See #888586 for details.
+
+ -- Michael Meskes   Sat, 03 Feb 2018 09:45:50 +0100
+
 quota (4.03-2) unstable; urgency=medium
 
   * With systemd only test after installation, the rest is handled by systemd.
diff --git a/debian/patches/loop.diff b/debian/patches/loop.diff
new file mode 100644
index 000..66d739e
--- /dev/null
+++ b/debian/patches/loop.diff
@@ -0,0 +1,14 @@
+#Description: Prevent quotacheck from going into en endless loop.
+#Author:  Christoph Biedl 
+--- a/quotacheck_v2.c
 b/quotacheck_v2.c
+@@ -363,7 +363,7 @@
+"specified on command line (%d). Quota file header "
+"may be corrupted.\n"),
+  le32toh(head.dqh_version), version);
+-  if (!ask_yn(_("Continue checking assuming version from command 
line?"), 1))
++  if ((flags & FL_INTERACTIVE) && !ask_yn(_("Continue checking 
assuming version from command line?"), 1))
+   return -1;
+   detected_versions[type] = version;
+   } else
+
diff --git a/debian/patches/series b/debian/patches/series
index a348ff0..b9712b6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 editor.diff
+loop.diff
--- End Message ---
--- Begin Message ---
The package made it's way into the archive, therefore the bug can be closed.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL--- End Message ---

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: linux-latest_80+deb9u4_multi.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_amd64.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_arm64.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_armel.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_armhf.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_i386.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_mips.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_mips64el.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_mipsel.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_ppc64el.changes
  ACCEPT
Processing changes file: linux-latest_80+deb9u4_s390x.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: systemd_232-25+deb9u2_mipsel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: systemd_232-25+deb9u2_armel.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_armhf.changes
  ACCEPT

Processed: Re: Bug#889873: vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #889873 [vagrant] vagrant: unable to download images (moved from 
atlas.hashicorp.com to app.vagrantup.com)
Added tag(s) pending.
> block -1 by 891484
Bug #889873 [vagrant] vagrant: unable to download images (moved from 
atlas.hashicorp.com to app.vagrantup.com)
889873 was not blocked by any bugs.
889873 was not blocking any bugs.
Added blocking bug(s) of 889873: 891484

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

Bug#891484: stretch-pu: package vagrant/1.9.1+dfsg-1+deb9u1

[Antonio Terceiro]

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

The platform from where vagrant downloads images has been discontinued
and we need to switch the default download location plus documentation,
usage messages etc to match the new platform. Without this update,
vagrant is pretty useless.

Changelog:

vagrant (1.9.1+dfsg-1+deb9u1) stretch; urgency=medium

  * 0008-Convert-atlas-references-to-vagrant-cloud.patch: backport upstream
patch to download boxes from app.vagrantcloud.com instead of the
deprecated atlas.hashicorp.com (Closes: #889873)

 -- Antonio Terceiro   Sun, 25 Feb 2018 21:54:18 -0300

Diff against package in stretch attached.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (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 39dbcb2..48bff55 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+vagrant (1.9.1+dfsg-1+deb9u1) stretch; urgency=medium
+
+  * 0008-Convert-atlas-references-to-vagrant-cloud.patch: backport upstream
+patch to download boxes from app.vagrantcloud.com instead of the
+deprecated atlas.hashicorp.com (Closes: #889873)
+
+ -- Antonio Terceiro   Sun, 25 Feb 2018 21:54:18 -0300
+
 vagrant (1.9.1+dfsg-1) unstable; urgency=medium
 
   * New upstream version 1.9.1+dfsg
diff --git a/debian/patches/0008-Convert-atlas-references-to-vagrant-cloud.patch b/debian/patches/0008-Convert-atlas-references-to-vagrant-cloud.patch
new file mode 100644
index 000..20533be
--- /dev/null
+++ b/debian/patches/0008-Convert-atlas-references-to-vagrant-cloud.patch
@@ -0,0 +1,286 @@
+From: Chris Roberts 
+Date: Sun, 25 Feb 2018 21:53:24 -0300
+Subject: Convert atlas references to vagrant cloud
+
+Backported-by: Antonio Terceiro 
+---
+ lib/vagrant/shared_helpers.rb   |  4 ++--
+ plugins/commands/box/command/add.rb |  2 +-
+ plugins/commands/login/client.rb| 21 -
+ plugins/commands/login/command.rb   |  8 
+ plugins/commands/login/locales/en.yml   | 10 +-
+ .../commands/login/middleware/add_authentication.rb |  3 ++-
+ plugins/commands/login/plugin.rb|  2 +-
+ templates/commands/init/Vagrantfile.erb |  9 +
+ templates/locales/en.yml|  8 
+ test/unit/plugins/commands/login/client_test.rb |  4 ++--
+ 10 files changed, 34 insertions(+), 37 deletions(-)
+
+diff --git a/lib/vagrant/shared_helpers.rb b/lib/vagrant/shared_helpers.rb
+index ffe61e5..93f4c11 100644
+--- a/lib/vagrant/shared_helpers.rb
 b/lib/vagrant/shared_helpers.rb
+@@ -5,12 +5,12 @@ require "thread"
+ module Vagrant
+   @@global_lock = Mutex.new
+ 
+-  # This is the default endpoint of the Atlas in
++  # This is the default endpoint of the Vagrant Cloud in
+   # use. API calls will be made to this for various functions
+   # of Vagrant that may require remote access.
+   #
+   # @return [String]
+-  DEFAULT_SERVER_URL = "https://atlas.hashicorp.com;
++  DEFAULT_SERVER_URL = "https://vagrantcloud.com;
+ 
+   # This holds a global lock for the duration of the block. This should
+   # be invoked around anything that is modifying process state (such as
+diff --git a/plugins/commands/box/command/add.rb b/plugins/commands/box/command/add.rb
+index 5545ea2..d8ae063 100644
+--- a/plugins/commands/box/command/add.rb
 b/plugins/commands/box/command/add.rb
+@@ -40,7 +40,7 @@ module VagrantPlugins
+ end
+ 
+ o.separator ""
+-o.separator "The box descriptor can be the name of a box on HashiCorp's Atlas,"
++o.separator "The box descriptor can be the name of a box on HashiCorp's Vagrant Cloud,"
+ o.separator "or a URL, or a local .box file, or a local .json file containing"
+ o.separator "the catalog metadata."
+ o.separator ""
+diff --git a/plugins/commands/login/client.rb b/plugins/commands/login/client.rb
+index 04b6ee0..fb2dd05 100644
+--- a/plugins/commands/login/client.rb
 b/plugins/commands/login/client.rb
+@@ -86,28 +86,26 @@ module VagrantPlugins
+   end
+ 
+   # Reads the access token if there is one. This will first read the
+-  # `ATLAS_TOKEN` environment variable and then fallback to the stored
++  # `VAGRANT_CLOUD_TOKEN` environment variable and then fallback to the stored
+   # access token on 

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_armhf.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u1_armhf.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_armhf.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_armhf.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_armhf.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_mips.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_mips64el.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_armhf.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_armhf.changes
  ACCEPT

Processed: tagging 890889, tagging 887412, tagging 887415, retitle 891010 to nmu: ruby-bcrypt-pbkdf_1.0.0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 890889 + stretch
Bug #890889 [release.debian.org] stretch-pu: package yorick-av/0.0.4-1
Added tag(s) stretch.
> tags 887412 + stretch
Bug #887412 [release.debian.org] RM: electrum/2.7.9-1
Added tag(s) stretch.
> tags 887415 + jessie
Bug #887415 [release.debian.org] RM: electrum/1.9.8-4
Added tag(s) jessie.
> retitle 891010 nmu: ruby-bcrypt-pbkdf_1.0.0-1
Bug #891010 [release.debian.org] Subject: nmu: ruby-bcrypt-pbkdf_1.0.0-1
Changed Bug title to 'nmu: ruby-bcrypt-pbkdf_1.0.0-1' from 'Subject: nmu: 
ruby-bcrypt-pbkdf_1.0.0-1'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887412
887415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887415
890889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890889
891010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_armhf.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_armhf.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_mips.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_armel.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_mips.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_armel.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_armel.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_mipsel.changes
  ACCEPT

Bug#891481: stretch-pu: package pjproject/2.5.5~dfsg-6+deb9u1

[Bernhard Schmidt]

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

Hi,

I'd like to ask for a SRM approval to include a non-security fix for an
important bug in the pjproject package into the next security upload.

In #881362 Joachim Förster reported issues resolving DNS SRV records
if the target does not have an  record. He identified and tested
an upstream patch that has been part of sid for more than 6 months.

We will have to do a security upload of pjproject soon, and I'd like to
include this fix there.

Relevant patch attached.

Bernhard
diff --git a/debian/patches/0008-r5536-Fix-SRV-without-.patch 
b/debian/patches/0008-r5536-Fix-SRV-without-.patch
new file mode 100644
index 000..2a20cb4
--- /dev/null
+++ b/debian/patches/0008-r5536-Fix-SRV-without-.patch
@@ -0,0 +1,55 @@
+From: Riza Sulistyo 
+Subject: [PATCH] Re #1945 (misc): Don't trigger SRV complete callback when
+ there is a parse error.
+Bug-Debian: https://bugs.debian.org/881362
+
+git-svn-id: https://svn.pjsip.org/repos/pjproject/trunk@5536 
74dad513-b988-da41-8d7b-12977e46ad98
+---
+ pjlib-util/src/pjlib-util/srv_resolver.c | 24 ++--
+ 1 file changed, 18 insertions(+), 6 deletions(-)
+
+diff --git a/pjlib-util/src/pjlib-util/srv_resolver.c 
b/pjlib-util/src/pjlib-util/srv_resolver.c
+index 8a4a599e..8a2f7e1b 100644
+--- a/pjlib-util/src/pjlib-util/srv_resolver.c
 b/pjlib-util/src/pjlib-util/srv_resolver.c
+@@ -652,6 +652,7 @@ static void dns_callback(void *user_data,
+ 
+ } else if (query_job->dns_state == PJ_DNS_TYPE_A) {
+   pj_bool_t is_type_a, srv_completed;
++pj_dns_addr_record rec;
+ 
+   /* Clear outstanding job */
+   if (common->type == PJ_DNS_TYPE_A) {
+@@ -668,15 +669,26 @@ static void dns_callback(void *user_data,
+ 
+   is_type_a = (common->type == PJ_DNS_TYPE_A);
+ 
++/* Parse response */
++if (status==PJ_SUCCESS && pkt->hdr.anscount != 0) {
++status = pj_dns_parse_addr_response(pkt, );
++if (status!=PJ_SUCCESS) {
++char errmsg[PJ_ERR_MSG_SIZE];
++  
++PJ_LOG(4,(query_job->objname, 
++"DNS %s record parse error for '%.*s'."
++" Err=%d (%s)",
++  (is_type_a ? "A" : ""),
++(int)query_job->domain_part.slen,
++query_job->domain_part.ptr,
++status,
++pj_strerror(status,errmsg,sizeof(errmsg)).ptr));
++}
++}
++
+   /* Check that we really have answer */
+   if (status==PJ_SUCCESS && pkt->hdr.anscount != 0) {
+   char addr[PJ_INET6_ADDRSTRLEN];
+-  pj_dns_addr_record rec;
+-
+-  /* Parse response */
+-  status = pj_dns_parse_addr_response(pkt, );
+-  if (status != PJ_SUCCESS)
+-  goto on_error;
+ 
+   pj_assert(rec.addr_count != 0);
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 4ddd84c..b23b21f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -18,3 +18,4 @@ asterisk/0017-r5475-svn-backport-Remove-DNS-cache-entry.patch
 asterisk/0018-r5477-svn-backport-Fix-DNS-write-on-freed-memory.patch
 asterisk/0019-Parse-zero-length-multipart-body-parts-correctly.patch
 asterisk/0020-Ensure-2543-transaction-key-buffer-is-large-enough.patch
+0008-r5536-Fix-SRV-without-.patch

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u1_armel.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_armel.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_armhf.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_armel.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_armhf.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_mips64el.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_mipsel.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_armel.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_mips.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_armel.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_armhf.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_armel.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_mips.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_armel.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_mips.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_armel.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_mips64el.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_mipsel.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_amd64.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_arm64.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_ppc64el.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_s390x.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_amd64.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_arm64.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_i386.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_amd64.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_i386.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_mips.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_i386.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_mips.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_ppc64el.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u1_all.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_amd64.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_arm64.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_i386.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_mips.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u1_s390x.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_amd64.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_arm64.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_armel.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_armhf.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_i386.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_mips.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_s390x.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_all.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_amd64.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_arm64.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_armel.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_armhf.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_i386.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_mips.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_s390x.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_arm64.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_i386.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_mips.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_s390x.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_all.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_amd64.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_arm64.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_armel.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_i386.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_mips.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_s390x.changes
  ACCEPT
Processing changes file: gosa-plugin-pwreset_0.99.4-1+deb9u1_all.changes
  ACCEPT
Processing changes file: libperlx-assert-perl_0.904-1+deb9u1_all.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_all.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_amd64.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_arm64.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_i386.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_mips.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_ppc64el.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_s390x.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_arm64.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_i386.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_s390x.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_arm64.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_i386.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_mips.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_s390x.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_arm64.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_i386.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_s390x.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_arm64.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_i386.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_s390x.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_amd64.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_arm64.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_i386.changes
  ACCEPT
Processing changes file: 

Bug#891470: stretch-pu: package auto-complete-el/1.3.1-2+deb9u1

[Adrian Bunk]

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

  * Add upstream fix for emacs25. (Closes: #849240)
emacs24 and emacs25 are co-installable.

  * Adjust the emacs dependencies to the emacs versions in stretch.
(Closes: #746982)
We ship two emacs versions in stretch, it should be possible
to remove the older one without forcing auto-complete-el removal.

  * Set auto-complete-el.emacsen-compat to silence installation warning.
diff -Nru auto-complete-el-1.3.1/debian/auto-complete-el.emacsen-compat 
auto-complete-el-1.3.1/debian/auto-complete-el.emacsen-compat
--- auto-complete-el-1.3.1/debian/auto-complete-el.emacsen-compat   
1970-01-01 02:00:00.0 +0200
+++ auto-complete-el-1.3.1/debian/auto-complete-el.emacsen-compat   
2018-02-25 22:08:51.0 +0200
@@ -0,0 +1 @@
+0
diff -Nru auto-complete-el-1.3.1/debian/changelog 
auto-complete-el-1.3.1/debian/changelog
--- auto-complete-el-1.3.1/debian/changelog 2012-03-25 17:30:40.0 
+0300
+++ auto-complete-el-1.3.1/debian/changelog 2018-02-25 22:08:51.0 
+0200
@@ -1,3 +1,13 @@
+auto-complete-el (1.3.1-2+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for emacs25. (Closes: #849240)
+  * Adjust the emacs dependencies to the emacs versions in stretch.
+(Closes: #746982)
+  * Set auto-complete-el.emacsen-compat to silence installation warning.
+
+ -- Adrian Bunk   Sun, 25 Feb 2018 22:08:51 +0200
+
 auto-complete-el (1.3.1-2) unstable; urgency=low
 
   * debian/emacsen-remove:
diff -Nru auto-complete-el-1.3.1/debian/control 
auto-complete-el-1.3.1/debian/control
--- auto-complete-el-1.3.1/debian/control   2012-03-25 17:30:34.0 
+0300
+++ auto-complete-el-1.3.1/debian/control   2018-02-25 22:08:51.0 
+0200
@@ -8,7 +8,7 @@
 
 Package: auto-complete-el
 Architecture: all
-Depends: ${misc:Depends}, emacs | emacs23 | emacs22 | emacs-snapshot
+Depends: ${misc:Depends}, emacs | emacs25 | emacs25-lucid | emacs25-nox
 Description: intelligent auto-completion extension for GNU Emacs
  Auto Complete Mode is an intelligent auto-completion extension for
  GNU Emacs. It extends the standard Emacs completion interface and
diff -Nru auto-complete-el-1.3.1/debian/patches/0001-Add-missing-nil.patch 
auto-complete-el-1.3.1/debian/patches/0001-Add-missing-nil.patch
--- auto-complete-el-1.3.1/debian/patches/0001-Add-missing-nil.patch
1970-01-01 02:00:00.0 +0200
+++ auto-complete-el-1.3.1/debian/patches/0001-Add-missing-nil.patch
2017-07-19 14:01:05.0 +0300
@@ -0,0 +1,22 @@
+From 8d3db89eaaaebf31cca574216e630f64e5e28c5f Mon Sep 17 00:00:00 2001
+From: Chris Zheng 
+Date: Fri, 11 Dec 2015 15:09:22 +0800
+Subject: Add missing nil.
+
+---
+ auto-complete.el | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: auto-complete-el-1.3.1/auto-complete.el
+===
+--- auto-complete-el-1.3.1.orig/auto-complete.el
 auto-complete-el-1.3.1/auto-complete.el
+@@ -671,7 +671,7 @@ You can not use it in source definition
+ (defun ac-menu-delete ()
+   (when ac-menu
+ (popup-delete ac-menu)
+-(setq ac-menu)))
++(setq ac-menu nil)))
+ 
+ (defsubst ac-inline-marker ()
+   (nth 0 ac-inline))
diff -Nru auto-complete-el-1.3.1/debian/patches/series 
auto-complete-el-1.3.1/debian/patches/series
--- auto-complete-el-1.3.1/debian/patches/series1970-01-01 
02:00:00.0 +0200
+++ auto-complete-el-1.3.1/debian/patches/series2017-07-19 
14:01:05.0 +0300
@@ -0,0 +1 @@
+0001-Add-missing-nil.patch

Bug#891466: stretch-pu: package 2ping/3.2.1-1+deb9u1

[Adrian Bunk]

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

  * Add the missing dependency on python-pkg-resources.
(Closes: #855972)
diff -Nru 2ping-3.2.1/debian/changelog 2ping-3.2.1/debian/changelog
--- 2ping-3.2.1/debian/changelog2016-03-26 07:42:15.0 +0200
+++ 2ping-3.2.1/debian/changelog2018-02-25 21:53:33.0 +0200
@@ -1,3 +1,11 @@
+2ping (3.2.1-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python-pkg-resources.
+(Closes: #855972)
+
+ -- Adrian Bunk   Sun, 25 Feb 2018 21:53:33 +0200
+
 2ping (3.2.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 2ping-3.2.1/debian/control 2ping-3.2.1/debian/control
--- 2ping-3.2.1/debian/control  2015-12-13 02:53:07.0 +0200
+++ 2ping-3.2.1/debian/control  2018-02-25 21:53:33.0 +0200
@@ -11,7 +11,7 @@
 
 Package: 2ping
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, python, 
python-argparse
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, python, 
python-argparse, python-pkg-resources
 Description: Ping utility to determine directional packet loss
  2ping is a bi-directional ping utility. It uses 3-way pings (akin to 
  TCP SYN, SYN/ACK, ACK) and after-the-fact state comparison between a 

Bug#891464: stretch-pu: package java-atk-wrapper/0.33.3-13+deb9u1

[Samuel Thibault]

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

Hello,

It was reported (#837081) that notably netbeans would crash on
some operations due to java-atk-wrapper bugs. This was reported as
being fixed by a couple of small patches which have now migrated to
testing. I'd like to upload them to Stretch as attached diff shows.

Samuel

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

Kernel: Linux 4.15.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (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 5747482..9b8e967 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+java-atk-wrapper (0.33.3-13+deb9u1) stretch; urgency=medium
+
+  * debian/patches/iter: Fix iterator initialization.
+  * debian/patches/child_add: Fix missing reference for children
+(Closes: #837081).
+
+ -- Samuel Thibault   Sun, 11 Dec 2016 13:08:23 +0100
+
 java-atk-wrapper (0.33.3-13) unstable; urgency=medium
 
   * patches/thread-daemon: Make JAW thread a daemon so that JVM termination 
does
diff --git a/debian/patches/child_add b/debian/patches/child_add
new file mode 100644
index 000..26b6dae
--- /dev/null
+++ b/debian/patches/child_add
@@ -0,0 +1,16 @@
+https://bugzilla.gnome.org/show_bug.cgi?id=793622
+---
+ jni/src/AtkWrapper.c |2 ++
+ 1 file changed, 2 insertions(+)
+
+--- a/jni/src/AtkWrapper.c
 b/jni/src/AtkWrapper.c
+@@ -683,6 +683,8 @@ signal_emit_handler (gpointer p)
+ "children_changed::add",
+ child_index,
+ para->child_impl);
++if (G_OBJECT(atk_obj) != NULL)
++  g_object_ref(G_OBJECT(atk_obj));
+ break;
+   }
+   case Sig_Object_Children_Changed_Remove:
diff --git a/debian/patches/iter b/debian/patches/iter
new file mode 100644
index 000..ad3e892
--- /dev/null
+++ b/debian/patches/iter
@@ -0,0 +1,34 @@
+https://bugzilla.gnome.org/show_bug.cgi?id=793620
+
+---
+ jni/src/AtkWrapper.c |2 ++
+ jni/src/jawimpl.c|   11 +--
+ 2 files changed, 7 insertions(+), 6 deletions(-)
+
+--- a/jni/src/jawimpl.c
 b/jni/src/jawimpl.c
+@@ -546,19 +546,18 @@ jaw_impl_finalize(GObject *gobject)
+   jaw_obj->acc_context = NULL;
+ 
+   /* Interface finalize */
+-  GHashTableIter *iter = NULL;
+-  gpointer *key = NULL;
+-  gpointer *value = NULL;
++  GHashTableIter iter;
++  gpointer value;
+ 
+-  g_hash_table_iter_init(iter, jaw_impl->ifaceTable);
+-  while (g_hash_table_iter_next(iter, key, value))
++  g_hash_table_iter_init(, jaw_impl->ifaceTable);
++  while (g_hash_table_iter_next(, NULL, ))
+   {
+ JawInterfaceInfo *info = (JawInterfaceInfo*)value;
+ info->finalize(info->data);
+ 
+ g_free(info);
+ 
+-g_hash_table_iter_remove(iter);
++g_hash_table_iter_remove();
+   }
+   if (jaw_impl->ifaceTable != NULL)
+   {
diff --git a/debian/patches/series b/debian/patches/series
index 2b34236..a22f971 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,3 +12,5 @@ getAccessibleContextNull
 init
 getAccessibleStateSetNull
 thread-daemon
+iter
+child_add

Bug#888788: stretch-pu: package lxc/1:2.0.7-2+deb9u2

[Antonio Terceiro]

On Fri, Feb 23, 2018 at 04:58:11PM +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-01-29 at 20:40 -0200, Antonio Terceiro wrote:
> > iproute has been a transitional package for a while, but the lxc-
> > debian
> > template was refering to it. Now that iproute has been finally
> > removed,
> > creating buster or sid containers fails.
> > 
> > This update replaces iproute with iproute2. I am running it on
> > ci.debian.net
> > 
> 
> Please go ahead.

Uploaded.


signature.asc
Description: PGP signature

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Chris Lamb]

Hi Adam,

> > Best case scenario for me is that I upload what I proposed in
> > #857746; I mean, it was seemingly approved before and the issues are
> > still outstanding.
> 
> There isn't necessarily a 1:1 mapping between changes that would be
> approved for an unblock during freeze and changes that are likely to
> get ACKed for a stable update.

Oh hilariously I did not spot p-u vs. freeze unblock. This bug is a
trainwreck of confusion :)

> I've repurposed the unblock as a p-u request. Which way we go with the
> exact changes will depend on someone looking over the diff with a
> stable update perspective.

(You are, of course, completely right that this would not necessarily or
automatically qualify for stretch via p-u..)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 857746 pu: package redis/3:3.2.6-1
Bug #857746 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] unblock: redis/3:3.2.8-2
Changed Bug title to 'pu: package redis/3:3.2.6-1' from 'unblock: 
redis/3:3.2.8-2'.
> tags 857746 = stretch
Bug #857746 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] pu: package redis/3:3.2.6-1
Added tag(s) stretch.
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 857746 = pu
Usertags were: unblock.
Usertags are now: pu.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Adam D. Barratt]

retitle 857746 pu: package redis/3:3.2.6-1
tags 857746 = stretch
user release.debian@packages.debian.org
usertags 857746 = pu
thanks

Hi,

On Sun, 2018-02-25 at 18:14 +, Chris Lamb wrote:
> Hi Adam,
> 
> > Ah, I think I got confused by the bugs - I meant #880474. I assumed
> > that you were looking at getting the service fix included, rather
> > than
> > the whole of the upstream releases.
> > 
> > Before we both get any more confused, which of the above were you
> > actually requesting?
> 
> Good idea! So, I want to fix #880474 ("Unknown lvalue
> 'RunTimeDirectory' in section 'Service'") in stretch.
> 
> The real "confusion" is I had already fixed, uploaded and had
> unblocked this via #857746 yet this new version never actually hit
> stretch. (!)

As I explained, that's because there was an RC bug affecting the
version that was unblocked, that I assume no-one noticed at the time.

> Best case scenario for me is that I upload what I proposed in
> #857746; I mean, it was seemingly approved before and the issues are
> still outstanding.

There isn't necessarily a 1:1 mapping between changes that would be
approved for an unblock during freeze and changes that are likely to
get ACKed for a stable update.

I've repurposed the unblock as a p-u request. Which way we go with the
exact changes will depend on someone looking over the diff with a
stable update perspective.

Hopefully that won't be too long, but we are also in the week before
the p-u freeze for the 9.4 point release, which is generally fairly
busy.

Regards,

Adam

Bug#885617: stretch-pu: package libextractor/1:1.3-4

[Bertrand Marc]

Le 10/02/2018 à 11:13, Julien Cristau a écrit :
> Control: tag -1 moreinfo
>
> On Thu, Dec 28, 2017 at 17:11:02 +0100, Bertrand Marc wrote:
>
>> diff -Nru libextractor-1.3/debian/patches/CVE-2017-15600.patch 
>> libextractor-1.3/debian/patches/CVE-2017-15600.patch
>> --- libextractor-1.3/debian/patches/CVE-2017-15600.patch 1970-01-01 
>> 01:00:00.0 +0100
>> +++ libextractor-1.3/debian/patches/CVE-2017-15600.patch 2017-12-28 
>> 11:39:33.0 +0100
>> @@ -0,0 +1,29 @@
>> +From: Bertrand Marc , Markus Koschany 
>> +Subject: CVE-2017-15600
>> +
>> +Bug-Upstream: 
>> http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg4.html
>> +Origin: 
>> https://gnunet.org/git/libextractor.git/commit/?id=38e8933539ee9d044057b18a971c2eae3c21aba7
>> +--- a/src/plugins/nsf_extractor.c
>>  b/src/plugins/nsf_extractor.c
>> +@@ -152,13 +152,17 @@
>> +   char nsfversion[32];
>> +   const struct header *head;
>> +   void *data;
>> ++  ssize_t ds;
>> + 
>> +-  if (sizeof (struct header) >
>> +-  ec->read (ec->cls,
>> +-   ,
>> +-   sizeof (struct header)))
>> ++  ds = ec->read (ec->cls,
>> ++ ,
>> ++ sizeof (struct header));
>> ++  if ( (-1 == ds) ||
>> ++   (sizeof (struct header) > ds) )
>> + return;
>> +   head = data; 
>> ++  if (NULL == head)
>> ++return 0; 
>> + 
> Curious how that works.  3 lines above is plain "return", and here
> "return 0".  What's the type of that function and how did the compiler
> not flag this?
>
> Cheers,
> Julien

Indeed, sorry. The type of the function was changed from void (in wheezy) to 
int (in jessie). I updated the patch attached accordingly.


Cheers,

Bertrand

diff -Nru libextractor-1.3/debian/changelog libextractor-1.3/debian/changelog
--- libextractor-1.3/debian/changelog	2016-04-26 22:58:56.0 +0200
+++ libextractor-1.3/debian/changelog	2017-12-28 11:39:33.0 +0100
@@ -1,3 +1,14 @@
+libextractor (1:1.3-4+deb9u1) stretch; urgency=medium
+
+  * Fix CVE-2017-15266, CVE-2017-15267, CVE-2017-15600, CVE-2017-15601,
+CVE-2017-15602, CVE-2017-15922 and CVE-2017-17440. Leon Zhao discovered
+several security vulnerabilities, NULL Pointer Dereferences, heap-based
+buffer overflows, integer signedness errors and out-of-bounds read that
+may lead to a denial-of-service (application crash) or have other
+unspecified impact.
+
+ -- Bertrand Marc   Thu, 28 Dec 2017 11:39:33 +0100
+
 libextractor (1:1.3-4) unstable; urgency=medium
 
   * Update debian/patches/ffmpeg2.9.patch with a new commit taken from upstream
diff -Nru libextractor-1.3/debian/patches/CVE-2017-15266.patch libextractor-1.3/debian/patches/CVE-2017-15266.patch
--- libextractor-1.3/debian/patches/CVE-2017-15266.patch	1970-01-01 01:00:00.0 +0100
+++ libextractor-1.3/debian/patches/CVE-2017-15266.patch	2017-12-28 11:39:33.0 +0100
@@ -0,0 +1,17 @@
+From: Bertrand Marc 
+Subject: CVE-2017-15266
+
+Bug-Upstream: http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg2.html
+Bug-Debian: https://bugs.debian.org/878314
+Origin: https://gnunet.org/git/libextractor.git/commit/?id=b577d5452c5c4ee9d552da62a24b95f461551fe2
+--- a/src/plugins/wav_extractor.c
 b/src/plugins/wav_extractor.c
+@@ -109,6 +109,8 @@
+ return;/* invalid sample size found in wav file */
+   if (0 == channels)
+ return;/* invalid channels value -- avoid division by 0! */
++  if (0 == sample_rate)
++return;/* invalid sample_rate */
+   samples = data_len / (channels * (sample_size >> 3));
+ 
+   snprintf (scratch,
diff -Nru libextractor-1.3/debian/patches/CVE-2017-15267.patch libextractor-1.3/debian/patches/CVE-2017-15267.patch
--- libextractor-1.3/debian/patches/CVE-2017-15267.patch	1970-01-01 01:00:00.0 +0100
+++ libextractor-1.3/debian/patches/CVE-2017-15267.patch	2017-12-28 11:39:33.0 +0100
@@ -0,0 +1,22 @@
+From: Markus Koschany 
+Date: Mon, 4 Dec 2017 00:00:15 +0100
+Subject: CVE-2017-15267
+
+Bug-Upstream: http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg3.html
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878314
+Origin: https://gnunet.org/git/libextractor.git/commit/?id=6095d7132b57fc7368fc7a40bab2a71b735724d2
+---
+ src/plugins/flac_extractor.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+--- a/src/plugins/flac_extractor.c
 b/src/plugins/flac_extractor.c
+@@ -339,6 +339,8 @@
+ 	  {
+ 	entry = >comments[count];
+ 	eq = (const char*) entry->entry;
++	if (NULL == eq)
++			break;
+ 	len = entry->length;
+ 	ilen = 0;
+ 	while ( ('=' != *eq) && ('\0' != *eq) &&
diff -Nru libextractor-1.3/debian/patches/CVE-2017-15600.patch libextractor-1.3/debian/patches/CVE-2017-15600.patch
--- libextractor-1.3/debian/patches/CVE-2017-15600.patch	1970-01-01 01:00:00.0 +0100
+++ 

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Chris Lamb]

Hi Adam,

> Ah, I think I got confused by the bugs - I meant #880474. I assumed
> that you were looking at getting the service fix included, rather than
> the whole of the upstream releases.
> 
> Before we both get any more confused, which of the above were you
> actually requesting?

Good idea! So, I want to fix #880474 ("Unknown lvalue 'RunTimeDirectory'
in section 'Service'") in stretch.

The real "confusion" is I had already fixed, uploaded and had unblocked
this via #857746 yet this new version never actually hit stretch. (!)

Best case scenario for me is that I upload what I proposed in #857746;
I mean, it was seemingly approved before and the issues are still
outstanding.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Adam D. Barratt]

On Sun, 2018-02-25 at 17:54 +, Chris Lamb wrote:
> Hi Adam,
> 
> > > Do I need to re-upload?
> > 
> > If you want to fix #857746 in stretch (which I assume is the
> > overall
> > goal) then yes, that'll need to go through proposed-updates with a
> > release.d.o p-u bug
> 
> I don't quite follow I'm afraid - I would simply be re-filing #857746
> with the exact same content?
> 
> (If so, couldn't I reopen and re-upload? Mostly trying to understand
> the process here and/or ensure I'm not missing anything, rather than
> shortcut or bypass anything...)
> 

Ah, I think I got confused by the bugs - I meant #880474. I assumed
that you were looking at getting the service fix included, rather than
the whole of the upstream releases.

Before we both get any more confused, which of the above were you
actually requesting?

Regards,

Adam

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Chris Lamb]

Hi Adam,

> > Do I need to re-upload?
> 
> If you want to fix #857746 in stretch (which I assume is the overall
> goal) then yes, that'll need to go through proposed-updates with a
> release.d.o p-u bug

I don't quite follow I'm afraid - I would simply be re-filing #857746
with the exact same content?

(If so, couldn't I reopen and re-upload? Mostly trying to understand
the process here and/or ensure I'm not missing anything, rather than
shortcut or bypass anything...)

Thank you for your patience. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#890897: transition: unibilium

[James McCoy]

On Fri, Feb 23, 2018 at 08:17:31AM -0500, James McCoy wrote:
> On Fri, Feb 23, 2018 at 10:11:42AM +0100, Emilio Pozuelo Monfort wrote:
> > Control: tags -1 confirmed
> > 
> > On 20/02/18 13:16, James McCoy wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: transition
> > > 
> > > There is an upstream SONAME bump due to support for terminfo's new wide
> > > format.  The dependency chain revolves around neovim and everything
> > > rebuilds and tests fine with the new unibilium.
> > 
> > Go ahead.
> 
> Thanks.  Uploaded.

Could libtickit be binNMUed?  That would be the last bit to finish
rebuilding against the new unibilium.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Adam D. Barratt]

On Sun, 2018-02-25 at 17:30 +, Chris Lamb wrote:
> Hi Adam,
> 
> > > What am I missing? :)
> > #857855, which was RC at the time and (at least according to the
> > metadata) a regression relative to the package that was already in
> > stretch.
> 
> Huh, okay. Can you recommend the best way forward at this point? Mark
> the bug as notfound in the stretch version?

#857855 is already marked as not affecting the package in stretch -
that's why it was an issue for the original unblock.

> Do I need to re-upload?

If you want to fix #857746 in stretch (which I assume is the overall
goal) then yes, that'll need to go through proposed-updates with a
release.d.o p-u bug as usual. We can't make a version of redis that was
superseded nearly a year ago appear in stretch otherwise.

Regards,

Adam

Bug#891452: nmu: tumbler_0.2.0-1

[Andreas Beckmann]

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

nmu tumbler_0.2.0-1 . ANY . experimental . -m "Rebuild against libopenraw7."

Let's finish the libopenraw transition in experimental, too.


Andreas

Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Chris Lamb]

Hi Adam,

> > What am I missing? :)

> #857855, which was RC at the time and (at least according to the
> metadata) a regression relative to the package that was already in
> stretch.

Huh, okay. Can you recommend the best way forward at this point? Mark
the bug as notfound in the stretch version? Do I need to re-upload?

I'm a little lost, alas :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: xrdp_0.9.1-9+deb9u2_ppc64el.changes
  ACCEPT

Bug#891448: nmu: osmo-trx_0.2.0-1

[Andreas Beckmann]

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

nmu osmo-trx_0.2.0-1 . ANY . experimental . -m "Rebuild against 
libuhd003.010.003."

libuhd recently had a transition in sid ...


Andreas

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

[CC += KiBi as requested]

On Fri, 2018-02-23 at 19:54 +0100, Michael Biebl wrote:
> Am 23.02.2018 um 19:19 schrieb Adam D. Barratt:
> > Thanks. Please feel free to upload.
> 
> Uploaded.
> 

Flagged for acceptance into p-u.

Regards,

Adam

Processed: Re: Bug#890470: stretch-pu: package systemd/232-25+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #890470 [release.debian.org] stretch-pu: package systemd/232-25+deb9u2
Added tag(s) pending.

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

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u1_source.changes
  ACCEPT
Processing changes file: directfb_1.2.10.0-8+deb9u1_source.changes
  ACCEPT
Processing changes file: drupal7_7.52-2+deb9u2_amd64.changes
  ACCEPT
Processing changes file: flatpak_0.8.9-0+deb9u1_source.changes
  ACCEPT
Processing changes file: fuse-zip_0.4.0-2+deb9u1_amd64.changes
  ACCEPT
Processing changes file: glade_3.20.0-2+deb9u1_source.changes
  ACCEPT
Processing changes file: gosa-plugin-pwreset_0.99.4-1+deb9u1_source.changes
  ACCEPT
Processing changes file: 
libhibernate-validator-java_4.3.3-1+deb9u1_amd64.changes
  ACCEPT
Processing changes file: libperlx-assert-perl_0.904-1+deb9u1_source.changes
  ACCEPT
Processing changes file: mapproxy_1.9.0-3+deb9u1_amd64.changes
  ACCEPT
Processing changes file: ntp_4.2.8p10+dfsg-3+deb9u2_source.changes
  ACCEPT
Processing changes file: opendmarc_1.3.2-2+deb9u1_amd64.changes
  ACCEPT
Processing changes file: postfix_3.1.8-0+deb9u1_amd64.changes
  ACCEPT
Processing changes file: qtpass_1.1.6-1+deb9u1_amd64.changes
  ACCEPT
Processing changes file: quota_4.03-2+deb9u1_amd64.changes
  ACCEPT
Processing changes file: slic3r_1.2.9+dfsg-9~deb9u1_source.changes
  ACCEPT
Processing changes file: systemd_232-25+deb9u2_source.changes
  ACCEPT
Processing changes file: uwsgi_2.0.14+20161117-3+deb9u1_sourceonly.changes
  ACCEPT
Processing changes file: virt-what_1.15-1+deb9u1_source.changes
  ACCEPT
Processing changes file: w3m_0.5.3-34+deb9u1_amd64.changes
  ACCEPT

Bug#888731: stretch-pu: package virt-what/1.15-1+deb9u1

[Adam D. Barratt]

On Sun, 2018-02-25 at 16:08 +0100, Guido Günther wrote:
> On Sun, Feb 25, 2018 at 02:59:02PM +, Adam D. Barratt wrote:
> > Control: tags -1 + pending
> > 
> > On Fri, 2018-02-23 at 18:50 +0100, Guido Günther wrote:
> > > On Fri, Feb 23, 2018 at 04:53:27PM +, Adam D. Barratt wrote:
[...]
> > > > +virt-what (1.15-1+deb9u1) stable-proposed-updates;
> > > > urgency=medium
> > > > 
> > > > "stretch", please.
> > > > 
> > > > Please go ahead.
> > > 
> > > Uploaded. Thanks,
> > 
> > (Without the distribution change.)
> 
> Sorry, I misread that. Will use stretch for future updates.

Thanks, sorry if it wasn't clear.

Regards,

Adam

Bug#888731: stretch-pu: package virt-what/1.15-1+deb9u1

[Guido Günther]

On Sun, Feb 25, 2018 at 02:59:02PM +, Adam D. Barratt wrote:
> Control: tags -1 + pending
> 
> On Fri, 2018-02-23 at 18:50 +0100, Guido Günther wrote:
> > On Fri, Feb 23, 2018 at 04:53:27PM +, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> > > 
> > > On Mon, 2018-01-29 at 10:25 +0100, Guido Günther wrote:
> > > > The update fixes problems with virt detection arch/aarch64 since
> > > > these
> > > > fall back to uname -m. x86 uses cpuid mostly so it went there
> > > > undetected.
> > > > 
> > > 
> > > +virt-what (1.15-1+deb9u1) stable-proposed-updates; urgency=medium
> > > 
> > > "stretch", please.
> > > 
> > > Please go ahead.
> > 
> > Uploaded. Thanks,
> 
> (Without the distribution change.)

Sorry, I misread that. Will use stretch for future updates.
 -- Guido

> 
> Flagged for acceptance.
> 
> Regards,
> 
> Adam
> 

Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Adam D. Barratt]

On Sun, 2018-02-25 at 14:55 +, Chris Lamb wrote:
> Hi Stefan,
> 
> > According to bug report #850534, it should be fixed by version
> > 3.2.6-2,
> > but obviously that version is not available for Debian stable.
> 
> Actually… not so obvious! This should have been fixed in stable
> via #857746.
> 
> Emilio, you unblocked this in:
> 
>   https://bugs.debian.org/857746#10
> 
> .. but it does not seem to have actually hit stretch:
[...]
> What am I missing? :)
> 

#857855, which was RC at the time and (at least according to the
metadata) a regression relative to the package that was already in
stretch.

Regards,

Adam

Bug#873330: stretch-pu: package libosmium/2.11.4-1

[Sebastiaan Couwenberg]

Control: tags -1 - moreinfo

On 08/27/2017 10:36 PM, Sebastiaan Couwenberg wrote:
> On 08/27/2017 12:46 PM, Adam D. Barratt wrote:
>> On Sat, 2017-08-26 at 17:42 +0200, Bas Couwenberg wrote:
>>> Upstream has releases a new stable release of libosmium fixing important
>>> bugs which I'd like to propose for inclusion in the next stable update.
>>
>> So far as I can see, the change to memory/item.hpp has not yet been
>> applied to unstable.
> 
> The fix for buffers larger than 2^32 bytes is included in 2.13.0 [0],
> and we have 2.13.1 in unstable. The fix for 2.11.x [1] differs to
> minimize the impact on existing code.
> 
> [0] 
> https://github.com/osmcode/libosmium/commit/57d4f7c114f44af2ff258899be2296a931b8eb96
> [1] 
> https://github.com/osmcode/libosmium/commit/0d9516b16a510c7375b26933462ba294ed6eb8c7

Can we get this into the next point release as well?

Kind Regards,

Bas

Processed: Re: Bug#873330: stretch-pu: package libosmium/2.11.4-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #873330 [release.debian.org] stretch-pu: package libosmium/2.11.4-1
Removed tag(s) moreinfo.

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

Bug#888488: stretch-pu: package w3m/0.5.3-34+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-24 at 07:38 +0900, Tatsuya Kinoshita wrote:
> On February 23, 2018 at 4:46PM +, adam (at adam-barratt.org.uk)
> wrote:
> >> w3m (0.5.3-34+deb9u1) stretch; urgency=medium
> 
> > Please go ahead.
> 
> Uploaded.
> 

Flagged for acceptance.

Regards,

Adam

Bug#890105: stretch-pu: package uwsgi/2.0.14+20161117-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 19:13 +0100, Salvatore Bonaccorso wrote:
> Hi Adam,
> 
> On Fri, Feb 23, 2018 at 05:38:15PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Sun, 2018-02-11 at 11:10 +0100, Salvatore Bonaccorso wrote:
> > > +uwsgi (2.0.14+20161117-3+deb9u1) stretch; urgency=medium
> > > +
> > > +  * Non-maintainer upload.
> > > +  * Stack-based buffer overflow in uwsgi_expand_path function
> > > (CVE-
> > > 2018-6758)
> > > +(Closes: #889753)
> > > 
> > 
> > Please go ahead.
> 
> Thanks a lot, I have uploaded the package.
> 

Flagged for acceptance into p-u; thanks.

Regards,

Adam

Bug#888731: stretch-pu: package virt-what/1.15-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 18:50 +0100, Guido Günther wrote:
> On Fri, Feb 23, 2018 at 04:53:27PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2018-01-29 at 10:25 +0100, Guido Günther wrote:
> > > The update fixes problems with virt detection arch/aarch64 since
> > > these
> > > fall back to uname -m. x86 uses cpuid mostly so it went there
> > > undetected.
> > > 
> > 
> > +virt-what (1.15-1+deb9u1) stable-proposed-updates; urgency=medium
> > 
> > "stretch", please.
> > 
> > Please go ahead.
> 
> Uploaded. Thanks,

(Without the distribution change.)

Flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#888488: stretch-pu: package w3m/0.5.3-34+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #888488 [release.debian.org] stretch-pu: package w3m/0.5.3-34+deb9u1
Added tag(s) pending.

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

Processed: Re: Bug#890105: stretch-pu: package uwsgi/2.0.14+20161117-3+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #890105 [release.debian.org] stretch-pu: package 
uwsgi/2.0.14+20161117-3+deb9u1
Added tag(s) pending.

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

Processed: Re: Bug#888731: stretch-pu: package virt-what/1.15-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #888731 [release.debian.org] stretch-pu: package virt-what/1.15-1+deb9u1
Added tag(s) pending.

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

Re: wanna-build access for binNMUs

[Michael Stapelberg]

For the record, I generated
https://people.debian.org/~stapelberg/binNMUs-golang.txt and pochu
scheduled them to address the immediate need.

In the long run, pochu mentioned we should have a consumer for lists such
as the above which would automatically schedule the builds. This sidesteps
the wanna-build access question.

On Sat, Feb 17, 2018 at 9:07 AM, Emilio Pozuelo Monfort 
wrote:

> Sorry for the delay,
>
> On 11/02/18 14:28, Michael Stapelberg wrote:
> > On Sat, Feb 10, 2018 at 1:14 PM, Philipp Kern  wrote:
> >
> >> On 02/10/2018 09:26 AM, Julien Cristau wrote:
> >>> On Tue, Jan 30, 2018 at 20:45:44 +0100, Emilio Pozuelo Monfort wrote:
> >>>
>  On 30/01/18 08:54, Michael Stapelberg wrote:
> > This would also be very helpful for fixing security issue #888777.
> 
>  You need to talk to the wanna-build team if you want to be able to
> >> schedule
>  binNMUs for your language rebuilds, just like the ocaml and haskell
> >> teams do.
> 
> >>> FWIW I disagree, I think this is something the wanna-build team has
> >>> essentially delegated to release, so getting people on board is a
> shared
> >>> thing between those two teams rather than solely a w-b thing.  It
> >>> happens once every few years though so there isn't really a process to
> >>> vet people.
> >>
> >> So can we have an opinion on the current proposal, which is a single DD
> >> (stapelberg)? As far as I know DSA's ticket is currently blocked on
> this.
> >>
> >
> > nit: there’s no blocked ticket, but rather, once debian-release is okay
> > with the proposal, someone would need to file a ticket on my behalf. See
> my
> > other reply upthread:
> >
> >> Hector Oron pointed out in the Debian RT that the release-team should
> > give their okay before the PostgreSQL account can be created. This should
> > be done by way of the release team filing the Debian RT ticket on my
> > behalf, preferable as an inline signed email.
> >
> > If I understand https://www.debian.org/intro/organization correctly,
> > then pochu@ should be able to make this call. Given that no objections
> have
> > been voiced by anyone involved within the last two weeks since I asked
> for
> > access, may I suggest to go ahead? Thank you!
>
> As I said on IRC: please provide an automated list of required binNMUs,
> like the
> haskell one, so that if at some point you can't handle them for some time,
> others (e.g. me) can easily schedule them.
>
> Emilio
>



-- 
Best regards,
Michael

Processed: Re: Bug#889279: stretch-pu: package quota/4.03-2+b1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #889279 [release.debian.org] stretch-pu: package quota/4.03-2+b1
Added tag(s) pending.

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

Bug#887359: stretch-pu: package slic3r/1.2.9+dfsg-9~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 18:08 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-01-15 at 14:05 +0100, Andreas Beckmann wrote:
> > Next round for slic3r ... more searchpath fixes to find Slic3r.pm
> > in
> > the
> > private library directory, #886125.
> > Since all the additional fixes from unstable looked sane and
> > worthwile
> > to have in stable, I just rebuilt the sid package, like last time.
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#889279: stretch-pu: package quota/4.03-2+b1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:03 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2018-02-03 at 09:55 +0100, Michael Meskes wrote:
> > As reported in #888586 quotacheck may run into an endless loop
> > because it fails
> > to honor the non-interactive flag and still asks a question while
> > there is no
> > way to answer it. The proposed patch is already in Sid waiting to
> > migrate to
> > testing.
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#889983: stretch-pu: package glade/3.20.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 23:44 +0100, Sébastien Villemot wrote:
> On Fri, Feb 23, 2018 at 05:36:38PM +, Adam D. Barratt wrote:
> 
> > On Fri, 2018-02-09 at 18:12 +0100, Sébastien Villemot wrote:
> > > I prepared a p-u for glade, fixing #859324 (basically glade eats
> > > a
> > > lot of CPU
> > > as soon as a non-trivial UI is created).
> > > 
> > 
> > Please go ahead.
> 
> Thanks, uploaded.
> 
Flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#887359: stretch-pu: package slic3r/1.2.9+dfsg-9~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #887359 [release.debian.org] stretch-pu: package slic3r/1.2.9+dfsg-9~deb9u1
Added tag(s) pending.

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

Bug#889622: stretch-pu: package fuse-zip/0.4.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:28 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-02-05 at 14:12 +1100, Matthew Harm Bekkema wrote:
> > I'd like to update fuse-zip in stretch to fix a bug which prevents
> > it
> > from
> > writing changes back to zip files. I took upstream's patch and
> > applied it to the
> > version in stretch: https://bitbucket.org/agalanin/fuse-zip/commits
> > /9
> > b9c2f47cfe9
> > 
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#889983: stretch-pu: package glade/3.20.0-2+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #889983 [release.debian.org] stretch-pu: package glade/3.20.0-2+deb9u1
Added tag(s) pending.

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

Processed: Re: Bug#889622: stretch-pu: package fuse-zip/0.4.0-2+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #889622 [release.debian.org] stretch-pu: package fuse-zip/0.4.0-2+deb9u1
Added tag(s) pending.

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

Bug#890506: stretch-pu: package ntp/1:4.2.8p10+dfsg-3+deb9u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-24 at 22:42 +0100, Bernhard Schmidt wrote:
> On 23.02.2018 18:44, Adam D. Barratt wrote:
> 
> Hi Adam,
> 
> > On Thu, 2018-02-15 at 12:55 +0100, Bernhard Schmidt wrote:
> > > I'd like to update ntp in Stretch to fix Bug#887385. There have
> > > been
> > > numerous
> > > reports about ntpd segfaulting with the libc6 update from
> > > stretch-proposed-updates or in sid. It does not happen on all
> > > machines (I for
> > > one did not see it once).
> > > 
> > > There has been an upstream bug and an upstream patch to increase
> > > the
> > > stack size. This patch has been part of sid/buster for some weeks
> > > now
> > > and
> > > one of the reporters on the bug confirmed it being fixed.
> > > 
> > 
> > Please go ahead.
> 
> Uploaded and ACCEPTed.
> 

Flagged for acceptance into p-u.

Regards,

Adam

Processed: Re: Bug#887999: stretch-pu: package libhibernate-validator-java/4.3.3-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #887999 [release.debian.org] stretch-pu: package 
libhibernate-validator-java/4.3.3-1
Added tag(s) pending.

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

Processed: Re: Bug#887311: stretch-pu: package libperlx-assert-perl/0.904-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #887311 [release.debian.org] stretch-pu: package 
libperlx-assert-perl/0.904-1+deb9u1
Added tag(s) pending.

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

Bug#887999: stretch-pu: package libhibernate-validator-java/4.3.3-1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 19:29 +0100, Markus Koschany wrote:
> Am 23.02.2018 um 17:44 schrieb Adam D. Barratt:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2018-01-22 at 15:01 +0100, Markus Koschany wrote:
> > > I would like to fix CVE-2017-7536 in libhibernate-validator-java. 
> > > The
> > > issue is no-dsa but still worth fixing.
> > > 
> > 
> > Please go ahead.
> > 
> > Regards,
> > 
> > Adam
> 
> Uploaded. Thank you!
> 

Flagged for acceptance into p-u.

Regards,

Adam

Bug#886877: stretch-pu: package gosa-plugin-pwreset/0.99.4-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 18:02 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Wed, 2018-01-10 at 21:27 +0100, Mike Gabriel wrote:
> > We identified a deprecated constructor call in the PHP package
> > gosa-
> > plugin-pwreset.
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#890506: stretch-pu: package ntp/1:4.2.8p10+dfsg-3+deb9u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #890506 [release.debian.org] stretch-pu: package 
ntp/1:4.2.8p10+dfsg-3+deb9u2
Added tag(s) pending.

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

Processed: Re: Bug#886380: stretch-pu: package opendmarc/1.3.2-2+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #886380 [release.debian.org] stretch-pu: package opendmarc/1.3.2-2+deb9u1
Added tag(s) pending.

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

Bug#887311: stretch-pu: package libperlx-assert-perl/0.904-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 18:09 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sun, 2018-01-14 at 21:32 +0100, Andreas Beckmann wrote:
> > let's add a few missing perl packages to the dependecies: #868075
> > 
> > $ debdiff libperlx-assert-perl_0.904-1_all.deb libperlx-assert-
> > perl_0.904-1+deb9u1_all.deb
> > File lists identical (after any substitutions)
> > 
> > Control files: lines which differ (wdiff format)
> > 
> > Depends: libdevel-strictmode-perl, libexporter-tiny-perl,
> > {+libkeyword-simple-perl, libdevel-declare-perl,+} perl
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#886593: stretch-pu: package qtpass/1.1.6-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #886593 [release.debian.org] stretch-pu: package qtpass/1.1.6-1
Added tag(s) pending.

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

Bug#886589: stretch-pu: package mapproxy/1.9.0-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:57 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sun, 2018-01-07 at 22:19 +0100, Bas Couwenberg wrote:
> > To fix CVE-2017-1000426 an update of mapproxy for stretch has been
> > prepared, but the security team doesn't consider the issue severe
> > enough
> > to warrant a DSA.
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#888783: stretch-pu: package postfix/3.1.8-0+deb9u1

[Adam D. Barratt]

On Fri, 2018-02-23 at 16:56 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-01-29 at 16:14 -0500, Scott Kitterman wrote:
> > This update is intended to accomplish several improvements:
> 
> [...]
> > As usual, the postfix upstream is very careful and thorough in
> > micro-
> > release
> > updates and all the upstream changes are good things for our
> > users.  I have
> > the proposed package in production and have not noted any issues.
> 
> +postfix (3.1.8-0+deb9u1) stretch; urgency=medium
> +
> +[Scott Kitterman]
> +
> +  * Rewrite debian/postfix-instance-generator to avoid use of
> postmulti to fix
> +failures when inet_interfaces != all.  Closes: #882141
> 
> The indentation of the maintainer header looks strange there.

It still does, fwiw. :)

> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#886877: stretch-pu: package gosa-plugin-pwreset/0.99.4-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #886877 [release.debian.org] stretch-pu: package 
gosa-plugin-pwreset/0.99.4-1+deb9u1
Added tag(s) pending.

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

Bug#886593: stretch-pu: package qtpass/1.1.6-1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:59 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-01-08 at 00:17 +0100, Philip Rinn wrote:
> > the current version in stable has a insecure built-in password
> > generator. As
> > the built-in password generator not used in qtpass' default config,
> > the
> > security team asked me to fix it via stretch-pu.
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#886589: stretch-pu: package mapproxy/1.9.0-3+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #886589 [release.debian.org] stretch-pu: package mapproxy/1.9.0-3+deb9u1
Added tag(s) pending.

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

Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'

[Chris Lamb]

Hi Stefan,

> According to bug report #850534, it should be fixed by version 3.2.6-2,
> but obviously that version is not available for Debian stable.

Actually… not so obvious! This should have been fixed in stable
via #857746.

Emilio, you unblocked this in:

  https://bugs.debian.org/857746#10

.. but it does not seem to have actually hit stretch:

 redis | 2:1.2.6-1  | squeeze  | source
 redis | 2:2.4.14-1 | wheezy   | source
 redis | 2:2.4.14-1+deb7u2  | wheezy-security  | source
 redis | 2:2.8.17-1~bpo70+2 | wheezy-backports | source
 redis | 2:2.8.17-1 | jessie-kfreebsd  | source
 redis | 2:2.8.17-1+deb8u5  | jessie-kfreebsd-security | source
 redis | 2:2.8.17-1+deb8u5  | jessie-security  | source
 redis | 2:2.8.17-1+deb8u5  | jessie   | source
 redis | 2:3.0.5-4~bpo8+1   | jessie-backports | source
 redis | 3:3.2.6-1  | stretch  | source
 redis | 3:3.2.8-2~bpo8+1   | jessie-backports | source
 redis | 5:4.0.6-1  | sid  | source, all
 redis | 5:4.0.6-5  | sid  | source, all
 redis | 5:4.0.7-1~bpo9+1   | stretch-backports| source, all
 redis | 5:4.0.7-1  | buster   | source, all
 redis | 5:4.0.7-1  | sid  | source, all
 redis | 5:4.0.8-1  | sid  | source, all

What am I missing? :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#886380: stretch-pu: package opendmarc/1.3.2-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:54 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Thu, 2018-01-04 at 23:01 -0500, Scott Kitterman wrote:
> > As released, opendmarc doesn't read it's configuration file which
> > substantially limits the packages usefullness as
> > packaged/released.  The
> > attached debdiff changes the service file so the configuration file
> > is
> > actually used and adjusts the configuration file to match the
> > option
> > values
> > previously hard coded in the service file.
> > 
> 
> Please go ahead; sorry for the delay.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#888958: stretch-pu: package flatpak/0.8.9-0+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #888958 [release.debian.org] stretch-pu: package flatpak/0.8.9-0+deb9u1
Added tag(s) pending.

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

Bug#888958: stretch-pu: package flatpak/0.8.9-0+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 23:23 +, Simon McVittie wrote:
> On Fri, 23 Feb 2018 at 18:13:20 +, Adam D. Barratt wrote:
> > On Wed, 2018-01-31 at 15:41 +, Simon McVittie wrote:
> > > Alexander Larsson has released an update to the Flatpak 0.8.x
> > > branch,
> > > fixing a sandbox bypass reported by Gabriel Campana of the Google
> > > security
> > > team. It also contains a couple of other backported fixes. I
> > > would
> > > like
> > > to include this in the next stretch point release; I have a
> > > tested
> > > build
> > > ready for upload.
> > 
> > Please go ahead.
> 
> Thanks, uploaded.
> 

Flagged for acceptance.

Regards,

Adam

Processed: Re: unblock: redis/3:3.2.8-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 857746
Bug #857746 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] unblock: redis/3:3.2.8-2
Unarchived Bug 857746
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#889317: stretch-pu: package directfb/1.2.10.0-8

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #889317 [release.debian.org] stretch-pu: package directfb/1.2.10.0-8
Added tag(s) pending.

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

Bug#889317: stretch-pu: package directfb/1.2.10.0-8

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 23:26 +0100, Sebastian Ramacher wrote:
> On 2018-02-23 17:06:10, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Sat, 2018-02-03 at 16:00 +0100, Sebastian Ramacher wrote:
> > > I'd like to provide a fix for #878324 for the next stable point
> > > release. The
> > > issue was fixed in unstable shortly after 1.2.10.0-8 was uploaded
> > > in
> > > -9. That
> > > fix came to late for stretch (or I forgot to ask for an unblock).
> > > 
> > > The debdiff is:
> > > 
> > > --- a/debian/changelog
> > > +++ b/debian/changelog
> > > @@ -1,3 +1,10 @@
> > > +directfb (1.2.10.0-8+deb9u1) stretch; urgency=medium
> > > +
> > > +  * debian/libdirectfb-1.2-9.install: Fix architecture-based
> > > filter
> > > to
> > > +actually install drivers. (Closes: #878324)
> > > 
> > 
> > Please go ahead.
> 
> Thanks, uploaded.
> 

Flagged for acceptance.

Regards,

Adam

Processed: Re: Bug#891142: stretch-pu: package cups/2.2.1-8+

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #891142 [release.debian.org] stretch-pu: package cups/2.2.1-8+deb9u1
Added tag(s) pending.

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

Bug#891142: stretch-pu: package cups/2.2.1-8+

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 21:27 +0100, Didier 'OdyX' Raboud wrote:
> Le vendredi, 23 février 2018, 18.50:52 h CET Adam D. Barratt a écrit
> :
> > > The proposed debdiff is attached; can I upload to stretch?
> > 
> > Please go ahead.
> 
> Uploaded.
> 

Flagged for acceptance.

Regards,

Adam

Bug#891426: stretch-pu: package nvidia-modprobe/384.111-1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2018-02-25 at 15:02 +0100, Andreas Beckmann wrote:
> please allow the upgrade of nvidia-modprobe in stretch to a new
> upstream release matching the updated nvidia-graphics-drivers
> package.
> Since we build the driver components that are available as source
> ourselves (as separate packages) instead of shipping the binaries
> from
> the nvidia-graphics-drivers blob package, we will have to update
> several
> packages in stable this time. Mixing the driver component (major)
> versions is untested and likely unsupported by upstream (there are
> usually no relevant code changes between the minor releases of the
> same
> major series, only between different major branches).
> 

Please go ahead.

Regards,

Adam

Processed: Re: Bug#891426: stretch-pu: package nvidia-modprobe/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #891426 [release.debian.org] stretch-pu: package 
nvidia-modprobe/384.111-1~deb9u1
Added tag(s) confirmed.

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

Bug#891421: stretch-pu: package nvidia-xconfig/384.111-1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2018-02-25 at 14:25 +0100, Andreas Beckmann wrote:
> please allow the upgrade of nvidia-xconfig in stretch to a new
> upstream
> release matching the updated nvidia-graphics-drivers package.
> Since we build the driver components that are available as source
> ourselves (as separate packages) instead of shipping the binaries
> from
> the nvidia-graphics-drivers blob package, we will have to update
> several
> packages in stable this time. Mixing the driver component (major)
> versions is untested and likely unsupported by upstream (there are
> usually no relevant code changes between the minor releases of the
> same
> major series, only between different major branches).
> 

Please go ahead.

Regards,

Adam

Processed: Re: Bug#891421: stretch-pu: package nvidia-xconfig/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #891421 [release.debian.org] stretch-pu: package 
nvidia-xconfig/384.111-1~deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#891423: stretch-pu: package nvidia-persistenced/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #891423 [release.debian.org] stretch-pu: package 
nvidia-persistenced/384.111-1~deb9u1
Added tag(s) confirmed.

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

Bug#891423: stretch-pu: package nvidia-persistenced/384.111-1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2018-02-25 at 14:43 +0100, Andreas Beckmann wrote:
> please allow the upgrade of nvidia-persistenced in stretch to a new
> upstream release matching the updated nvidia-graphics-drivers
> package.
> Since we build the driver components that are available as source
> ourselves (as separate packages) instead of shipping the binaries
> from
> the nvidia-graphics-drivers blob package, we will have to update
> several
> packages in stable this time. Mixing the driver component (major)
> versions is untested and likely unsupported by upstream (there are
> usually no relevant code changes between the minor releases of the
> same
> major series, only between different major branches).
> 

Please go ahead.

Regards,

Adam

Processed: Re: nmu: rpy_1.0.3-30

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #886771 [release.debian.org] nmu: rpy_1.0.3-30 (stretch)
Added tag(s) confirmed.
> close 884209
Bug #884209 [release.debian.org] nmu: rpy_1.0.3-30 (sid)
Marked Bug as done

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

Bug#886771: nmu: rpy_1.0.3-30

[Adam D. Barratt]

Control: tags -1 + confirmed
Control: close 884209

On Sun, 2018-02-25 at 15:24 +0100, Andreas Beckmann wrote:
> On Tue, 12 Dec 2017 18:47:07 +0100 Andreas Beckmann 
> wrote:
> > nmu 2 rpy_1.0.3-30 . ANY . stretch . -m "Rebuild against r-base
> > 3.3"
> > nmu 3 rpy_1.0.3-30 . ANY . unstable . -m "Rebuild against r-base
> > 3.4"
> 
> Gentle ping to take a look at #884209/#886771 before the next stretch
> point release. I'm afraid the bugs are not tagged/labeled correctly
> s.t.
> they have fallen through the cracks.

Both scheduled.

Regards,

Adam

Bug#886771: nmu: rpy_1.0.3-30

[Andreas Beckmann]

On Tue, 12 Dec 2017 18:47:07 +0100 Andreas Beckmann  wrote:
> nmu 2 rpy_1.0.3-30 . ANY . stretch . -m "Rebuild against r-base 3.3"
> nmu 3 rpy_1.0.3-30 . ANY . unstable . -m "Rebuild against r-base 3.4"

Gentle ping to take a look at #884209/#886771 before the next stretch
point release. I'm afraid the bugs are not tagged/labeled correctly s.t.
they have fallen through the cracks.


Thanks

Andreas

Bug#891426: stretch-pu: package nvidia-modprobe/384.111-1~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Control: block 888909 with -1

Hi,

please allow the upgrade of nvidia-modprobe in stretch to a new
upstream release matching the updated nvidia-graphics-drivers package.
Since we build the driver components that are available as source
ourselves (as separate packages) instead of shipping the binaries from
the nvidia-graphics-drivers blob package, we will have to update several
packages in stable this time. Mixing the driver component (major)
versions is untested and likely unsupported by upstream (there are
usually no relevant code changes between the minor releases of the same
major series, only between different major branches).

This is a rebuild of the package from sid with no further changes
needed. It is also available in stretch-backports for a month without
any problems being reported.


Andreas


nvidia-modprobe_384.111-1~deb9u1.dsc.diff.xz
Description: application/xz

Processed: stretch-pu: package nvidia-modprobe/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> block 888909 with -1
Bug #888909 [release.debian.org] stretch-pu: package 
nvidia-graphics-drivers/384.111-4~deb9u1
888909 was blocked by: 891423 891419 891421
888909 was not blocking any bugs.
Added blocking bug(s) of 888909: 891426

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

Bug#888531: transition: ruby2.5 - binNMU round #3

[Emilio Pozuelo Monfort]

On 25/02/18 14:43, Antonio Terceiro wrote:
> Hi,
> 
> On Wed, Feb 21, 2018 at 09:33:44AM +0100, Emilio Pozuelo Monfort wrote:
>> On 07/02/18 01:21, Antonio Terceiro wrote:
>>> Please binNMU:
>>>
>>> libguestfs
>>> mapserver
>>> passenger
>>> nbdkit
>>
>> Any update here?
> 
> Almost all of the the missing packages build for the default version of
> Ruby, so they need to be binNMUed after the switch.
> 
> Apart from those, I would like to have ruby-json and ruby-rmagick fixed
> before doing the switch. However I could leave ruby-rmagick to be fixed
> after, but ruby-json has too many reverse dependencies for that. There
> is work underway on ruby-rmagick, and I will look into ruby-json today.
> 
> With ruby-json fixed, I would like to go ahead and do the switch. How
> does that sound?

Definitely fix ruby-json before doing the switch. Fixing ruby-rmagick would be
good too, I think we can wait a bit for those. Thanks for the update.

Emilio

Bug#888531: transition: ruby2.5 - binNMU round #3

[Antonio Terceiro]

Hi,

On Wed, Feb 21, 2018 at 09:33:44AM +0100, Emilio Pozuelo Monfort wrote:
> On 07/02/18 01:21, Antonio Terceiro wrote:
> > Please binNMU:
> > 
> > libguestfs
> > mapserver
> > passenger
> > nbdkit
> 
> Any update here?

Almost all of the the missing packages build for the default version of
Ruby, so they need to be binNMUed after the switch.

Apart from those, I would like to have ruby-json and ruby-rmagick fixed
before doing the switch. However I could leave ruby-rmagick to be fixed
after, but ruby-json has too many reverse dependencies for that. There
is work underway on ruby-rmagick, and I will look into ruby-json today.

With ruby-json fixed, I would like to go ahead and do the switch. How
does that sound?


signature.asc
Description: PGP signature

Bug#891423: stretch-pu: package nvidia-persistenced/384.111-1~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Control: block 888909 with -1

Hi,

please allow the upgrade of nvidia-persistenced in stretch to a new
upstream release matching the updated nvidia-graphics-drivers package.
Since we build the driver components that are available as source
ourselves (as separate packages) instead of shipping the binaries from
the nvidia-graphics-drivers blob package, we will have to update several
packages in stable this time. Mixing the driver component (major)
versions is untested and likely unsupported by upstream (there are
usually no relevant code changes between the minor releases of the same
major series, only between different major branches).

This is a rebuild of the package from sid with no further changes
needed. It is also available in stretch-backports for a month without
any problems being reported.


Andreas


nvidia-persistenced_384.111-1~deb9u1.dsc.diff.xz
Description: application/xz

Processed: stretch-pu: package nvidia-persistenced/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> block 888909 with -1
Bug #888909 [release.debian.org] stretch-pu: package 
nvidia-graphics-drivers/384.111-4~deb9u1
888909 was blocked by: 891419 891421
888909 was not blocking any bugs.
Added blocking bug(s) of 888909: 891423

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

Bug#891421: stretch-pu: package nvidia-xconfig/384.111-1~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Control: block 888909 with -1

Hi,

please allow the upgrade of nvidia-xconfig in stretch to a new upstream
release matching the updated nvidia-graphics-drivers package.
Since we build the driver components that are available as source
ourselves (as separate packages) instead of shipping the binaries from
the nvidia-graphics-drivers blob package, we will have to update several
packages in stable this time. Mixing the driver component (major)
versions is untested and likely unsupported by upstream (there are
usually no relevant code changes between the minor releases of the same
major series, only between different major branches).

This is a rebuild of the package from sid with no further changes
needed. It is also available in stretch-backports for a month without
any problems being reported.


Andreas


nvidia-xconfig_384.111-1~deb9u1.dsc.diff.xz
Description: application/xz

Processed: stretch-pu: package nvidia-xconfig/384.111-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> block 888909 with -1
Bug #888909 [release.debian.org] stretch-pu: package 
nvidia-graphics-drivers/384.111-4~deb9u1
888909 was blocked by: 891419
888909 was not blocking any bugs.
Added blocking bug(s) of 888909: 891421

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

Processed: block 888909 with 891419

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 888909 with 891419
Bug #888909 [release.debian.org] stretch-pu: package 
nvidia-graphics-drivers/384.111-4~deb9u1
888909 was not blocked by any bugs.
888909 was not blocking any bugs.
Added blocking bug(s) of 888909: 891419
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#891419: stretch-pu: package nvidia-settings/384.111-1~deb9u1

[Andreas Beckmann]

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

Hi,

please allow the upgrade of nvidia-settings in stretch to a new upstream
release matching the updated nvidia-graphics-drivers package.
There are versioned Recommends in the driver packages that cannot be
satisfied by the older nvidia-settings version in stretch.
Since we build the driver components that are available as source
ourselves instead of shipping the binaries from the
nvidia-graphics-drivers blob package, we will have to update several
packages in stable this time. Mixing the driver component versions is
untested and unsupported by upstream.

This is a rebuild of the package from sid with no further changes
needed. It is also available in stretch-backports for a month without
any problems being reported.


Andreas


nvidia-settings_384.111-1~deb9u1.dsc.diff.xz
Description: application/xz

Processed: Bug#882697: stretch-pu: package apparmor/2.11.0-3+deb9u2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #882697 [release.debian.org] stretch-pu: package apparmor/2.11.0-3+deb9u1
Removed tag(s) moreinfo.
> retitle -1 stretch-pu: package apparmor/2.11.0-3+deb9u2
Bug #882697 [release.debian.org] stretch-pu: package apparmor/2.11.0-3+deb9u1
Changed Bug title to 'stretch-pu: package apparmor/2.11.0-3+deb9u2' from 
'stretch-pu: package apparmor/2.11.0-3+deb9u1'.

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

Bug#882697: stretch-pu: package apparmor/2.11.0-3+deb9u2

[intrigeri]

Control: tag -1 - moreinfo
Control: retitle -1 stretch-pu: package apparmor/2.11.0-3+deb9u2

Hi,

here's the updated debdiff; I've bumped the version in order to
avoid confusion.

This will now work fine except for Linux 4.14 to 4.14.12 that have the
bug which prevented us from including apparmor 2.11.0-3+deb9u1 in the
previous point release. The kernel fix has been in sid since
2018-01-15, in stretch-backports since 2018-01-16, and in testing
since 2018-01-20. So IMO the benefit (repairing stuff for Stretch
users running an up-to-date backported kernel) is worth the risk
(breaking stuff for Stretch users running an outdated Linux 4.14.x).

May I upload (with s/UNRELEASED/stretch/ of course)?

Cheers,
-- 
intrigeri

diff -Nru apparmor-2.11.0/debian/apparmor.install apparmor-2.11.0/debian/apparmor.install
--- apparmor-2.11.0/debian/apparmor.install	2017-03-28 12:23:08.0 +0200
+++ apparmor-2.11.0/debian/apparmor.install	2018-02-25 11:21:24.0 +0100
@@ -1,4 +1,5 @@
 debian/apport/source_apparmor.py /usr/share/apport/package-hooks/
+debian/features /usr/share/apparmor-features/
 debian/lib/apparmor/functions /lib/apparmor/
 debian/lib/apparmor/profile-load /lib/apparmor/
 etc/apparmor/parser.conf
diff -Nru apparmor-2.11.0/debian/changelog apparmor-2.11.0/debian/changelog
--- apparmor-2.11.0/debian/changelog	2017-03-28 12:29:15.0 +0200
+++ apparmor-2.11.0/debian/changelog	2018-02-25 11:21:24.0 +0100
@@ -1,3 +1,16 @@
+apparmor (2.11.0-3+deb9u2) UNRELEASED; urgency=medium
+
+  * Pin the AppArmor feature set to Stretch's kernel (Closes: #879585).
+This ensures Stretch systems, even when running a newer kernel (e.g.
+from backports), have their AppArmor feature set pinned to the one
+supported by the AppArmor policy shipped in Stretch. Otherwise they
+would experience breakage due to new AppArmor mediation features
+introduced in recent kernels.
+  * Configure gbp for DEP-14 and avoid gbp-pq prefixing patches
+with numbers.
+
+ -- intrigeri   Sun, 25 Feb 2018 10:21:24 +
+
 apparmor (2.11.0-3) unstable; urgency=medium
 
   * Fix CVE-2017-6507: don't unload unknown profiles during package
diff -Nru apparmor-2.11.0/debian/features apparmor-2.11.0/debian/features
--- apparmor-2.11.0/debian/features	1970-01-01 01:00:00.0 +0100
+++ apparmor-2.11.0/debian/features	2018-02-25 11:21:24.0 +0100
@@ -0,0 +1,23 @@
+caps {mask {chown dac_override dac_read_search fowner fsetid kill setgid setuid setpcap linux_immutable net_bind_service net_broadcast net_admin net_raw ipc_lock ipc_owner sys_module sys_rawio sys_chroot sys_ptrace sys_pacct sys_admin sys_boot sys_nice sys_resource sys_time sys_tty_config mknod lease audit_write audit_control setfcap mac_override mac_admin syslog wake_alarm block_suspend audit_read
+}
+}
+rlimit {mask {cpu fsize data stack core rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime
+}
+}
+capability {0xff
+}
+file {mask {create read write exec append mmap_exec link lock
+}
+}
+domain {change_profile {yes
+}
+change_onexec {yes
+}
+change_hatv {yes
+}
+change_hat {yes
+}
+}
+policy {set_load {yes
+}
+}
diff -Nru apparmor-2.11.0/debian/gbp.conf apparmor-2.11.0/debian/gbp.conf
--- apparmor-2.11.0/debian/gbp.conf	1970-01-01 01:00:00.0 +0100
+++ apparmor-2.11.0/debian/gbp.conf	2018-02-25 11:21:24.0 +0100
@@ -0,0 +1,6 @@
+[DEFAULT]
+pristine-tar = True
+debian-branch = debian/stretch
+upstream-branch = upstream/latest
+upstream-vcs-tag = v%(version)s
+patch-numbers = False
diff -Nru apparmor-2.11.0/debian/patches/pin-feature-set.patch apparmor-2.11.0/debian/patches/pin-feature-set.patch
--- apparmor-2.11.0/debian/patches/pin-feature-set.patch	1970-01-01 01:00:00.0 +0100
+++ apparmor-2.11.0/debian/patches/pin-feature-set.patch	2018-02-25 11:21:24.0 +0100
@@ -0,0 +1,18 @@
+Description: pin the AppArmor feature set to the one shipped by the apparmor package
+ .
+ Let's smooth UX on kernel upgrades and allow ourselves to update the AppArmor
+ policy in a relaxed manner.
+Bug-Debian: https://bugs.debian.org/879585
+Forwarded: not-needed
+Author: intrigeri 
+
+--- a/parser/parser.conf
 b/parser/parser.conf
+@@ -59,3 +59,7 @@
+ ## Adjust compression
+ #Optimize=compress-small
+ #Optimize=compress-fast
++
++## Pin feature set (avoid regressions when policy is lagging behind
++## the kernel)
++features-file=/usr/share/apparmor-features/features
diff -Nru apparmor-2.11.0/debian/patches/series apparmor-2.11.0/debian/patches/series
--- apparmor-2.11.0/debian/patches/series	2017-03-28 12:24:44.0 +0200
+++ apparmor-2.11.0/debian/patches/series	2018-02-25 11:21:24.0 +0100
@@ -2,6 +2,7 @@
 # Debian-specific patches
 #
 
+pin-feature-set.patch
 notify-group.patch
 
 #

Bug#891415: stretch-pu: package psad/2.4.3-1.2~deb9u1

[Andreas Beckmann]

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

Let's add a few missing dependencies to psad by rebuilding the package
from sid.


Andreas
diff -Nru psad-2.4.3/debian/changelog psad-2.4.3/debian/changelog
--- psad-2.4.3/debian/changelog 2016-09-30 20:40:12.0 +0200
+++ psad-2.4.3/debian/changelog 2018-02-25 12:42:49.0 +0100
@@ -1,3 +1,24 @@
+psad (2.4.3-1.2~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 25 Feb 2018 12:42:49 +0100
+
+psad (2.4.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on iproute2. (Closes: #867914)
+
+ -- Adrian Bunk   Sat, 03 Feb 2018 14:53:36 +0200
+
+psad (2.4.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on net-tools. (Closes: #867914)
+
+ -- Adrian Bunk   Sun, 06 Aug 2017 13:38:41 +0300
+
 psad (2.4.3-1) unstable; urgency=low
 
   * New upstream release 2.4.3
diff -Nru psad-2.4.3/debian/control psad-2.4.3/debian/control
--- psad-2.4.3/debian/control   2016-09-29 22:04:05.0 +0200
+++ psad-2.4.3/debian/control   2018-02-03 13:53:36.0 +0100
@@ -15,7 +15,7 @@
  libnet-ip-perl, libdate-calc-perl, libcarp-clan-perl,
  whois, psmisc, libiptables-parse-perl, libiptables-chainmgr-perl,
  default-mta | mail-transport-agent, bsd-mailx | mailx | mailutils,
- lsb-base
+ lsb-base, net-tools, iproute2
 Suggests: fwsnort
 Description: Port Scan Attack Detector
  PSAD is a collection of four lightweight system daemons (in Perl and

Bug#871056: transition: openssl

[Emilio Pozuelo Monfort]

On 12/10/17 10:56, Emilio Pozuelo Monfort wrote:
> On 21/09/17 21:39, Sebastian Andrzej Siewior wrote:
>> On 2017-09-13 18:51:43 [+0200], Emilio Pozuelo Monfort wrote:
>>> tags 871056 confirmed
>>> thanks
>>
>> just noticed that this bug has been confirmed. Does this mean anything
>> for the openssl transition? Usually this confirmed comes with "Go ahead"
>> which leads to an upload to unstable and the severity of the blocker
>> bugs is raised to serious.
>> Should the severity of the blocker bugs be raised or do we keep things
>> as they are for now?
> 
> As we discussed on the last release team meeting: let's do this, but first 
> send
> a 'warning' saying that the bugs will be bumped in a month, and do the bump
> later. That will give maintainers more time to react before the auto-removal
> kicks in.

We're getting close. According to the transition tracker, the remaining rdeps in
testing are:

netty-tcnative - fixed upstream
omniorb-dfsg - fixed in experimental
ruby2.3 - ongoing transition to ruby2.5, then this will be removed
xml-security-c - no fix, but upstream said it would get fixed "this year"
ipsec-tools - no fix, but due for autoremoval
openssh - Kurt has worked on a fix with upstream
qtbase-opensource-src - fixed in experimental, we need a Qt transition
curl - transition pending
kopete - no fix upstream, optional for jingle (call) support in XMPP
xmltooling - same as xml-security-c
zurl - blocked on curl

Hopefully we get those transitions done soon and the rest get some progress too.

Cheers,
Emilio

Processed: Re: Bug#891346: RM: jirc/1.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = jessie
Bug #891346 [release.debian.org] RM: jirc/1.0-1
Removed tag(s) stretch.
> clone -1 -2
Bug #891346 [release.debian.org] RM: jirc/1.0-1
Bug 891346 cloned as bug 891403
> tags -2 = stretch
Bug #891403 [release.debian.org] RM: jirc/1.0-1
Added tag(s) stretch; removed tag(s) jessie.

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