Processed: sbcl 2:1.4.11-1 makes pgloader FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pgloader
Bug #908641 [sbcl] sbcl 2:1.4.11-1 makes pgloader FTBFS
Added indication that 908641 affects src:pgloader

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

Bug#908641: sbcl 2:1.4.11-1 makes pgloader FTBFS

[Adrian Bunk]

Package: sbcl
Version: 2:1.4.11-1
Severity: serious
Control: affects -1 src:pgloader

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

...
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/build/1st/pgloader-3.5.2'
mkdir -p build/bin
mkdir -p /build/1st/pgloader-3.5.2/debian/home
buildapp --require sb-posix \
--require sb-bsd-sockets\
--load /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp\
--asdf-path .   \
--asdf-tree /usr/share/common-lisp/systems  \
--load-system asdf-finalizers   \
--load-system asdf-system-connections   \
--load-system pgloader  \
--load src/hooks.lisp   \
--entry pgloader:main   \
--dynamic-space-size 4096   \
--compress-core \
--output build/bin/pgloader
; compiling file "/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" 
(written 12 MAY 2018 08:48:30 AM):

; 
/build/1st/pgloader-3.5.2/debian/home/.cache/common-lisp/sbcl-1.4.11.debian-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-tmpGHU3ALSV.fasl
 written
; compilation finished in 0:00:08.272
;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp"
;; loading system "asdf-finalizers"
;; loading system "asdf-system-connections"
;; loading system "pgloader"
Fatal SIMPLE-ERROR:
  Compilation failed: Undefined instruction: MOVZXD in
 (INST MOVZXD RESULT MEMREF) in 
/usr/share/common-lisp/source/nibbles/sbcl-opt/x86-64-vm.lisp
make[1]: *** [debian/rules:29: override_dh_auto_build-arch] Error 1

Bug#908508: No org-loaddefs.el file could be found from where org.el is loaded

[bzg]

Hi Russ,

Russ Allbery  writes:

> WARNING: No org-loaddefs.el file could be found from where org.el is
> loaded.

This means Org has been packaged without org-loaddefs.el, which needs
to be manually created with ~$ make autoloads.

HTH,

-- 
 Bastien

Processed: Upstream tickets

[Debian Bug Tracking System]

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

> forwarded 908615 https://github.com/silx-kit/pyFAI/issues/888
Bug #908615 [src:pyfai] pyfai: FTBFS and autopkgtest fails with python3.7 in 
supported versions
Set Bug forwarded-to-address to 'https://github.com/silx-kit/pyFAI/issues/888'.
> forwarded 906488 https://bugs.launchpad.net/lifeograph/+bug/1776032
Bug #906488 [src:lifeograph] lifeograph: FTBFS in buster/sid (static assertion 
failed)
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/lifeograph/+bug/1776032'.
> forwarded 906381 https://github.com/lmfit/lmfit-py/pull/467
Bug #906381 [src:lmfit-py] lmfit-py: FTBFS in buster/sid (failing tests)
Set Bug forwarded-to-address to 'https://github.com/lmfit/lmfit-py/pull/467'.
>
End of message, stopping processing here.

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

Bug#895643: [Pkg-freeipa-devel] Bug#895643: Patch for building using default-jdk (openjdk10)

[Timo Aaltonen]

On 12.09.2018 00:27, Hilko Bengen wrote:
> control: tag -1 patch
> 
> Dear maintainer(s),
> 
> here's a patch that fixes the FTBFS issues with openjdk-10 and removes
> the openjdk-8 dependency.
> 
> Unfortunately, I do not know how to test whether the resulting package
> still works.

This is not for jss though?


-- 
t

Bug#908138: marked as done (hddemux: s390x must be added to architectures without knot-resolver)

[Debian Bug Tracking System]

Your message dated Wed, 12 Sep 2018 04:04:10 +
with message-id 
and subject line Bug#908138: fixed in hddemux 0.4-7
has caused the Debian Bug report #908138,
regarding hddemux: s390x must be added to architectures without knot-resolver
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.)


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

knot-resolver is not available om s390x due to
luajit not being availabe.
--- End Message ---
--- Begin Message ---
Source: hddemux
Source-Version: 0.4-7

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated hddemux 
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: Tue, 11 Sep 2018 23:50:01 -0400
Source: hddemux
Binary: hddemux
Architecture: source
Version: 0.4-7
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 hddemux- HTTP/1.x and DNS demultiplexer
Closes: 908138
Changes:
 hddemux (0.4-7) unstable; urgency=medium
 .
   [ Steve Langasek ]
   * Avoid test suite on s390x (Closes: #908138)
Checksums-Sha1:
 dd7356411acf1a31cc8e00ceb17024c65d8b0a22 1562 hddemux_0.4-7.dsc
 b60fd1f6f22e25d1056202c2772007168c6cd90b 7336 hddemux_0.4-7.debian.tar.xz
 18f89c8c05219abb7a3c432ae4a6fbb714c942bd 8003 hddemux_0.4-7_amd64.buildinfo
Checksums-Sha256:
 0af5ad5c8b6a10acaef2d8ccc5925aad3a08cb5c4b56b62e4a7f054b6a5a21d0 1562 
hddemux_0.4-7.dsc
 89daa4678680adfd522556275c5278a35ac11f8b54bf75048bdddaf573c336de 7336 
hddemux_0.4-7.debian.tar.xz
 d8a6a71727ffad97415433bb927c022c2a3cc1d7fa2d398cac6eff698025b991 8003 
hddemux_0.4-7_amd64.buildinfo
Files:
 deec5900a6001752cff41c591fdef9d9 1562 net optional hddemux_0.4-7.dsc
 0449f8c5f7cbf8960ba9cf9eda7bd5de 7336 net optional hddemux_0.4-7.debian.tar.xz
 d00fbfbca0f3545d3a76fcd43dfe3866 8003 net optional 
hddemux_0.4-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW5iNJQAKCRBsHx7ezFD6
U3+UAP9U8h/7SpdCFJBRpoOgju65oZuY+Mnthlse2cZCKdFQBwEA9Z0nNMb2Tlf1
Y5SY6tB9Z65mqJsRwCRnNU/oTMZPZAY=
=Cohj
-END PGP SIGNATURE End Message ---

Bug#906512: marked as done (uftrace: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 12 Sep 2018 03:34:16 +
with message-id 
and subject line Bug#906512: fixed in uftrace 0.9.0-1
has caused the Debian Bug report #906512,
regarding uftrace: FTBFS in buster/sid (failing tests)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
LDFLAGS=-Wl,-z,now,-z,relro ./configure --prefix=/usr --libdir=/usr/lib/uftrace
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
  GEN  version.h
gcc -O2 -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote 
/<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
-Wno-missing-field-initializers -DHAVE_CXA_DEMANGLE -DHAVE_PERF_CLOCKID 
-DHAVE_PERF_CTXSW  -fPIE -c -o /<>/uftrace.o 
/<>/uftrace.c
gcc -O2 -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote 
/<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
-Wno-missing-field-initializers -DHAVE_CXA_DEMANGLE -DHAVE_PERF_CLOCKID 
-DHAVE_PERF_CTXSW  -fPIE -c -o /<>/cmd-recv.o 
/<>/cmd-recv.c
gcc -O2 -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<> -iquote 
/<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
-Wno-missing-field-initializers -DHAVE_CXA_DEMANGLE -DHAVE_PERF_CLOCKID 
-DHAVE_PERF_CTXSW  -fPIE -c -o /<>/cmd-script.o 
/<>/cmd-script.c

[... snipped ...]

065 arg_order   : NG NG NG NG NG SK SK SK SK SK
066 no_demangle : NG NG NG NG NG NG NG NG NG NG
067 report_diff : NG NG NG NG NG NG NG NG NG NG
068 filter_time_A   : NG NG NG NG NG SK SK SK SK SK
069 graph   : NG NG NG NG NG NG NG NG NG NG
070 graph_backtrace : NG NG NG NG NG NG NG NG NG NG
071 graph_depth : NG NG NG NG NG NG NG NG NG NG
072 no_comment  : NG NG NG NG NG NG NG NG NG NG
073 lib_filter  : NG NG NG NG NG NG NG NG NG NG
074 lib_trigger : NG NG NG NG NG NG NG NG NG NG
075 lib_arg : NG NG NG NG NG SK SK SK SK SK
076 lib_replay_F: NG NG NG NG NG NG NG NG NG NG
077 lib_replay_T: NG NG NG NG NG NG NG NG NG NG
078 max_stack   : NG NG NG NG NG NG NG NG NG NG
079 replay_kernel_D : SK SK SK SK SK SK SK SK SK SK
080 replay_kernel_D2: SK SK SK SK SK SK SK SK SK SK
081 kernel_depth: SK SK SK SK SK SK SK SK SK SK
082 arg_many: NG NG NG NG NG SK SK SK SK SK
083 arg_float   : NG NG NG NG NG SK SK SK SK SK
084 arg_mixed   : NG NG NG NG NG SK SK SK SK SK
085 arg_reg : NG NG NG NG NG SK SK SK SK SK
086 arg_stack   : NG NG NG NG NG SK SK SK SK SK
087 arg_variadic: NG NG NG NG NG SK SK SK SK SK
088 graph_session   : NG NG NG NG NG NG NG NG NG NG
089 graph_exit  : NG NG NG NG NG NG NG NG NG NG
090 report_recursive: NG NG NG NG NG NG NG NG NG NG
091 replay_tid  : NG NG NG NG NG NG NG NG NG NG
092 report_tid  : NG NG NG NG NG NG NG NG NG NG
Traceback (most recent call last):
  File "./runtest.py", line 518, in 
result = run_single_case(name, flags, opts.split(), arg.diff, arg.debug)
  File "./runtest.py", line 424, in run_single_case
ret = tc.run(case, cflags, diff)
  File "/<>/tests/runtest.py", line 324, in run
result_tested = self.sort(result_origin)  # for python3
  File "/<>/tests/runtest.py", line 284, in sort
return func(self, output, ignore_children)
  File "/<>/tests/runtest.py", line 205, in report_sort
if line[5].startswith('__'):
IndexError: list index out of range
make[3]: *** [Makefile:16: test_run] Error 1
make[2]: *** [Makefile:242: test] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Bug#908568: nvidia-driver: build error

[Russ Allbery]

Vincent Lefevre  writes:
> On 2018-09-11 15:29:02 -0700, Russ Allbery wrote:
>> Vincent Lefevre  writes:

>>> This would mean that a breakage is possible after any patch (in
>>> particular with those "Update to SVN..." in the changelog).  Thus this
>>> means that the kernel module build system must check that the GCC
>>> Debian package version number matches the one used to build the
>>> kernel. For sid, GCC is often not in sync with the one used to build
>>> the kernel. This is a really big problem.

>> I don't think it's an NVIDIA-specific problem, though, right?  Doesn't
>> this happen with any kernel module build?

> I assume that this depends on which features of the interface are
> used.

Sorry, I should have checked before replying.  This is indeed an
NVIDIA-specific check in conftest.sh, not a general Linux issue.  It's not
doing any complicated logic; it's just parsing the version string and
aborting the compilation if it doesn't match.

If you set IGNORE_CC_MISMATCH=1 in the environment before installing the
package, does everything build and work correctly?

Apparently fglrx had a similar check, and the package maintainers chose to
patch it out.

-- 
Russ Allbery (r...@debian.org)   

Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Dale Harris]

On Tue, 11 Sep 2018 20:53:28 +0200 Sebastian Andrzej Siewior 
 wrote:
> On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> > Dmitry already implemented my short-term workaround:
> > https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
> > 
> > When this has been built on all release architectures openssl can bump 
> > the version requirement.
> > 
> > Even more cautious would be to wait until testing migration of Qt.
> 
> now after what happens I consider this issue (#908567) fixed since the
> only affected package by this is fixed. Also adding versioned depends is
> not easy as I expected it in the morning without too much mess around
> it.
> 
> > cu
> > Adrian
> 
> Sebastian
> 
> 

Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Dale Harris]

On Tue, 11 Sep 2018 20:53:28 +0200 Sebastian Andrzej Siewior 
 wrote:
> On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> > Dmitry already implemented my short-term workaround:
> > https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
> > 
> > When this has been built on all release architectures openssl can bump 
> > the version requirement.
> > 
> > Even more cautious would be to wait until testing migration of Qt.
> 
> now after what happens I consider this issue (#908567) fixed since the
> only affected package by this is fixed. Also adding versioned depends is
> not easy as I expected it in the morning without too much mess around
> it.
> 
> > cu
> > Adrian
> 
> Sebastian
> 
> 

Bug#908616: OpenAFS security release

[Benjamin Kaduk]

On Tue, Sep 11, 2018 at 10:02:20PM +0200, Salvatore Bonaccorso wrote:
> Hey!
> 
> On Tue, Sep 11, 2018 at 02:30:51PM -0500, Benjamin Kaduk wrote:
> > Source: openafs
> > Version: 1.6.9-2+deb8u7
> > Tags: security
> > Severity: serious
> > 
> > OpenAFS upstream released security releases 1.6.23 and 1.8.2 today, fixing:
> > http://openafs.org/pages/security/OPENAFS-SA-2018-001.txt
> > http://openafs.org/pages/security/OPENAFS-SA-2018-002.txt
> > http://openafs.org/pages/security/OPENAFS-SA-2018-003.txt
> > 
> > No CVEs have been assigned yet.
> 
> Would it be possible, that you with both your maintainers and upstream
> part could request accordingly CVEs via http://cveform.mitre.org/ (and
> then loop back the assignment here once got those).

OPENAFS-SA-2018-001 is CVE-2018-16947.
OPENAFS-SA-2018-002 is CVE-2018-16948.
OPENAFS-SA-2018-003 is CVE-2018-16949.

-Ben

Bug#908568: nvidia-driver: build error

[Vincent Lefevre]

On 2018-09-11 15:29:02 -0700, Russ Allbery wrote:
> Vincent Lefevre  writes:
> 
> > This would mean that a breakage is possible after any patch (in
> > particular with those "Update to SVN..." in the changelog).  Thus this
> > means that the kernel module build system must check that the GCC Debian
> > package version number matches the one used to build the kernel. For
> > sid, GCC is often not in sync with the one used to build the
> > kernel. This is a really big problem.
> 
> I don't think it's an NVIDIA-specific problem, though, right?  Doesn't
> this happen with any kernel module build?

I assume that this depends on which features of the interface are
used.

> Or am I confused and this is an NVIDIA-specific check?

I don't know. It would be interesting to know the causes of the
failures.

I tried to search for information and found:

  https://www.kernel.org/doc/html/v4.14/process/stable-api-nonsense.html

Some issues may come from the kernel build options, and concerning
the compiler:

  "Depending on the version of the C compiler you use, different
  kernel data structures will contain different alignment of
  structures, and possibly include different functions in different
  ways (putting functions inline or not.) The individual function
  organization isn’t that important, but the different data structure
  padding is very important."

Well, concerning the alignment of structures and internal padding,
this is a much more general problem that could affect any library
that expose structures in their .h public header files. I assume
that this will never change, otherwise one would see a breakage
in various places. So, I'm wondering why this is mentioned.

Concerning inline functions, this would need explanations. In any
case, I don't see why this would change between minor versions.
And this is more likely to be affected by compiler options.

Moreover, it appears that NVIDIA's compiler version check predates
the change of numbering in GCC. See for instance:

  
https://devtalk.nvidia.com/default/topic/833061/nvidia-drivers-352-09-dont-install/

"Compiler version check failed:

The major and minor number of the compiler used to
compile the kernel:

gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

does not match the compiler used here:

cc (Ubuntu 4.9.2-0ubuntu1~14.04) 4.9.2"

In the past, GCC 4.6, 4.7, 4.8, 4.9 were indeed different releases,
but now, only the major number corresponds to some given release:
5, 6, 7, 8, 9 (GCC was using X.Y.Z where Z was a patchlevel, and
now uses X.Y where Y is a patchlevel, thus to be consistent with
the past test, NVIDIA should now just check X).

https://devtalk.nvidia.com/default/topic/960778/linux/having-trouble-with-the-340-96-driver-on-kali-linux-failing-cc-version-check/

says: "That's because the ABI (i.e. how parameters are passed, or
how the stack is laid out) changes between gcc versions, especially
between major version changes (here, v5's ABI is incompatible with
V6's)."

Thus only the *major* version matters.

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

Bug#879139: marked as done (piccolo: Transition to SWT 4)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 23:51:55 +
with message-id 
and subject line Bug#879139: fixed in piccolo 1.2-1.1
has caused the Debian Bug report #879139,
regarding piccolo: Transition to SWT 4
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.)


-- 
879139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: piccolo
Version: 1.2
Severity: important

Hi,

piccolo depends on libswt-gtk-3-java which is going to be removed
in a near future. Could you please apply the patch provided to build
with libswt-gtk-4-java instead?

Thank you,

Emmanuel Bourg
diff --git a/debian/control b/debian/control
index 94e020e..0b4d0fd 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,7 @@
 Source: piccolo
 Priority: extra
 Maintainer: Javier Fernández-Sanguino Peña 
-Build-Depends: debhelper (>= 8.0.0), javahelper (>=0.25), libswt-gtk-3-java, 
quilt
+Build-Depends: debhelper (>= 8.0.0), javahelper (>=0.25), libswt-gtk-4-java, 
quilt
 Build-Depends-Indep: default-jdk, ant, junit
 Standards-Version: 3.9.2
 Section: java
diff --git a/debian/linkjars b/debian/linkjars
index f86c5b1..dca753a 100644
--- a/debian/linkjars
+++ b/debian/linkjars
@@ -1,3 +1,3 @@
 ant.jar
 junit.jar
-swt.jar
+swt4.jar
diff --git a/debian/rules b/debian/rules
index cfa2186..5901bf6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,7 @@ include /usr/share/quilt/quilt.make
 include /usr/share/javahelper/java-vars.mk
 
 export JAVA_HOME=/usr/lib/jvm/default-java
-export 
CLASSPATH=/usr/share/java/ant.jar:/usr/share/java/junit.swf:/usr/share/java/swt.jar
+export 
CLASSPATH=/usr/share/java/ant.jar:/usr/share/java/junit.swf:/usr/share/java/swt4.jar
 
 %:
dh $@ --with javahelper --with quilt
--- End Message ---
--- Begin Message ---
Source: piccolo
Source-Version: 1.2-1.1

We believe that the bug you reported is fixed in the latest version of
piccolo, 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.
Emmanuel Bourg  (supplier of updated piccolo 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, 12 Sep 2018 01:04:38 +0200
Source: piccolo
Binary: libpiccolo-java
Architecture: source
Version: 1.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Emmanuel Bourg 
Description:
 libpiccolo-java - toolkit for development of 2D structured graphics
Closes: 879139
Changes:
 piccolo (1.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Transition to SWT 4 (Closes: #879139)
Checksums-Sha1:
 da9860fc9cabff048ed8558e6622a0909ecb90d4 1851 piccolo_1.2-1.1.dsc
 d136f88f3e310f98312ade4fe993110e1bc066f4 9532 piccolo_1.2-1.1.debian.tar.xz
 0f7f55b7a877392533381187944cc7e8f0b836c3 9669 piccolo_1.2-1.1_source.buildinfo
Checksums-Sha256:
 cb74922cc0f879810dd165a7297fe46a87295af936ce9bb527c55270de2daf5b 1851 
piccolo_1.2-1.1.dsc
 35c0a99ddd7289f59db67c9d1565f8d096e69133ffaa3de44fbfc68b523031cf 9532 
piccolo_1.2-1.1.debian.tar.xz
 7fa1bf99895ed5500c617929893865be49d287d02810aa31b42201891b1ed0b1 9669 
piccolo_1.2-1.1_source.buildinfo
Files:
 0450be428e2fec680ac1f77f368672ed 1851 java extra piccolo_1.2-1.1.dsc
 6d29831e7effb9ec663b6c4fb51e0fed 9532 java extra piccolo_1.2-1.1.debian.tar.xz
 c45d1ea7b2f6787d1645153df7e9ca2d 9669 java extra 
piccolo_1.2-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAluYSqUSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs5qcQALIxM5XAsJFLj8TXiXBX+qDDmabTESPt
V49fnQ166CkLWw4vnzUYuyo+dGpnWnH3Xx0X2zvDFH3XxPpJoyZmnaI5ZGkHU/Yb
QkncY75U7AXwKoUruwayM0XrwVunFQa+5ArbrGEJ1mDzaKjv6ZXKZr+yuRlTZ+Rj
0mVjYbzPezMgCUYlSjcN6imtF30ClDjcNCGSRy31FHYmYDC/krbh+s6XdtDs1ua1
84FLajJI4ZrTW4mYhMRAuTLToz7Hb6++408WWKjXqQCtUhDzE2kB+Z5ed/PVjvSU
1cisN71eW6tKV2SycLg/bXPlDSxceRL/DjWKrI0t4LZdDMf10NUnMHn428DxFctz
KcnzI73Gi64mDt1RXjPwV0mPHgXRKB1H+182vKpkh4A7gTTA28KxQWM1Pt5PKc4q
GN2acXaJyGdxlKdfITEdVJ9jMlJpzKZ+HVgdEbi3pXuc5DIVQ65iIx8VIfkZblIS
CzNY+AI7or5Zk+u3Wfffpc3fSyESCmrH2ueOKPNsb/F6rci6SNuqSu5AAV5q6dZE

Bug#908571: marked as done (gxneur FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 23:49:39 +
with message-id 
and subject line Bug#908571: fixed in gxneur 0.20.0-2
has caused the Debian Bug report #908571,
regarding gxneur FTBFS with glib 2.58
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.)


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

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

...
tray_widget.c: In function 'gtk_tray_icon_class_init':
tray_widget.c:108:2: error: 'g_type_class_add_private' is deprecated 
[-Werror=deprecated-declarations]
  g_type_class_add_private (class, sizeof (GtkTrayIconPrivate));
  ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:34,
 from /usr/include/gtk-2.0/gtk/gtkprivate.h:30,
 from tray_widget.c:22:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:564: gxneur-tray_widget.o] Error 1
--- End Message ---
--- Begin Message ---
Source: gxneur
Source-Version: 0.20.0-2

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated gxneur package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Sep 2018 01:14:50 +0300
Source: gxneur
Binary: gxneur
Architecture: source amd64
Version: 0.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Description:
 gxneur - GTK+ frontend for xneur keyboard layout switcher
Closes: 886066 908571
Changes:
 gxneur (0.20.0-2) unstable; urgency=medium
 .
   * d/control: Move Vcs-* to salsa.
   * d/control: Bump Standards-Version: no changes needed.
   * Remove gconf dependence: add debian/patches/*-gconf.patch (Closes: #886066)
   * Add 03-glib-deprecated.patch: Fix FTBFS with glib 2.58 (Closes: #908571)
   * Remove legacy menu file.
   * d/control: Remove dh-autoreconf build dependence.
Checksums-Sha1:
 378fc2a1f274bc1794e393bb1a175a2f7de1bed6 1570 gxneur_0.20.0-2.dsc
 bef32b7edca11bf4d55cf43789e5b153f5e80a5c 10516 gxneur_0.20.0-2.debian.tar.xz
 86e02e804060ac21a18eb89022bbe7544ce79346 145348 
gxneur-dbgsym_0.20.0-2_amd64.deb
 180cb4d6e24469b84079565e15fed9456bf2523d 12056 gxneur_0.20.0-2_amd64.buildinfo
 be23050a391155163a2669a859edcb0a5d87136e 355516 gxneur_0.20.0-2_amd64.deb
Checksums-Sha256:
 43fd98188e76c38f17b36754464c5459acdf76ca6122122b7171d7dde2cae858 1570 
gxneur_0.20.0-2.dsc
 70a1d4282c22b7ed25accad073dc97897f4f45192f026e14a7392ec81b12c2cb 10516 
gxneur_0.20.0-2.debian.tar.xz
 f2d42ca18ded81bf861af7bd9794b60aa0960dcf9a81574d2a9c482d69b2e21e 145348 
gxneur-dbgsym_0.20.0-2_amd64.deb
 5792ecaa9e712d53cb3dfacfea9e9640663686fe87e7ab17dd5f6f4e708ba6ca 12056 
gxneur_0.20.0-2_amd64.buildinfo
 14cbceae327ca606a6607662191c1a36ebc9cb35a70eda9bc41e8fdd97c976c5 355516 
gxneur_0.20.0-2_amd64.deb
Files:
 9843be7bfd4f8e0c4f5e69723ec8cf69 1570 x11 optional gxneur_0.20.0-2.dsc
 9b128db7fb71301f2212adbb2fbce728 10516 x11 optional 
gxneur_0.20.0-2.debian.tar.xz
 5fd99bef49ea37ce5da3f5cef8788bf2 145348 debug optional 
gxneur-dbgsym_0.20.0-2_amd64.deb
 f61312040898179842e72b2d30150f4c 12056 x11 optional 
gxneur_0.20.0-2_amd64.buildinfo

Processed: bug 908571 is forwarded to https://github.com/AndrewCrewKuznetsov/xneur-devel/pull/30

[Debian Bug Tracking System]

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

> forwarded 908571 https://github.com/AndrewCrewKuznetsov/xneur-devel/pull/30
Bug #908571 [src:gxneur] gxneur FTBFS with glib 2.58
Set Bug forwarded-to-address to 
'https://github.com/AndrewCrewKuznetsov/xneur-devel/pull/30'.
> thanks
Stopping processing here.

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

Bug#908568: nvidia-driver: build error

[Russ Allbery]

Vincent Lefevre  writes:

> This would mean that a breakage is possible after any patch (in
> particular with those "Update to SVN..." in the changelog).  Thus this
> means that the kernel module build system must check that the GCC Debian
> package version number matches the one used to build the kernel. For
> sid, GCC is often not in sync with the one used to build the
> kernel. This is a really big problem.

I don't think it's an NVIDIA-specific problem, though, right?  Doesn't
this happen with any kernel module build?  Or am I confused and this is an
NVIDIA-specific check?

-- 
Russ Allbery (r...@debian.org)   

Bug#908551: apt-listchanges: apt update hangs if no mail system

[Robert Luberda]

RJ pisze:

An issue in apt-listchanges is that handling of Ctrl-C does not work,
when /bin/sh points to dash; this is visible here:

> ^CE: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10
> received signal 2.
> E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10

Pressing Ctrl-C causes apt-listchanges to exit with code 10, so the
above command should return 0, but... dash as parent process receives
SIGINT as well, what ends up with returning code 130.
bash works differently and returns 0, but I guess unfortunately dash
behavior's is correct according to POSIX. I will try to fix this inside
apt-listchanges somehow.

Regards,
robert

Bug#908568: nvidia-driver: build error

[Vincent Lefevre]

Control: retitle -1 nvidia kernel modules build error on GCC version mismatch

On 2018-09-11 09:54:06 -0700, Russ Allbery wrote:
> Vincent Lefevre  writes:
> 
> > Even with just a differing *minor* version? Note that since GCC 5,
> > an update of the minor version should just be bug fixes:
> 
> >   https://gcc.gnu.org/develop.html
> 
> The kernel uses GCC-specific features in an extremely aggressive way.  I'm
> not particularly surprised that ABI compatibility might break across minor
> versions.  Normally the linux-compiler-gcc-* packages express the required
> compiler version for building kernel modules and handle this, but they're
> only an upgrade ratchet, not a downgrade ratchet.  (Plus, that would just
> create an unsatisfiable dependency since the compiler packages aren't
> broken apart that way.)

This would mean that a breakage is possible after any patch
(in particular with those "Update to SVN..." in the changelog).
Thus this means that the kernel module build system must check
that the GCC Debian package version number matches the one used
to build the kernel. For sid, GCC is often not in sync with the
one used to build the kernel. This is a really big problem.

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

Processed: Re: Bug#908568: nvidia-driver: build error

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nvidia kernel modules build error on GCC version mismatch
Bug #908568 [nvidia-kernel-dkms] nvidia-driver: build error
Bug #908597 [nvidia-kernel-dkms] nvidia-kernel-dkms: Unable to upgrade and to 
reinstall
Changed Bug title to 'nvidia kernel modules build error on GCC version 
mismatch' from 'nvidia-driver: build error'.
Changed Bug title to 'nvidia kernel modules build error on GCC version 
mismatch' from 'nvidia-kernel-dkms: Unable to upgrade and to reinstall'.

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

Bug#908609: gtkhash: cannot fulfill the build dependencies

[Unit 193]

Howdy,

A solution to the problem is to pull a commit from upstream and adjust the 
packaging, patch attached.


~Unit 193
Unit193 @ freenode
Unit193 @ OFTCdiff -Nru gtkhash-1.1.1/debian/changelog gtkhash-1.1.1/debian/changelog
--- gtkhash-1.1.1/debian/changelog  2018-07-16 07:46:10.0 -0400
+++ gtkhash-1.1.1/debian/changelog  2018-09-11 17:30:43.0 -0400
@@ -1,3 +1,11 @@
+gtkhash (1.1.1-3.1) unstable; urgency=medium
+
+  * d/p/11-support-thunarx-3.patch: Add upstream commit to support thunarx-3.
+  * d/control: Adjust build-dep: libthunarx-2-dev → libthunarx-3-dev.
+  * d/thunar-gtkhash.install: Adapt to the thunarx-3 path.
+
+ -- Unit 193   Tue, 11 Sep 2018 17:30:43 -0400
+
 gtkhash (1.1.1-3) unstable; urgency=medium
 
   * Fix Vcs-*.
diff -Nru gtkhash-1.1.1/debian/control gtkhash-1.1.1/debian/control
--- gtkhash-1.1.1/debian/control2018-07-16 07:16:59.0 -0400
+++ gtkhash-1.1.1/debian/control2018-09-11 17:30:43.0 -0400
@@ -8,7 +8,7 @@
  nettle-dev,
  libgtk-3-dev (>= 3.0.0),
  libnautilus-extension-dev (>= 3.0),
- libthunarx-2-dev,
+ libthunarx-3-dev,
  libnemo-extension-dev,
  libcaja-extension-dev,
  intltool (>= 0.40.6),
diff -Nru gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 
gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch
--- gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 1969-12-31 
19:00:00.0 -0500
+++ gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 2018-09-11 
17:30:43.0 -0400
@@ -0,0 +1,54 @@
+From 9e35e3a0c248d57c62d064edbc14d3ed02c3bff8 Mon Sep 17 00:00:00 2001
+From: Tristan Heaven 
+Date: Sun, 20 May 2018 18:02:05 +0100
+Subject: [PATCH] add --with-thunarx= configure option for selecting thunarx
+ version (fixes #21)
+
+---
+ configure.ac | 14 ++
+ 1 file changed, 10 insertions(+), 4 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 9b474f2..fd1f99c 100644
+--- a/configure.ac
 b/configure.ac
+@@ -69,7 +69,7 @@ GLIB_GSETTINGS
+ # check for gtk+ {{{
+ AC_MSG_CHECKING([which GTK+ version to use])
+ AC_ARG_WITH([gtk],
+-  [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use [3.0]])],
++  [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use 
[default=3.0]])],
+   [with_gtk="${withval}"], [with_gtk="3.0"])
+ AC_MSG_RESULT([${with_gtk}])
+ 
+@@ -340,12 +340,18 @@ AC_ARG_ENABLE([thunar],
+ AC_MSG_RESULT([${enable_thunar}])
+ AM_CONDITIONAL([ENABLE_THUNAR], [test "${enable_thunar}" = "yes"])
+ 
++AC_MSG_CHECKING([which Thunarx version to use])
++AC_ARG_WITH([thunarx],
++  [AS_HELP_STRING([--with-thunarx=2|3], [Thunarx version to use 
[default=3]])],
++  [with_thunar="${withval}"], [with_thunarx="3"])
++AC_MSG_RESULT([${with_thunarx}])
++
+ if test "${enable_thunar}" = "yes" ; then
+   # Check for thunar
+-  PKG_CHECK_MODULES([THUNAR], [thunarx-2])
++  PKG_CHECK_MODULES([THUNAR], ["thunarx-${with_thunarx}"])
+   AC_SUBST([THUNAR_CFLAGS])
+   AC_SUBST([THUNAR_LIBS])
+-  THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir thunarx-2`
++  THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir 
"thunarx-${with_thunarx}"`
+   AC_SUBST([THUNAR_EXTENSION_DIR])
+ fi
+ # }}}
+@@ -392,7 +398,7 @@ echo "  gtkhash: ${enable_gtkhash} (gtk+-${with_gtk})"
+ echo "  gtkhash-caja: ${enable_caja}"
+ echo "  gtkhash-nautilus: ${enable_nautilus}"
+ echo "  gtkhash-nemo: ${enable_nemo}"
+-echo "  gtkhash-thunar: ${enable_thunar}"
++echo "  gtkhash-thunar: ${enable_thunar} (thunarx-${with_thunarx})"
+ 
+ blake2_funcs="
+   BLAKE2b BLAKE2s BLAKE2bp BLAKE2sp"
+
diff -Nru gtkhash-1.1.1/debian/patches/series 
gtkhash-1.1.1/debian/patches/series
--- gtkhash-1.1.1/debian/patches/series 2018-07-16 07:14:44.0 -0400
+++ gtkhash-1.1.1/debian/patches/series 2018-09-11 17:30:43.0 -0400
@@ -2,3 +2,4 @@
 20-fix-component-id.patch
 30-add-image-screenshot.patch
 40-fix-invalid-tags.patch
+50-support-thunarx-3.patch
diff -Nru gtkhash-1.1.1/debian/thunar-gtkhash.install 
gtkhash-1.1.1/debian/thunar-gtkhash.install
--- gtkhash-1.1.1/debian/thunar-gtkhash.install 2017-12-19 02:45:34.0 
-0500
+++ gtkhash-1.1.1/debian/thunar-gtkhash.install 2018-06-05 17:29:28.0 
-0400
@@ -1,2 +1,2 @@
-usr/lib/*/thunarx-2/libgtkhash-properties-thunar.so
+usr/lib/*/thunarx-3/libgtkhash-properties-thunar.so
 usr/share/appdata/thunar-gtkhash.metainfo.xml usr/share/metainfo

Processed: Patch for building using default-jdk (openjdk10)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #895643 [src:jss] jss build depends on openjdk-8-jdk
Added tag(s) patch.

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

Bug#895643: Patch for building using default-jdk (openjdk10)

[Hilko Bengen]

control: tag -1 patch

Dear maintainer(s),

here's a patch that fixes the FTBFS issues with openjdk-10 and removes
the openjdk-8 dependency.

Unfortunately, I do not know how to test whether the resulting package
still works.

Cheers,
-Hilko
>From 0c6569921d50bc0c9291653f9fe3b2d1cb9d79d8 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Subject: [PATCH] Add a cache for iconv_t handles to hive_t

It was brought to my attention that dumping a registry hive causes a
lot of time spent in disk I/O activity because iconv_open() and
iconv_close() are called for every key. Every iconv_open() call causes
/usr/lib/.../gconv/$ENCODING.so to be opened and mapped.

The iconv_t handles are now cached in the hive_h struct; they are
opened on-demand and re-used.

On my ~10 year old Lenovo T60, I have seen 57% savings in the overal
runtime of running

hivexregedit --export windows-8-enterprise-software.hive '\\'
---
 bootstrap|  1 +
 configure.ac |  2 ++
 lib/Makefile.am  |  2 ++
 lib/handle.c | 42 +-
 lib/hivex-internal.h | 31 ++-
 lib/node.c   |  6 +++---
 lib/utf16.c  | 38 --
 lib/value.c  | 10 +-
 lib/write.c  |  4 ++--
 m4/.gitignore|  2 ++
 10 files changed, 96 insertions(+), 42 deletions(-)

diff --git a/bootstrap b/bootstrap
index bd82477..373fad8 100755
--- a/bootstrap
+++ b/bootstrap
@@ -75,6 +75,7 @@ vc-list-files
 warnings
 xstrtol
 xstrtoll
+threadlib
 '
 
 $gnulib_tool			\
diff --git a/configure.ac b/configure.ac
index 547fb0d..8405774 100644
--- a/configure.ac
+++ b/configure.ac
@@ -38,7 +38,9 @@ AC_DEFINE([PACKAGE_VERSION_RELEASE],[hivex_release],[Release number])
 AC_DEFINE([PACKAGE_VERSION_EXTRA],["hivex_extra"],[Extra version string])
 
 gl_EARLY
+gl_THREADLIB_EARLY
 gl_INIT
+gl_THREADLIB
 
 AM_PROG_LIBTOOL
 
diff --git a/lib/Makefile.am b/lib/Makefile.am
index 4a7cea1..62cdf35 100644
--- a/lib/Makefile.am
+++ b/lib/Makefile.am
@@ -38,6 +38,8 @@ libhivex_la_SOURCES = \
 	visit.c \
 	write.c
 
+libhivex_la_SOURCES += $(top_srcdir)/gnulib/lib/glthread/threadlib.c
+
 libhivex_la_LIBADD =  ../gnulib/lib/libgnu.la $(LTLIBOBJS)
 libhivex_la_LDFLAGS = \
 	-version-info 0:0:0 \
diff --git a/lib/handle.c b/lib/handle.c
index 9dcf81d..01b8d80 100644
--- a/lib/handle.c
+++ b/lib/handle.c
@@ -30,6 +30,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 
 #ifdef HAVE_MMAP
 #include 
@@ -62,6 +64,32 @@ header_checksum (const hive_h *h)
 
 #define HIVEX_OPEN_MSGLVL_MASK (HIVEX_OPEN_VERBOSE|HIVEX_OPEN_DEBUG)
 
+iconv_t *
+_hivex_get_iconv (hive_h *h, recode_type t)
+{
+  glthread_lock_lock (>iconv_cache[t].mutex);
+  if (h->iconv_cache[t].handle == NULL) {
+if (t == utf8_to_latin1)
+  h->iconv_cache[t].handle = iconv_open ("LATIN1", "UTF-8");
+else if (t == latin1_to_utf8)
+  h->iconv_cache[t].handle = iconv_open ("UTF-8", "LATIN1");
+else if (t == utf8_to_utf16le)
+  h->iconv_cache[t].handle = iconv_open ("UTF-16LE", "UTF-8");
+else if (t == utf16le_to_utf8)
+  h->iconv_cache[t].handle = iconv_open ("UTF-8", "UTF-16LE");
+  } else {
+/* reinitialize iconv context */
+iconv (h->iconv_cache[t].handle, NULL, 0, NULL, 0);
+  }
+  return h->iconv_cache[t].handle;
+}
+
+void
+_hivex_release_iconv (hive_h *h, recode_type t)
+{
+  glthread_lock_unlock (>iconv_cache[t].mutex);
+}
+
 hive_h *
 hivex_open (const char *filename, int flags)
 {
@@ -164,11 +192,17 @@ hivex_open (const char *filename, int flags)
 goto error;
   }
 
+  for (int t=0; t<3; t++) {
+glthread_lock_init (>iconv_cache[t].mutex);
+h->iconv_cache[t].handle = NULL;
+  }
+
   /* Last modified time. */
   h->last_modified = le64toh ((int64_t) h->hdr->last_modified);
 
   if (h->msglvl >= 2) {
-char *name = _hivex_windows_utf16_to_utf8 (h->hdr->name, 64);
+char *name = _hivex_recode (h, utf16le_to_utf8,
+h->hdr->name, 64, NULL);
 
 fprintf (stderr,
  "hivex_open: header fields:\n"
@@ -424,6 +458,12 @@ hivex_close (hive_h *h)
   else
 r = 0;
   free (h->filename);
+  for (int t=0; t<3; t++) {
+if (h->iconv_cache[t].handle != NULL) {
+  iconv_close (h->iconv_cache[t].handle);
+  h->iconv_cache[t].handle = NULL;
+}
+  }
   free (h);
 
   return r;
diff --git a/lib/hivex-internal.h b/lib/hivex-internal.h
index 9a497ed..d04ae3c 100644
--- a/lib/hivex-internal.h
+++ b/lib/hivex-internal.h
@@ -22,6 +22,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 
 #include "byte_conversions.h"
 
@@ -35,6 +37,13 @@
 #define STRCASENEQLEN(a,b,n) (strncasecmp((a),(b),(n)) != 0)
 #define STRPREFIX(a,b) (strncmp((a),(b),strlen((b))) == 0)
 
+typedef enum {
+  utf8_to_latin1 = 0,
+  latin1_to_utf8,
+  utf8_to_utf16le,
+  utf16le_to_utf8,
+} recode_type;
+
 struct hive_h {
   char *filename;
   int fd;
@@ -79,6 +88,11 @@ struct hive_h {
   /* Internal data for 

Processed (with 1 error): Re: Bug#908551: apt-listchanges: apt update hangs if no mail system

[Debian Bug Tracking System]

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

> RJ writes:
Unknown command or malformed arguments to command.
> reassign 908551 citadel-server  902-4
Bug #908551 [apt-listchanges] apt-listchanges: apt update hangs if no mail 
system
Bug reassigned from package 'apt-listchanges' to 'citadel-server'.
No longer marked as found in versions apt-listchanges/3.10.
Ignoring request to alter fixed versions of bug #908551 to the same values 
previously set
Bug #908551 [citadel-server] apt-listchanges: apt update hangs if no mail system
Marked as found in versions citadel/902-4.
> thanks
Stopping processing here.

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

Bug#908551: apt-listchanges: apt update hangs if no mail system

[Robert Luberda]

RJ writes:

reassign 908551 citadel-server  902-4
thanks

> 
> Versions of packages apt-listchanges suggests:
> ii  citadel-server [mail-transport-agent]  902-4


> -- Desription of problem:
> When performing a apt update today (Monday, September 10, 2018) there
> was a news bit about the Apache/2 package that required reading and
> confirmation.
> Upon confirmation the apt-listchanges script returned to attempt to send
> mail to the configured user email (which is just 'root' in this case.)

Yes, apt-listchanges tries to execute `/usr/sbin/sendmail -oi -t'
command. It skips sending mails if the command does not exist.

> IF a system either does not have a mail service installed 

You have citadel-server installed, that provides mail service, so it's
not the case.

> or is
> impropery configured, apt-listchanges will hang while attempting to send
> an email before it allows the update process to continue.

IMHO if a mail service is improperly configured than it should fail
instead of hanging... Then apt-listchanges would display warning message
like this (BTW. I've just temporaily installed the latest version of
citadel-server, trying to reproduce the bug, but its sendmail command
just fails, not hangs):

  apt-listchanges: Mail to root: apt-listchanges: changelogs for vox
citmail: can't connect: No such file or directory
apt-listchanges warning: Cannot send mail to root: Command
'['/usr/sbin/sendmail', '-oi', '-t']' returned non-zero exit status 3.

Then apt-listchanges would continue. I agree, that apt-listchanges could
have set some timeout for  the sendmail command, and I can try to add
such timeout in next version.

> 
> ** I was able to work around this by editing the apt-listchanges script
> file by commenting out the offending Mail section as follows:

A simpler solution would be to run `dpkg-reconfigure apt-listchanges'
and give an empty list of e-mail addresses in the question related to
mail addresses.

> As with the other related 'Wishlist' bug reports for apt-listchanges,
> there should be additional prompts added to this file to:
> 
> (1) Ask if the user wants to mail a report (default N). 

This is done during apt-listchanges installation time, providing that
your debconf settings allows the question about e-mail address list to
appear.

> - Also notify
> user that the process may hang if no mail subsystem exists (which I
> believe is now the case starting with stretch) or is improperly
> configured. (Just 'root')

I think that the sendmail command should hang when misconfigured or for
any other reason - that's why I am reassigning the bug report to
citadel-server. (BTW. I am not sure if this is possible in case of
citadel-server, but maybe sendmail command was trying to send e-mails
via network? How long did you wait before deciding that the command hung?).

> 
> (2) See other 3 reports related to MAIL for additional prompt suggestions.

Could you please be more specific? Which other 3 bug reports are related
to this one?

Regards,
robert

Bug#908557: [RESOLVED] Error while setting the maximum protocol version

[Heinrich Schuchardt]

The issue was resolved with libqt5network5_5.11.1+dfsg-8_amd64.deb

Bug#908538: marked as done (ufo2ft: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 20:50:39 +
with message-id 
and subject line Bug#908538: fixed in ufo2ft 2.1.0-1
has caused the Debian Bug report #908538,
regarding ufo2ft: FTBFS in buster/sid (failing tests)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/outlineCompiler.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/postProcessor.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/util.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/maxContextCalc.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/fontInfoData.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/markFeatureWriter.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/preProcessor.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/featureCompiler.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/kernFeatureWriter.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
copying Lib/ufo2ft/__init__.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft
creating 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/featureWriters
copying Lib/ufo2ft/featureWriters/markFeatureWriter.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/featureWriters
copying Lib/ufo2ft/featureWriters/kernFeatureWriter.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/featureWriters
copying Lib/ufo2ft/featureWriters/__init__.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/featureWriters
copying Lib/ufo2ft/featureWriters/baseFeatureWriter.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/featureWriters
creating /<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
copying Lib/ufo2ft/filters/removeOverlaps.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
copying Lib/ufo2ft/filters/transformations.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
copying Lib/ufo2ft/filters/cubicToQuadratic.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
copying Lib/ufo2ft/filters/decomposeComponents.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
copying Lib/ufo2ft/filters/__init__.py -> 
/<>/.pybuild/cpython3_3.6_ufo2ft/build/ufo2ft/filters
running egg_info
creating Lib/ufo2ft.egg-info
writing Lib/ufo2ft.egg-info/PKG-INFO
writing dependency_links to Lib/ufo2ft.egg-info/dependency_links.txt
writing requirements to Lib/ufo2ft.egg-info/requires.txt
writing top-level names to Lib/ufo2ft.egg-info/top_level.txt
writing manifest file 'Lib/ufo2ft.egg-info/SOURCES.txt'
reading manifest file 'Lib/ufo2ft.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'Lib/ufo2ft.egg-info/SOURCES.txt'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.6_ufo2ft/build; 
python3.6 -m pytest tests
= test session starts ==
platform linux -- Python 3.6.6, pytest-3.6.4, py-1.6.0, pluggy-0.6.0 -- 
/usr/bin/python3.6
cachedir: ../../../.pytest_cache
rootdir: /<>, inifile: setup.cfg
collecting ... collected 86 items

tests/compiler_test.py::CompilerTest::test_TestFont_CFF PASSED   [  1%]
tests/compiler_test.py::CompilerTest::test_TestFont_TTF FAILED   [  2%]
tests/compiler_test.py::CompilerTest::test_deprecated_arguments PASSED   [  3%]
tests/compiler_test.py::CompilerTest::test_features PASSED   [  4%]
tests/compiler_test.py::CompilerTest::test_interpolatableTTFs_lazy FAILED [  5%]
tests/compiler_test.py::CompilerTest::test_mti_features PASSED   [  6%]
tests/compiler_test.py::CompilerTest::test_removeOverlaps FAILED [  8%]
tests/compiler_test.py::CompilerTest::test_removeOverlaps_CFF 

Processed: Re: gtk+3.0 breaks libgtk3-perl autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gdk-pixbuf
Bug #908323 [src:libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added indication that 908323 affects src:gdk-pixbuf

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

Bug#908323: gtk+3.0 breaks libgtk3-perl autopkgtest

[Jeremy Bicha]

Control: affects -1 src:gdk-pixbuf

On Tue, Sep 11, 2018 at 3:03 PM Paul Gevers  wrote:
> Control: affects -1 src:gtk+3.0
>
> Dear maintainers,
>
> With a recent upload of gtk+3.0 the autopkgtest of libgtk3-perl fails in
> testing when that autopkgtest is run with the binary packages of gtk+3.0
> from unstable. It passes when run with only packages from testing. This
> appears to be the same reason as reported in this bug.

The change that triggered this failure seems to be in gdk-pixbuf not
gtk3, but gdk-pixbuf is not a direct dependency of libgtk3-perl.

Thanks,
Jeremy Bicha

Processed: forcibly merging 908578 908619

[Debian Bug Tracking System]

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

> forcemerge 908578 908619
Bug #908578 [reportbug] reportbug: crash on requesting madison
Bug #908087 [reportbug] reportbug: Fails with: TypeError: fixer() missing 1 
required positional argument: 'check_hostname'
Bug #908619 [reportbug] reportbug: Crash when reporting bug: TypeError: fixer() 
missing argument: 'check_hostname'
Severity set to 'grave' from 'important'
908619 was not blocked by any bugs.
908619 was not blocking any bugs.
Added blocking bug(s) of 908619: 906127
Bug #908087 [reportbug] reportbug: Fails with: TypeError: fixer() missing 1 
required positional argument: 'check_hostname'
Merged 908087 908578 908619
> thanks
Stopping processing here.

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

Bug#908616: OpenAFS security release

[Salvatore Bonaccorso]

Hey!

On Tue, Sep 11, 2018 at 02:30:51PM -0500, Benjamin Kaduk wrote:
> Source: openafs
> Version: 1.6.9-2+deb8u7
> Tags: security
> Severity: serious
> 
> OpenAFS upstream released security releases 1.6.23 and 1.8.2 today, fixing:
> http://openafs.org/pages/security/OPENAFS-SA-2018-001.txt
> http://openafs.org/pages/security/OPENAFS-SA-2018-002.txt
> http://openafs.org/pages/security/OPENAFS-SA-2018-003.txt
> 
> No CVEs have been assigned yet.

Would it be possible, that you with both your maintainers and upstream
part could request accordingly CVEs via http://cveform.mitre.org/ (and
then loop back the assignment here once got those).

Regards,
Salvatore

Bug#908536: marked as done (jnr-posix: FTBFS in buster/sid (Plugin org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved))

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 19:52:24 +
with message-id 
and subject line Bug#908542: fixed in surefire 2.21.0-3
has caused the Debian Bug report #908542,
regarding jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
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.)


-- 
908542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jnr-posix
Version: 3.0.45-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibjnr-posix-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
   jh_linkjars -i -O--buildsystem=maven
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO] 
[INFO] --< com.github.jnr:jnr-posix >--
[INFO] Building jnr-posix 3.0.45
[INFO] [ jar ]-
[WARNING] The POM for org.apache.maven.plugins:maven-surefire-plugin:jar:2.18.1 
is missing, no dependency information available
[INFO] 
[INFO] 
[INFO] Skipping jnr-posix
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.423 s
[INFO] Finished at: 2018-09-10T10:23:13Z
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-surefire-plugin:2.18.1 or one of 
its dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-surefire-plugin:jar:2.18.1 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/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US 
returned exit code 1
make: *** 

Bug#908537: marked as done (jruby-joni: FTBFS in buster/sid (Plugin org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved))

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 19:52:24 +
with message-id 
and subject line Bug#908542: fixed in surefire 2.21.0-3
has caused the Debian Bug report #908542,
regarding jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibjruby-joni-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO] 
[INFO] < org.jruby.joni:joni >-
[INFO] Building Joni 2.1.18
[INFO] [ jar ]-
[WARNING] The POM for org.apache.maven.plugins:maven-surefire-plugin:jar:2.20.1 
is missing, no dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.245 s
[INFO] Finished at: 2018-09-10T13:52:45Z
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-surefire-plugin:2.20.1 or one of 
its dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-surefire-plugin:jar:2.20.1 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/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---

Bug#908542: marked as done (libsurefire-java: Maven pom contains unwanted rules)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 19:52:24 +
with message-id 
and subject line Bug#908542: fixed in surefire 2.21.0-3
has caused the Debian Bug report #908542,
regarding libsurefire-java: Maven pom contains unwanted rules
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.)


-- 
908542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsurefire-java
Version: 2.21.0-2
Severity: serious

When libsurefire-java/2.21.0-2 was built last week extra rules were
automatically added to the pom of the Maven plugin:

--- maven-surefire-plugin-2.21.0-1.pom  2018-09-11 00:24:27.213383006 +0200
+++ maven-surefire-plugin-2.21.0-2.pom  2018-09-11 00:24:37.677124688 +0200
@@ -37,6 +37,20 @@



+   org.apache.maven 
maven-plugin-descriptor * * * *,
+   org.apache.maven maven-toolchain * * * *,
+   org.apache.maven.plugins maven-assembly-plugin * * * *,
+   org.apache.maven.plugins maven-deploy-plugin * * * *,
+   org.apache.maven.plugins maven-enforcer-plugin * * * *,
+   org.apache.maven.plugins maven-failsafe-plugin * * * *,
+   org.apache.maven.plugins maven-scm-publish-plugin * * * *,
+   org.apache.maven.plugins maven-site-plugin * * * *,
+   org.apache.maven.plugins maven-surefire-plugin * * * *,
+   org.apache.rat apache-rat-plugin * * * *,
+   org.codehaus.mojo animal-sniffer-maven-plugin * * * *,
+   org.jacoco jacoco-maven-plugin * * * *,
+   org.powermock * * * * *
+
2.21.0

libsurefire-java


In particular, the rule:

   org.apache.maven.plugins maven-surefire-plugin * * * *

causes many packages to fail to build from source because they are unable
to resolve the version of the Surefire plugin (see #908535, #908536 and #908537)

I haven't figured out the origin of these rules yet, maybe a recent change in
maven-debian-helper. Once the root cause is identified the surefire package
must be rebuilt.
--- End Message ---
--- Begin Message ---
Source: surefire
Source-Version: 2.21.0-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated surefire 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: Tue, 11 Sep 2018 21:16:42 +0200
Source: surefire
Binary: libsurefire-java
Architecture: source
Version: 2.21.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libsurefire-java - Surefire test framework for Java
Closes: 908542
Changes:
 surefire (2.21.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild with maven-debian-helper/2.3.2 to remove the ignore rules
 copied into the installed poms (Closes: #908542)
Checksums-Sha1:
 c805a4c340214697f7ca3f302eca1fd368bfeaaf 2558 surefire_2.21.0-3.dsc
 71c514a7f07af4ea168f57a46c713bb046cdc4ca 9500 surefire_2.21.0-3.debian.tar.xz
 6335b9c27e93acaeaa084e7a1ad2f49c9272d5a0 16264 
surefire_2.21.0-3_source.buildinfo
Checksums-Sha256:
 02907a5245cf84885b66d84c1c3194a4db24585ba8a5323b20e7c5ddcd6f34c8 2558 
surefire_2.21.0-3.dsc
 9c63afed6187b6c00f0d0e8586e74121a09966b41489d2f20a2b08c0575a 9500 
surefire_2.21.0-3.debian.tar.xz
 6ea9fa2c399847644ca587fecbb6d3a3f9f29861dd10c0b3e09a6d25cc7e615a 16264 
surefire_2.21.0-3_source.buildinfo
Files:
 791008bcb9d02fc22cab5300ab1dcd28 2558 java optional surefire_2.21.0-3.dsc
 4e91d7032471781cdd91721ff1a0afe8 9500 java optional 
surefire_2.21.0-3.debian.tar.xz
 b7bf1087f7f7ec5688663d0a5889208d 16264 java optional 
surefire_2.21.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAluYFVQSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCspvEQAMeWv0zSNs1QtZXpkAD4XmSI74VVj41q
5k342AuUKNmZ4K/7isZWVOLWulc2gG8AggDQIq/pQmQ3SuS7S4OyeIOMETISt8pp

Bug#908535: marked as done (aether-ant-tasks: FTBFS in buster/sid (Plugin org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved))

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 19:52:24 +
with message-id 
and subject line Bug#908542: fixed in surefire 2.21.0-3
has caused the Debian Bug report #908542,
regarding aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
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.)


-- 
908542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aether-ant-tasks
Version: 1.0.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibaether-ant-tasks-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   jh_linkjars -i -O--buildsystem=maven
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO] 
[INFO] < org.eclipse.aether:aether-ant-tasks >-
[INFO] Building Aether Ant Tasks 1.0.1.v2014
[INFO] [ jar ]-
[WARNING] The POM for org.apache.maven.plugins:maven-surefire-plugin:jar:2.9 is 
missing, no dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.289 s
[INFO] Finished at: 2018-09-10T12:41:11Z
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-surefire-plugin:2.9 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-surefire-plugin:jar:2.9 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/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aether-ant-tasks.html

where you can get a full build log if 

Processed: Re: Bug#908494: lightning: no icon to access calendar after upgrade to TB 60

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #908494 [lightning] lightning: no icon to access calendar after upgrade to 
TB 60
Severity set to 'important' from 'grave'
> tags -1 unreproducible
Bug #908494 [lightning] lightning: no icon to access calendar after upgrade to 
TB 60
Added tag(s) unreproducible.

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

Processed: fixed 908324 in 4.4.4-2+deb9u3

[Debian Bug Tracking System]

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

> fixed 908324 4.4.4-2+deb9u3
Bug #908324 {Done: Salvatore Bonaccorso } [src:kamailio] 
kamailio: CVE-2018-16657
The source 'kamailio' and version '4.4.4-2+deb9u3' do not appear to match any 
binary packages
Ignoring request to alter fixed versions of bug #908324 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> owner 908606 !
Bug #908606 [src:picocli] picocli: Incomplete debian/copyright?
Warning: Unknown package 'src:picocli'
Owner recorded as Miroslav Kravec .
Warning: Unknown package 'src:picocli'
>
End of message, stopping processing here.

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

Bug#908606: picocli: Incomplete debian/copyright?

[Miroslav Kravec]

Hello Chris,

On Tue, Sep 11, 2018 at 8:48 PM Chris Lamb  wrote:
>
> I just ACCEPTed picocli from NEW but noticed it was missing
> attribution in debian/copyright for at least Robert Zenz.
>
> This is in no way exhaustive so please check over the entire package
> carefully and address these on your next upload.

Thank you for processing and ACCEPTing picocli package.

I'm sorry for issue with debian/copyright. I'll check over entire
package, and add missing attributions, and make new (next) upload.

Kind regards,
Miroslav Kravec
On Tue, Sep 11, 2018 at 8:48 PM Chris Lamb  wrote:
>
> Source: picocli
> Version: 3.5.2-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Miroslav Kravec ,
> ftpmas...@debian.org
>
> Hi,
>
> I just ACCEPTed picocli from NEW but noticed it was missing
> attribution in debian/copyright for at least Robert Zenz.
>
> This is in no way exhaustive so please check over the entire package
> carefully and address these on your next upload.
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Bug#908494: lightning: no icon to access calendar after upgrade to TB 60

[Carsten Schoenert]

Control: severity -1 important
Control: tags -1 unreproducible

On Mon, Sep 10, 2018 at 05:23:22PM +0100, George B. wrote:
> > what have you tried to debug the issue?
> 
> Deleted my Thunderbird profile and tested with a fresh one.
> 
> Tried "thunderbird --jsconsole" but there is no output.
> 
> Lightning is the only extension installed.
> Extension is listed as enabled in the "Add-ons" screen.
> Clicking on "Tools -> Add-on Preferences -> Lightning" brings up the
> "Advanced" section of Tunderbird Preferences.

To see if I can reproduce this behavior anyhow I have setup now a
complete new install of an Stretch system on i386 with and without the
Thunderbird packages with a further dist-upgrade to testing and start
the testing again within a Gnome3 desktop environment.

At no point I've seen a broken Lighting installation, no matter if I
copy a existing HOME folder into new the user profile or if I add
additional a existing Thunderbird profile into the new user profile
finally. I got always a working Lightning. So it's currently not a
problem of the Thunderbird packages.

The information from above is unfortunately a bare minimum of
information about your system and setup. Without additional information
it's impossible to do any further debugging from here.
The information from the first email is showing that debconf-show was
failing. That is unusual and must have a reason. This hides some maybe
interesting additional information about the packages around TB on your
system.

You also have written that Lightning is shown within the Extension
overview, this means Thunderbird has successful detected the Lightning
extension. So from the application view Lighting is around.
Is Ctrl+Shift+C showing the Calendar?

Currently I have no further idea how I can debug this a bit more, for me
it makes not really sense to do a lot of Q about some really basic
things if you can't do some more self research on your side.

I'm happy if other user can step in and try to help to untagle this
report.

Regards
Carsten

Processed: found 908616 in 1.6.9-1

[Debian Bug Tracking System]

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

> found 908616 1.6.9-1
Bug #908616 [src:openafs] OpenAFS security release
Marked as found in versions openafs/1.6.9-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#908597: nvidia-kernel-dkms: Unable to upgrade and to reinstall

[Debian Bug Tracking System]

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

> forcemerge 908568 908597
Bug #908568 [nvidia-kernel-dkms] nvidia-driver: build error
Bug #908597 [nvidia-kernel-dkms] nvidia-kernel-dkms: Unable to upgrade and to 
reinstall
Severity set to 'grave' from 'important'
Bug #908568 [nvidia-kernel-dkms] nvidia-driver: build error
Marked as found in versions nvidia-graphics-drivers/390.87-1.
Merged 908568 908597
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#908597: Re : Bug#908597: nvidia-kernel-dkms: Unable to upgrade and to reinstall

[Debian Bug Tracking System]

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

> reassign 908568 nvidia-kernel-dkms
Bug #908568 [nvidia-driver] nvidia-driver: build error
Bug reassigned from package 'nvidia-driver' to 'nvidia-kernel-dkms'.
No longer marked as found in versions nvidia-graphics-drivers/390.87-1.
Ignoring request to alter fixed versions of bug #908568 to the same values 
previously set
> forcemerge 908568 -1
Failed to forcibly merge 908568: Requested to merge with a non-numeric bug: 
'-1'.

>
End of message, stopping processing here.

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

Bug#903698: fixed in dh-python 3.20180723

[Paul Gevers]

Hi all, dear Piotr,

On Tue, 24 Jul 2018 09:42:34 +0200 Paul Gevers  wrote:
> On Mon, 23 Jul 2018 13:34:11 + =?utf-8?q?Piotr_O=C5=BCarowski?=
>  wrote:
> >* dh_python{2,3}:
> >  - fix \.so.* symlink renaming for non-default Python versions
> >(closes: 739500, 903698)
> 
> Thanks for the fix. It worked on all arches where sphinxbase was rebuild
> except for mipsel64el (see below), hence I reopen the bug.

Any progress on this issue? Do I need to start work around the issue (if
this is possible)?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#908616: OpenAFS security release

[Benjamin Kaduk]

Source: openafs
Version: 1.6.9-2+deb8u7
Tags: security
Severity: serious

OpenAFS upstream released security releases 1.6.23 and 1.8.2 today, fixing:
http://openafs.org/pages/security/OPENAFS-SA-2018-001.txt
http://openafs.org/pages/security/OPENAFS-SA-2018-002.txt
http://openafs.org/pages/security/OPENAFS-SA-2018-003.txt

No CVEs have been assigned yet.

-Ben

Processed: pyfai: FTBFS and autopkgtest fails with python3.7 in supported versions

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #908615 [src:pyfai] pyfai: FTBFS and autopkgtest fails with python3.7 in 
supported versions
Added indication that 908615 affects src:python3-defaults

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

Bug#908615: pyfai: FTBFS and autopkgtest fails with python3.7 in supported versions

[Paul Gevers]

Source: pyfai
Version: 0.15.0+dfsg1-1
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

[X-Debbugs-CC set to: debian...@lists.debian.org,
python3-defau...@packages.debian.org]

Dear maintainers,

Since the python3.7 transition started (which added python3.7 to the
supported Python versions) the autopkgtest of pyfai fails in testing
when that autopkgtest is run with the binary packages of
python3-defaults from unstable. It passes when run with only packages
from testing. I copied some of the output at the bottom of this report.
It seems that this failure also causes the package to FTBFS on
reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfai.html

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python3-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyfai/972161/log.gz

autopkgtest [05:07:40]: test python3: [---
=== python3.7 ===
Unable to import pyFAI.ext.splitBBoxLUT for Look-up table based
azimuthal integration
Unable to import pyFAI.ext.splitPixel full pixel splitting: cannot
import name 'splitPixel' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBox Bounding Box pixel splitting:
cannot import name 'splitBBox' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.histogram Cython histogram implementation:
cannot import name 'histogram' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBoxCSR CSR based azimuthal integration:
cannot import name 'splitBBoxCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitPixelFullCSR CSR based azimuthal
integration: cannot import name 'splitPixelFullCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyFAI/__init__.py", line 73, in tests
res = test.run_tests()
  File "/usr/lib/python3/dist-packages/pyFAI/test/__init__.py", line 59,
in run_tests
if not runner.run(suite()).wasSuccessful():
  File "/usr/lib/python3/dist-packages/pyFAI/test/__init__.py", line 50,
in suite
from . import test_all
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_all.py", line 47,
in 
from . import test_histogram
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py",
line 45, in 
from ..ext.histogram import histogram, histogram2d
ModuleNotFoundError: No module named 'pyFAI.ext.histogram'
autopkgtest [05:07:41]: test python3: ---]
autopkgtest [05:10:47]: test python3-dbg: [---
=== python3.7 ===
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't
resolve package from __spec__ or __package__, falling back on __name__
and __path__
  return f(*args, **kwds)
/usr/lib/python3/dist-packages/h5py/_hl/base.py:19: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from
'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import (Mapping, MutableMapping, KeysView,
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't
resolve package from __spec__ or __package__, falling back on __name__
and __path__
  return f(*args, **kwds)
Unable to import pyFAI.ext.splitBBoxLUT for Look-up table based
azimuthal integration
Unable to import pyFAI.ext.splitPixel full pixel splitting: cannot
import name 'splitPixel' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBox Bounding Box pixel splitting:
cannot import name 'splitBBox' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.histogram Cython histogram implementation:
cannot import name 'histogram' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBoxCSR CSR based azimuthal integration:
cannot import name 'splitBBoxCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitPixelFullCSR CSR based azimuthal
integration: cannot import name 'splitPixelFullCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)

Bug#908456: invesalius is no longer installable

[Andreas Tille]

On Tue, Sep 11, 2018 at 03:31:18PM -0300, Thiago Franco de Moraes wrote:
> >
> > This was easy - see my latest commit.
> 
> Thanks!

You are welcome.
 
> I created a patch to remove the python2 shebangs. This patch was already 
> applied into the upstream. But there is other problem:

Fine.
 
> W: invesalius: executable-not-elf-or-script 
> usr/share/invesalius/invesalius/gui/widgets/gradient.py
> W: invesalius: executable-not-elf-or-script 
> usr/share/invesalius/invesalius/data/viewer_slice.py
> W: invesalius: executable-not-elf-or-script 
> usr/share/invesalius/invesalius/data/viewer_volume.py
> 
> This is happening because these files have execution permission:
> 
> ▶ find -executable -type f -name "*.py"
> ./invesalius/data/viewer_slice.py
> ./invesalius/data/viewer_volume.py
> ./invesalius/gui/widgets/gradient.py

I decided to ignore this for this upload.
 
> This is a problem at the upstream. I don't know why this happened, maybe 
> someone using Windows ... I already fixed this problem at the upstream. But I 
> don't know how to solve this problem in the packaging.
> 
> ...
> So I think this is fixed.

Yes.  I just uploaded and leave those permission issues for a later
upload.

Kind regards

 Andreas. 

-- 
http://fam-tille.de

Bug#878834: marked as done (freetype: Upgrade to 2.8.1 breaks font rendering in various applications)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 15:06:27 -0400
with message-id 

and subject line Re: libfreetype6: font rendering broken in electron 
applications
has caused the Debian Bug report #878929,
regarding freetype: Upgrade to 2.8.1 breaks font rendering in various 
applications
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.)


-- 
878929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freetype
Version: 2.8.1-0.1
Severity: important

Dear Maintainer,

I upgraded freetype from 2.8.0 to 2.8.1 today and font rendering in both 
thunderbird and discord
took a really steep nosedive.

Freetype 2.8.0: https://imgur.com/8QLHYDK
Freetype 2.8.1: https://imgur.com/TtDN0pE

Thanks
Christian


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
The Thunderbird issue is already fixed.

Electron 1.9 was fixed and I believe Electron 1.7.10 also includes the
fix, months ago.

There's nothing really to be done in fontconfig or Debian any more so
I'm closing this bug.

Thanks,
Jeremy Bicha--- End Message ---

Bug#878870: marked as done (freetype 2.8.1 breaks font rendering)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 15:06:27 -0400
with message-id 

and subject line Re: libfreetype6: font rendering broken in electron 
applications
has caused the Debian Bug report #878929,
regarding freetype 2.8.1 breaks font rendering
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.)


-- 
878929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird,libfreetype6
Version: libfreetype6/2.8.1-0.1
Severity: serious
Tags: patch fixed-upstream upstream
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1409188

Hi,

freetype 2.8.1 breaks fonts when using subpixel rendering.

This is already fixed in firefox[1], the same code is also present in
thunderbird and I guess the same patch can be used there.

Could you please have a look at fixing thunderbird?

Regards,

Laurent Bigonville

[1] https://hg.mozilla.org/releases/mozilla-release/rev/8fe8227e5080
--- End Message ---
--- Begin Message ---
The Thunderbird issue is already fixed.

Electron 1.9 was fixed and I believe Electron 1.7.10 also includes the
fix, months ago.

There's nothing really to be done in fontconfig or Debian any more so
I'm closing this bug.

Thanks,
Jeremy Bicha--- End Message ---

Bug#878929: marked as done (libfreetype6: font rendering broken in electron applications)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 15:06:27 -0400
with message-id 

and subject line Re: libfreetype6: font rendering broken in electron 
applications
has caused the Debian Bug report #878929,
regarding libfreetype6: font rendering broken in electron applications
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.)


-- 
878929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfreetype6
Version: 2.8.1-0.1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

Font rendering in electron applications is now broken (eg basic electron sample
applications/discord).  Building manually this problem does not exist:

apt-get source libfreetype6
cd freetype-2.8.1/
tar xfj freetype-2.8.1.tar.bz2
cd freetype-2.8.1
./configure --without-bzip2 --without-harfbuzz
make -j4
LD_PRELOAD=./objs/.libs/libfreetype.so ~/discordapp/Discord #or other electron
app



-- 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/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
The Thunderbird issue is already fixed.

Electron 1.9 was fixed and I believe Electron 1.7.10 also includes the
fix, months ago.

There's nothing really to be done in fontconfig or Debian any more so
I'm closing this bug.

Thanks,
Jeremy Bicha--- End Message ---

Processed: gtk+3.0 breaks libgtk3-perl autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gtk+3.0
Bug #908323 [src:libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added indication that 908323 affects src:gtk+3.0

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

Bug#908456: marked as done (invesalius is no longer installable)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 19:04:13 +
with message-id 
and subject line Bug#908456: fixed in invesalius 3.1.2-1
has caused the Debian Bug report #908456,
regarding invesalius is no longer installable
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.)


-- 
908456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: invesalius
Version: 3.1.1-1
Severity: grave

The following packages have unmet dependencies:
 invesalius : Depends: python-gdcm but it is not going to be installed
  Depends: python-vtkgdcm but it is not going to be installed
--- End Message ---
--- Begin Message ---
Source: invesalius
Source-Version: 3.1.2-1

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

Debian distribution maintenance software
pp.
Thiago Franco de Moraes  (supplier of updated invesalius 
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: Mon, 10 Sep 2018 11:57:50 -0300
Source: invesalius
Binary: invesalius invesalius-examples invesalius-bin
Architecture: source
Version: 3.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Thiago Franco de Moraes 
Description:
 invesalius - 3D medical imaging reconstruction software
 invesalius-bin - Implementation of MIDA and contour based visualizations
 invesalius-examples - examples for 3D medical imaging reconstruction software
Closes: 908456
Changes:
 invesalius (3.1.2-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #908456
Checksums-Sha1:
 3748f258e37a322edb4af749380ff4edc5446530 2254 invesalius_3.1.2-1.dsc
 09564dac979a62a4557fdb0f87b878098401fe7e 80191758 
invesalius_3.1.2.orig.tar.gz
 0dee8a4a818065411c7d3c676d55bfd0050b5cbf 11652 
invesalius_3.1.2-1.debian.tar.xz
Checksums-Sha256:
 6c757cf09ed893e5a64997337226935ea9a9d000299335c413edbe9fb4c14270 2254 
invesalius_3.1.2-1.dsc
 d72e7f5957504ace5688edc0f083a11889c9d4a0937db75669379853501c32de 80191758 
invesalius_3.1.2.orig.tar.gz
 cd4a1d6e83f08ab314946ddb7a505479ff4fd0dec993334dd422f03dc464580b 11652 
invesalius_3.1.2-1.debian.tar.xz
Files:
 8f1301be40927f25a56fb9803799b91a 2254 graphics optional 
invesalius_3.1.2-1.dsc
 c5c55a5bab40948dbfa56ae9664b2de0 80191758 graphics optional 
invesalius_3.1.2.orig.tar.gz
 4c46fa456ed4cc173723f660302c11c2 11652 graphics optional 
invesalius_3.1.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluYDCQOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtH76g/9GWqlUW+lZ6grq0Ra8Hjka/0iZLNQLQ6T0Uin
Mu/T+lU8QS49KEsXIVsoXH8jgaATOS7kud+OQGm1mXK/sKCVBwYOWVjF/BvZ+vDG
ow8wgpDozFpV8MBJ+9R/HDxka+YkT0yZH3PRfcLTQH+oceMGqIGRgn0S6ISaMVWV
nlL4veo/YGoilTdBOkLbCccrAA+nfs8d+ai09v7KUvP/Bb6SywAxVfTLZ6rEoh1k
2FlNzKU0AfmoLb4M1qLC9vWijNfUoQ3iAOTxO8L4bE5Nxx8+KVfHfbdMwj9I6ulJ
ZU0RW4AETmW5Z8PbxdtABQJxGEVMJru4QkIMY0mPHFLCnPlkRlBzyAHsO9s4iD2l
PvBoOLJ61cNbBx2qADQzN8KnV/W5FTlPBXaJX8b+X+RQ1PbD7wWF2TtB1f0Vyhj+
of+D8cymLclGf6Cc+Lk/7q0VCg/vUykfgFd/YWMvB7KxrJrUDcGr5BZTwV02xJf4
LYBp+Qm7RCKOGm35hEZO/XzZzTLx9uTPmJZ4X8MKD+OkVNWV/Mx37DPofVW71odq
DpzdjloQ1JHOuSuEaZLhQh17I3gKKW28zp5t20835VcvD5r5JpSY703kMKiAXu/W
WsBaWyAAKOxIAmpdMzhOh7ZHDhANWk0EJdSnl/E8n//NRcRwv36GvThKpOQZRTOk
x8CC+7Q=
=CqLC
-END PGP SIGNATURE End Message ---

Bug#908323: gtk+3.0 breaks libgtk3-perl autopkgtest

[Paul Gevers]

Control: affects -1 src:gtk+3.0

Dear maintainers,

With a recent upload of gtk+3.0 the autopkgtest of libgtk3-perl fails in
testing when that autopkgtest is run with the binary packages of gtk+3.0
from unstable. It passes when run with only packages from testing. This
appears to be the same reason as reported in this bug.

Currently this regression is contributing to the delay of the migration
of gtk+3.0 to testing [1]. To notify the maintainers of that package of
the reason of the delay, I write this message to this bug with them is CC.

More information about this message can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=gtk+3.0

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgtk3-perl/972111/log.gz




signature.asc
Description: OpenPGP digital signature

Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Sebastian Andrzej Siewior]

On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> Dmitry already implemented my short-term workaround:
> https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
> 
> When this has been built on all release architectures openssl can bump 
> the version requirement.
> 
> Even more cautious would be to wait until testing migration of Qt.

now after what happens I consider this issue (#908567) fixed since the
only affected package by this is fixed. Also adding versioned depends is
not easy as I expected it in the morning without too much mess around
it.

> cu
> Adrian

Sebastian

Bug#908609: gtkhash: cannot fulfill the build dependencies

[Adrian Bunk]

Source: gtkhash
Version: 1.1.1-2
Severity: serious
Tags: ftbfs

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

gtkhash build-depends on:
- libthunarx-2-dev:arm64
libthunarx-2-dev depends on missing:
- thunar-data:arm64 (= 1.6.15-1)


Ubuntu seems to have a fix for the
libthunarx-2-dev -> libthunarx-3-dev
transition.

Bug#908608: xfdesktop4: cannot fulfill the build dependencies

[Adrian Bunk]

Source: xfdesktop4
Version: 4.12.4-1
Severity: serious
Tags: ftbfs
Control: fixed -1 4.13.2-1
Control: close -1

The following packages have unmet dependencies:
 builddeps:xfdesktop4 : Depends: libthunarx-2-dev (>= 1.4.0) but it is not 
going to be installed


This is already fixed in experimental.

Processed: xfdesktop4: cannot fulfill the build dependencies

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.13.2-1
Bug #908608 [src:xfdesktop4] xfdesktop4: cannot fulfill the build dependencies
Marked as fixed in versions xfdesktop4/4.13.2-1.
> close -1
Bug #908608 [src:xfdesktop4] xfdesktop4: cannot fulfill the build dependencies
Marked Bug as done

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

Bug#908607: pgformatter: Incomplete debian/copyright?

[Chris Lamb]

Source: pgformatter
Version: 3.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Christoph Berg , 
ftpmas...@debian.org

Hi,

I just ACCEPTed pgformatter from NEW but noticed it was missing 
attribution in debian/copyright for at least Beautify.pm, which
also appears to be a code copy (?).

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#908561: marked as done (i386 rustc produces SSE2 instructions)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 18:47:08 +
with message-id 
and subject line Bug#908561: fixed in rustc 1.24.1+dfsg1-1~deb9u4
has caused the Debian Bug report #908561,
regarding i386 rustc produces SSE2 instructions
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.)


-- 
908561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rustc
Version: 1.28.0+dfsg1-2
Severity: critical

Build anything with the rustc compiler for i386, and the result will
contain SSE2 instructions. This means rust-based packages don't support
the full range of what the i386 Debian architecture supports.

Specifically, this is the main cause for #908396/#908449.

Mike


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

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

Versions of packages rustc depends on:
ii  binutils  2.31.1-4
ii  gcc   4:8.1.0-1
ii  libc6 2.27-5
ii  libc6-dev [libc-dev]  2.27-5
ii  libgcc1   1:8.2.0-3
ii  libllvm6.01:6.0.1-6
ii  libstd-rust-dev   1.28.0+dfsg1-2
ii  libstdc++68.2.0-3

Versions of packages rustc recommends:
ii  cargo 0.28.0-1
ii  rust-gdb  1.28.0+dfsg1-2

Versions of packages rustc suggests:
pn  rust-doc  
pn  rust-src  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.24.1+dfsg1-1~deb9u4

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated rustc 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: Tue, 11 Sep 2018 11:08:03 +0200
Source: rustc
Binary: rustc libstd-rust-1.24 libstd-rust-dev rust-gdb rust-lldb rust-src
Architecture: source
Version: 1.24.1+dfsg1-1~deb9u4
Distribution: stretch
Urgency: medium
Maintainer: Rust Maintainers 
Changed-By: Julien Cristau 
Description:
 libstd-rust-1.24 - Rust standard libraries
 libstd-rust-dev - Rust standard libraries - development files
 rust-gdb   - Rust debugger (gdb)
 rust-lldb  - Rust debugger (lldb)
 rust-src   - Rust systems programming language - source code
 rustc  - Rust systems programming language
Closes: 908561
Changes:
 rustc (1.24.1+dfsg1-1~deb9u4) stretch; urgency=medium
 .
   * i686-baseline.patch: don't use pentium4 as i686 baseline (closes: #908561)
Checksums-Sha1:
 01de132aba11e22ea9f351d2b29559b1aa12953f 2985 rustc_1.24.1+dfsg1-1~deb9u4.dsc
 c690e89d297b3ac1f38d3f50ed72cb612a8e0975 64360 
rustc_1.24.1+dfsg1-1~deb9u4.debian.tar.xz
Checksums-Sha256:
 437c87ca46ba692cd06dc1ad771c3b6d003a9ee880ff21e92b09e9e2cff47cb5 2985 
rustc_1.24.1+dfsg1-1~deb9u4.dsc
 e945d222d8e7ab68af4f1ebd71bff370640de935b34a8ec022252009b10bf0f8 64360 
rustc_1.24.1+dfsg1-1~deb9u4.debian.tar.xz
Files:
 a1ca47bece01ed41c98565fd6ac00f7b 2985 devel optional 
rustc_1.24.1+dfsg1-1~deb9u4.dsc
 f80833a01f06d4c4ed9437d89d05ec51 64360 devel optional 
rustc_1.24.1+dfsg1-1~deb9u4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAluXuLIACgkQnbAjVVb4
z60KpA//Sga40dzoKP+VL+5Noj4vsWOt8idC5HnmqftjqMvGO5+35+v4E4LYGEIY
s6jsHwyyXaP6t3EYnmoxTZ0jneMfoU5tTXs/Sz7SOrBZgzKblABWWbVRF3VaRPFW
gEnhYCe3IBU4By9RleqnCCEOfFi/P1T57vX8fX5gzLZp+/R4gR0MpnZmY4UuZUdJ
+jl9mnF/QlagjJ1vV0vVhjeek0JZ7Qe3cCYv7DG3AMassqilASrEegVss8CmjvTy
mclGNALIJY11R6MymOAVPaNHuzcEacHfsGcBq/UjmuLsKk1A5jdmkkaQqba2PMUE
5ZE5Jt/zqYkO7YcGQ49TvXXG6iVmQfLHEMfp4s98XK7VoRqV6EJFBWYkD8SbdJ0V
aHOENJYLz0SxHPUQWJa1YGL4+gFyKsmswuX6cIobR76MCaIZXnT4lZMwWsPX3jvG
3rEabywp6UqCzmxDOgzabyk23moQGuzfAPz3oxnZiJaxJ367kzZq083/FhnpChE8

Bug#908606: picocli: Incomplete debian/copyright?

[Chris Lamb]

Source: picocli
Version: 3.5.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Miroslav Kravec , 
ftpmas...@debian.org

Hi,

I just ACCEPTed picocli from NEW but noticed it was missing 
attribution in debian/copyright for at least Robert Zenz.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#908605: postfixadmin: 'lib' directory missing

[Jakob Butler]

Package: postfixadmin
Version: 3.2-2
Severity: grave
Justification: renders package unusable

Hi,

Sorry, but it seems that the 'lib' directory is missing -- i.e. a similar issue 
as to bug #908317. Without this directory, the web interface won't work.

Maybe (?) you'll also want to include 'ADDITIONS' and 'VIRTUAL_VACATION' from 
the upstream package? (I don't use them, so don't know the relevance/benefit)

Thanks and best regards,
Jakob

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

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

Versions of packages postfixadmin depends on:
ii  apache2 [httpd] 2.4.34-1
ii  dbconfig-common 2.0.9
ii  debconf 1.5.69
ii  default-mysql-client1.0.4
ii  libapache2-mod-php  1:7.2+62
ii  libapache2-mod-php7.2 [libapache2-mod-php]  7.2.9-1
ii  php 1:7.2+62
ii  php-imap1:7.2+62
ii  php-mbstring1:7.2+62
ii  php-mysql   1:7.2+62
ii  php7.2 [php]7.2.9-1
ii  php7.2-imap [php-imap]  7.2.9-1
ii  php7.2-mbstring [php-mbstring]  7.2.9-1
ii  php7.2-mysql [php-mysqlnd]  7.2.9-1
ii  wwwconfig-common0.3.0

Versions of packages postfixadmin recommends:
ii  dovecot-core1:2.3.2.1-1
pn  mariadb-server  
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.35-1
ii  php7.2-cli [php-cli]7.2.9-1
ii  postfix-mysql   3.3.0-1+b1
ii  zendframework   1.12.20+dfsg-1

postfixadmin suggests no packages.

-- debconf information:
  postfixadmin/upgrade-backup: true
  postfixadmin/dbconfig-remove: true
  postfixadmin/remote/host: localhost
  postfixadmin/install-error: abort
  postfixadmin/upgrade-error: abort
  postfixadmin/mysql/method: Unix socket
  postfixadmin/db/dbname: postfixadmin
  postfixadmin/dbconfig-upgrade: true
  postfixadmin/remote/newhost:
  postfixadmin/internal/reconfiguring: false
  postfixadmin/remote/port:
  postfixadmin/passwords-do-not-match:
  postfixadmin/db/app-user: postfixadmin@localhost
  postfixadmin/dbconfig-reinstall: false
* postfixadmin/database-type: mysql
  postfixadmin/missing-db-package-error: abort
  postfixadmin/purge: false
* postfixadmin/mysql/admin-user: root
  postfixadmin/internal/skip-preseed: false
  postfixadmin/remove-error: abort
* postfixadmin/dbconfig-install: true

Bug#908456: invesalius is no longer installable

[Thiago Franco de Moraes]

On Tue, Sep 11, 2018 at 1:49 PM Andreas Tille  wrote:
>
> Hi Thiago,
>
> On Tue, Sep 11, 2018 at 10:21:51AM -0300, Thiago Franco de Moraes wrote:
> > Hi Andreas,
> >
> > Done! I've just pulled the changes to Salsa. I created a new release 
> > (3.1.2).
>
> Good. :-)
>
> > But I'm getting this warning:
> >  dpkg-gencontrol: warning: Depends field of package invesalius: unknown 
> > substitution variable ${python:Depends}
>
> This was easy - see my latest commit.

Thanks!

> > This warning happens with both my last version and with the last change you 
> > did. I'm using "gbp buildpackage" to create the package in Ubuntu and 
> > Debian Sid. I tested the package in Debian Sid and it is working correctly.
>
> Hmmm, here is a less easy one - no idea why you do not get this.  There
> are some remaining Python2 scripts that need to be ported:
>
> E: invesalius: missing-dep-for-interpreter python2 => python:any | 
> python-minimal:any | python2:any | python2-minimal:any 
> (usr/share/invesalius/invesalius/data/viewer_slice.py) #!/usr/bin/python2
> N:
> N:You used an interpreter for a script that is not in an essential
> N:package. In most cases, you will need to add a Dependency on the package
> N:that contains the interpreter. If the dependency is already present,
> N:please file a bug against Lintian with the details of your package so
> N:that its database can be updated.
> N:  
> N:In some cases a weaker relationship, such as Suggests or Recommends,
> N:will be more appropriate.
> N:  
> N:Severity: important, Certainty: possible
> N:  
> N:Check: scripts, Type: binary
> N:
> E: invesalius: missing-dep-for-interpreter python2 => python:any | 
> python-minimal:any | python2:any | python2-minimal:any 
> (usr/share/invesalius/invesalius/data/viewer_volume.py) #!/usr/bin/python2
> E: invesalius: missing-dep-for-interpreter python2 => python:any | 
> python-minimal:any | python2:any | python2-minimal:any 
> (usr/share/invesalius/invesalius/gui/widgets/gradient.py) #!/usr/bin/python2

I created a patch to remove the python2 shebangs. This patch was already 
applied into the upstream. But there is other problem:

W: invesalius: executable-not-elf-or-script 
usr/share/invesalius/invesalius/gui/widgets/gradient.py
W: invesalius: executable-not-elf-or-script 
usr/share/invesalius/invesalius/data/viewer_slice.py
W: invesalius: executable-not-elf-or-script 
usr/share/invesalius/invesalius/data/viewer_volume.py

This is happening because these files have execution permission:

▶ find -executable -type f -name "*.py"
./invesalius/data/viewer_slice.py
./invesalius/data/viewer_volume.py
./invesalius/gui/widgets/gradient.py

This is a problem at the upstream. I don't know why this happened, maybe 
someone using Windows ... I already fixed this problem at the upstream. But I 
don't know how to solve this problem in the packaging.

There is other problem, but I already fixed. I used debuild to test a change in 
the packaging that I did. It worked but when I commit the change I also commit 
some changes in the source code of InVesalius. I think debuild didn't unapply 
the patches. This happened at the commit 83d10824. I fixed this problem at the 
commit 0a1dfc00. Using the git diff to see the differences between the head and 
the upstream/3.1.2 show the only difference are the debian folder:

git diff --name-only HEAD upstream/3.1.2
debian/changelog
debian/compat
debian/control
debian/copyright
debian/dirs
debian/docs
debian/invesalius-bin.install
debian/invesalius-examples.examples
debian/invesalius.desktop
debian/invesalius.install
debian/invesalius.lintian-overrides
debian/invesalius.manpages
debian/invesalius.xpm
debian/invesalius3.1
debian/links
debian/patches/10_import_cython_modules.patch
debian/patches/10_remove_python2_shebang.patch
debian/patches/10_sample_path.patch
debian/patches/series
debian/rules
debian/source/format
debian/source/options
debian/watch
(END)

So I think this is fixed.

> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de

Best regards

Bug#907774: Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Dmitry Shachnev]

On Tue, Sep 11, 2018 at 07:18:28PM +0200, Kurt Roeckx wrote:
> > > If this is for a call to SSL_CTX_set_max_proto_version(), you can
> > > use 0 instead of TLS_MAX_VERSION.
> >
> > Good point, thanks.
> >
> > However as the patch is temporary, I do not think it is worth
> > a new upload to change that.
>
> But maybe you can get upstream to use that instead.

Done: https://codereview.qt-project.org/239603

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#907491: goobook fails to authenticate

[Sergio Mendoza]

Yes, goobook works fine and smooth.

Thanks,

Sergio.


-- 
Sergio Mendoza  
Instituto de Astronomia, UNAM
http://www.mendozza.org/sergio
On Tue, Sep 11, 2018 at 06:51:00PM +0200, Kurt Roeckx wrote:
> Now that bug #907278 is fixed, I think this is fixed too.
> 

Processed: affects 908535

[Debian Bug Tracking System]

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

> affects 908535 src:aether-ant-tasks src:jnr-posix src:jruby-joni
Bug #908535 [libsurefire-java] aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 [libsurefire-java] jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 [libsurefire-java] jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 [libsurefire-java] libsurefire-java: Maven pom contains unwanted 
rules
Added indication that 908535 affects src:aether-ant-tasks, src:jnr-posix, and 
src:jruby-joni
Added indication that 908536 affects src:aether-ant-tasks, src:jnr-posix, and 
src:jruby-joni
Added indication that 908537 affects src:aether-ant-tasks, src:jnr-posix, and 
src:jruby-joni
Added indication that 908542 affects src:aether-ant-tasks, src:jnr-posix, and 
src:jruby-joni
> thanks
Stopping processing here.

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

Processed: notfound 908595 in libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4 ...

[Debian Bug Tracking System]

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

> notfound 908595 libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4
Bug #908595 [libbind9-160] krb5-subdomain and ms-subdomain update policy rules 
ineffective
The source libbind9-140 and version 1:9.10.3.dfsg.P4-12.3+deb9u4 do not appear 
to match any binary packages
No longer marked as found in versions libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4.
> found 908595 bind9/1:9.10.3.dfsg.P4-12.3+deb9u4
Bug #908595 [libbind9-160] krb5-subdomain and ms-subdomain update policy rules 
ineffective
Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.3+deb9u4.
> thanks
Stopping processing here.

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

Bug#908138: hddemux: s390x must be added to architectures without knot-resolver

[Steve Langasek]

Package: hddemux
Version: 0.4-6
Followup-For: Bug #908138
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Hi Daniel,

The addition of the knot-resolver build-dependency regressed hddemux
buildability on s390x in Ubuntu, so I've patched the package there as
attached to keep it building.  Please consider applying in Debian as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru hddemux-0.4/debian/control hddemux-0.4/debian/control
--- hddemux-0.4/debian/control  2018-09-05 16:51:08.0 -0700
+++ hddemux-0.4/debian/control  2018-09-09 00:22:04.0 -0700
@@ -7,7 +7,7 @@
  debhelper (>= 11~),
  gnutls-bin [!arm64] ,
  knot-dnsutils [!arm64] ,
- knot-resolver [!arm64] ,
+ knot-resolver [!arm64 !s390x] ,
  libsystemd-dev,
  libuv1-dev,
  nginx-light [!arm64] ,
diff -Nru hddemux-0.4/debian/rules hddemux-0.4/debian/rules
--- hddemux-0.4/debian/rules2018-09-05 16:44:33.0 -0700
+++ hddemux-0.4/debian/rules2018-09-09 00:22:04.0 -0700
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-KRESD_BROKEN_ARCHES := arm64
+KRESD_BROKEN_ARCHES := arm64 s390x
 ifneq (, $(filter $(DEB_HOST_ARCH), $(KRESD_BROKEN_ARCHES)))
   DEB_BUILD_OPTIONS += nocheck
 endif

Processed: found 908595 in libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4

[Debian Bug Tracking System]

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

> found 908595 libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4
Bug #908595 [libbind9-160] krb5-subdomain and ms-subdomain update policy rules 
ineffective
The source libbind9-140 and version 1:9.10.3.dfsg.P4-12.3+deb9u4 do not appear 
to match any binary packages
Marked as found in versions libbind9-140/1:9.10.3.dfsg.P4-12.3+deb9u4.
> thanks
Stopping processing here.

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

Bug#890307: marked as done (tortoisehg: needs update for mercurial 4.6)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 17:35:47 +
with message-id 
and subject line Bug#890307: fixed in tortoisehg 4.7-0.1
has caused the Debian Bug report #890307,
regarding tortoisehg: needs update for mercurial 4.6
to be marked as done.

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

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


-- 
890307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tortoisehg
Version: 4.4.1-1
Severity: serious
X-Debbugs-Cc: mithra...@mithrandi.net

tortoisehg is uninstallable in sid since mercurial was updated to 4.5.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: tortoisehg
Source-Version: 4.7-0.1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated tortoisehg 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, 01 Sep 2018 16:37:37 +0100
Source: tortoisehg
Binary: tortoisehg tortoisehg-nautilus tortoisehg-caja
Architecture: source
Version: 4.7-0.1
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: James Cowgill 
Description:
 tortoisehg - Graphical tool for working with Mercurial
 tortoisehg-caja - Graphical tool for working with Mercurial (Caja extension)
 tortoisehg-nautilus - Graphical tool for working with Mercurial (Nautilus 
extension)
Closes: 890307
Changes:
 tortoisehg (4.7-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. (Closes: #890307)
   * d/control: bump mercurial dependency to 4.7.
   * d/control: migrate vcs repositories to salsa.d.o.
Checksums-Sha1:
 8de7179c37a0655e17f6df57782459988123b401 2167 tortoisehg_4.7-0.1.dsc
 9690c3c78ab0ddd3e270e27a2043dab13bc6a034 7947751 tortoisehg_4.7.orig.tar.gz
 183933aac33bf96fe90efe7531d090b7ae3bf447 17416 tortoisehg_4.7-0.1.debian.tar.xz
 cb9ba3d56240f9325a2e15bac0333bd45e454672 5656 
tortoisehg_4.7-0.1_source.buildinfo
Checksums-Sha256:
 7ab0af13f3df000aa98ad3ddd37275652f8de533ed0ed2f728ce7f93baa28e65 2167 
tortoisehg_4.7-0.1.dsc
 152fb92aa6787da73c0f75646432155921ae554b9d627b6b915eff887e6d29e9 7947751 
tortoisehg_4.7.orig.tar.gz
 890d422398d0d48da46d54cc950080c68ab05ed8436a5ceeb5649078f27f99ff 17416 
tortoisehg_4.7-0.1.debian.tar.xz
 98ad417af6c49d4e98140eb22574639c15ca4cbc84b04da51e653b4a02db7d79 5656 
tortoisehg_4.7-0.1_source.buildinfo
Files:
 d342c44f7448af785976442a2e78eefe 2167 vcs optional tortoisehg_4.7-0.1.dsc
 be07bacf6f934c2a264ecee230f24616 7947751 vcs optional 
tortoisehg_4.7.orig.tar.gz
 fd0353f7db826ef0dad625899c2c9a62 17416 vcs optional 
tortoisehg_4.7-0.1.debian.tar.xz
 06e177c73461d3fdf23b8ded26475c7b 5656 vcs optional 
tortoisehg_4.7-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAluKwjYUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe8+Ag/9Ee9zh00WYpxKV/FCkvBQEkeqWBT0
krhpjiAGSYei46z+R6U2ianjeDTyfVNny0oQOKavV6PHgLVjsEdPZd50va+CFGvI
l0yYwL9KZtxiF56qt6Hqvi8TeQgQBEA5PFV65dPz6y4KPQxOHWNMSyw23T11LNkz
gq8Gu0ABy0I43oqAG1EUYA6ACcOnVR0fg4YKPPdtAVznuNGdH7HdsFQvRKnjNvAW
A0gu150L2fWfXuzejcHrRZx4ag9yRfbFvjSTECY5ew8/ctyeGKQ8Ts9g4bO9n/cf
0gYJq1n3aOc8nO80kXW4HukCpPOZgpGLU4fyGHFEuWtAcRA6fu6NwUuUmWyDOpB/
TTfi7pa0UWDLEcmIvlGaD+dFlduet8oEGxZo9qCOU3Pg8ukOPx+LYGj+F806Bd8j
+SI4nI9DlqT+KLlu/uqUfmZYozTipGRu3TD4atrpU/tyA6Ha1xY2oscGK0g/loZE
gAy+cOJUM+kQUUOfaIVI/lkzHpGg4PKI5Me8Hb2ryQqhFBv8YX5v+3T6dai7cOAE
95SF24Sf9iHelGRYtGMR9ALVnFjY+c0ZRjjySqsknMPeDNQnpQUIJs/DKp+A5yT3
Rd9H4a5gDr4/Pe4Cq/HB7VzvfWo1tHgb04ppN6EpgrI+WRdcHmEwcwZIU8uncC6n
p1M8AebaH9KHguc=
=UrqK
-END PGP SIGNATURE End Message ---

Bug#907774: Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Kurt Roeckx]

On Tue, Sep 11, 2018 at 08:14:35PM +0300, Dmitry Shachnev wrote:
> Hi Kurt,
> 
> On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> > If this is for a call to SSL_CTX_set_max_proto_version(), you can
> > use 0 instead of TLS_MAX_VERSION.
> 
> Good point, thanks.
> 
> However as the patch is temporary, I do not think it is worth
> a new upload to change that.

But maybe you can get upstream to use that instead.

I'm thinking about removing that symbol from the public header,
but that would be a 1.2 thing in that case.


Kurt

Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Dmitry Shachnev]

Hi Kurt,

On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> If this is for a call to SSL_CTX_set_max_proto_version(), you can
> use 0 instead of TLS_MAX_VERSION.

Good point, thanks.

However as the patch is temporary, I do not think it is worth
a new upload to change that.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#908567: [Pkg-openssl-devel] Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Kurt Roeckx]

On Tue, Sep 11, 2018 at 02:28:02PM +0200, Jonas Smedegaard wrote:
> Jan-Marek Glogowski wrote:
> > Qt5 is just the first breaking package - I have no idea, how many 
> > packages use TLS_MAX_VERSION in their code.
> 
> According to https://codesearch.debian.net/search?q=TLS_MAX_VERSION the 
> following packages mention TLS_MAX_VERSION in source code:
> 
>  * fetchmail

Should still work

>  * musescore

Has a copy of the header only

>  * qtbase-opensource-src
>  * shim

Has a copy of the header only

>  * ncrack

Has a copy of the header only

>  * globus-gssapi-gsi

Should still work, only in comment, they don't want TLS 1.3


It really looks like qtbase-opensource-src is the only one that
breaks on it.


Kurt

Bug#907774: [Pkg-openssl-devel] Bug#908567: Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Kurt Roeckx]

On Tue, Sep 11, 2018 at 04:11:02PM +0300, Adrian Bunk wrote:
> 
> Dmitry already implemented my short-term workaround:
> https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/

If this is for a call to SSL_CTX_set_max_proto_version(), you can
use 0 instead of TLS_MAX_VERSION.


Kurt

Bug#908591: marked as done (maven-debian-helper: Ignored rules are included in the installed poms like publish rules)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 17:04:58 +
with message-id 
and subject line Bug#908591: fixed in maven-debian-helper 2.3.2
has caused the Debian Bug report #908591,
regarding maven-debian-helper: Ignored rules are included in the installed poms 
like publish rules
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.)


-- 
908591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maven-debian-helper
Version: 2.3.2
Severity: serious

I introduced a regression in maven-debian-helper/2.3 when I modified
the Maven mojos to use the plugin annotation. A copy/paste error in
SysInstallMojo caused the ignore rules to be added to the installed
poms instead of the publish rules. This caused plugin resolution
issues like #908542.
--- End Message ---
--- Begin Message ---
Source: maven-debian-helper
Source-Version: 2.3.2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated maven-debian-helper 
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: Tue, 11 Sep 2018 18:44:09 +0200
Source: maven-debian-helper
Binary: maven-debian-helper
Architecture: source
Version: 2.3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 maven-debian-helper - Helper tools for building Debian packages with Maven
Closes: 908591
Changes:
 maven-debian-helper (2.3.2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed a regression in maven-debian-helper/2.3 causing the ignored rules
 to be included in the installed poms like publish rules (Closes: #908591)
Checksums-Sha1:
 0d50e9d733cacbe9d6fcfd174c61ece13eaf5b97 2076 maven-debian-helper_2.3.2.dsc
 c4359dbbade342a6ec1228e5edf46a494a62ece6 88780 maven-debian-helper_2.3.2.tar.xz
 e127680e30b473bf11ce2147aa697bf0aeaedff2 14439 
maven-debian-helper_2.3.2_source.buildinfo
Checksums-Sha256:
 2f970d5015c9223448a9e2c7155ac3e132c7e62904588cef9afb1d4994c10b92 2076 
maven-debian-helper_2.3.2.dsc
 cc2b1481dbc8f86bdc8ba1349115dd02ca75e42dd0a97c05709dfc2cf01c299f 88780 
maven-debian-helper_2.3.2.tar.xz
 0081836aca541c28bc9e75f68f0c5a9b391e5671d8df5b2de7035187d39c9417 14439 
maven-debian-helper_2.3.2_source.buildinfo
Files:
 3b93afb81cd5ab7c43f49f5e423bbde3 2076 java optional 
maven-debian-helper_2.3.2.dsc
 69958c9ec6b0baa16c3688db719b479e 88780 java optional 
maven-debian-helper_2.3.2.tar.xz
 ad76311ae2fbb74b0bf3cc5194247233 14439 java optional 
maven-debian-helper_2.3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAluX8d8SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsDVgP/3c+GMNKc01Argzn2+WfQrTMCsDgpXs5
DEZ99WVuq7RPLlrqmPbyRCAPIS7td7XKzhtdWfNHHcxW6dQon+FcN05nRpjvdMUV
2HYhxS08WOLmunG9ojC6hByIGGPeZaRWc2Ldj97JeIVUtGWyDXKVHkb7QI/i12gA
hxlSLVffqmisDzxT6fMN2ZV7lbpLzW3VnkcWuITFD3Y9ovGROIVb81kewSXtOMOH
9b0IalI7ZCMX9hDxSZidV9ZrAMgW/QjcEKt+0NzBju26jGsc1b9QkQBqNOkn9KsB
xZFZPLJFDfEF9x4BaW8/Fx+nGsq698Vh6eC6tEhAGvCIRMb2pi0XCjVcAQs08+ss
rE+C5owVwE+yh/KkTOI8c4PJdUVv/prSxlSi52+TpWt2amaDPMsiCnyBFokGJjrC
RZi5KA5XhXx2r1mekPaYDroFNMViF5m95f8aPj+ONCNgwkWLNC1sHd3Ph1tqyyo/
ouvsIzfpGnBfmYVaSN6oMVvO+sYf+Yw9Liz/3wBNnlkTkCtBoBHdFg0PR7gNpukO
eAFfcgxJedHUQYGrfs0j3bkgwxlWaYmblARcORABpjxj4AKJlchDByuSvLP+tNKy
1GP4hzuf5ItKMMwfan/j3qzdmn5Di+MlL+BeQonmoawvPpHGPC1exftPWs44Pe2e
6Qtk9D2QVAL/
=zEm/
-END PGP SIGNATURE End Message ---

Bug#908070: marked as done (libdazzle FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 17:04:38 +
with message-id 
and subject line Bug#908070: fixed in gtk+3.0 3.24.0-3
has caused the Debian Bug report #908070,
regarding libdazzle FTBFS: test failure
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.)


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

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

...
OK:26
FAIL:   1
SKIP:   0
TIMEOUT:0


The output from the failed tests:

 1/27 test-applicationFAIL 0.09 s (killed by signal 
5 SIGTRAP)

--- command ---
G_TEST_BUILDDIR='/<>/obj-x86_64-linux-gnu/tests' MALLOC_CHECK_='2' 
GSETTINGS_BACKEND='memory' PYTHONDONTWRITEBYTECODE='yes' 
G_TEST_SRCDIR='/<>/tests' G_DEBUG='gc-friendly' 
/<>/obj-x86_64-linux-gnu/tests/test-application
--- stdout ---
/Dazzle/Application/basic: 
--- stderr ---

(/<>/obj-x86_64-linux-gnu/tests/test-application:23435): 
GLib-GIO-CRITICAL **: 12:30:40.566: g_dbus_connection_call_internal: assertion 
'object_path != NULL && g_variant_is_object_path (object_path)' failed
---

Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
FAILED: meson-test 
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 
ninja test returned exit code 1
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: gtk+3.0
Source-Version: 3.24.0-3

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

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

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

Debian distribution maintenance software
pp.
Iain Lane  (supplier of updated gtk+3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Sep 2018 17:33:38 +0100
Source: gtk+3.0
Binary: libgtk-3-0 libgtk-3-0-udeb libgtk-3-common libgtk-3-bin libgtk-3-dev 
libgtk-3-doc gtk-3-examples gir1.2-gtk-3.0 gtk-update-icon-cache libgail-3-0 
libgail-3-dev libgail-3-doc
Architecture: source
Version: 3.24.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Iain Lane 
Description:
 gir1.2-gtk-3.0 - GTK+ graphical user interface library -- gir bindings
 gtk-3-examples - example files for GTK+ 3
 gtk-update-icon-cache - icon theme caching utility
 libgail-3-0 - GNOME Accessibility Implementation Library -- shared libraries
 libgail-3-dev - GNOME Accessibility Implementation Library -- development files
 libgail-3-doc - documentation files of the Gail library
 libgtk-3-0 - GTK+ graphical user interface library
 libgtk-3-0-udeb - GTK+ graphical user interface library - minimal runtime 
(udeb)
 libgtk-3-bin - programs for the GTK+ graphical user interface library
 libgtk-3-common - common files for the GTK+ graphical user interface library
 libgtk-3-dev - development files for the GTK+ library
 libgtk-3-doc - documentation for the GTK+ graphical user interface library
Closes: 908070
Changes:
 gtk+3.0 (3.24.0-3) unstable; urgency=medium
 .
   * Cherry-pick 3c7d5e7 to fix a critical on gtk_application_shutdown when not
 using portals (Closes: #908070)
   * Add Applied-Upstream to last cherry-pick
   * Fix-portal-path-handling.patch: Cherry-pick from upstream.  Fix an
 incorrect dereference in the portal handling code.
Checksums-Sha1:
 32dea1ad87032435cabf6d88a1570f0a8c81ace7 3733 gtk+3.0_3.24.0-3.dsc
 d4d77a1519cb562ee437783184a4888b007d237b 148984 gtk+3.0_3.24.0-3.debian.tar.xz
 751a1fd08db40847f8bde1c9ac04097fb79e2e48 19774 
gtk+3.0_3.24.0-3_source.buildinfo
Checksums-Sha256:
 289326d190f364ac2eae129419d3b00b8cc91b0fca2fc6bfee5d2cc277e5d202 3733 
gtk+3.0_3.24.0-3.dsc
 5387db1530b81d64fbe723007d3ee735f3d428cacd0b8c74fa6966f8fec5 148984 
gtk+3.0_3.24.0-3.debian.tar.xz
 134af9725acea72e3be14d5d7e4a64eb2c58c9902d16446ed661fa0cce30827b 19774 
gtk+3.0_3.24.0-3_source.buildinfo
Files:
 

Bug#908568: nvidia-driver: build error

[Russ Allbery]

Vincent Lefevre  writes:

> Even with just a differing *minor* version? Note that since GCC 5,
> an update of the minor version should just be bug fixes:

>   https://gcc.gnu.org/develop.html

The kernel uses GCC-specific features in an extremely aggressive way.  I'm
not particularly surprised that ABI compatibility might break across minor
versions.  Normally the linux-compiler-gcc-* packages express the required
compiler version for building kernel modules and handle this, but they're
only an upgrade ratchet, not a downgrade ratchet.  (Plus, that would just
create an unsatisfiable dependency since the compiler packages aren't
broken apart that way.)

> If the minor version really matters, why Debian doesn't ship different
> packages, such as gcc-6.3 and gcc-6.4?

I suspect that usually only the kernel is affected.

-- 
Russ Allbery (r...@debian.org)   

Bug#907491: goobook fails to authenticate

[Kurt Roeckx]

Now that bug #907278 is fixed, I think this is fixed too.

Bug#908456: invesalius is no longer installable

[Andreas Tille]

Hi Thiago,

On Tue, Sep 11, 2018 at 10:21:51AM -0300, Thiago Franco de Moraes wrote:
> Hi Andreas,
> 
> Done! I've just pulled the changes to Salsa. I created a new release 
> (3.1.2).

Good. :-)

> But I'm getting this warning:
>  dpkg-gencontrol: warning: Depends field of package invesalius: unknown 
> substitution variable ${python:Depends} 

This was easy - see my latest commit.
 
> This warning happens with both my last version and with the last change you 
> did. I'm using "gbp buildpackage" to create the package in Ubuntu and Debian 
> Sid. I tested the package in Debian Sid and it is working correctly.

Hmmm, here is a less easy one - no idea why you do not get this.  There
are some remaining Python2 scripts that need to be ported:

E: invesalius: missing-dep-for-interpreter python2 => python:any | 
python-minimal:any | python2:any | python2-minimal:any 
(usr/share/invesalius/invesalius/data/viewer_slice.py) #!/usr/bin/python2
N: 
N:You used an interpreter for a script that is not in an essential
N:package. In most cases, you will need to add a Dependency on the package
N:that contains the interpreter. If the dependency is already present,
N:please file a bug against Lintian with the details of your package so
N:that its database can be updated.
N:
N:In some cases a weaker relationship, such as Suggests or Recommends,
N:will be more appropriate.
N:
N:Severity: important, Certainty: possible
N:
N:Check: scripts, Type: binary
N: 
E: invesalius: missing-dep-for-interpreter python2 => python:any | 
python-minimal:any | python2:any | python2-minimal:any 
(usr/share/invesalius/invesalius/data/viewer_volume.py) #!/usr/bin/python2
E: invesalius: missing-dep-for-interpreter python2 => python:any | 
python-minimal:any | python2:any | python2-minimal:any 
(usr/share/invesalius/invesalius/gui/widgets/gradient.py) #!/usr/bin/python2


Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#897711: marked as done (auto-07p: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 16:49:10 +
with message-id 
and subject line Bug#897711: fixed in auto-07p 0.9.1+dfsg-6
has caused the Debian Bug report #897711,
regarding auto-07p: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:auto-07p
Version: 0.9.1+dfsg-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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

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

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/auto-07p_0.9.1+dfsg-4_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c optimization.f90 -o 
../lib/optimization.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c parabolic.f90 -o 
../lib/parabolic.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c timeint.f90 -o ../lib/timeint.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c main.f90 -o ../lib/main.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c blas.f -o ../lib/blas.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c lapack.f -o ../lib/lapack.o
rm -f ../lib/libauto_c.a
gcc -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -O -c user_c.c -o user_c.o
ar cr ../lib/libauto_c.a user_c.o
rm -f user_c.o
make[2]: Leaving directory '/<>/auto-07p-0.9.1+dfsg/07p/src'
# work around case insensitive filesystems
cd ./cmds; for cmd in @H @LB @R @RD; do \
if test ! -r $cmd; then \
cp -p @$cmd $cmd; \
fi \
done
cd ./util;make
make[2]: Entering directory '/<>/auto-07p-0.9.1+dfsg/07p/util'
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O -c utility.f90 -o utility.o
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O autlab.f90 utility.o -o ../bin/autlab
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O double.f90 -o ../bin/double
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O triple.f90 -o ../bin/triple
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O keeplp.f90 utility.o -o ../bin/keeplp
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O keepbp.f90 utility.o -o ../bin/keepbp
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O keepsp.f90 utility.o -o ../bin/keepsp
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O keepuz.f90 utility.o -o ../bin/keepuz
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O deletelp.f90 utility.o -o 
../bin/deletelp
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O listlabels.f90 utility.o -o 
../bin/listlabels
gfortran -g -O2 -fdebug-prefix-map=/<>/auto-07p-0.9.1+dfsg=. 
-fstack-protector-strong -fPIC -fopenmp -O reduce.f90 utility.o -o ../bin/reduce
gfortran -g 

Processed: krb5-subdomain and ms-subdomain update policy rules ineffective

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:9.11.4.P1+dfsg-1
Bug #908595 [libbind9-160] krb5-subdomain and ms-subdomain update policy rules 
ineffective
Marked as found in versions bind9/1:9.11.4.P1+dfsg-1.
> found -1 1:9.11.4+dfsg-4
Bug #908595 [libbind9-160] krb5-subdomain and ms-subdomain update policy rules 
ineffective
Marked as found in versions bind9/1:9.11.4+dfsg-4.

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

Bug#908595: krb5-subdomain and ms-subdomain update policy rules ineffective

[Dominik George]

Package: libbind9-160
Version: 1:9.11.4.P2+dfsg-1
Severity: grave
Tags: security upstream patch
Forwarded: security-offi...@isc.org
Control: found -1 1:9.11.4.P1+dfsg-1
Control: found -1 1:9.11.4+dfsg-4

Hi,

I discovered the following security bug in bind9 a few weeks ago, and
responsibly disclosed it to the ISC security officer. Unfortunately, until
today they did not acknowledge it is a security issue - in contrast, they
proved that they do not fully understand the issue, and now have added a new
feature in the 9.11.4.P2 release which wrongly addresses this security
issue.

The issue is with DDNS update policies using Kerberos, namely the
krb5-subdomain and ms-subdomain update policies for TKEY-GSSAPI. The
documentation states, and has always stated, the following:


  krb5-self
  -

  This rule takes a Kerberos machine principal (host/machine@REALM) for
  machine in REALM and and converts it machine.realm allowing the machine to
  update machine.realm.  The REALM to be matched is specified in the identity
  field.  The name field should be set to "."


  krb5-subdomain
  --

  This rule takes a Kerberos machine principal (host/machine@REALM) for
  machine in REALM and converts it to machine.realm allowing the machine to
  update subdomains of machine.realm.  The REALM to be matched is specified in
  the identity field.  The name field should be set to "."

https://ftp.isc.org/isc/bind9/9.11.4-P1/doc/arm/Bv9ARM.ch06.html#dynamic_update_policies


(I am referring to both krb5-* and ms-* when saying krb5-* in the
following.)

Now the issue is the following (at least in all revisions of bind 9.10 and
9.11, *including the recently released 9.11.4.P1 and .P2*:

krb5-self works a documented, and allows any client showing a valid Kerberos
ticket for machine.realm to update exactly machine.realm.

However, krb5-subdomain is missing the documented check completely - *it
allows updating all records*. To be more precise, it checks the name of the
record to be updated against the name field, instead of, as documented,
against the machine name from the Kerberos identity.

If a BIND TKEY update policy is configured as described in the manual, with
the administrator intending to allow machines to update records below their
own hostname, they are indeed granting full access to the whole zonem
because the documented Kerberos name check is missing.


The ISC security officer claims the following:

  The documented update policy was never intended to work like documented.
  It was intended to work like th ecode does, only checking against the
  configured name field instead of the Kerberos machine name.

  This is not a security issue - it is a documentation bug.

I have raised concerns about these views with the ISC because it has some
implications that I will not believe to be correct:

  There already is a check called subdomai n(without krb5-) that allows
  updating subdomains of the configured name. It can also take a Kerberos
  principal name as TKEY identity - in that case it allows updating the
  subdomain given in the name field if a client shows a valid Kerberos
  ticket for the principal in the identity field. This is what the ISC
  claims to be the intention of krb5-subdomain - I do, however, doubt that
  the person adding the krb5-subdomain check intended to add a new check
  that does the same as the existing subdomain check.

  (I also doubt that the person intended to duplicate an existing check,
  then accidentally added documentation stating the contrary.)

  The code for krb5-subdomain *does* go through all the hassle to extract
  the machine name from the given Kerberos identity - it then ignores the
  result and always returns TRUE instead of checking the record to be
  updated against the machine name it just got hold of with so much work.
  I do doubt that the person writing the original code, in addition to
  the above, intentionally added this code handling a Kerberos identity,
  then always returning TRUE, resulting in the check to do the same as the
  normal subdomain check - only with 100 lines of string manipulation
  resulting in a no-op wrapped around it.


Even after explaining all this to the ISC, they decided to not fix these
checks to do what they are documented (and obviously intended) to do.
Instead, in 9.11.4.P1, they added *new* checks called krb5-subself and
ms-subself that do what krb5-subdomain and ms-subdomain were intended to do,
and sold this as a new feature (they also did not mention my research and
patching efforts doing so, they just told the world they added a cool new
feature - THANK YOU !). The broken -subdomain checks were kept as they
are, including the broken documentation.

Even if the ISC intends to keep the broken checks (which, again, are
duplicates of a more simple check, with tons of string manipulation code
wrapped around), I still consider this a serious security issue because with
the checks not doing what the documentation says for many 

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 908535 libsurefire-java
Bug #908535 [src:aether-ant-tasks] aether-ant-tasks: FTBFS in buster/sid 
(Plugin org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be 
resolved)
Bug reassigned from package 'src:aether-ant-tasks' to 'libsurefire-java'.
No longer marked as found in versions aether-ant-tasks/1.0.1-2.
Ignoring request to alter fixed versions of bug #908535 to the same values 
previously set
> reassign 908536 libsurefire-java
Bug #908536 [src:jnr-posix] jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug reassigned from package 'src:jnr-posix' to 'libsurefire-java'.
No longer marked as found in versions jnr-posix/3.0.45-2.
Ignoring request to alter fixed versions of bug #908536 to the same values 
previously set
> reassign 908537 libsurefire-java
Bug #908537 [src:jruby-joni] jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug reassigned from package 'src:jruby-joni' to 'libsurefire-java'.
No longer marked as found in versions jruby-joni/2.1.18-1.
Ignoring request to alter fixed versions of bug #908537 to the same values 
previously set
> affects 908535 aether-ant-tasks
Bug #908535 [libsurefire-java] aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Added indication that 908535 affects aether-ant-tasks
> affects 908536 jnr-posix
Bug #908536 [libsurefire-java] jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Added indication that 908536 affects jnr-posix
> affects 908537 jruby-joni
Bug #908537 [libsurefire-java] jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Added indication that 908537 affects jruby-joni
> forcemerge 908542 908535 908536 908537
Bug #908542 [libsurefire-java] libsurefire-java: Maven pom contains unwanted 
rules
Bug #908535 [libsurefire-java] aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Removed indication that 908535 affects aether-ant-tasks
Marked as found in versions surefire/2.21.0-2.
Bug #908537 [libsurefire-java] jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Removed indication that 908537 affects jruby-joni
Marked as found in versions surefire/2.21.0-2.
Bug #908542 [libsurefire-java] libsurefire-java: Maven pom contains unwanted 
rules
Added tag(s) ftbfs.
Bug #908536 [libsurefire-java] jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Removed indication that 908536 affects jnr-posix
Marked as found in versions surefire/2.21.0-2.
Merged 908535 908536 908537 908542
> block 908542 by 908591
Bug #908542 [libsurefire-java] libsurefire-java: Maven pom contains unwanted 
rules
Bug #908535 [libsurefire-java] aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 [libsurefire-java] jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 [libsurefire-java] jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
908542 was not blocked by any bugs.
908542 was not blocking any bugs.
Added blocking bug(s) of 908542: 908591
908535 was not blocked by any bugs.
908535 was not blocking any bugs.
Added blocking bug(s) of 908535: 908591
908536 was not blocked by any bugs.
908536 was not blocking any bugs.
Added blocking bug(s) of 908536: 908591
908537 was not blocked by any bugs.
908537 was not blocking any bugs.
Added blocking bug(s) of 908537: 908591
>
End of message, stopping processing here.

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

Bug#908591: maven-debian-helper: Ignored rules are included in the installed poms like publish rules

[Emmanuel Bourg]

Package: maven-debian-helper
Version: 2.3.2
Severity: serious

I introduced a regression in maven-debian-helper/2.3 when I modified
the Maven mojos to use the plugin annotation. A copy/paste error in
SysInstallMojo caused the ignore rules to be added to the installed
poms instead of the publish rules. This caused plugin resolution
issues like #908542.

Bug#908567: Bug#907774: Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage

[Lisandro Damián Nicanor Pérez Meyer]

On Tue, 11 Sep 2018 at 09:00, Jan-Marek Glogowski  wrote:

> Am 11.09.2018 um 11:57 schrieb Adrian Bunk:
>
>
> Qt5 is just the first breaking package - I have no idea, how many packages
> use TLS_MAX_VERSION in
> their code.


Only a handful according to
https://codesearch.debian.net/search?q=TLS_MAX_VERSION

Bug#858936: [Pkg-kannel-devel] Bug#858936: kannel: Please migrate to openssl1.1 in buster [patch]

[Michael Prokop]

Hi,

* Jonas Smedegaard [Tue Mar 06, 2018 at 09:26:47PM +0100]:
> Quoting Frans van Berckel (2018-03-06 20:49:14)
> > Nice to know, upstream officially changed the sources

> > * added support for openssl version > 1.1

> > https://redmine.kannel.org/projects/kannel/repository/revisions/5201

> Great!  thanks for pointing it out!

Any news regarding a new kannel version in Debian?

Currently kannel isn't part of testing and therefore won't make it
into Debian/buster if the RC bugs aren't fixed in time (being
#899559, which is trivial but probably needs a decision from the
maintainer + this one - #858936 - "just" requires an upload of the
current kannel version?).

Please let me/us know if there's anything specific to help with.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#908517: marked as done (pushover: crashes due to missing dep on fonts-freefont-ttf)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 15:36:10 +
with message-id 
and subject line Bug#908517: fixed in pushover 0.0.5+git20180909-2
has caused the Debian Bug report #908517,
regarding pushover: crashes due to missing dep on fonts-freefont-ttf
to be marked as done.

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

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


-- 
908517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pushover
Version: 0.0.5+git20180909-1
Severity: normal

(Reporting on the version that's stuck in NEW, no idea if it applies to the
old one too.)

If fonts-freefont-ttf is not installed, pushover segfaults on startup.
Thus, please add the dependency.


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

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

Versions of packages pushover depends on:
ii  libboost-filesystem1.62.0  1.62.0+dfsg-8
ii  libboost-system1.62.0  1.62.0+dfsg-8
ii  libc6  2.27-6
ii  libfribidi01.0.5-3
ii  libgcc11:8.2.0-6
ii  liblua5.3-05.3.3-1
ii  libpng16-161.6.34-2
ii  libsdl-mixer1.21.2.12-14
ii  libsdl-ttf2.0-02.0.11-4
ii  libsdl1.2debian1.2.15+dfsg2-1
ii  libstdc++6 8.2.0-6
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages pushover recommends:
ii  pushover-data  0.0.5+git20180909-1

pushover suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pushover
Source-Version: 0.0.5+git20180909-2

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated pushover 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: Tue, 11 Sep 2018 16:58:43 +0200
Source: pushover
Binary: pushover pushover-data
Architecture: source
Version: 0.0.5+git20180909-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gürkan Myczko 
Description:
 pushover   - Fun puzzle game with dominos
 pushover-data - Fun puzzle game with dominos, music files
Closes: 908517
Changes:
 pushover (0.0.5+git20180909-2) unstable; urgency=medium
 .
   * Add missing Depends fonts-freefont-ttf. (Closes: #908517)
Checksums-Sha1:
 a1096a9efb8ecaeaf1415af2c230d5cdd3c657d5 2093 pushover_0.0.5+git20180909-2.dsc
 995784c09ecdbb3a8c0c2005d5309cbc472d8394 539972 
pushover_0.0.5+git20180909-2.debian.tar.xz
 c09a68bf09bbe2f03e5723cca34075d9af4ea05d 5548 
pushover_0.0.5+git20180909-2_source.buildinfo
Checksums-Sha256:
 9353d9f815382306d12a6c95a5102b9416663446ccd3d792d5feac83f13750ca 2093 
pushover_0.0.5+git20180909-2.dsc
 70602b754793956458f91a7fe6723979fcef493e4ec1100b26374d693f2f303b 539972 
pushover_0.0.5+git20180909-2.debian.tar.xz
 cbc313a756327b2714643e46f0cfbaf324c0f1ab8bb9a655d91559f5756c4df6 5548 
pushover_0.0.5+git20180909-2_source.buildinfo
Files:
 d97d623cebeb17ed6075bf772727dcc4 2093 games optional 
pushover_0.0.5+git20180909-2.dsc
 2627abda2bf2f58f91e2aae00a94744f 539972 games optional 
pushover_0.0.5+git20180909-2.debian.tar.xz
 7ef8a3840bc72a7125c378d7aff77279 5548 games optional 
pushover_0.0.5+git20180909-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAluX3HoACgkQweDZLphv
fH7oGRAApgLXSxzrCv6CmxQcqXFIgZBkssgAY2h1FkhsqnOY8CdYJ0iXLCWRxPNq
WyYMHj38DJ+vttLiwRNT2SanWngnyRAcbHoTo/GhhngHlB20P/HRzWfTwKfrZEZt
m4Ai3EJGF4ITAKV1w5m8TeUGY8mAW/UScPYoUM+/k/TI7rcSBkmnNe5sI4I5sPCT
LgKP4ArC41N21uZDK6y7jxFz70k7/yjWJRIUfz8dop0NMVFASEjVfp9ZclsGR2OA
bCC8ZKYHyBu+hr+R51qSsE2ZeW00aNQrYai7/ZBZnZIsc+DjLAhR89AobRv2uOTL

Bug#908070: libdazzle FTBFS: test failure

[Iain Lane]

Control: reassign -1 libgtk-3-0
Control: found -1 3.24.0-2
Control: affects -1 src:libdazzle
Control: tags -1 + upstream confirmed fixed-upstream

Hey,

On Wed, Sep 05, 2018 at 11:21:02PM +0300, Adrian Bunk wrote:
> (/<>/obj-x86_64-linux-gnu/tests/test-application:23435): 
> GLib-GIO-CRITICAL **: 12:30:40.566: g_dbus_connection_call_internal: 
> assertion 'object_path != NULL && g_variant_is_object_path (object_path)' 
> failed

Thanks!

I think this is
https://gitlab.gnome.org/GNOME/gtk/commit/3c7d5e749ccafa75718ef00f1d5f6cdc0defacb3.

In gtk+3.0 3.24 there is a bug when shutting down GtkApplications and
not using portals. We should probably cherry-pick that patch if it's
breaking things. FTR, I doubt this g_critical is causing visible
problems for people at runtime, but an FTBFS fix is justification
enough.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Processed: Re: Bug#908070: libdazzle FTBFS: test failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgtk-3-0
Bug #908070 [src:libdazzle] libdazzle FTBFS: test failure
Bug reassigned from package 'src:libdazzle' to 'libgtk-3-0'.
No longer marked as found in versions libdazzle/3.30.0-1.
Ignoring request to alter fixed versions of bug #908070 to the same values 
previously set
> found -1 3.24.0-2
Bug #908070 [libgtk-3-0] libdazzle FTBFS: test failure
Marked as found in versions gtk+3.0/3.24.0-2.
> affects -1 src:libdazzle
Bug #908070 [libgtk-3-0] libdazzle FTBFS: test failure
Added indication that 908070 affects src:libdazzle
> tags -1 + upstream confirmed fixed-upstream
Bug #908070 [libgtk-3-0] libdazzle FTBFS: test failure
Added tag(s) upstream, fixed-upstream, and confirmed.

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

Bug#908561: marked as done (i386 rustc produces SSE2 instructions)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 14:44:01 +
with message-id 
and subject line Bug#908561: fixed in rustc 1.28.0+dfsg1-3
has caused the Debian Bug report #908561,
regarding i386 rustc produces SSE2 instructions
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.)


-- 
908561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rustc
Version: 1.28.0+dfsg1-2
Severity: critical

Build anything with the rustc compiler for i386, and the result will
contain SSE2 instructions. This means rust-based packages don't support
the full range of what the i386 Debian architecture supports.

Specifically, this is the main cause for #908396/#908449.

Mike


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

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

Versions of packages rustc depends on:
ii  binutils  2.31.1-4
ii  gcc   4:8.1.0-1
ii  libc6 2.27-5
ii  libc6-dev [libc-dev]  2.27-5
ii  libgcc1   1:8.2.0-3
ii  libllvm6.01:6.0.1-6
ii  libstd-rust-dev   1.28.0+dfsg1-2
ii  libstdc++68.2.0-3

Versions of packages rustc recommends:
ii  cargo 0.28.0-1
ii  rust-gdb  1.28.0+dfsg1-2

Versions of packages rustc suggests:
pn  rust-doc  
pn  rust-src  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.28.0+dfsg1-3

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated rustc 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: Tue, 11 Sep 2018 15:54:27 +0200
Source: rustc
Binary: rustc libstd-rust-1.28 libstd-rust-dev rust-gdb rust-lldb rust-doc 
rust-src
Architecture: source
Version: 1.28.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Julien Cristau 
Description:
 libstd-rust-1.28 - Rust standard libraries
 libstd-rust-dev - Rust standard libraries - development files
 rust-doc   - Rust systems programming language - Documentation
 rust-gdb   - Rust debugger (gdb)
 rust-lldb  - Rust debugger (lldb)
 rust-src   - Rust systems programming language - source code
 rustc  - Rust systems programming language
Closes: 908561
Changes:
 rustc (1.28.0+dfsg1-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ximin Luo ]
   * More sparc64 fixes, and increase allowed-test-failures there to 180.
 .
   [ Julien Cristau ]
   * Don't use pentium4 as i686 baseline (closes: #908561)
Checksums-Sha1:
 bd6e8fad52eaa5c9975f26dd6e0ce30042d8011a 2958 rustc_1.28.0+dfsg1-3.dsc
 846f853829dd1da4b76f2cf9355730fd73cecace 61640 
rustc_1.28.0+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 3a3f15776b44297df702328a722fa15fd777b2037ca1cbcb79ba860bf8251485 2958 
rustc_1.28.0+dfsg1-3.dsc
 426e14c5f1cc4ef8eedd1bb1ceea3a286b4dfea98518dfba7f73777107c8f683 61640 
rustc_1.28.0+dfsg1-3.debian.tar.xz
Files:
 a4778d66e04ce7b66c4fdfcd804a9654 2958 devel optional rustc_1.28.0+dfsg1-3.dsc
 a627fb5c414f71081036127f1240f1dc 61640 devel optional 
rustc_1.28.0+dfsg1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAluXyp4ACgkQnbAjVVb4
z63hJg//XdJPsOtxDqzofVpXiQDRDTJG+nxqCF5poyOcvYrR4L0LLfhbYTBxtWzk
w1oCozpX54Fv27P4jWpqgQWcn5u5qlcsaDteusnsqLTX3NHnlErD5TJw8kv34W9c
d+2UzNtaquJTrNV6hIgEQ8QP5ao5to43u1KBEPhuy5hLWFWORk63Ol31CF1j42o4
nl7EnM73pFKfSLWNH72XqEQTAmlKk0Jg2yH/UB3Ub8V2KQixME6MpOuirgNhfLNC
nlZmv08fHihsiC6irDg17rlQ1f0MpLeddYxT3GNDwSiIVUEWFxGCXUj1tXMlCfX2
9WYrZZqrSIo5Y6v3UbI/H0bJrEtAPsx62hrZEiduNQa9boVLNdCKWxATZ5jCiYP9

Processed: forcibly merging 908087 908578

[Debian Bug Tracking System]

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

> forcemerge 908087 908578
Bug #908087 [reportbug] reportbug: Fails with: TypeError: fixer() missing 1 
required positional argument: 'check_hostname'
Bug #908578 [reportbug] reportbug: crash on requesting madison
Severity set to 'grave' from 'normal'
908578 was not blocked by any bugs.
908578 was not blocking any bugs.
Added blocking bug(s) of 908578: 906127
Merged 908087 908578
> thanks
Stopping processing here.

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

Processed: Re: Bug#908459: theseus FTBFS with gcc 8

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #908459 {Done: Fabian Kloetzl } [src:theseus] 
theseus FTBFS with gcc 8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions theseus/3.3.0-7.

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

Bug#908459: theseus FTBFS with gcc 8

[Adrian Bunk]

Control: reopen -1

On Mon, Sep 10, 2018 at 03:18:13PM +0200, Fabian Klötzl wrote:
>...
> On 10.09.18 13:59, Andreas Tille wrote:
> > /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops 
> > -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result 
> > -Wformat-truncation=0 -pthread  -c logistic_dist.c
> > logistic_dist.c: In function 'evallogisticML':
> > logistic_dist.c:172:1: error: 'reciptmp.16' is used uninitialized in this 
> > function [-Werror=uninitialized]
> >  evallogisticML(const double *x, const int n,
> >  ^~
> > cc1: all warnings being treated as errors
> > 
> 
> That is a compiler bug [1, 2]. Temporarily deactivating -ffast-math or
> -Werror should help to move on, nonetheless.

Some builds were still running into #897876 due to the buildd chroots 
only regenerated twice per week (which is not something you should be
worried about), but the armhf/i386 and ppc64el FTBFS look more like
actual problems that need fixing in theseus.

> Best,
> Fabian
>...

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#908580: ibus-table-createdb fails with nonexisting $HOME

[Adrian Bunk]

Package: ibus-table
Version: 1.9.21-1
Severity: serious
Control: affects -1 src:ibus-table-others

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ibus-table-others.html

...
/usr/bin/ibus-table-createdb  -n compose.db -s compose.txt
Traceback (most recent call last):
  File "/usr/share/ibus-table/engine/tabcreatedb.py", line 455, in 
main()
  File "/usr/share/ibus-table/engine/tabcreatedb.py", line 175, in main
create_database=True)
  File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 262, in __init__
import ibus_table_location
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in 

__module_init = __ModuleInitializer()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in 
__init__
_init()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in _init
os.makedirs(IBUS_TABLE_LOCATION['data_home'])
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/nonexistent'
make[2]: *** [Makefile:519: compose.db] Error 1


This can be reproduced with:

# works
$ HOME=/tmp /usr/bin/ibus-table-createdb -n compose.db -s compose.txt

# fails
$ HOME=/doesnotexist /usr/bin/ibus-table-createdb -n compose.db -s compose.txt

Processed: ibus-table-createdb fails with nonexisting $HOME

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ibus-table-others
Bug #908580 [ibus-table] ibus-table-createdb fails with nonexisting $HOME
Added indication that 908580 affects src:ibus-table-others

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

Processed: bug 908070 is forwarded to https://gitlab.gnome.org/GNOME/libdazzle/issues/25

[Debian Bug Tracking System]

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

> forwarded 908070 https://gitlab.gnome.org/GNOME/libdazzle/issues/25
Bug #908070 [src:libdazzle] libdazzle FTBFS: test failure
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/libdazzle/issues/25'.
> thanks
Stopping processing here.

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

Bug#899115: marked as done (pasco FTCBFS: hard codes plain gcc, policy 4.6 violation)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 13:49:20 +
with message-id 
and subject line Bug#899115: fixed in pasco 20040505-3
has caused the Debian Bug report #899115,
regarding pasco FTCBFS: hard codes plain gcc, policy 4.6 violation
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.)


-- 
899115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pasco
Version: 20040505-2
Severity: serious
Justification: policy 4.6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

pasco fails to cross build from source, because its upstream Makefile
hard codes the build architecture compiler. While fixing it, I spotted a
policy 4.6 (error trapping in Makefiles) violation (hence serious). The
attached patch fixes both and makes pasco cross build successfully.
Please consider applying it.

Helmut
diff --minimal -Nru pasco-20040505/debian/changelog 
pasco-20040505/debian/changelog
--- pasco-20040505/debian/changelog 2017-01-26 00:04:03.0 +0100
+++ pasco-20040505/debian/changelog 2018-05-19 13:33:09.0 +0200
@@ -1,3 +1,10 @@
+pasco (20040505-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the upstream Makefile. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 19 May 2018 13:33:09 +0200
+
 pasco (20040505-2) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru pasco-20040505/debian/patches/10_add-GCC-hardening.patch 
pasco-20040505/debian/patches/10_add-GCC-hardening.patch
--- pasco-20040505/debian/patches/10_add-GCC-hardening.patch2015-07-13 
00:34:07.0 +0200
+++ pasco-20040505/debian/patches/10_add-GCC-hardening.patch2018-05-19 
13:33:09.0 +0200
@@ -1,14 +1,23 @@
 Last-Update: 2015-07-12
 Index: pasco-1.0+20040505/src/Makefile
 ===
+
+Also use $(CC) for cross building.
+
+And fix the policy 4.6 violation.
+
 --- pasco-1.0+20040505.orig/src/Makefile
 +++ pasco-1.0+20040505/src/Makefile
-@@ -1,7 +1,7 @@
+@@ -1,7 +1,10 @@
  all: install
  
- install:  pasco.c
+-install:  pasco.c
 -  gcc -o pasco pasco.c -lm -lc;cp pasco ../bin
-+  gcc $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) -o pasco pasco.c -lm -lc;cp pasco 
../bin
++pasco:  pasco.c
++  $(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) -o $@ $< -lm -lc
++
++install: pasco
++  cp pasco ../bin
  
  installwin:  pasco.c
gcc -DCYGWIN -o pasco.exe pasco.c -lm -lc;cp pasco.exe ../bin
--- End Message ---
--- Begin Message ---
Source: pasco
Source-Version: 20040505-3

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

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

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated pasco 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: Tue, 11 Sep 2018 15:28:39 +0200
Source: pasco
Binary: pasco
Architecture: source
Version: 20040505-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Description:
 pasco  - Internet Explorer cache forensic analysis tool
Closes: 899115
Changes:
 pasco (20040505-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Helmut Grohne ]
   * Fix the upstream Makefile. (Closes: #899115)
 .
   [ Lorenzo "Palinuro" Faletra ]
   * debian/control:
   - Bump Standards-Version 4.1.4.1.
   * Add debian/gbp.conf.
 .
   [ Raphaël Hertzog ]
   * Bump Standards-Version to 4.2.1
   * Bump debhelper compat level to 11
   * Add missing string.h include to fix implicit declarations warnings
Checksums-Sha1:
 aa18fc6b30e3f4265c4297428f6e39f3ccf27993 1634 pasco_20040505-3.dsc
 b3ce791a9afd7634d2788b4a62dc3569e7c56e7e 4532 pasco_20040505-3.debian.tar.xz
 3d2254c4a91dec14815c2fb3b43e5fd20dc57d5b 5525 pasco_20040505-3_amd64.buildinfo
Checksums-Sha256:
 8034c5c3cdb2f3ec9641466a8c971ba8ba3038764a7e7c38b4c9bcf13ff11bed 1634 
pasco_20040505-3.dsc
 1dd72dc629842b163b27a7eb42d897cebbf9d3a3e9d217e9815b6e59e29c7724 4532 
pasco_20040505-3.debian.tar.xz
 

Bug#905818: marked as done (dbusada: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 13:48:58 +
with message-id 
and subject line Bug#905818: fixed in dbusada 0.4.2-1
has caused the Debian Bug report #905818,
regarding dbusada: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
905818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbusada
Version: 0.4.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Reto Buerki , ftpmas...@debian.org

Hi,

I just ACCEPTed dbusada from NEW but noticed it was missing 
attribution in debian/copyright for at least Tero Koskinen?

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


Regards,

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

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

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

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated dbusada package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 04 Sep 2018 10:11:55 +0200
Source: dbusada
Binary: libdbusada0.4.1 libdbusada4-dev
Architecture: source
Version: 0.4.2-1
Distribution: experimental
Urgency: medium
Maintainer: Reto Buerki 
Changed-By: Nicolas Boulenguez 
Description:
 libdbusada0.4.1 - Ada bindings to the D-Bus message bus system (runtime)
 libdbusada4-dev - Ada bindings to the D-Bus message bus system
Closes: 905818
Changes:
 dbusada (0.4.2-1) experimental; urgency=medium
 .
   [ Reto Buerki ]
   * Update copyright (Closes: #905818)
   * Update to release 0.4.2
 .
   [ Nicolas Boulenguez ]
   * Simplify the packaging with dh-ada-library.
   * Regenerate the thin binding (to ensure that the end user can rebuild)
 but with g++-8 (independently of the current default C++ compiler).
   * Standards-Version: 4.2.1. No changes.
   * Give each binary package a distinct description.
   * Set as-needed and no-undefined linker options explicitly.
   * Pass a consistent set of flags to each Make, show them in the log.
   * Use dh_auto_* options instead of raw make (for example, -j).
Checksums-Sha1:
 c0f740060039f23af97b6d3130048eaff272bf2d 2157 dbusada_0.4.2-1.dsc
 ef5b2f1fc7bd2a48b3a8d47a3e21881192f5ccf3 44482 dbusada_0.4.2.orig.tar.bz2
 f144fa7c4b071418ec2696523c4f2d3431c43822 7444 dbusada_0.4.2-1.debian.tar.xz
Checksums-Sha256:
 dcd042a265ae5c55a0c43e842be9a84a8da936ca733cd121d34d83c9148b9a8c 2157 
dbusada_0.4.2-1.dsc
 faf27e86d940425db73efb1c4cc564427713e7e0150b1b8580923526aad9b4ac 44482 
dbusada_0.4.2.orig.tar.bz2
 105476867490ea740701d64955f18f2a8724dfb0f92e0aeded0c88c88b43e255 7444 
dbusada_0.4.2-1.debian.tar.xz
Files:
 71cf593b58e5396896200e45cefed179 2157 libs optional dbusada_0.4.2-1.dsc
 f1d5c46612ab87f50b9e39974b7c7de2 44482 libs optional dbusada_0.4.2.orig.tar.bz2
 ab32ec166276ef4948ddc6f0f5e7aabf 7444 libs optional 
dbusada_0.4.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAluXxWkTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38japeEACHJAiPjtz4/cTdEcWPfdhYBV9gwD+x
eXHQH5GpX1LWOJuqSzdbDKHFex9f/MB/uRyOm6QqtCdRrcZJqvpKQdRIHXpBxtAP
80lqZH3hHDgfuVKsgx5LBIDWmeJB8ybOOI538EDU40oq9cfKNCDrc2ZWT3kCudjb
MmywNl9qGyuF5cnHhDWQSeDrZkGkoKGO2bFswaCaAgb4aXVb5h/vAbqcrfrc0mWW
cIbB89jxjd4m+hlgJVIlRYZwpb69pcy+/r73HG2iWaHeDXFr5k8BjDSitlqYEX/9
Xx3D3CjO6uE8JXW26OaETxQu3msTCTyu54TbVfRAODyJ/KKJrLSSRxpewEeBNfe3
7jjJzT/t9Q8nT7VEhZbt/0jaQS9RBTgWMXc1KyabARpGtwfLVRamMEt/Y8vzHs6H
ht4zbfoC6VFH3miJBH+ge+B+1VxiTNbiblqS+GW9zctjEXvtjUGX+i6ertGX55Mc
1GwS0+tFQAuoSlIGbjvqS5Pi2Ff5LOQ0XXTDlHvKGGfwln6/IW4Gt58vWJvXtuPa
Hm4xqs2wKmfoJ5YhDsIV4c5pXXEaiCkWWzzgWfY1qvUyUErpR+dSY6F3L/1Rs/qp
NJc29HDJpSlaK+AVjZA4M4o5BM83qP8fB1sYBloRUHgN+8MeSwg3QoXzPRlmQM1n
vWpj6z0EMFZ1AQ==
=r1mx
-END PGP SIGNATURE End Message ---

Bug#868424: marked as done (gnome-breakout: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2018 13:49:05 +
with message-id 
and subject line Bug#868424: fixed in gnome-breakout 0.5.3-6
has caused the Debian Bug report #868424,
regarding gnome-breakout: Please drop the (build-)dependency against gnome-vfs
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.)


-- 
868424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-breakout
Version: 0.5.3-5
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: gnome-breakout
Source-Version: 0.5.3-6

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated gnome-breakout 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: Tue, 11 Sep 2018 15:01:54 +0200
Source: gnome-breakout
Binary: gnome-breakout
Architecture: source
Version: 0.5.3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 gnome-breakout - Clone of the classic game Breakout, written for GNOME
Closes: 868424 886078
Changes:
 gnome-breakout (0.5.3-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yavor Doganov ]
   * Port gnome-breakout to Goocanvas and GNOME 3.
 Thanks to Yavor Doganov for the patch! (Closes: #868424)
   * This package doesn't use GConf but ends up linking with it because
 libgnomui depends on it and exposes this dependency via its pkg-config 
file.
 Pass --as-needed to the linker to avoid that. (Closes: #886078)
 .
   [ Markus Koschany ]
   * Drop deprecated menu file.
   * Switch to compat level 11.
   * Declare compliance with Debian Policy 4.2.1.
   * wrap-and-sort -sa.
Checksums-Sha1:
 14f1e442bc23d069a4e44748041b6c564e9e299d 2210 gnome-breakout_0.5.3-6.dsc
 014533887d569d73cf7b7835e9b7884ecfdb18b5 21772 
gnome-breakout_0.5.3-6.debian.tar.xz
 d62e55db8145163634eb89f7d4f7141d34a193ca 14214 
gnome-breakout_0.5.3-6_amd64.buildinfo
Checksums-Sha256:
 15cc1b805b990e81a5335bf5040d16a1a5d8781d5171bad98c4c9bd18e9da75d 2210 
gnome-breakout_0.5.3-6.dsc
 755b1b0edf6421f18e621f19a3c525e17afb2e658bda18456612fb2fb6847de9 21772 
gnome-breakout_0.5.3-6.debian.tar.xz
 0ae6f9c60f89209f5e291d86c0c2409ad7dbdeca03bcded716f52e0f2224950d 14214 
gnome-breakout_0.5.3-6_amd64.buildinfo
Files:
 6a993675eb2a31010a9c5ee82e9d38ac 2210 games optional gnome-breakout_0.5.3-6.dsc
 864fe9f500d2a5931d0c97cb6bf96249 21772 games optional 
gnome-breakout_0.5.3-6.debian.tar.xz
 ccd4344d2c211c2988761a17cb5e4129 14214 games optional 
gnome-breakout_0.5.3-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAluXwipfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkosgP/2eM62JgvhmORQ3pQju33gJdiuM+JozHwS3+
/yuEPA1R5RXH0+h+Xt6xmbVMfhYt39Tq+u/veuwEr1HNkxAT/Qlnmeu3wNF0b91g
jxrIazjAblmAI3RV3WMzYTU9Hbk1ePFENk3kD7+ht9MFqYCP3WrrzxdxshzSd6Pi
HiSyg5jaSwXp8mTzrgXXy3OhAGpAGtHlLFmV3rF/mXr7LK6Uw7sNDPpxWQuLUKv/
L1Rr6Zx4joW0ErhaLwTE/XLnhNAWTbc+nyCl/6jN99bAatC3sCoPdcnVbfnmBb8X
eDYalq6Ao5Y07t+BiCox2iaLIOV8FxrvLRn5+exV7a5kYByLSnjRikaJrtPKtfEz
L+PYw1KG6WYhojZK8YQ9XgZsTnMgKu7kgf86G+lHm5Me/wcr4LM8DG3zfRgJ5R9C
e7yqNWY8wh1G3aexvBjBsXAcGL3uStVtlTaQXkNTRr6I4betJmbJ+obK2gyvqgfB
31Q2H7d51FP+0XGbv+MJUbj+yPvMWf4HELdJFwLxCFYRr+Mz+/EAD5NKexbbcdO0
bO7bxvcFE3Am+1Wz3tDj4+IFU/+GbtFXeQT8XU1smQ2Z2CmnkHFyQ4x+Ja41IkpA

Bug#908456: invesalius is no longer installable

[Thiago Franco de Moraes]

Hi Andreas,

Done! I've just pulled the changes to Salsa. I created a new release 
(3.1.2). But I'm getting this warning:
 dpkg-gencontrol: warning: Depends field of package invesalius: unknown 
substitution variable ${python:Depends} 

This warning happens with both my last version and with the last change you 
did. I'm using "gbp buildpackage" to create the package in Ubuntu and Debian 
Sid. I tested the package in Debian Sid and it is working correctly.

Best regards.

- Mensagem original -
De: "Andreas Tille" 
Para: 908...@bugs.debian.org
Cc: "Thiago Franco Moraes" 
Enviadas: Segunda-feira, 10 de setembro de 2018 4:01:41
Assunto: Re: Bug#908456: invesalius is no longer installable

Hi Thiago

On Mon, Sep 10, 2018 at 08:41:27AM +0300, Adrian Bunk wrote:
> Package: invesalius
> Version: 3.1.1-1
> Severity: grave
> 
> The following packages have unmet dependencies:
>  invesalius : Depends: python-gdcm but it is not going to be installed
>   Depends: python-vtkgdcm but it is not going to be installed

Gdcm has switched to Python3 now.  Can you please check with latest
invesalius and commit the needed changes to Git?

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: tagging 891104

[Debian Bug Tracking System]

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

> tags 891104 + buster sid
Bug #891104 [wapiti] wapiti: python-beautifulsoup is replaced with python-bs4
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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