Bug#936552: freecad: Python2 removal in sid/bullseye

[Scott Kitterman]

Bumping to serious since freecad is build-depending on packages requested for 
removal.

Scott K

Processed: severity of 936552 is serious

[Debian Bug Tracking System]

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

> severity 936552 serious
Bug #936552 [src:freecad] freecad: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#939628: marked as done (should archipel-* packages be removed from Debian?)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:52:47 +
with message-id 
and subject line Bug#939699: Removed package(s) from unstable
has caused the Debian Bug report #939628,
regarding should archipel-* packages be removed from Debian?
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.)


-- 
939628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:archipel-core
Severity: serious

Hello,
Debian is trying to remove Python 2 from the distribution
(https://wiki.debian.org/Python/2Removal) and i stumbled across archipel.

It looks like this project is no longer maintained upstream:

* https://github.com/ArchipelProject/Archipel latest commit is more than 3 years
  ago
* the homepage http://archipelproject.org/ returns an error from cloudflare and
  the wayback machine can find an actual page only back in April 2018
* the mailing list https://groups.google.com/forum/#!forum/archipelproject has
  no new post (execpt to report the website down) since early 2016

Here below is a recapt of the status of the archipel packages:

package last-upload popcon
archipel-core   2013-05-0547
archipel-agent-action-scheduler 2013-05-0512
archipel-agent-hypervisor-geolocalization   2013-05-05 7
archipel-agent-hypervisor-health2013-05-0510
archipel-agent-hypervisor-network   2013-05-0514
archipel-agent-hypervisor-platformrequest   2013-05-0510
archipel-agent-iphone-notification  2013-05-0517
archipel-agent-virtualmachine-oomkiller 2013-05-0512
archipel-agent-virtualmachine-snapshoting   2013-05-0513
archipel-agent-vmcasting2013-05-05 9
archipel-agent-vmparking2013-05-05 9
archipel-agent-xmppserver   2013-05-0510
archipel-agent-virtualmachine-vnc   2013-05-0513

It is my belief we should remove archipel* packages from Debian, in particular
because they are a close-set of packages, and they could ideally allow other
python2 packages to be removed (as archipel* will disappear as their
reverse-dependencies).

If i dont hear back in a week, i'll file RM bugs for all the aforementioned
packages.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 0.6.0-1+rm

Dear submitter,

as the package archipel-core 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/939699

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#875494: marked as done (connectomeviewer: Qt4 removal form Buster)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:46:21 +
with message-id 
and subject line Bug#939691: Removed package(s) from unstable
has caused the Debian Bug report #875494,
regarding connectomeviewer: Qt4 removal form 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.)


-- 
875494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: connectomeviewer
Version: 2.1.0-1.1
Severity: minor
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Note: this bug is being filled because your package recommends 
python-qscintilla2.

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 



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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 2.1.0+dfsg-1+rm

Dear submitter,

as the package connectomeviewer 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/939691

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#875114: marked as done ([pyside-tools] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:43:38 +
with message-id 
and subject line Bug#935667: Removed package(s) from unstable
has caused the Debian Bug report #875114,
regarding [pyside-tools] 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.)


-- 
875114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyside-tools
Version: 0.2.15-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 ---
Version: 0.2.15-1+rm

Dear submitter,

as the package pyside-tools 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/935667

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#866451: marked as done (photon: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:43:14 +
with message-id 
and subject line Bug#929542: Removed package(s) from unstable
has caused the Debian Bug report #866451,
regarding photon: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:photon
Version: 0.4.6-3.1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Version: 0.4.6-3.1+rm

Dear submitter,

as the package photon 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/929542

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#866445: marked as done (oboinus: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:42:22 +
with message-id 
and subject line Bug#920125: Removed package(s) from unstable
has caused the Debian Bug report #866445,
regarding oboinus: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oboinus
Version: 2.3-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Version: 2.3-1+rm

Dear submitter,

as the package oboinus 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/920125

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#899243: marked as done (Needs porting to later tornado)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 04:38:18 +
with message-id 
and subject line Bug#813870: Removed package(s) from unstable
has caused the Debian Bug report #899243,
regarding Needs porting to later tornado
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.)


-- 
899243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sockjs-tornado
Version: 1.0.3-1
Severity: serious

Hello,

in recent tornado versions, PeriodicCallback lost the io_loop argument:
http://www.tornadoweb.org/en/stable/ioloop.html#tornado.ioloop.PeriodicCallback
but sockjs.tornado is still trying to use of it:

>>> import sockjs.tornado
>>> sockjs.tornado.SockJSRouter(sockjs.tornado.SockJSConnection)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sockjs/tornado/router.py", line 111, in 
__init__
self.io_loop)
TypeError: __init__() takes 3 positional arguments but 4 were given

Because of this, sockjs.tornado does not work in current Debian Testing.


Enrico

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

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

Versions of packages python3-sockjs-tornado depends on:
ii  python3  3.6.4-1
ii  python3-tornado  5.0.2-1

python3-sockjs-tornado recommends no packages.

python3-sockjs-tornado suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.3-1+rm

Dear submitter,

as the package python-sockjs-tornado 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/813870

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#935911: marked as done (librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 03:49:09 +
with message-id 
and subject line Bug#935911: fixed in rust-md5 0.6.1-1
has caused the Debian Bug report #935911,
regarding librust-uuid+md5-dev/amd64 unsatisfiable Depends: 
librust-md5-0.6+default-dev
to be marked as done.

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

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


-- 
935911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-uuid
Version: 0.7.2-2
Severity: serious
Affects: src:rust-md5
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-uuid package depends on a newer rust-md5 than is available in the
Debian archive.

 librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev

Only rust-md5 0.3 is currently available.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-md5
Source-Version: 0.6.1-1

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

Debian distribution maintenance software
pp.
kpcyrd  (supplier of updated rust-md5 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: Sun, 08 Sep 2019 05:20:16 +0200
Source: rust-md5
Architecture: source
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: kpcyrd 
Closes: 935911
Changes:
 rust-md5 (0.6.1-1) unstable; urgency=medium
 .
   * Package md5 0.6.1 from crates.io using debcargo 2.4.0 (Closes: #935911)
Checksums-Sha1:
 cf7213062650fbd47c04785e307d4bb5eb8e6a12 2107 rust-md5_0.6.1-1.dsc
 82cda2f3baa2276e8221bae356a702cbd7bce41e 6574 rust-md5_0.6.1.orig.tar.gz
 ff869aa12906bca4d75913e20d3785476ffb2612 2764 rust-md5_0.6.1-1.debian.tar.xz
 c03ce8d423864191bbfef6bbdc5069c84d837228 6587 rust-md5_0.6.1-1_source.buildinfo
Checksums-Sha256:
 49a6fa34b4252766ca61ced4d0e360452e8b437aeac5956e4ad5b30c41eb998e 2107 
rust-md5_0.6.1-1.dsc
 7e6bcd6433cff03a4bfc3d9834d504467db1f1cf6d0ea765d37d330249ed629d 6574 
rust-md5_0.6.1.orig.tar.gz
 ad16807ff7eb1027d29f2d41f9adcafa025d4d4718fad18a89463e1b99363a75 2764 
rust-md5_0.6.1-1.debian.tar.xz
 0340a4da83bed8891678613763000f8e3e00d3c8d81063778a6b59ddd62e2286 6587 
rust-md5_0.6.1-1_source.buildinfo
Files:
 06e1c14ce48a319d125201fd6fab1b2b 2107 rust optional rust-md5_0.6.1-1.dsc
 34ddbed8eff4814baa910e33ceda55d6 6574 rust optional rust-md5_0.6.1.orig.tar.gz
 742d75c87ca8e0d4e00e7aa462463516 2764 rust optional 
rust-md5_0.6.1-1.debian.tar.xz
 4a3fa7804b17a62cf1e6cf4b836ee0c7 6587 rust optional 
rust-md5_0.6.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQI/BAEBCAApFiEEM+u4qOHFZTZFsSMqRaZQ4mOMU20FAl10c3ULHGdpdEByeHYu
Y2MACgkQRaZQ4mOMU22z3A//bOuxD6cOtksoYKDX1NlexHHvQYMHTxNLtL/w+oVq
wJgcaZfChDP8y+Surs4kwWeFKpY/IBd8QBV5bPAJ7WxquXcVc+XviIrnMPZzpf2+
PVx/45U3M4I4J5Z+l+3F5iDbkU4JsZA5MtiV4G/hY/2Cv6goVHmh1f/Z5Cd4OAqC
uG6k/jMynA/fusYYePiUe+C2XBe3CHxbXzlcgrZ03a+wNEpZP5/5yVmA65OJneXH
WipAMQ06hgxvY6sJVulQ4SCdKBnNr63rq/Yi/pGFdyMrq68RWg0T/dFlnAvTRLkL
wYxIcC6W+mjlAVWkaw69cTj21NkmprRxojJ1GR1oNhMphRhlskMxhqcXT2GHLZfh
ykCk6JODg9vvOxbZy60detsrHHcvtDzgnmTp07+xw/mOeVfsCQ0tvZYKdsTYdEaJ
hZ+/AnI3dJdaHjjiwbtreLWeo8gMmNTe6XYO+Tu+8xTH2pVVOatA+1r4GYXPCWKn
vFp7cFjI9kLcRsXFsh3E/Mgwgsr8R2cAQUi8nd1uORKffo0fb1TmpqZZIweeJp8B
cEcd0KH9zynIDp2k5QD0MYnSxnNYDuPP9itc9dJN/kUZ9MTqdOzlimGxzcPxnaSz
GScWpweCQlv1E0E49KYkT2rig5WnmMqANmdlr8gtTzg9eoxWVAPd0O47og4G8oOw
FkY=
=PrxQ
-END PGP SIGNATURE End Message ---

Bug#939505: bumblebee fails to disable discrete graphics card after upgrade nvidia driver to 430.40-2

[Mo Zhou]

same here.
reflink:
https://devtalk.nvidia.com/default/topic/1050786/linux/nvidia-drivers-430-09-causes-xorg-segfault-at-start-

Bug#875160: marked as done ([qthid-fcd-controller] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 03:05:59 +
with message-id 
and subject line Bug#875160: fixed in qthid-fcd-controller 4.1-4
has caused the Debian Bug report #875160,
regarding [qthid-fcd-controller] 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.)


-- 
875160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qthid-fcd-controller
Version: 4.1-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

= 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: qthid-fcd-controller
Source-Version: 4.1-4

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated 
qthid-fcd-controller 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: Sat, 07 Sep 2019 19:01:21 -0400
Source: qthid-fcd-controller
Architecture: source
Version: 4.1-4
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 658136 686689 875160
Changes:
 qthid-fcd-controller (4.1-4) unstable; urgency=medium
 .
   * Qt5 port (Closes: #875160) (LP: #1757840)
   * use system hidapi instead of buggy local copy (Closes: #658136, #686689)
   * install appdata (LP: #1592495)
Checksums-Sha1:
 742665279b72dd68e53436e162498dd2b80b9d6e 2363 qthid-fcd-controller_4.1-4.dsc
 5c957ea00f5e33d2b71178bf6fcf4f2d6020fc90 15800 
qthid-fcd-controller_4.1-4.debian.tar.xz
 69afa740d9d1c2e227d8babfa91dff5a0343c2c7 11665 
qthid-fcd-controller_4.1-4_amd64.buildinfo
Checksums-Sha256:
 5a781f26f3ff0f4a99ef2b7f3cd8e02d49f6dff3e87c4c3cec5dc1bc70ac94ee 2363 
qthid-fcd-controller_4.1-4.dsc
 28f35e7932f142712d5e9f94e0fb5821640eb384bc6ac0e55707b3d6de8953a7 15800 
qthid-fcd-controller_4.1-4.debian.tar.xz
 6e769375e93735a295618a9620ecafe6cc03461be678f82850384303b590fdc4 11665 
qthid-fcd-controller_4.1-4_amd64.buildinfo
Files:
 292269d24cbcf10179c91e71b77d249c 2363 science optional 
qthid-fcd-controller_4.1-4.dsc
 b73f48aba88e0f8a41acbe7ce5d2c289 15800 science optional 
qthid-fcd-controller_4.1-4.debian.tar.xz
 a100bd668f9d255d0c23f79d68a00237 11665 science optional 

Bug#939662: 回复: Bug#939662 closed by Stephen Kitt (Re: Bug#939662: sys/mman.h not found)

[Zhang Hao]

Dear

Even though I use the parameter "--host=x86_64-w64-32", the gperftools makefile 
dos not passed.
And The gperftools support "mingw-w64" to cross compile on linux.
You can find it on "https://github.com/gperftools/gperftools/issues/878;.
And I have report this issue in 
"https://github.com/gperftools/gperftools/issues/1108;.
The developer told me this is a "#include ." issue, not gperftools' 
problem.




发件人: Debian Bug Tracking System 
发送时间: 2019年9月7日 23:48
收件人: Zhang Hao 
主题: Bug#939662 closed by Stephen Kitt  (Re: Bug#939662: 
sys/mman.h not found)

This is an automatic notification regarding your Bug report
which was filed against the mingw-w64 package:

#939662: sys/mman.h not found

It has been closed by Stephen Kitt .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Stephen Kitt 
 by
replying to this email.


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

Processed (with 1 error): fixup 935717

[Debian Bug Tracking System]

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

> found 935717 16.1-7
Bug #935717 {Done: David Bremner } [haskell-mode] FTBFS: 
tests fail
There is no source info for the package 'haskell-mode' at version '16.1-7' with 
architecture ''
Unable to make a source version for version '16.1-7'
Marked as found in versions 16.1-7.
> notfound 935717 16.1-6
Bug #935717 {Done: David Bremner } [haskell-mode] FTBFS: 
tests fail
No longer marked as found in versions haskell-mode/16.1-6.
> rettitle 935717 botched source package generated from git
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#934799: marked as done (supertuxkart FTBFS (armel, mips, mipsel, m68k, powerpc, sh4): undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 00:34:51 +
with message-id 
and subject line Bug#934799: fixed in supertuxkart 1.0-3
has caused the Debian Bug report #934799,
regarding supertuxkart FTBFS (armel, mips, mipsel, m68k, powerpc, sh4): 
undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
to be marked as done.

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

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


-- 
934799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supertuxkart
Version: 1.0-2
Severity: serious
Tags: ftbfs

supertuxkart currently fails to build from source on armel, mips,
mipsel, m68k, powerpc and sh4 with the following error during final
linking:

| /usr/bin/ld: CMakeFiles/supertuxkart.dir/src/graphics/irr_driver.cpp.o: 
undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'

Possibly, -latomic is missing here.

Helmut
--- End Message ---
--- Begin Message ---
Source: supertuxkart
Source-Version: 1.0-3

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated supertuxkart package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Sep 2019 13:13:25 +0200
Source: supertuxkart
Architecture: source
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Reiner Herrmann 
Closes: 934799
Changes:
 supertuxkart (1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Enable Wayland support.
 - build-depend on libwayland-dev and libxkbcommon-dev
   * Link against libatomic on architectures where it is required.
 (Closes: #934799)
Checksums-Sha1:
 167fba160971831719c936adf767c2d17a18b1b6 2641 supertuxkart_1.0-3.dsc
 f0f1cb9202aee4730ab4e4816cda9857e4766759 2521212 
supertuxkart_1.0-3.debian.tar.xz
 d778305e2ef969bf5c345e34e0f2f4daed0f73d1 11300 
supertuxkart_1.0-3_amd64.buildinfo
Checksums-Sha256:
 3131c73c8c34f603815b7e95dc723139abda596d4f8d2929b885e336add68c9b 2641 
supertuxkart_1.0-3.dsc
 b25b991b3dbbbf2a47e8902d6f0da15d7238b0aa70f3ba33369fb833c7f6cbff 2521212 
supertuxkart_1.0-3.debian.tar.xz
 93ffe474a55a0d1a16c09409e7e5db5d3647c78f7255b6f729eaaa147b35cbb0 11300 
supertuxkart_1.0-3_amd64.buildinfo
Files:
 4ead7c107d594d594ac16a374005bcf3 2641 games optional supertuxkart_1.0-3.dsc
 d93f52b511cf9070a91e81c8b2de1565 2521212 games optional 
supertuxkart_1.0-3.debian.tar.xz
 6f9c842cacefbb0b87642d7abfcb382a 11300 games optional 
supertuxkart_1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl10R3hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkQfgP/RWA2sca7EgiL1JeppwQ4R1DCuOwRLSVLfVR
JXBEHo2ELyZgAN+zGUpXP6kfJw6VrDo6xchWY8Su0BxWHnlbs88nzl4etB3Dlw79
389HqkaHueuKh9dZa3SR2MQyHvg2cjcIeTbLKasTy4r2iOVoANYzQL9sGtb/la8g
NvlWo7vT6+thYKhF447rYYUbkR7PeKRIXnGmGE4G/Ky8TluVP2ibHIIBMVfRLNCI
VnqxojHY64mT9/71MkMxvCayiQX15xakD5Vy+3ecAKiMqVKjMh6ijM2Ok579Jj4n
bizMLJp0WG/qVv5WjNFsYaz3acr9OIyiTIZr94iZqqwur/qY6GjkPS+C29IyCMlM
oVeUV3H8xkPD32TTZ0qJqN0vWraLuTXz80Be+nci3bnRWXSBeX1RXH7861juHddl
9ulOzhMWuFANfQdWzGWr9+8GZZKhwxEHtIFpxcY1MKzrT8u+FupRL/dUXLsbM8MW
XmEftzhQJYUZj7ckpIAFyKzMAlDh2RJ/pDorHxk6HYTCgCAFtDYXPWeirqRKiKGZ
NW9OS0lSpGFe5IlJcQksu8VR5HC/xgripSlxd5/6uAyNwb7uP6KX1SzJgYjVlkV8
VbOaaML+L7C9x/hkMJE5zdTlQlhttOUEa+ldk63HjP/UtVk4k+jFSK/0hzb/V25D
DYQ9jdFG
=+UWb
-END PGP SIGNATURE End Message ---

Bug#939712: performous-composer: missing Depends on libqt5multimedia5-plugins

[Thorsten Glaser]

Package: performous-composer
Version: 2.0+20181009-gitbeeea23-1
Severity: serious
Justification: dependencies incorrect

https://github.com/performous/composer/issues/36

↓

https://stackoverflow.com/a/22046880/2171120

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages performous-composer depends on:
ii  libavcodec58   7:4.1.4-1+b2
ii  libavformat58  7:4.1.4-1+b2
ii  libavutil567:4.1.4-1+b2
ii  libc6  2.28-10
ii  libgcc11:9.2.1-7
ii  libqt5core5a   5.11.3+dfsg1-4
ii  libqt5gui5 5.11.3+dfsg1-4
ii  libqt5multimedia5  5.11.3-2
ii  libqt5network5 5.11.3+dfsg1-4
ii  libqt5widgets5 5.11.3+dfsg1-4
ii  libqt5xml5 5.11.3+dfsg1-4
ii  libstdc++6 9.2.1-7
ii  libswresample3 7:4.1.4-1+b2
ii  libswscale57:4.1.4-1+b2

performous-composer recommends no packages.

performous-composer suggests no packages.

-- no debconf information

Bug#875160: [qthid-fcd-controller] Future Qt4 removal from Buster

[A. Maitland Bottoms]

On Sat, 7 Sep 2019 22:44:00 +0200
Moritz Mühlenhoff  wrote: 
> Hi Maitland,
> we're moving forward with the Qt4 removal.
> 
> qthid-fcd-controller seems dead upstream, are you planning to port it
> yourself or shall we remove it from the archive?
> 
> Cheers,
> Moritz

Yeah, I have tried to get other people to do it.
Thanks to your email, I am starting to port it myself.
(I have gotten other Qt4 code to build under Qt5, so I can no longer
claim ignorance.)

Give me until the end of the month? If I cannot do it myself this
weekend, I might get someone at the GNU Radio conference to do it the
week after next. (Some folk there got gnuradio from qt4 to qt5.)

How hard can it be?

Thanks for the prompting,
-Maitland

Bug#938953: marked as done (libhugetlbfs-bin: missing Breaks+Replaces: libhugetlbfs0 (<< 2.21-2))

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 23:20:09 +
with message-id 
and subject line Bug#938953: fixed in libhugetlbfs 2.21-3
has caused the Debian Bug report #938953,
regarding libhugetlbfs-bin: missing Breaks+Replaces: libhugetlbfs0 (<< 2.21-2)
to be marked as done.

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

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


-- 
938953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhugetlbfs-bin
Version: 2.21-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libhugetlbfs-bin_2.21-2_amd64.deb ...
  Unpacking libhugetlbfs-bin (2.21-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libhugetlbfs-bin_2.21-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ld.hugetlbfs', which is also in package 
libhugetlbfs0:amd64 2.21-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libhugetlbfs-bin_2.21-2_amd64.deb


cheers,

Andreas


libhugetlbfs0=2.21-1+b1_libhugetlbfs-bin=2.21-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libhugetlbfs
Source-Version: 2.21-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Sep 2019 07:36:09 +0900
Source: libhugetlbfs
Architecture: source
Version: 2.21-3
Distribution: unstable
Urgency: medium
Maintainer: Punit Agrawal 
Changed-By: Punit Agrawal 
Closes: 938953
Changes:
 libhugetlbfs (2.21-3) unstable; urgency=medium
 .
   * Add Breaks+Replaces tag for libhugetlbfs-bin (Closes: #938953)
Checksums-Sha1:
 08d8c7105b4ffae2a13accf36d1a42ab386326ad 2324 libhugetlbfs_2.21-3.dsc
 08831ae9457f29305dea21be422e67bc0978be29 5892 libhugetlbfs_2.21-3.debian.tar.xz
 df7f0e5fb73d14e9d06ee49fbc37662878739804 7094 
libhugetlbfs_2.21-3_amd64.buildinfo
Checksums-Sha256:
 927381b77c5e88b9519f912a108942f07df43c08f08a3334f1ab41cc7b8a8cb4 2324 
libhugetlbfs_2.21-3.dsc
 3220c5298b419af1ad631165c78b6e4419307a4cdc13374548b69e6e67d70f0d 5892 
libhugetlbfs_2.21-3.debian.tar.xz
 c1f072cabf10a8b3d5354a0ee817a7b21d459d2dc7841224785ec18408e4a5ed 7094 
libhugetlbfs_2.21-3_amd64.buildinfo
Files:
 9375177568bfc516b255f3d325093f4d 2324 libs optional libhugetlbfs_2.21-3.dsc
 b6c911b101303784aded3c6ce952d7a1 5892 libs optional 
libhugetlbfs_2.21-3.debian.tar.xz
 bfcc70872394c6d81e516e32258ea5a5 7094 libs optional 
libhugetlbfs_2.21-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEvZ5M7BP8NElWggdO9Tkv0hP7/t0FAl10NcQRHHB1bml0QGRl
Ymlhbi5vcmcACgkQ9Tkv0hP7/t21wg//cwLEsSEITPwCPtCj29wkJv5Ht5PWsi+/
deDKo3C6tUifUohCkkyQe6OTfmBRcFbbnEIqdONbuw10bd6EI85b1H0LJeMpo2gM
tUwlvT6hqQC2u1fb5nsjZzFMWkKdVaGpja6HdHYO6qNWmQYjK494utVFUR1KKqHA
ZXLSdSKcACoPlOWO/kH+oGNVeC16PNy4HUhqWbhp4wWS84BHchNAeoWu3vqNuy2K
nt5ngfwf9q0OF13ZC27JPcek1Ni1QXOF/EsYi93nKcZKrQRXIrqZX/KCtirGPzSN
P/GWrGnYlBYaLl4qKdSa0Ana7gwcbq3hX0OxQMO1hqvLDAWsWYuhaRSkWo5EoBui
+IGFQvGUl43XYoR5j3pXf5v+Qtlj2rMx4f6r/QQsx/RMeCRXbwhTZhud9zDacWLy
VuY8TuXUKivyozBOQzYQRjFT5SMOrC5NPOFtRE9s4LB4fy4FT3E7CHzaT4f0CdIP
w5P+sL6o0wX5SnQmgpuu/8xwRmcw7arvZwmz5Tp3gkPT0lLQA/WrPBckm1otx0QT
8ILAr8YLal+m/q9Vu/bm3fwD/6l8OvdpTS80jMIY4R/BuNdj/0sg0yVWkQldZ7W9
Er1PfdkaOl/curaZCANqBZWs305bm5Jkhx5kJRO/LrpAsuIkf5P10hKzHbrSfNY5
qcLhFF/mvn4=
=EZno
-END PGP SIGNATURE End Message ---

Bug#932882: marked as done (python{,3}-pyroute2: /usr/bin/ss2 shipped in both packages)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 23:21:42 +
with message-id 
and subject line Bug#932882: fixed in pyroute2 0.5.4-2
has caused the Debian Bug report #932882,
regarding python{,3}-pyroute2: /usr/bin/ss2 shipped in both packages
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.)


-- 
932882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyroute2
Version: 0.5.4-1
Severity: serious

/usr/bin/ss2 is shipped in python-pyroute2 and python3-pyroute2 without any
kind of Conflicts/Replaces resulting in an error when trying to install
both packages:

> Preparing to unpack .../10-python-pyroute2_0.5.4-1_all.deb ...
> Unpacking python-pyroute2 (0.5.4-1) over (0.5.2-1) ...
> Preparing to unpack .../11-python3-pyroute2_0.5.4-1_all.deb ...
> Unpacking python3-pyroute2 (0.5.4-1) over (0.5.2-1) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-0jYnUK/11-python3-pyroute2_0.5.4-1_all.deb (--unpack):
>  trying to overwrite '/usr/bin/ss2', which is also in package python-pyroute2 
> 0.5.4-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Cheers,
Felix
--- End Message ---
--- Begin Message ---
Source: pyroute2
Source-Version: 0.5.4-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated pyroute2 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: Thu, 15 Aug 2019 15:02:27 +0200
Source: pyroute2
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Closes: 932882 937529
Changes:
 pyroute2 (0.5.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Thomas Goirand ]
   * Removed Python 2 support (Closes: #937529).
 - This also fixes /usr/bin/ss2 shipped in both Python 2 and Python 3
   versions of this package. Adding Breaks+Replaces to make sure upgrades
   are smooth (Closes: #932882).
   * Add remove-Google-Analytics-from-docs.patch.
   * Move the package to the DPMT:
 - Change the Maintainer field.
 - Fix VCS fields.
 - Add myself and Florian Pelgrim as uploaders.
   * Fixed debian/python-pyroute2-doc.links which were adding symlinks in the
 wrong folder.
   * Fixed debian/python-pyroute2-doc.doc-base which was also poiting to the
 wrong folder.
   * Added missing runtime depends: python3-psutil.
   * Fixed debian/copyright missing many licenses.
Checksums-Sha1:
 5ff4967edbf04c11afecd360e70323fa1b053baf 2144 pyroute2_0.5.4-2.dsc
 1a816299b2ef4e084a033ca4dae1b4f7a7344605 5636 pyroute2_0.5.4-2.debian.tar.xz
 df3ea68043d424130a2cb54b46f02d409b9cc6e4 7171 pyroute2_0.5.4-2_amd64.buildinfo
Checksums-Sha256:
 77ce01f8665501724414a95cd27f5cf9c62d7f4d942eb5a2887d59cc2c1dd623 2144 
pyroute2_0.5.4-2.dsc
 97a75964c53077231cc0c9daee2a18fffb84b1fad296d6683e5121fb2883fa19 5636 
pyroute2_0.5.4-2.debian.tar.xz
 5a00f85e3ec1f85f83e0d92c176d1eaf5590f87299edd6c142167385978e38e2 7171 
pyroute2_0.5.4-2_amd64.buildinfo
Files:
 9b47a97aaa392effface10d00ecf3cbf 2144 python optional pyroute2_0.5.4-2.dsc
 f21179ea8647436927cf7deeefee5cf9 5636 python optional 
pyroute2_0.5.4-2.debian.tar.xz
 5a786c0a46e86070c032b99718445370 7171 python optional 
pyroute2_0.5.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl10NhoACgkQ1BatFaxr
Q/5Hwg/8D0chkAWCpZhpq9baXGriMBWZvGRRzMUHmuacbhxDcxOXzOJq9B7LYvri
GfMLLQAWljQG7YGa8Ws42EqDjeH04N1jt9HeMJ2VMVmGIf6w/ubBT+ZoC6eMRPHz
ObCORxsDGcA5QKXtU77rj99KQFNyTaM/2pO1xhKlNwKQYw1pceuSRosOZs505v65
CSUaE0vxRisWj/WZ8FGH7RbzNaKEJ85AkSuQ6PPSI74SQGndsll+neUuqJtYKdhk
rx10EPTU9R5s73z2J8XE59qWYgu49EZevvbONAYPtepMJL8Gm8l56gHSfRy7NLhl
wvwRe7dnVnFTy0TjG8VAracrnMXvt6ZuQkWg56G2PDVw5i0cmP0KTvD09715k3N7
2z3teQk82ljKnn3MjgoX0jFgYVjIaogIq46i9cYEOIMO+KSJkXauJx40NPd3LTiL
cyxlfkusuErJQEpRC/rS+r0dz/pRCNYOhvUrz0p2oP1R6NmlY7+gRn/AJRGJG6Gf

Bug#939648: marked as done (git-buildpackage: FTBFS in unstable: flake8: E117 over-indented)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 21:33:48 +
with message-id 
and subject line Bug#939648: fixed in git-buildpackage 0.9.15
has caused the Debian Bug report #939648,
regarding git-buildpackage: FTBFS in unstable: flake8: E117 over-indented
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.)


-- 
939648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.9.14
Severity: serious
Tags: ftbfs
Justification: fails to build from source

During test-builds to evaluate whether the new version of gtk-doc-tools is
ready for upload to unstable, git-buildpackage failed to build. I can
reproduce the build failure in a pure unstable sbuild environment:

>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> make
> make[2]: Entering directory '/<>'
> flake8
> ./gbp/patch_series.py:148:17: E117 over-indented
> ./gbp/scripts/buildpackage.py:333:13: E117 over-indented
> ./gbp/scripts/import_orig.py:82:17: E117 over-indented
> ./gbp/scripts/common/import_orig.py:71:13: E117 over-indented
> ./.pybuild/cpython3_3.7/build/gbp/patch_series.py:148:17: E117 over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/buildpackage.py:333:13: E117 
> over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/import_orig.py:82:17: E117 
> over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/common/import_orig.py:71:13: E117 
> over-indented
> make[2]: *** [Makefile:20: syntax-check] Error 1

Full build log attached.

I would recommend skipping stylistic/non-functional checks like this one,
or making them only produce warnings, when "official" packages are built
in a Debian environment (the style checks can still be fatal when run as
part of `make check` during development, of course). Perhaps something
like this:

# in debian/rules
export IGNORE_STYLE_CHECKS = 1

# in the tests, replacing the flake8 invocation
flake8 || [ -n "$IGNORE_STYLE_CHECKS" ]

Regards,
smcv


git-buildpackage_0.9.14_all_20190907t091327.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: git-buildpackage
Source-Version: 0.9.15

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated git-buildpackage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Sep 2019 10:58:51 -0700
Source: git-buildpackage
Architecture: source
Version: 0.9.15
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 782886 939648
Changes:
 git-buildpackage (0.9.15) unstable; urgency=medium
 .
   [ Guido Günther ]
   * [b12b85a] import-orig: Allow to run a post unpack hook.
 The working directory of the hook is the top temporary directory the
 tarballs are being unpacked into.
   * [6696656] docs: Document gbp import-orig --postunpack
   * [292edcf] import_orig: Move upstream-vcs-tag's help to config.
 This way it can be shared.
   * [61757c0] import_dsc: Support upstream-vcs-tag (Closes: #782886)
   * [1acd0bb] docs: import-dsc: Document --upstream-vcs-tag
   * [b888349] gbp-clone: Support salsa: pseudo urls
   * Fix flake8 errors (Closes: #939648)
 .
   [ Hideki Yamane ]
   * [d1960b3] gbp.conf: Set default compresson to xz.
 The value is commented out so does not have any effect but it's
 better to recommend the right value.
 .
   [ Maximiliano Curia ]
   * [8afb7ee] import-orig/merge_replace Avoid calling force_head.
 The debian_merge_by_replace function ends up calling force_head, but up to
 this point the current branch could be anything, and thus when called from
 a feature branch the latest commits get lost.
Checksums-Sha1:
 f27941cab1cb18fbd9f0c0740cb5dcee2eb3893a 2274 git-buildpackage_0.9.15.dsc
 47f92b695b167699b967e3de46eb9bf5cb697ab0 890616 git-buildpackage_0.9.15.tar.xz
 57783f1890cf12b5aafff64a922a4552b820d190 12548 

Bug#925624: [Debichem-devel] Bug#925624: Bug#925624: abinit: ftbfs with GCC-9

[Michael Banck]

Hi,

On Sat, Sep 07, 2019 at 10:50:34PM +0200, Michael Banck wrote:
> > Program received signal SIGSEGV: Segmentation fault - invalid memory 
> > reference.
> > 
> > Backtrace for this error:
> > #0  0x7f063149eb40 in ???
> > #1  0x7f063149dd75 in ???
> > #2  0x7f063115893f in ???
> > #3  0x5612b98bb243 in forces_
> > at /<>/src/67_common/forces.F90:462
> 
> So at that line we have:
> 
> | if (usefock==1 .and. associated(fock).and.fock%fock_common%optfor) then
> 
> and if I step through that function with gdb, usefock is 0 (while fock
> is pointing to 0x0).
> 
> If I comment out the above if block (plus two more pretty much identical
> ones in m_forstr.F90 and m_stress.F90) most of the tests run fine (I
> guess the other ones really do need fock).
> 
> I am a bit baffled why gfortran compiles this in such a way (at -g
> without any -O as well) that we get a segfault here. I now tried with
> FCFLAGS='-g -O2' and then the test suite runs fine, so reassigning to
> gfortran-9 for now, do you have an idea what's going on?
> 
> (I filed this one upstream as well:
> https://github.com/abinit/abinit/issues/25)

So it appears that fock%fock_common%optstr cannot be guaranteed not to
be evaluated after associated(fock) is false as the Fortran language
apparently does not define short-circuit beahviour, see
https://www.scivision.dev/fortran-short-circuit-logic/

That explains why it works fine at -O2 (and would as well at -O1 in
gfortran), but crashed in -O0. I wonder why it built fine at -O0 in
stable though, it might be that the gfortran behaviour has been changed
recently.

I guess the fix would be to have two ifs here, like:

| if (usefock==1 .and. associated(fock)) then
|   if (fock%fock_common%optfor) then
| grtn(:,:)=grtn(:,:)+fock%fock_common%forces(:,:)
|   end if
| end if

I've uploaded abinit with FCFLAGS=-O2 now, should we close this bug and
leave it to the abinit maintainers to fix it properly, or do you want to
reassign it back?

Thanks to juliank for pointing me to the potential short-circuit logic
issue.


Michael

Bug#875022: marked as done ([libjdns] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 21:19:43 +
with message-id 
and subject line Bug#875022: fixed in libjdns 2.0.3-1.1
has caused the Debian Bug report #875022,
regarding [libjdns] 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.)


-- 
875022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjdns
Version: 2.0.3-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: libjdns
Source-Version: 2.0.3-1.1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Sep 2019 22:44:50 +0200
Source: libjdns
Architecture: source
Version: 2.0.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Ahlers 
Changed-By: Moritz Muehlenhoff 
Closes: 875022
Changes:
 libjdns (2.0.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop Qt4 packages (Closes: #875022)
Checksums-Sha1:
 52d19c2d73d6539b9c5bf5382455f738895b123f 2108 libjdns_2.0.3-1.1.dsc
 d9e06633b631ecbddd9c2c55bc567ba43951bbda 3020 libjdns_2.0.3-1.1.debian.tar.xz
 813ceff6ac8b785f23c7fc3e17d63d8d8364c445 12839 
libjdns_2.0.3-1.1_amd64.buildinfo
Checksums-Sha256:
 c4a81fe0415f84de6b5531c92793054a3a733e3fe677256aad81f1a58e960a7b 2108 
libjdns_2.0.3-1.1.dsc
 b2932cce3babc73f40b7e35eed5e75be4031aab05c86f1ba85d4269a96fc7597 3020 
libjdns_2.0.3-1.1.debian.tar.xz
 7fce0522b958061f92ea7599ae1f0e83082c7450c8b5cf5584e26d707a769aa2 12839 
libjdns_2.0.3-1.1_amd64.buildinfo
Files:
 5653c69efe99dec05419e7051079886b 2108 libs optional libjdns_2.0.3-1.1.dsc
 d0355852bb0da9901375e93e518e9bbc 3020 libs optional 
libjdns_2.0.3-1.1.debian.tar.xz
 064b3e41bcd642574c71a1f7f6618e4f 12839 libs optional 
libjdns_2.0.3-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAl10FyIACgkQEMKTtsN8
TjbICw/8C+NMwntcYlvZnK9u0Lkk+rFO2ywhLzGGix9PkXIJ/7cxeYsLn50UYsOo
WTbspa6lFayftgZGHkzTfC/hLzjAmlGEb5Fnx+4NUgGtwSKJHhuh/4MrmqdvIq1l

Bug#875494: connectomeviewer: Qt4 removal form Buster

[Moritz Mühlenhoff]

On Sat, Aug 24, 2019 at 08:19:02PM -0400, Scott Kitterman wrote:
> On Mon, 11 Sep 2017 16:33:30 -0300 =?utf-8?q?
> Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=  wrote:
> > Source: connectomeviewer
> > Version: 2.1.0-1.1
> > Severity: minor
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> > 
> > Note: this bug is being filled because your package recommends python-
> qscintilla2.
> > 
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as announced in:
> > 
> > [announced]
> > 
> 
> This is now in progress.  Upstream for this package seems dead (no commits in 
> upstream git in nearly two years).  It seems likely the right answer is 
> probably to remove the package.
> 
> This is the last package left in the archive that needs python-qscintilla2.
> 
> If no one indicates they are going to upload this without the python-
> qscintilla2 Recommends (I have no idea if that even makes sense), then I'll 
> file an QoRA rm bug soon.

Given that there was no further feedback, 
https://github.com/LTS5/connectomeviewer/
has no signs of Qt5 porting activity and the last maintainer upload was in 2012
I just filed a removal bug so that we can move forward with qscintilla2.

There's still ample time to re-introduced it before bullseye if someone steps
up and ports it.

Cheers,
Moritz

Processed: severity of 938874 is serious, block 938874 with 936341 938873

[Debian Bug Tracking System]

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

> severity 938874 serious
Bug #938874 [src:yum-metadata-parser] yum-metadata-parser: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> block 938874 with 936341 938873
Bug #938874 [src:yum-metadata-parser] yum-metadata-parser: Python2 removal in 
sid/bullseye
938874 was not blocked by any bugs.
938874 was not blocking any bugs.
Added blocking bug(s) of 938874: 938873 and 936341
> thanks
Stopping processing here.

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

Bug#939628: should archipel-* packages be removed from Debian?

[Sandro Tosi]

>  I'm in a rush now but will try to file the RM bug(s) today or if you
> may have more time please do it yourself.

no worries, i'm gonna file the RM bugs now -- thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#875184: [sofa-framework] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:10:03PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: sofa-framework
> Version: 1.0~beta4-12
> 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

The current releases on https://github.com/sofa-framework claim to be Qt5
compatible. Is anyone working on updating the package or should it be removed?

sofa-framework is one of the three remaining reverse dependencies of
libqwt5-qt4-dev at this point.

Cheers,
Moritz

Bug#875160: [qthid-fcd-controller] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:07:58PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: qthid-fcd-controller
> Version: 4.1-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 Maitland,
we're moving forward with the Qt4 removal.

qthid-fcd-controller seems dead upstream, are you planning to port it yourself
or shall we remove it from the archive?

Cheers,
Moritz

Processed: Re: [Debichem-devel] Bug#925624: abinit: ftbfs with GCC-9

[Debian Bug Tracking System]

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

> reassign 925624 gfortran-9
Bug #925624 [src:abinit] abinit: ftbfs with GCC-9
Bug reassigned from package 'src:abinit' to 'gfortran-9'.
No longer marked as found in versions abinit/8.8.4-2.
Ignoring request to alter fixed versions of bug #925624 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#925624: [Debichem-devel] Bug#925624: abinit: ftbfs with GCC-9

[Michael Banck]

reassign 925624 gfortran-9
thanks

Hi Matthias,

On Wed, Mar 27, 2019 at 07:43:54PM +, Matthias Klose wrote:
> Command   /<>/src/98_main/abinit <
> /<>/tests/Test_suite/fast_t30/t30.stdin >
> /<>/tests/Test_suite/fast_t30/t30.stdout 2>
> /<>/tests/Test_suite/fast_t30/t30.stderr returned
> exit_code: 139
> 
> [fast][t30][np=1]: fldiff.pl fatal error:
> The diff analysis cannot be done: the number of lines to be analysed differ.
> File /<>/tests/fast/Refs/t30.out: 399 lines, 44 ignored
> File /<>/tests/Test_suite/fast_t30/t30.out: 397 lines, 43 
> ignored [file=t30.out]
> [fast][t30][np=1]Test was not expected to fail but subprocesses returned 
> 139
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory 
> reference.
> 
> Backtrace for this error:
> #0  0x7f063149eb40 in ???
> #1  0x7f063149dd75 in ???
> #2  0x7f063115893f in ???
> #3  0x5612b98bb243 in forces_
>   at /<>/src/67_common/forces.F90:462

So at that line we have:

| if (usefock==1 .and. associated(fock).and.fock%fock_common%optfor) then

and if I step through that function with gdb, usefock is 0 (while fock
is pointing to 0x0).

If I comment out the above if block (plus two more pretty much identical
ones in m_forstr.F90 and m_stress.F90) most of the tests run fine (I
guess the other ones really do need fock).

I am a bit baffled why gfortran compiles this in such a way (at -g
without any -O as well) that we get a segfault here. I now tried with
FCFLAGS='-g -O2' and then the test suite runs fine, so reassigning to
gfortran-9 for now, do you have an idea what's going on?

(I filed this one upstream as well:
https://github.com/abinit/abinit/issues/25)


Michael

Bug#934814: libdballe7: built with libmariadbclient18, which doesn't exist any longer

[Enrico Zini]

On Sat, Aug 24, 2019 at 05:11:22PM +0200, Otto Kekäläinen wrote:

> Increasing severity to 'serious' since this is one of the 5 packages
> what still depend on libmariadbclient18, which will soon be removed
> from unstable and then render this package uninstallable. Please
> rebuild and upload, so that the package will automatically be built
> and depend on newest libraries (including libmariadb3 which has
> replaced libmariadbclient18).

I've done a new upload, I took advantage to upload a new upstream
release, as the current one in Debian had become rather obsolete.

Unfortunately, it's still stuck in binary-NEW since a week.

This issue should be fixed once the package passes binary-NEW.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#913978: (no subject)

[Mika Hanhijärvi]

Hi


Has there been any progress in fixing this bug?Atleast I have not heard
about any progress at all. Looks like Gnome developers do not care about
accessibility at all...

Bug#817713: vdk2-tutorial: diff for NMU version 1.1-3.1

[Boyuan Yang]

Control: tags 817713 + patch
Control: tags 817713 + pending

Dear maintainer,

I've prepared an NMU for vdk2-tutorial (versioned as 1.1-3.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -Nru vdk2-tutorial-1.1/debian/changelog vdk2-tutorial-
1.1/debian/changelog
--- vdk2-tutorial-1.1/debian/changelog  2019-09-07 15:39:45.0 -0400
+++ vdk2-tutorial-1.1/debian/changelog  2019-09-07 15:25:32.0 -0400
@@ -1,3 +1,20 @@
+vdk2-tutorial (1.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
++ Bump debhelper compat version to v12. (Closes: #817713)
++ Bump Standards-Version to 4.4.0.
++ Mark package vdk2-tutorial as Multi-Arch: foreign.
++ Mark the section for source package as doc. (lintian warning)
++ Let the binary package depends on ${misc:Depends}
+  (lintian warning)
+  * debian/rules: Use dh sequencer accordingly.
+  * debian/source/format: Use "3.0 (quilt)" format.
+  * debian/lintian-overrides: Add override for
+copyright-should-refer-to-common-license-file-for-gfdl.
+
+ -- Boyuan Yang   Sat, 07 Sep 2019 15:25:32 -0400
+
 vdk2-tutorial (1.1-3) unstable; urgency=low
 
   * rebuild to finish /usr/doc transition (closes: #359599)
diff -Nru vdk2-tutorial-1.1/debian/compat vdk2-tutorial-1.1/debian/compat
--- vdk2-tutorial-1.1/debian/compat 2019-09-07 15:39:45.0 -0400
+++ vdk2-tutorial-1.1/debian/compat 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-4
\ No newline at end of file
diff -Nru vdk2-tutorial-1.1/debian/control vdk2-tutorial-1.1/debian/control
--- vdk2-tutorial-1.1/debian/control2019-09-07 15:39:45.0 -0400
+++ vdk2-tutorial-1.1/debian/control2019-09-07 15:19:26.0 -0400
@@ -1,12 +1,14 @@
 Source: vdk2-tutorial
+Section: doc
 Priority: optional
 Maintainer: Michael Vogt 
-Build-Depends: debhelper (>> 3.0.0)
-Standards-Version: 3.5.6
+Build-Depends: debhelper-compat (= 12)
+Standards-Version: 4.4.0
 
 Package: vdk2-tutorial
-Section: doc
 Architecture: all
+Multi-Arch: foreign
+Depends: ${misc:Depends}
 Suggests: libvdk2-dev
 Description: Tutorial for the Visual Development Kit C++ library 2 
  The Visual Development Kit2 (VDK2) is a C++ library
diff -Nru vdk2-tutorial-1.1/debian/copyright vdk2-tutorial-
1.1/debian/copyright
--- vdk2-tutorial-1.1/debian/copyright  2019-09-07 15:39:45.0 -0400
+++ vdk2-tutorial-1.1/debian/copyright  2019-09-07 15:24:20.0 -0400
@@ -7,4 +7,4 @@
 
 Copyright: 
 GFDL 1.1 (GNU Free Documentation License), see
-http://www.gnu.org/copyleft/fdl.html
\ No newline at end of file
+https://www.gnu.org/licenses/fdl-1.1.html
diff -Nru vdk2-tutorial-1.1/debian/lintian-overrides vdk2-tutorial-
1.1/debian/lintian-overrides
--- vdk2-tutorial-1.1/debian/lintian-overrides  1969-12-31 19:00:00.0
-0500
+++ vdk2-tutorial-1.1/debian/lintian-overrides  2019-09-07 15:25:29.0
-0400
@@ -0,0 +1,2 @@
+# GFDL 1.1 not present in /usr/share/common-licenses/ directory
+vdk2-tutorial: copyright-should-refer-to-common-license-file-for-gfdl
diff -Nru vdk2-tutorial-1.1/debian/rules vdk2-tutorial-1.1/debian/rules
--- vdk2-tutorial-1.1/debian/rules  2019-09-07 15:39:45.0 -0400
+++ vdk2-tutorial-1.1/debian/rules  2019-09-07 15:25:32.0 -0400
@@ -1,52 +1,4 @@
 #!/usr/bin/make -f
 
-# debian/rules file for gtk+ Debian package
-# written Feb 1999 by Ionutz Borcoman 
-# used script written  April 1998 by Ben Gertzfield 
-
-build: build-stamp
-build-stamp:
-   dh_testdir
-   touch build-stamp
-
-clean:
-   dh_testdir
-   dh_testroot
-   rm -f build-stamp install-stamp 
-   # Add here commands to clean up after the build process.
-   dh_clean
-
-install: install-stamp
-install-stamp: build
-   dh_testdir
-   dh_testroot
-   dh_clean
-   touch install-stamp
-
-# Build architecture-independent files here.
-binary-indep: build install vdk-doc
-
-# Build architecture-dependent files here.
-binary-arch: 
-
-vdk-doc: build
-   dh_testdir
-   dh_testroot
-   dh_installdirs
-   dh_installdocs
-   dh_installchangelogs
-   dh_strip
-   dh_compress
-   dh_fixperms
-   dh_installdeb
-   dh_shlibdeps
-   dh_gencontrol
-   dh_makeshlibs
-   dh_md5sums
-   dh_builddeb
-
-source
diff:  
-   @echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+%:
+   dh $@
diff -Nru vdk2-tutorial-1.1/debian/source/format vdk2-tutorial-
1.1/debian/source/format
--- vdk2-tutorial-1.1/debian/source/format  1969-12-31 19:00:00.0
-0500
+++ vdk2-tutorial-1.1/debian/source/format  2019-09-07 15:08:39.0
-0400
@@ -0,0 +1 @@
+3.0 (quilt)


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

Processed: vdk2-tutorial: diff for NMU version 1.1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 817713 + patch
Bug #817713 [src:vdk2-tutorial] vdk2-tutorial: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817713 + pending
Bug #817713 [src:vdk2-tutorial] vdk2-tutorial: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#875250: Bug#875258: [scim] Future Qt4 removal from Buster

[Tz-Huan Huang]

On Fri, Aug 30, 2019 at 4:39 AM Moritz Mühlenhoff  wrote:

> On Sat, Sep 09, 2017 at 11:09:36PM +0200, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > Source: scim
> >
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as [announced] in:
> >
> > [announced] <
> https://lists.debian.org/debian-devel-announce/2017/08/msg6.html>
> >
> > 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] <
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522>
> >
> > 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
>
> Given upstream's comments on https://github.com/scim-im/scim/issues/21,
> let's
> move forward by dropping the scim-qt-immodule binary package? It can still
> be re-added if a Qt5 port appears at a later time.
>

Sure. I have made the update and been waiting for maintainer's review.

  https://github.com/leggewie-DM/scim/pull/1

Thanks,
Tz-Huan

Bug#939461: marked as done (node-supports-color breaks node-mocha autopkgtest: AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 19:07:52 +
with message-id 
and subject line Bug#939461: fixed in node-mocha 6.2.0+ds1-1
has caused the Debian Bug report #939461,
regarding node-supports-color breaks node-mocha autopkgtest: AssertionError 
[ERR_ASSERTION]: The expression evaluated to a falsy value
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.)


-- 
939461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-supports-color, node-mocha
Control: found -1 node-supports-color/6.1.0-2
Control: found -1 node-mocha/4.1.0+ds3-5
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of node-supports-color the autopkgtest of
node-mocha fails in testing when that autopkgtest is run with the binary
packages of node-supports-color from unstable. It passes when run with
only packages from testing. In tabular form:
   passfail
node-supports-colorfrom testing6.1.0-2
node-mocha from testing4.1.0+ds3-5
all others from testingfrom testing

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

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=node-supports-color

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

  1 failing

  1) Mocha
   should not output colors to pipe:

  Uncaught AssertionError [ERR_ASSERTION]: The expression
evaluated to a falsy value:

  assert(stdout.indexOf('[90m') === -1)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-mocha
Source-Version: 6.2.0+ds1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Sep 2019 20:18:02 +0200
Source: node-mocha
Architecture: source
Version: 6.2.0+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 935323 939461
Changes:
 node-mocha (6.2.0+ds1-1) experimental; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.4.0
   * Add debian/gbp.conf
   * Fix repacksuffix
   * New upstream version 6.2.0+ds1 (Closes: #939461)
   * Refresh patches
   * Update rollup config and use rollup-plugin-ignore (embedded)
   * Switch build and install to pkg-js-tools
   * Embed ansi-colors, log-symbols, node-environment-flags, object.assign,
 object-keys, has-symbols and flat as components
   * Add node-define-properties in dependencies
   * Replace oxygen-icon-theme dependency by a simple copy of the 2 images
 needed (Closes: #935323)
   * Embed object-keys, has-symbols and flat
   * Update lintian overrides
   * Replace test by a simple mocha --help (waiting for "unexpected" package)
   * Remove jekyll from build dependencies
Checksums-Sha1: 
 40f0a23f39ca26cb1a94392bb91b353ba09a948e 5464 node-mocha_6.2.0+ds1-1.dsc
 166352efbb8cd71aa1eded303641fddebf2986b5 14476 
node-mocha_6.2.0+ds1.orig-ansi-colors.tar.xz
 c32874ac2fe8cd80e399c6eb355d1a6439be54ec 5592 
node-mocha_6.2.0+ds1.orig-flat.tar.xz
 37c405c601079de77f39573efab96af2f9485014 4648 
node-mocha_6.2.0+ds1.orig-has-symbols.tar.xz
 26ee54dc2a721dd23543667f0ed1e9564d4b69e5 16664 
node-mocha_6.2.0+ds1.orig-log-symbols.tar.xz
 

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Paul Gevers]

Source: clazy
Version: 1.5-1
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

During a binNMU of clazy during the llvm-defaults transition, you package FTBFS
on armel. Can you please check and fix the situation?

The last part of the log message as currently shown on 
https://buildd.debian.org/status/fetch.php?pkg=clazy=armel=1.5-1%2Bb1=1567623182=0
 reads:

[100%] Linking CXX executable bin/clazy-standalone
/usr/bin/cmake -E cmake_link_script CMakeFiles/clazy-standalone.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wno-class-memaccess 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-common -Woverloaded-virtual 
-Wcast-qual -fno-strict-aliasing -pedantic -Wno-long-long -Wall -W 
-Wno-unused-parameter -Wwrite-strings -fno-exceptions -fno-rtti -fPIC  
-Wl,-z,relro -Wl,-z,now -latomic -rdynamic 
CMakeFiles/clazy-standalone.dir/src/ClazyStandaloneMain.cpp.o  -o 
bin/clazy-standalone  -L/usr/lib/llvm-8/lib 
-Wl,-rpath,/usr/lib/llvm-8/lib:/<>/obj-arm-linux-gnueabi/lib: 
lib/ClazyPlugin.so /usr/lib/llvm-8/lib/libclangFrontend.a 
/usr/lib/llvm-8/lib/libclangDriver.a /usr/lib/llvm-8/lib/libclangCodeGen.a 
/usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libclangAnalysis.a 
/usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
/usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
/usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
/usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
/usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
/usr/lib/llvm-8/lib/libclangFrontendTool.a 
/usr/lib/llvm-8/lib/libclangRewrite.a 
/usr/lib/llvm-8/lib/libclangSerialization.a 
/usr/lib/llvm-8/lib/libclangTooling.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
/usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libLLVM-8.so 
/usr/lib/llvm-8/lib/libclangAnalysis.a 
/usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
/usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
/usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
/usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
/usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
/usr/lib/llvm-8/lib/libclangFrontendTool.a 
/usr/lib/llvm-8/lib/libclangSerialization.a 
/usr/lib/llvm-8/lib/libclangTooling.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
/usr/lib/llvm-8/lib/libLLVM-8.so 
/usr/bin/ld: lib/ClazyPlugin.so: undefined reference to symbol 
'__atomic_load_4@@LIBATOMIC_1.0'
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libatomic.so: error adding 
symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/clazy-standalone.dir/build.make:128: 
bin/clazy-standalone] Error 1
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/clazy-standalone.dir/all] 
Error 2
make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[1]: *** [Makefile:155: all] Error 2
make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi'
dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install 
--strip-program=true" returned exit code 2
make: *** [debian/rules:19: build-arch] Error 255

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (200, 'testing'), (100, 
'testing')
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-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl1z/eoACgkQnFyZ6wW9
dQob6Qf+IBuxWmNSd6kwO4kHCm16SInrB4a3Rs2/PIcFopnGiQKY7UNza6iLcw2f
dd+uaLJkKQzYRq6IMHAfEQe7vjF3lB1oITyJNKx4VRpxQ8fMBkwVQsNsErs2ACBu
GFmFNoJaEWlaC0rZcpoHIZU2x98jhQheGv/hfQ2L8FaoKUqwo2PRGgFKoR0kGLvN
N6KZottKecx8M0BiIdyTHi1YC/c5VWqXue5vWRLmLpOPqs40+xZQClcutfhD/F0U
nSYRQPuYW+I0cdFObARzY80kqGqg6lwGGEb3SczUHSAuTPfLMFvaVCNL1FZN7TCg
FgGro3JPdiKOclpK9OL+KHI3JJMgUQ==
=Tiwf
-END PGP SIGNATURE-

Processed: reassign 939460 to src:libmojo-ioloop-readwriteprocess-perl

[Debian Bug Tracking System]

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

> reassign 939460 src:libmojo-ioloop-readwriteprocess-perl 0.23-1
Bug #939460 [libmojo-ioloop-readwriteprocess-perl] 
libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 
8.23
Bug reassigned from package 'libmojo-ioloop-readwriteprocess-perl' to 
'src:libmojo-ioloop-readwriteprocess-perl'.
No longer marked as found in versions 
libmojo-ioloop-readwriteprocess-perl/0.23-1.
Ignoring request to alter fixed versions of bug #939460 to the same values 
previously set
Bug #939460 [src:libmojo-ioloop-readwriteprocess-perl] 
libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 
8.23
Marked as found in versions libmojo-ioloop-readwriteprocess-perl/0.23-1.
> thanks
Stopping processing here.

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

Processed: retitle 939460 to libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 8.23 ...

[Debian Bug Tracking System]

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

> retitle 939460 libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest 
> failures with mojo 8.23
Bug #939460 [libmojo-ioloop-readwriteprocess-perl] libmojolicious-perl breaks 
libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at 
/usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.
Changed Bug title to 'libmojo-ioloop-readwriteprocess-perl: FTBFS and 
autopkgtest failures with mojo 8.23' from 'libmojolicious-perl breaks 
libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at 
/usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.'.
> tags 939460 + ftbfs
Bug #939460 [libmojo-ioloop-readwriteprocess-perl] 
libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 
8.23
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: reassign 939460 to libmojo-ioloop-readwriteprocess-perl ...

[Debian Bug Tracking System]

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

> reassign 939460 libmojo-ioloop-readwriteprocess-perl 0.23-1
Bug #939460 [src:libmojolicious-perl, src:libmojo-ioloop-readwriteprocess-perl] 
libmojolicious-perl breaks libmojo-ioloop-readwriteprocess-perl autopkgtest: 
Invalid path at /usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 
30.
Bug reassigned from package 'src:libmojolicious-perl, 
src:libmojo-ioloop-readwriteprocess-perl' to 
'libmojo-ioloop-readwriteprocess-perl'.
No longer marked as found in versions libmojolicious-perl/8.23+dfsg-1 and 
libmojo-ioloop-readwriteprocess-perl/0.23-1.
Ignoring request to alter fixed versions of bug #939460 to the same values 
previously set
Bug #939460 [libmojo-ioloop-readwriteprocess-perl] libmojolicious-perl breaks 
libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at 
/usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.
Marked as found in versions libmojo-ioloop-readwriteprocess-perl/0.23-1.
> forwarded 939460 
> https://github.com/mudler/Mojo-IOLoop-ReadWriteProcess/issues/4
Bug #939460 [libmojo-ioloop-readwriteprocess-perl] libmojolicious-perl breaks 
libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at 
/usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.
Set Bug forwarded-to-address to 
'https://github.com/mudler/Mojo-IOLoop-ReadWriteProcess/issues/4'.
> thanks
Stopping processing here.

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

Bug#939648: git-buildpackage: FTBFS in unstable: flake8: E117 over-indented

[Guido Günther]

Hi,
On Sat, Sep 07, 2019 at 10:29:08AM +0100, Simon McVittie wrote:
> Package: git-buildpackage
> Version: 0.9.14
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> During test-builds to evaluate whether the new version of gtk-doc-tools is
> ready for upload to unstable, git-buildpackage failed to build. I can
> reproduce the build failure in a pure unstable sbuild environment:
> 
> >debian/rules override_dh_auto_test
> > make[1]: Entering directory '/<>'
> > make
> > make[2]: Entering directory '/<>'
> > flake8
> > ./gbp/patch_series.py:148:17: E117 over-indented
> > ./gbp/scripts/buildpackage.py:333:13: E117 over-indented
> > ./gbp/scripts/import_orig.py:82:17: E117 over-indented
> > ./gbp/scripts/common/import_orig.py:71:13: E117 over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/patch_series.py:148:17: E117 over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/buildpackage.py:333:13: E117 
> > over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/import_orig.py:82:17: E117 
> > over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/common/import_orig.py:71:13: E117 
> > over-indented
> > make[2]: *** [Makefile:20: syntax-check] Error 1

Fixed in git 78f8759a3d8e52e63aa3ec4dc2212989ae836494 since some time,
i'll roll that into a release.

> 
> Full build log attached.
> 
> I would recommend skipping stylistic/non-functional checks like this one,
> or making them only produce warnings, when "official" packages are built
> in a Debian environment (the style checks can still be fatal when run as
> part of `make check` during development, of course). Perhaps something
> like this:
> 
> # in debian/rules
> export IGNORE_STYLE_CHECKS = 1
> 
> # in the tests, replacing the flake8 invocation
> flake8 || [ -n "$IGNORE_STYLE_CHECKS" ]

I somewhat fear that they will slip then but i'll give it some
consideration.
thanks!
 -- Guido

> 
> Regards,
> smcv

Bug#939489: Cannot access secondary GPU - error: [XORG] (EE)

[wglxy]

more information:


After I install package xserver-xorg-input-mouse, I got another error message.


If I run optirun, the error message is:






$ optirun glxgears
[  502.952517] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)

[  502.952549] [ERROR]Aborting because fallback start is disabled.







if I run primusrun, the error message is:




$ primusrun glxgears
/usr/bin/primusrun: line 41: warning: command substitution: ignored null byte 
in input
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)










Best regards,
Gulfstream

Bug#939505: Cannot access secondary GPU - error: [XORG] (EE)

[wglxy]

more information:


After I install package xserver-xorg-input-mouse, I got another error message.


If I run optirun, the error message is:






$ optirun glxgears
[  502.952517] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)

[  502.952549] [ERROR]Aborting because fallback start is disabled.







if I run primusrun, the error message is:




$ primusrun glxgears
/usr/bin/primusrun: line 41: warning: command substitution: ignored null byte 
in input
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)










Best regards,
Gulfstream

Bug#939662: marked as done (sys/mman.h not found)

[Debian Bug Tracking System]

Your message dated Sat, 7 Sep 2019 17:44:37 +0200
with message-id <20190907174437.737dc...@heffalump.sk2.org>
and subject line Re: Bug#939662: sys/mman.h not found
has caused the Debian Bug report #939662,
regarding sys/mman.h not found
to be marked as done.

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

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


-- 
939662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mingw-w64
Version: 6.0.0-3
Severity: serious
Tags: a11y ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

  Firstly I export my host as "x86_64-w64-mingw32" and then install the 
gcc-mingw-w64,g++-mingw-w64 and some tolls to compile.
  Secondly, I clone the source of gperftools from github to compile the 
tcmalloc.
  But this error "sys/mman.h not found" occured when I run the command "make" 
after the commands "sh autogen.sh" and "./configure mingw-w64" finished.
  I really not found the mman.h in the directory of mingw64.
  I need your help.



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

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

Versions of packages mingw-w64 depends on:
ii  g++-mingw-w64  8.3.0-19+21.4
ii  gcc-mingw-w64  8.3.0-19+21.4

mingw-w64 recommends no packages.

mingw-w64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tag -a11y -ftbfs
Control: severity normal

Hi,

On Sat, 7 Sep 2019 13:02:08 +, Zhang Hao  wrote:
> Justification: fails to build from source (but built successfully in the
> past)

FTBFS means that the package you’re filing the bug against doesn’t build;
this isn’t the case here.

>   Firstly I export my host as "x86_64-w64-mingw32" and then install the
> gcc-mingw-w64,g++-mingw-w64 and some tolls to compile. Secondly, I clone
> the source of gperftools from github to compile the tcmalloc. But this
> error "sys/mman.h not found" occured when I run the command "make" after
> the commands "sh autogen.sh" and "./configure mingw-w64" finished. I really
> not found the mman.h in the directory of mingw64. I need your help.

Look at README_windows.txt in the gperftools repository: Windows is only
supported minimally, using Visual Studio. You can’t build gperftools using
MinGW-w64 out of the box.

In projects which do support MinGW-w64, you need to use

./configure --host=x86_64-w64-mingw32

to configure the build, not "./configure mingw-w64".

Regards,

Stephen


pgp_QJ0aZbt3E.pgp
Description: OpenPGP digital signature
--- End Message ---

Bug#939672: tmate: does not work at all; fails saying '[lost server]'

[Antonio Terceiro]

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

Bug#935678: marked as done (cmus FTBFS on armel, mipsel, m68k, powerpc, sh4: undefined reference to `__atomic_fetch_add_8')

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 15:28:58 +
with message-id 
and subject line Bug#935678: fixed in cmus 2.8.0-2
has caused the Debian Bug report #935678,
regarding cmus FTBFS on armel, mipsel, m68k, powerpc, sh4: undefined reference 
to `__atomic_fetch_add_8'
to be marked as done.

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

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


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

cmus fails to build from source on armel, mipsel, m68k, powerpc, sh4
with the same error. Final linking fails to find __atomic_fetch_add_8:

|gcc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  -o cmus ape.o browser.o 
buffer.o cache.o channelmap.o cmdline.o cmus.o command_mode.o comment.o 
convert.lo cue.o cue_utils.o debug.o discid.o editable.o expr.o filters.o 
format_print.o gbuf.o glob.o help.o history.o http.o id3.o input.o job.o keys.o 
keyval.o lib.o load_dir.o locking.o mergesort.o misc.o options.o output.o pcm.o 
player.o play_queue.o pl.o rbtree.o read_wrapper.o search_mode.o search.o 
server.o spawn.o tabexp_file.o tabexp.o track_info.o track.o tree.o uchar.o 
u_collate.o ui_curses.o window.o worker.o xstrjoin.o file.o path.o prog.o 
xmalloc.o -lpthread -lncursesw -ltinfo  -ldl -Wl,--export-dynamic -ldiscid -lm
| /usr/bin/ld: track_info.o: in function `track_info_new':
| ./track_info.c:47: undefined reference to `__atomic_fetch_add_8'
| collect2: error: ld returned 1 exit status
| make[2]: *** [Makefile:52: cmus] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_build: make -j4 V=2 returned exit code 2
| make[1]: *** [debian/rules:32: override_dh_auto_build] Error 255
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:21: build-arch] Error 2

Given that it previously built on armel and mipsel, this bug is severity
serious.

Helmut
--- End Message ---
--- Begin Message ---
Source: cmus
Source-Version: 2.8.0-2

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated cmus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Sep 2019 10:37:13 -0400
Source: cmus
Architecture: source
Version: 2.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Ryan Kavanagh 
Closes: 935678
Changes:
 cmus (2.8.0-2) unstable; urgency=medium
 .
   * Set build flags via /usr/share/dpkg/buildflags.mk
   * Link with -latomic to fix FTBFS on various architectures (Closes: #935678)
Checksums-Sha1:
 cefb990334804bac53000ba34e8019e254414f3c 3400 cmus_2.8.0-2.dsc
 d6e3fb94fad95a8aa325e6e1acd175ff8158b40a 9392 cmus_2.8.0-2.debian.tar.xz
 e9d7917dca0ff7ab05ad92bb041ded9b74c5972c 12894 cmus_2.8.0-2_amd64.buildinfo
Checksums-Sha256:
 63a8ede9abfbc954f6e95ef0d5c870494312bf501e05f94795453bd52689dbe0 3400 
cmus_2.8.0-2.dsc
 dd57a6da39a80655320fde19401809353fade0d7b87c992abaeff635c437 9392 
cmus_2.8.0-2.debian.tar.xz
 703c5751ff882409c0befa8bf9e8b1e3ecf985ea99b87cb78659e5af03335bd9 12894 
cmus_2.8.0-2_amd64.buildinfo
Files:
 d6eb58d124b4cd825f0b65e571af165b 3400 sound optional cmus_2.8.0-2.dsc
 d04c2adeed3744675b8845ee82917ee9 9392 sound optional cmus_2.8.0-2.debian.tar.xz
 c67e9ea5e546a5e4c325a4885cb0ca95 12894 sound optional 
cmus_2.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQVDBAEBCgAtFiEETkaVGe1ndzQmj72Vj3v4/EoRyXoFAl1zx6gPHHJha0BkZWJp
YW4ub3JnAAoJEI97+PxKEcl6UOUn/j60adgSUnmkDNwfoHSs/ESHwubvQRR/mdWk
RYY9LjdbDLudTP+jJis3gAqbZgzapXhNYmTKI3BpdlBjDezNIn+L1TC2W+Jex559
0DV9vzKcJWtqW0f5Uf+I2XnBvms5yb4eL3FYkSN3WI7ruYaO8FtCMi+YBewNzlaQ
jpaWvo6cC0qOCZe/Bts4Z/I3RRd1vRWPpXNRFhSRAP2WZQ4EMTh+Yqf21sNIhCoe
M5tByxBFYTCTTa3Ij8CyyqoXYy5+aKpP8JWG5R79Bf4rP+fW5oM1998lKlgl4esD
k1P7JkF7ZsGCIEKmqWDlh9BisdSjI/oPI0BGmrthAGyvWSqpDRFMMmka5HCCfSLv
17qt4ID4K5235LWhYc/4ZCjqr4PzpZT4DuR+5KwRuT/GGXE1M8wqSh0II+2l76EQ
p5h6NYI1aWB1Spw6HN2xOTNsxx70YGHtU0Ls+pyLfbpgwz7OjWqhd3MH9bbqf8mw

Bug#938962: user-mode-linux needs update for new linux

[Romain Francoise]

Hi,

On Tue, Sep 3, 2019 at 3:21 PM Ritesh Raj Sarraf  wrote:
[...]
> In file included from /usr/include/pcap.h:43,
>  from arch/um/drivers/pcap_user.c:7:
> /usr/include/pcap/pcap.h:835:18: note: previous declaration of ‘pcap_open’ 
> was here
>  PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int flags,
>   ^
> make[2]: *** [scripts/Makefile.build:309: arch/um/drivers/pcap_user.o] Error 1

libpcap 1.9 includes support for remote capture, which was originally
a part of WinPcap extensions. The `pcap_open()' symbol is part of that
API and that's why it's defined in the header file even though remote
support is not enabled in Debian. I suggest you rename the function
defined in your program so that it doesn't conflict with libpcap.

Bug#933741: marked as done (qemu: CVE-2019-14378: heap buffer overflow during packet reassembly)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 15:18:29 +
with message-id 
and subject line Bug#933741: fixed in qemu 1:3.1+dfsg-8+deb10u2
has caused the Debian Bug report #933741,
regarding qemu: CVE-2019-14378: heap buffer overflow during packet reassembly
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.)


-- 
933741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:3.1+dfsg-8
Severity: grave
Tags: security upstream
Control: clone -1 -2
Control: reassign -2 src:slirp4netns 0.3.1-1
Control: retitle -2 slirp4netns: CVE-2019-14459: heap buffer overflow during 
packet reassembly

Hi,

The following vulnerability was published for qemu (respective the
SLiRP networking implemenatation which is as well forked in
slirp4netns).

CVE-2019-14378[0]:
| ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer
| overflow via a large packet because it mishandles a case involving the
| first fragment.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14378
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14378
[1] 
https://gitlab.freedesktop.org/slirp/libslirp/commit/126c04acbabd7ad32c2b018fe10dfac2a3bc1210
[2] https://www.openwall.com/lists/oss-security/2019/08/01/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:3.1+dfsg-8+deb10u2

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu 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: Sat, 24 Aug 2019 15:56:15 +0300
Source: qemu
Architecture: source
Version: 1:3.1+dfsg-8+deb10u2
Distribution: buster-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 931351 933650 933741
Changes:
 qemu (1:3.1+dfsg-8+deb10u2) buster-security; urgency=medium
 .
   * 
slirp-fix-heap-overflow-in-ip_reass-on-big-packet-input-CVE-2019-14378.patch
 Closes: #933741, CVE-2019-14378 (slirp heap buffer overflow)
   * qemu-bridge-helper-restrict-interface-name-to-IFNAMSIZ-CVE-2019-13164.patch
 Closes: #931351, CVE-2019-13164 (qemu-bridge-helper ifname overflow)
   * linux-user-sanitize-interp_info-for-mips-only.patch
 Closes: #933650 (some mips binaries fails to start)
Checksums-Sha1:
 fbe9b5e9a4966a2ca5979fecada49767742669f2 6152 qemu_3.1+dfsg-8+deb10u2.dsc
 b6a6c31d146b13e14af253d6dc25f16ccad7d060 8705368 qemu_3.1+dfsg.orig.tar.xz
 57f529797a1185d68ac567f71166293629594206 89496 
qemu_3.1+dfsg-8+deb10u2.debian.tar.xz
 9043e32a8ef8eae21e9a02f5b5ee59f98a3b8c7f 8322 
qemu_3.1+dfsg-8+deb10u2_source.buildinfo
Checksums-Sha256:
 942a73dd54ab72e3fc2d1681e59f66c4a7e711c1cdad2cf84eb308fa25f59951 6152 
qemu_3.1+dfsg-8+deb10u2.dsc
 2f277942759dd3eed21f7e00edfeab52b4f58d6f2f22d4f7e1a8aa4dc54c80d7 8705368 
qemu_3.1+dfsg.orig.tar.xz
 fcca1716c9ddf58e6e06d48e3ae809ce23877de327591851946802e87b8b7329 89496 
qemu_3.1+dfsg-8+deb10u2.debian.tar.xz
 c5db2c6b674838341556cb61cae759806d4e53fe05625e5d7eec14543ba7473f 8322 
qemu_3.1+dfsg-8+deb10u2_source.buildinfo
Files:
 4a4f7905815c2cfaaf671270fcb16c04 6152 otherosfs optional 
qemu_3.1+dfsg-8+deb10u2.dsc
 b17f33786c89d547150490811a40f0b2 8705368 otherosfs optional 
qemu_3.1+dfsg.orig.tar.xz
 6e88bd2ae2c065643b7a21813191b257 89496 otherosfs optional 
qemu_3.1+dfsg-8+deb10u2.debian.tar.xz
 f55706a97a0bed42552d53a4dc50a487 8322 otherosfs optional 
qemu_3.1+dfsg-8+deb10u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl1rt/sPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZXnUH/1PtvMR9VeH5GPGIKC9mShvkfoqGP/Y+R1BZ
t7rU4GiAgECHCllZ1/wWqfRLtUUWWHpQ3H3PBIN9DjWO3pBI4rcuIpGXWs9fsFcr
yaXa0WZRdDKwX2zYpKB1F9a5JjehEdkHgPAYquPwHqKsbFY6SY9eancy8pqaoQE+

Bug#935678: marked as pending in cmus

[Ryan Kavanagh]

Control: tag -1 pending

Hello,

Bug #935678 in cmus 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/multimedia-team/cmus/commit/79e098e5899c815587000870b79b63386f0c


Add -latomic build flag to fix FTBFS on various architectures (Closes: #935678)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935678

Processed: Bug#935678 marked as pending in cmus

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935678 [src:cmus] cmus FTBFS on armel, mipsel, m68k, powerpc, sh4: 
undefined reference to `__atomic_fetch_add_8'
Ignoring request to alter tags of bug #935678 to the same tags previously set

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

Bug#939670: gdcm-doc: depends on cruft package.

[peter green]

Package: gdcm-doc
Version: 2.8.8-9
Severity: serious
Tags: bullseye, sid

gdcm-doc depends on vtk6-doc which is no longer built by the vtk6 source 
package.

Processed: limit source to cmus, tagging 935678

[Debian Bug Tracking System]

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

> limit source cmus
Limiting to bugs with field 'source' containing at least one of 'cmus'
Limit currently set to 'source':'cmus'

> tags 935678 + pending
Bug #935678 [src:cmus] cmus FTBFS on armel, mipsel, m68k, powerpc, sh4: 
undefined reference to `__atomic_fetch_add_8'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#935346: work in progress upstream?

[David Bremner]

It looks like the pyqt5 branch discussed in 

   https://github.com/keithgg/puddletag/issues/418

has been merged to master, but I didn't manage to make it work with
PyQt5. It looks like the source still hardcodes pyqt5, so I don't know
what's going on there.

d

Bug#939401: nvidia-driver: Xorg crashing in an endless loop after upgrade to version 430

[Luca Boccassi]

On Wed, 4 Sep 2019 17:20:06 +0200 Andreas Beckmann <
a...@debian.org
> wrote:
> On 04/09/2019 17.15, Niklas Schmidt wrote:
> >   I tried rebooting with an older kernel to reinstall the
driver, which did not work. I also tried unplugging my second monitor
and deleting the xorg.conf file. This didn't help either. I have
resorted to using the legacy 390 driver for now.
> 
> Could you try 435.xx from experimental?
> 
> Andreas

Unfortunately I cannot reproduce this on my buster desktop (780gtx).

-- 
Kind regards,
Luca Boccassi


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

Processed: reassign 939643 939489

[Debian Bug Tracking System]

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

> reassign 939643 nvidia-driver 430.40-2
Bug #939643 [bumblebee] [bumblebee] does not work with nvidia drivers 430.40-2
Bug reassigned from package 'bumblebee' to 'nvidia-driver'.
No longer marked as found in versions bumblebee/3.2.1-20.
Ignoring request to alter fixed versions of bug #939643 to the same values 
previously set
Bug #939643 [nvidia-driver] [bumblebee] does not work with nvidia drivers 
430.40-2
Marked as found in versions nvidia-graphics-drivers/430.40-2.
> reassign 939489 nvidia-driver 430.40-2
Bug #939489 [bumblebee-nvidia] bumblebee fails to disable discrete graphics 
card after upgrade nvidia driver to 430.40-2
Bug reassigned from package 'bumblebee-nvidia' to 'nvidia-driver'.
No longer marked as found in versions bumblebee/3.2.1-20.
Ignoring request to alter fixed versions of bug #939489 to the same values 
previously set
Bug #939489 [nvidia-driver] bumblebee fails to disable discrete graphics card 
after upgrade nvidia driver to 430.40-2
Marked as found in versions nvidia-graphics-drivers/430.40-2.
> forcemerge 939401 939489 939643
Bug #939401 [nvidia-driver] nvidia-driver: Xorg crashing in an endless loop 
after upgrade to version 430
Bug #939643 [nvidia-driver] [bumblebee] does not work with nvidia drivers 
430.40-2
Severity set to 'grave' from 'normal'
Added tag(s) bullseye and sid.
Bug #939401 [nvidia-driver] nvidia-driver: Xorg crashing in an endless loop 
after upgrade to version 430
Added tag(s) bullseye and sid.
Bug #939489 [nvidia-driver] bumblebee fails to disable discrete graphics card 
after upgrade nvidia driver to 430.40-2
Merged 939401 939489 939643
>
End of message, stopping processing here.

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

Bug#939663: freefem++: B-D on cruft packages

[Esa Peuha]

Source: freefem++
Version: 3.61.1+dfsg1-4
Severity: serious

Currently freefem++ build-depends on libpetsc-real3.10-dev and
libpetsc-complex3.10-dev which are no longer built from source.
Please update these build-dependencies.

Bug#939662: sys/mman.h not found

[Zhang Hao]

Package: mingw-w64
Version: 6.0.0-3
Severity: serious
Tags: a11y ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

  Firstly I export my host as "x86_64-w64-mingw32" and then install the 
gcc-mingw-w64,g++-mingw-w64 and some tolls to compile.
  Secondly, I clone the source of gperftools from github to compile the 
tcmalloc.
  But this error "sys/mman.h not found" occured when I run the command "make" 
after the commands "sh autogen.sh" and "./configure mingw-w64" finished.
  I really not found the mman.h in the directory of mingw64.
  I need your help.



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

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

Versions of packages mingw-w64 depends on:
ii  g++-mingw-w64  8.3.0-19+21.4
ii  gcc-mingw-w64  8.3.0-19+21.4

mingw-w64 recommends no packages.

mingw-w64 suggests no packages.

-- no debconf information

Bug#934484: marked as done (python-pytest-asyncio: "Cannot import name 'transfer_markers'" with current pytest)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 12:44:58 +
with message-id 
and subject line Bug#934484: fixed in python-pytest-asyncio 0.10.0-1
has caused the Debian Bug report #934484,
regarding python-pytest-asyncio: "Cannot import name 'transfer_markers'" with 
current pytest
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.)


-- 
934484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-asyncio
Version: 0.9.0-1
Severity: serious
Tags: upstream

Dear Maintainer,

Since the recent upgrade of pytest, tests involving pytest-asyncio[1]
are failing with:

ImportError: cannot import name 'transfer_markers' from
'_pytest.python' (/usr/lib/python3/dist-packages/_pytest/python.py)

A quick search suggests the problem is a compatibility issue with
pytest-asyncio[2], which
has been resolved upstream[3].

The package needs to be upgraded to 0.10.0.

[1] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/a/aiofiles/2707314/log.gz
[2] https://github.com/pytest-dev/pytest-asyncio/issues/104
[3] https://github.com/pytest-dev/pytest-asyncio/pull/105


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

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

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE
--- End Message ---
--- Begin Message ---
Source: python-pytest-asyncio
Source-Version: 0.10.0-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated python-pytest-asyncio 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Sep 2019 12:39:12 +0200
Source: python-pytest-asyncio
Architecture: source
Version: 0.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team 
Changed-By: Jonas Smedegaard 
Closes: 934484
Changes:
 python-pytest-asyncio (0.10.0-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 + Pytest 4.1 support.
   Closes: Bug#934484. Thanks to David Steele.
 .
   [ Jonas Smedegaard ]
   * Declare compliance with Debian Policy 4.4.0.
   * Set Rules-Requires-Root: no.
   * Update watch file:
 + Simplify regular expressions.
 + Rewrite usage comment.
Checksums-Sha1:
 8a66a5dd5b73661e8fdf3981e24d560830c8449d 2094 
python-pytest-asyncio_0.10.0-1.dsc
 c9567b9e1de7efb1da884110bbf0cce404b58492 13968 
python-pytest-asyncio_0.10.0.orig.tar.gz
 d1b03a6be3144a2acb671f3ef1e9c0b0528f605f 2856 
python-pytest-asyncio_0.10.0-1.debian.tar.xz
 449f57f46de2c7b8ee7c71eb491385857efe00f2 5992 
python-pytest-asyncio_0.10.0-1_amd64.buildinfo
Checksums-Sha256:
 3e36f3a1aec8be8e9f43b145076e35c5907124db0eb7424ad5249ffea7b185e0 2094 
python-pytest-asyncio_0.10.0-1.dsc
 4a2f53fb40b8075739018e026bd0d3d2485d9f7c228974c817a6b43ed1350ed0 13968 
python-pytest-asyncio_0.10.0.orig.tar.gz
 d36c6bd9f7ec15b32753d1f189c215cb5f9d846faa3069aa22c60f3894d4c938 2856 
python-pytest-asyncio_0.10.0-1.debian.tar.xz
 d648f37829c0c46b74d5d3df4d05281953d46ed7c1e14141c58dd44b0c3b89ad 5992 
python-pytest-asyncio_0.10.0-1_amd64.buildinfo
Files:
 d6af2ad6ea808de06e41f57392f88f76 2094 python optional 
python-pytest-asyncio_0.10.0-1.dsc
 09683fc1fa2a49f180f6a8c02776f7dd 13968 python optional 
python-pytest-asyncio_0.10.0.orig.tar.gz
 1fc5d8700d5433650e0a9b9c121e1a7a 2856 python optional 
python-pytest-asyncio_0.10.0-1.debian.tar.xz
 e2a53703ec2fd0ffd8eb52adfff151bb 5992 python optional 
python-pytest-asyncio_0.10.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl1ziV0ACgkQLHwxRsGg
ASHOFQ//XjYpk4S4vP7cJ6LEd7k8MQqQTXti5U8mloe2Leybl0/Y83lmNLpfVNnz

Bug#938982: marked as done (xcffib: internet connection during build)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 12:47:27 +
with message-id 
and subject line Bug#938982: fixed in xcffib 0.8.1-0.4
has caused the Debian Bug report #938982,
regarding xcffib: internet connection during build
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.)


-- 
938982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xcffib
Version: 0.8.1-0.3
Severity: serious

hello, looks like the package is attempting internet connection during build 
(you can see e.g. on Ubuntu builds)

see build log:
make xcffib
make[2]: Entering directory '/<>'
cabal --config-file=./cabal.config new-run exe:xcffibgen -- --input 
/usr/share/xcb --output ./xcffib
Warning: Unknown/unsupported 'ghc' version detected (Cabal 2.2.0.1 supports
'ghc' version < 8.5): /usr/bin/ghc is version 8.6.5
Warning: Caught exception during _mirrors lookup:user error (res_query(3)
failed)
Warning: No mirrors found for http://hackage.haskell.org/
dieVerbatim: user error (cabal: Couldn't establish HTTP connection. Possible 
cause: HTTP proxy server
is down.
)
make[2]: *** [Makefile:16: xcffib] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


cheers,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: xcffib
Source-Version: 0.8.1-0.4

We believe that the bug you reported is fixed in the latest version of
xcffib, 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.
Gianfranco Costamagna  (supplier of updated xcffib 
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: Sat, 07 Sep 2019 08:59:04 +0200
Source: xcffib
Binary: python-xcffib python3-xcffib
Architecture: source
Version: 0.8.1-0.4
Distribution: unstable
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Gianfranco Costamagna 
Description:
 python-xcffib - This package is a Python binding for XCB (Python 2)
 python3-xcffib - This package is a Python binding for XCB (Python 3)
Closes: 938982
Changes:
 xcffib (0.8.1-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Avoid internet connection by patching cabal to not use a configuration
 file (Closes: #938982)
   * Disable tests for now, they might hang
Checksums-Sha1:
 6d03ccb75c671cc55648fe62659d1ca8cc878e7a 2466 xcffib_0.8.1-0.4.dsc
 46fd9dcaef877ba1a0843b46777ab807a378e1d7 4104 xcffib_0.8.1-0.4.debian.tar.xz
 a102d949ae49d1877f6a697b3311964f4f875843 13464 
xcffib_0.8.1-0.4_source.buildinfo
Checksums-Sha256:
 47f5f1cf15dabc76d55e4011cbeb48b3d8a18bbed177b2198d56ce4871e7b8e0 2466 
xcffib_0.8.1-0.4.dsc
 f47765db6bd36fe9f5d6d06c96bab33b9bde49ce0ac13f0933dc74cc588dbbd3 4104 
xcffib_0.8.1-0.4.debian.tar.xz
 7935011bc8d4b5ae941b51f5f82417c9f03b8ff32a42ccbabd84fcfab7542aa0 13464 
xcffib_0.8.1-0.4_source.buildinfo
Files:
 a495c553d5a13d3044c5e39c0d2a5655 2466 python optional xcffib_0.8.1-0.4.dsc
 4614f4e998ecec12e6d5a5805bf97381 4104 python optional 
xcffib_0.8.1-0.4.debian.tar.xz
 a3f2f5067a1939e8b3fcaaa63d05e3c1 13464 python optional 
xcffib_0.8.1-0.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl1zVtIACgkQ808JdE6f
Xdm7vA//SQaulhUjeM2lZeMO5jY0y41uT9A8iuYH5V7lAwbNd6PP7emVr583kPUr
lyR0rZ/MmVqiuDwHXzezb3rOtui6OIsH/kcwr0uCFB1Cuti/O1pARFA3hdBI8a6I
mJ06k8ZyO7ZEngf+coFbDtPh2FYlCSShCAsEDoS0XSVK5cl1gtlG0LcWeA3a90Ev
+xMcVmhWBGyrAYBKjNp48kt1NjXrMl9dmVJ5uYRWZ3tGpB8fBQ/n0x6/nUuWBNx2
chE1bdO2iNtoBCP0Ya9EnTa9Uq/FXqCTigO1C+mwbAukutf1bYch2Vjh5ZShZqUG
xcKOKgP1ILy7xLnTyig0GMeFqKIHUBhEiio/SyukhZ46c2Zb23U1CHj6/6UFyvHD
6JhsH+HB7+epAlv4VEJEZNgaa8zWPY+nOfgakLoK4RMVKtiTEyIgPZoXKqaTOpyP
qwCJrL7xkEriWmIMhs4c8vbtYImiTitSq0v4aUidZxzUDwqVNR/v3Yetc6uJ3Red
3Z/ABCw1jmoc3ac6dm+NprpnHFTVeaxeKQGwVym4VNQLkJ73MKy6i+6BNyRZ48yQ
WD5wH3slMr8Mvgq6LwQoFTyCOCuoj8yB71xd0Tj+aTAaWZQcCnS2Aq0fC/4sM30w
VN9iF0rqMYi6K2nT9Bu3vk5azi7hkLcGisR9q4Txmnkvu0EpIzo=
=RLwU
-END PGP 

Bug#912042: marked as done (electrum.png file moved from py-electrum to electrum without proper Breaks/Replaces)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 12:35:32 +
with message-id 
and subject line Bug#912042: fixed in electrum 3.3.8-0.1
has caused the Debian Bug report #912042,
regarding electrum.png file moved from py-electrum to electrum without proper 
Breaks/Replaces
to be marked as done.

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

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


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

Hi,

It seems that /usr/share/pixmaps/electrum.png has moved from
python3-electrum to electrum package without the proper Breaks/Replaces.

This caused the file to be completely absent from my system (not exactly
sure why TBH)

You should add Breaks/Replaces: python3-electrum (<< 3.2.3-1~) I guess

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages electrum depends on:
ii  python3   3.6.7-1
ii  python3-electrum  3.2.3-1

Versions of packages electrum recommends:
ii  python3-pyqt5  5.11.3+dfsg-1+b1

Versions of packages electrum suggests:
pn  python3-btchip  
pn  python3-trezor  
pn  python3-zbar

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: electrum
Source-Version: 3.3.8-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated electrum 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: Sat, 07 Sep 2019 10:34:31 +0200
Source: electrum
Architecture: source
Version: 3.3.8-0.1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Laurent Bigonville 
Closes: 912042 913760 921688
Changes:
 electrum (3.3.8-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Fix critical vulnerability allowing certain malicious servers to display
   fishing messages to the user (Closes: #921688)
 - debian/control: Update the build-dependencies
   * debian/rules: Stop calling pyrcc5, this is not needed anymore
   * Do not move files in debian/rules but use debian/*.install files
   * debian/control: Add proper Breaks/Replaces for electrum.png being moved
 between packages (Closes: #912042)
   * debian/control: revealer plugin seems to explicitly use "DejaVu Sans Mono"
 font, recommend fonts-dejavu-core accordingly. Do not delete
 SourceSansPro-Bold.otf font anymore as it's also explicitly used, but not
 part of any public font package
   * debian/control: Bump Standards-Version to 4.4.0 (no further changes)
   * debian/control: Add libsecp256k1-0 to the Recommends, it is used to speed
 up elliptic curve operations (Closes: #913760)
Checksums-Sha1:
 30ab85cf823ec41c691a2af9f1b487095ac40081 2125 electrum_3.3.8-0.1.dsc
 c95621c6b39618ed7c1edcc462c4bae2731903f2 8973635 electrum_3.3.8.orig.tar.gz
 64559f7ac5c56d0dd21461d6a35b80aa24601778 833 electrum_3.3.8.orig.tar.gz.asc
 11c52a2d6442994a8e9e8094d9272da53d0c8df4 15696 electrum_3.3.8-0.1.debian.tar.xz
 dda51da773226074fdd5146a16da8cbd0f2e4f06 14324 
electrum_3.3.8-0.1_source.buildinfo
Checksums-Sha256:
 997dd541ccaaa0ebb0824515fbc6adc84158dba05ad0ee085e0b29881b751afc 2125 
electrum_3.3.8-0.1.dsc
 af9206f397fb5f5e8d3f6e3a9f8b0db1389e1d147c88a6feba73c83f87ae1b0a 8973635 
electrum_3.3.8.orig.tar.gz
 b9499cd93b4c1d17e34da88d200ab21cf76a987a5820345c3604864ce88fbe3b 833 
electrum_3.3.8.orig.tar.gz.asc
 44854b78684e4ba21b8fb703e81f548a9498a074b950c0af9f0e127eb293b771 

Bug#921688: marked as done (Electrum vulnerable to malware)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 12:35:32 +
with message-id 
and subject line Bug#921688: fixed in electrum 3.3.8-0.1
has caused the Debian Bug report #921688,
regarding Electrum vulnerable to malware
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.)


-- 
921688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: electrum
Version: 3.1.3-1~bpo9+1

When electrum connects to certain malicious servers they issue a warning
message telling the user to upgrade by following a phishing link. The
link prompts the user to enter their credentials and install malware
which results in the loss of all their funds. A new version of electrum
has been realeased to address these problems.

The issue is being discussed here:
https://github.com/spesmilo/electrum/issues/4968 complete with
screenshots of the phishing messages.

Given the severity and urgency of this exploit, the appropriate new
version should be added to the official Debian repos ASAP to avoid
further attacks on users.

I am using Debian GNU/Linux 9 (stretch) 64-bit
Kernel 4.9.0-8-amd64
--- End Message ---
--- Begin Message ---
Source: electrum
Source-Version: 3.3.8-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated electrum 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: Sat, 07 Sep 2019 10:34:31 +0200
Source: electrum
Architecture: source
Version: 3.3.8-0.1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Laurent Bigonville 
Closes: 912042 913760 921688
Changes:
 electrum (3.3.8-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Fix critical vulnerability allowing certain malicious servers to display
   fishing messages to the user (Closes: #921688)
 - debian/control: Update the build-dependencies
   * debian/rules: Stop calling pyrcc5, this is not needed anymore
   * Do not move files in debian/rules but use debian/*.install files
   * debian/control: Add proper Breaks/Replaces for electrum.png being moved
 between packages (Closes: #912042)
   * debian/control: revealer plugin seems to explicitly use "DejaVu Sans Mono"
 font, recommend fonts-dejavu-core accordingly. Do not delete
 SourceSansPro-Bold.otf font anymore as it's also explicitly used, but not
 part of any public font package
   * debian/control: Bump Standards-Version to 4.4.0 (no further changes)
   * debian/control: Add libsecp256k1-0 to the Recommends, it is used to speed
 up elliptic curve operations (Closes: #913760)
Checksums-Sha1:
 30ab85cf823ec41c691a2af9f1b487095ac40081 2125 electrum_3.3.8-0.1.dsc
 c95621c6b39618ed7c1edcc462c4bae2731903f2 8973635 electrum_3.3.8.orig.tar.gz
 64559f7ac5c56d0dd21461d6a35b80aa24601778 833 electrum_3.3.8.orig.tar.gz.asc
 11c52a2d6442994a8e9e8094d9272da53d0c8df4 15696 electrum_3.3.8-0.1.debian.tar.xz
 dda51da773226074fdd5146a16da8cbd0f2e4f06 14324 
electrum_3.3.8-0.1_source.buildinfo
Checksums-Sha256:
 997dd541ccaaa0ebb0824515fbc6adc84158dba05ad0ee085e0b29881b751afc 2125 
electrum_3.3.8-0.1.dsc
 af9206f397fb5f5e8d3f6e3a9f8b0db1389e1d147c88a6feba73c83f87ae1b0a 8973635 
electrum_3.3.8.orig.tar.gz
 b9499cd93b4c1d17e34da88d200ab21cf76a987a5820345c3604864ce88fbe3b 833 
electrum_3.3.8.orig.tar.gz.asc
 44854b78684e4ba21b8fb703e81f548a9498a074b950c0af9f0e127eb293b771 15696 
electrum_3.3.8-0.1.debian.tar.xz
 18828ad1ba668b43577132410645015ca541571289557e5a914d59aee2d640af 14324 
electrum_3.3.8-0.1_source.buildinfo
Files:
 3d4b1cf9bc0e787d6ef42950bf5d6078 2125 utils optional electrum_3.3.8-0.1.dsc
 a49a76d019afa88a683932642b53aa63 8973635 utils optional 
electrum_3.3.8.orig.tar.gz
 c4937b121ac5b72cfc0907b3812e54fc 833 utils optional 
electrum_3.3.8.orig.tar.gz.asc
 c38df56060beb6378d2af4535e611ee8 15696 utils optional 
electrum_3.3.8-0.1.debian.tar.xz
 371322010beb2ae15afce7bf6ea4ecb5 14324 utils optional 

Bug#923595: marked as done (electrum: Electrum branch containing critical vulnerability should be updated)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 12:35:32 +
with message-id 
and subject line Bug#921688: fixed in electrum 3.3.8-0.1
has caused the Debian Bug report #921688,
regarding electrum: Electrum branch containing critical vulnerability should be 
updated
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.)


-- 
921688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: electrum
Version: 3.1.3-1~bpo9+1
Severity: important

Dear Maintainer,

Having the fact that all versions of Electrum older than 3.3.3 are vulnerable 
to a phishing attack (https://github.com/spesmilo/electrum/issues/4968 also 
warning on http://electrum.org), where malicious servers ask users to download 
bitcoin-stealing malware, why are we still on 3.1.3 branch on Debian Stable?

I think Electrum packages on all Debian versions should be updated urgently. 
It's almost impossible to use this software, because every time we try to make 
a transaction, a phinshing server asks us to download a fresh version of 
electrum from a fake domain.

Please consider moving to 3.3.4 on Debian Stable and Sid, since it's not a 
software that requires compilation, it shouldn't be a big mess to upgrade.

-- System Information:
Debian Release: 9.8
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'trusty-security'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

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

Versions of packages electrum depends on:
ii  python3   3.5.3-1
ii  python3-electrum  3.1.3-1~bpo9+1

Versions of packages electrum recommends:
ii  python3-pyqt5  5.7+dfsg-5

Versions of packages electrum suggests:
pn  python3-btchip  
pn  python3-trezor  
pn  python3-zbar

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: electrum
Source-Version: 3.3.8-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated electrum 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: Sat, 07 Sep 2019 10:34:31 +0200
Source: electrum
Architecture: source
Version: 3.3.8-0.1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Laurent Bigonville 
Closes: 912042 913760 921688
Changes:
 electrum (3.3.8-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Fix critical vulnerability allowing certain malicious servers to display
   fishing messages to the user (Closes: #921688)
 - debian/control: Update the build-dependencies
   * debian/rules: Stop calling pyrcc5, this is not needed anymore
   * Do not move files in debian/rules but use debian/*.install files
   * debian/control: Add proper Breaks/Replaces for electrum.png being moved
 between packages (Closes: #912042)
   * debian/control: revealer plugin seems to explicitly use "DejaVu Sans Mono"
 font, recommend fonts-dejavu-core accordingly. Do not delete
 SourceSansPro-Bold.otf font anymore as it's also explicitly used, but not
 part of any public font package
   * debian/control: Bump Standards-Version to 4.4.0 (no further changes)
   * debian/control: Add libsecp256k1-0 to the Recommends, it is used to speed
 up elliptic curve operations (Closes: #913760)
Checksums-Sha1:
 30ab85cf823ec41c691a2af9f1b487095ac40081 2125 electrum_3.3.8-0.1.dsc
 c95621c6b39618ed7c1edcc462c4bae2731903f2 8973635 electrum_3.3.8.orig.tar.gz
 64559f7ac5c56d0dd21461d6a35b80aa24601778 833 electrum_3.3.8.orig.tar.gz.asc
 11c52a2d6442994a8e9e8094d9272da53d0c8df4 15696 electrum_3.3.8-0.1.debian.tar.xz
 dda51da773226074fdd5146a16da8cbd0f2e4f06 14324 
electrum_3.3.8-0.1_source.buildinfo
Checksums-Sha256:
 997dd541ccaaa0ebb0824515fbc6adc84158dba05ad0ee085e0b29881b751afc 2125 

Processed: block 917972 with 939660

[Debian Bug Tracking System]

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

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

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

Bug#939659: golang-github-paypal-gatt: Incomplete debian/copyright?

[Chris Lamb]

Source: golang-github-paypal-gatt
Version: 0.0~git20151011.4ae819d-1
Severity: serious
Justication: Policy ยง12.5
X-Debbugs-CC: Thorsten Alteholz , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-paypal-gatt from NEW but noticed it was 
missing attribution in debian/copyright for at least linux/socket/*.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#925763: libusrsctp: ftbfs with GCC-9

[Jonas Smedegaard]

control: severity -1 important

Quoting Matthias Klose (2019-03-27 20:46:45)
> The package fails to build in a test rebuild on at least amd64 with
> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8.

[...]

> netinet/sctp_input.c:3879:64: error: taking address of packed member of 
> 'struct sctp_stream_reset_out_request' may result in an unaligned pointer 
> value [-Werror=address-of-packed-member]
>  3879 |  sctp_reset_out_streams(stcb, number_entries, 
> req_out_param->list_of_streams);
>   |   
> ~^

Temporarily setting -Wno-address-of-packed-member to suppress this.

Apparently the code works fine, and in the past upstream suppressed this 
type of warnings by default, dropping it only when older compilers 
failed to parse that build flag (by fixing the code issue at the time).

Lowering (but not closing) this bug as reminder to have this issue fixed 
properly.


 - Jonas

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

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


signature.asc
Description: signature

Processed: Re: Bug#925763: libusrsctp: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #925763 [src:libusrsctp] libusrsctp: ftbfs with GCC-9
Severity set to 'important' from 'serious'

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

Bug#939660: src:field3d: autopkgtest fails if package is rebuilt against ilmbase 2.3.0

[Matteo F. Vescovi]

Package: src:field3d
Version: 1.7.2-1
Severity: serious

Dear Maintainer,

while testing all reverse dependencies for the IlmBase transition[1],
your package was FTBFS due to inconsistent linking while running
autopkgtest checks.

Because of it, the package was actually removed from testing suite to
allow the migration of ilmbase library[2].

Digging a little more in the problem, it seems like libfield3d needs to
bump SONAME because its ABI is tied to ilmbase's.

Please, spend some efforts fixing this issue.


[1] https://bugs.debian.org/917972
[2] https://tracker.debian.org/news/1062407/field3d-removed-from-testing/

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: 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


signature.asc
Description: PGP signature

Bug#939658: printrun: Incomplete debian/copyright?

[Chris Lamb]

Source: printrun
Version: 2.0.0~rc5-1
Severity: serious
Justication: Policy ยง12.5
X-Debbugs-CC: Rock Storm , Thorsten Alteholz 
, Sean Whitton , 
ftpmas...@debian.org

Hi,

I just ACCEPTed printrun from NEW but noticed it was missing 
attribution in debian/copyright for at least *.appdata.xml and
printrun/gcoder.py, printrun/gcoder_line.pyx. (What is your list of
copyright holders based on, i.e., how did you find those names?)
Also, do we have source for PCB-milling-and-(comment).gcode? It
seems to be a generated file.

Please resolve the questions in your debian/copyright file for
posterity and not on this bug report.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#939630: [DRE-maint] Bug#939630: schleuder: breaks testbed?

[Georg Faerber]

control: tags -1 confirmed pending

Hi Gianfranco,

Thanks for your report.

On 19-09-07 08:16:22, Gianfranco Costamagna wrote:
> looks like you are playing with /dev/random removing and symlinking it
> again.
> 
> This might break the test environment, so I would say we should
> 
> 1) declare the test as breaks-testbed [1]
> 
> or
> 
> 2) stop doing that.
> 
> I tried to remove that if statement in Ubuntu, and the testsuite ran
> successfully everywhere, including armhf.
> 
> I discovered that issue, because in armhf the rm was failing because
> of "dev/random" busy issues.
> 
> you can see my "ubuntu3" upload, and the various test results if you
> want more information
> http://autopkgtest.ubuntu.com/packages/s/schleuder/eoan/armhf

Agreed -- I've just uploaded 3.4.0-4 which drops this workaround. Lets
see how this goes, I'll update this bug soonish once there are some
tests made.

Cheers,
Georg

Processed: Re: [DRE-maint] Bug#939630: schleuder: breaks testbed?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed pending
Bug #939630 [src:schleuder] schleuder: breaks testbed?
Added tag(s) confirmed and pending.

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

Bug#939654: libjpeg FTBFS inside sbuild

[Helmut Grohne]

Source: libjpeg
Version: 0.0~git20180720.99764820d250-1
Severity: serious
Tags: ftbfs

libjpeg fails to build from source in unstable when building it under
sbuild, because sbuild does not have a writeable $HOME directory:

|dh_auto_install
| make -j1 install 
DESTDIR=/<>/libjpeg-0.0\~git20180720.99764820d250/debian/libjpeg-tools
 AM_UPDATE_INFO_DIR=no
| make[1]: Entering directory '/<>'
| mkdir: cannot create directory ‘/sbuild-nonexistent’: Permission denied
| make[1]: *** [Makefile:383: install] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_install: make -j1 install 
DESTDIR=/<>/libjpeg-0.0\~git20180720.99764820d250/debian/libjpeg-tools
 AM_UPDATE_INFO_DIR=no returned exit code 2
| make: *** [debian/rules:5: binary] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Since our buildd network uses sbuild, this bug is serious.

Helmut

Processed: found 939651 in 1.0.0-1

[Debian Bug Tracking System]

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

> found 939651 1.0.0-1
Bug #939651 [meteo-qt] meteo-qt/buster crashes immediately because of changed 
openweathermap data structure
Ignoring request to alter found versions of bug #939651 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfound 939651 in 1.3-1

[Debian Bug Tracking System]

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

> notfound 939651 1.3-1
Bug #939651 [meteo-qt] meteo-qt/buster crashes immediately because of changed 
openweathermap data structure
Ignoring request to alter found versions of bug #939651 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#885881: mp3burn: does not work at all, produces blank CD ROMs

[Christoph Berg]

Control: severity -1 normal

Re: Stephen McGregor 2017-12-30 
<151466741537.8388.3618147145422386560.reportbug@localhost>
> Ran 
> 
>  mp3burn --check ATIP -o "dev=/dev/sr0 speed=10 "  -M lame  *mp3 
> 
> in  a directory of mp3 files.
> 
> A CD of blank tracks was produced. 

The package still works for me, "mp3burn *.mp3". I didn't check if the
above options break it, but the default configuration is usable, so
I'm downgrading this bug to "normal".

Christoph

Processed: Re: Bug#885881: mp3burn: does not work at all, produces blank CD ROMs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #885881 [mp3burn] mp3burn: does not work at all, produces blank CD ROMs
Severity set to 'normal' from 'grave'

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

Bug#939651: meteo-qt/buster crashes immediately because of changed openweathermap data structure

[Alf Gaida]

Package: meteo-qt
Version: 1.0.0-1
Severity: grave
Tags: patch

Hi,

there are a few possible ways to solve this:
* new version in buster
* a wholesale patch (just tested, apply fine, build and run fine)
* a stripped down patch who leaves typos and such things out

Tbh i would prefer the wholesale patch without changing the version. meteo-qt
is a typical leave package - nothing depend on it, so a wholesale patch
should not introduce any problem for other packages - and fixes some 
crashes beside only changing the read of the new data structure.

Cheers Alf 

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

Kernel: Linux 5.2.11-towo.2-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages meteo-qt depends on:
ii  python33.7.3-1
ii  python3-lxml   4.4.1-1
ii  python3-pyqt5  5.12.3+dfsg-2
ii  python3-sip4.19.18+dfsg-1

Versions of packages meteo-qt recommends:
ii  meteo-qt-l10n  1.0.0-1

meteo-qt suggests no packages.

-- debconf-show failed

Bug#939648: git-buildpackage: FTBFS in unstable: flake8: E117 over-indented

[Simon McVittie]

Package: git-buildpackage
Version: 0.9.14
Severity: serious
Tags: ftbfs
Justification: fails to build from source

During test-builds to evaluate whether the new version of gtk-doc-tools is
ready for upload to unstable, git-buildpackage failed to build. I can
reproduce the build failure in a pure unstable sbuild environment:

>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> make
> make[2]: Entering directory '/<>'
> flake8
> ./gbp/patch_series.py:148:17: E117 over-indented
> ./gbp/scripts/buildpackage.py:333:13: E117 over-indented
> ./gbp/scripts/import_orig.py:82:17: E117 over-indented
> ./gbp/scripts/common/import_orig.py:71:13: E117 over-indented
> ./.pybuild/cpython3_3.7/build/gbp/patch_series.py:148:17: E117 over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/buildpackage.py:333:13: E117 
> over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/import_orig.py:82:17: E117 
> over-indented
> ./.pybuild/cpython3_3.7/build/gbp/scripts/common/import_orig.py:71:13: E117 
> over-indented
> make[2]: *** [Makefile:20: syntax-check] Error 1

Full build log attached.

I would recommend skipping stylistic/non-functional checks like this one,
or making them only produce warnings, when "official" packages are built
in a Debian environment (the style checks can still be fatal when run as
part of `make check` during development, of course). Perhaps something
like this:

# in debian/rules
export IGNORE_STYLE_CHECKS = 1

# in the tests, replacing the flake8 invocation
flake8 || [ -n "$IGNORE_STYLE_CHECKS" ]

Regards,
smcv


git-buildpackage_0.9.14_all_20190907t091327.build.xz
Description: application/xz

Bug#939645: Please use YAML.load_stream() instead of YAML.load_documents(), which was removed in ruby 2.5

[Stig Sandbeck Mathisen]

Package: serverspec-runner
Version: 1.2.2-1
Severity: grave
Tags: patch upstream
Justification: renders package unusable

Dear Maintainer,

The package uses the YAML.load_documents() method, which is no longer present
in the Ruby version that ships with Debian.

The method is replaced with YAML.load_stream(), which is compatible.

The error message, when run, is:

/tmp/tmp.o0z1Ka0UgW$ serverspec-runner
Traceback (most recent call last):
7: from /usr/bin/serverspec-runner:61:in `'
6: from /usr/bin/serverspec-runner:61:in `load'
5: from /usr/share/serverspec-runner/Rakefile:14:in `'
4: from /usr/lib/ruby/vendor_ruby/rake/dsl_definition.rb:141:in 
`namespace'
3: from /usr/lib/ruby/vendor_ruby/rake/task_manager.rb:224:in 
`in_namespace'
2: from /usr/share/serverspec-runner/Rakefile:167:in `block in '
1: from /usr/share/serverspec-runner/Rakefile:167:in `open'
/usr/share/serverspec-runner/Rakefile:168:in `block (2 levels) in ': undefined method `load_documents' for Psych:Module (NoMethodError)
Did you mean?  load_stream


A patch is available in the upstream repo, at
https://github.com/hiracy/serverspec-runner/pull/47/commits/c459787defe1b08bbe46a5acf0ea07039fe44f61
this is also included in upstream version 1.3.8

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/24 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) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages serverspec-runner depends on:
ii  ruby 1:2.5.1
ii  ruby-net-ssh 1:5.1.0-1
ii  ruby-serverspec  2.41.3-3

serverspec-runner recommends no packages.

serverspec-runner suggests no packages.

-- no debconf information

Bug#939630: schleuder: breaks testbed?

[Gianfranco Costamagna]

Source: schleuder
Version: 3.4.0-3
Severity: serious

Hello,
looks like you are playing with /dev/random removing and symlinking it again.

This might break the test environment, so I would say we should

1) declare the test as breaks-testbed [1]

or

2) stop doing that.

I tried to remove that if statement in Ubuntu, and the testsuite ran 
successfully everywhere, including armhf.

I discovered that issue, because in armhf the rm was failing because of 
"dev/random" busy issues.

you can see my "ubuntu3" upload, and the various test results if you want more 
information
http://autopkgtest.ubuntu.com/packages/s/schleuder/eoan/armhf


[1] https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html

thanks

Gianfranco