Re: autopkgtest gating migration, nearly there. But ...
On Fri, Sep 14, 2018 at 10:39:36PM +0200, Paul Gevers wrote: > Dear all, > > We are nearly there to enable migration being gated by autopkgtest > results. Unfortunately I recently realized (after implementation and > deployment of what I thought would be the solution) that the current > situation is possibly not good enough yet. I'd like to solicit for your > help on determining the way forward. > > This e-mail is basically a follow-up of my earlier e-mail [1] about > needed improvements. Before I start with my real issue, let me note that > needs-recommends is now deprecated (it is still supported, but the docs > and lintian warn against it). So I don't bother about it anymore, except > somebody (me) still has to fix autodep8 to not emit it. > > Let me describe the problem and the current status. The migration > software (britney2) is now taking versioned dependencies, breaks and > conflicts of the binary packages from the source package that wants to > migrate into account when requesting the tests. It will add versioned > dependencies that are not in testing and it will add packages from > unstable when their version in testing is broken by (or conflicts with) > anything needed from unstable (recursively). However, it is not having > enough information to do this well (at least, I fear), because of the > following: > > 1) it only knows the Testsuite-Triggers, but it is missing possible > version information of test dependencies. (Possibly fixable by > dpkg-source, but that will take time to propagate and then the > Testsuite-Trigger field changes syntax and meaning). > > 2) @builddeps@ is not resolved by dpkg-source, so the migration software > doesn't know if build-depends should be evaluated for the list > (currently the migration software doesn't add them). (Possibly "fixable" > by always evaluating them, or possibly fixable by enhancing dpkg-source). > > 3) test dependencies generated by autodep8 are fully unknown to the > migration software. It seems (but I haven't verified properly) that e.g. > with r packages the test dependencies can be versioned as well. maybe debci could cache the actual test dependencies considered for a given package, including expansion @builddeps@ and stuff produced by autodep8, so that britney2 can query that information to calculate its required tests? a simple action plan would be: - make autopkgtst output the "expanded" control file considered for each test - make debci store that data in the database and expose it via the API (exact format TBD) - make britney2 query that API signature.asc Description: PGP signature
Uploading linux (4.18.8-1)
I intend to upload linux version 4.18.8-1 to unstable on Monday. This brings 2 upstream stable updates with many fixes, including a few security fixes. Other pending changes include: * [x86] wireless: Enable R8822BE as module (Closes: #908330) * linux-headers: Stop linking the doc directory, which is not binNMU-safe * mac80211: don't update the PM state of a peer upon a multicast frame (Closes: #887045, #886292) * [x86] Enable TI TPS6598x USB Power Delivery controller family * [x86] crypto: ccp: add timeout support in the SEV command (Closes: #908248) * [rt] Update to 4.18.7-rt5 No ABI bump is required. Ben. -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
Bug#908980: transition: qrencode (ongoing, apparently uncoordinated)
Package: release.debian.org Severity: normal User:release.debian@packages.debian.org Usertags: transition Control: forwarded -1https://release.debian.org/transitions/html/auto-qrencode.html Control: block -1 by 908929 X-Debbugs-CC:qrenc...@packages.debian.org oops, send this to the list instead of the bug submission address, resending. Hi debian-release, I thought I would let you know that there appears to be a libqrencode transition going on and this transition seems to be uncoordinated (at least I can find no recent mention of it in the debian-release archives). An automated transition tracker has been set-up at https://release.debian.org/transitions/html/auto-qrencode.html It appears that no binnmus have been scheduled in Debian for this transition yet, the packages listed as "good" either don't depend on the shared library or had a sourceful upload since the libqrencode upload. Over in raspbian our auto-binnmuer did schedule binnmus for this transition. All of them built successfully. However google-authenticator uses libqrencode through dlopen/dlsym rather than through the headers provided by libqrencode, so it needs sourceful changes (to both the upstream source and debian/control). Seehttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908929
Processed (with 1 error): transition: qrencode (ongoing, apparently uncoordinated)
Processing control commands: > forwarded -1https://release.debian.org/transitions/html/auto-qrencode.html Unknown command or malformed arguments to command. > block -1 by 908929 Bug #908980 [release.debian.org] transition: qrencode (ongoing, apparently uncoordinated) 908980 was not blocked by any bugs. 908980 was not blocking any bugs. Added blocking bug(s) of 908980: 908929 -- 908980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908965: stretch-pu: package postgrey/1.36-3+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Create the pid file in a subdirectory that is owned by the postgrey user, avoiding problems with removing or overwriting the pid file. diff -Nru postgrey-1.36/debian/changelog postgrey-1.36/debian/changelog --- postgrey-1.36/debian/changelog 2016-08-28 21:18:34.0 +0300 +++ postgrey-1.36/debian/changelog 2018-09-16 22:01:59.0 +0300 @@ -1,3 +1,12 @@ +postgrey (1.36-3+deb9u1) stretch; urgency=medium + + * Non-maintainer upload. + * debian/postgrey.init: create /var/run/postgrey if it +does not exist, patch provided by Laurent Bigonville . +(Closes: 756813, 880047) + + -- Adrian Bunk Sun, 16 Sep 2018 22:01:59 +0300 + postgrey (1.36-3) unstable; urgency=medium * debian/patches: diff -Nru postgrey-1.36/debian/postgrey.init postgrey-1.36/debian/postgrey.init --- postgrey-1.36/debian/postgrey.init 2016-08-28 21:18:34.0 +0300 +++ postgrey-1.36/debian/postgrey.init 2018-09-16 22:01:59.0 +0300 @@ -26,7 +26,7 @@ DESC="postfix greylisting daemon" DAEMON_USER=postgrey -PIDFILE=/var/run/$DAEMON_NAME.pid +PIDFILE=/var/run/postgrey/$DAEMON_NAME.pid SCRIPTNAME=/etc/init.d/$DAEMON_NAME # Gracefully exit if the package has been removed. @@ -55,6 +55,14 @@ # 0 if daemon has been started # 1 if daemon was already running # 2 if daemon could not be started + if [ ! -d /var/run/postgrey/ ] + then +mkdir /var/run/postgrey/ +chown $DAEMON_USER: /var/run/postgrey/ +chmod 0755 /var/run/postgrey/ +# Restore selinux context +[ -x /sbin/restorecon ] && /sbin/restorecon /var/run/postgrey/ + fi start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
Bug#908960: stretch-pu: package rtkit/0.11-4+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
* Move dbus and polkit from Recommends to Depends
rtkit can't do much really without either of them so bump them to Depends.
(Closes: #881342)
Read #881342 if you are interested in the nasty details of
what can happen without them.
diff -Nru rtkit-0.11/debian/changelog rtkit-0.11/debian/changelog
--- rtkit-0.11/debian/changelog 2015-10-25 00:44:21.0 +0300
+++ rtkit-0.11/debian/changelog 2018-09-16 21:49:03.0 +0300
@@ -1,3 +1,12 @@
+rtkit (0.11-4+deb9u1) stretch; urgency=medium
+
+ * Non-maintainer upload.
+ * Move dbus and polkit from Recommends to Depends
+rtkit can't do much really without either of them so bump them to Depends.
+(Closes: #881342)
+
+ -- Adrian Bunk Sun, 16 Sep 2018 21:49:03 +0300
+
rtkit (0.11-4) unstable; urgency=medium
* Remove stale ubuntu.series file.
diff -Nru rtkit-0.11/debian/control rtkit-0.11/debian/control
--- rtkit-0.11/debian/control 2015-10-25 00:44:21.0 +0300
+++ rtkit-0.11/debian/control 2018-09-16 21:49:03.0 +0300
@@ -22,11 +22,10 @@
Architecture: any
Depends:
adduser,
+ dbus,
+ policykit-1,
${misc:Depends},
${shlibs:Depends}
-Recommends:
- dbus,
- policykit-1
Description: Realtime Policy and Watchdog Daemon
RealtimeKit is a D-Bus system service that changes the
scheduling policy of user processes/threads to SCHED_RR
Bug#908958: stretch-pu: package xmotd/1.17.3b-9+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu xmotd in stretch currently just crashes. diff -Nru xmotd-1.17.3b/debian/changelog xmotd-1.17.3b/debian/changelog --- xmotd-1.17.3b/debian/changelog 2016-09-10 22:07:47.0 +0300 +++ xmotd-1.17.3b/debian/changelog 2018-09-16 21:30:35.0 +0300 @@ -1,3 +1,15 @@ +xmotd (1.17.3b-9+deb9u1) stretch; urgency=medium + + * Non-maintainer upload. + * debian/patches/bugfix/fix-warnings-hardening-build.patch: +- Fix most compile time warnings and avoid crash with hardening + flags (acknowledgments to Christoph Pleger for the patch) + (Closes: #889740). +- Backported to stretch is a partial version of this patch + sufficient to fix the crash. + + -- Adrian Bunk Sun, 16 Sep 2018 21:30:35 +0300 + xmotd (1.17.3b-9) unstable; urgency=medium * Make debian/copyright DEP5 compliant. diff -Nru xmotd-1.17.3b/debian/patches/bugfix/fix-warnings-hardening-build.patch xmotd-1.17.3b/debian/patches/bugfix/fix-warnings-hardening-build.patch --- xmotd-1.17.3b/debian/patches/bugfix/fix-warnings-hardening-build.patch 1970-01-01 02:00:00.0 +0200 +++ xmotd-1.17.3b/debian/patches/bugfix/fix-warnings-hardening-build.patch 2018-09-16 21:30:35.0 +0300 @@ -0,0 +1,75 @@ +Remove compiler and linker warnings +Index: xmotd-1.17.3b/atom.c +=== +--- xmotd-1.17.3b.orig/atom.c 2018-02-13 10:44:27.104309051 +0100 xmotd-1.17.3b/atom.c 2018-02-13 10:44:27.096309028 +0100 +@@ -29,6 +29,7 @@ + */ + #include + ++#include + #include + #include + #include +Index: xmotd-1.17.3b/textmode.c +=== +--- xmotd-1.17.3b.orig/textmode.c 2018-02-13 10:44:27.104309051 +0100 xmotd-1.17.3b/textmode.c 2018-02-13 10:44:27.096309028 +0100 +@@ -40,6 +40,9 @@ + #include + + #include "maindefs.h" ++#include "prototypes.h" ++ ++extern time_t motdChanged(); + + void + runInTextMode(argc, argv) +Index: xmotd-1.17.3b/xmotd.c +=== +--- xmotd-1.17.3b.orig/xmotd.c 2018-02-13 10:44:27.104309051 +0100 xmotd-1.17.3b/xmotd.c 2018-02-13 11:06:49.756282943 +0100 +@@ -70,6 +70,7 @@ + + #include "maindefs.h" + #include "main.h" ++#include "prototypes.h" + + extern time_t motdChanged(); + extern messageptr freeMessage(); +Index: xmotd-1.17.3b/Imakefile +=== +--- xmotd-1.17.3b.orig/Imakefile 2018-02-13 10:44:27.104309051 +0100 xmotd-1.17.3b/Imakefile2018-02-13 10:44:27.096309028 +0100 +@@ -60,7 +60,7 @@ + + SRCS = main.c xmotd.c changed.c textmode.c usage.c browser.c logo.c atom.c + OBJS = main.o xmotd.o changed.o textmode.o usage.o browser.o logo.o atom.o +-INCLS = maindefs.h appdefs.h main.h ++INCLS = maindefs.h appdefs.h main.h prototypes.h + + CDEBUGFLAGS = -g + MANSUFFIX = 8 +Index: xmotd-1.17.3b/Makefile +=== +--- xmotd-1.17.3b.orig/Makefile2018-02-13 10:44:27.104309051 +0100 xmotd-1.17.3b/Makefile 2018-02-13 10:44:27.096309028 +0100 +@@ -497,7 +497,7 @@ + + SRCS = main.c xmotd.c changed.c textmode.c usage.c browser.c logo.c atom.c + OBJS = main.o xmotd.o changed.o textmode.o usage.o browser.o logo.o atom.o +-INCLS = maindefs.h appdefs.h main.h ++INCLS = maindefs.h appdefs.h main.h prototypes.h + + CDEBUGFLAGS = -g + MANSUFFIX = 8 +Index: xmotd-1.17.3b/prototypes.h +=== +--- /dev/null 1970-01-01 00:00:00.0 + xmotd-1.17.3b/prototypes.h 2018-02-13 10:46:01.608588566 +0100 +@@ -0,0 +1,5 @@ ++#ifndef _XMOTD_PROTOTYPES_H ++#define _XMOTD_PROTOTYPES_H ++void updateTimeStamp(char *motdfile); ++char * getTimeStampName(void); ++#endif diff -Nru xmotd-1.17.3b/debian/patches/series xmotd-1.17.3b/debian/patches/series --- xmotd-1.17.3b/debian/patches/series 2016-09-10 22:07:47.0 +0300 +++ xmotd-1.17.3b/debian/patches/series 2018-09-16 21:30:35.0 +0300 @@ -6,3 +6,4 @@ debian/enable-xpm.diff -p1 debian/html-support-gone.diff -p1 debian/unqualify-xmotd-in-manpage.diff -p1 +bugfix/fix-warnings-hardening-build.patch
Bug#908956: stretch-pu: package gphoto2-cffi/0.3~a1-1.1~deb9u1
Thanks for noticing that this also affects stable and should be fixed there. I should have noticed that too, in hindsight. On Sun, 16 Sep 2018 at 19:45, Adrian Bunk wrote: > Package: release.debian.org > Severity: normal > Tags: stretch > User: release.debian@packages.debian.org > Usertags: pu > > python3-gphoto2cffi in stretch is currently completely > broken, just trying to import it fails: > > $ python3 > Python 3.5.3 (default, Jan 19 2017, 14:11:04) > [GCC 6.3.0 20170118] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> import gphoto2cffi > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/gphoto2cffi/__init__.py", line 1, > in > from .gphoto2 import (Camera, list_cameras, supported_cameras, > File "/usr/lib/python3/dist-packages/gphoto2cffi/gphoto2.py", line 15, > in > from . import errors, backend > File "/usr/lib/python3/dist-packages/gphoto2cffi/backend.py", line 56, > in > 'extract_exif': _lib.GP_FILE_OPERATION_EXIF}) > File "/usr/lib/python3.5/enum.py", line 243, in __call__ > return cls._create_(value, names, module=module, qualname=qualname, > type=type, start=start) > File "/usr/lib/python3.5/enum.py", line 343, in _create_ > enum_class = metacls.__new__(metacls, class_name, bases, classdict) > File "/usr/lib/python3.5/enum.py", line 114, in __new__ > enum_class = super().__new__(metacls, cls, bases, classdict) > TypeError: type() argument 1 must be str, not bytes > >>> > -- Best regards, Aigars Mahinovsmailto:aigar...@debian.org #--# | .''`.Debian GNU/Linux (http://www.debian.org)| | : :' : Latvian Open Source Assoc. (http://www.laka.lv) | | `. `'Linux Administration and Free Software Consulting | | `- (http://www.aiteki.com) | #--#
Bug#908957: stretch-pu: package z3/4.4.1-0.4~deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Installing multiple architectures of python-z3 at the
same time fails during installation, remove the incorrect
Multi-Arch: same.
diff -Nru z3-4.4.1/debian/changelog z3-4.4.1/debian/changelog
--- z3-4.4.1/debian/changelog 2016-09-26 08:28:12.0 +0300
+++ z3-4.4.1/debian/changelog 2018-09-16 20:46:04.0 +0300
@@ -1,3 +1,18 @@
+z3 (4.4.1-0.4~deb9u1) stretch; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for stretch.
+
+ -- Adrian Bunk Sun, 16 Sep 2018 20:46:04 +0300
+
+z3 (4.4.1-0.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove the incorrect Multi-Arch: same of python-z3,
+thanks to Helmut Grohne. (Closes: #874237)
+
+ -- Adrian Bunk Sun, 09 Sep 2018 22:28:32 +0300
+
z3 (4.4.1-0.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru z3-4.4.1/debian/control z3-4.4.1/debian/control
--- z3-4.4.1/debian/control 2016-07-20 14:07:58.0 +0300
+++ z3-4.4.1/debian/control 2018-09-09 22:28:32.0 +0300
@@ -61,7 +61,6 @@
Package: python-z3
Section: python
Architecture: any
-Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: libz3-dev (= ${binary:Version}), ${misc:Depends}, ${python:Depends},
${shlibs:Depends}
Description: theorem prover from Microsoft Research - Python bindings
Bug#908956: stretch-pu: package gphoto2-cffi/0.3~a1-1.1~deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
python3-gphoto2cffi in stretch is currently completely
broken, just trying to import it fails:
$ python3
Python 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170118] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gphoto2cffi
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gphoto2cffi/__init__.py", line 1, in
from .gphoto2 import (Camera, list_cameras, supported_cameras,
File "/usr/lib/python3/dist-packages/gphoto2cffi/gphoto2.py", line 15, in
from . import errors, backend
File "/usr/lib/python3/dist-packages/gphoto2cffi/backend.py", line 56, in
'extract_exif': _lib.GP_FILE_OPERATION_EXIF})
File "/usr/lib/python3.5/enum.py", line 243, in __call__
return cls._create_(value, names, module=module, qualname=qualname,
type=type, start=start)
File "/usr/lib/python3.5/enum.py", line 343, in _create_
enum_class = metacls.__new__(metacls, class_name, bases, classdict)
File "/usr/lib/python3.5/enum.py", line 114, in __new__
enum_class = super().__new__(metacls, cls, bases, classdict)
TypeError: type() argument 1 must be str, not bytes
>>>
diff -Nru gphoto2-cffi-0.3~a1/debian/changelog
gphoto2-cffi-0.3~a1/debian/changelog
--- gphoto2-cffi-0.3~a1/debian/changelog2016-04-04 22:28:11.0
+0300
+++ gphoto2-cffi-0.3~a1/debian/changelog2018-09-16 20:31:17.0
+0300
@@ -1,3 +1,17 @@
+gphoto2-cffi (0.3~a1-1.1~deb9u1) stretch; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for stretch.
+
+ -- Adrian Bunk Sun, 16 Sep 2018 20:31:17 +0300
+
+gphoto2-cffi (0.3~a1-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add upstream fix to unbreak python3-gphoto2cffi. (Closes: #896238)
+
+ -- Adrian Bunk Mon, 27 Aug 2018 22:41:25 +0300
+
gphoto2-cffi (0.3~a1-1) unstable; urgency=low
* Updated upstream version merging changes
diff -Nru
gphoto2-cffi-0.3~a1/debian/patches/0001-Make-enum-descriptors-strs-not-bytestrings-7.patch
gphoto2-cffi-0.3~a1/debian/patches/0001-Make-enum-descriptors-strs-not-bytestrings-7.patch
---
gphoto2-cffi-0.3~a1/debian/patches/0001-Make-enum-descriptors-strs-not-bytestrings-7.patch
1970-01-01 02:00:00.0 +0200
+++
gphoto2-cffi-0.3~a1/debian/patches/0001-Make-enum-descriptors-strs-not-bytestrings-7.patch
2018-08-27 22:34:41.0 +0300
@@ -0,0 +1,43 @@
+From 88ed97764365fea5f72a6f2c9aba0323b7fd93a8 Mon Sep 17 00:00:00 2001
+From: Johannes Baiter
+Date: Thu, 7 Jul 2016 16:14:37 +0200
+Subject: Make enum descriptors strs, not bytestrings (#7)
+
+---
+ gphoto2cffi/backend.py | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/gphoto2cffi/backend.py b/gphoto2cffi/backend.py
+index c49db11..21edc4b 100644
+--- a/gphoto2cffi/backend.py
b/gphoto2cffi/backend.py
+@@ -48,7 +48,7 @@ LOG_LEVELS = {
+ _lib.GP_LOG_DEBUG: logging.DEBUG}
+
+
+-FILE_OPS = IntEnum(b'FileOperations', {
++FILE_OPS = IntEnum('FileOperations', {
+ 'remove': _lib.GP_FILE_OPERATION_DELETE,
+ 'extract_preview': _lib.GP_FILE_OPERATION_PREVIEW,
+ 'extract_raw': _lib.GP_FILE_OPERATION_RAW,
+@@ -56,7 +56,7 @@ FILE_OPS = IntEnum(b'FileOperations', {
+ 'extract_exif': _lib.GP_FILE_OPERATION_EXIF})
+
+
+-CAM_OPS = IntEnum(b'CameraOperations', {
++CAM_OPS = IntEnum('CameraOperations', {
+ 'capture_image': _lib.GP_OPERATION_CAPTURE_IMAGE,
+ 'capture_video': _lib.GP_OPERATION_CAPTURE_VIDEO,
+ 'capture_audio': _lib.GP_OPERATION_CAPTURE_AUDIO,
+@@ -65,7 +65,7 @@ CAM_OPS = IntEnum(b'CameraOperations', {
+ 'trigger_capture': _lib.GP_OPERATION_TRIGGER_CAPTURE})
+
+
+-DIR_OPS = IntEnum(b'DirectoryOperations', {
++DIR_OPS = IntEnum('DirectoryOperations', {
+ 'remove': _lib.GP_FOLDER_OPERATION_REMOVE_DIR,
+ 'create': _lib.GP_FOLDER_OPERATION_MAKE_DIR,
+ 'delete_all': _lib.GP_FOLDER_OPERATION_DELETE_ALL,
+--
+2.11.0
+
diff -Nru gphoto2-cffi-0.3~a1/debian/patches/series
gphoto2-cffi-0.3~a1/debian/patches/series
--- gphoto2-cffi-0.3~a1/debian/patches/series 2016-04-04 22:24:03.0
+0300
+++ gphoto2-cffi-0.3~a1/debian/patches/series 2018-08-27 22:41:25.0
+0300
@@ -0,0 +1 @@
+0001-Make-enum-descriptors-strs-not-bytestrings-7.patch
Processed: Re: stretch-pu: package isort/4.2.5+ds1-2+deb9u1
Processing control commands: > tags -1 - moreinfo Bug #893541 [release.debian.org] stretch-pu: package isort/4.2.5+ds1-2+deb9u1 Removed tag(s) moreinfo. -- 893541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893541: stretch-pu: package isort/4.2.5+ds1-2+deb9u1
Control: tags -1 - moreinfo
On Mon, Jun 25, 2018 at 04:18:53AM +0200, Andreas Beckmann wrote:
> Control: tag -1 moreinfo
>
> On Mon, 19 Mar 2018 21:36:15 +0200 Adrian Bunk wrote:
> > Fix the dependencies of python-isort from empty to:
> > Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~)
>
> There is at least python-pkg-resources missing, too. #902327
Thanks for noticing, updated debdiff is attached.
The dependency changes are now:
python-isort
{+Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~)+}
isort
Depends: python3-isort, {+python3-pkg-resources,+} python3:any (>= 3.0~)
> Andreas
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
diff -Nru isort-4.2.5+ds1/debian/changelog isort-4.2.5+ds1/debian/changelog
--- isort-4.2.5+ds1/debian/changelog2016-07-20 01:31:43.0 +0300
+++ isort-4.2.5+ds1/debian/changelog2018-09-16 20:06:57.0 +0300
@@ -1,3 +1,14 @@
+isort (4.2.5+ds1-2+deb9u1) stretch; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing dependency on python3-pkg-resources. Thanks to
+Andreas Beckmann for reporting the issue. (Closes: #902327)
+ * Fix dependencies of the python2 package by using the correct
+${python:Depends} substvar instead of ${python3:Depends}. Thanks to Paul
+Wise for catching it. (Closes: #884682)
+
+ -- Adrian Bunk Sun, 16 Sep 2018 20:06:57 +0300
+
isort (4.2.5+ds1-2) unstable; urgency=medium
* Add python-isort package for Python 2 module (closes: #802582).
diff -Nru isort-4.2.5+ds1/debian/control isort-4.2.5+ds1/debian/control
--- isort-4.2.5+ds1/debian/control 2016-07-20 01:32:16.0 +0300
+++ isort-4.2.5+ds1/debian/control 2018-09-16 20:06:39.0 +0300
@@ -22,7 +22,8 @@
Package: isort
Architecture: all
-Depends: python3-isort, ${misc:Depends}, ${python3:Depends}
+Depends: python3-isort, python3-pkg-resources,
+ ${misc:Depends}, ${python3:Depends}
Description: utility for sorting Python imports
isort is a Python utility / library to sort imports alphabetically, and
automatically separated into sections. It provides a command line
@@ -33,7 +34,7 @@
Package: python-isort
Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends}
+Depends: ${misc:Depends}, ${python:Depends}
Description: library for sorting Python imports (Python 2)
isort is a Python utility / library to sort imports alphabetically, and
automatically separated into sections. It provides a command line
Processed: Re: Bug#905061: stretch-pu: package mruby/1.2.0+20161228+git30d5424a-1+deb9u1
Processing control commands: > tags -1 - moreinfo Bug #905061 [release.debian.org] stretch-pu: package mruby/1.2.0+20161228+git30d5424a-1+deb9u1 Removed tag(s) moreinfo. -- 905061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905061: stretch-pu: package mruby/1.2.0+20161228+git30d5424a-1+deb9u1
Control: tags -1 - moreinfo Hi, On Sun, Aug 26, 2018 at 02:35:52PM +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On 2018-07-31 03:29, Nobuhiro Iwamatsu wrote: > > I hereby propose an update for stretch of mruby. It contains a patch > > fixing CVE-2017-9527 [1]. The security issue was marked as being > > no-DSA [2]. > > According to the security tracker, that bug is not yet fixed in unstable - > is that correct? The version informatin on security-tracker was bit misleading resp. incorrect for unstable. The issue was fixed originally with an experimental upload as 1.2.0+20170601+git51e0e690-1. Later on a 1.3.0-1 was uploaded to unstable, I checked and the change was included there, so I fixed up the security-tracker information. There is though still the proposal from Moritz, to include more fixes in the proposed update if possible. Regards, Salvatore
Bug#908949: RM: uicilibris -- ROM; package m2l-pyqt does better; I maintain m2l-pyqt, so uicilibris is obsolete
Package: ftp.debian.org Severity: normal I am the author and the only developer of uicilibris, which has a low popularity index, and I shall not maintain it further, since the package m2l-pyqt, which I maintain in Debian, does better. Please remove uicilibris from unstable ; the package in testing will be auto- removed soon. Thank you
Bug#904316: transition: boost-defaults
Dimitri John Ledkov: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > This is a transition request to upgrade boost defaults from 1.62 to > 1.67. Whilst 1.65.1 never made it into Debian, it has in Ubuntu and > the transition from 1.62->1.65.1 has been completed there. The > transition from 1.65.1 -> 1.67 is ongoing, with almost all core > packages transitioned already. > > The most common issues are general fixes due to rebuilding with newer > gcc toolchain, removal of std::tr1::* provided namespace (e.g. instead > of std::tr1::regex use either boost::regex or std::regex), and change > in naming convention of boost_python sonames (which is now > multi-python aware upstream, and debian now matching it). > > Majority of fixes are already present in upstream releases, Ubuntu > uploads, or are trivial in nature. > > I would like to upload boost-defaults, to kick of transition and work > towards removing boost1.62 from testing before relese. > > Ben file: > > title = "boost-defaults"; > is_affected = .depends ~ /libboost[a-z-.]*1\.6[0123457]/; > is_good = .depends ~ /libboost[a-z-.]*1\.67/; > is_bad = .depends ~ /libboost[a-z-.]*1\.6[012345]/; > > > Hi, I noticed at least 13 packages that have boost-related changes in an Ubuntu diff (and I certainly have *not* checked all packages in the boost transition tracker; I only looked at dep level 3). * libcutl * lvtk * minieigen * opengm (removes binary packages) * performous (moves to boost1.65) * pyexiv2 * pytango * shark (reduces test precision) * tagpy * vcmi (moves to boost1.65) * anytun * aptitude * freeture Can you please provide a full list of packages that will break with the new boost default? How will Debian handle the packages that Ubuntu migrated to boost1.65 and left at that version (e.g. performous and vcmi above)? AFAICT, Debian does not have a boost1.65 to migrate too. Thanks, ~Niels
Bug#908931: transition: gnat-8, Ada component of gcc-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello. Ada packages Build-Depend: gnat, a virtual package Depending on the default compiler. In unstable, gnat/7.1 Depends: gnat-7. In experimental, gnat/8.0.0 Depends: gnat-8. In addition, Ada libraries directly Build-Depend: "gnat-VERSION", which also provides what could be expected in libgnat-8-dev if such a package existed. In this language, each change in the source of a library or its recursive dependencies requires a renaming of the -dev package. All reverse dependencies must then update their Build-Depends. The update to gnat-8 requires a renaming of all -dev packages, in addition to the traditional change of Shared Object Version. In order to reduce the number of such slow transitions, many unrelated changes (like new upstream releases) have been introduced with a single new name for the -dev package. Now, everything seems ready. Ben file: title = "gnat-8"; is_affected = .build-depends ~ "gnat"; is_good = .depends ~ "libgnat-8"; is_bad = .depends ~ /libgnat-[1-7]/; These packages are ready in experimental. A bin-NMU to unstable should be sufficient. They Build-Depend on each other via versioned packages (gnat-8, libfooVERSION-dev...) so the upload order should not matter. adabrowse adacgi adacontrol adasockets ahven anet asis dbusada dh-ada-library gnat gnat-gps gprbuild libalog libaunit libaws libflorist libgmpada libgnatcoll libgnatcoll-bindings libgnatcoll-db libgtkada liblog4ada libncursesada libtemplates-parser libtexttools libxmlada libxmlezout opentoken pcscada These packages are ready in unstable, but are not libraries. They Build-Depend: gnat without version restriction. They only need a dep-wait against gnat (>= 8). music123 ada-reference-manual This package is ready in experimental, but is not a library. It Build-Depend: gnat without version restriction. I suppose that it should be reuploaded to unstable, either after gnat/8.0.0 or with a dep-wait for gnat (>= 8) enforcing the build order. topal No one volunteers to update these packages. They Build-Depend: gnat-7 and would block the other ones. Please remove them from testing. polyorb spark What should we do now? Thanks.
transition: qrencode (ongoing, apparently uncoordinated)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-qrencode.html Control: block -1 by 908929 X-Debbugs-CC: qrenc...@packages.debian.org Hi debian-release, I thought I would let you know that there appears to be a libqrencode transition going on and this transition seems to be uncoordinated (at least I can find no recent mention of it in the debian-release archives). An automated transition tracker has been set-up at https://release.debian.org/transitions/html/auto-qrencode.html It appears that no binnmus have been scheduled in Debian for this transition yet, the packages listed as "good" either don't depend on the shared library or had a sourceful upload since the libqrencode upload. Over in raspbian our auto-binnmuer did schedule binnmus for this transition. All of them built successfully. However google-authenticator uses libqrencode through dlopen/dlsym rather than through the headers provided by libqrencode, so it needs sourceful changes (to both the upstream source and debian/control). See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908929
