Processed: re: nosexcover: Python2 removal in sid/bullseye

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

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



Processed: Liquidsoap update

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 939580 by 944404
Bug #939580 [src:liquidsoap] liquidsoap: FTBFS with new ffmpeg ocaml library
939580 was blocked by: 941907
939580 was not blocking any bugs.
Added blocking bug(s) of 939580: 944404
> thanks
Stopping processing here.

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



Bug#875031: [linguider] Future Qt4 removal from Buster

2019-11-09 Thread Moritz Mühlenhoff
On Fri, Oct 11, 2019 at 11:04:38PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 10:10:41PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: linguider
> > Version: 4.1.1-1
> > Severity: wishlist
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> > 
> > 
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as [announced] in:
> > 
> > [announced] 
> > 
> > 
> > Currently Qt4 has been dead upstream and we are starting to have problems
> > maintaining it, like for example in the [OpenSSL 1.1 support] case.
> > 
> > [OpenSSL 1.1 support] 
> > 
> > 
> > In order to make this move, all packages directly or indirectly depending on
> > the Qt4 libraries have to either get ported to Qt5 or eventually get
> > removed from the Debian repositories.
> > 
> > Therefore, please take the time and:
> > - contact your upstream (if existing) and ask about the state of a Qt5
> > port of your application
> > - if there are no activities regarding porting, investigate whether there 
> > are
> > suitable alternatives for your users
> > - if there is a Qt5 port that is not yet packaged, consider packaging it
> > - if both the Qt4 and the Qt5 versions already coexist in the Debian
> > archives, consider removing the Qt4 version
> 
> Hi,
> There hasn't been any followup on this bug since two years and we're now 
> moving
> forward with the Qt4 removal, are the immediate plans to port linguider to 
> Qt5 or
> should we remove it from the archive?

I've now filed a removal bug.
 
Cheers,
 Moritz



Bug#936214: bleachbit: Python2 removal in sid/bullseye

2019-11-09 Thread Jeremy Bicha
Control: severity -1 important

It looks to me like this bug was elevated to Serious to help with the
pygtk removal from Testing, but bleachbit has already been ported away
from pygtk in Testing. Therefore, I'm lowering the severity of this
bug to prevent its autoremoval at this time.

Obviously, this bug will become RC later in the Bullseye release
cycle, but I don't think it's necessary to happen this month.

Thanks,
Jeremy Bicha



Processed: Re: Bug#936214: bleachbit: Python2 removal in sid/bullseye

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #936214 [src:bleachbit] bleachbit: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'

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



Processed: re: nose2: Python2 removal in sid/bullseye

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

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



Processed: re: python-coverage-test-runner: Python2 removal in sid/bullseye

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 937666 serious
Bug #937666 [src:python-coverage-test-runner] python-coverage-test-runner: 
Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#944409: python-bx ftbfs on all 32bit architectures

2019-11-09 Thread Matthias Klose

Package: src:python-bx
Version: 0.8.5-1
Severity: serious
Tags: sid bullseye

see https://buildd.debian.org/status/package.php?p=python-bx

==
ERROR: bx.interval_index_file_tests.test_interval_index_file
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/.pybuild/cpython3_3.7_bx-python/build/bx/interval_index_file_tests.py", 
line 22, in test_interval_index_file

ix.add( name, start, end, i, max=interval_index_file.MAX )
  File 
"/<>/.pybuild/cpython3_3.7_bx-python/build/bx/interval_index_file.py", 
line 276, in add

self.indexes[name] = Index( max=max )
  File 
"/<>/.pybuild/cpython3_3.7_bx-python/build/bx/interval_index_file.py", 
line 346, in __init__

self.new( min, max )
  File 
"/<>/.pybuild/cpython3_3.7_bx-python/build/bx/interval_index_file.py", 
line 364, in new

self.offsets = offsets_for_max_size( max )
  File 
"/<>/.pybuild/cpython3_3.7_bx-python/build/bx/interval_index_file.py", 
line 136, in offsets_for_max_size
raise Exception( "%d is larger than the maximum possible size (%d)" % ( 
max_size, BIN_OFFSETS_MAX[0] ) )

Exception: 2147483648 is larger than the maximum possible size (2147483647)

--
Ran 132 tests in 9.362s

FAILED (errors=1)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_bx-python/build; python3.7 -m nose -v
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit 
code 13

make: *** [debian/rules:15: build-arch] Error 255



Bug#939571: uploaded a NMU, delayed 15 days

2019-11-09 Thread Gianfranco Costamagna
Hello,
On Tue, 5 Nov 2019 20:02:43 +0100 Georges Khaznadar  
wrote:
> Hello Gianfranco,
> 
> as the bug is (not elegantly) fixed, and as the deadline for autoremoval
> is in 25 days, I uploaded python-pyqtgraph_0.10.0-4.1 as an NMU.
> 
> If you prefer download the good fix before two weeks, do not worry, the
> NMU will silently die.
> 

I rescheduled it to go in *now* :)

thanks for doing it, I admit I lost a lot of time trying to trace it down and I 
failed, so help is appreciated!


> Best regards, Georges.
> 
> -- 
> Georges KHAZNADAR et Jocelyne FOURNIER
> 22 rue des mouettes, 59240 Dunkerque France.
> T??l??phone +33 (0)3 28 29 17 70
> 



Processed: forcibly merging 933642 944377

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 933642 944377
Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py 
processes running after build
Bug #944377 [devscripts] src:devscripts: Rebuild hangs
Severity set to 'serious' from 'important'
Marked as found in versions devscripts/2.19.5, devscripts/2.19.6, and 
devscripts/2.19.4.
Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py 
processes running after build
Marked as found in versions devscripts/2.19.7.
Merged 933642 944377
> thanks
Stopping processing here.

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



Bug#943867: stressant: non-buildd binaries

2019-11-09 Thread peter green

tags 943867 +patch
thanks

Since there was no maintainer response to this bug report, I decided to go 
ahead and prepare a NMU. While testing for said NMU I found that the package's 
clean target did not clean up properly. So I fixed it.

I have uploaded a NMU to delayed/5 with the attached debdiff, please tell me if 
you see an issue with it.
diff -Nru stressant-0.5.0/CHANGELOG stressant-0.5.0+nmu1/CHANGELOG
--- stressant-0.5.0/CHANGELOG   2019-10-27 20:29:43.0 +
+++ stressant-0.5.0+nmu1/CHANGELOG  2019-11-09 07:50:54.0 +
@@ -1,3 +1,11 @@
+stressant (0.5.0+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Re-upload source-only to allow migration to testing (Closes: 943867).
+  * Fix clean target.
+
+ -- Peter Michael Green   Sat, 09 Nov 2019 07:50:54 +
+
 stressant (0.5.0) unstable; urgency=medium
 
   * ship new stressant-meta package
diff -Nru stressant-0.5.0/debian/changelog stressant-0.5.0+nmu1/debian/changelog
--- stressant-0.5.0/debian/changelog2019-10-27 20:29:43.0 +
+++ stressant-0.5.0+nmu1/debian/changelog   2019-11-09 07:50:54.0 
+
@@ -1,3 +1,11 @@
+stressant (0.5.0+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Re-upload source-only to allow migration to testing (Closes: 943867).
+  * Fix clean target.
+
+ -- Peter Michael Green   Sat, 09 Nov 2019 07:50:54 +
+
 stressant (0.5.0) unstable; urgency=medium
 
   * ship new stressant-meta package
diff -Nru stressant-0.5.0/debian/rules stressant-0.5.0+nmu1/debian/rules
--- stressant-0.5.0/debian/rules2019-10-27 20:29:43.0 +
+++ stressant-0.5.0+nmu1/debian/rules   2019-11-09 07:50:54.0 +
@@ -26,3 +26,8 @@
 # builder=html,man only supported in Sphinx 1.6, not yet released:
 # http://www.sphinx-doc.org/en/master/setuptools.html
cd doc ; make html man
+
+override_dh_auto_clean:
+   dh_auto_clean
+   rm -rf doc/_build
+   rm -rf stressant.egg-info
diff -Nru stressant-0.5.0/__version.py stressant-0.5.0+nmu1/__version.py
--- stressant-0.5.0/__version.py2019-10-27 20:29:43.0 +
+++ stressant-0.5.0+nmu1/__version.py   2019-11-09 07:50:54.0 +
@@ -1,4 +1,4 @@
 # coding: utf-8
 # file generated by setuptools_scm
 # don't change, don't track in version control
-version = '0.5.0'
+version = '0.5.0+nmu1'


Processed: re: stressant: non-buildd binaries

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 943867 +patch
Bug #943867 [stressant] stressant: non-buildd binaries
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#925685: marked as done (flightgear: ftbfs with GCC-9)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 Nov 2019 09:23:01 +0100
with message-id <52996d67-8497-3bef-809f-35f7466e2...@debian.org>
and subject line 
has caused the Debian Bug report #925685,
regarding flightgear: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
cd /<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/test_suite && 
/usr/bin/c++  -DHAVE_CONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB 
-DWITH_EVENTINPUT 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/test_suite/run_test_suite_autogen/include
 -I/<>/flightgear-2018.3.2+dfsg/3rdparty/iaxclient/lib 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/<>/flightgear-2018.3.2+dfsg 
-I/<>/flightgear-2018.3.2+dfsg/src 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/src 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/src/Include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/hts_engine_API/include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/flite_hts_engine/include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/cppunit/include 
-I/<>/flightgear-2018.3.2+dfsg/src/FDM/JSBSim -I/<>/flightge
 ar-2018.3.2+dfsg/3rdparty/joystick -isystem /usr/include/x86_64-linux-gnu/qt5 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSvg  -g -O2 
-fdebug-prefix-map=/<>/flightgear-2018.3.2+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall  -D_REENTRANT -DBOOST_BIMAP_DISABLE_SERIALIZATION -g 
-DNDEBUG   -fPIC -std=gnu++11 -o 
CMakeFiles/run_test_suite.dir/fgCompilerOutputter.cxx.o -c 
/<>/flightgear-2018.3.2+dfsg/test_suite/fgCompilerOutputter.cxx
[100%] Building CXX object 
test_suite/CMakeFiles/run_test_suite.dir/fgTestListener.cxx.o
cd /<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/test_suite && 
/usr/bin/c++  -DHAVE_CONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB 
-DWITH_EVENTINPUT 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/test_suite/run_test_suite_autogen/include
 -I/<>/flightgear-2018.3.2+dfsg/3rdparty/iaxclient/lib 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/<>/flightgear-2018.3.2+dfsg 
-I/<>/flightgear-2018.3.2+dfsg/src 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/src 
-I/<>/flightgear-2018.3.2+dfsg/obj-x86_64-linux-gnu/src/Include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/hts_engine_API/include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/flite_hts_engine/include 
-I/<>/flightgear-2018.3.2+dfsg/3rdparty/cppunit/include 

Processed: Re: python-paraview has to be renamed to python3-paraview

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #944324 [src:paraview] python-paraview has to be renamed to python3-paraview
Severity set to 'important' from 'serious'

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



Bug#944324: python-paraview has to be renamed to python3-paraview

2019-11-09 Thread Matthias Klose

Control: severity -1 important

maybe I am wrong with that, the package is called paraview-python at least.



Bug#944392: frr: /usr/share/man/man8/vrrpd.8.gz is already shipped by vrrpd

2019-11-09 Thread David Lamparter
On Sat, Nov 09, 2019 at 03:33:05AM +0100, Andreas Beckmann wrote:
> Package: frr
> Version: 7.2-1
> Severity: serious
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.
[...]
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-3pfMjQ/16-frr_7.2-1_amd64.deb (--unpack):
>trying to overwrite '/usr/share/man/man8/vrrpd.8.gz', which is also in 
> package vrrpd 1.0-2+b2

Hi Andreas,


Thanks for catching this.  vrrpd is one of FRR's "protocol" daemons,
installed to /usr/lib/frr/ (hence the binary isn't colliding), but
obviously the manpage doesn't have this private directory.

I need to go dig through the Debian policy on what it says about this.
I'm guessing we should just rename our manpages to "frr-".  The
binary isn't in PATH either, i.e. you can't run FRR vrrpd by just typing
"vrrpd", so not getting the manpage with "man vrrpd" is consistent.

(It does make sense for vrrpd to be installed in parallel with FRR, in
particular since VRRP support is a recent FRR addition and existing
setups may very well want to stick with a vrrpd+FRR configuration.)

(Cc'ing onto FRR dev list for further comment.  Please keep the debian
bugtracker address in Cc:.  Also opening an issue on FRR github.)

Cheers,


-David



Bug#944380: GDC generates duplicate symbols when using mixins/interfaces

2019-11-09 Thread Matthias Klose

Control: found -1 9.2.1-16
Control: severity -1 important

according to the upstream report, also with 9.2.0.

On 08.11.19 23:18, Matthias Klumpp wrote:

Package: gdc-9
Version: 9.2.1-17
Severity: serious

Hi!
Currently, GDC can't build package like gtk-d because it generates
duplicate non-weak symbols in object files, causing a collision when
linking. This seems to happen when using mixins / interfaces.
For more information and a workaround, please check the upstream bug report.


if there's a workaround, please don't set the severity to serious.



Processed: Re: Bug#944380: GDC generates duplicate symbols when using mixins/interfaces

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> found -1 9.2.1-16
Bug #944380 [gdc-9] GDC generates duplicate symbols when using mixins/interfaces
Bug #942607 [gdc-9] gtk-d FTBFS on armhf, multiple definition errors.
Marked as found in versions gcc-9/9.2.1-16.
Marked as found in versions gcc-9/9.2.1-16.
> severity -1 important
Bug #944380 [gdc-9] GDC generates duplicate symbols when using mixins/interfaces
Bug #942607 [gdc-9] gtk-d FTBFS on armhf, multiple definition errors.
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'

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



Bug#944060: marked as done (exim4-daemon-light: FTBFS (testsuite error) on mipsel)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 19:04:40 +
with message-id 
and subject line Bug#944060: fixed in exim4 4.93~RC1-4
has caused the Debian Bug report #944060,
regarding exim4-daemon-light: FTBFS (testsuite error) on mipsel
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.)


-- 
944060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-daemon-light
Version: 4.93~RC0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

4.93~RC0-1 and later (including 4.93~RC1-2) FTBFS on mipsel, the binary
is built but broken.

/path/to/exim -C /dev/null -be '${if bool{0}{yes}{no}}'
fails with
2019-11-03 17:50:00 failed to malloc 2008002776 bytes of memory: called from 
line 3359 in readconf_main

cu Andreas

PS:
I wish I had seen the  build errors /before/ uploading to unstable but
whenever I checked mipse was at needs-build.
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.93~RC1-4

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated exim4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 19:25:10 +0100
Source: exim4
Architecture: source
Version: 4.93~RC1-4
Distribution: unstable
Urgency: low
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 944060
Changes:
 exim4 (4.93~RC1-4) unstable; urgency=low
 .
   * Add libnet-ssleay-perl dependency to "basic" autopkg test. We do not need
 it yet but will forget for sure to add it when we do.
   * Following upstream defaults do not disable incoming TLS by default - i.e.
 if MAIN_TLS_ENABLE is not set - but use a self-signed certificate.
 (Relevant upstream changes: tls_advertise_hosts defaults to * for TLS
 builds since 4.87_JH/18, on-demand generation of self-signed certificate
 for inbound SMTP since 4.88_JH/05, 4.93_JH/23 TLS enabled build by
 default.)
   * 75_02-Revert-preallocate-store-for-config-which-appears-to.patch: Fix
 mismerge which triggered a test error on mipsel. Closes: #944060
Checksums-Sha1: 
 2baf9338eaf12ea8bdcde4c31e84423d7e2a44a4 2888 exim4_4.93~RC1-4.dsc
 a402447d7da663db2ce5e715e4aa457775223ece 456360 exim4_4.93~RC1-4.debian.tar.xz
Checksums-Sha256: 
 b84a74c95f001d75487c09a64878662324edd2f7cd28c16d0c280abfb553fe82 2888 
exim4_4.93~RC1-4.dsc
 a2e04c32a6e567a4cafad4e5d87f713d65a1d74e0ed824cb7a25cee899e7f64b 456360 
exim4_4.93~RC1-4.debian.tar.xz
Files: 
 5be66af4aab168d77afd0a1d1f90625d 2888 mail standard exim4_4.93~RC1-4.dsc
 b6c62d604b1fda09f9f6ea61e64b4dea 456360 mail standard 
exim4_4.93~RC1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl3HBPIACgkQpU8BhUOC
FISX5Q/8CxZvDn/8uYCEgpRju5U0yi8IxMp1YLg5bnp+ulKnEx3nQiEHMevsl6En
t/SdW8RNwF01FLd6v+BGscnclYjMINYbJE39O3kbtuE+rQpaZ9tdPqpB/0iuCKEG
ui3y6VNugR/iLuCzdRUhHu1j1zjD7UOTBWfQNAtmB2mVGGmTloQI3269Z5yBP5Ud
O97L0ZzI9lYkDpqU5L9+0ooXERQshjjMrAPNKKPjftIuS+bPwkA8ffoakV9wBhiJ
d3kyvqi4/94vxBthimToDv3cTxoY3UVvf9lg2MZjHcGSVQVVhvSyaDRTKRQlVqbf
hkeE48zX4DOyn1fFUW5JKY+dAR6Cvx/Lm/IVjC41CM0Sg9T2VYw/GYKYFLi48asa
Z2VX8imq2E/IJ5OlfGKd57nnzvbPe46bOECX5wHp2V9nzWJ1C6UsEuah/QwZRRZC
2XiXROTHiGK5mBs2guwVaGngUI9p+47pGSoIwlp3x04PFFZO+nSY+pKEj56cLzVn
giXuUrPdnXTNYEWcnTxFXwMiAfizuSE3YJvS05zAhgoB0Rxzuj9NGrHcQYDsWCpz
Axwj9Uckxho9DmUBbbp88VvI+z00o9OaDyx7O0vicpN5etAeA/sSvugaA025nEFl
reLnurZGeZyYpwRjOGk7U5dw0aJ+qa+D7wKMNqJUU0bSlzH8fF8=
=pCmk
-END PGP SIGNATURE End Message ---


Bug#944426: lazarus-src-2.0 fails to upgrade from 2.0.2+dfsg-7 to 2.0.6+dfsg-1: trying to overwrite filefindlaz.lpk

2019-11-09 Thread Paul Gevers
Package: lazarus-src-2.0
Version: 2.0.2+dfsg-7
Severity: serious
Justification: fails to upgrade

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear all,

I just tried to upgrade my system, but it fails due to the new version of
lazarus-src-2.0 in testing.

Unpacking lazarus-src-2.0 (2.0.6+dfsg-1) over (2.0.2+dfsg-7) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-9w9w6M/46-lazarus-src-2.0_2.0.6+dfsg-1_all.deb (--unpack):
 trying to overwrite 
'/usr/lib/lazarus/2.0.6/examples/codepageconverter/filefind/filefindlaz.lpk', 
which is also in package lazarus-ide-2.0 2.0.6+dfsg-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Paul

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

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

lazarus-src-2.0 depends on no packages.

lazarus-src-2.0 recommends no packages.

Versions of packages lazarus-src-2.0 suggests:
iu  lazarus-ide-2.0  2.0.6+dfsg-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3HL5IACgkQnFyZ6wW9
dQqvjwgAlbHYWa/MhL8T9P5W7EQCbbftxQrD/oK4tSO8akfe7voHj9639x+mrB1U
tVC0fihED46pRfTv1rexR8Bs80buXvovcvGVWTyj062qNa9qneWGjBo5CfKg7GGo
SCzaEGxOsVIhOWQraU5L5Tj7xJ6+PA9nWB7jOL3cDCtE7Lr0fJc5omLhDyBjqDUn
h7tZsDMFDAQhg6pF1SbvobqOMD30k5t0XNcnIwTgmWCCBH37aMTdC+ckrJoTqUQp
bcqJHwjoe57i3O6elL8xKSS0fzLqZXQ+b5qwKhkHCH3Ea6lvfew8DIk+jDy6EQyl
0w+qmHd+rGo83Fsmy3ZcGncL/nZDKQ==
=rooA
-END PGP SIGNATURE-



Bug#944397: marked as done (libldm FTBFS: error: G_ADD_PRIVATE [-Werror])

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 11:04:41 +
with message-id 
and subject line Bug#944397: fixed in libldm 0.2.4-3
has caused the Debian Bug report #944397,
regarding libldm FTBFS: error: G_ADD_PRIVATE [-Werror]
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.)


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

libldm fails to build from source in unstable.

Here is the excerpt from reproducible builds amd64/pbuilder:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libldm_0.2.4-2.rbuild.log.gz
| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror -Wshadow -Wextra -Wno-unused-local-typedefs 
-Wno-unused-parameter -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -g -O2 
-ffile-prefix-map=/build/1st/libldm-0.2.4=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ldm.c  -fPIC -DPIC -o .libs/libldm_1_0_la-ldm.o
| ldm.c: In function 'ldm_init':
| ldm.c:293:13: error: G_ADD_PRIVATE [-Werror]
|   293 | o->priv = LDM_GET_PRIVATE(o);
|   | ^~~
| ldm.c: In function 'ldm_disk_group_init':
| ldm.c:430:13: error: G_ADD_PRIVATE [-Werror]
|   430 | o->priv = LDM_DISK_GROUP_GET_PRIVATE(o);
|   | ^~~
| ldm.c: In function 'ldm_volume_init':
| ldm.c:674:13: error: G_ADD_PRIVATE [-Werror]
|   674 | o->priv = LDM_VOLUME_GET_PRIVATE(o);
|   | ^~~
| ldm.c: In function 'ldm_partition_init':
| ldm.c:841:13: error: G_ADD_PRIVATE [-Werror]
|   841 | o->priv = LDM_PARTITION_GET_PRIVATE(o);
|   | ^~~
| ldm.c: In function 'ldm_disk_init':
| ldm.c:1055:13: error: G_ADD_PRIVATE [-Werror]
|  1055 | o->priv = LDM_DISK_GET_PRIVATE(o);
|   | ^~~
| cc1: all warnings being treated as errors
| make[3]: *** [Makefile:581: libldm_1_0_la-ldm.lo] Error 1
| make[3]: Leaving directory '/build/1st/libldm-0.2.4/src'
| make[2]: *** [Makefile:500: all-recursive] Error 1
| make[2]: Leaving directory '/build/1st/libldm-0.2.4'
| make[1]: *** [Makefile:407: all] Error 2
| make[1]: Leaving directory '/build/1st/libldm-0.2.4'
| dh_auto_build: make -j16 returned exit code 2
| make: *** [debian/rules:13: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Also observable on crossqa for arm64 using sbuild:
http://crossqa.debian.net/build/libldm_0.2.4-2_arm64_20191021161651.log

Looks like some glib interface change.

Helmut
--- End Message ---
--- Begin Message ---
Source: libldm
Source-Version: 0.2.4-3

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libldm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Nov 2019 11:37:27 +0100
Source: libldm
Architecture: source
Version: 0.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Closes: 944397
Changes:
 libldm (0.2.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
 .
   [ Hilko Bengen ]
   * Replace existing G_ADD_PRIVATE patch
   * Fix FTBFS by replacing *_GET_PRIVATE macros (Closes: #944397)
Checksums-Sha1:
 247e11452720bf96ac419275ae9fea9b279860a8 2040 libldm_0.2.4-3.dsc
 f9ead861172bb7cb3722281685d9242d5aa7ceda 4524 libldm_0.2.4-3.debian.tar.xz
 e6bdc04c2c1fa06188936ae2c31a4ea94fee67ad 8263 libldm_0.2.4-3_source.buildinfo
Checksums-Sha256:
 f2d215a08fa93e31c3febddbcbe2a0ed8313b5eb945d70259579d67a6ae78d3b 2040 
libldm_0.2.4-3.dsc
 f9dd3358fa1844306393cb520720e69549756de4e8d473417f8339ae7d0891af 4524 
libldm_0.2.4-3.debian.tar.xz
 7127f9cc1da413f39dea57cdfccbc81d1d536e47ad23a1a349d49770f7e2dacf 8263 
libldm_0.2.4-3_source.buildinfo
Files:
 4da2b51727a9add9385b8cc38136221c 2040 libs 

Bug#944199: marked as done (exim4: dsearch in config end up in exim4 panic)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 14:42:39 +
with message-id 
and subject line Bug#944199: fixed in exim4 4.93~RC1-3
has caused the Debian Bug report #944199,
regarding exim4: dsearch in config end up in exim4 panic
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.)


-- 
944199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4
Version: 4.93~RC1-2
Severity: important

Dear Maintainer,

using a virtual domain config as described in the current exim manual
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-some_common_configuration_settings.html#SECTvirtualdomains

renders exim4 unusable.

Config files:
# ls /etc/exim4/virtual
example.com
#

Config snippet:
virtual:
  driver = redirect
  domains = dsearch;/etc/mail/virtual
  data = ${lookup{$local_part}lsearch{/etc/mail/virtual/$domain}}
  no_more

Error (paniclog):
2019-11-05 17:27:01 1iRbGs-X0-9x Taint mismatch, string_vformat: 
dsearch_find 87
2019-11-05 17:27:50 Taint mismatch, string_vformat: dsearch_find 87

Regards
Benedikt Spranger
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.93~RC1-3

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated exim4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:10:27 +0100
Source: exim4
Architecture: source
Version: 4.93~RC1-3
Distribution: unstable
Urgency: low
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 944199
Changes:
 exim4 (4.93~RC1-3) unstable; urgency=low
 .
   * 75_01-Dsearch-Fix-taint-handling-in-lookup.-Bug-2465.patch: Untaint
 dsearch lookup. Closes: #944199
Checksums-Sha1: 
 b0f257b349d05a2cbbd42fc739aed16dbabe2dab 2868 exim4_4.93~RC1-3.dsc
 e7a51278b3b4e55711add1794cfaa8537d644e70 455428 exim4_4.93~RC1-3.debian.tar.xz
Checksums-Sha256: 
 c02579b2c2109b64f072ec2aabf992f5f50736ace64d69d695072b558b40470b 2868 
exim4_4.93~RC1-3.dsc
 3cfb1c7ddc61d1a2f84280e2faa98ee58b2aaf058abff486e5c0afb67cabe68c 455428 
exim4_4.93~RC1-3.debian.tar.xz
Files: 
 54f8db63630ae118996668d6894976b8 2868 mail standard exim4_4.93~RC1-3.dsc
 eebd7d0c571ac332acb3c4d514cd0445 455428 mail standard 
exim4_4.93~RC1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl3GyocACgkQpU8BhUOC
FIRJZA/+OnEH9bNomDiwmekLzkkpADxSAcCeT0A0WTzTQe8WQ4V+QwFQLXAeUYBx
i/U2Zl2nvDiPLsmAeZhFBrMKpO1DmPgz377dSScCv5fw0t0/vxaZsiOQtKXt3RvQ
MwbEqzuq9DtAMaFuuGmTHAMfOTf8ndFwZnOAuc5ynuTQwJ4KF0dtbhRdo6U0DdRA
vqbNM8N1rRX1P9NM8DUQ5aB4FW3VLDz087HPIXoV1Ki9bij4eqvyX3rH6Q/GGVF/
a4u9FgUn/h/e76zmumdpeSUx++pSJf6igwQGI6agpZcFAL4MusDX6JVN0nvmmfS9
AVfFa6odOFlhE0WZwwufO0LDsKeE3xXMsQ+KQjd4eIvU+FEuyQKBCCoHWY2NjSB8
l5mXOvQolyGvwgw2FZIJI5Ah4wdAA8bVDzF8rGNT5ON5sDEixltfnFcKPPyRc6Xc
gpDwMkrRbMRsGhCz04DiyzknJSsxXfgj4jHxp2TQNdZh+3Hiy0M4+hmB3i0GdquB
stECtKeZYADEwuG0ZsjAgVmopGd7mSZMeqLMNc/HsWO46t8PZOos29HqS9W5MAIL
DuPbyzGtT4y8FcMoi6Ew2PFx5TLNqoL38goGJfAukEuZnlp5k2qWYEUPF7acT7Jb
0hrQbai5VqWiJZSx0xyXB6wSg7P3mbOZcZeFs2NrmHHcez8ZS58=
=APyL
-END PGP SIGNATURE End Message ---


Bug#944249: gnuplot-mode does not work with emacs26

2019-11-09 Thread Agustin Martin
El jue., 7 nov. 2019 a las 2:57, Nicholas D Steeves
() escribió:
>
> Hi Olaf and Dima,
>
> Dima, if it's alright with you can I please take care of this bug?
> I've head I need an RC Bug NMU process for the "demonstrates skills
> and knowledge of process" section of my eventual DD application.

Sorry, I missed above part of your mesage. Just read the part below

> If Dima give the go-ahead I'll investigate if this would be approved
> for a stable update.  It seems like it would be, because RC bugs like
> this aren't supposed to be solved using backports.

and thought you were someone helping the ftpmaster team and knowing
about their procedures.

Since I already sent some patches, they can be a starting point for
your work. Feel free to modify them at your convenience.

Regards,

-- 
Agustin



Bug#943867: stressant: non-buildd binaries

2019-11-09 Thread Antoine Beaupré
On 2019-11-09 08:05:32, peter green wrote:
> tags 943867 +patch
> thanks
>
> Since there was no maintainer response to this bug report, I decided to go 
> ahead and prepare a NMU. While testing for said NMU I found that the 
> package's clean target did not clean up properly. So I fixed it.

thanks, feel free to upload sooner.

merged in git.

a.
-- 
La destruction de la société totalitaire marchande n'est pas une affaire
d'opinion. Elle est une nécessité absolue dans un monde que l'on sait
condamné. Puisque le pouvoir est partout, c'est partout et tout le temps
qu'il faut le combattre. - Jean-François Brient, de la servitude moderne



Bug#939987: marked as done (postgresql-hll is broken with glibc 2.29-1)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 19:00:29 +
with message-id 
and subject line Bug#939987: fixed in postgresql-hll 2.13-1
has caused the Debian Bug report #939987,
regarding postgresql-hll is broken with glibc 2.29-1
to be marked as done.

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

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


-- 
939987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-hll
Severity: serious
Forwarded: https://github.com/citusdata/postgresql-hll/issues/67

Conform the discussion on IRC (below) I am going to remove
postgresql-hll from bullseye as the glibc transition has started. This
bug is to keep it out of bullseye until the package is fixed.

Paul

2019-09-04 on #debian-release

[20:45:52]  Myon: how does
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/postgresql-hll/2871470/log.gz
look to you?
[20:46:08]  it's the failure in unstable with glibc from
experimental
[20:46:35]  would that remain an issue if we start the glibc
transition?
[20:47:46]  (I don't the failure will go away with a retry will it?)
[20:59:43]  elbrus: oh so that landed in Debian now. Ubuntu has
already had that problem for a while. Unfortunately
https://github.com/citusdata/postgresql-hll/issues/67 is dormant
[21:00:13]  Myon: still in experimental
[21:00:38]  nod
[21:01:03]  but a transition slot was requested
[21:01:05]  so experimental "migrations" are being tested like
testing now?
[21:01:22]  more or less
[21:01:24]  yes
[21:01:25]  nice
[21:01:38]  still not cronned due to "issues"
[21:02:11]  I don't have a plan for that problem - it's a niche
package, so it's not really much of an issue
[21:02:15] 
https://lists.debian.org/debian-devel/2019/09/msg00014.html
[21:02:36]  can you disable the test then?
[21:03:26]  I'd rather prefer if you could put the package on
ignore, or remove it from testing
[21:03:37]  because that looks like real breakage, not just in the
test
[21:04:00]  but I haven't even glanced at the problem
[21:05:27]  a, ok, I'll remove it when the transition starts than



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: postgresql-hll
Source-Version: 2.13-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated postgresql-hll package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Nov 2019 11:28:22 +0100
Source: postgresql-hll
Binary: postgresql-12-hll postgresql-12-hll-dbgsym
Architecture: source amd64
Version: 2.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Description:
 postgresql-12-hll - HyperLogLog extension for PostgreSQL
Closes: 939987
Changes:
 postgresql-hll (2.13-1) unstable; urgency=medium
 .
   * New upstream version.
   * tests: Add hll to shared_preload_libraries and set extra_float_digit=0.
   * tests: Paper over glibc2.29 changes with different log() precision.
 (Closes: #939987)
Checksums-Sha1:
 c92fc86979f0694721d07e1571746c2d67b04ebc 2194 postgresql-hll_2.13-1.dsc
 9c8ed700aa6f52c5bfb6b8e9ecdbdf5c291e37d6 2753827 
postgresql-hll_2.13.orig.tar.gz
 86c3546fe1e74c04e523816c6d2fe4b8f0ce110d 4384 
postgresql-hll_2.13-1.debian.tar.xz
 dacb85514a99a223431dd2779901c07c4b391f6b 94872 
postgresql-12-hll-dbgsym_2.13-1_amd64.deb
 8410e62bb445de869fb9af1ed85efb8317d39c08 82148 
postgresql-12-hll_2.13-1_amd64.deb
 03e1b7671be417b1330c39882dc7e2b6bf566c93 8542 
postgresql-hll_2.13-1_amd64.buildinfo
Checksums-Sha256:
 2fc9722d25c28180e26566569edd8665ea0318e73dfc2cf7a8d4e29a91485e3e 2194 
postgresql-hll_2.13-1.dsc
 900df14063e35e07aa15f93ba99886ae3ceafdbcdbc4cc0983b1c91f10e764ab 2753827 
postgresql-hll_2.13.orig.tar.gz
 d39bc1eb051b247a211c16a8826ddc3e3a5ac225bea9d6f8f1d113b2011fca0b 4384 
postgresql-hll_2.13-1.debian.tar.xz
 b448c0e752cfaa1b4e9efaa2a633d02c7f05bed682e75e3dbd0f38e1a58e42f4 94872 
postgresql-12-hll-dbgsym_2.13-1_amd64.deb
 

Processed: your mail

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 944243 important
Bug #944243 [logrotate] logrotate fails with "Permission denied" on LXC guest
Severity set to 'important' from 'grave'
> tags 944243 moreinfo buster
Bug #944243 [logrotate] logrotate fails with "Permission denied" on LXC guest
Added tag(s) buster and moreinfo.
>
End of message, stopping processing here.

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



Bug#944425: sat-xmpp-primitivus depends on python-urwid-satext which has been dropped

2019-11-09 Thread Paul Gevers
Package: sat-xmpp-primitivus
Version: 0.7.0a4-1
Severity: serious
Justification: not installable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package sat-xmpp-primitivus depends on python-urwid-satext. However, the
maintainer of src:urwid-satext, the source package that used to build that
binary package has removed python-urwid-satext due to process of removing
Python 2 from Debian. Please update your package to handle the new situation.

Paul

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

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

Versions of packages sat-xmpp-primitivus depends on:
ii  python   2.7.17-1
pn  python-dbus  
ii  python-gi3.34.0-1
pn  python-urwid 
pn  python-urwid-satext  
pn  sat-xmpp-core

Versions of packages sat-xmpp-primitivus recommends:
pn  python-xlib  

sat-xmpp-primitivus suggests no packages.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3HJtoACgkQnFyZ6wW9
dQqiFggAgAptBalFmJB67ZC0d1+P08wnSBN/c8ETuEwDWsoQeqRomdilSsQXm2ip
K59xvul6H20ZpIhmWvxCVZanZpr5revf2Qe4UquMcQRIDBIQdvLsKw/f/SdQzdrm
+GkUqP3z9jSxjdbQukVY0GW4Uv0LY9GdxN/RezAlKIwHOp/VLRyLkAErZAiiNKUt
qvwztx/jvKy5ARrPbW1LJLaM74cQ8URdThRRvC3ye+KmtzUFlJqUn6ScsmR9Yj8F
CzTM4OVReX6j1maUpLKQMBVq0Ab1ftMQhhI2LL3YdZENvEy28+opG927yvWJH9Ti
AAg8A03JS5OPgobe+GPYlaqGU0bzEw==
=ZCI0
-END PGP SIGNATURE-



Bug#896358: marked as done (python3-flask-rdf: flask_rdf fails to import)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:45 +
with message-id 
and subject line Bug#896358: fixed in python-flask-rdf 0.2.1-1+deb10u1
has caused the Debian Bug report #896358,
regarding python3-flask-rdf: flask_rdf 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.)


-- 
896358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-rdf
Version: 0.2.0-1.1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-flask-rdf importing the module flask_rdf
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_rdf/__init__.py", line 1, in 

from . import bottle
  File "/usr/lib/python3/dist-packages/flask_rdf/bottle.py", line 2, in 
from .common_decorators import ViewDecorator
  File "/usr/lib/python3/dist-packages/flask_rdf/common_decorators.py", line 3, 
in 
from rdflib.graph import Graph
ModuleNotFoundError: No module named 'rdflib'

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: python-flask-rdf
Source-Version: 0.2.1-1+deb10u1

We believe that the bug you reported is fixed in the latest version of
python-flask-rdf, 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.
Andreas Beckmann  (supplier of updated python-flask-rdf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Nov 2019 01:56:51 +0100
Source: python-flask-rdf
Architecture: source
Version: 0.2.1-1+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Andreas Beckmann 
Closes: 896358 896385
Changes:
 python-flask-rdf (0.2.1-1+deb10u1) buster; urgency=medium
 .
   * Non-maintainer upload.
   * Add Depends on python{3,}-rdflib.  (Closes: #896358, #896385)
Checksums-Sha1:
 90ed238d305943586d3c958c869a2546afe15c9d 2176 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 f60ac3f31d9125f8096b4bf95902fd77e6192226 2644 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 0b591a8c1f01484087aeda1dd91c5528486f55af 6530 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo
Checksums-Sha256:
 4f65f11599e280a63272185b674f360671d3a988d7f25af63a710f091711691c 2176 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 be30cabf6d489163fb9293b44cc3ef39d875f9297570bad1fc36474f55e48c05 2644 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 87e1ad5fc86a46f5e7c6de14c569f59eed4742b715b97068aeba9a952bb968fe 6530 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo
Files:
 21bb2f95fb927fed38b3ebd2a33828da 2176 python optional 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 99bc5260deeaa7e12013b44194336af0 2644 python optional 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 b0f9fa0576d7fbb4dbd40582bed3544c 6530 python optional 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl3GEhkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOFXEACIoEIotuDCLYJpVYBqutkK3dFoQibhQAZc
Q6Ciz6VdphIJRHfXKF/I8nVvo2nke2EhVD00p8EasRqR3wEcpRXztimfnMeMfEZW
lJvJgEpCXFKzs45UfWCbhvMSjlIUpM310C+XJowvQHliwj2dtEGol26T92J8ryoU
+hUsUTK+JmnL3/pdEEVP3SJ4xNv7XVfs9edxiw3Fjynzxl3Zs5/mD0SF9zFBpTcJ
KXvfNFBqdbc/1uZeAujuN/oHt2dJ6tUPmVUCqfklTVRci9NmZkz33KF8g1NKQiq4
1W2H4bb36reqUYs2BPNf5XPb4Cq9r9in1N23namRLNbV8EaXP5xVWuvgB/GAZU9a
vCvlOC+Y6XHSFg4xF4jQ5tD+HTUAAo2PbV23Wxuld6S0Tj0Lf/v4hGoKoGooAxS6
gxjTa/Glv7XNWfjEkSAI44x+kwI4DaC0xb4UeXamIlmr+IFVdhboMmWMDC9cx7gK
aP7nbWDTFxBlvxIPI2ZNXfujN2W/hVGz6xtejnQhBAw3L3hXrQEHPLDX3rm2saUK
gSXNC79yetGbmlW7ycNCH+MUKYeWhtio5URxHJBKCfHAZi28L71cOZWOg3EmZSrY

Bug#944244: marked as done ([standardskriver] Fails to detect local system's IP addresses)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:51 +
with message-id 
and subject line Bug#944244: fixed in standardskriver 0.0.3-2+deb10u1
has caused the Debian Bug report #944244,
regarding [standardskriver] Fails to detect local system's IP addresses
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.)


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

Package: standardskriver
Severity: serious
Version: 0.0.3-2

I just discovered, that standardskriver in buster/testing/unstable  
fails to detect the local system's IP addresses due to stdout changes  
in ifconfig. Furthermore, utilizing ifconfig form another application  
is not a good idea these days anymore, it should be replace by  
utilizing the "ip" command.


I will prepare updated packages for this within the next days.

Mike
--

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

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



pgpGc56sPaP0x.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: standardskriver
Source-Version: 0.0.3-2+deb10u1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated standardskriver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Nov 2019 19:00:58 +0100
Source: standardskriver
Architecture: source
Version: 0.0.3-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Closes: 944244
Changes:
 standardskriver (0.0.3-2+deb10u1) buster; urgency=medium
 .
   * debian/patches:
 + Add 0001_RawConfigParser-use-new-method-read_file-instead-of-.patch.
   Fix deprecation warning by config.RawConfigParser.
 + Add 0002_standardskriver-Use-ip-command-rather-than-deprecate.patch.
   Use external "ip" command rather than deprecated "ifconfig" command.
   This fixes (essential) local system's IPv4 detection. (Closes: #944244).
Checksums-Sha1:
 0a9b212fe21fd300da9961bb0f57b50650a36c5c 2090 
standardskriver_0.0.3-2+deb10u1.dsc
 2853804e6c9e54233a321459c68857662346e37f 3460 
standardskriver_0.0.3-2+deb10u1.debian.tar.xz
 5f341a7b55da4534ce05b1f154d78f69260c0b6d 6389 
standardskriver_0.0.3-2+deb10u1_source.buildinfo
Checksums-Sha256:
 eac84a2751aa1347f32b58e2fb1faa8be77fef13625e3b13cc28c2f6f0ea84a5 2090 
standardskriver_0.0.3-2+deb10u1.dsc
 f4addaea7bcda681b9ed613b91a07f32426dc45eaebc8f14e3aa5afd3a576d03 3460 
standardskriver_0.0.3-2+deb10u1.debian.tar.xz
 91358bedeb19d4d38465a5a7a64a698f9b43c9f2333ecee31dab9e2aec5b0ca6 6389 
standardskriver_0.0.3-2+deb10u1_source.buildinfo
Files:
 fa53779032fbbeb38647295072127713 2090 admin optional 
standardskriver_0.0.3-2+deb10u1.dsc
 844416d59060f761be006a775e810951 3460 admin optional 
standardskriver_0.0.3-2+deb10u1.debian.tar.xz
 5f542827796167493e4435ac8fa48db8 6389 admin optional 
standardskriver_0.0.3-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3DC6EVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxRggQAJ+qDgAy8JqLOIZxM3uzm570QO51
qoDHIUXN+QsM5R9JycSTc9uKi6HA3GY8TAWlSecKz6h8aOUF+Ncd5vdBZs50m/Va
dFqYn3zdIQp1O5Bb2sZ4H/8DbihOwQvt0e4JF6sZBM/w0abFBBSeL58qxpBLnQzP
kUAy1LA+/PQ6mhYq+jBGlkb02fyetwvgdt6hpdml43NmC6OkifKLE/lP+Vwkkkmy
eo/7VKObg4G96yHpu3+rJqBfN06VhhBFvpLRL7iNaNBn/8872/ruqLVdcys0GEiu
dlppzRXY4pE/gKY6p5ZolV90IwXbTeR9rTHhTvomf9Ui5YEPD52REoLauoyPP5A2
JzHyH1MpFYAmAK1K9TDMCH1VsGX6TLC0WwlRFgto+gMa4BNzud0Vagp3XT89JTkH
G3pFRL4jCFjc4wnedq1fz6kIWZ0ohHmZqQIAlwHwkeoz6YwD3KX+WoGKioacORTY
mAubdfoPJgMJeYvJASIPjH05EPFpKYi6VbDMSgsr4Q5qh6iUPDR+S1hxxJhbFdVl
+Sx1KaZn6Lw8JXr0Trwnkag2THiuInnqCR7VJRiFD/CU8zrrjFVihOwV4KoSid0k
TYejsnM7/m9d6sOo+qasMsh87/n0s26Ffe9Bsj4pdXPo9G+3ONBsZN5yOkjrBwMp

Bug#896385: marked as done (python-flask-rdf: flask_rdf fails to import)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:45 +
with message-id 
and subject line Bug#896385: fixed in python-flask-rdf 0.2.1-1+deb10u1
has caused the Debian Bug report #896385,
regarding python-flask-rdf: flask_rdf 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.)


-- 
896385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-flask-rdf
Version: 0.2.0-1.1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-flask-rdf importing the module flask_rdf
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/flask_rdf/__init__.py", line 1, in 

from . import bottle
  File "/usr/lib/python2.7/dist-packages/flask_rdf/bottle.py", line 2, in 

from .common_decorators import ViewDecorator
  File "/usr/lib/python2.7/dist-packages/flask_rdf/common_decorators.py", line 
3, in 
from rdflib.graph import Graph
ImportError: No module named rdflib.graph

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: python-flask-rdf
Source-Version: 0.2.1-1+deb10u1

We believe that the bug you reported is fixed in the latest version of
python-flask-rdf, 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.
Andreas Beckmann  (supplier of updated python-flask-rdf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Nov 2019 01:56:51 +0100
Source: python-flask-rdf
Architecture: source
Version: 0.2.1-1+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Andreas Beckmann 
Closes: 896358 896385
Changes:
 python-flask-rdf (0.2.1-1+deb10u1) buster; urgency=medium
 .
   * Non-maintainer upload.
   * Add Depends on python{3,}-rdflib.  (Closes: #896358, #896385)
Checksums-Sha1:
 90ed238d305943586d3c958c869a2546afe15c9d 2176 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 f60ac3f31d9125f8096b4bf95902fd77e6192226 2644 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 0b591a8c1f01484087aeda1dd91c5528486f55af 6530 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo
Checksums-Sha256:
 4f65f11599e280a63272185b674f360671d3a988d7f25af63a710f091711691c 2176 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 be30cabf6d489163fb9293b44cc3ef39d875f9297570bad1fc36474f55e48c05 2644 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 87e1ad5fc86a46f5e7c6de14c569f59eed4742b715b97068aeba9a952bb968fe 6530 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo
Files:
 21bb2f95fb927fed38b3ebd2a33828da 2176 python optional 
python-flask-rdf_0.2.1-1+deb10u1.dsc
 99bc5260deeaa7e12013b44194336af0 2644 python optional 
python-flask-rdf_0.2.1-1+deb10u1.debian.tar.xz
 b0f9fa0576d7fbb4dbd40582bed3544c 6530 python optional 
python-flask-rdf_0.2.1-1+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl3GEhkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOFXEACIoEIotuDCLYJpVYBqutkK3dFoQibhQAZc
Q6Ciz6VdphIJRHfXKF/I8nVvo2nke2EhVD00p8EasRqR3wEcpRXztimfnMeMfEZW
lJvJgEpCXFKzs45UfWCbhvMSjlIUpM310C+XJowvQHliwj2dtEGol26T92J8ryoU
+hUsUTK+JmnL3/pdEEVP3SJ4xNv7XVfs9edxiw3Fjynzxl3Zs5/mD0SF9zFBpTcJ
KXvfNFBqdbc/1uZeAujuN/oHt2dJ6tUPmVUCqfklTVRci9NmZkz33KF8g1NKQiq4
1W2H4bb36reqUYs2BPNf5XPb4Cq9r9in1N23namRLNbV8EaXP5xVWuvgB/GAZU9a
vCvlOC+Y6XHSFg4xF4jQ5tD+HTUAAo2PbV23Wxuld6S0Tj0Lf/v4hGoKoGooAxS6
gxjTa/Glv7XNWfjEkSAI44x+kwI4DaC0xb4UeXamIlmr+IFVdhboMmWMDC9cx7gK
aP7nbWDTFxBlvxIPI2ZNXfujN2W/hVGz6xtejnQhBAw3L3hXrQEHPLDX3rm2saUK
gSXNC79yetGbmlW7ycNCH+MUKYeWhtio5URxHJBKCfHAZi28L71cOZWOg3EmZSrY

Bug#939819: marked as done (mariadb-10.3: Replication hangs with "preparing" and never starts)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:14 +
with message-id 
and subject line Bug#939819: fixed in mariadb-10.3 1:10.3.18-0+deb10u1
has caused the Debian Bug report #939819,
regarding mariadb-10.3: Replication hangs with "preparing" and never starts
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.)


-- 
939819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.3
Source-Version: 1:10.3.17-0+deb10u1
Severity: serious
Forwarded: https://jira.mariadb.org/browse/MDEV-20247

Hi!

It seems like there's a serious regression in the latest stable update,
fixed already in upstream in 10.3.18, where replication malfunctions.
Please see the upstream report for more details.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: mariadb-10.3
Source-Version: 1:10.3.18-0+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.3 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: Mon, 16 Sep 2019 19:30:57 +0300
Source: mariadb-10.3
Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 
libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 
mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server 
mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb 
mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga 
mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.18-0+deb10u1
Distribution: buster
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadb-dev - MariaDB database development files
 libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
 libmariadb3 - MariaDB database client library
 libmariadbclient-dev - MariaDB database development files (transitional 
package)
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd19 - MariaDB embedded database, shared library
 mariadb-backup - Backup tool for MariaDB server
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.3 - MariaDB database client binaries
 mariadb-client-core-10.3 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.3 - MariaDB database server binaries
 mariadb-server-core-10.3 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 939819
Changes:
 mariadb-10.3 (1:10.3.18-0+deb10u1) buster; urgency=high
 .
   * New upstream version 10.3.18. Fixes regression introduced in 10.3.17
 (MDEV-20247: Replication hangs with "preparing" and never starts)
 (Closes: #939819)
Checksums-Sha1:
 0b9e87c95107615b217a792472dec0358a98266f 4812 
mariadb-10.3_10.3.18-0+deb10u1.dsc
 922a317edd6f44baacc49831ca278e7a9878a363 71950543 
mariadb-10.3_10.3.18.orig.tar.gz
 0c3a6922a528c6353dec7d99b2a2244c13eb6a25 195 
mariadb-10.3_10.3.18.orig.tar.gz.asc
 

Bug#942831: marked as done (CVE-2019-18217)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:22 +
with message-id 
and subject line Bug#942831: fixed in proftpd-dfsg 1.3.6-4+deb10u2
has caused the Debian Bug report #942831,
regarding CVE-2019-18217
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.)


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

This was assigned CVE-2019-18217:
https://github.com/proftpd/proftpd/commit/13fe9462787b9a551152162f46f1641d65fe4df4
https://github.com/proftpd/proftpd/issues/846

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: proftpd-dfsg
Source-Version: 1.3.6-4+deb10u2

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

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated proftpd-dfsg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Oct 2019 16:22:38 +0200
Source: proftpd-dfsg
Binary: proftpd-basic proftpd-basic-dbgsym proftpd-dev proftpd-doc 
proftpd-mod-geoip proftpd-mod-geoip-dbgsym proftpd-mod-ldap 
proftpd-mod-ldap-dbgsym proftpd-mod-mysql proftpd-mod-mysql-dbgsym 
proftpd-mod-odbc proftpd-mod-odbc-dbgsym proftpd-mod-pgsql 
proftpd-mod-pgsql-dbgsym proftpd-mod-snmp proftpd-mod-snmp-dbgsym 
proftpd-mod-sqlite proftpd-mod-sqlite-dbgsym
Architecture: source amd64 all
Version: 1.3.6-4+deb10u2
Distribution: buster-security
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Hilmar Preusse 
Description:
 proftpd-basic - Versatile, virtual-hosting FTP daemon - binaries
 proftpd-dev - Versatile, virtual-hosting FTP daemon - development files
 proftpd-doc - Versatile, virtual-hosting FTP daemon - documentation
 proftpd-mod-geoip - Versatile, virtual-hosting FTP daemon - GeoIP module
 proftpd-mod-ldap - Versatile, virtual-hosting FTP daemon - LDAP module
 proftpd-mod-mysql - Versatile, virtual-hosting FTP daemon - MySQL module
 proftpd-mod-odbc - Versatile, virtual-hosting FTP daemon - ODBC module
 proftpd-mod-pgsql - Versatile, virtual-hosting FTP daemon - PostgreSQL module
 proftpd-mod-snmp - Versatile, virtual-hosting FTP daemon - SNMP module
 proftpd-mod-sqlite - Versatile, virtual-hosting FTP daemon - SQLite3 module
Closes: 942831
Changes:
 proftpd-dfsg (1.3.6-4+deb10u2) buster-security; urgency=medium
 .
   * Add patch from upstream to address CVE-2019-18217.
 (Closes: #942831)
Checksums-Sha1:
 ffee4e24819a5c4798a74cf442f9b605e2a512ca 2839 proftpd-dfsg_1.3.6-4+deb10u2.dsc
 f7de2cc82c9684f71044f4fa9db88066386f16b7 78796 
proftpd-dfsg_1.3.6-4+deb10u2.debian.tar.xz
 88cbe5a5a6bd1acd2a7b745cdde8438224c62c64 3128256 
proftpd-basic-dbgsym_1.3.6-4+deb10u2_amd64.deb
 d2170e15d92df38e06495df494fbe35d14d445c3 2650948 
proftpd-basic_1.3.6-4+deb10u2_amd64.deb
 3693c2bfc9a3f29bfd65626c97e1bff2e934b55c 2661716 
proftpd-dev_1.3.6-4+deb10u2_amd64.deb
 646417a19e22996753721bddd3970f257ab5a01c 13019 
proftpd-dfsg_1.3.6-4+deb10u2_amd64.buildinfo
 6f929d0463a389cda9bfd0f244410a9dfa6a22f4 1695852 
proftpd-doc_1.3.6-4+deb10u2_all.deb
 9251a4877316540471c49ca32a41baf5b9a51f1e 27804 
proftpd-mod-geoip-dbgsym_1.3.6-4+deb10u2_amd64.deb
 05ce80b023e8f90f2f42610e996293d7f1f0ff9d 499432 
proftpd-mod-geoip_1.3.6-4+deb10u2_amd64.deb
 0f086c15f6ab23961b824095dbbda0f29ea8d494 45892 
proftpd-mod-ldap-dbgsym_1.3.6-4+deb10u2_amd64.deb
 433cfbf810bd2abd6fdd04dd81b882b18edb9216 506472 
proftpd-mod-ldap_1.3.6-4+deb10u2_amd64.deb
 6513d728cc943d88026dbf22f9456b256ec98366 34464 
proftpd-mod-mysql-dbgsym_1.3.6-4+deb10u2_amd64.deb
 0499d9f51ca76776029abdb68ce86a39fb002851 498036 
proftpd-mod-mysql_1.3.6-4+deb10u2_amd64.deb
 e97927a176cb42732003ff159374b1176c92e56b 27092 
proftpd-mod-odbc-dbgsym_1.3.6-4+deb10u2_amd64.deb
 b0c9636b5f3368585a73f489bb7aec9cd79194e1 499492 
proftpd-mod-odbc_1.3.6-4+deb10u2_amd64.deb
 e3a2915b5c145ccce7dac919b6512f983232a0bd 26012 
proftpd-mod-pgsql-dbgsym_1.3.6-4+deb10u2_amd64.deb
 51e97614e7a8f339e0442abc46b582c2aa9552e7 

Bug#941018: marked as done (libglib2.0-0: libdbus clients fail to authenticate with private GDBusServer)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:04 +
with message-id 
and subject line Bug#941018: fixed in glib2.0 2.58.3-2+deb10u2
has caused the Debian Bug report #941018,
regarding libglib2.0-0: libdbus clients fail to authenticate with private 
GDBusServer
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.)


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

After upgrading from 1.5.19-4 to 1.5.21-1 all may qt5 ibus stop working with 
ibus (for example anki, kate, konsole, ...). If one switches to say chinese, 
nothing happens , the default keyboard remains to input method.

Switching input method in chromium, for example, works.

Downgrading back to the version in testing (which is 1.5.19-4+b1) fixes the 
issue.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.58.3-2+deb10u2

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Nov 2019 08:29:15 +
Source: glib2.0
Architecture: source
Version: 2.58.3-2+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 941018
Changes:
 glib2.0 (2.58.3-2+deb10u2) buster; urgency=medium
 .
   * Team upload
   * d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
 d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
 Ensure libdbus clients can authenticate with a GDBusServer like the
 one in ibus, backported from upstream 2.62.x branch (Closes: #941018)
   * d/p/Add-a-test-for-GDBusServer-authentication.patch,
 d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch,
 d/p/gdbus-server-auth-test-Include-gcredentialsprivate.h.patch:
 Backport regression test for #941018
   * Build-depend on libdbus-1-dev for better test coverage
   * d/control.in: Set branch to debian/buster in Vcs-Git
Checksums-Sha1:
 67223876134dfff9c56a1cb899472f348d57fb26 3466 glib2.0_2.58.3-2+deb10u2.dsc
 227a1925e7e4ccbc59a1651d522f32edffa0f688 93604 
glib2.0_2.58.3-2+deb10u2.debian.tar.xz
 386dbde513fc1bbd69d7453e56d7d6f72f039348 8280 
glib2.0_2.58.3-2+deb10u2_source.buildinfo
Checksums-Sha256:
 585667486fca2f2a32c04670e1008c5e0ff0cd96024c8618a3e78ee546d85a12 3466 
glib2.0_2.58.3-2+deb10u2.dsc
 c4c01644ec784f6b138441d2f8efbfe606d3a3154109d517bf6d8e89e150c57f 93604 
glib2.0_2.58.3-2+deb10u2.debian.tar.xz
 4ad27e8c435a4b7b7ec01be16c49ec277d9011b9060eea6a1f3f3c3fec851a64 8280 
glib2.0_2.58.3-2+deb10u2_source.buildinfo
Files:
 a660838c985e2eb23c2d26edff709b15 3466 libs optional 
glib2.0_2.58.3-2+deb10u2.dsc
 cdc77b1b87bf26a9113eccd5197c76a3 93604 libs optional 
glib2.0_2.58.3-2+deb10u2.debian.tar.xz
 678c1a794258634d95c8e4c824af6522 8280 libs optional 
glib2.0_2.58.3-2+deb10u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl3GoukQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMTxldEACU4xlNAYw7F9th6F2MLMeHCrJjnVLcgSjA
f/00v9+9cRT4Izp79b2339/M0dOmSgYCrK6K5WFZTlZuExJMj7r6KQECL2z3be8R
Fxq87Dbw+9bBvyNslKr/uPs1JUykBtCmIVgUBRB6ZhQGOoWpGYA86Tq1Uh5LQFuO
Qah5kTwoc32AOiH48YXkn+Jx6Yn1dYkgfXjWo15hGxJu6aKZuicnVZYb4ri4oUcN
ETSkXdSPnOlq4/QmWo4cVzlVenZw9Lwr5aOD61UujY6aFg6Yj+jl+AeX79uhaJgw
fmzIg5DsQbyfot3EJlzIy+BlabuF5Ey+t8m5s5NCwM7YqDbTuW7DE+PIcP5u+az1
EBa11AYK9lfrhrf0KapmFgGpif/gresjOlue0z4qDUGW5AiR92Tzn2m78uH0Fo6g
LJ3vbo58wIPl7F27tXKJjkDE1U2pyFcQd1MEi55Kg3jUqeoFlsMXPpAX967jl8iO
Jz14ZzEuSK0RQpbC4C445G5+7R/8b+FQBfyBlFJYaWkCj+M8oHX7J7oNmxVrdMiA
d9672dcw4oFZPPZanpJdh7h4anunl489sYatUULat7jU/5Dp/wGpZ832E7NGmdwe
qJzI/xAqEFiJQQV4VsgcxIOflWEsC+ZdLn31Vb+mt8Zp+wJEzhqvxWZLzzZfxUE/
29MnEuQyQw==
=7gUf
-END PGP SIGNATURE End Message ---


Bug#934043: marked as done (segfaults with use-after-free when using KrbServiceName Any)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 20:35:04 +
with message-id 
and subject line Bug#934043: fixed in libapache-mod-auth-kerb 5.4-2.4~deb10u1
has caused the Debian Bug report #934043,
regarding segfaults with use-after-free when using KrbServiceName Any
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.)


-- 
934043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-auth-kerb
Version: 5.4-2.3
Severity: grave
Tags: patch upstream

Hi,

After upgrading to buster, mod_auth_kerb keeps on crashing Apache (thus the
grave severity), after printing

  double free or corruption (out)

This is indeed a use-after-free; verify_krb5_user gets in a keytab as a
parameter, and chooses to deallocate it even though the parent expects to keep
using it. I don't know why this didn't trigger as often in stretch,
although we've certainly seen mod_auth_kerb segfaults there as well
(especially with outdated keytabs).

The patch is trivial and can be found in upstream's bug tracker; just don't
deallocate the keytab in verify_krb5_user():

  https://sourceforge.net/p/modauthkerb/bugs/61/

This is not a leak, since the parent closes it inself, in all paths. I've 
verified
that it applies in Debian (just some changed line numbers) and fixes the issue.

Please consider for a buster point release, in addition to unstable.
It makes mod_auth_kerb borderline unusable.

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

Kernel: Linux 5.1.11 (SMP w/40 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libapache2-mod-auth-kerb depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  krb5-config 2.6
ii  libc6   2.28-10
pn  libcomerr2  
ii  libgssapi-krb5-21.17-3
ii  libk5crypto31.17-3
ii  libkrb5-3   1.17-3

libapache2-mod-auth-kerb recommends no packages.

libapache2-mod-auth-kerb suggests no packages.
--- End Message ---
--- Begin Message ---
Source: libapache-mod-auth-kerb
Source-Version: 5.4-2.4~deb10u1

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

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

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated libapache-mod-auth-kerb 
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, 27 Oct 2019 13:58:04 +0800
Source: libapache-mod-auth-kerb
Architecture: source
Version: 5.4-2.4~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Ghe Rivero 
Changed-By: Paul Wise 
Closes: 934043
Changes:
 libapache-mod-auth-kerb (5.4-2.4~deb10u1) buster; urgency=medium
 .
   * Rebuild for buster
 .
 libapache-mod-auth-kerb (5.4-2.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from upstream issue tracker to fix crash (Closes: #934043)
Checksums-Sha1:
 8cf6b1e0ea6c21f5c3e384118bc8b46d5407014f 1881 
libapache-mod-auth-kerb_5.4-2.4~deb10u1.dsc
 0d9f4c45c7d9289380dc5db0f3ec9a33fd36f307 51231 
libapache-mod-auth-kerb_5.4-2.4~deb10u1.diff.gz
 c20360cc9eeff357932c3fa9b89567785c158ebd 7002 
libapache-mod-auth-kerb_5.4-2.4~deb10u1_amd64.buildinfo
Checksums-Sha256:
 bec82352aaa830f19ab4e60e7fd228b1dabb73bc6d06181c5bf498b7157ce856 1881 
libapache-mod-auth-kerb_5.4-2.4~deb10u1.dsc
 277ed7a264c281a5266453c8525a830c1aebdb928c48cd267a679fe5d662b994 51231 
libapache-mod-auth-kerb_5.4-2.4~deb10u1.diff.gz
 9f8fceda02483eae3742b065d4fed4cb6572684362e69217bbc63ce081045575 7002 
libapache-mod-auth-kerb_5.4-2.4~deb10u1_amd64.buildinfo
Files:
 5b4681cd754932cb4730a32913094162 1881 net 

Bug#944400: sphinx: autopkgtest fails with texlive (2019.20191030-1)

2019-11-09 Thread Dmitry Shachnev
Control: reassign -1 texlive-base 2019.20191030-1
Control: affects -1 src:sphinx

Hi,

On Sat, Nov 09, 2019 at 08:17:40AM +0100, Bas Couwenberg wrote:
> Dear Maintainer,
>
> The autopkgtest of your package fail with texlive (2019.20191030-1):
>
>  https://ci.debian.net/data/autopkgtest/testing/amd64/s/sphinx/3363555/log.gz
>
> This is blocking testing migration of various packages.

According to [1] it is a bug in TeX Live, to be fixed soon.

Thanks to Norbert for investigating this!

[1]: https://lists.debian.org/debian-tex-maint/2019/11/msg9.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Processed: Re: Bug#944400: sphinx: autopkgtest fails with texlive (2019.20191030-1)

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 texlive-base 2019.20191030-1
Bug #944400 [src:sphinx] sphinx: autopkgtest fails with texlive 
(2019.20191030-1)
Bug reassigned from package 'src:sphinx' to 'texlive-base'.
No longer marked as found in versions sphinx/1.8.5-3.
Ignoring request to alter fixed versions of bug #944400 to the same values 
previously set
Bug #944400 [texlive-base] sphinx: autopkgtest fails with texlive 
(2019.20191030-1)
Marked as found in versions texlive-base/2019.20191030-1.
> affects -1 src:sphinx
Bug #944400 [texlive-base] sphinx: autopkgtest fails with texlive 
(2019.20191030-1)
Added indication that 944400 affects src:sphinx

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



Bug#942861: marked as done (linux-image-amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942861: fixed in linux 5.3.9-1
has caused the Debian Bug report #942861,
regarding linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
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.)


-- 
942861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.3.7-1
Severity: serious
Justification: Policy 12.5

adequate reports the file is missing, and is right. The directory is there,
but not a symbolic link and empty.

tglase@tglase-nb:~ $ ll -d /usr/share/doc/linux-image-amd64
drwxr-xr-x 2 root root 4096 Oct 22 15:50 /usr/share/doc/linux-image-amd64/
tglase@tglase-nb:~ $ ll  /usr/share/doc/linux-image-amd64
total 0


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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.3.0-1-amd64  5.3.7-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - 

Bug#937066: monkeysign: Python2 removal in sid/bullseye

2019-11-09 Thread Antoine Beaupré
There was a 3 year old "python 3" branch sitting around in the repo that
I revived by merging in the latest code.

Tests still fail (the test suite hangs on py2 and fails on py3), but at
least there's some work done. A large part of the porting was already
done by converting `print` statements to the `logging` library (thanks
to simonft).

Help on this front would be greatly appreciated. I was already
considering abandoning monkeysign before I realized I had to port it to
Python 3, so it is likely this software will simply die if no one steps
up to help.

A.
-- 
L'ennui avec la grande famille humaine, c'est que tout le monde veut
en être le père.
- Mafalda



Bug#885517: Bug#935335: Depends on removed python-zbar

2019-11-09 Thread Antoine Beaupré
On 2019-08-21 23:49:06, Andrey Rahmatullin wrote:
> Package: src:monkeysign
> Version: 2.2.4
> Severity: serious
>
> As Python 2 versions of zbar and zbarpygtk were removed, this package should 
> be
> updated to use Python 3 or removed.

Monkeysign will not be ported to zbar or pygtk3. There is already
another alternative (GNOME keysign) which does what monkeyscan does, and
better.

I will probably replace all of monkeyscan's code with this simple shell
command:

zenity --error --text="Monkeyscan has been removed from Monkeysign. Use 
GNOME keysign instead." --width 400

But I will focus on porting to Python 3 first..

a.
-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.- Stokely Carmichael



Bug#939571: marked as done (Fails to import)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 23:11:24 +
with message-id 
and subject line Bug#939571: fixed in python-pyqtgraph 0.10.0-5
has caused the Debian Bug report #939571,
regarding 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.)


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

Package: python3-pyqtgraph
Version: 0.10.0-4
Severity: important

Version 0.10.0-4 fails to import:


import pyqtgraph

Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/pyqtgraph/__init__.py", line 210, in 

   from .graphicsItems.GraphicsLayout import *
 File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/GraphicsLayout.py", 
line 6, in 
   from .PlotItem import PlotItem
 File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/PlotItem/__init__.py", 
line 1, in 
   from .PlotItem import PlotItem
 File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/PlotItem/PlotItem.py", 
line 9, in 
   from ...widgets.FileDialog import FileDialog
ModuleNotFoundError: No module named 'pyqtgraph.widgets'


--- End Message ---
--- Begin Message ---
Source: python-pyqtgraph
Source-Version: 0.10.0-5

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated python-pyqtgraph 
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: Tue, 05 Nov 2019 19:04:32 +0100
Source: python-pyqtgraph
Binary: python3-pyqtgraph python-pyqtgraph-doc
Architecture: source
Version: 0.10.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Georges Khaznadar 
Description:
 python-pyqtgraph-doc - Scientific Graphics and GUI Library for Python (common 
documentat
 python3-pyqtgraph - Scientific Graphics and GUI Library for Python 3
Closes: 939571
Changes:
 python-pyqtgraph (0.10.0-5) unstable; urgency=medium
 .
   [ Georges Khaznadar ]
   * For some mysterious reason, the expressions used to build the list of
 python files to package misses the last directory in the list; when I
 call *the same* expressions in a Python shell, it does not fail. So I
 made a quick &  fix: I hardcoded the list of files to package,
 which closes: #939571
 .
   [ Gianfranco Costamagna ]
   * Bump std-version to 4.1.1
Checksums-Sha1:
 f4cf5ccbe3f1e4a0dd0afd666beb44837ba92806 2173 python-pyqtgraph_0.10.0-5.dsc
 a1b87cd31c7074d9ff666353d08c24b284d63655 183756 
python-pyqtgraph_0.10.0-5.debian.tar.xz
 a87bd16c692be761ef2f9682011901bb301de224 8656 
python-pyqtgraph_0.10.0-5_source.buildinfo
Checksums-Sha256:
 32d0d7352f1a13c2df92e8d0bc449f6f48aff00330fecd7f0ece9d77ee64639e 2173 
python-pyqtgraph_0.10.0-5.dsc
 223797b0d10f42b3aa3a82621db302aa10b37e025159cedd0581ea1e38b76a4d 183756 
python-pyqtgraph_0.10.0-5.debian.tar.xz
 cac13b2fb754d0cd5c7deea3240fbac861923839489b0ae3e225eddbe624737c 8656 
python-pyqtgraph_0.10.0-5_source.buildinfo
Files:
 19d716e796145b4486c189c7ba9cdf05 2173 python optional 
python-pyqtgraph_0.10.0-5.dsc
 88b831f13597528c523ad40a9f26744a 183756 python optional 
python-pyqtgraph_0.10.0-5.debian.tar.xz
 961d2e236808bc6663cff9eed947817a 8656 python optional 
python-pyqtgraph_0.10.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl3HPUEACgkQ808JdE6f
XdkzehAA0qh5yLWwxREuoy63wE7WIFCrRuoxfQt7UJxcTYh0C5/7mhugbW/QL8MX
Wpr1xfkWMV5xXTamyYrONgdoZnHW9CTF76S+GOrTUIWwuQ42EXRzB76UaIhnQSm2
gX5g2Hq359rwl4cPhRNuPeor65l3aBkCXgtBxhvBntFp5Mb0BfSsCHv8XsZzPomO
akzJ5ZR8/jpkJsIfXz850MOKAT4Tf417iKDk5YWUuG4dynEhMcQz3x+epJ7REgut
2jBuZDevgyh5Y/EnGgEwxmNUgK8vRAzgQx0BOOcnCz7uEjpmlzezfV/e+H8dfV+E
DGAxoZ6YRzcMj7Ubdg/Y0tc/pMIeW82fmBiG+Eeqlp/7+JC/zAq3icvanIolx7P9
RvDt2BXfeGIqIwx600cPuZ2EIbSGVdWSYBDSHSQjtLtU8c2ZFD2Ufk54UAsJACS9
8XbQfZktQyTtGIGXGcMCiLQasL9bMSN9rAZteKziXaoCNIQseLT7leuRmNNyDGft
uNJaPBKDw/jjn3qX8pCcb/QsgJIlcScAr4hpOdRvDTQKICt6Af0oHq7K6Oe144xP

Processed: Bug#943870 marked as pending in auralquiz

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #943870 [src:auralquiz] auralquiz: FTBFS: undefined reference to 
`Phonon::phononVersion()'
Added tag(s) pending.

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



Bug#943870: marked as pending in auralquiz

2019-11-09 Thread Markus Koschany
Control: tag -1 pending

Hello,

Bug #943870 in auralquiz 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/games-team/auralquiz/commit/067418a58c74c1e036f190f6333e6822294fc462


Fix FTBFS by adding -lphonon4qt5 to LDFLAGS.

Thanks: Steve Langasek for the report and JanKusanagi for the fix.
Closes: #943870


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943870



Processed: reopening 933581

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 933581
Bug #933581 {Done: Gianfranco Costamagna } 
[python-networkx] BD on texlive-generic-extra which isn't build anymore and 
isn't in bullseye
'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 python-networkx/2.2-3.
> thanks
Stopping processing here.

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



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

2019-11-09 Thread Dmitry Bogatov


control: tags -1 +help

[2019-11-08 13:42] Santiago Vila 
> Hi.
>
> I've asked the Release Managers about this here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944351
>
> If they say yes, I'll modify base-files accordingly (for Debian 10.2).
>
> If they say no, please be ready to fix the bug in lsb-release as soon
> as you can, by making an upload to proposed-updates (there is a point
> release around the corner).

I am losing context. We have at least following three files (oh, why all
this madness?):

 * /usr/lib/os-release
 * /etc/os-release
 * /etc/debian_version

So, in case of conflicts, what should override what?

BTW, help via NMU/Team upload is welcome.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.



Bug#943870: marked as done (auralquiz: FTBFS: undefined reference to `Phonon::phononVersion()')

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 23:49:17 +
with message-id 
and subject line Bug#943870: fixed in auralquiz 1.0.0-3
has caused the Debian Bug report #943870,
regarding auralquiz: FTBFS: undefined reference to `Phonon::phononVersion()'
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.)


-- 
943870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: auralquiz
Version: 1.0.0-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear maintainers,

I noticed that the auralquiz package has been failing to build in Ubuntu. 
Testing in Debian unstable shows that it fails to build the same way:

[...]
g++ -Wl,-z,relro -Wl,-z,now -o auralquiz main.o auralwindow.o optionsdialog.o 
answerbox.o ranking.o musicanalyzer.o qrc_auralquiz.o moc_auralwindow.o 
moc_optionsdialog.o moc_answerbox.o moc_ranking.o moc_musicanalyzer.o   -ltag 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so /usr/lib/x86_64-linux-gnu/libQt5Core.so 
/usr/lib/x86_64-linux-gnu/libGL.so -lpthread   
/usr/bin/ld: auralwindow.o: in function `AuralWindow::showAbout()':
./src/auralwindow.cpp:1152: undefined reference to `Phonon::phononVersion()'
/usr/bin/ld: auralwindow.o: in function `AuralWindow::nextSongLoaded()':
./src/auralwindow.cpp:1343: undefined reference to `Phonon::MediaObject::play()'
/usr/bin/ld: ./src/auralwindow.cpp:1344: undefined reference to 
`Phonon::MediaObject::pause()'
/usr/bin/ld: auralwindow.o: in function 
`AuralWindow::playerStateChanged(Phonon::State, Phonon::State)':
[...]

  (https://launchpad.net/ubuntu/+source/auralquiz/1.0.0-2)

The undefined references are clearly because the binary uses libphonon but
is not being linked against it.  I do not know why it is not linking against
libphonon.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: auralquiz
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated auralquiz 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, 10 Nov 2019 00:11:04 +0100
Source: auralquiz
Architecture: source
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 943870
Changes:
 auralquiz (1.0.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Declare compliance with Debian Policy 4.4.1.
   * Fix FTBFS by adding -lphonon4qt5 to LDFLAGS.
 Thanks to Steve Langasek for the report and JanKusanagi for the fix.
 (Closes: #943870)
Checksums-Sha1:
 2b3c43ede4253493004837d72a03860ced222319 2142 auralquiz_1.0.0-3.dsc
 6b4cf4d4b23860adde7f76ef4ec5e7e79c399e30 2860 auralquiz_1.0.0-3.debian.tar.xz
 d8d3be09feb1390cfa1f2d4af77801429e693553 12026 
auralquiz_1.0.0-3_amd64.buildinfo
Checksums-Sha256:
 664f89aa627bb1744af0284ffd34e58a37c3e19a7ee8c05be6975dc56c1d4735 2142 
auralquiz_1.0.0-3.dsc
 4f215ef516b823ee4d5de327893c976c3bb981736fca6bbc9aa123d56f1c5ba6 2860 
auralquiz_1.0.0-3.debian.tar.xz
 8eb9e0203dc092361cd26dcb73a846b47a7a94f23e3bb52149e8c93b75cdda73 12026 
auralquiz_1.0.0-3_amd64.buildinfo
Files:
 5767a07159e87e8ad502256b54899c20 2142 games optional auralquiz_1.0.0-3.dsc
 b457cca57f699dbc1e036d41a474a975 2860 games optional 
auralquiz_1.0.0-3.debian.tar.xz
 171e4563a9c276a1527ab85c95ebd308 12026 games optional 
auralquiz_1.0.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl3HSB9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD

Bug#933581: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Nov 2019 00:55:18 +
with message-id 
and subject line Bug#933581: fixed in python-networkx 2.2-3
has caused the Debian Bug report #933581,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in 
bullseye
to be marked as done.

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

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


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

Recently the texlive-base package has stopped building the transitional
package texlive-generic-extra. This is an issue for your package as it
build-depends on it. Please update the building of your package to use
texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-07-16.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-networkx
Source-Version: 2.2-3

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
python-networkx 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, 10 Nov 2019 00:43:00 +0100
Source: python-networkx
Binary: python-networkx python3-networkx python-networkx-doc
Architecture: source
Version: 2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Gianfranco Costamagna 
Description:
 python-networkx - tool to create, manipulate and study complex networks
 python-networkx-doc - tool to create, manipulate and study complex networks - 
documenta
 python3-networkx - tool to create, manipulate and study complex networks 
(Python3)
Closes: 933581
Changes:
 python-networkx (2.2-3) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Team upload
   * Add patch from Steve Langasek  to move 
sphinx to Python3
   * Do not Recommend gdal, just Suggest it, to avoid Ubuntu putting too much 
stuff in main
   * Move some other dependencies to suggestions only, to avoid Ubuntu pulling 
too much stuff into main
 .
   [ Thomas Goirand, Paul Gevers, Steve Langasek ]
   * Removed build-depends on texlive-generic-extra (Closes: #933581).
Checksums-Sha1:
 9c25a8697b432c8c915894512a6745953b7c0e39 2820 python-networkx_2.2-3.dsc
 0deb3b674848975773bec9293726bec6e1f8b774 169300 
python-networkx_2.2-3.debian.tar.xz
 4b27a2730b2f8ad56ff4a469ea98b7d4366df186 9038 
python-networkx_2.2-3_source.buildinfo
Checksums-Sha256:
 14a9d6ca658d21c937f37e39a1cdf41ca5c999a2e2962aec7926adcbc92281de 2820 
python-networkx_2.2-3.dsc
 d75b1b34b11a8d09cac7f194b4161c487cd3b34fa7c611e9fb6e349a0d7ec2ea 169300 
python-networkx_2.2-3.debian.tar.xz
 d458b0eda1812e4d19a46cab4a4faace10e5e8cff9ae6a4fce705b50855a3351 9038 
python-networkx_2.2-3_source.buildinfo
Files:
 86eaea9cd28dfd075ce70080b5bfa5b4 2820 python optional python-networkx_2.2-3.dsc
 038807a8ca279f091e17e2e249352616 169300 python optional 
python-networkx_2.2-3.debian.tar.xz
 b0c597d2c1e854c907678d784cb1c795 9038 python optional 
python-networkx_2.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl3HUfUACgkQ808JdE6f
XdnsYg/+OGtmfI30SvONtin0KeK4GDp+CJtWrgI2rc8wAGd8BQRAIPSU2qHF++nt
JXZSiLQK0srE7L4X25OKIEwVysQwwrPf2C6f4gc/MiIxRki+VmmXuuK9tODWkvQr
e99AafJlyxPPmJxtNkP52fddWu40sQVK1EzemtSGHAh4WVY08X2eRiUTWcEH91Ji
p4MgTWRE5sL8TPXwuoneNXSfdQ8InOG0rS6xW/EUpETP3KQbincXDLRyFmBPKvvg
MKDcrGqgUdNFakM/y9cfXmRWTMu4v4xf9zh66tggda00IQ6Nwaq7qur1iBwUuUQD
xqQqsxtAPVaQ5FsmBO1Se2VmyG1XW+wG3JMrwq1MFC/5QiDfTmW9lyJFIlWEmFX5
R1wrmiFrL8N39YONV5IRby564E5QEk6Ojqa2Mrjv4LdHs76W71wFHRsZRw43jm1E
yHVhPpP2nH5VM8hoUmKdOmwfOFCCxxxYxCW+m6ibRiBSY4MVKkZtnnN4SXoGA1Nq
LKog2l7AA+4ox4mVysu0RdmLZn3Vx/Ov5kwNIvHbOCWu5LsWDVMeYPlAN5EGOGtd
548SuiVY15raSlj0D/XqM/KBYkm4irb0eSiAbokX4SzHXKYJCo7LSjSVONmbUZYO
4ov+gdrTzABKqvUFPkqNpOhMwe0SQvO/4S4DybruJkJt3H+wv4s=
=dtyX
-END PGP 

Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Ben Hutchings
On Sun, 2019-11-10 at 01:12 +, Ben Hutchings wrote:
> On Sun, 2019-11-10 at 02:11 +0100, Vincent Lefevre wrote:
> > On 2019-11-10 00:48:12 +, Ben Hutchings wrote:
> > > Control: retitle -1 ocaml-base-nox: Replaces 
> > > /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
> > > 
> > > On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
> > [...]
> > > > Is this the same bug as #944126 (the bug title is the same) or
> > > > is it still present in 4.08.1-4?
> > > 
> > > It appears that files have been moved both ways between ocaml-base-nox
> > > and ocaml-nox.  The original bug report showed two file conflicts, but
> > > only one of them was fixed.
> > 
> > ocaml-base-nox 4.08.1-4 has:
> > 
> > Replaces: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > Breaks: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > 
> > Isn't that sufficient?
> 
> Well, the upgrade still failed for me with this version.

Sorry, the version I found this in is 4.08.1-3, as recored on the bug
report.  Version 4.08.1-4 probably does fix this, but I've already
removed the ocaml packages since I didn't actually need them.

Ben.

-- 
Ben Hutchings
Humans are not rational beings; they are rationalising beings.




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


Bug#941231: u-boot-imx: mx6cuboxi fails to boot

2019-11-09 Thread Heinrich Schuchardt

The discussion lead to the following merged upstream patches:

[1] - https://patchwork.ozlabs.org/patch/1173314/
[2] - https://patchwork.ozlabs.org/patch/1173316/

Best regards

Heinrich



Processed: Bug#933581 marked as pending in python-networkx

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933581 [python-networkx] BD on texlive-generic-extra which isn't build 
anymore and isn't in bullseye
Added tag(s) pending.

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



Bug#933581: marked as pending in python-networkx

2019-11-09 Thread Sandro Tosi
Control: tag -1 pending

Hello,

Bug #933581 in python-networkx 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-networkx/commit/2d3f13a50e08dac190f8614d93594429252058dc


Drop python3 and -doc packages, taken over by src:networkx; this removes quite 
some b-d and all the patches; Closes: #935195, #933581


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933581



Processed: Re: Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 ocaml-base-nox: Replaces /usr/lib/ocaml/libasmrun_shared.so in 
> older ocaml-nox
Bug #944254 [ocaml-base-nox] ocaml-nox: Files overwrite 
/usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Changed Bug title to 'ocaml-base-nox: Replaces 
/usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox' from 'ocaml-nox: Files 
overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package'.

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



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Ben Hutchings
Control: retitle -1 ocaml-base-nox: Replaces /usr/lib/ocaml/libasmrun_shared.so 
in older ocaml-nox

On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
> On 2019-11-06 19:53:14 +, Ben Hutchings wrote:
> > Control: reassign -1 ocaml-base-nox 4.08.1-3
> 
> What's the status of this bug?
> 
> I can see in the Debian ChangeLog:
> 
> ocaml (4.08.1-4) unstable; urgency=medium 
>  #
>   
>  ▒
>   * ocaml-base-nox Breaks/Replaces also ocaml-nox (Closes: #944126)   
>  ▒
>   * Install seq compatibility package 
>  ▒
>   
>  ▒
>  -- Stéphane Glondu   Fri, 08 Nov 2019 11:43:37 +0100  
>  ▒
> 
> Is this the same bug as #944126 (the bug title is the same) or
> is it still present in 4.08.1-4?

It appears that files have been moved both ways between ocaml-base-nox
and ocaml-nox.  The original bug report showed two file conflicts, but
only one of them was fixed.

Ben.

-- 
Ben Hutchings
Humans are not rational beings; they are rationalising beings.



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


Processed: reassign 944126 to src:ocaml, reassign 944254 to src:ocaml, forcibly merging 944126 944254 ...

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 944126 src:ocaml 4.05.0-12
Bug #944126 {Done: Stéphane Glondu } [ocaml-nox] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Bug reassigned from package 'ocaml-nox' to 'src:ocaml'.
No longer marked as found in versions ocaml/4.05.0-12.
No longer marked as fixed in versions ocaml/4.08.1-4.
Bug #944126 {Done: Stéphane Glondu } [src:ocaml] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Marked as found in versions ocaml/4.05.0-12.
> reassign 944254 src:ocaml 4.05.0-12
Bug #944254 [ocaml-base-nox] ocaml-base-nox: Replaces 
/usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
Bug reassigned from package 'ocaml-base-nox' to 'src:ocaml'.
No longer marked as found in versions ocaml/4.08.1-3.
Ignoring request to alter fixed versions of bug #944254 to the same values 
previously set
Bug #944254 [src:ocaml] ocaml-base-nox: Replaces 
/usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
Marked as found in versions ocaml/4.05.0-12.
> forcemerge 944126 944254
Bug #944126 {Done: Stéphane Glondu } [src:ocaml] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Bug #944254 [src:ocaml] ocaml-base-nox: Replaces 
/usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
Marked Bug as done
Merged 944126 944254
> fixed 944126 4.08.1-4
Bug #944126 {Done: Stéphane Glondu } [src:ocaml] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Bug #944254 {Done: Stéphane Glondu } [src:ocaml] 
ocaml-base-nox: Replaces /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
Marked as fixed in versions ocaml/4.08.1-4.
Marked as fixed in versions ocaml/4.08.1-4.
> thanks
Stopping processing here.

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



Bug#875031: marked as done ([linguider] Future Qt4 removal from Buster)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Nov 2019 05:43:26 +
with message-id 
and subject line Bug#944405: Removed package(s) from unstable
has caused the Debian Bug report #875031,
regarding [linguider] Future Qt4 removal from Buster
to be marked as done.

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

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


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


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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


Processed: Re: Processed: Re: Bug#944400: sphinx: autopkgtest fails with texlive (2019.20191030-1)

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 944400 + pending
Bug #944400 [texlive-base] sphinx: autopkgtest fails with texlive 
(2019.20191030-1)
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Vincent Lefevre
On 2019-11-06 19:53:14 +, Ben Hutchings wrote:
> Control: reassign -1 ocaml-base-nox 4.08.1-3

What's the status of this bug?

I can see in the Debian ChangeLog:

ocaml (4.08.1-4) unstable; urgency=medium  #
   ▒
  * ocaml-base-nox Breaks/Replaces also ocaml-nox (Closes: #944126)▒
  * Install seq compatibility package  ▒
   ▒
 -- Stéphane Glondu   Fri, 08 Nov 2019 11:43:37 +0100   ▒

Is this the same bug as #944126 (the bug title is the same) or
is it still present in 4.08.1-4?

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



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Vincent Lefevre
On 2019-11-10 00:48:12 +, Ben Hutchings wrote:
> Control: retitle -1 ocaml-base-nox: Replaces 
> /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
> 
> On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
[...]
> > Is this the same bug as #944126 (the bug title is the same) or
> > is it still present in 4.08.1-4?
> 
> It appears that files have been moved both ways between ocaml-base-nox
> and ocaml-nox.  The original bug report showed two file conflicts, but
> only one of them was fixed.

ocaml-base-nox 4.08.1-4 has:

Replaces: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
Breaks: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)

Isn't that sufficient?

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



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

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +help
Bug #939733 [lsb-release] lsb-release: lsb_release does not show point release 
on Debian 10.1
Added tag(s) help.

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



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Ben Hutchings
On Sun, 2019-11-10 at 02:11 +0100, Vincent Lefevre wrote:
> On 2019-11-10 00:48:12 +, Ben Hutchings wrote:
> > Control: retitle -1 ocaml-base-nox: Replaces 
> > /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
> > 
> > On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
> [...]
> > > Is this the same bug as #944126 (the bug title is the same) or
> > > is it still present in 4.08.1-4?
> > 
> > It appears that files have been moved both ways between ocaml-base-nox
> > and ocaml-nox.  The original bug report showed two file conflicts, but
> > only one of them was fixed.
> 
> ocaml-base-nox 4.08.1-4 has:
> 
> Replaces: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> Breaks: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> 
> Isn't that sufficient?

Well, the upgrade still failed for me with this version.

Ben.

-- 
Ben Hutchings
Humans are not rational beings; they are rationalising beings.




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


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

2019-11-09 Thread Santiago Vila
On Sun, Nov 10, 2019 at 01:13:08AM +, Dmitry Bogatov wrote:
> 
> control: tags -1 +help
> 
> [2019-11-08 13:42] Santiago Vila 
> > Hi.
> >
> > I've asked the Release Managers about this here:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944351
> >
> > If they say yes, I'll modify base-files accordingly (for Debian 10.2).
> >
> > If they say no, please be ready to fix the bug in lsb-release as soon
> > as you can, by making an upload to proposed-updates (there is a point
> > release around the corner).
> 
> I am losing context. We have at least following three files (oh, why all
> this madness?):
> 
>  * /usr/lib/os-release
>  * /etc/os-release
>  * /etc/debian_version
> 
> So, in case of conflicts, what should override what?

Please note that /usr/lib/os-release and /etc/os-release are the same file.

AFAIK, lsb-release is already ignoring /etc/debian_version in buster,
which is the reason we have this problem.

We should either:

a) modify lsb-release so that it looks at /etc/debian_version again
(i.e. reverting the recent change)

or

b) As it has been suggested by you, fixing the problem in base-files
by including the minor version in /etc/os-release "somewhere".

I am ok with doing the change in base-files, because I believe it's
the best option in the long term.

I also believe that it would suffice to change VERSION_ID, but I need
confirmation for that.

My feeling is that Release Managers would welcome this change if it's
*limited* to VERSION_ID. Rationale: Major Release versions are integer
numbers (7, 8, 9, 10, etc), and we identify "buster" with "Debian 10",
without minor version, i.e. there should be no need
to change PRETTY_NAME or VERSION, only VERSION_ID.

So: Is this ok for you?

Thanks.



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Vincent Lefevre
On 2019-11-10 01:34:14 +, Ben Hutchings wrote:
> On Sun, 2019-11-10 at 01:12 +, Ben Hutchings wrote:
> > On Sun, 2019-11-10 at 02:11 +0100, Vincent Lefevre wrote:
> > > On 2019-11-10 00:48:12 +, Ben Hutchings wrote:
> > > > Control: retitle -1 ocaml-base-nox: Replaces 
> > > > /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
> > > > 
> > > > On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
> > > [...]
> > > > > Is this the same bug as #944126 (the bug title is the same) or
> > > > > is it still present in 4.08.1-4?
> > > > 
> > > > It appears that files have been moved both ways between ocaml-base-nox
> > > > and ocaml-nox.  The original bug report showed two file conflicts, but
> > > > only one of them was fixed.
> > > 
> > > ocaml-base-nox 4.08.1-4 has:
> > > 
> > > Replaces: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > > Breaks: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > > 
> > > Isn't that sufficient?
> > 
> > Well, the upgrade still failed for me with this version.
> 
> Sorry, the version I found this in is 4.08.1-3, as recored on the bug
> report.  Version 4.08.1-4 probably does fix this, but I've already
> removed the ocaml packages since I didn't actually need them.

I've just done the upgrade from 4.05.0-12 to 4.08.1-4, and I did not
get any error.

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



Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Ben Hutchings
Control: notfixed 944126 4.08.1-3
Control: forcemerge 944126 -1

On Sun, 2019-11-10 at 02:56 +0100, Vincent Lefevre wrote:
> On 2019-11-10 01:34:14 +, Ben Hutchings wrote:
> > On Sun, 2019-11-10 at 01:12 +, Ben Hutchings wrote:
> > > On Sun, 2019-11-10 at 02:11 +0100, Vincent Lefevre wrote:
> > > > On 2019-11-10 00:48:12 +, Ben Hutchings wrote:
> > > > > Control: retitle -1 ocaml-base-nox: Replaces 
> > > > > /usr/lib/ocaml/libasmrun_shared.so in older ocaml-nox
> > > > > 
> > > > > On Sun, 2019-11-10 at 01:41 +0100, Vincent Lefevre wrote:
> > > > [...]
> > > > > > Is this the same bug as #944126 (the bug title is the same) or
> > > > > > is it still present in 4.08.1-4?
> > > > > 
> > > > > It appears that files have been moved both ways between ocaml-base-nox
> > > > > and ocaml-nox.  The original bug report showed two file conflicts, but
> > > > > only one of them was fixed.
> > > > 
> > > > ocaml-base-nox 4.08.1-4 has:
> > > > 
> > > > Replaces: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > > > Breaks: ocaml-base (<< 4.08), ocaml-nox (<< 4.08)
> > > > 
> > > > Isn't that sufficient?
> > > 
> > > Well, the upgrade still failed for me with this version.
> > 
> > Sorry, the version I found this in is 4.08.1-3, as recored on the bug
> > report.  Version 4.08.1-4 probably does fix this, but I've already
> > removed the ocaml packages since I didn't actually need them.
> 
> I've just done the upgrade from 4.05.0-12 to 4.08.1-4, and I did not
> get any error.

Great.  Since the changelog for -4 closed #944126, I'm merging these
reports back together and marking them as both fixed in -4, not -3.

Ben.

-- 
Ben Hutchings
Humans are not rational beings; they are rationalising beings.



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


Processed (with 1 error): Re: Bug#944254: ocaml-nox: Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package

2019-11-09 Thread Debian Bug Tracking System
Processing control commands:

> notfixed 944126 4.08.1-3
Bug #944126 {Done: Stéphane Glondu } [ocaml-nox] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
No longer marked as fixed in versions ocaml/4.08.1-3.
> forcemerge 944126 -1
Bug #944126 {Done: Stéphane Glondu } [ocaml-nox] ocaml-nox: 
Files overwrite /usr/lib/ocaml/bigarray.cmi in ocaml-base-nox package
Unable to merge bugs because:
package of #944254 is 'ocaml-base-nox' not 'ocaml-nox'
Failed to forcibly merge 944126: Did not alter merged bugs.


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



Bug#896611: marked as done (portabase FTBFS with sphinx 1.7.2)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Nov 2019 05:43:54 +
with message-id 
and subject line Bug#944406: Removed package(s) from unstable
has caused the Debian Bug report #896611,
regarding portabase FTBFS with sphinx 1.7.2
to be marked as done.

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

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


-- 
896611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: portabase
Version: 2.1+git20120910-1.1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/portabase-2.1+git20120910'
for lang in en cs fr ja zh_TW; do \
dh_sphinxdoc -v usr/share/portabase/help/$lang ;\
done
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
make[1]: *** [debian/rules:56: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Version: 2.1+git20120910-1.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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


Bug#875098: marked as done ([portabase] Future Qt4 removal from Buster)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Nov 2019 05:43:54 +
with message-id 
and subject line Bug#944406: Removed package(s) from unstable
has caused the Debian Bug report #875098,
regarding [portabase] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
875098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: portabase
Version: 2.1+git20120910-1.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 2.1+git20120910-1.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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


Bug#941474: marked as done (networkx: Incomplete debian/copyright?)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Nov 2019 06:30:24 +
with message-id 
and subject line Bug#941474: fixed in networkx 2.4-1
has caused the Debian Bug report #941474,
regarding networkx: Incomplete debian/copyright?
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.)


-- 
941474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networkx
Version: 2.3-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: mo...@debian.org, ftpmas...@debian.org

Hi,

I just ACCEPTed networkx from NEW but noticed it was missing attribution
for at least Edward L. Platt.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: networkx
Source-Version: 2.4-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Nov 2019 23:55:38 -0500
Source: networkx
Architecture: source
Version: 2.4-1
Distribution: experimental
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 941474
Changes:
 networkx (2.4-1) experimental; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release
   * debian/rules
 - install examples
 - dont operate on networkx/tests/test.py, no longer present
   * debian/copyright
 - update copyright file; Closes: #941474
   * Use pytest instead of nose
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Fix wrong Vcs-*.
Checksums-Sha1:
 718ef25acfff83c2d03db40c5863dad0c22cb386 2596 networkx_2.4-1.dsc
 633ab7f52d145d1aaf16543d7407fc83e597f8c4 1165116 networkx_2.4.orig.tar.xz
 a1ebefd604eba7f8475d2c6add41c3bbb0ce52e4 14760 networkx_2.4-1.debian.tar.xz
 f04254a8de2fe8fc671e2f6c790fc70cc65c9492 8505 networkx_2.4-1_source.buildinfo
Checksums-Sha256:
 d20db1889409b56750f8360aeb13eecae6afb993ec43eada3fe29b9b8f0e346e 2596 
networkx_2.4-1.dsc
 23a9dfb710f653a07c1d85302da9c10ddc9db153a8e5b8a36101b4e4fc480c09 1165116 
networkx_2.4.orig.tar.xz
 7355ca818bbadbbe03de508d38dda5ed13ddb45c918f4ae0da5668a684df98f0 14760 
networkx_2.4-1.debian.tar.xz
 8c1aed952e55c391d9930e74eecf7621f620b636b72960c5051405cb53bc5005 8505 
networkx_2.4-1_source.buildinfo
Files:
 7f8f0855e4b2cb3c87e33ce8d4bed88b 2596 python optional networkx_2.4-1.dsc
 7da4a27a550a7738a7530b1c561e7e52 1165116 python optional 
networkx_2.4.orig.tar.xz
 f40e460acb75cfaedd8d084962a8cee9 14760 python optional 
networkx_2.4-1.debian.tar.xz
 7da637efb46685f9647638001a2d83d3 8505 python optional 
networkx_2.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3HmrEACgkQh588mTgB
qU+rTBAAxnOkKPrzvzd94hgNTA7rK5a8FXjKoYGsXP3diz6LKgQXwelIgfc13+Su
BQxgV2wCY2IoCrlDCcQ2shb34nIGNrkf3PYbktL30z4KuI/AWJhRVDpd0x1OKey2
Ocpu6KVbYRAd4l8E1J1WAP/cXklPawK4Ilqf2If3z2UbCc+Fys/qbgo0kMa9FpC5
VzRqBMQjXK3q8uUW1FsqcvDZMxyUw+MelQzrnPlkeaEi3w5cfbPGWVhScF5/w8jO
AZ9xJv8OayP4eOh+tA9fQv7CKZr10UCIPURanMRWzzoRXoMINJoNGVvnirryDpYM
8YSsD/5BEM0dmgWz4EFdUQSMX/8rQ0+5VLEe+y5kdZiElyk9WpeEbNaEv7SFdBH8
+9XqVKofURvOEBaDG0KBqeT4+0GwIedaYY/1PUltvj1mLAGGyMThptzaYBEvJw7m
zN/DZ8XPVXnxOYo5IHNAgrl8dfOeAX7bPsPZH4EBXSTBm/71/QQ6tMUTu2UXBrUB
pQ/bhGAD/IF2HbXOngboYGYJV9OkRcDy5yGjtJVwqiGs7hFD5mAjT3TWBQwHPO0p
X9DupdZGTo+R25luBtr1fH0dF81coYyOPt51jzE2Om3T6HMvedpAIjCXzvCLUxzi
75BXOI0O+1wqDyqcwKstL8896GEdvAcIrnyl7U8GSGV9yhWd1u8=
=oLXX
-END PGP SIGNATURE End Message ---


Bug#944327: fribidi: diff for NMU version 1.0.7-1.1

2019-11-09 Thread Lior Kaplan
Hi Salvatore,

As you already prepared a package, you can just upload it with no delay.

Thanks for the patch & help.

If you prefer we'd do the upload -let me know.



On Fri, Nov 8, 2019 at 2:51 PM Salvatore Bonaccorso 
wrote:

> Control: tags 944327 + patch
> Control: tags 944327 + pending
>
> Dear maintainer(s),
>
> I've prepared an NMU for fribidi (versioned as 1.0.7-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
>
> A merge request is as well created at
> https://salsa.debian.org/debian/fribidi/merge_requests/2 .
>
> Regards,
> Salvatore
>