Bug#854236: unblock: inkscape 0.92.1

2017-02-09 Thread Mattia Rizzolo 
Control: tag -1 - moreinfo

On Thu, Feb 09, 2017 at 06:39:00AM +, Niels Thykier wrote:
> I am ok with this provided:
> 
>  * We aim for 0.92.1 once that is released (assuming it is released
>soon)

Yes, that's my plan (0.92.2 is "planned" for April/May - I'm dreaming of
seeing stretch as stable by "then").  0.92.1 is scheduled for this week
end/early next week, should be soon enough.

>  * You are ready to react promptly to regressions

Sure.

>  * You are ready to promptly downgrade back to 0.92.0-4 plus minimal
>patches for fixing the text-height issue for the worst case.

This would be very annoying, but yes, I'm ok to do the downgrade if for
some odd reason everything crumbles and there is no good way forward.


Thank you!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#854236: unblock: inkscape 0.92.1

2017-02-09 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 - moreinfo
Bug #854236 [release.debian.org] unblock: inkscape 0.92.1
Bug #854247 [release.debian.org] unblock: inkscape 0.92.1
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.

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

Bug#854381: unblock: apt/1.4~rc1

2017-02-09 Thread David Kalnischkies 
On Thu, Feb 09, 2017 at 06:56:00AM +, Niels Thykier wrote:
> Julian Andres Klode:
> > Please unblock package apt
> 
> It seems to introduce a CI regression.
> 
> https://ci.debian.net/packages/a/apt/unstable/amd64/
[…]
| Statistics: 234 tests were run: 233 successfully and 1 failed
| Failed tests:  test-apt-tagfile-fields-order

The failing test checks if apt knows all fields dpkg knows – which as
dpkg introduced a new field "Auto-Built-Package" in 1.18.19 is making
all apt versions fail that test, we just happened to be uploading around
the same time.

(the test failed in the earlier 1.4~beta4 cases, too, if you look at the
output, 1.4~rc1 just fixed a report-test-as-always-successful case …)

Perhaps that test shouldn't be critical as we don't do much with the
fields (its about ordering them in output), but then again if it isn't
on the critical path we might end up desyncing for years again… the team
was discussing this a bit yesterday on IRC with no direct outcome, but
there will be one eventually… anyway, not a regression of 1.4 and
harmless as such.


There is another testcase regression hidden on Debian infra as its
running the tests on amd64: One test calls: date -d '0-12-25' which is
an invalid date on 32bit architectures… as the test is about the day
much more than the year a future release is going to change years.


We could be doing another upload to fix this I guess if you prefer, but
perhaps its better to get that huge diff out of the way first and deal
with these minor things later. We^WJulian will do as you prefer. ;P


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#854631: unblock: kodi/2:17.0+dfsg1-2

2017-02-09 Thread Bálint Réczey 
Hi Jonathan,

2017-02-08 22:04 GMT+01:00 Jonathan Wiltshire :
> Control: tag -1 confirmed moreinfo
>
> On Wed, Feb 08, 2017 at 09:51:32PM +0100, Balint Reczey wrote:
>> Current kodi version in Stretch is a Release Candidate
>> (2:17.0~rc3+dfsg1-2) while upstream just released final
>> Kodi 17.0.
>>
>> I believe the final version would be a better fit for
>> Stretch, while the diff between rc3 and final contains
>> quite a few bug fixes and translation updates:
>>
>> https://github.com/xbmc/xbmc/compare/4d93228e19afa928d08327...a10c5048f2487bd9b2dc1f35d2fee48a2594
>
> Skimming that comparison I'm inclined to agree.  Please be prepared to take
> prompt action (which might include reverting) if there are regressions
> though.
>
> Please go ahead to unstable and update this bug.

Thanks, it has been accepted to unstable.

Cheers,
Balint

Bug#854651: unblock: debootstrap/1.0.88

2017-02-09 Thread Cyril Brulebois 
Niels Thykier  (2017-02-09):
> Steve McIntyre:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Hey folks,
> > 
> > Please unblock debootstrap 1.0.88
> > 
> > We have a tiny fix for #836525, which will allow debootstrap to deal
> > with arch-qualified dependencies. It'll be a major PITA if debootstrap
> > can't deal with these in stretch. 
> > 
> > KiBi already knows about this upload and is happy AFAIK. He and I have
> > both tested the patch.
> > 
> > [...]
> > 
> 
> Unblocked from my PoV.  For good measure, I'll just have KiBi confirm
> that it is not going to disturb any test/release planning for d-i atm. :)

It would be nice if one could address #817236 at some point. Fixing
other bugs is nice but…

Fine for the unblock anyway.


KiBi.


signature.asc
Description: Digital signature

Bug#854674: unblock: puppet/4.8.2-2

2017-02-09 Thread Apollon Oikonomopoulos 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package puppet.

4.8.2-2 fixes a critical bug (#854487) introduced in 4.8.1-3. In short, 
the puppet package will enable the puppet service by default and puppet 
will try to connect to the 'puppet' host and receive configuration, 
which may or may not be intended.

Previously, our safeguard against this was to start the puppet service, 
but leave the agent locked, which meant it would not apply any 
configuration whatsoever. Unfortunately, this proved to be fragile and 
stopped working when the agent lock path changed.

The fix for this in unstable is to simply not enable the service on new 
installations at all, rather than enable it but lock the agent. This is 
a better approach for a number of reasons (resource waste, many systems 
running puppet under cron anyway etc). The change is properly 
documented, and also handles the upgrade path from Jessie. See the 
attached source debdiff for details.

unblock puppet/4.8.2-2
diff -Nru puppet-4.8.2/debian/changelog puppet-4.8.2/debian/changelog
--- puppet-4.8.2/debian/changelog	2017-01-23 14:39:14.0 +0200
+++ puppet-4.8.2/debian/changelog	2017-02-08 15:24:55.0 +0200
@@ -1,3 +1,18 @@
+puppet (4.8.2-2) unstable; urgency=high
+
+  * Do not enable the puppet service by default on fresh installs
+(Closes: #854487).
++ Preserve the agent lock on upgrade from 3.x to safeguard upgrades from
+  Jessie systems where puppet was installed but never used.
+  * Update the DEP-8 tests to check that the service is disabled.
+  * Strip the agent locking logic from puppet.preinst now that we disable the
+service by default.
+  * Add a debian/NEWS entry documenting the disabled service.
+  * Update the information in README.Debian and remove the (now obsolete)
+paragraph about stored configs.
+
+ -- Apollon Oikonomopoulos   Wed, 08 Feb 2017 15:24:55 +0200
+
 puppet (4.8.2-1) unstable; urgency=medium
 
   * New upstream bugfix release.
diff -Nru puppet-4.8.2/debian/NEWS puppet-4.8.2/debian/NEWS
--- puppet-4.8.2/debian/NEWS	2017-01-23 14:37:53.0 +0200
+++ puppet-4.8.2/debian/NEWS	2017-02-08 15:24:55.0 +0200
@@ -1,3 +1,21 @@
+puppet (4.8.2-2) unstable; urgency=high
+
+  As of 4.8.2-2, the puppet service is not enabled by default on new
+  installations and has to be manually enabled using
+
+  systemctl enable puppet.service
+  or
+  update-rc.d puppet enable
+
+  if desired. Note that upgrades from previous puppet versions are not
+  affected by this change and will preserve the service status.
+
+  Since some versions of the package shipped with the service enabled by
+  default, if you are upgrading please check and make sure that the service on
+  your system is properly enabled or disabled to match your preference.
+
+ -- Apollon Oikonomopoulos   Wed, 08 Feb 2017 17:43:52 +0200
+
 puppet (4.8.1-2) unstable; urgency=medium
 
   The Ruby Puppet master as shipped in Debian can currently handle Puppet 3.x
diff -Nru puppet-4.8.2/debian/puppet.postinst puppet-4.8.2/debian/puppet.postinst
--- puppet-4.8.2/debian/puppet.postinst	2017-01-23 14:37:53.0 +0200
+++ puppet-4.8.2/debian/puppet.postinst	2017-02-08 15:24:55.0 +0200
@@ -31,15 +31,24 @@
 	# Create folders common to "puppet" and "puppetmaster", which need
 	# to be owned by the "puppet" user
 	install --owner puppet --group puppet --directory \
-		/var/lib/puppet/state
+		/var/cache/puppet/state
 
-	# Between 4.4.1-2 and 4.8.1-3, puppet was called 'puppet-agent'
-	# Preserve the systemd and SysV service states
-	if [ -n "$2" ] && dpkg --compare-versions "$2" gt "4.4.1-2~" && \
+	if [ -z "$2" ]; then
+		# Disable the service by default on new installations
+		update-rc.d puppet defaults >/dev/null || true
+		update-rc.d puppet disable >/dev/null || true
+	elif [ -n "$2" ] && dpkg --compare-versions "$2" gt "4.4.2-1~" && \
 		dpkg --compare-versions "$2" lt "4.8.1-3~"; then
+		# Between 4.4.2-1 and 4.8.1-3, puppet was called 'puppet-agent'
+		# Preserve the systemd and SysV service states
 		if deb-systemd-helper debian-installed puppet-agent.service; then
-			if ! deb-systemd-helper --quiet was-enabled puppet-agent.service; then
-deb-systemd-helper unmask puppet.service >/dev/null || true
+			# dh_systemd_enable will not enable the service by
+			# default as of 4.8.2-2; enable it if puppet-agent was
+			# enabled.
+			deb-systemd-helper unmask puppet.service >/dev/null || true
+			if deb-systemd-helper --quiet was-enabled puppet-agent.service; then
+deb-systemd-helper enable puppet.service >/dev/null || true
+			else
 deb-systemd-helper update-state puppet.service >/dev/null || true
 			fi
 		fi
@@ -53,6 +62,18 @@
 		# Remove puppet-agent's symlinks to avoid duplicate starts
 		# under SysV
 		update-rc.d -f puppet-agent remove >/dev/null || true
+	elif [ -n "$2" ] && dpkg --compare-versions "$2" lt "4.4.2-1~";

Bug#854676: unblock: xrdp/0.9.1-5 [RC]

2017-02-09 Thread Dominik George 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package xrdp

The upload fixes the release critical bug #854548.

Unfortunately, a Forwarded: header in another patch file slipped in… I
do not think it makes the package unfit for migration, but do I have to
make a new upload and add it to the changelog?

- --- xrdp-0.9.1/debian/changelog 2017-01-25 18:10:11.0 +0100
+++ xrdp-0.9.1/debian/changelog 2017-02-09 12:47:36.0 +0100
@@ -1,3 +1,9 @@
+xrdp (0.9.1-5) unstable; urgency=medium
+
+  * Ensure creation of /run directory. (Closes: #854548)
+
+ -- Dominik George   Thu, 09 Feb 2017 12:47:36 +0100
+
 xrdp (0.9.1-4) unstable; urgency=high
 
   [ Thorsten Glaser ]
diff -Nru xrdp-0.9.1/debian/patches/lfs.diff xrdp-0.9.1/debian/patches/lfs.diff
- --- xrdp-0.9.1/debian/patches/lfs.diff  2017-01-25 18:03:33.0 +0100
+++ xrdp-0.9.1/debian/patches/lfs.diff  2017-02-06 21:57:37.0 +0100
@@ -1,5 +1,6 @@
 From: Thorsten Glaser 
 Subject: Enable Large File Support on (at least) 32-bit Linux
+Forwarded: https://github.com/neutrinolabs/xrdp/issues/647
 Reviewed-by: Dominik George 
 --- a/configure.ac
 +++ b/configure.ac
diff -Nru xrdp-0.9.1/debian/patches/systemd.diff 
xrdp-0.9.1/debian/patches/systemd.diff
- --- xrdp-0.9.1/debian/patches/systemd.diff  2017-01-25 18:10:11.0 
+0100
+++ xrdp-0.9.1/debian/patches/systemd.diff  2017-02-09 12:47:28.0 
+0100
@@ -3,7 +3,7 @@
 Forwarded: https://github.com/neutrinolabs/xrdp/pull/646
 --- a/instfiles/xrdp-sesman.service
 +++ b/instfiles/xrdp-sesman.service
- -@@ -1,12 +1,13 @@
+@@ -1,12 +1,14 @@
  [Unit]
  Description=xrdp session manager
 -After=syslog.target network.target
@@ -17,12 +17,13 @@
  Type=forking
 -PIDFile=/var/run/xrdp-sesman.pid
 +PIDFile=/run/xrdp/xrdp-sesman.pid
++RuntimeDirectory=xrdp
  EnvironmentFile=-/etc/sysconfig/xrdp
  EnvironmentFile=-/etc/default/xrdp
  ExecStart=/usr/sbin/xrdp-sesman $SESMAN_OPTIONS
 --- a/instfiles/xrdp.service
 +++ b/instfiles/xrdp.service
- -@@ -1,13 +1,16 @@
+@@ -1,13 +1,17 @@
  [Unit]
  Description=xrdp daemon
 +Documentation=man:xrdp(8) man:xrdp.ini(5)
@@ -34,6 +35,7 @@
  Type=forking
 -PIDFile=/var/run/xrdp.pid
 +PIDFile=/run/xrdp/xrdp.pid
++RuntimeDirectory=xrdp
  EnvironmentFile=-/etc/sysconfig/xrdp
  EnvironmentFile=-/etc/default/xrdp
 +User=xrdp

unblock xrdp/0.9.1-5

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlicXqExGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pYoHg//Q08RXyzpYCe+zbR3e8o7YB2hhC+R
zFKXct+nlpSR4TpXw3q26cx5GkeC/KsweHkuNJWN8MbNCw/TzLmBnF7YpFVj+/P0
hKoAnl07rr8mKtl6cp2MdYXR8/QsOSJR6tyvb8yHitrTpqt2MH6XhXvoMj0y6u3D
4bbb7vYdKSwmFVOGArdrW+T2tzfdrnzhrhIt6nYSJorpSAsMOAAwhZxtlNVnQh6q
miNGVbgCnD7Dbo8Vlmv9WCiA4EzOe2HOw/XhBLX4LwqxUT2OuL56V2VYyc0Q6wGt
nX1xBC9MFKdc+Uw4ukST0ZvUA75JyI7zqb02RjEbn5/iNlbVy07zOClfYb2OqoVI
UZ67938yw3sAgHkm8E327er1LQEvTrGBB9PHsp9BJjJeR7w6CEU6zwLIaw/ZAJrY
AiYU8/oAw38FzpPp5lCOuStCdP9IlrD09CZG67HbrJl+YWU2DkdoPEqNJ8649s75
XzobFAR40KTaemD81+zVEI8JUI3g6MA5yNAWvh9Qk+tm3kQizBmJ/4jYnrA89EcV
0CGVhW9ibCFUou2QWde2M5U04UwrChCU5AprqEwXMg8BTUvrTV8gxuOpVmGZf1Bh
t7uDagV2XFKwoahoYlM2b9yUCLBgWnSNwRC8aCKDXlOGcWT4M9orYsHYhpr11y9O
nvAX54I8gPbzr6I=
=jNIf
-END PGP SIGNATURE-

Bug#854678: unblock: lasagne/0.1+git20160728.8b66737-2

2017-02-09 Thread Daniel Stender 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi release team,

please unblock package lasagne. The new upload closes RC bug #834910.

Please see the attached debdiff for changes.

Thank you,
Daniel Stender

unblock lasagne/0.1+git20160728.8b66737-2

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru lasagne-0.1+git20160728.8b66737/debian/changelog lasagne-0.1+git20160728.8b66737/debian/changelog
--- lasagne-0.1+git20160728.8b66737/debian/changelog	2016-08-19 18:46:45.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/changelog	2017-02-09 12:25:30.0 +0100
@@ -1,3 +1,10 @@
+lasagne (0.1+git20160728.8b66737-2) unstable; urgency=medium
+
+  * Use inspect.signature instead of inspect.getargspec if possible
+(Closes: #834910) [Ole Streicher].
+
+ -- Daniel Stender   Thu, 09 Feb 2017 12:25:30 +0100
+
 lasagne (0.1+git20160728.8b66737-1) unstable; urgency=medium
 
   * Initial release (Closes: #818641).
diff -Nru lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch
--- lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch	1970-01-01 01:00:00.0 +0100
+++ lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch	2017-02-09 12:25:24.0 +0100
@@ -0,0 +1,42 @@
+Author: Ole Streicher 
+Description: Use inspect.signature instead of inspect.getargspec if possible
+ inspect.getargspec is deprectated in Python 3.5 and causes a warning.
+ The deprecation warning caused failures in test_get_output_with_unused_kwarg and
+ test_get_output_with_no_unused_kwarg.
+Bug: https://bugs.debian.org/834910
+Forwarded: https://github.com/Lasagne/Lasagne/pull/797
+--- a/lasagne/layers/helper.py
 b/lasagne/layers/helper.py
+@@ -1,6 +1,6 @@
+ from collections import deque
+ from difflib import get_close_matches
+-from inspect import getargspec
++import inspect
+ from itertools import chain
+ from warnings import warn
+ 
+@@ -9,6 +9,15 @@
+ 
+ from .. import utils
+ 
++def getargs(callable):
++try:
++pars = inspect.signature(callable).parameters
++return (list(pars.keys()),
++tuple(p.default for p in pars.values()
++  if p.default is not p.empty))
++except AttributeError:
++name, _, _, defaults = inspect.getargspec(callable)
++return (name, defaults)
+ 
+ __all__ = [
+ "get_all_layers",
+@@ -190,7 +199,7 @@
+  % layer)
+ all_outputs[layer] = layer.get_output_for(layer_inputs, **kwargs)
+ try:
+-names, _, _, defaults = getargspec(layer.get_output_for)
++names, defaults = getargs(layer.get_output_for)
+ except TypeError:
+ # If introspection is not possible, skip it
+ pass
diff -Nru lasagne-0.1+git20160728.8b66737/debian/patches/series lasagne-0.1+git20160728.8b66737/debian/patches/series
--- lasagne-0.1+git20160728.8b66737/debian/patches/series	2016-08-18 20:59:52.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/patches/series	2017-02-09 12:15:56.0 +0100
@@ -1,2 +1,3 @@
 pytest-no-cov-pep8.patch
 use-mathjax-package.patch
+remove-deprecated.patch
diff -Nru lasagne-0.1+git20160728.8b66737/debian/rules lasagne-0.1+git20160728.8b66737/debian/rules
--- lasagne-0.1+git20160728.8b66737/debian/rules	2016-08-18 20:59:52.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/rules	2017-02-09 12:15:56.0 +0100
@@ -8,7 +8,7 @@
 	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_test:
-	PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -rs lasagne/" dh_auto_test || true # 2 fails with Python 3.5 remain
+	PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -rs lasagne/" dh_auto_test
 
 override_dh_auto_install:
 	dh_auto_install

Bug#854685: unblock: viewvc/1.1.26-1

2017-02-09 Thread Sebastien Delafond 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,

the Security Team would like to request the unblocking of viewvc, which
fixes #854681 (CVE-2017-5938, XSS). DSA-3784-1 was just issued, fixing
this same issue in jessie-security.

The debdiff (below) is a tad larger than it ought to be, because:

  1. all copyright dates were updated to include "2017"
  2. the source wasn't repacked to omit Windows-specific code, like it
 was in 1.1.25+repack-1.

However, the only actual change is indeed the fix for CVE-2017-5938.

Here is the debdiff:


diff -Nru viewvc-1.1.25+repack/bin/asp/query.asp viewvc-1.1.26/bin/asp/query.asp
--- viewvc-1.1.25+repack/bin/asp/query.asp  2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/asp/query.asp 2017-01-25 00:07:15.0 +0100
@@ -3,7 +3,7 @@
 
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/asp/viewvc.asp 
viewvc-1.1.26/bin/asp/viewvc.asp
--- viewvc-1.1.25+repack/bin/asp/viewvc.asp 2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/asp/viewvc.asp2017-01-25 00:07:15.0 +0100
@@ -3,7 +3,7 @@
 
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cgi/query.cgi viewvc-1.1.26/bin/cgi/query.cgi
--- viewvc-1.1.25+repack/bin/cgi/query.cgi  2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/cgi/query.cgi 2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cgi/viewvc.cgi 
viewvc-1.1.26/bin/cgi/viewvc.cgi
--- viewvc-1.1.25+repack/bin/cgi/viewvc.cgi 2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/cgi/viewvc.cgi2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cvsdbadmin viewvc-1.1.26/bin/cvsdbadmin
--- viewvc-1.1.25+repack/bin/cvsdbadmin 2016-09-15 21:38:32.0 +0200
+++ viewvc-1.1.26/bin/cvsdbadmin2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/loginfo-handler 
viewvc-1.1.26/bin/loginfo-handler
--- viewvc-1.1.25+repack/bin/loginfo-handler2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/loginfo-handler   2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/make-database viewvc-1.1.26/bin/make-database
--- viewvc-1.1.25+repack/bin/make-database  2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/make-database 2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/mod_python/handler.py 
viewvc-1.1.26/bin/mod_python/handler.py
--- viewvc-1.1.25+repack/bin/mod_python/handler.py  2016-09-15 
21:38:32.0 +0200
+++ viewvc-1.1.26/bin/mod_python/handler.py 2017-01-25 00:07:1

Bug#854700: unblock: libproxy/0.4.14-2

2017-02-09 Thread Laurent Bigonville 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

Please unblock package libproxy

I recently discovered that the networkmanager libproxy plugin was not
listening to the correct NM event meaning that the cache of libproxy was
not properly cleaned up in case of network topology change.

After fixing that bug, I discovered that I could create a segfault in
some situation when the cache was invalidated.

The two patches have already been merged upstream

Upstream bug: https://github.com/libproxy/libproxy/issues/58 and
https://github.com/libproxy/libproxy/issues/59

unblock libproxy/0.4.14-2

Regards,

Laurent Bigonville

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libproxy-0.4.14/debian/changelog libproxy-0.4.14/debian/changelog
--- libproxy-0.4.14/debian/changelog2017-01-22 13:58:45.0 +0100
+++ libproxy-0.4.14/debian/changelog2017-02-08 12:17:50.0 +0100
@@ -1,3 +1,11 @@
+libproxy (0.4.14-2) unstable; urgency=medium
+
+  * debian/patches/fix-clean-reload-cache.patch: Make sure that the PAC/WPAD
+cache is cleanup when network topology changes and prevent a segfault in
+the process, patches merged upstream.
+
+ -- Laurent Bigonville   Wed, 08 Feb 2017 12:17:50 +0100
+
 libproxy (0.4.14-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru libproxy-0.4.14/debian/libgproxy1-plugin-gsettings.install 
libproxy-0.4.14/debian/libgproxy1-plugin-gsettings.install
--- libproxy-0.4.14/debian/libgproxy1-plugin-gsettings.install  2013-11-26 
02:22:50.0 +0100
+++ libproxy-0.4.14/debian/libgproxy1-plugin-gsettings.install  1970-01-01 
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/lib/libproxy/0.4.7/modules/config_gnome3.so
-usr/lib/libproxy/0.4.7/pxgsettings
diff -Nru libproxy-0.4.14/debian/patches/fix-clean-reload-cache.patch 
libproxy-0.4.14/debian/patches/fix-clean-reload-cache.patch
--- libproxy-0.4.14/debian/patches/fix-clean-reload-cache.patch 1970-01-01 
01:00:00.0 +0100
+++ libproxy-0.4.14/debian/patches/fix-clean-reload-cache.patch 2017-02-07 
16:48:06.0 +0100
@@ -0,0 +1,52 @@
+From 1bf46e951b9d35e2e5ad61c85b15f32496017247 Mon Sep 17 00:00:00 2001
+From: Laurent Bigonville 
+Date: Tue, 7 Feb 2017 16:02:29 +0100
+Subject: [PATCH] Use StateChanged signal instead of StateChange
+
+StateChange signal has been deprecated since NM 0.7 and has been
+completely removed in 0.9, see:
+https://developer.gnome.org/NetworkManager/0.9/ref-migrating.html
+
+Closes: #58
+---
+ libproxy/modules/network_networkmanager.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/libproxy/modules/network_networkmanager.cpp 
b/libproxy/modules/network_networkmanager.cpp
+index 5198860..546a8ee 100644
+--- a/libproxy/modules/network_networkmanager.cpp
 b/libproxy/modules/network_networkmanager.cpp
+@@ -62,7 +62,7 @@ class networkmanager_network_extension : public 
network_extension {
+ 
+   // If connection was successful, set it up
+   dbus_connection_set_exit_on_disconnect(conn, false);
+-  dbus_bus_add_match(conn, "type='signal',interface='" 
NM_DBUS_INTERFACE "',member='StateChange'", NULL);
++  dbus_bus_add_match(conn, "type='signal',interface='" 
NM_DBUS_INTERFACE "',member='StateChanged'", NULL);
+   dbus_connection_flush(conn);
+   }
+ 
+From 0bdcf9f9dbee67dee47694e0012fa891588abc89 Mon Sep 17 00:00:00 2001
+From: Laurent Bigonville 
+Date: Tue, 7 Feb 2017 16:05:00 +0100
+Subject: [PATCH] Set lasturl to NULL after free/delete
+
+It avoids the lasturl to be freed a 2nd time when the rewind() method is
+called.
+
+Closes: #59
+---
+ libproxy/modules/wpad_dns_alias.cpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/libproxy/modules/wpad_dns_alias.cpp 
b/libproxy/modules/wpad_dns_alias.cpp
+index 669dccf..5b8c2e0 100644
+--- a/libproxy/modules/wpad_dns_alias.cpp
 b/libproxy/modules/wpad_dns_alias.cpp
+@@ -39,6 +39,7 @@ class dns_alias_wpad_extension : public wpad_extension {
+   lastpac = *pac = lasturl->get_pac();
+   if (!lastpac) {
+   delete lasturl;
++  lasturl = NULL;
+   return NULL;
+   }
+ 
diff -Nru libproxy-0.4.14/debian/patches/series 
libproxy-0.4.14/debian/patches/series
--- libproxy-0.4.14/debian/patches/series   2017-01-22 13:49:57.0 
+0100
+++ libproxy-0.4.14/debian/patches/series   2017-02-07 16:48:25.0 
+0100
@@ -1 +1,2 @@
 disable-pac-test.patch
+fix-cle

Bug#854709: unblock: adwaita-icon-theme/3.22.0-2

2017-02-09 Thread Dmitry Shachnev 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package adwaita-icon-theme.

This fixes bug #853044 (of severity: important) — it was impossible to use
the Adwaita-dark GTK+ 3 theme. The fix is a backport of two small upstream
commits.

The debdiff of what I uploaded is attached.

unblock adwaita-icon-theme/3.22.0-2

--
Dmitry Shachnev
diff -Nru gnome-themes-standard-3.22.2/debian/changelog gnome-themes-standard-3.22.2/debian/changelog
--- gnome-themes-standard-3.22.2/debian/changelog	2016-10-12 17:22:33.0 +0300
+++ gnome-themes-standard-3.22.2/debian/changelog	2017-02-09 20:44:59.0 +0300
@@ -1,3 +1,10 @@
+gnome-themes-standard (3.22.2-2) unstable; urgency=medium
+
+  * Backport upstream fixes to build and install the Adwaita dark theme
+properly (closes: #853044).
+
+ -- Dmitry Shachnev   Thu, 09 Feb 2017 20:44:59 +0300
+
 gnome-themes-standard (3.22.2-1) unstable; urgency=medium
 
   [ Laurent Bigonville ]
diff -Nru gnome-themes-standard-3.22.2/debian/patches/dark_theme.diff gnome-themes-standard-3.22.2/debian/patches/dark_theme.diff
--- gnome-themes-standard-3.22.2/debian/patches/dark_theme.diff	1970-01-01 03:00:00.0 +0300
+++ gnome-themes-standard-3.22.2/debian/patches/dark_theme.diff	2017-02-09 20:44:59.0 +0300
@@ -0,0 +1,28 @@
+Description: build Adwaita-dark theme properly
+Origin: upstream, commits:
+ https://git.gnome.org/browse/gnome-themes-standard/commit/?id=bf146e3ba9da90e2
+ https://git.gnome.org/browse/gnome-themes-standard/commit/?id=ae703a57261c26ad
+Last-Update: 2017-02-09
+
+--- a/themes/Adwaita-dark/gtk-3.0/Makefile.am
 b/themes/Adwaita-dark/gtk-3.0/Makefile.am
+@@ -1,4 +1,4 @@
+-themedir = $(datadir)/themes/Adwaita/gtk-3.0
++themedir = $(datadir)/themes/Adwaita-dark/gtk-3.0
+ 
+ theme_DATA = gtk.css
+ 
+--- a/themes/Adwaita-dark/index.theme.in
 b/themes/Adwaita-dark/index.theme.in
+@@ -1,9 +1,9 @@
+ [X-GNOME-Metatheme]
+-_Name=Adwaita
++_Name=Adwaita-dark
+ Type=X-GNOME-Metatheme
+ _Comment=There is only one
+ Encoding=UTF-8
+-GtkTheme=Adwaita
++GtkTheme=Adwaita-dark
+ MetacityTheme=Adwaita
+ IconTheme=Adwaita
+ CursorTheme=Adwaita
diff -Nru gnome-themes-standard-3.22.2/debian/patches/series gnome-themes-standard-3.22.2/debian/patches/series
--- gnome-themes-standard-3.22.2/debian/patches/series	2016-05-22 23:51:11.0 +0300
+++ gnome-themes-standard-3.22.2/debian/patches/series	2017-02-09 20:44:59.0 +0300
@@ -0,0 +1 @@
+dark_theme.diff


signature.asc
Description: PGP signature

Bug#854711: Unblocking package netkit-ftp-ssl, resolving #854460.

2017-02-09 Thread Mats Erik Andersson 
Package: release.debian.org
Severity: important
Tags: patch

Being the maintainer of netkit-ftp-ssl, I request an unblocking
of netkit-ftp-ssl in version 0.17.34+0.2-4. This upload resolves
successfully the bug #854460 of severity 'important'.

The problem is interoperability with TLS-able FTP servers, like
Proftpd, which mandate that the data connection reuse the session
identity set by the control channel.

The presently available version in testing, 0.17.34+0.2-3, is
not able to fetch files or get listings with TLS protection due
to an accidental inactivation of function SSL_copy_session_id().
This is a legacy function, not documented in any manual page,
and only mentioned in one file 'ssleay.txt' of the openssl archive.

The debdiff reactivates this function call, which was commented
out by me due to a misunderstanding. In addition, it turns out
to be decisive to forbid the use of libssl in version 1.1 for
the binary package. The reason being that libssl (>= 1.1.0)
only succeeds to reuse the session identity a single time,
yes really a single time, with the present unintrusive and
long time used solution. Therefore I had to change the build
dependency to read

libssl1.0-dev | libssl-dev (<< 1.1.0~)

Both changes are necessary and they lead also to a package that
can be built directly in Wheezy without any changes, allowing
trivial backporting.

The packages netkit-ftp-ssl, linux-ftpd-ssl and netkit-telnet-ssl
have seen substantial improvement for certificate verification
and identification for this Debian release, but only the binary
ftp-ssl is affected by the present issue.

Best regards,
  Mats Erik Andersson, DM
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/changelog 
netkit-ftp-ssl-0.17.34+0.2/debian/changelog
--- netkit-ftp-ssl-0.17.34+0.2/debian/changelog 2017-01-18 19:33:56.0 
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/changelog 2017-02-08 18:39:46.0 
+0100
@@ -1,3 +1,14 @@
+netkit-ftp-ssl (0.17.34+0.2-4) unstable; urgency=medium
+
+  * Correctly reuse SSL session identity in data connection.
+This suffices for libssl1.0, not for libssl1.1.  (Closes: #854460)
++ debian/patches/700_prefer_tls.diff: Reactivate commented out
+  function call to SSL_copy_session_id().
++ debian/control: Prefer libssl1.0-dev and condition libssl-dev
+  on "<< 1.1.0~" for trivial backporting.
+
+ -- Mats Erik Andersson   Wed, 08 Feb 2017 
18:39:46 +0100
+
 netkit-ftp-ssl (0.17.34+0.2-3) unstable; urgency=low
 
   * Allow verification mode to print additional details about the
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/control 
netkit-ftp-ssl-0.17.34+0.2/debian/control
--- netkit-ftp-ssl-0.17.34+0.2/debian/control   2017-01-10 15:37:21.0 
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/control   2017-02-08 18:30:50.0 
+0100
@@ -4,7 +4,7 @@
 Maintainer: Mats Erik Andersson 
 Uploaders: Alberto Gonzalez Iniesta 
 Standards-Version: 3.9.8
-Build-Depends: debhelper (>= 9), libeditline-dev, libncurses5-dev, libssl-dev 
| libssl1.0-dev
+Build-Depends: debhelper (>= 9), libeditline-dev, libncurses5-dev, 
libssl1.0-dev | libssl-dev (<< 1.1.0~)
 
 Package: ftp-ssl
 Architecture: any
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/patches/700_prefer_tls.diff 
netkit-ftp-ssl-0.17.34+0.2/debian/patches/700_prefer_tls.diff
--- netkit-ftp-ssl-0.17.34+0.2/debian/patches/700_prefer_tls.diff   
2017-01-18 19:33:41.0 +0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/patches/700_prefer_tls.diff   
2017-02-08 15:39:49.0 +0100
@@ -23,7 +23,7 @@
  .
 Author: Mats Erik Andersson 
 Forwarded: no
-Last-Update: 2017-01-18
+Last-Update: 2017-02-07
 
 diff -Naurp netkit-ftp-0.17.debian/ftp/cmds.c netkit-ftp-0.17/ftp/cmds.c
 --- netkit-ftp-0.17.debian/ftp/cmds.c  2016-12-23 00:05:51.820239257 +0100
@@ -190,20 +190,8 @@
  .Xr ftpd 8 ,
 diff -Naurp netkit-ftp-0.17.debian/ftp/ftp.c netkit-ftp-0.17/ftp/ftp.c
 --- netkit-ftp-0.17.debian/ftp/ftp.c   2016-12-23 00:05:52.380213160 +0100
-+++ netkit-ftp-0.17/ftp/ftp.c  2017-01-18 19:19:27.145786765 +0100
-@@ -1672,7 +1672,10 @@ dataconn(const char *lmode)
-* this quick assuming Eric has this going
-* okay! ;-)
-*/
--  SSL_copy_session_id(ssl_data_con,ssl_con);
-+  /* MEA: Do not use deterministic session identities
-+   * in a subordinate connection.
-+   */
-+  //SSL_copy_session_id(ssl_data_con,ssl_con);
- 
-   /* we are doing I/O and not using select so 
-* it is "safe" to read ahead
-@@ -1686,12 +1689,17 @@ dataconn(const char *lmode)
 netkit-ftp-0.17/ftp/ftp.c  2017-02-07 23:35:32.871433587 +0100
+@@ -1686,12 +1686,17 @@ dataconn(const char *lmode)
  
if ((ret=SSL_connect(ssl_data_con))<=0) {
  static char errbuf[1024];
@@ -224,7 +212,7 @@
fflush(stderr);
  
/* abort time methinks ... */
-@@ -2111,16 +2119,50 @@ printbytes(off_t bytes)
+@@ -2111,16 +2116,50 @@ printbytes(off_t by

Processed: Re: Bug#854619: unblock: svtplay-dl/1.9.1-0.1

2017-02-09 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 - moreinfo
Bug #854619 [release.debian.org] unblock: svtplay-dl/1.9.1-0.1
Removed tag(s) moreinfo.

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

Bug#854619: unblock: svtplay-dl/1.9.1-0.1

2017-02-09 Thread Mattia Rizzolo 
Control: tag -1 - moreinfo

On Wed, Feb 08, 2017 at 08:11:25PM +, Jonathan Wiltshire wrote:
> On Wed, Feb 08, 2017 at 07:05:40PM +0100, Mattia Rizzolo wrote:
> > Please consider unblocking the package svtplay-dl
> > 
> > Well, the delta is quite small despite being a new upstream release, and
> > it is needed to make the package usable again.
> 
> I disagree, the bug it closes specifically mentions a targetted fix. Your
> upload is a much more invasive new upstream. Does the targetted fix not
> work?

It probably does, but
1) the relevant commit comes after several dozen other commits since the
   version currently in stretch (actually it happened "right before" the
   1.9.1 release); I can't assume that just because the patch applies it
   doesn't depend on some subtle change done before
2) if possible, I always prefer something that an upstream says it's
   "good" rather than mess with patches, especially in small projects
   like this where that's actually feasible
3) if you glances at the upstream commit log you can see there are at
   least 3 more crash fixes, and I deem crash important enough to be
   fixed if possible

Furthermore this is a leaf package, and even if it's true the Debian
freeze doesn't distinguish between leaf and non-leaf or priority of the
package I hope you can see how there is no way this update could
jeopardize the final release.

> We find packages like this are often broken by service API changes during a
> stable lifetime; is svtplay-dl suitable for a stable release?

Another version is available in jessie, and ttbomk everything went well,
so I'd say it is, yes.  Anyway, this is a question for the actual
maintainer :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: severity of 854711 is normal, tagging 854711, user release.debian....@packages.debian.org ...

2017-02-09 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 854711 normal
Bug #854711 [release.debian.org] Unblocking package netkit-ftp-ssl, resolving 
#854460.
Severity set to 'normal' from 'important'
> tags 854711 - patch
Bug #854711 [release.debian.org] Unblocking package netkit-ftp-ssl, resolving 
#854460.
Removed tag(s) patch.
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 854711 unblock
There were no usertags set.
Usertags are now: unblock.
> thanks
Stopping processing here.

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

Bug#854236: unblock: inkscape 0.92.1

2017-02-09 Thread Niels Thykier 
Control: tags -1 confirmed

Mattia Rizzolo:
> Control: tag -1 - moreinfo
> 
> On Thu, Feb 09, 2017 at 06:39:00AM +, Niels Thykier wrote:
>> I am ok with this provided:
>>
>>  * We aim for 0.92.1 once that is released (assuming it is released
>>soon)
> 
> Yes, that's my plan (0.92.2 is "planned" for April/May - I'm dreaming of
> seeing stretch as stable by "then").  0.92.1 is scheduled for this week
> end/early next week, should be soon enough.
> 
>>  * You are ready to react promptly to regressions
> 
> Sure.
> 
>>  * You are ready to promptly downgrade back to 0.92.0-4 plus minimal
>>patches for fixing the text-height issue for the worst case.
> 
> This would be very annoying, but yes, I'm ok to do the downgrade if for
> some odd reason everything crumbles and there is no good way forward.
> 
> 
> Thank you!
> 

Please go ahead then :)

~Niels

Processed: Re: Bug#854236: unblock: inkscape 0.92.1

2017-02-09 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 confirmed
Bug #854236 [release.debian.org] unblock: inkscape 0.92.1
Bug #854247 [release.debian.org] unblock: inkscape 0.92.1
Added tag(s) confirmed.
Added tag(s) confirmed.

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

Bug#854524: marked as done (unblock: linux/4.9.6-3)

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Thu, 9 Feb 2017 22:51:23 +0100
with message-id <20170209215121.ga25...@ugent.be>
and subject line Re: Bug#854524: unblock: linux/4.9.6-3
has caused the Debian Bug report #854524,
regarding unblock: linux/4.9.6-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

This includes many important bug fixes, including security fixes, and
new hardware support.  It also disables logfs, which is being removed
in Linux 4.10 and therefore would not be supportable in stretch.

The debdiff would be too large for you to review, unfortunately.
Instead, here are the changelog entries:

linux (4.9.6-3) unstable; urgency=medium

  * btree,musb,st_sensors: Ignore ABI changes (fixes FTBFS on armel,armhf)

 -- Ben Hutchings   Sat, 28 Jan 2017 16:11:16 +

linux (4.9.6-2) unstable; urgency=medium

  * linux-cpupower: Use dh-exec architecture filtering for x86-specific files
(fixes FTBFS on !x86)

 -- Ben Hutchings   Fri, 27 Jan 2017 22:09:50 +

linux (4.9.6-1) unstable; urgency=medium

  * New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.3
- iio: common: st_sensors: fix channel data parsing
- [mips] staging: octeon: Call SET_NETDEV_DEV()
- ALSA: hda - Fix up GPIO for ASUS ROG Ranger
- ALSA: hda - Apply asus-mode8 fixup to ASUS X71SL
- ALSA: usb-audio: Fix irq/process data synchronization
- fscrypt: fix renaming and linking special files
- [hppa/parisc] Add line-break when printing segfault info
- [hppa/parisc] Mark cr16 clocksource unstable on SMP systems
- HID: sensor-hub: Move the memset to sensor_hub_get_feature()
- mac80211: initialize fast-xmit 'info' later
- asm-prototypes: Clear any CPP defines before declaring the functions
- [x86] drm/i915: Fix oopses in the overlay code due to i915_gem_active
  stuff
- [x86] drm/i915: Fix oops in overlay due to frontbuffer tracking
- [x86] drm/i915: Force VDD off on the new power seqeuencer before
  starting to use it
- [x86] drm/i915: Initialize overlay->last_flip properly
- [x86] KVM: reset MMU on KVM_SET_VCPU_EVENTS
- [armhf] usb: musb: core: add clear_ep_rxintr() to musb_platform_ops
- [armhf] usb: musb: dsps: implement clear_ep_rxintr() callback
- usb: storage: unusual_uas: Add JMicron JMS56x to unusual device
- usb: gadgetfs: restrict upper bound on device configuration size
- USB: gadgetfs: fix unbounded memory allocation bug
- USB: gadgetfs: fix use-after-free bug
- USB: gadgetfs: fix checks of wTotalLength in config descriptors
- USB: fix problems with duplicate endpoint addresses
- usb: gadget: composite: Test get_alt() presence instead of set_alt()
- [arm64, armhf] usb: dwc3: core: avoid Overflow events
- usb: xhci: fix possible wild pointer
- [x86] usb: xhci: apply XHCI_PME_STUCK_QUIRK to Intel Apollo Lake
- xhci: free xhci virtual devices with leaf nodes first
- usb: xhci: fix return value of xhci_setup_device()
- usb: host: xhci: Fix possible wild pointer when handling abort command
- xhci: Handle command completion and timeout race
- usb: xhci: hold lock over xhci_abort_cmd_ring()
- USB: serial: omninet: fix NULL-derefs at open and disconnect
- USB: serial: quatech2: fix sleep-while-atomic in close
- USB: serial: pl2303: fix NULL-deref at open
- USB: serial: keyspan_pda: verify endpoints at probe
- USB: serial: spcp8x5: fix NULL-deref at open
- USB: serial: io_ti: fix NULL-deref at open
- USB: serial: io_ti: fix another NULL-deref at open
- USB: serial: io_ti: fix I/O after disconnect
- USB: serial: iuu_phoenix: fix NULL-deref at open
- USB: serial: garmin_gps: fix memory leak on failed URB submit
- USB: serial: ti_usb_3410_5052: fix NULL-deref at open
- USB: serial: io_edgeport: fix NULL-deref at open
- USB: serial: oti6858: fix NULL-deref at open
- USB: serial: cyberjack: fix NULL-deref at open
- USB: serial: kobil_sct: fix NULL-deref in write
- USB: serial: mos7840: fix NULL-deref at open
- USB: serial: mos7720: fix NULL-deref at open
- USB: serial: mos7720: fix use-after-free on probe errors
- USB: serial: mos7720: fix parport use-after-free on probe errors
- USB: serial: mos7720: fix parallel probe
- usb: xhci-m

Bug#854676: marked as done (unblock: xrdp/0.9.1-5 [RC])

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Thu, 9 Feb 2017 23:03:00 +0100
with message-id <20170209220258.ga25...@ugent.be>
and subject line Re: unblock: xrdp/0.9.1-5 [RC]
has caused the Debian Bug report #854676,
regarding unblock: xrdp/0.9.1-5 [RC]
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package xrdp

The upload fixes the release critical bug #854548.

Unfortunately, a Forwarded: header in another patch file slipped in… I
do not think it makes the package unfit for migration, but do I have to
make a new upload and add it to the changelog?

- --- xrdp-0.9.1/debian/changelog 2017-01-25 18:10:11.0 +0100
+++ xrdp-0.9.1/debian/changelog 2017-02-09 12:47:36.0 +0100
@@ -1,3 +1,9 @@
+xrdp (0.9.1-5) unstable; urgency=medium
+
+  * Ensure creation of /run directory. (Closes: #854548)
+
+ -- Dominik George   Thu, 09 Feb 2017 12:47:36 +0100
+
 xrdp (0.9.1-4) unstable; urgency=high
 
   [ Thorsten Glaser ]
diff -Nru xrdp-0.9.1/debian/patches/lfs.diff xrdp-0.9.1/debian/patches/lfs.diff
- --- xrdp-0.9.1/debian/patches/lfs.diff  2017-01-25 18:03:33.0 +0100
+++ xrdp-0.9.1/debian/patches/lfs.diff  2017-02-06 21:57:37.0 +0100
@@ -1,5 +1,6 @@
 From: Thorsten Glaser 
 Subject: Enable Large File Support on (at least) 32-bit Linux
+Forwarded: https://github.com/neutrinolabs/xrdp/issues/647
 Reviewed-by: Dominik George 
 --- a/configure.ac
 +++ b/configure.ac
diff -Nru xrdp-0.9.1/debian/patches/systemd.diff 
xrdp-0.9.1/debian/patches/systemd.diff
- --- xrdp-0.9.1/debian/patches/systemd.diff  2017-01-25 18:10:11.0 
+0100
+++ xrdp-0.9.1/debian/patches/systemd.diff  2017-02-09 12:47:28.0 
+0100
@@ -3,7 +3,7 @@
 Forwarded: https://github.com/neutrinolabs/xrdp/pull/646
 --- a/instfiles/xrdp-sesman.service
 +++ b/instfiles/xrdp-sesman.service
- -@@ -1,12 +1,13 @@
+@@ -1,12 +1,14 @@
  [Unit]
  Description=xrdp session manager
 -After=syslog.target network.target
@@ -17,12 +17,13 @@
  Type=forking
 -PIDFile=/var/run/xrdp-sesman.pid
 +PIDFile=/run/xrdp/xrdp-sesman.pid
++RuntimeDirectory=xrdp
  EnvironmentFile=-/etc/sysconfig/xrdp
  EnvironmentFile=-/etc/default/xrdp
  ExecStart=/usr/sbin/xrdp-sesman $SESMAN_OPTIONS
 --- a/instfiles/xrdp.service
 +++ b/instfiles/xrdp.service
- -@@ -1,13 +1,16 @@
+@@ -1,13 +1,17 @@
  [Unit]
  Description=xrdp daemon
 +Documentation=man:xrdp(8) man:xrdp.ini(5)
@@ -34,6 +35,7 @@
  Type=forking
 -PIDFile=/var/run/xrdp.pid
 +PIDFile=/run/xrdp/xrdp.pid
++RuntimeDirectory=xrdp
  EnvironmentFile=-/etc/sysconfig/xrdp
  EnvironmentFile=-/etc/default/xrdp
 +User=xrdp

unblock xrdp/0.9.1-5

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlicXqExGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pYoHg//Q08RXyzpYCe+zbR3e8o7YB2hhC+R
zFKXct+nlpSR4TpXw3q26cx5GkeC/KsweHkuNJWN8MbNCw/TzLmBnF7YpFVj+/P0
hKoAnl07rr8mKtl6cp2MdYXR8/QsOSJR6tyvb8yHitrTpqt2MH6XhXvoMj0y6u3D
4bbb7vYdKSwmFVOGArdrW+T2tzfdrnzhrhIt6nYSJorpSAsMOAAwhZxtlNVnQh6q
miNGVbgCnD7Dbo8Vlmv9WCiA4EzOe2HOw/XhBLX4LwqxUT2OuL56V2VYyc0Q6wGt
nX1xBC9MFKdc+Uw4ukST0ZvUA75JyI7zqb02RjEbn5/iNlbVy07zOClfYb2OqoVI
UZ67938yw3sAgHkm8E327er1LQEvTrGBB9PHsp9BJjJeR7w6CEU6zwLIaw/ZAJrY
AiYU8/oAw38FzpPp5lCOuStCdP9IlrD09CZG67HbrJl+YWU2DkdoPEqNJ8649s75
XzobFAR40KTaemD81+zVEI8JUI3g6MA5yNAWvh9Qk+tm3kQizBmJ/4jYnrA89EcV
0CGVhW9ibCFUou2QWde2M5U04UwrChCU5AprqEwXMg8BTUvrTV8gxuOpVmGZf1Bh
t7uDagV2XFKwoahoYlM2b9yUCLBgWnSNwRC8aCKDXlOGcWT4M9orYsHYhpr11y9O
nvAX54I8gPbzr6I=
=jNIf
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi,

On Thu, Feb 09, 2017 at 01:20:50PM +0100, Dominik George wrote:
> Please unblock package xrdp

Unblocked.

Thanks,

Ivo--- End Message ---

Bug#854678: marked as done (unblock: lasagne/0.1+git20160728.8b66737-2)

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Thu, 9 Feb 2017 23:55:20 +0100
with message-id <20170209225518.ga26...@ugent.be>
and subject line Re: unblock: lasagne/0.1+git20160728.8b66737-2
has caused the Debian Bug report #854678,
regarding unblock: lasagne/0.1+git20160728.8b66737-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.)


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

Hi release team,

please unblock package lasagne. The new upload closes RC bug #834910.

Please see the attached debdiff for changes.

Thank you,
Daniel Stender

unblock lasagne/0.1+git20160728.8b66737-2

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru lasagne-0.1+git20160728.8b66737/debian/changelog lasagne-0.1+git20160728.8b66737/debian/changelog
--- lasagne-0.1+git20160728.8b66737/debian/changelog	2016-08-19 18:46:45.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/changelog	2017-02-09 12:25:30.0 +0100
@@ -1,3 +1,10 @@
+lasagne (0.1+git20160728.8b66737-2) unstable; urgency=medium
+
+  * Use inspect.signature instead of inspect.getargspec if possible
+(Closes: #834910) [Ole Streicher].
+
+ -- Daniel Stender   Thu, 09 Feb 2017 12:25:30 +0100
+
 lasagne (0.1+git20160728.8b66737-1) unstable; urgency=medium
 
   * Initial release (Closes: #818641).
diff -Nru lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch
--- lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch	1970-01-01 01:00:00.0 +0100
+++ lasagne-0.1+git20160728.8b66737/debian/patches/remove-deprecated.patch	2017-02-09 12:25:24.0 +0100
@@ -0,0 +1,42 @@
+Author: Ole Streicher 
+Description: Use inspect.signature instead of inspect.getargspec if possible
+ inspect.getargspec is deprectated in Python 3.5 and causes a warning.
+ The deprecation warning caused failures in test_get_output_with_unused_kwarg and
+ test_get_output_with_no_unused_kwarg.
+Bug: https://bugs.debian.org/834910
+Forwarded: https://github.com/Lasagne/Lasagne/pull/797
+--- a/lasagne/layers/helper.py
 b/lasagne/layers/helper.py
+@@ -1,6 +1,6 @@
+ from collections import deque
+ from difflib import get_close_matches
+-from inspect import getargspec
++import inspect
+ from itertools import chain
+ from warnings import warn
+ 
+@@ -9,6 +9,15 @@
+ 
+ from .. import utils
+ 
++def getargs(callable):
++try:
++pars = inspect.signature(callable).parameters
++return (list(pars.keys()),
++tuple(p.default for p in pars.values()
++  if p.default is not p.empty))
++except AttributeError:
++name, _, _, defaults = inspect.getargspec(callable)
++return (name, defaults)
+ 
+ __all__ = [
+ "get_all_layers",
+@@ -190,7 +199,7 @@
+  % layer)
+ all_outputs[layer] = layer.get_output_for(layer_inputs, **kwargs)
+ try:
+-names, _, _, defaults = getargspec(layer.get_output_for)
++names, defaults = getargs(layer.get_output_for)
+ except TypeError:
+ # If introspection is not possible, skip it
+ pass
diff -Nru lasagne-0.1+git20160728.8b66737/debian/patches/series lasagne-0.1+git20160728.8b66737/debian/patches/series
--- lasagne-0.1+git20160728.8b66737/debian/patches/series	2016-08-18 20:59:52.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/patches/series	2017-02-09 12:15:56.0 +0100
@@ -1,2 +1,3 @@
 pytest-no-cov-pep8.patch
 use-mathjax-package.patch
+remove-deprecated.patch
diff -Nru lasagne-0.1+git20160728.8b66737/debian/rules lasagne-0.1+git20160728.8b66737/debian/rules
--- lasagne-0.1+git20160728.8b66737/debian/rules	2016-08-18 20:59:52.0 +0200
+++ lasagne-0.1+git20160728.8b66737/debian/rules	2017-02-09 12:15:56.0 +0100
@@ -8,7 +8,7 @@
 	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_test:
-	PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -rs lasagne/" dh_auto_test || true # 2 fails with Python 3.5 remain
+	PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{inte

Bug#854674: marked as done (unblock: puppet/4.8.2-2)

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Thu, 9 Feb 2017 23:59:20 +0100
with message-id <20170209225918.ga26...@ugent.be>
and subject line Re: unblock: puppet/4.8.2-2
has caused the Debian Bug report #854674,
regarding unblock: puppet/4.8.2-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.)


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

4.8.2-2 fixes a critical bug (#854487) introduced in 4.8.1-3. In short, 
the puppet package will enable the puppet service by default and puppet 
will try to connect to the 'puppet' host and receive configuration, 
which may or may not be intended.

Previously, our safeguard against this was to start the puppet service, 
but leave the agent locked, which meant it would not apply any 
configuration whatsoever. Unfortunately, this proved to be fragile and 
stopped working when the agent lock path changed.

The fix for this in unstable is to simply not enable the service on new 
installations at all, rather than enable it but lock the agent. This is 
a better approach for a number of reasons (resource waste, many systems 
running puppet under cron anyway etc). The change is properly 
documented, and also handles the upgrade path from Jessie. See the 
attached source debdiff for details.

unblock puppet/4.8.2-2
diff -Nru puppet-4.8.2/debian/changelog puppet-4.8.2/debian/changelog
--- puppet-4.8.2/debian/changelog	2017-01-23 14:39:14.0 +0200
+++ puppet-4.8.2/debian/changelog	2017-02-08 15:24:55.0 +0200
@@ -1,3 +1,18 @@
+puppet (4.8.2-2) unstable; urgency=high
+
+  * Do not enable the puppet service by default on fresh installs
+(Closes: #854487).
++ Preserve the agent lock on upgrade from 3.x to safeguard upgrades from
+  Jessie systems where puppet was installed but never used.
+  * Update the DEP-8 tests to check that the service is disabled.
+  * Strip the agent locking logic from puppet.preinst now that we disable the
+service by default.
+  * Add a debian/NEWS entry documenting the disabled service.
+  * Update the information in README.Debian and remove the (now obsolete)
+paragraph about stored configs.
+
+ -- Apollon Oikonomopoulos   Wed, 08 Feb 2017 15:24:55 +0200
+
 puppet (4.8.2-1) unstable; urgency=medium
 
   * New upstream bugfix release.
diff -Nru puppet-4.8.2/debian/NEWS puppet-4.8.2/debian/NEWS
--- puppet-4.8.2/debian/NEWS	2017-01-23 14:37:53.0 +0200
+++ puppet-4.8.2/debian/NEWS	2017-02-08 15:24:55.0 +0200
@@ -1,3 +1,21 @@
+puppet (4.8.2-2) unstable; urgency=high
+
+  As of 4.8.2-2, the puppet service is not enabled by default on new
+  installations and has to be manually enabled using
+
+  systemctl enable puppet.service
+  or
+  update-rc.d puppet enable
+
+  if desired. Note that upgrades from previous puppet versions are not
+  affected by this change and will preserve the service status.
+
+  Since some versions of the package shipped with the service enabled by
+  default, if you are upgrading please check and make sure that the service on
+  your system is properly enabled or disabled to match your preference.
+
+ -- Apollon Oikonomopoulos   Wed, 08 Feb 2017 17:43:52 +0200
+
 puppet (4.8.1-2) unstable; urgency=medium
 
   The Ruby Puppet master as shipped in Debian can currently handle Puppet 3.x
diff -Nru puppet-4.8.2/debian/puppet.postinst puppet-4.8.2/debian/puppet.postinst
--- puppet-4.8.2/debian/puppet.postinst	2017-01-23 14:37:53.0 +0200
+++ puppet-4.8.2/debian/puppet.postinst	2017-02-08 15:24:55.0 +0200
@@ -31,15 +31,24 @@
 	# Create folders common to "puppet" and "puppetmaster", which need
 	# to be owned by the "puppet" user
 	install --owner puppet --group puppet --directory \
-		/var/lib/puppet/state
+		/var/cache/puppet/state
 
-	# Between 4.4.1-2 and 4.8.1-3, puppet was called 'puppet-agent'
-	# Preserve the systemd and SysV service states
-	if [ -n "$2" ] && dpkg --compare-versions "$2" gt "4.4.1-2~" && \
+	if [ -z "$2" ]; then
+		# Disable the service by default on new installations
+		update-rc.d puppet defaults >/dev/null || true
+		update-rc.d puppet disable >/dev/null || true
+	elif [ -n "$2" ] && dpkg --compare-versions "$2" gt "4.4.2-1~" && \
 		dpkg --compare-versions "$2" lt "4.8.1-3~"; then
+		# Between 4.4.2-1 and 4.8.1-3, puppet was called 'puppet-agent'
+		# Preserve the systemd and SysV service states
 		if deb-systemd-helper debian-installed p

Bug#854651: marked as done (unblock: debootstrap/1.0.88)

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Fri, 10 Feb 2017 00:05:17 +0100
with message-id <20170209230515.ga26...@ugent.be>
and subject line Re: Bug#854651: unblock: debootstrap/1.0.88
has caused the Debian Bug report #854651,
regarding unblock: debootstrap/1.0.88
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.)


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

Hey folks,

Please unblock debootstrap 1.0.88

We have a tiny fix for #836525, which will allow debootstrap to deal
with arch-qualified dependencies. It'll be a major PITA if debootstrap
can't deal with these in stretch. 

KiBi already knows about this upload and is happy AFAIK. He and I have
both tested the patch.

diff -Nru debootstrap-1.0.87/debian/changelog 
debootstrap-1.0.88/debian/changelog
--- debootstrap-1.0.87/debian/changelog 2016-11-16 05:47:27.0 +
+++ debootstrap-1.0.88/debian/changelog 2017-02-08 23:52:56.0 +
@@ -1,3 +1,10 @@
+debootstrap (1.0.88) unstable; urgency=high
+
+  [ Sven Joachim ]
+  * Strip the arch-qualifier (Closes: #836525)
+
+ -- Steve McIntyre <93...@debian.org>  Wed, 08 Feb 2017 23:53:10 +
+
 debootstrap (1.0.87) unstable; urgency=high
 
   [ Julien Cristau ]
diff -Nru debootstrap-1.0.87/functions debootstrap-1.0.88/functions
--- debootstrap-1.0.87/functions2016-10-31 04:01:25.0 +
+++ debootstrap-1.0.88/functions2017-02-03 00:52:30.0 +
@@ -1336,6 +1336,7 @@
for $d (split /\s*,\s*/, $1) {
$d =~ s/\s*[|].*$//;
$d =~ s/\s*[(].*[)]\s*//;
+   $d =~ s/:.*//;
push @d, $d;
}
}

unblock debootstrap/1.0.88

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

On Thu, Feb 09, 2017 at 11:49:08AM +0100, Cyril Brulebois wrote:
> > Unblocked from my PoV.  For good measure, I'll just have KiBi confirm
> > that it is not going to disturb any test/release planning for d-i atm. :)
> 
> It would be nice if one could address #817236 at some point. Fixing
> other bugs is nice but…
> 
> Fine for the unblock anyway.

Added the unblock-udeb.

Cheers,

Ivo--- End Message ---

Bug#854685: marked as done (unblock: viewvc/1.1.26-1)

2017-02-09 Thread Debian Bug Tracking System 
Your message dated Fri, 10 Feb 2017 00:08:30 +0100
with message-id <20170209230828.ga26...@ugent.be>
and subject line Re: unblock: viewvc/1.1.26-1
has caused the Debian Bug report #854685,
regarding unblock: viewvc/1.1.26-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.)


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

the Security Team would like to request the unblocking of viewvc, which
fixes #854681 (CVE-2017-5938, XSS). DSA-3784-1 was just issued, fixing
this same issue in jessie-security.

The debdiff (below) is a tad larger than it ought to be, because:

  1. all copyright dates were updated to include "2017"
  2. the source wasn't repacked to omit Windows-specific code, like it
 was in 1.1.25+repack-1.

However, the only actual change is indeed the fix for CVE-2017-5938.

Here is the debdiff:


diff -Nru viewvc-1.1.25+repack/bin/asp/query.asp viewvc-1.1.26/bin/asp/query.asp
--- viewvc-1.1.25+repack/bin/asp/query.asp  2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/asp/query.asp 2017-01-25 00:07:15.0 +0100
@@ -3,7 +3,7 @@
 
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/asp/viewvc.asp 
viewvc-1.1.26/bin/asp/viewvc.asp
--- viewvc-1.1.25+repack/bin/asp/viewvc.asp 2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/asp/viewvc.asp2017-01-25 00:07:15.0 +0100
@@ -3,7 +3,7 @@
 
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cgi/query.cgi viewvc-1.1.26/bin/cgi/query.cgi
--- viewvc-1.1.25+repack/bin/cgi/query.cgi  2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/cgi/query.cgi 2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cgi/viewvc.cgi 
viewvc-1.1.26/bin/cgi/viewvc.cgi
--- viewvc-1.1.25+repack/bin/cgi/viewvc.cgi 2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/cgi/viewvc.cgi2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/cvsdbadmin viewvc-1.1.26/bin/cvsdbadmin
--- viewvc-1.1.25+repack/bin/cvsdbadmin 2016-09-15 21:38:32.0 +0200
+++ viewvc-1.1.26/bin/cvsdbadmin2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack/bin/loginfo-handler 
viewvc-1.1.26/bin/loginfo-handler
--- viewvc-1.1.25+repack/bin/loginfo-handler2016-09-15 21:38:32.0 
+0200
+++ viewvc-1.1.26/bin/loginfo-handler   2017-01-25 00:07:15.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/env python
 # -*-python-*-
 #
-# Copyright (C) 1999-2015 The ViewCVS Group. All Rights Reserved.
+# Copyright (C) 1999-2017 The ViewCVS Group. All Rights Reserved.
 #
 # By using this file, you agree to the terms and conditions set forth in
 # the LICENSE.html file which can be found at the top level of the ViewVC
diff -Nru viewvc-1.1.25+repack

Bug#853809: unblock: e2fsprogs/1.43.4-2

2017-02-09 Thread Cyril Brulebois 
Hi,

Theodore Ts'o  (2017-02-08):
> On Fri, Feb 03, 2017 at 10:34:09PM +0100, Emilio Pozuelo Monfort wrote:
> > 
> > This seems fine to me, unblocked. Cc'ing debian-boot@/Cyril for the
> > udeb unblock.
> 
> Hi, I've since found a regression that I would like to fix via a
> cherry pick from upstream.  The e2fsprogs/1.43.4-2 package hasn't
> transitioned into testing yet (it will in 3 more days).
> 
> Enclosed please find the source debdiff.  Would you prefer that I wait
> for 1.43.4-2 to transition into testing, and then upload 1.43.4-3 and
> then file a new unblock request?

Whatever release team members prefer I'll give -3 a try within d-i to
check there's no surprises with a casual installation, and I'll update
this bug report once I've done so.


KiBi.


signature.asc
Description: Digital signature

Bug#853809: unblock: e2fsprogs/1.43.4-2

2017-02-09 Thread Cyril Brulebois 
Hi again,

Cyril Brulebois  (2017-02-10):
> Whatever release team members prefer I'll give -3 a try within d-i to
> check there's no surprises with a casual installation, and I'll update
> this bug report once I've done so.

Tests within d-i with -3 look OK: creating an ext4 root partition on a
full disc is OK, creating both ext2 for /boot and ext4 for / with
encrypted LVM is also OK.

So no objections from me, thanks.


KiBi.


signature.asc
Description: Digital signature