Bug#926162: unblock: opensaml/3.0.1-1

2019-04-01 Thread wferi 
Control: tags -1 - moreinfo

Niels Thykier  writes:

> Please go ahead with the upload and remove the moreinfo tag when it is
> ready for unblocking.

Hi, opensaml 3.0.1-1 is already in unstable, ready for unblocking.
-- 
Thanks,
Feri

Processed: Re: Bug#926162: unblock: opensaml/3.0.1-1

2019-04-01 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo
Bug #926162 [release.debian.org] unblock: opensaml/3.0.1-1
Removed tag(s) moreinfo.

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

Bug#925357: marked as done (unblock: tomoyo-tools/2.6.0-20190305-1)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Tue, 2 Apr 2019 15:21:19 +0900
with message-id <20190402152119.0c85ec228d1bfbae6d6d8...@iijmio-mail.jp>
and subject line Re: Bug#925357: unblock: tomoyo-tools/2.6.0-20190305-1
has caused the Debian Bug report #925357,
regarding unblock: tomoyo-tools/2.6.0-20190305-1
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.)


-- 
925357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package tomoyo-tools

* I'd like to push tomoyo 2.6.0 for buster, since less upstream delta is
  better to reduce maintain cost.
* tomoyo-tools is leaf package, no worries about breaking other packages'
  behavior :) (and it's stable enough, IMHO).

 The blocker for update is debdiff is huge.

> $ wc -l tomoyo.debdiff
>   
> 
> 1528 tomoyo.debdiff

 However, most of above changes are almost same boring changes like this.

 diff -Nru tomoyo-tools-2.5.0-20170102/examples/candy.c 
tomoyo-tools-2.6.0-20190305/examples/candy.c
--- tomoyo-tools-2.5.0-20170102/examples/candy.c2017-01-04 
19:12:17.0 +0900
+++ tomoyo-tools-2.6.0-20190305/examples/candy.c2019-03-05 
09:00:00.0 +0900
@@ -2,11 +2,11 @@
  * candy.c
  *
  * An example program for CERBERUS.
- * ( http://osdn.jp/projects/tomoyo/document/winf2005-en.pdf )
+ * ( https://osdn.jp/projects/tomoyo/document/winf2005-en.pdf )
  *
  * Copyright (C) 2005-2011  NTT DATA CORPORATION
  *
- * Version: 2.5.0   2011/09/29
+ * Version: 2.6.0   2019/03/05
  *
  * This program is free software; you can redistribute it and/or modify it
  * under the terms of the GNU General Public License v2 as published by the

 URL change (use https), version and date update. I've striped down such
 things and diff size becomes just 255 lines (= upstream changes).

> $ wc -l tomoyo.diff 
> 255 tomoyo.diff

 And 1/3 of that is test file, remains are changes to update profile version.

diff --git a/kernel_test/tomoyo_bprm_test.c b/kernel_test/tomoyo_bprm_test.c
index c19d89e..1675ea6 100644
--- a/kernel_test/tomoyo_bprm_test.c
+++ b/kernel_test/tomoyo_bprm_test.c
@@ -178,6 +178,7 @@ int main(int argc, char *argv[])
ccs_test_init();
fprintf(domain_fp, "%s " BINDIR "/true\n", self_domain);
fprintf(domain_fp, "use_profile 255\n");
+   fprintf(domain_fp, "use_group 0\n");
fprintf(domain_fp, "select pid=%u\n", pid);
fprintf(domain_fp, "file read/write %s\n", proc_policy_domain_policy);
set_profile(3, "file::execute");
diff --git a/kernel_test/tomoyo_cond_test.c b/kernel_test/tomoyo_cond_test.c
index 123a2be..da5905d 100644
--- a/kernel_test/tomoyo_cond_test.c
+++ b/kernel_test/tomoyo_cond_test.c
@@ -388,7 +388,10 @@ static void stage_cond_test(void)
 int main(int argc, char *argv[])
 {
ccs_test_init();
-   fprintf(domain_fp, "ignore_global\n");
+   fprintf(domain_fp, "%s " BINDIR "/true\n", self_domain);
+   fprintf(domain_fp, "use_profile 255\n");
+   fprintf(domain_fp, "use_group 0\n");
+   fprintf(domain_fp, "%s\n", self_domain);
fprintf(domain_fp, "file read/write %s\n", proc_policy_domain_policy);
set_profile(3, "file::execute");
set_profile(3, "file::open");
diff --git a/kernel_test/tomoyo_new_file_test.c 
b/kernel_test/tomoyo_new_file_test.c
index 827c595..9c8ed87 100644
--- a/kernel_test/tomoyo_new_file_test.c
+++ b/kernel_test/tomoyo_new_file_test.c
@@ -118,6 +118,7 @@ static void stage_file_test(void)
size_t size = sizeof(buffer);
int pipe_fd[2] = { EOF, EOF };
int err = 0;
+   int flags;
int fd;
char pbuffer[1024];
struct stat sbuf;
@@ -184,6 +185,38 @@ static void stage_file_test(void)
write_domain_policy(policy, 1);
show_result(uselib("/tmp/uselib"), 0);
 
+   policy = "file write /dev/null";
+   fd = open("/dev/null", O_WRONLY);
+   show_result(fd, 0);
+   close(fd);
+   write_domain_policy(policy, 0);
+   fd = open("/dev/null", O_WRONLY);
+   show_result(fd, 1);
+   write_domain_policy(policy, 1);
+   flags = fcntl(fd, F_GETFL, 0) | O_APPEND;
+   policy = "file append /dev/null";
+   show_result(fcntl(fd, F_SETFL, flags), 0);
+   write_domain_policy(policy, 0);
+   show_result(fcntl(fd, F_SETFL, flags), 1);
+

Bug#925350: unblock: ubuntu-keyring/2018.09.18.1-5

2019-04-01 Thread Hideki Yamane 
On Sat, 23 Mar 2019 23:36:50 +0900 Hideki Yamane  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock

 Should I provide any other info for unblocking this?


-- 
Hideki Yamane

Bug#926203: marked as done (unblock: pacemaker/2.0.1-2)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Tue, 02 Apr 2019 05:42:00 +
with message-id 
and subject line Re: Bug#926203: unblock: pacemaker/2.0.1-2
has caused the Debian Bug report #926203,
regarding unblock: pacemaker/2.0.1-2
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.)


-- 
926203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pacemaker

Dear Release Team,

As reported in #925354, the newly reintroduced pacemaker-dev package
missed Breaks+Replaces against some long-obsolete packages from wheezy,
leading to file conflicts in certain situations.  The version already in
unstable fixes this bug, please unblock it.

Thanks,
Feri.

diff -Nru pacemaker-2.0.1/debian/changelog pacemaker-2.0.1/debian/changelog
--- pacemaker-2.0.1/debian/changelog2019-03-04 21:34:46.0 +0100
+++ pacemaker-2.0.1/debian/changelog2019-04-01 13:39:28.0 +0200
@@ -1,3 +1,19 @@
+pacemaker (2.0.1-2) unstable; urgency=medium
+
+  * [d8939cc] Avoid file conflicts with leftover packages from wheezy.
+Pacemaker-dev in wheezy was a metapackage pulling in several -dev
+packages.  It is removed during the jessie dist-upgrade due to
+dependency problems, and jessie does not have pacemaker at all, so these
+obsolete -dev packages are left behind, unless replaced by the
+renamed -dev packages from jessie-backports or later from stretch, both
+of which requires manual action.  Lacking that, a manual install of the
+reintroduced pacemaker-dev from buster will try to overwrite headers
+from those obsolete -dev packages causing file conflicts, because the
+old Breaks+Replaces relations weren't carried over from the stretch
+packages. (Closes: #925354)
+
+ -- Ferenc Wágner   Mon, 01 Apr 2019 13:39:28 +0200
+
 pacemaker (2.0.1-1) unstable; urgency=medium
 
   * [7d6ff2e] New upstream release (2.0.1)
diff -Nru pacemaker-2.0.1/debian/control pacemaker-2.0.1/debian/control
--- pacemaker-2.0.1/debian/control  2019-03-04 21:30:38.0 +0100
+++ pacemaker-2.0.1/debian/control  2019-03-29 09:06:28.0 +0100
@@ -332,6 +332,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Replaces:
  libcib-dev (<< 2),
  libcrmcluster-dev (<< 2),
@@ -340,6 +344,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Description: cluster resource manager development
  ${S:X-Common-Description}
  .

unblock pacemaker/2.0.1-2
--- End Message ---
--- Begin Message ---
Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package pacemaker
> 
> Dear Release Team,
> 
> As reported in #925354, the newly reintroduced pacemaker-dev package
> missed Breaks+Replaces against some long-obsolete packages from wheezy,
> leading to file conflicts in certain situations.  The version already in
> unstable fixes this bug, please unblock it.
> 
> Thanks,
> Feri.
> 
> [...]
> 
> unblock pacemaker/2.0.1-2
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926206: marked as done (unblock: espeakup/1:0.80-14)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Tue, 02 Apr 2019 05:40:00 +
with message-id <995e0ca3-0130-3638-8da7-513322431...@thykier.net>
and subject line Re: Bug#926206: unblock: espeakup/1:0.80-14
has caused the Debian Bug report #926206,
regarding unblock: espeakup/1:0.80-14
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.)


-- 
926206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,

Please unblock package espeakup: as reported in Bug#925973, the current
version of espeakup would stop it on preinst and start it on postinst.
For a screen reader for blind users this is really bad because if
anything goes wrong in between, the user is left without a screen
reader. We should thus pass --restart-after-upgrade to dh_systemd_start
to just restart the screen reader after successful upgrade.

Cc-ing kibi because of the udeb: this doesn't have any effect on the
udeb.

unblock espeakup/1:0.80-14

Thanks!

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (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 5.0.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE
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)

-- 
Samuel
il y a 10 catégories de personnes dans le monde : ceux qui comprennent le
binaire, et ceux qui ne le comprennent pas
diff -Nru espeakup-0.80/debian/changelog espeakup-0.80/debian/changelog
--- espeakup-0.80/debian/changelog  2019-02-20 15:44:59.0 +0100
+++ espeakup-0.80/debian/changelog  2019-03-29 17:03:23.0 +0100
@@ -1,3 +1,9 @@
+espeakup (1:0.80-14) unstable; urgency=medium
+
+  * rules: Restart espeakup after upgrade (Closes: Bug#925973).
+
+ -- Samuel Thibault   Fri, 29 Mar 2019 17:03:23 +0100
+
 espeakup (1:0.80-13) unstable; urgency=medium
 
   * debian/espeakup.finish-install: Fix writing down card id.
diff -Nru espeakup-0.80/debian/rules espeakup-0.80/debian/rules
--- espeakup-0.80/debian/rules  2019-01-01 17:07:20.0 +0100
+++ espeakup-0.80/debian/rules  2019-03-29 17:03:23.0 +0100
@@ -41,3 +41,6 @@
 override_dh_gencontrol:
echo 'espeak-ng:Version=$(ESPEAK_NG_VERSION)' >> 
debian/espeakup-udeb.substvars
dh_gencontrol
+
+override_dh_systemd_start:
+   dh_systemd_start --restart-after-upgrade
--- End Message ---
--- Begin Message ---
Samuel Thibault:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello,
> 
> Please unblock package espeakup: as reported in Bug#925973, the current
> version of espeakup would stop it on preinst and start it on postinst.
> For a screen reader for blind users this is really bad because if
> anything goes wrong in between, the user is left without a screen
> reader. We should thus pass --restart-after-upgrade to dh_systemd_start
> to just restart the screen reader after successful upgrade.
> 
> Cc-ing kibi because of the udeb: this doesn't have any effect on the
> udeb.
> 
> unblock espeakup/1:0.80-14
> 
> Thanks!
> 
> [...]
> 

Unblocked by ivodd, thanks.
~Niels--- End Message ---

Bug#926206: unblock: espeakup/1:0.80-14

2019-04-01 Thread Cyril Brulebois 
Samuel Thibault  (2019-04-02):
> Please unblock package espeakup: as reported in Bug#925973, the current
> version of espeakup would stop it on preinst and start it on postinst.
> For a screen reader for blind users this is really bad because if
> anything goes wrong in between, the user is left without a screen
> reader. We should thus pass --restart-after-upgrade to dh_systemd_start
> to just restart the screen reader after successful upgrade.
> 
> Cc-ing kibi because of the udeb: this doesn't have any effect on the
> udeb.

Thanks for that; no objections.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#926206: unblock: espeakup/1:0.80-14

2019-04-01 Thread Samuel Thibault 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,

Please unblock package espeakup: as reported in Bug#925973, the current
version of espeakup would stop it on preinst and start it on postinst.
For a screen reader for blind users this is really bad because if
anything goes wrong in between, the user is left without a screen
reader. We should thus pass --restart-after-upgrade to dh_systemd_start
to just restart the screen reader after successful upgrade.

Cc-ing kibi because of the udeb: this doesn't have any effect on the
udeb.

unblock espeakup/1:0.80-14

Thanks!

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (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 5.0.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE
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)

-- 
Samuel
il y a 10 catégories de personnes dans le monde : ceux qui comprennent le
binaire, et ceux qui ne le comprennent pas
diff -Nru espeakup-0.80/debian/changelog espeakup-0.80/debian/changelog
--- espeakup-0.80/debian/changelog  2019-02-20 15:44:59.0 +0100
+++ espeakup-0.80/debian/changelog  2019-03-29 17:03:23.0 +0100
@@ -1,3 +1,9 @@
+espeakup (1:0.80-14) unstable; urgency=medium
+
+  * rules: Restart espeakup after upgrade (Closes: Bug#925973).
+
+ -- Samuel Thibault   Fri, 29 Mar 2019 17:03:23 +0100
+
 espeakup (1:0.80-13) unstable; urgency=medium
 
   * debian/espeakup.finish-install: Fix writing down card id.
diff -Nru espeakup-0.80/debian/rules espeakup-0.80/debian/rules
--- espeakup-0.80/debian/rules  2019-01-01 17:07:20.0 +0100
+++ espeakup-0.80/debian/rules  2019-03-29 17:03:23.0 +0100
@@ -41,3 +41,6 @@
 override_dh_gencontrol:
echo 'espeak-ng:Version=$(ESPEAK_NG_VERSION)' >> 
debian/espeakup-udeb.substvars
dh_gencontrol
+
+override_dh_systemd_start:
+   dh_systemd_start --restart-after-upgrade

Processed: tagging 926188

2019-04-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 926188 - moreinfo
Bug #926188 [release.debian.org] unblock: postfix/3.4.5-1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#926123: marked as done (unblock: cabextract/1.9-2)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 1 Apr 2019 22:46:36 +0200
with message-id <86d2b29e-a3d8-1d6e-f733-33b7dfe0e...@gmail.com>
and subject line Re: Bug#926123: unblock: cabextract/1.9-2
has caused the Debian Bug report #926123,
regarding unblock: cabextract/1.9-2
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.)


-- 
926123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

block -1 by 926118


Hi

Please unblock package cabextract

I'm not the maintainer of cabextract, but of winetricks which is affected by
#914263 (cabextract: -F option doesn't work correctly.)

#914263 is a duplicate of #912687 (libmspack0: Regression when extracting
cabinets using -F
option fixed upstream, needs to be patched), see my previous unblock request
#926118.  It was fixed by:

cabextract (1.9-2) unstable; urgency=medium

  * Force libmspack0 version >= 0.9.1-1 to avoid bugs in that
package: Closes: #914263

 -- Eric Sharkey   Sun, 09 Dec 2018 08:06:55 -0500

Other changes I found in the debdiff:
- Bump debhelper version from 7 to 11
- Bump Standards-Version from 3.9.6 to 4.2.1
- d/rules target install: build
  drop dh_clean -k, add dh_prep


This unblock of cabextract is not strictly necessary for a pure Debian stable,
but might help e.g. derivatives.  If I'm wasting your time here, please just
NACK and close this report.


unblock cabextract/1.9-2


Thanks and greets
jre



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

Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
diffstat for cabextract-1.9 cabextract-1.9

 changelog |7 +++
 compat|2 +-
 control   |6 +++---
 rules |2 +-
 4 files changed, 12 insertions(+), 5 deletions(-)

diff -Nru cabextract-1.9/debian/changelog cabextract-1.9/debian/changelog
--- cabextract-1.9/debian/changelog 2018-11-11 17:46:01.0 +0100
+++ cabextract-1.9/debian/changelog 2018-12-09 14:06:55.0 +0100
@@ -1,3 +1,10 @@
+cabextract (1.9-2) unstable; urgency=medium
+
+  * Force libmspack0 version >= 0.9.1-1 to avoid bugs in that
+package: Closes: #914263
+
+ -- Eric Sharkey   Sun, 09 Dec 2018 08:06:55 -0500
+
 cabextract (1.9-1) unstable; urgency=medium
 
   * New upstream release: Closes: #913007
diff -Nru cabextract-1.9/debian/compat cabextract-1.9/debian/compat
--- cabextract-1.9/debian/compat2018-11-11 17:20:41.0 +0100
+++ cabextract-1.9/debian/compat2018-12-09 14:06:55.0 +0100
@@ -1 +1 @@
-7
+11
diff -Nru cabextract-1.9/debian/control cabextract-1.9/debian/control
--- cabextract-1.9/debian/control   2018-11-11 17:46:01.0 +0100
+++ cabextract-1.9/debian/control   2018-12-09 14:06:55.0 +0100
@@ -2,12 +2,12 @@
 Section: utils
 Priority: optional
 Maintainer: Eric Sharkey 
-Build-Depends: debhelper (>= 7), sharutils, libmspack-dev, pkg-config, 
automake-1.15
-Standards-Version: 3.9.6
+Build-Depends: debhelper (>= 11), sharutils, libmspack-dev, pkg-config, 
automake-1.15
+Standards-Version: 4.2.1
 
 Package: cabextract
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: libmspack0 (>= 0.9.1-1), ${shlibs:Depends}, ${misc:Depends}
 Multi-Arch: foreign
 Enhances: konqueror
 Description: Microsoft Cabinet file unpacker
diff -Nru cabextract-1.9/debian/rules cabextract-1.9/debian/rules
--- cabextract-1.9/debian/rules 2018-11-11 17:46:01.0 +0100
+++ cabextract-1.9/debian/rules 2018-12-09 14:06:55.0 +0100
@@ -44,7 +44,7 @@
 install: build
dh_testdir
dh_testroot
-   dh_clean -k
+   dh_prep
dh_installdirs
 
# Add here commands to install the package into debian/cabextract.
--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo

On 01.04.19 20:16, Eric Sharkey wrote:
> On Sun, Mar 31, 2019 at 3:58 PM Jens Reyer  wrote:
> 
>> Passing on Jonathan's question to you.
>>
>> [..]
>> The debhelper compat change is a problem. Would you or the maintainer be
>> interested in an upload reverting it?
>>
> 
>

Bug#926203: unblock: pacemaker/2.0.1-2

2019-04-01 Thread Ferenc Wágner 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pacemaker

Dear Release Team,

As reported in #925354, the newly reintroduced pacemaker-dev package
missed Breaks+Replaces against some long-obsolete packages from wheezy,
leading to file conflicts in certain situations.  The version already in
unstable fixes this bug, please unblock it.

Thanks,
Feri.

diff -Nru pacemaker-2.0.1/debian/changelog pacemaker-2.0.1/debian/changelog
--- pacemaker-2.0.1/debian/changelog2019-03-04 21:34:46.0 +0100
+++ pacemaker-2.0.1/debian/changelog2019-04-01 13:39:28.0 +0200
@@ -1,3 +1,19 @@
+pacemaker (2.0.1-2) unstable; urgency=medium
+
+  * [d8939cc] Avoid file conflicts with leftover packages from wheezy.
+Pacemaker-dev in wheezy was a metapackage pulling in several -dev
+packages.  It is removed during the jessie dist-upgrade due to
+dependency problems, and jessie does not have pacemaker at all, so these
+obsolete -dev packages are left behind, unless replaced by the
+renamed -dev packages from jessie-backports or later from stretch, both
+of which requires manual action.  Lacking that, a manual install of the
+reintroduced pacemaker-dev from buster will try to overwrite headers
+from those obsolete -dev packages causing file conflicts, because the
+old Breaks+Replaces relations weren't carried over from the stretch
+packages. (Closes: #925354)
+
+ -- Ferenc Wágner   Mon, 01 Apr 2019 13:39:28 +0200
+
 pacemaker (2.0.1-1) unstable; urgency=medium
 
   * [7d6ff2e] New upstream release (2.0.1)
diff -Nru pacemaker-2.0.1/debian/control pacemaker-2.0.1/debian/control
--- pacemaker-2.0.1/debian/control  2019-03-04 21:30:38.0 +0100
+++ pacemaker-2.0.1/debian/control  2019-03-29 09:06:28.0 +0100
@@ -332,6 +332,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Replaces:
  libcib-dev (<< 2),
  libcrmcluster-dev (<< 2),
@@ -340,6 +344,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Description: cluster resource manager development
  ${S:X-Common-Description}
  .

unblock pacemaker/2.0.1-2

Processed: submitter 926199

2019-04-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> submitter 926199 Rene Engelhard 
Bug #926199 [release.debian.org] stretch-pu: package 
libreoffice/1:5.2.7-1+deb9u6
Changed Bug submitter to 'Rene Engelhard ' from 'Rene 
Engelhard '.
> thanks
Stopping processing here.

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

Bug#926199: stretch-pu: package libreoffice/1:5.2.7-1+deb9u6

2019-04-01 Thread Rene Engelhard 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

now that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925
is finally fixed in stretch-p-u I think it's time to fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913641 in the sense
that we conflict against the "broken" OpenJDK (and build-conflict
against it. So we can remove the "build hack" needed to be introduced
in the +deb9u5 security update).

I also included a simple documentation fix I noticed when seeing
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926009

Diff is

diff -Nru libreoffice-5.2.7/debian/changelog libreoffice-5.2.7/debian/changelog
--- libreoffice-5.2.7/debian/changelog  2019-01-23 18:51:09.0 +0100
+++ libreoffice-5.2.7/debian/changelog  2019-01-23 18:51:09.0 +0100
@@ -1,3 +1,15 @@
+libreoffice (1:5.2.7-1+deb9u6) stretch; urgency=medium
+
+  * debian/patches/mention-java-common-package.diff: update message to
+reflect current config dir...
+  * debian/patches/disableClassPathURLCheck.diff: revert openjdk is fixed
+
+  * debian/control.in:
+- make -core conflict against openjdk-8-jre-headless (= 8u181-b13-2~deb9u1)
+  (closes: 913641#) and build-conflict against it
+
+ -- Rene Engelhard   Wed, 23 Jan 2019 18:51:09 +0100
+
 libreoffice (1:5.2.7-1+deb9u5) stretch-security; urgency=high

   * debian/patches/disableClassPathURLCheck.diff: add workaround to
diff -Nru libreoffice-5.2.7/debian/control libreoffice-5.2.7/debian/control
--- libreoffice-5.2.7/debian/control2019-01-23 18:51:09.0 +0100
+++ libreoffice-5.2.7/debian/control2019-01-23 18:51:09.0 +0100
@@ -183,6 +183,7 @@
  nvidia-glx-dev,
  nvidia-glx-legacy-dev,
  nvidia-libopencl1,
+ openjdk-8-jre-headless (= 8u181-b13-2~deb9u1),
  qt3-dev-tools
 Standards-Version: 3.9.4
 Vcs-Git: https://anonscm.debian.org/git/pkg-openoffice/libreoffice.git
@@ -430,7 +431,10 @@
 myspell-sw (<< 1:3.1.0-3),
 myspell-th (<< 1:3.1.0-3),
 myspell-tl (<< 0.4-0-5)
-Conflicts: cacao-oj6-jre, libreoffice-filter-binfilter, libreoffice-unbundled
+Conflicts: cacao-oj6-jre,
+   libreoffice-filter-binfilter,
+   libreoffice-unbundled,
+   openjdk-8-jre-headless (= 8u181-b13-2~deb9u1)
 Provides: libreoffice-bundled
 Replaces: libreoffice-calc (<< 1:3.3.2-5),
   libreoffice-common (<< 1:4.4.0~rc3-1),
diff -Nru libreoffice-5.2.7/debian/control.in 
libreoffice-5.2.7/debian/control.in
--- libreoffice-5.2.7/debian/control.in 2018-11-23 07:50:05.0 +0100
+++ libreoffice-5.2.7/debian/control.in 2019-01-23 18:51:09.0 +0100
@@ -20,6 +20,7 @@
  libc6-dev (= 2.6.1-4) [i386 amd64],
  libcairo2 (= 1.4.8-1),
  libxul-dev (= 1.8.0.13~pre070720-0etch1),
+ openjdk-8-jre-headless (= 8u181-b13-2~deb9u1),
  nvidia-glx-dev,
  nvidia-glx-legacy-dev,
  qt3-dev-tools,
@@ -269,7 +270,7 @@
 myspell-th (<< 1:3.1.0-3),
 myspell-tl (<< 0.4-0-5),
 browser-plugin-libreoffice
-Conflicts: cacao-oj6-jre, libreoffice-filter-binfilter, libreoffice-unbundled
+Conflicts: cacao-oj6-jre, libreoffice-filter-binfilter, libreoffice-unbundled, 
openjdk-8-jre-headless (= 8u181-b13-2~deb9u1)
 Provides: libreoffice-bundled
 Replaces: libreoffice-calc (<< 1:3.3.2-5),
   libreoffice-common (<< 1:4.4.0~rc3-1),
diff -Nru libreoffice-5.2.7/debian/patches/disableClassPathURLCheck.diff 
libreoffice-5.2.7/debian/patches/disableClassPathURLCheck.diff
--- libreoffice-5.2.7/debian/patches/disableClassPathURLCheck.diff  
2018-12-28 11:20:29.0 +0100
+++ libreoffice-5.2.7/debian/patches/disableClassPathURLCheck.diff  
1970-01-01 01:00:00.0 +0100
@@ -1,10 +0,0 @@
 a/configure.ac-old 2018-12-28 11:10:35.953066686 +0100
-+++ b/configure.ac 2018-12-28 11:11:06.049403639 +0100
-@@ -6976,6 +6976,7 @@
-
- # set to limit VM usage for JunitTests
- JAVAIFLAGS=-Xmx64M
-+JAVAIFLAGS="$JAVAIFLAGS 
-Djdk.net.URLClassPath.disableClassPathURLCheck=true"
- # set to limit VM usage for javac
- JAVAFLAGS=-J-Xmx128M
- fi
diff -Nru libreoffice-5.2.7/debian/patches/mention-java-common-package.diff 
libreoffice-5.2.7/debian/patches/mention-java-common-package.diff
--- libreoffice-5.2.7/debian/patches/mention-java-common-package.diff   
2017-09-17 15:36:00.0 +0200
+++ libreoffice-5.2.7/debian/patches/mention-java-common-package.diff   
2019-01-23 18:51:09.0 +0100
@@ -8,7 +8,7 @@
  fprintf(stderr,"javaldx: Could not find a Java Runtime Environment! 
\n");
 +fprintf(stderr,"Please ensure that a JVM and the package 
libreoffice-java-common\n");
 +fprintf(stderr,"is installed.\n");
-+fprintf(stderr,"If it is already installed then

Bug#926190: stretch-pu: package postfix/3.1.12-0+deb9u1

2019-04-01 Thread Scott Kitterman 
On Mon, 01 Apr 2019 14:30:04 -0400 Scott Kitterman  
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> This is the next in a series.  It contains upstream bug fix releases 3.1.10,
> 3.1.11, and 3.1.12.  I held off after 3.1.10 since it contains somewhat more
> new/changed code than these usually do.  Both 3.1.11 and 3.1.12 have since
> been released with no corrections needed to the refactored code.
> 
> I have been running 3.1.10/11 in production for some time and currently have
> 3.1.12 in production.  All with no issues.
> 
> I am particularly motivated to move forward with another stable update now
> because 3.1.12 fixes an LMTP performance issue that likely has been hurting
> any high volume receivers and is a regression for oldstable -> stable.  
There
> are also fixes for several smtputf8 fixes that are oldstable -> stable
> regressions.
> 
> Other than the openssl related refactoring that has been extensively tested
> by the postfix community, most of the changes are documentation.  The other
> code changes seem reasonably compact and low risk.

Forgot to mention in the original bug that there's also a pending unblock 
request for 3.4.5-1 (#926188) that will cover getting the LMTP performance fix 
into Buster.

Scott K

Bug#926177: marked as done (unblock: puppet-module-swift/13.1.0-4)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 01 Apr 2019 18:54:00 +
with message-id 
and subject line Re: Bug#926177: unblock: puppet-module-swift/13.1.0-4
has caused the Debian Bug report #926177,
regarding unblock: puppet-module-swift/13.1.0-4
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.)


-- 
926177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package puppet-module-swift,

When patching puppet-module-swift, to remove the "nobarrier" option
from fstab (not supported anymore in Buster), I did a syntax mistake
(missing closing single quote at the end of the string). This last
upload fixes it.

I've atteched the (one liner) debdiff.

Please unblock puppet-module-swift/13.1.0-4

Cheers,

Thomas Goirand (zigo)
diff -Nru puppet-module-swift-13.1.0/debian/changelog 
puppet-module-swift-13.1.0/debian/changelog
--- puppet-module-swift-13.1.0/debian/changelog 2019-01-24 14:00:43.0 
+0100
+++ puppet-module-swift-13.1.0/debian/changelog 2019-04-01 17:01:12.0 
+0200
@@ -1,3 +1,9 @@
+puppet-module-swift (13.1.0-4) unstable; urgency=medium
+
+  * Fix remove-nobarrier-option.patch braking Puppet's syntax.
+
+ -- Thomas Goirand   Mon, 01 Apr 2019 17:01:12 +0200
+
 puppet-module-swift (13.1.0-3) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru 
puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch
--- puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
2019-01-24 14:00:43.0 +0100
+++ puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
2019-04-01 17:01:12.0 +0200
@@ -14,7 +14,7 @@
 +$options = 'noatime,nodiratime,loop'
} else {
 -$options = 'noatime,nodiratime,nobarrier'
-+$options = 'noatime,nodiratime
++$options = 'noatime,nodiratime'
}
  
if($fstype == 'xfs'){
--- End Message ---
--- Begin Message ---
Thomas Goirand:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package puppet-module-swift,
> 
> When patching puppet-module-swift, to remove the "nobarrier" option
> from fstab (not supported anymore in Buster), I did a syntax mistake
> (missing closing single quote at the end of the string). This last
> upload fixes it.
> 
> I've atteched the (one liner) debdiff.
> 
> Please unblock puppet-module-swift/13.1.0-4
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926163: marked as done (unblock: ruby-rails-assets-perfect-scrollbar/1.4.0-2)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 01 Apr 2019 18:51:00 +
with message-id <5a84adff-518d-b031-2e04-05e008192...@thykier.net>
and subject line Re: Bug#926163: unblock: 
ruby-rails-assets-perfect-scrollbar/1.4.0-2
has caused the Debian Bug report #926163,
regarding unblock: ruby-rails-assets-perfect-scrollbar/1.4.0-2
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.)


-- 
926163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package ruby-rails-assets-perfect-scrollbar

Fixes rc bug #924174, fixes autopkgtest and removes unnecessary dependencies.

$ debdiff ruby-rails-assets-perfect-scrollbar_1.4.0-1.dsc 
ruby-rails-assets-perfect-scrollbar_1.4.0-2.dsc 
dpkg-source: warning: extracting unsigned source package 
(/home/pravi/forge/debian/git/ruby-team/ruby-rails-assets-perfect-scrollbar_1.4.0-1.dsc)
dpkg-source: warning: extracting unsigned source package 
(/home/pravi/forge/debian/git/ruby-team/ruby-rails-assets-perfect-scrollbar_1.4.0-2.dsc)
diff -Nru ruby-rails-assets-perfect-scrollbar-1.4.0/debian/changelog 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/changelog
--- ruby-rails-assets-perfect-scrollbar-1.4.0/debian/changelog  2019-01-14 
00:50:32.0 +0530
+++ ruby-rails-assets-perfect-scrollbar-1.4.0/debian/changelog  2019-04-01 
14:44:51.0 +0530
@@ -1,3 +1,12 @@
+ruby-rails-assets-perfect-scrollbar (1.4.0-2) unstable; urgency=medium
+
+  * Fix symbolic link to libjs-perfect-scrollbar (Closes: #924174)
+  * Don't load css in smoke test (fixes autopkgtest)
+  * Remove unnecessary dependencies
+  * Add comment to patch
+
+ -- Pirate Praveen   Mon, 01 Apr 2019 14:44:51 +0530
+
 ruby-rails-assets-perfect-scrollbar (1.4.0-1) unstable; urgency=medium
 
   * Team upload
diff -Nru ruby-rails-assets-perfect-scrollbar-1.4.0/debian/control 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/control
--- ruby-rails-assets-perfect-scrollbar-1.4.0/debian/control2019-01-14 
00:50:32.0 +0530
+++ ruby-rails-assets-perfect-scrollbar-1.4.0/debian/control2019-04-01 
14:44:51.0 +0530
@@ -20,9 +20,6 @@
  ruby | ruby-interpreter,
  ${misc:Depends},
  ${shlibs:Depends},
- rake,
- bundler,
- ruby-chromedriver-helper
 Description: Minimalistic but perfect custom scrollbar plugin
  perfect-scrollbar is minimalistic but a perfect scrollbar plugin.
  There is no change on design layout and no manipulation on DOM tree. It uses
diff -Nru ruby-rails-assets-perfect-scrollbar-1.4.0/debian/install 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/install
--- ruby-rails-assets-perfect-scrollbar-1.4.0/debian/install2019-01-14 
00:50:32.0 +0530
+++ ruby-rails-assets-perfect-scrollbar-1.4.0/debian/install1970-01-01 
05:30:00.0 +0530
@@ -1 +0,0 @@
-app usr/share/ruby-rails-assets-perfect-scrollbar
diff -Nru 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/libjs-perfect-scrollbar.install
 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/libjs-perfect-scrollbar.install
--- 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/libjs-perfect-scrollbar.install
2019-01-14 00:50:32.0 +0530
+++ 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/libjs-perfect-scrollbar.install
2019-04-01 14:44:51.0 +0530
@@ -1 +1 @@
-app/assets/javascripts/perfect-scrollbar/ usr/share/javascript/
+app/assets/javascripts/utatti-perfect-scrollbar/ usr/share/javascript/
diff -Nru 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/patches/set-rails-engine-root.patch
 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/patches/set-rails-engine-root.patch
--- 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/patches/set-rails-engine-root.patch
2019-01-14 00:50:32.0 +0530
+++ 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/patches/set-rails-engine-root.patch
2019-04-01 14:44:51.0 +0530
@@ -1,3 +1,5 @@
+Debian specific change to install assets in /usr/share
+
 --- a/lib/rails-assets-utatti-perfect-scrollbar.rb
 +++ b/lib/rails-assets-utatti-perfect-scrollbar.rb
 @@ -19,12 +19,13 @@ module RailsAssetsUtattiPerfectScrollbar
diff -Nru 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/ruby-rails-assets-perfect-scrollbar.install
 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/ruby-rails-assets-perfect-scrollbar.install
--- 
ruby-rails-assets-perfect-scrollbar-1.4.0/debian/ruby-rails-assets-perfect-scrollbar.install
1970-01-01 05

Bug#926162: unblock: opensaml/3.0.1-1

2019-04-01 Thread Niels Thykier 
Control: tags -1 moreinfo confirmed

Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package opensaml
> 
> Dear Release Team,
> 
> [...]
> 
> If you're fine with this, I'm ready to upload opensaml/3.0.1-1 to
> unstable.
> 
> Thanks,
> Feri.
> 
> [...]
> 
> unblock opensaml/3.0.1-1
> 


Please go ahead with the upload and remove the moreinfo tag when it is
ready for unblocking.

Thanks,
~Niels

Processed: Re: Bug#926162: unblock: opensaml/3.0.1-1

2019-04-01 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 moreinfo confirmed
Bug #926162 [release.debian.org] unblock: opensaml/3.0.1-1
Added tag(s) moreinfo and confirmed.

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

Processed: Re: Bug#926188: unblock: postfix/3.4.5-1

2019-04-01 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 moreinfo confirmed
Bug #926188 [release.debian.org] unblock: postfix/3.4.5-1
Added tag(s) confirmed and moreinfo.

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

Bug#926188: unblock: postfix/3.4.5-1

2019-04-01 Thread Niels Thykier 
Control: tags -1 moreinfo confirmed

Scott Kitterman:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package postfix
> 
> [...]
> Thanks,
> 
> Scott K
> 
> unblock postfix/3.4.5-1
> 

Please go ahead with the upload and remove the moreinfo tag when it is
ready for unblocking.

Thanks,
~Niels

Bug#926153: marked as done (unblock: mitmproxy/4.0.4-5)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 01 Apr 2019 18:34:00 +
with message-id 
and subject line Re: Bug#926153: unblock: mitmproxy/4.0.4-5
has caused the Debian Bug report #926153,
regarding unblock: mitmproxy/4.0.4-5
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.)


-- 
926153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear Release Team,

#923354 describes how mitmproxy 4.0.4-4 doesn't start at all due to a
missing dependency, and as such it should probably have used
"Severity:grave".

4.0.4-5 fixes that, and has been in unstable for a little while
now. I've attached the relevant debdiff between those two versions.

Could you please consider unblocking 4.0.4-5 ?

Cheers,

-- 
Seb

unblock mitmproxy/4.0.4-5

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/36 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 2227fb62..e2d46fbc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+mitmproxy (4.0.4-5) unstable; urgency=medium
+
+  * Add dependency on python3-pkg-resources (Closes: #923354)
+
+ -- Sebastien Delafond   Mon, 04 Mar 2019 10:49:20 +0100
+
 mitmproxy (4.0.4-4) unstable; urgency=medium
 
   * Remove references to manpage in debian/rules
diff --git a/debian/control b/debian/control
index 677d471d..f963a716 100644
--- a/debian/control
+++ b/debian/control
@@ -36,7 +36,7 @@ Homepage: https://mitmproxy.org
 Package: mitmproxy
 Architecture: all
 Pre-Depends: dpkg (>= 1.17.14)
-Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>= 
4.2.0~dfsg), python3-h11
+Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>= 
4.2.0~dfsg), python3-h11, python3-pkg-resources
 Conflicts: python-netlib
 Description: SSL-capable man-in-the-middle HTTP proxy
  mitmproxy is an SSL-capable man-in-the-middle HTTP proxy. It provides
--- End Message ---
--- Begin Message ---
Sebastien Delafond:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> 
> #923354 describes how mitmproxy 4.0.4-4 doesn't start at all due to a
> missing dependency, and as such it should probably have used
> "Severity:grave".
> 
> 4.0.4-5 fixes that, and has been in unstable for a little while
> now. I've attached the relevant debdiff between those two versions.
> 
> Could you please consider unblocking 4.0.4-5 ?
> 
> Cheers,
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926170: marked as done (unblock: libclamunrar/0.101.2-1)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 01 Apr 2019 18:33:00 +
with message-id 
and subject line Re: Bug#926170: unblock: libclamunrar/0.101.2-1
has caused the Debian Bug report #926170,
regarding unblock: libclamunrar/0.101.2-1
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.)


-- 
926170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package libclamunrar.
The new release is part of the new clamav release which fixes two RAR
related CVEs.

unblock libclamunrar/0.101.2-1

Sebastian
diff -Nru libclamunrar-0.101.1/clamav-config.h.in 
libclamunrar-0.101.2/clamav-config.h.in
--- libclamunrar-0.101.1/clamav-config.h.in 2019-02-09 23:29:30.0 
+0100
+++ libclamunrar-0.101.2/clamav-config.h.in 2019-03-30 14:57:29.0 
+0100
@@ -314,6 +314,9 @@
 /* Define to 1 if you have the `strnlen' function. */
 #undef HAVE_STRNLEN
 
+/* Define to 1 if you have the `strnstr' function. */
+#undef HAVE_STRNSTR
+
 /* Define to 1 if sysconf(_SC_PAGESIZE) is available */
 #undef HAVE_SYSCONF_SC_PAGESIZE
 
diff -Nru libclamunrar-0.101.1/configure libclamunrar-0.101.2/configure
--- libclamunrar-0.101.1/configure  2019-02-09 23:29:30.0 +0100
+++ libclamunrar-0.101.2/configure  2019-03-30 14:57:29.0 +0100
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for ClamAV 0.101.1.
+# Generated by GNU Autoconf 2.69 for ClamAV 0.101.2.
 #
 # Report bugs to .
 #
@@ -590,8 +590,8 @@
 # Identity of this package.
 PACKAGE_NAME='ClamAV'
 PACKAGE_TARNAME='clamav'
-PACKAGE_VERSION='0.101.1'
-PACKAGE_STRING='ClamAV 0.101.1'
+PACKAGE_VERSION='0.101.2'
+PACKAGE_STRING='ClamAV 0.101.2'
 PACKAGE_BUGREPORT='https://bugzilla.clamav.net/'
 PACKAGE_URL='https://www.clamav.net/'
 
@@ -753,6 +753,8 @@
 CHECK_CPPFLAGS
 CHECK_LIBS
 CHECK_CFLAGS
+ENABLE_FUZZ_FALSE
+ENABLE_FUZZ_TRUE
 BUILD_CONFIGURE_FLAGS
 VERSIONSCRIPT_FALSE
 VERSIONSCRIPT_TRUE
@@ -908,6 +910,7 @@
 enable_libtool_lock
 enable_gcc_vcheck
 enable_experimental
+enable_fuzz
 enable_mempool
 enable_check
 enable_rpath
@@ -1533,7 +1536,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures ClamAV 0.101.1 to adapt to many kinds of systems.
+\`configure' configures ClamAV 0.101.2 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1605,7 +1608,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of ClamAV 0.101.1:";;
+ short | recursive ) echo "Configuration of ClamAV 0.101.2:";;
esac
   cat <<\_ACEOF
 
@@ -1626,6 +1629,7 @@
   --disable-libtool-lock  avoid locking (might break parallel builds)
   --disable-gcc-vcheckdo not check for buggy gcc version
   --enable-experimental   enable experimental code
+  --enable-fuzz   enable building standalone fuzz targets [default=no]
   --disable-mempool   do not use memory pools
   --enable-check  enable check unit tests [default=auto]
   --disable-rpath do not hardcode runtime library paths
@@ -1819,7 +1823,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-ClamAV configure 0.101.1
+ClamAV configure 0.101.2
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -2363,7 +2367,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by ClamAV $as_me 0.101.1, which was
+It was created by ClamAV $as_me 0.101.2, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -4120,7 +4124,7 @@
 
 # Define the identity of the package.
  PACKAGE='clamav'
- VERSION='0.101.1'
+ VERSION='0.101.2'
 
 
 # Some tools Automake needs.
@@ -5849,10 +5853,10 @@
 
 
 
-VERSION="0.101.1"
+VERSION="0.101.2"
 
 LC_CURRENT=9
-LC_REVISION=1
+LC_REVISION=2
 LC_AGE=0
 LIBCLAMAV_VERSION="$LC_CURRENT":"$LC_REVISION":"$LC_AGE"
 
@@ -19150,6 +19154,27 @@
 BUILD_CONFIGURE_FLAGS=$build_configure_args
 
 
+# Check whether --enable-fuzz was given.
+if test "${enable_fuzz+set}" = set; then :
+  enableval=$enable_fuzz; enable_cov=$enableval
+else
+  enable_cov="no"
+fi
+
+
+if test "x$enable_fuzz" = "xyes"; then
+CXX

Bug#926190: stretch-pu: package postfix/3.1.12-0+deb9u1

2019-04-01 Thread Scott Kitterman 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

This is the next in a series.  It contains upstream bug fix releases 3.1.10,
3.1.11, and 3.1.12.  I held off after 3.1.10 since it contains somewhat more
new/changed code than these usually do.  Both 3.1.11 and 3.1.12 have since
been released with no corrections needed to the refactored code.

I have been running 3.1.10/11 in production for some time and currently have
3.1.12 in production.  All with no issues.

I am particularly motivated to move forward with another stable update now
because 3.1.12 fixes an LMTP performance issue that likely has been hurting
any high volume receivers and is a regression for oldstable -> stable.  There
are also fixes for several smtputf8 fixes that are oldstable -> stable
regressions.

Other than the openssl related refactoring that has been extensively tested
by the postfix community, most of the changes are documentation.  The other
code changes seem reasonably compact and low risk.

Usual fix list:

  [ Scott Kitterman ]

  * Add detailed smarthost instructions to README.Debian.  Thanks to Celejar
for the input.  Closes: #919444
  * Refresh patches

  [Wietse Venema]

  * 3.1.10
- Bugfix (introduced: Postfix 2.11): minor memory leak when
  minting issuer certs. This affects a tiny minority of use
  cases. Viktor Dukhovni, based on a fix by Juan Altmayer
  Pizzorno for the ssl_dane library. File: tls/tls_dane.c.
- Bugfix (introduced: Postfix 3.0): with smtputf8_enable=yes,
  table lookups could casefold the search string when searching
  a lookup table that does not use fixed-string keys (regexp,
  pcre, tcp, etc.). Historically, Postfix would not case-fold
  the search string with such tables. File: util/dict_utf8.c.
  Closes: #917512
- Multiple 'bit rot' fixes for OpenSSL API changes, including
  support to disable TLSv1.3, to avoid issuing multiple session
  tickets. Viktor Dukhovni. Files: proto/postconf.proto,
  proto/TLS_README.html, tls/tls.h, tls/tls_server.c,
  tls/tls_misc.c.
- Bugfix (introduced: 3.0): smtpd_discard_ehlo_keywords could
  not disable "SMTPUTF8". because the lookup table was using
  "EHLO_MASK_SMTPUTF8" instead. File: global/ehlo_mask.c.
- Documentation: update documentation for Postfix versions
  that support disabling TLS 1.3. File: proto/postconf.proto.
- Improved logging of TLS 1.3 summary information, and improved
  reporting of the same info in Received: message headers.
  Viktor Dukhovni. Files: proto/FORWARD_SECRECY_README.html,
  posttls-finger/posttls-finger.c, smtpd/smtpd.c, tls/tls.h,
  tls/tls_client.c, tls/tls_misc.c, tls/tls_proxy.h,
  tls/tls_proxy_context_print.c, tls/tls_proxy_context_scan.c,
  tls/tls_server.c.
  * 3.1.11
- Bugfix (introduced: postfix-2.11): with posttls-finger,
  connections to unix-domain servers always resulted in "Failed
  to establish session" even after a connection was established.
  Jaroslav Skarva.  File: posttls-finger/posttls-finger.c.
  * 3.1.12
- Bugfix (introduced: Postfix 2.2): reject_multi_recipient_bounce
  has been producing false rejects starting with the Postfix
  2.2 smtpd_end_of_data_restrictons, and for the same reasons,
  did the same with the Postfix 3.4 BDAT command. The latter
  was reported by Andreas Schulze. File: smtpd/smtpd_check.c.
- Bugfix (introduced: Postfix 3.0): LMTP connections over
  UNIX-domain sockets were cached but not reused, due to a
  cache lookup key mismatch. Therefore, idle cached connections
  could exhaust LMTP server resources, resulting in two-second
  pauses between email deliveries. This problem was investigated
  by Juliana Rodrigueiro. File: smtp/smtp_connect.c.

Thanks for considering,

Scott K
diff -Nru postfix-3.1.9/debian/changelog postfix-3.1.12/debian/changelog
--- postfix-3.1.9/debian/changelog	2019-02-08 09:07:54.0 -0500
+++ postfix-3.1.12/debian/changelog	2019-04-01 13:01:06.0 -0400
@@ -1,3 +1,61 @@
+postfix (3.1.12-0+deb9u1) stretch; urgency=medium
+
+  [Scott Kitterman]
+
+  * Add detailed smarthost instructions to README.Debian.  Thanks to Celejar
+for the input.  Closes: #919444
+  * Refresh patches
+
+  [Wietse Venema]
+
+  * 3.1.10
+- Bugfix (introduced: Postfix 2.11): minor memory leak when
+  minting issuer certs. This affects a tiny minority of use
+  cases. Viktor Dukhovni, based on a fix by Juan Altmayer
+  Pizzorno for the ssl_dane library. File: tls/tls_dane.c.
+- Bugfix (introduced: Postfix 3.0): with smtputf8_enable=yes,
+  table lookups could casefold the search string when searching
+  a lookup table that does not use fixed-string keys (regexp,
+  pcre, tcp, etc.). Historically, Postfix would not case-fold
+  the search string with such tables. File: util/dict_utf8.c.
+  Closes: #917

Bug#926123: unblock: cabextract/1.9-2

2019-04-01 Thread Eric Sharkey 
On Sun, Mar 31, 2019 at 3:58 PM Jens Reyer  wrote:

> Passing on Jonathan's question to you.
>
> [..]
> The debhelper compat change is a problem. Would you or the maintainer be
> interested in an upload reverting it?
>

 I'd rather release buster with cabextract 1.9-1.  There's no bug in it.
If you want to unblock libmspack and get that into buster, that's fine, and
1.9-1 is compatible with that.  There's no need to do anything to
cabextract in buster due to the mspack bug.

Eric Sharkey

Bug#926188: unblock: postfix/3.4.5-1

2019-04-01 Thread Scott Kitterman 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package postfix

As mentioned in the last unblock request, for postfix we've been doing stable
updates of new 3.1 series versions and I'm trying to follow a similar
approach during freeze, particularly due to the late switch to postfix 3.4.

Of course, as soon as I think it's quieted down and it's safe to update, there
is another one.  I would like to go ahead with this now and not wait because
there is a companion 3.1 update for stable that I would like to proceed with
sooner rather than later and I don't want stable to get ahead of testing in
terms of fixes/functionality.

There are two fixes in this release:

  * 3.4.5
- With message_size_limit=0 (which is NOT DOCUMENTED), BDAT
  chunks were always rejected as too large. File: smtpd/smtpd.c
- Bugfix (introduced: Postfix 3.0): LMTP connections over
  UNIX-domain sockets were cached but not reused, due to a
  cache lookup key mismatch. Therefore, idle cached connections
  could exhaust LMTP server resources, resulting in two-second
  pauses between email deliveries. This problem was investigated
  by Juliana Rodrigueiro. File: smtp/smtp_connect.c.

The latter fix is a regression from oldstable -> stable.  For high volume
LMTP users, the impact is likley significant, but difficult to diagnose.  I
definitely want this fixed in stable and I think we want it fixed in buster
too.

The first fix represents the next in a series of existing code limitations
that present problems not that BDAT is implemented.

As you can see, the diff is pretty trivial.  I have the package ready to
upload when ack'ed.

Thanks,

Scott K

unblock postfix/3.4.5-1
diff -Nru postfix-3.4.4/debian/changelog postfix-3.4.5/debian/changelog
--- postfix-3.4.4/debian/changelog	2019-03-25 11:03:58.0 -0400
+++ postfix-3.4.5/debian/changelog	2019-04-01 13:30:19.0 -0400
@@ -1,3 +1,19 @@
+postfix (3.4.5-1) UNRELEASED; urgency=medium
+
+  [Wietse Venema]
+
+  * 3.4.5
+- With message_size_limit=0 (which is NOT DOCUMENTED), BDAT
+  chunks were always rejected as too large. File: smtpd/smtpd.c
+- Bugfix (introduced: Postfix 3.0): LMTP connections over
+  UNIX-domain sockets were cached but not reused, due to a
+  cache lookup key mismatch. Therefore, idle cached connections
+  could exhaust LMTP server resources, resulting in two-second
+  pauses between email deliveries. This problem was investigated
+  by Juliana Rodrigueiro. File: smtp/smtp_connect.c.
+
+ -- Scott Kitterman   Mon, 01 Apr 2019 13:27:26 -0400
+
 postfix (3.4.4-1) unstable; urgency=medium
 
   [Wietse Venema]
diff -Nru postfix-3.4.4/HISTORY postfix-3.4.5/HISTORY
--- postfix-3.4.4/HISTORY	2019-03-14 19:57:12.0 -0400
+++ postfix-3.4.5/HISTORY	2019-03-30 10:33:58.0 -0400
@@ -24195,3 +24195,16 @@
 	does the same with the Postfix 3.4 BDAT command. The latter
 	was reported by Andreas Schulze. File: smtpd/smtpd_check.c.
 
+20190319
+
+	With message_size_limit=0 (which is NOT DOCUMENTED), BDAT
+	chunks were always rejected as too large. File: smtpd/smtpd.c
+
+20190328
+
+	Bugfix (introduced: Postfix 3.0): LMTP connections over
+	UNIX-domain sockets were cached but not reused, due to a
+	cache lookup key mismatch. Therefore, idle cached connections
+	could exhaust LMTP server resources, resulting in two-second
+	pauses between email deliveries. This problem was investigated
+	by Juliana Rodrigueiro. File: smtp/smtp_connect.c.
diff -Nru postfix-3.4.4/html/postconf.5.html postfix-3.4.5/html/postconf.5.html
--- postfix-3.4.4/html/postconf.5.html	2019-02-10 12:12:57.0 -0500
+++ postfix-3.4.5/html/postconf.5.html	2019-03-24 18:59:02.0 -0400
@@ -6241,7 +6241,7 @@
 (default: empty)
 
  The name of an optional logfile that is written by the Postfix
-postlogd(8) service. A non-empty value selects logging to syslogd(8).
+postlogd(8) service. An empty value selects logging to syslogd(8).
 Specify "/dev/stdout" to select logging to standard output. Stdout
 logging requires that Postfix is started with "postfix start-fg".
 
diff -Nru postfix-3.4.4/man/man5/postconf.5 postfix-3.4.5/man/man5/postconf.5
--- postfix-3.4.4/man/man5/postconf.5	2019-02-03 11:58:44.0 -0500
+++ postfix-3.4.5/man/man5/postconf.5	2019-03-24 18:59:03.0 -0400
@@ -3750,7 +3750,7 @@
 This feature is available in Postfix 2.3 and later.
 .SH maillog_file (default: empty)
 The name of an optional logfile that is written by the Postfix
-\fBpostlogd\fR(8) service. A non\-empty value selects logging to \fBsyslogd\fR(8).
+\fBpostlogd\fR(8) service. An empty value selects logging to \fBsyslogd\fR(8).
 Specify "/dev/stdout" to select logging to standard output. Stdout
 logging requires that Postfix is started with "postfix start\-fg".
 .PP
diff -Nru postfix-3.4.4/proto/postconf.proto postfix-3.4.5/proto/postconf.proto
--- postfix-3.4.4/proto/postco

Bug#924523: unblock: plinth/19.2

2019-04-01 Thread Sunil Mohan Adapa 
On Wed, 13 Mar 2019 15:07:27 -0700 Sunil Mohan Adapa 
wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Please unblock package plinth
> (binary packages: plinth, freedombox)
> 
> Due to incorrect release planning, we missed the full freeze deadline by a few
> hours. We assumed packages may transition on 12th March and did our release 
> few
> hours after 2019-03-02 00:00 UTC (package was accepted at 20:47:49 UTC). We
> request you to make an exception and transition FreedomBox release 19.2.
> 

Please let us know if any further information will help with this request.

Thank you,

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Re: buster and the release notes

2019-04-01 Thread Justin B Rye 
Niels Thykier wrote:
>> How about upgrading.dbk and whatsnew.dbk?
> 
> Hi,
> 
> The "upgrading.dbk" historically had release-specific content "hidden"
> deeply within selected sections.  In stretch we took an effort to
> extract that to "issues.dbk" so the "routined" administrator would only
> have to read "issues.dbk" for potential problems.
> 
> IOW: upgrading.dbk should be in a state where we can close it (assuming
> we got all the release specific issues moved to issues - I do not
> remember and I did not have time to check).

If the content's settled, now would be a good time to review the
English.  Issues in issues.dbk:

diff --git a/en/issues.dbk b/en/issues.dbk
index 8ddb32d3..69054251 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -76,7 +76,7 @@ information mentioned in .

In "deprecated-components":

 
   
 The package mcelog is no
-longer supported in kernels above 4.12. rasdaemon can be used as its
 replacement.
   
@@ -126,7 +126,7 @@ information mentioned in .

Still in "deprecated-components":

   
   
 
-  Icinga 1.x is EOL upstream since 2018-12-31, while the
+  Icinga 1.x is EOL upstream since 2018-12-31; while the

I would have said something like "has reached EOL", but Google tells
me plenty of people say "is EOL", so I'll just fix the comma-splice.

   icinga package
-  is still present, users should use the buster lifetime
+  is still available, users should use the buster lifetime

On second thoughts this isn't really necessary, so I'll take it out of
the attached version of the patch.

   to migrate to Icinga 2
   (icinga2 package)
   and Icinga Web 2

@@ -200,7 +200,7 @@ information mentioned in .

Under "obsolete-sysvinit-packages":

 SysV init related packages no longer required
 
   
-This section does not apply if you decided to stick with sysvinit-core.
+This section does not apply if you have decided to stick with 
sysvinit-core.
   

A nice demonstration of a subtle aspectual difference.  "I decided" is
just a finished event; "I have decided" means the effects are still
relevant - i.e. I haven't changed my mind again since.

 
 
@@ -238,7 +238,7 @@ information mentioned in .

Under "browser-security":

   releases. Therefore, browsers built upon e.g. the webkit and khtml
   enginesThese engines are shipped in a number of different
   source packages and the concern applies to all packages shipping
-  them. The concern also extends to web rendering engines not explicitely
+  them. The concern also extends to web rendering engines not explicitly

Spelling.  (Also: if we're going to expect users to know that, e.g.,
Konqueror is built on khtml, it would be nice if browsers could be
relied on to mention this sort of thing in their package descriptions.
But that's not a release-notes bug.)

   mentioned here. are included in &releasename;, but not
   covered by security support. These browsers should not be used against
   untrusted websites.
@@ -309,11 +309,11 @@ information mentioned in .

Under "su-environment-variables":

 
 Semantics for using environment variables for su changed
 
-  su changed semantics in &releasename; and no longer 
copies

This needs another tense/aspect tweak (because for a start buster
isn't in the past yet).

-  over DISPLAY and XAUTHORITY

"Copies over X" is unclear - does it copy something over them, or does
it copy them over to somewhere?  Besides, the idea of "copying" is a
bit of an implementation detail; the most that's apparent to the user
is that the variables are no longer set in root's environment.

-  environment variables. You need to explicitly set them and allow
-  explicitly access to your display if you need to run graphical

"Allow explicitly access" is scrambled word order.  But it doesn't
really need to repeat "explicitly" (explicitly).

-  applications with su. See su has changed semantics in &releasename; and no 
longer
+  preserves the user environment variables DISPLAY and
+  XAUTHORITY. If you need to run graphical applications
+  with su, you will have to explicitly set them to allow
+  access to your display. See bug #905409 for an extensive discussion.
 
   

(Didn't I hear something about problems for users who are running "su"
when they ought to be using "su -"?  Oh, yes, I heard about it from
the NEWS.Debian file, so never mind.)
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/issues.dbk b/en/issues.dbk
index 8ddb32d3..69054251 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -76,7 +76,7 @@ information mentioned in .
 
   
 The package mcelog is no
-longer supported in kernels above 4.12. rasdaemon can be used as

Freezing udebs until buster is released: upcoming

2019-04-01 Thread Cyril Brulebois 
Hi,

With the final freeze step being reached, it makes sense to establish a
general block-udeb until buster is out. I'll review packages currently
not migrated to testing (mainly looking at [1]), then implement this
udeb freeze (which is basically the same as usual, except it's going to
last longer than the approximate week around Alpha or RC releases for
D-I).

 1. https://d-i.debian.org/testing-summary.html


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#926177: unblock: puppet-module-swift/13.1.0-4

2019-04-01 Thread Thomas Goirand 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package puppet-module-swift,

When patching puppet-module-swift, to remove the "nobarrier" option
from fstab (not supported anymore in Buster), I did a syntax mistake
(missing closing single quote at the end of the string). This last
upload fixes it.

I've atteched the (one liner) debdiff.

Please unblock puppet-module-swift/13.1.0-4

Cheers,

Thomas Goirand (zigo)
diff -Nru puppet-module-swift-13.1.0/debian/changelog 
puppet-module-swift-13.1.0/debian/changelog
--- puppet-module-swift-13.1.0/debian/changelog 2019-01-24 14:00:43.0 
+0100
+++ puppet-module-swift-13.1.0/debian/changelog 2019-04-01 17:01:12.0 
+0200
@@ -1,3 +1,9 @@
+puppet-module-swift (13.1.0-4) unstable; urgency=medium
+
+  * Fix remove-nobarrier-option.patch braking Puppet's syntax.
+
+ -- Thomas Goirand   Mon, 01 Apr 2019 17:01:12 +0200
+
 puppet-module-swift (13.1.0-3) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru 
puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch
--- puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
2019-01-24 14:00:43.0 +0100
+++ puppet-module-swift-13.1.0/debian/patches/remove-nobarrier-option.patch 
2019-04-01 17:01:12.0 +0200
@@ -14,7 +14,7 @@
 +$options = 'noatime,nodiratime,loop'
} else {
 -$options = 'noatime,nodiratime,nobarrier'
-+$options = 'noatime,nodiratime
++$options = 'noatime,nodiratime'
}
  
if($fstype == 'xfs'){

Bug#926170: unblock: libclamunrar/0.101.2-1

2019-04-01 Thread Sebastian Andrzej Siewior 
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package libclamunrar.
The new release is part of the new clamav release which fixes two RAR
related CVEs.

unblock libclamunrar/0.101.2-1

Sebastian
diff -Nru libclamunrar-0.101.1/clamav-config.h.in 
libclamunrar-0.101.2/clamav-config.h.in
--- libclamunrar-0.101.1/clamav-config.h.in 2019-02-09 23:29:30.0 
+0100
+++ libclamunrar-0.101.2/clamav-config.h.in 2019-03-30 14:57:29.0 
+0100
@@ -314,6 +314,9 @@
 /* Define to 1 if you have the `strnlen' function. */
 #undef HAVE_STRNLEN
 
+/* Define to 1 if you have the `strnstr' function. */
+#undef HAVE_STRNSTR
+
 /* Define to 1 if sysconf(_SC_PAGESIZE) is available */
 #undef HAVE_SYSCONF_SC_PAGESIZE
 
diff -Nru libclamunrar-0.101.1/configure libclamunrar-0.101.2/configure
--- libclamunrar-0.101.1/configure  2019-02-09 23:29:30.0 +0100
+++ libclamunrar-0.101.2/configure  2019-03-30 14:57:29.0 +0100
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for ClamAV 0.101.1.
+# Generated by GNU Autoconf 2.69 for ClamAV 0.101.2.
 #
 # Report bugs to .
 #
@@ -590,8 +590,8 @@
 # Identity of this package.
 PACKAGE_NAME='ClamAV'
 PACKAGE_TARNAME='clamav'
-PACKAGE_VERSION='0.101.1'
-PACKAGE_STRING='ClamAV 0.101.1'
+PACKAGE_VERSION='0.101.2'
+PACKAGE_STRING='ClamAV 0.101.2'
 PACKAGE_BUGREPORT='https://bugzilla.clamav.net/'
 PACKAGE_URL='https://www.clamav.net/'
 
@@ -753,6 +753,8 @@
 CHECK_CPPFLAGS
 CHECK_LIBS
 CHECK_CFLAGS
+ENABLE_FUZZ_FALSE
+ENABLE_FUZZ_TRUE
 BUILD_CONFIGURE_FLAGS
 VERSIONSCRIPT_FALSE
 VERSIONSCRIPT_TRUE
@@ -908,6 +910,7 @@
 enable_libtool_lock
 enable_gcc_vcheck
 enable_experimental
+enable_fuzz
 enable_mempool
 enable_check
 enable_rpath
@@ -1533,7 +1536,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures ClamAV 0.101.1 to adapt to many kinds of systems.
+\`configure' configures ClamAV 0.101.2 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1605,7 +1608,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of ClamAV 0.101.1:";;
+ short | recursive ) echo "Configuration of ClamAV 0.101.2:";;
esac
   cat <<\_ACEOF
 
@@ -1626,6 +1629,7 @@
   --disable-libtool-lock  avoid locking (might break parallel builds)
   --disable-gcc-vcheckdo not check for buggy gcc version
   --enable-experimental   enable experimental code
+  --enable-fuzz   enable building standalone fuzz targets [default=no]
   --disable-mempool   do not use memory pools
   --enable-check  enable check unit tests [default=auto]
   --disable-rpath do not hardcode runtime library paths
@@ -1819,7 +1823,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-ClamAV configure 0.101.1
+ClamAV configure 0.101.2
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -2363,7 +2367,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by ClamAV $as_me 0.101.1, which was
+It was created by ClamAV $as_me 0.101.2, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -4120,7 +4124,7 @@
 
 # Define the identity of the package.
  PACKAGE='clamav'
- VERSION='0.101.1'
+ VERSION='0.101.2'
 
 
 # Some tools Automake needs.
@@ -5849,10 +5853,10 @@
 
 
 
-VERSION="0.101.1"
+VERSION="0.101.2"
 
 LC_CURRENT=9
-LC_REVISION=1
+LC_REVISION=2
 LC_AGE=0
 LIBCLAMAV_VERSION="$LC_CURRENT":"$LC_REVISION":"$LC_AGE"
 
@@ -19150,6 +19154,27 @@
 BUILD_CONFIGURE_FLAGS=$build_configure_args
 
 
+# Check whether --enable-fuzz was given.
+if test "${enable_fuzz+set}" = set; then :
+  enableval=$enable_fuzz; enable_cov=$enableval
+else
+  enable_cov="no"
+fi
+
+
+if test "x$enable_fuzz" = "xyes"; then
+CXXFLAGS="-std=c++11 -stdlib=libc++ $CXXFLAGS"
+fi
+
+ if test "x$enable_fuzz" = "xyes"; then
+  ENABLE_FUZZ_TRUE=
+  ENABLE_FUZZ_FALSE='#'
+else
+  ENABLE_FUZZ_TRUE='#'
+  ENABLE_FUZZ_FALSE=
+fi
+
+
 
   { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether uname(2) is POSIX" 
>&5
 $as_echo_n "checking whether uname(2) is POSIX... " >&6; }
@@ -19357,6 +19382,17 @@
 fi
 done
 
+for ac_func in strnstr
+do :
+  ac_fn_c_check_func "$LINENO" "strnstr" "ac_cv_func_strnstr"
+if test "x$ac_cv_func_strnstr" = xyes; then :
+  cat >>confdefs.h <<_ACEOF
+#define HAVE_STRNSTR 1
+_ACEOF
+
+fi
+done
+
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for _LARGEFILE_SOURCE value 
needed for large files" >&5
 $as_echo_n "checking for _LARGEFILE_SOURCE value needed for large files... " 
>&6; }
 if ${ac_cv_sys_l

Bug#926162: unblock: opensaml/3.0.1-1

2019-04-01 Thread Ferenc Wágner 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package opensaml

Dear Release Team,

To fix their latest security bug, Shibboleth upstream made a coordinated
patch release of the full stack, as usual.  You already unblocked the
critical part of this (xmltooling and shibboleth-sp) and they even
reached testing, so we're good.  OpenSAML, the middle component also
gained a small patch, and I'm asking you about that now.  It isn't
critical at all, just a tuning down of a handful or error messages to
warn level.  As upstream put it: "The goal of those changes was to reach
a state in which any ERROR in the log requires a necessary operational
response." I think eliminating this deviation would improve the
administration experience and the upstream support opportunities for the
users of buster, thus I ask you to consider accepting it.

The debdiff below does not convey properly how small this change really
is, because the current 3.0.0-2 package carries a forward ported
upstream patch CPPOST-110-Rebenchmark-tests-with-SHA256-disgest.patch,
which was released with 3.0.1 and thus removed from the Debian patch
queue.  So the biggest part of this diff does not appear if you compare
the patched trees.

The result of dh_auto_test was ignored in 3.0.0-1 waiting for the above
patch, and that should have already been reverted in 3.0.0-2, because
all tests succeed again with the patch (I checked the buildd logs
manually now).  So they're safe to reenable and have no effect on the
binary packages.

Finally, the path change in HTTPMetadataProvider.xml fixes a unit test
which requires network access and is skipped during the package build
anyway.  (But also succeeds after the necessary URL configuration now.)

If you're fine with this, I'm ready to upload opensaml/3.0.1-1 to
unstable.

Thanks,
Feri.

diff -Nru opensaml-3.0.0/configure opensaml-3.0.1/configure
--- opensaml-3.0.0/configure2018-07-10 03:09:31.0 +0200
+++ opensaml-3.0.1/configure2019-03-08 16:01:45.0 +0100
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for opensaml 3.0.0.
+# Generated by GNU Autoconf 2.69 for opensaml 3.0.1.
 #
 # Report bugs to .
 #
@@ -590,8 +590,8 @@
 # Identity of this package.
 PACKAGE_NAME='opensaml'
 PACKAGE_TARNAME='opensaml'
-PACKAGE_VERSION='3.0.0'
-PACKAGE_STRING='opensaml 3.0.0'
+PACKAGE_VERSION='3.0.1'
+PACKAGE_STRING='opensaml 3.0.1'
 PACKAGE_BUGREPORT='https://issues.shibboleth.net/'
 PACKAGE_URL=''
 
@@ -1430,7 +1430,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures opensaml 3.0.0 to adapt to many kinds of systems.
+\`configure' configures opensaml 3.0.1 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1500,7 +1500,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of opensaml 3.0.0:";;
+ short | recursive ) echo "Configuration of opensaml 3.0.1:";;
esac
   cat <<\_ACEOF
 
@@ -1658,7 +1658,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-opensaml configure 3.0.0
+opensaml configure 3.0.1
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -2202,7 +2202,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by opensaml $as_me 3.0.0, which was
+It was created by opensaml $as_me 3.0.1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -3067,7 +3067,7 @@
 
 # Define the identity of the package.
  PACKAGE='opensaml'
- VERSION='3.0.0'
+ VERSION='3.0.1'
 
 
 cat >>confdefs.h <<_ACEOF
@@ -21436,7 +21436,7 @@
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by opensaml $as_me 3.0.0, which was
+This file was extended by opensaml $as_me 3.0.1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   CONFIG_FILES= $CONFIG_FILES
@@ -21502,7 +21502,7 @@
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; 
s/[\\""\`\$]/&/g'`"
 ac_cs_version="\\
-opensaml config.status 3.0.0
+opensaml config.status 3.0.1
 configured by $0, generated by GNU Autoconf 2.69,
   with options \\"\$ac_cs_config\\"
 
diff -Nru opensaml-3.0.0/configure.ac opensaml-3.0.1/configure.ac
--- opensaml-3.0.0/configure.ac 2018-07-10 03:09:09.0 +0200
+++ opensaml-3.0.1/configure.ac 2019-02-21 21:05:56.0 +0100
@@ -1,5 +1,5 @@
 AC_PREREQ([2.50])
-AC_INIT([opensaml],[3.0.0],[https://issues.shibboleth.net/],[opensaml])
+AC_INIT([opensaml],[3

Bug#926153: unblock: mitmproxy/4.0.4-5

2019-04-01 Thread Sebastien Delafond 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear Release Team,

#923354 describes how mitmproxy 4.0.4-4 doesn't start at all due to a
missing dependency, and as such it should probably have used
"Severity:grave".

4.0.4-5 fixes that, and has been in unstable for a little while
now. I've attached the relevant debdiff between those two versions.

Could you please consider unblocking 4.0.4-5 ?

Cheers,

-- 
Seb

unblock mitmproxy/4.0.4-5

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/36 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 2227fb62..e2d46fbc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+mitmproxy (4.0.4-5) unstable; urgency=medium
+
+  * Add dependency on python3-pkg-resources (Closes: #923354)
+
+ -- Sebastien Delafond   Mon, 04 Mar 2019 10:49:20 +0100
+
 mitmproxy (4.0.4-4) unstable; urgency=medium
 
   * Remove references to manpage in debian/rules
diff --git a/debian/control b/debian/control
index 677d471d..f963a716 100644
--- a/debian/control
+++ b/debian/control
@@ -36,7 +36,7 @@ Homepage: https://mitmproxy.org
 Package: mitmproxy
 Architecture: all
 Pre-Depends: dpkg (>= 1.17.14)
-Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>= 
4.2.0~dfsg), python3-h11
+Depends: ${misc:Depends}, ${python3:Depends}, fonts-font-awesome (>= 
4.2.0~dfsg), python3-h11, python3-pkg-resources
 Conflicts: python-netlib
 Description: SSL-capable man-in-the-middle HTTP proxy
  mitmproxy is an SSL-capable man-in-the-middle HTTP proxy. It provides

Bug#925330: marked as done (unblock: qtwebkit-opensource-src/5.212.0~alpha2-21)

2019-04-01 Thread Debian Bug Tracking System 
Your message dated Mon, 1 Apr 2019 11:20:03 +0300
with message-id <20190401082003.ga15...@mitya57.me>
and subject line Re: Bug#925330: unblock: 
qtwebkit-opensource-src/5.212.0~alpha2-21
has caused the Debian Bug report #925330,
regarding unblock: qtwebkit-opensource-src/5.212.0~alpha2-21
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.)


-- 
925330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Dear Release team,

Please unblock package qtwebkit-opensource-src.

It fixes a bug of severity important: #924402. The debdiff is attached.

unblock qtwebkit-opensource-src/5.212.0~alpha2-21

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, Mar 23, 2019 at 12:06:46PM +0300, Dmitry Shachnev wrote:
> Please unblock package qtwebkit-opensource-src.
>
> It fixes a bug of severity important: #924402. The debdiff is attached.
>
> unblock qtwebkit-opensource-src/5.212.0~alpha2-21

It is in testing now, so closing this bug.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---

Bug#923184: unblock: qgis/3.4.6+dfsg-1

2019-04-01 Thread Dmitry Shachnev 
On Sun, Mar 31, 2019 at 05:29:03PM +0200, Paul Gevers wrote:
> If this helps to keep qgis in buster, yes. Please file a separate
> unblock report when you do, and please mention the checking of building
> qgis.

New sip4 is now uploaded, unblock request filed in #926150.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#924642: stretch-pu: package rsync/3.1.2-1+deb9u1

2019-04-01 Thread Paul Slootman 
On Sun 31 Mar 2019, Adam D. Barratt wrote:
> 
> Because:
> 
> Mar 15 10:54:14 /rsync_3.1.2-1+deb9u2_amd64.changes has bad PGP/GnuPG
> signature!

Damn, as this had to be built on a stretch system I had my old key on there :(

Re-signed, and re-uploaded.


Paul