Bug#889522: baresip FTBFS: test failure

[Adrian Bunk]

Source: baresip
Version: 0.5.7-1
Severity: serious

Some recent change in unstable makes baresip FTBFS:

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

...
[ RUN  ] test_ua_register
ua: SIP register failed: Invalid argument
TEST_ERR: test/ua.c:114: (Invalid argument)
selftest: ua_register test failed (Invalid argument)
ua: SIP register failed: Invalid argument
TEST_ERR: test/ua.c:114: (Invalid argument)
selftest: ua_register test failed (Invalid argument)
ua: SIP register failed: Invalid argument
TEST_ERR: test/ua.c:114: (Invalid argument)
selftest: ua_register test failed (Invalid argument)
test_ua_register: test failed (Invalid argument)
test failed (Invalid argument)
re main loop:
  maxfds:  1024
  nfds:24
  method:  3 (epoll)

Makefile:208: recipe for target 'test' failed
make[1]: *** [test] Error 22

Bug#885459: marked as done (telegram-desktop: FTBFS on all architectures)

[Debian Bug Tracking System]

Your message dated Sun, 4 Feb 2018 09:02:09 +0200
with message-id <20180204070209.GA25993@localhost>
and subject line Re: Bug#885459: telegram-desktop: FTCBFS on all architectures
has caused the Debian Bug report #885459,
regarding telegram-desktop: FTBFS on all architectures
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.)


-- 
885459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telegram-desktop
Source-Version: 1.2.1-2
Severity: grave

Package telegram-desktop FTCBFS on all architecture according to buildd 
logs[1].

There are all kinds of reasons about build failures across different 
architectures, including cc1plus internal compiler error, timeout, vmem 
exhaustion, etc.

Please investigate into this issue. I'm not sure what we can do, perhaps the 
best plan is to force non-parallel compilation (instead of make -j4 or 
whatsoever on buildds).

Regards,
Boyuan Yang

[1] https://buildd.debian.org/status/package.php?p=telegram-desktop


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 1.2.6-1

On Wed, Dec 27, 2017 at 08:16:45PM +0800, Boyuan Yang wrote:
>...
> There are all kinds of reasons about build failures across different 
> architectures, including cc1plus internal compiler error, timeout, vmem 
> exhaustion, etc.
>...

This seems fixed now, except for the mips/mipsel memory exhaustion that 
is handled in #889139:
https://buildd.debian.org/status/package.php?p=telegram-desktop

cu
Adrian

-- 

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

Processed: Re: severity of 889189 is normal

[Debian Bug Tracking System]

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

> severity 889189 grave
Bug #889189 [inventor-doc] inventor-doc is empty
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#889521: libmsv FTBFS on mips64el: shared library not built

[Adrian Bunk]

Source: libmsv
Version: 1.1.1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libmsv=mips64el=1.1.1-1=1517695216=0

...
checking whether to build shared libraries... no
...
mv debian/libmsv1/usr/lib/*.a debian/libmsv-dev/usr/lib
mv debian/libmsv1/usr/lib/*.so debian/libmsv-dev/usr/lib
mv: cannot stat 'debian/libmsv1/usr/lib/*.so': No such file or directory
debian/rules:45: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1


For some reason it Works for me on eller.

Processed: Re: Bug#889151: python3-matplotlib: backports.functools_lru_cache, subprocess32 are not Python 3 dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #889151 [python3-matplotlib] python3-matplotlib: 
backports.functools_lru_cache, subprocess32 are not Python 3 dependencies
Severity set to 'serious' from 'important'
> affects -1 src:python-memprof
Bug #889151 [python3-matplotlib] python3-matplotlib: 
backports.functools_lru_cache, subprocess32 are not Python 3 dependencies
Added indication that 889151 affects src:python-memprof

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

Bug#873440: ruby-grpc FTBFS: cc1: error: -Wformat-security ignored without -Wformat

[Steve Langasek]

Package: ruby-grpc
Version: 1.3.2+debian-3
Followup-For: Bug #873440
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hi Pirate,

Here's a patch to fix this build failure, which has been uploaded to Ubuntu.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ruby-grpc-1.3.2+debian/debian/patches/no-cflags-override.patch 
ruby-grpc-1.3.2+debian/debian/patches/no-cflags-override.patch
--- ruby-grpc-1.3.2+debian/debian/patches/no-cflags-override.patch  
1969-12-31 16:00:00.0 -0800
+++ ruby-grpc-1.3.2+debian/debian/patches/no-cflags-override.patch  
2018-02-03 20:20:51.0 -0800
@@ -0,0 +1,19 @@
+Description: Don't set -Wno-format which conflicts with default hardening flags
+ ruby-grpc sets -Wno-format in cflags, but by default Debian sets -Wformat
+ -Werror=format-security.  Passing -Wno-format breaks setting
+ -Werror=format-security, which should be kept for security reasons.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/873400
+
+Index: ruby-grpc-1.3.2+debian/src/ruby/ext/grpc/extconf.rb
+===
+--- ruby-grpc-1.3.2+debian.orig/src/ruby/ext/grpc/extconf.rb
 ruby-grpc-1.3.2+debian/src/ruby/ext/grpc/extconf.rb
+@@ -106,7 +106,6 @@
+ $CFLAGS << ' -Wall '
+ $CFLAGS << ' -Wextra '
+ $CFLAGS << ' -pedantic '
+-$CFLAGS << ' -Wno-format '
+ 
+ output = File.join('grpc', 'grpc_c')
+ puts 'Generating Makefile for ' + output
diff -Nru ruby-grpc-1.3.2+debian/debian/patches/series 
ruby-grpc-1.3.2+debian/debian/patches/series
--- ruby-grpc-1.3.2+debian/debian/patches/series2017-08-04 
11:36:52.0 -0700
+++ ruby-grpc-1.3.2+debian/debian/patches/series2018-02-03 
20:18:41.0 -0800
@@ -3,3 +3,4 @@
 no-make-in-extconf.patch
 use-system-grpc.patch
 fix-protoc-path.patch
+no-cflags-override.patch

Bug#889504: marked as done (libqt5core5a fails to install: rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 01:36:04 +
with message-id 
and subject line Bug#889504: fixed in qtbase-opensource-src 5.9.2+dfsg-9
has caused the Debian Bug report #889504,
regarding libqt5core5a fails to install: rmdir: failed to remove 
'/etc/xdg/QtProject': No such file or directory
to be marked as done.

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

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


-- 
889504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5core5a
Version: 5.9.2+dfsg-8
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

libqt5core5a fails to install:

# apt-get install libqt5core5a
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libdouble-conversion1 libglib2.0-0 libicu57 libpcre2-16-0
Suggested packages:
  libthai0
Recommended packages:
  libglib2.0-data shared-mime-info xdg-user-dirs qttranslations5-l10n
The following NEW packages will be installed:
  libdouble-conversion1 libglib2.0-0 libicu57 libpcre2-16-0 libqt5core5a
0 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 12.7 MB of archives.
After this operation, 42.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.stw-bonn.de/debian sid/main amd64 libdouble-conversion1 amd64 
2.0.1-4 [33.7 kB]
Get:2 http://ftp.stw-bonn.de/debian sid/main amd64 libglib2.0-0 amd64 2.54.3-2 
[2822 kB]
Get:3 http://ftp.stw-bonn.de/debian sid/main amd64 libicu57 amd64 57.1-8 [7699 
kB]
Get:4 http://ftp.stw-bonn.de/debian sid/main amd64 libpcre2-16-0 amd64 10.22-5 
[174 kB]
Get:5 http://ftp.stw-bonn.de/debian sid/main amd64 libqt5core5a amd64 
5.9.2+dfsg-8 [1930 kB]
Fetched 12.7 MB in 0s (70.6 MB/s)  
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libdouble-conversion1:amd64.
(Reading database ... 10065 files and directories currently installed.)
Preparing to unpack .../libdouble-conversion1_2.0.1-4_amd64.deb ...
Unpacking libdouble-conversion1:amd64 (2.0.1-4) ...
Selecting previously unselected package libglib2.0-0:amd64.
Preparing to unpack .../libglib2.0-0_2.54.3-2_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.54.3-2) ...
Selecting previously unselected package libicu57:amd64.
Preparing to unpack .../libicu57_57.1-8_amd64.deb ...
Unpacking libicu57:amd64 (57.1-8) ...
Selecting previously unselected package libpcre2-16-0:amd64.
Preparing to unpack .../libpcre2-16-0_10.22-5_amd64.deb ...
Unpacking libpcre2-16-0:amd64 (10.22-5) ...
Selecting previously unselected package libqt5core5a:amd64.
Preparing to unpack .../libqt5core5a_5.9.2+dfsg-8_amd64.deb ...
Unpacking libqt5core5a:amd64 (5.9.2+dfsg-8) ...
Setting up libdouble-conversion1:amd64 (2.0.1-4) ...
Setting up libglib2.0-0:amd64 (2.54.3-2) ...
No schema files found: doing nothing.
Setting up libicu57:amd64 (57.1-8) ...
Processing triggers for libc-bin (2.26-6) ...
Setting up libpcre2-16-0:amd64 (10.22-5) ...
Setting up libqt5core5a:amd64 (5.9.2+dfsg-8) ...
rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory
dpkg: error processing package libqt5core5a:amd64 (--configure):
 installed libqt5core5a:amd64 package post-installation script subprocess 
returned error exit status 1
Processing triggers for libc-bin (2.26-6) ...
Errors were encountered while processing:
 libqt5core5a:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
#

Helmut
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.9.2+dfsg-9

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtbase-opensource-src package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 22:12:49 -0300
Source: qtbase-opensource-src
Binary: libqt5core5a 

Processed: tag as pending

[Debian Bug Tracking System]

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

> tag 889504 pending
Bug #889504 [libqt5core5a] libqt5core5a fails to install: rmdir: failed to 
remove '/etc/xdg/QtProject': No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876250: marked as done (htmldoc does not trap errors inside make)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 00:49:59 +
with message-id 
and subject line Bug#876250: fixed in htmldoc 1.8.27-9
has caused the Debian Bug report #876250,
regarding htmldoc does not trap errors inside make
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.)


-- 
876250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: htmldoc
Version: 1.8.27-8
Severity: serious
Justification: policy 4.6
Tags: upstream
User: helm...@debian.org
Usertags: rebootstrap

The upstream Makefile.in defers to subdirectories in a shell loop. While
it does break the loop on error, it doesn't transfer the exit code. That
can lead to successful misbuilds and is thus prohibited by Debian policy
section 4.6. Policy would suggest prefixing the loop with "set -e", but
that doesn't work here due to the "|| break". Adding "set -e" and
removing "|| break" works though.

Helmut
--- End Message ---
--- Begin Message ---
Source: htmldoc
Source-Version: 1.8.27-9

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated htmldoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 01:28:08 +0100
Source: htmldoc
Binary: htmldoc htmldoc-common
Architecture: source
Version: 1.8.27-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 htmldoc- HTML processor that generates indexed HTML, PS, and PDF
 htmldoc-common - Common arch-independent files for htmldoc
Closes: 876250
Changes:
 htmldoc (1.8.27-9) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to the QA group.
   * Comment out VCS -- 503-compliant.
   * Comment out Homepage -- taken over by a dissertation fraudster.
   * Make errors during build fatal.  Closes: #876250.
   * Drop ancient Replaces/Conflicts.
   * dh 11.
   * R³.
Checksums-Sha1:
 41f61ff7e5bf597c7e9a69c164af4106efcc26d1 1837 htmldoc_1.8.27-9.dsc
 94f1b321f267db041eebd81ba6eb9100dce45d1f 8904 htmldoc_1.8.27-9.debian.tar.xz
 49443a67c4737edea6b5f3f3b47694a2de3298b3 5407 htmldoc_1.8.27-9_source.buildinfo
Checksums-Sha256:
 2496d92ddf2a28437acb12a92d1d230a4e3d14eda14e7382c4e66a2579a67706 1837 
htmldoc_1.8.27-9.dsc
 38b8954cb539d2ab74e904ceecbcd748161f06dc2546e6468de7cd1105bd0a97 8904 
htmldoc_1.8.27-9.debian.tar.xz
 5018c3aa387c30ea7b0ee7b88e181a9ca7ef394de39f1a9e55aafec05cf1fc4f 5407 
htmldoc_1.8.27-9_source.buildinfo
Files:
 b21ae1a309daf2b1537224e68988c958 1837 web optional htmldoc_1.8.27-9.dsc
 952ff99cda6d0f42b2720a3411de2370 8904 web optional 
htmldoc_1.8.27-9.debian.tar.xz
 b6f2739db946659c83c73081be938608 5407 web optional 
htmldoc_1.8.27-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlp2U6YUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH73OxAAzRPudA3R7MmoeUzx6o/Sk7LlEd6f
FHoOi/C2fsmbd+QIyqYfSOS5hgvK9mnzUOcoQx7tVXWmGPC2xAjizL2+V4Sd8hHZ
GRBeyeiTOlQxH4J1j8clyagQVkwgkCd96yv/dPRqneOSgt7h1rCK3OWb0NyGPICS
0xF8VB80oktYDIDNJqx6lNmrVRYx3qVI76i3vZ/WWPL4xJF26TAHKOvaB3rR43X4
xEqdxJRmwk4N0Jtr8KZ91hTBHDOxX+V6WLwSX56Ivkucs9fYo9gbRXYBv22HRalH
tpPMbLBDe6oj6ihHgInYwLhRz8VCWFkVhGzegosb59zHFp1araYbgkqI1pwCQ28s
wYd8oAB/IYtmObeTgDQmZVK+PaVwLhyuhzlnoFythU1+Tj0jE6e7aZxW0rRGBLHO
8uL5TtOrD70gstUwk5zpTf/eQfIRwrrowSY3sDwq6GeZauG9uIIpPux00OnNK36N
FWsiCsROFzdChMld1NsqIAF8QfXDU96/Hm5yqmNDJ6O6/Hg+ciPDXV4CyImwjEOT
tN23k4ODtlAeHBSnZeJ8tBlEA4WlBXo6FdnyHPpN4J3bCQe742am7FjC/rkR+zPZ
HHC1wvgr9JM7cajsPextT2auHEUEjMFER5EBZWSHbyVzRUCnkOp92RPZhKvDeY4Z
gwYb3SJsvBOefbI=
=WS9W
-END PGP SIGNATURE End Message ---

Bug#889510: ruby-rspec: FTBFS with ruby2.5

[Andreas Beckmann]

Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: sid buster experimental
Justification: fails to build from source
Control: found -1 3.6.0c0e0m0s0-1~exp1
Control: block 888531 with -1

Hi,

ruby-rspec in both sid and experimental FTBFS due to test failures
with ruby2.5 as the default.

Please see attached sid buildlog for the details of the failures, it's
hard for me to provide a batter excerpt than

  ERROR: Test "ruby2.5" failed. Exiting.


Andreas


ruby-rspec.build.gz
Description: application/gzip

Processed: ruby-rspec: FTBFS with ruby2.5

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.6.0c0e0m0s0-1~exp1
Bug #889510 [src:ruby-rspec] ruby-rspec: FTBFS with ruby2.5
Marked as found in versions ruby-rspec/3.6.0c0e0m0s0-1~exp1.
> block 888531 with -1
Bug #888531 [release.debian.org] transition: ruby2.5
888531 was not blocked by any bugs.
888531 was not blocking any bugs.
Added blocking bug(s) of 888531: 889510

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

Bug#884998: marked as done (vusb-analyzer: Please don't recommend python-gnome2)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 23:50:17 +
with message-id 
and subject line Bug#884998: fixed in vusb-analyzer 1.1-7
has caused the Debian Bug report #884998,
regarding vusb-analyzer: Please don't recommend python-gnome2
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.)


-- 
884998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vusb-analyzer
Severity: serious
Version: 0.6-1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python
Tags: sid buster

lottanzb recommends python-gnome2 which will be removed from Debian
Testing really soon.

My understanding is that it is an RC bug for a package to recommend a
removed package since it will keep the removed package installed after
upgrade.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: vusb-analyzer
Source-Version: 1.1-7

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated vusb-analyzer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 00:28:00 +0100
Source: vusb-analyzer
Binary: vusb-analyzer
Architecture: source
Version: 1.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 vusb-analyzer - tool for visualizing logs of USB packets
Closes: 884998
Changes:
 vusb-analyzer (1.1-7) unstable; urgency=medium
 .
   * QA upload.
   * Drop Recommends on removed python-gnome2. (Closes: #884998)
   * dh 11.
   * R³.
Checksums-Sha1:
 7dab8f51681a66885a4f27956bb458e93b05a97e 1802 vusb-analyzer_1.1-7.dsc
 a8c9d324ecccf93ff2bd744ba477e312d3d18017 7732 vusb-analyzer_1.1-7.debian.tar.xz
 5780da588df162714016f5e7088d9ffb4bb999d7 6016 
vusb-analyzer_1.1-7_source.buildinfo
Checksums-Sha256:
 f152467812497ed57347c4ac10f08631890217b0cd44c2b89d1f01b354ffa3e0 1802 
vusb-analyzer_1.1-7.dsc
 539997552194c663804762a5abadd66361361258ce927bb02d90a470935a5cb7 7732 
vusb-analyzer_1.1-7.debian.tar.xz
 310eac994cc713a28ffe65516bc8615e85b00080dd47eaf9abe53cd9543c1aa8 6016 
vusb-analyzer_1.1-7_source.buildinfo
Files:
 9a7b7402a2a550aa2b10b6ea33012908 1802 contrib/utils optional 
vusb-analyzer_1.1-7.dsc
 8c2b397a95b2b647bd7094cc8bea539f 7732 contrib/utils optional 
vusb-analyzer_1.1-7.debian.tar.xz
 f584c22a217cdd172425dd0eae2e8318 6016 contrib/utils optional 
vusb-analyzer_1.1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlp2RYwUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH6VBBAA9p+NbDkREE/x3+pENJxSyJ/McXkt
2xniF7Uk9ArbMSxE5FiMdIpsI1XYOWHxLezgV3jK8l356sQJ5guFZUnvHceeD+Pq
NxN0fcH8jx6L5QnWLMBBsj6bQUmBD85tQatRJarv0CTGalgwQpHUntCAyXLGV9lz
kGXh1W1ftOA53aNVkP9Av6DAa6kokqXStK6ExAcKnFnCAII84WOW9KRwAwOrBiAH
2oSpFdsYEnATXN9v3NSD/tgTgPbY7sMexWW3jv4e3GoFd1tQHMqU7XwqyQKaub+j
LUouFU9f7pRKl7b0oi7kFaVgaizVvLBCiZxMV59q//KOIxgNmCh4mQOmj2D6qUZs
nTGMuKvQ3ChgCeVq01o9YgebvEjhGRSTW3W41cFIYqJ8wUgRB7OjW5+VdeO9tDwT
L9yD9pV3K1xdb8PVRvD3xrXwONwjW2e6R1Ubl1DfF+RxsllnMWxDuBpFgsOvgUeT
VHjNVauztZFcC36H+SEyNXOGG2Oc31Dpq60BaONlhLSbGODteod6zVQyCRYPeXT4
sTam6XGstQq5uutPHfylU7++bJ6hTckqgFAjbv2acid//3U+L+tNdpjCI1W097Us
6SsFL43u+yIgaUtNffdPIcJVlX3dbHr8GMpoPYJw5d7N1yeJNsvPx0LmQhDPX809
UIxpBArqSpp36pY=
=NmV6
-END PGP SIGNATURE End Message ---

Bug#870271: marked as done (zookeeper: insecure permissions of /var/lib/zookeeper)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 23:50:46 +
with message-id 
and subject line Bug#870271: fixed in zookeeper 3.4.10-3
has caused the Debian Bug report #870271,
regarding zookeeper: insecure permissions of /var/lib/zookeeper
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.)


-- 
870271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Severity: grave
Tags: security
Justification: user security hole


Hi.

It seems there is a grave permission issue in the zookeeper package,
namely that /var/lib/zookeeper is created world-readable.
Since ZK creates its files word-readable as well, any user on the system
can extract any data stored with ZK, which can easily contain very
sensitive information on the clustered system relying on ZK.


Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.4.10-3

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated zookeeper 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, 03 Feb 2018 14:58:02 -0800
Source: zookeeper
Binary: libzookeeper-java zookeeper zookeeperd libzookeeper-java-doc 
libzookeeper-mt2 libzookeeper-st2 libzookeeper-mt-dev libzookeeper-st-dev 
zookeeper-bin python-zookeeper
Architecture: source all amd64
Version: 3.4.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 libzookeeper-java - Core Java libraries for zookeeper
 libzookeeper-java-doc - API Documentation for zookeeper
 libzookeeper-mt-dev - Development files for multi threaded zookeeper C bindings
 libzookeeper-mt2 - Multi threaded C bindings for zookeeper
 libzookeeper-st-dev - Development files for single threaded zookeeper C 
bindings
 libzookeeper-st2 - Single threaded C bindings for zookeeper
 python-zookeeper - Python bindings for zookeeper
 zookeeper  - High-performance coordination service for distributed application
 zookeeper-bin - Command line utilities for zookeeper
 zookeeperd - Init control scripts for zookeeper
Closes: 869912 870271 878994
Changes:
 zookeeper (3.4.10-3) unstable; urgency=medium
 .
   * The default value of JMXLOCALONLY is now true (Closes: #869912)
   * Drop transitional package libzookeeper2 (Closes: #878994)
   * /var/lib/zookeeper is no longer world-readable (Closes: #870271)
   * Use debhelper 11 and set compat level to 11
   * Bump Standards-Version to 4.1.3
   * Use https for Homepage URL
   * Drop build-dep on dh-systemd in favor of debhelper 10
   * Remove init.d skeleton template boilerplate
   * Remove Upstart config
   * Add ./NOTICE.txt to debian/zookeeper.docs
   * Set build target to Java 8
   * Correct ivy profile during test phase on i386 (See: #860650)
 Note that this does not mean that tests pass on i386 now, only
 that the tests can be run without ivy dying.
   * Disable tests that use the MiniKdc class
   * Rename zooinspector JAR file to zookeeper-zooinspector as per policy
   * Add debian/NEWS
Checksums-Sha1:
 51548611e2b10e80e9867fcfd384ef4ed28f3def 3090 zookeeper_3.4.10-3.dsc
 e6d4536de9f4b1ab9b7706bac2d85c2b62da 44396 zookeeper_3.4.10-3.debian.tar.xz
 e29a73b85030b59879b3dc4f470657cc8bd69f96 340296 
libzookeeper-java-doc_3.4.10-3_all.deb
 15f432cb84d5b18eda9b352487a8f235690c990a 1364680 
libzookeeper-java_3.4.10-3_all.deb
 ca5e3fc3461b3ad897b193e56db3acdb49e090b5 61648 
libzookeeper-mt-dev_3.4.10-3_amd64.deb
 0392644246f12f73dc78fcec45232a2d19b31af8 112164 
libzookeeper-mt2-dbgsym_3.4.10-3_amd64.deb
 eab6f6f4f294e076e3ca7bab4aa270850feb8793 45768 
libzookeeper-mt2_3.4.10-3_amd64.deb
 7ede581cc9271ca7dda2228a5fe7050b69f69539 58828 
libzookeeper-st-dev_3.4.10-3_amd64.deb
 0c764e3eee53d69d2591620165228a08f8c384f2 104988 

Bug#889336: Info received (dnsmasq cannot be started with systemd 237-1)

[Sławomir Gonet]

Attached systemd service (put in /etc/systemd/system/dnsmasq.service)
seems to work.

Keep in mind that it is not 1:1 replacement, it lacking features of
original unit file.

[Unit]
Description=A lightweight DHCP and caching DNS server
After=network.target

[Service]
Type=simple
ExecStartPre=/usr/sbin/dnsmasq --test
ExecStart=/usr/sbin/dnsmasq -k --user=dnsmasq --group=nogroup
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

-- 
sg

Bug#871108: marked as done (munin-c: FTBFS: threads.c:62:30: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 250 [-Werror=format-truncation=])

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 22:20:17 +
with message-id 
and subject line Bug#871108: fixed in munin-c 0.0.11-1
has caused the Debian Bug report #871108,
regarding munin-c: FTBFS: threads.c:62:30: error: '%s' directive output may be 
truncated writing up to 255 bytes into a region of size 250 
[-Werror=format-truncation=]
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.)


-- 
871108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: munin-c
Version: 0.0.9-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"munin-c\" -DPACKAGE_TARNAME=\"munin-c\" 
> -DPACKAGE_VERSION=\"0.0.9\" -DPACKAGE_STRING=\"munin-c\ 0.0.9\" 
> -DPACKAGE_BUGREPORT=\"https://github.com/munin-monitoring/munin-c/issues\; 
> -DPACKAGE_URL=\"https://github.com/munin-monitoring/munin-c\; 
> -DPACKAGE=\"munin-c\" -DVERSION=\"0.0.9\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 
> -DHAVE_WORKING_FORK=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wextra -Werror -pedantic -c -o threads.o 
> threads.c
> threads.c: In function 'threads':
> threads.c:62:30: error: '%s' directive output may be truncated writing up to 
> 255 bytes into a region of size 250 [-Werror=format-truncation=]
>snprintf(buff, 256, "/proc/%s/status", e->d_name);
>   ^~
> In file included from /usr/include/stdio.h:938:0,
>  from threads.c:13:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
> '__builtin___snprintf_chk' output between 14 and 269 bytes into a destination 
> of size 256
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>   ^~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~
> cc1: all warnings being treated as errors
> Makefile:432: recipe for target 'threads.o' failed
> make[2]: *** [threads.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/munin-c_0.0.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: munin-c
Source-Version: 0.0.11-1

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

Debian distribution maintenance software
pp.
Matthias Schmitz  (supplier of updated munin-c 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, 03 Feb 2018 11:47:27 +0100
Source: munin-c
Binary: munin-node-c munin-plugins-c
Architecture: source
Version: 0.0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Schmitz 
Changed-By: Matthias Schmitz 
Description:
 munin-node-c - C rewrite of Munin node
 munin-plugins-c - C rewrite of some Munin plugins
Closes: 783431 845426 856660 871108
Changes:
 munin-c (0.0.11-1) unstable; urgency=medium
 .
   * New upstream version 0.0.11
 Closes: #871108, Closes:  #783431, Closes: #856660, Closes: #845426)
   * Let uscan use Github as upstream does not release tarballs on sf.net 
anymore
   * Bump Debhelper to 11 and Standards-Version: to 4.1.3
   * 

Bug#889504: libqt5core5a fails to install: rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory

[Sven Joachim]

Am 03.02.2018 um 22:35 schrieb Helmut Grohne:

> libqt5core5a fails to install:
> [...]
> # apt-get install libqt5core5a
> dpkg: error processing package libqt5core5a:amd64 (--configure):
>  installed libqt5core5a:amd64 package post-installation script subprocess 
> returned error exit status 1
> Processing triggers for libc-bin (2.26-6) ...
> Errors were encountered while processing:
>  libqt5core5a:amd64
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Since many people are going to hit this, here's a $0.02 tip how to work
around it while the maintainers prepare a fix:

# mkdir -p /etc/xdg/QtProject
# dpkg --configure --pending

Cheers,
   Sven

Bug#889336: dnsmasq cannot be started with systemd 237-1

[Sławomir Gonet]

I am also affected, I see no workaround at this moment (without knowing
about systemd internals).

dnsmasq setup itself is still valid, # dnsmasq -d -C /etc/dnsmasq.conf
starts without issues.

-- 
sg

Bug#884001: linux-image-4.9.0-5-amd64: severe screen flickering and subsequent system freeze on intel broadwell after upgrade to stretch

[Daniel]

Package: src:linux
Version: 4.9.65-3+deb9u2
Followup-For: Bug #884001

Dear Maintainer,

after recently upgrading from jessie to stretch my laptop with intel core
i5-5200U became unusable with kernel 4.9:
a few minutes after booting I would get severe screen flickering with
subsequent complete system freeze requiring a hard reset.
This happened every time, and more quickly in gnome (X or wayland) than xfce
(but eventually also there).
The logs did not show anything, unfortunately.

The problem went away after upgrading to kernel 4.14 from stretch-backports. (I
still get minor flickering where the screen "slides" sideways sometimes after
user switch, but no more crashes.)

I should also mention that I did not experience this bug on jessie where I was
using kernel 4.9 from jessie-backports (with boot parameter
"i915.enable_psr=0") with no problems for many months.

Thanks, Daniel



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

** Model information
sys_vendor: Dell Inc.
product_name: XPS 13 9343
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A13
board_vendor: Dell Inc.
board_name: 0TM99H
board_version: A00

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Dell Broadwell-U Host Bridge -OPI [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell HD Graphics 5500 [1028:0665]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Dell Broadwell-U Audio Controller [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:04.0 Signal processing controller [1180]: Intel Corporation Broadwell-U 
Processor Thermal Subsystem [8086:1603] (rev 09)
Subsystem: Dell Broadwell-U Processor Thermal Subsystem [1028:0665]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Dell Wildcat Point-LP USB xHCI Controller [1028:0665]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Dell Wildcat Point-LP MEI Controller [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: Dell Wildcat Point-LP High Definition Audio Controller 
[1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #1 [8086:9c90] (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #4 [8086:9c96] (rev e3) (prog-if 00 [Normal 

Bug#884680: marked as done (xul-ext-quotecolors: Please depend on thunderbird | icedove)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 21:50:31 +
with message-id 
and subject line Bug#884680: fixed in quotecolors 0.3-5
has caused the Debian Bug report #884680,
regarding xul-ext-quotecolors: Please depend on thunderbird | icedove
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.)


-- 
884680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-quotecolors
Version: 0.3-4
Severity: serious

Hi,
Icedove has been re-rebranded to Thunderbird, but xul-ext-quotecolors
depends on icedove | iceape. Please fix this to depend on thunderbird
(perhaps | icedove) so the extension can be installed again.

Regards,
James
--- End Message ---
--- Begin Message ---
Source: quotecolors
Source-Version: 0.3-5

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

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

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

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated quotecolors package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 22:26:07 +0100
Source: quotecolors
Binary: xul-ext-quotecolors
Architecture: source all
Version: 0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Michael Meskes 
Description:
 xul-ext-quotecolors - Colorize different quoting levels in e-mail messages
Closes: 884680
Changes:
 quotecolors (0.3-5) unstable; urgency=medium
 .
   * Added myself to uploaders
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Switched to debhelper 11.
   * Rebuild to create correct dependency. (Closes: #884680)
Checksums-Sha1:
 5a1b2a35270aa8f3d9c823c5a36424dc6e0c89a3 2107 quotecolors_0.3-5.dsc
 0b6912d7724952edcc492206229320b2d216c0dd 3472 quotecolors_0.3-5.debian.tar.xz
 956c64a3d2294454ddf280e886c98dbeec59d1cd 6720 quotecolors_0.3-5_amd64.buildinfo
 828f98ad9fba39b65d9a07212d2665753a5d55a6 39732 
xul-ext-quotecolors_0.3-5_all.deb
Checksums-Sha256:
 52e672560d1c7680c8d62bfa14d948068a60928e2317db4f68422bde8f59aab5 2107 
quotecolors_0.3-5.dsc
 ca8235ccbe21e48c59b343862e2ab04436c7513da1bd712527e843b1cbeeb73d 3472 
quotecolors_0.3-5.debian.tar.xz
 ee0c53c855fbd2b71354539d42a2dc9013a8eecbc242f4421d11f4c6f03fc722 6720 
quotecolors_0.3-5_amd64.buildinfo
 93d240f027639645208a36a2c8a2af71ed4768f7817fa7af0631e7d874280bb7 39732 
xul-ext-quotecolors_0.3-5_all.deb
Files:
 f8acbb54f26dbf68dde2fe20a0a61cd0 2107 mail optional quotecolors_0.3-5.dsc
 57ced818b0d8f1a94693c5203a00f5fb 3472 mail optional 
quotecolors_0.3-5.debian.tar.xz
 3da9b227d7649c464d6c5f1fcc285192 6720 mail optional 
quotecolors_0.3-5_amd64.buildinfo
 6526b1df1a4a04a69a0349968f20d587 39732 mail optional 
xul-ext-quotecolors_0.3-5_all.deb

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEZ/2RWVGI6sRsEOjtNdhXwLvLOyUFAlp2KboWHG1lc2tlc0Bw
b3N0Z3Jlc3FsLm9yZwAKCRA12FfAu8s7Jbz4D/9x425UGnCFg05JfjwQyRTGzgbP
jZx2wURkB9EZ4jkwgdiTqh5uJGkQIdS6O74afvDL2sS2Nu26T0WPW39zbIkuIcsC
F53T6lZ3YoEN24fmHi4jmj3DCNGNgdZ6CPxbCEXsJ7AoHy/WdjftjUZXIdv2AhIN
OixzxUVQmzj9enXmbDuUpNsq4EYnb+X8MWNdVCvpngPZXqbEMIVTWBVE0N1KKEYR
58I4mmVc/gYzf1Do8zrdhX7T7T/ROwN753HkJLPy/mIUmBrmGCVfqDyo5DbXx2s6
u1vo2eTcsZhbL4FPxh0YRlJrjFsT4K50nikBtIA3DRSdq7XZzLGQOrS07F3kX6i5
jsKBbCc/6/KFxoqPepY9GyuYnC2gWY3Bt9Nd3bX8IrFdjacBwjvfdn1lLkDuO+NI
E5BGbXf9m9bpiVArXBIodZrSWwGf3FRNq+l9nGI4TycPRtqyG6b/r02ONR0qclKc
vFYEVcDTH65tOAuFdG0gGuvzu9+jIVFooB2PqK4DsHPnxO1C/SOBdzsOe0M0xT6a
uQFCoTr2XvBW0OqrmEDiyTu23ll06EaQxn8nmPYDcJPQQ8gnGrCfWzrLmzpfHmGM
oOrH7JLWzc3bw5CE7L86X4ryXwABFThkDGu8z3kEPG7QSDqGi0TQj2XyCFYRvmrE
76BSKtG7KQXqmPTTCg==
=KCMg
-END PGP SIGNATURE End Message ---

Bug#889504: libqt5core5a fails to install: rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory

[Ben Caradoc-Davies]

Upgrade of libqt5core5a (5.9.2+dfsg-7 => 5.9.2+dfsg-8) succeeded for me 
on sid. Prior to upgrade I had /etc/xdg/QtProject (an empty directory).


$ ls -ald /etc/xdg/QtProject
drwxr-xr-x 2 root root 4096 Jan 21 11:50 /etc/xdg/QtProject/

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#889492: marked as done (lyx: FTBFS twice in a row due to leftover lyx-dbg handling)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 21:35:09 +
with message-id 
and subject line Bug#889492: fixed in lyx 2.2.3-4
has caused the Debian Bug report #889492,
regarding lyx: FTBFS twice in a row due to leftover lyx-dbg handling
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.)


-- 
889492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lyx
Version: 2.3.0~rc2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

lyx/experimental fails to build twice in a row, the package in unstable
probably has the same problem.
>From the attached log, from the second build:

[...]
   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/lyx-2.3.0~rc2'
mkdir -p debian/lyx/usr/share/doc
ln -s lyx-common debian/lyx/usr/share/doc/lyx
mkdir -p debian/lyx-dbg/usr/share/doc
ln -s lyx debian/lyx-dbg/usr/share/doc/lyx-dbg
ln: failed to create symbolic link 'debian/lyx-dbg/usr/share/doc/lyx-dbg': File 
exists
debian/rules:62: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1
make[1]: Leaving directory '/build/lyx-2.3.0~rc2'
debian/rules:9: recipe for target 'binary' failed
make: *** [binary] Error 2

This looks like there are leftover commands for creating the
  debian/lyx-dbg/usr/share/doc/lyx-dbg -> lyx
symlink. Since the lyx-dbg package is no longer built, the temporary
debian/lyx-dbg staging directory is not cleaned up between the builds,
and the second build tries to create stuff that already exists there ...


Andreas


lyx_2.3.0~rc2-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lyx
Source-Version: 2.2.3-4

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated lyx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 22:04:02 +0100
Source: lyx
Binary: lyx lyx-common fonts-lyx
Architecture: source
Version: 2.2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Tobias Quathamer 
Description:
 fonts-lyx  - TrueType versions of some TeX fonts used by LyX
 lyx- document processor
 lyx-common - architecture-independent files for LyX
Closes: 889492
Changes:
 lyx (2.2.3-4) unstable; urgency=medium
 .
   * Remove unneeded symlink creation to debug package.
 After the dbgsym migration, there's no longer a lyx-dbg package
 created and the package FTBFS twice in a row due to the leftover
 directory.
 Thanks to Andreas Beckmann  (Closes: #889492)
Checksums-Sha1:
 183eed3618e30f05a522ee7ef14015a3d3ec5ff9 2198 lyx_2.2.3-4.dsc
 d58c254ca095dda545060f489393977814c8feed 42956 lyx_2.2.3-4.debian.tar.xz
 dd706503737f728e6e77b949581288c1b2ac736d 12432 lyx_2.2.3-4_amd64.buildinfo
Checksums-Sha256:
 75e3456ea35a16fa6e57e00508772f233af971fff607c4fec40312d1d790fdd2 2198 
lyx_2.2.3-4.dsc
 12237d86fe7b71aa5afcead59a3daafa6966c9382192c01513242e4680a68932 42956 
lyx_2.2.3-4.debian.tar.xz
 e65ef10847495ec5458a3e2b06c190d1f03c62ff5d0a32f89d2d41d455c0da93 12432 
lyx_2.2.3-4_amd64.buildinfo
Files:
 f872a7e1add086c07f4b35a383f96dd3 2198 editors optional lyx_2.2.3-4.dsc
 fa428e9d09cb0e19090e1a3b9a6ac086 42956 editors optional 
lyx_2.2.3-4.debian.tar.xz
 c42f4db0246cd946f7dedfab05b126fe 12432 editors optional 
lyx_2.2.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlp2JW0ACgkQEwLx8Dbr
6xms/A/9GCgj53othyHDsBT+m+Mc1rK3atB2GtlpFeOwWeW1enihhX8CYwFELNh3
zPlBeFT4fxhAZxew1Itg+Si1iO+ucfp8v05dxKRF/nMIZRf7K+++ujWuwsQQLnpJ
xy0TPuBx1Qg03PDXOg9zPzT6arQiyAO5jE9kL+LeFo9BpfRUvnxqUxpMAlxNx2ba
iEzz3NKF5nG2hoLvxIgj82e+Vz+xvSYQge6RTvhfjLRDpwtb0dXc7bVx8bgjpjbJ
cywrbT9jB7HUQLHAGBgOQatR0q1jzkIyevHrZVL1EMNlpLfJgiviOZSp7nTR8RFf

Bug#889492: marked as done (lyx: FTBFS twice in a row due to leftover lyx-dbg handling)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 21:35:23 +
with message-id 
and subject line Bug#889492: fixed in lyx 2.3.0~rc2-2
has caused the Debian Bug report #889492,
regarding lyx: FTBFS twice in a row due to leftover lyx-dbg handling
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.)


-- 
889492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lyx
Version: 2.3.0~rc2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

lyx/experimental fails to build twice in a row, the package in unstable
probably has the same problem.
>From the attached log, from the second build:

[...]
   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/lyx-2.3.0~rc2'
mkdir -p debian/lyx/usr/share/doc
ln -s lyx-common debian/lyx/usr/share/doc/lyx
mkdir -p debian/lyx-dbg/usr/share/doc
ln -s lyx debian/lyx-dbg/usr/share/doc/lyx-dbg
ln: failed to create symbolic link 'debian/lyx-dbg/usr/share/doc/lyx-dbg': File 
exists
debian/rules:62: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1
make[1]: Leaving directory '/build/lyx-2.3.0~rc2'
debian/rules:9: recipe for target 'binary' failed
make: *** [binary] Error 2

This looks like there are leftover commands for creating the
  debian/lyx-dbg/usr/share/doc/lyx-dbg -> lyx
symlink. Since the lyx-dbg package is no longer built, the temporary
debian/lyx-dbg staging directory is not cleaned up between the builds,
and the second build tries to create stuff that already exists there ...


Andreas


lyx_2.3.0~rc2-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lyx
Source-Version: 2.3.0~rc2-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated lyx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 22:15:41 +0100
Source: lyx
Binary: lyx lyx-common fonts-lyx
Architecture: source
Version: 2.3.0~rc2-2
Distribution: experimental
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Tobias Quathamer 
Description:
 fonts-lyx  - TrueType versions of some TeX fonts used by LyX
 lyx- document processor
 lyx-common - architecture-independent files for LyX
Closes: 889492
Changes:
 lyx (2.3.0~rc2-2) experimental; urgency=medium
 .
   * Remove unneeded symlink creation to debug package.
 After the dbgsym migration, there's no longer a lyx-dbg package
 created and the package FTBFS twice in a row due to the leftover
 directory.
 Thanks to Andreas Beckmann  (Closes: #889492)
Checksums-Sha1:
 d15497abde4e8ab450aa2a55493215e8501ca197 2226 lyx_2.3.0~rc2-2.dsc
 d6c4273db7e5b3da412079e603b88241592f39c1 15745996 lyx_2.3.0~rc2.orig.tar.xz
 2852cc91d15b4a227e1dc1ec5851da59cb722bb2 31444 lyx_2.3.0~rc2-2.debian.tar.xz
 7f78196ffc9c492a189035e93179fe75f54eecc5 12500 lyx_2.3.0~rc2-2_amd64.buildinfo
Checksums-Sha256:
 371eed9dca0161ffaa5a002cfe37120161dc70d33fa7b596e62657367fb2 2226 
lyx_2.3.0~rc2-2.dsc
 4ca46213e2dbf6f038c11ea6cee59248621b130d3c1773a0e48111839e19824d 15745996 
lyx_2.3.0~rc2.orig.tar.xz
 4f47d027ec0023ee6996ad3d83a032d2af2845cf476e1ae3858402e7919e5e2a 31444 
lyx_2.3.0~rc2-2.debian.tar.xz
 6a90ef18ad747502bcc82780c92108b5a6508a07e348a041d6c1f0a8adf8d7eb 12500 
lyx_2.3.0~rc2-2_amd64.buildinfo
Files:
 cfd8430b00e68fbfa3a3cb1d6bf63b21 2226 editors optional lyx_2.3.0~rc2-2.dsc
 4d9efdeb254e3fdc10de64c1cfe3a6b2 15745996 editors optional 
lyx_2.3.0~rc2.orig.tar.xz
 3af5d7a6526bdfff16785d828277f7db 31444 editors optional 
lyx_2.3.0~rc2-2.debian.tar.xz
 69d5213cb0d4a8f329e753dd85cb6f08 12500 editors optional 
lyx_2.3.0~rc2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlp2KEIACgkQEwLx8Dbr

Bug#889504: libqt5core5a fails to install: rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory

[Helmut Grohne]

Package: libqt5core5a
Version: 5.9.2+dfsg-8
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

libqt5core5a fails to install:

# apt-get install libqt5core5a
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libdouble-conversion1 libglib2.0-0 libicu57 libpcre2-16-0
Suggested packages:
  libthai0
Recommended packages:
  libglib2.0-data shared-mime-info xdg-user-dirs qttranslations5-l10n
The following NEW packages will be installed:
  libdouble-conversion1 libglib2.0-0 libicu57 libpcre2-16-0 libqt5core5a
0 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 12.7 MB of archives.
After this operation, 42.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.stw-bonn.de/debian sid/main amd64 libdouble-conversion1 amd64 
2.0.1-4 [33.7 kB]
Get:2 http://ftp.stw-bonn.de/debian sid/main amd64 libglib2.0-0 amd64 2.54.3-2 
[2822 kB]
Get:3 http://ftp.stw-bonn.de/debian sid/main amd64 libicu57 amd64 57.1-8 [7699 
kB]
Get:4 http://ftp.stw-bonn.de/debian sid/main amd64 libpcre2-16-0 amd64 10.22-5 
[174 kB]
Get:5 http://ftp.stw-bonn.de/debian sid/main amd64 libqt5core5a amd64 
5.9.2+dfsg-8 [1930 kB]
Fetched 12.7 MB in 0s (70.6 MB/s)  
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libdouble-conversion1:amd64.
(Reading database ... 10065 files and directories currently installed.)
Preparing to unpack .../libdouble-conversion1_2.0.1-4_amd64.deb ...
Unpacking libdouble-conversion1:amd64 (2.0.1-4) ...
Selecting previously unselected package libglib2.0-0:amd64.
Preparing to unpack .../libglib2.0-0_2.54.3-2_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.54.3-2) ...
Selecting previously unselected package libicu57:amd64.
Preparing to unpack .../libicu57_57.1-8_amd64.deb ...
Unpacking libicu57:amd64 (57.1-8) ...
Selecting previously unselected package libpcre2-16-0:amd64.
Preparing to unpack .../libpcre2-16-0_10.22-5_amd64.deb ...
Unpacking libpcre2-16-0:amd64 (10.22-5) ...
Selecting previously unselected package libqt5core5a:amd64.
Preparing to unpack .../libqt5core5a_5.9.2+dfsg-8_amd64.deb ...
Unpacking libqt5core5a:amd64 (5.9.2+dfsg-8) ...
Setting up libdouble-conversion1:amd64 (2.0.1-4) ...
Setting up libglib2.0-0:amd64 (2.54.3-2) ...
No schema files found: doing nothing.
Setting up libicu57:amd64 (57.1-8) ...
Processing triggers for libc-bin (2.26-6) ...
Setting up libpcre2-16-0:amd64 (10.22-5) ...
Setting up libqt5core5a:amd64 (5.9.2+dfsg-8) ...
rmdir: failed to remove '/etc/xdg/QtProject': No such file or directory
dpkg: error processing package libqt5core5a:amd64 (--configure):
 installed libqt5core5a:amd64 package post-installation script subprocess 
returned error exit status 1
Processing triggers for libc-bin (2.26-6) ...
Errors were encountered while processing:
 libqt5core5a:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
#

Helmut

Processed: Re: Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #887010 [telegram-desktop] telegram-desktop segfaults on debian buster 
(amd64) using Gnome3
Severity set to 'important' from 'grave'

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

Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3

[Коля Гурьев]

Control: severity -1 important

Please send Telegram logs from the ~/.local/share/TelegramDesktop/log.txt
file to debug this crash.

31.01.2018 12:34, Robin Mueller-Bady пишет:
> Setting XDG_CURRENT_DESKTOP to NONE works fine all the time. If it is not 
> set, Telegram
> won't start at all due to a SIGSEV. In both ways completely deterministic :-)

If so and the program works (in any way), the bug should have important
or normal severity because a workaround is found.

Bug#887757: marked as done (heaptrack FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 21:08:02 +
with message-id 
and subject line Bug#887757: fixed in heaptrack 1.0.1~20180129.gita4534d5-1
has caused the Debian Bug report #887757,
regarding heaptrack FTBFS with glibc 2.26
to be marked as done.

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

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


-- 
887757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heaptrack
Version: 1.0.1~20170503.git4da8c45-3
Severity: serious

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

...
/build/1st/heaptrack-1.0.1~20170503.git4da8c45/tests/manual/test.cpp: In 
function 'int main()':
/build/1st/heaptrack-1.0.1~20170503.git4da8c45/tests/manual/test.cpp:85:5: 
error: 'cfree' was not declared in this scope
 cfree(buf);
 ^
--- End Message ---
--- Begin Message ---
Source: heaptrack
Source-Version: 1.0.1~20180129.gita4534d5-1

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated heaptrack 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, 03 Feb 2018 20:36:37 +0100
Source: heaptrack
Binary: heaptrack heaptrack-gui libheaptrack
Architecture: source
Version: 1.0.1~20180129.gita4534d5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 heaptrack  - Heap memory profiler for Linux
 heaptrack-gui - Heap memory profiler for Linux
 libheaptrack - Heap memory profiler for Linux
Closes: 887757
Changes:
 heaptrack (1.0.1~20180129.gita4534d5-1) unstable; urgency=medium
 .
   * [a6dc2c1] New upstream version 0~20180129.gita4534d5. (Closes: #887757)
   * [718fc77] Disable KDE test
   * [2e67083] Ignore quilt dir
   * [29e6221] Apply cme fix dpkg
   * [d2703ab] Remove testsuite-field in d/control
   * [429a120] Update VCS-field (move to salsa)
   * [3c1ec4b] Use compat-level 11
   * [e8b0aa0] Update autopkgtest
   * [810d33c] Add one more autopkgtest
Checksums-Sha1:
 b1ab03f3209c4d9a166a16d9e1c00bc78a21 2530 
heaptrack_1.0.1~20180129.gita4534d5-1.dsc
 5760f4d15af609e0ad782f012bca6551f922c239 843704 
heaptrack_1.0.1~20180129.gita4534d5.orig.tar.xz
 6415ebc6b45cdf422da5bbab3bd18dcca51eb9f6 6908 
heaptrack_1.0.1~20180129.gita4534d5-1.debian.tar.xz
 47227366e9047c31a39d50639c2ca2b280707a51 21335 
heaptrack_1.0.1~20180129.gita4534d5-1_source.buildinfo
Checksums-Sha256:
 6db933b20c2b9a3cd410025baf82bd693318414adf799d4c3dbc26a540171135 2530 
heaptrack_1.0.1~20180129.gita4534d5-1.dsc
 8fb6112eef867ccde1438f30ac91e14e40f9308d579124006dcc7313818d0374 843704 
heaptrack_1.0.1~20180129.gita4534d5.orig.tar.xz
 6b76511fa78d0c49720f143c1dac3b93a45b13f84fa66412eb91dd63edf5c6df 6908 
heaptrack_1.0.1~20180129.gita4534d5-1.debian.tar.xz
 ae1313f157e51cdfd5e56c326a060dbeef7ba7bf6a6bcd5f32d83e74b0f8c70b 21335 
heaptrack_1.0.1~20180129.gita4534d5-1_source.buildinfo
Files:
 006c5aa5617e7db4d4b65ec0d8b71c8d 2530 devel optional 
heaptrack_1.0.1~20180129.gita4534d5-1.dsc
 344bee848c954d20d0f17b37dfa4a8ed 843704 devel optional 
heaptrack_1.0.1~20180129.gita4534d5.orig.tar.xz
 56de0c9c243d52e9e8278521e0f3b646 6908 devel optional 
heaptrack_1.0.1~20180129.gita4534d5-1.debian.tar.xz
 6860d03760722506cfbfcce59b6e0931 21335 devel optional 
heaptrack_1.0.1~20180129.gita4534d5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlp2E9oACgkQ0+Fzg8+n
/wbMbRAAhtE/5sYSKpytpsXUgWk4y52E+GcbkFerkE9cVSjAG3kOgKLSnv0QvJ9W
ynEtGgAgOu+ounJ1xHgRKmunNU+gWgNMHnl4xPiIv5aTbD7EygLkVSSf/Zcmwy7e
8z0uszprQy+P94V12OGhE9PmeOA60x6i0BVQFkI8mvpoCSdsalcP/dhcpxTWhVkK
5I3p0a3AVsjKjLdJ97XAX1D9w26xHFXxybbmzvDzlndcCBw5hfBhespaCcUghxlX
If7uUdEtolijJkrdpHgpHWPbTs4nTPmlnJCPhm1W6YvrhOTar/qMCXz5b7k7WvOl
SQl3ii2TrzmIShpvHzWRru/RgChv5jCVmI2fnmytF7tKALx86S0Xio15218co/F6

Bug#889502: cypari2: FTBFS on several architectures

[Andreas Beckmann]

Source: cypari2
Version: 1.1.3-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

cypari2/experimental FTBFS on several architectures:
https://buildd.debian.org/status/package.php?p=cypari2=experimental

I can reproduce this in pbuilder on i386, but not on amd64 (where it
also built successfully on the buildd).

Excerpt from
https://buildd.debian.org/status/fetch.php?pkg=cypari2=i386=1.1.3-3=1516945955=0

make[2]: Entering directory '/<>/docs'
Running Sphinx v1.6.6
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 6 source files that are out of date
updating environment: 6 added, 0 changed, 0 removed
reading sources... [ 16%] closure
reading sources... [ 33%] convert
reading sources... [ 50%] gen
reading sources... [ 66%] handle_error
reading sources... [ 83%] index
reading sources... [100%] pari_instance

/<>/docs/source/closure.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.closure'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.closure
/<>/docs/source/convert.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.convert'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.convert
/<>/docs/source/gen.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.gen'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.gen
/<>/docs/source/handle_error.rst:1: WARNING: autodoc: failed to 
import module u'cypari2.handle_error'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.handle_error
/<>/docs/source/pari_instance.rst:1: WARNING: autodoc: failed to 
import module u'cypari2.pari_instance'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.pari_instance
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done


Andreas

Processed: Re: Bug#889492: lyx: FTBFS twice in a row due to leftover lyx-dbg handling

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.2.3-2
Bug #889492 [src:lyx] lyx: FTBFS twice in a row due to leftover lyx-dbg handling
Marked as found in versions lyx/2.2.3-2.

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

Bug#889492: lyx: FTBFS twice in a row due to leftover lyx-dbg handling

[Dr. Tobias Quathamer]

control: found -1 2.2.3-2

Am 03.02.2018 um 21:46 schrieb Andreas Beckmann:
> Hi,
> 
> lyx/experimental fails to build twice in a row, the package in unstable
> probably has the same problem.
> [...]>
> This looks like there are leftover commands for creating the
>   debian/lyx-dbg/usr/share/doc/lyx-dbg -> lyx
> symlink. Since the lyx-dbg package is no longer built, the temporary
> debian/lyx-dbg staging directory is not cleaned up between the builds,
> and the second build tries to create stuff that already exists there ...

Hi Andreas,

very good catch, thanks a lot! Yes, this bug has been introduced in
2.2.3-2 already. I'm fixing it now.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#889492: lyx: FTBFS twice in a row due to leftover lyx-dbg handling

[Andreas Beckmann]

Source: lyx
Version: 2.3.0~rc2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

lyx/experimental fails to build twice in a row, the package in unstable
probably has the same problem.
>From the attached log, from the second build:

[...]
   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/lyx-2.3.0~rc2'
mkdir -p debian/lyx/usr/share/doc
ln -s lyx-common debian/lyx/usr/share/doc/lyx
mkdir -p debian/lyx-dbg/usr/share/doc
ln -s lyx debian/lyx-dbg/usr/share/doc/lyx-dbg
ln: failed to create symbolic link 'debian/lyx-dbg/usr/share/doc/lyx-dbg': File 
exists
debian/rules:62: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1
make[1]: Leaving directory '/build/lyx-2.3.0~rc2'
debian/rules:9: recipe for target 'binary' failed
make: *** [binary] Error 2

This looks like there are leftover commands for creating the
  debian/lyx-dbg/usr/share/doc/lyx-dbg -> lyx
symlink. Since the lyx-dbg package is no longer built, the temporary
debian/lyx-dbg staging directory is not cleaned up between the builds,
and the second build tries to create stuff that already exists there ...


Andreas


lyx_2.3.0~rc2-1_twice.log.gz
Description: application/gzip

Bug#881674: marked as done (libmsv-dev: Contains files owned by unprivileged user)

[Debian Bug Tracking System]

Your message dated Sat, 3 Feb 2018 20:22:22 +
with message-id <2018020320.p74pdydguuhi3...@scru.org>
and subject line failed RRR
has caused the Debian Bug report #881674,
regarding libmsv-dev: Contains files owned by unprivileged user
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.)


-- 
881674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmsv-dev
Version: 1.1-4
Severity: serious
Justification: Policy §10.9

libmsv-dev is built with its contents owned by the user doing the build:

https://buildd.debian.org/status/fetch.php?pkg=libmsv=amd64=1.1-4=1510377677=0
> ...
> drwxr-xr-x buildd/buildd 0 2017-11-11 04:20 ./
> drwxr-xr-x buildd/buildd 0 2017-11-11 04:20 ./usr/
> drwxr-xr-x buildd/buildd 0 2017-11-11 04:20 ./usr/include/
> drwxr-xr-x buildd/buildd 0 2017-11-11 04:20 ./usr/include/msv/
> ...

See also
https://lintian.debian.org/maintainer/cl...@debian.org.html#libmsv

debian/rules has:

dpkg-deb --root-owner-group --build debian/$(package) ..

but I think an equivalent dpkg-deb call for debian/$(devpkg) must also
need changing?

I'd recommend using debhelper rather than building the package from
first principles, but if you strongly prefer dpkg-deb for some reason,
please check the results with lintian, debc, debdiff or similar to
make sure the packaging did what you expect.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.1-5--- End Message ---

Bug#889144: stricter PIDfile handling breaks several daemons

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/8085

Hi Sven,

I filed an upstream issue at
https://github.com/systemd/systemd/issues/8085 trying to summarize what
the issue is afaiu from reading this and related bug reports.

If you have further feedback or corrections, please directly follow up
on the upstream bug report.

Sorry for the inconvenience. Unfortunately a git revert is non-trivial,
so this will probably need input from upstream.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#889144: stricter PIDfile handling breaks several daemons

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/systemd/systemd/issues/8085
Bug #889144 [systemd] stricter PIDfile handling breaks several daemons
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/8085'.

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

Bug#888921: marked as done (gcc-7 upgrade adds symbol in pcre3)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 19:07:54 +
with message-id 
and subject line Bug#888921: fixed in pcre3 2:8.39-9
has caused the Debian Bug report #888921,
regarding gcc-7 upgrade adds symbol in pcre3
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.)


-- 
888921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.3.0-1
Severity: serious
Control: affects -1 src:pcre3

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

Successful build in buster:

...
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-8_amd64)
+++ dpkg-gensymbolsy1tQ9U   2018-01-31 07:55:25.993668343 +
@@ -80,6 +80,6 @@
  (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
-#MISSING: 2:8.39-2# (c++|optional=STL)"std::vector::_M_insert_aux(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 7.7
- (c++|optional=STL)"void std::vector::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
+#MISSING: 2:8.39-8# (c++|optional=STL)"std::vector::_M_insert_aux(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 7.7
+#MISSING: 2:8.39-8# (c++|optional=STL)"void std::vector::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  (c++|optional=STL)"void std::vector::_M_realloc_insert(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4



buster with gcc-7 upgraded 7.2.0-19 -> 7.3.0-1:

...
dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 5 in use)
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-8_amd64)
+++ dpkg-gensymbolsMippQJ   2018-01-30 11:32:26.692762516 -1200
@@ -1,4 +1,5 @@
 libpcrecpp.so.0 libpcrecpp0v5 #MINVER#
+ 
_ZNSt6vectorIN7pcrecpp11StringPieceESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 2:8.39-8
  (c++)"operator<<(std::basic_ostream&, 
pcrecpp::StringPiece const&)@Base" 8.38
  (c++)"pcrecpp::Arg::parse_char(char const*, int, void*)@Base" 7.7
  (c++)"pcrecpp::Arg::parse_double(char const*, int, void*)@Base" 7.7
@@ -80,6 +81,6 @@
  (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
-#MISSING: 2:8.39-2# (c++|optional=STL)"std::vector::_M_insert_aux(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 7.7
- (c++|optional=STL)"void std::vector::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
+#MISSING: 2:8.39-8# (c++|optional=STL)"std::vector::_M_insert_aux(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 7.7
+#MISSING: 2:8.39-8# (c++|optional=STL)"void std::vector::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  (c++|optional=STL)"void std::vector::_M_realloc_insert(__gnu_cxx::__normal_iterator >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
dh_makeshlibs: failing due to earlier errors
debian/rules:91: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: pcre3
Source-Version: 

Processed: severity of 889189 is normal

[Debian Bug Tracking System]

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

> severity 889189 normal
Bug #889189 [inventor-doc] inventor-doc is empty
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#889471: libcairo-perl: FTBFS: t/CairoSurface.t failure

[Niko Tyni]

On Sat, Feb 03, 2018 at 07:19:24PM +0200, Niko Tyni wrote:
> Package: libcairo-perl
> Version: 1.106-2
> Severity: serious
> User: debian-p...@lists.debian.org
> Usertags: autopkgtest
> 
> As noticed by ci.debian.net, the test suite of this package
> recently started failing.
> 
>   Test Summary Report
>   ---
>   t/CairoSurface.t (Wstat: 139 Tests: 41 Failed: 0)
> Non-zero wait status: 139
> Parse errors: Bad plan.  You planned 88 tests but ran 41.
>   Files=9, Tests=256,  0 wallclock secs ( 0.08 usr  0.00 sys +  0.58 cusr  
> 0.05 csys =  0.71 CPU)
>   Result: FAIL
>  
> Timing suggests src:cairo (1.15.8-3 -> 1.15.10-1) as the probable cause
> for this regression.

Confirmed by downgrading libcairo2; that makes the test suite pass again.
Copying the cairo maintainers FYI.

With libcairo2 1.15.10-1, t/CairoSurface.t the libcairo-perl test suite
segfaults:

  ok 36 - An object of class 'Cairo::ImageSurface' isa 'Cairo::ImageSurface'
  ok 37 - An object of class 'Cairo::ImageSurface' isa 'Cairo::Surface'
  ok 38 - An object of class 'Cairo::ImageSurface' isa 'Cairo::ImageSurface'
  ok 39 - An object of class 'Cairo::ImageSurface' isa 'Cairo::Surface'
  ok 40
  ok 41
  Segmentation fault
 
Backtrace with -O0:

  Core was generated by `perl -Iblib/lib -Iblib/arch t/CairoSurface.t'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  png_get_IHDR (png_ptr=0x55bf0389cdd0, info_ptr=0x55bf035c6480, 
width=width@entry=0x7ffcbf7e50c0, 
  height=height@entry=0x55bf0328eb01, bit_depth=bit_depth@entry=0x8, 
  color_type=color_type@entry=0x, 
interlace_type=0x7ffcbf7e4fb0, compression_type=0x0, 
  filter_type=0x0) at pngget.c:841
  841   pngget.c: No such file or directory.
  (gdb) bt
  #0  png_get_IHDR (png_ptr=0x55bf0389cdd0, info_ptr=0x55bf035c6480, 
width=width@entry=0x7ffcbf7e50c0, 
  height=height@entry=0x55bf0328eb01, bit_depth=bit_depth@entry=0x8, 
  color_type=color_type@entry=0x, 
interlace_type=0x7ffcbf7e4fb0, compression_type=0x0, 
  filter_type=0x0) at pngget.c:841
  #1  0x7f1876db570f in read_png 
(png_closure=png_closure@entry=0x7ffcbf7e5020)
  at ../../../../src/cairo-png.c:595
  #2  0x7f1876db5e65 in cairo_image_surface_create_from_png_stream 
(read_func=, 
  closure=) at ../../../../src/cairo-png.c:837
  #3  0x7f1877050809 in XS_Cairo__ImageSurface_create_from_png_stream 
(my_perl=0x55bf03289260, 
  cv=0x55bf037f8a28) at CairoSurface.xs:494
  #4  0x55bf01174121 in Perl_pp_entersub (my_perl=0x55bf03289260) at 
pp_hot.c:4231
  #5  0x55bf0116bf46 in Perl_runops_standard (my_perl=0x55bf03289260) at 
run.c:41
  #6  0x55bf010ed08f in S_run_body (oldscope=, 
my_perl=) at perl.c:2519
  #7  perl_run (my_perl=0x55bf03289260) at perl.c:2447
  #8  0x55bf010c43a2 in main (argc=, argv=, 
env=)
  at perlmain.c:123
 
-- 
Niko Tyni   nt...@debian.org

Bug#887506: marked as done (notification-daemon: The notification-daemon binary moved to a different location)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 17:49:51 +
with message-id 
and subject line Bug#887506: fixed in notification-daemon 3.20.0-3
has caused the Debian Bug report #887506,
regarding notification-daemon: The notification-daemon binary moved to a 
different location
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.)


-- 
887506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: notification-daemon
Version: 3.20.0-2
Severity: serious
Control: affects -1 src:python-notify2

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

...
rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-notify2-0.3'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
PYTHONS="2.7 3.6" dbus-run-session -- xvfb-run -a debian/runtests.sh
debian/runtests.sh: 5: debian/runtests.sh: 
/usr/lib/notification-daemon/notification-daemon: not found
test_notify2.py:11: PyGIWarning: GdkPixbuf was imported without specifying a 
version first. Use gi.require_version('GdkPixbuf', '2.0') before import to 
ensure that the right version gets loaded.
  from gi.repository import GdkPixbuf
E
==
ERROR: test_get_server_caps (__main__.ModuleTests)
--
Traceback (most recent call last):
  File "test_notify2.py", line 17, in setUp
notify2.init("notify2 test suite")
  File "/build/1st/python-notify2-0.3/notify2.py", line 96, in init
'/org/freedesktop/Notifications')
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Notifications was not provided by any .service files
...


This is caused by the following unintentional
change in notification-daemon 3.20.0-2:
-/usr/lib/notification-daemon/notification-daemon
+/usr/lib/x86_64-linux-gnu/notification-daemon
--- End Message ---
--- Begin Message ---
Source: notification-daemon
Source-Version: 3.20.0-3

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

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

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated notification-daemon 
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, 03 Feb 2018 20:23:14 +0300
Source: notification-daemon
Binary: notification-daemon
Architecture: source
Version: 3.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Dmitry Shachnev 
Description:
 notification-daemon - daemon for displaying passive pop-up notifications
Closes: 887506
Changes:
 notification-daemon (3.20.0-3) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * Update Vcs fields for migration to https://salsa.debian.org/
 .
   [ Dmitry Shachnev ]
   * Fix location of notification-daemon binary (closes: #887506).
   * Bump Standards-Version to 4.1.3, no 

Processed: Add affects

[Debian Bug Tracking System]

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

> affects 889144 dnsmasq munin-node ulogd2
Bug #889144 [systemd] stricter PIDfile handling breaks several daemons
Added indication that 889144 affects dnsmasq, munin-node, and ulogd2
> thanks
Stopping processing here.

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

Bug#889471: libcairo-perl: FTBFS: t/CairoSurface.t failure

[Niko Tyni]

Package: libcairo-perl
Version: 1.106-2
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net, the test suite of this package
recently started failing.

  Test Summary Report
  ---
  t/CairoSurface.t (Wstat: 139 Tests: 41 Failed: 0)
Non-zero wait status: 139
Parse errors: Bad plan.  You planned 88 tests but ran 41.
  Files=9, Tests=256,  0 wallclock secs ( 0.08 usr  0.00 sys +  0.58 cusr  0.05 
csys =  0.71 CPU)
  Result: FAIL
 
Timing suggests src:cairo (1.15.8-3 -> 1.15.10-1) as the probable cause
for this regression.
-- 
Niko Tyni   nt...@debian.org

Bug#887506: Bug #887506 in notification-daemon marked as pending

[mitya57]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/notification-daemon/commit/73f70ef79876040d1aa603510d2d043689009529


Fix location of notification-daemon binary.

Closes: #887506.



(this message was generated automatically)
-- 
Greetings

Processed: cloning 860747, reassign -1 to gem2deb, tagging -1 ...

[Debian Bug Tracking System]

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

> clone 860747 -1
Bug #860747 [ruby-all-dev] ruby-all-dev: include upper bound on generated ruby 
dependencies
Bug 860747 cloned as bug 889470
> reassign -1 gem2deb
Bug #889470 [ruby-all-dev] ruby-all-dev: include upper bound on generated ruby 
dependencies
Bug reassigned from package 'ruby-all-dev' to 'gem2deb'.
Ignoring request to alter found versions of bug #889470 to the same values 
previously set
Ignoring request to alter fixed versions of bug #889470 to the same values 
previously set
> tags -1 + jessie-ignore stretch-ignore
Bug #889470 [gem2deb] ruby-all-dev: include upper bound on generated ruby 
dependencies
Ignoring request to alter tags of bug #889470 to the same tags previously set
> retitle -1 gem2deb: include upper bound on generated ruby dependencies
Bug #889470 [gem2deb] ruby-all-dev: include upper bound on generated ruby 
dependencies
Changed Bug title to 'gem2deb: include upper bound on generated ruby 
dependencies' from 'ruby-all-dev: include upper bound on generated ruby 
dependencies'.
> thanks
Stopping processing here.

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

Processed: Bug #887506 in notification-daemon marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #887506 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Added tag(s) pending.

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

Bug#889450: marked as done (src:django-anymail: Security issue with timing attack on WEBHOOK_AUTHORIZATION)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 17:04:48 +
with message-id 
and subject line Bug#889450: fixed in django-anymail 1.3-1
has caused the Debian Bug report #889450,
regarding src:django-anymail: Security issue with timing attack on 
WEBHOOK_AUTHORIZATION
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.)


-- 
889450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:django-anymail
Version: 0.8-2
Severity: serious
Tags: security upstream
Justification: security

This affects 0.8-2 in stable and 1.2 in unstable:

https://github.com/anymail/django-anymail/commit/c07998304b4a31df4c61deddcb03d3607a04691b

Security: prevent timing attack on WEBHOOK_AUTHORIZATION secret

Anymail's webhook validation was vulnerable to a timing attack.
An attacker could have used this to recover your WEBHOOK_AUTHORIZATION
shared secret, potentially allowing them to post fabricated or malicious
email tracking events to your app.

There have not been any reports of attempted exploit in the wild. (The
vulnerability was discovered through code review.) Attempts would be
visible in http logs as a very large number of 400 responses on
Anymail's webhook urls, or in Python error monitoring as a very large
number of AnymailWebhookValidationFailure exceptions.

If you are using Anymail's webhooks, you should upgrade to this release.
In addition, you may want to rotate to a new WEBHOOK_AUTHORIZATION
secret 
([docs](http://anymail.readthedocs.io/en/stable/tips/securing_webhooks/#use-a-shared-authorization-secret)),
particularly if your logs indicate attempted exploit.
--- End Message ---
--- Begin Message ---
Source: django-anymail
Source-Version: 1.3-1

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated django-anymail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 11:23:43 -0500
Source: django-anymail
Binary: python-django-anymail python3-django-anymail
Architecture: source all
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Description:
 python-django-anymail - Django email backend for multiple ESPs (Python 2)
 python3-django-anymail - Django email backend for multiple ESPs (Python 3)
Closes: 889450
Changes:
 django-anymail (1.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #889450)
 - Includes security fix for timing attack on WEBHOOK_AUTHORIZATION secret
   (no CVE assigned) as described in
   https://github.com/anymail/django-anymail/releases/tag/v1.2.1
   * Update debian/watch and debian/copyright to use secure URIs
Checksums-Sha1:
 76bca39bc107637152b322760be833f637b6af88 2182 django-anymail_1.3-1.dsc
 53f8410e7a3d49d41d3b7e06fd81971856037da8 56653 django-anymail_1.3.orig.tar.gz
 4b66f150af5589c74db99c115835bbf8eed459e8 3304 
django-anymail_1.3-1.debian.tar.xz
 9871e2e92e6f1174bc0c9eaa2ef179777cbb5d7d 5974 
django-anymail_1.3-1_amd64.buildinfo
 d6b1468af29edb14a578b207af1492ff90846dbe 53764 
python-django-anymail_1.3-1_all.deb
 cae0a4d73c3a632ccc3b68061f305eea541102e1 53848 
python3-django-anymail_1.3-1_all.deb
Checksums-Sha256:
 04d2aa883c7733e9b999e018d1cdff619c361b11cd25abc3d191c12dd3bb50f0 2182 
django-anymail_1.3-1.dsc
 6868f65ea15ea958591aecf222ddc3cf37970ca5441a035ddac285168720ed52 56653 
django-anymail_1.3.orig.tar.gz
 128bb179440d1537700a4b8d4617fc3c35f749bc311b89cbf0f0ccd5d5389669 3304 
django-anymail_1.3-1.debian.tar.xz
 1ce4b73781ac91f33c6ccbb9e4a8cb46c47cb9ee3efbbc4149a80ee19acae947 5974 
django-anymail_1.3-1_amd64.buildinfo
 5d3a9d11de9f0121efb6e0f1f46e9c0edb7eb12aa8ce9b23b3142abdc1b325f3 53764 
python-django-anymail_1.3-1_all.deb
 2bc621df179d371166c5fadad8fdb076662f9d6409a529d7db373031ca2e4e23 53848 

Bug#889183: marked as done (pyfai FTBFS: RuntimeError: Fail to generate 'check_calib' man documentation)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 17:05:43 +
with message-id 
and subject line Bug#889183: fixed in pyfai 0.15.0+dfsg1-1
has caused the Debian Bug report #889183,
regarding pyfai FTBFS: RuntimeError: Fail to generate 'check_calib' man 
documentation
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.)


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

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

...
I: pybuild base:184: 
PYTHONPATH=/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build 
xvfb-run -a --server-args="-screen 0 1024x768x24" python3.6 setup.py build_man
INFO:root:Generating grammar tables from /usr/lib/python3.6/lib2to3/Grammar.txt
INFO:root:Generating grammar tables from 
/usr/lib/python3.6/lib2to3/PatternGrammar.txt
INFO:pyFAI.setup:Use setuptools
running build_man
INFO:pyFAI.setup:Build man for entry-point target 'check_calib'
help2man: can't get `--help' info from /tmp/check_calib_59xexrun
Try `--no-discard-stderr' if option outputs to stderr
INFO:pyFAI.setup:b'Traceback (most recent call last):\n  File 
"/tmp/check_calib_59xexrun", line 2, in \nimport 
pyFAI.app.check_calib as app\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/__init__.py",
 line 56, in \nfrom .detectors import Detector\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/detectors.py",
 line 51, in \nfrom . import io\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/io.py", 
line 67, in \nfrom .utils import StringTypes, 
fully_qualified_name\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/utils/__init__.py",
 line 54, in \nfrom ..third_party import six\nModuleNotFoundError: 
No module named \'pyFAI.third_party\'\n'
INFO:pyFAI.setup:b'Traceback (most recent call last):\n  File 
"/tmp/check_calib_59xexrun", line 2, in \nimport 
pyFAI.app.check_calib as app\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/__init__.py",
 line 56, in \nfrom .detectors import Detector\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/detectors.py",
 line 51, in \nfrom . import io\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/io.py", 
line 67, in \nfrom .utils import StringTypes, 
fully_qualified_name\n  File 
"/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build/pyFAI/utils/__init__.py",
 line 54, in \nfrom ..third_party import six\nModuleNotFoundError: 
No module named \'pyFAI.third_party\'\n'
Traceback (most recent call last):
  File "setup.py", line 868, in 
setup_package()
  File "setup.py", line 865, in setup_package
setup(**setup_kwargs)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 129, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
  File "setup.py", line 248, in run
raise RuntimeError("Fail to generate '%s' man documentation" % target_name)
RuntimeError: Fail to generate 'check_calib' man documentation
E: pybuild pybuild:283: build: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/pyfai-0.15.0+dfsg/.pybuild/pythonX.Y_3.6/build 
xvfb-run -a --server-args="-screen 0 1024x768x24" python3.6 setup.py build_man
dh_auto_build: pybuild --build -i python{version} -p 3.6 returned exit code 13
debian/rules:20: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 25
--- End Message ---
--- Begin Message ---
Source: pyfai
Source-Version: 0.15.0+dfsg1-1

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pyfai 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 

Bug#889450: src:django-anymail: Security issue with timing attack on WEBHOOK_AUTHORIZATION

[Scott Kitterman]

On Sat, 03 Feb 2018 11:34:56 -0500 Scott Kitterman  
wrote:
> Package: src:django-anymail
> Version: 0.8-2
> Severity: serious
> Tags: security upstream
> Justification: security
> 
> This affects 0.8-2 in stable and 1.2 in unstable:
> 
> https://github.com/anymail/django-anymail/commit/c07998304b4a31df4c61deddcb03d3607a04691b

I've checked and the commit should apply directly to 0.8.

Scott K

Processed: Bug#889450 marked as pending

[Debian Bug Tracking System]

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

> tag 889450 pending
Bug #889450 [src:django-anymail] src:django-anymail: Security issue with timing 
attack on WEBHOOK_AUTHORIZATION
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#889450: marked as pending

[Scott Kitterman]

tag 889450 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/django-anymail.git/commit/?id=a31e71b

---
commit a31e71b74b775b60c7c89a408457c18231c5c193
Author: Scott Kitterman 
Date:   Sat Feb 3 11:43:48 2018 -0500

Add bug number to changelog

diff --git a/debian/changelog b/debian/changelog
index ef01178..394c0dc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 django-anymail (1.3-1) unstable; urgency=medium
 
-  * New upstream release
+  * New upstream release (Closes: #889450)
 - Includes security fix for timing attack on WEBHOOK_AUTHORIZATION secret
   (no CVE assigned) as described in
   https://github.com/anymail/django-anymail/releases/tag/v1.2.1

Bug#889026: marked as done (ruby-shadow: FTBFS with ruby2.5: too many arguments to function 'rb_struct_ptr' / subscripted value is neither array nor pointer nor vector)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 16:38:37 +
with message-id 
and subject line Bug#889026: fixed in ruby-shadow 2.5.0-1
has caused the Debian Bug report #889026,
regarding ruby-shadow: FTBFS with ruby2.5: too many arguments to function 
'rb_struct_ptr' / subscripted value is neither array nor pointer nor vector
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.)


-- 
889026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-shadow
Severity: serious
Justification: Fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.5

I am filing this at severity serious as I am about to enable building for
ruby2.5 in unstable.

┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/<> debian/ruby-shadow
"make clean"
make[1]: Entering directory '/<>'
make[1]: Leaving directory '/<>'
"make clean"
make[1]: Entering directory '/<>'
make[1]: Leaving directory '/<>'
current directory: /<>
/usr/bin/ruby2.5 -r ./siteconf20180131-27707-1rma5ui.rb extconf.rb
checking for getspent() in -lshadow... no
checking for getspent()... yes
checking for fgetspent()... yes
checking for setspent()... yes
checking for endspent()... yes
checking for lckpwdf()... yes
checking for ulckpwdf()... yes
checking for sgetspent()... yes
checking for ruby/io.h... yes
creating Makefile
current directory: /<>
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/<>'
rm -f 
rm -f shadow.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/<>'
current directory: /<>
make V=1 "DESTDIR="
make[1]: Entering directory '/<>'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -Ishadow 
-DHAVE_GETSPENT -DHAVE_FGETSPENT -DHAVE_SETSPENT -DHAVE_ENDSPENT -DHAVE_LCKPWDF 
-DHAVE_ULCKPWDF -DHAVE_SGETSPENT -DHAVE_RUBY_IO_H -Wdate-time 
-D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -DRUBY19  -o 
shadow.o -c shadow/shadow.c
shadow/shadow.c: In function 'rb_shadow_putspent':
shadow/shadow.c:149:5: warning: 'rb_struct_ptr' is deprecated 
[-Wdeprecated-declarations]
 val[i] = RSTRUCT_PTR( entry )[i]; //val[i] = RSTRUCT(entry)->ptr[i];
 ^~~
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from shadow/shadow.c:11:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
/usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h:129:52: note: in 
definition of macro 'NORETURN'
 #define NORETURN(x) __attribute__ ((__noreturn__)) x
^
/usr/include/ruby-2.5.0/ruby/backward.h:39:14: note: in expansion of macro 
'ERRORFUNC'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^
/usr/include/ruby-2.5.0/ruby/backward.h:39:58: note: in expansion of macro 
'DEPRECATED'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^~
/usr/include/ruby-2.5.0/ruby/backward.h:47:1: note: in expansion of macro 
'DECLARE_DEPRECATED_INTERNAL_FEATURE'
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
In file included from /usr/include/ruby-2.5.0/ruby.h:33:0,
 from shadow/shadow.c:11:
/usr/include/ruby-2.5.0/ruby/ruby.h:1189:33: error: too many arguments to 
function 'rb_struct_ptr'
 #define RSTRUCT_PTR(st) rb_struct_ptr(st)
 ^
shadow/shadow.c:149:14: note: in expansion of macro 'RSTRUCT_PTR'
 val[i] = RSTRUCT_PTR( entry )[i]; //val[i] = RSTRUCT(entry)->ptr[i];
  ^~~
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from shadow/shadow.c:11:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^

Bug#889450: src:django-anymail: Security issue with timing attack on WEBHOOK_AUTHORIZATION

[Scott Kitterman]

Package: src:django-anymail
Version: 0.8-2
Severity: serious
Tags: security upstream
Justification: security

This affects 0.8-2 in stable and 1.2 in unstable:

https://github.com/anymail/django-anymail/commit/c07998304b4a31df4c61deddcb03d3607a04691b

Security: prevent timing attack on WEBHOOK_AUTHORIZATION secret

Anymail's webhook validation was vulnerable to a timing attack.
An attacker could have used this to recover your WEBHOOK_AUTHORIZATION
shared secret, potentially allowing them to post fabricated or malicious
email tracking events to your app.

There have not been any reports of attempted exploit in the wild. (The
vulnerability was discovered through code review.) Attempts would be
visible in http logs as a very large number of 400 responses on
Anymail's webhook urls, or in Python error monitoring as a very large
number of AnymailWebhookValidationFailure exceptions.

If you are using Anymail's webhooks, you should upgrade to this release.
In addition, you may want to rotate to a new WEBHOOK_AUTHORIZATION
secret 
([docs](http://anymail.readthedocs.io/en/stable/tips/securing_webhooks/#use-a-shared-authorization-secret)),
particularly if your logs indicate attempted exploit.

Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

[Salvatore Bonaccorso]

Control: retitle -1 bind9: assertion failure in validator.c:1858

Hi

On Sat, Feb 03, 2018 at 11:12:30AM +0100, Vladislav Kurz wrote:
> This is a followup to archived bug #860225.
> 
> Although
> https://security-tracker.debian.org/tracker/CVE-2017-3139 states that
> debian is not affected by CVE-2017-3139, I observed this behavior on
> debian wheezy:
> 
> Feb  3 08:38:07 server named[16906]: validator.c:1858: INSIST(rdataset->type 
> == ((dns_rdatatype_t)dns_rdatatype_dnskey)) failed, back trace
> Feb  3 08:38:07 server named[16906]: #0 0x7f9b66798e19 in ??
> Feb  3 08:38:07 server named[16906]: #1 0x7f9b650d5f3a in ??
> Feb  3 08:38:07 server named[16906]: #2 0x7f9b66094e57 in ??
> Feb  3 08:38:07 server named[16906]: #3 0x7f9b6609b599 in ??
> Feb  3 08:38:07 server named[16906]: #4 0x7f9b650f4dfd in ??
> Feb  3 08:38:07 server named[16906]: #5 0x7f9b64aa8b50 in ??
> Feb  3 08:38:07 server named[16906]: #6 0x7f9b64492fbd in ??
> Feb  3 08:38:07 server named[16906]: exiting (due to assertion failure)
> 
> Ondrej Zary reported this on Sat, 02 Sep 2017 in bug #860225 but it
> was closed and archived without answer. May I ask why?

The bug was about CVE-2017-3137, it's never a good idea to mix up
things ;-). Anyway thanks that you took action and filled a new bug
for this issue you are experiencing.

JTR, since Red Hat does not provide much details on the CVE-2017-3139
we cannot say Debian is affected as well by this very same CVE. Since
it's not clear, what CVE-2017-3139 is in detail, I have removed the
CVE in the subject of this bug.

What seem clear is that apparently a fix in Debian wheezy's bind9
version causes the regression you notices. Thus I suggest the LTS team
to try to find the defective patch introducing the issue and then
issue just a regression update (without referencing CVE-2017-3139. If
its on the other hand clear that Debian wheezy used the very same
patch for a previous issue, and CVE-2017-3139 applies as well for
Debian wheezy, then obviously it's fine to use the CVE).

Regards,
Salvatore

Processed: Re: Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 bind9: assertion failure in validator.c:1858
Bug #889285 [bind9] bind9: CVE-2017-3139 affects debian too: assertion failure 
in validator.c:1858
Changed Bug title to 'bind9: assertion failure in validator.c:1858' from 
'bind9: CVE-2017-3139 affects debian too: assertion failure in 
validator.c:1858'.

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

Processed: block gdbm by apr-util failure

[Debian Bug Tracking System]

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

> block 888751 by 889170
Bug #888751 [release.debian.org] transition: gdbm
888751 was blocked by: 888754 888753 888752
888751 was not blocking any bugs.
Added blocking bug(s) of 888751: 889170
> thanks
Stopping processing here.

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

Bug#889025: marked as done (ruby-odbc: FTBFS with ruby2.5: invalid operands to binary / (have 'char *' and 'char *'))

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 15:35:14 +
with message-id 
and subject line Bug#889025: fixed in ruby-odbc 0.8-1
has caused the Debian Bug report #889025,
regarding ruby-odbc: FTBFS with ruby2.5: invalid operands to binary / (have 
'char *' and 'char *')
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.)


-- 
889025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-odbc
Severity: serious
Justification: Fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.5

I am filing this at severity serious as I am about to enable building for
ruby2.5 in unstable.

┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/<> debian/ruby-odbc
"make clean"
make[2]: Entering directory '/<>/ext'
make[2]: Leaving directory '/<>/ext'
"make clean"
make[2]: Entering directory '/<>/ext'
make[2]: Leaving directory '/<>/ext'
current directory: /<>/ext
/usr/bin/ruby2.5 -r ./siteconf20180131-26647-1wcu0cw.rb extconf.rb
checking for version.h... no
checking for sql.h... yes
checking for sqlext.h... yes
checking for SQLTCHAR in sqltypes.h... yes
checking for SQLLEN in sqltypes.h... yes
checking for SQLULEN in sqltypes.h... yes
checking for odbcinst.h... yes
checking for dlopen() in dlfcn.h... yes
checking for dlopen() in -ldl... yes
checking for SQLBIGINT in sqltypes.h with -DHAVE_LONG_LONG... yes
creating Makefile
current directory: /<>/ext
make V=1 "DESTDIR=" clean
make[2]: Entering directory '/<>/ext'
rm -f
rm -f odbc.so  *.o  *.bak mkmf.log .*.time
make[2]: Leaving directory '/<>/ext'
current directory: /<>/ext
make V=1 "DESTDIR="
make[2]: Entering directory '/<>/ext'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-DHAVE_SQL_H -DHAVE_SQLEXT_H -DHAVE_TYPE_SQLTCHAR -DHAVE_TYPE_SQLLEN 
-DHAVE_TYPE_SQLULEN -DHAVE_ODBCINST_H -DHAVE_DLOPEN -DHAVE_TYPE_SQLBIGINT 
-Wdate-time -D_FORTIFY_SOURCE=2   -DHAVE_SQLCONFIGDATASOURCE 
-DHAVE_SQLINSTALLERERROR -DUSE_DLOPEN_FOR_ODBC_LIBS -DHAVE_LONG_LONG -fPIC -g 
-O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o init.o -c 
init.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-DHAVE_SQL_H -DHAVE_SQLEXT_H -DHAVE_TYPE_SQLTCHAR -DHAVE_TYPE_SQLLEN 
-DHAVE_TYPE_SQLULEN -DHAVE_ODBCINST_H -DHAVE_DLOPEN -DHAVE_TYPE_SQLBIGINT 
-Wdate-time -D_FORTIFY_SOURCE=2   -DHAVE_SQLCONFIGDATASOURCE 
-DHAVE_SQLINSTALLERERROR -DUSE_DLOPEN_FOR_ODBC_LIBS -DHAVE_LONG_LONG -fPIC -g 
-O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o odbc.o -c 
odbc.c
odbc.c: In function 'start_gc':
odbc.c:913:5: warning: initialization makes integer from pointer without a cast 
[-Wint-conversion]
 rb_funcall(rb_mGC, IDstart, 0, NULL);
 ^~
odbc.c:913:5: note: (near initialization for 'rb_funcall_args[0]')
odbc.c: In function 'conf_dsn':
odbc.c:1602:6: warning: initialization makes integer from pointer without a 
cast [-Wint-conversion]
  a = rb_funcall(attr, IDkeys, 0, NULL);
  ^~
odbc.c:1602:6: note: (near initialization for 'rb_funcall_args[0]')
odbc.c: In function 'dbc_drvconnect':
odbc.c:2107:6: warning: initialization makes integer from pointer without a 
cast [-Wint-conversion]
  a = rb_funcall(rb_iv_get(drv, "@attrs"), IDkeys, 0, NULL);
  ^~
odbc.c:2107:6: note: (near initialization for 'rb_funcall_args[0]')
In file included from /usr/include/ruby-2.5.0/ruby.h:33:0,
 from odbc.c:21:
odbc.c: In function 'do_option':
odbc.c:4301:48: warning: pointer/integer type mismatch in conditional expression
 rb_scan_args(argc, argv, (op == -1) ? "11" : "01", , );
^
/usr/include/ruby-2.5.0/ruby/ruby.h:2190:52: note: in definition of macro 
'rb_scan_args_isdigit'
 # define rb_scan_args_isdigit(c) ((unsigned char)((c)-'0')<10)
^
/usr/include/ruby-2.5.0/ruby/ruby.h:2228:14: note: in expansion of macro 
'rb_scan_args_count'
 ((varc)/(rb_scan_args_count(fmt, varc)))
  

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

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 15:16:50 +
with message-id 
and subject line Bug#866433: fixed in impressive 0.11.2-1.1
has caused the Debian Bug report #866433,
regarding impressive: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
to be marked as done.

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

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


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

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

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

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated impressive 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, 03 Feb 2018 14:41:34 +0200
Source: impressive
Binary: impressive
Architecture: source
Version: 0.11.2-1.1
Distribution: unstable
Urgency: low
Maintainer: Yaroslav Halchenko 
Changed-By: Adrian Bunk 
Description:
 impressive - PDF presentation tool with eye candies
Closes: 866433
Changes:
 impressive (0.11.2-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Update the build dependency from python-imaging to python-pil,
 also drop the alternative dependency on python-imaging.
 (Closes: #866433)
Checksums-Sha1:
 d8dc19e152a1378a7a22922c90433516337d2357 2167 impressive_0.11.2-1.1.dsc
 da4cd746b24ae491631644bea54ac0df011f1c47 9728 
impressive_0.11.2-1.1.debian.tar.xz
Checksums-Sha256:
 753255d95a258009c7afea76673635879e17fdb51f85e26524c29b647bd6 2167 
impressive_0.11.2-1.1.dsc
 9f63b91de3aae198777115d8bef243eaaab5cc31cb5f6988401497279c559786 9728 
impressive_0.11.2-1.1.debian.tar.xz
Files:
 3f0e0de9e52007b88f78af2dd8aff48e 2167 x11 optional impressive_0.11.2-1.1.dsc
 a46402ddac8255d34fff145d0864b7bd 9728 x11 optional 
impressive_0.11.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlp1rxUACgkQiNJCh6LY
mLEekA//V+G75AoPGPZSIr6ykmEFKPAukCJ95frg/jvyo0nB/A5yeoN+Rx1hQTMi
KthFRjiE+Hi7yOJ1b9OttzB0NywFcpCPFh71KRrMcxIWLjv+dJ3uI6mwGE6cUNem
csXJicQenlHATYto0aUoabHSFhkmDhTkGOaWTvHARYYjxAgJvW4qARugc/FFY+yl
rLimuN76DQxfAvfrH8qRppTEYGWyMwd5JrLj3+Nfi1KRqvunHnwZkHzOViaXQ3OW
HA/htx/pxxN/rieSDme8iRB1+bbA4YjEUF0OKI7UnnkMDkl/FLvQ3m7Kcc4bYLIj
Q2P6t/QnE9FrYX6iwvY09+lr5AMHv9Wo+ppY7HJivMUQqoWILCAjgddD1Ro7zrQT
G5+OaNzRrwcxLeYBM2r7jdVzHiNwlSH1P2JWi5Yt0GLq6LkRzh/jB1ofMAmXFccE
JqHrWgPSdASXJrqdyYP58zHYe8IrH4uCYr+7TDRBciBddOepukSZwW5clhmiRF2W
ro7RAhS6olwiABhtNkIgIY2aYAQOvQRU2tDqbyQcrCuLdrAQ1Z+J2/8aHzAFeK6m
+SD0Swlrad/g8+ZE6sBgGW2mKazkiq1TfLFyQ2mkOkDVL0t2P4f2peF9MkOg6GMi
bBRA4If0QnD6e3zpmtkWrKAWlw37uM1//0g60pMIRekHNBJCUKc=
=z0J8
-END PGP SIGNATURE End Message ---

Bug#888654: marked as done (mpv: CVE-2018-6360)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 15:18:47 +
with message-id 
and subject line Bug#888654: fixed in mpv 0.27.0-3
has caused the Debian Bug report #888654,
regarding mpv: CVE-2018-6360
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.)


-- 
888654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpv
Version: 0.23.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/mpv-player/mpv/issues/5456

Hi,

the following vulnerability was published for mpv.

CVE-2018-6360[0]:
| mpv through 0.28.0 allows remote attackers to execute arbitrary code
| via a crafted web site, because it reads HTML documents containing
| VIDEO elements, and accepts arbitrary URLs in a src attribute without a
| protocol whitelist in player/lua/ytdl_hook.lua. For example, an
| av://lavfi:ladspa=file= URL signifies that the product should call
| dlopen on a shared object file located at an arbitrary local pathname.
| The issue exists because the product does not consider that youtube-dl
| can provide a potentially unsafe URL.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-6360
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6360
[1] https://github.com/mpv-player/mpv/issues/5456

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mpv
Source-Version: 0.27.0-3

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated mpv 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, 03 Feb 2018 14:59:20 +0100
Source: mpv
Binary: mpv libmpv1 libmpv-dev
Architecture: source
Version: 0.27.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 libmpv-dev - video player based on MPlayer/mplayer2 (client library dev files)
 libmpv1- video player based on MPlayer/mplayer2 (client library)
 mpv- video player based on MPlayer/mplayer2
Closes: 888654
Changes:
 mpv (0.27.0-3) unstable; urgency=high
 .
   * debian/patches/09_ytdl-hook-whitelist-protocols.patch:
 - Add patch which whitelists protocols received from youtube-dl.
   Fixes CVE-2018-6360. (Closes: #888654)
Checksums-Sha1:
 ade3cfeb669a5fa9b62a52bd58d43f5b2a791219 2862 mpv_0.27.0-3.dsc
 dacc52a468909f6369d7a3e2b0346e50db4c82f3 106516 mpv_0.27.0-3.debian.tar.xz
 a5e9df2cc13b162f8f365d6b9e332aef2d27b2a1 8273 mpv_0.27.0-3_source.buildinfo
Checksums-Sha256:
 ae67a4dceb9f9c4e33cd918a5b253e76583ca88c872f1fafd1ef78a5345dd36e 2862 
mpv_0.27.0-3.dsc
 d37995a0ca22027eca5559dbcfc37592335eb70360e68f0307d840af4ef898fe 106516 
mpv_0.27.0-3.debian.tar.xz
 a8b093454a689860b59f6919d1b3f56488ab323d33e13a81f26f3d08d5ed7470 8273 
mpv_0.27.0-3_source.buildinfo
Files:
 1826816c4d4874115ec5a38dcdae3c16 2862 video optional mpv_0.27.0-3.dsc
 357795b9b31f2d36a022452550a97fe3 106516 video optional 
mpv_0.27.0-3.debian.tar.xz
 1138f4c38afc17996b41571fe33b0318 8273 video optional 
mpv_0.27.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlp1wKYUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe/60hAAnmAerysoI2v/jcW0spJZnq53lZxq
GguuOV1lGxh4Q8q+5lwk4dp989a9nZFW0+F3AI3AdosocHXGhdx9fIfk4Ih6RLed
0D6FTMpdHAZadMgcapWKHZpKUlJ2XkW/2P0EL1oB0YCSQja9ET8SGEGPXQo4/bch
dSTeas1wTp/6cw4mPgRnNM4sgqScwb958oe6InV7ThO2RNP9a1dVJewuqv2YvIrq
T0i1TtsmZn8NcHxUaSh2AhBFjRsr5V8/1hQC7Z6CxOuSySYE6THfpLeq3Gsq5XkH
Gu4RHHD9WRmGTaYSUbCpJDmJemKCNXp/+g5PGMIr4bf46rQh1QVGWp0dJUj5UvLY
PcW3Wh2DYbj/8RMovxvDCZ+opRZt3tXFrt3RRnqZVmM9rwYq9gtoxNQNNwL6sFrO
ckLqLXXE5aRuV7HlpQlxpsvG6pIbKavPgLXhssYL39JAfwwo/TgZ/LGJTmS1Fm21

Bug#889336: dnsmasq cannot be started with systemd 237-1

[cruncher]

Package: dnsmasq
Version: 2.78-1
Severity: grave
Tags: upstream

After upgrading from systemd 236-3+b1 to 237-1, the service cannot be started
anymore getting following error in syslog (Tested on multiple (sid) machines):

Feb 03 10:47:35 pcname systemd[1]: Starting dnsmasq - A lightweight DHCP and
caching DNS server...
Feb 03 10:47:35 pcname dnsmasq[2720]: dnsmasq: syntax check OK.
Feb 03 10:47:35 pcname dnsmasq[2739]: started, version 2.78 cachesize 150
Feb 03 10:47:35 pcname dnsmasq[2739]: compile time options: IPv6 GNU-getopt
DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
inotif
Feb 03 10:47:35 pcname dnsmasq[2739]: read /etc/hosts - 30 addresses
Feb 03 10:47:35 pcname systemd[1]: dnsmasq.service: Permission denied while
opening PID file or unsafe symlink chain: /run/dnsmasq/dnsmasq.pid
Feb 03 10:49:06 pcname systemd[1]: dnsmasq.service: Start-post operation timed
out. Stopping.
Feb 03 10:49:06 pcname dnsmasq[2739]: exiting on receipt of SIGTERM
Feb 03 10:49:06 pcname systemd[1]: dnsmasq.service: Failed with result
'timeout'.
Feb 03 10:49:06 pcname systemd[1]: Failed to start dnsmasq - A lightweight DHCP
and caching DNS server.

Regards



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

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

Versions of packages dnsmasq depends on:
ii  dnsmasq-base 2.78-1
ii  init-system-helpers  1.51
ii  lsb-base 9.20170808
ii  netbase  5.4

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
pn  resolvconf  

-- Configuration Files:
/etc/default/dnsmasq [Errno 2] No such file or directory: '/etc/default/dnsmasq'
/etc/dnsmasq.conf changed [not included]

-- no debconf information

Bug#888953: marked as done (gobby accesses the network during the build)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 15:09:09 +
with message-id 
and subject line Bug#888953: fixed in gobby 0.6.0~20170204~e5c2d1-3
has caused the Debian Bug report #888953,
regarding gobby accesses the network during the build
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.)


-- 
888953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gobby
Version: 0.6.0~20170204~e5c2d1-2
Severity: serious
Tags: sid buster

While seen on a launchpad build, it looks like a missing build dependency,
because it tries to access the docbookx.dtd from the network:

make[3]: Leaving directory '/<>/po'
Making check in help
make[3]: Entering directory '/<>/help'
xmllint --noout --noent --path C:./C --xinclude --postvalid ./C/gobby.xml
xmllint --noout --xinclude --dtdvalid
'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd'
gobby-C.omf
error : error : No such file or directory
No such file or directory
warning: failed to load external entity
"http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd;
Could not parse DTD
http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd
./C/gobby.xml:6: warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
]>
  ^
Makefile:945: recipe for target 'check-doc-omf' failed
make[3]: *** [check-doc-omf] Error 2
make[3]: *** Waiting for unfinished jobs
error : No such file or directory
warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
validity error : Could not load the external subset
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
Document ./C/gobby.xml does not validate
Makefile:917: recipe for target 'check-doc-docs' failed
make[3]: *** [check-doc-docs] Error 3
make[3]: Leaving directory '/<>/help'
Makefile:1272: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:1567: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2

https://launchpad.net/ubuntu/+source/gobby/0.6.0~20170204~e5c2d1-2/+build/14219811
--- End Message ---
--- Begin Message ---
Source: gobby
Source-Version: 0.6.0~20170204~e5c2d1-3

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated gobby 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, 03 Feb 2018 12:23:50 +0100
Source: gobby
Binary: gobby
Architecture: source
Version: 0.6.0~20170204~e5c2d1-3
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Philipp Kern 
Description:
 gobby  - infinote-based collaborative text editor
Closes: 888953
Changes:
 gobby (0.6.0~20170204~e5c2d1-3) unstable; urgency=medium
 .
   * Apply patch to use yelp-tools rather than gtk-doc-utils.
 (Closes: #888953)
Checksums-Sha1:
 8a5fbf85b446bd5a1e95927d2889477ae52f3da5 1687 gobby_0.6.0~20170204~e5c2d1-3.dsc
 d3623a5a875339bf88099f5b1ab95997de93d64c 12048 
gobby_0.6.0~20170204~e5c2d1-3.debian.tar.xz
 bed15f3dc1481fc0287eb5359654e21e42a37a94 16658 
gobby_0.6.0~20170204~e5c2d1-3_source.buildinfo
Checksums-Sha256:
 b09c4cc230a2727232fb2c09f93b657be19ca214aa88d76c923762e3225a010c 1687 
gobby_0.6.0~20170204~e5c2d1-3.dsc
 dee79471527121f9d07baa5533a391871c764628749448d214b13148b14b 12048 
gobby_0.6.0~20170204~e5c2d1-3.debian.tar.xz
 3a0834ef01c8818a98a059bf3b8ff6cd471e4832534b326efb9174fbc6107edf 16658 
gobby_0.6.0~20170204~e5c2d1-3_source.buildinfo
Files:
 ffa5cdcba56e23e73b9eaaec17dc21ee 1687 net optional 
gobby_0.6.0~20170204~e5c2d1-3.dsc
 1ef84434885e9ace9b3138906f3664e6 12048 net optional 

Bug#889297: debops: New upstream release v0.6.0

[Daniel Stender]

On 02/03/2018 02:49 PM, Frans van Berckel wrote:
> Package: debops
> Version: 0.4.3-1
> Severity: serious
> 
> There a new upstream version v0.6.0, in Github releases available.
> 
> https://github.com/debops/debops/releases
> 
> If i am well, this one doesn't depends on the debops-playbooks package
> any more, as spoked about in debbug 880102.
> 
> RM: debops-playbooks/experimental -- ROM; not needed anymore
> https://bugs.debian.org/880102
> 
> But there a problem with this old one. Check debbug 880102 
> 
> debops: Uninstallable due to debops-playbooks removal
> https://bugs.debian.org/884639
> 
> So please, are you willing to update Debian VCS / Git? Good to know
> v1.0.0 is planned for spring 2018.
> 
> Thanks,
> 
> Frans van Berckel

Thanks for posting this bug report. The package update is coming up in the next 
weeks.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#866433: impressive: diff for NMU version 0.11.2-1.1

[Yaroslav Halchenko]

Feel welcome to upload without delays

On February 3, 2018 7:47:15 AM EST, Adrian Bunk  wrote:
>Control: tags 866433 + patch
>Control: tags 866433 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for impressive (versioned as 0.11.2-1.1) and 
>uploaded it to DELAYED/15. Please feel free to tell me if I should 
>cancel it.
>
>cu
>Adrian

-- 
Sent from a phone which beats iPhone.

Bug#889303: syslog-ng FTBFS: FAIL: modules/python/pylib/test_pylib

[Adrian Bunk]

Source: syslog-ng
Version: 3.13.2-2
Severity: serious

Some recent change in unstable makes syslog-ng FTBFS:

https://tests.reproducible-builds.org/debian/history/syslog-ng.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/syslog-ng.html

...
FAIL: modules/python/pylib/test_pylib
=

make[7]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
nosetests ../../modules/python/pylib/syslogng

--
Ran 108 tests in 0.230s

OK
pep8 --ignore=E501 ../../modules/python/pylib/syslogng
pylint -r n --rcfile=../../modules/python/pylib/pylintrc 
../../modules/python/pylib/syslogng
Using config file /build/1st/syslog-ng-3.13.2/modules/python/pylib/pylintrc
Unable to create directory /nonexistent/first-build/.pylint.d
Unable to create file /nonexistent/first-build/.pylint.d/syslogng1.stats: 
[Errno 2] No such file or directory: 
'/nonexistent/first-build/.pylint.d/syslogng1.stats'
* Module syslogng.debuggercli.templatelexer
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/templatelexer.py:127:
 [R1710(inconsistent-return-statements), 
TemplateLexer.t_dollarparen_PAREN_CLOSE] Either all return statements in a 
function should return an expression, or none of them should.
* Module syslogng.debuggercli.completerlang
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/completerlang.py:57:
 [R1710(inconsistent-return-statements), CompleterLang.p_error] Either all 
return statements in a function should return an expression, or none of them 
should.
* Module syslogng.debuggercli.commandlinelexer
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:56:
 [R1710(inconsistent-return-statements), CommandLineLexer._get_next_token] 
Either all return statements in a function should return an expression, or none 
of them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:89:
 [R1710(inconsistent-return-statements), 
CommandLineLexer._process_normal_character] Either all return statements in a 
function should return an expression, or none of them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:105:
 [R1710(inconsistent-return-statements), CommandLineLexer._close_paren] Either 
all return statements in a function should return an expression, or none of 
them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:112:
 [R1710(inconsistent-return-statements), CommandLineLexer._close_current_token] 
Either all return statements in a function should return an expression, or none 
of them should.

---
Your code has been rated at 9.96/10

Makefile:18463: recipe for target 'python-pylint' failed
make[7]: *** [python-pylint] Error 8
FAIL modules/python/pylib/test_pylib.sh (exit status: 2)


Testsuite summary for syslog-ng 3.13.2

# TOTAL: 71
# PASS:  70
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

Makefile:16576: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1

Bug#888654: mpv: CVE-2018-6360

[James Cowgill]

Hi,

On 28/01/18 14:17, Salvatore Bonaccorso wrote:
> Source: mpv
> Version: 0.23.0-1
> Severity: grave
> Tags: security upstream
> Forwarded: https://github.com/mpv-player/mpv/issues/5456
> 
> Hi,
> 
> the following vulnerability was published for mpv.
> 
> CVE-2018-6360[0]:
> | mpv through 0.28.0 allows remote attackers to execute arbitrary code
> | via a crafted web site, because it reads HTML documents containing
> | VIDEO elements, and accepts arbitrary URLs in a src attribute without a
> | protocol whitelist in player/lua/ytdl_hook.lua. For example, an
> | av://lavfi:ladspa=file= URL signifies that the product should call
> | dlopen on a shared object file located at an arbitrary local pathname.
> | The issue exists because the product does not consider that youtube-dl
> | can provide a potentially unsafe URL.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

I have attempted to backport the upstream patch to fix this and
committed it to the mpv repository on salsa. The diff is here:

https://salsa.debian.org/multimedia-team/mpv/compare/debian%2F0.23.0-2...debian%2Fstretch

Unlike the backport for 0.27 which was fairly straightforward, the
backport for 0.23 required significant changes and I ended up rewriting
half of it. This means I am less confident about catching all the cases
to fix this bug. It would be good if anyone could check it over.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#888953: gobby accesses the network during the build

[Philipp Kern]

On 02/01/2018 01:45 PM, Simon McVittie wrote:
>> Well, I suppose it'd help if there would be some guidance on how to do
>> things today. I'm (somewhat) happy to fix it upstream if needed.
> Here's upstream's migration guide, with links to the commits used to
> migrate an example package:
> https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure
> (I'll try to follow up to the other bugs from the same MBF as #885642 at
> some point with a reference to this.)

Ok, thanks. I did that and uploaded a new version. I hope that the new
toolchain does not access the network. I have honestly no clue how I'd
successfully test for that locally.

Kind regards
Philipp Kern



signature.asc
Description: OpenPGP digital signature

Processed: Bug #888654 in mpv marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888654 [src:mpv] mpv: CVE-2018-6360
Ignoring request to alter tags of bug #888654 to the same tags previously set

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

Bug#888654: Bug #888654 in mpv marked as pending

[jcowgill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/mpv/commit/e6d98c0b6bfcd3833fcaf39b4f166da8d3179720


Add patch for CVE-2018-6360

Closes: #888654



(this message was generated automatically)
-- 
Greetings

Bug#888654: Bug #888654 in mpv marked as pending

[jcowgill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/mpv/commit/ddface85a1adfdfe02ffb25b5ac7fac715213b97


Add patch for CVE-2018-6360

Closes: #888654



(this message was generated automatically)
-- 
Greetings

Processed: Bug #888654 in mpv marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888654 [src:mpv] mpv: CVE-2018-6360
Added tag(s) pending.

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

Bug#889285: bind9: CVE-2017-3139 affects debian too

[Roberto C . Sánchez]

On Sat, Feb 03, 2018 at 02:37:14PM +0100, Vladislav Kurz wrote:
> Hello LTS team,
> 
> please have a look at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889285
> 
> I think it is the same bug as CVE-2017-3139 which was considered to affect
> only RedHat, but it seems to affect debian wheezy too.
> 
> Please check if it is possible to apply the same fixes as RedHat did.
> Or at leas update the bind package in wheezy-backports to match the version
> and security fixes from debian jesssie.
> 
I am taking a look at this now.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#889298: wcc: Uninstallable since binutils 2.30-1, probably needs binNMU

[Axel Beckert]

Package: wcc
Version: 0.0.2+dfsg-2
Severity: serious

Hi,

wcc depends on libbinutils << 2.30 while Debian Unstable has libbinutils
2.30-1. So wcc either needs a binNMU or, if that doesn't suffice, a
sourceful upload.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 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)
LSM: AppArmor: enabled

Versions of packages wcc depends on:
ii  libbinutils   2.29.90.20180122-1
ii  libc6 2.26-6
ii  libcapstone3  3.0.4-3
ii  libelf1   0.170-0.3
ii  liblua5.3-0   5.3.3-1
ii  libopenlibm2  0.5.4+dfsg-3

wcc recommends no packages.

wcc suggests no packages.

-- no debconf information

Bug#889210: marked as done (libdap-doc is empty)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 13:50:06 +
with message-id 
and subject line Bug#889210: fixed in libdap 3.19.1-2
has caused the Debian Bug report #889210,
regarding libdap-doc is empty
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.)


-- 
889210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdap-doc
Version: 3.18.2-2
Severity: grave

$ dpkg -L libdap-doc 
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libdap-doc
/usr/share/doc/libdap-doc/changelog.Debian.gz
/usr/share/doc/libdap-doc/changelog.gz
/usr/share/doc/libdap-doc/copyright
/usr/share/doc/libdap-doc/readme.txt.gz
$ 


readme.txt.gz contains installation instructions
that shouldn't even be in the binary package.

The package in jessie contains 80 MB that seem to be missing.
--- End Message ---
--- Begin Message ---
Source: libdap
Source-Version: 3.19.1-2

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libdap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 12:35:34 +
Source: libdap
Binary: libdap25 libdapclient6v5 libdapserver7v5 libdap-bin libdap-dev 
libdap-doc
Architecture: source amd64 all
Version: 3.19.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libdap-bin - Binaries for the  libdap Data Access Protocol library
 libdap-dev - Development files (headers and static libraries) for libdap
 libdap-doc - Documentation for the libdap Data Access Protocol library
 libdap25   - Open-source Project for a Network Data Access Protocol library
 libdapclient6v5 - Client library for the Network Data Access Protocol
 libdapserver7v5 - Server library for the Network Data Access Protocol
Closes: 837429 889210
Changes:
 libdap (3.19.1-2) unstable; urgency=medium
 .
   * Change VCS to point to salsa.debian.org
   * Standards-Version: 4.1.3
   * Add libdap-doc.docs to install docs. Closes: #889210
   * Drop description reference to external docs. Closes: #837429
Checksums-Sha1:
 cf636f5d826173a50082645224cd1fb71e2b6399 2329 libdap_3.19.1-2.dsc
 ffb478a36cc34df85c6f18828af72ce9933fe391 13332 libdap_3.19.1-2.debian.tar.xz
 f067c655676af638e55316167785b7e68e2d1434 78784 
libdap-bin-dbgsym_3.19.1-2_amd64.deb
 8ddd5a27887cf5785df2719d7c25c2c8dc1c6f82 119756 libdap-bin_3.19.1-2_amd64.deb
 60c5a5e8eff0c950adcda15efb008ee98158d80e 813828 libdap-dev_3.19.1-2_amd64.deb
 d857539555902c371f58df52ad85da5a79a3c78e 3673268 libdap-doc_3.19.1-2_all.deb
 800bcdafda149ea495199b0d8c109489f7a2cb3a 4729972 
libdap25-dbgsym_3.19.1-2_amd64.deb
 384dbc9418106ea905940e0fe24327c2b01c69fb 531572 libdap25_3.19.1-2_amd64.deb
 9805d643c0c0456f481a30ad3a7043daeaebfe69 10781 libdap_3.19.1-2_amd64.buildinfo
 a3cb3588c19371d7ebb4fa620b5feb07554c2c32 807948 
libdapclient6v5-dbgsym_3.19.1-2_amd64.deb
 b4ee4a9e6b4517d4c878c0f7a9a92a3372add02d 192372 
libdapclient6v5_3.19.1-2_amd64.deb
 0b671f6f6a0421d6e649c39af83633eb495c0d44 128600 
libdapserver7v5-dbgsym_3.19.1-2_amd64.deb
 f8cc159c5f820efb69170e402811f17d4165c56b 125464 
libdapserver7v5_3.19.1-2_amd64.deb
Checksums-Sha256:
 faee2d54078829d43d99dd470df17fb08c76e7fabac8dbef9114c2630359b4f4 2329 
libdap_3.19.1-2.dsc
 16f484bdf21085ec8b1439bf1056a18b8e4e31b02eb1bcf8f8764c2811191a71 13332 
libdap_3.19.1-2.debian.tar.xz
 0bbb564f1ab660b4a0827623eaf6cd79470736924421bb72aed498b169376602 78784 
libdap-bin-dbgsym_3.19.1-2_amd64.deb
 e72b8f7c257666d5a146bc6532bbcf035d9332c9f55ec871f6dafb66426a2fac 119756 
libdap-bin_3.19.1-2_amd64.deb
 8bb523922bb3395f8379e0f1e8813167441292e39b041052cef3d7d1e01b0cc4 813828 
libdap-dev_3.19.1-2_amd64.deb
 faf2f59cc07a369b67c1f94b22dc0fc4c2538d2c4385c7f58c2c7aabee876c8b 3673268 
libdap-doc_3.19.1-2_all.deb
 e02d45a5bb956f97482c792a09e812582e378fe03dacf38fa1ffaea80747cbc0 

Bug#889297: debops: New upstream release v0.6.0

[Frans van Berckel]

Package: debops
Version: 0.4.3-1
Severity: serious

There a new upstream version v0.6.0, in Github releases available.

https://github.com/debops/debops/releases

If i am well, this one doesn't depends on the debops-playbooks package
any more, as spoked about in debbug 880102.

RM: debops-playbooks/experimental -- ROM; not needed anymore
https://bugs.debian.org/880102

But there a problem with this old one. Check debbug 880102 

debops: Uninstallable due to debops-playbooks removal
https://bugs.debian.org/884639

So please, are you willing to update Debian VCS / Git? Good to know
v1.0.0 is planned for spring 2018.

Thanks,


Frans van Berckel

Bug#889144: stricter PIDfile handling breaks several daemons

[Sven Hartge]

Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl:
> Am 03.02.2018 um 13:27 schrieb Sven Hartge:
>> Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl:

>>> Does munin-node have the same mismatch?
 
>> It has:

>> But, as you can see, the directory is also used by the munin-updater
>> which is run as user "munin" so you can't make the directory owned by
>> root.
 
> The alternative afaics would be, that the daemon writes the pid file as
> munin:munin then (or ulog:ulog for the above case).

No, this would open a potential DoS vector.

Image an attacker gaining access to the munin user. He would then be able
to write any PID to the PIDfile and the init system would kill the other
process when the munin-node service is stopped/restarted.

See https://security-tracker.debian.org/tracker/CVE-2017-14610 for
example.

Acknowleged, this is a a bit unlikely issue, but I don't think it would be
wise to propagate it further.

Also looking at the bigger picture here: This change in systemd, while
with security in mind, changes the way PIDfiles have been handled for the
last ... forever.

Debian packages one might be able to fix but what about all the other 3rd
party packages and locally written code out there? It is susceptible to
break upon upgrade to Buster and who will be blamed (again)? systemd of
course, "breaking all the things again".

Grüße,
Sven.

Bug#889144: stricter PIDfile handling breaks several daemons

[Michael Biebl]

Am 03.02.2018 um 13:27 schrieb Sven Hartge:
> Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl:
> 
>> Am 02.02.2018 um 20:07 schrieb Sven Hartge:
> 
>>> ulogd2 drops its priviliges on its own. It needs to start as root to
>>> connect to the netlink sockets.
>  
>> So, ulogd2 creates a directory /run/ulog which is owned by ulog:ulog but
>> then creates the pid file /run/ulog/ulog.pid owned by root:root.
> 
> Yes.
> 
>> I assume if you overwrite /usr/lib/tmpfiles.d/ulogd2.conf by creating a
>> /etc/tmpfiles.d/ulogd2.conf containing
>>
>> d /run/ulog 0755 root root - -
>>
>> ulogd2 will start properly.
> 
> It does. But there must be a reason for the directory to be owned by
> ulog:ulog, no? 

No idea. This is something the ulogd maintainer would have to answer.

What consequences does it have changing it? It may work for
> my simple setup but then break again for other people.
> 
>> I assume, ulogd2 should either ensure the pidfile is owned ulog:ulog or
>> change the run directory to match the permissions of the pid file.
>>
>> Does munin-node have the same mismatch?
> 
> It has:
> 

Ok, thanks for checking.

> But, as you can see, the directory is also used by the munin-updater
> which is run as user "munin" so you can't make the directory owned by
> root.

The alternative afaics would be, that the daemon writes the pid file as
munin:munin then (or ulog:ulog for the above case).

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



signature.asc
Description: OpenPGP digital signature

Processed: psad: diff for NMU version 2.4.3-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 867914 + pending
Bug #867914 [psad] psad: should depend on net-tools and iproute2
Added tag(s) pending.

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

Bug#867914: psad: diff for NMU version 2.4.3-1.2

[Adrian Bunk]

Control: tags 867914 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru psad-2.4.3/debian/changelog psad-2.4.3/debian/changelog
--- psad-2.4.3/debian/changelog	2017-08-06 13:38:41.0 +0300
+++ psad-2.4.3/debian/changelog	2018-02-03 14:53:36.0 +0200
@@ -1,3 +1,10 @@
+psad (2.4.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on iproute2. (Closes: #867914)
+
+ -- Adrian Bunk   Sat, 03 Feb 2018 14:53:36 +0200
+
 psad (2.4.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru psad-2.4.3/debian/control psad-2.4.3/debian/control
--- psad-2.4.3/debian/control	2017-08-06 13:38:41.0 +0300
+++ psad-2.4.3/debian/control	2018-02-03 14:53:36.0 +0200
@@ -15,7 +15,7 @@
  libnet-ip-perl, libdate-calc-perl, libcarp-clan-perl,
  whois, psmisc, libiptables-parse-perl, libiptables-chainmgr-perl,
  default-mta | mail-transport-agent, bsd-mailx | mailx | mailutils,
- lsb-base, net-tools
+ lsb-base, net-tools, iproute2
 Suggests: fwsnort
 Description: Port Scan Attack Detector
  PSAD is a collection of four lightweight system daemons (in Perl and

Processed: impressive: diff for NMU version 0.11.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 866433 + patch
Bug #866433 [src:impressive] impressive: depends on obsolete python-imaging 
(replace with python3-pil or python-pil)
Added tag(s) patch.
> tags 866433 + pending
Bug #866433 [src:impressive] impressive: depends on obsolete python-imaging 
(replace with python3-pil or python-pil)
Added tag(s) pending.

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

Bug#866433: impressive: diff for NMU version 0.11.2-1.1

[Adrian Bunk]

Control: tags 866433 + patch
Control: tags 866433 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru impressive-0.11.2/debian/changelog impressive-0.11.2/debian/changelog
--- impressive-0.11.2/debian/changelog	2017-12-19 19:40:40.0 +0200
+++ impressive-0.11.2/debian/changelog	2018-02-03 14:41:34.0 +0200
@@ -1,3 +1,12 @@
+impressive (0.11.2-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update the build dependency from python-imaging to python-pil,
+also drop the alternative dependency on python-imaging.
+(Closes: #866433)
+
+ -- Adrian Bunk   Sat, 03 Feb 2018 14:41:34 +0200
+
 impressive (0.11.2-1) unstable; urgency=medium
 
   * Fresh upstream release
diff -Nru impressive-0.11.2/debian/control impressive-0.11.2/debian/control
--- impressive-0.11.2/debian/control	2017-12-19 19:40:40.0 +0200
+++ impressive-0.11.2/debian/control	2018-02-03 14:41:34.0 +0200
@@ -13,7 +13,7 @@
  xvfb,
  xauth,
  python-pygame,
- python-imaging,
+ python-pil,
  libgl1-mesa-dri,
  mupdf-tools (>= 1.5) | xpoppler-utils,
  pdftk,
@@ -27,7 +27,7 @@
 Depends: python,
  ${misc:Depends},
  python-pygame,
- python-pil | python-imaging,
+ python-pil,
  mupdf-tools (>= 1.5) | xpoppler-utils,
 Recommends: mplayer,
 pdftk,

Bug#853640: reptyr: diff for NMU version 0.6.2-1.1

[Tobias Frost]

Control: tags 853640 + patch

Dear maintainer,

Lukas has prepared an NMU for reptyr (versioned as 0.6.2-1.1) and
I uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru reptyr-0.6.2/debian/changelog reptyr-0.6.2/debian/changelog
--- reptyr-0.6.2/debian/changelog	2015-02-09 01:13:04.0 +0100
+++ reptyr-0.6.2/debian/changelog	2018-01-27 18:37:40.0 +0100
@@ -1,3 +1,18 @@
+reptyr (0.6.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patches from upstream to fix FTBFS. (Closes: #853640)
+  * debian/control:
+- Bump dh version to 11, 7 is deprecated.
+- Use secure VCS links.
+- Bump standards version to 4.1.3 (no changes).
+  * Fix watch file.
+  * debian/rules:
+- Enable build-time hardening.
+- Fix FTBFS when /dev/tty0 does not exists.
+
+ -- Mateusz Łukasik   Sat, 27 Jan 2018 18:37:40 +0100
+
 reptyr (0.6.2-1) unstable; urgency=low
 
   * New release:
diff -Nru reptyr-0.6.2/debian/compat reptyr-0.6.2/debian/compat
--- reptyr-0.6.2/debian/compat	2015-02-09 01:11:06.0 +0100
+++ reptyr-0.6.2/debian/compat	2018-01-12 08:09:42.0 +0100
@@ -1 +1 @@
-7
+11
diff -Nru reptyr-0.6.2/debian/control reptyr-0.6.2/debian/control
--- reptyr-0.6.2/debian/control	2015-02-09 01:11:06.0 +0100
+++ reptyr-0.6.2/debian/control	2018-01-12 22:48:42.0 +0100
@@ -2,11 +2,11 @@
 Section: misc
 Priority: optional
 Maintainer: Evan Broder 
-Build-Depends: debhelper (>= 7.0.50~), dpkg-dev (>= 1.16.1~), python, python-pexpect
-Standards-Version: 3.9.6
+Build-Depends: debhelper (>= 11), python, python-pexpect
+Standards-Version: 4.1.3
 Homepage: https://github.com/nelhage/reptyr
-Vcs-Git: git://github.com/nelhage/reptyr.git -b debian
-Vcs-Browser: http://github.com/nelhage/reptyr/tree/debian
+Vcs-Git: https://github.com/nelhage/reptyr.git -b debian
+Vcs-Browser: https://github.com/nelhage/reptyr/tree/debian
 
 Package: reptyr
 Architecture: i386 amd64 armel armhf
diff -Nru reptyr-0.6.2/debian/patches/fix-ftbfs-gcc7.patch reptyr-0.6.2/debian/patches/fix-ftbfs-gcc7.patch
--- reptyr-0.6.2/debian/patches/fix-ftbfs-gcc7.patch	1970-01-01 01:00:00.0 +0100
+++ reptyr-0.6.2/debian/patches/fix-ftbfs-gcc7.patch	2018-01-27 18:37:21.0 +0100
@@ -0,0 +1,31 @@
+Description: Fix FTBFS with gcc-7
+Author: Nelson Elhage 
+Debian-Bug: https://bugs.debian.org/853640
+
+--- a/platform/linux/linux.h
 b/platform/linux/linux.h
+@@ -40,6 +40,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+
+--- a/attach.c
 b/attach.c
+@@ -389,8 +389,11 @@ int setup_steal_socket(struct steal_pty_state *steal) {
+ return errno;
+ 
+ steal->addr_un.sun_family = AF_UNIX;
+-snprintf(steal->addr_un.sun_path, sizeof(steal->addr_un.sun_path),
+- "%s/reptyr.sock", steal->tmpdir);
++if (snprintf(steal->addr_un.sun_path, sizeof(steal->addr_un.sun_path),
++ "%s/reptyr.sock", steal->tmpdir) >= sizeof(steal->addr_un.sun_path)) {
++error("tmpdir path too long!");
++return ENAMETOOLONG;
++}
+ 
+ if ((steal->sockfd = socket(AF_UNIX, SOCK_DGRAM, 0)) < 0)
+ return errno;
diff -Nru reptyr-0.6.2/debian/patches/series reptyr-0.6.2/debian/patches/series
--- reptyr-0.6.2/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ reptyr-0.6.2/debian/patches/series	2018-01-27 18:37:36.0 +0100
@@ -0,0 +1 @@
+fix-ftbfs-gcc7.patch
diff -Nru reptyr-0.6.2/debian/rules reptyr-0.6.2/debian/rules
--- reptyr-0.6.2/debian/rules	2015-02-09 01:11:06.0 +0100
+++ reptyr-0.6.2/debian/rules	2018-01-19 22:34:52.0 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+
 %:
 	dh $@
 
@@ -12,7 +14,12 @@
 # reptyr's test suite relies on being able to ptrace non-child
 # processes, which isn't allowed under yama's defaults on Ubuntu
 override_dh_auto_test:
+	if ! [ -f /dev/tty0 ]; \
+	then echo disable tests; \
+	else dh_auto_test; \
+	fi
+
 	if ! [ -f /proc/sys/kernel/yama/ptrace_scope ] || \
 	  [ "$$(cat /proc/sys/kernel/yama/ptrace_scope)" = 0 ]; then \
 	  dh_auto_test; \
-	fi
+	fi \
diff -Nru reptyr-0.6.2/debian/watch reptyr-0.6.2/debian/watch
--- reptyr-0.6.2/debian/watch	2015-02-09 01:11:06.0 +0100
+++ reptyr-0.6.2/debian/watch	2018-01-12 08:22:05.0 +0100
@@ -1,2 +1,3 @@
 version=3
-http://githubredir.debian.net/github/nelhage/reptyr/reptyr-(.*).tar.gz
+opts=uversionmangle=s/(\d+)-(\d+)-(\d+)/$1.$2.$3/ \
+https://github.com/nelhage/reptyr/releases .*/archive/reptyr-([\d.-]+)\.tar\.gz

Processed: reptyr: diff for NMU version 0.6.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853640 + patch
Bug #853640 [src:reptyr] reptyr: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#889144: stricter PIDfile handling breaks several daemons

[Sven Hartge]

Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl:

> Am 02.02.2018 um 20:07 schrieb Sven Hartge:

>> ulogd2 drops its priviliges on its own. It needs to start as root to
>> connect to the netlink sockets.
 
> So, ulogd2 creates a directory /run/ulog which is owned by ulog:ulog but
> then creates the pid file /run/ulog/ulog.pid owned by root:root.

Yes.

> I assume if you overwrite /usr/lib/tmpfiles.d/ulogd2.conf by creating a
> /etc/tmpfiles.d/ulogd2.conf containing
> 
> d /run/ulog 0755 root root - -
> 
> ulogd2 will start properly.

It does. But there must be a reason for the directory to be owned by
ulog:ulog, no? What consequences does it have changing it? It may work for
my simple setup but then break again for other people.

> I assume, ulogd2 should either ensure the pidfile is owned ulog:ulog or
> change the run directory to match the permissions of the pid file.
> 
> Does munin-node have the same mismatch?

It has:

,
| ds9:/run/munin# ls -al
| total 8
| drwxr-xr-x  2 munin root80 Feb  3 13:15 .
| drwxr-xr-x 55 root  root  1880 Feb  3 02:57 ..
| -rw-r--r--  1 munin munin7 Feb  3 13:15 
munin-feds.ath.cx-skuld.feds.ath.cx.lock
| -rw-r--r--  1 munin munin7 Feb  3 13:15 
munin-svenhartge.de-www.svenhartge.de.lock
`

But, as you can see, the directory is also used by the munin-updater
which is run as user "munin" so you can't make the directory owned by
root.

S°

Bug#884222: valabind: Fails to build with vala 0.38

[Sebastian Reichel]

On Tue, 30 Jan 2018 18:14:30 +0100 Rico Tzschichholz  wrote:
> On Mon, 22 Jan 2018 06:52:24 -0500 Jeremy Bicha  wrote:
> > https://salsa.debian.org/jbicha/valabind
> > 
> > Sebastian, could you take a look?
> > 
> 
> Afaics this looks good and should be uploaded asap.
> 
> This is the only bit which blocks the vala 0.38 introduction in testing.

I agree, based on a quick look. I'm currently too busy to take care
of it, though. Jeremy, could you upload your changes?

Thanks,

-- Sebastian


signature.asc
Description: PGP signature

Bug#889288: linux-image-4.9.0-5-amd64: Fails to boot on Apple MacMini4,1

[Romain Goyet]

Package: src:linux
Version: 4.9.65-3+deb9u2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * Fresh Debian 9.3 install on Apple MacMini4,1
   * Original kernel version (linux-image-4.9.0-4-amd64) works fine
   * "apt-get dist-upgrade": machine doesn't boot anymore
   * Found a workaround: "nomodeset nouveau.modeset=0" in boot args

-- Package-specific info:
** Version:
Linux version 4.9.0-5-amd64 (debian-ker...@lists.debian.org) (gcc version
6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3+deb9u2
(2018-01-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-5-amd64
root=UUID=f2f12a84-3ce3-4f48-b9c9-2b6aea4228a1 ro verbose nomodeset
nouveau.modeset=0

** Not tainted

** Kernel log:
[3.274777] systemd[1]: Started Dispatch Password Requests to Console
Directory Watch.
[3.278791] systemd[1]: Listening on Syslog Socket.
[3.282787] systemd[1]: Listening on udev Control Socket.
[3.286826] systemd[1]: Listening on fsck to fsckd communication Socket.
[3.291079] systemd[1]: Created slice User and Session Slice.
[3.342071] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[3.416026] usb 4-6: new full-speed USB device number 3 using ohci-pci
[3.508020] systemd-journald[187]: Received request to flush runtime
journal from PID 1
[3.518189] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[3.519785] ACPI: Power Button [PWRB]
[3.522092] input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[3.523577] ACPI: Sleep Button [SLPB]
[3.536642] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[3.538149] ACPI: Power Button [PWRF]
[3.562545] [Firmware Bug]: ACPI(IGPU) defines _DOD but not _DOS
[3.564118] ACPI: Video Device [IGPU] (multi-head: yes  rom: no  post:
no)
[3.565824] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2d/LNXVIDEO:00/input/input3
[3.593414] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[3.595748] sd 0:0:0:0: Attached scsi generic sg0 type 0
[3.597738] sr 1:0:0:0: Attached scsi generic sg1 type 5
[3.616173] EFI Variables Facility v0.08 2004-May-17
[3.623197] input: PC Speaker as /devices/platform/pcspkr/input/input4
[3.628356] bcma: bus0: Found chip with id 43224, rev 0x01 and package
0x08
[3.630074] bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800,
rev 0x22, class 0x0)
[3.631785] bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id
0x812, rev 0x17, class 0x0)
[3.635464] [drm] Initialized
[3.637484] bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev
0x0F, class 0x0)
[3.641977] snd_hda_intel :00:08.0: enabling device ( -> 0002)
[3.644813] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[3.660085] usb 4-6: New USB device found, idVendor=0a5c, idProduct=4500
[3.661825] usb 4-6: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[3.663552] usb 4-6: Product: BRCM2070 Hub
[3.665920] usb 4-6: Manufacturer: Apple Inc.
[3.682011] snd_hda_intel :00:08.0: Disabling MSI
[3.683728] snd_hda_intel :00:08.0: position_fix set to 1 for device
10de:cb89
[3.692287] hub 4-6:1.0: USB hub found
[3.696226] hub 4-6:1.0: 3 ports detected
[3.698389] wmi: Mapper loaded
[3.702988] bcma: bus0: Bus registered
[3.751573] intel_powerclamp: No package C-state available
[3.759918] hidraw: raw HID events driver (C) Jiri Kosina
[3.852461] usbcore: registered new interface driver usbhid
[3.854275] usbhid: USB HID core driver
[3.887351] Adding 3928060k swap on /dev/sda3.  Priority:-1 extents:1
across:3928060k SSFS
[3.899161] pstore: using zlib compression
[3.905496] pstore: Registered efi as persistent store backend
[3.911769] FAT-fs (sda1): Volume was not properly unmounted. Some data
may be corrupt. Please run fsck.
[3.949146] input: Apple Computer, Inc. IR Receiver as
/devices/pci:00/:00:06.0/usb4/4-5/4-5:1.0/0003:05AC:8242.0001/input/input5
[3.985834] Support for cores revisions 0x17 and 0x18 disabled by module
param allhwsupport=0. Try b43.allhwsupport=1
[3.988215] b43: probe of bcma0:1 failed with error -524
[3.990061] Broadcom 43xx driver loaded [ Features: PNLS ]
[4.003379] brcmsmac bcma0:1: mfg 4bf core 812 rev 23 class 0 irq 17
[4.009428] appleir 0003:05AC:8242.0001: input,hiddev0,hidraw0: USB HID
v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-:00:06.0-5/input0
[4.032027] usb 4-6.1: new full-speed USB device number 4 using ohci-pci
[4.043100] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[4.046109] brcmsmac bcma0:1 wlp3s0b1: renamed from wlan0
[4.148349] applesmc: key=215 fan=1 temp=29 index=28 acc=0 lux=0 kbd=0
[4.168960] usb 4-6.1: New USB device found, idVendor=05ac,
idProduct=820a
[4.170847] usb 4-6.1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[

Bug#889187: marked as done (e17-dbg is empty)

[Debian Bug Tracking System]

Your message dated Sat, 3 Feb 2018 11:53:05 +0100
with message-id <20180203105305.ga1...@argenau.bebt.de>
and subject line Re: [Pkg-e-devel] Bug#889187: e17-dbg is empty
has caused the Debian Bug report #889187,
regarding e17-dbg is empty
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.)


-- 
889187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e17-dbg
Version: 0.17.6-1.1+b1
Severity: grave

$ dpkg -L e17-dbg 
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/e17-dbg
/usr/share/doc/e17-dbg/NEWS.Debian.gz
/usr/share/doc/e17-dbg/changelog.Debian.amd64.gz
/usr/share/doc/e17-dbg/changelog.Debian.gz
/usr/share/doc/e17-dbg/changelog.gz
/usr/share/doc/e17-dbg/copyright
$



Debug information is in e17-dbgsym,
likely the fix is to drop e17-dbg.
--- End Message ---
--- Begin Message ---
Version: 0.21.2-2

On 2018-02-03 Adrian Bunk  wrote:
> Package: e17-dbg
> Version: 0.17.6-1.1+b1
> Severity: grave

> $ dpkg -L e17-dbg 
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/e17-dbg
> /usr/share/doc/e17-dbg/NEWS.Debian.gz
> /usr/share/doc/e17-dbg/changelog.Debian.amd64.gz
> /usr/share/doc/e17-dbg/changelog.Debian.gz
> /usr/share/doc/e17-dbg/changelog.gz
> /usr/share/doc/e17-dbg/copyright
> $


> Debug information is in e17-dbgsym,
> likely the fix is to drop e17-dbg.

This is fixed in experimental.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'--- End Message ---

Bug#889127: marked as done (ggcov FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 10:36:33 +
with message-id 
and subject line Bug#889127: fixed in ggcov 0.9-20
has caused the Debian Bug report #889127,
regarding ggcov FTBFS: test failures
to be marked as done.

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

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


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

Some recent change in unstable makes ggcov FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/ggcov-0.9'
(cd test && ./runtest)
Running tests
hostname: "profitbricks-build1-amd64"
date: "20180201T144325"
uname -s: "Linux"
uname -m: "x86_64"
uname -r: "4.9.0-5-amd64"
head -1 /etc/os-release: "PRETTY_NAME="Debian GNU/Linux buster/sid""
which gcc: "/usr/bin/gcc"
gcc --version: "gcc (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
which g++: "/usr/bin/g++"
g++ --version: "g++ (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
PASS: (test000) unit tests
ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test002) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test004) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test005.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test006) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose 
--no-log
ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose --no-log
PASS: (test021) unit test for libpopt / fakepopt.c
ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log
Total: 2/20 tests passed
debian/rules:34: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: ggcov
Source-Version: 0.9-20

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated ggcov package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Feb 2018 10:36:45 +
Source: ggcov
Binary: ggcov
Architecture: source amd64
Version: 0.9-20
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 ggcov  - Graphical tool for displaying gcov test coverage data
Closes: 889127
Changes:
 ggcov (0.9-20) unstable; urgency=medium
 .
   * Standards-Version: 4.1.3
   * Drop obsolete --with autoconf
   * Support for gcc 7.3. Closes: #889127
Checksums-Sha1:
 de29c80d766bdbf3164480616c582dcb9405f62b 1762 ggcov_0.9-20.dsc
 fda1a9ccab14a4315b9a4fd1324674305f274def 13856 ggcov_0.9-20.debian.tar.xz
 d27e0a234ca11fbad12d965d09259dfd35af295b 8200360 ggcov-dbgsym_0.9-20_amd64.deb
 4c87e4af9ffcbad2e7e75a115046d1cbf9de4963 13651 ggcov_0.9-20_amd64.buildinfo
 171d527d3c7a2ce664b8c17862058f7d80576567 748916 

Processed: Re: [Pkg-dns-devel] Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +wheezy
Bug #889285 [bind9] bind9: CVE-2017-3139 affects debian too: assertion failure 
in validator.c:1858
Added tag(s) wheezy.

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

Bug#889285: [Pkg-dns-devel] Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

[Ondřej Surý]

Control: tags -1 +wheezy

You should probably contact the Debian LTS team as it affects wheezy that’s 
maintained by LTS Team.

Ondrej
--
Ondřej Surý 

> On 3 Feb 2018, at 11:12, Vladislav Kurz  wrote:
> 
> Package: bind9
> Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> Severity: grave
> Tags: security
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> This is a followup to archived bug #860225.
> 
> Although
> https://security-tracker.debian.org/tracker/CVE-2017-3139 states that
> debian is not affected by CVE-2017-3139, I observed this behavior on
> debian wheezy:
> 
> Feb  3 08:38:07 server named[16906]: validator.c:1858: INSIST(rdataset->type 
> == ((dns_rdatatype_t)dns_rdatatype_dnskey)) failed, back trace
> Feb  3 08:38:07 server named[16906]: #0 0x7f9b66798e19 in ??
> Feb  3 08:38:07 server named[16906]: #1 0x7f9b650d5f3a in ??
> Feb  3 08:38:07 server named[16906]: #2 0x7f9b66094e57 in ??
> Feb  3 08:38:07 server named[16906]: #3 0x7f9b6609b599 in ??
> Feb  3 08:38:07 server named[16906]: #4 0x7f9b650f4dfd in ??
> Feb  3 08:38:07 server named[16906]: #5 0x7f9b64aa8b50 in ??
> Feb  3 08:38:07 server named[16906]: #6 0x7f9b64492fbd in ??
> Feb  3 08:38:07 server named[16906]: exiting (due to assertion failure)
> 
> Ondrej Zary reported this on Sat, 02 Sep 2017 in bug #860225 but it
> was closed and archived without answer. May I ask why?
> 
> I had a look in the relevant bug report at redhat, but they do not
> provide much details https://bugzilla.redhat.com/show_bug.cgi?id=1447743
> So I'm not 100% sure it is the same bug.
> 
> 
> *** 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 lines ***
> 
> 
> -- System Information:
> Debian Release: 7.11
>  APT prefers oldoldstable
>  APT policy: (500, 'oldoldstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.2.0-5-686-pae (SMP w/1 CPU core)
> Locale: LANG=sk_SK, LC_CTYPE=sk_SK (charmap=ISO-8859-2)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages bind9 depends on:
> ii  adduser3.113+nmu3
> ii  bind9utils 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  debconf [debconf-2.0]  1.5.49
> ii  libbind9-801:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  libc6  2.13-38+deb7u12
> ii  libcap21:2.22-1.2
> ii  libdns88   1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u9
> ii  libisc84   1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  libisccc80 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  libisccfg821:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  liblwres80 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> ii  libssl1.0.01.0.1t-1+deb7u3
> ii  libxml22.8.0+dfsg1-7+wheezy12
> ii  lsb-base   4.1+Debian8+deb7u1
> ii  net-tools  1.60-24.2
> ii  netbase5.0
> 
> bind9 recommends no packages.
> 
> Versions of packages bind9 suggests:
> pn  bind9-doc   
> ii  dnsutils1:9.8.4.dfsg.P1-6+nmu2+deb7u19
> pn  resolvconf  
> pn  ufw 
> 
> -- Configuration Files:
> /etc/bind/named.conf.local changed:
> //
> // Do any local configuration here
> //
> // Consider adding the 1918 zones here, if they are not used in your
> // organization
> include "/etc/bind/zones.rfc1918";
> 
> /etc/bind/named.conf.options changed:
> options {
>directory "/var/cache/bind";
>// If there is a firewall between you and nameservers you want
>// to talk to, you may need to fix the firewall to allow multiple
>// ports to talk.  See http://www.kb.cert.org/vuls/id/800113
>// If your ISP provided one or more IP addresses for stable 
>// nameservers, you probably want to use them as forwarders.  
>// Uncomment the following block, and insert the addresses replacing 
>// the all-0's placeholder.
>// forwarders {
>//0.0.0.0;
>// };
>auth-nxdomain no;# conform to RFC1035
>listen-on-v6 { none; };
>listen-on { 127.0.0.1; };
>dnssec-enable yes;
>dnssec-validation auto;
>dnssec-lookaside auto;
> };
> 
> 
> -- debconf information:
>  bind9/different-configuration-file:
>  bind9/run-resolvconf: true
>  bind9/start-as-user: bind
> 
> ___
> pkg-dns-devel mailing list
> pkg-dns-de...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-dns-devel

Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

[Vladislav Kurz]

Package: bind9
Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
Severity: grave
Tags: security
Justification: renders package unusable

Dear Maintainer,

This is a followup to archived bug #860225.

Although
https://security-tracker.debian.org/tracker/CVE-2017-3139 states that
debian is not affected by CVE-2017-3139, I observed this behavior on
debian wheezy:

Feb  3 08:38:07 server named[16906]: validator.c:1858: INSIST(rdataset->type == 
((dns_rdatatype_t)dns_rdatatype_dnskey)) failed, back trace
Feb  3 08:38:07 server named[16906]: #0 0x7f9b66798e19 in ??
Feb  3 08:38:07 server named[16906]: #1 0x7f9b650d5f3a in ??
Feb  3 08:38:07 server named[16906]: #2 0x7f9b66094e57 in ??
Feb  3 08:38:07 server named[16906]: #3 0x7f9b6609b599 in ??
Feb  3 08:38:07 server named[16906]: #4 0x7f9b650f4dfd in ??
Feb  3 08:38:07 server named[16906]: #5 0x7f9b64aa8b50 in ??
Feb  3 08:38:07 server named[16906]: #6 0x7f9b64492fbd in ??
Feb  3 08:38:07 server named[16906]: exiting (due to assertion failure)

Ondrej Zary reported this on Sat, 02 Sep 2017 in bug #860225 but it
was closed and archived without answer. May I ask why?

I had a look in the relevant bug report at redhat, but they do not
provide much details https://bugzilla.redhat.com/show_bug.cgi?id=1447743
So I'm not 100% sure it is the same bug.


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


-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=sk_SK, LC_CTYPE=sk_SK (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages bind9 depends on:
ii  adduser3.113+nmu3
ii  bind9utils 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  debconf [debconf-2.0]  1.5.49
ii  libbind9-801:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  libc6  2.13-38+deb7u12
ii  libcap21:2.22-1.2
ii  libdns88   1:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u9
ii  libisc84   1:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  libisccc80 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  libisccfg821:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  liblwres80 1:9.8.4.dfsg.P1-6+nmu2+deb7u19
ii  libssl1.0.01.0.1t-1+deb7u3
ii  libxml22.8.0+dfsg1-7+wheezy12
ii  lsb-base   4.1+Debian8+deb7u1
ii  net-tools  1.60-24.2
ii  netbase5.0

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind9-doc   
ii  dnsutils1:9.8.4.dfsg.P1-6+nmu2+deb7u19
pn  resolvconf  
pn  ufw 

-- Configuration Files:
/etc/bind/named.conf.local changed:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
include "/etc/bind/zones.rfc1918";

/etc/bind/named.conf.options changed:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk.  See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable 
// nameservers, you probably want to use them as forwarders.  
// Uncomment the following block, and insert the addresses replacing 
// the all-0's placeholder.
// forwarders {
//  0.0.0.0;
// };
auth-nxdomain no;# conform to RFC1035
listen-on-v6 { none; };
listen-on { 127.0.0.1; };
dnssec-enable yes;
dnssec-validation auto;
dnssec-lookaside auto;
};


-- debconf information:
  bind9/different-configuration-file:
  bind9/run-resolvconf: true
  bind9/start-as-user: bind

Bug#859829: bump

[Ferenc Wágner]

I'm still behind with backports due to the recent security release.
When keeping the stack in testing starts blocking independent work,
please notify me and I'll switch to asking for backports exceptions.
-- 
Feri

Bug#888697: marked as done (fp-units-rtl-3.0.4: [armel] fpmake could not find unit directory for dependency package "rtl")

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 09:49:57 +
with message-id 
and subject line Bug#888697: fixed in fpc 3.0.4+dfsg-15
has caused the Debian Bug report #888697,
regarding fp-units-rtl-3.0.4: [armel] fpmake could not find unit directory for 
dependency package "rtl"
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.)


-- 
888697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fp-units-rtl-3.0.4
Version: 3.0.4+dfsg-14
Severity: serious
Justification: Prevents build of castle-game-engine on armel
Control: affects castle-game-engine

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

My recent upload of castle-game-engine FTBFS¹ on armel because fpmake can't
find the rtl units, while it built in the past (albeit with FPCDIR set). The
error is this:

if [ '(' -n "" ')' -a \
 '(' 3.0.4 '!=' '2.6.4' ')' -a \
 '(' 3.0.4 '!=' '2.6.2' ')' ]; then \
   ./fpmake --globalunitdir="" -v -o -Ur; \
else \
   ./fpmake -v -o -Ur; \
fi
The installer encountered the following error:
Could not find unit directory for dependency package "rtl"
Makefile:60: recipe for target 'build-using-fpmake' failed

Although one could argue that I can set FPCDIR in the debian/rules file, I
believe fpc should be made such that that is unneeded. Indeed, setting FPCDIR
in the previous version of the debian/rules file actually caused cge to FTBFS
with the latest changes in fpc regarding Multi-Arch.

¹ 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=armel=6.2%2Bdfsg1-2=1517164194=0

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

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

fp-units-rtl-3.0.4 depends on no packages.

Versions of packages fp-units-rtl-3.0.4 recommends:
ii  fp-compiler-3.0.4  3.0.4+dfsg-14

fp-units-rtl-3.0.4 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlpuI+MACgkQnFyZ6wW9
dQo0Vgf/YnAJeKSj62WWA0fV87pIpzaCy7SyrZG99axPwN3UOA8by/neQrZ/ID9V
PQNljXL8r2K0hFo4cDyBM2D9Orv+YkoHvj5nuhrWot/cuD1Taz7VulnFGZn/22Qu
jqSNLZP3DYGsLmUfYsovWMnzjF6aDhoWl5RQKtl1VA03YdFLuhIOP3fK/p4LO37B
x8C4SDf9D7PwLPv7Wr64Ju787T4Ejdn14SzT8xzotvHG39RdcvJBQfIDRtPpYPRK
m/YBuMP2cxCMoS6+9i8MDVKIjroxptJSUK2dfFr8eTZbyyJiSQwnnhwqgXxzC8ik
9V5H6Yr4BQ0n9/dPa5d0R2woLpmtFw==
=kFf3
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.0.4+dfsg-15

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

Debian distribution maintenance software
pp.
Abou Al Montacir  (supplier of updated fpc 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, 03 Feb 2018 10:30:21 +0100
Source: fpc
Binary: fpc-3.0.4 fpc-source-3.0.4 fp-compiler-3.0.4 fp-ide-3.0.4 
fp-utils-3.0.4 fp-docs-3.0.4 fp-units-rtl-3.0.4 fp-units-base-3.0.4 
fp-units-fcl-3.0.4 fp-units-fv-3.0.4 fp-units-gtk2-3.0.4 fp-units-db-3.0.4 
fp-units-gfx-3.0.4 fp-units-net-3.0.4 fp-units-math-3.0.4 fp-units-misc-3.0.4 
fp-units-multimedia-3.0.4 fp-units-i386-3.0.4 fpc fpc-source fp-compiler fp-ide 
fp-utils fp-docs fp-units-rtl fp-units-base fp-units-fcl fp-units-fv 
fp-units-gtk2 fp-units-db fp-units-gfx fp-units-net fp-units-math fp-units-misc 
fp-units-multimedia fp-units-i386
Architecture: source
Version: 3.0.4+dfsg-15
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Abou Al Montacir 
Description:
 fp-compiler - Free Pascal - compiler dependency package
 fp-compiler-3.0.4 - Free Pascal - compiler
 fp-docs- Free Pascal - 

Bug#889006: dh-autoreconf is run before patching

[Niels Thykier]

Sven Joachim:
> On 2018-02-02 06:55 +0200, Adrian Bunk wrote:
> 
>> On Thu, Feb 01, 2018 at 07:01:00PM +, Niels Thykier wrote:
>>> ...
>>> Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
>>> we need to handle backports as well and that puts quilt back the table
>>> as well.  I am not quite sure that I want to backport quilt and dpatch
>>> to provide further debhelper backports.
>>
>> Why not?
>>
>> dpatch is a mostly obsolete Debian native package,
>> most recent upload 2015.
> 
> Moreover, dansguardian seems to be the only package which actually uses
> dh with the dpatch addon.  Apparently all other packages stuck with
> dpatch still use classic debhelper and not dh.
> 

If we are down to that level, then fixing dpatch in sid and moving on is
probably sufficient (among other, because dansguardian does not have a
history of being backported).

@Gergely: Are you ok with a (possible 0-day) NMU for tweaking the dpatch
sequence?  I am happy to test and include the proposed the patch for
#868978 as well while I am doing the upload. :)

>> quilt still has some upstream development, but nothing big.
>>
>> It might still be easier to revert the change in dh-autoreconf,
>> but dpatch and quilt are not packages where I would see any
>> potential problems with making and supporting a backport.
> 
> Fortunately there is already a backport of quilt for stretch, and adding
> a "Breaks: quilt (<< 0.63-8.2~)" to debhelper or dh-autoreconf looks
> reasonable to me.
> 
> Cheers,
>Sven
> 

Indeed, there is now a quilt backport with can solve that part with a
Breaks. :)

Thanks,
~Niels

Bug#885935: marked as done (python-pysodium depends on cruft package libsodium18)

[Debian Bug Tracking System]

Your message dated Sat, 03 Feb 2018 09:19:51 +
with message-id 
and subject line Bug#885935: fixed in pysodium 0.7.0-1
has caused the Debian Bug report #885935,
regarding python-pysodium depends on cruft package libsodium18
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.)


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

package: pysodium
severity: serious

libsodium18 has been replaced by libsodium23, python-pysodium and 
python3-pysodium still depends on libsodium18.

I have not checked whether a simple no-change rebuild and upload is all that is 
needed or if further changes are required but either way since the package is 
arch all a sourceful upload is needed.
--- End Message ---
--- Begin Message ---
Source: pysodium
Source-Version: 0.7.0-1

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated pysodium package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 02 Feb 2018 22:55:18 +
Source: pysodium
Binary: python-pysodium python3-pysodium
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christopher Hoskin 
Description:
 python-pysodium - Python libsodium wrapper (Python2 version)
 python3-pysodium - Python libsodium wrapper (Python3 version)
Closes: 885935
Changes:
 pysodium (0.7.0-1) unstable; urgency=medium
 .
   * Add upstream signing key
   * New upstream release (0.7.0)
   * Fix "python-pysodium depends on cruft package libsodium18" Updated
 dependency to libsodium23 (Closes: #885935)
   * Remove trailing whitespace from debian/control and debian/rules
   * Use secure uri in debian/watch
   * Bump debhelper compat from 9 to 11
   * Bump Standards-Version from 4.0.0 to 4.1.3 (no change required)
Checksums-Sha1:
 192a02f54939eae414bd7c9e83abba00d8fc48d9 2434 pysodium_0.7.0-1.dsc
 009c783943a089dc56120bf51fb425d6fb3bdaef 16827 pysodium_0.7.0.orig.tar.gz
 d788fdfe1074fc8d0ca87f37855dca023dc57528 801 pysodium_0.7.0.orig.tar.gz.asc
 9db79bf426f54678b462bbd9bcf0573853d3cac9 8628 pysodium_0.7.0-1.debian.tar.xz
 5376aa87420b5d12867f8a5ebaadc00339e9d364 6354 pysodium_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 01ea752f81152accb09a62efbc04d235bfeb7e4779c0d50708d530505b92c9c2 2434 
pysodium_0.7.0-1.dsc
 80f0969dbb099aed2d3149dcdd3c9ff1476e6c168df0de2d70148aec766ab475 16827 
pysodium_0.7.0.orig.tar.gz
 7d3f814fbf938b830a93a817afc4b8d284398778aef71298e46ebd58dc743286 801 
pysodium_0.7.0.orig.tar.gz.asc
 1d1b717c06508272f673efeecbe70222ed9f4094e5d594d76933d8335d81bd9f 8628 
pysodium_0.7.0-1.debian.tar.xz
 2f8ba964190bc620476a5fa53e2be76518840a5ce60eb057b093f945da101256 6354 
pysodium_0.7.0-1_amd64.buildinfo
Files:
 1a2cdd4d268986cc0fe030276b87d899 2434 python optional pysodium_0.7.0-1.dsc
 2ba95529a6629e7105f51864d701119c 16827 python optional 
pysodium_0.7.0.orig.tar.gz
 6d23cee3df94134fa5d5372213556391 801 python optional 
pysodium_0.7.0.orig.tar.gz.asc
 0bbed1cd31e8bc673a752452fae184b7 8628 python optional 
pysodium_0.7.0-1.debian.tar.xz
 405c746b759a9e26fee6848f70ef0688 6354 python optional 
pysodium_0.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAlp1eQ4ACgkQf6qUsnUU
SpqRbw//Y1H4KWt6CnItK8RXKcMdEwVwRfyJaPFhGTsbVbiHiXdfSsgqrcxvIS87
MhEPK9JtYdjMqJ5G7JQ07UQpkC/lgbtTvGfPC5YZtzCh4HiPwUEKwQ9+q4ZH9BZ+
RFbyIimS2Jz2V474akqoo4CsllGITUqUW8lSaK7U6t6HWPMka5Bb/AvhPxkPXy4w
xOFxgm7qDus2vY8dWn6WV61MomVVwdCft8vvIEAkA+imhl8PQCUvBxponO4nKXBs
HU+g01HXQrnVAUsgCwtzPOIOIX3P6wJzVJjF9UxiMf/oTMQtDT7ZBkg5264cQpb4
3BTfjMHAKaoKPNj1Glk+6tlb1dSypJ4ahz0A4a2Xhky0uNnUdtD1Tifg/VfI4R+k
KauaXir1RqUGwSJikc0WiJEVzl7cbUzMqhZJwKUttCpLMl6rCawNQxAQxuFFp1sq
b2VqDyRFLVTu48qvHR/DEJ9URa3sv6beBwOgTbPIj7O7ZPXHiCkuCDI0Nmx7W4Q5

Bug#889278: ruby-filepath FTBFS with Ruby 2.5

[Adrian Bunk]

Source: ruby-filepath
Version: 0.6-3
Severity: serious
Tags: buster sid

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

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-filepath-0.6/debian/ruby-filepath/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-filepath/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1917:in `[]': No such 
device or address - spec/fixtures/s1 (Errno::ENXIO)
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1917:in 
`get_matching_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1911:in 
`gather_directories'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1892:in 
`block in get_files_to_run'
from /usr/lib/ruby/vendor_ruby/rspec/core/flat_map.rb:7:in `each'
from /usr/lib/ruby/vendor_ruby/rspec/core/flat_map.rb:7:in `flat_map'
from /usr/lib/ruby/vendor_ruby/rspec/core/flat_map.rb:7:in `flat_map'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1890:in 
`get_files_to_run'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:928:in 
`files_to_run'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb 
failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-filepath-0.6/debian/ruby-filepath returned exit code 1
debian/rules:18: recipe for target 'binary' failed
make: *** [binary] Error 1