Bug#954303: marked as done (tika: CVE-2020-1950)

[Debian Bug Tracking System]

Your message dated Tue, 02 Feb 2021 07:34:15 +
with message-id 
and subject line Bug#954303: fixed in tika 1.22-2
has caused the Debian Bug report #954303,
regarding tika: CVE-2020-1950
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.)


-- 
954303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tika
Version: 1.22-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1  1.20-1

Hi,

The following vulnerability was published for tika.

CVE-2020-1950[0]:
Excessive memory usage (DoS) vulnerability in Apache Tika's PSDParser

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-1950
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1950
[1] https://www.openwall.com/lists/oss-security/2020/03/18/3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: tika
Source-Version: 1.22-2
Done: Moritz Muehlenhoff 

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

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

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

Debian distribution maintenance software
pp.
Moritz Muehlenhoff  (supplier of updated tika package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Jan 2021 22:18:47 +0100
Source: tika
Architecture: source
Version: 1.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Moritz Muehlenhoff 
Closes: 954302 954303
Changes:
 tika (1.22-2) unstable; urgency=medium
 .
   * Cherrypick upstream commit to address CVE-2020-1950 and CVE-2020-1951
(Closes: #954303, #954302)
Checksums-Sha1:
 31fb5c91570fe58bc3e6f7c989bf7468afc53b3f 2732 tika_1.22-2.dsc
 9ad02e6f35307838dd6d39cc8ff84c5016eed29a 10064 tika_1.22-2.debian.tar.xz
 202ead43222ace98f70240335f8e8dc7c8f7e8a9 15597 tika_1.22-2_amd64.buildinfo
Checksums-Sha256:
 5a23fbd2bbe0a1b756385038078276e31e172ef7afe356bf9cdad01346738bc0 2732 
tika_1.22-2.dsc
 b5dc83cbffe016c5a0659856a03ce73adf1a57f2e50efe14302589a5e92b8585 10064 
tika_1.22-2.debian.tar.xz
 fbc99a32c97b8d31ffb1526b415cbd8752a97cd38dce8124ac10c178e52d81f8 15597 
tika_1.22-2_amd64.buildinfo
Files:
 d6f5cbfdb5d14c1bd011fa0bbca63782 2732 java optional tika_1.22-2.dsc
 426d89c6ae323c62a02eac0e4b3f5de7 10064 java optional tika_1.22-2.debian.tar.xz
 8f3ba6cc925ca4ff65b085c9d558cbf1 15597 java optional 
tika_1.22-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmAY9hsACgkQEMKTtsN8
Tjb1eg/9GCgc4sDJIplYNRA03EY4e7CuTMXRvLzl4oqfbclhug1qb/xk8aQRPBFp
gaLso7a6rblFyB7Du93AV62+DpdaHFMg1qB5KJMRHiNPaRtFBSlAo1u36nTEL7QF
BXd26r39a2FfIQpf/olJkVRznTWolK/9IX8yKtXi1ErdEgFuoGaAcGTOs99a0b8s
qJiGw/u/5pZ50I3rdWP6xrSXjGhKl7087ciSXNdGAjFR1fN7falSFZ2oLDn2hXgM
+NzvmdjmLUsqpJ07BXrg1Bon+ErVNzcfSKGpGSMMxjkmGXVJAoC33fl1GeKOHkZr
5hJbw9pBfVL5hcGQHDGRUIGlzXxzEoArTwXndUBk1/5ZPxo+qY3nQrO34pAsORTa
6W+uMQ6lpSOQGo57J5b3QL8hSgGwmvttk1ffqlq4NEMwP2Isk2YNUUa3WMAhSX5z
1/Fmyae9tFMxtVbAN2OiC4BAo3+/SlG40gl26QXfu2RC8n8QTh7VgCuTVgwKOicu
4yEMW+AhYGoiTufvI5K5l1qrmbgHvPamLhrIbVOI4NwSR2+gpzPL9upqJQJTkRy/
FOauPcGlmAta694eCPMr/JEBzDVNEVPY3nGyhRldhXHnudfqpIDiZryXu8x3mbni
uihfmuYGHfAx19TSdpEr3b8J9rQBE1ZT2egek12SETopIRTLhgE=
=rrYv
-END PGP SIGNATURE End Message ---

Bug#954302: marked as done (tika: CVE-2020-1951)

[Debian Bug Tracking System]

Your message dated Tue, 02 Feb 2021 07:34:15 +
with message-id 
and subject line Bug#954302: fixed in tika 1.22-2
has caused the Debian Bug report #954302,
regarding tika: CVE-2020-1951
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.)


-- 
954302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tika
Version: 1.22-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1.20-1

Hi,

The following vulnerability was published for tika.

CVE-2020-1951[0]:
Infinite Loop (DoS) vulnerability in Apache Tika's PSDParser

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-1951
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1951
[1] https://www.openwall.com/lists/oss-security/2020/03/18/4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tika
Source-Version: 1.22-2
Done: Moritz Muehlenhoff 

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

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

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

Debian distribution maintenance software
pp.
Moritz Muehlenhoff  (supplier of updated tika package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Jan 2021 22:18:47 +0100
Source: tika
Architecture: source
Version: 1.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Moritz Muehlenhoff 
Closes: 954302 954303
Changes:
 tika (1.22-2) unstable; urgency=medium
 .
   * Cherrypick upstream commit to address CVE-2020-1950 and CVE-2020-1951
(Closes: #954303, #954302)
Checksums-Sha1:
 31fb5c91570fe58bc3e6f7c989bf7468afc53b3f 2732 tika_1.22-2.dsc
 9ad02e6f35307838dd6d39cc8ff84c5016eed29a 10064 tika_1.22-2.debian.tar.xz
 202ead43222ace98f70240335f8e8dc7c8f7e8a9 15597 tika_1.22-2_amd64.buildinfo
Checksums-Sha256:
 5a23fbd2bbe0a1b756385038078276e31e172ef7afe356bf9cdad01346738bc0 2732 
tika_1.22-2.dsc
 b5dc83cbffe016c5a0659856a03ce73adf1a57f2e50efe14302589a5e92b8585 10064 
tika_1.22-2.debian.tar.xz
 fbc99a32c97b8d31ffb1526b415cbd8752a97cd38dce8124ac10c178e52d81f8 15597 
tika_1.22-2_amd64.buildinfo
Files:
 d6f5cbfdb5d14c1bd011fa0bbca63782 2732 java optional tika_1.22-2.dsc
 426d89c6ae323c62a02eac0e4b3f5de7 10064 java optional tika_1.22-2.debian.tar.xz
 8f3ba6cc925ca4ff65b085c9d558cbf1 15597 java optional 
tika_1.22-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmAY9hsACgkQEMKTtsN8
Tjb1eg/9GCgc4sDJIplYNRA03EY4e7CuTMXRvLzl4oqfbclhug1qb/xk8aQRPBFp
gaLso7a6rblFyB7Du93AV62+DpdaHFMg1qB5KJMRHiNPaRtFBSlAo1u36nTEL7QF
BXd26r39a2FfIQpf/olJkVRznTWolK/9IX8yKtXi1ErdEgFuoGaAcGTOs99a0b8s
qJiGw/u/5pZ50I3rdWP6xrSXjGhKl7087ciSXNdGAjFR1fN7falSFZ2oLDn2hXgM
+NzvmdjmLUsqpJ07BXrg1Bon+ErVNzcfSKGpGSMMxjkmGXVJAoC33fl1GeKOHkZr
5hJbw9pBfVL5hcGQHDGRUIGlzXxzEoArTwXndUBk1/5ZPxo+qY3nQrO34pAsORTa
6W+uMQ6lpSOQGo57J5b3QL8hSgGwmvttk1ffqlq4NEMwP2Isk2YNUUa3WMAhSX5z
1/Fmyae9tFMxtVbAN2OiC4BAo3+/SlG40gl26QXfu2RC8n8QTh7VgCuTVgwKOicu
4yEMW+AhYGoiTufvI5K5l1qrmbgHvPamLhrIbVOI4NwSR2+gpzPL9upqJQJTkRy/
FOauPcGlmAta694eCPMr/JEBzDVNEVPY3nGyhRldhXHnudfqpIDiZryXu8x3mbni
uihfmuYGHfAx19TSdpEr3b8J9rQBE1ZT2egek12SETopIRTLhgE=
=rrYv
-END PGP SIGNATURE End Message ---

Processed: Bug#949276 marked as pending in python-limits

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #949276 [src:python-limits] python-limits: autopkgtest needs update
Added tag(s) pending.

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

Bug#949276: marked as pending in python-limits

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-limits/-/commit/bafed4c64ed825436e039e90d7b63c69bdad062d


autopkgtest: Use redis-cli instead of redis-trib.rb. (Closes: #949276)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/949276

Bug#981612: epoptes-client: socat[1483] E Failed to set SNI host ""

[Vagrant Cascadian]

Package: epoptes-client
Severity: serious
Control: forwarded -1 https://github.com/epoptes/epoptes/issues/127
X-Debbugs-Cc: Vagrant Cascadian 

Reported upstream, but the short of it is socat 1.7.4.0 (recently
updated in bullseye) defaults to using Server Name Indication (SNI) and
epoptes-client needs to disable it:

  $ /usr/sbin/epoptes-client
  Epoptes-client connecting to server:789...2021/02/01 18:39:47 socat[1483] E 
Failed to set SNI host ""

Reported upstream and submitted pull request that should fix the issue,
but curious what upstream has to say before rushing to apply the patch
in Debian.


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: epoptes-client: socat[1483] E Failed to set SNI host ""

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/epoptes/epoptes/issues/127
Bug #981612 [epoptes-client] epoptes-client: socat[1483] E Failed to set SNI 
host ""
Set Bug forwarded-to-address to 'https://github.com/epoptes/epoptes/issues/127'.

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

Bug#981579: marked as done (sq: missing Breaks+Replaces: ispell (<< 3.4.00-6.1~))

[Debian Bug Tracking System]

Your message dated Tue, 02 Feb 2021 02:37:16 +
with message-id 
and subject line Bug#981579: fixed in rust-sequoia-sq 0.24.0-3
has caused the Debian Bug report #981579,
regarding sq: missing Breaks+Replaces: ispell (<< 3.4.00-6.1~)
to be marked as done.

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

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


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', 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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../archives/sq_0.24.0-2_amd64.deb ...
  Unpacking sq (0.24.0-2) ...
  dpkg: error processing archive /var/cache/apt/archives/sq_0.24.0-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/sq', which is also in package ispell 
3.4.00-6+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/sq_0.24.0-2_amd64.deb

ispell used to ship a sq binary, that was dropped in 3.4.00-6.1


cheers,

Andreas


ispell=3.4.00-6+b1_sq=0.24.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rust-sequoia-sq
Source-Version: 0.24.0-3
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated 
rust-sequoia-sq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Feb 2021 20:23:35 -0500
Source: rust-sequoia-sq
Architecture: source
Version: 0.24.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Daniel Kahn Gillmor 
Closes: 981579
Changes:
 rust-sequoia-sq (0.24.0-3) unstable; urgency=medium
 .
   * Package sequoia-sq 0.24.0 from crates.io using debcargo 2.4.3
   * indicate Breaks/Replaces: ispell (<< 3.4.00-6.1~) (Closes: #981579)
 Thanks, Andreas Beckmann!
Checksums-Sha1:
 f46818fcd6749bbb2e45711ae2f29bd275bed349 1945 rust-sequoia-sq_0.24.0-3.dsc
 afed4a87539e29d49ab6fcf720c67a5ef63ae420 3468 
rust-sequoia-sq_0.24.0-3.debian.tar.xz
 ac5a1d4bd569908a2d10352a393d5fd5de6f7b77 13693 
rust-sequoia-sq_0.24.0-3_source.buildinfo
Checksums-Sha256:
 b8852c002ccbe06629b13411154ff49c436a75f8002da6ba15199f121939bdda 1945 
rust-sequoia-sq_0.24.0-3.dsc
 532fa417acf653dabb6809c21072a8db0cc47d9e0d4270028ea153a7a78d0a77 3468 
rust-sequoia-sq_0.24.0-3.debian.tar.xz
 64e390a25b9a2fb1205a954a2d33b51181ac08821e66eafa9db504f1c5cf6e46 13693 
rust-sequoia-sq_0.24.0-3_source.buildinfo
Files:
 ba3f267126412a3a357e7dc75b147066 1945 utils optional 
rust-sequoia-sq_0.24.0-3.dsc
 0f6f6c107ec3bc6760be1cdb0ce6a54c 3468 utils optional 
rust-sequoia-sq_0.24.0-3.debian.tar.xz
 c9439ac2dc01968ee52c4f546cf5cccf 13693 utils optional 
rust-sequoia-sq_0.24.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYBipmwAKCRA+nXFzcd5W
XJaxAQC1Q1ZzSysxzu3JAkwsxzmSVrhrV/lZI2h9CVpeR7QgaAD/XpcUactJ2bFw
5TkGTBVNuTaxVK9wIrtUfoftm9+OjwY=
=t9Zx
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#981393: ltsp: Unable to generate image

[Debian Bug Tracking System]

Processing control commands:

> severity 981393 important
Bug #981393 [ltsp] ltsp: Unable to generate image
Severity set to 'important' from 'grave'
> tags 981393 moreinfo
Bug #981393 [ltsp] ltsp: Unable to generate image
Added tag(s) moreinfo.

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

Bug#981393: ltsp: Unable to generate image

[Vagrant Cascadian]

Control: severity 981393 important
Control: tags 981393 moreinfo

On 2021-01-30, peto wrote:
> Installing packages according to LTSP Documentation and running ltsp image
> command as recommended here: https://ltsp.org/docs/installation/
...
> # ltsp image /
...
> ltsp image /
> Using x86_64 as the base name of image /
> Running: mount -t tmpfs -o mode=0755 tmpfs /tmp/tmp.xFuUMTjWhL/tmpfs
> Running: mount -t overlay -o
> upperdir=/tmp/tmp.xFuUMTjWhL/tmpfs/0/up,lowerdir=/,workdir=/tmp/tmp.xFuUMTjWhL/tmpfs/0/work
> /tmp/tmp.xFuUMTjWhL/tmpfs /tmp/tmp.xFuUMTjWhL/root/
> Trying to acquire package management lock: /var/lib/dpkg/lock
> Cleaning up x86_64 before mksquashfs...
> Traceback (most recent call last):
>   File "/usr/share/ltsp/client/login/pwmerge", line 440, in 
> main(sys.argv)
>   File "/usr/share/ltsp/client/login/pwmerge", line 434, in main
> pwm = PwMerge(args[0], args[1], args[2], **dopts)
>   File "/usr/share/ltsp/client/login/pwmerge", line 117, in __init__
> self.dpasswd, self.dgroup = self.read_dir(ddir, dur or dgr)
>   File "/usr/share/ltsp/client/login/pwmerge", line 188, in read_dir
> grn = g2n[pwe[PW_GID]]
> KeyError: 1007
> LTSP command failed: /usr/share/ltsp/client/login/pwmerge --ltsp --quiet
> /tmp/tmp.xFuUMTjWhL/root/tmp/pwempty /tmp/tmp.xFuUMTjWhL/root/etc
> /tmp/tmp.xFuUMTjWhL/root/tmp/pwmerged
> Aborting ltsp

I did not encounter this on a freshly installed bullseye system.

So we still need to identify what triggers the issue in your case.


While upstream appreciates bug reports upstream and is very responsive,
if you really prefer to only use the Debian bug tracker, I can forward
relevent issues upstream too after we have more clarity.

If you do forward the issue upstream yourself, please mark the bug as
forwarded or mention here and I can mark it.


Thanks!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#973082: marked as done (python-biplist: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 02 Feb 2021 01:34:45 +
with message-id 
and subject line Bug#973082: fixed in python-biplist 1.0.3-3
has caused the Debian Bug report #973082,
regarding python-biplist: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


-- 
973082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biplist
Version: 1.0.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_biplist/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_biplist/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_biplist/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_biplist/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_biplist/build; 
> python3.9 -m nose -v tests
> testCurrentOffsetOutOfRange (test_fuzz_results.TestFuzzResults) ... ok
> testExcessivelyLongAsciiString (test_fuzz_results.TestFuzzResults) ... ok
> testIntegerWithZeroByteLength (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidArrayObjectCount (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidDictionaryObjectCount (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidMarkerByteUnpack (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidObjectOffset (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidOffsetEnding (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidRealLength (test_fuzz_results.TestFuzzResults) ... ok
> testNaNDateSeconds (test_fuzz_results.TestFuzzResults) ... ok
> testNegativelyLongAsciiString (test_fuzz_results.TestFuzzResults) ... ok
> testRecursiveObjectOffset (test_fuzz_results.TestFuzzResults) ... ok
> testEmptyFile (test_invalid.TestInvalidPlistFile) ... ok
> testInvalid (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidObjectRefOverflow (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidObjectRefSize (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsestTableOffset (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsetOverflow (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsetSize (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidTemplate (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidTopObjectNumber (test_invalid.TestInvalidPlistFile) ... ok
> testTooShort (test_invalid.TestInvalidPlistFile) ... ok
> testBoolOnly (test_valid.TestValidPlistFile) ... ok
> testEmptyUnicodeRoot (test_valid.TestValidPlistFile) ... ok
> testFileRead (test_valid.TestValidPlistFile) ... ok
> Archive is created with class like this: ... ok
> testLargeDates (test_valid.TestValidPlistFile) ... ok
> testLargeIntegers (test_valid.TestValidP

Processed: reopening 852746, reopening 975931

[Debian Bug Tracking System]

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

> reopen 852746
Bug #852746 {Done: Debian FTP Masters } 
[libllvm7,libllvm9,libllvm10] crash if multiple ICDs dynamically linked to 
LLVM: LLVM ERROR: inconsistency in registered CommandLine options
Bug #964810 {Done: Debian FTP Masters } 
[libllvm7,libllvm9,libllvm10] gimp: Failure to start - GTK problem
Bug #969972 {Done: Debian FTP Masters } 
[libllvm7,libllvm9,libllvm10] Gimp fails to start
Bug #971510 {Done: Debian FTP Masters } 
[libllvm7,libllvm9,libllvm10] gimp: Crashes on startup with "Option 'polly' 
registered more than once"
'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:10.0.1-8+rm.
No longer marked as fixed in versions 1:10.0.1-8+rm.
No longer marked as fixed in versions 1:10.0.1-8+rm.
No longer marked as fixed in versions 1:10.0.1-8+rm.
> reopen 975931
Bug #975931 {Done: Debian FTP Masters } 
[libllvm10,libllvm11] libgpuarray autopkgtest using pocl on armhf triggers 
segfault in LLVM
'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:10.0.1-8+rm.
> thanks
Stopping processing here.

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

Bug#981079: marked as done (request-tracker4: RT4 does not ship with real ckeditor source)

[Debian Bug Tracking System]

Your message dated Tue, 02 Feb 2021 00:23:34 +
with message-id 
and subject line Bug#981079: fixed in request-tracker4 4.4.4+dfsg-1
has caused the Debian Bug report #981079,
regarding request-tracker4: RT4 does not ship with real ckeditor source
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.)


-- 
981079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: request-tracker4
Version: 4.4.4-2
Severity: serious
Justification: DFSG

During packaging of RT5 it was noticed that the ckeditor source
shipped in third-party does not correspond to the preferred form
of modification - it is still minified (like that shipped in the main
tarball). This is due to a change of upstream practice since the
third-party tarball setup was originally introduced.

This is fixed in RT5 by repacking the third-party-source to add
additional sources - see[1]. We should do something similar for RT4,
at least if we will keep RT4 around in bullseye.

[1] 

--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.4+dfsg-1
Done: Dominic Hargreaves 

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Feb 2021 23:16:08 +
Source: request-tracker4
Architecture: source
Version: 4.4.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Closes: 666123 846029 981079
Changes:
 request-tracker4 (4.4.4+dfsg-1) unstable; urgency=medium
 .
   [ Andrew Ruthven ]
   * Switch from gpg1 to gpg2 (Closes: #846029)
 Import the following patches from the upstream 4.4-trunk branch to support
 GnuPG v2.2. They have not yet been included in a 4.4.x release:
  * upstream_4.4-trunk_gpg:_add_extra_ignored_keywords.diff
  * upstream_4.4-trunk_gpg:_add_gpg.conf.diff
  * upstream_4.4-trunk_gpg:_always_use_temp_gpg_homedir.diff
  * upstream_4.4-trunk_gpg:_default_cert-digest_algo_SHA256.diff
  * upstream_4.4-trunk_gpg:_dont_override_fingerprint.diff
  * upstream_4.4-trunk_gpg:_fix_unitialised_warning.diff
  * upstream_4.4-trunk_gpg:_handle_FAILURE_keyword.diff
  * upstream_4.4-trunk_gpg:_make_crypt-gnupg.t_happy.diff
  * upstream_4.4-trunk_gpg:_move_signed_style_with_attachment.eml.diff
  * upstream_4.4-trunk_gpg:_quit_gpg-agent.diff
  * upstream_4.4-trunk_gpg:_update_warning_message_tests.diff
   * Add myself to debian/copyright and as an Uploader
   * Add fix_test_ldap_ipv4.diff to fix LDAP test.
 .
   [ Dominic Hargreaves ]
   * Depend on perl-doc so that script usage is printed correctly
 (Closes: #666123)
   * Import new dfsg version of third-party sources (Closes: #981079)
   * Add scripts to add additional sources to third-party directory
   * Refresh debian/copyright
Checksums-Sha1:
 914a2d64e25d877e2bcb835f3cca70eda4b989e8 5597 request-tracker4_4.4.4+dfsg-1.dsc
 a550ba2a5f7281abf3e2638e950262524e752107 3178021 
request-tracker4_4.4.4+dfsg.orig-third-party-source.tar.gz
 e2c9ed8716a180638b4ce34a05d67bcc6c4c0935 9977845 
request-tracker4_4.4.4+dfsg.orig.tar.gz
 01d587ca74b6754f10829060189b8cda858f1a11 85488 
request-tracker4_4.4.4+dfsg-1.debian.tar.xz
 7b47558dbe3a65c7f3fe40469207286a47e02eac 19492 
request-tracker4_4.4.4+dfsg-1_source.buildinfo
Checksums-Sha256:
 c937d6a22270089595614a9efe6b02ab70c8d82ff03f916779aa9129a2766bb2 5597 
request-tracker4_4.4.4+dfsg-1.dsc
 9f142a07b09cd34c9120fa71b88fab7904bdb475096ac7405766d7ca2ee3505d 3178021 
request-tracker4_4.4.4+dfsg.orig-third-party-source.tar.gz
 34c316a4a78d7ee9b95d4391530f9bb3ff3edd99ebbebfac6354ed173e940884 9977845 
request-tracker4_4.4.4+dfsg.orig.tar.gz
 4e736f8e184ad8650778e9671617e1f76355942b2779a8dce337671d959

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Charles Malaheenee]

Hello Simon,

Thank you for your efforts!

> Do you have the dbus-user-session package installed?

I had to install it. Indeed, it helps - now gnome-keyring is working fine with 
latest package version of libglib.

> If you rely on the ability to have a separate D-Bus session bus per
> X11 display for the same uid, then you can't use dbus-user-session
> permanently, because it represents a different model where each uid has
> only one instance of the D-Bus session bus.

For my "testing" setup it is ok. But I'm asking myself - is it only 
gnome-keyring affected or this "security hardening" could break other 
GNOME/MATE parts? dbus-x11 is a strict dependency of 
mate-session-manager/gnome-session-bin, while dbus-user-session is not even 
suggested...

--
Best Regards,
Charles Malaheenee

Processed: Bug#980192 marked as pending in ruby

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980192 [ruby2.7] ruby-2.7: autopkgtest regression in testing: 
Errno::ENAMETOOLONG: File name too long
Added tag(s) pending.

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

Bug#980192: marked as pending in ruby

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #980192 in ruby 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/ruby-team/ruby/-/commit/cc93c81e53e9e007db577082e73e2c61e6ce6f15


autopkgtest: skip all rubygems-related tests

During autopkgtest, we don't want to run the tests from the rubygems
included with ruby against the (often newer) rubygems provided by
ruby-rubygems.

Closes: #980192

Gbp-Dch: full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980192

Bug#980581: marked as done (schleuder-cli: FTBFS: Could not find 'thor' (~> 0))

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 23:22:36 +
with message-id 
and subject line Bug#980581: fixed in schleuder-cli 0.1.0-4
has caused the Debian Bug report #980581,
regarding schleuder-cli: FTBFS: Could not find 'thor' (~> 0)
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/schleuder-cli/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"schleuder-cli\"
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `rescue in block 
> in activate_dependencies': Could not find 'thor' (~> 0) among 64 total gem(s) 
> (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/schleuder-cli/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/schleuder-cli/usr/share/rubygems-integration/all/specifications/schleuder-cli-0.1.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1388:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1388:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1370:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could not 
> find 'thor' (~> 0) - did find: [thor-1.0.1] (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/schleuder-cli/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1400:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1388:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1388:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1370:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default

Bug#980641: FTBFS due to pillow update

[Mathias Gibbens]

  This FTBFS was caused by version 8.1.0 of python3-pil migrating to
testing a couple of weeks ago. There's an upstream bug about this: 
https://github.com/OpenTTD/nml/pull/182. Their solution of restricting
the maximum version of pillow won't work for Debian.

  Pillow also has an issue open: 
https://github.com/python-pillow/Pillow/issues/5203.

  It would be a shame if openttd got autorm'ed just as the bullseye
freeze starts in earnest.

Mathias


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

Bug#979874: marked as done (node-cross-spawn-async: Keep out of testing)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:55:21 +
with message-id 
and subject line Bug#978418: Removed package(s) from unstable
has caused the Debian Bug report #979874,
regarding node-cross-spawn-async: Keep out of testing
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.)


-- 
979874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-cross-spawn-async
Version: 2.2.5-4
Severity: serious

As node-cross-spawn, node-cross-spawn-async shoul d be kept out of
Bullseye
--- End Message ---
--- Begin Message ---
Version: 2.2.5-4+rm

Dear submitter,

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

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

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

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

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

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

Bug#973119: marked as done (odb-api: FTBFS: GribMetaData.h:23:10: fatal error: eckit/types/Metadata.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:58:18 +
with message-id 
and subject line Bug#978618: Removed package(s) from unstable
has caused the Debian Bug report #973119,
regarding odb-api: FTBFS: GribMetaData.h:23:10: fatal error: 
eckit/types/Metadata.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.)


-- 
973119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odb-api
Version: 0.18.1-14
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/debian/build/metkit/src/metkit && /usr/bin/c++ 
> -Dmetkit_EXPORTS -I/<>/metkit/src 
> -I/<>/debian/build/metkit/src -I/usr/include/hdf5/serial 
> -I/usr/include/x86_64-linux-gnu/eckit -pthread 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
> -D_FORTIFY_SOURCE=2 -pipe -fPIC -std=gnu++11 -o 
> CMakeFiles/metkit.dir/grib/GribIndex.cc.o -c 
> /<>/metkit/src/metkit/grib/GribIndex.cc
> In file included from /<>/metkit/src/metkit/grib/GribIndex.cc:11:
> /<>/metkit/src/metkit/grib/GribMetaData.h:23:10: fatal error: 
> eckit/types/Metadata.h: No such file or directory
>23 | #include "eckit/types/Metadata.h"
>   |  ^~~~
> compilation terminated.
> make[4]: *** [metkit/src/metkit/CMakeFiles/metkit.dir/build.make:514: 
> metkit/src/metkit/CMakeFiles/metkit.dir/grib/GribIndex.cc.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/odb-api_0.18.1-14_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.18.1-14+rm

Dear submitter,

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

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

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

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

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

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

Bug#979039: marked as done (python3.8 is scheduled for removal and should not migrate to testing)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:59:21 +
with message-id 
and subject line Bug#978710: Removed package(s) from unstable
has caused the Debian Bug report #979039,
regarding python3.8 is scheduled for removal and should not migrate to testing
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.)


-- 
979039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python3.8
Severity: serious
Tags: sid bullseye

python3.8 is scheduled for removal and should not migrate to testing.
--- End Message ---
--- Begin Message ---
Version: 3.8.7-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#981537: marked as done (boinc-app-seti: SETT@home no longer exists)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:52:58 +
with message-id 
and subject line Bug#978085: Removed package(s) from unstable
has caused the Debian Bug report #981537,
regarding boinc-app-seti: SETT@home no longer exists
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.)


-- 
981537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boinc-app-seti
Severity: serious

https://setiathome.berkeley.edu/

SETI@home is in hibernation.
We are no longer distributing tasks. The SETI@home message boards will continue 
to operate, and we'll continue working on the back-end data analysis. Maybe 
we'll even find ET!

Thanks to everyone for your support over the years. We encourage you to keep 
crunching for science.
--- End Message ---
--- Begin Message ---
Version: 8.00~svn4035-1+rm

Dear submitter,

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

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

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

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

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

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

Processed: Re: [Debian-med-packaging] Bug#981404: compressed file is world readable, while zstd is running

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.4.8+dfsg-1
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Marked as fixed in versions libzstd/1.4.8+dfsg-1.
> tag -1 patch
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Added tag(s) patch.

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

Bug#957801: marked as done (siproxd: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:00:05 +
with message-id 
and subject line Bug#978740: Removed package(s) from unstable
has caused the Debian Bug report #957801,
regarding siproxd: 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.)


-- 
957801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:siproxd
Version: 1:0.8.1-4.1
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/siproxd_0.8.1-4.1_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

[...]
 from /usr/include/osipparser2/osip_port.h:24,
 from /usr/include/osipparser2/osip_headers.h:25,
 from /usr/include/osipparser2/osip_message.h:25,
 from /usr/include/osipparser2/osip_parser.h:24,
 from plugin_stun.c:33:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output between 8 and 16 bytes into a destination of 
size 15
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ^~~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
plugin_stun.c:259:70: warning: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Wformat-truncation=]
  259 |  snprintf(ipstring, IPSTRING_SIZE-1, "%u.%u.%u.%u",
  |  ^
In file included from /usr/include/stdio.h:867,
 from /usr/include/osipparser2/osip_port.h:24,
 from /usr/include/osipparser2/osip_headers.h:25,
 from /usr/include/osipparser2/osip_message.h:25,
 from /usr/include/osipparser2/osip_parser.h:24,
 from plugin_stun.c:33:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output between 8 and 16 bytes into a destination of 
size 15
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ^~~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-D_GNU_SOURCE -DBUILDSTR=\"53\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread 
-D_POSIX_THREAD_SAFE_FUNCTIONS -c plugin_stun.c -o plugin_stun.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=link gcc -D_GNU_SOURCE  
-DBUILDSTR="\"`cat .buildno`\"" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread 
-D_POSIX_THREAD_SAFE_FUNCTIONS -module -avoid-version -shrext '.so' 
-Wl,-z,relro  -o plugin_stun.la -rpath /usr/lib/x86_64-linux-gnu/siproxd 
plugin_stun.lo  -lresolv -losipparser2 -losip2   -lltdl 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/plugin_stun.o   -lresolv 
/usr/lib/x86_64-linux-gnu/libosipparser2.so 
/usr/lib/x86_64-linux-gnu/libosip2.so /usr/lib/x86_64-linux-gnu/libltdl.so  -g 
-O2 -fstack-protector-strong -pthread -Wl,-z -Wl,relro   -pthread -Wl,-soname 
-Wl,plugin_stun.so -o .libs/plugin_stun.so
libtool: link: ar cr .libs/plugin_stun.a  plugin_stun.o
libtool: link: ranlib .libs/plugin_stun.a
libtool: link: ( cd "

Bug#981404: [Debian-med-packaging] Bug#981404: compressed file is world readable, while zstd is running

[Étienne Mollier]

Control: fixed -1 1.4.8+dfsg-1
Control: tag -1 patch

Greetings,

This critical issue is affecting Stable.  Permissions at
compression time are inherited from umask, this may be too
relaxed when handling sensitive files.

Fortunately, this seems to have been fixed upstream around
version 1.4.1.  Debian Sid is not affected anymore as far as I
can see.  I identified the few commits[1,2,3,4] from Mike
Swanson and Yann Collet which solved the issue.

[1] 
https://github.com/facebook/zstd/commit/3968160a916a759c3d3418da533e1b4f8b795343
[2] 
https://github.com/facebook/zstd/commit/af80f6dfacafcc2c916ecd57731107221e1f9986
[3] 
https://github.com/facebook/zstd/commit/8b6d96827c24dd09109830272f413254833317d9
[4] 
https://github.com/facebook/zstd/commit/7aaac3f69c1e0102099c192639017e660e88b4bf

After some folding, I obtained the following patch, with which I
could derive a fixed version of zstd 1.3.8 for Buster:

---8<--8<--8<--8<---
--- libzstd.orig/programs/fileio.c
+++ libzstd/programs/fileio.c
@@ -482,8 +482,14 @@
 }   }
 
 {   FILE* const f = fopen( dstFileName, "wb" );
-if (f == NULL)
+if (f == NULL) {
 DISPLAYLEVEL(1, "zstd: %s: %s\n", dstFileName, strerror(errno));
+} else if (srcFileName != NULL
+   && strcmp (srcFileName, stdinmark)
+   && strcmp(dstFileName, nulmark) ) {
+/* reduce rights on newly created dst file while compression 
is ongoing */
+chmod(dstFileName, 00600);
+}
 return f;
 }
 }
---8<--8<--8<--8<---

Side note to Debian Med, I know the package is transitionning to
pkg-rpm team, and I am not super comfortable yet preparing an
upload to Stable[5], so I'm just providing a proposal of patch
as a starter.

[5] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#912941: marked as done (mozjs52: No longer maintained upstream)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:54:35 +
with message-id 
and subject line Bug#978404: Removed package(s) from unstable
has caused the Debian Bug report #912941,
regarding mozjs52: No longer maintained upstream
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.)


-- 
912941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs52
Version: 52.9.1-1
Severity: serious
Control: block -1 by 908234 912940

mozjs52 is no longer supported by Mozilla now that Firefox 52 ESR has
reached End of Life.

mozjs60 is the currently supported release.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 52.9.1-1.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#978309: marked as done (node-cross-spawn-async: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:55:21 +
with message-id 
and subject line Bug#978418: Removed package(s) from unstable
has caused the Debian Bug report #978309,
regarding node-cross-spawn-async: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
978309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-cross-spawn-async
Version: 2.2.5-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/cross-spawn-async
>   /bin/sh -ex debian/tests/pkg-js/test
> + nodejs test/prepare
> Copied "prepare_()%!^&;, .sh" to "()%!^&;, "
> + mocha -C -R spec --timeout 8000 test/test
> 
> Error: Cannot find module 'mkdirp'
> Require stack:
> - /<>/test/test.js
> - /usr/share/nodejs/mocha/lib/esm-utils.js
> - /usr/share/nodejs/mocha/lib/mocha.js
> - /usr/share/nodejs/mocha/lib/cli/one-and-dones.js
> - /usr/share/nodejs/mocha/lib/cli/options.js
> - /usr/share/nodejs/mocha/bin/mocha
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:831:15)
> at Function.Module._load (internal/modules/cjs/loader.js:687:27)
> at Module.require (internal/modules/cjs/loader.js:903:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/<>/test/test.js:7:14)
> at Module._compile (internal/modules/cjs/loader.js:1015:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
> at Module.load (internal/modules/cjs/loader.js:879:32)
> at Function.Module._load (internal/modules/cjs/loader.js:724:14)
> at Module.require (internal/modules/cjs/loader.js:903:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object.exports.requireOrImport 
> (/usr/share/nodejs/mocha/lib/esm-utils.js:20:12)
> at Object.exports.loadFilesAsync 
> (/usr/share/nodejs/mocha/lib/esm-utils.js:33:34)
> at Mocha.loadFilesAsync (/usr/share/nodejs/mocha/lib/mocha.js:431:19)
> at singleRun (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:125:15)
> at exports.runMocha 
> (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:190:10)
> at Object.exports.handler (/usr/share/nodejs/mocha/lib/cli/run.js:362:11)
> at /usr/share/nodejs/yargs/lib/command.js:238:63
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/node-cross-spawn-async_2.2.5-4_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.2.5-4+rm

Dear submitter,

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

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

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

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

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

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

Bug#978340: marked as done (proftpd-mod-dnsbl: FTBFS: Cannot compile mod_dnsbl using prxs)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:00:28 +
with message-id 
and subject line Bug#978747: Removed package(s) from unstable
has caused the Debian Bug report #978340,
regarding proftpd-mod-dnsbl: FTBFS: Cannot compile mod_dnsbl using prxs
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.)


-- 
978340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-dnsbl
Version: 0.1.5-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-dnsbl prxs -c mod_dnsbl.c
> Cannot compile mod_dnsbl using prxs; use existing ./configure script instead:
> 
>   ./configure
>   make
>   make install
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/proftpd-mod-dnsbl_0.1.5-5_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.1.5-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#977719: marked as done (spotweb: CVE-2020-35545)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:04:08 +
with message-id 
and subject line Bug#978996: Removed package(s) from unstable
has caused the Debian Bug report #977719,
regarding spotweb: CVE-2020-35545
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.)


-- 
977719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spotweb
Version: 20130826+dfsg3-4
Severity: important
Tags: security upstream
Forwarded: https://github.com/spotweb/spotweb/issues/629
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for spotweb.

CVE-2020-35545[0]:
| Time-based SQL injection exists in Spotweb 1.4.9 via the query string.


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-35545
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35545
[1] https://github.com/spotweb/spotweb/issues/629

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 20130826+dfsg3-4.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#981608: Missing old/ directory from upstream

[Erik Huelsmann]

Package: ledgersmb
Version: 1.6.9+ds-1
Severity: grave

As of version 1.6.0, upstream has split the software over three
directories (lib/, old/bin/ and old/lib/), instead of bin/ and lib/ in
prior versions). The package should have been adapted to this change,
but wasn't completely: the package misses the old/bin/ directory,
rendering the package almost completely unusable -- creation of
customers is still possible, but there's no way to create invoices or
transactions, which really is what the software is about entirely.


Suggested solution is to add the following rule to the ledgersmb.install file:

  old/bin/* usr/share/ledgersmb/old/bin




-- 
Bye,

Erik.

Bug#968313: marked as done (simpleburn: FTBFS: libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57: multiple definition of `ui')

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:59:43 +
with message-id 
and subject line Bug#978715: Removed package(s) from unstable
has caused the Debian Bug report #968313,
regarding simpleburn: FTBFS: 
libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57: 
multiple definition of `ui'
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.)


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

| [100%] Linking C executable simpleburn
| cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/simpleburn.dir/link.txt --verbose=1
| /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -rdynamic 
CMakeFiles/simpleburn.dir/simpleburn.c.o  -o simpleburn  libcallbacks.a 
libmediainfos.a libprogress.a -lcdio -lm -lcddb -ldvdread -lgtk-3 -lgdk-3 
-lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo 
-lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lm -lcddb -ldvdread 
-lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 
-lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
| /usr/bin/ld: 
libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57: 
multiple definition of `ui'; 
CMakeFiles/simpleburn.dir/simpleburn.c.o:./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57:
 first defined here
| /usr/bin/ld: 
libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/progress.h:5: 
multiple definition of `commandinfos'; 
CMakeFiles/simpleburn.dir/simpleburn.c.o:./obj-x86_64-linux-gnu/src/./src/progress.h:5:
 first defined here
| /usr/bin/ld: 
libmediainfos.a(mediainfos.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57:
 multiple definition of `ui'; 
CMakeFiles/simpleburn.dir/simpleburn.c.o:./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57:
 first defined here
| /usr/bin/ld: 
libprogress.a(progress.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57: 
multiple definition of `ui'; 
CMakeFiles/simpleburn.dir/simpleburn.c.o:./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57:
 first defined here
| /usr/bin/ld: 
libprogress.a(progress.c.o):./obj-x86_64-linux-gnu/src/./src/progress.h:5: 
multiple definition of `commandinfos'; 
CMakeFiles/simpleburn.dir/simpleburn.c.o:./obj-x86_64-linux-gnu/src/./src/progress.h:5:
 first defined here
| collect2: error: ld returned 1 exit status
| make[3]: *** [src/CMakeFiles/simpleburn.dir/build.make:90: src/simpleburn] 
Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=simpleburn&arch=amd64&ver=1.8.0-1%2Bb6&stamp=1597254973&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.8.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#980662: marked as done (bro: FTBFS: Error copying file "bloom-filter.bif.bro" to "/<>/build/scripts/base/bif/bloom-filter.bif.bro".)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:55:46 +
with message-id 
and subject line Bug#978539: Removed package(s) from unstable
has caused the Debian Bug report #980662,
regarding bro: FTBFS: Error copying file "bloom-filter.bif.bro" to 
"/<>/build/scripts/base/bif/bloom-filter.bif.bro".
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.)


-- 
980662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bro
Version: 2.6.4+ds1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/build'
> [  0%] [BIFCL] Processing bloom-filter.bif
> cd /<>/build/src/probabilistic && /usr/bin/bifcl -s 
> /<>/src/probabilistic/bloom-filter.bif || ( rm -f 
> bloom-filter.bif.h bloom-filter.bif.cc bloom-filter.bif.init.cc && exit 1 )
> [  0%] [BIFCL] Processing stats.bif
> cd /<>/build/src && /usr/bin/bifcl 
> /<>/src/stats.bif || ( rm -f 
> /<>/build/src/stats.bif.func_def 
> /<>/build/src/stats.bif.func_h 
> /<>/build/src/stats.bif.func_init 
> /<>/build/src/stats.bif.netvar_def 
> /<>/build/src/stats.bif.netvar_h 
> /<>/build/src/stats.bif.netvar_init && exit 1 )
> [  0%] [BIFCL] Processing event.bif
> cd /<>/build/src/probabilistic && /usr/bin/cmake -E copy 
> bloom-filter.bif.bro 
> /<>/build/scripts/base/bif/bloom-filter.bif.bro
> cd /<>/build/src && /usr/bin/bifcl 
> /<>/src/event.bif || ( rm -f 
> /<>/build/src/event.bif.func_def 
> /<>/build/src/event.bif.func_h 
> /<>/build/src/event.bif.func_init 
> /<>/build/src/event.bif.netvar_def 
> /<>/build/src/event.bif.netvar_h 
> /<>/build/src/event.bif.netvar_init && exit 1 )
> cd /<>/build/src && /usr/bin/cmake -E copy stats.bif.bro 
> /<>/build/scripts/base/bif/stats.bif.bro
> [  1%] [BIFCL] Processing bro.bif
> cd /<>/build/src && /usr/bin/cmake -E copy event.bif.bro 
> /<>/build/scripts/base/bif/event.bif.bro
> cd /<>/build/src && /usr/bin/bifcl /<>/src/bro.bif 
> || ( rm -f /<>/build/src/bro.bif.func_def 
> /<>/build/src/bro.bif.func_h 
> /<>/build/src/bro.bif.func_init 
> /<>/build/src/bro.bif.netvar_def 
> /<>/build/src/bro.bif.netvar_h 
> /<>/build/src/bro.bif.netvar_init && exit 1 )
> Error copying file "bloom-filter.bif.bro" to 
> "/<>/build/scripts/base/bif/bloom-filter.bif.bro".
> make[3]: *** 
> [src/probabilistic/CMakeFiles/bif-alt--build-bro-6Ew2WG-bro-2.6.4+ds1-build-src-probabilistic-bloom-filter.bif.dir/build.make:86:
>  src/probabilistic/bloom-filter.bif.h] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/bro_2.6.4+ds1-2_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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

Dear submitter,

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

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

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

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

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

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

Bug#929381: marked as done (needs cdrecord binary which isn't in Debian)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:59:43 +
with message-id 
and subject line Bug#978715: Removed package(s) from unstable
has caused the Debian Bug report #929381,
regarding needs cdrecord binary which isn't in Debian
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.)


-- 
929381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: simpleburn
Version: 1.8.0-1+b3
Severity: grave

I tried burning an iso with simpleburn but it completely fails due to depending 
on cdrecord:

$ simpleburn
command: simpleburn.sh /dev/cdrom b-iso 'debian-buster-DI-rc1-amd64-netinst.iso'
/usr/bin/simpleburn.sh: line 171: cdrecord: command not found

cdrecord isn't avaible even in oldstable.

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

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

Versions of packages simpleburn depends on:
ii  cdrdao   1:1.2.4-1
ii  cdrskin  1.5.0-1
ii  icedax   9:1.1.11-3+b2
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcddb2 1.3.2-6
ii  libcdio-utils2.0.0-2
ii  libcdio182.0.0-2
ii  libdvdread4  6.0.1-1
ii  libfribidi0  1.0.5-3.1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  xorriso  1.5.0-1

Versions of packages simpleburn recommends:
pn  flac
pn  mencoder
pn  mpg123  
pn  mplayer | mplayer2  
pn  normalize-audio 
pn  vorbis-tools

simpleburn suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.8.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#978123: marked as done (node-postcss-filter-plugins: broken with node-postcss 8.x)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:53:37 +
with message-id 
and subject line Bug#978126: Removed package(s) from unstable
has caused the Debian Bug report #978123,
regarding node-postcss-filter-plugins: broken with node-postcss 8.x
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.)


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

Package: node-postcss-filter-plugins
Version: 2.0.2-3
Severity: serious

autopkgtest fails with stderr output

postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration

This was reported on the team mailing list [1] and tracked in postcss 8 
transition wiki [2] but filing a bug here for completeness.


[1] 
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-September/044914.html

[2] https://wiki.debian.org/Javascript/Nodejs/Transitions/PostCSS8

Full log of the failure,

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-postcss-filter-plugins/9136124/log.gz

Since it is no longer has any reverse (build) dependencies, it can be 
removed.
--- End Message ---
--- Begin Message ---
Version: 2.0.2-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#979087: marked as done (incompatible with node-postcss 8 and unmaintained)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:53:55 +
with message-id 
and subject line Bug#978130: Removed package(s) from unstable
has caused the Debian Bug report #979087,
regarding incompatible with node-postcss 8 and unmaintained
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.)


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

Package: node-postcss-filter-plugins,node-postcss-minify-font-values
Severity: serious

Already filed request for removal. Filing rc bug in case the removal 
takes longer than auto removal from testing for node-postcss 8 testing 
migration.
--- End Message ---
--- Begin Message ---
Version: 1.0.5-1.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#967141: marked as done (gmlive: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:01:54 +
with message-id 
and subject line Bug#978979: Removed package(s) from unstable
has caused the Debian Bug report #967141,
regarding gmlive: 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.)


-- 
967141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gmlive
Version: 0.22.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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 ---
Version: 0.22.3-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#981439: marked as done (liblivemedia: includes non-free code from RFC 3550)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:20:52 +
with message-id 
and subject line Bug#981451: Removed package(s) from unstable
has caused the Debian Bug report #981439,
regarding liblivemedia: includes non-free code from RFC 3550
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.)


-- 
981439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblivemedia
Version: 2018.11.26-1.1
Severity: serious
Control: submitter -1 Joerg Jaspert 

Let's turn this into a bug.


- Forwarded message from Joerg Jaspert  
-

Date: Thu, 15 Oct 2020 21:00:09 +
From: Joerg Jaspert 
To: Sebastian Ramacher , Debian Multimedia Maintainers 

Subject: liblivemedia_2020.08.19-1_multi.changes REJECTED
Message-Id: 


Hi,

unfortunately we have to reject this package:

This package contains non-free code copied from RFC 3550.
RFC 3550 was written in 2003, prior to the modifications to the relicensing
of RFCs in 2005 to make the code written in RFC licensed under an open
source license. Debian confirmed this non-free interpretation in bug 92810.

Additionally, in this package, there are several files that have a
copyright header but no explicit license attached, other than "all
rights reserved".  Two even state "this code may not be copied or used in
any form without permission from Live Networks, Inc." 

Installed by liblivemedia-dev:
- usr/include/livemedia/HMAC_SHA1.hh ("this code may not...")
- usr/include/livemedia/HMAC_hash.hh ("this code may not...")
- usr/include/livemedia/liveMedia_version.hh (just version #defines)
- usr/include/groupsock/groupsock_version.hh (just version #defines)
- usr/include/UsageEnvironment/UsageEnvironment_version.hh (just version 
#defines)
- usr/include/BasicUsageEnvironment/BasicUsageEnvironment_version.hh (just 
version #defines)

orig.tar.gz (excludes files mentioned above):
- live/liveMedia/HMAC_SHA1.cpp ("this code may not...")
- live/liveMedia/SRTPCryptographicContext.cpp ("this code may not...")
- live/liveMedia/rtcp_from_spec.{c,h} is copied from RFC 3550 and 
draft-ietf-avt-rtp-new-11 which were written prior to 2005 and are thus 
non-free per bug 92810.
- live/mediaServer/version.hh (All rights reserved, but only version #defines)

-- 
bye Joerg



===

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


- End forwarded message -

-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 2020.01.19-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#909210: marked as done (don't ship automake-1.15 in bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:17:59 +
with message-id 
and subject line Bug#980241: Removed package(s) from unstable
has caused the Debian Bug report #909210,
regarding don't ship automake-1.15 in 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.)


-- 
909210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: automake-1.15
Version: 1:1.15.1-5
Severity: serious

The 1.15 -> 1.16 changes were relatively minor.

All FTBFS it caused should already be filed as bugs,
and most have already been fixed.

So far I haven't seen a single one that would have
been difficult to fix.

There are currently no reverse (build) dependencies
on automake-1.15 in unstable, and I do not think
there should ever be any.

I might be missing something, but my current impression
is that we should not ship automake-1.15 in buster.
--- End Message ---
--- Begin Message ---
Version: 1:1.15.1-5.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#979223: marked as done (src:moblin-icon-theme: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:14:59 +
with message-id 
and subject line Bug#979342: Removed package(s) from unstable
has caused the Debian Bug report #979223,
regarding src:moblin-icon-theme: invalid maintainer address
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.)


-- 
979223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moblin-icon-theme
Version: 0.10.0-2
Severity: serious
X-Debbugs-Cc: Ying-Chun Liu (PaulLiu) , Holger Levsen 


The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Sun, 03 Jan 2021 13:05:47 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  zhengpeng-...@ubuntu.com
host mx.canonical.com [91.189.95.10]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in virtual alias table
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;zhengpeng-hou@ubuntu.com
Status: 5.0.0
Remote-MTA: dns; mx.canonical.com
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table
 End of forwarded message 
--- End Message ---
--- Begin Message ---
Version: 0.10.0-2.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#981540: marked as done (dtaus: Service no longer available)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:50:32 +
with message-id 
and subject line Bug#977879: Removed package(s) from unstable
has caused the Debian Bug report #981540,
regarding dtaus: Service no longer available
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.)


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

Quoting #977879:

This payment processing method was shut down in 2016:
https://de.wikipedia.org/wiki/Datentr%C3%A4geraustauschverfahren
--- End Message ---
--- Begin Message ---
Version: 0.9-1.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#981539: marked as done (cloudprint: Service has been shutdown)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:48:48 +
with message-id 
and subject line Bug#977644: Removed package(s) from unstable
has caused the Debian Bug report #981539,
regarding cloudprint: Service has been shutdown
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.)


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

https://support.google.com/chrome/answer/1069693

Adding this bug as a reminder that the package should
also be removed from buster.
--- End Message ---
--- Begin Message ---
Version: 0.14-14+rm

Dear submitter,

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

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

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

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

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

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

Bug#981600: nghttp2: util_localtime_date test fails in arch-only build

[Helmut Grohne]

Source: nghttp2
Version: 1.42.0-1
Severity: serious
Tags: ftbfs

An arch-only build (but not a full build) of nghttp2 seems to reliably
fail at test util_localtime_date:

|   Test: util_localtime_date ...FAILED
| 1. util_test.cc:454  - CU_ASSERT_STRING_EQUAL("02/Oct/2001:00:34:56 
+1200",util::common_log_date(1001939696).c_str())
| 2. util_test.cc:456  - 
CU_ASSERT_STRING_EQUAL("2001-10-02T00:34:56.123+12:00",util::iso8601_date(1001939696000LL
 + 123).c_str())
| 3. util_test.cc:461  - "02/Oct/2001:00:34:56 +1200" == 
util::format_common_log(common_buf.data(), 
std::chrono::system_clock::time_point( std::chrono::seconds(1001939696)))
| 4. util_test.cc:468  - "2001-10-02T00:34:56.123+12:00" == 
util::format_iso8601(iso8601_buf.data(), std::chrono::system_clock::time_point( 
std::chrono::milliseconds(1001939696123LL)))
...
| 
| Run Summary:Type  TotalRan Passed Failed Inactive
|   suites  1  1n/a  00
|tests 90 90 89  10
|  asserts   1011   1011   1007  4  n/a
| 
| Elapsed time =0.001 seconds
| FAIL nghttpx-unittest (exit status: 1)
| 
| 
| Testsuite summary for nghttp2 1.42.0
| 
| # TOTAL: 1
| # PASS:  0
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| See src/test-suite.log
| Please report to t-tujik...@users.sourceforge.net
| 
| make[5]: *** [Makefile:2787: test-suite.log] Error 1
| make[5]: Leaving directory '/<>/src'
| make[4]: *** [Makefile:2895: check-TESTS] Error 2
| make[4]: Leaving directory '/<>/src'
| make[3]: *** [Makefile:2994: check-am] Error 2
| make[3]: Leaving directory '/<>/src'
| make[2]: *** [Makefile:2679: check-recursive] Error 1
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:569: check-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2
| make: *** [debian/rules:64: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Since reproducible only performs full builds, it doesn't see this issue.
Likewise crossqa skips tests and does not see it either. I don't
understand the cause here and just report it. I hope it reproduces
reliably elsewhere as well.

Helmut

Bug#980709: marked as done (dolfin: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 22:43:45 +0100
with message-id <558db823ca4a04f9caf628a9b5ca7...@debian.org>
and subject line Re: dolfin: FTBFS: tests failed
has caused the Debian Bug report #980709,
regarding dolfin: FTBFS: tests failed
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.)


-- 
980709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolfin
Version: 2019.2.0~git20200629.946dbd3+lfs-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[8]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 98%] Building CXX object 
> demo/undocumented/waveguide/cpp/CMakeFiles/demo_waveguide.dir/main.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/demo/undocumented/waveguide/cpp" && 
> /usr/bin/c++ -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 
> -DHAS_MPI -DHAS_PETSC -DHAS_SCOTCH -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG 
> -I"/<>" -I"/<>/dolfin" 
> -I"/<>/obj-x86_64-linux-gnu" -isystem 
> /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem /usr/include/eigen3 
> -isystem /usr/include/hdf5/openmpi -isystem 
> /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem 
> /usr/lib/x86_64-linux-gnu/openmpi/include -isystem 
> /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/include -Wno-comment 
> -fpermissive -O2 -g -DNDEBUG -std=c++11 -o 
> CMakeFiles/demo_waveguide.dir/main.cpp.o -c 
> "/<>/demo/undocumented/waveguide/cpp/main.cpp"
> [ 98%] Linking CXX executable demo_spatial-coordinates
> cd 
> "/<>/obj-x86_64-linux-gnu/demo/undocumented/spatial-coordinates/cpp"
>  && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/demo_spatial-coordinates.dir/link.txt --verbose=1
> /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro 
> CMakeFiles/demo_spatial-coordinates.dir/main.cpp.o -o 
> demo_spatial-coordinates  ../../../../dolfin/libdolfin.so.2019.2.0.dev0 
> /usr/lib/x86_64-linux-gnu/libboost_timer.so 
> /usr/lib/x86_64-linux-gnu/libboost_chrono.so 
> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so 
> /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so 
> /usr/lib/x86_64-linux-gnu/libdl.so -lm 
> /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
> make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 98%] Built target demo_spatial-coordinates
> [ 98%] Linking CXX executable demo_waveguide
> cd "/<>/obj-x86_64-linux-gnu/demo/undocumented/waveguide/cpp" && 
> /usr/bin/cmake -E cmake_link_script CMakeFiles/demo_waveguide.dir/link.txt 
> --verbose=1
> /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro 
> CMakeFiles/demo_waveguide.dir/main.cpp.o -o demo_waveguide  
> ../../../../dolfin/libdolfin.so.2019.2.0.dev0 
> /usr/lib/x86_64-linux-gnu/libboost_timer.so 
> /usr/lib/x86_64-linux-gnu/libboost_chrono.so 
> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so 
> /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so 
> /usr/lib/x86_64-linux-gnu/libdl.so -lm 
> /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
> make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 98%] Built target demo_waveguide
> [100%] Linking CXX executable demo_sym-dirichlet-bc
> cd 
> "/<>/obj-x86_64-linux-gnu/demo/undocumented/sym-dirichlet-bc/cpp"
>  && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/demo_sym-dirichlet-bc.dir/link.txt --verbose=1
> /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro 
> CMakeFiles/demo_sym-dirichlet-bc.dir/main.cpp.o -o demo_sym-dirichlet-bc  
> ../../../../dolfin/libdolfin.so.2019.2.0.dev0 
> /usr/lib/x86_64-linux-gnu/libboost_timer.so 
> /usr/lib/x86_64-linux-gnu/libboost_chrono.so 
> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so 
> /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so 
> /usr/lib/x86_64-linux-gnu/libdl.so -lm 
> /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
> make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [100%] Built target demo_sym-dirichlet-bc
> [100%] Linking CXX executable demo_time-series
> cd "/<>/obj-x86_64-linux-gnu/demo/undocumen

Bug#969623: marked as done (gnome-shell-extension-show-ip: load fails: ReferenceError: None is not defined)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:43:04 +
with message-id 
and subject line Bug#977475: Removed package(s) from unstable
has caused the Debian Bug report #969623,
regarding gnome-shell-extension-show-ip: load fails: ReferenceError: None is 
not defined
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.)


-- 
969623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-show-ip
Version: 8-6
Severity: serious

I noticed that this extension now fails to load with this error:

ReferenceError: None is not defined

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell-extension-show-ip depends on:
ii  gnome-shell  3.36.5-1
ii  gnome-shell-extension-prefs  3.36.5-1

gnome-shell-extension-show-ip recommends no packages.

gnome-shell-extension-show-ip suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 8-6+rm

Dear submitter,

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

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

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

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

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

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

Bug#975931: marked as done (libgpuarray autopkgtest using pocl on armhf triggers segfault in LLVM)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:35:25 +
with message-id 
and subject line Bug#974788: Removed package(s) from unstable
has caused the Debian Bug report #975931,
regarding libgpuarray autopkgtest using pocl on armhf triggers segfault in LLVM
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.)


-- 
975931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl, libgpuarray
Control: found -1 pocl/1.5-7
Control: found -1 libgpuarray/0.7.6-5
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 pocl the autopkgtest of libgpuarray fails in
testing when that autopkgtest is run with the binary packages of pocl
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
pocl   from testing1.5-7
libgpuarrayfrom testing0.7.6-5
all others from testingfrom testing

I copied some of the output at the bottom of this report. There's not a
hell of a lot to use for debugging.

Currently this regression is blocking the migration of pocl 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=pocl

https://ci.debian.net/data/autopkgtest/testing/amdhf/libg/libgpuarray/8423908/log.gz

autopkgtest [20:16:04]: test command1: set -e ; for py in $(py3versions
-r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ;
DEVICE=opencl0:0 $py -m nose -v pygpu.tests ; echo "Testing with
$py-dbg:" ; DEVICE=opencl0:0 $py-dbg -m nose -v pygpu.tests ; done
autopkgtest [20:16:04]: test command1: [---
Testing with python3.9:
*** Testing for pthread-x-gene-1
mpi4py found: True
runTest (pygpu.tests.test_basic.test_errors) ... ok
pygpu.tests.test_basic.test_tril ... ok
pygpu.tests.test_basic.test_triu ... ok
pygpu.tests.test_blas.test_dot(1, 'float32', True, True, True, False)
... bash: line 1:  2439 Segmentation fault  DEVICE=opencl0:0 $py -m
nose -v pygpu.tests
autopkgtest [20:16:16]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1:10.0.1-8+rm

Dear submitter,

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

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

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

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

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

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

Bug#956881: marked as done (enchant: Keep out of bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:29:21 +
with message-id 
and subject line Bug#969473: Removed package(s) from unstable
has caused the Debian Bug report #956881,
regarding enchant: Keep out of 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.)


-- 
956881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enchant
Version: 1.6.0-11.3
Severity: serious
Tags: sid bullseye

Hello,

I don't think we want to ship both enchant (v1) and enchant-2 in
bullseye.

The transition[0] is in progress and bugs (most with patch) have been
opened against the rdeps.

So let's make it clear that enchant will not be present in bullseye.

Kind regards,

Laurent Bigonville

[0] https://release.debian.org/transitions/html/enchant-2.html


-- 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)

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

Dear submitter,

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

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

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

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

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

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

Bug#960748: marked as done (node-babel: meta bug to keep out of testing)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 21:23:51 +
with message-id 
and subject line Bug#960761: Removed package(s) from unstable
has caused the Debian Bug report #960748,
regarding node-babel: meta bug to keep out of testing
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.)


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

Package: node-babel
Version: 6.26.0+repack-4
Severity: serious
Control: block -1 by 960120
Control: block -1 by 959798
Control: block -1 by 960021

src:node-babel (babel 6.x) is replaced by src:node-babel7 (babel 7.x) 
and src:node-babel should not be part of bullseye.


The status of this transition is tracked at,
https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7

Last blockers for removal:

1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch 
to 'berry'/2.x (supports babel 7) in time for bullseye
2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by 
webpack

3. rainloop - #960021 - not in bullseye

Once the blockers are fixed, this should be changed to an RM bug.
--- End Message ---
--- Begin Message ---
Version: 6.26.0+repack-4+rm

Dear submitter,

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

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

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

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

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

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

Bug#975931: should be fixed with pocl 1.6 ?

[Andreas Beckmann]

On 2/1/21 8:56 PM, Paul Gevers wrote:
> On 21-01-2021 16:33, Paolo Greppi wrote:
>> pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares
>> that v1.6 includes "Support for Clang/LLVM 11".
> 
> And the autopkgtest doesn't fail anymore indeed.

Because we are back to LLVM 9, due to this regression.

Based on this bug and the generated OpenCL kernel involved I've added a
test to pocl in plain C that exhibits the bug without requiring python
or third-party libraries. That does fail on armhf with LLVM 10/11.

Since I don't know how to debug the state when pocl calls llvm, I'm
stuck here.


Andreas

Bug#976735: spyder needs source upload for Python 3.9 transition

[Julian Gilbey]

On Mon, Feb 01, 2021 at 09:45:24PM +0530, Nilesh Patra wrote:
> Hi Julian
> I read through the rest of the thread.
> 
> On Mon, 1 Feb, 2021, 6:31 pm Julian Gilbey,  wrote:
> 
>   I have a package of Spyder 4 waiting to upload, but it requires five
>   packages to be accepted into unstable from NEW first (pyls-server,
>   pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
>   rest of the packages are almost ready to
> 
>   go.
> 
> I requested on IRC (probably again after you) to process these ASAP, however I
> don't see pyls-server in NEW or at the archive yet.
> Has this been rejected, or am I missing something?
> Nilesh

Aww, thanks!!

My mistake (I was typing from memory in a rush); here is the correct
list of source packages:

euler:~ $ rmadison python-language-server pyls-black pyls-spyder abydos 
textdistance
abydos | 0.5.0+git20201231.344346a-1 | new| source
pyls-black | 0.4.6-1 | new| source
pyls-spyder| 0.3.0-1 | new| source
python-language-server | 0.36.2-1| new| source
textdistance   | 4.2.0-1 | new| source

Best wishes,

   Julian

Bug#975931: should be fixed with pocl 1.6 ?

[Paul Gevers]

Hi Paolo,

On 21-01-2021 16:33, Paolo Greppi wrote:
> pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares
> that v1.6 includes "Support for Clang/LLVM 11".

And the autopkgtest doesn't fail anymore indeed.

> Can you try your reproducer now ?

I *expect* it to reproduce the same path as the autopkgtest from
libgpuarray, so I *guess* it's gone there too.

We haven't established yet whether there was a bug in pocl, or if llvm
was to blame.

"""
a compiler (library) should not segfault in this case.
I hope you can shed some light on whether llvm or pocl is to
blame here.
"""

If it was pocl, this bug can be closed.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 976907 is normal

[Debian Bug Tracking System]

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

> # arch: all buildds run amd64
> severity 976907 normal
Bug #976907 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS on 
ppc64el (arch:all-only src pkg): dh_auto_test: error: cd 
obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short 
github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit code 1
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 976945 is important

[Debian Bug Tracking System]

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

> # arch: all buildds run amd64
> severity 976945 important
Bug #976945 [src:ruby-awesome-print] ruby-awesome-print: FTBFS on ppc64el 
(arch:all-only src pkg): ERROR: Test "ruby2.7" failed:  Failure/Error: 
expect(my.ai(plain: true)).to eq("#{my.inspect}\n" << `ls -alF 
#{my.path}`.chop)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#981300: arduino-core-avr breaks arduino-mk

[Carsten Schoenert]

Hi again,

Am Mon, Feb 01, 2021 at 07:54:51PM +0100 schrieb Carsten Schoenert:
 
> > the problem tends to be getting arduino-mk updated, think last time it
> > needed a team upload (python3 fixes).
> 
> If you need help let me know, currently I can't that Python3 fixes you
> mean.

hrhr, I need to read my writing again before start sending this...

I meant here I can't see what fixes will get needed.

O.k., I quickly imported 1.6.0 and there is one more .py file added to
the bin/ folder.

Running 2to3 on the folder shows just small further needed adjustments.

$ 2to3-2.7 bin/*
RefactoringTool: Skipping optional fixer: buffer
RefactoringTool: Skipping optional fixer: idioms
RefactoringTool: Skipping optional fixer: set_literal
RefactoringTool: Skipping optional fixer: ws_comma
RefactoringTool: Refactored bin/ard-reset-arduino
--- bin/ard-reset-arduino   (original)
+++ bin/ard-reset-arduino   (refactored)
@@ -1,6 +1,6 @@
 #!/usr/bin/env python
 
-from __future__ import print_function
+
 import serial
 import os.path
 import argparse
RefactoringTool: Refactored bin/robotis-loader
--- bin/robotis-loader  (original)
+++ bin/robotis-loader  (refactored)
@@ -25,7 +25,7 @@
 def progressBar(percent, precision=65):
 threshold=precision*percent/100.0
 sys.stdout.write('[ ')
-for x in xrange(0, precision):
+for x in range(0, precision):
 if x < threshold: sys.stdout.write('#')
 else: sys.stdout.write(' ')
 sys.stdout.write(' ] ')
@@ -36,7 +36,7 @@
 stat = os.stat(binary)
 size = stat.st_size
 firmware = file(binary, 'rb')
-print('* Opening %s, size=%d' % (binary, size))
+print(('* Opening %s, size=%d' % (binary, size)))
 except:
 exit('! Unable to open file %s' % binary)
 
@@ -80,7 +80,7 @@
 break
 print('')
 s.setDTR(True)
-print('* Checksum: %d' % (cs))
+print(('* Checksum: %d' % (cs)))
 s.write(chr(cs))
 print('* Firmware was sent')
 else:
@@ -91,4 +91,4 @@
 s.close()
 exit()
 else:
-print('Board -> '+line)
+print(('Board -> '+line))
RefactoringTool: Files that need to be modified:
RefactoringTool: bin/ard-reset-arduino
RefactoringTool: bin/robotis-loader

Seems doable without big headaches. Let me know how you like to proceed.

Regards
Carsten

Processed: severity of 976937 is important

[Debian Bug Tracking System]

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

> # arch: all buildds run amd64
> severity 976937 normal
Bug #976937 [src:python-trio] python-trio: FTBFS on ppc64el (arch:all-only src 
pkg): E: Build killed with signal TERM after 150 minutes of inactivity
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#973082: confirmed

[Hans-Christoph Steiner]

Great!  Then it sounds like it should be included.  It is a Python Team package 
and the source code is on salsa, so feel free to go ahead and upload.

Bug#979051: marked as done (src:aspell-hr: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 19:19:11 +
with message-id 
and subject line Bug#979051: fixed in aspell-hr 0.51-5
has caused the Debian Bug report #979051,
regarding src:aspell-hr: invalid maintainer address
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.)


-- 
979051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspell-hr
Version: 0.51-4
Severity: serious
X-Debbugs-Cc: Holger Levsen 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Sat, 02 Jan 2021 01:48:31 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  vedr...@riteh.hr
host rijeka.riteh.hr [161.53.40.4]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
--- End Message ---
--- Begin Message ---
Source: aspell-hr
Source-Version: 0.51-5
Done: Baptiste Beauplat 

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

Debian distribution maintenance software
pp.
Baptiste Beauplat  (supplier of updated aspell-hr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Feb 2021 18:07:28 +0100
Source: aspell-hr
Architecture: source
Version: 0.51-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Baptiste Beauplat 
Closes: 778679 965416 979051
Changes:
 aspell-hr (0.51-5) unstable; urgency=medium
 .
   * QA upload.
   * Remove trailing whitespace from changelog
   * Set Maintainer as Debian QA Group (See: #981056) (Closes: #979051)
   * Convert to debhelper:
 - Replace debhelper Build-Depends by debhelper-compat
 - Bump debhelper-compat to 13 (Closes: #965416)
 - Remove d/compat
 - Convert d/rules to use debhelper with aspell-simple
   (override_dh_auto_configure target added)
 - Delegate file installation to d/install (dh-exec style)
 - Delegate cleanup to d/clean
 - Add aspell and dh-exec to Build-Depends
 - Bump dictionaries-common-dev version to 1.23 in Build-Depends and
   Depends, required to automatically create symlinks and clean files.
   This effectively remove empty or unused file hr.compat, hr.rws and
   hr.contents (Closes: #778679)
 - Add ${misc:Depends} to Depends
   * Convert source package to 3.0 (quilt) format (no patches)
   * Remove unused d/dirs
   * Add watch file and upstream signing key
   * Host packaging project on Salsa:
 - Add Salsa CI pipeline
 - Use recommended branch name from DEP14
 - Add Vcs-* Fields
   * Convert copyright to DEP5
   * Bump Standard-Version to 4.5.1
   * Set Rules-Requires-Root: no
   * Add Homepage field
   * Remove article from short description
   * Add lintian-overrides to silence false positives:
 - Homepage is not a directory listing
 - Text is the correct section for an aspell dictionary
Checksums-Sha1:
 6ea0af158cd18fa1cc6af9daad2b488f03ce78d0 2150 aspell-hr_0.51-5.dsc
 6788b9001287f9debd59803f5f9c5005b701f8f7 208118 aspell-hr_0.51.orig.tar.bz2
 f063aca9a4d4ae098aba3dce326877c86e50c726 155 aspell-hr_0.51.orig.tar.bz2.asc
 5ec708de22257c8d5cf4e5d704e5b1cd222b1faf 4188 aspell-hr_0.51-5.debian.tar.xz
 95195871fbda929f280147cda031fa14086459ce 5889 aspell-hr_0.51-5_amd64.buildinfo
Checksums-Sha256:
 f6dfd8d66388937671d48816663312e45f127ddd40de37aba99bb654cffd8117 2150 
aspell-hr_0.51-5.dsc
 2ac4030354d7961e45d63b46e06e59248d59cc70dfc9e1d8ee0ae21d9c774a25 208118 
aspell-hr_0.51.orig.tar.bz2
 f6964b8dc9f63b67b016251449fa3857e6af11bed2ad268b76012fc60444fa09 155 
aspell-hr_0.51.orig.tar.bz2.asc
 f6e058a3389921507a09d306ea8a83cb11a29afcbd99db1c517f9f47184a1c47 4188 
aspell-hr_0.51-5.debian.tar.xz
 64e18f2706b22841b71812b0

Bug#962596: Backport to stretch?

[Michael Simons (.NET)]

Hi Julien,



Thanks for pushing the changes to buster.  Will this get backported to stretch 
as well?  If so, what is the timeframe users can expect?



> I'm not sure why this is blowing up again this week



See https://github.com/NuGet/Announcements/issues/49 for details on how this 
affected .NET users building on Debian.

Thanks

Michael


On Thu, 28 Jan 2021 15:17:34 +0100 "Julien Cristau"  wrote:
> Hi,

>

> I'm not sure why this is blowing up again this week when things have

> been in a bit of a limbo state since June last year, but in any case

> I've just pushed a change to buster to try and revert the blacklisting

> of legacy Symantec CAs.  That should hopefully make it to the archive in

> the next few days.

>

> Cheers,

> Julien

Bug#981300: arduino-core-avr breaks arduino-mk

[Carsten Schoenert]

Hello Simon,

you need to add me to the recipients please, then I get the emails for
this report too. :)

Am Fri, Jan 29, 2021 at 12:22:18PM + schrieb Simon John:
> Hello Carsten,
> 
> i rebuilt arduino-mk and removed its Depends and it worked, so changing it
> to "arduino-core (>= 2:1.8.13+dfsg1-1)" would be the proper fix.

I need to correct myself a bit, please do not use the old package name
here, please use the real package. This would be this:

  arduino (>= 2:1.8.13+dfsg1-1

> the problem tends to be getting arduino-mk updated, think last time it
> needed a team upload (python3 fixes).

If you need help let me know, currently I can't that Python3 fixes you
mean.
If youe need a sponsor then I'm also willing to help.

Regards

Processed: Re: Bug#892275: redshift: Unable to connect to GeoClue.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 geoclue-2.0
Bug #892275 [redshift] redshift: Unable to connect to GeoClue.
Bug reassigned from package 'redshift' to 'geoclue-2.0'.
No longer marked as found in versions redshift/1.12-4, redshift/1.11-2, and 
redshift/1.11-1.
Ignoring request to alter fixed versions of bug #892275 to the same values 
previously set
> affects -1 redshift
Bug #892275 [geoclue-2.0] redshift: Unable to connect to GeoClue.
Added indication that 892275 affects redshift

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

Bug#892275: redshift: Unable to connect to GeoClue.

[nicoo]

Control: reassign -1 geoclue-2.0
Control: affects -1 redshift

Hi Gabriel, Mike, and Nicolas,

On Thu, Jan 07, 2021 at 09:14:46PM +, Mike Gabriel wrote:
> On  Do 07 Jan 2021 22:03:11 CET, Debian Bug Tracking System wrote:
> 
> > Package: redshift-gtk
> > Version: 1.12-4
> > Followup-For: Bug #892275
> > 
> > Dear Maintainer,
> > 
> > It seems that I have the same bug since today's reboot.
> > See the attached screenshot.
> > Moreover, I can't stop redshift. I close the window and it comes back.
> > I can't stop it, even killing it makes the fatal window come back again.
> > redshift uses 100% of a processor.
> > 
> > Yours,
> > n.
> 
> I can confirm this. After upgrading geoclue-2.0 from 2.5.6-1 to 2.5.7-2,
> gtk-redshift is broken (again).

Urg.  I'm really sorry you all were affected by this issue.

Could you check the following two things for me?

1. Does redshift work in “manual” mode, i.e. providing it with latitude and
   longitude?  That could be a workaround, as you can pass it `-l LAT:LON` on
   the command line, or set it in ~/.config/redshift.conf like so:

[redshift]
location-provider=manual

[manual]
lat=12.34
lon=56.78


2. Is the AppArmor profile denying any actions from redshift?
   You should be able to find the relevant logs in /var/log/audit.log
   if you install/enable auditd.

> For some days now, redshift is unusable, thus bumping severity to grave
> again. Also, the upstream activity of redshift is suboptimal. Many open PRs,
> last activity dates back to summer 2020. :-(

Yes.  I'm also pretty unimpressed with the size of d/patches by now.  >_>'

I'm hopeful, though, as upstream mentionned resuming maintaining maintainance
of it, so there might be an upswing in activity.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#981270: marked as done (chromium: FTBFS after libopenjp2-7-dev upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 18:34:15 +
with message-id 
and subject line Bug#981270: fixed in chromium 88.0.4324.96-2
has caused the Debian Bug report #981270,
regarding chromium: FTBFS after libopenjp2-7-dev upgrade
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.)


-- 
981270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 88.0.4324.96-1
Severity: normal
Tags: ftbfs patch
X-Debbugs-Cc: mic...@lebihan.pl

Chromium FTBFS on unstable. Please see: 
https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=88.0.4324.96-1&stamp=1611833918&raw=0

I'm currently testing this patch that should fix it: 
https://salsa.debian.org/mimi8/chromium/-/commit/47b68ef69c3ca028832025df2a3907685c6ff279

Michel Le Bihan

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
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 chromium depends on:
ii  chromium-common  88.0.4324.96-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-7
ii  libavformat587:4.3.1-7
ii  libavutil56  7:4.3.1-7
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op1-7
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.103-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.3-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.1-1
ii  libre2-9 20201101+dfsg-2
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-2.1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  88.0.4324.96-1

Versions of packages chromium suggests:
ii  chromium-driver  88.0.4324.96-1
ii  chromium-l10n88.0.4324.96-1
ii  chromium-shell   88.0.4324.96-1

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-2
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox   88.0.4324.96-1
ii  fonts-liberation   1:1.07.4-11
ii  gnome-shell [notification-daemon]  3.38.3-1
ii  libgl1-mesa-dri20.3.3-1
ii  libu2f-udev1.1.10-3
ii  notification-daemon3.20.0-4
ii  system-config-printer  1.5.14-1
ii  upower 0.99.11-2

chromium-dbgsym depends on no packages.

Versions of packages chromium-driver depends on:
ii  libatomic1  10.2.1-6
ii  libc6   2.31-9
ii  libevent-2.1-7  2.1.12-stable-1
ii  libglib2.0-02.66.4-1
ii  libicu6767.1-6
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.29-1
ii  libnss3 2:3.60-1
ii  libre2-920201101+dfsg-2
ii  libstdc++6  10.2.1-6
ii  libxcb1 1.14-2.1
ii  zlib1g 

Processed: severity of 981270 is serious

[Debian Bug Tracking System]

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

> severity 981270 serious
Bug #981270 [chromium] chromium: FTBFS after libopenjp2-7-dev upgrade
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#981579: sq: missing Breaks+Replaces: ispell (<< 3.4.00-6.1~)

[Andreas Beckmann]

Package: sq
Version: 0.24.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', 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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../archives/sq_0.24.0-2_amd64.deb ...
  Unpacking sq (0.24.0-2) ...
  dpkg: error processing archive /var/cache/apt/archives/sq_0.24.0-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/sq', which is also in package ispell 
3.4.00-6+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/sq_0.24.0-2_amd64.deb

ispell used to ship a sq binary, that was dropped in 3.4.00-6.1


cheers,

Andreas


ispell=3.4.00-6+b1_sq=0.24.0-2.log.gz
Description: application/gzip

Bug#981508: marked as done (mercurial autopkgtest breaks with newer git)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 17:26:11 +
with message-id 
and subject line Bug#980576: fixed in mercurial 5.6.1-2
has caused the Debian Bug report #980576,
regarding mercurial autopkgtest breaks with newer git
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.)


-- 
980576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: mercurial
version: 5.6.1-1
severity: serious

Hi,

The mercurial autopkgtest fails with the latest git:

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/10134722/log.gz

It seems the output of git changed in a way that the test didn't expect.

I suspect this will be fixed by this upstream change:

https://www.mercurial-scm.org/repo/hg/rev/88dfe1c279bb

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 5.6.1-2
Done: Julien Cristau 

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Feb 2021 17:47:09 +0100
Source: mercurial
Architecture: source
Version: 5.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julien Cristau 
Closes: 980576
Changes:
 mercurial (5.6.1-2) unstable; urgency=medium
 .
   * tests: make test-subrepo-git.t compatible with git's master->main
 rename (closes: #980576).
Checksums-Sha1:
 8038d3109103de86ed48e3b3a3ee10f1ff36ad1e 2709 mercurial_5.6.1-2.dsc
 4ef6fb6521b960430a9a0c330234c7ffda0199c1 64120 mercurial_5.6.1-2.debian.tar.xz
Checksums-Sha256:
 9dbef682e7c3e95ef7f4ffbb4af1ee48cef345c1855f661dbdc9ebdeca66c9bb 2709 
mercurial_5.6.1-2.dsc
 8e0dab6e154def53acb5b391396d80f8c5ae0e2bfda3620bae546d12f9869625 64120 
mercurial_5.6.1-2.debian.tar.xz
Files:
 8f0912914e630c6ccfc4beaa2d500702 2709 vcs optional mercurial_5.6.1-2.dsc
 af00a7727fa5daea7c8d1307f6aa1074 64120 vcs optional 
mercurial_5.6.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmAYMooUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z62COBAAkiHpr8S4fRbddV1IYZ5Xnwoz9w3Y
Uvb/fAREt1P5rM7dNBJWwC5O+9WhkqRqnbno9XCqoGkfJ6PMSqb8Gb6IRn9vjOSx
EzF3lCQoPW2xWtVe8capGelLpD9JgZo/2EvuthqOIoGXJUUQ2icnQZ4K3Yvzadb2
gYuF8jAwTJpJpGFtWrXYvJzgNpdh9KMtLppAt5hciWNQcGPICK8NLi9/sqqE4S5g
6h73RoDHYAC4v6lTJ7fmecvmSOK9ZyGXu7zMLA0hZBKilXJvTWYpsEqJOt//ZCp1
u52t22wwdOfJQj1+EJOFnTqO0VZiSG4w9FYnRhr62UamT1/z6Gb14I0FJaLnD7Hs
XhXdg1Ylp/FTF3gRp82DtYiuQn6nzJYPu8RMgVL7CnMDvN481PhSey9W1TSAL+uI
WtzNegfgKDxvwdrD2JzS4Cp9rhl6YRdo3X18FPyGAzZzs4Yrv4bRKzliyz/o/SYA
S6F/hEXikQm8drkvTl17LgC1Dy3+1osSVb19ZaJm4pdXYaGKSivSUmfpP+bCE2R9
vfNOfjDtKNTC+XkMeXq9ncFN2pRVDhAESYiQjb0XE6veiagJivaAFH6/8gspoU1R
71AwziGZlLaTlqtzkHH1YTLejEPQkp9r0xB3WNwOiU0WCFiu7buAJUPgoWECOQcs
gFN4ePQaso7wEPQ=
=Fqd9
-END PGP SIGNATURE End Message ---

Bug#980576: marked as done (mercurial: autopkgtest needs update for new version of git)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 17:26:11 +
with message-id 
and subject line Bug#980576: fixed in mercurial 5.6.1-2
has caused the Debian Bug report #980576,
regarding mercurial: autopkgtest needs update for new version of git
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.)


-- 
980576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 5.5.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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

   passfail
gitfrom testing1:2.30.0-1
mercurial  from testing5.5.2-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 git to testing
[1]. Of course, git shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in git was
intended and your package needs to update to the new situation.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/9857175/log.gz

est-http-permissions.t
test-http-permissions.t ... # Test test-http-permissions.t
# Running sh "/tmp/hgtests.k6wnhqr_/child113/test-http-permissions.t.sh"

---
/tmp/autopkgtest-lxc.k1drd64q/downtmp/build.mL2/src/tests/test-convert-git.t
+++
/tmp/autopkgtest-lxc.k1drd64q/downtmp/build.mL2/src/tests/test-convert-git.t.err
@@ -680,6 +680,16 @@
   $ mkdir git-testrevs
   $ cd git-testrevs
   $ git init
+  hint: Using 'master' as the name for the initial branch. This default
branch name
+  hint: is subject to change. To configure the initial branch name to
use in all
+  hint: of your new repositories, which will suppress this warning, call:
+  hint:
+  hint:git config --global init.defaultBranch 
+  hint:
+  hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
+  hint: 'development'. The just-created branch can be renamed via this
command:
+  hint:
+  hint:git branch -m 
   Initialized empty Git repository in $TESTTMP/git-testrevs/.git/
   $ echo a >> a ; git add a > /dev/null; git commit -m 'first' > /dev/null
   $ echo a >> a ; git add a > /dev/null; git commit -m 'master commit'
> /dev/null
@@ -882,6 +892,16 @@

 convert using a different remote prefix
   $ git init git-repo7
+  hint: Using 'master' as the name for the initial branch. This default
branch name
+  hint: is subject to change. To configure the initial branch name to
use in all
+  hint: of your new repositories, which will suppress this warning, call:
+  hint:
+  hint:git config --global init.defaultBranch 
+  hint:
+  hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
+  hint: 'development'. The just-created branch can be renamed via this
command:
+  hint:
+  hint:git branch -m 
   Initialized empty Git repository in $TESTTMP/git-repo7/.git/
   $ cd git-repo7
 TODO: it'd be nice to use (?) lines instead of grep -v to handle the
@@ -957,6 +977,16 @@
 test for escaping the repo name (CVE-2016-3069)

   $ git init '`echo pwned >COMMAND-INJECTION`'
+  hint: Using 'master' as the name for the initial branch. This default
branch name
+  hint: is subject to change. To configure the initial branch name to
use in all
+  hint: of your new repositories, which will suppress this warning, call:
+  hint:
+  hint:git config --global init.defaultBranch 
+  hint:
+  hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
+  hint: 'development'. The just-created branch can be renamed via this
command:
+  hint:
+  hint:git branch -m 
   Ini

Processed: [bts-link] source package sopel

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package sopel
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #943405 (http://bugs.debian.org/943405)
> # Bug title: unsuitable for release: no upstream patch releases
> #  * https://github.com/sopel-irc/sopel/issues/2022
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 943405 + fixed-upstream
Bug #943405 [sopel] unsuitable for release: no upstream patch releases
Added tag(s) fixed-upstream.
> usertags 943405 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#981576: ghdl-common: missing Breaks+Replaces: ghdl (<< 0.37+dfsg2)

[Andreas Beckmann]

Package: ghdl-common
Version: 0.37+dfsg2-1
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 .../ghdl-common_0.37+dfsg2-1_amd64.deb ...
  Unpacking ghdl-common (0.37+dfsg2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ghdl-common_0.37+dfsg2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ghdl', which is also in package ghdl:amd64 
0.37+dfsg-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ghdl-common_0.37+dfsg2-1_amd64.deb

BTW, did you really intend to move /usr/bin/ghdl to the -common package?
That's rather unusual.
(But you need the B+R also for splitting out the /usr/lib bits to -common.)


cheers,

Andreas


ghdl=0.37+dfsg-3_ghdl-common=0.37+dfsg2-1.log.gz
Description: application/gzip

Processed: Bug#980576 marked as pending in mercurial

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version 
of git
Bug #981508 [src:mercurial] mercurial autopkgtest breaks with newer git
Added tag(s) pending.
Added tag(s) pending.

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

Bug#980576: marked as pending in mercurial

[Julien Cristau]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/mercurial/-/commit/b844a5fc220777af4894e0ba0eb1808d7a599ddf


tests: make test-subrepo-git.t compatible with git's master->main rename 
(closes: #980576).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980576

Processed: reassign 981508 to src:mercurial, forcibly merging 980576 981508

[Debian Bug Tracking System]

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

> reassign 981508 src:mercurial
Bug #981508 [mercurial] mercurial autopkgtest breaks with newer git
Bug reassigned from package 'mercurial' to 'src:mercurial'.
No longer marked as found in versions mercurial/5.6.1-1.
Ignoring request to alter fixed versions of bug #981508 to the same values 
previously set
> forcemerge 980576 981508
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version 
of git
Bug #981508 [src:mercurial] mercurial autopkgtest breaks with newer git
Added indication that 981508 affects src:git
Marked as found in versions mercurial/5.6.1-1 and mercurial/5.5.2-1.
Added tag(s) fixed-upstream, sid, patch, bullseye, and upstream.
Merged 980576 981508
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 980576 981508

[Debian Bug Tracking System]

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

> forcemerge 980576 981508
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version 
of git
Unable to merge bugs because:
package of #981508 is 'mercurial' not 'src:mercurial'
Failed to forcibly merge 980576: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: Bug#980576: mercurial: autopkgtest needs update for new version of git

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream fixed-upstream patch
Bug #980576 [src:mercurial] mercurial: autopkgtest needs update for new version 
of git
Added tag(s) fixed-upstream, patch, and upstream.

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

Bug#980576: mercurial: autopkgtest needs update for new version of git

[Julien Cristau]

Control: tag -1 upstream fixed-upstream patch

On Mon, Feb 01, 2021 at 05:42:04PM +0100, Julien Cristau wrote:
> On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> > Package: mercurial
> > Version: 5.6.1-1
> > Followup-For: Bug #980576
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu hirsute ubuntu-patch
> > 
> > Dear maintainers,
> > 
> > Attached is a patch that makes the mercurial test suite compatible with both
> > the old and new git behavior.  It has been uploaded to Ubuntu.  Please
> > consider applying in Debian as well.
> > 
> Hi Steve,
> 
> is this actually still an issue?
> https://www.mercurial-scm.org/repo/hg/rev/366c547a8a57 is in 5.6 and
> should address this, as far as I can tell.
> 
Nevermind, I see https://www.mercurial-scm.org/repo/hg/rev/88dfe1c279bb
is also needed and is not in the release, so I'll cherry-pick that.

Cheers,
Julien

Bug#980576: mercurial: autopkgtest needs update for new version of git

[Julien Cristau]

On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> Package: mercurial
> Version: 5.6.1-1
> Followup-For: Bug #980576
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu hirsute ubuntu-patch
> 
> Dear maintainers,
> 
> Attached is a patch that makes the mercurial test suite compatible with both
> the old and new git behavior.  It has been uploaded to Ubuntu.  Please
> consider applying in Debian as well.
> 
Hi Steve,

is this actually still an issue?
https://www.mercurial-scm.org/repo/hg/rev/366c547a8a57 is in 5.6 and
should address this, as far as I can tell.

Thanks,
Julien

> diff -Nru mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch 
> mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch
> --- mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch   
> 1969-12-31 16:00:00.0 -0800
> +++ mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch   
> 2021-01-30 17:04:28.0 -0800
> @@ -0,0 +1,33 @@
> +Description: make test cases compatible with git 2.30.0
> + New git upstream includes an additional warning when calling 'git init'
> + if you do not first set init.defaultBranch in your config.  Make the test
> + case compatible with both old and new git by setting init.defaultBranch
> + before calling git init.
> +Author: Steve Langasek 
> +Last-Update: 2021-01-30
> +Bug-Debian: https://bugs.debian.org/980576
> +
> +Index: mercurial-5.6.1/tests/test-convert-git.t
> +===
> +--- mercurial-5.6.1.orig/tests/test-convert-git.t
>  mercurial-5.6.1/tests/test-convert-git.t
> +@@ -677,6 +677,7 @@
> + 
> +   $ mkdir git-testrevs
> +   $ cd git-testrevs
> ++  $ git config --global init.defaultBranch master
> +   $ git init
> +   Initialized empty Git repository in $TESTTMP/git-testrevs/.git/
> +   $ echo a >> a ; git add a > /dev/null; git commit -m 'first' > /dev/null
> +Index: mercurial-5.6.1/tests/test-subrepo-git.t
> +===
> +--- mercurial-5.6.1.orig/tests/test-subrepo-git.t
>  mercurial-5.6.1/tests/test-subrepo-git.t
> +@@ -1199,6 +1199,7 @@
> +   $ hg init malicious-subrepository
> +   $ cd malicious-subrepository
> +   $ echo "s = [git]ext::sh -c echo% pwned:% \$PWNED_MSG% >pwned.txt" > 
> .hgsub
> ++  $ git config --global init.defaultBranch master
> +   $ git init s
> +   Initialized empty Git repository in 
> $TESTTMP/tc/malicious-subrepository/s/.git/
> +   $ cd s
> diff -Nru mercurial-5.6.1/debian/patches/series 
> mercurial-5.6.1/debian/patches/series
> --- mercurial-5.6.1/debian/patches/series 2021-01-08 07:02:06.0 
> -0800
> +++ mercurial-5.6.1/debian/patches/series 2021-01-30 14:48:59.0 
> -0800
> @@ -3,3 +3,4 @@
>  deb_specific__optional-dependencies
>  deb_specific__disable_libdir_replacement.patch
>  0005-Tolerate-SIGINT-getting-the-kill-in-test-stdio.py.patch
> +git-2.30.0-test-compat.patch

Bug#980602: marked as done (libxcb: FTBFS: ../../tests/check_public.c:40:24: error: too many arguments for format [-Werror=format-extra-args])

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 16:37:28 +
with message-id 
and subject line Bug#980602: fixed in libxcb 1.14-3
has caused the Debian Bug report #980602,
regarding libxcb: FTBFS: ../../tests/check_public.c:40:24: error: too many 
arguments for format [-Werror=format-extra-args]
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.)


-- 
980602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxcb
Version: 1.14-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../tests -I../src   -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Werror -pthread -I../../src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o check_public.o ../../tests/check_public.c
> In file included from ../../tests/check_public.c:1:
> ../../tests/check_public.c: In function ‘parse_display_pass’:
> ../../tests/check_public.c:40:24: error: too many arguments for format 
> [-Werror=format-extra-args]
>40 |   fail_unless(success, "unexpected parse failure %sfor '%s'", 
> test_string[test_type], name);
>   |^
> ../../tests/check_public.c:41:44: error: too many arguments for format 
> [-Werror=format-extra-args]
>41 |   fail_unless(strcmp(host, got_host) == 0, "parse %sproduced 
> unexpected hostname '%s' for '%s': expected '%s'", test_string[test_type], 
> got_host, name, host);
>   |
> ^~~
> ../../tests/check_public.c:42:39: error: too many arguments for format 
> [-Werror=format-extra-args]
>42 |   fail_unless(display == got_display, "parse %sproduced unexpected 
> display '%d' for '%s': expected '%d'", test_string[test_type], got_display, 
> name, display);
>   |   
> ^~
> ../../tests/check_public.c:43:37: error: too many arguments for format 
> [-Werror=format-extra-args]
>43 |   fail_unless(screen == got_screen, "parse %sproduced unexpected 
> screen '%d' for '%s': expected '%d'", test_string[test_type], got_screen, 
> name, screen);
>   | 
> ^
> ../../tests/check_public.c:49:24: error: too many arguments for format 
> [-Werror=format-extra-args]
>49 |   fail_unless(success, "unexpected screenless parse failure %sfor 
> '%s'", test_string[test_type], name);
>   |
> ^~~~
> ../../tests/check_public.c:50:44: error: too many arguments for format 
> [-Werror=format-extra-args]
>50 |   fail_unless(strcmp(host, got_host) == 0, "screenless parse 
> %sproduced unexpected hostname '%s' for '%s': expected '%s'", 
> test_string[test_type], got_host, name, host);
>   |
> ^~
> ../../tests/check_public.c:51:39: error: too many arguments for format 
> [-Werror=format-extra-args]
>51 |   fail_unless(display == got_display, "screenless parse %sproduced 
> unexpected display '%d' for '%s': expected '%d'", test_string[test_type], 
> got_display, name, display);
>   |   
> ^
> ../../tests/check_public.c: In function ‘parse_display_fail’:
> ../../tests/check_public.c:82:25: error: too many arguments for format 
> [-Werror=format-extra-args]
>82 |   fail_unless(!success, "unexpected parse success %sfor '%s'", 
> test_string[test_type], name);
>   | ^
> ../../tests/check_public.c:83:40: error: too many arguments for format 
> [-Werror=format-extra-args]
>83 |   fail_unless(got_host == (char *) -1, "host changed on parse failure 
> %sfor '%s': got %p", test_string[test_type], name, got_host);
>   |
> ^~
> ../../tests/check_public.c:84:35: error: too many arguments for format 
> [-Werror=format-extra-args]
>84 |   fail_unless(got_display == -42, "display chan

Bug#980202: marked as done (FTBFS: gscan2pdf tests fail)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 16:36:58 +
with message-id 
and subject line Bug#980202: fixed in imagemagick 8:6.9.11.60+dfsg-1
has caused the Debian Bug report #980202,
regarding FTBFS: gscan2pdf 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.)


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

While trying to rebuild gscan2pdf on a clean amd64 schroot using sbuild,
I found this FTBFS:

--8<---cut here---start->8---
ok 27 - POD test for blib/script/gscan2pdf
ok

Test Summary Report
---
t/1122_save_pdf_with_hocr.t (Wstat: 512 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
t/113_save_pdf_with_downsample.t(Wstat: 512 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
t/134_save_tiff_alpha.t (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=242, Tests=1168, 276 wallclock secs ( 0.48 usr  0.18 sys + 108.21 cusr 
19.84 csys = 128.71 CPU)
Result: FAIL
Failed 3/242 test programs. 5/1168 subtests failed.
make[2]: *** [Makefile:912: test_dynamic] Error 255
make[2]: Leaving directory '/<>'
dh_auto_test: error: make -j32 test TEST_VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:3: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Build finished at 2021-01-16T00:02:23Z

Finished



+--+
| Cleanup  |
+--+

Purging /<>
Not cleaning session: cloned chroot in use
E: Build failure (dpkg-buildpackage died)
--8<---cut here---end--->8---

I tried running the build twice, and both attempts failed with the same
reason.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.11.60+dfsg-1
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Feb 2021 16:22:02 +
Source: imagemagick
Architecture: source
Version: 8:6.9.11.60+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 980202
Changes:
 imagemagick (8:6.9.11.60+dfsg-1) unstable; urgency=high
 .
   * New upstream version
 - Bug fix: "gscan2pdf tests fail", thanks to Sergio Durigan Junior
   (Closes: #980202).
Checksums-Sha1:
 968f4558b041b813f9ac22f6511f01adf897a805 5079 imagemagick_6.9.11.60+dfsg-1.dsc
 824a63dce5e54bd8b78077d671d8ab06300a8848 9395144 
imagemagick_6.9.11.60+dfsg.orig.tar.xz
 e43c74a0710bb2d9de20720d0ee56664a3d1bc61 246212 
imagemagick_6.9.11.60+dfsg-1.debian.tar.xz
 3f415e9b57e6fb568ff6eacbcb13e7b61d0888ce 11984 
imagemagick_6.9.11.60+dfsg-1_source.buildinfo
Checksums-Sha256:
 25eb169738164121542d38c704d8d4b189ffe31a9fb35a65d866461ce691f865 5079 
imagemagick_6.9.11.60+dfsg-1.dsc
 472fb516df842ee9c819ed80099c188463b9e961303511c36ae24d0eaa8959c4 9395144 
imagemagick_6.9.11.60+dfsg.orig.tar.xz
 7bfa63be4e9b8bd62f726a869dcf86325eae8d203759324569e2c403fbeb 246212 
imagemagick_6.9.11.60+dfsg-1.debian.tar.xz
 fefef1b471d5428cf6b4bf5b0ce4eb880d62407f653c23e7e5b01f2a

Bug#980189: marked as done (flask-security: CVE-2021-21241)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 16:34:34 +
with message-id 
and subject line Bug#980189: fixed in flask-security 4.0.0-1
has caused the Debian Bug report #980189,
regarding flask-security: CVE-2021-21241
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.)


-- 
980189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-security
Version: 3.4.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Flask-Middleware/flask-security/issues/421
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for flask-security.

CVE-2021-21241[0]:
| The Python "Flask-Security-Too" package is used for adding security
| features to your Flask application. It is an is a independently
| maintained version of Flask-Security based on the 3.0.0 version of
| Flask-Security. In Flask-Security-Too from version 3.3.0 and before
| version 3.4.5, the /login and /change endpoints can return the
| authenticated user's authentication token in response to a GET
| request. Since GET requests aren't protected with a CSRF token, this
| could lead to a malicious 3rd party site acquiring the authentication
| token. Version 3.4.5 and version 4.0.0 are patched. As a workaround,
| if you aren't using authentication tokens - you can set the
| SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token
| unusable.

Admitelly the CVE description currently on MITRE is quite confusing
reffering to Flask-Security-Too package. But the other references
pointed out and reviewing the changes seem to apply to the original
project as well (I might miss something here).


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-2021-21241
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21241
[1] 
https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-hh7m-rx4f-4vpv
[2] https://github.com/Flask-Middleware/flask-security/pull/422
[3] 
https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f
[4] https://github.com/Flask-Middleware/flask-security/issues/421

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: flask-security
Source-Version: 4.0.0-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated flask-security package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Feb 2021 15:42:21 +0100
Source: flask-security
Architecture: source
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christoph Berg 
Closes: 980189
Changes:
 flask-security (4.0.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Christoph Berg ]
   * New upstream version 4.0.0.
 + Fixes /login and /change vulnerability. (Closes: 980189, CVE-2021-21241)
Checksums-Sha1:
 38a0940a39aabc21877741b6c55c3ca86aa5bde5 2420 flask-security_4.0.0-1.dsc
 9909af684fc85923ff5a7298a9437b0dd0c78995 407928 
flask-security_4.0.0.orig.tar.gz
 d4a2a75c7a2ce359053d3d37b3a4ff1970889bb5 3128 
flask-security_4.0.0-1.debian.tar.xz
Checksums-Sha256:
 1c9567749276f72ece1b9f5683c55b827acf1d51337c26577030a5d30db99836 2420 
flask-security_4.0.0-1.dsc
 4aa0a076fe0faabf01017d727e81fce0800170ce1cbf01534d16549fa6464d87 407928 
flask-security_4.0.0.orig.tar.gz
 0aa14ba46c02ebfb3

Bug#980603: [3dprinter-general] Bug#980603: cura: FTBFS: cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module 'PyQt5.QtCore' has no attribute 'pyqtProperty'

[Christoph Berg]

Re: Gregor Riepl
> If this is true and the failures are really only code style issues, I
> would suggest to silence the unit test and be done with it.
> 
> But it does look a bit more serious from the error messages.

Well if it's really *that* serious I'd expect cura not to start.

> Here's a patch, feel free to release if you agree:
> https://salsa.debian.org/3dprinting-team/cura/-/commit/03fde269efaced553a7c4e74846e2554dd2f6bcf
> 
> (or revert it, if you think we should rather wait for upstream)

Time for bullseye is running out, so I uploaded it now.

Christoph

Processed: Re: Bug#948739: gparted should not mask .mount units

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #948739 {Done: Phillip Susi } [gparted] gparted should 
not mask .mount units
'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 gparted/1.2.0-1.

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

Bug#948739: gparted should not mask .mount units

[Phillip Susi]

Control: reopen -1

Ivo De Decker writes:

> This new upstream version doesn't remove the code masking the systemd units.
> It just changes it a little. So it doesn't fix this bug.

Woops... you're right.

Bug#962596: Backport to stretch?

[Julien Cristau]

Hi Michael,

stretch is EOL, so I am not planning on touching it myself.

Cc:ing the team that looks after stretch-lts in case they want to handle
this.

Cheers,
Julien

On Mon, Feb 01, 2021 at 03:14:38PM +, Michael Simons (.NET) wrote:
> Hi Julien,
> 
>  
> 
> Thanks for pushing the changes to buster.  Will this get backported to stretch
> as well?  If so, what is the timeframe users can expect?
> 
>  
> 
> > I'm not sure why this is blowing up again this week
> 
>  
> 
> See https://github.com/NuGet/Announcements/issues/49 for details on how this
> affected .NET users building on Debian.
> 
> Thanks
> 
> Michael
> 
> 
> On Thu, 28 Jan 2021 15:17:34 +0100 “Julien Cristau" 
> wrote:
> > Hi,
> 
> > 
> 
> > I'm not sure why this is blowing up again this week when things have
> 
> > been in a bit of a limbo state since June last year, but in any case
> 
> > I've just pushed a change to buster to try and revert the blacklisting
> 
> > of legacy Symantec CAs.  That should hopefully make it to the archive in
> 
> > the next few days.
> 
> > 
> 
> > Cheers,
> 
> > Julien
> 

Bug#980576: mercurial: autopkgtest needs update for new version of git

[Steve Langasek]

Package: mercurial
Version: 5.6.1-1
Followup-For: Bug #980576
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear maintainers,

Attached is a patch that makes the mercurial test suite compatible with both
the old and new git behavior.  It has been uploaded to Ubuntu.  Please
consider applying in Debian as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch 
mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch
--- mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch 1969-12-31 
16:00:00.0 -0800
+++ mercurial-5.6.1/debian/patches/git-2.30.0-test-compat.patch 2021-01-30 
17:04:28.0 -0800
@@ -0,0 +1,33 @@
+Description: make test cases compatible with git 2.30.0
+ New git upstream includes an additional warning when calling 'git init'
+ if you do not first set init.defaultBranch in your config.  Make the test
+ case compatible with both old and new git by setting init.defaultBranch
+ before calling git init.
+Author: Steve Langasek 
+Last-Update: 2021-01-30
+Bug-Debian: https://bugs.debian.org/980576
+
+Index: mercurial-5.6.1/tests/test-convert-git.t
+===
+--- mercurial-5.6.1.orig/tests/test-convert-git.t
 mercurial-5.6.1/tests/test-convert-git.t
+@@ -677,6 +677,7 @@
+ 
+   $ mkdir git-testrevs
+   $ cd git-testrevs
++  $ git config --global init.defaultBranch master
+   $ git init
+   Initialized empty Git repository in $TESTTMP/git-testrevs/.git/
+   $ echo a >> a ; git add a > /dev/null; git commit -m 'first' > /dev/null
+Index: mercurial-5.6.1/tests/test-subrepo-git.t
+===
+--- mercurial-5.6.1.orig/tests/test-subrepo-git.t
 mercurial-5.6.1/tests/test-subrepo-git.t
+@@ -1199,6 +1199,7 @@
+   $ hg init malicious-subrepository
+   $ cd malicious-subrepository
+   $ echo "s = [git]ext::sh -c echo% pwned:% \$PWNED_MSG% >pwned.txt" > .hgsub
++  $ git config --global init.defaultBranch master
+   $ git init s
+   Initialized empty Git repository in 
$TESTTMP/tc/malicious-subrepository/s/.git/
+   $ cd s
diff -Nru mercurial-5.6.1/debian/patches/series 
mercurial-5.6.1/debian/patches/series
--- mercurial-5.6.1/debian/patches/series   2021-01-08 07:02:06.0 
-0800
+++ mercurial-5.6.1/debian/patches/series   2021-01-30 14:48:59.0 
-0800
@@ -3,3 +3,4 @@
 deb_specific__optional-dependencies
 deb_specific__disable_libdir_replacement.patch
 0005-Tolerate-SIGINT-getting-the-kill-in-test-stdio.py.patch
+git-2.30.0-test-compat.patch

Bug#976735: spyder needs source upload for Python 3.9 transition

[Nilesh Patra]

Hi Julian

I read through the rest of the thread.

On Mon, 1 Feb, 2021, 6:31 pm Julian Gilbey,  wrote:

> I have a package of Spyder 4 waiting to upload, but it requires five
> packages to be accepted into unstable from NEW first (pyls-server,
> pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
> rest of the packages are almost ready to

go.


I requested on IRC (probably again after you) to process these ASAP,
however I don't see pyls-server in NEW or at the archive yet.

Has this been rejected, or am I missing something?

Nilesh

>
>

Processed: severity of 981278 is important, tagging 981278

[Debian Bug Tracking System]

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

> severity 981278 important
Bug #981278 [subdownloader] subdownloader: Crashes when trying to download 
subtitle
Severity set to 'important' from 'grave'
> tags 981278 + confirmed
Bug #981278 [subdownloader] subdownloader: Crashes when trying to download 
subtitle
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#948739: marked as done (gparted should not mask .mount units)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 15:20:46 +
with message-id 
and subject line Bug#948739: fixed in gparted 1.2.0-1
has caused the Debian Bug report #948739,
regarding gparted should not mask .mount units
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.)


-- 
948739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:8.1p1-5
Severity: serious

Dear Maintainer,

Fail to upgrade with this error :

Setting up openssh-server (1:8.1p1-5) ...
rescue-ssh.target is a disabled or a static unit, not starting it.
Failed to restart ssh.service: Unit -.mount is masked.
invoke-rc.d: initscript ssh, action "restart" failed.
* ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Sat 2020-01-11 08:26:51 CET; 1 day 6h ago
   Docs: man:sshd(8)
 man:sshd_config(5)
   Main PID: 1119 (sshd)
 Memory: 3.7M
 CGroup: /system.slice/ssh.service
 `-1119 /usr/sbin/sshd -D

Christian

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

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

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  libaudit1  1:2.8.5-2+b1
ii  libc6  2.29-9
ii  libcom-err21.45.5-2
ii  libcrypt1  1:4.4.10-10
ii  libgssapi-krb5-2   1.17-6
ii  libkrb5-3  1.17-6
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux13.0-1
ii  libssl1.1  1.1.1d-2
ii  libsystemd0244-3
ii  libwrap0   7.6.q-30
ii  lsb-base   11.1.0
ii  openssh-client 1:8.1p1-5
ii  openssh-sftp-server1:8.1p1-5
ii  procps 2:3.3.15-2+b1
ii  runit-helper   2.8.14
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  244-3
ii  ncurses-term 6.1+20191019-1
ii  xauth1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  ssh-askpass   
pn  ufw   

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: gparted
Source-Version: 1.2.0-1
Done: Phillip Susi 

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

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

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

Debian distribution maintenance software
pp.
Phillip Susi  (supplier of updated gparted 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, 29 Jan 2021 15:34:55 -0500
Source: gparted
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Phillip Susi 
Changed-By: Phillip Susi 
Closes: 948739 950425
Changes:
 gparted (1.2.0-1) unstable; urgency=medium
 .
   [ nicoo ]
   * d/changelog: Update my name
 .
   [ Phillip Susi ]
   * New upstream version 1.2.0
 + Closes: #948739, #950425
   * Drop Reliably-detect-running-gpartedbin-using-pidof-54.patch
   * Update my email
Checksums-Sha1:
 e30e982d03ec23a10bf79619d038653254994c7d 1897 gparted_1.2.0-1.dsc
 61dbe956e6edbd489aad9bdb80f69b40b4f404a8 4057490 gparted_1.2.0.orig.tar.gz
 69fab34e2980175fbc27ca0ec9941d6186f381ed 488 gparted_1.2.0.orig.tar.gz.asc
 a572e20d139582ecaec0f11fcd74a1f76775211c 14788 gparted_1.2.0-1.debian.tar.xz
 97a9787b21071f7987ed92972d911fb2ff1e5ba2 15316 gparted_1.2.0-1_source.buildinfo
Checksums-Sha256:
 badc

Bug#973082: confirmed

[stefanor]

Hi Hans-Christoph (2021.02.01_10:27:12_+)
> Do the tests pass with this patch?

Yes.

SR

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

Processed: retitle 981420 to libglib2.0-0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.66.4-2 ...

[Debian Bug Tracking System]

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

> retitle 981420 libglib2.0-0: gnome-keyring unable to unlock login keyring on 
> some systems since GLib 2.66.4-2
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring
Changed Bug title to 'libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2' from 'libglib2.0-0: gnome-keyring 
unable to unlock login keyring'.
> affects 981420 + gnome-keyring
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Added indication that 981420 affects gnome-keyring
> thanks
Stopping processing here.

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

Processed: tagging 977779

[Debian Bug Tracking System]

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

> tags 99 + pending
Bug #99 [src:webkit2gtk] geary FTBFS on mipsel: test suite failure
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#976735: spyder needs source upload for Python 3.9 transition

[Julian Gilbey]

On Mon, Feb 01, 2021 at 01:34:46PM +, PICCA Frederic-Emmanuel wrote:
> > I have a package of Spyder 4 waiting to upload, but it requires five
> > packages to be accepted into unstable from NEW first (pyls-server,
> > pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
> > rest of the packages are almost ready to go.
> 
> Maybe you can contact the ftpmaster team and request a review of these 
> packages.
> 
> In order to avoid the spyder removal.
> 
> Cheers

Strangely enough, I've already done that ;-)

   Julian

Bug#976735: spyder needs source upload for Python 3.9 transition

[PICCA Frederic-Emmanuel]

> Strangely enough, I've already done that ;-)

my bad.

Cheers

Fred

Processed: found 980338 in 0.4.0-15.1, found 980348 in 0.1.3-5.1

[Debian Bug Tracking System]

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

> found 980338 0.4.0-15.1
Bug #980338 [src:hotswap] hotswap: should ship with bullseye?
Marked as found in versions hotswap/0.4.0-15.1.
> found 980348 0.1.3-5.1
Bug #980348 [src:ruby-wirble] ruby-wirble: ship with bullseye?
Marked as found in versions ruby-wirble/0.1.3-5.1.
> thanks
Stopping processing here.

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

Bug#976735: spyder needs source upload for Python 3.9 transition

[PICCA Frederic-Emmanuel]

> I have a package of Spyder 4 waiting to upload, but it requires five
> packages to be accepted into unstable from NEW first (pyls-server,
> pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
> rest of the packages are almost ready to go.

Maybe you can contact the ftpmaster team and request a review of these packages.

In order to avoid the spyder removal.

Cheers

Bug#976735: spyder needs source upload for Python 3.9 transition

[Julian Gilbey]

On Mon, Feb 01, 2021 at 04:21:15PM +0530, Nilesh Patra wrote:
> Hi Julian,
> 
> On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey  wrote:
> > On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > > Package: spyder
> > > Version: 3.3.6+dfsg1-5
> > > Severity: serious
> > >
> > > Since binNMUs are not possible for binary-all packages,
> > > a source upload is needed for the Python 3.9 transition.
> > >
> > > In a more general note, does /usr/bin/spyder3 have to use
> > > the versioned interpreter instead of python3?
> >
> > The versioned interpreter can be avoided by removing '{interpreter} '
> > from the definition of PYBUILD_AFTER_INSTALL in debian/rules.
> 
> Please consider to apply the fix if it works, also for #976966
> Since freeze is near, it would be unfortunate to loose spyder and spyder-* 
> packages in bullseye.
> 
> Nilesh

Hi Nilesh,

I tried it, but it turns out that the problem is much more serious
than this: all that this patch did was to highlight the other issues.
(See the other bug reports on python3-spyder.)

I have a package of Spyder 4 waiting to upload, but it requires five
packages to be accepted into unstable from NEW first (pyls-server,
pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
rest of the packages are almost ready to go.

I, too, hope that we can get them in before the freeze.

Best wishes,

   Julian

Bug#981562: marked as done (python-django: CVE-2021-3281)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 12:18:55 +
with message-id 
and subject line Bug#981562: fixed in python-django 2:2.2.18-1
has caused the Debian Bug report #981562,
regarding python-django: CVE-2021-3281
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.)


-- 
981562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1.7.11-1+deb8u10
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django:

CVE-2021-3281[0]

   https://www.djangoproject.com/weblog/2021/feb/01/security-releases/

At a first glance, all of jessie, stretch, buster, bullseye, sid and
experimental are vulnerable.

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-2021-3281
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3281


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.18-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Feb 2021 11:59:58 +
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:2.2.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Closes: 981562
Changes:
 python-django (2:2.2.18-1) unstable; urgency=medium
 .
   * New upstream security release:
 .
 - CVE-2021-3281: Potential directory-traversal via archive.extract().
 .
   The django.utils.archive.extract() function, used by startapp --template
   and startproject --template, allowed directory-traversal via an archive
   with absolute paths or relative paths with dot segments.
   (Closes: #981562)
 .
 
 .
   * Drop 0006-Fixed-31850-Fixed-BasicExtractorTests.test_extractio.patch;
 applied upstream.
Checksums-Sha1:
 5be0eab5bc2ea4687d6b39aecc90c422fc985c9a 2779 python-django_2.2.18-1.dsc
 b0f4d5e684f70717113d79dfe44c5d8bf88a826a 9180844 
python-django_2.2.18.orig.tar.gz
 62f00a124fc13312879d0440e4d1b662e947cb64 26532 
python-django_2.2.18-1.debian.tar.xz
 1a2e627e3e76e8484c5024bb33c6ca1a0dd00e33 7781 
python-django_2.2.18-1_amd64.buildinfo
Checksums-Sha256:
 95cb504064636be4757c71bd85b63bf43f8971136e8210fd705efa732307318c 2779 
python-django_2.2.18-1.dsc
 c9c994f5e0a032cbd45089798b52e4080f4dea7241c58e3e0636c54146480bb4 9180844 
python-django_2.2.18.orig.tar.gz
 a30ad38ea067f0f078c709d880aa1ca88c286e2351be84c8fcb290fc028c6fb7 26532 
python-django_2.2.18-1.debian.tar.xz
 b523ac0c6aa7c8e2a815e99a197845ffd8fb1112510589d7cda03020e8bdf0eb 7781 
python-django_2.2.18-1_amd64.buildinfo
Files:
 4e8cdb6b09b605433932812c5d00388b 2779 python optional 
python-django_2.2.18-1.dsc
 c6cf78dae9c0be5833d37be73ab63962 9180844 python optional 
python-django_2.2.18.orig.tar.gz
 0cd02934c79fc5288ed8cf26549fdd14 26532 python optional 
python-django_2.2.18-1.debian.tar.xz
 149a421f5312aca844e89be20ae042af 7781 python optional 
python-django_2.2.18-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmAX7i8ACgkQHpU+J9Qx
Hlis/g/+OxiRxNkPBruvpzT8OvrQ4MBCKLwbgF+RAd/X7c9ALWM+zENibd+KAuC8
wJSClxXCKdhy2+iD2sl+JRWJLjIwa6K0sbOLcqEKmCdSUmSQHt00/DX62HHuoaqA
z6UkFwrbeQNdy5pO3AxcjJ4hlGeA215VV/LW92cBaJ4HT21RhZiwdEs7tb2WZCZ2
HVkDfQNuD4daoWI62JIDEWFW29Tjvwdo+y/7gTZJL6YjadVDjz5zrLoqOIl0dR5t
bMYe+Oxe1ieJJUdm0WAuk24/wN7lN6Lw7Z5JdwzLNaP13U8TwEvwowZUU/eQZ9aE
FOnkr/OddE+1m3NI5pKckCQ3JVwmxy7AJ+Jo79JVemV7KsU+zmMst2EauiL8p6Ts
sBgV1F5qaSOD1at/z15

Processed: found 981562 in 2:2.2.17-2

[Debian Bug Tracking System]

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

> found 981562 2:2.2.17-2
Bug #981562 [python-django] python-django: CVE-2021-3281
There is no source info for the package 'python-django' at version '2:2.2.17-2' 
with architecture ''
Unable to make a source version for version '2:2.2.17-2'
Marked as found in versions 2:2.2.17-2.
> thanks
Stopping processing here.

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

Bug#981562: python-django: CVE-2021-3281

[Chris Lamb]

Package: python-django
Version: 1.7.11-1+deb8u10
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django:

CVE-2021-3281[0]

   https://www.djangoproject.com/weblog/2021/feb/01/security-releases/

At a first glance, all of jessie, stretch, buster, bullseye, sid and
experimental are vulnerable.

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-2021-3281
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3281


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#980637: marked as done (git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode')

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 11:34:01 +
with message-id 
and subject line Bug#980637: fixed in git-buildpackage 0.9.22
has caused the Debian Bug report #980637,
regarding git-buildpackage: FTBFS: AttributeError: 'str' object has no 
attribute 'decode'
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.)


-- 
980637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-buildpackage
Version: 0.9.21
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> flake8 
> flake8  examples/gbp-add-patch examples/zeitgeist-git.py
> export GIT_AUTHOR_NAME="Gbp Tests";   \
> export GIT_AUTHOR_EMAIL=te...@example.com;\
> export GIT_COMMITTER_NAME=$GIT_AUTHOR_NAME;   \
> export GIT_COMMITTER_EMAIL=$GIT_AUTHOR_EMAIL; \
> PYTHONPATH=.  \
> LC_ALL=C.UTF-8 python3 setup.py nosetests --with-xcoverage
> running nosetests
> running egg_info
> creating gbp.egg-info
> writing gbp.egg-info/PKG-INFO
> writing dependency_links to gbp.egg-info/dependency_links.txt
> writing entry points to gbp.egg-info/entry_points.txt
> writing requirements to gbp.egg-info/requires.txt
> writing top-level names to gbp.egg-info/top_level.txt
> writing manifest file 'gbp.egg-info/SOURCES.txt'
> reading manifest file 'gbp.egg-info/SOURCES.txt'
> writing manifest file 'gbp.egg-info/SOURCES.txt'
> Coverage.py warning: --include is ignored because --source is set 
> (include-ignored)
> Doctest: gbp.command_wrappers.Command.__call__ ... ok
> Doctest: gbp.command_wrappers.Command._f ... ok
> Doctest: gbp.command_wrappers.Command.call ... ok
> Doctest: gbp.config.GbpOptionParser._listify ... ok
> Doctest: gbp.config.GbpOptionParser._name_to_filename ... ok
> Doctest: gbp.config.GbpOptionParser.get_config_files ... ok
> Doctest: gbp.deb.format.DebianSourceFormat ... ok
> Doctest: gbp.deb.format.DebianSourceFormat.parse_file ... ok
> Doctest: gbp.deb.git.DebianGitRepository._build_legacy_tag ... ok
> Doctest: gbp.deb.git.DebianGitRepository._mangle_version ... ok
> Doctest: gbp.deb.git.DebianGitRepository._sanitize_version ... ok
> Doctest: gbp.deb.git.DebianGitRepository._unsanitize_version ... ok
> Doctest: gbp.deb.git.DebianGitRepository.tag_to_version ... ok
> Doctest: gbp.deb.git.DebianGitRepository.version_to_tag ... ok
> Doctest: gbp.deb.policy.DebianPkgPolicy ... ok
> Doctest: gbp.deb.policy.DebianPkgPolicy.build_tarball_name ... ok
> Doctest: gbp.deb.uscan.Uscan._parse ... ok
> Doctest: gbp.deb.uscan.Uscan._parse_uptodate ... ok
> Doctest: gbp.deb.uscan.Uscan._raise_error ... ok
> Doctest: gbp.format.format_b ... ok
> Doctest: gbp.format.format_str ... ok
> Doctest: gbp.git.args.GitArgs ... ok
> Doctest: gbp.git.commit.GitCommit.is_sha1 ... ok
> Doctest: gbp.git.modifier.GitModifier.get_author_env ... ok
> Doctest: gbp.git.modifier.GitModifier.get_committer_env ... ok
> Doctest: gbp.git.repository.GitRepository.strip_sha1 ... ok
> Doctest: gbp.git.rfc822_date_to_git ... ok
> Doctest: gbp.patch_series.Patch._get_subject_from_filename ... ok
> Doctest: gbp.patch_series.PatchSeries._get_topic ... ok
> Doctest: gbp.patch_series.PatchSeries._parse_line ... ok
> Doctest: gbp.patch_series.PatchSeries._read_series ... ok
> Doctest: gbp.patch_series.PatchSeries._split_strip ... ok
> Doctest: gbp.patch_series.PatchSeries._strip_comment ... ok
> Doctest: gbp.pkg.archive.Archive.parse_filename ... ok
> Doctest: gbp.pkg.compressor.Compressor.__repr__ ... ok
> Doctest: gbp.pkg.compressor.Compressor.cmdline ... ok
> Doctest: gbp.pkg.git.PkgGitRepository.sanitize_prefix ... ok
> Doctest: gbp.pkg.pkgpolicy.PkgPolicy.guess_upstream_src_version ... ok
> Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_packagename ... ok
> Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_upstreamversion ... ok
> Doctest: gbp.pkg.pkgpolicy.PkgPolicy.version_subst ... ok
> Doctest: gbp.rpm.git.RpmGitRepository._sanitize_tag ... ok
> Doctest: gbp.rpm.git.RpmGitRepository.version_to_tag ... ok
> Doctest: gbp.rpm.linkedlist.LinkedList.append ... ok
> Doctest: gbp.rpm.linkedlist.LinkedList.delete ... ok
> Doctest: gbp.rpm.linkedlist.LinkedList.insert_after ... ok
> Doctest: gbp.rpm.linkedlist.LinkedList.insert_before ... ok
> Doctest: gbp.rpm.linkedlist.LinkedList.prepend ... ok
> Doctest: gbp.rpm.linkedlist.LinkedListNode.set_data ... ok
> Doctest: gbp.rpm.policy.RpmP

Bug#980256: marked as done (git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not found)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 11:34:01 +
with message-id 
and subject line Bug#980256: fixed in git-buildpackage 0.9.22
has caused the Debian Bug report #980256,
regarding git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not 
found
to be marked as done.

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

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


-- 
980256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-buildpackage
Version: 0.9.21
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
git-buildpackage   from testing0.9.21
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?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/g/git-buildpackage/9735149/log.gz

+ python3 -c import setuptools
+ mktemp -d
+ GBP_TEMPDIR=/tmp/tmp.thAvJcvD7A
+ gbp buildpackage-rpm --git-packaging-dir=packaging/
--git-export-dir=/tmp/tmp.thAvJcvD7A -D%__python3 /usr/bin/python3
-D%__python /usr/bin/python3 -bb --nodeps
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Guido Günther]

Hi,
On Sun, Jan 31, 2021 at 11:41:07PM +0100, Jochen Sprickerhof wrote:
> * Guido Günther  [2021-01-31 13:19]:
> > Awesome. I had fixed the rpm parts here already
> > https://github.com/agx/git-buildpackage/tree/rpm but went for your
> > patches so your work is not lost. The reason i wrote 'tip of the
> > iceberg' is that the component tests need fixing as well - that's the bit
> > still missing - so tests still fail when the testdata for the component
> > tests is there (`git submodule update --init --recursive`).
> 
> Ha, I missed those. Attached one patch for GBP
> (gbp-rpm-Fix-tags-in-rpm-spec-files.patch)
> and three for the rpm-testdata repo to make all tests work.

All applied now. Thanks!
 -- Guido

> 
> Cheers Jochen

> From 3da6cd3af18d51cce569f2ee829356c8bbdb9392 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sun, 31 Jan 2021 22:40:00 +0100
> Subject: [PATCH] rpm: Fix tags in rpm spec files
> 
> ---
>  tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec   |  6 +++---
>  tests/data/rpm/specs/gbp-test2-reference.spec  | 11 +--
>  tests/data/rpm/specs/gbp-test2-reference2.spec | 15 +++
>  tests/data/rpm/specs/gbp-test3.spec|  2 +-
>  4 files changed, 16 insertions(+), 18 deletions(-)
> 
> diff --git a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec 
> b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> index 8a92725..d5b8763 100644
> --- a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> +++ b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> @@ -6,10 +6,10 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  Patch10:my2.patch
>  Patch20:my3.patch
>  Packager:   Markus Lehtonen 
> diff --git a/tests/data/rpm/specs/gbp-test2-reference.spec 
> b/tests/data/rpm/specs/gbp-test2-reference.spec
> index 1882131..5e1f176 100644
> --- a/tests/data/rpm/specs/gbp-test2-reference.spec
> +++ b/tests/data/rpm/specs/gbp-test2-reference.spec
> @@ -6,12 +6,12 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  # Patches auto-generated by git-buildpackage:
> -Patch0: new.patch
> +Patch1: new.patch
>  Packager:   Markus Lehtonen 
>  
>  %description
> @@ -27,14 +27,13 @@ Empty subpackage for the %{name} test package.
>  %prep
>  %setup -T -n %{name}-%{version} -c -a 10
>  
> -%patch
>  
>  echo "Do things"
>  
>  # Gbp-Patch-Macros
>  # new.patch
>  %if 1
> -%patch0 -p1
> +%patch1 -p1
>  %endif
>  
>  %build
> diff --git a/tests/data/rpm/specs/gbp-test2-reference2.spec 
> b/tests/data/rpm/specs/gbp-test2-reference2.spec
> index d41f450..32bbe97 100644
> --- a/tests/data/rpm/specs/gbp-test2-reference2.spec
> +++ b/tests/data/rpm/specs/gbp-test2-reference2.spec
> @@ -6,13 +6,13 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  # Patches auto-generated by git-buildpackage:
> -Patch0: 1.patch
> -Patch1: 2.patch
> +Patch1: 1.patch
> +Patch2: 2.patch
>  Packager:   Markus Lehtonen 
>  VCS:myvcstag
>  
> @@ -29,18 +29,17 @@ Empty subpackage for the %{name} test package.
>  %prep
>  %setup -T -n %{name}-%{version} -c -a 10
>  
> -%patch
>  
>  echo "Do things"
>  
>  # Gbp-Patch-Macros
>  # 1.patch
>  %if true
> -%patch0 -p1
> +%patch1 -p1
>  %endif
>  # 2.patch
>  %ifarch %ix86
> -%patch1 -p1
> +%patch2 -p1
>  %endif
>  
>  %build
> diff --git a/tests/data/rpm/specs/gbp-test3.spec 
> b/tests/data/rpm/specs/gbp-test3.spec
> index c0c20c8..043afec 100644
> --- a/tests/data/rpm/specs/gbp-test3.spec
> +++ b/tests/data/rpm/specs/gbp-test3.spec
> @@ -6,7 +6,7 @@ Group:  Development/Libraries
>  License:GPLv2
>  Source: %{name}-%{version}.tar.gz
>  # Gbp-Ignore-Patches: 10
> -Patch:  my.patch
> +Patch0: my.patch
>  Patch10:my2.patch
>  Patch20:my3.patch
>  
> -- 
> 2.30.0
> 

> From 6753fd1cb848efe21c67589ca0cc00d636dfd1e4 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sun, 31 Jan 2021 16:22:55 +0100
> Subject: [PATCH 1/3] Adopt to Python 3
> 
> ---
>  manage.py | 18 +-
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/manage.py b/manage.py
> index 3eb8c39..57a56c7 100755
> --- a/manage.py
> +++ b/manage.py
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python
> +#!/usr/bin/python3
>  # vim:fileencoding=utf-8:et:ts=4:sw=4:sts=4
>  #
>

Bug#976735: spyder needs source upload for Python 3.9 transition

[Nilesh Patra]

Hi Julian,

On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey  wrote:
> On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > Package: spyder
> > Version: 3.3.6+dfsg1-5
> > Severity: serious
> >
> > Since binNMUs are not possible for binary-all packages,
> > a source upload is needed for the Python 3.9 transition.
> >
> > In a more general note, does /usr/bin/spyder3 have to use
> > the versioned interpreter instead of python3?
>
> The versioned interpreter can be avoided by removing '{interpreter} '
> from the definition of PYBUILD_AFTER_INSTALL in debian/rules.

Please consider to apply the fix if it works, also for #976966
Since freeze is near, it would be unfortunate to loose spyder and spyder-* 
packages in bullseye.

Nilesh

Bug#976735: spyder needs source upload for Python 3.9 transition

[Nilesh Patra]

Hi Julian,

On Sun, 13 Dec 2020 06:58:29 + Julian Gilbey  wrote:
> On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> > Package: spyder
> > Version: 3.3.6+dfsg1-5
> > Severity: serious
> >
> > Since binNMUs are not possible for binary-all packages,
> > a source upload is needed for the Python 3.9 transition.
> >
> > In a more general note, does /usr/bin/spyder3 have to use
> > the versioned interpreter instead of python3?
>
> The versioned interpreter can be avoided by removing '{interpreter} '
> from the definition of PYBUILD_AFTER_INSTALL in debian/rules.

Please consider to apply the fix if it works, also for #976966
Since freeze is near, it would be unfortunate to loose spyder and spyder-* 
packages in bullseye.

Nilesh