Bug#961302: Processed: bug 961302 is forwarded to https://gitlab.com/sane-project/backends/-/issues/279

[Jörg Frings-Fürst]

Hello Moritz,

Am Samstag, dem 09.01.2021 um 23:40 +0100 schrieb Moritz Mühlenhoff:
> Am Mon, Jun 01, 2020 at 09:33:48PM +0200 schrieb Salvatore
> Bonaccorso:
> > Hi Jörg,
> > 
[...]

> What's the status, can you please fix this for unstable in time of
> the freeze?
> 

This is fixed since release 1.0.30-1~experimental1 and the bug is
closed.

> Cheers,
>     Moritz

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#979565: marked as done (/usr/lib/ispell/ogerman.aff: multiple errors)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 07:03:54 +
with message-id 
and subject line Bug#979575: fixed in ispell 3.4.02-1
has caused the Debian Bug report #979575,
regarding /usr/lib/ispell/ogerman.aff: multiple errors
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.)


-- 
979575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iogerman
Version: 1:2-37
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

During an upgrade:

[…]
Processing triggers for dictionaries-common (1.28.3) ...
ispell-autobuildhash: Processing 'british' dict.
ispell-autobuildhash: Processing 'ogerman' dict.
/usr/lib/ispell/ogerman.aff line 242: No such string character
/usr/lib/ispell/ogerman.aff line 293: No such string character
/usr/lib/ispell/ogerman.aff line 293: No such string character
/usr/lib/ispell/ogerman.aff line 308: No such string character
/usr/lib/ispell/ogerman.aff line 309: No such string character
/usr/lib/ispell/ogerman.aff line 324: No such string character
/usr/lib/ispell/ogerman.aff line 325: No such string character
/usr/lib/ispell/ogerman.aff line 340: No such string character
/usr/lib/ispell/ogerman.aff line 341: No such string character
/usr/lib/ispell/ogerman.aff line 782: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 783: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 784: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 785: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 786: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 787: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 804: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 829: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 832: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 850: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 878: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 938: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 955: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 972: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 989: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 1049: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 1062: Single characters must be separated by a 
blank
/usr/lib/ispell/ogerman.aff line 1075: Single characters must be separated by a 
blank
[…]



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages iogerman depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  dictionaries-common1.28.3
ii  ispell 3.4.01-1
ii  perl   5.32.0-6

iogerman recommends no packages.

Versions of packages iogerman suggests:
ii  wogerman  1:2-37

-- debconf information:
  shared/packages-ispell:
  iogerman/languages: deutsch (Old German -tex mode-), deutsch (Old German 8 
bit)
--- End Message ---
--- Begin Message ---
Source: ispell
Source-Version: 3.4.02-1
Done: Robert Luberda 

We believe that the bug you reported is fixed in the latest version of
ispell, 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.
Robert Luberda  (supplier of updated ispell 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

Bug#979549: marked as done (ingerman: Problems during ispell-autobuild)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 07:03:54 +
with message-id 
and subject line Bug#979575: fixed in ispell 3.4.02-1
has caused the Debian Bug report #979575,
regarding ingerman: Problems during ispell-autobuild
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.)


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

Dear Maintainer,

during dist-upgrade I've got the following messeges

ispell-autobuildhash: Processing 'ngerman' dict.
/usr/lib/ispell/ngerman.aff line 157: No such string character
/usr/lib/ispell/ngerman.aff line 214: No such string character
/usr/lib/ispell/ngerman.aff line 214: No such string character
/usr/lib/ispell/ngerman.aff line 217: No such string character
/usr/lib/ispell/ngerman.aff line 218: No such string character
/usr/lib/ispell/ngerman.aff line 219: No such string character
/usr/lib/ispell/ngerman.aff line 220: No such string character
/usr/lib/ispell/ngerman.aff line 224: No such string character
/usr/lib/ispell/ngerman.aff line 240: No such string character
/usr/lib/ispell/ngerman.aff line 255: No such string character
/usr/lib/ispell/ngerman.aff line 256: No such string character
/usr/lib/ispell/ngerman.aff line 271: No such string character
/usr/lib/ispell/ngerman.aff line 272: No such string character
/usr/lib/ispell/ngerman.aff line 462: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 463: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 464: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 465: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 466: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 467: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 695: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 696: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 697: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 698: Single characters must be separated by a b
lank
/usr/lib/ispell/ngerman.aff line 949: Single characters must be separated by a b
lank

Word 'Attach�' contains illegal characters

Word 'Boucl�' contains illegal characters

Word 'Bourr�e' contains illegal characters

Word 'B�chamel' contains illegal characters

Word 'Caf�' contains illegal characters

Word 'Chicor�e' contains illegal characters

Word 'Ch�teau' contains illegal characters

Word 'Cr�pe' contains illegal characters

Word 'Dekollet�' contains illegal characters

Word 'Drag�e' contains illegal characters

Word 'Expos�' contains illegal characters

Word 'Familiencaf�' contains illegal characters

Word 'Glac�handschuh' contains illegal characters

Word 'Kommuniqu�' contains illegal characters

Word 'Lam�' contains illegal characters

Word 'Linn�' contains illegal characters

Word 'Marineattach�' contains illegal characters

Word 'Milita"rattach�' contains illegal characters

Word 'Moir�' contains illegal characters

Word 'Napol�on' contains illegal characters

Word 'Neglig�' contains illegal characters

Word 'Nestl�' contains illegal characters

Word 'Pappmach�' contains illegal characters

Word 'pass�' contains illegal characters

Word 'Romm�' contains illegal characters

Word 'Souffl�' contains illegal characters

Word 'S�par�e' contains illegal characters

Word 'Variet�' contains illegal characters


Seems to be a problem with accent signs. I don't know if this is a problem
by ingerman or ispell itself


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'testing'), (600, 'stable'), (500, 
'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages ingerman depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  dictionaries-common1.28.3
ii  ispell 3.4.01-1

ingerman recommends no packages.

Versions of packages ingerman suggests:
ii  wngerman  20161207-8

-- debconf information:
  shared/packages-ispell:
  ingerman/languages: deutsch (New German -tex mode-), deutsch (New German 8 
bit)
--- 

Bug#979575: marked as done (ispell 3.4.01 breaks affix files of igerman98 and hkgerman)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 07:03:54 +
with message-id 
and subject line Bug#979575: fixed in ispell 3.4.02-1
has caused the Debian Bug report #979575,
regarding ispell 3.4.01 breaks affix files of igerman98 and hkgerman
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.)


-- 
979575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ispell
Version: 3.4.01-1
Severity: important

Dear Maintainer,

the upgrade of ispell from 3.4.00-8 to 3.4.01-1 breaks ispell
dictionary building in the German dictionary packages igerman98 and
hkgerman.

Currently I do not fully understand what happens, but using the old
affix files, that worked without problems in 3.4.00-8, results in
errors like this:

/usr/lib/ispell/ngerman.aff line 187: No such string character

(this reflects lines like:
altstringchar   ss  ss
altstringchar   SS  SS  # this definition is used for checking
)


or
/usr/lib/ispell/ngerman.aff line 462: Single characters must be separated by a 
blank

(this points to lines like:
A SS>   -ASS,A"SSCHENS
)


Removing the above altstrinchar lines and splitting the "SS" to "S S"
works around the errors, but in the resulting dictionaries some words
are missing, which isn't what I expect.


Some of the problems are based on igerman98 using native iso-8859-1
for some uncommon characters, which I'll try to work around myself,
but I'm not sure whether the "SS" issues are a problem of the German
dictionaries or some bug in the new ispell binary.

At least the behavior of ispell shouldn't change in such a non
backward compatible way...

We will need some versioned dependencies/conflicts or the like in
ispell and/or igerman/hkgerman.

This report it primarily to inform you, that there is some regression
with the upgrade, see also
https://bugs.debian.org/979549 (igerman98)
https://bugs.debian.org/979565 (hkgerman)

Not sure, whether these can be fixed without changes in ispell.

Greetings
Roland


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ispell
Source-Version: 3.4.02-1
Done: Robert Luberda 

We believe that the bug you reported is fixed in the latest version of
ispell, 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.
Robert Luberda  (supplier of updated ispell 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, 11 Jan 2021 07:38:18 +0100
Source: ispell
Architecture: source
Version: 3.4.02-1
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Robert Luberda 
Closes: 979575
Changes:
 ispell (3.4.02-1) unstable; urgency=medium
 .
   * New upstream version:
 + fixes regression introduced in 3.4.01 (closes: #979575).
   * Remove 0011-Missing-prototypes.patch and 0021-Fix-gcc-warnings.patch.
Checksums-Sha1:
 843dc4fa83b4915c2bc6e2223996835c3a680eeb 2781 ispell_3.4.02-1.dsc
 128e5e938cda41eee749008ad3799bdd5e6fd97f 670270 ispell_3.4.02.orig.tar.gz
 003225d80f02ec6adb62a517e75f9d56a5762f33 38952 ispell_3.4.02-1.debian.tar.xz
 fdac20d511224e73d2dd52a9458fca4bf90fb398 9720 ispell_3.4.02-1_amd64.buildinfo
Checksums-Sha256:
 dca763474b8a1d64b71d8135f9e162aba5282668a22d265c663ad60c23dda2e1 2781 
ispell_3.4.02-1.dsc
 6679604c3157fe54b2100905f3b52aaadfd23f46bb05a787188ec326f1c7d92c 670270 
ispell_3.4.02.orig.tar.gz
 b5043b1899c0c19d094fb4ea489c77c55eac468d94656428e7a856862320d646 38952 
ispell_3.4.02-1.debian.tar.xz
 d86a16fdc06169ce8a839e9a902a30f976abc5571ac89b739edeb23e8a2051c4 9720 
ispell_3.4.02-1_amd64.buildinfo
Files:
 3150d181dc598a95ab0dedffea027b7d 2781 text optional ispell_3.4.02-1.dsc
 ca07e4cff8701b0cde12547ba6b2768b 670270 text optional ispell_3.4.02.orig.tar.gz
 4e0d82d74d8934e302ba03fc193486ed 38952 text optional 
ispell_3.4.02-1.debian.tar.xz
 4210fe92e3459fb348378d24fb85ebc7 9720 text optional 
ispell_3.4.02-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAl/78zoACgkQYx3nVTvo

Bug#976891: placeholder until fastboot builds

[Timo Haverkamp]

Fix fastboot on Debian placeholder until fastboot builds.

https://corcorhacking.blogspot.com/2021/01/how-to-install-adb-fastboot-and-fix.html?m=1

Holen Sie sich Outlook für Android

Bug#979493: Error: Rule failed to generate the following targets: _doc/_html/highlight.pack.js

[Johannes Schauer Marin Rodrigues]

Hi Ralf,

Quoting Johannes Schauer Marin Rodrigues (2021-01-11 07:11:07)
> did you test this? As I already pointed out when we talked about this in
> connection with dose3, I had libjs-highlight.js installed the whole time. I
> just upgraded ocaml-odoc and the problem still persists.

scratch that. The bug is fixed. The tests on ci.debian.net are successful now.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#979493: Error: Rule failed to generate the following targets: _doc/_html/highlight.pack.js

[Johannes Schauer Marin Rodrigues]

Hi Ralf,

Quoting Ralf Treinen (2021-01-10 13:22:56)
> On Thu, Jan 07, 2021 at 11:47:06AM +0100, Johannes 'josch' Schauer wrote:
> > I now investigated further and it seems that the package has an autopkgtest
> > (yay!) so I triggered that and it failed with the same error message that I
> > got:
> > 
> > https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml-odoc/9469763/log.gz
> > 
> > Since the logs are removed after some time, here the last lines from the
> > log:
> > 
> > autopkgtest [02:11:21]: test odoc-on-odoc: [---
> > File series fully applied, ends at patch 
> > debian/patches/no-vendored-js-highlight
> > File "_doc/_html/_unknown_", line 1, characters 0-0:
> > Error: Rule failed to generate the following targets:
> > - _doc/_html/highlight.pack.js
> 
> That seems to be due to a missing libjs-highlight.js. This used to be
> only a Recommends, and hence was not pulled in by the test runner. I
> have now made it a Depends, I hope that will solve the problem.

did you test this? As I already pointed out when we talked about this in
connection with dose3, I had libjs-highlight.js installed the whole time. I
just upgraded ocaml-odoc and the problem still persists.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#971305: marked as done (patator: Switch to python3-pycryptodome)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 03:25:31 +
with message-id 
and subject line Bug#971305: fixed in patator 0.9-3
has caused the Debian Bug report #971305,
regarding patator: Switch to python3-pycryptodome
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.)


-- 
971305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: patator
Version: 0.9-1
Severity: important
Tags: sid bullseye
Usertags: pycrypto

Dear maintainer,

patator currently Build-Depends or Depends on python3-crypto from
PyCrypto. This project is no longer maintained and PyCryptodome
(https://www.pycryptodome.org/en/latest/) provides a drop in
replacement. Please switch to python3-pycryptodome. I'd like to
remove python-crypto before the release of bullseye.

Cheers 
--- End Message ---
--- Begin Message ---
Source: patator
Source-Version: 0.9-3
Done: Francisco Vilmar Cardoso Ruviaro 

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

Debian distribution maintenance software
pp.
Francisco Vilmar Cardoso Ruviaro  (supplier of 
updated patator 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, 11 Jan 2021 02:31:01 +
Source: patator
Architecture: source
Version: 0.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Francisco Vilmar Cardoso Ruviaro 
Closes: 971305
Changes:
 patator (0.9-3) unstable; urgency=medium
 .
   * Add debian/patches/pycryptodome.patch.
 Thanks to Sebastian Ramacher . (Closes: #971305)
   * Bump Standards-Version to 4.5.1.
   * debian/watch: bump to version 4.
Checksums-Sha1:
 e70e9b24ddbc0cc2ea351aece71dba4b8966a209 2259 patator_0.9-3.dsc
 8be60e3f7890606f23e255281839e39e71e6cb7a 4688 patator_0.9-3.debian.tar.xz
 c7b65e7f1b4dd3dce05d168ff8b318cbe6fbbfa0 7925 patator_0.9-3_amd64.buildinfo
Checksums-Sha256:
 87d74ac4c4322cf2b11afde77c145e038c7670c01ca94e2555b68117700cafff 2259 
patator_0.9-3.dsc
 13ebf47f82a09d79304968e517af86b9b0fd01f7d1874a96ece8038394a1ba0c 4688 
patator_0.9-3.debian.tar.xz
 d02f7816939065b8d1bd6ac5f8417af7015be74dfb7aad929db55325b7c190e0 7925 
patator_0.9-3_amd64.buildinfo
Files:
 803bc6c8da129e6aa27542cf640e4c7f 2259 utils optional patator_0.9-3.dsc
 0b2eca925129144e35465207166e525e 4688 utils optional 
patator_0.9-3.debian.tar.xz
 0670f59d660dd83f3f9317f4dc50a01f 7925 utils optional 
patator_0.9-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEEG4z2Vu87hEcvSPDngvv3BgsvfQAFAl/7vwEdHGZyYW5jaXNj
by5ydXZpYXJvQHJpc2V1cC5uZXQACgkQgvv3BgsvfQC7VQ//Qn6zDdjQpCS0kQn3
8QmncQ0mUjbbgGMdhJRUd8qZC7Lp3jC5dWrIFHMw/06JcfdnWF0quj500l4+5vg9
BSOehwUWBI+7uZtCQBPEdgvWB2NRQPxC5W3oQ2g4/uHtVmprwb9jyBZx3rqkgULE
1W65zfyDC6zr/hVC+627HatlKhNQh/Goep5uwfpjiB3Ox21HvUy+FlThtZPygTWP
v4ef8CtnRih44DjQX7Gs0Lg0TgeB8l3SIgGQldboEFmwgVkFj0Oy3eaqbbTCUlfl
Vy+qp5E8VcS0kw44wz5IESTV3UoQXd5I6uY9djkKYCd6NazXYz0kSMzx0iIdlba3
aucvbSiQ9+Xxf07v4l/+nEyCuSY5HUW1SrGlAt90VRLWRChF9gBPUKUtZKmYsN1i
74NVNBCbtVWAbuSxLzgCsW0uueQ72lH1oSj4FG+tFVr4z3Inyv41xRFmBoqzCFsR
+HmyDoK6fIHOjctXd1Ny81/jItA92E3WDcHLZi8s8a8YaDjzlufNYpbO4B/+4Lnt
R9Y44hW012opEXmaIJxKxyFUWPiVmGqrwQTmBwrTH7FPJ4MZyQ+TY99QII9W7Mrw
CPo50yqAtEhwCBsfKKBCYPb/2b4veahipZQwEW24XusYquAWnqWRrYHGEESgSsoC
qlpMZQYmAF7022Z9gnJ+KqeC2MU=
=cyUb
-END PGP SIGNATURE End Message ---

Bug#977468: smuxi is marked for autoremoval from testing

[Mirco Bauer]

Thanks for your email and raised concern, Jeremy.

Full accessibility in Smuxi has been a high priority for me for a long
time.

I looked into the vulnerability of the log4net library that Smuxi depends
on. my assessment doesn't classify a XXE for local configuration file as
release critical. An attacker would need to have write access to the
configuration file to exploit it. It that point a XXE is pointless, he can
just execute curl, wget, perl, python or write something to ~/.bashrc
directly.
Having identified the offending code the fix is a one line change on the
other hand. I plan to upload a fixed version of log4net in the coming days.

To bump the version to the latest one of log4net so late in the release
cycle I don't see as a good option. There are 2 other reverse dependencies
that could break where I am not upstream of.

Best regards,

Mirco Bauer

Smuxi and Debian developer


On Sun, 10 Jan 2021, 19:53 Jérémy Prego,  wrote:

> hello,
>
> as a blind user, I regret removing smuxi from debian. I am a daily smuxi
> user. Unfortunately, this is the only accessible graphical irc client
> that I know of under Debian. for other types of messaging i use pidgin,
> but for irc i really like to use smuxi ...
>
> is there really no solution to keep smuxi in debian?
>
> thanks,
>
> Jerem
> Le 10/01/2021 à 05:39, Debian testing autoremoval watch a écrit :
> > smuxi 1.0.7-5.1 is marked for autoremoval from testing on 2021-02-08
> >
> > It (build-)depends on packages with these RC bugs:
> > 977468: log4net: CVE-2018-1285
> >  https://bugs.debian.org/977468
> >
> >
> >
> > This mail is generated by:
> >
> https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
> >
> > Autoremoval data is generated by:
> >
> https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
>
>

Bug#979361: marked as done (tpm2-tss: FTBFS: missing BD on dh-pyhon)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 02:50:42 +
with message-id 
and subject line Bug#979361: fixed in tpm2-pkcs11 1.5.0-2
has caused the Debian Bug report #979361,
regarding tpm2-tss: FTBFS: missing BD on dh-pyhon
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.)


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

tpm2-pkcs11 fails to build:
|  debian/rules clean
| dh clean --exclude=.la --exclude=.pc --with python3
| dh: error: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/i386-linux-gnu/perl/5.32.0 /usr/local/share/perl/5.32.0 
/usr/lib/i386-linux-gnu/perl5/5.32 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl-base /usr/lib/i386-linux-gnu/perl/5.32 
/usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 12) line 1.
| BEGIN failed--compilation aborted at (eval 12) line 1.

See
https://buildd.debian.org/status/fetch.php?pkg=tpm2-pkcs11=i386=1.5.0-1=1609856984=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tpm2-pkcs11
Source-Version: 1.5.0-2
Done: SZ Lin (林上智) 

We believe that the bug you reported is fixed in the latest version of
tpm2-pkcs11, 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.
SZ Lin (林上智)  (supplier of updated tpm2-pkcs11 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, 11 Jan 2021 10:15:57 +0800
Source: tpm2-pkcs11
Architecture: source
Version: 1.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alvin Chen 
Changed-By: SZ Lin (林上智) 
Closes: 979361
Changes:
 tpm2-pkcs11 (1.5.0-2) unstable; urgency=medium
 .
   [ SZ Lin (林上智) ]
   * Fix FTBFS issue by adding dh-pyhon to BD (Closes: #979361)
 .
   [ Ying-Chun Liu (PaulLiu) ]
   * Add debian/gbp.conf
   * d/rules:
 - Add hardening ldflags
 - Clean tools/tpm2_pkcs11_tools.egg-info directory
Checksums-Sha1:
 3eff311b48ee3a48a3fe847db6523dea877c7da8 3180 tpm2-pkcs11_1.5.0-2.dsc
 4b7c6a4b375f2bde29be3d20c6df9e6aaf41eb85 11092 
tpm2-pkcs11_1.5.0-2.debian.tar.xz
 ea40cbe6329124b919ccf21c21772a7c55d7e1e0 9760 
tpm2-pkcs11_1.5.0-2_amd64.buildinfo
Checksums-Sha256:
 15bd62db83ac2c6ef417d4cd6e7cef968256fc5cef5f45b0e111e1bd239269a4 3180 
tpm2-pkcs11_1.5.0-2.dsc
 d3a945fa15a4fd4f0659c69b935def471f2ab554fc9faacf9402956400a5b38a 11092 
tpm2-pkcs11_1.5.0-2.debian.tar.xz
 cdf7e164d7f503a2f92f61b03ba9a8be2e689b49a44ad8add0b35ef250556d14 9760 
tpm2-pkcs11_1.5.0-2_amd64.buildinfo
Files:
 122af5a2ed181d2f79669611277e2d1a 3180 libs optional tpm2-pkcs11_1.5.0-2.dsc
 bb4cab17ceda1a60e19847d733849f97 11092 libs optional 
tpm2-pkcs11_1.5.0-2.debian.tar.xz
 b2b1f972fa9892c532cd5c2273c2e804 9760 libs optional 
tpm2-pkcs11_1.5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF4+DOLMUAeME/ES6qVmzipVh8/kFAl/7t5QACgkQqVmzipVh
8/lUzRAAiZtaMTiVtJaZa/3NsEjgSRKZ1zjy+jzB8wgRQc/PJals9cD5TeJ3ZLBV
XXKuEpN6ghrlhfUNf+lQIl+E6jldY11wt1UjQN+AWmreFYxxAZbt8ZHslb+G6M4L
GWmqTmuiQxq5R3vEax3X18gXkvsDXyDfs+bXDnZW1OaXkQXjazjMgEvvxpU+A6NE
O5dN0QYgsCbPyeEKHD6dSuZxqAr819K02jzuz4kcF+9knksMyDB6bhbEZljoOnt1
KNEcv6YzHZ8OluWqJBzueHH39hUsH3sk9F6vzLWsx8yve0A89V2zqd6XKuMSPOBF
T8RZN9EucfP1qi+3nTKSBpUSG/B0sOGlII4/mIlm5jarZSx5yflbAQo9WnNHPWpz
EPMJsZHe3vBM5EqcnQlOMG1xECbf+fDsD2yLTOwtoBQnZqaoihYSVP7j2pR0k9ID
A/FMUr1VUQPi85iCvWbdikm3ahykQFmE6sqBJi7vhGbWn6lXcu76BNY48kaM2qfz
83Mr0UClF1z2NR2KcSamCsFckRILJmaPJngA5Ndwyj8SehH5glfG0+q0CuUFyaCw
iGz+AKu77ed9uBhq4tY0FfoYByZ5sZk/q9RL6fSQ0KkZX8gLMF66a44vJCVR8aAA
CrJhQZjGkhKxvDrzqY1WtSOwHDxo7lOpLwxMvkqSS+vw/+5/lZo=
=Bmm+
-END PGP SIGNATURE End Message ---

Bug#975672: Bug#979245: RFS: xylib/1.6-0.1 [RC] [NMU] -- Library for reading x-y data from several file formats

[Stuart Prescott]

Hi Fabian

> But no, I do not currently intend to adopt this package. I just
> thought I'd try and help with the freeze preparation by fixing the RC
> bug in this package.

No worries. Thanks for taking care of an RC bug :)

> The reason I created the repository in the Science Team area is that I
> have write access there (unlike in the Debian group) and because it
> fits topically. If this is a problem, you can create a repository in
> the Debian group, give me "Maintainer" access (so that I can push to
> master), and I'll change the Vcs-* fields in d/control.

It's quite unusual to include the VCS within a team when the package is not 
maintained by the team; however, it's probably also better to have a packaging 
VCS somewhere than to not have one these days.

Anyway, I agree with your assessment that the package probably lives best 
within the Science Team and so I'll adopt the package into the Debian Science 
Team. Thanks for setting up a VCS for it!

> In any case, I've changed my upload to a QA upload now and reuploaded
> it to Salsa and Mentors.

I see bartm beat me to uploading it.

Thank you for your contribution to Debian!

cheers
Stuart



-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#957936: marked as done (wine: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 02:36:43 +
with message-id 
and subject line Bug#957936: fixed in wine 5.0.3-1
has caused the Debian Bug report #957936,
regarding wine: 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.)


-- 
957936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wine
Version: 5.0-3
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/wine_5.0-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
gcc -m64 -c -o sti_main.o sti_main.c -I. -I../../include -I../../include/msvcrt 
-D__WINESRC__ -D_REENTRANT -fPIC -fno-builtin -fshort-wchar -mabi=ms -Wall 
-pipe -fcf-protection=none -fno-stack-protector -fno-strict-aliasing 
-Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers 
-Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits 
-Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op 
-gdwarf-2 -gstrict-dwarf -Werror -Wdate-time -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fcommon -Wno-shift-overflow -Wno-unused-function 
-Wno-deprecated-declarations
gcc -m64 -c -o clipboard.o clipboard.c -I. -I../../include -I../.. 
-D__WINESRC__ -D_SHELL32_ -D_REENTRANT -fPIC -Wall -pipe -fcf-protection=none 
-fno-stack-protector -fno-strict-aliasing -Wdeclaration-after-statement 
-Wempty-body -Wignored-qualifiers -Wno-packed-not-aligned -Wshift-overflow=2 
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla 
-Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -Werror 
-Wdate-time -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fcommon 
-Wno-shift-overflow -Wno-unused-function -Wno-deprecated-declarations
../../tools/widl/widl --dlldata-only -o dlldata.c sti_wia.idl
../../tools/widl/widl -o sti_wia_p.c -m64 --nostdinc -I. -I../../include 
-I../../include/msvcrt -D__WINESRC__ sti_wia.idl
../../tools/widl/widl -o sti_wia.h -m64 --nostdinc -I. -I../../include 
-I../../include/msvcrt -D__WINESRC__ sti_wia.idl
../../tools/widl/widl -o sti_wia_r.res -m64 --nostdinc -I. -I../../include 
-I../../include/msvcrt -D__WINESRC__ sti_wia.idl
gcc -m64 -c -o dlldata.o dlldata.c -I. -I../../include -I../../include/msvcrt 
-D__WINESRC__ -DENTRY_PREFIX=STI_ -DPROXY_DELEGATION -DWINE_REGISTER_DLL 
-D_REENTRANT -fPIC -fno-builtin -fshort-wchar -mabi=ms -Wall -pipe 
-fcf-protection=none -fno-stack-protector -fno-strict-aliasing 
-Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers 
-Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits 
-Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op 
-gdwarf-2 -gstrict-dwarf -Werror -Wdate-time -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fcommon -Wno-shift-overflow -Wno-unused-function 
-Wno-deprecated-declarations
gcc -m64 -c -o sti_wia_p.o sti_wia_p.c -I. -I../../include 
-I../../include/msvcrt -D__WINESRC__ -D_REENTRANT -fPIC -fno-builtin 
-fshort-wchar -mabi=ms -Wall -pipe -fcf-protection=none -fno-stack-protector 
-fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body 
-Wignored-qualifiers -Wno-packed-not-aligned -Wshift-overflow=2 
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla 
-Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -Werror 

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

[Michael Gilbert]

On Tue, Dec 22, 2020 at 3:45 AM Michel Le Bihan wrote:
> I my NMU 87.0.4280.88-0.2 has just been uploaded to unstable and I'm
> interested in joining and helping with the package. My work is in
> https://salsa.debian.org/mimi8/chromium/ . Please also see the
> discussion under
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848 .

Hi Michel,

Thank you for helping out with the package over the past couple
months.  Clearly I have not had time lately. I just added you to the
salsa group.  Please feel free to add yourself as an uploader.

Best wishes,
Mike

Bug#977054: aiorwlock FTBFS with pytest 6

[s3v]

Dear Maintainer,

please find attached a patch to fix this issue.
Anyway new version for aiorwlock was released upstream
and affected code was changed.
FWIW, packaging aiorwlock 1.0.0 solves this bug.

Kind Regards.
Index: aiorwlock-0.6.0/tests/conftest.py
===
--- aiorwlock-0.6.0.orig/tests/conftest.py
+++ aiorwlock-0.6.0/tests/conftest.py
@@ -42,7 +42,7 @@ def loop(request, loop_type, debug):
 @pytest.mark.tryfirst
 def pytest_pycollect_makeitem(collector, name, obj):
 if collector.funcnamefilter(name):
-item = pytest.Function(name, parent=collector)
+item = pytest.Function.from_parent(collector, name=name)
 if 'run_loop' in item.keywords:
 return list(collector._genfunctions(name, obj))

Bug#979747: rtpproxy: FTBFS with GCC 10

[Logan Rosen]

Package: rtpproxy
Version: 1.2.1-2.2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

rtpproxy currently FTBFS in Debian unstable with GCC 10 as default.

>From a local build:
gcc -std=gnu99 -Wall -Wno-uninitialized -g -O2 -ffile-prefix-map=/build/rtpproxy
-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro
 -Wl,-z,now -o rtpproxy main.o rtp_server.o rtpp_record.o rtpp_util.o rtp.o rtp_
resizer.o rtpp_session.o rtpp_command.o rtpp_log.o rtpp_syslog_async.o -lm -lpth
read
/usr/bin/ld: rtpp_record.o:./rtpp_record.h:84: multiple definition of `__packed'
; main.o:./rtpp_record.h:84: first defined here
/usr/bin/ld: rtpp_session.o:./rtpp_record.h:84: multiple definition of `__packed
'; main.o:./rtpp_record.h:84: first defined here
/usr/bin/ld: rtpp_command.o:./rtpp_record.h:84: multiple definition of `__packed
'; main.o:./rtpp_record.h:84: first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:455: rtpproxy] Error 1
make[2]: Leaving directory '/build/rtpproxy-1.2.1'
make[1]: *** [Makefile:354: all] Error 2
make[1]: Leaving directory '/build/rtpproxy-1.2.1'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:6: build] Error 25

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10.patch: Fix compilation with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru rtpproxy-1.2.1/debian/patches/gcc-10.patch 
rtpproxy-1.2.1/debian/patches/gcc-10.patch
--- rtpproxy-1.2.1/debian/patches/gcc-10.patch  1969-12-31 19:00:00.0 
-0500
+++ rtpproxy-1.2.1/debian/patches/gcc-10.patch  2021-01-10 20:42:24.0 
-0500
@@ -0,0 +1,11 @@
+--- a/rtpp_record.h
 b/rtpp_record.h
+@@ -81,7 +81,7 @@
+ uint32_t family;
+ struct ip iphdr;
+ struct udphdr udphdr;
+-} __packed;
++};
+ 
+ struct pkt_hdr_adhoc {
+ union sockaddr_in_s addr;   /* Source address */
diff -Nru rtpproxy-1.2.1/debian/patches/series 
rtpproxy-1.2.1/debian/patches/series
--- rtpproxy-1.2.1/debian/patches/series2014-02-15 22:57:22.0 
-0500
+++ rtpproxy-1.2.1/debian/patches/series2021-01-10 20:38:05.0 
-0500
@@ -1 +1,2 @@
 syslog_format.patch
+gcc-10.patch

Bug#971303: marked as done (python-file-encryptor: Switch to python3-pycryptodome)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jan 2021 01:21:05 +
with message-id 
and subject line Bug#971303: fixed in python-file-encryptor 0.2.9-5
has caused the Debian Bug report #971303,
regarding python-file-encryptor: Switch to python3-pycryptodome
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.)


-- 
971303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-file-encryptor
Version: 0.2.9-3
Severity: important
Tags: sid bullseye
Usertags: pycrypto

Dear maintainer,

python-file-encryptor currently Build-Depends or Depends on
python3-crypto from PyCrypto. This project is no longer maintained
and PyCryptodome (https://www.pycryptodome.org/en/latest/) provides a
drop in replacement. Please switch to python3-pycryptodome. I'd like
to remove python-crypto before the release of bullseye.

Cheers 
--- End Message ---
--- Begin Message ---
Source: python-file-encryptor
Source-Version: 0.2.9-5
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-file-encryptor 
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, 10 Jan 2021 18:40:37 -0600
Source: python-file-encryptor
Architecture: source
Version: 0.2.9-5
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 971303
Changes:
 python-file-encryptor (0.2.9-5) unstable; urgency=medium
 .
   * Add patch to replace dependency on PyCrypto in order to use PyCryptodome.
 Previous fix was not enough. Thanks to Sebastian Ramacher for the patch
 (Closes: #971303)
   * Bump Standards-Version to 4.5.1. No changes required
   * debian/watch: Bump file standard version to 4
Checksums-Sha1:
 db65439a3be7add0df342600e9d787056ba7309b 2083 python-file-encryptor_0.2.9-5.dsc
 be9b686acbc0033cc63bfdd8ca5938ac1929e1e2 3608 
python-file-encryptor_0.2.9-5.debian.tar.xz
 5a0c0a58f7cf1d3899a243099c5bacfee93aa608 6401 
python-file-encryptor_0.2.9-5_amd64.buildinfo
Checksums-Sha256:
 648385dd73464cfb527fade348183f1ecc5cdc5d028af94cc8f2005a23dfb51a 2083 
python-file-encryptor_0.2.9-5.dsc
 b4a710a3990feff30c84b403bf0f9c2d3499af8acbbe79275962b9b5dbf31a26 3608 
python-file-encryptor_0.2.9-5.debian.tar.xz
 9f873db86ab5b39bc4c133c5da579e3c480e8b417363854be8ff231e17de0b20 6401 
python-file-encryptor_0.2.9-5_amd64.buildinfo
Files:
 f02cd8ca1f89575cb072ffde4dffd445 2083 python optional 
python-file-encryptor_0.2.9-5.dsc
 9ccbb8b8b29490e5f09682c0675b046e 3608 python optional 
python-file-encryptor_0.2.9-5.debian.tar.xz
 3a94ca43c38d52adc55f7b82fdbcc953 6401 python optional 
python-file-encryptor_0.2.9-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl/7ooERHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T93+g/+PFWheWBQ75vZI18Zfk9SCrE8Z5i2nqFR
3eWXbkECpwVC3BVju+q2Cvut7nFrWo6uthcbWqvAtkd64SA7Gspdnl7dGq7xyTqj
9Rs2CcnnKTFExVZpy4n4AMVqkQa6IA4cemfs7qPC63v/ibBk4C8kuDTdv46fp00w
Q6XmbkzPsmhQj/pMY5d5pm0tJZXgELrL5CsgJcxPvz3mpRERrMXuvTD1rcXvxgwC
50lACdMLcsTLE9XtfKw34iXb3UR0ZRnVWmERCAiUE8OdvUdMzDNKmJZavlZTuvGy
btWTQIgMZ9jmnLJ+sPoSBvRGMG7m4P3yHQMZzvN2d3QZYTjBxGkYxrk+FzD9daaY
HuewWqv/8C85jWaPEWmHLPfGna6E5BmUfHgag6BRnjUyDm2/EXDwoipo/2LeRnqm
Gj4MYstxWhgeSIUoJZewtoHorf7mIDCq2b0IRoDGK5kPAdFr0mX/x3lpdm2M1PwE
qJgJqlXxB9lZ65BTPFPsSBQ/ZUFAlo4b81MGvYQATEUuJzaVW2rEdRXVnosmKkjX
V/ng68nzszMmhzW0X2Q9l9CeYkjXzk9w9TKgwgmlBurBtWjjGj3xXDKj37eUqMSt
BNJigLntjM0/8fRrvZk+ADubFNxoWvcO1TnABlEYPAiTbFOxA2sSalvHrZKSeBMq
gt/I9AwsClM=
=ibeb
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#979156: Useless in Debian

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #979156 [php-net-idna2] Useless in Debian
Severity set to 'important' from 'serious'

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

Bug#979156: Useless in Debian

[Guilhem Moulin]

Control: severity -1 important

On Sun, 10 Jan 2021 at 20:35:45 -0400, David Prévot wrote:
> Guilhem, I did not spot that with ”build-rdeps php-net-idna2”, so I assume
> your need is a work in progress (please, do correct me If I’m wrong).

Yup you're right, once this is ready php-net-idna2 should show up in
Roundcube's (Build-)Depends.  I hope to finalize that before the freeze,
so lowering the bug severity for now to remove its RC status :-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#979156: [pkg-php-pear] Bug#979156: Useless in Debian

[David Prévot]

Hi,

Le 10/01/2021 à 19:58, Guilhem Moulin a écrit :

On Sun, 03 Jan 2021 at 16:54:41 -0800, Sunil Mohan Adapa wrote:



I will be filing an RM: bug on the package on Jan 10, 2021. I will
wait to see if the other uploaders think it is still needed.


Roundcube's test suite which I'm working on now has some tests making
use of Net_IDNA2 so I'd like to keep the package around if possible :-)


Seems like a good enough reason to keep it in testing/unstable. Feel 
free to downgrade the severity of this bug report, and Sunil, please 
hold on the RM request.


Guilhem, I did not spot that with ”build-rdeps php-net-idna2”, so I 
assume your need is a work in progress (please, do correct me If I’m 
wrong). In case you don’t need this package for Bullseye, please keep 
(or raise again) the severity of this bug report, and drop it once your 
extended testsuite is ready.



I can give a hand and help bringing it up to shape for Bullseye.


I’m pretty sure this will be appreciated if you want to keep the package 
around ;).


Regards

David

Bug#962203: NMU

[Paul Wise]

On Sun, 2021-01-10 at 13:32 +0100, A Mennucc1 wrote:

> Dear all, sorry for being MIA so long;

No worries, I'm sure you had good reason, it is more important to take
care of yourself than to contribute to Debian and other FLOSS projects.

> I have added the NMU to the GIT repository. a.

Thanks for also fixing the debdelta service!

PS: I think this points towards a need to have more people involved in
maintenance of the debdelta package and also the service.

A Mennucc1, would you be interested in having assistance with the
codebase and the service?

Calum, would you be interested in co-maintaining the code and helping
out with the service?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#979156: [pkg-php-pear] Bug#979156: Useless in Debian

[Guilhem Moulin]

Hi all,

On Sun, 03 Jan 2021 at 16:54:41 -0800, Sunil Mohan Adapa wrote:
> I will be filing an RM: bug on the package on Jan 10, 2021. I will
> wait to see if the other uploaders think it is still needed.

Roundcube's test suite which I'm working on now has some tests making
use of Net_IDNA2 so I'd like to keep the package around if possible :-)
I can give a hand and help bringing it up to shape for Bullseye.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#979311: marked as done (ipe: FTBFS: install: cannot stat '../../build/doc/*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 23:19:03 +
with message-id 
and subject line Bug#979311: fixed in ipe 7.2.23+dfsg1-2
has caused the Debian Bug report #979311,
regarding ipe: FTBFS: install: cannot stat '../../build/doc/*': 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.)


-- 
979311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipe
Version: 7.2.23+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

ipe fails to build on the buildds:
| install -m 0755 ../../build/bin/ipe /<>/debian/tmp/usr/bin
| install -m 0755 ../../scripts/* 
/<>/debian/tmp/usr/share/ipe/7.2.23/scripts
| install -m 0644 ../../man/*.1 /<>/debian/tmp/usr/share/man/man1 
| install -m 0644 ../../build/doc/* 
/<>/debian/tmp/usr/share/ipe/7.2.23/doc
| install: cannot stat '../../build/doc/*': No such file or directory
| make[3]: *** [Makefile:116: install] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=ipe=i386=7.2.23%2Bdfsg1-1=1609803607=0

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ipe
Source-Version: 7.2.23+dfsg1-2
Done: Steve M. Robbins 

We believe that the bug you reported is fixed in the latest version of
ipe, 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.
Steve M. Robbins  (supplier of updated ipe 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: Sun, 10 Jan 2021 16:52:36 -0600
Source: ipe
Architecture: source
Version: 7.2.23+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Closes: 979311
Changes:
 ipe (7.2.23+dfsg1-2) unstable; urgency=medium
 .
   [ Steve Robbins ]
   * [acfeb5f] Make the docs target a dependency of build-arch
 (not install) so that it will be picked up in --arch=any builds.
 Closes: #979311
Checksums-Sha1:
 ffce8787a25ad75e91f271fd9eea7dd7c53e36be 2265 ipe_7.2.23+dfsg1-2.dsc
 e5bc72ee4d337bd96b9fa17709508daf4fa3f799 10392 ipe_7.2.23+dfsg1-2.debian.tar.xz
 fa7e535874bc6f9cd05fb722b2b27b873eee3490 12522 
ipe_7.2.23+dfsg1-2_source.buildinfo
Checksums-Sha256:
 d9f65a33a8de100c07609b729d36c2ba0cb2129dfb0db39bfb6573c01e8115c9 2265 
ipe_7.2.23+dfsg1-2.dsc
 2fbb2d15609dc343da4f771f95e632042b22102f1529967323805fa045415397 10392 
ipe_7.2.23+dfsg1-2.debian.tar.xz
 728889baa3ee86682333c4c83bd350c1c76917e65f90b12758501cca82af 12522 
ipe_7.2.23+dfsg1-2_source.buildinfo
Files:
 1822759618c6c51de3fe1b9d8cc959f0 2265 graphics optional ipe_7.2.23+dfsg1-2.dsc
 dbe6bb99df088b5154dce2f17fcf10df 10392 graphics optional 
ipe_7.2.23+dfsg1-2.debian.tar.xz
 a869c84ebaadf1ed306561130336517c 12522 graphics optional 
ipe_7.2.23+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAl/7haYPHHNtckBkZWJp
YW4ub3JnAAoJEMnlXi+tyPS57DsP/3ch1zUY18idSNMDGsO6g8Thk84zpdyDTOPM
1SyvcbFhw2/0P52MlcelQkOyN+QQRq/EUctb8/Aq4d8Vr8nEN8UZ90SyEx9UsEwc
6WE2qeKYRHhR+tZrYR1rp1OOfBZ8RiSGlKAi5zE5ESSzSLFu7GEij9qmWrGCrlxm
/chss4lCvc07sZGTZBpYn1GwsJDBT2nmo98pyX0h1w4jT0fw2/fNU4F1u4iBZO66
2OK/U34ppszJ1iSesd1BUYhqiUaeg+v9/zTAXq7+wQk6CIvjHfJg06sdfEnEmWnv
Ss2h0slC7Jz9cWFgSXxsNMBI70eRd6dtKBRwPxyv6JePw1gJz39v7vHIr+ZrzrQz
6wDKCn6TZ1pOnfHbJ+K0s78FZrtlvPrGXiBy8FOYsTFip1Iz8zC14smo9XI7817u
j9fkCuaxbbpv4i0BGwCHpyz+wzni8z9iFZSwaBo39iQWvJ2imQ56+RnjOYSGUsU1
SvY5lQLEiT4U8rm6Dg4elptSDgU+ODAzEsBgqXnkQPbEjvC+Kr9odY0/fwWpG4mh
8/W8q5tyJLKmwFsqcWprNfHK7j5hH7IQtJPNLP4N1r1rf8TeaMgFHfdaSQWvJmqJ
5Jymok2ugbryhwXkSZw9grqAObRyM6LoF1scnhT13jQNFucAPLmk7EpF+JcAy3Il
ozd95EyI
=IAjc
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#971305 closed by Debian FTP Masters (reply to Francisco Vilmar Cardoso Ruviaro ) (Bug#971305: fixed in patator 0.9-2)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #971305 [src:patator] patator: Switch to python3-pycryptodome
Added tag(s) patch.

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

Bug#971305: closed by Debian FTP Masters (reply to Francisco Vilmar Cardoso Ruviaro ) (Bug#971305: fixed in patator 0.9-2)

[Sebastian Ramacher]

Control: tags -1 patch

On 2021-01-10 23:37:15 +0100, Sebastian Ramacher wrote:
> Control: reopen -1
> Control: severity -1 serious
> Control: block 979318 by -1
> 
> This wasn't enough. The binary package still depends on python3-crypto.
> Hence I'm reopening the bug.

The attached patch should fix this issue.

Cheers
-- 
Sebastian Ramacher
diff -Nru patator-0.9/debian/patches/pycryptodome.patch patator-0.9/debian/patches/pycryptodome.patch
--- patator-0.9/debian/patches/pycryptodome.patch	1970-01-01 01:00:00.0 +0100
+++ patator-0.9/debian/patches/pycryptodome.patch	2021-01-11 00:08:20.0 +0100
@@ -0,0 +1,22 @@
+--- patator-0.9.orig/patator.py
 patator-0.9/patator.py
+@@ -4196,7 +4196,7 @@ class RDP_login:
+ 
+ # VNC {{{
+ try:
+-  from Crypto.Cipher import DES
++  from Cryptodome.Cipher import DES
+ except ImportError:
+   notfound.append('pycrypto')
+ 
+--- patator-0.9.orig/requirements.txt
 patator-0.9/requirements.txt
+@@ -6,7 +6,7 @@ pyopenssl
+ #cx_Oracle # non free dependencies
+ mysqlclient
+ psycopg2-binary
+-pycrypto
++pycryptodomex
+ dnspython
+ IPy
+ pysnmp
diff -Nru patator-0.9/debian/patches/series patator-0.9/debian/patches/series
--- patator-0.9/debian/patches/series	2020-09-29 23:39:54.0 +0200
+++ patator-0.9/debian/patches/series	2021-01-11 00:08:15.0 +0100
@@ -1,2 +1,3 @@
 remove-cx-oracle-depencency.patch
 Improve-usage-output-to-report-correct-executable-name.patch
+pycryptodome.patch


signature.asc
Description: PGP signature

Processed: tagging 979733, bug 979733 is forwarded to https://github.com/wfx/teg/issues/25

[Debian Bug Tracking System]

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

> tags 979733 + ftbfs
Bug #979733 [teg] teg: FTBFS on several architectures
Added tag(s) ftbfs.
> forwarded 979733 https://github.com/wfx/teg/issues/25
Bug #979733 [teg] teg: FTBFS on several architectures
Set Bug forwarded-to-address to 'https://github.com/wfx/teg/issues/25'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#971303 closed by Debian FTP Masters (reply to Josue Ortega ) (Bug#971303: fixed in python-file-encryptor 0.2.9-4)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #971303 [src:python-file-encryptor] python-file-encryptor: Switch to 
python3-pycryptodome
Added tag(s) patch.

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

Bug#971303: closed by Debian FTP Masters (reply to Josue Ortega ) (Bug#971303: fixed in python-file-encryptor 0.2.9-4)

[Sebastian Ramacher]

Control: tags -1 + patch

On 2021-01-10 23:39:22 +0100, Sebastian Ramacher wrote:
> Control: reopen -1
> Control: severity -1 serious
> Control: block 971303 by -1
> 
> It looks like the fix wasn't enough. The binary package still depends on 
> python3-crypto.

The attached patch should fix the issue.

Cheers
-- 
Sebastian Ramacher
diff -Nru python-file-encryptor-0.2.9/debian/control python-file-encryptor-0.2.9/debian/control
--- python-file-encryptor-0.2.9/debian/control	2020-09-29 03:32:40.0 +0200
+++ python-file-encryptor-0.2.9/debian/control	2021-01-10 23:58:13.0 +0100
@@ -5,6 +5,7 @@
 Build-Depends: debhelper-compat (= 13),
  dh-python,
  python3-all,
+ python3-pycryptodome,
  python3-setuptools
 Standards-Version: 4.5.0
 Homepage: https://pypi.python.org/pypi/file_encryptor
@@ -15,8 +16,7 @@
 
 Package: python3-file-encryptor
 Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends},
- python3-pycryptodome
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Python 3 module to convergently encrypt and decrypt files
  This Python 3 module contains helper methods to encrypt and decrypt files
  inline (without using extra space) and to decrypt streams.
diff -Nru python-file-encryptor-0.2.9/debian/patches/pycryptodome.patch python-file-encryptor-0.2.9/debian/patches/pycryptodome.patch
--- python-file-encryptor-0.2.9/debian/patches/pycryptodome.patch	1970-01-01 01:00:00.0 +0100
+++ python-file-encryptor-0.2.9/debian/patches/pycryptodome.patch	2021-01-10 23:58:13.0 +0100
@@ -0,0 +1,24 @@
+--- python-file-encryptor-0.2.9.orig/file_encryptor/convergence.py
 python-file-encryptor-0.2.9/file_encryptor/convergence.py
+@@ -23,8 +23,8 @@
+ # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ # SOFTWARE.
+ 
+-from Crypto.Cipher import AES
+-from Crypto.Util import Counter
++from Cryptodome.Cipher import AES
++from Cryptodome.Util import Counter
+ from file_encryptor.settings import CHUNK_SIZE
+ 
+ from file_encryptor import key_generators
+--- python-file-encryptor-0.2.9.orig/setup.py
 python-file-encryptor-0.2.9/setup.py
+@@ -38,7 +38,7 @@ else:
+ VERSION = '0.2.9'
+ 
+ install_requirements = [
+-'pycrypto>=2.6.1'
++'pycryptodomex'
+ ]
+ 
+ test_requirements = [
diff -Nru python-file-encryptor-0.2.9/debian/patches/series python-file-encryptor-0.2.9/debian/patches/series
--- python-file-encryptor-0.2.9/debian/patches/series	2020-09-29 03:32:40.0 +0200
+++ python-file-encryptor-0.2.9/debian/patches/series	2021-01-10 23:58:13.0 +0100
@@ -1,2 +1,3 @@
 00-fix-readme-bad-import.patch
 00-fix-encoding.patch
+pycryptodome.patch


signature.asc
Description: PGP signature

Processed: block 972184 with 971305 971303

[Debian Bug Tracking System]

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

> block 972184 with 971305 971303
Bug #972184 [src:python-crypto] python-crypto: do not release with bullseye
972184 was blocked by: 971316 971294 971308 971292 971313 971296 971293 971289 
971301 971309 971297 971300 971317 971304 971298 971302 971290 971311 979734 
971291 971315 971310 971307 971299
972184 was not blocking any bugs.
Added blocking bug(s) of 972184: 971305 and 971303
> thanks
Stopping processing here.

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

Processed: block 979318 with 971303

[Debian Bug Tracking System]

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

> block 979318 with 971303
Bug #979318 [ftp.debian.org] RM: python-crypto -- ROM; unmaintained upstream, 
replaced by pycryptodome
979318 was blocked by: 971296 971299 971316 971289 971308 971309 971297 971305 
971311 979734 971291
979318 was not blocking any bugs.
Added blocking bug(s) of 979318: 971303
> thanks
Stopping processing here.

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

Bug#971299: onionshare: Switch to python3-pycryptodome

[Sebastian Ramacher]

On 2020-10-05 15:18:46 +0200, Clément Hermann wrote:
> 
> Hi,
> 
> Control: block 971299 with 886291
> thanks
> 
> On 28/09/2020 23:29, Sebastian Ramacher wrote:
> > Source: onionshare
> > Version: 2.2-2
> > Severity: important
> > Tags: sid bullseye
> > Usertags: pycrypto
> > 
> > Dear maintainer,
> > 
> > onionshare currently Build-Depends or Depends on python3-crypto from
> > PyCrypto. This project is no longer maintained and PyCryptodome
> > (https://www.pycryptodome.org/en/latest/) provides a drop in
> > replacement. Please switch to python3-pycryptodome. I'd like to
> > remove python-crypto before the release of bullseye.
> 
> 
> As far as I understand it, pycryptodome *can* be a drop-in replacement
> usually, but not currently in Debian since it doesn't install in Crypto
> but Cryptodomex namespace (#886291).
> 
> Are there any plan to change it when python3-crypto is removed or before ?
> 
> Of course, we can patch onionshare to import cryptodomex, but that patch
> would be debian-only then… Upstream already expect pycryptodome as
> Crypto module.

Sorry for the delay. I don't have any plans other than removing
python3-crypto. CCing the pycryptodome maintainer for more input.

Cheers

> 
> Take care,
> 
> -- 
> nodens

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#971303 closed by Debian FTP Masters (reply to Josue Ortega ) (Bug#971303: fixed in python-file-encryptor 0.2.9-4)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #971303 {Done: Josue Ortega } [src:python-file-encryptor] 
python-file-encryptor: Switch to python3-pycryptodome
'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 python-file-encryptor/0.2.9-4.
> severity -1 serious
Bug #971303 [src:python-file-encryptor] python-file-encryptor: Switch to 
python3-pycryptodome
Severity set to 'serious' from 'important'
> block 971303 by -1
Bug #971303 [src:python-file-encryptor] python-file-encryptor: Switch to 
python3-pycryptodome
Failed to set blocking bugs of 971303: It is nonsensical for a bug to block 
itself (or a merged partner): 971303.


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

Processed: Re: Bug#971305 closed by Debian FTP Masters (reply to Francisco Vilmar Cardoso Ruviaro ) (Bug#971305: fixed in patator 0.9-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #971305 {Done: Francisco Vilmar Cardoso Ruviaro 
} [src:patator] patator: Switch to 
python3-pycryptodome
'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 patator/0.9-2.
> severity -1 serious
Bug #971305 [src:patator] patator: Switch to python3-pycryptodome
Severity set to 'serious' from 'important'
> block 979318 by -1
Bug #979318 [ftp.debian.org] RM: python-crypto -- ROM; unmaintained upstream, 
replaced by pycryptodome
979318 was blocked by: 971309 971297 971289 971296 971308 971316 971299 971291 
979734 971311
979318 was not blocking any bugs.
Added blocking bug(s) of 979318: 971305

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

Processed: calibre: remove python3-crypto from (Build-)Depends

[Debian Bug Tracking System]

Processing control commands:

> block 972184 by -1
Bug #972184 [src:python-crypto] python-crypto: do not release with bullseye
972184 was blocked by: 971298 971302 971297 971296 971291 971310 971301 971292 
971313 971307 971308 971294 971300 971299 971293 971315 971289 971317 971311 
971290 971304 971309 971316
972184 was not blocking any bugs.
Added blocking bug(s) of 972184: 979734
> block 979318 by -1
Bug #979318 [ftp.debian.org] RM: python-crypto -- ROM; unmaintained upstream, 
replaced by pycryptodome
979318 was blocked by: 971289 971297 971299 971309 971296 971316 971311 971291 
971308
979318 was not blocking any bugs.
Added blocking bug(s) of 979318: 979734

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

Bug#979734: calibre: remove python3-crypto from (Build-)Depends

[Sebastian Ramacher]

Source: calibre
Version: 5.8.1+dfsg+fontFix-1
Severity: serious 
X-Debbugs-Cc: sramac...@debian.org
Control: block 972184 by -1
Control: block 979318 by -1

We will remove python3-crypto from bullseye. It is unmaintained and a
replacement is available via python3-pycryptodome. calibre only uses any
module from python3-crypto in src/calibre/test_build.py to check if is
installed. No other code in calibre uses python3-crypto. So I recommend
to simply remove this check and drop the dependencies.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: closing 971316

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #971316 {Done: Federico Ceratto } [src:onionbalance] 
onionbalance: Switch to python3-pycryptodome
Bug reopened
Ignoring request to alter fixed versions of bug #971316 to the same values 
previously set
> severity -1 serious
Bug #971316 [src:onionbalance] onionbalance: Switch to python3-pycryptodome
Severity set to 'serious' from 'important'
> block 979318 by -1
Bug #979318 [ftp.debian.org] RM: python-crypto -- ROM; unmaintained upstream, 
replaced by pycryptodome
979318 was blocked by: 971297 971311 971308 971299 971296 971309 971291 971289
979318 was not blocking any bugs.
Added blocking bug(s) of 979318: 971316

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

Bug#957902: marked as done (uronode: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 22:19:56 +
with message-id 
and subject line Bug#957902: fixed in uronode 2.12-1
has caused the Debian Bug report #957902,
regarding uronode: 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.)


-- 
957902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uronode
Version: 2.10-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/uronode_2.10-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

[...]
system.c:108:5: warning: ignoring return value of ‘chown’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  108 | chown(ptyname, 0, 0);
  | ^~~~
system.c: In function ‘login_open’:
system.c:169:5: warning: ignoring return value of ‘dup’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  169 | dup(0);
  | ^~
system.c:170:5: warning: ignoring return value of ‘dup’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  170 | dup(0);
  | ^~
system.c:205:5: warning: ignoring return value of ‘setgid’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  205 | setgid(pw->pw_gid);
  | ^~
system.c:206:5: warning: ignoring return value of ‘setuid’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  206 | setuid(pw->pw_uid);
  | ^~
system.c:269:4: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  269 |write(ptyfd, buf, cnt);
  |^~
system.c: In function ‘lastlog’:
system.c:538:3: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  538 |   write(last, (char *), sizeof(ll));
  |   ^~~~
ipc.c: In function ‘usr2_handler’:
ipc.c:41:7: warning: implicit declaration of function ‘node_prompt’ 
[-Wimplicit-function-declaration]
   41 |   node_prompt();
  |   ^~~
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c axdigi.c
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c calibrate.c
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c flexd.c
flexd.c: In function ‘download_dest’:
flexd.c:146:5: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  146 | write(STDOUT_FILENO, buffer, strlen(buffer));
  | ^~~~
flexd.c:155:5: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  155 | write(STDOUT_FILENO, buffer, strlen(buffer));
  | ^~~~
flexd.c:170:5: warning: ignoring return value of ‘write’ declared with 
attribute 

Bug#979733: teg: FTBFS on several architectures

[Markus Koschany]

Package: teg
Version: 0.12.0-1
Severity: serious


teg 0.12.0-1 FTBFS on several architectures. We are aware of the
problem which has been reported upstream.

https://github.com/wfx/teg/issues/25

Bug#979664: marked as done (apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 22:03:44 +
with message-id 
and subject line Bug#979664: fixed in apache2 2.4.46-3
has caused the Debian Bug report #979664,
regarding apache2: autopkgtest regression in testing: Failed test 2 in 
t/modules/data.t at line 21
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.)


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

Dear maintainer(s),

With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. 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

https://ci.debian.net/data/autopkgtest/testing/amd64/a/apache2/9549366/log.gz

# Failed test 2 in t/modules/data.t at line 21
t/modules/data.t 
Failed 1/2 subtests

[...]

Test Summary Report
---
t/modules/data.t  (Wstat: 0 Tests: 2 Failed: 1)
  Failed test:  2
Files=134, Tests=10102, 318 wallclock secs ( 3.23 usr  0.30 sys + 201.11
cusr 50.96 csys = 255.60 CPU)
Result: FAIL
Failed 1/134 test programs. 1/10102 subtests failed.
[warning] server localhost:8529 shutdown
[  error] error running tests (please examine t/logs/error_log)




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.46-3
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
apache2, 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.
Xavier Guimard  (supplier of updated apache2 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, 10 Jan 2021 22:43:21 +0100
Source: apache2
Architecture: source
Version: 2.4.46-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Xavier Guimard 
Closes: 979664
Changes:
 apache2 (2.4.46-3) unstable; urgency=medium
 .
   * Remove postinst/preinst hooks concerning old versions
   * Clean include-binaries
   * Enable verbose test output during autopkgtest
   * Declare compliance with policy 4.5.1
   * Add debian/gbp.conf
   * Disable temporary 3 subtests (Closes: #979664)
Checksums-Sha1: 
 6bf824d61bc85cc75b85a69e69aec986378f34f0 3501 apache2_2.4.46-3.dsc
 8e7e2343d600972f54ba17aa97b7ab453fc580e1 882256 apache2_2.4.46-3.debian.tar.xz
Checksums-Sha256: 
 05761e086ca7c5594514185d0ab1d0f1a6105f67902c7072997d733d9b4876ea 3501 
apache2_2.4.46-3.dsc
 e2fe07898776cc81fe557875c574ec95b4dcfc57f6f9f66b4a262d14c5eb595c 882256 
apache2_2.4.46-3.debian.tar.xz
Files: 
 1bdec13f3941b20b3336ccfee6480a41 3501 httpd optional apache2_2.4.46-3.dsc
 b0f79ede1093465d6538ced4075c7dfd 882256 httpd optional 
apache2_2.4.46-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/7dh8ACgkQ9tdMp8mZ
7ulIrBAAmnhC/wEm369vdTbeGw7mCmF7vTaOnIH5PrlbGIz2SdLSWma3lBtnYTK3
sD1UZZYzc0uSrwSdeHzaK+TUWw+j5MMmU5xQ4ruugugR/IRbAR6he/xPRy4mLxfy
vCZYpjcasIGrDQf2C507DT/+errFPx755U7kx6CxhiGQTXbFLg3u4WgyF3R010Ef
/M4WDfD3tscw+oh3TnF5dK0IV/LMcxBQK9PrsgF/zPZGiNkp1UThorFPqwN5TRNi
vW3PrMnGPMkPk+3/jhFSSDfT2irz9suLjuZzNmGqBjZmtl2B737OrGujoR+KVTfV
aw3XRm8d9dP5g0wY5vNvWR1Tw8ThH5Gyj0mWE/olXcfSHC23oJbMcCwueXTh3IEM
WJ7PyuCQIXjz/Vupx/fiLJNXvLBlMnW180lEdEMdcYnIasY9FZRvcZ1FKHrXmwpD
ra5aodhdZoyCta7lIqeDkswnHDAcSRc622dApcurYatx7BVwQ8AeFWIAnH42FQ2q
yXlwknvq8opQg/NGYFLt7wrZnq73MEy7TkwlFZSQACkg5KiCom21DlUQF6auxiUM
I+plXZLjo2pqTnHOtJ3TLkNfohHFGRKId50OavCGkV/PVtxb13lVtW5MGaHgT3+F
voWrYv7hFWAPnxOPRKs5ATwtlKXn3iCDfAKfQOUsl6B3HKyL/gg=
=pQOe
-END PGP SIGNATURE End Message ---

Bug#961932: marked as done (nethack-lisp: broken and unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 22:00:13 +
with message-id 
and subject line Bug#961932: fixed in nethack 3.6.6-2
has caused the Debian Bug report #961932,
regarding nethack-lisp: broken 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.)


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

I have just updated nethack to the latest upstream version to fix
several security vulnerabilities and a compilation error with GCC 10.
Unfortunately the Debian specific lisp patches don't work anymore with
the current release. I could fix a few minor errors but there are more
issues and I'm not really interested in maintaining a fork of nethack.
Though I guess someone else can fix it. I have pushed all lisp related
patches to a new lisp branch in Git.

I wonder if we should drop nethack-lisp completely or try to upstream
the code. It is quite obvious that the additional work to make the
lisp port work prevents more regular updates.
--- End Message ---
--- Begin Message ---
Source: nethack
Source-Version: 3.6.6-2
Done: Reiner Herrmann 

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated nethack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Jan 2021 16:34:33 +0100
Source: nethack
Binary: nethack-common nethack-common-dbgsym nethack-console 
nethack-console-dbgsym nethack-qt nethack-qt-dbgsym nethack-x11 
nethack-x11-dbgsym
Architecture: source amd64
Version: 3.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Reiner Herrmann 
Description:
 nethack-common - dungeon crawl game - common files
 nethack-console - dungeon crawl game - text-based interface
 nethack-qt - dungeon crawl game - Qt interface
 nethack-x11 - dungeon crawl game - X11 interface
Closes: 770749 961932
Changes:
 nethack (3.6.6-2) unstable; urgency=medium
 .
   * Team upload.
   * Re-enable the Qt interface, which now supports Qt5. (Closes: #770749)
   * Drop nethack-lisp which is broken and unmaintained. (Closes: #961932)
   * Enable support for curses windowtype in nethack-console.
   * Enable hitpointbar in nethack-console.
   * Enable all hardening options.
   * Bump Standards-Version to 4.5.1.
Checksums-Sha1:
 0d2f88f14ef7b2f92dc16fd0997bbd19f1fe570a 2473 nethack_3.6.6-2.dsc
 7f7cc74e189a27e326051ff5fb15e645d4e2fdcd 50040 nethack_3.6.6-2.debian.tar.xz
 05ac42968ab1509174522f28754426794e224576 163180 
nethack-common-dbgsym_3.6.6-2_amd64.deb
 85f655444d6a9a4312727804a4d48b954132f125 632136 
nethack-common_3.6.6-2_amd64.deb
 a97879edbfce2ebf3de2fad848d7ea4c369c1f88 2396808 
nethack-console-dbgsym_3.6.6-2_amd64.deb
 143218cd3cd8436241dd29f05f7f24113fa4fdd7 1248136 
nethack-console_3.6.6-2_amd64.deb
 61d4c0ed2f5cfd5a5fe4c7ade13512b1566e158a 3878316 
nethack-qt-dbgsym_3.6.6-2_amd64.deb
 0f7ca538b9d755f2c8818a625acebc32986c4d04 1256644 nethack-qt_3.6.6-2_amd64.deb
 67b1e028a571179d0c9ee8c13b7689bd0d0d706f 2450780 
nethack-x11-dbgsym_3.6.6-2_amd64.deb
 1681989b7787575060604ca271aef9ea21226c36 1278556 nethack-x11_3.6.6-2_amd64.deb
 c146eae510c29e8ffe65ccfd300b7a2e918800c8 14031 nethack_3.6.6-2_amd64.buildinfo
Checksums-Sha256:
 2576940f85e4fdd0f8723071307bf7db092385ddfc7164ac76611cf61c84430b 2473 
nethack_3.6.6-2.dsc
 f5bbf1d1d2da94bedf7227cb1735d4bbe39a354511668e708bac4d59771e84a6 50040 
nethack_3.6.6-2.debian.tar.xz
 56ad2efc823530991af4c360f03da5bea70e1e6ac4f6b8f343d736bfd37d6b71 163180 
nethack-common-dbgsym_3.6.6-2_amd64.deb
 9ab03a4dd048e1762c9af72cd27b2503f61a588c341d6c21585db8ec94cd4912 632136 
nethack-common_3.6.6-2_amd64.deb
 237a884ab6673fd0eb5ab2b38af9ac1ff212b03a0217dd7c684fadbe1e6917bb 2396808 
nethack-console-dbgsym_3.6.6-2_amd64.deb
 83a027ceccf8acb6a5d13b7aa17b85fc2f4ab03a9397440f84dca72c910096e7 1248136 
nethack-console_3.6.6-2_amd64.deb
 

Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman

[Agustin Martin]

El dom, 10 ene 2021 a las 22:39, Robert Luberda () escribió:
>
> reassign 979549 ispell 3.4.01-1
> reassign 979565 ispell 3.4.01-1
> forcemerge 979575 979549 979565
> affects 979575 ingerman iogerman ifrench iesperanto iswiss
> tags 979575 pending fixed-upstream
> thanks
>
>
> Roland Rosenfeld pisze:
> >
> > In the meantime upstream maintainer released a version 3.4.02 on
>
> Yes, I've noticed it this morning, and it looks like upgrading to that
> version fixes the issue.

This may also be causing #979694.

Regards,

Bug#979664: marked as pending in apache2

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #979664 in apache2 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/apache-team/apache2/-/commit/ac6936d8a7058b01a147475a5f004c8de6388045


Disable temporary 3 subtests

Closes: #979664


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/979664

Processed: Bug#979664 marked as pending in apache2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979664 [src:apache2] apache2: autopkgtest regression in testing: Failed 
test 2 in t/modules/data.t at line 21
Added tag(s) pending.

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

Processed: Re: Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman

[Debian Bug Tracking System]

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

> reassign 979549 ispell 3.4.01-1
Bug #979549 [ingerman] ingerman: Problems during ispell-autobuild
Bug reassigned from package 'ingerman' to 'ispell'.
No longer marked as found in versions igerman98/20161207-8.
Ignoring request to alter fixed versions of bug #979549 to the same values 
previously set
Bug #979549 [ispell] ingerman: Problems during ispell-autobuild
Marked as found in versions ispell/3.4.01-1.
> reassign 979565 ispell 3.4.01-1
Bug #979565 [iogerman] /usr/lib/ispell/ogerman.aff: multiple errors
Bug reassigned from package 'iogerman' to 'ispell'.
No longer marked as found in versions hkgerman/1:2-37.
Ignoring request to alter fixed versions of bug #979565 to the same values 
previously set
Bug #979565 [ispell] /usr/lib/ispell/ogerman.aff: multiple errors
Marked as found in versions ispell/3.4.01-1.
> forcemerge 979575 979549 979565
Bug #979575 [ispell] ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Bug #979565 [ispell] /usr/lib/ispell/ogerman.aff: multiple errors
Severity set to 'serious' from 'important'
Added tag(s) upstream.
Bug #979549 [ispell] ingerman: Problems during ispell-autobuild
Severity set to 'serious' from 'normal'
Added tag(s) upstream.
Merged 979549 979565 979575
> affects 979575 ingerman iogerman ifrench iesperanto iswiss
Bug #979575 [ispell] ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Bug #979549 [ispell] ingerman: Problems during ispell-autobuild
Bug #979565 [ispell] /usr/lib/ispell/ogerman.aff: multiple errors
Added indication that 979575 affects ingerman, iogerman, ifrench, iesperanto, 
and iswiss
Added indication that 979549 affects ingerman, iogerman, ifrench, iesperanto, 
and iswiss
Added indication that 979565 affects ingerman, iogerman, ifrench, iesperanto, 
and iswiss
> tags 979575 pending fixed-upstream
Bug #979575 [ispell] ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Bug #979549 [ispell] ingerman: Problems during ispell-autobuild
Bug #979565 [ispell] /usr/lib/ispell/ogerman.aff: multiple errors
Added tag(s) pending and fixed-upstream.
Added tag(s) pending and fixed-upstream.
Added tag(s) pending and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman

[Robert Luberda]

reassign 979549 ispell 3.4.01-1
reassign 979565 ispell 3.4.01-1
forcemerge 979575 979549 979565
affects 979575 ingerman iogerman ifrench iesperanto iswiss
tags 979575 pending fixed-upstream
thanks


Roland Rosenfeld pisze:
> 
> In the meantime upstream maintainer released a version 3.4.02 on

Yes, I've noticed it this morning, and it looks like upgrading to that
version fixes the issue.


Regards,
Robert

Bug#979639: src:sauce: invalid maintainer address

[Baptiste Beauplat]

Hi Ian,

On Sat, 09 Jan 2021 18:01:02 +0100 Ansgar  wrote:
> Source: sauce
> Version: 0.9.0
> Severity: serious
> Tags: bullseye sid
> 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, 09 Jan 2021 16:53:55 +

I'm Cc'ing you manually on this bug since you are the maintainer but the
email is incorrect (i...@davenant.greenend.org.uk).

Let me know if you don't have time to attend to it, I'll do an NMU with
your address fixed.

Best,
-- 
Baptiste Beauplat - lyknode



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977056: beanbag FTBFS with pytest 6

[s3v]

Dear Maintainer,

please find attached a patch to make tests able to pass.

Kind Regards
Index: beanbag-1.9.2/tests/test_attrdict.py
===
--- beanbag-1.9.2.orig/tests/test_attrdict.py
+++ beanbag-1.9.2/tests/test_attrdict.py
@@ -16,7 +16,8 @@ def test_manipulation():
 ad.foo.baz = "yaa"
 
 assert +ad.foo == {"bar": "hello, world", "baz": "yaa"}
-py.test.raises(KeyError, "str(ad.c.x.y.z)")
+with py.test.raises(KeyError):
+str(ad.c.x.y.z)
 
 ad.c.x.y.z = 3
 assert ad.c.x.y.z == 3
@@ -28,6 +29,7 @@ def test_manipulation():
 del ad.c.x
 assert +ad == {"a": 1, "b": "blat", "c": {"d": "e"}}
 
-py.test.raises(KeyError, "del ad.bar.baz")
+with py.test.raises(KeyError):
+del ad.bar.baz
 
 assert +ad is j

Bug#979727: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory

[Sebastian Ramacher]

Source: racon
Version: 1.4.13-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

|  28%] Building CXX object CMakeFiles/racon.dir/src/main.cpp.o
| /usr/bin/c++ -DRACON_VERSION=\"v1.4.13\" -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/config -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pedantic 
-pthread -std=c++11 -o CMakeFiles/racon.dir/src/main.cpp.o -c 
/<>/src/main.cpp
| /<>/test/racon_test.cpp:13:10: fatal error: 
bioparser/bioparser.hpp: No such file or directory
|13 | #include "bioparser/bioparser.hpp"
|   |  ^
| compilation terminated.
| make[3]: *** [CMakeFiles/racon_test.dir/build.make:85: 
CMakeFiles/racon_test.dir/test/racon_test.cpp.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| [ 35%] Building CXX object CMakeFiles/racon.dir/src/logger.cpp.o
| /usr/bin/c++ -DRACON_VERSION=\"v1.4.13\" -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/config -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pedantic 
-pthread -std=c++11 -o CMakeFiles/racon.dir/src/logger.cpp.o -c 
/<>/src/logger.cpp
| /<>/src/polisher.cpp:20:10: fatal error: 
bioparser/bioparser.hpp: No such file or directory
|20 | #include "bioparser/bioparser.hpp"
|   |  ^
| compilation terminated.
| make[3]: *** [CMakeFiles/racon_test.dir/build.make:111: 
CMakeFiles/racon_test.dir/src/polisher.cpp.o] Error 1
| [ 42%] Building CXX object CMakeFiles/racon.dir/src/polisher.cpp.o
| /usr/bin/c++ -DRACON_VERSION=\"v1.4.13\" -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/config -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pedantic 
-pthread -std=c++11 -o CMakeFiles/racon.dir/src/polisher.cpp.o -c 
/<>/src/polisher.cpp
| /<>/src/polisher.cpp:20:10: fatal error: 
bioparser/bioparser.hpp: No such file or directory
|20 | #include "bioparser/bioparser.hpp"
|   |  ^
| compilation terminated.
| make[3]: *** [CMakeFiles/racon.dir/build.make:111: 
CMakeFiles/racon.dir/src/polisher.cpp.o] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=racon=amd64=1.4.13-2%2Bb1=1610291712=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#978002: marked as done (clfft: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 19:48:17 +
with message-id 
and subject line Bug#978002: fixed in clfft 2.12.2-3.1
has caused the Debian Bug report #978002,
regarding clfft: autopkgtest regression
to be marked as done.

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

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


-- 
978002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clfft
Version: 2.12.2-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

clfft is unable to migrate to testing due to autopkgtest regressions:
| autopkgtest [23:13:07]: test build-examples: [---
| cp: cannot stat '/usr/share/doc/libclfft-doc/examples/*': No such file or 
directory
| autopkgtest [23:13:08]: test build-examples: ---]
| autopkgtest [23:13:08]: test build-examples:  - - - - - - - - - - results - - 
- - - - - - - -
| build-examples   FAIL non-zero exit status 1

https://ci.debian.net/data/autopkgtest/testing/amd64/c/clfft/9036543/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: clfft
Source-Version: 2.12.2-3.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated clfft 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, 10 Jan 2021 20:36:30 +0100
Source: clfft
Architecture: source
Version: 2.12.2-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 978002
Changes:
 clfft (2.12.2-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/tests/build-examples: Fix path of examples after debhelper compat
 bump (Closes: #978002)
Checksums-Sha1:
 fe68a14d032cda7141fdcec515eb874bbe1dc282 2314 clfft_2.12.2-3.1.dsc
 b738fb5a87a2961bd468e2569cbb4a6690b850d7 8064 clfft_2.12.2-3.1.debian.tar.xz
Checksums-Sha256:
 4721ef23a94b2bc8c2128f1be70f52d59ff1afd3a315d8edba519b14f0fdc39c 2314 
clfft_2.12.2-3.1.dsc
 30e7185cf281c3f9902af88c0d58467fb063b831e4ce48687e74322532391c8d 8064 
clfft_2.12.2-3.1.debian.tar.xz
Files:
 e29d395aa16a064f6aa7324f7883bc8c 2314 science optional clfft_2.12.2-3.1.dsc
 2ab9bc558a6b8f1f15c22790bcf763f3 8064 science optional 
clfft_2.12.2-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl/7WQoACgkQafL8UW6n
GZMLVhAAx2ukvMtcwRvB8CtjsL31tgBA4jUcTKTgueGpGGPWeZMB08cJcLhCG8SZ
V2Id84fLtTzfgNbIDH1uoBJBn0A9IeTKLpGAzyLfe0fq+5/gw9jOIp0YnokCDm/n
e8RzGx1lN7co7c9dkspTRuvbxkgFMhwlykxl85b73dBtMWbquiYOrxpKRymfxxhX
fTh9uBdPTDP45Kq6E3SqBHCfW4yLrX9nUeJfnpaFP/M7Aoqzcri8cuXBCekDDfqV
nPvFiKGeO1BMlCbSa/H0yqpmC/dhmDsOIHagJRuhM/Q1++YWpsODlo+QsXd+mKl6
oAizTcBDsa3NIqBcR5OlrEf0+BvqiwBLtYeI7SL4uMc2Qru8MmvG1lmn6YbN8Kx6
sg/WoSwusAPARYUHSPrFF+em6s+KnEPAnzmK1dFvGfng18qrHT8/TONXLKi0wdCY
5Io20MijdR0SxyqQJRPCOsJSxwrhzqrjurdVCMuVSniuj2eEi/MT6pUYlyR/o0md
QgKIJeEt5jnW6bsJq3fc1/MH/I6P8Vv9Vxj3m9azIgJ78SltODzq/DXXnwQsWFQ7
W/H8SR4zZrom7T4ZDMU8PBhwiPOy4rTID++t/Td8GxgSXPY5qjNthPeBtfeSCqpG
DuV9lo36tIL486yeBN1Sg5scWMhQARAtGXlR6jHmPZiUMb8wVw0=
=dUPZ
-END PGP SIGNATURE End Message ---

Bug#978002: clfft: diff for NMU version 2.12.2-3.1

[Sebastian Ramacher]

Control: tags 978002 + patch

Dear maintainer,

I've prepared an NMU for clfft (versioned as 2.12.2-3.1). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru clfft-2.12.2/debian/changelog clfft-2.12.2/debian/changelog
--- clfft-2.12.2/debian/changelog	2020-12-08 20:41:18.0 +0100
+++ clfft-2.12.2/debian/changelog	2021-01-10 20:36:30.0 +0100
@@ -1,3 +1,11 @@
+clfft (2.12.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/tests/build-examples: Fix path of examples after debhelper compat
+bump (Closes: #978002)
+
+ -- Sebastian Ramacher   Sun, 10 Jan 2021 20:36:30 +0100
+
 clfft (2.12.2-3) unstable; urgency=medium
 
   [ Anton Gladky ]
diff -Nru clfft-2.12.2/debian/.gitlab-ci.yml clfft-2.12.2/debian/.gitlab-ci.yml
--- clfft-2.12.2/debian/.gitlab-ci.yml	2020-12-08 20:24:33.0 +0100
+++ clfft-2.12.2/debian/.gitlab-ci.yml	2021-01-10 20:33:39.0 +0100
@@ -1,3 +1,6 @@
 include:
  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+reprotest:
+  allow_failure: true
diff -Nru clfft-2.12.2/debian/tests/build-examples clfft-2.12.2/debian/tests/build-examples
--- clfft-2.12.2/debian/tests/build-examples	2020-12-08 20:25:28.0 +0100
+++ clfft-2.12.2/debian/tests/build-examples	2021-01-10 20:35:34.0 +0100
@@ -14,7 +14,7 @@
 fi
 
 # Copy example source code.
-cp -a /usr/share/doc/libclfft-doc/examples/* "$AUTOPKGTEST_TMP"
+cp -a /usr/share/doc/libclfft-dev/examples/* "$AUTOPKGTEST_TMP"
 cd "$AUTOPKGTEST_TMP"
 
 # Create the CMake project.


signature.asc
Description: PGP signature

Processed: clfft: diff for NMU version 2.12.2-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 978002 + patch
Bug #978002 [src:clfft] clfft: autopkgtest regression
Added tag(s) patch.

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

Bug#979567: marked as done (src:libnfo: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 19:34:10 +
with message-id 
and subject line Bug#979567: fixed in libnfo 1.0.1-2
has caused the Debian Bug report #979567,
regarding src:libnfo: 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.)


-- 
979567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnfo
Version: 1.0.1-1
Severity: serious
Tags: bullseye sid
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: Fri, 08 Jan 2021 12:52:12 +

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:

  dav...@geexbox.org
host fry.geexbox.org [208.70.252.90]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;davide@geexbox.org
Status: 5.0.0
Remote-MTA: dns; fry.geexbox.org
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table
--- End Message ---
--- Begin Message ---
Source: libnfo
Source-Version: 1.0.1-2
Done: Baptiste Beauplat 

We believe that the bug you reported is fixed in the latest version of
libnfo, 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 libnfo 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, 10 Jan 2021 17:53:23 +0100
Source: libnfo
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Baptiste Beauplat 
Closes: 979567
Changes:
 libnfo (1.0.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Set Debian QA Group as Maintainer (See: #840040) (Closes: #979567)
   * Bump debhelper to 13:
 - Remove d/compat
 - Switch debhelper to debhelper-compat in Build-Depends
   * Move docs to main package's /usr/share/doc/:
 - Use installed docs instead of built one
 - Add a execute_after_dh_auto_install rule to move docs into a html/
   directory
 - Fix paths in doc-base control file
   * Convert copyright to DEP5
   * Update upstream metadata:
 - Move metadata to d/upstream/metadata
 - Contact and Name moved to d/copyright
 - Remove Homepage already present in d/control
 - Remove Watch already present in d/watch
 - Remove dead Donation link
 - Update Repository and Repository-Browse with github repository
 - Add Bug-Database and Bug-Submit using github repository
   * Use https for Homepage in d/control
   * Replace Priority extra by optional
   * Remove libnfo1-dbg in favor of libnfo1-dbgsym:
 - Remove entry from d/control
 - Add version information for debug package migration to dh_strip in
   d/rules
   * Bump Standard-Version to 4.5.1
   * Add Rules-Requires-Root: no
   * Remove the article from the Description
   * Install pkg-config metadata into /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig:
 - Add a execute_after_dh_auto_install rule to move libnfo.pc
 - Update paths in d/libnfo-dev.install
   * Add Build-Depends-Package: info to libnfo1 symbols file
   * Add hardening flags to d/rules
   * Remove trailing whitespace in d/rules
   * Update watch file:
 - Switch to version 4
 - Use the github repository (previous VCS is unavailable)
   * Host packaging on Salsa:
 - Add Salsa CI pipeline
 - Use DEP14 repository layout (gbp.conf added)
 - Add Vcs-* fields
   * Remove unused d/*.dirs
Checksums-Sha1:
 b7ae33273c28af6cb8ca20d4bec7f4576c2663fd 2017 libnfo_1.0.1-2.dsc
 5861d08225c7820610466bc26681e548bea35f20 4172 libnfo_1.0.1-2.debian.tar.xz
 baeb563f0a8c6349580958637aeb08fa862ec437 7367 

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Am 10.01.21 um 20:02 schrieb Jamie Zawinski:

Why would a xscreensaver instance running for user A have any influence on a 
xscreensaver instance running for user B? That seems absolutely weird to me and 
something I don't understand.


Yeah, that sounds impossible, assuming that the X server has restarted between 
user A and user B.

If things have gone wrong in a weird way, the "xscreensaver-systemd" process of 
user A might linger, but it won't be able to communicate with user B's xscreensaver.


Since Eduard has been claiming this originally:


 - having this xscreensaver hanging around disturbs the startup of
   another xscreensaver process in the new user session


I guess he needs to back this up somehow.
Unfortunately I haven't seen any log files or anything, which would give 
us the opportunity to retrace what's happening.


Michael



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Fix the version information

[Debian Bug Tracking System]

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

> notfound 960451 1.5-1
Bug #960451 {Done: Yao Wei (魏銘廷) } [meteo-qt] meteo-qt: Cannot 
connect to server anymore: version≥1.5 is needed
No longer marked as found in versions meteo-qt/1.5-1.
> fixed 960451 1.5-1
Bug #960451 {Done: Yao Wei (魏銘廷) } [meteo-qt] meteo-qt: Cannot 
connect to server anymore: version≥1.5 is needed
Marked as fixed in versions meteo-qt/1.5-1.
> thanks
Stopping processing here.

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

Processed: severity of 960451 is serious

[Debian Bug Tracking System]

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

> severity 960451 serious
Bug #960451 {Done: Yao Wei (魏銘廷) } [meteo-qt] meteo-qt: Cannot 
connect to server anymore: version≥1.5 is needed
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 957902

[Debian Bug Tracking System]

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

> tags 957902 + patch pending
Bug #957902 [src:uronode] uronode: ftbfs with GCC-10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#957902: uronode: ftbfs with GCC-10

[tony mancill]

On Fri, Jan 08, 2021 at 05:20:27PM -0500, Logan Rosen wrote:
> Package: uronode
> Version: 2.10-1
> Followup-For: Bug #957902
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu hirsute ubuntu-patch
> X-Debbugs-Cc: lo...@ubuntu.com
> Control: tags -1 patch
> 
> Hi,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * d/p/gcc-10.patch: Fix compilation with GCC 10.
> 
> Thanks for considering the patch.
 
Hi Logan,

Thank you for providing the patch.  I see from the VCS [1] that Dave
Hibberd has changes in progress for this package that address the GCC
issue.  I will coordinate with him to either upload 2.12 or apply your
patch to 2.10.

Cheers,
tony

[1] 
https://salsa.debian.org/debian-hamradio-team/uronode/-/commit/a3c68056517b59f29cf9345034143becca48885f


signature.asc
Description: PGP signature

Bug#979562: lightdm session termination does not stop xscreensaver

[Jamie Zawinski]

> Why would a xscreensaver instance running for user A have any influence on a 
> xscreensaver instance running for user B? That seems absolutely weird to me 
> and something I don't understand.

Yeah, that sounds impossible, assuming that the X server has restarted between 
user A and user B.

If things have gone wrong in a weird way, the "xscreensaver-systemd" process of 
user A might linger, but it won't be able to communicate with user B's 
xscreensaver.

--
Jamie Zawinski  https://www.jwz.org/  https://www.dnalounge.com/

Bug#979533: marked as done (chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-21111 CVE-2021-21112 CVE-2021

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 18:49:23 +
with message-id 
and subject line Bug#979520: fixed in chromium 87.0.4280.141-0.1
has caused the Debian Bug report #979520,
regarding chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 
CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 
CVE-2021-2 CVE-2021-21112 CVE-2021-21113 CVE-2021-21114  CVE-2021-21115 
CVE-2021-21116)
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.)


-- 
979520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chromium
Version: 87.0.4280.88-0.4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 87.0.4280.88-0.4~deb10u1

Hi

Please see
https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html
here is a new round of CVE fixes for chromium accordingly.

CVE-2020-15995 seems a bit unclear, it was previously marked to affect
only Chrome on Android, but now appears to affect as well us.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 87.0.4280.141-0.1
Done: Michel Le Bihan 

We believe that the bug you reported is fixed in the latest version of
chromium, 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.
Michel Le Bihan  (supplier of updated chromium package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Jan 2021 11:24:58 +0100
Source: chromium
Architecture: source
Version: 87.0.4280.141-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michel Le Bihan 
Closes: 979135 979520
Changes:
 chromium (87.0.4280.141-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream security release (closes: 979520).
 - CVE-2021-21106: Use after free in autofill. Reported by Weipeng Jiang
   @Krace from Codesafe Team of Legendsec at Qi'anxin Group
 - CVE-2021-21107: Use after free in drag and drop. Reported by Leecraso and
   Guang Gong of 360 Alpha Lab
 - CVE-2021-21108: Use after free in media. Reported by Leecraso and Guang
   Gong of 360 Alpha Lab
 - CVE-2021-21109: Use after free in payments. Reported by Rong Jian and
   Guang Gong of 360 Alpha Lab
 - CVE-2021-21110: Use after free in safe browsing. Reported by Anonymous
 - CVE-2021-2: Insufficient policy enforcement in WebUI. Reported by
   Alesandro Ortiz
 - CVE-2021-21112: Use after free in Blink. Reported by YoungJoo Lee
   @ashuu_lee of Raon Whitehat
 - CVE-2021-21113: Heap buffer overflow in Skia. Reported by tsubmunu
 - CVE-2020-16043: Insufficient data validation in networking. Reported by
   Samy Kamkar, Ben Seri at Armis, Gregory Vishnepolsky at Armis
 - CVE-2021-21114: Use after free in audio. Reported by Man Yue Mo of GitHub
   Security Lab
 - CVE-2020-15995: Out of bounds write in V8. Reported by Bohan Liu
   @P4nda20371774 of Tencent Security Xuanwu Lab
 - CVE-2021-21115: Use after free in safe browsing. Reported by Leecraso and
   Guang Gong of 360 Alpha Lab
 - CVE-2021-21116: Heap buffer overflow in audio. Reported by Alison
   Huffman, Microsoft Browser Vulnerability Research
 .
   [ Jan Luca Naumann ]
   * Use desktop gl implementation as default. (closes: 979135)
Checksums-Sha1:
 9d83a1d5ad83468c5ba5da045d0235465fe5321b 3576 chromium_87.0.4280.141-0.1.dsc
 ef2fa29cf9558fc0afbd7791ea6ee8ef73ac37af 393840792 
chromium_87.0.4280.141.orig.tar.xz
 aa7529eee2b61d683a4b7640724485be4c7a0778 189436 
chromium_87.0.4280.141-0.1.debian.tar.xz
Checksums-Sha256:
 0e2c2a41c2186a47eb918e3e046ba084ebf96779b282626798f89ebf8d6ee24a 3576 
chromium_87.0.4280.141-0.1.dsc
 577a92da6e3caacd22b0b2aedc9dc7e895652f54ec3e0f615457357be099b2ae 393840792 
chromium_87.0.4280.141.orig.tar.xz
 20c26ad853b88addb65fbb3a26ba92a89f9d47b33297ad6aefdc2c2470550580 189436 
chromium_87.0.4280.141-0.1.debian.tar.xz
Files:
 

Bug#979520: marked as done (chromium: Security upgrade to version 87.0.4280.141)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 18:49:23 +
with message-id 
and subject line Bug#979520: fixed in chromium 87.0.4280.141-0.1
has caused the Debian Bug report #979520,
regarding chromium: Security upgrade to version 87.0.4280.141
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.)


-- 
979520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 87.0.4280.88-0.4
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

there is a security fixed version 87.0.4280.141 of chrome available.

Can you please provide an adapted chromium package.

Thanks in advance.

Regards,
- Sedat -

[1] 
https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html


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

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

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.88-0.4
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-3
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-5
ii  libavformat587:4.3.1-5
ii  libavutil56  7:4.3.1-5
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op1-4
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.2-1
ii  libgcc-s110.2.1-3
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.6.7-1
ii  libicu67 67.1-5
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.9-4+b1
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  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse013.0-5
ii  libre2-9 20201101+dfsg-2
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-3
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-1
ii  libx11-xcb1  2:1.7.0-1
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  87.0.4280.88-0.4

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n87.0.4280.88-0.4
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-3
ii  libx11-62:1.7.0-1
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-sandbox87.0.4280.88-0.4
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.2-1
ii  libgl1-mesa-dri 20.3.2-1
ii  libu2f-udev 1.1.10-1.1
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.20.5-1
ii  system-config-printer   1.5.13-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 87.0.4280.141-0.1
Done: Michel Le Bihan 

We believe that the bug you reported is fixed in the latest version of
chromium, which is due to be installed in 

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Am 10.01.21 um 18:48 schrieb Tormod Volden:

OK, so I guess removing the global user enablement will avoid having
xscreensaver running in lightdm. However, I still wonder if this
lingering service that was observed will also be the case if a user
logs out and another (or same) logs in within 15 seconds? Is there
still an underlying issue here, that can affect security? Is it just
nornal that the systemd user "session" runs for a while after the user
logs out, which would mean the systemd user service is not suited for
this?


systemd --user sends the processes/services SIGTERM when the user 
session ends.

After a timeout, it will forcefully kill any remaining processes.
man systemd.kill has more details (see KillMode)
I have no idea why the xscreensaver process takes 15 secs until it is ended.

What I don't get:
Why would a xscreensaver instance running for user A have any influence 
on a xscreensaver instance running for user B? That seems absolutely 
weird to me and something I don't understand.



Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#966647: marked as done (libetpan: CVE-2020-15953)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 18:03:35 +
with message-id 
and subject line Bug#966647: fixed in libetpan 1.9.4-3
has caused the Debian Bug report #966647,
regarding libetpan: CVE-2020-15953
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.)


-- 
966647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libetpan
Version: 1.9.4-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/dinhvh/libetpan/issues/386
X-Debbugs-Cc: Debian Security Team 

Hi,

The following vulnerability was published for libetpan.

CVE-2020-15953[0]:
| LibEtPan through 1.9.4, as used in MailCore 2 through 0.6.3 and other
| products, has a STARTTLS buffering issue that affects IMAP, SMTP, and
| POP3. When a server sends a "begin TLS" response, the client reads
| additional data (e.g., from a meddler-in-the-middle attacker) and
| evaluates it in a TLS context, aka "response injection."


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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libetpan
Source-Version: 1.9.4-3
Done: Ricardo Mones 

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated libetpan 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: Sun, 10 Jan 2021 18:39:40 +0100
Source: libetpan
Architecture: source
Version: 1.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Closes: 966647
Changes:
 libetpan (1.9.4-3) unstable; urgency=medium
 .
   * Patch from upstream commits fixing CVE-2020-15953 (Closes: #966647)
   * Standards-Version: update to 4.5.1 with no other changes
   * Remove dh_strip override: dbgsym already in stable
   * Raise compat level to 13 and simplify rules
   * Rules-Requires-Root: add field
   * Add patch fixing encoding in some header files
   * Add upstream metadata file
   * Annotate files not installed
Checksums-Sha1:
 361b76a3e5879e6a49c8904e4d4f0a138952304e 2138 libetpan_1.9.4-3.dsc
 0435649f4c221af1a70835be94d46183424d64d9 23252 libetpan_1.9.4-3.debian.tar.xz
 7b749e755e1b61635b008b1598e836e0da83d74f 8069 libetpan_1.9.4-3_amd64.buildinfo
Checksums-Sha256:
 1629fe8ad57accb991d0b4d76e529d84cb02130b2ec55ed37a4ae0eb205e54fc 2138 
libetpan_1.9.4-3.dsc
 a7fdb374d95d4bd59f8b8a4b2c84e749a1d36cfa5bce3cc0c038d6ccdf457f38 23252 
libetpan_1.9.4-3.debian.tar.xz
 6802dea75d5651de6ebb62ee3dc155d952ce33e474c01dc21b0dd5439249001e 8069 
libetpan_1.9.4-3_amd64.buildinfo
Files:
 5a9f65dece7622f480ba2258a0bdad96 2138 mail optional libetpan_1.9.4-3.dsc
 b911a32224cf2deb40961a862b629a57 23252 mail optional 
libetpan_1.9.4-3.debian.tar.xz
 00587267b0b908500b31b7da5ccb156d 8069 mail optional 
libetpan_1.9.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAl/7PQsACgkQHw8KiN5b
zKa4sg//QY0TfyI+WpwGl0zoQzvo0XQf2u0gNUrMxDQOCNOpiNWnP3LL/LtJl0pP
EVO/uraxkaFA8SWLCP2vsnpC2sSbo3Wh+7lhuNqiPqcEXp1qs2naLvNGU48KoUhl
OtyUv761QU+yCMw9+1iDNWaxXz2oM2sAH979kGes14C3JdlyqdDqHYJ/ws3MDsyY
Ke6QULULoGKDv+jdd/l8eqU+vVhJeUy1Ct3Pkf2JeJxjP9Rxg4rjjVQa/xLJNGcH
zzzkp96+x/RKPUttBJ7oOEcKgqPlhqSiZMr58PbRgv4yLiAJHQoPkvuqyLNa067M
ek8GE2+VFz7QzTmHXr6NuyrQK1xj0EPrdrPs4T99Pl1FA80c913+2q1BbzZijAaO
IsBB822osnkptmQ2DI3a7ZHaUWLEXqE4RJrTdyiO5qQPXep65Kad664nUPYPlfAP
Zuze0n1Bc/5jelzkYkcz121cG4GKFklLMfz5OwKlk1LbmPYeVMi4xxHLZzBzwMaW
VNI9l101+FbbNfrHntzpj04UacD+UuHLjebaJEchx5iT8SmSt1hCg00BvS1sIAs0
4T5Lqw6iPsQ5AVfClItpLTs1givbqTa+tmjD08/kWYFXCH5ygdY6+lQnuYko/hZz
icv9v2iJZeElzWcMzYzPnP0rNwbncGtJ8OCjdIuf5OWBCHxF/HI=
=nBk0
-END PGP SIGNATURE End 

Bug#979719: socat in experimental is obsolete and no installable

[Eric Valette]

Package: socat
Version: 2.0.0~beta9-1 1
Severity: grave
Justification: renders package unusable

I can no more be installed

apt-get -t experimental install socat
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 socat : Depends: libssl1.0.2 (>= 1.0.2d) but it is not installable

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

Kernel: Linux 5.10.6 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages socat depends on:
ii  libc6  2.31-9
ii  libssl1.1  1.1.1i-1
ii  libwrap0   7.6.q-31

socat recommends no packages.

socat suggests no packages.

-- no debconf information

Bug#979562: lightdm session termination does not stop xscreensaver

[Tormod Volden]

OK, so I guess removing the global user enablement will avoid having
xscreensaver running in lightdm. However, I still wonder if this
lingering service that was observed will also be the case if a user
logs out and another (or same) logs in within 15 seconds? Is there
still an underlying issue here, that can affect security? Is it just
nornal that the systemd user "session" runs for a while after the user
logs out, which would mean the systemd user service is not suited for
this?

Also, Michael asked "Is xscreensaver really usable as a per user
service or should it be per session?". How can it be run per session?
Would it mean getting graphical-session.target to work for non-Gnome
sessions? Are there other systemd mechanisms, or does per-session mean
not using systemd?

Tormod

Bug#979562: lightdm session termination does not stop xscreensaver

[Tormod Volden]

On Sun, Jan 10, 2021 at 5:46 PM Michael Biebl wrote:
> If you want to clean up this state, I would propose to use the following
>
> deb-systemd-helper --user purge xscreensaver.service >/dev/null || true
> deb-systemd-helper --user unmask xscreensaver.service >/dev/null || true
>
> Guarded by a version check.
> This will remove the (global) enablement symlink and purge the
> init-system-helpers state.

Thanks, I'll add
if [ "$1" = "configure" ] && [ "$2" = "5.44+dfsg1-2" -o "$2" =
"5.45+dfsg1-1" ]; then ... fi
around it.

Tormod

Bug#979717: Move snapd from main to contrib or non-free

[Daniel Khodabakhsh]

Package: snapd
Version: all
Severity: critical

snapd is a gateway to non-free software so it should not be in the 'main'
archive.

People who exclusively use the 'main' archive should not be in a position
where they can accidentally install non-free software via 'apt'.

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Hi Tormod

Am 10.01.21 um 15:12 schrieb Tormod Volden:

I should add that although we added the
debian/xscreensaver.user.service file in 5.44+dfsg1-2, we are using
"dh_installsystemduser --no-enable" since 5.45+dfsg1-1, so it won't be
enabled for the lightdm user in new installs or upgrades skipping
5.44+dfsg1-2. It will now only be enabled for those individual users
who themselves enable it as described in README.Debian. So adding the
ConditionUser=!@system to the unit now won't help us much - only if
someone got it globally enabled by 5.44+dfsg1-2. I guess we instead
should explicitly disable it globally in xscreensaver.postinst to
clean this up for those who had 5.44+dfsg1-2 installed.


If you want to clean up this state, I would propose to use the following

deb-systemd-helper --user purge xscreensaver.service >/dev/null || true
deb-systemd-helper --user unmask xscreensaver.service >/dev/null || true

Guarded by a version check.
This will remove the (global) enablement symlink and purge the 
init-system-helpers state.


Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979562: lightdm session termination does not stop xscreensaver

[Jamie Zawinski]

On Jan 10, 2021, at 3:20 AM, Tormod Volden  wrote:
> 
>  For a multi-user host the administrator expectations are different, since 
> there might be various login managers and user desktop environments, and 
> xscreensaver should only run in some of them.

I would think that if an administrator installed xscreensaver on a multi-user 
system, the expectation would be for it to run in all graphical login sessions.

--
Jamie Zawinski  https://www.jwz.org/  https://www.dnalounge.com/

Bug#975672: Bug#979245: RFS: xylib/1.6-0.1 [RC] [NMU] -- Library for reading x-y data from several file formats

[Fabian Wolff]

Hi Stuart,

thanks for having a look at the package!

But no, I do not currently intend to adopt this package. I just
thought I'd try and help with the freeze preparation by fixing the RC
bug in this package.

The reason I created the repository in the Science Team area is that I
have write access there (unlike in the Debian group) and because it
fits topically. If this is a problem, you can create a repository in
the Debian group, give me "Maintainer" access (so that I can push to
master), and I'll change the Vcs-* fields in d/control.

In any case, I've changed my upload to a QA upload now and reuploaded
it to Salsa and Mentors.

Best,
Fabian


On 1/10/21 7:11 AM, Stuart Prescott wrote:
> Hi Fabian
> 
> I see you've imported the package into the Debian Science Team area on salsa. 
> Since xylib is orphaned, do you intend to adopt it and maintain it within the 
> Debian Science team? That would be a great outcome.
> 
> If you update the Maintainer and Uploaders fields in debian/control, close 
> #979256 in the changelog and update the version to 1.6-1, then I can sponsor 
> the maintainer upload to adopt the package :)
> 
> regards
> Stuart
> 

Bug#979713: flask-jwt-simple's autopkg tests fail with python3.9

[Matthias Klose]

Package: src:flask-jwt-simple
Version: 0.0.3-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

flask-jwt-simple's autopkg tests fail with python3.9, see
https://ci.debian.net/packages/f/flask-jwt-simple/testing/amd64/

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
identity = 'username'

def _create_jwt(self, identity):
jwt_data = self._get_jwt_data(identity)
secret = config.encode_key
algorithm = config.algorithm
>   return jwt.encode(jwt_data, secret, algorithm).decode('utf-8')
E   AttributeError: 'str' object has no attribute 'decode'

flask_jwt_simple/jwt_manager.py:175: AttributeError

Bug#979493: marked as done (Error: Rule failed to generate the following targets: _doc/_html/highlight.pack.js)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 15:04:13 +
with message-id 
and subject line Bug#979493: fixed in ocaml-odoc 1.5.2+dfsg-1
has caused the Debian Bug report #979493,
regarding Error: Rule failed to generate the following targets: 
_doc/_html/highlight.pack.js
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.)


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

Hi Ralf,

as you probably remember, I brought up the odoc problem before here:

https://gitlab.com/irill/dose3/-/merge_requests/1#note_475481814

I now investigated further and it seems that the package has an
autopkgtest (yay!) so I triggered that and it failed with the same error
message that I got:

https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml-odoc/9469763/log.gz

Since the logs are removed after some time, here the last lines from the
log:

autopkgtest [02:11:21]: test odoc-on-odoc: [---
File series fully applied, ends at patch debian/patches/no-vendored-js-highlight
File "_doc/_html/_unknown_", line 1, characters 0-0:
Error: Rule failed to generate the following targets:
- _doc/_html/highlight.pack.js
autopkgtest [02:11:26]: test odoc-on-odoc: ---]
autopkgtest [02:11:26]: test odoc-on-odoc:  - - - - - - - - - - results - - - - 
- - - - - -
odoc-on-odoc FAIL non-zero exit status 1
autopkgtest [02:11:27]:  summary
odoc-on-odoc FAIL non-zero exit status 1

[ I also took the liberty to add salsaci to the ocaml-odoc repository on
salsa and it seems there is also a FTBFS which I was unable to trigger
locally using sbuild:
https://salsa.debian.org/ocaml-team/ocaml-odoc/-/pipelines/216353 ]

This makes me believe that this is probably not a problem with my system
but with the ocaml-odoc package itself.

A minimal test that triggers this error message is this shell script:

--%<--
#!/bin/sh
mkdir "$1/test"
cat << END > "$1/test/dune-project"
(lang dune 2.0)
(name test)
(generate_opam_files true)
(package (name test))
END
chroot "$1" sh -c 'cd /test && dune build @doc'
-->%--

Which I passed to mmdebstrap with the first timestamp from
snapshot.debian.org in which the ocaml-odoc package existed to see
whether maybe this is a regression and this used to work in the
beginning:

$ mmdebstrap --aptopt='Acquire::Check-Valid-Until "false"' \
--variant=apt unstable --include=ocaml-odoc,ocaml-dune,ocaml-nox \
--customize-hook=/tmp/test.sh \
/dev/null http://snapshot.debian.org/archive/debian/20200624T145103Z/

But even back in June 2020 I got the same error message as from the
autopkgtest on debci run above.

I didn't try with the opam version yet. Maybe it works there. Nobody
else (build-)depends on ocaml-odoc yet, so this problem is probably not
super important unless we want to generate documentation for the next
dose3 release.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: ocaml-odoc
Source-Version: 1.5.2+dfsg-1
Done: Ralf Treinen 

We believe that the bug you reported is fixed in the latest version of
ocaml-odoc, 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.
Ralf Treinen  (supplier of updated ocaml-odoc 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: Sun, 10 Jan 2021 15:42:22 +0100
Source: ocaml-odoc
Architecture: source
Version: 1.5.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 979493
Changes:
 ocaml-odoc (1.5.2+dfsg-1) unstable; urgency=medium
 .
   [ Ralf Treinen ]
   * New upstream release
   * Promote libjs-highlight.js from Recommends to Depends (closes: #979493)
   * Standards-Version 4.5.1 (no change)
 .
   [ Johannes 'josch' Schauer ]
   * Add debian/salsa-ci.yml
Checksums-Sha1:
 0d8a7cdf46b1a7e78e635f4337fa232d16d88795 2310 ocaml-odoc_1.5.2+dfsg-1.dsc
 

Bug#957786: marked as done (sdlbasic: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 15:04:35 +
with message-id 
and subject line Bug#957786: fixed in sdlbasic 0.0.20070714-7
has caused the Debian Bug report #957786,
regarding sdlbasic: 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.)


-- 
957786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sdlbasic
Version: 0.0.20070714-6
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/sdlbasic_0.0.20070714-6_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

[...]
/usr/bin/ld: 
BASengine/BASengine.a(membank.o):/<>/src/sdlBasic/src/sdlBrt/BASengine/../SDLengine/SDLengine.h:340:
 multiple definition of `rrgb'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340: 
first defined here
/usr/bin/ld: 
BASengine/BASengine.a(membank.o):/<>/src/sdlBasic/src/sdlBrt/BASengine/../SDLengine/SDLengine.h:325:
 multiple definition of `putpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325: 
first defined here
/usr/bin/ld: 
BASengine/BASengine.a(membank.o):/<>/src/sdlBasic/src/sdlBrt/BASengine/../SDLengine/SDLengine.h:318:
 multiple definition of `getpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDLengine.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340:
 multiple definition of `rrgb'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDLengine.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325:
 multiple definition of `putpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDLengine.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318:
 multiple definition of `getpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(common.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340:
 multiple definition of `rrgb'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(common.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325:
 multiple definition of `putpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(common.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318:
 multiple definition of `getpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDL_extension.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318:
 multiple definition of `getpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDL_extension.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325:
 multiple definition of `putpixel'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:325: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(SDL_extension.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340:
 multiple definition of `rrgb'; 
sdlBrt.o:/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:340: 
first defined here
/usr/bin/ld: 
SDLengine/SDLengine.a(screen.o):/<>/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h:318:
 multiple definition of `getpixel'; 

Processed: [Pkg-zfsonlinux-devel] Bug#979709: ZFS crash on update!

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 977656 -1
Bug #977656 {Done: Mo Zhou } [zfs-dkms] zfs-dkms: Fail to 
build with 5.10 kernel with "error: ‘struct percpu_ref’ has no member named 
‘count’"
Bug #979158 {Done: Mo Zhou } [zfs-dkms] fails to install 
under kernel version 5.10.0
Bug #979709 [zfs-dkms] ZFS crash on update!
Severity set to 'grave' from 'normal'
Marked Bug as done
Marked as fixed in versions zfs-linux/2.0.1-1~exp1.
Bug #979158 {Done: Mo Zhou } [zfs-dkms] fails to install 
under kernel version 5.10.0
Merged 977656 979158 979709

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

Processed: Re: ispell 3.4.01 breaks affix files of igerman98 and hkgerman

[Debian Bug Tracking System]

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

> severity 979575 serious
Bug #979575 [ispell] ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Severity set to 'serious' from 'important'
> tags 979575 + upstream
Bug #979575 [ispell] ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#979562: lightdm session termination does not stop xscreensaver

[Tormod Volden]

I should add that although we added the
debian/xscreensaver.user.service file in 5.44+dfsg1-2, we are using
"dh_installsystemduser --no-enable" since 5.45+dfsg1-1, so it won't be
enabled for the lightdm user in new installs or upgrades skipping
5.44+dfsg1-2. It will now only be enabled for those individual users
who themselves enable it as described in README.Debian. So adding the
ConditionUser=!@system to the unit now won't help us much - only if
someone got it globally enabled by 5.44+dfsg1-2. I guess we instead
should explicitly disable it globally in xscreensaver.postinst to
clean this up for those who had 5.44+dfsg1-2 installed.

I will add a warning in README.Debian (and debian/changelog) that the
systemd unit is not recommended for now.

Tormod

Processed: Re: Bug#977286: crash on H.264 encoding

[Debian Bug Tracking System]

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

> reopen 977268
Bug #977268 [src:puppet] autopkgtest flaky on arm64
Bug 977268 is not marked as done; doing nothing.
> tags 977286 - patch
Bug #977286 {Done: Sebastian Ramacher } 
[intel-media-va-driver-non-free] crash on H.264 encoding
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#979582: marked as done (nageru: please drop the Build-Depends on libsrt-gnutls-dev which is RC-buggy)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 13:06:49 +
with message-id 
and subject line Bug#979582: fixed in nageru 2.0.1-2
has caused the Debian Bug report #979582,
regarding nageru: please drop the Build-Depends on libsrt-gnutls-dev which is 
RC-buggy
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.)


-- 
979582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nageru
Version: 2.0.1-1
Severity: serious
Justification: B-D RC buggy
Control: block -1 by 971754

Hi Steinar,

The srt source package is RC buggy and has just been orphaned. We'll
probably remove it soon from bullseye. nageru will go too then, unless
it drop the (apparent optional) Build-Depends.

src:gst-plugins-bad1.0 is currently preventing autoremoval as that's a
key package, but I requested its maintainer to drop the plugin in the
follow-up of bug #978564.

Alternatively, you could adopt src:srt and fix the issue, but please be
aware that srt upstream has a bad record for breaking ABI.

Paul


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

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nageru
Source-Version: 2.0.1-2
Done: Steinar H. Gunderson 

We believe that the bug you reported is fixed in the latest version of
nageru, 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.
Steinar H. Gunderson  (supplier of updated nageru 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: Sun, 10 Jan 2021 13:39:12 +0100
Source: nageru
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Steinar H. Gunderson 
Changed-By: Steinar H. Gunderson 
Closes: 979582
Changes:
 nageru (2.0.1-2) unstable; urgency=medium
 .
   * Build without SRT support (remove the build-dependency on
 libsrt-gnutls-dev), as the srt package in Debian is unmaintained and
 RC-buggy. (Closes: #979582)
Checksums-Sha1:
 f2db2c8e0df22820c7ffc869fa6ef9f442594e66 2362 nageru_2.0.1-2.dsc
 abfe3bc78f16ed8fed90eee0da0c13fcb1241518 5712 nageru_2.0.1-2.debian.tar.xz
 811e0962f158252d80050f933cd054a3c7747b39 15009 nageru_2.0.1-2_amd64.buildinfo
Checksums-Sha256:
 0add4bd06118ab8e36eaf97a21ad28687b09e79ef6e6bd77232eb5a48441dcd8 2362 
nageru_2.0.1-2.dsc
 50c213e2a09dd99f2dba7956d222158ecf4741c42b00ac7ca3cd066fb656c737 5712 
nageru_2.0.1-2.debian.tar.xz
 ef7ff14ccf0ebae19c7978ccbce27efbe1292580b85e1f1b266d28f25f4af4dd 15009 
nageru_2.0.1-2_amd64.buildinfo
Files:
 96232c2b65ac8dd5a1983d7483b40203 2362 video optional nageru_2.0.1-2.dsc
 af5e6b86b263aa51f7cfcbd08d2b5279 5712 video optional 
nageru_2.0.1-2.debian.tar.xz
 4dae93aff940970c4eacd11547fc7532 15009 video optional 
nageru_2.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwukAT/AowY5OrduDf2F1YXeXj3YFAl/693MACgkQf2F1YXeX
j3aFKA/9GrUmgjTeBw07oIbbZvUf3/qgaJUKvfKvvaM7zYcKsiiKzXnDAn0uDbVT
m2WyzhsNFy4ADe6fLhFoQhuuqpb0YVi8l/9PD5HyIwgFqjY3SXi9jwbmqsA6Wd3j
LCh1i01yEOm3eFxwqnSkfOZphREQXyOu5xt+ZU3gNimDz5so//W+n4KfQuBj6GTC
lLADoyh+UY0GCLb3GIq6y73Ix0qB7SggWqpMV9DpIfTfkMf6PbLrjTdTBzXuEuhR
wcLhQ38ZnNKfMQrAjC+LOoSt9I3AjUqGGWzPCMCY05E00/NVlpzP1o144n0iS3WD
bHT4SpOq7N9Q+7ERACgVqdVR75LYD9RSBdtXcEQh4Gc8qM9K+mto3pEu5T9cLjLm
T6PmfoP8ce/wekb1V60Nm3jBBhmM7Ab+iFnEM28C726cmWkTigJ5RgY2w2inqhHh
hjTmZSG/jcRSE0GVIWWwpUEgZUpOqVYeDHR6ZxfyLUKaaxpy1WIsx1bMVWFPtjTr
8Wcmi6Vo3CLrLydAGmVT0feGqZCP4Hcf+QoDsgjzqkWwonsEbv3G7o/UybqmoAF7
d+BegXO2qyQSzaiJ2FOLQ3xo8KSI+VqsozQYJJmTm0x4wx+nmiXMkLFoWD33mM1D
1Oyn4cUOHtyXClxErwj1CF8KjTsdf3I5BmcwaKpJlMRalMW4S0M=
=eiRr
-END PGP SIGNATURE End Message ---

Bug#979614: seamly2d: virtually dead fork of valentina

[Jonas Smedegaard]

Quoting Bernd Zeimetz (2021-01-10 13:05:47)
> 
> 
> On 1/10/21 10:20 AM, Jonas Smedegaard wrote:
> > Quoting Bernd Zeimetz (2021-01-09 22:09:06)
> >> Would have been nice to know about that after I've opened the RFP 
> >> bug - to be hones I haven't even been able to find valentina with 
> >> apt, maybe I've searched for the wrong words.
> > 
> > For future sake, I recommend to share RFPs and ITPs to 
> > debian-devel@l.d.o as is the default for reportbug
> 
> Thats why I've used reportbug, would have expected that that happens.

That's odd.  Maybe you have a ~/.reportbugrc file suppressing it?


> > https://en.wikipedia.org/wiki/Valentina_(software) has a summary, 
> > with link to a longer blog entry about it.
> > 
> > Following trails from there, I found this post which seems 
> > essential: 
> > https://web.archive.org/web/20171216140149/http://valentinaproject.forumotion.me/t23-my-vision
> 
> I've searched a bit, also found
> https://librearts.org/2017/12/valentina-seamly2d/
> which is the mentioned blog entry.

Yes, that is the page linked from Wikipedia.


> > Seems to me that Seamly2D has created a stronger brand with more 
> > fans, whereas Valentina has more programmers involved (i.e. has 
> > "only one" or "one at all", depending how you look at it).
> 
> Was probably easy as the valentina-project page points to seamly now, 
> which is rather sad.

Please use URLs.

I don't think https://valentinaproject.bitbucket.io/ points to Seamly2D 
anywhere.

If you are talking about http://valentina-project.org/ then yes, as the 
librearts article you link to above said, "Susan Spencer got the 
valentina-project.org domain name and the website as part of the 
separation deal."


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Am 10.01.21 um 13:19 schrieb Tormod Volden:

On Sun, Jan 10, 2021 at 12:44 PM Michael Biebl  wrote:


Negating @system might work.
Something like ConditionUser=!@system, but untested.


Thanks! I was just about to suggest this myself after searching around for this.
(https://www.freedesktop.org/software/systemd/man/systemd.unit.html)

I also wonder if PartOf=graphical-session.target would make sure the
service is stopped when the X sessions stops.
(https://www.freedesktop.org/software/systemd/man/systemd.special.html#)


graphical-session.target looks like a better fit indeed.
E.g. I don't expect xscreensaver to start (and work), if I log in on the 
console.
That said, graphical-session.target can also mean Wayland, which I 
suppose xscreensaver does not support.


graphical-session.target is something which TTBOMK is currently only 
implemented by GNOME. GNOME on the other hand does indeed have its own 
screensaver.




And maybe we should replace WantedBy=default.target by more specific
DEs, like WantedBy=xfce-session.target. I'd expect e.g. Gnome to start
its own screensaver by default.


I don't think something like xfce-session.target exists (yet)?


I also see that the systemd user task is per-user, not per-session.
Wonder what happens if a user log in twice...
"Problematic" according to https://systemd.io/DESKTOP_ENVIRONMENTS/


Right, I raised this in my initial reply.

All in all, I'm not sure, if a systemd --user service is a good fit for 
xscreensaver in its current state.


Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979493: Error: Rule failed to generate the following targets: _doc/_html/highlight.pack.js

[Ralf Treinen]

Hi Josch,

On Thu, Jan 07, 2021 at 11:47:06AM +0100, Johannes 'josch' Schauer wrote:

> I now investigated further and it seems that the package has an
> autopkgtest (yay!) so I triggered that and it failed with the same error
> message that I got:
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml-odoc/9469763/log.gz
> 
> Since the logs are removed after some time, here the last lines from the
> log:
> 
> autopkgtest [02:11:21]: test odoc-on-odoc: [---
> File series fully applied, ends at patch 
> debian/patches/no-vendored-js-highlight
> File "_doc/_html/_unknown_", line 1, characters 0-0:
> Error: Rule failed to generate the following targets:
> - _doc/_html/highlight.pack.js

That seems to be due to a missing libjs-highlight.js. This used to be
only a Recommends, and hence was not pulled in by the test runner. I
have now made it a Depends, I hope that will solve the problem.

> [ I also took the liberty to add salsaci to the ocaml-odoc repository on

> salsa and it seems there is also a FTBFS which I was unable to trigger
> locally using sbuild:
> https://salsa.debian.org/ocaml-team/ocaml-odoc/-/pipelines/216353 ]
> 
> This makes me believe that this is probably not a problem with my system
> but with the ocaml-odoc package itself.

Error: Too many opam files for package "dune_odoc_test":
1285- test/dune/dune_odoc_test.opam
1286- debian/output/source_dir/test/dune/dune_odoc_test.opam

That is weird. In particular I have no idea where that debian/output is
coming from. Anyway, I think that this is an indepenent problem.

Cheers -Ralf.

Bug#962203: NMU

[A Mennucc1]

Dear all, sorry for being MIA so long; I have added the NMU to the GIT
repository. a.



signature.asc
Description: OpenPGP digital signature

Bug#979524: marked as done (debian-reference: build-depends on libopencc2-data, which no longer exists)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 12:19:35 +
with message-id 
and subject line Bug#979524: fixed in debian-reference 2.77
has caused the Debian Bug report #979524,
regarding debian-reference: build-depends on libopencc2-data, which 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.)


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

package: src:debian-reference
version: 2.76
tags: bullseye sid ftbfs
severity: serious

Hi,

It seems debian-reference build-depends on libopencc2-data, which no longer
exists.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: debian-reference
Source-Version: 2.77
Done: Osamu Aoki 

We believe that the bug you reported is fixed in the latest version of
debian-reference, 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.
Osamu Aoki  (supplier of updated debian-reference 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, 10 Jan 2021 15:36:06 +0900
Source: debian-reference
Architecture: source
Version: 2.77
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki 
Changed-By: Osamu Aoki 
Closes: 941801 942942 953075 964674 972371 972437 979524
Changes:
 debian-reference (2.77) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * libopencc2-data has been replaced by libopencc-data. Dependency
 can be removed, since package opencc has an implicit hard dependency on
 the data package already. Closes: #964674, #979524
 .
   [ Osamu Aoki ]
   * Mention locales-all package. Closes: #953075
   * Update printing for post-CUPS 1.6. Closes: #941801
   * Convert source to XML.
 .
   [ Stuart Prescott ]
   * Migrate to Python3. Closes: #942942
   * Add CI to automate build tests on Salsa. Closes: #972371
 .
   [ xiao sheng wen (肖盛文) ]
   * get package info from oldstable and stable. Closes: #972437
Checksums-Sha1:
 226a49313514ea274eeb35dc5d7e4d371b03d23d 2718 debian-reference_2.77.dsc
 4f19960cf3e8b9e2be893e26fd377f77271d0de5 2006360 debian-reference_2.77.tar.xz
 beeb2f04d5952a2d1865cc71f835081fb99984da 13605 
debian-reference_2.77_amd64.buildinfo
Checksums-Sha256:
 058942e8d0aff249ecfb3557e2ea1fb2b0387edc29ea9d5fea7bfbfc70d07811 2718 
debian-reference_2.77.dsc
 9e220f86c62197581a09a4b4b82c5a504f978eb14d0e67b648b12dfdbe126115 2006360 
debian-reference_2.77.tar.xz
 59eb4c2742199072a5067cf3b0266c7bad39576d85291885c6a6354fdb5dbda2 13605 
debian-reference_2.77_amd64.buildinfo
Files:
 c6c965bd2636fd4a7bc4870dfa816879 2718 doc optional debian-reference_2.77.dsc
 36266b561d7b9c2749340730ac6d5fb5 2006360 doc optional 
debian-reference_2.77.tar.xz
 2e99782cc2d3f9be626c6275cdd1e0cb 13605 doc optional 
debian-reference_2.77_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAl/67K8ACgkQHhNWiB3Y
15GEzg/9FDQLofE1vlsaVjt2UgLW2D0SotECMD3kjtKRdAotC6t3lz25rOTcXOvU
v4m0091VR5WfeoamTXCAQRfuAsPxJmSOjOpQAFXRRxPPJMlzfwMIw7by+s6Nxkp/
kmFqq+sl/wFtLElRZJ3lmawMvBOgimLrtcDYtzkfPC/0TDzWCNS+VCLkBeBLmwUV
dyGbCBML2C4x7KJg8LsGy8X3kBe4aGaA+NtaX2hALDsh3D67oEYWFHI8pbZCQMuv
fzh4mAnXdAS0/+hq5rdQsixh8XKfoR/KEvz58OEBF1qXn4ctrZh7OcVE1bdKilq5
ndWosGyGPJT2SHFU29Rq3uUII4Hw7k/h4LeMpMVBNEjo5WcOn8bZRZABrnaFaEyw
stuUycJPhc1kpgz+mPfrYfL2seS/1Qhz8l4e5uQbkmiyQobgkTdiXhJ9gP27YYtX
49XGbDDP/1qWjUHp+5ilujZWuT/OzqKHhjgv/VbQvjV4f5gYJBjbBauzovUOnhWb
BCjSc+ni+9CtpRvzOaewecIzoHGSL5GsrHFUdtBxbw5YKBOA9hwxxoPTSlvLy+7B
oUTX5GTUTKYcWrE93UB4gwFmptSIJcOA64BZHmi6SbySnBSZJWD0cJEHKaBXVE2q
OeSecCnkrS43whGS95Hyl1ijGxWp2vWkqRTcWbL9OldGB7FKjGE=
=bSZi
-END PGP SIGNATURE End Message ---

Bug#964674: marked as done (debian-reference: FTBFS: build-dependency not installable: libopencc2-data)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 12:19:35 +
with message-id 
and subject line Bug#964674: fixed in debian-reference 2.77
has caused the Debian Bug report #964674,
regarding debian-reference: FTBFS: build-dependency not installable: 
libopencc2-data
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), build-essential, fakeroot, dblatex, 
> docbook-xml, docbook-xsl, fonts-liberation2, fonts-vlgothic, 
> fonts-wqy-microhei, libopencc2-data, libxml2-utils, locales-all | locales, 
> opencc, po4a, python, texlive-lang-chinese, texlive-lang-english, 
> texlive-lang-french, texlive-lang-german, texlive-lang-italian, 
> texlive-lang-japanese, texlive-lang-portuguese, texlive-lang-spanish, 
> texlive-xetex, w3m, xsltproc, zip
> Filtered Build-Depends: debhelper (>= 11), build-essential, fakeroot, 
> dblatex, docbook-xml, docbook-xsl, fonts-liberation2, fonts-vlgothic, 
> fonts-wqy-microhei, libopencc2-data, libxml2-utils, locales-all, opencc, 
> po4a, python, texlive-lang-chinese, texlive-lang-english, 
> texlive-lang-french, texlive-lang-german, texlive-lang-italian, 
> texlive-lang-japanese, texlive-lang-portuguese, texlive-lang-spanish, 
> texlive-xetex, w3m, xsltproc, zip
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [540 B]
> Get:5 copy:/<>/apt_archive ./ Packages [612 B]
> Fetched 2115 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libopencc2-data but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/debian-reference_2.76_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated debian-reference 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, 10 Jan 2021 15:36:06 +0900
Source: debian-reference
Architecture: source
Version: 2.77
Distribution: unstable

Bug#979562: lightdm session termination does not stop xscreensaver

[Tormod Volden]

On Sun, Jan 10, 2021 at 12:44 PM Michael Biebl  wrote:

> Negating @system might work.
> Something like ConditionUser=!@system, but untested.

Thanks! I was just about to suggest this myself after searching around for this.
(https://www.freedesktop.org/software/systemd/man/systemd.unit.html)

I also wonder if PartOf=graphical-session.target would make sure the
service is stopped when the X sessions stops.
(https://www.freedesktop.org/software/systemd/man/systemd.special.html#)

And maybe we should replace WantedBy=default.target by more specific
DEs, like WantedBy=xfce-session.target. I'd expect e.g. Gnome to start
its own screensaver by default.

I also see that the systemd user task is per-user, not per-session.
Wonder what happens if a user log in twice...
"Problematic" according to https://systemd.io/DESKTOP_ENVIRONMENTS/

Tormod

Bug#979524: debian-reference: build-depends on libopencc2-data, which no longer exists

[Osamu Aoki]

Hi,

I just uploaded 2.77 addressing all the issues.

I also made a merge of Boyan's changes while overriding them.

I hope this is OK since my change history should have most of the fixes
proposed.  If I am wrong, let me know.  That goes to 2.78.

On Sat, 2021-01-09 at 14:40 +0900, Osamu Aoki wrote:
> Hi,
> 
> I think it is time to fix this bug and upload package.  Let me make
> final check.  Osamu
> 
> On Fri, 2021-01-08 at 23:28 -0500, Boyuan Yang wrote:
> > 
...
> 

Bug#979614: seamly2d: virtually dead fork of valentina

[Bernd Zeimetz]

On 1/10/21 10:20 AM, Jonas Smedegaard wrote:
> Quoting Bernd Zeimetz (2021-01-09 22:09:06)
>>> Since then, he continued develop under original project name 
>>> Valentina, whereas Seamly2D virtually stalled with no substantial 
>>> code changes , only superficial changes to build infrastructure, 
>>> locales, and icons.
>>
>> well, compared to valentina it seems to have way more pull requests 
>> and is at least very responsive to requests. Looking on valentina it 
>> seems to be a one-man-show - more or less.
> 
> Seems to me that Seamly2D is similarly a one-woman-show - difference 
> (disregarding sexes) being that one is good with code and the other is 
> good with words and people.

I think its a woman and a man, at least according to the commits.
There is a long list of issues with interesting ideas, more pushing
towards cloud and similar features.


> But I might be wrong.  Or maybe code is largely "done" and only _need_ 
> smaller polishing.

Definitely not, there are some new features like keyboard shortcuts
(imho not chosen wisely, but thats my taste probably).


>>> I recommend that Debian does not carry Seamly3D, and encourage 
>>> helping out with maintaining Valentina instead.
>>
>> Would have been nice to know about that after I've opened the RFP bug 
>> - to be hones I haven't even been able to find valentina with apt, 
>> maybe I've searched for the wrong words.
> 
> For future sake, I recommend to share RFPs and ITPs to 
> debian-devel@l.d.o as is the default for reportbug

Thats why I've used reportbug, would have expected that that happens.

> That said, you got a point about keywords - and curiously, you didn't 
> add "sewing" to long description of Seamly2D either :-P

true. we've copied the same text ;)


> https://en.wikipedia.org/wiki/Valentina_(software) has a summary, with 
> link to a longer blog entry about it.
> 
> Following trails from there, I found this post which seems essential: 
> https://web.archive.org/web/20171216140149/http://valentinaproject.forumotion.me/t23-my-vision

I've searched a bit, also found
https://librearts.org/2017/12/valentina-seamly2d/
which is the mentioned blog entry.


> I found no similar information from Seamly2D side of the fork.  If you 
> find any then please do share.

Me neither.


> Seems to me that Seamly2D has created a stronger brand with more fans, 
> whereas Valentina has more programmers involved (i.e. has "only one" or 
> "one at all", depending how you look at it).

Was probably easy as the valentina-project page points to seamly now,
which is rather sad.


> I was hoping that the strong community of Seamly2D would lead to more 
> sample documents than the relatively few shipped with Valentina, but I 
> have so far not been able to locate any, and it seems all blog posts in 
> Seamly2D shares only PDFs, no *source* patterns.  Therefore I also am 
> unaware how compatible Valentina and Seamly2D is in their document 
> formats, if at all.


I also gave that a try: and they are not compatible anymore, although
seamly still says valentina format. Which is.. stupid.

It was easy to fix with

 3676  sed 's,solidLine,hair,g' -i hike_and_fly_backpack.val
 3678  sed 's,lineType,typeLine,g' -i hike_and_fly_backpack.val

I'd have expected a new file format name and extension.



-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#979693: [Pkg-javascript-devel] Bug#979693: Bug#979693: typescript-types_20210110-1_sourceonly.changes ACCEPTED into unstable

[Jonas Smedegaard]

Quoting Xavier (2021-01-10 12:16:47)
> Le 10/01/2021 à 11:05, Jonas Smedegaard a écrit :
> > Quoting Debian FTP Masters (2021-01-10 10:49:04)
> >> Changes:
> >>  typescript-types (20210110-1) unstable; urgency=medium
> >>  .
> >>* Team upload
> >>* Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693)
> > 
> > I am not convinced that above closes the bug: I think a Breaks is 
> > needed in the nodejs package.
> > 
> >  - Jonas
> 
> You were right but it took more time to build nodejs than 
> typescript-types

I don't understand how speed relates to this: Even it it took a week to 
compile nodejs, declaring it closed with the removal of the clashing 
files is still wrong: That only addresses *new* installs but issue still 
exists for *existing* installs of of node-typescript-types!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Am 10.01.21 um 12:20 schrieb Tormod Volden:

On Fri, Jan 8, 2021 at 10:00 PM Jamie Zawinski wrote:



In xscreensaver (or maybe lightdm).
Why is xscreensaver started in the lightdm session anyway?
Is xscreensaver really usable as a per user service or should it be per session?
Why is the lightdm xscreensaver instance interfering with the xscreensaver 
instance of the logged in user?
Questions that only the xscreensaver maintainer can answer.

If he thinks there is a genuine systemd issue, then I'd appreciate if it was 
reassigned back with more details.


XScreenSaver author here. I know nothing about lightdm, and didn't write the 
code attempting to integrate the two. However:

1) XScreenSaver should be running as the logged-in user, and terminate when 
they log out. Typically this happens when the X server dies and the $DISPLAY 
socket is closed, but SIGTERM works just as well.

2) It is also reasonable to configure things so that XScreenSaver is running when no one 
is logged in (so that there is a screensaver atop the login screen). If it is launched as 
root, it will setuid to "nobody" at startup, etc. But in this case, when a user 
logs in, it must be killed and re-started as that user.


It was not intentional from my side to have it run in the login window
by default. We used to just ship a systemd unit file that a user could
install if he wanted. Recently, in 5.44+dfsg1-2, we added the
debian/*.user.service file, it was part of a debhlper clean-up from my
package upload sponsor and I didn't foresee the implications.
"lightdm" is a system user (UID < 1000), is possible to have systemd
have it start only for "normal" users?


See man systemd.unit:


   ConditionUser=
   ConditionUser= takes a numeric "UID", a UNIX user name, or the
   special value "@system". This condition may be used to check
   whether the service manager is running as the given user. The
   special value "@system" can be used to check if the user id is
   within the system user range. This option is not useful for system
   services, as the system manager exclusively runs as the root user,
   and thus the test result is constant.


Negating @system might work.
Something like ConditionUser=!@system, but untested.








OpenPGP_signature
Description: OpenPGP digital signature

Processed: limit source to ocaml-odoc, tagging 979493

[Debian Bug Tracking System]

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

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

> tags 979493 + pending
Bug #979493 [ocaml-odoc] Error: Rule failed to generate the following targets: 
_doc/_html/highlight.pack.js
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#979640: src:adv-17v35x: invalid maintainer address

[Alexander Gerasiov]

On Sat, 09 Jan 2021 18:03:10 +0100
Ansgar  wrote:

> Source: adv-17v35x
> Version: 5.0.3.0-2
> Severity: serious
> Tags: bullseye sid
> X-Debbugs-Cc: Alexander Gerasiov , Holger Levsen
> 
> 
> The maintainer address is invalid, see below.

Yep, Andrey has retired from the project where he worked with the
hardware. (So did I.) So he definitely is not interested in packaging
this driver anymore.


I thinks the package could be orphaned. Let's wait for Andrey's response.

For now I'll take care on the package to resolve open issues for
Bullseye release.


-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: a...@gerasiov.net  WWW: https://gerasiov.net  TG/Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1

Bug#979562: lightdm session termination does not stop xscreensaver

[Tormod Volden]

On Fri, Jan 8, 2021 at 10:00 PM Jamie Zawinski wrote:
>
> > In xscreensaver (or maybe lightdm).
> > Why is xscreensaver started in the lightdm session anyway?
> > Is xscreensaver really usable as a per user service or should it be per 
> > session?
> > Why is the lightdm xscreensaver instance interfering with the xscreensaver 
> > instance of the logged in user?
> > Questions that only the xscreensaver maintainer can answer.
> >
> > If he thinks there is a genuine systemd issue, then I'd appreciate if it 
> > was reassigned back with more details.
>
> XScreenSaver author here. I know nothing about lightdm, and didn't write the 
> code attempting to integrate the two. However:
>
> 1) XScreenSaver should be running as the logged-in user, and terminate when 
> they log out. Typically this happens when the X server dies and the $DISPLAY 
> socket is closed, but SIGTERM works just as well.
>
> 2) It is also reasonable to configure things so that XScreenSaver is running 
> when no one is logged in (so that there is a screensaver atop the login 
> screen). If it is launched as root, it will setuid to "nobody" at startup, 
> etc. But in this case, when a user logs in, it must be killed and re-started 
> as that user.

It was not intentional from my side to have it run in the login window
by default. We used to just ship a systemd unit file that a user could
install if he wanted. Recently, in 5.44+dfsg1-2, we added the
debian/*.user.service file, it was part of a debhlper clean-up from my
package upload sponsor and I didn't foresee the implications.
"lightdm" is a system user (UID < 1000), is possible to have systemd
have it start only for "normal" users?

Many users will expect xscreensaver to start automatically in all
their sessions after installing the xscreensaver package. For a
multi-user host the administrator expectations are different, since
there might be various login managers and user desktop environments,
and xscreensaver should only run in some of them. Not sure how to find
the one-size-fits-all.

Tormod

Bug#979301: namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build

[Ivo De Decker]

Hi Andreas,

On Tue, Jan 05, 2021 at 12:56:24AM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.

Thanks for catching this!

I wasn't able to find this error in the tests on piuparts.debian.org. The
piuparts data passed on the britney says everything is ok. Is this a specific
test that you are running, that isn't run on piuparts.debian.org?


> [...]

> The buildds only perform separate arch and indep builds, while the
> maintainer uploaded namazu2-index-tools_2.0.21-22_all.deb seems to stem
> from a combined build.

So this is actually a bug in the source, which is the same in the version in
testing. So this bug actually also affects the version in testing. I'm not
adding a 'found' on that version because that would allow the package to
migrate to testing, while AIUI, the binaries for the newer version are broken.
I guess the only way to express that in the BTS is to clone the bug and
reassign one clone to the source in testing and unstable, and leave the other
one assigned to the binary in unstable.

Cheers,

Ivo

Bug#979693: [Pkg-javascript-devel] Bug#979693: typescript-types_20210110-1_sourceonly.changes ACCEPTED into unstable

[Xavier]

Le 10/01/2021 à 11:05, Jonas Smedegaard a écrit :
> Quoting Debian FTP Masters (2021-01-10 10:49:04)
>> Changes:
>>  typescript-types (20210110-1) unstable; urgency=medium
>>  .
>>* Team upload
>>* Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693)
> 
> I am not convinced that above closes the bug: I think a Breaks is needed 
> in the nodejs package.
> 
>  - Jonas

You were right but it took more time to build nodejs than typescript-types

Processed: Re: [PATCH] Ensure graceful signal handling when the pid file exists

[Debian Bug Tracking System]

Processing control commands:

> severity 948346 serious
Bug #948346 [xdm] xdm gets killed, but only on sunday, on the first startup 
(code=killed, signal=USR2)
Severity set to 'serious' from 'important'

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

Bug#952463: marked as done (bagel: flaky arm64 autopkgtest: terminate called without an active exception)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 12:46:30 +0200
with message-id <20210110104630.GI14316@localhost>
and subject line Re: Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky 
arm64 autopkgtest: terminate called without an active exception
has caused the Debian Bug report #952463,
regarding bagel: flaky arm64 autopkgtest: terminate called without an active 
exception
to be marked as done.

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

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


-- 
952463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bagel
Version: 1.2.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

With a recent upload of gcc-10 to unstable, the autopkgtest of bagel
failed on arm64 in testing when that autopkgtest was run with the binary
packages of gcc-10 from unstable. I looked into the history of your
autopkgtest and it fails very often.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.

I copied the output at the bottom of this report. All the failing tests
that I inspected look like it, albeit the test that fails differs
between runs.

I'll have the migration software ignore the results of your autopkgtest
on arm64 until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/4258642/log.gz

running test case 'hf_sto3g_relfci_gaunt'... terminate called without an
active exception
/tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh:
line 85: 15487 Aborted BAGEL test/${testname}.json >
${testname}.out
/tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh:
fork: retry: Resource temporarily unavailable
FAILED.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Sat, Jan 09, 2021 at 10:14:42PM +0100, Paul Gevers wrote:
> Hi Adrian,
> 
> On 09-01-2021 21:37, Adrian Bunk wrote:
> > you are saying the version in unstable passes all tests for migration,
> > and needs only this bug closed?
> 
> Yes. Otherwise the excuses would have mentioned the issues.
>...

Thanks, it seems I misunderstood the problem.

> Paul
> 
> PS: I did have a hint in place, but that was only to ignore failures on
> arm64. I've removed that just now.

I'm closing this bug now, please reopen if the problem reappears.

cu
Adrian--- End Message ---

Bug#979700: ruby-in-parallel frequently FTBFS: test failure

[Adrian Bunk]

Source: ruby-in-parallel
Version: 0.1.17-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/ruby-in-parallel.html
https://tests.reproducible-builds.org/debian/history/ruby-in-parallel.html
https://buildd.debian.org/status/fetch.php?pkg=ruby-in-parallel=all=0.1.17-1.1=1610125983=0

...
Failures:

  1) .run_in_parallel should raise an exception and return immediately with 
kill_all_on_error and one of the processes errors.
 Failure/Error: expect(@result_3).to_not eq(true)

   expected: value != true
got: true

   (compared using ==)
 # ./spec/in-paralell_spec.rb:136:in `block (2 levels) in '

Finished in 10.07 seconds (files took 0.24492 seconds to load)
19 examples, 1 failure

Failed examples:

rspec ./spec/in-paralell_spec.rb:129 # .run_in_parallel should raise an 
exception and return immediately with kill_all_on_error and one of the 
processes errors.

/usr/bin/ruby2.7 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-in-parallel returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 25

Processed: found 979671 in 340.76-6, found 979672 in 390.48-4, found 979673 in 418.116.00-2 ...

[Debian Bug Tracking System]

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

> found 979671 340.76-6
Bug #979671 [src:nvidia-graphics-drivers-legacy-340xx] 
nvidia-graphics-drivers-legacy-340xx: CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.76-6.
> found 979672 390.48-4
Bug #979672 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-legacy-390xx/390.48-4.
> found 979673 418.116.00-2
Bug #979673 [src:nvidia-graphics-drivers-tesla-418] 
nvidia-graphics-drivers-tesla-418: CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-tesla-418/418.116.00-2.
> found 979674 440.64.00-1
Bug #979674 [src:nvidia-graphics-drivers-tesla-440] 
nvidia-graphics-drivers-tesla-440: CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-tesla-440/440.64.00-1.
> found 979675 450.51.05-1
Bug #979675 [src:nvidia-graphics-drivers-tesla-450] 
nvidia-graphics-drivers-tesla-450: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-tesla-450/450.51.05-1.
> thanks
Stopping processing here.

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

Bug#979693: marked as done (nodejs: File conflict with node-typescript-types)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 10:19:22 +
with message-id 
and subject line Bug#979693: fixed in nodejs 12.20.1~dfsg-2
has caused the Debian Bug report #979693,
regarding nodejs: File conflict with node-typescript-types
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.)


-- 
979693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 12.20.1~dfsg-1
Severity: serious

Unpacking nodejs (12.20.1~dfsg-1) over (12.19.0~dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-vFR3K6/16-nodejs_12.20.1~dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/nodejs/@types/node/README.md', which is also 
in package node-typescript-types 20201201-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 12.20.1~dfsg-2
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
nodejs, 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.
Xavier Guimard  (supplier of updated nodejs 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, 10 Jan 2021 10:18:57 +0100
Source: nodejs
Architecture: source
Version: 12.20.1~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 979693
Changes:
 nodejs (12.20.1~dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Indicate that it breaks node-typescript-types < 20210110~
 (Closes: #979693)
Checksums-Sha1: 
 775525cbc05105ee0a13b4c0107f159c3c0a8cd2 3425 nodejs_12.20.1~dfsg-2.dsc
 a6144b4bf810338dadcd2b068cf1f434626e3c34 134260 
nodejs_12.20.1~dfsg-2.debian.tar.xz
Checksums-Sha256: 
 2ca4afe38029a451b01258413f68d7e88df7e9253d58ca7c7548a14331ba7a55 3425 
nodejs_12.20.1~dfsg-2.dsc
 763819eb28cc9c4ad72448b3c6c9a31fee9f1388f374f8405c6798da58561680 134260 
nodejs_12.20.1~dfsg-2.debian.tar.xz
Files: 
 cd807da617b982f14f10f1c361889b7b 3425 javascript optional 
nodejs_12.20.1~dfsg-2.dsc
 106b329f33e2c67f729b53284bcb8c60 134260 javascript optional 
nodejs_12.20.1~dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/60PQACgkQ9tdMp8mZ
7unjTw//WQ+SapNol8kuLYXsz7LuQVVL1uJaNsuvcuMma055JGw4LRWHtb8BCkOp
G+Ma5yLAHOvSnrmohDMN0zDQrRZypXqDAidMhzdvlRn06DQyYR7pAxZ6xUSHTgGJ
LH9/0Dy6xLvcx6aqOUStTb5dThnh31Bps8ICtbL37gNkAnR9c6VFPIIh58ku4mPF
qmEa9dJQjG5lZAiHq9MkkZoAFnAffjLJONvqOWusK5oZgwbO+W6U1LWihm6TH6wu
lTzKsJjQBQZoh23PECOHbRqAP3hZb/+GQDaRutb1m1szBsIlkMEXBSRzuQ/jwKI+
0WBEMT2uIDT5OlIbUPywH6Fpytx9ynQPopT0K/iQb7ewWv3lca0lvxDP8SeDun42
G5GMdxNma4XUsHujoXZBpjbvDONaJA4CPDlZoucQuyNF6AZzqhkRiF6D+haMV6/z
vUB3hWqCPMraaE5JSyWiVovRjR2H6ZFsyX9TusyVqWVXfMp7AMYrgEXCNJKYhlip
6qqsOidr93ARr+IYCcefYPPsawRPtxVdoUPwkHUnDiWTUZX+htO9tZu6s3wvGUAt
eKSN4ZtRFPX7wMf4PHbr30tWxFtZxImGi13vSfVxRMXcxdZt2oR9YNW4Q4NSQBaq
OPNSBUTXJNWd3/5uFDgNLUr0Tvt9VeBsxvPp6SQy1ZDDgkTivfU=
=lxa4
-END PGP SIGNATURE End Message ---

Bug#979693: [Pkg-javascript-devel] typescript-types_20210110-1_sourceonly.changes ACCEPTED into unstable

[Jonas Smedegaard]

Quoting Debian FTP Masters (2021-01-10 10:49:04)
> Changes:
>  typescript-types (20210110-1) unstable; urgency=medium
>  .
>* Team upload
>* Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693)

I am not convinced that above closes the bug: I think a Breaks is needed 
in the nodejs package.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#979693: marked as done (nodejs: File conflict with node-typescript-types)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jan 2021 09:49:04 +
with message-id 
and subject line Bug#979693: fixed in typescript-types 20210110-1
has caused the Debian Bug report #979693,
regarding nodejs: File conflict with node-typescript-types
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.)


-- 
979693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 12.20.1~dfsg-1
Severity: serious

Unpacking nodejs (12.20.1~dfsg-1) over (12.19.0~dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-vFR3K6/16-nodejs_12.20.1~dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/nodejs/@types/node/README.md', which is also 
in package node-typescript-types 20201201-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
--- End Message ---
--- Begin Message ---
Source: typescript-types
Source-Version: 20210110-1
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
typescript-types, 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.
Xavier Guimard  (supplier of updated typescript-types 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, 10 Jan 2021 10:19:52 +0100
Source: typescript-types
Architecture: source
Version: 20210110-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 979693
Changes:
 typescript-types (20210110-1) unstable; urgency=medium
 .
   * Team upload
   * Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693)
   * New upstream version 20210110
Checksums-Sha1: 
 034467b5284fff0437c76e1eac75fc9e8ce1b8e8 2058 typescript-types_20210110-1.dsc
 e90aa6f96a11dc5f03fc2d7c01277ee316ab0a9a 6860 
typescript-types_20210110.orig.tar.xz
 a617e27386d7bf93904f00fce0392209279b5c5c 5240 
typescript-types_20210110-1.debian.tar.xz
Checksums-Sha256: 
 20775f193c4cfeb293770b4a08231ef90696c4afb3723130c44d4800c5c3e54a 2058 
typescript-types_20210110-1.dsc
 c5986001fa20c8bcee53b3a3c1d90991a59939f9183ffa60879da8d494dd495b 6860 
typescript-types_20210110.orig.tar.xz
 040a011e24dc7f74a0e9c219bad8589565cc09fd6e8e3563fa8157fff6c30138 5240 
typescript-types_20210110-1.debian.tar.xz
Files: 
 d5016e2a8bca2fc6a5c175443a89a4db 2058 oldlibs optional 
typescript-types_20210110-1.dsc
 ebb5b6a4125c54a9235c6d4ca0e5095a 6860 oldlibs optional 
typescript-types_20210110.orig.tar.xz
 6dfb853660030ab028fbc7fe978eff13 5240 oldlibs optional 
typescript-types_20210110-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/6yeIACgkQ9tdMp8mZ
7umDHxAAg16kFfF78PefW+R/xonLNO2Bx2LBFaTAMlVGLNcntpUoR08Ki89jgRVJ
Bt7/GcLcyPbs8GHMabSDiIL6VZUk09s6yiw8ktNctg7GmooOvctotckFBwEQ7AXK
+JuSTjD5wlP5f/Q/nGv3F7rtkb7MsSM7ZsdSAoE3P7WOIStxaAwRGMwOrywzAnZx
7UBm0RyYG13HUcY/ZLfG11n3xh7ibpX+5dn8zOodobkH5VRZmjEjglAgc5IfdBk6
WPXeP3qJBb9Bs2GfpAjmHXYcFEFgJCHIk63XMpC2+Dxl5TyEkf6AhDfnxuxq3afp
8s0Zeh6hEo8mMVQrP688JabnKSew/ReJqldSHVUA8WykEmIPQRt/Uolm6UZoImt5
3ciFR6/3fRLUt6+f3u0h3lCmV9eJFALUrefxVsXx6RutPfzuEa/5hRJ+sWXSOXu2
TxSxXDsWOZw8jODnllIzcsL+3vybAkbnWUBb8sgzKeGFaYkLtd298pVIRvgA4T6t
TVpC4YZRHHy15SpiZH+kgl4T8Zki7jS6kSbg7Ri0H14lpVfQULOXG0zDid/toerT
r88eBH8IHI0cjpWAqN0OqBCecAwAcj74weBsicTgy69AZQoAMlpnD7HCkjLtHL/P
NIRo+WqNBNJqcpEx9/07G/xEeXTSnIhy+nh16tkxPG7quO0PgjY=
=7Q2S
-END PGP SIGNATURE End Message ---

Processed: Bug#979693 marked as pending in typescript-types

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979693 [nodejs] nodejs: File conflict with node-typescript-types
Ignoring request to alter tags of bug #979693 to the same tags previously set

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