Bug#926048: marked as done (RM: tbdialout/1.7.2-1+deb9u1)
Your message dated Sun, 31 Mar 2019 07:30:28 +0200 with message-id and subject line Re: Bug#926048: RM: tbdialout/1.7.2-1+deb9u1 has caused the Debian Bug report #926048, regarding RM: tbdialout/1.7.2-1+deb9u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926048 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: rm This extension is broken with Thunderbird 60 and was already removed from sid. Cheers, Moritz --- End Message --- --- Begin Message --- Hi Moritz, On 30-03-2019 22:33, Moritz Muehlenhoff wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > > This extension is broken with Thunderbird 60 and was already removed from sid. I assume you know that removals from sid are (normally) tracked in testing. If I now look with rmadison the package is indeed gone. Was there any particular reason why you thought this needed manual attention, or is my assumption plain wrong? Paul paul@testavoira ~ $ rmadison tbdialout tbdialout | 1.7.2-1| oldstable | source tbdialout | 1.7.2-1+deb9u1 | stable | source signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#926053: unblock: firefox-esr/60.6.1esr-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package firefox-esr. It upgrades to the latest 60 ESR release, including a few security fixes. unblock firefox-esr/60.6.1esr-1 Cheers, Moritz
Bug#926052: unblock: python-pip/18.1-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-pip The version 18.1-5 includes a fix so that using the --extra-index-url option of pip doesn't result in a "HTTPError: 404 Client Error: NOT FOUND". Note that the bug is Debian specific, and is due to the way upstream calls the requests module, which fails if the requests module is de-vendored / de-embedded from pip, which is what has been done in Debian. Bellow, inline in the body of this mail (sorry, I should have made it an attachment, maybe?) is the debdiff for the package. Note that the changes to the "hands-off-system-packages.patch" may be ignore, it's just produced by a "quilt refresh" of the patch. Reading it, you'll notice that the only thing that changes is the way "except HTTPError as exc:" is done, using the imported "HTTPError" from pip._vendor.requests.exceptions rather than from requests.HTTPError which fails. Note that this bug deeply impacts the OpenStack CI/CD system which deeply relies on pip and the --extra-index-url, which is why I care a lot for this patch to go through. Please unblock python-pip/18.1-5. Cheers, Thomas Goirand (zigo) diff -Nru python-pip-18.1/debian/changelog python-pip-18.1/debian/changelog --- python-pip-18.1/debian/changelog2019-01-03 17:38:22.0 +0100 +++ python-pip-18.1/debian/changelog2019-03-30 21:10:13.0 +0100 @@ -1,3 +1,15 @@ +python-pip (18.1-5) unstable; urgency=medium + + * Team upload. + * Refresh hands-off-system-packages.patch. + * Add Properly_catch_requests_HTTPError_in_index.py.patch: this fixes 404 +when using --extra-index-url due to the way we de-bundle python-requests +from pip. Thanks to Fabio Natali for the bug report, +Clark Boylan for the patch, and all of the OpenStack infra team for their +help and involving me for this fix (Closes: #837764). + + -- Thomas Goirand Sat, 30 Mar 2019 21:10:13 +0100 + python-pip (18.1-4) unstable; urgency=medium * Generate Built-Using at the build time (Closes: #831271). diff -Nru python-pip-18.1/debian/patches/hands-off-system-packages.patch python-pip-18.1/debian/patches/hands-off-system-packages.patch --- python-pip-18.1/debian/patches/hands-off-system-packages.patch 2019-01-03 17:38:22.0 +0100 +++ python-pip-18.1/debian/patches/hands-off-system-packages.patch 2019-03-30 21:10:13.0 +0100 @@ -17,17 +17,18 @@ Patch-Name: hands-off-system-packages.patch --- a/src/pip/_internal/utils/misc.py -+++ b/src/pip/_internal/utils/misc.py -@@ -285,22 +285,40 @@ +Index: python-pip/src/pip/_internal/utils/misc.py +=== +--- python-pip.orig/src/pip/_internal/utils/misc.py python-pip/src/pip/_internal/utils/misc.py +@@ -289,22 +289,40 @@ def renames(old, new): def is_local(path): """ -Return True if path is within sys.prefix, if we're running in a virtualenv. -- --If we're not in a virtualenv, all paths are considered "local." +Return True if this is a path pip is allowed to modify. -+ + +-If we're not in a virtualenv, all paths are considered "local." +If we're in a virtualenv, sys.prefix points to the virtualenv's +prefix; only sys.prefix is considered local. + diff -Nru python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch --- python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch 1970-01-01 01:00:00.0 +0100 +++ python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch 2019-03-30 21:10:13.0 +0100 @@ -0,0 +1,47 @@ +Description: Properly catch requests' HTTPError in index.py + This resolves issue #4195. + . + In index.py's index retrieval routine we were catching + requests.HTTPError to log and ignore 404s and other similar HTTP server + errors when pulling from (extra-)index-urls. Unfortunately, the actual + path to that exception is requests.exceptions.HTTPError and the alias we + were using does not work when pip is installed with unvendored libs as + with the debian packaged pip. + . + Thankfully the fix is simple. Import and use + requests.exceptions.HTTPError. This comes with the added bonus of + fitting in with the existing handling for RetryError and SSLError. With + this change in place upstream pip and downstream packaged pip should + both catch this exception properly. + . + Note: I've not added any tests cases as I'm unsure how to test the + distro packaging case within pip's testsuite. However, the existing test + suite should hopefully cover that this isn't a regression and I've + manually confirmed that this works with a hacked up debian package + install. Also this is how we handle RetryError and SSLError. +Author: Clark Boylan +Date: Fri, 29 Mar 2019 10:17:31 -0700 +Origin:
Bug#926050: stretch-pu: package python-pip/9.0.1-2+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Dear release team,
I would like to upload a fix to python-pip to Stretch, fixing pip download
when using --extra-index-url. Pip is indeed broken because of the way pip
handles exceptions from the vendored requests module, and the way Debian
de-embbed requests. The patch is pretty short (2 lines are changed).
Debdiff is attached.
Please allow me to upload python-pip/9.0.1-2+deb9u1 to stretch PU.
Cheers,
Thomas Goirand (zigo)
diff -Nru python-pip-9.0.1/debian/changelog python-pip-9.0.1/debian/changelog
--- python-pip-9.0.1/debian/changelog 2017-01-11 21:48:53.0 +0100
+++ python-pip-9.0.1/debian/changelog 2019-03-31 00:02:11.0 +0100
@@ -1,3 +1,12 @@
+python-pip (9.0.1-2+deb9u1) stretch; urgency=medium
+
+ * Team upload.
+ * Add Properly_catch_requests_HTTPError_in_index.py.patch, which fixes
+--extra-index-url results in "HTTPError: 404 Client Error: NOT FOUND".
+The patch makes works even with the unbundled requests. (Closes: #837764).
+
+ -- Thomas Goirand Sun, 31 Mar 2019 00:02:11 +0100
+
python-pip (9.0.1-2) unstable; urgency=medium
* d/control: Update python-setuptools Built-Using version.
diff -Nru
python-pip-9.0.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
python-pip-9.0.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
---
python-pip-9.0.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
1970-01-01 01:00:00.0 +0100
+++
python-pip-9.0.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
2019-03-31 00:01:10.0 +0100
@@ -0,0 +1,47 @@
+Description: Properly catch requests' HTTPError in index.py
+ This resolves issue #4195.
+ .
+ In index.py's index retrieval routine we were catching
+ requests.HTTPError to log and ignore 404s and other similar HTTP server
+ errors when pulling from (extra-)index-urls. Unfortunately, the actual
+ path to that exception is requests.exceptions.HTTPError and the alias we
+ were using does not work when pip is installed with unvendored libs as
+ with the debian packaged pip.
+ .
+ Thankfully the fix is simple. Import and use
+ requests.exceptions.HTTPError. This comes with the added bonus of
+ fitting in with the existing handling for RetryError and SSLError. With
+ this change in place upstream pip and downstream packaged pip should
+ both catch this exception properly.
+ .
+ Note: I've not added any tests cases as I'm unsure how to test the
+ distro packaging case within pip's testsuite. However, the existing test
+ suite should hopefully cover that this isn't a regression and I've
+ manually confirmed that this works with a hacked up debian package
+ install. Also this is how we handle RetryError and SSLError.
+Author: Clark Boylan
+Date: Fri, 29 Mar 2019 10:17:31 -0700
+Origin: upstream,
https://github.com/pypa/pip/pull/6367/commits/f8292a304deebcf0e4cda2e40caa226c70030f11
+Bug-Debian: https://bugs.debian.org/837764
+Last-Update: 2019-03-30
+
+--- python-pip-9.0.1.orig/pip/index.py
python-pip-9.0.1/pip/index.py
+@@ -34,7 +34,7 @@ from pip._vendor import html5lib, reques
+ from pip._vendor.packaging.version import parse as parse_version
+ from pip._vendor.packaging.utils import canonicalize_name
+ from pip._vendor.packaging import specifiers
+-from pip._vendor.requests.exceptions import SSLError
++from pip._vendor.requests.exceptions import HTTPError, SSLError
+ from pip._vendor.distlib.compat import unescape
+
+
+@@ -809,7 +809,7 @@ class HTMLPage(object):
+ return
+
+ inst = cls(resp.content, resp.url, resp.headers)
+-except requests.HTTPError as exc:
++except HTTPError as exc:
+ cls._handle_fail(link, exc, url)
+ except SSLError as exc:
+ reason = ("There was a problem confirming the ssl certificate: "
diff -Nru python-pip-9.0.1/debian/patches/series
python-pip-9.0.1/debian/patches/series
--- python-pip-9.0.1/debian/patches/series 2017-01-11 21:48:53.0
+0100
+++ python-pip-9.0.1/debian/patches/series 2019-03-31 00:02:05.0
+0100
@@ -4,3 +4,4 @@
set_user_default.patch
disable-pip-version-check.patch
html5lib-alternative-beta-name.patch
+Properly_catch_requests_HTTPError_in_index.py.patch
Processed: tagging 926048
Processing commands for cont...@bugs.debian.org: > tags 926048 + stretch Bug #926048 [release.debian.org] RM: tbdialout/1.7.2-1+deb9u1 Added tag(s) stretch. > 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
Bug#926048: RM: tbdialout/1.7.2-1+deb9u1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm This extension is broken with Thunderbird 60 and was already removed from sid. Cheers, Moritz
Bug#926045: unblock: software-properties/0.96.20.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package software-properties
This fixes a release critical bug that made software-properties
generate a trusted.gpg file in the wrong format, causing apt to
fail to read.
I essentially replaced the AptAuth.py with the one in Ubuntu 18.04,
which makes it use apt-key instead of gpg directly, so while this
is not as minimal a change as it maybe? could be, it's battle-tested :)
(include/attach the debdiff against the package in testing)
unblock software-properties/0.96.20.2-2
-- System Information:
Debian Release: buster/sid
APT prefers disco
APT policy: (991, 'disco'), (500, 'disco'), (500, 'cosmic-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0-7-generic (SMP w/8 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),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
diff -Nru software-properties-0.96.20.2/debian/changelog software-properties-0.96.20.2/debian/changelog
--- software-properties-0.96.20.2/debian/changelog 2016-06-30 12:13:48.0 +0200
+++ software-properties-0.96.20.2/debian/changelog 2019-03-30 20:45:34.0 +0100
@@ -1,3 +1,10 @@
+software-properties (0.96.20.2-2) unstable; urgency=medium
+
+ * softwareproperties/AptAuth.py: Use apt-key (Closes: #867681)
+ * debian/gbp.conf: Point to debian/buster
+
+ -- Julian Andres Klode Sat, 30 Mar 2019 20:45:34 +0100
+
software-properties (0.96.20.2-1) unstable; urgency=medium
* Imported Upstream version 0.96.20.2
diff -Nru software-properties-0.96.20.2/debian/gbp.conf software-properties-0.96.20.2/debian/gbp.conf
--- software-properties-0.96.20.2/debian/gbp.conf 2016-06-30 12:13:48.0 +0200
+++ software-properties-0.96.20.2/debian/gbp.conf 2019-03-30 20:45:34.0 +0100
@@ -1,2 +1,3 @@
-[buildpackage]
+[DEFAULT]
sign-tags = True
+debian-branch = debian/buster
diff -Nru software-properties-0.96.20.2/debian/patches/0001-Imported-Debian-version-0.96.9debian1.patch software-properties-0.96.20.2/debian/patches/0001-Imported-Debian-version-0.96.9debian1.patch
--- software-properties-0.96.20.2/debian/patches/0001-Imported-Debian-version-0.96.9debian1.patch 2016-06-30 12:13:48.0 +0200
+++ software-properties-0.96.20.2/debian/patches/0001-Imported-Debian-version-0.96.9debian1.patch 2019-03-30 20:45:34.0 +0100
@@ -46,7 +46,7 @@
True
diff --git a/softwareproperties/gtk/SoftwarePropertiesGtk.py b/softwareproperties/gtk/SoftwarePropertiesGtk.py
-index fbe5b0a..33eaaca 100644
+index 11e65c4..cf375c1 100644
--- a/softwareproperties/gtk/SoftwarePropertiesGtk.py
+++ b/softwareproperties/gtk/SoftwarePropertiesGtk.py
@@ -51,7 +51,11 @@ import softwareproperties.distro
diff -Nru software-properties-0.96.20.2/debian/patches/0004-Implement-PackageKit-support.patch software-properties-0.96.20.2/debian/patches/0004-Implement-PackageKit-support.patch
--- software-properties-0.96.20.2/debian/patches/0004-Implement-PackageKit-support.patch 2016-06-30 12:13:48.0 +0200
+++ software-properties-0.96.20.2/debian/patches/0004-Implement-PackageKit-support.patch 2019-03-30 20:45:34.0 +0100
@@ -146,7 +146,7 @@
return res
diff --git a/softwareproperties/gtk/SoftwarePropertiesGtk.py b/softwareproperties/gtk/SoftwarePropertiesGtk.py
-index 33eaaca..df8ad45 100644
+index cf375c1..92037a9 100644
--- a/softwareproperties/gtk/SoftwarePropertiesGtk.py
+++ b/softwareproperties/gtk/SoftwarePropertiesGtk.py
@@ -27,16 +27,21 @@ from __future__ import absolute_import, print_function
@@ -191,7 +191,7 @@
# Put some life into the user interface:
self.init_auto_update()
-@@ -1031,7 +1038,7 @@ class SoftwarePropertiesGtk(SoftwareProperties, SimpleGtkbuilderApp):
+@@ -1033,7 +1040,7 @@ class SoftwarePropertiesGtk(SoftwareProperties, SimpleGtkbuilderApp):
if e._dbus_error_name == 'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
logging.error("Authentication canceled, changes have not been saved")
@@ -200,7 +200,7 @@
#print(progress)
self.button_driver_revert.set_visible(False)
self.button_driver_apply.set_visible(False)
-@@ -1041,30 +1048,30 @@ class SoftwarePropertiesGtk(SoftwareProperties, SimpleGtkbuilderApp):
+@@ -1043,30 +1050,30 @@ class SoftwarePropertiesGtk(SoftwareProperties, SimpleGtkbuilderApp):
self.progress_bar.set_visible(True)
self.label_driver_action.set_label(_("Applying changes..."))
@@ -254,7 +254,7 @@
def on_driver_changes_apply(self, button):
-@@ -1077,18 +1084,36 @@ class
Processed: forgot to send to *-done
Processing commands for cont...@bugs.debian.org: > close 922339 Bug #922339 [release.debian.org] unblock: python-cassandra-driver/3.16.0-1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 922339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forgot to send to *-done
Processing commands for cont...@bugs.debian.org: > close 922809 Bug #922809 [release.debian.org] unblock: aac-tactics/8.8.0+1.gbp069dc3b-1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 922809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#922339: unblock: python-cassandra-driver/3.16.0-1
Processing commands for cont...@bugs.debian.org: > tags 922339 wontfix Bug #922339 [release.debian.org] unblock: python-cassandra-driver/3.16.0-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 922339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922339: unblock: python-cassandra-driver/3.16.0-1
tags 922339 wontfix thanks On Sun, 17 Mar 2019 17:38:21 + Jonathan Wiltshire wrote: > On Thu, Feb 14, 2019 at 08:11:55PM +0100, Héctor Orón Martínez wrote: > > Please unblock package python-cassandra-driver > > > > I have been working with Emmanuel Arias on getting his package sponsored > > into Debian, however it did not make it into Buster on time. It is a > > `salt` build dependency (however `salt` package maintainer has disabled > > it until it makes it in Buster). > > Is the intention that salt will enable support once this package migrates? > Will that require an unblock too? > > #921658 seems to suggest that salt is only a test-time build dependency. > Does this mean that not all of salt's tests are being run at the moment? > What is the impact of this? > > 2018-12-05 when the upload was prepared to 2019-02-08 when it was uploaded > is quite a long delay. Is long-term maintenance assured? Are sufficient > sponsors available for the next 5-6 years? I am closing this bug as wontfix as it is getting too late in the cycle for new packages and the above questions were not answered. Paul signature.asc Description: OpenPGP digital signature
Bug#926041: unblock: bwa/0.7.17-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package bwa. [ Dylan Aïssi ] * Add patch from upstream to fix CVE-2019-10269. (Closes: #926014) [ Jelmer Vernooij ] * Trim trailing whitespace. Thanks. Dylan
Processed: Re: Bug#922809: unblock: aac-tactics/8.8.0+1.gbp069dc3b-1
Processing commands for cont...@bugs.debian.org: > tags 922809 wontfix Bug #922809 [release.debian.org] unblock: aac-tactics/8.8.0+1.gbp069dc3b-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 922809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922809: unblock: aac-tactics/8.8.0+1.gbp069dc3b-1
tags 922809 wontfix thanks Hi Benjamin, On Tue, 12 Mar 2019 20:55:31 -0400 Benjamin Barenblat wrote: > > Couldn't you just fix the FTBFS by patching the original version in > > Debian? That would make reviewing a lot easier. > > Perhaps, but unfortunately, I don’t have the time to write those patches > right now. If the new version is too much to accept into buster at this > point, please feel free to close this as a wontfix – I think the world > can live without aac-tactics for one release cycle. So, that is what I end up doing. It's getting to late into the cycle to let new packages in. Paul signature.asc Description: OpenPGP digital signature
Bug#923797: marked as done (unblock: pyres/1.5-2)
Your message dated Sat, 30 Mar 2019 18:56:14 +0100
with message-id
and subject line Re: Bug#923797: unblock: pyres/1.5-2
has caused the Debian Bug report #923797,
regarding unblock: pyres/1.5-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.)
--
923797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923797
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
Could you, please, unblock pyres and remotecv?
The new pyres version closes #917658.
diff -Nru pyres-1.5/debian/changelog pyres-1.5/debian/changelog
--- pyres-1.5/debian/changelog 2017-09-07 23:14:28.0 -0300
+++ pyres-1.5/debian/changelog 2019-03-04 15:28:30.0 -0300
@@ -1,3 +1,16 @@
+pyres (1.5-2) unstable; urgency=high
+
+ [ Ondřej Nový ]
+
+ * d/control: Set Vcs-* to salsa.debian.org
+ * d/control: Remove ancient X-Python-Version field
+
+ [ Marcelo Jorge Vieira]
+
+ * AttributeError: 'int' object has no attribute 'iteritems' (Closes:
#917658)
+
+ -- Marcelo Jorge Vieira Mon, 04 Mar 2019 15:28:30
-0300
+
pyres (1.5-1) unstable; urgency=low
[ Gilles Dubuc ]
diff -Nru pyres-1.5/debian/control pyres-1.5/debian/control
--- pyres-1.5/debian/control2017-09-07 23:14:28.0 -0300
+++ pyres-1.5/debian/control2019-03-04 15:26:38.0 -0300
@@ -15,10 +15,9 @@
python-setuptools,
python-simplejson,
redis-server
-X-Python-Version: >= 2.7
Homepage: https://github.com/binarydud/pyres
-Vcs-Git:
https://anonscm.debian.org/git/python-modules/packages/pyres.git
-Vcs-Browser:
https://anonscm.debian.org/cgit/python-modules/packages/pyres.git
+Vcs-Git: https://salsa.debian.org/python-team/modules/pyres.git
+Vcs-Browser: https://salsa.debian.org/python-team/modules/pyres
Package: python-pyres
Architecture: all
diff -Nru pyres-1.5/debian/copyright pyres-1.5/debian/copyright
--- pyres-1.5/debian/copyright 2017-09-07 23:14:10.0 -0300
+++ pyres-1.5/debian/copyright 2019-03-04 15:26:38.0 -0300
@@ -74,4 +74,3 @@
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS THEME, EVEN IF ADVISED OF
THE
POSSIBILITY OF SUCH DAMAGE.
-
diff -Nru pyres-1.5/debian/patches/redis_3.patch pyres-
1.5/debian/patches/redis_3.patch
--- pyres-1.5/debian/patches/redis_3.patch 1969-12-31
21:00:00.0 -0300
+++ pyres-1.5/debian/patches/redis_3.patch 2019-03-04
15:27:28.0 -0300
@@ -0,0 +1,11 @@
+--- a/pyres/__init__.py
b/pyres/__init__.py
+@@ -291,7 +291,7 @@
+ def delayed_push(self, datetime, item):
+ key = int(time.mktime(datetime.timetuple()))
+ self.redis.rpush('resque:delayed:%s' % key,
ResQ.encode(item))
+-self.redis.zadd('resque:delayed_queue_schedule', key, key)
++self.redis.zadd('resque:delayed_queue_schedule', {key: key})
+
+ def delayed_queue_peek(self, start, count):
+ return [int(item) for item in self.redis.zrange(
diff -Nru pyres-1.5/debian/patches/series pyres-
1.5/debian/patches/series
--- pyres-1.5/debian/patches/series 1969-12-31 21:00:00.0
-0300
+++ pyres-1.5/debian/patches/series 2019-03-04 15:27:28.0
-0300
@@ -0,0 +1 @@
+redis_3.patch
Cheers,
--
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
http://movimente.me
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
tags 923797 wontfix
thanks
Hi Marcelo,
On Wed, 6 Mar 2019 15:29:00 +0100 Paul Gevers wrote:
> So you missed the soft freeze (like loads of other packages). The soft
> freeze is there for a reason, we try to prevent surprises while we are
> preparing for the release of buster. You didn't act on that FTBFS bug
> (or at least didn't show it) until two days ago. I am asking my question
> again, try to answer it differently this time: Can you please elaborate
> why you think we should grant your package an exception, assuming that
> we don't know what pyres is?
I am closing this bug now as it is getting too late for new packages.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
Processed: Re: Bug#923797: unblock: pyres/1.5-2
Processing commands for cont...@bugs.debian.org: > tags 923797 wontfix Bug #923797 [release.debian.org] unblock: pyres/1.5-2 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 923797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924027: marked as done (unblock: extsmail/2.2-4)
Your message dated Sat, 30 Mar 2019 18:45:18 +0100 with message-id and subject line Re: unblock: extsmail/2.2-4 has caused the Debian Bug report #924027, regarding unblock: extsmail/2.2-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, Please unblock extsmail. I uploaded a new version of extsmail, which reset the package's transition countdown, which will cause it to miss the hard freeze window: https://qa.debian.org/excuses.php?package=extsmail I did so as 2.0-2.1 was removed from testing, newest 2.2 upstream release includes many fixes, and the Debian package had several issues fixed. The full changelog is attached. Thanks for your work as release team ! Best, Olivier unblock extsmail/2.2-4 extsmail (2.2-4) unstable; urgency=low * debian/tests/control: Fix typo in Test-Command. -- Olivier Girondel Tue, 12 Feb 2019 11:36:19 +0100 extsmail (2.2-3) unstable; urgency=low * debian/patches/*: Fix implicit-declaration. * debian/rules: Add --no-parallel. * debian/control: Standards-Version: 4.3.0. * debian/tests/control: Add Restrictions: allow-stderr. -- Olivier Girondel Sun, 10 Feb 2019 00:12:20 +0100 extsmail (2.2-2) unstable; urgency=low * debian/control: Remove Vcs-Git. * debian/patches/*: Fix FTBFS. * debian/rules: Remove --no-parallel. * [bartm] restored changelog. -- Olivier Girondel Wed, 19 Dec 2018 23:27:42 +0100 extsmail (2.2-1) unstable; urgency=low * New upstream release 2.2. (Closes: #748739) * debian/compat: Upgrade to 11. * debian/control: Priority: optional. * debian/control: Vcs-Browser: https://github.com/ltratt/extsmail. * debian/control: Vcs-Git: https://github.com/oliv3/extsmail-debian. * debian/control: Build-Depends: Remove dh-autoreconf. * debian/control: Build-Depends: Update debhelper (>= 11). * debian/control: Update Homepage. * debian/control: Standards-Version: 4.2.1. * debian/copyright: Update copyright years. * debian/copyright: Update Source URL. * debian/copyright: Use secure copyright format URI. * debian/rules: Remove --with autoreconf. * debian/rules: Add --no-parallel. * debian/tests/control: Added. * debian/watch: version=4. * debian/watch: Use secure URI. -- Olivier Girondel Tue, 13 Nov 2018 16:12:07 +0100 extsmail (2.0-2) unstable; urgency=low * Upload to unstable. -- Olivier Girondel Thu, 14 May 2015 22:55:21 +0200 extsmail (2.0-1) experimental; urgency=low * New upstream 2.0 release. * debian/control: Standards-Version: 3.9.6. -- Olivier Girondel Fri, 14 Nov 2014 00:35:33 +0100 extsmail (1.9-1) unstable; urgency=low * New upstream 1.9 release. * debian/control: Standards-Version: 3.9.5. * debian/control: Build-Depends: debhelper (>= 9), dh-autoreconf. * debian/compat: Update to 9. * debian/copyright: Update years. * debian/rules: Use --with autoreconf. -- Olivier Girondel Fri, 20 Jun 2014 20:43:32 +0100 extsmail (1.4-1) unstable; urgency=low * Initial release (Closes: #652731) -- Olivier Girondel Tue, 20 Dec 2011 21:33:46 +0100 --- End Message --- --- Begin Message --- tags 924027 wontfix thanks Hi Olivier, On Fri, 8 Mar 2019 14:40:48 +0100 Olivier Girondel wrote: > Please unblock extsmail. > > I uploaded a new version of extsmail, which reset the package's > transition countdown, which will cause it to miss the hard freeze window: > > https://qa.debian.org/excuses.php?package=extsmail > > > I did so as 2.0-2.1 was removed from testing, newest 2.2 upstream > release includes many fixes, and the Debian package had several issues > fixed. We have decided to not unblock you package. The package missed the deadline for inclusion in buster and it is getting too late in the release cycle. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: unblock: extsmail/2.2-4
Processing commands for cont...@bugs.debian.org: > tags 924027 wontfix Bug #924027 [release.debian.org] unblock: extsmail/2.2-4 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 924027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Can I revert to older verion than current testing
Hi, I am not decided but I need a guidance what is acceptable path forward. This affects many non-Japanese system. Also, Japanese default Desktop install is also affected. im-config is pulled in by many localization tasks. On Sat, Mar 30, 2019 at 12:44:41PM +0100, Ivo De Decker wrote: > It doesn't look like this change is suitable for testing at this > point, so I'm going to close this request. > > If you upload a version with a small target fix compared to testing, > you could consider filing a new request. Question: If the last upload version 0.39-1 which ended up in testing has many issues to fix for me, can I just revert to the version just before, i. e., 0.38-1 with minimal changes? (Then provide debdiff against 0.38-1.) 0.38-1 was OK for more than 6 months. But that was not compatible with Japanese Desktop task. im-config (0.39-1) unstable; urgency=medium <<<=== TESTING [ YOSHINO Yoshihito ] * Support GNOME Wayland with gdm3. -- Osamu Aoki Sat, 09 Mar 2019 02:09:41 +0900 im-config (0.38-1) unstable; urgency=medium <<<=== REVERT TO? * Switch from bash to sh for im-config. * Add build time check to prevent shell grammar errors. -- Osamu Aoki Sat, 04 Aug 2018 23:53:32 +0900 This brute revert action will break Japanese Desktop task's peaceful upgrade. Also, unless Japanese Desktop task list is not changed, it's install will be severely broken... That's a shame. I will try best to fix 0.39-1. (YOSHINO-san, please check my proposed code and refine it to make it work for uim. If you can't come up with good fix, I have to do the last resort choice.) Osamu
Bug#923770: marked as done (unblock: zfs-linux/0.7.13-1)
Your message dated Sat, 30 Mar 2019 18:27:04 +0100 with message-id and subject line Re: unblock: zfs-linux/0.7.13-1 has caused the Debian Bug report #923770, regarding unblock: zfs-linux/0.7.13-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.) -- 923770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923770 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 X-Debbugs-CC: a...@debian.org Please unblock package zfs-linux which will land on unstable shortly. Please note that the upstream version of src:spl-linux must be aligned with src:zfs-linux, hence they should be unblocked at the same time. (explain the reason for the unblock here) [from 0.7.12-2 to 0.7.13-1] * New upstream release (released several hours ago) * Cherry-picked/backported many bug fixes from upstream. * linux 4.20 and 5.0 compatibility (include/attach the debdiff against the package in testing) More than 7000 lines of changes makes the all-in-one debdiff insane. Please review this instead: https://salsa.debian.org/zfsonlinux-team/zfs/compare/debian%2F0.7.12-2...debian%2F0.7.13-1 unblock zfs-linux/0.7.13-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- tags 923769 wontfix tags 923770 wontfix thanks On Tue, 5 Mar 2019 07:59:19 + Mo Zhou wrote: > Please unblock package zfs-linux > which will land on unstable shortly. > > Please note that the upstream version of src:spl-linux > must be aligned with src:zfs-linux, hence they should > be unblocked at the same time. Reading the described changes I am not spotting things that are in line with the freeze policy and the changes are too large to be reviewed by us. Thus, we will not unblock this. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#923769: marked as done (unblock: spl-linux/0.7.13-1)
Your message dated Sat, 30 Mar 2019 18:27:04 +0100 with message-id and subject line Re: unblock: zfs-linux/0.7.13-1 has caused the Debian Bug report #923769, regarding unblock: spl-linux/0.7.13-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.) -- 923769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923769 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 X-Debbugs-CC: a...@debian.org Please unblock package spl-linux which will land on unstable shortly. (explain the reason for the unblock here) New upstream release (released several hours ago). (include/attach the debdiff against the package in testing) Maybe this is much better than the hard-to-review debdiff: https://salsa.debian.org/zfsonlinux-team/spl/compare/debian%2F0.7.12-2...debian%2F0.7.13-1 unblock spl-linux/0.7.13-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- tags 923769 wontfix tags 923770 wontfix thanks On Tue, 5 Mar 2019 07:59:19 + Mo Zhou wrote: > Please unblock package zfs-linux > which will land on unstable shortly. > > Please note that the upstream version of src:spl-linux > must be aligned with src:zfs-linux, hence they should > be unblocked at the same time. Reading the described changes I am not spotting things that are in line with the freeze policy and the changes are too large to be reviewed by us. Thus, we will not unblock this. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: unblock: zfs-linux/0.7.13-1
Processing commands for cont...@bugs.debian.org: > tags 923769 wontfix Bug #923769 [release.debian.org] unblock: spl-linux/0.7.13-1 Added tag(s) wontfix. > tags 923770 wontfix Bug #923770 [release.debian.org] unblock: zfs-linux/0.7.13-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 923769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923769 923770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 924278 to stretch-pu: package clamav/0.101.2+dfsg-0+deb9u1
Processing commands for cont...@bugs.debian.org: > retitle 924278 stretch-pu: package clamav/0.101.2+dfsg-0+deb9u1 Bug #924278 [release.debian.org] stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1 Changed Bug title to 'stretch-pu: package clamav/0.101.2+dfsg-0+deb9u1' from 'stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 924278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 924278
Processing commands for cont...@bugs.debian.org: > tags 924278 + moreinfo Bug #924278 [release.debian.org] stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 924278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923257: marked as done (unblock: ruby-sprite-factory/1.7.1-3)
Your message dated Sat, 30 Mar 2019 18:11:49 +0100 with message-id <56495099-12c5-6eaf-da66-f5d2f5168...@debian.org> and subject line Re: unblock: open-build-service dependencies has caused the Debian Bug report #923257, regarding unblock: ruby-sprite-factory/1.7.1-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.) -- 923257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923257 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-sprite-factory This package FTBS before this version and it is an open-build-service dependency. I hope we can still include it in buster. To check the changes made please have a look at the git repo: https://salsa.debian.org/ruby-team/ruby-sprite-factory unblock ruby-sprite-factory/1.7.1-3 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- package release.debian.org tags 922310 wontfix tags 922316 wontfix tags 922341 wontfix tags 923257 wontfix thanks Hi, As I just wontfixed the open-build-service unblock request, I don't think these request make much sense anymore, hence closing. Paul--- End Message ---
Bug#922316: marked as done (unblock: ruby-leaflet-rails/1.3.1+dfsg-1)
Your message dated Sat, 30 Mar 2019 18:11:49 +0100 with message-id <56495099-12c5-6eaf-da66-f5d2f5168...@debian.org> and subject line Re: unblock: open-build-service dependencies has caused the Debian Bug report #922316, regarding unblock: ruby-leaflet-rails/1.3.1+dfsg-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.) -- 922316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Hey, Please unblock package ruby-leaflet-rails I am writing this on behalf of the Ruby team, requesting you to unblock ruby-leaflet-rails[1] by the soft freeze. The autopkgtest regression in testing was due to ruby-capybara[2], which was not in testing, which was blocked by an RC bug in puma[3]. Since they migrated on the last day before the soft freeze, there was no time to run autopkgtest for ruby-leaflet-rails and thus got blocked because of the same. Hence requesting you to unblock ruby-leaflet-rails/1.3.1+dfsg-1 [1]: https://tracker.debian.org/pkg/ruby-leaflet-rails [2]: https://tracker.debian.org/pkg/ruby-capybara [3]: https://tracker.debian.org/pkg/puma -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Best, Utkarsh --- End Message --- --- Begin Message --- package release.debian.org tags 922310 wontfix tags 922316 wontfix tags 922341 wontfix tags 923257 wontfix thanks Hi, As I just wontfixed the open-build-service unblock request, I don't think these request make much sense anymore, hence closing. Paul--- End Message ---
Bug#922341: marked as done (unblock: ruby-clockwork/2.0.3-4)
Your message dated Sat, 30 Mar 2019 18:11:49 +0100 with message-id <56495099-12c5-6eaf-da66-f5d2f5168...@debian.org> and subject line Re: unblock: open-build-service dependencies has caused the Debian Bug report #922341, regarding unblock: ruby-clockwork/2.0.3-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 922341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922341 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-clockwork `ruby-clockwork` did not make it on time for the soft-free however I'd like release team to consider and grant an exception for it so we can get `open-build-service` package in for Buster release. I am not attaching a debdiff since it is a major update. Gitlab is available at: https://salsa.debian.org/ruby-team/ruby-clockwork Thanks for considering unblock ruby-clockwork/2.0.3-4 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), LANGUAGE=ca_AD:ca (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- package release.debian.org tags 922310 wontfix tags 922316 wontfix tags 922341 wontfix tags 923257 wontfix thanks Hi, As I just wontfixed the open-build-service unblock request, I don't think these request make much sense anymore, hence closing. Paul--- End Message ---
Bug#922342: marked as done (unblock: ruby-jquery-ui-rails/6.0.1+dfsg-3)
Your message dated Sat, 30 Mar 2019 18:11:49 +0100 with message-id <56495099-12c5-6eaf-da66-f5d2f5168...@debian.org> and subject line Re: unblock: open-build-service dependencies has caused the Debian Bug report #922310, regarding unblock: ruby-jquery-ui-rails/6.0.1+dfsg-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.) -- 922310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922310 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-jquery-ui-rails `ruby-jquery-ui-rails` did not make it on time for the soft-free however I'd like release team to consider and grant an exception for it so we can get `open-build-service` package in for Buster release. I am not attaching a debdiff since it is a major update. Gitlab is available at: https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails Thanks for considering unblock ruby-jquery-ui-rails/6.0.1+dfsg-3 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), LANGUAGE=ca_AD:ca (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- package release.debian.org tags 922310 wontfix tags 922316 wontfix tags 922341 wontfix tags 923257 wontfix thanks Hi, As I just wontfixed the open-build-service unblock request, I don't think these request make much sense anymore, hence closing. Paul--- End Message ---
Bug#922310: marked as done (unblock: ruby-jquery-ui-rails/6.0.1+dfsg-3)
Your message dated Sat, 30 Mar 2019 18:11:49 +0100 with message-id <56495099-12c5-6eaf-da66-f5d2f5168...@debian.org> and subject line Re: unblock: open-build-service dependencies has caused the Debian Bug report #922310, regarding unblock: ruby-jquery-ui-rails/6.0.1+dfsg-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.) -- 922310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Hey, Please unblock package ruby-jquery-ui-rails I am writing this on behalf of the Ruby team, requesting you to unblock ruby-jquery-ui-rails[1] by the soft freeze. The autopkgtest regression in testing was due to ruby-capybara[2], which was not in testing, which was blocked by an RC bug in puma[3]. Since they migrated on the last day before the soft freeze, there was no time to run autopkgtest for ruby-jquery-ui-rails and thus got blocked because of the same. Hence requesting you to unblock ruby-jquery-ui-rails/6.0.1+dfsg-3 [1]: https://tracker.debian.org/pkg/ruby-jquery-ui-rails [2]: https://tracker.debian.org/pkg/ruby-capybara [3]: https://tracker.debian.org/pkg/puma -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Best, Utkarsh --- End Message --- --- Begin Message --- package release.debian.org tags 922310 wontfix tags 922316 wontfix tags 922341 wontfix tags 923257 wontfix thanks Hi, As I just wontfixed the open-build-service unblock request, I don't think these request make much sense anymore, hence closing. Paul--- End Message ---
Processed: Re: unblock: open-build-service dependencies
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 922310 wontfix Bug #922310 [release.debian.org] unblock: ruby-jquery-ui-rails/6.0.1+dfsg-3 Bug #922342 [release.debian.org] unblock: ruby-jquery-ui-rails/6.0.1+dfsg-3 Added tag(s) wontfix. Added tag(s) wontfix. > tags 922316 wontfix Bug #922316 [release.debian.org] unblock: ruby-leaflet-rails/1.3.1+dfsg-1 Added tag(s) wontfix. > tags 922341 wontfix Bug #922341 [release.debian.org] unblock: ruby-clockwork/2.0.3-4 Added tag(s) wontfix. > tags 923257 wontfix Bug #923257 [release.debian.org] unblock: ruby-sprite-factory/1.7.1-3 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 922310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922310 922316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922316 922341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922341 922342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922342 923257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922340: marked as done (unblock: open-build-service/2.9.4-1)
Your message dated Sat, 30 Mar 2019 17:58:14 +0100 with message-id and subject line Re: Bug#922340: unblock: open-build-service/2.9.4-1 has caused the Debian Bug report #922340, regarding unblock: open-build-service/2.9.4-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.) -- 922340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922340 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 open-build-service A lot of effort has been put into `open-build-service`, since ruby rails 5 transition needed to happen and it did. Even uploading the package on-time it was delayed due to a couple dependencies: `ruby-clockwork` and `ruby-jquery-ui-rails`. Please consider an exception and allow `open-build-service` into Buster release. I am not attaching a debdiff since it is a major upstream version update. You might check gitlab instead at: https://salsa.debian.org/ruby-team/open-build-service And its dependencies at: https://salsa.debian.org/ruby-team/ruby-clockwork https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails unblock open-build-service/2.9.4-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), LANGUAGE=ca_AD:ca (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- tags 922340 wontfix thanks On Sun, 17 Mar 2019 18:04:10 + Jonathan Wiltshire wrote: > On Wed, Mar 06, 2019 at 11:51:45PM +0100, Hector Oron wrote: > > OK, I tried, and to be honest, stable isn't perfect either, since > > distro lifecycle is longer than application support, so not allowing > > newer upstream versions in stable is problematic security wise in the > > long term. open-build-service is not the only one in this category, > > there are many packages in the same situation and it'd be nice to find > > a common solution for all those. > > What is upstream's approach to stable security updates like? How long is a > stable series maintained? Is it realistic to cherry-pick fixes from new > upstream releases for buster's lifetime? > > New upstreams in stable aren't a problem in themselves, but when not all > new upstream releases are suitable (e.g. mixing bug fixes and features) the > effect can be to block further releases, and make fixing high severity bugs > harder. Ok, let's finish this discussion. No unblock, sorry. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#922209: marked as done (unblock: mandos/1.8.3-3)
Your message dated Sat, 30 Mar 2019 18:01:11 +0100 with message-id <4cb99127-5de5-0d2d-6d15-e9845556c...@debian.org> and subject line Re: unblock: mandos/1.8.3-3 has caused the Debian Bug report #922209, regarding unblock: mandos/1.8.3-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.) -- 922209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team, Please allow mandos to migrate into testing and subsequent freeze. The mandos package was removed because libgnutls30 3.6.0 had removed functionality which Mandos depended on, but libgnutls30 3.6.6, with suitable replacement functionality, was not released until a few weeks ago, and we (also being upstream) had to scramble to implement a new protocol using the new GnuTLS features. This was done on this past Sunday (with a few more releases done on Saturday to fix minor bugs). We would have done it sooner after the package removal, but we needed GnuTLS 3.6.6, which *is* going into buster. It seems a pity to lose the mandos package after 10 years in Debian entirely because of the bad timing of GnuTLS 3.6.6 and the Debian freeze being so close. I brought this up on IRC #debian-release, and issue with the packaging (#922202) was revealed, but it was easily fixed since the offending code was only for backports, so a new version (1.8.3-3) has been uploaded with the relevant code simply removed. We are prepared to do any further required changes to the package (and/or upstream) as needed. /Teddy Hogeborn -- The Mandos Project https://www.recompile.se/mandos --- End Message --- --- Begin Message --- tags 922209 wontfix thanks Hi Teddy, On Wed, 13 Feb 2019 10:33:10 +0100 Teddy Hogeborn wrote: > It seems a pity to lose the mandos package after 10 years in Debian > entirely because of the bad timing of GnuTLS 3.6.6 and the Debian freeze > being so close. Although we understand that the RC issue in you package was caused by an new version of your build dependency, but unfortunately the solution came too late in the release cycle and we will not unblock your package. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: unblock: mandos/1.8.3-3
Processing commands for cont...@bugs.debian.org: > tags 922209 wontfix Bug #922209 [release.debian.org] unblock: mandos/1.8.3-3 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 922209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#922340: unblock: open-build-service/2.9.4-1
Processing commands for cont...@bugs.debian.org: > tags 922340 wontfix Bug #922340 [release.debian.org] unblock: open-build-service/2.9.4-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 922340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925418: marked as done (unblock: postfix/3.4.4-1)
Your message dated Sat, 30 Mar 2019 16:38:48 +
with message-id
and subject line unblock postfix
has caused the Debian Bug report #925418,
regarding unblock: postfix/3.4.4-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.)
--
925418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925418
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 postfix
About the time we were switching to postfix 3.4 in Buster there were a series
of bug reports/updates from upstream. The first one (3.4.1 was caught in the
transition from experimental to unstable/buster. I decided to wait and see
how things went upstream before uploading/asking for another unblock.
It looks like things have calmed down, so I'd like to get 3.4.4 into buster to
address several bugs, two of which are significant. Since this is a post-
freeze bugfix update, I've taken to using the same level of detail in debian/
changelog that I've used for the stretch pu uploads that we've been doing
(3.1.6, 3.1.8, and 3.1.9).
These are all good bug fixes to have. The broken DANE trust anchor file
support is a serious regression in it's own right and the
reject_multi_recipient_bounce bug, while not new, seems to be more frequent or
more visible with BDAT.
Thanks for considering,
Scott K
unblock postfix/3.4.4-1
diff -Nru postfix-3.4.1/debian/changelog postfix-3.4.4/debian/changelog
--- postfix-3.4.1/debian/changelog 2019-03-07 21:51:20.0 -0500
+++ postfix-3.4.4/debian/changelog 2019-03-24 15:35:12.0 -0400
@@ -1,3 +1,31 @@
+postfix (3.4.4-1) unstable; urgency=medium
+
+ [Wietse Venema]
+
+ * 3.4.2
+- Bugfix (introduced: 20181226): broken DANE trust anchor
+ file support, caused by left-over debris from the 20181226
+ TLS library overhaul. Scott Kitterman. File: tls/tls_dane.c.
+ Closes: #924183
+- Bugfix (introduced: Postfix-1.0.1): null pointer read, while
+ logging a warning after a corrupted bounce log file. File:
+ global/bounce_log.c.
+- Bugfix (introduced: Postfix-2.9.0): null pointer read, while
+ logging a warning after a postscreen_command_filter read
+ error. File: postscreen/postscreen_smtpd.c. global/bounce_log.c
+ * 3.4.3
+- Bitrot: LINUX5s support, after some sanity checks with a
+ rawhide prerelease version. Files: makedefs, util/sys_defs.h.
+ Closes: #922477
+ * 3.4.4
+- Bugfix (introduced: Postfix 2.2): reject_multi_recipient_bounce
+ has been producing false rejects starting with the Postfix
+ 2.2 smtpd_end_of_data_restrictons, and for the same reasons,
+ does the same with the Postfix 3.4 BDAT command. The latter
+ was reported by Andreas Schulze. File: smtpd/smtpd_check.c.
+
+ -- Scott Kitterman Sun, 24 Mar 2019 15:28:00 -0400
+
postfix (3.4.1-1) unstable; urgency=medium
[Scott Kitterman]
diff -Nru postfix-3.4.1/HISTORY postfix-3.4.4/HISTORY
--- postfix-3.4.1/HISTORY 2019-03-07 19:08:17.0 -0500
+++ postfix-3.4.4/HISTORY 2019-03-14 19:57:12.0 -0400
@@ -24169,3 +24169,29 @@
the same filename for a private key and certificate. Reported
by Mike Kazantsev. Fix by Viktor Dukhovni. Wietse fixed the
test. Files: tls/tls_certkey.c, tls/Makefile.in.
+
+20190310
+
+ Bitrot: LINUX5s support, after some sanity checks with a
+ rawhide prerelease version. Files: makedefs, util/sys_defs.h.
+
+ Bugfix (introduced: 20181226): broken DANE trust anchor
+ file support, caused by left-over debris from the 20181226
+ TLS library overhaul. By intrigeri. File: tls/tls_dane.c.
+
+ Bugfix (introduced: Postfix-1.0.1): null pointer read, while
+ logging a warning after a corrupted bounce log file. File:
+ global/bounce_log.c.
+
+ Bugfix (introduced: Postfix-2.9.0): null pointer read, while
+ logging a warning after a postscreen_command_filter read
+ error. File: postscreen/postscreen_smtpd.c. global/bounce_log.c
+
+20190312
+
+ Bugfix (introduced: Postfix 2.2): reject_multi_recipient_bounce
+ has been producing false rejects starting with the Postfix
+ 2.2 smtpd_end_of_data_restrictons, and for the same reasons,
+ does the same with the Postfix 3.4 BDAT command. The latter
+ was reported by Andreas Schulze. File: smtpd/smtpd_check.c.
+
diff -Nru postfix-3.4.1/makedefs postfix-3.4.4/makedefs
--- postfix-3.4.1/makedefs 2019-02-10 18:11:21.0 -0500
+++ postfix-3.4.4/makedefs 2019-03-10 19:42:59.0 -0400
@@ -557,7 +557,7 @@
: ${SHLIB_ENV="LD_LIBRARY_PATH=`pwd`/lib"}
:
Processed: Re: unblock: ruby-doorkeeper-openid-connect/1.5.5-1
Processing control commands: > tags -1 moreinfo Bug #925604 [release.debian.org] unblock: ruby-doorkeeper-openid-connect/1.5.5-1 Added tag(s) moreinfo. -- 925604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925604: unblock: ruby-doorkeeper-openid-connect/1.5.5-1
Control: tags -1 moreinfo Hi, On Wed, Mar 27, 2019 at 07:11:57PM +0530, Utkarsh Gupta wrote: > Please unblock package ruby-doorkeeper-openid-connect. > > There was a CVE bug (#924747) reported against the package with severity: > grave. > It was reported on 16th March and was resolved in the latest upload, which was > on 24th March. > Thus, requesting you to please unblock the same and let it be a part of > Buster, > as was going to :) This upload seems to include a number of changes other than the fix for the security issue. This doesn't seem to comply with the freeze policy. Perhaps you can clarify the changes. Otherwise, please revert the upload and upload a targeted fix for this issue. Thanks, Ivo
NEW changes in stable-new
Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_mipsel.changes ACCEPT
Bug#925934: RM: golang-gopkg-data-dog-go-sqlmock.v1/1.3.0-1
Control: tags -1 moreinfo Hi rajudev, On 28-03-2019 21:36, rajudev wrote: > > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > > This was a dependency of golang-github-lucasb-eyer-go-colorful as estimated by > dh-make-golang. > https://salsa.debian.org/libregeekingkid-guest/micro/wikis/Dependency-Tree-of-Micro > > Shengjing pointed it out that golang-github-data-dog-go-sqlmock-dev can be > used for package which imports gopkg.in/DATA-DOG/go-sqlmock.v1 > > Hence I want this package to be removed. Do you want it removed from Debian, or *only* from testing? In the former case, please clone this bug to the ftp.debian.org pseudo package. However, it can't be removed yet, as there are multiple packages (build) depending on it, which need to be fixed first (see below). Did you coordinate this removal request with the maintainers of those packages? Paul elbrus@respighi:~$ dak rm --no-action -R golang-github-lucasb-eyer-go-colorful Will remove the following packages from unstable: golang-github-lucasb-eyer-go-colorful | 1.0-2 | source golang-github-lucasb-eyer-go-colorful-dev | 1.0-2 | all Maintainer: Debian Go Packaging Team --- Reason --- -- Checking reverse dependencies... # Broken Depends: golang-github-gdamore-tcell: golang-github-gdamore-tcell-dev golang-github-rivo-tview: golang-github-rivo-tview-dev golang-github-zyedidia-tcell: golang-github-zyedidia-tcell-dev # Broken Build-Depends: golang-github-gdamore-tcell: golang-github-lucasb-eyer-go-colorful-dev golang-github-rivo-tview: golang-github-lucasb-eyer-go-colorful-dev golang-github-zyedidia-tcell: golang-github-lucasb-eyer-go-colorful-dev Dependency problem found.
Processed: Re: Bug#925934: RM: golang-gopkg-data-dog-go-sqlmock.v1/1.3.0-1
Processing control commands: > tags -1 moreinfo Bug #925934 [release.debian.org] RM: golang-gopkg-data-dog-go-sqlmock.v1/1.3.0-1 Added tag(s) moreinfo. -- 925934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_arm64.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_armel.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_armhf.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_i386.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_mips.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_mips64el.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_ppc64el.changes ACCEPT Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_s390x.changes ACCEPT Processing changes file: libdatetime-timezone-perl_2.09-1+2019a_all.changes ACCEPT Processing changes file: tzdata_2019a-0+deb9u1_all.changes ACCEPT
Bug#926031: unblock: chromium/73.0.3683.75-1
package: release.debian.org user: release.debian@packages.debian.org usertags: unblock Please consider unblocking chromium. This is a large upstream release with a bunch of security fixes. As has been done for the past few stable releases, the plan is to push ongoing upstream security updates to buster(-security). Best wishes, Mike unblock chromium/73.0.3683.75-1
Bug#926021: unblock: lam/7.1.4-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package lam
This package represents a minimal change to restore alternative
compatibility with the other mpi implementations in Debian (see #924452,
#922633). It will also remove FTBFS issues for existing netpipe and
xmpi packages in testing. In all, three AUTORM issues will be resolved.
Take care,
=
source debdiff
=
diff -Nru lam-7.1.4/debian/changelog lam-7.1.4/debian/changelog
--- lam-7.1.4/debian/changelog 2014-03-15 02:47:33.0 +
+++ lam-7.1.4/debian/changelog 2019-03-29 17:36:04.0 +
@@ -1,4 +1,39 @@
-lam (7.1.4-3.1) unstable; urgency=medium
+lam (7.1.4-6) unstable; urgency=medium
+
+ * Minimal RC fix for testing migration
+
+ -- Camm Maguire Fri, 29 Mar 2019 17:36:04 +
+
+lam (7.1.4-5) unstable; urgency=medium
+
+ * fix /usr/lib/lam/lib/* links in lam4-dev
+
+ -- Camm Maguire Mon, 25 Mar 2019 02:24:32 +
+
+lam (7.1.4-4) unstable; urgency=high
+
+ * Accept non-maintaner upload. Thanks Eric Dorland
+ * priority optional, thanks Andreas Beckmann
+ * debhelper compat level 9
+ * remove obsolete conflicts/replace, thanks Andreas Beckmann
+ * remove mpi virtual package, thanks Andreas Beckmann
+ * add breaks against old style alternatives, thanks Andreas Beckmann
+
+ * multiarch for liblam4, thanks Andreas Beckmann
+ * multiarch support in lam4-dev.{prerm,postinst}.in and rules, thanks Andreas
+ Beckmann , (Closes: #924452, #922633)
+ * remove old mpi alternative when appropriate in lam4-dev.preinst, thanks
+ Andreas Beckmann
+ * remove obsolete ldconfig call in liblam4.postinst, thanks Andreas Beckmann
+
+ * thanks to Aron Xu. (Closes: #721437)
+ * standard debian build flags
+ * lintian cleanups
+ * latest standards
+
+ -- Camm Maguire Thu, 21 Mar 2019 21:53:46 +
+
+am (7.1.4-3.1) unstable; urgency=medium
* Non-maintainer upload.
* Drop unnecessary autoconf and automake1.9 build deps. (Closes:
diff -Nru lam-7.1.4/debian/control lam-7.1.4/debian/control
--- lam-7.1.4/debian/control2014-03-15 02:45:39.0 +
+++ lam-7.1.4/debian/control2019-03-29 17:36:04.0 +
@@ -34,11 +34,13 @@
Package: liblam4
Section: libs
Architecture: any
+Multi-Arch: same
Depends: ${shlibs:Depends},${misc:Depends}
Provides: mpi
Conflicts: lam,lam1,lam4,lam4c2
Replaces: lam,lam1,lam4,lam4c2
Recommends: lam-runtime
+Breaks: libopenmpi-dev (<< 3.0.1~rc1-2), openmpi-bin (<< 3.0.1~rc1-2), mpich
(<< 3.3~a3-2), libmpich-dev (<< 3.3~a3-2)
Description: Shared libraries used by LAM parallel programs
LAM (Local Area Multicomputer) is an open source implementation of the
Message Passing Interface (MPI) standard.
diff -Nru lam-7.1.4/debian/lam4-dev.postinst lam-7.1.4/debian/lam4-dev.postinst
--- lam-7.1.4/debian/lam4-dev.postinst 2012-04-05 20:07:37.0 +
+++ lam-7.1.4/debian/lam4-dev.postinst 1970-01-01 00:00:00.0 +
@@ -1,27 +0,0 @@
-#!/bin/sh
-
-set -e
-
-update-alternatives --install /usr/include/mpi mpi /usr/include/lam 30 \
---slave /usr/lib/libmpi.so libmpi.so /usr/lib/liblam.so \
---slave /usr/lib/libmpio.so libmpio.so /usr/lib/liblamio.so \
---slave /usr/lib/libmpi++.so libmpi++.so /usr/lib/liblam++.so \
---slave /usr/lib/libmpi.a libmpi.a /usr/lib/liblam.a \
---slave /usr/lib/libmpio.a libmpio.a /usr/lib/liblamio.a \
---slave /usr/lib/libmpi++.a libmpi++.a /usr/lib/liblam++.a \
---slave /usr/bin/mpicc mpicc /usr/bin/mpicc.lam \
---slave /usr/share/man/man1/mpicc.1.gz mpicc.1.gz
/usr/share/man/man1/mpicc.lam.1.gz \
---slave /usr/bin/mpif77 mpif77 /usr/bin/mpif77.lam \
---slave /usr/share/man/man1/mpif77.1.gz mpif77.1.gz
/usr/share/man/man1/mpif77.lam.1.gz \
---slave /usr/bin/mpiCC mpiCC /usr/bin/mpic++.lam \
---slave /usr/share/man/man1/mpiCC.1.gz mpiCC.1.gz
/usr/share/man/man1/mpiCC.lam.1.gz \
---slave /usr/bin/mpic++ mpic++ /usr/bin/mpic++.lam \
---slave /usr/share/man/man1/mpic++.1.gz mpic++.1.gz
/usr/share/man/man1/mpic++.lam.1.gz
-
-update-alternatives \
---install /usr/share/man/man3/MPI_Comm_set_name.3.gz
MPI_Comm_set_name.3.gz /usr/share/man/man3/MPI_Comm_set_name_lam4-dev.3.gz 10
-
-
-#DEBHELPER#
-
-exit 0
diff -Nru lam-7.1.4/debian/lam4-dev.postinst.in
lam-7.1.4/debian/lam4-dev.postinst.in
--- lam-7.1.4/debian/lam4-dev.postinst.in 1970-01-01 00:00:00.0
+
+++ lam-7.1.4/debian/lam4-dev.postinst.in 2019-03-29 17:30:31.0
+
@@ -0,0 +1,31 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = "configure" ]; then
+
+update-alternatives \
+ --install /usr/include/@DEB_HOST_MULTIARCH@/mpi
mpi-@DEB_HOST_MULTIARCH@/usr/include/lam30 \
+ --slave
Bug#926018: [pre-approval] unblock: uim/1:1.8.8-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is a pre-approval for unblocking uim/1:1.8.8-4.
Please unblock package uim.
When upgrading from stretch to buster, input methods setting is broke
due to dropping uim-{byeoru,ipa-x-sampa,latin,look,m17nlib,pinyin,viqr}
packages previously.
So this uploading ressurects their packages for normally upgrading.
diff -Nru uim-1.8.8/debian/NEWS uim-1.8.8/debian/NEWS
--- uim-1.8.8/debian/NEWS 2017-10-01 11:24:34.0 +0900
+++ uim-1.8.8/debian/NEWS 2019-03-27 23:08:38.0 +0900
@@ -1,15 +1,5 @@
uim (1:1.8.6+gh20161003.0.d63dadd-5) unstable; urgency=medium
- automatically register/unregister input methods:
-
- - byeoru : byeoru hangul input method
- - ipa-x-sampa: X-SAMPA IPA input method
- - latin : Latin script input method
- - look : dictionary-based completion input method
- - m17nlib: m17nlib multilingual input method
- - pinyin : pinyin input method
- - viqr : Vietnamese Quoted-Readable input method
-
drop applet packages.
- uim-applet-gnome
diff -Nru uim-1.8.8/debian/changelog uim-1.8.8/debian/changelog
--- uim-1.8.8/debian/changelog 2018-08-03 21:26:06.0 +0900
+++ uim-1.8.8/debian/changelog 2019-03-28 09:31:18.0 +0900
@@ -1,3 +1,23 @@
+uim (1:1.8.8-4) unstable; urgency=medium
+
+ [ YOSHINO Yoshihito ]
+ * Non-maintainer upload.
+ * d/{uim.{postinst,prerm},NEWS}: Do not auto-register/unregister plugins of
+the following input methods:
+byeoru, ipa-x-sampa, latin, look, m17nlib, pinyin, viqr
+When upgrading from stretch this behaved badly and they took precedence
+over other popular plugins many people use.
+ * d/{control,rules,uim-*.{postinst,prerm}}: Resurrect packages
+uim-{byeoru,ipa-x-sampa,latin,look,m17nlib,pinyin,viqr} for those plugins.
+All of them exist in stretch and should upgrade normally.
+Dear testing/sid users,
+If you are using some of the input methods above, you have to manually
+install the respective package(s). Sorry for any inconvenience.
+ * d/{uim.preinst,control}: Unregister those plugins on upgrade from
+testing/sid. Make uim Pre-Depends: uim-data accordingly.
+
+ -- HIGUCHI Daisuke (VDR dai) Thu, 28 Mar 2019 09:31:18
+0900
+
uim (1:1.8.8-3) unstable; urgency=medium
[ HIGUCHI Daisuke (VDR dai) ]
diff -Nru uim-1.8.8/debian/control uim-1.8.8/debian/control
--- uim-1.8.8/debian/control2018-08-03 18:40:41.0 +0900
+++ uim-1.8.8/debian/control2019-03-27 23:08:38.0 +0900
@@ -40,9 +40,9 @@
Architecture: any
Multi-Arch: foreign
Depends: ${misc:Depends}, ${shlibs:Depends},
- uim-data (>= ${source:Version}),
uim-plugins (>= ${source:Version})
-Pre-Depends: dpkg (>= 1.15.7.2)
+Pre-Depends: dpkg (>= 1.15.7.2),
+ uim-data (>= ${source:Version})
Breaks: uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-utils (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
@@ -92,9 +92,23 @@
Architecture: all
Breaks: libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-anthy (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-m17nlib (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-byeoru (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-latin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-pinyin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-viqr (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-ipa-x-sampa (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-look (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~)
Replaces: libuim-data (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-anthy (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-m17nlib (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-byeoru (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-latin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-pinyin (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-viqr (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-ipa-x-sampa (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
+ uim-look (<< 1:1.8.6+gh20161003.0.d63dadd-5~),
uim-common (<< 1:1.8.6+gh20161003.0.d63dadd-5~)
Depends: m17n-db,
${misc:Depends}
@@ -344,6 +358,23 @@
This package contains a plugin for uim to support the use of the Japanese
input method SKK.
+Package: uim-m17nlib
+Section: utils
+Architecture: all
+Depends: ${misc:Depends},
+ uim (>= ${source:Version}),
+ uim-data (>= ${source:Version})
+Multi-Arch: foreign
+Description: Universal Input Method - m17nlib plugin metapackage
+ Uim is an input method module library which supports various scripts and can
+ act as a front end for a range of input methods, including Anthy, Canna,
+ or SKK (for Japanese), Pinyin (for Chinese), Byeoru (for Korean), and
+ M17n (for many other languages). Most of its functions are implemented in
+ Scheme, so it's very
NEW changes in stable-new
Processing changes file: clamav_0.100.3+dfsg-0+deb9u1_amd64.changes ACCEPT Processing changes file: libdatetime-timezone-perl_2.09-1+2019a_sourceonly.changes ACCEPT Processing changes file: tzdata_2019a-0+deb9u1_source.changes ACCEPT
Bug#925383: Processed: Re: Bug#925383: unblock: shorewall/5.2.3.2-1
On Sun, Mar 24, 2019 at 06:51:04PM +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > tags 925383 - moreinfo > Bug #925383 [release.debian.org] unblock: shorewall/5.2.3.2-1 > Removed tag(s) moreinfo. > > thanks > Stopping processing here. > Hi Jonathan, I removed the moreinfo tag nearly a week ago. Did I misunderstand what else I needed to do? Did I need to go ahead and upload as well? I was waiting for a pre-approval, but if uploading now makes more sense and saves you work (since you could review and then unblock the waiting package), I can upload right away. Regards, -Roberto -- Roberto C. Sánchez
Processed: clamav 0.100.3+dfsg-0+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926003 [release.debian.org] stretch-pu: package clamav/0.100.3+dfsg-0+deb9u1 Ignoring request to alter tags of bug #926003 to the same tags previously set -- 926003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926003: clamav 0.100.3+dfsg-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: clamav Version: 0.100.3+dfsg-0+deb9u1 Explanation: security updates: out-of-bounds heap read condition may occur when scanning PDF documents [CVE-2019-1787]; out-of-bounds heap read condition may occur when scanning PE files packed using Aspack [CVE-2019-1789]; out-of-bounds heap write condition may occur when scanning OLE2 files [CVE-2019-1788]
Processed: libdatetime-timezone-perl 2.09-1+2019a flagged for acceptance
Processing control commands: > tags -1 + pending Bug #925548 [release.debian.org] stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2019a Ignoring request to alter tags of bug #925548 to the same tags previously set -- 925548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: clamav 0.100.3+dfsg-0+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #926003 [release.debian.org] stretch-pu: package clamav/0.100.3+dfsg-0+deb9u1 Added tag(s) pending. -- 926003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925609: marked as done (unblock: rails/2:5.2.2.1+dfsg-1)
Your message dated Sat, 30 Mar 2019 12:52:29 +0100 with message-id and subject line Re: Bug#925609: unblock: rails/2:5.2.2.1+dfsg-1 has caused the Debian Bug report #925609, regarding unblock: rails/2:5.2.2.1+dfsg-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.) -- 925609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Hey, Please unblock package rails. There were 2 bugs (#924520 and #924521) reported against the package with severity: grave and severity: important, respectively. Both the bugs were reported on 13th March and were resolved in the latest upload, which was on 19th March. The package had previously migrated to testing until the two bugs were reported against it. Hence, requesting you to please unblock the same and let it be a part of Buster, which it was going to :) Note: This should be unblocked after/in/with reference to the unblock request for ruby-globalid (#925602). Best, Utkarsh unblock rails/2:5.2.2.1+dfsg-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hi Utkarsh, On 27-03-2019 15:10, Utkarsh Gupta wrote: > Please unblock package rails. unblocked, thanks. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#925548: libdatetime-timezone-perl 2.09-1+2019a 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 . Thanks for your contribution! Upload details == Package: libdatetime-timezone-perl Version: 2.09-1+2019a Explanation: update included data
Processed: libdatetime-timezone-perl 2.09-1+2019a flagged for acceptance
Processing control commands: > tags -1 + pending Bug #925548 [release.debian.org] stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2019a Added tag(s) pending. -- 925548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925602: marked as done (unblock: ruby-globalid/0.4.2-1)
Your message dated Sat, 30 Mar 2019 12:47:47 +0100 with message-id <69bdeca9-918c-a8af-0fd6-519b45989...@debian.org> and subject line Re: Bug#925602: unblock: ruby-globalid/0.4.2-1 has caused the Debian Bug report #925602, regarding unblock: ruby-globalid/0.4.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Hey, Please unblock package ruby-globalid. Recently, there was a bug (#925178) reported against the package with severity: important. The package was in testing and the bug was reported on 20th March and was resolved in the latest upload, which was on 24th March. This also causes regression in the migration of rails' latest update. Hence, request you to: unblock ruby-globalid/0.4.2-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- tags 925602 wontfix thanks On 28-03-2019 14:23, Utkarsh Gupta wrote: > It was breaking just the autopkgtest, thus the regression. > Everything else was fine. [...] > ruby-activejob from rails is the only reverse dependency of ruby-globalid. > Since the package is in good shape now, perhaps could be given an exception? > And it won't be risky either since ruby-activejob is the only rev-dep :) > Also, it was an RC bug at the last moment (though I understand the > scenario here) :( The bug is *not* RC, merely important. Although I am open for unblocks of targeted autopkgtest fixes, it is not the time for new upstream release and debhelper compat bumps. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: Bug#925602: unblock: ruby-globalid/0.4.2-1
Processing commands for cont...@bugs.debian.org: > tags 925602 wontfix Bug #925602 [release.debian.org] unblock: ruby-globalid/0.4.2-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 925602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925974: marked as done (unblock: im-config/0.42-1)
Your message dated Sat, 30 Mar 2019 12:44:41 +0100
with message-id <20190330114439.6p4q75yfknvnf...@debian.org>
and subject line Re: unblock: im-config/0.42-1
has caused the Debian Bug report #925974,
regarding unblock: im-config/0.42-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.)
--
925974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925974
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 im-config
(explain the reason for the unblock here)
This version should fix nasty performance bug as reported and summarized
in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925160#144
We don't want ssh into a typical system to be delayed 11 seconds.
(include/attach the debdiff against the package in testing)
I have to admit this is relatively large since it revert many previous
changes. I have to admit this needs to be proofed by Yoshino-san who
was involved for the version in testing. If I didn't screw-up while
cherry picking code snippets and changing glob, this should be better.
I made this in rush, so I am a bit worried.
If you go to git repo, that may be easier to see changes:
https://salsa.debian.org/input-method-team/im-config
Please make sure to see its devel branch which is quasi-native style.
The master and upstream branches are used as gbp-style.
diff -Nru im-config-0.39/70-im-config im-config-0.42/70-im-config
--- im-config-0.39/70-im-config 2019-03-09 02:09:03.0 +0900
+++ im-config-0.42/70-im-config 2019-03-30 00:31:43.0 +0900
@@ -1,8 +1,12 @@
#! /bin/sh
+# vim: set sts=4 expandtab:
+# systemd user-environment-generators
+#
+if ! [ -e "/usr/bin/ibus-daemon" ]; then
+if [ -r /etc/X11/Xsession.d/70im-config_launch ]; then
+. /etc/X11/Xsession.d/70im-config_launch
-if [ -r /etc/X11/Xsession.d/70im-config_launch ]; then
-. /etc/X11/Xsession.d/70im-config_launch
-
-# always export variables even for manual configuration.
-env | grep -E
'^(IM_CONFIG_PHASE|XMODIFIERS|GTK_IM_MODULE|QT_IM_MODULE|QT4_IM_MODULE|CLUTTER_IM_MODULE)='
+# always export variables even for manual configuration.
+env | grep -E
'^(IM_CONFIG_PHASE|XMODIFIERS|GTK_IM_MODULE|QT_IM_MODULE|QT4_IM_MODULE|CLUTTER_IM_MODULE|IM_CONFIG_SET_.*)='
+fi
fi
diff -Nru im-config-0.39/70im-config_launch im-config-0.42/70im-config_launch
--- im-config-0.39/70im-config_launch 2019-03-09 02:09:03.0 +0900
+++ im-config-0.42/70im-config_launch 2019-03-24 13:04:57.0 +0900
@@ -11,11 +11,6 @@
IMLAUNCH=/usr/bin/im-launch
-if [ "$IM_CONFIG_PHASE" = 1 ]; then
-IM_CONFIG_CHECK_ENV=1
-export IM_CONFIG_CHECK_ENV
-fi
-
# If already tweaked, keep hands off :-)
# If im-config is removed but not purged, keep hands off :-)
if [ -z "$XMODIFIERS" ] && \
@@ -26,6 +21,7 @@
[ -r /usr/share/im-config/xinputrc.common ]; then
IM_CONFIG_PHASE=1
export IM_CONFIG_PHASE
+if [ x != x"$ZSH_NAME" ]; then emulate -R sh ; fi
# initialize all im-config common functions and parameters
. /usr/share/im-config/xinputrc.common
unset TEXTDOMAIN
@@ -42,6 +38,17 @@
export QT_IM_MODULE
export QT4_IM_MODULE
export CLUTTER_IM_MODULE
+# backup data for change check
+IM_CONFIG_SET_XMODIFIERS="$XMODIFIERS"
+IM_CONFIG_SET_GTK_IM_MODULE="$GTK_IM_MODULE"
+IM_CONFIG_SET_QT_IM_MODULE="$QT_IM_MODULE"
+IM_CONFIG_SET_QT4_IM_MODULE="$QT4_IM_MODULE"
+IM_CONFIG_SET_CLUTTER_IM_MODULE="$CLUTTER_IM_MODULE"
+export IM_CONFIG_SET_XMODIFIERS
+export IM_CONFIG_SET_GTK_IM_MODULE
+export IM_CONFIG_SET_QT_IM_MODULE
+export IM_CONFIG_SET_QT4_IM_MODULE
+export IM_CONFIG_SET_CLUTTER_IM_MODULE
fi
# Change $STARTUP string to im-launch while keeping the old $STARTUP string
diff -Nru im-config-0.39/data/21_ibus.rc im-config-0.42/data/21_ibus.rc
--- im-config-0.39/data/21_ibus.rc 2018-08-04 23:20:43.0 +0900
+++ im-config-0.42/data/21_ibus.rc 2019-03-30 01:04:29.0 +0900
@@ -13,50 +13,51 @@
GTK_IM_MODULE=xim
# use immodule only when available for both GTK 2.0 and 3.0
IM_CONFIG_MARKER2=0
-IM_CONFIG_MARKER="$(imconfig_find_files_with_prefixpath_glob /usr/lib \
-'/usr/lib/*/gtk-2.0/*/immodules/im-ibus.so' \
-'/usr/lib/gtk-2.0/*/immodules/im-ibus.so')"
-if [ "x${IM_CONFIG_MARKER}" != "x" ]; then
-IM_CONFIG_MARKER2=1
-fi
+for IM_CONFIG_MARKER in /usr/lib/*-*-*/gtk-2.0/*/immodules/im-ibus.so \
+
Bug#925988: marked as done (unblock: sogo-connector/60.0.2-1)
Your message dated Sat, 30 Mar 2019 11:46:12 +
with message-id
and subject line unblock sogo-connector
has caused the Debian Bug report #925988,
regarding unblock: sogo-connector/60.0.2-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
925988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925988
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 sogo-connector
sogo-connector is a extension for Thunderbird which has no reverse
dependencies.
I'd like to see the sogo-connector package gets updated in
testing/buster. Upstream has fixed some minor issues regarding the
invitations dialog which could be always empty. The packaging itself got
no changes.
I've attached the debdiff output from the version currently in testing
against the version in unstable. Thanks for considering.
unblock sogo-connector/60.0.2-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru
sogo-connector-60.0.1/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
sogo-connector-60.0.2/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
---
sogo-connector-60.0.1/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
2019-02-20 14:31:59.0 +0100
+++
sogo-connector-60.0.2/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
2019-02-26 17:17:20.0 +0100
@@ -1,42 +1,7 @@
-
+
%dtd1;
@@ -54,10 +19,10 @@
@@ -80,11 +45,15 @@
null
null
+
+
+return {
+alldayEvent: "",
+recurrentEvent:
"",
+location: "",
+organizer: "",
+attendee: "",
+none: ""
+};
+
+
+
-
- var alldayEventText = "";
- var recurrentEventText =
"";
- var locationText = "";
- var organizerText = "";
- var attendeeText = "";
- var noneText = "";
-
-
+this.setAttribute("itemId", aItem.hashId);
+]]>
@@ -234,31 +207,32 @@
diff -Nru sogo-connector-60.0.1/debian/changelog
sogo-connector-60.0.2/debian/changelog
--- sogo-connector-60.0.1/debian/changelog 2019-02-21 19:27:47.0
+0100
+++ sogo-connector-60.0.2/debian/changelog 2019-03-07 19:40:57.0
+0100
@@ -1,3 +1,9 @@
+sogo-connector (60.0.2-1) unstable; urgency=medium
+
+ * [747546e] New upstream version 60.0.2
+
+ -- Carsten Schoenert Thu, 07 Mar 2019 19:40:57
+0100
+
sogo-connector (60.0.1-1) unstable; urgency=medium
* [37adbb6] New upstream version 60.0.1
diff -Nru sogo-connector-60.0.1/install.rdf sogo-connector-60.0.2/install.rdf
--- sogo-connector-60.0.1/install.rdf 2019-02-20 14:31:59.0 +0100
+++ sogo-connector-60.0.2/install.rdf 2019-02-26 17:17:20.0 +0100
@@ -5,7 +5,7 @@
--- End Message ---
--- Begin Message ---
Unblocked sogo-connector.--- End Message ---
Bug#923184: marked as done (unblock: qgis/3.4.6+dfsg-1)
Your message dated Sat, 30 Mar 2019 12:39:45 +0100 with message-id and subject line Re: Bug#923184: unblock: qgis/3.4.6+dfsg-1 has caused the Debian Bug report #923184, regarding unblock: qgis/3.4.6+dfsg-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.) -- 923184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923184 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 Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the latter in buster is probably better than leaving the qgis package at the last 2.18.x release (2.18.28). QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such the changes since the version in testing are quite large and cannot be considered "small, targeted fixes". While users of the qgis package are unlikely to use the version of the package available in stable, and more likely using the latest LTR from backports, I think having 3.4.5 in buster is better for users upgrading from stretch than leaving them with the EOL 2.18.28 release until the package is updated in buster-backports. Would you approve of moving QGIS 3.4.5 from experimental to unstable and allowing it to migrate to tesing for inclusion in buster? Or should we keep it experimental until after the release, and make the newer LTRs available in buster-backports when it hits testing? Kind Regards, Bas --- End Message --- --- Begin Message --- tags 923184 wontfix thanks Hi Sebastiaan, First of all, sorry it took a while to come back to your request. On 30-03-2019 11:18, Sebastiaan Couwenberg wrote: > On 3/17/19 11:43 PM, Sebastiaan Couwenberg wrote: >> On 3/17/19 8:17 PM, Sebastiaan Couwenberg wrote: >>> On 2/24/19 9:23 PM, Bas Couwenberg wrote: Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the latter in buster is probably better than leaving the qgis package at the last 2.18.x release (2.18.28). QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such the changes since the version in testing are quite large and cannot be considered "small, targeted fixes". Ack. While users of the qgis package are unlikely to use the version of the package available in stable, and more likely using the latest LTR from backports, I think having 3.4.5 in buster is better for users upgrading from stretch than leaving them with the EOL 2.18.28 release until the package is updated in buster-backports. Would you approve of moving QGIS 3.4.5 from experimental to unstable and allowing it to migrate to tesing for inclusion in buster? Or should we keep it experimental until after the release, and make the newer LTRs available in buster-backports when it hits testing? >>> >>> As reported by Lucas Nussbaum in #924833, qgis (2.18.28-2) FTBFS in >>> unstable due to sip4 (4.19.14+dfsg-1) which was uploaded a couple of >>> weeks after qgis. >>> >>> With 2.18.x being EOL upstream, we cannot rely on upstream to provide a >>> fix, and I lack the skills for it. >>> >>> I'm going to move QGIS 3.4 to unstable so that we at least have a >>> version of QGIS in unstable that supports SIP 4.19.14. >>> >>> If the changes in QGIS 3.4 are deemed to invasive for an unblock, we'll >>> have to release buster without qgis and deal with lots of unhappy users. Although we understand that the FTBFS issue in you package was caused by an new version of your build dependency, which had an upload very much not in line with the transition freeze at the time, we will not unblock your package. The changes are just too large in this stage of releasing buster. It would have helped your case if the work on packaging a newer version of qgis would have started earlier, such that the updates in buster would have been smaller. I am aware that you know the concept of autopkgtest, so we suggest you add a test where you try to prevent this kind of change going unnoticed, as you suggest that this is not the first time that sip4 breaks bindings that you use. If those tests are in place, this type of breakage will be spotted automatically and the migration software will block such an version from migrating, until the issue is fixed. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: Bug#923184: unblock: qgis/3.4.6+dfsg-1
Processing commands for cont...@bugs.debian.org: > tags 923184 wontfix Bug #923184 [release.debian.org] unblock: qgis/3.4.6+dfsg-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 923184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925963: marked as done (unblock: avy/0.4.0+git20190328.85b5d574-1)
Your message dated Sat, 30 Mar 2019 11:41:20 +
with message-id
and subject line unblock avy
has caused the Debian Bug report #925963,
regarding unblock: avy/0.4.0+git20190328.85b5d574-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.)
--
925963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925963
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 avy
Updating the avy package is needed to fix compatibility issues of the
zzz-to-char package (see, #925945). Changes in the avy package are
significant, but as far as I can tell they do not break stuff, rather
fixing issues with Emacs 26.1.
unblock avy/0.4.0+git20190328.85b5d574-1
With regards,
Lev Lamberov
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8),
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru avy-0.4.0+git20180322.2d613eb0/avy.el
avy-0.4.0+git20190328.85b5d574/avy.el
--- avy-0.4.0+git20180322.2d613eb0/avy.el 2018-03-23 01:33:23.0
+0500
+++ avy-0.4.0+git20190328.85b5d574/avy.el 2019-03-28 21:17:29.0
+0500
@@ -78,29 +78,39 @@
(character :tag "char")
(symbol :tag "non-printing key"
+(defconst avy--key-type
+ '(choice :tag "Command"
+(const avy-goto-char)
+(const avy-goto-char-2)
+(const avy-isearch)
+(const avy-goto-line)
+(const avy-goto-subword-0)
+(const avy-goto-subword-1)
+(const avy-goto-word-0)
+(const avy-goto-word-1)
+(const avy-copy-line)
+(const avy-copy-region)
+(const avy-move-line)
+(const avy-move-region)
+(const avy-kill-whole-line)
+(const avy-kill-region)
+(const avy-kill-ring-save-whole-line)
+(const avy-kill-ring-save-region)
+(function :tag "Other command")))
+
(defcustom avy-keys-alist nil
"Alist of avy-jump commands to `avy-keys' overriding the default `avy-keys'."
- :type '(alist
- :key-type (choice :tag "Command"
- (const avy-goto-char)
- (const avy-goto-char-2)
- (const avy-isearch)
- (const avy-goto-line)
- (const avy-goto-subword-0)
- (const avy-goto-subword-1)
- (const avy-goto-word-0)
- (const avy-goto-word-1)
- (const avy-copy-line)
- (const avy-copy-region)
- (const avy-move-line)
- (const avy-move-region)
- (const avy-kill-whole-line)
- (const avy-kill-region)
- (const avy-kill-ring-save-whole-line)
- (const avy-kill-ring-save-region)
- (function :tag "Other command"))
+ :type `(alist
+ :key-type ,avy--key-type
:value-type (repeat :tag "Keys" character)))
+(defcustom avy-orders-alist '((avy-goto-char . avy-order-closest))
+ "Alist of candidate ordering functions.
+Usually, candidates appear in their point position order."
+ :type `(alist
+ :key-type ,avy--key-type
+ :value-type function))
+
(defcustom avy-words
'("am" "by" "if" "is" "it" "my" "ox" "up"
"ace" "act" "add" "age" "ago" "aim" "air" "ale" "all" "and" "ant" "any"
@@ -234,6 +244,16 @@
Typically, these modes don't use the text representation."
:type 'list)
+(defcustom avy-single-candidate-jump t
+ "In case there is only one candidate jumps directly to it."
+ :type 'boolean)
+
+(defcustom avy-del-last-char-by '(8 127)
+ "List of event types, i.e. key presses, that delete the last
+character read. The default represents `C-h' and `DEL'. See
+`event-convert-list'."
+ :type 'list)
+
(defvar avy-ring (make-ring 20)
"Hold the window and point history.")
@@ -362,11 +382,22 @@
lst (cdr lst))
(nreverse path-alist)))
+(defun avy-order-closest (x)
+ (abs (- (caar x) (point
+
+(defvar avy-command nil
+ "Store the current command symbol.
+E.g. 'avy-goto-line or 'avy-goto-char.")
+
(defun
Bug#925962: marked as done (unblock: zzz-to-char/0.1.3-2)
Your message dated Sat, 30 Mar 2019 11:40:08 + with message-id and subject line unblock zzz-to-char has caused the Debian Bug report #925962, regarding unblock: zzz-to-char/0.1.3-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.) -- 925962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925962 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 zzz-to-char Version 0.1.3-2 contains a pretty small change to fix #925945, but for this fix to work it is also needed to update the avy package (unblock request coming soon), and changes in the avy package a more significant. Unfortunately, the zzz-to-char package without updating the avy package (its dependency) cannot be properly fixed. unblock zzz-to-char/0.1.3-2 With regards, Lev Lamberov -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru zzz-to-char-0.1.3/debian/changelog zzz-to-char-0.1.3/debian/changelog --- zzz-to-char-0.1.3/debian/changelog 2019-01-29 13:30:28.0 +0500 +++ zzz-to-char-0.1.3/debian/changelog 2019-03-29 12:14:23.0 +0500 @@ -1,3 +1,9 @@ +zzz-to-char (0.1.3-2) unstable; urgency=medium + + * Apply recent upstream commits (Closes: #925945) + + -- Lev Lamberov Fri, 29 Mar 2019 12:14:23 +0500 + zzz-to-char (0.1.3-1) unstable; urgency=medium * New upstream version 0.1.3 diff -Nru zzz-to-char-0.1.3/debian/patches/0002-fix-emacs26.diff zzz-to-char-0.1.3/debian/patches/0002-fix-emacs26.diff --- zzz-to-char-0.1.3/debian/patches/0002-fix-emacs26.diff 1970-01-01 05:00:00.0 +0500 +++ zzz-to-char-0.1.3/debian/patches/0002-fix-emacs26.diff 2019-03-29 12:14:23.0 +0500 @@ -0,0 +1,31 @@ +From: Mark Karpov +Subject: Apply upstream commits to fix zzz-to-char in Emacs 26.1 + +Apply 9f08bf94c56a39a2b65f90b852da76dfa6ec2a6f (Fix the call to +‘avy-jump’) and 1ed6d26bcd481d88c6440984c93c248abdea2804 (Use +‘avy-jump’ instead of ‘avy--generic-jump’) upstream commits. + +--- a/zzz-to-char.el b/zzz-to-char.el +@@ -63,15 +63,15 @@ This is an internal function, see also ` + (let ((p (point)) + (avy-all-windows nil)) + (avy-with zzz-to-char +- (avy--generic-jump ++ (avy-jump +(if (= 13 char) +"\n" + (regexp-quote (string char))) +- nil +- (max (- p zzz-to-char-reach) +-(point-min)) +- (min (+ p zzz-to-char-reach) +-(point-max ++ :window-flip nil ++ :beg (max (- p zzz-to-char-reach) ++ (point-min)) ++ :end (min (+ p zzz-to-char-reach) ++ (point-max + (let ((n (point))) + (when (/= n p) + (cl-destructuring-bind (beg . end) diff -Nru zzz-to-char-0.1.3/debian/patches/series zzz-to-char-0.1.3/debian/patches/series --- zzz-to-char-0.1.3/debian/patches/series 2019-01-29 13:30:28.0 +0500 +++ zzz-to-char-0.1.3/debian/patches/series 2019-03-29 12:14:23.0 +0500 @@ -1 +1,2 @@ 0001-remove-badges.diff +0002-fix-emacs26.diff --- End Message --- --- Begin Message --- Unblocked zzz-to-char.--- End Message ---
Bug#925461: marked as done (unblock: pypy/7.0.0+dfsg-3, backports.functools-lru-cache/1.5-3)
Your message dated Sat, 30 Mar 2019 12:08:07 +0100
with message-id <20190330110805.itzfsn6aw73ps...@debian.org>
and subject line Re: unblock: pypy/7.0.0+dfsg-3,
backports.functools-lru-cache/1.5-3
has caused the Debian Bug report #925461,
regarding unblock: pypy/7.0.0+dfsg-3, backports.functools-lru-cache/1.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.)
--
925461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925461
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 pypy & backports.functools-lru-cache.
A relatively last-minute feature in pypy was namespace package support
(#920899). Unfortunately the path I picked isn't what dh_pypy (in
dh-python) implemented, and I think Piotr's rationale for that was
reasonable. But I didn't notice the incompatibility until after the
freeze.
So, #924676 and #924677.
debdiffs attached.
unblock pypy/7.0.0+dfsg-3
unblock backports.functools-lru-cache/1.5-3
Thanks,
SR
diff -Nru pypy-7.0.0+dfsg/debian/changelog pypy-7.0.0+dfsg/debian/changelog
--- pypy-7.0.0+dfsg/debian/changelog2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/changelog2019-03-24 11:07:07.0 -0400
@@ -1,3 +1,12 @@
+pypy (7.0.0+dfsg-3) unstable; urgency=medium
+
+ * Update watch file regex, upstream calls it pypy2.7 now.
+ * pypycompile and pypyclean now read namespaces from /usr/share/pypy/ns
+(following dh_pypy). (Closes: #924676)
+- Breaks old pypy-backports.functools-lru-cache, using the old location.
+
+ -- Stefano Rivera Sun, 24 Mar 2019 11:07:07 -0400
+
pypy (7.0.0+dfsg-2) unstable; urgency=medium
* Remove dh_builddeb override, no longer necessary.
diff -Nru pypy-7.0.0+dfsg/debian/control pypy-7.0.0+dfsg/debian/control
--- pypy-7.0.0+dfsg/debian/control 2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/control 2019-03-24 11:07:07.0 -0400
@@ -18,8 +18,8 @@
procps,
pypy [any-amd64 any-i386 armhf ppc64 ppc64el s390x] ,
python (>= 2.6.6-11~),
- python-pycparser,
python-docutils,
+ python-pycparser,
python-sphinx (>= 1.0.7+dfsg),
python2.7-dev,
tcl-dev,
@@ -36,7 +36,9 @@
Package: pypy
Architecture: any
Depends: pypy-lib (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
-Breaks: pypy-dev (<< ${source:Version})
+Breaks:
+ pypy-backports.functools-lru-cache (<< 1.5-3~),
+ pypy-dev (<< ${source:Version})
Provides: ${pypy-abi}
Suggests: pypy-doc, pypy-tk (= ${binary:Version})
Pre-Depends: dpkg (>= 1.15.6~), ${misc:Pre-Depends}
diff -Nru pypy-7.0.0+dfsg/debian/copyright pypy-7.0.0+dfsg/debian/copyright
--- pypy-7.0.0+dfsg/debian/copyright2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/copyright2019-03-24 11:07:07.0 -0400
@@ -206,7 +206,7 @@
Floris Bruynooghe
Christopher Pope
Tristan Arthur
- Christian Tismer
+ Christian Tismer
Dan Stromberg
Carl Meyer
Florin Papa
diff -Nru pypy-7.0.0+dfsg/debian/pypy.dirs pypy-7.0.0+dfsg/debian/pypy.dirs
--- pypy-7.0.0+dfsg/debian/pypy.dirs2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.dirs2019-03-24 11:07:07.0 -0400
@@ -1,2 +1,2 @@
+/usr/share/pypy/ns
/usr/local/lib/pypy2.7/dist-packages
-/usr/lib/pypy/ns
diff -Nru pypy-7.0.0+dfsg/debian/pypy.install
pypy-7.0.0+dfsg/debian/pypy.install
--- pypy-7.0.0+dfsg/debian/pypy.install 2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.install 2019-03-24 11:07:07.0 -0400
@@ -2,5 +2,5 @@
debian/scripts/pypycompile/usr/bin
include/pypy_*.h /usr/lib/pypy/include
lib_pypy/_*_cffi.*.so /usr/lib/pypy/lib_pypy
-pypy/goal/pypy-c /usr/lib/pypy/bin
pypy/goal/libpypy-c.so/usr/lib/pypy/bin
+pypy/goal/pypy-c /usr/lib/pypy/bin
diff -Nru pypy-7.0.0+dfsg/debian/pypy.links pypy-7.0.0+dfsg/debian/pypy.links
--- pypy-7.0.0+dfsg/debian/pypy.links 2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.links 2019-03-24 11:07:07.0 -0400
@@ -1,2 +1,2 @@
-/usr/lib/pypy/bin/pypy-c /usr/bin/pypy
/usr/lib/pypy/bin/libpypy-c.so /usr/lib/libpypy-c.so
+/usr/lib/pypy/bin/pypy-c /usr/bin/pypy
diff -Nru pypy-7.0.0+dfsg/debian/scripts/pypyclean
pypy-7.0.0+dfsg/debian/scripts/pypyclean
--- pypy-7.0.0+dfsg/debian/scripts/pypyclean2019-02-12 17:41:21.0
-0500
+++ pypy-7.0.0+dfsg/debian/scripts/pypyclean2019-03-24 11:07:07.0
-0400
@@ -31,7 +31,7
Bug#919395: Heads up to release team about MariadB 10.3
Hi, On 3/23/19 2:26 AM, Andreas Beckmann wrote: On 2019-03-20 12:28, Emilio Pozuelo Monfort wrote: On 20/03/2019 00:49, Andreas Beckmann wrote: please give-back qt4-x11. A build has succeeded today in my pbuilder sid Scheduled. That worked. What needs to be done to make the three late binNMUs migrate to testing? Does not seem to happen on its own ... BinNMUs and new binaries also need an unblock during the freeze (this was a fairy recent change in britney), so they didn't migrate on their own. I unblocked them and they migrated. Ivo
Bug#925452: marked as done (unblock: pkg-kde-tools/0.15.29)
Your message dated Sat, 30 Mar 2019 11:58:40 +0100
with message-id <20190330105838.4n52c457tfz35...@debian.org>
and subject line Re: unblock: pkg-kde-tools/0.15.29
has caused the Debian Bug report #925452,
regarding unblock: pkg-kde-tools/0.15.29
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.)
--
925452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release team, please unblock package pkg-kde-tools.
It fixes a bug of severity important: #905736.
Additionally there are some minor changes related to updating URLs from
Alioth to Salsa. These were committed to our Git, I thought these can count
as “documentation fixes”, so I did not revert them.
The debdiff between 0.15.28 and 0.15.29 is attached.
unblock pkg-kde-tools/0.15.29
Also, can you please binNMU src:qtquickcontrols2-opensource-src against this
version of pkg-kde-tools? That will fix bug #905738 in Buster (currently it
is only fixed in experimental). If needed I can file a separate bug for that.
nmu qtquickcontrols2-opensource-src_5.11.3+dfsg-2 . ANY . -m 'Rebuild against
fixed pkg-kde-tools, see #905738'
--
Dmitry Shachnev
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+pkg-kde-tools (0.15.29) unstable; urgency=medium
+
+ [ Kunal Mehta ]
+ * Replace broken alioth URLs in man pages (Closes: #905845).
+
+ [ Simon Quigley ]
+ * Bump Standards-version to 4.1.4, no changes needed.
+ * Run wrap-and-sort.
+
+ [ Dmitry Shachnev ]
+ * Update Vcs fields for move to salsa.debian.org.
+
+ [ Andreas Ferber ]
+ * dh_qmlcdeps: don't exit on first package without qmlc files (Closes:
+#905736).
+
+ -- Dmitry Shachnev Sun, 24 Mar 2019 13:19:34 +0300
+
pkg-kde-tools (0.15.28) unstable; urgency=medium
* Bump libdpkg-perl build-dependency too, to make the tests pass.
--- a/debian/control
+++ b/debian/control
@@ -3,15 +3,15 @@ Section: devel
Priority: optional
Maintainer: Debian Qt/KDE Maintainers
Build-Depends: cmake (>= 2.6.4), debhelper (>= 9), libdpkg-perl (>= 1.19.0~)
-Standards-Version: 4.1.1
+Standards-Version: 4.1.4
Uploaders: Sune Vuorela ,
Modestas Vainius ,
Maximiliano Curia ,
Lisandro Damián Nicanor Pérez Meyer ,
Pino Toscano ,
- Dmitry Shachnev ,
-Vcs-Git: https://anonscm.debian.org/git/pkg-kde/pkg-kde-tools.git
-Vcs-Browser: https://anonscm.debian.org/git/pkg-kde/pkg-kde-tools.git
+ Dmitry Shachnev
+Vcs-Git: https://salsa.debian.org/qt-kde-team/pkg-kde-tools.git
+Vcs-Browser: https://salsa.debian.org/qt-kde-team/pkg-kde-tools
Package: pkg-kde-tools
Architecture: all
--- a/dh_qmlcdeps
+++ b/dh_qmlcdeps
@@ -75,7 +75,7 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
}
}, $tmpdir);
-$qt_version_bin or exit(0);
+$qt_version_bin or next;
my @qt_version = unpack("C4", $qt_version_bin);
my $qt_version_str = "$qt_version[2].$qt_version[1].$qt_version[0]";
$qt_version[2] == 5 or error("Qt version $qt_version_str is not supported");
--- a/man1/pkgkde-gensymbols.1
+++ b/man1/pkgkde-gensymbols.1
@@ -104,7 +104,7 @@ the
.BR dpkg-gensymbols (1)
man page.
.SH SEE ALSO
-.BR http://pkg-kde.alioth.debian.org/symbolfiles.html
+.BR https://qt-kde-team.pages.debian.net/symbolfiles.html
.br
.BR https://people.redhat.com/drepper/symbol\-versioning
.br
--- a/man1/pkgkde-symbolshelper.1
+++ b/man1/pkgkde-symbolshelper.1
@@ -85,7 +85,7 @@ pkgkde-symbolshelper batchpatch -v 1.8 foo_unstable_logs/foo_1.8-1*.build
This man page was based text written by others from the pkg-kde
symbols file help page.
.SH SEE ALSO
-.BR http://pkg-kde.alioth.debian.org/symbolfiles.html
+.BR https://qt-kde-team.pages.debian.net/symbolfiles.html
.br
.BR https://people.redhat.com/drepper/symbol\-versioning
.br
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Mon, Mar 25, 2019 at 01:07:24PM +0300, Dmitry Shachnev wrote:
> Subject: unblock: pkg-kde-tools/0.15.29
Unblocked by Niels.
Ivo--- End Message ---
Bug#925474: marked as done (unblock: python-aioxmpp/0.10.3-3)
Your message dated Sat, 30 Mar 2019 11:59:18 +0100
with message-id <20190330105917.nplkqkctkxtdw...@debian.org>
and subject line Re: unblock: python-aioxmpp/0.10.3-3
has caused the Debian Bug report #925474,
regarding unblock: python-aioxmpp/0.10.3-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.)
--
925474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925474
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-aioxmpp
Fixes the FTBFS issue #924801 by backporting an upstream commit.
diff -Nru python-aioxmpp-0.10.3/debian/changelog python-
aioxmpp-0.10.3/debian/changelog
--- python-aioxmpp-0.10.3/debian/changelog 2019-02-23 16:54:49.0
+0100
+++ python-aioxmpp-0.10.3/debian/changelog 2019-03-21 17:00:14.0
+0100
@@ -1,3 +1,15 @@
+python-aioxmpp (0.10.3-3) unstable; urgency=medium
+
+ * Fix test failure due to updated Python 3.7. This applies the
+unreleased upstream commit 13ab00d [1].
+
+[1]: https://github.com/horazont/aioxmpp/commit/
+ 13ab00d64094b9a13d9d6984d7509bb40efb1fce
+
+closes: #924801
+
+ -- Jonas Schäfer Thu, 21 Mar 2019 17:00:14 +0100
+
python-aioxmpp (0.10.3-2) unstable; urgency=medium
* Use CI=true mode [1] for tests during package build, to prevent
diff -Nru python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
--- python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
1970-01-01 01:00:00.0 +0100
+++ python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
2019-03-21 17:00:14.0 +0100
@@ -0,0 +1,20 @@
+diff --git a/tests/xso/test_model.py b/tests/xso/test_model.py
+index b6d2e29..b1a2a75 100644
+--- a/tests/xso/test_model.py
b/tests/xso/test_model.py
+@@ -2200,13 +2200,9 @@ class TestXSO(XMLTestCase):
+ )
+
+ def test_init_takes_no_arguments(self):
+-with self.assertRaisesRegex(
+-TypeError,
+-r"takes no (parameters|arguments)"):
++with self.assertRaises(TypeError):
+ xso.XSO("foo")
+-with self.assertRaisesRegex(
+-TypeError,
+-r"takes no (parameters|arguments)"):
++with self.assertRaises(TypeError):
+ xso.XSO(bar="foo")
+
+ def test_init_forwards_to_base_class(self):
diff -Nru python-aioxmpp-0.10.3/debian/patches/series python-
aioxmpp-0.10.3/debian/patches/series
--- python-aioxmpp-0.10.3/debian/patches/series 2019-01-12 22:35:42.0
+0100
+++ python-aioxmpp-0.10.3/debian/patches/series 2019-03-21 17:00:14.0
+0100
@@ -1,3 +1,4 @@
workaround-dh_python3-dep-issue.patch
remove-github-button.patch
remove-ci-buttons.patch
+python37-tests-compat.patch
unblock python-aioxmpp/0.10.3-3
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-
debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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
--- End Message ---
--- Begin Message ---
Hi,
On Mon, Mar 25, 2019 at 04:26:55PM +0100, Jonas Schäfer wrote:
> Subject: unblock: python-aioxmpp/0.10.3-3
Unblocked by jmw.
Ivo--- End Message ---
Bug#923184: unblock: qgis/3.4.6+dfsg-1
Control: retitle -1 unblock: qgis/3.4.6+dfsg-1 On 3/17/19 11:43 PM, Sebastiaan Couwenberg wrote: > On 3/17/19 8:17 PM, Sebastiaan Couwenberg wrote: >> On 2/24/19 9:23 PM, Bas Couwenberg wrote: >>> Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the >>> latter in buster is probably better than leaving the qgis package at the >>> last 2.18.x release (2.18.28). >>> >>> QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such >>> the changes since the version in testing are quite large and cannot be >>> considered "small, targeted fixes". >>> >>> While users of the qgis package are unlikely to use the version of the >>> package available in stable, and more likely using the latest LTR from >>> backports, I think having 3.4.5 in buster is better for users upgrading >>> from stretch than leaving them with the EOL 2.18.28 release until the >>> package is updated in buster-backports. >>> >>> Would you approve of moving QGIS 3.4.5 from experimental to unstable and >>> allowing it to migrate to tesing for inclusion in buster? >>> >>> Or should we keep it experimental until after the release, and make the >>> newer LTRs available in buster-backports when it hits testing? >> >> As reported by Lucas Nussbaum in #924833, qgis (2.18.28-2) FTBFS in >> unstable due to sip4 (4.19.14+dfsg-1) which was uploaded a couple of >> weeks after qgis. >> >> With 2.18.x being EOL upstream, we cannot rely on upstream to provide a >> fix, and I lack the skills for it. >> >> I'm going to move QGIS 3.4 to unstable so that we at least have a >> version of QGIS in unstable that supports SIP 4.19.14. >> >> If the changes in QGIS 3.4 are deemed to invasive for an unblock, we'll >> have to release buster without qgis and deal with lots of unhappy users. qgis (3.4.6+dfsg-1) has been uploaded to unstable. Please unblock it, to fix the FTBFS issue (#924833) in testing. The debdiff is 477M (60M gzipped), so not attached. unblock qgis/3.4.6+dfsg-1 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Bug#923184: unblock: qgis/3.4.6+dfsg-1
Processing control commands: > retitle -1 unblock: qgis/3.4.6+dfsg-1 Bug #923184 [release.debian.org] unblock: qgis/3.4.5+dfsg-1 Changed Bug title to 'unblock: qgis/3.4.6+dfsg-1' from 'unblock: qgis/3.4.5+dfsg-1'. -- 923184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924070: marked as done ([pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-1)
Your message dated Sat, 30 Mar 2019 10:42:55 +0100 with message-id and subject line Re: [pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-1 has caused the Debian Bug report #924070, regarding [pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-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.) -- 924070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-CC: pkg-nvidia-de...@lists.alioth.debian.org User: release.debian@packages.debian.org Usertags: unblock Dear Release Team Please consider a freeze exception for a new upstream release of nvidia-cuda-toolkit. Version 10.1 adds support for GCC 8 and Clang 7. This will allow us to drop gcc-7 from buster, as the only other packages needing gcc-7 are starpu and starpu-contrib (#924012) which will follow CUDA. nvidia-cuda-toolkit is non-free and the build consists of unpacking the pre-built binaries from upstream and repacking them into several separate binary packages for Debian. At this stage, 10.0 is in experimental, and I still need to prepare the packaging for 10.1 and have it go through NEW. For what it is worth, Ubuntu completed the transition to 10.0 two weeks ago, and I intend to test and complete the 10.1 transition there as well before finally asking for an unblock for buster. Regards Graham --- End Message --- --- Begin Message --- tags 924070 wontfix Hi Graham, On Sat, 9 Mar 2019 11:11:01 +0200 Graham Inggs wrote: > Please consider a freeze exception for a new upstream release of > nvidia-cuda-toolkit. We considered. > Version 10.1 adds support for GCC 8 and Clang 7. This will allow us > to drop gcc-7 from buster, as the only other packages needing gcc-7 > are starpu and starpu-contrib (#924012) which will follow CUDA. At this stage, we don't consider dropping gcc-7 from buster important enough to warrant the large changes required by this nvidia-cuda-toolkit version to unblock. Sorry. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed (with 5 errors): Re: [pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-1
Processing commands for cont...@bugs.debian.org: > tags 924070 wontfix Bug #924070 [release.debian.org] [pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-1 Added tag(s) wontfix. > Hi Graham, Unknown command or malformed arguments to command. > On Sat, 9 Mar 2019 11:11:01 +0200 Graham Inggs wrote: Unknown command or malformed arguments to command. > > Please consider a freeze exception for a new upstream release of Unknown command or malformed arguments to command. > > nvidia-cuda-toolkit. Unknown command or malformed arguments to command. > We considered. Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 924070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926010: unblock: jcodings/1.0.43-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package jcodings jruby-joni 2.1.26 package depends on jcondings and its upstream pom.xml speficies to use 1.0.43 (so I've updated it with 2.1.26-2 https://tracker.debian.org/news/1035918/accepted-jruby-joni-2126-2-source-into-unstable/ (maybe it's better to introduce jruby-joni 2.1.26-2 if it's okay). debdiff is here. diff -Nru jcodings-1.0.42/debian/changelog jcodings-1.0.43/debian/changelog --- jcodings-1.0.42/debian/changelog2019-01-02 12:45:13.0 +0900 +++ jcodings-1.0.43/debian/changelog2019-03-09 19:07:35.0 +0900 @@ -1,3 +1,9 @@ +jcodings (1.0.43-1) unstable; urgency=medium + + * New upstream release + + -- Hideki Yamane Sat, 09 Mar 2019 19:07:35 +0900 + jcodings (1.0.42-1) unstable; urgency=medium * New upstream release diff -Nru jcodings-1.0.42/debian/patches/remove_unnecessary_dependency.patch jcodings-1.0.43/debian/patches/remove_unnecessary_dependency.patch --- jcodings-1.0.42/debian/patches/remove_unnecessary_dependency.patch 2019-01-02 12:45:13.0 +0900 +++ jcodings-1.0.43/debian/patches/remove_unnecessary_dependency.patch 2019-03-09 19:07:35.0 +0900 @@ -6,7 +6,7 @@ --- a/pom.xml +++ b/pom.xml @@ -6,11 +6,6 @@ - 1.0.42 + 1.0.43 JCodings Byte based encoding support library for java - diff -Nru jcodings-1.0.42/pom.xml jcodings-1.0.43/pom.xml --- jcodings-1.0.42/pom.xml 2018-12-28 06:09:47.0 +0900 +++ jcodings-1.0.43/pom.xml 2019-03-07 02:15:23.0 +0900 @@ -3,7 +3,7 @@ 4.0.0 org.jruby.jcodings jcodings - 1.0.42 + 1.0.43 JCodings Byte based encoding support library for java Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Adlam.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Adlam.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Age_12_0.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Age_12_0.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Alnum.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Alnum.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Alpha.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Alpha.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Assigned.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Assigned.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_C.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_C.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Case_Ignorable.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Case_Ignorable.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cased.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cased.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cf.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cf.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Casefolded.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Casefolded.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Casemapped.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Casemapped.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Lowercased.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Lowercased.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Titlecased.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Titlecased.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Changes_When_Uppercased.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Changes_When_Uppercased.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Cn.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Cn.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Common.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Common.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Devanagari.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Devanagari.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Diacritic.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Diacritic.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Digit.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Digit.bin differ Binary files /tmp/uSPXIb6K1r/jcodings-1.0.42/resources/tables/CR_Egyptian_Hieroglyphs.bin and /tmp/CFVYbctSCt/jcodings-1.0.43/resources/tables/CR_Egyptian_Hieroglyphs.bin differ Binary
Bug#926008: unblock: kicad-templates/5.1.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kicad-templates
The kicad-templates package provides additional data for prepared
electronics schematic and PCB data for the kicad application. The data
of the templates are simple text files and by this the package is
platform independent.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-templates should make it's way into Buster finally.
The update within the upstream version is small and really clear. But
also the Debian packaging got just one small update on the
Standards-Version and the updated copyright file.
diff -Nru kicad-templates-5.0.2/debian/changelog
kicad-templates-5.1.0/debian/changelog
--- kicad-templates-5.0.2/debian/changelog 2018-12-04 21:13:06.0
+0100
+++ kicad-templates-5.1.0/debian/changelog 2019-03-11 20:37:17.0
+0100
@@ -1,3 +1,12 @@
+kicad-templates (5.1.0-1) unstable; urgency=medium
+
+ * [db07e5c] New upstream version 5.1.0
+ * [98163f0] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+ * [a21730b] d/copyright: update years on contributors
+
+ -- Carsten Schoenert Mon, 11 Mar 2019 20:37:17
+0100
+
kicad-templates (5.0.2-1) unstable; urgency=medium
* [7b1e635] New upstream version 5.0.2
diff -Nru kicad-templates-5.0.2/debian/control
kicad-templates-5.1.0/debian/control
--- kicad-templates-5.0.2/debian/control2018-08-31 22:12:24.0
+0200
+++ kicad-templates-5.1.0/debian/control2019-03-11 20:36:08.0
+0100
@@ -10,7 +10,7 @@
cmake,
Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-templates.git
Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-templates
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
Homepage: https://github.com/KiCad/kicad-templates
Package: kicad-templates
diff -Nru kicad-templates-5.0.2/debian/copyright
kicad-templates-5.1.0/debian/copyright
--- kicad-templates-5.0.2/debian/copyright 2018-08-31 22:12:45.0
+0200
+++ kicad-templates-5.1.0/debian/copyright 2019-03-11 20:36:51.0
+0100
@@ -10,11 +10,11 @@
Material'."
Files: *
-Copyright: 2018 KiCad Community
+Copyright: 2019 KiCad Community
License: CC-BY-SA-4.0-with-exception
Files: debian/*
-Copyright: 2018, Carsten Schoenert
+Copyright: 2019, Carsten Schoenert
2017-2018, Jean-Samuel Reynaud
License: GPL-2+
diff -Nru kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb
kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb
--- kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb
2018-11-15 18:38:06.0 +0100
+++ kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb
2019-02-06 20:45:57.0 +0100
@@ -435,7 +435,7 @@
(net 10 "Net-(J9-Pad2)"))
(pad 8 smd rect (at 2.7 -1.905 180) (size 1.55 0.6) (layers F.Cu F.Paste
F.Mask)
(net 8 /P3V3))
-(model ${KISYS3DMOD}/Package_SOIC.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
+(model ${KISYS3DMOD}/Package_SO.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
(at (xyz 0 0 0))
(scale (xyz 1 1 1))
(rotate (xyz 0 0 0))
unblock kicad-templates/5.1.0-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Update for roysindre.no
Dear roysindre.no Team, I am Sivam, IT Business Consultant from India. I found your website is not mobile friendly and not updated as per the Google's guidelines. If you wish, we can redesign your website and make it professional, stylish, responsive and search engine friendly. Our Designing packages starts just at USD 299 Let me know if you are interested. I will send you quote, past working examples, client testimonials and company profile. Best Regards, Sivam IT Business Consultant +91-9437528896
Bug#926007: unblock: kicad-symbols/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-symbols The kicad-symbols package provides additional data for schematic symbols for the kicad application. The schematic symbols data are simple text files and by this the package is platform independent. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-symbols should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-symbols-full.debdiff.tar.xz The modification of the debian folder between the version in testing and unstable is on contray really small. diff -puNr -puNr kicad-symbols-5.0.2/debian/changelog kicad-symbols-5.1.0/debian/changelog --- kicad-symbols-5.0.2/debian/changelog2018-12-04 21:07:58.0 +0100 +++ kicad-symbols-5.1.0/debian/changelog2019-03-11 20:26:47.0 +0100 @@ -1,3 +1,12 @@ +kicad-symbols (5.1.0-1) unstable; urgency=medium + + * [e0c482d] New upstream version 5.1.0 + * [ffcb043] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [591c592] d/copyright: update years on contributors + + -- Carsten Schoenert Mon, 11 Mar 2019 20:26:47 +0100 + kicad-symbols (5.0.2-1) unstable; urgency=medium * [97acd5a] New upstream version 5.0.2 diff -puNr -puNr kicad-symbols-5.0.2/debian/control kicad-symbols-5.1.0/debian/control --- kicad-symbols-5.0.2/debian/control 2018-08-31 22:04:13.0 +0200 +++ kicad-symbols-5.1.0/debian/control 2019-03-11 20:26:41.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/symbols Package: kicad-symbols diff -puNr -puNr kicad-symbols-5.0.2/debian/copyright kicad-symbols-5.1.0/debian/copyright --- kicad-symbols-5.0.2/debian/copyright2018-08-31 22:04:17.0 +0200 +++ kicad-symbols-5.1.0/debian/copyright2019-03-11 20:26:41.0 +0100 @@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018 KiCad Community +Copyright: 2019 KiCad Community License: CC-BY-SA-4.0-with-exception Files: debian/* -Copyright: 2018, Carsten Schoenert +Copyright: 2019, Carsten Schoenert 2017-2018, Jean-Samuel Reynaud License: GPL-2+ unblock kicad-symbols/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926006: unblock: kicad-packages3d/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-packages3d The kicad-packages3d package provides additional data of 3D-models for the kicad application. The 3D-models data are simple text files and by this the package is platform independent. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-packages3d should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-packages3d-full.debdiff.tar.xz A diff for the debian folder between the version in testing and unstable is about 95% changes to the debian/copyright file and the helper files of cme around this. The remaining about 5% is on updating the Standards-Versions and the new debian/changelog entry as no other modifications to the packaging was required. diff -puNr -puNr kicad-packages3d-5.0.2/debian/changelog kicad-packages3d-5.1.0/debian/changelog --- kicad-packages3d-5.0.2/debian/changelog 2018-12-06 16:47:58.0 +0100 +++ kicad-packages3d-5.1.0/debian/changelog 2019-03-15 20:15:27.0 +0100 @@ -1,3 +1,14 @@ +kicad-packages3d (5.1.0-1) unstable; urgency=medium + + * [674fff9] New upstream version 5.1.0 + * [387d52f] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [90c3af4] copyright: add some additional information for cme script ++ Add some helping content into debian/fill.copyright.blanks.yml. + * [581a7ec] copyright: update information due release of 5.1.0 + + -- Carsten Schoenert Fri, 15 Mar 2019 20:15:27 +0100 + kicad-packages3d (5.0.2-1) unstable; urgency=medium * [aeb1d03] New upstream version 5.0.2 diff -puNr -puNr kicad-packages3d-5.0.2/debian/control kicad-packages3d-5.1.0/debian/control --- kicad-packages3d-5.0.2/debian/control 2018-08-31 21:43:47.0 +0200 +++ kicad-packages3d-5.1.0/debian/control 2019-03-15 00:26:53.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/packages3d Package: kicad-packages3d diff -puNr -puNr kicad-packages3d-5.0.2/debian/copyright kicad-packages3d-5.1.0/debian/copyright --- kicad-packages3d-5.0.2/debian/copyright 2018-08-31 21:44:08.0 +0200 +++ kicad-packages3d-5.1.0/debian/copyright 2019-03-15 20:09:48.0 +0100 @@ -10,10 +10,17 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018, KiCad Community +Copyright: 2018, 2019, KiCad Community License: CC-BY-SA-4.0-with-exception [snip] [a lot of other modifications to d/copyright] The full diff for the debian folder I've uploaded again to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-packages3d.debian-folder.debdiff unblock kicad-packages3d/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926005: unblock: kicad-footprints/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-footprints The kicad-footprints package provides basic footprint data for the kicad application. The footprint data are simple text files and by this the package is platform independet. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-footprints should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-footprints-full.debdiff.tar.xz The modification of the debian folder between the version in testing and unstable is on contray really small. $ diff -puNr kicad-footprints-5.0.2/debian/ kicad-footprints-5.1.0/debian/ diff -puNr kicad-footprints-5.0.2/debian/changelog kicad-footprints-5.1.0/debian/changelog --- kicad-footprints-5.0.2/debian/changelog 2018-12-04 21:05:30.0 +0100 +++ kicad-footprints-5.1.0/debian/changelog 2019-03-11 19:58:05.0 +0100 @@ -1,3 +1,12 @@ +kicad-footprints (5.1.0-1) unstable; urgency=medium + + * [b602791] New upstream version 5.1.0 + * [22436a1] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [d70afad] d/copyright: update years on contributors + + -- Carsten Schoenert Mon, 11 Mar 2019 19:58:05 +0100 + kicad-footprints (5.0.2-1) unstable; urgency=medium * [de61c7a] New upstream version 5.0.2 diff -puNr kicad-footprints-5.0.2/debian/control kicad-footprints-5.1.0/debian/control --- kicad-footprints-5.0.2/debian/control 2018-08-31 21:19:42.0 +0200 +++ kicad-footprints-5.1.0/debian/control 2019-03-11 19:55:15.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/footprints Package: kicad-footprints diff -puNr kicad-footprints-5.0.2/debian/copyright kicad-footprints-5.1.0/debian/copyright --- kicad-footprints-5.0.2/debian/copyright 2018-08-31 21:20:48.0 +0200 +++ kicad-footprints-5.1.0/debian/copyright 2019-03-11 19:55:43.0 +0100 @@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018 KiCad Community +Copyright: 2019 KiCad Community License: CC-BY-SA-4.0-with-exception Files: debian/* -Copyright: 2018, Carsten Schoenert +Copyright: 2019, Carsten Schoenert 2017-2018, Jean-Samuel Reynaud License: GPL-2+ unblock kicad-footprints/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926004: unblock: kicad/5.1.0+dfsg1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kicad
The KiCad binary packages based on upstream 5.0.2 (the current version
in testing from December 2018) are build with GTK2+ bindings which has
now some important downsides for the usability of KiCad. The upstream
developers are aware of this and have worked on pushing the KiCad
applications to work and use GTK3+ bindings. They released the new
version 5.1.0 about two weeks ago which addresses also a move over to
provide a Python3 library and dropping the old Python2 library instead.
Furthermore some additional possible UI stuff mainly provided by
external extension, that are based on wxWidgets and wxPython4, aren't
working with the version from testing due the GTK3+ binding in
the wxWidgets libaries.
And as usual a lot of small bug fixes did happen between the two
released versions.
The binary packages from src:kicad have no reverse dependencies nor
providing any public library (besides the Python3 library) so there are
no problems to be expected by the update at least I don't now any of
them.
In the past I've provided snapshots of the ongoing development including
release candidates of 5.1.0 in experimental and based on the feedback
from the KiCad forum and community no big issues nor packaging problem
got reported so I finally uploaded the 5.1.0 release to unstable. Also
here since the upload no new bug reports nor issues in forum got
reported, in contrary people start asking then KiCad 5.1.0 will be
available in testing and finally in the Buster release. :)
In all the reported issues against KiCad are really just a few,
currently we have 5 reports.
The resulting full debdiff between 5.0.2 from testing and 5.1.0 is
rather big due a natural lot of changes within the upstream source.
I uploaded a compressed version of the (full) debdiff to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-full.debdiff.tar.xz
The probably more interesting things are the differences within the debian
folder. I created a dedicated diff on this that is also available on
p.d.o as I'm not sure it the list will accept the plain file due size
limitations.
https://people.debian.org/~tijuca/unblock/kicad.debian-folder.debdiff
To summarize the Debian specific changes here:
* Adopt the build dependencies so the build is using wxWidgest GTK3+
based packages.
* Adjust a dedicated (binary) package dependency to use python-wxgtk3.0
which is linked against wxgtk3.0 with GTK3+ symbols, needed for the
internal KiCad scripting interface.
* Use Clang instead of GCC as compiler as the required GLM library >=
0.9.9.3 uses the C++ standard in it's "own" way which Clang is able to
work with, GCC7 is not.
* The Dutch documentation got dropped as not updated since at least on
release cycle.
* Upstream is providing a lot more of documentation in 5.1.0 which are
finally packaged in kicad-doc-{en,it,ru,zh}, no new binary packages.
* As usual a lot of updates to d/copyright due the changes happen to the
source.
* The build of the documentation of the final 5.1.0 needs a workaround as
the cmake system otherwise is puzzled and breaks a successful build.
(Since my package upload the root for this issue got identified and
will get fixed in future upstream updates.)
unblock kicad/5.1.0+dfsg1-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#924278: stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1
On Wed, 27 Mar 2019 19:43:13 + "Adam D. Barratt" wrote: > On Wed, 2019-03-27 at 19:54 +0100, Sebastian Andrzej Siewior wrote: > > On 2019-03-10 23:55:55 [+0100], To sub...@bugs.debian.org wrote: > > > We would like to update clamav in stable to 0.101.1 which is the > > > latest > > > release provided by upstream. > > > This won't be as easy as it was previously because it will trigger > > > a > > > transistion (libclamav7 -> libclamav9) in stable similar to what we > > > did > > > in unstable (#922004) recently. > > > > upstream released 0.100.3 which fixes three bugs with CVE numbers > > [0]. > > There is also 0.101.2. > > > > For Stretch we tend to upload 0.100.3 before we get an approval for > > this > > one (which would be then 0.101.2). Since the 0.100.3 is smaller, it > > should be easier/quicker tor review. > > Is this okay? > > > > [0] https://blog.clamav.net/2019/03/clamav-01012-and-01003-patches-ha > > ve.html > > Sure. To make things easier to keep track of (at least for me), could > you open a new bug for the 0.100.3 update, and we'll keep using this > one for the effective transition. Filed (#926003). Scott K
Bug#926003: stretch-pu: package clamav/0.100.3+dfsg-0+deb9u1
On Sat, 30 Mar 2019 04:01:40 -0400 Scott Kitterman wrote: > Package: release.debian.org > Severity: normal > Tags: stretch > User: release.debian@packages.debian.org > Usertags: pu > > Clamav upstream has just done a security release. They did do a 0.100 update > so that we can get the security fixes out in advance of the pending libclamav9 > transition (#924278). Note: Since this is a security via updates update, I went ahead and uploaded it because I will be unavailable for almost all of the next 24 hours. Scott K
Bug#926002: unblock: zeromq3/4.3.1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team, Unfortunately upstream of zeromq3 broke GSSAPI detection[1] in the configure phase. It went undetected and now zeromq3 for Buster doesn't have GSSAPI support and this is a regression since Stretch. Luca Boccassi who is not just our fellow DD but also upstream fixed it with a small patch. Full debdiff is attached. Please let it migrate to Buster and have the same functionality available that's in Stretch. Thanks for consideration, Laszlo/GCS [1] https://bugs.debian.org/925914 diff -Nru zeromq3-4.3.1/debian/changelog zeromq3-4.3.1/debian/changelog --- zeromq3-4.3.1/debian/changelog 2019-01-26 12:49:45.0 + +++ zeromq3-4.3.1/debian/changelog 2019-03-28 16:37:09.0 + @@ -1,3 +1,10 @@ +zeromq3 (4.3.1-4) unstable; urgency=medium + + [ Luca Boccassi ] + * Fix GSSAPI support build (closes: #925914). + + -- Laszlo Boszormenyi (GCS) Thu, 28 Mar 2019 16:37:09 + + zeromq3 (4.3.1-3) unstable; urgency=medium [ Luca Boccassi ] diff -Nru zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch --- zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch 1970-01-01 00:00:00.0 + +++ zeromq3-4.3.1/debian/patches/gssapi_pkgconfig.patch 2019-03-28 16:37:09.0 + @@ -0,0 +1,30 @@ +Author: Luca Boccassi +Description: gssapi pkg-config check in configure.ac does not work + correctly enable the definition in platform.hpp so that the + gssapi support is actually built in if requested and available. +Origin: https://github.com/zeromq/libzmq/pull/3361 +--- a/configure.ac b/configure.ac +@@ -472,16 +472,20 @@ + # conditionally require libgssapi_krb5 + if test "x$require_libgssapi_krb5_ext" != "xno"; then + PKG_CHECK_MODULES([gssapi_krb5], [krb5-gssapi], [ ++have_gssapi_library="yes" + PKGCFG_NAMES_PRIVATE="$PKGCFG_NAMES_PRIVATE krb5-gssapi" + ], [ + AC_CHECK_HEADERS(gssapi/gssapi_generic.h) + AC_SEARCH_LIBS([gss_init_sec_context], [gssapi_krb5 gssapi], +-AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security]), ++have_gssapi_library="yes", + AC_MSG_ERROR(libgssapi_krb5 is needed for GSSAPI security)) + PKGCFG_LIBS_PRIVATE="$PKGCFG_LIBS_PRIVATE -lgssapi_krb5" + ]) + fi +-AM_CONDITIONAL(BUILD_GSSAPI, test "x$require_libgssapi_krb5_ext" != "xno") ++if test "x$have_gssapi_library" = "xyes"; then ++AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security]) ++fi ++AM_CONDITIONAL(BUILD_GSSAPI, test "x$have_gssapi_library" = "xyes") + + # Select curve encryption library, defaults to tweetnacl + # To use libsodium instead, use --with-libsodium (must be installed) diff -Nru zeromq3-4.3.1/debian/patches/series zeromq3-4.3.1/debian/patches/series --- zeromq3-4.3.1/debian/patches/series 2019-01-26 12:49:45.0 + +++ zeromq3-4.3.1/debian/patches/series 2019-03-28 16:37:09.0 + @@ -3,3 +3,4 @@ test_hardcoded_ipc_path.patch ppc64_atomic_intrinsics.patch test_pair_ipc_hurd.patch +gssapi_pkgconfig.patch
