Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 10:47, Pirate Praveen 
 wrote:



On Tue, 24 Sep, 2019 at 11:16, Simon McVittie  wrote:
Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland 
session

Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:

 After updating gnome to 2.34


I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.



That was a typo, sorry about that, it is 3.34 indeed.

Key GNOME 3.34 components, including gnome-session and gnome-shell, 
are

currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.



Since this was a crash of the desktop I was not really sure which 
component this will belong to.



 I'm not able to use debsign, it crashes the
 desktop. I'm logged out after screen is blacked out.


Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when 
using
debsign and pinentry-gnome3 in conjunction with a smart card 
(Nitrokey

Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.



I looked at apt list --upgradeable | grep gpg and upgraded all the 
components listed (earlier I tried to update all gnome components 
thinking it was an issue with gnome).


gpg-agent/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-client/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-server/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgconf/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgsm/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgv/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
libgpg-error-dev/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpg-error0/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpgme11/unstable 1.13.1-1 amd64 [upgradable from: 1.12.0-6]

After this upgrade there is no crash. pinentry-gnome3 has 
libgpg-error0 (>= 1.16) and I wonder if this should be bumped?




Though it did not crash in the same session, it crashed again after a 
reboot.


Versions of packages pinentry-gnome3 depends on:
ii  gcr  3.28.0-1
ii  libassuan0   2.5.1-2
ii  libc62.29-2
ii  libgcr-base-3-1  3.28.0-1
ii  libglib2.0-0 2.62.0-1
ii  libgpg-error01.36-7
ii  libncursesw6 6.1+20180210-4
ii  libsecret-1-00.18.6-2
ii  libtinfo66.1+20180210-4

Versions of packages pinentry-gnome3 recommends:
ii  dbus-user-session  1.12.8-3

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.34.0-1
ii  gnome-session-common   3.34.0-1
ii  gnome-settings-daemon  3.34.0-2
ii  gnome-shell3.34.0-1

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.31.91-1


smcv

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Tue, 24 Sep, 2019 at 11:16, Simon McVittie  wrote:
Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland 
session

Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:

 After updating gnome to 2.34


I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.



That was a typo, sorry about that, it is 3.34 indeed.

Key GNOME 3.34 components, including gnome-session and gnome-shell, 
are

currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.



Since this was a crash of the desktop I was not really sure which 
component this will belong to.



 I'm not able to use debsign, it crashes the
 desktop. I'm logged out after screen is blacked out.


Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when using
debsign and pinentry-gnome3 in conjunction with a smart card (Nitrokey
Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.



I looked at apt list --upgradeable | grep gpg and upgraded all the 
components listed (earlier I tried to update all gnome components 
thinking it was an issue with gnome).


gpg-agent/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-client/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg-wks-server/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpg/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgconf/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgsm/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
gpgv/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
libgpg-error-dev/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpg-error0/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
libgpgme11/unstable 1.13.1-1 amd64 [upgradable from: 1.12.0-6]

After this upgrade there is no crash. pinentry-gnome3 has libgpg-error0 
(>= 1.16) and I wonder if this should be bumped?



smcv

Processed: retitle 941018 to ibus: Regression from CVE-2019-14822 fix: does not work with qt5 applications

[Debian Bug Tracking System]

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

> retitle 941018 ibus: Regression from CVE-2019-14822 fix: does not work with 
> qt5 applications
Bug #941018 [ibus] ibus 1.5.21-1 does not work with qt5 applications
Changed Bug title to 'ibus: Regression from CVE-2019-14822 fix: does not work 
with qt5 applications' from 'ibus 1.5.21-1 does not work with qt5 applications'.
> thanks
Stopping processing here.

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

Bug#874916: marked as done (RM: imagevis3d -- RoM; dead upstream, no Qt5 port)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 05:05:42 +
with message-id 
and subject line Bug#941106: Removed package(s) from unstable
has caused the Debian Bug report #874916,
regarding RM: imagevis3d -- RoM; dead upstream, no Qt5 port
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.)


-- 
874916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagevis3d
Version: 3.1.0-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 3.1.0-7+rm

Dear submitter,

as the package imagevis3d has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/941106

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 05:04:39 +
with message-id 
and subject line Bug#941066: Removed package(s) from unstable
has caused the Debian Bug report #938221,
regarding python-toscawidgets: 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.)


-- 
938221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-toscawidgets
Version: 0.9.7.2-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-toscawidgets

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 ---
Version: 0.9.7.2-3+rm

Dear submitter,

as the package python-toscawidgets has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/941066

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 05:05:11 +
with message-id 
and subject line Bug#941067: Removed package(s) from unstable
has caused the Debian Bug report #938258,
regarding python-webflash: 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.)


-- 
938258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-webflash
Version: 0.1a9-5
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-webflash

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 ---
Version: 0.1a9-5+rm

Dear submitter,

as the package python-webflash has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/941067

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924757: anjuta: clean after build deletes libanjuta/interfaces/Makefile.am.gir which is not regenerated

[Jeremy Bicha]

On Sat, Mar 16, 2019 at 6:54 PM Andreas Beckmann  wrote:
> Source: anjuta
> Version: 2:3.28.0-6
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Hi,
>
> anjuta/experimental fails to build twice in a row. The first build
> succeeds, but the subsequent clean deletes
> libanjuta/interfaces/Makefile.am.gir which is not regenerated during the
> second build, fausing this to fail with:

My opinion is that I would not consider it a RC bug for a package to
FTBFS twice in a row. For a variety of reasons, I think it makes sense
to build packages from a clean chroot. (By the way, source-only
uploads are now required for updated packages for bullseye.)

Therefore, unless you can point to a clear statement in Debian Policy
or by the Release Team about this particular type of bug, I suggest we
lower this severity and stop the autoremoval of anjuta from Testing.

Or if you come up with a working patch, I would be happy to apply that instead.

Thanks,
Jeremy Bicha

Bug#940105: linux: serious corruption issue with btrfs

[Christoph Anton Mitterer]

Hey.

Is there anything one can help to speed this up?

A patch is available for two weeks now, while Debian users of testing
and unstable are left with the danger of catastrophic btrfs corruption
without even any warning to them (so that they could at least downgrade
to <5.2).

Cheers,
Chris.

Bug#874855: marked as done ([codequery] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 22:21:01 +
with message-id 
and subject line Bug#874855: fixed in codequery 0.21.1+dfsg1-1.1
has caused the Debian Bug report #874855,
regarding [codequery] Future Qt4 removal from Buster
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.)


-- 
874855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codequery
Version: 0.21.0+dfsg1-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: codequery
Source-Version: 0.21.1+dfsg1-1.1

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

Debian distribution maintenance software
pp.
Moritz Muehlenhoff  (supplier of updated codequery package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 21:00:25 +0200
Source: codequery
Architecture: source
Version: 0.21.1+dfsg1-1.1
Distribution: unstable
Urgency: medium
Maintainer: ChangZhuo Chen (陳昌倬) 
Changed-By: Moritz Muehlenhoff 
Closes: 874855 886193
Changes:
 codequery (0.21.1+dfsg1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to Qt5, thanks to Reiner Herrmann (Closes: #874855)
   * Update Qscintilla build dep, thanks to Reiner Herrmann (Closes: #886193)
Checksums-Sha1:
 ff01df579e6a6257648182449a37c39d1d43e8a3 1998 codequery_0.21.1+dfsg1-1.1.dsc
 1a3aa3888acb74f887956394ccf1ae5045843652 11580 
codequery_0.21.1+dfsg1-1.1.debian.tar.xz
 bc9aa138d6fb4d44734825ea8aefa6b7a99e58be 12706 
codequery_0.21.1+dfsg1-1.1_amd64.buildinfo
Checksums-Sha256:
 08f84251b80488e54dc6880070d704c271fdccffe857a6bc058d4671eaa8f960 1998 
codequery_0.21.1+dfsg1-1.1.dsc
 b62561cafce38743e121f54a1c8473f4975a98aecb12b97c8be3aaeb8ac0019a 11580 
codequery_0.21.1+dfsg1-1.1.debian.tar.xz
 9e16d1068eb3d87bf8f83c36a48dd4c7fae68dff1e50fe93eb00d34fb594d8f1 12706 
codequery_0.21.1+dfsg1-1.1_amd64.buildinfo
Files:
 e9ba743ccc4482f50382cdece00d7db9 1998 devel optional 
codequery_0.21.1+dfsg1-1.1.dsc
 30370e417ae9bd2132a9e75d4991a8b6 11580 devel optional 
codequery_0.21.1+dfsg1-1.1.debian.tar.xz
 b5c099d625a1001b0029380d7d77e71f 12706 devel optional 
codequery_0.21.1+dfsg1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Jason Crain]

On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote:
> per Github issue 121 there's no current activity to port scantailor to
> Qt5. Are you planning to switch to the scantailor-advanced fork? Otherwise
> let's remove it, we're now moving forward with removal of Qt4 from Debian
> (and all non-ported reverse dependencies left)

I will not be working on it, but Andreas Noteng has an ITP for
scantailor-advanced (https://bugs.debian.org/940329), which I suggested
could be a "Replaces" for scantailor.

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:09:29PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: scantailor
> Version: 0.9.12.2-3
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

Hi Jason,
per Github issue 121 there's no current activity to port scantailor to
Qt5. Are you planning to switch to the scantailor-advanced fork? Otherwise
let's remove it, we're now moving forward with removal of Qt4 from Debian
(and all non-ported reverse dependencies left)

Cheers,
Moritz

Bug#875150: Should we file a removal bug?

[Moritz Mühlenhoff]

On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi! It seems there is no activity on this bug, should we file a removal bug?

Adding the last two uploaders to CC.

Is anyone of you planning to upload a Qt5 compatible release candidate of 
qtiplot?
Otherwise we'll file a removal bug as we're closing in on the Qt5 removalnow.

(Upload also happen to experimental to avoid a later roundtrip through NEW when 
a final
1.0 comes out)

Cheers,
Moritz

Bug#941105: FTBFS: relocation R_X86_64_TPOFF32 against `tls_serialization_float_format' can not be used when making a shared object

[Magnus Holmgren]

Package: libstorj0
Version: 1.0.3-1
Severity: serious

While rebuilding packages depending on nettle, libstorj failed with the 
following error:

/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -O3 -Wall -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o libstorj.la -rpath /usr/lib storj.lo utils.lo http.lo 
uploader.lo downloader.lo bip39.lo crypto.lo rs.lo -lcurl -lnettle -ljson-c 
-luv -lm 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/storj.o .libs/utils.o 
.libs/http.o .libs/uploader.o .libs/downloader.o .libs/bip39.o .libs/crypto.o 
.libs/rs.o   /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so -lnettle -ljson-c -luv 
-lm  -g -O2 -fstack-protector-strong -O3 -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -pthread -Wl,-soname -Wl,libstorj.so.0 -o 
.libs/libstorj.so.0.0.0
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libjson-c.a(json_object.o):
 relocation R_X86_64_TPOFF32 against `tls_serialization_float_format' can not 
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status

Not sure what's happening there since -fPIC is indeed used.

The full build log is attached.

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer sbuild (Debian sbuild) 0.78.1 (09 February 2019) on johansson.kibibyte.se

+==+
| libstorj (amd64) Tue, 24 Sep 2019 20:03:59 + |
+==+

Package: libstorj
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-amd64-sbuild-2fc154fe-2db6-43fd-b47b-c98ab8b5fc71' 
with '<>'
I: NOTICE: Log filtering will replace 'build/libstorj-wu1kZk/resolver-e6BMLW' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://ftp.se.debian.org/debian sid InRelease [139 kB]
Get:2 http://ftp.se.debian.org/debian sid/main Sources.diff/Index [27.9 kB]
Get:3 http://ftp.se.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 
kB]
Get:4 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-0215.17.pdiff 
[20.1 kB]
Get:5 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-0813.11.pdiff 
[5362 B]
Get:6 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-1416.36.pdiff 
[10.1 kB]
Get:7 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-0215.17.pdiff [22.8 kB]
Get:8 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-0813.11.pdiff [4835 B]
Get:9 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-1416.36.pdiff [8123 B]
Get:6 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-1416.36.pdiff 
[10.1 kB]
Get:9 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-1416.36.pdiff [8123 B]
Fetched 266 kB in 7s (36.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  apt e2fsprogs libapt-pkg5.0 libarchive-zip-perl libattr1 libc-bin
  libc-dev-bin libc6 libc6-dev libcom-err2 libext2fs2 libss2 logsave
13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.1 MB of archives.
After this operation, 100 kB of additional disk space will be used.
Get:1 http://ftp.se.debian.org/debian sid/main amd64 libc6-dev amd64 2.29-2 
[2651 kB]
Get:2 http://ftp.se.debian.org/debian sid/main amd64 libc-dev-bin amd64 2.29-2 
[277 kB]
Get:3 http://ftp.se.debian.org/debian sid/main amd64 libc6 amd64 2.29-2 [2819 
kB]
Get:4 http://ftp.se.debian.org/debian sid/main amd64 libapt-pkg5.0 amd64 1.8.4 
[980 kB]
Get:5 http://ftp.se.debian.org/debian sid/main amd64 apt amd64 1.8.4 [1420 kB]
Get:6 http://ftp.se.debian.org/debian sid/main amd64 libc-bin amd64 2.29-2 [794 
kB]
Get:7 http://ftp.se.debian.org/debian sid/main amd64 logsave amd64 1.45.4-1 
[71.5 kB]
Get:8 http://ftp.se.debian.org/debian sid/main amd64 libext2fs2 amd64 1.45.4-1 
[245 kB]
Get:9 http://ftp.se.debian.org/debian sid/main amd64 e2fsprogs amd64 1.45.4-1 
[590 kB]
Get:10 http://ftp.se.debian.org/debian sid/main amd64 libattr1 amd64 1:2.4.48-5 
[21.5 kB]
Get:11 http://ftp.se.debian.org/debian sid/main amd64 libarchive-zip-perl all 
1.66-2 [103 kB]
Get:12 http://ftp.se.debian.org/debian sid/main amd64 libcom-err2 amd64 
1.45.4-1 [70.8 kB]
Get:13 http://ftp.se.debian.org/debian sid/main amd64 libss2 amd64 1.45.4-1 
[75.3 kB]
debconf: delaying package configuration, since apt-utils is not 

Processed: python-cryptography: diff for NMU version 2.6.1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 940547 + patch
Bug #940547 [python-cryptography] python-cryptography: Testsuite fails with 
OpenSSL 1.1.1d
Added tag(s) patch.
> tags 940547 + pending
Bug #940547 [python-cryptography] python-cryptography: Testsuite fails with 
OpenSSL 1.1.1d
Added tag(s) pending.

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

Bug#940547: python-cryptography: diff for NMU version 2.6.1-3.1

[Sebastian Andrzej Siewior]

Control: tags 940547 + patch
Control: tags 940547 + pending

Dear maintainer,

I've prepared an NMU for python-cryptography (versioned as 2.6.1-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
Sebastian
diff -Nru python-cryptography-2.6.1/debian/changelog python-cryptography-2.6.1/debian/changelog
--- python-cryptography-2.6.1/debian/changelog	2019-03-09 12:25:47.0 +0100
+++ python-cryptography-2.6.1/debian/changelog	2019-09-24 21:10:32.0 +0200
@@ -1,3 +1,12 @@
+python-cryptography (2.6.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport two patches to fix the testsute with newer openssl.
+  * Ignore test_load_ecdsa_no_named_curve in the testsuite because it known to
+break with newer openssl (Closes: #940547).
+
+ -- Sebastian Andrzej Siewior   Tue, 24 Sep 2019 21:10:32 +0200
+
 python-cryptography (2.6.1-3) unstable; urgency=medium
 
   * Fix autopkgtest dependencies.
diff -Nru python-cryptography-2.6.1/debian/patches/series python-cryptography-2.6.1/debian/patches/series
--- python-cryptography-2.6.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ python-cryptography-2.6.1/debian/patches/series	2019-09-24 20:38:45.0 +0200
@@ -0,0 +1,3 @@
+update-our-test-to-be-more-robust-wrt-some-changes-f.patch
+use-a-random-key-for-these-tests-4887.patch
+tests-Skip-test_load_ecdsa_no_named_curve.patch
diff -Nru python-cryptography-2.6.1/debian/patches/tests-Skip-test_load_ecdsa_no_named_curve.patch python-cryptography-2.6.1/debian/patches/tests-Skip-test_load_ecdsa_no_named_curve.patch
--- python-cryptography-2.6.1/debian/patches/tests-Skip-test_load_ecdsa_no_named_curve.patch	1970-01-01 01:00:00.0 +0100
+++ python-cryptography-2.6.1/debian/patches/tests-Skip-test_load_ecdsa_no_named_curve.patch	2019-09-24 20:38:23.0 +0200
@@ -0,0 +1,31 @@
+From: Sebastian Andrzej Siewior 
+Date: Tue, 24 Sep 2019 11:18:27 +0200
+Subject: [PATCH] tests: Skip test_load_ecdsa_no_named_curve
+
+The test_load_ecdsa_no_named_curve breaks with OpenSSL 1.1.1d which is
+due to to commit 9a43a733801bd ("[ec] Match built-in curves on
+EC_GROUP_new_from_ecparameters").
+
+Upstream is aware of the issue and it is tracked at
+	https://github.com/pyca/cryptography/issues/4998
+
+Signed-off-by: Sebastian Andrzej Siewior 
+---
+ tests/x509/test_x509.py | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/tests/x509/test_x509.py b/tests/x509/test_x509.py
+index 07a6019bd1394..c553636f27efe 100644
+--- a/tests/x509/test_x509.py
 b/tests/x509/test_x509.py
+@@ -4122,6 +4122,7 @@ ParsedCertificate = collections.namedtuple(
+ ec.ECDSA(cert.signature_hash_algorithm)
+ )
+ 
++@pytest.mark.skip(reason="Breaks with openssl 1.1.1d, https://github.com/pyca/cryptography/issues/4998;)
+ def test_load_ecdsa_no_named_curve(self, backend):
+ _skip_curve_unsupported(backend, ec.SECP256R1())
+ cert = _load_cert(
+-- 
+2.23.0
+
diff -Nru python-cryptography-2.6.1/debian/patches/update-our-test-to-be-more-robust-wrt-some-changes-f.patch python-cryptography-2.6.1/debian/patches/update-our-test-to-be-more-robust-wrt-some-changes-f.patch
--- python-cryptography-2.6.1/debian/patches/update-our-test-to-be-more-robust-wrt-some-changes-f.patch	1970-01-01 01:00:00.0 +0100
+++ python-cryptography-2.6.1/debian/patches/update-our-test-to-be-more-robust-wrt-some-changes-f.patch	2019-09-24 08:34:23.0 +0200
@@ -0,0 +1,35 @@
+From e575e3d482f976c4a1f3203d63ea0f5007a49a2a Mon Sep 17 00:00:00 2001
+From: Paul Kehrer 
+Date: Wed, 11 Sep 2019 12:12:30 +0800
+Subject: [PATCH] update our test to be more robust wrt some changes from
+ upstream (#4993)
+
+---
+ tests/hazmat/primitives/test_dh.py | 11 +--
+ 1 file changed, 9 insertions(+), 2 deletions(-)
+
+diff --git a/tests/hazmat/primitives/test_dh.py b/tests/hazmat/primitives/test_dh.py
+index c667cd16e1a6b..43f2ce5c0318b 100644
+--- a/tests/hazmat/primitives/test_dh.py
 b/tests/hazmat/primitives/test_dh.py
+@@ -157,8 +157,15 @@ from ...utils import load_nist_vectors, load_vectors_from_file
+ dh.generate_parameters(7, 512, backend)
+ 
+ def test_dh_parameters_supported(self, backend):
+-assert backend.dh_parameters_supported(23, 5)
+-assert not backend.dh_parameters_supported(23, 18)
++valid_p = int(
++b"907c7211ae61aaaba1825ff53b6cb71ac6df9f1a424c033f4a0a41ac42fad3a9"
++b"bcfc7f938a269710ed69e330523e4039029b7900977c740990d46efed79b9bbe"
++b"73505ae878808944ce4d9c6c52daecc0a87dc889c53499be93db8551ee685f30"
++b"349bf1b443d4ebaee0d5e8b441a40d4e8178f8f612f657a5eb91e0a8e"
++b"107755f", 16
++)
++assert backend.dh_parameters_supported(valid_p, 5)
++assert not backend.dh_parameters_supported(23, 22)
+ 
+ @pytest.mark.parametrize(
+ "vector",
+-- 
+2.23.0
+
diff -Nru 

Processed: .

[Debian Bug Tracking System]

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

> forwarded 940547 https://github.com/pyca/cryptography/issues/4998
Bug #940547 [python-cryptography] python-cryptography: Testsuite fails with 
OpenSSL 1.1.1d
Set Bug forwarded-to-address to 
'https://github.com/pyca/cryptography/issues/4998'.
> thanks.
Stopping processing here.

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

Processed: Re: Bug#941097: vips FTBFS on all release architectures: multiple definition of `OrcTargetPowerPCFlags'

[Debian Bug Tracking System]

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

> found 940979 1:0.4.30-1
Bug #940979 [src:orc] orc: OrcTargetPowerPCFlags enum typedef FTBFS
Marked as found in versions orc/1:0.4.30-1.
> notfound 940979 0.4.30-1
Bug #940979 [src:orc] orc: OrcTargetPowerPCFlags enum typedef FTBFS
The source 'orc' and version '0.4.30-1' do not appear to match any binary 
packages
No longer marked as found in versions orc/0.4.30-1.
> severity 940979 serious
Bug #940979 [src:orc] orc: OrcTargetPowerPCFlags enum typedef FTBFS
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#941097: vips FTBFS on all release architectures: multiple definition of `OrcTargetPowerPCFlags'

[Debian Bug Tracking System]

Processing control commands:

> block 941097 by 940979
Bug #941097 [src:vips] vips FTBFS on all release architectures: multiple 
definition of `OrcTargetPowerPCFlags'
941097 was blocked by: 940979
941097 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #941097 to the same blocks 
previously set

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

Processed: block 934627 with 941097

[Debian Bug Tracking System]

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

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

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

Bug#941097: vips FTBFS on all release architectures: multiple definition of `OrcTargetPowerPCFlags'

[GCS]

Control: block 941097 by 940979

Hi Paul,

On Tue, Sep 24, 2019 at 8:30 PM Paul Gevers  wrote:
> Source: vips
> Version: 8.7.4-1
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
[...]
> /usr/bin/ld: 
> conversion/.libs/libconversion.a(composite.o):/usr/include/orc-0.4/orc/orctarget.h:28:
>  multiple definition of `OrcTargetPowerPCFlags'; 
> resample/.libs/libresample.a(reducev.o):/usr/include/orc-0.4/orc/orctarget.h:28:
>  first defined here
> collect2: error: ld returned 1 exit status
 This is known, reported and fixing it depends on the orc maintainers.

Regards,
Laszlo/GCS

Processed: Re: Bug#941097: vips FTBFS on all release architectures: multiple definition of `OrcTargetPowerPCFlags'

[Debian Bug Tracking System]

Processing control commands:

> block 941097 by 940979
Bug #941097 [src:vips] vips FTBFS on all release architectures: multiple 
definition of `OrcTargetPowerPCFlags'
941097 was not blocked by any bugs.
941097 was not blocking any bugs.
Added blocking bug(s) of 941097: 940979

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

Bug#941097: vips FTBFS on all release architectures: multiple definition of `OrcTargetPowerPCFlags'

[Paul Gevers]

Source: vips
Version: 8.7.4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

For the libmatio transition I scheduled binNMU's for vips. All architectures
FTBFS. The reproducible build infrastructure is showing the same (on amd64, the
other archs were still fine on 2019-08-26).

51:5:9  -Wl,-z,relro -Wl,-z,now -o libvips.la -rpath /usr/lib/x86_64-linux-gnu  
resample/libresample.la arithmetic/libarithmetic.la colour/libcolour.la 
conversion/libconversion.la convolution/libconvolution.la 
deprecated/libdeprecated.la foreign/libforeign.la freqfilt/libfreqfilt.la 
histogram/libhistogram.la draw/libdraw.la iofuncs/libiofuncs.la 
morphology/libmorphology.la mosaicing/libmosaicing.la create/libcreate.la -lz 
-lMagickCore-6.Q16 -lpng16 -lz  -ltiff -ljpeg  -Wl,--export-dynamic -pthread 
-lgmodule-2.0 -lgobject-2.0 -lglib-2.0  -lexpat -lpangoft2-1.0 -lpango-1.0 
-lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lgsf-1 -lgobject-2.0 
-lglib-2.0 -lxml2 -lfftw3 -lorc-0.4 -llcms2 -lgif -lrsvg-2 -lm -lgio-2.0 
-lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo   -lpoppler-glib 
-lgobject-2.0 -lglib-2.0 -lcairo -lIlmImf -lImath -lHalf -lIex -lIexMath 
-lIlmThread -lpthread -lopenslide -lcfitsio -lpthread -lwebp -lwebpmux -lwebp 
-L/usr/lib/x86_64-linux-gnu/hdf5/serial/lib -lmatio -lhdf5 -lz -lexif -lm 
libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crti.o 
/usr/lib/gcc/x86_64-linux-gnu/9/crtbeginS.o  -Wl,--whole-archive 
resample/.libs/libresample.a arithmetic/.libs/libarithmetic.a 
colour/.libs/libcolour.a conversion/.libs/libconversion.a 
convolution/.libs/libconvolution.a deprecated/.libs/libdeprecated.a 
foreign/.libs/libforeign.a freqfilt/.libs/libfreqfilt.a 
histogram/.libs/libhistogram.a draw/.libs/libdraw.a iofuncs/.libs/libiofuncs.a 
morphology/.libs/libmorphology.a mosaicing/.libs/libmosaicing.a 
create/.libs/libcreate.a -Wl,--no-whole-archive  
/usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so -lpng16 -ltiff -ljpeg 
-lgmodule-2.0 -lexpat -lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype 
-lgsf-1 -lxml2 -lfftw3 -lorc-0.4 -llcms2 -lgif -lrsvg-2 -lgio-2.0 
-lgdk_pixbuf-2.0 -lpoppler-glib -lgobject-2.0 -lglib-2.0 -lcairo -lIlmImf 
-lImath -lHalf -lIex -lIexMath -lIlmThread -lopenslide -lcfitsio -lpthread 
-lwebpmux -lwebp -L/usr/lib/x86_64-linux-gnu/hdf5/serial/lib -lmatio -lhdf5 -lz 
-lexif -L/usr/lib/gcc/x86_64-linux-gnu/9 
-L/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/9/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/x86_64-linux-gnu/9/crtendS.o 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crtn.o  -g -O2 
-fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--export-dynamic 
-pthread   -pthread -fopenmp -Wl,-soname -Wl,libvips.so.42 -o 
.libs/libvips.so.42.9.5
/usr/bin/ld: 
conversion/.libs/libconversion.a(composite.o):/usr/include/orc-0.4/orc/orctarget.h:28:
 multiple definition of `OrcTargetPowerPCFlags'; 
resample/.libs/libresample.a(reducev.o):/usr/include/orc-0.4/orc/orctarget.h:28:
 first defined here
collect2: error: ld returned 1 exit status

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
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=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2KYCwACgkQnFyZ6wW9
dQrFZgf/fZeyd2D4my4iqiF1OZYQ8xjWQYY1kgZRO0aDJaHBT93pFv9Ez5B3i4yI
uuPRWpGGrM/9ixElSjBcm31iSqOQoT9DgByT1JuDhNTYlLODfHoeHxvYpM4umQm/
lPEdETGykLnwfVIl+sHlsO++6q12kh8OKsjPocft1K7PNzZnGaddvJWS8TMHm7vv
NvyACuqqGs9DT/0hA8Ao1quHNFhYTB7aulpz5GvgYoXCz4v6t7KK/nbiFzoGyea+
9zVgdR0m0+exDAwR3FzWzKqnsJvLbVwWlLnw89wuQRCRCf1kaFvyPQBLr5U+ku3T
uxLCT2/VhA/gRjQlUU00VWpHDpOutQ==
=3/Rm
-END PGP SIGNATURE-

Bug#940939: marked as done (plasma-discover: After KDE Frameworks 5.62 update plasma-discover doesn't start)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 18:04:19 +
with message-id 
and subject line Bug#940939: fixed in kirigami2 5.62.0-2
has caused the Debian Bug report #940939,
regarding plasma-discover: After KDE Frameworks 5.62 update plasma-discover 
doesn't start
to be marked as done.

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

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


-- 
940939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-discover
Version: 5.14.5.1-1
Severity: normal

After KDE Frameworks 5.62 update plasma-discover doesn't start.

$ /usr/bin/plasma-discover
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:46 Type TopLevelPageData unavailable
qrc:/qml/TopLevelPageData.qml:22 Type Action unavailable
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Action.qml:21
module "QtQuick.Controls" version 2.5 is not installed

org.kde.plasma.discover: Errors when loading the GUI
adding empty sources model QStandardItemModel(0x55c8b2c0ef60)
no packages for "org.kde.plasma.quicklaunch"
no packages for "org.kde.plasma.systemloadviewer"
no packages for "org.kde.plasma.showActivityManager"
no packages for "de.urwpp.URWCoreFontSetLevel2"
no packages for "libgphoto2"
no packages for "org.kde.plasma.grouping"
no packages for "org.kde.konqueror.desktop"
no packages for "org.kde.plasma.diskquota"
no packages for "org.kde.plasma.timer"
no packages for "org.kde.kscreen"
no packages for "libu2f-udev"
no packages for "org.kde.plasma.activitybar"
no packages for "org.kde.jovie.desktop"
no packages for "org.kde.plasma.appmenu"
no packages for "org.kde.plasma.binaryclock"
no packages for "org.kde.plasma.kimpanel"
no packages for "im.riot.webapp"
no packages for "org.debian.debian"
no packages for "io.devdocs.webapp"
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."



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

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

Versions of packages plasma-discover depends on:
ii  appstream0.12.8-1
ii  apt-config-icons 0.12.8-1
ii  kio  5.62.1-1
ii  libappstreamqt2  0.12.8-1
ii  libc62.29-2
ii  libkf5attica55.62.0-1
ii  libkf5configcore55.62.0-1
ii  libkf5configwidgets5 5.62.0-1
ii  libkf5coreaddons55.62.0-1
ii  libkf5crash5 5.62.0-1
ii  libkf5dbusaddons55.62.0-1
ii  libkf5i18n5  5.62.0-1
ii  libkf5itemmodels55.62.0-1
ii  libkf5kiocore5   5.62.1-1
ii  libkf5kiowidgets55.62.1-1
ii  libkf5newstuffcore5  5.62.0-1
ii  libkf5notifications5 5.62.0-1
ii  libkf5service-bin5.62.0-1
ii  libkf5service5   5.62.0-1
ii  libkf5widgetsaddons5 5.62.0-1
ii  libkf5xmlgui55.62.0-1
ii  libpackagekitqt5-1   1.0.1-1+b1
ii  libqt5core5a 5.11.3+dfsg1-4
ii  libqt5dbus5  5.11.3+dfsg1-4
ii  libqt5gui5   5.11.3+dfsg1-4
ii  libqt5network5   5.11.3+dfsg1-4
ii  libqt5qml5   5.11.3-4
ii  libqt5quick5 5.11.3-4
ii  libqt5widgets5   5.11.3+dfsg1-4
ii  libqt5xml5   5.11.3+dfsg1-4
ii  libstdc++6   9.2.1-8
ii  packagekit   1.1.12-5+b1
ii  plasma-discover-common   5.14.5.1-1
ii  qml-module-org-kde-kcoreaddons   5.62.0-1
ii  qml-module-org-kde-kirigami2 5.62.0-1
ii  qml-module-org-kde-kquickcontrols5.62.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.62.0-1
ii  

Processed: Re: Bug#939038: qtwebengine-opensource-src: FTBFS with libvpx6

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 qtwebengine-opensource-src/5.12.2+dfsg-1
Bug #939038 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Bug #939039 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
The source qtwebengine-opensource-src and version 5.12.2+dfsg-1 do not appear 
to match any binary packages
Marked as fixed in versions qtwebengine-opensource-src/5.12.2+dfsg-1.
Marked as fixed in versions qtwebengine-opensource-src/5.12.2+dfsg-1.

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

Bug#939038: qtwebengine-opensource-src: FTBFS with libvpx6

[Dmitry Shachnev]

Control: fixed -1 qtwebengine-opensource-src/5.12.2+dfsg-1

On Sat, Aug 31, 2019 at 01:09:42PM +0100, Jonathan Wiltshire wrote:
> During a rebuild for the libvpx6 transition qtwebengine-opensource-src
> failed to build from source. [...]
>
> https://buildd.debian.org/status/package.php?p=qtwebengine-opensource-src

The failing code was removed in [1], so backporting that may help.

However, the Qt WebEngine 5.12 branch builds cleanly, and I have just filed
a transition bug [2]. So just uploading 5.12.5 to unstable may be the easiest
thing to do.

[1]: https://webrtc-review.googlesource.com/c/src/+/76801/
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941093

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: severity of 941091 is important

[Debian Bug Tracking System]

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

> severity 941091 important
Bug #941091 [golang-github-docker-docker-dev] golang-github-docker-docker-dev: 
/usr/share/gocode/src/github.com/containerd/* already shipped by 
golang-github-containerd-containerd-dev
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#941091: golang-github-docker-docker-dev: /usr/share/gocode/src/github.com/containerd/* already shipped by golang-github-containerd-containerd-dev

[Andreas Beckmann]

Package: golang-github-docker-docker-dev
Version: 18.09.9+dfsg1-3
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.

The recent upload of golang-github-docker-docker-dev contains the
following files, which are already provided by
golang-github-containerd-containerd-dev/experimental:

usr/share/gocode/src/github.com/containerd/containerd/cio/io.go
usr/share/gocode/src/github.com/containerd/containerd/cio/io_test.go
usr/share/gocode/src/github.com/containerd/containerd/cio/io_unix.go
usr/share/gocode/src/github.com/containerd/containerd/cio/io_unix_test.go
usr/share/gocode/src/github.com/containerd/containerd/cio/io_windows.go
usr/share/gocode/src/github.com/containerd/containerd/defaults/defaults.go
usr/share/gocode/src/github.com/containerd/containerd/defaults/defaults_unix.go
usr/share/gocode/src/github.com/containerd/containerd/defaults/defaults_windows.go
usr/share/gocode/src/github.com/containerd/containerd/defaults/doc.go
usr/share/gocode/src/github.com/containerd/containerd/log/context.go
usr/share/gocode/src/github.com/containerd/containerd/log/context_test.go

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

  Preparing to unpack 
.../golang-github-containerd-containerd-dev_1.2.4~ds1-1_all.deb ...
  Unpacking golang-github-containerd-containerd-dev (1.2.4~ds1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-containerd-containerd-dev_1.2.4~ds1-1_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/containerd/containerd/cio/io.go', which is 
also in package golang-github-docker-docker-dev 18.09.9+dfsg1-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-containerd-containerd-dev_1.2.4~ds1-1_all.deb


cheers,

Andreas


golang-github-docker-docker-dev=18.09.9+dfsg1-3_golang-github-containerd-containerd-dev=1.2.4~ds1-1.log.gz
Description: application/gzip

Bug#940939: Bug

[Matthieu Gallien]

On Sunday, September 22, 2019 9:24:58 PM CEST you wrote:
> Hello,
> 
> Sorry for the confusion, the fix proposal is in https://phabricator.kde.org/
> D24147 .
> 
> Best regards

https://phabricator.kde.org/D24147 has landed in master branch of Kirigami2

Bug#941055: marked as done (dtkwm FTBFS: Project ERROR: set DTK_MODULE_NAME first)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 11:06:33 -0400
with message-id 

and subject line Re: [Pkg-deepin-devel] Bug#941055: dtkwm FTBFS: Project ERROR: 
set DTK_MODULE_NAME first
has caused the Debian Bug report #941055,
regarding dtkwm FTBFS: Project ERROR: set DTK_MODULE_NAME first
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.)


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

dtkwm fails to build from source in unstable. A build ends with:

|dh_auto_build
|  make -j16
| make[1]: Entering directory '/build/1st/dtkwm-2.0.9'
| cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile 
/build/1st/dtkwm-2.0.9/src/src.pro 'QMAKE_CFLAGS_RELEASE=-g -O2 
-ffile-prefix-map=/build/1st/dtkwm-2.0.9=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 
-ffile-prefix-map=/build/1st/dtkwm-2.0.9=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CXXFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2' 'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed' 'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile
| Project ERROR: set DTK_MODULE_NAME first
| make[1]: *** [Makefile:46: sub-src-make_first-ordered] Error 3
| make[1]: Leaving directory '/build/1st/dtkwm-2.0.9'
| dh_auto_build: make -j16 returned exit code 2
| make: *** [debian/rules:35: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

See for instance 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/dtkwm_2.0.9-3.rbuild.log.gz

Helmut
--- End Message ---
--- Begin Message ---
Version: 2.0.12-1

Fixed in the latest upload.

Thanks,
Boyuan Yang

Helmut Grohne  于2019年9月24日周二 上午12:21写道：
>
> Source: dtkwm
> Version: 2.0.9-3
> Severity: serious
> Tags: ftbfs
>
> dtkwm fails to build from source in unstable. A build ends with:
>
> |dh_auto_build
> |  make -j16
> | make[1]: Entering directory '/build/1st/dtkwm-2.0.9'
> | cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile 
> /build/1st/dtkwm-2.0.9/src/src.pro 'QMAKE_CFLAGS_RELEASE=-g -O2 
> -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2' 
> 'QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 
> -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
> 'QMAKE_CXXFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/build/1st/dtkwm-2.0.9=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2' 'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed' 'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
> QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile
> | Project ERROR: set DTK_MODULE_NAME first
> | make[1]: *** [Makefile:46: sub-src-make_first-ordered] Error 3
> | make[1]: Leaving directory '/build/1st/dtkwm-2.0.9'
> | dh_auto_build: make -j16 returned exit code 2
> | make: *** [debian/rules:35: build] Error 255
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
>
> See for instance 
> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/dtkwm_2.0.9-3.rbuild.log.gz
>
> Helmut
>
> ___
> Pkg-deepin-devel mailing list
> pkg-deepin-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-deepin-devel--- End Message ---

Bug#941059: marked as done (libjson-c-dev: broken so symlink)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 14:48:53 +
with message-id 
and subject line Bug#941059: fixed in json-c 0.13.1+dfsg-6
has caused the Debian Bug report #941059,
regarding libjson-c-dev: broken so symlink
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.)


-- 
941059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjson-c-dev
Version: 0.13.1+dfsg-5
Severity: serious

After the last update:

% ls -l /usr/lib/x86_64-linux-gnu/libjson-c.so
lrwxrwxrwx 1 root root 36 Sep 24 01:31 /usr/lib/x86_64-linux-gnu/libjson-c.so 
-> /lib/x86_64-linux-gnu/libjson-c.so.4

But:

% ls /lib/x86_64-linux-gnu/libjson-c.so.4
ls: cannot access '/lib/x86_64-linux-gnu/libjson-c.so.4': No such file or 
directory

Cheers

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

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

Versions of packages libjson-c-dev depends on:
ii  libjson-c4  0.13.1+dfsg-5

libjson-c-dev recommends no packages.

libjson-c-dev suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: json-c
Source-Version: 0.13.1+dfsg-6

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated json-c package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 10:12:44 -0400
Source: json-c
Architecture: source
Version: 0.13.1+dfsg-6
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 941059
Changes:
 json-c (0.13.1+dfsg-6) unstable; urgency=high
 .
   * QA upload.
   * debian/libjson-c4-dev.links: Fix broken so symlink and make
 everything unified under /usr/lib. (Closes: #941059)
Checksums-Sha1:
 72e9f7e9f9459e2a7c34bac3bdafcb9836367664 2072 json-c_0.13.1+dfsg-6.dsc
 088e20ce0d190fcb6e009acd66cead85ca7458eb 6568 
json-c_0.13.1+dfsg-6.debian.tar.xz
 174e8d3bcf6139eac912ca7ebf9ce6c5bd07aa02 6904 
json-c_0.13.1+dfsg-6_amd64.buildinfo
Checksums-Sha256:
 aa3f413f162c918e7ebe7b90d6fca1cb0eaaf19770489e32f2cb5a94cc8d18b2 2072 
json-c_0.13.1+dfsg-6.dsc
 7212b859fc76699f18112825af796be33771f4542d3c410a7b37c965863e2ad0 6568 
json-c_0.13.1+dfsg-6.debian.tar.xz
 0a0f182eff8fe1623a1b3ad0bf7fe28329e9de0f1e0a775796cd499b79859af3 6904 
json-c_0.13.1+dfsg-6_amd64.buildinfo
Files:
 7ce5f2000a473e61f0175bc09f70e39f 2072 libs optional json-c_0.13.1+dfsg-6.dsc
 8c1906bef784060488bb9476813cb357 6568 libs optional 
json-c_0.13.1+dfsg-6.debian.tar.xz
 0fddeed1f2df80b9890956946140f2d8 6904 libs optional 
json-c_0.13.1+dfsg-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl2KJekACgkQwpPntGGC
Ws4NRRAAqGNeoNn4GVjmYIfEYffANyICnHeOrnC+xzclx5sAcysblIXxPTSBHUl1
Z2+fcZR91K1BeQiK1wpzf9OFstjMYxFH5pHQsMzWzoc9vk6J90W2PG3gql8GBc3o
j3CbtbFR8LEbhZGSLjGQzQVRCplsVJXgh82CLIe4FkvgEt/Q1k+GRsaSieRWqbCH
K54/qaXp4jvfiUYRQbtAw7bXGvfdGBd+ClWmS8gYuHUIxu/ywCTSY9XkrB2N1e8Z
MTWcMn+CsZfZecUf59al1Xo/3NwB6ZRXnTgBy2hdlsZ/Ms/iBMq5xb6AWTBjMJxV
LywUZQPPhrBbaDRIU1JboVY3eU3v/PoS39RyBh+6PtYDJL01jBWnjil1fOE7ZbNq
PSpkmR9Vt0NHSa2Exrcc7fmQzx8e0rEss+F0OV5gimwF2AbYTyUnEWspL8BcAzxl
gFEjgnnPNqh7XU3c/W4FwtudLe1Kw7Nzf+793NtAO1Pl/3SOXVsRkmMPOmUY+CKl
45MrHKjCBr+dNXTnccyK82RZq4meUADAguYUMiXmIGJKEPKVXv/3UZxOtfeNirtk
xjorBsoYSITzuYOrMXTVkQw8nceJrJ4CDDRgwBBaM6FsrB27IYsDgD/YutXOqxEb
3n7iXYMOVTB+/MmeS6TYtRrk0N1mnov/j05d2UouYCW3QCuxTh8=
=DOIy
-END PGP SIGNATURE End 

Processed: Re: Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #940973 {Done: gregor herrmann } 
[src:libarchive-zip-perl] libarchive-zip-perl breaks strip-nondeterminism 
autopkgtest: error: becoming Archive::Zip::DirectoryMember
'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 libarchive-zip-perl/1.66-2.
> found -1 1.66-2
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Marked as found in versions libarchive-zip-perl/1.66-2.
> affects -1 + strip-nondeterminism
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Ignoring request to set affects of bug 940973 to the same value previously set
> tags -1 - fixed-upstream
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Removed tag(s) fixed-upstream.

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

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[gregor herrmann]

Control: reopen -1
Control: found -1 1.66-2
Control: affects -1 + strip-nondeterminism
Control: tags -1 - fixed-upstream

On Mon, 23 Sep 2019 18:47:44 +0200, gregor herrmann wrote:

> On Mon, 23 Sep 2019 13:02:04 +0100, Chris Lamb wrote:
> 
> > This has been fixed upstream here:
> >   
> > https://github.com/farblos/perl-Archive-Zip/commit/b0179cbbfeb276ceac0f424d32acf56811b01568
> Thanks for the analysis!
> I've now uploaded -2 with this patch (minus 2 not applying but
> irrelevant hunks) plus the previous commit which also touches on the
> same topic. Will monitor the behaviour a bit :)

And the result of the monitoring is: 1.66-2 breaks strip-nondeterminism
as well:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/3020870/log.gz

#v+
Reading ZIP archive failed: IO error: reading local extra field :  

error: becoming Archive::Zip::DirectoryMember 
# Looks like your test exited with 29 just after 20.
#v-

Looks like this needs more investigation …


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Dido: Slide


signature.asc
Description: Digital Signature

Processed: bug 940939 is forwarded to https://phabricator.kde.org/D24147

[Debian Bug Tracking System]

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

> forwarded 940939 https://phabricator.kde.org/D24147
Bug #940939 [src:kirigami2] plasma-discover: After KDE Frameworks 5.62 update 
plasma-discover doesn't start
Changed Bug forwarded-to-address to 'https://phabricator.kde.org/D24147' from 
'https://phabricator.kde.org/D22974'.
> thanks
Stopping processing here.

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

Processed: Confirm bug 941059

[Debian Bug Tracking System]

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

> tags 941059 + confirmed
Bug #941059 [libjson-c-dev] libjson-c-dev: broken so symlink
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#940604: marked as done (dhcpig depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 13:49:28 +
with message-id 
and subject line Bug#940604: fixed in dhcpig 1.5-3
has caused the Debian Bug report #940604,
regarding dhcpig depends on cruft package.
to be marked as done.

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

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


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

Package: dhcpig
Version: 1.5-2
Severity: serious
Tags: bullseye, sid

dhcpig depends on python-scapy which is no longer built by the scapy source 
package.

If you want your package to remain around you probably need to migrate to 
python 3.
--- End Message ---
--- Begin Message ---
Source: dhcpig
Source-Version: 1.5-3

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

Debian distribution maintenance software
pp.
Philippe Thierry  (supplier of updated dhcpig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 14:09:19 +0200
Source: dhcpig
Architecture: source
Version: 1.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Philippe Thierry 
Closes: 940604
Changes:
 dhcpig (1.5-3) unstable; urgency=medium
 .
   * Add support for Python3 (Closes: 940604)
Checksums-Sha1:
 272f4dfa879ffddeaee62427f0adae7b5632ab74 1950 dhcpig_1.5-3.dsc
 e0df8303d88b3e4a5bc8d4a9a1f24639c225fda8 4980 dhcpig_1.5-3.debian.tar.xz
 e2c4660295a507e7bd6cb1118f304c8b09279257 6127 dhcpig_1.5-3_amd64.buildinfo
Checksums-Sha256:
 953da03e4fdcb3f28d767ba6d5dbf3eb2d4bcf8ad2c0d16de694fe9331e7f2db 1950 
dhcpig_1.5-3.dsc
 d86042086f4e866d29750d59ec630c7b275950bf86d93040470088e179ee246b 4980 
dhcpig_1.5-3.debian.tar.xz
 00b897e72d71f88107c864a174181fd7539b5dc749bc79612af686dab8ee4362 6127 
dhcpig_1.5-3_amd64.buildinfo
Files:
 9c143cdc7b37e50611d0418d3de40d5c 1950 net optional dhcpig_1.5-3.dsc
 1705294e7ca3d67d60c1f04e4f1c1fb3 4980 net optional dhcpig_1.5-3.debian.tar.xz
 c2a4d723d9362cd4478d6008bfeb5f7d 6127 net optional dhcpig_1.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/N321ye0S80G/xoyyJ1XEt+UX28FAl2KGX4ACgkQyJ1XEt+U
X2/gew//Xu1Ec6ZqB/DP/sKxn/DsU0+1kx6gMtGxFk5EF4E2N5Au8NSWSp2NQmZQ
oIMl+UrIk2rxdGoQPn8ZBYmvp1mY6t5esJrbfAU8RmtazX5cVpyCtcMTnkIZTaBg
LEAwZRRrDGscsnHjEZ5nXqBVbgFmVvNs80LL2dzA5KTmzTyesX4aH3MUWqlyzTmV
CqCBmdZxrEHFWLn98iN+cNxUCid4yYgoH0jwazSvKSyzkJI+rZ2BXjdm3371Elmi
2DaaSLCy2sJkkHJbLpTHZZPrCJB1xJfxQT5M+tciiaCT5QDwyUVyBabCL80U3ZW0
yO2b2CQA+WRxStGlLXgP+SCtKkGOXlvBSYSKS2VRRDxc1sqRmmjWIpj3dAlv9xXB
OfVZ/Trt0E9li2cE7qwJbT5Qc3x5Rz8ym0dnNYo7UPBGX+17tEtosU+BchjHqyHM
DK9CYBn1227ztSbnYNdJptjHjeEalBELH+c3xebDvWGo6tTbKMiJgLBPSpAcT3aF
kbJVgshaRixpVsXhSvmj9Mz6riTS9/ftr49CufMI0avAIJ+/usuDNbR5K3PjQkma
+MDrz56FwUgGawewnOByPJid9qI2cy++hBUC78GzQRQT6izZVtEV7BD5sVoTUYGJ
5DrFxA/467rv5D6geA8fBpoXHXYdwhHhduXZfblbD/+oRXCsZtM=
=xhHB
-END PGP SIGNATURE End Message ---

Bug#934350: Debug make.log

[Jan Huijsmans]

Hi,

I found this bug as well on my server, after findingloads of ssh
probes in the iptables logging that should be dropped by the geoip
module. The issue is with the 5.2.0 kernel. I started with
xtables-addons 2.12 and got an error on line 472 of the same 
C file (.._timer was not found, suggested that this should be
..._timers). Alas I forgot to save that log.

Fall-back for me was to install a 4.19 kernel (4.19.0-6 from sid
repo, few minutes ago) The 4.19.0-6 kernel is now running nicely
with the 3.2-1 xtables-addons active.

Log of the 3.2-1 build:


DKMS make.log for xtables-addons-3.2 for kernel 5.2.0-2-amd64 (x86_64)
Tue 24 Sep 14:58:27 CEST 2019
make: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64'
make -C /usr/src/linux-headers-5.2.0-2-amd64 -f 
/usr/src/linux-headers-5.2.0-2-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
mkdir -p /var/lib/dkms/xtables-addons/3.2/build/extensions/.tmp_versions ; rm 
-f /var/lib/dkms/xtables-addons/3.2/build/extensions/.tmp_versions/*
make -f /usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build 
obj=/var/lib/dkms/xtables-addons/3.2/build/extensions
make -f /usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build 
obj=/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT need-builtin=
   gcc-8 
-Wp,-MD,/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/.xt_ACCOUNT.o.d
  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/8/include 
-I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include 
-I./arch/x86/include/generated -I/usr/src/linux-headers-5.2.0-2-common/include 
-I./include -I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-5.2.0-2-common/include/uapi -I./include/generated/uapi 
-include /usr/src/linux-headers-5.2.0-2-common/include/linux/kconfig.h -include 
/usr/src/linux-headers-5.2.0-2-common/include/linux/compiler_types.h 
-D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security 
-std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 
-mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel 
-DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 
-DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 
-DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables 
-mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables 
-fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation 
-Wno-format-overflow -O2 --param=allow-store-data-races=0 
-Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable 
-Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mrecord-mcount 
-mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla 
-Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow 
-fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack 
-Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init 
-fmacro-prefix-map=/usr/src/linux-headers-5.2.0-2-common/= 
-Wno-packed-not-aligned 
-I/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/..  -DMODULE  
-DKBUILD_BASENAME='"xt_ACCOUNT"' -DKBUILD_MODNAME='"xt_ACCOUNT"' -c -o 
/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/xt_ACCOUNT.o 
/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/xt_ACCOUNT.c
   ./tools/objtool/objtool orc generate  --module --no-fp --retpoline --uaccess 
/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/xt_ACCOUNT.o
  if objdump -h 
/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/xt_ACCOUNT.o | grep 
-q __ksymtab; then  gcc-8 -E -D__GENKSYMS__ 
-Wp,-MD,/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT/.xt_ACCOUNT.o.d
  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/8/include 
-I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include 
-I./arch/x86/include/generated -I/usr/src/linux-headers-5.2.0-2-common/include 
-I./include -I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-5.2.0-2-common/include/uapi -I./include/generated/uapi 
-include /usr/src/linux-headers-5.2.0-2-common/include/linux/kconfig.h -include 

Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers'

[Thorsten Glaser]

Hi,

I’ve had to downgrade in the meantime, since #935734 at least
has a workaround.

FWIW, the GNU Guix people have the same problem, and with a
different path, others:

https://www.redhat.com/archives/libvir-list/2019-July/msg01310.html
https://bugzilla.redhat.com/show_bug.cgi?id=1751120

I have this:

tglase@tglase:~ $ mount | fgrep cgroup
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/elogind type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind/elogind-cgroups-agent,name=elogind)

So, s!/machine!! on the path would most likely make it work.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Ian Campbell]

On Tue, 2019-09-24 at 10:05 +0100, Mark Hindley wrote:
> Ian,
> 
> Thanks for this.
> 
> On Tue, Sep 24, 2019 at 07:28:29AM +0800, Ian Campbell wrote:
> > On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote:
> > Would it be any help at all of the "dbus client-ish" bits and the
> > "direct API-ish" bits of the two libraries were split up into two
> > separate libraries? i.e. would that allow the c/r/p replacement of
> one
> > of the two libraries (AIUI the API one is the more problematic) to
> be
> > pushed further up the dependency stack?
> 
> I think that is what we already have (if I have understood you correctly). The
> dbus components are in systemd/elogind and the sd-*(3) APIs are in
> libsystemd0/libelogind0. Or have I misunderstood?

Probably I have, I thought the dbus client side stuff was in
libsystemd0/libelogind0 too.

> > Has anyone investigated late dynamic binding using a stub library which
> > merely determines which init is running and then dlopens the
> > appropriate libsystemd0 of libelogind0 library and forwards the calls
> > to it?
>  
> > I don't know if the dynamic linker could be coerced into doing the
> > selection automagically, in a way similar to how the hwcap stuff can be
> > used to pickup versions of libraries optimised for different classes of
> > processor. hwcap is provided by the kernel so I think can't be used
> > directly, but maybe there is a parallel mechanism somewhere?
> 
> I think Adam Borowski suggested somthing similar a while ago as an option, 
> but I
> am not aware of anything more than an idea.

Might be worth a PoC?

> I also experimented with LD_PRELOAD a while ago. But it felt very hackish.

Yeah. that's probably not the way to go.

Ian.

Bug#922869: marked as done (FTBFS: test failures / newly created file is older than distributed files)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 12:14:06 +0100
with message-id 
and subject line Closing
has caused the Debian Bug report #922869,
regarding FTBFS: test failures / newly created file is older than distributed 
files
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.)


-- 
922869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtool
Version: 2.4.6-10
Severity: serious

I got the following error:

## - ##
## Test results. ##
## - ##

ERROR: 150 tests were run,
15 failed (4 expected failures).
20 tests were skipped.

##  ##
## Summary of the failures. ##
##  ##
Failed tests:
GNU Libtool 2.4.6 test suite test groups:

 NUM: FILE-NAME:LINE TEST-GROUP-NAME
  KEYWORDS

 126: standalone.at:79   linking libltdl without autotools
  libtoolize
 127: subproject.at:57   compiling softlinked libltdl
  libtoolize automake autoconf
 128: subproject.at:73   compiling copied libltdl
  libtoolize automake autoconf
 129: subproject.at:89   installable libltdl
  libtoolize automake autoconf
 130: subproject.at:109  linking libltdl without autotools
  libtoolize
 131: nonrecursive.at:79 compiling softlinked libltdl
  libtoolize automake autoconf
 132: nonrecursive.at:103 compiling copied libltdl
  libtoolize automake autoconf
 133: nonrecursive.at:127 installable libltdl
  libtoolize automake autoconf
 137: tagdemo.at:338 static library
  cxx libtool libtoolize automake autoconf
 138: tagdemo.at:353 shared library
  cxx libtool libtoolize automake autoconf
 140: tagdemo.at:383 allow_undefined_flag
  cxx libtool libtoolize automake autoconf

[...]

## -- ##
## Detailed failed tests. ##
## -- ##

# -*- compilation -*-
126. standalone.at:79: testing linking libltdl without autotools ...
./standalone.at:82: $LIBTOOLIZE --copy --ltdl


stdout:
libtoolize: putting auxiliary files in 'libltdl'.
libtoolize: copying file 'libltdl/compile'
[...]
libtoolize: copying file 'libltdl/slist.c'
./standalone.at:83: $as_unset LIBTOOL; $as_unset LIBTOOLIZE; $MAKE $target 
CC="$CC" LIBTOOLFLAGS="$LIBTOOLFLAGS" CPPFLAGS="$CPPFLAGS" 
CFLAGS="$CFLAGS" LDFLAGS="$LDFLAGS"   CONFIGURE_OPTIONS="$configure_options"
stderr:
configure: error: newly created file is older than distributed files!
Check your system clock
make: *** [Makefile:24: libltdl/Makefile] Error 1
[...]

Ditto for the other failures.

The system clock seems fine. Or there is a serious issue with ntp.

-- System Information:
Debian Release: buster/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 4.19.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-- no debconf information
--- End Message ---
--- Begin Message ---

close 922869

thanks


Closing unreproducible bug.

Regards

Alastair

--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. --- End Message ---

Bug#939984: marked as done (metview, FTBFS on 32-bit, narrowing conversions.)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 11:20:26 +
with message-id 
and subject line Bug#939984: fixed in metview 5.6.1-4
has caused the Debian Bug report #939984,
regarding metview, FTBFS on 32-bit, narrowing conversions.
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.)


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

Package: metview
Version: 5.6.1-3
Severity: serious

It seems metview has recently started to fail to build on 32-bit,


/<>/atlas/src/tests/mesh/test_halo.cc: In function 'void 
atlas::test::traced_test_105(std::string&, int&, int)':
/<>/atlas/src/tests/mesh/test_halo.cc:142:40: error: narrowing 
conversion of '607990293346953216' from 'long long int' to 'long int' [-Wnarrowing]
   142 |  681187136435794030};
   |^
/<>/atlas/src/tests/mesh/test_halo.cc:157:60: error: narrowing 
conversion of '717939789677242368' from 'long long int' to 'long int' [-Wnarrowing]
   157 |  865001091216722323, 901706783667184769};
   |^
/<>/atlas/src/tests/mesh/test_halo.cc:172:80: error: narrowing 
conversion of '681187136204365458' from 'long long int' to 'long int' [-Wnarrowing]
   172 |  938197934089563136, 938197934125563136, 
938197934161563136};
   |
^
/<>/atlas/src/tests/mesh/test_halo.cc:188:40: error: narrowing 
conversion of '681187136281508315' from 'long long int' to 'long int' [-Wnarrowing]
   188 |  865001091628150894};
   |^
/<>/atlas/src/tests/mesh/test_halo.cc:201:80: error: narrowing 
conversion of '865001091473865179' from 'long long int' to 'long int' [-Wnarrowing]
   201 |  865001091628150894, 901706784087184768, 
938197934341563136};

I first noticed this in raspbian, but it's happening on the Debian reproducible 
builds site for i386 sid and armhf bullseye* too, so I don't think it's 
raspbian specific.

* i386 bullseye has not been tested by reproducible builds, i386 sid is showing 
a successful build on reproducible builds, but that success is older than the 
two failures.

--- End Message ---
--- Begin Message ---
Source: metview
Source-Version: 5.6.1-4

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated metview 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, 24 Sep 2019 10:03:54 +0100
Source: metview
Architecture: source
Version: 5.6.1-4
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 939984
Changes:
 metview (5.6.1-4) unstable; urgency=medium
 .
   * Fix 32-bit support with changes in atlas. Closes: #939984
Checksums-Sha1:
 85937f0d91372956a5a6098e4c3033964433e800 3014 metview_5.6.1-4.dsc
 6f287f0d403163a5f7d9ccaad5d305cae15b60d2 43848 metview_5.6.1-4.debian.tar.xz
Checksums-Sha256:
 61071c0d67e1e18dd5c55a99fc887913d3f26b7b294312f882e8f1bfa01c93c6 3014 
metview_5.6.1-4.dsc
 070f04c425ad281b6868c026f27c476cd128f5709a6956f576824d7ef385854c 43848 
metview_5.6.1-4.debian.tar.xz
Files:
 65a91ca168ab7d8b19296dbe85e37f82 3014 science optional metview_5.6.1-4.dsc
 70f42cb5f04a3973fb755ff14ee1c8b6 43848 science optional 
metview_5.6.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl2J9qIACgkQy+a7Tl2a
06W7RhAAoNbN6tFi0lkU2Zc21P/QeshUz4EFNJ88I3AoDDtxKNvc2VEIYwcJuctu
LbBVcwY3Z0XwBdPbmNIWXY+oR0yFbkR+HjMclbKqwMWBo3sevXuWOnyLToOUM494
K4Yc+zUcqUa5/lqrOaZ3bJ9wdMBkUB2wVMhM8zj708kG2IRtW7nlWLW24gGJ6W/Q
v0BZzDlTuvp2XfSSMZxvw1lv6aXHOzplPqCxGMReljwdiO33OWaNdoNyPG1AAHmV
UWs7z4TS7KKznpmKO4FeUXjnfQUvUzP29qtX+8TaYfLQpGaTLAgnbgXPR/yWH0Da
5T1JJ3WY8mxGZ2MghL3y3opG3hZ+856PTV7tCwpVvg5ozKOH7iyMscVfK4a7cTej

Bug#941046: bbdb: byte-compilation and startup broken with unversioned emacs

[David Bremner]

Control: severity -1 important
Control: tag -1 help

David Bremner  writes:

>
> debian/bbdb.emacsen-install was never updated for unversioned
> emacs. This means the package fails to byte compile, which in turn
> causes the startup file to bail out.

I have work in progress [1] that fixes the
byte-compilation. Unfortunately that seems to reveal another bug with
the maintainer scripts that bbdb-autoload.elc is not being generated.
That feels like a different bug to me, but I'd need more testing to be
sure.

> I'm not 100% sure about the severity. This bug does mean that unless
> people write their own startup code (manipulating load-paths and so
> on), bbdb is completely useless.

I'm downgrading the severity of this bug, as it only affects users
without emacs25 installed, and I suspect that's a minority.


[1]:  https://salsa.debian.org/emacsen-team/bbdb/tree/buster

Processed: Re: bbdb: byte-compilation and startup broken with unversioned emacs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #941046 [bbdb] bbdb: byte-compilation and startup broken with unversioned 
emacs
Severity set to 'important' from 'serious'
> tag -1 help
Bug #941046 [bbdb] bbdb: byte-compilation and startup broken with unversioned 
emacs
Added tag(s) help.

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

Processed: notfound 890239 in 65.0.3325.73-1, reassign 940973 to src:libarchive-zip-perl, fixed 940973 in 1.66-2

[Debian Bug Tracking System]

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

> notfound 890239 65.0.3325.73-1
Bug #890239 {Done: Michael Gilbert } [chromium] chromium: 
u2f yubico keys now need libu2f-udev in order to work
Bug #891473 {Done: Michael Gilbert } [chromium] chromium 
should Recommend libu2f-udev
No longer marked as found in versions chromium-browser/65.0.3325.73-1.
No longer marked as found in versions chromium-browser/65.0.3325.73-1.
> reassign 940973 src:libarchive-zip-perl 1.66-1
Bug #940973 {Done: gregor herrmann } 
[src:libarchive-zip-perl, src:strip-nondeterminism] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Bug reassigned from package 'src:libarchive-zip-perl, src:strip-nondeterminism' 
to 'src:libarchive-zip-perl'.
No longer marked as found in versions libarchive-zip-perl/1.66-1.
No longer marked as fixed in versions libarchive-zip-perl/1.66-2.
Bug #940973 {Done: gregor herrmann } 
[src:libarchive-zip-perl] libarchive-zip-perl breaks strip-nondeterminism 
autopkgtest: error: becoming Archive::Zip::DirectoryMember
Marked as found in versions libarchive-zip-perl/1.66-1.
> fixed 940973 1.66-2
Bug #940973 {Done: gregor herrmann } 
[src:libarchive-zip-perl] libarchive-zip-perl breaks strip-nondeterminism 
autopkgtest: error: becoming Archive::Zip::DirectoryMember
Marked as fixed in versions libarchive-zip-perl/1.66-2.
> thanks
Stopping processing here.

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

Bug#941076: debsign crashes gnome on wayland session

[Simon McVittie]

Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland session
Control: tags -1 + experimental moreinfo

On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:
> After updating gnome to 2.34

I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
2.32 was in 2010, and was followed by 3.0.

Key GNOME 3.34 components, including gnome-session and gnome-shell, are
currently only in experimental. You're welcome to try it, but please
make sure that bug reports are complete, precise and actionable.

> I'm not able to use debsign, it crashes the
> desktop. I'm logged out after screen is blacked out.

Please send details of the package versions involved, and whatever
backtraces and system log entries are available.

For what it's worth, I have not experienced similar crashes when using
debsign and pinentry-gnome3 in conjunction with a smart card (Nitrokey
Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
other people uploading GNOME 3.34 for the GNOME team are also using
debsign and pinentry-gnome3 in that environment.

smcv

Processed: Re: Bug#941076: debsign crashes gnome on wayland session

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 [GNOME 3.34] debsign crashes gnome on wayland session
Bug #941076 [gnome-session,pinentry-gnome3] debsign crashes gnome on wayland 
session
Changed Bug title to '[GNOME 3.34] debsign crashes gnome on wayland session' 
from 'debsign crashes gnome on wayland session'.
> tags -1 + experimental moreinfo
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
Added tag(s) moreinfo and experimental.

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

Bug#941077: xserver-xorg-video-ast: sourceless firmware in AST_DP501_firmware in src/ast_dp501fw.h

[Paul Wise]

Source: xserver-xorg-video-ast
Version: 1.1.5-1.1
Severity: serious
Justification: DFSG item 2

The AST_DP501_firmware array in src/ast_dp501fw.h contains a sourceless
firmware blob. I think this means that xserver-xorg-video-ast needs to
move to non-free, or it could use ast_dp501_fw.bin from the firmware
directory like the Linux kernel does and then move to contrib.

xserver-xorg-video-ast-1.1.5/ $ grep -C1 0x src/ast_dp501fw.h | head -n3
UCHAR AST_DP501_firmware[] = {\
0x00,0x00,0x00,0x00,0x00,0x00,0x04,0x00,\
0x00,0x00,0x04,0x56,0x00,0x00,0x04,0x56,\

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

Package: gnome-session,pinentry-gnome3
severity: critical

After updating gnome to 2.34 I'm not able to use debsign, it crashes 
the desktop. I'm logged out after screen is blacked out. Tried updating 
task-gnome-desktop and *wayland* packages but no effect. GNOME on Xorg 
works, it still shows a black screen when launching debsign but I don't 
lose the session.


It is possibly a bug in pinentry-gnome3 or gnome-keyring. I can use 
debsign with curses pinentry screen if I switch to a virtual terminal 
(control+alt+f2).

Bug#935578: (no subject)

[Paride Legovini]

We settled with 'batcat', see

https://github.com/sharkdp/bat/issues/656

Ongoing discussion on the upstream tooling make the rename easier and
keep the manpage consistent:

https://github.com/sharkdp/bat/issues/659

Paride

Bug#934850: (no subject)

[Paride Legovini]

We settled with 'batcat', see

https://github.com/sharkdp/bat/issues/656

Ongoing discussion on the upstream tooling make the rename easier and
keep the manpage consistent:

https://github.com/sharkdp/bat/issues/659

Paride

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 935578 934850
Bug #935578 [bat] bat: bacula-console-qt already ships /usr/sbin/bat (and 
/usr/share/man/man1/bat.1.gz)
Bug #935578 [bat] bat: bacula-console-qt already ships /usr/sbin/bat (and 
/usr/share/man/man1/bat.1.gz)
Marked as found in versions rust-bat/0.11.0-1.
Bug #934850 [bat] bat: missing Breaks+Replaces: bareos-bat
Marked as found in versions rust-bat/0.11.0-2.
Merged 934850 935578
>
End of message, stopping processing here.

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

Bug#935578: (no subject)

[Paride Legovini]

control: forcemerge 935578 934850

Merging the two bugs, as what we need is a full rename of the 'bat'
binary file and of its manpage, as #935578 bug states.

Paride

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

Ian,

Thanks for this.

On Tue, Sep 24, 2019 at 07:28:29AM +0800, Ian Campbell wrote:
> On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote:
> Would it be any help at all of the "dbus client-ish" bits and the
> "direct API-ish" bits of the two libraries were split up into two
> separate libraries? i.e. would that allow the c/r/p replacement of one
> of the two libraries (AIUI the API one is the more problematic) to be
> pushed further up the dependency stack?

I think that is what we already have (if I have understood you correctly). The
dbus components are in systemd/elogind and the sd-*(3) APIs are in
libsystemd0/libelogind0. Or have I misunderstood?

> Has anyone investigated late dynamic binding using a stub library which
> merely determines which init is running and then dlopens the
> appropriate libsystemd0 of libelogind0 library and forwards the calls
> to it?
 
> I don't know if the dynamic linker could be coerced into doing the
> selection automagically, in a way similar to how the hwcap stuff can be
> used to pickup versions of libraries optimised for different classes of
> processor. hwcap is provided by the kernel so I think can't be used
> directly, but maybe there is a parallel mechanism somewhere?

I think Adam Borowski suggested somthing similar a while ago as an option, but I
am not aware of anything more than an idea.

I also experimented with LD_PRELOAD a while ago. But it felt very hackish.

Mark

Bug#941030: marked as done (python3-os-apply-config: missing Breaks+Replaces: python-os-apply-config)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 09:19:29 +
with message-id 
and subject line Bug#941030: fixed in python-os-apply-config 10.4.1-2
has caused the Debian Bug report #941030,
regarding python3-os-apply-config: missing Breaks+Replaces: 
python-os-apply-config
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.)


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

Hi,

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

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

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

  Preparing to unpack .../python3-os-apply-config_10.4.1-1_all.deb ...
  Unpacking python3-os-apply-config (10.4.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-os-apply-config_10.4.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/os-apply-config', which is also in package 
python-os-apply-config 0.1.14-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-os-apply-config_10.4.1-1_all.deb


cheers,

Andreas


python-os-apply-config=0.1.14-1_python3-os-apply-config=10.4.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-os-apply-config
Source-Version: 10.4.1-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-os-apply-config 
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, 24 Sep 2019 11:02:00 +0200
Source: python-os-apply-config
Architecture: source
Version: 10.4.1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 941030
Changes:
 python-os-apply-config (10.4.1-2) experimental; urgency=medium
 .
   * Add Breaks+Replaces for python-os-apply-config (Closes: #941030).
Checksums-Sha1:
 a971c5a86e853b2149fcd279c13bb70624e93516 2357 
python-os-apply-config_10.4.1-2.dsc
 28e8378a17503763a5cd9bbbd97b6b4b69552827 4020 
python-os-apply-config_10.4.1-2.debian.tar.xz
 79fba3d3cd253011721192c8f362bdd8472bf760 8048 
python-os-apply-config_10.4.1-2_amd64.buildinfo
Checksums-Sha256:
 3a08429c22b6481ee78fe9e36f5d487fe038c74a3545e7d6d5d916ed2c813e9e 2357 
python-os-apply-config_10.4.1-2.dsc
 81aadec894e42053e0284c55e584e38297ed818680d167df22f3eb9315a85b39 4020 
python-os-apply-config_10.4.1-2.debian.tar.xz
 60a49369154186f4aa12cb27cd108b3c54250d00671a7b9a4025f529710e33ae 8048 
python-os-apply-config_10.4.1-2_amd64.buildinfo
Files:
 92892b520c37a6a4af0a5587a466511c 2357 python optional 
python-os-apply-config_10.4.1-2.dsc
 c6d27d1a154c052f07e5d0862280f2dc 4020 python optional 
python-os-apply-config_10.4.1-2.debian.tar.xz
 7f99acd50ce3f99c7b54df78281157e3 8048 python optional 
python-os-apply-config_10.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl2J3BAACgkQ1BatFaxr
Q/7G5Q/+KWhne8cMYqkE3IqKUngP3O891MUyNDbKrXVmLib6vB2DOU5VRlggg/cM
40tP0uXLzB0WKYGazpQIhDSoI69Qit/KnvdIjqOHnMwBxU17Oj/YX+a2hECERiCu
GknRF13GdshHaq6jE8OIT5bbQBcCFtX5lO/wh7thBm/tFVPrEYl4m7E7gD/4Gp2j
4Z6G+cFYBHLe5FUNBxvGSe2TPFx7W9NNnC2HWVIUlHZZR5A1qi6stlswJUYPgkzS
LaZ/0qKb65lColEvfzlmaL+OLZ/fpywKuET0lxlQNpcK3D2Bb7c8VXrOJaZaBaPQ
lIGVcQPaXNT3SWcInnrKDWdIWhS3M8JPY4+z1+Z+Xs6PVqcHbxqg0nixAn40DXTK
LpM50E2H/Nn0im211L/yBJ25ulZ4K0iKThNuWFrJP2EYJHem4KoPzOOi7nIZIaLQ
/UPPpeDoU6gPCIFt33SPt/Z9w7R+pmyfD41B2uyJXw6hHoSqJZd6sEOHl1CchmR9
1BSPQrFsKbcRM7z7T2a7Skks9xlSvAoKBwYKgM/e0L7H6cnmAJLm2lQYXk/22ILx
gqrfYVivhJ/DFyOBugkIGBunMN6XsEDwk4hC1+ZHsbR27j0QOng76nwZI25rkxyo

Bug#939672: marked as done (tmate: does not work at all; fails saying '[lost server]')

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 09:19:47 +
with message-id 
and subject line Bug#939672: fixed in tmate 2.3.0-1
has caused the Debian Bug report #939672,
regarding tmate: does not work at all; fails saying '[lost server]'
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.)


-- 
939672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tmate
Version: 2.2.1-1+b2
Severity: grave
Justification: renders package unusable
Tags: bullseye sid

When I try to start tmate, it just aborts and says '[lost server]'.
After that the terminal is broken, and I have to reset it. I tried it on
a Debian 10 VM and it just works, so this is not a server-side problem.
I guess that some dependency changed under tmate in an incompatible way,
and maybe just upgrading to the new upstream version fixes this.

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

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

Versions of packages tmate depends on:
ii  libc6   2.28-10
ii  libevent-2.1-6  2.1.8-stable-4
ii  libmsgpackc23.0.1-3
ii  libssh-40.9.0-1
ii  libtinfo6   6.1+20190803-1

tmate recommends no packages.

tmate suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tmate
Source-Version: 2.3.0-1

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

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

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated tmate 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, 24 Sep 2019 05:57:11 -0300
Source: tmate
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Lucas Kanashiro 
Changed-By: Lucas Kanashiro 
Closes: 939672
Changes:
 tmate (2.3.0-1) unstable; urgency=medium
 .
   * New upstream version 2.3.0 (Closes: #939672)
   * b-d on debhelper-compat
   * d/control: update VCS links
   * Declare compliance with Debian Policy 4.4.0
   * Refresh patches
Checksums-Sha1:
 797b7a280f4ff51b92332cbfd31a18b283da0489 1992 tmate_2.3.0-1.dsc
 91f690d2bee37c3f92a181a264f90d62c91651ee 611262 tmate_2.3.0.orig.tar.gz
 908a00032e6cfd6957003437e0d7f21770806084 5680 tmate_2.3.0-1.debian.tar.xz
 904808aa1916eb63f650706e9272a828b9183800 6645 tmate_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 36225085202ff8baecde0b9c6ebc27ea8864a02e361eedb2f930b6b49ab119c4 1992 
tmate_2.3.0-1.dsc
 f837514edbc19180d06b27713628466e68aba91654d748d6e65bfad308f5b00a 611262 
tmate_2.3.0.orig.tar.gz
 f5d7fb363818ca15b9297bfb76abd8e8b8ea5d206482a3c280e81005c18b7ea1 5680 
tmate_2.3.0-1.debian.tar.xz
 afbef8780b18331ccecc6ecfa1f8442d2185ba86d1d6ca5cb476a5993741fd28 6645 
tmate_2.3.0-1_amd64.buildinfo
Files:
 4e02a92b54c1c9019fc595d8c8c9f095 1992 devel optional tmate_2.3.0-1.dsc
 2dc05f8f07af8c86031cba7df0233b94 611262 devel optional tmate_2.3.0.orig.tar.gz
 c653e859151b957d449c4618f44cc4f0 5680 devel optional 
tmate_2.3.0-1.debian.tar.xz
 6aed7455feb826dad1368bf0d1464790 6645 devel optional 
tmate_2.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl2J3BYVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8sk0P/1nxcBsIfwmROu4yY3OO2rGuuXeK
VQ3CKPXnaZdGbJLuzT9OXRrWx1MmzpW/I14+5c5jnSDq1aQUtaWcpC9oEKf2LRCI
AsHiiYuqPb1y2ab+Y1hYtgvnmZKug0CokAvu2UpaQ4RTO0rTu8Ksw8bDEMKy8wQ0
yq08hr2U311GJzywgGXyJHYTWvY0TX8y9clJ9RNknvsf2tFrkSATNfuv3zUjkvC+
4btGcKuxZ6xcxP4EC9HkebULQO4cGIzL/Zec89mkMdUwRz62CZp29RsBoYjxrsok
PW6KZNT48jA0+O2zrw7lpiGnhVV1w+gUiIi8+4loR86XT4RcctkT3qFvJcX3kzNg

Bug#941028: marked as done (python3-os-refresh-config: missing Breaks+Replaces: python-os-refresh-config)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 09:19:35 +
with message-id 
and subject line Bug#941028: fixed in python-os-refresh-config 10.1.0-2
has caused the Debian Bug report #941028,
regarding python3-os-refresh-config: missing Breaks+Replaces: 
python-os-refresh-config
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.)


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

Hi,

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

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

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

  Preparing to unpack .../python3-os-refresh-config_10.1.0-1_all.deb ...
  Unpacking python3-os-refresh-config (10.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-os-refresh-config_10.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/os-refresh-config', which is also in package 
python-os-refresh-config 0.1.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-os-refresh-config_10.1.0-1_all.deb


cheers,

Andreas


python-os-refresh-config=0.1.2-1_python3-os-refresh-config=10.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-os-refresh-config
Source-Version: 10.1.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-os-refresh-config 
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, 24 Sep 2019 11:05:01 +0200
Source: python-os-refresh-config
Architecture: source
Version: 10.1.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 941028
Changes:
 python-os-refresh-config (10.1.0-2) experimental; urgency=medium
 .
   * Add Breaks+Replaces python-os-refresh-config (Closes: #941028).
Checksums-Sha1:
 a0936989f9fe9a9d954c5b41d810ea9d24e0692d 2411 
python-os-refresh-config_10.1.0-2.dsc
 face7788ccb1cbd3254adddc937f7b915b3daed5 2316 
python-os-refresh-config_10.1.0-2.debian.tar.xz
 7e09e654b70752eff7d6b4174dd18dcf1d11da7a 8112 
python-os-refresh-config_10.1.0-2_amd64.buildinfo
Checksums-Sha256:
 056f915eadc618cb2d583fba99433faab97db4f7f5857598262db1949bb32b6c 2411 
python-os-refresh-config_10.1.0-2.dsc
 48f28358833de3ee62e98e491dbf54b7b931a42c9313a6fa396faadfa1411b50 2316 
python-os-refresh-config_10.1.0-2.debian.tar.xz
 728b6b168090adfa3e6f3cdb9dba509653eb5747d3251a92acf20009e2875cc2 8112 
python-os-refresh-config_10.1.0-2_amd64.buildinfo
Files:
 753f88a2c832b5975cc60358c74e84ff 2411 python optional 
python-os-refresh-config_10.1.0-2.dsc
 4f61623591a2d3d587e8c474e122b8d8 2316 python optional 
python-os-refresh-config_10.1.0-2.debian.tar.xz
 47a42e078014fd41055ca1f991054111 8112 python optional 
python-os-refresh-config_10.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl2J3KEACgkQ1BatFaxr
Q/7/Tw//YvC6IkUbEZtS4Uevso3e0SblHqLWoOeSpQDte/9nYsBlZeHMsDvbXXF7
WhF+P6rvRH4fNmAeMRZw05tgK5lRkdGlrZyF8iWZQMMsNyyZPPQ5QGgbWHs+KE5D
Yqwl3o7BHRWn9qp4Of3ses+SKuqz5ZnD8B25CJsK+2d9LF/RFz0nI9fEiB575wzU
E0kwBGbWylehdw0FASVec2S2ZnwfwSYprIK+4l1ViPvzIhAUg2SccRMftdHktWZm
VPWd6G5z/EZ5LfK6KMIa0uRYc9yDP2teNHjYwn4YVwOo4xxzwrR0kRTnIL0VTUlX
y5RQ+FVU1iN33g6gNmI5oVHyecxKYpoOfB2lpVjqQ4qHoGwp2Ud0Qd5CtCi4JrTf
A5VcpjRI1wIWPFWeNDaEtA+tw9JX3TFpH22w9NIvoiU4CPqJtY9OuS6/cRkxhBTp
kLxWMmTciv9sSzeNQqFtYVxmQ/lOH/cBF6u0BTyGyqDm0OW2CeDMY6H6B0ZoGWPf
q1BqDrw6qKBIeaRkKAR075J1SrcBZpAfA+Dp47mdvrtmV13BF+nnhD8AQUxFKYqX

Processed: Bug#941030 marked as pending in python-os-apply-config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941030 [python3-os-apply-config] python3-os-apply-config: missing 
Breaks+Replaces: python-os-apply-config
Added tag(s) pending.

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

Processed: Bug#941028 marked as pending in python-os-refresh-config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941028 [python3-os-refresh-config] python3-os-refresh-config: missing 
Breaks+Replaces: python-os-refresh-config
Added tag(s) pending.

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

Bug#941030: marked as pending in python-os-apply-config

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #941030 in python-os-apply-config 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/openstack-team/libs/python-os-apply-config/commit/cef8678afe476e2fc2a49aab891d7b7b3937c0f8


Add Breaks+Replaces for python-os-apply-config (Closes: #941030).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941030

Bug#941028: marked as pending in python-os-refresh-config

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #941028 in python-os-refresh-config 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/openstack-team/libs/python-os-refresh-config/commit/a087c03588ac4ed5187479dff1138e555beda050


Add Breaks+Replaces python-os-refresh-config (Closes: #941028).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941028

Bug#939598: marked as done (libubootenv-tool: trying to overwrite '/usr/bin/fw_printenv', which is also in package u-boot-tools 2019.01+dfsg-7)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 08:36:26 +
with message-id 
and subject line Bug#939598: fixed in u-boot 2019.10~rc4+dfsg-1
has caused the Debian Bug report #939598,
regarding libubootenv-tool: trying to overwrite '/usr/bin/fw_printenv', which 
is also in package u-boot-tools 2019.01+dfsg-7
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.)


-- 
939598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libubootenv-tool,u-boot-tools
Severity: serious
Version: libubootenv/0.1-1 u-boot/2019.01+dfsg-7

Hi,

the new package libubootenv-tool has a file conflict with the existing
package u-boot-tools:

Preparing to unpack .../15-libubootenv-tool_0.1-1_amd64.deb ...
Unpacking libubootenv-tool (0.1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-S5V5yb/15-libubootenv-tool_0.1-1_amd64.deb (--unpack
):
 trying to overwrite '/usr/bin/fw_printenv', which is also in package 
u-boot-tools 2019.01+dfsg-7

Since the packages are both u-boot related, the new program might have
the same functionality as the existing one and hence using
update-alternatives for the two variants maybe an option.

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: u-boot
Source-Version: 2019.10~rc4+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 01:03:23 -0700
Source: u-boot
Architecture: source
Version: 2019.10~rc4+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 939598
Changes:
 u-boot (2019.10~rc4+dfsg-1) experimental; urgency=medium
 .
   * New upstream release candidate.
   * u-boot-rockchip: Add rock64-rk3328 target.
   * u-boot-rockchip: Install rockchip_make_fit_atf and Recommend python3.
   * generate-rksd: Add support for rk3328 and TPL images.
   * debian/patches:
 - Update ensure-config-sandbox-for-make-env.
 - Update qemu-riscv64-raw-initrd for.
 - Add description and forwarded links for qemu-riscv64-raw-initrd.
   * u-boot-qemu: Drop support for qemu_mips, qemu_mipsel and
 qemu_mips64el as the cross compilers are no longer available.
   * u-boot-tools:
 - Remove fw_printenv and fw_setenv and Recommend libubootenv-tool.
   (Closes: #939598)
 - Update package description.
   * README.Debian: Drop references to fw_setenv and fw_printenv.
   * debian/control:
 - [arm64] Drop Build-Depends on python-pyelftools; no longer needed
   for fit image creation.
 - Update Standards-Version to 4.4.0, no changes needed.
 - Update to debhelper-compat 12.
   * debian/copyright: Drop stanza and license for pcmcia; code was
 removed.
Checksums-Sha1:
 6ef4b603d3bebc8743ba0141f26d759f338c3e41 2849 u-boot_2019.10~rc4+dfsg-1.dsc
 839022ad4dc2db64d37575a8c88cd813d3e80990 11960016 
u-boot_2019.10~rc4+dfsg.orig.tar.xz
 381c0562a8a9f55896d3a80a14879bc505065ea5 41060 
u-boot_2019.10~rc4+dfsg-1.debian.tar.xz
 33cd9ef8c078dfc5e817f3e48cdd1975ade8a1ee 8722 
u-boot_2019.10~rc4+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 71fd24e03632b857820f74d3a5cc8ed2e4ec3f6c5f2a1bed72aa2ab2e8c2c983 2849 
u-boot_2019.10~rc4+dfsg-1.dsc
 74949890502e778804aa5b146cc631f4442ced7b054090ddfd4a6ec373151a27 11960016 
u-boot_2019.10~rc4+dfsg.orig.tar.xz
 7c0f5ddc065101c39a09b79211c8c3a4758c010bafdf75b73c7e52992afd15d5 41060 

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Trek]

On Tue, 24 Sep 2019 07:28:29 +0800
Ian Campbell  wrote:

> Has anyone investigated late dynamic binding using a stub library
> which merely determines which init is running and then dlopens the
> appropriate libsystemd0 of libelogind0 library and forwards the calls
> to it?

it could be in the form of libglvnd, a generic dispatcher to have
co-installed multiple vendor implementations of libgl, with runtime
selection

https://github.com/NVIDIA/libglvnd

a stripped down version of that architecture could be used to simply
detect what init system is actually running and then dispatch to the
correct library (libsystemd or libelogind)

ciao!

Bug#938133: marked as done (python-repoze.tm2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Sep 2019 07:19:06 +
with message-id 
and subject line Bug#938133: fixed in python-repoze.tm2 2.0-2
has caused the Debian Bug report #938133,
regarding python-repoze.tm2: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-repoze.tm2

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-repoze.tm2
Source-Version: 2.0-2

We believe that the bug you reported is fixed in the latest version of
python-repoze.tm2, 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.
Andrey Rahmatullin  (supplier of updated python-repoze.tm2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 12:06:06 +0500
Source: python-repoze.tm2
Architecture: source
Version: 2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrey Rahmatullin 
Closes: 938133
Changes:
 python-repoze.tm2 (2.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * Use debhelper-compat instead of debian/compat.
 .
   [ Andrey Rahmatullin ]
   * Drop Python 2 support (Closes: #938133).
Checksums-Sha1:
 

Bug#941059: libjson-c-dev: broken so symlink

[Sebastian Ramacher]

Package: libjson-c-dev
Version: 0.13.1+dfsg-5
Severity: serious

After the last update:

% ls -l /usr/lib/x86_64-linux-gnu/libjson-c.so
lrwxrwxrwx 1 root root 36 Sep 24 01:31 /usr/lib/x86_64-linux-gnu/libjson-c.so 
-> /lib/x86_64-linux-gnu/libjson-c.so.4

But:

% ls /lib/x86_64-linux-gnu/libjson-c.so.4
ls: cannot access '/lib/x86_64-linux-gnu/libjson-c.so.4': No such file or 
directory

Cheers

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

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

Versions of packages libjson-c-dev depends on:
ii  libjson-c4  0.13.1+dfsg-5

libjson-c-dev recommends no packages.

libjson-c-dev suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature