Bug#949464: marked as done (the gwcs build accesses the network during the build)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 08:42:39 +
with message-id 
and subject line Bug#949464: fixed in sphinx-astropy 1.2-2
has caused the Debian Bug report #949464,
regarding the gwcs build accesses the network during the build
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.)


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

the gwcs build accesses the network during the build, according to the build 
log:

[...]
Running Sphinx v1.8.5
making output directory...
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from
/usr/lib/python3/dist-packages/sphinx_astropy/local/python3_local_links.inv...
loading intersphinx inventory from 
https://docs.scipy.org/doc/numpy/objects.inv...
loading intersphinx inventory from
https://docs.scipy.org/doc/scipy/reference/objects.inv...
loading intersphinx inventory from https://matplotlib.org/objects.inv...
loading intersphinx inventory from 
http://docs.astropy.org/en/stable/objects.inv...
loading intersphinx inventory from http://docs.h5py.org/en/stable/objects.inv...
[autosummary] generating autosummary for: gwcs/ifu.rst,
gwcs/imaging_with_distortion.rst, gwcs/points_to_wcs.rst, gwcs/pure_asdf.rst,
gwcs/schemas/index.rst, gwcs/using_wcs.rst, gwcs/wcs_ape.rst,
gwcs/wcs_validation.rst, gwcs/wcstools.rst, index.rst
[automodsumm] index.rst: found 20 automodsumm entries to generate
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 10 source files that are out of date
updating environment: 30 added, 0 changed, 0 removed
--- End Message ---
--- Begin Message ---
Source: sphinx-astropy
Source-Version: 1.2-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated sphinx-astropy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 08:40:16 +0100
Source: sphinx-astropy
Architecture: source
Version: 1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 949464
Changes:
 sphinx-astropy (1.2-2) unstable; urgency=medium
 .
   * Disable intersphinx mapping for Debian package builds (Closes: #949464)
   * Push Standards-Version to 4.5.0. No changes needed.
Checksums-Sha1:
 22513f875e8f893790b9591afc9128709d0b0cac 2252 sphinx-astropy_1.2-2.dsc
 4468e75c8bbc930dd9da56933402f023ab694e4b 3136 
sphinx-astropy_1.2-2.debian.tar.xz
Checksums-Sha256:
 3c91c03b6c032a4931f68cdd3bbe051e76b2297b6cd43eb5025790072b04c62e 2252 
sphinx-astropy_1.2-2.dsc
 a35918b243950db931171687e9d7faa8c3be45d54d24ac03d514c2dbc187968b 3136 
sphinx-astropy_1.2-2.debian.tar.xz
Files:
 1b0423d81682b5f7412eb1c746687442 2252 python optional sphinx-astropy_1.2-2.dsc
 d816a639ef1ceadd7fe105feca4068a6 3136 python optional 
sphinx-astropy_1.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl430LkACgkQmk9WvbkO
GL04rBAAhWAXd+wnggQZZ9ZmuuF9gxF6jwMnz6HT1InOV/veG8mhYr9iYKOWqODa
kBP5zJtpX/2J0B8HK/zrWsaN6/ZL1J9zhm0+tKdg5kRYlOMwGc21gul7Zbns67DB
4HcYAPVP6MuM+zvETCFswREd2pxImqRFmjGOtWxKBUV5THy6UBg5Iii1gvVgP2I7
ERdSl21BWjnZvv06sim/qgkf7T4j5MEZ3sNYsqu2j14thvPJbxEM3ttafRfbhWhJ
wyenYaxUSj69DSlBzj0Zt5A2MWimpaE7PvAA+kqzfPeBuYQEN/e5LMHyHm3P2p1C
XQ9K9n0EfpE5Xlaj8IbG3PZ9XE4kgEr0EIgGh2d3rITcErWGjiD5c/Us9vpiYocI
OlUgqlhEpnEoqhuGbSxzigjxH51CafX2+2iy7iKgbc/L/vZGmsa0I3nz5HW1yVYb
cYU+jeh4dPVhP9dB6kayjDJLogeElGaI6Cp6KTZyEVsc2tfhHgyUqJFpfCYfAjIl
VILZ0QdrWSZfntZljXYQeQGPoCtl2LZ/DbflTN7m7UlckkxNBtO1t23RHpFBnELF
KAV5Oqgu6HCiBZ8xDsDjjyaMzL0xIUfsveip+1terHaWjNaOUAU5K6UlzpC6zgCi
iIWQp3s8l3cg7p09sL8UXXPKAr20Bixhfj6Bm3MDpa5WYN7pmDg=
=tQpZ
-END PGP SIGNATURE End Message ---

Bug#950533: upgrade fails in a chroot

[Steve McIntyre]

Package: systemd
Version: 244.1-2
Severity: serious

Hi folks,

I'm guessing this is fallout from enabling persistent journal by
default, maybe. I have a development box running multiple chroots, and
ths sid chroots are now failing to upgradw with the following errors:

Upgrading from 240-5 to 244.1-2:

...
Need to get 0 B/5987 kB of archives.
After this operation, 444 kB of additional disk space will be used.
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Setting up systemd (244.1-2) ...
[/usr/lib/tmpfiles.d/systemd-tmp.conf:11] Failed to replace specifiers: 
/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/systemd-tmp.conf:12] Failed to replace specifiers: 
/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/systemd-tmp.conf:13] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/systemd-tmp.conf:14] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/systemd-tmp.conf:22] Failed to replace specifiers: 
/var/lib/systemd/coredump/.#core*.%b*
ACL operation on "/var/log/journal" failed: No such file or directory
ACL operation on "/var/log/journal" failed: No such file or directory
Failed to re-open '/var/log/journal': No such file or directory
fchmod() of /var/log/journal failed: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 73
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

I don't have a /var/log/journal in those chroots.

-- Package-specific info:

-- System Information:
Debian Release: 10.2
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-7~deb10u2
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-1
ii  libpam-systemd  241-7~deb10u2

Versions of packages systemd suggests:
ii  policykit-10.105-25
ii  systemd-container  241-7~deb10u2

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133+deb10u1
ii  udev 241-7~deb10u2

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

-- no debconf information

Bug#950533: upgrade fails in a chroot

[Michael Biebl]

Hi Steve,

thanks for the bug report.

Am 03.02.20 um 09:59 schrieb Steve McIntyre:

> ACL operation on "/var/log/journal" failed: No such file or directory
> ACL operation on "/var/log/journal" failed: No such file or directory
> Failed to re-open '/var/log/journal': No such file or directory
> fchmod() of /var/log/journal failed: No such file or directory
> dpkg: error processing package systemd (--configure):
>  installed systemd package post-installation script subprocess returned error 
> exit status 73
> Errors were encountered while processing:
>  systemd
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> I don't have a /var/log/journal in those chroots.

The error message is misleading. postinst does create a /var/log/journal
directory. From a quick investigation with strace, the following seems
relevant

> getxattr("/proc/self/fd/4", "system.posix_acl_access", 0x7ffc2fdcc8c0, 132) = 
> -1 ENOENT (No such file or directory)
> writev(2, [{iov_base="ACL operation on \"/var/log/journ"..., iov_len=69}, 
> {iov_base="\n", iov_len=1}], 2ACL operation on "/var/log/journal" failed: No 
> such file or directory

Mounting a proc fs inside the chroot does fix the failure for me.

We run systemd-tmpfiles --create --prefix /var/log/journal
after creating the directory to ensure proper permissions and ACLs are
applied. Apparently this requires a mounted proc fs.

https://salsa.debian.org/systemd-team/systemd/blob/debian/master/src/core/chown-recursive.c#L17

A quick fix could be to guard the systemd-tmpfiles call with a

if mountpoint -q /proc ; then
...
fi





signature.asc
Description: OpenPGP digital signature

Bug#950535: iptables-restore segfaults on nat table

[Christoph Martin]

Package: iptables
Version: 1.8.2-4
Severity: grave

Dear Maintainer,

after updateing from stretch to buster ufw failed to work.

we have nat-table entries for PREROUTING and POSTROUTING . iptables-restore
segfaults on these rules. The following rules lead to the error:

*nat
-F PREROUTING
-A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194
-F PREROUTING
-F POSTROUTING
COMMIT

The version from backports: 1.8.3-2~bpo10+1 does not have this problem.
Please bring this fix to the stable release. The ufw firewall ist disabled
after this error. So I consider this a security problem

Christoph

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (700, 'stable-updates'), (700, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages iptables depends on:
ii  libc62.28-10
ii  libip4tc01.8.2-4
ii  libip6tc01.8.2-4
ii  libiptc0 1.8.2-4
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnfnetlink01.0.1-3+b1
ii  libnftnl11   1.1.2-2
ii  libxtables12 1.8.2-4

Versions of packages iptables recommends:
ii  nftables  0.9.0-2

Versions of packages iptables suggests:
ii  kmod  26-1



signature.asc
Description: OpenPGP digital signature

Processed: retitle 950533 to upgrade fails in a chroot without mounted /proc

[Debian Bug Tracking System]

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

> retitle 950533 upgrade fails in a chroot without mounted /proc
Bug #950533 [systemd] upgrade fails in a chroot
Changed Bug title to 'upgrade fails in a chroot without mounted /proc' from 
'upgrade fails in a chroot'.
> thanks
Stopping processing here.

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

Bug#949824: [DRE-maint] Bug#949824: schleuder: tests fail with ruby-sqlite 1.4.2-1

[Georg Faerber]

Control: Tags -1 + confirmed upstream
Control: Forwarded -1 https://0xacab.org/schleuder/schleuder/issues/453

Hi,

On 20-01-25 09:58:22, Antonio Terceiro wrote:
> I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its
> tests on the dependency resolution step.
> 
> [...]
> 
> I tried hacking it locally, and just changing ~> to >= makes it work,
> and all the tests pass. Please consider making the dependency check
> less strict.

Thanks for reporting -- confirmed, will be fixed upstream.

Cheers,
Georg

Bug#949434: marked as done (licensecheck: autopkgtest failure: Can't locate App/Licensecheck.pm in @INC)

[Debian Bug Tracking System]

Your message dated Mon, 3 Feb 2020 11:30:19 +0100
with message-id <20200203103019.ga23...@jadzia.comodo.priv.at>
and subject line Re: Bug#949434: licensecheck: autopkgtest failure: Can't 
locate App/Licensecheck.pm in @INC
has caused the Debian Bug report #949434,
regarding licensecheck: autopkgtest failure: Can't locate App/Licensecheck.pm 
in @INC
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.)


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

Dear maintainers,

With a recent upload of licensecheck you added an autopkgtest, awesome.
However, it fails. 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=licensecheck

https://ci.debian.net/data/autopkgtest/testing/amd64/l/licensecheck/3886815/log.gz

autopkgtest [04:40:01]: test autodep8-perl-build-deps:
/usr/share/pkg-perl-autopkgtest/runner build-deps
autopkgtest [04:40:01]: test autodep8-perl-build-deps:
[---
t/OSI.t ...
Can't locate App/Licensecheck.pm in @INC (you may need to install the
App::Licensecheck module) (@INC contains:
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO/blib/lib
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO/blib/arch
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0
/usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30
/usr/share/perl/5.30 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at t/OSI.t line 4.
BEGIN failed--compilation aborted at t/OSI.t line 4.
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run
t/SPDX.t ..
Can't locate App/Licensecheck.pm in @INC (you may need to install the
App::Licensecheck module) (@INC contains:
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO/blib/lib
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO/blib/arch
/tmp/autopkgtest-lxc.3dq2oqhz/downtmp/autopkgtest_tmp/smokeVoK0OO
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0
/usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30
/usr/share/perl/5.30 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at t/SPDX.t line 4.
BEGIN failed--compilation aborted at t/SPDX.t line 4.
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run
t/Software-License.t ..
1..29
not ok 1 - Script bin/licensecheck runs

# Failed test 'Script bin/licensecheck runs'
# at t/Software-License.t line 65.
# 2 - Can't open perl script "bin/licensecheck": No such file or directory
# Looks like you planned 29 tests but ran 1.
# Looks like you failed 1 test of 1 run.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 29/29 subtests
t/devscripts.t 
1..14
# Subtest: copyright declared on 2 lines; t/devscripts/bsd-regents.c
not ok 1 - bin/licensecheck -m --copyright t/devscripts/bsd-regents.c

# Failed test 'bin/licensecheck -m --copyright
t/devscripts/bsd-regents.c'
# at t/devscripts.t line 15.
# 2 - Can't open perl script "bin/licensecheck": No such file or
directory
not ok 2 - stdout matches

# Failed test 'stdout matches'
# at t/devscripts.t line 16.
# The output
# does not match
#   t/devscripts/bsd-regents.c  (?^:BSD (?:3-clause "New" or
"Revised" License|\(3 clause\)) 1987, 1993.*1994 The Regents of the
University of California.)
not ok 3 - stderr matches

# Failed test 'stderr matches'
# at t/devscripts.t line 19.
# The output
#   Can't open perl script "bin/licensecheck": No such file or directory
# does not match
1..3
# Looks like you failed 3 tests of 3.
not ok 1 - copyright declared on 2 lines; t/devscripts/bsd-regents.c

#   Failed test 'copyright declared on 2 lines; t/devscripts/bsd-regents.c'
#   at t/devscripts.t line 22.
# Subtest: copyright declared on 3 lines; t/devscripts/texinfo.tex
not ok 1 - bin/licensecheck -m --copyright t/devscripts/texinfo.tex

# Failed test

Processed: Re: [DRE-maint] Bug#949824: schleuder: tests fail with ruby-sqlite 1.4.2-1

[Debian Bug Tracking System]

Processing control commands:

> Tags -1 + confirmed upstream
Bug #949824 [src:schleuder] schleuder: tests fail with ruby-sqlite 1.4.2-1
Added tag(s) confirmed and upstream.
> Forwarded -1 https://0xacab.org/schleuder/schleuder/issues/453
Bug #949824 [src:schleuder] schleuder: tests fail with ruby-sqlite 1.4.2-1
Set Bug forwarded-to-address to 
'https://0xacab.org/schleuder/schleuder/issues/453'.

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

Bug#950228: marked as pending in ruby-kaminari

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-kaminari/commit/c320373d57d14ea88ba3866384fab3c97634fff9


Drop explicit debian/tests/control

Closes: #950228


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950228

Processed: Bug#950228 marked as pending in ruby-kaminari

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950228 [src:ruby-kaminari] ruby-kaminari: autopkgtest needs update for new 
version of gem2deb
Added tag(s) pending.

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

Bug#950228: marked as done (ruby-kaminari: autopkgtest needs update for new version of gem2deb)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 11:42:30 +
with message-id 
and subject line Bug#950228: fixed in ruby-kaminari 1.0.1-5
has caused the Debian Bug report #950228,
regarding ruby-kaminari: autopkgtest needs update for new version of gem2deb
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.)


-- 
950228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kaminari
Version: 1.0.1-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gem2deb

Dear maintainers,

With a recent upload of gem2deb the autopkgtest of ruby-kaminari fails
in testing when that autopkgtest is run with the binary packages of
gem2deb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
gem2debfrom testing1.0.3
ruby-kaminari  from testing1.0.1-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. The cause of
this is that gem2deb started to exit with code 77 to indicate that there
is no test to run. This is meant to be used in conjunction with the
skippable restriction, to avoid giving the wrong information to the
migration software. Please add the skippable restriction to your
package, or better, add a real test. Your second test also doesn't seem
to test the package to any substantial amount, please consider tagging
it as superficial.

Currently this regression is blocking the migration of gem2deb to
testing [1]. Of course, gem2deb shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
gem2deb was intended and your package needs to update to the new situation.

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=gem2deb

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-kaminari/4144033/log.gz

autopkgtest [03:10:52]: test command1: gem2deb-test-runner --autopkgtest
2>&1
autopkgtest [03:10:52]: test command1: [---

┌──┐
│ Run tests for ruby2.5: no test suite!
  │
└──┘

autopkgtest [03:10:53]: test command1: ---]
autopkgtest [03:10:53]: test command1:  - - - - - - - - - - results - -
- - - - - - - -
command1 FAIL non-zero exit status 77



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-kaminari
Source-Version: 1.0.1-5

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-kaminari 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 12:14:56 +0100
Source: ruby-kaminari
Architecture: source
Version: 1.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Closes: 950228
Changes:
 ruby-kaminari (1.0.1-5) unstable; urgency=medium
 .
   * Team upload
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Antonio Terceiro ]
   * Drop explicit debian/tests/control, and let autodep8 handle tests
 (Closes: #950228)
   * Add debian/patches/0001-gemspecs-drop-git-usage.patch (does what it says
 on the tin)
   * Packaging updates from a new run of gem2deb:
 - Bump debhelper compat to 12 and drop debian/compat
 - update homepage from upstream metadata
 - add Rules-Requires-Root: no
 - use ${ruby:Depends} for dependencies
 - Bump Standards-Version to 4.4.0 (no other changes needed)
 - Drop ${shlibs:Depends} as it is pointle

Bug#950540: System hangs at startup

[Dietz Proepper]

Package: haveged
Version: 1.9.8-2
Severity: critical

Hi,

after updating to haveged 1.9.8-3, my system hangs during boot.

The console output looks similar to the one in bug #950418.

Downgrading to 1.9.8-2 fixes the problem.

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

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

Versions of packages haveged depends on:
ii  init-system-helpers  1.57
ii  libc62.29-9
ii  libhavege2   1.9.8-3
ii  lsb-base 11.1.0

haveged recommends no packages.

Versions of packages haveged suggests:
ii  apparmor  2.13.3-7

-- no debconf information

Bug#950230: marked as done (gitlab-shell: autopkgtest needs update for new version of gem2deb)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 12:04:29 +
with message-id 
and subject line Bug#950230: fixed in gitlab-shell 10.3.0+debian-3.1
has caused the Debian Bug report #950230,
regarding gitlab-shell: autopkgtest needs update for new version of gem2deb
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.)


-- 
950230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab-shell
Version: 10.3.0+debian-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gem2deb

Dear maintainers,

With a recent upload of gem2deb the autopkgtest of gitlab-shell fails in
testing when that autopkgtest is run with the binary packages of gem2deb
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
gem2debfrom testing1.0.3
gitlab-shell   from testing10.3.0+debian-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. The cause of
this is that gem2deb started to exit with code 77 to indicate that there
is no test to run. This is meant to be used in conjunction with the
skippable restriction, to avoid giving the wrong information to the
migration software. Please add the skippable restriction to your
package, or better, add a real test.

Currently this regression is blocking the migration of gem2deb to
testing [1]. Of course, gem2deb shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
gem2deb was intended and your package needs to update to the new situation.

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=gem2deb

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gitlab-shell/4145589/log.gz

autopkgtest [08:10:08]: test command1: gem2deb-test-runner --autopkgtest
2>&1
autopkgtest [08:10:08]: test command1: [---

┌──┐
│ Run tests for ruby2.5: no test suite!
  │
└──┘

autopkgtest [08:10:09]: test command1: ---]
autopkgtest [08:10:09]: test command1:  - - - - - - - - - - results - -
- - - - - - - -
command1 FAIL non-zero exit status 77



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gitlab-shell
Source-Version: 10.3.0+debian-3.1

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated gitlab-shell 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 12:34:07 +0100
Source: gitlab-shell
Architecture: source
Version: 10.3.0+debian-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Closes: 950230
Changes:
 gitlab-shell (10.3.0+debian-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop debian/tests/control that uses gem2deb-test-runner since this is not
 a Ruby package (Closes: #950230)
Checksums-Sha1:
 79681d412b24397b98eb246ed7783f5934cbdca2 2517 
gitlab-shell_10.3.0+debian-3.1.dsc
 18aba61edfb125b8ab0e1b81b7489b388612aced 5320 
gitlab-shell_10.3.0+debian-3.1.debian.tar.xz
 82bd7a9727a6479e816684336598f036382a229b 6334 
gitlab-shell_10.3.0+debian-3.1_source.buildinfo
Checksums-Sha256:
 9e9afafd6d0fb7fa5b51cf3f2c1aa6c3a8b21caa064f7ea7c82f12313db7c74d 2517 
gitlab-shell_10.3.0+debian-3.1.dsc
 fd81440a80d0785f0b4934c2a0af02b3a74607097530fbf7f819248c09c9 5320 
gitlab-shell_10.3.0+debian-3.1.debian.tar.xz
 f7f6065d03b2025aed0d86cb88

Bug#950229: marked as done (ruby-flipper: autopkgtest needs update for new version of gem2deb)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 12:05:34 +
with message-id 
and subject line Bug#950229: fixed in ruby-flipper 0.17.1-5
has caused the Debian Bug report #950229,
regarding ruby-flipper: autopkgtest needs update for new version of gem2deb
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.)


-- 
950229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-flipper
Version: 0.17.1-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gem2deb

Dear maintainers,

With a recent upload of gem2deb the autopkgtest of ruby-flipper fails in
testing when that autopkgtest is run with the binary packages of gem2deb
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
gem2debfrom testing1.0.3
ruby-flipper   from testing0.17.1-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.  The cause of
this is that gem2deb started to exit with code 77 to indicate that there
is no test to run. This is meant to be used in conjunction with the
skippable restriction, to avoid giving the wrong information to the
migration software. Please add the skippable restriction to your
package, or better, add a real test.

Currently this regression is blocking the migration of gem2deb to
testing [1]. Of course, gem2deb shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
gem2deb was intended and your package needs to update to the new situation.

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=gem2deb

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-flipper/4144032/log.gz

autopkgtest [03:10:21]: test command1: ln -s ../flipper.gemspec
debian/gemspec && gem2deb-test-runner --autopkgtest --check-dependencies
2>&1
autopkgtest [03:10:21]: test command1: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5
  │
└──┘

GEM_PATH= ruby2.5 -e gem\ \"flipper\"

┌──┐
│ Run tests for ruby2.5: no test suite!
  │
└──┘

autopkgtest [03:10:21]: test command1: ---]
autopkgtest [03:10:22]: test command1:  - - - - - - - - - - results - -
- - - - - - - -
command1 FAIL non-zero exit status 77



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-flipper
Source-Version: 0.17.1-5

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-flipper 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 12:57:28 +0100
Source: ruby-flipper
Architecture: source
Version: 0.17.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Closes: 950229
Changes:
 ruby-flipper (0.17.1-5) unstable; urgency=medium
 .
   * Team upload.
   * debian/tests/control: add skippable restriction to handle new gem2deb
 behavior (Closes: #950229)
Checksums-Sha1:
 ca2abcf5a1a286ed44add9cb5dbfb3812fce88e5 2117 ruby-flipper_0.17.1-5.dsc
 96ae4b9b7892654a423b7f573b63a1d5d09a3d2c 4504 
ruby-flipper_0.17.1-5.debian.tar.xz
 98c2eca16e0344689ca1a9daded83f26c7cc8295 13180 
ruby-flipper_0.17.1-5_source.buildinfo
Checksums-Sha256:
 6a0ceec73e85054d467

Bug#949824: marked as done (schleuder: tests fail with ruby-sqlite 1.4.2-1)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 12:06:22 +
with message-id 
and subject line Bug#949824: fixed in schleuder 3.4.1-3
has caused the Debian Bug report #949824,
regarding schleuder: tests fail with ruby-sqlite 1.4.2-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.)


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

Hi,

I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its
tests on the dependency resolution step.

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

Invalid gemspec in [schleuder.gemspec]: No such file or directory - git
GEM_PATH= ruby2.5 -e gem\ \"schleuder\"
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not find 
'sqlite3' (~> 1.3.6) - did find: [sqlite3-1.4.2] (Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0',
 execute `gem env` for more information
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1469:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `each'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in 
`activate_dependencies'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1440:in `activate'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in 
`synchronize'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
from -e:1:in `'


I tried hacking it locally, and just changing ~> to >= makes it work,
and all the tests pass. Please consider making the dependency check less
strict.


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: schleuder
Source-Version: 3.4.1-3

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

Debian distribution maintenance software
pp.
Georg Faerber  (supplier of updated schleuder package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 11:07:21 +
Source: schleuder
Architecture: source
Version: 3.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Georg Faerber 
Closes: 949824
Changes:
 schleuder (3.4.1-3) unstable; urgency=medium
 .
   * debian/control:
 - Bump Standards-Version to 4.5.0, no changes required.
   * debian/patches:
 - Add patch to bump SQLite dependency in gemspec. (Closes: #949824)
 - Refresh patch to update sinatra to remove fuzz.
Checksums-Sha1:
 a3b3a55798a0f31d99a508bcf772b24ed654446a 1995 schleuder_3.4.1-3.dsc
 f7fdae7fb29640634e27dee9fa162ae2c76a21d5 201807 schleuder_3.4.1.orig.tar.gz
 2fb8c95e5b4354fbd8faf63eeac55dda7e7e538c 862 schleuder_3.4.1.orig.tar.gz.asc
 f8d9907fbb207747cefe17c41dce480ee24c198d 27744 schleuder_3.4.1-3.debian.tar.xz
 fe92facb4c3331a451ae84ade47042ddcf8dc934 9332 schleuder_3.4.1-3_amd64.buildinfo
Checksums-Sha256:
 edeb9899ce3be6607126689418fa38b3bd4073af891e58711b3d52f18857b32b 1995 
schleuder_3.4.1-3.dsc

Bug#950545: FTBFS against opencv 4.2.0

[Mo Zhou]

Source: eviacam
Version: 2.1.4-1
Severity: serious

Dear maintainer,

eviacam FTBFS against the latest version of OpenCV:
https://buildd.debian.org/status/package.php?p=eviacam&suite=sid
https://buildd.debian.org/status/fetch.php?pkg=eviacam&arch=amd64&ver=2.1.4-1%2Bb1&stamp=1580642132&raw=0

which looks due an API change at the first glance.


crvnormroi.cpp:449:35: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  449 |  SetP1ResizeInteger (pImg->GetSize(), x, y);
  |  ~^~
  |   |
  |   cv::Size {aka cv::Size_}
crvnormroi.cpp:359:50: note:   initializing argument 1 of ‘void 
CNormROI::SetP1ResizeInteger(const CvSize&, int, int)’
  359 | void CNormROI::SetP1ResizeInteger (const CvSize& size, const int x, 
const int y)
  |~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetP1MoveImg(const 
CIplImage*, int, int)’:
crvnormroi.cpp:457:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  457 |  SetP1MoveInteger (pImg->GetSize(), x, y);
  |~^~
  | |
  | cv::Size {aka cv::Size_}
crvnormroi.cpp:369:48: note:   initializing argument 1 of ‘void 
CNormROI::SetP1MoveInteger(const CvSize&, int, int)’
  369 | void CNormROI::SetP1MoveInteger (const CvSize& size, const int x, const 
int y)
  |  ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetP2ResizeImg(const 
CIplImage*, int, int)’:
crvnormroi.cpp:465:35: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  465 |  SetP2ResizeInteger (pImg->GetSize(), x, y);
  |  ~^~
  |   |
  |   cv::Size {aka cv::Size_}
crvnormroi.cpp:379:50: note:   initializing argument 1 of ‘void 
CNormROI::SetP2ResizeInteger(const CvSize&, int, int)’
  379 | void CNormROI::SetP2ResizeInteger (const CvSize& size, const int x, 
const int y)
  |~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetCenterImg(const 
CIplImage*, int, int)’:
crvnormroi.cpp:473:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  473 |  SetCenterInteger (pImg->GetSize(), x, y);
  |~^~
  | |
  | cv::Size {aka cv::Size_}
crvnormroi.cpp:389:48: note:   initializing argument 1 of ‘void 
CNormROI::SetCenterInteger(const CvSize&, int, int)’
  389 | void CNormROI::SetCenterInteger (const CvSize& size, const int x, const 
int y)
  |  ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::GetCenterImg(const 
CIplImage*, int&, int&)’:
crvnormroi.cpp:481:33: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  481 |  GetCenterInteger (pImg->GetSize(), x, y);
  |~^~
  | |
  | cv::Size {aka cv::Size_}
crvnormroi.cpp:398:48: note:   initializing argument 1 of ‘void 
CNormROI::GetCenterInteger(const CvSize&, int&, int&)’
  398 | void CNormROI::GetCenterInteger (const CvSize& size, int& x, int& y)
  |  ~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::SetSizeImg(const CIplImage*, 
int, int)’:
crvnormroi.cpp:489:31: error: cannot convert ‘cv::Size’ {aka ‘cv::Size_’} 
to ‘const CvSize&’
  489 |  SetSizeInteger (pImg->GetSize(), width, height);
  |  ~^~
  |   |
  |   cv::Size {aka cv::Size_}
crvnormroi.cpp:408:46: note:   initializing argument 1 of ‘void 
CNormROI::SetSizeInteger(const CvSize&, int, int)’
  408 | void CNormROI::SetSizeInteger (const CvSize& size, const int width, 
const int height)
  |~~^~~~
crvnormroi.cpp: In member function ‘void CNormROI::GetBoxImg(const CIplImage*, 
int&, int&, int&, int&)’:
crvnormroi.cpp:497:53: error: no matching function for call to 
‘CNormROI::GetBoxInteger(cv::Size, int&, int&, int&, int&)’
  497 |  GetBoxInteger (pImg->GetSize(), x, y, width, height);
  | ^
crvnormroi.cpp:418:6: note: candidate: ‘void CNormROI::GetBoxInteger(const 
CvSize&, int&, int&, int&, int&)’
  418 | void CNormROI::GetBoxInteger (const CvSize& size, int& x, int& y, int& 
width, int& height)
  |  ^~~~
crvnormroi.cpp:418:45: note:   no known conversion for argument 1 from 
‘cv::Size’ {aka ‘cv::Size_’} to ‘const CvSize&’
  418 | void CNormROI::GetBoxInteger (const CvSize& size, int& x, int& y, int& 

Bug#854596: marked as done (fontmatrix: uninstallable -at least under stretch, fontmatrix : Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided by any available package)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 13:29:12 +0100
with message-id <0383080a8c0d8307cd6c912e7bf65...@phys.ethz.ch>
and subject line i don't have such an old system, but with sid it's installable 
again
has caused the Debian Bug report #854596,
regarding fontmatrix: uninstallable -at least under stretch, fontmatrix : 
Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided 
by any available package
to be marked as done.

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

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


-- 
854596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontmatrix
Version: 0.6.0+svn20110930-1.1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (101, 'testing'), (10, 'experimental'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---

Version: 0.6.1+git20190730-1

This has been fixed while reintroduction of fontmatrix to Debian.--- End Message ---

Bug#799311: marked as done (fontmatrix: FTBFS: error: invalid new-expression of abstract class type 'IcuFontImpl')

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 13:29:12 +0100
with message-id <0383080a8c0d8307cd6c912e7bf65...@phys.ethz.ch>
and subject line i don't have such an old system, but with sid it's installable 
again
has caused the Debian Bug report #854596,
regarding fontmatrix: FTBFS: error: invalid new-expression of abstract class 
type 'IcuFontImpl'
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.)


-- 
854596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontmatrix
Version: 0.6.0+svn20110930-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

fontmatrix fails to build from source in unstable/amd64:

  [..]

  [ 74%] Building CXX object
  src/CMakeFiles/fontmatrix.dir/fmshaper.cpp.o
  [ 74%] Building CXX object
  src/CMakeFiles/fontmatrix.dir/icushaper.cpp.o
  /tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.cpp: In
  constructor 'IcuShaper::IcuShaper(FMOtf*, QString)':
  /tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.cpp:28:34:
  error: invalid new-expression of abstract class type 'IcuFontImpl'
icuFont = new IcuFontImpl ( otf );
^
  In file included from
  /tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.cpp:14:0:
  /tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.h:23:7: note:  
  because the following virtual functions are pure within 'IcuFontImpl':
   class IcuFontImpl : public LEFontInstance
 ^
  In file included from
  /tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.h:20:0,
   from
   
/tmp/buildd/fontmatrix-0.6.0+svn20110930/src/icushaper.cpp:14:
  /usr/include/x86_64-linux-gnu/layout/LEFontInstance.h:165:25: note:   
   virtual const void* icu_55::LEFontInstance::getFontTable(LETag,
  size_t&) const
   virtual const void* getFontTable(LETag tableTag, size_t &length)
   const = 0;
   ^
  src/CMakeFiles/fontmatrix.dir/build.make:2857: recipe for target
  'src/CMakeFiles/fontmatrix.dir/icushaper.cpp.o' failed
  make[3]: *** [src/CMakeFiles/fontmatrix.dir/icushaper.cpp.o] Error 1
  make[3]: Leaving directory
  '/tmp/buildd/fontmatrix-0.6.0+svn20110930/debian/build'

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/fontmatrix_0.6.0+svn20110930-1.1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Sep 17 05:13:05 GMT+12 2015
I: pbuilder-time-stamp: 1442509985
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 5), libfreetype6-dev, libqt4-dev (>= 4.3), cmake, 
libfontconfig1-dev, libm17n-dev, libicu-dev, python-all-dev, libpuzzle-dev, 
python-qt4, libqtwebkit-dev, libqt4-opengl-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20254 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on libfreetype6-dev; however:
  Package libfreetype6-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libqt4-dev (>= 4.3); however:
  Package libqt4-dev is not installed.
 pbuilder-satisfydepends-dummy depends on cmake; howe

Processed: transition: opencv

[Debian Bug Tracking System]

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

> block 948638 by 922583 950545
Bug #948638 [release.debian.org] transition: opencv
948638 was blocked by: 950310
948638 was not blocking any bugs.
Added blocking bug(s) of 948638: 950545 and 922583
> tags 950545 + ftbfs
Bug #950545 [src:eviacam] FTBFS against opencv 4.2.0
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Follow-up

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Severity set to 'critical' from 'important'

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

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[dimitris]

Package: libgcc1
Version: 1:9.2.1-25
Severity: grave
Justification: renders package unusable

hey,

after upgrading some latest packages on sid, i can no longer unlock luks
partition and boot. message:

"Please unlock disk rootfs:
libgcc_s.so.1 must be installed for pthread-cancel to work
Aborted"

so i think it's libgcc1 related.
had to chroot to disk from liveusb, downgrade some packages & finally use a
different kernel to boot.
noticed that update-initramfs with libgcc1 1:9.2.1-25 adds file : "Adding
binary /lib/x86_64-linux-gnu/libgcc_s.so.1" , while libgcc1 version
1:10-20200202-1 doesn't add any libgcc_s.so.1.

also, version from testing includes file /lib/x86_64-linux-gnu/libgcc_s.so.1,
while sid version uses /lib/libgcc_s.so.1 . libgcc-s1 also includes this file :
/usr/lib/x86_64-linux-gnu/libgcc_s.so.1

let me know if you need anymore info.

thanks,
d.



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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libgcc1 depends on:
ii  gcc-9-base  9.2.1-25
ii  libc6   2.29-9

libgcc1 recommends no packages.

libgcc1 suggests no packages.

-- no debconf information

Bug#950554: apertium-eo-es FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-eo-es
Version: 1:0.9.1~r60655-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-es.html

...
   dh_auto_build -O--fail-missing
make -j15
make[1]: Entering directory '/build/1st/apertium-eo-es-0.9.1~r60655'
apertium-validate-dictionary apertium-eo-es.es.dix
apertium-validate-dictionary apertium-eo-es.eo-es.dix
apertium-validate-dictionary apertium-eo-es.eo.dix
apertium-validate-dictionary apertium-eo-es.post-eo.dix
cg-comp apertium-eo-es.es-eo.rlx  es-eo.rlx.bin
apertium-validate-transfer apertium-eo-es.es-eo.t1x
apertium-validate-interchunk apertium-eo-es.es-eo.antaux1_t2x
apertium-validate-interchunk apertium-eo-es.es-eo.antaux2_t2x
apertium-validate-interchunk apertium-eo-es.es-eo.antaux3_t2x
apertium-validate-interchunk apertium-eo-es.es-eo.antaux4_t2x
apertium-validate-interchunk apertium-eo-es.es-eo.antaux5_t2x
apertium-eo-es.es-eo.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 277 at 1 Verb BARRIER Cnj_Rel.
apertium-eo-es.es-eo.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 278 at 1 Verb BARRIER Cnj_Rel.
apertium-eo-es.es-eo.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 279 at 1 Verb BARRIER Cnj_Rel.
apertium-validate-interchunk apertium-eo-es.es-eo.t2x
apertium-validate-postchunk apertium-eo-es.es-eo.t3x
lt-comp lr apertium-eo-es.post-eo.dix es-eo.autopgen.bin
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 584 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 585 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 586 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 587 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 588 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 589 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 590 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 591 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 592 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 593 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 594 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 595 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 596 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 597 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 598 after 
previous rule!
apertium-eo-es.es-eo.rlx: Warning: Expected closing ; on line 604 after 
previous rule!
apertium-gen-modes modes.xml
Sections: 1, Rules: 282, Sets: 178, Tags: 476
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-eo-es.es-eo.antaux3_t2x 
es-eo.antaux3_t2x.bin
apertium-preprocess-transfer apertium-eo-es.es-eo.antaux4_t2x 
es-eo.antaux4_t2x.bin
apertium-preprocess-transfer apertium-eo-es.es-eo.antaux1_t2x 
es-eo.antaux1_t2x.bin
apertium-preprocess-transfer apertium-eo-es.es-eo.antaux2_t2x 
es-eo.antaux2_t2x.bin
apertium-preprocess-transfer apertium-eo-es.es-eo.antaux5_t2x 
es-eo.antaux5_t2x.bin
apertium-preprocess-transfer apertium-eo-es.es-eo.t3x es-eo.t3x.bin
mkdir: cannot create directory ‘/build/1st/apertium-eo-es-0.9.1~r60655/modes’: 
File exists
main@standard 29 45
apertium-preprocess-transfer apertium-eo-es.es-eo.t2x es-eo.t2x.bin
cp *.mode modes/
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[1]: *** [Makefile:700: es-eo.mode] Error 1

Bug#950557: apertium-en-gl FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-en-gl
Version: 0.5.2~r57551-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-en-gl.html

...
make -j15
make[1]: Entering directory '/build/1st/apertium-en-gl-0.5.2~r57551'
make  all-am
make[2]: Entering directory '/build/1st/apertium-en-gl-0.5.2~r57551'
apertium-validate-dictionary apertium-en-gl.gl.dix
apertium-validate-dictionary apertium-en-gl.en-gl.dix
apertium-validate-dictionary apertium-en-gl.en-gl.dix
apertium-validate-dictionary apertium-en-gl.gl.dix
apertium-validate-dictionary apertium-en-gl.post-gl.dix
apertium-validate-dictionary apertium-en-gl.post-en.dix
apertium-validate-transfer apertium-en-gl.en-gl.t1x
apertium-validate-interchunk apertium-en-gl.en-gl.t2x
apertium-validate-postchunk apertium-en-gl.en-gl.t3x
apertium-validate-transfer apertium-en-gl.gl-en.t1x
lt-comp lr apertium-en-gl.post-en.dix gl-en.autopgen.bin
apertium-validate-interchunk apertium-en-gl.gl-en.t2x
apertium-validate-postchunk apertium-en-gl.gl-en.t3x
apertium-preprocess-transfer apertium-en-gl.en-gl.t2x en-gl.t2x.bin
apertium-gen-modes modes.xml
main@standard 29 45
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-en-gl.gl-en.t3x gl-en.t3x.bin
lt-comp lr apertium-en-gl.post-gl.dix en-gl.autopgen.bin
apertium-preprocess-transfer apertium-en-gl.en-gl.t3x en-gl.t3x.bin
Warning (743): Paths to rule 5 blocked by rule 3.
Warning (743): Paths to rule 5 blocked by rule 4.
apertium-preprocess-transfer apertium-en-gl.gl-en.t2x gl-en.t2x.bin
main@standard 209 543
apertium-preprocess-transfer apertium-en-gl.gl-en.t1x gl-en.t1x.bin
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:818: gl-en.mode] Error 1

Bug#950552: apertium-bel-rus FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-bel-rus
Version: 0.2.0~r81186-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-bel-rus.html

...
make -j1
make[1]: Entering directory '/build/1st/apertium-bel-rus-0.2.0~r81186'
/bin/mkdir -p .deps
touch .deps/.d
cp /usr/share/apertium/apertium-bel/bel.automorf.bin .deps/bel.automorf.bin
apertium-validate-dictionary apertium-bel-rus.bel-rus.dix
lt-comp lr apertium-bel-rus.bel-rus.dix bel-rus.autobil.bin
main@standard 64657 102821
lt-trim .deps/bel.automorf.bin bel-rus.autobil.bin bel-rus.automorf.bin
main@standard 87330 243173
cp /usr/share/apertium/apertium-bel/bel.prob bel-rus.prob
cg-comp /usr/share/apertium/apertium-bel/apertium-bel.bel.rlx bel-rus.rlx.bin
Sections: 1, Rules: 1, Sets: 6, Tags: 71
lrx-comp apertium-bel-rus.bel-rus.lrx bel-rus.autolex.bin
1: 28@29
cp /usr/share/apertium/apertium-rus/rus.autogen.bin bel-rus.autogen.bin
cp /usr/share/apertium/apertium-rus/rus.autopgen.bin bel-rus.autopgen.bin
apertium-validate-transfer apertium-bel-rus.bel-rus.t1x
apertium-preprocess-transfer apertium-bel-rus.bel-rus.t1x bel-rus.t1x.bin
apertium-validate-interchunk apertium-bel-rus.bel-rus.t2x
apertium-preprocess-transfer apertium-bel-rus.bel-rus.t2x bel-rus.t2x.bin
apertium-validate-postchunk apertium-bel-rus.bel-rus.t3x
apertium-preprocess-transfer apertium-bel-rus.bel-rus.t3x bel-rus.t3x.bin
cp /usr/share/apertium/apertium-rus/rus.automorf.bin .deps/rus.automorf.bin
apertium-validate-dictionary apertium-bel-rus.bel-rus.dix
lt-comp rl apertium-bel-rus.bel-rus.dix rus-bel.autobil.bin
main@standard 66411 104765
lt-trim .deps/rus.automorf.bin rus-bel.autobil.bin rus-bel.automorf.bin
final@inconditional 39 342
gci@standard 27159 57718
main@standard 70971 145733
multiwords@standard 1641 1974
Warning: section had no final state after trimming! Skipping it ...
cp /usr/share/apertium/apertium-rus/rus.prob rus-bel.prob
cg-comp /usr/share/apertium/apertium-rus/apertium-rus.rus.rlx rus-bel.rlx.bin
Sections: 4, Rules: 309, Sets: 441, Tags: 572
47 rules cannot be skipped by index.
lrx-comp apertium-bel-rus.rus-bel.lrx rus-bel.autolex.bin
Error: empty set of final states
make[1]: *** [Makefile:804: rus-bel.autolex.bin] Error 1

Bug#950556: initramfs-tools hook fails to copy libgcc_s.so.1

[Felix Zielcke]

Package: btrfs-progs
Version: 5.4.1-1
Severity: critical

My system didn't boot anymore. initramfs complained that for
phread_cancel you need libgcc_s.so installed.

The btrfs hook for initramfs expects it to be in the same dir as libc6.
But that's not true anymore since libgcc1 has been updated from gcc-9 to gcc-10.

libgcc1 in bullseye (version: 1:9.2.1-25) has it in /lib/x86_64-linux-gnu/
In sid (version: 1:10-20200202-1) it's directly in /lib/
or alternatetively in the new libgcc-s1 it is in /usr/lib/x86_64-linux-gnu/

quick&dirty solution:

--- btrfs.old   2020-02-03 14:39:26.409270708 +0100
+++ btrfs   2020-02-03 14:39:46.602089060 +0100
@@ -25,8 +25,8 @@
then
copy_exec /sbin/fsck.btrfs /sbin
fi
-   LIBC_DIR=$(ldd /bin/btrfs | sed -nr 's#.* => 
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
-   find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read 
so; do
+#  LIBC_DIR=$(ldd /bin/btrfs | sed -nr 's#.* => 
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
+   find -L "/lib" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; 
do
copy_exec "$so"
done
 fi

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

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

Versions of packages btrfs-progs depends on:
ii  libblkid12.34-0.1
ii  libc62.29-9
ii  libcom-err2  1.45.5-2
ii  libext2fs2   1.45.5-2
ii  liblzo2-22.10-2
ii  libuuid1 2.34-0.1
ii  libzstd1 1.4.4+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-1.2

btrfs-progs recommends no packages.

Versions of packages btrfs-progs suggests:
pn  duperemove  

-- no debconf information

Bug#950555: apertium-hbs-mkd FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-hbs-mkd
Version: 0.1.0~r76450-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-hbs-mkd.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-hbs-mkd-0.1.0~r76450'
make  all-am
make[2]: Entering directory '/build/1st/apertium-hbs-mkd-0.1.0~r76450'
xsltproc --stringparam alt hbs --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs.dix 
apertium-validate-dictionary apertium-hbs-mkd.mkd.dix
xsltproc --stringparam alt hbs_BS --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_BS.dix
xsltproc --stringparam alt hbs_HR --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_HR.dix
xsltproc --stringparam alt hbs_SR --stringparam var ek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_SR.dix
apertium-validate-dictionary apertium-hbs-mkd.hbs-mkd.dix
apertium-validate-dictionary apertium-hbs-mkd.hbs-mkd.dix
apertium-validate-dictionary apertium-hbs-mkd.mkd.dix
cg-comp apertium-hbs-mkd.hbs-mkd.rlx hbs-mkd.rlx.bin
cg-comp apertium-hbs-mkd.mkd-hbs.rlx mkd-hbs.rlx.bin
lrx-comp apertium-hbs-mkd.hbs-mkd.lrx hbs-mkd.autolex.bin
lrx-comp apertium-hbs-mkd.mkd-hbs.lrx mkd-hbs.autolex.bin
apertium-validate-transfer apertium-hbs-mkd.hbs-mkd.t1x
apertium-validate-interchunk apertium-hbs-mkd.hbs-mkd.t2x
apertium-validate-postchunk apertium-hbs-mkd.hbs-mkd.t3x
apertium-validate-transfer apertium-hbs-mkd.mkd-hbs.t1x
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 191 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 194 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 214 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 216 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 216 at 1 VBSer + Clt BARRIER V-FIN OR BOS.
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 216 at 1 VBSer + Clt BARRIER V-FIN OR EOS.
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 218 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Barriers only make sense for scanning or 
self tests on line 241 at 1 Lp + $$NUMBER + $$GENDER BARRIER S-BOUNDARY.
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 255 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 258 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 260 after 
previous rule!
1: 31@31
apertium-validate-interchunk apertium-hbs-mkd.mkd-hbs.t2x
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 319 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 354 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 355 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 356 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 358 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 359 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 361 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 362 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 365 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 386 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 415 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 454 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 592 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 593 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 594 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 597 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 598 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 599 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 600 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 601 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 602 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 603 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 604 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: Expected closing ; on line 606 after 
previous rule!
apertium-hbs-mkd.hbs-mkd.rlx: Warning: 

Bug#949132: marked as done (cdftools: FTBFS (LaTeX Error: File 'infwarerr.sty' not found.))

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 13:49:19 +
with message-id 
and subject line Bug#949132: fixed in cdftools 3.0.2-4
has caused the Debian Bug report #949132,
regarding cdftools: FTBFS (LaTeX Error: File 'infwarerr.sty' not found.)
to be marked as done.

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

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


-- 
949132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cdftools
Version: 3.0.2-3
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

In preparation of the netcdf-fortran transition as test rebuild of your package 
was done which FTBFS:

 (/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
 [Loading MPS to PDF converter (version 2006.09.02).]
 ) (/usr/share/texlive/texmf-dist/tex/latex/epstopdf-pkg/epstopdf-base.sty

 ! LaTeX Error: File `infwarerr.sty' not found.

 Type X to quit or  to proceed,
 or enter new name. (Default extension: sty)

 Enter file name: 
 ! Emergency stop.
  
 
 l.178   \RequirePackage{infwarerr}[2007/09/09]
  ^^M
 !  ==> Fatal error occurred, no output PDF file produced!

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: cdftools
Source-Version: 3.0.2-4

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated cdftools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 13:23:49 +
Source: cdftools
Architecture: source
Version: 3.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 949132
Changes:
 cdftools (3.0.2-4) unstable; urgency=medium
 .
   * Update homepage to https://github.com/meom-group/CDFTOOLS
   * Add B-D on texlive-latex-recommended, Closes: #949132
   * Standards-Version: 4.4.1.0
   * B-D on gfortran | fortran-compiler
   * Change d/macro.gfortran_debian to d/macro.f95_debian for flang compat.
   * Move to use debhelper-compat (= 12)
Checksums-Sha1:
 8e9ac9538f3cffe3e3a75c2a3d169ff5bfbd2d72 1960 cdftools_3.0.2-4.dsc
 24494b82ed19211d3a82d537e777855faa09dd07 18560 cdftools_3.0.2-4.debian.tar.xz
Checksums-Sha256:
 c98642deb17dd35d9ee288a9bc775de764ed6baa3e44dbdd79770137894f6e84 1960 
cdftools_3.0.2-4.dsc
 775fc9a7cb6f4dbb1198383615acf3b8f30531c502868096029fb582b5c3e35e 18560 
cdftools_3.0.2-4.debian.tar.xz
Files:
 b715c9d60d9db6fe039050a56e5aa0fa 1960 utils optional cdftools_3.0.2-4.dsc
 b0dd3f63728f287f3aa99ef1eb631574 18560 utils optional 
cdftools_3.0.2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl44IasACgkQy+a7Tl2a
06UElQ//V4fx0su5gmgT47D/dt6lfHRb43W4NUARXevIbrZMPGHJgqhMl9NJuAQf
X1bgeOGpA6FpYcL5kZu59vItzWQDtu1/RVj0nb3l2cPq0q3m82wUyk0cHK8WmFpM
vdKG2zjYJU+RJrMAFqlPe0ZZ99wJdPikNzt1rODmh6JxAEz6zrzZ27/1ZtX3W5Hu
Ftb4ygZL/DuaAUCix7UdcSfqrFWjrjWPqru0zUZ/BcLezpIcG7fKuDjdX/sybrcP
efk+duE2xYpc3JKSdVC6ONTio9SfrI1oDcSJqbRDgKKa87mHXm1WvkqrMT2vGLIF
nJmFn501Hu+mljRYf1M6At6lsEKe4H498660ESEAAUzKgeXIaPg21Qlf988b3tB+
VF6j79+3QZ57WWuKUHxlrcRUE6N3fwvzoL1WkYQfMe/NOI7BzZnZmNkxAiICSvl2
lHucf7+MnTArEbNCIdLc9/4ZN39cMRcYAWjbZDWOBIdoTYzl2bh1T8UlPTHVoUcQ
oHbd5KNxLT2Le2zmNlBGOooIPTxKROM+gAKAF074hMJ7bMKWXZUs0O0M8mIHt0oX
ctnIgWr9WHF434Dsxk/W+cUc+OggOnXeiZ28je1Qpjn6/wxOdLjTQNnmWZB0MBLd
ae0DKRwZWF51qYufoHhDwLpgTdBODp27zqJTEyDpLTpvb8iLSnE=
=Dt/J
-END PGP SIGNATURE End Message ---

Bug#950558: apertium-eo-en FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-eo-en
Version: 1.0.0~r63833-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-en.html

...
make -j15
make[1]: Entering directory '/build/1st/apertium-eo-en-1.0.0~r63833'
make  all-am
make[2]: Entering directory '/build/1st/apertium-eo-en-1.0.0~r63833'
apertium-validate-dictionary apertium-eo-en.eo.dix.xml
apertium-validate-dictionary apertium-eo-en.en.dix
apertium-validate-dictionary apertium-eo-en.eo-en.dix
apertium-validate-dictionary apertium-eo-en.eo-en.dix
apertium-validate-dictionary apertium-eo-en.en.dix
apertium-validate-dictionary apertium-eo-en.post-en.dix
apertium-validate-dictionary apertium-eo-en.post-eo.dix
apertium-validate-transfer apertium-eo-en.eo-en.t1x
apertium-validate-interchunk apertium-eo-en.eo-en.t2x
apertium-validate-interchunk apertium-eo-en.eo-en.antaux_t2x
apertium-validate-postchunk apertium-eo-en.eo-en.t3x
apertium-validate-transfer apertium-eo-en.en-eo.t1x
apertium-validate-transfer apertium-eo-en.en-eo.genitive.t1x
apertium-validate-interchunk apertium-eo-en.en-eo.antaux_t2x
apertium-validate-interchunk apertium-eo-en.en-eo.antaux2_t2x
apertium-preprocess-transfer apertium-eo-en.eo-en.t2x eo-en.t2x.bin
apertium-preprocess-transfer apertium-eo-en.eo-en.antaux_t2x 
eo-en.antaux_t2x.bin
lt-comp lr apertium-eo-en.post-en.dix eo-en.autopgen.bin
lt-comp lr apertium-eo-en.post-eo.dix en-eo.autopgen.bin
apertium-preprocess-transfer apertium-eo-en.eo-en.t3x eo-en.t3x.bin
apertium-preprocess-transfer apertium-eo-en.en-eo.genitive.t1x 
en-eo.genitive.t1x.bin
apertium-preprocess-transfer apertium-eo-en.en-eo.antaux_t2x 
en-eo.antaux_t2x.bin
apertium-preprocess-transfer apertium-eo-en.en-eo.antaux2_t2x 
en-eo.antaux2_t2x.bin
main@standard 29 45
apertium-validate-interchunk apertium-eo-en.en-eo.t2x
main@standard 29 45
apertium-preprocess-transfer apertium-eo-en.eo-en.t1x eo-en.t1x.bin
apertium-validate-postchunk apertium-eo-en.en-eo.t3x
apertium-preprocess-transfer apertium-eo-en.en-eo.t1x en-eo.t1x.bin
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-eo-en.en-eo.t2x en-eo.t2x.bin
apertium-preprocess-transfer apertium-eo-en.en-eo.t3x en-eo.t3x.bin
Warning (3511): Paths to rule 49 blocked by rule 44.
Warning (3511): Paths to rule 49 blocked by rule 44.
Warning (3610): Paths to rule 51 blocked by rule 45.
Warning (3610): Paths to rule 51 blocked by rule 45.
Warning (3710): Paths to rule 53 blocked by rule 46.
Warning (3710): Paths to rule 53 blocked by rule 46.
Warning (3710): Paths to rule 53 blocked by rule 46.
Warning (3710): Paths to rule 53 blocked by rule 46.
Warning (3811): Paths to rule 55 blocked by rule 47.
Warning (3811): Paths to rule 55 blocked by rule 47.
Warning (3811): Paths to rule 55 blocked by rule 47.
Warning (3811): Paths to rule 55 blocked by rule 47.
cp *.mode modes/
Warning (3360): Paths to rule 57 blocked by rule 55.
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:848: modes] Error 1

Bug#950227: marked as pending in ruby-mime-types

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-mime-types/commit/4cc9c16d74b0a172c5873c744f12c09530470aba


make some packaging updates

Closes: #950227


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950227

Bug#950560: apertium-oc-es FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-oc-es
Version: 1.0.6~r57551-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-oc-es.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-oc-es-1.0.6~r57551'
make  all-am
make[2]: Entering directory '/build/1st/apertium-oc-es-1.0.6~r57551'
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.oc.metadix 
>.deps/oc.metadix
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.es.dix >.deps/es.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.oc-es.dix >.deps/oc-es.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.post-es.dix 
>.deps/es.post.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.post-oc.dix 
>.deps/oc.post.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.oc.metadix 
>.deps/oc@aran.metadix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.es.dix 
>.deps/e...@aran.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.oc-es.dix 
>.deps/o...@aran-es.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.post-es.dix 
>.deps/e...@aran.post.dix
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.post-oc.dix 
>.deps/o...@aran.post.dix
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.oc-es.t1x > oc-es.t1x
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.oc-es.t2x > oc-es.t2x
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.oc-es.t3x > oc-es.t3x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.oc-es.t1x > 
oc@aran-es.t1x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.oc-es.t2x > 
oc@aran-es.t2x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.oc-es.t3x > 
oc@aran-es.t3x
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.es-oc.t1x > es-oc.t1x
apertium-validate-interchunk oc-es.t2x
apertium-validate-postchunk oc-es.t3x
apertium-validate-postchunk oc@aran-es.t3x
apertium-validate-interchunk oc@aran-es.t2x
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.es-oc.t2x > es-oc.t2x
xsltproc --stringparam alt oc alt.xsl apertium-oc-es.es-oc.t3x > es-oc.t3x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.es-oc.t1x > 
es-oc@aran.t1x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.es-oc.t2x > 
es-oc@aran.t2x
xsltproc --stringparam alt oc@aran alt.xsl apertium-oc-es.es-oc.t3x > 
es-oc@aran.t3x
apertium-validate-postchunk es-oc.t3x
apertium-validate-interchunk es-oc.t2x
apertium-validate-postchunk es-oc@aran.t3x
apertium-gen-modes modes.xml
apertium-gen-modes modes.xml
apertium-validate-transfer oc@aran-es.t1x
apertium-gen-modes modes.xml
apertium-validate-transfer oc-es.t1x
apertium-gen-modes modes.xml
apertium-validate-interchunk es-oc@aran.t2x
cp: cannot stat '*.mode': No such file or directory
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:960: oc-es.mode] Error 1

Bug#950559: apertium-mk-bg FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-mk-bg
Version: 0.2.0~r49489-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-mk-bg.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-mk-bg-0.2.0~r49489'
apertium-validate-dictionary apertium-mk-bg.mk.dix
apertium-validate-dictionary apertium-mk-bg.bg.dix
apertium-validate-dictionary apertium-mk-bg.mk-bg.dix
apertium-validate-dictionary apertium-mk-bg.mk-bg.dix
apertium-validate-dictionary apertium-mk-bg.bg.dix
apertium-validate-dictionary apertium-mk-bg.mk.dix
apertium-validate-transfer apertium-mk-bg.mk-bg.t1x
cg-comp apertium-mk-bg.mk-bg.rlx mk-bg.rlx.bin
cg-comp apertium-mk-bg.bg-mk.rlx bg-mk.rlx.bin
apertium-validate-transfer apertium-mk-bg.bg-mk.t1x
apertium-validate-dictionary apertium-mk-bg.post-mk.dix
apertium-validate-dictionary apertium-mk-bg.post-bg.dix
apertium-gen-modes modes.xml
Sections: 1, Rules: 4, Sets: 9, Tags: 58
apertium-gen-modes modes.xml
lt-comp lr apertium-mk-bg.post-mk.dix bg-mk.autopgen.bin
lt-comp lr apertium-mk-bg.post-bg.dix mk-bg.autopgen.bin
apertium-preprocess-transfer apertium-mk-bg.bg-mk.t1x bg-mk.t1x.bin
apertium-preprocess-transfer apertium-mk-bg.mk-bg.t1x mk-bg.t1x.bin
mkdir: cannot create directory ‘/build/1st/apertium-mk-bg-0.2.0~r49489/modes’: 
File exists
Sections: 2, Rules: 53, Sets: 93, Tags: 154
7 rules cannot be skipped by index.
main@standard 9 39
main@standard 20 53
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (659): Paths to rule 12 blocked by rule 11.
Warning (659): Paths to rule 12 blocked by rule 11.
Warning (1324): Paths to rule 14 blocked by rule 12.
Warning (2462): Paths to rule 23 blocked by rule 18.
Warning (2462): Paths to rule 23 blocked by rule 18.
cp *.mode modes/
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
cp: cannot stat '*.mode': No such file or directory
make[1]: *** [Makefile:698: bg-mk.mode] Error 1

Processed: Bug#950227 marked as pending in ruby-mime-types

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950227 [src:ruby-mime-types] ruby-mime-types: autopkgtest needs update for 
new version of gem2deb
Added tag(s) pending.

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

Bug#947995: ncbi-entrez-direct: ncbi-entrez-direct FTBFS in testing/unstable

[Aaron M. Ucko]

Andreas Tille  writes:

>> protected branches.  Could you please adjust the project's permissions?
>
> Done (hopefully), Andreas. 

I was able to push now, thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#950561: apertium-fr-es FTBFS with apertium 3.6.1

[Adrian Bunk]

Source: apertium-fr-es
Version: 0.9.2~r61322-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-fr-es.html

...
make -j15
make[1]: Entering directory '/build/1st/apertium-fr-es-0.9.2~r61322'
make  all-am
make[2]: Entering directory '/build/1st/apertium-fr-es-0.9.2~r61322'
apertium-validate-dictionary apertium-fr-es.post-es.dix
lrx-comp apertium-fr-es.fr-es.eco.lrx fr-es.eco.autolex.bin
apertium-validate-transfer apertium-fr-es.fr-es.t1x
apertium-validate-interchunk apertium-fr-es.fr-es.t2x
apertium-validate-postchunk apertium-fr-es.fr-es.t3x
apertium-validate-dictionary apertium-fr-es.post-fr.dix
lrx-comp apertium-fr-es.es-fr.eco.lrx es-fr.eco.autolex.bin
apertium-validate-transfer apertium-fr-es.es-fr.t1x
apertium-validate-interchunk apertium-fr-es.es-fr.t2x
apertium-validate-postchunk apertium-fr-es.es-fr.t3x
if [ ! -d .deps ]; then mkdir .deps; fi
lrx-comp apertium-fr-es.fr-es.lrx fr-es.autolex.bin
2: 40@42
lrx-comp apertium-fr-es.es-fr.lrx es-fr.autolex.bin
3: 62@66
touch .deps/.d
apertium-validate-modes modes.xml
5: 110@118
apertium-preprocess-transfer apertium-fr-es.fr-es.t3x fr-es.t3x.bin
xsltproc translate-to-default-equivalent.xsl apertium-fr-es.fr-es.dix  | gawk 
'{gsub("&", "&"); print;}' >.deps/common-fr-es.dix
xsltproc --stringparam alt std alt.xsl apertium-fr-es.es.dix | gawk '{gsub("&", 
"&"); print;}' >.deps/es.dix
apertium-preprocess-transfer apertium-fr-es.es-fr.t3x es-fr.t3x.bin
4: 89@95
xsltproc --stringparam alt eco alt.xsl apertium-fr-es.es.dix | gawk '{gsub("&", 
"&"); print;}'>.deps/eco-es.dix
apertium-preprocess-transfer apertium-fr-es.fr-es.t2x fr-es.t2x.bin
lt-comp lr apertium-fr-es.post-es.dix fr-es.autopgen.bin
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-fr-es.es-fr.t2x es-fr.t2x.bin
lt-comp lr apertium-fr-es.post-fr.dix es-fr.autopgen.bin
main@standard 67 139
main@standard 295 580
apertium-preprocess-transfer apertium-fr-es.fr-es.t1x fr-es.t1x.bin
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:945: modes/fr-es.mode] Error 1

Bug#950099: closed by Gürkan Myczko (fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists")

[Adrian Bunk]

Control: reopen -1

> Date: Mon, 03 Feb 2020 05:15:10 +0100
> From: Gürkan Myczko 
> To: 950099-d...@bugs.debian.org
> Subject: fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
> 
> Same like,
> https://bugs.debian.org/950103

Does it build for you?

It still fails the same both in reproducible builds and when I try 
to build it locally.

cu
Adrian

Processed: Re: Bug#950099 closed by Gürkan Myczko (fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists")

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #950099 {Done: Gürkan Myczko } [src:fonts-inter] 
fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
Bug reopened
Ignoring request to alter fixed versions of bug #950099 to the same values 
previously set

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

Bug#950562: acorn: FTBFS: Error: Cannot find module 'rollup-plugin-buble'

[Andreas Beckmann]

Source: acorn
Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

acorn/experimental recently started to FTBFS:

 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/build/acorn-6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0'
mkdir -p build/acorn/
cp -rf acorn build
# remove identifier
rm -f  build/acorn//src/identifier.js
touch build/acorn/builddir.stamp
node bin/generate-identifier-regex.js acorn/src/identifier.js > 
build/acorn/src/identifier.js
cd build && TRANSPILE=babel6 BABEL_PRESET=es2015 rollup -c 
acorn/rollup.config.js
[!] Error: Cannot find module 'rollup-plugin-buble'
Error: Cannot find module 'rollup-plugin-buble'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. 
(/build/acorn-6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0/build/acorn/rollup.config.js:5:29)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.require.extensions..js 
(/usr/share/nodejs/rollup/bin/src/run/loadConfigFile.js:39:24)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)

make[1]: *** [debian/rules:56: build/acorn/build.stamp] Error 1
make[1]: Leaving directory 
'/build/acorn-6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0'
make: *** [debian/rules:11: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas


acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-5.log.gz
Description: application/gzip

Bug#950227: marked as done (ruby-mime-types: autopkgtest needs update for new version of gem2deb)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 14:42:15 +
with message-id 
and subject line Bug#950227: fixed in ruby-mime-types 3.3.1-1
has caused the Debian Bug report #950227,
regarding ruby-mime-types: autopkgtest needs update for new version of gem2deb
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.)


-- 
950227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mime-types
Version: 3.2.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gem2deb

Dear maintainers,

With a recent upload of gem2deb the autopkgtest of ruby-mime-types fails
in testing when that autopkgtest is run with the binary packages of
gem2deb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
gem2debfrom testing1.0.3
ruby-mime-types from testing3.2.2-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. The cause of
this is that gem2deb started to exit with code 77 to indicate that there
is no test to run. This is meant to be used in conjunction with the
skippable restriction, to avoid giving the wrong information to the
migration software. Please add the skippable restriction to your
test. Depending on how much the smoke-test actually tests the package,
you may consider marking that as superficial as well.

Currently this regression is blocking the migration of gem2deb to
testing [1]. Of course, gem2deb shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
gem2deb was intended and your package needs to update to the new situation.

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=gem2deb

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-mime-types/4144034/log.gz


autopkgtest [03:10:42]: test command1: gem2deb-test-runner --autopkgtest
--check-dependencies 2>&1
autopkgtest [03:10:42]: test command1: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5
  │
└──┘

GEM_PATH= ruby2.5 -e gem\ \"mime-types\"

┌──┐
│ Run tests for ruby2.5: no test suite!
  │
└──┘

autopkgtest [03:10:43]: test command1: ---]
autopkgtest [03:10:43]: test command1:  - - - - - - - - - - results - -
- - - - - - - -
command1 FAIL non-zero exit status 77



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-mime-types
Source-Version: 3.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-mime-types 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 13:12:11 +0100
Source: ruby-mime-types
Architecture: source
Version: 3.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Closes: 950227
Changes:
 ruby-mime-types (3.3.1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Antonio Terceiro ]
   * New upstream version 3.3.1
   * Packaging updates from a new run of dh-make-ruby
 - bump debhelper compat to 12 and delete debian/compat
 - bump Standards-Version to 4.4.0; no other changes needed
 -

Bug#950564: olive-editor FTBFS on 32bit: error: narrowing conversion

[Adrian Bunk]

Source: olive-editor
Version: 20200121-1
Severity: serious
Tags: ftbfs

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

...
cd /<>/obj-i686-linux-gnu/app && /usr/bin/c++  
-DAPPVERSION=\"0.2.0\" -DGITHASH=\"\" -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS 
-DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_SVG_LIB -DQT_WIDGETS_LIB -I/<>/obj-i686-linux-gnu/app 
-I/<>/app 
-I/<>/obj-i686-linux-gnu/app/olive-editor_autogen/include -isystem 
/usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtCore 
-isystem /usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/i386-linux-gnu/qt5/QtGui -isystem 
/usr/include/i386-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/i386-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/i386-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/i386-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/i386-linux-gnu/qt5/QtSvg  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -O2 -Werror 
-Wuninitialized -pedantic-errors -Wall -Wextra -Wconversion -Wsign-conversion 
-fPIC -std=c++11 -o CMakeFiles/olive-editor.dir/node/inputarray.cpp.o -c 
/<>/app/node/inputarray.cpp
/<>/app/node/input.cpp: In member function ‘virtual void 
NodeInput::Load(QXmlStreamReader*, QHash&, 
QList&, QList&)’:
/<>/app/node/input.cpp:166:71: error: narrowing conversion of 
‘QXmlStreamReader::text() const().QStringRef::toULongLong(0, 10)’ from 
‘qulonglong’ {aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} 
[-Wnarrowing]
  166 | input_connections.append({this, 
reader->text().toULongLong()});
  | ~~^~
/<>/app/node/input.cpp:166:71: error: conversion from ‘qulonglong’ 
{aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} may change 
value [-Werror=conversion]
/<>/app/node/input.cpp: In member function ‘QVariant 
NodeInput::StringToValue(const QString&, QList&)’:
/<>/app/node/input.cpp:275:57: error: narrowing conversion of ‘(& 
string)->QString::toULongLong(0, 10)’ from ‘qulonglong’ {aka ‘long long 
unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} [-Wnarrowing]
  275 | footage_connections.append({this, string.toULongLong()});
  |   ~~^~
/<>/app/node/input.cpp:275:57: error: conversion from ‘qulonglong’ 
{aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} may change 
value [-Werror=conversion]
cc1plus: all warnings being treated as errors
make[3]: *** [app/CMakeFiles/olive-editor.dir/build.make:1452: 
app/CMakeFiles/olive-editor.dir/node/input.cpp.o] Error 1

Bug#950565: kalgebra FTBFS on architectures without qtwebengine5-dev

[Adrian Bunk]

Source: kalgebra
Version: 4:19.12.1-1
Severity: serious
Tags: ftbfs

Looks like a problem with the override_dh_auto_configure:

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

...
make[1]: Entering directory '/<>'
DMOBILE_BACKEND="none"
make[1]: Leaving directory '/<>'
   dh_auto_build --buildsystem=kf5 -a
cd obj-powerpc64le-linux-gnu && make -j8 "INSTALL=install 
--strip-program=true"
dh_auto_build: error: chdir("obj-powerpc64le-linux-gnu") failed: No such file 
or directory
dh_auto_build: error: cd obj-powerpc64le-linux-gnu && make -j8 "INSTALL=install 
--strip-program=true" returned exit code 25
make: *** [debian/rules:18: binary-arch] Error 25

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[Felix Zielcke]

On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
> Package: libgcc1
> Version: 1:9.2.1-25
> Severity: grave
> Justification: renders package unusable
> 
> hey,
> 
> after upgrading some latest packages on sid, i can no longer unlock
luks
> partition and boot. message:
> 
> "Please unlock disk rootfs:
> libgcc_s.so.1 must be installed for pthread-cancel to work
> Aborted"
> 
> so i think it's libgcc1 related.
> had to chroot to disk from liveusb, downgrade some packages & finally
use a
> different kernel to boot.
> noticed that update-initramfs with libgcc1 1:9.2.1-25 adds file :
"Adding
> binary /lib/x86_64-linux-gnu/libgcc_s.so.1" , while libgcc1 version
> 1:10-20200202-1 doesn't add any libgcc_s.so.1.
> 
> also, version from testing includes file /lib/x86_64-linux-
gnu/libgcc_s.so.1,
> while sid version uses /lib/libgcc_s.so.1 . libgcc-s1 also includes
this file :
> /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
> 
> let me know if you need anymore info.
> 
> thanks,
> d.

The btrfs binary in initramfs is also affected by this.
See #950556 [1]

Just now with your report I saw that both btrfs and cryptroot initramfs
hooks expects libgcc_s.so.1 in the same dir as libc.so.6
This was true in bullseye but now with the change to gcc-10 the path
has also changed.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556

Bug#950525: marked as done (broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.1})

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 15:05:16 +
with message-id 
and subject line Bug#950525: fixed in gcc-9 9.2.1-27
has caused the Debian Bug report #950525,
regarding broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.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.)


-- 
950525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-9
Version: 9.2.1-25
Severity: serious
X-Debug-Cc: debian-s...@lists.debian.org

On i386
# file /usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1
/usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1: broken symbolic link to
/lib/i386-linux-gnu/libgcc_s.so.1

On s390x:
$ file /usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so*
/usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so: broken symbolic link to
/lib/s390x-linux-gnu/libgcc_s.so.1

Which make some packages ftbfs on s390x:
https://buildd.debian.org/status/fetch.php?pkg=zlib&arch=s390x&ver=1%3A1.2.11.dfsg-1.2&stamp=1580704985&raw=0
--- End Message ---
--- Begin Message ---
Source: gcc-9
Source-Version: 9.2.1-27

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 12:40:17 +0100
Source: gcc-9
Architecture: source
Version: 9.2.1-27
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 950525
Changes:
 gcc-9 (9.2.1-27) unstable; urgency=medium
 .
   * Update to git 20200203 from the gcc-9 branch.
 - Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
   * libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
   * Allow retrying of a native build in case of unreproducible ICEs.
Checksums-Sha1:
 150a3ed9af1b214e727c2fd031352cbde136b036 22466 gcc-9_9.2.1-27.dsc
 dcdc3d3da2b617a2631b57f7ec3db87564284193 962088 gcc-9_9.2.1-27.debian.tar.xz
 415b205cf7b53a196292e4dfb961fcf0edd43308 9327 gcc-9_9.2.1-27_source.buildinfo
Checksums-Sha256:
 2078efe8472d85edc20e33a79ea1ce4a4d27827c531b2592cfaf72c88c118f5a 22466 
gcc-9_9.2.1-27.dsc
 fdee30e25d8d23d881f9b7f36b2ba918c85d81dd25c736ff1fea9771a994ccac 962088 
gcc-9_9.2.1-27.debian.tar.xz
 341a2de9c7c6dbb9d61857ef3a5687a95b7a286349740b8cf46b0f9dc746445c 9327 
gcc-9_9.2.1-27_source.buildinfo
Files:
 aa76b5fa65b67f65f72fcc35c7ad3884 22466 devel optional gcc-9_9.2.1-27.dsc
 f6f1f2de56e6e075a5b943da2c004db2 962088 devel optional 
gcc-9_9.2.1-27.debian.tar.xz
 127243bcdb24c646661fe26b6d9e55ff 9327 devel optional 
gcc-9_9.2.1-27_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl44MUUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9bd9EACI5ynJyLxt5S5SZxLOKcd0SpEyeM4lHG45
8xjjGulD9JFxgKo8sPyH5k40Yht6cHiyXDQ0NJTI4c4N3ttCj6K0efoMXPvoaZTM
y+fJtVox0iPYKxffE8tDjCxETMulRhw7lzB9l4dKHa7gn7dyBLGKTEWiaJBtDWpy
UkunsQT8E0E49A+AK792k5iSo9O3mHUk1PxsvtSppPJzSJoZJp8ZDrYRqmXhp5Nb
shSJF9LKW9/Neh2yRKHgRCMw2o7tHmosknIwNamW7/G5AOX6vqkMD4WwiHG4uj5K
76xxHO71oJffTtwc6iQy02EfCQmeUHkexbzWzRsLJ5erAh1SdHKfAfwcbA7yCdeD
uHllBWBtuIN7NFz5u1sQH/lzAiBkeFpDwWsw50ijwGlCEDdE9NOoW6gFPDoEtuBv
NpuEPFTPiL0Bz/q8o/x1J9qixhNQcoyQ2ZkTmP/lWssHdqC8gP+rc0r++WMYzXE4
5pYq8tjFeuwkag86XdQMCZRpFt18hh3ts1YYoLjIN3UReRX3ja/2jlrZkHp8w/Ku
ZcV4HBppfhJu2RPyPwXniCiM1yCnPEaDRLIogh06gaAof0XmlMP21vvo9rfUra4A
1ABLLb3/I/WJzDkSbRRHzw6+jA61elxdlN2W86yUQc1Otub1kC0Qj3xarADi7GmE
OWHEFIbRig==
=vLaR
-END PGP SIGNATURE End Message ---

Processed: py2removal bugs severity updates - 2020-02-03 15:35:31.005250+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # crossfire-maps is an application, has low popcon (48 < 300), and has 0 
> external rdeps or not in testing
> severity 936345 serious
Bug #936345 [src:crossfire-maps] crossfire-maps: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-png is a module and has 0 external rdeps or not in testing
> severity 937507 serious
Bug #937507 [src:pypng] pypng: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#939454: marked as done (link-grammar ftbfs (symbols file mismatches))

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 15:35:04 +
with message-id 
and subject line Bug#939454: fixed in link-grammar 5.7.0-1
has caused the Debian Bug report #939454,
regarding link-grammar ftbfs (symbols file mismatches)
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.)


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

Package: src:link-grammar
Version: 5.6.2-1
Severity: serious
Tags: sid bullseye

link-grammar ftbfs, symbols file mismatches for all architectures except for 
amd64.

See https://buildd.debian.org/status/package.php?p=link-grammar
--- End Message ---
--- Begin Message ---
Source: link-grammar
Source-Version: 5.7.0-1

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

Debian distribution maintenance software
pp.
Masayuki Hatta  (supplier of updated link-grammar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 23:51:14 +0900
Source: link-grammar
Architecture: source
Version: 5.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Masayuki Hatta 
Closes: 936951 939454
Changes:
 link-grammar (5.7.0-1) unstable; urgency=medium
 .
   [ Masayuki Hatta ]
   * QA upload.
   * Update standards version to 4.5.0, no changes needed.
   * Add 01-disable-multi-dict-test.patch to disable the multi-dict test.
 I'm still not sure why it works outside then fails inside pbuilder.
 .
   [ Fabian Wolff ]
   * New upstream release.
   * Update watch file to use GitHub.
   * Upgrade to debhelper compat level 12.
   * Drop python-link-grammar package (Closes: #936951).
   * Add flex to build dependencies.
   * "make check" should run during the build; this is not what
 autopkgtest is intended for.
   * Add 00-disable-python-test.patch to disable the Python tests during
 the build (see the header for justification), and add python-tests
 autopkgtest to run the Python tests on the installed package
 instead.
   * Remove debian/liblink-grammar5.symbols (Closes: #939454)
 (admittedly not the best solution probably, but whoever has a
 better idea is welcome to fix this in the future).
 .
   [ Debian Janitor ]
   * Re-export upstream signing key without extra signatures.
   * Remove obsolete fields Name from debian/upstream/metadata.
Checksums-Sha1:
 7fb6207f58dec1150b162868fcdd4c13be89f733 2940 link-grammar_5.7.0-1.dsc
 a05d70412b6d62a402c1e93ae6518fb918826825 3303328 link-grammar_5.7.0.orig.tar.xz
 d7999a35647921b82d594b60d2cf4e80b22c6556 22360 
link-grammar_5.7.0-1.debian.tar.xz
 079ff5203a8929ac15fea6cf3216d6000dd95b20 12831 
link-grammar_5.7.0-1_amd64.buildinfo
Checksums-Sha256:
 7c0e270493f3df18cca169d9144201e9579a2a96241e6f7fabacf38160c2c7a7 2940 
link-grammar_5.7.0-1.dsc
 321eabd8eb0ee77c4a9ff7f299cbf7dab816c6c7e3d4ed046fb4f51bc7aef67f 3303328 
link-grammar_5.7.0.orig.tar.xz
 609ed0bb8f1ed958822e2e7420645de2bd29d4a97762b94e5415c3623b35f94b 22360 
link-grammar_5.7.0-1.debian.tar.xz
 b4091907e3857996c70b16780efb625e7f28038c3545aa01df8f69c96ed33ac1 12831 
link-grammar_5.7.0-1_amd64.buildinfo
Files:
 2c9c1e1d91012204bf401bf492dafc29 2940 text optional link-grammar_5.7.0-1.dsc
 00f6d6615fdb8100746c1b37f6a52d7c 3303328 text optional 
link-grammar_5.7.0.orig.tar.xz
 d3e0cc85945f2b67fa3a14981b4e5084 22360 text optional 
link-grammar_5.7.0-1.debian.tar.xz
 a0c6fb133c43b08ee7f149861406082b 12831 text optional 
link-grammar_5.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEZDzS6N3LAPjxWBIb3a4SYm4UEDUFAl44OukSHG1oYXR0YUBk
ZWJpYW4ub3JnAAoJEN2uEmJuFBA1jVMP/01dutxvr8C8LInh3AbB/1nCPeW39iGK
2B358v1x3DblA+n9eG961Dg/vS3UdX4IyhIifJ4VF1LmB8h43aAEH91hQDB7YaKR
iUn+sZYWI9PFb40RvlvUKG3bnG0cIKPftYIv68rBcforDGIriOUL0rflrXx7RoGr
H41Jb35xVuLg1mGXsEr5j9hk2YCJbOlAN4Ae+SIEiJyTURZnBkHnsTnOOwJs22+q
FG39HsUOE7vIrV7+KHu0F3QKFkMFjBY+Uf21R4fKjaOPKreZtOZZNPE9H1WhbPH4
PKp0I3JPpZnpqDHWNbp+I6m6QnDUxJ3aqW5DBAky3ptUbvQrhfusUdYaygzj3dcw
QhQl314q6X4IeHD3tjqHcCxadcntf2+0pdVDhBbBd1MakXApYeFzFqlC5a

Bug#950110: marked as done (liboctomap-dev,...: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 15:36:51 +
with message-id 
and subject line Bug#950110: fixed in octomap 1.9.3+dfsg-2
has caused the Debian Bug report #950110,
regarding liboctomap-dev,...: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
950110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liboctomap-dev,liboctovis-dev,octomap-tools,octovis
Version: 1.9.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m51.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/liboctomap-dev/changelog.Debian.gz (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/copyright (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/geb079.bt (liboctomap-dev:amd64) 
!= /usr/share/doc/liboctomap1.8/examples/data/geb079.bt (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/mapcoll.txt 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/mapcoll.txt (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/scan.dat.bz2 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/scan.dat.bz2 (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/spherical_scan.graph 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/spherical_scan.graph (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/example-project.tgz 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/example-project.tgz (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8

1m12.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/liboctovis-dev/changelog.Debian.gz (liboctovis-dev:amd64) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/liboctovis-dev -> liboctomap1.8
  /usr/share/doc/liboctovis-dev/copyright (liboctovis-dev:amd64) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/liboctovis-dev -> liboctomap1.8

0m25.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/octomap-tools/changelog.Debian.gz (octomap-tools) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/octomap-tools -> liboctomap

Bug#950568: node-copy-webpack-plugin FTBFS: test failures

[Adrian Bunk]

Source: node-copy-webpack-plugin
Version: 4.3.0-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-copy-webpack-plugin.html

...
5 passing (81ms)
  65 failing

  1) apply function
   with glob in from
 can use a glob to move a file to the root directory:
 TypeError: pathType.dir is not a function
  at Promise.all.arrify.map.x 
(/usr/lib/nodejs/globby/node_modules/dir-glob/index.js:40:53)
  at Array.map ()
  at module.exports 
(/usr/lib/nodejs/globby/node_modules/dir-glob/index.js:40:35)
  at globDirs (/usr/lib/nodejs/globby/index.js:64:9)
  at getPattern (/usr/lib/nodejs/globby/index.js:67:64)
  at Promise.all.globTasks.map.task (/usr/lib/nodejs/globby/index.js:78:69)
  at Array.map ()
  at module.exports (/usr/lib/nodejs/globby/index.js:78:41)
  at processPattern (dist/processPattern.js:51:33)
  at /build/1st/node-copy-webpack-plugin-4.3.0/dist/index.js:114:57
...

Bug#948774: marked as done (xdrawchem: build with Open Babel 3)

[Debian Bug Tracking System]

Your message dated Mon, 3 Feb 2020 17:31:54 +0100
with message-id <20200203163154.ga28...@georges.khaznadar.fr>
and subject line Update to openbabel3 done
has caused the Debian Bug report #948774,
regarding xdrawchem: build with Open Babel 3
to be marked as done.

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

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


-- 
948774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdrawchem
Tags: patch
Control: block 948477 by -1

Hello,

I have prepared an NMU containing a patch to make xdrawchem build with
Open Babel 3.

Best,
Andrius

diff -Nru xdrawchem-1.10.2.1/debian/changelog 
xdrawchem-1.10.2.1/debian/changelog
--- xdrawchem-1.10.2.1/debian/changelog 2019-01-01 10:30:37.0 -0500
+++ xdrawchem-1.10.2.1/debian/changelog 2020-01-13 02:05:28.0 -0500
@@ -1,3 +1,10 @@
+xdrawchem (1:1.10.2.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Porting to Open Babel 3.
+
+ -- Andrius Merkys   Mon, 13 Jan 2020 02:05:28 -0500
+
 xdrawchem (1:1.10.2.1-2) unstable; urgency=medium
 
   * updated Standards-Version and dh level
diff -Nru xdrawchem-1.10.2.1/debian/patches/openbabel3.patch 
xdrawchem-1.10.2.1/debian/patches/openbabel3.patch
--- xdrawchem-1.10.2.1/debian/patches/openbabel3.patch  1969-12-31 
19:00:00.0 -0500
+++ xdrawchem-1.10.2.1/debian/patches/openbabel3.patch  2020-01-08 
04:38:17.0 -0500
@@ -0,0 +1,155 @@
+--- a/xdrawchem.pro
 b/xdrawchem.pro
+@@ -2,8 +2,8 @@
+ TARGET = xdrawchem
+ 
+ # edit to match your OB install
+-exists(/usr/include/openbabel-2.0/openbabel/mol.h) {
+-INCLUDEPATH += /usr/include/openbabel-2.0
++exists(/usr/include/openbabel3/openbabel/mol.h) {
++INCLUDEPATH += /usr/include/openbabel3
+ LIBS += -lopenbabel
+ }
+ exists(/usr/local/include/openbabel-2.0/openbabel/mol.h) {
+--- a/xdrawchem/ioiface.h
 b/xdrawchem/ioiface.h
+@@ -20,6 +20,9 @@
+ 
+ #include "chemdata.h"
+ 
++#include 
++#include 
++#include 
+ #include 
+ 
+ using namespace OpenBabel;
+--- a/xdrawchem/ioiface.cpp
 b/xdrawchem/ioiface.cpp
+@@ -193,7 +193,7 @@
+ int bondorder = bond->GetBondOrder();
+ 
+ //set elements
+-if ( !atom1->IsCarbon() ) {
++if ( atom1->GetAtomicNum() != 6 ) {
+ QString str( "" );
+ str += IOIface::symbol[atom1->GetAtomicNum() - 1];
+ str += "";
+@@ -201,7 +201,7 @@
+ 
+ }
+ 
+-if ( !atom2->IsCarbon() ) {
++if ( atom2->GetAtomicNum() != 6 ) {
+ QString str( "" );
+ 
+ str += IOIface::symbol[atom2->GetAtomicNum() - 1];
+@@ -216,7 +216,7 @@
+ 
+ //label atoms if not Carbon
+ 
+-if ( !atom1->IsCarbon() ) {
++if ( atom1->GetAtomicNum() != 6 ) {
+ 
+ text = new Text( chemdata->getRender2D() );
+ QString str = IOIface::symbol[atom1->GetAtomicNum() - 1];
+@@ -229,7 +229,7 @@
+ //qDebug() << "ioiface(1) text:" << str;
+ }
+ 
+-if ( !atom2->IsCarbon() ) {
++if ( atom2->GetAtomicNum() != 6 ) {
+ 
+ text = new Text( chemdata->getRender2D() );
+ QString str = IOIface::symbol[atom2->GetAtomicNum() - 1];
+--- a/xdrawchem/molecule.h
 b/xdrawchem/molecule.h
+@@ -3,6 +3,10 @@
+ #ifndef MOLECULE_H
+ #define MOLECULE_H
+ 
++#include 
++#include 
++#include 
++#include 
+ #include 
+ #include 
+ 
+--- a/xdrawchem/molecule_obmol.cpp
 b/xdrawchem/molecule_obmol.cpp
+@@ -58,7 +58,7 @@
+ Point point;
+ Text *text;
+ 
+-std::vector < OBEdgeBase * >::iterator bonditr;
++std::vector < OBBond * >::iterator bonditr;
+ std::map < Point, DPoint *, pt_cmp > points;
+ std::map < Point, DPoint *, pt_cmp >::iterator itr;
+ 
+@@ -133,7 +133,7 @@
+ int bondorder = bond->GetBondOrder();
+ 
+ //set elements
+-if ( !atom1->IsCarbon() ) {
++if ( atom1->GetAtomicNum() != 6 ) {
+ QString str( "" );
+ 
+ str += symbol[atom1->GetAtomicNum() - 1];
+@@ -142,7 +142,7 @@
+ 
+ }
+ 
+-if ( !atom2->IsCarbon() ) {
++if ( atom2->GetAtomicNum() != 6 ) {
+ QString str( "" );
+ 
+ str += symbol[atom2->GetAtomicNum() - 1];
+@@ -155,7 +155,7 @@
+ 
+ //label atoms if not Carbon
+ 
+-if ( !atom1->IsCarbon() ) {
++if ( atom1->GetAtomicNum() != 6 ) {
+ 
+ text = new Text( r );
+ QString str = symbol[atom1->GetAtomicNum() - 1];
+@@ -167,7 +167,7 @@
+ addText( text );
+ }
+ 
+-if ( !atom2->IsCarbon() ) {
++if ( atom2->

Processed: pyserial: diff for NMU version 3.4-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937533 + patch
Bug #937533 [src:pyserial] pyserial: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#937533: pyserial: diff for NMU version 3.4-5.1

[Sandro Tosi]

Control: tags 937533 + patch


Dear maintainer,

I've prepared an NMU for pyserial (versioned as 3.4-5.1). The diff
is attached to this message.

Regards.

diff -Nru pyserial-3.4/debian/changelog pyserial-3.4/debian/changelog
--- pyserial-3.4/debian/changelog	2020-01-07 08:21:42.0 -0500
+++ pyserial-3.4/debian/changelog	2020-02-03 11:29:07.0 -0500
@@ -1,3 +1,10 @@
+pyserial (3.4-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937533
+
+ -- Sandro Tosi   Mon, 03 Feb 2020 11:29:07 -0500
+
 pyserial (3.4-5) unstable; urgency=medium
 
   * Re-add the build dependency on python2, use python2 in the rules file.
diff -Nru pyserial-3.4/debian/control pyserial-3.4/debian/control
--- pyserial-3.4/debian/control	2020-01-07 08:21:37.0 -0500
+++ pyserial-3.4/debian/control	2020-02-03 11:26:53.0 -0500
@@ -3,23 +3,11 @@
 Priority: optional
 Maintainer: Matthias Klose 
 Build-Depends: debhelper (>= 9)
-Build-Depends-Indep: python2, python3, dh-python,
-  python-setuptools, python3-setuptools,
-XS-Python-Version: all
+Build-Depends-Indep: python3, dh-python,
+  python3-setuptools,
 Standards-Version: 4.4.1
 Homepage: http://pyserial.sourceforge.net/
 
-Package: python-serial
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
-Suggests: python-wxgtk3.0 | python-wxgtk
-XB-Python-Version: ${python:Versions}
-Description: pyserial - module encapsulating access for the serial port
- This module encapsulates the access for the serial port. It provides
- back-ends for standard Python running on Windows, Linux, BSD (possibly
- any POSIX compliant system). The module named "serial" automatically
- selects the appropriate back-end.
-
 Package: python3-serial
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}
diff -Nru pyserial-3.4/debian/rules pyserial-3.4/debian/rules
--- pyserial-3.4/debian/rules	2020-01-07 08:20:16.0 -0500
+++ pyserial-3.4/debian/rules	2020-02-03 11:27:36.0 -0500
@@ -6,8 +6,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-PY_INTERPRETER = /usr/bin/python
-
 build: build-stamp
 build-indep: build-stamp
 build-arch:
@@ -15,7 +13,6 @@
 
 build-stamp:
 	dh_testdir
-	python2 setup.py build
 	python3 setup.py build
 	touch build-stamp
 
@@ -32,13 +29,9 @@
 	dh_testroot
 	dh_prep
 	dh_installdirs
-	python2 setup.py install --root=$(CURDIR)/debian/python-serial --install-layout=deb
-	find debian/python-serial -name 'aio.py*' | xargs -r rm -f
 	python3 setup.py install --root=$(CURDIR)/debian/python3-serial --install-layout=deb
-	dh_python2
 	dh_python3
 	mv debian/python3-serial/usr/bin/miniterm.py debian/python3-serial/usr/bin/miniterm
-	rm -f debian/python-serial/usr/bin/miniterm.py
 
 # Build architecture-independent files here.
 binary-indep: build install

Bug#937533: marked as done (pyserial: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 17:05:32 +
with message-id 
and subject line Bug#937533: fixed in pyserial 3.4-5.1
has caused the Debian Bug report #937533,
regarding pyserial: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyserial

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyserial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 11:29:07 -0500
Source: pyserial
Architecture: source
Version: 3.4-5.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Sandro Tosi 
Closes: 937533
Changes:
 pyserial (3.4-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937533
Checksums-Sha1:
 0c4e350b7041e357fc481f804bae51be1b8c6ed0 1771 pyserial_3.4-5.1.dsc
 4ae585f99968df43b6dcf0f5f1378c9089609332 3952 pyserial_3.4-5.1.debian.tar.xz
 b204d0214a4e3f691c66ed5e075ccb46d07ec20c 5652 pyserial_3.4-5.1_source.buildinfo
Checksums-Sha256:
 6a16a16cca04a0f05ce5657eb840ea6c412f889808d79a9c6d3e394b72fb0e1f 1771 
pyserial_3.4-5.1.dsc
 41d57437d84320d231a42f81c2f27e6726ef481ab8a1fb0521fa1934470e63ca 3952 
pyserial_3.4-5.1.debian.tar.xz
 975fd5660a792320b1994b9c7569d8dd4dfc17255e4fbe4f89558986aad27c54 5652 
pyserial_3.4-5.1_source.buildinfo
Files:
 5148d027bbd24c8078687a4a16c78323 1771 python optional pyserial_3.4-5.1.dsc
 7a5efc195e89a

Processed: Bug#950549 marked as pending in requirejs-text

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950549 [node-requirejs-text] node-requirejs-text: package.json occupies 
the location supposed for node-requirejs
Added tag(s) pending.

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

Bug#950549: marked as pending in requirejs-text

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #950549 in requirejs-text 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/requirejs-text/commit/983b9a365ec37cc209c68b07b7db29e6abc864ba


Fix install

Closes: #950549


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950549

Processed: Re: [Pkg-javascript-devel] Bug#950549: node-requirejs-text: package.json occupies the location supposed for node-requirejs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #950549 [node-requirejs-text] node-requirejs-text: package.json occupies 
the location supposed for node-requirejs
Severity set to 'serious' from 'normal'

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

Processed: Re: FTBFS against opencv 4.0.1 (exp)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #922583 [src:gst-plugins-bad1.0] FTBFS against opencv 4.0.1 (exp)
Added tag(s) patch.

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

Bug#922583: FTBFS against opencv 4.0.1 (exp)

[Gianfranco Costamagna]

control: tags -1 patch

Author: Gianfranco Costamagna 
Last-Update: 2020-02-03

--- gst-plugins-bad1.0-1.16.2.orig/configure.ac
+++ gst-plugins-bad1.0-1.16.2/configure.ac
@@ -1845,7 +1845,7 @@ AG_GST_CHECK_FEATURE(OPENCV, [opencv plu
   HAVE_OPENCV="yes"
 fi
   ], [
-PKG_CHECK_MODULES([OPENCV], [opencv4 >= 4.0.0 opencv4 < 4.2.0] , [
+PKG_CHECK_MODULES([OPENCV], [opencv4 >= 4.0.0 opencv4 < 4.3.0] , [
 AC_PROG_CXX
 AC_LANG([C++])
 OLD_CPPFLAGS=$CPPFLAGS


this does the trick
(inspired form upstream commit a2cfd93891376f74cc877e633aa70933b17200d9)

G.
On Mon, 18 Feb 2019 06:36:30 + Mo Zhou  wrote:
> Source: gst-plugins-bad1.0
> Version: 1.14.4-1
> Severity: important
> 
> Failed due to missing files

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #950020 (http://bugs.debian.org/950020)
> # Bug title: meson autopkg tests failing on arm64
> #  * https://github.com/mesonbuild/meson/pull/6539
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 950020 + fixed-upstream
Bug #950020 [src:meson] meson autopkg tests failing on arm64
Added tag(s) fixed-upstream.
> usertags 950020 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package firefox-esr

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package firefox-esr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #944706 (http://bugs.debian.org/944706)
> # Bug title: firefox-esr: Tab crashes immediately after start up and Firefox 
> ESR was unusable.
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1596338
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> INCOMPLETE
> #  * closed upstream
> tags 944706 + fixed-upstream
Bug #944706 [firefox-esr] firefox-esr: Tab crashes immediately after start up 
and Firefox ESR was unusable.
Added tag(s) fixed-upstream.
> usertags 944706 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 944706 + status-RESOLVED resolution-INCOMPLETE
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INCOMPLETE.
> thanks
Stopping processing here.

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

Bug#950549: marked as done (node-requirejs-text: package.json occupies the location supposed for node-requirejs)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 17:20:38 +
with message-id 
and subject line Bug#950549: fixed in requirejs-text 2.0.16-1
has caused the Debian Bug report #950549,
regarding node-requirejs-text: package.json occupies the location supposed for 
node-requirejs
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.)


-- 
950549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-requirejs-text
Version: 2.3.6-1
Affects: node-requirejs node-grunt-contrib-requirejs

Hello,

node-requirejs-text installs its package.json to
/usr/share/nodejs/requirejs, where the package.json of node-requirejs is
expected to be. This results in the failing test (grunt test -v --debug)
for node-grunt-contrib-requirejs with the following output:

Registering "tasks" tasks.
Loading "requirejs.js" tasks...ERROR
>> ReferenceError: define is not defined

The problem disappears by moving node-requirejs-text's package.json to
/usr/share/nodejs/requirejs/text/. However, I'm not sure how to check
how this change affects node-requirejs-text itself.

Best,
Andrius
--- End Message ---
--- Begin Message ---
Source: requirejs-text
Source-Version: 2.0.16-1

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated requirejs-text package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 18:02:39 +0100
Source: requirejs-text
Architecture: source
Version: 2.0.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 950549
Changes:
 requirejs-text (2.0.16-1) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Add debian/gbp.conf
   * Initial upstream branch.
   * New upstream version 2.0.16
   * Fix install (Closes: #950549)
   * Update copyright
   * Fix VCS fields
Checksums-Sha1: 
 f2e06927a28b2213aaeff9d8ff6e46c0394dbe2f 2028 requirejs-text_2.0.16-1.dsc
 5e4293ba5ce364c9e9c198c98444dcbeb66be16e 8872 requirejs-text_2.0.16.orig.tar.gz
 d8a54e0bbc7eaac89c76d941d9c8bd4f84c7133c 2656 
requirejs-text_2.0.16-1.debian.tar.xz
Checksums-Sha256: 
 06336114cd33fe79daea1a86f6c2571e41e0de158cdf14c9c63a97dc90034e2f 2028 
requirejs-text_2.0.16-1.dsc
 89d197ec8e49cb7761a653d1b76fdbb10b197e764d18dc2f7fcb7090d551855f 8872 
requirejs-text_2.0.16.orig.tar.gz
 ab21ca0063aaa1cc04040bec164bde39e598cfe5944c272dae46b4c5c9b13ced 2656 
requirejs-text_2.0.16-1.debian.tar.xz
Files: 
 d5bb0d9a4051dafdd8535d16f7823e07 2028 javascript optional 
requirejs-text_2.0.16-1.dsc
 858da3b6831a4a3fda099321f608737d 8872 javascript optional 
requirejs-text_2.0.16.orig.tar.gz
 2611910575d0dfe18bba377f25f9b462 2656 javascript optional 
requirejs-text_2.0.16-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl44U8AACgkQ9tdMp8mZ
7unwDg//SWcEjDf51T4xLosgz1MOBgSqjLtQQ9vS+qy1A64WN7gF70XZYyUighPb
jOHq6kbf2m12LBuUsU42SYKiyuvwtAwj13HN2yWI8ucUylnaF2lzEAPMeqSqokEV
1TUv1A3FomOQb/2uk1rbC+FZQqlibKzj0q9d+mICu0C91FvyrIr7lewJBuM4K4qM
IrhWcratdKYeLu8rieBwZ9rWueHG38nV1LG54Uy5K6QqUmDUTxnGvuq7MAvlcUfn
7n5Vp/I7P2BTcBpmAGd5sTVkng8HUR6jeFUiRQBvHZgLewE51dtLGxXE0z6SI3KX
8NbWCt7wztnzujGCQtmVrfpaqut/oCXa3UV8MKzEzsJslV9psxRX6Ise1iJH/iGl
Dw53jYOapr3OEew75bKK8Ixq5e06/sGa+VmSNPC1XUODcSzQ5yxySCY89v/lhGWu
VGDgpQSbJ7l/lnB+evwMom8N9Cnzt7c4HNBd3C2T6EH5kNG8AoduT9mSTURg8Zzy
z9EQH9Djmn9DlM1HcuVohxs3j64FJ9UR0ZiGG0Gns0NVaO2QSTnyUoo0VGg6nu68
/UZoC7jkUaKZJ6TRXfBG4+0hU7kME5Ll05JpIa9s9szqlvuwjF2noyeUKZT86Wdq
CBYMmpr4v/sGb9NAS/KkGA6VYXfWoCtiNJgDqup/ZKEHhkadsDA=
=W/wp
-END PGP SIGNATURE End Message ---

Bug#950525: marked as done (broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.1})

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 17:34:28 +
with message-id 
and subject line Bug#950525: fixed in gcc-9 9.2.1-28
has caused the Debian Bug report #950525,
regarding broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.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.)


-- 
950525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-9
Version: 9.2.1-25
Severity: serious
X-Debug-Cc: debian-s...@lists.debian.org

On i386
# file /usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1
/usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1: broken symbolic link to
/lib/i386-linux-gnu/libgcc_s.so.1

On s390x:
$ file /usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so*
/usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so: broken symbolic link to
/lib/s390x-linux-gnu/libgcc_s.so.1

Which make some packages ftbfs on s390x:
https://buildd.debian.org/status/fetch.php?pkg=zlib&arch=s390x&ver=1%3A1.2.11.dfsg-1.2&stamp=1580704985&raw=0
--- End Message ---
--- Begin Message ---
Source: gcc-9
Source-Version: 9.2.1-28

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 18:12:19 +0100
Source: gcc-9
Architecture: source
Version: 9.2.1-28
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 950525
Changes:
 gcc-9 (9.2.1-28) unstable; urgency=medium
 .
   * Update to git 20200203 from the gcc-9 branch.
 - Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
   * libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
   * Allow retrying of a native build in case of unreproducible ICEs.
Checksums-Sha1:
 e9e3d8369537e4ff56849a27060c61fc8381d4b9 22466 gcc-9_9.2.1-28.dsc
 d687b834d2fdd68c63083b315cc6ea0e27fd7a08 962072 gcc-9_9.2.1-28.debian.tar.xz
 049f16a68d2f587c72f67360e3a1663d8731e0cc 9327 gcc-9_9.2.1-28_source.buildinfo
Checksums-Sha256:
 cff088cbf920cbadafd1c7a931af398a9c8cdd629fd54b1436df4c1ecf9c 22466 
gcc-9_9.2.1-28.dsc
 4b5fa173a3c78250ac732aede6625924a2dae9c6fb9c42c10b0933146867a826 962072 
gcc-9_9.2.1-28.debian.tar.xz
 4068b164f615d2a4c3377f75bd7433654629029cc7d6d25b478958fe8961b7a7 9327 
gcc-9_9.2.1-28_source.buildinfo
Files:
 8a43798acc42d35ffcf66fc8a20be763 22466 devel optional gcc-9_9.2.1-28.dsc
 ccba12c6b2af8a7682fe918d88e89ecc 962072 devel optional 
gcc-9_9.2.1-28.debian.tar.xz
 1b00e94350ecb4de6c32e67a9fd0b5d0 9327 devel optional 
gcc-9_9.2.1-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl44VRUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dpXD/wNXDeyPoULtENeMBG3aFOU3kspv+UFfgiA
NVP0E15LOQoaqSKEbHz2Q+IZpa4BWC0dr8DI+RiRRF0Aq7OBOj5JMwevchE+Y/V8
YUvQ1DInUb8AEERU7MPL7zySjN3O52PLdWCfZicof9DvFki8kekSESvfIh+UnJF/
BBmJIT3u68Rc43+gEcBQA42fzC8elj/M9evZyPGKvpzNmtPdvwv42P8oEZyZrQaz
uEAIf606TE69GsnJ26dL3DN8nVP6vPVx4B8W654Z86VmZYtK9gtotZQJiKiuXxH4
dnxDcoW3dHWmiPJJyZTVTXSqYrPZcaB2pKaLbUlcPJPDdwTGHDED5OPE/Frko/A1
5gWVvQF7uu+CSJk1ERVA26ZC8dG5OZt3gPLIKSK8tmpLdc0tgIlsY/wKXat1CIT2
cbYhIiqbkmS3Vpb+YdZpx1KPRGooMB+2ZrqfPB/zHbaN3iJWW+lvaEiGsVf7xkyI
LQN+HlnVzN9xQ5XJEo211dSEaYi8+kZrMEskTtl5G7JGYwBO/H+6dd1PsVgvTro+
+3YdApe1andnxxUeaDNjpw5J9QYg622HRmAO7Ib+fQPBuMjQq3nlEro/LMYpyCqw
7FkYmjHy3cHDqsdHpzf3Uv89PQvkf7oqfuxZk2waX+CvGmbwlAt1BP6N2ip8oLns
N50rwzEhAw==
=mIV8
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

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

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

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

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[Matthias Klose]

On 2/3/20 3:46 PM, Felix Zielcke wrote:
> On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
>> Package: libgcc1
>> Version: 1:9.2.1-25
>> Severity: grave
>> Justification: renders package unusable
>>
>> hey,
>>
>> after upgrading some latest packages on sid, i can no longer unlock
> luks
>> partition and boot. message:
>>
>> "Please unlock disk rootfs:
>> libgcc_s.so.1 must be installed for pthread-cancel to work
>> Aborted"
>>
>> so i think it's libgcc1 related.
>> had to chroot to disk from liveusb, downgrade some packages & finally
> use a
>> different kernel to boot.
>> noticed that update-initramfs with libgcc1 1:9.2.1-25 adds file :
> "Adding
>> binary /lib/x86_64-linux-gnu/libgcc_s.so.1" , while libgcc1 version
>> 1:10-20200202-1 doesn't add any libgcc_s.so.1.
>>
>> also, version from testing includes file /lib/x86_64-linux-
> gnu/libgcc_s.so.1,
>> while sid version uses /lib/libgcc_s.so.1 . libgcc-s1 also includes
> this file :
>> /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
>>
>> let me know if you need anymore info.
>>
>> thanks,
>> d.
> 
> The btrfs binary in initramfs is also affected by this.
> See #950556 [1]
> 
> Just now with your report I saw that both btrfs and cryptroot initramfs
> hooks expects libgcc_s.so.1 in the same dir as libc.so.6
> This was true in bullseye but now with the change to gcc-10 the path
> has also changed.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556

$ dpkg -S libgcc_s.so.1
libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
libgcc1: /lib/libgcc_s.so.1

if you need the library in /lib, make sure that you depend on libgcc1, else it's
found in /usr/lib/.

I'm fine to add some breaks if required.

Bug#950226: marked as done (ruby-rails-timeago: autopkgtest needs update for new version of gem2deb)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 18:05:07 +
with message-id 
and subject line Bug#950226: fixed in ruby-rails-timeago 2.17.1-2
has caused the Debian Bug report #950226,
regarding ruby-rails-timeago: autopkgtest needs update for new version of 
gem2deb
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.)


-- 
950226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rails-timeago
Version: 2.17.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gem2deb

Dear maintainers,

With a recent upload of gem2deb the autopkgtest of ruby-rails-timeago
fails in testing when that autopkgtest is run with the binary packages
of gem2deb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
gem2debfrom testing1.0.3
ruby-rails-timeago from testing2.17.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The cause of
this is that gem2deb started to exit with code 77 to indicate that there
is no test to run. This is meant to be used in conjunction with the
skippable restriction, to avoid giving the wrong information to the
migration software. Please add the skippable restriction to your
failing test, or better, add a real test as it looks to me that also
test 2 isn't really doing much. If that is the case, please mark the
test as superficial.

Currently this regression is blocking the migration of gem2deb to
testing [1]. Of course, gem2deb shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
gem2deb was intended and your package needs to update to the new situation.

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=gem2deb

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rails-timeago/4144035/log.gz

autopkgtest [03:10:27]: test command1: gem2deb-test-runner --autopkgtest
2>&1
autopkgtest [03:10:27]: test command1: [---

┌──┐
│ Run tests for ruby2.5: no test suite!
  │
└──┘

autopkgtest [03:10:27]: test command1: ---]
autopkgtest [03:10:28]: test command1:  - - - - - - - - - - results - -
- - - - - - - -
command1 FAIL non-zero exit status 77



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-rails-timeago
Source-Version: 2.17.1-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-rails-timeago 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 17:22:22 +0100
Source: ruby-rails-timeago
Architecture: source
Version: 2.17.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Closes: 950226
Changes:
 ruby-rails-timeago (2.17.1-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Set fields Upstream-Contact in debian/copyright.
   * Remove obsolete fields Name, Contact from debian/upstream/metadata.
 .
   [ Pirate Praveen ]
   * Remove debian/tests (replaced by testsuite in debian/control), also fixes
 autopkgtest regression with recent gem2deb versions (Closes: #950226)
Checksums-Sha1:
 5a9b837a6566355c1cc52ddc89238913cc9444b4 2247 ruby-rails-timeago_2.17.1-2.dsc
 9439611c0ee1821fb9e4f3fab0232d1fc2ca3c52 2992 
ruby-rails-timeago_2.17.1-2.debian.tar.xz
 dd173af89

Bug#950575: kamailio manual install fails die modules are not yet in path?¡

[PICCORO McKAY Lenz]

Package: kamailio,systemd
Version: kamailio/5.3.0-1
Version: systemd/230-7
Severity: grave

Another systemd related problem, (like happened with #921015 ), this
error seems does not hapened if are installed with apt.get

i try to install kamailio due other ways, like aptitude or gui others,
and in those ways will fail, because first selected package to install
are kamailio per se and some modules are not yet ready to use it,
this is the output due the systemd "thing" .. does not happened in devuan
with sysvinit or openrc only:

Feb  3 17:25:58 10-101-2-99 systemd[1]: Starting Kamailio (Openser)
SIP Server...
Feb  3 17:25:58 10-101-2-99 systemd[21293]: Failed at step
RUNTIME_DIRECTORY spawning /usr/sbin/kamailio: File exists
Feb  3 17:25:58 10-101-2-99 systemd[1]: kamailio.service: control
process exited, code=exited status=233
Feb  3 17:25:58 10-101-2-99 systemd[1]: Failed to start Kamailio
(Openser) SIP Server.
Feb  3 17:25:58 10-101-2-99 systemd[1]: Unit kamailio.service entered
failed state.
Feb  3 17:25:59 10-101-2-99 systemd[1]: kamailio.service holdoff time
over, scheduling restart.
Feb  3 17:25:59 10-101-2-99 systemd[1]: Stopping Kamailio (Openser)
SIP Server...
Feb  3 17:25:59 10-101-2-99 systemd[1]: Starting Kamailio (Openser)
SIP Server...
Feb  3 17:25:59 10-101-2-99 systemd[1]: Reloading.
Feb  3 17:25:59 10-101-2-99 kamailio[21315]: loading modules under
config path: /usr/lib/x86_64-linux-gnu/kamailio/modules/
Feb  3 17:25:59 10-101-2-99 kamailio[21315]: Listening on

i cannot find what means "RUNTIME DIRECTORY" maybe are due in buster
now path are not set and maybe does not find property the paths, but
only happened with systemd related, i tested same package in devuan
(yes, it works, taking directly from debian) and installs property..

i also tested with mxlinux and works too also..


Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#950576: network-manager fails to correctly configure eth0 speed and fails when autoneg is on

[Eric Valette]

Package: network-manager
Version: 1.22.6-1
Severity: critical
Justification: breaks unrelated software

If I let eth0 in /etc/network/interface I get my eth0 card correctly configured 
by ifplugd
each time using full duplex and 1000Mbps

ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

If I let network manager handle this interface and either set "allow autoneg" 
or disable
it and force  speed at 1000 I get no working interafce it keeps trying to 
configure
it in a loop.

The only config that works is:
1) disable autoneg
2) and set speed at 100Mbps

but this is not what I want and fisrt ethtool command shows the ethernet card 
is capable
of what I want.

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

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

Versions of packages network-manager depends on:
ii  adduser3.118
ii  dbus   1.13.12-2
ii  init-system-helpers1.57
ii  libaudit1  1:2.8.5-2+b1
ii  libbluetooth3  5.52-1
ii  libc6  2.30-0experimental1
ii  libcurl3-gnutls7.67.0-2
ii  libglib2.0-0   2.63.3-3
ii  libgnutls303.6.12-1
ii  libjansson42.12-1
ii  libmm-glib01.10.4-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4
ii  libnm0 1.22.6-1
ii  libpam-systemd 244.1-2
ii  libpolkit-agent-1-00.116-2
ii  libpolkit-gobject-1-0  0.116-2
ii  libpsl50.20.2-2
ii  libreadline8   8.0-3
ii  libselinux13.0-1
ii  libsystemd0244.1-2
ii  libteamdctl0   1.30-1
ii  libudev1   244.1-2
ii  libuuid1   2.34-0.1
ii  policykit-10.116-2
ii  udev   244.1-2
ii  wpasupplicant  2:2.9-6

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables 1.8.4-2
ii  modemmanager 1.10.4-0.1
ii  ppp  2.4.7-2+4.1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1
pn  libteam-utils

-- no debconf information

Bug#950060: marked as done (m2l-pyqt: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 18:34:45 +
with message-id 
and subject line Bug#950060: fixed in m2l-pyqt 1.6-3
has caused the Debian Bug report #950060,
regarding m2l-pyqt: missing build dependency on dh-python
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.)


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

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

...
dh clean --with python3
dh: error: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 12) line 
1.
BEGIN failed--compilation aborted at (eval 12) line 1.

make: *** [debian/rules:9: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: m2l-pyqt
Source-Version: 1.6-3

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated m2l-pyqt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 19:11:15 +0100
Source: m2l-pyqt
Architecture: source
Version: 1.6-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 950060
Changes:
 m2l-pyqt (1.6-3) unstable; urgency=medium
 .
   * added Vcs stuff
   * added a build-dependency on dh-python. Closes: #950060.
Checksums-Sha1:
 246653185be2d2c18aed4f2f8e1b85f571076394 1962 m2l-pyqt_1.6-3.dsc
 3e35199854e6547194f3c53fcc710af3df24b1a2 2272 m2l-pyqt_1.6-3.debian.tar.xz
 f21e41b3f31284dffc81337b1d7ff63a090f4c99 10027 m2l-pyqt_1.6-3_source.buildinfo
Checksums-Sha256:
 c5064b2868d67ae24cd15ce3029a36a82fc3ad3d3bdadb01b5f0072fd04d3ea9 1962 
m2l-pyqt_1.6-3.dsc
 f91b61b87531fe83046fbb2b85907d84d880e928f65a406d561ff5adda15ae6b 2272 
m2l-pyqt_1.6-3.debian.tar.xz
 efb2965825cc62b76aa0801aed04bdb4363e152ed0147a9ad059ac7895fbe553 10027 
m2l-pyqt_1.6-3_source.buildinfo
Files:
 1a769ed21c4f75ae1e90d6b3408ad594 1962 x11 optional m2l-pyqt_1.6-3.dsc
 d1749df5f49bd4a27470b3f63b936b1b 2272 x11 optional m2l-pyqt_1.6-3.debian.tar.xz
 205de1d25558f4bc8ae8b13e8af22e95 10027 x11 optional 
m2l-pyqt_1.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl44ZRgUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjlItg/+N0aLapszNAalvGhm2Dj+qWdPJkyQ
OW5WFBHa674+Xqu22tsyTwDLoor0TGbTjfEgOzXAH3s8rn4QmP7/1FlIofQqY1Y/
AJ7zr1G0fIHXdFKlkpVYaLBCSaZbeXrT9oBfEVuJSCJ0Je26gE0VxJSCj5/StQSf
7E3DfAYj087m5IZ7jOtj6ijlxjDoT8vzbwR8OvnzeOPJrB5stg+NLneg364VJm1o
MSNwPJM7BBBi83YHQVu+YU/AN3Vr/XKRUqsF6/vXQdgcnF/JzhWE2uXAFslHHU/k
xj0kuFaBje1CqHGbm8LC0WN0avZayL4onIVeYO1ezi9iEUZwAMhngUtSkDG1QSXA
3CDGuoPAm/bDeD94yzfp44CdJe08RA5M4pnhlCmu5M/VKcsO8UaZ1nhSAaRpCnTf
588kuFKuTwtWokogveF5q93OWPgW9ivniPYRo11v66BpvbmQ/5h1Gkca1mzTB/kz
mJHpdqwOgZ/nskMnf+6C3gjqkEO6PM3NktSagbEeupATSzz2jh3zXRYyBXe9WySP
8AyAU9O5BTxa1rZkfbliNTq1FTM6UlT1+UaEF9VSeOYrDYcHBb8eH2AsLYU5TMj/
yqYHULkFAtU+HNI2uRXcHXX1tgve93Liuwek0wC9FkUCCYz1WHspREk3Yv87+63j
sNqtdQbHzWZfUcU=
=eFkj
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#950575: kamailio manual install fails die modules are not yet in path?¡

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #950575 [kamailio,systemd] kamailio manual install fails die modules are 
not yet in path?¡
Added tag(s) moreinfo.
> severity -1 important
Bug #950575 [kamailio,systemd] kamailio manual install fails die modules are 
not yet in path?¡
Severity set to 'important' from 'grave'

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

Bug#950575: kamailio manual install fails die modules are not yet in path?¡

[Michael Biebl]

Control: tags -1 moreinfo
Control: severity -1 important

Please run

reportbug --template systemd
reportbug --template kamailio
systemctl cat kamailio.service
systemctl status kamailio.service
journalctl -b -u kamailio.service

on the affected system and attach the output to this bug report.



signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-utopia-maintainers] Bug#950576: network-manager fails to correctly configure eth0 speed and fails when autoneg is on

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #950576 [network-manager] network-manager fails to correctly configure eth0 
speed and fails when autoneg is on
Severity set to 'normal' from 'critical'
> tags -1 moreinfo
Bug #950576 [network-manager] network-manager fails to correctly configure eth0 
speed and fails when autoneg is on
Added tag(s) moreinfo.

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

Bug#950576: [Pkg-utopia-maintainers] Bug#950576: network-manager fails to correctly configure eth0 speed and fails when autoneg is on

[Michael Biebl]

Control: severity -1 normal
Control: tags -1 moreinfo


Am 03.02.20 um 19:27 schrieb Eric Valette:
> 
> If I let eth0 in /etc/network/interface I get my eth0 card correctly 
> configured by ifplugd
> each time using full duplex and 1000Mbps
> 
> ethtool eth0
> Settings for eth0:
> Supported ports: [ TP ]
> Supported link modes:   10baseT/Half 10baseT/Full 
> 100baseT/Half 100baseT/Full 
> 1000baseT/Full 
> Supported pause frame use: No
> Supports auto-negotiation: Yes
> Supported FEC modes: Not reported
> Advertised link modes:  1000baseT/Full 
> Advertised pause frame use: No
> Advertised auto-negotiation: Yes
> Advertised FEC modes: Not reported
> Speed: 1000Mb/s
> Duplex: Full
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: on
> MDI-X: off (auto)
> Supports Wake-on: pumbg
> Wake-on: g
> Current message level: 0x0007 (7)
>drv probe link
> Link detected: yes
> 
> If I let network manager handle this interface and either set "allow autoneg" 
> or disable
> it and force  speed at 1000 I get no working interafce it keeps trying to 
> configure
> it in a loop.
> 
> The only config that works is:
> 1) disable autoneg
> 2) and set speed at 100Mbps
> 
> but this is not what I want and fisrt ethtool command shows the ethernet card 
> is capable
> of what I want.

Please provide a verbose debug log
https://wiki.gnome.org/Projects/NetworkManager/Debugging



signature.asc
Description: OpenPGP digital signature

Processed: libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find -lgcc_s

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: 
cannot find -lgcc_s
Added indication that 950579 affects src:glib2.0, src:xterm, src:hdrmerge, and 
src:esorex

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

Bug#950579: libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find -lgcc_s

[Simon McVittie]

Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Justification: FTBFS
Tags: ftbfs
Control: affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex

https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=s390x&ver=2.62.4-2&stamp=1580755175&file=log

> Package versions:
[with linebreaks added for legibility, quoting only the most
libgcc-adjacent packages]
> gcc_4:9.2.1-3.1
> gcc-10-base_10-20200202-1
> gcc-9_9.2.1-25
> gcc-9-base_9.2.1-25
> libgcc-9-dev_9.2.1-25
> libgcc-s1_10-20200202-1
> libgcc1_1:10-20200202-1
...
> Sanity check compiler command line: cc
> /<>/debian/build/deb/meson-private/sanitycheckc.c
> -o /<>/debian/build/deb/meson-private/sanitycheckc.exe
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
> -Wl,--no-as-needed -Wl,-O1
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> /usr/bin/ld: cannot find -lgcc_s
> collect2: error: ld returned 1 exit status
> 
> -
> 
> meson.build:1:0: ERROR: Compiler cc can not compile programs.

Presumably the dependencies and Breaks should be such that it isn't
possible to get into a situation where libgcc_s can't be linked.

Recent builds of xterm, hdrmerge and esorex show similar symptoms.

smcv

Bug#950579: libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find -lgcc_s

[Matthias Klose]

On 2/3/20 8:14 PM, Simon McVittie wrote:
>> Sanity check compile stderr:
>> /usr/bin/ld: cannot find -lgcc_s
>> collect2: error: ld returned 1 exit status

this is fixed in unstable. please retry the package build.

Bug#950579: libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find -lgcc_s

[Aurelien Jarno]

On 2020-02-03 20:21, Matthias Klose wrote:
> On 2/3/20 8:14 PM, Simon McVittie wrote:
> >> Sanity check compile stderr:
> >> /usr/bin/ld: cannot find -lgcc_s
> >> collect2: error: ld returned 1 exit status
> 
> this is fixed in unstable. please retry the package build.
> 

That won't work. For that we have to first regenerate the chroots on
s390x. We agreed to do that after gcc-9 9.2.1-27 is built. As it FTBFS,
we need to wait for 9.2.1-28 to build. We also need to wait for a
dinstall cycle.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#950134: marked as done (pyferret ftbfs with python 3.8 and pango from experimental)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 19:35:15 +
with message-id 
and subject line Bug#950134: fixed in pyferret 7.5.0-3
has caused the Debian Bug report #950134,
regarding pyferret ftbfs with python 3.8 and pango from experimental
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.)


-- 
950134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyferret
Version: 7.5.0-2
Severity: serious
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

pyferret ftbfs with python 3.8 and pango from experimental

patch at
http://launchpadlibrarian.net/462588871/pyferret_7.5.0-2build1_7.5.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: pyferret
Source-Version: 7.5.0-3

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 950...@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: Mon, 03 Feb 2020 18:13:37 +
Source: pyferret
Architecture: source
Version: 7.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 950134
Changes:
 pyferret (7.5.0-3) unstable; urgency=medium
 .
   * Use debhelper-compat (=12)
   * Use https homepage
   * Fix FTBFS with python3.8 and pango from experimental. Thanks
 to Matthias Klose. Closes: #950134
Checksums-Sha1:
 53a0d2062460be74db38091582c4d4e4a1641b41 2171 pyferret_7.5.0-3.dsc
 d358c65c474fb2210009362c26a7127c4ffc067f 12252 pyferret_7.5.0-3.debian.tar.xz
Checksums-Sha256:
 95bcf90c3f896098ee05c507675315d73558dabce089f41826171e0382295ef0 2171 
pyferret_7.5.0-3.dsc
 96a14fca09b4b0dc2b61a933808960f879a40f4f4104cf737b8c8e65230028d2 12252 
pyferret_7.5.0-3.debian.tar.xz
Files:
 cc2d0c296ed6b6f8047d8f967e3b1515 2171 science optional pyferret_7.5.0-3.dsc
 9fadccb72bfaa7446c00d21ea298a153 12252 science optional 
pyferret_7.5.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl44cqMACgkQy+a7Tl2a
06XVMxAApaXVMfzu9E4IrBfwqZNKGuV6NMzkTA0tmTck7XKfVBwIlM3lRnW6oV3Q
HPoQF+FtN+OkIFp+tLMGH8+UtqcbtGFIJAUyrjyZ4csL/+PZmtZMV7ZvgwkqCwrc
pfKTIwJpGVxSzYdOiGuZilnua3hr6KwUb7tOTCkf2//DWb8e4C1G8kNw3TYikSY0
KgXHvFNZ184OKolG6gAo2k7lN8ts5DWjFSE+3yExDrw38z1rPONicuSBz73uQAQR
swy17cIoK8YbKmcuGnwwppxtCS8lO43SIkWMyeqACow4dd6w8WNdx3fXYgcIpRSD
ojCJIMdNqFmTGiQGpJH934xr/9fhqK/Z3nRpyCpt38ivwz0rz8tS5ubxF5d/QOVK
FGFWOrCyjvP3ywtU2SoNzlLgXo0s8cL1xlYBvQ1/CsGtlVI2Ezzf/TtaEZF/n4J/
Uy1SKuWJGbZD/+RaSCjuW7ZeTrP7TNXF6NQ8M3qT79dGFG5Ao5h9KpimG5MhewDO
vsg2xRbl0SUzFcVpvnye3NlKwe+vNexl/syoUomDMdxNUZ7TbhZwS/GWwX12cb3N
OqBErxYbnZeZ6rHffZpcx4R4h4t85HJB8K4zws9Idw5VrXR/M6JIwaLq9w9taYpB
HJ2OebMMzcwv+drTmTdQjMV3NWlOhwKtatjkoJNUKc+a5rg+ITA=
=s8Ek
-END PGP SIGNATURE End Message ---

Bug#949134: marked as done (oasis3: FTBFS (Assigning non-zero to $[ is no longer possible at ../../protex/protex line 87.))

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 19:50:06 +
with message-id 
and subject line Bug#949134: fixed in oasis3 3.mct+dfsg.121022-14
has caused the Debian Bug report #949134,
regarding oasis3: FTBFS (Assigning non-zero to $[ is no longer possible at 
../../protex/protex line 87.)
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.)


-- 
949134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oasis3
Version: 3.mct+dfsg.121022-13
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

In preparation of the netcdf-fortran transition as test rebuild of your package 
was done which FTBFS:

 make doc
 make[4]: Entering directory 
'/build/oasis3-3.mct+dfsg.121022/lib/mct/doc/texsrc'
 perl ../../protex/protex -b  m_Accumulator.F90 > m_Accumulator.tex
 Assigning non-zero to $[ is no longer possible at ../../protex/protex line 87.
 make[4]: *** [Makefile:27: m_Accumulator.tex] Error 255

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: oasis3
Source-Version: 3.mct+dfsg.121022-14

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated oasis3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 14:41:44 +
Source: oasis3
Architecture: source
Version: 3.mct+dfsg.121022-14
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 949134
Changes:
 oasis3 (3.mct+dfsg.121022-14) unstable; urgency=medium
 .
   * Standards-Version: 4.4.1
   * Mark liboasis3-doc as M-A: foreign
   * Patch from Bas Couwenberg for protex FTBFS. Closes:  #949134
   * Patch to escape chars that break new protex patch
Checksums-Sha1:
 21a318acfc13acd0da79ee4a8d0106d9130388a9 2255 oasis3_3.mct+dfsg.121022-14.dsc
 e8ffb18bb8aaa77bec284c90be80648fea3f4a0f 16272 
oasis3_3.mct+dfsg.121022-14.debian.tar.xz
Checksums-Sha256:
 23c40fb94c05d8349324dbb9bee9adb2f35efef29d47fe688eefeab046355e66 2255 
oasis3_3.mct+dfsg.121022-14.dsc
 f13590855f45a2933bad99131c00491728b28543e0dbd8e7cd5b72204ce21ec6 16272 
oasis3_3.mct+dfsg.121022-14.debian.tar.xz
Files:
 b582773ec4597a8e24840132bf3cc8fd 2255 science optional 
oasis3_3.mct+dfsg.121022-14.dsc
 e774c1759ea934201536fc5e6169c3ff 16272 science optional 
oasis3_3.mct+dfsg.121022-14.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl44dm4ACgkQy+a7Tl2a
06V1mw//e/EsC/3ITSnjfckc9OVcZTYlp0pQHBjJcXBUEi+iY9FQrJM/lOxNK2yk
LtxO+tuQjPYpMWA21UOPKPugGlM/XjeSDe6Y4Xrrlt80XTkrea6f9oBQdwwdpv47
xgOY0zB7jrrxs6grDeRy6VgV7X1T/nmXjaq6vzbmM6/zsIVSl+LUhb2bf8L1WuFM
Oa73w7eJD2dlqngg3UdpodJAigCtt+++cD7g1aKTwPuHDz2KSQ0lZIwMP9PR8fnl
Deq77tIkL9sVCjMz+2H8pWRVsQKpqoIEiiYBsihxyqNpibGWa0yjL8ltjX0Cfhao
9OrPfmLxBuSRPLN6eGK/U1jkSvkf1hx0IlvRPlmZ7jvONwvNbQX/gNM6W1eCp+i7
9UEhg/5vipJsheQ2jvkvkLBGLlWIXSW842ebZUnzVBeTeeVbv5tX34KOpJIGMsdV
30RJ4ruS4QQLMY1mmewGNs3FYHNLGbgxkH7txU9XQYK1zbUVaPbSyTjCn82NpBpK
rqmLTbO8XCeI/RtxR14tKDaZjGUWmqcBHI21XFRRQ0jJFd4wV4dWTd1vHZplzwca
Vz/3vsgiy3+0S8wDnEUwZUF24V+3VgDzHlbkN92E4l1r7ak/RRNYcM/DUkhtFfCn
I2KRSH8bZ2iArLv/lgsO5PUE/R76eHD61weZbZxo7ugxdw+o6os=
=rZpp
-END PGP SIGNATURE End Message ---

Bug#949759: marked as done (bootcd: Missing build dependencies on python3-docutils and shellia)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 19:49:21 +
with message-id 
and subject line Bug#949759: fixed in bootcd 6.01
has caused the Debian Bug report #949759,
regarding bootcd: Missing build dependencies on python3-docutils and shellia
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=bootcd&arch=all&ver=6.00&stamp=1576857218&raw=0

...
 debian/rules build-indep
make[1]: Entering directory '/<>'
make[1]: rst2man: Command not found
make[1]: *** [Makefile:51: bootcdwrite.1] Error 127
--- End Message ---
--- Begin Message ---
Source: bootcd
Source-Version: 6.01

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

Debian distribution maintenance software
pp.
Bernd Schumacher  (supplier of updated bootcd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 12:57:13 +0100
Source: bootcd
Architecture: source
Version: 6.01
Distribution: unstable
Urgency: medium
Maintainer: Bernd Schumacher 
Changed-By: Bernd Schumacher 
Closes: 949759
Changes:
 bootcd (6.01) unstable; urgency=medium
 .
   * Fixed bug "bootcd: Missing build dependencies on python3-docutils and
 shellia" reported by Adrian Bunk . closes: 949759
   * some smaller fixes
Checksums-Sha1:
 492099adfb1da7cf432459d42f142dc9458f94b9 1484 bootcd_6.01.dsc
 595796438775254385f8dda4ffa3d74ac017de4a 72724 bootcd_6.01.tar.xz
 8fdb5e6b5b878e908b2e7901c19987a8be73ff1a 5728 bootcd_6.01_source.buildinfo
Checksums-Sha256:
 75c1c5e27c34aadf5c71110b85404448c0288cd3d3b7177afb53876fdd11f8d1 1484 
bootcd_6.01.dsc
 68ec4dba388e270bf968381feb9c8ca16593bf5db93addc5363ec6aedd745eb0 72724 
bootcd_6.01.tar.xz
 456bf834742f730523ab5ec972e66263f0c08967cba62637b00476f3b4446d8c 5728 
bootcd_6.01_source.buildinfo
Files:
 8135a7a6bbb805849eb6acbbdf437dd9 1484 utils extra bootcd_6.01.dsc
 935954f698705f2e4bd8edd1bd6fb4a6 72724 utils extra bootcd_6.01.tar.xz
 76bd82c1f8d6d59e5841ed74168469f4 5728 utils extra bootcd_6.01_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJNBAEBCAA3FiEEx5NNNf+H1Sb3l9vqxRmiDRIUYfcFAl44c/gZHGJlcm5kLnNj
aHVtYWNoZXJAaHBlLmNvbQAKCRDFGaINEhRh95DPD/4kRuNhWQOvE6fBo04ZS4Qk
UEOtEjFwqyaD2LQcOjC+Bw2r3gkyYlfhTK/yjtUro3OR1QpnUqipE295qLrZtr0x
NjwmMfspAJG11PqGwdnuTLimz6aX4+8eQooBTbDdksE89k4XQV/1e2+525HmG9pz
HGxea9h0+mFbiEyoT1DokQ/FVzy5XsmF28HwmmI/5oHQuNyHqB1CVx+AO3PTW5qL
oa/QAF8QFou+QrZICBmATpqbmi4P2TaBg582OB931MSpR5pTm+zg4DkCuU7Pc8r/
SgTEJbebfpynHBkFW0rpMK1dXy2P/OtpdWvEKkqsZ5+yg8BRPUgVALr7yzj6ECPn
+zWeCQr9UqfG7Tw6Wp0KUrRJc+YiD2FBqwGFJHl/tXpy1cBQMHEo+NPJel8VwN8h
y6o68fQY37/y6CwV+lkS3P2WAh21qPTptF+s/TkbPCp5K+9hJ0qYxKt2e1kvE1OD
hwl/aaaG2gU1lbnz+xvdTYYxR/zZX+5JP8JxUoNcl9bJsfolU/zm58/uZOBpEdVy
9IE6+7yp5ULAD0HuTPdZk0PW2XqxzeEfdhdEalAttiLP7fmP48Yr/lM9JeNGnCKL
wdDuiSBRAzxL9E2Tm61xY0SUEn8xq3JxiJc2nt3iAQOiIDVvXaZZRcmogDQicuW7
aDZky50IWg4oZwWEwI/txg==
=+bbz
-END PGP SIGNATURE End Message ---

Bug#946011: closing 946011

[Salvatore Bonaccorso]

notfound 946011 1.7.11-1+deb8u7
close 946011 2:2.2.8-1
thanks

Processed: python-django: CVE-2020-7471: Potential SQL injection via StringAgg(delimiter)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:1.11.27-1~deb10u1
Bug #950581 [src:python-django] python-django: CVE-2020-7471: Potential SQL 
injection via StringAgg(delimiter)
Marked as found in versions python-django/1:1.11.27-1~deb10u1.

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

Processed: closing 946011

[Debian Bug Tracking System]

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

> notfound 946011 1.7.11-1+deb8u7
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version 
'1.7.11-1+deb8u7' with architecture ''
Unable to make a source version for version '1.7.11-1+deb8u7'
No longer marked as found in versions 1.7.11-1+deb8u7.
> close 946011 2:2.2.8-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:2.2.8-1' 
with architecture ''
Unable to make a source version for version '2:2.2.8-1'
Ignoring request to alter fixed versions of bug #946011 to the same values 
previously set
Bug #946011 [python-django] python-django: CVE-2019-19118
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#950581: python-django: CVE-2020-7471: Potential SQL injection via StringAgg(delimiter)

[Salvatore Bonaccorso]

Source: python-django
Version: 2:2.2.9-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:1.11.27-1~deb10u1

Hi,

The following vulnerability was published for python-django.

CVE-2020-7471[0]:
| Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3
| allows SQL Injection if untrusted data is used as a StringAgg
| delimiter (e.g., in Django applications that offer downloads of data
| as a series of rows with a user-specified column delimiter). By
| passing a suitably crafted delimiter to a
| contrib.postgres.aggregates.StringAgg instance, it was possible to
| break escaping and inject malicious SQL.


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-7471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7471
[1] https://www.djangoproject.com/weblog/2020/feb/03/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#950301: Fixed upstream in 0.10.0

[Fiona Klute]

This issue has been fixed in upstream version 0.10.0 (out just now).

This is caused by recent GnuTLS versions (since 3.6.11 AFAIK) listing
the peer's certificate type in the session description so they aren't
identical on anonymous client and authenticated server, so backporting
shouldn't be necessary.

Bug#950032: Use python3 in build script

[Daniel Moran]

The issue seems to stem from the fact the python3 package(s) do not
provide /usr/bin/python.

I've attached a patch which should fix builds which use either the
CMakeList.txt file, or the ./configure.py script.

This is only an initial change, as I haven't been able to try it out,
but should force the use of python3 rather than relying on
/usr/bin/python to point to the correct place.

Regards,
Dan
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 440eab076509..9ce9b51f2042 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -158,7 +158,7 @@ if( ENABLE_RUNTIME_SUBNORMAL )
DESTINATION ${CMAKE_INSTALL_DATADIR}/clc )
 endif()
 
-find_program( PYTHON python )
+find_program( PYTHON python3 )
 file( TO_CMAKE_PATH ${CMAKE_SOURCE_DIR}/generic/lib/gen_convert.py script_loc )
 add_custom_command(
OUTPUT convert.cl
diff --git a/configure.py b/configure.py
index dab5dc94dfab..cd2a48235436 100755
--- a/configure.py
+++ b/configure.py
@@ -151,7 +151,7 @@ b.build(prepare_builtins, "LLVM_TOOL_LINK",
 
 b.rule("PREPARE_BUILTINS", "%s -o $out $in" % prepare_builtins,
'PREPARE-BUILTINS $out')
-b.rule("PYTHON_GEN", "python < $in > $out", "PYTHON_GEN $out")
+b.rule("PYTHON_GEN", "python3 < $in > $out", "PYTHON_GEN $out")
 b.build('generic/lib/convert.cl', "PYTHON_GEN", ['generic/lib/gen_convert.py'])
 
 manifest_deps = set([sys.argv[0], os.path.join(srcdir, 'build', 
'metabuild.py'),

Bug#933441: marked as done (pcsx2: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 21:21:34 +
with message-id 
and subject line Bug#933441: fixed in pcsx2 1.5.0~gfc1d9aef0+dfsg-2
has caused the Debian Bug report #933441,
regarding pcsx2: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Source: pcsx2
Source-Version: 1.5.0~gfc1d9aef0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated pcsx2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 21:00:01 +
Source: pcsx2
Architecture: source
Version: 1.5.0~gfc1d9aef0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Graham Inggs 
Closes: 933441
Changes:
 pcsx2 (1.5.0~gfc1d9aef0+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Switch to GTK3 (Closes: #933441)
Checksums-Sha1:
 e66c0b64627cf749e58ecec19155df94cdbce2a5 2247 pcsx2_1.5.0~gfc1d9aef0+dfsg-2.dsc
 4adf4607ac0b88540ad1cd5157f5dad551c7a21c 10744 
pcsx2_1.5.0~gfc1d9aef0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 baf9521be32c950df2c80b0ec1864b07b1f33233d938d7ae0d560022773e5dd4 2247 
pcsx2_1.5.0~gfc1d9aef0+dfsg-2.dsc
 c92a1e99a87caad1377a1cc558fb1bfc828481c5f4e4a1d33967d198c09fe46d 10744 
pcsx2_1.5.0~gfc1d9aef0+dfsg-2.debian.tar.xz
Files:
 479e193ff5406fb4ebcf2c486cbaad8a 2247 games optional 
pcsx2_1.5.0~gfc1d9aef0+dfsg-2.dsc
 9e10760537b51da31ba8abc517bef166 10744 games optional 
pcsx2_1.5.0~gfc1d9aef0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl44iqEACgkQr8/sjmac
4cKc/Q//c614pqPYLGkp+rGx0Cf5hVC2sRKHw4/yngRoqXCEwrMvZsNoGv+ovv4k
rM8o5ovTGSgwy4jUXyOtAzwTpwEIQjtMkoy6VqgYzvyIlEDR9RHb0Q8tqouQWKXg
cT0U4GVAhbBh6M+zXrK5mpgBZuiuyFlkpn/wCEJVbhQT7Jcx6ZNEqKsxwtqS/3Pw
NpRzxYW5Nk0YpalxvTMMTaWlvTBaEO/43xyVR3eMFVO6IJofJxtQ5OFX7u8zZbVv
iylvYwBDDGqbPZuTp2ysPSzuQEKjc2HKnRpYgJtyS0yzNBEGyTHf/lNLgMjwJWkS
8DrNQLXKOow1VgTgaMJNnr60IrCpJv6Nwxdu6blzym4Pn1ck+N+BNhScPEG6fayz
toWurNpKqj86Grom7+Hak7AQAate/wYpb5vZRWKYu07NwFOrEsEN7I7TqGx+opw1
TXPdNmsdkFtp0KFpZFC1hhklen+DRbV3DQ4/2+h52uePxBZJqyZPyz4LVNX0BADK
jO7F3581y1erGkx5ib1cRmUzbBWWXDhE0naZUZvb56xOuzDa2ooo3T2/FiDIjWkM
9B5S6M/y6uFQKDdkvklmOWWTVRkg5OHT8cD+lVzqJdNqB2yDO8yY2AJGMp7CYuYA
vhw9cq4AaQNmaOmMd8znOERCZQ5cegTR91mwHr32rBscMNWDMeg=
=5Ti5
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 950408 1.3.7-2
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Marked as fixed in versions fwupd/1.3.7-2.
> fixed 950407 1.3.7-2
Bug #950407 [fwupd] fwupd-refresh.service contains @bindir breaking the unit 
file
Marked as fixed in versions fwupd/1.3.7-2.
> close 950408 1.3.7-2
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Ignoring request to alter fixed versions of bug #950408 to the same values 
previously set
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Marked Bug as done
> close 950407 1.3.7-2
Bug #950407 [fwupd] fwupd-refresh.service contains @bindir breaking the unit 
file
Ignoring request to alter fixed versions of bug #950407 to the same values 
previously set
Bug #950407 [fwupd] fwupd-refresh.service contains @bindir breaking the unit 
file
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[Nico Alt]

I can confirm this bug. After doing an apt full-upgrade, I faced the
same issue as OP. However, I was not able to fix it by downgrading
packages, but instead used a similar approach to the way described in
the btrfs bug #950556 [1].

After chrooting into the system, I changed the following file:

$ diff /usr/share/initramfs-tools/hooks/cryptroot.backup
/usr/share/initramfs-tools/hooks/cryptroot
416c416
< find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while
read so; do
---
> find -L "/lib" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do

After this, I updated initramfs with "update-initramfs -u -k all".

Note: for this to work cleanly, you need to bind proc, dev etc. and you
need to open your encrypted volume with the same name as described in
your system's /etc/crypttab. The commands I used:

sudo cryptsetup open /dev/sda5 sda5_crypt
[...]
sudo mount --bind /dev /mnt/dev
[...]

Cheers

Nico


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556

Bug#950594: flang FTBFS: dwz: Too many DIEs, not optimizing

[Adrian Bunk]

Source: flang
Version: 20190329-4
Severity: serious
Tags: ftbfs

...
   dh_dwz -O--buildsystem=cmake 
-O--builddirectory=/tmp/flang-20190329/debian/build
install -d debian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz -mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug -- 
debian/flang-7/usr/bin/flang-7 debian/flang-7/usr/bin/flang1 
debian/flang-7/usr/bin/flang2
dwz: debian/flang-7/usr/bin/flang-7: Too many DIEs, not optimizing
dwz: debian/flang-7/usr/bin/flang1: DWARF compression not beneficial - old size 
2259002 new size 2265054
dh_dwz: error: dwz 
-mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug -- 
debian/flang-7/usr/bin/flang-7 debian/flang-7/usr/bin/flang1 
debian/flang-7/usr/bin/flang2 returned exit code 1
make: *** [debian/rules:14: binary] Error 25

Bug#950565: marked as done (kalgebra FTBFS on architectures without qtwebengine5-dev)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 23:07:01 +
with message-id 
and subject line Bug#950565: fixed in kalgebra 4:19.12.1-2
has caused the Debian Bug report #950565,
regarding kalgebra FTBFS on architectures without qtwebengine5-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.)


-- 
950565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kalgebra
Version: 4:19.12.1-1
Severity: serious
Tags: ftbfs

Looks like a problem with the override_dh_auto_configure:

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

...
make[1]: Entering directory '/<>'
DMOBILE_BACKEND="none"
make[1]: Leaving directory '/<>'
   dh_auto_build --buildsystem=kf5 -a
cd obj-powerpc64le-linux-gnu && make -j8 "INSTALL=install 
--strip-program=true"
dh_auto_build: error: chdir("obj-powerpc64le-linux-gnu") failed: No such file 
or directory
dh_auto_build: error: cd obj-powerpc64le-linux-gnu && make -j8 "INSTALL=install 
--strip-program=true" returned exit code 25
make: *** [debian/rules:18: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: kalgebra
Source-Version: 4:19.12.1-2

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

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

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

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated kalgebra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 23:09:09 +0100
Source: kalgebra
Architecture: source
Version: 4:19.12.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Aurélien COUDERC 
Closes: 950565
Changes:
 kalgebra (4:19.12.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS on architectures without qtwebengine5-dev. (Closes: #950565)
   * Bump Standards-Version to 4.5.0, no change required.
Checksums-Sha1:
 f2ab7dbb4d1c3694c57d32e7916eaffbebf9bc8a 2936 kalgebra_19.12.1-2.dsc
 cdfb2469dbc1392155bd20fd82cebb3a53f611d4 10080 kalgebra_19.12.1-2.debian.tar.xz
 5277fd011dd7f3eb0367af718f28632bf5e76179 19867 
kalgebra_19.12.1-2_amd64.buildinfo
Checksums-Sha256:
 9200302889e17033796cb700258e99fe272fda2391c4d93d2f2fa8241ebd3d96 2936 
kalgebra_19.12.1-2.dsc
 749e31adfa04a6109f72db3ec195de4529bda3fc1de7944df22b8f2b8071116e 10080 
kalgebra_19.12.1-2.debian.tar.xz
 3e954ed146c0d29ceb367e55d041744514cabaae01e0113f2e2df2caa3fe5086 19867 
kalgebra_19.12.1-2_amd64.buildinfo
Files:
 904aa02289bb0307c5b967a34824672c 2936 kde optional kalgebra_19.12.1-2.dsc
 97db15cf712bd7cf662205c87438b438 10080 kde optional 
kalgebra_19.12.1-2.debian.tar.xz
 e20a1ebf8aa87f266317ae3e420083e1 19867 kde optional 
kalgebra_19.12.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl44mkwTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJIS8EADcKEgcCi0YZhl+2sHTVliXVW1BErPH
zaUoSF9OEfQRD6V6Kyv3seHkPRitqV0OL1Q+Ahuo1YsBBBIPM+WFv3CPTjrukzmU
dtWxnbUGA49ctsuNzzfcwTpQvGq5xvYnD1HkPjyHz5eovcJ7MlmLbXCSk6B6Wk3Y
LTNUrizCA7eMtYTEwHZN01wlL8Vcyi+rWLeBwm8uX0kcTvccz2ky6I4bvrhLUX+F
8z5+/MfH8wfQeHFqkTJUsXo+s6/c3lJdkf7AfLaXLjinCZdNm2HayJ/7jl2l3dbu
8zhjqjWj3NhFisW7lIElKXHvABnvJ8gpVHCS0d0m/u2Kndj2NLwrmvWAGw89SsUY
SRY2cVSoHOGP4fNeOE7n4OS3E7XaBWZhXKC0BAInwFKuvaEph1AzreaXjEnjV/4J
jiSTZv331AWg26Yrse57XpsHvx5DYaZRxlBr2Fbwpkt3A2xLIEGHaPjXGUBtRj7E
4+6gmMPPILY2RMDQUe5QSxlOP8Um/Aftg4ItaGWBtedrszfyuYH4ifwgirEBp8Aq
qbmcwLR6teInWb88js5Hcgk0M5WfeZeeW/Of5aDe0gLK279MpmKB9f8Xd2q+MGKA
X/dpXUDkhT7Z0JPjkuw5VNqpzgWFMwMjngiukoFLVTQLmVjGsTNNTS44J8DiJZ4M
TowpkjMsrTodag==
=w6VB
-END PGP SIGNATURE End Message ---

Processed: Bug#950533 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950533 [systemd] upgrade fails in a chroot without mounted /proc
Added tag(s) pending.

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

Bug#950533: marked as pending in systemd

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #950533 in systemd 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/systemd-team/systemd/commit/8b0e049febdd5a259aa14e11bcc319ca581c72d4


Don't fail upgrade if /proc is not mounted

Applying ACLs on /var/log/journal via systemd-tmpfiles requires a
mounted /proc. Skip this step if /proc is not available, e.g. in a
chroot.

Closes: #950533


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950533

Bug#950533: marked as done (upgrade fails in a chroot without mounted /proc)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 23:35:07 +
with message-id 
and subject line Bug#950533: fixed in systemd 244.1-3
has caused the Debian Bug report #950533,
regarding upgrade fails in a chroot without mounted /proc
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.)


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

Hi folks,

I'm guessing this is fallout from enabling persistent journal by
default, maybe. I have a development box running multiple chroots, and
ths sid chroots are now failing to upgradw with the following errors:

Upgrading from 240-5 to 244.1-2:

...
Need to get 0 B/5987 kB of archives.
After this operation, 444 kB of additional disk space will be used.
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Setting up systemd (244.1-2) ...
[/usr/lib/tmpfiles.d/systemd-tmp.conf:11] Failed to replace specifiers: 
/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/systemd-tmp.conf:12] Failed to replace specifiers: 
/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/systemd-tmp.conf:13] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/systemd-tmp.conf:14] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/systemd-tmp.conf:22] Failed to replace specifiers: 
/var/lib/systemd/coredump/.#core*.%b*
ACL operation on "/var/log/journal" failed: No such file or directory
ACL operation on "/var/log/journal" failed: No such file or directory
Failed to re-open '/var/log/journal': No such file or directory
fchmod() of /var/log/journal failed: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 73
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

I don't have a /var/log/journal in those chroots.

-- Package-specific info:

-- System Information:
Debian Release: 10.2
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-7~deb10u2
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-1
ii  libpam-systemd  241-7~deb10u2

Versions of packages systemd suggests:
ii  policykit-10.105-25
ii  systemd-container  241-7~deb10u2

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133+deb10u1
ii  udev 241-7~deb10u2

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 244.1-3

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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 MESSA

Bug#950024: marked as pending in ruby-github-markdown

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-github-markdown/commit/ff201826b489b731f5a94922ba8bd826e6a333d3


Fix typo introduced in debian/rules in 0.6.9-4 preventing the non-installation 
of tool gfm (Closes: #950024)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950024

Processed: Bug#950024 marked as pending in ruby-github-markdown

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950024 [ruby-github-markdown] ruby-github-markdown: ships /usr/bin/gfm 
already provided by the gfm package
Added tag(s) pending.

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

Bug#937507: marked as done (pypng: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 03 Feb 2020 23:49:58 +
with message-id 
and subject line Bug#937507: fixed in pypng 0.0.20+ds-2
has caused the Debian Bug report #937507,
regarding pypng: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pypng

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pypng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 11:20:46 -0500
Source: pypng
Architecture: source
Version: 0.0.20+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Sascha Steinbiss 
Changed-By: Sandro Tosi 
Closes: 937507
Changes:
 pypng (0.0.20+ds-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #937507
Checksums-Sha1:
 14b5494691000b27854091fa44b6d8332269ed15 1889 pypng_0.0.20+ds-2.dsc
 9351aa3ca44dfeeb97c6cf7cf58fce8419aee38a 3060 pypng_0.0.20+ds-2.debian.tar.xz
 be8477eb56c90065eace8f837d700fcf2ba2dc56 6336 
pypng_0.0.20+ds-2_source.buildinfo
Checksums-Sha256:
 d9e6273902ab3ad9a8d74cabbce984cf09c7de9e83322c55c40225811a53c12b 1889 
pypng_0.0.20+ds-2.dsc
 9fbe86c684491b0a970ec0e0355af7cb2acd1d831864d4332568e516c1b3016f 3060 
pypng_0.0.20+ds-2.debian.tar.xz
 b0d8429e0a5a5f954295a15185a0240afae6c41637250b1f7cab088cadbca5bb 6336 
pypng_0.0.20+ds-2_source.buildinfo
Files:
 93858e77ec6fea1d34348c18442c397f 1889 python optional pypng_0.0.20+ds-2.dsc
 714f1cc9b0c89398dc

Bug#950024: marked as done (ruby-github-markdown: ships /usr/bin/gfm already provided by the gfm package)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 00:35:10 +
with message-id 
and subject line Bug#950024: fixed in ruby-github-markdown 0.6.9-5
has caused the Debian Bug report #950024,
regarding ruby-github-markdown: ships /usr/bin/gfm already provided by the gfm 
package
to be marked as done.

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

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


-- 
950024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-github-markdown
Version: 0.6.9-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package ruby-github-markdown.
  Preparing to unpack .../18-ruby-github-markdown_0.6.9-4_amd64.deb ...
  Unpacking ruby-github-markdown (0.6.9-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-YI7FMa/18-ruby-github-markdown_0.6.9-4_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/gfm', which is also in package gfm 1.08-1+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-YI7FMa/18-ruby-github-markdown_0.6.9-4_amd64.deb


cheers,

Andreas


gfm=1.08-1+b1_ruby-github-markdown=0.6.9-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-github-markdown
Source-Version: 0.6.9-5

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

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

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-github-markdown 
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, 04 Feb 2020 00:17:09 +0100
Source: ruby-github-markdown
Architecture: source
Version: 0.6.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 950024
Changes:
 ruby-github-markdown (0.6.9-5) unstable; urgency=medium
 .
   * Fix typo introduced in debian/rules in 0.6.9-4 preventing the
 non-installation of tool gfm (Closes: #950024)
   * Bump Standards-Version to 4.5.0 (no changes needed)
   * Set Testsuite to autopkgtest-pkg-ruby and don't require root for d/rules
Checksums-Sha1:
 f7fcfa99a9b5fbf35bed0041307b2de71dd27ced 1783 ruby-github-markdown_0.6.9-5.dsc
 bcf306391b7bdb6f8e08ea0164e2e78a38026dbc 4276 
ruby-github-markdown_0.6.9-5.debian.tar.xz
 036903fc91c5f3db96dd075c483cf6d7d30171d3 13956 
ruby-github-markdown_0.6.9-5_source.buildinfo
Checksums-Sha256:
 106d9dff50ccafabda4758b18df31e11cb04f427833dcd923cd6bebd5c5187ae 1783 
ruby-github-markdown_0.6.9-5.dsc
 0da4c6c85947de7d96d1ecdd31f1d0858477bc5830bb29abd5021cf358520243 4276 
ruby-github-markdown_0.6.9-5.debian.tar.xz
 c97ef160f1429881fabd2d36f2b2ada512e18a120c8ac0912174a597921a50e8 13956 
ruby-github-markdown_0.6.9-5_source.buildinfo
Files:
 dd57ea79a23396dae9c6cae7679d333d 1783 ruby optional 
ruby-github-markdown_0.6.9-5.dsc
 da12b215f55b6ae46fd2f5b5538ea844 4276 ruby optional 
ruby-github-markdown_0.6.9-5.debian.tar.xz
 3b09380340887647ace3569b1b532ec4 13956 ruby optional 
ruby-github-markdown_0.6.9-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAl44sUMACgkQia+CtznN
IXqSEQf+Iw6rk5NNoOG/GKOiTfvTec4y5mUlabQaFat0l+J6zVuXiqYFgsca2zsI
vDEuZx47ca6vhVt05aa9sRp9MLwSWOlHSqWFSxFKTc6QuLd2ZyV5wqgF/o22gPZ1
UXQa18RUea/1TP4PeQRzHGxQQaGoZBsXfoyzGPauIBoZoBPx6RJ2s012omVpPK+G
3Q9j6SocFOKYze0+S+ayt31Y0fEyFB9XuRHc0mkMMnL1svUzzmVpmU0QDhxBZ53g
6UOXGSAyYxumZPidK4ScN0wKLew0E4YOZSxMmSu09qXx/QWSG6KJaETnKDrm7EJo
GHiLsac3Mnu8EIsDS2h433bEUewbPQ==
=7M2I
-END PGP SIGNATURE End Message ---

Bug#950598: python3-jupyter-sphinx: package relies on unavailable `ipywidgets.embed` module

[Sebastian Luque]

Package: python3-jupyter-sphinx
Version: 0.2.3-1
Severity: grave

Dear Maintainer,

The package is unuseable, as it relies on the `ipywidgets.embed` module,
which is unavailable in the latest sid version:

Extension error:
Could not import extension jupyter_sphinx.execute (exception: No module named 
'ipywidgets.embed')


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

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

Versions of packages python3-jupyter-sphinx depends on:
ii  python3 3.7.5-3
ii  python3-ipython 5.8.0-2
ii  python3-ipywidgets  6.0.0-6
ii  python3-nbconvert   5.6.1-1
ii  python3-nbformat5.0.4-1
ii  python3-sphinx  1.8.5-5

python3-jupyter-sphinx recommends no packages.

python3-jupyter-sphinx suggests no packages.

-- no debconf information

Processed: 950579: affects octomap

[Debian Bug Tracking System]

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

> affects 950579 src:octomap
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: 
cannot find -lgcc_s
Added indication that 950579 affects src:octomap
>
End of message, stopping processing here.

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

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[William Leung]

Package: libgcc1
Version: 1:10-20200202-1
Followup-For: Bug #950551

Same here. Did apt dist-upgrade and rebooted, then the libgcc_s.so.1 error
message appeared.

Tried OP method and worked:
1) Boot to an Ubuntu live USB
2) sudo cryptsetup open ...
3) chroot
4) Downgrade libgcc1 from 1:10-20200202-1 to 1:9.2.1-25
5) update-initramfs -u

After system restored, I upgraded libgcc1 again to reconfirm the problem.
This time, instead of downgrading libgcc1 in step 4, I just made symbolic link
to the file /lib/libgcc_s.so.1 under /lib/x86_64-linux-gnu/
This also worked for me.



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

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

Versions of packages libgcc1 depends on:
ii  gcc-10-base  10-20200202-1
ii  libc62.29-9
ii  libgcc-s110-20200202-1

libgcc1 recommends no packages.

libgcc1 suggests no packages.

Bug#885213: make-dfsg: please migrate to guile-2.2

[Rob Browning]

Actually now that guile-3.0 is in sid (though it's not yet building on
all the release architectures), I suppose we might just side-step 2.2
entirely, but either would be much appreciated.

Here this at least builds via "fakeroot debian/rules binary", but
regardless, I'd really like to resolve this soon.  I'm happy to make an
NMU if that's preferable.

Thanks

$ git diff
diff --git a/configure.ac b/configure.ac
index 02481ec..476f549 100644
--- a/configure.ac
+++ b/configure.ac
@@ -168,7 +168,7 @@ AC_ARG_WITH([guile], [AS_HELP_STRING([--with-guile],
 # comes with it's own PC file so we have to specify them as individual
 # packages.  Ugh.
 AS_IF([test "x$with_guile" != xno],
-[ PKG_CHECK_MODULES([GUILE], [guile-2.0], [have_guile=yes],
+[ PKG_CHECK_MODULES([GUILE], [guile-3.0], [have_guile=yes],
   [PKG_CHECK_MODULES([GUILE], [guile-1.8], [have_guile=yes],
 [have_guile=no])])
 ])
diff --git a/debian/control b/debian/control
index e251b40..3588b46 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Standards-Version: 4.1.3
 Homepage: https://www.gnu.org/software/make/
 Build-Depends: gettext, po-debconf, debhelper (>= 9.0.0), dh-autoreconf,
autoconf, automake | automaken, autopoint, file, pkg-config,
-   guile-2.0-dev, procps, libbsd-resource-perl 
+   guile-3.0-dev, procps, libbsd-resource-perl 

 Package: make
 Suggests: make-doc

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#949894: marked as done (quiterss: Segmentation fault at start)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 05:17:52 +
with message-id 
and subject line Bug#949894: fixed in quiterss 0.19.3+dfsg-1
has caused the Debian Bug report #949894,
regarding quiterss: Segmentation fault at start
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.)


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

Package: quiterss
Version: 0.19.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when I try to start quiterss I get a segmentation fault

I try:

***
1) to execute from command line:

$ quiterss &
[1] 22703
[1]+  Errore di segmentazione quiterss



***
2) to see what I can get using the debug symbols package and gdb:

$ gdb quiterss
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from quiterss...
Reading symbols from 
/usr/lib/debug/.build-id/73/ce3f81b45ac6dc622ccd7476886a63f1aadf32.debug...

(gdb) run
Starting program: /usr/bin/quiterss
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2373
2373	../sysdeps/x86_64/multiarch/memcpy-ssse3.S: File o directory non 
esistente.

(gdb) bt
#0  0x7371bd4b in __memcpy_ssse3 () at 
../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2373
#1  0x73af29e6 in QString::append(QString const&) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x5567826e in QString::operator+=(QString const&) (s=..., 
this=0x7fffd918) at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:483
#3  0x5567826e in operator+(QString const&, char const*) 
(s2=0x5572d0e9 "/debug.log", s1=...) at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1357
#4  0x5567826e in LogFile::msgHandler(QtMsgType, 
QMessageLogContext const&, QString const&) (type=QtInfoMsg, msg=...) at 
src/application/logfile.cpp:40

#5  0x73a6b4d1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x73a6ca8d in qt_message_output(QtMsgType, 
QMessageLogContext const&, QString const&) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x73b5d090 in QDebug::~QDebug() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7424fc2a in 
QGuiApplicationPrivate::createPlatformIntegration() () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x74251c30 in 
QGuiApplicationPrivate::createEventDispatcher() () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x73c39035 in QCoreApplicationPrivate::init() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7425399f in QGuiApplicationPrivate::init() () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x7789d4d9 in QApplicationPrivate::init() () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x556fe0b2 in QtSingleApplication::QtSingleApplication(int&, 
char**, bool) (this=0x7fffddf0, argc=, 
argv=, GUIenabled=)

at 3rdparty/qtsingleapplication/qtsingleapplication.cpp:154
#14 0x55675b88 in MainApplication::MainApplication(int&, char**) 
(this=0x7fffddf0, argc=@0x7fffddec: 1, argv=) at 
src/application/mainapplication.cpp:30
#15 0x555c52d4 in main(int, char**) (argc=, 
argv=0x7fffdfb8) at src/main/main.cpp:40

(gdb) n

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) q



***
3) to get a backtrace recompiling quiterss with nostrip[¹]

$ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' 
-ex 'thread apply all bt full' --args quiterss

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffed901700 (LWP 34164)]

Processed: fixed 950089 in 1.0.2-1

[Debian Bug Tracking System]

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

> fixed 950089 1.0.2-1
Bug #950089 [src:node-chrome-trace-event] node-chrome-trace-event FTBFS: error 
TS2300: Duplicate identifier 'IteratorResult'
Marked as fixed in versions node-chrome-trace-event/1.0.2-1.
> thanks
Stopping processing here.

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