Bug#942135: Сannot install Perl 5.30.0-6 without deleting the libgtk2-perl package

[intrigeri]

Hi,

Dominic Hargreaves (2020-11-10):
> On Tue, Nov 10, 2020 at 09:03:42AM +0100, intrigeri wrote:
>> Dominic Hargreaves (2020-11-09):
>> > A year on, it seems there's almost no realistic prospect of this
>> > package coming back. Shall we remove it from sid?
>> 
>> Thank you for caring!
>> 
>> Quoting the plan I proposed #912860: "I intend to remove libgtk2-perl
>> from testing soon after the Buster release, and then from sid later
>> during the Bullseye development cycle".

> We're quite a way through the bullseye development cycle already but
> I guess you mean once we're into the deep freeze when there is no longer
> any chance of reviving those packages for bullseye, which makes sense
> to me.

Actually, when writing my previous message here, I misread my own
initial proposal. You're indeed correct that under this proposal,
we could remove libgtk2-perl from sid right away. Thank you for
your patience! :)

Given the upcoming freeze, I'd like to give the maintainers of the
reverse-dependencies a last chance to get their package in Bullseye
before migration of new source packages to testing is disabled
(2021-02-12), which would be required if we removed libgtk2-perl and
all its reverse-dependencies right away.

In particular:

 - tinyca: a few months ago the maintainer was actively working on
   a solution

 - gprename: upstream ported to GTK 3, now waiting for the new release
   to be packaged & uploaded

So, I'm now leaning towards removing libgtk2-perl and its remaining
reverse-dependencies from sid at any time after 2021-02-12 (I don't
care much when exactly). At that point, indeed it'll be too late for
these packages to go into Bullseye, and their maintainers will have
2 years to find a solution.

Does this make sense to you?

Cheers!

Bug#979027: manpages-it: Package severely outdated, should not be shipped (as is) with Bullseye, successor to be released soon

[Helge Kreutzmann]

Package: manpages-it
Version: 3.73-2.1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: "Dr. Tobias Quathamer" , Francesco Paolo 
Lovergine 

The last real upload happend in 2014, more than 6 years ago. The
upstream man pages are now at version 5.10-1, even o-o-stable (which
will become o-o-o-stable once bullseye is released) has a newer
version of the man pages.

There has been extensive work on the upstream man pages as well
(inclunding, but not limited to, new major version of the tools
described). 

Therefore these very outdated man pages are strongly misleading to
Italian speaking users and should not be shipped.

Additionally, upstream has moved its translation to manpages-l10n
where current translations (as far as possible) are maintained. The
upstream maintainer Mario Blättermann has just announced that Italian
will be distributed (first time) in the next major version, slated 
for release on or around February 6th. 

It is the intention of the Debian manpage-l10n maintainers to also
enable Italian in that manpage-l10n version.

Therefor Itialian users will enjoy current localized man pages (just
shipped by a different source package).

Francesco, if you want to help us in the transition (I'm currently
helping Tobias in maintaining manpages-l10n, but more help would be
appreciated) please contact us.

Release team: Even if for some highly unlikely reason manpages-l10n
would not ship manpages-it, Bullseye should not mislead Itialian users
for thinking to read current (localized) translation when in fact it
is more than 6 years old.

-- System Information:
manpages-it depends on no packages.

manpages-it recommends no packages.

Versions of packages manpages-it suggests:
ii  konqueror [man-browser]  4:20.08.3-1
ii  man-db [man-browser] 2.9.3-2

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#976836: libgnutls30: 3.7.0-3 fails to connect on debian.ethz.ch

[Andreas Metzler]

On 2021-01-01 Petter Reinholdtsen  wrote:
> Is there any hope to have a fix for this in unstable soon?  The
> issue block ring and opendht from migrating to testing.

Hello Petter,

3.7.0-5 in unstable features the patch from the yet unmerged
. I would like
to give it more testing in unstable than two non-workdays provide,
though.

> Is this really a RC issue?  I can use https to deb.debian.org and
> some other https mirrors, so the problem seem to trigger only on
> selected mirror sites.  Anyone know of a site currently failing, after
> the debian.ethz.ch one was fixed?
> fixed.

As noted in the upstream bug report this bug is easy to make when using
acme-tiny, so I suspect it to be not that uncommon.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#979026: r-cran-rgdal: autopkgtest failure with PROJ 7.2.1

[Bas Couwenberg]

Source: r-cran-rgdal
Version: 1.5-18+dfsg-1
Severity: serious
Tags: upstream fixed-upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest of your package fail with PROJ 7.2.1:

 Error: isTRUE(all.equal(a, matrix(c(-5.917698, -1.87195), ncol = 2),   is 
not TRUE
 Execution halted
 autopkgtest [23:01:36]: test run-unit-test: ---]
 autopkgtest [23:01:36]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
 run-unit-testFAIL non-zero exit status 1

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rgdal/9312472/log.gz

This appears to be an issue with how upstream uses PROJ incorrectly,
as discussed on the PROJ list:

 https://lists.osgeo.org/pipermail/proj/2020-December/010014.html

Upstream doesn't appear to have a public VCS, so it's unclear if the fix
posted on the PROJ list can be easily turned into a patch for the Debian
package.

Kind Regards,

Bas

Processed: ospd-openvas' autopkg tests fail

[Debian Bug Tracking System]

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

> found 978522 1.0.1-2
Bug #978522 [src:ospd-openvas] ospd-openvas' autopkg tests fail
Marked as found in versions ospd-openvas/1.0.1-2.
> thanks
Stopping processing here.

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

Processed: re: rust-libm: autopkgtest failure on i386: 1.10009765625 is not equal to 2.0

[Debian Bug Tracking System]

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

> tags 979002 +patch
Bug #979002 [src:rust-libm] rust-libm: autopkgtest failure on i386: 
1.10009765625 is not equal to 2.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#979002: rust-libm: autopkgtest failure on i386: 1.10009765625 is not equal to 2.0

[plugwash]

tags 979002 +patch
thanks

I just whipped up a patch which made cargo test pass on debian i386, 
it's not particularly pretty though.


floor, ceil, round, roundf and rem_pio2f (but not floorf or ceilf) use 
an add/sub trick to round stuff to the nearest integer. Unfortunately 
while this trick works on architectures that use modern FPUs it seems to 
break on x87. Presumably due to excess precision.



For floor and ceil I made the functions use alternative implementations 
based on the proposal at

https://github.com/rust-lang/libm/issues/219

For the other functions I added a conversion to/from bits, this seems to 
force rounding and make the tests pass, though I don't know for sure how 
robust that solution is. The finer points of rust floating point on x87 
do not seem to be documented anywhere.


Finally I loosened the test slightly for j1f

I've pushed my changes at https://github.com/plugwash/libm 
 and also posted about them upstream

at https://github.com/rust-lang/libm/issues/243

I may or may not add these changes to the Debian package later.

Processed: pmix: breaks openmpi autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #978066 {Done: Alastair McKinstry } [src:pmix] pmix: 
breaks openmpi autopkgtest
'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 openmpi/4.1.0-2.

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

Bug#978066: pmix: breaks openmpi autopkgtest

[Graham Inggs]

Control: reopen -1

pmix/4.0.0~rc1-2 from unstable still causes the autopkgtests of
openmpi 4.0.5-7 in testing to fail [1], see for example:

4.0.5-7   2020-12-29 13:13:26 UTC   pmix/4.0.0~rc1-2 src:pmix from
unstable   2m 14s fail   britney test log (9.92 KB)   artifacts (3.17
KB)

Does libpmix2 need a Breaks: libopenmpi3 (<< 4.1.0-3) or similar [2]?

Is the Depends: libpmix2 in libopenmpi3 needed [3]?


[1] https://ci.debian.net/packages/o/openmpi/testing/amd64/
[2] https://sources.debian.org/src/pmix/4.0.0%7Erc1-2/debian/control/#L35
[3] https://sources.debian.org/src/openmpi/4.1.0-3/debian/control/#L101

Bug#979022: Useless in Debian

[David Prévot]

Package: php-dompdf
Severity: serious

[ Reported by a team member to see the package removed from testing ]

php-dompdf was introduced in Debian as part of the ownCloud packaging
effort, but no packages depend on it anymore, so I don’t believe it’s
useful to keep it around.

Unless someone disagree with the above, I intend to ask for removal of
this package soon (so if you read this message years from now, no need
to ask for permission to act on what I’ve failed to…).

Thank you Holger for reminding me that this package is still around!

Regards

David


signature.asc
Description: PGP signature

Bug#972910: lasagne ftbfs with python3.9

[Emmanuel Arias]

Hi, 

seems to be the same issue reported #962938.

Cheers,
eamanu

Processed: bug 972910 is forwarded to https://github.com/Lasagne/Lasagne/issues/923

[Debian Bug Tracking System]

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

> forwarded 972910 https://github.com/Lasagne/Lasagne/issues/923
Bug #972910 [src:lasagne] lasagne ftbfs with python3.9
Set Bug forwarded-to-address to 'https://github.com/Lasagne/Lasagne/issues/923'.
> thanks
Stopping processing here.

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

Bug#976245: marked as done (mugshot: Muhshot fails with AttributeError: 'ElementTree' object has no attribute 'getiterator' in console)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2021 00:37:14 +
with message-id 
and subject line Bug#976245: fixed in mugshot 0.4.3-1
has caused the Debian Bug report #976245,
regarding mugshot: Muhshot fails with AttributeError: 'ElementTree' object has 
no attribute 'getiterator' in console
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.)


-- 
976245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mugshot
Version: 0.4.2-1
Severity: important
X-Debbugs-Cc: juoza...@gmail.com

Dear Maintainer,

I'm unable to run mugshot, as it fails with error in console as shown below
It triggers a python3 error when trying to run it, with python 3.9 as default,
window does not open, so I'm unable to edit user information.

Terminal output:
$ mugshot
Traceback (most recent call last):
  File "/usr/bin/mugshot", line 36, in 
mugshot.main()
  File "/usr/lib/python3/dist-packages/mugshot/__init__.py", line 47, in main
window = MugshotWindow.MugshotWindow()
  File "/usr/lib/python3/dist-packages/mugshot_lib/Window.py", line 51, in
__new__
builder = get_builder('MugshotWindow')
  File "/usr/lib/python3/dist-packages/mugshot_lib/helpers.py", line 43, in
get_builder
builder.add_from_file(ui_filename)
  File "/usr/lib/python3/dist-packages/mugshot_lib/Builder.py", line 92, in
add_from_file
ele_widgets = tree.getiterator("object")
AttributeError: 'ElementTree' object has no attribute 'getiterator'



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mugshot depends on:
ii  accountsservice  0.6.55-3
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-8
ii  gir1.2-glib-2.0  1.66.1-1+b1
ii  gir1.2-gst-plugins-base-1.0  1.18.1-1
ii  gir1.2-gstreamer-1.0 1.18.1-1
ii  gir1.2-gtk-3.0   3.24.23-3
ii  python3  3.9.0-3
ii  python3-cairo1.16.2-4+b1
ii  python3-dbus 1.2.16-4
ii  python3-gi   3.38.0-1+b1
ii  python3-pexpect  4.6.0-4

Versions of packages mugshot recommends:
pn  gir1.2-cheese-3.0  
pn  gir1.2-gtkclutter-1.0  
pn  gstreamer1.0-tools 

Versions of packages mugshot suggests:
pn  gstreamer1.0-plugins-good  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mugshot
Source-Version: 0.4.3-1
Done: Sean Davis 

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

Debian distribution maintenance software
pp.
Sean Davis  (supplier of updated mugshot 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: SHA384

Format: 1.8
Date: Fri, 01 Jan 2021 16:06:20 -0800
Source: mugshot
Architecture: source
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sean Davis 
Closes: 976245
Changes:
 mugshot (0.4.3-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Sean Davis ]
   * New upstream version 0.4.3. Closes: #976245
   * d/control:
 - Update standards version to 4.5.1, no changes needed.
 - Remove python3-d

Bug#975201: marked as done (glob2: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 127)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2021 00:34:17 +
with message-id 
and subject line Bug#975201: fixed in glob2 0.9.4.4-5
has caused the Debian Bug report #975201,
regarding glob2: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 127
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> scons -c --portaudio=true 
> INSTALLDIR=/<>/debian/tmp/usr/share/games/ 
> BINDIR=/<>/debian/tmp/usr/games/ LINKFLAGS="-Wl,-z,relro 
> -Wl,-z,now" CXXFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security"
> scons: Reading SConscript files ...
> Checking for C library SDL... yes
> Checking for C library SDL_ttf... yes
> Checking for C library SDL_image... yes
> Checking for C library SDL_net... yes
> Checking for C library speex... yes
> Checking for C++ header file speex/speex.h... yes
> Checking for C library vorbisfile... yes
> Checking for C library vorbis... yes
> Checking for C library ogg... yes
> Checking for C++ header file zlib.h... yes
> Checking for C library z... yes
> Checking for C library boost_thread... yes
> Checking for C++ header file boost/thread/thread.hpp... yes
> Checking for C library boost_system... yes
> Checking for C++ header file boost/thread/thread.hpp... yes
> Checking for C library boost_date_time... yes
> Checking for C++ header file boost/date_time/posix_time/posix_time.hpp... yes
> Checking for C++ header file boost/shared_ptr.hpp... yes
> Checking for C++ header file boost/tuple/tuple.hpp... yes
> Checking for C++ header file boost/tuple/tuple_comparison.hpp... yes
> Checking for C++ header file boost/logic/tribool.hpp... yes
> Checking for C++ header file boost/lexical_cast.hpp... yes
> Checking for C library GL... yes
> Checking for C++ header file GL/gl.h... yes
> Checking for C library GLU... yes
> Checking for C++ header file GL/glu.h... yes
> Checking for C library fribidi... yes
> Checking for C++ header file fribidi/fribidi.h... yes
> Checking for C library portaudio... yes
> Checking for C++ header file portaudio.h... yes
> trying to use portaudio
> scons: done reading SConscript files.
> scons: Cleaning targets ...
> scons: done cleaning targets.
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building glob2 using existing ./glob2_0.9.4.4.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file 
> scons/addDependentLibsToBundle.pyc, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file scons/bundle.pyc, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file scons/nsis.pyc, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file scons/dmg.pyc, use 
> --include-removal to override
> dpkg-source: error: cannot represent change to 
> .sconf_temp/conftest_0e2cf318598b0769703de4f1cd96f098_0_99ba51cfb5cf044aa7652c73e7cd6ec4.o:
>  binary file contents changed
> dpkg-source: error: add 
> .sconf_temp/conftest_0e2cf318598b0769703de4f1cd96f098_0_99ba51cfb5cf044aa7652c73e7cd6ec4.o
>  in debian/source/include-binaries if you want to store the modified binary 
> in the debian tarball
> dpkg-source: error: cannot represent change to 
> .sconf_temp/conftest_247ab27d10a5fca6f4156e32d6cbb51a_0_0ac7732ca0e9ce31158c273311c9af2a.o:
>  binary file contents changed
> dpkg-source: error: add 
> .sconf_temp/conftest_247ab27d10a5fca6f4156e32d6cbb51a_0_0ac7732ca0e9ce31158c273311c9af2a.o
>  in debian/source/include-binaries if you want to store the modified binary 
> in the debian tarball
> dpkg-source: error: cannot represent change to 
> .sconf_temp/conftest_3569c8cde2441444535b9df40b23c180_0_3b1f13edae7faa0f01e798d7d72808ae.o:
>  binary file contents changed
> dpkg-source: error: add 
> .sconf_temp/conftest_3569c8cde2441444535b9df40b23c180_0_3b1f13edae7faa0f01e798d7d72808ae.o
>  in debian/source/include-binaries if you want to store the modified binary 
> in the debian tarball
> dpkg-source: error: cannot represent ch

Processed: affects 977230

[Debian Bug Tracking System]

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

> affects 977230 src:bagel
Bug #977230 [libboost-serialization1.74-dev] bagel FTBFS with Boost 1.74
Added indication that 977230 affects src:bagel
> thanks
Stopping processing here.

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

Bug#978370: marked as done (lgeneral: FTBFS: configure:5729: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2021 00:20:32 +
with message-id 
and subject line Bug#978370: fixed in lgeneral 1.4.3-2
has caused the Debian Bug report #978370,
regarding lgeneral: FTBFS: configure:5729: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:6: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
> ../../lib/autoconf/general.m4:1844: AC_CANONICAL_TARGET is expanded from...
> configure.in:6: the top level
> configure.in:41: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:41: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:6: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
> ../../lib/autoconf/general.m4:1844: AC_CANONICAL_TARGET is expanded from...
> configure.in:6: the top level
> configure.in:41: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:41: the top level
> autoreconf: configure.in: AM_GNU_GETTEXT is used, but not 
> AM_GNU_GETTEXT_VERSION
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:6: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
> ../../lib/autoconf/general.m4:1844: AC_CANONICAL_TARGET is expanded from...
> configure.in:6: the top level
> configure.in:41: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:41: the top level
> configure:5729: error: possibly undefined macro: AM_INTL_SUBDIR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:8: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/lgeneral_1.4.3-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!

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lgeneral package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 23:09:24 +0100
Source: lgeneral
Architecture: source
Version: 1.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 978370
Changes:
 lgeneral (1.4.3-2) unstable; urgency=medium
 .

Bug#971093: marked as done (lazr.config: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2021 00:20:25 +
with message-id 
and subject line Bug#971093: fixed in lazr.config 2.2.2-1
has caused the Debian Bug report #971093,
regarding lazr.config: FTBFS: dh_auto_test: error: pybuild --test -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.)


-- 
971093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lazr.config
Version: 2.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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,sphinxdoc --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr
> copying src/lazr/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr
> creating /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config
> copying src/lazr/config/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config
> copying src/lazr/config/interfaces.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config
> copying src/lazr/config/_config.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config
> creating 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests
> copying src/lazr/config/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests
> copying src/lazr/config/tests/test_config.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests
> creating 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> copying src/lazr/config/docs/usage_fixture.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> copying src/lazr/config/docs/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> copying src/lazr/config/docs/fixture.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> creating 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> running egg_info
> writing src/lazr.config.egg-info/PKG-INFO
> writing dependency_links to src/lazr.config.egg-info/dependency_links.txt
> writing namespace_packages to src/lazr.config.egg-info/namespace_packages.txt
> writing requirements to src/lazr.config.egg-info/requires.txt
> writing top-level names to src/lazr.config.egg-info/top_level.txt
> reading manifest file 'src/lazr.config.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching '.bzrignore'
> writing manifest file 'src/lazr.config.egg-info/SOURCES.txt'
> copying src/lazr/config/version.txt -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config
> copying src/lazr/config/docs/NEWS.rst -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> copying src/lazr/config/docs/usage.rst -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/docs
> copying src/lazr/config/tests/testdata/bad-invalid-name-chars.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/bad-invalid-name.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/bad-nonascii.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/bad-redefined-key.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/bad-redefined-section.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/config/tests/testdata/bad-sectionless.conf -> 
> /<>/.pybuild/cpython3_3.8_lazr.config/build/lazr/config/tests/testdata
> copying src/lazr/confi

Processed: Bug#976245 marked as pending in mugshot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976245 [mugshot] mugshot: Muhshot fails with AttributeError: 'ElementTree' 
object has no attribute 'getiterator' in console
Added tag(s) pending.

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

Bug#976245: marked as pending in mugshot

[Sean Davis]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/mugshot/-/commit/cf25d1cf044a6bf00d3a095c3249264608bf06ed


d/changelog: Closes: #976245


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976245

Bug#975696: marked as done (link-grammar: multi-thread test fails)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2021 00:05:41 +
with message-id 
and subject line Bug#975696: fixed in link-grammar 5.8.0-6
has caused the Debian Bug report #975696,
regarding link-grammar: multi-thread test fails
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.)


-- 
975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: link-grammar
Version: 5.8.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: pkg-sugar-de...@lists.alioth.debian.org, d...@jones.dk
Control: block 972670 by -1

Hi Abiword and Sugar Maintainers (since link-grammar is orphaned)

The upload of link-grammar 5.8.0-1 intermittently FTBFS on several
architectures, e.g. arm64 [1], armel [2] and ppc64 [3].  The failures
all happen during the multi-thread test with various errors:
double free or corruption (fasttop)
free(): invalid pointer
malloc_consolidate(): invalid chunk size
Segmentation fault
corrupted double-linked list

Giving back the builds eventually works, and link-grammar is currently
built on all release architectures.  However, this same test is run
during the autopkgtest and for some reason always fails on armhf [4].
This prevents the migration of link-grammar 5.8.0-1 to testing, and
will eventually cause the autoremoval of abiword and sugar from
testing.

Would you please have a look?

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=arm64&ver=5.8.0-1%2Bb1&stamp=1606121733&raw=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=armel&ver=5.8.0-1%2Bb1&stamp=1605753701&raw=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=ppc64&ver=5.8.0-1%2Bb1&stamp=1606118399&raw=0
[4] https://ci.debian.net/packages/l/link-grammar/testing/armhf/
--- End Message ---
--- Begin Message ---
Source: link-grammar
Source-Version: 5.8.0-6
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated link-grammar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2021 00:30:14 +0100
Source: link-grammar
Architecture: source
Version: 5.8.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jonas Smedegaard 
Closes: 975696
Changes:
 link-grammar (5.8.0-6) unstable; urgency=medium
 .
   * QA upload.
 .
   * drop unsuccessful patch 1001
   * add patches cherry-picked upstream
 to fix multi-thread test failure;
 closes: bug#975696
Checksums-Sha1:
 72c90dcf24a90189dfd388d1e12dca5f25fc9aba 3060 link-grammar_5.8.0-6.dsc
 5a238034d78df865bce7c9cdb95ecd15d4027df4 26160 
link-grammar_5.8.0-6.debian.tar.xz
 e998a5663427b5d7f8be6957c5ff747bbbe0bf16 13219 
link-grammar_5.8.0-6_amd64.buildinfo
Checksums-Sha256:
 0acad725052626cd350ee8761e9f4574a34e7300b985afc687189eda2d20451f 3060 
link-grammar_5.8.0-6.dsc
 d08abc301871dab5127862c757de26c4134a61c65824e407dece205f38145eed 26160 
link-grammar_5.8.0-6.debian.tar.xz
 e628b0ddeac6b325cc4ac109eedda5a9ff568dc14e812e0c6f408c8863eabd66 13219 
link-grammar_5.8.0-6_amd64.buildinfo
Files:
 4c50d176c4b65f39e0794d72e79e528e 3060 text optional link-grammar_5.8.0-6.dsc
 2f34b39300cb6919d02b61a1c639e8e1 26160 text optional 
link-grammar_5.8.0-6.debian.tar.xz
 24db71b46da257e93635503f5ae4260c 13219 text optional 
link-grammar_5.8.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/vtxAACgkQLHwxRsGg
ASEQqA//XTPFFb7PAVxLvz843mQda04O52oWxa2l1wC+mr51X/+MbVlspc9aM7lg
IryeU7IPUTtf+884+V/rQJqmSyWCIVEHKriaZBXEDkdzp9zA4cZn8E/kufjTUZ1h
mT0kGZKEq2ul5P5uJGH4O0PKJUpM1yM0kvjDJ4XG2saumj0He1d7UZk/sg1hL1/y
d2g+VzULBWffXaFmuWXVJamMrkyWVuVVY3yWjiJmf5T3kXLUcDL7Ec7LxBrzoWGm
y2ApWd9NwdGSMch1+I+ZaZw07n6FcG+cq7ywJz6OMfyYgl9suvncE+3h58XnYkE/
Fm6R8L+4FhBxGccntlBI5dHSXpyMwBmRCqJk4YloSNQDkcjzxCMC0jP9HvMCeYGT
VO4803L52P0feiAyTSdsDvvYGa0Lip0u/BlMTrHphxHuLOlYe0Wmy3yEPTkqnVnw
FnrB890B8zYoYFiY4OS9KGI6QguMsEqYtNFhhCmrv3f2fQfj0J73EKe1t64Ux/jy

Processed: severity of 978448 is serious

[Debian Bug Tracking System]

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

> severity 978448 serious
Bug #978448 [libaudit-dev] Static linking fails with undefined reference to 
`audit_strsplit_r'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#977230: bagel FTBFS with Boost 1.74

[Debian Bug Tracking System]

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

> reassign 977230 libboost-serialization1.74-dev
Bug #977230 [src:bagel] bagel FTBFS with Boost 1.74
Bug reassigned from package 'src:bagel' to 'libboost-serialization1.74-dev'.
No longer marked as found in versions bagel/1.2.2-1.
Ignoring request to alter fixed versions of bug #977230 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#977230: bagel FTBFS with Boost 1.74

[Michael Banck]

reassign 977230 libboost-serialization1.74-dev
thanks

On Fri, Jan 01, 2021 at 06:58:24PM +0200, Adrian Bunk wrote:
> On Fri, Jan 01, 2021 at 01:07:25PM +0100, Michael Banck wrote:
> > I tried to look at it, but it's unclear to me where BAGEL is being at
> > fault, it seems to just include boost headers and then there's error in
> > one of them? Should it do something different?
> 
> This might be a bug in boost?
> https://github.com/boostorg/property_tree/pull/62

Oh thanks - I didn't find much when searching.

I'm reassigning it to boost then for now.


Michael

Bug#979012: minetest-data: debian/copyright needs updating

[Norman Rasmussen]

Package: minetest-data
Version: 0.4.15+repack-1
Severity: serious
Justification: Policy 12.5

Dear Maintainer,

minetest-data 0.4.15 cleaned up usage of the WTFPL license, but
debian/copyright still references it. It looks like the MIT license was
chosen to replace the existing license, but it was not added to
debian/copyright when 0.4.15 was released. I assume that these were just
unintentional omissions and should be easy to resolve.

Additionally the upstream source is incomplete:
 - games/minetest_game/* files can be found at
   https://github.com/minetest/minetest_game
 - games/minetest_game/mods/$name/* files can be found at
   https://github.com/minetest-game-mods/$name

Thanks!
Norman

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages minetest-data depends on:
pn  fonts-croscore
pn  fonts-droid-fallback  

minetest-data recommends no packages.

minetest-data suggests no packages.

Bug#948645: marked as done (pesign FTBFS: nss-induced error: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘496’ to ‘240’ [-Werror=overflow])

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 23:04:02 +
with message-id 
and subject line Bug#948645: fixed in pesign 0.112-6
has caused the Debian Bug report #948645,
regarding pesign FTBFS: nss-induced error: unsigned conversion from ‘int’ to 
‘unsigned char’ changes value from ‘496’ to ‘240’ [-Werror=overflow]
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.)


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

pesign fails to build from source in unstable:

| /usr/bin/gcc -g -O2 -ffile-prefix-map=/build/1st/pesign-0.112=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/build/1st/pesign-0.112/include -I/usr/include/efivar -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/uuid -Werror -Wdate-time -D_FORTIFY_SOURCE=2 
-c -o efikeygen.o efikeygen.c
| In file included from /usr/include/nss/cert.h:22,
|  from efikeygen.c:39:
| efikeygen.c: In function 'add_cert_type':
| /usr/include/nss/certt.h:460:5: error: unsigned conversion from 'int' to 
'unsigned char' changes value from '496' to '240' [-Werror=overflow]
|   460 | (NS_CERT_TYPE_SSL_CLIENT | NS_CERT_TYPE_SSL_SERVER | 
NS_CERT_TYPE_EMAIL | \
|   | ^
| efikeygen.c:208:23: note: in expansion of macro 'NS_CERT_TYPE_APP'
|   208 |  unsigned char type = NS_CERT_TYPE_APP;
|   |   ^~~~
| cc1: all warnings being treated as errors
| make[2]: *** [/build/1st/pesign-0.112/Make.rules:33: efikeygen.o] Error 1
| make[2]: Leaving directory '/build/1st/pesign-0.112/src'
| make[1]: *** [Makefile:25: all] Error 2
| make[1]: Leaving directory '/build/1st/pesign-0.112'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:15: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Observed by crossqa:
http://crossqa.subdivi.de/build/pesign_0.112-5_arm64_20200111051741.log
Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pesign_0.112-5.rbuild.log.gz

Very likely, this failure is due to a change in nss. I've Cced the
mozilla team.

Helmut
--- End Message ---
--- Begin Message ---
Source: pesign
Source-Version: 0.112-6
Done: Steve McIntyre <93...@debian.org>

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

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

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated pesign package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jan 2021 22:34:53 +
Source: pesign
Architecture: source
Version: 0.112-6
Distribution: unstable
Urgency: medium
Maintainer: Debian UEFI maintainers 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 948645
Changes:
 pesign (0.112-6) unstable; urgency=medium
 .
   * Fix FTBFS with new versions of NSS, using patch from
 upstream. Thanks to Dan Nicholson. Closes: #948645
   * Update Standards-Version to 4.5.1
   * Update debhelper compat to 10
Checksums-Sha1:
 b9af1edefc96288426ddce63cef42f8a06c742dc 2168 pesign_0.112-6.dsc
 c568e36e7f7843be67fa6fd7723becf1f0aa349a 12160 pesign_0.112-6.debian.tar.xz
 28a46d676800737d45e5718c2196c32ea6ee9dca 6090 pesign_0.112-6_source.buildinfo
Checksums-Sha256:
 11bdaa53e73cd8d0b80f38f003e33c1ae0060a2853d9138f1a85640377a8fe27 2168 
pesign_0.112-6.dsc
 e4003e54db898cd10e768dae8330fa8922055e553d8f55b8ce45bfe8a6cc400b 12160 
pesign_0.112-6.debian.tar.xz
 8158187993102a4a5e08baddf86f5bf6436966f95be58fe23494af6ad353905d 6090 
pesign_0.112-6_source.buildinfo
Files:
 130b59e728d033e96a64f9cb4c3220ab 2168 devel optional pesign_0.112-6.dsc
 a0c5a9269a194a8b0d2532516f6c79c9 12160 devel optional 
pesign_0.112-6.debian.tar.xz
 d35bd40675ca327db7c890309351a439 6090 devel 

Bug#976836: libgnutls30: 3.7.0-3 fails to connect on debian.ethz.ch

[Petter Reinholdtsen]

Is there any hope to have a fix for this in unstable soon?  The
issue block ring and opendht from migrating to testing.

Is this really a RC issue?  I can use https to deb.debian.org and
some other https mirrors, so the problem seem to trigger only on
selected mirror sites.  Anyone know of a site currently failing, after
the debian.ethz.ch one was fixed?
fixed.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: Bug#979010: libqalculate20: crashes cantor due to symbol conflict with poppler

[Debian Bug Tracking System]

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

> severity 979010 serious
Bug #979010 [libqalculate20] libqalculate20: crashes cantor due to symbol 
conflict with poppler
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#978381: marked as done (google-recaptcha: FTBFS: TypeError: Argument 2 passed to PHPUnit\Framework\Assert::assertContains() must be iterable, string given, called in /<>/tests/ReCaptc

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 22:19:15 +
with message-id 
and subject line Bug#978381: fixed in google-recaptcha 1.2.4-2
has caused the Debian Bug report #978381,
regarding google-recaptcha: FTBFS: TypeError: Argument 2 passed to 
PHPUnit\Framework\Assert::assertContains() must be iterable, string given, 
called in /<>/tests/ReCaptcha/RequestMethod/PostTest.php on line 
118
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # keep in sync with debian/tests/phpunit
> find tests/ -type f -print0 | xargs -0 sed -i 's/function setUp()/function 
> setUp(): void/g'
> find tests/ -type f -print0 | xargs -0 sed -i 's/function tearDown()/function 
> tearDown(): void/g'
> phpunit --no-coverage
> PHPUnit 9.5.0 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 7.4.11
> Configuration: /<>/phpunit.xml.dist
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> E.E   51 / 51 
> (100%)
> 
> Time: 00:00.012, Memory: 6.00 MB
> 
> There were 6 errors:
> 
> 1) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data set 
> #0 ('')
> RuntimeException: No secret provided
> 
> /<>/src/ReCaptcha/ReCaptcha.php:136
> /<>/tests/ReCaptcha/ReCaptchaTest.php:48
> 
> 2) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data set 
> #1 (null)
> RuntimeException: No secret provided
> 
> /<>/src/ReCaptcha/ReCaptcha.php:136
> /<>/tests/ReCaptcha/ReCaptchaTest.php:48
> 
> 3) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data set 
> #2 (0)
> RuntimeException: No secret provided
> 
> /<>/src/ReCaptcha/ReCaptcha.php:136
> /<>/tests/ReCaptcha/ReCaptchaTest.php:48
> 
> 4) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data set 
> #3 (stdClass Object ())
> RuntimeException: The provided secret must be a string
> 
> /<>/src/ReCaptcha/ReCaptcha.php:140
> /<>/tests/ReCaptcha/ReCaptchaTest.php:48
> 
> 5) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data set 
> #4 (array())
> RuntimeException: No secret provided
> 
> /<>/src/ReCaptcha/ReCaptcha.php:136
> /<>/tests/ReCaptcha/ReCaptchaTest.php:48
> 
> 6) ReCaptcha\RequestMethod\PostTest::testHTTPContextOptions
> TypeError: Argument 2 passed to PHPUnit\Framework\Assert::assertContains() 
> must be iterable, string given, called in 
> /<>/tests/ReCaptcha/RequestMethod/PostTest.php on line 118
> 
> /<>/tests/ReCaptcha/RequestMethod/PostTest.php:118
> /<>/tests/ReCaptcha/RequestMethod/PostTest.php:145
> /<>/src/ReCaptcha/RequestMethod/Post.php:80
> /<>/tests/ReCaptcha/RequestMethod/PostTest.php:61
> 
> ERRORS!
> Tests: 51, Assertions: 139, Errors: 6.
> make[1]: *** [debian/rules:11: override_dh_auto_test] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/google-recaptcha_1.2.4-1_unstable.log

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

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

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: google-recaptcha
Source-Version: 1.2.4-2
Done: William Desportes 

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

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

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

De

Bug#972006: marked as done (pycompyle ftbfs with python3.9 (test failures))

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 22:18:28 +
with message-id 
and subject line Bug#972006: fixed in compyle 0.7-2
has caused the Debian Bug report #972006,
regarding pycompyle ftbfs with python3.9 (test failures)
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.)


-- 
972006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycompyle
Version: 0.7-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

pycompyle ftbfs with python3.9 (test failures), the failures are the same for
0.7 as seen in this test rebuild:

https://launchpadlibrarian.net/501583226/buildlog_ubuntu-groovy-amd64.compyle_0.6-1build1_BUILDING.txt.gz

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 34 failed, 214 passed, 43 skipped, 4 deselected, 127 warnings in 153.58 
seconds =
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/packages/tmp/compyle-0.7/.pybuild/cpython3_3.9_compyle/build; python3.9 -m
pytest --ignore=compyle/tests/test_cuda.py -k "not
test_that_multiple_compiles_do_not_occur_for_same_source and not
test_align_multiple"
--- End Message ---
--- Begin Message ---
Source: compyle
Source-Version: 0.7-2
Done: Antonio Valentino 

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

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

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated compyle 
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, 24 Dec 2020 16:21:31 +
Source: compyle
Architecture: source
Version: 0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Antonio Valentino 
Closes: 972006
Changes:
 compyle (0.7-2) unstable; urgency=medium
 .
   * Standards-Version bumped to v4.5.1 (no change).
   * debian/patched:
 - new 0002-Python-3.9.patch to fix compatibility with Puthon 3.9 (ast).
   Closes: #972006.
 - new 0003-Fix-32bit.patch to fix tests on 32bit architectures.
Checksums-Sha1:
 91d5c255c1d180b922a49728777c50bd880bef71 2100 compyle_0.7-2.dsc
 d38b6588defdadf03a5e9edd6e220a9a382d0291 6324 compyle_0.7-2.debian.tar.xz
 fc32fa88280fafcdbc6d2b5380f9477e58d855f7 7663 compyle_0.7-2_source.buildinfo
Checksums-Sha256:
 71f757b100ed8ca8f63cb4d7f2610c587831905ddbdf4eeec086db135caac992 2100 
compyle_0.7-2.dsc
 a6a02b1006f89ad149e181d7e09300c4d8a2cc3f200404708a2374093e038fe4 6324 
compyle_0.7-2.debian.tar.xz
 f605fab9beb2af325ee2f5655afe87ac0daedcb5660d82313d620906d770839b 7663 
compyle_0.7-2_source.buildinfo
Files:
 dcfd73316fb4fdcb3506657fb2600b5b 2100 python optional compyle_0.7-2.dsc
 bc8535cc357ed7b3f80e9915f55072de 6324 python optional 
compyle_0.7-2.debian.tar.xz
 7f4c201adefabc20ed86123a7368c24a 7663 python optional 
compyle_0.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/vnEQACgkQ0+Fzg8+n
/wYPthAAlwRQ7L1xFXC/sVSgTv8Yd4hZT0pem0WN3NcFYUo4/+qpTb4PTs/fMJEv
dHv0g94zXR3izEvyu63a5rqrj/kmAEfpsJDoGPEaL6QJzy/YC+wV5o8WPG2sMzLq
nmVeqJiFgZMm1Z6P7QtXJpgIAmPY8xEeOSb1i4s4iACwdZn2PCzmOBx+Y+PjcDxx
SYG4k3kMAVwSh29DPanY55p9U1uFg1azwE1XY1EVdvA+pWogvHjBrJcdksDHgRF7
gm8Ci0IH7MZa84lhR5bB1WfjDrnESqr5vnjG0MJXdfSUZVydWWJCW0eDFjrZWgOa
4ScfkaJU5K05f2R/J/os1iaFTyAc8M/LirtHG5v8Ug2JW7/Tnzf8OgodhS+tq0IJ
qSr6r3yGeMOpdYJfSVeKezvn2sJe3JnaNvumr/Y6lEFsKr9kvBOlsdAw5QWIlpYW
qK/QG0l/AssqlnoVMUN1nUJI2bJA9u9zSQEznpjiSv9ghpdmDWSSfwW7Acq9OZw4
b28wXBuih14y8fMmvEidB9NwFI3B7aMajIdwIt/87e8m9ogSDTvAH1d6ktpudmJZ
dV7Ua3G0jGvfCyAxuWsfIputoh+kakGPCeVMCkrsUNK43zHImeQlxQdLxKYRlIST
bvPfmntmxvALJEqaEwOFQjVw4kfJeu13BIAHy0ksWdb9rQmxZ7I=
=hY3q
-END PGP SIGNATURE End Message ---

Bug#970066: marked as done (atftp: CVE-2020-6097)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 21:03:20 +
with message-id 
and subject line Bug#970066: fixed in atftp 0.7.git20120829-3.2
has caused the Debian Bug report #970066,
regarding atftp: CVE-2020-6097
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.)


-- 
970066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atftp
Version: 0.7.git20120829-3.1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for atftp.

CVE-2020-6097[0]:
| An exploitable denial of service vulnerability exists in the atftpd
| daemon functionality of atftp 0.7.git20120829-3.1+b1. A specially
| crafted sequence of RRQ-Multicast requests trigger an assert() call
| resulting in denial-of-service. An attacker can send a sequence of
| malicious packets to trigger this vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-6097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6097
[1] https://talosintelligence.com/vulnerability_reports/TALOS-2020-1029

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: atftp
Source-Version: 0.7.git20120829-3.2
Done: Salvatore Bonaccorso 

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated atftp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Dec 2020 21:28:40 +0100
Source: atftp
Architecture: source
Version: 0.7.git20120829-3.2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Salvatore Bonaccorso 
Closes: 970066
Changes:
 atftp (0.7.git20120829-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix for DoS issue CVE-2020-6097 (Closes: #970066)
Checksums-Sha1: 
 5e9dc11e0cb90da13b3dcf58b63b3743c7a34a2e 1955 atftp_0.7.git20120829-3.2.dsc
 f394a7342acf5904e9882d119560e2c7e0c94dde 37840 
atftp_0.7.git20120829-3.2.diff.gz
Checksums-Sha256: 
 42457b62d8e9279d0ca119e33fb7f665fe37b407b3bcd4d3d997c46781f596e4 1955 
atftp_0.7.git20120829-3.2.dsc
 0971c5f6eb65d01609f48aa89909e42aee252f342dcffcf77976cadbcbbbe84b 37840 
atftp_0.7.git20120829-3.2.diff.gz
Files: 
 0cf0a9000702deebb4480845a21d7a22 1955 net extra atftp_0.7.git20120829-3.2.dsc
 d91412c62f86eeaa4a7b378a1347952c 37840 net extra 
atftp_0.7.git20120829-3.2.diff.gz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl/o8ANfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89Eq9MQAI50FNXDh5qDKy2OHrUs/0y9kKpSbVMa
QwS1EII7EKpJOPowUwREOrLP6io270WRnEjWDIQq+YIrxtgQZ/5NJSCjMchOuS+A
QzxUoDz2tx+ve6SpJwrahQcaIZNLZYYXqE94Q4jBmeWaKWQXoxyHt//Dfu5GLra0
UmjV5nZVgfSfUMRkFE6MAIKZE9eAbVqA8X853NBlrpEaxQyWbTFQCiBo/T5QltMX
9OTMlD9uocSjy6lTXJErxEEK3skNb/wsEugYiq9h6lVZofjKzBTt1/g4+8GtC7LP
IlXXLxb+y41+1yyyT9xvIggweZeZQWC64JsQfAubZRAAGlJ9HR7rVPMhbAVZgbnM
rA1NR9gi5vqe5Vv4dtsxZpG9N7E3V/CJVErDFdkYhCGPfoKjs9OX3IK+W1BwyWbU
U1DDQbOZQSfwjWj3L2yUugF0Jqa40dAOp7xc287B5FJLhDU4r6wouYRql88J0Oqu
Lxhis31Fnqn/K8iIwA2RunBCu11FFAATEvZg1XZbek+kY7bjU/U2k+PNGeXTDQ5V
xq5RL23do0v9300FhKr4P+sCyeMv+g/LCkCUjw2SyNbcSgnBopyl3wM6vwiWkOe2
5oHJ5MWhkz1GgwaVPWed71/seShHiQmoc1CcUPb8TbPp7LL1FU7ImK1LqR/3ecKR
bF6/W9GKiSSl
=HpKI
-END PGP SIGNATURE End Message ---

Bug#979002: rust-libm: autopkgtest failure on i386: 1.10009765625 is not equal to 2.0

[Paul Gevers]

Source: rust-libm
Version: 0.2.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package rust-libm, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can you please investigate the situation and fix it?

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

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=rust-libm

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-libm/8255835/log.gz

failures:

 math::ceil::tests::sanity_check stdout 
thread 'math::ceil::tests::sanity_check' panicked at 'assertion failed:
`(left == right)`
  left: `1.10009765625`,
 right: `2.0`', src/math/ceil.rs:50:9
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: libm::math::ceil::tests::sanity_check
 at ./src/math/ceil.rs:50
   3: libm::math::ceil::tests::sanity_check::{{closure}}
 at ./src/math/ceil.rs:49
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.47.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.

 math::floor::tests::sanity_check stdout 
thread 'math::floor::tests::sanity_check' panicked at 'assertion failed:
`(left == right)`
  left: `0.10009765625`,
 right: `1.0`', src/math/floor.rs:49:9
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: libm::math::floor::tests::sanity_check
 at ./src/math/floor.rs:49
   3: libm::math::floor::tests::sanity_check::{{closure}}
 at ./src/math/floor.rs:48
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.47.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.

 math::j1f::tests::test_y1f_2002 stdout 
thread 'math::j1f::tests::test_y1f_2002' panicked at 'assertion failed:
`(left == right)`
  left: `-0.10703231`,
 right: `-0.10703229`', src/math/j1f.rs:370:9
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: libm::math::j1f::tests::test_y1f_2002
 at ./src/math/j1f.rs:370
   3: libm::math::j1f::tests::test_y1f_2002::{{closure}}
 at ./src/math/j1f.rs:369
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.47.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.

 math::sincosf::tests::rotational_symmetry stdout 
thread 'math::sincosf::tests::rotational_symmetry' panicked at
'assertion failed: (s - s_plus).abs() < TOLERANCE',
src/math/sincosf.rs:148:13
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: libm::math::sincosf::tests::rotational_symmetry
 at ./src/math/sincosf.rs:148
   4: libm::math::sincosf::tests::rotational_symmetry::{{closure}}
 at ./src/math/sincosf.rs:138
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.47.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.


failures:
math::ceil::tests::sanity_check
math::floor::tests::sanity_check
math::j1f::tests::test_y1f_2002
math::sincosf::tests::rotational_symmetry

test result: FAILED. 42 passed; 4 failed; 0 ignored; 0 measured; 0
filtered out




OpenPGP_signature
Description: OpenPGP digital signature

Processed: retitle eds vs libphonenumber-dev boost deps FTBFS

[Debian Bug Tracking System]

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

> retitle 978172 evolution-data-server: FTBFS: libphonenumber-dev no longer 
> depends on libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
Bug #978172 [src:evolution-data-server] evolution-data-server: FTBFS: 
CheckFunctionExists.c:17: undefined reference to `res_query'
Changed Bug title to 'evolution-data-server: FTBFS: libphonenumber-dev no 
longer depends on libboost-dev as needed when defining 
I18N_PHONENUMBERS_USE_BOOST' from 'evolution-data-server: FTBFS: 
CheckFunctionExists.c:17: undefined reference to `res_query''.
> thanks
Stopping processing here.

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

Bug#978172: evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query'

[Andreas Henriksson]

Hello,

Seems like intentional(?) changes in libphonennumber caused this.

Adding recipient Matthias Klose, who uploaded the latest libphonenumber
version, to hopefully get a comment on if this is something than should
get fixed in libphonenumber or in e-d-s.

Please note that the libphonenumber Vcs-Git repo seems outdated so it's
not possible to track down exact commit which changed debian/control and
get more details!

On Sat, Dec 26, 2020 at 10:12:40PM +0100, Lucas Nussbaum wrote:
> Source: evolution-data-server
> Version: 3.38.2-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201226 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > /usr/bin/ld: CMakeFiles/cmTC_9ba60.dir/CheckFunctionExists.c.o: in function 
> > `main':
> > /usr/share/cmake-3.18/Modules/CheckFunctionExists.c:17: undefined reference 
> > to `res_query'
> > collect2: error: ld returned 1 exit status

Nope, this is a wild goose 

> 
> The full build log is available from:
>
> http://qa-logs.debian.net/2020/12/26/evolution-data-server_3.38.2-2_unstable.log
[...]


Hopefully actually relevant part (because I have to say finding the
actual error from CMake builds is horrible!):

```
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_24d88.dir/src.cxx.o
/usr/bin/c++ -DI18N_PHONENUMBERS_USE_BOOST  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-Dphone_number_with_boost_thread-mt -fPIE -o 
CMakeFiles/cmTC_24d88.dir/src.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
: warning: ISO C++11 requires whitespace after the macro name
In file included from /usr/include/phonenumbers/phonenumberutil.h:32,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1:
/usr/include/phonenumbers/base/memory/scoped_ptr.h:10:10: fatal error: 
boost/scoped_ptr.hpp: No such file or directory
   10 | #include 
  |  ^~
compilation terminated.
gmake[3]: *** [CMakeFiles/cmTC_24d88.dir/build.make:85: 
CMakeFiles/cmTC_24d88.dir/src.cxx.o] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
gmake[2]: *** [Makefile:140: cmTC_24d88/fast] Error 2
```

So this looks like a bug in libphonenumber to me Interestingly
this is part of libphonenumber 7.1.0-7 changelog:
 * Don't build using boost, not required on recent Linux versions.

... and in /usr/include/phonenumbers/base/memory/scoped_ptr.h we can
see that the boost header is conditionally included based on
`#if defined(I18N_PHONENUMBERS_USE_BOOST)`.

That define in turn is apparently set by evolution-data-server:
./cmake/modules/FindPhonenumber.cmake:set(PHONENUMBER_DEFINITIONS 
-DI18N_PHONENUMBERS_USE_BOOST CACHE STRING "libphonenumber compile definitions, 
default is -DI18N_PHONENUMBERS_USE_BOOST")

Does that mean evolution-data-server is supposed to open-code the
dependencies needed by libphonenumber on boost ?
I think it would be better if the libphonenumber-dev pulled in
everything needed in every supported configuration (or alternatively
provided 2 separate -dev packages, eg. libphonenumber-boost-dev which
deps on libphonennumber-dev plus required boost parts but that seems
too complex for little gain - not to mention needing to go through NEW).



Regards,
Andreas Henriksson

Processed: Re: Bug#963477: ruby-rack: CVE-2020-8184

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #963477 [src:ruby-rack] ruby-rack: CVE-2020-8184
Severity set to 'grave' from 'important'

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

Processed: found 963477 in 2.0.6-3

[Debian Bug Tracking System]

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

> found 963477 2.0.6-3
Bug #963477 [src:ruby-rack] ruby-rack: CVE-2020-8184
Marked as found in versions ruby-rack/2.0.6-3.
> thanks
Stopping processing here.

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

Bug#978988: marked as done (node-mqtt: autopkgtest regression in testing: Error: Timeout of 2000ms exceeded)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 20:20:11 +
with message-id 
and subject line Bug#978988: fixed in node-mqtt 4.2.6-2
has caused the Debian Bug report #978988,
regarding node-mqtt: autopkgtest regression in testing: Error: Timeout of 
2000ms exceeded
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.)


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

Dear maintainer(s),

With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?

Does your mocha-test connect to the internet by the way? In that case,
please also add a needs-internet restriction.

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

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mqtt/9241724/log.gz

  594 passing (1m)
  4 pending
  4 failing

  1) MqttClient
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  2) MQTT 5.0
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/client_mqtt5.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  3) MqttSecureClient
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/secure_client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  4) Websocket Client
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/websocket_client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)



/usr/share/nodejs/mocha/lib/runner.js:962
throw err;
^

NodeError: write after end
at writeAfterEnd
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:257:12)
at Connection.Writable.write
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:301:21)
at Connection. [as pingresp]
(/usr/share/nodejs/mqtt-connection/connection.js:83:10)
at Connection.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/server_helpers_for_client_tests.js:86:20)
at Connection.emit (events.js:314:20)
at Connection.emitPacket
(/usr/share/nodejs/mqtt-connection/connection.js:10:8)
at Connection.emit (events.js:314:20)
at addChunk
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:297:12)
at readableAddChunk
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:279:11)
at Connection.Readable.push
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:240:10)
at Connection.Duplexify._forward
(/usr/share/nodejs/duplexify/index.js:172:26)
at Transform.onreadable (/usr/share/nodejs/duplexify/index.js:136:10)
at Transform.emit (events.js:314:20)
at emitReadable_
(/usr/share/nodejs/readable-str

Processed: Bug#977979 marked as pending in jruby

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977979 [jruby] jruby fails to run without declaring the 
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable
Added tag(s) pending.

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

Bug#977979: marked as pending in jruby

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/jruby/-/commit/ffd10bfeb38278ee616ecbf22d935671c9679d19


d/patches: delete 0007 and don't add /usr/lib/ruby/vendor_ruby to the jruby 
LOAD_PATH anymore. (Closes: #977979, #977981)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977979

Processed: severity of 977719 is grave

[Debian Bug Tracking System]

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

> severity 977719 grave
Bug #977719 [src:spotweb] spotweb: CVE-2020-35545
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#978988: marked as pending in node-mqtt

[Ying-Chun Liu]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-mqtt/-/commit/8042bc17434c0e7bae1f55074adb720a26830b60


Import Debian changes 4.2.6-2

node-mqtt (4.2.6-2) unstable; urgency=low
.
  * autopkgtest: some tests take longer time than before thus we increase
timeout of mocha (Closes: #978988)

Signed-off-by: Ying-Chun Liu (PaulLiu) 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978988

Processed: Bug#978988 marked as pending in node-mqtt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978988 [src:node-mqtt] node-mqtt: autopkgtest regression in testing: 
Error: Timeout of 2000ms exceeded
Added tag(s) pending.

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

Processed: Re: mailutils: FTBFS on amd64 with current unstable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible moreinfo
Bug #976050 [mailutils] mailutils: FTBFS on amd64 with current unstable 
Added tag(s) moreinfo and unreproducible.

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

Bug#976050: mailutils: FTBFS on amd64 with current unstable

[Andreas Henriksson]

Control: tags -1 + unreproducible moreinfo

Hello,

I'm unable to reproduce your build problems. I've built mailutils
in a loop for a while now and every build succeeds for me.

On Sat, Nov 28, 2020 at 03:11:11PM -0600, Rob Browning wrote:
> 
> Package: mailutils
> Version: 1:3.10-3
> Severity: serious
> 
> After an "apt-get source mailutils/sid" with current unstable,
> "debian/rules binary" fails here like this:
> 
>   Creating popauth.1...
>   /home/vagrant/mailutils/mailutils-3.10/debian/tmp/usr/bin/popauth: error 
> while loading shared libraries: libmu_dbm.so.7: cannot open shared object 
> file: No such file or directory
[...]

Could you please try using `dpkg-buildpackage -uc -us`, rather than
directly invoking debian/rules, and see if it helps you detect any
misconfigurations in your build environment?

Could you please provide a full build log?

Can you think of anything that might be relevant why the build
would fail for you but not me?

Regards,
Andreas Henriksson

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

[Michel Le Bihan]

Hello,

Yes, it won't be updated. If there will be a security issue/vuln, then
probably somebody will write about it and we will do something about
that.

Michel Le Bihan

Le vendredi 01 janvier 2021 à 20:34 +0100, Stephen Kitt a écrit :
> Hi,
> 
> On Fri, 25 Dec 2020 20:50:04 +0100 Michel Le Bihan
>  wrote:
> > With
> > https://salsa.debian.org/mimi8/chromium/-/commit/d21192e70824befdfeed5a5145275139cd6c4ffa
> > the Widevine component won't be downloaded automatically. However,
> > unlike when `enable_widevine=false` is set, Widevine CDM component
> > will
> > still be used when found in `~/.config/chromium/WidevineCdm/`. It
> > is
> > possibly to copy it there, but there is no nice UI to do that.
> > 
> > This resolves the policy issue, while still making it possible to
> > use
> > that component. This change will be available in the next upload.
> 
> Doesn’t this mean though that users who *do* have the CDM component
> installed
> will no longer receive updates to it?
> 
> Regards,
> 
> Stephen

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

[Stephen Kitt]

Hi,

On Fri, 25 Dec 2020 20:50:04 +0100 Michel Le Bihan  wrote:
> With
> https://salsa.debian.org/mimi8/chromium/-/commit/d21192e70824befdfeed5a5145275139cd6c4ffa
> the Widevine component won't be downloaded automatically. However,
> unlike when `enable_widevine=false` is set, Widevine CDM component will
> still be used when found in `~/.config/chromium/WidevineCdm/`. It is
> possibly to copy it there, but there is no nice UI to do that.
> 
> This resolves the policy issue, while still making it possible to use
> that component. This change will be available in the next upload.

Doesn’t this mean though that users who *do* have the CDM component installed
will no longer receive updates to it?

Regards,

Stephen


pgpDwIGuGsQnc.pgp
Description: OpenPGP digital signature

Processed: Re: gimp: FTBFS: dh_install: error: missing files, aborting

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libheif-dev 1.10.0-1
Bug #978176 [src:gimp] gimp: FTBFS: dh_install: error: missing files, aborting
Bug reassigned from package 'src:gimp' to 'libheif-dev'.
No longer marked as found in versions gimp/2.10.22-2.
Ignoring request to alter fixed versions of bug #978176 to the same values 
previously set
Bug #978176 [libheif-dev] gimp: FTBFS: dh_install: error: missing files, 
aborting
Marked as found in versions libheif/1.10.0-1.
> retitle -1 libheif-dev missing dependencies on pkg-config Requires.private 
> listed components
Bug #978176 [libheif-dev] gimp: FTBFS: dh_install: error: missing files, 
aborting
Changed Bug title to 'libheif-dev missing dependencies on pkg-config 
Requires.private listed components' from 'gimp: FTBFS: dh_install: error: 
missing files, aborting'.
> affects -1 gimp
Bug #978176 [libheif-dev] libheif-dev missing dependencies on pkg-config 
Requires.private listed components
Added indication that 978176 affects gimp

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

Bug#978176: gimp: FTBFS: dh_install: error: missing files, aborting

[Andreas Henriksson]

Control: reassign -1 libheif-dev 1.10.0-1
Control: retitle -1 libheif-dev missing dependencies on pkg-config 
Requires.private listed components
Control: affects -1 gimp

Hello,

It seems like the recently uploaded libheif 1.10 is broken causing
problems for gimp (and all other reverse dependencies using
libheif.pc ?!). Thus reassigning, more details below.

On Sat, Dec 26, 2020 at 10:13:50PM +0100, Lucas Nussbaum wrote:
> Source: gimp
> Version: 2.10.22-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201226 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
[...]
> > dh_install: warning: Cannot find (any matches for) 
> > "usr/lib/gimp/2.0/plug-ins/file-heif" (tried in ., debian/tmp)
> > 
> > dh_install: warning: gimp missing files: usr/lib/gimp/2.0/plug-ins/file-heif
> > dh_install: error: missing files, aborting
> > make[1]: *** [debian/rules:44: override_dh_install] Error 25
> 
> The full build log is available from:
>http://qa-logs.debian.net/2020/12/26/gimp_2.10.22-2_unstable.log
[...]


In the full build log it can be seen that no version of libheif
is detected by configure despite the libheif-dev being installed
as part of build-dependencies.

This can be seen in config.log:

```
configure:29056: checking for libheif > 1.5.1
configure:29063: $PKG_CONFIG --exists --print-errors "libheif > 1.5.1"
Package aom was not found in the pkg-config search path.
Perhaps you should add the directory containing `aom.pc'
to the PKG_CONFIG_PATH environment variable
Package 'aom', required by 'libheif', not found
configure:29066: $? = 1
configure:29080: $PKG_CONFIG --exists --print-errors "libheif > 1.5.1"
Package aom was not found in the pkg-config search path.
Perhaps you should add the directory containing `aom.pc'
to the PKG_CONFIG_PATH environment variable
Package 'aom', required by 'libheif', not found
configure:29083: $? = 1
configure:29097: result: no
Package 'aom', required by 'libheif', not found
configure:29116: checking for libheif = 1.4.0
configure:29123: $PKG_CONFIG --exists --print-errors "libheif = 1.4.0"
Package aom was not found in the pkg-config search path.
Perhaps you should add the directory containing `aom.pc'
to the PKG_CONFIG_PATH environment variable
Package 'aom', required by 'libheif', not found
configure:29126: $? = 1
configure:29140: $PKG_CONFIG --exists --print-errors "libheif = 1.4.0"
```

New in libheif 1.10 (currently in unstable) is that the libheif.pc
pkg-config file has:

```
> grep Requires usr/lib/*/pkgconfig/libheif.pc
Requires:
Requires.private:  aom libde265 x265
```

This was not the case in libheif 1.9 (currently in testing).

The pkg-config file is thus broken when installing libheif-dev in
a clean system where the pkg-config files of aom, etc are not installed.

As far as I can tell the fix is:
a/ Add libaom-dev, libde265-dev and libx265-dev to Depends of libheif-dev
b/ preferably also write a simple autopkgtest that checks if libheif.pc
   works as expected
   eg. `pkg-config --exists --print-errors "libheif > 1.5.1"` should
   not error out when libheif-dev is installed.

Regards,
Andreas Henriksson

Processed: Re: Bug#976756 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#976756: fixed in mia 2.4.7-5)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #976756 {Done: Andreas Tille } [src:mia] mia: binary-all 
FTBFS
'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 mia/2.4.7-5.

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

Bug#976756: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#976756: fixed in mia 2.4.7-5)

[Adrian Bunk]

Control: reopen -1

On Fri, Jan 01, 2021 at 06:51:08PM +, Debian Bug Tracking System wrote:
>...
>  mia (2.4.7-5) unstable; urgency=medium
>  .
>* Team upload.
>* Ignore failures when trying to install some files that are not built
>  in arch all builds
>  Closes: #976756
>...

Still FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=mia&arch=all&ver=2.4.7-5&stamp=1609527793&raw=0

cu
Adrian

Bug#960488: marked as done (eslint: autopkgtest failure: missing test dependency to node-babel7)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 19:05:59 +
with message-id 
and subject line Bug#960488: fixed in eslint 5.16.0~dfsg+~4.16.8-1
has caused the Debian Bug report #960488,
regarding eslint: autopkgtest failure: missing test dependency to node-babel7
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.)


-- 
960488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eslint
Version: 5.16.0~dfsg-5
Severity: serious
Justification: unknwon

Hi,

node-babel7 seems required by autopkgtest test:

not ok 344 - 
/tmp/autopkgtest-lxc.9p09fhxf/downtmp/build.w0w/src/lib/formatters/codeframe.js
  ---
  message: '"@babel/code-frame" is not found.'
  severity: error
  data:
line: 8
column: 38
ruleId: node/no-missing-require
  ...

Cheers,
Xavier
--- End Message ---
--- Begin Message ---
Source: eslint
Source-Version: 5.16.0~dfsg+~4.16.8-1
Done: Jonas Smedegaard 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 19:48:57 +0100
Source: eslint
Architecture: source
Version: 5.16.0~dfsg+~4.16.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 960488
Changes:
 eslint (5.16.0~dfsg+~4.16.8-1) unstable; urgency=medium
 .
   * copyright: fix sort Files sections
   * build-depend on
 node-babel-core node-babel-loader node-babel-preset-env
 (not node-babel7);
 suggest node-babel-code-frame (not node-babel7)
   * declare compliance with Debian Policy 4.5.1
   * add file TODO listing pending packaging tasks,
 and their required missing Node.js dependencies
   * embed and install typescript types;
 provide virtual package node-types-eslint;
 build-depend on jq
   * update git-buildpackage settings:
 + use git branch debian/latest (not debian/sid)
   * generate unicode script during build
   * revive patch 2006 to avoid Nodejs module natural-compare;
 stop build-)depend on node-natural-compare
   * fix explicitly build-depend (not only depend) on lodash;
 fix annotate test-or-doc-only build-dependencies;
 fix build-depend explicitly on nodejs
   * fix have autopkgtest depend on recent node-babel-code-frame
 (not node-babel7 or older releases);
 properly closes: bug#960488
   * fix have autopkgtest depend on nodejs
   * update workarounds for failing tests;
 have autopkgtest depend on node-cheerio
   * drop patch 2004;
 build-depend on node-eslint-rule-composer
   * fix add version
 to provided virtual package node-eslint-config-eslint
Checksums-Sha1:
 f88435d179c9b610a9ea6eb324bbeb687fc9e18e 4279 eslint_5.16.0~dfsg+~4.16.8-1.dsc
 9159e8abb64ae82c962277905c62eb5e00057cdb 5072 
eslint_5.16.0~dfsg+~4.16.8.orig-Xtypes.tar.xz
 1c35c8140ec0f0c3450e5dc31a82efbf73224c4a 999416 
eslint_5.16.0~dfsg+~4.16.8.orig.tar.xz
 a8e1e289d8bd42844c74fb627195060b05c9269c 26756 
eslint_5.16.0~dfsg+~4.16.8-1.debian.tar.xz
 86fe6d5ef22f2133beac23b5df27590c054cd4f2 17021 
eslint_5.16.0~dfsg+~4.16.8-1_amd64.buildinfo
Checksums-Sha256:
 886a6d8cdabf478c315951f88d58a59b98154da03d6c39252978d745a8e8be0b 4279 
eslint_5.16.0~dfsg+~4.16.8-1.dsc
 a82ef7dcc6b24ed6682461ac4e6fd98a7c374cc6ba7d91007f2cd157e4be71d0 5072 
eslint_5.16.0~dfsg+~4.16.8.orig-Xtypes.tar.xz
 189c42bc869427d31259b77844a4f2a8df34ff2f5ed545d053a63f013b847a60 999416 
eslint_5.16.0~dfsg+~4.16.8.orig.tar.xz
 43a96c8df1511dacc842047bcfad4c4b83554b7688ef20321d6c6620149655ef 26756 
eslint_5.16.0~dfsg+~4.16.8-1.debian.tar.xz
 bd6d6b60b8da1c7b2c2d33632442b89dde415dade7e0a2ae91c0ed4b40a9ec98 17021 
eslint_5.16.0~dfsg+~4.16.8-1_amd64.buildinfo
Files:
 c986760a0424d0c595d0d5c534d7313b 4279 javascript optional 
eslint_5.16.0~dfsg+~4.16.8-1.dsc
 65b6327facc4c06a21eedbcf301d2218 5072 javascript optional 
eslint_5.16.0~dfsg+~4.16.8.orig-Xtypes.tar.xz
 c299105c442f1ff

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

[Christoph Anton Mitterer]

On Fri, 2021-01-01 at 12:10 +0100, Michel Le Bihan wrote:
> 
> 
> That's actually intended. It would be easier to set the build flag
> that
> disables it, but some users are still interested in using it. The way
> it's done currently still allows them to use it.

Yeah, but the point is, AFAIU, for those people who already have it now
(possibly unknowingly) it will be kept (and updated).

So unless such users accidentally stumble of this, they'll never be
able to decide whether they really want to keep it or not.



Cheers,
Chris.

Bug#976756: marked as done (mia: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 18:48:46 +
with message-id 
and subject line Bug#976756: fixed in mia 2.4.7-5
has caused the Debian Bug report #976756,
regarding mia: binary-all FTBFS
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=mia&arch=all&ver=2.4.7-3&stamp=1607360001&raw=0

...
CMake Error at mia/3d/cmake_install.cmake:110 (file):
  file INSTALL cannot find
  "/<>/obj-x86_64-linux-gnu/mia/3d/libmia3dtest-2.4.so.6.0.1":
  No such file or directory.
Call Stack (most recent call first):
  mia/cmake_install.cmake:65 (include)
  cmake_install.cmake:130 (include)


make[1]: *** [Makefile:96: install] Error 1
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.4.7-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mia package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 18:22:49 +0100
Source: mia
Architecture: source
Version: 2.4.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 976756
Changes:
 mia (2.4.7-5) unstable; urgency=medium
 .
   * Team upload.
   * Ignore failures when trying to install some files that are not built
 in arch all builds
 Closes: #976756
Checksums-Sha1:
 de40f4ba4161d8d0f5ff2cdbc6748e478c646683 2839 mia_2.4.7-5.dsc
 58e9e0bbf5c102584ab9aa946a644cb39fe9aea2 10404 mia_2.4.7-5.debian.tar.xz
 d78a69513f7d542692bc2825102ba3ff4cf3d65e 24405 mia_2.4.7-5_amd64.buildinfo
Checksums-Sha256:
 478187fa1a2a7dd43781757a0cdcbed52967bf584acd1b0978066344e552c2bb 2839 
mia_2.4.7-5.dsc
 162408d50960ac8e3c1c9807c6dcc7448eefb2d1648d3e6e1c2d7568ab1d309a 10404 
mia_2.4.7-5.debian.tar.xz
 2123e52a1e0b84c65b3175d4c630e25169554121bc7c057678c148fcd379a8b6 24405 
mia_2.4.7-5_amd64.buildinfo
Files:
 1eec2285ba2907e80ca435f6a8374033 2839 science optional mia_2.4.7-5.dsc
 ced3899c816dcf7c0219d13e6d114296 10404 science optional 
mia_2.4.7-5.debian.tar.xz
 f0a9ba517dbec20c54b13ba7dbda01f8 24405 science optional 
mia_2.4.7-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/vZ+IRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGFdQ/+JpkDA1S9sf+Hjg+fL4GzAh/GMlQqLXYb
lQZ07eHyRzIxb9tCynSzJlWJsQMsoqUSFGIx9KrWdwWfcHSJ6pnXGLxHTVcMhzYK
xH75EAVd7FAFoyBAECJ10gG0kjcDdqybuSEpzgID16gQ45KfS5rtEl31sSqG2ZVm
Sgq4DBfOEzHyORa0pc+IOzGUSvgCtV+VGfebcqgFNSpmzzK3g+qrTOuiGLCer3ax
6zLuklR1PJi7qfCqqwTQzAcooYHh5sjRt1BWgLy4rqvJUS2dHTneF6DKNMm5j0Jd
a+9P7iYc3FWeNOsTzwQ7W/MchYUimFAxMwfnUGSVuATj3fHOlcpyz4IqMZ/0xEsc
VdvJZR5xlEGNr+5mKl3oow+gd4jR+w0o4GLaRJ7HXurhWGjEguzeNQXT0JgUKqes
8RnLiuHV49EDAyLZeP0ilMCHvWvvl1gd65nIBH1qTtINVKSv/ejx64Kd+7hJ4Qfm
C9TM3AuxUrMpG9m7m8v3LwQ7e2W0RUv7mW72UuFg+7LUQ5pXvjW7MFADEYgdovAu
/4PBIp1Ret0ye363WrOQNi9fUlFseJTxYKdGfdi07TnWWYU/0qQjTcmLbsg3dqnj
F0MmGCVgPHaOdixCJjTh0w/kVTuMaWZ9wopWk+iTNm3Mz5n3xRW0zJiSn8poTlSJ
SjVCE4aMb5w=
=+yTN
-END PGP SIGNATURE End Message ---

Processed: affects 978448, block 978245 with 978448

[Debian Bug Tracking System]

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

> affects 978448 aide
Bug #978448 [libaudit-dev] Static linking fails with undefined reference to 
`audit_strsplit_r'
Added indication that 978448 affects aide
> block 978245 with 978448
Bug #978245 [src:aide] aide: FTBFS: configure: error: You don't have libaudit 
properly installed. Install it or try --without-audit.
978245 was not blocked by any bugs.
978245 was not blocking any bugs.
Added blocking bug(s) of 978245: 978448
> thanks
Stopping processing here.

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

Bug#978988: node-mqtt: autopkgtest regression in testing: Error: Timeout of 2000ms exceeded

[Paul Gevers]

Source: node-mqtt
Version: 4.2.6-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?

Does your mocha-test connect to the internet by the way? In that case,
please also add a needs-internet restriction.

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

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mqtt/9241724/log.gz

  594 passing (1m)
  4 pending
  4 failing

  1) MqttClient
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  2) MQTT 5.0
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/client_mqtt5.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  3) MqttSecureClient
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/secure_client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)

  4) Websocket Client
   pinging
 should reconnect if pingresp is not sent:
 Error: Timeout of 2000ms exceeded. For async tests and hooks,
ensure "done()" is called; if returning a Promise, ensure it resolves.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/websocket_client.js)
  at Test.Runnable._timeoutError
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
  at Timeout.
(/usr/share/nodejs/mocha/lib/runnable.js:244:24)
  at listOnTimeout (internal/timers.js:554:17)
  at processTimers (internal/timers.js:497:7)



/usr/share/nodejs/mocha/lib/runner.js:962
throw err;
^

NodeError: write after end
at writeAfterEnd
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:257:12)
at Connection.Writable.write
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:301:21)
at Connection. [as pingresp]
(/usr/share/nodejs/mqtt-connection/connection.js:83:10)
at Connection.
(/tmp/autopkgtest-lxc._v6d6q9e/downtmp/build.S1A/src/test/server_helpers_for_client_tests.js:86:20)
at Connection.emit (events.js:314:20)
at Connection.emitPacket
(/usr/share/nodejs/mqtt-connection/connection.js:10:8)
at Connection.emit (events.js:314:20)
at addChunk
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:297:12)
at readableAddChunk
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:279:11)
at Connection.Readable.push
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:240:10)
at Connection.Duplexify._forward
(/usr/share/nodejs/duplexify/index.js:172:26)
at Transform.onreadable (/usr/share/nodejs/duplexify/index.js:136:10)
at Transform.emit (events.js:314:20)
at emitReadable_
(/usr/share/nodejs/readable-stream/lib/_stream_readable.js:520:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
Emitted 'error' event on Connection instance at:
at writeAfterEnd
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:259:10)
at Connection.Writable.write
(/usr/share/nodejs/readable-stream/lib/_stream_writable.js:301:21)
[... lines matching original stack trace ...]
at processTicksAndRejections (internal/process/task_queues.js:83:21)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#967172: closing 967172

[Michael Banck]

close 967172 0.10.1~gite4aa500e-11
thanks

Processed: closing 967172

[Debian Bug Tracking System]

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

> close 967172 0.10.1~gite4aa500e-11
Bug #967172 [src:madness] madness: Unversioned Python removal in sid/bullseye
Marked as fixed in versions madness/0.10.1~gite4aa500e-11.
Bug #967172 [src:madness] madness: Unversioned Python removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Processed (with 1 error): merging 943167 967172

[Debian Bug Tracking System]

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

> merge 943167 967172
Bug #943167 {Done: Stuart Prescott } [src:madness] madness: 
Python2 removal in sid/bullseye
Unable to merge bugs because:
severity of #967172 is 'serious' not 'normal'
blocks of #967172 is '' not '937695'
done of #967172 is '' not 'Stuart Prescott '
Failed to merge 943167: Did not alter merged bugs.

> thanks
Stopping processing here.

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

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

[Adam D. Barratt]

Hi,

On Fri, 2021-01-01 at 14:21 +0100, Salvatore Bonaccorso wrote:
> Uplaoding 1.2.1+dfsg-1 + CVE fix cannot work. We have already
> released 1.2.1+dfsg-2+deb10u1 in the security archives, so any
> version we pick to fix issues need to be highter, no matter if we do
> several rollbacks or only the #975372 fix.
> 
> So we need in any case 1.2.1+dfsg-2+deb10u2 (no matter if "complete"
> rollback, or just the bugfix).
> 
> Given the move of the logdir and systemd unit has now been done with
> the DSA, I think my preference would be to only just address the
> "fallout" from the logdir move and so adress #975372.
> 
> Adam D. Barratt is Cc'ed in this message, who is a stable release
> managers in case he would like to indicate a preference.
> 
> Adam would that be fine with you with your SRM hat on, to let all the
> -2 changes pass to stable (agreeing that that would usually not be
> stable material under normal cicumstances) and so just address the
> introduced #975372?

As you say, such changes would not normally be considered as part of a
stable update. However, given that they've already been published via
the security archive and as such been on user systems for a month or so
by this stage, I think attempting to walk back the additional changes
now is likely to cause us more pain than just going with them, and
hoping that #975372 is the only issue caused as a result.

Regards,

Adam

Processed: unarchiving 960488

[Debian Bug Tracking System]

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

> unarchive 960488
Bug #960488 {Done: Jonas Smedegaard } [eslint] eslint: 
autopkgtest failure: missing test dependency to node-babel7
Unarchived Bug 960488
> thanks
Stopping processing here.

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

Bug#977230: bagel FTBFS with Boost 1.74

[Adrian Bunk]

On Fri, Jan 01, 2021 at 01:07:25PM +0100, Michael Banck wrote:
> Hi,
> 
> On Sat, Dec 12, 2020 at 09:45:10PM +0200, Adrian Bunk wrote:
> > Source: bagel
> > Version: 1.2.2-1
> > Severity: serious
> > Tags: ftbfs bullseye sid
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=bagel&arch=amd64&ver=1.2.2-1%2Bb2&stamp=1607773477&raw=0
> > 
> > ...
> > /usr/include/boost/property_tree/ptree_serialization.hpp: In function ‘void 
> > boost::property_tree::detail::load_children(Archive&, 
> > boost::property_tree::basic_ptree&)’:
> > /usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error: 
> > ‘library_version_type’ in namespace ‘bsa’ does not name a type
> >66 | const bsa::library_version_type library_version(
> >   |^~~~
> > ...
> 
> I tried to look at it, but it's unclear to me where BAGEL is being at
> fault, it seems to just include boost headers and then there's error in
> one of them? Should it do something different?
>...

This might be a bug in boost?
https://github.com/boostorg/property_tree/pull/62

> Michael

cu
Adrian

Processed: tagging 975145

[Debian Bug Tracking System]

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

> tags 975145 + patch
Bug #975145 [src:ser-player] ser-player: FTBFS: src/frame_slider.cpp:372:18: 
error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 975131

[Debian Bug Tracking System]

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

> tags 975131 + fixed-upstream
Bug #975131 [src:datovka] datovka: FTBFS: src/delegates/tag_item.cpp:59:15: 
error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#976482: marked as done (strace: FTBFS: ../io_uring.c:30:1: error: static assertion failed: "struct io_cqring_offsets.resv is missing, please update the decoder")

[Debian Bug Tracking System]

Your message dated Fri, 1 Jan 2021 15:26:06 +
with message-id <20210101152606.gb...@tack.einval.com>
and subject line Re: Bug#976482: strace: FTBFS: ../io_uring.c:30:1: error: 
static assertion failed: "struct io_cqring_offsets.resv is missing, please 
update the decoder"
has caused the Debian Bug report #976482,
regarding strace: FTBFS: ../io_uring.c:30:1: error: static assertion failed: 
"struct io_cqring_offsets.resv is missing, please update the decoder"
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.)


-- 
976482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strace
Version: 5.5-3
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H   -I./linux/aarch64 -I../linux/aarch64 -I./linux 
> -I../linux -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body 
> -Wformat-security -Wignored-qualifiers -Wimplicit-fallthrough=5 -Winit-self 
> -Wlogical-op -Wmissing-parameter-type -Wnested-externs 
> -Wold-style-declaration -Wold-style-definition -Woverride-init -Wsign-compare 
> -Wtype-limits -Wwrite-strings   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -O2 -MT 
> strace-io_uring.o -MD -MP -MF .deps/strace-io_uring.Tpo -c -o 
> strace-io_uring.o `test -f 'io_uring.c' || echo '../'`io_uring.c
> In file included from ../static_assert.h:11,
>  from ../xlat/uring_setup_features.h:4,
>  from ../io_uring.c:14:
> ../io_uring.c:30:1: error: static assertion failed: "struct 
> io_cqring_offsets.resv is missing, please update the decoder"
>30 | static_assert(0, "struct io_cqring_offsets.resv is missing"
>   | ^
> make[3]: *** [Makefile:5165: strace-io_uring.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/strace_5.5-3_unstable.log

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

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

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

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

Just uploaded version 5.10-1 with some tests disabled. Looks good on
amd64, arm64 and s390x so I think this is fixed.

Cheers,

Steve

On Sat, Dec 05, 2020 at 09:11:23PM +0100, Lucas Nussbaum wrote:
>On 05/12/20 at 13:31 +0100, Lucas Nussbaum wrote:
>> Source: strace
>> Version: 5.5-3
>> Severity: serious
>> Justification: FTBFS on arm64
>> Tags: bullseye sid ftbfs
>> Usertags: ftbfs-20201205 ftbfs-bullseye
>> 
>> Hi,
>> 
>> During a rebuild of all packages in sid, your package failed to build
>> on arm64 (I don't know if it also fails on amd64).
>
>It also fails on amd64. You can find a build log in
>http://qa-logs.debian.net/2020/12/05/amd64/
>
>Lucas
>
-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   https://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.--- End Message ---

Bug#978242: marked as done (nifti2dicom: FTBFS: unsatisfiable build-dependency: libnifti-dev (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Fri, 1 Jan 2021 16:01:44 +0100
with message-id <20210101150144.ge23...@an3as.eu>
and subject line Re: Bug#978242: nifti2dicom: FTBFS: unsatisfiable 
build-dependency: libnifti-dev (versioned dep on a virtual pkg?)
has caused the Debian Bug report #978242,
regarding nifti2dicom: FTBFS: unsatisfiable build-dependency: libnifti-dev 
(versioned dep on a virtual pkg?)
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cmake, qtbase5-dev, 
> libinsighttoolkit4-dev, libfftw3-dev, libtclap-dev, libvtk7-qt-dev | 
> libvtk7-dev (<< 6.2), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cmake, qtbase5-dev, 
> libinsighttoolkit4-dev, libfftw3-dev, libtclap-dev, libvtk7-qt-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [427 B]
> Get:5 copy:/<>/apt_archive ./ Packages [496 B]
> Fetched 1880 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libinsighttoolkit4-dev : Depends: libnifti-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/nifti2dicom_0.4.11-3_unstable.log

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

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

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
> >  libinsighttoolkit4-dev : Depends: libnifti-dev
> > E: Unable to correct problems, you have held broken packages.

This is fixed now.--- End Message ---

Bug#978974: freedict-tools FTBFS: No Python executable found, please make sure that a recent Python is in the search path.

[Adrian Bunk]

Source: freedict-tools
Version: 0.5.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=freedict-tools&arch=all&ver=0.5.0-1&stamp=1609433105&raw=0

...
   dh_auto_clean
make -j4 distclean
make[1]: Entering directory '/<>'
mk/config.mk:84: *** No Python executable found, please make sure that a recent 
Python is in the search path.  Stop.
make[1]: Leaving directory '/<>'
dh_auto_clean: error: make -j4 distclean returned exit code 2
make: *** [debian/rules:10: clean] Error 25

Bug#978975: ruby-em-redis FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: ruby-em-redis
Version: 0.3.0+gh-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-em-redis&arch=all&ver=0.3.0%2Bgh-2.1&stamp=1609255928&raw=0

...
EventMachine::ConnectionError: unable to resolve address: Address family for 
hostname not supported
/usr/lib/ruby/vendor_ruby/eventmachine.rb:679:in `connect_server': 
EventMachine::Protocols::Redis - should be able to provide a logger
/usr/lib/ruby/vendor_ruby/eventmachine.rb:679:in `bind_connect'
/usr/lib/ruby/vendor_ruby/eventmachine.rb:655:in `connect'
/<>/lib/em-redis/redis_protocol.rb:321:in `connect'
/<>/spec/redis_commands_spec.rb:9:in `block (2 levels) in 
'
/<>/spec/redis_commands_spec.rb:16:in `block in '
...
90 specifications (32 requirements), 0 failures, 75 errors
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/ruby-em-redis-0.3.0\+gh/debian/ruby-em-redis returned exit code 1
make[1]: *** [debian/rules:26: override_dh_auto_install] Error 25

Bug#978960: marked as done (python-azure's autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 14:50:17 +
with message-id 
and subject line Bug#978960: fixed in python-azure 20201208+git-3
has caused the Debian Bug report #978960,
regarding python-azure's autopkg tests fail
to be marked as done.

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

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


-- 
978960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-azure
Version: 20201208+git-2
Severity: serious
Tags: sid bullseye

python-azure's autopkg tests fail, blocking the migration of python3-defaults:

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

[...]
- Captured stdout call -
continue printing events
= 4 failed, 6 passed in 26.81 seconds ==
autopkgtest [05:09:30]: test python3-tests: ---]
autopkgtest [05:09:30]: test python3-tests:  - - - - - - - - - - results - - - -
- - - - - -
python3-testsFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: python-azure
Source-Version: 20201208+git-3
Done: Luca Boccassi 

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

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

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated python-azure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 14:18:01 +
Source: python-azure
Architecture: source
Version: 20201208+git-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Luca Boccassi 
Closes: 978960
Changes:
 python-azure (20201208+git-3) unstable; urgency=medium
 .
   * Deselect tests that need a working remote connection from autopkgtest
 run (Closes: #978960)
Checksums-Sha1:
 52d090ae2bde00d61fc1cfe714c2eb25606371c7 2629 python-azure_20201208+git-3.dsc
 1782c5fad1c0aee32a9951e7f532638961be5dbe 11576 
python-azure_20201208+git-3.debian.tar.xz
 708caeaecb7c3482af633ff58f2a04a8f0a666ce 8175 
python-azure_20201208+git-3_source.buildinfo
Checksums-Sha256:
 f199daeddb2aafa625f0f2e4e5188dc8942c6863ec4a9e005cd6e08e8a9fcdec 2629 
python-azure_20201208+git-3.dsc
 1155aaf47859e11763d5fc348783f0f15b19df5b185a5f65e54edb99341c9e4f 11576 
python-azure_20201208+git-3.debian.tar.xz
 23c6292db062c40cfb78dfa7b25723ea46eba0d86fef0bb4dde53571a8ec3655 8175 
python-azure_20201208+git-3_source.buildinfo
Files:
 db29c12853201683aaa212d876867b9c 2629 python optional 
python-azure_20201208+git-3.dsc
 5c2990db3b3b5bd76e7e847acbd1e7ca 11576 python optional 
python-azure_20201208+git-3.debian.tar.xz
 70913934be53bf47479233ecb29c4fa0 8175 python optional 
python-azure_20201208+git-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl/vMXcRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQSylmgFB4UWJ+MAf+IoUT6UVHlwa5KayR0jiH5ePXgihF27h3
Jzppon0OXx26JLBq3csM+9S9qykXA7GeT/e2mZtwTS943ZwUPhbbC9FjEwiZ4EmD
o8eTORKHjJqSAkplicRskiCPW1LCxyIpyB4YozlFTJwcYyfU/8oQ25F6+AQgHvw4
aYRVv9fTj9diIXmb+4mtIHyUeQkdVXK3i48vE8vIUztLJD0XATczJuV3Db3+zMDL
gZOTwy4GUx6BeKjQxwIYP9tiXnasGn0qmvo5oG49j2pHvXC+KZVQTRQemONYMRnw
L4ZWY0M3Jl4k54OzJC40d30MqXgOCqzTnyKW5dEdDYHraFRx3MMKWA==
=OzJr
-END PGP SIGNATURE End Message ---

Processed: Bug#978960 marked as pending in python-azure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978960 [src:python-azure] python-azure's autopkg tests fail
Added tag(s) pending.

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

Bug#978960: marked as pending in python-azure

[Luca Boccassi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-azure/-/commit/45ca7aea9f0bbd3ba084073e86a79c8bd5757015


Deselect tests that need a working remote connection from autopkgtest run

Closes: #978960


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978960

Processed: Bug#976932 marked as pending in gnome-photos

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976932 [src:gnome-photos] gnome-photos: FTBFS on machines with more than 
128 cores
Added tag(s) pending.

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

Bug#976932: marked as pending in gnome-photos

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gnome-photos/-/commit/11e4fd646c4e4aabb0dbfb69f9b449e03f92cfd5


Add patch to avoid exceeding gegl's arbitrary max number of threads

Closes: #976932


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976932

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

[Salvatore Bonaccorso]

Hi Alexander,

Sorry for the late reply.

On Sat, Dec 26, 2020 at 08:16:28PM +0300, Alexander Gerasiov wrote:
> On Thu, 24 Dec 2020 06:31:31 +0100
> Salvatore Bonaccorso  wrote:
> 
> > Hi Alexander,
> > 
> > On Tue, Dec 22, 2020 at 07:57:15PM +0300, Alexander Gerasiov wrote:
> > > On Sun, 20 Dec 2020 11:50:42 +0200
> > > Adrian Bunk  wrote:  
> > > > this is a regression in 1.2.1+dfsg-2 that is currently in both 
> > > > buster-security (which was done on top of 1.2.1+dfsg-2 that
> > > > introduced the regression, not on top of 1.2.1+dfsg-1 in buster)
> > > > and in unstable/testing (which currently misses the CVE fixes).
> > > > 
> > > > It would be good if you could make an upload to unstable with this
> > > > bug fixed on top of 1.2.1+dfsg-2+deb10u1, and then backport that
> > > > change to buster.
> > > > 
> > > > Please coordinate with the security team whether this would
> > > > warrant a regression update to the DSA or should be done through
> > > > the next point release.  
> > > 
> > > Hi, Team.
> > > 
> > > Does anyone mind against uploading fix to stable-proposed-update?
> > > The fix is here:
> > > https://salsa.debian.org/debian/minidlna/-/commits/buster-security/
> > > Or should it go to buster-security?  
> > 
> > Fixing it via buster-proposed-updates in the next point release works.
> > 
> > As regression from the last DSA, given we all have not spotted it was
> > based on the testing version, I think we can as well release it via a
> > regression update via buster-security.
> > 
> > This will be only an issue if someone decides to purge the package in
> > stable.
> > 
> > The other issue: As the update was based on -2 rather than -1 it
> > contains several more (packaging) changes as well and wonder if
> > current stable users might have any issue with those (I suspect not
> > because systemd service addition is probably ok, the move of
> > logdiretory might be though suprising in a stable update and the fix
> > for #941410 is probably just a benefit).
> > 
> > Do you anticipate any problems which would arise from this that we did
> > release it on top of the "wrong" version?
> You get it absolutely right. The only notable changes in -2 are:
> 1. systemd unit
> 2. logdir location
> 
> Others are packaging improvements and bugfixes we tested in testing for
> months, so I don't expect any regression here.
> 
> 
> So I have two open questions:
> 1. which version to upload? (I could upload version equal to
>1.2.1+dfsg-1 + CVE fixes on top (rollback all accident changes). Or I
>can only fix #975372 in current buster-security version as I did in
>testing.).

Uplaoding 1.2.1+dfsg-1 + CVE fix cannot work. We have already released
1.2.1+dfsg-2+deb10u1 in the security archives, so any version we pick
to fix issues need to be highter, no matter if we do several rollbacks
or only the #975372 fix.

So we need in any case 1.2.1+dfsg-2+deb10u2 (no matter if "complete"
rollback, or just the bugfix).

Given the move of the logdir and systemd unit has now been done with
the DSA, I think my preference would be to only just address the
"fallout" from the logdir move and so adress #975372.

Adam D. Barratt is Cc'ed in this message, who is a stable release
managers in case he would like to indicate a preference.

Adam would that be fine with you with your SRM hat on, to let all the
-2 changes pass to stable (agreeing that that would usually not be
stable material under normal cicumstances) and so just address the
introduced #975372?

> 2. where to upload? (buster-security of buster-proposed-updates)

Personally I would have said fixing it in the upcoming point release
is enough evne though the issue was introduced via a DSA. But the
point release date is not settled yet, and Moritz indicated offlist as
well that a regression update via a DSA is fine.

So in short: let's try to adress this with a regression update via a
DSA.

> 
> Please help me with the decision =)

Regards,
Salvatore

Bug#957424: marked as done (libaccounts-qt: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 12:50:34 +
with message-id 
and subject line Bug#957424: fixed in libaccounts-qt 1.16-1
has caused the Debian Bug report #957424,
regarding libaccounts-qt: ftbfs with GCC-10
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
Generating graph info page...
Generating directory documentatiQStandardPaths: XDG_RUNTIME_DIR not set, 
defaulting to '/tmp/runtime-root'
QStandardPaths: wrong ownership on runtime directory /tmp/runtime-root, 1001 
instead of 0
Building up file structure...
Insert custom filters...
Insert help data for filter section (1 of 1)...
Insert files...
Insert contents...
Insert indices...
Documentation successfully generated.
on...
Generating index page...
Generating page index...
Generating module index...
Generating namespace member index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating graphical class hierarchy...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
Running plantuml with JAVA...
Running dot...
Running dot for graph 1/1
Running qhelpgenerator...
lookup cache used 713/65536 hits=4304 misses=729
finished...
cp -r /<>/doc/html 
/<>/debian/tmp/usr/share/doc/accounts-qt; cp -r 
/<>/doc/qch /<>/debian/tmp/usr/share/doc/accounts-qt;
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
find debian/tmp -name jquery.js -exec ln -sfv 
/usr/share/javascript/jquery/jquery.js {} \;
'debian/tmp/usr/share/doc/accounts-qt/html/jquery.js' -> 
'/usr/share/javascript/jquery/jquery.js'
rm -f debian/tmp/usr/share/libaccounts-qt-tests/*
rm -f debian/tmp/usr/bin/*
dh_install --fail-missing
dh_install: warning: Please use dh_missing --list-missing/--fail-missing instead
dh_install: warning: This feature will be removed in compat 12.
make[1]: Leaving directory '/<>'
   dh_installdocs
   dh_installchangelogs
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_strip
   dh_makeshlibs
dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff 
output below
dpkg-gensymbols: warning: debian/libaccounts-qt5-1/DEBIAN/symbols doesn't match 
completely debian/libaccounts-qt5-1.symbols
--- debian/libaccounts-qt5-1.symbols (libaccounts-qt5-1_1.15-2_amd64)
+++ dpkg-gensymbolsZ1urcq   2020-02-26 12:44:42.003243232 +
@@ -1,4 +1,8 @@
 libaccounts-qt5.so.1 libaccounts-qt5-1 #MINVER#
+ _ZN10QByteArrayD1Ev@Base 1.15-2
+ _ZN10QByteArrayD2Ev@Base 1.15-2
+ _ZN7QStringD1Ev@Base 1.15-2
+ _ZN7QStringD2Ev@Base 1.15-2
  _ZN8Accounts11ApplicationC1EP14_AgApplication@Base 1.13
  _ZN8Accounts11ApplicationC1ERKS0_@Base 1.13
  _ZN8Accounts11ApplicationC1Ev@Base 1.13
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:36: binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: libaccounts-qt
Source-Version: 1.16-1
Done: Pino T

Bug#966594: rt-app: patch for newer json-c

[Wookey]

Gianfranco Costamagna  wrote:

> hello, attached a patch that makes it build with newer json-c

Great. Thanks for that. Only just noticed it now.

So I just updated to rt-1.0, included your fix (which saved me a load
of faff working out what was wrong with the build, so that was great),
converted to python3 and we have a useful package again :-)

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#966594: marked as done (rt-app: patch for newer json-c)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 12:34:39 +
with message-id 
and subject line Bug#966594: fixed in rt-app 1.0-1
has caused the Debian Bug report #966594,
regarding rt-app: patch for newer json-c
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.)


-- 
966594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-app
Version: 0.3-2
Severity: serious
tags: patch

hello, attached a patch that makes it build with newer json-c

thanks

G.
diff -Nru rt-app-0.3/debian/changelog rt-app-0.3/debian/changelog
--- rt-app-0.3/debian/changelog 2017-03-09 14:44:33.0 +0100
+++ rt-app-0.3/debian/changelog 2020-07-31 10:09:43.0 +0200
@@ -1,3 +1,9 @@
+rt-app (0.3-2.1) unstable; urgency=medium
+
+  * Patch for newer json-c (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
10:09:43 +0200
+
 rt-app (0.3-2) unstable; urgency=medium
 
   * Fix FTBFS on some arches by defining unsigned long long as __u64
diff -Nru rt-app-0.3/debian/patches/new-jsoncpp.patch 
rt-app-0.3/debian/patches/new-jsoncpp.patch
--- rt-app-0.3/debian/patches/new-jsoncpp.patch 1970-01-01 01:00:00.0 
+0100
+++ rt-app-0.3/debian/patches/new-jsoncpp.patch 2020-07-31 10:09:32.0 
+0200
@@ -0,0 +1,35 @@
+Description: Patch for newer json-c removed is_error
+Author: Gianfranco Costamagna 
+Last-Update: 2020-07-30
+
+Index: rt-app-0.3/src/rt-app_parse_config.c
+===
+--- rt-app-0.3.orig/src/rt-app_parse_config.c
 rt-app-0.3/src/rt-app_parse_config.c
+@@ -18,9 +18,16 @@
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, 
USA.
+ */
+-#include 
+ #include "rt-app_parse_config.h"
+ 
++// not exported anymore by new json-c
++#ifndef TRUE
++#define TRUE 1
++#endif
++#ifndef FALSE
++#define FALSE 0
++#endif
++
+ #define PFX "[json] "
+ #define PFL " "PFX
+ #define PIN PFX""
+@@ -886,7 +893,7 @@
+ {
+   struct json_object *global, *tasks, *resources;
+ 
+-  if (is_error(root)) {
++  if (root == NULL) {
+   log_error(PFX "Error while parsing input JSON");
+   exit(EXIT_INV_CONFIG);
+   }
diff -Nru rt-app-0.3/debian/patches/series rt-app-0.3/debian/patches/series
--- rt-app-0.3/debian/patches/series2017-03-09 14:44:33.0 +0100
+++ rt-app-0.3/debian/patches/series2020-07-31 10:09:39.0 +0200
@@ -1 +1,2 @@
 longlong-u64.diff
+new-jsoncpp.patch
--- End Message ---
--- Begin Message ---
Source: rt-app
Source-Version: 1.0-1
Done: Wookey 

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

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

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated rt-app package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jan 2021 04:55:59 +
Source: rt-app
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Linaro Packagers 
Changed-By: Wookey 
Closes: 945733 966594
Changes:
 rt-app (1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Convert python2 scripts to python3 (Closes: #945733)
 .
   [ Gianfranco Costamagna ]
   * Patch for newer json-c (Closes: #966594)
Checksums-Sha1:
 ca07f1dc864f1a77422b6ac5008f781c7f2466b8 1765 rt-app_1.0-1.dsc
 7601bea4988d23c9edbb8b0e45388af8e063f413 52074 rt-app_1.0.orig.tar.gz
 b20696340bc81ce5a18238298f64a1ae8009de79 5268 rt-app_1.0-1.debian.tar.xz
 f8dd8db3b6774b3882e5296b27a9bb53ce4e4e61  rt-app_1.0-1_source.buildinfo
Checksums-Sha256:
 0d477fb657834d21d9fa23c2d1ebe0d01c5ab3cbabccd8ccb31d463e152f3bfb 1765 
rt-app_1.0-1.dsc
 7562bd5fea657fec0fdc4e01fc78a3afd332ee8151424dbae4bf7767400259f6 52074 
rt-app_1.0.orig.tar.gz
 badf613c1ea4fe5d8fc46875edb152f83ff94e084efaaab40bcf14080eee077c 5268 
rt-app_1.0-1.debian.tar.xz
 84445f97425edbfcd133f99089b9ebe239d9aafde3d6377b6b73ab74810168e0  
rt-app_1.0-1_source.buildinfo
Files:
 6d81649b8bcb8a6bffc013d04347c30a 1765 mi

Bug#966789: marked as done (rt-app: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 12:34:39 +
with message-id 
and subject line Bug#945733: fixed in rt-app 1.0-1
has caused the Debian Bug report #945733,
regarding rt-app: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


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

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated rt-app package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jan 2021 04:55:59 +
Source: rt-app
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Linaro Packagers 
Changed-By: Wookey 
Closes: 945733 966594
Changes:
 rt-app (1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Convert python2 scripts to python3 (Closes: #945733)
 .
   [ Gianfranco Costamagna ]
   * Patch for newer json-c (Closes: #966594)
Checksums-Sha1:
 ca07f1dc864f1a77422b6ac5008f781c7f2466b8 1765 rt-app_1.0-1.dsc
 7601bea4988d23c9edbb8b0e45388af8e063f413 52074 rt-app_1.0.orig.tar.gz
 b20696340bc81ce5a18238298f64a1ae8009de79 5268 rt-app_1.0-1.debian.tar.xz
 f8dd8db3b6774b3882e5296b27a9bb53ce4e4e61  rt-app_1.0-1_source.buildinfo
Checksums-Sha256:
 0d477fb657834d21d9fa23c2d1ebe0d01c5ab3cbabccd8ccb31d463e152f3bfb 1765 
rt-app_1.0-1.dsc
 7562bd5fea657fec0fdc4e01fc78a3afd332ee8151424dbae4bf7767400259f6 52074 
rt-app_1.0.orig.tar.gz
 badf613c1ea4fe5d8fc46875edb152f83ff94e084efaaab40bcf14080eee077c 5268 
rt-app_1.0-1.debian.tar.xz
 84445f97425edbfcd133f99089b9ebe239d9aafde3d6377b6b73ab74810168e0  
rt-app_1.0-1_source.buildinfo
Files:
 6d81649b8bcb8a6bffc013d04347c30a 1765 misc optional rt-app_1.0-1.dsc
 1499a9ef69d656e33f39fa1f22154600 52074 misc optional rt-app_1.0.orig.tar.gz
 f9de2d8e3d7407c0a5dbbe7cd7aa5691 5268 misc optional rt-app_1.0-1.debian.tar.xz
 cee7397424f08e492f663bad61a79a01  misc optional 
rt-app_1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAl/vFU8ACgkQ+4YyUahv
nkedyA//XO8k52c2JdU5ja2kIPm2Dk7M2KlVsQAwS8pDa9ArVIpYlhm2AFA/pqD5
J0sGsrMOGYLmgvwqYz3kLU0HcNks/YlILWaPKI6nnQ2UmjZ86Gu62NiL4SWT+f8M
H9xqOe9CA4N9IjxZtI29SctoA3bCjdXpsdQWqNz5biGwiBxV4vgJMyaiaHIxsizh
ytm51O/cSKHnlYHpbFDOY4N4JSJjDdc2/sAgB1AeBWyS8QwhdKPGDPCaf7/clUrY
z/sRoTCMZ7ctkFS6ge5DK7VBWKLpiVNwuEBrcE5JyR+xXn2I1ojaLotbNGADyHSE
Ep6clFnFxpA4ACKgZb47TJFchHcizxL+1gkXtrOasnh18yXuXc/hDiCIIvpu4Mxh
OQb48Q2sGt4Qh+cbp+YOgvUCWb9KAJbNa1QLoB/4nfjICl5ehJMv/txuw62ZHvLO
SOQeCvML3j9/FbMAPvTDjGNHro1s6k9p0eIh9fTAwD8rh6aWtfz/3ATKCXOl0tJi
k/9R35PJjY2X/f07Ks8D7QKV5ItyVobjtywUEGWca4BSAanX0YzjIwa0Cl1O4eDT
X9U0rmc/d55PDIFx6DnWKdI6ZoW2FZPM0yQG4ISyZSrRtS2ftRQTZ0i6xfv5a/M1
65on+qxY4FxL4HVOZsQNhZ1iZuGQ1vd+Tm0Ul7202k/O59wLz8Q

Bug#945733: marked as done (rt-app: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 12:34:39 +
with message-id 
and subject line Bug#945733: fixed in rt-app 1.0-1
has caused the Debian Bug report #945733,
regarding rt-app: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
945733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-app
Version: 0.3-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated rt-app package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jan 2021 04:55:59 +
Source: rt-app
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Linaro Packagers 
Changed-By: Wookey 
Closes: 945733 966594
Changes:
 rt-app (1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Convert python2 scripts to python3 (Closes: #945733)
 .
   [ Gianfranco Costamagna ]
   * Patch for newer json-c (Closes: #966594)
Checksums-Sha1:
 ca07f1dc864f1a77422b6ac5008f781c7f2466b8 1765 rt-app_1.0-1.dsc
 7601bea4988d23c9edbb8b0e45388af8e063f413 52074 rt-app_1.0.orig.tar.gz
 b20696340bc81ce5a18238298f64a1ae8009de79 5268 rt-app_1.0-1.debian.tar.xz
 f8dd8db3b6774b3882e5296b27a9bb53ce4e4e61  rt-app_1.0-1_source.buildinfo
Checksums-Sha256:
 0d477fb657834d21d9fa23c2d1ebe0d01c5ab3cbabccd8ccb31d463e152f3bfb 1765 
rt-app_1.0-1.dsc
 7562bd5fea657fec0fdc4e01fc78a3afd332ee8151424dbae4bf7767400259f6 52074 
rt-app_1.0.orig.tar.gz
 badf613c1ea4fe5d8fc46875edb152f83ff94e084efaaab40bcf14080eee077c 5268 
rt-app_1.0-1.debian.tar.xz
 84445f97425edbfcd133f99089b9ebe239d9aafde3d6377b6b73ab74810168e0  
rt-app_1.0-1_source.buildinfo
Files:
 6d81649b8bcb8a6bffc013d04347

Bug#978939: marked as done (zeekctl: missing Breaks+Replaces: broctl (<< 2))

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 12:18:40 +
with message-id 
and subject line Bug#978939: fixed in zeekctl 2.2.0+ds1-2
has caused the Debian Bug report #978939,
regarding zeekctl: missing Breaks+Replaces: broctl (<< 2)
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.)


-- 
978939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zeekctl
Version: 2.2.0+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../zeekctl_2.2.0+ds1-1_all.deb ...
  Unpacking zeekctl (2.2.0+ds1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zeekctl_2.2.0+ds1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/broctl', which is also in package broctl 1.4-1
  Errors were encountered while processing:
   /var/cache/apt/archives/zeekctl_2.2.0+ds1-1_all.deb


cheers,

Andreas


broctl=1.4-1_zeekctl=2.2.0+ds1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zeekctl
Source-Version: 2.2.0+ds1-2
Done: Hilko Bengen 

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated zeekctl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jan 2021 12:46:07 +0100
Source: zeekctl
Architecture: source
Version: 2.2.0+ds1-2
Distribution: experimental
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Closes: 978939
Changes:
 zeekctl (2.2.0+ds1-2) experimental; urgency=medium
 .
   * Add Breaks/Replaces broctl (Closes: #978939)
   * Update dependencies for default-mta
Checksums-Sha1:
 1ec36366d3417ba5a4beae138497dd9eca441ae7 1936 zeekctl_2.2.0+ds1-2.dsc
 8c77a3cb35e06ac9b605cb180e686e2710a8be2c 13816 
zeekctl_2.2.0+ds1-2.debian.tar.xz
 c78408ec22298a430c60cef11e2b18559f11ce6b 8817 
zeekctl_2.2.0+ds1-2_source.buildinfo
Checksums-Sha256:
 b3533cc72f0c992431c9f88cfcb813c8611bb1e06642545ff79499f949d57b77 1936 
zeekctl_2.2.0+ds1-2.dsc
 b9dfef17baccf4e9a562fc60466f2775457e22583392b30ed23ba6042fe54a5f 13816 
zeekctl_2.2.0+ds1-2.debian.tar.xz
 bf25be9123d6042cb35b71a5a075f3bb4aa8e1b8bdaa16cdde9166beb52b224d 8817 
zeekctl_2.2.0+ds1-2_source.buildinfo
Files:
 b38d4d6ddf6cce9ccb2969e16c8e64bb 1936 net optional zeekctl_2.2.0+ds1-2.dsc
 440a67af9eec955b99ce9a7d2a9a6423 13816 net optional 
zeekctl_2.2.0+ds1-2.debian.tar.xz
 2960553a7574ed9d4f14dbc520c8a358 8817 net optional 
zeekctl_2.2.0+ds1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl/vDz0ACgkQdbcQY1wh
On5hZg/8CEk4X4HEbS/mg9rkU5FyXR8GdLr/j1NqbDprIyofkMv36M9mrfSmT0Iz
F+zWOU90fpEhUhVyaB2lOAqVyh+DDbhCXyaD512n3jQNBnpqs3VTDrVVkiVIRZy/
6nWSINLgLgCA+IsTfzsW8aLiy/vFvhWJKD6FIHwJnezxkvfd6T2irhsOxTuPxdJO
yzM6ACfuucjDT7NJAvXG9AGzMPuTVlHIoLSVTMzlzCjEKhbnMk6K7IixpDKYhDem
tLQASxC5tlrZeDw6nZQTeWUUWlJkLMp97I7Tnku/unt8/i5A38eRMa0N04Y9Uhla
13CbJNJk8ADvB+rDo9MlswRsdpFqfgNWJ0ThVqh77/GI80w0zKpdlOEHMrpsWOJH
JpHX6F9C6NQTo/veurB1SrVbhq3u6lGtXvXB26TiF/uwZTacscDY4nZmSXgLqHV2
7z+/iKQyayT3WLE8ZyXPN43Sc87/BOmdtSseHidcvQQxbWLDV6SEZ/wbqWJcq5mq
BLCEsHAHgeldHQSOSQyTvJq1UZB/VQzqjbspx6zNA1xDX71geGFLMgyjEvfbmkua
ZS8/delg1SBKUBva9yd4HfwooiADOGRTkF+3ru7atlN63R23CyrK1EpxZOVugJ4d
3HEgINq5xxsvGg8AayYHYUapK5u1OxCwx5v8gObyt5dfJWpzpfA=
=wyAT
-END PGP SIGNATURE End Message ---

Bug#977230: bagel FTBFS with Boost 1.74

[Michael Banck]

Hi,

On Sat, Dec 12, 2020 at 09:45:10PM +0200, Adrian Bunk wrote:
> Source: bagel
> Version: 1.2.2-1
> Severity: serious
> Tags: ftbfs bullseye sid
> 
> https://buildd.debian.org/status/fetch.php?pkg=bagel&arch=amd64&ver=1.2.2-1%2Bb2&stamp=1607773477&raw=0
> 
> ...
> /usr/include/boost/property_tree/ptree_serialization.hpp: In function ‘void 
> boost::property_tree::detail::load_children(Archive&, 
> boost::property_tree::basic_ptree&)’:
> /usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error: 
> ‘library_version_type’ in namespace ‘bsa’ does not name a type
>66 | const bsa::library_version_type library_version(
>   |^~~~
> ...

I tried to look at it, but it's unclear to me where BAGEL is being at
fault, it seems to just include boost headers and then there's error in
one of them? Should it do something different?

|In file included from ../../../src/util/serialization.h:46,
| from ../../../src/util/input/input.h:31,
| from input.cc:27:
|/usr/include/boost/property_tree/ptree_serialization.hpp: In function
|‘void boost::property_tree::detail::load_children(Archive&,
|boost::property_tree::basic_ptree&)’:
|/usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error:
|‘library_version_type’ in namespace ‘bsa’ does not name a type
|   66 |  


Michael

Bug#978935: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

[Michael Biebl]

Control: severity -1 normal

Am 01.01.21 um 01:19 schrieb Vincent Lefevre:

On 2020-12-31 20:22:56 +0100, Michael Biebl wrote:

Am 31.12.20 um 18:37 schrieb Vincent Lefevre:

During the upgrade, network-manager disconnected, so that I completely
lost the network connection. Fortunately, I was in front of my machine,
but this means that a remote upgrade can make the machine unavailable!


I might be mistaken, but afaics, this has always been the case for WiFi
connections (as it is not really possible to carry the state across daemon
reexecs). Are you saying this is not the case?


I've been using NetworkManager only since July on my laptop.
I've checked my logs, and this was the first time I upgraded
NetworkManager over WiFi.

Before using NetworkManager, I've never had such an problem, IIRC.
When my machine was connected via WiFi, I was using wicd. I suppose
that it could handle the reconnection, or this would mean that
I upgraded it only over Ethernet (I don't remember).

The name of the active connection could be stored in a file, so that
a reexec'ed daemon could pick the information. By active connection,
I mean the last connection chosen by the user, under the condition
that the user has not explicitly disconnected.


It's not that simple, unfortunately. There is much more state, 
especially in external daemons like wpasupplicant.



Ethernet connections should not be torn down on a daemon stop.


See also this NEWS entry from the 1.6 release:


* NetworkManager would now keep most connections up on shutdown (except Wi-Fi
connections, VPN connections and other kinds that can't be assumed on
startup)



The alternative of not restarting NM on upgrades isn't great either.

Not sure if there is anything that can be done about this.



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #978935 [network-manager] network-manager: disconnect on upgrade
Severity set to 'normal' from 'serious'

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

Processed: tagging 957424

[Debian Bug Tracking System]

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

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

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

Bug#945961: marked as done (xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*')

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 11:18:58 +
with message-id 
and subject line Bug#945961: fixed in xz-utils 5.2.5-1.0
has caused the Debian Bug report #945961,
regarding xz-utils: FTBFS: cannot stat 
'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'
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.)


-- 
945961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xz-utils
Version: 5.2.4-1
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
dh build --parallel
   dh_update_autotools_config -O--parallel
   dh_auto_configure -O--parallel
   dh_auto_build -O--parallel
   dh_auto_test -O--parallel
 fakeroot debian/rules binary
dh binary --parallel
   debian/rules install
make[1]: Entering directory '/build/xz-utils-5.2.4'
dh install --parallel
   debian/rules build
make[2]: Entering directory '/build/xz-utils-5.2.4'
dh build --parallel
make[2]: Leaving directory '/build/xz-utils-5.2.4'
   dh_testroot -O--parallel
   dh_prep -O--parallel
   debian/rules override_dh_auto_install
make[2]: Entering directory '/build/xz-utils-5.2.4'
dh_auto_install --builddirectory debian/xzdec-build
dh_auto_install --builddirectory debian/normal-build
dh_auto_install --builddirectory debian/static-build
set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
install -d debian/tmp/lib/$arch; \
mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No
such file or directory
make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
make[2]: Leaving directory '/build/xz-utils-5.2.4'
make[1]: *** [debian/rules:4: install] Error 2
make[1]: Leaving directory '/build/xz-utils-5.2.4'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.2.5-1.0
Done: Sebastian Andrzej Siewior 

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
xz-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Dec 2020 11:25:06 +0100
Source: xz-utils
Architecture: source
Version: 5.2.5-1.0
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Nieder 
Changed-By: Sebastian Andrzej Siewior 
Closes: 844770 894454 907449 945961 95 970891 975981 975984
Changes:
 xz-utils (5.2.5-1.0) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #975984).
 - Increase GETTEXT version (Closes: #95).
   * Add % target to the rules file to work with newer debhelper
 (Closes: #945961).
   * Enable threads for static builds (Closes: #907449).
   * Ignore SIGPIPE in xzdiff script (Closes: #844770).
   * Teach xzgrep about zstd (Closes: #970891).
   * Clean up the xz man page (Closes: #894454).
   * Ignore hard link count if input is not deleted (Closes: #975981).
Checksums-Sha1:
 35ea5b35d0b52f1eededba28120109f0002cf066 2527 xz-utils_5.2.5-1.0.dsc
 0b9d1e06b59f7fe0796afe1d93851b9306b4a3b6 1148824 xz-utils_5.2.5.orig.tar.xz
 603dd6d6ac39e20b3d1e79f2ead99d060b07c6e2 833 xz-utils_5.2.5.orig.tar.xz.asc
 68b7dc4c4fdfd990fcec35d8912677ffd9c00b9d 31636 xz-utils_5.2.5-1.0.debian.tar.xz
Checksums-Sha256:
 21fef59fb4b1ee054f5a29830e7e1416348c3a56cf24efbb422eefebbcbe094d 2527 
xz-utils_5.2.5-1.0.dsc
 3e1e518ffc912f86608a8cb35e4bd41ad1aec210df2a47aaa1f95e7f5576ef56 1148824 
xz-utils_5.2.5.orig.tar.xz
 6efc0075a58912e640119d2b52ef7d1518b260d8720fadc73df21ab7fc727624 833 
xz-utils_5.2.5.orig.tar.xz.asc
 163c5236a25cc8432fe6c2785c4c66916ea71e1e966130492bbe34f9a1ee679a 31636 
xz-utils_5.2.5-1.0.debian.tar.xz
Files:
 02a2dac614214b87e22730fb05b69d19 2527 utils optional xz-utils_5.2.5

Processed: Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Severity set to 'normal' from 'serious'

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

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Sebastian Ramacher]

Control: severity -1 normal

On 2021-01-01 11:17:38 +0100, Sebastiaan Couwenberg wrote:
> Control: tags -1 - moreinfo
> 
> On 1/1/21 10:09 AM, Sebastian Ramacher wrote:
> > On 2020-12-31 16:28:40 +0100, Sebastiaan Couwenberg wrote:
> >> On 12/31/20 4:13 PM, Daniele Tricoli wrote:
> >>> On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
>  Package: chardet
>  Version: 4.0.0-1
>  Severity: serious
>  Justification: makes the package in question unusable or mostly so
>  Control: affects -1 src:requests src:qgis
> 
>  Dear Maintainer,
> 
>  Upgrading python3-chardet causes the removal of many packages:
> 
>   The following packages will be REMOVED:
> chrome-gnome-shell gnome-music pycsw pycsw-wsgi 
>  python3-astropy-helpers python3-boto3 python3-botocore 
>  python3-cupshelpers python3-gitlab python3-numpydoc python3-owslib 
>  python3-plotly python3-pycsw python3-pywps python3-qgis
> python3-reportbug python3-requests python3-requests-oauthlib 
>  python3-s3transfer python3-sphinx python3-sphinx-astropy 
>  python3-sphinx-automodapi python3-sphinx-gallery pywps qgis 
>  qgis-plugin-grass reportbug system-config-printer
> system-config-printer-common system-config-printer-udev 
>  torbrowser-launcher
>   The following packages will be upgraded:
> python3-chardet
>   1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> 
>  python3-requests does not support version 3.1.0 or higher:
> 
>    python3-chardet (<< 3.1.0)
> 
>  With the freeze coming in a few months it may be wise to revert back to 
>  3.0.x for bullseye.
> 
>  Otherwise the python3-chardet rdeps need to fixed before that time.
> >>>
> >>> As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 
> >>> which
> >>> fix the problem, but there was a time window during the propagation of 
> >>> the new
> >>> version when the problem was reproducible.
> >>
> >> Thanks for quickly acting on this, but the problem is not limited to
> >> python3-requests. Several other reverse dependencies need to be updated
> >> for the new chardet as well. The autopkgtest failures include some of them:
> >>
> >>  https://qa.debian.org/excuses.php?package=chardet
> > 
> > Do you have specific packages in mind? All autopkgtests passed and no
> > other reverse depedency has upper bounds on the version on chardet. With
> > requests fixed, all others that you marked as affected are installable 
> > again.
> 
> The autopkgtests that failed before due to requests succeeded after they
> were retried with the new requests.
> 
> symver suggests that chardet 4 broke its API, so the other reverse
> dependencies should be tested to ensure they still work with the new
> chardet.

It didn't. It dropped support for old Python versions, added new
functions and reformatted a bunch of code.

> 
> python3-requests did that and resolved the issue for the packages I care
> about.
> 
> Not all of the python3-chardet rdeps have autopkgtest so that alone is
> not an indicator that nothing is broken any more.

Well, then let's downgrade the bug. Breakage in some reverse
dependencies without any evidence is not enough for an RC bug. So far
the only issue was python3-requests having overly strict version
constraints.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

[Michel Le Bihan]

Hello

Le vendredi 01 janvier 2021 à 02:53 +0100, Christoph Anton Mitterer a
écrit :
> Hey.
> 
> 
> Just wondered:
> 
> 
> 1) Since this is a binary blob who, by it's nature, is made for
> surveillance, it's IMO more a rather serious security issue than just
> a
> DFSG-policy problem.
> No one really knows what exactly Google ships there.
> 
> So maybe people should be told about this more actively in a DSA or
> NEWS.Debian entry?
> 
> 
> 
> 2) To my great surprise (and shock - due to the compromise) I found
> the
> binaries downloaded last July, even though I never used chromium on
> any
> site that uses EME or things like that.
> Which makes this behaviour even more suspicious.
> 
> 
It is downloaded on launch and not when visiting a site that requires
DRM.
> 
> 3) AFAIU, now the Debian package no longer downloads it automatically
> (with widevine-cdm-cu.patch), but many people will still have it
> silently in place (and presumably executed). Which is again kinda a
> point for (1).
> 
> 
That's actually intended. It would be easier to set the build flag that
disables it, but some users are still interested in using it. The way
it's done currently still allows them to use it.
> 
> 4) This problem of browsers downloading their own closed-source and
> possibly compromised stuff has already surfaced in the past.
> Wouldn't it be safer to completely remove the code doing at all?
> Right now we have widevine-cdm-cu.patch which is fine for just this,
> and as soon as Google would add something new it would probably get
> downloaded&executed again until someone notices by chance.
> 
> 
> In general, I think it's pretty bad if software circumvents secure
> APT
> do download further software:
> 
> - there is no central security support (just imagine an attacked
> simply
> blocks any time chromium tries to upgrade the binary blobs) and
> people will not even notice if upgrades from within the software
> fail.
> 
> - it's not taken into account by tools like check_apt either
> 
> - unless someone knows that Chromium puts software in .config it will
> stay there forever and not begin removed or so when the chromium
> package would be removed
> 
> - an evil Google could just selectively distribute hacked versions of
> their binaries - something which is more or less impossible when all
> software comes via secure APT
> 
> - doing package upgrade really in a secure way (i.e. preventing
> blocking attacks, downgrade attacks, or just not using
> outdated/insecure algorithms) is actually not that easy and I've seen
> many downloader packages doing it wrong - with secure APT there's one
> central place where all this is handled (securely)
> 
> 
> 
> Cheers,
> Chris.
> 
Michel Le Bihan

Processed: igraph: FTBFS on mips64el: test 229 randomly fails on mips64el arch

[Debian Bug Tracking System]

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

> reopen #970497 !
Bug #970497 {Done: Jerome BENOIT } [src:igraph] igraph: 
FTBFS on mips64el
Bug reopened
Changed Bug submitter to 'calcu...@rezozer.net' from 'Andreas Tille 
'.
Ignoring request to alter fixed versions of bug #970497 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#978963: marked as done (reportbug: Debian 10 system freezes. I can't find a record of the time it freezes in the syslog file.)

[Debian Bug Tracking System]

Your message dated Fri, 1 Jan 2021 12:03:03 +0100
with message-id <2950ab75-c8f4-6ee4-fb18-5a43e5462...@web.de>
and subject line Re: Bug#978963: reportbug: Debian 10 system freezes. I can't 
find a record of the time it freezes in the syslog file.
has caused the Debian Bug report #978963,
regarding reportbug: Debian 10 system freezes. I can't find a record of the 
time it freezes in the syslog file.
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.)


-- 
978963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.5.3~deb10u1
Severity: serious
Justification: must


* The system freezes during any operation. For example, during online meeting,
copying, file editing. Sometimes the system becomes extremely slow before the
freeze occurs. For example, the mouse pointer moves very slowly. In such a
case, when I tried to shut down the system with desktop environment, the system
froze again.

In the syslog file, I came across lines like the following;
interrupt took too long ...
kernel: [38221.708510] hrtimer: interrupt took 4980511 ns
e.g.

* I tested the system with or without an external disk attached to the system,
with the web cam off.

I organized the Grub as follows.
GRUB_CMDLINE_LINUX_DEFAULT = "quiet intel_idle.max_cstate = 1"

I tried removing the SSD disk and using the system via USB stick. But in this
case, the system freeze occurred.

I've tried Nvidia drivers instead of Nouveau.

* Despite all my attempts, I could not solve the freezing problem. I could not
find any data on the time the freezing problem occurred in the syslog records.

* CPU: Intel Core 2 Duo T7500 - GPU: Nvidia Geforce 8600M GS




-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/konuk/.reportbugrc:
reportbug_version "7.5.3~deb10u1"
mode standard
ui gtk
realname "Serkan"
email "ssser...@yahoo.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

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

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

Versions of packages reportbug depends on:
ii  apt1.8.2.2
ii  python33.7.3-1
ii  python3-reportbug  7.5.3~deb10u1
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail  
pn  debconf-utils   
pn  debsums 
pn  dlocate 
pn  emacs-bin-common
ii  file1:5.35-4+deb10u1
ii  gnupg   2.2.12-1+deb10u1
pn  postfix | exim4 | mail-transport-agent  
pn  python3-urwid   
ii  reportbug-gtk   7.5.3~deb10u1
ii  xdg-utils   1.1.3-1+deb10u1

Versions of packages python3-reportbug depends on:
ii  apt1.8.2.2
ii  file   1:5.35-4+deb10u1
ii  python33.7.3-1
ii  python3-apt1.8.4.3
ii  python3-debian 0.1.35
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1
ii  sensible-utils 0.0.12

python3-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On 01.01.2021 11.16, Serkan wrote:
> Package: reportbug
> Version: 7.5.3~deb10u1
> Severity: serious
> Justification: must
> 
> * The system freezes during any operation. For example, during online meeting,
> copying, file editing. Sometimes the system becomes extremely slow before the
> freeze occurs. For example, the mouse pointer moves very slowly. In such a
> case, when I tried to shut down the system with desktop environment, the 
> system
> froze again.

You filed this bug against the reportbug package, which is Debian's
helper tool to facilitate bug reporting, and not what you intended.
Since we cannot help you here, I'm closing this report.

You are more likely to receive helpful feedback if you file a bug
against the correct package, which in your case probably is the kernel
you are running. Reportbug will support you in identifying the running
kernel's package and in collecting potentially relevant system
information for the report, just run 

Bug#978277: marked as done (pytest-flask: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 11:03:42 +
with message-id 
and subject line Bug#978277: fixed in pytest-flask 0.15.1-2
has caused the Debian Bug report #978277,
regarding pytest-flask: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
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.)


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

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pytest-flask
> dpkg-buildpackage: info: source version 0.15.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ondřej Nový 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> pytest-flask-0.15.1/debian/source/options: 
> --extend-diff-ignore=^[^/]+.egg-info/
>  debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_pytest-flask/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> pytest-flask-0.15.1/debian/source/options: 
> --extend-diff-ignore=^[^/]+.egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pytest-flask using existing 
> ./pytest-flask_0.15.1.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  pytest-flask-0.15.1/pytest_flask/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/pytest-flask_0.15.1-1.diff.EPV7ca
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:36:40Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/pytest-flask_0.15.1-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!

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

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pytest-flask
Source-Version: 0.15.1-2
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated pytest-flask package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 13:43:24 +0530
Source: pytest-flask
Architecture: source
Version: 0.15.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Nilesh Patra 
Closes: 978277
Changes:
 pytest-flask (0.15.1-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 co

Processed: Re: Bug#947272: blt builds fine with gcc-10

[Debian Bug Tracking System]

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

> severity 947272 important
Bug #947272 [src:blt] blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error: argument 
'argv' doesn't match prototype
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#947272: blt builds fine with gcc-10

[Sergei Golovan]

severity 947272 important
thanks

Hi Holger,

On Wed, Dec 30, 2020 at 9:27 PM Holger Levsen  wrote:
>
> On Wed, Dec 30, 2020 at 06:36:23PM +0300, Sergei Golovan wrote:
> > There isn't Tcl/Tk 8.7 in unstable yet, only an alpha in experimantal.
> > After the Tcl/Tk 8.7 will be released, I'll deal with this bug in
> > unstable.
>
> ah, ok, makes sense.
>
> probably it would still be nicer to downgrade this bug to severity important
> until that tcl/tk version has reached unstable.

You're right. Currently this bug does not have any impact on the
bullseye release.
I'm downgrading its severity.

-- 
Sergei Golovan

Processed: Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Removed tag(s) moreinfo.

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

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Sebastiaan Couwenberg]

Control: tags -1 - moreinfo

On 1/1/21 10:09 AM, Sebastian Ramacher wrote:
> On 2020-12-31 16:28:40 +0100, Sebastiaan Couwenberg wrote:
>> On 12/31/20 4:13 PM, Daniele Tricoli wrote:
>>> On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
 Package: chardet
 Version: 4.0.0-1
 Severity: serious
 Justification: makes the package in question unusable or mostly so
 Control: affects -1 src:requests src:qgis

 Dear Maintainer,

 Upgrading python3-chardet causes the removal of many packages:

  The following packages will be REMOVED:
chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
 python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
 python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
 python3-qgis
python3-reportbug python3-requests python3-requests-oauthlib 
 python3-s3transfer python3-sphinx python3-sphinx-astropy 
 python3-sphinx-automodapi python3-sphinx-gallery pywps qgis 
 qgis-plugin-grass reportbug system-config-printer
system-config-printer-common system-config-printer-udev 
 torbrowser-launcher
  The following packages will be upgraded:
python3-chardet
  1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.

 python3-requests does not support version 3.1.0 or higher:

   python3-chardet (<< 3.1.0)

 With the freeze coming in a few months it may be wise to revert back to 
 3.0.x for bullseye.

 Otherwise the python3-chardet rdeps need to fixed before that time.
>>>
>>> As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 
>>> which
>>> fix the problem, but there was a time window during the propagation of the 
>>> new
>>> version when the problem was reproducible.
>>
>> Thanks for quickly acting on this, but the problem is not limited to
>> python3-requests. Several other reverse dependencies need to be updated
>> for the new chardet as well. The autopkgtest failures include some of them:
>>
>>  https://qa.debian.org/excuses.php?package=chardet
> 
> Do you have specific packages in mind? All autopkgtests passed and no
> other reverse depedency has upper bounds on the version on chardet. With
> requests fixed, all others that you marked as affected are installable again.

The autopkgtests that failed before due to requests succeeded after they
were retried with the new requests.

symver suggests that chardet 4 broke its API, so the other reverse
dependencies should be tested to ensure they still work with the new
chardet.

python3-requests did that and resolved the issue for the packages I care
about.

Not all of the python3-chardet rdeps have autopkgtest so that alone is
not an indicator that nothing is broken any more.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#978960: python-azure's autopkg tests fail

[Matthias Klose]

Package: src:python-azure
Version: 20201208+git-2
Severity: serious
Tags: sid bullseye

python-azure's autopkg tests fail, blocking the migration of python3-defaults:

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

[...]
- Captured stdout call -
continue printing events
= 4 failed, 6 passed in 26.81 seconds ==
autopkgtest [05:09:30]: test python3-tests: ---]
autopkgtest [05:09:30]: test python3-tests:  - - - - - - - - - - results - - - -
- - - - - -
python3-testsFAIL non-zero exit status 1

Processed: Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Added tag(s) moreinfo.

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

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Sebastian Ramacher]

Control: tags -1 + moreinfo

Hi Bas

On 2020-12-31 16:28:40 +0100, Sebastiaan Couwenberg wrote:
> reopen 978739
> thanks
> 
> On 12/31/20 4:13 PM, Daniele Tricoli wrote:
> > On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
> >> Package: chardet
> >> Version: 4.0.0-1
> >> Severity: serious
> >> Justification: makes the package in question unusable or mostly so
> >> Control: affects -1 src:requests src:qgis
> >>
> >> Dear Maintainer,
> >>
> >> Upgrading python3-chardet causes the removal of many packages:
> >>
> >>  The following packages will be REMOVED:
> >>chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
> >> python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
> >> python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
> >> python3-qgis
> >>python3-reportbug python3-requests python3-requests-oauthlib 
> >> python3-s3transfer python3-sphinx python3-sphinx-astropy 
> >> python3-sphinx-automodapi python3-sphinx-gallery pywps qgis 
> >> qgis-plugin-grass reportbug system-config-printer
> >>system-config-printer-common system-config-printer-udev 
> >> torbrowser-launcher
> >>  The following packages will be upgraded:
> >>python3-chardet
> >>  1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> >>
> >> python3-requests does not support version 3.1.0 or higher:
> >>
> >>   python3-chardet (<< 3.1.0)
> >>
> >> With the freeze coming in a few months it may be wise to revert back to 
> >> 3.0.x for bullseye.
> >>
> >> Otherwise the python3-chardet rdeps need to fixed before that time.
> > 
> > As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 
> > which
> > fix the problem, but there was a time window during the propagation of the 
> > new
> > version when the problem was reproducible.
> 
> Thanks for quickly acting on this, but the problem is not limited to
> python3-requests. Several other reverse dependencies need to be updated
> for the new chardet as well. The autopkgtest failures include some of them:
> 
>  https://qa.debian.org/excuses.php?package=chardet

Do you have specific packages in mind? All autopkgtests passed and no
other reverse depedency has upper bounds on the version on chardet. With
requests fixed, all others that you marked as affected are installable again.

Cheers

> 
> > Happy new year!
> 
> The same to you!
> 
> Kind Regards,
> 
> Bas
> 
> -- 
>  GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#978477: marked as done (entropybroker: FTBFS on 32 bit architectures: error: narrowing conversion of ‘2147763207’ from ‘long unsigned int’ to ‘long int’ [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 08:33:51 +
with message-id 
and subject line Bug#978477: fixed in entropybroker 2.9-5
has caused the Debian Bug report #978477,
regarding entropybroker: FTBFS on 32 bit architectures: error: narrowing 
conversion of ‘2147763207’ from ‘long unsigned int’ to ‘long int’ [-Wnarrowing]
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.)


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

entropybroker FTBFS on 32 bit architectures:
| In file included from ComScire_R2000KU/qwqng.cpp:32:
| ComScire_R2000KU/qwqng.hpp:70:32: error: narrowing conversion of ‘2147763201’ 
from ‘long unsigned int’ to ‘long int’ [-Wnarrowing]
|70 | #define QNG_E_GENERAL_FAILURE  0x80044401L
|   |^~~
| ComScire_R2000KU/qwqng.cpp:786:7: note: in expansion of macro 
‘QNG_E_GENERAL_FAILURE’
|   786 |  case QNG_E_GENERAL_FAILURE:
|   |   ^

https://buildd.debian.org/status/fetch.php?pkg=entropybroker&arch=i386&ver=2.9-4&stamp=1609085617&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: entropybroker
Source-Version: 2.9-5
Done: Thorsten Alteholz 

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated entropybroker 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Dec 2020 13:25:00 +0100
Source: entropybroker
Architecture: source
Version: 2.9-5
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 978477
Changes:
 entropybroker (2.9-5) unstable; urgency=medium
 .
   * make it compile on 32bit archs again (Closes: #978477)
Checksums-Sha1:
 a345ce5f188e0c585547edb8da0516cc504c0e9e 2168 entropybroker_2.9-5.dsc
 5ac88c8cdf39da5e49fd5b08e07eec7d1ccacc16 19336 
entropybroker_2.9-5.debian.tar.xz
 c5c460c4648eb14579222171de5b9378d846e288 8797 
entropybroker_2.9-5_amd64.buildinfo
Checksums-Sha256:
 c6e74609e024bc035bc98eea79e8e20d48de733a8c1c8ff575f0ac13cf32 2168 
entropybroker_2.9-5.dsc
 ef659d40754970ffe85f6ccf5cb76009bea1e7b9d9d295086901b899c25353cc 19336 
entropybroker_2.9-5.debian.tar.xz
 cce42a9885453ebe922c8a83dcf8b3ccec7279cc2b66c4c16674a0781c893136 8797 
entropybroker_2.9-5_amd64.buildinfo
Files:
 491585a269b903d0d7268e3c9367a37c 2168 utils optional entropybroker_2.9-5.dsc
 1432fc21c0d1196cb688167d0c4aa702 19336 utils optional 
entropybroker_2.9-5.debian.tar.xz
 d0b37224e04fac7a76a50221bcdb4d0c 8797 utils optional 
entropybroker_2.9-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl/u2/xfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR2tUD/0WSVJqzX/5NGXE2LtT30dB7vzOtRb1
3lXRnn3THDaVt/G8cC1M39a506v4i3UqWCUpahtTx8CBuAmxpEiHfJM6MLKf77MT
0iBJQT7Naw0+QFBqw3SBryqv8ic5yrBU/6ePdGSTzQ4erMyOY1Wt077VHiJVb/kE
4IPMNAa3ZNS2TNJxS7BBxDMJ/gGSajTF1E4mhfue/XchkOkV7LfUrXm2tahKnDwT
S2FQBJ+Bh2y5/5JBAM/FaJ/rs0/bto85wzMsUOU/FpbPnOFA7kVzFzbxJ3mLRnKn
GqrWG9TJGxKU1r55L0IufTe39RrHQdKsmpTD+WXR9BjUwlhl7t/LRorUFnIUGdNo
HP66llSa1Q/i8L76j37xonO8RmuuL4PmQiVsfHZXNHnwysutm+KehBmbhcRABq8u
bcuh8fCBpZgg0inUKeyW/CmbRuo+h+8deaUmEwOIZVMzxdLM8clou3Hp952Tw0XZ
ao/6WXlJWi/Iu/1tEY3mmxHnKnKMJfu4MDiW+f3P5GUFo7i1hiySxHoEr+dl8qqx
7eka3uWeuIF7fxcVvnZpf09AYj65UQHJSBS2i5AsEbWx/3/17ahbgTiQUQQmcrmy
+X9BIhqt2AO0KGtOez5LbZ/8pD2yYg9/m3BuZeW3DY9SzC9slwf9oT35lgMyHzQK
264eexSnqeCgcg==
=GmWM
-END PGP SIGNATURE End Message ---

Bug#978952: wsjtx: No audio on transmit

[Hilary Snaden]

Package: wsjtx
Version: 2.3.0~rc2+repack-1+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: hilary.sna...@zoho.com

Dear Maintainer,

There is no audio output to any of the listed devices (I have tried them all). 
This was also the case with version 2.2.2,

Operation in receive mode is mostly satisfactory.

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

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

Versions of packages wsjtx depends on:
ii  hamradio-files 20201008
ii  libboost-log1.74.0 1.74.0-3+b1
ii  libboost-thread1.74.0  1.74.0-3+b1
ii  libc6  2.31-5
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  10.2.1-1
ii  libgfortran5   10.2.1-1
ii  libgomp1   10.2.1-1
ii  libhamlib-utils3.3-10+b4
ii  libhamlib2 3.3-10+b4
ii  libqcustomplot2.0  2.0.1+dfsg1-4
ii  libqt5core5a   5.15.2+dfsg-2
ii  libqt5gui5 5.15.2+dfsg-2
ii  libqt5multimedia5  5.15.2-2
ii  libqt5multimedia5-plugins  5.15.2-2
ii  libqt5network5 5.15.2+dfsg-2
ii  libqt5serialport5  5.15.2-2
ii  libqt5sql5 5.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-2
ii  libstdc++6 10.2.1-1
ii  wsjtx-data 2.3.0~rc2+repack-1

Versions of packages wsjtx recommends:
ii  wsjtx-doc  2.3.0~rc2+repack-1

wsjtx suggests no packages.

-- no debconf information