Processed: severity of 969261 is important

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 969261 important
Bug #969261 [cyrus-imapd] cyrus-imapd: the service cyrus-imapd.service refuses 
to start after the upgrade of cyrus-imapd.3.2.3 from cyrus-imapd.3.2.2 and a 
reboot
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Processed: lib3mf: diff to use shlibs instead of symbols

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tags 957420 + patch
Bug #957420 [src:lib3mf] lib3mf: ftbfs with GCC-10
Added tag(s) patch.

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



Processed: py2removal bugs severity updates - 2020-09-26 04:34:06.577250+00:00

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

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



Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

2020-09-25 Thread José Luis Blanco-Claraco
Hi Sebastian (cc: Scott):

On Fri, Sep 25, 2020 at 10:50 PM Sebastian Ramacher
 wrote:
> Reducing the optimization level on mips64el might help to reduce the
> compile time. Alternatively, if possible, one could split the source
> files into smaller ones.

Hmmm... great idea!

In fact, there was already a piece of logic in debian/rules but was
only active in "mipsel", I have updated it upstream via this
commit/patch:
https://github.com/MRPT/mrpt/commit/8d60d8b5bc6e50e605c965ace165837840fb4c34

Do you think it might be worth submitting version 1:2.1.0-2 via a patch?

@Scott: Should I upload an entire new package to mentors.debian.net,
or would it be enough to send our the patch file, if you are willing
to sponsor the new upload?

Best,
JL



Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

2020-09-25 Thread Scott Talbert

On Sat, 26 Sep 2020, José Luis Blanco-Claraco wrote:


On Fri, Sep 25, 2020 at 10:50 PM Sebastian Ramacher
 wrote:

Reducing the optimization level on mips64el might help to reduce the
compile time. Alternatively, if possible, one could split the source
files into smaller ones.


Hmmm... great idea!

In fact, there was already a piece of logic in debian/rules but was
only active in "mipsel", I have updated it upstream via this
commit/patch:
https://github.com/MRPT/mrpt/commit/8d60d8b5bc6e50e605c965ace165837840fb4c34

Do you think it might be worth submitting version 1:2.1.0-2 via a patch?

@Scott: Should I upload an entire new package to mentors.debian.net,
or would it be enough to send our the patch file, if you are willing
to sponsor the new upload?


If you don't mind, please do a new package upload to mentors.

Thanks,
Scott

Bug#933110: pkg-components: No upstream maintainer ⇒ unsuitable for Bullseye

2020-09-25 Thread gregor herrmann
On Thu, 20 Aug 2020 11:23:42 +0200, intrigeri wrote:

> Simon McVittie (2020-08-20):
> >> I'll file bugs against all reverse-dependencies to alert their
> >> maintainer about this situation.
> > Should the bugs against rdeps be escalated to serious at this point,
> > potentially triggering autoremovals?
> I think now is a good time, indeed. Doing so.

All reverse build dependencies are fixed, and:


$ dak rm -s unstable -Rn pkg-components
Will remove the following packages from unstable:

pkg-components |   0.13 | source, all

Maintainer: Debian Perl Group 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Any last words before we file an RM bug?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Element Of Crime: Seit der Himmel


signature.asc
Description: Digital Signature


Processed: fixed 917485 in ckermit/302-5.3+deb9u1

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 917485 ckermit/302-5.3+deb9u1
Bug #917485 [ckermit] ckermit: relax openssl version check or tighten 
libssl1.x.y dependencies
Marked as fixed in versions ckermit/302-5.3+deb9u1.
> thanks
Stopping processing here.

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



Processed: found 917485 in 305~alpha02-1

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 917485 305~alpha02-1
Bug #917485 [ckermit] ckermit: relax openssl version check or tighten 
libssl1.x.y dependencies
Marked as found in versions ckermit/305~alpha02-1.
> thanks
Stopping processing here.

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



Bug#970876: marked as done (gimp: autopkgtest failure: libgimp/gimpthumb.h: No such file or directory)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 23:03:33 +
with message-id 
and subject line Bug#970876: fixed in gimp 2.10.20-2
has caused the Debian Bug report #970876,
regarding gimp: autopkgtest failure: libgimp/gimpthumb.h: No such file or 
directory
to be marked as done.

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

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


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

Dear maintainer(s),

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gimp/6942995/log.gz

autopkgtest [03:09:38]: test libgimp2.0-dev: [---
+ mktemp -d
+ WORKDIR=/tmp/tmp.K2nraOrlN0
+ export XDG_RUNTIME_DIR=/tmp/tmp.K2nraOrlN0
+ trap rm -rf "$WORKDIR" 0 INT QUIT ABRT PIPE TERM
+ cd /tmp/tmp.K2nraOrlN0
+ [ -n  ]
+ CROSS_COMPILE=
+ cat
+ cat
+ cat
+ pkg-config --cflags --libs gimp-2.0
+ gcc -o gimp-2.0-test gimp-2.0.c -pthread -I/usr/include/gimp-2.0
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/gegl-0.4
-I/usr/include/gio-unix-2.0 -I/usr/include/json-glib-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/babl-0.1
-lgimp-2.0 -lgimpmath-2.0 -lgimpconfig-2.0 -lgimpcolor-2.0
-lgimpbase-2.0 -lgdk_pixbuf-2.0 -lcairo -lgegl-0.4 -lgegl-npd-0.4 -lm
-Wl,--export-dynamic -lgmodule-2.0 -pthread -ljson-glib-1.0 -lgio-2.0
-lgobject-2.0 -lglib-2.0 -lbabl-0.1
+ echo build (gimp-2.0): OK
+ [ -x gimp-2.0-test ]
+ xvfb-run -a ./gimp-2.0-test
build (gimp-2.0): OK
+ echo run (gimp-2.0): OK
run (gimp-2.0): OK
+ pkg-config --cflags --libs gimpthumb-2.0
+ gcc -o gimpthumb-2.0-test gimpthumb-2.0.c -pthread
-I/usr/include/gimp-2.0 -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -lgimpthumb-2.0
-lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
gimpthumb-2.0.c:1:10: fatal error: libgimp/gimpthumb.h: No such file or
directory
1 | #include 
  |  ^
compilation terminated.
+ rm -rf /tmp/tmp.K2nraOrlN0
autopkgtest [03:09:38]: test libgimp2.0-dev: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gimp
Source-Version: 2.10.20-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gimp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Sep 2020 22:41:03 +0100
Source: gimp
Architecture: source
Version: 2.10.20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 970876
Changes:
 gimp (2.10.20-2) unstable; urgency=medium
 .
   * Team upload
   * Correct bug number in previous changelog entry
 (was #956183, should have been #956200)
   * d/tests/libgimp2.0-dev: Fix autopkgtest (Closes: #970876)
Checksums-Sha1:
 63cf2065f1649a84a6300733f1bc1e5f0261c9d1 3475 gimp_2.10.20-2.dsc
 a251cc2124b12211b570c93fead2305f462261c3 57924 gimp_2.10.20-2.debian.tar.xz
 29c1add4c7b90226bc2d296f1ff195e5d7a566e0 17494 gimp_2.10.20-2_source.buildinfo
Checksums-Sha256:
 8f3e95b97ff60e69583761bf7b62895b46041ca454ca3d933b02cd83aabd153a 3475 
gimp_2.10.20-2.dsc
 a683ab3ed8171561eeaaf662f3dca2dfb96883f3d4bcd16f602f5b884c4f77da 57924 
gimp_2.10.20-2.debian.tar.xz
 

Processed: closing 918061

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 918061 305~alpha02-1
Bug #918061 [ckermit] Should ckermit be removed?
Marked as fixed in versions ckermit/305~alpha02-1.
Bug #918061 [ckermit] Should ckermit be removed?
Marked Bug as done
> thanks
Stopping processing here.

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



Processed: closing 859719, closing 847453

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 859719 2.0.0-1
Bug #859719 [sslscan] sslscan: Please migrate to openssl1.1 in Buster
Marked as fixed in versions sslscan/2.0.0-1.
Bug #859719 [sslscan] sslscan: Please migrate to openssl1.1 in Buster
Marked Bug as done
> close 847453 2.0.0-1
Bug #847453 [sslscan] new upstream (1.11.8-rbsec)
Marked as fixed in versions sslscan/2.0.0-1.
Bug #847453 [sslscan] new upstream (1.11.8-rbsec)
Marked Bug as done
> thanks
Stopping processing here.

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



Processed: Bug#970876 marked as pending in gimp

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #970876 [src:gimp] gimp: autopkgtest failure: libgimp/gimpthumb.h: No such 
file or directory
Added tag(s) pending.

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



Processed: unarchiving 859719, reopening 859719, unarchiving 847453, reopening 847453, unarchiving 844025 ...

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # src:sslscan was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 859719
Bug #859719 {Done: Debian FTP Masters } 
[sslscan] sslscan: Please migrate to openssl1.1 in Buster
Unarchived Bug 859719
> reopen 859719
Bug #859719 {Done: Debian FTP Masters } 
[sslscan] sslscan: Please migrate to openssl1.1 in Buster
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.11.5-rbsec-1.1+rm.
> unarchive 847453
Bug #847453 {Done: Debian FTP Masters } 
[sslscan] new upstream (1.11.8-rbsec)
Unarchived Bug 847453
> reopen 847453
Bug #847453 {Done: Debian FTP Masters } 
[sslscan] new upstream (1.11.8-rbsec)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.11.5-rbsec-1.1+rm.
> unarchive 844025
Bug #844025 {Done: Debian FTP Masters } 
[sslscan] sslscan: static build
Unarchived Bug 844025
> reopen 844025
Bug #844025 {Done: Debian FTP Masters } 
[sslscan] sslscan: static build
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.11.5-rbsec-1.1+rm.
> thanks
Stopping processing here.

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



Bug#970876: marked as pending in gimp

2020-09-25 Thread Simon McVittie
Control: tag -1 pending

Hello,

Bug #970876 in gimp 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/gnome-team/gimp/-/commit/32433b164e2a3be7c04443307291b1875d87f2f7


d/tests/libgimp2.0-dev: Fix autopkgtest

Closes: #970876


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/970876



Processed: unarchiving 917485, reopening 917485, unarchiving 918061, reopening 918061

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # src:ckermit was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 917485
Bug #917485 {Done: Sebastian Andrzej Siewior } 
[ckermit] ckermit: relax openssl version check or tighten libssl1.x.y 
dependencies
Unarchived Bug 917485
> reopen 917485
Bug #917485 {Done: Sebastian Andrzej Siewior } 
[ckermit] ckermit: relax openssl version check or tighten libssl1.x.y 
dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 302-5.3+rm and ckermit/302-5.3+deb9u1.
> unarchive 918061
Bug #918061 {Done: Debian FTP Masters } 
[ckermit] Should ckermit be removed?
Unarchived Bug 918061
> reopen 918061
Bug #918061 {Done: Debian FTP Masters } 
[ckermit] Should ckermit be removed?
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 302-5.3+rm.
> thanks
Stopping processing here.

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



Bug#933114: marked as done (libcgi-application-plugin-devpopup-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 22:19:14 +
with message-id 
and subject line Bug#933114: fixed in libcgi-application-plugin-devpopup-perl 
1.08+~cs2.4-1
has caused the Debian Bug report #933114,
regarding libcgi-application-plugin-devpopup-perl: build-depends on 
pkg-components that won't be in Bullseye unless it finds a new upstream 
maintainer
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.)


-- 
933114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgi-application-plugin-devpopup-perl
Severity: important
User: debian-p...@lists.debian.org
Usertags: pkg-components-removal

Hi,

libcgi-application-plugin-devpopup-perl build-depends on
pkg-components. The Debian Perl group has decided today that we don't
want pkg-components to be included in the Bullseye release, unless
someone steps up and volunteers to be its upstream maintainer:
https://bugs.debian.org/933110

If libcgi-application-plugin-devpopup-perl is suitable for Bullseye,
please either port libcgi-application-plugin-devpopup-perl away from
pkg-components or consider taking over its maintenance upstream.

Thanks in advance!

Cheers, 
-- 
intrigeri, for the Debian Perl group
--- End Message ---
--- Begin Message ---
Source: libcgi-application-plugin-devpopup-perl
Source-Version: 1.08+~cs2.4-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcgi-application-plugin-devpopup-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Sep 2020 00:02:44 +0200
Source: libcgi-application-plugin-devpopup-perl
Architecture: source
Version: 1.08+~cs2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 933114
Changes:
 libcgi-application-plugin-devpopup-perl (1.08+~cs2.4-1) unstable; 
urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/upstream/metadata: change GitHub/CPAN URL(s) to HTTPS.
   * Remove Jaldhar H. Vyas from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
   * Drop pkg-components framework. (Closes: #933114)
   * Update debian/watch to multi upstream tarball.
   * Add debian/gbp.conf for MUT support.
 .
   * Import "upstream" version 1.08+~cs2.4.
   * Update debian/rules to new component setup.
   * Add debian/tests/pkg-perl/smoke-test to run all tests
 during autopkgtest.
   * Add /me to Uploaders.
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Drop unneeded version constraints from (build) dependencies, and old
 Breaks/Replaces.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata.
   * Add empty debian/tests/pkg-perl/syntax-skip to run syntax.t for all
 modules during autopkgtest.
Checksums-Sha1:
 b19905fd530b9627672c0123ec88aa683713c79f 3658 
libcgi-application-plugin-devpopup-perl_1.08+~cs2.4-1.dsc
 e78297c20ee6b40625043637522b64a7475c203d 3059 
libcgi-application-plugin-devpopup-perl_1.08+~cs2.4.orig-p.tar.gz
 97bfcae9108999cf4c6301f4f31cb34ee7f9642f 3194 
libcgi-application-plugin-devpopup-perl_1.08+~cs2.4.orig-q.tar.gz
 322dbc83dc20c151de5b35ac1b582ee70c6a91a8 16576 
libcgi-application-plugin-devpopup-perl_1.08+~cs2.4.orig.tar.gz
 afa03cdf14ae5fee2dd20a8a93de74a83a03d9f6 3404 
libcgi-application-plugin-devpopup-perl_1.08+~cs2.4-1.debian.tar.xz
Checksums-Sha256:
 

Bug#933112: marked as done (libcgi-application-plugin-authentication-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 22:03:44 +
with message-id 
and subject line Bug#933112: fixed in 
libcgi-application-plugin-authentication-perl 0.23+~cs0.5-1
has caused the Debian Bug report #933112,
regarding libcgi-application-plugin-authentication-perl: build-depends on 
pkg-components that won't be in Bullseye unless it finds a new upstream 
maintainer
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.)


-- 
933112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgi-application-plugin-authentication-perl
Severity: important
User: debian-p...@lists.debian.org
Usertags: pkg-components-removal

Hi,

libcgi-application-plugin-authentication-perl build-depends on
pkg-components. The Debian Perl group has decided today that we don't
want pkg-components to be included in the Bullseye release, unless
someone steps up and volunteers to be its upstream maintainer:
https://bugs.debian.org/933110

If libcgi-application-plugin-authentication-perl is suitable for
Bullseye, please either port
libcgi-application-plugin-authentication-perl away from
pkg-components or consider taking over its maintenance upstream.

Thanks in advance!

Cheers, 
-- 
intrigeri, for the Debian Perl group
--- End Message ---
--- Begin Message ---
Source: libcgi-application-plugin-authentication-perl
Source-Version: 0.23+~cs0.5-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcgi-application-plugin-authentication-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 23:40:30 CEST
Source: libcgi-application-plugin-authentication-perl
Binary: 
Architecture: source
Version: 0.23+~cs0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Built-For-Profiles: nocheck
Changed-By: gregor herrmann 
Description: 
Closes: 933112
Changes:
 libcgi-application-plugin-authentication-perl (0.23+~cs0.5-1) unstable; 
urgency=medium
 .
   * debian/watch: use uscan version 4.
   * Remove pkg-components framework. (Closes: #933112)
   * Update debian/watch to multi upstream tarballs.
   * Update debian/gbp.conf to multi upstream tarball.
 .
   * Import "upstream" version 0.23+~cs0.5.
   * Update debian/rules to multi components.
   * Add debian/tests/pkg-perl/smoke-tests to run all smoke tests
 during autopkgtest.
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Drop unneeded version constraints from (build) dependencies, and
 Breaks/Replaces.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
   * Set upstream metadata fields: Bug-Submit.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata.
   * Add test dependency on libreadonly-perl.
Checksums-Sha256: 
 13f7a69e1669caba3448940e63b40939350211c6736dc3626b4c56966ee7edd5 4131 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5-1.dsc
 facde3c320a05fd2a39a9449b651af73f9adbce097581ca078fbd77643e1cad7 6352 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5.orig-driver-cdbi.tar.gz
 a89f53d63be9deca5933e2d386a071923a404c2961f0e9fd93731ba0a8a0fce5 7739 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5.orig-driver-dbic.tar.gz
 80745e2118a66eb40fc2bba1b884c0fd8581968747111848da905482f437db48 107909 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5.orig.tar.gz
 6d621168dae7dd028a4afcf68c85a0d985855e20455f5c9202209c6582e9e3e0 10360 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5-1.debian.tar.xz
 0f8327f66e3c50917bc7101d5f646d5ea98fc1bdef14e672c2aa5cdfd78b224e 5969 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5-1_sourceonly.buildinfo
Checksums-Sha1: 
 1486f659e04705386be1c05f10969b5634000256 4131 
libcgi-application-plugin-authentication-perl_0.23+~cs0.5-1.dsc
 f976874ba8c1e8049424062db9d2638f27f7fbcb 6352 

Bug#970762: in package pciutils marked as pending

2020-09-25 Thread Guillem Jover
Hi!

On Fri, 2020-09-25 at 20:44:54 +0200, Daniel Leidert wrote:
> Control: reopen 970762
> 
> Am Mittwoch, den 23.09.2020, 03:13 +0200 schrieb Guillem Jover:
> > ---
> > commit c2c28549a513b93898d8c49f6eb8cefc1670a1e2
> > Author: Guillem Jover 
> > Date:   Wed Sep 23 03:00:35 2020 +0200
> > 
> > Force the hardlink for the backup pci.ids database in update-pciids
> > 
> > Closes: #970762, #970762
> 
> This patch only fixes the creation of the hardlink of pci.ids.gz.old ->
> pci.ids.gz, which btw seems really odd to me (why do we need this link?
> shouldn't .old be or at least link to the previous database?).

The hardlink is used to make a backup, then the destination file gets
replaced with the new database.

> However /usr/share/misc/pci.ids is still deleted and breaks virt-manager.
> 
> I was checking the script and it seems it fails somwhere at lines 52-60. If I
> print out the commands it looks like this:

Ugh, sorry completely missed this in the original report. :(

I've checked the code, and it seems there are several wrong things,
which I'll be fixing. First the PCI_IDS defaults to the compressed
file, but the pci.ids.deb ships an uncompressed one. Then the script
conflates the format that it downloads from, but does not cover what
it should write it to.

> Reopening report.

Thanks, will fix this tomorrow.

Regards,
Guillem



Bug#970933: geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 3.38.0

2020-09-25 Thread Simon McVittie
On Fri, 25 Sep 2020 at 21:31:02 +0200, Paul Gevers wrote:
> autopkgtest [06:10:02]: test version: [---
> Expected: geary: 3.38.0.1
>  Got: geary: 3.38.0
> autopkgtest [06:10:03]: test version: ---]

This appears to be because the upstream tarball is missing commit
26f3878 "Update files for 3.38.0.1" for some reason.

smcv



Processed: Bug#933112 marked as pending in libcgi-application-plugin-authentication-perl

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933112 [libcgi-application-plugin-authentication-perl] 
libcgi-application-plugin-authentication-perl: build-depends on pkg-components 
that won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) pending.

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



Bug#933112: marked as pending in libcgi-application-plugin-authentication-perl

2020-09-25 Thread gregor herrmann
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-authentication-perl/-/commit/38b9f3598c18a202ada1a50cde7acea88fe63cdb


Remove pkg-components framework.

Closes: #933112


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933112



Bug#968335: kernel hangs on linux-image-4.19.0-10-amd64

2020-09-25 Thread Mike Gulick
I have also seen a number of systems hang after upgrading to this kernel 
version.  It appears to happen when the system has docker containers 
running, possibly related to the virtual ethernet devices.  On some 
systems, I can trigger the bug within an hour or two of uptime.  Rolling 
back to 4.19.0-9 resolves the problem.  I also tried 4.19.0-11 from 
buster-proposed-updates on one system, and the system seems to be stable 
on that kernel as well.


-Mike



Bug#933115: marked as done (libcgi-application-plugin-tt-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 21:33:28 +
with message-id 
and subject line Bug#933115: fixed in libcgi-application-plugin-tt-perl 
1.05+~cs1.2-1
has caused the Debian Bug report #933115,
regarding libcgi-application-plugin-tt-perl: build-depends on pkg-components 
that won't be in Bullseye unless it finds a new upstream maintainer
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.)


-- 
933115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgi-application-plugin-tt-perl
Severity: important
User: debian-p...@lists.debian.org
Usertags: pkg-components-removal

Hi,

libcgi-application-plugin-tt-perl build-depends on pkg-components.
The Debian Perl group has decided today that we don't want
pkg-components to be included in the Bullseye release, unless someone
steps up and volunteers to be its upstream maintainer:
https://bugs.debian.org/933110

If libcgi-application-plugin-tt-perl is suitable for Bullseye, please
either port libcgi-application-plugin-tt-perl away from
pkg-components or consider taking over its maintenance upstream.

Thanks in advance!

Cheers, 
-- 
intrigeri, for the Debian Perl group
--- End Message ---
--- Begin Message ---
Source: libcgi-application-plugin-tt-perl
Source-Version: 1.05+~cs1.2-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcgi-application-plugin-tt-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 22:53:01 +0200
Source: libcgi-application-plugin-tt-perl
Architecture: source
Version: 1.05+~cs1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 933115
Changes:
 libcgi-application-plugin-tt-perl (1.05+~cs1.2-1) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Change bugtracker URL(s) to HTTPS.
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Jaldhar H. Vyas from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
   * Drop pkg-components framework. (Closes: #933115)
   * Update debian/watch to multi upstream tarballs.
   * Add debian/gbp.conf for component feature.
   * Update debian/rules to components.
 .
   * Import "upstream" version 1.05+~cs1.2.
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Drop old Breaks/Replaces.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
   * Add /me to Uploaders.
   * Add debian/tests/pkg-perl/smoke-tests to run tests for component
 during autopkgtest.
Checksums-Sha1:
 2abc318d69379a5713d933409c558d48a5c4c676 3213 
libcgi-application-plugin-tt-perl_1.05+~cs1.2-1.dsc
 cbc92108947adf03c15cc5f3f9ae37eae9fa7a7a 4116 
libcgi-application-plugin-tt-perl_1.05+~cs1.2.orig-lastmodified.tar.gz
 7024f78496cc6ba8890f3832a25dae118a274fa2 19044 
libcgi-application-plugin-tt-perl_1.05+~cs1.2.orig.tar.gz
 2672e132b1cecd388f35191928748771ace1b482 3472 
libcgi-application-plugin-tt-perl_1.05+~cs1.2-1.debian.tar.xz
Checksums-Sha256:
 8d9a292533c445024fe7a753fcc989e32f3d96dc32883e3999e470f6aad48f92 3213 
libcgi-application-plugin-tt-perl_1.05+~cs1.2-1.dsc
 dfec278c17b8d45eb64e6595f55f199551b77b193eda2963015ae88b7a413612 4116 
libcgi-application-plugin-tt-perl_1.05+~cs1.2.orig-lastmodified.tar.gz
 00d7311c4c664b9b689b89b11ecda6ddacc28e3ee66b0e5c0c9bd1dd29f9f31a 19044 
libcgi-application-plugin-tt-perl_1.05+~cs1.2.orig.tar.gz
 93b718f78b2ea86a50391b065fa1479e7204cecca6ae76b5d8a50932527d4469 3472 
libcgi-application-plugin-tt-perl_1.05+~cs1.2-1.debian.tar.xz
Files:
 c1740f0f34d6e5a61b2b8f403cc0ac02 3213 perl optional 

Bug#933115: marked as pending in libcgi-application-plugin-tt-perl

2020-09-25 Thread gregor herrmann
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-tt-perl/-/commit/9221bec9c912a66a8040ce182bf5ba31c82fa8e2


Drop pkg-components framework.

Closes: #933115


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933115



Processed: Bug#933115 marked as pending in libcgi-application-plugin-tt-perl

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933115 [libcgi-application-plugin-tt-perl] 
libcgi-application-plugin-tt-perl: build-depends on pkg-components that won't 
be in Bullseye unless it finds a new upstream maintainer
Added tag(s) pending.

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



Bug#970941: f2fs-tools: CVE-2020-6070

2020-09-25 Thread Salvatore Bonaccorso
Source: f2fs-tools
Version: 1.11.0-1.1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for f2fs-tools.

CVE-2020-6070[0]:
| An exploitable code execution vulnerability exists in the file system
| checking functionality of fsck.f2fs 1.12.0. A specially crafted f2fs
| file can cause a logic flaw and out-of-bounds heap operations,
| resulting in code execution. An attacker can provide a malicious file
| to trigger this vulnerability.


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-6070
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6070
[1] https://talosintelligence.com/vulnerability_reports/TALOS-2020-0988

Please adjust the affected versions in the BTS as needed.

Note, I did try to reach out to upstream to isolate the upstream
fixes, but got not repsonse so far. In any case bullseye should
ideally get a newer version, thus the RC severity (ortogonally to it,
the issue wouldbe no-dsa for buster).

Regards,
Salvatore



Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

2020-09-25 Thread Sebastian Ramacher
On 2020-09-25 07:58:56 +0200, José Luis Blanco-Claraco wrote:
> Thanks for reporting, Sebastian!
> 
> Although, I'm not sure how to proceed in this case... it compiled in
> the past but it looks like the builder machine entered into swapping
> (?) this time.

Reducing the optimization level on mips64el might help to reduce the
compile time. Alternatively, if possible, one could split the source
files into smaller ones.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#970935: glib-networking breaks libsoup2.4 autopkgtest: libsoup-2.4/ssl-test.test (Child process killed by signal 5)

2020-09-25 Thread Paul Gevers
Source: glib-networking, libsoup2.4
Control: found -1 glib-networking/2.66.0-1
Control: found -1 libsoup2.4/2.70.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of glib-networking the autopkgtest of libsoup2.4
fails in testing when that autopkgtest is run with the binary packages
of glib-networking from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
glib-networkingfrom testing2.66.0-1
libsoup2.4 from testing2.70.0-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/libs/libsoup2.4/7182493/log.gz

Running test: libsoup-2.4/ssl-test.test
# random seed: R02S0708d54b4a1a80d57044bd9d7e4d6122
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation
gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’
**
ERROR:../tests/ssl-test.c:451:main: assertion failed (error == NULL):
Failed to populate trust list from /dev/null: No certificate was found.
(g-tls-error-quark, 1)
# ERROR:../tests/ssl-test.c:451:main: assertion failed (error == NULL):
Failed to populate trust list from /dev/null: No certificate was found.
(g-tls-error-quark, 1)
1..12
# Start of ssl tests
# Bug Reference: https://bugzilla.gnome.org/673678
ok 1 /ssl/session-properties
ok 2 /ssl/tls-interaction # SKIP Not reliable?
https://gitlab.gnome.org/GNOME/libsoup/issues/120
# Start of message-properties tests
# GLib-GIO-DEBUG: GSocketClient: Starting new address enumeration
# GLib-GIO-DEBUG: GSocketClient: Address enumeration succeeded
# GLib-GIO-DEBUG: GSocketClient: Starting TCP connection attempt
# GLib-GIO-DEBUG: GSocketClient: TCP connection successful
# GLib-GIO-DEBUG: GSocketClient: Starting application layer connection
# GLib-GIO-DEBUG: GSocketClient: Connection successful!
# Bug Reference: https://bugzilla.gnome.org/665182
ok 3 /ssl/message-properties/async
# Bug Reference: https://bugzilla.gnome.org/665182
ok 4 /ssl/message-properties/sync
# End of message-properties tests
# Start of strictness tests
# Start of async tests
# Start of strict tests
# GLib-GIO-DEBUG: GSocketClient: Starting new address enumeration
# GLib-GIO-DEBUG: GSocketClient: Address enumeration succeeded
# GLib-GIO-DEBUG: GSocketClient: Starting TCP connection attempt
# GLib-GIO-DEBUG: GSocketClient: TCP connection successful
# GLib-GIO-DEBUG: GSocketClient: Starting application layer connection
# GLib-GIO-DEBUG: GSocketClient: Connection successful!
# Bug Reference: https://bugzilla.gnome.org/690176
# Bug Reference: https://bugzilla.gnome.org/665182
ok 5 /ssl/strictness/async/strict/with-ca
# GLib-GIO-DEBUG: GSocketClient: Starting new address enumeration
# GLib-GIO-DEBUG: GSocketClient: Address enumeration succeeded
# GLib-GIO-DEBUG: GSocketClient: Starting TCP connection attempt
# GLib-GIO-DEBUG: GSocketClient: TCP connection successful
# GLib-GIO-DEBUG: GSocketClient: Starting application layer connection
# GLib-GIO-DEBUG: GSocketClient: Connection successful!
**
ERROR:../tests/ssl-test.c:115:do_strictness_test: Unexpected status 200
OK (expected 6 SSL handshake failed)
# ERROR:../tests/ssl-test.c:115:do_strictness_test: Unexpected status
200 OK (expected 6 SSL handshake failed)
# Bug Reference: https://bugzilla.gnome.org/690176
# Bug Reference: https://bugzilla.gnome.org/665182
not ok 6 /ssl/strictness/async/strict/without-ca
# End of strict tests
# Start of non-strict tests
# GLib-GIO-DEBUG: GSocketClient: Starting new address enumeration
# GLib-GIO-DEBUG: GSocketClient: Address enumeration succeeded
# GLib-GIO-DEBUG: GSocketClient: Starting TCP connection attempt
# GLib-GIO-DEBUG: GSocketClient: TCP connection successful
# GLib-GIO-DEBUG: GSocketClient: Starting application layer connection
# GLib-GIO-DEBUG: GSocketClient: Connection successful!
# Bug Reference: https://bugzilla.gnome.org/690176
# Bug Reference: https://bugzilla.gnome.org/665182
ok 7 /ssl/strictness/async/non-strict/with-ca
# GLib-GIO-DEBUG: GSocketClient: Starting new address enumeration
# GLib-GIO-DEBUG: GSocketClient: Address enumeration succeeded
# GLib-GIO-DEBUG: GSocketClient: Starting TCP connection attempt
# GLib-GIO-DEBUG: GSocketClient: TCP connection successful
# GLib-GIO-DEBUG: GSocketClient: Starting application layer connection
# GLib-GIO-DEBUG: GSocketClient: 

Processed: glib-networking breaks libsoup2.4 autopkgtest: libsoup-2.4/ssl-test.test (Child process killed by signal 5)

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> found -1 glib-networking/2.66.0-1
Bug #970935 [src:glib-networking, src:libsoup2.4] glib-networking breaks 
libsoup2.4 autopkgtest: libsoup-2.4/ssl-test.test (Child process killed by 
signal 5)
Marked as found in versions glib-networking/2.66.0-1.
> found -1 libsoup2.4/2.70.0-1
Bug #970935 [src:glib-networking, src:libsoup2.4] glib-networking breaks 
libsoup2.4 autopkgtest: libsoup-2.4/ssl-test.test (Child process killed by 
signal 5)
Marked as found in versions libsoup2.4/2.70.0-1.

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



Bug#933113: marked as done (libcgi-application-plugin-authorization-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 19:48:23 +
with message-id 
and subject line Bug#933113: fixed in 
libcgi-application-plugin-authorization-perl 0.07+~cs0.1-1
has caused the Debian Bug report #933113,
regarding libcgi-application-plugin-authorization-perl: build-depends on 
pkg-components that won't be in Bullseye unless it finds a new upstream 
maintainer
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.)


-- 
933113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgi-application-plugin-authorization-perl
Severity: important
User: debian-p...@lists.debian.org
Usertags: pkg-components-removal

Hi,

libcgi-application-plugin-authorization-perl build-depends on
pkg-components. The Debian Perl group has decided today that we don't
want pkg-components to be included in the Bullseye release, unless
someone steps up and volunteers to be its upstream maintainer:
https://bugs.debian.org/933110

If libcgi-application-plugin-authorization-perl is suitable for
Bullseye, please either port
libcgi-application-plugin-authorization-perl away from pkg-components
or consider taking over its maintenance upstream.

Thanks in advance!

Cheers, 
-- 
intrigeri, for the Debian Perl group
--- End Message ---
--- Begin Message ---
Source: libcgi-application-plugin-authorization-perl
Source-Version: 0.07+~cs0.1-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcgi-application-plugin-authorization-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 21:23:19 +0200
Source: libcgi-application-plugin-authorization-perl
Architecture: source
Version: 0.07+~cs0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 933113
Changes:
 libcgi-application-plugin-authorization-perl (0.07+~cs0.1-1) unstable; 
urgency=medium
 .
   [ gregor herrmann ]
   * Remove Jaldhar H. Vyas from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
   * Remove pkg-component framework. (Closes: #933113)
   * Update debian/watch to use multi upstream tarball feature.
   * debian/rules: adjust to run dh_auto_* also for subcomponent.
   * Add debian/gbp.conf to tell gbp about the new component.
 .
   * Import "upstream" version 0.07+~cs0.1.
   * Add /me to Uploaders.
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Drop unneeded version constraints from (build) dependencies, and
 ancient Breaks/Replaces.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
Checksums-Sha1:
 f4f60f9cd8240d413092cee336b95c9dc4535faa 3550 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1-1.dsc
 685ff1df9dbcb39e15fca266e1c87a946114091a 9639 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1.orig-driver-ad.tar.gz
 b7be2443889036c132af8dfc7abe7111bacbe0fe 20810 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1.orig.tar.gz
 125d4fc025db8def06550a5337962f4fcb960dbb 4296 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1-1.debian.tar.xz
Checksums-Sha256:
 5e4dc939de1802e2004deac1c0ce50f21a818832ed867e83ebec7399191a3257 3550 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1-1.dsc
 8ade3754e635a3b16fd9cc965c9a8c810f977bb698af7ba77b955fe754e7a7c1 9639 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1.orig-driver-ad.tar.gz
 607864011f2000c8db20789e720cb6b129fe26cabb4008e40dffac1977bf5a87 20810 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1.orig.tar.gz
 569c364ed4cbb7387be8576c08170b9ae23868e019211b4c685cb3b07eab837e 4296 
libcgi-application-plugin-authorization-perl_0.07+~cs0.1-1.debian.tar.xz
Files:
 735e2893a129b00296c515239c7003f7 3550 perl 

Processed: Bug#933113 marked as pending in libcgi-application-plugin-authorization-perl

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933113 [libcgi-application-plugin-authorization-perl] 
libcgi-application-plugin-authorization-perl: build-depends on pkg-components 
that won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) pending.

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



Bug#970933: geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 3.38.0

2020-09-25 Thread Paul Gevers
Source: geary
Version: 3.38.0.1-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
geary  from testing3.38.0.1-3
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? By the way, geary also
FTBFS on s390x.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/geary/7180319/log.gz

autopkgtest [06:10:02]: test version: [---
Expected: geary: 3.38.0.1
 Got: geary: 3.38.0
autopkgtest [06:10:03]: test version: ---]



signature.asc
Description: OpenPGP digital signature


Bug#933113: marked as pending in libcgi-application-plugin-authorization-perl

2020-09-25 Thread gregor herrmann
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-authorization-perl/-/commit/aa19498d3bb46bf48b54c29eaccae32de459cf87


Remove pkg-component framework.

Closes: #933113


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933113



Processed: Re: Processed (with 1 error): bts gets a bit confused

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # oops
> reassign 968629 src:ruby-rspec 3.9.0c1e0m1s2-1
Bug #968629 {Done: Antonio Terceiro } [src:ruby-diff-lcs, 
src:ruby-rspec] ruby-diff-lcs breaks ruby-rspec autopkgtest: loads of deltas
Bug reassigned from package 'src:ruby-diff-lcs, src:ruby-rspec' to 
'src:ruby-rspec'.
No longer marked as found in versions ruby-rspec/3.9.0c1e0m1s2-1 and 
ruby-diff-lcs/1.4.4-1.
No longer marked as fixed in versions ruby-diff-lcs/3.9.0c2e2m1s3-1 and 
ruby-rspec/3.9.0c2e2m1s3-1.
Bug #968629 {Done: Antonio Terceiro } [src:ruby-rspec] 
ruby-diff-lcs breaks ruby-rspec autopkgtest: loads of deltas
Marked as found in versions ruby-rspec/3.9.0c1e0m1s2-1.
> fixed 968629 3.9.0c2e2m1s3-1
Bug #968629 {Done: Antonio Terceiro } [src:ruby-rspec] 
ruby-diff-lcs breaks ruby-rspec autopkgtest: loads of deltas
Marked as fixed in versions ruby-rspec/3.9.0c2e2m1s3-1.
> thanks
Stopping processing here.

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



Bug#970762: in package pciutils marked as pending

2020-09-25 Thread Daniel Leidert
Control: reopen 970762

Am Mittwoch, den 23.09.2020, 03:13 +0200 schrieb Guillem Jover:

[..]
> ---
> commit c2c28549a513b93898d8c49f6eb8cefc1670a1e2
> Author: Guillem Jover 
> Date:   Wed Sep 23 03:00:35 2020 +0200
> 
> Force the hardlink for the backup pci.ids database in update-pciids
> 
> Closes: #970762, #970762

This patch only fixes the creation of the hardlink of pci.ids.gz.old ->
pci.ids.gz, which btw seems really odd to me (why do we need this link?
shouldn't .old be or at least link to the previous database?).

However /usr/share/misc/pci.ids is still deleted and breaks virt-manager.

I was checking the script and it seems it fails somwhere at lines 52-60. If I
print out the commands it looks like this:

> + DECOMP=cat
> + SRC=https://pci-ids.ucw.cz/v2.2/pci.ids.gz
> + GREP=zgrep
> + which curl
> + DL=curl -o /usr/share/misc/pci.ids.gz.new 
> https://pci-ids.ucw.cz/v2.2/pci.ids.gz
> + false
> + curl -o /usr/share/misc/pci.ids.gz.new 
> https://pci-ids.ucw.cz/v2.2/pci.ids.gz
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  278k  100  278k0 0   814k  0 --:--:-- --:--:-- --:--:--  814k
> + cat
> + 
> + zgrep ^C  /usr/share/misc/pci.ids.gz.neww
> sh: 0: getcwd() failed: No such file or directory
> + [ -f /usr/share/misc/pci.ids.gz ]
> + ln -f /usr/share/misc/pci.ids.gz /usr/share/misc/pci.ids.gz.old
> + chmod -f --reference=/usr/share/misc/pci.ids.gz.old 
> /usr/share/misc/pci.ids.gz.neww
> + mv /usr/share/misc/pci.ids.gz.neww /usr/share/misc/pci.ids.gz
> + rm /usr/share/misc/pci.ids.gz.new
> + [ /usr/share/misc/pci.ids != /usr/share/misc/pci.ids.gz ]
> + rm -f /usr/share/misc/pci.ids /usr/share/misc/pci.ids.old
> + false
> + echo Done.

Note the getcwd() failure.

Reopening report.

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


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


Processed: Re: Bug#970762: in package pciutils marked as pending

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> reopen 970762
Bug #970762 {Done: Guillem Jover } [pciutils] virt-manger 
fails to open vm console/info with: Error launching details: g-io-error-quark: 
Error opening file /usr/share/misc/pci.ids: No such file or directory
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pciutils/1:3.7.0-3.

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



Bug#966985: Bug#970410: src:html5lib: fails to migrate to testing for too long: autopkgtest regressions

2020-09-25 Thread Paul Gevers
Hi Sandro,

On 24-09-2020 17:21, Sandro Tosi wrote:
>> Thank you for the recent upload. Unfortunately, your package still can't
>> migrate because it causes a FTBFS/autopkgtest regression in
>> python-bleach (hence in CC).
>>
>>> 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.
>>
>> Both packages are key packages [1], so will not be removed
>> automatically. Please align how to fix the situation.
> 
> bleach needs to be upgraded to 3.2.1

But is it possible that this new version of bleach must have a versioned
dependency on html5lib? I see multiple regressions that all look the
same (with the old html5lib, which is the one in testing):
cannot import name 'attributeMap' from 'html5lib._tokenizer'

Paul



signature.asc
Description: OpenPGP digital signature


Bug#970921: marked as done (error: PyCapsule_GetPointer called with incorrect name)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 18:03:31 +
with message-id 
and subject line Bug#970921: fixed in calibre 5.0.1+dfsg-1
has caused the Debian Bug report #970921,
regarding error: PyCapsule_GetPointer called with incorrect name
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.)


-- 
970921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calibre
Version: 4.99.12+dfsg+really4.23.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

calibre fails to start with this error:
```
Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 529, in main
app, opts, args = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 114, in init_qt
app = Application(args, override_program_name=override, 
windows_app_uid=MAIN_APP_UID)
  File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__
raise RuntimeError('Failed to load the progress_indicator C extension, with 
error: {}'.format(pi_err))
RuntimeError: Failed to load the progress_indicator C extension, with error: 
PyCapsule_GetPointer called with incorrect name
```



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

Versions of packages calibre depends on:
ii  calibre-bin  4.99.12+dfsg+really4.23.0-1
ii  dpkg 1.20.5
ii  fonts-liberation 1:1.07.4-11
ii  imagemagick  8:6.9.11.24+dfsg-1+b1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.24+dfsg-1+b1
ii  libjpeg-turbo-progs  1:2.0.5-1.1
ii  libjxr-tools 1.1-6+b1
ii  optipng  0.7.7-1+b1
ii  poppler-utils20.09.0-2
ii  python3  3.8.2-3
ii  python3-apsw 3.32.2-r1-1
ii  python3-bs4  4.9.1-1
ii  python3-chardet  3.0.4-7
ii  python3-chm  0.8.6-2+b1
ii  python3-css-parser   1.0.4-2
ii  python3-cssselect1.1.0-2
ii  python3-cssutils 1.0.2-3
ii  python3-dateutil 2.8.1-4
ii  python3-dbus 1.2.16-3
ii  python3-feedparser   5.2.1-2
ii  python3-html2text2020.1.16-1
ii  python3-html5-parser 0.4.9-3+b1
ii  python3-html5lib 1.1-2
ii  python3-lxml 4.5.2-1
ii  python3-markdown 3.2.2-2
ii  python3-mechanize1:0.4.5-2
ii  python3-msgpack  0.6.2-1+b1
ii  python3-netifaces0.10.9-0.2+b1
ii  python3-pil  7.2.0-1
ii  python3-pkg-resources49.3.1-2
ii  python3-pygments 2.3.1+dfsg-4
ii  python3-pyparsing2.4.7-1
ii  python3-pyqt55.15.1+dfsg-2
ii  python3-pyqt5.qtsvg  5.15.1+dfsg-2
ii  python3-pyqt5.qtwebengine5.15.1-1
ii  python3-regex0.1.20200714-1
ii  python3-routes   2.4.1-2
ii  python3-zeroconf 0.26.1-1
ii  xdg-utils1.1.3-2

Versions of packages calibre recommends:
ii  python3-dnspython  2.0.0-1
ii  udisks22.9.1-2

Versions of packages calibre suggests:
pn  python3-openssl   
pn  python3-unrardll  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: calibre
Source-Version: 5.0.1+dfsg-1
Done: YOKOTA Hiroshi 

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

Debian distribution 

Processed (with 1 error): bts gets a bit confused

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassing 968629 src:ruby-rspec 3.9.0c1e0m1s2-1
Unknown command or malformed arguments to command.
> affects 968629 ruby-diff-lcs
Bug #968629 {Done: Antonio Terceiro } [src:ruby-diff-lcs, 
src:ruby-rspec] ruby-diff-lcs breaks ruby-rspec autopkgtest: loads of deltas
Added indication that 968629 affects ruby-diff-lcs
> fixed 968629 3.9.0c2e2m1s3-1
Bug #968629 {Done: Antonio Terceiro } [src:ruby-diff-lcs, 
src:ruby-rspec] ruby-diff-lcs breaks ruby-rspec autopkgtest: loads of deltas
The source 'ruby-diff-lcs' and version '3.9.0c2e2m1s3-1' do not appear to match 
any binary packages
Marked as fixed in versions ruby-diff-lcs/3.9.0c2e2m1s3-1.
> thanks
Stopping processing here.

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



Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

2020-09-25 Thread Michel Le Bihan
Hello,

Indeed I had a copy in /usr/local/ that I don't remember installing.
Sorry for this bug report.

Michel Le Bihan

Le vendredi 25 septembre 2020 à 13:01 +0100, Simon McVittie a écrit :
> Control: tags -1 + moreinfo unreproducible
> 
> On Fri, 25 Sep 2020 at 13:02:20 +0200, Michel Le Bihan wrote:
> > When trying to launch gnome-screenshot, I get this error:
> > 
> > michel@debian:~$ gnome-screenshot --interactive
> > gnome-screenshot: symbol lookup error: gnome-screenshot: undefined
> > symbol:
> > hdy_init, version LIBHANDY_1_0
> 
> What does
> 
> ldd `command -v gnome-screenshot`
> 
> output?
> 
> Do you have a locally-installed copy of libhandy-1.so.0 that is found
> before the system copy, perhaps in /usr/local? (If you do, please
> remove
> it: Debian package dependencies cannot take locally-installed
> libraries
> into account.)
> 
> > Versions of packages gnome-screenshot depends on:
> ...
> > ii  libhandy-1-0 1.0.0-1
> 
> This should be sufficient to provide hdy_init, version LIBHANDY_1_0.
> 
> smcv



Bug#957590: marked as done (netatalk: ftbfs with GCC-10)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 16:33:46 +
with message-id 
and subject line Bug#957590: fixed in netatalk 3.1.12~ds-5
has caused the Debian Bug report #957590,
regarding netatalk: 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.)


-- 
957590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:netatalk
Version: 3.1.12~ds-4
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/netatalk_3.1.12~ds-4_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

[...]
gcc -DHAVE_CONFIG_H -I. -I../..   -I../../include -I../../include -I../.. 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DAPPLCNAME 
-DSERVERTEXT=\"/var/lib/netatalk/msg/\" 
-D_PATH_AFPDPWFILE=\"/etc/netatalk/afppasswd\" 
-D_PATH_AFPDUAMPATH=\"/usr/lib/netatalk//\" -D_PATH_CONFDIR=\"/etc/netatalk/\" 
-D_PATH_STATEDIR='"/var/lib/netatalk/"' -pthread -I/usr/include/tracker-2.0 
-I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDBUS_COMPILATION 
-D_U_="__attribute__((unused))" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o afpd-afpstats.o 
`test -f
  'afpstats.c' || echo './'`afpstats.c
afpstats.c: In function ‘afpstats_init’:
afpstats.c:114:5: warning: ‘g_type_init’ is deprecated 
[-Wdeprecated-declarations]
  114 | g_type_init();
  | ^~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/dbus-1.0/dbus/dbus-glib.h:27,
 from afpstats.c:26:
/usr/include/glib-2.0/gobject/gtype.h:691:23: note: declared here
  691 | void  g_type_init(void);
  |   ^~~
afpstats.c:115:5: warning: ‘g_thread_init’ is deprecated 
[-Wdeprecated-declarations]
  115 | g_thread_init(NULL);
  | ^
In file included from /usr/include/glib-2.0/glib.h:110,
 from afpstats.c:25:
/usr/include/glib-2.0/glib/deprecated/gthread.h:261:10: note: declared here
  261 | void g_thread_init   (gpointer vtable);
  |  ^
afpstats.c:119:5: warning: ‘g_thread_create’ is deprecated: Use 'g_thread_new' 
instead [-Wdeprecated-declarations]
  119 | thread = g_thread_create(afpstats_thread, NULL, TRUE, NULL);
  | ^~
In file included from /usr/include/glib-2.0/glib.h:110,
 from afpstats.c:25:
/usr/include/glib-2.0/glib/deprecated/gthread.h:100:10: note: declared here
  100 | GThread *g_thread_create   (GThreadFunc   func,
  |  ^~~
gcc -DHAVE_CONFIG_H -I. -I../..   -I../../include -I../../include -I../.. 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DAPPLCNAME 
-DSERVERTEXT=\"/var/lib/netatalk/msg/\" 
-D_PATH_AFPDPWFILE=\"/etc/netatalk/afppasswd\" 
-D_PATH_AFPDUAMPATH=\"/usr/lib/netatalk//\" -D_PATH_CONFDIR=\"/etc/netatalk/\" 

Bug#958616: marked as done (netatalk: Build-Depends on deprecated dh-systemd which is going away)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 16:33:46 +
with message-id 
and subject line Bug#958616: fixed in netatalk 3.1.12~ds-5
has caused the Debian Bug report #958616,
regarding netatalk: Build-Depends on deprecated dh-systemd which is going away
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.)


-- 
958616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netatalk
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal

Hi,

your package netatalk declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.

For bullseye we intend to drop this empty transitional package.

Once we drop dh-systemd, this bug report will become RC.

Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: netatalk
Source-Version: 3.1.12~ds-5
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated netatalk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 18:06:13 +0200
Source: netatalk
Architecture: source
Version: 3.1.12~ds-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Netatalk team 
Changed-By: Jonas Smedegaard 
Closes: 957590 958616
Changes:
 netatalk (3.1.12~ds-5) unstable; urgency=medium
 .
   * add patches cherry-picked from upstream merge-requests:
 + fix ftbfs with GCC-10;
   closes: bug#957590, thanks to Matthias Klose
 + fix implicit declarations in become_root() and unbecome_root()
 + fix garbage read in bsd_attr_list()
 + fix use after free in get_tm_used()
 + fix afpd segfault in Spotlight SPARQL parser
   * use debhelper compatibility level 10 (not 9)
   * stop build-depend on dh-systemd
 (provided by debhelper even in oldstable);
 closes: bug#958616, thanks to Michael Biebl
   * annotate superficial autopkgtest
   * unfuzz patch 103
   * enable CNID backend mysql
 (MariaDB avoids OpenSSL since 1:10.3.13-1,
 available since buster);
 build-depend on libmariadb-dev-compat
   * simplify source script copyright-check
Checksums-Sha1:
 fa227bdea459f7883dcca4ace1e6561f7abb9791 2503 netatalk_3.1.12~ds-5.dsc
 ca1d70b3407b3a327b077ef3b6abf2a4f5035836 56684 
netatalk_3.1.12~ds-5.debian.tar.xz
 588911e8ded13ffb35c9fd800cc5dc6eed6fff2c 9858 
netatalk_3.1.12~ds-5_amd64.buildinfo
Checksums-Sha256:
 d1a921a4a1ff365ad493449f97de01df09920520335f69edf2f80ea17495fc18 2503 
netatalk_3.1.12~ds-5.dsc
 e319d6d1b748b6a13aee1ae1b6b414ae09b0bea5610a172019795ae15b03cc1d 56684 
netatalk_3.1.12~ds-5.debian.tar.xz
 15654e123d4440c00ff961efe3b069f2f2e6a1e4b6b6db77dfa657e65dea20f5 9858 
netatalk_3.1.12~ds-5_amd64.buildinfo
Files:
 6adde965730215a1b18efbda3b93f9f8 2503 net optional netatalk_3.1.12~ds-5.dsc
 990f6e853c44ed51e1810e491b78ccf2 56684 net optional 
netatalk_3.1.12~ds-5.debian.tar.xz
 c2b1b16fa5d00848a3a70c74d72e0d9c 9858 net optional 
netatalk_3.1.12~ds-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9uGE8ACgkQLHwxRsGg
ASHsJw//bdMWN8ZIQ1BE9Fmct2HYh4C5jacJIWnakviNhtUVHiMC2uA7yW1nsDuT
BSIalcwR9V7/8L/hW+FznXYu5Fva/sOdPnQyu6YGF5D7eBHOtCfo/df53HJg36B3
yw+1TvChlqQssPLx+37O3rmGBOMJuPHPfDyye8fVpCJpqYSRIa2Bt4E6EDsIh097
SU8LFM5pLx1xBgmwARzKluBgMhdtO6NzyRWtITStD1Vb/KYPk6V/Tf/3GS+htzjQ
XAs018ZuNPZ7+X5atwzFNws8VcavkiVBhbXJP3i3QYN7RA2YpkkzxvT7KMaeUYFD
M4ucKvZ3PvHochF8TfWfFNHMGW/0iTUvcwM+Zs/zrSSb/C5fA9kz5YGB3lZCV452
xc5aIau7Pv7i0CA2jNBqGVsntqsNtii8EpI7ydi9B2YcTZivg/erXybDlMRcDSHk
nyFEMOfUC1SThbjpMjwdzrbp6ufbRZP7yN4ll9mUS/k+51xs6diKCXPbtSAO9x5/

Bug#970921: error: PyCapsule_GetPointer called with incorrect name

2020-09-25 Thread Vincas Dargis
Package: calibre
Version: 4.99.12+dfsg+really4.23.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

calibre fails to start with this error:
```
Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 529, in main
app, opts, args = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 114, in init_qt
app = Application(args, override_program_name=override, 
windows_app_uid=MAIN_APP_UID)
  File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__
raise RuntimeError('Failed to load the progress_indicator C extension, with 
error: {}'.format(pi_err))
RuntimeError: Failed to load the progress_indicator C extension, with error: 
PyCapsule_GetPointer called with incorrect name
```



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

Versions of packages calibre depends on:
ii  calibre-bin  4.99.12+dfsg+really4.23.0-1
ii  dpkg 1.20.5
ii  fonts-liberation 1:1.07.4-11
ii  imagemagick  8:6.9.11.24+dfsg-1+b1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.24+dfsg-1+b1
ii  libjpeg-turbo-progs  1:2.0.5-1.1
ii  libjxr-tools 1.1-6+b1
ii  optipng  0.7.7-1+b1
ii  poppler-utils20.09.0-2
ii  python3  3.8.2-3
ii  python3-apsw 3.32.2-r1-1
ii  python3-bs4  4.9.1-1
ii  python3-chardet  3.0.4-7
ii  python3-chm  0.8.6-2+b1
ii  python3-css-parser   1.0.4-2
ii  python3-cssselect1.1.0-2
ii  python3-cssutils 1.0.2-3
ii  python3-dateutil 2.8.1-4
ii  python3-dbus 1.2.16-3
ii  python3-feedparser   5.2.1-2
ii  python3-html2text2020.1.16-1
ii  python3-html5-parser 0.4.9-3+b1
ii  python3-html5lib 1.1-2
ii  python3-lxml 4.5.2-1
ii  python3-markdown 3.2.2-2
ii  python3-mechanize1:0.4.5-2
ii  python3-msgpack  0.6.2-1+b1
ii  python3-netifaces0.10.9-0.2+b1
ii  python3-pil  7.2.0-1
ii  python3-pkg-resources49.3.1-2
ii  python3-pygments 2.3.1+dfsg-4
ii  python3-pyparsing2.4.7-1
ii  python3-pyqt55.15.1+dfsg-2
ii  python3-pyqt5.qtsvg  5.15.1+dfsg-2
ii  python3-pyqt5.qtwebengine5.15.1-1
ii  python3-regex0.1.20200714-1
ii  python3-routes   2.4.1-2
ii  python3-zeroconf 0.26.1-1
ii  xdg-utils1.1.3-2

Versions of packages calibre recommends:
ii  python3-dnspython  2.0.0-1
ii  udisks22.9.1-2

Versions of packages calibre suggests:
pn  python3-openssl   
pn  python3-unrardll  

-- no debconf information



Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

2020-09-25 Thread Michel Le Bihan
Package: gnome-screenshot
Version: 3.38.0-1
Severity: grave
Justification: renders package unusable

Hello,

When trying to launch gnome-screenshot, I get this error:

michel@debian:~$ gnome-screenshot --interactive
gnome-screenshot: symbol lookup error: gnome-screenshot: undefined symbol:
hdy_init, version LIBHANDY_1_0



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

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

Versions of packages gnome-screenshot depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.0-2
ii  libgtk-3-0   3.24.23-1
ii  libhandy-1-0 1.0.0-1
ii  libx11-6 2:1.6.12-1
ii  libxext6 2:1.3.3-1+b2

gnome-screenshot recommends no packages.

gnome-screenshot suggests no packages.

-- no debconf information



Bug#970910: marked as done (node-rollup-plugin-babel: autopkgtest failures [PATCH])

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 16:25:18 +0200
with message-id <34fc1066-fe13-a95f-3921-4257ffa2f...@debian.org>
and subject line Re: [Pkg-javascript-devel] Bug#970910: Bug#970910: 
node-rollup-plugin-babel: autopkgtest failures [PATCH]
has caused the Debian Bug report #970910,
regarding node-rollup-plugin-babel: autopkgtest failures [PATCH]
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.)


-- 
970910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-babel
Version: 5.2.1+~4.4.0-2
Severity: serious
tags: patch

Hello, looks like the autopkgtestsuite fails because of 
autopkgtest [08:35:49]: test pkg-js-autopkgtest: 
/usr/share/pkg-js-autopkgtest/runner
autopkgtest [08:35:49]: test pkg-js-autopkgtest: [---
Found debian/nodejs/main, package.json is packages/babel/package.json
Using packages/babel/package.json
Node module name is @rollup/plugin-babel
# Copy test files
Looking at /usr/lib/nodejs/@rollup/plugin-babel
Looking at /usr/lib/*/nodejs/@rollup/plugin-babel
Looking at /usr/share/nodejs/@rollup/plugin-babel
Found /usr/share/nodejs/@rollup/plugin-babel
Linking /usr/share/nodejs/@rollup/plugin-babel/dist
Linking /usr/share/nodejs/@rollup/plugin-babel/package.json
Linking /usr/share/nodejs/@rollup/plugin-babel/types
Launch debian/tests/pkg-js/test with sh -ex
+ cd packages/babel
+ tape test/as-input-plugin.js test/as-output-plugin.js
debian/tests/pkg-js/test: 2: tape: not found
autopkgtest [08:35:49]: test pkg-js-autopkgtest: ---]
autopkgtest [08:35:50]: test pkg-js-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -


Adding node-tape to build-dependencies might fix the issue.

thanks for having a look,

G.
--- End Message ---
--- Begin Message ---
Le 25/09/2020 à 15:33, Xavier a écrit :
> Control: tags + moreinfo
> 
> Le 25/09/2020 à 12:42, Gianfranco Costamagna a écrit :
>> Source: node-rollup-plugin-babel
>> Version: 5.2.1+~4.4.0-2
>> Severity: serious
>> tags: patch
>>
>> Hello, looks like the autopkgtestsuite fails because of 
>> autopkgtest [08:35:49]: test pkg-js-autopkgtest: 
>> /usr/share/pkg-js-autopkgtest/runner
>> autopkgtest [08:35:49]: test pkg-js-autopkgtest: [---
>> Found debian/nodejs/main, package.json is packages/babel/package.json
>> Using packages/babel/package.json
>> Node module name is @rollup/plugin-babel
>> # Copy test files
>> Looking at /usr/lib/nodejs/@rollup/plugin-babel
>> Looking at /usr/lib/*/nodejs/@rollup/plugin-babel
>> Looking at /usr/share/nodejs/@rollup/plugin-babel
>> Found /usr/share/nodejs/@rollup/plugin-babel
>> Linking /usr/share/nodejs/@rollup/plugin-babel/dist
>> Linking /usr/share/nodejs/@rollup/plugin-babel/package.json
>> Linking /usr/share/nodejs/@rollup/plugin-babel/types
>> Launch debian/tests/pkg-js/test with sh -ex
>> + cd packages/babel
>> + tape test/as-input-plugin.js test/as-output-plugin.js
>> debian/tests/pkg-js/test: 2: tape: not found
>> autopkgtest [08:35:49]: test pkg-js-autopkgtest: ---]
>> autopkgtest [08:35:50]: test pkg-js-autopkgtest:  - - - - - - - - - - 
>> results - - - - - - - - - -
>>
>>
>> Adding node-tape to build-dependencies might fix the issue.
>>
>> thanks for having a look,
>>
>> G.
> 
> Hi,
> 
> debian/tests/autopkgtest-pkg-nodejs.conf contains
> 
>   "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"
> 
> which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
> this bug should be reassigned to autodep8.
> 
> Cheers,
> Xavier

After new tests (schroot and lxc), autodep8 gives the good test
dependencies to node-rollup-plugin-babel, so it's not
node-rollup-plugin-babel/Debian issue:

$ autodep8
Test-Command: cd legacy && sh -ex ../debian/nodejs/legacy/test
Depends: @, @builddeps@, mocha, node-rollup-plugin-json
Features: test-name=legacy-test
Restrictions: allow-stderr

extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)
Test-Command: /usr/share/pkg-js-autopkgtest/runner require
Depends: @, nodejs, pkg-js-autopkgtest, mocha, node-tape,
 node-rollup-plugin-json (>= 4.1.0)
Restrictions: superficial, skippable,
Features: test-name=pkg-js-autopkgtest-require

Test-Command: /usr/share/pkg-js-autopkgtest/runner
Depends: @, @builddeps@, pkg-js-autopkgtest, mocha, node-tape,
 node-rollup-plugin-json (>= 4.1.0)
Restrictions: allow-stderr, skippable,
Features: test-name=pkg-js-autopkgtest--- End Message ---


Processed: notfound 970911 in 3.38.0-1

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 970911 3.38.0-1
Bug #970911 {Done: Simon McVittie } [gnome-screenshot] 
gnome-screenshot: does not start: undefined symbol: hdy_init
No longer marked as found in versions gnome-screenshot/3.38.0-1.
> thanks
Stopping processing here.

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



Processed: Re: Bug#970912: Fails to upgrade: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 cowdancer
Bug #970912 [libncurses6] Fails to upgrade: version 
`NCURSES6_TINFO_6.2.current' not found (required by 
/lib/x86_64-linux-gnu/libncurses.so.6)
Bug reassigned from package 'libncurses6' to 'cowdancer'.
No longer marked as found in versions ncurses/6.2+20200918-1.
Ignoring request to alter fixed versions of bug #970912 to the same values 
previously set
> forcemerge 970555 -1
Bug #970555 [cowdancer] cowdancer: needlessly links with ncurses
Bug #970594 [cowdancer] libtinfo6: Error with updating from 6.2-1 to 
6.2+20200912-1
Bug #970688 [cowdancer] rm: /lib/i386-linux-gnu/libtinfo.so.6: version 
`NCURSES6_TINFO_6.2.current' not found (required by 
/lib/i386-linux-gnu/libncurses.so.6)
Bug #970912 [cowdancer] Fails to upgrade: version `NCURSES6_TINFO_6.2.current' 
not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Severity set to 'important' from 'serious'
Marked as found in versions cowdancer/0.88.
Bug #970594 [cowdancer] libtinfo6: Error with updating from 6.2-1 to 
6.2+20200912-1
Bug #970688 [cowdancer] rm: /lib/i386-linux-gnu/libtinfo.so.6: version 
`NCURSES6_TINFO_6.2.current' not found (required by 
/lib/i386-linux-gnu/libncurses.so.6)
Merged 970555 970594 970688 970912

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



Bug#970912: Fails to upgrade: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)

2020-09-25 Thread Sven Joachim
Control: reassign -1 cowdancer
Control: forcemerge 970555 -1

On 2020-09-25 13:28 +0200, Michael Biebl wrote:

> Package: libncurses6
> Version: 6.2+20200918-1
> Severity: serious
>
> Today I tried to upgrade my cowbuilder chroots.
> This failed with the following error message:
>
> Preparing to unpack .../libncurses6_6.2+20200918-1_amd64.deb ...
> Unpacking libncurses6:amd64 (6.2+20200918-1) over (6.2-1) ...
> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' 
> not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
> dpkg: error while cleaning up:
>  rm command for cleanup subprocess returned error exit status 1
> dpkg-split: /lib/x86_64-linux-gnu/libtinfo.so.6: version 
> `NCURSES6_TINFO_6.2.current' not found (required by 
> /lib/x86_64-linux-gnu/libncurses.so.6)
> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' 
> not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
> dpkg: error processing archive 
> /var/cache/apt/archives/libtinfo6_6.2+20200918-1_amd64.deb (--unpack):
>  rm command for cleanup subprocess returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/libtinfo6_6.2+20200918-1_amd64.deb

Use the --no-cowdancer-update cowbuilder option to work around this, see
#970555 for details.

Cheers,
   Sven



Bug#970768: torbrowser-launcher: error while checking version number after TorBrowser 10.0 release

2020-09-25 Thread Roger Shimizu
On Thu, Sep 24, 2020 at 1:49 PM Lev Lamberov  wrote:
>
> I've installed torbrowser-launcher from experimental and can confirm
> that it works properly for me. Thanks for you work on it!

Dear Lev,

Thanks for your confirmation!
I uploaded -14 to unstable and buster-backports.
So for debian it should be OK now.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1



Bug#970911: marked as done (gnome-screenshot: does not start: undefined symbol: hdy_init)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 14:57:44 +0100
with message-id <20200925135744.ga4...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#970911: gnome-screenshot: does not start: undefined 
symbol: hdy_init
has caused the Debian Bug report #970911,
regarding gnome-screenshot: does not start: undefined symbol: hdy_init
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.)


-- 
970911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-screenshot
Version: 3.38.0-1
Severity: grave
Justification: renders package unusable

Hello,

When trying to launch gnome-screenshot, I get this error:

michel@debian:~$ gnome-screenshot --interactive
gnome-screenshot: symbol lookup error: gnome-screenshot: undefined symbol:
hdy_init, version LIBHANDY_1_0



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

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

Versions of packages gnome-screenshot depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.0-2
ii  libgtk-3-0   3.24.23-1
ii  libhandy-1-0 1.0.0-1
ii  libx11-6 2:1.6.12-1
ii  libxext6 2:1.3.3-1+b2

gnome-screenshot recommends no packages.

gnome-screenshot suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 25 Sep 2020 at 14:27:41 +0200, Michel Le Bihan wrote:
> Le vendredi 25 septembre 2020 à 13:01 +0100, Simon McVittie a écrit :
> > Do you have a locally-installed copy of libhandy-1.so.0 that is found
> > before the system copy, perhaps in /usr/local?
>
> Indeed I had a copy in /usr/local/ that I don't remember installing.

Closing as not-a-bug.

smcv--- End Message ---


Bug#970910: [Pkg-javascript-devel] Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

2020-09-25 Thread Xavier
Control: tags + moreinfo

Le 25/09/2020 à 12:42, Gianfranco Costamagna a écrit :
> Source: node-rollup-plugin-babel
> Version: 5.2.1+~4.4.0-2
> Severity: serious
> tags: patch
> 
> Hello, looks like the autopkgtestsuite fails because of 
> autopkgtest [08:35:49]: test pkg-js-autopkgtest: 
> /usr/share/pkg-js-autopkgtest/runner
> autopkgtest [08:35:49]: test pkg-js-autopkgtest: [---
> Found debian/nodejs/main, package.json is packages/babel/package.json
> Using packages/babel/package.json
> Node module name is @rollup/plugin-babel
> # Copy test files
> Looking at /usr/lib/nodejs/@rollup/plugin-babel
> Looking at /usr/lib/*/nodejs/@rollup/plugin-babel
> Looking at /usr/share/nodejs/@rollup/plugin-babel
> Found /usr/share/nodejs/@rollup/plugin-babel
> Linking /usr/share/nodejs/@rollup/plugin-babel/dist
> Linking /usr/share/nodejs/@rollup/plugin-babel/package.json
> Linking /usr/share/nodejs/@rollup/plugin-babel/types
> Launch debian/tests/pkg-js/test with sh -ex
> + cd packages/babel
> + tape test/as-input-plugin.js test/as-output-plugin.js
> debian/tests/pkg-js/test: 2: tape: not found
> autopkgtest [08:35:49]: test pkg-js-autopkgtest: ---]
> autopkgtest [08:35:50]: test pkg-js-autopkgtest:  - - - - - - - - - - results 
> - - - - - - - - - -
> 
> 
> Adding node-tape to build-dependencies might fix the issue.
> 
> thanks for having a look,
> 
> G.

Hi,

debian/tests/autopkgtest-pkg-nodejs.conf contains

  "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"

which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
this bug should be reassigned to autodep8.

Cheers,
Xavier



Processed: tagging 970910

2020-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 970910 + moreinfo
Bug #970910 [src:node-rollup-plugin-babel] node-rollup-plugin-babel: 
autopkgtest failures [PATCH]
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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



Bug#957807: marked as done (slashem: ftbfs with GCC-10)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 12:48:54 +
with message-id 
and subject line Bug#957807: fixed in slashem 0.0.7E7F3-10
has caused the Debian Bug report #957807,
regarding slashem: 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.)


-- 
957807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:slashem
Version: 0.0.7E7F3-9
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/slashem_0.0.7E7F3-9_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

[...]
../win/proxy/prxyconn.c:221:9: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  221 |   write((int)wfd, buffer, nb);
  | ^
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:179,
 from /usr/include/stdlib.h:394,
 from ../win/proxy/prxyconn.c:5:
../win/proxy/prxyconn.c:223:15: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  223 |  if (FD_ISSET((int)rfd, )) {
  |   ^
../win/proxy/prxyconn.c:223:15: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  223 |  if (FD_ISSET((int)rfd, )) {
  |   ^
../win/proxy/prxyconn.c:224:16: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  224 |  nb = read((int)rfd, buffer, sizeof(buffer));
  |^
../win/proxy/prxyconn.c: In function ‘client_read’:
../win/proxy/prxyconn.c:239:15: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  239 | nb = read((int)handle, buf, len);
  |   ^
../win/proxy/prxyconn.c: In function ‘client_write’:
../win/proxy/prxyconn.c:247:16: warning: cast from pointer to integer of 
different size [-Wpointer-to-int-cast]
  247 | nb = write((int)handle, buf, len);
  |^
../win/proxy/prxyconn.c: In function ‘proxy_connect_file’:
../win/proxy/prxyconn.c:574:49: warning: cast to pointer from integer of 
different size [-Wint-to-pointer-cast]
  574 |  return proxy_init_client_services(client_read, (void *)from_game[0],
  | ^
../win/proxy/prxyconn.c:575:18: warning: cast to pointer from integer of 
different size [-Wint-to-pointer-cast]
  575 |client_write, (void *)to_game[1]);
  |  ^
../win/proxy/prxyconn.c: In function ‘proxy_connect_tcp’:
../win/proxy/prxyconn.c:611:13: warning: implicit declaration of function 
‘inet_addr’ [-Wimplicit-function-declaration]
  611 | iaddr = inet_addr(s);
  | ^
../win/proxy/prxyconn.c:629:52: warning: cast to pointer from integer of 
different size [-Wint-to-pointer-cast]
  629 | return proxy_init_client_services(client_read, (void *)skt,
  |^
../win/proxy/prxyconn.c:630:21: warning: cast to pointer from integer of 
different size [-Wint-to-pointer-cast]
  630 |   client_write, (void *)skt);
  | ^
cc -DDEBIAN_GTK -g -O2 -fomit-frame-pointer -fstack-protector 
--param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o version.o version.c
Loading ...
cc -L/usr/X11R6/lib -Wl,-z,relro -o slashem monst.o objects.o alloc.o allmain.o 
apply.o artifact.o attrib.o ball.o bones.o botl.o cmd.o dbridge.o decl.o 
detect.o dig.o display.o dlb.o do.o 

Bug#970917: vzquota: unusable without kernel support

2020-09-25 Thread Chris Hofstaedtler
Source: vzquota
Version: 3.1-4
Severity: serious

vzquota needs kernel support, specifically the "vz" patches. Debian
hasn't shipped those in a long time. By now it appears upstream
development has moved back behind more closed doors, and it's
unlikely we'll see anything for bullseye.

Continuing shipping vzquota will not help anyone.

See #970916 for the vzctl bug.

Chris



Bug#970916: vzctl: unusable without kernel support

2020-09-25 Thread Chris Hofstaedtler
Source: vzctl
Version: 4.9.4-6
Severity: serious

vzctl needs kernel support, specifically the "vz" patches. Debian
hasn't shipped those in a long time. By now it appears upstream
development has moved back behind more closed doors, and it's
unlikely we'll see anything for bullseye.

Also, IIRC, the RHEL8-based kernel trees would need newer tooling,
not "vzctl". (Which also doesn't seem to be public.)

Continuing shipping vzctl will not help anyone.
I'll also file bugs against the related vzquota, vzstats programs.

Chris



Bug#970915: isakmpd: outdated upstream source unacceptable for distribution

2020-09-25 Thread Chris Hofstaedtler
Source: isakmpd
Version: 20041012-10
Severity: grave

Our isakmpd sources are by now 16 years old. The sources in OpenBSD
have in the meantime seen a number of improvements and security
fixes, plus protocol fixes.

Shipping such an old version with known security problems is a
disgrace to our users.
If we do not want to properly maintain this, lets stop shipping it
at all - we have better IPsec VPN options to choose from.

Chris



Processed: Re: Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

2020-09-25 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #970911 [gnome-screenshot] gnome-screenshot: does not start: undefined 
symbol: hdy_init
Added tag(s) unreproducible and moreinfo.

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



Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

2020-09-25 Thread Simon McVittie
Control: tags -1 + moreinfo unreproducible

On Fri, 25 Sep 2020 at 13:02:20 +0200, Michel Le Bihan wrote:
> When trying to launch gnome-screenshot, I get this error:
> 
> michel@debian:~$ gnome-screenshot --interactive
> gnome-screenshot: symbol lookup error: gnome-screenshot: undefined symbol:
> hdy_init, version LIBHANDY_1_0

What does

ldd `command -v gnome-screenshot`

output?

Do you have a locally-installed copy of libhandy-1.so.0 that is found
before the system copy, perhaps in /usr/local? (If you do, please remove
it: Debian package dependencies cannot take locally-installed libraries
into account.)

> Versions of packages gnome-screenshot depends on:
...
> ii  libhandy-1-0 1.0.0-1

This should be sufficient to provide hdy_init, version LIBHANDY_1_0.

smcv



Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

2020-09-25 Thread Markus Koschany

Am 25.09.20 um 08:17 schrieb Emmanuel Bourg:
[...]
> Hi Paul,
> 
> The version 4.x has been packaged separately as
> libhibernate-validator4-java. libspring-java has been updated to use it
> but not the other reverse dependencies.
> 
> Emmanuel Bourg

Hi,

pdfsam is the only other reverse-dependency. I am currently working on
updating it including the sejda libraries. Why did you upgrade
hibernate-validator to version 5.x when no other package in Debian
requires it? Wouldn't it have been simpler to revert the upgrade instead
of creating a separate hibernate-validator4 package?

Markus



signature.asc
Description: OpenPGP digital signature


Bug#970912: Fails to upgrade: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)

2020-09-25 Thread Michael Biebl
Package: libncurses6
Version: 6.2+20200918-1
Severity: serious

Today I tried to upgrade my cowbuilder chroots.
This failed with the following error message:

The following packages will be upgraded:
  binutils binutils-common binutils-x86-64-linux-gnu bsdutils coreutils cpp 
cpp-10 g++ g++-10 gcc gcc-10 gcc-10-base libasan6
  libatomic1 libbinutils libblkid1 libcc1-0 libctf-nobfd0 libctf0 
libdebconfclient0 libgcc-10-dev libgcc-s1 libgnutls30 libgomp1
  libitm1 liblsan0 libmount1 libncurses6 libncursesw6 libquadmath0 libseccomp2 
libsmartcols1 libstdc++-10-dev libstdc++6
  libsystemd0 libtinfo6 libtsan0 libubsan1 libudev1 libuuid1 linux-libc-dev 
mount ncurses-base ncurses-bin util-linux
45 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 52.4 MB of archives.
After this operation, 300 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian sid/main amd64 bsdutils amd64 1:2.36-3+b1 
[148 kB]
Get:2 http://ftp.de.debian.org/debian sid/main amd64 coreutils amd64 8.32-4+b1 
[2867 kB]
Get:3 http://ftp.de.debian.org/debian sid/main amd64 libncursesw6 amd64 
6.2+20200918-1 [132 kB]
Get:4 http://ftp.de.debian.org/debian sid/main amd64 libncurses6 amd64 
6.2+20200918-1 [102 kB]
Get:5 http://ftp.de.debian.org/debian sid/main amd64 libtinfo6 amd64 
6.2+20200918-1 [340 kB]
Get:6 http://ftp.de.debian.org/debian sid/main amd64 ncurses-bin amd64 
6.2+20200918-1 [427 kB]
Get:7 http://ftp.de.debian.org/debian sid/main amd64 util-linux amd64 2.36-3+b1 
[1136 kB]
Get:8 http://ftp.de.debian.org/debian sid/main amd64 ncurses-base all 
6.2+20200918-1 [270 kB]
Get:9 http://ftp.de.debian.org/debian sid/main amd64 libsystemd0 amd64 246.6-1 
[370 kB]
Get:10 http://ftp.de.debian.org/debian sid/main amd64 mount amd64 2.36-3+b1 
[184 kB]
Get:11 http://ftp.de.debian.org/debian sid/main amd64 libcc1-0 amd64 10.2.0-9 
[39.7 kB]
Get:12 http://ftp.de.debian.org/debian sid/main amd64 libgomp1 amd64 10.2.0-9 
[99.9 kB]
Get:13 http://ftp.de.debian.org/debian sid/main amd64 libitm1 amd64 10.2.0-9 
[25.8 kB]
Get:14 http://ftp.de.debian.org/debian sid/main amd64 libatomic1 amd64 10.2.0-9 
[9004 B]
Get:15 http://ftp.de.debian.org/debian sid/main amd64 libasan6 amd64 10.2.0-9 
[340 kB]
Get:16 http://ftp.de.debian.org/debian sid/main amd64 liblsan0 amd64 10.2.0-9 
[141 kB]
Get:17 http://ftp.de.debian.org/debian sid/main amd64 libtsan0 amd64 10.2.0-9 
[313 kB]
Get:18 http://ftp.de.debian.org/debian sid/main amd64 libubsan1 amd64 10.2.0-9 
[134 kB]
Get:19 http://ftp.de.debian.org/debian sid/main amd64 libquadmath0 amd64 
10.2.0-9 [145 kB]
Get:20 http://ftp.de.debian.org/debian sid/main amd64 gcc-10-base amd64 
10.2.0-9 [199 kB]
Get:21 http://ftp.de.debian.org/debian sid/main amd64 libstdc++6 amd64 10.2.0-9 
[492 kB]
Get:22 http://ftp.de.debian.org/debian sid/main amd64 g++-10 amd64 10.2.0-9 
[8664 kB]
Get:23 http://ftp.de.debian.org/debian sid/main amd64 libstdc++-10-dev amd64 
10.2.0-9 [1737 kB]
Get:24 http://ftp.de.debian.org/debian sid/main amd64 libgcc-10-dev amd64 
10.2.0-9 [2330 kB]
Get:25 http://ftp.de.debian.org/debian sid/main amd64 gcc-10 amd64 10.2.0-9 
[15.9 MB]
Get:26 http://ftp.de.debian.org/debian sid/main amd64 cpp-10 amd64 10.2.0-9 
[8005 kB]
Get:27 http://ftp.de.debian.org/debian sid/main amd64 libgcc-s1 amd64 10.2.0-9 
[41.3 kB]
Get:28 http://ftp.de.debian.org/debian sid/main amd64 libctf0 amd64 2.35.1-1 
[46.4 kB]
Get:29 http://ftp.de.debian.org/debian sid/main amd64 libctf-nobfd0 amd64 
2.35.1-1 [102 kB]
Get:30 http://ftp.de.debian.org/debian sid/main amd64 libbinutils amd64 
2.35.1-1 [475 kB]
Get:31 http://ftp.de.debian.org/debian sid/main amd64 binutils-common amd64 
2.35.1-1 [2214 kB]
Get:32 http://ftp.de.debian.org/debian sid/main amd64 binutils amd64 2.35.1-1 
[59.7 kB]
Get:33 http://ftp.de.debian.org/debian sid/main amd64 binutils-x86-64-linux-gnu 
amd64 2.35.1-1 [1618 kB]
Get:34 http://ftp.de.debian.org/debian sid/main amd64 libblkid1 amd64 2.36-3+b1 
[195 kB]
Get:35 http://ftp.de.debian.org/debian sid/main amd64 libdebconfclient0 amd64 
0.254 [49.4 kB]
Get:36 http://ftp.de.debian.org/debian sid/main amd64 libgnutls30 amd64 
3.6.15-4 [1189 kB]
Get:37 http://ftp.de.debian.org/debian sid/main amd64 libmount1 amd64 2.36-3+b1 
[212 kB]
Get:38 http://ftp.de.debian.org/debian sid/main amd64 libseccomp2 amd64 2.4.4-1 
[45.2 kB]
Get:39 http://ftp.de.debian.org/debian sid/main amd64 libsmartcols1 amd64 
2.36-3+b1 [158 kB]
Get:40 http://ftp.de.debian.org/debian sid/main amd64 libudev1 amd64 246.6-1 
[162 kB]
Get:41 http://ftp.de.debian.org/debian sid/main amd64 libuuid1 amd64 2.36-3+b1 
[82.7 kB]
Get:42 http://ftp.de.debian.org/debian sid/main amd64 g++ amd64 4:10.2.0-1 
[1644 B]
Get:43 http://ftp.de.debian.org/debian sid/main amd64 gcc amd64 4:10.2.0-1 
[5196 B]
Get:44 http://ftp.de.debian.org/debian sid/main amd64 cpp amd64 4:10.2.0-1 
[19.7 kB]
Get:45 http://ftp.de.debian.org/debian sid/main amd64 linux-libc-dev amd64 
5.8.10-1 [1182 kB]
Fetched 52.4 MB in 0s (124 MB/s)
debconf: 

Bug#968193: marked as done (dh-python autopkg tests fail)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 11:03:28 +
with message-id 
and subject line Bug#968193: fixed in dh-python 4.20200925
has caused the Debian Bug report #968193,
regarding dh-python autopkg tests fail
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.)


-- 
968193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dh-python
Version: 4.20200804
Severity: serious
Tags: sid bullseye patch

The dh-python autopkg tests fail, still needing the unversioned python binary.
Please adjust those, or disable those as done already by Stefano.

patch at
https://patches.ubuntu.com/d/dh-python/dh-python_4.20200804ubuntu1.patch
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 4.20200925
Done: =?utf-8?q?Piotr_O=C5=BCarowski?= 

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated dh-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 12:35:52 +0200
Source: dh-python
Architecture: source
Version: 4.20200925
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Closes: 968046 968193
Changes:
 dh-python (4.20200925) unstable; urgency=medium
 .
   * Add Breaks/Replaces python2 to ease upgrades with python2 (closes: 968046)
   * Disable Python 2.X tests by default (closes: 968193)
Checksums-Sha1:
 51f20bbd7436860e9570e632198551a48c63a9ff 1888 dh-python_4.20200925.dsc
 34ed20cee0ed35085ce055ba2326dcafc25b1331 95148 dh-python_4.20200925.tar.xz
 c9f84a3a2093533c2a7975e745a5f7feae5914d7 6241 
dh-python_4.20200925_amd64.buildinfo
Checksums-Sha256:
 324de47babc9241e35bae2cff6593e9f3a01beb3a21a27333c045c451a677722 1888 
dh-python_4.20200925.dsc
 9c967b4afc0df2a9ebdbb1dec95c04b6d3a4442f03207f68000332eb03a9f2b9 95148 
dh-python_4.20200925.tar.xz
 c9614546b8f995d060d291c0a412b902d412a1f1abb74f2817744419fa8ee5bd 6241 
dh-python_4.20200925_amd64.buildinfo
Files:
 000aca59a8893d376f27e5c965355260 1888 python optional dh-python_4.20200925.dsc
 57f87b6ac5dc88d9dd1cf053e170 95148 python optional 
dh-python_4.20200925.tar.xz
 8c906c7d9d50d9f6b397aabc3fa6d5b5 6241 python optional 
dh-python_4.20200925_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAl9tyr0ACgkQrvbxoqdF
dkXWGRAAxL2l358+ZPMnma9fryKnbGnVQ6+srE+EltM3tkC7cL34Lx1R3HvwCr0A
J4VK5TRXEDAbPgwflyrw9dJyXEbDhgoYyH+RE+HmU6N6ej895AiJi2V4XlNCHj0n
I8GRJsDWnAYA+JY4/DsCMUi4rAq0DM9h16PY7skwVkh4Zw2o3ppvUMajRGLR+2Yd
C+H6Yz7HSSiolUDmQBrbmYer2cFfZucBWp47QbwdEXMPM3GXiSGAzzpXMyLKF3Pt
1Vd4SEzC+O1/DNnXrvG9ARmSBIHuFaDY2gdxE/XvRgZi4nLgb8xvpqaoxYEvUIUu
G+x43KEqi6zoZbU3eGomJ6b2l490rOTxEewDp7vYgX0QnOFsn6i27atflK9BYc9X
2/ig07MVi9Q0srfF4PWqww7ntHT6f1ADwtIrLnbi/dq1UPRSIRBVE8a4rlUsRPAA
8Tjr0etzJrLV/YcuD+jrcuVbsfrnQyEAgicHo+Ev8ut+WFbB0HOL5QB9dxOs8BOC
AMzQZadop7DLkRBbuRkYDH+fuSCbJGgGRZ2foKysUV++5A8N1hzLvzoG3EjAwohF
EiMcQm2BWRAeGN2up86ai/A9Y6Rdk3R9dgLy38n2Co2W6qhws5W6VGlFECOLuBUF
MS4OjuqTwWRXAtU0wVAMGYiM5yo3QzuAEMO68H2eEuT6OwRA6is=
=eTIJ
-END PGP SIGNATURE End Message ---


Bug#968046: marked as done (dh-python: missing Breaks+Replaces: python2 (<< 2.7.18))

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 11:03:28 +
with message-id 
and subject line Bug#968046: fixed in dh-python 4.20200925
has caused the Debian Bug report #968046,
regarding dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)
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.)


-- 
968046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-python
Version: 4.20200804
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../dh-python_4.20200804_all.deb ...
  Unpacking dh-python (4.20200804) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dh-python_4.20200804_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/dh-python_4.20200804_all.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 4.20200925
Done: =?utf-8?q?Piotr_O=C5=BCarowski?= 

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated dh-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Sep 2020 12:35:52 +0200
Source: dh-python
Architecture: source
Version: 4.20200925
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Closes: 968046 968193
Changes:
 dh-python (4.20200925) unstable; urgency=medium
 .
   * Add Breaks/Replaces python2 to ease upgrades with python2 (closes: 968046)
   * Disable Python 2.X tests by default (closes: 968193)
Checksums-Sha1:
 51f20bbd7436860e9570e632198551a48c63a9ff 1888 dh-python_4.20200925.dsc
 34ed20cee0ed35085ce055ba2326dcafc25b1331 95148 dh-python_4.20200925.tar.xz
 c9f84a3a2093533c2a7975e745a5f7feae5914d7 6241 
dh-python_4.20200925_amd64.buildinfo
Checksums-Sha256:
 324de47babc9241e35bae2cff6593e9f3a01beb3a21a27333c045c451a677722 1888 
dh-python_4.20200925.dsc
 9c967b4afc0df2a9ebdbb1dec95c04b6d3a4442f03207f68000332eb03a9f2b9 95148 
dh-python_4.20200925.tar.xz
 c9614546b8f995d060d291c0a412b902d412a1f1abb74f2817744419fa8ee5bd 6241 
dh-python_4.20200925_amd64.buildinfo
Files:
 000aca59a8893d376f27e5c965355260 1888 python optional dh-python_4.20200925.dsc
 57f87b6ac5dc88d9dd1cf053e170 95148 python optional 
dh-python_4.20200925.tar.xz
 8c906c7d9d50d9f6b397aabc3fa6d5b5 6241 python optional 
dh-python_4.20200925_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAl9tyr0ACgkQrvbxoqdF
dkXWGRAAxL2l358+ZPMnma9fryKnbGnVQ6+srE+EltM3tkC7cL34Lx1R3HvwCr0A
J4VK5TRXEDAbPgwflyrw9dJyXEbDhgoYyH+RE+HmU6N6ej895AiJi2V4XlNCHj0n
I8GRJsDWnAYA+JY4/DsCMUi4rAq0DM9h16PY7skwVkh4Zw2o3ppvUMajRGLR+2Yd
C+H6Yz7HSSiolUDmQBrbmYer2cFfZucBWp47QbwdEXMPM3GXiSGAzzpXMyLKF3Pt
1Vd4SEzC+O1/DNnXrvG9ARmSBIHuFaDY2gdxE/XvRgZi4nLgb8xvpqaoxYEvUIUu
G+x43KEqi6zoZbU3eGomJ6b2l490rOTxEewDp7vYgX0QnOFsn6i27atflK9BYc9X
2/ig07MVi9Q0srfF4PWqww7ntHT6f1ADwtIrLnbi/dq1UPRSIRBVE8a4rlUsRPAA
8Tjr0etzJrLV/YcuD+jrcuVbsfrnQyEAgicHo+Ev8ut+WFbB0HOL5QB9dxOs8BOC
AMzQZadop7DLkRBbuRkYDH+fuSCbJGgGRZ2foKysUV++5A8N1hzLvzoG3EjAwohF
EiMcQm2BWRAeGN2up86ai/A9Y6Rdk3R9dgLy38n2Co2W6qhws5W6VGlFECOLuBUF
MS4OjuqTwWRXAtU0wVAMGYiM5yo3QzuAEMO68H2eEuT6OwRA6is=
=eTIJ
-END PGP SIGNATURE End Message ---


Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

2020-09-25 Thread Gianfranco Costamagna
Hello,

> Adding node-tape to build-dependencies might fix the issue.
> 

please note, it might not fail because node-tape is added by some other rollup 
dependency, so its already installed.

But I think if a dependency is directly used by the tool, it should be declared 
explictly, we shouldn't rely
on something that is already available (specially because non essential)

G.



Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

2020-09-25 Thread Gianfranco Costamagna
Source: node-rollup-plugin-babel
Version: 5.2.1+~4.4.0-2
Severity: serious
tags: patch

Hello, looks like the autopkgtestsuite fails because of 
autopkgtest [08:35:49]: test pkg-js-autopkgtest: 
/usr/share/pkg-js-autopkgtest/runner
autopkgtest [08:35:49]: test pkg-js-autopkgtest: [---
Found debian/nodejs/main, package.json is packages/babel/package.json
Using packages/babel/package.json
Node module name is @rollup/plugin-babel
# Copy test files
Looking at /usr/lib/nodejs/@rollup/plugin-babel
Looking at /usr/lib/*/nodejs/@rollup/plugin-babel
Looking at /usr/share/nodejs/@rollup/plugin-babel
Found /usr/share/nodejs/@rollup/plugin-babel
Linking /usr/share/nodejs/@rollup/plugin-babel/dist
Linking /usr/share/nodejs/@rollup/plugin-babel/package.json
Linking /usr/share/nodejs/@rollup/plugin-babel/types
Launch debian/tests/pkg-js/test with sh -ex
+ cd packages/babel
+ tape test/as-input-plugin.js test/as-output-plugin.js
debian/tests/pkg-js/test: 2: tape: not found
autopkgtest [08:35:49]: test pkg-js-autopkgtest: ---]
autopkgtest [08:35:50]: test pkg-js-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -


Adding node-tape to build-dependencies might fix the issue.

thanks for having a look,

G.



Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

2020-09-25 Thread José Luis Blanco-Claraco
Thanks for reporting, Sebastian!

Although, I'm not sure how to proceed in this case... it compiled in
the past but it looks like the builder machine entered into swapping
(?) this time.

JL

--

/**
 * Jose Luis Blanco-Claraco
 * Universidad de Almería - Departamento de Ingeniería
 * [Homepage]( https://w3.ual.es/~jlblanco/ )
 * [GH profile]( https://github.com/jlblancoc )
 */



Bug#965288: marked as done (r-cran-findpython: Python2 removal in sid/bullseye)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 09:49:09 +
with message-id 
and subject line Bug#965288: fixed in r-cran-findpython 1.0.5-4
has caused the Debian Bug report #965288,
regarding r-cran-findpython: 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.)


-- 
965288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-findpython
Version: 1.0.5-2
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, in details:

(binary:r-cran-findpython)Recommends->python

Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: r-cran-findpython
Source-Version: 1.0.5-4
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-findpython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Sep 2020 11:29:56 +0200
Source: r-cran-findpython
Architecture: source
Version: 1.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 965288 967038
Changes:
 r-cran-findpython (1.0.5-4) unstable; urgency=medium
 .
   * Team upload.
   * Drop python from alternatives
 Closes: #965288, #967038
Checksums-Sha1:
 47110a124777d2d9caed7f6546ef1337cee3fef9 2146 r-cran-findpython_1.0.5-4.dsc
 9ab9366b437fb5f36d2dfd383159f92128b14c34 2576 
r-cran-findpython_1.0.5-4.debian.tar.xz
 5e78b6329a5855d913824e49bc7e95908e57dc33 8469 
r-cran-findpython_1.0.5-4_amd64.buildinfo
Checksums-Sha256:
 774d0244d8da0c9a73c5369f32bbe697970a5d897fe3db39c545ddc756f70cd1 2146 
r-cran-findpython_1.0.5-4.dsc
 c11158a5301158ce0a9471e46b83e34bd040dbe33754fb81a40d314d3af2 2576 
r-cran-findpython_1.0.5-4.debian.tar.xz
 9dd6c44ba81fd2b9f26857705a609cdad8ec9f88cf59f90520d0e2f33aba79de 8469 
r-cran-findpython_1.0.5-4_amd64.buildinfo
Files:
 29c8da6995786323f4675868833ec980 2146 gnu-r optional 
r-cran-findpython_1.0.5-4.dsc
 6f62924c0ab9e2b071cae6780949d11f 2576 gnu-r 

Bug#967038: marked as done (r-cran-findpython: Unversioned Python removal in sid/bullseye)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 09:49:09 +
with message-id 
and subject line Bug#967038: fixed in r-cran-findpython 1.0.5-4
has caused the Debian Bug report #967038,
regarding r-cran-findpython: Unversioned Python 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.)


-- 
967038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:r-cran-findpython
Version: 1.0.5-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

see
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-findpython/6517588/log.gz

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: r-cran-findpython
Source-Version: 1.0.5-4
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-findpython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Sep 2020 11:29:56 +0200
Source: r-cran-findpython
Architecture: source
Version: 1.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 965288 967038
Changes:
 r-cran-findpython (1.0.5-4) unstable; urgency=medium
 .
   * Team upload.
   * Drop python from alternatives
 Closes: #965288, #967038
Checksums-Sha1:
 47110a124777d2d9caed7f6546ef1337cee3fef9 2146 r-cran-findpython_1.0.5-4.dsc
 9ab9366b437fb5f36d2dfd383159f92128b14c34 2576 
r-cran-findpython_1.0.5-4.debian.tar.xz
 5e78b6329a5855d913824e49bc7e95908e57dc33 8469 
r-cran-findpython_1.0.5-4_amd64.buildinfo
Checksums-Sha256:
 774d0244d8da0c9a73c5369f32bbe697970a5d897fe3db39c545ddc756f70cd1 2146 
r-cran-findpython_1.0.5-4.dsc
 c11158a5301158ce0a9471e46b83e34bd040dbe33754fb81a40d314d3af2 2576 
r-cran-findpython_1.0.5-4.debian.tar.xz
 9dd6c44ba81fd2b9f26857705a609cdad8ec9f88cf59f90520d0e2f33aba79de 8469 
r-cran-findpython_1.0.5-4_amd64.buildinfo
Files:
 29c8da6995786323f4675868833ec980 2146 gnu-r optional 
r-cran-findpython_1.0.5-4.dsc
 6f62924c0ab9e2b071cae6780949d11f 2576 gnu-r optional 
r-cran-findpython_1.0.5-4.debian.tar.xz
 dae5095bc1e4ce1c8b163bb60a087d02 8469 gnu-r optional 
r-cran-findpython_1.0.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9tuekRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH/fQ//d27ISJ12rBCwTMiNblojzASAVHmZIL6D
BCeEA2VriqSsWmEVhWGKq0CQjtuZsbxHd+liIWh6/lXXIfSwKAlcyeZ79roOtHKc
LO/mMoyX9ZoNTcHs70nKmGyitA/Vf8lsWYDG26dRA3xd+ABYw27KD/A6Ea6fvjvf
msTeGcYRL/Gfg3wf/Zp/p89zREnL+9L/TJTEog07PeatfmUgP9NmMWzNb7VLpm4r
0eUcCE6nJUJ8DS22481vMlMN1DDKQLzBRKxa91gg7wIgdiWFwDYWvYiQN8gygMUk
FY8rkDQOegmIDaHFEP3gJMlgzjJvXFzOipemqtuQyTmzN7zyG5LaFVHwnxoX9x0Y
cusPP+09XZmT5FiTbtH8f+k0s6FJkVZfNxDr/gZB2P1LQbZw1RwOys+cseBEWFbe
SaInYA+Sh3JNUzsi7VOzwyOiM4LiNnEd5m7jYerV5Lxi6uGe9jsHT7kqKuvL6HmO
fKf5z+5aB3VhRmvcuFrhNSgRMlmZYewUHv1B/eHB+1BE+5BvSvy+K4oRP3H2UTjw
0ucQhlLf49K9dbdjM4/aftoqBCfK6uvOvDBrWocbOoTV1Xw6phfXrQ/NHvhmgNiZ

Bug#961491: marked as done (CVE-2020-10936: Security flaws in setuid wrappers)

2020-09-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Sep 2020 08:38:52 +
with message-id 
and subject line Bug#961491: fixed in sympa 6.2.40~dfsg-5
has caused the Debian Bug report #961491,
regarding CVE-2020-10936: Security flaws in setuid wrappers
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.)


-- 
961491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: sympa
severity: critical
tags: upstream security patch

Security advisory: https://sympa-community.github.io/security/2020-002.html

Excerpt:

--snip--
A vulnerability has been discovered in Sympa web interface by which attacker 
can execute arbitrary code with root
privileges.

Sympa uses two sorts of setuid wrappers:

FastCGI wrappers
newaliases wrapper

The FastCGI wrappers (wwsympa-wrapper.fcgi and sympa_soap_server-wrapper.fcgi) 
were used to make the web interface
running under privileges of a dedicated user.

The newaliases wrapper (sympa_newaliases-wrapper) allows Sympa to update the 
alias database with root privileges.

Since these setuid wrappers did not clear environment variables, if environment 
variables like PERL5LIB were injected,
forged code might be loaded and executed under privileges of setuid-ed users.
--snap--

Affects all versions of Sympa. Patch is attached.

The following change should also be considered to switch off installation as 
setuid, which is not needed in most cases:
https://github.com/sympa-community/sympa/pull/944/commits/bc9579c7abddc77c92ad51897bd16aba12383d5f

See also 
https://github.com/sympa-community/sympa/issues/943#issuecomment-633278517 
which claims that the patch
is incomplete.

CVE is not yet published.

Regards
Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
commit 3f8449c647e5ab32cf6f8837cb600c1756b6189c
Author: IKEDA Soji 
Date:   Fri Mar 27 21:28:18 2020 +0900

Sympa SA 2020-002 (candidate): Setuid wrappers should clear environment variables to avoid exploits.

diff --git a/src/cgi/sympa_soap_server-wrapper.fcgi.c b/src/cgi/sympa_soap_server-wrapper.fcgi.c
index f4c6a66..435d40c 100644
--- a/src/cgi/sympa_soap_server-wrapper.fcgi.c
+++ b/src/cgi/sympa_soap_server-wrapper.fcgi.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
   2006, 2007, 2008, 2009, 2010, 2011 Comite Reseau des Universites
   Copyright (c) 2011, 2012, 2013, 2014, 2015, 2016, 2017 GIP RENATER
+  Copyright 2020 The Sympa Community. See the AUTHORS.md
+  file at the top-level directory of this distribution and at
+  .
  
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
@@ -24,8 +27,10 @@
 #include 
 
 int main(int argn, char **argv, char **envp) {
+char *myenvp[] = { "IFS= \t\n", "PATH=/bin:/usr/bin", NULL };
+
 setreuid(geteuid(),geteuid());
 setregid(getegid(),getegid());
 argv[0] = SYMPASOAP;
-return execve(SYMPASOAP,argv,envp);
+return execve(SYMPASOAP, argv, myenvp);
 }
diff --git a/src/cgi/wwsympa-wrapper.fcgi.c b/src/cgi/wwsympa-wrapper.fcgi.c
index c66c7f8..34198ec 100644
--- a/src/cgi/wwsympa-wrapper.fcgi.c
+++ b/src/cgi/wwsympa-wrapper.fcgi.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
   2006, 2007, 2008, 2009, 2010, 2011 Comite Reseau des Universites
   Copyright (c) 2011, 2012, 2013, 2014, 2015, 2016, 2017 GIP RENATER
+  Copyright 2020 The Sympa Community. See the AUTHORS.md
+  file at the top-level directory of this distribution and at
+  .
  
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
@@ -24,8 +27,10 @@
 #include 
 
 int main(int argn, char **argv, char **envp) {
+char *myenvp[] = { "IFS= \t\n", "PATH=/bin:/usr/bin", NULL };
+
 setreuid(geteuid(),geteuid()); // Added to fix the segfault
 setregid(getegid(),getegid()); // Added to fix the segfault
 argv[0] = WWSYMPA;
-return execve(WWSYMPA,argv,envp);
+return execve(WWSYMPA, argv, myenvp);
 }
diff --git a/src/libexec/sympa_newaliases-wrapper.c b/src/libexec/sympa_newaliases-wrapper.c
index a399218..a1e5935 100644
--- a/src/libexec/sympa_newaliases-wrapper.c
+++ b/src/libexec/sympa_newaliases-wrapper.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
   

Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

2020-09-25 Thread Nicolas Noirbent
Package: black
Version: 20.8b1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The new black package version 20.8b1-1 seems to be missing some files:

% black
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in 
from black._black_version import version as __version__
ModuleNotFoundError: No module named 'black._black_version'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/black", line 33, in 
sys.exit(load_entry_point('black==20.8b1', 'console_scripts', 'black')())
  File "/usr/bin/black", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1014, in _gcd_import
  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 671, in _load_unlocked
  File "", line 783, in exec_module
  File "", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/black/__init__.py", line 65, in 
from _black_version import version as __version__
ModuleNotFoundError: No module named '_black_version'

Looking at the source, _black_version.py appears to be generated by the 
setup.py:
https://github.com/psf/black/blob/master/setup.py#L50-L53

Regards,


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

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

Versions of packages black depends on:
ii  python33.8.2-3
ii  python3-appdirs1.4.4-1
ii  python3-click  7.1.2-1
ii  python3-mypy-extensions0.4.3-1
ii  python3-pathspec   0.8.0-1
ii  python3-pkg-resources  49.3.1-2
ii  python3-regex  0.1.20200714-1
ii  python3-toml   0.10.1-1
ii  python3-typed-ast  1.4.1-1+b1
ii  python3-typing-extensions  3.7.4.2-1

black recommends no packages.

Versions of packages black suggests:
pn  python-black-doc  

-- no debconf information



Bug#970900: depends on non-existing qml-module-qtqml-modules2 (typo?)

2020-09-25 Thread fzielcke
Package: nextcloud-desktop
Version: 3.0.1-2
Severity: serious

Dear Maintainer,

now with the added dependencies to fix #969576 it's uninstallable on sid.

qml-module-qtqml-modules2 doestn't exist.
But maybe it's a typo and you actually meant qml-module-qtqml-models2? 

Kind regards
Felix Zielcke

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 nextcloud-desktop depends on:
ii  libc6 2.31-3
ii  libcloudproviders00.3.0-3
ii  libgcc-s1 10.2.0-9
ii  libglib2.0-0  2.66.0-2
ii  libnextcloudsync0 3.0.1-1
ii  libqt5core5a  5.14.2+dfsg-6
ii  libqt5dbus5   5.14.2+dfsg-6
ii  libqt5gui55.14.2+dfsg-6
ii  libqt5keychain1   0.10.0-1
ii  libqt5network55.14.2+dfsg-6
ii  libqt5qml55.14.2+dfsg-3
ii  libqt5quick5  5.14.2+dfsg-3
ii  libqt5quickcontrols2-55.14.2+dfsg-2
ii  libqt5sql5-sqlite 5.14.2+dfsg-6
ii  libqt5svg55.14.2-2
ii  libqt5webenginecore5  5.14.2+dfsg1-5
ii  libqt5webenginewidgets5   5.14.2+dfsg1-5
ii  libqt5webkit5 5.212.0~alpha4-5
ii  libqt5widgets55.14.2+dfsg-6
ii  libstdc++610.2.0-9
ii  nextcloud-desktop-common  3.0.1-2
ii  nextcloud-desktop-l10n3.0.1-2

Versions of packages nextcloud-desktop recommends:
pn  nextcloud-desktop-doc  

nextcloud-desktop suggests no packages.

-- no debconf information



Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

2020-09-25 Thread Emmanuel Bourg
On 24/09/2020 11:20, Paul Gevers wrote:

> Ping. This bug is blocking the migration of libhibernate-validator-java
> to testing (bug #953338).
> 
> If no solution to this issue can be found, I think we should revert to
> the previous version of libhibernate-validator-java.

Hi Paul,

The version 4.x has been packaged separately as
libhibernate-validator4-java. libspring-java has been updated to use it
but not the other reverse dependencies.

Emmanuel Bourg