Bug#939621: marked as done (libaunit19-dev: missing Breaks+Replaces: libaunit18-dev)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 05:49:03 +
with message-id 
and subject line Bug#939621: fixed in libaunit 19-2
has caused the Debian Bug report #939621,
regarding libaunit19-dev: missing Breaks+Replaces: libaunit18-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.)


-- 
939621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaunit19-dev
Version: 19-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libaunit19-dev_19-1_amd64.deb ...
  Unpacking libaunit19-dev (19-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libaunit19-dev_19-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/aunit/ada_containers-aunit_lists.ali', 
which is also in package libaunit18-dev 18-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libaunit19-dev_19-1_amd64.deb


cheers,

Andreas


libaunit18-dev=18-2_libaunit19-dev=19-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libaunit
Source-Version: 19-2

We believe that the bug you reported is fixed in the latest version of
libaunit, 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.
Nicolas Boulenguez  (supplier of updated libaunit 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 01:45:07 +0200
Source: libaunit
Architecture: source
Version: 19-2
Distribution: experimental
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 939621
Changes:
 libaunit (19-2) experimental; urgency=medium
 .
   * Build-Depend: gnat-9. Closes: #939621. Then 19-dev Depends: gnat-9 as
 18-dev on gnat-8. Each compiler conflicts with previous versions of
 itself exactly in order to prevent coinstallations of -dev versions.
Checksums-Sha1:
 7fa252e387a1c9529f97eaf5b57d6a64fdff 2046 libaunit_19-2.dsc
 98f6aa1e5f077c5b8cb2f9e3106c4136b042a6ea 7932 libaunit_19-2.debian.tar.xz
Checksums-Sha256:
 5fad4efb9f1ef69a4f23e0c6ed71403c3650ed0e179bd1f28d6278af92b81052 2046 
libaunit_19-2.dsc
 129df661f88c4fc2adfdce06135d37005dba3b8080187d4fcc87601261f7e277 7932 
libaunit_19-2.debian.tar.xz
Files:
 3df736005b7c30746ee0a63c32c908c8 2046 libdevel optional libaunit_19-2.dsc
 c920a95ccfdd70b370554ceda4134442 7932 libdevel optional 
libaunit_19-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl1zP6ATHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jQ+qD/9rJpFZt9G91soW32D/CeOzYJ4GAmQO
gL6pZCW32jsZ75MAXZxNmgYeGUp4k7aJ1T4WupGPxUVFbVtw/N75AlQRSIFlg0Ma
y0RKK3DmAP3ZkK/pDTbrA3W9xP34DwN84ky4nipTDx2kAyxjZMuHS0DeGE4n/Jfp
lwxqWLaQllocig2ae6o8hea/wJbfU+JpZa3M1K+WJnv1qXg2ePzvxWq6DlifWkZW
g2usMpdUBDKIZ9a81WNogd7g7O/Ei8h2xUVXn8Xb7JEmIOgccCoAlQyx5WpWEQif
M5WKVAsGS+C4/b5m4RmuonAyF7/89uQu7AjupON2UNuYwFl+C8vbaIn4iVde4cZN
isnez7toVGGYus+zVzBIxlrTlWLOxIifDiRVVrF112F5p4Q7Fa/G+qZz5YYf4I6D
64N5+ZynIvsyS0w9QXUsUnSXZTM0XuVIFY15HwslEeueo5nr6DeLSOu46Z1urVtc
k14lBhiipISIvBaPSR4G+yPLTMAmscj0bqkYfftlPHwYf8lR6+HS1wy8QreaPj92
sIHoJt3GdWN4AGlO8EkusxyEcaP7u6vculfrorPpsK6W59cztsbpiFFauJkNB8gp
D6qf6f4UUbsdeoCaNOLfzrW4F0ryYid87XWDxdpOq8/6+PIjrq1YUwlEpv2fywCR
F+1SgeCIbjeq2A==
=yfeA
-END PGP SIGNATURE End Message ---

Bug#874824: marked as done ([amule] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2019 04:34:07 +
with message-id 
and subject line Bug#874824: fixed in amule 1:2.3.2-6
has caused the Debian Bug report #874824,
regarding [amule] 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.)


-- 
874824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amule
Version: 1:2.3.2-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: amule
Source-Version: 1:2.3.2-6

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated amule package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 06 Sep 2019 23:45:02 -0400
Source: amule
Architecture: source
Version: 1:2.3.2-6
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 856914 874824 931270
Changes:
 amule (1:2.3.2-6) unstable; urgency=medium
 .
   * debian/patches/12eca130e743932c17343a1fe82f88a31bd1453a.patch
 - fix crash in amulegui; Closes: #856914
   * debian/control
 - remove 'experimental' tag from amulegui description; Closes: #931270
 - remove libqt4-dev from b-d; Closes: #874824
 - bump Standards-Version to 4.4.0 (no changes needed)
Checksums-Sha1:
 3c5c03ea3ae7c5f0b24a13b6f8cf6c2f007b5fd4 2311 amule_2.3.2-6.dsc
 86ef752d0d0510da6cb5c29cdd0e21b9d87caa59 29184 amule_2.3.2-6.debian.tar.xz
 1d050cfeab9cce67125c6f8a937b8864aff8fa91 12131 amule_2.3.2-6_source.buildinfo
Checksums-Sha256:
 558c52ec718a4a02741b1bfccea2f47e5120b1da52708147c83984dbf354fb35 2311 
amule_2.3.2-6.dsc
 87fb7dc20c199b25a398d2f29da7abd1d644265bb3b35cc9ba5e85c8f0e2ed63 29184 
amule_2.3.2-6.debian.tar.xz
 af0319b566051f45dec19f11410c010a713bbe3b868deb0209af5680dd9e47fc 12131 
amule_2.3.2-6_source.buildinfo
Files:
 2eb8830eb9e164437ac5fd2d56cb93da 2311 net optional amule_2.3.2-6.dsc
 92ee59769315c07139b1768fb53a05bb 29184 net optional amule_2.3.2-6.debian.tar.xz
 e5dd2f6a653f6d92e48775d0714c7652 12131 net optional 
amule_2.3.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Re: python-turbogears2: please provide Python3 module

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #880154 [python-turbogears2] python-turbogears2: please provide Python3 
module
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#935698: amule-utils-gui: amulegui crashing with current libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #935698 [amule-utils-gui] amule-utils-gui: amulegui crashing with current 
libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends
Severity set to 'normal' from 'grave'

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

Bug#935698: amule-utils-gui: amulegui crashing with current libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends

[Sandro Tosi]

control: severity -1 normal

On Tue, Aug 27, 2019 at 1:00 PM Martintxo  wrote:
> OK. Many thanks for you response Bernhard.
>
> Today I find some time for make this.
>
> I installed the following packages:

thanks for your report, but i dont believe it warrants an RC severity,
so i'm downgrading to normal. I can run amulegui on an up-to-date
unstable machine, and if it was failing globally, i feel a lot more
users would complain.

Regards,
-- 
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#874824: Reopened

[Lisandro Damián Nicanor Pérez Meyer]

Hi! The package still build-depends upon libqt4-dev, so the bug is still valid.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Processed: your mail

[Debian Bug Tracking System]

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

> unarchive 874824
Bug #874824 {Done: Sandro Tosi } [src:amule] [amule] Future 
Qt4 removal from Buster
Unarchived Bug 874824
> reopen 874824
Bug #874824 {Done: Sandro Tosi } [src:amule] [amule] Future 
Qt4 removal from Buster
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions amule/1:2.3.2-2.
> severity 874824 serious
Bug #874824 [src:amule] [amule] Future Qt4 removal from Buster
Ignoring request to change severity of Bug 874824 to the same value.
> thanks
Stopping processing here.

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

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

[Sandro Tosi]

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 939179 + src:wxpython3.0
Bug #939179 [src:bibus] bibus: Python2 removal in sid/bullseye
Added indication that 939179 affects src:wxpython3.0
> affects 939180 + src:wxpython3.0
Bug #939180 [src:bittornado] bittornado: Python2 removal in sid/bullseye
Added indication that 939180 affects src:wxpython3.0
> affects 939181 + src:wxpython3.0
Bug #939181 [src:cycle] cycle: Python2 removal in sid/bullseye
Added indication that 939181 affects src:wxpython3.0
> affects 939182 + src:wxpython3.0
Bug #939182 [src:drpython] drpython: Python2 removal in sid/bullseye
Added indication that 939182 affects src:wxpython3.0
> affects 939183 + src:wxpython3.0
Bug #939183 [src:openstv] openstv: Python2 removal in sid/bullseye
Added indication that 939183 affects src:wxpython3.0
> affects 939184 + src:wxpython3.0
Bug #939184 [src:paprass] paprass: Python2 removal in sid/bullseye
Added indication that 939184 affects src:wxpython3.0
> affects 939185 + src:wxpython3.0
Bug #939185 [src:pytimechart] pytimechart: Python2 removal in sid/bullseye
Bug #936011 [src:pytimechart] pytimechart: should this package be removed?
Added indication that 939185 affects src:wxpython3.0
Added indication that 936011 affects src:wxpython3.0
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936011
939179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939179
939180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939180
939181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939181
939182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939182
939183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939183
939184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939184
939185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939627: mrtrix3: Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: mrtrix3
Version: 3.0~rc3+git135-g2b8e7d0c2-3
Severity: serious
Justification: Depends upon Qt4 which will not be shipped with bullseye
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 



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

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=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)
LSM: AppArmor: enabled

Bug#939626: centreon-broker: Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: centreon-broker
Version: 18.10.0-4
Severity: serious
Justification: Depends upon Qt4 which will not be shipped with bullseye
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 


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

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=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)
LSM: AppArmor: enabled

Bug#874843: RC bug ignored

[Lisandro Damián Nicanor Pérez Meyer]

Hi Eduard!

As you reassigned the bug to wnpp cdcat lost it's RC bug. Do you mind if I 
clone it and reassign the clone to cdcat?

We are targetting at removing Qt4 from testing as a first step.

Thanks, Lisandro.

Bug#936069: sorry, these were my fault

[Nicholas D Steeves]

Hi,

Sorry, these bugs were my fault and were introduced by my MR.  Jan,
thank you for taking care of them! :-)

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#923084: Prepared gandi-cli release “1.5-1”

[Ben Finney]

Howdy Unit193,

On 14-Aug-2019, Ben Finney wrote:
> Control: tags -1 + confirmed pending

I have prepared a release, “1.5-1”, but failed to get it into the
Debian archive.

This is because the Debian GnuPG keyring is not yet up to date with my
signing key, and its copy of my key is expired.

Are you able to finalise that release, and upload it to Debian? The
instructions in ‘debian/README.Source’ are accurate, but in brief:
Finalise the release in the changelog, export the Debian packaging
onto the upstream source in a separate build area. Build the source
package from that. Run any tests you want. If they pass, upload the
package.

(Reminder, in case you need it, that uploads must now *not* include
binary package, otherwise they won't go to the build daemons.)

If the upload succeeds, commit the finalised changelog entry to your
fork of the Git repository. Make a merge request and I'll be able to
get it into the central repository.

No obligation on you to do any of this, because eventually the Debian
keyring will have my updated key and I will again be able to upload
packages.

-- 
 \   “Are you pondering what I'm pondering?” “Well, I think so |
  `\  Brain, but what if we stick to the seat covers?” —_Pinky and |
_o__)   The Brain_ |
Ben Finney 


signature.asc
Description: PGP signature

Processed: found 939598 in 0.1-1, found 939598 in 2019.01+dfsg-7

[Debian Bug Tracking System]

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

> found 939598 0.1-1
Bug #939598 [libubootenv-tool,u-boot-tools] libubootenv-tool: trying to 
overwrite '/usr/bin/fw_printenv', which is also in package u-boot-tools 
2019.01+dfsg-7
There is no source info for the package 'u-boot-tools' at version '0.1-1' with 
architecture ''
Marked as found in versions libubootenv/0.1-1.
> found 939598 2019.01+dfsg-7
Bug #939598 [libubootenv-tool,u-boot-tools] libubootenv-tool: trying to 
overwrite '/usr/bin/fw_printenv', which is also in package u-boot-tools 
2019.01+dfsg-7
There is no source info for the package 'libubootenv-tool' at version 
'2019.01+dfsg-7' with architecture ''
Marked as found in versions u-boot/2019.01+dfsg-7.
> thanks
Stopping processing here.

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

Bug#939623: python3-mne: missing Breaks+Replaces: python-mne

[Andreas Beckmann]

Package: python3-mne
Version: 0.18.1+dfsg-0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'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 .../python3-mne_0.18.1+dfsg-0.1_all.deb ...
  Unpacking python3-mne (0.18.1+dfsg-0.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-mne_0.18.1+dfsg-0.1_all.deb (--unpack):
   trying to overwrite '/usr/bin/mne', which is also in package python-mne 
0.17+dfsg-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-mne_0.18.1+dfsg-0.1_all.deb


cheers,

Andreas


python-mne=0.17+dfsg-1_python3-mne=0.18.1+dfsg-0.1.log.gz
Description: application/gzip

Bug#939621: libaunit19-dev: missing Breaks+Replaces: libaunit18-dev

[Andreas Beckmann]

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

Hi,

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

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

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

  Preparing to unpack .../libaunit19-dev_19-1_amd64.deb ...
  Unpacking libaunit19-dev (19-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libaunit19-dev_19-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/aunit/ada_containers-aunit_lists.ali', 
which is also in package libaunit18-dev 18-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libaunit19-dev_19-1_amd64.deb


cheers,

Andreas


libaunit18-dev=18-2_libaunit19-dev=19-1.log.gz
Description: application/gzip

Bug#939620: python3-zope.testrunner: missing Breaks+Replaces: python-zope.testrunner

[Andreas Beckmann]

Package: python3-zope.testrunner
Version: 4.4.9-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 .../python3-zope.testrunner_4.4.9-2_all.deb ...
  Unpacking python3-zope.testrunner (4.4.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/zope-testrunner', which is also in package 
python-zope.testrunner 4.4.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb


cheers,

Andreas


python-zope.testrunner=4.4.9-1_python3-zope.testrunner=4.4.9-2.log.gz
Description: application/gzip

Bug#938875: yum-utils: Python2 removal in sid/bullseye

[Thomas Goirand]

On 9/5/19 9:18 PM, Mike Miller wrote:
> The upstream replacement for the combination of yum + yum-utils (Python
> 2 only) is dnf (Python 3).
> 
> The only reverse dependency of yum-utils is mock. It looks like the
> version of mock already in Debian supports either dnf or yum. Once dnf
> is in Debian, mock can drop the dependency on yum and yum-utils, and
> yum-utils can be removed.
> 

And then I believe yum should also be removed. Your thoughts?

Cheers,

Thomas Goirand (zigo)

Bug#939401:

[Krzysztof Marczak]

I have similar behavior after upgrade to version 430. When xorg starts
there is black screen for about 10 seconds and then it returns to tty. I
have nVidia GTX 1050 card. I'm going to install version 435 from
experimental to solve this problem
   Krzysztof

Bug#939589: marked as done (pymca: build failure on armhf)

[Debian Bug Tracking System]

Your message dated Fri, 06 Sep 2019 20:38:20 +
with message-id 
and subject line Bug#939589: fixed in pymca 5.5.0+dfsg-2
has caused the Debian Bug report #939589,
regarding pymca: build failure on armhf
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.)


-- 
939589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymca
Version: 5.5.0+dfsg-1
Severity: serious

Hello, looks like your last upload is FTBFS on armhf...
https://buildd.debian.org/status/package.php?p=pymca=unstable

Also, you might have a test failure on autopkgtestsuite:
testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Segmentation fault


Can you please have a look?

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: pymca
Source-Version: 5.5.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pymca, 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.
Drew Parsons  (supplier of updated pymca 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 02:19:10 +0800
Source: pymca
Architecture: source
Version: 5.5.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 939589
Changes:
 pymca (5.5.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * debian patch testInteractionSilxMpl_skip_OpenGL.patch skips
 testInteractionSilxMpl unless OpenGL is available
   * skip OpenGL tests on armhf (OpenGL is not available there)
 Closes: #939589.
   * Standards-Version: 4.4.0
   * mark pymca-data, pymca-doc as Multi-Arch: foreign
Checksums-Sha1:
 8c102a5ef5fbcc3d8c7049c63dc91361a81b5f15 3566 pymca_5.5.0+dfsg-2.dsc
 874bae3616bffd464b71a68a4ce9c0a64549967b 10056 pymca_5.5.0+dfsg-2.debian.tar.xz
 d784df8276cd60726b29af9ead129f5b70bdf366 19854 
pymca_5.5.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 7f558026e29bd6caf8678978729ce9880f28d5683169b193d8b583113ae76937 3566 
pymca_5.5.0+dfsg-2.dsc
 2a474c3b7a3bee91b2f55cbdd1b17b4e7b212116f3cb1d5d8b203b429bd444ff 10056 
pymca_5.5.0+dfsg-2.debian.tar.xz
 95f2d0f6fe798ecd0fe713514bfc5a06eff28148d528b0ddd78db150d8b01822 19854 
pymca_5.5.0+dfsg-2_source.buildinfo
Files:
 d8782a6d96537cd5ff3d274311d9a7a7 3566 science optional pymca_5.5.0+dfsg-2.dsc
 03d233279c1e7cb23b58e22345e52f2b 10056 science optional 
pymca_5.5.0+dfsg-2.debian.tar.xz
 433b5420061d11d2c9f24fdb8b1ac9ee 19854 science optional 
pymca_5.5.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl1ytE4UHGRwYXJzb25z
QGRlYmlhbi5vcmcACgkQVz7x5L1aAfor3A//QscgU4frbAOr996PjVzamb+sJ4II
+Lra8daU2tYOkj1xWROZ7ATnOFphzgIk+j2Hn1qXiLMScLLm30ROeGDSlUmp2hC5
aitICX0RUpHfp2hkQ93Ue2yUAbv6Blj0pYMRysu+SaiRfHK7ZNnQL1H4VjbLHlD/
W96cNAfZYATO/0A0MPBDfI/cd17acDq3K+sPPJds03tPU4Uzb132SREX/RvMobyc
v1vTO4RLNZ39aE1AvIgrm0J7n1a2Mz2ytxm3aLJkm8QvQkOk+GFF8VaNNGlohUgK
ZRntMhimcRKMc1X9VHKoYNVEw2zb+SsJI/2mtzFu/GjmMs58ODFa0JT4wm/aZsRJ
UXr+A8zgT4/kCpJ5H+ld/ShSlqN+bTXnrrFzdcs2FWGUPBm2/aJ4LCdB2TIT0/5M
gpYVnB+bu6WJ3lD2GAYlRigltcHgmtV7CuaaZcg2SwpXixf87RBUN0AQUbbxa0HS
3Q84+dHMik64ZCRAbjvNNBi/FYV6iL8H8AX2niLYX1ECJI/NqcyXifsWiPQVlGuT
8+cPt9YeLbKhbgJsFHgWGVKWfARho9B9m+Uqq/tHs0S6Et8SAWjoRXMLc5lPuKsX
wUdTpXzSw+LJk7RXTjW/GWUvYevNLF4sPSt3cl8c6YvipB+7EPdq/uIMEhYX7/Db
v1yFWeeUT25EApc=
=xY3a
-END PGP SIGNATURE End Message ---

Processed (with 1 error): add blocking bugs

[Debian Bug Tracking System]

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

> block 938562 by 938562
Bug #938562 [src:sshfp] sshfp: Python2 removal in sid/bullseye
Failed to set blocking bugs of 938562: It is nonsensical for a bug to block 
itself (or a merged partner): 938562.

> block 936850 by 937300
Bug #936850 [src:libesedb] libesedb: Python2 removal in sid/bullseye
936850 was not blocked by any bugs.
936850 was not blocking any bugs.
Added blocking bug(s) of 936850: 937300
> block 936852 by 937300
Bug #936852 [src:libevt] libevt: Python2 removal in sid/bullseye
936852 was not blocked by any bugs.
936852 was not blocking any bugs.
Added blocking bug(s) of 936852: 937300
> block 936853 by 937300
Bug #936853 [src:libevtx] libevtx: Python2 removal in sid/bullseye
936853 was not blocked by any bugs.
936853 was not blocking any bugs.
Added blocking bug(s) of 936853: 937300
> block 936890 by 937300
Bug #936890 [src:liblnk] liblnk: Python2 removal in sid/bullseye
936890 was not blocked by any bugs.
936890 was not blocking any bugs.
Added blocking bug(s) of 936890: 937300
> block 936895 by 937300
Bug #936895 [src:libmsiecf] libmsiecf: Python2 removal in sid/bullseye
936895 was not blocked by any bugs.
936895 was not blocking any bugs.
Added blocking bug(s) of 936895: 937300
> block 936897 by 937300
Bug #936897 [src:libolecf] libolecf: Python2 removal in sid/bullseye
936897 was not blocked by any bugs.
936897 was not blocking any bugs.
Added blocking bug(s) of 936897: 937300
> block 936915 by 937300
Bug #936915 [src:libscca] libscca: Python2 removal in sid/bullseye
936915 was not blocked by any bugs.
936915 was not blocking any bugs.
Added blocking bug(s) of 936915: 937300
> block 936941 by 936299 936341 936442 936488 936625 936755 937092 937298 
> 937325 937750 938844 938873 938875 936942 936341 936511 938341
Bug #936941 [src:libxml2] libxml2: Python2 removal in sid/bullseye
936941 was not blocked by any bugs.
936941 was not blocking any bugs.
Added blocking bug(s) of 936941: 936942, 938873, 937298, 936755, 936299, 
938875, 936625, 936488, 937750, 936511, 937092, 936442, 938844, 938341, 937325, 
and 936341
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936850
936852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936852
936853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936853
936890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936890
936895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936895
936897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936897
936915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936915
936941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936941
938562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939608: bitcoin: CVE-2019-15947

[Salvatore Bonaccorso]

Source: bitcoin
Version: 0.18.1~dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for bitcoin.

CVE-2019-15947[0]:
| In Bitcoin Core 0.18.0, bitcoin-qt stores wallet.dat data unencrypted
| in memory. Upon a crash, it may dump a core file. If a user were to
| mishandle a core file, an attacker can reconstruct the user's
| wallet.dat file, including their private keys, via a grep "6231 0500"
| command.

The severity is a bit exagerated here, but given the package is only
in testing and unstable, before the buster release this might be
considered RC and needed to fix. But it's a long road to there.

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-15947
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15947

Please adjust the affected versions in the BTS as needed.



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

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

Bug#932637: nmu now in the delayed queue

[gregor herrmann]

On Fri, 06 Sep 2019 08:40:53 +0200, Dominique Dumont wrote:

> On Thursday, 5 September 2019 20:45:05 CEST gregor herrmann wrote:
> > What happened to this NMU?
> It's in unstable 

AH, right, should have checked.
 
> > I just noticed that the bug ist still open and perl6-readline was
> > removed from testing …
> The nmu version (0.1.4-3.1) cannot go in testing because rakudo is FTBS with 
> newer libuv.

Right.

But #932637 (and probably #919368 as well) should still be closed
with version 0.1.4-3.1, I guess?
 

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#939457: marked as done (lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in)

[Debian Bug Tracking System]

Your message dated Fri, 06 Sep 2019 19:19:04 +
with message-id 
and subject line Bug#939457: fixed in beautifulsoup4 4.8.0-2
has caused the Debian Bug report #939457,
regarding lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out 
*exactly* the same as it went in
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.)


-- 
939457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxml, beautifulsoup4
Control: found -1 lxml/4.4.1-1
Control: found -1 beautifulsoup4/4.8.0-1
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 lxml the autopkgtest of beautifulsoup4 fails in
testing when that autopkgtest is run with the binary packages of lxml
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
lxml   from testing4.4.1-1
beautifulsoup4 from testing4.8.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test seems
to me to be testing a reasonable thing, but I am not in the position to
judge if this is indeed guaranteed behavior: A real XHTML document
should come out *exactly* the same as it went in.

Currently this regression is blocking the migration of lxml 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=lxml

https://ci.debian.net/data/autopkgtest/testing/amd64/b/beautifulsoup4/2885653/log.gz

autopkgtest [18:11:15]: test unittests3: [---
=== python3.7 ===
.../usr/lib/python3/dist-packages/bs4/builder/_htmlparser.py:78:
UserWarning: don't crash
  warnings.warn(msg)
..F...F..
==
FAIL: test_nested_namespaces
(bs4.tests.test_lxml.LXMLXMLTreeBuilderSmokeTest)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/bs4/testing.py", line 841, in
test_nested_namespaces
self.assertEqual(doc, soup.encode())
AssertionError: b'http://ns1/;>\nhttp://ns2[96 chars]ent>' != b'http://ns1/;>\nhttp://n[99 chars]ent>'

==
FAIL: A real XHTML document should come out *exactly* the same as it
went in.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/bs4/testing.py", line 830, in
test_real_xhtml_document
soup.encode("utf-8"), markup)
AssertionError: b'http://www.w3.org/1999/xhtml;>\n[56 chars]tml>' !=
b'http://www.w3.org/1999/xhtml;>\n<[55
chars]tml>'

--
Ran 496 tests in 0.443s

FAILED (failures=2)
autopkgtest [18:11:16]: test unittests3: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: beautifulsoup4
Source-Version: 4.8.0-2

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

(This message was generated automatically at their request; if you
believe that there is a problem 

Bug#939457: lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in

[Stefano Rivera]

Hi Paul (2019.09.05_04:56:41_-0300)

Fixed upstream in beautifulsoup4, upload incoming.

https://bugs.launchpad.net/beautifulsoup/+bug/1840141

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936068: marked as done (python3-gnuplot: missing Breaks+Replaces: python-gnuplot)

[Debian Bug Tracking System]

Your message dated Fri, 06 Sep 2019 19:08:27 +
with message-id 
and subject line Bug#936068: fixed in python-gnuplot 1.8-8
has caused the Debian Bug report #936068,
regarding python3-gnuplot: missing Breaks+Replaces: python-gnuplot
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.)


-- 
936068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gnuplot
Version: 1.8-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python3-gnuplot_1.8-7_all.deb ...
  Unpacking python3-gnuplot (1.8-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-gnuplot_1.8-7_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-gnuplot/html/ANNOUNCE.html', 
which is also in package python-gnuplot 1.8-6
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-gnuplot_1.8-7_all.deb


cheers,

Andreas


python-gnuplot=1.8-6_python3-gnuplot=1.8-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-gnuplot
Source-Version: 1.8-8

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-gnuplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Sep 2019 12:03:26 -0600
Source: python-gnuplot
Binary: python3-gnuplot
Architecture: source
Version: 1.8-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Josue Ortega 
Description:
 python3-gnuplot - Python interface to the gnuplot plotting program
Closes: 936068
Changes:
 python-gnuplot (1.8-8) unstable; urgency=medium
 .
   * debian/control: Add Breaks+Replaces: python-gnuplot. Closes: #936068
   * Upload to unstable
Checksums-Sha1:
 9ed179c0dd23f7323cf4721f048c228e74ca0b6d 2147 python-gnuplot_1.8-8.dsc
 b83c7080c73ce8595d6767694d0bb7bdbb8ea9bf 13304 
python-gnuplot_1.8-8.debian.tar.xz
 6cf8a9ddc4c4375ded191a75af2711161a71bb16 5989 
python-gnuplot_1.8-8_amd64.buildinfo
Checksums-Sha256:
 3ac3bebcb5f43d4a15ff19904908449534d48406df1ca90f350da993f65c8d4c 2147 
python-gnuplot_1.8-8.dsc
 310fbdd493a5d94addfee08646e375e21cc6c8dc6c1d07ff538e7495255d1d07 13304 
python-gnuplot_1.8-8.debian.tar.xz
 ac496e98d07d4e3af3562c70a3aa702057aaa2a53fd43c96a02b53d392d01ee6 5989 
python-gnuplot_1.8-8_amd64.buildinfo
Files:
 ab6a8382f587654f36f8f70eed90e645 2147 python optional python-gnuplot_1.8-8.dsc
 df8ea139c6b45ae011c1a92d0ef43c57 13304 python optional 
python-gnuplot_1.8-8.debian.tar.xz
 bee11ab82b4439d3fbc9373027756221 5989 python optional 
python-gnuplot_1.8-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl1yoksRHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+1MA/7BdYRalwb8LxsIu1goUWdy1QRYmvRYUCF
Q5kmk1mJIgHliIymlrmv5NDIHmHT4ZZtrLQvy8LZWT1UTRNMH5QpiTTZyNiXBrNF
iINa6qVBHdUC3kweHh2vbYQOGyG9dioc5yt/zw1BRn81RXh9BjHWnfUA82moRvpO
OYBSQm+L8A3l8WR5dA8sl1Lqy/YQQEYmYbUfSG/Hn8XP1fLqtrgKU+eoPLHCS8KK
Cdc6ediPwIC+EVksER4MUUV6NbBVLJe8hTSPyaHuEg31MRnptMWbrs9GDBg6yF4W
+xihGbsw5QkOH4KT7Qo/RVFffR49HMB4iSv4WgFBaXEaGNPzGj5YFAgARD0QW/bH
NNs1/mUR+Mce1p3IELzIT6Wdxoe2ohJQco6F9YFMPkeiHVzi1Cab8WjX0Nebkmem
vfv5uADlGk5T/4EO7jY/VS1rUzycvAfiqKlHZUBtt7IGFFcYVTjy4MeEfrnVrf3Q
4jvR/XF6wz3zHLKzuO1d40LGhawBhtMpFsevSBHwy31MXKdMUeWn31K416EtvXLV
5ncLHU9JRcOGlikNGGCHTF1cXLnnqi0yKxXkusjpAj4IM/T5TbjJNSIYlKfu0D2v
tt2eoLpXpP0UiU1fBZjT55QNgohSEq5pST4u078/evhu8kO+SauNhdZXrnZPh217
9Xx79R+yLZE=
=4qOp
-END PGP SIGNATURE End 

Bug#939457: marked as pending in beautifulsoup4

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/beautifulsoup4/commit/9d3ef189e56a65b218a4f3a3c89716aecde0ac20


Patch: Fixed the definition of the default XML namespace when using lxml 4.4. 
(Closes: #939457)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/939457

Processed: Bug#939457 marked as pending in beautifulsoup4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #939457 [src:lxml, src:beautifulsoup4] lxml breaks beautifulsoup4 
autopkgtest: a real XHTML didn't come out *exactly* the same as it went in
Added tag(s) pending.

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

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

[Axel Beckert]

Package: libubootenv-tool,u-boot-tools
Severity: serious
Version: libubootenv/0.1-1 u-boot/2019.01+dfsg-7

Hi,

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

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

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

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

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

Bug#939596: python3-ndg-httpsclient: trying to overwrite '/usr/bin/ndg_httpclient', which is also in package python-ndg-httpsclient 0.5.1-1

[Axel Beckert]

Package: python3-ndg-httpsclient
Version: 0.5.1-2
Severity: serious

Dear Maintainer,

your upload seems to have moved /usr/bin/ndg_httpclient (and
potentially further files) from python-ndg-httpsclient to
python3-ndg-httpsclient without the according Breaks and Replaces
headers.

This resulted in the following file conflict when upgrading
python3-ndg-httpsclient from 0.5.1-1 to 0.5.1-2 with
python-ndg-httpsclient being installed, too:

Preparing to unpack .../29-python3-ndg-httpsclient_0.5.1-2_all.deb ...
Unpacking python3-ndg-httpsclient (0.5.1-2) over (0.5.1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-idI8Ph/29-python3-ndg-httpsclient_0.5.1-2_all.deb 
(--unpack):
 trying to overwrite '/usr/bin/ndg_httpclient', which is also in package 
python-ndg-httpsclient 0.5.1-1

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

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

Versions of packages python3-ndg-httpsclient depends on:
ii  python3  3.7.3-1
ii  python3-openssl  19.0.0-1
ii  python3-pyasn1   0.4.2-3

python3-ndg-httpsclient recommends no packages.

python3-ndg-httpsclient suggests no packages.

-- no debconf information

Bug#939594: vmtk build-depends on cruft package

[Peter Michael Green]

package: vmtk
severity: serious
version: 1.3+dfsg-2.3

vmtk build-depends on libvtk6-java which is no longer built by the vtk6 
source package.

Processed: severity of 939558 is important, found 939558 in 4.19.37-5+deb10u2

[Debian Bug Tracking System]

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

> severity 939558 important
Bug #939558 [src:linux] System powers off or crashes when asking "suspend to 
ram" via GUI
Severity set to 'important' from 'serious'
> found 939558 4.19.37-5+deb10u2
Bug #939558 [src:linux] System powers off or crashes when asking "suspend to 
ram" via GUI
Marked as found in versions linux/4.19.37-5+deb10u2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#939593: gnome-vfs: FTBFS with gtk-doc-tools 1.32 (from experimental)

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 876586 -1
Bug #876586 [src:gnome-vfs] gnome-vfs FTBFS with gtk-doc-tools 1.26: 
gtkdoc-mktmpl is no longer available
Bug #939593 [src:gnome-vfs] gnome-vfs: FTBFS with gtk-doc-tools 1.32 (from 
experimental)
Severity set to 'serious' from 'important'
939500 was blocked by: 939592 939591 939593
939500 was blocking: 938944
Removed blocking bug(s) of 939500: 939593
Added tag(s) ftbfs and buster.
Merged 876586 939593

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

Processed: fix severity

[Debian Bug Tracking System]

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

> severity 939420 serious
Bug #939420 [stdx-allocator] stdx-allocator: FTBFS, test failures.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#934599: Important Issues Reply Back

[Mrs Alice Louise Walton]

Hi, I'm  Mrs Alice Louise Walton i have an important issue for you, reply via 
e-mail:alicewalton0...@gmail.com.for details.

Bug#939404: marked as done (ldc ftbfs, missing b-d gdmd)

[Debian Bug Tracking System]

Your message dated Fri, 6 Sep 2019 18:45:35 +0200
with message-id 

and subject line Re: Bug#939404: ldc ftbfs, missing b-d gdmd
has caused the Debian Bug report #939404,
regarding ldc ftbfs, missing b-d gdmd
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.)


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

Package: src:ldc
Version: 1:1.17.0-1
Severity: serious
Tags: sid bullseye

looks like gdmd isn't available, and according to the changelog gdc should be 
used for the bootstrap?
--- End Message ---
--- Begin Message ---
Am Mi., 4. Sept. 2019 um 18:18 Uhr schrieb Matthias Klumpp :
>
> Am Mi., 4. Sept. 2019 um 18:05 Uhr schrieb Matthias Klose :
> >
> > On 04.09.19 18:01, Matthias Klumpp wrote:
> > > Am Mi., 4. Sept. 2019 um 18:00 Uhr schrieb Matthias Klose 
> > > :
> > >>
> > >> Package: src:ldc
> > >> Version: 1:1.17.0-1
> > >> Severity: serious
> > >> Tags: sid bullseye
> > >>
> > >> looks like gdmd isn't available, and according to the changelog gdc 
> > >> should be
> > >> used for the bootstrap?
> > >
> > > Man you're quick ^^
> >
> > sorry ;)
> >
> > > gdmd is currently stuck in NEW, I hope it gets accepted quickly:
> > > https://ftp-master.debian.org/new/gdmd_2.068.2%2Bgit190828-1.html

The package is accepted now, and LDC is building with GDC as
bootstrapping compiler now :-)
Very neat!

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/--- End Message ---

Bug#939589: pymca: build failure on armhf

[Gianfranco Costamagna]

Source: pymca
Version: 5.5.0+dfsg-1
Severity: serious

Hello, looks like your last upload is FTBFS on armhf...
https://buildd.debian.org/status/package.php?p=pymca=unstable

Also, you might have a test failure on autopkgtestsuite:
testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Segmentation fault


Can you please have a look?

thanks

Gianfranco

Bug#935699: marked as done (gdm3: uninstallable on s390x)

[Debian Bug Tracking System]

Your message dated Fri, 06 Sep 2019 16:05:00 +
with message-id 
and subject line Bug#935699: fixed in gdm3 3.33.92-2
has caused the Debian Bug report #935699,
regarding gdm3: uninstallable on s390x
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.)


-- 
935699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gdm3
version: 3.30.2-3
severity: serious

Hi,

On s390x, gdm3 isn't installable, because it needs gnome-shell, which FTBFS
there. So either the dependency should be dropped or the binaries for gdm3 on
s390x should be removed.

Please note that this blocks the s390x binaries from some other packages (like
gnome-panel and gnome-applets) to migrate to testing. This also blocks new
source uploads for the packages depending on libgdm1.

Ivo
--- End Message ---
--- Begin Message ---
Source: gdm3
Source-Version: 3.33.92-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Sep 2019 16:44:21 +0100
Source: gdm3
Architecture: source
Version: 3.33.92-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Iain Lane 
Closes: 935699
Changes:
 gdm3 (3.33.92-2) experimental; urgency=medium
 .
   [ Simon McVittie ]
   * Merge packaging changes from unstable (Closes: #935699)
 .
   [ Laurent Bigonville ]
   * Add extra explanation to the GDM PAM service about what pam_selinux is
 actually doing
Checksums-Sha1:
 0df7a5591904bf24aee84809abc95de83487c25a 2991 gdm3_3.33.92-2.dsc
 e3da32f7b21b625a5f1a479bbaa0bf7ff19e127b 89792 gdm3_3.33.92-2.debian.tar.xz
 5c645807c1901b7f7f4d444db5c533dd12869057 20495 gdm3_3.33.92-2_source.buildinfo
Checksums-Sha256:
 4b26572e0d8ca848e05000dc9f56ea65232a7fbeedd2aacb07a4089ee594f519 2991 
gdm3_3.33.92-2.dsc
 1924d891a08b7653dfeb6b5cbe83c6d88e52537cd8663fa378875dc8463b5b92 89792 
gdm3_3.33.92-2.debian.tar.xz
 709bed3e7e76942a88c1a6a789eed016e45652f7025c2d12206d99aeec87bb3c 20495 
gdm3_3.33.92-2_source.buildinfo
Files:
 1ffe7a7c289b54b755d6ae312413e91d 2991 gnome optional gdm3_3.33.92-2.dsc
 657d0d1484902a54a2d068387fd167f9 89792 gnome optional 
gdm3_3.33.92-2.debian.tar.xz
 e13c2212be32a0f3d82e8a788c11cb82 20495 gnome optional 
gdm3_3.33.92-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPQ77lee1I38W6CJY41LVxRxQQdQFAl1ygC8ACgkQ41LVxRxQ
QdTaKg/+MTvz4Rv1KAO06HN1ETwxcpWBa1MKp+0/lf37f4yTdlBs2nY+9HHZIEaT
3n3fycxo7PhGQLcrJQxCUPf6snxR95F6twpS75zhzEhuYxaDgn1TxeqxcUZb1xhU
+9o6qApyrX8SFEkoiZue4Z5WemSPlj4Sc5fOXdlTcigt06O0nGvdxz25UngOSalW
1pznIuljFWOrzLCMSOWy69Pf5AL/jfsHxA21eh+huBw+VwLHbI343tT2JK1JLrx7
PSVN4lwD31iJWE5aPRwlpqjVElWLPjHSyDllvwdxfLMEGMZCCTtIylNtiUH71zAE
O1p7Yu7uJ0XMpDfsXmkSq5yvk/RnWUOalPVJ0K0Sw2z7qJKf1jKrWsQ2GCnUH2EZ
OAAMNqYCYeNrlTAbT3VnnG5Mm4LXgorDI1DA2WHCRuWqje4vVEbPYbhYSQpVTYtY
YW+uM3ufP9BjuSADX78xEZQ24e9B9kErokRpaXak7L6Ye48bkH6r8ftB+EPD2xy5
XPkp5TdxveIR8AYGWMR5bCzoTSOh0UAqUhwBiAO+l3uT5050hLHDpTD6nh+9QJdI
f7TL6Hq4yjeVQ5ZhAwNOZlyajKFpdSuQ8SZ9WaECUPurQDH/Y68tYT2DeMvMlJDw
KB2gUbSgS5TzGGTQOqexXFulirgKtC2EDn4P2Isqv21Xim0B1oo=
=XzVX
-END PGP SIGNATURE End Message ---

Processed: Re: [Pkg-fonts-devel] Bug#939578: fontforge: FTBFS: There is no package matching [libspiro1-dev] and noone provides it

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 d-shlibs 0.86
Bug #939578 [src:fontforge] fontforge: FTBFS: There is no package matching 
[libspiro1-dev] and noone provides it
Bug reassigned from package 'src:fontforge' to 'd-shlibs'.
No longer marked as found in versions fontforge/1:20170731~dfsg-1.
Ignoring request to alter fixed versions of bug #939578 to the same values 
previously set
Bug #939578 [d-shlibs] fontforge: FTBFS: There is no package matching 
[libspiro1-dev] and noone provides it
Marked as found in versions d-shlibs/0.86.
> affects -1 fontforge
Bug #939578 [d-shlibs] fontforge: FTBFS: There is no package matching 
[libspiro1-dev] and noone provides it
Added indication that 939578 affects fontforge

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

Bug#939578: [Pkg-fonts-devel] Bug#939578: fontforge: FTBFS: There is no package matching [libspiro1-dev] and noone provides it

[Jonas Smedegaard]

control: reassign -1 d-shlibs 0.86
control: affects -1 fontforge

Quoting Sebastian Ramacher (2019-09-06 15:49:40)
> Source: fontforge
> Version: 1:20170731~dfsg-1
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> fontforge no longer builds due the spiro transition:
> | d-shlibmove --commit \
> |   --devunversioned \
> |   --exclude-la \
> |   --extralib debian/tmp/x/usr/lib/libgioftp.so \
> |   --extralib debian/tmp/x/usr/lib/libgunicode.so \
> |   --extralib debian/tmp/x/usr/lib/libgutils.so \
> |   --movedev "debian/tmp/x/usr/include/*" usr/include/ \
> |   --movedev "debian/tmp/x/usr/lib/pkgconfig/*.pc" usr/lib/pkgconfig \
> |   --override s/libfontforge2-dev/libfontforge-dev/ \
> |   debian/tmp/x/usr/lib/libfontforge.so
> | Library package automatic movement utility
> |  --> libfontforge-dev package from same source package.
> |  --> libfreetype6-dev package exists.
> |  --> libgif-dev package exists.
> |  --> libglib2.0-dev package exists.
> |  --> libjpeg-dev package exists.
> |  --> libltdl7-dev is provided by a package.
> |  --> libpng-dev package exists.
> |  --> libpython-dev package exists.
> |  --> libreadline-dev package exists.
> | devlibs error: There is no package matching [libspiro1-dev] and noone 
> provides it, please report bug to d-shlibs maintainer
> |  --> libtiff5-dev package exists.
> |  --> libuninameslist-dev package exists.
> |  --> libxml2-dev package exists.
> |  --> zlib1g-dev package exists.
> | make: *** [debian/rules:63: debian/stamp-local-shlibs-libfontforge] Error 1
> | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
> returned exit status 2
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=fontforge=amd64=1%3A20170731%7Edfsg-1%2Bb2=1567253536=0
> for the full log.

This bug is in d-shlibs (but can be worked around locally in fontforge).

Thanks for reporting,

 - 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#939400: sddm: Auth: sddm-helper exited with 11

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #939400 [sddm] sddm: Auth: sddm-helper exited with 11
Severity set to 'normal' from 'grave'

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

Bug#939400: sddm: Auth: sddm-helper exited with 11

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Konomi!

El 2019-09-05 a las 01:14 +1000, Konomi escribió:

Package: sddm
Version: 0.18.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable



Quoting the upstream bug report:



"sddm-greeter needs execution rights at 
/var/lib/sddm/.cache/sddm-greeter/qmlcache/*.qmlc.
krunner needs execution at /home/user/.cache/krunner/qmlcache/*.qmlc. It breaks
when /var and /home partitions are mounted with noexec flag which is often used 
on
hardened setups or Trusted Path Execution available on hardened linux kernels.



As for now it could be fixed by disabling qml cache by setting 
QML_DISABLE_DISK_CACHE=1
environment variable. Is there a chance that qt will check permission rights 
first then
quietly disable qmlcache per app instead of crashing?



Alternatively it could create cachedir somewhere in /usr/lib/qt same as python3 
have
it's pycache dir."



Upstream bug report: https://bugreports.qt.io/browse/QTBUG-58508



The work around of adding QML_DISABLE_DISK_CACHE=1 to /etc/enviroment got sddm 
working
for me again. Without the work around sddm will start but show just a black 
screen, so
I've marked this bug as grave since it completely breaks the package.


I don't see any reference that a program needs to support a hardened setup in 
Debian, and this is clearly something not supported upstream, as such I'm 
degrading the severity of this issue.


Let's see what do the qt maintainers think about setting a different cache dir 
or patching qt to disable the disk cache if the cache won't be loadable.


Happy hacking,
--
"It's a well-known fact that computing devices such as the abacus were 
invented thousands of years ago. But it's not well known that the first use of 
common computer protocol occurred in the Old Testament. This, of course, was 
when Moses aborted the Egyptians' process with a control-sea."

-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#939578: fontforge: FTBFS: There is no package matching [libspiro1-dev] and noone provides it

[Sebastian Ramacher]

Source: fontforge
Version: 1:20170731~dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

fontforge no longer builds due the spiro transition:
| d-shlibmove --commit \
|   --devunversioned \
|   --exclude-la \
|   --extralib debian/tmp/x/usr/lib/libgioftp.so \
|   --extralib debian/tmp/x/usr/lib/libgunicode.so \
|   --extralib debian/tmp/x/usr/lib/libgutils.so \
|   --movedev "debian/tmp/x/usr/include/*" usr/include/ \
|   --movedev "debian/tmp/x/usr/lib/pkgconfig/*.pc" usr/lib/pkgconfig \
|   --override s/libfontforge2-dev/libfontforge-dev/ \
|   debian/tmp/x/usr/lib/libfontforge.so
| Library package automatic movement utility
|  --> libfontforge-dev package from same source package.
|  --> libfreetype6-dev package exists.
|  --> libgif-dev package exists.
|  --> libglib2.0-dev package exists.
|  --> libjpeg-dev package exists.
|  --> libltdl7-dev is provided by a package.
|  --> libpng-dev package exists.
|  --> libpython-dev package exists.
|  --> libreadline-dev package exists.
| devlibs error: There is no package matching [libspiro1-dev] and noone 
provides it, please report bug to d-shlibs maintainer
|  --> libtiff5-dev package exists.
|  --> libuninameslist-dev package exists.
|  --> libxml2-dev package exists.
|  --> zlib1g-dev package exists.
| make: *** [debian/rules:63: debian/stamp-local-shlibs-libfontforge] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

See
https://buildd.debian.org/status/fetch.php?pkg=fontforge=amd64=1%3A20170731%7Edfsg-1%2Bb2=1567253536=0
for the full log.

Cheers
-- 
Sebastian Ramacher

Bug#935345: microbegps: Qt4 removal from Bullseye

[Andreas Tille]

On Fri, Sep 06, 2019 at 04:21:10PM +0300, Dmitry Shachnev wrote:
> > AttributeError: 'GPSAnalyzer' object has no attribute 'sgroups'
> 
> self.sgroups is set in visualize() method.
> 
> So maybe it works only when you actually have some data? E.g. if you open
> a file and then save it, it should work.
> 
> Anyway, it does not look like a regression from Python 3 or Qt 5 port.

I'll try to find some users if not I'll upload in the middle of next
week and trust that users will send a bug report.

Thanks a lot for your quick help

   Andreas.

-- 
http://fam-tille.de

Bug#939580: liquidsoap: FTBFS with new ffmpeg ocaml library

[Gianfranco Costamagna]

Source: liquidsoap
Version: 1.3.7-1
Severity: serious


Hello, looks like the new ffmpeg library changes something and now testsuite 
fails...

Can you please have a look?

snip of build log:
OCAMLOPT -c decoder/raw_audio_decoder.ml
OCAMLOPT -c decoder/ffmpeg_decoder.ml
File "decoder/ffmpeg_decoder.ml", line 121, characters 8-20:
Error: This pattern matches values of type [? `Frame of 'a ]
   but a pattern was expected which matches values of type
 FFmpeg.Avutil.audio FFmpeg.Avutil.frame
make[4]: *** [../Makefile.rules:197: decoder/ffmpeg_decoder.cmx] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [../Makefile.rules:67: all-auto-ocaml-prog] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile.rules:27: all-subdirs] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build] Error 2


build log here:
http://debomatic-amd64.debian.net/distribution#unstable/liquidsoap/1.3.7-2/buildlog

thanks

Gianfranco

Bug#935345: microbegps: Qt4 removal from Bullseye

[Dmitry Shachnev]

On Fri, Sep 06, 2019 at 03:05:44PM +0200, Andreas Tille wrote:
> Program starts now and I can use every menu item with exception of "File / 
> Save".
> Then I get:
>
> $ LC_ALL=C MicrobeGPS 
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
> QObject::connect: Cannot queue arguments of type 'QTextCursor'
> (Make sure 'QTextCursor' is registered using qRegisterMetaType().)
> Exception in thread Thread-1:
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
> self.run()
>   File "/usr/lib/python3.5/threading.py", line 862, in run
> self._target(*self._args, **self._kwargs)
>   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1627, in 
> savethisfile
> s_data = {'candidates':self.sgroups,
> AttributeError: 'GPSAnalyzer' object has no attribute 'sgroups'

self.sgroups is set in visualize() method.

So maybe it works only when you actually have some data? E.g. if you open
a file and then save it, it should work.

Anyway, it does not look like a regression from Python 3 or Qt 5 port.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: notfixed 830807 in 6.1.2-5, tagging 875212, notfound 875212 in 3.0.4-1 ..., fixed 878854 in 1.3-2 ...

[Debian Bug Tracking System]

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

> # unconfuse bts - found and fixed in the same version
> notfixed 830807 6.1.2-5
Bug #830807 {Done: "Gudjon I. Gudjonsson" } [src:qwt] qwt: 
Prepare a jessie-backports upload
No longer marked as fixed in versions 6.1.2-5.
> tags 875212 + sid
Bug #875212 {Done: Moritz Mühlenhoff } [src:swift-im] 
[swift-im] Future Qt4 removal from Buster
Added tag(s) sid.
> notfound 875212 3.0.4-1
Bug #875212 {Done: Moritz Mühlenhoff } [src:swift-im] 
[swift-im] Future Qt4 removal from Buster
No longer marked as found in versions swift-im/3.0.4-1.
> notfixed 930598 1.34.2+dfsg1-1
Bug #930598 {Done: Ximin Luo } [src:rustc] rustc: Please 
backport upstream patch to fix ABI breakage on sparc64
No longer marked as fixed in versions 1.34.2+dfsg1-1.
> notfound 936203 0.8.1-2
Bug #936203 {Done: Sandro Tosi } [src:betamax] betamax: 
Python2 removal in sid/bullseye
No longer marked as found in versions betamax/0.8.1-2.
> notfound 936204 3.6.0.0-2
Bug #936204 {Done: Sandro Tosi } [src:billiard] billiard: 
Python2 removal in sid/bullseye
No longer marked as found in versions billiard/3.6.0.0-2.
> notfound 936411 1.7.0-2
Bug #936411 {Done: Sandro Tosi } [src:django-ajax-selects] 
django-ajax-selects: Python2 removal in sid/bullseye
No longer marked as found in versions django-ajax-selects/1.7.0-2.
> notfound 936417 1.4.6-2.1
Bug #936417 {Done: Sandro Tosi } [src:django-nose] 
django-nose: Python2 removal in sid/bullseye
No longer marked as found in versions django-nose/1.4.6-2.1.
> notfound 936461 0.2.5-2
Bug #936461 {Done: Sandro Tosi } [src:easyprocess] 
easyprocess: Python2 removal in sid/bullseye
No longer marked as found in versions easyprocess/0.2.5-2.
> notfound 936494 0.10.5-3
Bug #936494 {Done: Sandro Tosi } [src:exam] exam: Python2 
removal in sid/bullseye
No longer marked as found in versions exam/0.10.5-3.
> notfound 936712 1.3.0-2
Bug #936712 {Done: Sandro Tosi } [src:httmock] httmock: 
Python2 removal in sid/bullseye
No longer marked as found in versions httmock/1.3.0-2.
> notfound 936807 4.2.1-4
Bug #936807 {Done: Sandro Tosi } [src:kombu] kombu: Python2 
removal in sid/bullseye
No longer marked as found in versions kombu/4.2.1-4.
> notfound 936826 1.3.1-2
Bug #936826 {Done: Sandro Tosi } [src:lazy-object-proxy] 
lazy-object-proxy: Python2 removal in sid/bullseye
No longer marked as found in versions lazy-object-proxy/1.3.1-2.
> notfound 936965 1.4.3-2
Bug #936965 {Done: Sandro Tosi } [src:logilab-common] 
logilab-common: Python2 removal in sid/bullseye
No longer marked as found in versions logilab-common/1.4.3-2.
> notfound 938813 1:0.39+20181101-1
Bug #938813 {Done: Sandro Tosi } [src:webpy] webpy: Python2 
removal in sid/bullseye
No longer marked as found in versions webpy/1:0.39+20181101-1.
> reassign 878854 src:raspell 1.3-1
Bug #878854 {Done: Cédric Boutillier } 
[libraspell-ruby,libraspell-ruby1.8,libraspell-ruby1.9.1] please drop 
transitional packages libraspell-ruby, libraspell-ruby1.8 and 
libraspell-ruby1.9.1
Bug reassigned from package 
'libraspell-ruby,libraspell-ruby1.8,libraspell-ruby1.9.1' to 'src:raspell'.
No longer marked as found in versions 1.3-1.
No longer marked as fixed in versions raspell/1.3-2.
Bug #878854 {Done: Cédric Boutillier } [src:raspell] please 
drop transitional packages libraspell-ruby, libraspell-ruby1.8 and 
libraspell-ruby1.9.1
Marked as found in versions raspell/1.3-1.
> fixed 878854 1.3-2
Bug #878854 {Done: Cédric Boutillier } [src:raspell] please 
drop transitional packages libraspell-ruby, libraspell-ruby1.8 and 
libraspell-ruby1.9.1
Marked as fixed in versions raspell/1.3-2.
> reassign 913756 libgranite5 5.2.3-1
Bug #913756 {Done: Boyuan Yang } [libgranite5,tootle] tootle: 
Tootle window opens and closes immediately
Bug reassigned from package 'libgranite5,tootle' to 'libgranite5'.
No longer marked as found in versions granite/5.2.3-1 and tootle/0.2.0-1.
No longer marked as fixed in versions granite/5.2.4-1.
Bug #913756 {Done: Boyuan Yang } [libgranite5] tootle: Tootle 
window opens and closes immediately
Marked as found in versions granite/5.2.3-1.
> fixed 913756 5.2.4-1
Bug #913756 {Done: Boyuan Yang } [libgranite5] tootle: Tootle 
window opens and closes immediately
Marked as fixed in versions granite/5.2.4-1.
> affects 913756 + tootle
Bug #913756 {Done: Boyuan Yang } [libgranite5] tootle: Tootle 
window opens and closes immediately
Added indication that 913756 affects tootle
> tags 913756 + sid
Bug #913756 {Done: Boyuan Yang } [libgranite5] tootle: Tootle 
window opens and closes immediately
Added tag(s) sid.
> notfound 938778 1.1.4+dfsg-3
Bug #938778 {Done: Sandro Tosi } [src:vine] vine: Python2 
removal in sid/bullseye
No longer marked as found in versions vine/1.1.4+dfsg-3.
> notfound 938773 1.9.1-4
Bug #938773 {Done: Benjamin Drung } 
[src:versiontools] versiontools: Python2 removal in sid/bullseye
No longer marked as found in versions versiontools/1.9.1-4.
> notfound 938761 0.7-5
Bug #938761 {Done: Sandro Tosi } 

Bug#935345: microbegps: Qt4 removal from Bullseye

[Andreas Tille]

On Fri, Sep 06, 2019 at 03:40:18PM +0300, Dmitry Shachnev wrote:
> That is because resource_stream() returns stream in binary mode, not text:
> 
> https://setuptools.readthedocs.io/en/latest/pkg_resources.html#basic-resource-access
> 
> Try adding .decode('utf-8'):
> 
>   fields = line.decode('utf-8').rstrip('\t|\n').split('\t|\t')
> 
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1573, in run
> > self.failed.emit('Error loading NCBI 
> > taxonomy!Message: '+e.message+'')
> > AttributeError: 'TypeError' object has no attribute 'message'
> 
> Use str(e) instead of e.message.

Program starts now and I can use every menu item with exception of "File / 
Save".
Then I get:

$ LC_ALL=C MicrobeGPS 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
QObject::connect: Cannot queue arguments of type 'QTextCursor'
(Make sure 'QTextCursor' is registered using qRegisterMetaType().)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1627, in 
savethisfile
s_data = {'candidates':self.sgroups,
AttributeError: 'GPSAnalyzer' object has no attribute 'sgroups'


Thanks a lot for your help in any case

   Andreas.

-- 
http://fam-tille.de

Bug#935345: microbegps: Qt4 removal from Bullseye

[Dmitry Shachnev]

On Fri, Sep 06, 2019 at 02:30:25PM +0200, Andreas Tille wrote:
> Now I see at least a flash of a window before I get:
>
> $ MicrobeGPS 
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1571, in run
> nodes,ranks = 
> taxonomy.parse_nodes_dmp(pkg_resources.resource_stream('microbegps','data/taxonomy/nodes.dmp'))
>   File "/usr/lib/python3/dist-packages/microbegps/taxonomy.py", line 15, in 
> parse_nodes_dmp
> fields = line.rstrip('\t|\n').split('\t|\t')
> TypeError: a bytes-like object is required, not 'str'

That is because resource_stream() returns stream in binary mode, not text:

https://setuptools.readthedocs.io/en/latest/pkg_resources.html#basic-resource-access

Try adding .decode('utf-8'):

  fields = line.decode('utf-8').rstrip('\t|\n').split('\t|\t')

> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1573, in run
> self.failed.emit('Error loading NCBI 
> taxonomy!Message: '+e.message+'')
> AttributeError: 'TypeError' object has no attribute 'message'

Use str(e) instead of e.message.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#939569: icingaweb2-module-statusmap: Incomplete debian/copyright?

[Chris Lamb]

Source: icingaweb2-module-statusmap
Version: 20160720-1
Severity: serious
Justication: Policy ยง 12.5
X-Debbugs-CC: David Kunz , ftpmas...@debian.org

Hi,

I just ACCEPTed icingaweb2-module-statusmap from NEW but noticed it 
was missing attribution in debian/copyright for at least Jorik Tangelder,
Robert Kieffer and Andrei Mackenzie.

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#939568: icingaweb2-module-graphite: Incomplete debian/copyright?

[Chris Lamb]

Source: icingaweb2-module-graphite
Version: 1.1.0-1
Severity: serious
Justication: Policy ยง12.5
X-Debbugs-CC: David Kunz , ftpmas...@debian.org

Hi,

I just ACCEPTed icingaweb2-module-graphite from NEW but noticed it 
was missing attribution in debian/copyright for at least library/vendor.

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#935345: microbegps: Qt4 removal from Bullseye

[Andreas Tille]

Hi Dmitry,

On Fri, Sep 06, 2019 at 02:28:48PM +0300, Dmitry Shachnev wrote:
> On Fri, Sep 06, 2019 at 01:18:33PM +0200, Andreas Tille wrote:
> > since upstream is currently inactive I tried my best to do the
> > porting of this package in Git[1].  The Python3 port went quite
> > smoothly and I have the feeling I made quite some progress with
> > Qt5 port.  However, when I build HEAD from the packaging Git[1]
> > install the package and try to start the binary I get:
> >
> > [...]
> >   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1005, in 
> > initUI
> > self.treeView.header().setClickable(True)
> > AttributeError: 'QHeaderView' object has no attribute 'setClickable'
> 
> As the next line connects to sectionClicked signal, I think the code author
> meant setSectionsClickable() here too.
> 
> https://doc.qt.io/qt-5/qheaderview.html#setSectionsClickable

Now I see at least a flash of a window before I get:


$ MicrobeGPS 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1571, in run
nodes,ranks = 
taxonomy.parse_nodes_dmp(pkg_resources.resource_stream('microbegps','data/taxonomy/nodes.dmp'))
  File "/usr/lib/python3/dist-packages/microbegps/taxonomy.py", line 15, in 
parse_nodes_dmp
fields = line.rstrip('\t|\n').split('\t|\t')
TypeError: a bytes-like object is required, not 'str'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1573, in run
self.failed.emit('Error loading NCBI 
taxonomy!Message: '+e.message+'')
AttributeError: 'TypeError' object has no attribute 'message'


... but h, this looks like a Python2 - Python3 conversion issue
rather than a Qt4 - Qt5 conversion problem.  If there is no other clue
from the Qt-experts I might redirect my question to debian-python list
...

Kind regards and thanks for your patience

   Andreas.

-- 
http://fam-tille.de

Processed: tagging 935550, found 939502 in 0.3.4-8, tagging 935563, tagging 935353, tagging 939489 ...

[Debian Bug Tracking System]

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

> tags 935550 + sid bullseye
Bug #935550 [src:yubioath-desktop] yubioath-desktop: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> found 939502 0.3.4-8
Bug #939502 [src:haskell-attoparsec-enumerator] haskell-attoparsec-enumerator: 
Removal notice: unused Haskell library
Marked as found in versions haskell-attoparsec-enumerator/0.3.4-8.
> tags 935563 + sid bullseye
Bug #935563 {Done: Ole Streicher } [python3-sunpy] astropy 
3.2.1 breaks sunpy
Added tag(s) sid and bullseye.
> tags 935353 + sid bullseye
Bug #935353 [src:vistrails] vistrails: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> tags 939489 + sid bullseye
Bug #939489 [bumblebee-nvidia] bumblebee fails to disable discrete graphics 
card after upgrade nvidia driver to 430.40-2
Added tag(s) sid and bullseye.
> tags 937448 + experimental
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 931943 + sid bullseye
Bug #931943 {Done: Gert Wollny } [src:vtk6] vtk6: FTBFS with 
PROJ 6
Added tag(s) sid and bullseye.
> tags 939303 + sid bullseye
Bug #939303 [src:matplotlib2] matplotlib2: FTBFS unsatisfied b-d on python-pyshp
Added tag(s) sid and bullseye.
> tags 925794 + experimental
Bug #925794 {Done: Bernd Zeimetz } [src:open-vm-tools] 
open-vm-tools: ftbfs with GCC-9
Added tag(s) experimental.
> tags 935341 + sid bullseye
Bug #935341 [src:backintime] backintime-qt4: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> tags 935346 + sid bullseye
Bug #935346 [src:puddletag] puddletag: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> tags 935349 + sid bullseye
Bug #935349 [src:python-pyface] python-pyface: Qt4 removal from Bullseye
Added tag(s) bullseye and sid.
> tags 935352 + sid bullseye
Bug #935352 [src:trimage] trimage: Qt4 removal from Bullseye
Added tag(s) bullseye and sid.
> tags 935354 + sid bullseye
Bug #935354 [src:vitables] vitables: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> tags 939399 + sid
Bug #939399 {Done: Bas Couwenberg } [src:libgeotiff] 
libgeotiff FTBFS in bullseye (possiblly armhf specific), test discrepancies.
Added tag(s) sid.
> tags 939492 + sid bullseye
Bug #939492 [src:nbsphinx] nbsphinx: testsuite failures with new pandoc
Added tag(s) bullseye and sid.
> found 935211 0.36.0-1
Bug #935211 [python-acme] python-acme: Please port to Python 3 and/or drop 
Python 2 package
Marked as found in versions python-acme/0.36.0-1.
> tags 875050 + sid
Bug #875050 {Done: Moritz Muehlenhoff } [src:mustang-plug] 
[mustang-plug] Future Qt4 removal from Buster
Added tag(s) sid.
> found 939529 0.3.1-4
Bug #939529 [src:gtg] gtg: should this package be removed?
Marked as found in versions gtg/0.3.1-4.
> tags 939529 + sid bullseye
Bug #939529 [src:gtg] gtg: should this package be removed?
Added tag(s) sid and bullseye.
> found 939531 1.2.0-3
Bug #939531 [src:medit] medit: should this package be removed?
Marked as found in versions medit/1.2.0-3.
> tags 939531 + sid bullseye
Bug #939531 [src:medit] medit: should this package be removed?
Added tag(s) bullseye and sid.
> tags 934079 + sid
Bug #934079 {Done: Bastien Roucariès } [acorn] FTBFS: build 
depends on older node-unicode-*
Added tag(s) sid.
> tags 935345 + sid bullseye
Bug #935345 [src:microbegps] microbegps: Qt4 removal from Bullseye
Added tag(s) sid and bullseye.
> tags 936016 - buster
Bug #936016 {Done: "Alf Gaida" } [meteo-qt] meteo-qt 
crashes immediately
Removed tag(s) buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
875050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875050
925794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925794
931943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931943
934079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934079
935211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935211
935341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935341
935345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935345
935346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935346
935349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935349
935352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935352
935353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935353
935354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935354
935550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935550
935563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935563
936016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936016
937448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937448
939303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939303
939399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939399
939489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939489
939492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939492
939502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939502
939529: 

Processed: reassign 939527 to src:vcdimager, severity of 939527 is serious

[Debian Bug Tracking System]

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

> reassign 939527 src:vcdimager 0.7.24+dfsg-0.2
Bug #939527 [src:vcdimager] vcdimager contains one file with different license
Ignoring request to reassign bug #939527 to the same package
Bug #939527 [src:vcdimager] vcdimager contains one file with different license
Ignoring request to alter found versions of bug #939527 to the same values 
previously set
> # looks like a d/copyright issue, so RC
> severity 939527 serious
Bug #939527 [src:vcdimager] vcdimager contains one file with different license
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#935345: microbegps: Qt4 removal from Bullseye

[Dmitry Shachnev]

Hi Andreas,

On Fri, Sep 06, 2019 at 01:18:33PM +0200, Andreas Tille wrote:
> since upstream is currently inactive I tried my best to do the
> porting of this package in Git[1].  The Python3 port went quite
> smoothly and I have the feeling I made quite some progress with
> Qt5 port.  However, when I build HEAD from the packaging Git[1]
> install the package and try to start the binary I get:
>
> [...]
>   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1005, in 
> initUI
> self.treeView.header().setClickable(True)
> AttributeError: 'QHeaderView' object has no attribute 'setClickable'

As the next line connects to sectionClicked signal, I think the code author
meant setSectionsClickable() here too.

https://doc.qt.io/qt-5/qheaderview.html#setSectionsClickable

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#934079: marked as done (FTBFS: build depends on older node-unicode-*)

[Debian Bug Tracking System]

Your message dated Fri, 06 Sep 2019 11:22:16 +
with message-id 
and subject line Bug#934079: fixed in acorn 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3
has caused the Debian Bug report #934079,
regarding FTBFS: build depends on older node-unicode-*
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.)


-- 
934079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acorn
Version: 6.1.1+ds+~0.3.1+~4.0.0+~1.0.0+~5.0.1+ds+~1.6.2+ds-1
Severity: serious

Hi,

acorn build-depends on node-unicode-11.0.0 which is not available
anymore in the archive, as of buster it's node-unicode-12.0.0 (and
node-unicode-12.1.0 in current bullseye).

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: acorn
Source-Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3

We believe that the bug you reported is fixed in the latest version of
acorn, 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.
Bastien Roucariès  (supplier of updated acorn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Sep 2019 12:37:01 +0200
Source: acorn
Architecture: source
Version: 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Closes: 934079
Changes:
 acorn 
(6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3)
 experimental; urgency=medium
 .
   * Bug fix: "build depends on older node-unicode-*", thanks to
 daniel.baum...@progress-linux.org; (Closes: #934079). Depends
 on newly introduced node-unicode-lastest
Checksums-Sha1:
 23ffc503b76f048929fdb66ba72120178416c80a 9900 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.dsc
 b3b460a84834f5ba5506fe23f86e39740701a6a4 15604 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.debian.tar.xz
 5f75db4dd0ea49b8b99f490573e1f2b3ebc0647d 16960 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3_source.buildinfo
Checksums-Sha256:
 6dbd867ee15b61efb1f2a371b0fc2aa797987a3bfe376cfd70f036f321cb4551 9900 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.dsc
 d692f77e546e5eceb00659e0a076277984d0fa3b4622d1e4e84aa23677fb4662 15604 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.debian.tar.xz
 9b96b23c1581f46841037de9b5902bd153dd7566af01470f3bcee2b048a08189 16960 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3_source.buildinfo
Files:
 9f46d29fa28a95944babcc3595ae67d2 9900 javascript optional 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.dsc
 6982110d26b54dabf67179723fa91884 15604 javascript optional 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3.debian.tar.xz
 c6315ca019b7942fd150a64924dadc2e 16960 javascript optional 
acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAl1yNzgACgkQADoaLapB
CF+7pQ/9F2JQUJUmpV31v/R5s8r1qDWozX/b1pfh06/fn1uYSJUE+YbnpgbMKOVw
2mb5KYow/VpxtAa8ai3XKrtW2JustwRNs/Z0HjXyaG7+64nhSeWA6+Rgi9hcaZPE
R0ns5MMxTJDCrU0Yri4LgkOXyDSoABTmxEY+bxA6Wkv5Nu9rQOPHqXoR6IrJHP+x
LDoSfjbKBK8oll8WGKLulG5veMNaDBLvwCmV+U51m3EIWYwfgz+K98jifRgTqrkX
R0C7vGumHRVViC7x2xNm2FSwpiIWwuPNR6uEbQTDoq7XiDhisVHWGmqx8Xl6In1t
wySkcYX48me5H6Ggea0mOprFYmKU2tGniI0CpaIOUB8O+qMjCkI2expOJBOu+yGt

Bug#935345: microbegps: Qt4 removal from Bullseye

[Andreas Tille]

Control: tags -1 help

Hi,

since upstream is currently inactive I tried my best to do the
porting of this package in Git[1].  The Python3 port went quite
smoothly and I have the feeling I made quite some progress with
Qt5 port.  However, when I build HEAD from the packaging Git[1]
install the package and try to start the binary I get:

$ MicrobeGPS 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
  File "/usr/bin/MicrobeGPS", line 11, in 
load_entry_point('MicrobeGPS==1.0.0', 'console_scripts', 'MicrobeGPS')()
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1738, in main
GPSAnalyzer() 
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 877, in __init__
self.initUI()
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1005, in initUI
self.treeView.header().setClickable(True)
AttributeError: 'QHeaderView' object has no attribute 'setClickable'


For the keyword 'setClickable' my web searches remained unsuccessful.
Is there any hint how to fix this?

Kind regards

   Andreas.


[1] https://salsa.debian.org/med-team/microbegps

-- 
http://fam-tille.de

Processed: Re: Bug#935345: microbegps: Qt4 removal from Bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #935345 [src:microbegps] microbegps: Qt4 removal from Bullseye
Added tag(s) help.

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

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

[Eric Maeker]

Hello Andreas

I'm totally overbooked by my work. I have a pending update to v1.1.0, but
no time to finish the job for now.
I'll try to find some free time.

Thanks
Eric


Le ven. 6 sept. 2019 à 11:41, Andreas Tille  a écrit :

> Hi,
>
> thanks to a patch by Michael Crusoe I'm a bit further now but there are
> remaining errors.  I have no idea about C++/Qt and thus need to ask for
> help.  Eric, are you up to safe your package inside Debian?
>
> ...
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/freemedforms-project-1.0.0=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DFREEMEDFORMS -
>  DDRUGS_DATABASE_VERSION=0x000804 -DWITH_EPISODE_REMOVAL
> -DWITH_CHEQUE_PRINTING -DWITH_FRENCH_FSP -DWITH_FRENCH_HPRIM_INTEGRATOR
> -DFULLAPPLICATION_BUILD -DBINARY_NAME="\"DataPackUtils\"" -
>  DBUILD_PATH_POSTFIXE="\"FreeMedForms\""
> -DPACKAGE_VERSION="\"1.0.0\""
> -DSOURCES_ROOT_PATH="\"/build/freemedforms-project-1.0.0\""
> -DLINUX_INTEGRATED -DLINUX_QT_PATH="\"/usr/lib/x86_64-linux-gnu\"" -
>   DLINUX_QT_PLUGINS_PATH="\"/usr/lib/x86_64-linux-gnu/qt5/plugins\""
> -DLIBRARY_BASENAME="\"lib/x86_64-linux-gnu\""
> -DLINUX_PLUGIN_PATH="\"/usr//lib/x86_64-linux-gnu/DataPackUtils\""
> -DGIT_REVISION_HASH="\"DEBR1.0. 0-1\"" -DQT_NO_CAST_TO_ASCII
> -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DRELEASE
> -DQT_DISABLE_DEPRECATED_BEFORE=0x040900 -DDATAPACKUTILS_LIBRARY
> -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -   DQT_WIDGETS_LIB
> -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_NETWORK_LIB
> -DQT_CORE_LIB -I. -I/build/freemedforms-project-1.0.0/plugins
> -I/build/freemedforms-project-1.0.0/libs -I/build/
> freemedforms-project-1.0.0/contrib
> -I/build/freemedforms-project-1.0.0/contrib/quazip -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem /usr/include/x86_64-
>  linux-gnu/qt5/QtPrintSupport -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem /usr/include/
>  x86_64-linux-gnu/qt5/QtSql -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I/build/freemedforms-project-1.
> 0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.moc -isystem
> /usr/include/libdrm
> -I/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/.ui
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o
> /build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.obj/unix/packservercreator.o
> servercreation/packservercreator.cpp
> servercreation/servercreationwidget.cpp: In member function 'void
> DataPack::Internal::ServerCreationWidgetPrivate::createActions()':
> servercreation/servercreationwidget.cpp:97:39: error: invalid use of
> incomplete type 'class QAction'
>97 | aGroupByServer = new QAction(q);
>   |   ^
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
>  from servercreation/servercreationwidget.h:18,
>  from servercreation/servercreationwidget.cpp:28:
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward
> declaration of 'class QAction'
>68 | class QAction;
>   |   ^~~
> servercreation/servercreationwidget.cpp:98:38: error: invalid use of
> incomplete type 'class QAction'
>98 | aGroupByQueue = new QAction(q);
>   |  ^
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
>  from servercreation/servercreationwidget.h:18,
>  from servercreation/servercreationwidget.cpp:28:
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward
> declaration of 'class QAction'
>68 | class QAction;
>   |   ^~~
> servercreation/servercreationwidget.cpp: In member function 'void
> DataPack::ServerCreationWidget::retranslate()':
> servercreation/servercreationwidget.cpp:258:22: error: invalid use of
> incomplete type 'class QAction'
>   258 | d->aGroupByServer->setText(tr("Group by server"));
>   |  ^~
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
>  from servercreation/servercreationwidget.h:18,
>  from servercreation/servercreationwidget.cpp:28:
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward
> declaration of 'class QAction'
>68 | class QAction;
>   |   ^~~
> servercreation/servercreationwidget.cpp:259:21: error: invalid use of
> incomplete type 'class QAction'
>   259 | d->aGroupByQueue->setText(tr("Group by queue"));
>   | ^~
> In file included from
> 

Bug#939561: soapybladerf ftbfs in unstable

[Matthias Klose]

Package: src:soapybladerf
Version: 0.3.5-1
Severity: serious
Tags: sid bullseye

soapybladerf ftbfs in unstable:

/usr/bin/c++  -DHAS_BLADERF_GAIN_MODE -DbladeRFSupport_EXPORTS 
-I/<>  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -std=c++11 -fPIC 
-Wno-unused-parameter -Wall -Wextra -fvisibility=hidden -std=gnu++11 -o 
CMakeFiles/bladeRFSupport.dir/bladeRF_Streaming.cpp.o -c 
/<>/bladeRF_Streaming.cpp
/<>/bladeRF_Streaming.cpp: In member function ‘virtual 
SoapySDR::Stream* bladeRF_SoapySDR::setupStream(int, const string&, const 
std::vector&, const Kwargs&)’:
/<>/bladeRF_Streaming.cpp:125:17: error: invalid conversion from 
‘bladerf_module’ {aka ‘int’} to ‘bladerf_channel_layout’ [-fpermissive]

  125 | _dir2mod(direction),
  | ^~~
  | |
  | bladerf_module {aka int}
In file included from /<>/bladeRF_SoapySDR.hpp:26,
 from /<>/bladeRF_Streaming.cpp:22:
/usr/include/libbladeRF.h:2555:58: note:   initializing argument 2 of ‘int 
bladerf_sync_config(bladerf*, bladerf_channel_layout, bladerf_format, unsigned 
int, unsigned int, unsigned int, unsigned int)’

 2555 |   bladerf_channel_layout layout,
  |   ~~~^~
/<>/bladeRF_Streaming.cpp: In member function ‘virtual int 
bladeRF_SoapySDR::writeStream(SoapySDR::Stream*, const void* const*, size_t, 
int&, long long int, long int)’:
/<>/bladeRF_Streaming.cpp:387:41: error: invalid conversion from 
‘bladerf_channel’ {aka ‘int’} to ‘bladerf_direction’ [-fpermissive]

  387 | bladerf_get_timestamp(_dev, BLADERF_MODULE_TX, 
);
  | ^
  | |
  | bladerf_channel {aka int}
/usr/include/libbladeRF.h:2481:55: note:   initializing argument 2 of ‘int 
bladerf_get_timestamp(bladerf*, bladerf_direction, bladerf_timestamp*)’

 2481 | bladerf_direction dir,
  | ~~^~~
/<>/bladeRF_Settings.cpp: In member function ‘virtual double 
bladeRF_SoapySDR::getFrequency(int, size_t, const string&) const’:
/<>/bladeRF_Settings.cpp:411:64: error: cannot convert ‘unsigned 
int*’ to ‘bladerf_frequency*’ {aka ‘long unsigned int*’}

  411 | int ret = bladerf_get_frequency(_dev, _dir2mod(direction), );
  |^
  ||
  |unsigned 
int*

In file included from /<>/bladeRF_SoapySDR.hpp:26,
 from /<>/bladeRF_Settings.cpp:22:
/usr/include/libbladeRF.h:1277:56: note:   initializing argument 3 of ‘int 
bladerf_get_frequency(bladerf*, bladerf_channel, bladerf_frequency*)’

 1277 | bladerf_frequency *frequency);
  | ~~~^
/<>/bladeRF_Settings.cpp: In member function ‘virtual long long int 
bladeRF_SoapySDR::getHardwareTime(const string&) const’:
/<>/bladeRF_Settings.cpp:570:49: error: invalid conversion from 
‘bladerf_channel’ {aka ‘int’} to ‘bladerf_direction’ [-fpermissive]
  570 | const int ret = bladerf_get_timestamp(_dev, BLADERF_MODULE_RX, 
);

  | ^
  | |
  | bladerf_channel {aka 
int}
/usr/include/libbladeRF.h:2481:55: note:   initializing argument 2 of ‘int 
bladerf_get_timestamp(bladerf*, bladerf_direction, bladerf_timestamp*)’

 2481 | bladerf_direction dir,
  | ~~^~~
/<>/bladeRF_Settings.cpp: In member function ‘virtual void 
bladeRF_SoapySDR::writeSetting(const string&, const string&)’:
/<>/bladeRF_Settings.cpp:823:50: error: ‘bladerf_module’ is not a 
class, namespace, or enumeration
  823 | bladerf_xb200_set_path(_dev, 
bladerf_module::BLADERF_MODULE_RX, bladerf_xb200_path::BLADERF_XB200_BYPASS);

  |  ^~
In file included from /<>/bladeRF_SoapySDR.hpp:26,
 from /<>/bladeRF_Settings.cpp:22:
/<>/bladeRF_Settings.cpp:823:66: error: expected unqualified-id 
before ‘(’ token
  823 | bladerf_xb200_set_path(_dev, 
bladerf_module::BLADERF_MODULE_RX, bladerf_xb200_path::BLADERF_XB200_BYPASS);
  | 
^
/<>/bladeRF_Settings.cpp:823:66: error: expected primary-expression 
before ‘)’ token
  823 | bladerf_xb200_set_path(_dev, 

Processed: Re: Bug#939558: System powers off or crashes when asking "suspend to ram" via GUI

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 5.2.9-2
Bug #939558 [linux-image] System powers off or crashes when asking "suspend to 
ram" via GUI
Warning: Unknown package 'linux-image'
Bug reassigned from package 'linux-image' to 'src:linux'.
No longer marked as found in versions 4.19.0-5-amd64.
Ignoring request to alter fixed versions of bug #939558 to the same values 
previously set
Bug #939558 [src:linux] System powers off or crashes when asking "suspend to 
ram" via GUI
Marked as found in versions linux/5.2.9-2.
> severity -1 serious
Bug #939558 [src:linux] System powers off or crashes when asking "suspend to 
ram" via GUI
Severity set to 'serious' from 'normal'

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

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

[Andreas Tille]

Hi,

thanks to a patch by Michael Crusoe I'm a bit further now but there are
remaining errors.  I have no idea about C++/Qt and thus need to ask for
help.  Eric, are you up to safe your package inside Debian?

...
g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/freemedforms-project-1.0.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DFREEMEDFORMS -   
DDRUGS_DATABASE_VERSION=0x000804 -DWITH_EPISODE_REMOVAL -DWITH_CHEQUE_PRINTING 
-DWITH_FRENCH_FSP -DWITH_FRENCH_HPRIM_INTEGRATOR -DFULLAPPLICATION_BUILD 
-DBINARY_NAME="\"DataPackUtils\"" - 
DBUILD_PATH_POSTFIXE="\"FreeMedForms\"" -DPACKAGE_VERSION="\"1.0.0\"" 
-DSOURCES_ROOT_PATH="\"/build/freemedforms-project-1.0.0\"" -DLINUX_INTEGRATED 
-DLINUX_QT_PATH="\"/usr/lib/x86_64-linux-gnu\"" -  
DLINUX_QT_PLUGINS_PATH="\"/usr/lib/x86_64-linux-gnu/qt5/plugins\"" 
-DLIBRARY_BASENAME="\"lib/x86_64-linux-gnu\"" 
-DLINUX_PLUGIN_PATH="\"/usr//lib/x86_64-linux-gnu/DataPackUtils\"" 
-DGIT_REVISION_HASH="\"DEBR1.0. 0-1\"" -DQT_NO_CAST_TO_ASCII 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DRELEASE 
-DQT_DISABLE_DEPRECATED_BEFORE=0x040900 -DDATAPACKUTILS_LIBRARY -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -   DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB 
-I. -I/build/freemedforms-project-1.0.0/plugins 
-I/build/freemedforms-project-1.0.0/libs -I/build/
freemedforms-project-1.0.0/contrib 
-I/build/freemedforms-project-1.0.0/contrib/quazip -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem /usr/include/x86_64- 
linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem /usr/include/   
x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I/build/freemedforms-project-1. 
0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.moc -isystem 
/usr/include/libdrm 
-I/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/.ui 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.obj/unix/packservercreator.o
 servercreation/packservercreator.cpp
servercreation/servercreationwidget.cpp: In member function 'void 
DataPack::Internal::ServerCreationWidgetPrivate::createActions()':
servercreation/servercreationwidget.cpp:97:39: error: invalid use of incomplete 
type 'class QAction'
   97 | aGroupByServer = new QAction(q);
  |   ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
 from servercreation/servercreationwidget.h:18,
 from servercreation/servercreationwidget.cpp:28:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
declaration of 'class QAction'
   68 | class QAction;
  |   ^~~
servercreation/servercreationwidget.cpp:98:38: error: invalid use of incomplete 
type 'class QAction'
   98 | aGroupByQueue = new QAction(q);
  |  ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
 from servercreation/servercreationwidget.h:18,
 from servercreation/servercreationwidget.cpp:28:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
declaration of 'class QAction'
   68 | class QAction;
  |   ^~~
servercreation/servercreationwidget.cpp: In member function 'void 
DataPack::ServerCreationWidget::retranslate()':
servercreation/servercreationwidget.cpp:258:22: error: invalid use of 
incomplete type 'class QAction'
  258 | d->aGroupByServer->setText(tr("Group by server"));
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
 from servercreation/servercreationwidget.h:18,
 from servercreation/servercreationwidget.cpp:28:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
declaration of 'class QAction'
   68 | class QAction;
  |   ^~~
servercreation/servercreationwidget.cpp:259:21: error: invalid use of 
incomplete type 'class QAction'
  259 | d->aGroupByQueue->setText(tr("Group by queue"));
  | ^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
 from servercreation/servercreationwidget.h:18,
 from servercreation/servercreationwidget.cpp:28:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
declaration of 'class QAction'
   68 | class QAction;
  |   ^~~


Kind 

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

[Jonas Smedegaard]

Quoting James R Barlow (2019-09-06 10:15:59)
> On Thu, Sep 5, 2019 at 11:57 PM Jonas Smedegaard  wrote:
> >
> > Quoting Sean Whitton (2019-09-06 06:20:47)
> > > On Sat 31 Aug 2019 at 03:58PM +02, Jonas Smedegaard wrote:
> > >
> > > > Possibly some of the other tools uses undocumented insecure 
> > > > ghostscript calls which was recently removed.
> > > >
> > > > To investigate that further, someone needs to extract the actual 
> > > > input (probably Postscript or PDF) and the exact command used to 
> > > > call ghostscript.
> > >
> > > This was indeed a problem and ocrmypdf upstream has fixed it in 
> > > the latest release.
> >
> > Ah, great that the cause has been located!
> >
> > ...and happy that my guess was correct :-)
> 
> Not quite? ocrmypdf did not use any undocumented ghostscript calls. It 
> followed an example from Ghostscript's documentation almost verbatim 
> to generate a .ps from a template that tells Ghostscript to insert an 
> ICC profile, referenced by filename. Ghostscript 9.28 is disabling 
> access to all files from a .ps file unless safety is explicitly 
> disabled. So nothing undocumented or exploitable was happening. (But 
> it does make sense for Ghostscript to make the change.)
> 
> It does mean any other software that uses Ghostscript to generate 
> PDF/X, PDF/E, or PDF/A is likely going to break as well with this 
> release.

Thanks for the clarification - helps me not spread any further false 
information!

 - Jonas

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

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


signature.asc
Description: signature

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

[James R Barlow]

On Thu, Sep 5, 2019 at 11:57 PM Jonas Smedegaard  wrote:
>
> Quoting Sean Whitton (2019-09-06 06:20:47)
> > On Sat 31 Aug 2019 at 03:58PM +02, Jonas Smedegaard wrote:
> >
> > > Possibly some of the other tools uses undocumented insecure
> > > ghostscript calls which was recently removed.
> > >
> > > To investigate that further, someone needs to extract the actual
> > > input (probably Postscript or PDF) and the exact command used to
> > > call ghostscript.
> >
> > This was indeed a problem and ocrmypdf upstream has fixed it in the
> > latest release.
>
> Ah, great that the cause has been located!
>
> ...and happy that my guess was correct :-)

Not quite? ocrmypdf did not use any undocumented ghostscript calls. It
followed an example from Ghostscript's documentation almost verbatim
to generate a .ps from a template that tells Ghostscript to insert an ICC
profile, referenced by filename. Ghostscript 9.28 is disabling access to
all files from a .ps file unless safety is explicitly disabled. So nothing
undocumented or exploitable was happening. (But it does make sense
for Ghostscript to make the change.)

It does mean any other software that uses Ghostscript to generate
PDF/X, PDF/E, or PDF/A is likely going to break as well with this
release.


> They've issued another pre-release yesterday - I hope to package that
> soon, maybe today.
>
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#924839: marked as done (sphinxcontrib-programoutput: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 6 Sep 2019 09:25:16 +0200
with message-id 
and subject line Can be closed
has caused the Debian Bug report #924839,
regarding sphinxcontrib-programoutput: FTBFS: tests failed
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.)


-- 
924839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-programoutput
Version: 0.11-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
> --with python2,python3,sphinxdoc
> dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
> binary binary-arch binary-indep build build-arch build-indep clean install 
> install-arch install-indep)
> set -e ; for i in 2.7 3.7 ; do \
>   PYTHONPATH=. PYTHON=python$i python$i setup.py test ; \
> done
> running test
> running egg_info
> writing requirements to src/sphinxcontrib_programoutput.egg-info/requires.txt
> writing src/sphinxcontrib_programoutput.egg-info/PKG-INFO
> writing namespace_packages to 
> src/sphinxcontrib_programoutput.egg-info/namespace_packages.txt
> writing top-level names to 
> src/sphinxcontrib_programoutput.egg-info/top_level.txt
> writing dependency_links to 
> src/sphinxcontrib_programoutput.egg-info/dependency_links.txt
> reading manifest file 'src/sphinxcontrib_programoutput.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/sphinxcontrib_programoutput.egg-info/SOURCES.txt'
> running build_ext
> test_execute (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... 
> ok
> test_execute_with_hidden_standard_error 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_execute_with_shell 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_from_programoutput_node 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_from_programoutput_node_extraargs 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output (sphinxcontrib.programoutput.tests.test_command.TestCommand) 
> ... ok
> test_get_output_non_zero 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output_with_hidden_standard_error 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output_with_working_directory 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_list 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_list_hashable 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_string_command 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_slice_empty (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_no_int (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_simple (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_too_many (sphinxcontrib.programoutput.tests.test_util.TestSlice) 
> ... ok
> test_init_cache (sphinxcontrib.programoutput.tests.test_setup.TestSetup) ... 
> ok
> test_command (sphinxcontrib.programoutput.tests.test_directive.TestDirective) 
> ... ERROR
> test_command_non_default_prompt 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_ellipsis_negative_stop 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_ellipsis_start_and_negative_stop 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_ellipsis_start_and_stop 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_ellipsis_stop_only 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_expansion_with_shell 
> (sphinxcontrib.programoutput.tests.test_directive.TestDirective) ... ERROR
> test_expected_non_zero_return_code 
> 

Bug#939528: marked as done (signal-desktop: Program fails to start after latest upgrade, worked fine before.)

[Debian Bug Tracking System]

Your message dated Fri, 6 Sep 2019 09:23:38 +0200
with message-id <3ad6da61-5e57-9f28-c9e4-ec9f9899e...@debian.org>
and subject line Re: signal-desktop: Program fails to start after latest 
upgrade, worked fine before.
has caused the Debian Bug report #939528,
regarding signal-desktop: Program fails to start after latest upgrade, worked 
fine before.
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.)


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

Dear Maintainer,

   * What led up to the situation?
   
running apt upgrade

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

After the recent upgrade signal-desktop refuses to start, it immediately 
terminates with the following error:

[13283:0906/015852.140508:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox 
helper binary was found, but is not configured correctly. Rather than run 
without sandboxing I'm aborting now. You need to make sure that 
/opt/Signal/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

This command fixes the problem:

sudo chmod 4755 /opt/Signal/chrome-sandbox

To make sure the error can be reproduced I ran:

apt reinstall signal-desktop

and the error re-appeared. Changing the permissions fixed the problem again.

Thank you very much for maintaining this package.

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/16 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages signal-desktop depends on:
ii  libappindicator1  0.4.92-7
ii  libasound21.1.8-1
ii  libnotify40.7.8-1
ii  libnss3   2:3.45-1
ii  libxss1   1:1.2.3-1
ii  libxtst6  2:1.2.3-1

signal-desktop recommends no packages.

signal-desktop suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 06 Sep 2019 02:06:22 +0200 Alexander  wrote:
> Package: signal-desktop
> Version: 1.27.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>
> running apt upgrade
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> After the recent upgrade signal-desktop refuses to start, it immediately 
> terminates with the following error:
> 
> [13283:0906/015852.140508:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox 
> helper binary was found, but is not configured correctly. Rather than run 
> without sandboxing I'm aborting now. You need to make sure that 
> /opt/Signal/chrome-sandbox is owned by root and has mode 4755.
> Trace/breakpoint trap
> 
> This command fixes the problem:
> 
> sudo chmod 4755 /opt/Signal/chrome-sandbox
> 
> To make sure the error can be reproduced I ran:
> 
> apt reinstall signal-desktop
> 
> and the error re-appeared. Changing the permissions fixed the problem again.
> 
> Thank you very much for maintaining this package.

This package is not maintained by Debian itself, so you'll have to
contact the upstream maintainer directly, I assume under
https://github.com/signalapp/Signal-Desktop

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



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

Bug#934599: We are a Chinese factory of fabric processing

[xu]

hiIf you are not interested in our products and services, you can 
unsubscribed
 our email and you will no longer receive similar email notifications.
[http://mc.avawebsite.com/stat/?keyid=BFEBFBFF00020655USER-20190628TO=934...@bugs.debian.org=2019-9-6%2015:14:38=We%20are%20a%20Chinese%20factory%20of%20fabric%20processing]

Bug#931255: Update in stable?

[Mike Gabriel]

Hi,

On Thu, 29 Aug 2019 15:47:19 +0200 Mathieu Parent 
 wrote:

> Le jeu. 29 août 2019 à 15:39, Christoph Haas  a écrit :
> >
> > I would like to see this simple fix in Buster. Without it the 
package is nearly unusable in my opinion. Do you think the release team 
would agree?

>
> Yes, the release team will agree.
>
> Unfortunately, I won't work on this soon.
>
> Regards
> --
> Mathieu Parent
>
>

Mathieu, if you can prepare the package according to your workflow and 
directly upload to buster, I can handle the communication with the 
release team. The change regarding #931255 is so obviously needed, that 
we can immediately upload to buster without pre-upload approval.


Will that help to speed up things?

Mike

Bug#932637: nmu now in the delayed queue

[Dominique Dumont]

On Thursday, 5 September 2019 20:45:05 CEST gregor herrmann wrote:
> What happened to this NMU?

It's in unstable 

> I just noticed that the bug ist still open and perl6-readline was
> removed from testing …

The nmu version (0.1.4-3.1) cannot go in testing because rakudo is FTBS with 
newer libuv.

I'm waiting for an upstream fix for rakudo. Probably with next release.

All the best

Dod

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

[Jonas Smedegaard]

Quoting Sean Whitton (2019-09-06 06:20:47)
> On Sat 31 Aug 2019 at 03:58PM +02, Jonas Smedegaard wrote:
> 
> > Possibly some of the other tools uses undocumented insecure 
> > ghostscript calls which was recently removed.
> >
> > To investigate that further, someone needs to extract the actual 
> > input (probably Postscript or PDF) and the exact command used to 
> > call ghostscript.
> 
> This was indeed a problem and ocrmypdf upstream has fixed it in the 
> latest release.

Ah, great that the cause has been located!

...and happy that my guess was correct :-)


> However, there are still test failures, and upstream suspects that we 
> might just need to wait on ghostscript making a full release: 
> 

They've issued another pre-release yesterday - I hope to package that 
soon, maybe today.


 - Jonas

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

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


signature.asc
Description: signature

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

[Andreas Tille]

Control: tags -1 help

Hi Moritz,

On Thu, Sep 05, 2019 at 11:26:12PM +0200, Moritz Mühlenhoff wrote:
> I've downloaded 1.0.0 and the included README.md states "FreeMedForms
> and derivatives are coded in C++ / Qt5", so I suppose the latest
> version should now support Qt5.
> 
> If that works fine, it would be great to have an upload within the next
> weeks, as we're trying to finally remove Qt4 for good.

Thanks for the ping.  Version 1.0.0 is in packaging Git since nearly two
years[1].  I updated the repository[2] to latest packaging standards and
the build runs into:


...
 Reading /build/freemedforms-project-1.0.0/contrib/quazip/quazip.pro
Info: creating stash file 
/build/freemedforms-project-1.0.0/contrib/quazip/.qmake.stash
Info: creating cache file 
/build/freemedforms-project-1.0.0/contrib/quazip/.qmake.cache
  Reading /build/freemedforms-project-1.0.0/contrib/quazip/quazip/quazip.pro
Project MESSAGE: Using system libquazip0 package
 Reading /build/freemedforms-project-1.0.0/libs/datapackutils/datapackutils.pro
Info: creating stash file 
/build/freemedforms-project-1.0.0/libs/datapackutils/.qmake.stash
Info: creating cache file 
/build/freemedforms-project-1.0.0/libs/datapackutils/.qmake.cache
Reading /build/freemedforms-project-1.0.0/freemedforms/plugins/plugins.pro
 Reading 
/build/freemedforms-project-1.0.0/plugins/fmfcoreplugin/fmfcoreplugin.pro
Info: creating stash file 
/build/freemedforms-project-1.0.0/plugins/fmfcoreplugin/.qmake.stash
Info: creating cache file 
/build/freemedforms-project-1.0.0/plugins/fmfcoreplugin/.qmake.cache
Project ERROR: Unknown module(s) in QT: script
dh_auto_configure: cd freemedforms && qmake -makefile "QMAKE_CFLAGS_RELEASE=-g 
-O2 -fdebug-prefix-map=/build/freemedforms-project-1.0.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/build/freemedforms-project-1.0.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/build/freemedforms-project-1.0.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/build/freemedforms-project-1.0.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro 
-Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr -r CONFIG\+=LINUX_INTEGRATED 
CONFIG\+=dontbuildquazip LIBRARY_BASENAME=lib/x86_64-linux-gnu 
INSTALL_ROOT_PATH=/usr/ freemedforms.pro returned exit code 3
make[1]: *** [debian/rules:59: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/build/freemedforms-project-1.0.0'
make: *** [debian/rules:55: build] Error 2
...


I have no idea how to proceed from here and Eric did not responded
for a long time.

Kind regards

  Andreas.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#22
[2] https://salsa.debian.org/med-team/freemedforms-project

-- 
http://fam-tille.de

Processed: Re: Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #874880 [src:freemedforms-project] [freemedforms-project] Future Qt4 
removal from Buster
Added tag(s) help.

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

Bug#935794: xfce4-sntray-plugin FTBFS

[Mike Gabriel]

Hi,

On  Sa 31 Aug 2019 14:33:35 CEST, Jonathan Wiltshire wrote:

On Fri, Aug 30, 2019 at 06:14:10AM +,  
mike.gabr...@das-netzwerkteam.de wrote:

Hi,

Am Donnerstag, 29. August 2019 schrieb peter green:
> It looks like that class was dropped from vala-panel in  
https://gitlab.com/vala-panel-project/vala-panel/commit/87493a6dfab9868f77b7b19b57fca40a06fe80af

>
> Unfortunately the commit message doesn't give any clues to what  
if-anything it should be replaced with.

>
> If a proper fix cannot be found then one option would be to drop  
the vala-panel support from this package. The popcon figures for  
the vala-panel variant are the lowest of any of the variants.  
https://qa.debian.org/popcon.php?package=xfce4-sntray-plugin . I  
decided to go ahead and do that in raspbian for the moment to  
complete the transition there.

>
> A debdiff should appear soon at  
https://debdiffs.raspbian.org/main/x/xfce4-sntray-plugin . No  
intent to NMU in Debian.

>
> There does seem to be some upstream activity on  
xfce4-sntray-plugin at  
https://github.com/rilian-la-te/xfce4-sntray-plugin but I can't  
find anything relavent to this issue.

>

I hope that upstream makes a new release soon, see
https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34

In the past, Konstantin has been really quick with such requests.


Seems to be fixed in  
https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/-/tags/0.4.12


Currently waiting for an "r4" release of cmake-vala...

See https://gitlab.com/vala-panel-project/cmake-vala/issues/4

Mike
--

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

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



pgp5vEaBVWMfn.pgp
Description: Digitale PGP-Signatur