Bug#956987: marked as done (afnix: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 26 Dec 2020 07:33:21 +
with message-id 
and subject line Bug#956987: fixed in afnix 3.3.0-1
has caused the Debian Bug report #956987,
regarding afnix: 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.)


-- 
956987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:afnix
Version: 2.9.2-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/afnix_2.9.2-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

[...]
make[6]: Entering directory '/<>/prj/std/sps/src'
make[6]: Leaving directory '/<>/prj/std/sps/src'
make[5]: Leaving directory '/<>/prj/std/sps'
make[5]: Entering directory '/<>/prj/std/tls'
make[6]: Entering directory '/<>/prj/std/tls/src'
make[6]: Leaving directory '/<>/prj/std/tls/src'
make[5]: Leaving directory '/<>/prj/std/tls'
make[4]: Leaving directory '/<>/prj/std'
make[3]: Leaving directory '/<>/prj'
make[3]: Entering directory '/<>/tst'
make[4]: Entering directory '/<>/tst/ref'
make[4]: Leaving directory '/<>/tst/ref'
make[4]: Entering directory '/<>/tst/mod'
make[4]: Leaving directory '/<>/tst/mod'
make[3]: Leaving directory '/<>/tst'
make[3]: Entering directory '/<>/exp'
make[4]: Entering directory '/<>/exp/ref'
make[4]: Leaving directory '/<>/exp/ref'
make[4]: Entering directory '/<>/exp/api'
make[4]: Leaving directory '/<>/exp/api'
make[4]: Entering directory '/<>/exp/prj'
make[5]: Entering directory '/<>/exp/prj/amd'
make[6]: Entering directory '/<>/exp/prj/amd/src'
make[7]: Entering directory '/<>/exp/prj/amd/src/app'
make[7]: Leaving directory '/<>/exp/prj/amd/src/app'
make[7]: Entering directory '/<>/exp/prj/amd/src/tst'
make[7]: Leaving directory '/<>/exp/prj/amd/src/tst'
make[6]: Leaving directory '/<>/exp/prj/amd/src'
make[6]: Entering directory '/<>/exp/prj/amd/doc'
make[6]: Leaving directory '/<>/exp/prj/amd/doc'
make[5]: Leaving directory '/<>/exp/prj/amd'
make[4]: Leaving directory '/<>/exp/prj'
make[3]: Leaving directory '/<>/exp'
make[3]: Entering directory '/<>/doc'
make[4]: Entering directory '/<>/doc/dtd'
make[4]: Leaving directory '/<>/doc/dtd'
make[4]: Entering directory '/<>/doc/etc'
make[4]: Leaving directory '/<>/doc/etc'
make[4]: Entering directory '/<>/doc/xml'
make[5]: Entering directory '/<>/doc/xml/eul'
make[5]: Leaving directory '/<>/doc/xml/eul'
make[5]: Entering directory '/<>/doc/xml/vol'
make[6]: Entering directory '/<>/doc/xml/vol/vol-0'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-0'
make[6]: Entering directory '/<>/doc/xml/vol/vol-1'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-1'
make[6]: Entering directory '/<>/doc/xml/vol/vol-2'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-2'
make[5]: Leaving directory '/<>/doc/xml/vol'
make[4]: Leaving directory '/<>/doc/xml'
make[3]: Leaving directory '/<>/doc'
make[3]: Entering directory '/<>/etc'
make[3]: Leaving directory '/<>/etc'
make[2]: Leaving directory '/<>'
rm -rf bld
dh_clean
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./cnf/bin/afnix-setup -o --prefix=/usr
afnix-setup: cannot find compiler file error: cannot find version for compiler 
gcc
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build] Error 2
dpkg-buildpackage: error: debian/rules 

Bug#974949: marked as done (systray-mdstat: fails to start with org.freedesktop.DBus.Error.ServiceUnknown)

[Debian Bug Tracking System]

Your message dated Sat, 26 Dec 2020 07:33:55 +
with message-id 
and subject line Bug#974949: fixed in systray-mdstat 1.2.0-2
has caused the Debian Bug report #974949,
regarding systray-mdstat: fails to start with 
org.freedesktop.DBus.Error.ServiceUnknown
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.)


-- 
974949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systray-mdstat
Version: 1.2.0-1
Severity: grave
Justification: renders package unusable

Hello,
I've just given the new version from unstable a try.

It seems to completely fail to start:

  $ systray-mdstat &
  [1] 64881
  $ org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Notifications was not provided by any .service files
  
  [1]+  Exit 11 systray-mdstat

This seems to render the package unusable.
I am setting grave severity accordingly: this should prevent migration
to testing, until the bug is fixed.

Please investigate and fix the bug.
Thanks!


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

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

Versions of packages systray-mdstat depends on:
ii  libdesktop-notify-perl  0.05-2
ii  libfile-sharedir-perl   1.118-1
ii  libgtk3-perl0.037-1
ii  libtry-tiny-perl0.30-1
ii  perl5.30.3-4

systray-mdstat recommends no packages.

Versions of packages systray-mdstat suggests:
ii  fbpanel 7.0-4+b1
pn  smart-notifier  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systray-mdstat
Source-Version: 1.2.0-2
Done: Axel Beckert 

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated systray-mdstat 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, 26 Dec 2020 08:08:20 +0100
Source: systray-mdstat
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Closes: 974949
Changes:
 systray-mdstat (1.2.0-2) unstable; urgency=medium
 .
   * Remove redundant debian/tests/control again. We were already and still
 are using "Testsuite: autopkgtest-pkg-perl". Duh.
   * Declare compliance with Debian Policy 4.5.1. (No changes needed.)
   * Add hard dependency on virtual package notification-daemon.
 + Mention in README.Debian that not all notification-daemon
   implementations start up automatically upon user login.
 + Closes: #974949
Checksums-Sha1:
 e9a166379dd2881bf62ea90c4867f9bf2a406167 2806 systray-mdstat_1.2.0-2.dsc
 f5d3d7af57cf0367f9469841fd336f7c098c3d6b 15528 
systray-mdstat_1.2.0-2.debian.tar.xz
 1b9f77c0e402b91f6e857510d774e2b050f67f65 20516 
systray-mdstat_1.2.0-2_source.buildinfo
Checksums-Sha256:
 bdf014c0e95291569b39b5ca8c2a7bedf91fa2666f496bc61c5941547e0e3401 2806 
systray-mdstat_1.2.0-2.dsc
 c479c5cfeba25d2e9064ffbabdbc7fbd5d68b922fc0d824fa201304e2eb0e954 15528 
systray-mdstat_1.2.0-2.debian.tar.xz
 8cc17203c516c0f1d7f2544f392564b246b2b4781627b50d656be9c1d3cbd6a7 20516 
systray-mdstat_1.2.0-2_source.buildinfo
Files:
 30ebeb622065296f1d6a4a1479234f16 2806 utils optional systray-mdstat_1.2.0-2.dsc
 20090332361ac9549a369d35e3bc535c 15528 utils optional 
systray-mdstat_1.2.0-2.debian.tar.xz
 b27fec1265ad7c62df0a4850588e47d5 20516 utils optional 
systray-mdstat_1.2.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAl/m4fMACgkQa+Zjx1o1
yXW8iw/7BfMhCygwOzZtKKzz7xByp8TKQbhe97WV+NwyuRGOcEc//yegrzsnQ4cO
yOfUNt//omUCLkGYQwm3VFyPNSidxHq0z3MOSgIlqycuaE1W6ZQP+mzKr1coBE4/
sLXX/t4QAckZRNIzinfbShaQcPX303WjdarjSGkSjz+zMtSqpjmmnfojeSBfg6iQ

Processed: tagging 974949

[Debian Bug Tracking System]

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

> tags 974949 + pending
Bug #974949 [systray-mdstat] systray-mdstat: fails to start with 
org.freedesktop.DBus.Error.ServiceUnknown
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#978104: dh-make-elpa: Can't locate object method "home_dir" via package "DhMakeELPA::Config" at /usr/share/perl5/DhMakeELPA/Command/Packaging.pm line 387.

[Axel Beckert]

Package: dh-make-elpa
Version: 0.19
Severity: grave
Tags: patch

Hi,

when trying to use dh-make-elpa, it aborts for me as follows:

$ dh-make-elpa --pkg-emacsen --version="1+24+gc830b9d"
I: couldn't generate d/docs: not fully implemented
Can't locate object method "home_dir" via package "DhMakeELPA::Config" at 
/usr/share/perl5/DhMakeELPA/Command/Packaging.pm line 387.

Exit code is 25.

I suspect that the actually trying to be packaged mode doesn't make a
difference here, but for the sake of completeness: This happened during
trying to package https://github.com/mickeynp/ligature.el.

Since home_dir seems to be a hash key and not a method, I tried to
enclose it in curly brackets. Then it bails out on the next word. In the
end I also had to fix these errors, too, to get it running until the
end:

Can't locate object method "data_dir" via package "DhMakeELPA::Config" at 
/usr/share/perl5/DhMakeELPA/Command/Packaging.pm line 387.
Can't locate object method "verbose" via package "DhMakeELPA::Config" at 
/usr/share/perl5/DhMakeELPA/Command/Packaging.pm line 392.

My first try was to convert the function calls to hash accesses. Which
seems to have worked.

So I looked through perl5320delta(1) to see if there was a change in
Perl which could trigger this, but found none on a first glance.

Then I checked the dh-make-perl code to see if the same code is in
there, too. And it is. So I checked which code is different and in the
end I figured that (probably with the separation from dh-make-perl) too
much code has been removed from dh-make-elpa compared to
dh-make-perl. More precisely, re-adding these options (!) fixed it as in
the call to __PACKAGE__->mk_accessors accessors are generated from the
configured options. Here's the patch:

--- /usr/share/perl5/DhMakeELPA/Config.pm.BACKUP2020-06-25 
20:22:12.0 +0200
+++ /usr/share/perl5/DhMakeELPA/Config.pm   2020-12-26 03:56:47.075818430 
+0100
@@ -16,9 +16,12 @@
 
 my @OPTIONS = (
 'backups!',
+'data-dir=s',
 'dh=i',
+'home-dir=s',
 'network!',
 'pkg-emacsen!',
+'verbose!',
 'version=s'
 );
 

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

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

Versions of packages dh-make-elpa depends on:
ii  dh-elpa 2.0.6
ii  libarray-utils-perl 0.5-1
ii  libdebian-source-perl   0.113
ii  libfile-find-rule-perl  0.34-1
ii  libfile-grep-perl   0.02-1
ii  libgit-repository-perl  1.324-1
ii  libtrycatch-perl1.003002-2+b7
ii  perl5.32.0-6

Versions of packages dh-make-elpa recommends:
ii  devscripts  2.20.5

dh-make-elpa suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/perl5/DhMakeELPA/Command/Packaging.pm (from 
dh-make-elpa package)

Bug#973228: (no subject)

[Paul Aguilar]

Hey buddy 
Sent from my iPhone

Bug#975535: elpy's autopkg tests fail with Python 3.9

[Nicholas D Steeves]

Hi Matthias,

On Mon, Nov 23, 2020 at 11:21:29AM +0100, Matthias Klose wrote:
> Package: src:elpy
> Version: 1.34.0-2
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/e/elpy/8349971/log.gz
> 
> [...]
> Ran 436 tests, 432 results as expected, 3 unexpected, 1 skipped (2020-11-22
> 10:13:43+, 71.268224 sec)
> 
> 3 unexpected results:
>FAILED  elpy-company-backend-should-add-shell-candidates
>FAILED  elpy-fold-at-point-should-fold-and-unfold-comments
>FAILED  elpy-pdb-debug-buffer-should-ignore-breakpoints
> 
> 1 skipped results:
>   SKIPPED  elpy-shell-send-region-or-buffer-should-notify-of-removing-main

I've made progress with this, and encountered a couple blockers along
the way (one outstanding at this time).  Currently the need for Jedi
0.18 means the work in git (Elpy 1.35 minus rope, plus cherrypicked
support for Jedi refactoring) cannot yet be uploaded.

One nice thing about all this: it was good to have a high priority
practice reason to enhance Elpy's packaging and test output for more
complete and useful debugging output.

Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: block 975535 with 977931

[Debian Bug Tracking System]

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

> block 975535 with 977931
Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9
975535 was blocked by: 977558 977563
975535 was not blocking any bugs.
Added blocking bug(s) of 975535: 977931
> thanks
Stopping processing here.

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

Processed: Re: ddccontrol: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ddccontrol/ddccontrol/issues/74 
> https://github.com/ddccontrol/ddccontrol/pull/80
Bug #957127 [src:ddccontrol] ddccontrol: ftbfs with GCC-10
Set Bug forwarded-to-address to 
'https://github.com/ddccontrol/ddccontrol/issues/74 
https://github.com/ddccontrol/ddccontrol/pull/80'.
> tags -1 + fixed-upstream patch
Bug #957127 [src:ddccontrol] ddccontrol: ftbfs with GCC-10
Added tag(s) patch and fixed-upstream.

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

Bug#957127: ddccontrol: ftbfs with GCC-10

[Paul Wise]

Control: forwarded -1 https://github.com/ddccontrol/ddccontrol/issues/74 
https://github.com/ddccontrol/ddccontrol/pull/80
Control: tags -1 + fixed-upstream patch

On Fri, 17 Apr 2020 10:58:40 + Matthias Klose wrote:

> 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.

This issue has been reported and fixed upstream so a patch is available:

https://github.com/ddccontrol/ddccontrol/issues/74
https://github.com/ddccontrol/ddccontrol/pull/80

In addition I have requested a new release of ddccontrol:

https://github.com/ddccontrol/ddccontrol/issues/87

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#975065: marked as done (broker: FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 26 Dec 2020 00:17:01 +0100
with message-id <87r1ndqxw2@msgid.hilluzination.de>
and subject line FTBFS fixed in 1.4.0+ds1-1
has caused the Debian Bug report #975065,
regarding broker: 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.)


-- 
975065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: broker
Version: 1.2.8+ds1-1
Severity: important

Dear Maintainer,

fails to build from source, as if pybind/python bindings are failing
to compile with very large and long c++ error messages from a single
translation unit.

Possibly pybind incompatibility?

Regards,

Dimitri.
--- End Message ---
--- Begin Message ---
control: fixed -1 1.4.0+ds1-1

Just uploaded broker/1.4.0+ds1-1 which builds fine in my unstable
chroot environment.

Cheers,
-Hilko--- End Message ---

Processed: affects

[Debian Bug Tracking System]

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

> affects 978022 src:petsc src:mumps src:dolfin src:dolfinx
Bug #978022 [libopenmpi3] libopenmpi3 Runtime failure opal_pmix_base_select 
failed
Added indication that 978022 affects src:petsc, src:mumps, src:dolfin, and 
src:dolfinx
> thanks
Stopping processing here.

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

Bug#976134: marked as done (vorta: flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 22:49:47 +
with message-id 
and subject line Bug#976134: fixed in vorta 0.7.1-3
has caused the Debian Bug report #976134,
regarding vorta: flaky autopkgtest
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.)


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

Hi Maintainer

The autopkgtests of vorta are failing often.  Two of the failures
[1][2] seem to be a time out, but there may be other problems as well.
I've copied what I hope is the relevant part of these logs below.

Regards
Graham


[1] https://ci.debian.net/data/autopkgtest/testing/arm64/v/vorta/8520699/log.gz
[2] https://ci.debian.net/data/autopkgtest/testing/i386/v/vorta/8521042/log.gz


=== FAILURES ===
_ test_archive_extract _

qapp = 
qtbot = 
mocker = 
borg_json_output = ._read_json at
0xb4c3cc10>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0xaf6a7a90>

def test_archive_extract(qapp, qtbot, mocker, borg_json_output,
monkeypatch):
main = qapp.main_window
tab = main.archiveTab
main.tabWidget.setCurrentIndex(3)

tab.populate_from_profile()
qtbot.waitUntil(lambda: tab.archiveTable.rowCount() == 2)

monkeypatch.setattr(
vorta.views.extract_dialog.ExtractDialog, "exec_", lambda
*args: True
)

tab.archiveTable.selectRow(0)
stdout, stderr = borg_json_output('list_archive')
popen_result = mocker.MagicMock(stdout=stdout, stderr=stderr,
returncode=0)
mocker.patch.object(vorta.borg.borg_thread, 'Popen',
return_value=popen_result)
qtbot.mouseClick(tab.extractButton, QtCore.Qt.LeftButton)

>   qtbot.waitUntil(lambda: hasattr(tab, '_window'), timeout=1)
E   AssertionError: waitUntil timed out in 1 miliseconds

tests/test_archives.py:129: AssertionError
--- End Message ---
--- Begin Message ---
Source: vorta
Source-Version: 0.7.1-3
Done: Nicholas D Steeves 

We believe that the bug you reported is fixed in the latest version of
vorta, 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.
Nicholas D Steeves  (supplier of updated vorta 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, 25 Dec 2020 17:26:40 -0500
Source: vorta
Architecture: source
Version: 0.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Nicholas D Steeves 
Closes: 976134
Changes:
 vorta (0.7.1-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Nicholas D Steeves ]
   * Minor enhancements to long description.
   * Add 0010-Increase-timeouts-for-all-self-tests.patch (Closes: #976134).
Checksums-Sha1:
 8f6397992155ba39c837f612472c6929c34fe190 2692 vorta_0.7.1-3.dsc
 48b2860bd136e0f1fd50b3e452dae3a431b8765f 8736 vorta_0.7.1-3.debian.tar.xz
 05d53dd6de20f035a68cb4f0e797c4d635af4569 13710 vorta_0.7.1-3_amd64.buildinfo
Checksums-Sha256:
 1fd157278d81cf89701d1d9429ac9b9f6e50bb16d3df69b2ff50d881e69eb656 2692 
vorta_0.7.1-3.dsc
 ef7d8a46dd032356a705be62673e95b542125312778281c8fca74406ce437a50 8736 
vorta_0.7.1-3.debian.tar.xz
 c0dcc7f04a46bd68d0c10e0f170a6bb9812bceaa00ec4c23a950dc3f536f793d 13710 
vorta_0.7.1-3_amd64.buildinfo
Files:
 0a0159a64a0563a591e380cd94fd7582 2692 utils optional vorta_0.7.1-3.dsc
 0de3c1339719d0452785cd8b485a2cc4 8736 utils optional 
vorta_0.7.1-3.debian.tar.xz
 a98e7962fc2181ac3a17016b10077492 13710 utils optional 
vorta_0.7.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZ39U8fqGga2OwLzmeurE7GqqCpcFAl/maJIACgkQeurE7Gqq
CpflWRAAueYxuz6IBcPV3DXC1sfbXi4HZrDqyNayeleBvNoR+EfKoIRFkxtMinQ5
dPllSqPFGrrAiGWg4QOJ5Ii5f2AxReK19jx7Y5Hn41MuCeCrPBIVce5vsyuWE5Iy

Bug#978100: libreoffice-parlatype: missing Breaks+Replaces: parlatype-libreoffice-helpers (<< 2)

[Andreas Beckmann]

Package: libreoffice-parlatype
Version: 2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libreoffice-parlatype_2.1-1_all.deb ...
  Unpacking libreoffice-parlatype (2.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-parlatype_2.1-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/libreoffice/share/Scripts/python/Parlatype.py', which is also in 
package parlatype-libreoffice-helpers 1.6.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libreoffice-parlatype_2.1-1_all.deb

The existing
  Breaks+Replaces: parlatype-libreoffice-helpers (<= 1.6.2)
are insufficient, the package was dropped in the parlatype 2.0-1 upload.

cheers,

Andreas


parlatype-libreoffice-helpers=1.6.2-1_libreoffice-parlatype=2.1-1.log.gz
Description: application/gzip

Bug#978097: libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 2.4.1-2 ???)

[Andreas Beckmann]

Package: libcpu-features-dev
Version: 0.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block -1 with 978096

Hi,

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

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

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

  Preparing to unpack .../libcpu-features-dev_0.6.0-1+b1_amd64.deb ...
  Unpacking libcpu-features-dev (0.6.0-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/cpu_features/cpu_features_cache_info.h', 
which is also in package libvolk2-dev:amd64 2.4.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb
 
src:volk seems to use an embedded copy of libcpu-features-dev and ships it
in libvolk2-dev. I've requested that to be dropped in #978096, but as long
as this has not happened the version libcpu-features-dev should use in the
to-be-added Breaks+Replaces is only a guess.


cheers,

Andreas


libvolk2-dev=2.4.1-1_libcpu-features-dev=0.6.0-1+b1.log.gz
Description: application/gzip

Processed: libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 2.4.1-2 ???)

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 978096
Bug #978097 [libcpu-features-dev] libcpu-features-dev: missing Breaks+Replaces: 
libvolk2-dev (<< 2.4.1-2 ???)
978097 was not blocked by any bugs.
978097 was not blocking any bugs.
Added blocking bug(s) of 978097: 978096

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

Bug#978096: libvolk2-dev: /usr/include/cpu_features/*.h is now packaged separately as libcpu-features-dev

[Andreas Beckmann]

Package: libvolk2-dev
Version: 2.4.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Preparing to unpack .../libcpu-features-dev_0.6.0-1+b1_amd64.deb ...
  Unpacking libcpu-features-dev (0.6.0-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/cpu_features/cpu_features_cache_info.h', 
which is also in package libvolk2-dev:amd64 2.4.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb

src:cpu-features has just passed new and ships these files which are
conflicting:

  usr/include/cpu_features/cpu_features_cache_info.h
  usr/include/cpu_features/cpu_features_macros.h
  usr/include/cpu_features/cpuinfo_x86.h

You should consider using the packaged library instead of the embedded copy.

cheers,

Andreas


libvolk2-dev=2.4.1-1_libcpu-features-dev=0.6.0-1+b1.log.gz
Description: application/gzip

Bug#978094: libhts3: missing Breaks+Replaces: libhts-dev (<< 1.11-3)

[Andreas Beckmann]

Package: libhts3
Version: 1.11-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../libhts3_1.11-3_amd64.deb ...
  Unpacking libhts3:amd64 (1.11-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libhts3_1.11-3_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/faidx.5.gz', which is also in 
package libhts-dev:amd64 1.9-11
  Errors were encountered while processing:
   /var/cache/apt/archives/libhts3_1.11-3_amd64.deb


cheers,

Andreas


libhts-dev=1.9-11_libhts3=1.11-3.log.gz
Description: application/gzip

Bug#978093: uhd-doc: missing Breaks+Replaces: uhd-host (<< 4.0.0.0-3)

[Andreas Beckmann]

Package: uhd-doc
Version: 4.0.0.0-3
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 .../uhd-doc_4.0.0.0-3_all.deb ...
  Unpacking uhd-doc (4.0.0.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uhd-doc_4.0.0.0-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/uhd-host', which is also in package 
uhd-host 3.15.0.0-4+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/uhd-doc_4.0.0.0-3_all.deb


cheers,

Andreas


uhd-host=3.15.0.0-4+b1_uhd-doc=4.0.0.0-3.log.gz
Description: application/gzip

Processed: fixed 966348 in 1:4.4.13-2

[Debian Bug Tracking System]

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

> fixed 966348 1:4.4.13-2
Bug #966348 {Done: Bernhard Schmidt } [src:ortp] ortp: 
FTBFS error: '__builtin_strncpy' specified bound 4 equals destination size
Marked as fixed in versions ortp/1:4.4.13-2.
> thanks
Stopping processing here.

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

Bug#963363: marked as done (libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 22:16:35 +0100
with message-id <160893099529.1527682.17224647246926537...@auryn.jones.dk>
and subject line Re: Bug#957480: libsrtp2: ftbfs with GCC-10
has caused the Debian Bug report #957480,
regarding libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using 
NSS...failed with error code 8
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Build done. Please run '/usr/bin/make runtest' to run self tests.
> running libsrtp2 test applications...
> crypto/test/cipher_driver -v
> cipher test driver
> David A. McGrew
> Cisco Systems, Inc.
> running cipher self-test for null cipher...passed
> running cipher self-test for AES-128 counter mode using NSS...passed
> running cipher self-test for AES-256 counter mode using NSS...passed
> running cipher self-test for AES-192 counter mode using NSS...passed
> running cipher self-test for AES-128 GCM using NSS...failed with error code 8
> make[1]: *** [Makefile:47: runtest] Error 8

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/libsrtp2_2.3.0-4_unstable.log

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

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

Quoting Bernhard Schmidt (2020-12-25 14:55:55)
> Control: tags -1 patch
> 
> This might fix it...
> 
> https://github.com/cisco/libsrtp/commit/716a73862b387a2107f37398c0fb7d9a754c0ccd

Yes, evidently it does: I applied that patch since release 2.3.0-3 and 
it built fine - I simply forgot to close this bugreport.

Sorry...!


 - Jonas

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

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

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

Bug#957480: marked as done (libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 22:16:35 +0100
with message-id <160893099529.1527682.17224647246926537...@auryn.jones.dk>
and subject line Re: Bug#957480: libsrtp2: ftbfs with GCC-10
has caused the Debian Bug report #957480,
regarding libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using 
NSS...failed with error code 8
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.)


-- 
957480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsrtp2
Version: 2.3.0-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/libsrtp2_2.3.0-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

[...]
checking for int8_t... yes
checking for uint8_t... yes
checking for int16_t... yes
checking for uint16_t... yes
checking for int32_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking size of unsigned long... 8
checking size of unsigned long long... 8
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for socket... yes
checking for inet_aton... yes
checking for usleep... yes
checking for sigaction... yes
checking whether to enable debug logging in all modules... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to leverage OpenSSL crypto... no
checking whether to leverage NSS crypto... no
checking for pcap_create in -lpcap... yes
checking for pcap_create in -lwpcap... no
checking whether to redirect logging to stdout... no
checking wheather to use a file for logging... no
checking for extra C compiler flags... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating crypto/Makefile
config.status: creating doc/Makefile
config.status: creating fuzzer/Makefile
config.status: creating libsrtp2.pc
config.status: creating crypto/include/config.h
configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-dependency-tracking, --disable-silent-rules, --disable-stdout, 
--enable-syslog, --disable-debug
touch debian/stamp-autotools
/usr/bin/make -C . shared_library test
make[1]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -Icrypto/include -I./include -I./crypto/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -O4 
-fexpensive-optimizations -funroll-loops -fPIC -c srtp/srtp.c -o srtp/srtp.o
gcc -DHAVE_CONFIG_H -Icrypto/include -I./include -I./crypto/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -O4 
-fexpensive-optimizations -funroll-loops -fPIC -c srtp/ekt.c -o srtp/ekt.o
gcc -DHAVE_CONFIG_H -Icrypto/include -I./include -I./crypto/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -O4 
-fexpensive-optimizations -funroll-loops -fPIC -c crypto/cipher/cipher.c -o 
crypto/cipher/cipher.o
gcc -DHAVE_CONFIG_H -Icrypto/include -I./include -I./crypto/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -O4 
-fexpensive-optimizations -funroll-loops -fPIC -c crypto/cipher/null_cipher.c 
-o crypto/cipher/null_cipher.o
gcc -DHAVE_CONFIG_H -Icrypto/include -I./include 

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

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 20:34:13 +
with message-id 
and subject line Bug#973137: fixed in pypuppetdb 2.2.0-1
has caused the Debian Bug report #973137,
regarding pypuppetdb: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/types.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/errors.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/api.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/QueryBuilder.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/package.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/utils.py -> 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build/pypuppetdb
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/types.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/errors.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/api.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/QueryBuilder.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/package.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
> copying pypuppetdb/utils.py -> 
> /<>/.pybuild/cpython3_3.8_pypuppetdb/build/pypuppetdb
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_pypuppetdb/build; python3.9 -m pytest 
> tests
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> plugins: cov-2.8.1
> collected 127 items
> 
> tests/test_baseapi.py .F [ 
> 39%]
> FF.FF[ 
> 43%]
> tests/test_connect.py .  [ 
> 44%]
> tests/test_package.py .  [ 
> 44%]
> tests/test_querybuilder.py ...   [ 
> 69%]
> tests/test_types.py ..   [ 
> 92%]
> tests/test_utils.py .
> [100%]Coverage.py warning: No data was collected. (no-data-collected)
> 
> 
> === FAILURES 
> ===
> ___ TesteAPIQuery.test_setting_headers_without_token 
> ___
> 
> self = 
> baseapi = 
> 
> def test_setting_headers_without_token(self, baseapi):
> httpretty.enable()
> stub_request('http://localhost:8080/pdb/query/v4/nodes')
> >   baseapi._query('nodes')  # need to query some endpoint
> 
> tests/test_baseapi.py:191: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> ../../../pypuppetdb/api.py:339: in _query
> r = self._session.get(url, params=payload,
> /usr/lib/python3/dist-packages/requests/sessions.py:543: in get
> return self.request('GET', url, **kwargs)
> 

Processed: Re: Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"

[Debian Bug Tracking System]

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

> reopen 978008
Bug #978008 {Done: Vincas Dargis } [libkwaylandserver5] 
libkwaylandserver5: undefined symbol: 
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Bug reopened
Ignoring request to alter fixed versions of bug #978008 to the same values 
previously set
> severity 978008 important
Bug #978008 [libkwaylandserver5] libkwaylandserver5: undefined symbol: 
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Severity set to 'important' from 'grave'
> retitle 978008 missing breaks against old kwin version
Bug #978008 [libkwaylandserver5] libkwaylandserver5: undefined symbol: 
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Changed Bug title to 'missing breaks against old kwin version' from 
'libkwaylandserver5: undefined symbol: 
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"'.
> tag 978008 + pending
Bug #978008 [libkwaylandserver5] missing breaks against old kwin version
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"

[Norbert Preining]

reopen 978008
severity 978008 important
retitle 978008 missing breaks against old kwin version
tag 978008 + pending
thanks

> Unpacking kwin-x11 (4:5.20.4-3) over (4:5.19.5-3+b1) ...

> So I guess I've got stuck on just a transition. I thought user-manager
> removal was one of these temporarily-transitional-stuff, so I avoided that.
> I should have removed it and there would be no issue.

Still, this should not happen, it is a missing breaks.

I reopen the bug, adjust severity, and mark as pending.

> Sorry for the noise.

Not noise at all, thanks for the report!

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#974551: marked as done (linphone: missing build-dependency on python-pystache)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 21:29:22 +0100
with message-id 
and subject line Fix uploaded to unstable
has caused the Debian Bug report #974551,
regarding linphone: missing build-dependency on python-pystache
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.)


-- 
974551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linphone
Version: 3.12.0-3.1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

linphone build-depends on python-pystache. However, sid has only
python3-pystache.

-Ralf.
--- End Message ---
--- Begin Message ---
The fixed version has been uploaded to unstable--- End Message ---

Processed: influxdb: CVE-2019-20933

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.6.4-1
Bug #978087 [src:influxdb] influxdb: CVE-2019-20933
Marked as found in versions influxdb/1.6.4-1.
> found -1 1.0.2+dfsg1-1
Bug #978087 [src:influxdb] influxdb: CVE-2019-20933
Marked as found in versions influxdb/1.0.2+dfsg1-1.
> fixed -1 1.1.1+dfsg1-4+deb9u1
Bug #978087 [src:influxdb] influxdb: CVE-2019-20933
The source 'influxdb' and version '1.1.1+dfsg1-4+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions influxdb/1.1.1+dfsg1-4+deb9u1.

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

Bug#978087: influxdb: CVE-2019-20933

[Salvatore Bonaccorso]

Source: influxdb
Version: 1.6.4-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/influxdata/influxdb/issues/12927
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.6.4-1
Control: found -1 1.0.2+dfsg1-1
Control: fixed -1 1.1.1+dfsg1-4+deb9u1

Hi,

The following vulnerability was published for influxdb.

CVE-2019-20933[0]:
| InfluxDB before 1.7.6 has an authentication bypass vulnerability in
| the authenticate function in services/httpd/handler.go because a JWT
| token may have an empty SharedSecret (aka shared secret).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-20933
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20933
[1] https://github.com/influxdata/influxdb/issues/12927
[2] 
https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0

Regards,
Salvatore

Bug#964403: marked as done (goxel FTBFS on armel: Must be linked with libatomic)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 20:17:50 +
with message-id 
and subject line Bug#964403: fixed in goxel 0.10.6-2
has caused the Debian Bug report #964403,
regarding goxel FTBFS on armel: Must be linked with libatomic
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=goxel=armel=0.10.6-1=1592688053=0

...
g++ -o goxel -fsanitize=address -fsanitize=undefined -pthread -Wl,-z,relro 
src/yocto.o src/xxhash.o src/utils.o src/tools.o src/theme.o src/tests.o 
src/system.o src/shape.o src/shader_cache.o src/script.o src/render.o 
src/quantization.o src/procedural.o src/pathtracer.o src/palette.o 
src/model3d.o src/meta.o src/mesh_utils.o src/mesh_to_vertices.o src/mesh.o 
src/material.o src/marchingcube.o src/main.o src/luagoxel.o src/layer.o 
src/imgui.o src/image.o src/gui.o src/goxel.o src/gesture3d.o src/gesture.o 
src/camera.o src/box_edit.o src/assets.o src/action.o src/utils/vec.o 
src/utils/texture.o src/utils/sound.o src/utils/mustache.o src/utils/json.o 
src/utils/ini.o src/utils/img.o src/utils/gl.o src/utils/color.o 
src/utils/cache.o src/utils/box.o src/utils/b64.o src/tools/shape.o 
src/tools/selection.o src/tools/procedural.o src/tools/plane.o src/tools/move.o 
src/tools/line.o src/tools/laser.o src/tools/fuzzy_select.o src/tools/extrude.o 
src/tools/color_picker.o src/tools/brush.o src/gui/view_panel.o 
src/gui/topbar.o src/gui/tools_panel.o src/gui/settings.o 
src/gui/render_panel.o src/gui/palette_panel.o src/gui/menu.o 
src/gui/material_panel.o src/gui/light_panel.o src/gui/layers_panel.o 
src/gui/image_panel.o src/gui/export_panel.o src/gui/debug_panel.o 
src/gui/cameras_panel.o src/gui/app.o src/gui/about.o src/formats/wavefront.o 
src/formats/vxl.o src/formats/voxlap.o src/formats/vox.o src/formats/txt.o 
src/formats/qubicle.o src/formats/povray.o src/formats/png_slices.o 
src/formats/png.o src/formats/gox.o src/formats/gltf.o src/formats/dicom.o 
-lasan -lubsan -lpng -lGL -lm -lglfw -lgtk-3 -lgdk-3 -lpangocairo-1.0 
-lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lgobject-2.0 -lglib-2.0
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::operator+=(unsigned long long)':
/usr/include/c++/9/bits/atomic_base.h:335: undefined reference to 
`__atomic_fetch_add_8'
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::store(unsigned long long, std::memory_order)':
/usr/include/c++/9/bits/atomic_base.h:397: undefined reference to 
`__atomic_store_8'
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/9/bits/atomic_base.h:419: undefined reference to 
`__atomic_load_8'
collect2: error: ld returned 1 exit status
scons: *** [goxel] Error 1


Fix/Workaround:

--- debian/rules.old2020-07-05 21:59:58.246217695 +
+++ debian/rules2020-07-05 22:00:26.841963922 +
@@ -2,6 +2,11 @@
 export DH_VERBOSE = 1
 NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
+
+
 include /usr/share/dpkg/default.mk  # provides DEB_VERSION
 
 %:
--- End Message ---
--- Begin Message ---
Source: goxel
Source-Version: 0.10.6-2
Done: Federico Ceratto 

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

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

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated goxel 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, 25 Dec 2020 19:30:10 +
Source: goxel
Architecture: source
Version: 0.10.6-2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 949552 964403 978021
Changes:
 goxel (0.10.6-2) unstable; urgency=medium
 .
   * Link to 

Processed: found 972134 in 83.0.4103.116-3

[Debian Bug Tracking System]

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

> found 972134 83.0.4103.116-3
Bug #972134 [chromium] chromium: please, consider moving the package to 
team-maintainance to properly maintain it
Marked as found in versions chromium/83.0.4103.116-3.
> thanks
Stopping processing here.

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

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

[Michel Le Bihan]

Hello,

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.

Michel Le Bihan

Bug#976245: mugshot: Muhshot fails with AttributeError: 'ElementTree' object has no attribute 'getiterator' in console

[Stephan Lachnit]

Can confirm, currently unusable. Has been fixed upstream [1], but no new 
release yet.
The fix should be added as patch or upstream should be asked for a new release 
before Bullseye.

Regards,
Stephan

[1] 
https://github.com/bluesabre/mugshot/commit/643b3d005a8865c961b836aeae4c1f76711646e9

Processed: Re: Bug#977931: python3-jedi: Version 0.17.2 of jedi is not compatible with the 0.8 branch of parso.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + upstream fixed-upstream
Bug #977931 [python3-jedi] python3-jedi: Version 0.17.2 of jedi is not 
compatible with the 0.8 branch of parso.
Added tag(s) fixed-upstream and upstream.
> severity -1 serious
Bug #977931 [python3-jedi] python3-jedi: Version 0.17.2 of jedi is not 
compatible with the 0.8 branch of parso.
Severity set to 'serious' from 'important'

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

Bug#975799: marked as done (python-clickhouse-driver: FTBFS: ModuleNotFoundError: No module named 'clickhouse_driver.varint')

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 17:49:48 +
with message-id 
and subject line Bug#975799: fixed in python-clickhouse-driver 0.1.3-3
has caused the Debian Bug report #975799,
regarding python-clickhouse-driver: FTBFS: ModuleNotFoundError: No module named 
'clickhouse_driver.varint'
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.)


-- 
975799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-clickhouse-driver
Version: 0.1.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_install
>   install -d /<>/debian/tmp
>   pybuild --install -i python{version} -p "3.8 3.9" --dest-dir 
> /<>/debian/tmp
> I: pybuild base:232: /usr/bin/python3.8 setup.py install --root 
> /<>/debian/python3-clickhouse-driver 
> running install
> running build
> running build_py
> running build_ext
> running install_lib
> creating /<>/debian/python3-clickhouse-driver
> creating /<>/debian/python3-clickhouse-driver/usr
> creating /<>/debian/python3-clickhouse-driver/usr/lib
> creating /<>/debian/python3-clickhouse-driver/usr/lib/python3.8
> creating 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages
> creating 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/bufferedwriter.cpython-38-x86_64-linux-gnu.so
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver
> creating 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/dbapi
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/dbapi/errors.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/dbapi
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/dbapi/__init__.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/dbapi
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/dbapi/connection.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/dbapi
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/dbapi/cursor.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/dbapi
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/clientinfo.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver
> creating 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/nothingcolumn.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/lowcardinalitycolumn.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/__init__.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/enumcolumn.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/stringcolumn.cpython-38-x86_64-linux-gnu.so
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/floatcolumn.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/service.py
>  -> 
> /<>/debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages/clickhouse_driver/columns
> copying 
> /<>/.pybuild/cpython3_3.8_clickhouse-driver/build/clickhouse_driver/columns/decimalcolumn.py
>  -> 
> 

Bug#975825: marked as done (python-m2r: FTBFS: AttributeError: 'str' object has no attribute 'supported')

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 17:06:23 +
with message-id 
and subject line Bug#975825: fixed in python-m2r 0.2.1-5
has caused the Debian Bug report #975825,
regarding python-m2r: FTBFS: AttributeError: 'str' object has no attribute 
'supported'
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying m2r.py -> /<>/.pybuild/cpython3_3.9/build
> running egg_info
> creating m2r.egg-info
> writing m2r.egg-info/PKG-INFO
> writing dependency_links to m2r.egg-info/dependency_links.txt
> writing entry points to m2r.egg-info/entry_points.txt
> writing requirements to m2r.egg-info/requires.txt
> writing top-level names to m2r.egg-info/top_level.txt
> writing manifest file 'm2r.egg-info/SOURCES.txt'
> reading manifest file 'm2r.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found under 
> directory '*'
> warning: no previously-included files matching '*.py[co]' found under 
> directory '*'
> writing manifest file 'm2r.egg-info/SOURCES.txt'
> sphinx-build -b html docs debian/doc/html
> Running Sphinx v3.3.1
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 266, in 
> add_source_parser
> for filetype in parser.supported:
> AttributeError: 'str' object has no attribute 'supported'
> The full traceback has been saved in /tmp/sphinx-err-32it295p.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/python-m2r_0.2.1-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-m2r
Source-Version: 0.2.1-5
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
python-m2r, 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 python-m2r 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, 25 Dec 2020 17:36:21 +0100
Source: python-m2r
Architecture: source
Version: 0.2.1-5
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 975825
Changes:
 python-m2r (0.2.1-5) unstable; urgency=medium
 .
   * update git-buildpage settings:
 + use DEP-14 git branch names
 + add usage comment
   * update patch 1001;
 closes: bug#975825,
 thanks to Lucas Nussbaum, Kyle Robbertze, and Daniel Caballero
   * use debhelper compatibility level 13 (not 12)
   * declare compliance with Debian Policy 4.5.1
   * update and unfuzz patches
Checksums-Sha1:
 6e698c9ddcb9e766db402324f5732492dc96dc1a 2140 python-m2r_0.2.1-5.dsc
 b9c2df06d7c631bf04a1b809407fab886e53e9ca 5384 python-m2r_0.2.1-5.debian.tar.xz
 fed5f596292fe0a40045f7b0ff5d1a43469488e1 7833 
python-m2r_0.2.1-5_amd64.buildinfo
Checksums-Sha256:
 49bd903fafdf1bd4952b94a66b780edeabafe588f867fca3e20cf695f3394bf5 2140 

Bug#975854: marked as done (mediastreamer2: FTBFS: string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound 8 equals destination size [-Werror=stringop-truncation])

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 18:00:24 +0100
with message-id 
and subject line Fixed version has just been uploaded to unstable
has caused the Debian Bug report #975854,
regarding mediastreamer2: FTBFS: string_fortified.h:106:10: error: 
‘__builtin_strncpy’ specified bound 8 equals destination size 
[-Werror=stringop-truncation]
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.)


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

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
> -DBZRTP_STATIC -DHAVE_CONFIG_H -DMS2_EXPORTS -DMS2_FILTERS -DMS2_INTERNAL 
> -DMS2_STATIC -DORTP_STATIC -DVIDEO_ENABLED -D_TRUE_TIME 
> -Dmediastreamer_base_EXPORTS -I/<>/include 
> -I/<>/src/audiofilters -I/<>/src/utils 
> -I/<>/src/voip -I/<>/obj-x86_64-linux-gnu 
> -I/<>/obj-x86_64-linux-gnu/src -I/usr/include/libxml2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC  -Wall 
> -Wuninitialized -Wno-format-truncation -Werror -Wextra -Wno-unused-parameter 
> -fno-strict-aliasing -Wno-missing-field-initializers 
> -Wdeclaration-after-statement -Wstrict-prototypes 
> -Wno-error=strict-prototypes -o 
> CMakeFiles/mediastreamer_base.dir/otherfilters/void.c.o -c 
> /<>/src/otherfilters/void.c
> In file included from /usr/include/string.h:495,
>  from /usr/include/bctoolbox/port.h:38,
>  from /<>/include/mediastreamer2/mscommon.h:22,
>  from /<>/include/mediastreamer2/msfilter.h:23,
>  from 
> /<>/include/mediastreamer2/mstonedetector.h:24,
>  from /<>/src/audiofilters/tonedetector.c:25:
> In function ‘strncpy’,
> inlined from ‘detector_process’ at 
> /<>/src/audiofilters/tonedetector.c:176:8:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: 
> ‘__builtin_strncpy’ specified bound 8 equals destination size 
> [-Werror=stringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> ^~
> [ 22%] Building C object 
> src/CMakeFiles/mediastreamer_voip-static.dir/audiofilters/ulaw.c.o
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
> -DBZRTP_STATIC -DHAVE_CONFIG_H -DMS2_EXPORTS -DMS2_FILTERS -DMS2_INTERNAL 
> -DMS2_STATIC -DORTP_STATIC -DVIDEO_ENABLED -D_TRUE_TIME 
> -I/<>/include -I/<>/src/audiofilters 
> -I/<>/src/utils -I/<>/src/voip 
> -I/<>/obj-x86_64-linux-gnu 
> -I/<>/obj-x86_64-linux-gnu/src -I/usr/include/libxml2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Wuninitialized -Wno-format-truncation -Werror -Wextra -Wno-unused-parameter 
> -fno-strict-aliasing -Wno-missing-field-initializers 
> -Wdeclaration-after-statement -Wstrict-prototypes 
> -Wno-error=strict-prototypes -o 
> CMakeFiles/mediastreamer_voip-static.dir/audiofilters/ulaw.c.o -c 
> /<>/src/audiofilters/ulaw.c
> [ 23%] Linking C shared library libmediastreamer_base.so
> cc1: all warnings being treated as errors
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/mediastreamer_base.dir/link.txt --verbose=1
> make[3]: *** [src/CMakeFiles/mediastreamer_voip-static.dir/build.make:306: 
> src/CMakeFiles/mediastreamer_voip-static.dir/audiofilters/tonedetector.c.o] 
> Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/mediastreamer2_2.16.1-4_unstable.log

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

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

Bug#975825: python-m2r: FTBFS: AttributeError: 'str' object has no attribute 'supported'

[Jonas Smedegaard]

Control: forwarded -1 https://github.com/CrossNox/m2r2/pull/14

Thanks Kyle!

The actual patch was burried one step deeper, but your pointer was quite 
helpful nonetheless :-)


 - Jonas

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

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

signature.asc
Description: signature

Processed: Re: Bug#975825: python-m2r: FTBFS: AttributeError: 'str' object has no attribute 'supported'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/CrossNox/m2r2/pull/14
Bug #975825 [src:python-m2r] python-m2r: FTBFS: AttributeError: 'str' object 
has no attribute 'supported'
Changed Bug forwarded-to-address to 'https://github.com/CrossNox/m2r2/pull/14' 
from 'https://github.com/CrossNox/m2r2/issues/13'.

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

Bug#966348: marked as done (ortp: FTBFS error: '__builtin_strncpy' specified bound 4 equals destination size)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 17:21:37 +0100
with message-id 
and subject line Fixed version has just hit unstable
has caused the Debian Bug report #966348,
regarding ortp: FTBFS error: '__builtin_strncpy' specified bound 4 equals 
destination size
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.)


-- 
966348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ortp
Version: 1:1.0.2-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: found -1 1:4.3.2-1

[ 24%] Building C object src/CMakeFiles/ortp.dir/rtcp.c.o
cd /build/ortp-1.0.2/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -Dortp_EXPORTS 
-I/build/ortp-1.0.2/include -I/build/ortp-1.0.2/src 
-I/build/ortp-1.0.2/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/build/ortp-1.0.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC-Wall 
-Wuninitialized -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/ortp.dir/rtcp.c.o   -c /build/ortp-1.0.2/src/rtcp.c
In file included from /usr/include/string.h:495,
 from /build/ortp-1.0.2/include/ortp/port.h:41,
 from /build/ortp-1.0.2/include/ortp/logging.h:29,
 from /build/ortp-1.0.2/include/ortp/ortp.h:66,
 from /build/ortp-1.0.2/src/rtcp.c:28:
In function 'strncpy',
inlined from 'rtcp_app_init' at /build/ortp-1.0.2/src/rtcp.c:373:2,
inlined from 'rtp_session_send_rtcp_APP' at 
/build/ortp-1.0.2/src/rtcp.c:626:13:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: 
'__builtin_strncpy' specified bound 4 equals destination size 
[-Werror=stringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
cc1: all warnings being treated as errors
make[3]: *** [src/CMakeFiles/ortp.dir/build.make:235: 
src/CMakeFiles/ortp.dir/rtcp.c.o] Error 1

This is probably gcc-10 doing more checking than previous versions.


Andreas
--- End Message ---
--- Begin Message ---
.--- End Message ---

Bug#978079: python3-rawkit: Support for libraw20 missing

[Kendy Kutzner]

Package: python3-rawkit
Version: 0.6.0-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kendy.kutz...@gmail.com

Dear Maintainer,

   * What led up to the situation?

sudo aptitude install libraw20 python3-rawkit
python3
>>> from rawkit.raw import Raw
>>> r=Raw(filename='1608680820.cr2')
[...]
ImportError: Unsupported Libraw version: 0.20.2.

I'm using bullseye/sid.

Kendy


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

Kernel: Linux 5.9.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=C.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 python3-rawkit depends on:
ii  python3  3.9.0-4

python3-rawkit recommends no packages.

python3-rawkit suggests no packages.

-- no debconf information

Processed: Re: Bug#975548: marked as done (mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED])

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #975548 {Done: Debian FTP Masters } 
[src:mariadb-10.3] mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED]
'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 1:10.3.24-2+rm.

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

Bug#975548: marked as done (mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED])

[Aurelien Jarno]

control: reopen -1

The package has been removed from unstable, but is still present in
experimental. Reopening the bug.

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

Processed: Re: mugshot: Muhshot fails with AttributeError: 'ElementTree' object has no attribute 'getiterator' in console

[Debian Bug Tracking System]

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

> severity 976245 grave
Bug #976245 [mugshot] mugshot: Muhshot fails with AttributeError: 'ElementTree' 
object has no attribute 'getiterator' in console
Severity set to 'grave' from 'important'
> tags 976245 fixed-upstream
Bug #976245 [mugshot] mugshot: Muhshot fails with AttributeError: 'ElementTree' 
object has no attribute 'getiterator' in console
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Pirate Praveen]

Control: forwarded -1 
https://github.com/ai/autoprefixer-rails/issues/199


On Fri, 25 Dec 2020 14:51:34 +0530 Pirate Praveen 
 wrote:
> Even though the build now succeed, it is producing a broken output. 
Size of autoprefixer.js dropped from 4.5 mb to 900 kb. It should bundle 
postcss and polyfills.

>
> It may be because newer versions of browsers supporting new features 
without polyfills. But we need to confirm it.

>
> One way could be building the upstream code with build dependencies 
matching the versions in debian. rollup, its plugins or 
caniuse-db/browserslist update may have caused this change.


This seems to be caused by @rollup/plugin-node-resolve 10. Running 
build in upstream repo with updated @rollup/plugin-node-resolve throws 
a similar error.


With upsteam yarn.lock and yarnpkg install,

(debian-sid)pravi@ilvala2:~/forge/js-team/autoprefixer-rails-10.1.0.0/build$ 
yarnpkg run rollup -c

yarn run v1.22.10
$ 
/home/pravi/forge/js-team/autoprefixer-rails-10.1.0.0/build/node_modules/.bin/rollup 
-c


autoprefixer.js → ../vendor/autoprefixer.js...
created ../vendor/autoprefixer.js in 8s
Done in 8.47s.

Now with updated @rollup/plugin-node-resolve

(debian-sid)pravi@ilvala2:~/forge/js-team/autoprefixer-rails-10.1.0.0/build$ 
yarnpkg upgrade @rollup/plugin-node-resolve@^10.0.0

yarn upgrade v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.1.3: The platform "linux" is incompatible with this 
module.
info "fsevents@2.1.3" is an optional dependency and failed 
compatibility check. Excluding it from installation.

[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ @rollup/plugin-node-resolve@10.0.0
info All dependencies
└─ @rollup/plugin-node-resolve@10.0.0
Done in 3.75s.

$ yarnpkg run rollup -c
yarn run v1.22.10
$ 
/home/pravi/forge/js-team/autoprefixer-rails-10.1.0.0/build/node_modules/.bin/rollup 
-c


autoprefixer.js → ../vendor/autoprefixer.js...
[!] Error: Could not load process (imported by 
node_modules/postcss/lib/postcss.js): ENOENT: no such file or 
directory, open 'process'
Error: Could not load process (imported by 
node_modules/postcss/lib/postcss.js): ENOENT: no such file or 
directory, open 'process'


error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about 
this command.

Bug#977710: marked as done (libjs-milligram is not maintained by JS Team)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 15:05:11 +
with message-id 
and subject line Bug#977710: fixed in libjs-milligram 1.4.1-2
has caused the Debian Bug report #977710,
regarding libjs-milligram is not maintained by JS Team
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.)


-- 
977710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-milligram
Severity: serious
Tags: security

libjs-milligram is marked as maintained by JS Team, howeber uploader is
not member of this team and repository isn't under /js-team/ tree.
--- End Message ---
--- Begin Message ---
Source: libjs-milligram
Source-Version: 1.4.1-2
Done: Federico Ceratto 

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated libjs-milligram 
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, 25 Dec 2020 14:42:13 +
Source: libjs-milligram
Architecture: source
Version: 1.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 977710
Changes:
 libjs-milligram (1.4.1-2) unstable; urgency=medium
 .
   * Update maintainer (Closes: #977710)
Checksums-Sha1:
 8599c10dbad1f070d7a79978c52ca9bbaef81471 1907 libjs-milligram_1.4.1-2.dsc
 83ec20d9a8f408fecd6ae41b003f2afc94523657 2056 
libjs-milligram_1.4.1-2.debian.tar.xz
 c51cd2f8f27f6cd06ce611a0dcda913fc6171ff8 5755 
libjs-milligram_1.4.1-2_amd64.buildinfo
Checksums-Sha256:
 d69df812aeaf0a5d221b2c8c4ff3298dd1a3561506888bcaacb8688a7585de10 1907 
libjs-milligram_1.4.1-2.dsc
 3b3745f0b90a23401bf589e7d055dc5c3b293cfdfd7a4de216fc59e983dc6003 2056 
libjs-milligram_1.4.1-2.debian.tar.xz
 6d34a9fa2f91c635024126ebfbed877add32088ebe4eab2576b9b97a12d6efc7 5755 
libjs-milligram_1.4.1-2_amd64.buildinfo
Files:
 3e25be3853530edff8ec2190c767c7c9 1907 javascript optional 
libjs-milligram_1.4.1-2.dsc
 dee81d1abb45c9e3e35c50f1c3d61afe 2056 javascript optional 
libjs-milligram_1.4.1-2.debian.tar.xz
 c814600d8ec2a56608d0eea13a406d46 5755 javascript optional 
libjs-milligram_1.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl/l+7MACgkQbzG8RPUX
fapfaxAAivaQpHV/yaDuWwdC/0R1kaxShh1eTqX3D9a4JjgHMwcIuvOcCJqoqbSr
BGElVD62vgZV3mwFjWhP5C/PbOWph5y0HtZXmU6KFqLyT6rLTz/9A9c1/SDbnPwB
p6DSJo0cJFdwzCEvLh2Dqt4rn75axi8FUYLuerQUZui6qAluVls7ZVlNu+4whEXN
Efo7CvPC9sJv7FR/6Q6eRLSNH4nvLX7X7C+G4A1w6EzHi6IE5u2nMZhXUyE27VXo
a8UOmBfvYAcXXzLff5RIaumHJet02NSk5qyadlX3UQfBR6dxPPqfCfWgd4Zif/Iu
K4LyOT4JdjcTqtWoQICAzfxXN4izR/YwBRN8rfjsXBepPRm2v2+eCD3mUgvt3ppc
G/gbAEKzHw2MUewt2+aES08bqWNMN0/87MexiyMo7uCIOeEIsZKiOi9d5Dpk8vz3
8RAvzydsn2PIxtG9YRSz8XQ9+PzvBXigfjFlvCvELxTR4tzUtOYwFXckfJywO4Rs
pb94C3aW3hcONmZPofj0fL8V9YO3Q+nkwwMr/Oh68GW60zSnxcOTH/gWj42l/rLM
M2CvM9QRNX0kNv+n9bUxMajuIn2R3ssqzyPjphg+kRY/rRBJiPWAZ0G0+1dPhKxe
3KQQy7xMSCgzXv8VDkZCJt3NPQgfZW1lIsDS0KPg8JSMIVSApus=
=bMzU
-END PGP SIGNATURE End Message ---

Bug#958497: marked as done (geoclue-2.0 violates GDPR)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 14:34:26 +
with message-id 
and subject line Bug#958497: fixed in geoclue-2.0 2.5.7-1
has caused the Debian Bug report #958497,
regarding geoclue-2.0 violates GDPR
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.)


-- 
958497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: geoclue-2.0
Version: 2.5.6-1
Severity: serious

The geoclue package collects SSIDs in the neighborhood and sends them to
Mozilla location services.

The SSID of an adhoc network (which for instance is set up for tethering
via a mobile phone) is personally identifiable information. Sending this
information about a third person without his or her explicit consent to
another party especially one outside of the European Union is in breach
of the German law Datenschutz-Grundverordnung which is the German
implementation of the European General Data Protection Regulation (GDPR).

The easiest remedy would be to remove the package from the repository
until it is fixed upstream to be compliant.

Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924516

src/gclue-config.c:219:
#define DEFAULT_WIFI_URL
"https://location.services.mozilla.com/v1/geolocate?key=; MOZILLA_API_KEY
#define DEFAULT_WIFI_SUBMIT_URL
"https://location.services.mozilla.com/v1/submit?key=; MOZILLA_API_KEY

Best regards

Heinrich Schuchardt
--- End Message ---
--- Begin Message ---
Source: geoclue-2.0
Source-Version: 2.5.7-1
Done: Laurent Bigonville 

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

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

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated geoclue-2.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Dec 2020 14:59:35 +0100
Source: geoclue-2.0
Architecture: source
Version: 2.5.7-1
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Laurent Bigonville 
Closes: 924516 958497
Changes:
 geoclue-2.0 (2.5.7-1) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * New upstream version 2.5.7
 - Check the maximum allowed accuracy level even for system applications.
   Respect the value of the user preference concerning the usage of their
   geolocation. This should fix the privacy and GDPR conformity concerns as
   the user explicitly needs to enable the option.
   Note that there is no distinction between the system applications
   anymore, turning on the option is allowing them all to get the location.
   (Closes: #924516, #958497)
   * debian/README.Debian: Add information about MLS and a link to the service
 Privacy Notice page
   * Add debian/salsa-ci.yml file
   * debian/control: Remove Craig Andrews from the Uploaders.
 He has not been active since 2009, thanks for his previous work on the
 package
   * d/p/: Add a patch to make the Mozilla API key configurable
   * debian/rules: Use the key that has been allocated to debian for MLS queries
   * d/gbp.conf: Stop adding the commit-id and set multimaint-merge to True
   * debian/control: Bump Standards-Version to 4.5.1 (no further changes)
   * d/p: Add an upstream patch to fix the display of the usage indicator
   * d/p: Remove the remaining differences between system app and flatpak ones.
 This fix an issue when geoclue is D-Bus activated by a client and also
 make sure that a running client is disconnected when the user disables
 the location services (set the accuracy to 0)
 .
   [ Chris McGee ]
   * debian/control: Add rules requires root
 .
   [ Debian Janitor ]
   * Refer to specific version of license LGPL-2+.
   * Apply multi-arch hints.
 + geoclue-doc, libgeoclue-doc: Add Multi-Arch: foreign.
Checksums-Sha1:
 c06f08da2d6cda9428924a67213f0446c4b3daf3 2386 geoclue-2.0_2.5.7-1.dsc
 28fec44b0583208a8654296ab39d45f2ab71d318 85764 geoclue-2.0_2.5.7.orig.tar.bz2
 a47ac7a0aac0a8f4d365c01bcfdc6e03363f0551 14728 
geoclue-2.0_2.5.7-1.debian.tar.xz
 

Processed: found 958497 in 2.5.0-1, tagging 958497

[Debian Bug Tracking System]

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

> found 958497 2.5.0-1
Bug #958497 [geoclue-2.0] geoclue-2.0 violates GDPR
Marked as found in versions geoclue-2.0/2.5.0-1.
> tags 958497 + buster
Bug #958497 [geoclue-2.0] geoclue-2.0 violates GDPR
Added tag(s) buster.
> thanks
Stopping processing here.

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

Processed: Re: Bug#957480: libsrtp2: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #957480 [src:libsrtp2] libsrtp2: FTBFS: running cipher self-test for 
AES-128 GCM using NSS...failed with error code 8
Bug #963363 [src:libsrtp2] libsrtp2: FTBFS: running cipher self-test for 
AES-128 GCM using NSS...failed with error code 8
Added tag(s) patch.
Added tag(s) patch.

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

Bug#957480: libsrtp2: ftbfs with GCC-10

[Bernhard Schmidt]

Control: tags -1 patch

This might fix it...

https://github.com/cisco/libsrtp/commit/716a73862b387a2107f37398c0fb7d9a754c0ccd

Processed: found 966348 in 1:1.0.2-1

[Debian Bug Tracking System]

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

> found 966348 1:1.0.2-1
Bug #966348 [src:ortp] ortp: FTBFS error: '__builtin_strncpy' specified bound 4 
equals destination size
Marked as found in versions ortp/1:1.0.2-1.
> thanks
Stopping processing here.

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

Processed: block 977592 with 977568

[Debian Bug Tracking System]

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

> block 977592 with 977568
Bug #977592 [release.debian.org] transition: xalan
977592 was not blocked by any bugs.
977592 was not blocking any bugs.
Added blocking bug(s) of 977592: 977568
> thanks
Stopping processing here.

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

Bug#977568: xml-security-c changes for xalan 1.12

[Bill Blough]

Hi,

I've uploaded xalan 1.12 to unstable.  If you would like me to NMU
xml-security-c with the necessary changes (attached to 977568), I would
be happy to do so.

Best regards,
Bill



-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Processed: reassign 977502 to podman

[Debian Bug Tracking System]

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

> reassign 977502 podman
Bug #977502 {Done: Reinhard Tartler } 
[podman,golang-github-containers-common] 
podman,golang-github-containers-common: both ship 
/usr/share/man/man5/containers-mounts.conf.5.gz
Bug reassigned from package 'podman,golang-github-containers-common' to 
'podman'.
No longer marked as found in versions libpod/2.1.1+dfsg1-2 and 
golang-github-containers-common/0.28.1+ds1-1.
No longer marked as fixed in versions libpod/2.2.1+dfsg1-1 and 
libpod/2.1.1+dfsg1-3.
> thanks
Stopping processing here.

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

Bug#973848: security update of chromium in Debian stable?

[Tomas Pospisek]

It seems like Linux Mint was able to build Chromium v87 for "debbie":

  
http://packages.linuxmint.com/search.php?release=any=any=chromium

which is as far as I understand based on Debian buster. So I am *assuming* 
they have somehow resolved the "SFINAE" problem?


All this is just slightly informed guessing since in truth I do not 
understand a thing about how Linux Mint is building stuff...


?
*t

On Wed, 23 Dec 2020, Jan Luca Naumann wrote:


Hey,

parallel to Michel's very nice work to get chromium into unstable
(thanks to him!), I tried to build the current version in a buster
chroot. At the moment I struggle that there seems a difference how
SFINAE[1] in a special case [2] is handled different between buster's
and unstable's clang version. Since I had not so much time I have not
found a fix to work around this.

If people are more experienced with C++ templates than me, I would be
happy to share the problem and the build log ;)

Best,
Jan

[1] https://en.wikipedia.org/wiki/Substitution_failure_is_not_an_error

[2]

In file included from
../../third_party/blink/common/privacy_budget/identifiability_metric_builder.cc:5:
In file included from
../../third_party/blink/public/common/privacy_budget/identifiability_metric_builder.h:9:
In file included from
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/vector:60:
In file included from
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/bits/stl_algobase.h:64:
In file included from
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/bits/stl_pair.h:59:
In file included from
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/bits/move.h:55:
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/type_traits:2046:15:
error: only enumeration types
have underlying types
 typedef __underlying_type(_Tp) type;
 ^
../../third_party/blink/public/common/privacy_budget/identifiable_token.h:121:40:
note: in instantiation of template
class 'std::underlying_type >' requested here
   typename U = typename std::underlying_type::type,

Am 23.12.20 um 12:13 schrieb Tomas Pospisek:

Hi all,

now that sid has seen an update of Chromium to v87 (hooray and thanks
everybody!) does anybody know it there's activity or plans towards
updating chromium in Debian stable?

Chromium from sid is not installable in Debian stable due to

    Depends: libc6 (>= 2.29)

whereas stable has 2.28.

I'm not sure what the correct procedure would be to kickstart the Debian
stable update?

*t

Bug#978051: [Pkg-javascript-devel] Bug#978051: node-consolidate depends on babel-core 6

[Xavier]

Le 25/12/2020 à 09:55, Xavier Guimard a écrit :
> Package: node-consolidate
> Version: 0.15.1+repack-1
> Severity: serious
> 
> Enabling test proves that node-consolidate depends on node-babel-core 6:
> 
> ```
>   function requireReact(module, filename) {
> var babel = requires.babel || (requires.babel = require('babel-core'));
>   
> var compiled = babel.transformFileSync(filename, { presets: [ 'react' ] 
> }).code;
>   
> return module._compile(compiled, filename);
>   }
>   
>   exports.requireReact = requireReact;
>   
>   /**
>*  Converting a string into a node module.
>*/
>   function requireReactString(src, filename) {
> var babel = requires.babel || (requires.babel = require('babel-core'));
>   
> if (!filename) filename = '';
> var m = new module.constructor();
> filename = filename || '';
>   
> // Compile Using React
> var compiled = babel.transform(src, { presets: [ 'react' ] }).code;
> ```

Maybe we can simply remove it from Debian: no reverse dependencies

Processed: Re: again not fixed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js 
symlink
Added tag(s) help.

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

Bug#977960: again not fixed

[Xavier]

Control: tags -1 help

Le 25/12/2020 à 10:34, Matthias Klose a écrit :
> Control: reopen -1
> Control: found -1 3.5.1+dfsg+~3.5.5-3
> 
> the changelog reads:
> 
>   * Team upload
>   * libjs-jquery must require node-jquery with the same version
> (Closes: #977960)
> 
> and after the upgrade:
> 
> $ ls -l /usr/share/nodejs/jquery/dist/
> total 0
> lrwxrwxrwx 1 root root 34 Dec 23 22:00 jquery.js ->
> ../../nodejs/jquery/dist/jquery.js
> lrwxrwxrwx 1 root root 38 Dec 23 22:00 jquery.min.js ->
> ../../nodejs/jquery/dist/jquery.min.js
> lrwxrwxrwx 1 root root 45 Dec 23 22:00 jquery.min.js.brotli ->
> ../../nodejs/jquery/dist/jquery.min.js.brotli
> lrwxrwxrwx 1 root root 41 Dec 23 22:00 jquery.min.js.gz ->
> ../../nodejs/jquery/dist/jquery.min.js.gz
> lrwxrwxrwx 1 root root 39 Dec 23 22:00 jquery.min.map ->
> ../../nodejs/jquery/dist/jquery.min.map
> lrwxrwxrwx 1 root root 46 Dec 23 22:00 jquery.min.map.brotli ->
> ../../nodejs/jquery/dist/jquery.min.map.brotli
> lrwxrwxrwx 1 root root 42 Dec 23 22:00 jquery.min.map.gz ->
> ../../nodejs/jquery/dist/jquery.min.map.gz
> 
> I would appreciate if you could do a little bit more engineering instead of
> witchcraft to fix this issue.  How would tightening of the depends have an
> effect on this?
> 
> With every such upload you also trigger thousands auf autopkg tests, doomed to
> be invalid with the next upload.
> 
> As I said earlier:
> 
>> please could you check an upgrade path from the last versions?
>> snapshot.debian.org should have these packages.
> 
>> You also could create such a directory with the symlinks and check that the
>> upgrade works.
> 
> Finding out how you got into this situation would be the preferred first thing
> to do.  If you don't want to spend that time, think about how to fix the 
> issue.
> E.g. would it be ok to remove these symlinks in a preinst, guarding that fix 
> to
> only apply to versions until the version that fixes the issue?
> 
> Merry XMas, Matthias

Hi,

I tried many upgrades from stable, from testing, without any problem.
Then I don't know how to fix this. Waiting for help from another JS Team
member.

Bug#977657: marked as done (swi-prolog: FTBFS with OpenSSL 1.1.1i)

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 11:18:40 +
with message-id 
and subject line Bug#977657: fixed in swi-prolog 8.2.3+dfsg-2
has caused the Debian Bug report #977657,
regarding swi-prolog: FTBFS with OpenSSL 1.1.1i
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.)


-- 
977657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swi-prolog
Version: 8.2.3+dfsg-1
Severity: serious
Forwarded: https://github.com/SWI-Prolog/packages-ssl/issues/159
Tag: patch

Hi,

Swi-prolog is failing to build using OpenSSL 1.1.1i. I've attached
a patch that fixes it.


Kurt

--- packages/ssl/test_ssl.pl.orig	2020-12-18 11:04:37.481046178 +0100
+++ packages/ssl/test_ssl.pl	2020-12-18 11:06:09.479169064 +0100
@@ -629,11 +629,14 @@
 test('Certificate is not issued by trusted CA'):-
 do_verification_test(14, try_ssl_client('www.example.com', test_verify_hook), VerificationResults, Status),
 ( VerificationResults:Status == [unknown_issuer]:true ->
-% OpenSSL 1.0.2 and above
+% OpenSSL 1.0.2 - 1.1.1h
 true
 ; VerificationResults:Status == [unknown_issuer, not_trusted]:true ->
 % OpenSSL 1.0.1 and below
 true
+; VerificationResults:Status == [unknown_issuer, verified]:true ->
+% OpenSSL 1.1.1i and above
+true
 ).
 
 test('Certificate is issued by trusted CA but has been altered so signature is wrong', VerificationResults:Status == [bad_signature, verified]:true):-
--- End Message ---
--- Begin Message ---
Source: swi-prolog
Source-Version: 8.2.3+dfsg-2
Done: Lev Lamberov 

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

Debian distribution maintenance software
pp.
Lev Lamberov  (supplier of updated swi-prolog 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, 25 Dec 2020 15:47:31 +0500
Source: swi-prolog
Architecture: source
Version: 8.2.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Lev Lamberov 
Changed-By: Lev Lamberov 
Closes: 977657
Changes:
 swi-prolog (8.2.3+dfsg-2) unstable; urgency=medium
 .
   * Add patch to fix FTBFS with OpenSSL 1.1.1i (Closes: #977657)
 Thanks to Kurt Roeckx
Checksums-Sha1:
 a6f760abb089ddf60347a8e91cf9df10576d97f9 3464 swi-prolog_8.2.3+dfsg-2.dsc
 00427143a13531ed3e81abfc155f00daef0042e8 33528 
swi-prolog_8.2.3+dfsg-2.debian.tar.xz
 b2658f9a82cea6ab93ff627e82c03eedfc88f404 15827 
swi-prolog_8.2.3+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 8a8e5f568d44eeba4efd4c914d329792f88f69b150dcef77f31525b11286d5c4 3464 
swi-prolog_8.2.3+dfsg-2.dsc
 7c002f5f05bc675bd05e57f9289938de90038e3d44a7dd22f8b8379ea2e16433 33528 
swi-prolog_8.2.3+dfsg-2.debian.tar.xz
 e189aa9e7c2686dd630c82c265491a798e533b6a16074d93884e2cc80f748062 15827 
swi-prolog_8.2.3+dfsg-2_amd64.buildinfo
Files:
 6c68fef47b4a5c3fd792f5a738b11563 3464 interpreters optional 
swi-prolog_8.2.3+dfsg-2.dsc
 8a6730fd4a36289880de6b430403d386 33528 interpreters optional 
swi-prolog_8.2.3+dfsg-2.debian.tar.xz
 5c40432e4756665ec2690735ea10f860 15827 interpreters optional 
swi-prolog_8.2.3+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAl/lx4kACgkQXudu4gIW
0qWuExAAo2mOwYKgacgr5gX1AhIJt37qG+qn4usCFP4atc2DMXUD6/LmILAqBQuR
6zizf8+QEc0zZFk/2YEu2T9J3i37x6NzmE5xF5r9Q0r38/nsLHl9iBDxBmI1i0eO
Aj5RK+Kk53AKWSBIuR9wzvWpd4UW4kHoIVt4ORJam8CmQd7MNAl3b5gnzKSzIem/
ul3Wefxp1qM1mWBqIuWulHU2hDxwql4Q0CZ/V29C0mlSKlhqdqyf3LwBXcTxvnsh
N1QdPvyscVaaGLMrLKlehl7tbTv52d/GRhdc8kq6LhiPBm7DkVK4zXpclnUiSgid
V7ixoiXK5PBnUlXPm8fXFH0M4WrZ2NtIY7uaE0qDEa8cpZIzUaOprFJ2xgE8scuf
p7SiRwdkvJor5Nl0SGxHw6jNodJH0MnE+tMf6gSMcU5wzQHou2GR/txCGxqpV5KT
KV/782ZbX8y0l1Wnu/CWxE4gSZq2R1D02b86Ns7FmIg6lIAQjbd7WagY5i38B2Dy
qis2ChHTo7Y1A9Q2E1BbziqZF10x2LNx3xLGg6HXlgjYpOn9Ag0l8eXm1gBriGU0
kCvO5wC/jMj05mRSc0Kp7KuQ4b2gUDujg4FAoM+bQWseCCD+c7HM5z+ZyJ6dnAD4
OgQSeL9V+ab5688jtm5/zckRWcpO0Qn2wSnr+hHlg6i6gCWv0n8=
=SMw4
-END PGP SIGNATURE End Message ---

Processed: pmix: breaks openmpi autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:deal.ii
Bug #978066 [src:pmix] pmix: breaks openmpi autopkgtest
Added indication that 978066 affects src:deal.ii

-- 
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]

Source: pmix
Version: 4.0.0~rc1-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:deal.ii
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Hi Maintainer

The upload of pmix 4.0.0~rc1-1 to unstable causes the autopkgtests of
openmpi in testing to fail [1].  I've copied what I hope is the
relevant part of the log below.

There's also a FTBFS in the recent binNMU of deal.ii [2]. I believe
this is related to pmix rather than openmpi as the binNMU failed in
Ubuntu as well, where they have the new pmix, but not the new openmpi.

Regards
Graham


[1] https://ci.debian.net/packages/o/openmpi/testing/amd64/
[2] https://buildd.debian.org/status/package.php?p=deal.ii=unstable


autopkgtest [06:32:43]: test hello2: [---
[ci-359-a03b0931:01932] *** Process received signal ***
[ci-359-a03b0931:01932] Signal: Segmentation fault (11)
[ci-359-a03b0931:01932] Signal code: Invalid permissions (2)
[ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70
[ci-359-a03b0931:01932] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00]
[ci-359-a03b0931:01932] [ 1] [0x5632cd610c70]
[ci-359-a03b0931:01932] *** End of error message ***
Segmentation fault
autopkgtest [06:32:46]: test hello2: ---]
autopkgtest [06:32:46]: test hello2:  - - - - - - - - - - results - -
- - - - - - - -
hello2   FAIL non-zero exit status 139
autopkgtest [06:32:46]: test hello2:  - - - - - - - - - - stderr - - -
- - - - - - -
[ci-359-a03b0931:01932] *** Process received signal ***
[ci-359-a03b0931:01932] Signal: Segmentation fault (11)
[ci-359-a03b0931:01932] Signal code: Invalid permissions (2)
[ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70
[ci-359-a03b0931:01932] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00]
[ci-359-a03b0931:01932] [ 1] [0x5632cd610c70]
[ci-359-a03b0931:01932] *** End of error message ***
Segmentation fault
autopkgtest [06:32:47]: test hello4: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 18479 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [06:32:53]: test hello4: [---
[ci-359-a03b0931:02130] *** Process received signal ***
[ci-359-a03b0931:02130] Signal: Segmentation fault (11)
[ci-359-a03b0931:02130] Signal code: Invalid permissions (2)
[ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00
[ci-359-a03b0931:02130] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00]
[ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00]
[ci-359-a03b0931:02130] *** End of error message ***
Segmentation fault
autopkgtest [06:32:54]: test hello4: ---]
autopkgtest [06:32:55]: test hello4:  - - - - - - - - - - results - -
- - - - - - - -
hello4   FAIL non-zero exit status 139
autopkgtest [06:32:55]: test hello4:  - - - - - - - - - - stderr - - -
- - - - - - -
[ci-359-a03b0931:02130] *** Process received signal ***
[ci-359-a03b0931:02130] Signal: Segmentation fault (11)
[ci-359-a03b0931:02130] Signal code: Invalid permissions (2)
[ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00
[ci-359-a03b0931:02130] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00]
[ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00]
[ci-359-a03b0931:02130] *** End of error message ***
Segmentation fault
autopkgtest [06:32:55]:  summary
hello1   FAIL non-zero exit status 139
hello2   FAIL non-zero exit status 139
hello4   FAIL non-zero exit status 139

Processed: again not fixed

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #977960 {Done: Xavier Guimard } [libjs-jquery] dangling 
/usr/share/javascript/jquery/jquery.js symlink
'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 node-jquery/3.5.1+dfsg+~3.5.5-3.
> found -1 3.5.1+dfsg+~3.5.5-3
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js 
symlink
Marked as found in versions node-jquery/3.5.1+dfsg+~3.5.5-3.

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

Bug#977960: again not fixed

[Matthias Klose]

Control: reopen -1
Control: found -1 3.5.1+dfsg+~3.5.5-3

the changelog reads:

  * Team upload
  * libjs-jquery must require node-jquery with the same version
(Closes: #977960)

and after the upgrade:

$ ls -l /usr/share/nodejs/jquery/dist/
total 0
lrwxrwxrwx 1 root root 34 Dec 23 22:00 jquery.js ->
../../nodejs/jquery/dist/jquery.js
lrwxrwxrwx 1 root root 38 Dec 23 22:00 jquery.min.js ->
../../nodejs/jquery/dist/jquery.min.js
lrwxrwxrwx 1 root root 45 Dec 23 22:00 jquery.min.js.brotli ->
../../nodejs/jquery/dist/jquery.min.js.brotli
lrwxrwxrwx 1 root root 41 Dec 23 22:00 jquery.min.js.gz ->
../../nodejs/jquery/dist/jquery.min.js.gz
lrwxrwxrwx 1 root root 39 Dec 23 22:00 jquery.min.map ->
../../nodejs/jquery/dist/jquery.min.map
lrwxrwxrwx 1 root root 46 Dec 23 22:00 jquery.min.map.brotli ->
../../nodejs/jquery/dist/jquery.min.map.brotli
lrwxrwxrwx 1 root root 42 Dec 23 22:00 jquery.min.map.gz ->
../../nodejs/jquery/dist/jquery.min.map.gz

I would appreciate if you could do a little bit more engineering instead of
witchcraft to fix this issue.  How would tightening of the depends have an
effect on this?

With every such upload you also trigger thousands auf autopkg tests, doomed to
be invalid with the next upload.

As I said earlier:

> please could you check an upgrade path from the last versions?
> snapshot.debian.org should have these packages.

> You also could create such a directory with the symlinks and check that the
> upgrade works.

Finding out how you got into this situation would be the preferred first thing
to do.  If you don't want to spend that time, think about how to fix the issue.
E.g. would it be ok to remove these symlinks in a preinst, guarding that fix to
only apply to versions until the version that fixes the issue?

Merry XMas, Matthias

Bug#978008: marked as done (libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE")

[Debian Bug Tracking System]

Your message dated Fri, 25 Dec 2020 11:26:51 +0200
with message-id <54795d1c-995b-c091-5206-1c521130d...@gmail.com>
and subject line Close 978008
has caused the Debian Bug report #978008,
regarding libkwaylandserver5: undefined symbol: 
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
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.)


-- 
978008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkwaylandserver5
Version: 5.20.4-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After today Sid upgrades my KDE desktop failed to fully load after login. I see
background and KDE spinner, but desktop does not appear.

I've found this in `~/.xsession-errors`:
```
/usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5:
undefined symbol:
_ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe
llSurfaceInterfaceE
```

I've downgraded libkwaylandserver5 (to 5.19.5-2), kwayland-integration (to 
5.19.5-3) and
kwayland-data (to 4:5.74.0-2), rebooted and it started working again.

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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

X-CrossAssassin-Score: 21779--- End Message ---

Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"

[Vincas Dargis]

On Thu, 24 Dec 2020 21:56:55 +0900 Norbert Preining  
wrote:

Which version of kwin do you have installed?

Seems like a missing breaks against old versions of kwin or so.


After removing user-manager, full-upgrade upgraded kwin too:
```
Unpacking kwin-x11 (4:5.20.4-3) over (4:5.19.5-3+b1) ...
```

Now my status is this:
```
$ dpkg -l "*kwin*" | fgrep ii
ii  kwin-common4:5.20.4-3   amd64KDE window 
manager, common files
ii  kwin-data  4:5.20.4-3   all  KDE window 
manager data files
ii  kwin-style-breeze  4:5.20.4-2   amd64KWin 
Breeze Style
ii  kwin-x11   4:5.20.4-3   amd64KDE window 
manager, X11 version
ii  libkwin4-effect-builtins1  4:5.20.4-3   amd64KDE window 
manager effect builtins library
ii  libkwineffects12a  4:5.20.4-3   amd64KDE window 
manager effects library
ii  libkwinglutils12   4:5.20.4-3   amd64KDE window 
manager gl utils library
ii  libkwinxrenderutils12  4:5.20.4-3   amd64KDE window 
manager render utils library
ii  qml-module-org-kde-kwindowsystem:amd64 5.77.0-2 amd64provides integration of QML and KDE frameworks - 
kwindowsystem

```



> It seems that I have go perform `full-upgrade` that removes `user-manager`. 
After that KDE desktop works.

Yes, user-manager is going away. It is now a kcm and not a separate
program.


So I guess I've got stuck on just a transition. I thought user-manager removal was one of these 
temporarily-transitional-stuff, so I avoided that. I should have removed it and there would be no issue.


Sorry for the noise.

Bug#978058: simgear FTBFS: error: cannot convert ‘boost::algorithm::split_iterator’ to ‘PathSplitIterator’

[Helmut Grohne]

Source: simgear
Version: 1:2020.3.4+dfsg-1
Severity: serious
Tags: ftbfs

simgear fails to build from source in unstable on amd64. A build ends
with:

| cd /<>/build/simgear && /usr/bin/c++ -DHAVE_CONFIG_H 
-DHAVE_INTTYPES_H -I/<>/build -I/<> 
-I/<>/build/simgear -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -msse2 -mfpmath=sse -ftree-vectorize -ftree-slp-vectorize  
-Wall -fPIC -Wno-unused-local-typedefs  -DBOOST_BIMAP_DISABLE_SERIALIZATION 
-DBOOST_NO_STDLIB_CONFIG -O3 -g -DNDEBUG -msse2 -mfpmath=sse -ftree-vectorize 
-ftree-slp-vectorize -std=gnu++11 -o 
CMakeFiles/SimGearCore.dir/props/props.cxx.o -c 
/<>/simgear/props/props.cxx
| /<>/simgear/props/props.cxx: In function ‘SGPropertyNode* 
find_node(SGPropertyNode*, const Range&, bool, int)’:
| /<>/simgear/props/props.cxx:577:69: error: template argument 1 
is invalid
|   577 |   typedef split_iterator::type>
|   | ^
| /<>/simgear/props/props.cxx: In instantiation of 
‘SGPropertyNode* find_node(SGPropertyNode*, const Range&, bool, int) [with 
Range = boost::iterator_range]’:
| /<>/simgear/props/props.cxx:2113:26:   required from here
| /<>/simgear/props/props.cxx:581:26: error: cannot convert 
‘boost::algorithm::split_iterator’ to ‘PathSplitIterator’ {aka 
‘int’} in initialization
|   581 | = make_split_iterator(path, first_finder("/", is_equal()));
|   |   ~~~^
|   |  |
|   |  boost::algorithm::split_iterator
| make[3]: *** [simgear/CMakeFiles/SimGearCore.dir/build.make:1515: 
simgear/CMakeFiles/SimGearCore.dir/props/props.cxx.o] Error 1
| make[3]: Leaving directory '/<>/build'
| make[2]: *** [CMakeFiles/Makefile2:1810: 
simgear/CMakeFiles/SimGearCore.dir/all] Error 2
| make[2]: Leaving directory '/<>/build'
| make[1]: *** [Makefile:185: all] Error 2
| make[1]: Leaving directory '/<>/build'
| dh_auto_build: error: cd build && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:42: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

This is also seen by crossqa since around 5 days and wasn't an issue 13
days ago:
http://crossqa.debian.net/build/simgear_1:2020.3.4+dfsg-1_s390x_20201218192054.log
http://crossqa.debian.net/src/simgear

Helmut

Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Pirate Praveen]

Control: reopen -1

On Thu, 24 Dec 2020 20:44:50 +0530 Pirate Praveen  
wrote:
> It is fixed by changing the order of plugins used in rollup.config.js, 
> rollup-plugin-polyfills should come before commonjs and node-resolve 
> plugins.

Even though the build now succeed, it is producing a broken output. Size of 
autoprefixer.js dropped from 4.5 mb to 900 kb. It should bundle postcss and 
polyfills.

It may be because newer versions of browsers supporting new features without 
polyfills. But we need to confirm it.

One way could be building the upstream code with build dependencies matching 
the versions in debian. rollup, its plugins or caniuse-db/browserslist update 
may have caused this change.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: Re: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #977900 {Done: Pirate Praveen } [src:node-autoprefixer] 
node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'
'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 node-autoprefixer/10.1.0+~cs11.3.2.0-1.

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

Bug#978051: node-consolidate depends on babel-core 6

[Xavier Guimard]

Package: node-consolidate
Version: 0.15.1+repack-1
Severity: serious

Enabling test proves that node-consolidate depends on node-babel-core 6:

```
  function requireReact(module, filename) {
var babel = requires.babel || (requires.babel = require('babel-core'));
  
var compiled = babel.transformFileSync(filename, { presets: [ 'react' ] 
}).code;
  
return module._compile(compiled, filename);
  }
  
  exports.requireReact = requireReact;
  
  /**
   *  Converting a string into a node module.
   */
  function requireReactString(src, filename) {
var babel = requires.babel || (requires.babel = require('babel-core'));
  
if (!filename) filename = '';
var m = new module.constructor();
filename = filename || '';
  
// Compile Using React
var compiled = babel.transform(src, { presets: [ 'react' ] }).code;
```

Processed: Re: mocha,node-postcss: both ship usr/share/nodejs/nanoid/*

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mocha
Bug #977796 {Done: Xavier Guimard } [mocha,node-postcss] 
mocha,node-postcss: both ship usr/share/nodejs/nanoid/*
Bug reassigned from package 'mocha,node-postcss' to 'mocha'.
No longer marked as found in versions node-postcss/8.2.1+~cs5.3.23-1 and 
node-mocha/8.2.1+ds1+~cs29.4.27-1.
No longer marked as fixed in versions node-mocha/8.2.1+ds1+~cs29.4.27-2.

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

Bug#977796: mocha,node-postcss: both ship usr/share/nodejs/nanoid/*

[Pirate Praveen]

Control: reassign -1 mocha

On Mon, 21 Dec 2020 01:40:48 +0100 Andreas Beckmann  wrote:
> Package: mocha,node-postcss

Fixed in mocha.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.