Bug#943542: google-cloud-print-connector: hardcoded dependency on libsnmp30

[Peter Green]

Package: google-cloud-print-connector
Version: 1.12.1
Severity: serious
Tags: bullseye, sid

After uploading my fix for 942331 to Raspbian bullseye I discovered another 
problem. The dependency on libsnmp30 is hardcoded.

In raspbian I have just gone ahead and changed the dependency. a debdiff should 
appear soon at 
https://debdiffs.raspbian.org/main/g/google-cloud-print-connector/

Bug#942339: marked as done (peony-extensions: FTBFS - local unused g_ptr_array_copy definition collides with glib)

[Debian Bug Tracking System]

Your message dated Sat, 26 Oct 2019 02:41:43 +
with message-id 
and subject line Bug#942339: fixed in peony-extensions 1.1.3-1
has caused the Debian Bug report #942339,
regarding peony-extensions: FTBFS - local unused g_ptr_array_copy definition 
collides with glib
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.)


-- 
942339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: peony-extensions
Version: 1.1.2-1
Severity: serious
Tags: patch
Justification: FTBFS

Dear Maintainer,

The peony-extensions package currently fails to build from source.

The package will soon also be part of the gssdp/gupnp transition.
Since I haven't been able to find any signs of porting attempts started
anywhere I think it might be best to simply unblock the transition by
disabling upnp sendto support. This can be easily done by dropping the
gupnp build-dependency as built features are autodetected.

The attached debdiff takes care of both of the above issues.

Regards,
Andreas Henriksson
diff -Nru peony-extensions-1.1.2/debian/changelog 
peony-extensions-1.1.2/debian/changelog
--- peony-extensions-1.1.2/debian/changelog 2018-11-16 08:13:45.0 
+0100
+++ peony-extensions-1.1.2/debian/changelog 2019-10-14 22:22:38.0 
+0200
@@ -1,3 +1,14 @@
+peony-extensions (1.1.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add debian/patches/fix-ftbfs-gptrarraycopy.patch
+- fixes FTBFS by dropping unused locally defined
+  g_ptr_array_copy which collides with glib function with same name.
+  * Drop gupnp build-dependency, disabling upnp sendto support.
+- needs porting to gupnp 1.2
+
+ -- Andreas Henriksson   Mon, 14 Oct 2019 22:22:38 +0200
+
 peony-extensions (1.1.2-1) unstable; urgency=medium
 
   * Initial release. (Closes: #913874)
diff -Nru peony-extensions-1.1.2/debian/control 
peony-extensions-1.1.2/debian/control
--- peony-extensions-1.1.2/debian/control   2018-11-16 08:13:45.0 
+0100
+++ peony-extensions-1.1.2/debian/control   2019-10-14 22:01:01.0 
+0200
@@ -16,7 +16,6 @@
libgtk-3-dev,
libjson-glib-dev,
libmagic-dev,
-   libgupnp-1.0-dev,
libmate-desktop-dev (>= 1.18),
libstartup-notification0-dev,
mate-common (>= 1.18),
diff -Nru peony-extensions-1.1.2/debian/patches/fix-ftbfs-gptrarraycopy.patch 
peony-extensions-1.1.2/debian/patches/fix-ftbfs-gptrarraycopy.patch
--- peony-extensions-1.1.2/debian/patches/fix-ftbfs-gptrarraycopy.patch 
1970-01-01 01:00:00.0 +0100
+++ peony-extensions-1.1.2/debian/patches/fix-ftbfs-gptrarraycopy.patch 
2019-10-14 22:20:03.0 +0200
@@ -0,0 +1,35 @@
+--- a/parchives/src/glib-utils.c
 b/parchives/src/glib-utils.c
+@@ -569,22 +569,6 @@
+ }
+ 
+ 
+-GPtrArray *
+-g_ptr_array_copy (GPtrArray *array)
+-{
+-  GPtrArray *new_array;
+-  
+-  if (array == NULL)
+-  return NULL;
+-  
+-  new_array = g_ptr_array_sized_new (array->len);
+-  memcpy (new_array->pdata, array->pdata, array->len * sizeof 
(gpointer)); 
+-  new_array->len = array->len;
+-  
+-  return new_array;
+-}
+-
+-
+ void
+ g_ptr_array_free_full (GPtrArray *array,
+GFunc  free_func,
+--- a/parchives/src/glib-utils.h
 b/parchives/src/glib-utils.h
+@@ -67,7 +67,6 @@
+ int  last_field);
+ int n_fields (char   **str_array);
+ char *  get_time_string  (time_t   time);
+-GPtrArray * g_ptr_array_copy (GPtrArray   *array);
+ voidg_ptr_array_free_full(GPtrArray   *array,
+ GFuncfunc,
+ gpointer 
user_data);
diff -Nru peony-extensions-1.1.2/debian/patches/series 
peony-extensions-1.1.2/debian/patches/series
--- peony-extensions-1.1.2/debian/patches/series1970-01-01 
01:00:00.0 +0100
+++ peony-extensions-1.1.2/debian/patches/series2019-10-14 
22:19:31.0 +0200
@@ -0,0 +1 @@
+fix-ftbfs-gptrarraycopy.patch
--- End Message ---
--- Begin Message ---
Source: peony-extensions
Source-Version: 1.1.3-1

We believe that the bug you reported is fixed in the latest version of
peony-extensions, which is due to be installed in the Debian FTP archive.

A summary of the changes between 

Bug#937855: marked as done (python-jsonext: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 26 Oct 2019 01:48:57 +
with message-id 
and subject line Bug#937855: fixed in python-jsonext 0.4.2-1
has caused the Debian Bug report #937855,
regarding python-jsonext: Python2 removal in sid/bullseye
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.)


-- 
937855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-jsonext
Version: 0.4.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-jsonext

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-jsonext
Source-Version: 0.4.2-1

We believe that the bug you reported is fixed in the latest version of
python-jsonext, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 937...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-jsonext package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Oct 2019 12:25:12 +1100
Source: python-jsonext
Architecture: source
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 937855
Changes:
 python-jsonext (0.4.2-1) unstable; urgency=medium
 .
   [ Ben Finney ]
   * New upstream version.
 Now includes user documentation.
   * Declare conformance to “Standards-Version: 4.4.1”.
   * Specify HTTPS URL for upstream source repository.
   * Improve consistency of copyright grant in Debian packaging.
   * Use a null command for ‘clean’ during ‘Git-BuildPackage’.
   * Declare Debhelper compatibility level 12.
   * debian/compat:
 * Remove obsolescent configuration file.
   * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets.
 These are no longer mentioned in Debian Policy 4.1.4 and later.
   * Update copyright years for Debian packaging.
   * Specify current VCS for Debian packaging work.
   * 

Bug#942331: google-cloud-print-connector FTBFS with current cups (was: google-cloud-print-connector: FTBFS during rebuild with libsnmp35)

[peter green]

tags 942331 +patch
thanks


Your package is part of the libsnmp transition. During a rebuild your package
FTBFS on all architectures.

Reading the log more thoroughly it seems the actual failure is cups related.


cgo-gcc-prolog:95:2: warning: ‘cupsGetPPD3’ is deprecated: Use cupsCopyDestInfo 
and friends instead. [-Wdeprecated-declarations]
In file included from 
src/github.com/google/cloud-print-connector/cups/cups.h:15,
  from 
src/github.com/google/cloud-print-connector/cups/core.go:14:
/usr/include/cups/ppd.h:360:22: note: declared here
   360 | extern http_status_t cupsGetPPD3(http_t *http, const char *name, time_t 
*modtime, char *buffer, size_t bufsize) _CUPS_DEPRECATED_1_6_MSG("Use 
cupsCopyDestInfo and friends instead.");
   |  ^~~
# github.com/google/cloud-print-connector/cups
cups.c: In function ‘getIPPRequestStatusCode’:
cups.c:42:12: error: dereferencing pointer to incomplete type ‘ipp_t’ {aka 
‘struct _ipp_s’}
42 |  return ipp->request.status.status_code;
   |^~
cups.c: In function ‘getAttributeDateValue’:
cups.c:47:13: error: dereferencing pointer to incomplete type ‘ipp_attribute_t’ 
{aka ‘struct _ipp_attribute_s’}
47 |  return attr->values[i].date;
   | ^~
crypto

Specifically it seems cups no longer allows direct access to some structures ( 
https://github.com/apple/cups/commit/0fb02fb9cef39fd0b0c838f11af21d99fe5eab9b#diff-a299fb5293cedc8102f5963e50fbe22c
 ).

I have whipped up a patch and it seems to build, but I have not tested it beyond 
that as I do not use google cloud printing. In particular I note that it seems the 
only way to iterate through the attributes changes ipp->next. I don't know why 
the the API is designed this way or if this will cause any problems. I also notice 
that ippGetValueTag applies a mask before returning the tag, again I don't know if 
that will cause any problems. Also I don't know go, so my changes to the go code 
should probablly be checked by someone who actually knows the langauge.

I have uploaded my fix to raspbian, a debdiff should appear soon at 
https://debdiffs.raspbian.org/main/g/google-cloud-print-connector/

Processed: google-cloud-print-connector FTBFS with current cups (was: google-cloud-print-connector: FTBFS during rebuild with libsnmp35)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 942331 +patch
Bug #942331 [src:google-cloud-print-connector] google-cloud-print-connector: 
FTBFS during rebuild with libsnmp35
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#937855: python-jsonext: Python2 removal in sid/bullseye (now this is an RC bug...)

[Ben Finney]

Control: tags -1 + pending - patch

On 18-Oct-2019, Thomas Goirand wrote:

> Attached is a debdiff fixing this RC bug. There's other clean-up
> necessary for this package (like removing the X-Python{3,}-Version:)
> which I think should be done before the upload.

Thanks for the proposed changes.

(Something in your toolchain – or possibly you, manually? – are
removing valid U+000C white space characters from source files. I
would reject a diff with that error, not sure if it was deliberate
though.)

> Let me know if you're ok for me to NMU this package.

I've packaged a newer upstream release and am dealing with this bug in
with that. Thanks again.

-- 
 \  “One bad programmer can easily create two new jobs a year. |
  `\  Hiring more bad programmers will just increase our perceived |
_o__) need for them.” —David Lorge Parnas, 1999-03 |
Ben Finney 


signature.asc
Description: PGP signature

Processed: Re: Bug#937855: python-jsonext: Python2 removal in sid/bullseye (now this is an RC bug...)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending - patch
Bug #937855 {Done: Sandro Tosi } [src:python-jsonext] 
python-jsonext: Python2 removal in sid/bullseye
Added tag(s) pending.
Bug #937855 {Done: Sandro Tosi } [src:python-jsonext] 
python-jsonext: Python2 removal in sid/bullseye
Removed tag(s) patch.

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

Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers'

[Anthony DeRobertis]

Package: libvirt-daemon
Version: 5.6.0-2
Followup-For: Bug #939983

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Searching the web led to a suggestion this is from libvirt not realizing
its on a systemd machine and trying to use non-systemd cgroups. (It
should be machine.slice under systemd).

Installing systemd-container, making sure it was started
(machines.target and machine.slice, though maybe that'll happen
automatically --- certainly should on reboot), and restarting libvirt
fixed it here.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 
'testing'), (500, 'stable'), (130, 'unstable-debug'), (130, 'unstable'), (120, 
'experimental-debug'), (120, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt-daemon depends on:
ii  libblkid1   2.34-0.1
ii  libc6   2.29-2
ii  libcap-ng0  0.7.9-2+b1
ii  libdbus-1-3 1.12.16-2
ii  libdevmapper1.02.1  2:1.02.155-3
ii  libfuse22.9.9-2
ii  libgcc1 1:9.2.1-8
ii  libgnutls30 3.6.9-5
ii  libnetcf1   1:0.2.8-1+b3
ii  libparted2  3.3-1
ii  libpcap0.8  1.9.1-2
ii  libpciaccess0   0.14-1
ii  libselinux1 2.9-2+b2
ii  libudev1242-7
ii  libvirt05.6.0-2
ii  libxenmisc4.11  4.11.1+92-g6c33308a8d-2+b1
ii  libxenstore3.0  4.11.1+92-g6c33308a8d-2+b1
ii  libxentoollog1  4.11.1+92-g6c33308a8d-2+b1
ii  libxml2 2.9.4+dfsg1-7+b3

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.4+dfsg1-7+b3
ii  netcat-openbsd  1.203-2
ii  qemu-kvm1:4.1-1+b2

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster  
pn  libvirt-daemon-driver-storage-rbd  
pn  libvirt-daemon-driver-storage-zfs  
ii  libvirt-daemon-system  5.6.0-2
pn  numad  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHMEARECADMWIQTlAc7j4DAtSNRJJ0z7P4jCVepZ/gUCXbOIAhUcYW50aG9ueUBk
ZXJvYmVydC5uZXQACgkQ+z+IwlXqWf4P/gCfXPpKvk+nDfuSbVxcVZxMnpk9rbkA
n2rOrdrR+7rJJm7VNqqCjGxVXGIu
=IOZI
-END PGP SIGNATURE-

Bug#925859: marked as done (wmwave: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 22:20:00 +
with message-id 
and subject line Bug#925859: fixed in wmwave 0.4-11
has caused the Debian Bug report #925859,
regarding wmwave: ftbfs with GCC-9
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.)


-- 
925859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wmwave
Version: 0.4-10
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/wmwave_0.4-10_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
 /<>/Makefile
 /<>/wmwave.1
 /<>/wmwave.c

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=en_US.UTF-8
LC_ALL=POSIX
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-d426f01b-440b-449c-8b04-9de6632c98ce
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

dpkg-buildpackage: info: source package wmwave
dpkg-buildpackage: info: source version 0.4-10
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Guido Günther 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make clean
make[1]: Entering directory '/<>'
rm -f *.o
rm -f wmwave 
rm -f *~
make[1]: Leaving directory '/<>'
dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 8 in use)
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
dh_testdir
touch configure-stamp
dh_testdir
# Add here commands to compile the package.
/usr/bin/make CFLAGS="-Wall -g -O2"
make[1]: Entering directory '/<>'
cc -Wall -g -O2 -I/usr/X11R6/share/include -c wmgeneral.c -o wmgeneral.o
cc -Wall -g -O2 -I/usr/X11R6/share/include -c wmwave.c -o wmwave.o
cc -Wall -g -O2 -o wmwave wmgeneral.o  -lXext -L/usr/X11R6/lib -lXpm -lXext 
-lX11 -lm -liw wmwave.o
/usr/bin/ld: wmwave.o: in function `iw_getinf_stats':
/<>/wmwave.c:363: undefined reference to `iw_get_range_info'
/usr/bin/ld: /<>/wmwave.c:365: undefined reference to 
`iw_get_stats'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:24: wmwave] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:28: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: wmwave
Source-Version: 0.4-11

We believe that the bug you reported is fixed in the latest version of
wmwave, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 925...@bugs.debian.org,
and the maintainer will reopen 

Bug#943533: ldh-gui-suite: fails to install: mv: cannot move '/tmp/debconf_SxQLyd2wY8' to '/var/lib/one.liberty/deckhost.conf': No such file or directory

[Andreas Beckmann]

Package: ldh-gui-suite
Version: 0.1~20190927-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up ldh-gui-suite (0.1~20190927-3) ...
  mv: cannot move '/tmp/debconf_SxQLyd2wY8' to 
'/var/lib/one.liberty/deckhost.conf': No such file or directory
  dpkg: error processing package ldh-gui-suite (--configure):
   installed ldh-gui-suite package post-installation script subprocess returned 
error exit status 1
  Processing triggers for systemd (242-7) ...
  Processing triggers for libc-bin (2.29-2) ...
  Processing triggers for dictionaries-common (1.28.1) ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1) ...
  Errors were encountered while processing:
   ldh-gui-suite


You probably need to ship /var/lib/one.liberty as an empty directory
in the package.


cheers,

Andreas


ldh-gui-suite_0.1~20190927-3.log.gz
Description: application/gzip

Bug#943532: kwartz-client: fails to install: /etc/nslcd.conf:23: bindpw: wrong number of arguments

[Andreas Beckmann]

Package: kwartz-client
Version: 1.0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up kwartz-client (1.0-6) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Restarting LDAP connection daemon: nslcdnslcd: /etc/nslcd.conf:23: bindpw: 
wrong number of arguments
   [ESC][31mfailed![ESC][39;49m
  dpkg: error processing package kwartz-client (--configure):
   installed kwartz-client package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.29-2) ...
  Processing triggers for ca-certificates (20190110) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   kwartz-client


cheers,

Andreas


kwartz-client_1.0-6.log.gz
Description: application/gzip

Bug#941055: Bug #941055: dtkwm FTBFS: Project ERROR: set DTK_MODULE_NAME first

[Boyuan Yang]

notfound 941055 2.0.9-3
found 941055 2.0.9-4
thanks

This bug actually does not affect dtkwm in Buster. I am hacking into the
version string to avoid mentioning stable in the bug.

Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Andreas Beckmann]

Package: node-tslib
Version: 1.10.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + node-rollup-plugin-typescript

Hi,

during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.

Your package ships:

drwxr-xr-x root/root 0 2019-08-03 13:44 ./usr/share/nodejs/tslib/
-rw-r--r-- root/root   701 2019-06-10 22:24 
./usr/share/nodejs/tslib/package.json
-rw-r--r-- root/root  2290 2019-06-10 22:24 
./usr/share/nodejs/tslib/tslib.d.ts
-rw-r--r-- root/root36 2019-06-10 22:24 
./usr/share/nodejs/tslib/tslib.es6.html
-rw-r--r-- root/root  9436 2019-06-10 22:24 
./usr/share/nodejs/tslib/tslib.es6.js
-rw-r--r-- root/root32 2019-06-10 22:24 
./usr/share/nodejs/tslib/tslib.html
-rw-r--r-- root/root 12037 2019-06-10 22:24 
./usr/share/nodejs/tslib/tslib.js

but package node-typescript ships:

lrwxrwxrwx root/root 0 2019-10-15 06:12 ./usr/share/nodejs/tslib -> 
typescript/lib


Installing something over existing symlinks is considered bad practice.
See e.g. https://lists.debian.org/87ehlevcrf@windlord.stanford.edu

It may break in subtle ways and dpkg cannot detect this as a problem.
* Your package might silently overwrite files installed at the symlink
  destination by other packages.
* If the package shipping the symlink decides to make the link point
  somewhere else (or turn it into a real directory), the files owned
  by your package "will be lost" somewhere in the filesystem.
* Depending on installation order the problematic path will be created
  either as a symlink or a directory: the package installed first will
  "win" and all others have "lost".
  Note that dpkg intentionally does not replace directories with
  symlinks and vice versa, see in particular the end of point 4 in
  
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
  (Note: Adding Pre-Depends is *not* a solution.)

Please move the files shipped in your package to the "real" location.

>From the attached log (scroll to the bottom...):

0m24.0s ERROR: installs objects over existing directory symlinks:
  /usr/share/nodejs/tslib/package.json (node-tslib) != 
/usr/share/nodejs/typescript/lib/package.json (?)
/usr/share/nodejs/tslib -> typescript/lib
  /usr/share/nodejs/tslib/tslib.d.ts (node-tslib) != 
/usr/share/nodejs/typescript/lib/tslib.d.ts (?)
/usr/share/nodejs/tslib -> typescript/lib
  /usr/share/nodejs/tslib/tslib.es6.html (node-tslib) != 
/usr/share/nodejs/typescript/lib/tslib.es6.html (?)
/usr/share/nodejs/tslib -> typescript/lib
  /usr/share/nodejs/tslib/tslib.es6.js (node-tslib) != 
/usr/share/nodejs/typescript/lib/tslib.es6.js (?)
/usr/share/nodejs/tslib -> typescript/lib
  /usr/share/nodejs/tslib/tslib.html (node-tslib) != 
/usr/share/nodejs/typescript/lib/tslib.html (?)
/usr/share/nodejs/tslib -> typescript/lib
  /usr/share/nodejs/tslib/tslib.js (node-tslib) != 
/usr/share/nodejs/typescript/lib/tslib.js (?)
/usr/share/nodejs/tslib -> typescript/lib


cheers,

Andreas


node-rollup-plugin-typescript_1.0.0-1.log.gz
Description: application/gzip

Bug#942507: pdfsam: Not working due to multiple errors

[Markus Koschany]

Control: severity -1 important

I'm downgrading this issue to important because pdfsam in testing is not
affected. As long as hibernate-validator 5.x does not migrate to
testing, before this bug is fixed in unstable, it should not be a problem




signature.asc
Description: OpenPGP digital signature

Bug#943506: marked as done (python3-apsw,python3-apsw-dbg: both ship /usr/lib/python3/dist-packages/apsw.cpython-37dm-x86_64-linux-gnu.so)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 19:34:37 +
with message-id 
and subject line Bug#943506: fixed in python-apsw 3.29.0-r1-2
has caused the Debian Bug report #943506,
regarding python3-apsw,python3-apsw-dbg: both ship 
/usr/lib/python3/dist-packages/apsw.cpython-37dm-x86_64-linux-gnu.so
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.)


-- 
943506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-apsw,python3-apsw-dbg
Version: 3.29.0-r1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python3-apsw-dbg.
  Preparing to unpack .../python3-apsw-dbg_3.29.0-r1-1_amd64.deb ...
  Unpacking python3-apsw-dbg (3.29.0-r1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-apsw-dbg_3.29.0-r1-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/apsw.cpython-37dm-x86_64-linux-gnu.so', which 
is also in package python3-apsw 3.29.0-r1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-apsw-dbg_3.29.0-r1-1_amd64.deb


cheers,

Andreas


python3-apsw=3.29.0-r1-1_python3-apsw-dbg=3.29.0-r1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-apsw
Source-Version: 3.29.0-r1-2

We believe that the bug you reported is fixed in the latest version of
python-apsw, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joel Rosdahl  (supplier of updated python-apsw package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2019 20:15:23 +0200
Source: python-apsw
Architecture: source
Version: 3.29.0-r1-2
Distribution: unstable
Urgency: medium
Maintainer: Joel Rosdahl 
Changed-By: Joel Rosdahl 
Closes: 943506
Changes:
 python-apsw (3.29.0-r1-2) unstable; urgency=medium
 .
   * Back out "Fix the installation of 3.8 extensions" (closes: #943506)
Checksums-Sha1:
 dbf61aa8729c5cb615caba8465a75c3657dcbfd3 2104 python-apsw_3.29.0-r1-2.dsc
 0a3c2fe1fc4399930d435784b3d56706a2cdaecd 5644 
python-apsw_3.29.0-r1-2.debian.tar.xz
 6e4517cd3d4c64fdaaec8dd9f93eab4383c827c5 10682 
python-apsw_3.29.0-r1-2_amd64.buildinfo
Checksums-Sha256:
 bb57b78b6d4386fe5e327846dc7032158933ff9c3c75bd8f356d99292063b347 2104 
python-apsw_3.29.0-r1-2.dsc
 19f231ad8ff24473c9d2f449eca34f15962c2680e1867b4e9d6bd2ef2f6c73e6 5644 
python-apsw_3.29.0-r1-2.debian.tar.xz
 22245ee1df62c4ef1508ee8e40623efb5974e5edaca5d60110928b0f0cd86f53 10682 
python-apsw_3.29.0-r1-2_amd64.buildinfo
Files:
 a819360742e72ade4d07981a55e909bb 2104 python optional 
python-apsw_3.29.0-r1-2.dsc
 ed3170a2f29ee2330b3f36e5ed00a404 5644 python optional 
python-apsw_3.29.0-r1-2.debian.tar.xz
 e70c41b39c73e542a16b3bf5a77b5a8e 10682 python optional 
python-apsw_3.29.0-r1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWpOacaRnks9XhmpRmW3aB1WUrbgFAl2zPZIACgkQmW3aB1WU
rbibAg/+KwfuQOxVxqKnpZLMVuCk+lapuGEOD/4LqMetx4nkOffkKSnQ8Te9dsZn
gKV01g2QymYZfBu6gU42+jDjOR1i8Z4HffQNv+zp/Lp5HYyQomMxnZWdXK6sYIvJ
PY6+cianUWCGFdSxHQVnpk40OX/YR0N9HXOasG+uYHLOg5o3DoCTvXm47n2DVFoP
aitMqMvpUN/nCVX+cuNQ3QjIXaZ8zo49jSPJK5qdNP47IIAVTJwIoeDref1IqGN+
BRSN//Zi5k5sXfcCbiaBI27zocDQfS0gvHPV/xqfdqIj4kOdw1kXjk8iKuP3MUWb
625HOjTamMwfJn7wZcu/dFJrLUARX2PA4UhWO0e6Z7QtIjjpueWgGHjlt7UDMoLk
lzEEmEyigRZdbt4VnBlVnsJpVn9GihELniGGmZoEbVuDkmnuLqggausxIqzbVDUX
2ccnTaI7j/zQBZjD8RVcXWxp5Pi7sTN9fxIA+35GXQb55QMw5l7PNZX7OU8MhGdC
xscprtn1lN+1NluO8Ms7+AMOKPO2hC7nbugzuHLNk3GiVp55QhM7V77cCH28nRmI
bPqZtucTMCSIp7OuYTvx1n02u9FuIO8/cUDfb29G6lBMd4uylinxxQV81OU7Vp1y
ZShCYQsBy8yXlmUFOid77791QEVVnwTL1EssXZNTzuoy/tZg3SA=
=hPff
-END PGP SIGNATURE End Message ---

Processed: Re: Bug #941055: dtkwm FTBFS: Project ERROR: set DTK_MODULE_NAME first

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 941055 2.0.9-3
Bug #941055 {Done: Boyuan Yang } [src:dtkwm] dtkwm FTBFS: 
Project ERROR: set DTK_MODULE_NAME first
No longer marked as found in versions dtkwm/2.0.9-3.
> found 941055 2.0.9-4
Bug #941055 {Done: Boyuan Yang } [src:dtkwm] dtkwm FTBFS: 
Project ERROR: set DTK_MODULE_NAME first
The source 'dtkwm' and version '2.0.9-4' do not appear to match any binary 
packages
Marked as found in versions dtkwm/2.0.9-4.
> thanks
Stopping processing here.

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

Bug#942619: marked as done (screenruler: Maintainer email address not working)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 21:51:11 +
with message-id 
and subject line Bug#942619: fixed in screenruler 0.960+bzr41+deb10-4
has caused the Debian Bug report #942619,
regarding screenruler: Maintainer email address not working
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.)


-- 
942619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: screenruler
Severity: serious
Justification: Policy 3.3

Policy requires a maintainer email address that accepts mail.  Mail for
this maintainer has been failing for some time:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  rai...@ubuntu.com
host mx.canonical.com [91.189.95.10]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in virtual alias table

Scott K
--- End Message ---
--- Begin Message ---
Source: screenruler
Source-Version: 0.960+bzr41+deb10-4

We believe that the bug you reported is fixed in the latest version of
screenruler, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated screenruler 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2019 23:12:42 +0200
Source: screenruler
Architecture: source
Version: 0.960+bzr41+deb10-4
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 942619
Changes:
 screenruler (0.960+bzr41+deb10-4) unstable; urgency=medium
 .
   * nominated myself as the maintainer. Closes: #942619
Checksums-Sha1:
 24d515f4323826f8c189fd1f8125bc2cb6b81c3d 2042 
screenruler_0.960+bzr41+deb10-4.dsc
 d8d5862c67f8319c7ed45e6754dd9e141e4f5873 5956 
screenruler_0.960+bzr41+deb10-4.debian.tar.xz
 74464e412f92b0ecdcf4c47d389a9a64a36b70a8 5239 
screenruler_0.960+bzr41+deb10-4_source.buildinfo
Checksums-Sha256:
 6439eaacb7e190f4e77e16b2bf44023d132ca21e178749d4202a9016ba910b40 2042 
screenruler_0.960+bzr41+deb10-4.dsc
 3adbca5a8417c0a9665609c64ac26484e0eaadd3e029278b03531226d815e10c 5956 
screenruler_0.960+bzr41+deb10-4.debian.tar.xz
 4715605ba4b71b97f0cf355d0918188a396ef22192bfb7e0da73a4d3cb4a8bfe 5239 
screenruler_0.960+bzr41+deb10-4_source.buildinfo
Files:
 5394f5af7cdf4f44e2b597344c0b0b0f 2042 gnome optional 
screenruler_0.960+bzr41+deb10-4.dsc
 8132c2da8e28fc2a3025832263008bc2 5956 gnome optional 
screenruler_0.960+bzr41+deb10-4.debian.tar.xz
 e7c3a7fb750997e72386fb41940e7f29 5239 gnome optional 
screenruler_0.960+bzr41+deb10-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl2zZaAUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmqfxAAhYTdk5GNBZmHZUI1H1jUvi0iTMlS
sL/Wltij1WBZdm3Lv9bLGTa0h2sU/EriyJ61avGvV2fOt5ZkJFKwmf/nEuiKOYu3
hXE1C4nXUevDAe0KzKU2MQW2AW5Ho53+OL4+9w4rmyWieC1PrC2bRYqggwt+Plu5
PA1leTtK7v95SwmZRMR/WgODAEGQq6D3dbxmLjW0xqkWM2jxKM36B2k7+R/CFL1x
mSyfNhCPT7BfrPRffEZ/MpMWOsG4h4zqjEFWfk9DoPim9Om7/0RSDTGqW8aywW5I
0uEBmNaH8GdnGXN3iWGbGZU62Lz0gKmkJB8XWw9AC21TCf4hMlIUuzpEjUk+33iF
HGq+wJLFxKM7miIT35cZVDgqNPhPjzSVfmjPF752CPLl6A8/U+QPO+deHIpWizcO
VmJNIr0OIctxSg3qfLStf12QGieVhP4yUpwAVyGR02e8UiHcllesN+JVCdHky4eW
7pHh1wwlT0x/Zt96ficY6Zd+3ErMPq7hNIGRWLeesqNvrvB4JlijypxRznQW/pVX
kfP04V6pGJwYjEklQ4XhdSD/RG/TxH4IC/M3HEYbLquvijWC+Rxec5+/HBSHq250
dRpAZuBXlGNZsLP/47OzmGdIX1CsHsgMWjuqgQxV6Bb0TtDonBZypNfm+SBBVLDy
nvPgbfBLCLsS5zM=
=U0Rq
-END PGP SIGNATURE End Message ---

Bug#943534: python3-lesscpy: fails to install: update-alternatives: error: alternative path /usr/bin/python3-lesscpy doesn't exist

[Andreas Beckmann]

Package: python3-lesscpy
Version: 0.13.0+ds-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python3-lesscpy (0.13.0+ds-1.1) ...
  update-alternatives: error: alternative path /usr/bin/python3-lesscpy doesn't 
exist
  dpkg: error processing package python3-lesscpy (--configure):
   installed python3-lesscpy package post-installation script subprocess 
returned error exit status 2
  Processing triggers for libc-bin (2.29-2) ...
  Errors were encountered while processing:
   python3-lesscpy

With the python2 variant gone, the alternatives can probably be dropped
- but don't forget to properly remove them on upgrades.


cheers,

Andreas


python3-lesscpy_0.13.0+ds-1.1.log.gz
Description: application/gzip

Processed: Re: pdfsam: Not working due to multiple errors

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #942507 [pdfsam] pdfsam: Not working due to multiple errors
Severity set to 'important' from 'grave'

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

Processed: Re: Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 943470 1.22.2+dfsg-1
Bug #943470 [webext-ublock-origin] webext-ublock-origin: Version in stable not 
working after [DSA 4549-1] firefox-esr security update
Marked as fixed in versions ublock-origin/1.22.2+dfsg-1.
> thanks
Stopping processing here.

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

Processed: closing 909994

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 909994 0.5.2-2
Bug #909994 [src:python-pgpy] python-pgpy: FTBFS (No module named '_gpgme')
The source 'python-pgpy' and version '0.5.2-2' do not appear to match any 
binary packages
Marked as fixed in versions python-pgpy/0.5.2-2.
Bug #909994 [src:python-pgpy] python-pgpy: FTBFS (No module named '_gpgme')
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#909994: closing 909994

[Daniel Kahn Gillmor]

close 909994 0.5.2-2
thanks

python-pgpy 0.5.2-2 builds fine on the build daemons.

I suspect that the problem in #909994 was due to some breakage with
gpgme.

Bug#943527: webext-umatrix: umatrix is unusable with current firefox-esr

[Daniel Reichelt]

Package: webext-umatrix
Version: 1.3.16+dfsg-2
Severity: grave
Justification: renders package unusable

Hi,

since the latest update of firefox-esr from 60.9 to 68.2, umatrix is no longer
usable. I tried v1.4 from addons.mozilla.org which seems to do fine.

Please update to the latest version. Thanks!

Daniel



-- System Information:
Debian Release: 10.1
  APT prefers proposed-updates
  APT policy: (990, 'proposed-updates'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 
'oldstable-debug'), (500, 'oldstable'), (99, 'testing'), (98, 'unstable'), (96, 
'oldoldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-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/bash
Init: sysvinit (via /sbin/init)

Versions of packages webext-umatrix depends on:
ii  fonts-font-awesome 5.0.10+really4.7.0~dfsg-1
ii  fonts-roboto-unhinted  2:0~20170802-3
ii  libjs-codemirror   5.43.0-1
ii  libjs-punycode 1.3.2-2
ii  publicsuffix   20190415.1030-1

Versions of packages webext-umatrix recommends:
ii  firefox-esr  68.2.0esr-1~deb10u1

webext-umatrix suggests no packages.

-- no debconf information

Processed: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + node-rollup-plugin-typescript
Bug #943526 [node-tslib] node-tslib: directory vs. symlink conflict: 
/usr/share/nodejs/tslib
Added indication that 943526 affects node-rollup-plugin-typescript

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

Bug#943524: python3-stdlib-extensions: FTBFS with ModuleNotFoundError: No module named '_sysconfigdata_d_linux_x86_64-linux-gnu'

[Andreas Beckmann]

Source: python3-stdlib-extensions
Version: 3.8.0~a3-1
Severity: serious

Hi,

python3-stdlib-extensions/experimental FTBFS in an up-to-date
sid/experimental pbuilder environment:

[...]
cd 3.8 && PYTHONPATH=/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib 
python3.8-dbg setup.py build
running build
running build_ext
setup.py:623: DeprecationWarning: invalid escape sequence \s
  archs = re.findall('-arch\s+(\w+)', cflags)
setup.py:4: DeprecationWarning: the imp module is deprecated in favour of 
importlib; see the module's documentation for alternative uses
  import sys, os, imp, re, optparse
setup.py:787: DeprecationWarning: SO is deprecated, use EXT_SUFFIX
  so_ext = sysconfig.get_config_var("SO")
Traceback (most recent call last):
  File "setup.py", line 877, in 
main()
  File "setup.py", line 849, in main
setup(# PyPI Metadata (PEP 301)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/core.py", 
line 148, in setup
dist.run_commands()
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 966, in run_commands
self.run_command(cmd)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 985, in run_command
cmd_obj.run()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/command/build.py", 
line 135, in run
self.run_command(cmd_name)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/cmd.py", 
line 313, in run_command
self.distribution.run_command(command)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 985, in run_command
cmd_obj.run()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/command/build_ext.py",
 line 310, in run
customize_compiler(self.compiler)
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 197, in customize_compiler
get_config_vars('CC', 'CXX', 'CFLAGS',
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 501, in get_config_vars
func()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 461, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
ModuleNotFoundError: No module named '_sysconfigdata_d_linux_x86_64-linux-gnu'
make: *** [debian/rules:60: dbg-stamp-py3.8] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas


python3-stdlib-extensions_3.8.0~a3-1.log.gz
Description: application/gzip

Bug#943523: xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)'

[Andreas Beckmann]

Source: xpdf
Version: 3.04-13exp2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

xpdf/experimental FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=xpdf=experimental

 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cp goo/gfile.h xpdf/xfile.h
sed -e s/GFILE/XFILE/g -i xpdf/xfile.h
cp goo/gfile.cc xpdf/xfile.cc
sed -e s/GFILE/XFILE/g -i xpdf/xfile.cc
cp xpdf/GlobalParams.h xpdf/XPDFParams.h
sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \
-e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \
-e s/PopplerParams/GlobalParams/g \
-i xpdf/XPDFParams.h
cp xpdf/GlobalParams.cc xpdf/XPDFParams.cc
sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \
-e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \
-e s/PopplerParams/GlobalParams/g \
-i xpdf/XPDFParams.cc
mkdir -p build
cp goo/parseargs.c goo/parseargs.h xpdf/CoreOutputDev.cc xpdf/CoreOutputDev.h 
xpdf/PDFCore.cc xpdf/PDFCore.h xpdf/XPDFApp.cc xpdf/XPDFApp.h xpdf/XPDFCore.cc 
xpdf/XPDFCore.h xpdf/XPDFParams.cc xpdf/XPDFParams.h xpdf/XPDFTree.cc 
xpdf/XPDFTree.h xpdf/XPDFViewer.cc xpdf/XPDFViewer.h xpdf/xfile.cc xpdf/xfile.h 
xpdf/xpdf.cc xpdf/config.h xpdf/XPDFTreeP.h xpdf/about-text.h xpdf/*.xbm 
xpdf/xpdfIcon.xpm build
sed -E -e s/GString/GooString/g -e s/GMutex/GooMutex/g -e s/GHash/GooHash/g \
-e s/GList/GooList/g -e s/\/\/g \
-e s/GBool/bool/g -e s/gTrue/true/g -e s/gFalse/false/g \
-e 's/deleteGooList\(([^,]+), ([^)]+)\);/deleteGooList<\2> \(\1\);/' \
-i build/*
mv build/parseargs.c build/parseargs.cc
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H 
-DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/CoreOutputDev.o 
build/CoreOutputDev.cc
x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H 
-DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/PDFCore.o build/PDFCore.cc
build/PDFCore.cc: In member function 'virtual void 
PDFCore::displayDest(LinkDest*, double, int, bool)':
build/PDFCore.cc:311:37: error: no matching function for call to 
'PDFDoc::findPage(Ref&)'
 topPageA = doc->findPage(pageRef);
 ^
compilation terminated due to -Wfatal-errors.
make[1]: *** [: build/PDFCore.o] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:50: build-arch] Error 2


Andreas

Bug#943522: node-file-entry-cache: fails to clean after build

[Andreas Beckmann]

Source: node-file-entry-cache
Version: 5.0.1+~2.0.1+~2.0.0+~1.0.0+~2.0.1-3
Severity: serious

Hi,

node-file-entry-cache/experimental fails to clean after a successful
build:

 debian/rules clean
dh clean
   dh_clean
rm: cannot remove './debian/node_modules': Is a directory
dh_clean: rm -f -- debian/node-file-entry-cache.substvars 
debian/node-flat-cache.substvars debian/node-write.substvars 
./debian/node_modules debian/files returned exit code 1
make: *** [debian/rules:66: clean] Error 255

This sounds like you have a 'debian/node_modules' entry without
trailing slash in debian/clean.


Andreas


node-file-entry-cache_5.0.1+~2.0.1+~2.0.0+~1.0.0+~2.0.1-3_twice.log.gz
Description: application/gzip

Bug#943521: node-proxyquire: fails to clean after build: rm: cannot remove './debian/node_modules': Is a directory

[Andreas Beckmann]

Source: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-3
Severity: serious

Hi,

node-proxyquire fails to clean after a successful build:

 debian/rules clean
dh clean
   dh_clean
rm: cannot remove './debian/node_modules': Is a directory
dh_clean: rm -f -- debian/node-proxyquire.substvars ./debian/node_modules 
debian/files returned exit code 1
make: *** [debian/rules:47: clean] Error 255


This sounds like you have a 'debian/node_modules' entry without
trailing slash in debian/clean.


Andreas


node-proxyquire_2.1.3+~1.0.1+~1.0.2-3_twice.log.gz
Description: application/gzip

Bug#943517: boxbackup: FTBFS with test failures

[Andreas Beckmann]

Package: boxbackup
Version: 0.13~~git20190527.g039c4a1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

boxbackup/experimental FTBFS in my sid/experimental pbuilder environment
on amd64 and i386. This seems to be a recent regression, since earlier
builds of that version have succeeded.

Unfortunately I can't tell from the buildlog which error is the actual
failure and which errors are expected for some tests.


Andreas


boxbackup_0.13~~git20190527.g039c4a1-2.log.gz
Description: application/gzip

Processed: valinor: FTBFS and autopkgtest failure due to new version of python-colorama

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python-colorama
Bug #943516 [src:valinor] valinor: FTBFS and autopkgtest failure due to new 
version of python-colorama
Added indication that 943516 affects src:python-colorama

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

Bug#943516: valinor: FTBFS and autopkgtest failure due to new version of python-colorama

[Paul Gevers]

Source: valinor
Version: 1.1.4-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-colorama

[X-Debbugs-CC: debian...@lists.debian.org,
python-color...@packages.debian.org]

Dear maintainers,

With a recent upload of python-colorama the autopkgtest of valinor fails
in testing when that autopkgtest is run with the binary packages of
python-colorama from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
python-coloramafrom testing0.4.1-1
valinorfrom testing1.1.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. I also tried
to rebuild on reproducible-builds.org infrastructure and your package
FTBFS with the same error.

Currently this regression is blocking the migration of python-colorama
to testing [1]. Of course, python-colorama shouldn't just break your
autopkgtest (or even worse, your package), but the change in
python-colorama was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-colorama should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-colorama/0.4.1-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-colorama

https://ci.debian.net/data/autopkgtest/testing/amd64/v/valinor/3248223/log.gz

autopkgtest [18:12:07]: test valinor: [---
=== python3.7 ===
.F
==
FAIL: testARMNoneEABIGDB (test.test_outputdir.TestCLIOutputDirectory)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.ejtpkkiz/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 48, in testARMNoneEABIGDB
runWithDir()
  File
"/tmp/autopkgtest-lxc.ejtpkkiz/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 46, in runWithDir
out = self.runCheck(args)
  File
"/tmp/autopkgtest-lxc.ejtpkkiz/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 33, in runCheck
self.assertEqual(status, 0)
AssertionError: 1 != 0
 >> begin captured stdout << -

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/share/valinor/valinor/main.py", line 36, in main
version=pkg_resources.require("valinor")[0].version,
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
900, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
791, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (colorama 0.4.1
(/usr/lib/python3/dist-packages),
Requirement.parse('colorama<0.4,>=0.3'), {'valinor'})


- >> end captured stdout << --

--
Ran 2 tests in 0.245s

FAILED (failures=1)
autopkgtest [18:12:08]: test valinor: ---]



signature.asc
Description: OpenPGP digital signature

Bug#943507: [Pkg-javascript-devel] Bug#943507: eslint: FTBFS in experimental

[Jonas Smedegaard]

Hi Andreas,

Quoting Andreas Beckmann (2019-10-25 18:04:33)
> eslint FTBFS in my pbuilder sid/experimental environment on both amd64 
> and i386. There is a test failing, but I couldn't easily see which 
> one:
> 
> # tests 16628
> # pass 16627
> # fail 1
> make[1]: *** [debian/rules:79: override_dh_auto_test] Error 1

Thanks for reporting this.

This is a known error - and one of the reasons eslint is still kept in 
experimental: Oddly, 1-2 tests succeeds in my cowbuilder environment but 
hangs in Debian sbuild - and surpringly also in your pbuilder (I had 
thought it was somehow tied to differences between cowbuilder and 
sbuild).

The tests use TAP output: errors are found with regex '^not ok':

> not ok 15448 configInitializer "before each" hook for "should create default 
> config"
>  Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
> "done()" is called; if returning a Promise, ensure it resolves.
>  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
>  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
>  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
>  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
>  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

The eslint currently in experimental is several years old, and I am 
slowly grinding my way through dependencies and build-dependencies to 
bump to newer releases, hoping that magically solves to problem, but any 
help identifying the cause more directly is certainly appreciated, and 
that would make it possible to release even an older release of eslint 
to unstable - even older releases are very useful for some purposes.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#933918: marked as done (src:lava: Unsafe use of yaml.load())

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 17:19:30 +
with message-id 
and subject line Bug#933918: fixed in lava 2019.10-1
has caused the Debian Bug report #933918,
regarding src:lava: Unsafe use of yaml.load()
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.)


-- 
933918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lava
Version: 2019.01-5
Severity: grave
Tags: security
Justification: user security hole

The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed.  This raises a deprecation warning which has
caused and autopkgtest failure on this package.  These are generally
trivial to fix, see the upstream guidance [1].

Scott K

[1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation
--- End Message ---
--- Begin Message ---
Source: lava
Source-Version: 2019.10-1

We believe that the bug you reported is fixed in the latest version of
lava, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Remi Duraffort  (supplier of updated lava package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Oct 2019 15:25:30 +0200
Source: lava
Architecture: source
Version: 2019.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Remi Duraffort 
Closes: 933918 940682
Changes:
 lava (2019.10-1) unstable; urgency=medium
 .
   * LAVA Software 2019.10 release
 557ab2abf Add unit tests for TestJob can_resubmit method.
 08e15334e lava_server: load local settings if available
 ec30dbf60 lava_server: add compatibility layer against renames
 4d0c47cd6 lava_scheduler_app: fix usage of User.is_authenticated
 c6eac7ad2 lava_server: drop pointless if
 2763292c6 lava_scheduler_app: don't add view permissions on Django 2
 429c60e36 lava_server: fix default development branding dimensions
 0f0b9fd36 lava_server: relax security-related settings for local 
development
 54960a290 lava_server: admin: customize titles
 a4aa03f02 doc: clarify usage of connection-namespace
 b5325a2e3 device-types: Add more uboot error messages
 f231d80ee devce-type: Fix meson-g12a-sei510
 c1c8e22ea Fix authorization API errors and add unit tests.
 2a8b19674 lava-slave: accept slave dir as an option
 cc58ec37b lava-slave: use absolute path to lava-run
 3e8f45ec4 scheduler, server: drop hardcoded device types path
 a47517522 server: drop hardcoded usage of devices directory
 cb0e1c1f7 settings.development: use device type configuration from source 
tree
 dcceb98e3 Procfile: run all processes locally
 215904362 doc: fix hangout link for the design meeting
 549d97cac Add documentation file for new authorization model.
 5b6c32814 docker: upgrade sentry-sdk to 0.11.2
 9a048b1bf Remove deprecated support for json job definition
 41924cf27 CI: fix failure when the yaml default format change
 935c4e221 Reintroduce 'cancel_resubmit_testjob' permission.
 857f011db services/docker: allow to set lava-master --event-url
 4fd207886 Remove dependency on dateutil
 813ed5544 lava-server manage commands: port to Django 2
 c981d0753 lava-server manage users: in csv, print the fullname
 ad9140324 Port management commands to Django 2
 f2b863ba4 development settings: use local directory for health-checks
 978b4fcb7 dev settings: remove references to "precious" directory
 d62f5fd6a lava_common: fix license headers
 45d2120e5 device-type: Add meson-g12b-a311d-khadas-vim3
 82752014f Add debian/bullseye requirements
 07f3bbcba Move django related functions to lava_server.compat
 f4fd43adb yaml.load: add a compatibility layer to always use the best 
available loader
 067a01726 Move the lava.utils module into lava_server
 7bba79ba0 Show users in group admin.
 297be49da device-type: Add hifive-unleashed-a00
 324746e82 device-types: add two olimex-lime boards
 dad61da61 Fix bulk cancel of test jobs in admin.
 

Bug#940682: marked as done (lava-server: depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 17:19:30 +
with message-id 
and subject line Bug#940682: fixed in lava 2019.10-1
has caused the Debian Bug report #940682,
regarding lava-server: depends on cruft package.
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.)


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

Package: lava-server
Version: 2019.01-5
Severity: serious
Tags: bullseye, sid

lava depends on gunicorn3 which is no longer built by the gunicorn source package. 
I belive you need to change your dependency to gunicorn, possiblly with a version 
constraint of >= 19.9.0-4
--- End Message ---
--- Begin Message ---
Source: lava
Source-Version: 2019.10-1

We believe that the bug you reported is fixed in the latest version of
lava, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 940...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Remi Duraffort  (supplier of updated lava package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Oct 2019 15:25:30 +0200
Source: lava
Architecture: source
Version: 2019.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Remi Duraffort 
Closes: 933918 940682
Changes:
 lava (2019.10-1) unstable; urgency=medium
 .
   * LAVA Software 2019.10 release
 557ab2abf Add unit tests for TestJob can_resubmit method.
 08e15334e lava_server: load local settings if available
 ec30dbf60 lava_server: add compatibility layer against renames
 4d0c47cd6 lava_scheduler_app: fix usage of User.is_authenticated
 c6eac7ad2 lava_server: drop pointless if
 2763292c6 lava_scheduler_app: don't add view permissions on Django 2
 429c60e36 lava_server: fix default development branding dimensions
 0f0b9fd36 lava_server: relax security-related settings for local 
development
 54960a290 lava_server: admin: customize titles
 a4aa03f02 doc: clarify usage of connection-namespace
 b5325a2e3 device-types: Add more uboot error messages
 f231d80ee devce-type: Fix meson-g12a-sei510
 c1c8e22ea Fix authorization API errors and add unit tests.
 2a8b19674 lava-slave: accept slave dir as an option
 cc58ec37b lava-slave: use absolute path to lava-run
 3e8f45ec4 scheduler, server: drop hardcoded device types path
 a47517522 server: drop hardcoded usage of devices directory
 cb0e1c1f7 settings.development: use device type configuration from source 
tree
 dcceb98e3 Procfile: run all processes locally
 215904362 doc: fix hangout link for the design meeting
 549d97cac Add documentation file for new authorization model.
 5b6c32814 docker: upgrade sentry-sdk to 0.11.2
 9a048b1bf Remove deprecated support for json job definition
 41924cf27 CI: fix failure when the yaml default format change
 935c4e221 Reintroduce 'cancel_resubmit_testjob' permission.
 857f011db services/docker: allow to set lava-master --event-url
 4fd207886 Remove dependency on dateutil
 813ed5544 lava-server manage commands: port to Django 2
 c981d0753 lava-server manage users: in csv, print the fullname
 ad9140324 Port management commands to Django 2
 f2b863ba4 development settings: use local directory for health-checks
 978b4fcb7 dev settings: remove references to "precious" directory
 d62f5fd6a lava_common: fix license headers
 45d2120e5 device-type: Add meson-g12b-a311d-khadas-vim3
 82752014f Add debian/bullseye requirements
 07f3bbcba Move django related functions to lava_server.compat
 f4fd43adb yaml.load: add a compatibility layer to always use the best 
available loader
 067a01726 Move the lava.utils module into lava_server
 7bba79ba0 Show users in group admin.
 297be49da device-type: Add hifive-unleashed-a00
 324746e82 device-types: add two olimex-lime boards
 dad61da61 Fix bulk cancel of test jobs in admin.
 ba0288cae scheduler.jobs.show: fix missing value after 2019.09
 8455b55f2 docker: do not ask for input while migrating
 dfd9de33d debian: lava-common should have 

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

On Fri, Oct 25, 2019 at 06:45:27PM +0200, Matthias Klose wrote:
> Control: tags -1 + moreinfo
> 
> On 25.10.19 18:33, Rene Engelhard wrote:
> > And since then I also can just reproduce it in a chroot, too.
> 
> You didn't say that before.

I did in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943401#17

--- snip ---
So, the last exception one (which I badly edited out of my last mail,
after I
actually mentioned it..  - my bad.) is reproducible here in a quick
"debian/tests/smoketest" run in a uptodate sid chroot.

Given LO didn't change (what gets installed) and the exceptionprotector
stuff gets
built with the new(er) g++ and this ends up in

Failure instantiating protector
"/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/LinkTarget/Library/unoexceptionprotector.so",
"unoexceptionprotector"
make: ***
[/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/solenv/gbuild/CppunitTest.mk:114:
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/CppunitTest/smoketest.test]
Error 1
make: Target 'CppunitTest_smoketest' not remade because of errors.
--- snip ---
. My paste said exactly that:

> Please could you provide a test case,

No

> or adding information what is going wrong?

See above. apt-get build-dep libreoffice, install the test
depenencies of smoketest, debian/tests/smoketest in the chroot.

Regards,

Rene

Bug#943512: notion: FTBFS on i386 with test failure

[Andreas Beckmann]

Source: notion
Version: 3+2019092501-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

notion/experimental FTBFS on i386 (which is a regression from sid):
https://buildd.debian.org/status/fetch.php?pkg=notion=i386=3%2B2019092501-1=1569833560=0

   dh_auto_test -a
make -j4 test
make[1]: Entering directory '/<>'
>> pkg-config found Lua 5.3 (available: lua5.3 lua-5.3).
>> Lua 5.3 binary is /usr/bin/lua5.3 and luac is /usr/bin/luac5.3
make -C mod_xrandr test
make[2]: Entering directory '/<>/mod_xrandr'
for i in test_xrandr*.lua ; do echo 'Testing' $i ; /usr/bin/lua5.3 $i ; done
Testing test_xrandr.lua
Testing test_xrandr_remove_screen.lua
make[2]: Leaving directory '/<>/mod_xrandr'
make -C mod_xinerama test
make[2]: Entering directory '/<>/mod_xinerama'
/usr/bin/lua5.3 test_xinerama.lua

Testing:merge_contained_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1 } }

Testing:merge_contained_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=0, y=0, h=600, w=800 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1, 2 } }

Testing:merge_contained_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=100, y=100, h=400, w=600 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1, 2 } }

Testing:merge_contained_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=100, y=100, h=600, w=800 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1 } }
   2: { x=100, y=100, h=600, w=800, ids={ 2 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=0, y=0, h=600, w=800 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1, 2 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=100, y=100, h=400, w=600 }
Output:
   1: { x=0, y=0, h=600, w=800, ids={ 1, 2 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=100, y=100, h=600, w=800 }
Output:
   1: { x=0, y=0, h=700, w=900, ids={ 1, 2 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=400, y=400, h=600, w=800 }
   3: { x=500, y=0, h=300, w=500 }
Output:
   1: { x=0, y=0, h=1000, w=1200, ids={ 1, 2, 3 } }

Testing:merge_overlapping_screens
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=900, y=100, h=300, w=300 }
   3: { x=400, y=400, h=600, w=800 }
Output:
   1: { x=0, y=0, h=1000, w=1200, ids={ 1, 2, 3 } }

Testing:merge_overlapping_screens_alternative
Input:
   1: { x=0, y=0, h=600, w=800 }
   2: { x=400, y=400, h=600, w=800 }
   3: { x=900, y=100, h=300, w=300 }
Output:
   1: { x=0, y=0, h=1000, w=1200, ids={ 1, 2 } }
   2: { x=900, y=100, h=300, w=300, ids={ 3 } }
make[2]: Leaving directory '/<>/mod_xinerama'
make -C libtu test
make[2]: Entering directory '/<>/libtu'
make -C test test
make[3]: Entering directory '/<>/libtu/test'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Os -W -Wall -pedantic 
-DCF_XFREE86_TEXTPROP_BUG_WORKAROUND -DHAVE_X11_BMF   -DHAS_SYSTEM_ASPRINTF=1 
-DNOTION_RELEASE='"3+2019092501"' -MMD -Os -W -Wall -pedantic 
-DCF_XFREE86_TEXTPROP_BUG_WORKAROUND -DHAVE_X11_BMF   -DHAS_SYSTEM_ASPRINTF=1 
-DNOTION_RELEASE='"3+2019092501"'  -D_POSIX_C_SOURCE=200112L -W -Wall -pedantic 
-MMD -Os -W -Wall -pedantic -DCF_XFREE86_TEXTPROP_BUG_WORKAROUND -DHAVE_X11_BMF 
-I../..  -DHAS_SYSTEM_ASPRINTF=1 -DNOTION_RELEASE='"3+2019092501"' 
-D_XOPEN_SOURCE -D_XOPEN_SOURCE_EXTENDED -std=c99 -DCF_HAS_VA_COPY -MMD -o 
tutest ../misc.c ../tokenizer.c ../util.c ../output.c tutest.c -llua5.3 -ldl -lm
In file included from ../tokenizer.c:424:
../np/np-conv.h:15:13: warning: ‘num_to_char’ defined but not used 
[-Wunused-function]
   15 |  static int num_to_##T(T *ret, const NPNum *num, bool allow_uns_big) \
  | ^~~
../np/np-conv.h:118:1: note: in expansion of macro ‘FN_NUM_TO_SIGNED’
  118 | FN_NUM_TO_SIGNED(char, UCHAR_MAX, CHAR_MAX, CHAR_MIN)
  | ^~~~
tutest.c: In function ‘main’:
tutest.c:92:14: warning: unused parameter ‘argc’ [-Wunused-parameter]
   92 | int main(int argc, char *argv[])
  |  ^~~~
./tutest
[TESTING] libtu 
[TEST] test_get_token: [ERROR]: 33
make[3]: *** [Makefile:21: test] Error 1
make[3]: Leaving directory '/<>/libtu/test'
make[2]: *** [Makefile:50: test] Error 2
make[2]: Leaving directory '/<>/libtu'
make[1]: *** [Makefile:59: test] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 test returned exit code 2


Andreas

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

Hi,

On Fri, Oct 25, 2019 at 06:48:45PM +0200, Rene Engelhard wrote:
> > or adding information what is going wrong?
> 
> See above. apt-get build-dep libreoffice, install the test
> depenencies of smoketest, debian/tests/smoketest in the chroot.

Or just build libreoffice as is in sid. Same error when it tries to run
the first C++ unit test.

Regards,

Rene
> 

Processed: tagging 943401

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 943401 - moreinfo
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Added tag(s) moreinfo.

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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Matthias Klose]

Control: tags -1 + moreinfo

On 25.10.19 18:33, Rene Engelhard wrote:

And since then I also can just reproduce it in a chroot, too.


You didn't say that before. Please could you provide a test case, or adding 
information what is going wrong?

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21)

[Rene Engelhard]

Hi,

On Fri, Oct 25, 2019 at 06:33:13PM +0200, Rene Engelhard wrote:
> On Fri, Oct 25, 2019 at 06:25:43PM +0200, Matthias Klose wrote:
> > [...] -12 was uploaded on Oct 23, but you say
> > that the tests started failing on Oct 21.
> 
> No, the submitter did which clearly was wrong. Please read the bug,
> I said that at my very first message.

Which is why I reitled the bug already ...

> > So why do you think this is related to gcc-9?
> 
> Because the exception-related message started on Oct 24. See
> https://ci.debian.net/packages/libr/libreoffice/unstable/amd64/:
> 
> https://ci.debian.net/data/packages/unstable/amd64/libr/libreoffice/3241554.log
> oh, gcc-9 9.2.1-12.
> Log:
> https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/libreoffice/3241554/log.gz

... to what we have here. (yes, this thread has the old subject, but
that doesn't matter for the bug contents.)

Changing subject now...

Regards,

Rene

Processed: notfound 932777 in 6.0.7-1, found 932777 in 6.0.8-1~exp2, severity of 932777 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 932777 6.0.7-1
Bug #932777 [scotch] scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order 
bump_b1.grf
No longer marked as found in versions scotch/6.0.7-1.
> found 932777 6.0.8-1~exp2
Bug #932777 [scotch] scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order 
bump_b1.grf
There is no source info for the package 'scotch' at version '6.0.8-1~exp2' with 
architecture ''
Unable to make a source version for version '6.0.8-1~exp2'
Marked as found in versions 6.0.8-1~exp2.
> severity 932777 serious
Bug #932777 [scotch] scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order 
bump_b1.grf
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#943476: django-reversion: Python2 removal in sid/bullseye + Django 2.2 support

[Sandro Tosi]

control: retitle -1 django-reversion: Django 2.2 support
control: user debian-pyt...@lists.debian.org
control: usertag - py2removal

On Fri, 25 Oct 2019 11:54:34 +0200 Thomas Goirand  wrote:
> Source: django-reversion
> Version: 3.0.3-1
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

python2 support was dropped as part of 3.0.4-1
(https://tracker.debian.org/news/1045684/accepted-django-reversion-304-1-source-all-into-unstable/),
so i removed the tags for py2removal as it doesnt apply here.

> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests (the specific reason can be found searching this
> source package in
> https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).

please be careful with cut & paste :) django-reversion is not in that
list as it was not flagged as part of the second set of MBF bugs

> Moreover, this package needs to add support for Django 2.2 which is is SID
> since 3 days after Buster is released. Your package will be AUTORM if you
> don't do anything to fix the situation.

this is still valid, and there might be 2.2 support upstream already
(had a very quick glance at the repo)

Processed (with 2 errors): Re: django-reversion: Python2 removal in sid/bullseye + Django 2.2 support

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 django-reversion: Django 2.2 support
Bug #943476 [src:django-reversion] django-reversion: Python2 removal in 
sid/bullseye + Django 2.2 support
Changed Bug title to 'django-reversion: Django 2.2 support' from 
'django-reversion: Python2 removal in sid/bullseye + Django 2.2 support'.
> user debian-pyt...@lists.debian.org
Unknown command or malformed arguments to command.

> usertag - py2removal
Unknown command or malformed arguments to command.


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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

Hi,

On Fri, Oct 25, 2019 at 06:25:43PM +0200, Matthias Klose wrote:
> [...] -12 was uploaded on Oct 23, but you say
> that the tests started failing on Oct 21.

No, the submitter did which clearly was wrong. Please read the bug,
I said that at my very first message.

> So why do you think this is related to gcc-9?

Because the exception-related message started on Oct 24. See
https://ci.debian.net/packages/libr/libreoffice/unstable/amd64/:

https://ci.debian.net/data/packages/unstable/amd64/libr/libreoffice/3241554.log
oh, gcc-9 9.2.1-12.
Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/libreoffice/3241554/log.gz

And since then I also can just reproduce it in a chroot, too.

Regards,

Rene

Bug#933334: ugene: FTBFS in buster (dpkg-shlibdeps error)

[Santiago Vila]

On Fri, Oct 25, 2019 at 05:49:25PM +0200, Andreas Beckmann wrote:
> On Mon, 29 Jul 2019 11:02:45 + Santiago Vila  wrote:
> > Package: src:ugene
> > Version: 1.31.1+dfsg-1
> 
> > I tried to build this package in buster but it failed:
> 
> I cannot reproduce this in buster, ugene just builds fine in my pbuilder
> buster environment (normal, -A, -B; amd64 and i386). Did you mean bullseye?

I meant buster. I only tried amd64, where -A works and -B fails.

I've put all my failed build logs here:

https://people.debian.org/~sanvila/build-logs/ugene/

I'm using sbuild. You will also see that I'm using eatmydata, but at
least in one build log I didn't use eatmydata and it also failed, so
eatmydata is not to blame for the failure.

> In sid it now fails with
> 
> make[3]: *** No rule to make target 'QtWebKit/QWebView', needed by
> '_tmp/ui/ui_Reporter.h'.  Stop.

That's very strange because sid has version 1.31.1+dfsg-1 as well.
It would seem that this is a Makefile bug and it worked for you by
pure chance in buster.

I can offer ssh access to one of my machines, where the problem
happened 100% of the time so far. Please contact me privately for
details.

Thanks.

Bug#943510: python-urllib3: FTBFS with test failures

[Andreas Beckmann]

Source: python-urllib3
Version: 1.25.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

python-urllib3/experimental FTBFS with some failing tests:
https://buildd.debian.org/status/fetch.php?pkg=python-urllib3=all=1.25.6-1=1570856398=0

   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7_urllib3/build; 
python2.7 -m pytest --ignore=test/appengine --ignore=test/with_dummyserver 
--ignore=test/test_connectionpool.py --ignore=test/test_ssl.py 
--ignore=test/contrib/test_pyopenssl.py 
--ignore=test/contrib/test_securetransport.py 
--ignore=test/contrib/test_socks.py -k-test_recent_date
= test session starts ==
platform linux2 -- Python 2.7.17rc1, pytest-4.6.5, py-1.8.0, pluggy-0.12.0
rootdir: /<>, inifile: setup.cfg
collected 476 items / 1 deselected / 475 selected

test/test_collections.py .   [  7%]
test/test_compatibility.py ...   [  8%]
test/test_connection.py  [  9%]
test/test_exceptions.py .[ 12%]
test/test_fields.py ...  [ 15%]
test/test_filepost.py ...[ 17%]
test/test_no_ssl.py ..   [ 17%]
test/test_poolmanager.py .   [ 23%]
test/test_proxymanager.py ...[ 23%]
test/test_queue_monkeypatch.py . [ 24%]
test/test_response.py ..sss. [ 34%]
..   [ 37%]
test/test_retry.py . [ 45%]
test/test_util.py ..s... [ 56%]
 [ 71%]
F..F..s...s. [ 86%]
...  [ 96%]
test/test_wait.py .  [ 99%]
test/contrib/test_pyopenssl_dependencies.py ss   [100%]

=== FAILURES ===
_ 
TestUtil.test_parse_url[http://K\xf6nigsg\xe4\xdfchen.de/stra\xdfe-expected_url27]
 _

self = 
url = 'http://Königsgäßchen.de/straße'
expected_url = Url(scheme='http', auth=None, host='xn--knigsgchen-b4a3dun.de', 
port=None, path='/stra%C3%9Fe', query=None, fragment=None)

@pytest.mark.parametrize(
"url, expected_url",
chain(parse_url_host_map, non_round_tripping_parse_url_host_map),
)
def test_parse_url(self, url, expected_url):
>   returned_url = parse_url(url)

test/test_util.py:310: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
urllib3/util/url.py:401: in parse_url
return six.raise_from(LocationParseError(source_url), None)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

value = LocationParseError(u'Failed to parse: 
http://K\xf6nigsg\xe4\xdfchen.de/stra\xdfe',)
from_value = None

def raise_from(value, from_value):
>   raise value
E   LocationParseError: Failed to parse: 
http://K\xf6nigsg\xe4\xdfchen.de/stra\xdfe

/usr/lib/python2.7/dist-packages/six.py:737: LocationParseError
_ 
TestUtil.test_url_vulnerabilities[http://\u30d2:\u30ad@\u30d2.abc.\u30cb/\u30d2?\u30ad#\u30ef-expected_url5]
 _

self = 
url = 'http://ヒ:キ@ヒ.abc.ニ/ヒ?キ#ワ'
expected_url = Url(scheme=u'http', auth=u'%E3%83%92:%E3%82%AD', 
host=u'xn--pdk.abc.xn--idk', port=None, path=u'/%E3%83%92', query=u'%E3%82%AD', 
fragment=u'%E3%83%AF')

@pytest.mark.parametrize("url, expected_url", url_vulnerabilities)
def test_url_vulnerabilities(self, url, expected_url):
if expected_url is False:
with pytest.raises(LocationParseError):
parse_url(url)
else:
>   assert parse_url(url) == expected_url

test/test_util.py:436: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
urllib3/util/url.py:401: in parse_url
return six.raise_from(LocationParseError(source_url), None)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

value = LocationParseError(u'Failed to parse: 
http://\u30d2:\u30ad@\u30d2.abc.\u30cb/\u30d2?\u30ad#\u30ef',)
from_value = None

def raise_from(value, from_value):
>   raise value
E   LocationParseError: Failed to parse: 
http://\u30d2:\u30ad@\u30d2.abc.\u30cb/\u30d2?\u30ad#\u30ef

/usr/lib/python2.7/dist-packages/six.py:737: LocationParseError
 2 failed, 465 passed, 8 skipped, 1 deselected in 10.96 seconds 
E: pybuild 

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[Andreas Beckmann]

Source: python-django
Version: 2:3.0~beta1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

python-django/experimental FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=python-django=all=2%3A3.0%7Ebeta1-1=1571079369=0


==
FAIL: test_explicit_ForeignKey 
(nested_foreign_keys.tests.DeeplyNestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 176, in 
test_explicit_ForeignKey

self.assertEqual(Package.objects.exclude(screening__movie__director=self.director).count(),
 1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_inheritance (nested_foreign_keys.tests.DeeplyNestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 153, in 
test_inheritance

self.assertEqual(Event.objects.exclude(screening__movie__director=self.director).count(),
 1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_explicit_ForeignKey 
(nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 100, in 
test_explicit_ForeignKey

self.assertEqual(Package.objects.exclude(screening__movie=self.movie).count(), 
1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_explicit_ForeignKey_NullFK 
(nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 121, in 
test_explicit_ForeignKey_NullFK

self.assertEqual(PackageNullFK.objects.exclude(screening__movie=self.movie).count(),
 2)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 2

==
FAIL: test_inheritance (nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 53, in 
test_inheritance

self.assertEqual(Event.objects.exclude(screening__movie=self.movie).count(), 1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_inheritance_null_FK 
(nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File 

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Matthias Klose]

On 25.10.19 18:09, Rene Engelhard wrote:

Hi,

On Fri, Oct 25, 2019 at 05:59:53PM +0200, Rene Engelhard wrote:

OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.


no. based on what rationale?


And to prevent said gcc-9 version from migrating, to not break something
else (no idea whether it does, but..).

The Release Team asked me exactly this: to reassign the bug to gcc-9.


base on what rationale?

> As can be seen on [1], the autopkgtests started failing this Monday and
> succeeded only once since then.

At this time, there was no new gcc-9 in the archive, -9 was on the archive on 
Oct 8, -10 and -11 are ftbfs, and -12 was uploaded on Oct 23, but you say that 
the tests started failing on Oct 21.  So why do you think this is related to gcc-9?

Processed: bug 885810 is forwarded to https://github.com/DaveDavenport/gmpc/issues/16

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 885810 https://github.com/DaveDavenport/gmpc/issues/16
Bug #885810 [src:gmpc] gmpc: Depends on libunique
Set Bug forwarded-to-address to 
'https://github.com/DaveDavenport/gmpc/issues/16'.
> thanks
Stopping processing here.

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

Processed: reassign 943401 to libstdc++6, found 943401 in 9.2.1-12

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 943401 libstdc++6
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Ignoring request to reassign bug #943401 to the same package
> found 943401 9.2.1-12
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Marked as found in versions gcc-9/9.2.1-12.
> thanks
Stopping processing here.

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

Processed: Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 943401 libstdc++6
Bug #943401 [src:libreoffice] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Bug reassigned from package 'src:libreoffice' to 'libstdc++6'.
No longer marked as found in versions libreoffice/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Lower the severity of unreproducible report to prevent auto-removal
> severity 941267 important
Bug #941267 [ukwm] ukwm can't start, dmesg has segfault error info 
libukwm-cogl-1.so [b5b4c000+68000]
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

Hi,

On Fri, Oct 25, 2019 at 05:59:53PM +0200, Rene Engelhard wrote:
> > > OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.
> > 
> > no. based on what rationale?

And to prevent said gcc-9 version from migrating, to not break something
else (no idea whether it does, but..). 

The Release Team asked me exactly this: to reassign the bug to gcc-9.

Regards,

Rene

Processed: found 943401 in 9.2.1-12

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 943401 9.2.1-12
Bug #943401 [src:libreoffice] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
The source 'libreoffice' and version '9.2.1-12' do not appear to match any 
binary packages
Marked as found in versions libreoffice/9.2.1-12.
> thanks
Stopping processing here.

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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

reassign 943401 libstdc++6
thanks

On Fri, Oct 25, 2019 at 05:53:54PM +0200, Matthias Klose wrote:
> Control: reassign -1 src:libreoffice
> 
> On 25.10.19 17:31, Rene Engelhard wrote:
> > reassign 943401 libstdc++6
> > found 943401 9.2.1-12
> > thanks
> > 
> > Hi,
> > 
> > On Fri, Oct 25, 2019 at 12:21:11PM +0200, Matthias Klose wrote:
> > > > I guess I need to disable make check to get round this.. (Unless someone
> > > > at GCC tells me what change libstdc++6(?) might have to cause this or
> > > > some other debugging help...)
> > > 
> > > gcc-9 9.2.1-9 (r276687) was uploaded on Oct 10, the next version built in
> > > the archive was 9.2.1-12 (r277294), built on Oct 23. Fyi, I see these 
> > > issues
> > > in Ubuntu focal as well.
> > 
> > OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.
> 
> no. based on what rationale?

Because libreoffice didn't change. gcc-9 did. And you yourself say
that it also affects Ubuntu which has an older libreoffice version.

If you say it's a libreoffice bug you should say why - until then i
assume it's some gcc-9 change.

Regards,

Rene

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Matthias Klose]

Control: reassign -1 src:libreoffice

On 25.10.19 17:31, Rene Engelhard wrote:

reassign 943401 libstdc++6
found 943401 9.2.1-12
thanks

Hi,

On Fri, Oct 25, 2019 at 12:21:11PM +0200, Matthias Klose wrote:

I guess I need to disable make check to get round this.. (Unless someone
at GCC tells me what change libstdc++6(?) might have to cause this or
some other debugging help...)


gcc-9 9.2.1-9 (r276687) was uploaded on Oct 10, the next version built in
the archive was 9.2.1-12 (r277294), built on Oct 23. Fyi, I see these issues
in Ubuntu focal as well.


OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.


no. based on what rationale?

Processed: Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:libreoffice
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Bug reassigned from package 'libstdc++6' to 'src:libreoffice'.
No longer marked as found in versions gcc-9/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set

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

Bug#943506: python3-apsw,python3-apsw-dbg: both ship /usr/lib/python3/dist-packages/apsw.cpython-37dm-x86_64-linux-gnu.so

[Andreas Beckmann]

Package: python3-apsw,python3-apsw-dbg
Version: 3.29.0-r1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python3-apsw-dbg.
  Preparing to unpack .../python3-apsw-dbg_3.29.0-r1-1_amd64.deb ...
  Unpacking python3-apsw-dbg (3.29.0-r1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-apsw-dbg_3.29.0-r1-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/apsw.cpython-37dm-x86_64-linux-gnu.so', which 
is also in package python3-apsw 3.29.0-r1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-apsw-dbg_3.29.0-r1-1_amd64.deb


cheers,

Andreas


python3-apsw=3.29.0-r1-1_python3-apsw-dbg=3.29.0-r1-1.log.gz
Description: application/gzip

Processed: tagging 943401

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 943401 - help
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Removed tag(s) help.
> thanks
Stopping processing here.

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

Bug#933334: ugene: FTBFS in buster (dpkg-shlibdeps error)

[Andreas Beckmann]

On Mon, 29 Jul 2019 11:02:45 + Santiago Vila  wrote:
> Package: src:ugene
> Version: 1.31.1+dfsg-1

> I tried to build this package in buster but it failed:

I cannot reproduce this in buster, ugene just builds fine in my pbuilder
buster environment (normal, -A, -B; amd64 and i386). Did you mean bullseye?

In sid it now fails with

make[3]: *** No rule to make target 'QtWebKit/QWebView', needed by
'_tmp/ui/ui_Reporter.h'.  Stop.

Andreas

Processed: retitle 943401 to libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure instantiating exceptionprotector) ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 943401 libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure 
> instantiating exceptionprotector)
Bug #943401 [libstdc++6] C++ Unit tests failing (Failure instantiating 
protector)
Changed Bug title to 'libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)' from 'C++ Unit tests failing 
(Failure instantiating protector)'.
> affects 943401 src:libreoffice
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Added indication that 943401 affects src:libreoffice
> thanks
Stopping processing here.

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

Processed: tagging 943396

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 943396 + sid bullseye
Bug #943396 [src:fftw3] FTBFS on armhf: testsuite segfault
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 943401 libstdc++6
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector)
Bug reassigned from package 'src:libreoffice' to 'libstdc++6'.
Ignoring request to alter found versions of bug #943401 to the same values 
previously set
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> found 943401 9.2.1-12
Bug #943401 [libstdc++6] C++ Unit tests failing (Failure instantiating 
protector)
Marked as found in versions gcc-9/9.2.1-12.
> thanks
Stopping processing here.

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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Rene Engelhard]

reassign 943401 libstdc++6
found 943401 9.2.1-12
thanks

Hi,

On Fri, Oct 25, 2019 at 12:21:11PM +0200, Matthias Klose wrote:
> > I guess I need to disable make check to get round this.. (Unless someone
> > at GCC tells me what change libstdc++6(?) might have to cause this or
> > some other debugging help...)
> 
> gcc-9 9.2.1-9 (r276687) was uploaded on Oct 10, the next version built in
> the archive was 9.2.1-12 (r277294), built on Oct 23. Fyi, I see these issues
> in Ubuntu focal as well.

OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.

Regards,

Rene

Processed: reassign 941982 to wnpp ..., severity of 941982 is normal, affects 941982

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 941982 wnpp
Bug #941982 [libsys-info-base-perl] libsys-info-base-perl: missing file 
Sys/Info.pm
Bug reassigned from package 'libsys-info-base-perl' to 'wnpp'.
No longer marked as found in versions libsys-info-base-perl/0.7807-2.
Ignoring request to alter fixed versions of bug #941982 to the same values 
previously set
> retitle 941982 ITP: libsys-info-perl -- module to fetch information from the 
> host system
Bug #941982 [wnpp] libsys-info-base-perl: missing file Sys/Info.pm
Changed Bug title to 'ITP: libsys-info-perl -- module to fetch information from 
the host system' from 'libsys-info-base-perl: missing file Sys/Info.pm'.
> severity 941982 normal
Bug #941982 [wnpp] ITP: libsys-info-perl -- module to fetch information from 
the host system
Severity set to 'normal' from 'grave'
> affects 941982 libsys-info-base-perl
Bug #941982 [wnpp] ITP: libsys-info-perl -- module to fetch information from 
the host system
Added indication that 941982 affects libsys-info-base-perl
> thanks
Stopping processing here.

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

Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

[Vincent Lefevre]

Control: tags -1 + upstream
Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=130819

On 2019-10-24 11:00:28 +0200, Vincent Lefevre wrote:
> However, with the default urllist value, it is downloaded using http
> (not https). One needs to set urllist to
> 
>   [q[https://www.cpan.org/]]

I've just reported the bug upstream.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream
Bug #942851 [src:perl] perl: CPAN.pm is insecure by default, no warnings
Added tag(s) upstream.
> forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=130819
Bug #942851 [src:perl] perl: CPAN.pm is insecure by default, no warnings
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=130819'.

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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 943401 C++ Unit tests failing (Failure instantiating protector)
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector
Changed Bug title to 'C++ Unit tests failing (Failure instantiating protector)' 
from 'C++ Unit tests failing (Failure instantiating protector'.
>
End of message, stopping processing here.

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

Bug#943396: FTBFS on armhf: testsuite segfault

[Graham Inggs]

On Thu, 24 Oct 2019 at 21:30, Andreas Beckmann  wrote:
> Is this reproducible in buster, too, or limited to sid/bullseye?

Reproducible builds [1] says sid and bullseye only.


[1] https://tests.reproducible-builds.org/debian/history/armhf/fftw3.html

Bug#942275: marked as done (libmoox-options-perl: test regression with librole-tiny-perl 2.001003-1)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 11:49:17 +
with message-id 
and subject line Bug#942275: fixed in librole-tiny-perl 2.001004-1
has caused the Debian Bug report #942275,
regarding libmoox-options-perl: test regression with librole-tiny-perl 
2.001003-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.)


-- 
942275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmoox-options-perl
Version: 4.103-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, libmoox-options-perl has a test
failure which also makes the package FTBFS:

https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmoox-options-perl/3150674/log.gz

t/16-namespace_clean.t .. 
ok 1 - TestNamespaceClean is a package
Can't locate object method "__" via package "TestNamespaceClean" at 
/usr/share/perl5/MooX/Options/Role.pm line 352.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed 


Currently this only happens in unstable, and I haven't yet seen why.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWF9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYIqw//XGnU4dpmTGHf/zNwzGrxbtXxwtCws0FycziVOMyibaHrsSnfWo1z4q9x
S2l9SRolRx6QdzS0iXdege9Ay0tqAvE+ae6lGkHsb6zg8fe1oGGkh8B35TMx6U0j
jhjjtJU0iruB0mMr783TKH/4kWlAOfTprq6C0MPbiJ5WBm3v+sCe2JArfKIJhcW6
GheUF+lH2zsXR9u6AcZK5uOlxo/Bjawak6akbxbNfPxxcpOWKmUz9V1h8iaElim6
qqgiAJRXMDty0+tNP3tYYK4ta4cwUzj2cGevfBIBlNYhUMsK7sRlLjO2Rb6e22mU
wwr5HGcEjkr1o//h7wZ1bYU/yK5GDtrw0lnbluG9qHu1cO0kIYF0Cut8wTWisw9q
aPYau5b6xE+70swsRiArrA3UPrmWKgUK2lRhZC1MVzpakFT01uaINwaMyCL606bG
jB4/g7+BbKmLCyTSOx0uWaRIG5KgtFQTm8Dm7agjQdsLVMTmOXzRQi7saP0slHCT
ak80F2h4LY3PtlNWK9+T1RBHkC0FaZxOqWVEVUVXC+U4kSQzF8F5ir8NwiDPKr1E
+kYXOdecvcKw1nC+SKQIJLrAt2ibTjogd33v5QXIjRNd+/lHtZeHANV5m5TeNqWK
uNEo2qrVys+d2RAWBjvboxJgtW7K24cMnUTYIw6C9kc2UJc7/K4=
=vx9q
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: librole-tiny-perl
Source-Version: 2.001004-1

We believe that the bug you reported is fixed in the latest version of
librole-tiny-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated librole-tiny-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Oct 2019 13:30:00 +0200
Source: librole-tiny-perl
Architecture: source
Version: 2.001004-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 942275
Changes:
 librole-tiny-perl (2.001004-1) unstable; urgency=medium
 .
   * Import upstream version 2.001004.
 Fixes "libmoox-options-perl: test regression with librole-tiny-perl
 2.001003-1" (Closes: #942275)
   * Update years of packaging copyright.
   * Annotate test-only build dependencies with .
   * debian/watch: use uscan version 4.
   * Remove obsolete fields Name, Contact from debian/upstream/metadata.
Checksums-Sha1:
 d1b37afe2f71ac9100e376c19f9f2cbf27f18158 2520 librole-tiny-perl_2.001004-1.dsc
 e116b1a31c8b9930010671ec67f59ecd2e68c5f3 31569 
librole-tiny-perl_2.001004.orig.tar.gz
 1d0a7c8f2a1cda2fcd6659b09dfd7638051f423a 3548 
librole-tiny-perl_2.001004-1.debian.tar.xz
Checksums-Sha256:
 59c89fe886228fca3395eefdcf67505495a0f02f5a6641ddb6d03ba4847b0ca3 2520 
librole-tiny-perl_2.001004-1.dsc
 92ba5712850a74102c93c942eb6e7f62f7a4f8f483734ed289d08b324c281687 31569 
librole-tiny-perl_2.001004.orig.tar.gz
 75415dd92c33f40bdb3be3854bd98e56e9e56988270b3a7ca240fff10b16b360 3548 
librole-tiny-perl_2.001004-1.debian.tar.xz
Files:
 225563d7bc98c40b85f5cc0c7a6e3a0a 2520 perl optional 
librole-tiny-perl_2.001004-1.dsc
 98446826608b1e943e65c1f6e35942fe 31569 perl optional 

Bug#943320: marked as done (python3-pluggy: missing dependency on python3-importlib-metadata)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 13:45:50 +0200
with message-id <2365b39e-5476-8c8c-e07a-44c541689...@debian.org>
and subject line fixed in 0.13.0-2
has caused the Debian Bug report #943320,
regarding python3-pluggy: missing dependency on python3-importlib-metadata
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.)


-- 
943320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pluggy
Version: 0.13.0-1
Severity: serious
X-Debbugs-CC: rb-gene...@lists.reproducible-builds.org

Hi,

The python3-pluggy binary package appears to be missing a dependency
on python3-importlib-metadata:

I: pybuild base:217: cd 
/tmp/buildd/diffoscope-127/.pybuild/cpython3_3.7/build; python3.7 -m pytest -vv 
-r sxX -l --cov=diffoscope --cov-report=term-missing --cov-report=html
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/pytest.py", line 8, in 
from _pytest.assertion import register_assert_rewrite
  File "/usr/lib/python3/dist-packages/_pytest/assertion/__init__.py", line 
13, in 
from _pytest.assertion import rewrite
  File "/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py", line 
24, in 
from _pytest.assertion import util
  File "/usr/lib/python3/dist-packages/_pytest/assertion/util.py", line 11, 
in 
import _pytest._code
  File "/usr/lib/python3/dist-packages/_pytest/_code/__init__.py", line 7, 
in 
from .code import Code  # noqa
  File "/usr/lib/python3/dist-packages/_pytest/_code/code.py", line 15, in 

import pluggy
  File "/usr/lib/python3/dist-packages/pluggy/__init__.py", line 16, in 

from .manager import PluginManager, PluginValidationError
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 11, in 

import importlib_metadata
ModuleNotFoundError: No module named 'importlib_metadata'

This appears to be a regression from 0.12.0-1 (which has this
dependency). Discovered when trying to release diffoscope on behalf on
the Reproducible Builds[0] effort hence the X-Debbugs-CC, but likely
affects other packages.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---

Version: 0.13.0-2--- End Message ---

Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Markus Koschany]

Control: block 943470 by 942349

Hello,

Am 25.10.19 um 01:49 schrieb Jens Rottmann:
> Ping.
> 
> As Jonas anticipated, regression in Stable: ublock no longer works after
> Firefox ESR updated to 68.
> 
> Thanks and best regards,
> Jens

The testing version of ublock-origin is pending approval by the release
team. [1] Once they approve the backport, I will upload 1.22.2+dfsg to
stable and oldstable.

Regards,

Markus


[1] https://bugs.debian.org/942349



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Debian Bug Tracking System]

Processing control commands:

> block 943470 by 942349
Bug #943470 [webext-ublock-origin] webext-ublock-origin: Version in stable not 
working after [DSA 4549-1] firefox-esr security update
943470 was not blocked by any bugs.
943470 was not blocking any bugs.
Added blocking bug(s) of 943470: 942349

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

Processed: Re: Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Debian Bug Tracking System]

Processing control commands:

> block 943470 by 942349
Bug #943470 [webext-ublock-origin] webext-ublock-origin: Version in stable not 
working after [DSA 4549-1] firefox-esr security update
943470 was blocked by: 942349
943470 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #943470 to the same blocks 
previously set

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

Processed: Re: Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Debian Bug Tracking System]

Processing control commands:

> block 943470 by 942349
Bug #943470 [webext-ublock-origin] webext-ublock-origin: Version in stable not 
working after [DSA 4549-1] firefox-esr security update
943470 was blocked by: 942349
943470 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #943470 to the same blocks 
previously set

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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 943401 1:6.3.3~rc1-1
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector
No longer marked as found in versions libreoffice/1:6.3.3~rc1-1.
> thanks
Stopping processing here.

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

Processed: retitle 942851 to perl: CPAN.pm is insecure by default, no warnings, tagging 943439

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 942851 perl: CPAN.pm is insecure by default, no warnings
Bug #942851 [src:perl] perl-modules-5.30: CPAN.pm is insecure by default, no 
warnings
Changed Bug title to 'perl: CPAN.pm is insecure by default, no warnings' from 
'perl-modules-5.30: CPAN.pm is insecure by default, no warnings'.
> tags 943439 + sid bullseye
Bug #943439 {Done: Markus Koschany } [src:asc] src:asc: Please 
update/remove libwxgtk3.0-dev build-dependency
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Matthias Klose]

On 25.10.19 07:46, Rene Engelhard wrote:

retitle 943401 C++ Unit tests failing (Failure instantiating protector
"/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/LinkTarget/Library/unoexceptionprotector.so",
"unoexceptionprotector")
severity 943401 serious
tag 943401 + sid
tag 943401 + help
thanks

Hi,

On Thu, Oct 24, 2019 at 07:21:47PM +0200, Rene Engelhard wrote:

On Thu, Oct 24, 2019 at 06:19:55PM +0200, Rene Engelhard wrote:

So they might be just flaky? That is not new (in buildd builds they also just 
som


So, the last exception one (which I badly edited out of my last mail, after I
actually mentioned it..  - my bad.) is reproducible here in a quick
"debian/tests/smoketest" run in a uptodate sid chroot.

Given LO didn't change (what gets installed) and the exceptionprotector stuff 
gets
built with the new(er) g++ and this ends up in

Failure instantiating protector 
"/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/LinkTarget/Library/unoexceptionprotector.so",
 "unoexceptionprotector"
make: *** 
[/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/solenv/gbuild/CppunitTest.mk:114:
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/CppunitTest/smoketest.test]
 Error 1
make: Target 'CppunitTest_smoketest' not remade because of errors.


Sigh, ok, that also fails now in builds running any(?) cppunit test

I guess I need to disable make check to get round this.. (Unless someone
at GCC tells me what change libstdc++6(?) might have to cause this or
some other debugging help...)


gcc-9 9.2.1-9 (r276687) was uploaded on Oct 10, the next version built in the 
archive was 9.2.1-12 (r277294), built on Oct 23. Fyi, I see these issues in 
Ubuntu focal as well.

Bug#933781: marked as done (python3-django-pagination: fails to install: SyntaxError: invalid syntax)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 10:19:04 +
with message-id 
and subject line Bug#933781: fixed in django-pagination 1.0.7-4
has caused the Debian Bug report #933781,
regarding python3-django-pagination: fails to install: SyntaxError: invalid 
syntax
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.)


-- 
933781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-pagination
Version: 1.0.7-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python3-django-pagination (1.0.7-3) ...
File 
"/usr/lib/python3/dist-packages/pagination/templatetags/pagination_tags.py", 
line 225
  except KeyError, AttributeError:
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-django-pagination (--configure):
   installed python3-django-pagination package post-installation script 
subprocess returned error exit status 1
  Processing triggers for libc-bin (2.28-10) ...
  Errors were encountered while processing:
   python3-django-pagination


cheers,

Andreas


python3-django-pagination_1.0.7-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: django-pagination
Source-Version: 1.0.7-4

We believe that the bug you reported is fixed in the latest version of
django-pagination, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated django-pagination package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2019 12:00:48 +0200
Source: django-pagination
Architecture: source
Version: 1.0.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Closes: 933781
Changes:
 django-pagination (1.0.7-4) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * Bump debhelper-compat to 11
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Thomas Goirand ]
   * Team upload.
   * Add python3-fix-for-except.patch (Closes: #933781).
Checksums-Sha1:
 1c81c58a72d552123ad148c6e252d9d6b8f147a9 2173 django-pagination_1.0.7-4.dsc
 3af497c45faf9ca0e8f80b84fc990fb3303f4acd 2956 
django-pagination_1.0.7-4.debian.tar.xz
 a53c400d58edea7a6143fae707b332914ef779ac 6045 
django-pagination_1.0.7-4_amd64.buildinfo
Checksums-Sha256:
 b1e4f9e3433873e0ff0c3bf652a4a5c467cf2f0e2484154e27ca097e31d1fb6d 2173 
django-pagination_1.0.7-4.dsc
 7f9ca9dd62245778321e88ede97330066619ddc4c58483d28f419e2285357d7a 2956 
django-pagination_1.0.7-4.debian.tar.xz
 f4f866f5255954d8bdebeaac8b3fe785f34c825ddce30cc70790e65168cd49bf 6045 
django-pagination_1.0.7-4_amd64.buildinfo
Files:
 dc8969e194aa3c136eace2b74307a240 2173 python optional 
django-pagination_1.0.7-4.dsc
 7bb9adaa01e635d8c0160be958b61772 2956 python optional 
django-pagination_1.0.7-4.debian.tar.xz
 156117ff9bc75ff5ec3a56726a06582b 6045 python optional 
django-pagination_1.0.7-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl2yyLgACgkQ1BatFaxr
Q/7gOw//bkH/nTe8Lu/blQLG5ulDpe8panFkKDWDMyuVEG68E9FMmIIc5ZN2ntcg
n8brWqfsAIR52GWW/S9f51+nzo/A33Ys0HOglJVK+z7zd6bLSvZVZ37u+iwmpjoB
gnlfT/w4fRwv4V8bnC6z8Z4Stz7K3ZKoMI1o7HJJXXg6Og1rLJ14gbpDlGGqKtha
x9UppzRL5TEN5y+mVU/rz8YG77q7OVHehdgc4e02DeV1NBlYVfG6EPJCMIkuEjlZ
LbT03VP1tnad+ZkC6coh1pZE0BV8VPnvuSPVivz8xWfFjlb8ifxysWGtV+TElLnh
ui8euYMze2a/ALEctCf7sw5SzF2kWEzSKX6++5s82jCQzHYVng6Nwtz7GHC+8fDr
af1MnZSOrrUD9zJV0ERoZN4KZRwjFO0rBLgl6BuL7PwHSLlpKmEWpj9vEXgqgQ6v
obbGE6izoh8glg5i49/AKmUCbk0Scbt+7g1fiLWjfF++79KEQR/f4JCDzKwQNv83
CZDVWxdvLD9dwsGlz6OIzRQgN7mBmBGec3nmyOVNOcGnmzU9bko9OO8Cc31bucrm
wXRcghMXMVMXnvEX68u/Gi5IZLW1XjBoPIBNsFWYktRylRR8tiRrSJuWgwoXiq2D
PTpWuRirJ0NZkN24IWyHMQCAPGeA1sJ+3yWt+pL0UGRFXAg617E=
=JgQ5
-END PGP SIGNATURE End Message ---

Bug#943479: FTBFS with ghc-8.6.5

[Ilias Tsitsimpis]

Source: haskell-werewolf
Version: 1.5.2.0-4
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

This package FTBFS with newer versions of GHC (ghc-8.6.5) with the
following error:

Building executable 'werewolf' for werewolf-1.5.2.0..
[ 1 of 53] Compiling Game.Werewolf.Message ( app/Game/Werewolf/Message.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Message.o )
[ 2 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledge.Command ( 
app/Game/Werewolf/Variant/NoRoleKnowledge/Command.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledge/Command.o
 )
[ 3 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledge.Engine ( 
app/Game/Werewolf/Variant/NoRoleKnowledge/Engine.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledge/Engine.o
 )
[ 4 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledgeOrReveal.Command ( 
app/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.o
 )

app/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.hs:56:31: error:
• Parse error in expression!
• In the quasi-quotation:

[iFile|variant/no-role-knowledge-or-reveal/command/status/dead-players.txt|]
   |
56 | deadPlayersText game = 
[iFile|variant/no-role-knowledge-or-reveal/command/status/dead-players.txt|]
   |   
^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

-- 
Ilias

Bug#933781: marked as pending in django-pagination

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #933781 in django-pagination reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/django-pagination/commit/fb0b8261493ca6b1268502b9325404d77de32d0c


* Team upload.
  * Add python3-fix-for-except.patch (Closes: #933781).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933781

Processed: Bug#933781 marked as pending in django-pagination

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933781 [python3-django-pagination] python3-django-pagination: fails to 
install: SyntaxError: invalid syntax
Added tag(s) pending.

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

Bug#943476: django-reversion: Python2 removal in sid/bullseye + Django 2.2 support

[Thomas Goirand]

Source: django-reversion
Version: 3.0.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Dear maintainer,

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.


Moreover, this package needs to add support for Django 2.2 which is is SID
since 3 days after Buster is released. Your package will be AUTORM if you
don't do anything to fix the situation.

Cheers,

Thomas Goirand (zigo)


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#942585: marked as done (FTBFS with ghc-8.6.5 on ppc64el)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 09:48:53 +
with message-id 
and subject line Bug#942585: fixed in gtk2hs-buildtools 0.13.5.0-2
has caused the Debian Bug report #942585,
regarding FTBFS with ghc-8.6.5 on ppc64el
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.)


-- 
942585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk2hs-buildtools
Version: 0.13.4.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.haskell.org/ghc/ghc/issues/17203

This package FTBFS with ghc-8.6.5 on ppc64el. Let's remove it from
testing for now, to allow the rest of the Haskell packages to migrate.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Source: gtk2hs-buildtools
Source-Version: 0.13.5.0-2

We believe that the bug you reported is fixed in the latest version of
gtk2hs-buildtools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated gtk2hs-buildtools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Oct 2019 12:25:32 +0300
Source: gtk2hs-buildtools
Architecture: source
Version: 0.13.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 942585
Changes:
 gtk2hs-buildtools (0.13.5.0-2) unstable; urgency=medium
 .
   * Remove obsolete `BangPatterns` patch
   * Build with -O0 on ppc64el to workaround a GHC bug (Closes: #942585)
Checksums-Sha1:
 807fc55c13d184a15cda05f2e35502f7234a0405 2635 gtk2hs-buildtools_0.13.5.0-2.dsc
 79af0de4871f9d229f19e9881cac9cee2b07ee7e 7120 
gtk2hs-buildtools_0.13.5.0-2.debian.tar.xz
 1377ea10e21e500756fd528a1bbb75aacc884931 8664 
gtk2hs-buildtools_0.13.5.0-2_amd64.buildinfo
Checksums-Sha256:
 40d93c52b9f834dba9e0705206446194f3c691d60362c46c9f831011da1193b2 2635 
gtk2hs-buildtools_0.13.5.0-2.dsc
 9d9e7af95a30a49c36d013eb8c3779caf42e6eacd09b8ded6a35012a2d7963b5 7120 
gtk2hs-buildtools_0.13.5.0-2.debian.tar.xz
 08d0053228a8cb16262218a8d202407d8baffcb765968478fa75f2fedc5767b6 8664 
gtk2hs-buildtools_0.13.5.0-2_amd64.buildinfo
Files:
 a07b9cf075d9dae466a9e807e68e1cfe 2635 haskell optional 
gtk2hs-buildtools_0.13.5.0-2.dsc
 f0f821b158d60ad564cba2f90675850c 7120 haskell optional 
gtk2hs-buildtools_0.13.5.0-2.debian.tar.xz
 ad96e29402a323ee94e426bfc5a1343e 8664 haskell optional 
gtk2hs-buildtools_0.13.5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl2ywqUUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwY2xAAwdt9H9B7KJqGZnwWDg3jhXiPa2mL
hVhVJk82mt00XypeC0zF0ruGWTlEDSmJ5CrbhMY8vRcThtljLeRJ9pNElBGr0LA7
MEE+JFa4b9V+hq2coA3E3wKBbi5vyJR5ZviaH6u6ZLQutOquOaBeQGKO7UFjI7FC
Raoc5GcD6gPSOUWRVxp5Cg7Q8jMHhufFs2zVKnEE0tFNHjoq8GBCaLH84eKtZhOJ
pWe8BMwrxvekB5wiwgcMs2103jpmlsB0cQfXTY2QJ6EHcS+nQOMJnFPSOdnixYZ+
jdu4P91vgSAVttcmsJaoFgBpzSLIhlgrFrOezKvzEmrA2iqdVmS+ZLHiiXuZ6x5T
Yic5HoIfWTMsA8J2k8cLPfOywxKPO60IETLgUGk4F9BosHkcakQRnqwvXZu6YOzY
dQgSin+v/siq3IWlk2IzbhGB3vh1pCgl4BR6jeh4wcPjc4EToNuSkNior+nVqur5
EU0xbCMeJCsFc4SAkMOI/VlzE20SZeMUI8FVWq+PZ4BwHxPM56ywWH8mwIOvOHs4
Dwc6QWt7O/rFYlLqRBn22m3292wHD5easHesZoRix18sMWm8gmu54Nw+jIMj4gev
VC9SGrzAsK04h28m1OxoU8pnLqFdc1D9CVNVUjTGQfyFf0s0H/o0VVOn04M7ulrV
0lCDLKfATNp15/g=
=Rkax
-END PGP SIGNATURE End Message ---

Bug#936418: Please add support for Django 2.2

[Thomas Goirand]

Hi,

Your package also needs to support Django 2.2, which is in Sid, and
which your package is blocking the transition. At this point, as there's
only 4 Django packages remaining, your package may be left behind and
AUTORM from Testing.

Cheers,

Thomas Goirand (zigo)

Processed: django-picklefield: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 936418 django-picklefield: Py2 rm in sid/bullseye + django 2.2
Bug #936418 [src:django-picklefield] django-picklefield: Python2 removal in 
sid/bullseye
Changed Bug title to 'django-picklefield: Py2 rm in sid/bullseye + django 2.2' 
from 'django-picklefield: Python2 removal in sid/bullseye'.
>
End of message, stopping processing here.

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

Processed: severity 936418 serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 936418 serious
Bug #936418 [src:django-picklefield] django-picklefield: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#943474: Doesn't build with Django 2.2

[Thomas Goirand]

Source: django-modeltranslation
Version: 0.12.2-1
Severity: serious

Hi,

Your package doesn't build with Django 2.2, which is blocking is transition to
Testing. Please fix this ASAP. This also means fixing Py2 removal, as there's
no Py2 support in Django 2.2.

Cheers,

Thomas Goirand (zigo)

Bug#943473: autopkg tests fail with multiple python3 versions

[Matthias Klose]

Package: src:odil
Version: 0.10.0-3
Severity: serious
Tags: sid bullseye

The autopkg tests fail with multiple python3 versions, it looks like the only 
reason for that is a wrong build dependency, please replace python3-dev with 
python3-all-dev.


I didn't check if there are more issues.

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

[handsome_feng]

Tags:  moreinfo


Hi, Faris,


Can you show me the hardware environment? such as 'lspci', 'cat /proc/cpuinfo'. 
Also the OpenGL info: 'dpkg -l | grep mesa'. Since we can't reproduce here. 


Thanks!
handsome_feng

Processed: bug 943424 is forwarded to https://gitlab.freedesktop.org/plymouth/plymouth/issues/88

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 943424 https://gitlab.freedesktop.org/plymouth/plymouth/issues/88
Bug #943424 [plymouth] Plymouth prevents clean shutdown in some cases, which 
may result in data loss
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/plymouth/plymouth/issues/88'.
> thanks
Stopping processing here.

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

Bug#943470: webext-ublock-origin: Version in stable not working after [DSA 4549-1] firefox-esr security update

[Laura Arjona Reina]

Package: webext-ublock-origin
Version: 1.18.4+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

After updating Firefox in Debian stable ([DSA 4549-1] firefox-esr security
update), I can use Firefox but the ublock origin extension disappeared.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

With a new profile, I still cannot see the extension.
I have tried to remove and reinstall the package (from stable, version
1.18.4+dfsg-2) but it didn't solve the issue.
I have tried to remove the folder storage/default/moz-extension+++whatever as
suggested in 931640, with no luck.

I have installed the version in testing (1.22.2+dfsg-1), and the problem was
solved for new firefox profiles (although it appears disabled). Then, I have
removed the folder "browser-extension-data" of my old profile, and then ublock
origin also appeared in my old profile (and enabled).

I have then tried to remove the testing version (1.22.2+dfsg-1) and reinstall
the stable version (1.18.4+dfsg-2) but the extension disappeared again.

Thanks

-- 
Laura Arjona
https://wiki.debian.org/LauraArjona



-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

webext-ublock-origin depends on no packages.

Versions of packages webext-ublock-origin recommends:
ii  chromium 76.0.3809.100-1~deb10u1
ii  firefox-esr  68.2.0esr-1~deb10u1

Versions of packages webext-ublock-origin suggests:
pn  ublock-origin-doc  

-- no debconf information

Processed: fixed upstream, see also duplicate/related bug report

[Debian Bug Tracking System]

Processing control commands:

> tags 885259 + fixed-upstream
Bug #885259 [src:arandr] arandr: Depends on unmaintained pygtk
Ignoring request to alter tags of bug #885259 to the same tags previously set

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

Bug#885259: fixed upstream, see also duplicate/related bug report

[Andreas Henriksson]

Control: tags 885259 + fixed-upstream

As already mentioned in #936132 there's a new upstream release
available 0.1.10 that ports to python3 and GObject.

See #936132 for more info. (Or from people viewing this from
the other side see #885259 which should also be closed at the same time.)

Regards,
Andreas Henriksson

Processed: fixed upstream, see also duplicate/related bug report

[Debian Bug Tracking System]

Processing control commands:

> tags 885259 + fixed-upstream
Bug #885259 [src:arandr] arandr: Depends on unmaintained pygtk
Ignoring request to alter tags of bug #885259 to the same tags previously set

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

Bug#885271: dia: Python2 removal in sid/bullseye

[Andreas Henriksson]

On Fri, Oct 25, 2019 at 09:02:10AM +0200, Andreas Henriksson wrote:
> Control: tags 943016 + patch
[...]
> The easiest way to accomplish that would simply be to disable the
> python(2) plugin. Attaching a patch that does that (which maybe someone
> wants to extend with Breaks: towards affected reverse dependencies).
[...]

Improved patch attached.

v2:

- add debian/NEWS entry
- also close pygtk2 RC bug (#885271)
- add Breaks: as previously mentioned.


FYI the dia flatpak (as distributed by GNOME) seems to have recently
*enabled* building the python2 support, which means that might be an
option for those who want to continue using it.

Also note about dia on the tracker.debian.org page:
Marked for autoremoval on 23 November: #885271

Regards,
Andreas Henriksson
diff -Nru dia-0.97.3+git20160930/debian/changelog 
dia-0.97.3+git20160930/debian/changelog
--- dia-0.97.3+git20160930/debian/changelog 2018-12-01 16:02:28.0 
+0100
+++ dia-0.97.3+git20160930/debian/changelog 2019-10-25 09:23:46.0 
+0200
@@ -1,3 +1,14 @@
+dia (0.97.3+git20160930-8.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop --with-python configure flag, dh-python usage and (build-)deps.
+(Closes: #943016, #885271)
+  * Add Breaks on current versions of trac-diavisview and python-ldaptor
+as they seem to use the python bindings (see #938690 and #936830)
+  * add debian/NEWS entry about python disabled and mention dia flatpak.
+
+ -- Andreas Henriksson   Fri, 25 Oct 2019 09:23:46 +0200
+
 dia (0.97.3+git20160930-8.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dia-0.97.3+git20160930/debian/control 
dia-0.97.3+git20160930/debian/control
--- dia-0.97.3+git20160930/debian/control   2018-02-14 14:15:39.0 
+0100
+++ dia-0.97.3+git20160930/debian/control   2019-10-25 09:20:06.0 
+0200
@@ -7,7 +7,6 @@
automake,
dblatex,
debhelper (>= 10),
-   dh-python,
docbook-xml,
docbook-xsl,
intltool,
@@ -22,8 +21,6 @@
libxml-parser-perl,
libxml2-dev,
libxslt1-dev,
-   python-dev,
-   python-gtk2,
texlive-lang-cyrillic,
texlive-lang-french,
texlive-lang-german,
@@ -37,8 +34,9 @@
 
 Package: dia-common
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, python-gtk2
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: dia
+Breaks: trac-diavisview (<= 0.3-2), python-ldaptor (<= 0.0.43+debian1-7.2)
 Description: Diagram editor (common files)
  Dia is an editor for diagrams, graphs, charts etc. There is support for UML
  static structure diagrams (class diagrams), Entity-Relationship diagrams,
diff -Nru dia-0.97.3+git20160930/debian/NEWS dia-0.97.3+git20160930/debian/NEWS
--- dia-0.97.3+git20160930/debian/NEWS  1970-01-01 01:00:00.0 +0100
+++ dia-0.97.3+git20160930/debian/NEWS  2019-10-25 09:23:39.0 +0200
@@ -0,0 +1,9 @@
+dia (0.97.3+git20160930-8.2) unstable; urgency=medium
+
+  The python interface to dia has been disabled since Python 2 will
+  soon go end of life. If you have a need for the python interface
+  the current recommendation is to look into using the dia flatpak
+  as that (still as of right now) seems to carry the python2 parts
+  and might be usable for your needs.
+
+ -- Andreas Henriksson   Fri, 25 Oct 2019 09:21:38 +0200
diff -Nru dia-0.97.3+git20160930/debian/rules 
dia-0.97.3+git20160930/debian/rules
--- dia-0.97.3+git20160930/debian/rules 2018-02-11 22:52:07.0 +0100
+++ dia-0.97.3+git20160930/debian/rules 2019-10-25 08:38:05.0 +0200
@@ -9,13 +9,13 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 
 %:
-   dh $@ --parallel --with python2
+   dh $@ --parallel
 
 override_dh_auto_configure:
libtoolize --copy --force
autoreconf -fi
intltoolize
-   dh_auto_configure -- --with-python --with-cairo --with-hardbooks
+   dh_auto_configure -- --with-cairo --with-hardbooks
 
 override_dh_auto_build:
# docbook-xsl source for referenced pngs