Processed: tagging 939932

[Debian Bug Tracking System]

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

> tags 939932 + confirmed
Bug #939932 [src:varnish-modules] varnish-modules: FTBFS after new varnish 
update
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#935290: fakeroot bug

[Robert Lemmen]

having looked at the fakeroot source, it is a bit more complicated than
I thought at first. so until I man up a bit more: #940056

cu  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: PGP signature

Bug#939185: marked as done (RM: pytimechart -- RoM; python2-only; dead upstream; low popcon; no rdeps)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 04:34:49 +
with message-id 
and subject line Bug#936011: Removed package(s) from unstable
has caused the Debian Bug report #936011,
regarding RM: pytimechart -- RoM; python2-only; dead upstream; low popcon; no 
rdeps
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.)


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

Package: src:pytimechart
Version:  1.0.0~rc1-3.3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

  This is the preferred option.

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

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

  This is the least preferred option.

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

  affects  + src:pytimechart

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pytimechart | 1.0.0~rc1-3.3 | source, all

--- Reason ---
RoM; python2-only; dead upstream; low popcon; no rdeps
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/936011

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind 

Bug#936011: marked as done (RM: pytimechart -- RoM; python2-only; dead upstream; low popcon; no rdeps)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 04:34:49 +
with message-id 
and subject line Bug#936011: Removed package(s) from unstable
has caused the Debian Bug report #936011,
regarding RM: pytimechart -- RoM; python2-only; dead upstream; low popcon; no 
rdeps
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.)


-- 
936011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pytimechart
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello,
As part of the effort to remove Python 2 from Debian
(https://wiki.debian.org/Python/2Removal) i came across pytimechart; it seems a
very useful tools, but it's still python2-only and there hasnt been a new
upstream release in almost 10 years.

I've looked on github and other source hosting website and there's no version
supporting python3.

I believe we should remove this package.  If i dont hear anything back in 10
days with reasons to keep this around, i'll file a RM bug.

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

Versions of packages pytimechart depends on:
ii  python2.7.16-1
pn  python-chaco  
pn  python-enthoughtbase  
pn  python-fonttools  
ii  python-gtk2   2.24.0-6
ii  python-kiwisolver 1.0.1-2+b1
ii  python-wxgtk3.0   3.0.2.0+dfsg-8

pytimechart recommends no packages.

pytimechart suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pytimechart | 1.0.0~rc1-3.3 | source, all

--- Reason ---
RoM; python2-only; dead upstream; low popcon; no rdeps
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/936011

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

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

Bug#894519: marked as done (RM: python-gtkglext1 -- RoQA; python2-only; dead upstream; low popcon; no rdeps)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 04:34:11 +
with message-id 
and subject line Bug#894519: Removed package(s) from unstable
has caused the Debian Bug report #894519,
regarding RM: python-gtkglext1 -- RoQA; python2-only; dead upstream; low 
popcon; no rdeps
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.)


-- 
894519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gtkglext1
Version: 1.1.0-9.1
Severity: serious
Tags: buster sid

python-gtkglext1 has no reverse dependencies. (xpra recommends it). It
was removed from Testing a month ago because it depends on pygtk which
the Debian GNOME team is working to remove from Debian. [1]

python-gtkglext1's last upstream release was 12 years ago [2] and its
last Debian upload was 6 years ago.

Therefore, I intend for file a Debian removal bug for python-gtkglext1
soon. Please let me know if this is ok with you.

[1] https://bugs.debian.org/885373
[2] https://projects-old.gnome.org/gtkglext/download.html

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-gtkglext1 |  1.1.0-9.1 | source
python-gtkglext1 | 1.1.0-9.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; python2-only; dead upstream; low popcon; no rdeps
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 894...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/894519

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

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

Bug#940076: Keyexchange with firefox not working

[Jörg Frings-Fürst]

Package: keepassxc
Version: 2.4.3+dfsg.1-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

after the last update the keyexchange with firefox are not longer working.

CU
Jörg



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

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

Versions of packages keepassxc depends on:
ii  libargon2-10~20171227-0.2
ii  libc6  2.28-10
ii  libgcrypt201.8.5-2
ii  libqrencode4   4.0.2-1+b1
ii  libqt5concurrent5  5.11.3+dfsg1-4
ii  libqt5core5a   5.11.3+dfsg1-4
ii  libqt5dbus55.11.3+dfsg1-4
ii  libqt5gui5 5.11.3+dfsg1-4
ii  libqt5network5 5.11.3+dfsg1-4
ii  libqt5svg5 5.11.3-3
ii  libqt5widgets5 5.11.3+dfsg1-4
ii  libqt5x11extras5   5.11.3-2
ii  libsodium231.0.18-1
ii  libstdc++6 9.2.1-4
ii  libx11-6   2:1.6.7-1
ii  libxi6 2:1.7.9-1
ii  libxtst6   2:1.2.3-1
ii  libykpers-1-1  1.20.0-1+b1
ii  libzxcvbn0 2.4+dfsg-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

keepassxc recommends no packages.

keepassxc suggests no packages.

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl15w1gACgkQCfifPIyh
0l1UXxAAz8f8M4uiIhTV03BZD8xFdXiTHjFbGEv87lO/zEEcjJzHsHS7L0k/AzDV
KRmonFs6u+ZXHEhdynCir1v0/1pZdiNetr09qb+l0akVgq0OniJ9jRgJ2+KIl+vg
gTtDfuu+uVWaVEYUc3WTKZXQt0f1U3P2+RkvmtFLa/Vkke1WbgmCJ3ycTIC1uqG/
LWKd9DHN6KqguERiB/K6sASXpZzhCPiAi6hkaib9grFESpcmk9GdoL7wSY8hUV3V
+J7lqkXSWtIu6w1Cz/cZhciZkGvOlNrJDVzPywuRSkKzu56PJnL/0uCVECNvn3nQ
gnFSihM2kxKB6/wG5xkuAqRZ8AK0sVuLZd87f5RrsVuHN1u9+7+ytrY9ZoGkPbI7
bVOmxvfWE1NAf1BzfTSSpdJPpDt5+FeCiA4hs7zTAfrUBbyN5zq34LR46Dz5YK4C
WB5xyUzDdandYcO8/8/oBKp6isN8k8Nmpi71iLKAQlloOkr2sWaD6/XY5rc1hGQI
M01T+BC9zkTBK3Pb59xT8WSHkSlBwfocXtzN1hSD2B8w4vGzo8aoEIuXEqUdzweD
N7fz1kKEeBH2w1Mq6I5EioNReQ5i2/Xoi9EWvcqcQNQf0ah8UC/QXuKk105cn/JL
3SehQTOADHIzEqkysBHGFwwq1QDqehVYjYru5wBz8gUmvKNiARo=
=w0ew
-END PGP SIGNATURE-

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

[Ying-Chun Liu (PaulLiu)]

Hi Felix,


Thanks too. Actually I didn't do much things. Just update to the latest
upstream version 4.1.0.

The only thing that needs to do is  rebasing
turn-off-fastmath-for-amd64.patch.


Yours,
Paul


Felix Lechner 於 2019/9/11 下午9:28 寫道:
>
> That's why I uploaded it. It only took four years for someone to think
> the same way!
>
> I'll look over your patch and update the package. Thanks for using it.
>
> Kind regards,
> Felix



signature.asc
Description: OpenPGP digital signature

Bug#932339: marked as done (Hangs while building test packages due to debhelper commit 789eb18b)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 19:29:52 -0700
with message-id 

and subject line Resolved with listed commit
has caused the Debian Bug report #932339,
regarding Hangs while building test packages due to debhelper commit 789eb18b
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.)


-- 
932339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 12.2.2
Severity: important
X-Debbugs-CC: la...@debian.org, kact...@debian.org

Hi,

Updating from version 12.1.1 in testing to 12.2.2 breaks the build
process for test packages in Lintian. The unstable pipelines on
jenkins and Gitlab are failing.

The command 't/bin/build-test-packages' in Lintian runs for a while
but then hangs. Some of the processes that build test packages in
parallel may not terminate. The command also stalled when using
'--jobs=1'. I was unable to locate an error message.

The issue is caused by commit 789eb18b, which was found through
bisection. The change looks innocuous. Sorry I could not be of more
help.

Kind regards
Felix Lechner
--- End Message ---
--- Begin Message ---
This bug was resolved with the commit listed above, but it did not
appear in the changelog. The commit was marked 'Dch-Gbp: ignore'.
Closing now.--- End Message ---

Processed: retitle 936011 to RM: pytimechart -- RoM; python2-only; dead upstream; low popcon; no rdeps ...

[Debian Bug Tracking System]

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

> retitle 936011 RM: pytimechart -- RoM; python2-only; dead upstream; low 
> popcon; no rdeps
Bug #936011 [src:pytimechart] pytimechart: should this package be removed?
Bug #939185 [src:pytimechart] pytimechart: Python2 removal in sid/bullseye
Changed Bug title to 'RM: pytimechart -- RoM; python2-only; dead upstream; low 
popcon; no rdeps' from 'pytimechart: should this package be removed?'.
Changed Bug title to 'RM: pytimechart -- RoM; python2-only; dead upstream; low 
popcon; no rdeps' from 'pytimechart: Python2 removal in sid/bullseye'.
> reassign 936011 ftp.debian.org
Bug #936011 [src:pytimechart] RM: pytimechart -- RoM; python2-only; dead 
upstream; low popcon; no rdeps
Bug #939185 [src:pytimechart] RM: pytimechart -- RoM; python2-only; dead 
upstream; low popcon; no rdeps
Bug reassigned from package 'src:pytimechart' to 'ftp.debian.org'.
Bug reassigned from package 'src:pytimechart' to 'ftp.debian.org'.
No longer marked as found in versions pytimechart/1.0.0~rc1-3.3.
No longer marked as found in versions pytimechart/1.0.0~rc1-3.3.
Ignoring request to alter fixed versions of bug #936011 to the same values 
previously set
Ignoring request to alter fixed versions of bug #939185 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: retitle 894519 to RM: python-gtkglext1 -- RoQA; python2-only; dead upstream; low popcon; no rdeps ...

[Debian Bug Tracking System]

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

> retitle 894519 RM: python-gtkglext1 -- RoQA; python2-only; dead upstream; low 
> popcon; no rdeps
Bug #894519 [src:python-gtkglext1] python-gtkglext1: Intent to remove from 
Debian
Changed Bug title to 'RM: python-gtkglext1 -- RoQA; python2-only; dead 
upstream; low popcon; no rdeps' from 'python-gtkglext1: Intent to remove from 
Debian'.
> reassign 894519 ftp.debian.org
Bug #894519 [src:python-gtkglext1] RM: python-gtkglext1 -- RoQA; python2-only; 
dead upstream; low popcon; no rdeps
Bug reassigned from package 'src:python-gtkglext1' to 'ftp.debian.org'.
No longer marked as found in versions python-gtkglext1/1.1.0-9.1.
Ignoring request to alter fixed versions of bug #894519 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#940068: gr-gsm FTBFS in unstable

[Vasil Velichkov]

Hi Peter,

On 12/09/2019 01.36, peter green wrote:
> Package: gr-gsm
> Version: 0.42.2-1
> Severity: serious
> Tags: bullseye, sid
> 
> gr-gsm failed to build with the following errors when an attempt was made to 
> binnmu it for the new gnuradio.
> 
>> CMake Warning at CMakeLists.txt:135 (find_package):
>>    Found package configuration file:
>>
>>  /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake
>>
>>    but it set Gnuradio_FOUND to FALSE so package "Gnuradio" is considered to
>>    be NOT FOUND.  Reason given by package:
>>
>>    Gnuradio could not be found because dependency MPLIB could not be found.
>>
>>
>>
>> -- Checking for module 'volk'
>> --   Found volk, version 2.0
>> -- Found VOLK: /usr/lib/x86_64-linux-gnu/libvolk.so
>> -- Checking for module 'cppunit'
>> --   Found cppunit, version 1.14.0
>> -- Found CPPUNIT: /usr/lib/x86_64-linux-gnu/libcppunit.so;dl
>> -- Checking for module 'libosmocore'
>> --   Found libosmocore, version 0.12.0
>> -- Found libosmocore: /usr/lib/x86_64-linux-gnu/libosmocore.so
>> -- Checking for module 'libosmocodec'
>> --   Found libosmocodec, version 0.12.0
>> -- Found libosmocodec: /usr/lib/x86_64-linux-gnu/libosmocodec.so
>> -- Checking for module 'libosmocoding'
>> --   Found libosmocoding, version 0.12.0
>> -- Found libosmocoding: /usr/lib/x86_64-linux-gnu/libosmocoding.so
>> -- Checking for module 'libosmogsm'
>> --   Found libosmogsm, version 0.12.0
>> -- Found libosmogsm: /usr/lib/x86_64-linux-gnu/libosmogsm.so
>> CMake Error at CMakeLists.txt:150 (message):
>>    GnuRadio Runtime required to compile gr-gsm

We are working on gnuradio 3.8 support in 
https://github.com/ptrkrysik/gr-gsm/issues/475

Bug#940031: gnucash-docs_3.7-1_all.changes REJECTED

[Dmitry Smirnov]

On Wednesday, 11 September 2019 9:59:36 PM AEST Aurelien Jarno wrote:
> Built-Using should use the source package name (i.e. fonts-freefont) and
> not the binary package name.

Of course. Thanks for pointing this out. Will fix...

-- 
Best wishes,
 Dmitry Smirnov.

---

Politics: a Trojan horse race.
-- Stanisław Jerzy Lec


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

Bug#940031: marked as done (gnucash-docs_3.7-1_all.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 23:04:40 +
with message-id 
and subject line Bug#940031: fixed in gnucash-docs 3.7-2
has caused the Debian Bug report #940031,
regarding gnucash-docs_3.7-1_all.changes REJECTED
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.)


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

On 2019-09-11 06:24, Debian FTP Masters wrote:
> 
> gnucash-docs_3.7-1_all.deb: Built-Using refers to non-existing source package 
> fonts-freefont-otf (= 20120503-9)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 

Built-Using should use the source package name (i.e. fonts-freefont) and
not the binary package name.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
--- Begin Message ---
Source: gnucash-docs
Source-Version: 3.7-2

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

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

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash-docs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 08:24:21 +1000
Source: gnucash-docs
Architecture: source
Version: 3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 940031
Changes:
 gnucash-docs (3.7-2) unstable; urgency=medium
 .
   * Fixed generation of "Built-Using" field (Closes: #940031).
 Thanks, Aurelien Jarno.
Checksums-Sha1:
 babf4bd5492c5ebf5290fe14a0fd7729b163aee7 1964 gnucash-docs_3.7-2.dsc
 3bf2d8efa7083c88740d8bf75f7c0e22f76ece2f 13868 gnucash-docs_3.7-2.debian.tar.xz
 28ae000375a413c761ff2e93864a623f8e18fe88 7998 
gnucash-docs_3.7-2_amd64.buildinfo
Checksums-Sha256:
 138daf1fb945d7f8596b5e011cffca2434ae528ad1504eda8fe99e0130c1c297 1964 
gnucash-docs_3.7-2.dsc
 0bcac536748f08559d33b4d1c5ccf8d2e0142ee42bb79407960bfed675fc8bab 13868 
gnucash-docs_3.7-2.debian.tar.xz
 b4b8bca7f871452a9f56ed978d7689abe901fb18ea246ab8f253b429b15a48e4 7998 
gnucash-docs_3.7-2_amd64.buildinfo
Files:
 e9b9669f86af4eef7929a9badbd9cc9b 1964 doc optional gnucash-docs_3.7-2.dsc
 61122fe530faa00f68e32c6ec3d35d02 13868 doc optional 
gnucash-docs_3.7-2.debian.tar.xz
 bd14deea7c47d10ad4977bc1f42ad126 7998 doc optional 
gnucash-docs_3.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl15eKgACgkQUra72VOW
jRt7yw//dzYwAajMBMOOKQGx3Re0l5k8TjU/gNhprWylCrtns352g01kVFqFu8pX
kglMM3yLab6MatHdZAwEMuVY5BmtGAteBwcUvIebjIQsBdhrq+io3otkNb1qDJuL
Kwexi0Xy7yTF2L3umzgd4KRLT8GBtEYoDJKmS4UlPNBV8z8bOGtoIXFDrS6HFdJg
byNcUjMgY0utCv1UTehhZvOjSUvRiq4Jx810wa/v4CGj6Djvot2nOyuvDBmM5UDK
KTtTbw/rN937tux53NsI0j8V35u8/Jb1UqXMnzX6pLcJ7ABzj1BS7yterx+E18Mc
z5u3cfvIJUH8j0yXR5e6gKjJO+5VXoSIOdNBvM2MZRwT5bat6Wg7aXjfr7bdpRJz
LNHgtj+lyGvkT6kibTZh+cFWqr2YsD3XkVp1GgZwTJzb31LbbxhRNa0pwCiEI8q8
f6Zz9trCev51c5hoJmfh+fI3eL+r9UB/QV7WL631gWeJ39usqdROlblSBvW34aAm
LXikHdSON4hNPR/LljVY82/+UGaTHNtpYM/7WCrt6Jf7aAMXU6TLb7dnEmFBRTUE
DvPPL4L2rfhktkEzqWZgoBa8GssVUFm/Jnfcj+afkC1+exST1ftGdS8OurvmX5Fu
FYWENjDe0T0r8p4lqR/kAVs/Ez7X5JaZ+gBCHiN/3e7MWbTtFj8=
=8Lw9
-END PGP SIGNATURE End Message ---

Bug#940031: marked as pending in gnucash-docs

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #940031 in gnucash-docs 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/debian/gnucash-docs/commit/e0c6697153e9e5ea2fa12e0aa0cebc4ef5362a78


Fixed generation of "Built-Using" field (Closes: #940031).

 Thanks, Aurelien Jarno.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/940031

Processed: Bug#940031 marked as pending in gnucash-docs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940031 [src:gnucash] gnucash-docs_3.7-1_all.changes REJECTED
Added tag(s) pending.

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

Bug#940071: gr-radar FTBFS in unstable.

[peter green]

Package: gr-radar
Version: 0.0.0.20180308-1
Severity: serious
Tags: bullseye, sid

gr-radar failed to build with the following errors when an attempt was made to 
binnmu it for the new gnuradio.


CMake Error at CMakeLists.txt:120 (find_package):
   Could not find a configuration file for package "Gnuradio" that is
   compatible with requested version "3.7.2".

   The following configuration files were considered but not accepted:

 /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake, version: 
3.8.0.0



-- Configuring incomplete, errors occurred!

Bug#940069: gr-limsdr FTBFS in unstable.

[peter green]

Package: gr-limesdr
Version: 0.9~beta-1+b2
Severity: serious
Tags: bullseye, sid

gr-limesdr failed to build with the following errors when an attempt was made 
to binnmu it for the new gnuradio.


-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
   Could NOT find MPLIB (missing: MPLIBXX_LIBRARY MPLIB_LIBRARY
   MPLIB_INCLUDE_DIR)
Call Stack (most recent call first):
   /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/FindMPLIB.cmake:26 
(find_package_handle_standard_args)
   /usr/share/cmake-3.13/Modules/CMakeFindDependencyMacro.cmake:48 
(find_package)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:26 
(find_dependency)
   CMakeLists.txt:130 (find_package)

Bug#940068: gr-gsm FTBFS in unstable

[peter green]

Package: gr-gsm
Version: 0.42.2-1
Severity: serious
Tags: bullseye, sid

gr-gsm failed to build with the following errors when an attempt was made to 
binnmu it for the new gnuradio.


CMake Warning at CMakeLists.txt:135 (find_package):
   Found package configuration file:

 /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake

   but it set Gnuradio_FOUND to FALSE so package "Gnuradio" is considered to
   be NOT FOUND.  Reason given by package:

   Gnuradio could not be found because dependency MPLIB could not be found.



-- Checking for module 'volk'
--   Found volk, version 2.0
-- Found VOLK: /usr/lib/x86_64-linux-gnu/libvolk.so
-- Checking for module 'cppunit'
--   Found cppunit, version 1.14.0
-- Found CPPUNIT: /usr/lib/x86_64-linux-gnu/libcppunit.so;dl
-- Checking for module 'libosmocore'
--   Found libosmocore, version 0.12.0
-- Found libosmocore: /usr/lib/x86_64-linux-gnu/libosmocore.so
-- Checking for module 'libosmocodec'
--   Found libosmocodec, version 0.12.0
-- Found libosmocodec: /usr/lib/x86_64-linux-gnu/libosmocodec.so
-- Checking for module 'libosmocoding'
--   Found libosmocoding, version 0.12.0
-- Found libosmocoding: /usr/lib/x86_64-linux-gnu/libosmocoding.so
-- Checking for module 'libosmogsm'
--   Found libosmogsm, version 0.12.0
-- Found libosmogsm: /usr/lib/x86_64-linux-gnu/libosmogsm.so
CMake Error at CMakeLists.txt:150 (message):
   GnuRadio Runtime required to compile gr-gsm

Processed: tagging 917686

[Debian Bug Tracking System]

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

> tags 917686 - bullseye
Bug #917686 {Done: Rene Engelhard } [src:lightproof] 
lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error")
Removed tag(s) bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 917686

[Debian Bug Tracking System]

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

> tags 917686 - buster
Bug #917686 {Done: Rene Engelhard } [src:lightproof] 
lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error")
Removed tag(s) buster.
> thanks
Stopping processing here.

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

Processed: tagging 917686

[Debian Bug Tracking System]

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

> tags 917686 - sid
Bug #917686 {Done: Rene Engelhard } [src:lightproof] 
lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error")
Removed tag(s) sid.
> thanks
Stopping processing here.

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

Bug#940063: gnss-sdr FTBFS, is gr-iio broken? did gnuradio break ABI?

[peter green]

Package: gnss-sdr
Version: 0.0.11-1
Severity: serious

gnss-sdr seems to have recently started failing to build with the following 
error.


cd /build/1st/gnss-sdr-0.0.11/obj-x86_64-linux-gnu/src/utils/front-end-cal && /usr/bin/c++  
-DBOOST_GREATER_1_65 -DGNSSSDR_INSTALL_DIR=\"/usr\" -DGNSS_SDR_VERSION=\"0.0.11\" 
-DHAS_STD_FILESYSTEM=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES 
-I/build/1st/gnss-sdr-0.0.11/src/core/libs -I/build/1st/gnss-sdr-0.0.11/src/core/interfaces 
-I/build/1st/gnss-sdr-0.0.11/src/core/libs/supl -I/build/1st/gnss-sdr-0.0.11/src/core/libs/supl/asn-supl 
-I/build/1st/gnss-sdr-0.0.11/src/core/libs/supl/asn-rrlp 
-I/build/1st/gnss-sdr-0.0.11/src/core/system_parameters -I/build/1st/gnss-sdr-0.0.11/src/core/receiver 
-I/build/1st/gnss-sdr-0.0.11/obj-x86_64-linux-gnu/src/algorithms/PVT/libs 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/PVT/libs -I/build/1st/gnss-sdr-0.0.11/src/algorithms/libs 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/libs/rtklib 
-I/build/1st/gnss-sdr-0.0.11/obj-x86_64-linux-gnu/src/core/monitor 
-I/build/1st/gnss-sdr-0.0.11/src/core/monitor 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/acquisition/adapters 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/libs/gsl/include 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/acquisition/gnuradio_blocks 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/libs/opencl 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/acquisition/libs 
-I/build/1st/gnss-sdr-0.0.11/src/algorithms/channel/libs -isystem /usr/include/glog  -g -O2 
-ffile-prefix-map=/build/1st/gnss-sdr-0.0.11=. -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Wextra -pthread 
-std=c++2a -o CMakeFiles/front-end-cal.dir/main.cc.o -c 
/build/1st/gnss-sdr-0.0.11/src/utils/front-end-cal/main.cc
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libgnuradio-iio.so: undefined reference to 
`gr::analog::sig_source::make(double, gr::analog::gr_waveform_t, double, 
double, float, float)'
collect2: error: ld returned 1 exit status


I first saw this in raspbian bullseye, but it's also happening on the Debian reproducible 
builds site, the precise error quoted above was taken from a "reproducible 
builds" build for amd64.

This kind of looks like gnuradio broke ABI and therefore broke gr-iio, but i'm 
not by any means an expert on how different gnuradio bits fit together.

Bug#875047: marked as pending in midisnoop

[Dmitry Eremin-Solenikov]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/midisnoop/commit/b4b06a8b8d0f3dce361c0b03db4c2cff3420d97f


Update to qt5 (Closes: #875047)

Signed-off-by: Dmitry Eremin-Solenikov 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/875047

Bug#935606: marked as done (pki-server: fails to install: several SyntaxError raised)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 21:04:26 +
with message-id 
and subject line Bug#935606: fixed in dogtag-pki 10.7.3-2
has caused the Debian Bug report #935606,
regarding pki-server: fails to install: several SyntaxError raised
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up pki-server (10.7.3-1) ...
File "/usr/lib/python2.7/dist-packages/pki/server/__init__.py", line 417
  print('CATALINA_BASE="%s"' % self.base_dir, file=f)
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python2.7/dist-packages/pki/server/deployment/pkihelper.py", 
line 981
  raise Exception('Server unreachable due to SSL error: %s' % reason) from 
exc
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package pki-server (--configure):
   installed pki-server package post-installation script subprocess returned 
error exit status 101
  Processing triggers for libc-bin (2.28-10) ...
  Processing triggers for ca-certificates (20190110) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  done.
  done.
  Errors were encountered while processing:
   pki-server


cheers,

Andreas


pki-server_10.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.7.3-2

We believe that the bug you reported is fixed in the latest version of
dogtag-pki, 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.
Timo Aaltonen  (supplier of updated dogtag-pki 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: Wed, 11 Sep 2019 23:40:05 +0300
Source: dogtag-pki
Architecture: source
Version: 10.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 918538 935606 936435
Changes:
 dogtag-pki (10.7.3-2) unstable; urgency=medium
 .
   * Switch to python3. (Closes: #918538, #936435, #935606)
   * tests: Migrate to dscreate, bump 389-ds-base dependency.
Checksums-Sha1:
 7b27e0b05eadfd28fbb6194f33a09cd0ff34e3a7 3726 dogtag-pki_10.7.3-2.dsc
 d55cd082f239430b7fd5aed190b0ce8469dd4d0c 30728 
dogtag-pki_10.7.3-2.debian.tar.xz
 b47b0f8e4571bd882469e96c3238b25f44fa168b 14227 
dogtag-pki_10.7.3-2_source.buildinfo
Checksums-Sha256:
 22d2ed786bbde2bf938529dc5e5ed63059743cea24ab1c34707dd83355f220e2 3726 
dogtag-pki_10.7.3-2.dsc
 d081c5ea600cee63d98c06bf681faeda38f59b46d59b9bc7d64e6638a760bbad 30728 
dogtag-pki_10.7.3-2.debian.tar.xz
 cd644ee689a06715682e65b9483d76499c5bf8b5675c5d043650f050171cb8d6 14227 
dogtag-pki_10.7.3-2_source.buildinfo
Files:
 862292f9f4c2f8587fc90d83d5d192dc 3726 java optional dogtag-pki_10.7.3-2.dsc
 cec6002959cdb9ec93a5e7e4f981575c 30728 java optional 
dogtag-pki_10.7.3-2.debian.tar.xz
 609e4e0fffb087e8890e3ddca81a6a91 14227 java optional 
dogtag-pki_10.7.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl15W74ACgkQy3AxZaiJ
hNzW1A/9Gct70mbnMfHRqPRUH9yOVRsidrdwrQ3KMSwS2xVrNgrGs9e4G91xjP0M
nqcRmNJEzMpRfAladGL7yB/2ykF+TgVbls++vzomjkwskgllnrniBqgc/nPvypFl
7QhFNfgCLhzYNzPBJddncN+VcJwJWsRk28XyILOG30Bpcbvq4LHdpJZYwKk0OaeY
bmE+FCaEiEZA2IWevOFFgHmoGlbJ/canY+Iy6t6jOuxD72qOb33RvnvU0mp1XEIs
2mY6d83jP/Bb42ZIyjeHHq9EtqxX6RWbc61MKQm7oTfAOs75/uebDTMwcTGkzsqu
E3kx6JyVgksQ1Ca1zPgUI0lhsEspKTrWTfPu6B159rlWswfE/G0n4b6t46/yUHwc
0xCROwP9p0xWtlY+JJVIT9HX/B8DNph+3YT2dU6XrNQzH9FvOcQDc3e6AfCh7O81

Processed: Bug#875047 marked as pending in midisnoop

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #875047 [src:midisnoop] [midisnoop] Future Qt4 removal from Buster
Added tag(s) pending.

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

Processed: reassign 935134 to src:linux, fixed 935134 in 4.9.189-1, reassign 940027 to courier-mta ...

[Debian Bug Tracking System]

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

> reassign 935134 src:linux 4.9.168-1+deb9u5
Bug #935134 {Done: Ben Hutchings } 
[linux-headers-4.9.0-9-common] wireguard-dkms: kernel module fails to build 
with latest Stretch linux kernel sources
Warning: Unknown package 'linux-headers-4.9.0-9-common'
Bug reassigned from package 'linux-headers-4.9.0-9-common' to 'src:linux'.
No longer marked as found in versions 4.9.168-1+deb9u5.
No longer marked as fixed in versions linux/4.9.189-1.
Bug #935134 {Done: Ben Hutchings } [src:linux] 
wireguard-dkms: kernel module fails to build with latest Stretch linux kernel 
sources
The source 'linux' and version '4.9.168-1+deb9u5' do not appear to match any 
binary packages
Marked as found in versions linux/4.9.168-1+deb9u5.
> fixed 935134 4.9.189-1
Bug #935134 {Done: Ben Hutchings } [src:linux] 
wireguard-dkms: kernel module fails to build with latest Stretch linux kernel 
sources
Marked as fixed in versions linux/4.9.189-1.
> reassign 940027 courier-mta
Bug #940027 [courier-msa] cannot stop courier-msa
Warning: Unknown package 'courier-msa'
Bug reassigned from package 'courier-msa' to 'courier-mta'.
Ignoring request to alter found versions of bug #940027 to the same values 
previously set
Ignoring request to alter fixed versions of bug #940027 to the same values 
previously set
> found 939987 2.12-3
Bug #939987 [postgresql-hll] postgresql-hll is broken with glibc 2.29-1
There is no source info for the package 'postgresql-hll' at version '2.12-3' 
with architecture ''
Unable to make a source version for version '2.12-3'
Marked as found in versions 2.12-3.
> tags 939987 + sid bullseye
Bug #939987 [postgresql-hll] postgresql-hll is broken with glibc 2.29-1
Added tag(s) bullseye and sid.
> tags 939670 + experimental
Bug #939670 [gdcm-doc] gdcm-doc: depends on cruft package.
Added tag(s) experimental.
> tags 939754 + sid bullseye
Bug #939754 [gimp] gimp: Crashes when I try to open an image or create a new one
Added tag(s) sid and bullseye.
> tags 939876 + sid bullseye
Bug #939876 [gimp] gimp: segmentation fault on open
Added tag(s) bullseye and sid.
> tags 939974 + sid bullseye
Bug #939974 [src:osmo-trx] osmo-trx FTBFS: undefined reference to symbol 
'_ZN5boost6system16generic_categoryEv'
Added tag(s) bullseye and sid.
> tags 939461 + experimental
Bug #939461 {Done: Xavier Guimard } [src:node-mocha] 
node-supports-color breaks node-mocha autopkgtest: AssertionError 
[ERR_ASSERTION]: The expression evaluated to a falsy value
Added tag(s) experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
935134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935134
939461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939461
939670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939670
939754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939754
939876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939876
939974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939974
939987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939987
940027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#940058: httpie: CVE-2019-10751

[Salvatore Bonaccorso]

Source: httpie
Version: 0.9.8-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for httpie.

CVE-2019-10751[0]:
| All versions of the HTTPie package prior to version 1.0.3 are
| vulnerable to Open Redirect that allows an attacker to write an
| arbitrary file with supplied filename and content to the current
| directory, by redirecting a request from HTTP to a crafted URL
| pointing to a server in his or hers control.

The issue is demostrable via the poc in [1].

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-10751
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10751
[1] https://snyk.io/vuln/SNYK-PYTHON-HTTPIE-460107

Regards,
Salvatore

Processed: reassign 939461 to src:node-mocha, fixed 939461 in 6.2.0+ds1-1, affects 939461, fixed 935243 in 2.3-1 ...

[Debian Bug Tracking System]

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

> reassign 939461 src:node-mocha 4.1.0+ds3-5
Bug #939461 {Done: Xavier Guimard } [src:node-supports-color, 
src:node-mocha] node-supports-color breaks node-mocha autopkgtest: 
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value
Bug reassigned from package 'src:node-supports-color, src:node-mocha' to 
'src:node-mocha'.
No longer marked as found in versions node-supports-color/6.1.0-2 and 
node-mocha/4.1.0+ds3-5.
No longer marked as fixed in versions node-mocha/6.2.0+ds1-1.
Bug #939461 {Done: Xavier Guimard } [src:node-mocha] 
node-supports-color breaks node-mocha autopkgtest: AssertionError 
[ERR_ASSERTION]: The expression evaluated to a falsy value
Marked as found in versions node-mocha/4.1.0+ds3-5.
> fixed 939461 6.2.0+ds1-1
Bug #939461 {Done: Xavier Guimard } [src:node-mocha] 
node-supports-color breaks node-mocha autopkgtest: AssertionError 
[ERR_ASSERTION]: The expression evaluated to a falsy value
Marked as fixed in versions node-mocha/6.2.0+ds1-1.
> affects 939461 + src:node-supports-color
Bug #939461 {Done: Xavier Guimard } [src:node-mocha] 
node-supports-color breaks node-mocha autopkgtest: AssertionError 
[ERR_ASSERTION]: The expression evaluated to a falsy value
Added indication that 939461 affects src:node-supports-color
> fixed 935243 2.3-1
Bug #935243 {Done: Mechtilde Stehmann } [webext-tbsync, 
webext-dav4tbsync, webext-eas4tbsync] Does not work with Thunderbird 6x (60+)
There is no source info for the package 'webext-dav4tbsync' at version '2.3-1' 
with architecture ''
There is no source info for the package 'webext-eas4tbsync' at version '2.3-1' 
with architecture ''
Marked as fixed in versions tbsync/2.3-1.
> notfixed 935243 webext-tbsync/2.3
Bug #935243 {Done: Mechtilde Stehmann } [webext-tbsync, 
webext-dav4tbsync, webext-eas4tbsync] Does not work with Thunderbird 6x (60+)
The source webext-tbsync and version 2.3 do not appear to match any binary 
packages
No longer marked as fixed in versions webext-tbsync/2.3.
> thanks
Stopping processing here.

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

Bug#916317: marked as done (pythonqt dependency problems)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 18:07:18 +
with message-id 
and subject line Bug#940025: Removed package(s) from unstable
has caused the Debian Bug report #916317,
regarding pythonqt dependency problems
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Attempted to run calamares to install a live-build produced ISO on 12/11/18. 
Calamares would not start from launcher, so I run it at the terminal and got 
output that read: cannot find libPythonQt-Qt5-Python3.6.so.3 and 
libPythonQt-QtAll-Qt5-Python3.6.so.3. The versions of those two libraries are 
now libPythonQt-Qt5-Python3.7.so.3.2.0 and 
libPythonQt-QtAll-Qt5-Python3.7.so.3.2.0.

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

I created symlinks to the two newer libraries with the old library names and 
calamares started up and worked as expected.



*** End of the template - remove these template lines ***


-- System Information:
Debian Release: Testing
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 3.2-10+rm

Dear submitter,

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

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

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

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

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

Bug#915329: marked as done (gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 17:35:00 +
with message-id 
and subject line Bug#915329: fixed in gigedit 1.1.1-1
has caused the Debian Bug report #915329,
regarding gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gigedit.html

...
In file included from builtinpix.cpp:2:
../compat.h: In constructor 'HBox::HBox()':
../compat.h:140:41: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HBox() : Gtk::Box(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'VBox::VBox()':
../compat.h:145:41: error: 'VERTICAL' is not a member of 'Gtk::Orientation'
 VBox() : Gtk::Box(Gtk::Orientation::VERTICAL) {}
 ^~~~
../compat.h: In constructor 'HButtonBox::HButtonBox()':
../compat.h:150:53: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HButtonBox() : Gtk::ButtonBox(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'HScale::HScale()':
../compat.h:155:45: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HScale() : Gtk::Scale(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'HScale::HScale(const 
Glib::RefPtr&)':
../compat.h:156:104: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HScale(const Glib::RefPtr& adjustment) : 
Gtk::Scale(adjustment, Gtk::Orientation::HORIZONTAL)
...
--- End Message ---
--- Begin Message ---
Source: gigedit
Source-Version: 1.1.1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated gigedit 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: Wed, 11 Sep 2019 19:07:13 +0200
Source: gigedit
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 915329
Changes:
 gigedit (1.1.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * Use debhelper-compat instead of debian/compat
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Sebastian Ramacher ]
   * New upstream release
 - Fix build against newer versions of libgtkmm. (Closes: #915329)
   * debian/control:
 - Bump debhelper compat to 12.
 - Bump Standards-Version
 - Add autoconf-archive to B-Ds to link with pthread
 - Bump libgig-dev B-D to >= 4.2
   * debian/patches:
 - Refreshed.
 - Link with pthreads.
Checksums-Sha1:
 e1eecf77e3e69618bde3a77d0002ee23b799063f 2115 gigedit_1.1.1-1.dsc
 4c626af9cb3da2ba5dc142612d0b537c72d4e90d 1146369 gigedit_1.1.1.orig.tar.bz2
 cc71133ceb127b1fd1d092f9d96ecf85bc1d0dea 6604 gigedit_1.1.1-1.debian.tar.xz
Checksums-Sha256:
 a4a4b71de76d49ded1bcec9bc2ddd2987d6b2e6722ce4010ae4f7c4e587cec0a 2115 
gigedit_1.1.1-1.dsc
 2b77069302f8721fd614ae4e3ca364f1977731deb166bf5af00d389e9908ab21 1146369 
gigedit_1.1.1.orig.tar.bz2
 bd48e6cc9d180f6b837096f963b5f2bb4c35ece6f6e82f2698a25464b4ab3353 6604 
gigedit_1.1.1-1.debian.tar.xz
Files:
 a094cbd56d8c096129df10c4ddd5238c 2115 sound optional gigedit_1.1.1-1.dsc
 2597cfddbceb28f5e764929e6c9755ab 1146369 sound optional 
gigedit_1.1.1.orig.tar.bz2
 d36b0c62cdfb4203a6e10f1adb30f591 6604 sound optional 
gigedit_1.1.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl15KmwACgkQafL8UW6n
GZPdExAAqj6ITAeuoyRsZZA8pRs4exacj7wWDzZiUF0ZidvqUtsLC1s/scexGms/
vugQn3NPaVPWaZ47gRkpXNRpeH0qBI3HDv218tiJIFjl7zcpEzBOOic/oIU59/0g

Bug#939733: lsb-release: lsb_release does not show point release on Debian 10.1

[Dmitry Bogatov]

control: severity -1 +normal

[2019-09-10 10:21] Jonathan Wiltshire 
> >> The x.y there was a remnant from Debian sarge times.
> > 
> > Up until squeeze I have seen it show x.y.z, then from wheezy to
> > stretch I see only x.y, but it does seem new behaviour in buster to
> > only show x.
> > 
> > $ ansible '*' -i inventories/testing -a 'lsb_release -d' | grep ^Descr | 
> > sort -u
> > Description:Debian GNU/Linux 10 (buster)
> > Description:Debian GNU/Linux 8.11 (jessie)
> > Description:Debian GNU/Linux 9.10 (stretch)
>
> This stems from lsb_release switching to reading the cross-distro
> standard file, /usr/lib/os-release:
>
> | $ cat /etc/debian_version
> | 10.1
> | $ cat /usr/lib/os-release
> | PRETTY_NAME="Debian GNU/Linux 10 (buster)"
> | NAME="Debian GNU/Linux"
> | VERSION_ID="10"
> | VERSION="10 (buster)"

As pointed by maintainer of base-files, this format of
/usr/lib/os-release is with us for some time (just checked on stretch
box).

In theory, I can revert #914287, but is it good thing? Actually, I fail
to see the whole point of `lsb_release` command. You can't squash all
information in your /etc/apt/sources.list into two digits.

This said, I feel current behaviour more logical. LSB pretends to
provide cross-distributions interface, so reading /usr/lib/os-release
feels more natural than /etc/debian_release.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#917686: marked as done (lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error"))

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 16:49:00 +
with message-id 
and subject line Bug#917686: fixed in lightproof 1.6-2
has caused the Debian Bug report #917686,
regarding lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error")
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.)


-- 
917686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lightproof
Version: 1.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for oxt in `find . -name "*.oxt"`; do \
>   oxt=`echo $oxt | sed -e 's,./,,'`; \
>   pkg="libreoffice-`echo $oxt | cut -d- -f1 | sed -e "s/_/-/g" | tr A-Z 
> a-z`"; \
>   dir=`echo $oxt | cut -d- -f1`; \
>   mkdir -p 
> /<>/debian/$pkg/usr/lib/libreoffice/share/extensions/$dir && \
>   cd 
> /<>/debian/$pkg/usr/lib/libreoffice/share/extensions/$dir && \
>   unzip -o /<>/$oxt; \
> done
> Archive:  /<>/lightproof_en-0.4.3.oxt
> warning [/<>/lightproof_en-0.4.3.oxt]:  zipfile is empty
> Archive:  /<>/lightproof_hu-1.6.2.oxt
> warning [/<>/lightproof_hu-1.6.2.oxt]:  zipfile is empty
> Archive:  /<>/lightproof_editor-0.1.oxt
>   inflating: META-INF/manifest.xml   
>   inflating: description.xml 
>   inflating: Linguistic.xcu  
>   inflating: Lightproof.py   
>   inflating: pythonpath/lightproof_handler_lightproof_editor.py  
>   inflating: pythonpath/lightproof_impl_lightproof_editor.py  
>   inflating: pythonpath/lightproof_lightproof_editor.py  
>   inflating: pythonpath/lightproof_compile_lightproof_editor.py  
>   inflating: README  
>   inflating: doc/syntax.txt  
>   inflating: doc/manual.txt  
>   inflating: src/en/en.dat   
>   inflating: lightproof_editor/script.xlb  
>   inflating: lightproof_editor/RegisteredFlag  
>   inflating: lightproof_editor/General.xba  
>   inflating: lightproof_editor/dialog.xlb  
>   inflating: Office/UI/StartModuleWindowState.xcu  
>   inflating: Office/UI/WriterWindowState.xcu  
>   inflating: Office/Accelerators.xcu  
>   inflating: icons/comp.png  
>   inflating: icons/compall.png   
>   inflating: icons/comp16.png
>   inflating: icons/compall16.png 
>   inflating: icons/debug16.png   
>   inflating: icons/debug.png 
>   inflating: META-INF/manifest.xml   
>   inflating: Addons.xcu  
>   inflating: pythonpath/lightproof_opts_lightproof_editor.py  
> Archive:  /<>/lightproof_ru_RU-0.3.4.oxt
> warning [/<>/lightproof_ru_RU-0.3.4.oxt]:  zipfile is empty
> make[1]: *** [debian/rules:38: override_dh_auto_install] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/lightproof_1.6-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated lightproof 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: Wed, 11 Sep 2019 18:22:54 +0200
Source: lightproof
Architecture: source
Version: 1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 773919 917686
Changes:
 lightproof (1.6-2) unstable; urgency=medium
 .
   * apply patch from Jérémy Bobbio  to output locales in a
 stable order to make the build reproducible (Closes: #773919)
   * 

Processed: Bug#917686 marked as pending in lightproof

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917686 [src:lightproof] lightproof: FTBFS: "zipfile is empty" with python 
3.7 ("Key Error")
Added tag(s) pending.

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

Bug#917686: marked as pending in lightproof

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #917686 in lightproof 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/libreoffice-team/libs/lightproof/commit/176005cc68354f8eacd35c7a5a6fe57a64c45bdf


add upstream patch to fix build with python 3.7 (closes: #917686)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917686

Bug#940034: elogind and the release team block

[Adam Borowski]

On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote:
> I reached out to jcristau to talk about his block hint.
> Based on our IRC discussion, it sounds like he was having trouble
> bringing himself to remove the hint presumably because he doesn't think
> the broader issue was being dealt with.

> The systemd maintainers are telling you that you need to provide
> libpam-systemd.

We _did_ use libpam-systemd in the past.  This code was working and tested,
by January 2018 (using consolekit not elogind by then), then a different
version (with elogind), well-tested in Devuan then finally submitted in
November 2018.  The difference is the point the alternative happens at:

PROGRAM -> policykit -> libpam-XXX -> logind

A)
PROGRAM -> policykit-systemd -> libpam-systemd -> systemd
|
`> policykit-elogind -> libpam-elogind -> elogind

B)
PROGRAM -> policykit-systemd -> libpam-systemd -> systemd
 |
 `> libpam-elogind -> elogind

C)
PROGRAM -> policykit-systemd -> libpam-systemd -> systemd
   |
   `> elogind

The Jan 2018 version used A; the Nov 2018 version used C.  Another debated
option was B with dlopen.  Finally (shortly before Buster freeze), it was
requested to make libelogind fully ABI-compatible with libsystemd -- which
elogind's upstream helped implement, but that version was not allowed into
Buster.  And now, we have that replacement problem.

Thus... which way do you want?

> Actually, they would prefer that you create an elogind that mirrors
> enough of the interfaces that you can just use libpam-systemd.  You said
> that would not work, explaining that elogind for example doesn't have a
> concept of slices.  You never clearly articulated why it couldn't
> emulate slices enough to pacify libpam-systemd.  I don't know if it is
> just that work hasn't been done or if it would be a bad idea for some
> reason.

Making elogind implement every single feature of systemd would effectively
make it systemd.  That's not the point.

If I had infinite tuits, I'd implement a clean unix-logind that stubs the
API to good old POSIX functionality -- if you type "who" on a 1990s' system,
you'll already get the same thing the logind idea reimplements.  Unlike
elogind which is a trimmed copy of systemd, that'd make slices completely
out of question.  Same applies to any logind for non-Linux or non-GNU.

I'd say we want the stubs to be as lean as possible (for simplicity, less
moving parts, smaller attack surface, etc), rather than to implement every
single add-on.  If I wanted systemd, I know where to find it (although it
doesn't even boot on my main desktop).


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Your snowflakes have nothing on my socks drawer.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Bug#940034: elogind and the release team block

[Sam Hartman]

> "Adam" == Adam Borowski  writes:

Adam> On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote:
>> I reached out to jcristau to talk about his block hint.  Based on
>> our IRC discussion, it sounds like he was having trouble bringing
>> himself to remove the hint presumably because he doesn't think
>> the broader issue was being dealt with.

>> The systemd maintainers are telling you that you need to provide
>> libpam-systemd.

Adam> We _did_ use libpam-systemd in the past.  This code was
Adam> working and tested, by January 2018 (using consolekit not
Adam> elogind by then), then a different version (with elogind),
Adam> well-tested in Devuan then finally submitted in November 2018.
Adam> The difference is the point the alternative happens at:

As Mark pointed out I meant libsystemd0.
That is, to make the convergance point the dbus APIs etc.

--Sam

Bug#916026: bootchart2: diff for NMU version 0.14.4-3.1

[Boyuan Yang]

Control: tags 916026 + patch
Control: tags 916026 + pending

Dear maintainer,

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

Regards.

diff -Nru bootchart2-0.14.4/debian/bootchart2.lintian-overrides bootchart2-
0.14.4/debian/bootchart2.lintian-overrides
--- bootchart2-0.14.4/debian/bootchart2.lintian-overrides   2012-12-12
15:25:52.0 -0500
+++ bootchart2-0.14.4/debian/bootchart2.lintian-overrides   2019-09-11
10:19:48.0 -0400
@@ -1,2 +1,4 @@
 # it's intentional, indeed.
 bootchart2: package-contains-empty-directory lib/bootchart/tmpfs/
+# Broken as provided by upstream, keep as is
+bootchart2: init.d-script-depends-on-all-virtual-facility
etc/init.d/bootchart-done required-start
diff -Nru bootchart2-0.14.4/debian/changelog bootchart2-
0.14.4/debian/changelog
--- bootchart2-0.14.4/debian/changelog  2012-12-12 15:25:52.0 -0500
+++ bootchart2-0.14.4/debian/changelog  2019-09-11 10:19:53.0 -0400
@@ -1,3 +1,23 @@
+bootchart2 (0.14.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
++ Bump Standards-Version to 4.4.0.
++ Update Vcs-* fields to use git package repo under Salsa Debian
+  group.
++ Use secure URI in homepage field.
+  * debian/patches: Add patch 0006 from upstream to fix FTBFS against
+glibc 2.28. (Closes: #916026)
+  * debian/watch: Correctly monitor GitHub upstream.
+  * debian/copyright:
++ Use secure URI.
+- Delete fields for missing files.
+  * debian/bootchart2.lintian-overrides: Add lintian override for
+init.d-script-depends-on-all-virtual-facility (suppress warning
+for now).
+
+ -- Boyuan Yang   Wed, 11 Sep 2019 10:19:53 -0400
+
 bootchart2 (0.14.4-3) unstable; urgency=low
 
   * Added missing dependency on lsb-base (>= 3.0-6). Thanks to Adam D.
diff -Nru bootchart2-0.14.4/debian/control bootchart2-0.14.4/debian/control
--- bootchart2-0.14.4/debian/control2012-12-12 15:25:52.0 -0500
+++ bootchart2-0.14.4/debian/control2019-09-11 10:13:22.0 -0400
@@ -6,10 +6,10 @@
 Build-Depends:
  debhelper (>= 8~)
  , python (>= 2.6.6-3~)
-Standards-Version: 3.9.3
-Homepage: http://github.com/mmeeks/bootchart
-Vcs-Git: git://git.debian.org/collab-maint/bootchart2.git
-Vcs-Browser: http://git.debian.org/?p=collab-maint/bootchart2.git
+Standards-Version: 4.4.0
+Homepage: https://github.com/mmeeks/bootchart
+Vcs-Git: https://salsa.debian.org/debian/bootchart2.git
+Vcs-Browser: https://salsa.debian.org/debian/bootchart2
 X-Python-Version: >= 2.6
 
 Package: bootchart2
diff -Nru bootchart2-0.14.4/debian/copyright bootchart2-
0.14.4/debian/copyright
--- bootchart2-0.14.4/debian/copyright  2012-12-12 15:25:52.0 -0500
+++ bootchart2-0.14.4/debian/copyright  2019-09-11 10:15:28.0 -0400
@@ -1,5 +1,6 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Source: http://github.com/mmeeks/bootchart
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: bootchart2
+Source: https://github.com/mmeeks/bootchart
 
 Files: *
 Copyright: © Anders Norgaard 
@@ -32,10 +33,6 @@
 Copyright: © 2010-2012, David Paleino 
 License: GPL-2+
 
-Files: debian/manpages/*
-Copyright: © 2011, Francesca Ciceri 
-License: GPL-2+
-
 License: GPL-2+
  This program is free software: you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
diff -Nru bootchart2-0.14.4/debian/patches/0006-include-sys-sysmacros.h-for-
major-minor-makedev.patch bootchart2-0.14.4/debian/patches/0006-include-sys-
sysmacros.h-for-major-minor-makedev.patch
--- bootchart2-0.14.4/debian/patches/0006-include-sys-sysmacros.h-for-major-
minor-makedev.patch 1969-12-31 19:00:00.0 -0500
+++ bootchart2-0.14.4/debian/patches/0006-include-sys-sysmacros.h-for-major-
minor-makedev.patch 2019-09-11 09:59:14.0 -0400
@@ -0,0 +1,23 @@
+From: Mike Frysinger 
+Date: Thu, 21 Apr 2016 00:19:32 -0400
+Subject: include sys/sysmacros.h for major/minor/makedev
+
+These funcs are defined in the sys/sysmacros.h header, not sys/types.h.
+Linux C libraries are updating to drop the implicit include, so we need
+to include it explicitly.
+---
+ collector/collector.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/collector/collector.c b/collector/collector.c
+index 7a746f8..5ca4cd6 100644
+--- a/collector/collector.c
 b/collector/collector.c
+@@ -33,6 +33,7 @@
+ #include "common.h"
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru bootchart2-0.14.4/debian/patches/series bootchart2-
0.14.4/debian/patches/series
--- bootchart2-0.14.4/debian/patches/series 2012-12-12 15:25:52.0
-0500
+++ bootchart2-0.14.4/debian/patches/series 2019-09-11 09:59:14.0
-0400
@@ -3,3 +3,4 @@
 0002-pybootchartgui-skip-malformed-taskstats-lines.patch
 

Processed: bootchart2: diff for NMU version 0.14.4-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 916026 + patch
Bug #916026 [src:bootchart2] bootchart2 FTBFS with glibc 2.28
Added tag(s) patch.
> tags 916026 + pending
Bug #916026 [src:bootchart2] bootchart2 FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#940034: elogind and the release team block

[Mark Hindley]

Julien,

On Wed, Sep 11, 2019 at 03:07:51PM +0100, Mark Hindley wrote:
> I would hope we can all accept those. If so, there is no requirement for a
> manual block: at the moment there are RC bugs which prevent migration. If or
> when they are resolved migration can occur based on the release teams policy 
> in
> effect at that time.

I see you have removed the block whilst I was writing this.

Thank you.

Mark

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

[Felix Lechner]

Hi Paul,

On Wed, Sep 11, 2019 at 6:12 AM Ying-Chun Liu (PaulLiu)
 wrote:
>
> I'm maintaining telegram-cli. I'm using wolfssl because telegram-cli is
> GPL.
>
> They are using openssl but it is actually violates the GPL license. So I
> tried to build telegram-cli with wolfssl and it just works great.

That's why I uploaded it. It only took four years for someone to think
the same way!

I'll look over your patch and update the package. Thanks for using it.

Kind regards,
Felix

Bug#939768: gimp: Crash on startup

[Christophe TROESTLER]

Package: gimp
Version: 2.10.8-2+b1
Severity: grave

On startup Gimp crashes with the following trace:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6) 

using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 2264 - Thread 2264 #

[New LWP 2265]
[New LWP 2266]
[New LWP 2267]
[New LWP 2268]
[New LWP 2269]
[New LWP 2270]
[New LWP 2271]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffcbcd09e50, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7febe8435e00 (LWP 2264) "gimp"  __libc_read (nbytes=256, 
buf=0x7ffcbcd09e50, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7febe7480700 (LWP 2265) "gmain" 0x7febea190819 in 
__GI___poll (fds=0x5613fc0b5220, nfds=2, timeout=3963) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7febe6c7f700 (LWP 2266) "gdbus" 0x7febea190819 in 
__GI___poll (fds=0x5613fc099440, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7febd88c9700 (LWP 2267) "async" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7febd3fff700 (LWP 2268) "worker"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7febd37fe700 (LWP 2269) "worker"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7febd2ffd700 (LWP 2270) "worker"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7febd27fc700 (LWP 2271) "pool-gimp" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7febd27fc700 (LWP 2271)):
#0  0x7febea195f59 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7febea4a7a7f in g_cond_wait_until () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7febea42e0c1 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7febea42e681 in g_async_queue_timeout_pop () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7febea486301 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7febea48589d in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7febea26cfa3 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140650825631488, 
9204343308728132154, 140723476296814, 140723476296815, 140650825631488, 
94643832894144, -9193041426433449414, -9193059371445525958}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#7  0x7febea19b4cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7febd2ffd700 (LWP 2270)):
#0  0x7febea195f59 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7febea4a795f in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x5613fb75dd73 in  ()
#3  0x7febea48589d in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7febea26cfa3 in 

Bug#940034: elogind and the release team block

[Mark Hindley]

Sam,

Thanks

On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote:
> I reached out to jcristau to talk about his block hint.
> Based on our IRC discussion, it sounds like he was having trouble
> bringing himself to remove the hint presumably because he doesn't think
> the broader issue was being dealt with.

Thanks for helping to clarify that.

[snip]

> Actually, they would prefer that you create an elogind that mirrors
> enough of the interfaces that you can just use libpam-systemd.  You said
> that would not work, explaining that elogind for example doesn't have a
> concept of slices.  You never clearly articulated why it couldn't
> emulate slices enough to pacify libpam-systemd.  I don't know if it is
> just that work hasn't been done or if it would be a bad idea for some
> reason.

This was from my discussions with elogind upstream, mainly in the context of
#923244. We considered the possibility of linking elogind against
libsystemd0. However, it was felt that the implementations were sufficiently
different to make that unfeasible. My understanding is that elogind doesn't have
a concept of slice simply because it doesn't require them. It just maps pids,
sessions and users.

But I am happy to go back to them and ask again.

> Now you've got someone arguing that the providing libpam-systemd and
> conflicting with libpam-systemd is problematic.

Do you mean libsystemd0 here?

> And I'll admit that it is definitely a problematic approach.
> I realize that you talked it over with the systemd maintainers and while
> they didn't quite agree, my reading of their message was fairly
> sympathetic.
> 
> So now you've got conflicting requirements coming from multiple
> directions.
> 
> I really don't see a way forward besides getting enough of the right
> parties involved to understand the issues and come up with a solution
> that balances the trade offs across multiple packages.
> 
> I'm sorry that you've been placed in this position.

No worries. Thanks for your help.

My suggestion is based on the following premises:-

 - We are currently early in the bullseye cycle. There seems to me to be no
   better time to allow a wider audience to test elogind and report problems. I
   can certainly understand reluctance to test this later in the cycle.
 
 - The existing RC bug handling is sufficient on its own to control whether
   elogind should be in testing.

 - If problems are found with elogind either directly or indirectly, please
   submit bugs, RC status if it is warranted, and I will be happy to deal with
   them. I want elogind to be as good as it can be both for its users and for
   people who choose not to use it.

I would hope we can all accept those. If so, there is no requirement for a
manual block: at the moment there are RC bugs which prevent migration. If or
when they are resolved migration can occur based on the release teams policy in
effect at that time.

Does that seem reasonable?

Mark

Bug#940040: ubuntu-dev-tools: pbuilder-dist broken in unstable

[Gianfranco Costamagna]

Source: ubuntu-dev-tools
Version: 0.173
Severity: serious

Hello, looks like the last upload broke at least pbuilder-dist

pbuilder-dist eoan login
Traceback (most recent call last):
  File "/usr/bin/pbuilder-dist", line 506, in 
main()
  File "/usr/bin/pbuilder-dist", line 431, in main
app = PbuilderDist(parts[0])
  File "/usr/bin/pbuilder-dist", line 123, in __init__
self.system_architecture = ubuntutools.misc.host_architecture()
  File "/usr/lib/python3/dist-packages/ubuntutools/misc.py", line 97, in 
host_architecture
if not arch or 'not found' in arch[0]:
TypeError: a bytes-like object is required, not 'str'

G.

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

[Mark Hindley]

Julien,

Thank you.

On Wed, Sep 11, 2019 at 02:48:19PM +0200, Julien Cristau wrote:
> -UID: 41176  
> 
> Package: libelogind0
> Version: 241.3-1+debian1
> Severity: serious
> 
> I wrote this in #934132 but that is being ignored so I'll repeat here.

I don't think it was being ignored, rather I had already answered it there.

> I don't think it's reasonable to ship this package with C/R/P
> libsystemd0.

I understand that you don't like it. However, for libelogind0 to export the same
symbols as libsystemd0 so that it could C/R/P libsystemd0 was the agreed
solution to bug #923244.

Do you have another suggestion as to how we could have resolved that? Other
solutions were discounted at the time.

> I think it opens you (and, more importantly, users) up to issues like
> #934491.  Even if #935910 were to be fixed in the package manager in  
> > 
> bullseye, it would still mean libelogind0 couldn't ship with the C/R/P
> until bullseye+1.

I think it seems likely from discussions on #debian-dpkg that #935910 will be
fixed in APT and #934491 can be addressed by adding Breaks: << fixed APT.

> But beyond that particular issue, I'm sorry to say I think fundamentally
> attempting to provide a drop-in replacement for libsystemd0 while
> conflicting with systemd is doomed.  The replacement of sysvinit with
> systemd was careful to keep both init systems co-installable, and I
> think that's something to preserve to avoid providing users with a
> loaded footgun with alternative init systems.

I think this is where we will just have to disagree. I think choice in software
is important. That choice is precious and can be exercised in many ways. Most
importantly,  you are free to choose not to use something that you don't like or
don't want.

Best wishes

Mark

Bug#940034: elogind and the release team block

[Sam Hartman]

Dear Mark:

I reached out to jcristau to talk about his block hint.
Based on our IRC discussion, it sounds like he was having trouble
bringing himself to remove the hint presumably because he doesn't think
the broader issue was being dealt with.

I suggested that he might open his concerns as an RC bug on the package,
because that would regularize the situation.

Please do not just downgrade an RC bug opened by a member of the release
team.  I think the release team would be entirely justified in blocking
your package or removing it at that point.

Unfortunately, it sounds like you are in a bad situation.

The systemd maintainers are telling you that you need to provide
libpam-systemd.

Actually, they would prefer that you create an elogind that mirrors
enough of the interfaces that you can just use libpam-systemd.  You said
that would not work, explaining that elogind for example doesn't have a
concept of slices.  You never clearly articulated why it couldn't
emulate slices enough to pacify libpam-systemd.  I don't know if it is
just that work hasn't been done or if it would be a bad idea for some
reason.

Now you've got someone arguing that the providing libpam-systemd and
conflicting with libpam-systemd is problematic.
And I'll admit that it is definitely a problematic approach.
I realize that you talked it over with the systemd maintainers and while
they didn't quite agree, my reading of their message was fairly
sympathetic.


So now you've got conflicting requirements coming from multiple
directions.

I really don't see a way forward besides getting enough of the right
parties involved to understand the issues and come up with a solution
that balances the trade offs across multiple packages.

I'm sorry that you've been placed in this position.

--Sam

Bug#939990: bird: CVE-2019-16159

[Ondrej Zajicek]

Hi

For Sid, we plan to release soon version 1.6.8 including bugfix for this
bug.

For Buster, i backported bugfix for this bug and two other important
security-related bugfixes for 1.6.6, available in oz-deb Git branch:

https://gitlab.labs.nic.cz/labs/bird/commits/oz-deb

The fixes are:

ba870cab310c151ae8827907c604900ff5cd4d11
 - Fix this bug (CVE-2019-16159)

37f39789f483afd10bcfadca8b414e951ffb6d22
 - Fix bug in privilege revocation causing BIRD in some cases run with
   more privileges than necessary

2545b91b8b96151b415c4d22b3c4ab3835752540
 - Fix bug allowing easily triggerable crash from CLI

-- 
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)


signature.asc
Description: PGP signature

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

[Thorsten Glaser]

Hello Julien,

> conflicting with systemd is doomed.  The replacement of sysvinit with
> systemd was careful to keep both init systems co-installable, and I

note that:

① elogind is not part of the init system, only an add-on to enable
  systemd-like Provides to get some GUI software to run without
  resorting to using consolekit (which is only available from older
  versions of Debian)

② systemd currently is the one that isn’t coinstallable (cf. #935304)

> think that's something to preserve to avoid providing users with a
> loaded footgun with alternative init systems.

This is about an alternative logind implementation, which happens to
be usable with an “alternative” init system.

But what do you propose instead?

Also, question back: could elogind work with libsystemd0, and could
elogind work with systemd (although while this would address the
issue of switching, not Conflicting with systemd increases the chance
that elogind is installed by accident, which people also don’t want)?

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

**

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

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

**

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

[Felix Lechner]

Hi Paul,

I am the maintainer of this library package. Are you aware of any
packages that depend on it?

Kind regards
Felix

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

[Ying-Chun Liu (PaulLiu)]

Felix Lechner 於 2019/9/11 下午8:25 寫道:
> Hi Paul,
>
> I am the maintainer of this library package. Are you aware of any
> packages that depend on it?
>
> Kind regards
> Felix

Hi Felix,


I'm maintaining telegram-cli. I'm using wolfssl because telegram-cli is
GPL.


They are using openssl but it is actually violates the GPL license. So I
tried to build telegram-cli with wolfssl and it just works great.


Yours,
Paul




signature.asc
Description: OpenPGP digital signature

Bug#934691: marked as done (rekall: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 12:51:52 +
with message-id 
and subject line Bug#934691: fixed in rekall 1.6.0+dfsg-3
has caused the Debian Bug report #934691,
regarding rekall: maintainer address bounces
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.)


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

Package: rekall
Severity: serious
x-debbugs-cc: sa...@debian.org
x-debbugs-cc: ben...@debian.org

While sending https://lists.debian.org/debian-python/2019/08/msg00072.html I got

  forensics-de...@lists.alioth.debian.org
(generated fromrek...@packages.debian.org)
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address
--- End Message ---
--- Begin Message ---
Source: rekall
Source-Version: 1.6.0+dfsg-3

We believe that the bug you reported is fixed in the latest version of
rekall, 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.
Raphaël Hertzog  (supplier of updated rekall 
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: Wed, 11 Sep 2019 14:19:03 +0200
Source: rekall
Architecture: source
Version: 1.6.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Closes: 934691
Changes:
 rekall (1.6.0+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Update team maintainer address to Debian Security Tools
 . Closes: #934691
   * Update Vcs-Git and Vcs-Browser for the move to salsa.debian.org
   * Replace priority extra with optional.
Checksums-Sha1:
 fd5b78ffc8ee6f556712dbf62a606e67d60bae22 2269 rekall_1.6.0+dfsg-3.dsc
 6cb2b51e0715d166941e835fda28d62f37c2942a 19391856 
rekall_1.6.0+dfsg-3.debian.tar.xz
 9d77a7e1e8dc74c377dfa75ee0519f14373cd688 7766 
rekall_1.6.0+dfsg-3_source.buildinfo
Checksums-Sha256:
 92cb140495a5e1a3b2677a0a31b6de2ccf327340013ca3d44c6c8279a96e9cee 2269 
rekall_1.6.0+dfsg-3.dsc
 85f3b4273be9a55a2744628c6dfaf74bf18183bc0379cf50aef0b8f3a9a242b1 19391856 
rekall_1.6.0+dfsg-3.debian.tar.xz
 b3d99be23079bd750d7f61429045d24ae64d9d521c6c2b822b7f620608a55302 7766 
rekall_1.6.0+dfsg-3_source.buildinfo
Files:
 f1a939597801a57fa9f7f2e412d96ec9 2269 python optional rekall_1.6.0+dfsg-3.dsc
 abf91fd942b367c7f65ca3fa25ae03f5 19391856 python optional 
rekall_1.6.0+dfsg-3.debian.tar.xz
 edc30040652b68b8573e7df124c194c4 7766 python optional 
rekall_1.6.0+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl146jYACgkQA4gdq+vC
mrlrcAgAjKJ+PS7qRcNKWuvaq9HtseZP3yoF4+wTfgW7UZ13pOr/j2nxDtf5ISw+
fBNMkNo6q7YHDVQ0DqjqlorilQ1PDygHgpnuunoz0537Xl2kcnD+hFWUOTKI/oW+
bM8SnRrnXWInvVvehiwCa9HOFi3Z+8q3gao0yElY+e7Nb6HXV0+D2wrnoPEsXwCz
KuWKC6/Flk2UfilHNDDdc2Ta0K+PY9z+iQOhnODqkA4B3PhidlHbFqdFM0uYXF6X
nS6k8sREML+9WyYNaYd5Z4y3Ng8TdrNAAIS1W23vGoJi9Ryi2/pB22j2QmLl/3aX
Mk1nPkll3khJrUJjNv8R1m6ls2jK2A==
=d7uY
-END PGP SIGNATURE End Message ---

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

[Julien Cristau]

Package: libelogind0
Version: 241.3-1+debian1
Severity: serious

I wrote this in #934132 but that is being ignored so I'll repeat here.

I don't think it's reasonable to ship this package with C/R/P
libsystemd0.

I think it opens you (and, more importantly, users) up to issues like
#934491.  Even if #935910 were to be fixed in the package manager in


bullseye, it would still mean libelogind0 couldn't ship with the C/R/P
until bullseye+1.

But beyond that particular issue, I'm sorry to say I think fundamentally
attempting to provide a drop-in replacement for libsystemd0 while
conflicting with systemd is doomed.  The replacement of sysvinit with
systemd was careful to keep both init systems co-installable, and I
think that's something to preserve to avoid providing users with a
loaded footgun with alternative init systems.

Cheers,
Julien

Bug#934691: rekall: maintainer address bounces

[Raphael Hertzog]

Control: tag -1 + pending

On Tue, 13 Aug 2019, peter green wrote:
> While sending https://lists.debian.org/debian-python/2019/08/msg00072.html I 
> got
> 
>   forensics-de...@lists.alioth.debian.org
> (generated fromrek...@packages.debian.org)
> host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
> SMTP error from remote mail server after RCPT 
> TO::
> 550 Unrouteable address

The maintainer email has been fixed in git a long time ago but no upload
happened so far. I wanted to wait for the python 3 conversion but since
it might take some time still, I'll go ahead with an upload right now
to get this RC bugs out of the picture.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Processed: Re: Bug#934691: rekall: maintainer address bounces

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #934691 [rekall] rekall: maintainer address bounces
Added tag(s) pending.

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

Bug#939949: marked as done (sleepyhead: B-D on cruft package)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 12:21:11 +
with message-id 
and subject line Bug#939949: fixed in sleepyhead 1.0.0-beta-2+dfsg-7
has caused the Debian Bug report #939949,
regarding sleepyhead: B-D on cruft package
to be marked as done.

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

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


-- 
939949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleepyhead
Version: 1.0.0-beta-2+dfsg-6
Severity: serious

Currently sleepyhead build-depends on libquazip5-headers, which is
no longer built from source as its contents have been merged into
libquazip5-dev, thus making sleepyhead unbuildable since these two
packages are not coinstallable. Please remove the build-dependency
on libquazip5-headers.
--- End Message ---
--- Begin Message ---
Source: sleepyhead
Source-Version: 1.0.0-beta-2+dfsg-7

We believe that the bug you reported is fixed in the latest version of
sleepyhead, 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.
Andreas Tille  (supplier of updated sleepyhead 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: Wed, 11 Sep 2019 14:00:59 +0200
Source: sleepyhead
Binary: sleepyhead
Architecture: source
Version: 1.0.0-beta-2+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 sleepyhead - Sleep tracking software with a focus on monitoring CPAP treatment
Closes: 939949
Changes:
 sleepyhead (1.0.0-beta-2+dfsg-7) unstable; urgency=medium
 .
   * Team upload.
   * Drop libquazip5-headers from Build-Depends
 Closes: #939949
   * debhelper-compat 12
   * Standards-Version: 4.4.0
Checksums-Sha1:
 d29c7724f7aeb917a7e60d365ce6f25e789c8fbf 2179 
sleepyhead_1.0.0-beta-2+dfsg-7.dsc
 95620e7272afb7cb47b7a487cbd0c62e38174d1b 207676 
sleepyhead_1.0.0-beta-2+dfsg-7.debian.tar.xz
Checksums-Sha256:
 cba1672864e5f7367f5cf6c731fecfc179c485d2e3d7af41b8a6b0ea65fb241f 2179 
sleepyhead_1.0.0-beta-2+dfsg-7.dsc
 6fd69d4e60522c057c3888302f3be00d708685f1cd474c843cedc46f18e1a41f 207676 
sleepyhead_1.0.0-beta-2+dfsg-7.debian.tar.xz
Files:
 5b93c8691aeec0e2b127c3f8229189d0 2179 science optional 
sleepyhead_1.0.0-beta-2+dfsg-7.dsc
 fe3b352a5c00948ca5579e9287807850 207676 science optional 
sleepyhead_1.0.0-beta-2+dfsg-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl144/URHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGC+A//b7UxpPqUOCoMMpMJJqgeMoLk6uoQEMix
hdiJ2kPm4S7SJ4SR98+oczQXkdyzaZKIJuadykEYjdntGvJmTlmxwLkSL2UWMbxz
oVtTgfqUjY6suYjpLk9C7tuA00BXWq7sLKETEHUEZwbaHeJITxbAE9q8lKaVK/rN
/oQNiNNodCjJWWZQCA5oPhnn4JMpPrjnm5WmmfmCgKkaaIXo8EaH3RfqgqSm4gZ6
SZODF+m6pSKYKeJghP6x9ZqIQDK1FDu8rQ1P1I9p6JCmUreR3NkiDYn0yIN8Ribi
TWIN9loeMh+NLHQpfr7I0z+QqDvcJj4VvoX61MtGWST/bYhgc5/a1G8Me5VBoz7A
1zF3ymD3UO2B1nZdEyoCWv7s8MY6AsH4Y5+QfOWInk0Hp8e8u5Bb+en8dEPi9JN4
lAuBTIIVaVHxnUk0g6HxJwvDxqxg2lqM6MTR8betK/Gfp70x3U9q6aKAz6JzsP5Q
hEeCrEcgKnCouewshX2mlwr2HHwV3Q/yh0a9XhQ+Z7YlAFW8bmKe7wy4ux16mtzC
heKqpZgc2/GI7BAY9Y7tiLGTcTS+M9Rl+OpPqkcWJ6bHNVsDNPhiCR7Ocijv0dYA
BFFDpOoEVh38qJLZSgdRMH+F+2hIZ96W5jzPM+qQQEs3woWaiX820fs2eqW93zRY
kEuNhszsbYU=
=5Rjq
-END PGP SIGNATURE End Message ---

Bug#925745: Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

[Andreas Tille]

Hi Olivier,

On Tue, Aug 20, 2019 at 05:57:50PM +0200, Olivier Sallou wrote:
> 
> On 8/20/19 3:41 PM, Andreas Tille wrote:
> > Hi Olivier,
> >
> > I'm just forwarding this to Debian Mentors list to get a wider audience.
> > I'd prefer a fix over simply removing the test ...
> 
> 
> commenting in text_line_reader.h:
> 
>         // operator const std::string& () const { return
> line_string() ; }
> 
> do the job and test pass
> 
> 
> but I would prefer a c++ friend to acknowledge this It works but I
> do not if there are side effects

Any news about this?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#939626: Upstream

[Sébastien Delafond]

Upstream indicates that:

  We are working actively on that subject. So the next release of
  centreon-broker won't need qt4 nor qt5. Qt will be completely removed
  from it. We hope this change to be finish for the next release of
  Centreon.

This is targetted for 19.10, to be released in October 2019.

Bug#940031: gnucash-docs_3.7-1_all.changes REJECTED

[Aurelien Jarno]

Package: src:gnucash
Version: 1:3.7-1
Severity: serious

On 2019-09-11 06:24, Debian FTP Masters wrote:
> 
> gnucash-docs_3.7-1_all.deb: Built-Using refers to non-existing source package 
> fonts-freefont-otf (= 20120503-9)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 

Built-Using should use the source package name (i.e. fonts-freefont) and
not the binary package name.

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

Processed: bug 939626 is forwarded to https://github.com/centreon/centreon-broker/issues/277

[Debian Bug Tracking System]

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

> forwarded 939626 https://github.com/centreon/centreon-broker/issues/277
Bug #939626 [src:centreon-broker] centreon-broker: Qt4 removal from Buster
Set Bug forwarded-to-address to 
'https://github.com/centreon/centreon-broker/issues/277'.
> thanks
Stopping processing here.

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

Processed: tagging 939626

[Debian Bug Tracking System]

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

> tags 939626 + upstream
Bug #939626 [src:centreon-broker] centreon-broker: Qt4 removal from Buster
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#939838: nftables: please apply upstream commits to fix firewalld testsuite failures

[Gianfranco Costamagna]

On Mon, 9 Sep 2019 14:25:31 +0200 Gianfranco Costamagna 
 wrote:
> Source: nftables
> Version: 0.9.2-1
> Severity: serious
> Justification: breaks another package from working correctly
> 
> Hello, according to firewalld upstream devs, we need 2 commits to fixup their 
> test failures.
> I also cherry-picked another hotfix, because it seemed important to me
> (note, I just uploaded them in Ubuntu, I didn't run the tests yet)
> commit ids:
> - 2e57d4ff79fa166f2dea3686ca4fe051b656a8d2
> - 03478af1bea03eafd43df94334cb001ed26145a3
> - 1e2aae7d73ce733650d78da452d45d6c5498cc33
> 
> patch here:
> 
> http://launchpadlibrarian.net/441272565/nftables_0.9.2-1_0.9.2-1ubuntu1.diff.gz
> 
> 
> thanks
> 
> Gianfranco
> 
> 

BTW all the tests, except for one, are fixed with the three commits above

the last failure is:
ICMP block test case

firewalld upstream sais the last remaining failure has been introduced in: 
9b032cd6477b ("monitor: fix double cache update with --echo")

G.

Bug#939937: Acknowledgement (Remotely exploitable null pointer dereference bug)

[Max Kellermann]

I committed my patch to libapreq's Subversion repository:

 http://svn.apache.org/viewvc?view=revision=1866760

Bug#940026: gvfs: unbuildable in unstable: requires experimental gsettings-desktop-schemas

[Simon McVittie]

Source: gvfs
Version: 1.42.0-1
Severity: grave
Justification: renders package unusable

> gvfs unsatisfiable Build-Depends(-Arch) on amd64: 
> gsettings-desktop-schemas-dev (>= 3.33.0)

We cannot upload the new gsettings-desktop-schemas-dev to unstable yet,
because it Breaks the current version of mutter, which cannot go to
unstable until we are ready for the libmutter and evolution-data-server
ABI transitions to take place.

This probably needs to be reverted via a 1.42.0+really1.38.1 or
1.42.0+really1.40.1 upload to unstable, and 1.42.0+really1.42.0 to
experimental.

Unfortunately this has also knocked gvfs 1.41.x out of experimental,
because that happens automatically whenever the source version in unstable
is higher.

smcv

Bug#934885: marked as done (August 2019 security release)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 09:20:10 +
with message-id 
and subject line Bug#934885: fixed in nodejs 10.16.3~dfsg-1
has caused the Debian Bug report #934885,
regarding August 2019 security release
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.)


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

nodejs is affected by some of the recently announced HTTP2 issues:

https://nodejs.org/en/blog/vulnerability/aug-2019-security-releases/
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 10.16.3~dfsg-1

We believe that the bug you reported is fixed in the latest version of
nodejs, 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.
Jérémy Lal  (supplier of updated nodejs 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: Wed, 11 Sep 2019 10:39:30 +0200
Source: nodejs
Architecture: source
Version: 10.16.3~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 919588 934885 939001
Changes:
 nodejs (10.16.3~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 10.16.3~dfsg (Closes: #934885)
   * Avoid two tests to cause a FTBFS (Closes: #919588)
   * Delete applied ssl 1.1.1 compatibility patches
   * Never run tests in parallel to avoid memory exhaustion
   * README: match current modules search paths (Closes: #939001)
   * Fix make-doc patch, simplify make using NODE_PATH
   * B-D pkg-js-tools
   * Tighten dep on libuv1 version
Checksums-Sha1:
 18dffcf2e4b08b7ac8a319953ec85c5d5d122465 3062 nodejs_10.16.3~dfsg-1.dsc
 eeae907a6f5e3d84e86a68b5f4cd705ead72ed80 17057172 
nodejs_10.16.3~dfsg.orig.tar.xz
 b9552650512dc06845c8e3d8e1eaa6b1b01a0d4a 93220 
nodejs_10.16.3~dfsg-1.debian.tar.xz
 972cfed64c9b4f12d454e5db65bc108367c1314a 8190 
nodejs_10.16.3~dfsg-1_source.buildinfo
Checksums-Sha256:
 092bc85272a4d25e79e888913c1a470f6c230e448b49c74778486a3a56a6cdb9 3062 
nodejs_10.16.3~dfsg-1.dsc
 38358e22e385ef5174e7fdf53d92081f03bf33149675bbe4aff00a22f559bf13 17057172 
nodejs_10.16.3~dfsg.orig.tar.xz
 3b175f7bd7ec8bc6c7f4a9ce9ad1011a45cce68b3ee74af9945d0d79b04a57b1 93220 
nodejs_10.16.3~dfsg-1.debian.tar.xz
 9fed752a7160dafb30a65348b17b62c35d94f5ea217ff34bc956b60736bdae5f 8190 
nodejs_10.16.3~dfsg-1_source.buildinfo
Files:
 97fb19bb03d8101062d846b985e6813e 3062 javascript optional 
nodejs_10.16.3~dfsg-1.dsc
 92bab069c0afeefa7f90cae6bf2261de 17057172 javascript optional 
nodejs_10.16.3~dfsg.orig.tar.xz
 6b8269369d41a092b5e54b3721727c7e 93220 javascript optional 
nodejs_10.16.3~dfsg-1.debian.tar.xz
 d359aff8efdbdb381c566e8c8424f4df 8190 javascript optional 
nodejs_10.16.3~dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl14svESHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0c04P/1HfXMrvpMnJmZihGg70D8ui0xnkumRx
kLDfQk9HJG97tE96LRLuDjbv4rx/+tApKUuaAL5u/4gLda0WXdrx/qI4uTHxS2JU
6nV+ymldwiInjtzDLvzq7PfzIAcHMf1OtpSChkSxM2E3ecpc/ITC/z3CjbIehtng
EUGahDPMhfwC+zwIOMu42nWNazXuVN9E3eC9lI0llEGj9hvFp3dsrRHLdhWysxZp
D0TFoOockwbq4MkmYwcHC3MxW73XP6UqSfYk3scbfvSQMe0rQJAuUwpCH3HnISAC
lnXFbaJaH1TaGSlp8MSpX7Qmn1cAIZS13H6oqvUpJlZqY9MDTsBhfOd/tTBPawAo
gMIAChcIGnE7PUtpQJ2OH8pqQNRWdBQBCh0o34UqfjZXhtceH8VnRKydQSfCV1H7
ycC1JiEP9bhLer6XrVyqKREfQlqz4olvHUxFG6LWwjkMfLtHqA32fB0DzBi4QCfe
zQuzIdbqBlDxkyht3Trc2Vr61ffKj6sZw9P9BW5craysHLXbKMjsxSnGWoqzqKAN
Rt/y/puEYjlmrJCALzH4l1W+71KvYFK/SXlAdSqpwkF9/t6bkwfYZOWLA5drVxA8
wa9lB+4tTxM2XgNfN6kjts683SOedimMzBOh35GhXFD55cnGRDsN29l8Rq1jhyKJ
x/bWGrTpMyPn
=p5TP
-END PGP SIGNATURE End Message ---

Bug#935290: moar digging

[Robert Lemmen]

On Wed, Sep 11, 2019 at 08:42:48AM +0200, Dominique Dumont wrote:
> Could you open a bug against fakeroot to have statx supported ?

will do, but want to include a patch so might take a few days

regards  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: PGP signature

Bug#933163: grave bug in stable only fixed in testing/unstable?

[Matt Bernstein]

Hi,

I think this bug got closed without a fix in stable.

Thankfully 3.0.11 is available in buster-backports. But could either 
3.0.11 or the one-line fix be applied to buster please?


Thank you,

Matt

Bug#940015: minder: Incomplete debian/copyright?

[Chris Lamb]

Source: minder
Version: 1.3.0-1
Severity: serious
Justication: Policy ยง12.5
X-Debbugs-CC: Yangfl , ftpmas...@debian.org

Hi,

I just ACCEPTed minder from NEW but noticed lots of files say that
they are GPL-2+, not GPL-3+.

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#940017: crypto-policies: Incomplete debian/copyright?

[Chris Lamb]

Source: crypto-policies
Version: 20190816git-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Hideki Yamane , lavam...@debian.org, 
ftpmas...@debian.org

Hi,

I just ACCEPTed minder from NEW but noticed it was missing attribution
for at least Tomáš Mráz.

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#939779: marked as done (kmod FTBFS: dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!?)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 07:53:17 +
with message-id 
and subject line Bug#939779: fixed in kmod 26-2
has caused the Debian Bug report #939779,
regarding kmod FTBFS: dh_makeshlibs: The udeb libkmod2-udeb does not contain 
any shared libraries but --add-udeb=libkmod2-udeb was passed!?
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.)


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

kmod fails to build from source in unstable:

| dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
| dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries 
but --add-udeb=libkmod2-udeb was passed!?
| make: *** [debian/rules:115: .stamp-binary] Error 255
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Is this a debhelper regression?

Helmut
--- End Message ---
--- Begin Message ---
Source: kmod
Source-Version: 26-2

We believe that the bug you reported is fixed in the latest version of
kmod, 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.
Marco d'Itri  (supplier of updated kmod 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: Wed, 11 Sep 2019 09:29:57 +0200
Source: kmod
Architecture: source
Version: 26-2
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Closes: 939779
Changes:
 kmod (26-2) unstable; urgency=medium
 .
   * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
 actually contain a library. (Closes: #939779)
   * Switched to dh.
Checksums-Sha1:
 a2695de7a1d7dbd6d7e936494ba61579d0f798c9 1810 kmod_26-2.dsc
 7697ade18a52de77a3f02ddc41121b90b39c6c65 8132 kmod_26-2.debian.tar.xz
 d96a88a58b83297a466f90f1179e7fcf829705d1 7676 kmod_26-2_amd64.buildinfo
Checksums-Sha256:
 1ec187fe643832dabd44dfff5ff41f6f532897d45f0725236e71c60a0ae500e6 1810 
kmod_26-2.dsc
 3bf955198ad1cf33c9325e2f971650ec3bcbaaa95dfa254ac2ecaa9f708586dd 8132 
kmod_26-2.debian.tar.xz
 215deddcf9412ca0b352f5639e2b490df41af19e66cea033513f92f50d1ebd4e 7676 
kmod_26-2_amd64.buildinfo
Files:
 33046f6bfcdabf7f6b329da4688c110c 1810 admin important kmod_26-2.dsc
 0c4b630db5ca6fdb36dd371facca11b3 8132 admin important kmod_26-2.debian.tar.xz
 64a68b290edd040a77a3ce862fef2739 7676 admin important kmod_26-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEGBsIcS5ipP0URKfyK/WlwSLE96QFAl14orMACgkQK/WlwSLE
96Qy3Qv+Nrmijb0blN6uYavPbTeSOzUeOC/rGlsGY9L10CZeAWTTVrS2+8rUj48O
gZ1g6CaOal4m8zVijCGwM8BzAo5dFvqO/uFegqf2a/gSilwdN8b8SA/f3neV7sCg
1S3SRwYUT+bzOiDNcrmV/v8j6s70g1STJpODuopklEumlASZaaczYPPBylMxi3ad
Q/MBc5KnmXRdMAfEb97eXMJFAAEXPjFG3zis6WRnR9IUclULZQFY4sRipbddNmPw
66YIu38ZnLGfTHUgP6hiCwPE3/4G6mSD1o2ELvUiqso/cMCOSaOY+6BMPn9Z4x5K
xW2gEdjgTrdG7te3XyvTL6CMfBUMtamGjK/wsl5WcdftSaPd7ADx72eUaYWbfOXU
GXWDCGzYvlqYjwon1JdnhyItg7pIYiT6GvmiYndJEw8wPbuTlsi9xk+h8tS0K3LH
PupI4sgGLvFHwIahpOtToRbkPbi7TjOsTL/S2rfhmIITQ9mHjWc0t1Dgl5YVT/2q
s2yLgqB+
=qf4F
-END PGP SIGNATURE End Message ---

Bug#925738: marked as done (libcec: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 07:19:09 +
with message-id 
and subject line Bug#925738: fixed in libcec 4.0.4+dfsg1-3
has caused the Debian Bug report #925738,
regarding libcec: ftbfs with GCC-9
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.)


-- 
925738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcec
Version: 4.0.4+dfsg1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libcec_4.0.4+dfsg1-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/cec/_cec.so
-- Set runtime path of 
"/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/cec/_cec.so"
 to ""
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/cec.py
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/cec/__init__.py
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libcec.pc
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/cec.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/cecc.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/cecloader.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/ceccloader.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/cectypes.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/include/libcec/version.h
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/x86_64-linux-gnu/libcec.so.4.0.4
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/x86_64-linux-gnu/libcec.so.4
-- Installing: 
/<>/libcec-4.0.4+dfsg1/debian/tmp/usr/lib/x86_64-linux-gnu/libcec.so
make[2]: Leaving directory 
'/<>/libcec-4.0.4+dfsg1/obj-x86_64-linux-gnu'
rm debian/tmp/usr/bin/cec-client
mv debian/tmp/usr/bin/cec-client-* debian/tmp/usr/bin/cec-client
make[1]: Leaving directory '/<>/libcec-4.0.4+dfsg1'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installexamples -a
   dh_installman -a
   dh_python2 -a
I: dh_python2 fs:343: renaming _cec.so to _cec.x86_64-linux-gnu.so
/usr/share/dh-python/dh_python2:67: DeprecationWarning: The 'warn' method is 
deprecated, use 'warning' instead
  'libpython%s: %s', so_version, fn)
W: dh_python2 dh_python2:67: public extension linked with libpython2.7: 
_cec.x86_64-linux-gnu.so
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcec4/DEBIAN/symbols doesn't match 
completely debian/libcec4.symbols
--- debian/libcec4.symbols (libcec4_4.0.4+dfsg1-2_amd64)
+++ dpkg-gensymbolsqU3lwz   2019-03-26 16:42:59.361339522 +
@@ -388,7 +388,7 @@
  _ZN3CEC13CCECProcessorD2Ev@Base 2.1.4
  _ZN3CEC13CCECTypeUtils14GetMaskForTypeENS_15cec_device_typeE@Base 2.1.4
  _ZN3CEC13CCECTypeUtils8ToStringENS_10cec_opcodeE@Base 2.1.4
- 

Bug#939975: marked as done (rauc: Testsuite makes rauc FTBFS on all archs)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 07:09:35 +
with message-id 
and subject line Bug#939975: fixed in rauc 1.1-2
has caused the Debian Bug report #939975,
regarding rauc: Testsuite makes rauc FTBFS on all archs
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.)


-- 
939975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rauc
Version: 1.1-1
Severity: serious
Tags: fixed-upstream patch
Justification: FTBFS on all archs

Hello,

rauc 1.1-1 failed on all arches that don't cheat by not using nocheck:

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

I talked to upstream and four commits are needed. Some are already in
upstream's master, two are still waiting in a pull request on github[1].

I prepared an MR on salsa which adds all necessary commits on top of
1.1-1:

https://salsa.debian.org/debian/rauc/merge_requests/6

If time to work on this is a problem for you I can prepare and upload an
NMU with these changes. Just tell me ...

Best regards
Uwe

[1] https://github.com/rauc/rauc/pull/476
--- End Message ---
--- Begin Message ---
Source: rauc
Source-Version: 1.1-2

We believe that the bug you reported is fixed in the latest version of
rauc, 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.
Arnaud Rebillout  (supplier of updated rauc 
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: Wed, 11 Sep 2019 07:45:32 +0700
Source: rauc
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Rebillout 
Changed-By: Arnaud Rebillout 
Closes: 939975
Changes:
 rauc (1.1-2) unstable; urgency=medium
 .
   [ Uwe Kleine-König ]
   * Cherry pick fix from upstream that removes a wrong test that made rauc
 FTBFS. (commit: 35c98ab18f)
   * Cherry pick fix from upstream that makes rauc work on big endian.
 (commit: bc25067177)
   * Another test fix by Enrico Jörns from
 https://github.com/rauc/rauc/pull/476.
   * The three above changes fix rauc's testsuite and so make rauc build again.
 (Closes: #939975)
Checksums-Sha1:
 bb401ab7f59fc90b7ee07c2cdd03791465725183 2011 rauc_1.1-2.dsc
 df1326bbc4ea06b4e1d0cd75a98f4fefdb8ed43d 9560 rauc_1.1-2.debian.tar.xz
 8189bd9457985e39253950e76d0a5cba4fa7d654 8608 rauc_1.1-2_amd64.buildinfo
Checksums-Sha256:
 865a2addd71d828204ae923b454e392226e5a39cf4117e882e639396ec048e6a 2011 
rauc_1.1-2.dsc
 58f09392be5ab070632152b73c68120fb5ace2058c54d981c610a26ddc50b6cc 9560 
rauc_1.1-2.debian.tar.xz
 778fe935c44b9648b23cc20b888bb0a5d10b92041ab595f705dba96f3d2efbef 8608 
rauc_1.1-2_amd64.buildinfo
Files:
 5e57c5c329c1026fcf2917f1f707f995 2011 admin optional rauc_1.1-2.dsc
 f4ee857e6a5407e80bf7613a375ced6a 9560 admin optional rauc_1.1-2.debian.tar.xz
 216b7c33abe46743463b9e7e78de8c45 8608 admin optional rauc_1.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAl14mL4ACgkQwfwUeK3K
7Aki9AgAns/voChpeSOXxQKKJo17ycMsnJkdAEXyCUMgzgSh/9T3mVbuYpZqDLCT
mJWXqRpywkXpVNbXuqSi/ixJ5PVlivgJ3pjPcsc8YvXBFxnvt+9CSuozygHHtHid
wPX9POgaCtvRnxc78kqQN+2R8n/BRD2JZGz5/eOPKwoYulDCGIiwKxIrPE2Nu8bO
0h5pc2lYj4GYEoYmw6zAw7wW8a0D833gT+ysLUtwCTqkk2Wv18clJtekA+NF1mSL
MXCEW3mL+/Kkm//IYkNJIsum3Xd4dxrhOrUQN75yqoJLHjyU8WkMWOEQsqhCTelf
vTbzzEETPAzDIXUwbvsRHGf8qWbm7Q==
=cNkn
-END PGP SIGNATURE End Message ---

Bug#935290: moar digging

[Dominique Dumont]

On Wednesday, 11 September 2019 07:21:24 CEST Robert Lemmen wrote:
> ...and it's fakeroot! it does ld_preload to map file user ids, and doing
> that it fakes stat calls, but not statx!

Excellent news.

I've relayed your findings to upstream.

Could you open a bug against fakeroot to have statx supported ?

Thanks for digging this problem :-)

All the best

Dod

Bug#935550: yubioath-desktop: Qt4 removal from Bullseye

[Scott Kitterman]

On Fri, 23 Aug 2019 23:19:06 +0300 Dmitry Shachnev  wrote:
> Source: yubioath-desktop
> Version: 3.0.1-2
> Severity: important
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> Hi!
> 
> As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
> cycle, as announced in [1].
> 
> 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.
> 
> Your package still uses Qt 4, via the Python bindings (PySide).

Note that pyside removal is imminent, so porting/update is essential if this 
package is to remain viable.

Scott K

Bug#935549: yubikey-piv-manager: Qt4 removal from Bullseye

[Scott Kitterman]

On Fri, 23 Aug 2019 23:17:28 +0300 Dmitry Shachnev  wrote:
> Source: yubikey-piv-manager
> Version: 1.4.2-2
> Severity: important
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> Hi!
> 
> As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
> cycle, as announced in [1].
> 
> 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.
> 
> Your package still uses Qt 4, via the Python bindings (PySide).

Bumping to serious because pyside removal (as part of the Qt 4 removal) is 
imminent.

Scott K

Processed: severity of 935549 is serious

[Debian Bug Tracking System]

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

> severity 935549 serious
Bug #935549 [src:yubikey-piv-manager] yubikey-piv-manager: Qt4 removal from 
Bullseye
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#875122: marked as done ([pyside] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2019 06:02:20 +
with message-id 
and subject line Bug#935025: Removed package(s) from unstable
has caused the Debian Bug report #875122,
regarding [pyside] 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.)


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


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.2.2+source1-3+rm

Dear submitter,

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

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

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

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

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