Processed: reopening 959075

[Debian Bug Tracking System]

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

> reopen 959075
Bug #959075 {Done: Paul Wise } [ifenslave] ifupdown: Bonding 
is not working with ifenslave 2.10 wich removes ifenslave command
Bug #959236 {Done: Paul Wise } [ifenslave] Bringing up a bond 
results in an infinite loop
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ifenslave/2.10+nmu2.
No longer marked as fixed in versions ifenslave/2.10+nmu2.
> thanks
Stopping processing here.

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

Processed: severity of 963746 is important, tagging 963746 ...

[Debian Bug Tracking System]

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

> severity 963746 important
Bug #963746 [nfs-common] nfs-common: Random Segmentation Violations of rpc.gssd 
Daemon
Severity set to 'important' from 'critical'
> tags 963746 + upstream
Bug #963746 [nfs-common] nfs-common: Random Segmentation Violations of rpc.gssd 
Daemon
Added tag(s) upstream.
> forwarded 963746 
> https://lore.kernel.org/linux-nfs/406fe972135846dc8a23b60be59b0...@tu-berlin.de/
Bug #963746 [nfs-common] nfs-common: Random Segmentation Violations of rpc.gssd 
Daemon
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-nfs/406fe972135846dc8a23b60be59b0...@tu-berlin.de/'.
> thanks
Stopping processing here.

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

Bug#963713: marked as done (net-snmp: CVE-2019-20892)

[Debian Bug Tracking System]

Your message dated Thu, 02 Jul 2020 04:03:34 +
with message-id 
and subject line Bug#963713: fixed in net-snmp 5.8+dfsg-3
has caused the Debian Bug report #963713,
regarding net-snmp: CVE-2019-20892
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.)


-- 
963713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: net-snmp
Version: 5.8+dfsg-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for net-snmp.

CVE-2019-20892[0]:
| net-snmp before 5.8.1.pre1 has a double free in
| usm_free_usmStateReference in snmplib/snmpusm.c via an SNMPv3 GetBulk
| request. NOTE: this affects net-snmp packages shipped to end users by
| multiple Linux distributions, but might not affect an upstream
| release.

See [1] for the CVE heads-up post, and [2] the Launchpad Bug where the
issue originally is tracked from. The issue can be verified with:

| # systemctl stop snmpd.service
| # cat >> /var/lib/snmp/snmpd.conf << __EOF__
| createUser testuser SHA "testpass" AES "testpass"
| __EOF__
| # cat >> /etc/snmp/snmpd.conf << __EOF__
| rwuser testuser
| __EOF__
| # systemctl start snmpd.service
| # snmpbulkget -v3 -Cn1 -Cr1472 -l authPriv -u testuser -a SHA -A testpass -x 
AES -X testpass 127.0.0.1 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.7

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-2019-20892
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20892
[1] https://www.openwall.com/lists/oss-security/2020/06/25/4
[2] https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1877027

Please adjust the affected versions in the BTS as needed, I'm not sure
where the issue has been introduced, but possibly does not affect
indeed older suites (please do double check).

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: net-snmp
Source-Version: 5.8+dfsg-3
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated net-snmp 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: Thu, 02 Jul 2020 13:38:58 +1000
Source: net-snmp
Architecture: source
Version: 5.8+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Net-SNMP Packaging Team 
Changed-By: Craig Small 
Closes: 792832 905668 944336 944953 953044 963713 964054
Changes:
 net-snmp (5.8+dfsg-3) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Improve cross building: (Closes: #944953)
 + Build-Depends: perl-xs-dev for building a perl extension.
 + cross.patch: Detect mysql using pkg-config.
 .
   [ Craig Small ]
   * Log ipv6 error once Closes: #944336
   * Move net-snmp-create-v3-user to snmpd Closes: #953044
   * snmpd: Quiet on access errors to mounts Closes: #792832
   * snmpd: swinst_apt: Don't use dpkg directories Closes: #905668
   * libsnmp: Fix double free crash CVE-2019-20892 Closes: #963713
   * Enable TLS and DTLS transports Closes: #964054
Checksums-Sha1:
 b4b3d05648df63213e1650bff45508240384140f 2812 net-snmp_5.8+dfsg-3.dsc
 5e3e11fe7c94623fce06d7a1fa3932e16c7889e4 69736 
net-snmp_5.8+dfsg-3.debian.tar.xz
 0b5ac7fb78d43a727128a24da54420a25c9714eb 10018 
net-snmp_5.8+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 e04045dd533dfbc5f685e704602b7e779bda1d2437c27f3ba6b577a45231da6f 2812 
net-snmp_5.8+dfsg-3.dsc
 9f37979e06d43e2c75d9fae9773256135ff62cdf8f2e46f128471104d0fc1c29 69736 
net-snmp_5.8+dfsg-3.debian.tar.xz
 9bba88f5d9819a02e1d8a2553af10573d6bf2a3523b221e61e880d75eb20160d 10018 
net-snmp_5.8+dfsg-3_amd64.buildinfo
Files:
 83aecdf14d294faba634dddb15aad344 2812 net optional net-snmp_5.8+dfsg-3.dsc
 55348703bd383888bd9d14f959a91842 69736 net optional 
net-snmp_5.8+dfsg-3.debian.tar.xz
 2ea51d6edc8ca7fb8dba6ef3f398aec8 10018 net optional 

Processed: reassign 964111 to dpkg

[Debian Bug Tracking System]

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

> reassign 964111 dpkg
Bug #964111 [dpkg-source] dpkg-source: False positive 'points outside source 
root'
Warning: Unknown package 'dpkg-source'
Bug reassigned from package 'dpkg-source' to 'dpkg'.
Ignoring request to alter found versions of bug #964111 to the same values 
previously set
Ignoring request to alter fixed versions of bug #964111 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: dpkg-source: False positive 'points outside source root'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dpkg-source: False positive 'points outside source root'
Bug #964111 [dpkg-source] dpkg-source: Uninitialized value $canon_pathname
Warning: Unknown package 'dpkg-source'
Changed Bug title to 'dpkg-source: False positive 'points outside source root'' 
from 'dpkg-source: Uninitialized value $canon_pathname'.
Warning: Unknown package 'dpkg-source'
> severity -1 serious
Bug #964111 [dpkg-source] dpkg-source: False positive 'points outside source 
root'
Warning: Unknown package 'dpkg-source'
Severity set to 'serious' from 'minor'
Warning: Unknown package 'dpkg-source'

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

Bug#956691: marked as done (psi: Please witch to enchant-2 instead of enchant(1))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 21:52:11 +
with message-id 
and subject line Bug#956691: fixed in psi 1.3-6
has caused the Debian Bug report #956691,
regarding psi:  Please witch to enchant-2 instead of enchant(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.)


-- 
956691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi
Version: 1.3-5
Severity: important
Control: block 947979 by -1

Hello,

Could you please switch from enchant(1) to the enchant-2 library?

We are trying to get rid of enchant(1) for the bullseye release.

I see some support for enchant2, but switching the build-dependency to
libenchant-2-dev is not enough as the "debian-changes" is reverting
changing the pkg-config file from enchant-2 to enchant.

Could you please drop that change and switch the build-dependency?

Kind regards,
Laurent Bigonville

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

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

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

Debian distribution maintenance software
pp.
Jan Niehusmann  (supplier of updated psi 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: Wed, 01 Jul 2020 23:01:13 +0200
Source: psi
Binary: psi
Architecture: source amd64
Version: 1.3-6
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann 
Changed-By: Jan Niehusmann 
Description:
 psi- Jabber client using Qt
Closes: 956691
Changes:
 psi (1.3-6) unstable; urgency=medium
 .
   * Update watch file to point to the project's github page
   * Use libhunspell instead of libenchant (Closes: Bug#956691)
Checksums-Sha1:
 7d8d3317bc9e3657ffaf0b71ba0b20d4205b2fd3 1654 psi_1.3-6.dsc
 1298a6c9084e8c329ca1a744b1921fe36e95b35c 11232 psi_1.3-6.debian.tar.xz
 7528b4491b6033d8f13ae41685c73328b0e3f147 11260 psi_1.3-6_amd64.buildinfo
 f5979604ba04c522b2dbdc3e8dfc4e95011a4a04 3093864 psi_1.3-6_amd64.deb
Checksums-Sha256:
 4b2470d02a042f43935f9ff0295ed3691d4badeee1cbacabcf89774981f2d9a6 1654 
psi_1.3-6.dsc
 e52372b61a6d007ef780ec0e28acf59866ec5113cb547e1bbca6b3408760431e 11232 
psi_1.3-6.debian.tar.xz
 86001364e00719e14025e4ab7c6790b7be4291dc210abee3d8f886a0aca15ae0 11260 
psi_1.3-6_amd64.buildinfo
 b4085486ce63ab19d840b33b815376bbcb81dec76ed5b250a6a4d703ef1b1f02 3093864 
psi_1.3-6_amd64.deb
Files:
 941fa331da129b2c36006b193feb3cbd 1654 net optional psi_1.3-6.dsc
 7fd0df9b74a3cb431e099e4de405c40d 11232 net optional psi_1.3-6.debian.tar.xz
 658d474cf54b19bf36a351a61d50e621 11260 net optional psi_1.3-6_amd64.buildinfo
 3e5d9bbbfd99542f71c6c3d00260cc6e 3093864 net optional psi_1.3-6_amd64.deb

-BEGIN PGP SIGNATURE-

iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAl79AGoPHGphbkBkZWJp
YW4ub3JnAAoJEMJAzpldAmsRNeUL/jO9BdKxPZmSYYCejjdP5bOkjUsl/B3GXm7E
yWedd9NuuMSVcHSpbT6N+J0r/Mjj77+y+HdpVnJ6RO+EVjR8bF/FXURfvi1YIj+l
HIuc2KkKWtMYH6qftRgidl8r9sINx9NDpG443dAFzOTXMcBLRlvGyQDP8aGylp9/
2kFwgEPGUs/d7Sakun/GSWc0X6hdD+430Sed194yFPbA8kt0j+ahwdD5OrdNus/n
efgO837xXiXRxC5KaBaE6Pkiwk2/0DDlnYWMZVCBXICnc9Z7AqmZSj5GPeYffwbQ
IS+Dz0t0Z0EsmCqPo6kDRBZPph5bmx20rFF7JL2YB/A6cquB01xYB2sLUg8kUB41
Ls+R/lmQiYajWydBDpR5EidGKio4gcC2+eUSwsG/dUli4Fol1kOK0CPpoH62u7V0
5K3CBWH42mryrs9QaW+dWvKNKEQdSi5h7VcO7DFRKrSfKJxdjRWwP84FxL7XKR/r
7fIePxvvz8l6xHZzeOe+tRe9CeUxow==
=8ynY
-END PGP SIGNATURE End Message ---

Bug#964110: eccodes FTBFS on 32bit

[Adrian Bunk]

Source: eccodes
Version: 2.18.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=eccodes=sid

...
/<>/fortran/grib_type_interfaces.f90:55:26:

   55 |subroutine check_int_i4(a,b,n) bind(C, name='check_int_')
  |  1
..
   61 |subroutine check_int_i8(a,b,n) bind(C, name='check_int_')
  |  2
Error: Ambiguous interfaces in generic interface 'check_int' for ‘check_int_i4’ 
at (1) and ‘check_int_i8’ at (2)
/<>/fortran/grib_type_interfaces.f90:76:29:

   76 |subroutine check_size_t_i4(a,b,n) bind(C, name='check_size_t_')
  | 1
..
   82 |subroutine check_size_t_i8(a,b,n) bind(C, name='check_size_t_')
  | 2
Error: Ambiguous interfaces in generic interface 'check_size_t' for 
‘check_size_t_i4’ at (1) and ‘check_size_t_i8’ at (2)
/<>/fortran/grib_type_interfaces.f90:22:25:

   22 |subroutine f_sizeof_i4(a,b,n) bind(C, name='f_sizeof_')
  | 1
..
   28 |subroutine f_sizeof_i8(a,b,n) bind(C, name='f_sizeof_')
  | 2
Error: Ambiguous interfaces in generic interface 'f_sizeof' for ‘f_sizeof_i4’ 
at (1) and ‘f_sizeof_i8’ at (2)
make[3]: *** [fortran/CMakeFiles/grib_types.dir/build.make:66: 
fortran/CMakeFiles/grib_types.dir/grib_type_interfaces.f90.o] Error 1


debian/patches/gfortran-10.patch assumes long is 8 byte,
which is not true on 32bit architectures.

Bug#964109: flint: FTBFS on 32 bit archs

[Sebastian Ramacher]

Source: flint
Version: 2.6.0~rc3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

flint fails to build on 32 bit architectures. For example:
| mul_johnsonPASS
| push_term_fq_nmod_fmpzPASS
| push_term_fq_nmod_uiPASS
| push_term_fq_nmod_uiPASS
| reversePASS
| scalar_mul_uiPASS
| sort_termsPASS
| total_degreePASS
| univarPASS
| PASS
| E: Build killed with signal TERM after 150 minutes of inactivity

https://buildd.debian.org/status/fetch.php?pkg=flint=i386=2.6.0-2=1592647407=0

| refinePASS
| make[3]: *** [../Makefile.subdirs:97: 
../build/fmpz_factor/test/t-pollard_brent_single_RUN] Aborted
| make[3]: *** Waiting for unfinished jobs
| PASS
| PASS
| make[3]: Leaving directory '/<>/fmpz_factor'
| make[2]: *** [Makefile:217: check] Error 2

https://buildd.debian.org/status/fetch.php?pkg=flint=armel=2.6.0-2=1592639203=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#964108: pyscanfcs FTBFS

[Adrian Bunk]

Source: pyscanfcs
Version: 0.3.6+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=pyscanfcs=sid

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
cp --reflink=auto -a ./debian/pyscanfcs.desktop 
debian/pyscanfcs/usr/share/applications//
install -d debian/pyscanfcs/usr/share/doc/pyscanfcs/examples
cp --reflink=auto -a ./misc/ 
debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/
install -d debian/.debhelper/generated/pyscanfcs
mv /<>/debian/pyscanfcs/usr/bin/pyscanfcs \
   /<>/debian/pyscanfcs/usr/lib/pyscanfcs/pyscanfcs_run
cd /<>/debian/pyscanfcs/usr/bin/; \
ln -s ../lib/pyscanfcs/pyscanfcs_run pyscanfcs; cd -
/<>
mv debian/pyscanfcs.xpm \
debian/pyscanfcs/usr/share/pixmaps
chmod -R 644 debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/setup.py': Permission 
denied
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/dat2csv.py': Permission 
denied
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/binningc.pyx': 
Permission denied
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/README.md': Permission 
denied
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/MakeTestDat_SFCS.py': 
Permission denied
chmod: cannot access 
'debian/pyscanfcs/usr/share/doc/pyscanfcs/examples/misc/ExampleFunc_Exp_correlated_noise.txt':
 Permission denied
make[1]: *** [debian/rules:53: override_dh_install] Error 1

Bug#963387: marked as done (libmojolicious-perl: Invalid selectors (breaks RT))

[Debian Bug Tracking System]

Your message dated Wed, 1 Jul 2020 22:12:00 +0100
with message-id <20200701211200.kfgsohpbxndld...@urchin.earth.li>
and subject line done
has caused the Debian Bug report #963387,
regarding libmojolicious-perl: Invalid selectors (breaks RT)
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/perl ./sbin/rt-test-dependencies --with-SQLite --with-fastcgi
> perl:
>   >=5.10.1(5.30.3) ...found
> users:
>   rt group (user42) ...found
>   bin owner (user42) ...found
>   libs owner (user42) ...found
>   libs group (user42) ...found
>   web owner (user42) ...found
>   web group (user42) ...found
> CLI dependencies:
>   Getopt::Long >= 2.24 ...found
>   Term::ReadLine ...found
>   LWP >= 6.02 ...found
>   HTTP::Request::Common ...found
>   Term::ReadKey ...found
>   Text::ParseWords ...found
> CORE dependencies:
>   Storable >= 2.08 ...found
>   Text::Password::Pronounceable ...found
>   HTML::FormatText::WithLinks >= 0.14 ...found
>   CSS::Minifier::XS ...found
>   Email::Address::List >= 0.06 ...found
>   Locale::Maketext::Lexicon >= 0.32 ...found
>   Convert::Color ...found
>   CGI::Emulate::PSGI ...found
>   DateTime::Format::Natural >= 0.67 ...found
>   Time::ParseDate ...found
>   File::Temp >= 0.19 ...found
>   IPC::Run3 ...found
>   Sys::Syslog >= 0.16 ...found
>   Regexp::Common::net::CIDR ...found
>   HTML::Mason::PSGIHandler >= 0.52 ...found
>   Text::Wrapper ...found
>   DateTime::Locale >= 0.40 ...found
>   Scope::Upper ...found
>   Encode >= 2.64 ...found
>   HTML::FormatText::WithLinks::AndTables >= 0.06 ...found
>   Role::Basic >= 0.12 ...found
>   MIME::Types ...found
>   Business::Hours ...found
>   Digest::base ...found
>   Data::ICal ...found
>   List::MoreUtils ...found
>   HTML::RewriteAttributes >= 0.05 ...found
>   Symbol::Global::Name >= 0.05 ...found
>   URI::QueryParam ...found
>   Date::Extract >= 0.02 ...found
>   HTML::Scrubber >= 0.08 ...found
>   URI >= 1.59 ...found
>   Email::Address >= 1.912 ...found
>   HTML::Entities ...found
>   Module::Refresh >= 0.03 ...found
>   File::Glob ...found
>   HTML::Quoted ...found
>   DBIx::SearchBuilder >= 1.65 ...found
>   CGI::PSGI >= 0.12 ...found
>   Tree::Simple >= 1.04 ...found
>   Devel::StackTrace >= 1.19 ...found
>   Apache::Session >= 1.53 ...found
>   Regexp::Common ...found
>   Locale::Maketext >= 1.06 ...found
>   Plack::Handler::Starlet ...MISSING
>   Crypt::Eksblowfish ...found
>   Locale::Maketext::Fuzzy >= 0.11 ...found
>   DBI >= 1.37 ...found
>   JSON ...found
>   HTTP::Message >= 6.0 ...found
>   JavaScript::Minifier::XS ...found
>   HTML::Mason >= 1.43 ...found
>   Time::HiRes ...found
>   Log::Dispatch >= 2.30 ...found
>   Text::WikiFormat >= 0.76 ...found
>   CGI >= 4 ...found
>   MIME::Entity >= 5.504 ...found
>   Mail::Mailer >= 1.57 ...found
>   File::Spec >= 0.8 ...found
>   Text::Template >= 1.44 ...found
>   Date::Manip ...found
>   DateTime >= 0.44 ...found
>   Module::Versions::Report >= 1.05 ...found
>   Clone ...found
>   Regexp::IPv6 ...found
>   Devel::GlobalDestruction ...found
>   File::ShareDir ...found
>   Net::CIDR ...found
>   Data::Page::Pageset ...found
>   CSS::Squish >= 0.06 ...found
>   UNIVERSAL::require ...found
>   Plack >= 1.0002 ...found
>   Scalar::Util ...found
>   CGI::Cookie >= 1.20 ...found
>   Digest::MD5 >= 2.27 ...found
>   Mail::Header >= 2.12 ...found
>   Net::IP ...found
>   LWP::Simple ...found
>   Digest::SHA ...found
>   XML::RSS >= 1.05 ...found
>   Pod::Select ...found
>   Errno ...found
>   Text::Quoted >= 2.07 ...found
>   Data::GUID ...found
>   Class::Accessor::Fast ...found
> DEVELOPER dependencies:
>   File::Which ...found
>   String::ShellQuote ...found
>   Test::MockTime ...found
>   File::Find ...found
>   Locale::PO ...found
>

Processed: Re: [request-tracker-maintainers] Bug#963387: Bug#963387: Bug#963387: request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libmojolicious-perl
Bug #963387 [src:request-tracker4] request-tracker4: FTBFS with newer 
libmojolicious-perl: t/web/ticket_owner.t
Bug reassigned from package 'src:request-tracker4' to 'libmojolicious-perl'.
No longer marked as found in versions request-tracker4/4.4.4-1.
Ignoring request to alter fixed versions of bug #963387 to the same values 
previously set
> retitle -1 libmojolicious-perl: Invalid selectors (breaks RT)
Bug #963387 [libmojolicious-perl] request-tracker4: FTBFS with newer 
libmojolicious-perl: t/web/ticket_owner.t
Changed Bug title to 'libmojolicious-perl: Invalid selectors (breaks RT)' from 
'request-tracker4: FTBFS with newer libmojolicious-perl: t/web/ticket_owner.t'.
> found -1 8.54+dfsg-1
Bug #963387 [libmojolicious-perl] libmojolicious-perl: Invalid selectors 
(breaks RT)
Marked as found in versions libmojolicious-perl/8.54+dfsg-1.
> fixed -1 8.55+dfsg-1
Bug #963387 [libmojolicious-perl] libmojolicious-perl: Invalid selectors 
(breaks RT)
There is no source info for the package 'libmojolicious-perl' at version 
'8.55+dfsg-1' with architecture ''
Unable to make a source version for version '8.55+dfsg-1'
Marked as fixed in versions 8.55+dfsg-1.
> affects -1 request-tracker4
Bug #963387 [libmojolicious-perl] libmojolicious-perl: Invalid selectors 
(breaks RT)
Added indication that 963387 affects request-tracker4

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

Bug#963387: [request-tracker-maintainers] Bug#963387: Bug#963387: Bug#963387: request-tracker4: FTBFS: CORE missing dependencies: Plack::Handler::Starlet ...MISSING

[Dominic Hargreaves]

Control: reassign -1 libmojolicious-perl
Control: retitle -1 libmojolicious-perl: Invalid selectors (breaks RT)
Control: found -1 8.54+dfsg-1
Control: fixed -1 8.55+dfsg-1
Control: affects -1 request-tracker4

On Tue, Jun 23, 2020 at 12:19:03AM +0100, Dominic Hargreaves wrote:
> > Almost certainly triggered by the recent uploads of libmojolicious-perl.
> > It happens with both 8.55+dfsg-1 (sid) and 8.54+dfsg-1 (bullseye).
> 
> Confirmed it doesn't happen with 8.53. Forwarded upstream.

I got this wrong, 8.55 is fine - it's only 8.54 that's broken. See
changelog entry:

8.55  2020-06-18
  - Fixed a regression in Mojo::DOM::CSS that caused some selectors to not be 
valid anymore.

Processed: reassign 961798 to src:python-pyaudio, merging 961798 963321, tagging 961798

[Debian Bug Tracking System]

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

> reassign 961798 src:python-pyaudio
Bug #961798 [python-pyaudio] python-pyaudio: FTBFS for doc package
Bug reassigned from package 'python-pyaudio' to 'src:python-pyaudio'.
No longer marked as found in versions 0.2.11-1.1.
Ignoring request to alter fixed versions of bug #961798 to the same values 
previously set
> merge 961798 963321
Bug #961798 [src:python-pyaudio] python-pyaudio: FTBFS for doc package
Bug #961798 [src:python-pyaudio] python-pyaudio: FTBFS for doc package
Marked as found in versions python-pyaudio/0.2.11-1.1.
Added tag(s) bullseye, ftbfs, and sid.
Bug #963321 [src:python-pyaudio] python-pyaudio: FTBFS: dh_linktree: error: 
link destination 
debian/python-pyaudio-doc/usr/share/doc/python-pyaudio-doc/docs/_static is a 
directory
Merged 961798 963321
> tags 961798 + patch
Bug #961798 [src:python-pyaudio] python-pyaudio: FTBFS for doc package
Bug #963321 [src:python-pyaudio] python-pyaudio: FTBFS: dh_linktree: error: 
link destination 
debian/python-pyaudio-doc/usr/share/doc/python-pyaudio-doc/docs/_static is a 
directory
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#951537: Resolved in 2.1.5-1 for unstable

[Mike Gabriel]

Control: close -1
Control: fixed -1 2.1.5-1

This issue has now been also resolved in Debian unstable via upload of  
php-horde-2.1.5-1. Unfortunately, closing this bug via d/changelog has  
been left out.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpnOCE1eEtdm.pgp
Description: Digitale PGP-Signatur

Processed: severity of 960769 is important

[Debian Bug Tracking System]

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

> severity 960769 important
Bug #960769 [src:swt4-gtk] swt4-gtk FTBFS on 32bit
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: src:pbcopper: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.6.0+dfsg-4
Bug #964104 [src:pbcopper] src:pbcopper: fails to migrate to testing for too 
long
Marked as fixed in versions pbcopper/1.6.0+dfsg-4.
Bug #964104 [src:pbcopper] src:pbcopper: fails to migrate to testing for too 
long
Marked Bug as done

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

Bug#964104: src:pbcopper: fails to migrate to testing for too long

[Paul Gevers]

Source: pbcopper
Version: 1.3.0+dfsg-3
Severity: serious
Control: close -1 1.6.0+dfsg-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#960237: marked as done (FTBFS: No such file or directory: /usr/share/zoneinfo/)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 19:33:31 +
with message-id 
and subject line Bug#960237: fixed in clickhouse 18.16.1+ds-7.1
has caused the Debian Bug report #960237,
regarding FTBFS: No such file or directory: /usr/share/zoneinfo/
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.)


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

Hi,

During a test recompilation with the new ICU release I've realized
your package FTBFS in Sid with its self-tests. Relevant output logs:
  Start 11: with_server
11/11 Test #11: with_server ***Failed   10.32 sec
[...]
Poco::Exception. Code: 1000, e.code() = 0, e.displayText() =
Exception: Could not determine time zone from TZ variable value:
`Europe/Moscow': boost::filesystem::canonical: No such file or
directory: "/usr/share/zoneinfo/", e.what() = Exception

You need to add tzdata to your build dependencies, that will fix it.

Regards,
Laszlo/GCS
--- End Message ---
--- Begin Message ---
Source: clickhouse
Source-Version: 18.16.1+ds-7.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated clickhouse 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: Thu, 18 Jun 2020 18:24:20 +0300
Source: clickhouse
Architecture: source
Version: 18.16.1+ds-7.1
Distribution: unstable
Urgency: low
Maintainer: Alexander GQ Gerasiov 
Changed-By: Adrian Bunk 
Closes: 960237
Changes:
 clickhouse (18.16.1+ds-7.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Build depend on tzdata. (Closes: #960237)
Checksums-Sha1:
 9db52c3470fd48d05b5799924b738eb8ee1cb04b 3205 clickhouse_18.16.1+ds-7.1.dsc
 663007d17be9680de52aed83d5bd9d77b162c229 24008 
clickhouse_18.16.1+ds-7.1.debian.tar.xz
Checksums-Sha256:
 c9de767d457ef8ae73d05ae2d708f3880d163fb2fbd59f9d5543d02c3ec124fc 3205 
clickhouse_18.16.1+ds-7.1.dsc
 ec1e573fad80799680367ffea48a9158a249a49e15f270bfc2c386df7115e5fc 24008 
clickhouse_18.16.1+ds-7.1.debian.tar.xz
Files:
 f7733d1a091f5812ebce9316a5c03683 3205 database optional 
clickhouse_18.16.1+ds-7.1.dsc
 05bacbb2dd8cf3882110c7658bc8bc51 24008 database optional 
clickhouse_18.16.1+ds-7.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7rjycACgkQiNJCh6LY
mLEP8w//SJtlxbiqJWYn4xwyis4tV/u/lT2hd60d5Z8x6TokYr9OXTPbEyOjstt9
Z+h3GlrX4w6Vo6se4MbH/a7hd4HPtoS4LhPgkQTfwNWbd20hsRaAR+x6rSUl4fs3
8Wt//B8FNo0xFi5vXuU24JM45LdpCk4v0E0iRKWLfKdY5jMIBHS6DyJ2nlU50yuK
w0ECFLSAIFwje79xeWcVynY0lFILS+2DY0RVoTQU7NqK9CKatgRsL4xnpdtFWACy
5qHN03VlxkmQpky3GNNfDLIEpgzfbBu6g6xaLjD66MaCS/dbQlyG+qUNr2p9PzU5
VF+6FKQpaoT+g7Tc5cwPCj0xNJaa238IDjKBpw3tHkMtIbxuCeludI4BMDYvw1xN
mqYjvBEahlyqPui0tlVQuv/b+8iIxmt3jQ4wbDhe6u8EzqIUa/Ef8pMc7/8AWeWo
6TJqLzpwvdIEue2afTpbMalIRXVt+dL4bSTvxBUCfL5UYhaNtDIEqd3aBalku+aw
ctObZ+Z78DHq3soAjsSzFHATeE0+H9eA2Zenn35YevH0jCT0MwDcU5MMA2uEB21r
VJ6UNcLBwenVBlHgf07kn7wQ1xWwMPSo9xSNI/4zcqZIkKas2fpEa8i9Qrwq3Hvx
fg/qELvWNxXmON2N7cnEeN23JzJKikqo1HHi+JQA45TRpfU++Pk=
=Cd75
-END PGP SIGNATURE End Message ---

Bug#958578: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 19:19:46 +
with message-id 
and subject line Bug#956927: fixed in wav2cdr 2.3.4-4
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
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.)


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

Dear maintainer(s),

With a recent upload of wav2cdr you added an autopkgtest, great. However
it fails on arm64. I copied some of the output at the bottom of this report.

Currently this failure 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=wav2cdr

https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz

autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav
$AUTOPKGTEST_TMP/silence.mp3
autopkgtest [19:42:21]: test command3: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
bash: line 1:   837 Aborted bash -ec 'wav2cdr
debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout)
autopkgtest [19:42:21]: test command3: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wav2cdr
Source-Version: 2.3.4-4
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated wav2cdr 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: Wed, 01 Jul 2020 21:44:51 +0300
Source: wav2cdr
Architecture: source
Version: 2.3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 749005 956927
Changes:
 wav2cdr (2.3.4-4) unstable; urgency=medium
 .
   * QA upload.
   * Use C99 fixed-size integer types to fix runtime assertion on
 64bit architectures other than amd64 and alpha. (Closes: #956927)
   * data.c: Remove incorrect const. (Closes: #749005)
   * Stop linking to the dead Homepage.
Checksums-Sha1:
 d76120429ed236d4f1c9b34c8e453dccfbbc0736 1819 wav2cdr_2.3.4-4.dsc
 038c4c842874f47077ff4f169978c5489224c2d9 35700 wav2cdr_2.3.4-4.debian.tar.xz
Checksums-Sha256:
 1e953b0439f3e831a456ccaf37378d00457e70bc3be32ed8a1268f26351105d4 1819 
wav2cdr_2.3.4-4.dsc
 b74cc7703d4823ed70ab511ce187973c43ec864e94a7e6e1afdda4b26087dbd8 35700 
wav2cdr_2.3.4-4.debian.tar.xz
Files:
 0604143655196c17b9d9fb60bbcb35f4 1819 sound optional wav2cdr_2.3.4-4.dsc
 a33db8bc47a2b71611000c5ece51cd66 35700 sound optional 
wav2cdr_2.3.4-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl783Y0ACgkQiNJCh6LY
mLFiRRAAmQgW8EVscQ5drKIIzRmtjzVo0R4BFdE6asrvtuWDRQEjUjN55JkxjR6X
/IHtgATFkyISmhhrUTRunHrWXcG40UH+D4r4cXzakW5JAn5+t3+Krkuw5WvmK3SI
u8cU3scNvB2Rem2GhbyRP+3KvCgb3PwgVrqFti7GZTWKnTcAQhLhms7zrWVjryZ4
Ipillz1HZTLfDPk8Nv+BPH0S2g/oN9F5aZe5R21Rd+X04QG10dX5PQcTTh1/kyM+
5tD3Gk76mxOK/bcW7owhMka/NuYsi5tAZMj5hf1PgPeVcLC/Pk1tOgz6M6JYRDPu
nxm+dCTvD56c2tCidnHBU7pAA8YLCM5PzciLmvyKQMKdJwjAwC/geWXyj3gtUdNs
EfWGQ9DaMhbg5UoMeyp2GefJlrcY3zSwxuhmuOD0KEkCsZxj/0Z8c/4LHScT8z2F
xvJbRCR8sVUmlO/pAvzzKhNCpHllXm6ByYCqhV5wlwsdoFXjR5Lq4/z4uEroEIil
kmcN4I19H5FcJ+gytYcHH1wudu3XNMCDkXQOit2fBxrCksucU9pKgfI9T4s+78tL
+4Vbt4q0ZEnOZ+bInXgjxkKW8i3EcvcSgcxwtvrL8FykJZiMuAr6OroZs3Id4e9Z
aTUoCj9QN7wklPzpvBRAlFdA/V3/8HD6jKov6InTgrtKKVUXXd4=
=PV/O
-END PGP SIGNATURE End Message ---

Bug#963782: marked as done (gpgme1.0: autopkgtest failure due to bash wrong syntax)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 19:19:10 +
with message-id 
and subject line Bug#963782: fixed in gpgme1.0 1.13.1-9
has caused the Debian Bug report #963782,
regarding gpgme1.0: autopkgtest failure due to bash wrong syntax
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.)


-- 
963782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.13.1-8
Severity: serious
Tags: patch

Hello, please accept this patch to fix a bad syntax.
(two main issues, missing


Processing triggers for libc-bin (2.31-0ubuntu10) ...
(Reading database ... 78068 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [15:17:55]: test checky2106: [---
unsigned long on this platform is 4 octets.
This means that GPGME will fail when encountering expiration
dates after 2106-02-07 06:28:16Z.

Please see https://dev.gnupg.org/T4766 and https://dev.gnupg.org/T4826
for more details.
/tmp/autopkgtest.FpdOQK/build.XhH/src/debian/tests/checky2106: line 25: [: 
missing `]'
autopkgtest [15:17:57]: test checky2106: ---]
autopkgtest [15:18:00]: test checky2106:  - - - - - - - - - - results - - - - - 
- - - - -
checky2106   FAIL non-zero exit status 1
autopkgtest [15:18:00]: test checky2106:  - - - - - - - - - - stderr - - - - - 
- - - - -
/tmp/autopkgtest.FpdOQK/build.XhH/src/debian/tests/checky2106: line 25: [: 
missing `]'
autopkgtest [15:18:02]:  summary
python3  PASS
checky2106   FAIL non-zero exit status 1



diff -Nru gpgme1.0-1.13.1/debian/changelog gpgme1.0-1.13.1/debian/changelog
--- gpgme1.0-1.13.1/debian/changelog2020-06-26 10:16:00.0 +0200
+++ gpgme1.0-1.13.1/debian/changelog2020-06-26 23:44:40.0 +0200
@@ -1,3 +1,9 @@
+gpgme1.0 (1.13.1-8ubuntu2) groovy; urgency=medium
+
+  * Fix test sadness on 32bit systems due to bad bash syntax.
+
+ -- Gianfranco Costamagna   Fri, 26 Jun 2020 
23:44:40 +0200
+
 gpgme1.0 (1.13.1-8ubuntu1) groovy; urgency=low
 
   * Merge from Debian unstable.  Remaining changes:
diff -Nru gpgme1.0-1.13.1/debian/tests/checky2106 
gpgme1.0-1.13.1/debian/tests/checky2106
--- gpgme1.0-1.13.1/debian/tests/checky2106 2020-06-26 10:15:43.0 
+0200
+++ gpgme1.0-1.13.1/debian/tests/checky2106 2020-06-26 23:44:17.0 
+0200
@@ -22,8 +22,8 @@
 Please see https://dev.gnupg.org/T4766 and https://dev.gnupg.org/T4826
 for more details.
 " "$sz" "$limit"
-if [ "$(dpkg-architecture -qDEB_HOST_ARCH_BITS)" == 32 &&
- $(date +%s) -lt $(TZ=UTC date +%s 2031-02-07) ]; then
+if [ "$(dpkg-architecture -qDEB_HOST_ARCH_BITS)" == 32 ] &&
+[ $(date +%s) -lt $(TZ=UTC date +%s --date='2031-02-07') ]; then
 printf "We permit skipping this test during autopkgtest until 75 years
 before the cutoff.
 

thanks!

Gianfranco
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.13.1-9
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gpgme1.0 
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: Wed, 01 Jul 2020 14:50:20 -0400
Source: gpgme1.0
Architecture: source
Version: 1.13.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Closes: 963782
Changes:
 gpgme1.0 (1.13.1-9) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * fix test sadness on 32bit systems due to bad bash syntax (Closes: #963782)
Checksums-Sha1:
 155c4023ffd7871bf19e90b9b5ff428742a1f339 2282 gpgme1.0_1.13.1-9.dsc
 7cadf961fc871be3872a08cd4c5e4351df045f17 20720 gpgme1.0_1.13.1-9.debian.tar.xz
 5995a98ef337e0fe576e40f51fcd17d5e555bedc 13967 
gpgme1.0_1.13.1-9_source.buildinfo
Checksums-Sha256:
 b043c8caeacc82d1ff8749334c01cc57c583fa81a53ed847a9821b5f2b08c2b3 2282 
gpgme1.0_1.13.1-9.dsc
 

Bug#956927: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 19:19:46 +
with message-id 
and subject line Bug#956927: fixed in wav2cdr 2.3.4-4
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
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.)


-- 
956927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wav2cdr
Version: 2.3.4-3
Severity: important

The new and first CI test[1] for wav2cdr fails in arm64[2]. Consequently,
the revision 2.3.4-3 will not migrate to testing.

[1] 
https://salsa.debian.org/debian/wav2cdr/-/blob/debian/master/debian/tests/control
[2] 
https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz

The significative output is:

autopkgtest [19:42:07]: test command1: wav2cdr -V | grep Version
autopkgtest [19:42:07]: test command1: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:07]: test command1: ---]
autopkgtest [19:42:07]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
autopkgtest [19:42:07]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
[...]
autopkgtest [19:42:16]: test command2: wav2cdr --help | grep describes
autopkgtest [19:42:16]: test command2: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:16]: test command2: ---]
autopkgtest [19:42:16]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 1
autopkgtest [19:42:17]: test command2:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
[...]
autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav 
$AUTOPKGTEST_TMP/silence.mp3
autopkgtest [19:42:21]: test command3: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
bash: line 1:   837 Aborted bash -ec 'wav2cdr 
debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a 
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout)
autopkgtest [19:42:21]: test command3: ---]
autopkgtest [19:42:21]: test command3:  - - - - - - - - - - results - - - - - - 
- - - -
command3 FAIL non-zero exit status 134
autopkgtest [19:42:22]: test command3:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:22]:  summary
command1 FAIL non-zero exit status 1
command2 FAIL non-zero exit status 1
command3 FAIL non-zero exit status 134


Eriberto
--- End Message ---
--- Begin Message ---
Source: wav2cdr
Source-Version: 2.3.4-4
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated wav2cdr 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: Wed, 01 Jul 2020 21:44:51 +0300
Source: wav2cdr
Architecture: source
Version: 2.3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 749005 956927
Changes:
 wav2cdr (2.3.4-4) unstable; urgency=medium
 .
   * QA upload.
   * Use C99 fixed-size integer types to fix runtime assertion on
 64bit architectures other than amd64 and alpha. (Closes: #956927)
   * data.c: Remove incorrect const. (Closes: #749005)
   * Stop linking to the dead Homepage.
Checksums-Sha1:
 d76120429ed236d4f1c9b34c8e453dccfbbc0736 1819 wav2cdr_2.3.4-4.dsc
 038c4c842874f47077ff4f169978c5489224c2d9 35700 wav2cdr_2.3.4-4.debian.tar.xz
Checksums-Sha256:
 

Bug#908694: album-data: please remove dependency on libjs-swfobject, which is going away

[David Ljung Madison]

I am the author of album / album-data


Is this being maintained anymore?  If not, how can I take over the
maintenance of this package and/or find a Debian Maintainer who can?

Because this dependency has not been removed, the package has
now been dropped.

Dave

---
Dave Madison Stellarhttp://GetDave.com/415.341.
---

Bug#964101: tiddit: generates extremely large file during autopkgtesting

[Paul Gevers]

Source: tiddit
Version: 2.12.0+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: -1 issue

Dear maintainer(s),

In the last upload of the tiddit package, an autopkgtest was added,
great. However, the package seems to generate files, and one file is
growing to at least 29 GB. Maybe bigger, but with that size, the VM as
runs on several of our arm64 workers is full (total size is 40 GB).

root@ci-182-f37c0a21:/tmp/autopkgtest-lxc.mk9f7rok/downtmp/autopkgtest_tmp#
ls -alh
total 29G
drwxr-xr-x 2 debci debci 4.0K Jun 30 22:29 .
drwxrwxrwx 5 root  root  4.0K Jun 30 22:29 ..
-rw-r--r-- 1 debci debci 1.4M Jun 30 22:19 normal.bam
-rw-r--r-- 1 debci debci 5.8M Jun 28 10:11 normal.sam
-rw-r--r-- 1 debci debci  11M Jun 28 10:10 ref.fa
-rw-r--r-- 1 debci debci0 Jun 30 22:29 test1.db
-rw-r--r-- 1 debci debci0 Jun 30 22:29 test1.gc.wig
-rw-r--r-- 1 debci debci  29G Jun 30 22:22 test1.sample.bam
-rw-r--r-- 1 debci debci0 Jun 30 22:29 test1.signals.tab
-rw-r--r-- 1 debci debci0 Jun 30 22:29 test1.wig
-rw-r--r-- 1 debci debci 1.1M Jun 30 22:19 tumor.bam
-rw-r--r-- 1 debci debci 4.5M Jun 28 10:12 tumor.sam

Please be a bit more gentle with your tests for our infrastructure. I'll
have the ci infrastructure ignore tests on arm64 for now until you close
this bug.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: affects 956927

[Debian Bug Tracking System]

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

> affects 956927 wav2cdr
Bug #956927 [src:wav2cdr] wav2cdr is broken on 64bit architectures other than 
amd64 and alpha
Bug #958578 [src:wav2cdr] wav2cdr is broken on 64bit architectures other than 
amd64 and alpha
Added indication that 956927 affects wav2cdr
Added indication that 958578 affects wav2cdr
> thanks
Stopping processing here.

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

Processed: found 956927 in 2.3.4-1

[Debian Bug Tracking System]

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

> found 956927 2.3.4-1
Bug #956927 [src:wav2cdr] wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: 
Assertion `sizeof(UINT32) == 4' failed.
Bug #958578 [src:wav2cdr] wav2cdr: autopkgtest failure on arm64: Assertion 
`sizeof(UINT32) == 4' failed
Marked as found in versions wav2cdr/2.3.4-1.
Marked as found in versions wav2cdr/2.3.4-1.
> thanks
Stopping processing here.

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

Processed: retitle 956927 to wav2cdr is broken on 64bit architectures other than amd64 and alpha

[Debian Bug Tracking System]

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

> retitle 956927 wav2cdr is broken on 64bit architectures other than amd64 and 
> alpha
Bug #956927 [src:wav2cdr] wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: 
Assertion `sizeof(UINT32) == 4' failed.
Bug #958578 [src:wav2cdr] wav2cdr: autopkgtest failure on arm64: Assertion 
`sizeof(UINT32) == 4' failed
Changed Bug title to 'wav2cdr is broken on 64bit architectures other than amd64 
and alpha' from 'wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: 
Assertion `sizeof(UINT32) == 4' failed.'.
Changed Bug title to 'wav2cdr is broken on 64bit architectures other than amd64 
and alpha' from 'wav2cdr: autopkgtest failure on arm64: Assertion 
`sizeof(UINT32) == 4' failed'.
> thanks
Stopping processing here.

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

Processed: Merge and sort

[Debian Bug Tracking System]

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

> reassign 956927 src:wav2cdr
Bug #956927 [wav2cdr] wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: 
Assertion `sizeof(UINT32) == 4' failed.
Bug reassigned from package 'wav2cdr' to 'src:wav2cdr'.
No longer marked as found in versions wav2cdr/2.3.4-3.
Ignoring request to alter fixed versions of bug #956927 to the same values 
previously set
> forcemerge 958578 956927
Bug #958578 [src:wav2cdr] wav2cdr: autopkgtest failure on arm64: Assertion 
`sizeof(UINT32) == 4' failed
Bug #956927 [src:wav2cdr] wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: 
Assertion `sizeof(UINT32) == 4' failed.
Severity set to 'serious' from 'important'
962062 was blocked by: 958578
962062 was not blocking any bugs.
Added blocking bug(s) of 962062: 956927
Marked as found in versions wav2cdr/2.3.4-3.
Merged 956927 958578
> block 962062 by 956927
Bug #962062 {Done: Paul Gevers } [src:wav2cdr] src:wav2cdr: 
fails to migrate to testing for too long: autopkgtest regression on arm64
962062 was blocked by: 956927 958578
962062 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #962062 to the same blocks 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 963421

[Debian Bug Tracking System]

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

> tags 963421 + pending
Bug #963421 [src:calligra] calligra: FTBFS: dh_install: error: missing files, 
aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Resolved in 2.1.5-1 for unstable

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #951537 {Done: robe...@debian.org (Roberto C. Sanchez)} 
[src:php-horde-data] php-horde-data: CVE-2020-8518
Bug 951537 is already marked as done; not doing anything.
> fixed -1 2.1.5-1
Bug #951537 {Done: robe...@debian.org (Roberto C. Sanchez)} 
[src:php-horde-data] php-horde-data: CVE-2020-8518
Marked as fixed in versions php-horde-data/2.1.5-1.

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

Bug#963431: marked as done (specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 15:49:09 +
with message-id 
and subject line Bug#963431: fixed in specutils 1.0-2
has caused the Debian Bug report #963431,
regarding specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.8 returned exit code 13
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> Downloading 'astropy-helpers'; run setup.py with the --offline option to 
> force offline installation.
> Freezing version number to ./specutils/version.py
> running config
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161: 
> AstropyDeprecationWarning: The package argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the package name in 
> setup.cfg instead
>   warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166: 
> AstropyDeprecationWarning: The version argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the version number in 
> setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:171: 
> AstropyDeprecationWarning: The release argument to generate_version_py has 
> been deprecated and will be removed in future. We now use the presence of the 
> "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:186: 
> AstropyDeprecationWarning: Specifying the package name using the 
> "package_name" option in setup.cfg is deprecated - use the "name" option 
> instead.
>   warnings.warn('Specifying the package name using the "package_name" '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:239: 
> AstropyDeprecationWarning: The packagename argument to generate_version_py 
> has been deprecated and will be removed in future. Specify the package name 
> in setup.cfg instead
>   warnings.warn('The packagename argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:244: 
> AstropyDeprecationWarning: The version argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the version number in 
> setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:249: 
> AstropyDeprecationWarning: The release argument to generate_version_py has 
> been deprecated and will be removed in future. We now use the presence of the 
> "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:264: 
> AstropyDeprecationWarning: Specifying the package name using the 
> "package_name" option in setup.cfg is deprecated - use the "name" option 
> instead.
>   warnings.warn('Specifying the package name using the "package_name" '
> /usr/lib/python3/dist-packages/astropy_helpers/git_helpers.py:114: 
> UserWarning: Error running git: [Errno 2] No such file or directory: 'git'
>   warnings.warn('Error running git: ' + str(e))
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> --use-system-astropy-helpers
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/_astropy_init.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/conftest.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/version.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> creating 

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

[Luca Boccassi]

On Tue, 30 Jun 2020 12:12:34 +0200 Chris Hofstaedtler 
wrote:
> * Simon McVittie  [200630 11:23]:
> > On Tue, 30 Jun 2020 at 10:51:39 +0200, Chris Hofstaedtler wrote:
> > > I'm not sure it was a good idea before. Is static linking something
> > > you actively want to support for glib?
> > 
> > It has worked in the past, Policy says the static library "is usually
> > provided", and we occasionally get bug reports from people who want to
> > link random libraries statically, so I didn't feel comfortable with
> > unilaterally disabling it for no particular reason. The autopkgtest
> > is there partly because things we don't test usually don't work, and
> > partly because static linking to libmount regressed during GLib's move
> > from Autotools to Meson (the pkg-config metadata in GLib was wrong);
> > I added it to confirm that the regression fix had been effective.
> > 
> > If I'm disabling the static library because dependencies no longer
> > support it, then I can redirect bug reporters to the dependency and
> > let them argue their case there if they want to (as with libdbus, which
> > can't be linked statically any more due to libsystemd).
> 
> Understood.
> 
> Feel free to point people at libmount/src:util-linux.
> 
> I'll see about removing libmount's static library in the -dev
> package.
> 
> > People occasionally try to change Policy to say that static equivalents
> > of shared libraries are definitely optional, or even that they are
> > discouraged, but this never reaches consensus, because someone always
> > appears and says "well actually, I rely on Debian shipping shared libfoo
> > and libbar for armhf so that I can statically link them into a binary
> > for my embedded frobnicator device, which
> > (has glibc from 2005|doesn't have glibc|doesn't have space for glibc|...)".
> > The obvious counterpoint that solving this is not really Debian's job
> > is rarely effective.
> > 
> > It is technically possible to link just the top of a dependency stack
> > statically (for example a GLib program with static GLib and libmount,
> > but dynamic libcryptsetup and glibc), but pkg-config doesn't make this
> > straightforward and in practice it requires hard-coding paths to static
> > libraries, so the autopkgtest in GLib doesn't attempt to exercise this.
> 
> Thanks for the explanation!
> 
> Best,
> Chris

Hi,

Note that with this change: 
https://github.com/karelzak/util-linux/pull/1084
we'll be able to use dlopen instead of linking, so the current problem
will go away. The broader issue of availability of static libraries
down the stack is a different matter of course - if it doesn't happen
for this, it will happen for something else and so on.

-- 
Kind regards,
Luca Boccassi


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

Processed: tagging 964055

[Debian Bug Tracking System]

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

> tags 964055 + bullseye sid
Bug #964055 [src:hddemux] hddemux: FTBFS: failed to query server
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#963438: marked as done (ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 15:03:56 +
with message-id 
and subject line Bug#963438: fixed in ccdproc 2.1.0-3
has caused the Debian Bug report #963438,
regarding ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.8 returned exit code 13
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for t in .pybuild/*/build ; do \
>   cp -av ccdproc/tests/data/ ${t}/ccdproc/tests/ ; \
> done
> 'ccdproc/tests/data/' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data'
> 'ccdproc/tests/data/README.rst' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/README.rst'
> 'ccdproc/tests/data/a8280271.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/a8280271.fits'
> 'ccdproc/tests/data/expected_ifc_file_properties.csv' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/expected_ifc_file_properties.csv'
> 'ccdproc/tests/data/flat-mef.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/flat-mef.fits'
> 'ccdproc/tests/data/science-mef.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/science-mef.fits'
> 'ccdproc/tests/data/sip-wcs.fit' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/sip-wcs.fit'
> dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_ccdproc/build; 
> python3.8 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.8.3, pytest-4.6.11, py-1.8.1, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> plugins: openfiles-0.5.0, astropy-header-0.1.2, arraydiff-0.3, 
> hypothesis-5.16.0, remotedata-0.3.2, doctestplus-0.7.0
> collected 305 items / 1 errors / 304 selected
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/run_for_memory_profile.py _
> ccdproc/tests/run_for_memory_profile.py:8: in 
> from memory_profiler import memory_usage
> E   ModuleNotFoundError: No module named 'memory_profiler'
> === warnings summary 
> ===
> ccdproc/extern/bitfield.py:251
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/extern/bitfield.py:251:
>  DeprecationWarning: invalid escape sequence \_
> """
> 
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/log_meta.py:66: 
> DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use 
> inspect.signature() or inspect.getfullargspec()
> (original_args, varargs, keywords, defaults) = inspect.getargspec(func)
> 
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/log_meta.py:82: 
> DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
> `signature` and the `Signature` object directly
> signature_with_arg_added = inspect.formatargspec(original_args, varargs,
> 
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
> !!! Interrupted: 1 errors during collection 
> 
> = 21 warnings, 1 error in 0.81 seconds 
> =
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.8_ccdproc/build; python3.8 -m pytest 
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 
> returned exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ccdproc_2.1.0-2_unstable.log

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

About the archive rebuild: The rebuild was 

Bug#959075: Still not working on Debian testing

[Di Domizio Daniele]

Hello,
bonding still not going up on the latest ifenslave 2.10+nmu2.

My problem seems to be the IFUPDOWN_$IFACE variable on line 84, which is not 
null and makes the script skip the interface enslaving.

I changed line 84 to

if ifquery --state $slave 2>/dev/null; then

and now the bond comes up correctly.

Daniele

Bug#959623: marked as done (ppl: FTBFS: swi_cfli.hh:351:35: error: cannot convert ‘int*’ to ‘size_t*’ {aka ‘long unsigned int*’})

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 14:39:56 +
with message-id 
and subject line Bug#959623: fixed in ppl 1:1.2-8.1
has caused the Debian Bug report #959623,
regarding ppl: FTBFS: swi_cfli.hh:351:35: error: cannot convert ‘int*’ to 
‘size_t*’ {aka ‘long unsigned int*’}
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.)


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

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I. -I../../..  -I../../../interfaces -I../../../interfaces/Prolog 
> -I/interfaces/Prolog -I../../../src -I/usr/lib/swi-prolog/include 
> -I/usr/include/pl  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -frounding-math -g 
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g 
> -fpermissive -W -Wall -c -o ppl_prolog_Polyhedron.lo `test -f 
> '../ppl_prolog_Polyhedron.cc' || echo './'`../ppl_prolog_Polyhedron.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../interfaces 
> -I../../../interfaces/Prolog -I/interfaces/Prolog -I../../../src 
> -I/usr/lib/swi-prolog/include -I/usr/include/pl -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -frounding-math -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall -c 
> ../ppl_prolog_common.cc  -fPIC -DPIC -o .libs/ppl_prolog_common.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../interfaces 
> -I../../../interfaces/Prolog -I/interfaces/Prolog -I../../../src 
> -I/usr/lib/swi-prolog/include -I/usr/include/pl -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -frounding-math -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall -c 
> ../ppl_prolog_Polyhedron.cc  -fPIC -DPIC -o .libs/ppl_prolog_Polyhedron.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../interfaces 
> -I../../../interfaces/Prolog -I/interfaces/Prolog -I../../../src 
> -I/usr/lib/swi-prolog/include -I/usr/include/pl -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -frounding-math -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall -c 
> swi_efli.cc  -fPIC -DPIC -o .libs/swi_efli.o
> In file included from swi_efli.hh:28,
>  from swi_efli.cc:24:
> ../../../src/ppl.hh: In member function 
> ‘Parma_Polyhedra_Library::CO_Tree::iterator 
> Parma_Polyhedra_Library::CO_Tree::insert(Parma_Polyhedra_Library::dimension_type)’:
> ../../../src/ppl.hh:23729:66: warning: implicitly-declared ‘constexpr 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator::tree_iterator(const 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator&)’ is deprecated 
> [-Wdeprecated-copy]
> 23729 |   return iterator(insert_precise(key, Coefficient_zero(), itr));
>   |  ^
> ../../../src/ppl.hh:23444:18: note: because 
> ‘Parma_Polyhedra_Library::CO_Tree::tree_iterator’ has user-provided 
> ‘Parma_Polyhedra_Library::CO_Tree::tree_iterator& 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator::operator=(const 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator&)’
> 23444 |   tree_iterator& operator=(const tree_iterator& itr);
>   |  ^~~~
> ../../../src/ppl.hh:23028:46: note:   initializing argument 3 of 
> ‘Parma_Polyhedra_Library::CO_Tree::tree_iterator 
> Parma_Polyhedra_Library::CO_Tree::insert_precise(Parma_Polyhedra_Library::dimension_type,
>  Parma_Polyhedra_Library::CO_Tree::data_type_const_reference, 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator)’
> 23028 |tree_iterator itr);
>   |~~^~~
> ../../../src/ppl.hh: In member function 
> ‘Parma_Polyhedra_Library::CO_Tree::iterator 
> Parma_Polyhedra_Library::CO_Tree::insert(Parma_Polyhedra_Library::dimension_type,
>  Parma_Polyhedra_Library::CO_Tree::data_type_const_reference)’:
> ../../../src/ppl.hh:23745:51: warning: implicitly-declared ‘constexpr 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator::tree_iterator(const 
> Parma_Polyhedra_Library::CO_Tree::tree_iterator&)’ is deprecated 
> [-Wdeprecated-copy]
> 23745 | return iterator(insert_precise(key, data1, itr));
>   |   ^
> 

Bug#963423: marked as done (auto-multiple-choice: FTBFS: ! LaTeX Error: File `ctexhook.sty' not found.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 14:37:37 +
with message-id 
and subject line Bug#963423: fixed in auto-multiple-choice 1.4.0-5
has caused the Debian Bug report #963423,
regarding auto-multiple-choice: FTBFS: ! LaTeX Error: File `ctexhook.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.)


-- 
963423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: auto-multiple-choice
Version: 1.4.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/I18N'
> msgfmt lang/ar.po -o lang/ar.mo
> msgfmt lang/de.po -o lang/de.mo
> msgfmt lang/es.po -o lang/es.mo
> msgfmt lang/fr.po -o lang/fr.mo
> msgfmt lang/ja.po -o lang/ja.mo
> msgfmt lang/pt_BR.po -o lang/pt_BR.mo
> msgfmt lang/pt_PT.po -o lang/pt_PT.mo
> msgfmt lang/ta.po -o lang/ta.mo
> make[3]: Leaving directory '/<>/I18N'
> pngtopnm icons/auto-multiple-choice.png | ppmtoxpm > 
> icons/auto-multiple-choice.xpm
> ppmtoxpm: (Computing colormap...
> ppmtoxpm: ...Done.  40 colors found.)
> 
> rsvg-convert -f pdf img_src/important.svg -o img_pdf/important.pdf
> rsvg-convert -f pdf img_src/note.svg -o img_pdf/note.pdf
> rsvg-convert -f pdf img_src/warning.svg -o img_pdf/warning.pdf
> dblatex -P latex.encoding=utf8 -b xetex -t tex -p custom.xsl 
> --texstyle=amcdocstyle --xslt-opts="--nonet" --xslt-opts="--catalogs"  
> auto-multiple-choice.fr.xml -o auto-multiple-choice.fr.tex
> Build the book set list...
> Variable $SGML_CATALOG_FILES not set
> Build the listings...
> Variable $SGML_CATALOG_FILES not set
> Variable $SGML_CATALOG_FILES not set
> XSLT stylesheets DocBook - LaTeX 2e (0.3.11py3)
> ===
> Build the listings...
> Variable $SGML_CATALOG_FILES not set
> Variable $SGML_CATALOG_FILES not set
> XSLT stylesheets DocBook - LaTeX 2e (0.3.11py3)
> ===
> dblatex -P latex.encoding=utf8 -b xetex -t tex -p custom.xsl 
> --texstyle=amcdocstyle --xslt-opts="--nonet" --xslt-opts="--catalogs"  
> auto-multiple-choice.ja.xml -o auto-multiple-choice.ja.tex
> Build the book set list...
> Variable $SGML_CATALOG_FILES not set
> Image 'tiger' not found
> 'auto-multiple-choice.en.tex' successfully built
> /usr/bin/perl extrait-fichiers.pl --liste auto-multiple-choice.en.ext 
> auto-multiple-choice.en.xml
> xsltproc --nonet --catalogs --param man.charmap.use.subset "0" --param 
> make.year.ranges "1" --param make.single.year.ranges "1" --param 
> man.output.lang.in.name.enabled "1" 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl 
> auto-multiple-choice.en.xml
> Variable $SGML_CATALOG_FILES not set
> *** File auto-multiple-choice.en.xml
>   I lang=en
>   * extracting modeles/en/simple-txt
> embedded description / N=AMC-TXT format simple example
>   * extracting modeles/en/simple
> embedded description / N=Simple example
>   * extracting modeles/en/groups
> embedded description / N=Groups
>   * extracting modeles/en/separate
> embedded description / N=Separate answers
>   * extracting modeles/en/scoring
> embedded description / N=Scoring strategy
> rm -f html/auto-multiple-choice.en/*.html
> xsltproc --nonet --catalogs --stringparam base.dir 
> html/auto-multiple-choice.en/ doc-xhtml.xsl auto-multiple-choice.en.xml
> Variable $SGML_CATALOG_FILES not set
> Image 'tigre' not found
> 'auto-multiple-choice.fr.tex' successfully built
> Build the listings...
> /usr/bin/perl extrait-fichiers.pl --liste auto-multiple-choice.fr.ext 
> auto-multiple-choice.fr.xml
> Variable $SGML_CATALOG_FILES not set
> Note: Writing auto-multiple-choice.1
> Variable $SGML_CATALOG_FILES not set
> Writing html/auto-multiple-choice.en/prerequis.html for sect1(prerequis)
> Writing html/auto-multiple-choice.en/usagenotes.html for sect1(usagenotes)
> *** File auto-multiple-choice.fr.xml
>   I lang=fr
>   * extracting modeles/fr/simple-txt
> embedded description / N=Exemple simple au format AMC-TXT
>   * extracting modeles/fr/simple
> embedded description / N=Exemple simple
>   * extracting modeles/fr/groupes
> embedded description / N=Groupes
>   * extracting modeles/fr/ensemble
> embedded description / N=R?ponses s?par?es
>   * extracting modeles/fr/bareme
> embedded description / N=Bar?me
> xsltproc --nonet --catalogs --param man.charmap.use.subset "0" 

Bug#960327: marked as done (squid: autopkgtest regression: test_daemons (__main__.BasicTest))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 13:49:22 +
with message-id 
and subject line Bug#960327: fixed in squid 4.12-1
has caused the Debian Bug report #960327,
regarding squid: autopkgtest regression: test_daemons (__main__.BasicTest)
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.)


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

Dear maintainer(s),

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

   passfail
squid  from testing4.11-4
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/squid/5424910/log.gz
autopkgtest [00:09:42]: test squid: [---
Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Enabling module socache_shmcb.
Enabling module ssl.
See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and
create self-signed certificates.
To activate the new configuration, you need to run:
  systemctl restart apache2
Enabling site default-ssl.
To activate the new configuration, you need to run:
  systemctl reload apache2
test_daemons (__main__.BasicTest)
Test daemon ... FAIL
test_ftp_proxy (__main__.BasicTest)
Test ftp ... ok
test_http_proxy (__main__.BasicTest)
Test http ... ok
test_https_proxy (__main__.BasicTest)
Test https ... ok
test_squidclient (__main__.BasicTest)
Test squidclient ... ok
test_zz_apparmor (__main__.BasicTest)
Test apparmor ... ok

==
FAIL: test_daemons (__main__.BasicTest)
Test daemon
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.lb13ubw0/downtmp/build.JEa/src/debian/tests/test-squid.py",
line 120, in test_daemons
self.assertTrue(check_pidfile(exe, pidfile))
AssertionError: False is not true

--
Ran 6 tests in 236.530s

FAILED (failures=1)
autopkgtest [00:13:40]: test squid: ---]




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 4.12-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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: Wed,  1 Jul 2020 10:52:54 +0200
Source: squid
Architecture: source
Version: 4.12-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 960327 960819
Changes:
 squid (4.12-1) unstable; urgency=high
 .
   * Urgency high due to security fixes
 .
   [ Sergio Durigan Junior  ]
   * Don't restart squid by hand on postinst script.
 When installing/upgrading squid, the service is being restarted
 manually in the postinst script, which can break installations that
 have the squid apparmor enabled because it will try to restart the
 service before reloading the apparmor profile.
 There is no reason to restart squid manually, since the 

Bug#960819: marked as done (squid command failure without systemd)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 13:49:22 +
with message-id 
and subject line Bug#960819: fixed in squid 4.12-1
has caused the Debian Bug report #960819,
regarding squid command failure without systemd
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.)


-- 
960819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 4.11-5
Severity: grave


Since the /run/squid directory now depends on systemd squid.service file
for existence the 'squid' binary cannot be run.

This breaks all non-systemd init systems, multi-tenant installations,
and scripts running the squid binary for control commands.


When started without the "service squid" systemd-specific command Squid
produces:

2020/05/17 17:07:48| FATAL: failed to open /run/squid/squid.pid: (2) No
such file or directory
exception location: File.cc(190) open
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 4.12-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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: Wed,  1 Jul 2020 10:52:54 +0200
Source: squid
Architecture: source
Version: 4.12-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 960327 960819
Changes:
 squid (4.12-1) unstable; urgency=high
 .
   * Urgency high due to security fixes
 .
   [ Sergio Durigan Junior  ]
   * Don't restart squid by hand on postinst script.
 When installing/upgrading squid, the service is being restarted
 manually in the postinst script, which can break installations that
 have the squid apparmor enabled because it will try to restart the
 service before reloading the apparmor profile.
 There is no reason to restart squid manually, since the restart will
 be automatically performed later.
 .
   * Drop conffile check for squid < 2.7
 squid 2.7 is long, long gone, so it should be safe to drop the
 postinst code to make sure that /etc/squid/squid.conf was properly
 upgraded.
 .
   * Fix 'pidfile' on d/t/tests-squid.py.
 The pidfile lives under '/run/squid/', not '/run/'. (Closes: #960327)
 .
   [ Juri Grabowski  ]
   * add gbp.conf for squid
 .
   * New upstream version 4.12
 - Fixes security issue SQUID-2020:5 (CVE-2020-14059)
 - Fixes security issue SQUID-2020:6 (CVE-2020-14058)
 - Fixes security issue SQUID-2020:7 (CVE-2020-15049)
 .
   * remove 0004-upstream-bug5041.patch - Fixed in upstream
 .
   [ Luigi Gangitano  ]
 .
   * Move PID file to /run (Closes: #960819)
Checksums-Sha1:
 4855d5e5b5d01769c6d977681a06c4a4cbb8b8bc 2888 squid_4.12-1.dsc
 316b8a343aa542b5e7469d33b9d726bee00679c6 2450564 squid_4.12.orig.tar.xz
 d57379171ab37ca1d154d33805454e1f911019a9 1194 squid_4.12.orig.tar.xz.asc
 f5e3e5c10fd03d0883244ad177f0e218f1174f52 40004 squid_4.12-1.debian.tar.xz
 3b597c33c4f535f94ec71286985d76e76b5be3da 8984 squid_4.12-1_amd64.buildinfo
Checksums-Sha256:
 e1d03abc7b2832c49b54cdab7afbb834347ba8572ce3f87eee659d210fb62287 2888 
squid_4.12-1.dsc
 f42a03c8b3dc020722c88bf1a87da8cb0c087b2f66b41d8256c77ee1b527e317 2450564 
squid_4.12.orig.tar.xz
 675a89c011e30b3899ef6ad5061f8e75892388bec49347b761a844a4421d9c60 1194 
squid_4.12.orig.tar.xz.asc
 9402023a03a18e5dd533c09b48a5ca27ae5e1e5425d0b2c245d3684ec07d3651 40004 
squid_4.12-1.debian.tar.xz
 c73095d75a22d6d8dfb0d889071741af37f11edcab8ffdfb522d6dfc538f9bbf 8984 
squid_4.12-1_amd64.buildinfo
Files:
 6695a12f908f92ef889fd0c711c586a6 2888 web optional squid_4.12-1.dsc
 ad7a4a8a0031cae3435717a759173829 2450564 web optional squid_4.12.orig.tar.xz
 5aeb028653ddb46de1ae98a772a99acc 1194 web optional squid_4.12.orig.tar.xz.asc
 617fb7bee90b082930d03323f0298b04 40004 web optional squid_4.12-1.debian.tar.xz
 e9b459fe2081f366038b762f131f53c4 8984 web optional squid_4.12-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#964040: marked as done (git-buildpackage: FTBFS: E741 ambiguous variable name 'l')

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 13:34:18 +
with message-id 
and subject line Bug#964040: fixed in git-buildpackage 0.9.20
has caused the Debian Bug report #964040,
regarding git-buildpackage: FTBFS: E741 ambiguous variable name 'l'
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.)


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

This package fails to build on current sid.

>From my build log:

  make[2]: Entering directory '/<>'
  flake8 
  ./.pybuild/cpython3_3.8/build/gbp/patch_series.py:108:81: E741 ambiguous 
variable name 'l'
  ./.pybuild/cpython3_3.8/build/gbp/scripts/pq.py:123:22: E741 ambiguous 
variable name 'l'
  ./.pybuild/cpython3_3.8/build/gbp/git/repository.py:518:37: E741 ambiguous 
variable name 'l'
  ./.pybuild/cpython3_3.8/build/gbp/git/repository.py:600:37: E741 ambiguous 
variable name 'l'
  ./gbp/patch_series.py:108:81: E741 ambiguous variable name 'l'
  ./gbp/scripts/pq.py:123:22: E741 ambiguous variable name 'l'
  ./gbp/git/repository.py:518:37: E741 ambiguous variable name 'l'
  ./gbp/git/repository.py:600:37: E741 ambiguous variable name 'l'
  make[2]: *** [Makefile:20: syntax-check] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: git-buildpackage
Source-Version: 0.9.20
Done: =?utf-8?q?Guido_G=C3=BCnther?= 

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated git-buildpackage 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: Wed, 01 Jul 2020 14:47:44 +0200
Source: git-buildpackage
Architecture: source
Version: 0.9.20
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 96396 956103 962916 964040
Changes:
 git-buildpackage (0.9.20) unstable; urgency=medium
 .
   * [e513375] doctest: Ignore exception detail.
 We used the tests to check whether the right exception was returned but
 python 3.8 breaks this again.  Doctest were a nice feature but keeping up
 with the subtle breackage is too cumbersome.
   * [3b05fa8] deb: git: Escape '.' on pristine-tar matches
 '.' is valid in source package names and version numbers so we
 want to match exactly that and not an arbitrary character.
   * [74b3799] pristine-tar: Escape '+' in match regexp.
 When looking for matching file name we need to exscape the valid '+' but
 need to do it late since it must not be escaped for git-grep.
 (Closes: #956103)
   * [a3d9c98] docs: import-ref: Fix wrong --upstream-tree default
 (Closes: #962916)
   * [f68858e] import-orig: Print all found sources with `verbose`
   * [111aa86] get_component_tarballs: Check for signature too
 (Closes: #96396)
   * [4f2569d] git: Drop another doctest that matched exception
 type.
   * [305a4ad] import_orig: Drop all upstream signatures with
 --upstream-signatures=off.  This makes sure we don't use spurious files as
 signatures
   * [0bc42b4] Make flake8 E741 happy
 (Closes: #964040)
Checksums-Sha1:
 c5743b1b35a54d0f20c645fd6d42e9f2af1bb716 2278 git-buildpackage_0.9.20.dsc
 baf791ac4883694ba58de8a44917ae70109f7113 3285996 git-buildpackage_0.9.20.tar.xz
 9355655bc46de453e6fcab4c4dfc22448bf4a977 15996 
git-buildpackage_0.9.20_source.buildinfo
Checksums-Sha256:
 9d82e02c18c48674cc77e3b3f2b25efd117b257735f0558f5454381481a67da4 2278 
git-buildpackage_0.9.20.dsc
 0b9b130351535697cc688daea91a7e91eccc5c17e251604089344ab5f81d17f3 3285996 
git-buildpackage_0.9.20.tar.xz
 b2fe1cf1abe93779e183ba3b7814ccabab637651c0da38b8c369d8e2de3a43d1 15996 
git-buildpackage_0.9.20_source.buildinfo
Files:
 fe6b2a4021bf607805a4640d4f4be679 2278 vcs optional git-buildpackage_0.9.20.dsc
 cba0914c06329da6f3da230b5f01a94c 3285996 vcs 

Bug#964086: r-cran-sf: autopkgtest failures with PROJ 7.1.0

[Bas Couwenberg]

Source: r-cran-sf
Version: 0.9-3+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest of your package fail with PROJ 7.1.0:

 BEGIN TEST testthat.R

 R version 4.0.2 (2020-06-22) -- "Taking Off Again"
 Copyright (C) 2020 The R Foundation for Statistical Computing
 Platform: x86_64-pc-linux-gnu (64-bit)

 R is free software and comes with ABSOLUTELY NO WARRANTY.
 You are welcome to redistribute it under certain conditions.
 Type 'license()' or 'licence()' for distribution details.

 R is a collaborative project with many contributors.
 Type 'contributors()' for more information and
 'citation()' on how to cite R or R packages in publications.

 Type 'demo()' for some demos, 'help()' for on-line help, or
 'help.start()' for an HTML browser interface to help.
 Type 'q()' to quit R.

 > library(testthat)
 > suppressPackageStartupMessages(library(sf))
 > 
 > test_check("sf")
 proj_create: Cannot find proj.db
 proj_create: Cannot find proj.db
 proj_create_operation_factory_context: Cannot find proj.db
 pj_obj_create: Cannot find proj.db
 pj_obj_create: Cannot find proj.db
 Cannot open layer foo
 Reading layer `nospatial' from data source 
`/usr/lib/R/site-library/sf/gpkg/nospatial.gpkg' using driver `GPKG'
 Reading layer `nospatial' from data source 
`/usr/lib/R/site-library/sf/gpkg/nospatial.gpkg' using driver `GPKG'
 OGR: Unsupported geometry type
 -- 1. Failure: filter to sfc works (@test_tidy.R#17)  
--
 d %>% filter(!st_is_empty(geometry)) not identical to d[1, ].
 Component "geometry": Attributes: < Component "class": 1 string mismatch >

 -- 2. Failure: filter to sfc works (@test_tidy.R#19)  
--
 d %>% filter(st_is(geometry, "POINT")) not identical to d[1:2, ].
 Component "geometry": Attributes: < Component "class": 1 string mismatch >

 Failed to create feature 1 in x
 Failed to create feature 1 in x
 == testthat results  
===
 [ OK: 522 | SKIPPED: 17 | WARNINGS: 6 | FAILED: 2 ]
 1. Failure: filter to sfc works (@test_tidy.R#17) 
 2. Failure: filter to sfc works (@test_tidy.R#19) 

 Error: testthat unit tests failed
 Execution halted

https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-sf/6060227/log.gz

The upstream git repo shows several changes related to PROJ 7.1.0,
you can likely cherry-pick those to fix this issue.

Kind Regards,

Bas

Processed: [git-buildpackage/master] Make flake8 E741 happy

[Debian Bug Tracking System]

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

> tag 964040 pending
Bug #964040 [src:git-buildpackage] git-buildpackage: FTBFS: E741 ambiguous 
variable name 'l'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#964040: [git-buildpackage/master] Make flake8 E741 happy

[Guido Günther]

tag 964040 pending
thanks

Date:   Wed Jul 1 14:46:11 2020 +0200
Author: Guido Günther 
Commit ID: 0bc42b4b0312fc965881409e619093cd0fb077f9
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=0bc42b4b0312fc965881409e619093cd0fb077f9
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=0bc42b4b0312fc965881409e619093cd0fb077f9

Make flake8 E741 happy

Closes: #964040

  

Bug#964084: haskell-derive: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-derive
Version: 2.6.5-1
Severity: grave
Justification: renders package unusable

This package is unmaintained (see https://github.com/ndmitchell/derive#readme).
Does not build with newer haskell-src-exts, is not part of Stackage and
has no rev dependencies.

I intend to remove this package.

-- 
Ilias

Bug#963324: marked as done (apertium-apy: FTBFS: AttributeError: module 'tornado.web' has no attribute 'asynchronous')

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 12:33:30 +
with message-id 
and subject line Bug#963324: fixed in apertium-apy 0.11.6-1
has caused the Debian Bug report #963324,
regarding apertium-apy: FTBFS: AttributeError: module 'tornado.web' has no 
attribute 'asynchronous'
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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 6, in 
> from apertium_apy import apy
>   File "/<>/apertium_apy/apy.py", line 38, in 
> from apertium_apy.handlers import (
>   File "/<>/apertium_apy/handlers/__init__.py", line 1, in 
> 
> from apertium_apy.handlers.analyze import AnalyzeHandler  # noqa: F401
>   File "/<>/apertium_apy/handlers/analyze.py", line 5, in 
> 
> from apertium_apy.handlers.base import BaseHandler
>   File "/<>/apertium_apy/handlers/base.py", line 16, in 
> class BaseHandler(tornado.web.RequestHandler):
>   File "/<>/apertium_apy/handlers/base.py", line 177, in 
> BaseHandler
> @tornado.web.asynchronous
> AttributeError: module 'tornado.web' has no attribute 'asynchronous'
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
> python3.8 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit 
> code 13
> make: *** [debian/rules:8: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/apertium-apy_0.11.5-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: apertium-apy
Source-Version: 0.11.6-1
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-apy 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: Wed, 01 Jul 2020 13:45:06 +0530
Source: apertium-apy
Architecture: source
Version: 0.11.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 963324
Changes:
 apertium-apy (0.11.6-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * debian/control:
 + Set debhelper-compat version in Build-Depends.
   * Added debian/upstream/metadata.
 .
   [ Kartik Mistry ]
   * New upstream release (Closes: #963324)
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Updated Maintainer email address.
 + dh to 13.
 + Added 'Rules-Requires-Root' field.
   * Removed debian/apertium-apy.1. Already in upstream.
Checksums-Sha1:
 485dcf01f4925c1a73b8bd709477d492be02e1cb 2167 apertium-apy_0.11.6-1.dsc
 7fbd98703789d30c29914ceab29416e59ba072a4 267848 apertium-apy_0.11.6.orig.tar.gz
 7dc1cde8505be5f80aaf2fce14121775da55440e 6140 
apertium-apy_0.11.6-1.debian.tar.xz
Checksums-Sha256:
 89f3714a74ac910b2769b29f2ed97854cc380a66a82b2fe54b7b83ae8e1ed590 2167 
apertium-apy_0.11.6-1.dsc
 4d2d674d45978de59312a327958f225ef3edeb4f4ef887db71e28e9630cefce6 267848 
apertium-apy_0.11.6.orig.tar.gz
 d3bca8f5295fd984874c96c7dcafb070abd839fa70b72704b2c0c1fc2ea1bc00 6140 
apertium-apy_0.11.6-1.debian.tar.xz
Files:
 6b6367b03cc18955243ed9e680f79fbe 2167 science optional 

Bug#964081: marked as done (rails: CVE-2020-8185: Untrusted users able to run pending migrations in production)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 12:05:03 +
with message-id 
and subject line Bug#964081: fixed in rails 2:6.0.3.2+dfsg-1
has caused the Debian Bug report #964081,
regarding rails: CVE-2020-8185: Untrusted users able to run pending migrations 
in production
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.)


-- 
964081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rails
Version: 2:6.0.3.1+dfsg-1
Severity: grave
Tags: security upstream

Hi

For details please see
https://groups.google.com/g/rubyonrails-security/c/pAe9EV8gbM0

It only affects experimental. To make sure it does not migrate unfixed
to unstable, using an RC severity here.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: rails
Source-Version: 2:6.0.3.2+dfsg-1
Done: Utkarsh Gupta 

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

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

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated rails 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: Wed, 01 Jul 2020 17:12:45 +0530
Source: rails
Architecture: source
Version: 2:6.0.3.2+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 964081
Changes:
 rails (2:6.0.3.2+dfsg-1) experimental; urgency=medium
 .
   * New upstream version 6.0.3.2+dfsg
 - Fixes CVE-2020-8185: Untrusted users able to run pending
   migrations in production (Closes: 964081)
   * Refresh d/patches
Checksums-Sha1:
 85379215adc881eb39727d5eef1c289ecd3c67cf 5246 rails_6.0.3.2+dfsg-1.dsc
 4fadc020c6598d215fa8c64b7d2cdc116940acd0 13966404 
rails_6.0.3.2+dfsg.orig.tar.xz
 543757bfa422d2ef2caf43ad43af0c91727774c1 96416 
rails_6.0.3.2+dfsg-1.debian.tar.xz
 01d976dc376237d49105392ff5b45d429653f2b3 41839 
rails_6.0.3.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 458c3ccd68bca255391779fb9b889485906de7f808f0843d6c0346d727164d89 5246 
rails_6.0.3.2+dfsg-1.dsc
 1e1fb1dcedba5daab17f69aa63d4f5c3e5bb027239f7d223cb960f7405afe20c 13966404 
rails_6.0.3.2+dfsg.orig.tar.xz
 579f7407d3ba95deeca8528e3dd931da440fb04b147fbf23d98334d3e568cd0d 96416 
rails_6.0.3.2+dfsg-1.debian.tar.xz
 f1d45340c6d136ee0e4e2aabeccd360680dd7b63b4cfbe68e8e49c8990ab8189 41839 
rails_6.0.3.2+dfsg-1_amd64.buildinfo
Files:
 78fb749a9b404e8fd225ca7fcc01042f 5246 ruby optional rails_6.0.3.2+dfsg-1.dsc
 2333929498af59636aab238f9ec038e3 13966404 ruby optional 
rails_6.0.3.2+dfsg.orig.tar.xz
 bb531b28af168eaa83d0383fb1a4b96c 96416 ruby optional 
rails_6.0.3.2+dfsg-1.debian.tar.xz
 7f7ef66b865b3c648d49f25531f91e2e 41839 ruby optional 
rails_6.0.3.2+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl78eT0THHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlnPOEACjRSuHrkrg8bHVcAzFh6wGkyTragcQ
9lUUjEpoCi7z/Biy4dA+UYbKoac1jcLoIXTbCxit82M9sXHjRnOyfS3f6S6rONxo
KqEJJYd3m1YEiMvK5xoCoWHm2nWdYd1w+NUM7uJI3wu80znK6aQpd23xo8irURS4
EALP9+V1gsNtle9MGndW7ZLM2/qGy0N+tlRXeMwHoBx+GJdO1VW2rb2bvSYyCH7d
ycq/VOsiAa8/QwYSHzR7AhKvK/66LN/pYed8FW8Y5preM0k3aCOPKe1PcU8x4Bog
HVohnfcR8cvAGn7+qbox2fmGVO0ZnEdElmXkotcZ2T8hREfEZkiUXtaZFCj4F3pS
2GM3vWinzzdu60+PkN/dFDWSrJOC/gI3P5hZF5F6/8zJRK5aFSNb0I6yGGkM/V3B
APne5BTzIij7wyT0GnbAckw2lLF6tnb/Gmp6eOOWlIKbQ3Br/JFBh2nRz6FE7nK8
pmczSMa6gzfOALYq+TTpe2aDASNGWvPiHL9dGhWe7TD7kbvpJJR3mDXxG8hYJm1x
dnuaoALNJOCM3U94tJ6meA6uTlPYFok85FACkXPxComTC5LTsVOtacd77T4RCE7a
2jh+qqDhbEqCiipRYhe4q+1L1JBQXZ4yT/4tblWUfDWhW8gghffimt+hBF/irLkv
0Q6jdRpILmO+eQ==
=DciR
-END PGP SIGNATURE End Message ---

Bug#963812: marked as done (src:edict: fails to migrate to testing for too long: maintainer built arch:all)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 12:03:36 +
with message-id 
and subject line Bug#963812: fixed in edict 2020.07.01-1
has caused the Debian Bug report #963812,
regarding src:edict: fails to migrate to testing for too long: maintainer built 
arch:all
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.)


-- 
963812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: edict
Version: 2019.02.20-1
Severity: serious
Control: close -1 2020.04.28-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: edict
Source-Version: 2020.07.01-1
Done: Ludovic Drolez 

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

Debian distribution maintenance software
pp.
Ludovic Drolez  (supplier of updated edict 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: Wed, 01 Jul 2020 10:05:09 +0200
Source: edict
Architecture: source
Version: 2020.07.01-1
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Ludovic Drolez 
Closes: 963812
Changes:
 edict (2020.07.01-1) unstable; urgency=medium
 .
   * New upstream release
   * Source only upload. Closes: #963812
Checksums-Sha1:
 b40f50d77ab68b109db7379ba3896104e73e2a83 1404 edict_2020.07.01-1.dsc
 b9f786a485f6bc6d27eb7a6ae809c4b8e6795eca 13692027 edict_2020.07.01.orig.tar.gz
 fc910dfa7adf3d5e31080107d10cd82d87aad5d6 9156 edict_2020.07.01-1.debian.tar.xz
 b7c9dc8f1921bf2a52f7907848c61d03edca9f50 5871 
edict_2020.07.01-1_amd64.buildinfo
Checksums-Sha256:
 cd4fa93baa05df6f0d58f2525563da044c553a886d835c27e0c57aa7dbee10f1 1404 
edict_2020.07.01-1.dsc
 2cdf5d6b23911d1f2ea26388cceed1e13f753f359dde97dd0ea02855b1676143 13692027 
edict_2020.07.01.orig.tar.gz
 09c071e4edf887821152dd8ffcb95ae8fb50dfc98f299bf1b719c312296d2a74 9156 
edict_2020.07.01-1.debian.tar.xz
 1850a68050c6995283ce72e8fa337b373bddf64fd46d02875aee8062a5ce3d64 5871 
edict_2020.07.01-1_amd64.buildinfo
Files:
 6f36ee06334999df3f425aac10a0e77f 1404 text optional edict_2020.07.01-1.dsc
 ca7d8e10be001055865032d130b3f167 13692027 text optional 
edict_2020.07.01.orig.tar.gz
 dc640228e89194e9c89efc027057 9156 text optional 
edict_2020.07.01-1.debian.tar.xz
 

Bug#950762: marked as done (ksh,ksh93: both ship /etc/skel/.kshrc with insufficient Conflicts/Breaks/Replaces)

[Debian Bug Tracking System]

Your message dated Wed, 1 Jul 2020 07:48:24 -0400
with message-id <20200701114824.ga3627...@ninsei.weeraman.com>
and subject line Conflicts relation with ksh93
has caused the Debian Bug report #950762,
regarding ksh,ksh93: both ship /etc/skel/.kshrc with insufficient 
Conflicts/Breaks/Replaces
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.)


-- 
950762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ksh,ksh93
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Control: found -1 2020.0.0-5
Control: found -1 93u+20120801-6

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install ksh
  # (1)
  apt-get install ksh93
  apt-get remove ksh93
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /etc/skel/.kshrc

(also happens with both packages swapped)

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

Since you obviously want the two packages to be co-installable,
* either move /etc/skel/.kshrc to a separate packages, and let both depend on it
* or let only one (ksh) ship it and the other (ksh93) depend on it.

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

1m14.7s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/ksh.list expected(root, root, - 100644, 1012, None) != 
found(root, root, - 100644, 995, None)
1m14.7s ERROR: FAIL: After purging files have disappeared:
  /etc/skel/.kshrc   owned by: ksh93

1m14.7s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/ksh.listnot owned


cheers,

Andreas


ksh=2020.0.0-5_ksh93=93u+20120801-6.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: ksh/2020.0.0+really93u+20120801-6

A conflicts relation with ksh93 was added to address this as ksh2020 was
rolled back to ksh93 in src:ksh. Plus, src:ksh93 is in the ftp-master
queue for removal.

-- 
Regards
Anuradha--- End Message ---

Bug#936508: fdb: Python2 removal in sid/bullseye

[Bastian Germann]

What was the point of introducing the python-fdb (py2) package again? It
will never enter testing.

Bug#964081: rails: CVE-2020-8185: Untrusted users able to run pending migrations in production

[Salvatore Bonaccorso]

Source: rails
Version: 2:6.0.3.1+dfsg-1
Severity: grave
Tags: security upstream

Hi

For details please see
https://groups.google.com/g/rubyonrails-security/c/pAe9EV8gbM0

It only affects experimental. To make sure it does not migrate unfixed
to unstable, using an RC severity here.

Regards,
Salvatore

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

[Axel Beckert]

Hi,

Mark Hindley wrote:
> > > I am struggling to understand how libelogind0 came to be installed in the 
> > > build
> > > in the first place. Can you help me understand that?
> > 
> > No idea; apt's resolver is sometimes creative.  Other examples include
> > [1], [2], [3].
> > 
> >   [1]: 
> > https://buildd.debian.org/status/logs.php?pkg=hplip=3.20.6%2Bdfsg0-1=amd64
> >   [2]: 
> > https://buildd.debian.org/status/logs.php?pkg=gnome-applets=3.37.2-1=amd64
> >   [3]: 
> > https://buildd.debian.org/status/logs.php?pkg=kopete=4%3A20.04.1-1=amd64
> 
> Thanks. I have looked through these and, again, I can see no other regerences 
> to
> either elogind or systemd that might explain this.
> 
> However, all 4 examples you have given relate to builds for
> experimental.


Is it still the case that the buildds use aptitude for resolving
dependencies on experimental builds? Because aptitude might be even
more "creative" than apt in that regards.

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

Bug#959852: marked as done (dracut-live: missing Breaks+Replaces: dracut-core (<< 050))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 10:33:40 +
with message-id 
and subject line Bug#959852: fixed in dracut 050+65-1
has caused the Debian Bug report #959852,
regarding dracut-live: missing Breaks+Replaces: dracut-core (<< 050)
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.)


-- 
959852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dracut-live
Version: 050+35-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../dracut-live_050+35-4_all.deb ...
  Unpacking dracut-live (050+35-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dracut-live_050+35-4_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/dracut/modules.d/90dmsquash-live/apply-live-updates.sh', which is 
also in package dracut-core 048+80-2
  Errors were encountered while processing:
   /var/cache/apt/archives/dracut-live_050+35-4_all.deb

There might also be a file conflict on dracut-network on these files:
  usr/lib/dracut/modules.d/90livenet/fetch-liveupdate.sh
  usr/lib/dracut/modules.d/90livenet/livenet-generator.sh
  usr/lib/dracut/modules.d/90livenet/livenetroot.sh
  usr/lib/dracut/modules.d/90livenet/module-setup.sh
  usr/lib/dracut/modules.d/90livenet/parse-livenet.sh
which could require an additional B+R: dracut-network (<< 050)
but that cannot be tested currently due to the dracut-core conflict
causing an early failure.

cheers,

Andreas


dracut-core=048+80-2_dracut-live=050+35-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dracut
Source-Version: 050+65-1
Done: Thomas Lange 

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

Debian distribution maintenance software
pp.
Thomas Lange  (supplier of updated dracut 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: Wed, 01 Jul 2020 12:13:36 +0200
Source: dracut
Architecture: source
Version: 050+65-1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Lange 
Changed-By: Thomas Lange 
Closes: 959852 963989
Changes:
 dracut (050+65-1) unstable; urgency=medium
 .
   * control: add breaks and replaces, Closes: #959852
   * merge upstream changes, Closes: #963989
   * add module nvmf
Checksums-Sha1:
 e8a709ca8e878f01494134840f085548c69f6efe 2330 dracut_050+65-1.dsc
 01bfcda40bcbc4bb63aca7b85e90ab7db376da8d 305572 dracut_050+65.orig.tar.xz
 b8cd2e261dcb38fc6e64a6abb30436c36d95c41c 12800 dracut_050+65-1.debian.tar.xz
 c16c4cb6dda90e7e68ae4ebd08ccc23357a866ad 8278 dracut_050+65-1_amd64.buildinfo
Checksums-Sha256:
 0b6b8686199b7a21447de85d9efbaf43734f0a8cbf8aece19ed2fdd92f6bfa7c 2330 
dracut_050+65-1.dsc
 beaf7bc474e203745833f1fc2e8248b1404939e3a074b5ab53f15a22cc379efb 305572 
dracut_050+65.orig.tar.xz
 a497613d3b360ce26415c49d5e68d665b9aa1ff8c7048318c53c5872cd5cd561 12800 
dracut_050+65-1.debian.tar.xz
 4d87da23d0dbe6c255009ae4d903e0da94829961e50fd0a7f66a3a8905ee7932 8278 
dracut_050+65-1_amd64.buildinfo
Files:
 6fdb7c82831a37de4330cab391d602a5 2330 utils optional dracut_050+65-1.dsc
 deca5b962c463eea7780f85fe023310c 305572 utils optional 
dracut_050+65.orig.tar.xz
 872ebee6d219d4ffbf050e73ee126637 12800 utils optional 
dracut_050+65-1.debian.tar.xz
 8e719fca1032e3bf142789323e73eb09 8278 utils optional 
dracut_050+65-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAl78YzsRHGxhbmdlQGRl
Ymlhbi5vcmcACgkQK/jZ/gdLzeQZdg/+K2qU5XW1Td0hK+k+pTArQaH5WOTE/YQU
KoaGQoGC92K/XsWEfHCos5FSpfeiE4WBfiNGSQtPEJgMLEyH7Y6QCbqGcsC/AMlP

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

[Mark Hindley]

Ansgar,

On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote:
> On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote:
> > I am struggling to understand how libelogind0 came to be installed in the 
> > build
> > in the first place. Can you help me understand that?
> 
> No idea; apt's resolver is sometimes creative.  Other examples include
> [1], [2], [3].
> 
>   [1]: 
> https://buildd.debian.org/status/logs.php?pkg=hplip=3.20.6%2Bdfsg0-1=amd64
>   [2]: 
> https://buildd.debian.org/status/logs.php?pkg=gnome-applets=3.37.2-1=amd64
>   [3]: 
> https://buildd.debian.org/status/logs.php?pkg=kopete=4%3A20.04.1-1=amd64

Thanks. I have looked through these and, again, I can see no other regerences to
either elogind or systemd that might explain this.

However, all 4 examples you have given relate to builds for experimental. Is
that always the case? If so, I wonder if this is related to the presence in
experimental of libpam-elogind-compat?

Mark

Processed: Re: Bug#963857: gammaray: FTBFS on IPv6-only environments

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #963857 [src:gammaray] gammaray: FTBFS on IPv6-only environments
Added tag(s) unreproducible.

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

Bug#963857: gammaray: FTBFS on IPv6-only environments

[Dmitry Shachnev]

Control: tags -1 unreproducible

Hi Dominic!

On Sun, Jun 28, 2020 at 01:00:21PM +0100, Dominic Hargreaves wrote:
> Source: gammaray
> Version: 2.11.1-1
> Severity: serious
> Justification: FTBFS (when it built before)
>
> During archive-wide test rebuilding of an IPv6-only environment (which
> appears on some normal buildds)[1] we noticed that this package fails:
>
> The full log is available at 
> http://perl.debian.net/rebuild-logs/sid-v6only/gammaray_2.11.1-1/gammaray_2.11.1-1_amd64-2020-06-14T14:09:54Z.build
>
> One way to replicate this environment is like so:
>
>   # unshare -n
>   # ip li set lo up
>   # ip li add dummy0 type dummy
>   # ip li set dummy0 up

I cannot reproduce this bug using your instructions. Can you please check
again if it happens with Qt 5.14 from unstable (and with gammaray 2.11.1-2
from unstable too)?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)

[Dmitry Shachnev]

Control: severity -1 important

On Tue, Jun 30, 2020 at 12:50:36AM +0200, ydir...@free.fr wrote:
> The other pyside2 packages (code, gui etc) were still at 5.15.0-1~exp1.
>
> If I just update qtsvg to 5.15.0-2 the segfault still happens.
>
> Update the rest of pyside2 triggers a huge cascading of upgrades to Qt 5.14
> which had not been done when I had installed the exp packages, and when I
> updated qtsvg initially.
>
> Among them:
>
>  Unpacking libqt5svg5:amd64 (5.14.2-2) over (5.12.5-2) ...
>
> With all this upgraded, I confirm there is no segfault any more.
>
> Thus, the problem is likely caused by an undeclared versioned dependency on an
> underlying lib, and libqt5svg5 looks like a good candidate.  

I have now bumped Qt build-dependencies in Git, that should help.

In the mean time, downgrading the severity of this bug as it should not
block Qt migration to testing (especially when we require new Qt).

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #963983 [python3-pyside2.qtsvg] python3-pyside2.qtsvg: segfault on import
Severity set to 'important' from 'grave'

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

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)

[Dmitry Shachnev]

On Wed, Jul 01, 2020 at 11:29:39AM +0800, pengzon...@uniontech.com wrote:
> Hi!
>
> Some information on this, it look like  the same issue as #963709.
>
> (gdb) r PnsAppWebX.py 
> Starting program: /usr/bin/python PnsAppWebX.py
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
> [New Thread 0xe6bc41e0 (LWP 21532)]
> Could not initialize GLX
>
> Thread 1 "python" received signal SIGABRT, Aborted.
> __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
> 50 ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.
> (gdb) b libglxmapping.c:432
> No source file named libglxmapping.c.
> Make breakpoint pending on future shared library load? (y or [n]) y
> Breakpoint 1 (libglxmapping.c:432) pending.
> (gdb) p vendor->dlhandle
> No symbol "vendor" in current context.
> (gdb) p (char *)dlerror()
> $1 = 0xab233500 "/lib/aarch64-linux-gnu/libglapi.so.0: cannot allocate 
> memory in static TLS block"
> (gdb) 
>
> Now, is this the only  way we can fix this issue？and is there any way to
> fix this issue fundamentally？
> Thank you for letting me know.

As I said in that bug, there is a glibc patch currently under review,
which is *maybe* related:

https://sourceware.org/pipermail/libc-alpha/2020-May/114247.html

But I have not tested it.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#956712: Bug 956712 (emacs in Debian Stable)

[Heenec]

On 28.06.20 05:23, R S Chakravarti  wrote:
> Hi,
> I don't have a deep knowledge of the OS but I was surprised to see a bug
> reported in
> this binary package which is a metapackage. I already had emacs-lucid
> installed when
> I installed emacs. Since package emacs contains only documentation, the
> reported bug
> shouldn't affect me. It seems to me that it ought to pertain to
> emacs-gtk or emacs-
> lucid. Would you please let me know if I am right?
> Best wishes,
> RSC.

Yes, you are actually right, this bug should not belong to the emacs
metapackage, but to one of its dependencies. It's my mistake.

I suppose, that the actual bug may reside in emacs-common or in
emacs-bin-common, on which emacs-gtk and emacs-lucid depend, but I am
not sure.

And no, the emacs metapackage depends on emacs-gtk, emacs-lucid or
emacs-nox, so your installation is very likely affected.

Thank you for noticing.

Heenec

Bug#964046: marked as done (python3-skimage: missing (unversioned) Breaks+Replaces: python-skimage)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 08:36:55 +
with message-id 
and subject line Bug#964046: fixed in skimage 0.17.2-2
has caused the Debian Bug report #964046,
regarding python3-skimage: missing (unversioned) Breaks+Replaces: python-skimage
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.)


-- 
964046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-skimage
Version: 0.17.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../python3-skimage_0.17.2-1_all.deb ...
  Unpacking python3-skimage (0.17.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-skimage_0.17.2-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/skivi.1.gz', which is also in 
package python-skimage 0.14.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-skimage_0.17.2-1_all.deb

Since python-skimage no longer exists, the B+R can be unversioned.


cheers,

Andreas


python-skimage=0.14.2-2_python3-skimage=0.17.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.17.2-2
Done: Ole Streicher 

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated skimage 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: Wed, 01 Jul 2020 09:27:57 +0200
Source: skimage
Architecture: source
Version: 0.17.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 919852 964046
Changes:
 skimage (0.17.2-2) unstable; urgency=low
 .
   * Remove outdated link to bootstrap-responsive.css (Closes: #919852)
   * Declare Breaks+Provides for python-skimage (Closes: #964046)
Checksums-Sha1:
 1641250d7c250c44a972c595b5dc7a72d9bc040a 2855 skimage_0.17.2-2.dsc
 9d475cb203947b20398cc3a6f5026e91a90079c0 23508 skimage_0.17.2-2.debian.tar.xz
Checksums-Sha256:
 50fda818637f09998edd26772b0d328d8310658497dca2de121c1b6e6858d0cb 2855 
skimage_0.17.2-2.dsc
 73499979cda578c7b0d4115e5e105465332ec2c7013b4010244e314e87026785 23508 
skimage_0.17.2-2.debian.tar.xz
Files:
 28d31a609038723705f05fc68733e056 2855 python optional skimage_0.17.2-2.dsc
 3d03f2a531085b5959e88325a26e0c4e 23508 python optional 
skimage_0.17.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl78RfgACgkQcRWv0HcQ
3Pd4pA/6A4CGr49DJSO2u4hjfj1E8k28rHLZz+xeAOi4T7oTHWnsfYfHFPbd1lKr
qIyyf0dxSl3o45GVEEurvfdHj79LbcO8Lp25EfTgey5778NWvVs0bEvIbY3fYV4d
eERc5ox0kPimjGUYs2Hmhhln8NSr92WIerU+BmGYqjHC5y8GDFHVkKadtYEv22Ow
BFAOMWcisiY/yeuUfCBgTkflcSnFMrbN5eYbqSqOfevwmVsoT6Wj6WduRcYXf6gB
l+fTtwq8smGf2I9m/LwN4Prvi6yLMDNUNwsAEoFo6DJwdbrOATBU150LBJBxCuOK
2tFBdVNbicE6VuMGwN4Iem+1HEaKjYdndvBCybjEo5FOC1gV+6Da1V9IxtazkK7P
wKwJ9byASbcUzFLy8KZ73FAGNXS1D7Iat4H9RkhJAhNhryABQOUuUQjNvCEQWTQL
mDrdZCGc4vwP13+UGaNHdKHP71XG7bf4tlZNfhq+KYlpy9vtGyb6FBGnPuxyIS9t
cznsMcNiDNMqgDPO825iXZJm4E9OjulMLqNa4tkBk8b4n8E6Lpjmewx0lKY2TyK2
w6QJLX+4YYSbrsc7qdcJMcPdeilcAwijyt6WkAy0a+CTQB5Hw5Fohh/8Pat/mACK
nPK7dl9BkC8RMSAIiJhsBQUv0hSL1SuyyqjRsBOiLzcQhekLtnE=
=4dMg
-END PGP SIGNATURE End Message ---

Bug#960347: marked as done (libsolv{,ext}-dev: missing (unversioned) Breaks+Replaces: libsolv{,ext}0-dev)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 08:36:40 +
with message-id 
and subject line Bug#960347: fixed in libsolv 0.7.14-1
has caused the Debian Bug report #960347,
regarding libsolv{,ext}-dev: missing (unversioned) Breaks+Replaces: 
libsolv{,ext}0-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.)


-- 
960347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsolv-dev,libsolvext-dev
Version: 0.7.11-1
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 without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libsolvext-dev:amd64.
  Preparing to unpack .../libsolvext-dev_0.7.11-1_amd64.deb ...
  Unpacking libsolvext-dev:amd64 (0.7.11-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsolvext-dev_0.7.11-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/libsolvext.pc', 
which is also in package libsolvext0-dev:amd64 0.6.36-2
  Selecting previously unselected package libsolv-dev:amd64.
  Preparing to unpack .../libsolv-dev_0.7.11-1_amd64.deb ...
  Unpacking libsolv-dev:amd64 (0.7.11-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsolv-dev_0.7.11-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/libsolv.pc', which 
is also in package libsolv0-dev:amd64 0.6.36-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libsolvext-dev_0.7.11-1_amd64.deb
   /var/cache/apt/archives/libsolv-dev_0.7.11-1_amd64.deb

Since the versioned -dev packages will go away, the B+R can be unversioned.


cheers,

Andreas


libsolv0-dev=0.6.36-2_libsolv-dev=0.7.11-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libsolv
Source-Version: 0.7.14-1
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated libsolv 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: Wed, 01 Jul 2020 09:34:51 +0200
Source: libsolv
Architecture: source
Version: 0.7.14-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Mike Gabriel 
Closes: 960347
Changes:
 libsolv (0.7.14-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control:
 + Add B:/R: for libsolv0-dev -> libsolv-dev and libsolvext0-dev ->
   libsolvext-dev. (Closes: #960347).
   * debian/patches:
 + Rebase 1005_install-cmake-module-into-libdir.patch.
   * debian/copyright:
 + Update auto-generated copyright.in file.
 + Update copyright attributions.
   * debian/libsolv1.lintian-overrides:
 + Renamed tag: shlib-calls-exit -> exit-in-shared-library.
Checksums-Sha1:
 4a0ad19b1dd9a20b4747a3d93fb37ff76ce4c150 2403 libsolv_0.7.14-1.dsc
 2a6341df038f5a7ff0c46985ba9b1bce8609c2a1 716644 libsolv_0.7.14.orig.tar.gz
 908b962e450ccd4a33b8a8302eb289894e269f0a 20268 libsolv_0.7.14-1.debian.tar.xz
 d952377deac567e3ddf649ad67ac1977a775b0dc 9015 libsolv_0.7.14-1_source.buildinfo
Checksums-Sha256:
 84e150e1786549fdaad8816e468ddbbe8e44e9c30c13a2e63a6cf96df8100314 2403 
libsolv_0.7.14-1.dsc
 34a67c23cedd38a949607d8cdbd867aa4b07556f18a57e17162ac962bbdbbf54 716644 
libsolv_0.7.14.orig.tar.gz
 b23b931f1ed7dbe5abef55366597e69eefd179d172c9cc8f1ebf6729dc357c1a 20268 
libsolv_0.7.14-1.debian.tar.xz
 e88e81e434f862ff54afaad758aff75f23d6fd82d1d6143f86faf7837309722a 9015 
libsolv_0.7.14-1_source.buildinfo
Files:
 37fe8afb3ef4e3b91c8658d4633ace9c 2403 admin optional libsolv_0.7.14-1.dsc
 a7a991fa70c310c31fabedc5b12453af 716644 admin optional 
libsolv_0.7.14.orig.tar.gz
 

Bug#960762: [Pkg-libvirt-maintainers] Bug#960762: libvirt: random (?) test hangs

[Guido Günther]

Hi,
On Tue, Jun 30, 2020 at 09:28:34PM +0200, Andrea Bolognani wrote:
> On Sat, May 16, 2020 at 03:00:46PM +0300, Adrian Bunk wrote:
> > Source: libvirt
> > Version: 6.0.0-7
> > Severity: serious
> > Tags: ftbfs
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=libvirt=all=6.0.0-7=1589452859=0
> > https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.0.0-7=1589494701=0
> > 
> > ...
> > make  check-TESTS
> > make[4]: Entering directory '/<>/debian/build/tests'
> > make[5]: Entering directory '/<>/debian/build/tests'
> > PASS: sockettest
> > PASS: virbuftest
> > PASS: virhostcputest
> [...]
> > PASS: virsh-vcpupin
> > PASS: virsh-optparse
> > PASS: virt-aa-helper-test
> > E: Build killed with signal TERM after 150 minutes of inactivity
> 
> Has anyone managed to reproduce this? I've built 6.0.0-7 from source
> in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder
> and in a sid:i386 VM, without encountering a single failure.

I tried to reproduce too when this came in and couldn't.
 -- Guido

> 
> The latest build attempt on i386 also failed:
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.4.0-1=1593097042=0
> 
> However, the failure in this case was not limited to i386 and the
> error was completely different, caused this time by
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963704
> 
> All I can think of at this point is a temporary glitch of the
> buildd. In a couple of weeks, when we upload 6.5.0, we'll hopefully
> see that build fine on all architectures, i386 included...
> 
> Does anyone have any better theories? Or a way to dig further?
> 
> -- 
> Andrea Bolognani 
> Resistance is futile, you will be garbage collected.



> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#964027: marked as done (incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jul 2020 06:05:18 +
with message-id 
and subject line Bug#964027: fixed in openafs 1.8.6-1
has caused the Debian Bug report #964027,
regarding incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" 
[...] undefined!
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.)


-- 
964027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openafs-modules-dkms
Version: 1.8.6~pre1-3
Severity: grave
Justification: package is not compatible with the current kernel

The package cannot successfully be installed under 5.7.0-1-amd64.
The build fails with:

  LD [M]  
/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP/afspag.o
  MODPOST 2 modules
ERROR: modpost: "__pagevec_lru_add" 
[/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP/openafs.ko]
 undefined!
make[5]: *** 
[/usr/src/linux-headers-5.7.0-1-common/scripts/Makefile.modpost:99: __modpost] 
Error 1
make[4]: *** [/usr/src/linux-headers-5.7.0-1-common/Makefile:1658: modules] 
Error 2
make[3]: *** [/usr/src/linux-headers-5.7.0-1-common/Makefile:180: sub-make] 
Error 2
make[3]: Leaving directory '/usr/src/linux-headers-5.7.0-1-amd64'
FAILURE: make exit code 2
make[2]: *** [Makefile.afs:279: openafs.ko] Error 1
make[2]: Leaving directory 
'/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP'
make[1]: *** [Makefile:186: linux_compdirs] Error 2
make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs'
make: *** [Makefile:15: all] Error 2

The entire build log, /var/lib/dkms/openafs/1.8.6pre1/build/make.log, is
attached.

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

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

Versions of packages openafs-modules-dkms depends on:
ii  dkms   2.8.2-2
ii  libc6-dev  2.31-0experimental0
ii  perl   5.30.3-4

Versions of packages openafs-modules-dkms recommends:
ii  openafs-client  1.8.6~pre1-3

openafs-modules-dkms suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A
DKMS make.log for openafs-1.8.6pre1 for kernel 5.7.0-1-amd64 (x86_64)
Tue 30 Jun 2020 12:34:56 PM EDT
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... xsltproc
checking for fop... no
checking for dblatex... no
checking for docbook2pdf... no
configure: WARNING: Docbook stylesheets not found; some documentation can't be 
built
checking for kindlegen... no
checking for doxygen... no
checking for dot... dot
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes