Bug#951752: gcc-python-plugin FTBFS with python3.8

[Steve Langasek]

Package: gcc-python-plugin
Version: 0.17-5
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi Matthias,

gcc-python-plugin ftbfs with python3.8.  Attached is the patch I've uploaded
to Ubuntu for this build failure.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gcc-python-plugin-0.17/debian/patches/python3.8-compat.patch 
gcc-python-plugin-0.17/debian/patches/python3.8-compat.patch
--- gcc-python-plugin-0.17/debian/patches/python3.8-compat.patch
1969-12-31 16:00:00.0 -0800
+++ gcc-python-plugin-0.17/debian/patches/python3.8-compat.patch
2020-02-20 21:44:49.0 -0800
@@ -0,0 +1,40 @@
+Description: fix compatibility with Python 3.8
+ Python 3.8 changes the type of an element of the PyTypeObject struct
+ (https://www.python.org/dev/peps/pep-0590/) leading to compiler errors.
+Author: Steve Langasek 
+Last-Update: 2020-02-20
+Forwarded: no
+
+Index: gcc-python-plugin-0.17/gcc-python-wrapper.c
+===
+--- gcc-python-plugin-0.17.orig/gcc-python-wrapper.c
 gcc-python-plugin-0.17/gcc-python-wrapper.c
+@@ -137,7 +137,11 @@
+ sizeof(PyGccWrapperTypeObject), /*tp_basicsize*/
+ 0, /*tp_itemsize*/
+ NULL, /* tp_dealloc */
++#if PY_VERSION_HEX >= 0x0308
++0, /* tp_vectorcall_offset */
++#else
+ NULL, /* tp_print */
++#endif
+ NULL, /* tp_getattr */
+ NULL, /* tp_setattr */
+ #if PY_MAJOR_VERSION < 3
+Index: gcc-python-plugin-0.17/cpybuilder.py
+===
+--- gcc-python-plugin-0.17.orig/cpybuilder.py
 gcc-python-plugin-0.17/cpybuilder.py
+@@ -254,7 +254,11 @@
+ result += 'sizeof(%(struct_name)s), /*tp_basicsize*/\n' % 
self.__dict__
+ result += '0, /*tp_itemsize*/\n'
+ result += self.c_ptr_field('tp_dealloc')
+-result += self.c_ptr_field('tp_print')
++result += '#if PY_VERSION_HEX >= 0x0308\n' % self.__dict__
++result += '0, /*tp_vectorcall_offset*/\n' % self.__dict__
++result += '#else\n' % self.__dict__
++result += 'NULL, /*tp_print*/\n' % self.__dict__
++result += '#endif\n' % self.__dict__
+ result += self.c_ptr_field('tp_getattr')
+ result += self.c_ptr_field('tp_setattr')
+ result += '#if PY_MAJOR_VERSION < 3\n' % self.__dict__
diff -Nru gcc-python-plugin-0.17/debian/patches/series 
gcc-python-plugin-0.17/debian/patches/series
--- gcc-python-plugin-0.17/debian/patches/series2020-02-20 
05:15:45.0 -0800
+++ gcc-python-plugin-0.17/debian/patches/series2020-02-20 
21:43:59.0 -0800
@@ -4,3 +4,4 @@
 gcc-8-fix.diff
 werror.diff
 gcc-10.diff
+python3.8-compat.patch

Bug#855541: Update: actually it works

[Jean-Philippe MENGUAL]

Hi,

Ok I have just built the git release, now it works. So to maintain this 
package usable in Debian, you need to update it to the latest git 
release, from December, 28. Do you want a specific bug to request 
update? Without it, I think it is unusable now.


Regards

--
Jean-Philippe MENGUAL

Bug#855541: purple-matrix: Not ready for release yet

[Jean-Philippe MENGUAL]

Package: purple-matrix
Version: 0.0.0+git20191228-1
Followup-For: Bug #855541

Hi,

What server do you use to have this package working? Here on two
servers I get:
Failed to create e2e db table (step)

So this package seems unusable now.

Regards

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages purple-matrix depends on:
ii  libc6   2.29-10
ii  libgcrypt20 1.8.5-3
ii  libglib2.0-02.62.4-2
ii  libhttp-parser2.9   2.9.2-2
ii  libjson-glib-1.0-0  1.4.4-2
ii  libolm3 3.1.3+dfsg-2
ii  libpurple0  2.13.0-2.2+b1
ii  libsqlite3-03.31.1-2

purple-matrix recommends no packages.

purple-matrix suggests no packages.

-- debconf-show failed

Bug#947856: php-mongo-php-adapter: Remove depends/build-depends on src:mongodb

[David Prévot]

Hi Moritz,

Le 20/02/2020 à 12:43, Moritz Mühlenhoff a écrit :

> let's remove this (and php-php-mongodb)? There are no rev deps in the archive

Sure, please proceed. I uploaded those in order to enable mongoDB tests
in other packages (before being aware of the mongoDB state) so they are
pretty useless.

Regards

David



signature.asc
Description: OpenPGP digital signature

Processed: Re: ITP: gcc64 -- compiler host64 and target 32 with multilib

[Debian Bug Tracking System]

Processing control commands:

> unblock 950652 by 950542 950545 950547 950549 950550
Bug #950652 [wnpp] ITP: gcc64 -- compiler host64 and target 32 with multilib
950652 was blocked by: 950542 950550 950549 950545 950547
950652 was not blocking any bugs.
Removed blocking bug(s) of 950652: 950549, 950542, 950547, 950550, and 950545
> block 950652 by 950642 950645 950647 950649 950650
Bug #950652 [wnpp] ITP: gcc64 -- compiler host64 and target 32 with multilib
950652 was not blocked by any bugs.
950652 was not blocking any bugs.
Added blocking bug(s) of 950652: 950647, 950642, 950649, 950645, and 950650

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

Processed: py2removal bugs severity updates - 2020-02-20 23:34:55.924577+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # sslstrip is an application, has low popcon (170 < 300), and has 0 external 
> rdeps or not in testing
> severity 938564 serious
Bug #938564 [src:sslstrip] sslstrip: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#941669: marked as done (python3-rpi.gpio fails to work on aarch64 (upgrade needed))

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 23:20:32 +
with message-id 
and subject line Bug#941669: fixed in rpi.gpio 0.7.0-0.1
has caused the Debian Bug report #941669,
regarding python3-rpi.gpio fails to work on aarch64 (upgrade needed)
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.)


-- 
941669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rpi.gpio
Version: 0.6.5-1
Severity: grave
Tags: upstream
Justification: renders package unusable


Hi,

python3-rpi.gpio 0.6.5 as is current in sid, doesn't support
aarch64:

Traceback (most recent call last):
  File "./server.py", line 8, in 
import RPi.GPIO as GPIO
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 23, in 

from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!


Upstream has fixed this in the 0.7.0 release, see here
https://sourceforge.net/p/raspberry-gpio-python/tickets/161/

I am kindly asking to please update the Debian package.

Andre'

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

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

Versions of packages python3-rpi.gpio depends on:
ii  libc62.28-10
ii  python3  3.7.3-1
ii  rpi.gpio-common  0.6.5-1

python3-rpi.gpio recommends no packages.

python3-rpi.gpio suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rpi.gpio
Source-Version: 0.7.0-0.1
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rpi.gpio, 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 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rpi.gpio 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: Thu, 16 Jan 2020 16:20:40 +
Source: rpi.gpio
Binary: python3-rpi.gpio python3-rpi.gpio-dbgsym rpi.gpio-common
Architecture: source
Version: 0.7.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Raspberry Pi Maintainers 

Changed-By: Peter Michael Green 
Description:
 python3-rpi.gpio - Module to control Raspberry Pi GPIO channels (Python 3)
 rpi.gpio-common - Module to control Raspberry Pi GPIO channels (common files)
Closes: 938409 941669
Changes:
 rpi.gpio (0.7.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release
 - Fixes pi detection on arm64 (Closes: 941669)
 - Adds Raspberry pi 4 support.
   * Drop python 2 support (Closes: 938409)
   * Drop spelling.patch (fixed upstream)
Checksums-Sha1:
 cf63bbac540c1679dd9299ca16e7c6ca1e23b151 2162 rpi.gpio_0.7.0-0.1.dsc
 427089f39f13954c09d09a6a08a9249173fb8a17 30845 rpi.gpio_0.7.0.orig.tar.gz
 d9a50d93d41c41e21f09f03c5cc04da679cfd8d2 2844 rpi.gpio_0.7.0-0.1.debian.tar.xz
Checksums-Sha256:
 9658537db9464ecc57c8adb1a3951bcf32a4bea12eec1fafb7068088a7dc4fa8 2162 
rpi.gpio_0.7.0-0.1.dsc
 7424bc6c205466764f30f666c18187a0824077daf20b295c42f08aea2cb87d3f 30845 
rpi.gpio_0.7.0.orig.tar.gz
 f5dfdc8991e4f669c97abbf241e5c8eb16ca010f52fac2cf307fcfc3ff7313aa 2844 
rpi.gpio_0.7.0-0.1.debian.tar.xz
Files:
 842a102c113c22417993e3b1dd7a9117 2162 python optional rpi.gpio_0.7.0-0.1.dsc
 777617f9dea9a1680f9af43db0cf150e 30845 python optional 
rpi.gpio_0.7.0.orig.tar.gz
 7f8a7a904b1d3e08a5e05b78c10724d9 2844 python optional 
rpi.gpio_0.7.0-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl5PEEUUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuN5g/+IqyyN5E0y6Fo8hLIkonJi8bvEOyv
uvJ2GUg3X6AlL8Zq1EbUbJiT+JJqzJLwBkCE3gKVO8F5TFBKhIDn7w6H16P+zI9W
cZElIbdWGp/rz5Bw6fvz1k0X2hSM8ABVAamk20ZHG6Y9szxAznFg5icgprVxfUya
x91Tze2cxZ3r9AwRiFk1mERPKZpOTFXkF1SpAgvpIjUJXvfBqEGrRC8nQFSITMnh
Fw7WNEe06UwUDsUSFPXnST77tcYLApOYoBEO5hWJPAOL1NqyNXnjpm52YMAjsLAU

Bug#941669: python3-rpi.gpio fails to work on aarch64 (upgrade needed)

[peter green]

I just found my Debian arm64 Pi and tested this, it seems to work after setting 
"iomem=relaxed" on the kernel command line.

More than enough time has passed since my last mail where I said I would NMU 
after testing, so I have gone ahead with the upload.

Bug#947856: php-mongo-php-adapter: Remove depends/build-depends on src:mongodb

[Moritz Mühlenhoff]

On Tue, Dec 31, 2019 at 02:40:54PM -0500, mo...@debian.org wrote:
> Package: php-mongo-php-adapter
> Severity: normal
> 
> Hello,
> this package still depends/build-depends on a binary package from src:mongodb.
> As mentioned in #947743, there are several issues with mongodb:
> 
> * rc-buggy
> * un-upgreadable due to license issues
> * not part of stable
> * preventing some py2rm work
> 
> and so we're trying to remove it from Debian as it doesnt provide a good
> enough solution nor provides an actual service to our users (who very likely
> want to get a latest version of mongodb, which we cant provide).
> 
> Please remove the dependency (either binary of build-) from this package.

David,
let's remove this (and php-php-mongodb)? There are no rev deps in the archive
and this blocking the removal of src:mongodb and in turn various Python 2 
removals.

Cheers,
Moritz

Bug#885299: bumping severity of pygtk bugs

[Moritz Mühlenhoff]

On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> Control: tags -1 -buster
> 
> 
> As part of the Python2 removal, it is our intent that pygtk will be removed 
> from Testing before the release of Debian 11
> "Bullseye". Therefore, I am bumping the severity of this bug to Serious to 
> ensure that there is plenty of warning before
> the Debian 11 release and to make the eventual removal of pygtk as smooth as 
> possible.

Should griffith be removed? It's dropped from testing for two years now
and the upstream homepage vanished. Piotr, given that you're among the
upstream authors, is this still maintained?

Cheers,
Moritz

Bug#951743: OpenSSL linking without license exception

[Bastian Germann]

Package: calibre
Severity: serious

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. Please
build without the certgen extension or try to build with an OpenSSL API
compatible library like wolfssl.

Bug#948130: marked as done (timeshift FTBFS: vala error: Creation method of abstract class cannot be public.)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 21:36:44 +
with message-id 
and subject line Bug#948130: fixed in timeshift 19.01+ds-2.1
has caused the Debian Bug report #948130,
regarding timeshift FTBFS: vala error: Creation method of abstract class cannot 
be public.
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.)


-- 
948130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timeshift
Version: 19.01+ds-2
Severity: serious
Tags: ftbfs

timeshift fails to build from source.

| Utility/AsyncTask.vala:76.2-76.17: error: Creation method of abstract class 
cannot be public.
|  public AsyncTask(){
|  
| Compilation failed: 1 error(s), 11 warning(s)
| make[2]: *** [makefile:52: app-gtk] Error 1
| make[2]: Leaving directory '/build/1st/timeshift-19.01+ds/src'
| make[1]: *** [makefile:2: all] Error 2
| make[1]: Leaving directory '/build/1st/timeshift-19.01+ds'
| dh_auto_build: make -j15 "INSTALL=install --strip-program=true" returned exit 
code 2
| make: *** [debian/rules:12: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Observed by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/timeshift_19.01+ds-2.rbuild.log.gz
Observed by crossqa:
http://crossqa.debian.net/build/timeshift_19.01+ds-2_ppc64el_20200104101849.log

Helmut
--- End Message ---
--- Begin Message ---
Source: timeshift
Source-Version: 19.01+ds-2.1
Done: Steve Meliza 

We believe that the bug you reported is fixed in the latest version of
timeshift, 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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Meliza  (supplier of updated timeshift 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: Mon, 17 Feb 2020 22:33:00 -0800
Source: timeshift
Architecture: source
Version: 19.01+ds-2.1
Distribution: unstable
Urgency: high
Maintainer: Yanhao Mo 
Changed-By: Steve Meliza 
Closes: 948130
Changes:
 timeshift (19.01+ds-2.1) unstable; urgency=high
 .
   * Non-maintainer upload
   * d/patches: Add a patch to fix FTBFS (Closes: #948130)
Checksums-Sha1:
 5a2af7213ee5acc68673a6e6f29224613a4091a7 1939 timeshift_19.01+ds-2.1.dsc
 4fd9f4e83a59f80c8f8a6a1e15bfe97d357ca59e 4488 
timeshift_19.01+ds-2.1.debian.tar.xz
 d015e6ca8c75a5dd8d9198f70e4e7dee8482c3e6 14558 
timeshift_19.01+ds-2.1_amd64.buildinfo
Checksums-Sha256:
 11af3cbf342143ed0d1172fa4c8b237a3aaa38b60f39af7a9159036b132c544b 1939 
timeshift_19.01+ds-2.1.dsc
 e595351473deed202180dcaad8f0dffa9ed47f4ea352433af6993026d76a76a5 4488 
timeshift_19.01+ds-2.1.debian.tar.xz
 9ad3d7dfc455d116590613f836296b3233ca2943050975321787f952100a2b38 14558 
timeshift_19.01+ds-2.1_amd64.buildinfo
Files:
 2d9ffd730b0f204fcb204fa6c888b273 1939 utils optional timeshift_19.01+ds-2.1.dsc
 382d918ffcd5a5694cb291d854802d77 4488 utils optional 
timeshift_19.01+ds-2.1.debian.tar.xz
 9e1d581360fc972ca20c36cb5272eff9 14558 utils optional 
timeshift_19.01+ds-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl5O9boACgkQwpPntGGC
Ws6Mxw//V/Tri5ZIKnwsPyFiqqzvAiW05r8SjBtp7pxlBOXdkSm2Aeqsuze8FzDm
G/JujDjCmvUM6dI454K/K4NCUYuwcVihsQghyY5BPf5viTQwgHBc6+u7AA52V1j7
6+gtEMN9K83MU5q6pVMrYvSniwedwcznaY4cO2O6JU6OgQo75oyLM2/Go3GJ+eLp
SheVzsBJfbbYLqf8IWZoa2JBMRhomAi5Y1SJiolfoD8Mdo1BciLfbwIt+cRno/AX
FUCWldbTw1GRLblIIrJwlCeKqYt2fiBHpnQv802DV1WU4KtxJljIHRgmyi+deSA1
+250FzmVgFHlethvx18bFRROk5sP5kmD++zxirukTcqOBg302ZTMUim7ADOPF/R0
Vzh1eEYj6rqbAMGQEycEukRp8uvOQ7eekFIyv4wSHOnVYKaO47n3M/O4efsjimlk
LkpMXjnyN9PW2VKT8Bb1yZOpZz+h2SfSyEvUUvSwZsxYcN9KPq6Qklr4RnX0hLcw
uhoLVwhMeKsCi2KfGHaExEREUg3YgSlu5qq5ZHh2UiZ96fbPppk5AH4b6czgTObo
cIHTf0dYIrlyQJ7s3DEX3kbZ8+7C8yH9qduVzmR4DaReS9AVQ1OdDnTSu20nUbFy
rltTTHIRq+PfsnZ7ElxpOb5MCR5L1Rr7yoguWi+Yt1jm2H0ypt0=
=Jmug
-END PGP SIGNATURE End Message ---

Bug#951735: klayout: FTBFS against Ruby2.7 on different $arch

[Utkarsh Gupta]

Package: klayout
Version: 0.26.2-1
Severity: critical
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition

Dear Maintainer,

There's FTBFS against Ruby2.7 on different architectures which is
blocking our transition going on right now.
I reported this upstream, too (https://github.com/KLayout/klayout/issues/506).

The failures against Ruby2.7 on different $arch could be found here:
https://buildd.debian.org/status/package.php?p=klayout

Requesting you to please take a look at it and help us in fixing them :)


Best,
Utkarsh
---

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

Kernel: Linux 5.4.0-4-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=U
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages klayout depends on:
ii  libc6 2.29-10
ii  libgcc-s1 [libgcc1]   10-20200211-1
ii  libgcc1   1:10-20200211-1
ii  libpython3.7  3.7.6-1+b1
ii  libqt5core5a  5.12.5+dfsg-8
pn  libqt5designer5   
ii  libqt5gui55.12.5+dfsg-8
pn  libqt5multimedia5 
pn  libqt5multimediawidgets5  
ii  libqt5network55.12.5+dfsg-8
pn  libqt5printsupport5   
pn  libqt5sql5
ii  libqt5svg55.12.5-2
ii  libqt5widgets55.12.5+dfsg-8
pn  libqt5xml5
pn  libqt5xmlpatterns5
ii  libruby2.52.5.7-1+b1
ii  libstdc++610-20200211-1
ii  python3   3.7.5-3
ii  zlib1g1:1.2.11.dfsg-1.2

Bug#951565: freerdp2-x11: does not work at all, immediately exits, against xrdp server (rdesktop works)

[Mike Gabriel]

Control: severity -1 important

Hi Thorsten,

On  Di 18 Feb 2020 07:18:23 CET, Thorsten Glaser wrote:


Package: freerdp2-x11
Version: 2.0.0~git20190204.1.2693389a+dfsg1-2
Severity: grave
Justification: renders package unusable

tglase@tglase-nb:~ $ xfreerdp /v:tglase-edge
[07:15:07:750] [29233:29234]  
[INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[07:15:07:751] [29233:29234] [INFO][com.freerdp.client.x11] - No  
user name set. - Using login name: tglase
[07:15:08:615] [29233:29234] [INFO][com.freerdp.gdi] - Local  
framebuffer format  PIXEL_FORMAT_BGRX32
[07:15:08:615] [29233:29234] [INFO][com.freerdp.gdi] - Remote  
framebuffer format PIXEL_FORMAT_RGB16
[07:15:08:628] [29233:29234] [INFO][com.winpr.clipboard] -  
initialized POSIX local file subsystem
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.update] -  
[0x03] Cache Glyph - SERVER BUG: The support for this feature was  
not announced! Use /relax-order-checks to ignore
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.update] -  
order flags 03 failed
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.fastpath] -  
Fastpath update Orders [0] failed, status 0
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.fastpath] -  
fastpath_recv_update() - -1
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.fastpath] -  
fastpath_recv_update_data() fail
[07:15:08:744] [29233:29234] [ERROR][com.freerdp.core.transport] -  
transport_check_fds: transport->ReceiveCallback() - -3
[07:15:08:745] [29233:29234] [ERROR][com.freerdp.core] -  
freerdp_check_fds() failed - 0
[07:15:08:745] [29233:29234] [INFO][com.freerdp.client.common] -  
Network disconnect!
[07:15:08:745] [29233:29234] [ERROR][com.freerdp.client.x11] -  
Failed to check FreeRDP file descriptor

131|tglase@tglase-nb:~ $ rdesktop -g 1000x768 tglase-edge
Connection established using plain RDP.
[…]

xfreerdp just exits with errorlevel 131 (could be signal 3),
whereas rdesktop works (shows the remote login screen).
xfreerdp, just before exiting, paints a window, but I cannot
see if anything is in it because it goes away too quickly.

I also tried xfreerdp /size:1000x768 /v:tglase-edge but that
does not change anything.


While being keen on seeing the above issue fixed very soon, I think it  
does not justify a severity:grave (unless you also observe freerdp2  
failing against MS Windows's RDP server).


Please let me know which xRDP version you tested against.

I will get in touch with upstream and see what can be done about this.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpTKZ9qYMrbC.pgp
Description: Digitale PGP-Signatur

Bug#951727: qmelt: command not found

[Jonas Smedegaard]

Quoting Celelibi (2020-02-20 21:42:02)
> The error message is pretty simple (and is mostly the subject of this 
> bug report).
> 
> When I try to export a video, the export job fails immediately and its 
> log (accessible via right-click on the job) says verbatim:
> 
> /usr/bin/nice: '/usr/bin/qmelt': No such file or directory
> Failed with exit code 127

Thanks for the clarification.


> However, I think I found a workaround.
> As I understand, qmelt is supposed to be provided by mltframework. It
> looks like it's actually part of the melt package, with the name 'melt',
> instead of 'qmelt'.
> 
> Therefore, an easy workaround that works for me is to install melt and
> make a symlink from qmelt to melt.
> 
> I'm not sure whether the package melt is actually supposed to provide a
> binary named qmelt. Anyway I guess a fix could be to add a dependency to
> melt and add a postinst script that runs:
> ln -s /usr/bin/melt /usr/bin/qmelt

If indeed qmelt and melt is the same (I suspect it isn't, given the 
comment by author of melt to the upstream bugreport you referenced 
earlier - but I'll leave it to the package maintainer to examine closer) 
then I guess a better approach would be to patch the code tp call melt 
instead of qmelt.


 - 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

Processed: Re: Bug#951565: freerdp2-x11: does not work at all, immediately exits, against xrdp server (rdesktop works)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #951565 [freerdp2-x11] freerdp2-x11: does not work at all, immediately 
exits, against xrdp server (rdesktop works)
Severity set to 'important' from 'grave'

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

Bug#950736: closing 950736

[Salvatore Bonaccorso]

close 950736 1.7.0+dfsg1-1
thanks

Closing manually, as the 1.7.0+dfsg1-1 upload did not contain the bug closers.

Processed: closing 950736

[Debian Bug Tracking System]

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

> close 950736 1.7.0+dfsg1-1
Bug #950736 [src:consul] consul: CVE-2020-7219 CVE-2020-7955
The source 'consul' and version '1.7.0+dfsg1-1' do not appear to match any 
binary packages
Marked as fixed in versions consul/1.7.0+dfsg1-1.
Bug #950736 [src:consul] consul: CVE-2020-7219 CVE-2020-7955
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#951703: marked as done (swig: does not install /usr/bin/swig anymore)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 20:47:19 +
with message-id 
and subject line Bug#951703: fixed in swig 4.0.1-2.1
has caused the Debian Bug report #951703,
regarding swig: does not install /usr/bin/swig anymore
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.)


-- 
951703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swig
Version: 4.0.1-2
Severity: serious
Affects: astrometry.net
Tags: +patch

The "swig" binary package does not install a symlink /usr/bin/swig -->
swig4.0 anymore. Since this breaks the build of a number of packages, I
set the severity to "serious".

Typical error message:

swig -python -I../include -I../include/astrometry -I/usr/include/wcslib
-I../include -I../include/astrometry -I/usr/include/wcslib -o
util_wrap.c util.i
error: command 'swig' failed with exit status 1

>From the source (on salsa), I guess this was just forgotten to adjust.

See

https://salsa.debian.org/debian/swig/merge_requests/1

for the trivial fix.

Best

Ole
--- End Message ---
--- Begin Message ---
Source: swig
Source-Version: 4.0.1-2.1
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
swig, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated swig 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: Thu, 20 Feb 2020 14:46:05 -0500
Source: swig
Architecture: source
Version: 4.0.1-2.1
Distribution: unstable
Urgency: high
Maintainer: Torsten Landschoff 
Changed-By: Boyuan Yang 
Closes: 951703
Changes:
 swig (4.0.1-2.1) unstable; urgency=high
 .
   * Non-maintainer upload.
 .
   [ Boyuan Yang ]
   * debian/: Replace all occurrences of swig3.0 with swig4.0.
 .
   [ Ole Streicher ]
   * debian/swig.links: Update swig.links for version 4.0.
 (Closes: #951703)
Checksums-Sha1:
 3cfc97732082dd986a0e1e69a67cf44e201e1034 2159 swig_4.0.1-2.1.dsc
 832d339ede7f0c0d7edcf738e658c02d49667e05 19628 swig_4.0.1-2.1.debian.tar.xz
 b646a2eadf58d22f37743488804a4f405ea9feeb 7445 swig_4.0.1-2.1_amd64.buildinfo
Checksums-Sha256:
 c35bb0cccdf7461ad3e6cb861212288fd49a2104ce95691a6475812103360338 2159 
swig_4.0.1-2.1.dsc
 455924a69073442ae48516e125569c2cd6bef72461b6c95d1adc8bd9d64a5abd 19628 
swig_4.0.1-2.1.debian.tar.xz
 65d5def527be9d8f65079cd1a0e12c3000978bdb6b266f9282f513e81d2bb52d 7445 
swig_4.0.1-2.1_amd64.buildinfo
Files:
 bc6eb4af7e7a1d89867cae858860acfb 2159 interpreters optional swig_4.0.1-2.1.dsc
 8f1433e9d86287b20ee557ff43ca20f6 19628 interpreters optional 
swig_4.0.1-2.1.debian.tar.xz
 fd1a0dafddfd2f59ac8a25c7bde0c640 7445 interpreters optional 
swig_4.0.1-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl5O5CQACgkQwpPntGGC
Ws6awxAAl7s4dxIrG1EW9mbW6aoq4LivUIgYJlTbemEKOYLTfXNAg3DPs5onlK5E
SZ4xPOf3jf3ek6FfZHL5nsg26YMfL6Dg3BORjogpzx2BGNsz4kW7v55+uG5O9M8c
DBzsMsrL08dfD5FSBQSf2MUxYQbfs+sQbiFN7d2DM8WtndSZMHu7iQ2+VSkhTe4Q
iDgy0YCwniK8obWMYSwwB9VehaokORnu5QZTXcKsnjGBGMvNoKAeKpuJFCZUnsC2
PDI5Y+edo6z3iNerZVu/34iQchKjex0DYyOEjG8Qyq5O/3BQEeI7N7EURl95yxoU
dcbTkvW9bNUbTfpvlz0uDvg23jzRBVUC++KAZAymaaW2XO5/EE2sJC9621OVWhOw
RnlLL75ojNHugohVcBtVVZJgCd5lu6rrBiig2QZ5vss8Vx7mFkCyo0W3RY2mTUrP
1Q11UkYwjKcqNFXszXDJp3mKDuat0eub58wE1tE276IPfSTzSjulLEW08EjQubIU
YkG6nPq6PdHBHF/D/aCCaY/p63hcxQvzxQhgkihBq3H6adTbeRxpNNnPhuanoGIg
owG6Tdi7RgaQHooAMysorEEBVKlWt5TFDKVGatCYb2buH0G9vGzUpNwX2BDrdiFp
PcjktyOBWUkL1Ty4qQrmS+gTg1JCaPiGLiHwilD14uxxQDYe7oc=
=9sYX
-END PGP SIGNATURE End Message ---

Bug#951730: OpenSSL linking without license exception

[Bastian Germann]

Package: argyll
Severity: serious

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. I can build
fine without libssl, so please remove this dependency.

Bug#951727: qmelt: command not found

[Celelibi]

Package: shotcut
Version: 20.02.17-1
Followup-For: Bug #951727

The error message is pretty simple (and is mostly the subject of this
bug report).

When I try to export a video, the export job fails immediately and its log
(accessible via right-click on the job) says verbatim:

/usr/bin/nice: '/usr/bin/qmelt': No such file or directory
Failed with exit code 127


However, I think I found a workaround.
As I understand, qmelt is supposed to be provided by mltframework. It
looks like it's actually part of the melt package, with the name 'melt',
instead of 'qmelt'.

Therefore, an easy workaround that works for me is to install melt and
make a symlink from qmelt to melt.

I'm not sure whether the package melt is actually supposed to provide a
binary named qmelt. Anyway I guess a fix could be to add a dependency to
melt and add a postinst script that runs:
ln -s /usr/bin/melt /usr/bin/qmelt

Best regards,
Celelibi

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages shotcut depends on:
ii  libc6  2.29-10
ii  libgcc-s1  10-20200211-1
ii  libjs-three111+dfsg1-1
ii  libmlt++3  6.20.0-1
ii  libmlt66.20.0-1
ii  libqt5core5a   5.12.5+dfsg-8
ii  libqt5gui5 5.12.5+dfsg-8
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5network5 5.12.5+dfsg-8
ii  libqt5opengl5  5.12.5+dfsg-8
ii  libqt5qml5 5.12.5-5
ii  libqt5quick5   5.12.5-5
ii  libqt5quickwidgets55.12.5-5
ii  libqt5sql5 5.12.5+dfsg-8
ii  libqt5webkit5  5.212.0~alpha3-6
ii  libqt5websockets5  5.12.5-2+b1
ii  libqt5widgets5 5.12.5+dfsg-8
ii  libqt5xml5 5.12.5+dfsg-8
ii  libstdc++6 10-20200211-1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2   5.12.5-5
ii  qml-module-qtquick-controls5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs 5.12.5-1+b1
ii  qml-module-qtquick-extras  5.12.5-1+b1
ii  qml-module-qtquick-layouts 5.12.5-5
ii  qml-module-qtquick-window2 5.12.5-5
ii  qml-module-qtquick25.12.5-5

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information

Bug#950063: influxdb-python FTBFS with pandas 0.25.3

[Andreas Tille]

On Thu, Feb 20, 2020 at 10:31:41AM -0500, Alexandre Viau wrote:
> On Thu, Feb 20, 2020 at 4:15 AM Andreas Tille  wrote:
> > Regarding your wish to remove you from Maintainers: I did not intend to
> > take over the package from you personally.  I rather wanted to do
> > something like:
> >
> >   Maintainer: Debian Python Modules Team 
> > 
> >   Uploaders: Alexandre Viau 
> >
> > and you become a member of DPMT to maintain the package inside the team.
> > If you are short in time I could probably do a team upload to fix the
> > current issues, thought.
> 
> Okay that works.

Since I do not have sufficient permissions I asked for it in

   https://salsa.debian.org/salsa/support/issues/197

I'll keep you updated who the migration proceeds.

Kind regards

  Andreas.

> You may do the upload right now and I'll make sure that I am a member
> on salsa DPMT (I used to be on Alioth) before my next upload.
> 
> Thank you for caring about this package!
> 
> Cheers,
> 
> --
> Alexandre Viau
> av...@debian.org
> 

-- 
http://fam-tille.de

Bug#951703: swig: diff for NMU version 4.0.1-2.1

[Boyuan Yang]

Control: tags 951703 + patch
Control: tags 951703 + pending

Dear maintainer,

I've prepared an NMU for swig (versioned as 4.0.1-2.1) and
uploaded it to DELAYED/0 since you are listed in the lowNMU
list.

Regards,
Boyuan Yang

diff -Nru swig-4.0.1/debian/changelog swig-4.0.1/debian/changelog
--- swig-4.0.1/debian/changelog 2020-02-19 15:13:39.0 -0500
+++ swig-4.0.1/debian/changelog 2020-02-20 14:46:05.0 -0500
@@ -1,3 +1,16 @@
+swig (4.0.1-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+
+  [ Boyuan Yang ]
+  * debian/: Replace all occurrences of swig3.0 with swig4.0.
+
+  [ Ole Streicher ]
+  * debian/swig.links: Update swig.links for version 4.0.
+(Closes: #951703)
+
+ -- Boyuan Yang   Thu, 20 Feb 2020 14:46:05 -0500
+
 swig (4.0.1-2) unstable; urgency=low
 
   * debian/control: Update Standards-Version to 4.5.0 (no changes).
diff -Nru swig-4.0.1/debian/patches/ccache-rename.diff swig-
4.0.1/debian/patches/ccache-rename.diff
--- swig-4.0.1/debian/patches/ccache-rename.diff2020-01-16
17:50:05.0 -0500
+++ swig-4.0.1/debian/patches/ccache-rename.diff2020-02-20
14:43:25.0 -0500
@@ -1,6 +1,6 @@
 Description: Work around renaming of ccache-swig binary
  The package suffixes binaries with the major version, which changes
- ccache-swig to ccache-swig3.0. However, ccache is sensitive to the
+ ccache-swig to ccache-swig4.0. However, ccache is sensitive to the
  name of its binary. The test did not take the program-suffix configure
  option into account.
  .
diff -Nru swig-4.0.1/debian/swig4.0.dirs swig-4.0.1/debian/swig4.0.dirs
--- swig-4.0.1/debian/swig4.0.dirs  2020-01-16 17:30:31.0 -0500
+++ swig-4.0.1/debian/swig4.0.dirs  2020-02-20 14:43:43.0 -0500
@@ -1,4 +1,4 @@
 usr/bin
 usr/share/man/man1
-usr/share/swig3.0
+usr/share/swig4.0
 usr/share/doc
diff -Nru swig-4.0.1/debian/swig4.0-examples.links swig-4.0.1/debian/swig4.0-
examples.links
--- swig-4.0.1/debian/swig4.0-examples.links2020-01-16 17:30:31.0
-0500
+++ swig-4.0.1/debian/swig4.0-examples.links2020-02-20 14:44:22.0
-0500
@@ -1 +1 @@
-usr/share/doc/swig3.0-examples usr/share/doc/swig3.0/examples
+usr/share/doc/swig4.0-examples usr/share/doc/swig4.0/examples
diff -Nru swig-4.0.1/debian/swig4.0-examples.override swig-
4.0.1/debian/swig4.0-examples.override
--- swig-4.0.1/debian/swig4.0-examples.override 2020-01-18 17:32:43.0
-0500
+++ swig-4.0.1/debian/swig4.0-examples.override 2020-02-20 14:43:58.0
-0500
@@ -1 +1 @@
-swig3.0-examples: extra-license-file usr/share/doc/swig3.0-
examples/GIFPlot/LICENSE
+swig4.0-examples: extra-license-file usr/share/doc/swig4.0-
examples/GIFPlot/LICENSE
diff -Nru swig-4.0.1/debian/swig.links swig-4.0.1/debian/swig.links
--- swig-4.0.1/debian/swig.links2020-01-16 17:30:31.0 -0500
+++ swig-4.0.1/debian/swig.links2020-02-20 14:42:11.0 -0500
@@ -1,2 +1,2 @@
-usr/bin/swig3.0usr/bin/swig
-usr/bin/ccache-swig3.0 usr/bin/ccache-swig
+usr/bin/swig4.0usr/bin/swig
+usr/bin/ccache-swig4.0 usr/bin/ccache-swig
diff -Nru swig-4.0.1/debian/tests/control swig-4.0.1/debian/tests/control
--- swig-4.0.1/debian/tests/control 2020-01-16 17:30:31.0 -0500
+++ swig-4.0.1/debian/tests/control 2020-02-20 14:42:43.0 -0500
@@ -1,8 +1,8 @@
 Tests: flatnested-crash
-Depends: swig3.0
+Depends: swig4.0
 
-Test-Command: ccache-swig3.0 -V
-Depends: swig3.0
+Test-Command: ccache-swig4.0 -V
+Depends: swig4.0
 
 Test-Command: ccache-swig -V
 Depends: swig
diff -Nru swig-4.0.1/debian/tests/flatnested-crash swig-
4.0.1/debian/tests/flatnested-crash
--- swig-4.0.1/debian/tests/flatnested-crash2020-01-16 17:30:31.0
-0500
+++ swig-4.0.1/debian/tests/flatnested-crash2020-02-20 14:43:00.0
-0500
@@ -20,10 +20,10 @@
 %}
 EOF
 
-swig3.0 -version
-swig3.0 -c++ -python nested_scope.i
+swig4.0 -version
+swig4.0 -c++ -python nested_scope.i
 echo "Wrapping for Python: okay"
-swig3.0 -c++ -ruby nested_scope.i
+swig4.0 -c++ -ruby nested_scope.i
 echo "Wrapping for Ruby: okay"
-swig3.0 -c++ -tcl nested_scope.i
+swig4.0 -c++ -tcl nested_scope.i
 echo "Wrapping for Tcl: okay"

Processed: swig: diff for NMU version 4.0.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 951703 + patch
Bug #951703 [swig] swig: does not install /usr/bin/swig anymore
Added tag(s) patch.
> tags 951703 + pending
Bug #951703 [swig] swig: does not install /usr/bin/swig anymore
Added tag(s) pending.

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

Processed: timidity: upgrading broke sound via pulseaudio

[Debian Bug Tracking System]

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

> package timidity
Limiting to bugs with field 'package' containing at least one of 'timidity'
Limit currently set to 'package':'timidity'

> tags 901148 + patch
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #904652 [timidity] pulseaudio: looses device and replace it with dummy 
package so no sound possible
Bug #918522 [timidity] No sound with PulseAudio when an NVidia GPU is installed.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#951728: autofdo: FTBFS on armel, mipsel

[Ivo De Decker]

package: src:autofdo
version: 0.19-2
severity: serious
tags: ftbfs

Hi,

The latest upload of autofdo to unstable fails on armel, mipsel:

https://buildd.debian.org/status/package.php?p=autofdo

Cheers,

Ivo

Bug#951727: qmelt: command not found

[Jonas Smedegaard]

Hi Celelibi,

Quoting Celelibi (2020-02-20 20:00:20)
> shotcut uses the program qmelt to export the videos. However, unless 
> I'm mistaken, this program is nowhere to be found in debian.

You reference other bugreports about non-Debian packages.

Please describe the exact commands you use with official Debian 
packages, and quote the error messages you experience.

(also, please note that I am not the package maintainer)


 - 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#901148: timidity: upgrading broke sound via pulseaudio

[Joachim Wiedorn]

Now I have made new Debian packages for buster and testing
including my patch:

https://www.joonet.de/sources/timidity/

---
Have a nice day.
Joachim (Germany)


pgpdpALCRekgS.pgp
Description: Digitale Signatur von OpenPGP

Bug#951727: qmelt: command not found

[Celelibi]

Package: shotcut
Version: 20.02.17-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

shotcut uses the program qmelt to export the videos. However, unless I'm
mistaken, this program is nowhere to be found in debian.

This has already been asked on the forum of shotcut and been discarded
as a packaging issue.
https://forum.shotcut.org/t/shotcut-export-not-working-usr-bin-nice-usr-bin-qmelt-not-found/8043


I tagged this bug as grave since the inability to export a video would
make the whole package pretty useless for most people.

It looks like this bug was already reported back in 2016 for a
non-official debian version.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818114

If anyone has already managed to use this package, I wonder where does
their qmelt program come from.

Best regards,
Celelibi


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages shotcut depends on:
ii  libc6  2.29-10
ii  libgcc-s1  10-20200211-1
ii  libjs-three111+dfsg1-1
ii  libmlt++3  6.20.0-1
ii  libmlt66.20.0-1
ii  libqt5core5a   5.12.5+dfsg-8
ii  libqt5gui5 5.12.5+dfsg-8
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5network5 5.12.5+dfsg-8
ii  libqt5opengl5  5.12.5+dfsg-8
ii  libqt5qml5 5.12.5-5
ii  libqt5quick5   5.12.5-5
ii  libqt5quickwidgets55.12.5-5
ii  libqt5sql5 5.12.5+dfsg-8
ii  libqt5webkit5  5.212.0~alpha3-6
ii  libqt5websockets5  5.12.5-2+b1
ii  libqt5widgets5 5.12.5+dfsg-8
ii  libqt5xml5 5.12.5+dfsg-8
ii  libstdc++6 10-20200211-1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2   5.12.5-5
ii  qml-module-qtquick-controls5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs 5.12.5-1+b1
ii  qml-module-qtquick-extras  5.12.5-1+b1
ii  qml-module-qtquick-layouts 5.12.5-5
ii  qml-module-qtquick-window2 5.12.5-5
ii  qml-module-qtquick25.12.5-5

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information

Processed: tagging 694323

[Debian Bug Tracking System]

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

> tags 694323 + bullseye-ignore
Bug #694323 [lmodern] [gsfonts] Fonts include copyrighted adobe fragment all 
right reserved
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Processed: tagging 927255

[Debian Bug Tracking System]

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

> tags 927255 + bullseye-ignore
Bug #927255 [powerpc-utils] powerpc-utils is uninstallable
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Processed: tagging 717636

[Debian Bug Tracking System]

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

> tags 717636 + bullseye-ignore
Bug #717636 [texlive-lang-other] [latex-sanskrit] Package contain type1 
startlock fragment from black book
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Processed: tagging 694324

[Debian Bug Tracking System]

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

> tags 694324 + bullseye-ignore
Bug #694324 [tex-gyre] Fonts include copyrighted adobe fragment all right 
reserved
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Processed: tagging 807168

[Debian Bug Tracking System]

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

> tags 807168 + bullseye-ignore
Bug #807168 [src:debian-installer-netboot-images] 
debian-installer-netboot-images: required resources not declared as 
build-dependencies (fetches via network)
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Processed: tagging 614497

[Debian Bug Tracking System]

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

> tags 614497 + bullseye-ignore
Bug #614497 [doc-debian] doc-debian: The OPL-licensed documents taken from 
Debian website are non-free
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Bug#951643: marked as done (murasaki: FTBFS with new mpi)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 18:19:39 +
with message-id 
and subject line Bug#951643: fixed in murasaki 1.68.6-9
has caused the Debian Bug report #951643,
regarding murasaki: FTBFS with new mpi
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.)


-- 
951643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: murasaki
Version: 1.68.6-8
Severity: serious

murasaki_mpi.cc: In function ‘void mpi_types_init()’:
murasaki_mpi.cc:107:14: error: call to ‘MPI_Address’ declared with attribute 
error: MPI_Address was remov
ed in MPI-3.0.  Use MPI_Get_address instead.
  107 |   MPI_Address(,disp);
  |   ~~~^~~
murasaki_mpi.cc:108:14: error: call to ‘MPI_Address’ declared with attribute 
error: MPI_Address was remov
ed in MPI-3.0.  Use MPI_Get_address instead.
  108 |   MPI_Address(,disp+1);
  |   ~~~^~~
murasaki_mpi.cc:109:14: error: call to ‘MPI_Address’ declared with attribute 
error: MPI_Address was remov
ed in MPI-3.0.  Use MPI_Get_address instead.
  109 |   MPI_Address(,disp+1);
  |   ~~~^
murasaki_mpi.cc:112:18: error: call to ‘MPI_Type_struct’ declared with 
attribute error: MPI_Type_struct w
as removed in MPI-3.0.  Use MPI_Type_create_struct instead.
  112 |   MPI_Type_struct(3,blocklen,disp,type,_HashMessage_type);
  |   ~~~^~~~
make[3]: *** [Makefile:189: murasaki_mpi.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:8: all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" 
USE_MPI=YES returned exit code 2
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:19: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: murasaki
Source-Version: 1.68.6-9
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
murasaki, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated murasaki 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: Thu, 20 Feb 2020 21:11:15 +0530
Source: murasaki
Architecture: source
Version: 1.68.6-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 951643
Changes:
 murasaki (1.68.6-9) unstable; urgency=medium
 .
   * Team Upload.
 .
   [ Steffen Moeller ]
   * d/u/metadata: yamllint
 .
   [ Nilesh Patra ]
   * Fix syntax with new MPI version
 Closes: #951643
   * Drop compat, switch to debhelper-compat
   * Add "Rules-Requires-Root: no"
   * Switch to https
   * Fix License locations, switch to https
   * Update spellings patch
   * Bump standards version to 4.5.0
 .
   [ Andreas Tille ]
   * Remove trailing whitespace in debian/rules (routine-update)
Checksums-Sha1:
 70d5cd1a5345267ac8fb664d5b0192e4b114e5ba 2237 murasaki_1.68.6-9.dsc
 518b55db453f370dd40b21d541e56bd45a18edbf 10292 murasaki_1.68.6-9.debian.tar.xz
 10f44dfed9d24e5a25ba7b358b5b59e610ad1724 9226 murasaki_1.68.6-9_amd64.buildinfo
Checksums-Sha256:
 93fe170d5b0d8eb6ea1a06f809e400bf28ef28d6bc7db67a029c225cae5a5779 2237 
murasaki_1.68.6-9.dsc
 32d67fa34d50a25eaa517059985b2b1e891677d2e8ff8751224197a93212575b 10292 
murasaki_1.68.6-9.debian.tar.xz
 a02c714afad7ca0d76652fa33bec363ca8e0ea621a6c3d89f546906a3256c3ec 9226 
murasaki_1.68.6-9_amd64.buildinfo
Files:
 73f37f28827cda451fc331c34dff5024 2237 science optional murasaki_1.68.6-9.dsc
 8224e51ac9dafa3c4aa25f3b686247fe 10292 science optional 
murasaki_1.68.6-9.debian.tar.xz
 72d59565f1ecf642445563bb7e23d02e 9226 science optional 
murasaki_1.68.6-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5OyloOHHRpbGxlYUBy

Processed: [bts-link] source package src:cstore-fdw

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cstore-fdw
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #946256 (http://bugs.debian.org/946256)
> # Bug title: cstore-fdw needs porting to PostgreSQL 12
> #  * https://github.com/citusdata/cstore_fdw/issues/212
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 946256 + fixed-upstream
Bug #946256 [src:cstore-fdw] cstore-fdw needs porting to PostgreSQL 12
Added tag(s) fixed-upstream.
> usertags 946256 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 946256 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:golang-github-proglottis-gpgme

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:golang-github-proglottis-gpgme
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #951372 (http://bugs.debian.org/951372)
> # Bug title: golang-github-proglottis-gpgme: CVE-2020-8945
> #  * https://github.com/proglottis/gpgme/pull/23
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 951372 + fixed-upstream
Bug #951372 [src:golang-github-proglottis-gpgme] 
golang-github-proglottis-gpgme: CVE-2020-8945
Added tag(s) fixed-upstream.
> usertags 951372 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#950813: marked as done (volume-key FTBFS, missing build-dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 18:06:20 +
with message-id 
and subject line Bug#950813: fixed in volume-key 0.3.12-3
has caused the Debian Bug report #950813,
regarding volume-key FTBFS, missing build-dependency on dh-python
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.)


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

Source: volume-key
Version: 0.3.12-2
Tags: bullseye, sid, patch
Severity: serious

volume-key currently fails to build because of a missing build-dependency on 
dh-python, please add it.
--- End Message ---
--- Begin Message ---
Source: volume-key
Source-Version: 0.3.12-3
Done: Michael Biebl 

We believe that the bug you reported is fixed in the latest version of
volume-key, 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 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated volume-key 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: Thu, 20 Feb 2020 18:31:30 +0100
Source: volume-key
Architecture: source
Version: 0.3.12-3
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Closes: 950813
Changes:
 volume-key (0.3.12-3) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * Team upload.
   * Don't build for non-Linux since libcryptsetup-dev is Linux-only
 .
   [ Michael Biebl ]
   * Add explicit Build-Depends on dh-python (Closes: #950813)
   * Bump Standards-Version to 4.5.0
   * Bump debhelper compat level to 12
Checksums-Sha1:
 36c5defc31fa768b77067375bafaadce53fd6246 2286 volume-key_0.3.12-3.dsc
 601a6b1e4e8a40a6921c5ab69dba10176c56fec8 4972 volume-key_0.3.12-3.debian.tar.xz
 3bf8bb3bbc7f4eea37b19b1af328f64621839cd2 6910 
volume-key_0.3.12-3_source.buildinfo
Checksums-Sha256:
 dc971456b4f3b1015bef1977d601a13c590e380b54cc7105a8d58d4f75fdca22 2286 
volume-key_0.3.12-3.dsc
 918120ddb324cea144d58d7bcb0024428e46bfa978bb68805e652fe7895dc2d0 4972 
volume-key_0.3.12-3.debian.tar.xz
 b1f951467cec4adc4fcda6a51c43091913ce74f67134b14ad52a0dd01debdc98 6910 
volume-key_0.3.12-3_source.buildinfo
Files:
 35e218e91a3ba83d2bac18415c85d56a 2286 utils optional volume-key_0.3.12-3.dsc
 5f9a0fca21d306b291b80b10323d2e12 4972 utils optional 
volume-key_0.3.12-3.debian.tar.xz
 006392e18677d89734ecb305f072aff7 6910 utils optional 
volume-key_0.3.12-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl5OxvgACgkQauHfDWCP
ItxN6A/8D2d9ngOlNae1bnr3B+AmzUuPhCc8j/Y6KlMW7kLf2FVfYfAzqQYRWdlr
QlOq3MmuyAEVCpvbtFeih3vMqFvugFUXVdR4ECztgUHuzppUkEvKNTSxCw/fPS2E
WOR1mL1s4wMH8nUj6L0zEU6dIdothUD4pYG40dO77/w1pPjhkcx/oDfG+dLmjuId
18FDh9BHUrWiGI5iwLBPLs9lxYr/HC2LteD14utMzyLpZ1VPAS94un2U4f1DYzN4
Oizkm6M2UnrijvWqAnZppNBYnW9zZooA2EEwb9uxNmmvG+2/5sAZvPuyOFeASdzb
YLJvVqXHEErAalWklP+LCvCrIULRvCKKH5D5akUopT9i8KX7ZZ6ZtYn3XKEBr4jI
XaefgqTYM1qRHQBNGA8frUh2JUMBHyQ8xK/LHGSG8UsTaitHSv7q4kQUHW15/bCO
4Dcl0fQ+Xg2Zqf7CRoZrriVAh88pyWdfnrTqiSuspWqLUE9zpmJm48v+iykJevSj
INho88BQWCNHCBFZT2JVgm1shIBzGLJP2vTl+XZkxoyW0nQfV9Tk92GlnjaMSWZ+
Z1Rmj5fBKzBaAkKOAeu3q/Mdftr1t52AMfZ7LfkZSopljrbRApjpA7nw0tzfzMeX
mnZYTj2ApGhp4/PBG+3oi7cNUtlbqnS0WpLfMu3eU4f8Huyaa4s=
=hacD
-END PGP SIGNATURE End Message ---

Processed: fixed 938130 in 3.5.34-1

[Debian Bug Tracking System]

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

> # close message has typo in bug number
> fixed 938130 3.5.34-1
Bug #938130 {Done: Sandro Tosi } [src:python-reportlab] 
python-reportlab: Python2 removal in sid/bullseye
Marked as fixed in versions python-reportlab/3.5.34-1.
> thanks
Stopping processing here.

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

Processed: update info for #949705

[Debian Bug Tracking System]

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

> reopen 949705
Bug #949705 {Done: Debian FTP Masters } 
[src:libidn2] libidn2: binary-arch target depends on makeinfo (but texinfo is 
in Build-Depends-Indep)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libidn2/2.0.5-1+deb10u1.
> fixed 949705 libidn2/2.0.5-1+deb10u1
Bug #949705 [src:libidn2] libidn2: binary-arch target depends on makeinfo (but 
texinfo is in Build-Depends-Indep)
Marked as fixed in versions libidn2/2.0.5-1+deb10u1.
> # fix is moving texinfo from Build-Depends-Indep to Build-Depends
> tags 949705 patch
Bug #949705 [src:libidn2] libidn2: binary-arch target depends on makeinfo (but 
texinfo is in Build-Depends-Indep)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#951725: scikit-learn: FTBFS on arm64, armhf, ppc64el: test failures

[Ivo De Decker]

package: src:scikit-learn
version: 0.22.1+dfsg-2
severity: serious
tags: ftbfs

Hi,

The latest upload of scikit-learn to unstable fails on arm64, armhf, ppc64el:

https://buildd.debian.org/status/package.php?p=scikit-learn

Cheers,

Ivo

Processed: severity of 937277 is serious

[Debian Bug Tracking System]

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

> # version in testing still depends on removed package
> severity 937277 serious
Bug #937277 {Done: Emmanuel Bouthenot } [src:pg-activity] 
pg-activity: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#951723: pymongo: FTBFS: test failures on 32 bit architectures

[Ivo De Decker]

package: src:pymongo
version: 3.10.0-1
severity: serious
tags: ftbfs

Hi,

The latest upload of pymongo to unstable fails on armel, armhf, i386, mipsel:

"OverflowError: timestamp out of range for platform time_t"

https://buildd.debian.org/status/package.php?p=pymongo

Cheers,

Ivo

Processed: fixed 934840 in 1.180

[Debian Bug Tracking System]

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

> fixed 934840 1.180
Bug #934840 [src:gcc-defaults] gcc-defaults: Build takes forever in stretch
Marked as fixed in versions gcc-defaults/1.180.
> thanks
Stopping processing here.

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

Bug#951722: autopkgtest suite flaky on arm64

[Michael Biebl]

Source: dovecot
Version: 1:2.3.7.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Hi,

the autopkgtest suite appears to be flaky on arm64. Sometimes it
succeeds, sometimes command1 fails [1].

This is problematic, as this (randomly) blocks other packages from
entering testing, a recent example is systemd which is currently blocked
because of

  autopkgtest for dovecot/1:2.3.7.2-1: amd64: Pass, arm64: Regression

I asked on #debci, and they recommended to file this as RC bug.
If you think this is an issue of the debci arm64 infrastructure, please
get in touch with debian...@lists.debian.org.

Regards,
Michael

[1] 
https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dovecot/4294703/log.gz

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#951721: autopkgtest suite flaky on arm64: command10 randomly fails

[Michael Biebl]

Source: suricata
Version: 1:4.1.5-2
Severity: serious
User: debian...@lists.debian.org

Hi,

the autopkgtest suite appears to be flaky on arm64. Sometimes it
succeeds, sometimes command10 fails.

This is problematic, as this (randomly) blocks other packages from
entering testing, a recent example is systemd which is currently blocked
because of

  autopkgtest for suricata/1:4.1.5-2: amd64: Pass, arm64: Regression

I asked on #debci, and they recommended to file this as RC bug.
If you think this is an issue of the debci arm64 infrastructure, please
get in touch with debian...@lists.debian.org.

Regards,
Michael

Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?

[Olek Wojnar]

Hi Steve,

On Thu, Feb 13, 2020, 14:42 Steve Cotton  wrote:

> Hi all in the Games Team,
>
> One of the Debian games affected by the python3 transition is 2
> Lightyears
> Into Space, source package name "lightyears". I've ported it to
> python3-pygame,
> and opened an upstream issue for merging it (sadly this doesn't have an
> upstream response yet).
>
> The Debian package isn't currently maintained by the Games Team, but one
> of the
> serious bugs is "Maintainer email address not working". I'm wondering if
> the
> Games Team would adopt it and apply my python3 port?
>

That's a great game, I've played it quite a few times over the years. I'll
be happy to sponsor the upload under the Games Team umbrella.

However, have you tried contacting the maintainer and the uploader team to
make sure they're ok with transferring the package to the Games Team? I
think it makes sense for us to have it but we need to check with them
first. If you have already obtained that permission, please forward the
email to these lists so that we have it for reference.

Debian bugs:
>   #942622 src:lightyears: Maintainer email address not working
>   #912488 lightyears: Please migrate to python3-pygame
>   #936945 lightyears: Python2 removal in sid/bullseye
>
> Upstream pull request:
>   https://github.com/20kly/20kly/issues/2
>   https://github.com/stevecotton/20kly/tree/version1.4/python3
>
> The Debian package's "copyright" file cleans up some of the oddities of the
> upstream README.md's licensing section, I'm sure it's distributable but
> expect
> it to get some questions if it went through the NEW queue. Oddities such as
> attributing an image as "copyright NASA" instead of saying that it's one of
> NASA's public domain images. I'm happy to put some effort in to fixing
> that.
>

Please do (pending approval to move the package)! Let me know what you need
from me (off-lists is fine for coordinating details).

-Olek

>

Bug#948914: marked as done (qmath3d: FTBFS: The qmake executable '/usr/bin/qmake' failed with exit code 1.)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 16:37:48 +
with message-id 
and subject line Bug#948914: fixed in qmath3d 0~1.0-3
has caused the Debian Bug report #948914,
regarding qmath3d: FTBFS: The qmake executable '/usr/bin/qmake' failed with 
exit code 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.)


-- 
948914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmath3d
Version: 0~1.0-2)
Severity: serious
Justification: FTBFS on all archs

Hi Wookey! During a rebuild of your package it FTBFS:



The error seems to be:

WARNING: Error setting up Qt for '/usr/bin/qmake': The qmake executable 
'/usr/bin/qmake' failed with exit code 1.

And looking at the package's source code you are not exporting QT_SELECT 
widely, just during configure time.

Let me suggest you to simply export QT_SELECT as described in



Thanks for your work!

Lisandro.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: qmath3d
Source-Version: 0~1.0-3
Done: Wookey 

We believe that the bug you reported is fixed in the latest version of
qmath3d, 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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wookey  (supplier of updated qmath3d 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, 19 Feb 2020 04:07:06 +
Source: qmath3d
Architecture: source
Version: 0~1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Closes: 928245 948914
Changes:
 qmath3d (0~1.0-3) unstable; urgency=medium
 .
   * Ensure Qt5 is used throughout build (Closes: #948914)
   * Remove /tmp vulnerability (Closes: #928245)
Checksums-Sha1:
 9848ba23d9a1fa6e613b70281261a792f4c81086 1783 qmath3d_0~1.0-3.dsc
 9adfd795948768ae678789064d219029d1c8e9cc 3784 qmath3d_0~1.0-3.debian.tar.xz
 2afdc1b00ba17d00f1a092953b0ef6fcb4aee113 9960 qmath3d_0~1.0-3_amd64.buildinfo
Checksums-Sha256:
 c4be1dd742421c6e13f102b3c0cd4c7b2c8428ba74cdaa326beda918209048d3 1783 
qmath3d_0~1.0-3.dsc
 30415458f63701d91b7b11cb4a804297c8a9a292fd6a1f502832964b7ee6e9bf 3784 
qmath3d_0~1.0-3.debian.tar.xz
 3bf11e06d8d9393466cb236ccb6ae9b16d335b6412d61d00ad8afed10e0f7d4d 9960 
qmath3d_0~1.0-3_amd64.buildinfo
Files:
 498d3b3c59cb7d37166df6c2cafec9e4 1783 libs optional qmath3d_0~1.0-3.dsc
 84ac261122af357e4721ca254976fb47 3784 libs optional 
qmath3d_0~1.0-3.debian.tar.xz
 074ce5cae7204ab69b9ca92cc03bfa8b 9960 libs optional 
qmath3d_0~1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAl5OsXsACgkQ+4YyUahv
nkcGIBAApaXI7oHiw3Fq7OjL3H5+MoohlL5FCUOHNdw89szyngsdjuqHp3Ba0hl+
oG26NUPZcaB9O7azjucMlBDcRVNpl49bBlLJc5RpakNtJuM6kwaw7csjMNiP+gHL
BTEqStaPo/cu49AGH2LLGWvmXRCX7fRHv0m9y+2HAV0CppXUOFC7itvQn8ysWkaT
rIHvF/FHq0Zkb9QJ8ELCC8FygSFO8Ht0lebfsgi6tvgap8l9U0rEHrPCuQGrvOe0
g5nhcpFdtbvtfpxO2nKkCM67TIlEqf2AKVX4/YondwfdBOITxgDLKc/8yMiy272A
LsEmEPlvJEfOq8G+gXLj5V4BHe7Hcu4ZoiSAVJNuEh+9roT7QF7dLKJ5thboX3Sb
cZQczV3pY6HCH5Z+57PcztIKS/NKgV3jZzTd/Nn12i/UcI/q4VLYEgZe2c0FEyIM
cGgWaY1kZgvg73lVH5w7mbvaJxJvz7KSfL2u7wUQEwU7tvfAJ9YM3bW9WU/W1tWJ
mFV+01SqS1nKOZ+h9Mz+4T2JorFLqaFTXPOCra0XZRBjZGDL/H/pkDy/puGHNLkw
Yxr36aT9pptBTZvJ1HmLz+U0H5V0rEIcGteaJ79cvQJ2BOFRjgiPmOtiHQqAAg+8
Z1V8N9z+nitXjYxL0xEBptdU2iY/AvYvSJBmmoGfJ9BwwUiGFwc=
=x3Ru
-END PGP SIGNATURE End 

Bug#951703: swig: does not install /usr/bin/swig anymore

[Boyuan Yang]

Control: affects -1 + mypaint

On Thu, 20 Feb 2020 11:39:07 +0100 Ole Streicher  wrote:
> Package: swig
> Version: 4.0.1-2
> Severity: serious
> Affects: astrometry.net
> Tags: +patch
> 
> The "swig" binary package does not install a symlink /usr/bin/swig -->
> swig4.0 anymore. Since this breaks the build of a number of packages, I
> set the severity to "serious".

Looks like it's indeed the case and it is breaking everything that build-
depends on swig. Please consider uploading the trivial fix with a source-only
upload.

-- 
Thanks,
Boyuan Yang


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

Processed: Re: swig: does not install /usr/bin/swig anymore

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + mypaint
Bug #951703 [swig] swig: does not install /usr/bin/swig anymore
Added indication that 951703 affects mypaint

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

Bug#951488: rspamd/buster causes extensive load on upstream servers, will be disabled

[Lee Garrett]

Package: rspamd
Followup-For: Bug #951488

Hi,

after debugging the issue further with the upstream author we came to the
conclusion that the packages in Debian are not reponsible for the issue.
Apparently even older versions shipped by Synology appliances are causing the
issue due to a broken backpressue algorithm.

Source:
https://twitter.com/rspamd/status/1229774962296225799
https://www.reddit.com/r/synology/comments/f5jczp/mailplus_server_and_rspamdcom/fi0g29t/

As such, I'm closing this bug.

Regards,
Lee

Processed: closing 951488

[Debian Bug Tracking System]

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

> close 951488
Bug #951488 [rspamd] rspamd/buster causes extensive load on upstream servers, 
will be disabled
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#951717: broccoli-ruby: suppor for multiple Ruby versions is broken

[Antonio Terceiro]

Source: broccoli-ruby
Version: 1.62-1
Severity: serious
Justification: broken, deprecated upstream, blocks Ruby transition
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition

After rebuilding broccoli-ruby with ruby2.7 support added, the shared
libraries are not linked correctly. For example, this is after building
from source, and extracting the resulting binary into
/tmp/ruby-broccoli:

$ find /tmp/ruby-broccoli/usr/ -name \*.so -print -exec 'ldd' '{}' ';' | grep 
ruby
/tmp/ruby-broccoli/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0/broccoli_ext.so
libruby-2.5.so.2.5 => /lib/x86_64-linux-gnu/libruby-2.5.so.2.5 
(0x7f92d9dea000)
/tmp/ruby-broccoli/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0/broccoli_ext.so
libruby-2.5.so.2.5 => /lib/x86_64-linux-gnu/libruby-2.5.so.2.5 
(0x7fafc0e04000)

note that both libraries are linked against ruby2.5 (which is currently
the default).

OTOH, at https://github.com/zeek/broccoli-ruby upstream says this is
"DEPRECATED", so maybe it shoud be removed from Debian? For as long as I
can remember, this package has caused problems on new Ruby versions.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


signature.asc
Description: PGP signature

Bug#950063: influxdb-python FTBFS with pandas 0.25.3

[Alexandre Viau]

On Thu, Feb 20, 2020 at 4:15 AM Andreas Tille  wrote:
> Regarding your wish to remove you from Maintainers: I did not intend to
> take over the package from you personally.  I rather wanted to do
> something like:
>
>   Maintainer: Debian Python Modules Team 
> 
>   Uploaders: Alexandre Viau 
>
> and you become a member of DPMT to maintain the package inside the team.
> If you are short in time I could probably do a team upload to fix the
> current issues, thought.

Okay that works.

You may do the upload right now and I'll make sure that I am a member
on salsa DPMT (I used to be on Alioth) before my next upload.

Thank you for caring about this package!

Cheers,

--
Alexandre Viau
av...@debian.org

Bug#951712: pyppl hard-codes python 3.7 for the build, ftbfs with 3.8

[Matthias Klose]

Package: src:pplpy
Version: 0.8.4-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

pyppl hard-codes python 3.7 for the build, ftbfs with 3.8, and doesn't have a
specific build dependency on 3.7.  Please make the build independent of the
python3 version.

Bug#946150: marked as done (please update build-deps on iptables)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 13:19:11 +
with message-id 
and subject line Bug#946150: fixed in keepalived 1:2.0.19-2
has caused the Debian Bug report #946150,
regarding please update build-deps on iptables
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.)


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

Hi there!

The src:iptables debian package (v1.8.4-1) dropped the libiptc-dev and libiptc0
binary packages. The content is included now in either libip4tc or libip6tc.
Such change comes from upstream. 

This package seems to `#include `, which is fine; But
I encourage to please update the build-deps to use libip4tc-dev instead of
libiptc-dev.

The header file is the same. Also pkg-config information should be right.

The build should be something like:

gcc $(pkg-config xtables --cflags) yourpackage.c -lip4tc or -lip6tc

instead of:

gcc yourpackage.c -liptc 

This may need reporting upstream. Let me know if you find any issue with this
change.
--- End Message ---
--- Begin Message ---
Source: keepalived
Source-Version: 1:2.0.19-2
Done: Alexander Wirt 

We believe that the bug you reported is fixed in the latest version of
keepalived, 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 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated keepalived 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: Thu, 20 Feb 2020 12:16:19 +0100
Source: keepalived
Binary: keepalived keepalived-dbgsym
Architecture: source amd64
Version: 1:2.0.19-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Description:
 keepalived - Failover and monitoring daemon for LVS clusters
Closes: 946150
Changes:
 keepalived (1:2.0.19-2) unstable; urgency=medium
 .
   [ Thomas Goirand ]
   * Drop build-depends on iptables-dev (Closes: #946150).
Checksums-Sha1:
 bc7d488040ce915478b6f5c620d66f9e9a9474e7 2077 keepalived_2.0.19-2.dsc
 7211df21d7e5e036db9cf775b9b27ea04ae6fbc8 10848 
keepalived_2.0.19-2.debian.tar.xz
 29be8e9b6d0c8c7e58e9a29b5662b2ffa32f652a 911740 
keepalived-dbgsym_2.0.19-2_amd64.deb
 b02706c1017f09a5448e989e6604272c28fc774a 7971 
keepalived_2.0.19-2_amd64.buildinfo
 2c0c560027863ab4fbf93a7a6c86069459f98e36 523896 keepalived_2.0.19-2_amd64.deb
Checksums-Sha256:
 0b3d2e593bb850dfc7e3376ad183bfc73a9c9bf9ece350a80acd7877e206ab1f 2077 
keepalived_2.0.19-2.dsc
 252903c6b5347ab26518fb84fb13e1fd61b2e17d60c1ee58021e30d919131f60 10848 
keepalived_2.0.19-2.debian.tar.xz
 4dc895b2ee4371c6d60708ba5884b385edd449e584728b75909742c037d1e793 911740 
keepalived-dbgsym_2.0.19-2_amd64.deb
 0a25484881b80a21ef88d79494026e8aceade71f6987ad3ff171f7c7c8a59498 7971 
keepalived_2.0.19-2_amd64.buildinfo
 62ce69107a38b458363ecafc4a59fd5263381f644637463da6d744224a95d55e 523896 
keepalived_2.0.19-2_amd64.deb
Files:
 c4a34e4ef4ef375b97d585a467e17b19 2077 admin optional keepalived_2.0.19-2.dsc
 d994e059a7d95ae9001770aa62445605 10848 admin optional 
keepalived_2.0.19-2.debian.tar.xz
 2444713205d43c0412c06a557b868069 911740 debug optional 
keepalived-dbgsym_2.0.19-2_amd64.deb
 4abb6e93582053e4a38cb54ddbcda2c0 7971 admin optional 
keepalived_2.0.19-2_amd64.buildinfo
 203fd31773dc8b6c3b0ca11fec3b4440 523896 admin optional 
keepalived_2.0.19-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbjlmweHRXblz0FtJHkX4yp3iOxYFAl5Og8oACgkQHkX4yp3i
OxYncxAAgbNoweZQc4Ml3blTNFTGEKUdiwg7d87OJEgFv7kldCbAos0kMF2lF8tn
pk9AbFDFc2Qw7hkgmYSgkFebRvVIHxooj3/lt+Qpsz1FO2EZjdSPg0AUnmgQvx/N
E7RmkPXsMNhqiGWh03DP89nE0vUDVfNmyfwXLGrThyS7Ien7IiDwZB7RhZjU0Qsr
qJl7u1meLTHPLp90dAnfRRkaVJa2qk9tVYWdqJYf/qr8NM8Do1P0syYE22Lk1uWf
CBTKsUbBVW4zvqVU/Sg3yii8kDRWTyjUn73yRV00vspa+r/DBh8I+ltt8IpL5x7s
Qrwhbnk5BVe4ZYkcBnfa/V1C/82caEJlW4cZrgXPp7vKu8CXz00N4BF/2P7MLZ/X
ZX0w6HL/1Z8fok4cBUPqKvEYMfXkgT8MvJAfQ+yezU7bPj2zYlqTE8zckNvdyV57
4XQhs1keKcM4w9g9zy/Xkw4YaIe5bkHAAplXPPPS47B4TA/RkM8zZLGD8Uzry4ob
mokqbmqUWoZLXxnRAGr+h+XPcBNBEJSZnRO3nRrXn8vytMY9aCXZMbZ75zMHt00C

Bug#951698: marked as done (linux kernel 5.x does not work with disk encryption 4.19 works)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 13:44:44 +0100
with message-id <20200220124443.55cyy3fuxar75...@shell.thinkmo.de>
and subject line Re: Bug#951698: linux kernel 5.x does not work with disk 
encryption 4.19 works
has caused the Debian Bug report #951698,
regarding linux kernel 5.x does not work with disk encryption 4.19 works
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.)


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

Package: linux-image-amd64
Version: 5.4.19-1, 5.5~rc5-1~exp1
Control: notfound -1 4.19.67-2+deb10u2
Severity: critical
justification: makes system unbootable

When trying to unlock an encrypted disk it fails with error (the 
encryption was setup by buster debian installer).

libgcc_s.so.1 must be installed for pthread_cancel to work.

libgcc_s.so.1 seems to be still present and latest version.

$ dpkg -S libgcc_s.so.1
libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
libgcc-9-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1
libgcc-8-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/8/libgcc_s.so.1
libgcc1: /lib/libgcc_s.so.1

This started happening after upgrading the system from buster to sid. 
With older kernel version from buster, the system still boots without 
any problem.


System Information
   Manufacturer: LENOVO
   Product Name: 20AMS16Q03
   Version: ThinkPad X240


--- End Message ---
--- Begin Message ---
On Thu, Feb 20, 2020 at 11:06:50AM +0100, Pirate Praveen wrote:
> Package: linux-image-amd64
> Version: 5.4.19-1, 5.5~rc5-1~exp1
> Control: notfound -1 4.19.67-2+deb10u2
> Severity: critical
> justification: makes system unbootable

No, it does not.  The kernel makes the system bootable, so it can't
break unrelated stuff.

> libgcc_s.so.1 must be installed for pthread_cancel to work.
> libgcc_s.so.1 seems to be still present and latest version.

See #950254.  Closing, as this is known.

Bastian

-- 
Deflector shields just came on, Captain.--- End Message ---

Bug#950073: marked as done (python-lti FTBFS; test failures)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 12:19:21 +
with message-id 
and subject line Bug#950073: fixed in python-lti 0.9.4-2
has caused the Debian Bug report #950073,
regarding python-lti FTBFS; test failures
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.)


-- 
950073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-lti
Version: 0.9.4-1
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-lti.html

...
=== FAILURES ===
_ TestToolConfig.test_allow_suboptions _

self = 

def test_allow_suboptions(self):

config = ToolConfig(title = "Test Config",
secure_launch_url = "https://www.example.com/lti;,
custom_params = {"custom1": "customval1"})
config.description ='Description of boringness'
config.launch_url = 'http://www.example.com/lti'
config.vendor_code = 'test'
config.vendor_name = 'test.tool'
config.vendor_description = 'We test things'
config.vendor_url = 'http://www.example.com/about'
config.vendor_contact_email = 'supp...@example.com'
config.vendor_contact_name = 'Joe Support'

config.set_custom_param('custom2', 'customval2')

config.set_ext_params('example.com', { 'extkey1': 'extval1' })
config.set_ext_param('example.com', 'extkey2', 'extval2')
config.set_ext_param('example.com', 'extopt1',
{ 'optkey1': 'optval1', 'optkey2': 'optval2' })
config.set_ext_param('example.com', 'extopt1',
{ 'labels':{
'en':'Image Library',
'es':'Biblioteca de Imagenes'
}
})
config.set_ext_param('two.example.com', 'ext1key', 'ext1val')

config.cartridge_bundle = 'BLTI001_Bundle'

correct = normalize_xml(CC_LTI_WITH_SUBOPTIONS_XML)
got = normalize_xml(config.to_xml())
>   self.assertEqual(got, correct)
E   AssertionError: b'http://www.w3.org/2001/XMLSchema-ins[1863 chars]ink>' != 
b'http://www.imsglobal.org/xsd/imslt[1863 chars]ink>'

tests/test_tool_config.py:159: AssertionError
___ TestToolConfig.test_generate_xml ___

self = 

def test_generate_xml(self):
'''
Should generate the expected config xml.
'''
config = ToolConfig(title = "Test Config",
secure_launch_url = "https://www.example.com/lti;,
custom_params = {"custom1": "customval1"})
config.description ='Description of boringness'
config.launch_url = 'http://www.example.com/lti'
config.vendor_code = 'test'
config.vendor_name = 'test.tool'
config.vendor_description = 'We test things'
config.vendor_url = 'http://www.example.com/about'
config.vendor_contact_email = 'supp...@example.com'
config.vendor_contact_name = 'Joe Support'

config.set_custom_param('custom2', 'customval2')

config.set_ext_params('example.com', { 'extkey1': 'extval1' })
config.set_ext_param('example.com', 'extkey2', 'extval2')
config.set_ext_param('example.com', 'extopt1',
{ 'optkey1': 'optval1', 'optkey2': 'optval2' })
config.set_ext_param('two.example.com', 'ext1key', 'ext1val')

config.cartridge_bundle = 'BLTI001_Bundle'

correct = normalize_xml(CC_LTI_XML)
got = normalize_xml(config.to_xml())
>   self.assertEqual(got, correct)
E   AssertionError: b'http://www.w3.org/2001/XMLSchema-ins[1807 chars]ink>' != 
b'http://www.imsglobal.org/xsd/imslt[1807 chars]ink>'

tests/test_tool_config.py:125: AssertionError
 TestToolConfig.test_optional_config_parameters 

self = 

def test_optional_config_parameters(self):
'''
Should contain cartridge_icon, and blti:icon.
'''
config = ToolConfig(title = "Test config",
launch_url = "http://www.example.com;,
secure_launch_url = "http://www.example.com;)
config.icon = 'http://wil.to/_/beardslap.gif'
config.secure_icon = 'https://www.example.com/secure_icon.png'
config.cartridge_icon = 'BLTI001_Icon'

correct = normalize_xml(CC_LTI_OPTIONAL_PARAMS_XML)
got = normalize_xml(config.to_xml())
>   

Bug#949194: marked as done (libnbd: FTBFS: dh: unable to load addon python3)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 12:37:51 +0100
with message-id <87zhdd7als@msgid.hilluzination.de>
and subject line Closing this bug.
has caused the Debian Bug report #949194,
regarding libnbd: FTBFS: dh: unable to load addon python3
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.)


-- 
949194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnbd
Version: 1.0.3-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid/amd64 chroot.
Attached is the full build log, hopefully relevant excerpt follows:

dpkg-buildpackage: info: source package libnbd
dpkg-buildpackage: info: source version 1.0.3-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Hilko Bengen 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with=python3,ocaml
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 12) line 
1.
BEGIN failed--compilation aborted at (eval 12) line 1.

make: *** [debian/rules:4: clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Fri Jan 17 21:13:32 UTC 2020
I: pbuilder-time-stamp: 1579295612
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/libnbd_1.0.3-1.dsc]
I: copying [pkgs/libnbd_1.0.3.orig.tar.gz]
I: copying [pkgs/libnbd_1.0.3.orig.tar.gz.asc]
I: copying [pkgs/libnbd_1.0.3-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sun Oct 13 00:00:18 2019 UTC
gpgv:using RSA key AE731055442A1D96CF4D4C7875B710635C213A7E
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./libnbd_1.0.3-1.dsc
dpkg-source: info: extracting libnbd in libnbd-1.0.3
dpkg-source: info: unpacking libnbd_1.0.3.orig.tar.gz
dpkg-source: info: unpacking libnbd_1.0.3-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 
0001-Disable-.opt-tests-if-ocamlopt-is-not-available.patch
dpkg-source: info: applying 
0002-interop-Increase-time-to-wait-for-nbd-server.patch
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/libnbd_1.0.3-1.dsc' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdmainutils debhelper
  dh-autoreconf dh-ocaml dh-strip-nondeterminism dwz file gettext gettext-base
  gnutls-bin groff-base icu-devtools intltool-debian libaio1
  libarchive-zip-perl libbrotli1 libbsd0 libcroco3 libcurl3-gnutls
  libdebhelper-perl libelf1 libevent-2.1-7 libexpat1 libexpat1-dev
  libfile-stripnondeterminism-perl libfindlib-ocaml libglib2.0-0 libgmp-dev
  libgmpxx4ldbl libgnutls-dane0 libgnutls-openssl27 libgnutls28-dev
  libgnutlsxx28 libgssapi-krb5-2 libicu-dev libicu63 libidn2-dev libk5crypto3
  libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common
  libmagic-mgc libmagic1 libmpdec2 libnbd0 libncurses-dev libncurses5-dev
  libncurses6 libnghttp2-14 libopts25 libp11-kit-dev libpipeline1 libpsl5
  libpython3-dev libpython3-stdlib libpython3.7 libpython3.7-dev
  libpython3.7-minimal libpython3.7-stdlib libreadline8 librtmp1 libsasl2-2
  libsasl2-modules-db libsigsegv2 libsqlite3-0 libssh-4 libssh2-1 libssl1.1
  libsub-override-perl libtasn1-6-dev libtool libuchardet0 

Processed: Bug#950073 marked as pending in python-lti

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950073 [src:python-lti] python-lti FTBFS; test failures
Added tag(s) pending.

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

Bug#950073: marked as pending in python-lti

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #950073 in python-lti 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/python-lti/commit/5508d186ff14a49d011044f5239dcccf9196d877


Add patch to canonicalize (C14N) XML structures before comparing them (Closes: 
#950073).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950073

Bug#951706: gdspy hard-codes python3.7, without depending on it

[Matthias Klose]

Package: src:gdspy
Version: 1.4.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

override_dh_installdocs hard-codes the use of python 3.7, which will break with
3.8.  Please make the rules file independent of the python version.

Bug#951705: Do not link with OpenSSL

[Bastian Germann]

Package: mupdf
Version: 1.15.0+ds1-1
Severity: serious

mupdf is AGPL licensed and does not come with an OpenSSL linking
exception. According to ftp-master this is a serious violation
(https://ftp-master.debian.org/REJECT-FAQ.html).

Not linking with libssl does not lead to any package errors and only
slightly reduces the package's features.
I removed it in
https://salsa.debian.org/koster/mupdf/merge_requests/2

Bug#951703: swig: does not install /usr/bin/swig anymore

[Ole Streicher]

Package: swig
Version: 4.0.1-2
Severity: serious
Affects: astrometry.net
Tags: +patch

The "swig" binary package does not install a symlink /usr/bin/swig -->
swig4.0 anymore. Since this breaks the build of a number of packages, I
set the severity to "serious".

Typical error message:

swig -python -I../include -I../include/astrometry -I/usr/include/wcslib
-I../include -I../include/astrometry -I/usr/include/wcslib -o
util_wrap.c util.i
error: command 'swig' failed with exit status 1

>From the source (on salsa), I guess this was just forgotten to adjust.

See

https://salsa.debian.org/debian/swig/merge_requests/1

for the trivial fix.

Best

Ole

Bug#951702: subvertpy ftbfs on 64bit big endian targets

[Matthias Klose]

Package: src:subvertpy
Version: 0.11.0~git20191228+2423bf1-1
Severity: serious
Tags: sid bullseye

seen on ppc64 and s390x at least:

[...]
Generating objects inventory at apidocs/objects.inv
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test
running test
running build
running build_py
running build_ext
running build_scripts
Running unittest without install.
Segmentation fault
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=139:
python2.7 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p 2.7 returned exit 
code 13

Bug#950675: upstream does support it, but ...

[Dimitri John Ledkov]

I do wonder if doxygen-latex should instead be replaced by docbook
output + docbook2pdf.

Bug#931903: marked as done (node-acorn: fails to upgrade from 'sid' - trying to overwrite /usr/lib/nodejs/acorn-dynamic-import/lib/index.js)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 10:19:04 +
with message-id 
and subject line Bug#931903: fixed in acorn 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
has caused the Debian Bug report #931903,
regarding node-acorn: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/nodejs/acorn-dynamic-import/lib/index.js
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.)


-- 
931903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-acorn
Version: 
6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack 
.../node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb
 ...
  Unpacking node-acorn 
(6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1)
 over (5.5.3+ds3-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb
 (--unpack):
   trying to overwrite '/usr/lib/nodejs/acorn-dynamic-import/lib/index.js', 
which is also in package node-acorn-dynamic-import 4.0.0-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb


cheers,

Andreas


node-acorn-dynamic-import=4.0.0-1_node-acorn=6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: acorn
Source-Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
Done: =?utf-8?q?Bastien_Roucari=C3=A8s?= 

We believe that the bug you reported is fixed in the latest version of
acorn, 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 931...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated acorn 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: Thu, 20 Feb 2020 11:00:16 +0100
Source: acorn
Architecture: source
Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Closes: 915022 931903
Changes:
 acorn 
(6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7)
 experimental; urgency=medium
 .
   * Bug fix: "fails to upgrade from sid: unable to install new version of
 '/usr/share/doc/node-acorn-node/README.md': No such file or
 directory", thanks to Andreas Beckmann (Closes: #915022).
   * Bug fix: "fails to upgrade from sid - trying to overwrite
 /usr/lib/nodejs/acorn-dynamic-import/lib/index.js", thanks to Andreas
 Beckmann (Closes: #931903).
Checksums-Sha1:
 7ce9eab2c33913787012b42549b44b13b7fd49bd 9892 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7.dsc
 3702bf2a9cd7229a90bf13e9dade12f31812647d 15672 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7.debian.tar.xz
 dd71c93db45d004438b63d781342cc2d97295065 16800 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7_source.buildinfo
Checksums-Sha256:
 28ca68619d91ed0dc1ebbdbd4f906e437538719d647fd5fc2c42a470e9882369 

Bug#915022: marked as done (node-acorn: fails to upgrade from sid: unable to install new version of '/usr/share/doc/node-acorn-node/README.md': No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 10:19:04 +
with message-id 
and subject line Bug#915022: fixed in acorn 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
has caused the Debian Bug report #915022,
regarding node-acorn: fails to upgrade from sid: unable to install new version 
of '/usr/share/doc/node-acorn-node/README.md': No such file or directory
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.)


-- 
915022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-acorn
Version: 
6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

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

  Preparing to unpack 
.../node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb
 ...
  Unpacking node-acorn 
(6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1)
 over (5.5.3+ds3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb
 (--unpack):
   unable to install new version of '/usr/share/doc/node-acorn-node/README.md': 
No such file or directory
  Errors were encountered while processing:
   
/var/cache/apt/archives/node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb

Is it trying to install a file over an existing, broken directory symlink?


cheers,

Andreas


node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: acorn
Source-Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
Done: =?utf-8?q?Bastien_Roucari=C3=A8s?= 

We believe that the bug you reported is fixed in the latest version of
acorn, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated acorn 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: Thu, 20 Feb 2020 11:00:16 +0100
Source: acorn
Architecture: source
Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Closes: 915022 931903
Changes:
 acorn 
(6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7)
 experimental; urgency=medium
 .
   * Bug fix: "fails to upgrade from sid: unable to install new version of
 '/usr/share/doc/node-acorn-node/README.md': No such file or
 directory", thanks to Andreas Beckmann (Closes: #915022).
   * Bug fix: "fails to upgrade from sid - trying to overwrite
 /usr/lib/nodejs/acorn-dynamic-import/lib/index.js", thanks to Andreas
 Beckmann (Closes: #931903).
Checksums-Sha1:
 7ce9eab2c33913787012b42549b44b13b7fd49bd 9892 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7.dsc
 3702bf2a9cd7229a90bf13e9dade12f31812647d 15672 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7.debian.tar.xz
 dd71c93db45d004438b63d781342cc2d97295065 16800 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7_source.buildinfo
Checksums-Sha256:
 28ca68619d91ed0dc1ebbdbd4f906e437538719d647fd5fc2c42a470e9882369 9892 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-7.dsc
 666cf55ef0286ba43b8df1686bd186e4a1c2fbdcaaba0263eb25fadf90e0ef9b 

Bug#951698: linux kernel 5.x does not work with disk encryption 4.19 works

[Pirate Praveen]

Package: linux-image-amd64
Version: 5.4.19-1, 5.5~rc5-1~exp1
Control: notfound -1 4.19.67-2+deb10u2
Severity: critical
justification: makes system unbootable

When trying to unlock an encrypted disk it fails with error (the 
encryption was setup by buster debian installer).

libgcc_s.so.1 must be installed for pthread_cancel to work.

libgcc_s.so.1 seems to be still present and latest version.

$ dpkg -S libgcc_s.so.1
libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
libgcc-9-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1
libgcc-8-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/8/libgcc_s.so.1
libgcc1: /lib/libgcc_s.so.1

This started happening after upgrading the system from buster to sid. 
With older kernel version from buster, the system still boots without 
any problem.


System Information
   Manufacturer: LENOVO
   Product Name: 20AMS16Q03
   Version: ThinkPad X240

Processed: linux kernel 5.x does not work with disk encryption 4.19 works

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 4.19.67-2+deb10u2
Bug #951698 [linux-image-amd64] linux kernel 5.x does not work with disk 
encryption 4.19 works
There is no source info for the package 'linux-image-amd64' at version 
'4.19.67-2+deb10u2' with architecture ''
Unable to make a source version for version '4.19.67-2+deb10u2'
Ignoring request to alter found versions of bug #951698 to the same values 
previously set

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

Processed: limit source to acorn, tagging 931903, tagging 915022

[Debian Bug Tracking System]

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

> limit source acorn
Limiting to bugs with field 'source' containing at least one of 'acorn'
Limit currently set to 'source':'acorn'

> tags 931903 + pending
Bug #931903 [node-debbundle-acorn] node-acorn: fails to upgrade from 'sid' - 
trying to overwrite /usr/lib/nodejs/acorn-dynamic-import/lib/index.js
Added tag(s) pending.
> tags 915022 + pending
Bug #915022 [node-acorn] node-acorn: fails to upgrade from sid: unable to 
install new version of '/usr/share/doc/node-acorn-node/README.md': No such file 
or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#950063: influxdb-python FTBFS with pandas 0.25.3

[Andreas Tille]

Hi Alexandre,

On Wed, Feb 19, 2020 at 09:51:43AM -0500, Alexandre Viau wrote:
> Feel free to move influxdb-python to DPMT.

Thanks.
 
> However, if you do, please remove me from the maintainers and
> delete/move the existing salsa project.

For sure I can transfer the project on Salsa.

Regarding your wish to remove you from Maintainers: I did not intend to
take over the package from you personally.  I rather wanted to do
something like:

  Maintainer: Debian Python Modules Team 

  Uploaders: Alexandre Viau 

and you become a member of DPMT to maintain the package inside the team.
If you are short in time I could probably do a team upload to fix the
current issues, thought.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#950049: marked as done (python-djangosaml2 FTBFS with Python 3.8 as supported version)

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 09:05:38 +
with message-id 
and subject line Bug#950049: fixed in python-djangosaml2 0.18.1-1
has caused the Debian Bug report #950049,
regarding python-djangosaml2 FTBFS with Python 3.8 as supported version
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.)


-- 
950049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-djangosaml2
Version: 0.17.2-1
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-djangosaml2.html

...
==
FAIL: test_login_one_idp (djangosaml2.tests.SAML2Tests)
--
Traceback (most recent call last):
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 150, in test_login_one_idp
self.assertSAMLRequestsEquals(
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 86, in assertSAMLRequestsEquals
self.assertEqual(remove_variable_attributes(real_xml),
AssertionError: 'https://idp.ex[418 chars]est>' != 'http://sp.ex[418 chars]est>'
Diff is 2245 characters long. Set self.maxDiff to None to see it.

==
FAIL: test_login_several_idps (djangosaml2.tests.SAML2Tests)
--
Traceback (most recent call last):
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 208, in test_login_several_idps

self.assertSAMLRequestsEquals(decode_base64_and_inflate(saml_request).decode('utf-8'),
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 86, in assertSAMLRequestsEquals
self.assertEqual(remove_variable_attributes(real_xml),
AssertionError: 'https://idp2.e[419 chars]est>' != 'http://sp.ex[419 chars]est>'
Diff is 2249 characters long. Set self.maxDiff to None to see it.

==
FAIL: test_logout_service_global (djangosaml2.tests.SAML2Tests)
--
Traceback (most recent call last):
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 429, in test_logout_service_global

self.assertSAMLRequestsEquals(decode_base64_and_inflate(saml_response).decode('utf-8'),
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 86, in assertSAMLRequestsEquals
self.assertEqual(remove_variable_attributes(real_xml),
AssertionError: 'https://idp.example.com/simp[356 chars]nse>'
Diff is 1548 characters long. Set self.maxDiff to None to see it.

==
FAIL: test_logout_service_local (djangosaml2.tests.SAML2Tests)
--
Traceback (most recent call last):
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 377, in test_logout_service_local

self.assertSAMLRequestsEquals(decode_base64_and_inflate(saml_request).decode('utf-8'),
  File 
"/build/1st/python-djangosaml2-0.17.2/.pybuild/cpython3_3.8_django-saml2/build/djangosaml2/tests/__init__.py",
 line 86, in assertSAMLRequestsEquals
self.assertEqual(remove_variable_attributes(real_xml),
AssertionError: 'https://idp.ex[424 chars]est>' != 'https://idp.example.com/simp[424 chars]est>'
Diff is 1191 characters long. Set self.maxDiff to None to see it.

--
Ran 23 tests in 0.402s

FAILED (failures=4, skipped=1)
Destroying test database for alias 'default'...
System check identified no issues (0 silenced).
E: pybuild pybuild:341: test: plugin custom failed with: exit code=1: python3.8 
tests/run_tests.py
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned 
exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: python-djangosaml2
Source-Version: 0.18.1-1
Done: Michael Fladischer 

We believe that the bug you 

Bug#951611: marked as done (python-django-modelcluster: autopkgtest failure: No module named 'django_modelcluster')

[Debian Bug Tracking System]

Your message dated Thu, 20 Feb 2020 08:50:02 +
with message-id 
and subject line Bug#951611: fixed in python-django-modelcluster 5.0.1-2
has caused the Debian Bug report #951611,
regarding python-django-modelcluster: autopkgtest failure: No module named 
'django_modelcluster'
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.)


-- 
951611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-modelcluster
Version: 5.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainers,

Your new package python-django-modelcluster has an autopkgtest, great.
However, it fails. I copied some of the output at the bottom of this
report. You're using autodep8 to trigger the test, but it seems your
package naming and Python module name aren't aligned for autodep8.
autodep8 recently acquired a new feature that enables you to tell
autode8 what the real module name is that should be tested [1].

Currently this regression is blocking the migration to testing [2]. Can
you please investigate the situation and fix it?

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

Paul

[1]
https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES
[2] https://qa.debian.org/excuses.php?package=python-django-modelcluster

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-modelcluster/4070428/log.gz

autopkgtest [03:13:18]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import django_modelcluster;
print(django_modelcluster)" ; done
autopkgtest [03:13:18]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'django_modelcluster'



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-django-modelcluster
Source-Version: 5.0.1-2
Done: Michael Fladischer 

We believe that the bug you reported is fixed in the latest version of
python-django-modelcluster, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
python-django-modelcluster 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: Thu, 20 Feb 2020 09:28:13 +0100
Source: python-django-modelcluster
Architecture: source
Version: 5.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Closes: 951611
Changes:
 python-django-modelcluster (5.0.1-2) unstable; urgency=medium
 .
   * Tell autodep8 to use the correct import name (Closes: #951611).
   * Bump Standards-Version to 4.5.0.
Checksums-Sha1:
 a8928ba716a3b8b61f7723e71f05b85a8a2c44ab 1921 
python-django-modelcluster_5.0.1-2.dsc
 63911c9fdbaeae506888e0affac53fe08de279b7 2644 
python-django-modelcluster_5.0.1-2.debian.tar.xz
 4cc0f9b1c42bb6ac1b7b5ba0ea1c758ec2d1a32e 7252 
python-django-modelcluster_5.0.1-2_amd64.buildinfo
Checksums-Sha256:
 0d67f9e47ba830502ce66edd32f01d2dbf0e8695ddf93b146c461b2d68751fa1 1921 
python-django-modelcluster_5.0.1-2.dsc
 0e893c51113aa8a1b151be3ecc69e1fa66f0c5ea36f9e7c07e1b04385080c5c4 2644 
python-django-modelcluster_5.0.1-2.debian.tar.xz
 d85da29cfae4257d70a117730ff95b6b0664251e0e57b84dac3360ac9201bb6b 7252 
python-django-modelcluster_5.0.1-2_amd64.buildinfo
Files:
 530e48783648fe33159b12dba966a862 1921 python optional 
python-django-modelcluster_5.0.1-2.dsc
 6016ea73698e3855cf293fbcfc0e6189 2644 python optional 
python-django-modelcluster_5.0.1-2.debian.tar.xz
 2430a161bbd4d4e88b537185eac95077 7252 python optional 
python-django-modelcluster_5.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl5ORQMACgkQ/9PIi5l9

Bug#951691: src:ruby-prawn-svg: fails to migrate to testing for too long

[Paul Gevers]

Source: ruby-prawn-svg
Version: 0.28.0-3
Severity: serious
Control: fixed -1 0.29.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:ruby-prawn-svg in its current version in unstable has been trying to
migrate for 346 days. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Processed: src:ruby-prawn-svg: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.29.1-1
Bug #951691 [src:ruby-prawn-svg] src:ruby-prawn-svg: fails to migrate to 
testing for too long
Marked as fixed in versions ruby-prawn-svg/0.29.1-1.

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

Processed: src:infnoise: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.3.1+dfsg-1
Bug #951689 [src:infnoise] src:infnoise: fails to migrate to testing for too 
long
Marked as fixed in versions infnoise/0.3.1+dfsg-1.

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

Bug#951690: src:python-cobra: fails to migrate to testing for too long

[Paul Gevers]

Source: python-cobra
Version: 0.14.1-1
Severity: serious
Control: fixed -1 0.14.2-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:python-cobra
in its current version in unstable has been trying to migrate for 354
days. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Bug#951689: src:infnoise: fails to migrate to testing for too long

[Paul Gevers]

Source: infnoise
Version: 0.2.6+dfsg-1
Severity: serious
Control: fixed -1 0.3.1+dfsg-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:infnoise in
its current version in unstable has been trying to migrate for 360 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Processed: src:python-cobra: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.14.2-2
Bug #951690 [src:python-cobra] src:python-cobra: fails to migrate to testing 
for too long
Marked as fixed in versions python-cobra/0.14.2-2.

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

Processed: src:aspell-ta: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 20040424-1-2
Bug #951688 [src:aspell-ta] src:aspell-ta: fails to migrate to testing for too 
long
Marked as fixed in versions aspell-ta/20040424-1-2.

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

Bug#951688: src:aspell-ta: fails to migrate to testing for too long

[Paul Gevers]

Source: aspell-ta
Version: 20040424-1-1
Severity: serious
Control: fixed -1 20040424-1-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:aspell-ta in
its current version in unstable has been trying to migrate for 362 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature