Bug#891063:

[Rob Browning]

Vincent Lefevre  writes:

> The current workaround is to unset XDG_RUNTIME_DIR completely (this is
> sufficient for Emacs and doesn't affect dbus), but this might yield
> other issues and bug reports...
>
> But in any case, the bug needs to be fixed.

Perhaps, but I don't have the impression that this is an emacs bug, or
at least not specifically an emacs bug until/unless running arbitrary
gtk apps via "su" is an expected, and explicitly supported arrangement.

Right now, I suspect it's not in general.

i.e. I suspect that to do what it sounds like you'd prefer, you'll need
to pursue adoption of a broader policy, which may well involve
coordination with the su developers, gtk developers, and perhaps some
number of other libraries.

Otherwise, I suspect you'll end up playing version-to-version
whac-a-mole with various dependencies.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#906003: Keep plowshare-modules out of Debian releases

[Carl Suster]

Package: plowshare-modules
Severity: serious
Justification: none

The plowshare-modules package contains scripts that need frequent replacing to
keep pace with changes to the websites supported by the scripts since those
sites make frequent changes.

The main package plowshare contains a script (plowmod) to maintain a user-local
copy of the modules, and tools to write your own modules. Upstream treated this
as the preferred way to install and discouraged package maintainers from
packaging the modules at all after they were split into a different upstream
repository and designated as "unofficial".

Given this I don't think it makes sense to keep plowshare-modules in Debian
releases. Plowshare itself can stay (and changes only infrequently upstream),
but the user should install the modules with the plowmod script.

I will still try to update the modules package for unstable periodically, but
this RC bug is to stop that effort from migrating to testing.



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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.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 plowshare-modules depends on:
pn  plowshare  

plowshare-modules recommends no packages.

plowshare-modules suggests no packages.

Bug#905999: marked as done (quantlib-python: missing dependency on python3)

[Debian Bug Tracking System]

Your message dated Mon, 13 Aug 2018 00:05:20 +
with message-id 
and subject line Bug#905999: fixed in quantlib-swig 1.13-1
has caused the Debian Bug report #905999,
regarding quantlib-python: missing dependency on python3
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.)


-- 
905999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quantlib-python
Version: 1.12-1
Severity: serious
Tags: patch

Fix:

--- debian/rules.old2018-08-12 21:38:27.803119469 +
+++ debian/rules2018-08-12 21:38:38.571119366 +
@@ -202,7 +202,7 @@
 #  dh_suidregister
 #  dh_pycentral-p$(pypackage)
 #  dh_python   -p$(pypackage)
-   dh_python2 
+   dh_python3
dh_makeshlibs
dh_installdeb
dh_shlibdeps
--- End Message ---
--- Begin Message ---
Source: quantlib-swig
Source-Version: 1.13-1

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated quantlib-swig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 12 Aug 2018 18:27:34 -0500
Source: quantlib-swig
Binary: quantlib-python
Architecture: source amd64
Version: 1.13-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 quantlib-python - Python3 bindings for the Quantlib Quantitative Finance 
library
Closes: 905999
Changes:
 quantlib-swig (1.13-1) unstable; urgency=medium
 .
   * New upstream release
 .
   * debian/rules: Call dh_python (thanks, Adrian Bunk)  (Closes: #905999)
Checksums-Sha1:
 e687d9725b0142cbbc8b2545dd6cf2cdcac7230b 1826 quantlib-swig_1.13-1.dsc
 d3b41a63f8217766a60de0010528607b09595115 4238649 quantlib-swig_1.13.orig.tar.gz
 e92a6b0d32e087aef2616cdfe5e96370825e17dc 9620 
quantlib-swig_1.13-1.debian.tar.xz
 451e302ffcd46c9fc440520c2d16e4a66a079f61 23949500 
quantlib-python-dbgsym_1.13-1_amd64.deb
 d17f217f80629bff3afe7af3a961b7a112beb814 2354336 
quantlib-python_1.13-1_amd64.deb
 b590898f0b9152390cb391aaec4f50a8f7dc311d 7074 
quantlib-swig_1.13-1_amd64.buildinfo
Checksums-Sha256:
 674629aa90d8c876137695a36401daa035a7c758f181f14feb5bbbd729167e0a 1826 
quantlib-swig_1.13-1.dsc
 0ab99d6a43b2a204d6366fb600aa3cd049ee29e1d0406fefaedcc0f4fd9c65c2 4238649 
quantlib-swig_1.13.orig.tar.gz
 832c144a485fb993a897f48520fc4bf669f8b0af3dfcb8a37263e773ea177ef5 9620 
quantlib-swig_1.13-1.debian.tar.xz
 455144eac1ddee45ff1a3e1c4b7cfb9c6be82bb0c4e5ec37c41fd903406ce361 23949500 
quantlib-python-dbgsym_1.13-1_amd64.deb
 7fb4bfe08b2790d5919695e48998f7b5d0a0eb634ad181636541e7e9c21b7fcd 2354336 
quantlib-python_1.13-1_amd64.deb
 7f6e352d1266b2553fd11d9edaa7a60928a7b2234c93939a3186498bd692d07b 7074 
quantlib-swig_1.13-1_amd64.buildinfo
Files:
 1baf09b3aa99d2985c7a232c4b4d4e1f 1826 interpreters optional 
quantlib-swig_1.13-1.dsc
 5c20f91a798de4cd1cd6065621420b36 4238649 interpreters optional 
quantlib-swig_1.13.orig.tar.gz
 851114a1e2f56396c7db7c74ea1d357e 9620 interpreters optional 
quantlib-swig_1.13-1.debian.tar.xz
 71fe55914c6b2c21290a5950cf4dc178 23949500 debug optional 
quantlib-python-dbgsym_1.13-1_amd64.deb
 78c3a695b5e2d464b18e7e98264ea6ed 2354336 python optional 
quantlib-python_1.13-1_amd64.deb
 753aa3b79768002d5946d8e15f3ff077 7074 interpreters optional 
quantlib-swig_1.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBW3DFxKFIn+KrmaIaAQgP3Q/9Fxi6rkV+Ox7IS1hJjvGc39BvJB7Ieluz
4ZuX2CS3bAbA2+jTV8fvNZGNGEU92K5uF9ageQvFu/PcTfrsWxZcnZ4Uk8L8eofJ
any7flupKQ4JuyYa6mlBHxyNnRvohc0RaUt643qpmkwcFP4/YfbXqAv4C4IVFZCj
7SiA7zAKpFKJN0YuAFWYq8vFO2amShyHwSmYNb+TDW0xxCbrm//DL6Y6xRS7TimD
gdIFucl+FqDrySSNIap+u7j7dITXeBTNPW84UqEmmJbYFEvm9pzSntszWdVJNO5L
+Ig+Hxxt3qI2PydxHh1S539was2Fn/5KXmeuC0tLLaO33yDIiEr7p7VueOc+QYiw
LEIARl0OxwMcJrbKYinv9qH7Os82hhe4ikyqX4tkeDksyGZ4GzgDh/f+GXpgPSuu
v0tzXewChuvk/Eg1FISygYwQysMDJy4/ddDCYm3Zd4CK92Wj0e3C83dlg6kr1P0u
HFEf6R8nJWICPrYP2nsquSlRUoZ9Slkd/hwyzWwKCsuJpWAl+kuIcGlHw6VCKPE2
A36PwqY6On2

Bug#891063:

[Vincent Lefevre]

On 2018-08-12 17:33:22 -0500, Rob Browning wrote:
> Vincent Lefevre  writes:
> > The answer is to build Emacs with "--without-gsettings".
> 
> That's not how I read the thread, or rather it sounded like they were
> saying that it's not a general solution, but it might be fine for a
> custom build for you.
> 
> i.e. I read the thread more as emacs is "working as designed" for
> current libraries, desktops, etc.

Well, there's a bug, and this bug must be fixed somewhere, by building
emacs with --without-gsettings if not fixed anywhere else.

For GNOME users, GNOME has its own editor anyway.

> But if you want --without-gsettings, then perhaps you could just switch
> to the emacs-lucid or emacs-nox packages, they've been building
> --without-gsettings since 24.3+1-2.  (Though I suspect you may well hit
> other similar problems in the long run.)

I want an X interface, so that emacs-nox is not OK. I had used the
lucid version in the past when Emacs was affected by a GTK bug, but
IIRC, there were some rendering issues of this interface. Moreover,
emacs-lucid cannot be installed due to a conflict with emacs-calfw.

> Alternately, you could "apt build-dep emacs25" (or emacs-gtk if you're
> using sid), and "fakeroot debian/rules binary" after adjusting the
> debian/rules confflags to build your own gtk version
> --without-gsettings.

Yes, but that's annoying.

> Or, as I've seen suggested elsewhere, you might consider switching from
> the potentially fraught approach of using su, to a tramp or sudoedit
> based approach (since it doesn't sound like emacs upstream expects the
> su approach to ever necessarily avoid this kind of issue -- gsettings or
> not).

I often need to do other things from root (e.g. daemon stop/start),
not just edit files.

The current workaround is to unset XDG_RUNTIME_DIR completely (this is
sufficient for Emacs and doesn't affect dbus), but this might yield
other issues and bug reports...

But in any case, the bug needs to be fixed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#905999: quantlib-python: missing dependency on python3

[Dirk Eddelbuettel]

On 13 August 2018 at 01:24, Adrian Bunk wrote:
| Package: quantlib-python
| Version: 1.12-1
| Severity: serious
| Tags: patch
| 
| Fix:
| 
| --- debian/rules.old  2018-08-12 21:38:27.803119469 +
| +++ debian/rules  2018-08-12 21:38:38.571119366 +
| @@ -202,7 +202,7 @@
|  #dh_suidregister
|  #dh_pycentral-p$(pypackage)
|  #dh_python   -p$(pypackage)
| - dh_python2 
| + dh_python3
|   dh_makeshlibs
|   dh_installdeb
|   dh_shlibdeps

Thanks, will fix.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: Re: Bug#897878: ucommon: diff for NMU version 7.0.0-12.1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #897878 {Done: Bernhard Schmidt } [src:ucommon] ucommon: 
ftbfs with GCC-8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ucommon/7.0.0-13.
> notfixed -1 7.0.0-13
Bug #897878 [src:ucommon] ucommon: ftbfs with GCC-8
The source 'ucommon' and version '7.0.0-13' do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #897878 to the same values 
previously set

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

Bug#897878: ucommon: diff for NMU version 7.0.0-12.1

[Bernhard Schmidt]

Control: reopen -1
Control: notfixed -1 7.0.0-13

On 13.08.2018 00:05, Bernhard Schmidt wrote:
> On 12.08.2018 19:20, Adrian Bunk wrote:
>> Control: tags 897878 + patch
>> Control: tags 897878 + pending
>> Control: tags 898502 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for ucommon (versioned as 7.0.0-12.1) and uploaded 
>> it to DELAYED/15. Please feel free to tell me if I should cancel it.
>>
> 
> Thanks, I've incorporated your fixes into the Vcs and team-uploaded -13
> with an update for salsa. Should hit the archive shortly.

Bah, so it looks like 32bit arches are still failing with different
symbols. Patches welcome.

Bernhard

Bug#891063:

[Rob Browning]

Vincent Lefevre  writes:

> The answer is to build Emacs with "--without-gsettings".

That's not how I read the thread, or rather it sounded like they were
saying that it's not a general solution, but it might be fine for a
custom build for you.

i.e. I read the thread more as emacs is "working as designed" for
current libraries, desktops, etc.

But if you want --without-gsettings, then perhaps you could just switch
to the emacs-lucid or emacs-nox packages, they've been building
--without-gsettings since 24.3+1-2.  (Though I suspect you may well hit
other similar problems in the long run.)

Alternately, you could "apt build-dep emacs25" (or emacs-gtk if you're
using sid), and "fakeroot debian/rules binary" after adjusting the
debian/rules confflags to build your own gtk version
--without-gsettings.

Or, as I've seen suggested elsewhere, you might consider switching from
the potentially fraught approach of using su, to a tramp or sudoedit
based approach (since it doesn't sound like emacs upstream expects the
su approach to ever necessarily avoid this kind of issue -- gsettings or
not).

Hope this helps
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#906000: etckeeper: missing dependency on python

[Adrian Bunk]

Package: etckeeper
Version: 1.18.7-1
Severity: serious

etckeeper installs a Python module but no longer
has a python dependency.

Bug#905999: quantlib-python: missing dependency on python3

[Adrian Bunk]

Package: quantlib-python
Version: 1.12-1
Severity: serious
Tags: patch

Fix:

--- debian/rules.old2018-08-12 21:38:27.803119469 +
+++ debian/rules2018-08-12 21:38:38.571119366 +
@@ -202,7 +202,7 @@
 #  dh_suidregister
 #  dh_pycentral-p$(pypackage)
 #  dh_python   -p$(pypackage)
-   dh_python2 
+   dh_python3
dh_makeshlibs
dh_installdeb
dh_shlibdeps

Bug#897878: marked as done (ucommon: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 22:20:32 +
with message-id 
and subject line Bug#897878: fixed in ucommon 7.0.0-13
has caused the Debian Bug report #897878,
regarding ucommon: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ucommon
Version: 7.0.0-12
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/ucommon_7.0.0-12_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html

[...]
make[2]: Leaving directory '/<>/utils'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/usr/share/ucommon/cmake'
 /usr/bin/install -c -m 644 cmake/CapeConfig.cmake cmake/CapeMakeTargets.cmake 
'/<>/debian/tmp/usr/share/ucommon/cmake'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 ucommon-config.1 commoncpp-config.1 
'/<>/debian/tmp/usr/share/man/man1'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 ucommon.pc commoncpp.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c ucommon-config commoncpp-config 
'/<>/debian/tmp/usr/bin'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -a
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
dh_installdocs --exclude=.map --exclude=.md5
make[1]: Leaving directory '/<>'
   dh_installchangelogs -a
   dh_installman -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   debian/rules override_dh_strip
make[1]: Entering directory '/<>'
dh_strip --dbgsym-migration='libucommon8-dbg (<< 7.0.0-7~)'
make[1]: Leaving directory '/<>'
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libucommon8/DEBIAN/symbols doesn't match 
completely debian/libucommon8.symbols
--- debian/libucommon8.symbols (libucommon8_7.0.0-12_amd64)
+++ dpkg-gensymbolsjqszvZ   2018-05-02 13:05:46.327397688 +
@@ -14,6 +14,9 @@
  (c++)"VTT for ost::TTYStream@Base" 7.0.0
  (c++)"VTT for ost::ThreadQueue@Base" 7.0.0
  (c++)"VTT for ost::ttystream@Base" 7.0.0
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 7.0.0-12
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 7.0.0-12
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3ost4Slog5LevelEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 7.0.0-12
  (c++)"non-virtual thunk to ost::AppLog::~AppLog()@Base" 7.0.0
  (c++)"non-virtual thunk to ost::SerialService::~SerialService()@Base" 7.0.0
  (c++)"non-virtual thunk to ost::SharedMemPager::~SharedMemPager()@Base" 7.0.0
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:11: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2
--- End Message ---
--- Begin Message ---
Source: ucommon
Source-Version: 7.0.0-13

We believe that the bug you reported is fixed in the latest version of
ucommon, w

Bug#897878: ucommon: diff for NMU version 7.0.0-12.1

[Bernhard Schmidt]

On 12.08.2018 19:20, Adrian Bunk wrote:
> Control: tags 897878 + patch
> Control: tags 897878 + pending
> Control: tags 898502 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for ucommon (versioned as 7.0.0-12.1) and uploaded 
> it to DELAYED/15. Please feel free to tell me if I should cancel it.
> 

Thanks, I've incorporated your fixes into the Vcs and team-uploaded -13
with an update for salsa. Should hit the archive shortly.

Bernhard

Bug#905993: python3-rope: Missing/Incorrect dependencies/recommends

[Adrian Bunk]

Package: python3-rope
Version: 0.10.5-2
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-12 21:30:34.763123980 +
+++ debian/control  2018-08-12 21:31:04.359123698 +
@@ -38,9 +38,9 @@
 
 Package: python3-rope
 Architecture: all
-Depends: ${python:Depends},
+Depends: ${python3:Depends},
  ${misc:Depends}
-Recommends: python-svn,
+Recommends: python3-svn,
 mercurial,
 git-core
 Description: Python 3 refactoring library

Bug#905992: cvc4: FTBFS on all autobuilders

[Ralf Treinen]

Source: cvc4
Version: 1.6-1
Severity: serious

Hi, cvc4 fails to build on all autobuilders, with 

Making all in options
make[7]: Entering directory 
'/<>/builds/i686-pc-linux-gnu/production/src/options'
[...]
/usr/bin/env: 'python3': No such file or directory

-Ralf.

Bug#905990: python3-libesedb: missing dependency on python3

[Adrian Bunk]

Package: python3-libesedb
Version: 20170121-4
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-12 21:11:54.759134661 +
+++ debian/control  2018-08-12 21:12:06.015134554 +
@@ -68,7 +68,7 @@
 Package: python3-libesedb
 Section: python
 Architecture: any
-Depends: libesedb1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, 
${python:Depends}
+Depends: libesedb1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, 
${python3:Depends}
 Description: Extensible Storage Engine DB access library -- Python 3 bindings
  libesedb is a library to access the Extensible Storage Engine (ESE)
  Database File (EDB) format. The ESE database format is used in may

Bug#905989: python3-enet: missing python3 dependency

[Adrian Bunk]

Package: python3-enet
Version: 0.0~vcs.2017.05.26.git-2
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-12 21:08:44.955136471 +
+++ debian/control  2018-08-12 21:08:55.283136373 +
@@ -33,10 +33,10 @@
 Architecture: any
 Depends:
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
  ${shlibs:Depends}
 Breaks:
- ${python:Breaks}
+ ${python3:Breaks}
 Description: Python3 wrapper for the ENet library
  python-enet provides a thin wrapper around the enet networking
  library. ENet is a thin layer to provide reliable communication over

Bug#905955: marked as done (s-tui: Please, add python3-distutils to its depedencies)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 20:38:40 +
with message-id 
and subject line Bug#905955: fixed in s-tui 0.7.5-2
has caused the Debian Bug report #905955,
regarding s-tui: Please, add python3-distutils to its depedencies
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.)


-- 
905955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s-tui
Version: 0.7.5-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

s-tui doesn't ask for installing the python3-distutils package, but it's
needed.

Traceback (most recent call last):
  File "/usr/bin/s-tui", line 11, in 
load_entry_point('s-tui==0.7.5', 'console_scripts', 's-tui')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 43, in 
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'


Best regards,
Manolo Díaz


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

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

Versions of packages s-tui depends on:
ii  python3 3.6.5-3
ii  python3-psutil  5.4.6-1+b1
ii  python3-urwid   2.0.1-2+b1

s-tui recommends no packages.

s-tui suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: s-tui
Source-Version: 0.7.5-2

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated s-tui package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 21:30:49 +0200
Source: s-tui
Binary: s-tui
Architecture: source all
Version: 0.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Description:
 s-tui  - terminal UI for monitoring your computer
Closes: 905955
Changes:
 s-tui (0.7.5-2) unstable; urgency=medium
 .
   * Add python3-distutils as dependency (Closes: #905955)
Checksums-Sha1:
 aaacad77ec9fa7e08320f50ac9ca2811ca227c5b 1880 s-tui_0.7.5-2.dsc
 36cbb4c0af55c7c17df250f32b4497ce9ea45c38 2688 s-tui_0.7.5-2.debian.tar.xz
 a6a96a8614e56c8d1dba2d15b139e65ab33307b5 30252 s-tui_0.7.5-2_all.deb
 cc1fcdb8f045a824766a6d9b1f2a1429fdac9d4a 6054 s-tui_0.7.5-2_amd64.buildinfo
Checksums-Sha256:
 7d3003f4174e508b022317ec65a44e5bc67da4e00cffee95e0d7aed07fda465b 1880 
s-tui_0.7.5-2.dsc
 ed267c100eda10d33031949524cb0db6223930958dfb3f75ebc1f90fb49d6b56 2688 
s-tui_0.7.5-2.debian.tar.xz
 2ee1eece6e565e0237de22129652aa3679316d88b3a11d2b4843ef4d67fb3956 30252 
s-tui_0.7.5-2_all.deb
 7a93e8a6be9c69e872b55a5e089126e516482de79bec87cc08c74340b8cbfe3d 6054 
s-tui_0.7.5-2_amd64.buildinfo
Files:
 84f415ae156c08668f591b0f74befeb2 1880 utils optional s-tui_0.7.5-2.dsc
 8564b12892e7bfaf19a1885ead3f8da9 2688 utils optional 
s-tui_0.7.5-2.debian.tar.xz
 c56a8ca537d78c6abab9a36cfda06dd3 30252 utils optional s-tui_0.7.5-2_all.deb
 0d4ed1117225b6bf250a27954c7b2fb3 6054 utils optional 
s-tui_0.7.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAltwi9kPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmho6MQAKQ6hXzI+vkPf3WkTm6Jx7pfkeFH5jC3md01
qvIW4PygeNBp/G+XOOC4cnzxs7y00voU5kh5Vvj9QzYI9a95WhDc1jf6rg7KWPdc
2QB1P2qzA2FDr7Fq6jo

Bug#898633: evolution-data-server: efail attack against S/MIME

[Jeremy Bicha]

On Mon, May 14, 2018 at 9:33 AM Yves-Alexis Perez  wrote:
> as you are certainly aware, a paper describing a vulnerability called
> efail has been published today (https://efail.de). It describes an
> attack scenario which can enable an attacker with read/write access to
> the encrypted mails to retrieve plaintext via an external server if HTML
> mail and loading of remote content is enabled.
>
> The PGP/MIME part is apparently not vulnerable in Evolution, but the
> S/MIME seems to be (according to the authors).
>
> It's unclear if a fix needs to be done at the evolution(-data-server)
> layer or below, so feel free to reassign to an underlying library if
> needed (nss for example).
>
> We'll likely have to issue a DSA at one point.

Yvez, the Evolution bug was closed upstream. Should we close the bug
in Debian too?

https://bugzilla.gnome.org/796135

Thanks,
Jeremy Bicha

Bug#905054: marked as done (tuxmath-data: broken symlink: /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> ../../fonts/opentype/andika/Andika-R.ttf)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 19:50:17 +
with message-id 
and subject line Bug#905054: fixed in tuxmath 2.0.3-4
has caused the Debian Bug report #905054,
regarding tuxmath-data: broken symlink: 
/usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> 
../../fonts/opentype/andika/Andika-R.ttf
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.)


-- 
905054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tuxmath-data
Version: 2.0.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m23.3s ERROR: FAIL: Broken symlinks:
  /usr/share/tuxmath/fonts/AndikaDesRevG.ttf -> 
../../fonts/opentype/andika/Andika-R.ttf

The font file is (nowadays?) located at 
/usr/share/fonts/truetype/andika/Andika-R.ttf
 

cheers,

Andreas


tuxmath-data_2.0.3-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tuxmath
Source-Version: 2.0.3-4

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated tuxmath package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 21:24:40 +0200
Source: tuxmath
Binary: tuxmath tuxmath-data
Architecture: source
Version: 2.0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Holger Levsen 
Changed-By: Holger Levsen 
Description:
 tuxmath- math game for kids with Tux
 tuxmath-data - math game for kids with Tux -- data files
Closes: 905054
Changes:
 tuxmath (2.0.3-4) unstable; urgency=medium
 .
   * tuxmath-data: update path for font symlink so it points to
 /usr/share/fonts/truetype/andika/Andika-R.ttf. (Closes: #905054)
 Thanks to Andreas Beckmann for reporting this issue.
   * Bump standards version to 4.2.0, no changes needed.
Checksums-Sha1:
 5488e1911a5cd2ad2843f3018e2bc4d14b436175 2110 tuxmath_2.0.3-4.dsc
 fa10847f361d0cafdb3f31a5bdeceb530ebef5d0 17216 tuxmath_2.0.3-4.debian.tar.xz
 7102cc88846d0818942a40397603ee3c1ebe0f46 12728 tuxmath_2.0.3-4_source.buildinfo
Checksums-Sha256:
 1e9e50b75295e4509a4c739764a4136d17a6863e8b684fb08cc201a7dc4c7ee2 2110 
tuxmath_2.0.3-4.dsc
 62e64ffc6edad01a2f49c9d28f674e387fe811d3c131c0acbe7e25507f5af234 17216 
tuxmath_2.0.3-4.debian.tar.xz
 afe17661a19680deeada1a94e083a0490a62f98b8ed11d11cbd3dc2be62f3619 12728 
tuxmath_2.0.3-4_source.buildinfo
Files:
 6d678c34ba1578a71cee81dcd6a262e5 2110 games optional tuxmath_2.0.3-4.dsc
 222ecd9a57e038facecd10c2f7ce7c47 17216 games optional 
tuxmath_2.0.3-4.debian.tar.xz
 78028ed6d1ab0e05e0c33425064cfd21 12728 games optional 
tuxmath_2.0.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAltwjUQACgkQCRq4Vgaa
qhzeAg/8DrCRihoDHxXEt8Gfd6biQ15UwEgjyg75yGNLC5JgOcVIwGlteZo4mvwT
60CV/tWUZ4/Rs9ZQV3RqZEwOdRvMtJsJts3E9KAz21as+dvvNnQk0bdY2XCPsQxI
fonMQibYKnmenjvm+ZwMO5qZrl+xYbsCzLPufFHb52zPjjlRXtpOUhmM+GnH4Xmd
z3TSWW6zSRLbcMl1eEWeHEUqOcttOjaQxf0+EJwFdENSFet9fc4bmpbvOC8YPk1V
fg+Ou0I0CEaf5cBVQ+xREBePAot3LGiuVhPm3+QXetmblyCaL4VzqHmJxIM0/6DZ
wgjJtnTrolUCLgwAbCYpb7Oo57ssxJaHLoCLicOy1AwmbCVvACKhE5aHcocGZZQs
XZcqiDVwv6SNtXThNgU4DJmSThE/z1SBw12LXxEtlXPHUU9fGGzC72lJHqziSZFm
YAWDhekfws6hGFRTrJqZwhTYOPReOHyw06sZjOjz8T/5y/yvIibYZLS2rS97oMVb
6xaySSxscIEsF8EPKIq/XASjF1EB8oVST9vcDXyL2Tmop5kf6cvkjFZ55mkCGbVI
F8gU3UOX9mSmY9EsokWUbFi+mTOt8HavKDnCMrR5EoyT2zpPajI7JTAU6+d+/k0l
Hakd0QhfAgLj1zpqDt4dAdv15KvD5cKFAz75xTIJCzr6ymMZ1Bo=
=lw7J
-END PGP SIGNATURE End Message ---

Bug#896761: marked as done (chrome-gnome-shell: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 19:33:59 +
with message-id 
and subject line Bug#896761: fixed in chrome-gnome-shell 10.1-1
has caused the Debian Bug report #896761,
regarding chrome-gnome-shell: missing build dependency on python3-distutils
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.)


-- 
896761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chrome-gnome-shell
Version: 9-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chrome-gnome-shell.html

...
/usr/bin/python3 /build/1st/chrome-gnome-shell-10/connector/setup.py build
Traceback (most recent call last):
  File "/build/1st/chrome-gnome-shell-10/connector/setup.py", line 5, in 

from distutils.core import setup
ModuleNotFoundError: No module named 'distutils.core'
make[3]: *** [CMakeFiles/build-connector.dir/build.make:60: 
CMakeFiles/build-connector] Error 1


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: chrome-gnome-shell
Source-Version: 10.1-1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated chrome-gnome-shell 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 15:17:07 -0400
Source: chrome-gnome-shell
Binary: chrome-gnome-shell
Architecture: source
Version: 10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 chrome-gnome-shell - GNOME Shell extensions integration for web browsers
Closes: 896761
Changes:
 chrome-gnome-shell (10.1-1) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/maintscript: Remove obsolete conffiles
 .
   [ Jeremy Bicha ]
   * New upstream release
   * Add Breaks against firefox and firefox-esr << 56 per upstream
 .
   [ Ritesh Raj Sarraf ]
   * Add build dependency on python3-distutils (Closes: #896761)
Checksums-Sha1:
 3eae2d7c8a67b41bddbf08bac6521bb1b9c82ca0 2130 chrome-gnome-shell_10.1-1.dsc
 f8c05bd58302c6b0ad3220f9e82df4a43b4ea4f3 169088 
chrome-gnome-shell_10.1.orig.tar.xz
 e11f25d304e6c4ee32f287fe40c68e43c4fe540c 3860 
chrome-gnome-shell_10.1-1.debian.tar.xz
 b7206dec8bb3a249324a5285545e89105949d4ac 9792 
chrome-gnome-shell_10.1-1_source.buildinfo
Checksums-Sha256:
 4a551b9530c10544fde2b8584ca9c5904d67ef8eb4e01ef5d5d68531644edb9b 2130 
chrome-gnome-shell_10.1-1.dsc
 56ad4fee9078ba62c43d2439f15a93d4b87881fab35900d7f5038d5a95efa438 169088 
chrome-gnome-shell_10.1.orig.tar.xz
 50d9110fe743b1ece802466d8024eef81fed039d748148daf959449ce01a5678 3860 
chrome-gnome-shell_10.1-1.debian.tar.xz
 555032304b14cb404b8d58d9a36137c27eaa14f0f58a27e9239b76fe300f9939 9792 
chrome-gnome-shell_10.1-1_source.buildinfo
Files:
 249c250043feb236ae82630b3813c87c 2130 gnome optional 
chrome-gnome-shell_10.1-1.dsc
 11dd4c539fefff7153b4f0af8e6e4a71 169088 gnome optional 
chrome-gnome-shell_10.1.orig.tar.xz
 eaa0139c9ef34c2def46f0fb9f4544ac 3860 gnome optional 
chrome-gnome-shell_10.1-1.debian.tar.xz
 b76dd9c21a5b62f7c1903515d61531af 9792 gnome optional 
chrome-gnome-shell_10.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAltwiG8ACgkQ5mx3Wuv+
bH2JRA//WMb32hdTbBuhSAXlpdp13fVAueHkXE5IXZdUGlUC9p+mVl+sWAllYLHO
hjkfCdHoglgD7NlfwlS0TALQKYjjQKLAYLuqJZFPQHuweY5zbFP6KCjXwbhe3Ocx
CC2cTZuAWBG+Zz6P80gZFH1K57mbdrk9VmjWlVfdWsBGQcL8V6Q3UDnQenCU6Xyr
yu/Daw5645C3G1CkRKlvFb2K+HBuuv/bwPgwCfab6F6i+L3lcRGu6brMXg/fKlDV
KRc+Puaiess92D6/YDkGg+ZVB88jsOUi4y8zc3iBrO4JQ3d88c2ahA6GZBcEInGl
7Qx78jt3usBCEmMtUpHf7e9/orOv8EUclYLPCu3UCUybqcinKmBKzAvYPIQNdarZ
VOPO/WJKTNZFrdqdsW+ePe10/ltoPB0GaJpVBtFVc0PrqunULAnuwiwQZegp6h8B
R4agbNFc1HtOzgIM68zhjo132+RShrzrF91hU+MEtnVcCER2YLJoadvHdtIEh/be
rGusug1IsZi2xTSOQqrm8MUcnwzwRtVOJwfrcJsmNlvj50sXtfij42cTbDFVFrHF
yTVYFMsoId+/

Bug#891063:

[Vincent Lefevre]

On 2018-08-12 21:19:37 +0200, Vincent Lefevre wrote:
> On 2018-08-10 11:35:26 +0200, Vincent Lefevre wrote:
> > I've just reported a bug upstream:
> > 
> >   https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413
> 
> The answer is to build Emacs with "--without-gsettings".

This may also fix other bugs, such as dconf default settings
overriding .emacs settings.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#891063:

[Vincent Lefevre]

On 2018-08-10 11:35:26 +0200, Vincent Lefevre wrote:
> I've just reported a bug upstream:
> 
>   https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413

The answer is to build Emacs with "--without-gsettings".

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: tagging 905966, reassign 905966 to src:linux, forcibly merging 905751 905966

[Debian Bug Tracking System]

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

> tags 905966 - newcomer
Bug #905966 [src:linux] linux-image-4.9.0-0.bpo.7-amd64: CVE-2018-5390 not 
fixed?
Removed tag(s) newcomer.
> reassign 905966 src:linux
Bug #905966 [src:linux] linux-image-4.9.0-0.bpo.7-amd64: CVE-2018-5390 not 
fixed?
Ignoring request to reassign bug #905966 to the same package
> forcemerge 905751 905966
Bug #905751 {Done: Salvatore Bonaccorso } [src:linux] linux: 
CVE-2018-5390
Bug #905751 {Done: Salvatore Bonaccorso } [src:linux] linux: 
CVE-2018-5390
The source linux and version 4.9.110-1~deb8u1 do not appear to match any binary 
packages
Marked as found in versions linux/4.9.110-1~deb8u1.
Bug #905966 [src:linux] linux-image-4.9.0-0.bpo.7-amd64: CVE-2018-5390 not 
fixed?
Marked Bug as done
Marked as fixed in versions linux/4.9.110-3+deb9u1.
The source linux and version 4.9.110-1~deb8u1 do not appear to match any binary 
packages
Marked as found in versions linux/4.9~rc3-1~exp1.
Merged 905751 905966
> thanks
Stopping processing here.

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

Bug#905985: pygame FTBFS with python 3.7

[peter green]

Package: pygame
Version: 1.9.3+dfsg2-2
Severity: serious

pygame fails to build with python 3.7


src/pypm.c:4976:18: error: 'PyThreadState {aka struct _ts}' has no member named 
'exc_type'; did you mean 'curexc_type'?
  if ((tstate->exc_type != NULL) & (tstate->exc_type != Py_None)) {


I understand that this is fixed in the new upstream version 1.9.4

Bug#905977: kea-ctrl-agent: missing dependency on python3

[Adrian Bunk]

Package: kea-ctrl-agent
Version: 1.4.0.P1-3
Severity: serious

kea-ctrl-agent lacks a python3 dependency
for /usr/sbin/kea-shell

This can be fixed by adding dh-python to the build dependencies
plus python3 to the "dh $@ --with" in debian/rules.

Processed: Re: Bug#902557: transition: Perl 5.28

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 905913
Bug #902557 [release.debian.org] transition: Perl 5.28
902557 was blocked by: 900232 899021 897790 904727 901085 904740 902556 904914 
904737 900832 902674 904735 629405 901082 862678 902771 897724
902557 was not blocking any bugs.
Added blocking bug(s) of 902557: 905913

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

Bug#905555: marked as done (emacs-nox: fails to upgrade from 47.0)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 17:49:35 +
with message-id 
and subject line Bug#90: fixed in emacs 1:25.2+1-10
has caused the Debian Bug report #90,
regarding emacs-nox: fails to upgrade from 47.0
to be marked as done.

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

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


-- 
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-nox
Version: 1:25.2+1-9
Severity: serious

Upgrading emacs-nox from 47.0 failed in a chroot for me:

,
| # apt-get dist-upgrade
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| Calculating upgrade... Done
| The following package was automatically installed and is no longer required:
|   emacs25-nox
| Use 'sudo apt autoremove' to remove it.
| The following packages will be REMOVED:
|   emacs25-bin-common emacs25-common
| The following NEW packages will be installed:
|   emacs-bin-common emacs-common
| The following packages will be upgraded:
|   emacs-nox emacs25-nox emacsen-common
| 3 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
| Need to get 0 B/16.3 MB of archives.
| After this operation, 78.8 kB disk space will be freed.
| Do you want to continue? [Y/n] 
| debconf: delaying package configuration, since apt-utils is not installed
| (Reading database ... 15154 files and directories currently installed.)
| Preparing to unpack .../emacs25-nox_1%3a25.2+1-9_all.deb ...
| Remove emacsen-common for emacs25
| emacsen-common: Handling removal of emacsen flavor emacs25
| Unpacking emacs25-nox (1:25.2+1-9) over (25.2+1-6+b3) ...
| (Reading database ... 15146 files and directories currently installed.)
| Removing emacs25-bin-common (25.2+1-6+b3) ...
| Removing emacs25-common (25.2+1-6) ...
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/scalable/mimetypes' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/scalable/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/48x48/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/32x32/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/24x24/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/16x16/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/128x128/apps' not empty so not removed
| (Reading database ... 12537 files and directories currently installed.)
| Preparing to unpack .../emacsen-common_3.0.2_all.deb ...
| Unpacking emacsen-common (3.0.2) over (2.0.8) ...
| dpkg: warning: unable to delete old directory '/etc/emacs/site-start.d': 
Directory not empty
| dpkg: warning: unable to delete old directory '/etc/emacs': Directory not 
empty
| Selecting previously unselected package emacs-common.
| Preparing to unpack .../emacs-common_1%3a25.2+1-9_all.deb ...
| Unpacking emacs-common (1:25.2+1-9) ...
| Selecting previously unselected package emacs-bin-common.
| Preparing to unpack .../emacs-bin-common_1%3a25.2+1-9_i386.deb ...
| Unpacking emacs-bin-common (1:25.2+1-9) ...
| Preparing to unpack .../emacs-nox_1%3a25.2+1-9_i386.deb ...
| dpkg-query: no packages found matching emacs-nox:i386
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox' not owned by 
package 'emacs-nox:i386'
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox/copyright' not 
owned by package 'emacs-nox:i386'
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox/changelog.gz' 
not owned by package 'emacs-nox:i386'
| dpkg-maintscript-helper: error: directory '/usr/share/doc/emacs-nox' contains 
files not owned by package emacs-nox:i386, cannot switch to symlink
| dpkg: error processing archive 
/var/cache/apt/archives/emacs-nox_1%3a25.2

Bug#905976: printer-driver-sag-gdi: missing dependency on python3

[Adrian Bunk]

Package: printer-driver-sag-gdi
Version: 0.1-5
Severity: serious

printer-driver-sag-gdi lacks a python3 dependency
for /usr/lib/cups/filter/rastertosag-gdi

Bug#897878: ucommon: diff for NMU version 7.0.0-12.1

[Adrian Bunk]

Control: tags 897878 + patch
Control: tags 897878 + pending
Control: tags 898502 + pending

Dear maintainer,

I've prepared an NMU for ucommon (versioned as 7.0.0-12.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru ucommon-7.0.0/debian/changelog ucommon-7.0.0/debian/changelog
--- ucommon-7.0.0/debian/changelog	2017-09-08 12:21:56.0 +0300
+++ ucommon-7.0.0/debian/changelog	2018-08-12 20:01:58.0 +0300
@@ -1,3 +1,11 @@
+ucommon (7.0.0-12.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix symbols for gcc 8. (Closes: #897878)
+  * Fix symbols for ia64 and riscv64. (Closes: #898502)
+
+ -- Adrian Bunk   Sun, 12 Aug 2018 20:01:58 +0300
+
 ucommon (7.0.0-12) unstable; urgency=medium
 
   * Add copyright-check maintainer script to source.
diff -Nru ucommon-7.0.0/debian/libucommon8.symbols ucommon-7.0.0/debian/libucommon8.symbols
--- ucommon-7.0.0/debian/libucommon8.symbols	2017-09-08 11:50:31.0 +0300
+++ ucommon-7.0.0/debian/libucommon8.symbols	2018-08-12 20:01:58.0 +0300
@@ -14,6 +14,9 @@
  (c++)"VTT for ost::TTYStream@Base" 7.0.0
  (c++)"VTT for ost::ThreadQueue@Base" 7.0.0
  (c++)"VTT for ost::ttystream@Base" 7.0.0
+ (c++|optional)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char const*, char const*, std::forward_iterator_tag)@Base" 7.0.0
+ (c++|optional)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char*, char*, std::forward_iterator_tag)@Base" 7.0.0
+ (c++|optional)"std::_Rb_tree_iterator, std::allocator > const, ost::Slog::Level> > std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_emplace_hint_unique, std::allocator > const&>, std::tuple<> >(std::_Rb_tree_const_iterator, std::allocator > const, ost::Slog::Level> >, std::piecewise_construct_t const&, std::tuple, std::allocator > const&>&&, std::tuple<>&&)@Base" 7.0.0
  (c++)"non-virtual thunk to ost::AppLog::~AppLog()@Base" 7.0.0
  (c++)"non-virtual thunk to ost::SerialService::~SerialService()@Base" 7.0.0
  (c++)"non-virtual thunk to ost::SharedMemPager::~SharedMemPager()@Base" 7.0.0
@@ -2166,16 +2169,8 @@
  (c++)"ucommon::String::unquote(char*, char const*)@Base" 7.0.0
  (c++)"ucommon::String::upper()@Base" 7.0.0
  (c++)"ucommon::String::upper(char*)@Base" 7.0.0
- (c++|arch=alpha sh4)"ucommon::String::vprintf(char const*, __va_list_tag)@Base" 7.0.0
- (c++|arch=amd64 kfreebsd-amd64 powerpc powerpcspe s390x x32)"ucommon::String::vprintf(char const*, __va_list_tag*)@Base" 7.0.0
- (c++|arch=hurd-i386 i386 kfreebsd-i386 ppc64 ppc64el)"ucommon::String::vprintf(char const*, char*)@Base" 7.0.0
- (c++|arch=arm64 armel armhf)"ucommon::String::vprintf(char const*, std::__va_list)@Base" 7.0.0
- (c++|arch=hppa m68k mips mips64el mipsel sparc64)"ucommon::String::vprintf(char const*, void*)@Base" 7.0.0
- (c++|arch=alpha sh4)"ucommon::String::vscanf(char const*, __va_list_tag)@Base" 7.0.0
- (c++|arch=amd64 kfreebsd-amd64 powerpc powerpcspe s390x x32)"ucommon::String::vscanf(char const*, __va_list_tag*)@Base" 7.0.0
- (c++|arch=hurd-i386 i386 kfreebsd-i386 ppc64 ppc64el)"ucommon::String::vscanf(char const*, char*)@Base" 7.0.0
- (c++|arch=arm64 armel armhf)"ucommon::String::vscanf(char const*, std::__va_list)@Base" 7.0.0
- (c++|arch=hppa m68k mips mips64el mipsel sparc64)"ucommon::String::vscanf(char const*, void*)@Base" 7.0.0
+ (c++|regex)"^ucommon::String::vprintf\(char const\*, (.+)\)@Base" 7.0.0
+ (c++|regex)"^ucommon::String::vscanf\(char const\*, (.+)\)@Base" 7.0.0
  (c++)"ucommon::String::~String()@Base" 7.0.0
  (c++|arch-bits=32)"ucommon::StringPager::StringPager(char**, unsigned int)@Base" 7.0.0
  (c++|arch-bits=64)"ucommon::StringPager::StringPager(char**, unsigned long)@Base" 7.0.0

Processed: ucommon: diff for NMU version 7.0.0-12.1

[Debian Bug Tracking System]

Processing control commands:

> tags 897878 + patch
Bug #897878 [src:ucommon] ucommon: ftbfs with GCC-8
Added tag(s) patch.
> tags 897878 + pending
Bug #897878 [src:ucommon] ucommon: ftbfs with GCC-8
Added tag(s) pending.
> tags 898502 + pending
Bug #898502 [src:ucommon] ucommon: Please update symbols for riscv64 and ia64
Added tag(s) pending.

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

Processed: Re: Bug#888995: FTBFS: async_execution_load_test fails on armhf, mips and mipsel

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dbus-cpp: async_execution_load_test fails sometimes (randomly?)
Bug #888995 [src:dbus-cpp] Bug#888995: FTBFS: async_execution_load_test fails 
on armhf, mips and mipsel
Changed Bug title to 'dbus-cpp: async_execution_load_test fails sometimes 
(randomly?)' from 'Bug#888995: FTBFS: async_execution_load_test fails on armhf, 
mips and mipsel'.
> found -1 5.0.0+18.04.20171031-1
Bug #888995 [src:dbus-cpp] dbus-cpp: async_execution_load_test fails sometimes 
(randomly?)
Ignoring request to alter found versions of bug #888995 to the same values 
previously set
> severity -1 serious
Bug #888995 [src:dbus-cpp] dbus-cpp: async_execution_load_test fails sometimes 
(randomly?)
Severity set to 'serious' from 'important'

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

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Helge Kreutzmann]

Hello Andreas Henriksson,
On Sun, Aug 12, 2018 at 05:35:35PM +0200, Andreas Henriksson wrote:
> Hello Helge Kreutzmann,
> 
> Sorry if my comments sounded too negative, some more reasoning below.

No problem.

> On Sun, Aug 12, 2018 at 04:35:47PM +0200, Helge Kreutzmann wrote:
> > Hello Andreas Henriksson,
> > I'm a bit puzzled by your e-mail. Simon asked me to provide some text,
> > Chris prodded me and Davide and Simon reviewed my text (which does not
> > imply that it is perfect or so).
> [...]
> > Well, I think for _Debian_ users the change *is* suprising, but only
> > because the su version (and its configuration / behaviour) has
> > changed.
> [...]
> 
> If the change in behaviour isn't something we can just live with
> I think solving it via pam configuration seems like the best course
> of action. Please see the mail I just quickly banged together and
> sent to debian-devel (with you BCCed).

Yes, I read it. Thanks for letting me know.

> [...]
> > Which is clearly not the case here. So upstreaming is no option.
> 
> Carrying patches downstream forever isn't something I'm very

Not forever: Only until the next stable release has happend. Then drop
it again. Clear timeline.

> enthusiastic about as you probably understand. As you might have
> also noticed I've removed myself from util-linux maintenance (lack of

No, I've not researched about util-linux any further, I just stumbled
over the bug and wanted to add my few cents to help resolving it. I
belive writing patches is better than simply complaining, and for
documentation this is within my skill set.

> time). I thus don't really see it suitable for me to add patches like
> this that someone else gets to maintain, but anyone with upload
> privilegies can upload a NMU themselves ofcourse! (so there's no need
> to wait for me to do it.)

Hopfeully your successor can chime in and put his/her POV on this. 

> OTOH please consider I've spent years to back util-linux out of the
> corner it was stuck in. Non upstreamed/upstreamable patches was part
> of the problem. I would very much appreciate some sympathy on that
> rather than pushing things back into the corner as soon as I turn my
> back. ;P

Thanks for your efforts. And I perfectly understand that you want to
avoid (ongoing) distribution specific patches where possible.

> [...]
> > Thanks. But as stated earlier, having it in NEWS is only part of the
> > solution, [...]
> 
> I'd even call it a workaround which simply serves the purpose of me
> not having to touch the pam configuration with zero peer review.
> (And I also doubt more people read manpages than read NEWS. Targeting
> release notes might be a much better option. Things that aren't new
> but just best practises we want to spread the knowledge of might be
> better suited for debian-handbook or similar)

And again who reads the release notes, especially ordinary users who
(like me at work) simply get a system delivered, without any further
"changelog", "NEWS", "release information"? There is no perfect
solution. So besides the NEWs file you mentioned, the other two
options could work in parallel.

[...]

> Sorry for sending another sloppy mail today, but hopefully you can
> make some sense of what I wrote. Really need to attend personal
> things now instead Final words, don't expect me to actually maintain
> util-linux anymore. Don't wait for me to upload what you think is
> sensible.

I wish you good success to your personal endavours and thanks for the time
you invested in Debian. 

I'm not going to do an NMU for a documentation patch, so let's wait
for your sucessor.

(For me the bug is solved, this bug report is just about spreading the
word appropriately).

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#904755: marked as done (yapf: missing dependency on python-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 15:37:44 +
with message-id 
and subject line Bug#904755: fixed in yapf 0.22.0-2
has caused the Debian Bug report #904755,
regarding yapf: missing dependency on python-pkg-resources
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.)


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

stretch $ yapf
Traceback (most recent call last):
  File "/usr/bin/yapf", line 6, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

sid $ yapf
Traceback (most recent call last):
  File "/usr/bin/yapf", line 6, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

sid $ yapf3
Traceback (most recent call last):
  File "/usr/bin/yapf3", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

For yapf3, the missing depndency would be python3-pkg-resources


Andreas
--- End Message ---
--- Begin Message ---
Source: yapf
Source-Version: 0.22.0-2

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

Debian distribution maintenance software
pp.
Ana Custura  (supplier of updated yapf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 15:47:28 +0100
Source: yapf
Binary: python-yapf yapf python3-yapf yapf3
Architecture: source all
Version: 0.22.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ana Custura 
Changed-By: Ana Custura 
Description:
 python-yapf - public modules for yapf (Python 2)
 python3-yapf - public modules for yapf (Python 3)
 yapf   - Python code formatter for different styles (Python 2)
 yapf3  - Python code formatter for different styles (Python 3)
Closes: 903533 904755
Changes:
 yapf (0.22.0-2) unstable; urgency=medium
 .
   * debian/control:
   - adds missing dependency on python-pkg-resources (Closes: #904755)
   - updates Debian policy to 4.2.0
   - bumps debhelper vesion to 11
   - updates vcs fields
   * debian/compat:
   - bumps debhelper vesion to 11
   * debian/rules:
   - prevents some Python3 tests from running (Closes: #903533)
Checksums-Sha1:
 0a8911c9b6d6f14e41cf5cbb148fbfd81c0f5585 2254 yapf_0.22.0-2.dsc
 b9dcefed3704168d9d7488e598d9f54dfe36e837 3616 yapf_0.22.0-2.debian.tar.xz
 241e9eed658f445ae41e4faa817c6fec6fefc4a0 108584 python-yapf_0.22.0-2_all.deb
 ee3f61f9a6d7237a9699289d83c74896e1623b80 108680 python3-yapf_0.22.0-2_all.deb
 44f748cd8f30edadd4cc07c793172f26ce0b 22576 yapf3_0.22.0-2_all.deb
 0dc583ca858b44c22df35791e2a773cfe0ccbcdd 22560 yapf_0.22.0-2_all.deb
 8afdf9f08298c979354827f97e15b6657879175b 7432 yapf_0.22.0-2_amd64.buildinfo
Checksums-Sha256:
 511bbf55a1f59cdc0d3abd5a4eee5bd80c4b59efc4478ad5aeddb0b8b2022f79 2254 
yapf_0.22.0-2.dsc
 bbb26d5ab503f179e028c68ecdb4f9edb660318d8d259ecac8f628d335b5cfaf 3616 
yapf_0.22.0-2.debian.tar.xz
 83ce09b4327cada70614b1bb42059de0cc44157980d005ee0faa210d4a39d981 108584 
python-yapf_0.22.0-2_all.deb
 bbae46db444047788d421a9c615a7ec475ac5e5417d40fa8e54a1f56c87afa07 108680 
python3-yapf_0.22.0-2_all.deb
 a57ca2297ff0ea115cfc987aaa02bf451a40274dbea5928a090ff8a3ae8ce5ab 22576 
yapf3_0.22.0-2_all.deb
 7e4a86b631576206fa256270bd87fa809ed738ad2414322083b8ddb441689c20 22560 
yapf_0.22.0-2_all.deb
 8e0eb0dbbf0ae101e6573c01dcd16a1a2141a00c5ef24467bd0508c7a8230240 7432 
yapf_0.22.0-2_amd64.buildinfo
Files:
 be878a2bd33fd7c7655cca510dc37caa 2254 python optional yapf_0.22.0-2.dsc
 9c7a9418d9bbb1c8633d4fd262d35250 3616 python optional 
yapf_0.22.0-2.debian.tar.xz
 e45bfac65b480b2846fe38a6f9a5526b 108584 python optional 
python-yapf_0.22.0-2_all.deb
 bb0a439ac99bd6d9b2c38fdc4a1c36cb 108680 python optional 
python3-yapf_0.22.0-2_all.deb
 8c5a2d2520c97b2e55d31187676941b3 22576 python optional yapf3_0.22.0-2_all.deb
 e547a48a10a7beafdcfd31c13c4527db 22560 python optional yapf_0.22.0-2_all.deb
 5909eab0e118db48a1911ebb858b329f 7432 python op

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Andreas Henriksson]

Hello Helge Kreutzmann,

Sorry if my comments sounded too negative, some more reasoning below.

On Sun, Aug 12, 2018 at 04:35:47PM +0200, Helge Kreutzmann wrote:
> Hello Andreas Henriksson,
> I'm a bit puzzled by your e-mail. Simon asked me to provide some text,
> Chris prodded me and Davide and Simon reviewed my text (which does not
> imply that it is perfect or so).
[...]
> Well, I think for _Debian_ users the change *is* suprising, but only
> because the su version (and its configuration / behaviour) has
> changed.
[...]

If the change in behaviour isn't something we can just live with
I think solving it via pam configuration seems like the best course
of action. Please see the mail I just quickly banged together and
sent to debian-devel (with you BCCed).

[...]
> Which is clearly not the case here. So upstreaming is no option.

Carrying patches downstream forever isn't something I'm very
enthusiastic about as you probably understand. As you might have
also noticed I've removed myself from util-linux maintenance (lack of
time). I thus don't really see it suitable for me to add patches like
this that someone else gets to maintain, but anyone with upload
privilegies can upload a NMU themselves ofcourse! (so there's no need
to wait for me to do it.)

OTOH please consider I've spent years to back util-linux out of the
corner it was stuck in. Non upstreamed/upstreamable patches was part
of the problem. I would very much appreciate some sympathy on that
rather than pushing things back into the corner as soon as I turn my
back. ;P

[...]
> Thanks. But as stated earlier, having it in NEWS is only part of the
> solution, [...]

I'd even call it a workaround which simply serves the purpose of me
not having to touch the pam configuration with zero peer review.
(And I also doubt more people read manpages than read NEWS. Targeting
release notes might be a much better option. Things that aren't new
but just best practises we want to spread the knowledge of might be
better suited for debian-handbook or similar)

It seems to me that the pam configuration, even ignoring the current
implementation differences, is long overdue for an overhaul (based
on the bug reports zeha reassigned).
Hopefully we can get a discussion going on what a suitable pam
configuration should look like and get enough people involved to make a
good tradeoff and get all changes peer reviewed.

I however fear that everyone who has prior PAM knowledge knows how easy
it is to get things wrong and are smart enough to keep their hands away.
Possibly we might need to find new people who haven't already cut
themselves on pam configuration to become interested and involved, and
learn as they go (to eventually also learn to never touch pam
configuration ever again).

Sorry for sending another sloppy mail today, but hopefully you can
make some sense of what I wrote. Really need to attend personal
things now instead Final words, don't expect me to actually maintain
util-linux anymore. Don't wait for me to upload what you think is
sensible.

Regards,
Andreas Henriksson

Bug#903533: marked as done (yapf FTBFS with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 15:37:44 +
with message-id 
and subject line Bug#903533: fixed in yapf 0.22.0-2
has caused the Debian Bug report #903533,
regarding yapf FTBFS with Python 3.7 as supported version
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.)


-- 
903533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yapf
Version: 0.22.0-1
Severity: serious

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

...
I: pybuild base:217: cd 
/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build; python3.7 -m nose 
.F...F..F...
==
FAIL: testAsyncAsNonKeyword 
(yapftests.reformatter_basic_test.BasicReformatterTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/reformatter_basic_test.py",
 line 2489, in testAsyncAsNonKeyword
self.assertCodeEqual(code, reformatter.Reformat(uwlines, verify=False))
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/yapf_test_helper.py",
 line 57, in assertCodeEqual
self.fail('\n'.join(msg))
AssertionError: Code format mismatch:
Expected:
 > from util import async
 > 
 > 
 > class A(object):
 > def foo(self):
 > async.run()
 > 
 > def bar(self):
 > pass
Actual:
 > from util import async
 > 
 > 
 > class A(object):
 > def foo(self):
 > async .run()
 > 
 > def bar(self):
 > pass
Diff:
--- actual
+++ expected
@@ -3,7 +3,7 @@
 
 class A(object):
 def foo(self):
-async .run()
+async.run()
 
 def bar(self):
 pass

==
FAIL: testListComprehensionPreferThreeLinesForLineWrap 
(yapftests.reformatter_basic_test.BasicReformatterTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/reformatter_basic_test.py",
 line 526, in testListComprehensionPreferThreeLinesForLineWrap
self.assertCodeEqual(expected_formatted_code, reformatter.Reformat(uwlines))
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/yapf_test_helper.py",
 line 57, in assertCodeEqual
self.fail('\n'.join(msg))
AssertionError: Code format mismatch:
Expected:
 > def given(y):
 >   long_variable_name = [
 >   long_var_name + 1
 >   for long_var_name, number_two in ()
 >   if long_var_name == 2 and number_two == 3
 >   ]
Actual:
 > def given(y):
 >   long_variable_name = [
 >   long_var_name + 1 for long_var_name, number_two in ()
 >   if long_var_name == 2 and number_two == 3
 >   ]
Diff:
--- actual
+++ expected
@@ -1,5 +1,6 @@
 def given(y):
   long_variable_name = [
-  long_var_name + 1 for long_var_name, number_two in ()
+  long_var_name + 1
+  for long_var_name, number_two in ()
   if long_var_name == 2 and number_two == 3
   ]

==
FAIL: testStronglyConnected (yapftests.split_penalty_test.SplitPenaltyTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/split_penalty_test.py",
 line 205, in testStronglyConnected
(']', None),
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/split_penalty_test.py",
 line 72, in _CheckPenalties
self.assertEqual(list_of_expected, FlattenRec(tree))
AssertionError: Lists differ: [('['[25 chars]or', 0), ('a', 3000), ('in', 
3000), ('foo', 30[93 chars]one)] != [('['[25 chars]or', None), ('a', None), 
('in', None), ('foo',[99 chars]one)]

First differing element 2:
('for', 0)
('for', None)

  [('[', None),
   ('a', None),
-  ('for', 0),
?  ^

+  ('for', None),
?  

-  ('a', 3000),
-  ('in', 3000),
- 

Bug#905971: linux-image-4.17.0-0.bpo.1-arm64: Linux 4.17 doesn't boot on Raspberry Pi 3 B

[Takashi Yoshi]

Package: src:linux
Version: 4.17.8-1~bpo9+1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After installing the latest backports kernel (4.17.0) the system doesn't boot 
anymore.
There is no output on the serial console either.

I had to revert to 4.16.x to get my Pi to boot again.

If there's anything else you need to know, I'd be happy to test.


-- Package-specific info:
** Model information
Device Tree model: Raspberry Pi 3 Model B

** PCI devices:

** USB devices:
Bus 001 Device 006: ID 0846:9021 NetGear, Inc. WNA3100M(v1) Wireless-N 300 
[Realtek RTL8192CU]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast 
Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.16.0-0.bpo.2-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linux-image-4.17.0-0.bpo.1-arm64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.17.0-0.bpo.1-arm64 recommends:
ii  apparmor 2.11.0-3+deb9u2
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.17.0-0.bpo.1-arm64 suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.17  

Versions of packages linux-image-4.17.0-0.bpo.1-arm64 is related to:
pn  firmware-amd-graphics 
ii  firmware-atheros  20161130-3
pn  firmware-bnx2 
pn  firmware-bnx2x
ii  firmware-brcm8021120161130-3
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
ii  firmware-misc-nonfree 20161130-3
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20161130-3
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#899957: marked as done (libbase58: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 15:05:12 +
with message-id 
and subject line Bug#899957: fixed in libbase58 0.1.4-2
has caused the Debian Bug report #899957,
regarding libbase58: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
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.)


-- 
899957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbase58
Version: 0.1.4-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libbase58,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libbase58 since the list address
pkg-bitcoin-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bitcoin-de...@lists.alioth.debian.org is 11.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libbase58
Source-Version: 0.1.4-2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libbase58 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 17:49:53 +0300
Source: libbase58
Binary: libbase58-0 libbase58-dev
Architecture: source
Version: 0.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 libbase58-0 - library for Bitcoin's base58 encoding
 libbase58-dev - library for Bitcoin's base58 encoding -- development files
Closes: 899957
Changes:
 libbase58 (0.1.4-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #904955) (Closes: #899957)
Checksums-Sha1:
 05b846793d6b4f4dbf264ef491e943bae1768bf5 1957 libbase58_0.1.4-2.dsc
 31ae7ebeed5723ce619465b7f654435725024809 5440 libbase58_0.1.4-2.debian.tar.xz
Checksums-Sha256:
 63ad37afe276eca49c2401d977f62a14effe5cf784dbb41167d9f2e86967fce7 1957 
libbase58_0.1.4-2.dsc
 ef4a7e74ccd4f483c3cf2d293b8335b30120f09d64ace47ad2d6d03ca71f628c 5440 
libbase58_0.1.4-2.debian.tar.xz
Files:
 1035f164e710c7066eb396696c056db7 1957 libs optional libbase58_0.1.4-2.dsc
 b5843814d9f9e5be79ed420a1a3b8a26 5440 libs optional 
libbase58_0.1.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltwSawACgkQiNJCh6LY
mLE8iBAAhLB2hLT+1O14DZam6i4+iiVWG4iSNUrrOb7DvdFA3mDygVMwWy/iaFw1
zVB5OQUCQ5lN8/G0gXNuhc23m78teIW

Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.2

[Adrian Bunk]

On Sun, Aug 12, 2018 at 04:13:22PM +0200, Anton Gladky wrote:
> Hello Adrian,

Hi Anton,

> thank you for your work on OpenFoam. Please feel free
> to move the upload into the DELAYED/0.

thanks, done.

> Best regards
> 
> Anton

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#901539: marked as done (gnushogi swallows errors from make (policy 4.6))

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 14:40:38 +
with message-id 
and subject line Bug#901539: fixed in gnushogi 1.4.2-4
has caused the Debian Bug report #901539,
regarding gnushogi swallows errors from make (policy 4.6)
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.)


-- 
901539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnushogi
Version: 1.4.2-3
Severity: serious
Justification: policy 4.6
Tags: upstream

If you run

grep '^\s*-' Makefile.in

you'll find a number of crucial make rules that ignore errors. In
particular the main build and install targets are among them. Thus
gnushogi continues building in the presence of errors and risks
misbuilds. Such behaviour is prohibited by policy section 4.6.

Helmut
--- End Message ---
--- Begin Message ---
Source: gnushogi
Source-Version: 1.4.2-4

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

Debian distribution maintenance software
pp.
Yann Dirson  (supplier of updated gnushogi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 12 Aug 2018 14:39:58 +0200
Source: gnushogi
Binary: gnushogi gnuminishogi
Architecture: source amd64
Version: 1.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson 
Changed-By: Yann Dirson 
Description:
 gnuminishogi - program to play minishogi, a shogi variant on a 5x5 board
 gnushogi   - program to play shogi, the Japanese version of chess
Closes: 901539
Changes:
 gnushogi (1.4.2-4) unstable; urgency=medium
 .
   * Don't ignore failures from sub-makes (Closes: #901539)
Checksums-Sha1:
 f4453c8b6b68aaf318ff5fedbb89658f97f370e7 1966 gnushogi_1.4.2-4.dsc
 1223f151e07ece2bef228c32cbde32de529eb04b 7704 gnushogi_1.4.2-4.debian.tar.xz
 ee3bb1c3632ace59c50ab5ae8fefbd73248d60d2 162180 
gnuminishogi-dbgsym_1.4.2-4_amd64.deb
 5f03a3e85375be801dc5c0e833d79eaf670928e7 93488 gnuminishogi_1.4.2-4_amd64.deb
 59a4f4cd4bd2d1062c88b677ad8750e234e85242 6234 gnushogi_1.4.2-4_amd64.buildinfo
 932300f2d10796c21b353eff69653d4b0daffbbd 244652 gnushogi_1.4.2-4_amd64.deb
Checksums-Sha256:
 e85b524c12413a8cabdbf0ab7943c0c3ff5f12bc812f64e72b413cc392c25940 1966 
gnushogi_1.4.2-4.dsc
 affa6ed2cc3e79819714a69802569e762f64edbdd2adf27bc2dcac1fff6f20c1 7704 
gnushogi_1.4.2-4.debian.tar.xz
 df5388f01b584525ad0a4f8e5bbfc2b04a74854983bc77682d2ca13d7c2eb245 162180 
gnuminishogi-dbgsym_1.4.2-4_amd64.deb
 f3b1459f32212a249c69f023e2da8b0aa8bf18bd39ae93cbffe58703d8869936 93488 
gnuminishogi_1.4.2-4_amd64.deb
 46b2c7505c00a2d41908c039db1993c338b096c41c70c982cc31416600490c4d 6234 
gnushogi_1.4.2-4_amd64.buildinfo
 3d0182df6c54e503fc3b5524e8f891b0687992d0a2191257220d3ada4c84021e 244652 
gnushogi_1.4.2-4_amd64.deb
Files:
 f6aee7947cbb6a27c4b5291052ac12e2 1966 games optional gnushogi_1.4.2-4.dsc
 2b5b3a7083e33daa0232ae95317d6284 7704 games optional 
gnushogi_1.4.2-4.debian.tar.xz
 29ca68c817129982f37adf1f820c64df 162180 debug optional 
gnuminishogi-dbgsym_1.4.2-4_amd64.deb
 a537685804774b609b8f60dd8cff95c8 93488 games optional 
gnuminishogi_1.4.2-4_amd64.deb
 67f8ad416fdea2a39ab436e9d1b2da64 6234 games optional 
gnushogi_1.4.2-4_amd64.buildinfo
 c8e4a6a1ecb2766295206c5e9fa3d583 244652 games optional 
gnushogi_1.4.2-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdK8F3dkgJ/Xww83VDYXyliWj+f0FAltwPN0ACgkQDYXyliWj
+f1Wlw/+Lau+VPQIHxRZCfIvMkKCVavJOjJcg0TknuhEay3h0FCiLMxJq59aKxd/
XRtR/XL9YuxVr+Exk0hdqGb/nMyN9vcOBJ9cUs+iN1Ujo4QYaRtu5Yum+dNnWgvu
7LZ3YsxRWdeBgdtDn1ZaNnstckbOmo+zjIK2vEXYbRz1DuaFleRrwXVTwXsfllVd
hYWYpjDRok5U8+/2Lr8WY+pdQShPjblqDLvTTubtDgJkmoK2F0luzkx1Q7fNaX5c
a0pQXAkt2Ouz6EsA1N+hrZhUfePjYfkOGbauNHe+yLAdhpsACmoCw4ILXIM816Ff
5ubFCTiTVM/SfAbon5hBaJiUIeVDl3luytEDuHHDnxfb85ol5LGold13z32oNw7e
CBZOPUDa3bdGgSAwniPvcn2hJIy4O7urUzW9D+xZ6+srWG2LNAkQP3Y54oiATMFi
H7BdTdUuJk2Xe8nZgXN1jrRdvm9OfJAoZnmdScb5eqx8wV7nuMQhwycX9+5WZL4V
Miu8YnK2dA7Wbx5KOP3e05USMbRWIMNJE/SQBx15qphDHvfSkz1AD9/uepBNrd+a
EJbuLq3gowVH8ap+WxK7xrhEO5AsuwUhju/TjNUVUXBP88wkpGE467K8kcLkPpYa
O7lKBJiFTW6QmAGbJ+i5j5+hTameVGmZ

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Helge Kreutzmann]

Hello Andreas Henriksson,
I'm a bit puzzled by your e-mail. Simon asked me to provide some text,
Chris prodded me and Davide and Simon reviewed my text (which does not
imply that it is perfect or so).

On Sun, Aug 12, 2018 at 05:56:14AM +0200, Andreas Henriksson wrote:
> Hello Helge Kreutzmann,
> 
> I'm skeptical how relevant it is to document how X and ssh works
> in the _su_ manpage, but either way since you're patching the

I'm fine to skip the X and ssh part, but as stated above the reviewer
liked the idea and I actually tried to keep it short and simple. And
no, I don't intend to go into any more details, which would be way
over top in the su manpage.

> manpage this is something you want to send upstream for review if
> you think it's worth persuing and my opinion doesn't count there.

Well, I think for _Debian_ users the change *is* suprising, but only
because the su version (and its configuration / behaviour) has
changed. For upstream util-linux this is not the case, there no change
has occured, only one more distribution is now using the su
implementation.

So I could very well understand if util-linux upstream would reject
the change, as there nothing has happend (and why should users of
other distributions care about a Debian specific issue?). 

> As always to increase chances of a favourable review getting the
> administrative details right from the start is useful, so please
> see Documentation/howto-contribute.txt

As you can see from the bug log, there already was some review.
Looking at howto-contribute.txt, it also says:
* neutrality: the files in util-linux should be distribution-neutral.

Which is clearly not the case here. So upstreaming is no option.

> (You might also want to replace references to 'Debian 9' with
> 'shadow su implementation' or similar.)

I think the explicit reference to Debian serves a purpose here: The
user might not know that previous versions of su came from shadow, and
current ones from util-linux. They just see their workflow break.

> I'll add a note to util-linux.NEWS about DISPLAY and XAUTHORITY.

Thanks. But as stated earlier, having it in NEWS is only part of the
solution, because in larger installations NEWS are not seen by
ordinary users, e.g at work I've never seen any NEWS file, I simply
was informed than an upgrade had happened, so I rely on other
information sources, where man pages are my first try. (And search in
the web and hopefully finding bug reports like this are really
disliked last options.)

So I would ask you to carry a patch simliar to the one proposed (maybe
stripped, if you don't like the part about better solutions, security
wise) until the next Debian version is released and then drop it
again, so people on the next stable version can read it in the man
page.

If you agree I'm fine to further tune the patch.

Greetings

 Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.2

[Anton Gladky]

Hello Adrian,

thank you for your work on OpenFoam. Please feel free
to move the upload into the DELAYED/0.

Best regards

Anton


2018-08-12 15:08 GMT+02:00 Adrian Bunk :
> Dear maintainer,
>
> I've prepared an NMU for openfoam (versioned as 4.1+dfsg1-2.2) and
> uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it.
>
> This change works around gcc 8 seemingly using more memory,
> which caused FTBFS on mips/mipsel.
>
> cu
> Adrian
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#903182: marked as done (mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8"))

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 13:40:53 +
with message-id 
and subject line Bug#903182: fixed in mtr 0.92-2
has caused the Debian Bug report #903182,
regarding mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8")
to be marked as done.

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

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


-- 
903182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mtr
Version: 0.92-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./bootstrap.sh
touch configure.in && \
touch aclocal.m4 && \
touch configure
head -n 1 debian/changelog | sed 's/[^(]*(\([^-]*\)-.*/\1/' > .tarball-version
autoreconf -fi
autoreconf: 'configure.ac' and 'configure.in' both present.
autoreconf: proceeding with 'configure.ac'

[... snipped ...]

dh_auto_install --builddirectory=mtr --destdir=debian/mtr
cd mtr && make -j1 install DESTDIR=/<>/debian/mtr 
AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>/mtr'
make[3]: Entering directory '/<>/mtr'
 /bin/mkdir -p '/<>/debian/mtr/usr/bin'
  /usr/bin/install -c mtr mtr-packet '/<>/debian/mtr/usr/bin'
make  install-exec-hook
make[4]: Entering directory '/<>/mtr'
`setcap cap_net_raw+ep /<>/debian/mtr/usr/bin/mtr-packet` \
|| chmod u+s /<>/debian/mtr/usr/bin/mtr-packet
/bin/bash: line 1: setcap: command not found
make[4]: Leaving directory '/<>/mtr'
 /bin/mkdir -p 
'/<>/debian/mtr/usr/share/bash-completion/completions'
 /usr/bin/install -c -m 644 ../bash-completion/mtr 
'/<>/debian/mtr/usr/share/bash-completion/completions'
 /bin/mkdir -p '/<>/debian/mtr/usr/share/man/man8'
 /usr/bin/install -c -m 644 ../mtr.8 ../mtr-packet.8 
'/<>/debian/mtr/usr/share/man/man8'
make[3]: Leaving directory '/<>/mtr'
make[2]: Leaving directory '/<>/mtr'
dh_auto_install --builddirectory=mtr-tiny --destdir=debian/mtr-tiny
cd mtr-tiny && make -j1 install 
DESTDIR=/<>/debian/mtr-tiny AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>/mtr-tiny'
make[3]: Entering directory '/<>/mtr-tiny'
 /bin/mkdir -p '/<>/debian/mtr-tiny/usr/bin'
  /usr/bin/install -c mtr mtr-packet '/<>/debian/mtr-tiny/usr/bin'
make  install-exec-hook
make[4]: Entering directory '/<>/mtr-tiny'
`setcap cap_net_raw+ep /<>/debian/mtr-tiny/usr/bin/mtr-packet` \
|| chmod u+s /<>/debian/mtr-tiny/usr/bin/mtr-packet
/bin/bash: line 1: setcap: command not found
make[4]: Leaving directory '/<>/mtr-tiny'
 /bin/mkdir -p 
'/<>/debian/mtr-tiny/usr/share/bash-completion/completions'
 /usr/bin/install -c -m 644 ../bash-completion/mtr 
'/<>/debian/mtr-tiny/usr/share/bash-completion/completions'
 /bin/mkdir -p '/<>/debian/mtr-tiny/usr/share/man/man8'
 /usr/bin/install -c -m 644 ../mtr.8 ../mtr-packet.8 
'/<>/debian/mtr-tiny/usr/share/man/man8'
make[3]: Leaving directory '/<>/mtr-tiny'
make[2]: Leaving directory '/<>/mtr-tiny'
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   debian/rules override_dh_installchangelogs-arch
make[1]: Entering directory '/<>'
dh_installchangelogs -a NEWS
make[1]: Leaving directory '/<>'
   dh_installman -a
dh_installman: Cannot find (any matches for) "mtr/mtr.8" (tried in .)

dh_installman: Aborting due to earlier error
debian/rules:7: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder
but it also fails in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: mtr
Source-Version: 0.92-2

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

Debian distribution maintenance software
pp.
Sam

Bug#905966: linux-image-4.9.0-0.bpo.7-amd64: CVE-2018-5390 not fixed?

[Gerlof Fokkema]

Package: src:linux
Version: 4.9.110-1~deb8u1
Severity: grave
Tags: newcomer

Dear Maintainer,

On august 6th DSA-4266-1 linux was announced
(https://www.debian.org/security/2018/dsa-4266.en.html).
However, source package linux-4.9 (debian oldstable, jessie) is not included in
the overview for CVE-2018-5390
(https://security-tracker.debian.org/tracker/CVE-2018-5390).

On august 8th an updated kernel package was published for affected
distributions with linux kernel 4.9+ (debian stable, stretch).

On debian jessie I can only install up to 4.9.0-0.bpo.7-amd64
(4.9.110-1~deb8u1), which, as far as I can tell, should be affected by
CVE-2018-5390 as well. As of today there does not seem to be any update
regarding this CVE with respect to linux-4.9 on debian oldstable (jessie).

Can I conclude linux-4.9 on debian oldstable is not affected, or will there be
an update for this package as well?

Thanks in advance,
Gerlof Fokkema


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Supermicro
product_name: X8DTU
product_version: 1234567890
chassis_vendor: Supermicro
chassis_version: 1234567890
bios_vendor: American Megatrends Inc.
bios_version: 2.1c  
board_vendor: Supermicro
board_name: X8DTU
board_version: 1234567890

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

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

Versions of packages linux-image-4.9.0-0.bpo.7-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.120+deb8u3
ii  kmod18-3
ii  linux-base  4.3~bpo8+1

Versions of packages linux-image-4.9.0-0.bpo.7-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.1.0-2~bpo8+1

Versions of packages linux-image-4.9.0-0.bpo.7-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02~beta2-22+deb8u1
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-0.bpo.7-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Processed: tagging 903629

[Debian Bug Tracking System]

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

> tags 903629 + ftbfs
Bug #903629 [php-sabredav] php-sabredav: FTBFS in unstable
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#872692: hgview fails to run

[James Cowgill]

Control: tags -1 sid buster fixed-upstream

Hi,

This is fixed upstream in 1.10.2 (or possibly earlier). It would be good
to get that version uploaded in Debian.

Also tagging "sid buster" because my understanding from the upstream fix
is that this is only broken with mercurial >= 4.3 (and stretch has 4.0).

James



signature.asc
Description: OpenPGP digital signature

Processed: Bug#872692: hgview fails to run

[Debian Bug Tracking System]

Processing control commands:

> tags -1 sid buster fixed-upstream
Bug #872692 [hgview] hgview fails to run
Added tag(s) sid, fixed-upstream, and buster.

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

Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.2

[Adrian Bunk]

Dear maintainer,

I've prepared an NMU for openfoam (versioned as 4.1+dfsg1-2.2) and 
uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it.

This change works around gcc 8 seemingly using more memory,
which caused FTBFS on mips/mipsel.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru openfoam-4.1+dfsg1/debian/changelog openfoam-4.1+dfsg1/debian/changelog
--- openfoam-4.1+dfsg1/debian/changelog	2018-08-03 23:38:10.0 +0300
+++ openfoam-4.1+dfsg1/debian/changelog	2018-08-12 13:41:17.0 +0300
@@ -1,3 +1,11 @@
+openfoam (4.1+dfsg1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -g1 on mips/mipsel to workaround address space
+limitations.
+
+ -- Adrian Bunk   Sun, 12 Aug 2018 13:41:17 +0300
+
 openfoam (4.1+dfsg1-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru openfoam-4.1+dfsg1/debian/rules openfoam-4.1+dfsg1/debian/rules
--- openfoam-4.1+dfsg1/debian/rules	2018-04-11 22:25:22.0 +0300
+++ openfoam-4.1+dfsg1/debian/rules	2018-08-12 13:41:17.0 +0300
@@ -3,6 +3,11 @@
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 VENDOR := $(shell dpkg-vendor --derives-from Ubuntu && echo Ubuntu || echo Debian)
 
+# less debug info to avoid running out of address space during build
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+export DEB_CXXFLAGS_MAINT_APPEND = -g1
+endif
+
 %:
 	dh $@
 

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

I've uploaded a version that should fix this.

On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius  wrote:
> > On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> > > But the upgrade path from stretch is not clean:
> > > 
> > >   Selecting previously unselected package python3-cliapp.
> > >   Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
> > >   Unpacking python3-cliapp (1.20170827-1) ...
> > >   dpkg: error processing archive 
> > > /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
> > >trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also 
> > > in package python-cliapp 1.20160724-2
> > >   Errors were encountered while processing:
> > >/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb
> > > 
> > > So you will need some Breaks and Replaces against the old
> > > package in stretch.
> > 
> > I see the problem now. I was confused by you calling it an upgrade problem,
> > when it isn't. It's a problem with one package containing the same file as
> > another package, and the two packages are only tangentially related.
> > 
> > It doesn't seem to me to be a particularly likely scenario, to me. A user
> > would need to change their sources.list to point from stretch to buster,
> > and then not upgrade anything else, but install python3-cliapp.
> > 
> > I'll add the Breaks and Replaces some day. Or have all of cliapp removed
> > from Debian.
> 
> Hi Lars,
> 
> Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
> is a key package and as such a potential blocker for the new Debian release.
> 
> If you are pondering a removal (per your last sentence), the following
> packages currently rely on cliapp in testing and would need to migrate
> away first:
> 
> """
> 
> Checking reverse dependencies...
> # Broken Depends:
> 
> cmdtest: cmdtest
> freedom-maker: freedom-maker
> live-wrapper: live-wrapper
> vmdb2: vmdb2
> vmdebootstrap: vmdebootstrap
> 
> # Broken Build-Depends:
> cmdtest: python-cliapp
> freedom-maker: python3-cliapp
> live-wrapper: python-cliapp
> vmdb2: python3-cliapp
> """
> 
> Thanks,
> ~Niels
> 


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

Bug#905910: marked as done (libssh has dropped libssh_threads library)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 12:50:31 +
with message-id 
and subject line Bug#905910: fixed in remmina 1.2.31.2+dfsg-2
has caused the Debian Bug report #905910,
regarding libssh has dropped libssh_threads library
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.)


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

Hi,

libssh 0.8.0 has dropped the libssh_thread library and the only function
exported by it has been merged in the main library

Applying the attached patch should fix the build

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-rc4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru remmina-1.2.31.2+dfsg/debian/control 
remmina-1.2.31.2+dfsg/debian/control
--- remmina-1.2.31.2+dfsg/debian/control2018-07-29 14:54:23.0 
+0200
+++ remmina-1.2.31.2+dfsg/debian/control2018-08-11 16:03:14.0 
+0200
@@ -20,7 +20,7 @@
  libsoup2.4-dev,
  libspice-client-gtk-3.0-dev,
  libspice-protocol-dev,
- libssh-dev (>= 0.8.0~20170825.94fa1e38),
+ libssh-dev (>= 0.8.0),
  libtelepathy-glib-dev,
  libvncserver-dev,
  libvte-2.91-dev,
diff -Nru remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch 
remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch
--- remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch   
1970-01-01 01:00:00.0 +0100
+++ remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch   
2018-08-11 16:03:14.0 +0200
@@ -0,0 +1,14 @@
+--- a/cmake/FindLIBSSH.cmake
 b/cmake/FindLIBSSH.cmake
+@@ -42,11 +42,6 @@ find_library(LIBSSH_LIBRARY
+   PATHS ${PC_LIBSSH_PKGCONF_LIBRARY_DIRS}
+ )
+ 
+-find_library(LIBSSH_THREADS_LIBRARY
+-  NAMES ssh_threads
+-  PATHS ${PC_LIBSSH_LIBDIR} ${PC_LIBSSH_LIBRARY_DIRS}
+-)
+-
+ include(FindPackageHandleStandardArgs)
+ 
+ find_package_handle_standard_args(LIBSSH DEFAULT_MSG LIBSSH_LIBRARY 
LIBSSH_INCLUDE_DIR)
diff -Nru remmina-1.2.31.2+dfsg/debian/patches/series 
remmina-1.2.31.2+dfsg/debian/patches/series
--- remmina-1.2.31.2+dfsg/debian/patches/series 2018-08-01 22:20:23.0 
+0200
+++ remmina-1.2.31.2+dfsg/debian/patches/series 2018-08-11 16:03:14.0 
+0200
@@ -1 +1,2 @@
 0001-Fix_warnings_on_manpages.patch
+0002-remove-libssh_threads.patch
--- End Message ---
--- Begin Message ---
Source: remmina
Source-Version: 1.2.31.2+dfsg-2

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated remmina package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 14:27:56 +0200
Source: remmina
Binary: remmina remmina-common remmina-dev remmina-plugin-rdp 
remmina-plugin-vnc remmina-plugin-xdmcp remmina-plugin-nx remmina-plugin-spice 
remmina-plugin-telepathy remmina-plugin-secret remmina-plugin-exec
Architecture: source
Version: 1.2.31.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Matteo F. Vescovi 
Description:
 remmina- GTK+ Remote Desktop Client
 remmina-common - Common files for Remmina
 remmina-dev - Headers for Remmina
 remmina-plugin-exec - EXEC plugin for Remmina
 remmina-plugin-nx - NX plugin for Remmina
 remmina-plugin-rdp - RDP plugin for Remmina
 remmina-plugin-secret - Secret plugin for Remmina
 remmina-plugin-spice - Spice plugin for Remmina
 remmina-plugin-telepathy - Telepathy pl

Bug#905960: Errors from dmesg

[Andrew Goodbody]

These errors show in dmesg

[  794.423036] radeon :01:00.0: evergreen_cs_track_validate_texture:855 
texture bo too small (layer size 9338880, offset 0, max layer 1, depth 1, bo 
size 4096) (1920 1216)
[  794.423070] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
[  798.068277] fuse init (API version 7.26)
[  809.632694] radeon :01:00.0: ring 0 stalled for more than 10240msec
[  809.632702] radeon :01:00.0: GPU lockup (current fence id 
0x028f last fence id 0x0290 on ring 0)
[  809.950539] radeon :01:00.0: Saved 23 dwords of commands on ring 0.
[  809.950551] radeon :01:00.0: GPU softreset: 0x0019
[  809.950553] radeon :01:00.0:   GRBM_STATUS   = 0xE5703CA0
[  809.950555] radeon :01:00.0:   GRBM_STATUS_SE0   = 0xFC07
[  809.950557] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[  809.950559] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
[  809.950561] radeon :01:00.0:   SRBM_STATUS2  = 0x
[  809.950563] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x0100
[  809.950565] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00011000
[  809.950567] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x00068404
[  809.950569] radeon :01:00.0:   R_008680_CP_STAT  = 0x80878647
[  809.950571] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  809.951993] radeon :01:00.0: GRBM_SOFT_RESET=0x7F6B
[  809.952046] radeon :01:00.0: SRBM_SOFT_RESET=0x0100
[  809.953192] radeon :01:00.0:   GRBM_STATUS   = 0x3828
[  809.953194] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
[  809.953196] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[  809.953198] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
[  809.953199] radeon :01:00.0:   SRBM_STATUS2  = 0x
[  809.953201] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
[  809.953203] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x
[  809.953205] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x
[  809.953207] radeon :01:00.0:   R_008680_CP_STAT  = 0x
[  809.953209] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  809.953220] radeon :01:00.0: GPU reset succeeded, trying to resume
[  809.976424] [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
[  809.980840] [drm] PCIE GART of 1024M enabled (table at 0x00162000).
[  809.980931] radeon :01:00.0: WB enabled
[  809.980934] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x4033ff39
[  809.980937] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0xf2e8ad02
[  809.981685] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0x7f7ea565
[  809.997885] [drm] ring test on 0 succeeded in 2 usecs
[  809.997896] [drm] ring test on 3 succeeded in 6 usecs
[  810.173646] [drm] ring test on 5 succeeded in 2 usecs
[  810.173654] [drm] UVD initialized successfully.
[  810.194052] [drm] ib test on ring 0 succeeded in 0 usecs
[  810.194129] [drm] ib test on ring 3 succeeded in 0 usecs
[  810.848908] [drm] ib test on ring 5 succeeded
[  821.089203] radeon :01:00.0: ring 0 stalled for more than 10092msec
[  821.089209] radeon :01:00.0: GPU lockup (current fence id 
0x0295 last fence id 0x0296 on ring 0)
[  821.403656] radeon :01:00.0: Saved 23 dwords of commands on ring 0.
[  821.403668] radeon :01:00.0: GPU softreset: 0x0019
[  821.403670] radeon :01:00.0:   GRBM_STATUS   = 0xE5703CA0
[  821.403672] radeon :01:00.0:   GRBM_STATUS_SE0   = 0xFC07
[  821.403675] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[  821.403677] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
[  821.403679] radeon :01:00.0:   SRBM_STATUS2  = 0x
[  821.403681] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x0100
[  821.403692] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00011000
[  821.403695] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x00068404
[  821.403699] radeon :01:00.0:   R_008680_CP_STAT  = 0x80878647
[  821.403701] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  821.409670] radeon :01:00.0: GRBM_SOFT_RESET=0x7F6B
[  821.409723] radeon :01:00.0: SRBM_SOFT_RESET=0x0100
[  821.410868] radeon :01:00.0:   GRBM_STATUS   = 0x3828
[  821.410870] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
[  821.410872] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[  821.410874] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
[  821.410876] radeon :01:00.0:   SRBM_STATUS2  = 0x

Bug#905910: Bug #905910 in remmina marked as pending

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #905910 in remmina 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-remote-team/remmina/commit/eeafde5de5570b9ba3285a202b81da49af26c62e


debian/patches/: patchset updated

- 0002-Fix_Cmake_rule_for_LibSSH.patch added

Closes: #905910



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905910

Processed: Bug #905910 in remmina marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905910 [src:remmina] libssh has dropped libssh_threads library
Added tag(s) pending.

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

Bug#905960: Errors from dmesg

[Andrew Goodbody]

dmesg.txt
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

These errors show in dmesg

Bug#905960: System was ok, broken by dist-upgrade

[Andrew Goodbody]

System was working ok until I rebooted after dist-upgrade.
Booting Ubuntu 18.04 live CD works ok.
Login screen is ok.

Bug#903367: marked as done (vcdimager: FTBFS in buster/sid (dh_installinfo: Cannot find "docs/vcd-info.info"))

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 12:22:00 +
with message-id <3cda02c6-bf50-8131-62a9-74b6de47c...@thykier.net>
and subject line vcdimager: FTBFS in buster/sid (dh_installinfo: Cannot find 
"docs/vcd-info.info")
has caused the Debian Bug report #903367,
regarding vcdimager: FTBFS in buster/sid (dh_installinfo: Cannot find 
"docs/vcd-info.info")
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.)


-- 
903367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vcdimager
Version: 2.0.1+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh_testdir
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:72: installing './compile'
configure.ac:51: installing './config.guess'
configure.ac:51: installing './config.sub'

[... snipped ...]

 /usr/bin/install -c -m 644 vcdxbuild.1 vcdxgen.1 vcdxrip.1 vcdxminfo.1 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/share/man/man1'
make[5]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[4]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[4]: Entering directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
Making install in test
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/test'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/test'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/test'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/test'
Making install in docs
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/docs'
Making install in example
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/example'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/example'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/example'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/example'
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libvcdinfo.pc 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
make[1]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
dh_testdir -a
dh_testroot -a
dh_installdocs -a
dh_installinfo -a
dh_installinfo: Cannot find (any matches for) "docs/vcd-info.info" (tried in .)

debian/rules:68: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: vcdimager
Source-Version: 2.0.1+dfsg-3

On Mon, 09 Jul 2018 

Bug#905960: amdgpu: After login the screen is corrupted, it is unusable in this state

[Andrew Goodbody]

Package: xserver-xorg-video-amdgpu
Version: 18.0.1-1+b1
Severity: critical
File: amdgpu
Justification: breaks the whole system



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Oct  7  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul  1 18:07 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20)

Xorg X server log files on system:
--
-rw-r--r-- 1 ag ag 42666 Aug 12 12:52 /home/ag/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/ag/.local/share/xorg/Xorg.0.log):
---
[   790.408] (--) Log file renamed from 
"/home/ag/.local/share/xorg/Xorg.pid-5321.log" to 
"/home/ag/.local/share/xorg/Xorg.0.log"
[   793.189] 
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[   793.189] Build Operating System: Linux 4.9.0-6-amd64 x86_64 Debian
[   793.189] Current Operating System: Linux quad 4.17.0-1-amd64 #1 SMP Debian 
4.17.8-1 (2018-07-20) x86_64
[   793.189] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-amd64 
root=/dev/md0 ro quiet
[   793.189] Build Date: 01 July 2018  05:07:24PM
[   793.189] xorg-server 2:1.20.0-3 (https://www.debian.org/support) 
[   793.189] Current version of pixman: 0.34.0
[   793.189]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   793.189] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   793.189] (==) Log file: "/home/ag/.local/share/xorg/Xorg.0.log", Time: Sun 
Aug 12 12:51:32 2018
[   793.207] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   793.259] (==) No Layout section.  Using the first Screen section.
[   793.259] (==) No screen section available. Using defaults.
[   793.259] (**) |-->Screen "Default Screen Section" (0)
[   793.259] (**) |   |-->Monitor ""
[   793.267] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   793.267] (==) Automatically adding devices
[   793.267] (==) Automatically enabling devices
[   793.267] (==) Automatically adding GPU devices
[   793.267] (==) Max clients allowed: 256, resource mask: 0x1f
[   793.267] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   793.267]Entry deleted from font path.
[   793.267] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   793.267] (==) ModulePath set to "/usr/lib/xorg/modules"
[   793.267] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   793.267] (II) Loader magic: 0x55d8c2a26de0
[   793.267] (II) Module ABI versions:
[   793.267]X.Org ANSI C Emulation: 0.4
[   793.267]X.Org Video Driver: 24.0
[   793.267]X.Org XInput driver : 24.1
[   793.267]X.Org Server Extension : 10.0
[   793.268] (++) using VT number 2

[   793.272] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_38
[   793.273] (II) xfree86: Adding drm device (/dev/dri/card0)
[   793.275] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[   793.281] (--) PCI:*(1@0:0:0) 1002:6779:174b:a004 rev 0, Mem @ 
0xd000/268435456, 0xfade/131072, I/O @ 0xb000/256, BIOS @ 
0x/131072
[   793.281] (--) PCI: (6@0:5:0) 14f1:8800:0070:9002 rev 5, Mem @ 
0xfd00/16777216
[   793.281] (II) LoadModule: "glx"
[   793.301] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   793.366] (II) Module glx: vendor="X.Org Foundation"
[   793.366]compiled for 1.20.0, module version = 1.0.0
[   793.366]ABI class: X.Org Server Extension, version 10.0
[   793.366] (II) Applying OutputClass "Radeon" to /dev/dri/card0
[   793.366]loading driver: radeon
[   793.366] (==) Matched radeon as autoconfigured driver 0
[   793.366] (==) Matched ati as autoconfigured driver 1
[   793.366] (==) Matched modesetti

Bug#903367: vcdimager: FTBFS in buster/sid (dh_installinfo: Cannot find "docs/vcd-info.info")

[Niels Thykier]

Source: vcdimager
Source-Version: 2.0.1+dfsg-3

On Mon, 09 Jul 2018 00:07:05 + Santiago Vila  wrote:
> Package: src:vcdimager
> Version: 2.0.1+dfsg-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]


Fixed in 2.0.1+dfsg-3 but I forgot the changelog entry.

Thanks,
~Niels

Bug#902760: [Bug #902760] Testsuite fails with ARPACK 3.6 (#1107)

[Sylvestre Ledru]

Looks like https://github.com/opencollab/arpack-ng/issues/142 ?

S


On 27/07/2018 01:34, Andreas Tille wrote:
> Hi,
>
> just forwarding the suspicion of igraph upstream that the problem is
> caused by arpack.  I'm tempted to reassign bug #902760 but I'd like
> to hear your opinion first.
>
> Kind regards
>
>  Andreas.
>
> - Forwarded message from Tamás Nepusz  -
>
> Date: Thu, 26 Jul 2018 11:19:03 -0700
> From: Tamás Nepusz 
> To: igraph/igraph 
> Cc: Andreas Tille , Author 
> Subject: Re: [igraph/igraph] Testsuite fails with ARPACK 3.6 (#1107)
>
> Okay, I am pretty certain that this is an inherent issue with ARPACK 3.6; the 
> same problem can also be triggered in GNU Octave (4.4.0) when linked with 
> ARPACK 3.6 (I tried it on a Mac with Homebrew). The code below produces the 
> PageRank matrix of the graph from the igraph test case:
>
> ```
> octave:1> m = ones(11, 11) * 0.15 / 11;
> octave:2> m(1, 2:11) += 0.85;
> octave:3> m(2:11, 1) = (1 - m(1, 1)) / 10;
> ```
>
> and it blows up exactly the same way:
>
> ```
> octave:4> [v, lambda] = eigs(m, 1)
> error: __eigs__: eigs: error - in dnaupd
> error: called from
> eigs at line 285 column 18
> ```
>
> I'll file a bug report to `arpack-ng`.
>

Bug#896230: marked as done (python-gpod: gpod fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 10:33:57 +
with message-id 
and subject line Bug#896230: fixed in libgpod 0.8.3-12
has caused the Debian Bug report #896230,
regarding python-gpod: gpod fails to import
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.)


-- 
896230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-gpod
Version: 0.8.3-11
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-gpod importing the module gpod
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/gpod/__init__.py", line 8, in 
from gpod import *
  File "/usr/lib/python2.7/dist-packages/gpod/gpod.py", line 28, in 
_gpod = swig_import_helper()
  File "/usr/lib/python2.7/dist-packages/gpod/gpod.py", line 27, in 
swig_import_helper
return importlib.import_module('_gpod')
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named _gpod

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: libgpod
Source-Version: 0.8.3-12

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libgpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 13:11:58 +0300
Source: libgpod
Binary: libgpod-dev libgpod4 libgpod-common libgpod-doc python-gpod libgpod-cil 
libgpod-cil-dev
Architecture: source
Version: 0.8.3-12
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 libgpod-cil - CLI bindings for libgpod
 libgpod-cil-dev - CLI bindings for libgpod -- development files
 libgpod-common - common files for libgpod
 libgpod-dev - development files for libgpod
 libgpod-doc - documentation for libgpod
 libgpod4   - library to read and write songs and artwork to an iPod
 python-gpod - Python bindings for libgpod
Closes: 896230
Changes:
 libgpod (0.8.3-12) unstable; urgency=high
 .
   * QA upload.
   * python-gpod: Add the missing dependency on python-gobject-2.
 (Closes: #896230)
Checksums-Sha1:
 6fde5fa66f49cc3c3dd09535e69c77fcf7c47ea2 3164 libgpod_0.8.3-12.dsc
 83d97af7629bda34e4770d02a382afce6c1e5d00 16600 libgpod_0.8.3-12.debian.tar.xz
Checksums-Sha256:
 3cfc0e8094d760f573384f659a98550eb607d2d4f99fd3d38e535328c2f319bd 3164 
libgpod_0.8.3-12.dsc
 9d71246c5458db70f6e3523085c756d58d69692422ac413972182d8c52f2e361 16600 
libgpod_0.8.3-12.debian.tar.xz
Files:
 4d8e0b7ddaf1f6081b87a6bb7fd0faf0 3164 libs optional libgpod_0.8.3-12.dsc
 40ea48cfdf3da9db6935b6d46c4dc7d5 16600 libs optional 
libgpod_0.8.3-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltwCP8ACgkQiNJCh6LY
mLHcixAAzYgrOs1/yMj1sf8mFpliTIDac4A0z9zoO2EfpyoVEnQm9oqP8bEEVzgW
kgpSjUhN17Zxo64n+oBDg4WgeOXF9g/b2C6n3mAMnH1bKpjT/8MqvvmJH7vrAMQs
mwrY3FRMTm8EniR8liSz7k1+qHWkBTjwwuIw4R65weWotoUpfz8vXdw+VoVuIZnK
k542sFa1EKtub1rco0stAvaBTGC4+59By6o2Non5Mk0KgPyQHZgA/X3DRWMW8vfi
XKEYe72hHrPiyocnBcXEQnKnhBR+LykDAJNZF4Z6wr54RxHVjz7ojdXJwmfWEiic
XErOgnNny4HFos7WHQEzZ4FprEwoXtLN6q0yscFQxve6xvTtYEME1byivEHFVq94
HUq2x4GsvrRtwHqXsluyJJUPRT9QKZil7f9fpKl4XgizQ+6O3QLfay8OBp3gjx4B
S+ogpeOjMd4hrzry++eJSSwWiX5jRAn+x/FAUv87ytRTbIL5c3aZxYxz/qQQNYFn
/YvpJ0+PawQzOYNG2Ys4o/5XLaa2kIeNpFpPcRDUOp4Fbjp2NesX02B4tvegnIcn
q4bfJsYh2EnN9McERski+7E35lfu5gyQg9KBADhpLzJz9CYcLNSCiga5wrPhcINB
hkVWHOOGLx/IVQ8nr1hzdRyX/NfPXNe9VE56pLPyFHBx8KKi5Jo=

Processed: found 896230 in 0.8.3-8.2

[Debian Bug Tracking System]

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

> found 896230 0.8.3-8.2
Bug #896230 [python-gpod] python-gpod: gpod fails to import
Marked as found in versions libgpod/0.8.3-8.2.
> thanks
Stopping processing here.

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

Bug#905955: s-tui: Please, add python3-distutils to its depedencies

[Manolo Díaz]

Package: s-tui
Version: 0.7.5-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

s-tui doesn't ask for installing the python3-distutils package, but it's
needed.

Traceback (most recent call last):
  File "/usr/bin/s-tui", line 11, in 
load_entry_point('s-tui==0.7.5', 'console_scripts', 's-tui')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 43, in 
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'


Best regards,
Manolo Díaz


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

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

Versions of packages s-tui depends on:
ii  python3 3.6.5-3
ii  python3-psutil  5.4.6-1+b1
ii  python3-urwid   2.0.1-2+b1

s-tui recommends no packages.

s-tui suggests no packages.

-- no debconf information

Bug#903801: marked as done (python-pika,python-pika-doc: both ship /usr/share/doc/python-pika/README.rst)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 09:51:31 +
with message-id 
and subject line Bug#903801: fixed in python-pika 0.11.0-3
has caused the Debian Bug report #903801,
regarding python-pika,python-pika-doc: both ship 
/usr/share/doc/python-pika/README.rst
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.)


-- 
903801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pika,python-pika-doc
Version: 0.11.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

This is probably caused by a behavioral change of dh_installdocs in
debhelper compat level 11.

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

  Selecting previously unselected package python-pika-doc.
  Preparing to unpack .../python-pika-doc_0.11.0-2_all.deb ...
  Unpacking python-pika-doc (0.11.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pika-doc_0.11.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-pika/README.rst', which is also 
in package python-pika 0.11.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pika-doc_0.11.0-2_all.deb

cheers,

Andreas


python-pika=0.11.0-2_python-pika-doc=0.11.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pika
Source-Version: 0.11.0-3

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

Debian distribution maintenance software
pp.
Jan Dittberner  (supplier of updated python-pika package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Aug 2018 11:24:46 +0200
Source: python-pika
Binary: python-pika python-pika-doc python3-pika
Architecture: source all
Version: 0.11.0-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Jan Dittberner 
Description:
 python-pika - AMQP client library for Python 2
 python-pika-doc - AMQP client library documentation
 python3-pika - AMQP client library for Python 3
Closes: 903801
Changes:
 python-pika (0.11.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
 .
   [ Jan Dittberner ]
   * Fix "both ship /usr/share/doc/python-pika/README.rst" remove
 debian/python-pika.docs and debian/python3-pika.docs to avoid installing
 README.rst that is in python-pika-doc too (Closes: #903801)
Checksums-Sha1:
 3f756793a75472afdd835a9c6e4a520880296a70 2069 python-pika_0.11.0-3.dsc
 5641dd0703a6e4ca4d68ca26b4cc648ae749254f 4656 
python-pika_0.11.0-3.debian.tar.xz
 74e3e50845ec210282bd2626fbe80708dd93bbc2 137336 
python-pika-doc_0.11.0-3_all.deb
 25ad63326053c1c5578e50fe2123029dd32fa765 94280 python-pika_0.11.0-3_all.deb
 4b10da3d95e64e44524532042762a4944da4cbde 10117 
python-pika_0.11.0-3_amd64.buildinfo
 bbee0be41733617a848f16b03d4d8bacdf06d65b 94336 python3-pika_0.11.0-3_all.deb
Checksums-Sha256:
 3858de6dae49fbfd28d9c979628bf3630382e5c0c7e9f53ebb07398d8b138d12 2069 
python-pika_0.11.0-3.dsc
 0cb4d7789d46c9c6f478b3b135546b0d1e5f619847836ad7fac6add78deb7802 4656 
python-pika_0.11.0-3.debian.tar.xz
 4ff7e97d457a7e9c242ea0b493ce3998f14b9960666b417e933f6a379d71bf59 137336 
python-pika-doc_0.11.0-3_all.deb
 2e526a4ac21baeb14f873a2f76f2cc801fe511a724efbd7d412ba4f195749e69 94280 
python-pika_0.11.0-3_all.deb
 0274b92a17c99a10a0a00c76c3f905b0b9ac6fb3fd68137486b624462b13eae6 10117 
python-pika_0.11.0-3_amd64.buildinfo
 9e61b8abbcb30a4be54940acd07e128935fa65bd66259951e7d197e1b828ee39 94336 
python3-pika_0.11.0-3_all.deb
Files:
 3b712a59dd1c2ad2423c45a4357b0200 2069 python optional python-pika_0.11.0-3.dsc
 ba997598975a8ce58fc178f01e64e46c 4656 python optional 
python-pika_0.11.0-3.debian.tar.xz
 2746a8928250726dbaee1d0a9efede92 137336 doc optional 
python-pika-doc_0.11.0-3_all.deb
 f920fea41da96cbf6222d070d822

Bug#903801: Bug #903801 in python-pika marked as pending

[Jan Dittberner]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-pika/commit/77bd0f9600c8746bf74172307f1860421fdcd6fe


Fix "both ship /usr/share/doc/python-pika/README.rst" remove 
debian/python-pika.docs to avoid installing README.rst that is in 
python-pika-doc too (Closes: #903801)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903801

Processed: Bug #903801 in python-pika marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903801 [python-pika,python-pika-doc] python-pika,python-pika-doc: both 
ship /usr/share/doc/python-pika/README.rst
Added tag(s) pending.

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

Bug#905908: libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3

[Kyle Robbertze]

Curiouser and curiouser...

> $ ldconfig -p | grep libGL.so.1

libGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so.1
libGL.so.1 (libc6) => /usr/lib/i386-linux-gnu/libGL.so.1

> $ ls -lgo /usr/lib/x86_64-linux-gnu/libGL.so.*

lrwxrwxrwx 1 50 Aug 11 15:45 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu

> $ dpkg -S /usr/lib/x86_64-linux-gnu/libGL.so.*

diversion by glx-diversions from: /usr/lib/x86_64-linux-gnu/libGL.so.1
diversion by glx-diversions to: 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
libgl1:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1

During the next run of apt, the post-install re-ran and completed successfully
(though apt did complain about it not running any of the 4 expected actions).







signature.asc
Description: OpenPGP digital signature

Bug#904598: marked as done (libreoffice: Find/Replace dialogs' options are broken in gen vclplug)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 09:07:24 +
with message-id 
and subject line Bug#905408: fixed in libreoffice 1:6.1.0-1
has caused the Debian Bug report #905408,
regarding libreoffice: Find/Replace dialogs' options are broken in gen vclplug
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.)


-- 
905408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice
Version: 1:6.1.0~rc2-3
Severity: important

Dear Maintainer,

Libreoffice's find/replace dialogs' options have become partially hidden
and unusable.  Seen in writer and impress.  I've included a picture of
the dialog from writer.



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

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

Versions of packages libreoffice depends on:
ii  libreoffice-avmedia-backend-gstreamer  1:6.1.0~rc2-3
ii  libreoffice-base   1:6.1.0~rc2-3
ii  libreoffice-calc   1:6.1.0~rc2-3
ii  libreoffice-core   1:6.1.0~rc2-3
ii  libreoffice-draw   1:6.1.0~rc2-3
ii  libreoffice-impress1:6.1.0~rc2-3
ii  libreoffice-math   1:6.1.0~rc2-3
ii  libreoffice-report-builder-bin 1:6.1.0~rc2-3
ii  libreoffice-writer 1:6.1.0~rc2-3
ii  python3-uno1:6.1.0~rc2-3

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-1
ii  fonts-liberation1:1.07.4-7
ii  fonts-liberation2   2.00.1-7
ii  fonts-linuxlibertine5.3.0-4
ii  fonts-noto-hinted   20171026-2
ii  fonts-noto-mono 20171026-2
ii  fonts-sil-gentium-basic 1.102-1
ii  libreoffice-java-common 1:6.1.0~rc2-3
ii  libreoffice-librelogo   1:6.1.0~rc2-3
ii  libreoffice-nlpsolver   0.9+LibO6.1.0~rc2-3
ii  libreoffice-ogltrans1:6.1.0~rc2-3
ii  libreoffice-report-builder  1:6.1.0~rc2-3
ii  libreoffice-script-provider-bsh 1:6.1.0~rc2-3
ii  libreoffice-script-provider-js  1:6.1.0~rc2-3
ii  libreoffice-script-provider-python  1:6.1.0~rc2-3
ii  libreoffice-sdbc-postgresql 1:6.1.0~rc2-3
ii  libreoffice-wiki-publisher  1.2.0+LibO6.1.0~rc2-3

Versions of packages libreoffice suggests:
ii  cups-bsd2.2.8-5
ii  default-jre [java6-runtime] 2:1.10-67
ii  firefox-esr 52.9.0esr-1
ii  ghostscript 9.22~dfsg-2.1
ii  gnupg   2.2.9-1
pn  gpa 
ii  gstreamer1.0-libav  1:1.14.2-dmo1
ii  gstreamer1.0-plugins-bad1:1.14.2-dmo1
ii  gstreamer1.0-plugins-base   1.14.2-dmo1
ii  gstreamer1.0-plugins-good   1.14.2-dmo1
ii  gstreamer1.0-plugins-ugly   1:1.14.2-dmo1
ii  hunspell-en-us [hunspell-dictionary]1:2018.04.16-1
pn  hyphen-hyphenation-patterns 
ii  imagemagick 8:6.9.10.2+dfsg-3
ii  imagemagick-6.q16 [imagemagick] 8:6.9.10.2+dfsg-3
ii  libgl1  1.0.0+git20180308-3
pn  libreoffice-gnome | libreoffice-kde5
pn  libreoffice-grammarcheck
pn  libreoffice-help
pn  libreoffice-l10n
pn  libreoffice-officebean  
ii  libsane 1.0.25-4.1
ii  libxrender1 1:0.9.10-1
pn  myspell-dictionary  
pn  mythes-thesaurus
pn  openclipart2-libreoffice | openclipart-libreoffice  
ii  openjdk-10-jre [java6-runtime

Bug#905408: marked as done (libreoffice: missed radiobuttons and checkbox in forms with gen VCLplug)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 09:07:24 +
with message-id 
and subject line Bug#905408: fixed in libreoffice 1:6.1.0-1
has caused the Debian Bug report #905408,
regarding libreoffice: missed radiobuttons and checkbox in forms with gen 
VCLplug
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.)


-- 
905408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreoffice
Version: 3a6.1.0~rc2-3
Severity: grave
Justification: renders package unusable

I found that in my database forms, at version 6.1 libreoffice, all checkboxes 
and radiobuttons are missing. 
Only their labels exist, but no field to enter/check value. 
Simplest way to observe it is to run: 
soffice -base
and try to choose 'open existing database file'
In 6.0x everything is ok.


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.1.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 12 Aug 2018 08:13:03 +0200
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-help-common 
libreoffice-writer libreoffice-calc libreoffice-impress libreoffice-draw 
libreoffice-math libreoffice-base-core libreoffice-base 
libreoffice-style-breeze libreoffice-style-colibre libreoffice-style-tango 
libreoffice-style-sifr libreoffice-style-elementary libreoffice-gnome 
python3-uno libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-avmedia-backend-gstreamer libreoffice-avmedia-backend-vlc 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-am libreoffice-l10n-ar libreoffice-l10n-as 
libreoffice-l10n-ast libreoffice-l10n-be libreoffice-l10n-bg 
libreoffice-l10n-bn libreoffice-l10n-br libreoffice-l10n-bs libreoffice-l10n-ca 
libreoffice-l10n-cs libreoffice-l10n-cy libreoffice-l10n-da libreoffice-l10n-de
 libreoffice-l10n-dz libreoffice-l10n-el libreoffice-l10n-en-gb 
libreoffice-l10n-en-za libreoffice-l10n-eo libreoffice-l10n-es 
libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa libreoffice-l10n-fi 
libreoffice-l10n-fr libreoffice-l10n-ga libreoffice-l10n-gd libreoffice-l10n-gl 
libreoffice-l10n-gu libreoffice-l10n-gug libreoffice-l10n-he 
libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id 
libreoffice-l10n-is libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka 
libreoffice-l10n-kk libreoffice-l10n-km libreoffice-l10n-kmr 
libreoffice-l10n-kn libreoffice-l10n-ko libreoffice-l10n-lt libreoffice-l10n-lv 
libreoffice-l10n-mk libreoffice-l10n-mn libreoffice-l10n-ml libreoffice-l10n-mr 
libreoffice-l10n-nb libreoffice-l10n-ne libreoffice-l10n-nl libreoffice-l10n-nn 
libreoffice-l10n-nr libreoffice-l10n-nso libreoffice-l10n-oc 
libreoffice-l10n-om libreoffice-l10n-or libreoffice-l10n-pa-in 
libreoffice-l10n-pl libreoffice-l10n-pt
 libreoffice-l10n-pt-br libreoffice-l10n-ro libreoffice-l10n-ru 
libreoffice-l10n-rw libreoffice-l10n-si libreoffice-l10n-sk libreoffice-l10n-sl 
libreoffice-l10n-sr libreoffice-l10n-ss libreoffice-l10n-st libreoffice-l10n-sv 
libreoffice-l10n-ta libreoffice-l10n-te libreoffice-l10n-tg libreoffice-l10n-th 
libreoffice-l10n-tn libreoffice-l10n-tr libreoffice-l10n-ts libreoffice-l10n-ug 
libreoffice-l10n-uk libreoffice-l10n-uz 

Bug#905408: marked as done (libreoffice: missed radiobuttons and checkbox in forms with gen VCLplug)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 09:07:24 +
with message-id 
and subject line Bug#904598: fixed in libreoffice 1:6.1.0-1
has caused the Debian Bug report #904598,
regarding libreoffice: missed radiobuttons and checkbox in forms with gen 
VCLplug
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.)


-- 
904598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreoffice
Version: 3a6.1.0~rc2-3
Severity: grave
Justification: renders package unusable

I found that in my database forms, at version 6.1 libreoffice, all checkboxes 
and radiobuttons are missing. 
Only their labels exist, but no field to enter/check value. 
Simplest way to observe it is to run: 
soffice -base
and try to choose 'open existing database file'
In 6.0x everything is ok.


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.1.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 12 Aug 2018 08:13:03 +0200
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-help-common 
libreoffice-writer libreoffice-calc libreoffice-impress libreoffice-draw 
libreoffice-math libreoffice-base-core libreoffice-base 
libreoffice-style-breeze libreoffice-style-colibre libreoffice-style-tango 
libreoffice-style-sifr libreoffice-style-elementary libreoffice-gnome 
python3-uno libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-avmedia-backend-gstreamer libreoffice-avmedia-backend-vlc 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-am libreoffice-l10n-ar libreoffice-l10n-as 
libreoffice-l10n-ast libreoffice-l10n-be libreoffice-l10n-bg 
libreoffice-l10n-bn libreoffice-l10n-br libreoffice-l10n-bs libreoffice-l10n-ca 
libreoffice-l10n-cs libreoffice-l10n-cy libreoffice-l10n-da libreoffice-l10n-de
 libreoffice-l10n-dz libreoffice-l10n-el libreoffice-l10n-en-gb 
libreoffice-l10n-en-za libreoffice-l10n-eo libreoffice-l10n-es 
libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa libreoffice-l10n-fi 
libreoffice-l10n-fr libreoffice-l10n-ga libreoffice-l10n-gd libreoffice-l10n-gl 
libreoffice-l10n-gu libreoffice-l10n-gug libreoffice-l10n-he 
libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id 
libreoffice-l10n-is libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka 
libreoffice-l10n-kk libreoffice-l10n-km libreoffice-l10n-kmr 
libreoffice-l10n-kn libreoffice-l10n-ko libreoffice-l10n-lt libreoffice-l10n-lv 
libreoffice-l10n-mk libreoffice-l10n-mn libreoffice-l10n-ml libreoffice-l10n-mr 
libreoffice-l10n-nb libreoffice-l10n-ne libreoffice-l10n-nl libreoffice-l10n-nn 
libreoffice-l10n-nr libreoffice-l10n-nso libreoffice-l10n-oc 
libreoffice-l10n-om libreoffice-l10n-or libreoffice-l10n-pa-in 
libreoffice-l10n-pl libreoffice-l10n-pt
 libreoffice-l10n-pt-br libreoffice-l10n-ro libreoffice-l10n-ru 
libreoffice-l10n-rw libreoffice-l10n-si libreoffice-l10n-sk libreoffice-l10n-sl 
libreoffice-l10n-sr libreoffice-l10n-ss libreoffice-l10n-st libreoffice-l10n-sv 
libreoffice-l10n-ta libreoffice-l10n-te libreoffice-l10n-tg libreoffice-l10n-th 
libreoffice-l10n-tn libreoffice-l10n-tr libreoffice-l10n-ts libreoffice-l10n-ug 
libreoffice-l10n-uk libreoffice-l10n-uz 

Bug#904598: marked as done (libreoffice: Find/Replace dialogs' options are broken in gen vclplug)

[Debian Bug Tracking System]

Your message dated Sun, 12 Aug 2018 09:07:24 +
with message-id 
and subject line Bug#904598: fixed in libreoffice 1:6.1.0-1
has caused the Debian Bug report #904598,
regarding libreoffice: Find/Replace dialogs' options are broken in gen vclplug
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.)


-- 
904598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice
Version: 1:6.1.0~rc2-3
Severity: important

Dear Maintainer,

Libreoffice's find/replace dialogs' options have become partially hidden
and unusable.  Seen in writer and impress.  I've included a picture of
the dialog from writer.



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

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

Versions of packages libreoffice depends on:
ii  libreoffice-avmedia-backend-gstreamer  1:6.1.0~rc2-3
ii  libreoffice-base   1:6.1.0~rc2-3
ii  libreoffice-calc   1:6.1.0~rc2-3
ii  libreoffice-core   1:6.1.0~rc2-3
ii  libreoffice-draw   1:6.1.0~rc2-3
ii  libreoffice-impress1:6.1.0~rc2-3
ii  libreoffice-math   1:6.1.0~rc2-3
ii  libreoffice-report-builder-bin 1:6.1.0~rc2-3
ii  libreoffice-writer 1:6.1.0~rc2-3
ii  python3-uno1:6.1.0~rc2-3

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-1
ii  fonts-liberation1:1.07.4-7
ii  fonts-liberation2   2.00.1-7
ii  fonts-linuxlibertine5.3.0-4
ii  fonts-noto-hinted   20171026-2
ii  fonts-noto-mono 20171026-2
ii  fonts-sil-gentium-basic 1.102-1
ii  libreoffice-java-common 1:6.1.0~rc2-3
ii  libreoffice-librelogo   1:6.1.0~rc2-3
ii  libreoffice-nlpsolver   0.9+LibO6.1.0~rc2-3
ii  libreoffice-ogltrans1:6.1.0~rc2-3
ii  libreoffice-report-builder  1:6.1.0~rc2-3
ii  libreoffice-script-provider-bsh 1:6.1.0~rc2-3
ii  libreoffice-script-provider-js  1:6.1.0~rc2-3
ii  libreoffice-script-provider-python  1:6.1.0~rc2-3
ii  libreoffice-sdbc-postgresql 1:6.1.0~rc2-3
ii  libreoffice-wiki-publisher  1.2.0+LibO6.1.0~rc2-3

Versions of packages libreoffice suggests:
ii  cups-bsd2.2.8-5
ii  default-jre [java6-runtime] 2:1.10-67
ii  firefox-esr 52.9.0esr-1
ii  ghostscript 9.22~dfsg-2.1
ii  gnupg   2.2.9-1
pn  gpa 
ii  gstreamer1.0-libav  1:1.14.2-dmo1
ii  gstreamer1.0-plugins-bad1:1.14.2-dmo1
ii  gstreamer1.0-plugins-base   1.14.2-dmo1
ii  gstreamer1.0-plugins-good   1.14.2-dmo1
ii  gstreamer1.0-plugins-ugly   1:1.14.2-dmo1
ii  hunspell-en-us [hunspell-dictionary]1:2018.04.16-1
pn  hyphen-hyphenation-patterns 
ii  imagemagick 8:6.9.10.2+dfsg-3
ii  imagemagick-6.q16 [imagemagick] 8:6.9.10.2+dfsg-3
ii  libgl1  1.0.0+git20180308-3
pn  libreoffice-gnome | libreoffice-kde5
pn  libreoffice-grammarcheck
pn  libreoffice-help
pn  libreoffice-l10n
pn  libreoffice-officebean  
ii  libsane 1.0.25-4.1
ii  libxrender1 1:0.9.10-1
pn  myspell-dictionary  
pn  mythes-thesaurus
pn  openclipart2-libreoffice | openclipart-libreoffice  
ii  openjdk-10-jre [java6-runtime

Processed: Re: emacs25: Silent file corruption on file with BOM: BOM gets removed

[Debian Bug Tracking System]

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

> tags 883434 upstream fixed-upstream
Bug #883434 [emacs25] emacs25: Silent file corruption on file with BOM: BOM 
gets removed
Added tag(s) upstream and fixed-upstream.
>
End of message, stopping processing here.

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

Processed: Bug #904598 in libreoffice marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904598 [src:libreoffice] libreoffice: Find/Replace dialogs' options are 
broken in gen vclplug
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms with gen VCLplug
Added tag(s) pending.
Added tag(s) pending.

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

Bug#904598: Bug #904598 in libreoffice marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/3c1aee743e2de32b636ce906145ce588d9f285af


also depend on colibre in -common (closes: #904598, #905408, #905819)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904598

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Niels Thykier]

Lars Wirzenius:
> On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
>> Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
>> is a key package and as such a potential blocker for the new Debian release.
> 
> Key pacakge? I did not know that. What makes cliapp a key package?
> 

I had a look at https://udd.debian.org/cgi-bin/key_packages.yaml.cgi and
it says:


- reason: cmdtest depends python-cliapp
  source: python-cliapp

- reason: xauth build-depends cmdtest
  source: cmdtest

- reason: popcon
  source: xauth

(Where popcon is that one of auth's binaries are installed on 5% or more
 of all machines reporting back to popcon)

> I'll try to get this fixed soon. Sorry about the delay.
> 

Thanks. :)
~Niels

Processed: Bug #904598 in libreoffice marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904598 [src:libreoffice] libreoffice: Find/Replace dialogs' options are 
broken in gen vclplug
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms with gen VCLplug
Ignoring request to alter tags of bug #904598 to the same tags previously set
Ignoring request to alter tags of bug #905408 to the same tags previously set

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

Bug#904598: Bug #904598 in libreoffice marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/3c1aee743e2de32b636ce906145ce588d9f285af


also depend on colibre in -common (closes: #904598, #905408, #905819)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904598

Bug#905945: x2goclient links against libssh_threads library that is not built anymore

[Laurent Bigonville]

Source: x2goclient
Version: 4.1.2.1-1
Severity: serious

Hi,

x2goclient wants to link against libssh_threads library but that library
is now gone.

The (only) exported function has been moved to the main libssh library,
so the fix should be trivial, the build system should stop linking
against it.

Kind regards,

Laurent Bigonville

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

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

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
> is a key package and as such a potential blocker for the new Debian release.

Key pacakge? I did not know that. What makes cliapp a key package?

I'll try to get this fixed soon. Sorry about the delay.



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