date:20201019

Processing control commands:

> tags -1 unreproducible
Bug #972524 [src:monitoring-plugins] monitoring-plugins: FTBFS on buster 
(dh_compress)
Added tag(s) unreproducible.
> severity -1 important
Bug #972524 [src:monitoring-plugins] monitoring-plugins: FTBFS on buster 
(dh_compress)
Severity set to 'important' from 'serious'

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

Bug#972524: [Pkg-nagios-devel] Bug#972524: monitoring-plugins: FTBFS on buster (dh_compress)

2020-10-19 Thread Sebastiaan Couwenberg

Control: tags -1 unreproducible
Control: severity -1 important

Hi Jakob,

Thanks for reporting this issue, but unfortunately I cannot reproduce it.

Building 2.2-6 in a buster chroot works as expected:

 gbp clone \
 https://salsa.debian.org/nagios-team/pkg-monitoring-plugins.git
 git checkout -b buster debian/2.2-6
 gbp buildpackage --git-pbuilder \
  --git-dist=buster \
  --git-debian-branch=buster

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#972540: python3-torch: Depends on not-existing packages "3.8"

2020-10-19 Thread Norbert Preining

Package: python3-torch
Version: 1.6.0-3
Severity: grave

Hi,

it seems that something went havoc in the depends field and
python3-torch requests a package
3.8
which probably should have been a version number.

Best

Norbert

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

Kernel: Linux 5.9.1+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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-torch depends on:
pn  3.8 
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-15
pn  libgoogle-glog0v5   
pn  libonnx1
ii  libprotobuf23   3.12.3-2+b1
ii  libstdc++6  10.2.0-15
pn  libtorch1.6 
ii  python3 3.8.6-1
ii  python3-future  0.18.2-4
ii  python3-numpy [python3-numpy-abi9]  1:1.19.2-2+b1
ii  python3-pkg-resources   50.3.0-1
ii  python3-requests2.23.0+dfsg-2
ii  python3-six 1.15.0-1
ii  python3-yaml5.3.1-2+b1
ii  python3.8   3.8.6-1

Versions of packages python3-torch recommends:
pn  libtorch-dev  
ii  ninja-build   1.10.1-1

Versions of packages python3-torch suggests:
pn  python3-hypothesis  
ii  python3-pytest  4.6.11-1

Processed: Re: zfsutils-linux: No NMU binary compliant

Processing control commands:

> tag -1 patch
Bug #972327 [zfsutils-linux] zfsutils-linux: No NMU binary compliant
Added tag(s) patch.

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

Processed: Re: Bug#971214: elpy: FTBFS: tests failed

Processing control commands:

> tag -1 unreproducible
Bug #971214 [src:elpy] elpy: FTBFS: tests failed
Added tag(s) unreproducible.

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

Bug#971214: elpy: FTBFS: tests failed

2020-10-19 Thread Nicholas D Steeves

Control: tag -1 unreproducible
Justification: fixed via black-20.8b1-2

Hi Lucas,

Lucas Nussbaum  writes:

> Source: elpy
> Version: 1.34.0-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200926 ftbfs-bullseye
>

I believe this was due to #970901 in Black.  The failure logs are dated
2020-10-06, and the fix for Black was uploaded 2020-10-12.  At the
moment, due to hardware failure, I don't have access to my SSO
certificate and cannot schedule a rebuild for affected archs at

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

I just tried building against black-20.8b1-2, and this build was
successful.  If you or someone else could schedule a rebuild I would
very much appreciate it :-)  I've marked this bug unreproducible in the
meantime, and believe that a rebuild will confirm my results.

Thanks!
Nicholas

Bug#969648: BD-Uninstallable Re: dask, pandas 1.1


A bot wrote:

Dependency installability problem for dask on all:

dask build-depends on:
- python3-pandas:amd64 (>= 0.19.0)
dask build-depends on:
- python3-distributed:amd64
python3-distributed depends on:
- python3-dask:amd64 (>= 2.9.0)
python3-pandas conflicts with:
- python3-dask:amd64 (< 2.11.0+dfsg-1.1~)
I removed the python3-distributed build-dependency to break this cycle, 
but I've only tested that with my version.  It can be added back once we 
have an installable dask.

Bug#972205: arm-compute-library binary-all FTBFS: This package can only be built for armhf and arm64

2020-10-19 Thread Wookey

yes, the attempt in the package rules to avoid build failures on unsupported 
architectures actually was null in the debian context and just broke the 
ability to build the arch-all binaries on any architecture (needed for 
source-only uploads).

Fixed in 19.11-3, just uploaded.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Processed: closing 972205

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

> close 972205
Bug #972205 [src:arm-compute-library] arm-compute-library binary-all FTBFS: 
This package can only be built for armhf and arm64
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#972524: monitoring-plugins: FTBFS on buster (dh_compress)

2020-10-19 Thread Jakob Bohm

Source: monitoring-plugins
Version: 2.2-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

When trying to locally rebuild monitoring-plugins on a Buster system with the
build-depends installed, the build actually fails during dh_compress.

This was tried with both the version 22-6 packaged source and the suggested
git package source.

Steps to reproduce:

# LC_ALL=C aptitude build-depends monitoring-plugins
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
$ apt-get source monitoring-plugins
Reading package lists... Done
NOTICE: 'monitoring-plugins' packaging is maintained in the 'Git' version 
control system at:
https://salsa.debian.org/nagios-team/pkg-monitoring-plugins.git
Please use:
git clone https://salsa.debian.org/nagios-team/pkg-monitoring-plugins.git
to retrieve the latest (possibly unreleased) updates to the package.
Skipping already downloaded file 'monitoring-plugins_2.2-6.dsc'
Skipping already downloaded file 'monitoring-plugins_2.2.orig.tar.gz'
Skipping already downloaded file 'monitoring-plugins_2.2-6.debian.tar.xz'
Need to get 0 B of source archives.
dpkg-source: info: extracting monitoring-plugins in monitoring-plugins-2.2
dpkg-source: info: unpacking monitoring-plugins_2.2.orig.tar.gz
dpkg-source: info: unpacking monitoring-plugins_2.2-6.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 02_check_icmp_links
dpkg-source: info: applying 10_spell_fixes
dpkg-source: warning: diff 
'monitoring-plugins-2.2/debian/patches/10_spell_fixes' patches file 
monitoring-plugins-2.2/plugins-root/check_icmp.c more than once
dpkg-source: info: applying 11_check_dhcp_MSG_PEAK
dpkg-source: info: applying 12_check_apt_only_crit
dpkg-source: info: applying 13_check_apt_list_packages
dpkg-source: info: applying 14_mariadb
dpkg-source: info: applying 15_check_smtp_initialize
$ cd monitoring-plugins-2.2
.../monitoring-plugins-2.2$ fakeroot dpkg-buildpackage -b --no-sign

Expected results:
 Successful build

Actual results with monitoring-plugins_2.2-6.dsc

...
dh_compress -s
dh_compress: Compatibility levels before 9 are deprecated (level 5 in use)
dh_compress: -s/--same-arch is deprecated; please use -a/--arch instead
dh_compress: This feature will be removed in compat 12.
gzip: usr/share/doc/monitoring-plugins-standard/changelog.gz: No such file or 
directory
dh_compress: gzip -9nf usr/share/doc/monitoring-plugins-standard/changelog 
usr/share/doc/monitoring-plugins-standard/changelog.Debian returned exit code 1
gzip: usr/share/doc/monitoring-plugins-basic/changelog.gz: No such file or 
directory
dh_compress: gzip -9nf usr/share/doc/monitoring-plugins-basic/changelog 
usr/share/doc/monitoring-plugins-basic/changelog.Debian returned exit code 1
dh_compress: Aborting due to earlier error
make: *** [debian/rules:219: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
.../monitoring-plugins-2.2$

Actual results with a git checkout instead of the source package (HEAD
tag is c852ee9514a8d5c9fc497a944c8d7e4801223dca):

.../pkg-monitoring-plugins$ fakeroot dpkg-buildpackage -b --no-sign
...
dh_compress -i
gzip: usr/share/doc/monitoring-plugins/README.Debian.gz: No such file or 
directory
gzip: usr/share/doc/monitoring-plugins/changelog.gz: No such file or directory
dh_compress: gzip -9nf usr/share/doc/monitoring-plugins/README.Debian 
usr/share/doc/monitoring-plugins/changelog 
usr/share/doc/monitoring-plugins/changelog.Debian returned exit code 1
dh_compress: Aborting due to earlier error
make: *** [debian/rules:199: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
.../pkg-monitoring-plugins$

Note 1: System has been set up to also use the buster-backports repository
  for any packages there included.
Note 2: The git repository source no longer uses compat 5, but same failure
  still happens



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

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

Bug#972024: marked as done (python-geotiepoints ftbfs with python3.9 as supported python3 version)

Your message dated Tue, 20 Oct 2020 00:13:39 +
with message-id 
and subject line Bug#972024: fixed in python-geotiepoints 1.2.0-3
has caused the Debian Bug report #972024,
regarding python-geotiepoints ftbfs with python3.9 as supported python3 version
to be marked as done.

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

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


-- 
972024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-geotiepoints
Version: 1.2.0-2
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

[...]
creating build/temp.linux-x86_64-3.9/geotiepoints
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.9
-I/usr/lib/python3/dist-packages/numpy/core/include -c
geotiepoints/multilinear_cython.c -o
build/temp.linux-x86_64-3.9/geotiepoints/multilinear_cython.o -O3
In file included from /usr/include/python3.9/numpy/ndarraytypes.h:1822,
 from /usr/include/python3.9/numpy/ndarrayobject.h:12,
 from /usr/include/python3.9/numpy/arrayobject.h:4,
 from geotiepoints/multilinear_cython.c:584:
/usr/include/python3.9/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning
"Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API
NPY_1_7_API_VERSION" [-Wcpp]
   17 | #warning "Using deprecated NumPy API, disable it with " \
  |  ^~~
geotiepoints/multilinear_cython.c: In function ‘__Pyx_InitGlobals’:
geotiepoints/multilinear_cython.c:24682:1: warning: ‘PyEval_InitThreads’ is
deprecated [-Wdeprecated-declarations]
24682 | PyEval_InitThreads();
  | ^~
In file included from /usr/include/python3.9/Python.h:145,
 from geotiepoints/multilinear_cython.c:20:
/usr/include/python3.9/ceval.h:130:37: note: declared here
  130 | Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void);
  | ^~
geotiepoints/multilinear_cython.c: In function ‘__Pyx_modinit_type_init_code’:
geotiepoints/multilinear_cython.c:24742:25: error: ‘PyTypeObject’ {aka ‘struct
_typeobject’} has no member named ‘tp_print’
24742 |   __pyx_type___pyx_array.tp_print = 0;
  | ^
geotiepoints/multilinear_cython.c:24747:31: error: ‘PyTypeObject’ {aka ‘struct
_typeobject’} has no member named ‘tp_print’
24747 |   __pyx_type___pyx_MemviewEnum.tp_print = 0;
  |   ^
geotiepoints/multilinear_cython.c:24762:30: error: ‘PyTypeObject’ {aka ‘struct
_typeobject’} has no member named ‘tp_print’
24762 |   __pyx_type___pyx_memoryview.tp_print = 0;
  |  ^
geotiepoints/multilinear_cython.c:24775:35: error: ‘PyTypeObject’ {aka ‘struct
_typeobject’} has no member named ‘tp_print’
24775 |   __pyx_type___pyx_memoryviewslice.tp_print = 0;
  |   ^
--- End Message ---
--- Begin Message ---
Source: python-geotiepoints
Source-Version: 1.2.0-3
Done: Antonio Valentino 

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated 
python-geotiepoints 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: Sun, 18 Oct 2020 05:54:19 +
Source: python-geotiepoints
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Closes: 972024
Changes:
 python-geotiepoints (1.2.0-3) unstable; urgency=medium
 .
   * Force cython to re-generate geotiepoints/multilinear_cython.c
 (Closes: #972024).
Checksums-Sha1:
 5e69f045572f3badb427b6e26c398dff37631fb8 1664 python-geotiepoints_1.2.0-3.dsc

Bug#924937: marked as done (libpq5: OpenSSL license contamination of GPL reverse-dependencies)

Your message dated Tue, 20 Oct 2020 01:58:39 +0200
with message-id <2d1b0add-9a63-9ca4-f11d-8d89fed22...@debian.org>
and subject line Re: Bug#924937: OpenSSL license contamination of GPL 
reverse-dependencies
has caused the Debian Bug report #924937,
regarding libpq5: OpenSSL license contamination of GPL reverse-dependencies
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.)

-- 
924937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpq5
Version: 11.2-2
Severity: serious
Affects: bandwidthd-pgsql dballe inspircd libnss-pgsql2 libodb-pgsql-2.4 pmacct 
r-cran-rpostgresql saga sphinxsearch tora ulogd2-pgsql yubikey-server-c
Justification: renders many Debian packages undistributable

Hello,

It's come to my attention that in buster and unstable, packages which
build-depend on libpq-dev wind up linked against libpq5, which in turn
links against OpenSSL (libssl1.1).

This includes software which is licensed under the GPL and uses the
PostgreSQL APIs.

It is well understood that the OpenSSL license is not "compatible" with
the GPL (either version 2 or 3); and furthermore, Debian has long taken
the position that, unless a license exception is granted by the
copyright holders, a package which is distributed under the GPL must
only link to libraries whose licenses are also GPL-compatible in order
for it to be included in Debian.

I am opening this as a serious bug, since I believe this makes a large
and indeterminate number of packages non-distributable in buster.

See also bug 921488 which was the same situation but with MariaDB.

Based on a quick glance through the debian/copyright files of reverse
dependencies, I found the following packages that appear to generally be
licensed GPL-2 (only) for example and list no OpenSSL linking exception.
If I've accurately understood which licence applies in these cases, this
situation certainly cannot be resolved even with the upcoming OpenSSL
upstream relicense to Apache-2.0. Note that this is an indicative
non-exhaustive list only, based on some approximations and only sampling
to check accuracy; I haven't verified each one in detail.

bandwidthd-pgsql
dballe
inspircd
libnss-pgsql2
libodb-pgsql-2.4
pmacct
r-cran-rpostgresql
saga
sphinxsearch
tora
ulogd2-pgsql
yubikey-server-c

There are many more reverse dependencies licensed with GPL-2+, GPL-3,
etc, which suffer this redistributability until the relicensed OpenSSL
arrives in Debian.

Thanks,

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, 20 Oct 2020 01:16:07 +0200 Bastian Germann
 wrote:

> OpenSSL, cups, and libgcc are considered system libraries now:
> http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html.
> I guess this issue can be closed.

Right, doing so.

signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: Bug#972404: transition: KDEPIM 20.08 and Frameworks 5.74.0

Processing control commands:

> severity 972224 serious
Bug #972224 [zanshin] zanshin: FTBFS against KDEPIM 20.08
Severity set to 'serious' from 'normal'
> severity 972226 serious
Bug #972226 [kjots] kjots: FTBFS with KDEPIM 20.08
Severity set to 'serious' from 'normal'

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

Bug#924937: OpenSSL license contamination of GPL reverse-dependencies

2020-10-19 Thread Bastian Germann

On Wed, 27 Mar 2019 11:04:30 +0100 Christoph Berg 
wrote:> Re: Ansgar Burchardt 2019-03-20
<751a89074fcaa393f2cc26ff676e9e3434ecd706.ca...@43-1.org>
> > the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> > than just libpq5: just looking at a small sample of the direct rdeps of
> > libssl1.1, one can find the following GPL-licensed programs linking it:
> > 
> >   cryptsetup, wesnoth, mydumper, mupdf, gatling, kopete
> > 
> > Also amanda-client, validns as they contain patches in d/patches
> > licensed under the GPL.
> > 
> > There are probably lots more, especially when you start looking at
> > libraries (and their whole dependency trees).
> > 
> > There is also cups which was reported to switch to Apache-2 which is
> > also GPL-2-incompatible...  That has lots of rdeps too (including for
> > example all GTK applications).
> > 
> > Fedora treats OpenSSL as a "system library"[1].  I would guess they
> > might do the same for libcups too.
> > 
> > Ansgar
> > 
> >   [1] 
> > https://fedoraproject.org/wiki/Licensing:FAQ#What.27s_the_deal_with_the_OpenSSL_license.3F
> 
> Reassigning to ftp-master to get an answer on if this is a problem for
> Debian, or if we can invoke the system library exception, or other
> resolutions.
> 
> Christoph

OpenSSL, cups, and libgcc are considered system libraries now:
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html.
I guess this issue can be closed.

Bug#972207: marked as done (pymongo ftbfs with python3.9 as supported python3 version)

Your message dated Mon, 19 Oct 2020 23:19:21 +
with message-id 
and subject line Bug#972207: fixed in pymongo 3.11.0-1
has caused the Debian Bug report #972207,
regarding pymongo ftbfs with python3.9 as supported python3 version
to be marked as done.

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

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


-- 
972207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymongo
Version: 3.10.0-2
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9


==
FAIL: test_instantiation (test_custom_types.TestBSONTypeEnDeCodecs)
--
TypeError: Can't instantiate abstract class testcodec with abstract method
transform_python

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/test/test_custom_types.py", line 270, in 
test_instantiation
run_test(TypeEncoder, {'python_type': MyType,}, fail=True)
  File "/<>/test/test_custom_types.py", line 263, in run_test
codec()
AssertionError: "Can't instantiate abstract class .* with abstract methods .*"
does not match "Can't instantiate abstract class testcodec with abstract method
transform_python"

--
Ran 317 tests in 5.721s

FAILED (failures=1, skipped=125)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1:
python3.9 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned
exit code 13
make: *** [debian/rules:8: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2020-10-14T02:40:37Z

Finished

--- End Message ---
--- Begin Message ---
Source: pymongo
Source-Version: 3.11.0-1
Done: Federico Ceratto 

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated pymongo 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: Sat, 17 Oct 2020 22:23:41 +0100
Source: pymongo
Architecture: source
Version: 3.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 972207
Changes:
 pymongo (3.11.0-1) unstable; urgency=medium
 .
   [ Federico Ceratto ]
   * New upstream release
 .
   [ Stefano Rivera ]
   * Fix test failure on Python 3.9 (Closes: #972207)
   * Temporarily install __pycache__ directories, to appease dh_missing.
Checksums-Sha1:
 9b28ae798bf9c45e26a77fa463266979f20beff5 2423 pymongo_3.11.0-1.dsc
 8117d0ccddfb8947c58e6d3d4b037c12b6c2297a 773027 pymongo_3.11.0.orig.tar.gz
 8ab6efb3af84642b0dad0f0df9aa0b26952ce114 6876 pymongo_3.11.0-1.debian.tar.xz
 f854e7a9c4a189524c0cb49957552bc9a634353a 10007 pymongo_3.11.0-1_amd64.buildinfo
Checksums-Sha256:
 3c9a268fa7eaa08a8a23cc1010bce978ca10baf6782f24c25303a79ff9ee3364 2423 
pymongo_3.11.0-1.dsc
 0492725a6cd25c3f30ad00caa741a50d906070b7e7ec030c516a1c75003118cb 773027 
pymongo_3.11.0.orig.tar.gz
 f64c223a31fa64a6ea9e8a16c2c68e83e258b16325da554fa91742b075c0feaf 6876 
pymongo_3.11.0-1.debian.tar.xz
 669e6e8448a742384a5cffd5b6d25f089c0514562e4f6f624197a124045b3108 10007 
pymongo_3.11.0-1_amd64.buildinfo
Files:
 06c093ea8e2515d161ad2ea2bb161817 2423 python optional pymongo_3.11.0-1.dsc
 2a9377f24ee9cbd5f479d936567b0a63 773027 python optional 
pymongo_3.11.0.orig.tar.gz
 98811f5168235be4e2f10d18b7d89a88 6876 python optional 
pymongo_3.11.0-1.debian.tar.xz
 e1594ba36477c0240143dc24c43d0aaa 10007 python optional 
pymongo_3.11.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl+OGgwACgkQbzG8RPUX
fapUVhAAoqLuahApVqezW+w5OFrUVjKZvNvJG1m/ULGTRberLJP8eZR2pkvvYKWz

Bug#969648: dask, pandas 1.1


On 19/10/2020 20:07, Stefano Rivera wrote:

Hi Rebecca (2020.10.19_11:51:33_-0700)


Or maybe not an actual regression...it's a ~5e-7 difference and one of the
things the patch does (at around dask/dataframe/tests/test_rolling.py:270)
is _tighten_ the tolerance on that test.


Hrm, I didn't see that failure. Testing again on a 32bit arch to be
sure...


My log is from amd64, but I don't know if it's reproducible.

Bug#969648: marked as pending in dask


sorry, not any more.

On 19/10/2020 19:57, Rebecca N. Palmer wrote:

That looks like my earlier version, which fails with NameError.

Bug#969648: marked as pending in dask


That looks like my earlier version, which fails with NameError.

Bug#969648: dask, pandas 1.1

Or maybe not an actual regression...it's a ~5e-7 difference and one of 
the things the patch does (at around 
dask/dataframe/tests/test_rolling.py:270) is _tighten_ the tolerance on 
that test.


I have filed a separate bug (#972516) for the fsspec issues.

Processed: 967909

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

> retitle 967909 RM: editline; better options, no reverse dependencies
Bug #967909 [ftp.debian.org] RM: editline; better options; no reverse 
dependencies
Changed Bug title to 'RM: editline; better options, no reverse dependencies' 
from 'RM: editline; better options; no reverse dependencies'.
> severity 967909 normal
Bug #967909 [ftp.debian.org] RM: editline; better options, no reverse 
dependencies
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#969648: dask, pandas 1.1


I have now tested it.  (The dask tests are run in autopkgtest, not build.)

The attached is what I have so far, but it had these failures.  The 
first two happen with or without 969648.patch and (from debci results) 
appear to be triggered by the new fsspec, but the last is a *regression* 
caused by this patch.


=== FAILURES 
===
_ test_errors 
__


dir_server = '/tmp/tmpuxg_g6b8'

def test_errors(dir_server):
f = open_files("http://localhost:8999/doesnotexist;)[0]
with pytest.raises(requests.exceptions.RequestException):
with f as f:
>   f.read()

/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:117:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

/usr/lib/python3/dist-packages/fsspec/implementations/http.py:343: in read
self._fetch_all()
/usr/lib/python3/dist-packages/fsspec/asyn.py:121: in wrapper
return maybe_sync(func, self, *args, **kwargs)
/usr/lib/python3/dist-packages/fsspec/asyn.py:100: in maybe_sync
return sync(loop, func, *args, **kwargs)
/usr/lib/python3/dist-packages/fsspec/asyn.py:71: in sync
raise exc.with_traceback(tb)
/usr/lib/python3/dist-packages/fsspec/asyn.py:55: in f
result[0] = await future
/usr/lib/python3/dist-packages/fsspec/implementations/http.py:360: in 
async_fetch_all

r.raise_for_status()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _


self = http://localhost:8999/doesnotexist) [404 File not 
found]>
GMT', 'Connection': 'close', 'Content-Type': 'text/html;charset=utf-8', 
'Content-Length': '469')>



def raise_for_status(self) -> None:
if 400 <= self.status:
# reason should always be not None for a started response
assert self.reason is not None
self.release()
>   raise ClientResponseError(
self.request_info,
self.history,
status=self.status,
message=self.reason,
headers=self.headers)
E   aiohttp.client_exceptions.ClientResponseError: 404, 
message='File not found', url=URL('http://localhost:8999/doesnotexist')


/usr/lib/python3/dist-packages/aiohttp/client_reqrep.py:941: 
ClientResponseError
- Captured stderr call 
-

127.0.0.1 - - [19/Oct/2020 17:38:10] code 404, message File not found
127.0.0.1 - - [19/Oct/2020 17:38:10] "HEAD /doesnotexist HTTP/1.1" 404 -
127.0.0.1 - - [19/Oct/2020 17:38:10] code 404, message File not found
127.0.0.1 - - [19/Oct/2020 17:38:10] "GET /doesnotexist HTTP/1.1" 404 -
 test_urlpath_inference_errors 
_


def test_urlpath_inference_errors():
# Empty list
with pytest.raises(ValueError, match="empty"):
get_fs_token_paths([])

# Protocols differ
with pytest.raises(ValueError, match="the same protocol"):
get_fs_token_paths(["s3://test/path.csv", "/other/path.csv"])

# Options differ
with pytest.raises(ValueError, match="the same file-system 
options"):

get_fs_token_paths(
[
"ftp://myu...@node.com/test/path.csv;,
"ftp://otheru...@node.com/other/path.csv;,
]
)

# Unknown type
with pytest.raises(TypeError):
>   get_fs_token_paths(
{
"sets/are.csv",
"unordered/so/they.csv",
"should/not/be.csv",
"allowed.csv",
}
)
E   Failed: DID NOT RAISE 

/usr/lib/python3/dist-packages/dask/bytes/tests/test_local.py:86: Failed
__ test_time_rolling_methods[window3-std-args6-True] 
___


method = 'std', args = (), window = <5 * Seconds>, check_less_precise = {}

@pytest.mark.parametrize(
"method,args,check_less_precise", 
rolling_method_args_check_less_precise

)
@pytest.mark.parametrize("window", ["1S", "2S", "3S", 
pd.offsets.Second(5)])
def test_time_rolling_methods(method, args, window, 
check_less_precise):

if dd._compat.PANDAS_GT_110:
check_less_precise = {}
else:
check_less_precise = {"check_less_precise": check_less_precise}

# DataFrame
if method == "apply":
kwargs = {"raw": False}
else:
kwargs = {}
prolling = ts.rolling(window)
drolling = dts.rolling(window)
>   assert_eq(
getattr(prolling, method)(*args, **kwargs),
getattr(drolling, method)(*args, **kwargs),
**check_less_precise,
)

/usr/lib/python3/dist-packages/dask/dataframe/tests/test_rolling.py:288:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Processed: reassign 967909; better options exist; no reverse dependencies

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

> retitle 967909 RM: editline; better options; no reverse dependencies
Bug #967909 [src:editline] editline: Please remove in favour of libedit
Changed Bug title to 'RM: editline; better options; no reverse dependencies' 
from 'editline: Please remove in favour of libedit'.
> reassign 967909 ftp.debian.org
Bug #967909 [src:editline] RM: editline; better options; no reverse dependencies
Bug reassigned from package 'src:editline' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #967909 to the same values 
previously set
Ignoring request to alter fixed versions of bug #967909 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#970111: enigmail: Upgrade to migration version 2.2.x for Thunderbird 78

2020-10-19 Thread Bastian Germann

On Tue, 6 Oct 2020 13:04:24 +0200 Gregor Riepl  wrote:
> Thunderbird 78.3.1 is now in unstable, and without Enigmail 2.2,
> existing users may lose their existing configuration.
> 
> Please consider uploading the migration wizard (i.e. Enigmail 2.2) as
> soon as possible.

enigmail seems to be the only package keeping thunderbird from migrating
to testing. I second the asap request.

Bug#951389: marked as done (akonadi-backend-postgresql: Initialisation of database fail if locale en_US.UTF8 is not avalaible systemwide)

Your message dated Mon, 19 Oct 2020 23:42:09 +0200
with message-id <2805746.mKCIRZJcHu@tuxin>
and subject line Re: Bug#951389: akonadi-backend-postgresql: Initialisation of 
database fail if locale  en_US.UTF8 is not avalaible systemwide
has caused the Debian Bug report #951389,
regarding akonadi-backend-postgresql: Initialisation of database fail if locale 
 en_US.UTF8 is not avalaible systemwide
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.)

-- 
951389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akonadi-backend-postgresql
Version: 4:19.08.3-1
Severity: grave
Justification: renders package unusable
Tags: l10n patch
forwarded: https://bugs.kde.org/show_bug.cgi?id=417721

Dear Maintainer,

The creation of database fail if locale en_US.UTF8 is not installed systemwise 
(by pulling
locale-all package for instance).

Indeed akonadi create database by using --locale en_US.UTF8
(see 
https://github.com/KDE/akonadi/blob/8aca730125ad247014868ba6e4cc530f4209619a/src/server/storage/dbconfigpostgresql.cpp#L297
and 
https://github.com/KDE/akonadi/blob/8aca730125ad247014868ba6e4cc530f4209619a/src/server/storage/dbconfigpostgresql.cpp#L484

correct flags will be: -E UTF8 --no-locale   
that does not need to install a locale systemwise and is safe

Thanks

Bastien

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 4:20.08.2-1

Upstream has fixed this within the 20.08.2 release.

hefee

--
On Samstag, 15. Februar 2020 21:38:43 CEST Bastien Roucariès wrote:
> Package: akonadi-backend-postgresql
> Version: 4:19.08.3-1
> Severity: grave
> Justification: renders package unusable
> Tags: l10n patch
> forwarded: https://bugs.kde.org/show_bug.cgi?id=417721
> 
> Dear Maintainer,
> 
> The creation of database fail if locale en_US.UTF8 is not installed
> systemwise (by pulling locale-all package for instance).
> 
> Indeed akonadi create database by using --locale en_US.UTF8
> (see
> https://github.com/KDE/akonadi/blob/8aca730125ad247014868ba6e4cc530f4209619
> a/src/server/storage/dbconfigpostgresql.cpp#L297 and
> https://github.com/KDE/akonadi/blob/8aca730125ad247014868ba6e4cc530f4209619a
> /src/server/storage/dbconfigpostgresql.cpp#L484
> 
> correct flags will be: -E UTF8 --no-locale
> that does not need to install a locale systemwise and is safe
> 
> Thanks
> 
> Bastien

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

Bug#907496: marked as done (libcurlpp0: Always fails with "No URL set!")

Your message dated Mon, 19 Oct 2020 21:49:24 +
with message-id 
and subject line Bug#907496: fixed in curlpp 0.8.1-3
has caused the Debian Bug report #907496,
regarding libcurlpp0: Always fails with "No URL set!"
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.)


-- 
907496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurlpp0
Version: 0.8.1-2+b1
Severity: grave
Justification: renders package unusable

libcurlpp0 appears to always fail with a "No URL set!" error message.
I only tested the "Easy" API.

For example even the first example in its repo

doesn't work:

$ g++ -Wall example00.cpp `curlpp-config --cflags --libs` `curl-config --cflags 
--libs`
$ ./a.out 
No URL set!

I recompiled libcurlpp using both 7 & 8[1] and when linking the example program 
to
the new build it works fine (both static & dynamic libs). So I'm not sure where
the problem lies but even after reinstalling the Debian package I could only get
it to work with my local libcurlpp.

[1] GCC package versions:
g++-7: 7.3.0-28
g++-8: 4:8.2.0-1

-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libcurlpp0 depends on:
ii  libc6   2.27-5
ii  libcurl47.61.0-1
ii  libgcc1 1:8.2.0-4
ii  libstdc++6  8.2.0-4

libcurlpp0 recommends no packages.

libcurlpp0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: curlpp
Source-Version: 0.8.1-3
Done: =?utf-8?q?Alo=C3=AFs_Micard?= 

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

Debian distribution maintenance software
pp.
Aloïs Micard  (supplier of updated curlpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2020 22:37:23 +0200
Source: curlpp
Architecture: source
Version: 0.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Aloïs Micard 
Changed-By: Aloïs Micard 
Closes: 907496 907733
Changes:
 curlpp (0.8.1-3) unstable; urgency=medium
 .
   * Make myself maintainer. (Closes: #907733)
   * Bump debhelper compat.
   * Mark libcurl4-nss-dev as conflict. (Closes: #907496)
Checksums-Sha1:
 39394f98b20240aaadd999487aff0cd8284aa7f5 2047 curlpp_0.8.1-3.dsc
 ca1ec182941867560042442619f5ce6d366209bf 4100 curlpp_0.8.1-3.debian.tar.xz
 0138d26f4de70602525b109ea4d7292c3ea9a66c 7110 curlpp_0.8.1-3_amd64.buildinfo
Checksums-Sha256:
 6f17393fbffb1909f1ce93486876d16c9c23cb8173d956e6ce39a39c62245f68 2047 
curlpp_0.8.1-3.dsc
 ac8dd17b1050d8194fb14e0ab261c841fbead9772fe5fefc93c34327382f1c68 4100 
curlpp_0.8.1-3.debian.tar.xz
 180e74ea8ab2b84a2f708f08c49172238d8616eca82886fda42f13ec56399bc6 7110 
curlpp_0.8.1-3_amd64.buildinfo
Files:
 c0ac674c239d48abef0a9305d2193e46 2047 libs optional curlpp_0.8.1-3.dsc
 6be9c4c57fb56ebd378d804a5dd0a8a7 4100 libs optional 
curlpp_0.8.1-3.debian.tar.xz
 2b59804aa1ffa96a2b77aba8208d679d 7110 libs optional 
curlpp_0.8.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECYc16JDXWgmzZBaOGg64LwcfXv4FAl+OBhwQHGFsb2lzQG1p
Y2FyZC5sdQAKCRAaDrgvBx9e/luND/9vK5JiZyKmnG6rZzgYFfADXlb2Nh7OEWIg
2bl4r8GBIG6pn3t6pszZe4LmPHBSfK4PgliA4LXnA/LvE00xrPh+shY9G06nCrKQ
rcHcLDpdQ/tu6VTotTl4ntQ6f1rXMDgrVcs8L+z0JAi4YTq/P9f0nHg89wX21zuo
B2TumCaJRptxT9drnhqwYpCLPdI7Bsas7wLHOGJOJWJl7Vjt8hfQzy728/as6DuE
RijTxJ2cKfNLjDheJPtQCf3EBdCpTLfy5sCaBuIuda+m6PpPyVWn686ZQB5USI0V
JDj1e4ejwuGG7zPiYjDBUqZaNE8aW+k7qO1DorBOi932cku3/s/1qlmQzoQhze5k
GJ5ogrrjvwmijcKx+t4G9CHYvhu4bMlIy+H7jZjNSflyTK6Ppj/ubmDuMlL+lHJD
0nSts39V7OTtR2r7xplxB1+YV9rThAJ3rBgX8lfbX6uDVFlff9oJkWX3zVM2FWCm

Bug#951388: marked as done ([akonadi-backend-postgresql] apparmor profile unsuitable)

Your message dated Mon, 19 Oct 2020 23:38:57 +0200
with message-id <2301010.GHar0l7m0l@tuxin>
and subject line Re: Bug#951388: [akonadi-backend-postgresql] apparmor profile 
unsuitable
has caused the Debian Bug report #951388,
regarding [akonadi-backend-postgresql] apparmor profile unsuitable
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.)


-- 
951388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akonadi-backend-postgresql
Version: 4:19.08.3-1
Severity: grave
Justification: renders package unusable
Tags: patch

Dear Maintainer,

Please find the following update for apparmor 

Please apply

Bastiendiff --git a/apparmor.d/postgresql_akonadi b/apparmor.d/postgresql_akonadi
index c25fa08..b650612 100644
--- a/apparmor.d/postgresql_akonadi
+++ b/apparmor.d/postgresql_akonadi
@@ -5,21 +5,27 @@
 
 profile postgresql_akonadi {
   #include 
+  #include 
   #include 
 
   capability setgid,
   capability setuid,
 
+  signal receive set=kill peer=/usr/bin/akonadiserver,
+  signal receive set=term peer=/usr/bin/akonadiserver,
+
   /etc/passwd r,
+
   /{usr/,}bin/dash mrix,
   /{usr/,}bin/locale mrix,
+  /{var/,}run/systemd/resolve/resolv.conf r,
   /usr/lib/postgresql/*/bin/initdb mrix,
   /usr/lib/postgresql/*/bin/pg_ctl mrix,
   /usr/lib/postgresql/*/bin/postgres mrix,
+  /usr/lib/postgresql/*/bin/pg_upgrade mrix,
   /usr/share/postgresql/** r,
   owner /dev/shm/PostgreSQL.* rw,
   owner @{xdg_data_home}/akonadi/** rwlk,
-  owner @{xdg_data_home}/akonadi/db_data/** l,
 
   # Site-specific additions and overrides. See local/README for details.
   #include 
diff --git a/apparmor.d/usr.bin.akonadiserver b/apparmor.d/usr.bin.akonadiserver
index 2055a49..8a8cc23 100644
--- a/apparmor.d/usr.bin.akonadiserver
+++ b/apparmor.d/usr.bin.akonadiserver
@@ -13,7 +13,8 @@
 
   signal send set=kill peer=mysqld_akonadi,
   signal send set=term peer=mysqld_akonadi,
-
+  signal send set=kill peer=postgresql_akonadi,
+  signal send set=term peer=postgresql_akonadi,
 
   /etc/xdg/** r,
   /usr/bin/akonadiserver mr,
@@ -32,7 +33,7 @@
   owner @{xdg_config_home}/akonadi* rw,
   owner @{xdg_config_home}/QtProject/qtlogging.ini r,
   owner @{xdg_config_home}/akonadi/ rw,
-  owner @{xdg_config_home}/akonadi/* rwl,
+  owner @{xdg_config_home}/akonadi/** rwl,
   owner @{xdg_config_home}/akonadi/akonadiconnectionrc wl,
   owner @{xdg_config_home}/akonadi/akonadiconnectionrc.lock rwk,
   owner @{xdg_config_home}/akonadi/akonadiserverrc.lock rwk,
@@ -44,6 +45,8 @@
   owner @{xdg_data_home}/akonadi/** rwk,
   owner @{PROC}/@{pid}/loginuid r,
   owner @{PROC}/@{pid}/mounts r,
+  owner /{,var/}run/user/[0-9]*/akonadi/ w,
+  owner /{,var/}run/user/[0-9]*/akonadi/** rw,
 
   # Site-specific additions and overrides. See local/README for details.
   #include 


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version:  4:20.08.2-1

Upstream has accepted the patch and released 20.08.2.

hefee

--
On Samstag, 15. Februar 2020 21:08:15 CEST Bastien Roucariès wrote:
> Package: akonadi-backend-postgresql
> Version: 4:19.08.3-1
> Severity: grave
> Justification: renders package unusable
> Tags: patch
> 
> Dear Maintainer,
> 
> Please find the following update for apparmor
> 
> Please apply
> 
> Bastien



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

Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9

2020-10-19 Thread Markus Koschany


Am 19.10.20 um 23:33 schrieb Joachim Wuttke:
> Markus:
> 
> Further investigation shows that the problem is not with NumPy.
> CMake not even finds Python.h.
> 
> The problem is most likely a mixture of Python 3.8 and 3.9 files on your
> system.
> 
> Try to uninstall libpython3-dev, which still depends on 3.8.
> 
> Good luck, Joachim

I built siconos in a clean chroot environment. The recent rebuild of
siconos also shows build failures

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

I don't think it's specific to my environment.

Cheers,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#971274: marked as done (webext-compactheader: not compatible with thunderbird 78)

Your message dated Mon, 19 Oct 2020 21:34:53 +
with message-id 
and subject line Bug#972413: Removed package(s) from unstable
has caused the Debian Bug report #971274,
regarding webext-compactheader: not compatible with thunderbird 78
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.)


-- 
971274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-compactheader
Version: 3.0.0~beta5-2
Severity: grave
Control: forwarded -1 https://github.com/jmozmoz/compactheader/issues/42

After upgrading thunderbird from 68 to 78, it deactivated the
CompactHeader extension as incompatible.

Perhaps it should be replaced by
https://addons.thunderbird.net/en-US/thunderbird/addon/compact-headers/ ?


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

Kernel: Linux 5.9.0-rc7-nouveau (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages webext-compactheader depends on:
ii  thunderbird  1:78.3.1-1

webext-compactheader recommends no packages.

webext-compactheader suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.0.0~beta5-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#947113: marked as done (lout: CVE-2019-19917 CVE-2019-19918)

Your message dated Mon, 19 Oct 2020 21:33:55 +
with message-id 
and subject line Bug#972182: Removed package(s) from unstable
has caused the Debian Bug report #947113,
regarding lout: CVE-2019-19917 CVE-2019-19918
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.)


-- 
947113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lout
Version: 3.39-3
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for lout.

CVE-2019-19917[0]:
| Lout 3.40 has a buffer overflow in the StringQuotedWord() function in
| z39.c.


CVE-2019-19918[1]:
| Lout 3.40 has a heap-based buffer overflow in the srcnext() function
| in z02.c.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19917
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19917
[1] https://security-tracker.debian.org/tracker/CVE-2019-19918
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19918

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 3.39-3+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9

2020-10-19 Thread Joachim Wuttke


Markus:

Further investigation shows that the problem is not with NumPy.
CMake not even finds Python.h.

The problem is most likely a mixture of Python 3.8 and 3.9 files on your system.

Try to uninstall libpython3-dev, which still depends on 3.8.

Good luck, Joachim



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#957121: marked as done (dbacl: ftbfs with GCC-10)

Your message dated Mon, 19 Oct 2020 21:33:12 +
with message-id 
and subject line Bug#972117: Removed package(s) from unstable
has caused the Debian Bug report #957121,
regarding dbacl: ftbfs with GCC-10
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.)


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dbacl_1.14.1-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
cat hmine.1in \
| sed -e "s|[@]VERSION@|1.14.1|g" \
| sed -e "s|[@]PKGDATADIR@|/usr/share/dbacl|g" \
| sed -e "s|[@]PKGDOCDIR@|/usr/share/doc/dbacl|g" \
> hmine.1
cat hypex.1in \
| sed -e "s|[@]VERSION@|1.14.1|g" \
| sed -e "s|[@]PKGDATADIR@|/usr/share/dbacl|g" \
| sed -e "s|[@]PKGDOCDIR@|/usr/share/doc/dbacl|g" \
> hypex.1
make[3]: Leaving directory '/<>/man'
Making all in ts
make[3]: Entering directory '/<>/ts'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/ts'
Making all in TREC
make[3]: Entering directory '/<>/TREC'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/TREC'
Making all in contrib
make[3]: Entering directory '/<>/contrib'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/contrib'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test
make -j4 check VERBOSE=1
make[1]: Entering directory '/<>'
Making check in doc
make[2]: Entering directory '/<>/doc'
Making check in chess
make[3]: Entering directory '/<>/doc/chess'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<>/doc/chess'
make[3]: Entering directory '/<>/doc'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
Making check in src
make[2]: Entering directory '/<>/src'
Making check in .
make[3]: Entering directory '/<>/src'
make  icheck pcheck
make[4]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I/usr/include/slang  -Wdate-time -D_FORTIFY_SOURCE=2 
-funsigned-char -std=c99 -D_XOPEN_SOURCE=700 -Wall -pedantic  -O3 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o icheck.o icheck.c
gcc -DHAVE_CONFIG_H -I. -I/usr/include/slang  -Wdate-time -D_FORTIFY_SOURCE=2 
-funsigned-char -std=c99 -D_XOPEN_SOURCE=700 -Wall -pedantic  -O3 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DTEST_PARSER ./hparse.c ./rfc822.c ./rfc2822.c util.o 
fram.o jenkins2.o -o pcheck -Wl,-z,relro -Wl,-z,now
./hparse.c: In function ‘main’:
./hparse.c:1036:12: warning: variable ‘h’ set but not used 
[-Wunused-but-set-variable]
 1036 |   hline_t *h = NULL;
  |^
gcc -funsigned-char -std=c99 -D_XOPEN_SOURCE=700 -Wall -pedantic  -O3 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -o icheck icheck.o fram.o 
catfun.o util.o fh.o probs.o jenkins.o jenkins2.o mtherr.o igam.o gamma.o 
const.o polevl.o isnan.o ndtr.o mb.o wc.o -lm 
/usr/bin/ld: fram.o:./src/fram.c:30: multiple definition of `inputline'; 
icheck.o:./src/icheck.c:44: first defined here
/usr/bin/ld: fram.o:./src/fram.c:29: multiple

Bug#953006: marked as done (Switch to current libreadline)

Your message dated Mon, 19 Oct 2020 21:33:12 +
with message-id 
and subject line Bug#972117: Removed package(s) from unstable
has caused the Debian Bug report #953006,
regarding Switch to current libreadline
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.)


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

The package is not bound by license to build against the old
libreadline5. It can also use the current GPL-3 libreadline.
--- End Message ---
--- Begin Message ---
Version: 1.14.1-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#947805: marked as done (Please port to gupnp/gssdp 1.2)

Your message dated Mon, 19 Oct 2020 21:31:33 +
with message-id 
and subject line Bug#970846: Removed package(s) from unstable
has caused the Debian Bug report #947805,
regarding Please port to gupnp/gssdp 1.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.)


-- 
947805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upnp-router-control
Version: 0.2-1.2
Severity: serious
Tags: sid buster
Forwarded: https://bugs.launchpad.net/upnp-router-control/+bug/1857942

Hello,

We are planning to upload gupnp/gssdp 1.2 to debian unstable.

Unfortunately upnp-router-control FTBFS with this version and needs to
be ported.

Could you please have a look at porting it to the latest version? I've
opened a bug upstream for that as well:
https://bugs.launchpad.net/upnp-router-control/+bug/1857942

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Version: 0.2-1.2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#971957: marked as done (libxs FTBFS with libpgm 5.3)

Your message dated Mon, 19 Oct 2020 21:32:32 +
with message-id 
and subject line Bug#971968: Removed package(s) from unstable
has caused the Debian Bug report #971957,
regarding libxs FTBFS with libpgm 5.3
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.)


-- 
971957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxs
Severity: normal
Tags: ftbfs

Hi,

With the recent libpgm 5.3 release currently in experimental libxs
fails to build. It still checks only for the 5.2 release. Attached
patch fixes this issue as soon I'm going to ask for libpgm transition
for unstable.
Question is, do you want to keep libxs in the archives? Its upstream
has disappeared and popcon is only nine users.

Regards,
Laszlo/GCS
Description: search for libpgm 5.3+
 Simply update configure checking.
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2020-10-10

---

--- libxs-1.2.0.orig/configure.ac
+++ libxs-1.2.0/configure.ac
@@ -408,7 +408,7 @@ AS_IF([test "x$enable_plugins" != "xno"]
 #  PGM extension
 libxs_pgm_ext="no"
 
-pgm_basename="libpgm-5.1.118~dfsg"
+pgm_basename="libpgm-5.3.128~dfsg"
 
 AC_ARG_WITH([pgm], [AS_HELP_STRING([--with-pgm],
 [build libxs with PGM extension [default=no]])],
@@ -473,7 +473,7 @@ AS_IF([test "x$with_pgm_ext" != "xno"],
 # Build with system openpgm
 AS_IF([test "x$with_system_pgm_ext" != "xno"], [
 m4_ifdef([PKG_CHECK_MODULES], [
-PKG_CHECK_MODULES([OpenPGM], [openpgm-5.2 >= 5.2])
+PKG_CHECK_MODULES([OpenPGM], [openpgm-5.3 >= 5.3])
 AC_DEFINE([XS_HAVE_OPENPGM], [1], [Have OpenPGM extension])
 LIBXS_EXTRA_CXXFLAGS="$OpenPGM_CFLAGS $LIBXS_EXTRA_CXXFLAGS"
 ],
--- End Message ---
--- Begin Message ---
Version: 1.2.0-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#972394: got same error in other project

2020-10-19 Thread Markus Koschany

Hi Joachim,

Am 19.10.20 um 23:15 schrieb Joachim Wuttke:
> Hi Markus,
> 
> I confirm that this is a serious issue.
> 
> I got the same error message
> 
>    Could NOT find Python3 (missing: Python3_INCLUDE_DIRS Python3_LIBRARIES
>    Development NumPy Development.Module Development.Embed) (found version
>    "3.9.0")

at first I just thought the package is missing a build-dependency on
python3.


> in a completely different software project after I dist-upgraded my Debian/
> testing system. That upgrade did not affect my cmake, which I compile
> myself (version 3.18.20200714-g2da7786-dirty). However, the upgrade did
> change numerous Python3 packages, among them
> 
>    python3-numpy:amd64 (1:1.19.1-1, 1:1.19.2-2+b1)
> 
> but not python3-dev. So my guess is the problem is a change in
> python3-numpy
> that breaks CMake's
> 
>    find_package(Python3 COMPONENTS Development NumPy)
> 
> command.
> 
> Accordingly, I will report the bug to python3-numpy.

Ok, that sounds reasonable. I just stumbled upon this issue while
rebuilding your package, feel free to reassign or address it as you see fit.

Regards,

Markus






signature.asc
Description: OpenPGP digital signature

Bug#942148: marked as done (ndiswrapper-dkms: ndiswrapper 1.60 module fails to compile for kernel 5.3)

Your message dated Mon, 19 Oct 2020 21:27:47 +
with message-id 
and subject line Bug#965949: Removed package(s) from unstable
has caused the Debian Bug report #942148,
regarding ndiswrapper-dkms: ndiswrapper 1.60 module fails to compile for kernel 
5.3
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.)


-- 
942148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndiswrapper-dkms
Version: 1.60-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

   kernel upgrade to linux-image-5.3.2


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

   Effective was building the module for linux-image-4.20.17, ineffective was 
building for linux-image-5.3.2 and linux-image-5.3.5.


   * What was the outcome of this action?

   4.20.17: module ndiswrapper works flawlessly.
   5.3.*: make: *** [Makefile:1639: 
_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2

   Reason: In file linux/sched.h, the member "cpus_allowed" of struct 
task_struct has been renamed to "cpus_mask" in kernel 5.3.


   * What outcome did you expect instead?

   successfuil build
   
Kind regards
 LB


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

Kernel: Linux 4.20.17-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ndiswrapper-dkms depends on:
ii  dkms  2.7.1-4

ndiswrapper-dkms recommends no packages.

ndiswrapper-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.60-8+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

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

Your message dated Mon, 19 Oct 2020 21:26:05 +
with message-id 
and subject line Bug#963669: Removed package(s) from unstable
has caused the Debian Bug report #937960,
regarding python-numpy: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-numpy

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#972394: got same error in other project

2020-10-19 Thread Joachim Wuttke


Hi Markus,

I confirm that this is a serious issue.

I got the same error message

   Could NOT find Python3 (missing: Python3_INCLUDE_DIRS Python3_LIBRARIES
   Development NumPy Development.Module Development.Embed) (found version
   "3.9.0")

in a completely different software project after I dist-upgraded my Debian/
testing system. That upgrade did not affect my cmake, which I compile
myself (version 3.18.20200714-g2da7786-dirty). However, the upgrade did
change numerous Python3 packages, among them

   python3-numpy:amd64 (1:1.19.1-1, 1:1.19.2-2+b1)

but not python3-dev. So my guess is the problem is a change in python3-numpy
that breaks CMake's

   find_package(Python3 COMPONENTS Development NumPy)

command.

Accordingly, I will report the bug to python3-numpy.

Regards, Joachim



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#967095: marked as done (rome: FTBFS: [ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:3.5.1:bundle (bundle) on project rome: Execution bundle of goal org.apache.felix:maven-bund

Your message dated Mon, 19 Oct 2020 22:07:55 +0100
with message-id <20201019210755.3ku2tpnqwhnvktzc@debian>
and subject line Re: rome: FTBFS: [ERROR] Failed to execute goal 
org.apache.felix:maven-bundle-plugin:3.5.1:bundle (bundle) on project rome: 
Execution bundle of goal org.apache.felix:maven-bundle-plugin:3.5.1:bundle 
failed: Plugin org.apache.felix:maven-bundle-plugin:3.5.1 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.osgi:org.osgi.core:jar:debian has not been downloaded from it before. -> 
[Help 1]
has caused the Debian Bug report #967095,
regarding rome: FTBFS: [ERROR] Failed to execute goal 
org.apache.felix:maven-bundle-plugin:3.5.1:bundle (bundle) on project rome: 
Execution bundle of goal org.apache.felix:maven-bundle-plugin:3.5.1:bundle 
failed: Plugin org.apache.felix:maven-bundle-plugin:3.5.1 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.osgi:org.osgi.core:jar:debian has not been downloaded from it before. -> 
[Help 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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibrome-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] rome-parent
> [pom]
> [INFO] rome-utils 
> [jar]
> [INFO] rome   
> [jar]
> [INFO] 
> [INFO] -< com.rometools:rome-parent 
> >--
> [INFO] Building rome-parent 1.12.2
> [1/3]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --< com.rometools:rome-utils 
> >--
> [INFO] Building rome-utils 1.12.2 
> [2/3]
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> rome-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ rome-utils 
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 8 source files to /<>/rome-utils/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ rome-utils ---
> [INFO] Not copying test resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
> rome-utils ---
> [INFO] Not compiling

Bug#969648: marked as done (dask: autopkgtest fail with pandas 1.1 - datetime issues)

Your message dated Mon, 19 Oct 2020 21:03:45 +
with message-id 
and subject line Bug#969648: fixed in dask 2.11.0+dfsg-2
has caused the Debian Bug report #969648,
regarding dask: autopkgtest fail with pandas 1.1 - datetime issues
to be marked as done.

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

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


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

Package: python3-dask
Version: 2.11.0+dfsg-1
Tags: fixed-upstream

With pandas 1.1.x from experimental, dask fails 8 of its tests, at least 
mostly datetime-related.


Log: 
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dask/6900447/log.gz


Upstream fix (untested): https://github.com/dask/dask/pull/6429
Note that this also includes some "xfail on numpy 1.20" parts, which we 
probably don't want.
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2.11.0+dfsg-2
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated dask package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2020 13:39:49 -0700
Source: dask
Architecture: source
Version: 2.11.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 969648 972516
Changes:
 dask (2.11.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Stefano Rivera ]
   * Round-trip patches through gbp-pq.
   * Patch: Compatibility with pandas 1.1, Thanks Rebecca Palmer.
 (Closes: #969648)
   * wrap-and-sort control files.
   * Patches for compatibility with current fsspec. (Closes: #972516)
 - Depend on python3-aiohttp for autopkgtests.
Checksums-Sha1:
 3b0d97bba8ab263cecd2116222c0310491ddc499 2279 dask_2.11.0+dfsg-2.dsc
 25aae11bd9d52bbcdf99574071e5173b23283e43 12540 dask_2.11.0+dfsg-2.debian.tar.xz
 160915010b557db34c9c25288ac8eab7649e367e 7209 
dask_2.11.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 a0b51e7ba2d36c5a58edd73e7333ef596eaad2787189aa71346d3e9dbb0fa5cb 2279 
dask_2.11.0+dfsg-2.dsc
 8ac1158d3c47dd024e8fdbc644a2de14008f6c55ba4cf1515e427c3411f9d2b8 12540 
dask_2.11.0+dfsg-2.debian.tar.xz
 3e1bf92a07ed480410617ac3300b118e28376df593a6451ea162fde10c864d28 7209 
dask_2.11.0+dfsg-2_source.buildinfo
Files:
 81f40392ca5c411948c250850fb36652 2279 python optional dask_2.11.0+dfsg-2.dsc
 3c329a1f6348638d059a30ff57feac09 12540 python optional 
dask_2.11.0+dfsg-2.debian.tar.xz
 4084b3fe2cbe9f748c299ea88dfc6c43 7209 python optional 
dask_2.11.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCX435xAAKCRBHew2wJjpU
2PYQAPoDruWTg1mARMCn2/3w8kimnbhJkE1/LSN53zcLmue2bgD/afHDOmGveQ4n
PVtmKwO4zs+l1tfsI+MaJHYBBpMVHgM=
=tPhz
-END PGP SIGNATURE End Message ---

Bug#952058: marked as done (jfractionlab: FTBFS: src/jfractionlab/officeMachine/OfficeMachine.java:12: error: package com.sun.star.awt does not exist)

Your message dated Mon, 19 Oct 2020 21:53:25 +0100
with message-id <20201019205325.uxypiyvgocqn76oa@debian>
and subject line Re: jfractionlab: FTBFS: 
src/jfractionlab/officeMachine/OfficeMachine.java:12: error: package 
com.sun.star.awt does not exist
has caused the Debian Bug report #952058,
regarding jfractionlab: FTBFS: 
src/jfractionlab/officeMachine/OfficeMachine.java:12: error: package 
com.sun.star.awt does not exist
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.)


-- 
952058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jfractionlab
Version: 0.92-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dpkg-query: package 'openoffice-java-common' is not installed
> Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
> dpkg-query: package 'openoffice-java-common' is not installed
> Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
> mkdir -p target/classes
> # compile java sources
> find src/jfractionlab -name *.java -and -type f -print0 | xargs -0 
> /usr/bin/javac -client -source 7 -target 7 -encoding ISO-8859-1 -d 
> target/classes -cp 
> src:/usr/share/java/tablelayout.jar:/usr/share/java/java_uno.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/ridl.jar:/usr/share/java/unoloader.jar:
> warning: [options] bootstrap class path not set in conjunction with -source 7
> src/jfractionlab/officeMachine/OfficeMachine.java:12: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.MessageBoxButtons;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:13: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.MessageBoxType;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:14: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.Rectangle;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:15: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.XMessageBox;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:16: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.XMessageBoxFactory;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:17: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.XWindow;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:18: error: package 
> com.sun.star.awt does not exist
> import com.sun.star.awt.XWindowPeer;
>^
> src/jfractionlab/officeMachine/OfficeMachine.java:27: error: package 
> com.sun.star.document does not exist
> import com.sun.star.document.XEmbeddedObjectSupplier2;
> ^
> src/jfractionlab/officeMachine/OfficeMachine.java:28: error: package 
> com.sun.star.frame does not exist
> import com.sun.star.frame.XComponentLoader;
>  ^
> src/jfractionlab/officeMachine/OfficeMachine.java:29: error: package 
> com.sun.star.frame does not exist
> import com.sun.star.frame.XDesktop;
>  ^
> src/jfractionlab/officeMachine/OfficeMachine.java:36: error: package 
> com.sun.star.table does not exist
> import com.sun.star.table.XCell;
>  ^
> src/jfractionlab/officeMachine/OfficeMachine.java:37: error: package 
> com.sun.star.table does not exist
> import com.sun.star.table.XCellRange;
>  ^
> src/jfractionlab/officeMachine/OfficeMachine.java:38: error: package 
> com.sun.star.text does not exist
> import com.sun.star.text.XText;
> ^
> src/jfractionlab/officeMachine/OfficeMachine.java:39: error: package 
> com.sun.star.text does not exist
> import com.sun.star.text.XTextContent;
> ^
> src/jfractionlab/officeMachine/OfficeMachine.java:40: error: package 
> com.sun.star.text does not exist
> import com.sun.star.text.XTextDocument;
> ^
> src/jfractionlab/officeMachine/OfficeMachine.java:41: error: package 
> com.sun.star.text does not exist
> import com.sun.star.text.XTextRange;
> ^
> src/jfractionlab/officeMachine/OfficeMachine.java:42: error: package 
> com.sun.star.text does not exist
> import

Processed: closing 959136

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

> close 959136
Bug #959136 [src:dask] numpy breaks dask autopkgtest: E assert 10 == 11
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#951854: fixed in muchsync 5-2

On Mon, 24 Feb 2020 22:09:01 + Debian FTP Masters
 wrote:

>  muchsync (5-2) unstable; urgency=medium
>  .
>* Links with wolfssl instead of libcrypto, fix:
>  "OpenSSL linking without license exception", thanks to Bastian Germann
>  (Closes: #951854).

This patch is not needed anymore, given that OpenSSL is now considered a
system library, i.e. doesn't require a license exception in muchsync.

See
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

It's obviously your choice, if you want to continue to ship this patch
and use libwolfssl.

Regards,
Michael

signature.asc
Description: OpenPGP digital signature

Bug#951854: fixed in muchsync 5-2

Am 19.10.20 um 22:40 schrieb Michael Biebl:
> See
> http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

See also https://salsa.debian.org/ftp-team/website/-/merge_requests/6



signature.asc
Description: OpenPGP digital signature

Bug#952868: OpenSSL linking without license exception

Am 19.10.20 um 22:42 schrieb Michael Biebl:
> On Sun, 1 Mar 2020 13:14:49 +0100 Bastian Germann
>  wrote:
>> Package: wesnoth
>> Severity: serious
>>
>> This GPL2 package links with OpenSSL. The OpenSSL license is
>> incompatible with the GPL (see
>> https://ftp-master.debian.org/REJECT-FAQ.html). This can be solved by
>> asking upstream to add a license exception or by linking with wolfSSL
>> instead. You can find a patch enclosed (untested).
> 
> This patch is not strictly needed anymore, given that OpenSSL is now
> considered a system library, i.e. doesn't require a license exception in
> wesnoth.
> 
> See
> http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html
> 

See also https://salsa.debian.org/ftp-team/website/-/merge_requests/6



signature.asc
Description: OpenPGP digital signature

Bug#952868: OpenSSL linking without license exception

On Sun, 1 Mar 2020 13:14:49 +0100 Bastian Germann
 wrote:
> Package: wesnoth
> Severity: serious
> 
> This GPL2 package links with OpenSSL. The OpenSSL license is
> incompatible with the GPL (see
> https://ftp-master.debian.org/REJECT-FAQ.html). This can be solved by
> asking upstream to add a license exception or by linking with wolfSSL
> instead. You can find a patch enclosed (untested).

This patch is not strictly needed anymore, given that OpenSSL is now
considered a system library, i.e. doesn't require a license exception in
wesnoth.

See
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

It's obviously your choice, if you want to continue to ship this patch
and use libwolfssl (although I think OpenSSL is much more battle tested).

Regards,
Michael

signature.asc
Description: OpenPGP digital signature

Bug#972519: black: autopkgtest regression

2020-10-19 Thread Sebastian Ramacher

Source: black
Version: 20.8b1-2
Severity: serious

black currently fails its autopkgtests on amd64 and is thus unable to
migrate to testing:
| test_async_main (tests.test_primer.PrimerCLITests) ... Can not find 'black' 
executable in PATH. No point in running
| FAIL
| test_handle_debug (tests.test_primer.PrimerCLITests) ... ok
| test_help_output (tests.test_primer.PrimerCLITests) ... ok
|
| ==
| FAIL: test_async_main (tests.test_primer.PrimerCLITests)
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.8/contextlib.py", line 75, in inner
| return func(*args, **kwds)
|   File "./tests/test_primer.py", line 204, in test_async_main
| self.assertEqual(0, return_val)
| AssertionError: 0 != -1
|
| --
| Ran 141 tests in 35.425s
|
| FAILED (failures=1, skipped=13, expected failures=3)
| Test failed: 
| error: Test failed: 

See https://ci.debian.net/data/autopkgtest/testing/amd64/b/black/7489655/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#951730: marked as done (OpenSSL linking without license exception)

Your message dated Mon, 19 Oct 2020 21:29:08 +0200
with message-id <61e76839-c802-55d3-a40f-1da7919b3...@fishpost.de>
and subject line OpenSSL is considered a system library
has caused the Debian Bug report #951730,
regarding OpenSSL linking without license exception
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.)


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

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. I can build
fine without libssl, so please remove this dependency.
--- End Message ---
--- Begin Message ---
OpenSSL is considered a system library (GPL: "major component of the
operating system") in Debian as of
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

With that, the exception for system libraries can be invoked and a
GPL-licensed program may link with OpenSSL without an additional exception.--- End Message ---

Bug#951780: marked as done (OpenSSL linking without license exception)

Your message dated Mon, 19 Oct 2020 21:29:08 +0200
with message-id <61e76839-c802-55d3-a40f-1da7919b3...@fishpost.de>
and subject line OpenSSL is considered a system library
has caused the Debian Bug report #951780,
regarding OpenSSL linking without license exception
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.)

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

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. Please
replace libssl with a GPL compatible library. I successfully compiled
with libwolfssl which has an OpenSSL API compatibility layer.
--- End Message ---
--- Begin Message ---
OpenSSL is considered a system library (GPL: "major component of the
operating system") in Debian as of
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

With that, the exception for system libraries can be invoked and a
GPL-licensed program may link with OpenSSL without an additional exception.--- End Message ---

Bug#969362: python-flask-cors: CVE-2020-25032

2020-10-19 Thread Salvatore Bonaccorso

Hi Bastian,

On Wed, Oct 14, 2020 at 05:39:00PM +0200, Salvatore Bonaccorso wrote:
> Hi Bastian,
> 
> On Tue, Oct 13, 2020 at 11:36:40PM +0200, Bastian Germann wrote:
> > Hi Salvatore,
> > 
> > Thanks for your hints.
> > 
> > Am 10.10.20 um 23:02 schrieb Salvatore Bonaccorso:
> > > Hi Bastian,
> > > 
> > > [Please do send such requests always to team@s.d.o, dev-ref gives as
> > > well some further hints at
> > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#handling-security-related-bugs]
> > > 
> > > On Thu, Oct 08, 2020 at 04:25:55PM +0200, Bastian Germann wrote:
> > >> On Tue, 01 Sep 2020 10:51:48 +0200 Salvatore Bonaccorso
> > >>  wrote:
> > >>> The following vulnerability was published for python-flask-cors.
> > >>>
> > >>> CVE-2020-25032[0]:
> > >>> | An issue was discovered in Flask-CORS (aka CORS Middleware for Flask)
> > >>> | before 3.0.9. It allows ../ directory traversal to access private
> > >>> | resources because resource matching does not ensure that pathnames are
> > >>> | in a canonical format.
> > >>>
> > >>>
> > >>> 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-25032
> > >>> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25032
> > >>> [1] 
> > >>> https://github.com/corydolphin/flask-cors/commit/67c4b2cc98ae87cf1fa7df4f97fd81b40c79b895
> > >>
> > >> I have prepared a buster-security release at
> > >>
> > >> https://salsa.debian.org/python-team/packages/python-flask-cors/-/tags/debian%2F3.0.7-2
> > > 
> > > As for the update, please do send always as a debdiff from a built
> > > (and tested) package (this request is similarly to what stable release
> > > managers would expect for point release updates, it helps us as well
> > > to archive discussion and debdiffs to review).
> > 
> > The debdiff is enclosed. Also available at:
> > https://salsa.debian.org/python-team/packages/python-flask-cors/-/tags/debian%2F3.0.7-1+deb10u1
> > > 
> > > But I can give already a first feedback: debian/changelog uses 3.0.7-2
> > > as version. Even though 3.0.7-2 might never have been seen in the
> > > archive, please do use 3.0.7-1+deb10u1 instead following the usual
> > > convention. While at it use urgency=high (for consistency in security
> > > updates).
> > > 
> > > For the bug closer I think you will need to use "Closes: #969362)".
> > 
> > I applied all suggestions.
> > 
> > > Furthermore: what kind of testing did the update recieve, were you
> > > able to test the update in production environments, are there any
> > > problems spotted? I'm asking in particular as the modfied tests seem
> > > to pass ok as well without the patch (but I only quickly gave it a
> > > test from the git repository, might be something else strange here).
> > 
> > I ran the built package on buster but did not try to confirm that the
> > security issue is closed as claimed by upstream. No problems spotted.
> 
> Ack thanks for confirming. I have uploadd the package to
> security-master and we will release DSA soon when time permits.

DSA 4775-1 has been released now for it.

> I think it's okay to not have patched as well the example (wher the
> call was fixed accordingly including /api/ in the target URL, anybody
> searching for examples will probably look online anyway).
> 
> > >> The new upstream release is waiting in the master branch to be published
> > >> in sid.
> > > 
> > > Ok, although not required, if you have that already ok to be uploaded
> > > I would say to go ahead with the unstable upload and have the fixes
> > > exposed there already.
> > 
> > I cannot upload because I am not a DD. It would be nice if someone could
> > sponsor the new version. It also closes a FTBFS, which got me interested
> > in the package in the first place.
> 
> Can you ask anybody in the team to do that?

This still would be needed.

Regards,
Salvatore

Bug#951877: marked as done (OpenSSL linking without license exception)

Your message dated Mon, 19 Oct 2020 21:26:29 +0200
with message-id
and subject line OpenSSL is considered a system library
has caused the Debian Bug report #951877,
regarding OpenSSL linking without license exception
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.

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

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. I can build
fine without libssl, so please remove this dependency. If you want to
keep it maybe you want to try building with wolfssl which has an OpenSSL
compatibility library.
--- End Message ---
--- Begin Message ---
OpenSSL is considered a system library (GPL: "major component of the
operating system") in Debian as of
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

With that, the exception for system libraries can be invoked and a
GPL-licensed program may link with OpenSSL without an additional exception.--- End Message ---

Bug#969648: dask, pandas 1.1

Hi Rebecca (2020.10.19_12:07:08_-0700)
> > Or maybe not an actual regression...it's a ~5e-7 difference and one of the
> > things the patch does (at around dask/dataframe/tests/test_rolling.py:270)
> > is _tighten_ the tolerance on that test.
> 
> Hrm, I didn't see that failure. Testing again on a 32bit arch to be
> sure...

Aha. Reproduced.

And found https://github.com/dask/dask/pull/6502

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#969648: dask, pandas 1.1

Hi Rebecca (2020.10.19_11:51:33_-0700)

> Or maybe not an actual regression...it's a ~5e-7 difference and one of the
> things the patch does (at around dask/dataframe/tests/test_rolling.py:270)
> is _tighten_ the tolerance on that test.

Hrm, I didn't see that failure. Testing again on a 32bit arch to be
sure...

> That looks like my earlier version, which fails with NameError.

Yeah, I applied it as-is first, and then followed up with the fixes,
after seeing the test failures.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#969648: dask, pandas 1.1

Hi Rebecca (2020.10.19_11:26:19_-0700)

> I have now tested it.  (The dask tests are run in autopkgtest, not build.)

Thanks. I took your untested patch and tested it, too.

It needed some tweaking, which it looks like you've also done.

> The attached is what I have so far, but it had these failures.  The first
> two happen with or without 969648.patch and (from debci results) appear to
> be triggered by the new fsspec, but the last is a *regression* caused by
> this patch.

I cherry picked these to fix these failures:
https://github.com/dask/dask/pull/6331
https://github.com/dask/dask/pull/6446

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#952399: marked as done (OpenSSL linking without license exception)

Your message dated Mon, 19 Oct 2020 21:04:36 +0200
with message-id <650272e2-fd4f-d1b1-1e02-6d3f2cba3...@fishpost.de>
and subject line kmod: OpenSSL is considered a system library
has caused the Debian Bug report #952399,
regarding OpenSSL linking without license exception
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.)


-- 
952399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmod
Version: 26-1
Severity: serious

All of the GPL-2+ licensed executables contained in the kmod binary
package link to libcrypto even though they do not have any OpenSSL
license exception. ftp-master considers this a serious issue. So please
remove this optional dependency or ask upstream for a license exception.
--- End Message ---
--- Begin Message ---
OpenSSL is considered a system library (GPL: "major component of the
operating system") in Debian as of
http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html

With that, the exception for system libraries can be invoked and a
GPL-licensed program may link with OpenSSL without an additional exception.--- End Message ---

Bug#969648: marked as pending in dask

Control: tag -1 pending

Hello,

Bug #969648 in dask 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/packages/dask/-/commit/f37e48dc02aad3d34f9ea9acb7ca8d65fd107aab


Patch: Compatibility with pandas 1.1, Thanks Rebecca Palmer. (Closes: #969648)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969648

Processed: Bug#969648 marked as pending in dask

Processing control commands:

> tag -1 pending
Bug #969648 [python3-dask] dask: autopkgtest fail with pandas 1.1 - datetime 
issues
Added tag(s) pending.

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

Bug#972515: src:csvkit: fails to migrate to testing for too long: autopkgtest failure

2020-10-19 Thread Paul Gevers

Source: csvkit
Version: 1.0.2-2
Severity: serious
Control: close -1 1.0.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 969550
Control: affects -1 src:python-agate-sql src:python-agate

Dear maintainer(s),

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

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

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

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

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=csvkit




signature.asc
Description: OpenPGP digital signature

Processed: src:csvkit: fails to migrate to testing for too long: autopkgtest failure

Processing control commands:

> close -1 1.0.5-1
Bug #972515 [src:csvkit] src:csvkit: fails to migrate to testing for too long: 
autopkgtest failure
Marked as fixed in versions csvkit/1.0.5-1.
Bug #972515 [src:csvkit] src:csvkit: fails to migrate to testing for too long: 
autopkgtest failure
Marked Bug as done
> block -1 by 969550
Bug #972515 {Done: Paul Gevers } [src:csvkit] src:csvkit: 
fails to migrate to testing for too long: autopkgtest failure
972515 was not blocked by any bugs.
972515 was not blocking any bugs.
Added blocking bug(s) of 972515: 969550
> affects -1 src:python-agate-sql src:python-agate
Bug #972515 {Done: Paul Gevers } [src:csvkit] src:csvkit: 
fails to migrate to testing for too long: autopkgtest failure
Added indication that 972515 affects src:python-agate-sql and src:python-agate

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

Processed: [bts-link] source package src:pyxdg

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

> #
> # bts-link upstream status pull for source package src:pyxdg
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #964609 (http://bugs.debian.org/964609)
> # Bug title: pyxdg: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
> python{version} -p 3.8 returned exit code 13
> #  * https://gitlab.freedesktop.org/xdg/pyxdg/-/issues/20
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 964609 + fixed-upstream
Bug #964609 [src:pyxdg] pyxdg: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p 3.8 returned exit code 13
Bug #968399 [src:pyxdg] pyxdg ftbfs, test failure
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 964609 - status-opened
Usertags were: status-opened.
Usertags are now: .
> usertags 964609 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #968399 (http://bugs.debian.org/968399)
> # Bug title: pyxdg ftbfs, test failure
> #  * https://gitlab.freedesktop.org/xdg/pyxdg/-/issues/20
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 968399 + fixed-upstream
Bug #968399 [src:pyxdg] pyxdg ftbfs, test failure
Bug #964609 [src:pyxdg] pyxdg: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p 3.8 returned exit code 13
Ignoring request to alter tags of bug #968399 to the same tags previously set
Ignoring request to alter tags of bug #964609 to the same tags previously set
> usertags 968399 - status-opened
Usertags were: status-opened.
Usertags are now: .
> usertags 968399 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package malcontent

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

> #
> # bts-link upstream status pull for source package malcontent
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #972145 (http://bugs.debian.org/972145)
> # Bug title: mct_manager_get_app_filter() fails closed if accountsservice not 
> installed
> #  * https://gitlab.freedesktop.org/pwithnall/malcontent/-/issues/27
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 972145 + fixed-upstream
Bug #972145 [libmalcontent-0-0] mct_manager_get_app_filter() fails closed if 
accountsservice not installed
Added tag(s) fixed-upstream.
> usertags 972145 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:git-remote-hg

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

> #
> # bts-link upstream status pull for source package src:git-remote-hg
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #971061 (http://bugs.debian.org/971061)
> # Bug title: git-remote-hg: Mercurial no longer supports Python 2
> #  * https://github.com/mnauw/git-remote-hg/issues/34
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 971061 + fixed-upstream
Bug #971061 [src:git-remote-hg] git-remote-hg: Mercurial no longer supports 
Python 2
Added tag(s) fixed-upstream.
> usertags 971061 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: gadmin-rsync: diff for NMU version 0.1.7-1.1

Processing control commands:

> tags 957250 + patch
Bug #957250 [src:gadmin-rsync] gadmin-rsync: ftbfs with GCC-10
Added tag(s) patch.
> tags 957250 + pending
Bug #957250 [src:gadmin-rsync] gadmin-rsync: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957250: gadmin-rsync: diff for NMU version 0.1.7-1.1

2020-10-19 Thread Sudip Mukherjee

Control: tags 957250 + patch
Control: tags 957250 + pending
--

Dear maintainer,

I've prepared an NMU for gadmin-rsync (versioned as 0.1.7-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru gadmin-rsync-0.1.7/debian/changelog 
gadmin-rsync-0.1.7/debian/changelog
--- gadmin-rsync-0.1.7/debian/changelog 2011-03-26 09:31:20.0 +
+++ gadmin-rsync-0.1.7/debian/changelog 2020-10-19 18:03:24.0 +0100
@@ -1,3 +1,10 @@
+gadmin-rsync (0.1.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957250)
+
+ -- Sudip Mukherjee   Mon, 19 Oct 2020 18:03:24 
+0100
+
 gadmin-rsync (0.1.7-1) unstable; urgency=low
 
   * New Maintainer. (Closes: #605305)
diff -Nru gadmin-rsync-0.1.7/debian/patches/fix_gcc-10.patch 
gadmin-rsync-0.1.7/debian/patches/fix_gcc-10.patch
--- gadmin-rsync-0.1.7/debian/patches/fix_gcc-10.patch  1970-01-01 
01:00:00.0 +0100
+++ gadmin-rsync-0.1.7/debian/patches/fix_gcc-10.patch  2020-10-19 
18:02:58.0 +0100
@@ -0,0 +1,19 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957250
+Forwarded: no
+
+---
+
+--- gadmin-rsync-0.1.7.orig/src/restore_menu.c
 gadmin-rsync-0.1.7/src/restore_menu.c
+@@ -41,8 +41,6 @@
+ //#include "key_handling.h"
+ 
+ 
+-GtkTreeIter iter_filesel;
+-
+ extern gchar *global_key_path;
+ extern gchar *global_scripts_dir;
+ extern gchar *global_backup_name;
diff -Nru gadmin-rsync-0.1.7/debian/patches/series 
gadmin-rsync-0.1.7/debian/patches/series
--- gadmin-rsync-0.1.7/debian/patches/series2011-03-09 18:35:03.0 
+
+++ gadmin-rsync-0.1.7/debian/patches/series2020-10-19 17:56:03.0 
+0100
@@ -1,3 +1,4 @@
 01-icondir.patch
 02-desktop.patch
 03_spelling_errors.patch
+fix_gcc-10.patch

Bug#937184: Python 3 port of offlineimap underway

2020-10-19 Thread Sudip Mukherjee

On Sat, Oct 17, 2020 at 12:46 AM Brett Gilio  wrote:
>
> Sudip Mukherjee  writes:
> >
> > upstream is asking to treat offlineimap and offlineimap3 as separate
> > package. https://github.com/OfflineIMAP/offlineimap3/issues/10
>
> I think we should preserve offlineimap until offlineimap3 is released,
> and then we can probably rename offlineimap3 once offlineimap is
> considered unsupported by the maintainers.

It has been removed today :(


-- 
Regards
Sudip

Bug#972500: marked as done (hamster-time-tracker does not launch on Buster using the backported package)

Your message dated Mon, 19 Oct 2020 18:29:14 +0200
with message-id 
and subject line 
has caused the Debian Bug report #972500,
regarding hamster-time-tracker does not launch on Buster using the backported 
package
to be marked as done.

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

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


-- 
972500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hamster-time-tracker
Version: 3.0.2-3~bpo10+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

I'm trying to start hamster-time-tracker. I have used the program for
many years (as hamster-applet) and upgraded to the transitional package.

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

Trying to start the program is ineffective.
Trying to reinstall the program did not solve the issue.

   * What was the outcome of this action?
$ hamster
Traceback (most recent call last):
  File "/usr/bin/hamster", line 149, in on_activate_window
self._open_window(action.get_name(), data)
  File "/usr/bin/hamster", line 184, in _open_window
self.overview_controller = Overview()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
__init__
self.find_facts()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
find_facts
self.facts = self.storage.get_facts(start, end, search_terms=search)
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
get_facts
for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
server_version = self._connection.Version()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
_message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name,
interface_name)
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
_method_lookup
raise UnknownMethodException('%s is not a valid method of interface
%s' %
(method_name, dbus_interface))
UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
method: Version is not a valid method of interface org.gnome.Hamster

Traceback (most recent call last):
  File "/usr/bin/hamster", line 149, in on_activate_window
self._open_window(action.get_name(), data)
  File "/usr/bin/hamster", line 184, in _open_window
self.overview_controller = Overview()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
__init__
self.find_facts()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
find_facts
self.facts = self.storage.get_facts(start, end, search_terms=search)
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
get_facts
for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
server_version = self._connection.Version()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
_message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name,
interface_name)
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
_method_lookup
raise UnknownMethodException('%s is not a valid method of interface
%s' %
(method_name, dbus_interface))
UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
method: Version is not a valid method of interface org.gnome.Hamster

   * What outcome did you expect instead?

Package should work. Reinstalling should install, or propose missing

Bug#972500: hamster-time-tracker does not launch on Buster using the backported package

2020-10-19 Thread Ulrike Uhlig

Hi!

thank you for the quick reply.

On 19.10.20 17:39, Raphael Hertzog wrote:

> Ulrike, did you restart your computer after the upgrade just to make sure
> that the dbus service was properly using the new code ?

I totally never reboot after installing packages, except for kernel
updates :) But but but! Rebooting actually worked! So no need to further
investigate that.

Thanks! <3
Ulrike

Bug#972500: hamster-time-tracker does not launch on Buster using the backported package

2020-10-19 Thread Raphael Hertzog

Hi,

Philipp, you uploaded the backport. Can you have a look at this report?

Ulrike, did you restart your computer after the upgrade just to make sure
that the dbus service was properly using the new code ?

Thank you in advance.

On Mon, 19 Oct 2020, Ulrike Uhlig wrote:
> Package: hamster-time-tracker
> Version: 3.0.2-3~bpo10+1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
>* What led up to the situation?
> 
> I'm trying to start hamster-time-tracker. I have used the program for
> many years (as hamster-applet) and upgraded to the transitional package.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Trying to start the program is ineffective.
> Trying to reinstall the program did not solve the issue.
> 
>* What was the outcome of this action?
> $ hamster
> Traceback (most recent call last):
>   File "/usr/bin/hamster", line 149, in on_activate_window
> self._open_window(action.get_name(), data)
>   File "/usr/bin/hamster", line 184, in _open_window
> self.overview_controller = Overview()
>   File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
> __init__
> self.find_facts()
>   File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
> find_facts
> self.facts = self.storage.get_facts(start, end, search_terms=search)
>   File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
> get_facts
> for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
>   File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
> server_version = self._connection.Version()
>   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
> __call__
> return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
> __call__
> **keywords)
>   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
> _message_cb
> (candidate_method, parent_method) = _method_lookup(self, method_name,
> interface_name)
>   File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
> _method_lookup
> raise UnknownMethodException('%s is not a valid method of interface
> %s' %
> (method_name, dbus_interface))
> UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
> method: Version is not a valid method of interface org.gnome.Hamster
> 
> Traceback (most recent call last):
>   File "/usr/bin/hamster", line 149, in on_activate_window
> self._open_window(action.get_name(), data)
>   File "/usr/bin/hamster", line 184, in _open_window
> self.overview_controller = Overview()
>   File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
> __init__
> self.find_facts()
>   File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
> find_facts
> self.facts = self.storage.get_facts(start, end, search_terms=search)
>   File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
> get_facts
> for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
>   File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
> server_version = self._connection.Version()
>   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
> __call__
> return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
> __call__
> **keywords)
>   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
> _message_cb
> (candidate_method, parent_method) = _method_lookup(self, method_name,
> interface_name)
>   File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
> _method_lookup
> raise UnknownMethodException('%s is not a valid method of interface
> %s' %
> (method_name, dbus_interface))
> UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
> method: Version is not a valid method of interface org.gnome.Hamster
> 
>* What outcome did you expect instead?
> 
> Package should work. Reinstalling should install, or propose missing
> libraries,
> or software if any.
> 
> *** End of the template - remove these template lines ***
> 
> 
> 
> -- System Information:
> Debian Release: 10.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores)

Bug#972500: hamster-time-tracker does not launch on Buster using the backported package

2020-10-19 Thread Philipp Huebner

Hi,

Am 19.10.20 um 17:39 schrieb Raphael Hertzog:
> Philipp, you uploaded the backport. Can you have a look at this report?

sure, I will do that tomorrow.

Since hamster was not part of buster I did not test an old hamster
profile with the new hamster-time-tracker.

@Ulrike: could you please give it a try with your existing config+data
temporarily renamed?

Best wishes
Philipp

Bug#950677: marked as done (pglogical-ticker FTBFS with PostgreSQL 12)

Your message dated Mon, 19 Oct 2020 15:04:12 +
with message-id 
and subject line Bug#950677: fixed in pglogical-ticker 1.4.1-3
has caused the Debian Bug report #950677,
regarding pglogical-ticker FTBFS with PostgreSQL 12
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.)


-- 
950677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pglogical-ticker
Version: 211
Severity: serious
Tags: ftbfs

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

...
 fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control  2019-09-12 03:21:00.0 -1200
+++ debian/control.2ofOpA   2020-01-30 11:15:37.578761355 -1200
@@ -7,9 +7,8 @@
 Homepage: https://github.com/enova/pglogical_ticker
 Vcs-Git: https://github.com/enova/pglogical_ticker.git
 
-Package: postgresql-11-pglogical-ticker
+Package: postgresql-12-pglogical-ticker
 Architecture: any
-Depends: postgresql-11, postgresql-11-pglogical, ${shlibs:Depends}, 
${misc:Depends}
+Depends: postgresql-12, postgresql-12-pglogical, ${shlibs:Depends}, 
${misc:Depends}
 Description: Have time-based replication delay for pglogical
- A pglogical extension to get time-based replication delay for PostgreSQL 11.
-
+ A pglogical extension to get time-based replication delay for PostgreSQL 12.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
debian/control] Error 1
--- End Message ---
--- Begin Message ---
Source: pglogical-ticker
Source-Version: 1.4.1-3
Done: Christoph Berg 

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pglogical-ticker 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: Mon, 19 Oct 2020 16:31:42 +0200
Source: pglogical-ticker
Architecture: source
Version: 1.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Jeremy Finzel 
Changed-By: Christoph Berg 
Closes: 950677
Changes:
 pglogical-ticker (1.4.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Use dh --with pgxs.
   * R³: no.
   * DH 13.
   * debian/tests: Use 'make' instead of postgresql-server-dev-all.
 .
 pglogical-ticker (1.4.1-2) unstable; urgency=medium
 .
   * Team upload for PostgreSQL 13. (Closes: #950677)
Checksums-Sha1:
 c98853a1061716164fc0a245413a7c6cac1857e0 1980 pglogical-ticker_1.4.1-3.dsc
 26f4e02fb57894b8937b70cb45defacb0f6d6a16 2816 
pglogical-ticker_1.4.1-3.debian.tar.xz
Checksums-Sha256:
 2ce214f072ce2686648b63ed3cbd451cbfd8d45625e54e8baa27974e5ac62f08 1980 
pglogical-ticker_1.4.1-3.dsc
 62bbcbf44d13af78b6f6a087dde082c9e89053670a90dd2e725d8096eafde207 2816 
pglogical-ticker_1.4.1-3.debian.tar.xz
Files:
 6e2aa45cbf4398917afc71d160488594 1980 database optional 
pglogical-ticker_1.4.1-3.dsc
 bed6e2cdd0f836e9f0fc02da701cbeeb 2816 database optional 
pglogical-ticker_1.4.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl+Npl8ACgkQTFprqxLS
p64Q6xAAnE6azQB/6uTyyEVyW/thOcKCbb+Xnq38a7SQekGCxzcIazkXiP1aL5Mm
HvVyRBQN3D+eBfhHn+sozxi6FcvogWdfEZQX+1dhLF/o8D5iWFB3WJQfpZGKT26h
zXLM+WdSsykF79GGSJRinXv/x9UeCbJEbaCrZlc7t3a6VCU0UjJRPft+022qr0qF
70zp/dw8kYBifnvyNFIJwpEUSmr229j1yl32tz+b7GMqjDtxl6brvtJN5Se5xuR9
gMahaDHjUH5ENfEFMUleZUiIMzRRb3wLC3xV1hbZgLygI/kadoLVVYzmSZ5qntlp
jiaTIkom1fm4KyB0q0myqU0bSI9ihnBOHfCydozK0wJPRdbCBb28GwxEZbVrULX0
zZhJI+asLulcEN3xhE6N5KCK+gvWMLZ+pEJ0tBzcwkfDTJ5ZcZ8jcgUGENewDcVQ
yGostlVuVxOLDD3BU/k1Z7QIvk6yMpuZTtgyWvy76jivtILj7PGTOhEXv5pvXlan
G1O134/g6u7Gm6VzFiHpvofwy4gMSg0A6Klc+PQKb53IL+uzChrf4aplRAkOljyL
rIs6SWEqMeyxDSis6ZHGX9WrNABQifdT0uLMBW6DmjFmFqUnRwsuxqxhZh4OkIOA
6sFse1YuYbZFgtakq8J39K2lr+kv7sas+UHuYQMpWFIXV0qmVjk=
=HKJD
-END PGP SIGNATURE End Message ---

Bug#972465: marked as done (unpack error when installing together)

Your message dated Mon, 19 Oct 2020 14:42:26 +
with message-id 
and subject line Bug#972465: fixed in onednn 2.0~beta8+ds-3
has caused the Debian Bug report #972465,
regarding unpack error when installing together
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.)


-- 
972465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmkldnn1,libdnnl1
Severity: serious

When trying to install both libmkldnn1 and libdnnl1, dpkg errors out:

| Unpacking libdnnl1:amd64 (2.0~beta8+ds-2) ...
| Selecting previously unselected package libmkldnn1:amd64.
| Preparing to unpack .../libmkldnn1_2.0~beta4-1_amd64.deb ...
| Unpacking libmkldnn1:amd64 (2.0~beta4-1) ...
| dpkg: error processing archive 
/var/cache/apt/archives/libmkldnn1_2.0~beta4-1_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/libdnnl.so.1', which is also 
in package libdnnl1:amd64 2.0~beta8+ds-2
| Errors were encountered while processing:
|  /var/cache/apt/archives/libmkldnn1_2.0~beta4-1_amd64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)

If I understand things correctly, libmkldnn1 is supposed to go away in
favour of libdnnl1. If that is the case, at the very least libdnnl1
should add Breaks and Replaces on libmkldnnl1.

Helmut
--- End Message ---
--- Begin Message ---
Source: onednn
Source-Version: 2.0~beta8+ds-3
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated onednn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2020 22:01:16 +0800
Source: onednn
Architecture: source
Version: 2.0~beta8+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team 
Changed-By: Mo Zhou 
Closes: 972465
Changes:
 onednn (2.0~beta8+ds-3) unstable; urgency=medium
 .
   * Breaks & Replaces libmkldnn1 and libmkldnn-dev. (Closes: #972465)
   * Packaging repo has been transferred from science team to deep learning 
team.
   * Replace the science team with deep learning team in maintainer field.
Checksums-Sha1:
 573113043c8c7efcf96345000c387af8d54d50e3 2286 onednn_2.0~beta8+ds-3.dsc
 75b46eb6d2d9e81fa5a4b594686fad009cb88d53 9632 
onednn_2.0~beta8+ds-3.debian.tar.xz
 6af637e44f094a25b9d4b416226bd858481a320c 8292 
onednn_2.0~beta8+ds-3_source.buildinfo
Checksums-Sha256:
 1fc80fe962a5e2980b4cdb6f6a2c28f916538a196b31fbacf92472d68000363a 2286 
onednn_2.0~beta8+ds-3.dsc
 fcbdd8b200bbdda9656e21b4e98e0e5d0486a17c28e2c47146f4b1163c248596 9632 
onednn_2.0~beta8+ds-3.debian.tar.xz
 f964eed568431de8ce2d1ef69b3b047516d923fe48da6647436e5867992796e8 8292 
onednn_2.0~beta8+ds-3_source.buildinfo
Files:
 f92e09eed038c5d7265e14e60647a990 2286 science optional 
onednn_2.0~beta8+ds-3.dsc
 ea0b773aca6346aaee3c81fea0e544fd 9632 science optional 
onednn_2.0~beta8+ds-3.debian.tar.xz
 266bedb868cb06cfc279f6cf6426b184 8292 science optional 
onednn_2.0~beta8+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl+NnOARHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaooarRAAopCGiKw5eEY9ctQsge0ekSM0H5ViqokX
ki8uz3r07jd9uyUNhfz1WFk2h8rtWf7TpOGRijpqYafrv8rRHYp3QSucdoTX9KeN
1yqjM0/ndvHY5BsTmY3HtifKkroBzn4KdEaSuFryJL4c+UYYd1d2zj0ylr79lgSp
rCIBqbNnwY2i4kysuPyHO0zZRH3RtfM5tTmXr6Ac+ru4Ttkd+pT6LijOkZIPWft7
Gvqh89Y+AIjpk1XZUzJ3MfhN0XEVdbR+NHD3CpnWz+G3XcBALUpUIg+xgHHOOWe7
0EhU9YQol/+T1eSq1j4GPjmrSAyP4ESdWkDfESnjmYmoQaJgy+VPCxslrumVGIg4
OGhGvOpv1a9YB5NOxr58dasFcxRM1QcyFv7CdqfwRrCfeVb+KnriJDxDD4MlfWbX
JQKiH9cSjEZx3tFoV9EdkijxcBDAZ0pus9Z8zCZAI+v16sj5j2N39kAXRjR/GW+h
D+LbHVGm4LOXM1Le9gbFo0bDcRIYBzUttzei76lfCNaH+6KAtgay8VjrgbnRJNJE
aunE/kP051JyDrFTZRJR2bWEUCwDbPfzxfZv18RMkkCLQ4VdbSylIeVuFkSjltEc
nHbCI/yYSgrS7990vtvhYErj5H0I7KONuD/peBjRypdcqool9Yj+tCEBcnMmwDN1
n7Td31WAmtg=
=VULn
-END PGP SIGNATURE End Message ---

Bug#971609: marked as done (r-cran-sna: Not build in Debian, unsatisfiable build-deps)

Your message dated Mon, 19 Oct 2020 16:34:41 +0200
with message-id <8b34d88d-7b8a-fe1d-2e62-74388b572...@debian.org>
and subject line Re: r-cran-sna: Not build in Debian, unsatisfiable build-deps
has caused the Debian Bug report #971609,
regarding r-cran-sna: Not build in Debian, unsatisfiable build-deps
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.)


-- 
971609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sna
Version: 2.5-2
Severity: serious

As documented in update-excuses, the r-cran-sna package is not migratable to
testing because it build-depends on packages that are not available in
Debian (neither in unstable, nor in any other release, nor in the NEW
queue):

$ grep-excuses r-cran-sna
r-cran-sna (- to 2.5-2)
Maintainer: Debian R Packages Maintainers
Migration status for r-cran-sna (- to 2.5-2): BLOCKED: Rejected/violates 
migration policy/introduces a regression
Issues preventing migration:
r-cran-sna/amd64 has unsatisfiable dependency
r-cran-sna unsatisfiable Build-Depends(-Arch) on amd64: 
r-cran-statnet.common
r-cran-sna unsatisfiable Build-Depends(-Arch) on amd64: r-cran-network
Not built on buildd: arch amd64 binaries uploaded by tille
Additional info:
Cannot be tested by piuparts (not a blocker) - 
https://piuparts.debian.org/sid/source/r/r-cran-sna.html
uninstallable on arch amd64, not running autopkgtest there
136 days old (needed 5 days)
$

There is a 228-day-old wnpp bug for r-cran-network:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951510

and also for r-cran-statnet.common:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951511

So it would be good if those would get uploaded to the archive, given there
is another package that build-depends on them.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.6-1


Both r-cran-statnet.common and r-cran-network have been accepted into
the Debian archive.

-- 
Michael R. Crusoe




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#972505: pgl-ddl-deploy needs porting to PostgreSQL 13

2020-10-19 Thread Christoph Berg

Package: postgresql-12-pgl-ddl-deploy
Version: 1.7.0-1
Severity: serious
Forwarded: https://github.com/enova/pgl_ddl_deploy/issues/55

pgl-ddl-deploy needs porting to PostgreSQL 13.

Please remove pgl-ddl-deploy from testing for the time being so
pglogical and the other pglogical reverse-depends can migrate to
testing.

Christoph

Bug#972504: python-cogent ftbfs with python3.9 as supported python3 version

2020-10-19 Thread Matthias Klose

Package: src:python-cogent
Version: 2020.2.7a+dfsg-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

python-cogent ftbfs with python3.9 as supported python3 version:

[...]
==
ERROR: test_dendro_shape (tests.test_draw.test_dendrogram.TestDendro)
exercising using different values of shape parameter
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_dendrogram.py",
line 125, in test_dendro_shape
fig = dnd.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_annotated_dotplot_remove_tracks
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
removing annotation tracks from dotplot should work
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 209, in test_annotated_dotplot_remove_tracks
orig_fig = dp.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 564, in figure
result = func()
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 355, in _build_2x2_fig
_ = self._build_fig(xaxis="x2", yaxis="y2")
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 326, in _build_fig
f = self.core.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_count_gaps_per_seq
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
creation of drawables works
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 241, in test_count_gaps_per_seq
self._check_drawable_styles(aln.count_gaps_per_seq, styles)
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 140, in _check_drawable_styles
self._check_drawable_attrs(obj.drawable.figure, style)
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 222, in figure
self.layout.yaxis.title = ytitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_dotplot_annotated
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
alignment with / without annotated seqs
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 174, in test_dotplot_annotated
self._check_drawable_attrs(dp.figure, "scatter")
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_dotplot_regression
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
Tests whether dotplot produces traces and in correct ordering. Also tests if
pop_trace() works
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 148, in test_dotplot_regression
_ = dp.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_union (tests.test_util.test_union_dict.UnionDictTests)
correctly adjust a prob vector so all values > minval
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/util/union_dict.py",
line 47, in __getattr__
result = super().__getattr__(item)
AttributeError: 'super' object has no attribute '__getattr__'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_util/test_union_dict.py",
line 63, in test_union
self.assertEqual(d.d.e, 5)
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/util/union_dict.py",
line

Bug#972430: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9

2020-10-19 Thread jim_p

Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430

I found these 2 patches from aur. In my eyes they seem identical

https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/nvidia-340.108-fix-5.9-kernel-
compile.patch

http://ix.io/2Bbp

And as usual, I do not know how to do the patching myself, so I leave it to a
more experienced user.



-- Package-specific info:
uname -a:
Linux mitsos 5.8.0-3-amd64 #1 SMP Debian 5.8.14-1 (2020-10-10) x86_64 GNU/Linux

/proc/version:
Linux version 5.8.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-13) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.8.14-1 (2020-10-10)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-13) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.151528] Console: colour VGA+ 80x25
[0.585389] pci :01:00.0: vgaarb: setting as boot VGA device
[0.585389] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.585389] pci :01:00.0: vgaarb: bridge control possible
[0.585389] vgaarb: loaded
[0.769867] Linux agpgart interface v0.103
[3.307811] nvidia: loading out-of-tree module taints kernel.
[3.307823] nvidia: module license 'NVIDIA' taints kernel.
[3.356487] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.388466] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.388839] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.388849] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.788565] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.850973] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9
[3.851048] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.851117] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.851184] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[9.055136] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Oct 19 14:45 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Oct 19 14:46 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Oct 19 14:46 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Oct 19 14:45 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jun  8 11:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   25 Jun  8 11:36 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jun  8 11:36 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jun  8 11:36 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jun  8 11:36 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jun  8 11:36 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jun  8 11:36 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jun  8 11:36 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Jan  5  2020 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root root   57 Jan  5  2020 
/etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1
lrwxrwxrwx 1 root root   56 Jan  5  2020

Bug#969648: dask, pandas 1.1

The upstream patch doesn't even apply as-is; this version does, but I 
don't have time right now to actually test it.


There's also a circular dependency problem, as dask indirectly 
build-depends on itself and my new pandas makes it uninstallable.


Description: pandas 1.1 compatibility

Origin: part of upstream f212b76fefeb93298205d7d224cbc1f7ed387ce9
Author: Tom Augspurger, Rebecca Palmer

diff --git a/dask/dataframe/core.py b/dask/dataframe/core.py
index 4a5c6d1f..cedd46fc 100644
--- a/dask/dataframe/core.py
+++ b/dask/dataframe/core.py
@@ -2487,7 +2487,7 @@ Dask Name: {name}, {task} tasks"""
 else:
 is_anchored = offset.isAnchored()

-include_right = is_anchored or not hasattr(offset, "_inc")
+include_right = is_anchored or not hasattr(offset, "delta")

 if end == self.npartitions - 1:
 divs = self.divisions
@@ -4106,7 +4106,7 @@ class DataFrame(_Frame):
 left_index=on is None,
 right_index=True,
 left_on=on,
-suffixes=[lsuffix, rsuffix],
+suffixes=(lsuffix, rsuffix),
 npartitions=npartitions,
 shuffle=shuffle,
 )
diff --git a/dask/dataframe/tests/test_dataframe.py 
b/dask/dataframe/tests/test_dataframe.py

index 64c15000..5e4f2bef 100644
--- a/dask/dataframe/tests/test_dataframe.py
+++ b/dask/dataframe/tests/test_dataframe.py
@@ -37,6 +37,9 @@ dsk = {
 meta = make_meta({"a": "i8", "b": "i8"}, index=pd.Index([], "i8"))
 d = dd.DataFrame(dsk, "x", meta, [0, 5, 9, 9])
 full = d.compute()
+CHECK_FREQ = {}
+if dd._compat.PANDAS_GT_110:
+CHECK_FREQ["check_freq"] = False


 def test_dataframe_doc():
@@ -222,7 +225,18 @@ def test_index_names():
 assert ddf.index.compute().name == "x"


-@pytest.mark.parametrize("npartitions", [1, pytest.param(2, 
marks=pytest.mark.xfail)])

+@pytest.mark.parametrize(
+"npartitions",
+[
+1,
+pytest.param(
+2,
+marks=pytest.mark.xfail(
+not dd._compat.PANDAS_GT_110, reason="Fixed upstream."
+),
+),
+],
+)
 def test_timezone_freq(npartitions):
 s_naive = pd.Series(pd.date_range("20130101", periods=10))
 s_aware = pd.Series(pd.date_range("20130101", periods=10, 
tz="US/Eastern"))

@@ -385,12 +399,48 @@ def test_describe_numeric(method, test_values):
 (None, None, None, ["c", "d", "g"]),  # numeric + bool
 (None, None, None, ["c", "d", "f", "g"]),  # numeric + bool + 
timedelta

 (None, None, None, ["f", "g"]),  # bool + timedelta
-("all", None, None, None),
-(["number"], None, [0.25, 0.5], None),
-([np.timedelta64], None, None, None),
-(["number", "object"], None, [0.25, 0.75], None),
-(None, ["number", "object"], None, None),
-(["object", "datetime", "bool"], None, None, None),
+pytest.param(
+"all",
+None,
+None,
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
+pytest.param(
+["number"],
+None,
+[0.25, 0.5],
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
+pytest.param(
+[np.timedelta64],
+None,
+None,
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
+pytest.param(
+["number", "object"],
+None,
+[0.25, 0.75],
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
+pytest.param(
+None,
+["number", "object"],
+None,
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
+pytest.param(
+["object", "datetime", "bool"],
+None,
+None,
+None,
+marks=pytest.mark.xfail(PANDAS_GT_110, reason="upstream 
changes"),

+),
 ],
 )
 def test_describe(include, exclude, percentiles, subset):
@@ -2522,15 +2572,17 @@ def test_to_timestamp():
 index = pd.period_range(freq="A", start="1/1/2001", end="12/1/2004")
 df = pd.DataFrame({"x": [1, 2, 3, 4], "y": [10, 20, 30, 40]}, 
index=index)

 ddf = dd.from_pandas(df, npartitions=3)
-assert_eq(ddf.to_timestamp(), df.to_timestamp())
+assert_eq(ddf.to_timestamp(), df.to_timestamp(), **CHECK_FREQ)
 assert_eq(
 ddf.to_timestamp(freq="M", how="s").compute(),
 df.to_timestamp(freq="M", how="s"),
+**CHECK_FREQ
 )
 assert_eq(ddf.x.to_timestamp(), df.x.to_timestamp())
 assert_eq(
 ddf.x.to_timestamp(freq="M", how="s").compute(),
 df.x.to_timestamp(freq="M", how="s"),
+**CHECK_FREQ
 )


diff --git a/dask/dataframe/tests/test_extensions.py

Bug#972500: hamster-time-tracker does not launch on Buster using the backported package

2020-10-19 Thread Ulrike Uhlig

Package: hamster-time-tracker
Version: 3.0.2-3~bpo10+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

I'm trying to start hamster-time-tracker. I have used the program for
many years (as hamster-applet) and upgraded to the transitional package.

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

Trying to start the program is ineffective.
Trying to reinstall the program did not solve the issue.

   * What was the outcome of this action?
$ hamster
Traceback (most recent call last):
  File "/usr/bin/hamster", line 149, in on_activate_window
self._open_window(action.get_name(), data)
  File "/usr/bin/hamster", line 184, in _open_window
self.overview_controller = Overview()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
__init__
self.find_facts()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
find_facts
self.facts = self.storage.get_facts(start, end, search_terms=search)
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
get_facts
for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
server_version = self._connection.Version()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
_message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name,
interface_name)
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
_method_lookup
raise UnknownMethodException('%s is not a valid method of interface
%s' %
(method_name, dbus_interface))
UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
method: Version is not a valid method of interface org.gnome.Hamster

Traceback (most recent call last):
  File "/usr/bin/hamster", line 149, in on_activate_window
self._open_window(action.get_name(), data)
  File "/usr/bin/hamster", line 184, in _open_window
self.overview_controller = Overview()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 477, in
__init__
self.find_facts()
  File "/usr/lib/python3/dist-packages/hamster/overview.py", line 531, in
find_facts
self.facts = self.storage.get_facts(start, end, search_terms=search)
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 156, in
get_facts
for fact in self.conn.GetFactsJSON(dbus_range, search_terms)]
  File "/usr/lib/python3/dist-packages/hamster/client.py", line 99, in conn
server_version = self._connection.Version()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 654, in
_message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name,
interface_name)
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 246, in
_method_lookup
raise UnknownMethodException('%s is not a valid method of interface
%s' %
(method_name, dbus_interface))
UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown
method: Version is not a valid method of interface org.gnome.Hamster

   * What outcome did you expect instead?

Package should work. Reinstalling should install, or propose missing
libraries,
or software if any.

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



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

Kernel: Linux 4.19.0-11-amd64 (SMP w/4 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hamster-time-tracker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  libjs-jquery 3.3.1~dfsg-3
ii  libjs-jquery-ui  1.12.1+dfsg-5
ii  python3

Bug#962194: marked as done (lintian-brush: autopkgtest failure on s390x)

Your message dated Mon, 19 Oct 2020 10:37:39 +
with message-id 
and subject line Bug#962194: fixed in ruamel.yaml 0.16.12-2
has caused the Debian Bug report #962194,
regarding lintian-brush: autopkgtest failure on s390x
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.)


-- 
962194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lintian-brush
Version: 0.69


Hello, since version 0.68 we are hitting autopkgtest failures on Ubuntu s390x
(but I presume this might be an endianess issue unrelated to Ubuntu, but an 
issue on Debian too)

look e.g.:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lintian-brush/20200526_071151_45b70@/log.gz

or
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lintian-brush/20200602_160733_92e77@/log.gz


autopkgtest [16:06:43]: test tool-testsuite: [---
failed to open trace file: [Errno 13] Permission denied: 
'/you-should-use-TestCaseInTempDir-if-you-need-a-log-file'
.../usr/lib/python3/dist-packages/debian/changelog.py:483: UserWarning: 
Unexpected line while looking for first heading: THIS IS NOT A PARSEABLE LINE
  warnings.warn(message)
/usr/lib/python3/dist-packages/debian/changelog.py:483: 
UserWarning: Unexpected line while looking for first heading: lalalalala
  warnings.warn(message)
/usr/lib/python3/dist-packages/debian/changelog.py:483: UserWarning: Found eof 
where expected first heading
  warnings.warn(message)
./tmp/autopkgtest.aoDwvO/build.6pK/src/lintian_brush/_deb822.py:115: 
UserWarning: cannot parse package relationship "${misc:Depends}", returning it 
raw
  warnings.warn(
...ss...EE.x..sed:
 can't read debian/rules: No such file or directory
sed: can't read debian/rules: No such file or directory
.sed: can't read debian/rules: No such file or directory
sed: can't read debian/rules: No such file or directory
./tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:176:
 UserWarning: A common license shortname (Apache-2.0) is used, but license text 
not recognized.
  warn(
../tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:160: 
UserWarning: Unable to get canonical name for 'BSD-3-clause'
  warn('Unable to get canonical name for %r' % license_id)
/tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:190: 
UserWarning: Found full license text for BSD-3-clause, but unknown synopsis 
BSD-3-clause (BSD-3-clause)
  warn('Found full license text for %s, but unknown synopsis %s (%s)'
.../usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: 
UserWarning: cannot parse package relationship "libf2fs5 (= 
${binary:Version})", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "libf2fs-format4 (= ${binary:Version})", 
returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "${shlibs:Depends}", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "${misc:Depends}", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "f2fs-tools (= ${binary:Version})", returning 
it raw
  warnings.warn(
/usr/lib/python3/dist-packages/debian/changelog.py:483: 
UserWarning: Unexpected line while looking for start of change data:  * Initial 
Release.
  warnings.warn(message)
.../usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115:
 UserWarning: cannot parse package relationship "${misc:Depends}", returning it 
raw
  warnings.warn(
..Tree has non-standard patches directory debian/patches-applied.
..dpkg-architecture: warning: cannot determine CC system 
type, falling back to default (native compilation)
Use of uninitialized value $step in string ne at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/perl_build.pm line 24.
Use of uninitialized value $step in string ne at

Bug#962194: marked as pending in ruamel.yaml

2020-10-19 Thread Michael R. Crusoe

Control: tag -1 pending

Hello,

Bug #962194 in ruamel.yaml 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/packages/ruamel.yaml/-/commit/f1f3a6991f6d3531ab203157d68c4fe317c4feeb


default to pure Python processing on big-endian systems

Closes: #962194


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962194

Processed: Bug#962194 marked as pending in ruamel.yaml

Processing control commands:

> tag -1 pending
Bug #962194 [ruamel.yaml] lintian-brush: autopkgtest failure on s390x
Added tag(s) pending.

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

Bug#972469: marked as done (joblib: TerminatedWorkerError, AttributeError: '_SafeQueue' object has no attribute '_notempty' with Python 3.9)

Your message dated Mon, 19 Oct 2020 10:04:01 +
with message-id 
and subject line Bug#972469: fixed in joblib 0.17.0-0.1
has caused the Debian Bug report #972469,
regarding joblib: TerminatedWorkerError, AttributeError: '_SafeQueue' object 
has no attribute '_notempty' with Python 3.9
to be marked as done.

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

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


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

Package: python3-joblib
Tags: fixed-upstream
Control: affects -1 scikit-learn statsmodels
Control: block 966426 by -1
Severity: serious
Justification: causes other packages to FTBFS

Our current version of joblib is incompatible with Python 3.9, which was 
recently added to the supported versions list (#966426).  This causes at 
least scikit-learn and statsmodels to fail their tests.


Upstream fix: https://github.com/joblib/loky/pull/250

Traceback (from scikit-learn test log):

___ test_multi_class_n_jobs[kernel3] 
___


kernel = 1**2 * RBF(length_scale=1)

@pytest.mark.parametrize('kernel', kernels)
def test_multi_class_n_jobs(kernel):
# Test that multi-class GPC produces identical results with 
n_jobs>1.

gpc = GaussianProcessClassifier(kernel=kernel)
gpc.fit(X, y_mc)

gpc_2 = GaussianProcessClassifier(kernel=kernel, n_jobs=2)
>   gpc_2.fit(X, y_mc)

sklearn/gaussian_process/tests/test_gpc.py:178:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

sklearn/gaussian_process/_gpc.py:657: in fit
self.base_estimator_.fit(X, y)
sklearn/multiclass.py:241: in fit
self.estimators_ = Parallel(n_jobs=self.n_jobs)(delayed(_fit_binary)(
/usr/lib/python3/dist-packages/joblib/parallel.py:1016: in __call__
self.retrieve()
/usr/lib/python3/dist-packages/joblib/parallel.py:908: in retrieve
self._output.extend(job.get(timeout=self.timeout))
/usr/lib/python3/dist-packages/joblib/_parallel_backends.py:554: in 
wrap_future_result

return future.result(timeout=timeout)
/usr/lib/python3.9/concurrent/futures/_base.py:440: in result
return self.__get_result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _


self = TerminatedWorkerError>


def __get_result(self):
if self._exception:
>   raise self._exception
E 
joblib.externals.loky.process_executor.TerminatedWorkerError: A worker 
process managed by the executor was unexpectedly terminated. This could 
be caused by a segmentation fault while calling the function or by an 
excessive memory usage causing the Operating System to kill the worker. 
The exit codes of the workers are {EXIT(1)}


/usr/lib/python3.9/concurrent/futures/_base.py:389: TerminatedWorkerError
- Captured stdout call 
-




LokyProcess-45 failed with traceback:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/joblib/externals/loky/backend/popen_loky_posix.py", 
line 195, in 

process_obj = pickle.load(from_parent)
  File 
"/usr/lib/python3/dist-packages/joblib/externals/loky/backend/queues.py", 
line 75, in __setstate__

self._after_fork()
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 69, in 
_after_fork

self._reset(after_fork=True)
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 73, in _reset
self._notempty._at_fork_reinit()
AttributeError: '_SafeQueue' object has no attribute '_notempty'






LokyProcess-46 failed with traceback:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/joblib/externals/loky/backend/popen_loky_posix.py", 
line 195, in 

process_obj = pickle.load(from_parent)
  File 
"/usr/lib/python3/dist-packages/joblib/externals/loky/backend/queues.py", 
line 75, in __setstate__

self._after_fork()
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 69, in 
_after_fork

self._reset(after_fork=True)
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 73, in _reset
self._notempty._at_fork_reinit()
AttributeError: '_SafeQueue' object has no attribute '_notempty'

Bug#959639: marked as done (joblib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

Your message dated Mon, 19 Oct 2020 10:04:01 +
with message-id 
and subject line Bug#959639: fixed in joblib 0.17.0-0.1
has caused the Debian Bug report #959639,
regarding joblib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.8 returned exit code 13
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.)


-- 
959639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: joblib
Version: 0.14.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package joblib
> dpkg-buildpackage: info: source version 0.14.0-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Stuart Prescott 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --buildsystem=pybuild --with=python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building joblib using existing ./joblib_0.14.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building joblib in joblib_0.14.0-3.debian.tar.xz
> dpkg-source: info: building joblib in joblib_0.14.0-3.dsc
>  debian/rules binary
> dh binary --buildsystem=pybuild --with=python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/backports.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_store_backends.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/numpy_pickle.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_compat.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/func_inspect.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_memmapping_reducer.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/memory.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_parallel_backends.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/logger.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/format_stack.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/compressor.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/hashing.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/my_exceptions.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_dask.py -> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_memory_helpers.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/_multiprocessing_helpers.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/numpy_pickle_utils.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/executor.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/pool.py -> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/numpy_pickle_compat.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/parallel.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/testing.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib
> copying joblib/disk.py -> /<>/.pybuild/cpython3_3.8/build/joblib
> creating /<>/.pybuild/cpython3_3.8/build/joblib/test
> copying joblib/test/test_my_exceptions.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib/test
> copying joblib/test/test_parallel.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib/test
> copying joblib/test/test_numpy_pickle_utils.py -> 
> /<>/.pybuild/cpython3_3.8/build/joblib/test
> copying

Bug#972490: rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED

2020-10-19 Thread Aurelien Jarno

Source: rubygems 
Version: 3.2.0~rc.1-2
Severity: serious

- Forwarded message from Debian FTP Masters 
 -

From: Debian FTP Masters 
To: all Build Daemon 
Date: Mon, 19 Oct 2020 03:49:20 +
Subject: rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED
Message-Id: 

Version check failed:
Your upload included the binary package ruby-bundler, version 2.2.0~rc.1, for 
all,
however unstable already has version 2.2.0~rc.1.
Uploads to unstable must have a higher version than present in unstable.

Mapping sid to unstable.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

- End forwarded message -

Bug#972451: marked as done (fckit: binary-all FTBFS)

Your message dated Mon, 19 Oct 2020 07:18:22 +
with message-id 
and subject line Bug#972451: fixed in fckit 0.9.0-3
has caused the Debian Bug report #972451,
regarding fckit: binary-all FTBFS
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=fckit=all=0.9.0-2=1603019016=0

...
   dh_missing -i -O--buildsystem=ecbuild
dh_missing: warning: usr/module/fckit/array.mod exists in debian/tmp but is not 
installed to anywhere (related file: "debian/build-gfortran/module/array.mod")
dh_missing: warning: usr/module/fckit/fckit_array_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_array_module.mod")
dh_missing: warning: usr/module/fckit/fckit_buffer_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_buffer_module.mod")
dh_missing: warning: usr/module/fckit/fckit_c_interop_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_c_interop_module.mod")
dh_missing: warning: usr/module/fckit/fckit_configuration_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_configuration_module.mod")
dh_missing: warning: usr/module/fckit/fckit_exception_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_exception_module.mod")
dh_missing: warning: usr/module/fckit/fckit_final_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_final_module.mod")
dh_missing: warning: usr/module/fckit/fckit_log_module.mod exists in debian/tmp 
but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_log_module.mod")
dh_missing: warning: usr/module/fckit/fckit_main_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_main_module.mod")
dh_missing: warning: usr/module/fckit/fckit_module.mod exists in debian/tmp but 
is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_module.mod")
dh_missing: warning: usr/module/fckit/fckit_mpi_module.mod exists in debian/tmp 
but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_mpi_module.mod")
dh_missing: warning: usr/module/fckit/fckit_object_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_object_module.mod")
dh_missing: warning: usr/module/fckit/fckit_owned_object_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_owned_object_module.mod")
dh_missing: warning: usr/module/fckit/fckit_pathname_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_pathname_module.mod")
dh_missing: warning: usr/module/fckit/fckit_refcount_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_refcount_module.mod")
dh_missing: warning: usr/module/fckit/fckit_resource_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_resource_module.mod")
dh_missing: warning: usr/module/fckit/fckit_shared_object_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_shared_object_module.mod")
dh_missing: warning: usr/module/fckit/fckit_shared_ptr_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_shared_ptr_module.mod")
dh_missing: warning: usr/module/fckit/fckit_signal_module.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_signal_module.mod")
dh_missing: warning: usr/module/fckit/fckit_test_abort.mod exists in debian/tmp 
but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_test_abort.mod")
dh_missing: warning: usr/module/fckit/fckit_test_abort_fx.mod exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/build-gfortran/module/fckit_test_abort_fx.mod")
dh_missing: warning:

Bug#966847: marked as done (wine-development: FTBFS: cpanelfolder.c:262:5: error: ‘strcpy’ offset 12 from the object at ‘pidl’ is out of the bounds of referenced subobject ‘szName’ with type ‘CHAR[1]’