Processed (with 1 error): Re: Bug#927183: [pre-approval] unblock: debiancontributors/0.7.8-1
Processing control commands: > tags -1 moreinfo cionfirmed Unknown tag/s: cionfirmed. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore. Bug #927183 [release.debian.org] [pre-approval] unblock: debiancontributors/0.7.8-1 Added tag(s) moreinfo. -- 927183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#927189: unblock: docker.io/18.09.1+dfsg1-5+b10
Processing control commands: > tags -1 moreinfo confirmed Bug #927189 [release.debian.org] unblock: docker.io/18.09.1+dfsg1-5+b10 Added tag(s) confirmed and moreinfo. -- 927189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927183: [pre-approval] unblock: debiancontributors/0.7.8-1
Control: tags -1 moreinfo cionfirmed Daniele Tricoli: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Hello! > > This is a pre-approval to unblock package debiancontributors 0.7.8-1 > > debiancontributors is a package used internally by our infra team and this > upload would fix some simple but important bugs, in particular: > > https://salsa.debian.org/python-team/modules/python-debiancontributors/commit/51adfafa4ee8cb58fc4d651ec99b6f46a83f02d5 > > https://salsa.debian.org/python-team/modules/python-debiancontributors/commit/b41908ea65e6a550438f90339c29ea2a3feda718 > > The first one (workaround for #801506) is the most important one: > python-requests can't support (for now) 100-Continue response. > > The debdiff against the package in testing is attached. Thanks for considering > this pre-approval. > > unblock debiancontributors/0.7.8-1 > > [...] > Please go ahead with the upload and remove the moreinfo tag when the upload is ready to be unblocked. For future reference: Please avoid generic code-style rewrite/refactoring during freezes (and instead deploy it after the freeze). In the particular instance, it was manageable to review but most of the was "noise" due to that refactoring - this in turn increases the risk that the proposal is rejected. Thanks, ~Niels
Bug#927189: unblock: docker.io/18.09.1+dfsg1-5+b10
Control: tags -1 moreinfo confirmed Arnaud Rebillout: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package docker.io. > > unblock docker.io/18.09.1+dfsg1-5+b10 > > I'd like to fix #925224 [1] for buster. The fix is trivial, and allows > the docker's debootstrap script to work again when it queries > security.debian.org, by following redirections. Please see bug for > more details. > > I attached a source debdiff as mentioned in buster freeze policy [2]. > > Sorry for the inconvenience, > > Thanks! > > Arnaud > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925224 > [2] https://release.debian.org/buster/freeze_policy.html. > > [...] > Please go ahead with the upload and remove the moreinfo tag when it is ready to be unblocked. Thanks, ~Niels
Bug#927192: marked as done (unblock: node-sshpk/1.13.1+dfsg-2)
Your message dated Tue, 16 Apr 2019 05:35:00 + with message-id and subject line Re: Bug#927192: unblock: node-sshpk/1.13.1+dfsg-2 has caused the Debian Bug report #927192, regarding unblock: node-sshpk/1.13.1+dfsg-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.) -- 927192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927192 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 node-sshpk Hello, I imported upstream patch fo fix #901093, CVE-2018-3737. Here is the full changes: * Enable nocheck build profile * Declare compliance with policy 4.3.0 * Add patch to fix ReDoS when parsing crafted invalid public keys (Closes: #901093, CVE-2018-3737) * Fix VCS fields * Fix debian/copyright format URL * Add descriptions in patches * Add upstream/metadata Reverse dependencies: - node-http-signature +-> node-request +-> node-jsdom +-> node-ytdl-core +-> node-coveralls +-> node-millstone +-> node-matrix-js-sdk +-> node-jsonld +-> node-gyp || |V +-> npm |+-> npm2deb +-> yarnpkg +-> gitlab Change on installed files is minimalistic: * 2 regexp improvements * a null substitution: - var data = m[2] + m[3]; + var data = m[2] + (m[3] ? m[3] : ''); So I think it is not risky to upgrade node-sshpk. Cheers, Xavier unblock node-sshpk/1.13.1+dfsg-2 diff --git a/debian/changelog b/debian/changelog index edaed62..0cb77bd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,21 @@ +node-sshpk (1.13.1+dfsg-2) unstable; urgency=medium + + * Team upload + + [ Pirate Praveen ] + * Enable nocheck build profile + + [ Xavier Guimard ] + * Declare compliance with policy 4.3.0 + * Add patch to fix ReDoS when parsing crafted invalid public keys +(Closes: #901093, CVE-2018-3737) + * Fix VCS fields + * Fix debian/copyright format URL + * Add descriptions in patches + * Add upstream/metadata + + -- Xavier Guimard Tue, 16 Apr 2019 06:57:20 +0200 + node-sshpk (1.13.1+dfsg-1) unstable; urgency=medium * Team upload diff --git a/debian/control b/debian/control index 76f60a3..e0eac6f 100644 --- a/debian/control +++ b/debian/control @@ -7,23 +7,23 @@ Build-Depends: debhelper (>= 9) , dh-buildinfo , nodejs - , node-tape - , node-temp - , openssl + , node-tape + , node-temp + , openssl , node-marked-man - , node-sinon - , node-dashdash (>= 1.12.0) - , node-assert-plus (>= 1.0.0) - , node-getpass (>= 0.1.1) - , node-asn1 (>= 0.2.3) - , node-jsbn (>= 0.1.0) - , node-ecc-jsbn (>= 0.1.1) - , node-tweetnacl (>= 0.14.0) - , node-bcrypt-pbkdf (>= 1.0.0) -Standards-Version: 4.1.2 + , node-sinon + , node-dashdash (>= 1.12.0) + , node-assert-plus (>= 1.0.0) + , node-getpass (>= 0.1.1) + , node-asn1 (>= 0.2.3) + , node-jsbn (>= 0.1.0) + , node-ecc-jsbn (>= 0.1.1) + , node-tweetnacl (>= 0.14.0) + , node-bcrypt-pbkdf (>= 1.0.0) +Standards-Version: 4.3.0 Homepage: https://github.com/arekinath/node-sshpk#readme -Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-sshpk.git -Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-sshpk.git +Vcs-Browser: https://salsa.debian.org/js-team/node-sshpk +Vcs-Git: https://salsa.debian.org/js-team/node-sshpk.git Package: node-sshpk Architecture: all diff --git a/debian/copyright b/debian/copyright index 72d1687..24e192f 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,4 +1,4 @@ -Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: sshpk Upstream-Contact: https://github.com/arekinath/node-sshpk/issues Source: https://github.com/arekinath/node-sshpk#readme @@ -32,4 +32,3 @@ License: Expat ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - diff --git a/debian/patches/CVE-2018-3737.diff b/debian/patches/CVE-2018-3737.diff new file mode 100644 index 000..640a8f3 --- /dev/null +++ b/debian/patches/CVE-2018-3737.diff @@ -0,0 +1,63 @@ +Description: Fix CVE-2018-3737 +Author: Xavier Guimard +Origin: https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957 +Bug: https://security-tracker.debian.org/tracker/CVE-2018-3737 +Forwarded: not-needed +Last-Update: 2019-04-16 + +--- a/lib/formats/ssh.js b/lib/formats/ssh.j
Bug#927192: unblock: node-sshpk/1.13.1+dfsg-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-sshpk
Hello,
I imported upstream patch fo fix #901093, CVE-2018-3737. Here is the
full changes:
* Enable nocheck build profile
* Declare compliance with policy 4.3.0
* Add patch to fix ReDoS when parsing crafted invalid public keys
(Closes: #901093, CVE-2018-3737)
* Fix VCS fields
* Fix debian/copyright format URL
* Add descriptions in patches
* Add upstream/metadata
Reverse dependencies:
- node-http-signature
+-> node-request
+-> node-jsdom
+-> node-ytdl-core
+-> node-coveralls
+-> node-millstone
+-> node-matrix-js-sdk
+-> node-jsonld
+-> node-gyp
||
|V
+-> npm
|+-> npm2deb
+-> yarnpkg
+-> gitlab
Change on installed files is minimalistic:
* 2 regexp improvements
* a null substitution:
- var data = m[2] + m[3];
+ var data = m[2] + (m[3] ? m[3] : '');
So I think it is not risky to upgrade node-sshpk.
Cheers,
Xavier
unblock node-sshpk/1.13.1+dfsg-2
diff --git a/debian/changelog b/debian/changelog
index edaed62..0cb77bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+node-sshpk (1.13.1+dfsg-2) unstable; urgency=medium
+
+ * Team upload
+
+ [ Pirate Praveen ]
+ * Enable nocheck build profile
+
+ [ Xavier Guimard ]
+ * Declare compliance with policy 4.3.0
+ * Add patch to fix ReDoS when parsing crafted invalid public keys
+(Closes: #901093, CVE-2018-3737)
+ * Fix VCS fields
+ * Fix debian/copyright format URL
+ * Add descriptions in patches
+ * Add upstream/metadata
+
+ -- Xavier Guimard Tue, 16 Apr 2019 06:57:20 +0200
+
node-sshpk (1.13.1+dfsg-1) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index 76f60a3..e0eac6f 100644
--- a/debian/control
+++ b/debian/control
@@ -7,23 +7,23 @@ Build-Depends:
debhelper (>= 9)
, dh-buildinfo
, nodejs
- , node-tape
- , node-temp
- , openssl
+ , node-tape
+ , node-temp
+ , openssl
, node-marked-man
- , node-sinon
- , node-dashdash (>= 1.12.0)
- , node-assert-plus (>= 1.0.0)
- , node-getpass (>= 0.1.1)
- , node-asn1 (>= 0.2.3)
- , node-jsbn (>= 0.1.0)
- , node-ecc-jsbn (>= 0.1.1)
- , node-tweetnacl (>= 0.14.0)
- , node-bcrypt-pbkdf (>= 1.0.0)
-Standards-Version: 4.1.2
+ , node-sinon
+ , node-dashdash (>= 1.12.0)
+ , node-assert-plus (>= 1.0.0)
+ , node-getpass (>= 0.1.1)
+ , node-asn1 (>= 0.2.3)
+ , node-jsbn (>= 0.1.0)
+ , node-ecc-jsbn (>= 0.1.1)
+ , node-tweetnacl (>= 0.14.0)
+ , node-bcrypt-pbkdf (>= 1.0.0)
+Standards-Version: 4.3.0
Homepage: https://github.com/arekinath/node-sshpk#readme
-Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-sshpk.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-sshpk.git
+Vcs-Browser: https://salsa.debian.org/js-team/node-sshpk
+Vcs-Git: https://salsa.debian.org/js-team/node-sshpk.git
Package: node-sshpk
Architecture: all
diff --git a/debian/copyright b/debian/copyright
index 72d1687..24e192f 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: sshpk
Upstream-Contact: https://github.com/arekinath/node-sshpk/issues
Source: https://github.com/arekinath/node-sshpk#readme
@@ -32,4 +32,3 @@ License: Expat
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
-
diff --git a/debian/patches/CVE-2018-3737.diff
b/debian/patches/CVE-2018-3737.diff
new file mode 100644
index 000..640a8f3
--- /dev/null
+++ b/debian/patches/CVE-2018-3737.diff
@@ -0,0 +1,63 @@
+Description: Fix CVE-2018-3737
+Author: Xavier Guimard
+Origin:
https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957
+Bug: https://security-tracker.debian.org/tracker/CVE-2018-3737
+Forwarded: not-needed
+Last-Update: 2019-04-16
+
+--- a/lib/formats/ssh.js
b/lib/formats/ssh.js
+@@ -14,9 +14,9 @@
+ var sshpriv = require('./ssh-private');
+
+ /*JSSTYLED*/
+-var SSHKEY_RE = /^([a-z0-9-]+)[ \t]+([a-zA-Z0-9+\/]+[=]*)([\n
\t]+([^\n]+))?$/;
++var SSHKEY_RE = /^([a-z0-9-]+)[ \t]+([a-zA-Z0-9+\/]+[=]*)([ \t]+([^
\t][^\n]*[\n]*)?)?$/;
+ /*JSSTYLED*/
+-var SSHKEY_RE2 = /^([a-z0-9-]+)[ \t]+([a-zA-Z0-9+\/ \t\n]+[=]*)(.*)$/;
++var SSHKEY_RE2 = /^([a-z0-9-]+)[ \t\n]+([a-zA-Z0-9+\/][a-zA-Z0-9+\/
\t\n=]*)([^a-zA-Z0-9+\/ \t\n=].*)?$/;
+
+ function read(buf, options) {
+ if (typeof (buf) !== 'string') {
+@@ -71,7 +71,7 @@
+* chars from the beginning up to this point in the the string.
+* Then offset in this and try to make up for missing = chars.
+*/
+- var data = m[2] + m[3];
++ var data = m[2] + (m[3] ? m
Bug#927191: stretch-pu: package python-django-casclient/1.2.0-2
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi. I would like to update python-django-casclient in the next stable
point release.
Per [1], the version currently in Stretch is not functional due to
middleware API changes in Django 1.10 and above. Unfortunately, this
breakage went unnoticed prior to the release of Stretch.
Also, since python-django-casclient requires Django in order to be
usable, I would like to add a dependency on Django, which is currently
missing. [2] [3]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926350
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896317
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896404
A source debdiff with the proposed changes has been attached.
Thanks.
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-django-casclient-1.2.0/debian/changelog
python-django-casclient-1.2.0/debian/changelog
--- python-django-casclient-1.2.0/debian/changelog 2016-08-05
09:41:53.0 -0400
+++ python-django-casclient-1.2.0/debian/changelog 2019-04-15
22:45:34.0 -0400
@@ -1,3 +1,17 @@
+python-django-casclient (1.2.0-2+deb9u1) stretch; urgency=medium
+
+ [ William Blough ]
+ * Team upload
+ * Apply django 1.10 middleware fix from upstream (Closes: #926350)
+
+ [ Adrian Bunk ]
+ * python-django-casclient: Add the missing dependency
+on python-django. (Closes: #896317)
+ * python3-django-casclient: Add the missing dependency
+on python3-django. (Closes: #896404)
+
+ -- William Blough Mon, 15 Apr 2019 22:45:34 -0400
+
python-django-casclient (1.2.0-2) unstable; urgency=medium
[ Joost van Baal-Ilić ]
diff -Nru python-django-casclient-1.2.0/debian/control
python-django-casclient-1.2.0/debian/control
--- python-django-casclient-1.2.0/debian/control2016-08-05
09:41:53.0 -0400
+++ python-django-casclient-1.2.0/debian/control2019-04-15
22:45:34.0 -0400
@@ -15,7 +15,7 @@
Package: python-django-casclient
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
+Depends: python-django, ${python:Depends}, ${misc:Depends}
Suggests: python-django-cas-doc
Description: CAS client library for Django, K-State's version (Python 2)
Django-cas is a Central Authentication Service (CAS) client library for
@@ -27,7 +27,7 @@
Package: python3-django-casclient
Architecture: all
-Depends: ${python3:Depends}, ${misc:Depends}
+Depends: python3-django, ${python3:Depends}, ${misc:Depends}
Suggests: python-django-cas-doc
Description: CAS client library for Django, K-State's version (Python 3)
Django-cas is a Central Authentication Service (CAS) client library for
diff -Nru
python-django-casclient-1.2.0/debian/patches/django_110_middleware_fix
python-django-casclient-1.2.0/debian/patches/django_110_middleware_fix
--- python-django-casclient-1.2.0/debian/patches/django_110_middleware_fix
1969-12-31 19:00:00.0 -0500
+++ python-django-casclient-1.2.0/debian/patches/django_110_middleware_fix
2019-04-15 22:45:34.0 -0400
@@ -0,0 +1,41 @@
+Description: Fix middleware to be compatible with Django 1.10
+Origin: upstream,
https://patch-diff.githubusercontent.com/raw/kstateome/django-cas/pull/64.diff
+Last-Update: 2019-04-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/cas/middleware.py
b/cas/middleware.py
+@@ -5,6 +5,15 @@ try:
+ except ImportError:
+ from urllib.parse import urlencode
+
++
++MIDDLEWARE_BASE = None
++
++try:
++from django.utils.deprecation import MiddlewareMixin
++MIDDLEWARE_BASE = MiddlewareMixin
++except ImportError:
++MIDDLEWARE_BASE = object
++
+ from django.conf import settings
+ from django.contrib.auth import REDIRECT_FIELD_NAME
+ from django.contrib.auth import logout as do_logout
+@@ -19,7 +28,7 @@ from cas.views import login as cas_login
+ __all__ = ['CASMiddleware']
+
+
+-class CASMiddleware(object):
++class CASMiddleware(MIDDLEWARE_BASE):
+ """
+ Middleware that allows CAS authentication on admin pages
+ """
+@@ -81,7 +90,7 @@ class CASMiddleware(object):
+ return None
+
+
+-class ProxyMiddleware(object):
++class ProxyMiddleware(MIDDLEWARE_BASE):
+
+ # Middleware used to "fake" the django app that it lives at the Proxy
Domain
+ def process_request(self, request):
diff -Nru python-django-casclient-1.2.0/debian/patches/series
python-django-casclient-1.2.0/debian/patches/series
--- python-django-casclient-1.2.0/debian/patches/series 1969-12-31
19:00:00.0 -0500
+++ python-d
Bug#927189: unblock: docker.io/18.09.1+dfsg1-5+b10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package docker.io. unblock docker.io/18.09.1+dfsg1-5+b10 I'd like to fix #925224 [1] for buster. The fix is trivial, and allows the docker's debootstrap script to work again when it queries security.debian.org, by following redirections. Please see bug for more details. I attached a source debdiff as mentioned in buster freeze policy [2]. Sorry for the inconvenience, Thanks! Arnaud [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925224 [2] https://release.debian.org/buster/freeze_policy.html. - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, 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 -BEGIN PGP SIGNATURE- iQJTBAEBCgA9FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAly1Sk0fHGFybmF1ZC5y ZWJpbGxvdXRAY29sbGFib3JhLmNvbQAKCRDnJeh5FGACFgnpD/4yuJiQwCsyo/RD MgK3YGW6cr2wGd3VcrRuoIp7B1sVGO+fJej/dqAZWI2/prRqQaLc878bjF4ipR88 54k4CuCucdvvEcfz+lwaTuecQwzMzWNAQDwq1qUq1ImvusC9Od2Z276BF3+rMy2Y 8KyeJ3w+gCH/tAHAhqfWMFmkFUHujdoBMkXBgqZEUF1IjjYhW8Qg2bGyOysdt1vJ MCTaIWg/R5ZJWFG8Ef/jbOkCwXJxEBugaAk72lIG5K0ShoYyfuL94l3CPnklwecP t+6rmaEkHo9g1/y8OWIfr6c2I0znPannNGpMgOVSgTW5ABJDVnWyyR9n9veUnhw6 mAdbivorf6/ZopH7zEYYWAG5q5/5c1L/UWr+buJgPwFgpH+OMN1/BF4IB8PzryA1 QJ7SVXxxon7Hw+YosPXisuY3Riw6uFe9dhT0du1nqC0celOPFaxsd6SRBhlv3G6I ldwLTV41jGC71YHR7Dhqg14Nq5aSSCpR8CsF5YpvQIfgxH1XNEvMDrdHoueQlh6A dU0h3sBQJJz/BuOD2BVoYt+cMaU5qtnq49ZIK9T0XQGWrsytm3/UEM5gHHehDnVL c60Ah23D9EnFuQji5RfAHSLFn4ZHO2aGhBe5xJH4T461My3r5uMZmROeANbTZIK8 rq2IJ7ujE6NAVnDAaTYzANYytcbGZg== =4P6K -END PGP SIGNATURE- diff -Nru docker.io-18.09.1+dfsg1/debian/changelog docker.io-18.09.1+dfsg1/debian/changelog --- docker.io-18.09.1+dfsg1/debian/changelog2019-02-02 06:00:35.0 +0700 +++ docker.io-18.09.1+dfsg1/debian/changelog2019-04-16 09:56:17.0 +0700 @@ -1,3 +1,9 @@ +docker.io (18.09.1+dfsg1-6) unstable; urgency=medium + + * Add patch to fix Debian security presence check (Closes: #925224). + + -- Arnaud Rebillout Tue, 16 Apr 2019 09:56:17 +0700 + docker.io (18.09.1+dfsg1-5) unstable; urgency=medium * Install "containerd-shim" as "docker-containerd-shim" (Closes: #920935). diff -Nru docker.io-18.09.1+dfsg1/debian/patches/engine-contrib-debootstrap-curl-follow-location.patch docker.io-18.09.1+dfsg1/debian/patches/engine-contrib-debootstrap-curl-follow-location.patch --- docker.io-18.09.1+dfsg1/debian/patches/engine-contrib-debootstrap-curl-follow-location.patch 1970-01-01 08:00:00.0 +0800 +++ docker.io-18.09.1+dfsg1/debian/patches/engine-contrib-debootstrap-curl-follow-location.patch 2019-04-16 09:56:17.0 +0700 @@ -0,0 +1,25 @@ +From: Mattias Jernberg +Date: Wed, 5 Dec 2018 19:35:17 +0100 +Subject: mkimage: Fix Debian security presence check + +Add Location following since security redirects to security-cdn and caused the repository to be added on Debian unstable. + +Signed-off-by: Mattias Jernberg +Origin: upstream, https://github.com/docker/engine/commit/8db5403 +--- + contrib/mkimage/debootstrap | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/engine/contrib/mkimage/debootstrap b/engine/contrib/mkimage/debootstrap +index 9f7d8987ad2a..a919429b0bde 100755 +--- a/engine/contrib/mkimage/debootstrap b/engine/contrib/mkimage/debootstrap +@@ -193,7 +193,7 @@ if [ -z "$DONT_TOUCH_SOURCES_LIST" ]; then + case "$lsbDist" in + debian) + # updates and security! +- if curl -o /dev/null -s --head --fail "http://security.debian.org/dists/$suite/updates/main/binary-$(rootfs_chroot dpkg --print-architecture)/Packages.gz"; then ++ if curl -o /dev/null -s --head --location --fail "http://security.debian.org/dists/$suite/updates/main/binary-$(rootfs_chroot dpkg --print-architecture)/Packages.gz"; then + ( + set -x + sed -i " diff -Nru docker.io-18.09.1+dfsg1/debian/patches/series docker.io-18.09.1+dfsg1/debian/patches/series --- docker.io-18.09.1+dfsg1/debian/patches/series 2019-01-27 17:02:58.0 +0700 +++ docker.io-18.09.1+dfsg1/debian/patches/series 2019-04-16 09:56:17.0 +0700 @@ -12,6 +12,7 @@ cli-fix-manpages-build-script.patch cli-fix-registry-debug-message-go-1.11.patch +engine-contrib-debootstrap-curl-follow-location.patch engine-test-noinstall.patch go-metrics_prometheus-fix_Observer.patch
Bug#927183: [pre-approval] unblock: debiancontributors/0.7.8-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello!
This is a pre-approval to unblock package debiancontributors 0.7.8-1
debiancontributors is a package used internally by our infra team and this
upload would fix some simple but important bugs, in particular:
https://salsa.debian.org/python-team/modules/python-debiancontributors/commit/51adfafa4ee8cb58fc4d651ec99b6f46a83f02d5
https://salsa.debian.org/python-team/modules/python-debiancontributors/commit/b41908ea65e6a550438f90339c29ea2a3feda718
The first one (workaround for #801506) is the most important one:
python-requests can't support (for now) 100-Continue response.
The debdiff against the package in testing is attached. Thanks for considering
this pre-approval.
unblock debiancontributors/0.7.8-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to
en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru debiancontributors-0.7.7/dc-tool debiancontributors-0.7.8/dc-tool
--- debiancontributors-0.7.7/dc-tool2018-02-14 15:33:56.0 +0100
+++ debiancontributors-0.7.8/dc-tool2019-04-16 01:24:06.0 +0200
@@ -26,6 +26,7 @@
import argparse
import logging
+
def read_json_sources(source_name, pathnames):
import debiancontributors as dc
# Read JSON data, parsing it to validate it
@@ -50,6 +51,7 @@
submission = dc.Submission.from_json(source_name, sys.stdin)
return submission
+
if __name__ == "__main__":
parser = argparse.ArgumentParser()
parser.add_argument("--debug", help="enable debugging output",
action="store_true")
@@ -95,8 +97,10 @@
sys.exit(1)
# Override auth_token and baseurl from commandline if requested
-if args.auth_token: submission.set_auth_token(args.auth_token)
-if args.baseurl: submission.baseurl = args.baseurl
+if args.auth_token:
+submission.set_auth_token(args.auth_token)
+if args.baseurl:
+submission.baseurl = args.baseurl
if args.post:
success, details = submission.post()
diff -Nru debiancontributors-0.7.7/debian/changelog
debiancontributors-0.7.8/debian/changelog
--- debiancontributors-0.7.7/debian/changelog 2018-02-14 14:27:21.0
+0100
+++ debiancontributors-0.7.8/debian/changelog 2019-04-16 02:27:01.0
+0200
@@ -1,3 +1,12 @@
+debiancontributors (0.7.8-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Update to use my debian.org mail address.
+ * debian/control
+- Bump Standards-Version to 4.3.0 (no changes needed).
+
+ -- Daniele Tricoli Tue, 16 Apr 2019 02:27:01 +0200
+
debiancontributors (0.7.7-1) unstable; urgency=medium
* Team upload.
diff -Nru debiancontributors-0.7.7/debian/control
debiancontributors-0.7.8/debian/control
--- debiancontributors-0.7.7/debian/control 2018-02-14 14:27:21.0
+0100
+++ debiancontributors-0.7.8/debian/control 2019-04-16 02:27:01.0
+0200
@@ -1,6 +1,6 @@
Source: debiancontributors
Maintainer: Debian Python Modules Team
-Uploaders: Enrico Zini , Daniele Tricoli
+Uploaders: Enrico Zini , Daniele Tricoli
Section: python
Priority: optional
Build-Depends: debhelper (>= 11),
@@ -14,7 +14,7 @@
python3-six,
python3-debian
Build-Depends-Indep: help2man
-Standards-Version: 4.1.3
+Standards-Version: 4.3.0
Homepage:
https://salsa.debian.org/python-team/modules/python-debiancontributors
Vcs-Git:
https://salsa.debian.org/python-team/modules/python-debiancontributors.git
Vcs-Browser:
https://salsa.debian.org/python-team/modules/python-debiancontributors
diff -Nru debiancontributors-0.7.7/debian/copyright
debiancontributors-0.7.8/debian/copyright
--- debiancontributors-0.7.7/debian/copyright 2018-02-14 14:27:21.0
+0100
+++ debiancontributors-0.7.8/debian/copyright 2019-04-16 02:27:01.0
+0200
@@ -9,7 +9,7 @@
Files: debian/*
Copyright: 2013, Enrico Zini
- 2016, Daniele Tricoli
+ 2016, Daniele Tricoli
License: LGPL-3+
License: LGPL-3+
diff -Nru debiancontributors-0.7.7/debian/rules
debiancontributors-0.7.8/debian/rules
--- debiancontributors-0.7.7/debian/rules 2018-02-14 14:27:21.0
+0100
+++ debiancontributors-0.7.8/debian/rules 2019-04-16 02:27:01.0
+0200
@@ -24,4 +24,3 @@
exit 1 ; \
fi
gbp buildpackage --git-debian-branch=backport -S -us -uc
-
diff -Nru debiancontributors-0.7.7/debiancontributors/parser.py
debiancontributors-0.7.8/debiancontributors/parser.py
--- debiancontributors-0.7.7/
Bug#925506: stretch-pu: package java-common/0.58+deb9u1
On Sun, Apr 14, 2019 at 09:20:13PM +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Mon, 2019-03-25 at 22:35 +0100, Moritz Muehlenhoff wrote: > > How about the following debdiff to address the fallout of > > the Xul deprecation in icedtea-web (#921748) for the next > > point update? > > > > default-jre is the only reverse dependency of > > default-java-plugin, so the patch also removes default-java-plugin > > along. > > I assume the upgrade path from systems with the packages already > installed has been tested without issue? I think so: I've upgraded my stretch desktop with java-common and the various default-foo packages from the previous version to the new release for about two weeks now, given that the only in-archive reverse dep of default-java-plugin was in java-common, I can't think of another upgrade path to test. Cheers, Moritz
Processed: tagging 925506
Processing commands for cont...@bugs.debian.org: > tags 925506 - moreinfo Bug #925506 [release.debian.org] stretch-pu: package java-common/0.58+deb9u1 Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 925506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924493: stretch-pu: package publicsuffix/20190221.0923-0+deb9u1
On Sat 2019-04-13 22:04:03 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Wed, 2019-03-13 at 11:12 -0400, Daniel Kahn Gillmor wrote: >> Please consider an update to publicsuffix in debian stretch. >> >> This package reflects the state of the network, and keeping it >> current >> is useful for all the packages that depend on it. >> > > Please go ahead. Thanks, uploaded. In the month since i made this initial request for update, more upstream updates have come in, so i've also just now filed #927160. If there's a way that you'd prefer i track these updates that's different from what i'm doing, please let me know. Thanks for your work maintaining stretch! --dkg signature.asc Description: PGP signature
Bug#926817: marked as done (unblock: publicsuffix/20190415.1030-1)
Your message dated Mon, 15 Apr 2019 21:58:53 +0200 with message-id <20190415195850.6b7otetcvay5l...@debian.org> and subject line Re: unblock: publicsuffix/20190329.0756-1 has caused the Debian Bug report #926817, regarding unblock: publicsuffix/20190415.1030-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.) -- 926817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926817 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 Control: affects -1 src:publicsuffix Please unblock package publicsuffix The publicsuffix package contains up-to-date descriptions of the network environment. In addition to capturing the most recent state of the DNS's public cutpoints, this update marks the correct level of debian policy compliance (4.3.0) and moves to debhelper compat level 12 (no changes to the generated tarball resulted from this shift in dh compat level). Buster should start off with an accurate state of the public network. The debdiff is attached. unblock publicsuffix/20190329.0756-1 Thanks for your work on Buster! --dkg diff --git publicsuffix-20190221.0923-1/debian/changelog publicsuffix-20190329.0756-1/debian/changelog index 818926d..6a336fc 100644 --- publicsuffix-20190221.0923-1/debian/changelog +++ publicsuffix-20190329.0756-1/debian/changelog @@ -1,3 +1,9 @@ +publicsuffix (20190329.0756-1) unstable; urgency=medium + + * new upstream version + + -- Daniel Kahn Gillmor Wed, 03 Apr 2019 22:49:31 -0400 + publicsuffix (20190221.0923-1) unstable; urgency=medium * new upstream version diff --git publicsuffix-20190221.0923-1/debian/compat publicsuffix-20190329.0756-1/debian/compat deleted file mode 100644 index b4de394..000 --- publicsuffix-20190221.0923-1/debian/compat +++ /dev/null @@ -1 +0,0 @@ -11 diff --git publicsuffix-20190221.0923-1/debian/control publicsuffix-20190329.0756-1/debian/control index 683edff..f9f9dbe 100644 --- publicsuffix-20190221.0923-1/debian/control +++ publicsuffix-20190329.0756-1/debian/control @@ -3,10 +3,10 @@ Section: net Priority: optional Maintainer: Daniel Kahn Gillmor Build-Depends: - debhelper (>= 11~), + debhelper-compat (= 12), psl-make-dafsa, python3-minimal, -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://publicsuffix.org Vcs-Browser: https://salsa.debian.org/debian/publicsuffix Vcs-Git: https://salsa.debian.org/debian/publicsuffix.git diff --git publicsuffix-20190221.0923-1/debian/upstream-changes.txt publicsuffix-20190329.0756-1/debian/upstream-changes.txt index f575c27..b85f949 100644 --- publicsuffix-20190221.0923-1/debian/upstream-changes.txt +++ publicsuffix-20190329.0756-1/debian/upstream-changes.txt @@ -1,3 +1,102 @@ +commit 826d762a078ae21cd8bb95fa8f38ae84bb3948e7 +Author: Rishabh +Date: Fri Mar 29 00:56:08 2019 -0700 + +Add discourse.group for Civilized Discourse Construction Kit, Inc. (#768) + +At Discourse (Civilized Discourse Construction Kit, Inc.), we host free +discussion forums for open source organizations under the `discourse.group` domain. +https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/ + +Therefore, each subdomain of discourse.group should be treated as a distinct domain. +Website: https://www.discourse.org/ + +As we host multiple forums under the discourse.group domain we'd like to add it to the PSL to: + +1. Ensure that each subdomain of discourse.group is treated as a distinct domain. +2. Adding cookie security. + +commit 1def5910a0c1db384691adf55f769de191b4f2b7 +Author: Vincent Fiduccia +Date: Fri Mar 29 00:53:18 2019 -0700 + +Add on-rancher.cloud and on-rio.io (#779) + +We are adding a feature to automatically provide each user cluster with a ..on-rancher.cloud (and on-rio.io) DNS entry, so each user-id is a mutually untrusting third-party that should not be able to set cookies readable by each other. We also plan to provide Let's Encrypt wildcard certs for each user-id. + +commit 2b92a7f2c9c91f1141faea73d3ec2d429da18698 +Author: Boris Rybalkin +Date: Fri Mar 29 07:49:12 2019 + + +Syncloud dynamic dns service (#727) + +Syncloud DDNS server (syncloud.it) hosts user's DNS records and also has its own site at syncloud.it. +So In practice allthesebelong todifferent people: +user1.syncloud.it +user2.syncloud.it +www.syncloud.it + +Also any incorrectly set cookie sharing across all three is not safe as different users can run anything under *
Bug#927161: marked as done (unblock: glx-alternatives/1.0.0)
Your message dated Mon, 15 Apr 2019 19:53:00 +
with message-id <7a0f2094-e07b-9bbf-9e5d-2662aef83...@thykier.net>
and subject line Re: Bug#927161: unblock: glx-alternatives/1.0.0
has caused the Debian Bug report #927161,
regarding unblock: glx-alternatives/1.0.0
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.)
--
927161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927161
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 glx-alternatives
The relevant change in this update is the addition of Breaks against
some packages from the obsolete 304xx legacy driver.
These ensure on some stretch->buster upgrade paths that the obsolete
packages get removed, where previously they were either causing partial
upgrades (keeping xserver-xorg-core/stretch) or provoking dpkg
trigger cycles.
unblock glx-alternatives/1.0.0
diff -Nru glx-alternatives-0.9.1/debian/changelog
glx-alternatives-1.0.0/debian/changelog
--- glx-alternatives-0.9.1/debian/changelog 2019-01-27 08:03:20.0
+0100
+++ glx-alternatives-1.0.0/debian/changelog 2019-04-14 09:11:12.0
+0200
@@ -1,3 +1,13 @@
+glx-alternatives (1.0.0) unstable; urgency=medium
+
+ * glx-alternative-nvidia: Add Breaks against nvidia-legacy-304xx-driver,
+xserver-xorg-video-nvidia-legacy-304xx, nvidia-legacy-304xx-alternative
+to ensure the obsolete legacy version from stretch gets removed during
+upgrades to buster.
+ * Drop versioned constraints that are satisfied in wheezy.
+
+ -- Andreas Beckmann Sun, 14 Apr 2019 09:11:12 +0200
+
glx-alternatives (0.9.1) unstable; urgency=medium
* Switch to debhelper-compat (= 12).
@@ -14,6 +24,19 @@
-- Andreas Beckmann Mon, 17 Dec 2018 23:30:30 +0100
+glx-alternatives (0.8.8~deb9u2) stretch; urgency=medium
+
+ * Revert dpkg-trigger changes from 0.8.8 as it may cause an exception thrown
+in apt. (Closes: #922210)
+
+ -- Andreas Beckmann Wed, 13 Feb 2019 12:49:52 +0100
+
+glx-alternatives (0.8.8~deb9u1) stretch; urgency=medium
+
+ * Rebuild for stretch.
+
+ -- Andreas Beckmann Mon, 04 Feb 2019 23:44:19 +0100
+
glx-alternatives (0.8.8) unstable; urgency=medium
* glx-diversions: Put all packages that had shared libraries diverted into
@@ -49,6 +72,13 @@
-- Andreas Beckmann Mon, 16 Jul 2018 16:26:25 +0200
+glx-alternatives (0.8.3~deb9u1) stretch; urgency=medium
+
+ * Rebuild for stretch.
+ * Revert to debhelper compat level 9.
+
+ -- Andreas Beckmann Fri, 04 May 2018 23:41:35 +0200
+
glx-alternatives (0.8.3) unstable; urgency=medium
* Divert libGL.so.1.7.0, libGLESv1_CM.so.1.2.0, libGLESv2.so.2.1.0,
diff -Nru glx-alternatives-0.9.1/debian/control
glx-alternatives-1.0.0/debian/control
--- glx-alternatives-0.9.1/debian/control 2019-01-27 08:03:20.0
+0100
+++ glx-alternatives-1.0.0/debian/control 2019-04-14 09:11:12.0
+0200
@@ -36,7 +36,6 @@
Pre-Depends:
nvidia-installer-cleanup,
Depends:
- dpkg (>= 1.15),
glx-alternative-mesa (= ${binary:Version}),
${misc:Depends}
Conflicts:
@@ -101,6 +100,10 @@
nvidia-alternative-legacy-71xx (<< 304),
# libGLX_indirect.so.0 alternative
nvidia-alternative (<< 390.67-3~),
+# ensure removal on upgrades from stretch
+ nvidia-legacy-304xx-driver (<< 304.137-7~),
+ xserver-xorg-video-nvidia-legacy-304xx (<< 304.137-7~),
+ nvidia-legacy-304xx-alternative (<< 304.137-7~),
Description: allows the selection of NVIDIA as GLX provider
In setups with several GLX providers (e.g. the free MESA implementation and
proprietary graphics hardware vendor implementations) this metapackage
--- End Message ---
--- Begin Message ---
Andreas Beckmann:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package glx-alternatives
>
> The relevant change in this update is the addition of Breaks against
> some packages from the obsolete 304xx legacy driver.
> These ensure on some stretch->buster upgrade paths that the obsolete
> packages get removed, where previously they were either causing partial
> upgrades (keeping xserver-xorg-core/stretch) or provoking dpkg
> trigger cycles.
>
> unblock glx-alternatives/1.0.0
>
Unblocked, thanks.
~Niels--- End Message ---
Bug#927157: marked as done (unblock: live-config/5.20190312)
Your message dated Mon, 15 Apr 2019 18:53:00 +
with message-id
and subject line Re: Bug#927157: unblock: live-config/5.20190312
has caused the Debian Bug report #927157,
regarding unblock: live-config/5.20190312
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.)
--
927157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927157
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 live-config
It contains some minor packaging updates but more importantly it
contains a fix that allows auto-login for lxqt on its live cd.
Without this unblock users will have to type 'user/live' on
the login screen when booting the lxqt live cd.
Full DebDiff:
"""
diff -Nru live-config-5.20180224/components/0085-sddm
live-config-5.20190312/components/0085-sddm
--- live-config-5.20180224/components/0085-sddm 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/components/0085-sddm 2019-03-11 12:15:09.0
+
@@ -62,10 +62,20 @@
# autologin
if [ -n "${LIVE_USERNAME}" ]
then
+ LIVE_X_SESSION_MANAGER=$(realpath /usr/bin/x-session-manager)
+ case "${LIVE_X_SESSION_MANAGER}" in
+ /usr/bin/startkde)
+ LIVE_SESSION="plasma.desktop"
+ ;;
+
+ /usr/bin/startlxqt)
+ LIVE_SESSION="lxqt.desktop"
+ ;;
+ esac
cat > /etc/sddm.conf << EOF
[Autologin]
User=${LIVE_USERNAME}
-Session=plasma.desktop
+Session=${LIVE_SESSION}
EOF
fi
diff -Nru live-config-5.20180224/debian/changelog
live-config-5.20190312/debian/changelog
--- live-config-5.20180224/debian/changelog 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/changelog 2019-03-11 12:15:09.0
+
@@ -1,3 +1,15 @@
+live-config (5.20190312) unstable; urgency=medium
+
+ * Update compat to debhelper-compat (= 12)
+- Use dh_missing instead of 'dh_install --fail-missing'
+- Rename no-restart-on-upgrade to no-stop-on-upgrade
+ * Upgrade standards version to 4.3.0
+ * Add self to uploaders
+ * Integrate patch to select desktop environments for SDDM
+(Closes: #921921)
+
+ -- Jonathan Carter Mon, 11 Mar 2019 12:15:09 +
+
live-config (5.20180224) unstable; urgency=medium
[ Steve McIntyre ]
diff -Nru live-config-5.20180224/debian/compat
live-config-5.20190312/debian/compat
--- live-config-5.20180224/debian/compat2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/compat1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-11
diff -Nru live-config-5.20180224/debian/control
live-config-5.20190312/debian/control
--- live-config-5.20180224/debian/control 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/control 2019-03-11 12:15:09.0
+
@@ -1,11 +1,13 @@
Source: live-config
Maintainer: Live Systems Maintainers
-Uploaders: Iain R. Learmonth , Raphaël Hertzog
+Uploaders: Iain R. Learmonth ,
+ Raphaël Hertzog ,
+ Jonathan Carter
Section: misc
Priority: optional
-Build-Depends: debhelper (>= 11)
+Build-Depends: debhelper-compat (= 12)
Build-Depends-Indep: lsb-release
-Standards-Version: 4.1.3
+Standards-Version: 4.3.0
Vcs-Browser: https://salsa.debian.org/live-team/live-config
Vcs-Git: https://salsa.debian.org/live-team/live-config.git
Homepage: https://debian-live.alioth.debian.org/live-config/
@@ -35,6 +37,7 @@
Package: live-config-doc
Architecture: all
+Multi-Arch: foreign
Section: doc
Depends: ${misc:Depends}
Description: Live System Configuration Components (documentation)
diff -Nru live-config-5.20180224/debian/rules
live-config-5.20190312/debian/rules
--- live-config-5.20180224/debian/rules 2018-02-24 10:54:36.0 +
+++ live-config-5.20190312/debian/rules 2019-03-11 12:15:09.0 +
@@ -1,7 +1,12 @@
#!/usr/bin/make -f
+# Don't build live-config-sysvinit on Ubuntu since Ubuntu doesn't offer
sysvinit
+ifeq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
+SUPPORT_SYSVINIT := -Nlive-config-sysvinit
+endif
+
%:
- dh $@
+ dh $@ $(SUPPORT_SYSVINIT)
override_dh_auto_install:
dh_auto_install -- DESTDIR=debian/tmp
@@ -21,8 +26,8 @@
override_dh_compress:
dh_compress -Xusr/share/doc/live-config/examples
-override_dh_install:
- dh_install --fai
Bug#927161: unblock: glx-alternatives/1.0.0
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package glx-alternatives
The relevant change in this update is the addition of Breaks against
some packages from the obsolete 304xx legacy driver.
These ensure on some stretch->buster upgrade paths that the obsolete
packages get removed, where previously they were either causing partial
upgrades (keeping xserver-xorg-core/stretch) or provoking dpkg
trigger cycles.
unblock glx-alternatives/1.0.0
diff -Nru glx-alternatives-0.9.1/debian/changelog
glx-alternatives-1.0.0/debian/changelog
--- glx-alternatives-0.9.1/debian/changelog 2019-01-27 08:03:20.0
+0100
+++ glx-alternatives-1.0.0/debian/changelog 2019-04-14 09:11:12.0
+0200
@@ -1,3 +1,13 @@
+glx-alternatives (1.0.0) unstable; urgency=medium
+
+ * glx-alternative-nvidia: Add Breaks against nvidia-legacy-304xx-driver,
+xserver-xorg-video-nvidia-legacy-304xx, nvidia-legacy-304xx-alternative
+to ensure the obsolete legacy version from stretch gets removed during
+upgrades to buster.
+ * Drop versioned constraints that are satisfied in wheezy.
+
+ -- Andreas Beckmann Sun, 14 Apr 2019 09:11:12 +0200
+
glx-alternatives (0.9.1) unstable; urgency=medium
* Switch to debhelper-compat (= 12).
@@ -14,6 +24,19 @@
-- Andreas Beckmann Mon, 17 Dec 2018 23:30:30 +0100
+glx-alternatives (0.8.8~deb9u2) stretch; urgency=medium
+
+ * Revert dpkg-trigger changes from 0.8.8 as it may cause an exception thrown
+in apt. (Closes: #922210)
+
+ -- Andreas Beckmann Wed, 13 Feb 2019 12:49:52 +0100
+
+glx-alternatives (0.8.8~deb9u1) stretch; urgency=medium
+
+ * Rebuild for stretch.
+
+ -- Andreas Beckmann Mon, 04 Feb 2019 23:44:19 +0100
+
glx-alternatives (0.8.8) unstable; urgency=medium
* glx-diversions: Put all packages that had shared libraries diverted into
@@ -49,6 +72,13 @@
-- Andreas Beckmann Mon, 16 Jul 2018 16:26:25 +0200
+glx-alternatives (0.8.3~deb9u1) stretch; urgency=medium
+
+ * Rebuild for stretch.
+ * Revert to debhelper compat level 9.
+
+ -- Andreas Beckmann Fri, 04 May 2018 23:41:35 +0200
+
glx-alternatives (0.8.3) unstable; urgency=medium
* Divert libGL.so.1.7.0, libGLESv1_CM.so.1.2.0, libGLESv2.so.2.1.0,
diff -Nru glx-alternatives-0.9.1/debian/control
glx-alternatives-1.0.0/debian/control
--- glx-alternatives-0.9.1/debian/control 2019-01-27 08:03:20.0
+0100
+++ glx-alternatives-1.0.0/debian/control 2019-04-14 09:11:12.0
+0200
@@ -36,7 +36,6 @@
Pre-Depends:
nvidia-installer-cleanup,
Depends:
- dpkg (>= 1.15),
glx-alternative-mesa (= ${binary:Version}),
${misc:Depends}
Conflicts:
@@ -101,6 +100,10 @@
nvidia-alternative-legacy-71xx (<< 304),
# libGLX_indirect.so.0 alternative
nvidia-alternative (<< 390.67-3~),
+# ensure removal on upgrades from stretch
+ nvidia-legacy-304xx-driver (<< 304.137-7~),
+ xserver-xorg-video-nvidia-legacy-304xx (<< 304.137-7~),
+ nvidia-legacy-304xx-alternative (<< 304.137-7~),
Description: allows the selection of NVIDIA as GLX provider
In setups with several GLX providers (e.g. the free MESA implementation and
proprietary graphics hardware vendor implementations) this metapackage
NEW changes in stable-new
Processing changes file: libreoffice_5.2.7-1+deb9u6_mips64el.changes ACCEPT Processing changes file: linux_4.9.168-1_mipsel.changes ACCEPT
Bug#927160: stretch-pu: package publicsuffix/20190415.1030-0+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Control: affects -1 src:publicsuffix Please consider an update to publicsuffix in debian stretch. This package reflects the state of the network, and keeping it current is useful for all the packages that depend on it. The debdiff from the previous version in stretch is attached. This proposed release is also available at the "publicsuffix_debian/20190415.1030-0+deb9u1" tag on the "debian/stretch" branch at the git repo for publicsuffix packaging: https://salsa.debian.org/debian/publicsuffix Please followup on this ticket to confirm whether I should upload this revision to stretch. ../publicsuffix_20190221.0923-0+deb9u1_20190415.1030-0+deb9u1.debdiff.gz Description: Binary data
Bug#926817: unblock: publicsuffix/20190329.0756-1
Control: tags 926817 - moreinfo Control: retitle 926817 unblock: publicsuffix/20190415.1030-1 unblock publicsuffix/20190415.1030-1 On Sun 2019-04-14 12:35:44 +0200, Ivo De Decker wrote: > We don't accept debhelper compat changes during the freeze. Please do an > upload reverting that change and update this request after that. There are no differences between the binary package output for debhelper 11 and debhelper 12, but ok, i've reverted that change. I've gone ahead and updated to the latest upstream data as well. The updated debdiff is attached. Thanks for your work on the release! --dkg diff --git publicsuffix-20190221.0923-1/debian/changelog publicsuffix-20190415.1030-1/debian/changelog index 818926d..80eae84 100644 --- publicsuffix-20190221.0923-1/debian/changelog +++ publicsuffix-20190415.1030-1/debian/changelog @@ -1,3 +1,15 @@ +publicsuffix (20190415.1030-1) unstable; urgency=medium + + * new upstream version + + -- Daniel Kahn Gillmor Mon, 15 Apr 2019 13:47:04 -0400 + +publicsuffix (20190329.0756-1) unstable; urgency=medium + + * new upstream version + + -- Daniel Kahn Gillmor Wed, 03 Apr 2019 22:49:31 -0400 + publicsuffix (20190221.0923-1) unstable; urgency=medium * new upstream version diff --git publicsuffix-20190221.0923-1/debian/control publicsuffix-20190415.1030-1/debian/control index 683edff..e50f1e4 100644 --- publicsuffix-20190221.0923-1/debian/control +++ publicsuffix-20190415.1030-1/debian/control @@ -6,7 +6,7 @@ Build-Depends: debhelper (>= 11~), psl-make-dafsa, python3-minimal, -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://publicsuffix.org Vcs-Browser: https://salsa.debian.org/debian/publicsuffix Vcs-Git: https://salsa.debian.org/debian/publicsuffix.git diff --git publicsuffix-20190221.0923-1/debian/upstream-changes.txt publicsuffix-20190415.1030-1/debian/upstream-changes.txt index f575c27..027116e 100644 --- publicsuffix-20190221.0923-1/debian/upstream-changes.txt +++ publicsuffix-20190415.1030-1/debian/upstream-changes.txt @@ -1,3 +1,143 @@ +commit 033221af7f600bcfce38dcbfafe03b9a2269c4cc +Author: İlhan Subaşı +Date: Mon Apr 15 13:30:45 2019 +0300 + +Update .TR (#741) + +- Add tsk.tr +- Sort entries + +commit 9375b697baddb0827a5995c81bd3c75877a0b35d +Author: Paulus Schoutsen +Date: Mon Apr 15 03:15:13 2019 -0700 + +Add Nabu Casa (#781) + +Nabu Casa offers Home Assistant Cloud, a cloud extension for the open source home automation platform Home Assistant. With Home Assistant Cloud, local running Home Assistant instances can be accessed via the internet and integrate with cloud-only services like Alexa and Google Assistant. + +To allow remote connection to Home Assistant instances, we're soon giving users the option to access their local running instance under the domain https://.ui.nabu.casa. These domains will be served by their local Home Assistant instances, not under our control. Home Assistant allows users to built extensions in both Python and JavaScript, which will allow the user to run any code under their domain. For security, cookies should not be allowed to be shared across subdomains. + +commit 93e545f2989a4541eb1cfdf9ed9ed9bb9e2e4ab4 +Author: Paul Cammish <30495014+pcamm...@users.noreply.github.com> +Date: Mon Apr 15 11:12:33 2019 +0100 + +Added uk0.bigv.io under Bytemark Hosting (#745) + +uk0.bigv.io is used as a domain name for our self-service customers, and therefore hosts various customer virtual machines under the same 'public' domain name. These domains are often used for administrative control panels, and other interfaces, so cookie security at this level would be very useful. + +Note: This had to be excluded from #620 due to technical issues preventing the DNS verification at the time, but that issue has now been resolved. + +commit b1bb1c841157eada1e88840e3d813e6fb8e8b81a +Author: Tom Whitwell +Date: Mon Apr 15 11:05:52 2019 +0100 + +Add GOV.UK PaaS client domains (#765) + +GOV.UK Platform as a Service is the UK Government's PaaS - these are the domains we use for client applications, ie. appname.cloudapps.digital / appname.london.cloudapps.digital. + +We need these domains to be in the public suffix list as each subdomain is specific to one client application: cookie isolation is required. + +Additionally, one of our subdomains has been flagged as phishing, which has resulted in the whole london.cloudapps.digital being flagged as dangerous. We would like an explicit distinction between independent subdomains. + +commit 826d762a078ae21cd8bb95fa8f38ae84bb3948e7 +Author: Rishabh +Date: Fri Mar 29 00:56:08 2019 -0700 + +Add discourse.group for Civilized Discourse Construction Kit, Inc. (#768) + +At Discourse (Civilized Discourse Construction Kit, Inc.), we host free +discussion forums for open source organizations under the `discourse.group` domain. +https://blog.discourse.org/2018/11/free-ho
Processed: Re: unblock: publicsuffix/20190329.0756-1
Processing control commands: > tags 926817 - moreinfo Bug #926817 [release.debian.org] unblock: publicsuffix/20190329.0756-1 Removed tag(s) moreinfo. > retitle 926817 unblock: publicsuffix/20190415.1030-1 Bug #926817 [release.debian.org] unblock: publicsuffix/20190329.0756-1 Changed Bug title to 'unblock: publicsuffix/20190415.1030-1' from 'unblock: publicsuffix/20190329.0756-1'. -- 926817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: stretch-pu: package publicsuffix/20190415.1030-0+deb9u1
Processing control commands: > affects -1 src:publicsuffix Bug #927160 [release.debian.org] stretch-pu: package publicsuffix/20190415.1030-0+deb9u1 Added indication that 927160 affects src:publicsuffix -- 927160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927157: unblock: live-config/5.20190312
Uploaded live-config/5.20190312, which downgrades debhelper (/compat) back to 11 at the request of release team.
Bug#927141: marked as done (unblock: calamares-settings-debian/10.0.19-1)
Your message dated Mon, 15 Apr 2019 17:19:00 + with message-id <6e10f4fa-7549-b034-d287-0dfa105fc...@thykier.net> and subject line Re: Bug#927141: unblock: calamares-settings-debian/10.0.19-1 has caused the Debian Bug report #927141, regarding unblock: calamares-settings-debian/10.0.19-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.) -- 927141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927141 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 calamares-settings-debian This upload fixes the following important issues: * Fix Debian name (too long to fit into label size) * Fix Debian release notes URL (still refered to stretch) * Fix stale EFI file (BTS #927102) Full DebDiff: """ diff -Nru calamares-settings-debian-10.0.18/calamares/branding/debian/branding.desc calamares-settings-debian-10.0.19/calamares/branding/debian/branding.desc --- calamares-settings-debian-10.0.18/calamares/branding/debian/branding.desc 2019-02-15 14:03:55.0 + +++ calamares-settings-debian-10.0.19/calamares/branding/debian/branding.desc 2019-04-15 12:59:42.0 + @@ -7,12 +7,12 @@ shortProductName:Debian version: 10 (buster) shortVersion:10 -versionedName: Debian GNU/Linux 10 (buster) +versionedName: Debian 10 (buster) shortVersionedName: Debian 10 bootloaderEntryName: Debian productUrl: https://debian.org supportUrl: https://www.debian.org/support -releaseNotesUrl: https://www.debian.org/releases/stretch/releasenotes +releaseNotesUrl: https://www.debian.org/releases/buster/releasenotes images: productLogo: "debian-logo.png" diff -Nru calamares-settings-debian-10.0.18/calamares/modules/bootloader.conf calamares-settings-debian-10.0.19/calamares/modules/bootloader.conf --- calamares-settings-debian-10.0.18/calamares/modules/bootloader.conf 2019-02-15 14:03:55.0 + +++ calamares-settings-debian-10.0.19/calamares/modules/bootloader.conf 2019-04-15 12:59:42.0 + @@ -51,4 +51,4 @@ # seems to be the only one). If you set this to false, take care # to add another module to optionally install the fallback on those # boards that need it. -installEFIFallback: true +installEFIFallback: false diff -Nru calamares-settings-debian-10.0.18/debian/changelog calamares-settings-debian-10.0.19/debian/changelog --- calamares-settings-debian-10.0.18/debian/changelog 2019-02-15 14:06:39.0 + +++ calamares-settings-debian-10.0.19/debian/changelog 2019-04-15 13:32:36.0 + @@ -1,3 +1,12 @@ +calamares-settings-debian (10.0.19-1) unstable; urgency=medium + + * New upstream release +- Don't install unnecessary efi file (Closes: #927102) +- Fix distribution description +- Fix release notes URL + + -- Jonathan Carter Mon, 15 Apr 2019 13:32:36 + + calamares-settings-debian (10.0.18-1) unstable; urgency=medium * New upstream releas """ thanks, -Jonathan --- End Message --- --- Begin Message --- Jonathan Carter: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package calamares-settings-debian > > This upload fixes the following important issues: > > * Fix Debian name (too long to fit into label size) > * Fix Debian release notes URL (still refered to stretch) > * Fix stale EFI file (BTS #927102) > > Full DebDiff: > > [...] > > thanks, > > -Jonathan > Unblocked, thanks. ~Niels--- End Message ---
Processed: Re: Bug#926199: stretch-pu: package libreoffice/1:5.2.7-1+deb9u6
Processing commands for cont...@bugs.debian.org: > tag 926199 - moreinfo Bug #926199 [release.debian.org] stretch-pu: package libreoffice/1:5.2.7-1+deb9u7 Removed tag(s) moreinfo. > 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
tag 926199 - moreinfo thanks Hi Adam, On Sun, Apr 14, 2019 at 09:23:10PM +0100, Adam D. Barratt wrote: > On Mon, 2019-04-01 at 21:43 +0200, Rene Engelhard wrote: > > 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). > > How much has the upgrade path from current stable been tested? e.g. Good point... > what happens if APT decides to upgrade LO before openjdk-8 and for some > reason the system does not have the security.d.o package installed? *Shrugs*, people should install security updates... Anyways: Seems to just work. Plain stable + apt-get install libreoffice libreoffice-report-builder (which pulled in default-jre) and then adding proposed-updates and the new packages (deb9u7) and apt upgrade. See attached log. Regards, Rene WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages have been kept back: icedtea-netx The following packages will be upgraded: ca-certificates-java fonts-opensymbol icedtea-netx-common libopenjp2-7 libpq5 libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base libreoffice-base-core libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress libreoffice-java-common libreoffice-librelogo libreoffice-math libreoffice-nlpsolver libreoffice-ogltrans libreoffice-pdfimport libreoffice-report-builder libreoffice-report-builder-bin libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-script-provider-python libreoffice-sdbc-hsqldb libreoffice-sdbc-postgresql libreoffice-style-galaxy libreoffice-wiki-publisher libreoffice-writer libssh2-1 libssl1.0.2 libsystemd0 libudev1 openjdk-8-jre openjdk-8-jre-headless python3-uno systemd systemd-sysv tzdata udev uno-libs3 ure wget 45 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 35.6 MB/119 MB of archives. After this operation, 6623 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-base-drivers 1:5.2.7-1+deb9u7 [509 kB] Get:2 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-base 1:5.2.7-1+deb9u7 [1493 kB] Get:3 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-calc 1:5.2.7-1+deb9u7 [6454 kB] Get:4 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-impress 1:5.2.7-1+deb9u7 [918 kB] Get:5 http://ftp.de.debian.org/debian proposed-updates/main amd64 libsystemd0 amd64 232-25+deb9u11 [281 kB] Get:6 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-draw 1:5.2.7-1+deb9u7 [2427 kB] Get:7 http://ftp.de.debian.org/debian proposed-updates/main amd64 systemd amd64 232-25+deb9u11 [2471 kB] Get:8 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-writer 1:5.2.7-1+deb9u7 [7595 kB] Get:9 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ uno-libs3 5.2.7-1+deb9u7 [858 kB] Get:10 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-ogltrans 1:5.2.7-1+deb9u7 [71.6 kB] Get:11 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ ure 5.2.7-1+deb9u7 [1689 kB] Get:12 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ python3-uno 1:5.2.7-1+deb9u7 [178 kB] Get:13 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-sdbc-hsqldb 1:5.2.7-1+deb9u7 [109 kB] Get:14 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-style-galaxy 1:5.2.7-1+deb9u7 [1844 kB] Get:15 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-script-provider-js 1:5.2.7-1+deb9u7 [615 kB] Get:16 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-script-provider-bsh 1:5.2.7-1+deb9u7 [32.9 kB] Get:17 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-report-builder 1:5.2.7-1+deb9u7 [306 kB] Get:18 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-pdfimport 1:5.2.7-1+deb9u7 [185 kB] Get:19 file:/home/rene/Debian/Pakete/LibreOffice/libreoffice/tmp ./ libreoffice-java-common 1:5.2.7-1+deb9u7 [1933 kB] Get:20 http://ftp.de.debian.org/debian proposed-updates/main amd64 udev amd64 232-25+deb9u11 [1115 kB] Get:21 http://ftp.de.debian.org/debian proposed-updates/main amd64 libudev1 amd64 232-25+deb9u11 [126 kB] Get:22 http://ftp.de.debian.org/debian proposed-updates/main amd64 systemd-sysv amd64 232-25+deb9u11 [82.4 kB] Get:23 http://ftp.de.debian.org/debian proposed-updates/main amd64 openjdk-8-jre
Bug#927156: unblock: parted/3.2-25
Control: tags -1 confirmed d-i Colin Watson: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock parted 3.2-25: there was an arithmetic error in its > handling of extended partitions, which was often in practice masked by > higher-level tools but could be triggered in some circumstances such as > by gnome-disks, leading to disturbing results like apparently-vanishing > partitions. The patch is pretty clear if you look at a little more > context: one branch of an if/else block multiplied by the device's > sector size while the other didn't, which was obviously wrong. > > [...] > > unblock parted/3.2-25 > Approved from a RT PoV; CC'ing KiBi for a d-i review. Thanks, ~Niels
Processed: Re: Bug#927156: unblock: parted/3.2-25
Processing control commands: > tags -1 confirmed d-i Bug #927156 [release.debian.org] unblock: parted/3.2-25 Added tag(s) d-i and confirmed. -- 927156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927157: unblock: live-config/5.20190312
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-config
It contains some minor packaging updates but more importantly it
contains a fix that allows auto-login for lxqt on its live cd.
Without this unblock users will have to type 'user/live' on
the login screen when booting the lxqt live cd.
Full DebDiff:
"""
diff -Nru live-config-5.20180224/components/0085-sddm
live-config-5.20190312/components/0085-sddm
--- live-config-5.20180224/components/0085-sddm 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/components/0085-sddm 2019-03-11 12:15:09.0
+
@@ -62,10 +62,20 @@
# autologin
if [ -n "${LIVE_USERNAME}" ]
then
+ LIVE_X_SESSION_MANAGER=$(realpath /usr/bin/x-session-manager)
+ case "${LIVE_X_SESSION_MANAGER}" in
+ /usr/bin/startkde)
+ LIVE_SESSION="plasma.desktop"
+ ;;
+
+ /usr/bin/startlxqt)
+ LIVE_SESSION="lxqt.desktop"
+ ;;
+ esac
cat > /etc/sddm.conf << EOF
[Autologin]
User=${LIVE_USERNAME}
-Session=plasma.desktop
+Session=${LIVE_SESSION}
EOF
fi
diff -Nru live-config-5.20180224/debian/changelog
live-config-5.20190312/debian/changelog
--- live-config-5.20180224/debian/changelog 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/changelog 2019-03-11 12:15:09.0
+
@@ -1,3 +1,15 @@
+live-config (5.20190312) unstable; urgency=medium
+
+ * Update compat to debhelper-compat (= 12)
+- Use dh_missing instead of 'dh_install --fail-missing'
+- Rename no-restart-on-upgrade to no-stop-on-upgrade
+ * Upgrade standards version to 4.3.0
+ * Add self to uploaders
+ * Integrate patch to select desktop environments for SDDM
+(Closes: #921921)
+
+ -- Jonathan Carter Mon, 11 Mar 2019 12:15:09 +
+
live-config (5.20180224) unstable; urgency=medium
[ Steve McIntyre ]
diff -Nru live-config-5.20180224/debian/compat
live-config-5.20190312/debian/compat
--- live-config-5.20180224/debian/compat2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/compat1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-11
diff -Nru live-config-5.20180224/debian/control
live-config-5.20190312/debian/control
--- live-config-5.20180224/debian/control 2018-02-24 10:54:36.0
+
+++ live-config-5.20190312/debian/control 2019-03-11 12:15:09.0
+
@@ -1,11 +1,13 @@
Source: live-config
Maintainer: Live Systems Maintainers
-Uploaders: Iain R. Learmonth , Raphaël Hertzog
+Uploaders: Iain R. Learmonth ,
+ Raphaël Hertzog ,
+ Jonathan Carter
Section: misc
Priority: optional
-Build-Depends: debhelper (>= 11)
+Build-Depends: debhelper-compat (= 12)
Build-Depends-Indep: lsb-release
-Standards-Version: 4.1.3
+Standards-Version: 4.3.0
Vcs-Browser: https://salsa.debian.org/live-team/live-config
Vcs-Git: https://salsa.debian.org/live-team/live-config.git
Homepage: https://debian-live.alioth.debian.org/live-config/
@@ -35,6 +37,7 @@
Package: live-config-doc
Architecture: all
+Multi-Arch: foreign
Section: doc
Depends: ${misc:Depends}
Description: Live System Configuration Components (documentation)
diff -Nru live-config-5.20180224/debian/rules
live-config-5.20190312/debian/rules
--- live-config-5.20180224/debian/rules 2018-02-24 10:54:36.0 +
+++ live-config-5.20190312/debian/rules 2019-03-11 12:15:09.0 +
@@ -1,7 +1,12 @@
#!/usr/bin/make -f
+# Don't build live-config-sysvinit on Ubuntu since Ubuntu doesn't offer
sysvinit
+ifeq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
+SUPPORT_SYSVINIT := -Nlive-config-sysvinit
+endif
+
%:
- dh $@
+ dh $@ $(SUPPORT_SYSVINIT)
override_dh_auto_install:
dh_auto_install -- DESTDIR=debian/tmp
@@ -21,8 +26,8 @@
override_dh_compress:
dh_compress -Xusr/share/doc/live-config/examples
-override_dh_install:
- dh_install --fail-missing
+override_dh_missing:
+ dh_missing --fail-missing
override_dh_installinit:
- dh_installinit -p live-config-sysvinit --no-restart-on-upgrade
--no-start --update-rcd-params='start 00 S .' --name live-config --onlyscripts
+ dh_installinit -p live-config-sysvinit --no-stop-on-upgrade --no-start
--update-rcd-params='start 00 S .' --name live-config --onlyscripts
"""
thanks,
-Jonathan
Processed: Re: unblock: node-formidable/1.2.1-2
Processing control commands: > tags -1 - moreinfo Bug #924627 [release.debian.org] unblock: node-formidable/1.2.1-2 Bug #924649 [release.debian.org] unblock: node-formidable/1.2.1-2 Removed tag(s) moreinfo. Removed tag(s) moreinfo. -- 924627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924627 924649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924627: unblock: node-formidable/1.2.1-2
Control: tags -1 - moreinfo
> Please unblock package node-formidable
> > [...]
> > node-formidable hasn't been updated for years. Testing version isn't
> > compatible with our nodejs but this was not seen since there was no
> > real tests (see https://bugs.debian.org/924589).
> >
> > I upgraded it and added full tests (build and autopkgtest).
> >
> > node-formidable reverse dependencies:
> > - node-superagent:
> >+- node-supertest (no reverse dependencies)
> >
> > node-formidable bug does not affect these packages since the failing
> > functions are not used in it, that's why I decrease bug severity to
> > important. I tested the 2 reverse dependencies with both old and new
> > node-formidable with success (sbuild and autopkgtest).
> >
> > debdiff is big since I embedded some node modules (only for tests,
> > they are not installed). Upstream changes are not so big. I updated
> > also debian/* files and added examples (and tests of course).
> >
> > I think it's low risky to update node-formidable. However I leave
> > you
> > appreciate if it is opportune.
>
>
> Hi all,
>
> when enabling upstream test in 1.2.1-1, it fails only under debci LXC
> environment. After many tries, I fixed this in 1.2.1-2 (was a test
> loop:
> test/run.js tried to test itself). So all tests are OK now. If you
> think
> it is opportune to unblock node-formidable,
Hi all,
here is a partial diff that shows changes on installed files.
Cheers,
Xavier
diff --git a/lib/file.js b/lib/file.js
index 1e7184d..50d34c0 100644
--- a/lib/file.js
+++ b/lib/file.js
@@ -1,7 +1,7 @@
if (global.GENTLY) require = GENTLY.hijack(require);
var util = require('util'),
-WriteStream = require('fs').WriteStream,
+fs = require('fs'),
EventEmitter = require('events').EventEmitter,
crypto = require('crypto');
@@ -23,17 +23,19 @@ function File(properties) {
if(typeof this.hash === 'string') {
this.hash = crypto.createHash(properties.hash);
+ } else {
+this.hash = null;
}
}
module.exports = File;
util.inherits(File, EventEmitter);
File.prototype.open = function() {
- this._writeStream = new WriteStream(this.path);
+ this._writeStream = new fs.WriteStream(this.path);
};
File.prototype.toJSON = function() {
- return {
+ var json = {
size: this.size,
path: this.path,
name: this.name,
@@ -43,16 +45,23 @@ File.prototype.toJSON = function() {
filename: this.filename,
mime: this.mime
};
+ if (this.hash && this.hash != "") {
+json.hash = this.hash;
+ }
+ return json;
};
File.prototype.write = function(buffer, cb) {
var self = this;
+ if (self.hash) {
+self.hash.update(buffer);
+ }
+
+ if (this._writeStream.closed) {
+return cb();
+ }
+
this._writeStream.write(buffer, function() {
-if (self.hash) {
- if (self.hash.hasOwnProperty('update')) {
-self.hash.update(buffer);
- }
-}
self.lastModifiedDate = new Date();
self.size += buffer.length;
self.emit('progress', self.size);
@@ -62,10 +71,10 @@ File.prototype.write = function(buffer, cb) {
File.prototype.end = function(cb) {
var self = this;
+ if (self.hash) {
+self.hash = self.hash.digest('hex');
+ }
this._writeStream.end(function() {
-if(self.hash) {
- self.hash = self.hash.digest('hex');
-}
self.emit('end');
cb();
});
diff --git a/lib/incoming_form.js b/lib/incoming_form.js
index 291236d..dbd920b 100644
--- a/lib/incoming_form.js
+++ b/lib/incoming_form.js
@@ -1,5 +1,6 @@
if (global.GENTLY) require = GENTLY.hijack(require);
+var crypto = require('crypto');
var fs = require('fs');
var util = require('util'),
path = require('path'),
@@ -23,13 +24,15 @@ function IncomingForm(opts) {
this.ended = false;
this.maxFields = opts.maxFields || 1000;
- this.maxFieldsSize = opts.maxFieldsSize || 2 * 1024 * 1024;
+ this.maxFieldsSize = opts.maxFieldsSize || 20 * 1024 * 1024;
+ this.maxFileSize = opts.maxFileSize || 200 * 1024 * 1024;
this.keepExtensions = opts.keepExtensions || false;
- this.uploadDir = opts.uploadDir || os.tmpDir();
+ this.uploadDir = opts.uploadDir || (os.tmpdir && os.tmpdir()) || os.tmpDir();
this.encoding = opts.encoding || 'utf-8';
this.headers = null;
this.type = null;
- this.hash = false;
+ this.hash = opts.hash || false;
+ this.multiples = opts.multiples || false;
this.bytesReceived = null;
this.bytesExpected = null;
@@ -37,10 +40,11 @@ function IncomingForm(opts) {
this._parser = null;
this._flushing = 0;
this._fieldsSize = 0;
+ this._fileSize = 0;
this.openedFiles = [];
return this;
-};
+}
util.inherits(IncomingForm, EventEmitter);
exports.IncomingForm = IncomingForm;
@@ -74,6 +78,40 @@ IncomingForm.prototype.parse = function(req, cb) {
return true;
};
+ // Setup callback first, so we don't miss anything from data events emitted
+ // immediately.
+ if (cb) {
+var fields = {}, files = {};
+this
+ .on('field', function(
Bug#927156: unblock: parted/3.2-25
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock parted 3.2-25: there was an arithmetic error in its
handling of extended partitions, which was often in practice masked by
higher-level tools but could be triggered in some circumstances such as
by gnome-disks, leading to disturbing results like apparently-vanishing
partitions. The patch is pretty clear if you look at a little more
context: one branch of an if/else block multiplied by the device's
sector size while the other didn't, which was obviously wrong.
diff -Nru parted-3.2/debian/.git-dpm parted-3.2/debian/.git-dpm
--- parted-3.2/debian/.git-dpm 2018-10-22 11:26:47.0 +0100
+++ parted-3.2/debian/.git-dpm 2019-04-15 15:21:54.0 +0100
@@ -1,6 +1,6 @@
# see git-dpm(1) from git-dpm package
-4e3c21b5b25c90ece1b197243a422663053bbc42
-4e3c21b5b25c90ece1b197243a422663053bbc42
+f82a0f5d3d12e7125572518294bb296465786422
+f82a0f5d3d12e7125572518294bb296465786422
a3803540db7f12359a111d6449159b91032c253f
a3803540db7f12359a111d6449159b91032c253f
parted_3.2.orig.tar.xz
diff -Nru parted-3.2/debian/changelog parted-3.2/debian/changelog
--- parted-3.2/debian/changelog 2019-01-12 16:45:45.0 +
+++ parted-3.2/debian/changelog 2019-04-15 15:38:11.0 +0100
@@ -1,3 +1,11 @@
+parted (3.2-25) unstable; urgency=medium
+
+ * Cherry-pick from upstream:
+- libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors (closes:
+ #926735, LP: #1641308).
+
+ -- Colin Watson Mon, 15 Apr 2019 15:38:11 +0100
+
parted (3.2-24) unstable; urgency=medium
* Set Rules-Requires-Root: no.
diff -Nru parted-3.2/debian/patches/blkpg-resize-partition-uses-bytes.patch
parted-3.2/debian/patches/blkpg-resize-partition-uses-bytes.patch
--- parted-3.2/debian/patches/blkpg-resize-partition-uses-bytes.patch
1970-01-01 01:00:00.0 +0100
+++ parted-3.2/debian/patches/blkpg-resize-partition-uses-bytes.patch
2019-04-15 15:21:54.0 +0100
@@ -0,0 +1,36 @@
+From f82a0f5d3d12e7125572518294bb296465786422 Mon Sep 17 00:00:00 2001
+From: "Brian C. Lane"
+Date: Fri, 5 Jun 2015 14:40:00 -0700
+Subject: libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors (#1135493)
+
+This results in the extended partition vanishing after adding another
+partition.
+
+Resolves: rhbz#1135493
+
+Bug-Debian: https://bugs.debian.org/926735
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1641308
+Origin: upstream,
https://git.savannah.gnu.org/cgit/parted.git/commit/?id=c6dc6e5d0f49a26242d2b28622514814a53d92e1
+Last-Update: 2019-04-15
+
+Patch-Name: blkpg-resize-partition-uses-bytes.patch
+---
+ libparted/arch/linux.c | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/libparted/arch/linux.c b/libparted/arch/linux.c
+index 3bd2878d..f85bee80 100644
+--- a/libparted/arch/linux.c
b/libparted/arch/linux.c
+@@ -2583,7 +2583,10 @@ static int _blkpg_resize_partition (PedDisk* disk,
const PedPartition *part)
+ if (walk->geom.start == part->geom.start+1)
+ linux_part.length = 1;
+ }
+-} else linux_part.length = 1;
++} else {
++linux_part.length = 1;
++}
++linux_part.length *= disk->dev->sector_size;
+ }
+ else
+ linux_part.length = part->geom.length *
disk->dev->sector_size;
diff -Nru parted-3.2/debian/patches/series parted-3.2/debian/patches/series
--- parted-3.2/debian/patches/series2018-10-22 11:26:47.0 +0100
+++ parted-3.2/debian/patches/series2019-04-15 15:21:54.0 +0100
@@ -29,3 +29,4 @@
fat-resize-retain-boot-code.patch
sysmacros-for-major-minor.patch
nvme-model-names-from-sysfs.patch
+blkpg-resize-partition-uses-bytes.patch
unblock parted/3.2-25
--
Colin Watson [cjwat...@debian.org]
NEW changes in stable-new
Processing changes file: gocode_20150303-3+deb9u1_armel.changes ACCEPT Processing changes file: gocode_20150303-3+deb9u1_armhf.changes ACCEPT Processing changes file: linux-latest_80+deb9u7_mips64el.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_arm64.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_armel.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_armhf.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_i386.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_mips.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_mips64el.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_mipsel.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_ppc64el.changes ACCEPT
Processed: Re: Bug#927064: unblock: synaptic/0.84.5+nmu1
Processing control commands: > retitle -1 unblock: synaptic/0.84.6 Bug #927064 [release.debian.org] unblock: synaptic/0.84.5+nmu1 Changed Bug title to 'unblock: synaptic/0.84.6' from 'unblock: synaptic/0.84.5+nmu1'. > tags -1 - moreinfo Bug #927064 [release.debian.org] unblock: synaptic/0.84.6 Removed tag(s) moreinfo. -- 927064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927064: unblock: synaptic/0.84.5+nmu1
Control: retitle -1 unblock: synaptic/0.84.6
Control: tags -1 - moreinfo
X-Debbugs-CC: m...@debian.org
Michael Vogt(the synaptic maintainer) has merged my PR on github and
uploaded synaptic/0.84.6.
It has been built on all release architectures.
The full changelog is:
synaptic (0.84.6) unstable; urgency=medium
.
[ sajolida ]
* Give visual feedback while starting
.
[ Shengjing Zhu ]
* configure.in: Miss bumping version str to 0.84.5
* synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
* gsynaptic: Show possible reason when failed to init gtk
.
[ Michael Vogt ]
* configure.in: Bump version to 0.84.6
In addition to my previous attached debdiff, there're two trivial new
lines in synaptic.desktop:
+StartupNotify=true
+StartupWMClass=synaptic
Full debdiff between 0.84.5 and 0.84.6 is:
diff -Nru synaptic-0.84.5/configure.in synaptic-0.84.6/configure.in
--- synaptic-0.84.5/configure.in2018-11-08 15:50:31.0 +0800
+++ synaptic-0.84.6/configure.in2019-04-15 15:39:32.0 +0800
@@ -1,7 +1,7 @@
dnl Process this file with autoconf to produce a configure script.
AC_INIT(configure.in)
-AM_INIT_AUTOMAKE(synaptic, 0.84.5)
+AM_INIT_AUTOMAKE(synaptic, 0.84.6)
AM_CONFIG_HEADER(config.h)
AM_MAINTAINER_MODE
diff -Nru synaptic-0.84.5/data/synaptic.desktop.in
synaptic-0.84.6/data/synaptic.desktop.in
--- synaptic-0.84.5/data/synaptic.desktop.in2018-11-08 15:50:31.0
+0800
+++ synaptic-0.84.6/data/synaptic.desktop.in2019-04-15 15:39:32.0
+0800
@@ -8,3 +8,5 @@
Type=Application
Categories=PackageManager;GTK;System;Settings;
X-Ubuntu-Gettext-Domain=synaptic
+StartupNotify=true
+StartupWMClass=synaptic
diff -Nru synaptic-0.84.5/debian/changelog synaptic-0.84.6/debian/changelog
--- synaptic-0.84.5/debian/changelog2018-11-08 15:50:31.0 +0800
+++ synaptic-0.84.6/debian/changelog2019-04-15 15:39:32.0 +0800
@@ -1,3 +1,18 @@
+synaptic (0.84.6) unstable; urgency=medium
+
+ [ sajolida ]
+ * Give visual feedback while starting
+
+ [ Shengjing Zhu ]
+ * configure.in: Miss bumping version str to 0.84.5
+ * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
+ * gsynaptic: Show possible reason when failed to init gtk
+
+ [ Michael Vogt ]
+ * configure.in: Bump version to 0.84.6
+
+ -- Michael Vogt Mon, 15 Apr 2019 09:39:32 +0200
+
synaptic (0.84.5) unstable; urgency=medium
[ Jeremy Bicha ]
@@ -6,7 +21,7 @@
[ Guillem Jover ]
* Update sections and their descriptions (Closes: #880482)
- -- Michael Vogt Thu, 08 Nov 2018 08:50:31 +0100
+ -- Michael Vogt Mon, 15 Apr 2019 09:39:26 +0200
synaptic (0.84.4) unstable; urgency=medium
diff -Nru synaptic-0.84.5/debian/control synaptic-0.84.6/debian/control
--- synaptic-0.84.5/debian/control 2018-11-08 15:50:31.0 +0800
+++ synaptic-0.84.6/debian/control 2019-04-15 15:39:32.0 +0800
@@ -11,7 +11,7 @@
Package: synaptic
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, hicolor-icon-theme, policykit-1
+Depends: ${shlibs:Depends}, ${misc:Depends}, hicolor-icon-theme, policykit-1,
zenity
Conflicts: menu (<< 2.1.11)
Recommends: libgtk2-perl (>= 1:1.130), xdg-utils
Suggests: dwww, menu, deborphan, apt-xapian-index, tasksel,
software-properties-gtk
diff -Nru synaptic-0.84.5/debian/patches/00list
synaptic-0.84.6/debian/patches/00list
--- synaptic-0.84.5/debian/patches/00list 2018-11-08 15:50:31.0
+0800
+++ synaptic-0.84.6/debian/patches/00list 2019-04-15 15:39:32.0
+0800
@@ -1,3 +0,0 @@
-01_ubuntu_changelog
-#10_ubuntu_maintenance_gui
-
diff -Nru synaptic-0.84.5/debian/synaptic-pkexec
synaptic-0.84.6/debian/synaptic-pkexec
--- synaptic-0.84.5/debian/synaptic-pkexec 2018-11-08 15:50:31.0
+0800
+++ synaptic-0.84.6/debian/synaptic-pkexec 2019-04-15 15:39:32.0
+0800
@@ -1,2 +1,19 @@
#!/bin/sh
-pkexec "/usr/sbin/synaptic" "$@"
+
+USING_WAYLAND=0
+if [ ! "x${WAYLAND_DISPLAY}" = "x" ]; then
+USING_WAYLAND=1
+fi
+if [ "x${XDG_SESSION_TYPE}" = "xwayland" ]; then
+USING_WAYLAND=1
+fi
+
+if [ "x${USING_WAYLAND}" = "x1" ]; then
+# Running wayland; start synaptic without pkexec
+zenity --warning --width=500 --text \
+"You are using Wayland environment, Synaptic will continue without
administrative privileges.\\n\
+To make Synaptic fully functional, please restart your session without
Wayland."
+exec "/usr/sbin/synaptic" "$@"
+else
+pkexec "/usr/sbin/synaptic" "$@"
+fi
diff -Nru synaptic-0.84.5/gtk/gsynaptic.cc synaptic-0.84.6/gtk/gsynaptic.cc
--- synaptic-0.84.5/gtk/gsynaptic.cc2018-11-08 15:50:31.0 +0800
+++ synaptic-0.84.6/gtk/gsynaptic.cc2019-04-15 15:39:32.0 +0800
@@ -409,7 +409,14 @@
#endif
#endif
- gtk_init(&argc, &argv);
+ if (!gtk_init_check(&argc, &argv)) {
+ std::cout <<
+ _("Failed to initialize GTK.\n") <<
+ "\n" <<
+ _("Probably you'
NEW changes in stable-new
Processing changes file: gocode_20150303-3+deb9u1_all.changes ACCEPT Processing changes file: gocode_20150303-3+deb9u1_amd64.changes ACCEPT Processing changes file: gocode_20150303-3+deb9u1_arm64.changes ACCEPT Processing changes file: gocode_20150303-3+deb9u1_i386.changes ACCEPT Processing changes file: gocode_20150303-3+deb9u1_ppc64el.changes ACCEPT Processing changes file: jabref_3.8.1+ds-3+deb9u1_all.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_s390x.changes ACCEPT
Bug#927141: unblock: calamares-settings-debian/10.0.19-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package calamares-settings-debian This upload fixes the following important issues: * Fix Debian name (too long to fit into label size) * Fix Debian release notes URL (still refered to stretch) * Fix stale EFI file (BTS #927102) Full DebDiff: """ diff -Nru calamares-settings-debian-10.0.18/calamares/branding/debian/branding.desc calamares-settings-debian-10.0.19/calamares/branding/debian/branding.desc --- calamares-settings-debian-10.0.18/calamares/branding/debian/branding.desc 2019-02-15 14:03:55.0 + +++ calamares-settings-debian-10.0.19/calamares/branding/debian/branding.desc 2019-04-15 12:59:42.0 + @@ -7,12 +7,12 @@ shortProductName:Debian version: 10 (buster) shortVersion:10 -versionedName: Debian GNU/Linux 10 (buster) +versionedName: Debian 10 (buster) shortVersionedName: Debian 10 bootloaderEntryName: Debian productUrl: https://debian.org supportUrl: https://www.debian.org/support -releaseNotesUrl: https://www.debian.org/releases/stretch/releasenotes +releaseNotesUrl: https://www.debian.org/releases/buster/releasenotes images: productLogo: "debian-logo.png" diff -Nru calamares-settings-debian-10.0.18/calamares/modules/bootloader.conf calamares-settings-debian-10.0.19/calamares/modules/bootloader.conf --- calamares-settings-debian-10.0.18/calamares/modules/bootloader.conf 2019-02-15 14:03:55.0 + +++ calamares-settings-debian-10.0.19/calamares/modules/bootloader.conf 2019-04-15 12:59:42.0 + @@ -51,4 +51,4 @@ # seems to be the only one). If you set this to false, take care # to add another module to optionally install the fallback on those # boards that need it. -installEFIFallback: true +installEFIFallback: false diff -Nru calamares-settings-debian-10.0.18/debian/changelog calamares-settings-debian-10.0.19/debian/changelog --- calamares-settings-debian-10.0.18/debian/changelog 2019-02-15 14:06:39.0 + +++ calamares-settings-debian-10.0.19/debian/changelog 2019-04-15 13:32:36.0 + @@ -1,3 +1,12 @@ +calamares-settings-debian (10.0.19-1) unstable; urgency=medium + + * New upstream release +- Don't install unnecessary efi file (Closes: #927102) +- Fix distribution description +- Fix release notes URL + + -- Jonathan Carter Mon, 15 Apr 2019 13:32:36 + + calamares-settings-debian (10.0.18-1) unstable; urgency=medium * New upstream releas """ thanks, -Jonathan
Processed: Re: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)
Processing control commands:
> tags -1 - moreinfo
Bug #926994 {Done: Ivo De Decker }
[release.debian.org] unblock: gcc-mingw-w64/21.2 (pre-upload approval request)
Removed tag(s) moreinfo.
--
926994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#926994: unblock: gcc-mingw-w64/21.2 (pre-upload approval request)
Control: tags -1 - moreinfo Le 13/04/2019 16:31, Ivo De Decker a écrit : I had a look at the patches, and they seem like something that would be acceptable for buster. Please go ahead with the upload to unstable and remove the moreinfo tag from this bug once the builds are done. The builds are done, but I see you beat me to it ;-). Thanks, Stephen
NEW changes in stable-new
Processing changes file: linux_4.9.168-1_mips64el.changes ACCEPT
Bug#927129: marked as done (unblock: postgresql-common/200+deb10u1)
Your message dated Mon, 15 Apr 2019 12:45:00 + with message-id and subject line Re: Bug#927129: unblock: postgresql-common/200+deb10u1 has caused the Debian Bug report #927129, regarding unblock: postgresql-common/200+deb10u1 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.) -- 927129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927129 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 postgresql-common. The new version contains in NEWS.Debian the same message that was added to the release notes as #926627. Thanks. commit b7ded1188f8605fc815149018d44766d2c302bd2 Author: Christoph Berg Date: Fri Apr 12 15:18:36 2019 +0200 postgresql-common.NEWS: Warn users about glibc collation changes The same message will appear in the release-notes: #926627 diff --git a/debian/changelog b/debian/changelog index 58f61b0..427c1d8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +postgresql-common (200+deb10u1) unstable; urgency=medium + + * When upgrading from stretch to buster, all text indexes need to be +reindexed. Warn users about that in NEWS.Debian. + + -- Christoph Berg Fri, 12 Apr 2019 14:32:52 +0200 + postgresql-common (200) unstable; urgency=medium * pg_createcluster: Don't refuse explicit -p argument even when port is diff --git a/debian/postgresql-common.NEWS b/debian/postgresql-common.NEWS index fca02fd..7db0799 100644 --- a/debian/postgresql-common.NEWS +++ b/debian/postgresql-common.NEWS @@ -1,3 +1,25 @@ +postgresql-common (200+deb10u1) buster; urgency=high + + Existing PostgreSQL databases need to be reindexed + + When upgrading from stretch to buster, the glibc locale data is upgraded. + Specifically, this changes how PostgreSQL sorts data in text indexes. To + avoid corruption, such indexes need to be REINDEXed immediately after + upgrading the locales or locales-all packages, before putting back the + database into production. + + Suggested command: sudo -u postgres reindexdb --all + + Alternatively, upgrade the databases to PostgreSQL 11 using + pg_upgradecluster. (This uses pg_dump by default which will rebuild all + indexes. Using -m upgrade or pg_upgrade is not safe because it preserves + the now-wrong index ordering.) + + Refer to the PostgreSQL Wiki for more information: +https://wiki.postgresql.org/wiki/Locale_data_changes + + -- Christoph Berg Fri, 12 Apr 2019 14:32:52 +0200 + postgresql-common (161) unstable; urgency=medium pg_ctlcluster is now enforcing stricter file ownership on the cluster config unblock postgresql-common/200+deb10u1 Christoph --- End Message --- --- Begin Message --- Christoph Berg: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package postgresql-common. The new version contains in > NEWS.Debian the same message that was added to the release notes as > #926627. Thanks. > > [...] > > unblock postgresql-common/200+deb10u1 > > Christoph > Unblocked, thanks. ~Niels--- End Message ---
NEW changes in stable-new
Processing changes file: libreoffice_5.2.7-1+deb9u6_mipsel.changes ACCEPT
Bug#927129: unblock: postgresql-common/200+deb10u1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package postgresql-common. The new version contains in NEWS.Debian the same message that was added to the release notes as #926627. Thanks. commit b7ded1188f8605fc815149018d44766d2c302bd2 Author: Christoph Berg Date: Fri Apr 12 15:18:36 2019 +0200 postgresql-common.NEWS: Warn users about glibc collation changes The same message will appear in the release-notes: #926627 diff --git a/debian/changelog b/debian/changelog index 58f61b0..427c1d8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +postgresql-common (200+deb10u1) unstable; urgency=medium + + * When upgrading from stretch to buster, all text indexes need to be +reindexed. Warn users about that in NEWS.Debian. + + -- Christoph Berg Fri, 12 Apr 2019 14:32:52 +0200 + postgresql-common (200) unstable; urgency=medium * pg_createcluster: Don't refuse explicit -p argument even when port is diff --git a/debian/postgresql-common.NEWS b/debian/postgresql-common.NEWS index fca02fd..7db0799 100644 --- a/debian/postgresql-common.NEWS +++ b/debian/postgresql-common.NEWS @@ -1,3 +1,25 @@ +postgresql-common (200+deb10u1) buster; urgency=high + + Existing PostgreSQL databases need to be reindexed + + When upgrading from stretch to buster, the glibc locale data is upgraded. + Specifically, this changes how PostgreSQL sorts data in text indexes. To + avoid corruption, such indexes need to be REINDEXed immediately after + upgrading the locales or locales-all packages, before putting back the + database into production. + + Suggested command: sudo -u postgres reindexdb --all + + Alternatively, upgrade the databases to PostgreSQL 11 using + pg_upgradecluster. (This uses pg_dump by default which will rebuild all + indexes. Using -m upgrade or pg_upgrade is not safe because it preserves + the now-wrong index ordering.) + + Refer to the PostgreSQL Wiki for more information: +https://wiki.postgresql.org/wiki/Locale_data_changes + + -- Christoph Berg Fri, 12 Apr 2019 14:32:52 +0200 + postgresql-common (161) unstable; urgency=medium pg_ctlcluster is now enforcing stricter file ownership on the cluster config unblock postgresql-common/200+deb10u1 Christoph
Bug#914591: stretch-pu: package python-cryptography/1.7.1-3
On 2019-04-15 08:50:52 [+0100], Adam D. Barratt wrote: > OK, thanks for the confirmation. > > Please go ahead. uploaded. > Regards, > > Adam Sebastian
Bug#927127: marked as done (unblock: ruby-websocket/1.2.8-2)
Your message dated Mon, 15 Apr 2019 12:09:21 +
with message-id
and subject line unblock ruby-websocket
has caused the Debian Bug report #927127,
regarding unblock: ruby-websocket/1.2.8-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.)
--
927127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927127
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-websocket
This fixes a file conflict with another package that invades its
namespace. The changes are trivial:
8<8<8<-
diff --git a/debian/changelog b/debian/changelog
index dc5fdfc..d49bace 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ruby-websocket (1.2.8-2) unstable; urgency=medium
+
+ * Team upload
+ * Add Breaks/Replaces against ruby-websocker-parser (Closes: #926254)
+
+ -- Antonio Terceiro Sun, 14 Apr 2019 20:23:47 -0300
+
ruby-websocket (1.2.8-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/control b/debian/control
index 27f764d..2304613 100644
--- a/debian/control
+++ b/debian/control
@@ -20,6 +20,8 @@ XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby | ruby-interpreter,
${misc:Depends},
${shlibs:Depends}
+Breaks: ruby-websocket-parser (<= 1.0.0-1)
+Replaces: ruby-websocket-parser (<= 1.0.0-1)
Description: Universal Ruby library to handle WebSocket protocol
This library focuses on providing abstraction layer over
WebSocket API instead of providing server or client
8<8<8<-
unblock ruby-websocket/1.2.8-2
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Unblocked ruby-websocket.--- End Message ---
Bug#927125: unblock: desktop-base/10.0.2
Le 15/04/2019 à 13:19, Jonathan Carter a écrit : > It fixes/completes the artwork, which unfortunately results in a rather large > diff (due to wallpaper changes which makes a debdiff a bit impractical), but > I've > tested it locally and it works fine and fixes the important changes. I’d like to add that I tested these changes on top of default desktop installs for Gnome, KDE and XFCE in some VMs and these were working as expected. Thanks, -- Aurélien
Bug#927127: unblock: ruby-websocket/1.2.8-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ruby-websocket
This fixes a file conflict with another package that invades its
namespace. The changes are trivial:
8<8<8<-
diff --git a/debian/changelog b/debian/changelog
index dc5fdfc..d49bace 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ruby-websocket (1.2.8-2) unstable; urgency=medium
+
+ * Team upload
+ * Add Breaks/Replaces against ruby-websocker-parser (Closes: #926254)
+
+ -- Antonio Terceiro Sun, 14 Apr 2019 20:23:47 -0300
+
ruby-websocket (1.2.8-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/control b/debian/control
index 27f764d..2304613 100644
--- a/debian/control
+++ b/debian/control
@@ -20,6 +20,8 @@ XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby | ruby-interpreter,
${misc:Depends},
${shlibs:Depends}
+Breaks: ruby-websocket-parser (<= 1.0.0-1)
+Replaces: ruby-websocket-parser (<= 1.0.0-1)
Description: Universal Ruby library to handle WebSocket protocol
This library focuses on providing abstraction layer over
WebSocket API instead of providing server or client
8<8<8<-
unblock ruby-websocket/1.2.8-2
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
signature.asc
Description: PGP signature
Bug#924642: stretch-pu: package rsync/3.1.2-1+deb9u1
On Sun 14 Apr 2019, Adam D. Barratt wrote: > > Apologies for having let this slip off the radar a little. NP > I just flagged the current upload to be rejected. Please re-build the > package with "stretch" in the changelog rather than "stretch-security", > and feel free to go ahead with the re-upload once dak confirms that the > reject has been actioned. I've just uploaded it. Thanks, Paul
Bug#926994: marked as done (unblock: gcc-mingw-w64/21.2 (pre-upload approval request))
Your message dated Mon, 15 Apr 2019 11:20:27 + with message-id and subject line unblock gcc-mingw-w64 has caused the Debian Bug report #926994, regarding unblock: gcc-mingw-w64/21.2 (pre-upload approval request) 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.) -- 926994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926994 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, I have a couple of fixes pending upload for gcc-mingw-w64, and I’m wondering if they’d pass muster for Buster. The attached patches fix, in order: * #923214 — an ICE hit with external static data members * #925172 — std::filesystem support is broken in the current Buster package I’m requesting approval for these fixes before uploading them to unstable. The candidate source package would contain only those fixes plus the result of running "dch -r". Note that because of the way gcc-mingw-w64 works, this would involve pulling gcc-8 8.3.0-6 (or whatever version is in unstable when the package is built) in too. Regards, Stephen unblock gcc-mingw-w64/21.2 -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Unblocked gcc-mingw-w64.--- End Message ---
Bug#927125: unblock: desktop-base/10.0.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package desktop-base It fixes important dependency problems: * missing plymouth depends on plymouth-label which is needed to display text output during boot * missing dependency on font to make text render correctly in login screen By mistake I also uploaded a whole bunch of fixes that was pending in master (I believed that they were already uploaded by coucouf before). It fixes/completes the artwork, which unfortunately results in a rather large diff (due to wallpaper changes which makes a debdiff a bit impractical), but I've tested it locally and it works fine and fixes the important changes. Thanks -Jonathan
NEW changes in stable-new
Processing changes file: gocode_20150303-3+deb9u1_source.changes ACCEPT Processing changes file: jabref_3.8.1+ds-3+deb9u1_source.changes ACCEPT Processing changes file: vcftools_0.1.14+dfsg-4+deb9u1_amd64.changes ACCEPT
Processed: gocode 20150303-3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926438 [release.debian.org] stretch-pu: package gocode/20150303-3+deb9u1 Ignoring request to alter tags of bug #926438 to the same tags previously set -- 926438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vcftools 0.1.14+dfsg-4+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927068 [release.debian.org] stretch-pu: package vcftools/0.1.14+dfsg-4+deb9u1 Added tag(s) pending. -- 927068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vcftools 0.1.14+dfsg-4+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927068 [release.debian.org] stretch-pu: package vcftools/0.1.14+dfsg-4+deb9u1 Ignoring request to alter tags of bug #927068 to the same tags previously set -- 927068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: jabref 3.8.1+ds-3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927072 [release.debian.org] stretch-pu: package jabref/3.8.1+ds-3 Added tag(s) pending. -- 927072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927072: jabref 3.8.1+ds-3+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: jabref Version: 3.8.1+ds-3+deb9u1 Explanation: fix XML External Entity attack [CVE-2018-1000652]
Processed: jabref 3.8.1+ds-3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927072 [release.debian.org] stretch-pu: package jabref/3.8.1+ds-3 Ignoring request to alter tags of bug #927072 to the same tags previously set -- 927072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927121: marked as done (unblock: glusterfs/5.5-3)
Your message dated Mon, 15 Apr 2019 10:42:04 +
with message-id
and subject line unblock glusterfs
has caused the Debian Bug report #927121,
regarding unblock: glusterfs/5.5-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.)
--
927121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927121
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 glusterfs
It adds one upstream patch - which is now in the 5.6 release - to fix this
critical
bug: https://bugzilla.redhat.com/show_bug.cgi?id=1673058
See also: https://review.gluster.org/#/c/glusterfs/+/22404/
diff -Naur '--exclude=.svn' 5.5-2/debian/changelog 5.5-3/debian/changelog
--- 5.5-2/debian/changelog 2019-04-09 13:47:11.558039914 +0200
+++ 5.5-3/debian/changelog 2019-04-15 10:23:28.871148221 +0200
@@ -1,3 +1,10 @@
+glusterfs (5.5-3) unstable; urgency=medium
+
+ * Add upstream patch 05-client-rpc-payload-wire to fix the payload being sent
+on the wire.
+
+ -- Patrick Matthäi Mon, 15 Apr 2019 10:07:38 +0200
+
glusterfs (5.5-2) unstable; urgency=medium
* Uploading to unstable.
diff -Naur '--exclude=.svn'
5.5-2/debian/patches/05-client-rpc-payload-wire.diff
5.5-3/debian/patches/05-client-rpc-payload-wire.diff
--- 5.5-2/debian/patches/05-client-rpc-payload-wire.diff1970-01-01
01:00:00.0 +0100
+++ 5.5-3/debian/patches/05-client-rpc-payload-wire.diff2019-04-15
10:23:28.943147770 +0200
@@ -0,0 +1,1619 @@
+commit 1fba86169b0850c3fcd02e56d0ddbba3efe9ae78
+Author: Poornima G
+Date: Sun Mar 24 09:40:50 2019 +0530
+
+client-rpc: Fix the payload being sent on the wire
+
+The fops allocate 3 kind of payload(buffer) in the client xlator:
+- fop payload, this is the buffer allocated by the write and put fop
+- rsphdr paylod, this is the buffer required by the reply cbk of
+ some fops like lookup, readdir.
+- rsp_paylod, this is the buffer required by the reply cbk of fops like
+ readv etc.
+
+Currently, in the lookup and readdir fop the rsphdr is sent as payload,
+hence the allocated rsphdr buffer is also sent on the wire, increasing
+the bandwidth consumption on the wire.
+
+With this patch, the issue is fixed.
+
+Fixes: bz#1673058
+Change-Id: Ie8158921f4db319e60ad5f52d851fa5c9d4a269b
+Signed-off-by: Poornima G
+
+diff --git a/xlators/protocol/client/src/client-handshake.c
b/xlators/protocol/client/src/client-handshake.c
+index ed9d0a5d9..e1334f9e3 100644
+--- a/xlators/protocol/client/src/client-handshake.c
b/xlators/protocol/client/src/client-handshake.c
+@@ -34,7 +34,6 @@ typedef struct client_fd_lk_local {
+ clnt_fd_ctx_t *fdctx;
+ } clnt_fd_lk_local_t;
+
+-
+ int32_t
+ client3_getspec(call_frame_t *frame, xlator_t *this, void *data)
+ {
+@@ -201,8 +200,8 @@ clnt_release_reopen_fd(xlator_t *this, clnt_fd_ctx_t
*fdctx)
+ req.fd = fdctx->remote_fd;
+
+ ret = client_submit_request(this, &req, frame, conf->fops,
GFS3_OP_RELEASE,
+-clnt_release_reopen_fd_cbk, NULL, NULL, 0,
NULL,
+-0, NULL, (xdrproc_t)xdr_gfs3_releasedir_req);
++clnt_release_reopen_fd_cbk, NULL,
++(xdrproc_t)xdr_gfs3_releasedir_req);
+ out:
+ if (ret) {
+ clnt_fd_lk_reacquire_failed(this, fdctx, conf);
+@@ -486,8 +485,8 @@ protocol_client_reopendir(clnt_fd_ctx_t *fdctx, xlator_t
*this)
+ frame->local = local;
+
+ ret = client_submit_request(this, &req, frame, conf->fops,
GFS3_OP_OPENDIR,
+-client3_3_reopendir_cbk, NULL, NULL, 0, NULL,
0,
+-NULL, (xdrproc_t)xdr_gfs3_opendir_req);
++client3_3_reopendir_cbk, NULL,
++(xdrproc_t)xdr_gfs3_opendir_req);
+ if (ret) {
+ gf_msg(this->name, GF_LOG_ERROR, 0, PC_MSG_DIR_OP_FAILED,
+"failed to send the re-opendir request");
+@@ -547,8 +546,8 @@ protocol_client_reopenfile(clnt_fd_ctx_t *fdctx, xlator_t
*this)
+ local->loc.path);
+
+ ret = client_submit_request(this, &req, frame, conf->fops, GFS3_OP_OPEN,
+-client3_3_reopen_cbk, NULL, NULL, 0, NULL, 0,
+-NULL, (xdrproc_t)xdr_gfs3_open_req);
++client3_3_reopen_cbk, NULL,
++(xdrproc_t)xdr_gfs3_ope
Bug#927068: vcftools 0.1.14+dfsg-4+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: vcftools Version: 0.1.14+dfsg-4+deb9u1 Explanation: security fixes [CVE-2018-11099 CVE-2018-11129 CVE-2018-11130]
Processed: gocode 20150303-3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926438 [release.debian.org] stretch-pu: package gocode/20150303-3+deb9u1 Added tag(s) pending. -- 926438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926438: gocode 20150303-3+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: gocode Version: 20150303-3+deb9u1 Explanation: gocode-auto-complete-el: Promote auto-complete-el to Pre-Depends
Bug#926773: marked as done (unblock: bash/5.0-2)
Your message dated Mon, 15 Apr 2019 10:38:06 + with message-id and subject line unblock bash has caused the Debian Bug report #926773, regarding unblock: bash/5.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.) -- 926773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926773 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 consider unblocking bash, adding one upstream issue, and fixing the clear_console utility. Changes: bash (5.0-3) unstable; urgency=medium . * Apply upstream patch 003. * Fix clear_console locking up video when X is running and logging out from a plain text console. Closes: #810660. LP: #1822184. --- End Message --- --- Begin Message --- Unblocked bash.--- End Message ---
Re: Please verify that buster related suites are functional
On Mon, Apr 15, 2019 at 07:57:20AM +0200, Salvatore Bonaccorso wrote: > Hi Niels, release team and ftp-masters, > > [dropping backports list for this reply, adding ftp-masters] > > On Sun, Apr 14, 2019 at 09:02:00PM +, Niels Thykier wrote: > > Hi Security team and backports team, > > > > According to the release team's checklist we have the following TODO for > > you: > > > > """ > > Check with security team and backports team that it is possible to build > > uploads for -security and -backports > > """ > > > > To our knowledge, the relevant suites have already been created > > (#917537) and ask that you kindly smoke test them to ensure they work as > > intended. > > > > * Please let us know when you have verified these relevant suites or if > >you have any issues with them. > > The easiest thing is still to do as in previous releases and prepare a > src:hello as follows (which have done locally): > > hello (2.10-1+deb10u1) buster-security; urgency=high > . >* Non-maintainer upload by the Security Team. >* No-change test upload for buster-security > > upload it, verify it get's correctly processed into the embargoed > queues, buildd's pick it up for build on all supported architectures. > > Then the next step was to actually dak install it and verify it > correctly land in the security archive. > > But after that we have a hello/2.10-1+deb10u1 in the security archive. > Question to FTP master, can we just after this test dak remove the > package again and let forget the test version? > > I'm asking because Santiago, maintainer of src:hello raised concern > that we should not use src:hello for this final infrastructure test. > Obviously we otherwise can just fork it. But as package it has nice > characteristics as testpackage. Exactly. Leaving aside the fact that we are highly skilled people that could use all sort of sandboxes to test things and not the real thing, if you absolutely must use a real package, for all means use one that either: a) Has a real security problem. b) Has a real security history that will surely make subsequent security uploads to supersede the "fake" one, for example, the linux package. If this is not possible, I offered Salvatore and Security People to upload base-files in a way that leaves no traces after the test has been made. I still have to upload base-files_10.2 for buster with the final changes, if you can upload base-files_10.1+deb1 and we can have any assurance that this will not prevent base-files_10.2 from propagating from unstable to testing, that would be a lot better than a fake upload of src:hello. Thanks.
Bug#927119: marked as done (unblock: apt-dater/1.0.4-2)
Your message dated Mon, 15 Apr 2019 10:35:21 + with message-id and subject line unblock apt-dater has caused the Debian Bug report #927119, regarding unblock: apt-dater/1.0.4-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.) -- 927119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927119 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 apt-dater. It adds missing README.* files and fixes a bug, where you can not create new sessions, because of an old deprecated configuration for tmux. diff -Naur '--exclude=.svn' 1.0.4-1/debian/apt-dater.docs 1.0.4-2/debian/apt-dater.docs --- 1.0.4-1/debian/apt-dater.docs 2019-02-11 10:58:30.644694694 +0100 +++ 1.0.4-2/debian/apt-dater.docs 2019-04-15 10:23:54.946984935 +0200 @@ -1,3 +1,2 @@ README -README.tclfilter -README.xmlreport +README.* diff -Naur '--exclude=.svn' 1.0.4-1/debian/changelog 1.0.4-2/debian/changelog --- 1.0.4-1/debian/changelog2019-02-11 10:58:30.624694772 +0100 +++ 1.0.4-2/debian/changelog2019-04-15 10:23:54.906985186 +0200 @@ -1,3 +1,12 @@ +apt-dater (1.0.4-2) unstable; urgency=medium + + * Install missing docs. +Closes: #924176 + * Add patch 01-tmux-options to fix an error with tmux 2.4, because of an old +invalid option. + + -- Patrick Matthäi Mon, 15 Apr 2019 10:07:25 +0200 + apt-dater (1.0.4-1) unstable; urgency=medium * New upstream release. diff -Naur '--exclude=.svn' 1.0.4-1/debian/patches/01-tmux-options.diff 1.0.4-2/debian/patches/01-tmux-options.diff --- 1.0.4-1/debian/patches/01-tmux-options.diff 1970-01-01 01:00:00.0 +0100 +++ 1.0.4-2/debian/patches/01-tmux-options.diff 2019-04-15 10:23:54.906985186 +0200 @@ -0,0 +1,15 @@ +# tmux 2.4 changed this option, we need it for new created sessions +# or tmux will fail with an unknown option error. + +diff -Naur apt-dater-1.0.4.orig/conf/tmux.conf apt-dater-1.0.4/conf/tmux.conf +--- apt-dater-1.0.4.orig/conf/tmux.conf2019-02-10 22:16:03.0 +0100 apt-dater-1.0.4/conf/tmux.conf 2019-04-15 10:02:11.499131926 +0200 +@@ -11,7 +11,7 @@ + set -g terminal-overrides 'xterm*:smcup@:rmcup@' + + set-option -g history-limit 1 +-set-option -g set-remain-on-exit on ++set-hook -g session-created 'set remain-on-exit on' + + # Make C-a q kill the pane (simular to GNU screen) + bind-key q confirm-before -p "kill-pane #P? (y/n)" kill-pane diff -Naur '--exclude=.svn' 1.0.4-1/debian/patches/series 1.0.4-2/debian/patches/series --- 1.0.4-1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ 1.0.4-2/debian/patches/series 2019-04-15 10:23:54.906985186 +0200 @@ -0,0 +1 @@ +01-tmux-options.diff unblock apt-dater/1.0.4-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Unblocked apt-dater.--- End Message ---
Bug#927118: marked as done (unblock: python-trustme/0.4.0-3)
Your message dated Mon, 15 Apr 2019 10:33:22 + with message-id and subject line unblock python-trustme has caused the Debian Bug report #927118, regarding unblock: python-trustme/0.4.0-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.) -- 927118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927118 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 python-trustme This fixes a second FTBFS, further to the previous unblock request in bug 925576. This time the build failed on the buildds but not in my local testing because openssl was installed there, which (correctly) isn't a build dependency. The fix is to generate larger keys. The same change has now been accepted by upstream. diff -Nru python-trustme-0.4.0/debian/changelog python-trustme-0.4.0/debian/changelog --- python-trustme-0.4.0/debian/changelog 2018-10-13 22:48:59.0 +0100 +++ python-trustme-0.4.0/debian/changelog 2019-04-13 17:30:43.0 +0100 @@ -1,3 +1,19 @@ +python-trustme (0.4.0-3) unstable; urgency=medium + + * d/p/keysize: bump test key sizes to 2048 to fulfil Debian's new default +requirement. This fixes another FTBFS due to test failure in the case that +the openssl binary package is installed, which is not a build dependency, +but apparently the buildds have it by default. Closes: #926652. + + -- Robie Basak Sat, 13 Apr 2019 17:30:20 +0100 + +python-trustme (0.4.0-2) unstable; urgency=medium + + * Explicitly build-depend on python3-idna to fix FTBFS. +Closes: #925566. + + -- Robie Basak Tue, 26 Mar 2019 23:22:42 + + python-trustme (0.4.0-1) unstable; urgency=low * Initial release. Closes: #910951. diff -Nru python-trustme-0.4.0/debian/control python-trustme-0.4.0/debian/control --- python-trustme-0.4.0/debian/control 2018-10-13 22:48:59.0 +0100 +++ python-trustme-0.4.0/debian/control 2019-04-13 17:22:21.0 +0100 @@ -6,6 +6,7 @@ Build-Depends: debhelper (>= 9~), dh-python, python3, + python3-idna, python3-openssl, python3-pytest, python3-service-identity, diff -Nru python-trustme-0.4.0/debian/patches/keysize python-trustme-0.4.0/debian/patches/keysize --- python-trustme-0.4.0/debian/patches/keysize 1970-01-01 01:00:00.0 +0100 +++ python-trustme-0.4.0/debian/patches/keysize 2019-04-13 17:26:01.0 +0100 @@ -0,0 +1,33 @@ +From 96b8799325fa0f53fad4db529cbd2d25af42ebff Mon Sep 17 00:00:00 2001 +From: Robie Basak +Date: Sat, 13 Apr 2019 17:02:53 +0100 +Subject: [PATCH] Increase key size to 2048 bits + +Debian changed the default security level to 2 since openssl package +version 1.1.1~~pre9-1 (August 2018), which requires a minimum key size +of 2048 bit or larger RSA and DHE keys. To avoid test failures on newer +Debian systems against OpenSSL, use a key size of at least 2048 bits. + +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926652 +Forwarded: https://github.com/python-trio/trustme/pull/45 +Last-Update: 2019-04-13 +--- + trustme/__init__.py | 7 ++- + 1 file changed, 6 insertions(+), 1 deletion(-) + +--- a/trustme/__init__.py b/trustme/__init__.py +@@ -33,7 +33,12 @@ + # On my laptop, making a CA + server certificate using 1024 bit keys takes ~40 + # ms, and using 4096 bit keys takes ~2 seconds. We want tests to run in 40 ms, + # not 2 seconds. +-_KEY_SIZE = 1024 ++# ++# However, Debian changed the default security level to 2 in openssl ++# 1.1.1~~pre9-1 (August 2018), which requires a minimum key size of 2048 bit or ++# larger for RSA and DHE keys. To avoid test failures on newer Debian systems ++# against OpenSSL, we must therefore use a key size of at least 2048 bits. ++_KEY_SIZE = 2048 + + def _name(name): + return x509.Name([ diff -Nru python-trustme-0.4.0/debian/patches/series python-trustme-0.4.0/debian/patches/series --- python-trustme-0.4.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ python-trustme-0.4.0/debian/patches/series 2019-04-13 17:25:34.0 +0100 @@ -0,0 +1 @@ +keysize unblock python-trustme/0.4.0-3 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Unblocked python-trustme.--- End Message ---
Bug#926651: marked as done (unblock: nodejs/10.15.2~dfsg-2)
Your message dated Mon, 15 Apr 2019 10:31:47 + with message-id and subject line unblock nodejs has caused the Debian Bug report #926651, regarding unblock: nodejs/10.15.2~dfsg-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.) -- 926651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926651 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 nodejs Two trivial changes: - two tests are marked as flaky (one fails with eatmydata, one fails for no known reason though i suspect it is related to running tests in parallel). - debian/gbp.conf set to debian/buster branch unblock nodejs/10.15.2~dfsg-2 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru nodejs-10.15.2~dfsg/debian/changelog nodejs-10.15.2~dfsg/debian/changelog --- nodejs-10.15.2~dfsg/debian/changelog2019-02-28 15:52:30.0 +0100 +++ nodejs-10.15.2~dfsg/debian/changelog2019-04-08 15:06:40.0 +0200 @@ -1,3 +1,12 @@ +nodejs (10.15.2~dfsg-2) unstable; urgency=medium + + * Avoid two tests to cause a FTBFS (Closes #919588) ++ test-fs-error-messages fails with eatmydata ++ test-net-listen-after-destroying-stdin is flaky + * gbp for debian/buster branch + + -- Jérémy Lal Mon, 08 Apr 2019 15:06:40 +0200 + nodejs (10.15.2~dfsg-1) unstable; urgency=high * New upstream version 10.15.2~dfsg diff -Nru nodejs-10.15.2~dfsg/debian/gbp.conf nodejs-10.15.2~dfsg/debian/gbp.conf --- nodejs-10.15.2~dfsg/debian/gbp.conf 2018-06-11 09:15:16.0 +0200 +++ nodejs-10.15.2~dfsg/debian/gbp.conf 2019-04-08 15:04:57.0 +0200 @@ -2,7 +2,7 @@ [DEFAULT] upstream-branch = upstream-10.x -debian-branch = master-10.x +debian-branch = debian/buster pristine-tar = True sign-tags = True diff -Nru nodejs-10.15.2~dfsg/debian/patches/test_ci_buildd.patch nodejs-10.15.2~dfsg/debian/patches/test_ci_buildd.patch --- nodejs-10.15.2~dfsg/debian/patches/test_ci_buildd.patch 2019-01-30 00:12:11.0 +0100 +++ nodejs-10.15.2~dfsg/debian/patches/test_ci_buildd.patch 2019-04-08 15:02:58.0 +0200 @@ -31,7 +31,7 @@ @echo "Clean up any leftover processes, error if found." --- a/test/parallel/parallel.status +++ b/test/parallel/parallel.status -@@ -8,6 +8,29 @@ +@@ -8,6 +8,35 @@ # https://github.com/nodejs/node/issues/23207 test-net-connect-options-port: PASS,FLAKY @@ -58,10 +58,16 @@ +# might fail, see https://github.com/nodejs/node/issues/17909 +test-fs-utimes: PASS,FLAKY + ++# https://bugs.debian.org/919588 ++## flaky on some user environments ++test-net-listen-after-destroying-stdin: PASS,FLAKY ++## fails when running with eatmydata ++test-fs-error-messages: PASS,FLAKY ++ [$system==win32] test-http2-pipe: PASS,FLAKY test-worker-syntax-error: PASS,FLAKY -@@ -21,6 +44,10 @@ +@@ -21,6 +50,10 @@ # https://github.com/nodejs/node/issues/25028 test-cli-node-options: PASS,FLAKY --- End Message --- --- Begin Message --- Unblocked nodejs.--- End Message ---
Bug#926830: marked as done (unblock: uhubctl/2.0.0-5)
Your message dated Mon, 15 Apr 2019 10:32:50 + with message-id and subject line unblock uhubctl has caused the Debian Bug report #926830, regarding unblock: uhubctl/2.0.0-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.) -- 926830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926830 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 uhubctl Hello release team Recently I've updated the uhubctl package in experimental to fix its autopkgtests which were failing. The upload to experimental which fixed the issue was imported into Ubuntu where it works fine [1] I'd like to have that fix in buster if possible, a debdiff is attached thanks! [1] http://autopkgtest.ubuntu.com/packages/u/uhubctl/disco/amd64 unblock uhubctl/2.0.0-5 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-2-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru uhubctl-2.0.0/debian/changelog uhubctl-2.0.0/debian/changelog --- uhubctl-2.0.0/debian/changelog 2018-09-24 17:25:02.0 +0800 +++ uhubctl-2.0.0/debian/changelog 2019-04-10 16:30:47.0 +0800 @@ -1,3 +1,19 @@ +uhubctl (2.0.0-5) unstable; urgency=medium + + * Upload to unstable. + + -- gustavo panizzo Wed, 10 Apr 2019 16:30:47 +0800 + +uhubctl (2.0.0-4) experimental; urgency=medium + + [ Ondřej Nový ] + * d/control: Add Vcs-* field + + [ gustavo panizzo ] + * [fc94ec] Fix autopkgtest + + -- gustavo panizzo Wed, 03 Apr 2019 09:34:35 +0800 + uhubctl (2.0.0-3) unstable; urgency=medium * [f88227] Fix autopkgtests diff -Nru uhubctl-2.0.0/debian/control uhubctl-2.0.0/debian/control --- uhubctl-2.0.0/debian/control2018-09-24 17:25:02.0 +0800 +++ uhubctl-2.0.0/debian/control2019-04-01 10:14:07.0 +0800 @@ -5,6 +5,8 @@ Build-Depends: debhelper (>= 11.0.0), libusb-1.0-0-dev, autopkgtest Standards-Version: 4.2.1 Homepage: https://github.com/mvp/uhubctl +Vcs-Browser: https://salsa.debian.org/debian/uhubctl +Vcs-Git: https://salsa.debian.org/debian/uhubctl.git Package: uhubctl Architecture: any diff -Nru uhubctl-2.0.0/debian/tests/control uhubctl-2.0.0/debian/tests/control --- uhubctl-2.0.0/debian/tests/control 2018-09-24 17:25:02.0 +0800 +++ uhubctl-2.0.0/debian/tests/control 2019-04-02 17:06:31.0 +0800 @@ -1 +1,2 @@ Tests: run-uhubctl-v +Depends: @ diff -Nru uhubctl-2.0.0/debian/tests/run-uhubctl-v uhubctl-2.0.0/debian/tests/run-uhubctl-v --- uhubctl-2.0.0/debian/tests/run-uhubctl-v2018-09-24 17:25:02.0 +0800 +++ uhubctl-2.0.0/debian/tests/run-uhubctl-v2019-04-03 00:46:36.0 +0800 @@ -4,4 +4,4 @@ set -e -./uhubctl -v +uhubctl -v --- End Message --- --- Begin Message --- Unblocked uhubctl.--- End Message ---
Re: Summary of the Arm ports BoF at DC18
On Sun, Apr 14, 2019 at 09:06:06PM -0300, Antonio Terceiro wrote: > can you please add Paul? I signed up, but never had the bandwidth to > actually do anything, and now with DebConf getting closer I will have > even less time. ACK, done. > BTW Amazon also has arm64 instances now so maybe it would be easier to > use those instead. I thought one goal was also to avoid being excessively tied to a single provider? -- 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
Bug#927121: unblock: glusterfs/5.5-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package glusterfs
It adds one upstream patch - which is now in the 5.6 release - to fix this
critical
bug: https://bugzilla.redhat.com/show_bug.cgi?id=1673058
See also: https://review.gluster.org/#/c/glusterfs/+/22404/
diff -Naur '--exclude=.svn' 5.5-2/debian/changelog 5.5-3/debian/changelog
--- 5.5-2/debian/changelog 2019-04-09 13:47:11.558039914 +0200
+++ 5.5-3/debian/changelog 2019-04-15 10:23:28.871148221 +0200
@@ -1,3 +1,10 @@
+glusterfs (5.5-3) unstable; urgency=medium
+
+ * Add upstream patch 05-client-rpc-payload-wire to fix the payload being sent
+on the wire.
+
+ -- Patrick Matthäi Mon, 15 Apr 2019 10:07:38 +0200
+
glusterfs (5.5-2) unstable; urgency=medium
* Uploading to unstable.
diff -Naur '--exclude=.svn'
5.5-2/debian/patches/05-client-rpc-payload-wire.diff
5.5-3/debian/patches/05-client-rpc-payload-wire.diff
--- 5.5-2/debian/patches/05-client-rpc-payload-wire.diff1970-01-01
01:00:00.0 +0100
+++ 5.5-3/debian/patches/05-client-rpc-payload-wire.diff2019-04-15
10:23:28.943147770 +0200
@@ -0,0 +1,1619 @@
+commit 1fba86169b0850c3fcd02e56d0ddbba3efe9ae78
+Author: Poornima G
+Date: Sun Mar 24 09:40:50 2019 +0530
+
+client-rpc: Fix the payload being sent on the wire
+
+The fops allocate 3 kind of payload(buffer) in the client xlator:
+- fop payload, this is the buffer allocated by the write and put fop
+- rsphdr paylod, this is the buffer required by the reply cbk of
+ some fops like lookup, readdir.
+- rsp_paylod, this is the buffer required by the reply cbk of fops like
+ readv etc.
+
+Currently, in the lookup and readdir fop the rsphdr is sent as payload,
+hence the allocated rsphdr buffer is also sent on the wire, increasing
+the bandwidth consumption on the wire.
+
+With this patch, the issue is fixed.
+
+Fixes: bz#1673058
+Change-Id: Ie8158921f4db319e60ad5f52d851fa5c9d4a269b
+Signed-off-by: Poornima G
+
+diff --git a/xlators/protocol/client/src/client-handshake.c
b/xlators/protocol/client/src/client-handshake.c
+index ed9d0a5d9..e1334f9e3 100644
+--- a/xlators/protocol/client/src/client-handshake.c
b/xlators/protocol/client/src/client-handshake.c
+@@ -34,7 +34,6 @@ typedef struct client_fd_lk_local {
+ clnt_fd_ctx_t *fdctx;
+ } clnt_fd_lk_local_t;
+
+-
+ int32_t
+ client3_getspec(call_frame_t *frame, xlator_t *this, void *data)
+ {
+@@ -201,8 +200,8 @@ clnt_release_reopen_fd(xlator_t *this, clnt_fd_ctx_t
*fdctx)
+ req.fd = fdctx->remote_fd;
+
+ ret = client_submit_request(this, &req, frame, conf->fops,
GFS3_OP_RELEASE,
+-clnt_release_reopen_fd_cbk, NULL, NULL, 0,
NULL,
+-0, NULL, (xdrproc_t)xdr_gfs3_releasedir_req);
++clnt_release_reopen_fd_cbk, NULL,
++(xdrproc_t)xdr_gfs3_releasedir_req);
+ out:
+ if (ret) {
+ clnt_fd_lk_reacquire_failed(this, fdctx, conf);
+@@ -486,8 +485,8 @@ protocol_client_reopendir(clnt_fd_ctx_t *fdctx, xlator_t
*this)
+ frame->local = local;
+
+ ret = client_submit_request(this, &req, frame, conf->fops,
GFS3_OP_OPENDIR,
+-client3_3_reopendir_cbk, NULL, NULL, 0, NULL,
0,
+-NULL, (xdrproc_t)xdr_gfs3_opendir_req);
++client3_3_reopendir_cbk, NULL,
++(xdrproc_t)xdr_gfs3_opendir_req);
+ if (ret) {
+ gf_msg(this->name, GF_LOG_ERROR, 0, PC_MSG_DIR_OP_FAILED,
+"failed to send the re-opendir request");
+@@ -547,8 +546,8 @@ protocol_client_reopenfile(clnt_fd_ctx_t *fdctx, xlator_t
*this)
+ local->loc.path);
+
+ ret = client_submit_request(this, &req, frame, conf->fops, GFS3_OP_OPEN,
+-client3_3_reopen_cbk, NULL, NULL, 0, NULL, 0,
+-NULL, (xdrproc_t)xdr_gfs3_open_req);
++client3_3_reopen_cbk, NULL,
++(xdrproc_t)xdr_gfs3_open_req);
+ if (ret) {
+ gf_msg(this->name, GF_LOG_ERROR, 0, PC_MSG_DIR_OP_FAILED,
+"failed to send the re-open request");
+@@ -745,8 +744,8 @@ protocol_client_reopendir_v2(clnt_fd_ctx_t *fdctx,
xlator_t *this)
+ frame->local = local;
+
+ ret = client_submit_request(this, &req, frame, conf->fops,
GFS3_OP_OPENDIR,
+-client4_0_reopendir_cbk, NULL, NULL, 0, NULL,
0,
+-NULL, (xdrproc_t)xdr_gfx_opendir_req);
++client4_0_reopendir_cbk, NULL,
++(xdrproc_t)xdr_gfx_opendir_req);
+ if (ret) {
+ gf_msg(this->name, GF_LOG_ERROR, 0, PC_MSG_DIR_OP_FAILED,
+"failed to send the re-opend
Bug#927119: unblock: apt-dater/1.0.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package apt-dater. It adds missing README.* files and fixes a bug, where you can not create new sessions, because of an old deprecated configuration for tmux. diff -Naur '--exclude=.svn' 1.0.4-1/debian/apt-dater.docs 1.0.4-2/debian/apt-dater.docs --- 1.0.4-1/debian/apt-dater.docs 2019-02-11 10:58:30.644694694 +0100 +++ 1.0.4-2/debian/apt-dater.docs 2019-04-15 10:23:54.946984935 +0200 @@ -1,3 +1,2 @@ README -README.tclfilter -README.xmlreport +README.* diff -Naur '--exclude=.svn' 1.0.4-1/debian/changelog 1.0.4-2/debian/changelog --- 1.0.4-1/debian/changelog2019-02-11 10:58:30.624694772 +0100 +++ 1.0.4-2/debian/changelog2019-04-15 10:23:54.906985186 +0200 @@ -1,3 +1,12 @@ +apt-dater (1.0.4-2) unstable; urgency=medium + + * Install missing docs. +Closes: #924176 + * Add patch 01-tmux-options to fix an error with tmux 2.4, because of an old +invalid option. + + -- Patrick Matthäi Mon, 15 Apr 2019 10:07:25 +0200 + apt-dater (1.0.4-1) unstable; urgency=medium * New upstream release. diff -Naur '--exclude=.svn' 1.0.4-1/debian/patches/01-tmux-options.diff 1.0.4-2/debian/patches/01-tmux-options.diff --- 1.0.4-1/debian/patches/01-tmux-options.diff 1970-01-01 01:00:00.0 +0100 +++ 1.0.4-2/debian/patches/01-tmux-options.diff 2019-04-15 10:23:54.906985186 +0200 @@ -0,0 +1,15 @@ +# tmux 2.4 changed this option, we need it for new created sessions +# or tmux will fail with an unknown option error. + +diff -Naur apt-dater-1.0.4.orig/conf/tmux.conf apt-dater-1.0.4/conf/tmux.conf +--- apt-dater-1.0.4.orig/conf/tmux.conf2019-02-10 22:16:03.0 +0100 apt-dater-1.0.4/conf/tmux.conf 2019-04-15 10:02:11.499131926 +0200 +@@ -11,7 +11,7 @@ + set -g terminal-overrides 'xterm*:smcup@:rmcup@' + + set-option -g history-limit 1 +-set-option -g set-remain-on-exit on ++set-hook -g session-created 'set remain-on-exit on' + + # Make C-a q kill the pane (simular to GNU screen) + bind-key q confirm-before -p "kill-pane #P? (y/n)" kill-pane diff -Naur '--exclude=.svn' 1.0.4-1/debian/patches/series 1.0.4-2/debian/patches/series --- 1.0.4-1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ 1.0.4-2/debian/patches/series 2019-04-15 10:23:54.906985186 +0200 @@ -0,0 +1 @@ +01-tmux-options.diff unblock apt-dater/1.0.4-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#927118: unblock: python-trustme/0.4.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-trustme This fixes a second FTBFS, further to the previous unblock request in bug 925576. This time the build failed on the buildds but not in my local testing because openssl was installed there, which (correctly) isn't a build dependency. The fix is to generate larger keys. The same change has now been accepted by upstream. diff -Nru python-trustme-0.4.0/debian/changelog python-trustme-0.4.0/debian/changelog --- python-trustme-0.4.0/debian/changelog 2018-10-13 22:48:59.0 +0100 +++ python-trustme-0.4.0/debian/changelog 2019-04-13 17:30:43.0 +0100 @@ -1,3 +1,19 @@ +python-trustme (0.4.0-3) unstable; urgency=medium + + * d/p/keysize: bump test key sizes to 2048 to fulfil Debian's new default +requirement. This fixes another FTBFS due to test failure in the case that +the openssl binary package is installed, which is not a build dependency, +but apparently the buildds have it by default. Closes: #926652. + + -- Robie Basak Sat, 13 Apr 2019 17:30:20 +0100 + +python-trustme (0.4.0-2) unstable; urgency=medium + + * Explicitly build-depend on python3-idna to fix FTBFS. +Closes: #925566. + + -- Robie Basak Tue, 26 Mar 2019 23:22:42 + + python-trustme (0.4.0-1) unstable; urgency=low * Initial release. Closes: #910951. diff -Nru python-trustme-0.4.0/debian/control python-trustme-0.4.0/debian/control --- python-trustme-0.4.0/debian/control 2018-10-13 22:48:59.0 +0100 +++ python-trustme-0.4.0/debian/control 2019-04-13 17:22:21.0 +0100 @@ -6,6 +6,7 @@ Build-Depends: debhelper (>= 9~), dh-python, python3, + python3-idna, python3-openssl, python3-pytest, python3-service-identity, diff -Nru python-trustme-0.4.0/debian/patches/keysize python-trustme-0.4.0/debian/patches/keysize --- python-trustme-0.4.0/debian/patches/keysize 1970-01-01 01:00:00.0 +0100 +++ python-trustme-0.4.0/debian/patches/keysize 2019-04-13 17:26:01.0 +0100 @@ -0,0 +1,33 @@ +From 96b8799325fa0f53fad4db529cbd2d25af42ebff Mon Sep 17 00:00:00 2001 +From: Robie Basak +Date: Sat, 13 Apr 2019 17:02:53 +0100 +Subject: [PATCH] Increase key size to 2048 bits + +Debian changed the default security level to 2 since openssl package +version 1.1.1~~pre9-1 (August 2018), which requires a minimum key size +of 2048 bit or larger RSA and DHE keys. To avoid test failures on newer +Debian systems against OpenSSL, use a key size of at least 2048 bits. + +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926652 +Forwarded: https://github.com/python-trio/trustme/pull/45 +Last-Update: 2019-04-13 +--- + trustme/__init__.py | 7 ++- + 1 file changed, 6 insertions(+), 1 deletion(-) + +--- a/trustme/__init__.py b/trustme/__init__.py +@@ -33,7 +33,12 @@ + # On my laptop, making a CA + server certificate using 1024 bit keys takes ~40 + # ms, and using 4096 bit keys takes ~2 seconds. We want tests to run in 40 ms, + # not 2 seconds. +-_KEY_SIZE = 1024 ++# ++# However, Debian changed the default security level to 2 in openssl ++# 1.1.1~~pre9-1 (August 2018), which requires a minimum key size of 2048 bit or ++# larger for RSA and DHE keys. To avoid test failures on newer Debian systems ++# against OpenSSL, we must therefore use a key size of at least 2048 bits. ++_KEY_SIZE = 2048 + + def _name(name): + return x509.Name([ diff -Nru python-trustme-0.4.0/debian/patches/series python-trustme-0.4.0/debian/patches/series --- python-trustme-0.4.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ python-trustme-0.4.0/debian/patches/series 2019-04-13 17:25:34.0 +0100 @@ -0,0 +1 @@ +keysize unblock python-trustme/0.4.0-3 signature.asc Description: PGP signature
NEW changes in stable-new
Processing changes file: ca-certificates-java_20170929~deb9u3_all.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_amd64.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_arm64.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_armel.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_armhf.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_i386.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_mips.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_mips64el.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_mipsel.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_ppc64el.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_s390x.changes ACCEPT Processing changes file: perlbrew_0.78-1+deb9u1_all.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_all.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_amd64.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_arm64.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_armel.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_armhf.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_i386.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_mips.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_mips64el.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_mipsel.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_ppc64el.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_s390x.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_all.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_amd64.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_arm64.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_armel.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_armhf.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_i386.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_ppc64el.changes ACCEPT
Processed: retitle 926048 to RM: tbdialout -- RoQA; incompatible with newer thunderbird versions, tagging 926048
Processing commands for cont...@bugs.debian.org: > retitle 926048 RM: tbdialout -- RoQA; incompatible with newer thunderbird > versions Bug #926048 [release.debian.org] RM: tbdialout/1.7.2-1+deb9u1 Changed Bug title to 'RM: tbdialout -- RoQA; incompatible with newer thunderbird versions' from 'RM: tbdialout/1.7.2-1+deb9u1'. > tags 926048 + pending Bug #926048 [release.debian.org] RM: tbdialout -- RoQA; incompatible with newer thunderbird versions Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 926048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 925504 to RM: timeline -- RoQA; incompatible with newer thunderbird versions, tagging 925504
Processing commands for cont...@bugs.debian.org: > retitle 925504 RM: timeline -- RoQA; incompatible with newer thunderbird > versions Bug #925504 [release.debian.org] RM: timeline/0.5-4 Changed Bug title to 'RM: timeline -- RoQA; incompatible with newer thunderbird versions' from 'RM: timeline/0.5-4'. > tags 925504 + pending Bug #925504 [release.debian.org] RM: timeline -- RoQA; incompatible with newer thunderbird versions Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 925504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 926830
Processing commands for cont...@bugs.debian.org:
> reopen 926830
Bug #926830 {Done: Niels Thykier } [release.debian.org]
unblock: uhubctl/2.0.0-5
Bug reopened
Ignoring request to alter fixed versions of bug #926830 to the same values
previously set
> tags 926830 - moreinfo
Bug #926830 [release.debian.org] unblock: uhubctl/2.0.0-5
Ignoring request to alter tags of bug #926830 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: ca-certificates-java_20170929~deb9u3_source.changes ACCEPT Processing changes file: ckermit_302-5.3+deb9u1_source.changes ACCEPT Processing changes file: perlbrew_0.78-1+deb9u1_sourceonly.changes ACCEPT Processing changes file: postfix_3.1.12-0+deb9u1_source.changes ACCEPT Processing changes file: runc_0.1.1+dfsg1-2+deb9u1_source.changes ACCEPT Processing changes file: linux_4.9.168-1_mips.changes ACCEPT
Processed: tagging 926651
Processing commands for cont...@bugs.debian.org: > tags 926651 - moreinfo Bug #926651 [release.debian.org] unblock: nodejs/10.15.2~dfsg-2 Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 926651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ckermit 302-5.3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #919043 [release.debian.org] stretch-pu: ckermit/302-5.3+deb9u1 Ignoring request to alter tags of bug #919043 to the same tags previously set -- 919043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914591: stretch-pu: package python-cryptography/1.7.1-3
Control: tags -1 + confirmed On Mon, 2019-04-15 at 08:30 +0200, Sebastian Andrzej Siewior wrote: > On 2019-04-14 21:08:46 [+0100], Adam D. Barratt wrote: > > On Sun, 2018-11-25 at 13:49 +0100, Sebastian Andrzej Siewior wrote: > > > With the intention of pushing OpenSSL 1.1.0j into Stretch here is > > > the > > > proposed change for python-cryptography. > > > The package python-cryptography fails to build due to an API > > > change > > > of BIO_callback_ctrl() in OpenSSL. While this is a no-no in a > > > stable > > > release, it has been explained [0] that the function / callback > > > was > > > always used with a different prototype. I fixed this by removing > > > the > > > function / prototype from the python wrapper while upstream > > > removed > > > the almost all BIO related wrappers [1]. > > > I did a rebuild of python-cryptography's rdeps in Stretch against > > > OpenSSL 1.1.0i and the proposed package with no fallout [2]. > > > > Just to be 100% sure on the scope here, those rebuilds were just > > for > > confirmation? i.e. they are not required if we go ahead. > > Excatly. I just wanted to makes sure that this change (this update of > python-cryptography) did not break any of its users / reverse > dependecies. OK, thanks for the confirmation. Please go ahead. Regards, Adam
Processed: Re: Bug#914591: stretch-pu: package python-cryptography/1.7.1-3
Processing control commands: > tags -1 + confirmed Bug #914591 [release.debian.org] stretch-pu: package python-cryptography/1.7.1-3 Added tag(s) confirmed. -- 914591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ca-certificates-java 20170929~deb9u3 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926870 [release.debian.org] stretch-pu: package ca-certificates-java/20170929~deb9u2 Ignoring request to alter tags of bug #926870 to the same tags previously set -- 926870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: runc 0.1.1+dfsg1-2+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #924939 [release.debian.org] stretch-pu: package runc/0.1.1+dfsg1-2+deb9u1 Ignoring request to alter tags of bug #924939 to the same tags previously set -- 924939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926870: ca-certificates-java 20170929~deb9u3 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: ca-certificates-java Version: 20170929~deb9u3 Explanation: fix printf syntax problem introduced in 20170929~deb9u2
Processed: ca-certificates-java 20170929~deb9u3 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926870 [release.debian.org] stretch-pu: package ca-certificates-java/20170929~deb9u2 Added tag(s) pending. -- 926870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924939: runc 0.1.1+dfsg1-2+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: runc Version: 0.1.1+dfsg1-2+deb9u1 Explanation: security fix [CVE-2019-5736]
Bug#926190: postfix 3.1.12-0+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: postfix Version: 3.1.12-0+deb9u1 Explanation: new upstream stable release
Bug#927067: perlbrew 0.78-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: perlbrew Version: 0.78-1+deb9u1 Explanation: allow HTTPS CPAN URLs
Processed: postfix 3.1.12-0+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926190 [release.debian.org] stretch-pu: package postfix/3.1.12-0+deb9u1 Added tag(s) pending. -- 926190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: perlbrew 0.78-1+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927067 [release.debian.org] stretch-pu: package perlbrew/0.78-1+deb9u1 Ignoring request to alter tags of bug #927067 to the same tags previously set -- 927067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: runc 0.1.1+dfsg1-2+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #924939 [release.debian.org] stretch-pu: package runc/0.1.1+dfsg1-2+deb9u1 Added tag(s) pending. -- 924939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: perlbrew 0.78-1+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #927067 [release.debian.org] stretch-pu: package perlbrew/0.78-1+deb9u1 Added tag(s) pending. -- 927067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: postfix 3.1.12-0+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926190 [release.debian.org] stretch-pu: package postfix/3.1.12-0+deb9u1 Ignoring request to alter tags of bug #926190 to the same tags previously set -- 926190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919043: ckermit 302-5.3+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: ckermit Version: 302-5.3+deb9u1 Explanation: drop OpenSSL version check
Processed: ckermit 302-5.3+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #919043 [release.debian.org] stretch-pu: ckermit/302-5.3+deb9u1 Added tag(s) pending. -- 919043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927107: marked as done (unblock: openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12)
Your message dated Mon, 15 Apr 2019 07:22:00 +
with message-id
and subject line Re: Bug#927107: unblock:
openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
has caused the Debian Bug report #927107,
regarding unblock: openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
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.)
--
927107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927107
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 openvswitch
As per the one liner attached debdiff, this Debian release -12 fixes
the debian/ifupdown.sh script which ends up in:
/etc/network/if-{pre-up,post-down}.d/openvswitch
When using an OVSBond interface, the script wasn't using --may-exist,
and as a consequence, may fail setting-up network interfaces in case
the bond already exists.
Note that the same change was commited upstream recently.
unblock openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
2019-03-31 00:50:26.0 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
2019-04-14 00:25:19.0 +0200
@@ -1,3 +1,10 @@
+openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12) unstable; urgency=medium
+
+ * Add --may-exist in debian/ifupdown.sh as per upstream commit. Without it,
+networking service may fail (Closes: #926942).
+
+ -- Thomas Goirand Sun, 14 Apr 2019 00:25:19 +0200
+
openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-11) unstable; urgency=medium
* Removes network.service from openvswitch-switch.service to avoid a
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
2019-03-31 00:50:26.0 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
2019-04-14 00:25:19.0 +0200
@@ -67,7 +67,7 @@
ip link set "${IFACE}" up
;;
OVSBond)
-ovs_vsctl -- --fake-iface add-bond "${IF_OVS_BRIDGE}"\
+ovs_vsctl -- --fake-iface --may-exist add-bond
"${IF_OVS_BRIDGE}"\
"${IFACE}" ${IF_OVS_BONDS} ${IF_OVS_OPTIONS} \
${OVS_EXTRA+-- $OVS_EXTRA}
--- End Message ---
--- Begin Message ---
Thomas Goirand:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package openvswitch
>
> As per the one liner attached debdiff, this Debian release -12 fixes
> the debian/ifupdown.sh script which ends up in:
> /etc/network/if-{pre-up,post-down}.d/openvswitch
>
> When using an OVSBond interface, the script wasn't using --may-exist,
> and as a consequence, may fail setting-up network interfaces in case
> the bond already exists.
>
> Note that the same change was commited upstream recently.
>
> unblock openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
>
Unblocked, thanks.
~Niels--- End Message ---
Bug#927111: unblock: wpa/2:2.7+git20190128+0c1e29f-4
Control: tags -1 d-i confirmed Andrej Shadura: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock the package wpa. > > This upload fixes a security vulnerability in WPA3-Personal and EAP (#926801): > > - CVE-2019-9494: SAE cache attack against ECC groups (VU#871675) > - CVE-2019-9495: EAP-pwd cache attack against ECC groups > - CVE-2019-9496: SAE confirm missing state validation > - CVE-2019-9497: EAP-pwd server not checking for reflection attack > - CVE-2019-9498: EAP-pwd server missing commit validation for scalar/element > - CVE-2019-9499: EAP-pwd peer missing commit validation for scalar/element > > For more details on the vulnerability itself, see: > - https://w1.fi/security/2019-1/ > - https://w1.fi/security/2019-2/ > - https://w1.fi/security/2019-3/ > - https://w1.fi/security/2019-4/ > > Since the patches are quite big, you can check them here: > - > https://salsa.debian.org/debian/wpa/tree/debian/master/debian/patches/2019-sae-eap > - > https://sources.debian.org/src/wpa/2:2.7+git20190128+0c1e29f-4/debian/patches/2019-sae-eap/ > > Erroneously not mentioned in the changelog, this upload also declares a > correct > build dependency on libnl-3-dev. > > unblock wpa/2:2.7+git20190128+0c1e29f-4 > Hi, Thanks for filing this unblock. From a RT PoV it looks fine and I have Cc'ed KiBi for a d-i ack before accepting it fully. Thanks, ~Niels
Processed: Re: Bug#927111: unblock: wpa/2:2.7+git20190128+0c1e29f-4
Processing control commands: > tags -1 d-i confirmed Bug #927111 [release.debian.org] unblock: wpa/2:2.7+git20190128+0c1e29f-4 Added tag(s) d-i and confirmed. -- 927111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927110: marked as done (unblock: python-darkslide/4.0.1-2)
Your message dated Mon, 15 Apr 2019 07:21:00 + with message-id and subject line Re: Bug#927110: unblock: python-darkslide/4.0.1-2 has caused the Debian Bug report #927110, regarding unblock: python-darkslide/4.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.) -- 927110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927110 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 the package python-darkslide. This upload fixes a bug which prevented darkslide from doing having any useful functionality in buster: $ darkslide slides.md Adding 'slides.md' (markdown) Error: markdown() takes 1 positional argument but 2 were given For more information about the bug, see https://bugs.debian.org/923977. The debdiff is attached for your reference. unblock python-darkslide/4.0.1-2 -- Cheers, Andrej diff --git a/debian/changelog b/debian/changelog index 6f748d7..7f718d2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +python-darkslide (4.0.1-2) unstable; urgency=medium + + * Support python-markdown >= 3 (Closes: #923977). + * Bump the python3-markdown build dependency. + + -- Andrej Shadura Sat, 13 Apr 2019 00:10:51 +0200 + python-darkslide (4.0.1-1) unstable; urgency=medium [ Ondřej Nový ] diff --git a/debian/control b/debian/control index ea38679..e874172 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: python3-all, python3-setuptools (>= 0.6.24), python3-six, -python3-markdown, +python3-markdown (>= 3.0), python3-jinja2, python3-pygments, python3-docutils, diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..95d3385 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +support-markdown3.patch diff --git a/debian/patches/support-markdown3.patch b/debian/patches/support-markdown3.patch new file mode 100644 index 000..a4e134d --- /dev/null +++ b/debian/patches/support-markdown3.patch @@ -0,0 +1,18 @@ +Subject: extensions is now a named argument to markdown() +From: Andrej Shadura + +Bug: https://github.com/ionelmc/python-darkslide/issues/10 +Bug-Debian: https://bugs.debian.org/923977 +Forwarded: not-needed + +--- a/src/darkslide/parser.py b/src/darkslide/parser.py +@@ -57,7 +57,7 @@ + if text.startswith(u'\ufeff'): # check for unicode BOM + text = text[1:] + +-return markdown.markdown(text, self.md_extensions) ++return markdown.markdown(text, extensions=self.md_extensions) + elif self.format == 'restructuredtext': + try: + from .rst import html_body --- End Message --- --- Begin Message --- Andrej Shadura: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock the package python-darkslide. > > This upload fixes a bug which prevented darkslide from doing having any useful > functionality in buster: > > $ darkslide slides.md > Adding 'slides.md' (markdown) > Error: markdown() takes 1 positional argument but 2 were given > > For more information about the bug, see https://bugs.debian.org/923977. > The debdiff is attached for your reference. > > unblock python-darkslide/4.0.1-2 > Unblocked, thanks. ~Niels--- End Message ---
Bug#927111: unblock: wpa/2:2.7+git20190128+0c1e29f-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the package wpa. This upload fixes a security vulnerability in WPA3-Personal and EAP (#926801): - CVE-2019-9494: SAE cache attack against ECC groups (VU#871675) - CVE-2019-9495: EAP-pwd cache attack against ECC groups - CVE-2019-9496: SAE confirm missing state validation - CVE-2019-9497: EAP-pwd server not checking for reflection attack - CVE-2019-9498: EAP-pwd server missing commit validation for scalar/element - CVE-2019-9499: EAP-pwd peer missing commit validation for scalar/element For more details on the vulnerability itself, see: - https://w1.fi/security/2019-1/ - https://w1.fi/security/2019-2/ - https://w1.fi/security/2019-3/ - https://w1.fi/security/2019-4/ Since the patches are quite big, you can check them here: - https://salsa.debian.org/debian/wpa/tree/debian/master/debian/patches/2019-sae-eap - https://sources.debian.org/src/wpa/2:2.7+git20190128+0c1e29f-4/debian/patches/2019-sae-eap/ Erroneously not mentioned in the changelog, this upload also declares a correct build dependency on libnl-3-dev. unblock wpa/2:2.7+git20190128+0c1e29f-4 -- Cheers, Andrej
Bug#927110: unblock: python-darkslide/4.0.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the package python-darkslide. This upload fixes a bug which prevented darkslide from doing having any useful functionality in buster: $ darkslide slides.md Adding 'slides.md' (markdown) Error: markdown() takes 1 positional argument but 2 were given For more information about the bug, see https://bugs.debian.org/923977. The debdiff is attached for your reference. unblock python-darkslide/4.0.1-2 -- Cheers, Andrej diff --git a/debian/changelog b/debian/changelog index 6f748d7..7f718d2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +python-darkslide (4.0.1-2) unstable; urgency=medium + + * Support python-markdown >= 3 (Closes: #923977). + * Bump the python3-markdown build dependency. + + -- Andrej Shadura Sat, 13 Apr 2019 00:10:51 +0200 + python-darkslide (4.0.1-1) unstable; urgency=medium [ Ondřej Nový ] diff --git a/debian/control b/debian/control index ea38679..e874172 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: python3-all, python3-setuptools (>= 0.6.24), python3-six, -python3-markdown, +python3-markdown (>= 3.0), python3-jinja2, python3-pygments, python3-docutils, diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..95d3385 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +support-markdown3.patch diff --git a/debian/patches/support-markdown3.patch b/debian/patches/support-markdown3.patch new file mode 100644 index 000..a4e134d --- /dev/null +++ b/debian/patches/support-markdown3.patch @@ -0,0 +1,18 @@ +Subject: extensions is now a named argument to markdown() +From: Andrej Shadura + +Bug: https://github.com/ionelmc/python-darkslide/issues/10 +Bug-Debian: https://bugs.debian.org/923977 +Forwarded: not-needed + +--- a/src/darkslide/parser.py b/src/darkslide/parser.py +@@ -57,7 +57,7 @@ + if text.startswith(u'\ufeff'): # check for unicode BOM + text = text[1:] + +-return markdown.markdown(text, self.md_extensions) ++return markdown.markdown(text, extensions=self.md_extensions) + elif self.format == 'restructuredtext': + try: + from .rst import html_body
