Bug#935343: marked as done (eficas: Qt4 removal from Bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 28 Sep 2019 05:21:52 +
with message-id 
and subject line Bug#941288: Removed package(s) from unstable
has caused the Debian Bug report #935343,
regarding eficas: Qt4 removal from Bullseye
to be marked as done.

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

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


-- 
935343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eficas
Version: 6.4.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 (PyQt4).

Therefore, please take the time and:

- contact your upstream (if existing) and ask about the state of a Qt 5 /
  PyQt5 port of your application;
- if there are no activities regarding porting, investigate whether there are
  suitable alternatives for your users;
- if there is a Qt 5 port that is not yet packaged, consider packaging it;
- if both the Qt 4 and the Qt 5 versions already coexist in the Debian
  archives, consider removing the Qt 4 version.

Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4.
Please see [2] for the general porting instructions, and [3] for some
Python-specific differences.

The removal is being tracked in [4]. My intention is to bump the severity
of this bug to RC soon, like it is already the case with other Qt 4 removal
bugs.

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
[2]: https://doc.qt.io/qt-5/sourcebreaks.html
[3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html
[4]: https://wiki.debian.org/Qt4Removal

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 6.4.0-1-2+rm

Dear submitter,

as the package eficas 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/941288

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

[Debian Bug Tracking System]

Your message dated Sat, 28 Sep 2019 05:21:22 +
with message-id 
and subject line Bug#941285: Removed package(s) from unstable
has caused the Debian Bug report #875150,
regarding [qtiplot] 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.)


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


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

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

Dear submitter,

as the package qtiplot 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/941285

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

[Debian Bug Tracking System]

Your message dated Sat, 28 Sep 2019 05:20:47 +
with message-id 
and subject line Bug#941286: Removed package(s) from unstable
has caused the Debian Bug report #875158,
regarding [qtexengine] 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.)


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


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

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

Dear submitter,

as the package qtexengine 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/941286

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#918396: marked as done (golang-github-glendc-gopher-json FTBFS with Go 1.11)

[Debian Bug Tracking System]

Your message dated Sat, 28 Sep 2019 05:20:15 +
with message-id 
and subject line Bug#940890: Removed package(s) from unstable
has caused the Debian Bug report #918396,
regarding golang-github-glendc-gopher-json FTBFS with Go 1.11
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.)


-- 
918396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-glendc-gopher-json
Version: 0.1.0+git20170414.0.dc47430-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-glendc-gopher-json.html

...
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16 
github.com/glendc/gopher-json
=== RUN   TestSimple
--- FAIL: TestSimple (0.00s)
json_test.go:59: cannot encode recursively nested tables to JSON
stack traceback:
[G]: in function 'encode'
:45: in main chunk
[G]: ?
=== RUN   TestCustomRequire
--- PASS: TestCustomRequire (0.00s)
FAIL
FAILgithub.com/glendc/gopher-json   0.007s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16 
github.com/glendc/gopher-json returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.1.0+git20170414.0.dc47430-4+rm

Dear submitter,

as the package golang-github-glendc-gopher-json 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/940890

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 ---

Processed: Re: [Pkg-electronics-devel] Bug#930890: ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #930890 [src:ghdl] Update GHDL packaging for newer releases
Severity set to 'serious' from 'wishlist'
> found -1 0.35+git20181129+dfsg-3
Bug #930890 [src:ghdl] Update GHDL packaging for newer releases
Marked as found in versions ghdl/0.35+git20181129+dfsg-3.

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

Bug#941204: marked as done (sdrangelove FTBFS in unstable with new gnuradio: gmpxx.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 28 Sep 2019 01:49:32 +
with message-id 
and subject line Bug#941204: fixed in sdrangelove 0.0.1.20150707-3
has caused the Debian Bug report #941204,
regarding sdrangelove FTBFS in unstable with new gnuradio: gmpxx.h: No such 
file or directory
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer(s),

gnuradio was updated one month ago in unstable and your package was binNMU'ed
to pick up the new library. It FTBFS on all architectures.

cd /<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio && 
/usr/bin/c++  -DBOOST_ALL_NO_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB 
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_PLUGIN -DQT_SHARED 
-DQT_WIDGETS_LIB -DUSE_FFTW -DUSE_SIMD -Dinputgnuradio_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio/inputgnuradio_autogen/include
 -I/<>/obj-x86_64-linux-gnu -I/<>/include 
-I/<>/include-gpl -I/<>/plugins/samplesource/gnuradio 
-I/<>/obj-x86_64-linux-gnu/plugins/samplesource/gnuradio -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -msse2 
-fPIC   -fPIC -std=gnu++11 -o CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o 
-c /<>/plugins/samplesource/gnuradio/gnuradiothread.cpp
In file included from /usr/include/gnuradio/sync_block.h:27,
 from 
/<>/plugins/samplesource/gnuradio/gnuradiothread.cpp:24:
/usr/include/gnuradio/block.h:34:10: fatal error: gmpxx.h: No such file or 
directory
   34 | #include 
  |  ^
compilation terminated.
make[3]: *** 
[plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/build.make:109: 
plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/gnuradiothread.cpp.o]
 Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:479: 
plugins/samplesource/gnuradio/CMakeFiles/inputgnuradio.dir/all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:87: all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
make: *** [debian/rules:14: build-arch] Error 255


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2MorcACgkQnFyZ6wW9
dQqaYQf+K+dRl6K6FBDResB3PJqKGUjZXTXobIt63C0GRjSooNm5ATHJDossE4j7
M75MuIC/2JLiWkRez3hSxKitx8ma+zz1//IFbtgFHRV/pUq0URgirKD8tZOogtQ0
6MpSimm21/Vm2It6RKeIIfCW3g3oC3P4dQuQwuQGAZFOx+4qRt4F73kxx8CV3GjN
wGrxQlwkqvY4hXM8l6JtzqSAdWP3bCIKL9Mb20e1Nr3Muv4fF8FartszpAgA9CqF
EbbS4g4ZH+gw3E6+AEnxtupydUHF/+RHDg2lyEC89aylyXhCGZxgwXw3dJO6ARIA
rozUUvyAWkNtbO1CnTXtUEUTfg0FeQ==
=So5e
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: sdrangelove
Source-Version: 0.0.1.20150707-3

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

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

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated sdrangelove 
package)

(This message was generated automatically at their request; if you
believe that 

Bug#932872: [libkscreenlocker5] Doesn't lock automatically by timeout

[Maximiliano Curia]

Control: severity -1 normal
Control: tags -1 + unreproducible

On 2019-07-24 01:49, Alex Volkov wrote:

Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave


Doesn't lock automatically by timeout, which presents a security issue. 
Seems
to work in a newly created test user setup, and randomly works 
sometimes in my
user, but I have no idea what makes in work. Probably some app 
"inhibits" the

automatic timeout, but I have no idea how to check it with all that
"brilliant" dbus crap.  Ubuntu has https://wiki.ubuntu.com/
DebuggingScreenLocking, but it's for Gnome, not KDE.


Hi Alex,

I'm really sorry that kscreenlocker is not working right for you, sadly 
I'm not being able to reproduce this issue, and as far as I can see it 
works as expected. But, there are a couple of catches in this, for 
example Xserver won't allow a screen lockeer to work whenever a context 
menu window or a tooltip is being shown, this is a known problem in the 
X11 world [1] [2] [3] that's only solved by migrating to wayland.


From the side of the inhibitors, I'm not sure if there is an api you can 
call to obtain the current inhibitors, but you can always try to lock 
the screen by hand and see if the screen does in fact get locked or not. 
Some known inhibitors are: google-chrome in certain situations, slide 
programs in presentation mode, and most video players.


Hope this help you figuring out where is the problem you are seeing.

[1]: https://bugs.kde.org/show_bug.cgi?id=78871
[2]: 
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579
[3]: 
http://blog.martin-graesslin.com/blog/2015/01/why-screen-lockers-on-x11-cannot-be-secure/




--- System information. ---
Architecture:
Kernel:   Linux 4.19.37-bootes0-iommu-p-1000

Debian Release: 10.0
  991 stable  security.debian.org
  991 stable  ftp.fi.debian.org
  990 buster-backports ftp.debian.org
   99 stable  www.deb-multimedia.org
  500 stable  dl.google.com
  500 stable  deb.torproject.org


Happy hacking,
--
Saludos /\/\ /\ >< `/


signature.asc
Description: OpenPGP digital signature

Bug#941273: marked as done (runit: FTBFS (looks like endless loop))

[Debian Bug Tracking System]

Your message dated Fri, 27 Sep 2019 23:36:48 +
with message-id 
and subject line Bug#941273: fixed in runit 2.1.2-35
has caused the Debian Bug report #941273,
regarding runit: FTBFS (looks like endless loop)
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.)


-- 
941273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:runit
Version: 2.1.2-34
Severity: serious

I noticed that the last runit build is already taking over 13h on
buildds.  The hppa build log[1] looks like the build failed due to an
endless loop.

I asked the other builds to be killed.

Ansgar

  [1] 
https://buildd.debian.org/status/fetch.php?pkg=runit=hppa=2.1.2-34=1569581954=0
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-35

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

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

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated runit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Sep 2019 23:19:30 +
Source: runit
Architecture: source
Version: 2.1.2-35
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Closes: 933078 939971 941273
Changes:
 runit (2.1.2-35) unstable; urgency=medium
 .
   * Temporary disable forced-rescan test (Closes: #941273)
 .
 runit (2.1.2-34) unstable; urgency=medium
 .
   [ Dmitry Bogatov ]
   * Add series of patches to implement force-rescan feature (Closes: #933078)
   * Fix 1 second delay in forced rescan implementation
 .
   [ Lorenzo Puliti ]
   * update-service: move supervise directories in tmpfs
   * invoke-run: add verbose option and export NAME (Closes: #939971)
Checksums-Sha1:
 ba3bd305748048a77f4115840e503485b10f7b53 2221 runit_2.1.2-35.dsc
 4045d51a984b694c727be7787b048feba3c16378 40416 runit_2.1.2-35.debian.tar.xz
 e4b2de488679b0aeab7b788424139cb436165a87 6015 runit_2.1.2-35_source.buildinfo
Checksums-Sha256:
 853f93541f88ce7ea070379a0ada19b11fd9f18ff0fc50550e891925d0584359 2221 
runit_2.1.2-35.dsc
 043bb18dec013c82ba499f8d2189b8e6eb0bf8540187a2b590d3bed8ba3775b9 40416 
runit_2.1.2-35.debian.tar.xz
 a5f7f6192627ffd73be88428bef418391cde64cacb50f7f7ad40c26d355c0f4f 6015 
runit_2.1.2-35_source.buildinfo
Files:
 1fbe2c59b520ad92a75e47dbfb9b56bc 2221 admin optional runit_2.1.2-35.dsc
 e3dd03c290826e03e93ed14a7f1c100b 40416 admin optional 
runit_2.1.2-35.debian.tar.xz
 81c222aab5261d4ff0ac1ec0419f3a10 6015 admin optional 
runit_2.1.2-35_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAl2OmSgTHGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5u0UD/97bnqQ/zcuv3I5DlMqNHLY3gUqKXPq
E4kuTLZhgBcFenr43yRQOtTJu5dFX1PxU9frGMKekDvvyDiEVoBEB8Tz5nkvKGA4
6vUCHEl8JxwIZ1wOw2VOazofc9GAMB9mDD74NN+bjjlcuDPdsiyrCUiqdoVrDgKI
+LVA5zfOsiKgsGyFbEWY3ACA4g8TR9+GkXSz0qHxw7V3dAHG0hTTlDhXIHN9MjQl
5+GdFs/8gTDy7OPNih/WcYhVLTqNmSIZZntHN9DGhqWhpC/DuS/1vQygZv5EUcUQ
nRQAW+N9PDBZqI2rePJgeUvXnMn8G/lsPp1Wqw2UOa7xk202t7+5XgUuvstb7hxp
d1qHkjQCnIJG0puzdG9x2d433TRQtypmQwAWcM5T6YuTAti3KXfAZqJ7Rxpi0BcF
b0ORz5LT+wkmRIRV8acgg7Nu0oWSkMYbnDknOrNbintOd8mzrUkO0MMSH9JYY4RY
6InX/ZbdRWOeXncJ88titEKHqXh2ukzjAANFIF2nUWZStlXUl8OaiAo0jhW9mDEe
KlvRxOouB1eTzlcQQhHERzd4vHOqlqZ5AfoPZyx21uxS7TIiQkAnnQpHIW62LCz1
koB66kA8Fp4Ss38GB5hNm4dl/x6h9z7QzCva5dvHBGz1HqtKm6xjRWEkqSHbWJu/
PKs86YHl2PYS9Q==
=bONw
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#932872: [libkscreenlocker5] Doesn't lock automatically by timeout

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #932872 [libkscreenlocker5] [libkscreenlocker5] Doesn't lock automatically 
by timeout
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #932872 [libkscreenlocker5] [libkscreenlocker5] Doesn't lock automatically 
by timeout
Added tag(s) unreproducible.

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

Processed: Bug#941273 marked as pending in runit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941273 [src:runit] runit: FTBFS (looks like endless loop)
Added tag(s) pending.

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

Bug#941273: marked as pending in runit

[Dmitry Bogatov]

Control: tag -1 pending

Hello,

Bug #941273 in runit 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/runit/commit/166d6052c62b8178910ae3ebbdb6a9c65a67dd11


Temporary disable forced-rescan test

Closes: #941273


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941273

Bug#933290: BD on texlive-generic-extra which isn't build anymore and isn't in bullseye

[Steve Langasek]

Package: owncloud-client
Version: 2.5.1.10973+dfsg-1
Followup-For: Bug #933290
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

This is fixed by simply replacing texlive-generic-extra with
texlive-plain-extra in the build-dependencies.  Please find a patch
attached.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru owncloud-client-2.5.1.10973+dfsg/debian/control 
owncloud-client-2.5.1.10973+dfsg/debian/control
--- owncloud-client-2.5.1.10973+dfsg/debian/control 2018-12-28 
11:00:36.0 -0800
+++ owncloud-client-2.5.1.10973+dfsg/debian/control 2019-09-27 
14:49:23.0 -0700
@@ -26,7 +26,7 @@
xvfb,
zlib1g-dev
 Build-Depends-Indep: texlive-fonts-recommended,
- texlive-generic-extra,
+ texlive-plain-extra,
  texlive-latex-extra,
  texlive-latex-recommended,
  xsltproc

Bug#935343: eficas: Qt4 removal from Bullseye

[Moritz Mühlenhoff]

On Tue, Sep 17, 2019 at 11:25:56PM +0200, Moritz Mühlenhoff wrote:
> On Wed, Aug 21, 2019 at 11:00:10PM +0300, Dmitry Shachnev wrote:
> > Source: eficas
> > Version: 6.4.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 (PyQt4).
> > 
> > Therefore, please take the time and:
> > 
> > - contact your upstream (if existing) and ask about the state of a Qt 5 /
> >   PyQt5 port of your application;
> > - if there are no activities regarding porting, investigate whether there 
> > are
> >   suitable alternatives for your users;
> > - if there is a Qt 5 port that is not yet packaged, consider packaging it;
> > - if both the Qt 4 and the Qt 5 versions already coexist in the Debian
> >   archives, consider removing the Qt 4 version.
> 
> Per https://www.code-aster.org/forum2/viewtopic.php?id=22738 is obsolete
> and won't get ported.
> 
> Is this accurate? Does anyone of the maintainers intend to port it themselves?
> Otherwise let's remove it as we're moving forward with the Qt4 removal now.

I've now filed a removal bug.

Cheers,
Moritz 

Bug#935764: marked as done (freeipmi: --link-doc between architecture all and not all packages breaks binNMUs)

[Debian Bug Tracking System]

Your message dated Fri, 27 Sep 2019 21:36:16 +
with message-id 
and subject line Bug#935764: fixed in freeipmi 1.6.4-2
has caused the Debian Bug report #935764,
regarding freeipmi: --link-doc between architecture all and not all packages 
breaks binNMUs
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.)


-- 
935764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeipmi
Version: 1.6.3-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libfreeipmi17

The recent binNMU on amd64 rendered the freeipmi packages uninstallable
because of the --link-doc from an arch:any to an arch:all package.
The arch-dependent binary packages all got a dependency on
freeipmi-common (= 1.6.3-1.1+b1) which does not exist (as it is an
arch:all package, available at version 1.6.3-1.1 only).

Andreas

PS: don't forget to do source-only uploads to sid, otherwise the package
won't migrate to testing


libfreeipmi17_1.6.3-1.1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: freeipmi
Source-Version: 1.6.4-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Sep 2019 23:19:39 +0200
Source: freeipmi
Architecture: source
Version: 1.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 935764
Changes:
 freeipmi (1.6.4-2) unstable; urgency=medium
 .
   * [5fef9cf] Rise compat level to 10.
   * [f65913c] Implement our own version of --link-doc.
 We need to depend on freeipmi-common anyway, so ignoring the broken
 dependencies created by --link-doc is the best option for now.
 Thanks to Andreas Beckmann (Closes: #935764)
   * [b1d0a64] Build-depend on texinfo.
 makeinfo is missing at build time.
   * [861bfac] Remove existing doc directories before linking
Checksums-Sha1:
 4850cef3b5c843a72b14aa17086c507bd9bf0328 3053 freeipmi_1.6.4-2.dsc
 147bf374d1436606f9be1141c32feefa911c29d1 24944 freeipmi_1.6.4-2.debian.tar.xz
 c4b5eb5c0c84d9ed7e00f7f1cf253d76c8170b99 6733 freeipmi_1.6.4-2_source.buildinfo
Checksums-Sha256:
 b42fe5a0c6e9ca53a3a219abea11447532cdd43dbce42b6287da99350b6d5265 3053 
freeipmi_1.6.4-2.dsc
 b6ac5edaff52a9162b2711b48d264097a00b3feae58e312b867c5e262243669d 24944 
freeipmi_1.6.4-2.debian.tar.xz
 86d506527c2f419cff3e79209b152066c24c610d511aa364ca3d7f86e6be6d12 6733 
freeipmi_1.6.4-2_source.buildinfo
Files:
 626ada70dcf21acbefaf35e33f21120b 3053 admin optional freeipmi_1.6.4-2.dsc
 57368b41ab086c5a613577f17d5dbaf9 24944 admin optional 
freeipmi_1.6.4-2.debian.tar.xz
 f90825b43b10ecb80ea242a0f767fbae 6733 admin optional 
freeipmi_1.6.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl2OfWUACgkQ6zYXGm/5
Q196KQ//fZ+Zig2iCp2up9b03QOsbkDwZ4UxtYXg7ua9B2T4i0dJhWUmFAApv66b
SLcwzCNNgpexZr0u18C6bsxngF37/R7SZ6oK95W09TzLFa6/HOW5UBwcQ//AYzKS
Hr+CyK/sTFocgJvYqKWQQpe9AioB2bbgWk3qTUE6Hh+VzmF4ZJkxwQ15Ndt0a22g
kplNEoVTw98F3t8SlzYfuhPC0TMtpcWmG81swBEWHqV7rPAwzmDf8LYoJits/uua
gV23+Bfl2weJ1MlHmuyjgLOBYawa4NEVL15+huoM87qH8P8hiqom/samwKdaxHFo
mctIZE5zclKlmfTzcfkX8YXlmev15W2VACXMUF9uqwkba/EqsFXB19eAd+Dnyedl
xb+RI3v2plsFtQVYuhGNHE5ulXfwCtnPJ9W5UO4gIVtRjk+svy6qrudahGHBDHqY
6wnctAlwrT1mIHceAcXyEi70/455HzrugdPw4T0XHmSL8mGxWzBXqaGNOFTSuBu+
5Ln5DENLojJRo9HTrOx1OMHZ5Is0qJ6/2US5IFQJ5wiHRtT6944CRXDGV3KY2iyH
x1yIecPpGwSghRkFQuuti8Uh1DJP7AosUWun9KrGFA2nXgT/IphxPZQem2256EsY
NCx1k0HEW5+bb8ZNA0OucC7Uk+wE5trbPYwH/9aM6YtcikD2AlI=
=aDD/
-END PGP SIGNATURE End Message ---

Bug#935764: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

[Bernd Zeimetz]

Hi,

thanks for investigating, a fix for it is already in git, just failed to
build due to other issues.

Bernd


On 9/27/19 3:23 PM, Fabio Fantoni wrote:
> |change freeipmi-common (= ${source:Version}) to ||freeipmi-common (=
> ${binary:Version}) can solve the issue or can be other "unexpected"
> cases of issue?|
> 
> 

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#875150: Should we file a removal bug?

[Moritz Mühlenhoff]

On Wed, Sep 25, 2019 at 07:57:47AM +0200, Andreas Tille wrote:
> Hi,
> 
> On Tue, Sep 24, 2019 at 10:48:24PM +0200, Moritz Mühlenhoff wrote:
> > On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > Hi! It seems there is no activity on this bug, should we file a removal 
> > > bug?
> > 
> > Adding the last two uploaders to CC.
> 
> ... as well as Uploaders in d/control in CC.
>  
> > Is anyone of you planning to upload a Qt5 compatible release candidate of 
> > qtiplot?
> > Otherwise we'll file a removal bug as we're closing in on the Qt5 
> > removalnow.
> > 
> > (Upload also happen to experimental to avoid a later roundtrip through NEW 
> > when a final
> > 1.0 comes out)
> 
> While the website[1] is announcing
> 
> 2019/09/18 - QtiPlot 1.0.0-rc10 release available. New features and 
> improvements: 
> 
> (without mentioning a Qt 5 port explicitly :-() the download area[2]
> does not contain any source download of this.  It seems upstream changed
> to a closed source model since you can only download binaries with
> restricted functionality or you need to buy a license.

I've just filed a removal bug.

Cheers,
Moritz

Processed: Re: Processed (with 1 error): Re: Bug#940679: cython3: generated code does out of bounds reads in with-dict (subclass of) cdef class

[Debian Bug Tracking System]

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

> retitle 940679 cython3: generated code does out of bounds reads in with-dict 
> (subclass of) cdef class
Bug #940679 [cython3] pandas: random test crashes
Changed Bug title to 'cython3: generated code does out of bounds reads in 
with-dict (subclass of) cdef class' from 'pandas: random test crashes'.
>
End of message, stopping processing here.

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

Processed (with 1 error): Re: Bug#940679: cython3: generated code does out of bounds reads in with-dict (subclass of) cdef class

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cython3
Bug #940679 [src:pandas] pandas: random test crashes
Bug reassigned from package 'src:pandas' to 'cython3'.
No longer marked as found in versions pandas/0.23.3+dfsg-6.
Ignoring request to alter fixed versions of bug #940679 to the same values 
previously set
> affects -1 python3-pandas python3-skimage
Bug #940679 [cython3] pandas: random test crashes
Added indication that 940679 affects python3-pandas and python3-skimage
> tags -1 fixed-upstream
Bug #940679 [cython3] pandas: random test crashes
Added tag(s) fixed-upstream.
> retitle -1: cython3: generated code does out of bounds reads in with-dict 
> (subclass of) cdef class
Unknown command or malformed arguments to command.


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

Bug#940679: cython3: generated code does out of bounds reads in with-dict (subclass of) cdef class

[Rebecca N. Palmer]

Control: reassign -1 cython3
Control: affects -1 python3-pandas python3-skimage
Control: tags -1 fixed-upstream
Control: retitle -1: cython3: generated code does out of bounds reads in 
with-dict (subclass of) cdef class

No, it is a proper Timedelta-sized space (144 bytes, not a _Timedelta's 
128).  The bug is that Cython is treating the tp_dictoffset slot (128 
bytes from the start of Timedelta) as the *start of* a PyDictObject (48 
bytes, so won't fit here) when it's actually a *pointer to* the 
PyDictObject.

This only happens when tp_dictoffset is nonzero, i.e. either a cdef
class with an instance dict (non-default but allowed), or a normal
Python class inheriting from a cdef class.

This appears to be fixed upstream (though they only seem to have noticed 
that they weren't checking whether the pointer was NULL, not that they 
weren't treating it as a pointer at all):

https://github.com/cython/cython/commit/253c25a902aef2c54de31baa22af73d0dbad2a06#diff-32655df5c2097cca93b52a2ff7583bef

I haven't checked whether this patch can be applied to our Cython 
version.  As it has been released upstream and there is already a 
request for the new upstream version (#941021), packaging this is
probably a better use of time.

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

[Salvatore Bonaccorso]

Hi,

On Thu, Sep 26, 2019 at 04:32:58PM -0400, Boyuan Yang wrote:
> X-Debbugs-CC: debian-secur...@lists.debian.org

Adding now explicity the team alias.

> 在 2019-09-23一的 17:52 +0200，Gunnar Hjalmarsson写道：
> > It may be worth mentioning that Ubuntu's security team has disabled 
> > CVE-2019-14822.patch in the stable releases for now.
> 
> (With my Debian Input Method Team member hat on)
> 
> While we are still waiting for an upstream fix, I think having security flaw
> might be better than broken, at least in Sid. Maybe we could revert the
> problematic CVE fix for now? Of course it would be best if anyone can come up
> with a patch that fixes both CVE-2019-14822 and the usability issue for Qt5
> apps.
> 
> I'm also interested in the attitude of Security Team towards the broken ibus
> in buster-security.

We are aware of it, but to my understanding the condidtions how this
is happending are right now investigated. We discussed this quickly
when we saw Ubuntu did revert the fix, and questioned if we want to
follow the revert from Ubuntu, but opted to monitor the progress, and
hold it back for now. I see you are involved in the triage, so I'm
actually hopefull we can resolve the regression soonish without need
ot reverting the CVE fix.

I as well pinged Simon, who found the security issue, if he can have a
look at the current regression if he has ideas.

Thanks for your work, fwiw!

Regards,
Salvatore

Bug#939492: marked as done (nbsphinx: testsuite failures with new pandoc)

[Debian Bug Tracking System]

Your message dated Fri, 27 Sep 2019 15:20:22 +
with message-id 
and subject line Bug#939492: fixed in nbsphinx 0.4.2+ds-3
has caused the Debian Bug report #939492,
regarding nbsphinx: testsuite failures with new pandoc
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.)


-- 
939492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbsphinx
Version: 0.4.2+ds-1
Severity: serious


Hello, looks like the package is not able anymore to include svg into the pdf 
files...

Look to the testsuite
https://ci.debian.net/packages/n/nbsphinx/

This might be due to a regression/change in pandoc.

cheers,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: nbsphinx
Source-Version: 0.4.2+ds-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Sep 2019 15:03:39 +
Source: nbsphinx
Architecture: source
Version: 0.4.2+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Jerome Benoit 
Closes: 939492
Changes:
 nbsphinx (0.4.2+ds-3) unstable; urgency=medium
 .
   * Debianization:
 - Python 2 removal (Closes: #939492);
 - debian/adhoc/*, refresh.
Checksums-Sha1:
 bf2a52b8027cc8a9df2bc82936071c47b6f6f5ef 3386 nbsphinx_0.4.2+ds-3.dsc
 9652179ce01ca2c298b56163b86cded4ad98328d 767712 
nbsphinx_0.4.2+ds-3.debian.tar.xz
 5bc3bf4754b6f58ec5f27a0d48b94b9206fa3977 6309 
nbsphinx_0.4.2+ds-3_source.buildinfo
Checksums-Sha256:
 a6b6d37e0e2589650c58aeb6cde495ade55b15b936b711b6e74357a6580b9ec9 3386 
nbsphinx_0.4.2+ds-3.dsc
 3c4a04c64ae3495c798b0d10e79c7d8bd0073cfb7426a735584359d5f12e5c17 767712 
nbsphinx_0.4.2+ds-3.debian.tar.xz
 c71d6edbc34158e40a619dfcc531124b38b25fddb34efa95ebb37b4e0fcc01d3 6309 
nbsphinx_0.4.2+ds-3_source.buildinfo
Files:
 52a397866b198aaff46111f47f2359d6 3386 python optional nbsphinx_0.4.2+ds-3.dsc
 08339daa7df62caa2e1b1d1ea1160ceb 767712 python optional 
nbsphinx_0.4.2+ds-3.debian.tar.xz
 69a94932966d18c02be6e99d0a481cc8 6309 python optional 
nbsphinx_0.4.2+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl2OJZoVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLnWwgALSkA9l88m3M6JzoBlgLGkKCX9Gq
dVMac5zIrHkTjfANAEdLos727qL9UmC5AAjAewo7YqgJfxZDOLL+e6PQKEspSqS6
eQi8F2GdCtsd23hvaA/sC0x58ZUm3jj0hOB10AJG/3Qso8rYgywDRTxA2/l4V7zl
DRYyH6JkMc45cWE9OqJ6wBzuNjloxz/1vpT0ytBU4V6LUIAoaexrJU7uFZ9EaQeg
98aYedvJH1CM6fm/vb+K7Bq7JeddwohnL/wOinjYyPsI4U+NKwa6AOouMbZlk+nk
+ufQFI2kCttSf0OCGPldCx28gbkfkfq4a1Pmj0P/KV0snN6+ufjSweKJv29p46U6
VW+6tuzONFGBspL/VlOlr1z3yI5BRYaPFgQ/O1Ylp0lEP1R68taKTl3pCyDi46W6
7EpeVwEfyJK6+oL3UhGs7+3wDpd2aYaieq504bGN5j/dUjJPKy9z3sBgF6Wj0lUl
G8O1aJ+mfs9JRx/P8hu2ACCrgDsDPQNcYf7pMVuqADToWX3nW9IcZ7wZEeEh4WvU
EVPq5fXoFSZVd7QL++QNy+S3wvEirXf5j9piOSGa4UV5q6bYnNJckMedDjM4U0Gw
b4Dkms4VzkqNiQ5RxHlNNLfxCqBhiXuq/f7YoYGAaeJZsV9eZ8Xw1T61c4CKlKnl
3e70wA9xqrGe1SF6Qwme1EHN/WU9Mwz6zZg/vdjx55QIcUo9s3uzsN9NnhsQkUid
GXPKEamBd+Zj1xrkAT26ffHK8hYwWIB6Qo1pxX9TthzsAfvvmX9CdrsE7IQhi1ZV
oY9vrkqkS9zsvvw2YWaolQvOb8Ef73U+QwRypqatOdJ4dQFEwjOAGU6kf2ht747R
hRsiZ4RPmYGWYzePCSRqBQMizC3+a3gUGohu6FYpp/JczZYUN8dnLBGJzhnaxEXF
qtvb9nT7NxkJAysHW8oO5i3u2zx/Izavy5Xo/7DyeA9h4IyG1DMQM/pPY96AyJat
pyATN0oKiH6UtXL59ur/zeKxsyijygOt0rGgaJmHL0Ca1+prQuuth19Ej9FoM1uc
iZpZY1b44xxPXIQFsHdq4UtZIVT6McoPxI1x5iEWvPlJI5myqTZQyt3ASlJP4nsC
Hpr1jLUA51PcHjo9RTD8tVLhSv+R6q6hizazEIstEANowgjGRkhRAnrnjLJvpOtr
WcXHL/xTy1MCPeP8xtHTJ5KXZp001EyejUolnNb4mHj5KP6PG4fSylcNJrvuDKz/
NQddbWy9y+iBRQk8whHJbA2rRUC3hAeRaPaKCYU3EH/EQOBHN4HpAyWNMxcTbPKT
I7UciaOfapBTvvEpCSinNBFP9oMaYGwceE8AsNiFPm4wng1+6TF/gYwL/oQ=
=atlU
-END PGP SIGNATURE End Message ---

Bug#941076: marked as done (libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used with GLib >= 2.59)

[Debian Bug Tracking System]

Your message dated Fri, 27 Sep 2019 16:20:09 +0100
with message-id <20190927152009.ga19...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#941076: libgcr-base-3-1: pinentry-gnome3 causes 
gnome-shell crash if used with GLib >= 2.59
has caused the Debian Bug report #941076,
regarding libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used 
with GLib >= 2.59
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.)


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

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

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


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

On Fri, 27 Sep 2019 at 15:49:43 +0100, Simon McVittie wrote:
> This looks like the bug fixed in 27c58b7f "system-prompter: Fix use
> of g_hash_table_lookup_extended", which was an incompatibility between
> gcr < 3.28.1 and GLib >= 2.59 - and indeed you had gcr < 3.28.1 before
> upgrading. (The fix was also backported in 3.28.0-4, but you didn't
> have that either.) I'll close this bug when the reassign operation has
> been processed.--- End Message ---

Bug#941076: libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used with GLib >= 2.59

[Pirate Praveen]

On Fri, Sep 27, 2019 at 15:49, Simon McVittie  wrote:

Control: tags -1 = bullseye sid
Control: retitle -1 libgcr-base-3-1: pinentry-gnome3 causes 
gnome-shell crash if used with GLib >= 2.59

Control: reassign -1 libgcr-base-3-1 3.28.0-1
Control: affects -1 + gnome-shell pinentry-gnome3
Control: fixed -1 3.28.0-4

On Wed, 25 Sep 2019 at 16:59:01 +0530, Pirate Praveen wrote:

 2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2


On Fri, 27 Sep 2019 at 19:20:24 +0530, Pirate Praveen wrote:

 Thread 1 (Thread 0x7fe7cc222ac0 (LWP 1660)):
 #0  0x7fe7d5a23468 in prompt_stop_prompting 
(self=0x556f95d03770 [GcrSystemPrompter], callback=, 
send_done_message=1, wait_for_reply=0) at 
gcr/gcr-system-prompter.c:501


This looks like the bug fixed in 27c58b7f "system-prompter: Fix use
of g_hash_table_lookup_extended", which was an incompatibility between
gcr < 3.28.1 and GLib >= 2.59 - and indeed you had gcr < 3.28.1 before
upgrading. (The fix was also backported in 3.28.0-4, but you didn't
have that either.) I'll close this bug when the reassign operation has
been processed.

So upgrading this library was the correct solution, and there
is no missing dependency in gnome-shell, pinentry-gnome3 or
gnome-session.

If anything, the correct relationship would have been for
libglib2.0-0 (>= 2.59) to have a Breaks on libgcr-base-3-1 (<< 
3.28.0-4~).

However, that version is older than buster (which was released with
gcr 3.28.1-1), and in general Debian does not support upgrades from
older-than-buster to bullseye (or in general from older than Debian n
to Debian n+1).

In future please upgrade the entire system to at least the versions in
stable, then reboot, before attempting to use any package from 
testing,

unstable or experimental. This would have saved you a lot of time in
dealing with an already-fixed bug.



This machine was always in sid, though I only used to update specific 
packages like gnome, firefox, libreoffice etc. I guess I should start 
doing dist-upgrades and not try to save bandwidth.



This would also have gone considerably faster if you had started the
bug report by locating the process that segfaulted (gnome-shell) and
using reportbug to report it as a bug in that process (the gnome-shell
package). This would have given us a complete list of the libraries
loaded into that process.



Thanks for tracking down the issue and sorry for the noise.


Thanks,
smcv

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

[Mark Hindley]

Julien,

On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
> 
> The "init" package has the "Important: yes" control field which as I
> understand it tells apt to behave like "Essential: yes", except for not
> trying to install the package if it is not installed.
> 
> That's not quite enough for our purposes, because apt would still be
> allowed to replace systemd-sysv with sysvinit-core, but maybe
> systemd-sysv could get that flag as well?
> 
> Julian didn't seem to find the idea crazy when we brought that up on
> irc.

Thanks. The aim of preventing accidental removal of systemd is very
reasonable. However, using this approach the hurdle you create even to a user
who really wants to uninstall is pretty high. Few people will continue having
seen the 'You are about to do something potentially harmful' warning.

I think the effect we are after is rather closer to that of apt-mark hold
systemd or dpkg --set-selections systemd hold. Once held, uninstalling the
package requires a specific request to apt.  But I realise this approach will
also prevent upgrades.

Mark

Processed: Re: Bug#941076: libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used with GLib >= 2.59

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = bullseye sid
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
Added tag(s) sid and bullseye; removed tag(s) moreinfo and experimental.
> retitle -1 libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used 
> with GLib >= 2.59
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
Changed Bug title to 'libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash 
if used with GLib >= 2.59' from '[GNOME 3.34] debsign crashes gnome on wayland 
session'.
> reassign -1 libgcr-base-3-1 3.28.0-1
Bug #941076 [gnome-session,pinentry-gnome3] libgcr-base-3-1: pinentry-gnome3 
causes gnome-shell crash if used with GLib >= 2.59
Bug reassigned from package 'gnome-session,pinentry-gnome3' to 
'libgcr-base-3-1'.
No longer marked as found in versions gnome-session/3.34.0-1, 
libgcr-base-3-1/3.28.0-1, and pinentry-gnome3/1.1.0-3.
No longer marked as fixed in versions libgcr-base-3-1/3.33.4-2.
Bug #941076 [libgcr-base-3-1] libgcr-base-3-1: pinentry-gnome3 causes 
gnome-shell crash if used with GLib >= 2.59
Marked as found in versions gcr/3.28.0-1.
> affects -1 + gnome-shell pinentry-gnome3
Bug #941076 [libgcr-base-3-1] libgcr-base-3-1: pinentry-gnome3 causes 
gnome-shell crash if used with GLib >= 2.59
Added indication that 941076 affects gnome-shell and pinentry-gnome3
> fixed -1 3.28.0-4
Bug #941076 [libgcr-base-3-1] libgcr-base-3-1: pinentry-gnome3 causes 
gnome-shell crash if used with GLib >= 2.59
Marked as fixed in versions gcr/3.28.0-4.

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

Bug#941076: libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash if used with GLib >= 2.59

[Simon McVittie]

Control: tags -1 = bullseye sid
Control: retitle -1 libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash 
if used with GLib >= 2.59
Control: reassign -1 libgcr-base-3-1 3.28.0-1
Control: affects -1 + gnome-shell pinentry-gnome3
Control: fixed -1 3.28.0-4

On Wed, 25 Sep 2019 at 16:59:01 +0530, Pirate Praveen wrote:
> 2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2

On Fri, 27 Sep 2019 at 19:20:24 +0530, Pirate Praveen wrote:
> Thread 1 (Thread 0x7fe7cc222ac0 (LWP 1660)):
> #0  0x7fe7d5a23468 in prompt_stop_prompting (self=0x556f95d03770 
> [GcrSystemPrompter], callback=, send_done_message=1, 
> wait_for_reply=0) at gcr/gcr-system-prompter.c:501

This looks like the bug fixed in 27c58b7f "system-prompter: Fix use
of g_hash_table_lookup_extended", which was an incompatibility between
gcr < 3.28.1 and GLib >= 2.59 - and indeed you had gcr < 3.28.1 before
upgrading. (The fix was also backported in 3.28.0-4, but you didn't
have that either.) I'll close this bug when the reassign operation has
been processed.

So upgrading this library was the correct solution, and there
is no missing dependency in gnome-shell, pinentry-gnome3 or
gnome-session.

If anything, the correct relationship would have been for
libglib2.0-0 (>= 2.59) to have a Breaks on libgcr-base-3-1 (<< 3.28.0-4~).
However, that version is older than buster (which was released with
gcr 3.28.1-1), and in general Debian does not support upgrades from
older-than-buster to bullseye (or in general from older than Debian n
to Debian n+1).

In future please upgrade the entire system to at least the versions in
stable, then reboot, before attempting to use any package from testing,
unstable or experimental. This would have saved you a lot of time in
dealing with an already-fixed bug.

This would also have gone considerably faster if you had started the
bug report by locating the process that segfaulted (gnome-shell) and
using reportbug to report it as a bug in that process (the gnome-shell
package). This would have given us a complete list of the libraries
loaded into that process.

Thanks,
smcv

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

[Adam Borowski]

On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
> 
> The "init" package has the "Important: yes" control field which as I
> understand it tells apt to behave like "Essential: yes", except for not
> trying to install the package if it is not installed.
> 
> That's not quite enough for our purposes, because apt would still be
> allowed to replace systemd-sysv with sysvinit-core, but maybe
> systemd-sysv could get that flag as well?

That flag is not for "without an explicit user choice".  It's for "you're
breaking the packaging system, far more than ignoring dependencies".

It's the biggest hammer dpkg has.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄ etc), let the drink age at least 3-6 months.

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 13:33, Simon McVittie  wrote:

On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:



 On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 


 wrote:
 > Let me try downgrading libgcr-base-3-1 and reproduce the crash.



 Do I need to install some -dbgsym packages?


Yes, please install at least gdb, libgcr-base-3-1-dbgsym and
libglib2.0-0-dbgsym (the versions corresponding to the libraries you
already have installed), then use

coredumpctl gdb 1648

to use gdb to inspect the core dump that was captured by
systemd-coredump. The stack traces printed by systemd-coredump are 
only

intended as a brief summary of the core dump, and detailed debugging
(including use of detached debug symbols) is outside the scope of
systemd-coredump itself.

For more details see .


 Attaching core dump.


FYI that's a stack trace, not a core dump. A core dump is a large 
binary
file, and is not usually useful or desirable to send to bugs (it is 
likely

to contain information that you would prefer to keep confidential).
You can get a more detailed stack trace from the core dump by using
gdb and -dbgsym packages, and that more detailed stack trace is what
maintainers will usually need to be able to act on crash reports.


sudo coredumpctl gdb 1660
thread apply all bt full
with set logging on

gdb.txt attached.

smcv



Thread 10 (Thread 0x7fe7cac4e700 (LWP 1672)):
#0  0x7fe7d662dd2f in __GI___poll (fds=0x7fe7bc001a10, nfds=4, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1  0x7fe7d73a50ae in g_main_context_poll (priority=, 
n_fds=4, fds=0x7fe7bc001a10, timeout=, context=0x7fe7bc00db30) 
at ../../../glib/gmain.c:4216
ret = 
errsv = 
poll_func = 0x7fe7d73b49f0 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 4
allocated_nfds = 
fds = 0x7fe7bc001a10
#2  0x7fe7d73a50ae in g_main_context_iterate (context=0x7fe7bc00db30, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3912
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 4
allocated_nfds = 
fds = 0x7fe7bc001a10
#3  0x7fe7d73a5413 in g_main_loop_run (loop=0x7fe7bc00dc20) at 
../../../glib/gmain.c:4111
__FUNCTION__ = "g_main_loop_run"
#4  0x7fe7d75e9676 in gdbus_shared_thread_func (user_data=0x7fe7bc00db00) 
at ../../../gio/gdbusprivate.c:279
data = 0x7fe7bc00db00
#5  0x7fe7d73cdd1d in g_thread_proxy (data=0x556f93cbaad0) at 
../../../glib/gthread.c:805
thread = 0x556f93cbaad0
__FUNCTION__ = "g_thread_proxy"
#6  0x7fe7d4fd3fb7 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633516074752, 
-1980838052628451829, 140633524463902, 140633524463903, 140633516074752, 
140633516072000, 1967285514314788363, 1967245874865843723}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#7  0x7fe7d66382ef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fe7b3fff700 (LWP 1675)):
#0  0x7fe7d4fd9db5 in futex_wait_cancelable (private=0, expected=0, 
futex_word=0x556f93cd4d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
__ret = -512
oldtype = 0
err = 
spin = 0
buffer = {__routine = 0x7fe7d4fd9b40 <__condvar_cleanup_waiting>, __arg 
= 0x7fe7b3ffea00, __canceltype = 0, __prev = 0x0}
cbuffer = {wseq = 0, cond = 0x556f93cd4d00, mutex = 0x556f93cd4cd8, 
private = 0}
err = 
g = 0
flags = 
g1_start = 
signals = 
result = 0
wseq = 0
seq = 0
private = 0
#1  0x7fe7d4fd9db5 in __pthread_cond_wait_common (abstime=0x0, 
mutex=0x556f93cd4cd8, cond=0x556f93cd4d00) at pthread_cond_wait.c:502
spin = 0
buffer = {__routine = 0x7fe7d4fd9b40 <__condvar_cleanup_waiting>, __arg 
= 0x7fe7b3ffea00, __canceltype = 0, __prev = 0x0}
cbuffer = {wseq = 0, cond = 0x556f93cd4d00, mutex = 0x556f93cd4cd8, 
private = 0}
err = 
g = 0
flags = 
g1_start = 
signals = 
result = 0
wseq = 0
seq = 0
private = 0
#2  0x7fe7d4fd9db5 in __pthread_cond_wait (cond=0x556f93cd4d00, 
mutex=0x556f93cd4cd8) at pthread_cond_wait.c:655
#3  0x7fe7c8734e63 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7fe7c8734bb7 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7fe7d4fd3fb7 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633134069504, 
-1980838052628451829, 140722895835582, 140722895835583, 

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

[Julien Cristau]

On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote:
> I think it is fair to ask Julien as the bug submitter to engage here
> either by coming up with new options that none of us have explored or by
> coming up with specific problems. Alternatively it would be reasonable
> for him to ask someone else who has more time to dedicate to this issue
> to step in.
> 
So one thing I think we should ensure is we don't end up uninstalling
systemd without an explicit user choice.

The "init" package has the "Important: yes" control field which as I
understand it tells apt to behave like "Essential: yes", except for not
trying to install the package if it is not installed.

That's not quite enough for our purposes, because apt would still be
allowed to replace systemd-sysv with sysvinit-core, but maybe
systemd-sysv could get that flag as well?

Julian didn't seem to find the idea crazy when we brought that up on
irc.

Cheers,
Julien

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

[Mark Hindley]

Sam,

On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote:
> > "Mark" == Mark Hindley  writes:
> 
> Mark> Sam, Since I cannot get a working and robust dpkg-divert
> Mark> solution, I feel the need to revisit the validity of these
> Mark> concerns.
> 
> I'd like to push back on the phrasing here.
> What i'm hearing is that after spending a couple of weeks exploring ways
> to meet these concerns, you'd now like to push back on whether they are
> a good idea in the first place.
> That seems dismissive both of Julien's concerns and the engineering
> effort you and others have spent exploring what the valid options are.
> I agree with you that it's time to go back and revisit whether these
> concerns are requirements that we can meet.

I wasn't intending to be dismissive at all. And I apologise if sloppy or
careless use of language on my part gave that impression.

[snip]

> I think it is fair to ask Julien as the bug submitter to engage here
> either by coming up with new options that none of us have explored or by
> coming up with specific problems. Alternatively it would be reasonable
> for him to ask someone else who has more time to dedicate to this issue
> to step in.
> 
> In general, we expect maintainers to respond to RC bugs within two
> weeks.
> I think that in a situation like this it would be reasonable to expect
> Julien to respond within two weeks as well.
> However, for your information, DSA is having some significant hardware
> challenges and I think he is very involved in that.
> I'd recommend being very receptive to a specific request for more time.
> 
> Assuming no response, I think it would be reasonable for you to close
> the bug after the timeout arguing that you have considered the issues
> he brought up, considered alternative designs, and articulated why this
> is the best option.

I am happy with that.

Thank you for your help, advice and facilitation.

Mark

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

[Thorsten Glaser]

Hello Sam,

> What i'm hearing is that after spending a couple of weeks exploring ways
> to meet these concerns, you'd now like to push back on whether they are
> a good idea in the first place.
> That seems dismissive both of Julien's concerns and the engineering

this is a completely wrong summary of what has been discussed,
misleading and shining a bad light on us in a prejudiced way¹.

Please do take the time to read (apparently not re-read) the
mails sent to this bugreport, in which the various solutions
were discussed.

Please do also reread

wrt. the position of the people involved here.


① Perhaps it’s best if someone else gets involved as mediator?

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

**

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

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

**

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

[Sam Hartman]

> "Mark" == Mark Hindley  writes:

Mark> Sam, Since I cannot get a working and robust dpkg-divert
Mark> solution, I feel the need to revisit the validity of these
Mark> concerns.

I'd like to push back on the phrasing here.
What i'm hearing is that after spending a couple of weeks exploring ways
to meet these concerns, you'd now like to push back on whether they are
a good idea in the first place.
That seems dismissive both of Julien's concerns and the engineering
effort you and others have spent exploring what the valid options are.
I agree with you that it's time to go back and revisit whether these
concerns are requirements that we can meet.
But that's exactly because you've spent time working to address the
concerns.  In particular:

* You have explored and documented why libelogind0 needs to be a
  different implementation than libsystemd0: while its API and perhaps
  DBUS interface is the same, its cgroup interface is very different.

* You have explored options for maintaining libsystemd0 and libelogind0
  co-installable and described problems with those approaches: namely
  that there is a significant period on every upgrade where libsystemd0
  will be used rathen than libelogind.  That period will depend on how
  many packages are being unpacked before triggers get run.


I haven't responded to your text because I disagree with your premis.
You seemed to be trying to show that no problem could exist.  Since the
concern raised explicitly included problems caused by our incomplete
understanding of what apt's dependency resolver will do, that's a really
hard thing to do, and I'd expect that if you went down that path it
would involve formal proofs and some model of apt's behavior.

Instead, I think you've done the work to argue that you have the best
option anyone has come up with.  You've explored the other options Simon
and Michael have suggested and explained why they won't work.
You've worked with the Apt developers to resolve the concrete problem
that Simon had with your approach.
In your testing you are not able to  produce particularly bad
situations.

I think it is fair to ask Julien as the bug submitter to engage here
either by coming up with new options that none of us have explored or by
coming up with specific problems. Alternatively it would be reasonable
for him to ask someone else who has more time to dedicate to this issue
to step in.


In general, we expect maintainers to respond to RC bugs within two
weeks.
I think that in a situation like this it would be reasonable to expect
Julien to respond within two weeks as well.
However, for your information, DSA is having some significant hardware
challenges and I think he is very involved in that.
I'd recommend being very receptive to a specific request for more time.

Assuming no response, I think it would be reasonable for you to close
the bug after the timeout arguing that you have considered the issues
he brought up, considered alternative designs, and articulated why this
is the best option.

I won't lie: there are various ways politics  can happn at that point.

I have a couple roles in this:

1) facilitating communications.

2) I'm an experienced Debian Developer.  I'm giving you advice on what
is reasonable process in handling an RC bug.  I don't have any DPL
powers in that regard; other DDs may disagree with me.  If you want to
double check my recommendations with other developers that wouldn't be
bad.  If other developers pop up here, considering their input would be
a good idea.


3) I cannot review specific Release Team decisions.  I do have a role in
reviewing whether the release team is using a reasonable process and
talking to release team members or release managers when I have concerns
about that.  Ultimately, I can ask the project to review a release team
decision if I think the process is unreasonable.  (I have the technical
power to ask the project to review a decision in other circumstances,
but I would be much more reluctant to use that power in a situation
where I thought the process was reasonable than in a situation where I
thought it was not.)

--Sam

Bug#941273: runit: FTBFS (looks like endless loop)

[Ansgar Burchardt]

Package: src:runit
Version: 2.1.2-34
Severity: serious

I noticed that the last runit build is already taking over 13h on
buildds.  The hppa build log[1] looks like the build failed due to an
endless loop.

I asked the other builds to be killed.

Ansgar

  [1] 
https://buildd.debian.org/status/fetch.php?pkg=runit=hppa=2.1.2-34=1569581954=0

Bug#935764: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

[Fabio Fantoni]

Hi, I trying to solve it and do a MR in salsa but I not found a better
way that revert this for now:
https://salsa.debian.org/debian/freeipmi/commit/af06af712350aabb28df359b4e9f0a1a0bfe978d
Someone know a better way please?

Anyway the upload of 1.6.4-1.1 seems don't have the serious issue of
*+b1 dep. so I think we can avoid to autoremove it.

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

[xiao shengwen]

Package: ukwm
Version: 1.1.11-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

ukwm can't start,crash.The dmesg has the following error info:

[  306.124994] ukwm[1159]: segfault at 38 ip b5b57084 sp bf9b2d0c error 4 in 
libukwm-cogl-1.so[b5b19000+68000]
[  306.125015] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85 c0 74 
02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24 04 <8b> 40 38 
c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4

I run ukwm on console,It has display the following error:   

InitDBusCommunicationServer: Server started.
name_acquired_cb call, Acquired bus name: org.ukui.ukwm.UkwmPlugin.
Gtk-Message: 19:01:46.511: Failed to load module "topmenu-gtk-module"
Window manager warning: Failed to allocate shadow texture: Failed to create 
texture 2d due to size/format constraints
Window manager warning: Failed to allocate shadow texture: Failed to create 
texture 2d due to size/format constraints
段错误


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-6-686 (SMP w/1 CPU core)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ukwm depends on:
ii  gsettings-desktop-schemas  3.28.1-1
ii  libc6  2.28-10
ii  libglib2.0-0   2.58.3-2+deb10u1
ii  libukwm-1-01.1.11-1+b1
ii  libx11-6   2:1.6.7-1
ii  libxcomposite1 1:0.4.4-2
ii  libxrandr2 2:1.5.1-1
ii  ukui-settings-daemon   1.1.7-2
ii  ukwm-common1.1.11-1
ii  zenity 3.30.0-2

Versions of packages ukwm recommends:
ii  ukui-window-switch  1.1.2-1

Versions of packages ukwm suggests:
ii  ukui-control-center  1.1.6-2
ii  xdg-user-dirs0.17-2

-- no debconf information

The whole dmesg:

[0.00] Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
[0.00] Disabled fast string operations
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000d8000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1f6d] usable
[0.00] BIOS-e820: [mem 0x1f6e-0x1f6ebfff] ACPI data
[0.00] BIOS-e820: [mem 0x1f6ec000-0x1f6f] ACPI NVS
[0.00] BIOS-e820: [mem 0x1f70-0x1fff] reserved
[0.00] BIOS-e820: [mem 0xfec1-0xfec1] reserved
[0.00] BIOS-e820: [mem 0xff80-0xffbf] reserved
[0.00] BIOS-e820: [mem 0xfc00-0x] reserved
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] SMBIOS 2.3 present.
[0.00] DMI: Sony Corporation VGN-B99C, BIOS R0042G9 01/19/2005
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 1587.905 MHz processor
[0.019677] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.019682] e820: remove [mem 0x000a-0x000f] usable
[0.019693] last_pfn = 0x1f6e0 max_arch_pfn = 0x10
[0.019702] MTRR default type: uncachable
[0.019704] MTRR fixed ranges enabled:
[0.019707]   0-9 write-back
[0.019709]   A-B uncachable
[0.019710]   C-C7FFF write-protect
[0.019712]   C8000-E uncachable
[0.019714]   F-F write-protect
[0.019716] MTRR variable ranges enabled:
[0.019718]   0 base 0 mask FE000 write-back
[0.019721]   1 base 01F70 mask 0 uncachable
[0.019723]   2 base 01F80 mask FFF80 uncachable
[0.019724]   3 disabled
[0.019725]   4 disabled
[0.019727]   5 disabled
[0.019728]   6 disabled
[0.019729]   7 disabled
[0.020403] x86/PAT: PAT not supported by CPU.
[0.020572] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[0.045264] initial memory mapped: [mem 0x-0x0dff]
[0.045327] BRK [0x0daaf000, 0x0daa] PGTABLE
[0.045358] RAMDISK: [mem 0x1c7a5000-0x1e9cbfff]
[0.045369] ACPI: Early table checksum verification disabled
[0.046070] ACPI: RSDP 0x000F69B0 14 (v00 SONY  )
[0.046076] ACPI: RSDT 0x1F6E79DF 30 (v01 SONY   G9   
20050119 PTL  )
[0.046087] ACPI: FACP 0x1F6EBEC2 84 (v02 SONY   G9   
20050119 PTL  0050)
[0.046098] ACPI: DSDT 0x1F6E7E7B 004047 (v01 SONY   G9  

Bug#940678: Please import pools by stable device label

[Antonio Russo]

Could you please clarify: did you experience any data loss, or were you simply 
unable to import your pool at one point?

As a second note, you should have done something like

zpool import -d /dev/disks/by-id -a

so that your import is done by labels that are stable across boots (names like 
/dev/sdX are not necessarily stable). This is a "well-known" best
practice with ZFS [1] (you should always create pools using these symlinks as 
well).

If you have only experienced an inability to import your pool at boot, my guess 
is that you had (and continue to have) the inappropriate
import by device node setup. This configuration error will lead to you 
continuing to have problems importing your pool at later times,
and is not a bug. To fix that problem you should zpool export all your pools 
(this might be tricky, especially if you are zfs on root),
and then run the above command. As always, double check all this!

If you did NOT experience any data loss, could you please lower the severity of 
this bug? And if my above analysis of your pool setup is
correct, could you please close this bug report?

Thank you,
Antonio

[1] 
https://github.com/zfsonlinux/zfs/wiki/faq#selecting-dev-names-when-creating-a-pool

Processed: reassign 941264 to php-cache-lite

[Debian Bug Tracking System]

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

> reassign 941264 php-cache-lite 1.8.2-1
Bug #941264 [src:phpunit, src:php-cache-lite] phpunit breaks php-cache-lite 
autopkgtest: tries to write to /usr/bin/.phpunit.result.cache
Bug reassigned from package 'src:phpunit, src:php-cache-lite' to 
'php-cache-lite'.
No longer marked as found in versions php-cache-lite/1.8.2-1 and 
phpunit/8.3.5-1.
Ignoring request to alter fixed versions of bug #941264 to the same values 
previously set
Bug #941264 [php-cache-lite] phpunit breaks php-cache-lite autopkgtest: tries 
to write to /usr/bin/.phpunit.result.cache
Marked as found in versions php-cache-lite/1.8.2-1.
> thanks
Stopping processing here.

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

Bug#941264: phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache

[Paul Gevers]

Control: reassign 941264 php-cache-lite/1.8.2-1

Hi,

Normally I check the bts for bugs, but it slipped. There is bug #940275
already.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#941264: phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache

[Paul Gevers]

Source: phpunit, php-cache-lite
Control: found -1 phpunit/8.3.5-1
Control: found -1 php-cache-lite/1.8.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of phpunit the autopkgtest of php-cache-lite fails
in testing when that autopkgtest is run with the binary packages of
phpunit from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
phpunitfrom testing8.3.5-1
php-cache-lite from testing1.8.2-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the
test now tries to write in /usr/bin, which is obviously not good.

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

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
phpunit/8.3.5-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=phpunit

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-cache-lite/3027486/log.gz

autopkgtest [02:12:32]: test command1: [---
PHPUnit 8.3.5 by Sebastian Bergmann and contributors.

  24 /
24 (100%)PHP Warning:
file_put_contents(/usr/bin/.phpunit.result.cache): failed to open
stream: Permission denied in
/usr/share/php/PHPUnit/Runner/DefaultTestResultCache.php on line 108


Time: 15.44 seconds, Memory: 4.00 MB

OK (24 tests, 30 assertions)
autopkgtest [02:12:48]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Processed: phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache

[Debian Bug Tracking System]

Processing control commands:

> found -1 phpunit/8.3.5-1
Bug #941264 [src:phpunit, src:php-cache-lite] phpunit breaks php-cache-lite 
autopkgtest: tries to write to /usr/bin/.phpunit.result.cache
Marked as found in versions phpunit/8.3.5-1.
> found -1 php-cache-lite/1.8.2-1
Bug #941264 [src:phpunit, src:php-cache-lite] phpunit breaks php-cache-lite 
autopkgtest: tries to write to /usr/bin/.phpunit.result.cache
Marked as found in versions php-cache-lite/1.8.2-1.

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

Bug#915646: FTBFS: haddock: internal error: internal: extractDecl

[Gianfranco Costamagna]

control: severity -1 important

I'm downgrading because I pushed a package without the -doc build

G.
On Wed, 5 Dec 2018 17:10:19 +0200 Ilias Tsitsimpis  wrote:
> Source: haskell-esqueleto
> Version: 2.5.3.git20180402-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> libghc-esqueleto-doc FTBFS with the following error:
> 
>haddock: internal error: internal: extractDecl
> 
> This is most probably a Haddock bug[1], fixed in a newer version of GHC.
> 
> On the other hand, haskell-esqueleto is not currently needed, is not
> part of the latest LTS, and Debian uses an unpublished snapshot of the
> code[2]. Should we remove this package from Debian?
> 
> [1] https://github.com/haskell/haddock/issues/775
> [2] https://github.com/bitemyapp/esqueleto/issues/105
> 
> -- 
> Ilias
> 
> 

Processed: Re: FTBFS: haddock: internal error: internal: extractDecl

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #915646 [src:haskell-esqueleto] FTBFS: haddock: internal error: internal: 
extractDecl
Severity set to 'important' from 'serious'

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

Processed: found 940963 in 2:4.10.8+dfsg-1, affects 940963

[Debian Bug Tracking System]

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

> found 940963 2:4.10.8+dfsg-1
Bug #940963 [samba-common-bin] samba doesn't start anymore
Marked as found in versions samba/2:4.10.8+dfsg-1.
> affects 940963 src:cups src:tdb
Bug #940963 [samba-common-bin] samba doesn't start anymore
Added indication that 940963 affects src:cups and src:tdb
> thanks
Stopping processing here.

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

Bug#925779: marked as done (mlpack: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 27 Sep 2019 08:35:27 +
with message-id 
and subject line Bug#925779: fixed in mlpack 3.2.0-1
has caused the Debian Bug report #925779,
regarding mlpack: 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.)


-- 
925779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mlpack
Version: 3.0.4-1
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/mlpack_3.0.4-1_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.

[...]
make -f src/mlpack/methods/det/CMakeFiles/mlpack_det.dir/build.make 
src/mlpack/methods/det/CMakeFiles/mlpack_det.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 27%] Building CXX object 
src/mlpack/methods/det/CMakeFiles/mlpack_det.dir/det_main.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/mlpack/methods/det && /usr/bin/c++ 
 -DARMA_NO_DEBUG -DBOOST_TEST_DYN_LINK -DHAS_OPENMP -DNDEBUG 
-I/<>/src -I/<>/obj-x86_64-linux-gnu/src/mlpack/..  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-ftemplate-depth=1000 -O3 -fopenmp   -DBINDING_TYPE=BINDING_TYPE_CLI 
-std=gnu++11 -o CMakeFiles/mlpack_det.dir/det_main.cpp.o -c 
/<>/src/mlpack/methods/det/det_main.cpp
In file included from /<>/src/mlpack/methods/det/dt_utils.hpp:147,
 from /<>/src/mlpack/methods/det/det_main.cpp:15:
/<>/src/mlpack/methods/det/dt_utils_impl.hpp: In function 
'mlpack::det::DTree* mlpack::det::Trainer(MatType&, size_t, 
bool, size_t, size_t, bool) [with MatType = arma::Mat; TagType = int]':
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:189:3: error: 'folds' 
not specified in enclosing 'parallel'
  189 |   for (omp_size_t fold = 0; fold < (omp_size_t) folds; fold++)
  |   ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:187:11: error: 
enclosing 'parallel'
  187 |   #pragma omp parallel for default(none) \
  |   ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:192:33: error: 
'testSize' not specified in enclosing 'parallel'
  192 | const size_t start = fold * testSize;
  | ^~~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:187:11: error: 
enclosing 'parallel'
  187 |   #pragma omp parallel for default(none) \
  |   ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:194:61: error: 
'cvData' not specified in enclosing 'parallel'
  194 | * testSize, (size_t) cvData.n_cols);
  |  ~~~^~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:187:11: error: 
enclosing 'parallel'
  187 |   #pragma omp parallel for default(none) \
  |   ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:222:5: error: 
'minLeafSize' not specified in enclosing 'parallel'
  222 | cvDTree.Grow(train, cvOldFromNew, useVolumeReg, maxLeafSize,
  | ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:187:11: error: 
enclosing 'parallel'
  187 |   #pragma omp parallel for default(none) \
  |   ^~~
/<>/src/mlpack/methods/det/dt_utils_impl.hpp:222:5: error: 
'maxLeafSize' not specified in enclosing 'parallel'
  222 | cvDTree.Grow(train, 

Processed: tagging 941249

[Debian Bug Tracking System]

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

> tags 941249 + pending
Bug #941249 [virt-manager] virt-manager: Can not open detail of connection and 
detail or console of a VM
Ignoring request to alter tags of bug #941249 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#941249: [Pkg-libvirt-maintainers] Bug#941249: virt-manager: Can not open detail of connection and detail or console of a VM

[Guido Günther]

Hi,
On Fri, Sep 27, 2019 at 07:59:16AM +0200, Sebastien Helleu wrote:
> Package: virt-manager
> Version: 1:2.2.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more 
> detail of connection, or detail/console of a VM, no window is open when I 
> click or if I select Open in the menu.
> 
> Here's the output of virt-manager --debug --no-fork:
> 
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (cli:208) Launched 
> with command line: /usr/share/virt-manager/virt-manager --debug --no-fork
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:223) 
> virt-manager version: 2.2.1
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:224) 
> virtManager import:  '/usr/share/virt-manager/virtManager/__init__.py'>
> 
> (virt-manager:2944): dbind-WARNING **: 07:56:10.508: Couldn't connect to 
> accessibility bus: Failed to connect to socket /tmp/dbus-0YN5eotkNt: 
> Connexion refusée
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:274) 
> PyGObject version: 3.34.0
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:278) GTK 
> version: 3.24.11
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (systray:213) Showing 
> systray: False
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (inspection:41) python 
> guestfs is not installed
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:116) Loading 
> stored URIs:
> qemu+ssh://shelleu@10.10.43.16/system  
> qemu:///system
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:537) 
> processing cli command uri= show_window=manager domain=
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:539) No cli 
> action requested, launching default window
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (manager:184) Showing 
> manager
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:391) window 
> counter incremented to 1
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:285) Initial 
> gtkapplication activated
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:533) 
> conn=qemu:///system changed to state=Connexion
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:946) 
> Scheduling background open thread for qemu:///system
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:986) 
> libvirt version=5006000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:988) 
> daemon version=5006000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:989) conn 
> version=4001000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:991) 
> qemu:///system capabilities:
> 
> 
>   
> eef59000-6784---
> 
>   x86_64
>   Westmere
>   Intel
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> 
>   
>   
>   
> 
> 
> 
>   
>   
> tcp
> rdma
>   
> 
> 
>   
> 
>   3959980
>   989995
>   0
>   0
>   
> 
>   
>   
> 
> 
> 
> 
>   
> 
>   
> 
> 
>   
> 
> 
>   none
>   0
> 
> 
>   dac
>   0
>   +101:+112
>   +101:+112
> 
>   
> 
>   
> hvm
> 
>   64
>   /usr/bin/qemu-system-alpha
>   clipper
>   
> 
> 
>   
>   
>   
> 
>   
> 
>   
> hvm
> 
>   32
>   /usr/bin/qemu-system-arm
>   integratorcp
>   versatileab
>   smdkc210
>   nuri
>   palmetto-bmc
>   microbit
>   mainstone
>   canon-a1100
>   terrier
>   n800
>   verdex
>   kzm
>   versatilepb
>   midway
>   virt-2.7
>   emcraft-sf2
>   mcimx7d-sabre
>   highbank
>   imx25-pdk
>   n810
>   virt-2.11
>   realview-pbx-a9
>   tosa
>   sx1-v1
>   swift-bmc
>   mps2-an511
>   musca-a
>   realview-pb-a8
>   sabrelite
>   akita
>   cubieboard
>   virt-2.9
>   xilinx-zynq-a9
>   virt-3.1
>   vexpress-a15
>   virt-4.1
>   virt
>   musca-b1
>   mps2-an521
>   realview-eb
>   cheetah
>   vexpress-a9
>   virt-2.6
>   mps2-an505
>   spitz
>   netduino2
>   lm3s6965evb
>   virt-2.10
>   lm3s811evb
>   z2
>   raspi2
>   connex
>   borzoi
>   mcimx6ul-evk
>   

Bug#941249: marked as pending in virt-manager

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #941249 in virt-manager 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/libvirt-team/virt-manager/commit/667db917a46e88d56249b43b58248f8e5c764118


d/control: Depend on gir1.2-gtksource-4

Closes: #941249


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941249

Processed: Bug#941249 marked as pending in virt-manager

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941249 [virt-manager] virt-manager: Can not open detail of connection and 
detail or console of a VM
Added tag(s) pending.

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

Bug#941249: virt-manager: Can not open detail of connection and detail or console of a VM

[Laurent Bigonville]

On Fri, 27 Sep 2019 07:59:16 +0200 Sebastien Helleu 
 wrote:



[ven., 27 sept. 2019 07:56:12 virt-manager 2944] DEBUG (cli:200) Uncaught 
exception:
Traceback (most recent call last):
   File "/usr/share/virt-manager/virtManager/xmleditor.py", line 11, in 
 gi.require_version("GtkSource", "4")
   File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
 raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
   File "/usr/share/virt-manager/virtManager/manager.py", line 489, in 
row_activated
 self.show_vm(_src)
   File "/usr/share/virt-manager/virtManager/manager.py", line 474, in show_vm
 vmmenu.VMActionUI.show(self, self.current_vm())
   File "/usr/share/virt-manager/virtManager/vmmenu.py", line 329, in show
 from .vmwindow import vmmVMWindow
   File "/usr/share/virt-manager/virtManager/vmwindow.py", line 15, in 
 from .details.details import vmmDetails
   File "/usr/share/virt-manager/virtManager/details/details.py", line 18, in 

 from ..addhardware import vmmAddHardware
   File "/usr/share/virt-manager/virtManager/addhardware.py", line 23, in 

 from .device.fsdetails import vmmFSDetails
   File "/usr/share/virt-manager/virtManager/device/fsdetails.py", line 14, in 

 from ..storagebrowse import vmmStorageBrowser
   File "/usr/share/virt-manager/virtManager/storagebrowse.py", line 11, in 

 from .hoststorage import vmmHostStorage
   File "/usr/share/virt-manager/virtManager/hoststorage.py", line 16, in 

 from .createpool import vmmCreatePool
   File "/usr/share/virt-manager/virtManager/createpool.py", line 19, in 

 from .xmleditor import vmmXMLEditor
   File "/usr/share/virt-manager/virtManager/xmleditor.py", line 14, in 
 gi.require_version("GtkSource", "3.0")
   File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
 raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available


Looking at the code it's missing a dependency against the 
gir1.2-gtksource-4 package

Bug#940723: java-package requires libgtk-3-0 and libcairo-gobject2 to build java8 221

[Emmanuel Bourg]

Control: severity -1 normal

Processed: Re: java-package requires libgtk-3-0 and libcairo-gobject2 to build java8 221

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #940723 [java-package] java-package requires libgtk-3-0 and 
libcairo-gobject2 to build java8 221
Severity set to 'normal' from 'serious'

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

Processed: not yet fixed in upstream

[Debian Bug Tracking System]

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

> tag 941018 - fixed-upstream
Bug #941018 [ibus] ibus: Regression from CVE-2019-14822 fix: does not work with 
qt5 applications
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#941249: virt-manager: Can not open detail of connection and detail or console of a VM

[Sebastien Helleu]

Package: virt-manager
Version: 1:2.2.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more detail 
of connection, or detail/console of a VM, no window is open when I click or if 
I select Open in the menu.

Here's the output of virt-manager --debug --no-fork:

[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (cli:208) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:223) 
virt-manager version: 2.2.1
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:224) 
virtManager import: 

(virt-manager:2944): dbind-WARNING **: 07:56:10.508: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-0YN5eotkNt: Connexion 
refusée
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:274) 
PyGObject version: 3.34.0
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:278) GTK 
version: 3.24.11
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (systray:213) Showing 
systray: False
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (inspection:41) python 
guestfs is not installed
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:116) Loading 
stored URIs:
qemu+ssh://shelleu@10.10.43.16/system  
qemu:///system
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:537) processing 
cli command uri= show_window=manager domain=
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:539) No cli 
action requested, launching default window
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (manager:184) Showing 
manager
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:391) window 
counter incremented to 1
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:285) Initial 
gtkapplication activated
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:533) 
conn=qemu:///system changed to state=Connexion
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:946) 
Scheduling background open thread for qemu:///system
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:986) libvirt 
version=5006000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:988) daemon 
version=5006000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:989) conn 
version=4001000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:991) 
qemu:///system capabilities:


  
eef59000-6784---

  x86_64
  Westmere
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  



  
  
tcp
rdma
  


  

  3959980
  989995
  0
  0
  

  
  




  

  


  


  none
  0


  dac
  0
  +101:+112
  +101:+112

  

  
hvm

  64
  /usr/bin/qemu-system-alpha
  clipper
  


  
  
  

  

  
hvm

  32
  /usr/bin/qemu-system-arm
  integratorcp
  versatileab
  smdkc210
  nuri
  palmetto-bmc
  microbit
  mainstone
  canon-a1100
  terrier
  n800
  verdex
  kzm
  versatilepb
  midway
  virt-2.7
  emcraft-sf2
  mcimx7d-sabre
  highbank
  imx25-pdk
  n810
  virt-2.11
  realview-pbx-a9
  tosa
  sx1-v1
  swift-bmc
  mps2-an511
  musca-a
  realview-pb-a8
  sabrelite
  akita
  cubieboard
  virt-2.9
  xilinx-zynq-a9
  virt-3.1
  vexpress-a15
  virt-4.1
  virt
  musca-b1
  mps2-an521
  realview-eb
  cheetah
  vexpress-a9
  virt-2.6
  mps2-an505
  spitz
  netduino2
  lm3s6965evb
  virt-2.10
  lm3s811evb
  z2
  raspi2
  connex
  borzoi
  mcimx6ul-evk
  musicpal
  virt-2.8
  ast2500-evb
  virt-3.0
  sx1
  realview-eb-mpcore
  witherspoon-bmc
  romulus-bmc
  virt-4.0
  mps2-an385
  virt-2.12
  collie
  


  
  
  

  

  
hvm

  32
  /usr/bin/qemu-system-arm
  integratorcp
  versatileab
  smdkc210
  nuri
  palmetto-bmc
  microbit
  mainstone
  canon-a1100
  terrier
  n800
  verdex
  kzm
  versatilepb
  midway
  virt-2.7
  emcraft-sf2
  mcimx7d-sabre
  highbank