date:20190919

Your message dated Fri, 20 Sep 2019 05:20:13 +
with message-id 
and subject line Bug#940795: fixed in ufolib2 0.4.0+dfsg1-2
has caused the Debian Bug report #940795,
regarding fonttools breaks ufolib2 autopkgtest: cannot import name 'PY3' from 
'fontTools.misc.py23
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.)


-- 
940795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonttools, ufolib2
Control: found -1 fonttools/4.0.0-1
Control: found -1 ufolib2/0.3.2+dfsg1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of fonttools the autopkgtest of ufolib2 fails in
testing when that autopkgtest is run with the binary packages of
fonttools from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
fonttools  from testing4.0.0-1
ufolib2from testing0.3.2+dfsg1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of fonttools to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? By the way, the version of
ufolib2 in unstable is failing for a different reason.

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

Paul

[1] https://qa.debian.org/excuses.php?package=fonttools

https://ci.debian.net/data/autopkgtest/testing/amd64/u/ufolib2/2990429/log.gz

Testing with python3.7:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ufoLib2/__init__.py", line 3, in

from ufoLib2.objects import Font
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/__init__.py",
line 4, in 
from ufoLib2.objects.font import Font
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/font.py", line 9,
in 
from ufoLib2.objects.info import Info
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/info.py", line 4,
in 
from ufoLib2.types import (
  File "/usr/lib/python3/dist-packages/ufoLib2/types.py", line 2, in

from fontTools.misc.py23 import PY3
ImportError: cannot import name 'PY3' from 'fontTools.misc.py23'
(/usr/lib/python3/dist-packages/fontTools/misc/py23.py)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ufolib2
Source-Version: 0.4.0+dfsg1-2

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

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

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

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷)  (supplier of updated ufolib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 13:00:47 +0800
Source: ufolib2
Binary: python3-ufolib2
Architecture: source all
Version: 0.4.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Yao Wei (魏銘廷) 
Description:
 python3-ufolib2 - Unified Font Object (UFO) fonts library
Closes: 940795
Changes:
 ufolib2 (0.4.0+dfsg1-2) unstable; urgency=medium
 .
   * debian/control:
 - Bump debhelper-compat to 12
 - Remove Testsuite because module name is different to the package name
   (Closes: #940795)
   * debian/rules:
 - debian/rules: Add PYBUILD_NAME
 - Use PYBUILD_TEST_ARGS instead of overriding dh_auto_test
Checksums-Sha1:
 7eb95fb340e5dc6548670c7bc987e1b3cce8092c 2185 ufolib2_0.4.0+dfsg1-2.dsc
 e35238590982c0be96f341936815ab5135017fad 2436 
ufolib2_0.4.0+dfsg1-2.debian.tar.xz
 e667f73265b459a5c135886bd2883e40d2651915 13632 
python3-ufolib2_0.4.0+dfsg1-2_all.deb
 329f3249ba4dfd9c8b9e22d05f9770f5e92d7c72 7877 
ufolib2_0.4.0+dfsg1-2_amd64.buildinfo
Checksums-Sha256:

Processed: reassign 940795 to ufolib2

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

> reassign 940795 ufolib2
Bug #940795 [src:fonttools, src:ufolib2] fonttools breaks ufolib2 autopkgtest: 
cannot import name 'PY3' from 'fontTools.misc.py23
Bug reassigned from package 'src:fonttools, src:ufolib2' to 'ufolib2'.
No longer marked as found in versions fonttools/4.0.0-1 and 
ufolib2/0.3.2+dfsg1-1.
Ignoring request to alter fixed versions of bug #940795 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: udev rules and created user conflict with the one shipped in trousers package

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

> block 918973 by 940807
Bug #918973 [libtss2-udev] udev rules and created user conflict with the one 
shipped in trousers package
918973 was not blocked by any bugs.
918973 was not blocking any bugs.
Added blocking bug(s) of 918973: 940807
> thanks
Stopping processing here.

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

Bug#918973: udev rules and created user conflict with the one shipped in trousers package

2019-09-19 Thread Ying-Chun Liu (PaulLiu)

block 918973 by 940807

thanks


Hi.

I've now preparing a native package that solves the problem. Will upload
it soon to NEW and to salsa.

Thanks,
Paul




signature.asc
Description: OpenPGP digital signature

Bug#934966: marked as done (libstb: CVE-2019-13217 CVE-2019-13218 CVE-2019-13219 CVE-2019-13220 CVE-2019-13221 CVE-2019-13222 CVE-2019-13223)

Your message dated Fri, 20 Sep 2019 03:19:31 +
with message-id 
and subject line Bug#934966: fixed in libstb 0.0~git20190817.1.052dce1-1
has caused the Debian Bug report #934966,
regarding libstb: CVE-2019-13217 CVE-2019-13218 CVE-2019-13219 CVE-2019-13220 
CVE-2019-13221 CVE-2019-13222 CVE-2019-13223
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.)


-- 
934966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstb
Version: 0.0~git20190617.5.c72a95d-2
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for libstb.

CVE-2019-13217[0]:
| A heap buffer overflow in the start_decoder function in stb_vorbis
| through 2019-03-04 allows an attacker to cause a denial of service or
| execute arbitrary code by opening a crafted Ogg Vorbis file.


CVE-2019-13218[1]:
| Division by zero in the predict_point function in stb_vorbis through
| 2019-03-04 allows an attacker to cause a denial of service by opening
| a crafted Ogg Vorbis file.


CVE-2019-13219[2]:
| A NULL pointer dereference in the get_window function in stb_vorbis
| through 2019-03-04 allows an attacker to cause a denial of service by
| opening a crafted Ogg Vorbis file.


CVE-2019-13220[3]:
| Use of uninitialized stack variables in the start_decoder function in
| stb_vorbis through 2019-03-04 allows an attacker to cause a denial of
| service or disclose sensitive information by opening a crafted Ogg
| Vorbis file.


CVE-2019-13221[4]:
| A stack buffer overflow in the compute_codewords function in
| stb_vorbis through 2019-03-04 allows an attacker to cause a denial of
| service or execute arbitrary code by opening a crafted Ogg Vorbis
| file.


CVE-2019-13222[5]:
| An out-of-bounds read of a global buffer in the draw_line function in
| stb_vorbis through 2019-03-04 allows an attacker to cause a denial of
| service or disclose sensitive information by opening a crafted Ogg
| Vorbis file.


CVE-2019-13223[6]:
| A reachable assertion in the lookup1_values function in stb_vorbis
| through 2019-03-04 allows an attacker to cause a denial of service by
| opening a crafted Ogg Vorbis file.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-13217
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13217
[1] https://security-tracker.debian.org/tracker/CVE-2019-13218
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13218
[2] https://security-tracker.debian.org/tracker/CVE-2019-13219
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13219
[3] https://security-tracker.debian.org/tracker/CVE-2019-13220
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13220
[4] https://security-tracker.debian.org/tracker/CVE-2019-13221
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13221
[5] https://security-tracker.debian.org/tracker/CVE-2019-13222
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13222
[6] https://security-tracker.debian.org/tracker/CVE-2019-13223
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13223

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libstb
Source-Version: 0.0~git20190817.1.052dce1-1

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated libstb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 08:31:51 +0800
Source: libstb
Architecture: source
Version: 0.0~git20190817.1.052dce1-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Yangfl 
Closes: 932660 934966
Changes:
 libstb (0.0~git20190817.1.052dce1-1) unstable; urgency=medium
 .
   [ Boyuan Yang ]
   * New upstream snapshot

Bug#939754: gimp: Still happening

2019-09-19 Thread Antonio Campos

I see what you mean. have to do a fresh install then.

Thanks a lot for your help.
Best regards.

El vie., 20 sept. 2019 3:56, Jeremy Bicha  escribió:

> On Thu, Sep 19, 2019 at 9:33 PM Antonio Campos 
> wrote:
> > Here is your output:
> > 
> > apt policy libgegl-0.4-0
> > libgegl-0.4-0:
> >   Installed: 1:0.4.16-dmo2
> >   Candidate: 1:0.4.16-dmo2
> >   Version table:
> >  *** 1:0.4.16-dmo2 100
> > 100 /var/lib/dpkg/status
>
> We cannot support the use of the deb-multimedia.org repositories.
>
> The Installed line should read:
>  Installed: 0.4.14-2
>
> Perhaps the simplest way to fix your system is to do a new install and
> don't add that repository.
>
> Thanks,
> Jeremy Bicha
>

Bug#939754: gimp: Still happening

On Thu, Sep 19, 2019 at 9:33 PM Antonio Campos  wrote:
> Here is your output:
> 
> apt policy libgegl-0.4-0
> libgegl-0.4-0:
>   Installed: 1:0.4.16-dmo2
>   Candidate: 1:0.4.16-dmo2
>   Version table:
>  *** 1:0.4.16-dmo2 100
> 100 /var/lib/dpkg/status

We cannot support the use of the deb-multimedia.org repositories.

The Installed line should read:
 Installed: 0.4.14-2

Perhaps the simplest way to fix your system is to do a new install and
don't add that repository.

Thanks,
Jeremy Bicha

Bug#935843: marked as done (node-babel-plugin-transform-define: autopkgtest fails on deprecation warning with new version of node-lodash)

Your message dated Fri, 20 Sep 2019 01:49:10 +
with message-id 
and subject line Bug#935843: fixed in node-babel-plugin-transform-define 1.3.0-3
has caused the Debian Bug report #935843,
regarding node-babel-plugin-transform-define: autopkgtest fails on deprecation 
warning with new version of node-lodash
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.)


-- 
935843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-babel-plugin-transform-define
Version: 1.3.0-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:node-lodash

[X-Debbugs-CC: debian...@lists.debian.org, node-lod...@packages.debian.org]

Dear maintainers,

With a recent upload of node-lodash the autopkgtest of
node-babel-plugin-transform-define fails in testing when that
autopkgtest is run with the binary packages of node-lodash from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
node-lodash from testing4.17.15+dfsg-1
node-babel-plugin-transform-define  from testing1.3.0-2
all others  from testingfrom testing

I copied some of the output at the bottom of this report. The test fails
an a deprecation *warning* reported to stderr. Either you want to fix
the deprecation *now*, disable deprecation warnings in autopkgtest or
allow output to stderr by setting the allow-stderr restriction.

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=node-lodash

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-babel-plugin-transform-define/2822448/log.gz

autopkgtest [11:16:18]: test require: [---
(node:1065) [DEP0016] DeprecationWarning: 'root' is deprecated, use 'global'
autopkgtest [11:16:19]: test require: ---]
autopkgtest [11:16:19]: test require:  - - - - - - - - - - results - - -
- - - - - - -
require  FAIL stderr: (node:1065) [DEP0016]
DeprecationWarning: 'root' is deprecated, use 'global'
autopkgtest [11:16:20]: test require:  - - - - - - - - - - stderr - - -
- - - - - - -



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-babel-plugin-transform-define
Source-Version: 1.3.0-3

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated 
node-babel-plugin-transform-define package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 03:28:26 +0200
Source: node-babel-plugin-transform-define
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 935843
Changes:
 node-babel-plugin-transform-define (1.3.0-3) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.4.0
   * Add debian/gbp.conf
   * Add upstream/metadata
   * Install CODE_OF_CONDUCT.md in the right place
   * Update VCS fields to salsa
   * Switch install and minimal test to pkg-js-tools (Closes: #935843)
   * Enable upstream test (this embeds assert-transform for test only)
   * Add mocha, node-bluebird and node-colors in build dependencies
Checksums-Sha1: 
 f4890406529913d3532f1e06f6700e28fbfd41d6 2589 
node-babel-plugin-transform-define_1.3.0-3.dsc

Bug#939754: gimp: Still happening

2019-09-19 Thread Antonio Campos

Hi again,

Just to let you know, Gimp seems to be working fine again after that last
upgrade I did. But the library you mention is a mystery.

Many Thanks.

Here is your output:

apt policy libgegl-0.4-0
libgegl-0.4-0:
  Installed: 1:0.4.16-dmo2
  Candidate: 1:0.4.16-dmo2
  Version table:
 *** 1:0.4.16-dmo2 100
100 /var/lib/dpkg/status

On Fri, 20 Sep 2019 at 03:24, Jeremy Bicha  wrote:

> On Thu, Sep 19, 2019 at 9:20 PM Antonio Campos 
> wrote:
> > Really sorry but did all my upgrades again and can't get that version of
> 'libgegl' in any repo, the newest available is '0-4.0'. Tried different
> mirros from different countries, and also checked but is not even in SID.
>
> Please post the output of
>
> apt policy libgegl-0.4-0
>
> Thanks,
> Jeremy
>

Bug#939754: gimp: Still happening

On Thu, Sep 19, 2019 at 9:20 PM Antonio Campos  wrote:
> Really sorry but did all my upgrades again and can't get that version of 
> 'libgegl' in any repo, the newest available is '0-4.0'. Tried different 
> mirros from different countries, and also checked but is not even in SID.

Please post the output of

apt policy libgegl-0.4-0

Thanks,
Jeremy

Bug#939754: gimp: Still happening

2019-09-19 Thread Antonio Campos

Really sorry but did all my upgrades again and can't get that version of
'libgegl' in any repo, the newest available is '0-4.0'. Tried different
mirros from different countries, and also checked but is not even in SID.

Could be a mirroring issue??

Hope that helps. Many thanks.

Tested with US, UK, Australia and Spain mirrors (plus deb.debian.org).
Currently using UK:

deb http://ftp.uk.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ testing main contrib non-free

deb http://ftp.uk.debian.org/debian/ testing-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ testing-updates main contrib
non-free

deb http://security.debian.org/ testing-security main
deb-src http://security.debian.org/ testing-security main

El vie., 20 sept. 2019 2:12, Jeremy Bicha  escribió:

> On Thu, Sep 19, 2019 at 7:15 PM amgcampos  wrote:
> > - Recently did a distro-upgrade to bullseye.
>
> Please install all updates (sudo apt update && sudo apt dist-upgrade).
> libgegl-0.4-0 is now at version 0.14.4-2.
>
> Thanks,
> Jeremy
>

Processed: try to unblock totem from migrationg to testing

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

> notfound 934390 3.30.0-4
Bug #934390 {Done: Simon McVittie } [totem] totem, nautilus: 
not co-installable in unstable
No longer marked as found in versions totem/3.30.0-4.
>
End of message, stopping processing here.

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

Bug#939754: gimp: Still happening

On Thu, Sep 19, 2019 at 7:15 PM amgcampos  wrote:
> - Recently did a distro-upgrade to bullseye.

Please install all updates (sudo apt update && sudo apt dist-upgrade).
libgegl-0.4-0 is now at version 0.14.4-2.

Thanks,
Jeremy

Bug#896346: marked as done (python-guessit: guessit fails to import)

Your message dated Thu, 19 Sep 2019 23:34:49 +
with message-id 
and subject line Bug#896202: fixed in guessit 3.0.0-1
has caused the Debian Bug report #896202,
regarding python-guessit: guessit fails to import
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.)


-- 
896202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-guessit
Version: 0.11.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-guessit importing the module guessit
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/guessit/__init__.py", line 99, in 

from guessit.plugins import transformers
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
222, in 
reload()
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
220, in reload
reload_options(all_transformers())
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
179, in all_transformers
return _extensions.objects()
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 261, in 
map
raise NoMatches('No %s extensions found' % self.namespace)
stevedore.exception.NoMatches: No guessit.transformer extensions found

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: guessit
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated guessit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Sep 2019 00:57:32 +0200
Source: guessit
Binary: python3-guessit
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python3-guessit - library for guessing information from video filenames 
(Python 3)
Closes: 867862 881289 896202 896282 907821 936675
Changes:
 guessit (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Carl Suster ]
   * Add gbp config file
   * New upstream release (Closes: #867862, #881289, #907821):
 - Fix failed to import in Python 3 (Closes: #896282).
 - drop patches: upstream has been rewritten
   * Add myself to Uploaders
 .
   [ Thomas Goirand ]
   * Team upload.
   * Removed Python 2 support (Closes: #936675).
 - Fixed failed to import in Python 2 (Closes: #896202).
   * Fixed (build-)depends for this release.
   * Add remove-failing-tests.patch.
   * Fix Standards-Version to 4.4.0
Checksums-Sha1:
 f264839434f14168c42f34b02e039beacc9b435d 2373 guessit_3.0.0-1.dsc
 b724f5dcf7852cc8958ec7bdad6974858b8b9d26 133379 guessit_3.0.0.orig.tar.gz
 d714f2075b7d03d0c2b4701a254e820c68c2dabc 5228 guessit_3.0.0-1.debian.tar.xz
 84b61b750317d80ead3b3d2c3952629fef706d1f 6955 guessit_3.0.0-1_amd64.buildinfo
 c0d2456fc2b9cd473be4f25c78aea324ce4bfbc7 103824

Bug#896282: marked as done (python3-guessit: guessit fails to import)

Your message dated Thu, 19 Sep 2019 23:34:49 +
with message-id 
and subject line Bug#896282: fixed in guessit 3.0.0-1
has caused the Debian Bug report #896282,
regarding python3-guessit: guessit fails to import
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.)


-- 
896282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-guessit
Version: 0.11.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-guessit importing the module guessit
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/guessit/__init__.py", line 99, in 

from guessit.plugins import transformers
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
222, in 
reload()
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
220, in reload
reload_options(all_transformers())
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
179, in all_transformers
return _extensions.objects()
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 261, in map
raise NoMatches('No %s extensions found' % self.namespace)
stevedore.exception.NoMatches: No guessit.transformer extensions found

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: guessit
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated guessit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Sep 2019 00:57:32 +0200
Source: guessit
Binary: python3-guessit
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python3-guessit - library for guessing information from video filenames 
(Python 3)
Closes: 867862 881289 896202 896282 907821 936675
Changes:
 guessit (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Carl Suster ]
   * Add gbp config file
   * New upstream release (Closes: #867862, #881289, #907821):
 - Fix failed to import in Python 3 (Closes: #896282).
 - drop patches: upstream has been rewritten
   * Add myself to Uploaders
 .
   [ Thomas Goirand ]
   * Team upload.
   * Removed Python 2 support (Closes: #936675).
 - Fixed failed to import in Python 2 (Closes: #896202).
   * Fixed (build-)depends for this release.
   * Add remove-failing-tests.patch.
   * Fix Standards-Version to 4.4.0
Checksums-Sha1:
 f264839434f14168c42f34b02e039beacc9b435d 2373 guessit_3.0.0-1.dsc
 b724f5dcf7852cc8958ec7bdad6974858b8b9d26 133379 guessit_3.0.0.orig.tar.gz
 d714f2075b7d03d0c2b4701a254e820c68c2dabc 5228 guessit_3.0.0-1.debian.tar.xz
 84b61b750317d80ead3b3d2c3952629fef706d1f 6955 guessit_3.0.0-1_amd64.buildinfo
 c0d2456fc2b9cd473be4f25c78aea324ce4bfbc7 103824 python3-guessit_3.0.0-1_all.deb

Bug#896322: marked as done (python3-subliminal: subliminal fails to import)

Your message dated Thu, 19 Sep 2019 23:34:49 +
with message-id 
and subject line Bug#896282: fixed in guessit 3.0.0-1
has caused the Debian Bug report #896282,
regarding python3-subliminal: subliminal fails to import
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.)


-- 
896282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-subliminal
Version: 1.1.1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-subliminal importing the module subliminal
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/subliminal/__init__.py", line 10, in 

from .api import (ProviderPool, check_video, provider_manager, 
download_best_subtitles, download_subtitles,
  File "/usr/lib/python3/dist-packages/subliminal/api.py", line 13, in 
from .subtitle import compute_score, get_subtitle_path
  File "/usr/lib/python3/dist-packages/subliminal/subtitle.py", line 7, in 

from guessit.matchtree import MatchTree
  File "/usr/lib/python3/dist-packages/guessit/__init__.py", line 99, in 

from guessit.plugins import transformers
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
222, in 
reload()
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
220, in reload
reload_options(all_transformers())
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
179, in all_transformers
return _extensions.objects()
  File "/usr/lib/python3/dist-packages/guessit/plugins/transformers.py", line 
111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 261, in map
raise NoMatches('No %s extensions found' % self.namespace)
stevedore.exception.NoMatches: No guessit.transformer extensions found

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: guessit
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated guessit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Sep 2019 00:57:32 +0200
Source: guessit
Binary: python3-guessit
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python3-guessit - library for guessing information from video filenames 
(Python 3)
Closes: 867862 881289 896202 896282 907821 936675
Changes:
 guessit (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Carl Suster ]
   * Add gbp config file
   * New upstream release (Closes: #867862, #881289, #907821):
 - Fix failed to import in Python 3 (Closes: #896282).
 - drop patches: upstream has been rewritten
   * Add myself to Uploaders
 .
   [ Thomas Goirand ]
   * Team upload.
   * Removed Python 2 support (Closes: #936675).
 - Fixed failed to import in Python 2 (Closes: #896202).
   * Fixed (build-)depends for this release.
   * Add

Bug#896202: marked as done (python-guessit: guessit fails to import)

Your message dated Thu, 19 Sep 2019 23:34:49 +
with message-id 
and subject line Bug#896202: fixed in guessit 3.0.0-1
has caused the Debian Bug report #896202,
regarding python-guessit: guessit fails to import
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.)


-- 
896202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-subliminal
Version: 1.1.1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-subliminal importing the module subliminal
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/subliminal/__init__.py", line 10, in 

from .api import (ProviderPool, check_video, provider_manager, 
download_best_subtitles, download_subtitles,
  File "/usr/lib/python2.7/dist-packages/subliminal/api.py", line 13, in 

from .subtitle import compute_score, get_subtitle_path
  File "/usr/lib/python2.7/dist-packages/subliminal/subtitle.py", line 7, in 

from guessit.matchtree import MatchTree
  File "/usr/lib/python2.7/dist-packages/guessit/__init__.py", line 99, in 

from guessit.plugins import transformers
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
222, in 
reload()
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
220, in reload
reload_options(all_transformers())
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
179, in all_transformers
return _extensions.objects()
  File "/usr/lib/python2.7/dist-packages/guessit/plugins/transformers.py", line 
111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 261, in 
map
raise NoMatches('No %s extensions found' % self.namespace)
stevedore.exception.NoMatches: No guessit.transformer extensions found

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: guessit
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated guessit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Sep 2019 00:57:32 +0200
Source: guessit
Binary: python3-guessit
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python3-guessit - library for guessing information from video filenames 
(Python 3)
Closes: 867862 881289 896202 896282 907821 936675
Changes:
 guessit (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Carl Suster ]
   * Add gbp config file
   * New upstream release (Closes: #867862, #881289, #907821):
 - Fix failed to import in Python 3 (Closes: #896282).
 - drop patches: upstream has been rewritten
   * Add myself to Uploaders
 .
   [ Thomas Goirand ]
   * Team upload.
   * Removed Python 2 support (Closes: #936675).
 - Fixed failed to import in Python 2 (Closes: #896202).
   * Fixed (build-)depends for this release.

Bug#881289: marked as done (guessit FTBFS: NoMatches: No guessit.transformer extensions found)

Your message dated Thu, 19 Sep 2019 23:34:49 +
with message-id 
and subject line Bug#881289: fixed in guessit 3.0.0-1
has caused the Debian Bug report #881289,
regarding guessit FTBFS: NoMatches: No guessit.transformer extensions found
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.)


-- 
881289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guessit
Version: 0.11.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes guessit FTBFS:

https://tests.reproducible-builds.org/debian/history/guessit.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guessit.html

...
==
ERROR: Failure: NoMatches (No guessit.transformer extensions found)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/__init__.py", 
line 99, in 
from guessit.plugins import transformers
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 222, in 
reload()
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 220, in reload
reload_options(all_transformers())
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 179, in all_transformers
return _extensions.objects()
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 252, in 
map
raise NoMatches('No %s extensions found' % self.namespace)
NoMatches: No guessit.transformer extensions found

--
Ran 1 test in 0.116s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: guessit
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated guessit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Sep 2019 00:57:32 +0200
Source: guessit
Binary: python3-guessit
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python3-guessit - library for guessing information from video filenames 
(Python 3)
Closes: 867862 881289 896202 896282 907821 936675
Changes:
 guessit (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Carl Suster ]
   * Add gbp config file
   * New upstream release (Closes: #867862, #881289, #907821):
 - Fix failed to import in Python 3 (Closes: #896282).

Bug#939754: gimp: Still happening

2019-09-19 Thread amgcampos

Package: gimp
Version: 2.10.8-2+b1
Followup-For: Bug #939754

Dear Maintainer,


- Just trying to open an image (any format), get a segmentation fault 
and gimp crashes.
- It is just impossible to work with Gimp right now, can't open images.
- Recently did a distro-upgrade to bullseye.
- Please find Gimp crash output bug information below:

Hoping to be helpfull. Regards

 == Gimp Output =
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6) 

using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 25863 - Thread 25863 #

[New LWP 25870]
[New LWP 25871]
[New LWP 25875]
[New LWP 25876]
[New LWP 25877]
[New LWP 25878]
[New LWP 25879]
[New LWP 25893]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffce23a9d90, fd=17) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7fa87449ae00 (LWP 25863) "gimp-2.10"  __libc_read 
(nbytes=256, buf=0x7ffce23a9d90, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fa871a52700 (LWP 25870) "gmain"  0x7fa8761f6edf in 
__GI___poll (fds=0x55e773a12180, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7fa872253700 (LWP 25871) "gdbus"  0x7fa8761f6edf in 
__GI___poll (fds=0x55e773a65a60, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7fa857612700 (LWP 25875) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fa856e11700 (LWP 25876) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7fa856610700 (LWP 25877) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7fa855e0f700 (LWP 25878) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7fa85560e700 (LWP 25879) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fa83700 (LWP 25893) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 9 (Thread 0x7fa83700 (LWP 25893)):
#0  0x7fa8761fc279 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fa8764cd95f in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8769780cd in  () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3  0x7fa8764ab89d in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa8762d1fb7 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140360604972800, 
5350031916341022875, 140724103977582, 140724103977583, 140360604972800, 
140360604969216, -5372972126464487269, -5372849380020170597}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#5  0x7fa87620149f in clone () at

Processed: fixed 881264 2.0.5-1

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

> fixed 881264 2.0.5-1
Bug #881264 [src:subliminal] subliminal: FTBFS and Debci failure with stevedore 
1.25.0-2
The source 'subliminal' and version '2.0.5-1' do not appear to match any binary 
packages
Marked as fixed in versions subliminal/2.0.5-1.
>
End of message, stopping processing here.

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

Bug#924757: anjuta: clean after build deletes libanjuta/interfaces/Makefile.am.gir which is not regenerated

Control: version -1 anjuta/2:3.28.0-5

Let's not delay the vala transition for this issue.

Thanks,
Jeremy

Bug#888547: marked as done (CVE-2017-1000190: XXE vulnerability resulting in SSRF, information disclosure, DoS, etc.)

Your message dated Thu, 19 Sep 2019 22:36:33 +
with message-id 
and subject line Bug#888547: fixed in simple-xml 2.7.1-3
has caused the Debian Bug report #888547,
regarding CVE-2017-1000190: XXE vulnerability resulting in SSRF, information 
disclosure, DoS, etc.
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.)


-- 
888547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simple-xml
Severity: important
Tags: security

CVE-2017-1000190 has been assigned to this bug in simple-xml:
https://github.com/ngallagher/simplexml/issues/18

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: simple-xml
Source-Version: 2.7.1-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated simple-xml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 00:12:59 +0200
Source: simple-xml
Architecture: source
Version: 2.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 888547
Changes:
 simple-xml (2.7.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed CVE-2017-1000190: XXE vulnerability (Closes: #888547)
   * Enabled the unit tests
   * Standards-Version updated to 4.4.0
Checksums-Sha1:
 3f9d5f4aaf05297faa25cc70641b8ab7ed9f821b 2111 simple-xml_2.7.1-3.dsc
 e08845258a56787bd7e17148bd571513fadd3cf3 5916 simple-xml_2.7.1-3.debian.tar.xz
 0ed5d2a718b518181f498b7887e1e7937ac36177 8565 
simple-xml_2.7.1-3_source.buildinfo
Checksums-Sha256:
 e261346f0594dfbc0b9126d1a96a5368cc7b0279d14e68bf0631dbe923f7cd4e 2111 
simple-xml_2.7.1-3.dsc
 88737dfb2507b74d1ade090c77c271eddc22853d37e596171eced73f4cce0e0b 5916 
simple-xml_2.7.1-3.debian.tar.xz
 0c07e048bbae67e353cc5f7c4ee4ad87e98396204be5c45f69ecd7783e3f5290 8565 
simple-xml_2.7.1-3_source.buildinfo
Files:
 5cf696abd7b86e801842dd85c18d9890 2111 java optional simple-xml_2.7.1-3.dsc
 7825a5aa7896ddbfd539ffa8d4c31fcf 5916 java optional 
simple-xml_2.7.1-3.debian.tar.xz
 62ec76103b0fc53a303dfd17d7c908e8 8565 java optional 
simple-xml_2.7.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl2D/YYSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsXkUP/3ENfTToUWjK1/xSvD5/kfTpeMcdq+RX
Q/CHaa1kkBM6IGOkYHmP+44BryS2KzQZunBwTONWJPxlM7pFDPIIG2vlWHgYS8eB
6z0Nx011arJH1egmPd8wK5w7GLFQ8Any0D4neETffl3H8ZQ4hKda6dpevNBsWwN1
zftWpPjcoq5v5Opp2oUv8TuB2rYkaeh8rA0INHM4pw+Kx0UJor51CjLBmMwx6w/H
kRlvAbRLmXdG9GZ+cSbaX2YEbQLM3h4U0DQxT6vrrKDBjwQKzia9NzmG9c9bVV3n
kOVsPYUfwm7bypqo/ubMqii/XalJmnFKQR7SwvtRxJnWrNp4M26yZkEaXOMLHA4S
Rxcr8TMJj986R451nRXOS0t3P5cnsb7Grsaj39qXO8Stah22KVcEL7RkFVhQDQtM
ThOF+Srsf/f1OS9KahOfp2psidoeo78Rphwbpi9CsCZyR+DGvDjIP3N1kyYZDMq+
TL/61JAZ22rDCqWsZSWxjoj3/uVDaqlMnbffNu54YqfT4XjfRleiMIHz+FFA+TQB
3Gs4TEFPMhmWeplG/eRWh9MlZBd21/gEHnNUm+eezoCBI8rEq/wsS1fQTfi0BkSO
qMPZFvFx1l3SXfscRA8z2stgHzxsh95arMazaK6/eDW6TII3nRL1MtrpGVWN4GHX
JNrOPWdoG9y9
=QNmo
-END PGP SIGNATURE End Message ---

Bug#924610: marked as done (libsdl2: Multiple security issues)

Your message dated Thu, 19 Sep 2019 22:08:35 +
with message-id 
and subject line Bug#924610: fixed in libsdl2 2.0.10+dfsg1-1
has caused the Debian Bug report #924610,
regarding libsdl2: Multiple security issues
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.)


-- 
924610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsdl2
Severity: grave
Tags: security

Hi,
a number of security issues were found in SDL, please see the following
links for references.

https://security-tracker.debian.org/tracker/CVE-2019-7638
https://security-tracker.debian.org/tracker/CVE-2019-7637
https://security-tracker.debian.org/tracker/CVE-2019-7636
https://security-tracker.debian.org/tracker/CVE-2019-7635
https://security-tracker.debian.org/tracker/CVE-2019-7578
https://security-tracker.debian.org/tracker/CVE-2019-7577
https://security-tracker.debian.org/tracker/CVE-2019-7576
https://security-tracker.debian.org/tracker/CVE-2019-7575
https://security-tracker.debian.org/tracker/CVE-2019-7574
https://security-tracker.debian.org/tracker/CVE-2019-7573
https://security-tracker.debian.org/tracker/CVE-2019-7572

Some bugs have links to upstream fixes, I think we can go ahead and
merge those. The others have proposed patches, but let's not rush
any upload and wait until these are properly reviewed/merged by
upstream.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libsdl2
Source-Version: 2.0.10+dfsg1-1

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated libsdl2 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, 19 Sep 2019 23:50:39 +0200
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Felix Geyer 
Closes: 892087 924610 939249
Changes:
 libsdl2 (2.0.10+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #939249)
 - Fixes warnings with -Wundef on non-x86 hosts. (Closes: #892087)
 - Fixes CVE-2019-7572, CVE-2019-7573, CVE-2019-7574, CVE-2019-7575,
   CVE-2019-7576, CVE-2019-7577, CVE-2019-7578, CVE-2019-7635,
   CVE-2019-7636, CVE-2019-7638 and CVE-2019-13626 (Closes: #924610)
   * Drop fix-cross-building-907711.patch, fixed upstream.
   * Bump SHLIBVER to 2.0.10.
   * Add support for nodoc build-profile.
   * Switch to debhelper compat level 12.
   * Cherry-pick upstream fix for CVE-2019-13616.
   * Mark autopkgtests as superficial.
Checksums-Sha1:
 0d8ad8c262f1f331083b19e06f4093cd72c00074 2823 libsdl2_2.0.10+dfsg1-1.dsc
 36a22d420157c9dad291d8a2ce27065ac5e0213d 2550516 
libsdl2_2.0.10+dfsg1.orig.tar.xz
 b4100b3207c9c7a67a9564a8dbfc474f6f95b7b3 17736 
libsdl2_2.0.10+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 e2252a09f6831a1ce3d10b1d6174b0f0f3602b128916d4df490ec6d3fa898fe1 2823 
libsdl2_2.0.10+dfsg1-1.dsc
 8a425d050c492cd0c352b522beea2c379938c4be0d47607db5b1b68f2ddc7fee 2550516 
libsdl2_2.0.10+dfsg1.orig.tar.xz
 5a0dc089fda3d01d342f5f38cafb65954c863eadfe3f97259aa14535c0cb13c5 17736 
libsdl2_2.0.10+dfsg1-1.debian.tar.xz
Files:
 ba6a204a4b7d58b5e4198bdc5095fb09 2823 libs optional libsdl2_2.0.10+dfsg1-1.dsc
 677763f073f2ce8e7600eabd0a938ef0 2550516 libs optional 
libsdl2_2.0.10+dfsg1.orig.tar.xz
 c69a3d75bb731e57bdce70645f1a67d6 17736 libs optional 
libsdl2_2.0.10+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAl2D+gcACgkQ/iLG/YMT
XUUjFBAAhIFjOJs/jO4BG2r3L9g//MyLqrB9UesjEbxOpxOYOLpQpmvLRU1MdN0R
MSF4445STPLN60s38xwWPVvpwFDvyDTll7cOaNyhU6RQbGqhbWq5d+GKoKZvVba6
+U/7DDCeilfs870FO6meHDCaMU8J4/5lMW3uXZi+hvicGkjCQUrG2RTOgk42a2GA
dm7uBw2eXblntEsgi8+X0uCdkyFCfiKCGldqfTaF36D+/ooEOCRh3Ok+/elrTbOD
sKP8+rnErZbjKVVBfHExy6REkWWc+piinPyf3lxtqxZPTg8d9z+MNaT26JNnGJb/
/BIbYXlDk015eQH64GYp+cQfukOdQHHdIc7/IUNKxTv2xWd7iBh3Pu8CcWXU9r+L
frv8hyB7QnDEGgi3t3odY6OVB8BY8XaMVclm1f7t9IXFr0MzaNUhGE3/CS1dKkeV

Bug#874868: marked as done ([fcitx] Future Qt4 removal from Buster)

Your message dated Thu, 19 Sep 2019 21:35:39 +
with message-id 
and subject line Bug#874868: fixed in fcitx 1:4.2.9.6-6
has caused the Debian Bug report #874868,
regarding [fcitx] Future Qt4 removal from Buster
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.)


-- 
874868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fcitx
Version: 1:4.2.9.1-6
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: fcitx
Source-Version: 1:4.2.9.6-6

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx 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, 19 Sep 2019 16:45:44 -0400
Source: fcitx
Architecture: source
Version: 1:4.2.9.6-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Closes: 874868
Changes:
 fcitx (1:4.2.9.6-6) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 + Bump Standards-Version to 4.4.0.
 + Bump debhelper compat to v12.
 - Drop everything related to Qt4. (Closes: #874868)
 + Unconditionally break package fcitx-module-quickphrase-editor
   since it should not appear in newer Debian system.
   * debian/compat: Dropped, not needed.
Checksums-Sha1:
 5147b3e2970328d4abfb308c1e04e9e71584241d 4338 fcitx_4.2.9.6-6.dsc
 f3487e58a7add46ff3b1d069c30275126aed3851 27116 fcitx_4.2.9.6-6.debian.tar.xz
 48ffbcbfbccfa9007583ae8de987112e541bbd59 30623 fcitx_4.2.9.6-6_amd64.buildinfo
Checksums-Sha256:
 d76b37e3179e302a0ce362674ade63ddd2a8ae562aed129b05f73ee00e647aef 4338 
fcitx_4.2.9.6-6.dsc
 522a11851e455d77033da3eaf5bca63740090c7182a1800eb09d28561bdf6e1d 27116 
fcitx_4.2.9.6-6.debian.tar.xz
 147edb505294dd58b18c1464d996b869919b74c553d6955b5169f659fd612172 30623 
fcitx_4.2.9.6-6_amd64.buildinfo
Files:
 63a37ff9b2386226a3cd2950fef5a9e2 4338 utils optional fcitx_4.2.9.6-6.dsc
 e83db55dcc7bcca1702887cd55cb298a 27116 utils optional 
fcitx_4.2.9.6-6.debian.tar.xz
 d7a94ab70127adb6acf9e1bcc4b67509 30623 utils optional 
fcitx_4.2.9.6-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#940703: [Debian-med-packaging] Bug#940703: augustus_3.3.3+dfsg-1_mips64el.changes REJECTED

2019-09-19 Thread Sascha Steinbiss

> On 19. Sep 2019, at 11:29, Aurelien Jarno  wrote:
> 
> Package: augustus
> Version: 3.3.3+dfsg-1
> Severity: serious
> 
> On 2019-09-18 23:34, Debian FTP Masters wrote:
>> augustus_3.3.3+dfsg-1_mips64el.deb: Built-Using refers to non-existing 
>> source package libbam-dev (= 0.1.19-4)
>> 
>> 
>> Mapping sid to unstable.
>> 
>> ===
>> 
>> Please feel free to respond to this email if you don't understand why
>> your files were rejected, or if you upload new files which address our
>> concerns.
>> 
>> 
>> 
> 
> The Built-Using field should use the source package (i.e.
> samtools-legacy), not the binary package.

Why? In the build am only using the static library from libbam-dev, not 
compiling source code from the samtools-legacy source package. Sorry, but this 
is a serious question as I am not sure what do do here.

7.8 of the policy requires that I have an ‘=‘ version relation on the package 
listed in ‘Built-Using' — I am not even sure how I would determine that for the 
source package since it’s not even used in the build?
Do I even need to provide a Built-Using here? Searching on code search for 
libbam-dev and samtools-legacy did not turn up a single case where a 
Built-Using was set.

Thanks
Sascha

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924359

signature.asc
Description: Message signed with OpenPGP

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-19 Thread Mark Hindley

On Thu, Sep 19, 2019 at 08:36:53PM +0100, Mark Hindley wrote:
> Control: tags -1 pending
> 
> Simon,
> 
> On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote:
> > I think I have finally got to the bottom of this. As you suspected it is 
> > apt's
> > invocation of dpkg. See #935910.
> 
> This has now been fixed in apt 1.9.4 (experimental).
> 
> I propose to add
> 
>  Breaks: apt (<< 1.9.4)
> 
> to the libelogind0 stanza in d/control.
> 
> In my testing with apt v1.9.4 system breakage is avoided. After the systemd
> prerm fails, dpkg returns immediately and apt is still available to fix the
> system.

Actually, Julian has just uploaded apt 1.8.4 with the same fix to unstable.

On irc he also said there was little point in adding the Breaks: as apt doesn't
rexec itself.

I suppose the only thing it might achieve is to ensure apt had been updated to
the latest version already.

Mark

Bug#940611: marked as done (fails to start because no wrapper missing)

Your message dated Thu, 19 Sep 2019 20:34:18 +
with message-id 
and subject line Bug#940611: fixed in beagle 5.1-190824+dfsg-2
has caused the Debian Bug report #940611,
regarding fails to start because no wrapper missing
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.)


-- 
940611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: beagle
Version: 5.0-180928+dfsg-1
Severity: serious

Hi,

beagle is written in java and shipped as /usr/share/beagle/beagle.jar
with 0644 permissions.

/usr/bin/beagle is a symlink to above jar. Starting it fails, as the jar
is not executable.

However, even if it would be executable, it woudln't work as jars are
not binaries to be executed directly in the first place. Something like
this should be used as /usr/bin/beagle instead of the symlink:

---snip---
#!/bin/sh

set -e

java -jar /usr/share/beagle/beagle.jar ${@}
---snap---

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: beagle
Source-Version: 5.1-190824+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated beagle 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: Tue, 17 Sep 2019 22:52:54 +0200
Source: beagle
Architecture: source
Version: 5.1-190824+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 940611
Changes:
 beagle (5.1-190824+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Baumann ]
   * Provide wrapper script instead of symlinks to JARs
 Closes: #940611
 .
   [ Andreas Tille ]
   * Remove obsolete fields Name, Contact from debian/upstream/metadata.
 .
   [ Dylan Aïssi ]
   * Fix autopkgtest tests.
Checksums-Sha1:
 b7e847e2c2a8e01c756e791b9d3c514c98ec71fd 2151 beagle_5.1-190824+dfsg-2.dsc
 b060acbc14069bdd130095006817f83b79fcba39 1355480 
beagle_5.1-190824+dfsg-2.debian.tar.xz
 6411ba80b3db933555fedf496a24f2afc52d846d 13107 
beagle_5.1-190824+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 eb72c632007af90b88e1d4208150f1e5c857cc8c352160514827261aa7b0b922 2151 
beagle_5.1-190824+dfsg-2.dsc
 35bc7d93bd80ee2b06fd86014d4d53829221fea302be760c6a3b41dc7fb7f9fd 1355480 
beagle_5.1-190824+dfsg-2.debian.tar.xz
 42c67d191fda4f17b7d0de7ea0a9e43e2c6a2fbbf58cf8249a5ccb8155385c71 13107 
beagle_5.1-190824+dfsg-2_amd64.buildinfo
Files:
 1865088d8e1f1d77a27836a90bcc09e6 2151 science optional 
beagle_5.1-190824+dfsg-2.dsc
 c68dcead3c09e97b580b4459181eafe9 1355480 science optional 
beagle_5.1-190824+dfsg-2.debian.tar.xz
 34fdcd65485f74eca8b72863f7a555d5 13107 science optional 
beagle_5.1-190824+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl2D3AgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH6lw//T7zPsYt9HRXCZhoIODBRJCelsDqrpAP6
Zlp769xlGVhuPQRAQX8fWkl6RBQg29LYy6hSfhHixCSc1WJ5GtmXapLi908SgeS6
a3a9uGoar6WV4he8Mg439RPxv89IzVbfiXGrmp0pXI/vftu6+Nm0Mhg5oTlDqery
AH66Awo+bX72ErMgD6Y5hybIbILng3+/EiI/lr4F2mLYBBjNmOWzJDrdIh8K1QxU
nXCyeqLyXYFfFCJgABggaM6Z3hZcuGSns01my7KE4IHSP3f3cuKFeSAKnnEe+kKJ
p8wkVI9NH+gPIwQtfx1A5cPC5vAT4B8D4UfvgC6Gov0fWKLmcNZybQnTVcxG4lZH
+d8Pmw/3vshRY4RgWmUV5GWfiWsM4Yg24URGebcmeGvAcVPzeRNTTS4Nbg8DwPSE
v4Hk7KdLQkzCuD1AaMxim6DYgYi9+E2qkGmBffJAJIr9z2RwEuwsUFUynEsNOszl
ijTh1m1QIJZc6r0nuYSlJnKXAPEoPqnkWcJt+lCQVGoM5Zj5YtpMe3N66BlaEdig
SwBWDYq6wrHIVoLFxwU9fLitZMT48uAa6SpD6Sr/S+rTc7LPC2KdTUcDp2ed/DsU
XdiKV9q9QmteR/fQZDZMA/EO4pRHpWM4Z5Vm3woNmBBfeyq0YqV9gcs0vDdZORed
0XgI64seyss=
=w3EN
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package imapfilter

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

> #
> # bts-link upstream status pull for source package imapfilter
> # 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 #939702 (http://bugs.debian.org/939702)
> # Bug title: imapfilter: CVE-2016-10937: does not validate hostname
> #  * https://github.com/lefcha/imapfilter/issues/142
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 939702 + fixed-upstream
Bug #939702 [imapfilter] imapfilter: CVE-2016-10937: does not validate hostname
Added tag(s) fixed-upstream.
> usertags 939702 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 939702 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#940679: pandas: FTBFS on amd64 - TestDatetimelikeSubtype::test_astype_category[index3] crash

2019-09-19 Thread Rebecca N. Palmer


Control: retitle -1 pandas: random test crashes

You're right that there are multiple issues here.

--- Random test crashes (this bug):

tests/indexes/interval/test_astype.py::TestDatetimelikeSubtype::test_astype_category[index3] 
on amd64; worked when retried, also works here
tests/reshape/test_tile.py::TestDatelike::test_qcut_nat[timedelta64[ns]] 
on mips64el; worked when retried


Only seen in -6, but given their intermittency this isn't proof that 
they're new.  If they are new, they're probably changes in some 
dependency, as the actual -5 to -6 change is in a different test.  Not 
found in a search of upstream issues.


--- Bootstrap issue (arch:all BD-Uninstallable):

python3-pandas is arch:all (so last successfully built in -4), and is no 
longer in the sid Packages list at all.  (I don't know if this always 
happens this quickly.)


arch:all pandas build-depends on itself via python3-statsmodels and 
python3-xarray.


These are used in some tests (which skip, not fail, if they are not 
available), and some documentation examples (which leave error messages 
in the documentation, but don't fail the build).


Hence, a solution to this is to drop those build-dependencies for one 
upload.


--- Failure with statsmodels 0.9:

This looks like something that should actually be fixed in statsmodels, 
not worked around in a pandas test, as it can also break actual use:


https://github.com/statsmodels/statsmodels/issues/4772
https://github.com/statsmodels/statsmodels/pull/4963/commits/064c5c3c59946fc702880b7fbda0e0b81a1fe30c



Hence, I plan to upload (but haven't yet tested):
pandas
- Revert the -6 patch and skip the test instead
- Temporarily drop statsmodels+xarray build-dependencies
- Add xarray autopkgtest-dependency
statsmodels
- Apply the above upstream patch

I also plan to investigate what causes these test crashes, but this may 
be hard if I can't reproduce them.

Processed: Re: Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

Processing control commands:

> tags -1 pending
Bug #934491 [libelogind0] libelogind0: failing to switch from systemd to 
sysvinit-core/elogind results in libsystemd.so.0 disappearing
Added tag(s) pending.

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

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-19 Thread Mark Hindley

Control: tags -1 pending

Simon,

On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote:
> I think I have finally got to the bottom of this. As you suspected it is apt's
> invocation of dpkg. See #935910.

This has now been fixed in apt 1.9.4 (experimental).

I propose to add

 Breaks: apt (<< 1.9.4)

to the libelogind0 stanza in d/control.

In my testing with apt v1.9.4 system breakage is avoided. After the systemd
prerm fails, dpkg returns immediately and apt is still available to fix the
system.

Are you happy with this?

Mark

Processed: Re: Bug#940679: pandas: FTBFS on amd64 - TestDatetimelikeSubtype::test_astype_category[index3] crash

Processing control commands:

> retitle -1 pandas: random test crashes
Bug #940679 [src:pandas] pandas: FTBFS on amd64 - 
TestDatetimelikeSubtype::test_astype_category[index3] crash
Changed Bug title to 'pandas: random test crashes' from 'pandas: FTBFS on amd64 
- TestDatetimelikeSubtype::test_astype_category[index3] crash'.

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

Processed: fonttools breaks ufolib2 autopkgtest: cannot import name 'PY3' from 'fontTools.misc.py23

Processing control commands:

> found -1 fonttools/4.0.0-1
Bug #940795 [src:fonttools, src:ufolib2] fonttools breaks ufolib2 autopkgtest: 
cannot import name 'PY3' from 'fontTools.misc.py23
Marked as found in versions fonttools/4.0.0-1.
> found -1 ufolib2/0.3.2+dfsg1-1
Bug #940795 [src:fonttools, src:ufolib2] fonttools breaks ufolib2 autopkgtest: 
cannot import name 'PY3' from 'fontTools.misc.py23
Marked as found in versions ufolib2/0.3.2+dfsg1-1.

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

Bug#940795: fonttools breaks ufolib2 autopkgtest: cannot import name 'PY3' from 'fontTools.misc.py23

2019-09-19 Thread Paul Gevers

Source: fonttools, ufolib2
Control: found -1 fonttools/4.0.0-1
Control: found -1 ufolib2/0.3.2+dfsg1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of fonttools the autopkgtest of ufolib2 fails in
testing when that autopkgtest is run with the binary packages of
fonttools from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
fonttools  from testing4.0.0-1
ufolib2from testing0.3.2+dfsg1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of fonttools to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? By the way, the version of
ufolib2 in unstable is failing for a different reason.

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

Paul

[1] https://qa.debian.org/excuses.php?package=fonttools

https://ci.debian.net/data/autopkgtest/testing/amd64/u/ufolib2/2990429/log.gz

Testing with python3.7:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ufoLib2/__init__.py", line 3, in

from ufoLib2.objects import Font
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/__init__.py",
line 4, in 
from ufoLib2.objects.font import Font
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/font.py", line 9,
in 
from ufoLib2.objects.info import Info
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/info.py", line 4,
in 
from ufoLib2.types import (
  File "/usr/lib/python3/dist-packages/ufoLib2/types.py", line 2, in

from fontTools.misc.py23 import PY3
ImportError: cannot import name 'PY3' from 'fontTools.misc.py23'
(/usr/lib/python3/dist-packages/fontTools/misc/py23.py)



signature.asc
Description: OpenPGP digital signature

Bug#940679: pandas: FTBFS on amd64 - TestDatetimelikeSubtype::test_astype_category[index3] crash

2019-09-19 Thread Gianfranco Costamagna

Hello,
> 1) create an amd64 sid chroot
> 2) install python3-pandas there
> 3) install build-dependencies
> 4) dpkg-buildpackage -A
> 5) sign & upload
> 
> after the package is installed, a source-only upload is required to let the 
> migration happen, since arch:all binNMUs are not a thing (yet).


I did the above, without the "upload" part, so I can just upload in case you 
need help or you don't have a deb file handy (or machine capable enough)

Also, I would like to mention a problem that sometimes occurs (e.g. it happened 
on amd64, mips64el and some port machine)

../debian/tmp/usr/lib/python3/dist-packages/pandas/tests/reshape/test_tile.py::TestDatelike::test_qcut_nat[timedelta64[ns]]
 Segmentation fault

Graham suggests that might be related to some particular time in the day, e.g. 
a test that fails when starts on day=x and ends on day=x+1 or something 
similar...
Do you have any idea?
I retried the builds and they seems ok now but the problem is still there

G.

Bug#935109: marked as done (hwinfo: FTBFS on x32: mdt.c:20:10: fatal error: x86emu.h: No such file or directory)

Your message dated Thu, 19 Sep 2019 16:34:02 +
with message-id 
and subject line Bug#935109: fixed in hwinfo 21.67-1.1
has caused the Debian Bug report #935109,
regarding hwinfo: FTBFS on x32: mdt.c:20:10: fatal error: x86emu.h: 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.)


-- 
935109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hwinfo
Version: 21.67-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

[…]
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O2 -Wall -Wno-pointer-sign -pipe -g   
-I/<>/src/hd -O2 -Wall -Wno-pointer-sign -pipe -g -fPIC  
-I../src/hd -O2 -Wall -Wno-pointer-sign -pipe -g -fPIC  -I../../src/hd 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Lsrc -Lsrc -Lsrc mdt.c
mdt.c:20:10: fatal error: x86emu.h: No such file or directory
 #include 
  ^~
compilation terminated.
[…]

I’m working on a patch.
--- End Message ---
--- Begin Message ---
Source: hwinfo
Source-Version: 21.67-1.1

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

Debian distribution maintenance software
pp.
Thorsten Glaser  (supplier of updated hwinfo 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: SHA384

Format: 1.8
Date: Mon, 09 Sep 2019 17:39:10 +0200
Source: hwinfo
Architecture: source
Version: 21.67-1.1
Distribution: unstable
Urgency: low
Maintainer: Sebastien Badia 
Changed-By: Thorsten Glaser 
Closes: 935109
Changes:
 hwinfo (21.67-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add x32 to list of architectures needing libx86emu-dev (Closes: #935109)
Checksums-Sha1:
 4f263e1aa5272a99b1f796a599a8d255ea105e48 2164 hwinfo_21.67-1.1.dsc
 c5894563eed652730858d64467dad97db57246a5 18708 hwinfo_21.67-1.1.debian.tar.xz
Checksums-Sha256:
 7f0cd1a73a7959d0f10f1d303ce2a4185233d8869be799bb9cd17fadb2d4afe5 2164 
hwinfo_21.67-1.1.dsc
 5eedf747a44d5b0b8ef8223b43b3ba69e72cd4ce25c5b2c612aa1967d4a8811c 18708 
hwinfo_21.67-1.1.debian.tar.xz
Files:
 d611534c134c5e79863d4e069204801e 2164 admin optional hwinfo_21.67-1.1.dsc
 8b388e4d64dd60cc2a8e3b0746f576f1 18708 admin optional 
hwinfo_21.67-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJddnNEAAoJEHa1NLLpkAfgr2cP/jU71XXXYE9e957ZfEVF8t/3
vIAljfxykDnhfYFNVlmPCzGMS7BnMbq+cccVlRGHAtYN2LCOdsByCFO50PeoRowK
JEN8bvBbfhDOrK4NUhMhjNwboJHNbxMTblX4vlQxMRWH8ebjWbch13LDJjWpSNO6
BwCTSl9etDKQtyHLsqPWtSkubHB9sUQnECuidLw7KktG5EWv+G4eC1uwVKCS9k2o
dv2cBahop5/2cGomzXk7vOufMuXI0rhkQpYZJmkSfGOpAEVxuF9bxaCL4s8jtB9g
jfWe/yrlUSpGLSkBu+w12rz4uR8cbwgRcdqNUM4fLknZvx06D5+Iwt3ykjGmDgNR
sE1z1w6rorTz5FAsevFtBASYt1PiyikMZFFlipsQvqriyNX7eWg8Y6abvTFoNMkS
JUFqUqi2y4HR19B2Yk+Rv70z6EgN1InILVKYJD7ZM5RmFkR0GbvTWPLSt3Q+pixr
cinSIZVLrgJD7eFpGE+Af2tP/6sgXG7qjeLWfOwvTVThs9LmLLABd7NWY8DdhFHD
qkTUeG1lvOJkSFTvwgnwyFpz4QvcvFfe7qCPA2ReJLBYRlf7TLxWX6LBb5S2z+D/
ia564Q0w1Wflfb+uCf6VcqLMYq5VQmLrHg8MKKvDCQlOAGC6LIuSnyGxfi9k/VTk
NhhTnl6mlISbWCzTm82a
=DO0y
-END PGP SIGNATURE End Message ---

Bug#916026: marked as done (bootchart2 FTBFS with glibc 2.28)

Your message dated Thu, 19 Sep 2019 15:34:00 +
with message-id 
and subject line Bug#916026: fixed in bootchart2 0.14.4-3.1
has caused the Debian Bug report #916026,
regarding bootchart2 FTBFS with glibc 2.28
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.)


-- 
916026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid

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

...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47: warning: implicit declaration of function 
'makedev' [-Wimplicit-function-declaration]
  if (mknod (TMPFS_PATH "/kmsg", S_IFCHR|0666, makedev(1, 11)) < 0) {
   ^~~
...
cc -g -Wall -O0  -pthread -Icollector -o bootchart-collector 
collector/collector.o collector/output.o collector/tasks.o 
collector/tasks-netlink.o collector/dump.o
/usr/bin/ld: collector/collector.o: in function `enter_environment':
/build/1st/bootchart2-0.14.4/collector/collector.c:633: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:39: bootchart-collector] Error 1
--- End Message ---
--- Begin Message ---
Source: bootchart2
Source-Version: 0.14.4-3.1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated bootchart2 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: Wed, 11 Sep 2019 10:19:53 -0400
Source: bootchart2
Architecture: source
Version: 0.14.4-3.1
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Boyuan Yang 
Closes: 916026
Changes:
 bootchart2 (0.14.4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control:
 + Bump Standards-Version to 4.4.0.
 + Update Vcs-* fields to use git package repo under Salsa Debian
   group.
 + Use secure URI in homepage field.
   * debian/patches: Add patch 0006 from upstream to fix FTBFS against
 glibc 2.28. (Closes: #916026)
   * debian/watch: Correctly monitor GitHub upstream.
   * debian/copyright:
 + Use secure URI.
 - Delete fields for missing files.
   * debian/bootchart2.lintian-overrides: Add lintian override for
 init.d-script-depends-on-all-virtual-facility (suppress warning
 for now).
Checksums-Sha1:
 721adc0b7b91cc46eac8cba8b19641340b43a80c 2020 bootchart2_0.14.4-3.1.dsc
 9723f91cd1744413e416396f1bfc64137fabac36 7340 
bootchart2_0.14.4-3.1.debian.tar.xz
 6c02f3da0d4afbab5242901d66414ac177732778 6560 
bootchart2_0.14.4-3.1_amd64.buildinfo
Checksums-Sha256:
 d7206723c3018056f5671f614df2b42663f55fe2c52c6c3e52362265d07588bc 2020 
bootchart2_0.14.4-3.1.dsc
 c53575583b8d00292a155b62c9e6a80779065ce9f0a8e02e4b1fd8b8a7481239 7340 
bootchart2_0.14.4-3.1.debian.tar.xz
 41d439e4d4a9cc2b68b094a49749b2687bd5c0b7972166c72d08460fc57d80e8 6560 
bootchart2_0.14.4-3.1_amd64.buildinfo
Files:
 ec862a3eec7b1af6554672507b24b358 2020 utils optional bootchart2_0.14.4-3.1.dsc
 b18718081bfc7cb554b9e67def057a78 7340 utils optional 
bootchart2_0.14.4-3.1.debian.tar.xz
 404071f68737518d83edebbba327fc64 6560 utils optional 
bootchart2_0.14.4-3.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl15BEAACgkQwpPntGGC
Ws62VA/7BvFmifkLZAXXe/Cdtg95wU7Al3C6VorlCuGsoplu5vzMBoXHFsw7Qc35
MeDYWNAr3346Ez/1JVE3i5DzZz8twVAFgdZjT7Jft6MTzRWJNsFc/U3INYUlMwLY
NMqV84TXOxqsZlnjfaGpBJ4xTNsHu8TbZqK5oV6TxuDQXa94fghtDASA2xt5GiX3
moT6eBy6Kg/3Sq7JDhypJ5YnhF4xEHXTZbF9mwBmzUaTd3NpGQxy3+cR47HJa8Mj
ZcLVLsrxo7X9/4VEJ8YLNZfBdhGWmsP6SCWYhfe2N0HjGifERbYdxoL3l55PaB0n
gS/gAvCcBGe27UqPtkmGxLv5iThH+4IdyiRY8aZO+yuFW7radZs9QYhBIUGmbN21
OtocBR2DGZL27Uw2Ec5hbuc5u78PlPGZz5DYIM5psPMWU7JNB7cuh7Hm94ijVfu/
Ip4rROBIzWTaaLcww5v8TzGp5vqZIFsk9HGyB2ARzeWdbXFPpVvPM4IAukxRVK4z
i/2NEpf4mRIsj+61ldq+yddeUIEzA2L4BJZYwu/UUDM3G1F66wG3iAzplkBU/WsY

Bug#940611: fails to start because no wrapper missing

Hi Dylan,

On Thu, Sep 19, 2019 at 05:08:28PM +0200, Dylan Aïssi wrote:
> Le mar. 17 sept. 2019 à 23:08, Andreas Tille  a écrit :
> > Thanks for your bug report including the patch.  I've pushed it the the
> > packaging Git leaving the package for final inspection by Dylan.
> 
> Thanks both. I will update autopkgtest tests to use the wrapper.
> 
> @Andreas, I was too busy IRL and I let my gpg key expire. I have
> updated my key on the Debian server but I cannot upload any package
> until the next sync. Don't hesitate to upload any relevant changes.

Just ping me if you consider beagle ready in Git.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#940611: fails to start because no wrapper missing

2019-09-19 Thread Dylan Aïssi

Hi,

Le mar. 17 sept. 2019 à 23:08, Andreas Tille  a écrit :
> Thanks for your bug report including the patch.  I've pushed it the the
> packaging Git leaving the package for final inspection by Dylan.

Thanks both. I will update autopkgtest tests to use the wrapper.

@Andreas, I was too busy IRL and I let my gpg key expire. I have
updated my key on the Debian server but I cannot upload any package
until the next sync. Don't hesitate to upload any relevant changes.

Best,
Dylan

Bug#912077: Any chance to get libbiod compiling again?

2019-09-19 Thread Pjotr Prins

Just so you know, libbiod does not depend on undead. We imported the
relevant sources (a small subset).

On Thu, Sep 19, 2019 at 04:45:28PM +0200, Matthias Klumpp wrote:
> Am Do., 19. Sept. 2019 um 08:29 Uhr schrieb Andreas Tille
> :
> >
> > Hi Matthias,
> >
> > On Thu, Sep 19, 2019 at 12:49:54AM +0200, Matthias Klumpp wrote:
> > > > As I told you before:  I have no idea about meson.  It would be great if
> > > > we could get it working but if we restrict the package to those
> > > > architectures where it builds out of the box and save some manpower I
> > > > bet the world will keep on turning round.
> > >
> > > It's not just that. Also the build needs to be changed to respect
> > > Debian's compile flags, build a shared library and write a pkg-config
> > > file. All doable with Makefiles, but not really much fun. At that
> > > point just using Meson becomes easier.
> > > The package is team-maintained, right? In that case I may just give
> > > this a shot this weekend and get the biod package to build again. It
> > > shouldn't actually by hard to do at all (famous last words :P)
> >
> > Its team maintained and you are member of the team.  Just push whatever
> > you consider sensible.
> 
> I'll have a look, maybe at the weekend. This really shouldn't be
> difficult to solve.
> 
> > > > > Btw, if libundead has no users anymore, removing it completely may be
> > > > > a good idea - we don't need to maintain something that's dead and has
> > > > > no users.
> > > >
> > > > I was about to file a removal request to ftpmaster before you said in
> > > > your last mail that the former build issue might have been caused due
> > > > to the lack of libundead.  I would really love to get rid of unneeded
> > > > packages.
> > >
> > > Better check for reverse dependencies, but if there are none, I don't
> > > see a need to keep it.
> >
> > $ apt-cache rdepends libundead0
> > libundead0
> > Reverse Depends:
> >   libundead-dev
> >   sambamba
> >   libundead-dev
> >   libbiod0
> 
> Oh, it has more rdeps than just libbiod, in that case we probably need
> to keep it for a bit longer!
> 
> > > Undead is basically deprecated & removed D
> > > stdlib modules with zero or very little maintenance, so generally
> > > something a project wants to get rid of rather quickly anyway, and
> > > quite likely nothing worth keeping in Debian on its own.
> >
> > So I'll ask for removal since if I understood you correctly it will
> > go away from both projects above.
> 
> -- 
> I welcome VSRE emails. See http://vsre.info/Don't do that just yet!
> UndeaD is stuff removed from the D standard library for projects which
> didn't go ahead with removing the deprecated stuff to depend on. Those
> projects should move away from the deprecated code ASAP, but if they
> haven't, we need undeaD for them.
> (The undead library itself doesn't receive much maintenance though,
> that is true - there is usually a reason for why some things were
> removed from the srdlib ^^)
> 
> Cheers,
> Matthias

Bug#912077: Any chance to get libbiod compiling again?

2019-09-19 Thread Matthias Klumpp

Am Do., 19. Sept. 2019 um 08:29 Uhr schrieb Andreas Tille
:
>
> Hi Matthias,
>
> On Thu, Sep 19, 2019 at 12:49:54AM +0200, Matthias Klumpp wrote:
> > > As I told you before:  I have no idea about meson.  It would be great if
> > > we could get it working but if we restrict the package to those
> > > architectures where it builds out of the box and save some manpower I
> > > bet the world will keep on turning round.
> >
> > It's not just that. Also the build needs to be changed to respect
> > Debian's compile flags, build a shared library and write a pkg-config
> > file. All doable with Makefiles, but not really much fun. At that
> > point just using Meson becomes easier.
> > The package is team-maintained, right? In that case I may just give
> > this a shot this weekend and get the biod package to build again. It
> > shouldn't actually by hard to do at all (famous last words :P)
>
> Its team maintained and you are member of the team.  Just push whatever
> you consider sensible.

I'll have a look, maybe at the weekend. This really shouldn't be
difficult to solve.

> > > > Btw, if libundead has no users anymore, removing it completely may be
> > > > a good idea - we don't need to maintain something that's dead and has
> > > > no users.
> > >
> > > I was about to file a removal request to ftpmaster before you said in
> > > your last mail that the former build issue might have been caused due
> > > to the lack of libundead.  I would really love to get rid of unneeded
> > > packages.
> >
> > Better check for reverse dependencies, but if there are none, I don't
> > see a need to keep it.
>
> $ apt-cache rdepends libundead0
> libundead0
> Reverse Depends:
>   libundead-dev
>   sambamba
>   libundead-dev
>   libbiod0

Oh, it has more rdeps than just libbiod, in that case we probably need
to keep it for a bit longer!

> > Undead is basically deprecated & removed D
> > stdlib modules with zero or very little maintenance, so generally
> > something a project wants to get rid of rather quickly anyway, and
> > quite likely nothing worth keeping in Debian on its own.
>
> So I'll ask for removal since if I understood you correctly it will
> go away from both projects above.

-- 
I welcome VSRE emails. See http://vsre.info/Don't do that just yet!
UndeaD is stuff removed from the D standard library for projects which
didn't go ahead with removing the deprecated stuff to depend on. Those
projects should move away from the deprecated code ASAP, but if they
haven't, we need undeaD for them.
(The undead library itself doesn't receive much maintenance though,
that is true - there is usually a reason for why some things were
removed from the srdlib ^^)

Cheers,
Matthias

Bug#940774: rakudo: upgrade issues

2019-09-19 Thread gregor herrmann

Package: rakudo
Version: 2019.07.1-3
Severity: serious
Justification: fails to upgrade, leaves package in broken state

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This does not look good when upgrading from 2018.12-5:

Preparing to unpack .../29-rakudo_2019.07.1-3_amd64.deb ...
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-tap-harness' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-tap-harness/perl6-tap-harness.p6deps' 
not owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-tap-harness/lib' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-tap-harness/lib/TAP.pm' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-tap-harness/META6.json' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-readline' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-readline/lib' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-readline/lib/Readline.pm' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-readline/perl6-readline.p6deps' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-readline/META6.json' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef' not owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources/scripts' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/perl5tar.pl' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32http.ps1' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32unzip.ps1' 
not owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/resources/config.json' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Extract.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/LocalCache.pm6' 
not owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/Ecosystems.pm6' 
not owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/MetaCPAN.pm6' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils' not owned by package 
'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/URI.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/FileSystem.pm6' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemInfo.pm6' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemQuery.pm6' not 
owned by package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Config.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Install.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Fetch.pm6' not owned by 
package 'rakudo:amd64'
dpkg-maintscript-helper: error: file 
'/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/CLI.pm6' not owned by

Processed: Re: Bug#940728: pybuild does not copy all files in setup.py install

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

> severity 940728 normal
Bug #940728 [dh-python] pybuild does not copy all files in setup.py install
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#940596: marked as done (upgrading libjbig2dec0 broke mupdf)

Your message dated Thu, 19 Sep 2019 15:50:51 +0200
with message-id <20190919135050.GA10913@jcristau-z4>
and subject line Re: Bug#940596: upgrading libjbig2dec0 broke mupdf
has caused the Debian Bug report #940596,
regarding upgrading libjbig2dec0 broke mupdf
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.)


-- 
940596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mupdf
Version: 1.15.0+ds1-1+b1
Severity: grave

After upgrading libjbig2dec0 from 0.16-1 to 0.16+20190905-2 it does not 
start anymore:

md@bongo:~$ mupdf
/usr/lib/mupdf/mupdf-x11: symbol lookup error: /usr/lib/mupdf/mupdf-x11: 
undefined symbol: jbig2_ctx_new
[Exit 127]
md@bongo:~$ nm -D /usr/lib/x86_64-linux-gnu/libjbig2dec.so.0 | grep 
jbig2_ctx_new
3a40 T jbig2_ctx_new_imp
md@bongo:~$

-- 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.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mupdf depends on:
ii  libc62.29-1
ii  libfreetype6 2.9.1-4
ii  libharfbuzz0b2.6.1-3
ii  libjbig2dec0 0.16+20190905-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libopenjp2-7 2.3.0-2
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  zlib1g   1:1.2.11.dfsg-1+b1

mupdf recommends no packages.

Versions of packages mupdf suggests:
pn  mupdf-tools  

-- no debconf information

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, Sep 17, 2019 at 05:47:03PM +0200, Marco d'Itri wrote:
> Package: mupdf
> Version: 1.15.0+ds1-1+b1
> Severity: grave
> 
> After upgrading libjbig2dec0 from 0.16-1 to 0.16+20190905-2 it does not 
> start anymore:
> 
> md@bongo:~$ mupdf
> /usr/lib/mupdf/mupdf-x11: symbol lookup error: /usr/lib/mupdf/mupdf-x11: 
> undefined symbol: jbig2_ctx_new
> [Exit 127]
> md@bongo:~$ nm -D /usr/lib/x86_64-linux-gnu/libjbig2dec.so.0 | grep 
> jbig2_ctx_new
> 3a40 T jbig2_ctx_new_imp
> md@bongo:~$
> 
Latest libjbig2dec0 (0.16+20190905-3) should fix this.

Cheers,
Julien--- End Message ---

Processed: reassign 940555 to gnome-software, forcibly merging 940204 940467, tagging 940688

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

> reassign 940555 gnome-software 3.30.6-5
Bug #940555 [gnome logiciels (gnome softwares)] Debian 10 Buster - gnome 
logiciels (gnome softwares) v. 3.30.6
Warning: Unknown package 'logiciels'
Warning: Unknown package 'softwares'
Bug reassigned from package 'gnome logiciels (gnome softwares)' to 
'gnome-software'.
No longer marked as found in versions 3.30.6.
Ignoring request to alter fixed versions of bug #940555 to the same values 
previously set
Bug #940555 [gnome-software] Debian 10 Buster - gnome logiciels (gnome 
softwares) v. 3.30.6
Marked as found in versions gnome-software/3.30.6-5.
> forcemerge 940204 940467
Bug #940204 {Done: Andreas Beckmann } [bed] bed desktop file 
is missing the additional category 'ConsoleOnly'
Warning: Unknown package 'bed'
Bug #940204 {Done: Andreas Beckmann } [bed] bed desktop file 
is missing the additional category 'ConsoleOnly'
Warning: Unknown package 'bed'
There is no source info for the package 'bed' at version '0.2.27' with 
architecture ''
Unable to make a source version for version '0.2.27'
There is no source info for the package 'bed' at version '3.0.0' with 
architecture ''
Unable to make a source version for version '3.0.0'
Marked as found in versions 3.0.0.
Warning: Unknown package 'bed'
Bug #940467 {Done: Andreas Beckmann } [bed] Some Installation 
failure and beds desktop file is missing the additional category 'ConsoleOnly'
Warning: Unknown package 'bed'
Severity set to 'normal' from 'grave'
Warning: Unknown package 'bed'
Warning: Unknown package 'bed'
There is no source info for the package 'bed' at version '0.2.27' with 
architecture ''
Unable to make a source version for version '0.2.27'
There is no source info for the package 'bed' at version '3.0.0' with 
architecture ''
Unable to make a source version for version '3.0.0'
Marked as found in versions 0.2.27.
Warning: Unknown package 'bed'
Merged 940204 940467
Warning: Unknown package 'bed'
> tags 940688 + sid bullseye
Bug #940688 [mcomix] mcomix: Python 3 fork available
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: correct bug #

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

> block 940720 by 940728
Bug #940720 [src:python-asdf] python-asdf breaks gwcs autopkgtest: No module 
named 'asdf.extern'
940720 was not blocked by any bugs.
940720 was not blocking any bugs.
Added blocking bug(s) of 940720: 940728
> thanks
Stopping processing here.

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

Processed: notfound 933375 in 0.4.159, reassign 921019 to src:linux, fixed 921019 in 5.2.6-1 ..., tagging 934095 ...

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

> # fix bug metadata to allow archival
> notfound 933375 0.4.159
Bug #933375 {Done: Jonas Smedegaard } [cdbs] cdbs: breaks with 
debhelper compat level 12 (dh_clean -k was deprecated in favor of dh_prep)
No longer marked as found in versions cdbs/0.4.159.
> reassign 921019 src:linux
Bug #921019 {Done: Ben Hutchings } [linux-image-arm64] 
arm64: Please provide sound modules for Allwinner A64 based systems
Bug reassigned from package 'linux-image-arm64' to 'src:linux'.
No longer marked as found in versions linux-latest/100.
No longer marked as fixed in versions linux/5.2.6-1.
> fixed 921019 5.2.6-1
Bug #921019 {Done: Ben Hutchings } [src:linux] arm64: 
Please provide sound modules for Allwinner A64 based systems
Marked as fixed in versions linux/5.2.6-1.
> reassign 932722 src:linux
Bug #932722 {Done: Ben Hutchings } [linux-image-amd64] 
Please add CONFIG_CRYPTO_ZSTD
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-latest/105.
No longer marked as fixed in versions linux/5.2.6-1.
> fixed 932722 5.2.6-1
Bug #932722 {Done: Ben Hutchings } [src:linux] Please add 
CONFIG_CRYPTO_ZSTD
Marked as fixed in versions linux/5.2.6-1.
> tags 934095 + experimental
Bug #934095 {Done: Thomas Goirand } [python-os-testr] 
python-os-testr (build-)depends on cruft package.
Added tag(s) experimental.
> reassign 933569 postgresql-common
Bug #933569 {Done: Christoph Berg } [src:postgresql-11] 
postgresql: test failures with systemd 242-1
Bug reassigned from package 'src:postgresql-11' to 'postgresql-common'.
No longer marked as found in versions postgresql-11/11.4-1.
No longer marked as fixed in versions postgresql-common/204.
> fixed 933569 204
Bug #933569 {Done: Christoph Berg } [postgresql-common] 
postgresql: test failures with systemd 242-1
Marked as fixed in versions postgresql-common/204.
> notfixed 618033 2009-10
Bug #618033 {Done: Hilmar Preuße } [texlive-binaries] 
texlive-bin-2009: Missing -D_FILE_OFFSET_BITS=64 leads to files not opening 
(x86 /32bit)
No longer marked as fixed in versions texlive-bin/2009-10.
> reassign 909480 src:feersum 1.406-1
Bug #909480 {Done: Xavier Guimard } [libhttp-tiny-perl] 
HTTP::Tiny tries to reuse closed connections
Bug reassigned from package 'libhttp-tiny-perl' to 'src:feersum'.
No longer marked as found in versions libhttp-tiny-perl/0.070-1.
No longer marked as fixed in versions feersum/1.407-1.
Bug #909480 {Done: Xavier Guimard } [src:feersum] HTTP::Tiny 
tries to reuse closed connections
Marked as found in versions feersum/1.406-1.
> fixed 909480 1.407-1
Bug #909480 {Done: Xavier Guimard } [src:feersum] HTTP::Tiny 
tries to reuse closed connections
Marked as fixed in versions feersum/1.407-1.
> notfixed 913247 2.91-1
Bug #913247 {Done: Dmitry Bogatov } [sysvinit-utils] Please 
provide a C implementation of /lib/init/init-d-script
No longer marked as fixed in versions sysvinit/2.91-1.
> fixed 929654 0~20190709+git706d06c0-1
Bug #929654 {Done: Xavier } [node-unicode-12.0.0] Outdated 
node-unicode-property-value-aliases results in incomplete package rebuild
There is no source info for the package 'node-unicode-12.0.0' at version 
'0~20190709+git706d06c0-1' with architecture ''
Unable to make a source version for version '0~20190709+git706d06c0-1'
Marked as fixed in versions 0~20190709+git706d06c0-1.
> notfixed 929654 3.4.0+ds-1
Bug #929654 {Done: Xavier } [node-unicode-12.0.0] Outdated 
node-unicode-property-value-aliases results in incomplete package rebuild
There is no source info for the package 'node-unicode-12.0.0' at version 
'3.4.0+ds-1' with architecture ''
Unable to make a source version for version '3.4.0+ds-1'
No longer marked as fixed in versions 3.4.0+ds-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
618033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618033
909480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909480
913247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913247
921019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921019
929654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929654
932722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932722
933375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933375
933569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933569
934095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932865: python-qrtools: not installable: depends on python2 version of zbar

2019-09-19 Thread Boyuan Yang

Control: tags -1 + fixed-upstream
X-Debbugs-CC: paul...@debian.org

Upstream has merged python3 migration code. We should consider packaging it.

Thanks,
Boyuan Yang

On Fri, 13 Sep 2019 02:34:44 +0800 "Ying-Chun Liu (PaulLiu)" <
paul...@debian.org> wrote:
> Hi all,
> 
> 
> Unfortunately, I'm still using this app. Or not me cause I can use
> command line,
> 
> but I must keep this app running otherwise I'll be in trouble.
> 
> So I propose a merge request to the upstream that ports this app to python3.
> 
> 
> https://code.launchpad.net/~paulliu/qr-tools/python3/+merge/372711
> 
> Will do NMU for a patch maintained inside Debian if the upstream is
> really dead and don't want to accept or discuss my patch.
> 
> If the upstream accepts my patch then we can upgrade to latest upstream.
> 
> 
> Yours,
> Paul


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

Processed: Re: python-qrtools: not installable: depends on python2 version of zbar

Processing control commands:

> tags -1 + fixed-upstream
Bug #932865 [python-qrtools] python-qrtools: not installable: depends on 
python2 version of zbar
Added tag(s) fixed-upstream.

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

Bug#940728: pybuild does not copy all files in setup.py install

2019-09-19 Thread Ole Streicher

Package: dh-python
Version: 4.20190722
Severity: serious
Control: affects -1 src:python-asdf
Control: affects -1 src:python-can
Control: block 947020 by -1
X-Debbugs-Cc: umlae...@debian.org

Hi,

when I try to build the python-asdf package, some subdirectories are not
copied; namely `asdf/external`:

8<--
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /build/python-asdf-2.4.2/.pybuild/cpython3_3.7_asdf/build/asdf
[...]
8<--

The subdir `asdf/external` which is in the source is not created and not
filled during this process.

However, when I run `python3 setup.py build` or `pybuild --build`
manually, everything is correct:

8<--
$ python3 setup.py build -vvv
running build
running build_py
creating build
creating build/lib
creating build/lib/asdf
copying asdf/yamlutil.py -> build/lib/asdf
[...]
creating build/lib/asdf/extern
copying asdf/extern/RangeHTTPServer.py -> build/lib/asdf/extern
copying asdf/extern/__init__.py -> build/lib/asdf/extern
copying asdf/extern/atomicfile.py -> build/lib/asdf/extern
copying asdf/extern/decorators.py -> build/lib/asdf/extern
[...]
8<--

This was also reported on the debian-python mailing list:

https://lists.debian.org/debian-python/2019/09/msg00040.html

A similar problem was reported on the mailing list for the python-can
package (IOhannes put into cc, and set python-can as affected):

https://lists.debian.org/debian-python/2019/09/msg00071.html

Best regards

Ole

Processed (with 1 error): pybuild does not copy all files in setup.py install

Processing control commands:

> affects -1 src:python-asdf
Bug #940728 [dh-python] pybuild does not copy all files in setup.py install
Added indication that 940728 affects src:python-asdf
> affects -1 src:python-can
Bug #940728 [dh-python] pybuild does not copy all files in setup.py install
Added indication that 940728 affects src:python-can
> block 947020 by -1
Failed to set blocking bugs of 947020: Unable to read any bugs successfully.


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

Bug#940720: python-asdf breaks gwcs autopkgtest: No module named 'asdf.extern'

2019-09-19 Thread Ole Streicher

Hi Paul,

this is a problem of dh-python not copying everything during setup.py. See

https://lists.debian.org/debian-python/2019/09/msg00040.html

I will open a bug report for dh-python here.

Cheers

Ole

Bug#934185: libkscreenlocker5: fails to accept correct pin after entering pin less than 6 chars with libpam-poldi

2019-09-19 Thread Franklin, Jason

Greetings,

I worked through the problem here and submitted the following patch to
the upstream developers of the screen locker:

https://phabricator.kde.org/D23849

The patch was accepted by the team, and the screen locker is now fixed
for the next version.

Would it be possible to have this upstream commit cherry picked and
applied to this Debian package for an immediate fix?

-- 
Jason Franklin



signature.asc
Description: OpenPGP digital signature

Bug#940679: pandas: FTBFS on amd64 - TestDatetimelikeSubtype::test_astype_category[index3] crash

2019-09-19 Thread Gianfranco Costamagna

Hello,
On Thu, 19 Sep 2019 11:41:22 +0200 Graham Inggs  wrote:
> Hi Rebecca
> 
> On 2019/09/18 23:51, Rebecca N. Palmer wrote:
> > Was your local build on a different architecture, or must this be 
> > something random / hardware-or-environment-dependent / a very recent 
> > change in a build-dependency?
> 
> I first ran into a problem with the arch:all build of 0.23.3+dfsg-5 [1].
> 
> This seemed to be upstream issue #24088 [2], so I tested a src:all build 
> including the patch on barriere.debian.org.
> 
> This should have been caught by the autopkgtest, but I noticed that 
> python3-statsmodels was missing from the test dependencies.
> 
> After the build was successful on barriere, I uploaded with both changes.
> 
> At this point, I should have filed a bug against statsmodels to prevent 
> the migration of 0.9.0-5 to testing, but was expecting the pandas builds 
> to go smoothly.
> 
> I see 0.23.3+dfsg-6 was given back on amd64, and has just built 
> successfully.  I'll keep an eye on the arch:all build, and investigate 
> further if needed.

I think there is a chicken-and-egg problem now, on arch:all.

There should be a python3-pandas old binary around to satisfy the arch:all 
build-deps, but for some reasons it is not being picked up by the builders, and 
even in a local chroot.

apt-cache policy python3-pandas
python3-pandas:
  Installed: (none)
  Candidate: (none)
  Version table:

Fetched 377 kB in 2s (228 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package python3-pandas is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-pandas' has no installation candidate

My suggestion is:

1) create an amd64 sid chroot
2) install python3-pandas there
3) install build-dependencies
4) dpkg-buildpackage -A
5) sign & upload

after the package is installed, a source-only upload is required to let the 
migration happen, since arch:all binNMUs are not a thing (yet).

This should unblock the migration.

G.

Bug#940723: java-package requires libgtk-3-0 and libcairo-gobject2 to build java8 221

2019-09-19 Thread Santiago R.R.

Package: java-package
Version: 0.62
Severity: serious

Dear java-package maintainers,

When trying to build the deb package of jdk-8u221-linux-x64.tar.gz on a
clean sid pbuilder, I got the following errors:

…
dpkg-shlibdeps: error: cannot find library libgtk-3.so.0 needed by 
debian/oracle-java8-jdk/usr/lib/jvm/oracle-java8-jdk-amd64/jre/lib/amd64/libglassgtk3.so
 (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgdk-3.so.0 needed by 
debian/oracle-java8-jdk/usr/lib/jvm/oracle-java8-jdk-amd64/jre/lib/amd64/libglassgtk3.so
 (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libcairo-gobject.so.2 needed by 
debian/oracle-java8-jdk/usr/lib/jvm/oracle-java8-jdk-amd64/jre/lib/amd64/libglassgtk3.so
 (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
…
dpkg-shlibdeps: error: cannot continue due to the errors listed above
Note: libraries are not searched in other binary packages that do not have any 
shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to use -l.
…
dh_shlibdeps: Aborting due to earlier error
make[1]: *** [debian/rules:17: override_dh_shlibdeps] Error 255
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Installing libcairo-gobject2 and libgtk-3-0 makes make-jpkg happy.

Cheers,

 -- Santiago

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CO.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 java-package depends on:
ii  build-essential  12.8
ii  debhelper12.6.1
ii  dpkg-dev 1.19.7
ii  fakeroot 1.24-1
ii  libasound2   1.1.8-1
ii  libfontconfig1   2.13.1-2+b1
ii  libgl1-mesa-glx  19.1.6-1
ii  libgtk2.0-0  2.24.32-4
ii  libx11-6 2:1.6.7-1
ii  libxslt1.1   1.1.32-2.1
ii  libxtst6 2:1.2.3-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  unzip6.0-25

java-package recommends no packages.

Versions of packages java-package suggests:
pn  openjdk-7-jre  


signature.asc
Description: PGP signature

Bug#925670: marked as done (dlt-daemon: ftbfs with GCC-9)

Your message dated Thu, 19 Sep 2019 12:18:58 +
with message-id 
and subject line Bug#925670: fixed in dlt-daemon 2.18.4-0.1
has caused the Debian Bug report #925670,
regarding dlt-daemon: ftbfs with GCC-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
  |  ^~
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 39%] Linking C executable dlt-receive
cd /<>/obj-x86_64-linux-gnu/src/console && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/dlt-receive.dir/link.txt --verbose=1
[ 39%] Built target dlt-control
make -f src/examples/CMakeFiles/dlt-example-user.dir/build.make 
src/examples/CMakeFiles/dlt-example-user.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/examples 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/examples 
/<>/obj-x86_64-linux-gnu/src/examples/CMakeFiles/dlt-example-user.dir/DependInfo.cmake
 --color=
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu99  -Wl,-z,relro -rdynamic 
CMakeFiles/dlt-receive.dir/dlt-receive.c.o  -o dlt-receive 
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/lib: 
../lib/libdlt.so.2.18.0 -lrt -lpthread 
Scanning dependencies of target dlt-example-user
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/examples/CMakeFiles/dlt-example-user.dir/build.make 
src/examples/CMakeFiles/dlt-example-user.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 40%] Building C object 
src/examples/CMakeFiles/dlt-example-user.dir/dlt-example-user.c.o
cd /<>/obj-x86_64-linux-gnu/src/examples && /usr/bin/cc 
-DCONFIGURATION_FILES_DIR=\"/etc\" -DDLT_SYSTEMD_ENABLE 
-DDLT_SYSTEMD_JOURNAL_ENABLE -DDLT_USER_IPC_PATH=\"/tmp\" -DDLT_USE_IPv6 
-D_GNU_SOURCE -I/<> -I/<>/include/dlt 
-I/<>/src/shared -I/<>/src/core_dump_handler 
-I/<>/src/offlinelogstorage -I/<>/src/lib 
-I/<>/src/daemon -I/<>/src/console 
-I/<>/src/gateway -I/<>/systemd/3rdparty  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99   -Wall 
-Wextra -Wno-variadic-macros -Wno-strict-aliasing -o 
CMakeFiles/dlt-example-user.dir/dlt-example-user.c.o   -c 
/<>/src/examples/dlt-example-user.c
[ 41%] Building C object 
src/console/CMakeFiles/dlt-passive-node-ctrl.dir/dlt-control-common.c.o
cd /<>/obj-x86_64-linux-gnu/src/console && /usr/bin/cc 
-DCONFIGURATION_FILES_DIR=\"/etc\" -DDLT_SYSTEMD_ENABLE 
-DDLT_SYSTEMD_JOURNAL_ENABLE -DDLT_USER_IPC_PATH=\"/tmp\" -DDLT_USE_IPv6 
-D_GNU_SOURCE -I/<> -I/<>/include/dlt 
-I/<>/src/shared -I/<>/src/core_dump_handler 
-I/<>/src/offlinelogstorage -I/<>/src/lib 
-I/<>/src/daemon -I/<>/src/console 
-I/<>/src/gateway -I/<>/systemd/3rdparty  -g -O2

Processed: Re: dlt-daemon: ftbfs with GCC-9

Processing control commands:

> tags -1 patch pending
Bug #925670 [src:dlt-daemon] dlt-daemon: ftbfs with GCC-9
Added tag(s) pending and patch.

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

Bug#940720: python-asdf breaks gwcs autopkgtest: No module named 'asdf.extern'

2019-09-19 Thread Paul Gevers

Source: python-asdf
Control: found -1 python-asdf/2.4.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks regression
Control: affects -1 src:gwcs
Control: affects -1 src:sunpy

Dear maintainers,

With a recent upload of python-asdf the autopkgtest of gwcs fails in
testing when that autopkgtest is run with the binary packages of
python-asdf from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
python-asdffrom testing2.4.2-1
gwcs   from testing0.10.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems to me
that python-asdf is missing files it expects internally. The same issue
can be seen in the autopkgtest of python-asdf itself, and of sunpy.

Currently this regression is blocking the migration of python-asdf to
testing [1]. Can you please investigate the situation?

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-asdf

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gwcs/2984900/log.gz


 ERRORS

_ ERROR collecting tags/tests/test_selector.py
_
ImportError while importing test module
'/usr/lib/python3/dist-packages/gwcs/tags/tests/test_selector.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/gwcs/tags/__init__.py:4: in 
from .wcs import *
/usr/lib/python3/dist-packages/gwcs/tags/wcs.py:5: in 
from asdf import yamlutil
/usr/lib/python3/dist-packages/asdf/__init__.py:36: in 
from .asdf import AsdfFile, open_asdf
/usr/lib/python3/dist-packages/asdf/asdf.py:18: in 
from . import block
/usr/lib/python3/dist-packages/asdf/block.py:20: in 
from .compat.numpycompat import NUMPY_LT_1_7
/usr/lib/python3/dist-packages/asdf/compat/numpycompat.py:1: in 
from ..util import minversion
/usr/lib/python3/dist-packages/asdf/util.py:15: in 
from .extern.decorators import add_common_docstring
E   ModuleNotFoundError: No module named 'asdf.extern'
___ ERROR collecting tags/tests/test_wcs.py

ImportError while importing test module
'/usr/lib/python3/dist-packages/gwcs/tags/tests/test_wcs.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/gwcs/tags/__init__.py:4: in 
from .wcs import *
/usr/lib/python3/dist-packages/gwcs/tags/wcs.py:5: in 
from asdf import yamlutil
/usr/lib/python3/dist-packages/asdf/__init__.py:36: in 
from .asdf import AsdfFile, open_asdf
/usr/lib/python3/dist-packages/asdf/asdf.py:18: in 
from . import block
/usr/lib/python3/dist-packages/asdf/block.py:20: in 
from .compat.numpycompat import NUMPY_LT_1_7
/usr/lib/python3/dist-packages/asdf/compat/numpycompat.py:1: in 
from ..util import minversion
/usr/lib/python3/dist-packages/asdf/util.py:15: in 
from .extern.decorators import add_common_docstring
E   ModuleNotFoundError: No module named 'asdf.extern'



signature.asc
Description: OpenPGP digital signature

Processed: python-asdf breaks gwcs autopkgtest: No module named 'asdf.extern'

Processing control commands:

> found -1 python-asdf/2.4.2-1
Bug #940720 [src:python-asdf] python-asdf breaks gwcs autopkgtest: No module 
named 'asdf.extern'
Marked as found in versions python-asdf/2.4.2-1.
> affects -1 src:gwcs
Bug #940720 [src:python-asdf] python-asdf breaks gwcs autopkgtest: No module 
named 'asdf.extern'
Added indication that 940720 affects src:gwcs
> affects -1 src:sunpy
Bug #940720 [src:python-asdf] python-asdf breaks gwcs autopkgtest: No module 
named 'asdf.extern'
Added indication that 940720 affects src:sunpy

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

Bug#940717: gtk-d FTBFS on armhf, tries to build with ldc but it's not installed.

2019-09-19 Thread peter green


Package: gtk-d
Version: 3.9.0-1
Severity: serious

the new gtk-d upload failed to build on armhf, the dependencies install gdc but 
the package tries to build with ldc.

I presume this was triggered by the change in default d compiler on armhf from 
ldc to gdc. The changelog mentions building with gdc, but whatever the actual 
change was it doesn't seem to have had the desired affect.

Processed: fixup bug metatada, the bts doesn't like it when a bug is filed against one package but fixed by another.

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

> reassign 939375 dh-dlang
Bug #939375 {Done: Matthias Klumpp } [dub] dub depends on 
unavailable default-d-compiler
Bug reassigned from package 'dub' to 'dh-dlang'.
No longer marked as found in versions dub/1.16.0-1.
No longer marked as fixed in versions dh-dlang/0.6.3.
> close 939375 0.6.3
Bug #939375 {Done: Matthias Klumpp } [dh-dlang] dub depends on 
unavailable default-d-compiler
Marked as fixed in versions dh-dlang/0.6.3.
Bug #939375 {Done: Matthias Klumpp } [dh-dlang] dub depends on 
unavailable default-d-compiler
Bug 939375 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#925754: Fixed in newer release of libopenshot / libopenshot-audio

2019-09-19 Thread FeRD

This issue was fixed with the simultaneous release of libopenshot-0.2.3 and
libopenshot-audio-0.1.8 on 2019-03-22. The new releases use an upgraded and
streamlined build of the Juce library sources, removing the problematic
modules which were causing FTBFS issues with GCC 9. See upstream issue
https://github.com/OpenShot/libopenshot-audio/issues/33 .

libopenshot-audio-0.1.8 release:
https://github.com/OpenShot/libopenshot-audio/releases/tag/v0.1.8
libopenshot-0.2.3 release:
https://github.com/OpenShot/libopenshot/releases/tag/v0.2.3

(The OpenShot application also released version 2.4.4 at that time:
https://github.com/OpenShot/openshot-qt/releases/tag/v2.4.4 )

Bug#940605: marked as done (jbig2dec: ABI breakage without SONAME and package name change)

Your message dated Thu, 19 Sep 2019 11:06:16 +
with message-id 
and subject line Bug#940605: fixed in jbig2dec 0.16+20190905-3
has caused the Debian Bug report #940605,
regarding jbig2dec: ABI breakage without SONAME and package name change
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.)


-- 
940605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjbig2dec0
Version: 0.16+20190905-2
Severity: normal

Dear Maintainer,

this version and the previous version 0.16+20190905-1 break mupdf which
crashes with message "undefined symbol: jbig2_ctx_new".

Regards,
Jörg.


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

Kernel: Linux 5.2.14 (SMP w/8 CPU cores)
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 /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libjbig2dec0 depends on:
ii  libc6  2.29-1

libjbig2dec0 recommends no packages.

libjbig2dec0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jbig2dec
Source-Version: 0.16+20190905-3

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated jbig2dec 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, 19 Sep 2019 12:41:12 +0200
Source: jbig2dec
Architecture: source
Version: 0.16+20190905-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Closes: 940605
Changes:
 jbig2dec (0.16+20190905-3) unstable; urgency=medium
 .
   * Fix Vcs-Browser URL.
   * Add patch 2002 to restore ABI compatibility.
 Closes: Bug#940605. Thanks to Julien Cristau.
   * Update symbols file: 1 symbol added (i.e. restored).
Checksums-Sha1:
 21bcbfc695398b99feed491d5b66e3d4ad811503 2137 jbig2dec_0.16+20190905-3.dsc
 3a3b419dc95f51771dd82e2d612ba5640e8024e3 20476 
jbig2dec_0.16+20190905-3.debian.tar.xz
 ade887fac33000b430d26792d7185ca94a4d69e6 7614 
jbig2dec_0.16+20190905-3_amd64.buildinfo
Checksums-Sha256:
 cbf61cdc0bf3b820b684488b95e4494e88b793b24a636058cc8f0a4965f6a726 2137 
jbig2dec_0.16+20190905-3.dsc
 80980eda59c522dbd79a56e9a5c7c06a81975bbc52d06eca8ac585b5b9254526 20476 
jbig2dec_0.16+20190905-3.debian.tar.xz
 aba15ed3ac2b8df4b0f07fbd39376daacb1c4d8e4d55ddf1f755b81c5791af9c 7614 
jbig2dec_0.16+20190905-3_amd64.buildinfo
Files:
 6b826bee9bcf7ad4c4594d9aeb4b20c5 2137 libs optional 
jbig2dec_0.16+20190905-3.dsc
 eb3ecea2972baadf01e20e1a68fc69e8 20476 libs optional 
jbig2dec_0.16+20190905-3.debian.tar.xz
 4aedb66446999e09dce1285a9651fa69 7614 libs optional 
jbig2dec_0.16+20190905-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2DXKEACgkQLHwxRsGg
ASGyexAAiGI74ktjBTUe8B1CZfFYs27sMoO+k8kD9ITJBZbys2F48NFS8Lothmub
E7oXQLAyDKqWnDyTVdsN8gYoPRnzQuQ8saoioHVNWQOWEb4PlQ2FO5UFZWkrYJHn
gUxbArRp3xsZUXtzxVYJ0LdVKFcor6lj0jnxU4gqwInAxi7tqFNvXbjH6SgCLszm
GnQIK58BMoEGbTI1iIUGLBR9894leaH92wDaxF0yRixvErXDGckk4kh0Cs8II8Sv
hQnyaC5YKCJ0FYo8W7OZt2q2R/L7c3sDrpnsd1k6+7wDJdhz+U/G/mxLR/WKKj5P
Q+9YJ5EMLg8N61bdp/lvDVy4b5u7MlrWYZgbnMpi8xnsUXev/3zr6YsQNW4wvBYY
Zwwp1bykaPB9+m+QUvqJoYyGhYLLK4qq3XosJfXvv+lMXuj9AtwMwq6sZQavUA7v
QllwGkaSzvICvFsRIUrQYDMlTQpJ7Gk1xbjAMknqOIRQLGjchCKw7AUnG0c4c7rC
9oGptI0a7+qWn+fgVLNDs/I27AiSIywWc31O+wIFJVjlBwpFsdhr5D9iIcihUtg8
ygJJDWV7HQ3etv5G6fxLuGmy52p4JdI1SS2lYM7wtsJXpunIs/ckDi7v/eiXQrob
1iI5IfccEUF1sGZtnTBriAAEf8u/YCLH3OezPNE2uSM5EtA25kI=
=e1JH
-END PGP SIGNATURE End Message ---

Bug#940605: Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1

2019-09-19 Thread Jonas Smedegaard

Quoting Jonas Smedegaard (2019-09-19 12:28:56)
> Quoting Julien Cristau (2019-09-19 12:07:16)
> > The former seems easier.
> 
> Thanks - also for your earlier clear explanation for the rejection.
> 
> My skills include reverting the upstream change but not comprehending 
> the concequences of such revert.
> 
> Help in the form of a patch would be tremendously appreciated.  

Ohhh, you already did.  Thanks a lot!


 - 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#940605: Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1

2019-09-19 Thread Jonas Smedegaard

Quoting Julien Cristau (2019-09-19 12:07:16)
> Control: tag -1 + patch
> 
> On Wed, Sep 18, 2019 at 12:01:04PM +0200, Julien Cristau wrote:
> > Control: severity 940605 serious
> > Control: retitle 940605 jbig2dec: ABI breakage without SONAME and package 
> > name change
> > 
> > On Wed, Sep 18, 2019 at 08:22:49AM +0200, Jonas Smedegaard wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: binnmu
> > > 
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > > 
> > > Hi release team,
> > > 
> > > Due to libjbig2dec0 upstream API being unstable, and a new release of
> > > libjbig2dec0 introduced a new symbol, mupdf needs a bunNMU to catch up.
> > > libjbig2dec0 tracks symbols changes, so a simple rebuild should properly
> > > tighten dependency to only the new API.
> > > 
> > > Please rebuild mupdf against libjbig2dec0 0.16+20190905-2 to bump its
> > > dependency on libjbig2dec0.
> > > 
> > NAK.  jbig2dec's symbols file diff includes this gem:
> > 
> > - jbig2_ctx_new@Base 0.11
> > 
> > This is broken.  It means jbig2_ctx_new, previously part of the ABI
> > surface, is no longer exported.  That needs to be fixed, either by
> > bringing it back or by bumping SONAME and library package name.
> > 
> The former seems easier.

Thanks - also for your earlier clear explanation for the rejection.

My skills include reverting the upstream change but not comprehending 
the concequences of such revert.

Help in the form of a patch would be tremendously appreciated.  

 - 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#940684: marked as done (breezy: build-depends on obsolete package.)

Your message dated Thu, 19 Sep 2019 10:19:13 +
with message-id 
and subject line Bug#940684: fixed in breezy 3.0.1-5
has caused the Debian Bug report #940684,
regarding breezy: build-depends on obsolete package.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: breezy
Severity: serious
Version: 3.0.1-2

Breezy (both versions 3.0.1-2 and 3.0.1-4) build-depends on python-subunit 
which is no longer built by the subunit source package.
--- End Message ---
--- Begin Message ---
Source: breezy
Source-Version: 3.0.1-5

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooĳ  (supplier of updated breezy 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, 19 Sep 2019 09:36:44 +
Source: breezy
Architecture: source
Version: 3.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Breezy Maintainers 
Changed-By: Jelmer Vernooĳ 
Closes: 936237 940684
Changes:
 breezy (3.0.1-5) unstable; urgency=medium
 .
   * Add Provides for bzr and the bzr plugins bundled by Breezy ahead of
 transition from Bazaar to Breezy.
   * Bump Breezy's default alterantives priority for the bzr command to 50,
 higher than that of Bazaar.
   * Drop Python 2 packages; they no longer build since the removal
 of python-testtools and python-subunit. Closes: #940684, #936237
   * Add dependency on python3-six, previously pulled in indirectly.
Checksums-Sha1:
 8be111c7970f85206c245fe23ab2ecd8750a28e1 2696 breezy_3.0.1-5.dsc
 e6a52825c6fe83282c6d49ab0323d134d88faa1f 63588 breezy_3.0.1-5.debian.tar.xz
 78495ddac14a0f76f320037bfc634fc3b7532ac1 10290 breezy_3.0.1-5_amd64.buildinfo
Checksums-Sha256:
 1a6b9568fffa1bf15c3db95bbc5395fd70bf7f8273e0f970411897463cadb708 2696 
breezy_3.0.1-5.dsc
 40d472f006e09fadcaa6daf32d55c9fd66cc3a20ae66d9f28c2e65d8fa10cee5 63588 
breezy_3.0.1-5.debian.tar.xz
 700ce71c15fcccb07a966dd38481fc432cb95a3210f8a75622e3f44f3c9d6a04 10290 
breezy_3.0.1-5_amd64.buildinfo
Files:
 ae909e4e4e51bff0548935f1a5968b59 2696 vcs optional breezy_3.0.1-5.dsc
 b104766d5e546adcfe7ed0df020e3b1a 63588 vcs optional 
breezy_3.0.1-5.debian.tar.xz
 699552f79a360931dba8e2859931749f 10290 vcs optional 
breezy_3.0.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl2DU84ACgkQV5wWDUye
I+hLdxAAp0vQodCx/onxqQsNwM5UE2xQaArelcEghsHPNjnNeW4a4BfnoJij+C5M
qtke+yW7ltKW1UqsAAa2+vkUg5LGrF9gWTb7/O89Eay00qCFxmy7/XQa5tr7mCJl
JYscuYKr2U5W/KkhMhJdYFK75mbtnaCx705ITKjtpKNFwijL5qksuUk6FLaqywsB
CKGNS6L4Cql+IoXLsmxolumWjTuzL67x5KUuMMRnhO/llOqDzfStb0xTThJUxU+e
BtZDkGK5opGJ14fQOCYE4eq4LTuQNZsAE0ZmKGUmwxDnpmynGoVgQlDkVMkl23kc
6FzZ+xiIeuRLFYpGwS+bPRQFs66I2b5sDId++4T42Mn0X7lb1Qreiuhax/F6ya8p
yGn3cxOPmd8ccXH50AKWgoRlDdi58t1aMKW/HoKMYBOYY1mwx/Hd2RASVF6g2dR3
QQuQ9bmQF9A81Xu1T3mxF7O0ntAJgkUn+iMPnnFiGvxTiwEZdAMCEuvUc7FMU+zu
8b68POHdvFpiIH/+xu+nQoz8OAstw8wTy2T2EQNe6FgdI7T7FUJA+Ky+5wMWT6cG
GlQXOETImW4S58Fw5GpW1nckXWTaEtZAcqAHYk0V1rqvOPCWK1RTzAJNWaz8HOs6
TypQuISJdInMkH2DooxOY2WTap5LreQozfMUiddPftZQoEXMOSc=
=9se5
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#940605: Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1

Processing control commands:

> tag -1 + patch
Bug #940605 [libjbig2dec0] jbig2dec: ABI breakage without SONAME and package 
name change
Added tag(s) patch.

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

Bug#940605: Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1

2019-09-19 Thread Julien Cristau

Control: tag -1 + patch

On Wed, Sep 18, 2019 at 12:01:04PM +0200, Julien Cristau wrote:
> Control: severity 940605 serious
> Control: retitle 940605 jbig2dec: ABI breakage without SONAME and package 
> name change
> 
> On Wed, Sep 18, 2019 at 08:22:49AM +0200, Jonas Smedegaard wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: binnmu
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > Hi release team,
> > 
> > Due to libjbig2dec0 upstream API being unstable, and a new release of
> > libjbig2dec0 introduced a new symbol, mupdf needs a bunNMU to catch up.
> > libjbig2dec0 tracks symbols changes, so a simple rebuild should properly
> > tighten dependency to only the new API.
> > 
> > Please rebuild mupdf against libjbig2dec0 0.16+20190905-2 to bump its
> > dependency on libjbig2dec0.
> > 
> NAK.  jbig2dec's symbols file diff includes this gem:
> 
> - jbig2_ctx_new@Base 0.11
> 
> This is broken.  It means jbig2_ctx_new, previously part of the ABI
> surface, is no longer exported.  That needs to be fixed, either by
> bringing it back or by bumping SONAME and library package name.
> 
The former seems easier.

Cheers,
Julien
>From 66749851a073946c4a4c45f087eafe3456947c62 Mon Sep 17 00:00:00 2001
From: Julien Cristau 
Date: Thu, 19 Sep 2019 12:03:07 +0200
Subject: [PATCH] Restore ABI compatibility (closes: #940605)

---
 debian/changelog |  7 +++
 debian/libjbig2dec0.symbols  |  1 +
 debian/patches/1002_abi_compat.patch | 18 ++
 debian/patches/series|  1 +
 4 files changed, 27 insertions(+)
 create mode 100644 debian/patches/1002_abi_compat.patch

diff --git a/debian/changelog b/debian/changelog
index f65ce86..2d6583d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+jbig2dec (0.16+20190905-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Restore ABI compatibility (closes: #940605)
+
+ -- Julien Cristau   Thu, 19 Sep 2019 11:56:17 +0200
+
 jbig2dec (0.16+20190905-2) unstable; urgency=medium
 
   * Fix have libjbig2dec0-dev depend on pkg-config
diff --git a/debian/libjbig2dec0.symbols b/debian/libjbig2dec0.symbols
index 4047c0e..c89abd1 100644
--- a/debian/libjbig2dec0.symbols
+++ b/debian/libjbig2dec0.symbols
@@ -11,6 +11,7 @@ libjbig2dec.so.0 libjbig2dec0 #MINVER#
  (optional=privatelib)jbig2_build_huffman_table@Base 0.11
  jbig2_complete_page@Base 0.11
  jbig2_ctx_free@Base 0.15+20190209
+ jbig2_ctx_new@Base 0.11
  jbig2_ctx_new_imp@Base 0.16+20190905
  jbig2_data_in@Base 0.11
  (optional=privatelib)jbig2_decode_generic_mmr@Base 0.11
diff --git a/debian/patches/1002_abi_compat.patch b/debian/patches/1002_abi_compat.patch
new file mode 100644
index 000..b3bfb28
--- /dev/null
+++ b/debian/patches/1002_abi_compat.patch
@@ -0,0 +1,18 @@
+diff --git a/jbig2.c b/jbig2.c
+index 97018ea..17ffd72 100644
+--- a/jbig2.c
 b/jbig2.c
+@@ -99,6 +99,13 @@ jbig2_error(Jbig2Ctx *ctx, Jbig2Severity severity, int32_t segment_number, const
+ return -1;
+ }
+ 
++#undef jbig2_ctx_new
++Jbig2Ctx *
++jbig2_ctx_new(Jbig2Allocator *allocator, Jbig2Options options, Jbig2GlobalCtx *global_ctx, Jbig2ErrorCallback error_callback, void *error_callback_data)
++{
++return jbig2_ctx_new_imp((allocator), (options), (global_ctx), (error_callback), (error_callback_data), JBIG2_VERSION_MAJOR, JBIG2_VERSION_MINOR);
++}
++
+ Jbig2Ctx *
+ jbig2_ctx_new_imp(Jbig2Allocator *allocator, Jbig2Options options, Jbig2GlobalCtx *global_ctx, Jbig2ErrorCallback error_callback, void *error_callback_data, int jbig2_version_major, int jbig2_version_minor)
+ {
diff --git a/debian/patches/series b/debian/patches/series
index 38452ba..1fdac8a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 1001_ignore_python_test.patch
+1002_abi_compat.patch
 1004_extract_infile_from_autogen-sh.patch
 2001_disable_memento.patch
-- 
2.23.0

Bug#940679: pandas: FTBFS on amd64 - TestDatetimelikeSubtype::test_astype_category[index3] crash

2019-09-19 Thread Graham Inggs


Hi Rebecca

On 2019/09/18 23:51, Rebecca N. Palmer wrote:
Was your local build on a different architecture, or must this be 
something random / hardware-or-environment-dependent / a very recent 
change in a build-dependency?


I first ran into a problem with the arch:all build of 0.23.3+dfsg-5 [1].

This seemed to be upstream issue #24088 [2], so I tested a src:all build 
including the patch on barriere.debian.org.


This should have been caught by the autopkgtest, but I noticed that 
python3-statsmodels was missing from the test dependencies.


After the build was successful on barriere, I uploaded with both changes.

At this point, I should have filed a bug against statsmodels to prevent 
the migration of 0.9.0-5 to testing, but was expecting the pandas builds 
to go smoothly.


I see 0.23.3+dfsg-6 was given back on amd64, and has just built 
successfully.  I'll keep an eye on the arch:all build, and investigate 
further if needed.


Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=pandas=all=0.23.3%2Bdfsg-5=1568792282=0

[2] https://github.com/pandas-dev/pandas/issues/24088
[3] 
https://salsa.debian.org/science-team/pandas/commit/b06adee846441925c3b87dc2a8d3c3a845f2e752

Bug#940703: augustus_3.3.3+dfsg-1_mips64el.changes REJECTED

2019-09-19 Thread Aurelien Jarno

Package: augustus
Version: 3.3.3+dfsg-1
Severity: serious

On 2019-09-18 23:34, Debian FTP Masters wrote:
> augustus_3.3.3+dfsg-1_mips64el.deb: Built-Using refers to non-existing source 
> package libbam-dev (= 0.1.19-4)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

The Built-Using field should use the source package (i.e.
samtools-legacy), not the binary package.

Bug#939794: marked as done (ghostscript breaks fig2dev autopkgtest: compare arrow tips with template failed unexpectedly)

Your message dated Thu, 19 Sep 2019 11:04:15 +0200
with message-id <156888385598.6451.4061855850838616...@auryn.jones.dk>
and subject line Re: Bug#939794: Seems to be fixed in rc3
has caused the Debian Bug report #939794,
regarding ghostscript breaks fig2dev autopkgtest: compare arrow tips with
template failed unexpectedly
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.)

--
939794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript, fig2dev
Control: found -1 ghostscript/9.28~~rc2~dfsg-1
Control: found -1 fig2dev/1:3.2.7a-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of ghostscript the autopkgtest of fig2dev fails in
testing when that autopkgtest is run with the binary packages of
ghostscript from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
ghostscriptfrom testing9.28~~rc2~dfsg-1
fig2devfrom testing1:3.2.7a-7
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. (The output is
rather dense. I would love a more verbose output, so that others like me
have something to look at.)

Currently this regression is blocking the migration of ghostscript to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fig2dev/2909339/log.gz
Test PostScript output language.

28: compare arrow tips with templateFAILED (output.at:41)

signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 9.28~~rc3~dfsg-1

Quoting Roland Rosenfeld (2019-09-19 10:41:36)
> As far as I can see, this issue is fixed in 9.28~~rc3 by the following
> commit:
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0350a0ab56e7b180d62af9423313d6c70345b386
> I'm not sure, why upstream doesn't mention this in their bugzilla...

Yes, It is also my understanding that that commit specifically addresses
the issue you brought up. Thanks!

> Debian CI for fig2dev is now green:
> https://ci.debian.net/packages/f/fig2dev/unstable/amd64/

I immediately built the rc3 when it was released, specifically with this
issue in mind.

Thanks for confirming that the upstream solution worked.

- 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
--- End Message ---

Bug#939794: Seems to be fixed in rc3

2019-09-19 Thread Roland Rosenfeld

As far as I can see, this issue is fixed in 9.28~~rc3 by the following
commit:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0350a0ab56e7b180d62af9423313d6c70345b386
I'm not sure, why upstream doesn't mention this in their bugzilla...

Debian CI for fig2dev is now green:
https://ci.debian.net/packages/f/fig2dev/unstable/amd64/

Greetings
Roland


signature.asc
Description: PGP signature

Bug#935839: marked as done (node-applause: autopkgtest fails on deprecation warning with new version of node-lodash)

Your message dated Thu, 19 Sep 2019 08:38:37 +
with message-id 
and subject line Bug#935839: fixed in node-applause 1.2.2-3
has caused the Debian Bug report #935839,
regarding node-applause: autopkgtest fails on deprecation warning with new 
version of node-lodash
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.)


-- 
935839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-applause
Version: 1.2.2-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:node-lodash

[X-Debbugs-CC: debian...@lists.debian.org, node-lod...@packages.debian.org]

Dear maintainers,

With a recent upload of node-lodash about two weeks ago the autopkgtest
of node-applause fails in testing when that autopkgtest is run with the
binary packages of node-lodash from unstable. It passes when run with
only packages from testing. In tabular form:
   passfail
node-lodashfrom testing4.17.15+dfsg-1
node-applause  from testing1.2.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails
an a deprecation *warning* reported to stderr. Either you want to fix
the deprecation *now*, disable deprecation warnings in autopkgtest or
allow output to stderr by setting the allow-stderr restriction.

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=node-lodash

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-applause/2822447/log.gz

  47 passing (51ms)

autopkgtest [11:16:31]: test runtestsuite: ---]
autopkgtest [11:16:31]: test runtestsuite:  - - - - - - - - - - results
- - - - - - - - - -
runtestsuite FAIL stderr: (node:1754) [DEP0016]
DeprecationWarning: 'root' is deprecated, use 'global'
autopkgtest [11:16:31]: test runtestsuite:  - - - - - - - - - - stderr -
- - - - - - - - -



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-applause
Source-Version: 1.2.2-3

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-applause 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, 19 Sep 2019 08:19:23 +0200
Source: node-applause
Architecture: source
Version: 1.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 935839
Changes:
 node-applause (1.2.2-3) unstable; urgency=medium
 .
   * Team upload
   * Switch test and install to pkg-js-tools (Closes: #935839)
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.4.0
   * Drop unneeded version constraints from (build) dependencies
Checksums-Sha1: 
 61a7d2a14d8bea37b5339aeb2c00682fb8f2b55b 2171 node-applause_1.2.2-3.dsc
 ad452a382e4fe45037eead69269b71172901adf9 2584 
node-applause_1.2.2-3.debian.tar.xz
Checksums-Sha256: 
 c3ed83d83ee5a545582cd921629c189f4a06be805b1a50d79a663583bc9a9829 2171 
node-applause_1.2.2-3.dsc
 894f55699a9a407152d649529efb712ca60b1f163ada571a1f4ee0575150 2584 
node-applause_1.2.2-3.debian.tar.xz
Files: 
 eff4bd498cb0843e965d8da3a6c1f17a 2171 javascript optional 
node-applause_1.2.2-3.dsc
 1e02db1b70be8eaef355904168492526 2584 javascript optional 
node-applause_1.2.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl2DNMEACgkQ9tdMp8mZ

Bug#913649: marked as done (should not ship with buster)

Your message dated Thu, 19 Sep 2019 07:37:07 +
with message-id 
and subject line Bug#940669: Removed package(s) from unstable
has caused the Debian Bug report #913649,
regarding should not ship with buster
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.)


-- 
913649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: common-lisp-controller
Version: 7.11
Severity: serious

common-lisp-controller is obsolete, and should not ship with buster. It has
been superseded by ASDF.

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
--- End Message ---
--- Begin Message ---
Version: 7.11+rm

Dear submitter,

as the package common-lisp-controller has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/940669

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#933919: src:lavacli: Unsafe use of yaml.load()

2019-09-19 Thread Scott Kitterman

On Thursday, September 19, 2019 2:54:50 AM EDT Remi Duraffort wrote:
> Hello,
> 
> looking at the failing CI jobs at
> https://ci.debian.net/packages/l/lavacli/unstable/amd64/ (more precisely
> https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lavacli/2666918/log.
> gz) we can see that the failure is due to a change in python3-yaml package
> that break the lavacli unit tests (change in the dumper output).
> 
> This issue has been reported in #934269 and fixed by
> https://git.lavasoftware.org/lava/lavacli/commit/1d374ccba0dc291e8d745ec90ff
> a8b4a32fb11af
> 
> So we should close this issue (#933919) and wait for the next release
> (coming in next week) to close #934269.

Since the autopkgtest is failing, the severity of normal is wrong for 934269.  
I think if you bump it's severity to reflect the current situation, that's fine.

Scott K

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

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi Lisandro,

On Wed, Sep 18, 2019 at 07:42:23PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> On 19/09/17 10:17, Andreas Tille wrote:
> > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > 
> > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty 
> > > code?
> > 
> > A lot is excluded in advance from the packaging Git:
> > 
> > Files-Excluded: */libQGLViewer*
> > */csparse
> > */gtest
> > */qwt*
> > */eigen-3*
> > */newmat
> > */extlibs/json
> > */tinyxml
> > */*.dll
> > */*.lib
> > */SuiteSparse
> > 
> > Some of these previously resided in SofaKernel/extlibs before
> > the removal.
> 
> Well, the first error I see is that the software seems to require cpsarse, 
> but I
> don't seem to find it in the archive :-(

Good catch.  No idea why this was excluded.  I've fixed this in a new repackaged
tarball.  Please `gbp pull`
 
> Am I missing something? 

Please always assume that the problem is at my side. ;-)

Thanks a lot for your help

 Andreas.

-- 
http://fam-tille.de

Bug#933919: src:lavacli: Unsafe use of yaml.load()

2019-09-19 Thread Remi Duraffort

Hello,

looking at the failing CI jobs at
https://ci.debian.net/packages/l/lavacli/unstable/amd64/ (more precisely
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lavacli/2666918/log.gz)
we can see that the failure is due to a change in python3-yaml package that
break the lavacli unit tests (change in the dumper output).

This issue has been reported in #934269 and fixed by
https://git.lavasoftware.org/lava/lavacli/commit/1d374ccba0dc291e8d745ec90ffa8b4a32fb11af

So we should close this issue (#933919) and wait for the next release
(coming in next week) to close #934269.


Rgds

-- 
Rémi Duraffort

Bug#933629: marked as done (hepmc3 FTBFS on arch-only: missing Build-Depends: doxygen for running dh_doxygen)

Your message dated Thu, 19 Sep 2019 06:33:56 +
with message-id 
and subject line Bug#933629: fixed in hepmc3 3.1.2-2
has caused the Debian Bug report #933629,
regarding hepmc3 FTBFS on arch-only: missing Build-Depends: doxygen for running 
dh_doxygen
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.)


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

hepmc3 fails to build from source, because it unconditionally runs
dh_doxygen but lists doxygen in Build-Depends-Indep only. arch-only
builds are deemed to fail.

Helmut
--- End Message ---
--- Begin Message ---
Source: hepmc3
Source-Version: 3.1.2-2

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

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

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated hepmc3 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, 19 Sep 2019 14:14:37 +0800
Source: hepmc3
Architecture: source
Version: 3.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Closes: 933629
Changes:
 hepmc3 (3.1.2-2) unstable; urgency=medium
 .
   * Move doxygen from B-D-I to B-D. (Closes: #933629)
   * Don't run unit tests on arch=all.
   * Fixup FTBFS on any architecture.
Checksums-Sha1:
 79861f1d357e1672557ecac24b1e3edc663843a5 2243 hepmc3_3.1.2-2.dsc
 844c6ae36c54cfd1506f6208c737141cae2bcaba 4028 hepmc3_3.1.2-2.debian.tar.xz
 569e6f9661f959be8de76a291385ebde2d18cf27 6808 hepmc3_3.1.2-2_source.buildinfo
Checksums-Sha256:
 54d171ee7c741832386ead942712df33206397ac867301afe5d516a380bea0cf 2243 
hepmc3_3.1.2-2.dsc
 8bce957ef7bba7c4da990609cd9ddc500bf372f3d22c53134654913ab3fc3081 4028 
hepmc3_3.1.2-2.debian.tar.xz
 3d4126cd4b73acece685d9c02696fb2fb8b92f0cf2a3683f6142d418d329904a 6808 
hepmc3_3.1.2-2_source.buildinfo
Files:
 a4651c051390b37f94b46beb1e2e40bd 2243 science optional hepmc3_3.1.2-2.dsc
 e337f34dcdb2af82453845c89b0bb870 4028 science optional 
hepmc3_3.1.2-2.debian.tar.xz
 fb20c170b95afefc8d7e4aa0608b29f3 6808 science optional 
hepmc3_3.1.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl2DHTAVHGNkbHVtaW5h
dGVAZ21haWwuY29tAAoJEGJkXrNfaGqK/f4P/jDBbVCxdXs75Z43nO46dd++EUBA
4cSiNu1u4k26H0amDxFGmjAkY0o1+im+Cu2z3Zb8JORp3C5D0bc8XQaJTodNml5S
ma6NotyiRXUucIqX3t3fv3CA/oUfbmBn4kumSu7kMxfmpqB7EXuQfsPdeaoJPQV5
uaqIvdLRVLzVt2Qihm2p7wt4OPlQXbIed6zY6DmIAbpzwwtbwa6E3IiLTOyVoloP
vt45q1akrl7Bqt02UBkNALnpHBKUEiooky6KRKPDOGIlZiYz+bmENjoZIaHjiFZQ
GXuushCozx31FwjKJGKf34ZArtoxdZn18HUaT1xWliCJMrC9LyFZyhJ86P0RKk9A
JUeH78iVvoo9SjTgt1DEWllNa73T0bHsDlp3xjIHru8uF9iTf9//7T3YtqWYVfkz
4WX6X/cmrwnTt66L2wHE8K7mCbtXlulGcXHKHU6jzKi/B2kIdok2kGF8JyhQ/v0v
3oBqZfAuyzM5VM8hBR9Gxm8BfpGxgcC2QhvNo/Rn20LfuBi3tU6YrRFOZtV8FdX2
cKibLBFBnr3szPcriPKnWLPNkLEDjC9ZzQ7ChiBOvVdsqbismY93PRKUjbPV+//4
qLp8Ezusc1yEydfx4CvRueWglctC1Pi5gJtDlEpPXGDxPcyF46//72U/ZOWAyI4K
IyCuQzZp0pw4i+aR
=x7iP
-END PGP SIGNATURE End Message ---

Bug#912077: Any chance to get libbiod compiling again?

Hi Matthias,

On Thu, Sep 19, 2019 at 12:49:54AM +0200, Matthias Klumpp wrote:
> > As I told you before:  I have no idea about meson.  It would be great if
> > we could get it working but if we restrict the package to those
> > architectures where it builds out of the box and save some manpower I
> > bet the world will keep on turning round.
> 
> It's not just that. Also the build needs to be changed to respect
> Debian's compile flags, build a shared library and write a pkg-config
> file. All doable with Makefiles, but not really much fun. At that
> point just using Meson becomes easier.
> The package is team-maintained, right? In that case I may just give
> this a shot this weekend and get the biod package to build again. It
> shouldn't actually by hard to do at all (famous last words :P)

Its team maintained and you are member of the team.  Just push whatever
you consider sensible.
 
> > > Btw, if libundead has no users anymore, removing it completely may be
> > > a good idea - we don't need to maintain something that's dead and has
> > > no users.
> >
> > I was about to file a removal request to ftpmaster before you said in
> > your last mail that the former build issue might have been caused due
> > to the lack of libundead.  I would really love to get rid of unneeded
> > packages.
> 
> Better check for reverse dependencies, but if there are none, I don't
> see a need to keep it.

$ apt-cache rdepends libundead0
libundead0
Reverse Depends:
  libundead-dev
  sambamba
  libundead-dev
  libbiod0

> Undead is basically deprecated & removed D
> stdlib modules with zero or very little maintenance, so generally
> something a project wants to get rid of rather quickly anyway, and
> quite likely nothing worth keeping in Debian on its own.

So I'll ask for removal since if I understood you correctly it will
go away from both projects above.

Thanks a lot for your help

Andreas. 

-- 
http://fam-tille.de

Bug#912077: Any chance to get libbiod compiling again?