date:20200721

Processed: Bug#963761 marked as pending in node-node-sass

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #963761 {Done: Andrius Merkys } [src:node-node-sass] 
node-node-sass: missing versioned dependency relation?: Sass could not find a 
binding for your current environment
Added tag(s) pending.

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

Bug#963761: marked as pending in node-node-sass

2020-07-21 Thread Andrius Merkys

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-node-sass/-/commit/b67b2da66b2dcc8d4b675ec5706c8aa311fbb376


Tightening dependency on nodejs (Closes: #963761). Thanks Jonas Smedegaard and 
Paul Gevers.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963761

Bug#963761: marked as done (node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Wed, 22 Jul 2020 05:33:38 +
with message-id 
and subject line Bug#963761: fixed in node-node-sass 
4.14.1+git20200512.e1fc158+dfsg-2
has caused the Debian Bug report #963761,
regarding node-node-sass: missing versioned dependency relation?: Sass could 
not find a binding for your current environment
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.)


-- 
963761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-node-sass
Version: 4.14.1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, nod...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs src:node-grunt-sass

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-grunt-sass fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-grunt-sassfrom testing3.1.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. Similar to the
issues with node-iconv and node-expat, node-node-sass seems to be
missing a versioned relation with nodejs. Because of the missing
relation, nodejs can be upgraded without the rebuild node-node-sass from
unstable.

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-grunt-sass/6051450/log.gz

autopkgtest [01:12:40]: test pkg-js-autopkgtest: [---
Using package.json
Node module name is grunt-sass
# Copy test files
Looking at /usr/lib/nodejs/grunt-sass
Looking at /usr/lib/*/nodejs/grunt-sass
Looking at /usr/share/nodejs/grunt-sass
Found /usr/share/nodejs/grunt-sass
Linking /usr/share/nodejs/grunt-sass/package.json
Linking /usr/share/nodejs/grunt-sass/tasks
Launch debian/tests/pkg-js/test with sh -ex
+ grunt sass nodeunit
Loading "gruntfile.js" tasks...ERROR
>> Error: Missing binding
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
>> Node Sass could not find a binding for your current environment:
Linux 64-bit with Node.js 12.x
>>
>> Found bindings for the following environments:
>>   - Linux 64-bit with Node.js 10.x
>>
>> This usually happens because your environment has changed since
running `npm install`.
>> Run `npm rebuild node-sass` to download the binding for your current
environment.
Warning: Task "sass" not found. Use --force to continue.

Aborted due to warnings.
autopkgtest [01:12:41]: test pkg-js-autopkgtest: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-node-sass
Source-Version: 4.14.1+git20200512.e1fc158+dfsg-2
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated node-node-sass 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, 22 Jul 2020 01:12:22 -0400

Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

2020-07-21 Thread merkys

On 2020-07-12 13:52, Jonas Smedegaard wrote:
> I think that when we declare only¹ lower bounds, we do avoid the biggest 
> headache of nodejs failing to transition - and reduce the problem to 
> each package requiring a binNMU being flagged as such.

[snip]

> ¹ ...and obviously declare upper bounds too when we _know_ what they 
> are, but generally in Debian we have no crystal ball so cannot know 
> which future release will break things.

I completely agree.

Thanks,
Andrius



signature.asc
Description: OpenPGP digital signature

Bug#966002: python3-pandas: cannot be loaded anymore - FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/matplotlib/mpl-data/matplotlibrc'

2020-07-21 Thread Norbert Preining

Package: python3-pandas
Version: 0.25.3+dfsg2-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info


$ python3
Python 3.8.5 (default, Jul 20 2020, 18:32:44)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pandas
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pandas/__init__.py", line 56, in 
from pandas.core.api import (
  File "/usr/lib/python3/dist-packages/pandas/core/api.py", line 24, in 
from pandas.core.groupby import Grouper, NamedAgg
  File "/usr/lib/python3/dist-packages/pandas/core/groupby/__init__.py", line 
1, in 
from pandas.core.groupby.generic import (  # noqa: F401
  File "/usr/lib/python3/dist-packages/pandas/core/groupby/generic.py", line 
44, in 
from pandas.core.frame import DataFrame
  File "/usr/lib/python3/dist-packages/pandas/core/frame.py", line 115, in 

from pandas.core.series import Series
  File "/usr/lib/python3/dist-packages/pandas/core/series.py", line 84, in 

import pandas.plotting
  File "/usr/lib/python3/dist-packages/pandas/plotting/__init__.py", line 59, 
in 
from pandas.plotting._core import (
  File "/usr/lib/python3/dist-packages/pandas/plotting/_core.py", line 17, in 

import pandas.plotting._matplotlib  # noqa
  File 
"/usr/lib/python3/dist-packages/pandas/plotting/_matplotlib/__init__.py", line 
3, in 
from pandas.plotting._matplotlib.boxplot import (
  File "/usr/lib/python3/dist-packages/pandas/plotting/_matplotlib/boxplot.py", 
line 4, in 
from matplotlib.artist import setp
  File "/usr/lib/python3/dist-packages/matplotlib/__init__.py", line 899, in 

rcParamsDefault = _rc_params_in_file(
  File "/usr/lib/python3/dist-packages/matplotlib/__init__.py", line 798, in 
_rc_params_in_file
with _open_file_or_url(fname) as fd:
  File "/usr/lib/python3.8/contextlib.py", line 113, in __enter__
return next(self.gen)
  File "/usr/lib/python3/dist-packages/matplotlib/__init__.py", line 776, in 
_open_file_or_url
with open(fname, encoding=encoding) as f:
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/share/matplotlib/mpl-data/matplotlibrc'
>>>


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

Kernel: Linux 5.8.0-rc6 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-pandas depends on:
ii  python33.8.2-3
ii  python3-dateutil   2.8.1-4
ii  python3-numpy  1:1.19.0-1
ii  python3-pandas-lib 0.25.3+dfsg2-3
ii  python3-pkg-resources  46.1.3-1
ii  python3-six1.15.0-1
ii  python3-tz 2020.1-2

Versions of packages python3-pandas recommends:
ii  python3-bs4 4.9.1-1
ii  python3-html5lib1.1-1
ii  python3-lxml4.5.2-1
ii  python3-matplotlib  3.3.0-1
ii  python3-numexpr 2.7.1-1+b1
ii  python3-openpyxl3.0.3-1
ii  python3-scipy   1.4.1-2
ii  python3-tables  3.6.1-2
ii  python3-xlrd1.1.0-5
ii  python3-xlwt1.3.0-3

Versions of packages python3-pandas suggests:
ii  python-pandas-doc0.25.3+dfsg2-3
pn  python3-statsmodels  

-- no debconf information

Processed: tagging 963556

2020-07-21 Thread Debian Bug Tracking System

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

> tags 963556 + fixed
Bug #963556 {Done: Paul Gevers } [src:gxr] src:gxr: fails to 
migrate to testing for too long: unfixed RC bug
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#965995: dnscrypt-proxy: Purging fails: rm: cannot remove '/etc/dnscrypt-proxy/dnscrypt-proxy.conf.dpkg-bak': Is a directory

2020-07-21 Thread Axel Beckert

Package: dnscrypt-proxy
Version: 2.0.44+ds1-2
Severity: serious
X-Debbugs-Cc: Axel Beckert 

Purging dnscrypt-proxy fails for me as follows (and IIRC I never changed
anything from the default config, but the package might have a bit on
history on that machine):

# dpkg --purge dnscrypt-proxy
(Reading database ... 1190427 files and directories currently installed.)
Purging configuration files for dnscrypt-proxy (2.0.44+ds1-2) ...
rm: cannot remove '/etc/dnscrypt-proxy/dnscrypt-proxy.conf.dpkg-bak': Is a 
directory
dpkg: error processing package dnscrypt-proxy (--purge):
 installed dnscrypt-proxy package post-removal script subprocess returned error 
exit status 1
Errors were encountered while processing:
 dnscrypt-proxy

Might be just a missing "-r" to "rm" in the postrm script or so.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dnscrypt-proxy depends on:
ii  adduser   3.118
ii  libc6 2.31-1
ii  lsb-base  11.1.0

dnscrypt-proxy recommends no packages.

Versions of packages dnscrypt-proxy suggests:
pn  resolvconf

Bug#964408: marked as done (python-redisearch-py: autopkgtest failure: No module named 'redisearch_py')

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 21:18:39 +
with message-id 
and subject line Bug#964408: fixed in python-redisearch-py 1.0.0-1
has caused the Debian Bug report #964408,
regarding python-redisearch-py: autopkgtest failure: No module named 
'redisearch_py'
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.)


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

Dear maintainer(s),

You recently added an autopkgtest to your package python-redisearch-py,
great. However, it fails. Currently this failure is blocking the
migration to testing [1]. Can you please investigate the situation and
fix it?

I copied some of the output at the bottom of this report. You're using
autodep8 to test your python package. You probably need to tell it that
your module is named differently.

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-redisearch-py

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-redisearch-py/6046207/log.gz

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-redisearch-py
Source-Version: 1.0.0-1
Done: Michael Fladischer 

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated python-redisearch-py 
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, 21 Jul 2020 22:59:35 +0200
Source: python-redisearch-py
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Closes: 964408
Changes:
 python-redisearch-py (1.0.0-1) unstable; urgency=low
 .
   * New upstream release.
   * Tell autodep8 to use the correct import name (Closes: #964408).
   * Fix typo in long description (python -> Python).
Checksums-Sha1:
 d8b95b92790cc62b0d47219f251f87f2f1a0e5bf 1819 python-redisearch-py_1.0.0-1.dsc
 c059c81c8ba93b8986ea686aaefe65bfc8ba7c23 2101812 
python-redisearch-py_1.0.0.orig.tar.gz
 e15429cca41accdd3a5efdf956de6000bc82c111 2320 
python-redisearch-py_1.0.0-1.debian.tar.xz
 48f31c12f166b4db4a6fb9da6066330d1cc73263 6782 
python-redisearch-py_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 cb6d22ea852d822025590b72a36b2a2f7860130aff4604683d5ab22f88e3220b 1819 
python-redisearch-py_1.0.0-1.dsc
 def2bd579d57f1b93f14476f20f5a460d34e073437431266bd7399e9ca230fed 2101812 
python-redisearch-py_1.0.0.orig.tar.gz
 a48fb2abfc27689cb063239088b483a8b3ec9ffc33c5dbdd765183286ce41e97 2320 
python-redisearch-py_1.0.0-1.debian.tar.xz
 5d0d3165d39050d4ea124c87e3b4ac07fca9772fbc0cb8e826e8312710061cd5 6782 
python-redisearch-py_1.0.0-1_amd64.buildinfo
Files:
 7ac6a3aa4ca1cab941abac3e3dbfcc2a 1819 python optional 
python-redisearch-py_1.0.0-1.dsc
 8379b00d6e79a9fdb2ea3a70665c3ef5 2101812 python optional 
python-redisearch-py_1.0.0.orig.tar.gz
 fa94d7a48c581e9211dc37778dfa734f 2320 python optional 
python-redisearch-py_1.0.0-1.debian.tar.xz
 999c41eb07ba4d5c3db01e08db52df1d 6782 python optional 
python-redisearch-py_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl8XWEAACgkQ/9PIi5l9

Bug#961280: marked as done (guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 23:06:13 +0200
with message-id <20200721210613.ga690...@ramacher.at>
and subject line Re: Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: 
alternatives priority expects min version < 1000.
has caused the Debian Bug report #961280,
regarding guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority 
expects min version < 1000
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.)

-- 
961280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guile-2.2
Version: 2.2.7+1-5
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While bootstrap testing unstable, I noticed that guile-2.2 fails to
build from source (natively). A build now ends quicky:

| dpkg-buildpackage: info: source package guile-2.2
| dpkg-buildpackage: info: source version 2.2.7+1-5
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Rob Browning 

|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| /bin/bash: ${\#x}: bad substitution
| debian/rules:70: *** ERROR: alternatives priority expects min version < 1000. 
 Stop.
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

This only happens since make-dfsg/4.3-1, but I think the bug here
ultimately is with guile-2.2. The relevant code from debian/rules is:

| ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo ok;))
|   $(error ERROR: alternatives priority expects min version < 1000)
| endif

It is surprising that this didn't fail with earlier versions of make.
The shell substitution is clearly wrong. It is unclear what it is
supposed to achieve. In any case, deleting these lines makes the build
proceed.

Helmut
--- End Message ---
--- Begin Message ---
Version: 3.0.4-1

On 2020-05-22 14:41:05 +0200, Helmut Grohne wrote:
> Control: clone -1 -2
> Control: reassign -2 src:guile-3.0
> 
> On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> > While bootstrap testing unstable, I noticed that guile-2.2 fails to
> > build from source (natively). A build now ends quicky:
> > 
> > | dpkg-buildpackage: info: source package guile-2.2
> > | dpkg-buildpackage: info: source version 2.2.7+1-5
> > | dpkg-buildpackage: info: source distribution unstable
> > | dpkg-buildpackage: info: source changed by Rob Browning 
> > 
> > |  dpkg-source --before-build .
> > | dpkg-buildpackage: info: host architecture amd64
> > |  fakeroot debian/rules clean
> > | /bin/bash: ${\#x}: bad substitution
> > | debian/rules:70: *** ERROR: alternatives priority expects min version < 
> > 1000.  Stop.
> > | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> > exit status 2
> > 
> > This only happens since make-dfsg/4.3-1, but I think the bug here
> > ultimately is with guile-2.2. The relevant code from debian/rules is:
> > 
> > | ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo 
> > ok;))
> > |   $(error ERROR: alternatives priority expects min version < 1000)
> > | endif
> > 
> > It is surprising that this didn't fail with earlier versions of make.
> > The shell substitution is clearly wrong. It is unclear what it is
> > supposed to achieve. In any case, deleting these lines makes the build
> > proceed.
> 
> guile-3.0 also has this exact same bug.

guile-3.0 (3.0.4-1) unstable; urgency=medium

  * Upgrade to 3.0.4

  * debian/rules: fix deb_src_min_ver limit check.

Cheers
-- 
Sebastian Ramacher

signature.asc
Description: PGP signature
--- End Message ---

Processed: Re: Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #961230 {Done: Sebastian Ramacher } [src:guile-2.2] 
guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min 
version < 1000.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 3.0.4-1.

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

Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.

2020-07-21 Thread Sebastian Ramacher

Control: reopen -1

Sorry, that went to the wrong bug

On 2020-07-21 23:06:13 +0200, Sebastian Ramacher wrote:
> Version: 3.0.4-1
> 
> On 2020-05-22 14:41:05 +0200, Helmut Grohne wrote:
> > Control: clone -1 -2
> > Control: reassign -2 src:guile-3.0
> > 
> > On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> > > While bootstrap testing unstable, I noticed that guile-2.2 fails to
> > > build from source (natively). A build now ends quicky:
> > > 
> > > | dpkg-buildpackage: info: source package guile-2.2
> > > | dpkg-buildpackage: info: source version 2.2.7+1-5
> > > | dpkg-buildpackage: info: source distribution unstable
> > > | dpkg-buildpackage: info: source changed by Rob Browning 
> > > 
> > > |  dpkg-source --before-build .
> > > | dpkg-buildpackage: info: host architecture amd64
> > > |  fakeroot debian/rules clean
> > > | /bin/bash: ${\#x}: bad substitution
> > > | debian/rules:70: *** ERROR: alternatives priority expects min version < 
> > > 1000.  Stop.
> > > | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess 
> > > returned exit status 2
> > > 
> > > This only happens since make-dfsg/4.3-1, but I think the bug here
> > > ultimately is with guile-2.2. The relevant code from debian/rules is:
> > > 
> > > | ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo 
> > > ok;))
> > > |   $(error ERROR: alternatives priority expects min version < 1000)
> > > | endif
> > > 
> > > It is surprising that this didn't fail with earlier versions of make.
> > > The shell substitution is clearly wrong. It is unclear what it is
> > > supposed to achieve. In any case, deleting these lines makes the build
> > > proceed.
> > 
> > guile-3.0 also has this exact same bug.
> 
> guile-3.0 (3.0.4-1) unstable; urgency=medium
> 
>   * Upgrade to 3.0.4
> 
>   * debian/rules: fix deb_src_min_ver limit check.
> 
> Cheers
> -- 
> Sebastian Ramacher



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#961230: marked as done (guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 23:06:13 +0200
with message-id <20200721210613.ga690...@ramacher.at>
and subject line Re: Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: 
alternatives priority expects min version < 1000.
has caused the Debian Bug report #961230,
regarding guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority 
expects min version < 1000.
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.)

-- 
961230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guile-2.2
Version: 2.2.7+1-5
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While bootstrap testing unstable, I noticed that guile-2.2 fails to
build from source (natively). A build now ends quicky:

| dpkg-buildpackage: info: source package guile-2.2
| dpkg-buildpackage: info: source version 2.2.7+1-5
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Rob Browning 

|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| /bin/bash: ${\#x}: bad substitution
| debian/rules:70: *** ERROR: alternatives priority expects min version < 1000. 
 Stop.
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

This only happens since make-dfsg/4.3-1, but I think the bug here
ultimately is with guile-2.2. The relevant code from debian/rules is:

| ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo ok;))
|   $(error ERROR: alternatives priority expects min version < 1000)
| endif

It is surprising that this didn't fail with earlier versions of make.
The shell substitution is clearly wrong. It is unclear what it is
supposed to achieve. In any case, deleting these lines makes the build
proceed.

Helmut
--- End Message ---
--- Begin Message ---
Version: 3.0.4-1

On 2020-05-22 14:41:05 +0200, Helmut Grohne wrote:
> Control: clone -1 -2
> Control: reassign -2 src:guile-3.0
> 
> On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> > While bootstrap testing unstable, I noticed that guile-2.2 fails to
> > build from source (natively). A build now ends quicky:
> > 
> > | dpkg-buildpackage: info: source package guile-2.2
> > | dpkg-buildpackage: info: source version 2.2.7+1-5
> > | dpkg-buildpackage: info: source distribution unstable
> > | dpkg-buildpackage: info: source changed by Rob Browning 
> > 
> > |  dpkg-source --before-build .
> > | dpkg-buildpackage: info: host architecture amd64
> > |  fakeroot debian/rules clean
> > | /bin/bash: ${\#x}: bad substitution
> > | debian/rules:70: *** ERROR: alternatives priority expects min version < 
> > 1000.  Stop.
> > | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> > exit status 2
> > 
> > This only happens since make-dfsg/4.3-1, but I think the bug here
> > ultimately is with guile-2.2. The relevant code from debian/rules is:
> > 
> > | ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo 
> > ok;))
> > |   $(error ERROR: alternatives priority expects min version < 1000)
> > | endif
> > 
> > It is surprising that this didn't fail with earlier versions of make.
> > The shell substitution is clearly wrong. It is unclear what it is
> > supposed to achieve. In any case, deleting these lines makes the build
> > proceed.
> 
> guile-3.0 also has this exact same bug.

guile-3.0 (3.0.4-1) unstable; urgency=medium

  * Upgrade to 3.0.4

  * debian/rules: fix deb_src_min_ver limit check.

Cheers
-- 
Sebastian Ramacher

signature.asc
Description: PGP signature
--- End Message ---

Processed: tagging 965985, found 965985 in 17.2.7-2.1, found 965985 in 16.2.6-5

2020-07-21 Thread Debian Bug Tracking System

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

> tags 965985 + upstream
Bug #965985 [src:bareos] CVE-2020-4042 / CVE-2020-11061
Added tag(s) upstream.
> found 965985 17.2.7-2.1
Bug #965985 [src:bareos] CVE-2020-4042 / CVE-2020-11061
Marked as found in versions bareos/17.2.7-2.1.
> found 965985 16.2.6-5
Bug #965985 [src:bareos] CVE-2020-4042 / CVE-2020-11061
Marked as found in versions bareos/16.2.6-5.
> thanks
Stopping processing here.

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

Bug#965985: CVE-2020-4042 / CVE-2020-11061

2020-07-21 Thread Moritz Muehlenhoff

Source: bareos
Severity: grave
Tags: security

CVE-2020-11061:
https://github.com/bareos/bareos/security/advisories/GHSA-mm45-cg35-54j4

CVE-2020-4042
https://github.com/bareos/bareos/security/advisories/GHSA-vqpj-2vhj-h752

Cheers,
Moritz

Bug#965979: freerdp2: CVE-2020-15103

2020-07-21 Thread Salvatore Bonaccorso

Source: freerdp2
Version: 2.1.2+dfsg1-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/FreeRDP/FreeRDP/pull/6381
X-Debbugs-Cc: Debian Security Team 

Hi,

The following vulnerability was published for freerdp2.

CVE-2020-15103[0]:
| Integer overflow due to missing input sanitation in rdpegfx channel

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-15103
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15103
[1] https://github.com/FreeRDP/FreeRDP/pull/6381

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#965305: marked as done (ruby-kramdown: CVE-2020-14001)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 19:18:45 +
with message-id 
and subject line Bug#965305: fixed in ruby-kramdown 2.3.0-1
has caused the Debian Bug report #965305,
regarding ruby-kramdown: CVE-2020-14001
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.)


-- 
965305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kramdown
Version: 1.17.0-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 
Control: found -1 1.17.0-1

Hi,

The following vulnerability was published for ruby-kramdown.

CVE-2020-14001[0]:
| The kramdown gem before 2.3.0 for Ruby processes the template option
| inside Kramdown documents by default, which allows unintended read
| access (such as template="/etc/passwd") or unintended embedded Ruby
| code execution (such as a string that begins with
| template="string://%= `). NOTE: kramdown is used in Jekyll, GitLab
| Pages, GitHub Pages, and Thredded Forum.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-14001
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14001
[1] 
https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ruby-kramdown
Source-Version: 2.3.0-1
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-kramdown 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, 21 Jul 2020 21:02:27 +0530
Source: ruby-kramdown
Architecture: source
Version: 2.3.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Closes: 965305
Changes:
 ruby-kramdown (2.3.0-1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream version 2.3.0 (Closes: #965305) (Fixes: CVE-2020-14001)
   * Bump Standards-Version to 4.5.0 (no changes needed)
   * Drop patches not needed anymore
Checksums-Sha1:
 d38fc9e1471d683317788c34b9d7f349d7e914a6 2278 ruby-kramdown_2.3.0-1.dsc
 5c77c487286e187af5f537aa88364206f9019703 123436 ruby-kramdown_2.3.0.orig.tar.gz
 7350240f082a15f26074e200a048ba8bcc8cd8ff 5116 
ruby-kramdown_2.3.0-1.debian.tar.xz
 6fd3552aacadbe198e8751a58ae4f51f816ce74e 10830 
ruby-kramdown_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 404fcb072529131f368067d625a0b54e993f707244c9d1440b2d745a3e7d0176 2278 
ruby-kramdown_2.3.0-1.dsc
 dd56cd8ee1656ffb5d5fd90ce8f4f5b7f4d4a78cf6ef57b16cfc96416086a12f 123436 
ruby-kramdown_2.3.0.orig.tar.gz
 2e608f1c1953f281990653eef54eea5f386aaa8362f16ffbc55f81705ca0ced0 5116 
ruby-kramdown_2.3.0-1.debian.tar.xz
 ff4b42c987262a8aa292418b71a5272defc9af00ae6d6042f95e96f5dfa40d5a 10830 
ruby-kramdown_2.3.0-1_amd64.buildinfo
Files:
 39edcd7f2977858cfdae82eef4969a2b 2278 ruby optional ruby-kramdown_2.3.0-1.dsc
 5825e6e7b3a50704de27573c18d60492 123436 ruby optional 
ruby-kramdown_2.3.0.orig.tar.gz
 60937dfaed9546645a7221eda121d59d 5116 ruby optional 
ruby-kramdown_2.3.0-1.debian.tar.xz
 95e76ecdba31c7825e0214739e9da2f8 10830 ruby optional 
ruby-kramdown_2.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl8XPMQACgkQj1PgGTsp
S3WG0g//QkFb7gWVZ8GSE3xhmei9Cd2K0gw6PFlZ4qv4IkkY/m7wdQaTQKRs7HdG
PNzdwsdQAiuIJqJ534v8gYaSuFtkkCydBCMwyYCu8XYNNtE2tcNhgDhH1hPoYKqO
GqlGdEMwt2f2Y8nzIQWWUP0kZoXPyh/7A8rD5dC5oBT6lZFda83k7f7BRD9Lq317
ckGi9zH+Iwx1DeFWVDqxYCcLe+Z28wPyHlfSnR4YSUhjOKRbLHzstNwjUlN4Qs4f
/CEYh+p9WAPOF0GwWXekemJA0PC/VHWPofVhm5y6Ko1CRUIZQOGAwWULX+zNjqMX
vIVnjtAPbjiddzeevNhfjPdMR/dB8BR4Czl0CgS5TzQH5MSElISRHWAsTz68NP18
zRMgpLigL7lprsINmBmhilKloc5BLfV/0+NoEufDMpG5o6ZV2Z5PPljwur2XS70z

Bug#963408: marked as done (pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 18:48:27 +
with message-id 
and subject line Bug#963408: fixed in pmtools 2.2.0-2
has caused the Debian Bug report #963408,
regarding pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


-- 
963408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmtools
Version: 2.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t t/lib/*.t
> t/basepods.t . 
> 1..3
> ok 1 - basepods runs
> ok 2 - found Perl POD
> ok 3 - found POD POD
> ok
> t/faqpods.t .. 
> 1..2
> ok 1 - faqpods runs
> ok 2 - found a Perl FAQ POD
> ok
> t/lib/pmtools.t .. 
> 1..7
> ok 1 - created a pmtools iterator
> ok 2 - first POD file, first @INC
> ok 3 - middle POD file, first @INC
> ok 4 - last POD file, first @INC
> ok 5 - last POD file, last @INC
> ok 6 - beyond end of filenames
> ok 7 - way beyond end of filenames
> ok
> t/modpods.t .. 
> 1..2
> ok 1 - modpods runs
> ok 2 - found Tie::Hash
> ok
> t/pfcat.t  
> 1..2
> ok 1 - pfcat runs
> ok 2 - catted module function
> ok
> t/plxload.t .. 
> 1..1
> ok 1 - modules loaded
> ok
> t/pmall.t  
> 1..2
> ok 1 - pmall runs
> ok 2 - synopsized all modules
> ok
> 
> #   Failed test 'found Carp'
> #   at t/pman.t line 20.
> #   'pod2text: unable to format 
> /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm
> # '
> # doesn't match '(?^ms:NAME.*[Cc]arp - \w.*SYNOPSIS.*DESCRIPTION)'
> # Looks like you failed 1 test of 2.
> t/pman.t . 
> 1..2
> ok 1 - pman runs
> not ok 2 - found Carp
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests 
> t/pmcat.t  
> 1..2
> ok 1 - pmcat runs
> ok 2 - catted Carp
> ok
> t/pmcheck.t .. 
> 1..2
> ok 1 - pmcheck runs
> ok 2 - pmcheck had output
> ok
> t/pmdesc.t ... 
> 1..2
> ok 1 - pmdesc runs
> ok 2 - described a module
> ok
> t/pmeth.t  
> 1..2
> ok 1 - pmeth runs
> ok 2 - list methods of a module
> ok
> t/pmexp.t  
> 1..2
> ok 1 - pmexp runs
> ok 2 - listed module exports
> ok
> t/pmfunc.t ... 
> 1..3
> ok 1 - pmfunc runs
> ok 2 - found 'chdir()'
> ok 3 - display function body
> ok
> t/pmload.t ... 
> 1..2
> ok 1 - pmload runs
> ok 2 - listed loaded modules
> ok
> t/pmls.t . 
> 1..2
> ok 1 - pmls runs
> ok 2 - found Tie::Hash
> ok
> t/pmpath.t ... 
> 1..2
> ok 1 - pmpath runs
> ok 2 - found Tie::Hash
> ok
> t/pmvers.t ... 
> 1..2
> ok 1 - pmvers runs
> ok 2 - found version of Tie::Hash
> ok
> t/podgrep.t .. 
> 1..2
> ok 1 - podgrep runs
> ok 2 - found DESCRIPTION
> ok
> t/pods.t . 
> 1..2
> ok 1 - pods runs
> ok 2 - found Tie::Hash
> ok
> t/podtoc.t ... 
> 1..2
> ok 1 - podtoc runs
> ok 2 - found Table of Contents
> ok
> t/sitepods.t . 
> 1..1
> ok 1 - sitepods runs
> ok
> t/stdpods.t .. 
> 1..2
> ok 1 - stdpods runs
> ok 2 - found Tie::Hash
> ok
> 
> Test Summary Report
> ---
> t/pman.t   (Wstat: 256 Tests: 2 Failed: 1)
>   Failed test:  2
>   Non-zero exit status: 1
> Files=23, Tests=51,  3 wallclock secs ( 0.04 usr  0.03 sys +  2.14 cusr  0.41 
> csys =  2.62 CPU)
> Result: FAIL
> Failed 1/23 test programs. 1/51 subtests failed.
> make[2]: *** [Makefile:1077: test_dynamic] Error 255
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/pmtools_2.2.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pmtools
Source-Version: 2.2.0-2
Done: gregor herrmann 

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

A summary of the changes between this

Bug#965976: zeek: Uninstallable, needs to be rebuilt against newer libc6

2020-07-21 Thread Axel Beckert

Package: zeek
Version: 3.0.7+ds1-2
Severity: serious
X-Debbugs-Cc: Axel Beckert 

Hi Hilko,

zeek is currently uninstallable in Unstable and Testing as libc6 2.31
migrated to testing but zeek depends on "libc6 (<< 2.31)".

Or from a different point of view: I can't upgrade libc6 in Unstable due
to the zeek package being installed. ;-)

Please either schedule a binNMU or make a sourceful upload to get a
newer package built against the newer libc6.

P.S.: And thanks for bringing Bro/Zeek back in shape for Debian!

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zeek depends on:
ii  libbroker21.2.8+ds1-1
ii  libc6 2.30-8
ii  libcaf-core0.16.3 0.16.3-0.3
ii  libgcc-s1 10.1.0-6
ii  libgoogle-perftools4  2.8-1
ii  libkrb5-3 1.17-10
ii  libmaxminddb0 1.3.2-1
ii  libpcap0.81.9.1-4
ii  libsqlite3-0  3.32.3-1
ii  libssl1.1 1.1.1g-1
ii  libstdc++610.1.0-6
ii  zeek-common   3.0.7+ds1-2
ii  zlib1g1:1.2.11.dfsg-2

zeek recommends no packages.

zeek suggests no packages.

-- no debconf information

Bug#963408: marked as pending in pmtools

2020-07-21 Thread gregor herrmann

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/pmtools/-/commit/7d5cfa43be46e79172c7f85eb995fed37c608a07


Add patch to ignore modules in perl-base paths in pman.

Closes: #963408


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963408

Processed: Bug#963408 marked as pending in pmtools

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #963408 [src:pmtools] pmtools: FTBFS: dh_auto_test: error: make -j4 test 
TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.

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

Bug#964815:

2020-07-21 Thread ANTHONY Clark

Somebody hacking me

Bug#963046: marked as done (libcddb-get-perl: freedb server down)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 17:33:39 +
with message-id 
and subject line Bug#963046: fixed in libcddb-get-perl 2.28-3
has caused the Debian Bug report #963046,
regarding libcddb-get-perl: freedb server down
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.)


-- 
963046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcddb-get-perl
Version: 2.28-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the freedb.freedb.org server was switched off since April, so you can’t 
get any CD information anymore.

I found that you can use the gnudb.gnudb.org server.

Maybe you should change the default server.

Shade and sweet water!

Stephan


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

Kernel: Linux 5.7.2 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libcddb-get-perl depends on:
ii  perl  5.30.3-4

libcddb-get-perl recommends no packages.

libcddb-get-perl suggests no packages.

-- no debconf information

-- 
|If your life was a horse, you'd have to shoot it.|
--- End Message ---
--- Begin Message ---
Source: libcddb-get-perl
Source-Version: 2.28-3
Done: gregor herrmann 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Jul 2020 19:11:16 +0200
Source: libcddb-get-perl
Architecture: source
Version: 2.28-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 963046
Changes:
 libcddb-get-perl (2.28-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Ryan Niebur from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ Laurent Baillet ]
   * fix lintian file-contains-trailing-whitespace warning
 .
   [ gregor herrmann ]
   * Rename debian/NEWS.Debian to debian/NEWS to get it actually installed.
   * debian/watch: use uscan version 4.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 9 to 12.
   * Set debhelper-compat version in Build-Depends.
 .
   [ gregor herrmann ]
   * Add patch to replace freedb server with gnudb server.
 Thanks to Stephan Seitz for the bug report and Elimar Riesebieter for the
 patch. (Closes: #963046)
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
Checksums-Sha1:
 d800aa194dcdd149945d8c8d7d4761b5608b2470 2331 libcddb-get-perl_2.28-3.dsc
 fce91d5e80035ff15de8d6a52f8808ad4b73 4756 
libcddb-get-perl_2.28-3.debian.tar.xz
Checksums-Sha256:
 41f333b72eb348dd53c91f400adc30d5e49285ed4ec5cf38dbd87404674a4521 2331 
libcddb-get-perl_2.28-3.dsc
 9a449217f6dcdb16d9c4a13a74e2137e1b700ffeaf522169c21fad0e2dfa6599 4756 
libcddb-get-perl_2.28-3.debian.tar.xz
Files:
 4a3283d795f48fef5e5629c7c778c01c 2331 perl optional libcddb-get-perl_2.28-3.dsc
 10c590e6e8cd9107b4089c12105adb5e 4756 perl optional 
libcddb-get-perl_2.28-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl8XImhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaB7xAAtpuq2rhLXijusaW/KEJF0GSEqXicICd+dLN8w9ZD1m1U7q+u2stM9zqi
JQTDcDMD6QQbGvQNkTIa73lQGUIDwg5JDu3C26nRhqbdH8tuTjAVfh6viTWcu7f2
azkJe1b0YX6yx/3m20pwWGBagAHRrf1ddXiecmdc3th7ZVHTWn5n+yJynQe2rvdQ

Processed: Bug#963046 marked as pending in libcddb-get-perl

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #963046 [libcddb-get-perl] libcddb-get-perl: freedb server down
Added tag(s) pending.

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

Bug#963046: marked as pending in libcddb-get-perl

2020-07-21 Thread gregor herrmann

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libcddb-get-perl/-/commit/1e54c2291d48673eee3a53a48fdaae88ecfa583e


Add patch to replace freedb server with gnudb server.

Thanks: Stephan Seitz for the bug report and Elimar Riesebieter for the patch.
Closes: #963046


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963046

Bug#963314: marked as done (unattended-upgrades: FTBFS: AssertionError: 1 != 0)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 15:34:33 +
with message-id 
and subject line Bug#963314: fixed in unattended-upgrades 2.5
has caused the Debian Bug report #963314,
regarding unattended-upgrades: FTBFS: AssertionError: 1 != 0
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.)


-- 
963314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unattended-upgrades
Version: 2.4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test/packages/equivs.0Q38O3'
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>create-stamp debian/debhelper-build-stamp
>dh_testroot
>dh_prep
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_installdeb
>dh_gencontrol
>dh_md5sums
>dh_builddeb
> dpkg-deb: building package 'test-package' in '../test-package_1.3_all.deb'.
> make[4]: Leaving directory '/<>/test/packages/equivs.0Q38O3'
>  dpkg-genbuildinfo --build=binary
>  dpkg-genchanges --build=binary >../test-package_1.3_amd64.changes
> dpkg-genchanges: info: binary-only upload (no source code included)
>  dpkg-source --after-build .
> dpkg-buildpackage: info: binary-only upload (no source included)
> 
> The package has been created.
> Attention, the package has been created in the current directory,
> not in ".." as indicated by the message above!
>  Conffiles:
> dpkg-deb -I test-package_1.3_all.deb conffiles
> /etc/configuration-file/configuration-file
> make[3]: Leaving directory '/<>/test/packages'
> set -e; \
> find . -name 'test_*.py' | \
> while read file; do \
> if [ -x $file ]; then \
>   echo "Running $file with python3"; \
>   python3 $file 2>&1; \
>   echo "Running $file with python3-coverage"; \
>   python3 -m coverage run -a $file 2>&1; \
> fi \
> done
> Running ./test_log_install_progress.py with python3
> .
> --
> Ran 1 test in 0.001s
> 
> OK
> Running ./test_log_install_progress.py with python3-coverage
> .
> --
> Ran 1 test in 0.002s
> 
> OK
> Running ./test_regression.py with python3
> .
> --
> Ran 1 test in 0.002s
> 
> OK
> Running ./test_regression.py with python3-coverage
> .
> --
> Ran 1 test in 0.002s
> 
> OK
> Running ./test_on_battery.py with python3
> .
> --
> Ran 1 test in 0.003s
> 
> OK
> Running ./test_on_battery.py with python3-coverage
> .
> --
> Ran 1 test in 0.003s
> 
> OK
> Running ./test_logdir.py with python3
> ../test_logdir.py:44: ResourceWarning: unclosed file <_io.TextIOWrapper 
> name='/tmp/tmptfmv00lr/mylog/unattended-upgrades.log' mode='a' 
> encoding='UTF-8'>
>   logging.root.handlers = []
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> .
> --
> Ran 2 tests in 0.003s
> 
> OK
> Running ./test_logdir.py with python3-coverage
> ../test_logdir.py:44: ResourceWarning: unclosed file <_io.TextIOWrapper 
> name='/tmp/tmpj9m5f2sq/mylog/unattended-upgrades.log' mode='a' 
> encoding='UTF-8'>
>   logging.root.handlers = []
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> .
> --
> Ran 2 tests in 0.004s
> 
> OK
> Running ./test_motd.py with python3
> .
> --
> Ran 1 test in 0.001s
> 
> OK
> Running ./test_motd.py with python3-coverage
> .
> --
> Ran 1 test in 0.001s
> 
> OK
> Running ./test_pep8.py with python3
> ./../unattended-upgrade-shutdown:71:13: E741 ambiguous variable name 'l'
> F
> ==
> FAIL: test_pep8_clean (__main__.PackagePep8TestCase)
> --
> Traceback (most recent

Bug#965308: jackd won't start

2020-07-21 Thread Arnaldo Pirrone


Here it is,
See ya

Il 21/07/20 alle 15:25, Sebastian Ramacher ha scritto:

Hi,

and ldd -r /usr/bin/jackd?

Best

On 2020-07-21 14:38:37 +0200, Arnaldo Pirrone wrote:

Sure,
you can find it attached.

Il 19/07/20 alle 15:30, Sebastian Ramacher ha scritto:

Control: tags -1 + moreinfo

On 2020-07-19 10:14:58 +0200, Arnaldo Pirrone wrote:

Package: jackd2
Version: 1.9.14~dfsg-0.1
Severity: grave
X-Debbugs-Cc: it9...@gmail.com

Hi, after the update jackd is not starting anymore. Apparently this is related.

Sun Jul 19 10:05:53 2020: ERROR: Can't load "/usr/lib/x86_64-linux-
gnu/jack/jack_alsa.so": /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: undefined
symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE

I suspect this is caused by an old libjack library somewhere in
/usr/local. Could you please provide the output of

ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so

to confirm that?

Cheers

ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so
linux-vdso.so.1 (0x7ffd4e4f9000)
libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 
(0x7ffbd5f9)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ffbd5dc3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ffbd5c7f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ffbd5c65000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ffbd5aa)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ffbd5a9a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ffbd5a76000)
/lib64/ld-linux-x86-64.so.2 (0x7ffbd60e)
undefined symbol: _ZTIN4Jack15JackAudioDriverE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver4OpenEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver4OpenEjjbbiibPKcS2_jj
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver13SetSampleRateEj
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver7ProcessEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver9SetMasterEb  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver9GetMasterEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver8AddSlaveEPNS_19JackDriverInterfaceE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11RemoveSlaveEPNS_19JackDriverInterfaceE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver17ProcessReadSlavesEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver18ProcessWriteSlavesEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11ProcessReadEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver12ProcessWriteEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15ProcessReadSyncEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver16ProcessWriteSyncEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver16ProcessReadAsyncEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver17ProcessWriteAsyncEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZNK4Jack10JackDriver10IsRealTimeEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15SaveConnectionsEi   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15LoadConnectionsEib  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11StartSlavesEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver10StopSlavesEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver12ResumeRefNumEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver13SuspendRefNumEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZNK4Jack10JackDriver16GetClientControlEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver10InitializeEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZThn8_N4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZThn8_NK4Jack10JackDriver16GetClientControlEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack17JackServerGlobals17on_device_releaseE   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack17JackServerGlobals17on_device_acquireE

Bug#965954: marked as done (python3-matplotlib: import of library fails)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 15:04:29 +
with message-id 
and subject line Bug#965954: fixed in matplotlib 3.3.0-2
has caused the Debian Bug report #965954,
regarding python3-matplotlib: import of library fails
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.)


-- 
965954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-matplotlib
Version: 3.3.0-1
Severity: critical
X-Debbugs-Cc: none, J-V Peetz 

Dear Sandro Tosi,

in ipython3 the import of matplotlib.pyplot fails:

In[1]: import matplotlib.pyplot as plt

---
FileNotFoundError Traceback (most recent call last)
 in 
> 1 import matplotlib.pyplot as plt

/usr/lib/python3/dist-packages/matplotlib/__init__.py in 
897 # by explicitly calling the superclass (dict.update, dict.items) to 
avoid
898 # triggering resolution of _auto_backend_sentinel.
--> 899 rcParamsDefault = _rc_params_in_file(
900 cbook._get_data_path("matplotlibrc"),
901 # Strip leading comment.

/usr/lib/python3/dist-packages/matplotlib/__init__.py in
_rc_params_in_file(fname, transform, fail_on_error)
796 """
797 rc_temp = {}
--> 798 with _open_file_or_url(fname) as fd:
799 try:
800 for line_no, line in enumerate(fd, 1):

/usr/lib/python3.8/contextlib.py in __enter__(self)
111 del self.args, self.kwds, self.func
112 try:
--> 113 return next(self.gen)
114 except StopIteration:
115 raise RuntimeError("generator didn't yield") from None

/usr/lib/python3/dist-packages/matplotlib/__init__.py in 
_open_file_or_url(fname)
774 if encoding is None:
775 encoding = "utf-8"
--> 776 with open(fname, encoding=encoding) as f:
777 yield f
778

FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/matplotlib/mpl-data/matplotlibrc'

Any idea?

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.7.9 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python3-matplotlib depends on:
ii  libc6   2.30-8
ii  libfreetype62.10.2+dfsg-3
ii  libgcc-s1   10.1.0-6
ii  libjs-jquery3.5.1+dfsg-4
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libstdc++6  10.1.0-6
ii  python-matplotlib-data  3.3.0-1
ii  python3 3.8.2-3
ii  python3-cycler  0.10.0-3
ii  python3-dateutil2.8.1-4
ii  python3-kiwisolver  1.0.1-3+b1
ii  python3-numpy [python3-numpy-abi9]  1:1.19.0-1
ii  python3-pil 7.2.0-1
ii  python3-pyparsing   2.4.7-1
ii  python3-six 1.15.0-1

Versions of packages python3-matplotlib recommends:
ii  python3-tk  3.8.5-1

Versions of packages python3-matplotlib suggests:
ii  dvipng 1.15-1.1+b1
ii  ffmpeg 7:4.3-3+b1
ii  ghostscript9.52~dfsg-1
ii  gir1.2-gtk-3.0 3.24.20-1
ii  inkscape   1.0-3
ii  ipython3   7.16.1-1
ii  librsvg2-common2.48.7-1
pn  python-matplotlib-doc  
pn  python3-cairocffi  
ii  python3-gi 3.36.0-4
ii  python3-gi-cairo   3.36.0-4
pn  python3-gobject
pn  python3-nose   
pn  python3-pyqt5  
ii  python3-scipy  1.4.1-2
pn  python3-sip
ii  python3-tornado6.0.4-2
ii  texlive-extra-utils2020.20200629-1
ii  texlive-latex-extra2020.20200629-1
pn  ttf-staypuft   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 3.3.0-2
Done: Sandro Tosi 

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

Processed: Bug#965954 marked as pending in matplotlib

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #965954 [python3-matplotlib] python3-matplotlib: import of library fails
Ignoring request to alter tags of bug #965954 to the same tags previously set

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

Bug#965954: marked as pending in matplotlib

2020-07-21 Thread Sandro Tosi

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/matplotlib/-/commit/d728a2842311355eb39fc90c6f7e3eb00bf6cb4c


explicitly install matplotlibrc in /usr/share/matplotlib/mpl-data/; Closes: 
#965954


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/965954

Processed: limit source to matplotlib, tagging 965954

2020-07-21 Thread Debian Bug Tracking System

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

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

> tags 965954 + pending
Bug #965954 [python3-matplotlib] python3-matplotlib: import of library fails
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#964610: nibabel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 - upstream
Bug #964610 [src:nibabel] nibabel: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Removed tag(s) upstream.
> tags -1 pending
Bug #964610 [src:nibabel] nibabel: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Added tag(s) pending.

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

Bug#964610: nibabel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-07-21 Thread Andreas Tille

Control: tags -1 - upstream
Control: tags -1 pending

The build time test issue was solved thanks to upstream (switched from
nose to pytest).  Unfortunately there are now issues with sphinx to
build the docs.  My dirty workaroung did not worked so I simply added
' || true ' behind the sphinx call.  This needs to be sorted out before
uploading.

Moreover autopkgtest should be switched from nose to pytest.

Any help is welcome

  Andreas.

-- 
http://fam-tille.de

Bug#963347: gst-plugins-ugly1.0: FTBFS: Can't locate Regexp/Assemble.pm in @INC

2020-07-21 Thread Jonas Smedegaard

Package: cdbs
Followup-For: Bug #963347

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: affects -1 =
Control: reassign -1 src:gst-plugins-ugly1.0 1.16.2-2

cdbs provides templates for packages to include.
gst-plugins-ugly1.0 also build-depends on automake
even though it is called through a cdbs template.

cdbs offers an optional mechanism to help resolve build-dependencies,
but does not itself build-depend on the tools used in its templates.
If that was the case, then cdbs would depend on openjdk and php-dev
and cmake and a lot of other tools, which would not be helpful.

Concretely, src:gst-plugins-ugly1.0 uses the rules/utils.mk template
and need to either a) declare needed build-dependencies (which indeed has
changed over time¹), or supress unused parts (notably licensecheck),
or stop include /usr/share/cdbs/1/rules/utils.mk.

Hope that helps,


 - Jonas

¹ inadequate communication of the change to build-dependencies
is maybe worthy of a separate bugreport (not this bugreport)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8W86EACgkQLHwxRsGg
ASHNqw/8D3o9uCSUPzaC7JKmSmzxIKWj4UvIQddys+WC8F6sf0hCv8nx9bwpZhO+
98ClTFvKZlPmdb/IiSGPAAGPuc/kvwTaNGbnzZ5bDDLEW0peEnucpj5lKtbm00B/
v9WQoEZ7BDUrmhhVxULWERh/ZlfochhS1R0Gh50SE0ROQMP+dQoMBey9+R8BRRzT
clLDsKf+zC6i0JFf9XTgcS/QgFTIHffC5+UmjbrScBTkyCtN/tthMbj8kU2Z++FM
38jwvvKNu1z19sVtx043WHy+WqAEq+xA1KgRQ4nR9PGN5ccz2FkK9kKkaEsMwmFO
j/3DIFzn22Dq4p1A+4M+cseLL9432aKA6y1cQWZB11olNDGN3XYKrVDc8l+MzLPR
K3uosqxoobB4d0774/qOpadmtppQWHt3ao3HDDiavtEv6pllHkH/IQoHhiSOQhUf
mLO+r63H+4bTgYJaS3nmy0MBxlAXqF3d/TaA4wlBSalHn4v/W4pyQ1pvE2kY6FPz
Of/nb3izQx2WUjJy3AgVI9wWPpfq6+vNgtRnjSba4JwKNSwIiRQBy1AvSEQtSOL5
A5I0jnpW/uqmh1agnkUnG4Z/8ALiKmjjKPpeAlOOG0oha5BiSbRC03OQrX59dATs
atGm0PE4FR2OK/+RJoQZkXb3/AD49iFOdT8v1+vm+Vwp0oqv1wE=
=iv/m
-END PGP SIGNATURE-

Bug#965308: jackd won't start

2020-07-21 Thread Sebastian Ramacher

Hi,

and ldd -r /usr/bin/jackd?

Best

On 2020-07-21 14:38:37 +0200, Arnaldo Pirrone wrote:
> Sure,
> you can find it attached.
> 
> Il 19/07/20 alle 15:30, Sebastian Ramacher ha scritto:
> > Control: tags -1 + moreinfo
> > 
> > On 2020-07-19 10:14:58 +0200, Arnaldo Pirrone wrote:
> > > Package: jackd2
> > > Version: 1.9.14~dfsg-0.1
> > > Severity: grave
> > > X-Debbugs-Cc: it9...@gmail.com
> > > 
> > > Hi, after the update jackd is not starting anymore. Apparently this is 
> > > related.
> > > 
> > > Sun Jul 19 10:05:53 2020: ERROR: Can't load "/usr/lib/x86_64-linux-
> > > gnu/jack/jack_alsa.so": /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: 
> > > undefined
> > > symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE
> > I suspect this is caused by an old libjack library somewhere in
> > /usr/local. Could you please provide the output of
> > 
> > ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so
> > 
> > to confirm that?
> > 
> > Cheers
> 

> ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so
>   linux-vdso.so.1 (0x7ffd4e4f9000)
>   libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 
> (0x7ffbd5f9)
>   libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
> (0x7ffbd5dc3000)
>   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ffbd5c7f000)
>   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
> (0x7ffbd5c65000)
>   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ffbd5aa)
>   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ffbd5a9a000)
>   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
> (0x7ffbd5a76000)
>   /lib64/ld-linux-x86-64.so.2 (0x7ffbd60e)
> undefined symbol: _ZTIN4Jack15JackAudioDriverE
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver4OpenEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack15JackAudioDriver4OpenEjjbbiibPKcS2_jj  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack15JackAudioDriver13SetSampleRateEj  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack15JackAudioDriver7ProcessEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver9SetMasterEb
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver9GetMasterEv
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver8AddSlaveEPNS_19JackDriverInterfaceE
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: 
> _ZN4Jack10JackDriver11RemoveSlaveEPNS_19JackDriverInterfaceE
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver17ProcessReadSlavesEv   
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver18ProcessWriteSlavesEv  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver11ProcessReadEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver12ProcessWriteEv
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver15ProcessReadSyncEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver16ProcessWriteSyncEv
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver16ProcessReadAsyncEv
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver17ProcessWriteAsyncEv   
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZNK4Jack10JackDriver10IsRealTimeEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver15SaveConnectionsEi 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver15LoadConnectionsEib
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver11StartSlavesEv 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver10StopSlavesEv  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver12ResumeRefNumEv
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver13SuspendRefNumEv   
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii 
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZNK4Jack10JackDriver16GetClientControlEv   
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZN4Jack10JackDriver10InitializeEv  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZThn8_N4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol: _ZThn8_NK4Jack10JackDriver16GetClientControlEv  
> (/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
> undefined symbol:

Bug#965954: python3-matplotlib: import of library fails

2020-07-21 Thread Jörg-Volker Peetz

Package: python3-matplotlib
Version: 3.3.0-1
Severity: critical
X-Debbugs-Cc: none, J-V Peetz 

Dear Sandro Tosi,

in ipython3 the import of matplotlib.pyplot fails:

In[1]: import matplotlib.pyplot as plt

---
FileNotFoundError Traceback (most recent call last)
 in 
> 1 import matplotlib.pyplot as plt

/usr/lib/python3/dist-packages/matplotlib/__init__.py in 
897 # by explicitly calling the superclass (dict.update, dict.items) to 
avoid
898 # triggering resolution of _auto_backend_sentinel.
--> 899 rcParamsDefault = _rc_params_in_file(
900 cbook._get_data_path("matplotlibrc"),
901 # Strip leading comment.

/usr/lib/python3/dist-packages/matplotlib/__init__.py in
_rc_params_in_file(fname, transform, fail_on_error)
796 """
797 rc_temp = {}
--> 798 with _open_file_or_url(fname) as fd:
799 try:
800 for line_no, line in enumerate(fd, 1):

/usr/lib/python3.8/contextlib.py in __enter__(self)
111 del self.args, self.kwds, self.func
112 try:
--> 113 return next(self.gen)
114 except StopIteration:
115 raise RuntimeError("generator didn't yield") from None

/usr/lib/python3/dist-packages/matplotlib/__init__.py in 
_open_file_or_url(fname)
774 if encoding is None:
775 encoding = "utf-8"
--> 776 with open(fname, encoding=encoding) as f:
777 yield f
778

FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/matplotlib/mpl-data/matplotlibrc'

Any idea?

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.7.9 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python3-matplotlib depends on:
ii  libc6   2.30-8
ii  libfreetype62.10.2+dfsg-3
ii  libgcc-s1   10.1.0-6
ii  libjs-jquery3.5.1+dfsg-4
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libstdc++6  10.1.0-6
ii  python-matplotlib-data  3.3.0-1
ii  python3 3.8.2-3
ii  python3-cycler  0.10.0-3
ii  python3-dateutil2.8.1-4
ii  python3-kiwisolver  1.0.1-3+b1
ii  python3-numpy [python3-numpy-abi9]  1:1.19.0-1
ii  python3-pil 7.2.0-1
ii  python3-pyparsing   2.4.7-1
ii  python3-six 1.15.0-1

Versions of packages python3-matplotlib recommends:
ii  python3-tk  3.8.5-1

Versions of packages python3-matplotlib suggests:
ii  dvipng 1.15-1.1+b1
ii  ffmpeg 7:4.3-3+b1
ii  ghostscript9.52~dfsg-1
ii  gir1.2-gtk-3.0 3.24.20-1
ii  inkscape   1.0-3
ii  ipython3   7.16.1-1
ii  librsvg2-common2.48.7-1
pn  python-matplotlib-doc  
pn  python3-cairocffi  
ii  python3-gi 3.36.0-4
ii  python3-gi-cairo   3.36.0-4
pn  python3-gobject
pn  python3-nose   
pn  python3-pyqt5  
ii  python3-scipy  1.4.1-2
pn  python3-sip
ii  python3-tornado6.0.4-2
ii  texlive-extra-utils2020.20200629-1
ii  texlive-latex-extra2020.20200629-1
pn  ttf-staypuft   

-- no debconf information

Processed: reassigning bug to src:cdbs

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 src:cdbs
Bug #963347 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: FTBFS: Can't locate 
Regexp/Assemble.pm in @INC
Bug reassigned from package 'src:gst-plugins-ugly1.0' to 'src:cdbs'.
No longer marked as found in versions gst-plugins-ugly1.0/1.16.2-2.
Ignoring request to alter fixed versions of bug #963347 to the same values 
previously set
> affects -1 src:gst-plugins-ugly1.0
Bug #963347 [src:cdbs] gst-plugins-ugly1.0: FTBFS: Can't locate 
Regexp/Assemble.pm in @INC
Added indication that 963347 affects src:gst-plugins-ugly1.0
> found -1 0.4.162
Bug #963347 [src:cdbs] gst-plugins-ugly1.0: FTBFS: Can't locate 
Regexp/Assemble.pm in @INC
Marked as found in versions cdbs/0.4.162.

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

Bug#963347: reassigning bug to src:cdbs

2020-07-21 Thread Gianfranco Costamagna

control: reassign -1 src:cdbs
control: affects -1 src:gst-plugins-ugly1.0
control: found -1 0.4.162

Hello, looks like the new cdbs is using features of libregexp-assemble-perl 
without having a runtime dependency on it.
This makes gst-plugins-ugly1.0 FTBFS with the following error:

>  debian/rules build
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; find -- * -type f -regextype posix-extended '!' -regex '^(.+\.(|)|)$' 
> -regex '^.+\.(|)$' -print0 | perl -0 /usr/lib/cdbs/license-miner
> Can't locate Regexp/Assemble.pm in @INC (you may need to install the 
> Regexp::Assemble module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl) at /usr/lib/cdbs/license-miner 
> line 13.
> BEGIN failed--compilation aborted at /usr/lib/cdbs/license-miner line 13.
> make: *** [/usr/share/cdbs/1/rules/utils.mk:143: debian/copyright_newhints] 
> Error 2

Bug#965308: jackd won't start

2020-07-21 Thread Arnaldo Pirrone


Sure,
you can find it attached.

Il 19/07/20 alle 15:30, Sebastian Ramacher ha scritto:

Control: tags -1 + moreinfo

On 2020-07-19 10:14:58 +0200, Arnaldo Pirrone wrote:

Package: jackd2
Version: 1.9.14~dfsg-0.1
Severity: grave
X-Debbugs-Cc: it9...@gmail.com

Hi, after the update jackd is not starting anymore. Apparently this is related.

Sun Jul 19 10:05:53 2020: ERROR: Can't load "/usr/lib/x86_64-linux-
gnu/jack/jack_alsa.so": /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: undefined
symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE

I suspect this is caused by an old libjack library somewhere in
/usr/local. Could you please provide the output of

ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so

to confirm that?

Cheers


ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so
linux-vdso.so.1 (0x7ffd4e4f9000)
libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 
(0x7ffbd5f9)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ffbd5dc3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ffbd5c7f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ffbd5c65000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ffbd5aa)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ffbd5a9a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ffbd5a76000)
/lib64/ld-linux-x86-64.so.2 (0x7ffbd60e)
undefined symbol: _ZTIN4Jack15JackAudioDriverE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver4OpenEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver4OpenEjjbbiibPKcS2_jj
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver13SetSampleRateEj
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver7ProcessEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver9SetMasterEb  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver9GetMasterEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver8AddSlaveEPNS_19JackDriverInterfaceE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11RemoveSlaveEPNS_19JackDriverInterfaceE  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver17ProcessReadSlavesEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver18ProcessWriteSlavesEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11ProcessReadEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver12ProcessWriteEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15ProcessReadSyncEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver16ProcessWriteSyncEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver16ProcessReadAsyncEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver17ProcessWriteAsyncEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZNK4Jack10JackDriver10IsRealTimeEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15SaveConnectionsEi   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver15LoadConnectionsEib  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver11StartSlavesEv   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver10StopSlavesEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver12ResumeRefNumEv  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver13SuspendRefNumEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZNK4Jack10JackDriver16GetClientControlEv 
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack10JackDriver10InitializeEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZThn8_N4Jack15JackAudioDriver12ClientNotifyEiPKciiS2_ii  
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZThn8_NK4Jack10JackDriver16GetClientControlEv
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack17JackServerGlobals17on_device_releaseE   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack17JackServerGlobals17on_device_acquireE   
(/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so)
undefined symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE

Bug#964541: make: Regression on s390x, echo EPERM, caused by posix_spawn change

2020-07-21 Thread Julian Andres Klode

On Tue, Jul 21, 2020 at 12:49:59PM +0200, Christian Borntraeger wrote:
> On 21.07.20 10:18, Adrian Bunk wrote:
> > [ adding debian-s390 to Cc ]
> > 
> > On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote:
> >> Package: make-dfsg
> >> Version: 4.3-4
> >> Severity: serious
> >> Tags: patch
> >> User: ubuntu-de...@lists.ubuntu.com
> >> Usertags: origin-ubuntu groovy ubuntu-patch
> >>
> >> In Ubuntu, the attached patch was applied to achieve the following:
> >>
> >> The autopkgtests for flatpak-builder/s390x where failing with
> >>
> >>   echo Building
> >>   make: echo: Operation not permitted
> >>   make: *** [Makefile:2: all] Error 127
> 
> Julian,
> 
> is there a launchpad entry for the Ubuntu bug that was fixed by this change?

Yes, https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1886814, it's also
in the IBM bugzilla thingy - you can see Andreas Krebbel is replying to that.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#965951: twms fails to start

2020-07-21 Thread José Antonio Jiménez Madrid

Package: twms
Version: 0.07z-1
Severity: grave
Justification: renders package unusable

Dear sir/madam,

I have installed twms as I would like to server some maps following the wms
standard.

The twms package install flawlessly, but I cannot start the server.

I start the server with:

>systemctl start twms

without messages, but when I check the processes running in the system twms is
not there and also there is no new port open. Checking it status with:

> systemctl status twms

I get the following information:

---

 twms.service - twms web map service
   Loaded: loaded (/lib/systemd/system/twms.service; enabled; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Tue 2020-07-21 13:01:51 CEST; 1s
ago
  Process: 3647 ExecStart=/usr/bin/twms $PORT (code=exited, status=1/FAILURE)
 Main PID: 3647 (code=exited, status=1/FAILURE)

jul 21 13:01:51  twms[3647]: from twms import *
jul 21 13:01:51  twms[3647]:   File "/usr/lib/python3/dist-
packages/twms/twms.py", line 30, in 
jul 21 13:01:51  twms[3647]: config = imp.load_source("config",
config_path)
jul 21 13:01:51  twms[3647]:   File "/usr/lib/python3.7/imp.py", line 171,
in load_source
jul 21 13:01:51  twms[3647]: module = _load(spec)
jul 21 13:01:51  twms[3647]:   File "/etc/twms/twms.conf", line 8, in

jul 21 13:01:51  twms[3647]: import fetchers
jul 21 13:01:51  twms[3647]: ModuleNotFoundError: No module named
'fetchers'
jul 21 13:01:51  systemd[1]: twms.service: Main process exited,
code=exited, status=1/FAILURE
jul 21 13:01:51  systemd[1]: twms.service: Failed with result 'exit-code'.

--
(I have replaced the name of my system with ""

The file fetchers.py is located at
/usr/lib/python3/dist-packages/twms


I have not programmed in python since 10 years ago, I have forgotten a lot of
things, but I think it is a problem with the path where twms is looking for
modules.
I would appreciate all help to fix this problem and have twms working.

I am very happy to perform all the necessary tests to locate and fix the
problem.

Thanks for your great work !!!


Jose







-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages twms depends on:
ii  adduser3.118
ii  python33.7.3-1
ii  python3-pil5.4.1-2+deb10u1
ii  python3-webpy  1:0.39+20181101-1

Versions of packages twms recommends:
ii  python3-cairo   1.16.2-1+b1
ii  python3-pyproj  1.9.6-1

twms suggests no packages.

-- no debconf information

Bug#964541: make: Regression on s390x, echo EPERM, caused by posix_spawn change

2020-07-21 Thread Christian Borntraeger

On 21.07.20 10:18, Adrian Bunk wrote:
> [ adding debian-s390 to Cc ]
> 
> On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote:
>> Package: make-dfsg
>> Version: 4.3-4
>> Severity: serious
>> Tags: patch
>> User: ubuntu-de...@lists.ubuntu.com
>> Usertags: origin-ubuntu groovy ubuntu-patch
>>
>> In Ubuntu, the attached patch was applied to achieve the following:
>>
>> The autopkgtests for flatpak-builder/s390x where failing with
>>
>>   echo Building
>>   make: echo: Operation not permitted
>>   make: *** [Makefile:2: all] Error 127

Julian,

is there a launchpad entry for the Ubuntu bug that was fixed by this change?

>>
>> git bisect lead to
>>
>> commit 749a54d7a458dc6779936138caf40ce600a80052 (refs/bisect/bad)
>> Author: Aron Barath 
>> Date:   Mon Jul 9 09:05:31 2018 +0200
>>
>> * job.c (child_execute_job): Prefer posix_spawn() over fork()/exec()
>>
>> and I can confirm that disabling posix_spawn makes the autopkgtest
>> work again.
>>
>> Earlier research also indicated that this is a heisenbug, if I try
>> to print to stderr before printing to stdout, no issue occurs.
>>
>>   * Pass --disable-posix-spawn to configure, as use of posix_spawn()
>> causes a regression on s390x, with commands getting EPERM when
>> writing to stdout.
>> ...
> 
> Is posix_spawn() broken on s390x, or is this a bug in make?
> 
> The former would be really worrisome for a release architecture.

Bug#954190: marked as done (dh-runit: FTBFS on armhf due to shake testsuite failure)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 11:04:05 +
with message-id 
and subject line Bug#954190: fixed in dh-runit 2.9.0
has caused the Debian Bug report #954190,
regarding dh-runit: FTBFS on armhf due to shake testsuite failure
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.)


-- 
954190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-runit
Version: 2.8.15
Severity: serious
Tags: ftbfs
Justification: fails to build from source

According to build logs dh-runit FTBFS, but only on armhf. This is because
the testsuite exits nonzero. I can reproduce the error in the log [1]
inside an armhf chroot (created with debootstrap), but not on other 
architectures (amd64). 

To reproduce there is no need to build the package, just download dh-runit 
source inside
the chroot, make sure build-dep are installed, then do

root@lorenz:/home/extra/dh-runit-2.8.15# ghc testrunner.hs 
[1 of 1] Compiling Main ( testrunner.hs, testrunner.o )
Linking testrunner ...

root@lorenz:/home/extra/dh-runit-2.8.15# ./testrunner 
Error when reading Shake database .shake/.shake.database
  Witness type has disappeared, StepKey {4f23698ed1fc9a1a}
  CallStack (from HasCallStack):
error, called at src/Development/Shake/Internal/Core/Storage.hs:191:40 in 
shake-0.16.4-1RhwnB79ZHh8eiw92e7jMZ:Development.Shake.Internal.Core.Storage
All files will be rebuilt

# tar (for t/out/935997.tar)
# mv (for t/out/935997.tar)
# rm (for t/out/935997.log)
# mkdir (for t/out/935997.log)
[ and the test continue till the end]

Dear libghc-shake-dev maintainer, 
I'm not knowledgeble of shake: is this likely a bug in shake or a bug that 
need a fix on dh-runit side?

Thanks,
Lorenzo

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/dh-runit.html


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

Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages dh-runit depends on:
ii  debhelper12.9
ii  libfile-copy-recursive-perl  0.45-1
ii  libfile-slurp-perl   .29-1
ii  libtext-hogan-perl   2.01-1

dh-runit recommends no packages.

dh-runit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dh-runit
Source-Version: 2.9.0
Done: Lorenzo Puliti 

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

Debian distribution maintenance software
pp.
Lorenzo Puliti  (supplier of updated dh-runit 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, 03 Jul 2020 10:02:29 +0200
Source: dh-runit
Binary: dh-runit runit-helper
Architecture: source
Version: 2.9.0
Distribution: unstable
Urgency: medium
Maintainer: Lorenzo Puliti 
Changed-By: Lorenzo Puliti 
Description:
 dh-runit   - debhelper add-on to handle runit runscripts
 runit-helper - dh-runit implementation detail
Closes: 954190 964174 964175 964178
Changes:
 dh-runit (2.9.0) unstable; urgency=medium
 .
   * Add a comment on Conflicts and Breaks runit 2.1.2-36
   * Deprecate the 'since' option, bump depends on runit-helper
   * d/rules: clean testsuite artifacts
   * Disable the testsuite on armhf to workaroud FTBFS (Closes: #954190)
   * Acknowledge Helmut Grohne for fixing #939631
   * d/control: set Rules-Requires-Root: no
   * d/copyright: update copyright
   * Fix logservice failure due to loguser transition (Closes: #964175)
   * Avoid infinte loop of symlinks (Closes: #964174)
   * Print version in maintscript snippets
   * Do not overwrite the presubj file (Closes: #964178)
Checksums-Sha1:
 a6420f222a8d5021a74eccb39907961777aee6a6 1782 dh-runit_2.9.0.dsc

Bug#963046: libcddb-get-perl: freedb server down

2020-07-21 Thread Elimar Riesebieter

Control: tags -1 patch

* Stephan Seitz  [2020-06-18 12:18 +0200]:

> Package: libcddb-get-perl
> Version: 2.28-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> the freedb.freedb.org server was switched off since April, so you can’t 
> get any CD information anymore.
> 
> I found that you can use the gnudb.gnudb.org server.
> 
> Maybe you should change the default server.

Attached patch should fix the issue.

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)
From 81bbf0bf33736f9ff7df4030323148dc5049b36e Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Tue, 21 Jul 2020 11:55:24 +0200
Subject: [PATCH] Replace freedb server with gnudb server

---
 CDDB_get.pm | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/CDDB_get.pm b/CDDB_get.pm
index f446214..35e643d 100644
--- a/CDDB_get.pm
+++ b/CDDB_get.pm
@@ -66,9 +66,9 @@ my $CDROM_MSF=0x02;
 
 # default config
 
-my $CDDB_HOST = "freedb.freedb.org";
-my $CDDB_PORT = 8880;
-my $CDDB_MODE = "cddb";
+my $CDDB_HOST = "gnudb.gnudb.org";
+my $CDDB_PORT = 80;
+my $CDDB_MODE = "http";
 my $CD_DEVICE = "/dev/cdrom";
 
 my $HELLO_ID  = "root nowhere.com fastrip 0.77";
@@ -608,9 +608,9 @@ CDDB - Read the CDDB entry for an audio CD in your drive
 
  # following variables just need to be declared if different from defaults
 
- $config{CDDB_HOST}="freedb.freedb.org";	# set cddb host
- $config{CDDB_PORT}=8880;			# set cddb port
- $config{CDDB_MODE}="cddb";			# set cddb mode: cddb or http
+ $config{CDDB_HOST}="gnudb.gnudb.org";		# set cddb host
+ $config{CDDB_PORT}=80;			# set cddb port
+ $config{CDDB_MODE}="http";			# set cddb mode: cddb or http
  $config{CD_DEVICE}="/dev/cdrom";		# set cd device
 
  # user interaction welcome?
-- 
2.28.0.rc1



signature.asc
Description: PGP signature

Processed: Re: libcddb-get-perl: freedb server down

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #963046 [libcddb-get-perl] libcddb-get-perl: freedb server down
Added tag(s) patch.

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

Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

2020-07-21 Thread Andreas Tille

Hi Pranav,

On Mon, Jul 06, 2020 at 12:06:06PM +0300, Adrian Bunk wrote:
> 
> The actual problem is:
> Due to the dh compat bump in gff2aplot the gffread autopkgtest runs
> additional tests, and on two of these gffread is segfaulting.

I've checked the debdiff of the two binary packages in question
which are affected by the debhelper compat bump:

$ debdiff gff2aplot_2.0-11_amd64.deb gff2aplot_2.0-12_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/README
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.gff
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.sim
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.sim.gff
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.tblastx.gff
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs.fa
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/kk.sim
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/mm.fa
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.AG.hs-mm.gff
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.GT.hs-mm.gff
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.hs.gb
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.mm.gb
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/splice_sites/README
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/wublast/README
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.hs.gene.gb
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mm.gene.gb
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.blastn
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.blastn.full.gff
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.tblastx.aplot.gff
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.tblastx.gff

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/README.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.gff.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.sim.gff.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.sim.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/mhcregion/hs-mm.tblastx.gff.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/hs.fa.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/kk.sim.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/mhcregion/mm.fa.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.AG.hs-mm.gff.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.GT.hs-mm.gff.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.hs.gb.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/splice_sites/KCRB.mm.gb.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/splice_sites/README.gz
-rw-r--r--  root/root   /usr/share/doc/gff2aplot/examples/wublast/README.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.hs.gene.gb.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mm.gene.gb.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.blastn.full.gff.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.blastn.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.tblastx.aplot.gff.gz
-rw-r--r--  root/root   
/usr/share/doc/gff2aplot/examples/wublast/taf6.mmhs.genomic.tblastx.gff.gz

Control files: lines which differ (wdiff format)

Installed-Size: [-647-] {+1451+}
Version: [-2.0-11-] {+2.0-12+}


So the files are not compressed now any more.  Could you have
a look at the consequences this has on the test in gffread?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#964642: marked as done (ukui-greeter: FTBFS: Error copying /<>/ukui-greeter/resource/badges/pantheon_badge.png to /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/ba

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 10:06:42 +
with message-id 
and subject line Bug#964642: fixed in ukui-greeter 1.2.6-1
has caused the Debian Bug report #964642,
regarding ukui-greeter: FTBFS: Error copying 
/<>/ukui-greeter/resource/badges/pantheon_badge.png to 
/<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/pantheon_badge.png:
 Cannot create 
/<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/pantheon_badge.png
 for output
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.)


-- 
964642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-greeter
Version: 1.2.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/ukui-greeter'
> /usr/lib/qt5/bin/qmake -install qinstall -exe ukui-greeter 
> /<>/debian/ukui-greeter/usr/sbin/ukui-greeter
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/95-ukui-greeter.conf 
> /<>/debian/ukui-greeter/usr/share/lightdm/lightdm.conf.d/95-ukui-greeter.conf
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/ukui-greeter.conf 
> /<>/debian/ukui-greeter/etc/lightdm/ukui-greeter.conf
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/ukui-greeter.desktop 
> /<>/debian/ukui-greeter/usr/share/xgreeters/ukui-greeter.desktop
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/arrow_left.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/arrow_left.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/translations/es.qm 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/translations/es.qm
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/budgie_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/budgie_badge.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/arrow_left_active.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/arrow_left_active.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/translations/fr.qm 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/translations/fr.qm
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/gnome_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/gnome_badge.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/arrow_left_prelight.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/arrow_left_prelight.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/translations/pt.qm 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/translations/pt.qm
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/kde_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/kde_badge.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/arrow_right.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/arrow_right.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/translations/ru.qm 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/translations/ru.qm
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/lubuntu_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/lubuntu_badge.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/background-ubuntu.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/background-ubuntu.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/translations/zh_CN.qm 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/translations/zh_CN.qm
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/mate_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/mate_badge.png
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/ukui-greeter/resource/badges/pantheon_badge.png 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/pantheon_badge.png
> Error copying 
> /<>/ukui-greeter/resource/badges/pantheon_badge.png to 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/pantheon_badge.png:
>  Cannot create 
> /<>/debian/ukui-greeter/usr/share/ukui-greeter/images/badges/pantheon_badge.png
>  for

Bug#938774: viewmol: Python2 removal in sid/bullseye

2020-07-21 Thread Drew Parsons

Package: viewmol
Followup-For: Bug #938774

For those following the plight of viewmol, avogadro may be your best
substitute.  Its molecule building is not quite as intuitive as
viewmol but works well enough once you catch the rhythm of it (hold
and drag the mouse button to add a new atom bonded to an existing atom).

avogadro also has the nice feature of energy minimisation for geometry
optimisation (available from 1.93.0+git20200509.e169315-1), which
viewmol never provided. avogadro can also generate input files for
molecular dynamics computations.

Bug#963440: marked as done (kafkacat: FTBFS: dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${pre

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 09:33:53 +
with message-id 
and subject line Bug#963440: fixed in kafkacat 1.6.0-1
has caused the Debian Bug report #963440,
regarding kafkacat: FTBFS: dh_auto_configure: error: ./configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-json --enable-avro --no-download 
returned exit code 1
to be marked as done.

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

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


-- 
963440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kafkacat
Version: 1.5.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- --enable-json --enable-avro --no-download
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking --enable-json --enable-avro --no-download
> Unknown option disable-option-checking
> Usage: ./configure [OPTIONS...]
> 
>  mklove configure script - mklove, not autoconf
>  Copyright (c) 2014-2015 Magnus Edenhill - https://github.com/edenhill/mklove
> 
> Standard options:
>--prefix=PATHInstall arch-independent files in 
> PATH [/usr/local]
>--exec-prefix=PATH   Install arch-dependent files in PATH 
> [$prefix]
>--bindir=PATHUser executables [$exec_prefix/bin]
>--sbindir=PATH   System admin executables 
> [$exec_prefix/sbin]
>--libexecdir=PATHProgram executables 
> [$exec_prefix/libexec]
>--datadir=PATH   Read-only arch-independent data 
> [$prefix/share]
>--sysconfdir=PATHConfiguration data [$prefix/etc]
>--sharedstatedir=PATHModifiable arch-independent data 
> [$prefix/com]
>--localstatedir=PATH Modifiable local state data 
> [$prefix/var]
>--libdir=PATHLibraries [$exec_prefix/lib]
>--includedir=PATHC/C++ header files [$prefix/include]
>--infodir=PATH   Info documentation [$prefix/info]
>--mandir=PATHManual pages [$prefix/man]
> 
> Configure tool options:
>--list-modules   List loaded mklove modules
>--list-checksList checks
>--fail-fatal All failures are fatal
>--no-cache   Dont use or generate config.cache
>--debug  Enable configure debugging
>--clean  Remove generated configure files
>--reconfigureRerun configure with same arguments 
> as last run
>--no-downloadDisable downloads of required mklove 
> modules
>--update-modules Update modules from global repository
>--repo-url=URL_OR_PATH   Override mklove modules repo URL 
> [http://github.com/edenhill/mklove/raw/master]
>--help   Show configure usage
>--program-prefix=PFX Program prefix
> 
> Compatibility options:
>--enable-maintainer-mode Maintainer mode (no-op)
>--disable-maintainer-modeMaintainer mode (no-op)
>--disable-dependency-trackingDisable dependency tracking (no-op)
>--disable-silent-rules   Verbose build output (no-op)
> 
> Cross-compilation options:
>--host=HOST  Configure to build programs to run on 
> HOST (no-op)
>--build=BUILDConfigure for building on BUILD 
> (no-op)
>--target=TARGET  Configure for

Bug#962863: marked as done (r-cran-rdflib: autopkgtest regression)

2020-07-21 Thread Debian Bug Tracking System

Your message dated Tue, 21 Jul 2020 10:42:04 +0200
with message-id 

and subject line Re: [R-pkg-team] Bug#962863: r-cran-rdflib: autopkgtest 
regression
has caused the Debian Bug report #962863,
regarding r-cran-rdflib: autopkgtest regression
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.)

-- 
962863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rdflib
Version: 0.2.3+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime in the last month, r-cran-rdflib started to fail its own
autopkgtests [1].
There's a failing migration-reference/0 test in testing on 2020-05-22
which was before the new r-base migrated.

I've copied what I hope is the relevant part of the log below.

Regards
Graham

[1] https://ci.debian.net/packages/r/r-cran-rdflib/testing/amd64/

> library(testthat)
> library(rdflib)
>
> test_check("rdflib")
librdf error - XML parser error: Extra content at the end of the document
── 1. Error: @id is not a URI, we should get localhost (@test-parse-serialize.R#
jsonld.InvalidUrllist(code = "loading remote context failed", url =
"http://schema.org/;, cause = list())
Backtrace:
 1. rdflib::rdf_parse(ex, "jsonld")
 2. jsonld::jsonld_to_rdf(...)
 3. jsonld:::store_val()

── 2. Error: @id is a URI, we should not get localhost (@test-parse-serialize.R#
jsonld.InvalidUrllist(code = "loading remote context failed", url =
"http://schema.org/;, cause = list())
Backtrace:
 1. rdflib::rdf_parse(ex, "jsonld")
 2. jsonld::jsonld_to_rdf(...)
 3. jsonld:::store_val()

══ testthat results  ═══
[ OK: 55 | SKIPPED: 6 | WARNINGS: 0 | FAILED: 2 ]
1. Error: @id is not a URI, we should get localhost
(@test-parse-serialize.R#139)
2. Error: @id is a URI, we should not get localhost
(@test-parse-serialize.R#150)

Error: testthat unit tests failed
Execution halted
autopkgtest [06:40:45]: test run-unit-test: ---]
autopkgtest [06:40:45]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Hi Nilesh

On Mon, 20 Jul 2020 at 14:27, Nilesh Patra  wrote:
> In the test logs I observed that it _did_
> pass on July 15 after it again started to fail yet again - weirdly
> enough. Log here[1]
> Is it randomly failing here, or is it error at my end?
> I'm not sure, please let me know.
> This is tagged for removal within a week now, and hence it'd be great if
> I can get a response.

It seems to be passing in testing now.  Possibly fixed by the upload
of r-cran-jsonld/2.2+dfsg-1 ?   I'm closing this bug.

Regards
Graham--- End Message ---

Bug#964541: make: Regression on s390x, echo EPERM, caused by posix_spawn change

2020-07-21 Thread Adrian Bunk

[ adding debian-s390 to Cc ]

On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote:
> Package: make-dfsg
> Version: 4.3-4
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu groovy ubuntu-patch
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
> The autopkgtests for flatpak-builder/s390x where failing with
> 
>   echo Building
>   make: echo: Operation not permitted
>   make: *** [Makefile:2: all] Error 127
> 
> git bisect lead to
> 
> commit 749a54d7a458dc6779936138caf40ce600a80052 (refs/bisect/bad)
> Author: Aron Barath 
> Date:   Mon Jul 9 09:05:31 2018 +0200
> 
> * job.c (child_execute_job): Prefer posix_spawn() over fork()/exec()
> 
> and I can confirm that disabling posix_spawn makes the autopkgtest
> work again.
> 
> Earlier research also indicated that this is a heisenbug, if I try
> to print to stderr before printing to stdout, no issue occurs.
> 
>   * Pass --disable-posix-spawn to configure, as use of posix_spawn()
> causes a regression on s390x, with commands getting EPERM when
> writing to stdout.
>...

Is posix_spawn() broken on s390x, or is this a bug in make?

The former would be really worrisome for a release architecture.

cu
Adrian

Bug#960748: [Pkg-javascript-devel] Bug#960748: node-babel: meta bug to keep out of testing

2020-07-21 Thread Pirate Praveen




On 2020, ജൂലൈ 21 9:45:50 AM IST, peter green  wrote:
>> 
>> Last blockers for removal:
>> 
>> 1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch 
>> to 'berry'/2.x (supports babel 7) in time for bullseye
>> 2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by 
>> webpack
>> 3. rainloop - #960021 - not in bullseye
>> 
>> Once the blockers are fixed, this should be changed to an RM bug.
>
>It looks like several packages were missed that build-depend on the babeljs
>virtual package which is provided by node-babel-cli
>
>Namely (in testing, there may be others in unstable I don't know about)
>
>node-ramda
>node-globby
>node-rollup-plugin-buble
>
>Are these something you want to deal with centrally or should I file individual
>bug reports?
>

This is already fixed. node-babel7 now provides babeljs.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: Re: Bug#964610: nibabel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-07-21 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 upstream
Bug #964610 [src:nibabel] nibabel: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Added tag(s) upstream.
> tags -1 help
Bug #964610 [src:nibabel] nibabel: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Added tag(s) help.
> forwarded -1 https://github.com/nipy/nibabel/issues/937
Bug #964610 [src:nibabel] nibabel: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/nipy/nibabel/issues/937'.

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

Bug#964610: nibabel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-07-21 Thread Andreas Tille

Control: tags -1 upstream
Control: tags -1 help
Control: forwarded -1 https://github.com/nipy/nibabel/issues/937

53 matches

Mail list logo