Processed: severity of 973701 is serious

[Debian Bug Tracking System]

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

> severity 973701 serious
Bug #973701 [network-manager] network-manager: 'systemctl restart 
ModemManager.service' wipes /etc/resolve.conf (almost) clean
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#975203: marked as done (petsc: FTBFS: dh_sphinxdoc: error: error: unknown JavaScript code: debian/petsc3.14-doc/usr/share/doc/petsc3.14-doc/html/_static/doctools.js)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 01:06:19 +
with message-id 
and subject line Bug#975203: fixed in petsc 3.14.1+dfsg1-2
has caused the Debian Bug report #975203,
regarding petsc: FTBFS: dh_sphinxdoc: error: error: unknown JavaScript code: 
debian/petsc3.14-doc/usr/share/doc/petsc3.14-doc/html/_static/doctools.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.)


-- 
975203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: petsc
Version: 3.14.1+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # for some reason dh_sphinxdoc does not recognise jquery, searchtools or 
> underscore
> dh_sphinxdoc -i -Xjquery -Xsearchtools -Xunderscore
> dh_sphinxdoc: error: error: unknown JavaScript code: 
> debian/petsc3.14-doc/usr/share/doc/petsc3.14-doc/html/_static/doctools.js
> make[1]: *** [debian/rules:538: override_dh_sphinxdoc-indep] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/petsc_3.14.1+dfsg1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated petsc 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, 22 Nov 2020 01:29:32 +0800
Source: petsc
Architecture: source
Version: 3.14.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 975203
Changes:
 petsc (3.14.1+dfsg1-2) unstable; urgency=medium
 .
   * provide alternatives links for lowercase petsc.pc pkgconfig files
   * add doctools to the list of js scripts provided in docs which are
 not recognized by dh_sphinxdoc (built by different version of
 sphinx). Closes: #975203.
   * Standards-Version: 4.5.1
Checksums-Sha1:
 2551a5c3fab6f57972822570900bf2465eca9a49 4208 petsc_3.14.1+dfsg1-2.dsc
 5ebded4b05e8612daac1dfd1a443c8efda7c709c 109908 
petsc_3.14.1+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 878a802c8a699da62da3ed161173be92a98daa3b830c491da0957272a69649b0 4208 
petsc_3.14.1+dfsg1-2.dsc
 41c3e21c6203be90e4170d94567e12cc0040851faab0615c1a12b87bb037dce3 109908 
petsc_3.14.1+dfsg1-2.debian.tar.xz
Files:
 71e3cf75637b74ea6e5b0babfefbd577 4208 devel optional petsc_3.14.1+dfsg1-2.dsc
 322b7efa0a75946c87a932122e47821e 109908 devel optional 
petsc_3.14.1+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl+5rrQACgkQVz7x5L1a
AfoTKQ//YbBvixXU5azPW536o7vtdsgtu0Z0RSexaAzl/zBEWUFp9857h2fRKMWK
Ji7cxUKleKb0HkIXt272KnyFxmuTQw86bCQMcW1eC+TZ8xV2YSMNSipPIOAeCqXw
B4/IJmEQSBY/903nWxtj0nsqQrEW2CdpNH47VCs7DqotnW+WBQeYx8tR5Z7EtJOr
6o7pZfZpe3DDoeg4Uj2MUotU8lBv8nRjEYJ/xMPz8pkNWGdUpAcmVftWlIGheSAr
m8dbpZ06dwebYrbArghQ0CVa/ToR+Tr/w2mmsf/gFwMpjaQcQGU8zCKKkyReisBi
cRuvGTSmBx0ql7Lk2LnInz4rURPJ8mMiNMi1tXVO0ZdaY17pczp8qEMagD+QjK5J
yV78Mn2OpdyLJgiIU6/xj+FNBPZxTdec+uwwJQZvret7rJ4pvitmrRIVKsuOozGm
S5KsPmRiH7ZChVTB83Q1ZDJrkj4HntxLjaLar2tWkI48WdmVRoH7QSwAL5jtQgSk
oiSKjUYiGedNcG61SXIVmtaP7jtigScnkbeq6aPhNhwflKBgxAd1Jo1U8ABiycXO
AzJwSNhUICDhwyler+sfxwPMJpXSSLlzcQgTgt+TMdPtPknKUsn/OcztvgMJXJyz
d2z2azeuQ08Ef2s8/YrXyolqh4kovNM9mpNbKH2YzVnit0OdrMw=
=9Oaw
-END PGP SIGNATURE End Message ---

Bug#972749: xen-tools: bullseye: /updates -> -security

[Axel Beckert]

Hi,

Paul Wise wrote:
> Sure, short-term hardcoding is fine, although short-term hardcoding
> usually turns into long-term hardcoding surprisingly quickly ;)

A so called "providurium". ;-)

> So perhaps leave this bug open or clone and retitle it as a reminder to
> switch from hardcoding to the new mechanism when that happens.

Yeah, but severity wishlist at most. I don't see it gonna happen with
just me a s upstream maintainer.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#968965: [Pkg-xen-devel] Bug#968965: xen: FTBFS woes in sid

[Hans van Kranenburg]

On 11/20/20 8:02 PM, Hans van Kranenburg wrote:
> So,
> 
> On 9/21/20 4:16 PM, Hans van Kranenburg wrote:
>> [...]
>>
> [...]
>  >8 
> 
> dh_install: warning: Cannot find (any matches for)
> "usr/lib/debug/usr/lib/xen-*/boot/*" (tried in ., debian/tmp)
> 
> dh_install: warning: xen-utils-4.14 missing files:
> usr/lib/debug/usr/lib/xen-*/boot/*
> dh_install: error: missing files, aborting
> 
>  >8 
> 
> I can only find CONFIG_PV_SHIM=n in the build log. What is going on
> here? Attached is the build log.

Ok, this probably has something to do with upstream commit 8845155c83
"pvshim: make PV shim build selectable from configure" (Xen 4.12) which
causes the shim not to be built during our i386 build any more.

In Xen 4.11 we have commit a516bddbd3 "tools/firmware/Makefile:
CONFIG_PV_SHIM: enable only on x86_64". The part of this file that this
patch changes is removed in the above mentioned commit.

Because all of this is such a big mess, I just tried to revert
8845155c83 and then do 0b898ccc2 and a516bddbd3 on top of the previous
code again.

And, yes, now it goes through, and ./usr/lib/xen-4.14/boot/xen-shim is
included in the i386 package. At least we have a workaround now.

> My WIP branch is here (including the make-patches commit, it's ready to
> build). I also forwarded the thing to latest stable-4.14.

Again at:

> https://salsa.debian.org/xen-team/debian-xen/-/commits/knorrie/4.14/

I'll rerun both the amd64 and i386 build here and actually boot the
amd64 packages in a test environment. If success, then I'm going to try
put this in experimental again so we can see if it all succeeds on the
buildds.

Then after final review we should be able to upload to unstable
beginning next week.

K

Bug#974532: marked as done (src:libctl: fails to migrate to testing for too long: FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 00:39:49 +
with message-id 
and subject line Bug#974532: fixed in libctl 4.5.0-6
has caused the Debian Bug report #974532,
regarding src:libctl: fails to migrate to testing for too long: FTBFS
to be marked as done.

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

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


-- 
974532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libctl
Version: 4.5.0-4
Severity: serious
Control: close -1 4.5.0-5
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 970233

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libctl
Source-Version: 4.5.0-6
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libctl 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, 22 Nov 2020 00:25:02 +0100
Source: libctl
Architecture: source
Version: 4.5.0-6
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 970233 974532
Changes:
 libctl (4.5.0-6) unstable; urgency=medium
 .
   * make package build again (Closes: #974532)
   * move examples to -dev package (Closes: #970233)
Checksums-Sha1:
 24861b9be064d3f39782569bd9b38ac04c4e7eb1 2115 libctl_4.5.0-6.dsc
 39c7748bc3b64f674d338b68f1e69c3d4f732555 8764 libctl_4.5.0-6.debian.tar.xz
 5b578a97ba64113df3eb0ce736df49c9d24e81f6 7457 libctl_4.5.0-6_amd64.buildinfo
Checksums-Sha256:
 3bf2085a037202a5556587165918dec274374b25f8244172f738bf25cdca09de 2115 
libctl_4.5.0-6.dsc
 cf265b2ea85ea4c7f20ed2a5c9e87229c24d8eefdf673d16b7a0c95dbbe6c2f4 8764 
libctl_4.5.0-6.debian.tar.xz
 05f15db4f1d61bb34cc76db71e593eee320642ce32cffaa0c4e8c7e007a655dd 7457 
libctl_4.5.0-6_amd64.buildinfo
Files:
 5964b8b2ea36c56c91da609950ff118c 2115 devel optional libctl_4.5.0-6.dsc
 fc6c7fa1515b81ac04f7dd2cbe4af5ec 8764 devel optional 
libctl_4.5.0-6.debian.tar.xz
 b15fb555da4aa6f29de7bc9ca435dbdb 7457 devel optional 
libctl_4.5.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl+5rTlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR7xKEACLRtbAxeIscVSsqAZKKwpZCNDJxXlu
K1RfScJjhIGzTQQ4Sev+0d0a52CKOZEYrLi60Dj7Oq6lHYUYXqVj9pJ9J/orup6x
xrSaR6B+kR+BVGTZYwqeAnOw+TJW67ysouXIybzLFxRKaWQprc

Bug#970233: marked as done (libctl: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 00:39:49 +
with message-id 
and subject line Bug#970233: fixed in libctl 4.5.0-6
has caused the Debian Bug report #970233,
regarding libctl: binary-any FTBFS
to be marked as done.

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

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


-- 
970233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libctl
Version: 4.5.0-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=libctl&suite=sid

...
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples
sed -i -e 's@/<>/.@/usr/share/libctl@g' 
debian/libctl-doc/usr/share/doc/libctl-dev/examples/example.scm
sed: can't read 
debian/libctl-doc/usr/share/doc/libctl-dev/examples/example.scm: No such file 
or directory
make[1]: *** [debian/rules:20: override_dh_installexamples] Error 2
--- End Message ---
--- Begin Message ---
Source: libctl
Source-Version: 4.5.0-6
Done: Thorsten Alteholz 

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libctl 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, 22 Nov 2020 00:25:02 +0100
Source: libctl
Architecture: source
Version: 4.5.0-6
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 970233 974532
Changes:
 libctl (4.5.0-6) unstable; urgency=medium
 .
   * make package build again (Closes: #974532)
   * move examples to -dev package (Closes: #970233)
Checksums-Sha1:
 24861b9be064d3f39782569bd9b38ac04c4e7eb1 2115 libctl_4.5.0-6.dsc
 39c7748bc3b64f674d338b68f1e69c3d4f732555 8764 libctl_4.5.0-6.debian.tar.xz
 5b578a97ba64113df3eb0ce736df49c9d24e81f6 7457 libctl_4.5.0-6_amd64.buildinfo
Checksums-Sha256:
 3bf2085a037202a5556587165918dec274374b25f8244172f738bf25cdca09de 2115 
libctl_4.5.0-6.dsc
 cf265b2ea85ea4c7f20ed2a5c9e87229c24d8eefdf673d16b7a0c95dbbe6c2f4 8764 
libctl_4.5.0-6.debian.tar.xz
 05f15db4f1d61bb34cc76db71e593eee320642ce32cffaa0c4e8c7e007a655dd 7457 
libctl_4.5.0-6_amd64.buildinfo
Files:
 5964b8b2ea36c56c91da609950ff118c 2115 devel optional libctl_4.5.0-6.dsc
 fc6c7fa1515b81ac04f7dd2cbe4af5ec 8764 devel optional 
libctl_4.5.0-6.debian.tar.xz
 b15fb555da4aa6f29de7bc9ca435dbdb 7457 devel optional 
libctl_4.5.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl+5rTlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR7xKEACLRtbAxeIscVSsqAZKKwpZCNDJxXlu
K1RfScJjhIGzTQQ4Sev+0d0a52CKOZEYrLi60Dj7Oq6lHYUYXqVj9pJ9J/orup6x
xrSaR6B+kR+BVGTZYwqeAnOw+TJW67ysouXIybzLFxRKaWQprchHRjxI4TEafnew
CJ+8aaJ1zgwYOIA90KLCmtqUbGpjxRHZZ2yNy/ESW88ueKfvnnoRE+qwXkSY7wqU
08KF3ufxnF/rYSrbV5Dc2tXoS4iM/vI69M85NeK7zo1cUkWDpmM5bsBJ8BtiyRLB
lcfdIbNxzCXuIZunIPqpYZAW+xI8YXLKPjiADfd9cNCQRutEwjFaDy+x+sR0IObJ
uBQeOxevzoQoi25NnCoQazrvSW/v1/1JV5i0hxRqAIfAe6I1IDRw+YjteFqYvOKe
1zX0oxSRguCNw+5fbZAtMRQGYZnFQb7psiwdTXxpjdEvw5ev2VC8HCKQOF3FyVXS
K1KYo3EQUj7ekQcNeaRzXwits9neEYphgupNgs9pXf8gtk5llkL1yJkpxOowh5YY
ikcgDAoNe5JKyb2w6/x8hilYJzrR3cI/4D9NC9MhFHRXbmAfLgLYNAwqjGzMpSJA
nsoccPatiIO+8IUVd3ZR/APn9zycXVRLkn8yQLF/1SAPG6hIySe7Q+/m4EQCKArr
GEDKbT17hh8aog==
=KysZ
-END PGP SIGNATURE End Message ---

Bug#975423: pam-python: needs a source only upload.

[peter green]

Package: pam-python
Version: 1.0.9-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing.
Please make a source-only upload so your package can migrate.

Bug#975225: marked as done (junit5: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 23:48:56 +
with message-id 
and subject line Bug#975225: fixed in junit5 5.3.2-4
has caused the Debian Bug report #975225,
regarding junit5: FTBFS: test failed
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=junit5 -Dfile.encoding=UTF-8 --parallel 
> --max-workers=4 jar
> Initialized native services in: /<>/.gradle/native
> Using 4 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@6e4de19b
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@6e4de19b
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@2427e004
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on 
> org.gradle.internal.reflect.JavaMethod 
> (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class 
> java.lang.ClassLoader
> WARNING: Please consider reporting this to the maintainers of 
> org.gradle.internal.reflect.JavaMethod
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@dd2856e
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'junit5', project ':documentation', project 
> ':junit-bom', project ':junit-jupiter-api', project ':junit-jupiter-engine', 
> project ':junit-jupiter-migrationsupport', project ':junit-jupiter-params', 
> project ':junit-platform-commons', project ':junit-platform-commons-java-9', 
> project ':junit-platform-console', project 
> ':junit-platform-console-standalone', project ':junit-platform-engine', 
> project ':junit-platform-launcher', project ':junit-platform-runner', project 
> ':junit-platform-suite-api', project ':junit-platform-surefire-provider', 
> project ':junit-vintage-engine']
>   Keep-alive timer started
>   Adding Debian repository to project 'junit5'
>   Adding Debian repository to project 'documentation'
>   Adding Debian repository to project 'junit-bom'
>   Adding Debian repository to project 'junit-jupiter-api'
>   Adding Debian repository to project 'junit-jupiter-engine'
>   Adding Debian repository to project 'junit-jupiter-migrationsupport'
>   Adding Debian repository to project 'junit-jupiter-params'
>   Adding Debian repository to project 'junit-platform-commons'
>   Adding Debian repository to project 'junit-platform-commons-java-9'
>   Adding Debian repository to project 'junit-platform-console'
>   Adding Debian repository to project 'junit-platform-console-standalone'
>   Adding Debian repository to project 'junit-platform-engine'
>   Adding Debian repository to project 'junit-platform-launcher'
>   Adding Debian repository to project 'junit-platform-runner'
>   Adding Debian repository to project 'junit-platform-suite-api'
>   Adding Debian repository to project 'junit-platform-sur

Bug#957759: marked as done (repmgr: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 23:49:14 +
with message-id <81f0de33-b1ae-4b40-f6a0-5c98a556f...@p10link.net>
and subject line re: repmgr: ftbfs with GCC-10
has caused the Debian Bug report #957759,
regarding repmgr: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
/<>/repmgr-action-standby.c: In function ‘do_standby_clone’:
/<>/repmgr-action-standby.c:6923:30: note: length computed here
 6923 |  strncpy(cell->oid, oid, 1 + strlen(oid));
  |  ^~~
In file included from /usr/include/string.h:495,
 from /usr/include/postgresql/internal/c.h:61,
 from /usr/include/postgresql/internal/postgres_fe.h:25,
 from /<>/repmgr.h:65,
 from /<>/repmgr-action-standby.c:24:
In function ‘strncpy’,
inlined from ‘tablespace_data_append’ at 
/<>/repmgr-action-standby.c:6924:2,
inlined from ‘get_tablespace_data_barman’ at 
/<>/repmgr-action-standby.c:6780:3,
inlined from ‘run_file_backup’ at 
/<>/repmgr-action-standby.c:6288:8,
inlined from ‘do_standby_clone’ at 
/<>/repmgr-action-standby.c:626:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
/<>/repmgr-action-standby.c: In function ‘do_standby_clone’:
/<>/repmgr-action-standby.c:6924:32: note: length computed here
 6924 |  strncpy(cell->name, name, 1 + strlen(name));
  |^~~~
In file included from /usr/include/string.h:495,
 from /usr/include/postgresql/internal/c.h:61,
 from /usr/include/postgresql/internal/postgres_fe.h:25,
 from /<>/repmgr.h:65,
 from /<>/repmgr-action-standby.c:24:
In function ‘strncpy’,
inlined from ‘tablespace_data_append’ at 
/<>/repmgr-action-standby.c:6925:2,
inlined from ‘get_tablespace_data_barman’ at 
/<>/repmgr-action-standby.c:6780:3,
inlined from ‘run_file_backup’ at 
/<>/repmgr-action-standby.c:6288:8,
inlined from ‘do_standby_clone’ at 
/<>/repmgr-action-standby.c:626:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
/<>/repmgr-action-standby.c: In function ‘do_standby_clone’:
/<>/repmgr-action-standby.c:6925:40: note: length computed here
 6925 |  strncpy(cell->location, location, 1 + strlen(location));
  |^~~~
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation 
-Wno-stringop-truncation 

Bug#929710: marked as done (libopenzwave1.6-dev: missing Breaks+Replaces: libopenzwave1.5-dev)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:53:07 +
with message-id 
and subject line Bug#929710: fixed in openzwave 1.6.1545+ds-1
has caused the Debian Bug report #929710,
regarding libopenzwave1.6-dev: missing Breaks+Replaces: libopenzwave1.5-dev
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.)


-- 
929710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenzwave1.6-dev
Version: 1.6+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libopenzwave1.6-dev_1.6+ds-1_amd64.deb ...
  Unpacking libopenzwave1.6-dev (1.6+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libopenzwave1.6-dev_1.6+ds-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/openzwave/Bitfield.h', which is also in 
package libopenzwave1.5-dev 1.5+ds-6
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libopenzwave1.6-dev_1.6+ds-1_amd64.deb


cheers,

Andreas


libopenzwave1.5-dev=1.5+ds-6_libopenzwave1.6-dev=1.6+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openzwave
Source-Version: 1.6.1545+ds-1
Done: Nicolas Mora 

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

Debian distribution maintenance software
pp.
Nicolas Mora  (supplier of updated openzwave 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, 21 Nov 2020 09:28:41 -0500
Source: openzwave
Architecture: source
Version: 1.6.1545+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Nicolas Mora 
Closes: 929710
Changes:
 openzwave (1.6.1545+ds-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * d/control: Add breaks+replace previous version 1.5 (Closes: #929710)
   * d/patches: remove patches compile-error, fix-compiler-warnings
update modify-flags, spelling
   * d/install: install libopenzwave.a
   * d/tests: update autopkgtests to use installed libopenzwave.a
   * d/control: Add Rules-Requires-Root: no
   * d/rules: Use dpkg-dev to get package version instead of dpkg-parsechangelog
Checksums-Sha1:
 cc16280052af8138668dd228053f8534c1e9442f 2344 openzwave_1.6.1545+ds-1.dsc
 1b257fc0decf57e27bfb70961b3c2df8a58c3c57 17364602 
openzwave_1.6.1545+ds.orig.tar.gz
 929741e79b26f90344afd385bdebdfe37f1e7f09 7228 
openzwave_1.6.1545+ds-1.debian.tar.xz
 270be4694696d9eaf7bc925dbfcf14496a709aaf 7863 
openzwave_1.6.1545+ds-1_amd64.buildinfo
Checksums-Sha256:
 aabad51a8bd0ebfcf02b126e238958000580c4a2dbd13e652535ac69901517f6 2344 
openzwave_1.6.1545+ds-1.dsc
 806c18cc4e80552c25cd477be811ea64c5ff81c00bc9a3c4f498f3d4944e8232 17364602 
openzwave_1.6.1545+ds.orig.tar.gz
 1e311689efa012af4472d9cddbc01ba457005ba1df3e879343e8fa34d3ee64bd 7228 
openzwave_1.6.1545+ds-1.debian.tar.xz
 c58aac8a420e8f43803010a7d490c4a09eba094af073de9879d74edfdd8a0fa5 7863 
openzwave_1.6.1545+ds-1_amd64.buildinfo
Files:
 3b2c45b7a2270df510bee89791f82562 2344 devel optional 
openzwave_1.6.1545+ds-1.dsc
 27f912fb255211eb3b6543ba6937604f 17364602 devel optional 
openzwave_1.6.1545+ds.orig.tar.gz
 06008eefd58a1dba160b41c5acebcd74 7228 devel optional 
openzwave_1.6.1545+ds-1.debian.tar.xz
 90802826e6e8383f32662aeb21e8d3d3 7863 devel optional 
openzwave_1.6.1545+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAl+5k9wACgkQ/oITlEC9
IrnlyBAAnmbc1KNMohpI55EnTZ9zbXXkhFUrJrEznCYA8TvIlOrwRuTj

Bug#972053: marked as done (CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 CVE-2019-20631 CVE-2019-20632 CVE-202

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:34:07 +
with message-id 
and subject line Bug#972053: fixed in gpac 1.0.1+dfsg1-2
has caused the Debian Bug report #972053,
regarding CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 
CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 
CVE-2019-20631 CVE-2019-20632 CVE-2020-11558 CVE-2020-6630 CVE-2020-6631
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.)


-- 
972053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpac
Version: 0.5.2-426-gc5ad4e4+dfsg5-5
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2019-20161:
https://github.com/gpac/gpac/issues/1320
https://github.com/gpac/gpac/commit/7a09732d4978586e6284e84caa9c301b2fa5e956

CVE-2019-20162:
https://github.com/gpac/gpac/issues/1327
https://github.com/gpac/gpac/commit/3c0ba42546c8148c51169c3908e845c308746c77

CVE-2019-20163:
https://github.com/gpac/gpac/issues/1335
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #4)

CVE-2019-20165:
https://github.com/gpac/gpac/issues/1338
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #1)

CVE-2019-20170:
https://github.com/gpac/gpac/issues/1328
https://github.com/gpac/gpac/commit/16856430287cc10f495eb241910b4dc45b193e03

CVE-2019-20171:
https://github.com/gpac/gpac/issues/1337
https://github.com/gpac/gpac/commit/72cdc5048dead86bb1df7d21e0b9975e49cf2d97
https://github.com/gpac/gpac/commit/2bcca3f1d4605100bb27d3ed7be25b53cddbc75c

CVE-2019-20208:
https://github.com/gpac/gpac/issues/1348
https://github.com/gpac/gpac/commit/bcfcb3e90476692fe0d2bb532ea8deeb2a77580e 
(chunk #1)

CVE-2019-20628:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/commit/98b727637e32d1d4824101d8947e2dbd573d4fc8
https://github.com/gpac/gpac/issues/1269

CVE-2019-20629:
https://github.com/gpac/gpac/commit/2320eb73afba753b39b7147be91f7be7afc0eeb7
https://github.com/gpac/gpac/issues/1264

CVE-2019-20630:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1268

CVE-2019-20631:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1270

CVE-2019-20632:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1271

CVE-2020-11558:
https://github.com/gpac/gpac/commit/6063b1a011c3f80cee25daade18154e15e4c058c
https://github.com/gpac/gpac/issues/1440

CVE-2020-6630:
https://github.com/gpac/gpac/issues/1377
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521

CVE-2020-6631:
https://github.com/gpac/gpac/issues/1378
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521
  
While individual commits refs are listed above, this should really be fixed
via a new upstream release for bullseye, after all the current base version
is from 2015
--- End Message ---
--- Begin Message ---
Source: gpac
Source-Version: 1.0.1+dfsg1-2
Done: Reinhard Tartler 

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

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

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated gpac 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, 21 Nov 2020 17:13:44 -0500
Source: gpac
Architecture: source
Version: 1.0.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Reinhard Tartler 
Closes: 782093 931088 932242 940882 972053
Changes:
 gpac (1.0.1+dfsg1-2) unstable; urgency=medium
 .
   * Upload to unstable
 .
 gpac (1.0.1+dfsg1-1) experimental; urgency=medium
 .
   * New upstream version
 - soname bump to libgpac10
 - Fixes lots of security issues, closes: #972053
CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165
CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629
   

Bug#968965: xen: FTBFS woes in sid

[Hans van Kranenburg]

On 11/21/20 5:40 AM, Elliott Mitchell wrote:
> On Fri, Nov 20, 2020 at 08:02:26PM +0100, Hans van Kranenburg wrote:
>> So,
>>
>> On 9/21/20 4:16 PM, Hans van Kranenburg wrote:
>>> [...]
>>>
>>> gcc-Wl,-z,relro -Wl,-z,now -pthread -Wl,-soname
>>> -Wl,libxentoolcore.so.1 -shared -Wl,--version-script=libxentoolcore.map
>>> -o libxentoolcore.so.1.0 handlereg.opic
>>> /usr/bin/ld: i386:x86-64 architecture of input file `handlereg.opic' is
>>> incompatible with i386 output
>>> /usr/bin/ld: handlereg.opic: file class ELFCLASS64 incompatible with
>>> ELFCLASS32
>>> /usr/bin/ld: final link failed: file in wrong format
>>> collect2: error: ld returned 1 exit status
>>
>> This one is caused by "debian/rules: Combine shared Make args". I
>> reverted that change for now.
>>
>> [...]
> 
> I was going to type, "That can't be true!  Both sections are identical,
> so that commit *couldn't* have done it!"
> 
> Being the careful sort, look closer.  Look closer.  Then realize if one
> reads fast they look identical, but they're getting *slightly* different
> values for ${XEN_TARGET_ARCH}.  Mainly for $(make_args_xen),
> ${XEN_TARGET_ARCH} gets $(xen_arch_$(flavour)), but for
> $(make_args_tools), ${XEN_TARGET_ARCH} gets $(xen_arch_$(DEB_HOST_ARCH)).
> 
> Three of us and we didn't spot that difference.  Should still combine
> ${XEN_COMPILE_ARCH} which remains identical for both values.

Ok, I will make it a partial revert and add the above information about it.

Thanks.

Hans

Bug#975188: marked as done (rust-native-tls: FTBFS: build-dependency not installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:15 +
with message-id 
and subject line Bug#975188: fixed in rust-foreign-types-0.3 0.3.2-1
has caused the Debian Bug report #975188,
regarding rust-native-tls: FTBFS: build-dependency not installable: 
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
to be marked as done.

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

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


-- 
975188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-native-tls
Version: 0.2.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-lazy-static-1+default-dev, 
> librust-libc-0.2+default-dev, librust-log-0.4+default-dev (>= 0.4.5-~~), 
> librust-openssl-0.10+default-dev (>= 0.10.25-~~), 
> librust-openssl-probe-0.1+default-dev, librust-openssl-sys-0.9+default-dev 
> (>= 0.9.30-~~), librust-schannel-0.1+default-dev (>= 0.1.16-~~), 
> librust-security-framework-sys-0.4+default-dev (>= 0.4.1-~~), 
> librust-tempfile-3+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-lazy-static-1+default-dev, 
> librust-libc-0.2+default-dev, librust-log-0.4+default-dev (>= 0.4.5-~~), 
> librust-openssl-0.10+default-dev (>= 0.10.25-~~), 
> librust-openssl-probe-0.1+default-dev, librust-openssl-sys-0.9+default-dev 
> (>= 0.9.30-~~), librust-schannel-0.1+default-dev (>= 0.1.16-~~), 
> librust-security-framework-sys-0.4+default-dev (>= 0.4.1-~~), 
> librust-tempfile-3+default-dev, build-essential, fakeroot
> 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 [529 B]
> Get:5 copy:/<>/apt_archive ./ Packages [604 B]
> Fetched 2096 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:
>  librust-openssl-dev : Depends: librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~) 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/11/19/rust-native-tls_0.2.4-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rust-foreign-types-0.3
Source-Version: 0.3.2-1
Done: Fabio Rafael da Rosa 

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

Debian distribution maintenance software
pp.
Fabio Rafael da Rosa  (supplier of updated 
rust-foreign-types-0.3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the a

Bug#975182: marked as done (rust-crypto-hash: FTBFS: build-dependency not installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:15 +
with message-id 
and subject line Bug#975182: fixed in rust-foreign-types-0.3 0.3.2-1
has caused the Debian Bug report #975182,
regarding rust-crypto-hash: FTBFS: build-dependency not installable: 
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
to be marked as done.

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

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


-- 
975182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-crypto-hash
Version: 0.3.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-commoncrypto-0.2+default-dev, 
> librust-hex-0.4+default-dev, librust-openssl-0.10+default-dev, 
> librust-winapi-0.3+default-dev, librust-winapi-0.3+minwindef-dev, 
> librust-winapi-0.3+wincrypt-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-commoncrypto-0.2+default-dev, 
> librust-hex-0.4+default-dev, librust-openssl-0.10+default-dev, 
> librust-winapi-0.3+default-dev, librust-winapi-0.3+minwindef-dev, 
> librust-winapi-0.3+wincrypt-dev, build-essential, fakeroot
> 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 [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [466 B]
> Get:5 copy:/<>/apt_archive ./ Packages [535 B]
> Fetched 1958 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:
>  librust-openssl-dev : Depends: librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~) 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/11/19/rust-crypto-hash_0.3.4-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rust-foreign-types-0.3
Source-Version: 0.3.2-1
Done: Fabio Rafael da Rosa 

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

Debian distribution maintenance software
pp.
Fabio Rafael da Rosa  (supplier of updated 
rust-foreign-types-0.3 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: Thu, 19 Nov 2020 21:01:37 CET
Source: rust-foreign-types-0.3
Binary: librust-foreign-types-0.3-dev
Architecture: amd64 source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Fabio Rafael da Rosa 
Descriptio

Bug#975185: marked as done (rust-openssl: FTBFS: build-dependency not installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:15 +
with message-id 
and subject line Bug#975185: fixed in rust-foreign-types-0.3 0.3.2-1
has caused the Debian Bug report #975185,
regarding rust-openssl: FTBFS: build-dependency not installable: 
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
to be marked as done.

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

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


-- 
975185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-openssl
Version: 0.10.29-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-bitflags-1+default-dev, 
> librust-cfg-if-0.1+default-dev, librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~), librust-lazy-static-1+default-dev, librust-libc-0.2+default-dev, 
> librust-openssl-sys-0.9+default-dev (>= 0.9.55-~~), build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-bitflags-1+default-dev, 
> librust-cfg-if-0.1+default-dev, librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~), librust-lazy-static-1+default-dev, librust-libc-0.2+default-dev, 
> librust-openssl-sys-0.9+default-dev (>= 0.9.55-~~), build-essential, fakeroot
> 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 [960 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [492 B]
> Get:5 copy:/<>/apt_archive ./ Packages [563 B]
> Fetched 2015 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: 
> librust-foreign-types-0.3+default-dev (>= 0.3.1-~~) 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/11/19/rust-openssl_0.10.29-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rust-foreign-types-0.3
Source-Version: 0.3.2-1
Done: Fabio Rafael da Rosa 

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

Debian distribution maintenance software
pp.
Fabio Rafael da Rosa  (supplier of updated 
rust-foreign-types-0.3 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: Thu, 19 Nov 2020 21:01:37 CET
Source: rust-foreign-types-0.3
Binary: librust-foreign-types-0.3-dev
Architecture: amd64 source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer

Bug#975181: marked as done (rust-publicsuffix: FTBFS: build-dependency not installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:15 +
with message-id 
and subject line Bug#975181: fixed in rust-foreign-types-0.3 0.3.2-1
has caused the Debian Bug report #975181,
regarding rust-publicsuffix: FTBFS: build-dependency not installable: 
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
to be marked as done.

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

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


-- 
975181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-publicsuffix
Version: 1.5.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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), dh-cargo (>= 15), cargo, rustc, 
> libstd-rust-dev, librust-error-chain-0.12+default-dev, 
> librust-idna-0.2+default-dev, librust-lazy-static-1+default-dev, 
> librust-native-tls-0.2+default-dev, librust-regex-1+default-dev, 
> librust-url-2+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 15), cargo, rustc, 
> libstd-rust-dev, librust-error-chain-0.12+default-dev, 
> librust-idna-0.2+default-dev, librust-lazy-static-1+default-dev, 
> librust-native-tls-0.2+default-dev, librust-regex-1+default-dev, 
> librust-url-2+default-dev, build-essential, fakeroot
> 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 [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [462 B]
> Get:5 copy:/<>/apt_archive ./ Packages [535 B]
> Fetched 1954 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:
>  librust-openssl-dev : Depends: librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~) 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/11/19/rust-publicsuffix_1.5.2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rust-foreign-types-0.3
Source-Version: 0.3.2-1
Done: Fabio Rafael da Rosa 

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

Debian distribution maintenance software
pp.
Fabio Rafael da Rosa  (supplier of updated 
rust-foreign-types-0.3 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: Thu, 19 Nov 2020 21:01:37 CET
Source: rust-foreign-types-0.3
Binary: librust-foreign-types-0.3-dev
Architecture: amd64 source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Fabio Rafael da Rosa 
Description: 
 li

Bug#975172: marked as done (rust-hyper-tls: FTBFS: build-dependency not installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:15 +
with message-id 
and subject line Bug#975172: fixed in rust-foreign-types-0.3 0.3.2-1
has caused the Debian Bug report #975172,
regarding rust-hyper-tls: FTBFS: build-dependency not installable: 
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
to be marked as done.

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

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


-- 
975172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-hyper-tls
Version: 0.3.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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), dh-cargo (>= 15), cargo, rustc, 
> libstd-rust-dev, librust-bytes-0.4+default-dev, 
> librust-futures-0.1+default-dev (>= 0.1.21-~~), 
> librust-hyper-0.12+default-dev, librust-native-tls-0.2+default-dev, 
> librust-tokio-io-0.1+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 15), cargo, rustc, 
> libstd-rust-dev, librust-bytes-0.4+default-dev, 
> librust-futures-0.1+default-dev (>= 0.1.21-~~), 
> librust-hyper-0.12+default-dev, librust-native-tls-0.2+default-dev, 
> librust-tokio-io-0.1+default-dev, build-essential, fakeroot
> 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 [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [468 B]
> Get:5 copy:/<>/apt_archive ./ Packages [544 B]
> Fetched 1969 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:
>  librust-openssl-dev : Depends: librust-foreign-types-0.3+default-dev (>= 
> 0.3.1-~~) 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/11/19/rust-hyper-tls_0.3.2-2_unstable.log

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

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: rust-foreign-types-0.3
Source-Version: 0.3.2-1
Done: Fabio Rafael da Rosa 

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

Debian distribution maintenance software
pp.
Fabio Rafael da Rosa  (supplier of updated 
rust-foreign-types-0.3 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: Thu, 19 Nov 2020 21:01:37 CET
Source: rust-foreign-types-0.3
Binary: librust-foreign-types-0.3-dev
Architecture: amd64 source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Fabio Rafael da Rosa 
Description: 
 librust-foreign-types-0.3-dev - Framewo

Bug#974722: marked as done (slurm-llnl: CVE-2020-27746: X11 forwarding - fix potential leak of the magic cookie when sent as an argument to the xauth command)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:18 +
with message-id 
and subject line Bug#974722: fixed in slurm-wlm 20.02.6-1
has caused the Debian Bug report #974722,
regarding slurm-llnl: CVE-2020-27746: X11 forwarding - fix potential leak of 
the magic cookie when sent as an argument to the xauth command
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.)


-- 
974722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-llnl
Version: 19.05.5-2.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2020-27746[0]:
| X11 forwarding - avoid unsafe use of magic cookie as arg to xauth
| command

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-27746
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27746
[1] 
https://github.com/SchedMD/slurm/commit/07309deb45c33e735e191faf9dd31cca1054a15c
[2] https://lists.schedmd.com/pipermail/slurm-announce/2020/45.html
[3] https://www.schedmd.com/news.php?id=240

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 20.02.6-1
Done: Gennaro Oliva 

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Nov 2020 00:11:42 +0100
Source: slurm-wlm
Binary: libpam-slurm libpam-slurm-adopt libpmi0 libpmi0-dbgsym libpmi0-dev 
libpmi2-0 libpmi2-0-dbgsym libpmi2-0-dev libslurm-dev libslurm-perl libslurm35 
libslurm35-dbgsym libslurmdb-perl slurm-client slurm-client-dbgsym 
slurm-client-emulator slurm-wlm slurm-wlm-basic-plugins 
slurm-wlm-basic-plugins-dbgsym slurm-wlm-basic-plugins-dev slurm-wlm-doc 
slurm-wlm-emulator slurm-wlm-torque slurmctld slurmctld-dbgsym slurmd 
slurmd-dbgsym slurmdbd slurmdbd-dbgsym sview
Architecture: source amd64 all
Version: 20.02.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpam-slurm-adopt - PAM module to authenticate users running a SLURM job and 
track th
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libpmi2-0  - SLURM PMI2 library implementation
 libpmi2-0-dev - SLURM PMI2 library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm35 - Runtime library files for SLURM
 libslurmdb-perl - Perl API for the SLURM database
 slurm-client - SLURM client side commands
 slurm-client-emulator - SLURM client side commands for the emulator
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM documentation
 slurm-wlm-emulator - SLURM emulator
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state
Closes: 949734 974721 974722
Changes:
 slurm-wlm (20.02.6-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #974721, #974722)
   * Refresh miscellanea-manpages and mail-path patches
   * Remove use-python3 patch included upstream
   * Remove smap command
   * Remove cray.conf.5 man page
   * Bump libslurm to soname 35
   * Update configurators
   * Fix the slurmdbd example file (Closes: #949734)
   * Remove l

Bug#974721: marked as done (slurm-llnl: CVE-2020-27745: PMIx - fix potential buffer overflows from use of unpackmem())

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 22:00:18 +
with message-id 
and subject line Bug#974721: fixed in slurm-wlm 20.02.6-1
has caused the Debian Bug report #974721,
regarding slurm-llnl: CVE-2020-27745: PMIx - fix potential buffer overflows 
from use of unpackmem()
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.)


-- 
974721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-llnl
Version: 19.05.5-2.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2020-27745[0]:
| PMIx - fix potential buffer overflows from use of unpackmem()

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-27745
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27745
[1] 
https://github.com/SchedMD/slurm/commit/c3142dd87e06621ff148791c3d2f298b5c0b3a81
[2] https://lists.schedmd.com/pipermail/slurm-announce/2020/45.html
[3] https://www.schedmd.com/news.php?id=240

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 20.02.6-1
Done: Gennaro Oliva 

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Nov 2020 00:11:42 +0100
Source: slurm-wlm
Binary: libpam-slurm libpam-slurm-adopt libpmi0 libpmi0-dbgsym libpmi0-dev 
libpmi2-0 libpmi2-0-dbgsym libpmi2-0-dev libslurm-dev libslurm-perl libslurm35 
libslurm35-dbgsym libslurmdb-perl slurm-client slurm-client-dbgsym 
slurm-client-emulator slurm-wlm slurm-wlm-basic-plugins 
slurm-wlm-basic-plugins-dbgsym slurm-wlm-basic-plugins-dev slurm-wlm-doc 
slurm-wlm-emulator slurm-wlm-torque slurmctld slurmctld-dbgsym slurmd 
slurmd-dbgsym slurmdbd slurmdbd-dbgsym sview
Architecture: source amd64 all
Version: 20.02.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpam-slurm-adopt - PAM module to authenticate users running a SLURM job and 
track th
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libpmi2-0  - SLURM PMI2 library implementation
 libpmi2-0-dev - SLURM PMI2 library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm35 - Runtime library files for SLURM
 libslurmdb-perl - Perl API for the SLURM database
 slurm-client - SLURM client side commands
 slurm-client-emulator - SLURM client side commands for the emulator
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM documentation
 slurm-wlm-emulator - SLURM emulator
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state
Closes: 949734 974721 974722
Changes:
 slurm-wlm (20.02.6-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #974721, #974722)
   * Refresh miscellanea-manpages and mail-path patches
   * Remove use-python3 patch included upstream
   * Remove smap command
   * Remove cray.conf.5 man page
   * Bump libslurm to soname 35
   * Update configurators
   * Fix the slurmdbd example file (Closes: #949734)
   * Remove llnl from the source package name and from the
 con

Bug#975418: ostree: FTBFS with test failure on some filesystems: tests/test-pull-summary-sigs.sh: Successful pull with old summary

[Simon McVittie]

Source: ostree
Version: 2020.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

ostree 2020.8-1 successfully built in my build environment (sbuild on a
qemu VM running Debian 10, with ext4 filesystems) and on mips*el and
various ports architectures, but failed on all non-mips*el release
architectures.

I think this might be filesystem-dependent: the equivalent installed-test
succeeds when run from an empty directory on btrfs, but fails when run
from an empty directory on tmpfs. I'm looking into it, no need to report
it again.

>From the point at which the test fails, it might be to do with timestamp
resolution?

smcv

Bug#958592: marked as done (open-isns: Build-Depends on deprecated dh-systemd which is going away)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 21:10:09 +
with message-id 
and subject line Bug#958592: fixed in open-isns 0.100-1
has caused the Debian Bug report #958592,
regarding open-isns: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.

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

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


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

Hi,

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

For bullseye we intend to drop this empty transitional package.

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

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

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: open-isns
Source-Version: 0.100-1
Done: Ritesh Raj Sarraf 

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

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

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated open-isns package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Nov 2020 20:00:00 +0530
Source: open-isns
Binary: libisns-dev libisns-udeb libisns0 libisns0-dbgsym open-isns-discoveryd 
open-isns-discoveryd-dbgsym open-isns-server open-isns-server-dbgsym 
open-isns-utils open-isns-utils-dbgsym
Architecture: source amd64
Version: 0.100-1
Distribution: unstable
Urgency: medium
Maintainer: Debian iSCSI Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 libisns-dev - Internet Storage Name Service - development files
 libisns-udeb - Internet Storage Name Service - shared libraries (udeb)
 libisns0   - Internet Storage Name Service - shared libraries
 open-isns-discoveryd - Internet Storage Name Service - iSNS discovery daemon
 open-isns-server - Internet Storage Name Service - iSNS server
 open-isns-utils - Internet Storage Name Service - client utilities
Closes: 958592
Changes:
 open-isns (0.100-1) unstable; urgency=medium
 .
   * Drop build dependency on dh-systemd (Closes: #958592)
   * New upstream version 0.100
   * Add patch to fix build failure. Patch picked from upstream
   * Overhaul the packaging with OpenSSL
Checksums-Sha1:
 7bd3381e010d8aefb1fda44c6c8a448c38a2b35d 2336 open-isns_0.100-1.dsc
 0c625a22714c2ba4bdd58db5ec05ef93fb3c3639 300611 open-isns_0.100.orig.tar.gz
 5b65a46f1d770017993925e704b81f852da89926 14908 open-isns_0.100-1.debian.tar.xz
 903623d23413715c39ef3ffebd345ed0a4b86955 116472 libisns-dev_0.100-1_amd64.deb
 5ee79c33b30116a7223553d66eeb8640306bb274 86732 libisns-udeb_0.100-1_amd64.udeb
 cbd80e344328e8be6e8c96771130c197ab7a2d7d 330468 
libisns0-dbgsym_0.100-1_amd64.deb
 174b1fedf26223abf5b0dccdc248e36ccafe43a3 92160 libisns0_0.100-1_amd64.deb
 938dbb7c54ee66b98fbcd53097fc6bdd54b6edfa 36132 
open-isns-discoveryd-dbgsym_0.100-1_amd64.deb
 2ab69501ce016e81c012833c84d564f59321147b 29792 
open-isns-discoveryd_0.100-1_amd64.deb
 faf3f05bc7b26e01cfae9d832e3d27ccbdd8455c 11816 
open-isns-server-dbgsym_0.100-1_amd64.deb
 f2d29634804b754a977006feaa06ec79b5a225bb 20720 
open-isns-server_0.100-1_amd64.deb
 054f63966658686463d5a5fc09d78e3550bca705 26168 
open-isns-utils-dbgsym_0.100-1_amd64.deb
 c2064431c32a150b0a3dcc819e8817bd583c7526 33400 
open-isns-utils_0.100-1_amd64.deb
 e0f966af431dcb845b61b6def3b375b4fe3353d2 8501 open-isns_0.100-1_amd64.buildinfo
Checksums-Sha256:
 a1fc9a90f4ac423fe36384c36db2dfce66830c23719ef6afe471140694c24ce1 2336 
open-isns_0.100-1.dsc
 b011edbb0f31690aaca902a8ecf4e1f17b01d6c9e9afc51909d26b0993b4328f 300611 
open-isns_0.100.orig.tar.gz
 e1a0d557d1fa2d888ca744e0c503b1ffd6bd6b341be5dfc1a8823005cd88c768 14908 
open-isns_0.100-1.debian.tar.xz

Bug#975415: git-revise: autopkgtest failure on armhf & ppc64el showing the package downloads code from internet

[Paul Gevers]

Source: git-revise
Version: 0.6.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package git-revise, great.
However, it fails on armhf and ppc64el. Currently this failure is
blocking the migration to testing [1]. Can you please investigate the
situation and fix it? (I have manually retriggered the failing runs as
in case they are flaky; new autopkgtests are not automatically retried).

I copied some of the output at the bottom of this report. I noticed that
the test uses pip to download packages from the internet. The
ftp-masters have ruled that this is forbidden:
https://ftp-master.debian.org/REJECT-FAQ.html [Non-Main II].

Paul

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

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

ERROR: invocation failed (exit code 1), logfile:
/tmp/autopkgtest-lxc.f5o8xggd/downtmp/build.GgD/src/.tox/format/log/format-1.log
== log start
===
Collecting black
  Downloading black-20.8b1.tar.gz (1.1 MB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Collecting click>=7.1.2
  Downloading click-7.1.2-py2.py3-none-any.whl (82 kB)
Collecting regex>=2020.1.8
  Downloading regex-2020.10.28.tar.gz (694 kB)
Collecting typed-ast>=1.4.0
  Using cached typed_ast-1.4.1.tar.gz (208 kB)
Collecting mypy-extensions>=0.4.3
  Using cached mypy_extensions-0.4.3-py2.py3-none-any.whl (4.5 kB)
Collecting toml>=0.10.1
  Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting pathspec<1,>=0.6
  Downloading pathspec-0.8.0-py2.py3-none-any.whl (28 kB)
Collecting appdirs
  Downloading appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting typing-extensions>=3.7.4
  Using cached typing_extensions-3.7.4.3-py3-none-any.whl (22 kB)
Building wheels for collected packages: black, regex, typed-ast
  Building wheel for black (PEP 517): started
  Building wheel for black (PEP 517): finished with status 'done'
  Created wheel for black: filename=black-20.8b1-py3-none-any.whl
size=124186
sha256=9f3176da50d383ad44ceec1128cd60d00cd2b4ee5acd3b67a5bbdbf44f78682a
  Stored in directory:
/home/debci/.cache/pip/wheels/95/a4/59/10cd5378d52f92cdb45025f040e4686e10ae5217961c25fd66
  Building wheel for regex (setup.py): started
  Building wheel for regex (setup.py): finished with status 'error'
  ERROR: Command errored out with exit status 1:





signature.asc
Description: OpenPGP digital signature

Processed: elementpath breaks python-xmlschema autopkgtest: lots of errors

[Debian Bug Tracking System]

Processing control commands:

> found -1 elementpath/2.0.4-1
Bug #975412 [src:elementpath, src:python-xmlschema] elementpath breaks 
python-xmlschema autopkgtest: lots of errors
Marked as found in versions elementpath/2.0.4-1.
> found -1 python-xmlschema/1.2.2-2
Bug #975412 [src:elementpath, src:python-xmlschema] elementpath breaks 
python-xmlschema autopkgtest: lots of errors
Marked as found in versions python-xmlschema/1.2.2-2.

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

Bug#975412: elementpath breaks python-xmlschema autopkgtest: lots of errors

[Paul Gevers]

Source: elementpath, python-xmlschema
Control: found -1 elementpath/2.0.4-1
Control: found -1 python-xmlschema/1.2.2-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
elementpathfrom testing2.0.4-1
python-xmlschema   from testing1.2.2-2
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xmlschema/8327442/log.gz


==
ERROR: test_xml_document_validation
(xmlschema.testing.builders.TestValidator004)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/testing/builders.py",
line 537, in test_xml_document_validation
self.check_iter_errors()
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/testing/builders.py",
line 503, in check_iter_errors
lazy_errors = list(xmlschema.iter_errors(xml_file,
schema=self.schema, lazy=True))
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1405, in iter_errors
yield from self._validate_references(validation='lax', **kwargs)
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1420, in _validate_references
for error in counter.iter_errors(identities):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/identities.py",
line 422, in iter_errors
refer_values = identities[self.identity.refer].counter
KeyError: XsdKey(name='author_dn')

==
ERROR: test_default_namespace (tests.validation.test_decoding.TestDecoding)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/tests/validation/test_decoding.py",
line 820, in test_default_namespace
self.assertEqual(xs.to_dict("""http://example.com/foo";>bar""",
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1555, in decode
for result in self.iter_decode(source, path, schema_path,
validation, *args, **kwargs):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1542, in iter_decode
yield schema.validation_error(validation, reason, elem, source,
namespaces)
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/xsdbase.py",
line 906, in validation_error
raise error
xmlschema.validators.exceptions.XMLSchemaValidationError: failed
validating http://example.com/foo}foo' at 0x7f6c7ca66d60>
with XMLSchema10(namespace='http://example.com/foo'):

Reason: http://example.com/foo}foo' at 0x7f6c7ca66d60> is not
an element of the schema

Instance:

  http://example.com/foo";>bar

Path: /foo


==
ERROR: test_json_path_decoding (tests.validation.test_decoding.TestDecoding)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/tests/validation/test_decoding.py",
line 501, in test_json_path_decoding
json_data = xmlschema.to_json(xml_file, schema=schema, path='*')
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/documents.py",
line 234, in to_json
obj = schema.decode(source, path=path, **kwargs)
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1555, in decode
for result in self.iter_decode(source, path, schema_path,
validation, *args, **kwargs):
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/schema.py",
line 1542, in iter_decode
yield schema.validation_error(validation, reason, elem, source,
namespaces)
  File
"/tmp/autopkgtest-lxc.5wa53j63/downtmp/build.JBu/src/xmlschema/validators/xsdbase.py",
line 906, in validatio

Bug#975411: meson: autopkgtest arm64 regression: #error gas syntax assembly for this test needs to be written

[Paul Gevers]

Source: meson
Version: 0.56.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
meson  from testing0.56.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/m/meson/8336251/log.gz

The Meson build system
Version: 0.56.0
Source dir: /tmp/autopkgtest-lxc.5bf91z4q/downtmp/build.pfy/src/test
cases/common/122 llvm ir and assembly
Build dir: /tmp/autopkgtest-lxc.5bf91z4q/downtmp/build.pfy/src/b 7396edba24
Build type: native build
Project name: llvm-ir
Project version: undefined
C compiler for the host machine: cc (gcc 10.2.0 "cc (Debian 10.2.0-16)
10.2.0")
C linker for the host machine: cc ld.bfd 2.35.1
C++ compiler for the host machine: c++ (gcc 10.2.0 "c++ (Debian
10.2.0-16) 10.2.0")
C++ linker for the host machine: c++ ld.bfd 2.35.1
Host machine cpu family: aarch64
Host machine cpu: aarch64
Message: underscore is NOT prefixed
Message: underscore is NOT prefixed
Build targets in project: 2

Found ninja-1.10.1 at /usr/bin/ninja
[1/6] Compiling C object square_asm_c.p/square-aarch64.S.o
FAILED: square_asm_c.p/square-aarch64.S.o
cc -Isquare_asm_c.p -I. '-I../test cases/common/122 llvm ir and
assembly' -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall
-Winvalid-pch -g -MD -MQ square_asm_c.p/square-aarch64.S.o -MF
square_asm_c.p/square-aarch64.S.o.d -o square_asm_c.p/square-aarch64.S.o
-c '../test cases/common/122 llvm ir and assembly/square-aarch64.S'
../test cases/common/122 llvm ir and assembly/square-aarch64.S:18:2:
error: #error gas syntax assembly for this test needs to be written
   18 | #error gas syntax assembly for this test needs to be written
  |  ^
[2/6] Compiling C object square_asm_cpp.p/square-aarch64.S.o
FAILED: square_asm_cpp.p/square-aarch64.S.o
cc -Isquare_asm_cpp.p -I. '-I../test cases/common/122 llvm ir and
assembly' -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall
-Winvalid-pch -g -MD -MQ square_asm_cpp.p/square-aarch64.S.o -MF
square_asm_cpp.p/square-aarch64.S.o.d -o
square_asm_cpp.p/square-aarch64.S.o -c '../test cases/common/122 llvm ir
and assembly/square-aarch64.S'
../test cases/common/122 llvm ir and assembly/square-aarch64.S:18:2:
error: #error gas syntax assembly for this test needs to be written
   18 | #error gas syntax assembly for this test needs to be written
  |  ^
[3/6] Compiling C object square_asm_c.p/main.c.o
[4/6] Compiling C++ object square_asm_cpp.p/main.cpp.o
ninja: build stopped: subcommand failed.


ninja explain: deps for 'square_asm_c.p/square-aarch64.S.o' are missing
ninja explain: square_asm_c.p/square-aarch64.S.o is dirty
ninja explain: deps for 'square_asm_c.p/main.c.o' are missing
ninja explain: square_asm_c.p/main.c.o is dirty
ninja explain: square_asm_c is dirty
ninja explain: deps for 'square_asm_cpp.p/square-aarch64.S.o' are missing
ninja explain: square_asm_cpp.p/square-aarch64.S.o is dirty
ninja explain: deps for 'square_asm_cpp.p/main.cpp.o' are missing
ninja explain: square_asm_cpp.p/main.cpp.o is dirty
ninja explain: square_asm_cpp is dirty


autopkgtest [23:31:58]: test exhaustive: ---]



signature.asc
Description: OpenPGP digital signature

Bug#974024: inn2 FTBFS on IPV6-only buildds

[Russ Allbery]

Russ Allbery  writes:
> Adrian Bunk  writes:

>> ...
>> lib/network/server..MISSED 34-42 (killed by signal 14)
>> ...
>> Failed Set Fail/Total (%) Skip Stat  Failing Tests
>> -- --    
>> lib/network/server9/3426%8   --  34-42

>> Failed 9/3631 tests, 99.75% okay, 55 tests skipped.
>> Files=60,  Tests=3631,  12.90 seconds (2.43 usr + 1.92 sys = 4.35 CPU)
>> make[2]: *** [Makefile:38: test] Error 1

> I'm working on a fix.  It's unfortunately rather complicated because the
> assumption that binding on any address will provide two sockets ran fairly
> deep.

> I think the problem only affects the test suite.

This is fixed by upstream commits r10388 (trunk) and r10396 (stable).

-- 
Russ Allbery (r...@debian.org)  

Processed: src:sieve-connect: fails to migrate to testing for too long: maintainer built arch:all binary

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.90-1
Bug #975410 [src:sieve-connect] src:sieve-connect: fails to migrate to testing 
for too long: maintainer built arch:all binary
Marked as fixed in versions sieve-connect/0.90-1.
Bug #975410 [src:sieve-connect] src:sieve-connect: fails to migrate to testing 
for too long: maintainer built arch:all binary
Marked Bug as done

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

Bug#975410: src:sieve-connect: fails to migrate to testing for too long: maintainer built arch:all binary

[Paul Gevers]

Source: sieve-connect
Version: 0.88-1.1
Severity: serious
Control: close -1 0.90-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#975409: pwman FTBFS: ModuleNotFoundError: No module named 'cryptography'

[Adrian Bunk]

Source: pwman3
Version: 0.12.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pwman3&arch=all&ver=0.12.1-1&stamp=1605944549&raw=0

...
dh_auto_clean
I: pybuild base:232: python3.8 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 390, in 
import pwman
  File "/<>/pwman/__init__.py", line 33, in 
from pwman.data.factory import check_db_version
  File "/<>/pwman/data/__init__.py", line 1, in 
from . import factory
  File "/<>/pwman/data/factory.py", line 25, in 
from pwman.data.database import DatabaseException
  File "/<>/pwman/data/database.py", line 22, in 
from pwman.util.crypto_engine import CryptoEngine
  File "/<>/pwman/util/crypto_engine.py", line 29, in 
from cryptography.fernet import Fernet
ModuleNotFoundError: No module named 'cryptography'
E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: 
python3.8 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.8 3.9" returned 
exit code 13
make[1]: *** [debian/rules:15: override_dh_auto_clean] Error 25

Processed: reassign 969072 to groff

[Debian Bug Tracking System]

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

> reassign 969072 groff
Bug #969072 [src:dahdi-tools] dahdi-tools FTBFS on armel/mipsel/hppa/powerpc: 
pre-grohtml: fatal error: cannot create temporary file: File exists
Bug reassigned from package 'src:dahdi-tools' to 'groff'.
No longer marked as found in versions dahdi-tools/1:3.1.0-1.
Ignoring request to alter fixed versions of bug #969072 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#957888: marked as done (tuxmath: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 17:49:31 +
with message-id 
and subject line Bug#957859: fixed in t4kcommon 0.1.1-10
has caused the Debian Bug report #957859,
regarding tuxmath: 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.)


-- 
957859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tuxmath
Version: 2.0.3-5
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/tuxmath_2.0.3-5_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

[...]
x86_64-linux-gnu-gcc -Wall -g -DDATA_PREFIX=\"/usr/share/tuxmath\" -DDEBUG 
-DSOUND -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/SDL  -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -pthread 
-I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/libxml2 
-D_GNU_SOURCE=1 -D_REENTRANT -pthread -I/usr/include/SDL 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/librsvg-2.0 
-I/usr/include/gdk-pixbuf-2.0 -I/us
 r/include/libmount -I/usr/include/blkid -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libxml2  -Wl,-z,relro -Wl,--as-needed -o 
generate_lesson generate_lesson.o mathcards.o options.o fileops.o lessons.o  
-lm  -lSDL -lSDL_image -lSDL -lSDL_mixer -lSDL -lrsvg-2 -lm -lgio-2.0 
-lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo -lcairo -lSDL_net -lSDL 
-lxml2 -lt4k_common -lSDL_mixer -lSDL_net -lSDL_image -lSDL -lSDL_Pango 
-lpango-1.0 -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 
-lcairo -lxml2
/usr/bin/ld: In function ‘strncpy’,
inlined from ‘config_highscores’ at tuxmathadmin.c:562:3:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
mathcards.o:/usr/include/t4k_common.h:242: multiple definition of 
`wrapped_lines'; generate_lesson.o:/usr/include/t4k_common.h:242: first defined 
here
/usr/bin/ld: options.o:/usr/include/t4k_common.h:242: multiple definition of 
`wrapped_lines'; generate_lesson.o:/usr/include/t4k_common.h:242: first defined 
here
/usr/bin/ld: fileops.o:/usr/include/t4k_common.h:242: multiple definition of 
`wrapped_lines'; generate_lesson.o:/usr/include/t4k_common.h:242: first defined 
here
/usr/bin/ld: lessons.o:/usr/include/t4k_common.h:242: multiple definition of 
`wrapped_lines'; generate_lesson.o:/usr/include/t4k_common.h:242: first defined 
here
In function ‘strncpy’,
inlined from ‘clear_highscores’ at tuxmathadmin.c:605:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ spe

Bug#957859: marked as done (t4kcommon: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 17:49:31 +
with message-id 
and subject line Bug#957859: fixed in t4kcommon 0.1.1-10
has caused the Debian Bug report #957859,
regarding t4kcommon: 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.)


-- 
957859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:t4kcommon
Version: 0.1.1-7
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/t4kcommon_0.1.1-7_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

[...]
t4k_loaders.c:735:26: warning: ‘/images/’ directive writing 8 bytes into a 
region of size between 1 and 1024 [-Wformat-overflow=]
  735 |   sprintf(pngfn, "%s/" IMAGE_DIR "/%s%d-%d-%d.png", cachepath, 
name, i, width, height);
  |  ^
t4k_loaders.c:735:29: note: format string is defined here
  735 |   sprintf(pngfn, "%s/" IMAGE_DIR "/%s%d-%d-%d.png", cachepath, 
name, i, width, height);
  | ^~~
t4k_loaders.c:735:26: note: directive argument in the range [0, 2147483647]
  735 |   sprintf(pngfn, "%s/" IMAGE_DIR "/%s%d-%d-%d.png", cachepath, 
name, i, width, height);
  |  ^
In file included from /usr/include/stdio.h:867,
 from /usr/include/SDL/SDL_stdinc.h:37,
 from /usr/include/SDL/SDL_main.h:26,
 from /usr/include/SDL/SDL.h:30,
 from t4k_common.h:62,
 from t4k_globals.h:37,
 from t4k_loaders.c:28:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output 18 or more bytes (assuming 1050) into a 
destination of size 1024
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g 
-DCOMMON_DATA_PREFIX=\"/usr/share/t4k_common\" -DDEBUG -DUSE_T4K_PREFIX=1  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL  
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/SDL -pthread -I/usr/include/librsvg-2.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/inc
 lude/freetype2 -I/usr/include/libpng16 -I/usr/include/libpng16 
-I/usr/include/libxml2 -c -o t4k_sdl.lo t4k_sdl.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -g -DCOMMON_DATA_PREFIX=\"/usr/share/t4k_common\" -DDEBUG 
-DUSE_T4K_PREFIX=1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE=1 
-D_REENTRANT -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL 
-

Bug#969072: dahdi-tools FTBFS on armel/mipsel/hppa/powerpc: pre-grohtml: fatal error: cannot create temporary file: File exists

[Tzafrir Cohen]

  
  
Hi,



On abel in a armel chroot the issue is
  reproduced by running:


  man -Thtml 



even on an empty man page.



Right now you can try:


$ schroot -r -c session:tzafrir-dahdi-tools -- man -Thtml
  ~tzafrir/test.8 >/dev/null
  pre-grohtml: fatal error: cannot create temporary file: File
  exists
  man: command exited with status 1: /usr/lib/man-db/zsoelim |
  /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE |
  preconv -e UTF-8 | tbl | groff -mandoc -Thtml


Not reproduced in a armhf chroot there or in a qemu armel chroot
  on my laptop.



-- Tzafrir

  

Bug#975246: marked as done (The autopkgtests are failing with python3.9 enabled)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 16:48:57 +
with message-id 
and subject line Bug#975246: fixed in pyferret 7.6.3-3
has caused the Debian Bug report #975246,
regarding The autopkgtests are failing with python3.9 enabled
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.)


-- 
975246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pyferret
Version: 7.6.3-2
Severity: serious
Tags: patch
User: debian-pyt...@lists.debian.org
Usertags: origin-ubuntu ubuntu-patch python3.9

The issue is currently visible on Ubuntu but the problem exists in
Debian, the autopkgtest are failing if a new version of python is
supported but not yet default

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/p/pyferret/20201113_141906_8bc78@/log.gz

"
test command1: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd
"$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import pyferret"
; done
Testing with python3.9:
bash: python3.9: command not found
"

That's because
- the tests Depends on python3-ferret
- python3-ferret Depends on python3 (so default python version)
- the tests try to import on all supported versions, and not only the
default one

Either the test should test only the current version or Depends on
python3-all (which the attached patch is doing)


Cheers,
Sebastien Bacher

diff -Nru pyferret-7.6.3/debian/changelog pyferret-7.6.3/debian/changelog
--- pyferret-7.6.3/debian/changelog	2020-10-17 09:52:39.0 +0200
+++ pyferret-7.6.3/debian/changelog	2020-11-19 15:20:31.0 +0100
@@ -1,3 +1,11 @@
+pyferret (7.6.3-2.1) unstable; urgency=medium
+
+  * debian/tests/control:
+- Build-Depends on python3-all since the tests try to import for all
+  supported python versions and not only the current one
+
+ -- Sebastien Bacher   Thu, 19 Nov 2020 15:20:31 +0100
+
 pyferret (7.6.3-2) unstable; urgency=medium
 
   * Update d/not-installed to work with python3.9. Closes: #972430, #972347
diff -Nru pyferret-7.6.3/debian/tests/control pyferret-7.6.3/debian/tests/control
--- pyferret-7.6.3/debian/tests/control	2020-10-17 09:52:39.0 +0200
+++ pyferret-7.6.3/debian/tests/control	2020-11-19 15:00:42.0 +0100
@@ -4,4 +4,4 @@
  ; echo "Testing with $py:"
  ; $py -c "import pyferret"
  ; done
-Depends: python3-ferret
+Depends: python3-ferret, python3-all
--- End Message ---
--- Begin Message ---
Source: pyferret
Source-Version: 7.6.3-3
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pyferret 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: Sat, 21 Nov 2020 15:26:15 +
Source: pyferret
Architecture: source
Version: 7.6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 975246
Changes:
 pyferret (7.6.3-3) unstable; urgency=medium
 .
   [ Sebastien Bacher ]
   * debian/tests/control:
 - Build-Depends on python3-all since the tests try to import for all
   supported python versions and not only the current one
   Closes: #975246
 .
   [ Alastair McKinstry ]
   * standards-Version: 4.5.1
Checksums-Sha1:
 a0bcc55737bc172e6dc13e3482127e681aa1a53e 2255 pyferret_7.6.3-3.dsc
 987b3f2070544f8bc50643f9a343c5bedcbef045 40480 pyferret_7.6.3-3.debian.tar.xz
Checksums-Sha256:
 e56869fbbcfad2c132a7ce9a3399ed2837c128861af25ddbef2d991babdaf2a4 2255 
pyferret_7.6.3-3.dsc
 446c8c961599464ce642a6691a0b093868fd07d2ea09c978a10445842b251ef7 40480 
pyferret_7.6.3-3.debian.tar.xz
Files:
 a5140362c46207e8d4b09f498fce0f55 2255 science optional pyferret_7.6.3-3.dsc
 e7dd0bde0327801c6f65fbd953f37cbe 40480 science optional 
pyferret_7.6.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl+5P9wACgkQy+a7Tl2a
06Xi4RAAkDdlAKJ+vFC7PnkEzscVbX4EJ6fmyUd4UlmjtwkFMw0faBjGQl

Bug#968102: tbsync: Incompatible with Thunderbird 78

[Jonas Smedegaard]

Another no-op post to bump timestapm of this bugreport: Helps nudge the 
kick-packages-with-broken-rdeps-from-testing machinery to look further 
back at thunderbird for the real cause.

 - 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#971770: webext-dav4tbsync: Incompatible with Thunderbird 78

[Jonas Smedegaard]

No-op post to bump timestapm of this bugreport: Helps nudge the 
kick-packages-with-broken-rdeps-from-testing machinery to look further 
back at thunderbird for the real cause.


 - 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

Processed: severity of 973703 is important

[Debian Bug Tracking System]

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

> severity 973703 important
Bug #973703 {Done: Pino Toscano } [cantor-backend-scilab] 
cantor-backend-scilab: dependency no longer available on i386 and armhf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#933948: Config value incorrectly parsed in init.d script

[Norbert Harrer]

I don't think it's systemd's fault. There is a sub-optimal sed regex in
most courier init.d scripts. Here is a scenario with courier-mta-ssl as
an example (though, it also happens to other parts like courier-imap-ssl):

Usually, the config file /etc/courier/esmtpd-ssl contains:

ESMTPDSSLSTART=YES

And everything works fine. However, when you save the config through the
admin webpage, it changes it to:

ESMTPDSSLSTART="YES"

This should be fine as well, since the shell command executed by the
admin page parses it just the same:

> /usr/sbin/esmtpd-ssl stop ; . /etc/courier/esmtpd-ssl ; test 
"$ESMTPDSSLSTART" != YES || /usr/sbin/esmtpd-ssl start


But in /etc/init.d/courier-mta-ssl it is parsed with sed:

DO_START=$(sed -ne 's/^ESMTPDSSLSTART=\([^[:space:]]*\)/\1/p' 
/etc/courier/esmtpd-ssl | tr "A-Z" "a-z")


Which leads to DO_START containing the value "yes" including the quotes.
Further down the line in /usr/lib/courier/init-d-script-courier this
causes the script to exit quietly, if DO_START is anything other then yes.
After replacing the line with:

DO_START=$(sed -ne 's/^ESMTPDSSLSTART=\W*\(\w\+\)\W*/\1/p' 
/etc/courier/esmtpd-ssl | tr "A-Z" "a-z")


"systemctl restart courier-mta-ssl" works again.


Note 1: The ugly thing is, that when you make the changes through the web
interface, everything continues to work fine, because it parses the
config files correctly during restart. Then some time later, when you
restart the machine or restart the service with systemctl, it doesn't
come up again with no hints at all in the log files. I also think it
happens when courier crashes, and systemd tries to restart the service.

Note 2: Another thing is curious: Not all courier services use the init.d
scripts, some have their own systemd config in /lib/systemd/system/
which bypass the init.d script:

> systemctl status `systemctl -t service | grep courier | awk '{ print 
$1; }'` | grep Loaded


   Loaded: loaded (/lib/systemd/system/courier-authdaemon.service; 
enabled; vendor preset: enabled)

   Loaded: loaded (/etc/init.d/courier-imap-ssl; generated)
   Loaded: loaded (/lib/systemd/system/courier-imap.service; enabled; 
vendor preset: enabled)

   Loaded: loaded (/etc/init.d/courier-msa; generated)
   Loaded: loaded (/etc/init.d/courier-mta-ssl; generated)
   Loaded: loaded (/etc/init.d/courier-pop-ssl; generated)
   Loaded: loaded (/lib/systemd/system/courier-pop.service; enabled; 
vendor preset: enabled)

   Loaded: loaded (/etc/init.d/courier; generated)
   Loaded: loaded (/etc/init.d/courierfilter; generated)

So only the services

  courier-imap-ssl
  courier-msa
  courier-mta-ssl
  courier-pop-ssl

are prone to this bug, which gives the whole thing an even more sporadic
character.

Regards,
Norbert

Bug#975162: marked as done (xygrib: FTBFS: SkewT.h:38:25: error: invalid use of incomplete type ‘class QPainterPath’)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 13:52:03 +
with message-id 
and subject line Bug#975162: fixed in xygrib 1.2.6-2
has caused the Debian Bug report #975162,
regarding xygrib: FTBFS: SkewT.h:38:25: error: invalid use of incomplete type 
‘class QPainterPath’
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.)


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

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DQT_CORE_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB 
> -DQT_WIDGETS_LIB -DQT_XML_LIB -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src -I/usr/include/openjpeg-2.3 
> -I/<>/obj-x86_64-linux-gnu/CMakeFiles/include 
> -I/<>/src/util -I/<>/src/map 
> -I/<>/obj-x86_64-linux-gnu/src/map/map_autogen/include 
> -I/<>/src/GUI -I/<>/obj-x86_64-linux-gnu/src/GUI 
> -I/<>/src/g2clib-1.6.0 -I/<>/src/map/.. 
> -I/<>/src/map/../util -I/<>/src/map/../GUI -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -DACCEPT_USE_OF_DEPRECATED_PROJ_API_H -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -fPIC -fPIC -std=gnu++11 -o 
> CMakeFiles/XyGrib.dir/Metar.cpp.o -c /<>/src/Metar.cpp
> /<>/src/MapDrawer.cpp: In member function ‘void 
> MapDrawer::draw_Cartouche_Gridded(QPainter&, const Projection*, 
> GriddedPlotter*)’:
> /<>/src/MapDrawer.cpp:734:25: warning: ‘int 
> QFontMetrics::width(const QString&, int) const’ is deprecated: Use 
> QFontMetrics::horizontalAdvance [-Wdeprecated-declarations]
>   734 |   w1 = fmbig.width(tval2)+5;
>   | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:59,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/QPainter:1,
>  from /<>/src/MapDrawer.cpp:25:
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qfontmetrics.h:106:9: note: declared 
> here
>   106 | int width(const QString &, int len = -1) const;
>   | ^
> /<>/src/MapDrawer.cpp:738:47: warning: ‘int 
> QFontMetrics::width(const QString&, int) const’ is deprecated: Use 
> QFontMetrics::horizontalAdvance [-Wdeprecated-declarations]
>   738 |  int t = fmsmall.width (datalist.at(i))+5;
>   |   ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:59,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/QPainter:1,
>  from /<>/src/MapDrawer.cpp:25:
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qfontmetrics.h:106:9: note: declared 
> here
>   106 | int width(const QString &, int len = -1) const;
>   | ^
> /<>/src/MapDrawer.cpp:778:41: warning: ‘int 
> QFontMetrics::width(const QString&, int) const’ is deprecated: Use 
> QFontMetrics::horizontalAdvance [-Wdeprecated-declarations]
>   778 | int t = fmdate.width (datalist.at(i))+5;
>   | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:59,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/QPainter:1,
>  from /<>/src/MapDrawer.cpp:25:
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qfontmetrics.h:106:9: note: declared 
> here
>   106 | int width(const QString &, int len = -1) const;
>   | ^
> /<>/src/MapDrawer.cpp:800:24: warning: ‘int 
> QFontMetrics::width(const QString&, int) const’ is deprecated: Use 
> QFontMetrics::horizontalAdvance [-Wdeprecated-declarations]
>   800 |   w = fmsign.width(sign)+5;
>   |^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:59,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/QPainter:1,
>  from /<>/src/MapDrawer.cpp:25:
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qfontmetrics.h:106:9: note: declared 
> here
>   106 | int

Bug#975109: marked as done (antimony: FTBFS in testing and unstable)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 13:33:25 +
with message-id 
and subject line Bug#975109: fixed in antimony 0.9.3-2
has caused the Debian Bug report #975109,
regarding antimony: FTBFS in testing and unstable
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.)


-- 
975109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: antimony
Version: 0.9.3-1.2
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

As per reproducible builds [1], antimony recently started failing to
build in testing and unstable.

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

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/antimony.html


[ 96%] Building CXX object
app/CMakeFiles/antimony.dir/viewport/control/point.cpp.o
cd /build/1st/antimony-0.9.3/obj-x86_64-linux-gnu/app && /usr/bin/c++
-DBOOST_ALL_NO_LIB -DBOOST_PYTHON_DYN_LINK -DQT_CONCURRENT_LIB
-DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG
-DQT_OPENGL_LIB -DQT_WIDGETS_LIB
-I/build/1st/antimony-0.9.3/obj-x86_64-linux-gnu/app
-I/build/1st/antimony-0.9.3/app
-I/build/1st/antimony-0.9.3/obj-x86_64-linux-gnu/app/antimony_autogen/include
-I/build/1st/antimony-0.9.3/lib/graph/inc
-I/build/1st/antimony-0.9.3/lib/fab/inc -isystem
/usr/include/python3.8 -isystem /usr/include/x86_64-linux-gnu/qt5
-isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -Wall -Wextra -g
-Werror=switch -O3 -DRELEASE   -D'GITREV="+ "' -D'GITTAG=""'
-D'GITBRANCH=""' -fPIC -std=gnu++11 -o
CMakeFiles/antimony.dir/viewport/control/point.cpp.o -c
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp:37:48: error:
return type 'class QPainterPath' is incomplete
   37 | QPainterPath PointControl::shape(QMatrix4x4 m) const
  |^
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp: In member
function 'virtual void PointControl::shape(QMatrix4x4) const':
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp:39:18: error:
aggregate 'QPainterPath path' has incomplete type and cannot be
defined
   39 | QPainterPath path;
  |  ^~~~
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp: In member
function 'virtual void PointControl::paint(QMatrix4x4, bool,
QPainter*)':
/build/1st/antimony-0.9.3/app/viewport/control/point.cpp:49:10: error:
'void s' has incomplete type
   49 | auto s = shape(m);
  |  ^
--- End Message ---
--- Begin Message ---
Source: antimony
Source-Version: 0.9.3-2
Done: Tiago Bortoletto Vaz 

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

Debian distribution maintenance software
pp.
Tiago Bortoletto Vaz  (supplier of updated antimony package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Nov 2020 09:45:45 -0500
Source: antimony
Binary: antimony antimony-dbgsym
Architecture: source amd64
Version: 0.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Tiago Bortoletto Vaz 
Changed-By: Tiago Bortoletto Vaz 
Description:
 antimony   - Computer-aided design CAD tool
Closes: 975109
Changes:
 antimony (0.9.3-2) unstable; urgency=medium
 .
   * Add patch to import QPainterPath. Thanks to Tobias Frost. Closes: #975109
Checksums-Sha1:
 72ed40f026e97f50770d9abd4afa8abe0bfa5e08 1975 antimony_0.9.3-2.dsc
 7de930dbd7232c027907fed1e2b3f80a00b32465 9992 antimony_0.9.3-2.debian.tar.xz
 2ef137acd40d8bb8d752577dee9ff96ba164e85d 19395632 
antimony-dbgsym_0.9.3-2_amd64.deb
 06f696db1ce8fee9cbe382148eebdd6174e58689 16859 antimony_0.9.3-2_amd64.buildinfo
 a9318d170809145f0832e4793f782bc1e4fcf387 532492 antimony_0.9.3-2_amd64.deb
Chec

Bug#974915: marked as done (genny: missing Breaks+Replaces: golang-github-cheekybits-genny-dev (<< 1.0.0-4))

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 13:03:55 +
with message-id 
and subject line Bug#974915: fixed in golang-github-cheekybits-genny 1.0.0-7
has caused the Debian Bug report #974915,
regarding genny: missing Breaks+Replaces: golang-github-cheekybits-genny-dev 
(<< 1.0.0-4)
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.)


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

Hi,

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

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

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

  Preparing to unpack .../genny_1.0.0-5_amd64.deb ...
  Unpacking genny (1.0.0-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/genny_1.0.0-5_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/genny', which is also in package 
golang-github-cheekybits-genny-dev 1.0.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/genny_1.0.0-5_amd64.deb


cheers,

Andreas


golang-github-cheekybits-genny-dev=1.0.0-3_genny=1.0.0-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-github-cheekybits-genny
Source-Version: 1.0.0-7
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated 
golang-github-cheekybits-genny 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, 21 Nov 2020 21:20:16 +0900
Source: golang-github-cheekybits-genny
Architecture: source
Version: 1.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Roger Shimizu 
Closes: 974915
Changes:
 golang-github-cheekybits-genny (1.0.0-7) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 - Move Breaks+Replaces: golang-github-cheekybits-genny-dev (<< 1.0.0-4)
   to package genny. Thanks to Andreas Beckmann for the advice.
   (Closes: #974915)
Checksums-Sha1:
 1d3c2cf506fb005ffc7f323b9861bb7d3ba1f449 2401 
golang-github-cheekybits-genny_1.0.0-7.dsc
 634c2c97b08e92d14e468fa4af849ee66cc49836 3284 
golang-github-cheekybits-genny_1.0.0-7.debian.tar.xz
 e14ef64269ced9262f2f796b0d98b49a1a258363 5700 
golang-github-cheekybits-genny_1.0.0-7_source.buildinfo
Checksums-Sha256:
 967bc6cd773066e8639fb651fa509111b6cbfce84c2f22aa2c7cf8b32d77158c 2401 
golang-github-cheekybits-genny_1.0.0-7.dsc
 cc6a87636d32ef039c4913d18600d33db23fb7a9bab45c6c402e1b15cad6c138 3284 
golang-github-cheekybits-genny_1.0.0-7.debian.tar.xz
 9afda5be31d0539a3612302a62489ec732446aac74cdeae08c6d5378d02afecb 5700 
golang-github-cheekybits-genny_1.0.0-7_source.buildinfo
Files:
 ea2f1846254421315d03c1ed3239e913 2401 devel optional 
golang-github-cheekybits-genny_1.0.0-7.dsc
 31bb67f8b1e1d133bf806bb1b259b2e5 3284 devel optional 
golang-github-cheekybits-genny_1.0.0-7.debian.tar.xz
 7e1f54c97273260c4df0eea2480c1d50 5700 devel optional 
golang-github-cheekybits-genny_1.0.0-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl+5BrgQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qJJ3D/0bVUmQRWx3u+Af3iT6m1WWNAYmCPE3lorm
2Nzx3Pcj5ueyf4H5VVJ29Wt24um9DQiPngF6Z/5lwceR2P+VvYqouYgdpJMJrJGq
etPcbnpgAZpBm3NkGDuyv/TaQLkPb98qpXX2RSa2bvCIFIEfgU+LplocYytYVgPD
QupkBX6+Q564XMxbYK0g44pQHN6bljSmjTrpOXAlU8XzuELkrI2uIGhHQtLmnxcU
5fCIroN43AOAmP2DKp2kyIrN1gNO3xIAYmh/cpr+oXCnXS/uMchwtTbCggwfD2yc
TACnl/V0MsMiv0vj2848DcXP+bcnjpty3bhJPSYiSb4GTORc2f7PnIdjdl6t38Tb
P+1ER/fMVwjsYweYDpNDoAeJ2cPNLcPNcDmVKnM/+Wn7r

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

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 13:03:49 +
with message-id 
and subject line Bug#973077: fixed in commonmark-bkrs 0.5.4+ds-5
has caused the Debian Bug report #973077,
regarding commonmark-bkrs: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


-- 
973077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commonmark-bkrs
Version: 0.5.4+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} 
> CommonMark/test/test-CommonMark.py" dh_auto_test
> I: pybuild base:217: python3.9 CommonMark/test/test-CommonMark.py
> Traceback (most recent call last):
>   File "/<>/CommonMark/test/test-CommonMark.py", line 5, in 
> 
> from CommonMark_bkrs import CommonMark
>   File 
> "/<>/.pybuild/cpython3_3.9/build/CommonMark_bkrs/__init__.py", 
> line 3, in 
> from CommonMark_bkrs.CommonMark import HTMLRenderer
>   File 
> "/<>/.pybuild/cpython3_3.9/build/CommonMark_bkrs/CommonMark.py", 
> line 18, in 
> HTMLunescape = html.parser.HTMLParser().unescape
> AttributeError: 'HTMLParser' object has no attribute 'unescape'
> E: pybuild pybuild:352: test: plugin custom failed with: exit code=1: 
> python3.9 CommonMark/test/test-CommonMark.py
> dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned 
> exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/commonmark-bkrs_0.5.4+ds-4_unstable.log

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

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: commonmark-bkrs
Source-Version: 0.5.4+ds-5
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated commonmark-bkrs 
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, 21 Nov 2020 12:44:39 +
Source: commonmark-bkrs
Architecture: source
Version: 0.5.4+ds-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jerome Benoit 
Closes: 973077
Changes:
 commonmark-bkrs (0.5.4+ds-5) unstable; urgency=medium
 .
   [ Jerome Benoit ]
   * d/p/upstream-fix-deprecation-HTMLunescape.patch: patch deprecated
 HTMLParser.unescape for python >=3.9 (Closes: #973077).
   * d/control: Introduce Rules-Requires-Root field and set to no.
   * d/p/debianization.patch: Specify Forwarded field as NA.
   * Set upstream metadata fields: Repository-Browse, Repository.
   * Update d/*.lintian-overrides.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
Checksums-Sha1:
 db176d0bf81d30adc02cbbaa487f076ba755900f 2962 commonmark-bkrs_0.5.4+ds-5.dsc
 59240211292da154bf112d6ba50d5aaed7080c01 6388 
commonmark-bkrs_0.5.4+ds-5.debian.tar.xz
 11edd542dd5a91cf9543f40e2ad1e0e1ddcfd81f 7238 
commonmark-bkrs_0.5.4+ds-5_source.buildinfo
Checksums-Sha256:
 a6dc0ea098b054a3a79b0588e90a84c11b08163080e57c4a9d4777f5a3411618 2962 
commonmark-bkrs_0.5.4+ds-5.dsc
 1234f3e29279b334902efc3c6dcf472508ea7dcd319a7334e8b9ea053a1c1f51 6388 
commonmark-bkrs_0.5.4+ds-5.debian.tar.xz
 613207

Bug#974915: marked as pending in golang-github-cheekybits-genny

[Roger Shimizu]

Control: tag -1 pending

Hello,

Bug #974915 in golang-github-cheekybits-genny 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/go-team/packages/golang-github-cheekybits-genny/-/commit/ad1eb2a559992bc9fc272d3edc7f190906964c3c


Prepare to release 1.0.0-7

* d/control:
  - Move Breaks+Replaces: golang-github-cheekybits-genny-dev (<< 1.0.0-4)
to package genny. Thanks to Andreas Beckmann for the advice.

Closes: #974915


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974915

Processed: Bug#974915 marked as pending in golang-github-cheekybits-genny

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974915 [genny] genny: missing Breaks+Replaces: 
golang-github-cheekybits-genny-dev (<< 1.0.0-4)
Added tag(s) pending.

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

Bug#975376: [pkg-netfilter-team] Bug#975376: Fails to build with Linux 5.9.9 because of change in ip_route_me_harder()

[Jeremy Sowden]

On 2020-11-21, at 11:23:36 +0100, Sven Hartge wrote:
> Package: xtables-addons-dkms
> Version: 3.11-1
> Severity: grave
>
> Hi!
>
> Kernel 5.9.9 changes ip_route_me_harder() with commit
> 46d6c5ae953cc0be38efd0e469284df7c4328cf8 causing a build failure for
> xtables-addons-dkms:
>
> ,
> | In file included from 
> /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
> |  from 
> /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:20:
> | /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:74: 
> note: expected ‘struct sk_buff *’ but argument is of type ‘unsigned int’
> |19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
> sk_buff *skb, unsigned addr_type);
> |   |  
> ^~~
> | /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:125:6: 
> error: too few arguments to function ‘ip_route_me_harder’
> |   125 |  if (ip_route_me_harder(net, nskb, addr_type))
> |   |  ^~
> | In file included from 
> /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
> |  from 
> /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:20:
> | /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:5: 
> note: declared here
> |19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
> sk_buff *skb, unsigned addr_type);
> |   | ^~
> | /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c: In function 
> ‘echo_tg4’:
> | /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:195:39: error: 
> passing argument 2 of ‘ip_route_me_harder’ from incompatible pointer type 
> [-Werror=incompatible-pointer-types]
> |   195 |  if (ip_route_me_harder(par_net(par), newskb, RTN_UNSPEC) != 0)
> |   |   ^~
> |   |   |
> |   |   struct sk_buff *
> | In file included from 
> /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
> |  from 
> /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:16:
> | /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:54: 
> note: expected ‘struct sock *’ but argument is of type ‘struct sk_buff *’
> |19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
> sk_buff *skb, unsigned addr_type);
> |   | ~^~
> | /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:195:6: error: 
> too few arguments to function ‘ip_route_me_harder’
> |   195 |  if (ip_route_me_harder(par_net(par), newskb, RTN_UNSPEC) != 0)
> |   |  ^~
> | In file included from 
> /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
> |  from 
> /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:16:
> | /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:5: 
> note: declared here
> |19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
> sk_buff *skb, unsigned addr_type);
> |   | ^~
> `
>
> This has been fixed upstream with 3.12 and 3.13 respectively.

Yes, I just noticed the new releases.  I'm in the process of packaging
3.13 now.

J.


signature.asc
Description: PGP signature

Bug#975361: marked as done (src:node-rollup-plugin-buble: contains source-less code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 11:51:59 +0100
with message-id 
and subject line Closed with 975362
has caused the Debian Bug report #975361,
regarding src:node-rollup-plugin-buble: contains source-less code
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.)


-- 
975361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-buble
Version: 0.21.3+~0.19.8-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

files below packages/wasm/ are source-less compiled wabt code.

Lintian warns about this, but is suppressed with comment "Unused files".
That is wrong: A Debian source package *must* include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4ChEACgkQLHwxRsGg
ASFB1hAAn3pcGUDsrTKqMftFl/W4amljA7NdP4ROtZ1L+ipgG9Ua+x4MRdnDGvEW
ostgZJvQVwJK5NSm3OU7rM6hkrmwAC4Aotj/eJMIjTbT4mfo5KyfBedjZgOkzPcI
I5G7tGhXVQ69381rq6S5pYfLWxgR1hVuvohjYb2ko8N4cBqAESDIzVnYgCPhxaQJ
TyNahaQwQZzK3UaR1lgysP7a+MiKrZuQJSU5gYNOxNv8Zn8vFSQ+2K10BVFZHy2r
6Y65eZUP9NcmGsAG3DVYBnZXrBiTd+GMdAP0cXncslVCsbSmOLU+Yn8fJPkrHjH8
RiwJLZiVsh5nbRRMFPuCS657E5KOKYNnOU8g0X5u3Zs/UsPOA0KA4Vy6bz2MYHmD
d08Fy9XA2vRzgfzUXQ+gSd7zBn2kV5fAOQwGkyMrms02FEZACUS0yP4dHF3yb1LF
5aHtcT3QvfTsnjJ56Y8PeXWkzfzBXIZBo2N3Oaf/7XoFTvMX3tGbUgs0mF8O4/0+
Eq8wE3IfbuviI2jvI2RRTyMXMNE1qarKSZ1LVvtS1ZTn52CUv+TvV9tdhzQX5EmB
EooeozVer1NugJ49Osd99L04vclxKaw3LqbFwhfNjyhivsasiVxJ8VXwXkmxtx7a
T5Oq81DuddD5EElOOdhqabai/xSfH5E+NAEcUPYdEAWV6aaIxsg=
=7UD4
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 20999--- End Message ---

Bug#975376: Fails to build with Linux 5.9.9 because of change in ip_route_me_harder()

[Sven Hartge]

Package: xtables-addons-dkms
Version: 3.11-1
Severity: grave

Hi!

Kernel 5.9.9 changes ip_route_me_harder() with commit
46d6c5ae953cc0be38efd0e469284df7c4328cf8 causing a build failure for
xtables-addons-dkms:

,
| In file included from 
/usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
|  from 
/var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:20:
| /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:74: 
note: expected ‘struct sk_buff *’ but argument is of type ‘unsigned int’
|19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
sk_buff *skb, unsigned addr_type);
|   |  
^~~
| /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:125:6: error: 
too few arguments to function ‘ip_route_me_harder’
|   125 |  if (ip_route_me_harder(net, nskb, addr_type))
|   |  ^~
| In file included from 
/usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
|  from 
/var/lib/dkms/xtables-addons/3.11/build/extensions/xt_DELUDE.c:20:
| /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:5: 
note: declared here
|19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
sk_buff *skb, unsigned addr_type);
|   | ^~
| /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c: In function 
‘echo_tg4’:
| /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:195:39: error: 
passing argument 2 of ‘ip_route_me_harder’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
|   195 |  if (ip_route_me_harder(par_net(par), newskb, RTN_UNSPEC) != 0)
|   |   ^~
|   |   |
|   |   struct sk_buff *
| In file included from 
/usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
|  from 
/var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:16:
| /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:54: 
note: expected ‘struct sock *’ but argument is of type ‘struct sk_buff *’
|19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
sk_buff *skb, unsigned addr_type);
|   | ~^~
| /var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:195:6: error: 
too few arguments to function ‘ip_route_me_harder’
|   195 |  if (ip_route_me_harder(par_net(par), newskb, RTN_UNSPEC) != 0)
|   |  ^~
| In file included from 
/usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter/x_tables.h:245,
|  from 
/var/lib/dkms/xtables-addons/3.11/build/extensions/xt_ECHO.c:16:
| /usr/src/linux-headers-5.9.0-3-common/include/linux/netfilter_ipv4.h:19:5: 
note: declared here
|19 | int ip_route_me_harder(struct net *net, struct sock *sk, struct 
sk_buff *skb, unsigned addr_type);
|   | ^~
`

This has been fixed upstream with 3.12 and 3.13 respectively.

Grüße,
Sven.

Bug#975372: minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge

[Chris Lamb]

Source: minidlna
Version: 1.2.1+dfsg-2
Severity: serious
Tags: patch

Hi,

Purging the package currently fails with the following error:

  Purging configuration files for minidlna (1.2.1+dfsg-2) ...
  rm: cannot remove '/var/log/minidlna': Is a directory
  dpkg: error processing package minidlna (--purge):
   installed minidlna package post-removal script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   minidlna
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Patch attached.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-diff --git a/debian/minidlna.postrm b/debian/minidlna.postrm
index 0e9114d..5cde64c 100644
--- a/debian/minidlna.postrm
+++ b/debian/minidlna.postrm
@@ -5,8 +5,8 @@ set -e
 
 case "$1" in
 purge)
-   rm -rf /var/cache/minidlna
-rm -f /var/log/minidlna.log* /var/log/minidlna
+   rm -rf /var/cache/minidlna /var/log/minidlna
+rm -f /var/log/minidlna.log*
 ;;
 
 remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)

Bug#972454: marked as done (Does not build with Linux 5.9, but new compatible release available upstream)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:19:13 +
with message-id <20201121091913.gg206...@azazel.net>
and subject line 3.11 uploaded to the archive.
has caused the Debian Bug report #972454,
regarding Does not build with Linux 5.9, but new compatible release available 
upstream
to be marked as done.

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

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


-- 
972454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons-dkms
Version: 3.9-1
Severity: grave
Tags: patch

Hello!

As the subject says: The current version 3.9 does not build with Linux
5.9, but a new upstream release is available.

I created a MR in Salsa correcting this:

https://salsa.debian.org/debian/xtables-addons/-/merge_requests/1

It contains the following changes:

 New upstream release, compatible with Linux 5.9
 
 * Update watch file to new release location
   Releases can now be downloaded from https://inai.de/files/xtables-addons/
 * Disable patches integrated upstream
 * Also install xt_geoip_fetch script and man page

Grüße,
Sven.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xtables-addons-dkms depends on:
ii  dkms   2.8.3-4
ii  make   4.3-4
ii  xtables-addons-common  3.11-0.0~sh.1

Versions of packages xtables-addons-dkms recommends:
pn  linux-headers  

xtables-addons-dkms suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
A new 3.11-1 package has now been accepted into unstable.

J.


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

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:47 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-replace 
2.3.4+repack+~2.2.0-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-replace
Source-Version: 2.3.4+repack+~2.2.0-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated 
node-rollup-plugin-replace 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, 21 Nov 2020 09:27:42 +0100
Source: node-rollup-plugin-replace
Architecture: source
Version: 2.3.4+repack+~2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-replace (2.3.4+repack+~2.2.0-1) unstable; urgency=medium
 .
   * Team upload
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 faf2b664a9738318a3ba4dab7d32b9a493c75559 2976 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.dsc
 b32e83503166f9862b674f32044bdb69fd1f4cc0 38212 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig-legacy.tar.xz
 5661ed9a84f93c1017d034599946feb1ec482ba5 324792 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig.tar.xz
 780ddb7794418cc0796a46c6feb81f00e3d1f216 6156 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.debian.tar.xz
Checksums-Sha256: 
 5b2ac14add5d69305ba5c61e70a010b1995dcbdcd91c4447284014714f6f7944 2976 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.dsc
 883c0d6e30b2f32ec1b4b2e6dbb0a1ece000bfc176579681d17f728b665a41a5 38212 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig-legacy.tar.xz
 bbe3fb6619b7c4fdb33b4309421cf93564e350b1b975c74fd21099348d1d16ce 324792 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig.tar.xz
 ad7e76616fbc2e54efb4518e0a20e0b194a86a88cd74fd738ddf027fdcfcb148 6156 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.debian.tar.xz
Files: 
 e55729074ac86dc33f30d9b70fd42cd2 2976 javascript optional 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.dsc
 246be610ac7ead3522f5b04b10488071 38212 javascript optional 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig-legacy.tar.xz
 5daceb64e1eff65b5c056ada86264e6e 324792 javascript optional 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0.orig.tar.xz
 50cc9992b61608f3538e7a780533faa1 6156 javascript optional 
node-rollup-plugin-replace_2.3.4+repack+~2.2.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl+41aIACgkQ9tdMp

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:35 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-json 
4.1.0+repack+~4.0.0-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-json
Source-Version: 4.1.0+repack+~4.0.0-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-rollup-plugin-json 
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, 21 Nov 2020 09:27:18 +0100
Source: node-rollup-plugin-json
Architecture: source
Version: 4.1.0+repack+~4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-json (4.1.0+repack+~4.0.0-1) unstable; urgency=medium
 .
   * Team upload
   * Use dh-sequence-nodejs
   * Use pkg-js-tools 0.9.41 auto test link
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 cab258327cea32106cc730fd344b6bf86795a644 3019 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.dsc
 49938aa880a653f8060782427a52cba3c88758b7 36172 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig-legacy.tar.xz
 8eda4d2724d6aac9dab0e70d9e3cb4fd7b4a039f 289556 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig.tar.xz
 5ea27387b3ac6f59497eebef83ca43d93daf8ca7 5880 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.debian.tar.xz
Checksums-Sha256: 
 17641f3473f51702b332056022beb93e6da0009b85223f8ce3b1abe6f5155765 3019 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.dsc
 4cdea8f61d64fad4f2ef09b546879d315d68c8d27c95656b1ec0e4129792f710 36172 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig-legacy.tar.xz
 66e0880c3a4fccfcf856e7e9add05a0be0f1f697b432473e57d782af25c346d8 289556 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig.tar.xz
 d53275610d6b39acb137c1d3a84fe9d96d55fe286d37870c394a23613e18d0ef 5880 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.debian.tar.xz
Files: 
 fcca2f33f06d62559b3088dea1b16cb7 3019 javascript optional 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.dsc
 0f8230e94bbcaff0325a214125494366 36172 javascript optional 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig-legacy.tar.xz
 d7d35cf2dc3ffda4d04bf125cb537e95 289556 javascript optional 
node-rollup-plugin-json_4.1.0+repack+~4.0.0.orig.tar.xz
 91c4efaa2355f7a8c8e4ce04988796c7 5880 javascript optional 
node-rollup-plugin-json_4.1.0+repack+~4.0.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukF

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:41 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-node-resolve 
10.0.0+repack+~4.2.4-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-node-resolve
Source-Version: 10.0.0+repack+~4.2.4-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated 
node-rollup-plugin-node-resolve 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, 21 Nov 2020 09:27:33 +0100
Source: node-rollup-plugin-node-resolve
Architecture: source
Version: 10.0.0+repack+~4.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-node-resolve (10.0.0+repack+~4.2.4-1) unstable; 
urgency=medium
 .
   * Team upload
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 07e216b2d7da4e01f4b324e67f747ab12570cf04 3208 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.dsc
 44fa70dd5d2a7f4c7a7ef43bfea184683f3d9bb3 39092 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig-legacy.tar.xz
 c67bb3107bcd8437562886e5928db2d0b8b8ebc1 324968 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig.tar.xz
 f95a1d8aa0e6876a537f55751bf24617b9e8558f 8396 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.debian.tar.xz
Checksums-Sha256: 
 eb2b48c722557b1446987c7317c0322dd9fa73160fe55539f5850d88ea55082e 3208 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.dsc
 0bdfa3e89fa0a586693bbdceffd81b0972ba0dd07e0873eef34dd993e7257a4c 39092 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig-legacy.tar.xz
 62e6befa30965e3c9aaec95055e7e3a06934c38d0198fceba7df8c6e7ba864f3 324968 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig.tar.xz
 762445590816f17f838bb05b6d8ad5b16210bc7833b555719c51c766771efbbc 8396 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.debian.tar.xz
Files: 
 b0d4f81af816fea8b724001ca0c701e3 3208 javascript optional 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.dsc
 18fbbf050df498627e86eab6c134e566 39092 javascript optional 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig-legacy.tar.xz
 8fb7b025c8a4762c7a25b809f6986dd0 324968 javascript optional 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4.orig.tar.xz
 ec6a38f6a01b11e4bf732a031015a4ea 8396 javascript optional 
node-rollup-plugin-node-resolve_10.0.0+repack+~4.2.4-1.

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:14 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-alias 
3.1.1+repack+~2.2.0-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-alias
Source-Version: 3.1.1+repack+~2.2.0-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-rollup-plugin-alias 
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, 21 Nov 2020 09:26:06 +0100
Source: node-rollup-plugin-alias
Architecture: source
Version: 3.1.1+repack+~2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-alias (3.1.1+repack+~2.2.0-1) unstable; urgency=medium
 .
   * Team upload
   * Add missing provides
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 d36236173a46f7b4d2bb4026a36ea9ea1856bc14 2814 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.dsc
 4a1effb20bfeb3ccc3a853910aac140b6657d3fc 84520 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig-legacy.tar.xz
 e2f5585023cc2bac39a86c53483084521978a506 289420 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig.tar.xz
 8be3e0d3b5b5d24de89967a881612a26ff00d6a2 6152 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.debian.tar.xz
Checksums-Sha256: 
 9d949424f65908a65b74fc95e5ef3d7568eef862240de85cc7395ec4ebdd9e08 2814 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.dsc
 879506436fcc49755ad1a188f016408f884f1e10da71697baf317ae021bccf35 84520 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig-legacy.tar.xz
 ce1404f86ec90ef0f32ca7e2a75d49b478e30c6a47cbb1c9b788d9b1a7ee8e2d 289420 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig.tar.xz
 91a0c4d75e8ba3414a53b479d8f71af24ba9f7255fba64f5292fe64d4615bcbe 6152 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.debian.tar.xz
Files: 
 26137abec8798317891bb7c816035a39 2814 javascript optional 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.dsc
 6a913644a232f095a69ea0b75df1976c 84520 javascript optional 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig-legacy.tar.xz
 1679e2224823eb45bf52e01585d1963a 289420 javascript optional 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0.orig.tar.xz
 96a20afb3d117d1a36c498fbfff2f9e9 6152 javascript optional 
node-rollup-plugin-alias_3.1.1+repack+~2.2.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl+41DQACgkQ9tdMp8mZ
7umHYg

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:21 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-babel 
5.2.1+repack+~4.4.0-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-babel
Source-Version: 5.2.1+repack+~4.4.0-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-rollup-plugin-babel 
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, 21 Nov 2020 09:26:29 +0100
Source: node-rollup-plugin-babel
Architecture: source
Version: 5.2.1+repack+~4.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-babel (5.2.1+repack+~4.4.0-1) unstable; urgency=medium
 .
   * Team upload
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 44e47dc722ba4b7bce585fe9ee16dfed4c2eafbd 2848 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.dsc
 a23504966226a898503f4306ac240f986e7f8837 46244 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig-legacy.tar.xz
 8671b483056b6278a3d574ff79a4896d7e459b82 310020 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig.tar.xz
 69cb6ab2b57a68d34d525120a4cea86c2da9d34d 7468 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.debian.tar.xz
Checksums-Sha256: 
 0863f7846e31bed3e7468df19a477ab0c3456ddb85473f425fea682238dc27d4 2848 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.dsc
 7445c0e41b55b68909988d0e231dddfcba5ef2ea76af8a50fbf62f6ed204415e 46244 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig-legacy.tar.xz
 77bc576df22a7d117594c16122720fd0070f6483e8e9405f73f3f173f9f85587 310020 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig.tar.xz
 90c23e27f1fc5625bc15637c9343c911f6af2bb663de18b1161946793de15483 7468 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.debian.tar.xz
Files: 
 c28f6cf70b5e0a2e64ab65f43112e840 2848 javascript optional 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.dsc
 0f101e3ebb08ebabad37de5d05f59531 46244 javascript optional 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig-legacy.tar.xz
 de430e60b24479954e840e8c6bffd0b0 310020 javascript optional 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0.orig.tar.xz
 17f484247c0ea70f39a44aea7783f576 7468 javascript optional 
node-rollup-plugin-babel_5.2.1+repack+~4.4.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl+41McACgkQ9tdMp8mZ
7unckhAAkAGZwzQyvD8iUq0FkGOHNiL0

Bug#975362: marked as done (src:node-rollup-plugin-json: contains source-less wasm code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:20:28 +
with message-id 
and subject line Bug#975362: fixed in node-rollup-plugin-buble 
0.21.3+repack+~0.19.8-1
has caused the Debian Bug report #975362,
regarding src:node-rollup-plugin-json: contains source-less wasm code
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.)


-- 
975362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-buble
Source-Version: 0.21.3+repack+~0.19.8-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-rollup-plugin-buble 
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, 21 Nov 2020 09:26:39 +0100
Source: node-rollup-plugin-buble
Architecture: source
Version: 0.21.3+repack+~0.19.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975362
Changes:
 node-rollup-plugin-buble (0.21.3+repack+~0.19.8-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Pirate Praveen ]
   * Update minimum version of node-typescript
 .
   [ Xavier Guimard ]
   * Remove @rollup/wasm from import (Closes: #975362) and repack
Checksums-Sha1: 
 5d72473c109d25a8f659e086dad0d61e07e23991 2854 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.dsc
 24b060603c23d735c151a080061c0aacb8cd97a2 16208 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig-legacy.tar.xz
 ec41c07f62fe19a10b2803a99cc4a288a7af7990 269272 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig.tar.xz
 388f2e4f220bffb9242d29b8f42bf4f3362e21ae 3880 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.debian.tar.xz
Checksums-Sha256: 
 2370713cc5789c72f076dafb005bab048245d109e2d90649bd0c4511cf2aad6f 2854 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.dsc
 dd010df6ccb12bcdd305761e67771329f510bfc8f79832175a4028cfc634e426 16208 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig-legacy.tar.xz
 5cb5bdb78513ce66d15f9d44ea5cbbc5becaa01ec70dd9d0cd6070fc47c01035 269272 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig.tar.xz
 fc51a382e20282a27a2858fb49d26c513d83a6f5c19180dec224532c6c78d229 3880 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.debian.tar.xz
Files: 
 9e4c662afcaefb958ef392253f293675 2854 javascript optional 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.dsc
 104b56dbed6d89188290991af862a9bf 16208 javascript optional 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig-legacy.tar.xz
 02429701c7f571ced092e5fb35c9717c 269272 javascript optional 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8.orig.tar.xz
 f3e700af8881d4765f43bb56fa79683b 3880 javascript optional 
node-rollup-plugin-buble_0.21.3+repack+~0.19.8-1.debian.tar.xz

Bug#975241: marked as done (terminado fails autopkg tests both in testing and unstable)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 09:21:04 +
with message-id 
and subject line Bug#975241: fixed in terminado 0.9.1-2
has caused the Debian Bug report #975241,
regarding terminado fails autopkg tests both in testing and unstable
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.)


-- 
975241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:terminado
Version: 0.9.1-1
Severity: serious
Tags: sid bullseye ftbfs

terminado fails autopkg tests both in testing and unstable:

[...]
autopkgtest [18:10:36]: test runtestsuite3: [---
..E
==
ERROR: test_max_terminals (terminado.tests.basic_test.NamedTermTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 98, in __call__
result = self.orig_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 594, in
post_coroutine
return self.io_loop.run_sync(
  File "/usr/lib/python3/dist-packages/tornado/ioloop.py", line 532, in run_sync
return future_cell[0].result()
  File "/usr/lib/python3/dist-packages/tornado/gen.py", line 742, in run
yielded = self.gen.throw(*exc_info)  # type: ignore
  File
"/tmp/autopkgtest-lxc.lx8y8pgy/downtmp/build.JHO/src/terminado/tests/basic_test.py",
line 216, in test_max_terminals
pids = yield self.get_pids(tms)
  File "/usr/lib/python3/dist-packages/tornado/gen.py", line 735, in run
value = future.result()
  File "/usr/lib/python3/dist-packages/tornado/gen.py", line 742, in run
yielded = self.gen.throw(*exc_info)  # type: ignore
  File
"/tmp/autopkgtest-lxc.lx8y8pgy/downtmp/build.JHO/src/terminado/tests/basic_test.py",
line 127, in get_pids
pid = yield tm.get_pid()
  File "/usr/lib/python3/dist-packages/tornado/gen.py", line 735, in run
value = future.result()
  File "/usr/lib/python3/dist-packages/tornado/gen.py", line 748, in run
yielded = self.gen.send(value)
  File
"/tmp/autopkgtest-lxc.lx8y8pgy/downtmp/build.JHO/src/terminado/tests/basic_test.py",
line 98, in get_pid
pid = int(stdout.split('\n')[1])
ValueError: invalid literal for int() with base 10: '\x1b[?2004l\r3257\r'
 >> begin captured logging << 
asyncio: DEBUG: Using selector: EpollSelector
tornado.general: WARNING: tornado.autoreload started more than once in the same
process
tornado.access: INFO: 101 GET /named/0 (127.0.0.1) 1.06ms
terminado.websocket: INFO: TermSocket.open: 0
terminado.management: INFO: New terminal with specified name: 0
terminado.websocket: INFO: TermSocket.open: Opened 0
tornado.access: INFO: 101 GET /named/1 (127.0.0.1) 14.85ms
terminado.websocket: INFO: TermSocket.open: 1
terminado.management: INFO: New terminal with specified name: 1
terminado.websocket: INFO: TermSocket.open: Opened 1
tornado.access: INFO: 101 GET /named/2 (127.0.0.1) 1.24ms
terminado.websocket: INFO: TermSocket.open: 2
terminado.management: INFO: New terminal with specified name: 2
terminado.websocket: INFO: TermSocket.open: Opened 2
terminado.management: INFO: EOF on FD 18; stopping reading
terminado.management: INFO: Terminal 0 closed
terminado.management: INFO: EOF on FD 19; stopping reading
terminado.management: INFO: Terminal 1 closed
terminado.management: INFO: EOF on FD 20; stopping reading
terminado.management: INFO: Terminal 2 closed
- >> end captured logging << -

--
Ran 3 tests in 9.230s

FAILED (errors=1)
--- End Message ---
--- Begin Message ---
Source: terminado
Source-Version: 0.9.1-2
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated terminado 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:

Bug#975362: [Pkg-javascript-devel] Bug#975362: src:node-rollup-plugin-json: contains source-less wasm code

[Xavier]

Le 20/11/2020 à 19:33, Jonas Smedegaard a écrit :
> Package: src:node-rollup-plugin-json
> Version: 4.1.0+~4.0.0-2
> Severity: serious
> Justification: Policy 2.1
>
> source contains compiled webassembly code from project wabt.
> 
> A corresponding lintian override has the comment "Unused files",
> but that's not ok: Used or not, all code must include source.

Fixed, thanks. However you should also open a bug against lintian: if
you consider that having unused wasm files in source is a RC bug, then
lintian should not consider this as "pedantic".

Ref:
 P source-contains-prebuilt-wasm-binary

 The source tarball contains a prebuilt binary wasm object. They are
 usually provided for the convenience of users. These files usually just
 take up space in the tarball and need to be rebuilt from source.

 Check if upstream also provides source-only tarballs that you can use
 as the upstream distribution instead. If not, you may want to ask
 upstream to provide source-only tarballs.

List of packages that have wasm files in their sources:
https://lintian.debian.org/tags/source-contains-prebuilt-wasm-binary.html

Bug#975241: marked as pending in terminado

[Julien Puydt]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/terminado/-/commit/6ebf175a8c93d92b9b173ac2de85763acf4894f0


Add trivial patch (Closes: #975241)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975241

Processed: Bug#975241 marked as pending in terminado

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975241 [src:terminado] terminado fails autopkg tests both in testing and 
unstable
Added tag(s) pending.

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

Processed: Bug#975362 marked as pending in node-rollup-plugin-replace

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Ignoring request to alter tags of bug #975362 to the same tags previously set

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

Bug#975362: marked as pending in node-rollup-plugin-node-resolve

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-node-resolve/-/commit/4c53beae9f61b6193a40457a7d6cc98bb502d5da


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Bug#975362: marked as pending in node-rollup-plugin-replace

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-replace/-/commit/7398569fd9752e814c6497dc8e24527b18b04a5a


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Processed: Bug#975362 marked as pending in node-rollup-plugin-node-resolve

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Ignoring request to alter tags of bug #975362 to the same tags previously set

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

Bug#975362: marked as pending in node-rollup-plugin-json

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-json/-/commit/a181fe9d650fb6b8490b16d37cd6932cc9547dd6


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Processed: Bug#975362 marked as pending in node-rollup-plugin-json

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Ignoring request to alter tags of bug #975362 to the same tags previously set

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

Processed: Bug#975362 marked as pending in node-rollup-plugin-buble

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Ignoring request to alter tags of bug #975362 to the same tags previously set

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

Bug#975362: marked as pending in node-rollup-plugin-buble

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-buble/-/commit/d791b569f5f1cc8f9cc497904f83ed2bf253cbeb


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Processed: Bug#975362 marked as pending in node-rollup-plugin-babel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Ignoring request to alter tags of bug #975362 to the same tags previously set

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

Bug#975362: marked as pending in node-rollup-plugin-babel

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-babel/-/commit/99a0666832faa1c480c941f9f547a02afcd10cca


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Bug#975362: marked as pending in node-rollup-plugin-alias

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-rollup-plugin-alias/-/commit/a7ef897bc85557b3f9c296dcfc922b8192213f29


Remove @rollup/wasm from import

Closes: #975362


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975362

Processed: Bug#975362 marked as pending in node-rollup-plugin-alias

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975362 [src:node-rollup-plugin-json] src:node-rollup-plugin-json: contains 
source-less wasm code
Added tag(s) pending.

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

Bug#975360: marked as done (node-webassemblyjs: contains source-less code)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 08:48:33 +
with message-id 
and subject line Bug#975360: fixed in node-webassemblyjs 
1.9.1+repack+~cs10.9.15-1
has caused the Debian Bug report #975360,
regarding node-webassemblyjs: contains source-less code
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.)


-- 
975360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-webassemblyjs
Version: 1.9.1+dfsg+~cs7.7.13-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains convenience code copy of wabt.js
which consist almost purely of compiled wabt code.

Furthermore, lintian warnings about this issue is wrongly suppressed.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4B6EACgkQLHwxRsGg
ASEG+hAApEZ5/tEVl+sCMLRbCGzXgdu5az0zuSBYnxjIbJlz75gkWPyMC8JxK+A3
8L2+TRPDIX5EoTAAdojwfqeXygKs8E9sl07POw50//Srw9m+tbvVNn1KL8fun6hm
B0k1GKIWuwoVF92kRUE5rT5ySab7Cx8krEO4fsxB+038O+1wWCTGvApzWh8c1lhU
t9uIuJG0w9mPtHheI44VKaez/ZelJk/qZ3k5Acf+0AjU8E1IGXfkz8P5rrW2H9h7
t+MwJhFPydR/2IcuSYP2jBVqOXJojYHYO78dQQyuSzosYh7WfoO3/FEZdNaAd9WX
Vc+4EVCpi9qfMrlE/eNqdGG0LMd92dr8SvB9Pa6lPLUCMSj5iAyM5N+anKR4u9FH
KL340LkiSf7d0oeRn9sn4NcZlDoDVx7eY3qVBYsmIMIv0mVvt042OfOHqxs2z2fZ
6YqJh6cNx4GLjsLmXsDR+uvz3dnTIIaHYGyf1G0i69a3UYI/D+tkabFO9IKzPTjc
qwh1+By1pXswgN+aTwGnetYOrRF5mXA3RZAVt+tvapVoiX7Q0HlhsACyXeLL55Df
Wnwt1wfkY6wqDTWPXZf06VS0/7v10+emPE5AtL4edsiGcSIUlabVSsOEHMI/R8EL
zP+unlUb54F5ZwLF9Qxtyvr9kR5Ok7xjGxSGbRsYOUjMtwQ2xR8=
=5FNY
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-webassemblyjs
Source-Version: 1.9.1+repack+~cs10.9.15-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-webassemblyjs 
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, 21 Nov 2020 08:38:25 +0100
Source: node-webassemblyjs
Architecture: source
Version: 1.9.1+repack+~cs10.9.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 975360
Changes:
 node-webassemblyjs (1.9.1+repack+~cs10.9.15-1) unstable; urgency=medium
 .
   * Team upload
   * No more embed wabt (source unavailable) and repack. This will break
 @webassemblyjs/wasm-parser and wast-loader (Closes: #975360)
Checksums-Sha1: 
 246e812d366c9199ab9454fa0680a56927614e0c 5270 
node-webassemblyjs_1.9.1+repack+~cs10.9.15-1.dsc
 5c7460d55bdaa173973c7eaa4e59cf73857a73ac 7052 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-arrayprototypeflatmap.tar.xz
 52c20d8e798ccee8238a16e3b6d76d1f2fac569b 2420 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-babel-plugin-mamacro.tar.xz
 fce9bc2c717ca40e4ba23dad3df15601268b1863 5260 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-call-bind.tar.xz
 7b623582934a60dc8e1a51dc915fc898450c1354 8600 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-get-intrinsic.tar.xz
 5cd7e7fc2b950177a40645e9f2130e222cab9848 9008 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-is-regex.tar.xz
 c1cc1584a10a9c60348eaeb04b9fea3eb41553c8 2600 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-requireindex.tar.xz
 b1b4c550f6c518c95d0afeef943833d41a0cc940 3052 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-xtucieee754.tar.xz
 b7d440b7a10cf8c54f557af60c6f7e48a92c1fdb 24960 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-xtuclong.tar.xz
 0b090b64d057d56d031074da8367661781135375 489848 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig.tar.xz
 bab33daeaf85fbb9f2fbfafba10036a8aee16cd7 6576 
node-webassemblyjs_1.9.1+repack+~cs10.9.15-1.debian.tar.xz
Checksums-Sha256: 
 3f511d1abbaef7edcde61e1c96758c5aa6e5add952d651886279037542a21a7f 5270 
node-webassemblyjs_1.9.1+repack+~cs10.9.15-1.dsc
 38ebbc1731b600f74131d58334e86b3c4e08991607a1b5744edeefadcd44d404 7052 
node-webassemblyjs_1.9.1+repack+~cs10.9.15.orig-arrayprototypeflatmap.tar.xz
 99958bb515f5f74ac1ba6

Bug#973104: marked as done (caffe: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libboost_python39.so.1.71.0: undefined reference to `_Py_NewReference')

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 08:46:36 +
with message-id 
and subject line Bug#973104: fixed in caffe 1.0.0+git20180821.99bd997-8
has caused the Debian Bug report #973104,
regarding caffe: FTBFS: ld: 
/usr/lib/x86_64-linux-gnu/libboost_python39.so.1.71.0: undefined reference to 
`_Py_NewReference'
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.)


-- 
973104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe
Version: 1.0.0+git20180821.99bd997-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-sign-compare -Wno-uninitialized -O3 
> -DNDEBUG -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic 
> CMakeFiles/test.testbin.dir/test_accuracy_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_argmax_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_batch_norm_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_batch_reindex_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_benchmark.cpp.o 
> CMakeFiles/test.testbin.dir/test_bias_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_blob.cpp.o 
> CMakeFiles/test.testbin.dir/test_caffe_main.cpp.o 
> CMakeFiles/test.testbin.dir/test_common.cpp.o 
> CMakeFiles/test.testbin.dir/test_concat_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_contrastive_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_convolution_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_crop_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_data_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_data_transformer.cpp.o 
> CMakeFiles/test.testbin.dir/test_db.cpp.o 
> CMakeFiles/test.testbin.dir/test_deconvolution_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_dummy_data_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_eltwise_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_embed_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_euclidean_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_filler.cpp.o 
> CMakeFiles/test.testbin.dir/test_filter_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_flatten_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_gradient_based_solver.cpp.o 
> CMakeFiles/test.testbin.dir/test_hdf5_output_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_hdf5data_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_hinge_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_im2col_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_image_data_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_infogain_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_inner_product_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_internal_thread.cpp.o 
> CMakeFiles/test.testbin.dir/test_io.cpp.o 
> CMakeFiles/test.testbin.dir/test_layer_factory.cpp.o 
> CMakeFiles/test.testbin.dir/test_lrn_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_lstm_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_math_functions.cpp.o 
> CMakeFiles/test.testbin.dir/test_maxpool_dropout_layers.cpp.o 
> CMakeFiles/test.testbin.dir/test_memory_data_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_multinomial_logistic_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_mvn_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_net.cpp.o 
> CMakeFiles/test.testbin.dir/test_neuron_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_platform.cpp.o 
> CMakeFiles/test.testbin.dir/test_pooling_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_power_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_protobuf.cpp.o 
> CMakeFiles/test.testbin.dir/test_random_number_generator.cpp.o 
> CMakeFiles/test.testbin.dir/test_reduction_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_reshape_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_rnn_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_scale_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_sigmoid_cross_entropy_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_slice_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_softmax_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_softmax_with_loss_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_solver.cpp.o 
> CMakeFiles/test.testbin.dir/test_solver_factory.cpp.o 
> CMakeFiles/test.testbin.dir/test_split_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_spp_layer.cpp.o 
> CMakeFiles/test.testbin.dir/test_stochastic_pooling.cpp.o 
> CMakeFiles/test.testbin.dir/test_syncedmem.cpp.o 

Bug#973825: sdpa: diff for NMU version 7.3.14+dfsg-1.1

[Sebastian Ramacher]

Control: tags 973825 + patch
Control: tags 973825 + pending

Dear maintainer,

I've prepared an NMU for sdpa (versioned as 7.3.14+dfsg-1.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru sdpa-7.3.14+dfsg/debian/changelog sdpa-7.3.14+dfsg/debian/changelog
--- sdpa-7.3.14+dfsg/debian/changelog	2020-03-14 01:00:00.0 +0100
+++ sdpa-7.3.14+dfsg/debian/changelog	2020-11-21 09:34:51.0 +0100
@@ -1,3 +1,14 @@
+sdpa (7.3.14+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Peter Michael Green ]
+  * Use only the first two parts of version number when generating libmumps-seq dependency
+(Closes: 973825)
+  * Bump build-dependency on libmumps-seq-dev to >= 5.3.4
+
+ -- Sebastian Ramacher   Sat, 21 Nov 2020 09:34:51 +0100
+
 sdpa (7.3.14+dfsg-1) unstable; urgency=low
 
* New upstream
diff -Nru sdpa-7.3.14+dfsg/debian/control sdpa-7.3.14+dfsg/debian/control
--- sdpa-7.3.14+dfsg/debian/control	2020-03-14 01:00:00.0 +0100
+++ sdpa-7.3.14+dfsg/debian/control	2020-11-21 09:25:33.0 +0100
@@ -4,7 +4,7 @@
 Maintainer: Makoto Yamashita 
 Build-Depends: cdbs, debhelper (>= 7), 
automake, autotools-dev, autoconf, gfortran,
-   libopenblas-pthread-dev, libmumps-seq-dev, libscotch-dev, liboctave-dev
+   libopenblas-pthread-dev, libmumps-seq-dev (>= 5.3.4), libscotch-dev, liboctave-dev
 Standards-Version: 4.1.1
 Homepage: http://sdpa.sourceforge.net/
 
diff -Nru sdpa-7.3.14+dfsg/debian/rules sdpa-7.3.14+dfsg/debian/rules
--- sdpa-7.3.14+dfsg/debian/rules	2020-03-14 01:00:00.0 +0100
+++ sdpa-7.3.14+dfsg/debian/rules	2020-11-21 09:25:08.0 +0100
@@ -38,7 +38,7 @@
 DEB_CONFIGURE_EXTRA_FLAGS += --with-mumps-libs=$(MUMPS_LIBS)
 
 
-LIBMUMPS_VER := $(shell dpkg --status libmumps-seq-dev | awk '/^Version:/ {print $$2}' |cut -f 1 -d "-")
+LIBMUMPS_VER := $(shell dpkg --status libmumps-seq-dev | awk '/^Version:/ {print $$2}' |cut -f 1 -d "-" | cut -d . -f 1-2)
 DEB_DH_GENCONTROL_ARGS_ALL = -- -Vmumps-seq:Version=$(LIBMUMPS_VER)
 
 SDPA_DIR=$(CURDIR)/debian/sdpa


signature.asc
Description: PGP signature

Processed: sdpa: diff for NMU version 7.3.14+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 973825 + patch
Bug #973825 [src:sdpa] sdpa dependency generation broken with latest mumps
Added tag(s) patch.
> tags 973825 + pending
Bug #973825 [src:sdpa] sdpa dependency generation broken with latest mumps
Added tag(s) pending.

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