Bug#887869: python-filelock FTBFS: test failures

[Adrian Bunk]

Source: python-filelock
Version: 3.0.0-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-filelock-3.0.0'
PYTHONPATH=. python2 /build/1st/python-filelock-3.0.0/debian/test.py
.FF..FF...
==
FAIL: test_threaded1 (__main__.FileLockTest)
--
Traceback (most recent call last):
  File "/build/1st/python-filelock-3.0.0/debian/test.py", line 228, in 
test_threaded1
threads1[i].join()
  File "/build/1st/python-filelock-3.0.0/debian/test.py", line 61, in join
raise (wrapper_ex.__class__, wrapper_ex, self.ex[2])
AssertionError

==
FAIL: test_timeout (__main__.FileLockTest)
--
Traceback (most recent call last):
  File "/build/1st/python-filelock-3.0.0/debian/test.py", line 248, in 
test_timeout
self.assertRaises(filelock.Timeout, lock2.acquire, timeout=1)
AssertionError: Timeout not raised

==
FAIL: test_default_timeout (__main__.SoftFileLockTest)
--
Traceback (most recent call last):
  File "/build/1st/python-filelock-3.0.0/debian/test.py", line 273, in 
test_default_timeout
self.assertRaises(filelock.Timeout, lock2.acquire)
AssertionError: Timeout not raised

==
FAIL: test_del (__main__.SoftFileLockTest)
--
Traceback (most recent call last):
  File "/build/1st/python-filelock-3.0.0/debian/test.py", line 330, in test_del
self.assertRaises(filelock.Timeout, lock2.acquire, timeout = 1)
AssertionError: Timeout not raised

--
Ran 22 tests in 19.163s

FAILED (failures=4)
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#887868: libgnomecanvas FTBFS with gtk-doc-tools 1.27-1

[Adrian Bunk]

Source: libgnomecanvas
Version: 2.30.3-3
Severity: serious
Tags: buster sid

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

...
Making all in reference
make[4]: Entering directory '/build/1st/libgnomecanvas-2.30.3/docs/reference'
gtk-doc: Scanning header files
gtk-doc: Building XML
./libgnomecanvas.args:7: warning: Property GnomeCanvasBpath:bpath has no 
documentation.
./libgnomecanvas.args:17: warning: Property GnomeCanvasClipgroup:path has no 
documentation.
./libgnomecanvas.args:27: warning: Property GnomeCanvasClipgroup:wind has no 
documentation.
./libgnomecanvas.args:47: warning: Property GnomeCanvas:focused-item has no 
documentation.
./libgnomecanvas.args:77: warning: Property GnomeCanvasItem:parent has no 
documentation.
./libgnomecanvas.args:87: warning: Property GnomeCanvasLine:arrow-shape-a has 
no documentation.
./libgnomecanvas.args:97: warning: Property GnomeCanvasLine:arrow-shape-b has 
no documentation.
./libgnomecanvas.args:107: warning: Property GnomeCanvasLine:arrow-shape-c has 
no documentation.
./libgnomecanvas.args:117: warning: Property GnomeCanvasLine:cap-style has no 
documentation.
./libgnomecanvas.args:127: warning: Property GnomeCanvasLine:fill-color has no 
documentation.
./libgnomecanvas.args:137: warning: Property GnomeCanvasLine:fill-color-gdk has 
no documentation.
./libgnomecanvas.args:147: warning: Property GnomeCanvasLine:fill-color-rgba 
has no documentation.
./libgnomecanvas.args:157: warning: Property GnomeCanvasLine:fill-stipple has 
no documentation.
./libgnomecanvas.args:167: warning: Property GnomeCanvasLine:first-arrowhead 
has no documentation.
./libgnomecanvas.args:177: warning: Property GnomeCanvasLine:join-style has no 
documentation.
./libgnomecanvas.args:187: warning: Property GnomeCanvasLine:last-arrowhead has 
no documentation.
./libgnomecanvas.args:197: warning: Property GnomeCanvasLine:line-style has no 
documentation.
./libgnomecanvas.args:207: warning: Property GnomeCanvasLine:points has no 
documentation.
./libgnomecanvas.args:217: warning: Property GnomeCanvasLine:smooth has no 
documentation.
./libgnomecanvas.args:227: warning: Property GnomeCanvasLine:spline-steps has 
no documentation.
./libgnomecanvas.args:237: warning: Property GnomeCanvasLine:width-pixels has 
no documentation.
./libgnomecanvas.args:247: warning: Property GnomeCanvasLine:width-units has no 
documentation.
./libgnomecanvas.args:257: warning: Property GnomeCanvasPixbuf:anchor has no 
documentation.
./libgnomecanvas.args:267: warning: Property GnomeCanvasPixbuf:height has no 
documentation.
./libgnomecanvas.args:277: warning: Property GnomeCanvasPixbuf:height-in-pixels 
has no documentation.
./libgnomecanvas.args:287: warning: Property GnomeCanvasPixbuf:height-set has 
no documentation.
./libgnomecanvas.args:297: warning: Property GnomeCanvasPixbuf:pixbuf has no 
documentation.
./libgnomecanvas.args:307: warning: Property GnomeCanvasPixbuf:width has no 
documentation.
./libgnomecanvas.args:317: warning: Property GnomeCanvasPixbuf:width-in-pixels 
has no documentation.
./libgnomecanvas.args:327: warning: Property GnomeCanvasPixbuf:width-set has no 
documentation.
./libgnomecanvas.args:337: warning: Property GnomeCanvasPixbuf:x has no 
documentation.
./libgnomecanvas.args:347: warning: Property GnomeCanvasPixbuf:x-in-pixels has 
no documentation.
./libgnomecanvas.args:357: warning: Property GnomeCanvasPixbuf:y has no 
documentation.
./libgnomecanvas.args:367: warning: Property GnomeCanvasPixbuf:y-in-pixels has 
no documentation.
./libgnomecanvas.args:377: warning: Property GnomeCanvasPolygon:points has no 
documentation.
./libgnomecanvas.args:387: warning: Property GnomeCanvasRE:x1 has no 
documentation.
./libgnomecanvas.args:397: warning: Property GnomeCanvasRE:x2 has no 
documentation.
./libgnomecanvas.args:407: warning: Property GnomeCanvasRE:y1 has no 
documentation.
./libgnomecanvas.args:417: warning: Property GnomeCanvasRE:y2 has no 
documentation.
./libgnomecanvas.args:627: warning: Property GnomeCanvasShape:cap-style has no 
documentation.
./libgnomecanvas.args:637: warning: Property GnomeCanvasShape:dash has no 
documentation.
./libgnomecanvas.args:647: warning: Property GnomeCanvasShape:fill-color has no 
documentation.
./libgnomecanvas.args:657: warning: Property GnomeCanvasShape:fill-color-gdk 
has no documentation.
./libgnomecanvas.args:667: warning: Property GnomeCanvasShape:fill-color-rgba 
has no documentation.
./libgnomecanvas.args:677: warning: Property GnomeCanvasShape:fill-stipple has 
no documentation.
./libgnomecanvas.args:687: warning: Property GnomeCanvasShape:join-style has no 
documentation.
./libgnomecanvas.args:697: warning: Property GnomeCanvasShape:miterlimit has no 
documentation.
./libgnomecanvas.args:707: warning: Property GnomeCanvasShape:outline-color has 
no documentation.
./libgnomecanvas.args:717: warning: Property GnomeCanvasShape:outline-color-gdk 
has no documentation.
./libgnomecanvas.args:727: 

Bug#887866: cxref FTBFS on amd64/i386 with glibc 2.26

[Adrian Bunk]

Source: cxref
Version: 1.6e-2
Severity: serious
Tags: buster sid

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

...
../src/cxref -O. -NREADME-TMP -xref README.c
/usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21: cxref: 
syntax error, unexpected IDENTIFIER, expecting ')'

The previous 10, current and next 10 symbols are:
-10 | 297 : LONG : long
 -9 | 301 :   DOUBLE : double
 -8 | 258 :   IDENTIFIER : __n
 -7 |  41 :  ')' : )
 -6 |  59 :  ';' : ;
 -5 | 286 :   EXTERN : extern
 -4 | 296 :  INT : int
 -3 | 258 :   IDENTIFIER : __fpclassifyf128
 -2 |  40 :  '(' : (
 -1 | 258 :   IDENTIFIER : _Float128
  0 | 258 :   IDENTIFIER : __value
  1 |  41 :  ')' : )
  2 |  59 :  ';' : ;
  3 | 286 :   EXTERN : extern
  4 | 296 :  INT : int
  5 | 258 :   IDENTIFIER : __signbitf128
  6 |  40 :  '(' : (
  7 | 258 :   IDENTIFIER : _Float128
  8 | 258 :   IDENTIFIER : __value
  9 |  41 :  ')' : )
 10 |  59 :  ';' : ;

../src/cxref -O. -NREADME-TMP -xref README.c -latex -html-src -rtf -sgml
/usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21: cxref: 
syntax error, unexpected IDENTIFIER, expecting ')'

The previous 10, current and next 10 symbols are:
-10 | 297 : LONG : long
 -9 | 301 :   DOUBLE : double
 -8 | 258 :   IDENTIFIER : __n
 -7 |  41 :  ')' : )
 -6 |  59 :  ';' : ;
 -5 | 286 :   EXTERN : extern
 -4 | 296 :  INT : int
 -3 | 258 :   IDENTIFIER : __fpclassifyf128
 -2 |  40 :  '(' : (
 -1 | 258 :   IDENTIFIER : _Float128
  0 | 258 :   IDENTIFIER : __value
  1 |  41 :  ')' : )
  2 |  59 :  ';' : ;
  3 | 286 :   EXTERN : extern
  4 | 296 :  INT : int
  5 | 258 :   IDENTIFIER : __signbitf128
  6 |  40 :  '(' : (
  7 | 258 :   IDENTIFIER : _Float128
  8 | 258 :   IDENTIFIER : __value
  9 |  41 :  ')' : )
 10 |  59 :  ';' : ;

mv README.c.tex README_c.tex
mv: cannot stat 'README.c.tex': No such file or directory
Makefile:100: recipe for target 'readme' failed
make[2]: *** [readme] Error 1

Bug#884294: Patch for pandas RC 884294, someone to sponsor?

[Lumin]

> I'd volunteer to upload once it is pushed.  Please ping me after pushing
> since there is not commit mailing list and I'm not sure whether the
> tracker solution is implemented yet.

Done.
https://salsa.debian.org/science-team/pandas/commits/debian

-- 
Best,

Bug#886163: marked as done (lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: output differs!)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 05:50:02 +
with message-id 
and subject line Bug#886163: fixed in lintian 2.5.71
has caused the Debian Bug report #886163,
regarding lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: 
output differs!
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/lintian.html

...
tests::files-multiarch-foreign-files: diff -u 
t/tests/files-multiarch-foreign-files/tags 
/build/1st/lintian-2.5.67/debian/test-out/tests/files-multiarch-foreign-files/tags.files-multiarch-foreign-files
--- t/tests/files-multiarch-foreign-files/tags  2018-01-01 14:58:24.0 
+
+++ 
/build/1st/lintian-2.5.67/debian/test-out/tests/files-multiarch-foreign-files/tags.files-multiarch-foreign-files
2019-02-04 09:30:53.054375012 +
@@ -1,3 +0,0 @@
-E: libfoo-dev: multiarch-foreign-cmake-file usr/lib/TRIPLET/cmake/foo.cmake
-E: libfoo-dev: multiarch-foreign-pkgconfig usr/lib/TRIPLET/pkgconfig/libfoo.pc
-E: libfoo-dev: multiarch-foreign-static-library usr/lib/TRIPLET/libfoo.a
fail tests::files-multiarch-foreign-files: output differs!


SS..
Skipped/disabled tests:
  [debs]
deb-format-wrong-order: Unmet test dependencies: dpkg (<< 1.17.2)
  [tests]
changelog-file-strange-date: Unmet test dependencies: dpkg (<< 1.18.2)
deb-format-udeb-compression: Unmet test dependencies: dpkg (<< 1.18.11)
debconf-config-not-executable: Unmet test dependencies: dpkg (<< 1.19.0)
debhelper-compat: Unmet test dependencies: debhelper (<< 9.20151101~)
debhelper-compat-empty: Unmet test dependencies: debhelper (<< 9.20151101~)
runtests-arch-amd64: architecture mismatch
upstream-metadata-invalid-yml: (disabled) YAML::XS executes code by default 
and code has not been converted
version-substvars-obsolete: Unmet test dependencies: dpkg (<< 1.17.2)

Failed tests (1)
tests::files-multiarch-foreign-files
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.71

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian 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, 21 Jan 2018 05:24:47 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.71
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 886163 887428 887715 887817
Changes:
 lintian (2.5.71) unstable; urgency=medium
 .
   * Summary of tag changes:
 + Added:
   - patch-file-present-but-not-mentioned-in-series
 .
   * checks/files.pm:
 + [CL] Ignore Rust .rs files in extra-license-file.  (Closes: #887715)
   * checks/patch-systems.{desc,pm}:
 + [CL] Check for patch files under the debian/patches that are not
   mentioned in any series file. Thanks to Paul Wise for the idea.
   (Closes: #887817)
   * checks/python.{desc,pm}:
 + [CL] Don't emit "python-package-missing-depends-on-python" for debug
   packages
 + [CL] Include possibility that the file should not even be installed
   in the description of python-package-missing-depends-on-python.
 .
   * data/spelling/corrections:
 + [PW] Add a number of corrections.
   * data/rules/rules-should-not-use:
 + [CL] Add more context to xz-compression-level-too-high tag output.
 .
   * lib/Lintian/Collect/Package.pm:
 + [CL] Fix "Use of uninitialized value 

Bug#866463: marked as done (pysurfer: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 07:04:38 +0200
with message-id <20180121050438.GA17002@localhost>
and subject line Re: Bug#866463: pysurfer: depends on obsolete python-imaging 
(replace with python3-pil or python-pil)
has caused the Debian Bug report #866463,
regarding pysurfer: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
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.)


-- 
866463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pysurfer
Version: 0.7-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
On Thu, Jun 29, 2017 at 04:39:06PM +, Matthias Klose wrote:
> Package: src:pysurfer
> Version: 0.7-2
> Severity: important
> Tags: sid buster
> User: d...@debian.org
> Usertags: imaging-pillow
> 
> One or more binary packages built from this source depends on or
> recommends python-imaging, which is obsolete for some years now.
> Please build the source using the python-pil package. If your
> package doesn't need to be built with Python2, please consider using
> Python3 and depend on python3-pil.
>...

This is a false positive, the dependency is already
  python-pil | python-imaging


cu
Adrian

-- 

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

Bug#887863: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Guillem Jover]

On Sun, 2018-01-21 at 02:59:53 +0100, Andreas Beckmann wrote:
> Control: clone -1 -2
> Control: retitle -2 libglib2.0-dev: needs dummy empty prerm
> Control: reassign -2 libglib2.0-dev 2.54.2-1
> 
> >> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:>>> For 
> >> now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
> Even if python is going to get fixed, this probably won't help
> libglib2.0-dev (which drops the python dependency in buster), therefore
> it will need to add the dummy empty prerm to mitigate this issue.

I don't see why this would be needed. If python gets fixed to use
Pre-Depends, then it does not matter whether libglib2.0-dev stops
depending on it, as python should then be always usable even when
just unpacked.

Thanks,
Guillem

Bug#874420: Testing migration of the fixed node-babel depends on nodejs migration

[Adrian Bunk]

Testing migration of the fixed node-babel depends on nodejs migration.

cu
Adrian

-- 

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

Bug#887865: shimdandy FTBFS with libclojure-java 1.9.0~alpha15-1

[Adrian Bunk]

Source: shimdandy
Version: 1.2.0-1
Severity: serious

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

...
[WARNING] The POM for org.clojure:clojure:jar:1.8.x is missing, no dependency 
information available
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] shimdandy-api .. SUCCESS [  2.595 s]
[INFO] shimdandy-impl . FAILURE [  0.013 s]
[INFO] shimdandy-parent ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.847 s
[INFO] Finished at: 2019-02-18T00:38:30-12:00
[INFO] Final Memory: 17M/591M
[INFO] 
[ERROR] Failed to execute goal on project shimdandy-impl: Could not resolve 
dependencies for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0: 
Cannot access central (https://repo.maven.apache.org/maven2) in offline mode 
and the artifact org.clojure:clojure:jar:1.8.x has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :shimdandy-impl
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/shimdandy-1.2.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/shimdandy-1.2.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/shimdandy-1.2.0/debian 
-Dmaven.repo.local=/build/1st/shimdandy-1.2.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2

Bug#887864: libint1 lost/renamed libraries without changing the package name

[Adrian Bunk]

Package: libint1
Version: 1.2.1-1
Severity: serious
Control: affects -1 src:ghemical

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

...
libtool: link: g++ -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -o ghemical fileio.o 
filetrans.o custom_app.o custom_camera.o custom_lights.o project.o spline.o 
pangofont_wcl.o oglview_wcl.o ac_stor_wcl.o p1dview_wcl.o p2dview_wcl.o 
eldview_wcl.o rcpview_wcl.o gpcview_wcl.o ogl_plane.o ogl_surface.o 
ogl_ribbon.o gtk_simple_dialogs.o gtk_glade_dialog.o gtk_file_export_dialog.o 
gtk_file_import_dialog.o gtk_geomopt_dialog.o gtk_moldyn_dialog.o 
gtk_progress_dialog.o gtk_setup_dialog.o gtk_stereo_dialog.o 
gtk_trajview_dialog.o gtk_wnd.o gtk_oglview_wnd.o gtk_p1dview_wnd.o 
gtk_p2dview_wnd.o gtk_eldview_wnd.o gtk_rcpview_wnd.o gtk_gpcview_wnd.o 
gtk_app.o gtk_project.o gtk_main.o -pthread -Wl,--export-dynamic -pthread  -lm 
-L/usr/X11R6/lib -lgthread-2.0 /usr/lib/x86_64-linux-gnu/libgtkglext-x11-1.0.so 
/usr/lib/x86_64-linux-gnu/libgdkglext-x11-1.0.so -lXmu -lXt -lSM -lICE 
-lpangox-1.0 -lX11 -lgmodule-2.0 -lglade-2.0 -lgtk-x11-2.0 -lgdk-x11-
 2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 
-lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig 
/usr/lib/x86_64-linux-gnu/libfreetype.so -lxml2 -lopenbabel -lghemical 
-lSCmbptr12 -lSCcints -lSCmbpt -lSCpsi -lSCdft -lSCscf -lSCwfn -lSCintv3 
-lSCbasis -lSCoint3 -lSCsolvent -lSCmolecule -lSCisosurf -lSCoptimize 
-lSCsymmetry -lSCscmat -lSCoptions -lSCgroup -lSCrender -lSCmisc -lSCstate 
-lSCkeyval -lSCclass -lSCcontainer -lSCref -lmopac7 -lGL -lGLU -loglappth 
-pthread
/usr/bin/ld: warning: libint-stable.so.1, needed by 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so, not found (try 
using -rpath or -rpath-link)
/usr/bin/ld: warning: libr12-stable.so.1, needed by 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so, not found (try 
using -rpath or -rpath-link)
/usr/bin/ld: warning: libderiv-stable.so.1, needed by 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so, not found (try 
using -rpath or -rpath-link)
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `init_libint'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `init_libint_base'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `build_eri'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `libint_storage_required'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `build_r12_grt'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `libr12_storage_required'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `free_libint'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `init_libr12'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `free_libr12'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib/libSCcints.so: undefined 
reference to `init_libr12_base'
collect2: error: ld returned 1 exit status
Makefile:571: recipe for target 'ghemical' failed
make[4]: *** [ghemical] Error 1

Processed: libint1 lost/renamed libraries without changing the package name

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ghemical
Bug #887864 [libint1] libint1 lost/renamed libraries without changing the 
package name
Added indication that 887864 affects src:ghemical

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

Processed: severity of 887789 is serious, usertagging 887789

[Debian Bug Tracking System]

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

> # missing dependencies is an RC bug
> severity 887789 serious
Bug #887789 [gitlint] gitlint: package should depend on python3-sh
Severity set to 'serious' from 'important'
> usertags 887789 + bittenby
User is p...@debian.org
There were no usertags set.
Usertags are now: bittenby.
> thanks
Stopping processing here.

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Andreas Beckmann]

Control: clone -1 -2
Control: retitle -2 libglib2.0-dev: needs dummy empty prerm
Control: reassign -2 libglib2.0-dev 2.54.2-1

>> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:>>> For 
>> now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
Even if python is going to get fixed, this probably won't help
libglib2.0-dev (which drops the python dependency in buster), therefore
it will need to add the dummy empty prerm to mitigate this issue.


Andreas

Processed: Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #887629 [python2.7-minimal,python3.6-minimal,debhelper] python: Wants to be 
used like Essential:yes but does not follow its requirements
Bug 887629 cloned as bug 887863
> retitle -2 libglib2.0-dev: needs dummy empty prerm
Bug #887863 [python2.7-minimal,python3.6-minimal,debhelper] python: Wants to be 
used like Essential:yes but does not follow its requirements
Changed Bug title to 'libglib2.0-dev: needs dummy empty prerm' from 'python: 
Wants to be used like Essential:yes but does not follow its requirements'.
> reassign -2 libglib2.0-dev 2.54.2-1
Bug #887863 [python2.7-minimal,python3.6-minimal,debhelper] libglib2.0-dev: 
needs dummy empty prerm
Bug reassigned from package 'python2.7-minimal,python3.6-minimal,debhelper' to 
'libglib2.0-dev'.
Ignoring request to alter found versions of bug #887863 to the same values 
previously set
Ignoring request to alter fixed versions of bug #887863 to the same values 
previously set
Bug #887863 [libglib2.0-dev] libglib2.0-dev: needs dummy empty prerm
Marked as found in versions glib2.0/2.54.2-1.

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

Bug#885525: nm-applet crashes when connecting to VPN

[Leonardo Franchi Zeclhynscki]

glad this is fixed, what is the ETA for it making to debian buster repos? 
should I install directly from sid?

Bug#886506: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Ben Hutchings]

On Wed, 17 Jan 2018 12:31:06 +0100 Aurelien Jarno  wrote:
[...]
> busybox is compiled with -mpreferred-stack-boundary=2 on i386 which has
> the same effect of reducing the default stack alignment from 16 bytes to
> 2 bytes. This comes from arch/i386/Makefile:

The argument is the log2 of the alignment, so this sets alignment to 4
bytes - which is compliant with the System V psABI for i386.

Any assumption of 16-byte stack alignment in glibc on i386 will break
not only busybox but most binaries built with old versions of gcc
(before 4.2, if the comment in busybox is correct).  So this really
ought to be fixed there.

I think that any libraries that need to maintain backward binary
compatibility will need to be compiled with the option
-mincoming-stack-boundary=2.  gcc will then fix up the stack alignment
in functions that need greater alignment for local variables.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.


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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Guillem Jover]

Control: reassign -1 python2.7-minimal,python3.6-minimal,debhelper
Control: retitle -1 python: Wants to be used like Essential:yes but does not 
follow its requirements
Control: affects -1 - libc6 libexpat1
Control: affects -1 + libglib2.0-dev

Hi!

On Sat, 2018-01-20 at 23:19:30 +0200, Niko Tyni wrote:
> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:
> > For now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
> > error starts to show up elsewhere (e.g. in a package where both old and
> > new prerm use python3), probably adding the Pre-Depends to libexpat1
> > would be the general solution.
> 
> FWIW, I have the feeling that having libexpat1 Pre-Depend:libc6 would
> be a wrong place to fix this longer-term, though it might be a viable
> workaround for now. I fear that this will pop up with zlib1g (another
> dependency of python3.5-minimal in stretch) next as soon as it gets built
> against a newer glibc version. And having special handling in libexpat1
> and zlib1g because they happen to be dependencies of python3.x-minimal
> seems wrong.

Yes.

> The core problem here is python3 usage in 'prerm upgrade'. Non-essential
> packages are not generally safe to use at that point. AFAICS, if
> python3.x-minimal is intended to be usable in 'prerm upgrade', it
> needs to follow the same rules as essential packages: "must supply
> all of their core functionality even when unconfigured" (policy 3.8).
> In practice I think that means it must Pre-Depend on all the libraries
> it links against, (so libexpat1 and zlib1g in addition to the current
> pre-dependency on libc.)

Exactly right. :) BTW this would require a discussion on debian-devel,
even though I guess it might not be controversial.

> [I don't know if even that is enough or if apt/dpkg give special treatment
> to packages tagged Essential:yes in this context.]

dpkg only takes Essential:yes into account on removal, when showing
its scary prompt; and when deconfiguring a package, to refuse the
action. AFAIR apt uses Essential:yes as things that need to
be installed (if they are not), for its own scary prompt, and to
prioritize its installation at the beginning of the transaction.

> Now, as we can't change python3 in stretch anymore, we can either push
> this down the chain in sid/buster and modify new libexpat1 and zlib1g to
> pre-depend on libc as a workaround, or we have to add fallback 'new-prerm
> failed-upgrade' handling to the packages whose 'prerm upgrade' in stretch
> is using python3.

I don't think this needs to be changed in stretch anyway? The new
dependencies on the newer libc are coming from sid/buster, so fixing
that should be enough, AFAICS (but I've not looked very hard :).

> I see the py3clean invocation is generated by dh_python3 so this is
> probably going to be much wider issue than just libglib2.0-dev...

I'm also assigning to debhelper, in case this needs mitigations there
too. Feel free to sort this out between yourselves, by reassigning,
cloning or whatever. ;)

Thanks,
Guillem

Processed: Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python2.7-minimal,python3.6-minimal,debhelper
Bug #887629 [apt,dpkg] libc6: bad upgrade path: libexpat1 unpacked and python3 
called before libc6 unpacked
Bug reassigned from package 'apt,dpkg' to 
'python2.7-minimal,python3.6-minimal,debhelper'.
Ignoring request to alter found versions of bug #887629 to the same values 
previously set
Ignoring request to alter fixed versions of bug #887629 to the same values 
previously set
> retitle -1 python: Wants to be used like Essential:yes but does not follow 
> its requirements
Bug #887629 [python2.7-minimal,python3.6-minimal,debhelper] libc6: bad upgrade 
path: libexpat1 unpacked and python3 called before libc6 unpacked
Changed Bug title to 'python: Wants to be used like Essential:yes but does not 
follow its requirements' from 'libc6: bad upgrade path: libexpat1 unpacked and 
python3 called before libc6 unpacked'.
> affects -1 - libc6 libexpat1
Bug #887629 [python2.7-minimal,python3.6-minimal,debhelper] python: Wants to be 
used like Essential:yes but does not follow its requirements
Removed indication that 887629 affects libc6 and libexpat1
> affects -1 + libglib2.0-dev
Bug #887629 [python2.7-minimal,python3.6-minimal,debhelper] python: Wants to be 
used like Essential:yes but does not follow its requirements
Added indication that 887629 affects libglib2.0-dev

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Guillem Jover]

Hi!

On Thu, 2018-01-18 at 21:45:51 +0100, Aurelien Jarno wrote:
> On 2018-01-18 20:38, Julian Andres Klode wrote:
> > On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote:
> > > This failure is normal given libexpat1 requires the new libc which has
> > > not been unpacked yet.
> > 
> > Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
> > in preinst actions. The thing is that Depends only after postinst ordering,
> > not unpack ordering.
> 
> Well it's not the preinst script, but the prerm script. The problem is
> unpacking libexpat1 before libc6 breaks libexpat1 and not usable
> anymore.

Depends only applies at configure time, not unpack time anyway. In
addition in this case dpkg does not even know there's such dependency
because the new package does not depend on python any longer (and dpkg
only tests the dependencies of the new version not the old one).

> From what I understand from the debian-policy, a prerm script might
> consider that all the dependencies have been at least unpacked when
> called:
> 
> | "The package whose prerm is being called will be at least
> | “Half-Installed”. All package dependencies will at least be
> | “Half-Installed” and will have previously been configured and not
> | removed. If there was no error, all dependencies will at least be
> | “Unpacked”, but these actions may be called in various error
> | states where dependencies are only “Half-Installed” due to a
> | partial upgrade.

First, notice that half-installed is one state lower than unpacked. In
addition when it says that "All package dependencies will at least be
“Half-Installed” and will have previously been configured and not
removed.", this means that they will have been fully configured before
on any version, but not the depended-on version (if there's such
dependency now).

Thanks,
Guillem

Bug#887815: [Pkg-utopia-maintainers] Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

[Michael Biebl]

Control: reassign -1 network-manager
Control: found -1 1.10.2-1
Control: affects -1 network-manager-iodine

Hi Guido

Am 20.01.2018 um 13:58 schrieb Michael Biebl:
> Am 20.01.2018 um 12:09 schrieb Guido Günther:
>> /usr/include/libnm/nm-setting-tc-config.h:43:1: error: 'NMTCQdisc' is 
>> deprecated: Not available before 1.10.2
> 
> I suppose this is the problem in configure.ac
> 
> LIBNM_CFLAGS="$LIBNM_CFLAGS -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2"
> LIBNM_CFLAGS="$LIBNM_CFLAGS -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2"
> 
> This triggers a warning which together with Werror leads to the build
> failure.
> The pkg-utopia maintained VPN modules trigger this warning as well, but
> don't use Werror, so do not fail the build.

I poked NM upstream about this issue. They referred me to
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/libnm-core/nm-setting-tc-config.h?id=685cb5c88bf90b285a18a98a6bbeafa559938fee
which should solve this issue.
This will be part of the next NM release which should be anytime soon.

If the nm-iodine issue is pressing, I can cherry-pick this fix.
Otherwise I would just wait for 1.10.4.

Reassigning the bug accordingly.


Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-utopia-maintainers] Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 network-manager
Bug #887815 [src:network-manager-iodine] network-manager-iodine FTBFS with 
network-manager 1.10.2-1
Bug reassigned from package 'src:network-manager-iodine' to 'network-manager'.
No longer marked as found in versions network-manager-iodine/1.2.0-1.
Ignoring request to alter fixed versions of bug #887815 to the same values 
previously set
> found -1 1.10.2-1
Bug #887815 [network-manager] network-manager-iodine FTBFS with network-manager 
1.10.2-1
Marked as found in versions network-manager/1.10.2-1.
> affects -1 network-manager-iodine
Bug #887815 [network-manager] network-manager-iodine FTBFS with network-manager 
1.10.2-1
Added indication that 887815 affects network-manager-iodine

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

Processed: tagging 887735 ..., notfound 884027 in 44:17.08.3-2, found 884027 in 4:17.08.3-2 ...

[Debian Bug Tracking System]

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

> tags 887735 + sid buster
Bug #887735 [src:mpdecimal] mpdecimal FTBFS: not writing through dangling 
symlink 'debian/libmpdec-doc/usr/share/doc/libmpdec-doc/_static/doctools.js'
Added tag(s) sid and buster.
> retitle 885962 FTBFS on btrfs: Exception in thread "main" 
> java.lang.AssertionError: expected:<2> but was:<1>
Bug #885962 {Done: Andreas Tille } [src:libsis-base-java] 
FTBFS: Exception in thread "main" java.lang.AssertionError: expected:<2> but 
was:<1>
Changed Bug title to 'FTBFS on btrfs: Exception in thread "main" 
java.lang.AssertionError: expected:<2> but was:<1>' from 'FTBFS: Exception in 
thread "main" java.lang.AssertionError: expected:<2> but was:<1>'.
> notfound 884027 44:17.08.3-2
Bug #884027 {Done: Pino Toscano } [marble-qt,marble-data] 
marble-qt: Update pulls in 81 MB of KDE (libkf5*) libraries despite package 
description says "no KDE dependencies"
There is no source info for the package 'marble-qt' at version '44:17.08.3-2' 
with architecture ''
There is no source info for the package 'marble-data' at version '44:17.08.3-2' 
with architecture ''
Unable to make a source version for version '44:17.08.3-2'
No longer marked as found in versions 44:17.08.3-2.
> found 884027 4:17.08.3-2
Bug #884027 {Done: Pino Toscano } [marble-qt,marble-data] 
marble-qt: Update pulls in 81 MB of KDE (libkf5*) libraries despite package 
description says "no KDE dependencies"
Marked as found in versions marble/4:17.08.3-2.
> reassign 887668 src:linux 4.14~rc3-1~exp1
Bug #887668 [linux-image-4.14.0-rc3-amd64] linux-image-4.14.0-rc3-amd64: 
MosChip MCS9922 serial+parallel port PCI-e card no longer working
Warning: Unknown package 'linux-image-4.14.0-rc3-amd64'
Bug reassigned from package 'linux-image-4.14.0-rc3-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.14~rc3-1~exp1.
Ignoring request to alter fixed versions of bug #887668 to the same values 
previously set
Bug #887668 [src:linux] linux-image-4.14.0-rc3-amd64: MosChip MCS9922 
serial+parallel port PCI-e card no longer working
Marked as found in versions linux/4.14~rc3-1~exp1.
> reassign 885775 src:linux 4.14.7-1
Bug #885775 [linux-image-4.14.0-2-amd64] apparmor: Apparmor triggers NULL 
pointer dereference in kernel 4.14.7-1 when updating with aptitude
Warning: Unknown package 'linux-image-4.14.0-2-amd64'
Bug reassigned from package 'linux-image-4.14.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.14.7-1.
Ignoring request to alter fixed versions of bug #885775 to the same values 
previously set
Bug #885775 [src:linux] apparmor: Apparmor triggers NULL pointer dereference in 
kernel 4.14.7-1 when updating with aptitude
Marked as found in versions linux/4.14.7-1.
> thanks
Stopping processing here.

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

Bug#887585: marked as done (stealth: missing build dependency on texlive-latex-extra)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 22:50:37 +
with message-id 
and subject line Bug#887585: fixed in stealth 4.01.10-1
has caused the Debian Bug report #887585,
regarding stealth: missing build dependency on texlive-latex-extra
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.)


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

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

...
No post-processing required for this latex conversion
cp stealth.sty ../../tmp/manual/LaTeX
latex stealth.latex
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./stealth.latex
LaTeX2e <2017-04-15>
Babel <3.16> and hyphenation patterns for 3 language(s) loaded.
Original Yodl file: ../../release.yo
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.sty
This is `epsf.tex' v2.7.4 <14 February 2011>
) (./stealth.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

Package hyperref Warning: Values of option `pdfpagemode':
(hyperref)* `UseNone'
(hyperref)* `UseOutlines'
(hyperref)* `UseThumbs'
(hyperref)* `FullScreen'
(hyperref)* `UseOC' (PDF 1.5)
(hyperref)* `UseAttachments' (PDF 1.6)
(hyperref)* An empty value disables the option.
(hyperref)Unknown value `None' on input line 4374.

(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))

Package hyperref Message: Driver (default): hdvips.

(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))

! LaTeX Error: File `makecell.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
! Emergency stop.
 
 
l.23 ^^M
--- End Message ---
--- Begin Message ---
Source: stealth
Source-Version: 4.01.10-1

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

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated stealth 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: Thu, 18 Jan 2018 13:12:32 +0100
Source: stealth
Binary: stealth stealth-doc
Architecture: source amd64 all
Version: 4.01.10-1
Distribution: unstable
Urgency: low
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Description:
 stealth- stealthy File Integrity Checker
 stealth-doc - stealthy File Integrity Checker documentation
Closes: 887585
Changes:
 stealth (4.01.10-1) unstable; urgency=low
 .
   * Added texlive-latex-extra to 'control' and updated required versions.
 (Closes: #887585).
   * Updated debhelper version in 'compat' to use DH 11.
   * Updated copyright info in 'copyright'
   * Bump Standards-Version to 4.1.3.
Checksums-Sha1:
 f05c28c9db3942715dc5c978711fc0a92f37581a 2266 

Bug#866458: marked as done (pydicom: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 22:35:45 +
with message-id 
and subject line Bug#866458: fixed in pydicom 0.9.9-3
has caused the Debian Bug report #866458,
regarding pydicom: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pydicom
Version: 0.9.9-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: pydicom
Source-Version: 0.9.9-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pydicom 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, 20 Jan 2018 23:07:33 +0100
Source: pydicom
Binary: python-dicom python3-dicom python-dicom-doc
Architecture: source
Version: 0.9.9-3
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 python-dicom - DICOM medical file reading and writing (Python 2)
 python-dicom-doc - DICOM medical file reading and writing (documentation)
 python3-dicom - DICOM medical file reading and writing (Python 3)
Closes: 782928 866458
Changes:
 pydicom (0.9.9-3) unstable; urgency=medium
 .
   * Team upload.
   * Replace python-imaging by python-pil
 Closes: #866458
   * Packae just supports Python3 - thus close bug
 Closes: #782928
   * Secure URI in watch file
   * Standards-Version: 4.1.3
   * Secure Vcs-Git
   * Fix path in copyright
Checksums-Sha1:
 b3498b4e0a4b2edccdcb2d0e34533501aaf0bcd1 2188 pydicom_0.9.9-3.dsc
 5ec5f57467767eee056bc7a68a74191ecb97b78c 4668 pydicom_0.9.9-3.debian.tar.xz
 60d60fb8558b8a416be1742f48004664c9062d16 14976 pydicom_0.9.9-3_source.buildinfo
Checksums-Sha256:
 a2912866e1e74756fbd12dad02150e3d3d0baa397a02f4994f39502288650fd2 2188 
pydicom_0.9.9-3.dsc
 f8a1309a98e8f5d2dc8376d0b24a5e202aa444b5cceace5e2f5650063a2db8ea 4668 
pydicom_0.9.9-3.debian.tar.xz
 3626314763433d57b9866add0a54062bf50774c1f8367cec9ef0870e1886 14976 
pydicom_0.9.9-3_source.buildinfo
Files:
 63f7ab23321492ba2d8817a1cfea2615 2188 python optional pydicom_0.9.9-3.dsc
 b651302f5708647a1e513c9fbea504a2 4668 python optional 
pydicom_0.9.9-3.debian.tar.xz
 60e5037a40687dac80d9afdbec89e46b 14976 python optional 
pydicom_0.9.9-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlpjvo4OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGdLA//VPmr125GyGDYeKPlCKGLSw+EHxC9FiLkqjU2
FeSVES6WgIlqOMuoKnFZZLKdca4EuBnySnrmD8yMDDP3ObjcVUhQXMoozujxSdq8
oBZceIC2yrCljQyNjY8qSfntEiYZhtKNBoq6eQsdhQ18Yd1Qxx+hVormdk9/B8N0
KR8a2G9HvCK6I7vykM9YQntOAFHa9W35fQUrXb18xDJWuYRzjzF30QrVxh+xLJ+b
GqDSOVb8MVgfBe0lnnpSCl7g2no1lOZQ+V0XOT3aYaSqeGxApHN22Efnpd+0rDSy
/6Q+th9MifJMDVQPnWt6DIqMmo1gDVMg1+TpQEkTz3OXmf0YY93I94+HPs6yEzxW
Q7q6MTIcjVSsDrROGI8z5pQ1NpOx00VVLMdM8St/PRQi0uGXGhvSo7/Zmx9OduyB
V3/h5Ttw8fmTVVzQrHJxTrwAX/38nKli4mVXWpiD/8xiIo7wKLZ0GoBM2v/ik0Fq
Y11/MjdjGlv//JcSYxD4SvQOK808oopB+QMKHdCEd+OLu5DBdIG4HJ1hlup97RAN
cNNJpRNg9O3Qc64EcdiKD+ya27L6Wj/1LzCda1W6Fuvof8VQ3L4HYzUNtSyKvTGK
qbdbpUDAWuOX5IClNiHUZvFBuXld7pb8i5ZmtZ6kwZfketV6XNIsERzfsHHKObU5
qTes988=
=dUp8
-END PGP SIGNATURE End Message ---

Bug#887807: marked as done (natlog FTBFS with yodl 4.02.00-2)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 22:19:53 +
with message-id 
and subject line Bug#887807: fixed in natlog 1.03.01-1
has caused the Debian Bug report #887807,
regarding natlog FTBFS with yodl 4.02.00-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.)


-- 
887807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: natlog
Version: 1.03.00-2
Severity: serious

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

...
yodl2man  -o ../../tmp/man/natlog.1 natlog
Yodl2man 4.02.00
Yodl: including file ../../release.yo
natlog.yo:30: DEFINEMACRO: `tr' multiply defined
Yodl is processing a(n) article
Error(s) detected
/usr/bin/yodl indicates failure!
Fatal: system - failure of system call (status 256)
debian/rules:25: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: natlog
Source-Version: 1.03.01-1

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated natlog 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, 20 Jan 2018 13:08:11 -0800
Source: natlog
Binary: natlog
Architecture: source amd64
Version: 1.03.01-1
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: tony mancill 
Description:
 natlog - Source-natting firewall logging utility
Closes: 887807
Changes:
 natlog (1.03.01-1) unstable; urgency=medium
 .
   [ Frank B. Brokken ]
   * New upstream version 1.03.01
   * Upstream fixed doubly defined Yodl documentation macro (Closes: #887807).
   * Updated `control' and `compat' for DH 11.
   * Bump Standards-Version to 4.1.3
 .
   [ tony mancill ]
   * Use DH sequencer in debian/rules
Checksums-Sha1:
 90acc39e634030e3c35c26d3996b2276e9df4163 2048 natlog_1.03.01-1.dsc
 0768f2a1930ffac814a766424d404ebff3d9a2e8 304563 natlog_1.03.01.orig.tar.gz
 1cc4fc694cf6b225079dd4d4bb054c647260305a 7452 natlog_1.03.01-1.debian.tar.xz
 b4a1fc43ef854f80bc4e7fd327dba8c6d2998292 1902040 
natlog-dbgsym_1.03.01-1_amd64.deb
 238f155a23e1712e26419b7094ebd3ad9bf5a034 6000 natlog_1.03.01-1_amd64.buildinfo
 c57fcc355ee24b94a664949277d8bdf8a66723d0 51416 natlog_1.03.01-1_amd64.deb
Checksums-Sha256:
 6fa51f94ac70b25bb5846e97ca2984135781a1deaf19159ddc0f83eea3684e42 2048 
natlog_1.03.01-1.dsc
 9c7d8e80022c3e97ba8881b1d7e0221649c7eccc33ad56be8e7a7f3771bc16dc 304563 
natlog_1.03.01.orig.tar.gz
 ac420c422617cd2fd18acf35f11c281ebea218f6f15e9cfa60862a77fbeebd32 7452 
natlog_1.03.01-1.debian.tar.xz
 c7ed75bcdf2cc88f2b24464c89dbfee09e9f8aae48d626ef3f3504199470409c 1902040 
natlog-dbgsym_1.03.01-1_amd64.deb
 751c0c5b6c66585108f418220d8b0cdba4cb026345304db78c79501f3e1ee1b1 6000 
natlog_1.03.01-1_amd64.buildinfo
 872a0868956b276b22421896d62ff870e7bfe3374a367f26a7f15481d3505671 51416 
natlog_1.03.01-1_amd64.deb
Files:
 3decb7b1ad9a2d0ff3e4ab8c3d808377 2048 devel optional natlog_1.03.01-1.dsc
 ed90883b445b433c510d2c358f3f96a4 304563 devel optional 
natlog_1.03.01.orig.tar.gz
 515d7288e921dc0b3ceb4dc52030c07c 7452 devel optional 
natlog_1.03.01-1.debian.tar.xz
 3d0aabefb11a8997ce46e85b02b41e3d 1902040 debug optional 
natlog-dbgsym_1.03.01-1_amd64.deb
 aac0d5a6d5546f26053d5bea39c80e52 6000 devel optional 
natlog_1.03.01-1_amd64.buildinfo
 c1e6fb4022c09c248436654d9f610d6c 51416 devel optional 
natlog_1.03.01-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlpjvXgUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbkyxAAvlJz88vXo0QdLUZqcYNhjYMfTb0z
mXMZ/reZ+hQaCN9lGiC8w8OBnr7lTZHmwSW9RogqGQK7E6PU66tK+NUPK5oO4a//
YdViZY5D6JJYy5yShvOP+uEPGqm1BLnpAEXDviehpQawph5Fow/GI0tf3zC7vUpA
NhA6THiV44CayjvEzFaizqksNbB1BMIE6tVDl8UqJfKJdqEorwi4yWWPkFmXvxsY
GNxwqNPb1Bwgz683tlEMGTFSMtyqRVtAzkiEVIRu0wtmntUHQHXOfduqv+CeZWsw
kebrYhPeb4gBMakz1oYdwIWrN1QJzcCFkBOS9hhH8MI4LGVjwWx5jNcyXXLtIr7I

Processed: Pending fixes for bugs in the zookeeper package

[Debian Bug Tracking System]

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

> tag 870271 + pending
Bug #870271 [src:zookeeper] zookeeper: insecure permissions of 
/var/lib/zookeeper
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870271: Pending fixes for bugs in the zookeeper package

[pkg-java-maintainers]

tag 870271 + pending
thanks

Some bugs in the zookeeper package are closed in revision
6bce520e5f862a626a697a25ac583bec9eb4 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/zookeeper.git/commit/?id=6bce520

Commit message:

/var/lib/zookeeper is no longer world-readable (Closes: #870271)

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Niko Tyni]

On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:

> For now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
> error starts to show up elsewhere (e.g. in a package where both old and
> new prerm use python3), probably adding the Pre-Depends to libexpat1
> would be the general solution.

FWIW, I have the feeling that having libexpat1 Pre-Depend:libc6 would
be a wrong place to fix this longer-term, though it might be a viable
workaround for now. I fear that this will pop up with zlib1g (another
dependency of python3.5-minimal in stretch) next as soon as it gets built
against a newer glibc version. And having special handling in libexpat1
and zlib1g because they happen to be dependencies of python3.x-minimal
seems wrong.

The core problem here is python3 usage in 'prerm upgrade'. Non-essential
packages are not generally safe to use at that point. AFAICS, if
python3.x-minimal is intended to be usable in 'prerm upgrade', it
needs to follow the same rules as essential packages: "must supply
all of their core functionality even when unconfigured" (policy 3.8).
In practice I think that means it must Pre-Depend on all the libraries
it links against, (so libexpat1 and zlib1g in addition to the current
pre-dependency on libc.)

[I don't know if even that is enough or if apt/dpkg give special treatment
to packages tagged Essential:yes in this context.]

Now, as we can't change python3 in stretch anymore, we can either push
this down the chain in sid/buster and modify new libexpat1 and zlib1g to
pre-depend on libc as a workaround, or we have to add fallback 'new-prerm
failed-upgrade' handling to the packages whose 'prerm upgrade' in stretch
is using python3.

I see the py3clean invocation is generated by dh_python3 so this is
probably going to be much wider issue than just libglib2.0-dev...

Just my two cents,
-- 
Niko Tyni   nt...@debian.org

Bug#886922: marked as pending

[Mike Gabriel]

tag 886922 pending
thanks

Hello,

Bug #886922 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-remote/arctica-greeter.git/commit/?id=66674a9

---
commit 66674a9ab24236f710dce6e1f0789f013da5f8cb
Merge: db0ec51 918c251
Author: Mike Gabriel 
Date:   Sat Jan 20 21:51:21 2018 +0100

Merge branch 'master' into debian/stretch/backports

diff --cc debian/changelog
index dca0318,b3fbdfd..01253c8
--- a/debian/changelog
+++ b/debian/changelog
@@@ -1,9 -1,13 +1,19 @@@
+ arctica-greeter (0.99.0.2-2) unstable; urgency=medium
+ 
+   * debian/arctica-greeter-guest-session.install:
+ + Add EOL at EOF.
+   * debian/arctica-greeter-theme-debian.post*:
+ + Drop postinst/postrm script. For glib-compile-schemas we have a trigger
+   in libglib2.0-bin since 2010. (Closes: #886922).
+ 
+  -- Mike Gabriel   Sun, 14 Jan 2018 22:25:54 +0100
+ 
 +arctica-greeter (0.99.0.2-1~bpo9+1) stretch-backports; urgency=medium
 +
 +  * Rebuild for stretch-backports.
 +
 + -- Mike Gabriel   Fri, 05 Jan 2018 01:00:13 +0100
 +
  arctica-greeter (0.99.0.2-1) unstable; urgency=medium
  
* Initial release to Debian. (Closes: #879650).

Processed: Bug#886922 marked as pending

[Debian Bug Tracking System]

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

> tag 886922 pending
Bug #886922 {Done: Mike Gabriel } 
[arctica-greeter-theme-debian] arctica-greeter-theme-debian: fails to purge: 
arctica-greeter-theme-debian.postrm: glib-compile-schemas: not found
Ignoring request to alter tags of bug #886922 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Re: gxineplugin: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending patch
Bug #886947 [gxineplugin] gxineplugin: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added tag(s) pending and patch.

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

Bug#886947: gxineplugin: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Followup-For: Bug #886947
Control: tag -1 pending patch

commit pushed to the GIT repo, but since I don't know how to update the
libmozjs B-D properly, I'm not going to upload it.


Andreas

Bug#886581: marked as done (do not transition; errors in the dependency chain)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 15:29:15 -0500
with message-id 

Bug#886799: fixing openafs kernel module for security updated kernel

[Benjamin Kaduk]

The SRU request for jessie is in #887857.

I don't think there is a way to get a fix into jessie-backports, so
I think we will need to remove openafs-modules-source and
openafs-modules-dkms from jessie-backports and pull the version from
buster into jessie-backports-sloppy (which will be a trip through
NEW and require a DD sponsor, since I'm only a DM).

I'm still looking at wheezy.

-Ben

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

[Julien Aubin]

Package: intel-microcode
Version: 3.20171117.1~bpo9+1
Severity: critical
Tags: security
Justification: root security hole

Hi,

As of now intel-microcode of stretch is still set to 20170707 (20171117
through
bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could you
please bring quickly the microcode update to stretch, at least on bpo ?

Thanks a lot



-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages intel-microcode depends on:
ii  iucode-tool  2.1.1-1

Versions of packages intel-microcode recommends:
ii  initramfs-tools  0.130

intel-microcode suggests no packages.

-- no debconf information

Bug#884290: marked as done (zfsnap: depends on nonfree zfsutils-linux (favored over zfs-fuse))

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 19:06:27 +
with message-id 
and subject line Bug#884290: fixed in zfsnap 1.11.1-5.1
has caused the Debian Bug report #884290,
regarding zfsnap: depends on nonfree zfsutils-linux (favored over zfs-fuse)
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.)


-- 
884290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfsnap
Version: 1.11.1-5
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

zfsnap depends on zfsutils-linux | zfsutils | zfs-fuse | zfs.

zfsutils-linux is nonfree and therefore not allowed to be listed as
dependency of a package in main, according to Debian Policy §2.2.1.

zfsutils is a virtual package apparently provided only by zfsutils-linux
and therefore not allowed either.

zfs is apparently a non-existent package.

Please either remove dependency on zfsutils-linux and zfsutils (maybe
instead listing those as suggests), or move this package to contrib.

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloxHlMACgkQLHwxRsGg
ASEzgw/+NLIDfkYRMl9YZGX5btLbJQlnbwMwNAuyUdmws1Sl4fxltYAEhkuaqOsS
pHCqCnb8lRZ+fHwDAdDOu30+azLVhM5epi7pGI+eMwF7iJ2uxK9VBS81ZzdW8gf8
m6jG4WpqmrAHKprKpfa10h58pYoio54y4pvRdmmxzUD1/WMV2ftUGRIKnmvdTlot
LNIzA7QJG7fTUDAiHv8UoYdXYpLbud3vRMVpkdvGVWYQVgT6u/5ggthqO8z0tSDA
BoEqluQEbg7cOlLbBY4OwxinedarOLoXGA2z6DDjKW+F4u/EclJKO92gX8dA20zP
WPfES3Ot6jWMCw1zzYtsXp+YSf/GFQq/VGnZIwwvD4P0WnydkdpPGg36xN3FWMY3
GPAxi8ZpkDdbDbg1bKa6pmujD0PBSuUpYcvtkSKxu6ijfqWb0t6oojW7/EVfxK4G
dH+LXJccWSn3wITYIODZFl7u28iSrcZtDdkAgVh2UjFFDqWdMWIZyQ1Z2D5HAKX4
qf0FfGXIRhvy9CcuSP1RDdqvXD5PCh0jdegUwnWFu3tnEaaWXINjnfURWxE5CuJZ
V2Uop79+JDNYWvR47SP0KU51g0wlKCDJ1MuXUh239I75bgdvomhSdTJWOWaJgzuC
TGj54CEv02RRZuw6c9MXWyQMwaepD8RF45mXzKE/Q2XeooTwDBQ=
=fkOJ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: zfsnap
Source-Version: 1.11.1-5.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated zfsnap 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, 10 Jan 2018 20:17:40 +0200
Source: zfsnap
Binary: zfsnap
Architecture: source
Version: 1.11.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: Adrian Bunk 
Description:
 zfsnap - Automatic snapshot creation and removal for ZFS
Closes: 884290
Changes:
 zfsnap (1.11.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Correct the order of dependencies to list
 zfs-fuse (in main) first. (Closes: #884290)
Checksums-Sha1:
 863fa62e43d31946eb8dae01429a162171671aff 1781 zfsnap_1.11.1-5.1.dsc
 bdee07e9f305b26bccf3af0325530f0775b4ada3 6741 zfsnap_1.11.1-5.1.diff.gz
Checksums-Sha256:
 b52bc1fbc624dfdc0501b96352ed643d729ccd508d5b50fa201f68a4a3119773 1781 
zfsnap_1.11.1-5.1.dsc
 dee4c7677f478adb30f0e44b45ef451af592ad2c320d41ec37f336a00a0f160c 6741 
zfsnap_1.11.1-5.1.diff.gz
Files:
 5df4fada8c7215f14989fcb3ffedfc25 1781 admin extra zfsnap_1.11.1-5.1.dsc
 e3880cd8b91ea5b32fd6bc2d3b6fdd92 6741 admin extra zfsnap_1.11.1-5.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpWW3IACgkQiNJCh6LY
mLEScA/+P0MqJ5nwtO4urxQBaDEQd4Z0oZl22DqkatWAI+ejzr9jib7rbPugoMvt
lY1qaw/X+7gD8VQOeOvjeWwbo/DPdFswNEOq5isoZhkXwE5CJK+y24udskSj8Jq1
vQXz8SHV5O9qCVJiNyD7IbGFJ+Nyc+78M7bTOslU1SLm6wQAb7O6fSYZbI5ZBe0y
D112yVFvr2D36UvRDXYWlNXVeRxlsrdhkOBqQ/JoqiTXIK/C6mCro9DvrXxnqrZL
YiT7KTdvlQ5KTBX/+hpBCqWTbtfgTcaBiaylJEGNnrXFvym1vS16TVrLGN0d2jWS
1Adz3+E/CILb7QCYBmUBb+oXwcFE61gsRdXik+C7Z20CT+6FsPSvOzQ2GzOYMJcQ
SL8w/nPe/MEabxGFTbDR3p61kBKsV4P+LBC2jdfIXHP/i/2Y8o5kSD0fCXQHAW/9
Ysg0suIT/QPWSHRoEmvTNFJXQJxTS+Uk6pGbikSUsxofQbGfh9PPL+XEHRHPswdy
46hgnASHEPsuOBMvLChTboC2u1u3usnNdmB1cpTz8OrY6HZ+AuFP9thKcsLFIQK7
Y8AjG+aNlZUf2mGnfsCf/u4usFwGH7i209ORkul0ZMUaRw5/Dh0gT/TZ7LY8BRKi

Bug#887727: marked as done (debhelper,dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*))

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 18:49:23 +
with message-id 
and subject line Bug#887727: fixed in debhelper 11.1.3
has caused the Debian Bug report #887727,
regarding debhelper,dh-dist-zilla: dh-dist-zilla based package builds no more 
run dh_auto_install (and maybe other dh_auto_*)
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.)


-- 
887727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper,dh-dist-zilla
Version: debhelper/10.10.6
Severity: serious
Tags: sid buster
Control: affects -1 src:roary src:systray-mdstat

Hi,

Sascha Steinbiss  (X-Debbugs-Cc'ed) made me aware
that at least two dh-dist-zilla based source packages (roary and
systray-mdstat) produce more or less empty packages when build now
(but don't FTBFS and in case of systray-mdstat not even throw a single
lintian warning).

An DH_VERBOSE=1 build log reveals that dh_auto_install is no more
called in the build. (This probably also counts for other dh_auto_*
scripts.) This smells a lot like being caused by this change in
debhelper/10.10.6 (uploaded November 2017, i.e. shortly after the
latest uploads of the two mentioned packages):

  * dh,dh_auto_*: Support skipping all of the dh_auto_* helpers if the
package does not seem to have a build system (and there are no
build system related options passed to dh).

Which is this commit:
https://anonscm.debian.org/git/debhelper/debhelper.git/commit/?id=52bf7ef7

Reverting this commit fixes the issue as dh_auto_install is called
again.

So I now wonder:

* Is this a bug in debhelper? I.e. does the new (additional?)
  buildsystem detection not work properly?

* Or is this a bug in dh-dist-zilla and it should have declared
  something in
  /usr/share/perl5/Debian/Debhelper/Sequence/dist_zilla.pm
  which wasn't relevant yet, but is now?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.1.3

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 20 Jan 2018 18:26:06 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.1.3
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 446856 873831 887727
Changes:
 debhelper (11.1.3) unstable; urgency=medium
 .
   * autoscripts/*: Improve rollback handling of many scripts.
 Notably a lot of scripts failed to rerun the postinst parts
 on an "abort-upgrade".  (Closes: #446856)
   * debian/control: Add a Breaks on meson to ensure that we have
 meson (>= 0.40.0) as the meson build system uses --wrap-mode.
 This is mostly relevant for backports.
   * Dh_Lib.pm: When printing commands (e.g. for doit), also show
 changes to the environment (when done as a part of the
 command).
   * ninja.pm: Set LC_ALL=C.UTF-8 when calling ninja to avoid
 meson choking on UTF-8 characters when it embeds itself into
 e.g. the build or install.  (Closes: #873831)
   * dh: Remove the assumption that sequences will supply only
 "safe no-op" parameters to commands.  Thanks to Axel Beckert
 and Sascha Steinbiss for the report.  (Closes: #887727)
Checksums-Sha1:
 9adce9426bda8c3414c3ddbaa803dd2f665ff2d8 1781 debhelper_11.1.3.dsc
 

Bug#887797: marked as done (libgaminggear-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/libgaminggear)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 17:51:09 +
with message-id 
and subject line Bug#887797: fixed in libgaminggear 0.15.1-5
has caused the Debian Bug report #887797,
regarding libgaminggear-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc-base/libgaminggear
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.)


-- 
887797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgaminggear-doc
Version: 0.15.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libgaminggear-doc.
  Preparing to unpack .../5-libgaminggear-doc_0.15.1-4_all.deb ...
  Unpacking libgaminggear-doc (0.15.1-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gCm8r9/5-libgaminggear-doc_0.15.1-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/libgaminggear', which is also in 
package libgaminggear-dev:amd64 0.15.1-3
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-gCm8r9/5-libgaminggear-doc_0.15.1-4_all.deb


cheers,

Andreas


libgaminggear-dev=0.15.1-3_libgaminggear-doc=0.15.1-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libgaminggear
Source-Version: 0.15.1-5

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated libgaminggear 
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, 20 Jan 2018 18:20:45 +0100
Source: libgaminggear
Binary: libgaminggear-dev libgaminggear-doc libgaminggear0 libgaminggear-common 
gaminggear-utils
Architecture: source
Version: 0.15.1-5
Distribution: unstable
Urgency: medium
Maintainer: Pierre-Elliott Bécue 
Changed-By: Pierre-Elliott Bécue 
Description:
 gaminggear-utils - Utilities from libgaminggear
 libgaminggear-common - Functionalities for gaming input devices, common files
 libgaminggear-dev - Functionalities for gaming input devices (devel)
 libgaminggear-doc - Functionalities for gaming input devices (documentation)
 libgaminggear0 - Functionalities for gaming input devices
Closes: 887797
Changes:
 libgaminggear (0.15.1-5) unstable; urgency=medium
 .
   * d/control:
 - Add a missing Breaks+Replaces reference on -doc package regarding files
   previously in -dev package. (Closes: #887797)
Checksums-Sha1:
 36e3465f8abb41b1b7345d3ef97cce0f963f87a3 2361 libgaminggear_0.15.1-5.dsc
 16530767da68c129638b33296af2188df4fd6a48 13652 
libgaminggear_0.15.1-5.debian.tar.xz
 237c43d3c5fe6233dfe17a1e21908026e3f2c22b 12951 
libgaminggear_0.15.1-5_amd64.buildinfo
Checksums-Sha256:
 1feaf57d3595fe1583794f2a918d38aeb52bcf7469686d6c818914c52d6bd154 2361 
libgaminggear_0.15.1-5.dsc
 44b49effafcb50c37ab44f5dcf3b4f225e37041c84e1e370118b3aca954f3e8d 13652 
libgaminggear_0.15.1-5.debian.tar.xz
 b343ec84388f24b11cb8e7c6f0662e9d60bb9252c315dc5e710d997ae4f4 12951 
libgaminggear_0.15.1-5_amd64.buildinfo
Files:
 30424d03210eacf17076fcc6197a2e69 2361 libs optional libgaminggear_0.15.1-5.dsc
 6d5f732d674de54a82d8ee9803bbf41e 13652 libs optional 
libgaminggear_0.15.1-5.debian.tar.xz
 1bfebd860cd88ac9575056e9237ceb9d 12951 libs optional 
libgaminggear_0.15.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAlpjetAACgkQKb+g0Hkp
Csr9vQ//Ub8wMYNWP8tO9YvQmBhhHr1qvLSUKO1dysQAD3hxqZnj59XgCCEaJbfD
0ET0rF/v9H7HXAJkv1ZKy7pMGQFWvNtKqVOSvQM06QSbxDFXpKXrQKeSiXJ+b14m

Bug#887797: libgaminggear-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/libgaminggear

[Pierre-Elliott Bécue]

Le samedi 20 janvier 2018 à 01:24:53+0100, Andreas Beckmann a écrit :
> Package: libgaminggear-doc
> Version: 0.15.1-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libgaminggear-doc.
>   Preparing to unpack .../5-libgaminggear-doc_0.15.1-4_all.deb ...
>   Unpacking libgaminggear-doc (0.15.1-4) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-gCm8r9/5-libgaminggear-doc_0.15.1-4_all.deb (--unpack):
>trying to overwrite '/usr/share/doc-base/libgaminggear', which is also in 
> package libgaminggear-dev:amd64 0.15.1-3
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-gCm8r9/5-libgaminggear-doc_0.15.1-4_all.deb

Oops, my bad, sorry for the mess.

Fixing it in a new release.

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2


signature.asc
Description: PGP signature

Bug#887612: marked as done (libvirt-daemon-system: prompting due to modified conffiles which were not modified by the user: /etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 17:06:15 +
with message-id 
and subject line Bug#887612: fixed in libvirt 4.0.0-1
has caused the Debian Bug report #887612,
regarding libvirt-daemon-system: prompting due to modified conffiles which were 
not modified by the user: /etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper
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.)


-- 
887612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon-system
Version: 4.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up libvirt-daemon-system (4.0.0~rc1-1) ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/libvirt-qemu ...
  
  Configuration file '/etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** usr.lib.libvirt.virt-aa-helper (Y/I/N/O/D/Z) [default=N] ? dpkg: error 
processing package libvirt-daemon-system (--configure):
   end of file on stdin at conffile prompt
  Errors were encountered while processing:
   libvirt-daemon-system

This was encountered on a sid -> experimental upgrade.


cheers,

Andreas


libvirt-daemon-system_4.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.0.0-1

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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, 20 Jan 2018 16:31:11 +0100
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 libnss-libvirt - nss plugin providing IP add ress resolution for virtual 
machines
 libvirt-clients - Programs for the libvirt library
 libvirt-daemon - Virtualization daemon
 libvirt-daemon-driver-storage-gluster - Virtualization daemon glusterfs 
storage driver
 libvirt-daemon-driver-storage-rbd - Virtualization daemon RBD storage driver
 libvirt-daemon-driver-storage-sheepdog - Virtualization daemon Sheedog storage 
driver
 

Bug#883785: marked as done (libvirtd crashes when starting a vm with IDE cdrom)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 17:06:15 +
with message-id 
and subject line Bug#881293: fixed in libvirt 4.0.0-1
has caused the Debian Bug report #881293,
regarding libvirtd crashes when starting a vm with IDE cdrom
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.)


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

Package: libvirt
Version: 3.10
Severity: grave

With libvirt version 3.10 I cannot start a VM. Reverting to 3.0
(Debian/stable) all is fine. This was initially found in GNOME-Boxes
but I have been able to reproduce on the command line using virsh.

Note also that I had the same issue with 3.9.

On one console:

$ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd

On a second console, I tried to start the VM:

$ virsh start boxes-winxp

Then I got this exception from libvirtd:

Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7febad4a5700 (LWP 7867)]
0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
(gdb) bt
#0  0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
#1  0x7feb7d266da3 in qemuDomainDetermineDiskChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#2  0x7feb7d28eec2 in qemuProcessPrepareHost ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#3  0x7feb7d294b71 in qemuProcessStart ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#4  0x7feb7d2f5201 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#5  0x7feb7d2f58e6 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#6  0x7febb9e5e077 in virDomainCreate (domain=0x7feb980008c0)
at ../../../src/libvirt-domain.c:6531
#7  0x56190ba2ed9c in ?? ()
#8  0x7febb9ec697c in virNetServerProgramDispatchCall (msg=0x56190d9e7590, 
client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40)
at ../../../src/rpc/virnetserverprogram.c:437
#9  virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, 
client=0x56190d9e6fb0, msg=0x56190d9e7590)
at ../../../src/rpc/virnetserverprogram.c:307
#10 0x56190ba3e988 in ?? ()
#11 0x7febb9da1c01 in virThreadPoolWorker (
opaque=opaque@entry=0x56190d9ce9f0)
at ../../../src/util/virthreadpool.c:167
#12 0x7febb9da0f78 in virThreadHelper (data=)
at ../../../src/util/virthread.c:206
#13 0x7febb68b0519 in start_thread (arg=0x7febad4a5700)
at pthread_create.c:456
#14 0x7febb65f2a5f in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb) 

I noticed that running with 3.0 I had a message saying that /dev/sr0 is
not accessible. And indeed I do not have a CDROM on this machine. The
.xml were migrated from a machine with a CDROM to this new one.

Removing:


  
  
  
  
  


Seems to fix the issue. Yet, libvirt should not crash on this. And the
backtrace makes sense with this fix BTW.

Please let me know if you need additional information.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.0.0-1

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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, 20 Jan 2018 16:31:11 +0100
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev 

Bug#882618: marked as done (libdbix-class-schema-loader-perl: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 17:05:55 +
with message-id 
and subject line Bug#882618: fixed in libdbix-class-schema-loader-perl 0.07047-2
has caused the Debian Bug report #882618,
regarding libdbix-class-schema-loader-perl: Test failures
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.)


-- 
882618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbix-class-schema-loader-perl
Version: 0.07047-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=123681

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net [0], libdbix-class-schema-loader-perl's
test suite fails since recent changes in prerequsites. The same
happens during build which leads to a FTBFS bug:

DBIx::Class::ResultSource::schema(): Unable to perform storage-dependent 
operations with a detached result source (source 'Bar' is not associated with a 
schema). You need to use $schema->thaw() or manually set 
$DBIx::Class::ResultSourceHandle::thaw_schema while thawing. at 
t/20invocations.t line 18
# Looks like your test exited with 255 just after 7.
t/20invocations.t ... 
1..68
ok 1 - 'hardcode' isa 'DBIx::Class::Schema'
ok 2 - 'hardcode' isa 'DBIx::Class::ResultSet'
ok 3 - 'hardcode' isa 'DBICTest::Schema::_hardcode::Foo'
ok 4 - hardcode correct object
ok 5 - hardcode object created
ok 6 - No warnings during hardcode invocations
ok 7 - 'normal' isa 'DBIx::Class::Schema'
rmdir t/var/DDzUVkb6WU
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 61/68 subtests 

DBIx::Class::ResultSource::schema(): Unable to perform storage-dependent 
operations with a detached result source (source 'Bar' is not associated with a 
schema). You need to use $schema->thaw() or manually set 
$DBIx::Class::ResultSourceHandle::thaw_schema while thawing. at 
t/backcompat/0.04006/20invocations.t line 21
# Looks like your test exited with 255 just after 5.
t/backcompat/0.04006/20invocations.t  
1..32
ok 1 - 'hardcode' isa 'DBIx::Class::Schema'
ok 2 - 'hardcode' isa 'DBIx::Class::ResultSet'
ok 3 - hardcode
ok 4
ok 5 - 'normal' isa 'DBIx::Class::Schema'
rmdir t/var/BdN94D7OJ3
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 27/32 subtests 


While this is probably a bug in libhash-merge-perl (or one of its
dependencies), we have a problem here, and should update the
dependencies once it's fixed.


Cheers,
gregor


[0]
https://ci.debian.net/packages/libd/libdbix-class-schema-loader-perl/unstable/amd64/


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAloYlZxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYwzhAAxUrKJzSLaKMPQmrPVnau1NDrJBMRq4VcVcBBfFlwKul4f3hvSDIopGKO
JrQrqvq2Z53mwHAfMh1kCoCYUoQ3CDiQvsv5sPI1noKIRCBkebLne7kkxWIAMb5U
0TO4n/6nNMEF0lY4Ir2pUEaCC50/UuFRw8T+btb01gUcNP2TguTdvalM3YF+qSC/
YDHlYTnoIvB1gR/qpRvwxuIED0/mq3RiOsFdEJTAERJknlbpWkD4JZApXiAtOgeD
E0QQBJ3/+7Yk6qkgru/O+Gxb7gTpFW3Gur0C2uJ4UxMYt6xvZFysQHOU8GJzM+oC
RxgsMf96iLoF7IkMzChNmYVvbBgrjEuNOtEpYqPYvQk9ZcBVN6LY8JGXYhFCJcWk
rF1hZgjO7XOPNE0UrznPFqe36r5BKpfFIP7HqH2UdIBhTGBq8Xt33993SkQZ+1Pj
KEw3etFtPrI/H93LMRDnB09UlspJ+zRibzODRzK2Rt9RNeRdZ2EHQkliVL8kt9g/
YBdWW/kMMURB9+R/cLuQjMqmVm4JRyfM4tD14GmHl18+ZQI0ck2pB6xVGAW8dyZV
XV23yCuMqg0SChhrKk6jDtjSolcNWtWW1Ok8dfsS3GhQ9YxFtTvTk0HnAXGhikDq
JvMjtYt2CPcs24A1MWzyp2HH+gbXXiPUEZF6gfRmXn1AvhTCGSM=
=q5E3
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libdbix-class-schema-loader-perl
Source-Version: 0.07047-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libdbix-class-schema-loader-perl 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

Bug#866458: Please update Git repository mentioned in VCS fields

[Yaroslav Halchenko]

On Sat, 20 Jan 2018, Andreas Tille wrote:



> Could you please bring the Git repository in sync to enable me to make
> a proper team upload instead of putting the work to inject a NMU into
> the repository for something that is so simple that if it would be less
> work if you do it yourself.

our bad

moszumanska:~
*$> cat /srv/git.debian.org/git/pkg-exppsy/pydicom.git/HEAD 
ref: refs/heads/debian-release

$> echo 'ref: refs/heads/debian' >| 
/srv/git.debian.org/git/pkg-exppsy/pydicom.git/HEAD


try now ;)
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#881293: marked as done (libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 17:06:15 +
with message-id 
and subject line Bug#881293: fixed in libvirt 4.0.0-1
has caused the Debian Bug report #881293,
regarding libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso
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.)


-- 
881293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon
Version: 3.9.0-1
Severity: important


[  271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp 
7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000]

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

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

Versions of packages libvirt-daemon depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-3
ii  libaudit1   1:2.8.1-2
ii  libavahi-client30.7-3
ii  libavahi-common30.7-3
ii  libblkid1   2.30.2-0.1
ii  libc6   2.24-17
ii  libcap-ng0  0.7.7-3.1+b1
ii  libcurl3-gnutls 7.56.1-1
ii  libdbus-1-3 1.12.0-1
ii  libdevmapper1.02.1  2:1.02.145-1
ii  libfuse22.9.7-1
ii  libgnutls30 3.5.16-1
ii  libnetcf1   1:0.2.8-1+b2
ii  libnl-3-200 3.2.27-2
ii  libnl-route-3-200   3.2.27-2
ii  libnuma12.0.11-2.1
ii  libparted2  3.2-18
ii  libpcap0.8  1.8.1-5
ii  libpciaccess0   0.13.4-1+b2
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
ii  libselinux1 2.7-2
ii  libssh2-1   1.8.0-1
ii  libudev1235-2
ii  libvirt03.9.0-1
ii  libxen-4.8  4.8.1-1+deb9u3
ii  libxenstore3.0  4.8.1-1+deb9u3
ii  libxml2 2.9.4+dfsg1-5+b1
ii  libyajl22.1.0-2+b3

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.4+dfsg1-5+b1
ii  netcat-openbsd  1.178-3
ii  qemu1:2.10.0+dfsg-2
ii  qemu-kvm1:2.10.0+dfsg-2

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster   
pn  libvirt-daemon-driver-storage-rbd   
pn  libvirt-daemon-driver-storage-sheepdog  
pn  libvirt-daemon-driver-storage-zfs   
ii  libvirt-daemon-system   3.9.0-1
pn  numad   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.0.0-1

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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, 20 Jan 2018 16:31:11 +0100
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 libnss-libvirt - nss plugin providing IP add ress resolution for virtual 
machines
 libvirt-clients - Programs for the libvirt library
 libvirt-daemon - Virtualization daemon
 libvirt-daemon-driver-storage-gluster - Virtualization daemon glusterfs 
storage driver
 libvirt-daemon-driver-storage-rbd - Virtualization daemon RBD storage driver
 libvirt-daemon-driver-storage-sheepdog - Virtualization daemon Sheedog storage 
driver
 libvirt-daemon-driver-storage-zfs - Virtualization daemon ZFS storage 

Bug#887810: marked as done (krb5-multidev: "krb5-config.mit --cflags gssapi" returns wrong include directory)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 16:49:47 +
with message-id 
and subject line Bug#887810: fixed in krb5 1.16-2
has caused the Debian Bug report #887810,
regarding krb5-multidev: "krb5-config.mit --cflags gssapi" returns wrong 
include directory
to be marked as done.

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

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


-- 
887810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: krb5-multidev
Version: 1.16-1
Severity: serious
Control: affects -1 src:dovecot

dovecot FTBFS with krb5-multidev 1.16-1:

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

...
checking for krb5-config... krb5-config.mit
checking gssapi/gssapi.h usability... no
checking gssapi/gssapi.h presence... no
checking for gssapi/gssapi.h... no
checking gssapi.h usability... no
checking gssapi.h presence... no
checking for gssapi.h... no
configure: error: Can't build with GSSAPI support: gssapi.h not found
debian/rules:80: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1


Root cause:

$ krb5-config.mit --cflags gssapi
-isystem /usr/include/x86_64-linux-gnu/mit-krb5
$ 
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.16-2

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated krb5 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, 20 Jan 2018 11:02:57 -0500
Source: krb5
Binary: krb5-user krb5-kdc krb5-kdc-ldap krb5-admin-server krb5-kpropd 
krb5-multidev libkrb5-dev libkrb5-dbg krb5-pkinit krb5-otp krb5-k5tls krb5-doc 
libkrb5-3 libgssapi-krb5-2 libgssrpc4 libkadm5srv-mit11 libkadm5clnt-mit11 
libk5crypto3 libkdb5-9 libkrb5support0 libkrad0 krb5-gss-samples krb5-locales 
libkrad-dev
Architecture: source
Version: 1.16-2
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Description:
 krb5-admin-server - MIT Kerberos master server (kadmind)
 krb5-doc   - documentation for MIT Kerberos
 krb5-gss-samples - MIT Kerberos GSS Sample applications
 krb5-k5tls - TLS plugin for MIT Kerberos
 krb5-kdc   - MIT Kerberos key server (KDC)
 krb5-kdc-ldap - MIT Kerberos key server (KDC) LDAP plugin
 krb5-kpropd - MIT Kerberos key server (Slave KDC Support)
 krb5-locales - internationalization support for MIT Kerberos
 krb5-multidev - development files for MIT Kerberos without Heimdal conflict
 krb5-otp   - OTP plugin for MIT Kerberos
 krb5-pkinit - PKINIT plugin for MIT Kerberos
 krb5-user  - basic programs to authenticate using MIT Kerberos
 libgssapi-krb5-2 - MIT Kerberos runtime libraries - krb5 GSS-API Mechanism
 libgssrpc4 - MIT Kerberos runtime libraries - GSS enabled ONCRPC
 libk5crypto3 - MIT Kerberos runtime libraries - Crypto Library
 libkadm5clnt-mit11 - MIT Kerberos runtime libraries - Administration Clients
 libkadm5srv-mit11 - MIT Kerberos runtime libraries - KDC and Admin Server
 libkdb5-9  - MIT Kerberos runtime libraries - Kerberos database
 libkrad-dev - MIT Kerberos RADIUS Library Development
 libkrad0   - MIT Kerberos runtime libraries - RADIUS library
 libkrb5-3  - MIT Kerberos runtime libraries
 libkrb5-dbg - debugging files for MIT Kerberos
 libkrb5-dev - headers and development libraries for MIT Kerberos
 libkrb5support0 - MIT Kerberos runtime libraries - Support library
Closes: 887810
Changes:
 krb5 (1.16-2) unstable; urgency=medium
 .
   * Update location of packaging GIT repository
   * krb5-config was incorrectly changed to include the multiarch tripple
 in include paths.  However, our include files are not architecture
 specific; fix krb5-config to not include a multiarch tripple in
 include paths, Closes: #887810
Checksums-Sha1:
 42cea3421ff9db5e67530bac89a5b0e346a6e5b4 3358 krb5_1.16-2.dsc
 0f418e40327e4c02a98d6e13139b116bd800653c 96272 

Processed: Pending fixes for bugs in the libdbix-class-schema-loader-perl package

[Debian Bug Tracking System]

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

> tag 882618 + pending
Bug #882618 [libdbix-class-schema-loader-perl] 
libdbix-class-schema-loader-perl: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to debhelper, tagging 887727

[Debian Bug Tracking System]

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

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 887727 + pending
Bug #887727 [debhelper] debhelper,dh-dist-zilla: dh-dist-zilla based package 
builds no more run dh_auto_install (and maybe other dh_auto_*)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882618: Pending fixes for bugs in the libdbix-class-schema-loader-perl package

[pkg-perl-maintainers]

tag 882618 + pending
thanks

Some bugs in the libdbix-class-schema-loader-perl package are closed
in revision 5c422180e28ee04e2d6197f9f7c27e5e09b15d07 in branch
'master' by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdbix-class-schema-loader-perl.git/commit/?id=5c42218

Commit message:

Add patch 0001-Disable-cloning-when-merging-hashes.patch

to handle Hash::Merge's changed cloning behaviour.

Thanks: Niko Tyni for writing the patch.
Closes: #882618

Processed: limit source to krb5, tagging 887810

[Debian Bug Tracking System]

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

> limit source krb5
Limiting to bugs with field 'source' containing at least one of 'krb5'
Limit currently set to 'source':'krb5'

> tags 887810 + pending
Bug #887810 [krb5-multidev] krb5-multidev: "krb5-config.mit --cflags gssapi" 
returns wrong include directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887810: krb5-multidev: "krb5-config.mit --cflags gssapi" returns wrong include directory

[Sam Hartman]

I am testing a fix.
My apologies for the sloppy change.

Bug#887749: marked as done (pymca FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 16:06:42 +
with message-id 
and subject line Bug#887749: fixed in pymca 5.2.2+dfsg-2
has caused the Debian Bug report #887749,
regarding pymca FTBFS with glibc 2.26
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.)


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

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

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/1st/pymca-5.2.2+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE=1 -IPyMca5/PyMcaIO/specfile/include 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c PyMca5/PyMcaIO/specfile/src/locale_management.c -o 
build/temp.linux-amd64-2.7/PyMca5/PyMcaIO/specfile/src/locale_management.o
PyMca5/PyMcaIO/specfile/src/locale_management.c:27:10: fatal error: xlocale.h: 
No such file or directory
 #include 
  ^~~
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: pymca
Source-Version: 5.2.2+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pymca package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Jan 2018 15:26:30 +0100
Source: pymca
Binary: pymca python-pymca5 python-pymca5-dbg python3-pymca5 python3-pymca5-dbg 
pymca-data pymca-doc
Architecture: source
Version: 5.2.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 pymca  - Applications and toolkit for X-ray fluorescence analysis -- scrip
 pymca-data - Architecture independent data files for PyMca
 pymca-doc  - Documentation files for PyMca
 python-pymca5 - Applications and toolkit for X-ray fluorescence analysis -- 
Pytho
 python-pymca5-dbg - Applications and toolkit for X-ray fluorescence analysis 
-- Pytho
 python3-pymca5 - Applications and toolkit for X-ray fluorescence analysis -- 
Pytho
 python3-pymca5-dbg - Applications and toolkit for X-ray fluorescence analysis 
-- Pytho
Closes: 887749
Changes:
 pymca (5.2.2+dfsg-2) unstable; urgency=medium
 .
   * fix FTBFS with glibc2.26 (Closes: #887749)
   * d/patches/
 - 0001-xlocale.h-not-available-under-glibc-2.26.patch (Added)
Checksums-Sha1:
 ec795fbd3d599960619d9fd4f906dc8ca0579b76 2898 pymca_5.2.2+dfsg-2.dsc
 0bf8b347192970e69c02817f7329944ae042068c 8548 pymca_5.2.2+dfsg-2.debian.tar.xz
Checksums-Sha256:
 4ee549995c8acdb1c43b682b52bbba62e61a5f954fe57a97270f62b865d405da 2898 
pymca_5.2.2+dfsg-2.dsc
 d01985b29d0d14ea5c9cadad7ef7e2030af3aecc07f7d0e1d77b0fd1f6d09e3f 8548 
pymca_5.2.2+dfsg-2.debian.tar.xz
Files:
 edc2367919dcf1824d90c20cbca123b7 2898 science optional pymca_5.2.2+dfsg-2.dsc
 c8cdbc1beeab6cf41170f6a517bc1f45 8548 science optional 
pymca_5.2.2+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAlpjZHkRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvDww/9HsjbkIFjs9+TaU+rN1Ng+Wlavd1sFVg5
SPEGVJrGAE/vL2zjgEA8M5g1mYcec+0GQHqWClHdUq1mThcEwF8wM4OSbOJ4M7Sv
1iaRTg0ZE3ZEsmW4PGr+PmlqKkz6bGJaKrR687aistQl6Xhpkh+vzb0HtgAQlNEY
GrKbS8FfZOtuPTbFjYB3wQmdS1552ctUSN1U6zhi1sOMmM8kN0LxjjdRTU+ikGpT
rtNgYH9tQtOwZL0Pj2VXWddYifu7DdxbQdq/0Km2+aPwDNTLL6zgSFD5wrc4bnxm
Sp8FscSApXruhuMzWTbf0zgS2poNvWlGrpEer3r9VZKOxjqwPjhMPwnoRZX1GcyV
Edmgp8/M7nPmNL+r90ume6M4rV7MhQvmWbtEaqQYEXZLmDbAyy/+v0x65SAIjqm/
ZaKLiWRCJ+swUhitcbEua1wFRcV4cp6+ih/PQiJ2SvwvyAc8CqFzf2RaiLu2x0/p
24ZFZt3mrhmzMbu4a4yT318zV0o8PkZUgN7fDlqg0y8zvKhRFS7YeH0Jbg6Qfa+B
GCI2ZgzjX4UIg1nuIWfcr2mACt7CDK0FPyqhNxdTy/s1WlqDfopMTQDnpgznxjEA

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Andreas Beckmann]

On 2018-01-18 23:59, David Kalnischkies wrote:
> Hi,
> 
> On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote:
> [...]
>   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
>   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> not found (required by /lib/i386-linux-gnu/libexpat.so.1)
>   dpkg: warning: subprocess old pre-removal script returned error exit 
> status 1
>   dpkg: trying script from the new package instead ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb 
> (--unpack):
>there is no script in the new version of the package - giving up
>   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> not found (required by /lib/i386-linux-gnu/libexpat.so.1)

 This failure is normal given libexpat1 requires the new libc which has
 not been unpacked yet.
>>>
>>> Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
>>> in preinst actions. The thing is that Depends only after postinst ordering,
>>> not unpack ordering.
>>
>> Well it's not the preinst script, but the prerm script. The problem is
>> unpacking libexpat1 before libc6 breaks libexpat1 and not usable
>> anymore.
> 
> prerm is the very first script being called (see §6.6) and usually it is
> the script of the version installed (only in error cases the script from
> the version being upgraded to will be tried as detailed in the dpkg
> messages) so I would argue that the dependencies (maybe) satisfied are
> the dependencies of the installed version, not the one being installed
> (argueably the dependency set of v1 and v2 could conflict with each
> other, so if dependencies of v2 would be satisfied that means v1 script
> would be bound to explode). But thats perhaps just the fear talking as
> going with dependencies of v2 would probably result in a lot of hard
> coding problems for apt & dpkg (and other low package managers).
> 
> In any case, the unpack of these packages is in the same dpkg call, so
> if dpkg would have wanted it could have reordered them & apt has no idea
> about maintainerscript in general, so I would say this isn't an apt bug.
> 
> (Althrough, if we decide on v2, I guess apt needs to change anyhow as
> that same call thing might be just dumb luck in this case. Not even sure
> if v1 is in any way "guaranteed" to be perfectly honest…)
> 
> Can't stop the feeling that we had issues with python begin called from
> prerm before and the general advice was: "don't – stick to essential".

I tested a bit more to find adding which Pre-Depends would solve the
issue *without* adding a dummy empty prerm to libglib2.0-dev:

libglib2.0-dev: Pre-Depends: libexpat1
OR
libexpat1: Pre-Depends: libc6 (>= 2.25)

The following does not help:

libglib2.0-dev: Pre-Depends: python3:any


For now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
error starts to show up elsewhere (e.g. in a package where both old and
new prerm use python3), probably adding the Pre-Depends to libexpat1
would be the general solution.


Andreas

Bug#884288: marked as done (simplesnap: depends on nonfree zfsutils-linux (favored over zfs-fuse))

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 15:20:11 +
with message-id 
and subject line Bug#884288: fixed in simplesnap 1.0.4+nmu1
has caused the Debian Bug report #884288,
regarding simplesnap: depends on nonfree zfsutils-linux (favored over zfs-fuse)
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.)


-- 
884288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: simplesnap
Version: 1.0.4
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

simplesnap depends on zfsutils | zfsutils-linux | zfs-fuse.

zfsutils is a virtual package provided only by zfsutils-linux, and
zfsutils-linux is nonfree.

Effectively, simplesnap recommends a nonfree tool favored over a free
one.

Policy §2.2.1 says:

> must not declare a Pre-Depends, Depends, Recommends, Build-Depends,
> Build-Depends-Indep, or Build-Depends-Arch relationship on a non-main
> package unless that package is only listed as a non-default
> alternative for a package in main),


Please list only zfs-fuse as dependency of simplesnap, demoting
zfsutils and zfsutils-linux to only a suggestion.

Or alternatively move simplesnap to contrib where stronger ties to
nonfree packages is permitted.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloxF2oACgkQLHwxRsGg
ASGhjw/8Dzq+DmMypcc41mwrJf/BWM12o8e5dRvtLkqCm5gr/5pW9Qw3/sW4yWd9
kdV1793WFEjUZymnJcAiRXtMN4uF8SdNYhgzDXSiJT1dwL42NGcAkGkm822Ki7bv
LpR92KSHUPUoBNppEzeB6bmmC/UBtJEO5HVKLKJnp9WdWCPJBAVov8IUXhYvwiav
A59pk3y3kZYnajWBQp3VzrSWqbcLt49be/6CJLaMvvRla6Xm3sHPLCj0zH1A7KAh
UAXk5Qva0wpuaMVBiCHvRF+BS0lZ6W34Oo03LXA/fnkeZdJqwzKaDmHvwNKHnaJY
GXOACl1QJp0YbKTFXDP3+L8eddoN6h2nUt4urlqPjhQJVNZaA25TcdcPUxQbggbc
2Ui0g8g0lFh933NIoWE2tFG1gajkGQpcl26fWY+KBYx8uAui8Xyoq90bORtrVmFa
n637gSbswWL+HuGSazbng1Aa50+6xM6bDJl4YWNGj7HwiFtCsxxPyti7Su31ZNF+
Fiug18HdOxYdbejxRC+FFIrnk6dFeiamfPAI4+iSahkhEOOklfLZWFjQj3PdTzh8
FDonVCZ7KPlI03giM71dSpFM5b1DzRdt0Iq/VZEcTVg9OI760nEEM4K6v/4DMWPD
PdziUIVbyGo3kpUcIuY9R6IQf91mRGzmN7UdjKb/KqWb1jPmQbU=
=1HgR
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: simplesnap
Source-Version: 1.0.4+nmu1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated simplesnap 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, 10 Jan 2018 15:09:28 +0200
Source: simplesnap
Binary: simplesnap
Architecture: source
Version: 1.0.4+nmu1
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: Adrian Bunk 
Description:
 simplesnap - Simple and powerful network transmission of ZFS snapshots
Closes: 884288
Changes:
 simplesnap (1.0.4+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Correct the order of dependencies to list
 zfs-fuse (in main) first. (Closes: #884288)
Checksums-Sha1:
 44921ad8641500be163398f02044e88249864a8b 1585 simplesnap_1.0.4+nmu1.dsc
 089547ab397a88ceafcfb2f86bc3ea83a1363a01 32616 simplesnap_1.0.4+nmu1.tar.xz
Checksums-Sha256:
 7fba7c86a715bcd986224abab2aae1468da578982a9a6368d3da2ef7a16d83f7 1585 
simplesnap_1.0.4+nmu1.dsc
 be8a7dcf389774a4871bb0672316988fbd51ad765e74bc7753cea2f22c52b0bf 32616 
simplesnap_1.0.4+nmu1.tar.xz
Files:
 416d814a0c76f009a8579c225311d658 1585 admin optional simplesnap_1.0.4+nmu1.dsc
 405f82a585e7cf9b8ac7d8e5b4e77583 32616 admin optional 
simplesnap_1.0.4+nmu1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpWEUUACgkQiNJCh6LY
mLFEig//c+cZM+7EiPK1KDMI8Mp4ZYQOau19Pij/RswBpTgW1Y1AXJ9Spv3b9zpl
xdDYrnV9E7RMX3+lin52NwGDs7YUGJZoKUKKlpZUcBBndWCoow6uw+Gr5Uc5wVLp
XSDf+ht6/ZFu05JNFdhWytlhJkNzHrOEU+IT1Y0ZQ3mVOLD6byw8GxCVJlhsaMNF
zFdODqElOM6jF2xZoJLFx359xQQkk6qb3BOVaP83wwZ1LBgddFRUu6CVtowgVfhE
yhWMfNv0IypScL0v+hGR+S1vq3KP0v/PydO7aK/7uL10kXMHPhaV55G1Y1xQ0o4M

Bug#887836: marked as done (kile: core dumps on start in KileTool::LivePreviewManager::buildLivePreviewMenu)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 15:14:47 +
with message-id 
and subject line Bug#887836: fixed in kile 4:2.9.91-4
has caused the Debian Bug report #887836,
regarding kile: core dumps on start in 
KileTool::LivePreviewManager::buildLivePreviewMenu
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.)


-- 
887836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kile
Version: 4:2.9.91-3
Severity: grave
Justification: renders package unusable

Dear all,

kile recently started to refuse to start, core dumping on the way:
$ kile
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' 
from launcher.
kdeinit5: preparing to launch 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: PID 31435 terminated.
Segmentation fault (core dumped)
$

(gdb) bt
#0  0x7f848c416dac in KileTool::LivePreviewManager::buildLivePreviewMenu (
this=this@entry=0x0, config=0x559edd0ee470) at ./src/livepreview.cpp:278
#1  0x7f848c418eee in KileTool::LivePreviewManager::readConfig (this=0x0,
config=) at ./src/livepreview.cpp:400
#2  0x7f848c37ccbf in Kile::readConfig (this=this@entry=0x559edcfc0840)
at ./src/kile.cpp:2375
#3  0x7f848c395060 in Kile::Kile (this=0x559edcfc0840,
allowRestore=, parent=,
__in_chrg=, __vtt_parm=)
at ./src/kile.cpp:266
#4  0x7f848c41e3c8 in kdemain (argc=, argv=)
at ./src/main.cpp:156
#5  0x7f848be68f2a in __libc_start_main (main=0x559edadc2730 ,
argc=1, argv=0x7ffef5ff6c08, init=, fini=,
rtld_fini=, stack_end=0x7ffef5ff6bf8)
at ../csu/libc-start.c:310
#6  0x559edadc276a in _start ()



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

Kernel: Linux 4.14.14 (SMP w/8 CPU cores)
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)

Versions of packages kile depends on:
ii  kio5.37.0-2
ii  konsole-kpart  4:17.08.3-1
ii  libc6  2.26-4
ii  libgcc11:7.2.0-19
ii  libkf5codecs5  5.37.0-2
ii  libkf5completion5  5.37.0-2
ii  libkf5configcore5  5.37.0-2
ii  libkf5configgui5   5.37.0-2
ii  libkf5configwidgets5   5.37.0-2
ii  libkf5coreaddons5  5.37.0-3
ii  libkf5dbusaddons5  5.37.0-2
ii  libkf5guiaddons5   5.37.0-2
ii  libkf5i18n55.37.0-2
ii  libkf5iconthemes5  5.37.0-2
ii  libkf5jobwidgets5  5.37.0-2
ii  libkf5khtml5   5.37.0-3
ii  libkf5kiocore5 5.37.0-2
ii  libkf5kiofilewidgets5  5.37.0-2
ii  libkf5kiowidgets5  5.37.0-2
ii  libkf5parts5   5.37.0-2
ii  libkf5service-bin  5.37.0-2
ii  libkf5service5 5.37.0-2
ii  libkf5texteditor5  5.37.0-2+b1
ii  libkf5textwidgets5 5.37.0-2
ii  libkf5widgetsaddons5   5.37.0-2
ii  libkf5windowsystem55.37.0-2
ii  libkf5xmlgui5  5.37.0-2
ii  libpoppler-qt5-1   0.61.1-2
ii  libqt5core5a   5.9.2+dfsg-7
ii  libqt5dbus55.9.2+dfsg-7
ii  libqt5gui5 5.9.2+dfsg-7
ii  libqt5script5  5.9.2+dfsg-2
ii  libqt5widgets5 5.9.2+dfsg-7
ii  libqt5xml5 5.9.2+dfsg-7
ii  libstdc++6 7.2.0-19
ii  perl   5.26.1-4
ii  texlive-latex-base 2017.20180110-1

Versions of packages kile recommends:
ii  dvipng   1.15-1
ii  ghostscript  9.22~dfsg-1
ii  imagemagick  8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-16
ii  psutils  1.17.dfsg-4
ii  texlive  2017.20180110-1

Versions of packages kile suggests:
ii  aspell  0.60.7~20110707-4
ii  asymptote   2.41-4
ii  context 2017.05.15.20170613-2
ii  dblatex 0.3.10-2
ii  ispell  3.4.00-6
pn  kbibtex 
pn  kile-doc
pn  kile-l10n   
pn  latex2html  
pn  lilypond
ii  texlive-plain-generic [tex4ht]  2017.20180110-1
ii  texlive-xetex   2017.20180110-1
ii  zip 3.0-11+b1

-- no debconf information
Norbert

--
PREINING Norbert 

Bug#887727: [debhelper-devel] Bug#887727: debhelper, dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*)

[Axel Beckert]

Control: tag -1 - moreinfo

Hi Niels,

thanks for coming up with a patch so quickly!

Niels Thykier wrote:
> Could you please verify that the attached patch fixes the problem for you?

systray-mdstat and roary both build fine again with this patch applied
on top of debhelper's git HEAD.

Since 10.10.6 to 11.1.2 is rather big range of releases which saw
several uploads to backports as well as an Ubuntu release I intent to
update dh-dist-zilla's  debhelper dependency to << 10.10.6~ and >=
11.1.3~.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: Digital signature

Bug#884294: Patch for pandas RC 884294, someone to sponsor?

[Andreas Tille]

Hi Lumin,

On Sat, Jan 20, 2018 at 01:42:43PM +, Lumin wrote:
> Control: tags -1 +patch
> 
> Pandas FTBFS on amd64 due to test failure:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884294
> I reproduced this FTBFS on my machine (sid/amd64).
> 
> This test failure was due to a numpy problem. Upstream workaround
> (bypass) is available:
> * 
> https://github.com/pandas-dev/pandas/commit/5f2b96bb637f6ddeec169c5ef8ad20013a03c853
> 
> Another test failure arose (not related to #884924). The new failure
> could be solved by referencing:
> * https://github.com/pandas-dev/pandas/issues/17046
> * https://github.com/pandas-dev/pandas/pull/17051
> 
> For details about more test failures arose when I'm writing this email please
> check the patches.
> 
> debomatic-amd64 build was successful:
> http://debomatic-amd64.debian.net/distribution#unstable/pandas/0.20.3-11/buildlog
> 
> git-formatted patches are attached. I can push the commits to salsa if
> the fix is fine.

Thanks a lot for your work.  Its very much appreciated.  Please push
(which you can do in any future case without asking).

> Can someone review and sponsor the Team upload?

I'd volunteer to upload once it is pushed.  Please ping me after pushing
since there is not commit mailing list and I'm not sure whether the
tracker solution is implemented yet.

> Thanks.

Lots of thanks to you

  Andreas.

-- 
http://fam-tille.de

Processed: Re: [debhelper-devel] Bug#887727: debhelper, dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #887727 [debhelper] debhelper,dh-dist-zilla: dh-dist-zilla based package 
builds no more run dh_auto_install (and maybe other dh_auto_*)
Removed tag(s) moreinfo.

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

Bug#887738: nspr FTBFS with glibc 2.26

[Jason Duerstock]

Source: nspr
Followup-For: Bug #887738

Dear Maintainer,

The attached patch fixes this bug.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- nspr/pr/tests/prfz.c.orig   2018-01-20 13:38:48.877027452 +
+++ nspr/pr/tests/prfz.c2018-01-20 13:23:00.495279463 +
@@ -10,6 +10,7 @@
 #include 
 #include 
 #include 
+#include 
 
 int
 main(int argc, char **argv)

Bug#866458: Please update Git repository mentioned in VCS fields

[Andreas Tille]

Hi again,

On Sun, Jan 07, 2018 at 08:25:35AM +0100, Andreas Tille wrote:
> I'd volunteer to work on this bug but the repository specified in
> the VCS fields is not up to date.

To explain what I mean:

 $ debcheckout pydicom
 $ head pydicom/debian/changelog
pydicom (0.9.5~rc1-1) experimental; urgency=low

  * New upstream release candidate
  * Boosted policy compliance to 3.9.1 -- no changes are necessary
  * Deprecated debian/patches/up_with_statement_python2.5 -- absorbed upstream
  * Enabled unit-testing in-place

 -- Yaroslav Halchenko   Mon, 13 Sep 2010 22:26:52 -0400

pydicom (0.9.4.1-1) unstable; urgency=low
 $ apt-get source pydicom
 $ head pydicom-0.9.9/debian/changelog
pydicom (0.9.9-2) unstable; urgency=medium

  * Update maintainer email.
  * Bump standards version to 3.9.6; no changes necessary.
  * CME-base automatic modernization of debian/control.
  * Switch to debhelper 9.
  * Build python3 package.
  * Build documentation and ship it in a -doc package.

 -- Michael Hanke   Sat, 05 Sep 2015 07:38:24 +0200


Could you please bring the Git repository in sync to enable me to make
a proper team upload instead of putting the work to inject a NMU into
the repository for something that is so simple that if it would be less
work if you do it yourself.

Thank you

  Andreas.

-- 
http://fam-tille.de

Bug#884294: Patch for pandas RC 884294, someone to sponsor?

[Lumin]

Control: tags -1 +patch

Pandas FTBFS on amd64 due to test failure:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884294
I reproduced this FTBFS on my machine (sid/amd64).

This test failure was due to a numpy problem. Upstream workaround
(bypass) is available:
* 
https://github.com/pandas-dev/pandas/commit/5f2b96bb637f6ddeec169c5ef8ad20013a03c853

Another test failure arose (not related to #884924). The new failure
could be solved by referencing:
* https://github.com/pandas-dev/pandas/issues/17046
* https://github.com/pandas-dev/pandas/pull/17051

For details about more test failures arose when I'm writing this email please
check the patches.

debomatic-amd64 build was successful:
http://debomatic-amd64.debian.net/distribution#unstable/pandas/0.20.3-11/buildlog

git-formatted patches are attached. I can push the commits to salsa if
the fix is fine.
Can someone review and sponsor the Team upload?
Thanks.

pandas (0.20.3-11) unstable; urgency=medium

  * Team upload.
  * Cherry-pick upstream commit 5f2b96bb637f6ddeec169c5ef8ad20013a03c853
to workaround a numpy bug. (Closes: #884294)
+ patches/up_tst_dont_assert_that_a_bug_exists_in_numpy
  * Cherry-pick upstream commits to fix test failure caused by test_argsort().
+ patches/up_tst_np_argsort_comparison2
  * Workaround test failure of test_basic_indexing() in file
pandas/tests/series/test_indexing.py .
+ patches/deb_fix_test_failure_test_basic_indexing



-- 
Best,
From 23745eb17f921b42e1b3ee574c2aef0f05d4252f Mon Sep 17 00:00:00 2001
From: Mo Zhou 
Date: Sat, 20 Jan 2018 09:02:43 +
Subject: [PATCH 1/7] Cherry-pick upstream commit
 5f2b96bb637f6ddeec169c5ef8ad20013a03c853 to workaround a numpy bug. (Closes:
 #884294)

---
 debian/patches/series  |  1 +
 .../up_tst_dont_assert_that_a_bug_exists_in_numpy  | 33 ++
 2 files changed, 34 insertions(+)
 create mode 100644 debian/patches/up_tst_dont_assert_that_a_bug_exists_in_numpy

diff --git a/debian/patches/series b/debian/patches/series
index b0c042d..209965f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,6 +9,7 @@ deb_skip_sequencelike_on_armel
 # 858260.patch
 up_print_versions
 up_network_seaborn
+up_tst_dont_assert_that_a_bug_exists_in_numpy
 dateutil-2.6.1-fixed-ambiguous-tz-dst-be.patch
 mark_tests_working_on_intel.patch
 mark_tests_working_on_intel_s390x.patch
diff --git a/debian/patches/up_tst_dont_assert_that_a_bug_exists_in_numpy b/debian/patches/up_tst_dont_assert_that_a_bug_exists_in_numpy
new file mode 100644
index 000..4242da7
--- /dev/null
+++ b/debian/patches/up_tst_dont_assert_that_a_bug_exists_in_numpy
@@ -0,0 +1,33 @@
+From 5f2b96bb637f6ddeec169c5ef8ad20013a03c853 Mon Sep 17 00:00:00 2001
+From: Eric Wieser 
+Date: Sat, 15 Jul 2017 13:30:03 +0100
+Subject: [PATCH] TST: Don't assert that a bug exists in numpy (#16940)
+
+Better to ignore the warning from the bug, rather than assert the bug is still there
+
+After this change, numpy/numpy#9412 _could_ be backported to fix the bug
+---
+ pandas/tests/test_algos.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/pandas/tests/test_algos.py b/pandas/tests/test_algos.py
+index 9504d2a9426..993dcc4f527 100644
+--- a/pandas/tests/test_algos.py
 b/pandas/tests/test_algos.py
+@@ -2,6 +2,7 @@
+ 
+ import numpy as np
+ import pytest
++import warnings
+ 
+ from numpy.random import RandomState
+ from numpy import nan
+@@ -127,7 +128,7 @@ def test_unsortable(self):
+ arr = np.array([1, 2, datetime.now(), 0, 3], dtype=object)
+ if compat.PY2 and not pd._np_version_under1p10:
+ # RuntimeWarning: tp_compare didn't return -1 or -2 for exception
+-with tm.assert_produces_warning(RuntimeWarning):
++with warnings.catch_warnings():
+ pytest.raises(TypeError, algos.safe_sort, arr)
+ else:
+ pytest.raises(TypeError, algos.safe_sort, arr)
-- 
2.15.1

From b92f86abb26073326ec80dffaa017c1e3f77eab5 Mon Sep 17 00:00:00 2001
From: Mo Zhou 
Date: Sat, 20 Jan 2018 09:04:32 +
Subject: [PATCH 2/7] dch: finalize, upload to unstable

---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index bed979e..53b0deb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pandas (0.20.3-11) unstable; urgency=medium
+
+  * Team upload.
+  * Cherry-pick upstream commit 5f2b96bb637f6ddeec169c5ef8ad20013a03c853
+to workaround a numpy bug. (Closes: #884294)
+
+ -- Mo Zhou   Sat, 20 Jan 2018 09:00:31 +
+
 pandas (0.20.3-10) unstable; urgency=medium
 
   * Team upload.
-- 
2.15.1

From c37cee1b4a9c44522c6bf3d74bceb8f0b20364cd Mon Sep 17 00:00:00 2001
From: Mo Zhou 
Date: Sat, 20 Jan 2018 10:12:15 +
Subject: [PATCH 3/7] Cherry-pick upstream commit to fix test failure caused by

Processed: Patch for pandas RC 884294, someone to sponsor?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #884294 [src:pandas] pandas FTBFS: test failure
Added tag(s) patch.

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

Bug#887815: [Pkg-utopia-maintainers] Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

[Michael Biebl]

Am 20.01.2018 um 12:09 schrieb Guido Günther:
> /usr/include/libnm/nm-setting-tc-config.h:43:1: error: 'NMTCQdisc' is 
> deprecated: Not available before 1.10.2

I suppose this is the problem in configure.ac

LIBNM_CFLAGS="$LIBNM_CFLAGS -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2"
LIBNM_CFLAGS="$LIBNM_CFLAGS -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2"

This triggers a warning which together with Werror leads to the build
failure.
The pkg-utopia maintained VPN modules trigger this warning as well, but
don't use Werror, so do not fail the build.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#887836: kile: core dumps on start in KileTool::LivePreviewManager::buildLivePreviewMenu

[Norbert Preining]

Package: kile
Version: 4:2.9.91-3
Severity: grave
Justification: renders package unusable

Dear all,

kile recently started to refuse to start, core dumping on the way:
$ kile
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' 
from launcher.
kdeinit5: preparing to launch 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: PID 31435 terminated.
Segmentation fault (core dumped)
$

(gdb) bt
#0  0x7f848c416dac in KileTool::LivePreviewManager::buildLivePreviewMenu (
this=this@entry=0x0, config=0x559edd0ee470) at ./src/livepreview.cpp:278
#1  0x7f848c418eee in KileTool::LivePreviewManager::readConfig (this=0x0,
config=) at ./src/livepreview.cpp:400
#2  0x7f848c37ccbf in Kile::readConfig (this=this@entry=0x559edcfc0840)
at ./src/kile.cpp:2375
#3  0x7f848c395060 in Kile::Kile (this=0x559edcfc0840,
allowRestore=, parent=,
__in_chrg=, __vtt_parm=)
at ./src/kile.cpp:266
#4  0x7f848c41e3c8 in kdemain (argc=, argv=)
at ./src/main.cpp:156
#5  0x7f848be68f2a in __libc_start_main (main=0x559edadc2730 ,
argc=1, argv=0x7ffef5ff6c08, init=, fini=,
rtld_fini=, stack_end=0x7ffef5ff6bf8)
at ../csu/libc-start.c:310
#6  0x559edadc276a in _start ()



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

Kernel: Linux 4.14.14 (SMP w/8 CPU cores)
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)

Versions of packages kile depends on:
ii  kio5.37.0-2
ii  konsole-kpart  4:17.08.3-1
ii  libc6  2.26-4
ii  libgcc11:7.2.0-19
ii  libkf5codecs5  5.37.0-2
ii  libkf5completion5  5.37.0-2
ii  libkf5configcore5  5.37.0-2
ii  libkf5configgui5   5.37.0-2
ii  libkf5configwidgets5   5.37.0-2
ii  libkf5coreaddons5  5.37.0-3
ii  libkf5dbusaddons5  5.37.0-2
ii  libkf5guiaddons5   5.37.0-2
ii  libkf5i18n55.37.0-2
ii  libkf5iconthemes5  5.37.0-2
ii  libkf5jobwidgets5  5.37.0-2
ii  libkf5khtml5   5.37.0-3
ii  libkf5kiocore5 5.37.0-2
ii  libkf5kiofilewidgets5  5.37.0-2
ii  libkf5kiowidgets5  5.37.0-2
ii  libkf5parts5   5.37.0-2
ii  libkf5service-bin  5.37.0-2
ii  libkf5service5 5.37.0-2
ii  libkf5texteditor5  5.37.0-2+b1
ii  libkf5textwidgets5 5.37.0-2
ii  libkf5widgetsaddons5   5.37.0-2
ii  libkf5windowsystem55.37.0-2
ii  libkf5xmlgui5  5.37.0-2
ii  libpoppler-qt5-1   0.61.1-2
ii  libqt5core5a   5.9.2+dfsg-7
ii  libqt5dbus55.9.2+dfsg-7
ii  libqt5gui5 5.9.2+dfsg-7
ii  libqt5script5  5.9.2+dfsg-2
ii  libqt5widgets5 5.9.2+dfsg-7
ii  libqt5xml5 5.9.2+dfsg-7
ii  libstdc++6 7.2.0-19
ii  perl   5.26.1-4
ii  texlive-latex-base 2017.20180110-1

Versions of packages kile recommends:
ii  dvipng   1.15-1
ii  ghostscript  9.22~dfsg-1
ii  imagemagick  8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-16
ii  psutils  1.17.dfsg-4
ii  texlive  2017.20180110-1

Versions of packages kile suggests:
ii  aspell  0.60.7~20110707-4
ii  asymptote   2.41-4
ii  context 2017.05.15.20170613-2
ii  dblatex 0.3.10-2
ii  ispell  3.4.00-6
pn  kbibtex 
pn  kile-doc
pn  kile-l10n   
pn  latex2html  
pn  lilypond
ii  texlive-plain-generic [tex4ht]  2017.20180110-1
ii  texlive-xetex   2017.20180110-1
ii  zip 3.0-11+b1

-- no debconf information
Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#887835: qt5ct just *doesn't* work - The QT_QPA_PLATFORMTHEME environment variable is not set correctly

[Norbert Preining]

Package: qt5ct
Version: 0.34-1
Severity: grave
Justification: renders package unusable

Dear all,

although the man page of qt5ct proudly states:
  qt5ct hasn't options. It just works.
reality is that it simply doesn't start, but shows a warning dialog with
  The QT_QPA_PLATFORMTHEME environment variable is not set correctly
and that's it.

Best

Norbert


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

Kernel: Linux 4.14.14 (SMP w/8 CPU cores)
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)

Versions of packages qt5ct depends on:
ii  libc62.26-4
ii  libgcc1  1:7.2.0-19
ii  libgl1   1.0.0-1.1
ii  libqt5core5a [qtbase-abi-5-9-2]  5.9.2+dfsg-7
ii  libqt5dbus5  5.9.2+dfsg-7
ii  libqt5gui5   5.9.2+dfsg-7
ii  libqt5widgets5   5.9.2+dfsg-7
ii  libstdc++6   7.2.0-19

qt5ct recommends no packages.

Versions of packages qt5ct suggests:
pn  qt5-style-plugins  

-- no debconf information

Bug#887762: marked as done (gcc-mingw-w64 FTBFS with gcc-7-source 7.2.0-19)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 12:05:04 +
with message-id 
and subject line Bug#887762: fixed in gcc-mingw-w64 20.1
has caused the Debian Bug report #887762,
regarding gcc-mingw-w64 FTBFS with gcc-7-source 7.2.0-19
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.)


-- 
887762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-mingw-w64
Version: 20
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-mingw-w64.html

...
# niXman’s experimental::filesystem support
patch -p0 -d/build/1st/gcc-mingw-w64-20/src < 
debian/patches/gcc-7-filesystem.patch
patching file libstdc++-v3/src/filesystem/fs-posix.h
patching file libstdc++-v3/src/filesystem/fs-win32.h
patching file libstdc++-v3/src/filesystem/dir.cc
patching file libstdc++-v3/src/filesystem/ops.cc
Hunk #11 succeeded at 519 (offset 20 lines).
Hunk #12 succeeded at 721 (offset 20 lines).
Hunk #13 succeeded at 781 (offset 20 lines).
Hunk #14 succeeded at 830 (offset 20 lines).
Hunk #15 succeeded at 854 (offset 20 lines).
Hunk #16 succeeded at 880 (offset 20 lines).
Hunk #17 succeeded at 939 (offset 20 lines).
Hunk #18 succeeded at 966 (offset 20 lines).
Hunk #19 succeeded at 973 (offset 20 lines).
Hunk #20 succeeded at 1023 (offset 20 lines).
Hunk #21 succeeded at 1073 (offset 20 lines).
Hunk #22 succeeded at 1155 (offset 20 lines).
Hunk #23 succeeded at 1212 (offset 20 lines).
Hunk #24 FAILED at 1214.
Hunk #25 FAILED at 1252.
Hunk #26 succeeded at 1364 (offset 65 lines).
Hunk #27 succeeded at 1385 (offset 65 lines).
Hunk #28 succeeded at 1438 (offset 65 lines).
Hunk #29 succeeded at 1456 (offset 65 lines).
Hunk #30 succeeded at 1463 (offset 65 lines).
Hunk #31 succeeded at 1477 (offset 65 lines).
Hunk #32 succeeded at 1537 (offset 65 lines).
Hunk #33 succeeded at 1554 (offset 65 lines).
2 out of 33 hunks FAILED -- saving rejects to file 
libstdc++-v3/src/filesystem/ops.cc.rej
patching file libstdc++-v3/src/filesystem/path.cc
debian/rules:227: recipe for target 'mingw-w64-patch-stamp' failed
make: *** [mingw-w64-patch-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: gcc-mingw-w64
Source-Version: 20.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated gcc-mingw-w64 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, 20 Jan 2018 12:11:38 +0100
Source: gcc-mingw-w64
Binary: gcc-mingw-w64 gcc-mingw-w64-i686 gcc-mingw-w64-x86-64 g++-mingw-w64 
g++-mingw-w64-i686 g++-mingw-w64-x86-64 gfortran-mingw-w64 
gfortran-mingw-w64-i686 gfortran-mingw-w64-x86-64 gobjc-mingw-w64 
gobjc-mingw-w64-i686 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64 
gobjc++-mingw-w64-i686 gobjc++-mingw-w64-x86-64 gnat-mingw-w64 
gnat-mingw-w64-i686 gnat-mingw-w64-x86-64 gcc-mingw-w64-base
Architecture: source
Version: 20.1
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 g++-mingw-w64 - GNU C++ compiler for MinGW-w64
 g++-mingw-w64-i686 - GNU C++ compiler for MinGW-w64 targeting Win32
 g++-mingw-w64-x86-64 - GNU C++ compiler for MinGW-w64 targeting Win64
 gcc-mingw-w64 - GNU C compiler for MinGW-w64
 gcc-mingw-w64-base - GNU Compiler Collection for MinGW-w64 (base package)
 gcc-mingw-w64-i686 - GNU C compiler for MinGW-w64 targeting Win32
 gcc-mingw-w64-x86-64 - GNU C compiler for MinGW-w64 targeting Win64
 gfortran-mingw-w64 - GNU Fortran compiler for MinGW-w64
 gfortran-mingw-w64-i686 - GNU Fortran compiler for MinGW-w64 targeting Win32
 gfortran-mingw-w64-x86-64 - GNU Fortran compiler for MinGW-w64 targeting Win64
 gnat-mingw-w64 - GNU Ada compiler for MinGW-w64
 gnat-mingw-w64-i686 - GNU Ada compiler for MinGW-w64 targeting Win32
 gnat-mingw-w64-x86-64 - GNU Ada compiler for MinGW-w64 targeting Win64
 gobjc++-mingw-w64 - GNU Objective-C++ compiler 

Bug#887814: marked as done (freeipa FTBFS with libkrb5-dev 1.16-1)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 11:35:22 +
with message-id 
and subject line Bug#887814: fixed in freeipa 4.6.2-1
has caused the Debian Bug report #887814,
regarding freeipa FTBFS with libkrb5-dev 1.16-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.)


-- 
887814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeipa
Version: 4.4.4-4
Severity: serious

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

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I. -I../../util 
-I../../../util -DPREFIX=\"/usr\" -DBINDIR=\"/usr/bin\" 
-DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib\" 
-DDATADIR=\"/usr/share\" -DLDAPIDIR=\"/var/run\" -Wall -Wshadow 
-Wstrict-prototypes -Wpointer-arith -Wcast-align 
-Werror-implicit-function-declaration -DWITH_OPENLDAP -I/usr/include/nspr 
-I/usr/include/nss -I/usr/include/nspr -DUSE_OPENLDAP 
-DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
-D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 
-DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/nspr -I/usr/include/nss -I/usr/include/nspr 
-Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-align 
-Werror-implicit-function-declaration -g -O2 
-fdebug-prefix-map=/build/1st/freeipa-4.4.4=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ipa_kdb.c  -fPIC -DPIC -o .libs/ipa_kdb.o
ipa_kdb.c:729:2: error: #error unsupported DAL major version
 #error unsupported DAL major version
  ^
--- End Message ---
--- Begin Message ---
Source: freeipa
Source-Version: 4.6.2-1

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated freeipa 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, 20 Jan 2018 12:41:28 +0200
Source: freeipa
Binary: freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests
Architecture: source
Version: 4.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 freeipa-admintools - FreeIPA centralized identity framework -- admintools
 freeipa-client - FreeIPA centralized identity framework -- client
 freeipa-common - FreeIPA centralized identity framework -- common files
 freeipa-server - FreeIPA centralized identity framework -- server
 freeipa-server-dns - FreeIPA centralized identity framework -- IPA DNS 
integration
 freeipa-server-trust-ad - FreeIPA centralized identity framework -- AD trust 
installer
 freeipa-tests - FreeIPA centralized identity framework -- tests
 python-ipaclient - FreeIPA centralized identity framework -- Python modules 
for ipac
 python-ipalib - FreeIPA centralized identity framework -- shared Python modules
 python-ipaserver - FreeIPA centralized identity framework -- Python modules 
for serv
 python-ipatests - FreeIPA centralized identity framework -- Python modules for 
test
Closes: 887814
Changes:
 freeipa (4.6.2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Remove upstreamed patches:
   add-debian-platform.diff,
   ipa-kdb-support-dal-version-5-and-6.diff,
   purge-firefox-extension.diff,
   fix-ipa-otpd-install.diff,
   fix-ipa-otpd-service.diff,
   purge-firefox-extension.diff,
   prefix.patch,
   fix-kdcproxy-path.diff,
   fix-is-running.diff,
   fix-pkcs11-helper.diff,
   fix-dnssec-services.diff
 - Remove obsolete patches: fix-memcached.diff,
   fix-oddjobs.diff,
   fix-kdcproxy-paths.diff
 - Refresh rest of the patches
   * control et al: Memcached is not used anymore.
   * control, 

Bug#887815: network-manager-iodine FTBFS with network-manager 1.10.2-1

[Guido Günther]

Dear NM maintainers,
On Sat, Jan 20, 2018 at 08:07:47AM +0200, Adrian Bunk wrote:
> Source: network-manager-iodine
> Version: 1.2.0-1
> Severity: serious
> Tags: buster sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/network-manager-iodine.html
> 
> ...
> gcc -DHAVE_CONFIG_H -I. -I..  -pthread -I/usr/include/libnm 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 
> -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -DG_DISABLE_DEPRECATED 
> -DBINDIR=\"/usr/bin\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" 
> -DVERSION="\"1.2.0\"" -DLIBDIR=\""/usr/lib/x86_64-linux-gnu"\" 
> -DLIBEXECDIR=\""/usr/lib/NetworkManager"\" -DLOCALSTATEDIR=\""/var"\" 
> -DDATADIR=\"/usr/share\" -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -std=gnu89 -g 
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wshadow 
> -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement 
> -Wstrict-prototypes -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare 
> -fno-strict-aliasing -Werror -c -o nm-iodine-service.o nm-iodine-service.c
> In file included from /usr/include/libnm/nm-utils.h:38:0,
>  from /usr/include/libnm/nm-setting-ip-config.h:31,
>  from /usr/include/libnm/nm-setting-ip4-config.h:30,
>  from /usr/include/libnm/NetworkManager.h:72,
>  from nm-iodine-service.c:45:
> /usr/include/libnm/nm-setting-tc-config.h:43:1: error: 'NMTCQdisc' is 
> deprecated: Not available before 1.10.2 [-Werror=deprecated-declarations]
>  voidnm_tc_qdisc_ref  (NMTCQdisc *qdisc);
>  ^~~~

We simply include NetworkManager.h here and don't use nm_tc_qdisc_ref. I
wonder what we could do different?
Cheers,
 -- Guido

Processed: tagging 887762

[Debian Bug Tracking System]

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

> tags 887762 + pending
Bug #887762 [src:gcc-mingw-w64] gcc-mingw-w64 FTBFS with gcc-7-source 7.2.0-19
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887798: firefox-esr: impossible to connect to Google domains

[Vincent Lefevre]

On 2018-01-20 01:32:11 +0100, Vincent Lefevre wrote:
> 
> Your connection is not secure
> 
> The owner of www.google.fr has configured their website improperly. To
> protect your information from being stolen, Firefox has not connected
> to this website.
> 
> This site uses HTTP Strict Transport Security (HSTS) to specify that
> Firefox may only connect to it securely. As a result, it is not
> possible to add an exception for this certificate.
> 
> 
> And after clicking on "Advanced":
> 
> 
> www.google.fr uses an invalid security certificate.
> 
> The certificate is not trusted because the issuer certificate is unknown. The 
> server might not be sending the appropriate intermediate certificates. An 
> additional root certificate may need to be imported.
> 
> Error code: SEC_ERROR_UNKNOWN_ISSUER
> 

As a temporary and insecure workaround, I can avoid this error by
setting security.OCSP.require to false, even though the error was
not about OCSP.

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

Bug#878479: marked as done (pypy runs into 150 minute timeout on slower buildds)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 10:24:32 +
with message-id 
and subject line Bug#878479: fixed in pypy 5.10.0+dfsg-3
has caused the Debian Bug report #878479,
regarding pypy runs into 150 minute timeout on slower buildds
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.)


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

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

...
[backendopt:malloc] removed 23295 simple mallocs in total
[backendopt:mergeifblocks] starting to merge if blocks
#*.++*%%%*+.
+**+++..
...+*%%##%%**...
...++***++..
...*%+*%%*++..++
...+%%*.

..%+
...*#%+..+++
.+%+#%*+...*%.[-32e57] translation-task}

[translation:info] inserting stack checks...
[-32e57] {translation-task
starting stackcheckinsertion_lltype
..
[rtyper] -=- specialized 7 more blocks -=-
E: Build killed with signal TERM after 150 minutes of inactivity


I tried a manual build on armel and it did succeed,
the problem might be that some part of this test
takes more than 150 minutes without outputting anything.
--- End Message ---
--- Begin Message ---
Source: pypy
Source-Version: 5.10.0+dfsg-3

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pypy 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, 20 Jan 2018 21:06:44 +1100
Source: pypy
Binary: pypy pypy-tk pypy-lib pypy-lib-testsuite pypy-doc pypy-dev
Architecture: source
Version: 5.10.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Stefano Rivera 
Changed-By: Stefano Rivera 
Description:
 pypy   - fast alternative implementation of Python - PyPy interpreter
 pypy-dev   - header files for PyPy (an alternative Python interpreter)
 pypy-doc   - developer Documentation for PyPy (an alternative Python interpret
 pypy-lib   - standard library for PyPy (an alternative Python interpreter)
 pypy-lib-testsuite - standard library test suite for PyPy (an alternative 
Python inter
 pypy-tk- Tkinter module for PyPy (an alternative Python interpreter)
Closes: 878479
Changes:
 pypy (5.10.0+dfsg-3) unstable; urgency=medium
 .
   * Patch: dots-stackcheck: Print more dots to avoid timing out on slower
 buildds (Closes: #878479)
Checksums-Sha1:
 1a4ee02afd8e92455e1eb740f1677fedaf5b6841 2337 pypy_5.10.0+dfsg-3.dsc
 d6906216e2b7a667cc06f5924a906d9eea902dc4 12595676 pypy_5.10.0+dfsg.orig.tar.xz
 b78574859e82ae50d7ffaed0996a7cf535cb873b 69136 pypy_5.10.0+dfsg-3.debian.tar.xz
 0b8c485e5f42c44efd3a82841bf6a8850071b75a 9240 
pypy_5.10.0+dfsg-3_source.buildinfo
Checksums-Sha256:
 f8c5eceb0da120b8b18c8bf63bd3207e115085b86f5970c0b9f355c60dfa0d9e 2337 
pypy_5.10.0+dfsg-3.dsc
 08a87ee46d02fa5ee6d951c7200ea0194590b880e911419ae62d2ce452758f8b 12595676 
pypy_5.10.0+dfsg.orig.tar.xz
 c21d71721065a664135511270679947b28f83a33c6a02adf20a85ac75e0b5696 69136 
pypy_5.10.0+dfsg-3.debian.tar.xz
 d00336fce2677eb0ab43ba92516e3e5da254ff0ee58bdca71784b482a0d7c5d1 9240 
pypy_5.10.0+dfsg-3_source.buildinfo
Files:
 946ffd03d9bf3714ba99e775dec5171b 2337 python optional pypy_5.10.0+dfsg-3.dsc
 8e7d1dd467a2b549ef3ea4012c23af5b 12595676 python optional 
pypy_5.10.0+dfsg.orig.tar.xz
 170a9a50263868ab5b310951ee9f8534 69136 python 

Bug#879452: marked as done (src:python-git: Incompatible with git 2.15?)

[Debian Bug Tracking System]

Your message dated Sat, 20 Jan 2018 10:04:36 +
with message-id 
and subject line Bug#879452: fixed in python-git 2.1.8-1
has caused the Debian Bug report #879452,
regarding src:python-git: Incompatible with git 2.15?
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.)


-- 
879452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-git
Version: 2.1.6-1
Tags: upstream
Severity: grave

Dear Maintainer,

in an attempt to use bro-pkg to install packaged scripts into the Bro
network sensor, I ran into the following problem:

,
| $ sudo bro-pkg --verbose install https://github.com/corelight/bro-shellshock
| Traceback (most recent call last):
|   File "/usr/bin/bro-pkg", line 1947, in 
| main()
|   File "/usr/bin/bro-pkg", line 1943, in main
| args.run_cmd(manager, args, config)
|   File "/usr/bin/bro-pkg", line 346, in cmd_install
| prefer_installed=False)
|   File "/usr/lib/python3/dist-packages/bropkg/manager.py", line 1053, in info
| return self._info(package, status, version)
|   File "/usr/lib/python3/dist-packages/bropkg/manager.py", line 1095, in _info
| versions = _get_version_tags(clone)
|   File "/usr/lib/python3/dist-packages/bropkg/manager.py", line 2048, in 
_get_version_tags
| for tagref in clone.tags:
|   File "/usr/lib/python3/dist-packages/git/repo/base.py", line 335, in tags
| return TagReference.list_items(self)
|   File "/usr/lib/python3/dist-packages/git/util.py", line 932, in list_items
| out_list.extend(cls.iter_items(repo, *args, **kwargs))
|   File "/usr/lib/python3/dist-packages/git/refs/symbolic.py", line 613, in 
_iter_items
| for sha, rela_path in cls._iter_packed_refs(repo):  # @UnusedVariable
|   File "/usr/lib/python3/dist-packages/git/refs/symbolic.py", line 97, in 
_iter_packed_refs
| raise TypeError("PackingType of packed-Refs not understood: %r" % line)
| TypeError: PackingType of packed-Refs not understood: '# pack-refs with: 
peeled fully-peeled sorted'
`

Replacing the installed git/1:2.15.0~rc1-1 (current unstable) with
git/1:2.14.2-1 from testing solves the problem.

This looks like upstream issue
. for
which a pull request
 has been
proposed.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: python-git
Source-Version: 2.1.8-1

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

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated python-git 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, 20 Jan 2018 18:48:00 +0900
Source: python-git
Binary: python-git python3-git python-git-doc
Architecture: source all
Version: 2.1.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: TANIGUCHI Takaki 
Description:
 python-git - Python library to interact with Git repositories - Python 2.7
 python-git-doc - Python library to interact with Git repositories - docs
 python3-git - Python library to interact with Git repositories - Python 3.x
Closes: 879452 880446
Changes:
 python-git (2.1.8-1) unstable; urgency=medium
 .
   * New upstream version 2.1.8 (Closes: #880446)
 - Fix "Incompatible with git 2.15?" (Closes: #879452)
   * debian/control: Replace python3-sphinx instead of python2-sphinx
   * delete debian/patches/0001-recognize-the-new-packed-ref-header-format.patch
 Upstream merged
Checksums-Sha1:
 dce8a183cbb1a64abb939c3e7e6f206204b3905d 2441 python-git_2.1.8-1.dsc
 8d533251b2c7eec7b4ed8631969cc9a8d168 431074 python-git_2.1.8.orig.tar.gz
 b6584d453d564b9c04978d6a4e5aeee47816c662 6072 python-git_2.1.8-1.debian.tar.xz
 45933352d143632df2a509f71c9dc42fe21640b8 125656 python-git-doc_2.1.8-1_all.deb
 

Bug#887775: libgnomekbd FTBFS: symbol differences

[Simon McVittie]

On Fri, 19 Jan 2018 at 22:35:01 +0200, Adrian Bunk wrote:
> - gkbd_indicator_VOID__VOID@Base 3.26.0
> +#MISSING: 3.26.0-2# gkbd_indicator_VOID__VOID@Base 3.26.0

> - gkbd_keyboard_drawing_VOID__UINT@Base 3.26.0
> +#MISSING: 3.26.0-2# gkbd_keyboard_drawing_VOID__UINT@Base 3.26.0

These are both "marshallers" generated by glib-genmarshal, and because
of their commonly-used type signatures they duplicate standard functions
provided by GLib itself (g_cclosure_marshal_VOID__VOID and
g_cclosure_marshal_VOID__UINT). When glib-genmarshal generates header
files, it makes those duplicate marshallers into a #define for the
ones in GLib.

Until recently, when glib-genmarshal generated function bodies, it
generated (unnecessary) bodies for these duplicates too; but now it
skips them.

This is *technically* an ABI break, but these functions aren't really
meant to be public ABI, a library user would have to go out of their
way (#undef the aliases for GLib functions) to call them, and codesearch
doesn't see any references. So I think they can be removed from the
symbols file or marked (optional).

smcv

Processed: Re: [debhelper-devel] Bug#887727: debhelper, dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch moreinfo
Bug #887727 [debhelper] debhelper,dh-dist-zilla: dh-dist-zilla based package 
builds no more run dh_auto_install (and maybe other dh_auto_*)
Added tag(s) patch and moreinfo.

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

Bug#887727: [debhelper-devel] Bug#887727: debhelper, dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*)

[Niels Thykier]

Control: tags -1 patch moreinfo

Axel Beckert:
> Package: debhelper,dh-dist-zilla
> Version: debhelper/10.10.6
> Severity: serious
> Tags: sid buster
> Control: affects -1 src:roary src:systray-mdstat
> 
> Hi,
> 
> Sascha Steinbiss  (X-Debbugs-Cc'ed) made me aware
> that at least two dh-dist-zilla based source packages (roary and
> systray-mdstat) produce more or less empty packages when build now
> (but don't FTBFS and in case of systray-mdstat not even throw a single
> lintian warning).
> 
> An DH_VERBOSE=1 build log reveals that dh_auto_install is no more
> called in the build. (This probably also counts for other dh_auto_*
> scripts.) This smells a lot like being caused by this change in
> debhelper/10.10.6 (uploaded November 2017, i.e. shortly after the
> latest uploads of the two mentioned packages):
> 
>   * dh,dh_auto_*: Support skipping all of the dh_auto_* helpers if the
> package does not seem to have a build system (and there are no
> build system related options passed to dh).
> 
> Which is this commit:
> https://anonscm.debian.org/git/debhelper/debhelper.git/commit/?id=52bf7ef7
> 
> Reverting this commit fixes the issue as dh_auto_install is called
> again.
> 
> So I now wonder:
> 
> * Is this a bug in debhelper? I.e. does the new (additional?)
>   buildsystem detection not work properly?
> 
> * Or is this a bug in dh-dist-zilla and it should have declared
>   something in
>   /usr/share/perl5/Debian/Debhelper/Sequence/dist_zilla.pm
>   which wasn't relevant yet, but is now?
> 
>   Regards, Axel
> 

Hi Axel and Sascha,

Thanks for reporting the bug.

Could you please verify that the attached patch fixes the problem for you?

Thanks,
~Niels
>From 903a802b449d840cbf43eb3ffd3147e433bfaa1b Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sat, 20 Jan 2018 09:38:35 +
Subject: [PATCH] dh: Always run commands with sequence defined options

Signed-off-by: Niels Thykier 
---
 dh | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/dh b/dh
index 47160317..787462aa 100755
--- a/dh
+++ b/dh
@@ -998,6 +998,9 @@ sub can_skip {
 	return 0 if $user_specified_options ||
 		(exists $ENV{DH_OPTIONS} && length $ENV{DH_OPTIONS});
 
+	return 0 if exists($command_opts{$command})
+		and @{$command_opts{$command}};
+
 	if (! defined $skipinfo{$command}) {
 		$skipinfo{$command}=[extract_skipinfo($command)];
 	}
-- 
2.15.1

Processed: reassign 887752

[Debian Bug Tracking System]

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

> reassign 887752 src:pillow 5.0.0-1
Bug #887752 [src:didjvu] didjvu: FTBFS and Debci failure with python-pil 5.0.0-1
Bug reassigned from package 'src:didjvu' to 'src:pillow'.
No longer marked as found in versions didjvu/0.8.1-2.
Ignoring request to alter fixed versions of bug #887752 to the same values 
previously set
Bug #887752 [src:pillow] didjvu: FTBFS and Debci failure with python-pil 5.0.0-1
Marked as found in versions pillow/5.0.0-1.
> retitle 887752 pillow: TIFFReadScanline: scanline oriented access is not 
> supported for downsampled JPEG compressed images
Bug #887752 [src:pillow] didjvu: FTBFS and Debci failure with python-pil 5.0.0-1
Changed Bug title to 'pillow: TIFFReadScanline: scanline oriented access is not 
supported for downsampled JPEG compressed images' from 'didjvu: FTBFS and Debci 
failure with python-pil 5.0.0-1'.
> forwarded 887752 https://github.com/python-pillow/Pillow/issues/2926
Bug #887752 [src:pillow] pillow: TIFFReadScanline: scanline oriented access is 
not supported for downsampled JPEG compressed images
Set Bug forwarded-to-address to 
'https://github.com/python-pillow/Pillow/issues/2926'.
> affects 887752 + src:didjvu
Bug #887752 [src:pillow] pillow: TIFFReadScanline: scanline oriented access is 
not supported for downsampled JPEG compressed images
Added indication that 887752 affects src:didjvu
> thanks
Stopping processing here.

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

Bug#887632: Bug#887632: progressivemauve FTBFS with glibc 2.26

[Andreas Tille]

Hi Fabian,

On Fri, Jan 19, 2018 at 04:30:43PM +0100, Fabian Klötzl wrote:
> This bug is easily fixed by forcing mauve to use the native getopt. A
> half-hearted fix is pushed.

Works.

> However, I have trouble removing the
> unnecessary files from the orig tarball, because the pristine-tar branch
> contains only a .delta and a .id file?

That is the usual layout.  You could have either have done a `gbp-build`
before you increased the version number to obtain the orig.tar.xz or
simply `apt-get source` to get the orig tarball.  Than you add the +dfsg
to the version and do:

   mk-origtargz 

to obtain the new tarball.
 
> Any help would be appreciated.

Package uploaded - thanks for your help

 Andreas. 

-- 
http://fam-tille.de

Bug#859543: openhpi: diff for NMU version 3.6.1-3.1

[Adrian Bunk]

Control: tags 859543 + pending

Dear maintainer,

I've prepared an NMU for openhpi (versioned as 3.6.1-3.1) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru openhpi-3.6.1/debian/changelog openhpi-3.6.1/debian/changelog
--- openhpi-3.6.1/debian/changelog	2017-09-12 19:50:16.0 +0300
+++ openhpi-3.6.1/debian/changelog	2018-01-20 09:57:25.0 +0200
@@ -1,3 +1,11 @@
+openhpi (3.6.1-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS with OpenSSL 1.1 by honouring OPENSSL_NO_MD2.
+(Closes: #859543)
+
+ -- Adrian Bunk   Sat, 20 Jan 2018 09:57:25 +0200
+
 openhpi (3.6.1-3) unstable; urgency=medium
 
   * Fixed SNMPFLAGS FTBFS (Closes: #870733)
diff -Nru openhpi-3.6.1/debian/control openhpi-3.6.1/debian/control
--- openhpi-3.6.1/debian/control	2017-09-12 19:50:16.0 +0300
+++ openhpi-3.6.1/debian/control	2018-01-20 09:57:25.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Mohan Devarajulu 
 Uploaders: Khalid Aziz 
 Homepage: http://openhpi.org
-Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), autotools-dev, autoconf (>= 2.57), dh-autoreconf, automake(>= 1.9), uuid-dev, libglib2.0-dev (>= 2.2), pkg-config, libltdl-dev, openipmi (>= 2.0.7), libopenipmi-dev (>=2.0.7), libsnmp-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), libsysfs-dev (>= 0.3), libncurses5-dev, libxml2-dev
+Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), autotools-dev, autoconf (>= 2.57), dh-autoreconf, automake(>= 1.9), uuid-dev, libglib2.0-dev (>= 2.2), pkg-config, libltdl-dev, openipmi (>= 2.0.7), libopenipmi-dev (>=2.0.7), libsnmp-dev, libssl-dev, libsysfs-dev (>= 0.3), libncurses5-dev, libxml2-dev
 Standards-Version: 4.0.0
 
 Package: libopenhpi3
diff -Nru openhpi-3.6.1/debian/patches/no-md2.patch openhpi-3.6.1/debian/patches/no-md2.patch
--- openhpi-3.6.1/debian/patches/no-md2.patch	1970-01-01 02:00:00.0 +0200
+++ openhpi-3.6.1/debian/patches/no-md2.patch	2018-01-20 09:57:25.0 +0200
@@ -0,0 +1,32 @@
+Description: Fix FTBFS with OpenSSL 1.1 by honouring OPENSSL_NO_MD2
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/859543
+
+--- openhpi-3.6.1.orig/plugins/ipmidirect/ipmi_auth.cpp
 openhpi-3.6.1/plugins/ipmidirect/ipmi_auth.cpp
+@@ -21,6 +21,7 @@
+ #include "ipmi_auth.h"
+ #include 
+ #include 
++#include 
+ 
+ 
+ cIpmiAuth *
+@@ -32,7 +33,7 @@ IpmiAuthFactory( tIpmiAuthType type )
+ return new cIpmiAuthNone;
+ 
+case eIpmiAuthTypeMd2:
+-#ifdef HAVE_OPENSSL_MD2_H
++#if defined(HAVE_OPENSSL_MD2_H) && !defined(OPENSSL_NO_MD2)
+ return new cIpmiAuthMd2;
+ #else
+ break;
+@@ -78,7 +79,7 @@ cIpmiAuthNone::Check( cIpmiAuthSg /*d*/[
+ }
+ 
+ 
+-#ifdef HAVE_OPENSSL_MD2_H
++#if defined(HAVE_OPENSSL_MD2_H) && !defined(OPENSSL_NO_MD2)
+ #include 
+ 
+ 
diff -Nru openhpi-3.6.1/debian/patches/series openhpi-3.6.1/debian/patches/series
--- openhpi-3.6.1/debian/patches/series	2017-09-12 19:50:16.0 +0300
+++ openhpi-3.6.1/debian/patches/series	2018-01-20 09:57:25.0 +0200
@@ -1,3 +1,4 @@
 makefile_fix.patch
 ipmi_direct_gcc_fix.patch
 snmpflags-fix.patch
+no-md2.patch

Processed: openhpi: diff for NMU version 3.6.1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 859543 + pending
Bug #859543 [src:openhpi] openhpi: Please migrate to openssl1.1 in buster
Added tag(s) pending.

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