Processed: Pending fixes for bugs in the clojure package

[Debian Bug Tracking System]

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

> tag 850774 + pending
Bug #850774 [libclojure-java] libclojure-java: fails to upgrade squeeze -> 
wheezy -> jessie -> stretch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#850774: Pending fixes for bugs in the clojure package

[pkg-java-maintainers]

tag 850774 + pending
thanks

Some bugs in the clojure package are closed in revision
2dc532d83260e03b579be6375cc3edc22f050d73 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/clojure.git/commit/?id=2dc532d

Commit message:

Added Breaks/Replaces clojure (<< 1.8) to libclojure-java (Closes: #850774)

Bug#850794: storaged: build-depends on removed libstoragemgmt

[Andreas Beckmann]

Source: storaged
Version: 2.6.2-1
Severity: serious
Justification: fails to build from source

storaged can no longer be built since libstoragemgmt was removed from
the archive, see https://bugs.debian.org/849670 for details on the
removal.


Andreas

Bug#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Emmanuel Bourg]

I'm unable to reproduce this issue. The pom file
build/debian/easybind.pom should be generated automatically, this
feature was added to gradle-debian-helper 1.4.

Santiago could you post the full build log please? I'd like to check the
versions of gradle and gradle-debian-helper used.

Thank you,

Emmanuel Bourg

Bug#850774: marked as done (libclojure-java: fails to upgrade squeeze -> wheezy -> jessie -> stretch)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:03:50 +
with message-id 
and subject line Bug#850774: fixed in clojure 1.8.0-2
has caused the Debian Bug report #850774,
regarding libclojure-java: fails to upgrade squeeze -> wheezy -> jessie -> 
stretch
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.)


-- 
850774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclojure-java
Version: 1.8.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + clojure

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze' to 'wheezy' to 'jessie' to 'stretch'.
It installed fine in 'squeeze', and upgraded to 'wheezy' and 'jessie'
successfully, but then the upgrade to 'stretch' failed.

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

  Selecting previously unselected package libclojure-java.
  Preparing to unpack .../libclojure-java_1.8.0-1_all.deb ...
  Unpacking libclojure-java (1.8.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libclojure-java_1.8.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/java/clojure.jar', which is also in package 
clojure 1.1.0+dfsg-1


cheers,

Andreas


clojure_1.8.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: clojure
Source-Version: 1.8.0-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated clojure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 09:45:44 +0100
Source: clojure
Binary: clojure libclojure-java
Architecture: source all
Version: 1.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 clojure- Lisp dialect for the JVM
 libclojure-java - Lisp dialect for the JVM (library)
Closes: 850774
Changes:
 clojure (1.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Added Breaks/Replaces clojure (<< 1.8) to libclojure-java (Closes: #850774)
Checksums-Sha1:
 a5e402074601fac3532c2ecbaaf6f63c26925f50 2047 clojure_1.8.0-2.dsc
 a71c621ecdb887cf99ef1922eb927dce24661f3b 12408 clojure_1.8.0-2.debian.tar.xz
 b3472b895bc0c679b6b4722bb646a017d07b56ff 46616 clojure_1.8.0-2_all.deb
 7d819cd5511abde3bcfc9d339cc66f8fe9ea4f00 9705 clojure_1.8.0-2_amd64.buildinfo
 8479d0a6d5fcc4a9ffdfddbab58c73c2f021d93b 3218050 
libclojure-java_1.8.0-2_all.deb
Checksums-Sha256:
 dbbaa5f39d6b37ea1c000762420ee0237503a40ff7084c0a421d6c52373f7dde 2047 
clojure_1.8.0-2.dsc
 86a6be444792340c258419fb08ad6eb5519c5aa11be9eb2524b4616d1c4e6f9b 12408 
clojure_1.8.0-2.debian.tar.xz
 f62eed35fb4e04a9144ce747f83dece26649137fcf8f65df9ab69b41cfb52fd3 46616 
clojure_1.8.0-2_all.deb
 ff1fa1aff5e9cc235806f777f4f6127280497ea65c7b26aa0a914bd56322f20f 9705 
clojure_1.8.0-2_amd64.buildinfo
 f7c278cdd026d925d428fe973736e05e18e0ce27e1d6e8db6d619898666ecb07 3218050 
libclojure-java_1.8.0-2_all.deb
Files:
 27109ca2461eb3495cf2ac7197a02833 2047 devel optional clojure_1.8.0-2.dsc
 48b4d48fb489c892a7026c3d62db61fa 12408 devel optional 
clojure_1.8.0-2.debian.tar.xz
 9ac2dce4ee036570c54fe5823c724a71 46616 devel optional clojure_1.8.0-2_all.deb
 93fa77859f151a4f0dc1b4fda8180316 9705 devel optional 
clojure_1.8.0-2_amd64.buildinfo
 be277464d0ba778b3ef549917998bc01 3218050 java optional 
libclojure-java_1.8.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlh0n5MACgkQ9RPEGeS5
0KzwZQ//T+4CbZFy1WW2NI+I3uti6tPaEv8xj6C0q1Y9lvnSPZf/qY7l/emdb9YM
Sa0TZZT/cg7OzleMOje70RZyONQP5v9dYOzu3HFiE6Eee09VrfyNZw2/2JAwWx8m
HocrPTaDB6yhMvVx21i7uQZzhSkHiq2Em28ItTZTD1YoFYTfwZL1oQmgKSMAkZY0
LMFJLmTGDwt06CSfvJMv1SGYJwnZpeQShD79Ovfbk11kvYezC0qwmMTnLo6vHjL2
ZPH8LWrdcoP40K/Zc5pmzAlXSznPeq/1CPLpMliwm7L3vxjIEpoXDbn8saVTJey4
yhQXKrhJGYPVQ47pUgRV4jp+qJRy4aC8p6Hm73PXc1xeQ7xmoNZPTNooQZxfN75r
S3JCKgkPVE5x8jyN6fl0ffBL7BVhQaJ6B7LkeKSznNtegccuzeecS/L7V6oOPAHd
bEE6+Nuxta1IjNwsDHMC

Bug#850022: marked as done (jstest-gtk: Does Not Open)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:04:48 +
with message-id 
and subject line Bug#850569: fixed in jstest-gtk 0.1.1~git20160825-2
has caused the Debian Bug report #850569,
regarding jstest-gtk: Does Not Open
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.)


-- 
850569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jstest-gtk
Version: 0.1.1~git20160825-1
Severity: grave
Justification: renders package unusable


Does not open. Error in terminal is can not load file /usr/bin/data/generic.png

If I create a sym link like this;

sudo ln -s /usr/share/jstest-gtk/data /usr/bin/ 
It will open as expected.



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

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

Versions of packages jstest-gtk depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libc6   2.24-8
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libgcc1 1:6.2.1-5
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgtkmm-2.4-1v51:2.24.5-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.1-5
ii  libx11-62:1.6.4-2

Versions of packages jstest-gtk recommends:
ii  joystick  1:1.6.0-1

jstest-gtk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jstest-gtk
Source-Version: 0.1.1~git20160825-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated jstest-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 09:08:01 +0100
Source: jstest-gtk
Binary: jstest-gtk
Architecture: source
Version: 0.1.1~git20160825-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 jstest-gtk - joystick testing and configuration tool
Closes: 850022 850569
Changes:
 jstest-gtk (0.1.1~git20160825-2) unstable; urgency=medium
 .
   * Hard-code the data directory instead of relying on binreloc
 (closes: #850022, #850569).
   * Enable all hardening options.
Checksums-Sha1:
 7ddb0c62c5827a6ab3adb6c52c0c94e705801381 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 237c64547ccf705485cf6129aea6c8fbf9cf06e4 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Checksums-Sha256:
 cef75e034dab5269ac19cb5ceb23a5204c155b42d7b65dfafc10f3319bf25905 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 8d06f7755409ce33ffcf24f2c0906667a8cdc6edcbee806f480b071c6d76ec5d 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Files:
 58f51b761aebf60477459206e82e9732 2103 utils optional 
jstest-gtk_0.1.1~git20160825-2.dsc
 7cc3ef0c76330f52b3a369002d89b10d 5020 utils optional 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlh0loMACgkQgNMC9Yht
g5y21xAAhizVDkaurhZQdu/Qhk98ksb2gVhhDeJU13k113U4gd/kdX36tqx/uc5f
N+w04EM5WI1h3mbFIc6X4XeSzoRbbdjLqPDVrK/+ShcX2hUBSd/UB8/LJ96u1Wsy
EBfVCBHzBAdZMfZ0PhLdZHrMOllidHa0u9XPazILXo5hgkbzYIy5kDaB64VJfywo
yUjkccwXP3DbbAS5l4jAC1smCiv2mOZlVb1IvQBAYZxtzTtsyfXOaQDqRepbQL5U
Mkbinh+bZKLRbkeI/Wlfzn3YoboAAOWyXY3PB6Wy/7AT6gI5NBIIVNWRQ/blglDp
Zzrgn3kumlx21TE2BEN40VLASLVHwRhoXQGHJYkD27eIpzrKjN9ekbzjHEOeOZMM
dA+DNsRghzgdvH1bEWcbh8+ixtFtGP5MDRhUlv0+vEx3Xh96fK8k6DCOy+BA92dt
WdcToObSen5xCUDSQDMx3ozuBJftYGO+I8PXw08ivqupHxfTHyQY7F2ppCleK0c+
+U0MCYAwDg7DtY5BQ5IYnPTmJWgBH4bmaB6x3V2VQn/Ez5UYT95uK9r+vN1cNc/P
O8mSS92/541S+crMszbRkgL1tLNRzfWqS2K4XFGm/kfw//Mddl8sf0HFGAudnp7a
9WUw71/0NcUmB6RYEHJBsy8KNZkIEP9NhXhSjYvJawN582LZ/tE=
=tT75
-END PGP SIGNATURE End Message ---

Bug#850767: marked as done (r-bioc-phyloseq: unsatisfiable Depends: r-cran-ade4 (>= 1.7.4))

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:07:43 +
with message-id 
and subject line Bug#850767: fixed in r-bioc-phyloseq 1.19.1-2
has caused the Debian Bug report #850767,
regarding r-bioc-phyloseq: unsatisfiable Depends: r-cran-ade4 (>= 1.7.4)
to be marked as done.

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

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


-- 
850767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-bioc-phyloseq
Version: 1.19.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to install due
to unsatisfiably dependency.

sid has r-cran-ade4 1.7-5-1 and stretch has 1.7-4-1
=> possily punctuation typo


Andreas
--- End Message ---
--- Begin Message ---
Source: r-bioc-phyloseq
Source-Version: 1.19.1-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-phyloseq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 09:31:39 +0100
Source: r-bioc-phyloseq
Binary: r-bioc-phyloseq
Architecture: source all
Version: 1.19.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 r-bioc-phyloseq - GNU R handling and analysis of high-throughput microbiome 
census
Closes: 850767
Changes:
 r-bioc-phyloseq (1.19.1-2) unstable; urgency=medium
 .
   * Fix versioned depends from r-cran-ade4
 Closes: #850767
Checksums-Sha1:
 28a73619a4786bf58f535d026ed3d04b7d2fb7db 2298 r-bioc-phyloseq_1.19.1-2.dsc
 6650ca7435c005a7a1967c624848bd5abb225b73 13388 
r-bioc-phyloseq_1.19.1-2.debian.tar.xz
 7b07d9e97bab548cb3df3ac095c37825bcdf305d 3104584 
r-bioc-phyloseq_1.19.1-2_all.deb
 188781338606215d3d4911c445388e43898de590 8899 
r-bioc-phyloseq_1.19.1-2_amd64.buildinfo
Checksums-Sha256:
 9c5a2500c01bc891cfa6a25a0e41cccda989bd2f16204324d14e200019dc6213 2298 
r-bioc-phyloseq_1.19.1-2.dsc
 6afa826419a6780d421dace0dccfa30b371e2026de32e174bced5054a124cb08 13388 
r-bioc-phyloseq_1.19.1-2.debian.tar.xz
 df7cfb7b327b02b3de294bb4c584ae6963861a1b9fa529eb9c07ecbdf6b2a8ed 3104584 
r-bioc-phyloseq_1.19.1-2_all.deb
 19e18e173af33c8c19bb5967cb41bc3e924bbfbd2b72092c8b034af331be68d3 8899 
r-bioc-phyloseq_1.19.1-2_amd64.buildinfo
Files:
 10477db2e621f09052c2cb22e9833955 2298 gnu-r optional 
r-bioc-phyloseq_1.19.1-2.dsc
 badf9c1db7941472ca93c939ae574604 13388 gnu-r optional 
r-bioc-phyloseq_1.19.1-2.debian.tar.xz
 7e7518f3a04e5f08312680b3a78d8a46 3104584 gnu-r optional 
r-bioc-phyloseq_1.19.1-2_all.deb
 2be19ee8aa4aa18bf135623ca91f4071 8899 gnu-r optional 
r-bioc-phyloseq_1.19.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYdJ0RAAoJEFeKBJTRxkbRtncP/RxFJcV7cMi/rJKWh0VTDWRb
GAHrnvGbNVlZ9eRj2fsJsWCT5SZ0Jscms1fsoThrS1KxOcjYhxiVSqLOCeAXIV+P
OWHDGPsbkGTzge8iL2PTn9NPKcPd6pTrxGU8Hw/tDZjmPMd/SKXkG0cC/bXykOGK
WncRzC7gsHH4wfXXNW1i89BkQRSjRfET8pjDFyPKJaZd/mwfpK4wbOxGWmA/IP/W
qeG+s9+iv5YvtgWfjoXi5L/Dv2DWBFkO2uM/ZfHsUdeiQAjasyhn3mWG0NhqFWbx
JdgPJ/Si8560ocVChzbgFhM6WAiOGcUHXtY3k+g7cawybgjG6O9OIrF9cF9i7xoP
0oOqPBqv3HdRHQ5zZW3fM2zCKoO8dvuBpKxYk9F0WNQkPEiStN5IBkh33mwFViuQ
T3WiIiEdbXK9LgrqcTS5OwbaMg1JBTeDUMeuptWHiVgLQ3jPxjJ4wk8BNsMnJ1ln
gqhhCD9cWZkQzpeXeWoPD+KfFNVLfG4gn+YZaKiTav+5fAh2HAWNQcUi2fsicMUO
nn0+vYEBwJ3T9DnWWT4+7GM1bFHMZjHg0UQATPerHC2QzXildZGBP/6awKzq+bsG
/BJaUhOkqJI3Dvr82lqfGzTV1KRHrx+UpkDmeRaaqwAU1x2m1dJz+sXaKXoZjMje
bTm/yQdkOejIqEvV6EfM
=rFhs
-END PGP SIGNATURE End Message ---

Bug#850569: marked as done (jstest-gtk: Crash for missing data files)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:04:48 +
with message-id 
and subject line Bug#850022: fixed in jstest-gtk 0.1.1~git20160825-2
has caused the Debian Bug report #850022,
regarding jstest-gtk: Crash for missing data files
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.)


-- 
850022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jstest-gtk
Version: 0.1.1~git20160825-1
Severity: important

Starting jstest-gtk with a PS3 controller connected crashes the application with
the following message:

  Error: Failed to open file '/usr/bin/data/PS3.png': No such file or directory

If I start the app with a disconnected controller, an unhandled exception error
is shown after connecting the controller and clicking refresh.

It seems like the program is calculating the data path from its main program's
basename. This is useful for running from the build directory, but does not
follow the installation structure (the missing file is installed at
/usr/share/jstest-gtk/data/PS3.png).


Thanks,
  Lluis


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

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

Versions of packages jstest-gtk depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libc6   2.24-8
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libgcc1 1:6.2.1-5
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgtkmm-2.4-1v51:2.24.5-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.1-5
ii  libx11-62:1.6.4-2

Versions of packages jstest-gtk recommends:
ii  joystick  1:1.6.0-1

jstest-gtk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jstest-gtk
Source-Version: 0.1.1~git20160825-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated jstest-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 09:08:01 +0100
Source: jstest-gtk
Binary: jstest-gtk
Architecture: source
Version: 0.1.1~git20160825-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 jstest-gtk - joystick testing and configuration tool
Closes: 850022 850569
Changes:
 jstest-gtk (0.1.1~git20160825-2) unstable; urgency=medium
 .
   * Hard-code the data directory instead of relying on binreloc
 (closes: #850022, #850569).
   * Enable all hardening options.
Checksums-Sha1:
 7ddb0c62c5827a6ab3adb6c52c0c94e705801381 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 237c64547ccf705485cf6129aea6c8fbf9cf06e4 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Checksums-Sha256:
 cef75e034dab5269ac19cb5ceb23a5204c155b42d7b65dfafc10f3319bf25905 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 8d06f7755409ce33ffcf24f2c0906667a8cdc6edcbee806f480b071c6d76ec5d 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Files:
 58f51b761aebf60477459206e82e9732 2103 utils optional 
jstest-gtk_0.1.1~git20160825-2.dsc
 7cc3ef0c76330f52b3a369002d89b10d 5020 utils optional 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlh0loMACgkQgNMC9Yht
g5y21xAAhizVDkaurhZQdu/Qhk98ksb2gVhhDeJU13k113U4gd/kdX36tqx/uc5f
N+w04EM5WI1h3mbFIc6X4XeSzoRbbdjLqPDVrK/+ShcX2hUBSd/UB8/LJ96u1Wsy
EBfVCBHzBAdZMfZ0PhLdZHrMOllidHa0u9XPazILXo5hgkbzYIy5kDaB64VJfywo
yUjkccwXP3DbbAS5l4jAC1smCiv2mOZlVb1IvQBAYZxtzTtsyfXOaQDqRepbQL5U
Mkbinh+bZKLRbkeI/Wlfzn3YoboAAOWyXY3PB6Wy/7AT6gI5NBIIVNWRQ/blglDp
Zzrgn3kumlx21TE2BEN40VLASLVHwRhoXQGHJYkD27eIpzrKjN9ekbzjHEOeOZMM
dA+DNsRghzgdvH1bEWcbh8+ixtFtGP5MDRhUlv0+vEx3Xh96fK8k6DCOy+BA92dt
WdcToObSen5xCUDSQDMx3ozuBJftYGO+I8PXw08ivqupHxfTHyQY7F

Bug#850569: marked as done (jstest-gtk: Crash for missing data files)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:04:48 +
with message-id 
and subject line Bug#850569: fixed in jstest-gtk 0.1.1~git20160825-2
has caused the Debian Bug report #850569,
regarding jstest-gtk: Crash for missing data files
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.)


-- 
850569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jstest-gtk
Version: 0.1.1~git20160825-1
Severity: important

Starting jstest-gtk with a PS3 controller connected crashes the application with
the following message:

  Error: Failed to open file '/usr/bin/data/PS3.png': No such file or directory

If I start the app with a disconnected controller, an unhandled exception error
is shown after connecting the controller and clicking refresh.

It seems like the program is calculating the data path from its main program's
basename. This is useful for running from the build directory, but does not
follow the installation structure (the missing file is installed at
/usr/share/jstest-gtk/data/PS3.png).


Thanks,
  Lluis


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

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

Versions of packages jstest-gtk depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libc6   2.24-8
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libgcc1 1:6.2.1-5
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgtkmm-2.4-1v51:2.24.5-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.1-5
ii  libx11-62:1.6.4-2

Versions of packages jstest-gtk recommends:
ii  joystick  1:1.6.0-1

jstest-gtk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jstest-gtk
Source-Version: 0.1.1~git20160825-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated jstest-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 09:08:01 +0100
Source: jstest-gtk
Binary: jstest-gtk
Architecture: source
Version: 0.1.1~git20160825-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 jstest-gtk - joystick testing and configuration tool
Closes: 850022 850569
Changes:
 jstest-gtk (0.1.1~git20160825-2) unstable; urgency=medium
 .
   * Hard-code the data directory instead of relying on binreloc
 (closes: #850022, #850569).
   * Enable all hardening options.
Checksums-Sha1:
 7ddb0c62c5827a6ab3adb6c52c0c94e705801381 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 237c64547ccf705485cf6129aea6c8fbf9cf06e4 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Checksums-Sha256:
 cef75e034dab5269ac19cb5ceb23a5204c155b42d7b65dfafc10f3319bf25905 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 8d06f7755409ce33ffcf24f2c0906667a8cdc6edcbee806f480b071c6d76ec5d 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Files:
 58f51b761aebf60477459206e82e9732 2103 utils optional 
jstest-gtk_0.1.1~git20160825-2.dsc
 7cc3ef0c76330f52b3a369002d89b10d 5020 utils optional 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlh0loMACgkQgNMC9Yht
g5y21xAAhizVDkaurhZQdu/Qhk98ksb2gVhhDeJU13k113U4gd/kdX36tqx/uc5f
N+w04EM5WI1h3mbFIc6X4XeSzoRbbdjLqPDVrK/+ShcX2hUBSd/UB8/LJ96u1Wsy
EBfVCBHzBAdZMfZ0PhLdZHrMOllidHa0u9XPazILXo5hgkbzYIy5kDaB64VJfywo
yUjkccwXP3DbbAS5l4jAC1smCiv2mOZlVb1IvQBAYZxtzTtsyfXOaQDqRepbQL5U
Mkbinh+bZKLRbkeI/Wlfzn3YoboAAOWyXY3PB6Wy/7AT6gI5NBIIVNWRQ/blglDp
Zzrgn3kumlx21TE2BEN40VLASLVHwRhoXQGHJYkD27eIpzrKjN9ekbzjHEOeOZMM
dA+DNsRghzgdvH1bEWcbh8+ixtFtGP5MDRhUlv0+vEx3Xh96fK8k6DCOy+BA92dt
WdcToObSen5xCUDSQDMx3ozuBJftYGO+I8PXw08ivqupHxfTHyQY7F

Bug#850022: marked as done (jstest-gtk: Does Not Open)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:04:48 +
with message-id 
and subject line Bug#850022: fixed in jstest-gtk 0.1.1~git20160825-2
has caused the Debian Bug report #850022,
regarding jstest-gtk: Does Not Open
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.)


-- 
850022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jstest-gtk
Version: 0.1.1~git20160825-1
Severity: grave
Justification: renders package unusable


Does not open. Error in terminal is can not load file /usr/bin/data/generic.png

If I create a sym link like this;

sudo ln -s /usr/share/jstest-gtk/data /usr/bin/ 
It will open as expected.



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

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

Versions of packages jstest-gtk depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libc6   2.24-8
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libgcc1 1:6.2.1-5
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgtkmm-2.4-1v51:2.24.5-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.1-5
ii  libx11-62:1.6.4-2

Versions of packages jstest-gtk recommends:
ii  joystick  1:1.6.0-1

jstest-gtk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jstest-gtk
Source-Version: 0.1.1~git20160825-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated jstest-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 09:08:01 +0100
Source: jstest-gtk
Binary: jstest-gtk
Architecture: source
Version: 0.1.1~git20160825-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 jstest-gtk - joystick testing and configuration tool
Closes: 850022 850569
Changes:
 jstest-gtk (0.1.1~git20160825-2) unstable; urgency=medium
 .
   * Hard-code the data directory instead of relying on binreloc
 (closes: #850022, #850569).
   * Enable all hardening options.
Checksums-Sha1:
 7ddb0c62c5827a6ab3adb6c52c0c94e705801381 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 237c64547ccf705485cf6129aea6c8fbf9cf06e4 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Checksums-Sha256:
 cef75e034dab5269ac19cb5ceb23a5204c155b42d7b65dfafc10f3319bf25905 2103 
jstest-gtk_0.1.1~git20160825-2.dsc
 8d06f7755409ce33ffcf24f2c0906667a8cdc6edcbee806f480b071c6d76ec5d 5020 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz
Files:
 58f51b761aebf60477459206e82e9732 2103 utils optional 
jstest-gtk_0.1.1~git20160825-2.dsc
 7cc3ef0c76330f52b3a369002d89b10d 5020 utils optional 
jstest-gtk_0.1.1~git20160825-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlh0loMACgkQgNMC9Yht
g5y21xAAhizVDkaurhZQdu/Qhk98ksb2gVhhDeJU13k113U4gd/kdX36tqx/uc5f
N+w04EM5WI1h3mbFIc6X4XeSzoRbbdjLqPDVrK/+ShcX2hUBSd/UB8/LJ96u1Wsy
EBfVCBHzBAdZMfZ0PhLdZHrMOllidHa0u9XPazILXo5hgkbzYIy5kDaB64VJfywo
yUjkccwXP3DbbAS5l4jAC1smCiv2mOZlVb1IvQBAYZxtzTtsyfXOaQDqRepbQL5U
Mkbinh+bZKLRbkeI/Wlfzn3YoboAAOWyXY3PB6Wy/7AT6gI5NBIIVNWRQ/blglDp
Zzrgn3kumlx21TE2BEN40VLASLVHwRhoXQGHJYkD27eIpzrKjN9ekbzjHEOeOZMM
dA+DNsRghzgdvH1bEWcbh8+ixtFtGP5MDRhUlv0+vEx3Xh96fK8k6DCOy+BA92dt
WdcToObSen5xCUDSQDMx3ozuBJftYGO+I8PXw08ivqupHxfTHyQY7F2ppCleK0c+
+U0MCYAwDg7DtY5BQ5IYnPTmJWgBH4bmaB6x3V2VQn/Ez5UYT95uK9r+vN1cNc/P
O8mSS92/541S+crMszbRkgL1tLNRzfWqS2K4XFGm/kfw//Mddl8sf0HFGAudnp7a
9WUw71/0NcUmB6RYEHJBsy8KNZkIEP9NhXhSjYvJawN582LZ/tE=
=tT75
-END PGP SIGNATURE End Message ---

Bug#787552: [eclipse-wtp][FTBFS][LICENSE Problem] Multiple distribution problem

[Emmanuel Bourg]

control: severity -1 normal

The build failure caused by JFlex has been fixed. I don't think there is
a license issue with the rsc files but for clarity it would be good to
explain this in debian/copyright.

Processed: Re: Bug#787552: [eclipse-wtp][FTBFS][LICENSE Problem] Multiple distribution problem

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #787552 [eclipse-wtp] [eclipse-wtp][FTBFS][LICENSE Problem] Multiple 
distribution problem
Severity set to 'normal' from 'serious'

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

Bug#850798: tika: FTBFS: Could not resolve dependencies for project org.apache.tika:tika-parsers:jar:1.5

[Chris Lamb]

Source: tika
Version: 1.5-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

tika fails to build from source in unstable/amd64:

  […]

  Adding debian:PSCProcert.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:Certplus_Root_CA_G2.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:GeoTrust_Global_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
  Adding debian:GeoTrust_Universal_CA.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:GlobalSign_Root_CA_-_R2.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
  Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:ACCVRAIZ1.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:Equifax_Secure_CA.pem
  Adding debian:ComSign_CA.pem
  Adding debian:QuoVadis_Root_CA_3_G3.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
  Adding debian:Juur-SK.pem
  Adding debian:Go_Daddy_Class_2_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:SecureTrust_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding debian:GeoTrust_Primary_Certification_Authority.pem
  Adding debian:Izenpe.com.pem
  Adding debian:GlobalSign_Root_CA_-_R3.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Entrust_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:RSA_Security_2048_v3.pem
  Adding debian:ISRG_Root_X1.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:Security_Communication_EV_RootCA1.pem
  Adding debian:OpenTrust_Root_CA_G1.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:Visa_eCommerce_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
  Adding debian:DigiCert_Trusted_Root_G4.pem
  Adding debian:Sonera_Class_2_Root_CA.pem
  Adding debian:QuoVadis_Root_CA_2_G3.pem
  Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  done.
  Setting up openjdk-8-jdk-headless:amd64 (8u111-b14-3) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript 

Bug#850794: storaged: build-depends on removed libstoragemgmt

[Andreas Henriksson]

Control: severity -1 important

Hello Andreas Beckmann,

Thanks for your bug report. The storaged package is only in experimental
though so I don't think serious is the correct severity (it's annoying
that it shows up on my personal tracking page as urgent when really
there's no urgency for experimental), thus lowering.

FYI, hopefully this will be resolved by storaged package being removed.

On Tue, Jan 10, 2017 at 09:55:44AM +0100, Andreas Beckmann wrote:
> Source: storaged
> Version: 2.6.2-1
> Severity: serious
> Justification: fails to build from source
> 
> storaged can no longer be built since libstoragemgmt was removed from
> the archive, see https://bugs.debian.org/849670 for details on the
> removal.

Some more background info if you're interested:

Upstream udisks2 and storaged maintainers are discussing merging
back together.

https://lists.freedesktop.org/archives/devkit-devel/2016-November/001764.html

Martin Pitt (DD and udisks2 upstream) is now working on cockpit and is
interested in finishing the work to get it into the archive (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820107 ).
Note that cockpit depends on storaged (currently), nothing else uses it.
Hopefully once the upstream work on merging udisks2 / storaged (and
we know which one of udisks2 and storaged we're getting rid of)
he (or pkg-utopia) will pick up the RFA of storaged if needed and update
the packaging to be in shape for an unstable upload or we can RM
storaged.

(Personally I think storaged is the better name but I'd really like
to avoid renaming the DBus interfaces and having to port everything
over but lets see what Martin and others finally decide.)

Regards,
Andreas Henriksson

Processed: Re: Bug#850794: storaged: build-depends on removed libstoragemgmt

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #850794 [src:storaged] storaged: build-depends on removed libstoragemgmt
Severity set to 'important' from 'serious'

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

Bug#848748: Sympy removal ahead

[Andreas Tille]

Hi Ole,

thanks a lot for caring!

On Tue, Jan 10, 2017 at 10:27:00AM +0100, Ole Streicher wrote:
> 
> blockdiag:
>  * has RC #848748 with no attempts to solve since opened
>(errors in build time tests)
>  * is not team maintained and has no Debian git repository
>  * (build-) depends somehow (could not find out how) on execnet

I'd recommend team maintenance in Debian Science team since the package
seems to fit.  This would enable us to apply the suggested patch (see
Message #10 in #848748 - thanks to Rebecca N. Palmer).  I'd volunteer to
move the package to Debian Science Git and will assume agreement if I
do not hear from Kouhei Maeda soon.
 
> execnet:
>  * has RC bugs #840823, #846951 and #846952 (errors in build time tests)
>  * is not team maintained
>  * is RFA
> 
> The mentioned build dependency of sympy seems to be optional (builds
> fine without it), and I also have no idea of how to solve the RC bugs in
> blockdiag and execnet. So save sympy from removal, I would propose to
> remove the dependency as long as the RC bugs remain unfixed. I can do
> that in the next days as a team upload.
> 
> Any objections here? Better proposals?

No better proposal since I have no idea how to fix those execnet bugs.
IMHO it would not really fit into Debian Science team but if there is no
agreement to move it to Debian Python Modules Team (which is usually
only given if there is an *active* Uploader behind which I'm not) we
could also try Debian Science Git - but moving it here alone is not
magically solving the issues. 

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#848653: marked as done (libsass-python: FTBFS: FAIL: test_compile_source_map (sasstests.CompileTestCase))

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 10:03:42 +
with message-id 
and subject line Bug#848653: fixed in libsass-python 0.12.3-1
has caused the Debian Bug report #848653,
regarding libsass-python: FTBFS: FAIL: test_compile_source_map 
(sasstests.CompileTestCase)
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.)


-- 
848653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsass-python
Version: 0.11.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

libsass-python fails to build from source in unstable/amd64:

  […]

  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-2.7' does not exist -- can't clean it
pybuild --clean --test-pytest -i python{version} -p 3.5
  I: pybuild base:184: python3.5 setup.py clean 
  running clean
  removing '«BUILDDIR»/.pybuild/pythonX.Y_3.5/build' (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-3.5' does not exist -- can't clean it
rm -rf .pybuild/
find . -name \*.pyc -exec rm {} \;
  rm -fr libsass.egg-info .libsass-upstream-version
  make[1]: Leaving directory '«BUILDDIR»'
 dh_clean -O--buildsystem=pybuild
rm -f debian/debhelper-build-stamp
rm -f debian/python-libsass.substvars
rm -f debian/python-libsass.*.debhelper
rm -rf debian/python-libsass/
rm -f debian/python3-libsass.substvars
rm -f debian/python3-libsass.*.debhelper
rm -rf debian/python3-libsass/
rm -f debian/pysassc.substvars
rm -f debian/pysassc.*.debhelper
rm -rf debian/pysassc/
rm -rf debian/.debhelper/
rm -f debian/*.debhelper.log
rm -f debian/files
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS \) -prune -o -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
rm -f *-stamp
   debian/rules build
  dpkg-query -f '\n' -W libsass-dev|sed 's/-.*//' > .libsass-upstream-version
  dh build --with python2,python3 --buildsystem=pybuild
 dh_testdir -O--buildsystem=pybuild
 dh_update_autotools_config -O--buildsystem=pybuild
 dh_auto_configure -O--buildsystem=pybuild
pybuild --configure --test-pytest -i python{version} -p 2.7
  I: pybuild base:184: python2.7 setup.py config 
  running config
pybuild --configure --test-pytest -i python{version} -p 3.5
  I: pybuild base:184: python3.5 setup.py config 
  running config
 debian/rules override_dh_auto_build
  make[1]: Entering directory '«BUILDDIR»'
  pybuild --build -p "2.7 3.5"
  I: pybuild base:184: /usr/bin/python3 setup.py build 
  running build
  running build_py
  copying sass.py -> «BUILDDIR»/.pybuild/pythonX.Y_3.5/build
  copying sassc.py -> «BUILDDIR»/.pybuild/pythonX.Y_3.5/build
  copying sasstests.py -> «BUILDDIR»/.pybuild/pythonX.Y_3.5/build
  creating «BUILDDIR»/.pybuild/pythonX.Y_3.5/build/sassutils
  copying sassutils/__init__.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/sassutils
  copying sassutils/wsgi.py -> «BUILDDIR»/.pybuild/pythonX.Y_3.5/build/sassutils
  copying sassutils/builder.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/sassutils
  copying sassutils/distutils.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/sassutils
  running build_ext
  building '_sass' extension
  creating build
  creating build/temp.linux-x86_64-3.5
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -g -O2 -fdebug-prefix-map=«BUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m -c pysass.cpp -o 
build/temp.linux-x86_64-3.5/pysass.o -c -O3 -fPIC -std=c++0x -Wall 
-Wno-parentheses -Werror=switch -DLIBSASS_VERSION=""
  cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
C/ObjC but not for C++
  x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix

Bug#850772: multipath-tools-boot: fails to upgrade from 'jessie' - trying to overwrite /etc/init.d/multipath-tools-boot

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tag -1 +moreinfo

On Tue, 2017-01-10 at 02:17 +0100, Andreas Beckmann wrote:
> Package: multipath-tools-boot
> Version: 0.6.4-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> 
> >From the attached log (scroll to the bottom...):
> 
>   Preparing to unpack .../multipath-tools-boot_0.6.4-1_all.deb ...
>   Unpacking multipath-tools-boot (0.6.4-1) over (0.5.0-6+deb8u2) ...
>   dpkg: error processing archive /var/cache/apt/archives/multipath-tools-
> boot_0.6.4-1_all.deb (--unpack):
>    trying to overwrite '/etc/init.d/multipath-tools-boot', which is also in
> package multipath-tools 0.5.0-6+deb8u2
>   Preparing to unpack .../multipath-tools_0.6.4-1_amd64.deb ...
>   invoke-rc.d: could not determine current runlevel
>   invoke-rc.d: policy-rc.d denied execution of stop.
>   Unpacking multipath-tools (0.6.4-1) over (0.5.0-6+deb8u2) ...
> 
> 

I am surprised that I'm not able to reproduce this locally.
Please see the terminal log.

Selecting previously unselected package librados2.
Preparing to unpack .../librados2_0.80.11-1.1_amd64.deb ...
Unpacking librados2 (0.80.11-1.1) ...
Selecting previously unselected package libsgutils2-2.
Preparing to unpack .../libsgutils2-2_1.42-2_amd64.deb ...
Unpacking libsgutils2-2 (1.42-2) ...
Selecting previously unselected package sg3-utils.
Preparing to unpack .../sg3-utils_1.42-2_amd64.deb ...
Unpacking sg3-utils (1.42-2) ...
Selecting previously unselected package sg3-utils-udev.
Preparing to unpack .../sg3-utils-udev_1.42-2_all.deb ...
Unpacking sg3-utils-udev (1.42-2) ...
Preparing to unpack .../kpartx_0.6.4-1_amd64.deb ...
Unpacking kpartx (0.6.4-1) over (0.5.0-6+deb8u2) ...
Selecting previously unselected package liburcu4:amd64.
Preparing to unpack .../liburcu4_0.9.3-1_amd64.deb ...
Unpacking liburcu4:amd64 (0.9.3-1) ...
Preparing to unpack .../multipath-tools_0.6.4-1_amd64.deb ...
Unpacking multipath-tools (0.6.4-1) over (0.5.0-6+deb8u2) ...
Preparing to unpack .../multipath-tools-boot_0.6.4-1_all.deb ...
Unpacking multipath-tools-boot (0.6.4-1) over (0.5.0-6+deb8u2) ...
Processing triggers for libc-bin (2.24-8) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for systemd (215-17+deb8u2) ...
Setting up libc-l10n (2.24-8) ...
Setting up locales (2.24-8) ...
Installing new version of config file /etc/locale.alias ...
Generating locales (this might take a while)...
  en_IN.UTF-8... done
Generation complete.
Setting up libreadline7:amd64 (7.0-1) ...
Setting up libboost-system1.61.0:amd64 (1.61.0+dfsg-3+b1) ...
Setting up libboost-thread1.61.0:amd64 (1.61.0+dfsg-3+b1) ...
Setting up libnspr4:amd64 (2:4.12-6) ...
Setting up libnss3:amd64 (2:3.26.2-1) ...
Setting up librados2 (0.80.11-1.1) ...
Setting up libsgutils2-2 (1.42-2) ...
Setting up sg3-utils (1.42-2) ...
Setting up sg3-utils-udev (1.42-2) ...
update-initramfs: deferring update (trigger activated)
Setting up kpartx (0.6.4-1) ...
Setting up liburcu4:amd64 (0.9.3-1) ...
Setting up multipath-tools (0.6.4-1) ...
Setting up multipath-tools-boot (0.6.4-1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.24-8) ...
Processing triggers for initramfs-tools (0.115) ...
update-initramfs: Generating /boot/initrd.img-3.14-2-amd64
Log ended: 2017-01-10  16:21:09

Log started: 2017-01-10  16:23:10
Selecting previously unselected package less.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 27029 files and directories currently installed.)
Preparing to unpack .../archives/less_458-3_amd64.deb ...
Unpacking less (458-3) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up less (458-3) ...
Log ended: 2017-01-10  16:23:15

> In case it does matter, this was observed during a
> wheezy->jessie->stretch upgrade test.
- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlh0vsgACgkQpjpYo/Lh
dWmnmA/9EBTUA6cDWr5YlPc2pYNldGBlzMpZngI3hhdNqaFfvsEcQaYvZM6

Processed: Re: Bug#850772: multipath-tools-boot: fails to upgrade from 'jessie' - trying to overwrite /etc/init.d/multipath-tools-boot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +moreinfo
Bug #850772 [multipath-tools-boot] multipath-tools-boot: fails to upgrade from 
'jessie' - trying to overwrite /etc/init.d/multipath-tools-boot
Added tag(s) moreinfo.

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

Processed: Pending fixes for bugs in the java-gnome package

[Debian Bug Tracking System]

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

> tag 849669 + pending
Bug #849669 [src:java-gnome] java-gnome: FTBFS on arm: dh_install: 
libjava-gnome-java-doc missing files: doc/api/
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#849669: Pending fixes for bugs in the java-gnome package

[pkg-java-maintainers]

tag 849669 + pending
thanks

Some bugs in the java-gnome package are closed in revision
7a933266320a9fbae204e477bba53206172cbeb0 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java-gnome.git/commit/?id=7a93326

Commit message:

Build with the DH sequencer instead of CDBS (Closes: #849669)

Processed: reassign 850811 to reportbug, severity of 850811 is serious

[Debian Bug Tracking System]

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

> reassign 850811 reportbug 7.1.1
Bug #850811 [reportbug 7.1.1] reportbug - crashing
Warning: Unknown package '7.1.1'
Bug reassigned from package 'reportbug 7.1.1' to 'reportbug'.
Ignoring request to alter found versions of bug #850811 to the same values 
previously set
Ignoring request to alter fixed versions of bug #850811 to the same values 
previously set
Bug #850811 [reportbug] reportbug - crashing
Marked as found in versions reportbug/7.1.1.
> severity 850811 serious
Bug #850811 [reportbug] reportbug - crashing
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#849669: marked as done (java-gnome: FTBFS on arm: dh_install: libjava-gnome-java-doc missing files: doc/api/)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 11:34:37 +
with message-id 
and subject line Bug#849669: fixed in java-gnome 4.1.3-5
has caused the Debian Bug report #849669,
regarding java-gnome: FTBFS on arm: dh_install: libjava-gnome-java-doc missing 
files: doc/api/
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.)


-- 
849669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java-gnome
Version: 4.1.3-4
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

dh_installpam -plibjava-gnome-java-doc 
dh_installlogrotate -plibjava-gnome-java-doc 
dh_installlogcheck -plibjava-gnome-java-doc 
dh_installchangelogs -plibjava-gnome-java-doc 
dh_installudev -plibjava-gnome-java-doc 
dh_lintian -plibjava-gnome-java-doc 
dh_bugfiles -plibjava-gnome-java-doc 
dh_install -plibjava-gnome-java-doc 
dh_install: Cannot find (any matches for) "doc/api/" (tried in "." and 
"debian/tmp")
dh_install: libjava-gnome-java-doc missing files: doc/api/
dh_install: missing files, aborting
/usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
'binary-install/libjava-gnome-java-doc' failed
make: *** [binary-install/libjava-gnome-java-doc] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

Full build log:
https://tests.reproducible-builds.org/debian/unstable/armhf/java-gnome
--- End Message ---
--- Begin Message ---
Source: java-gnome
Source-Version: 4.1.3-5

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated java-gnome package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 12:05:43 +0100
Source: java-gnome
Binary: libjava-gnome-java libjava-gnome-jni libjava-gnome-java-doc
Architecture: source all amd64
Version: 4.1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libjava-gnome-java - Java-gnome language bindings project
 libjava-gnome-java-doc - Java-gnome language bindings project documentation
 libjava-gnome-jni - Java-gnome language bindings project JNI layer
Closes: 779344 836100 849669
Changes:
 java-gnome (4.1.3-5) unstable; urgency=medium
 .
   * Team upload.
   * Build with the DH sequencer instead of CDBS (Closes: #849669)
   * Use dbus-run-session instead of dbus-launch to run metacity
 and depend on dbus (>= 1.8) instead of dbus-x11 (Closes: #836100)
   * Disabled parallel building (Closes: #779344)
   * Standards-Version updated to 3.9.8
   * Switch to debhelper level 10
   * Use secure Vcs-* URLs
Checksums-Sha1:
 0f68de9ddea4d81a71884a6355582c9a09742213 2489 java-gnome_4.1.3-5.dsc
 c40b1c89acf92999ee36bc628af3604685cead99 8576 java-gnome_4.1.3-5.debian.tar.xz
 9f43ba28e466f1c09e32b5c51bd918ceccb568e2 15189 
java-gnome_4.1.3-5_amd64.buildinfo
 5eab56599d8fc77f4b4ffeb1cdfa7cebbb0b6eaa 940948 
libjava-gnome-java-doc_4.1.3-5_all.deb
 f80e4d893ff8718169037066cba3fc7e486ce964 1261164 
libjava-gnome-java_4.1.3-5_all.deb
 f48a4d5d1452fcc7179764beb7c39ec6c883baf7 1180588 
libjava-gnome-jni-dbgsym_4.1.3-5_amd64.deb
 6c828436da0b2c67e5b744d9588fc085820f387d 167212 
libjava-gnome-jni_4.1.3-5_amd64.deb
Checksums-Sha256:
 c7db4cf898cde024e415a8e1135bc8e85a7f1e98d61c5c71f92e7b72e650551d 2489 
java-gnome_4.1.3-5.dsc
 7eec82661f76b9236cbe82413060b8ac0ab90cad9f31de91a054b8be51b892a3 8576 
java-gnome_4.1.3-5.debian.tar.xz
 fa0180533d13291366c2697a7874a9cfe9ce65e130dec15240bc17ec55c5b133 15189 
java-gnome_4.1.3-5_amd64.buildinfo
 f18c25e28541fc8c128209a4a001db1c6b2e9fa4a40381e7273a5ab5f0637f19 940948 
libjava-gnome-java-doc_4.1.3-5_all.deb
 256d4d0f898def673424298ccab0b6d820c4ec0abe2eaf12a432024551fc9b81 1261164 
libjava-gnome-java_4.1.3-5_all.deb
 eb2126c009a71f34d71011e79ac9c414b3ae

Bug#840831: marked as done (libvirtuoso5.5-cil: fails to install: E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 12:52:02 +0100
with message-id <20170110115159.amcu7s6c7w2k5...@mapreri.org>
and subject line Re: Bug#840831: libvirtuoso5.5-cil: fails to install: E: 
installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed
has caused the Debian Bug report #840831,
regarding libvirtuoso5.5-cil: fails to install: E: installing Assembly 
/usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed
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.)


-- 
840831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirtuoso5.5-cil
Version: 6.1.6+dfsg2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package libvirtuoso5.5-cil.
  (Reading database ... 
(Reading database ... 7366 files and directories currently installed.)
  Preparing to unpack .../libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1_amd64.deb ...
  Unpacking libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ...
  Setting up libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ...
  * Installing 1 assembly from libvirtuoso5.5-cil into Mono
  E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll 
failed
  E: Installation of libvirtuoso5.5-cil with 
/usr/share/cli-common/runtimes.d/mono failed
  dpkg: error processing package libvirtuoso5.5-cil (--configure):
   subprocess installed post-installation script returned error exit status 29
  Errors were encountered while processing:
   libvirtuoso5.5-cil

cheers,

andreas


libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Sat, Oct 15, 2016 at 01:55:28PM +0200, Andreas Beckmann wrote:
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libvirtuoso5.5-cil.
>   (Reading database ... 
> (Reading database ... 7366 files and directories currently installed.)
>   Preparing to unpack .../libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1_amd64.deb ...
>   Unpacking libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ...
>   Setting up libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ...
>   * Installing 1 assembly from libvirtuoso5.5-cil into Mono
>   E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll 
> failed
>   E: Installation of libvirtuoso5.5-cil with 
> /usr/share/cli-common/runtimes.d/mono failed
>   dpkg: error processing package libvirtuoso5.5-cil (--configure):
>subprocess installed post-installation script returned error exit status 29
>   Errors were encountered while processing:
>libvirtuoso5.5-cil

I can't reproduce it, neither piuparts can (anymore?).  Probably
something fixed elsewhere in the meantime.

Closing.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---

Processed: wand: please update dependency on imagemgick

[Debian Bug Tracking System]

Processing control commands:

> block 849218 by -1
Bug #849218 [release.debian.org] transition: imagemagick
849218 was blocked by: 844464 844558 847371 848264 844357 844227 847527
849218 was not blocking any bugs.
Added blocking bug(s) of 849218: 850815

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

Bug#850815: wand: please update dependency on imagemgick

[Mattia Rizzolo]

Source: wand
Version: 0.4.4-1
Severity: serious
Control: block 849218 by -1

Dear maintainer, wand declare these dependencies in its binaries

| Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends},
|  libmagickwand5 | libmagickwand-6.q16-2,

imagemagick is having a transition, and the soname of libmagickwand
changed, therefore the binary name changed; please update your package
accordingly.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#817414: marked as done (crypt++el: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 12:18:37 +
with message-id 
and subject line Bug#817414: fixed in crypt++el 2.94-3
has caused the Debian Bug report #817414,
regarding crypt++el: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crypt++el
Severity: important
Usertags: compat-4-removal

Hi,

The package crypt++el uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: crypt++el
Source-Version: 2.94-3

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated crypt++el package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 12:41:03 +0100
Source: crypt++el
Binary: crypt++el
Architecture: source all
Version: 2.94-3
Distribution: unstable
Urgency: medium
Maintainer: Mario Lang 
Changed-By: Christoph Martin 
Description:
 crypt++el  - Emacs-Lisp Code for handling compressed and encrypted files
Closes: 817414
Changes:
 crypt++el (2.94-3) unstable; urgency=medium
 .
   * update to debhelper >= 9 (closes: #817414)
   * update standards version to 3.9.8 - no changes
Checksums-Sha1:
 7fff6c74e891f5a3dd1d977ec14c78101d153b30 1648 crypt++el_2.94-3.dsc
 df9cef721fdb684844a4cb73cc31a1a04b197ef0 3609 crypt++el_2.94-3.diff.gz
 7f0bcd3e2da88c4bd5c599e141ae37b05205c79e 35340 crypt++el_2.94-3_all.deb
 38cced612d84da8fa6e60c687c6d0f9dfd070ea6 4997 crypt++el_2.94-3_amd64.buildinfo
Checksums-Sha256:
 d2ad6eb039fcb2b7dd4fe68e57e4271e83191112a78b6fa693189381081980d4 1648 
crypt++el_2.94-3.dsc
 0b16a478a27f2b00f30fd8bf0116ae65a716cac73297eedbcad8d6d58a51a35d 3609 
crypt++el_2.94-3.diff.gz
 394f6ace0de7a377a753a383075cf6e0be7f6dd72cbe718fbaa503450ed29efa 35340 
crypt++el_2.94-3_all.deb
 a0749034e97ef6425acf33c6f983c7bf609763e54a73b8c43c6d345683567d14 4997 
crypt++el_2.94-3_amd64.buildinfo
Files:
 12b03bce5e9379c50e8652d515bb3133 1648 editors extra crypt++el_2.94-3.dsc
 b28d8d2c4bc8419c873c32b35f566ec2 3609 editors extra crypt++el_2.94-3.diff.gz
 1261ceec9807e758a9b76996a61f183d 35340 editors extra crypt++el_2.94-3_all.deb
 a85db272a1a587f7c1912618847b0a77 4997 editors extra 
crypt++el_2.94-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYdMv7AAoJEPqBswqWsQmcw7sQAN3uHPs1aIu/+QBjrVrTmfzN
ZUf9bbgD3LAp40hGNIRSYLF1oL3Wf7bY9AXR4rTgnUEkVZJ1yzVfvSaiz2YeBqRy
gxih/T1Qs/mLqGh90syGtMalatUhP0HVIh6AaQb4VmLQSq67joYYRqK6aFpgsee1
JciG5+P+EbhZ3poUZZLi2Pi+NsOWz3uRmSL0cujF9EwMtJLeZ8kFrwzng41Sn9Aa
qEscabljoI9l2EyjHdSE4vArvNXIzexLkqsz+dHj5Qq/IgBZ/lQ14X28vGkL9Cr/
askHVgfJNnw7nTzgMljXHadaYOzSB120AmIPgEZ+rqAaIiZo5xKF88iVGELUYmpT
WfX/6woLsiZdwbgEP8Hg27TIxKiNT5MQHoDcO2lIpIvm6s76aN2hiX2oh1LGgY4x
Z+aCbbMElwtlSKOavO01D3wcCmD/WDtxWFFDQ/o+8rBjJAxp+PY8dFCsHL86oiBM
HYia4s9xqEMjnQ97Cn2gF+SNB6HsCzpY8uxo6K8Q1m3+7Yoz8ex9a7jvjyPY2u3w
zVzv0Pg1z4MbsGHdm/DgdEvy47JaG7DMTjtVKFa1nPBh7FAjMkF9a/PRLO64rLng
m511YS8aceJLDMwooyxux6x+YLrXHPengSMFlYChGWVIHDSNOAzA3P6nAjd9sUrN
Pa/OSc0B7wCilBklekoP
=L02O
-END PGP SIGNATURE End Message ---

Bug#850682: mariadb-10.0: segmentation fault after killing a query blocked on disk space availability

[Apollon Oikonomopoulos]

Apparently this is MySQL bug #69926[1], affecting MariaDB/MySQL from 5.1 
up to 10.0/5.6.

[1] https://bugs.mysql.com/bug.php?id=69926

Bug#828594: marked as done (virtuoso-opensource: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 12:19:14 +
with message-id 
and subject line Bug#828594: fixed in virtuoso-opensource 6.1.6+dfsg2-4
has caused the Debian Bug report #828594,
regarding virtuoso-opensource: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtuoso-opensource
Version: 6.1.6+dfsg2-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/virtuoso-opensource_6.1.6+dfsg2-3_amd64-20160529-1549

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: virtuoso-opensource
Source-Version: 6.1.6+dfsg2-4

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated virtuoso-opensource 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 12:56:02 +0100
Source: virtuoso-opensource
Binary: virtuoso-opensource virtuoso-server virtuoso-minimal 
virtuoso-opensource-6.1 virtuoso-opensource-6.1-common 
virtuoso-opensource-6.1-bin virtuoso-vsp-startpage virtuoso-vad-conductor 
virtuoso-vad-doc virtuoso-vad-demo virtuoso-vad-tutorial 
virtuoso-vad-rdfmappers virtuoso-vad-sparqldemo virtuoso-vad-syncml 
virtuoso-vad-bpel virtuoso-vad-isparql virtuoso-vad-ods libvirtodbc0 
libvirtuoso5.5-cil
Architecture: source
Version: 6.1.6+dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Mattia Rizzolo 
Description:
 libvirtodbc0 - high-performance database - ODBC libraries
 libvirtuoso5.5-cil - high-performance database - Mono assemblies
 virtuoso-minimal - high-performance database - core dependency package
 virtuoso-opensource - high-performance database
 virtuoso-opensource-6.1 - high-performance database - support files
 virtuoso-opensource-6.1-bin - high-performance database - binaries
 virtuoso-opensource-6.1-common - high-performance database - common files
 virtuoso-server - high-performance database - server dependency package
 virtuoso-vad-bpel - high-performance database - BPEL module
 virtuoso-vad-conductor - high-performance database - conductor module
 virtuoso-vad-demo - high-performance database - demo module
 virtuoso-vad-doc - high-performance database - documentation module
 virtuoso-vad-isparql - high-performance database - iSPARQL module
 virtuoso-vad-ods - high-performance database - Open Data Spaces module
 virtuoso-vad-rdfmappers - high-performance database - RDF mappers module
 virtuoso-vad-sparqldemo - high-performance database - SPARQL demo module
 virtuoso-vad-syncml - high-performance database - SyncML module
 virtuoso-vad-tutorial - high-performance database - tutorial module
 virtuoso-vsp-startpage - high-performance database - web interface files
Closes: 828594
Changes:
 virtuoso-opensource (6.1.6+dfsg2-4) unstable; urgency=medium
 .
   * QA upload.
   * Add patch to fix FTBFS with OpenSSL 1.1.
 Thanks to Sebastian Andrzej Siewior  for the
 patch.  Closes: #828594
   * d/control: drop make from build-deps, as it's build-essential and that
 version is old enough.
   * Bump debhelper compat level to 10.
 + --with autoreconf is now defuault.
 + --parallel is now default.
Checksums-Sha1:
 735523411cb25f6bbe0cc5ded9257de56258a021 3985 
virtuoso-open

Bug#850700: Pending fixes for bugs in the resteasy package

[pkg-java-maintainers]

tag 850700 + pending
thanks

Some bugs in the resteasy package are closed in revision
acbd6fea9a1ce60d193859dfb7b66ffbc9a5e59d in branch 'master' by
Emmanuel Bourg

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

Commit message:

Removed servlet-api-2.5.jar from the Class-Path attribute in the manifests 
(Closes: #850700)

Processed: Pending fixes for bugs in the resteasy package

[Debian Bug Tracking System]

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

> tag 850700 + pending
Bug #850700 [libresteasy-java] sid/stretch version depends on 
servlet-api-2.5.jar
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841583: (no subject)

[Cédric Boutillier]

Thanks for the report. I am investigating this bug.

Cheers,

Cédric

Bug#845905: (no subject)

[Cédric Boutillier]

Thanks for the report. I am investigating this bug.

Cheers,

Cédric

Bug#845877: marked as done (mydumper: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 13:00:43 +
with message-id 
and subject line Bug#845877: fixed in mydumper 0.9.1-2
has caused the Debian Bug report #845877,
regarding mydumper: switch to build depend on the metapackage 
default-libmysqlclient-dev
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.)


-- 
845877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mydumper
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: mydumper
Source-Version: 0.9.1-2

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

Debian distribution maintenance software
pp.
Mateusz Kijowski  (supplier of updated mydumper 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 02 Jan 2017 15:40:34 +0100
Source: mydumper
Binary: mydumper mydumper-doc
Architecture: source amd64 all
Version: 0.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Mateusz Kijowski 
Changed-By: Mateusz Kijowski 
Description:
 mydumper   - High-performance MySQL backup tool
 mydumper-doc - High-performance MySQL backup tool - documentation
Closes: 841607 845877
Changes:
 mydumper (0.9.1-2) unstable; urgency=medium
 .
   * Depend on default-libmysqlclient-dev (Closes: #845877, #841607)
   * bump standards version to 3.9.8
   * Separate doc package to comply with standards 3.9.7
   * dh compat level bumped to 9
   * changed homepage and debian/watch to github
Checksums-Sha1:
 7f7477cd71d032247f4a01f0e5ef93b1c7059588 1953 mydumper_0.9.1-2.dsc
 b603257a505af04e3a8f4f74c4f37ad0b5927a38 6332 mydumper_0.9.1-2.debian.tar.xz
 2e725c6acb0e70016387a104275afa4e133b2ea2 80952 
mydumper-dbgsym_0.9.1-2_amd64.deb
 8c06a13ff114ed158471ebd5370e999c15d52291 28690 mydumper-doc_0.9.1-2_all.deb
 b8f07f14970f926b9ffa5f98058ab19d3271fffc 7425 mydumper_0.9.1-2_amd64.buildinfo
 cc5d56b9620338787bd76afcc0863627bfb54d31 42660 mydumper_0.9.1-2_amd64.deb
Checksums-Sha256:
 c8402d86736b8eda2d50e95d85a48daf4738c6bb5fba83eebdd722df7e9eef72 1953 
mydumper_0.9.1-2.dsc
 38e5a04f78be6f68c27043be2f6e826dbb0087a070a885f052633632cd50b17a 6332 
mydumper_0.9.1-2.debian.tar.xz
 7e7386c5ad5a0655e0c148250501cfc55e5ca01f0ed2f689ffe860e0c54ba5e3 80952 
mydumper-dbgsym_0.9.1-2_amd64.deb
 6d9658b77f429926055a656494449a4e27c95c323e44530edc87b6d8392cfcc2 28690 
mydumper-doc_0.9.1-2_all.deb
 632bed6ac4a56971fb817eb748a01b752c451d3e728ffc125381f18a3fe0d30b 7425 
mydumper_0.9.1-2_amd64.buildinfo
 08f430ffd20de5cfb613c9c92c0250040182bb0d8993f149d7a2b3ff04232e4b 42660 
mydumper_0.9.1-2_amd64.deb
Files:
 0a6bcc9cee4d0fd8689c057466d1230e 1953 database extra mydumper_0.9.1-2.dsc
 36fd7f90df5d3cb01d18ea0fae796ca8 6332 database extra 
mydumper_0.9.1-2.debian.tar.xz
 14d2fc5e4844c1cbb88bcdbfdc7fe785 80952 debug extra 
mydumper-dbgsym_0.9.1-2_amd64.deb
 d4f091e4687058dec726077cd1fd2983 28690 doc extra mydumper-doc_0.9.1-2_all.deb
 46626a2607081dfac3daf5229b3f53af 7425 database extra 
mydumper_0.9.1-2_amd64.buildinfo
 853ba7b164a5948551d860145e420475 42660 database extra 
mydumper_0.9.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEK+x51vtJ+yJ4cpAbsNnUqDzTu8EFAlhvlVARHGZlbmlvQGRl
Ymlhbi5vcmcACgkQsNnUqDzTu8Er0Q//fGIq+Noqj4uJFh9UXxortf/SwrRtlTlz
Whra2uQPpFYzkCUDzCuJCz0G3hrg8C6plVB3PDqD+mNNNmsSx4ElpH5XhZQpME8I
D3H

Bug#849958: marked as done (openmolar: Does not start; missing QtWebkit)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 14:02:16 +0100
with message-id <1484053336.7044.16.ca...@gmail.com>
and subject line New upstream fixes this
has caused the Debian Bug report #849958,
regarding openmolar: Does not start; missing QtWebkit
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.)


-- 
849958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmolar
Version: 0.6.2-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Traceback (most recent call last):
  File "/usr/bin/openmolar", line 30, in 
main.run()
  File "/usr/share/openmolar/openmolar/main.py", line 122, in run
chosen_func()
  File "/usr/share/openmolar/openmolar/main.py", line 65, in main
from openmolar.qt4gui import maingui
  File "/usr/share/openmolar/openmolar/qt4gui/maingui.py", line 49, in 
from openmolar.qt4gui.fees import fees_module
  File "/usr/share/openmolar/openmolar/qt4gui/fees/fees_module.py", line 49, in 

from openmolar.qt4gui.printing import om_printing
  File "/usr/share/openmolar/openmolar/qt4gui/printing/om_printing.py", line 
63, in 
from openmolar.qt4gui.dialogs.print_record_dialog import PrintRecordDialog
  File "/usr/share/openmolar/openmolar/qt4gui/dialogs/print_record_dialog.py", 
line 26, in 
from PyQt4 import QtGui, QtCore, QtWebKit
ImportError: cannot import name QtWebKit


I also cannot find QtWebkit from PyQt4 for Python 2 in Debian.

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/lksh
Init: systemd (via /run/systemd/system)

Versions of packages openmolar depends on:
ii  python  2.7.13-1
ii  python-mysqldb  1.3.7-1+b1
ii  python-qscintilla2  2.9.3+dfsg-4
ii  python-qt4  4.11.4+dfsg-2
pn  python:any  
ii  xdg-utils   1.1.1-1

openmolar recommends no packages.

Versions of packages openmolar suggests:
pn  mysql-server | mariadb-server  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlhqhL0xGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pblQRAAoWuhLnQwud7CUzVh2t9nFtKFaWFR
ZGbSNj2qGZmh6AK3uRmKTycstXORY5v7Em2B9FCausjKxhdcXagiOpSAxwxw+YHv
AfNE1qrPlLqVC3Y0obE5tCsbw4tpDHQ6eHB2zzSTeJwNJSZvZ1SNG3FH1C+BBllh
uRZ3uAVQHG1ZSWIwR5HkQlGLrOIChhGVtRhxJwC0BOMjBp88tl573fQw2HjKKMwn
2uX+OrKN5XjgQmnRRfieP03yQEVhWJx1nJz0sXFGje9R685Z/VUJoUzXuYS20pr8
XDLSo3/IMARxfHAy6m12SyWLwvMkMjj7UhsfzBMLN0N2MVKwB+D/i3xHq27azRwQ
FWQEZGrdspGdbW8CY+tcdaw0op4rBtlLVXHaAFsQlqcOjx020i0uNkw3B1pDltaH
hTeubUw//yxx4kQCwhFLy2oZnH+mxBGSWZLVy7briz26Udo0UfywP9Ka20R1PUuc
AkzdfZkQq3J3KxZFj9o+0r4R4UjtqE+zqDlpcZ2naT+wynAG/IlQBQ6501v6zAxO
Ldjn38u5dwEuR6IEaAh4HLGW2R8ABeRvVRWCdPUZCIFK9oMh7iitJbtu+86qUkn/
WSRr8ZJyKRUVT5E+6oxs7WwUk59vXlw1zItWnzSJwiRMuj62ecEXIu/AUEVW1CI8
e+mz3luLiQnS0uY=
=tZjD
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 1.0.15-gd81f9e5-1--- End Message ---

Bug#841607: marked as done (mydumper: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 13:00:43 +
with message-id 
and subject line Bug#841607: fixed in mydumper 0.9.1-2
has caused the Debian Bug report #841607,
regarding mydumper: FTBFS: dh_auto_configure: cmake .. 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
to be marked as done.

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

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


-- 
841607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mydumper
Version: 0.9.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> make[2]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> Building CXX object CMakeFiles/cmTC_368db.dir/feature_tests.cxx.o
> /usr/bin/c++ -std=c++98 -o CMakeFiles/cmTC_368db.dir/feature_tests.cxx.o 
> -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.cxx
> Linking CXX executable cmTC_368db
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_368db.dir/link.txt 
> --verbose=1
> /usr/bin/c++CMakeFiles/cmTC_368db.dir/feature_tests.cxx.o  -o 
> cmTC_368db -rdynamic 
> make[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> make[1]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
> Feature record: CXX_FEATURE:0cxx_aggregate_default_initializers
> Feature record: CXX_FEATURE:0cxx_alias_templates
> Feature record: CXX_FEATURE:0cxx_alignas
> Feature record: CXX_FEATURE:0cxx_alignof
> Feature record: CXX_FEATURE:0cxx_attributes
> Feature record: CXX_FEATURE:0cxx_attribute_deprecated
> Feature record: CXX_FEATURE:0cxx_auto_type
> Feature record: CXX_FEATURE:0cxx_binary_literals
> Feature record: CXX_FEATURE:0cxx_constexpr
> Feature record: CXX_FEATURE:0cxx_contextual_conversions
> Feature record: CXX_FEATURE:0cxx_decltype
> Feature record: CXX_FEATURE:0cxx_decltype_auto
> Feature record: CXX_FEATURE:0cxx_decltype_incomplete_return_types
> Feature record: CXX_FEATURE:0cxx_default_function_template_args
> Feature record: CXX_FEATURE:0cxx_defaulted_functions
> Feature record: CXX_FEATURE:0cxx_defaulted_move_initializers
> Feature record: CXX_FEATURE:0cxx_delegating_constructors
> Feature record: CXX_FEATURE:0cxx_deleted_functions
> Feature record: CXX_FEATURE:0cxx_digit_separators
> Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
> Feature record: CXX_FEATURE:0cxx_explicit_conversions
> Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
> Feature record: CXX_FEATURE:0cxx_extern_templates
> Feature record: CXX_FEATURE:0cxx_final
> Feature record: CXX_FEATURE:0cxx_func_identifier
> Feature record: CXX_FEATURE:0cxx_generalized_initializers
> Feature record: CXX_FEATURE:0cxx_generic_lambdas
> Feature record: CXX_FEATURE:0cxx_inheriting_constructors
> Feature record: CXX_FEATURE:0cxx_inline_namespaces
> Feature record: CXX_FEATURE:0cxx_lambdas
> Feature record: CXX_FEATURE:0cxx_lambda_init_captures
> Feature record: CXX_FEATURE:0cxx_local_type_template_args
> Feature record: CXX_FEATURE:0cxx_long_long_type
> Feature record: CXX_FEATURE:0cxx_noexcept
> Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
> Feature record: CXX_FEATURE:0cxx_nullptr
> Feature record: CXX_FEATURE:0cxx_override
> Feature record: CXX_FEATURE:0cxx_range_for
> Feature record: CXX_FEATURE:0cxx_raw_string_literals
> Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
> Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
> Feature record: CXX_FEATURE:0cxx_return_type_deduction
> Feature record: CXX_FEATURE:0cxx_right_angle_brackets
> Feature record: CXX_FEATURE:0cxx_rvalue_references
> Feature record: CXX_FEATURE:0cxx_sizeof_member
> Feature record: CXX_FEATURE:0cxx_static_assert
> Feature record: CXX_FEATURE:0cxx_strong_enums
> Feature record: CXX_FEATURE:1cxx_template_template_parameters
> Feature record: CXX_FEATURE:0cxx_thread_local
> Feature record: CXX_FEATURE:0cxx_trailing_return_types
> Feature record: CXX_FEATURE:0cxx_unicode_literals
> Feature record: CXX_FEATURE:0cxx_uniform_initialization
> Feature record: CXX_FEATURE:0cxx_unrestricted_unions
> Feature record: CXX_FEA

Bug#850700: marked as done (sid/stretch version depends on servlet-api-2.5.jar)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 13:03:42 +
with message-id 
and subject line Bug#850700: fixed in resteasy 3.0.19-3
has caused the Debian Bug report #850700,
regarding sid/stretch version depends on servlet-api-2.5.jar
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.)


-- 
850700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libresteasy-java
Version: 3.0.19-2
Severity: serious

Dear maintainer,

The META-INF/MANIFEST.MF of the JAR files in this package state that
this package depends on servlet-api-2.5.jar which has now been removed
from testing/stretch and unstable/sid:

Class-Path: /usr/share/java/servlet-api-2.5.jar /usr/share/java/log4j-1.
 2.jar /usr/share/java/slf4j-api.jar /usr/share/java/slf4j-simple.jar /us
 r/share/java/scannotation.jar /usr/share/java/httpclient.jar /usr/share/
 java/commons-io.jar /usr/share/java/tomcat-annotations-api.jar /usr/shar
 e/java/el-api-2.1.jar

While a binNMU would correct the immediate issue, a larger issue exists
in that the Debian package does not state this dependency, and so I have
ended up with broken libresteasy-java JARs on my system.

Disclaimer: I am no Java developer, but an application I use is failing
to start because it indirectly depends on servlet-api-2.5.jar.

HTH,
Chris

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

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

Versions of packages libresteasy-java depends on:
ii  libcommons-io-java 2.5-1
ii  libhttpclient-java 4.5.2-2
ii  libjackson-json-java   1.9.2-8
ii  libjaxb-java   2.2.5-2
ii  libjaxrs-api-java  2.0.1-1
ii  libjboss-logging-java  3.3.0-2
ii  libjettison-java   1.2-3
ii  libtomcat8-java8.5.9-2
ii  libyaml-snake-java 1.17-1

Versions of packages libresteasy-java recommends:
ii  libjboss-logging-tools-java  2.0.2-1

libresteasy-java suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: resteasy
Source-Version: 3.0.19-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated resteasy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 12:56:01 +0100
Source: resteasy
Binary: libresteasy-java
Architecture: source all
Version: 3.0.19-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libresteasy-java - RESTEasy -- Framework for RESTful Web services and Java 
applicati
Closes: 850700
Changes:
 resteasy (3.0.19-3) unstable; urgency=medium
 .
   * Team upload.
   * Removed servlet-api-2.5.jar from the Class-Path attribute in the manifests
 (Closes: #850700)
   * Switch to debhelper level 10
Checksums-Sha1:
 06535d52211f471c99117ab1f712492170469425 2332 resteasy_3.0.19-3.dsc
 544c7eac6625498515f23f2ecc38963046845227 6436 resteasy_3.0.19-3.debian.tar.xz
 5b5b5691301194c6a8ae4eaa4c7888329ed3d6fb 1064276 
libresteasy-java_3.0.19-3_all.deb
 7238b4a6dc3bb06fdea7b9c5dea09a075176a081 14757 
resteasy_3.0.19-3_amd64.buildinfo
Checksums-Sha256:
 81badfc22d8b4ec3e22775369416f125d2515baa19898498b3dcd54325927990 2332 
resteasy_3.0.19-3.dsc
 0c6e0e869878290193d93bcd69d90246b24ab080ca0eec0a1d2d80bdad6eafe2 6436 
resteasy_3.0.19-3.debian.tar.xz
 398307920c1e13a6c751676e9282dfb96dee2b9d340d6cd2d323f4b4240085f3 1064276 
libresteasy-java_3.0.19-3_all.deb
 57e069b6160983e9cade0b3086cd1c9fc51868132e54a04a8f1c9e5fd67d4730 14757 
resteasy_3.0.19-3_amd64.buildinfo
Files:
 0bbcd40162c115530ec0631cfe80b9f4 2332 java optional resteasy_3.0.19-3.dsc
 0893dd222037433fc31933a21859feab 6436 java optional 
resteasy_3.0.19-3.debian.tar.xz
 a9082eef8cb64de8f372d39c5ba3a7f0 1064276 jav

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

[Graham Inggs]

Control: tags -1 patch

Hi

The attached patch fixes more narrowing conversions with GCC 6 on 
architectures where char is unsigned by default.


Regards
Graham

Description: Fix more narrowing conversions with GCC 6
 Needed for architectures where char is unsigned by default
Bug-Debian: https://bugs.debian.org/848917
Author: Graham Inggs 
Last-Update: 2017-01-10
--- a/plant.h
+++ b/plant.h
@@ -30,7 +30,7 @@
   char maxargs;
   char max_harmonic[NARGS];
   char max_power_of_t;
-  char  *arg_tbl;
+  signed char  *arg_tbl;
   void  *lon_tbl;
   void  *lat_tbl;
   void  *rad_tbl;
@@ -1531,7 +1531,7 @@
  3,13,
 
 };
-static char  args[] = {
+static signed char  args[] = {
   0,  3,
   3,  4,  3, -8,  4,  3,  5,  1,
   2,  2,  5, -5,  6,  2,
@@ -4393,7 +4393,7 @@
 
 };
 
-static char  argsm[] = {
+static signed char  argsm[] = {
   0,  3,
   3,  4,  3, -8,  4,  3,  5,  1,
   2,  2,  5, -5,  6,  2,
@@ -5760,7 +5760,7 @@
  0,   119,
 
 };
-static char  argsl[] = {
+static signed char  argsl[] = {
   0,  1,
   3,  1, 10,  1, 12, -1, 11,  1,
   4,  2, 10,  2, 12, -1, 13, -1, 11,  0,
@@ -7455,7 +7455,7 @@
 
 };
 /* Mars*/
-static char  argsmr[] = {
+static signed char  argsmr[] = {
   0,  4,
   3,  4,  3, -8,  4,  3,  5,  2,
   3,  5,  2, -6,  3, -4,  4,  0,
@@ -8347,7 +8347,7 @@
 
 };
 
-static char  argsv[] = {
+static signed char  argsv[] = {
   0,  3,
   2,  2,  5, -5,  6,  0,
   3,  2,  2,  1,  3, -8,  4,  0,
@@ -9500,7 +9500,7 @@
 
 };
 
-static char  argsj[] = {
+static signed char  argsj[] = {
   0,  6,
   3,  2,  5, -6,  6,  3,  7,  0,
   2,  2,  5, -5,  6,  6,
@@ -6,7 +6,7 @@
 
 };
 
-static char argsst[] = {
+static signed char argsst[] = {
   0,  7,
   3,  2,  5, -6,  6,  3,  7,  0,
   2,  2,  5, -5,  6,  5,
--- a/src/starpos.cpp
+++ b/src/starpos.cpp
@@ -2155,7 +2155,7 @@
 	  char *p;
 	#else
 	#ifdef __STDC__
-	   char *p;
+	   signed char *p;
 	#else
 	  char *p;
 	#endif
@@ -2324,7 +2324,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif
@@ -2476,7 +2476,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif
@@ -2593,7 +2593,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif

Processed: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #848917 [src:nautic] nautic FTBFS on architectures where char is unsigned: 
error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
Added tag(s) patch.

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

Bug#846640: marked as done (lldb-3.8: lldb freezes after "run")

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 13:20:43 +
with message-id 
and subject line Bug#846640: fixed in llvm-toolchain-3.9 1:3.9.1-2
has caused the Debian Bug report #846640,
regarding lldb-3.8: lldb freezes after "run"
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.)


-- 
846640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable

lldb 3.8 freezes after "run". Same for lldb 3.9 in stretch. Details: 
http://bugs.debian.org/846531--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.9
Source-Version: 1:3.9.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.9 
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, 17 Dec 2016 17:55:44 +0100
Source: llvm-toolchain-3.9
Binary: clang-3.9 clang-format-3.9 clang-tidy-3.9 clang-3.9-doc libclang1-3.9 
libclang1-3.9-dbg libclang-3.9-dev libclang-common-3.9-dev libfuzzer-3.9-dev 
python-clang-3.9 clang-3.9-examples libllvm3.9 libllvm3.9-dbg llvm-3.9 
llvm-3.9-runtime llvm-3.9-dev llvm-3.9-tools libllvm-3.9-ocaml-dev llvm-3.9-doc 
llvm-3.9-examples lldb-3.9 liblldb-3.9 liblldb-3.9-dbg python-lldb-3.9 
liblldb-3.9-dev
Architecture: source amd64 all
Version: 1:3.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-3.9  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.9-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.9-examples - Clang examples
 clang-format-3.9 - Tool to format C/C++/Obj-C code
 clang-tidy-3.9 - clang-based C++ linter tool
 libclang-3.9-dev - clang library - Development package
 libclang-common-3.9-dev - clang library - Common development package
 libclang1-3.9 - C interface to the clang library
 libclang1-3.9-dbg - clang library
 libfuzzer-3.9-dev - Library for coverage-guided fuzz testing
 liblldb-3.9 - Next generation, high-performance debugger, library
 liblldb-3.9-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-3.9-dev - Next generation, high-performance debugger, header files
 libllvm-3.9-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm3.9 - Modular compiler and toolchain technologies, runtime library
 libllvm3.9-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lldb-3.9   - Next generation, high-performance debugger
 llvm-3.9   - Modular compiler and toolchain technologies
 llvm-3.9-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-3.9-doc - Modular compiler and toolchain technologies, documentation
 llvm-3.9-examples - Modular compiler and toolchain technologies, examples
 llvm-3.9-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-3.9-tools - Modular compiler and toolchain technologies, tools
 python-clang-3.9 - Clang Python Bindings
 python-lldb-3.9 - Next generation, high-performance debugger, python lib
Closes: 846269 846616 846638 846640
Changes:
 llvm-toolchain-3.9 (1:3.9.1-2) unstable; urgency=medium
 .
   * debian/orig-tar.sh: less verbose
   * Remove the info section from the generated manpages (Closes: #846269)
   * Disable libedit usage in lldb because of garbage (Closes: #846616)
   * Fix the path to lldb-server (to lldb-server-3.9) (Closes: #846638)
   * d/p/lldb-server-link.diff Fix the lldb hang. It was due to a linking issue.
 Thanks to Pavel Labath (Closes: #846640)
Checksums-Sha1:
 8912df4b8fa5e55335c345d653bbe33f2a20cd2c 6399 llvm-toolchain-3.9_3.9.1-2.dsc
 9f93e46396e765e49918095445e258b707ad4f58 71652 
llvm-toolchain-3.9_3.9.1-2.debian.tar.xz
 bd37ec003dda51654b7aeb7cab89333e4074022b 213146444 
clang-3.9-dbgsym_3.9.1-2_amd64.deb
 a51d4bfa256304da70f401af1c99c326beed4a78 21452 clang-3.9-doc_3.9.1-2_all.deb
 3dfc

Bug#846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Gert Wollny]

Digging to reasons for pending autoremovals I came across this bug 

First I had a strange problem with the X connection: I run Debian in a
chroot into which I ssh with "ssh -Y  localhost:". X-clients like
emacs run correctly, but dpkg-buildpackage failed with 


dh_auto_test -O--buildsystem=pybuild
pybuild --test -i python{version} -p 2.7
I: pybuild base:184: cd /home/gerddie/debian-other/python-traits-
4.6.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v 
X11 connection rejected because of wrong authentication.
python -m unittest: cannot connect to X server localhost:11.0

Anywy, when I run the test manually then I can confirm the bug - with
different numbers though (see below).

==
FAIL: test_delegation_refleak
(traits.tests.test_regression.TestRegression)
--
Traceback (most recent call last):
  File "/home/gerddie/debian-other/python-traits-
4.6.0/.pybuild/pythonX.Y_2.7/build/traits/tests/test_regression.py",
line 173, in test_delegation_refleak
self.assertEqual(counts[warmup:-1], counts[warmup+1:])
AssertionError: Lists differ: [83406, 83481, 83556, 83631] != [83481,
83556, 83631, 83706]

First differing element 0:
83406
83481

- [83406, 83481, 83556, 83631]
?  ---

+ [83481, 83556, 83631, 83706]
? +++


==
FAIL: test_no_leaking_notifiers
(traits.tests.test_regression.TestRegression)
Extended trait change notifications should not leaf
--
Traceback (most recent call last):
  File "/home/gerddie/debian-other/python-traits-
4.6.0/.pybuild/pythonX.Y_2.7/build/traits/tests/test_regression.py",
line 125, in test_no_leaking_notifiers
self.assertEqual(len(ctrait._notifiers(1)), 0)
AssertionError: 1 != 0

--
Ran 538 tests in 24.723s

Bug#850811: marked as done (reportbug - crashing)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 09:04:16 -0500
with message-id 

and subject line Re: [Reportbug-maint] Bug#850811: reportbug - crashing
has caused the Debian Bug report #850811,
regarding reportbug - crashing
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.)


-- 
850811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug 7.1.1


Dear maintainers, 

sorry to tell you on this way, that reportbug is not working for me any more.
I am running debian/testing, and the same error appears on 32-bit and 64-bit 
systems. This is the output, where I tried to tell a bug in 
virtualbox-guest-x11:

 snip ...

username@host2:~$ reportbug  
~$

--- snap ---

Thank you for any help.

Best regards

Hans

--- End Message ---
--- Begin Message ---
Version: 7.1.2

On Tue, Jan 10, 2017 at 6:11 AM, Hans  wrote:
> Package: reportbug 7.1.1

upgrade to the latest version, this bug is fixed there

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi--- End Message ---

Bug#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Santiago Vila]

On Tue, Jan 10, 2017 at 10:02:12AM +0100, Emmanuel Bourg wrote:
> I'm unable to reproduce this issue. The pom file
> build/debian/easybind.pom should be generated automatically, this
> feature was added to gradle-debian-helper 1.4.
> 
> Santiago could you post the full build log please?

Sure. There was already a build failure here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/easybind_1.0.3-1.rbuild.log

I've also put my build logs here:

https://people.debian.org/~sanvila/build-logs/easybind/

> I'd like to check the versions of gradle and gradle-debian-helper
> used.

If this is not a bug in easybind, please use "reassign" and "affects".

Thanks.

Bug#850725: marked as done (flickcurl: New upstream release, fixing overflows)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 15:04:31 +
with message-id 
and subject line Bug#850725: fixed in flickcurl 1.26-1
has caused the Debian Bug report #850725,
regarding flickcurl: New upstream release, fixing overflows
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.)


-- 
850725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flickcurl
Version: 1.25-3
Severity: grave
Tags: security
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

A new upstream release of libflickr is available.

Upstream changelog mentions seemingly security-related bugfixes:

> Multiple error path allocation fixes, several memory leak fixes and a
> few overflows found via Coverity.

I am unable to determine if those are truly security-related, so severity
inflated to be on the safe side: Please adjust as appropriate.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYc8oGAAoJECx8MUbBoAEh67QP/14maf4BTKvQNI+GPTOyVMTZ
1kJZeQBIvU++S+yv4P8GAJgMCmqNgUuSzbNgCQkio/1CYTkcKHXwKb3t+/IzN9jE
s1vlE56iP82k4TIQk50NmzMuCAdXThTQIeVT5VyeDcaEuvzW2gxNNW//1xbmNmz0
6hV7ms/zzord8YEVB4uGPcc31KgETCziDl3Yt6Y6cYdQ/wyjOga8e3X+ALz1Dq7n
ludjB4IB7iOfsxPDWj3RL1Xa8HBoo+Z1NnuMgQOUlV9nw0BeAqKoL/PeijX6n29V
90tyizFlO6wF3ZAFKJXP6TmO07D/RSEZ4cEUxeETQq2ccV8x/TH1LPYYjsmtKYQS
T9HhOITHuivJGLH4uuKOw9DgaPYk//9cpSO1wXomTdTmKkPHIMnXcs7DKgQGbTcP
IG1pFeGGbZqYzLwwffZPoDZtqc8N8vuttwwO7DaMNoPTmfSSbI49BlaZKK3be9Ih
FoklI0+2egZykx1Q/Mpf49swFCv10IHciUtwATh+U1kWWrb84sZQiLJATAJR09wz
EU7UwZKNgm7SWbD3321nGUQHwAiJIPTmnNpRtjteUStm5tMHDBS1f9xHcjlgezJo
+gCoZ1GI4QvXE5CuRVxSS6TEVYCJsB31tjYr0WJdDUQzihgY0qzZhWt2FcRS4KlR
65PZwEmSv+swuR8y/SGq
=m7cZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: flickcurl
Source-Version: 1.26-1

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

Debian distribution maintenance software
pp.
Kumar Appaiah  (supplier of updated flickcurl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 19:38:00 +0530
Source: flickcurl
Binary: libflickcurl-dev libflickcurl0 libflickcurl0-dbg flickcurl-utils 
flickcurl-doc
Architecture: source all amd64
Version: 1.26-1
Distribution: unstable
Urgency: medium
Maintainer: Kumar Appaiah 
Changed-By: Kumar Appaiah 
Description:
 flickcurl-doc - utilities to call the Flickr API from command line - 
documentatio
 flickcurl-utils - utilities to call the Flickr API from command line
 libflickcurl-dev - C library for accessing the Flickr API - development files
 libflickcurl0 - C library for accessing the Flickr API
 libflickcurl0-dbg - C library for accessing the Flickr API - debugging symbols
Closes: 850725 850727
Changes:
 flickcurl (1.26-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #850725)
   * Depend on libraptor2-dev (Closes: #850727)
   * Standards version is now 3.9.8 (no changes needed)
   * Remove HTTPS URL fix patches
Checksums-Sha1:
 ee4b4b67917859d73739e0a5675efd0f1bb88184 2157 flickcurl_1.26-1.dsc
 547480030ce4f777bb35d98b43fe15ee3eeae0e0 1870073 flickcurl_1.26.orig.tar.gz
 f55a2e71cb48265461be1f49f21f2ecb82fa5312 4828 flickcurl_1.26-1.debian.tar.xz
 14c0ecdb0e8921a058d4248e6f43c3e24627a4ac 696144 flickcurl-doc_1.26-1_all.deb
 09c5c51d681a7da52f6c65f7983e6e805e4f5724 147620 
flickcurl-utils_1.26-1_amd64.deb
 85a73b0363c9c7d03a0a69e6f44cc84969614847 6532 flickcurl_1.26-1_amd64.buildinfo
 bc8dc4c197cdf0e96e0ad68ee22ca5d91410c131 117074 
libflickcurl-dev_1.26-1_amd64.deb
 f4185bf0281becb9fa3febb4575064a7fea12836 596056 
libflickcurl0-dbg_1.26-1_amd64.deb
 56e531babb7a8c8a096c5422e122d985c5dc81d0 175404 libflickcurl0_1.26-1_amd64.deb
Checksums-Sha256:
 88b7eabda97e5a8d012fad5a72c936ef89b4a0a8e53dac2f4db5447c4661bb7b 2157 
flickcurl_1.26-1.dsc
 ff42a36c7c1c7d368246f6bc9b7d792ed298348e5f0f5d432e49f6803562f5a3 1870073 
flickcurl_1.26.orig.tar.gz
 137d36db6b724f2e8755a6e5e1191a71699ce0178b5ec217bfa079c48b2e6ef7 4828 
flickcurl_1.26-1.debian.tar.xz
 a140082b8411d49ff567193d4aa

Bug#798590: marked as done (libv8-3.14: FTBFS on mipsel: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 15:06:25 +
with message-id 
and subject line Bug#798590: fixed in libv8-3.14 3.14.5.8-11
has caused the Debian Bug report #798590,
regarding libv8-3.14: FTBFS on mipsel: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
798590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libv8-3.14
Version: 3.14.5.8-10
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid stretch

libv8-3.14 failed to builds on mipsel:
| [149:12|%  73|+ 4460|-   0]: mjsunit/harmony/block-lazy-compile 
|
| [149:13|%  73|+ 4461|-   0]: mjsunit/harmony/block-leave 
| 
| [149:17|%  73|+ 4462|-   0]: mjsunit/harmony/block-leave 
| 
| [149:24|%  74|+ 4463|-   0]: mjsunit/harmony/block-let-crankshaft 
|  
| [149:32|%  74|+ 4464|-   0]: mjsunit/harmony/block-leave 
| 
| [149:39|%  74|+ 4465|-   0]: mjsunit/harmony/block-let-crankshaft 
|  
| [149:44|%  74|+ 4466|-   0]: mjsunit/harmony/block-let-declaration 
|   
| [149:54|%  74|+ 4467|-   0]: mjsunit/harmony/block-let-crankshaft 
|  
| [150:00|%  74|+ 4468|-   0]: 
mjsunit/harmony/block-let-declaration/usr/share/cdbs/1/class/makefile.mk:67: 
recipe for target 'debian/stamp-makefile-check' failed
| Makefile:215: recipe for target 'mipsel.release.check' failed
| Build killed with signal TERM after 150 minutes of inactivity

The build is killed due to inactivity. The log clearly shows that there is
inactivity, but not on stdout so the build is killed (see #731940 in sbuild
which was recently fixed in experimental). Until the buildds get that fixed, it
might be the best idea to simply redirect the output to stderr.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: libv8-3.14
Source-Version: 3.14.5.8-11

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated libv8-3.14 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 15:26:12 +0100
Source: libv8-3.14
Binary: libv8-dev libv8-3.14-dev libv8-3.14.5 libv8-3.14-dbg
Architecture: source
Version: 3.14.5.8-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Balint Reczey 
Description:
 libv8-3.14-dbg - V8 JavaScript engine - debugging symbols
 libv8-3.14-dev - V8 JavaScript engine - development files for 3.14 branch
 libv8-3.14.5 - V8 JavaScript engine - runtime library
 libv8-dev  - V8 JavaScript engine - development files for latest branch
Closes: 749288 760994 798590 812304 831161
Changes:
 libv8-3.14 (3.14.5.8-11) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Fix FTBFS due to this == NULL tests (Closes: #831161)
   * Increase stack size for failing test to make it pass
   * Fix test failures by disabling optimizations (Closes: #812304)
   * Use -fno-delete-null-pointer-checks C++ flag instead of disabling all 
optimizations
   * Add support for powerpc, ppc and ppc64el platform merging patch from Ubuntu
 (Closes: #760994)
   * Target default mips variant instead of loongson to fix FTBFS (Closes: 
#798590)
   * Sync d/control and d/control.in
   * Keep old ABI to prevent symbol changes due to libcxx11 (GCC 5) transition
 .
   [ Peter Michael Green ]
   * Add Raspbian support to configuration logic (Closes: #749288)
Checksums-Sha1:
 0

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

Package: monit
Version: 1:5.20.0-5
Severity: grave
Justification: causes non-serious data loss

I've noticed that the latest version of monit has overwritten
its log file (/var/log/monit.log). /var/log/monit.log.1 ends
on January 2 with:

[...]
[CET Jan  2 07:32:58] error: Queued event file: unable to read event size 
-- end of file
[CET Jan  2 07:32:58] error: Queued event file: unable to read event size 
-- end of file
[CET Jan  2 07:32:58] error: 'eth0' link down
[CET Jan  2 07:34:58] error: Queued event file: unable to read event size 
-- end of file
[CET Jan  2 07:34:58] error: Queued event file: unable to read event size 
-- end of file
[CET Jan  2 07:34:58] error: 'eth0' link down
[CET Jan  2 07:35:07] info : Awakened by the SIGHUP signal
Reinitializing Monit - Control file '/etc/monit/monitrc'

while /var/log/monit.log starts with:

[CET Jan 10 10:29:40] info : Starting Monit 5.20.0 daemon
[CET Jan 10 10:29:40] info : 'zira' Monit 5.20.0 started

In /var/log/dpkg.log about monit:

2017-01-10 10:29:32 upgrade monit:amd64 1:5.20.0-4 1:5.20.0-5
2017-01-10 10:29:32 status half-configured monit:amd64 1:5.20.0-4
2017-01-10 10:29:32 status unpacked monit:amd64 1:5.20.0-4
2017-01-10 10:29:32 status half-installed monit:amd64 1:5.20.0-4
2017-01-10 10:29:33 status triggers-pending systemd:amd64 232-8
2017-01-10 10:29:33 status half-installed monit:amd64 1:5.20.0-4
2017-01-10 10:29:33 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:33 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:39 configure monit:amd64 1:5.20.0-5 
2017-01-10 10:29:39 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status unpacked monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status half-configured monit:amd64 1:5.20.0-5
2017-01-10 10:29:40 status installed monit:amd64 1:5.20.0-5

-- Package-specific info:

Monit config file /etc/monit/monitrc is *NOT* readable by reportbug.
Please, consider to rerun reportbug as root and *carefully* examine
reportbug's output (e.g., monitrc content), before sending it out.

Contents of /etc/monit/ directory:
/etc/monit:
total 36
drwxr-xr-x 2 root root  4096 2017-01-10 10:29:40 conf-available
drwxr-xr-x 2 root root  4096 2015-12-05 21:19:30 conf-enabled
drwxr-xr-x 2 root root  4096 2015-07-07 14:43:58 conf.d
-rw--- 1 root root 12449 2016-10-23 02:13:50 monitrc
drwxr-xr-x 2 root root  4096 2016-12-11 18:22:40 monitrc.d
drwxr-xr-x 2 root root  4096 2017-01-10 10:29:40 templates

/etc/monit/conf-available:
total 60
-rw-r--r-- 1 root root  481 2015-12-05 21:13:49 acpid
-rw-r--r-- 1 root root  640 2015-12-05 21:13:49 apache2
-rw-r--r-- 1 root root  455 2015-12-05 21:13:49 at
-rw-r--r-- 1 root root  691 2015-12-05 21:13:49 cron
-rw-r--r-- 1 root root  602 2015-12-05 21:13:49 mdadm
-rw-r--r-- 1 root root  669 2015-12-05 21:13:49 memcached
-rw-r--r-- 1 root root  703 2015-12-05 21:13:49 mysql
-rw-r--r-- 1 root root  521 2015-12-05 21:13:49 nginx
-rw-r--r-- 1 root root  471 2015-12-05 21:13:49 openntpd
-rw-r--r-- 1 root root  950 2015-12-05 21:13:49 openssh-server
-rw-r--r-- 1 root root  683 2015-12-05 21:13:49 pdns-recursor
-rw-r--r-- 1 root root 1421 2015-12-05 21:13:49 postfix
-rw-r--r-- 1 root root  869 2016-03-22 16:43:44 rsyslog
-rw-r--r-- 1 root root  501 2015-12-05 21:13:49 smartmontools
-rw-r--r-- 1 root root  306 2016-02-04 15:03:50 snmpd

/etc/monit/conf-enabled:
total 0

/etc/monit/conf.d:
total 4
-rw-r--r-- 1 root root 357 2015-07-07 14:43:58 eth0

/etc/monit/monitrc.d:
total 64
-rw-r--r-- 1 root root  481 2015-06-09 15:52:48 acpid
-rw-r--r-- 1 root root  640 2015-06-09 15:52:48 apache2
-rw-r--r-- 1 root root  455 2015-06-09 15:52:48 at
-rw-r--r-- 1 root root  691 20

Bug#751121: marked as done (Please fix "FIXME" statements in copyright file)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 15:07:53 +
with message-id 
and subject line Bug#751121: fixed in netatalk 2.2.5-2
has caused the Debian Bug report #751121,
regarding Please fix "FIXME" statements in copyright file
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.)


-- 
751121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netatalk
Version 2.2.2-1
Severity: serious
Tags: jessie sid


Your debian/copyright file contains lots of FIXMEs.

For example there is an entry for
  distrib/initscripts/rc.atalk.suse.tmpl
but this file does not exist. The corresponding file
  distrib/initscripts/rc.atalk.suse-sysv.tmpl
contains just the line:
 Copyright (c) 1996-2001 SuSE GmbH Nuernberg, Germany.  All rights reserved.
How do you know that Debian is allowed to distribute it?
--- End Message ---
--- Begin Message ---
Source: netatalk
Source-Version: 2.2.5-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated netatalk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 15:29:57 +0100
Source: netatalk
Binary: netatalk netatalk-dbg
Architecture: source
Version: 2.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netatalk team 
Changed-By: Jonas Smedegaard 
Description:
 netatalk   - AppleTalk user binaries
 netatalk-dbg - Debug symbols for netatalk
Closes: 751121 760111 760112
Changes:
 netatalk (2.2.5-2) unstable; urgency=medium
 .
   [ Adrian Knoth ]
   * Add patch to source init functions in init.d script.
   * Bump debhelper compatibility level to 9.
 .
   [ Brian Campbell ]
   * Add myself to uploaders
 .
   [ Chris Boot ]
   * Add myself to uploaders
 .
   [ Jonas Smedegaard ]
   * Address most FIXMEs.
   * Update watch file:
 + Bump to version 4.
 + Track any release (not only 2.x).
 + Mention gpb --uscan in usage comment.
   * Stop track upstream source with CDBS (use gpb --uscan).
   * Update git-buildpackage config: Filter any .gitignore file.
   * Modernize CDBS:
 + Build-depend on licensecheck (not devscripts).
 + Tighten binary package relations to be package-specific.
   * Declare compliance with Debian Policy 3.9.8.
   * Update copyright info:
 + Resolve remaining FIXMEs.
   Closes: Bug#751121. Thanks to Luca Falavigna.
 + Use License-Grant and License-Reference fields.
   Thanks to Ben Finney.
 + Clarify vaguely ORed license pair.
 + Re-label to use SPDX license shortnames FSFUL FSFULLR X11.
 + Extend coverage of Debian packaging.
   * Add lintian override regarding license in License-Reference field.
 See bug#786450.
   * Drop example script to convert from netatalk 2.0.4~beta2-4 and
 earlier: needed package db4.2-util no longer available.
 Stop suggest db4.2-util.
   * Fix version in NEWS entry.
   * Add patches cherry-picked upstream, including ASP/DDP fixes.
 Closes: Bug#760111, #760112. Thanks to Vincent Duvert.
   * Fix stop build-depend on d-shlibs.
Checksums-Sha1:
 010ff916c2376f816ab0e3dbe1d8a44fac7cf2db 2262 netatalk_2.2.5-2.dsc
 866509bc8953d5613a1f1bcbd9d5937aa273b3b3 48124 netatalk_2.2.5-2.debian.tar.xz
Checksums-Sha256:
 4a608fb3850c872f1cf58ad0918283caa6c7583c49c6ac679e83f75245a84c95 2262 
netatalk_2.2.5-2.dsc
 d118e7f894cb0ae9b4aed2f5d2545bd0fdf681bba25d45751efa6f4b36f7d64f 48124 
netatalk_2.2.5-2.debian.tar.xz
Files:
 21b2ccca7b14de700015da24afd55055 2262 net extra netatalk_2.2.5-2.dsc
 950b3d9365c6b62f740e00210fe745c6 48124 net extra netatalk_2.2.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYdPDxAAoJECx8MUbBoAEheIoP/3HmBpU1uQC+hgwtQmwDzYT+
A+XeRnyB3FGI14+h1nub0TpY6mLy0v8RvhFde2dMKIBNoQHXsNzO8VjraxhH5AXH
ZKVW5Gq8BRdbRj+IcD4sm3+T/yLDorGe0nYa7PafCO7M2L7aJBP+DzK33yY3IcWp
uFQe11hHKeaYA0i2uNsONzkCY2Dok9gs4GYwhquV1ZlV24AVswQnxiA5gpoiJjhf
Rz78m7v66wj3AN3hgwB3ul7uJRged4fyzyaE0nBWyyrltBK0DsE6Qyb9OKpaaTyh
UiVmpR3Z06aOXXi/yey+PNTCpwYC8QxwZfUVV23/

Bug#831161: marked as done (libv8-3.14: FTBFS with GCC 6: ../src/spaces.h:837:39: error: nonnull argument 'this' compared to NULL [-Werror=nonnull-compare])

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 15:06:25 +
with message-id 
and subject line Bug#831161: fixed in libv8-3.14 3.14.5.8-11
has caused the Debian Bug report #831161,
regarding libv8-3.14: FTBFS with GCC 6: ../src/spaces.h:837:39: error: nonnull 
argument 'this' compared to NULL [-Werror=nonnull-compare]
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.)


-- 
831161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libv8-3.14
Version: 3.14.5.8-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
>   g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' 
> '-DV8_TARGET_ARCH_X64' '-DBUILDING_V8_SHARED' '-DV8_SHARED' -I../src  -Wall 
> -Werror -W -Wno-unused-parameter -Wnon-virtual-dtor -pthread -fno-rtti 
> -fno-exceptions -pedantic -ansi -fvisibility=hidden -fPIC -fdata-sections 
> -ffunction-sections -O3  -MMD -MF 
> /«PKGBUILDDIR»/out/x64.release/.deps//«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o.d.raw
>  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o 
> /«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o 
> ../src/spaces.cc
> In file included from ../src/mark-compact.h:32:0,
>  from ../src/incremental-marking.h:33,
>  from ../src/heap.h:35,
>  from ../src/elements.h:33,
>  from ../src/objects-inl.h:38,
>  from ../src/v8.h:60,
>  from ../src/spaces.cc:28:
> ../src/spaces.h: In member function 'bool v8::internal::CodeRange::exists()':
> ../src/spaces.h:837:39: error: nonnull argument 'this' compared to NULL 
> [-Werror=nonnull-compare]
>bool exists() { return this != NULL && code_range_ != NULL; }
>^
> ../src/spaces.h: In member function 'bool 
> v8::internal::CodeRange::contains(v8::internal::Address)':
> ../src/spaces.h:839:5: error: nonnull argument 'this' compared to NULL 
> [-Werror=nonnull-compare]
>  if (this == NULL || code_range_ == NULL) return false;
>  ^~
> cc1plus: all warnings being treated as errors
> make[2]: *** [/«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/libv8-3.14_3.14.5.8-10_unstable_gcc6.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: libv8-3.14
Source-Version: 3.14.5.8-11

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated libv8-3.14 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 15:26:12 +0100
Source: libv8-3.14
Binary: libv8-dev libv8-3.14-dev libv8-3.14.5 libv8-3.14-dbg
Architecture: source
Version: 3.14.5.8-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Balint Reczey 
Description:
 libv8-3.14-dbg - V8 JavaScript engine - debugging symbols
 libv8-3.14-dev - V8 JavaScript engine - development files for 3.14 branch
 libv8-3.14.5 - V8 JavaScript engine - runtime library
 libv8-dev  - V8 JavaS

Bug#812304: marked as done (libv8-3.14: FTBFS with GCC 6: x64.release.check crashed)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 15:06:25 +
with message-id 
and subject line Bug#812304: fixed in libv8-3.14 3.14.5.8-11
has caused the Debian Bug report #812304,
regarding libv8-3.14: FTBFS with GCC 6: x64.release.check crashed
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.)


-- 
812304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libv8-3.14
Version: 3.14.5.8-10
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> exit code: -11
> --- CRASHED ---
> 
 
[00:27|%  99|+ 2781|- 3286]: message/overwritten-builtins 
 
=== message/overwritten-builtins ===
> Command:  /<>/out/x64.release/d8 --test --stress-opt 
> --always-opt --nobreak-on-abort --nodead-code-elimination 
> /<>/test/message/overwritten-builtins.js 
> exit code: -11
> --- CRASHED ---
> 
 
[00:27|%  99|+ 2781|- 3287]: message/replacement-marker-as-argument 
   
=== message/replacement-marker-as-argument ===
> Command:  /<>/out/x64.release/d8 --test --nobreak-on-abort 
> --nodead-code-elimination 
> /<>/test/message/replacement-marker-as-argument.js 
> exit code: -11
> --- CRASHED ---
> 
   
[00:27|%  99|+ 2781|- 3288]: message/replacement-marker-as-argument 
   
=== message/replacement-marker-as-argument ===
> Command:  /<>/out/x64.release/d8 --test --stress-opt 
> --always-opt --nobreak-on-abort --nodead-code-elimination 
> /<>/test/message/replacement-marker-as-argument.js 
> exit code: -11
> --- CRASHED ---
> 
   
[00:27|%  99|+ 2781|- 3289]: message/replacement-marker-as-argument 
   
=== message/replacement-marker-as-argument ===
> Command:  /<>/out/x64.release/d8 --test --nocrankshaft 
> --nobreak-on-abort --nodead-code-elimination 
> /<>/test/message/replacement-marker-as-argument.js 
> exit code: -11
> --- CRASHED ---
> 
   
[00:27|%  99|+ 2781|- 3290]: message/simple-throw 
 
=== message/simple-throw ===
> Command:  /<>/out/x64.release/d8 --test --nocrankshaft 
> --nobreak-on-abort --nodead-code-elimination 
> /<>/test/message/simple-throw.js 
> exit code: -11
> --- CRASHED ---
> 
 
[00:27|%  99|+ 2781|- 3291]: message/simple-throw 
 
=== message/simple-throw ===
> Command:  /<>/out/x64.release/d8 --test --nobreak-on-abort 
> --nodead-code-elimination /<>/test/message/simple-throw.js 
> exit code: -11
> --- CRASHED ---
> 
 
[00:27|%  99|+ 2781|- 3292]: message/simple-throw 
 
=== message/simple-throw ===
> Command:  /<>/out/x64.release/d8 --test --stress-opt 
> --always-opt --nobreak-on-abort --nodead-code-elimination 
> /<>/test/message/simple-throw.js 
> exit code: -11
> --- CRASHED ---
> 
 
[00:27|%  99|+ 2781|- 3293]: message/try-catch-finally-no-message 
 
=== message/try-catch-finally-no-message ===
> Command:  /<>/out/x64.release/d8 --test --nobreak-on-abort 
> --nodead-code-elimination 
> /<>/test/message/try-catch-finally-no-mess

Bug#846531: marked as done (lldb-3.8 and lldb-3.9 are completely unusable in stretch (multiply problems); fix them or remove from scretch)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 16:15:55 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #846531,
regarding lldb-3.8 and lldb-3.9 are completely unusable in stretch (multiply 
problems); fix them or remove from scretch
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.)


-- 
846531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable

lldb 3.8 is unusable is Stretch. Here is list of bugs. Most of them apply to 
lldb 3.9, too. Some of them apply
to lldb 3.7, too, but lldb 3.7 is somewhat usable unlike lldb 3.8 and lldb 3.9.

Steps to reproduce. I installed fresh Debian Stretch amd64 to Qemu/KVM virtual 
machine (for clean experiment)
using Debian Stretch alpha 8 installer
( 
http://cdimage.debian.org/cdimage/stretch_di_alpha8/amd64/iso-cd/debian-stretch-DI-alpha8-amd64-netinst.iso
 ).
During installation I cleared checkbox "Install standard system utilities" to 
catch lldb dependency errors.
After installation I put 'APT::Install-Recommends "false";' to apt.conf for the 
same reason.
Then I performed some misc. configuration and installed some misc. packages 
(for example, openssh-server to
connect to this VM from outside).
Then:

debian:~# apt-get install clang-3.8 lldb-3.8
debian:~# echo 'int main (void) {}' > a.cpp
debian:~# clang-3.8 -g -o a a.cpp  # See below on clang-3.8 and clang++-3.8
debian:~# lldb-3.8 ./a
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
(lldb)

Problem 1. "ImportError: No module named lldb.embedded_interpreter".

Then I pressed "r". "\U+96272" appeared instead. This happened in ssh session 
from host in X terminal (KDE's
konsole), TERM is xterm. Same is happenning on linux console in VM (TERM is 
linux).

Problem 2. "\U+96272".

Then:

debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
error: process launch failed: unable to locate lldb-server

Problem 3. "error: process launch failed: unable to locate lldb-server".

Then:

debian:~# ln -s lldb-server-3.8 /usr/bin/lldb-server
debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
^C
^\Quit
debian:~#

And now lldb freezed.

Problem 4. lldb freezes.

And now I don't know what to do and how to fix this. It seems
http://lists.llvm.org/pipermail/lldb-dev/2016-March/009925.html is related.

Then:

debian:~# apt-get install python-lldb-3.8

This fixed that "lldb.embedded_interpreter" problem, but lldb still freezes.

Full log is here: http://paste.debian.net/900115/

Additional notes:
* This bug report is sent from that VM using "bugreport".
* lldb 3.9 has the same bugs except that "lldb.embedded_interpreter" bug.
* lldb 3.7 has some of this bugs, but it is usable. It doesn't freeze, so I 
actually was able
to debug that C++ one-liner (but terminal support is still broken).
* At first I compiled the program so: "clang-3.8 -g -o a a.cpp" and reproduced 
all this bugs.
Then I compiled it so: "clang++-3.8 -g -o a a.cpp" and reproduced all this bugs 
again.

So:
* Fix this bugs in lldb 3.7, lldb 3.8 and lldb 3.9 before Stretch release. Or 
just remove this packages from Scretch.
* Test that they work out-of-the-box. Even if the system doesn't have "standard 
system utilities" and apt configured
not to install recommended packages.


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

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

Versions of packages lldb-3.8 depends on:
ii  libc6 2.24-7
ii  libedit2  3.1-20160903-2
ii  libffi6   3.2.1-6
ii  libgcc1   1:6.2.0-13
ii  liblldb-3.8   1:3.8.1-16
ii  libllvm3.81:3.8.1-16
ii  libncurses5   6.0+20160917-1
ii  libpython2.7  2.7.12-7
ii  libstdc++66.2.0-13
ii  libtinfo5 6.0+20160917-1
ii  llvm-3.8-dev  1:3.8.1-16
ii  zlib1g1:1.2.8.dfsg-2+b3

lldb-3.8 recommends no packages.

Versions of pac

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 846531 1:3.8.1-16
Bug #846531 [lldb-3.8] lldb-3.8 and lldb-3.9 are completely unusable in stretch 
(multiply problems); fix them or remove from scretch
Marked as fixed in versions llvm-toolchain-3.8/1:3.8.1-16.
> thanks
Stopping processing here.

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

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

zira:~> journalctl -b -u monit
-- Logs begin at Fri 2015-07-03 14:03:14 CEST, end at Tue 2017-01-10 16:15:02 
CET. --
Jan 09 15:09:46 zira systemd[1]: Starting LSB: service and resource monitoring 
daemon...
Jan 09 15:09:46 zira monit[759]: Starting daemon monitor: monit.
Jan 09 15:09:46 zira systemd[1]: Started LSB: service and resource monitoring 
daemon.
Jan 10 10:29:32 zira systemd[1]: Stopping LSB: service and resource monitoring 
daemon...
Jan 10 10:29:32 zira monit[20166]: Stopping daemon monitor: monit.
Jan 10 10:29:32 zira systemd[1]: Stopped LSB: service and resource monitoring 
daemon.
Jan 10 10:29:40 zira systemd[1]: Starting LSB: service and resource monitoring 
daemon...
Jan 10 10:29:40 zira monit[21356]: Starting daemon monitor: monit.
Jan 10 10:29:40 zira systemd[1]: Started LSB: service and resource monitoring 
daemon.

Note that after the reboot on Jan 09, the log file /var/log/monit.log
with logs between Jan 02 and Jan 09 was still there.

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

Bug#850829: monit overwrites its log file

[Sergey B Kirpichev]

On Tue, Jan 10, 2017 at 04:08:03PM +0100, Vincent Lefevre wrote:
> I've noticed that the latest version of monit has overwritten
> its log file (/var/log/monit.log). /var/log/monit.log.1 ends
> on January 2 with:

How logging system configured?  journald?

> [...]
> [CET Jan  2 07:32:58] error: Queued event file: unable to read event size 
> -- end of file
> [CET Jan  2 07:32:58] error: Queued event file: unable to read event size 
> -- end of file
> [CET Jan  2 07:32:58] error: 'eth0' link down
> [CET Jan  2 07:34:58] error: Queued event file: unable to read event size 
> -- end of file
> [CET Jan  2 07:34:58] error: Queued event file: unable to read event size 
> -- end of file
> [CET Jan  2 07:34:58] error: 'eth0' link down
> [CET Jan  2 07:35:07] info : Awakened by the SIGHUP signal
> Reinitializing Monit - Control file '/etc/monit/monitrc'
> 
> while /var/log/monit.log starts with:
> 
> [CET Jan 10 10:29:40] info : Starting Monit 5.20.0 daemon
> [CET Jan 10 10:29:40] info : 'zira' Monit 5.20.0 started

What happens with logfile if you do manual restart of the monit?  stop
and start?  If you do reload?

Bug#844943: python-bleach: FTBFS: Tests failures

[Barry Warsaw]

On Jan 10, 2017, at 09:37 AM, Pirate Praveen wrote:

>bleach and other projects using html5lib seems to have locked the version of
>html5lib to the one with 7 nines. Can we also go back to the older version
>which works?

I had a conversation with the upstream pip maintainer.  In theory it may be
possible.  In practice it's often a nightmare to go backwards.  I'm willing to
help try to make that happen if others are also willing to help.

>It is not sustainable to expect maintainers to reverse dependencies to fix
>breakage with out giving them advance notice. Since python-bleach has
>autopkgtests defined, it would have been easy to find out if an update of
>python-html5lib would break it or not using a tool like build-and-upload
>script from pkg-ruby-extras team [1]

I'm not sure why you think I'd know anything about an obscure Ruby tool.  I
still contend that Debian ought to have automatic promotion gating on reverse
dependency building and testing.

All that aside, if someone wants to help put together a git branch that
properly reverts html5lib to seven-9's, I will gladly review and test it with
pip, and upload it if it looks okay.

Cheers,
-Barry


pgpvrc2qv10Fk.pgp
Description: OpenPGP digital signature

Bug#835783: marked as done (llvm-toolchain-snapshot: FTBFS: make[1]: gcc-6.1: Command not found)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 16:51:58 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #835783,
regarding llvm-toolchain-snapshot: FTBFS: make[1]: gcc-6.1: Command not found
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.)


-- 
835783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-snapshot
Version: 1:3.9~svn274438-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> make[1]: Entering directory '/<>'
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> for f in debian/*.in; do \
>   f2=$(echo $f | sed 's/\.in$//;s/X\.Y/3.9/'); \
>   echo "$f => $f2"; \
>   sed -e 's|@DEB_HOST_MULTIARCH@|x86_64-linux-gnu|g' \
>   -e "s|@OCAML_STDLIB_DIR@|/usr/lib/ocaml|g" \
>   -e "s|@LLVM_VERSION_FULL@|3.9.0|g" \
>   -e "s|@LLVM_VERSION@|3.9|g" $f > $f2; \
> done
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arc

Processed: Re: With 2.6-2 i dont have the wifi adapter in the (network-manager) list available.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #849122 [wpasupplicant] With 2.6-2 i dont have the wifi adapter in the 
(network-manager) list available.
Added tag(s) moreinfo.

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

Bug#849122: With 2.6-2 i dont have the wifi adapter in the (network-manager) list available.

[Andrew Shadura]

Control: tag -1 moreinfo

On Thu, 22 Dec 2016 20:41:31 +0100 cruncher  wrote:
> Me too, i have also that problem.
> 
> When installing 2.6-2, i cant see even the device anywhere (ifconfig nor
> network-manager), downgrading to 2.5-2+v2.4-3+b1 works again.
> 
> I'm building the driver module (8188eu) also myself for this device:
> Wifi adapter: 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n 
> Wireless
> Network Adapter

Have you resolved this issue? Could you please provide more details,
logs, anything?

-- 
Cheers,
  Andrew

Bug#823058: marked as done (libc++: FTBFS on armel: cannot compile this atomic library call yet)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 16:18:55 +
with message-id 
and subject line Bug#823058: fixed in libc++ 3.9.1-2
has caused the Debian Bug report #823058,
regarding libc++: FTBFS on armel: cannot compile this atomic library call yet
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.)


-- 
823058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libc++
Version: 3.7.0-1
Severity: serious
Justification: fails to build from source

Hi,

libc++ FTBFS on armel:

https://buildd.debian.org/status/fetch.php?pkg=libc%2B%2B&arch=armel&ver=3.7.0-1&stamp=1458134892

[...]
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/memory.cpp
In file included from ../src/memory.cpp:16:
../src/support/atomic_support.h:73:12: error: cannot compile this atomic 
library call yet
return __atomic_add_fetch(__val, __a, __order);
   ^~~
1 error generated.
debian/rules:19: recipe for target 'override_dh_auto_build' failed


Andreas
--- End Message ---
--- Begin Message ---
Source: libc++
Source-Version: 3.9.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libc++ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 16:45:20 +0100
Source: libc++
Binary: libc++1 libc++-dev libc++-test libc++abi1 libc++abi-dev libc++abi-test 
libc++-helpers
Architecture: source amd64 all
Version: 3.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libc++-dev - LLVM C++ Standard library (development files)
 libc++-helpers - LLVM C++ Standard library - build helpers
 libc++-test - LLVM C++ Standard library (test cases)
 libc++1- LLVM C++ Standard library
 libc++abi-dev - LLVM low level support for a standard C++ library (development 
fi
 libc++abi-test - libc++abi test cases
 libc++abi1 - LLVM low level support for a standard C++ library
Closes: 823058
Changes:
 libc++ (3.9.1-2) unstable; urgency=medium
 .
   * Silent a few tests on some archs to make the testsuite green.
 The testsuites are more than 5000 tests. We can live with ignoring a few
 tests.
 (Closes: #823058) even if it was a different issue
   * Remove useless libc++1.postinst, libc++1.postrm, libc++abi1.postinst
 and libc++abi1.postrm
   * Add debian/watch to detect new upstream release (but should
 not be used to retrieve sources)
Checksums-Sha1:
 61e07035be9efdce63f608fc2fd83996a6b60faa 2323 libc++_3.9.1-2.dsc
 e5854787f56d2926d1983e537afddbd0048547c9 12224 libc++_3.9.1-2.debian.tar.xz
 e5f5cfc39167759bf778d93111a73c104cd258f9 374130 libc++-dev_3.9.1-2_amd64.deb
 418bbffee23497870924dfc16a1dbba804641422 6008 libc++-helpers_3.9.1-2_all.deb
 e1b2c4ce4d8019f33bf593bce5b839cdf708912b 913450 libc++-test_3.9.1-2_amd64.deb
 871e4b155fc89585fc65ed11a2d148e2095b64c5 177440 libc++1_3.9.1-2_amd64.deb
 839d7db8bb8538a629b9f5c0eb46d56914c8f3e4 7570 libc++_3.9.1-2_amd64.buildinfo
 020591ce0f4d108c7b71d377c487ffce2cd6bf33 80716 libc++abi-dev_3.9.1-2_amd64.deb
 4dceb210f1063148d8b0e44b8d084cf1a170f15a 454174 
libc++abi-test_3.9.1-2_amd64.deb
 459546ac54b40e3df2b91b4c17c8e7b1c93d10f5 71710 libc++abi1_3.9.1-2_amd64.deb
Checksums-Sha256:
 86212d13459d36caea48aa451afca9e838cfab9ed8795a35b38cc676c3e817b5 2323 
libc++_3.9.1-2.dsc
 bb3118b60e491301d7cbee10b664f98981383886ad89e8adbacf7bdaeed475e6 12224 
libc++_3.9.1-2.debian.tar.xz
 31c06217cb1aa0caca727ded6cbec7241d7b31789700bc7863ba95dae0640e16 374130 
libc++-dev_3.9.1-2_amd64.deb
 41393973bcf2f6f9ad6368472c493aff5095afea18745fc1cfd7ceeef0def817 6008 
libc++-helpers_3.9.1-2_all.deb
 66b5997ca89e39ae921e460d4331060852e11bf1181ac8a3d8ed6fabcc12deae 913450 
libc++-test_3.9.1-2_amd64.deb
 7d6ca43cd38e5a96ce06ba5c

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

[Andrew Shadura]

On Mon, 26 Dec 2016 16:39:43 -0300 Lisandro
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer 
wrote:
> On lunes, 26 de diciembre de 2016 20:04:08 ART Andrew Shadura wrote:
> > On 26/12/16 19:28, Lisandro Damián Nicanor Pérez Meyer wrote:
> > > Thanks to Eduard Bloch at [bug] I've tried adding
> > > 
> > > [device]
> > > wifi.scan-rand-mac-address=no
> > > 
> > > to /etc/NetworkManager/NetworkManager.conf
> > > 
> > > and updating wpasupplicant... and voilá, WiFi is on again.
> > > 
> > > [bug] 
> > > 
> > > I don't know if it's a bug in the driver, NM or wpasupplicant, but at
> > > least
> > > things now work.
> > 
> > Lisandro, what NM version are you using? A related bug has been fixed by
> > mbiebl recently:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835822#67
> 
> Interesting. I was using 1.4.2-3. After trying this workaround/fix I updated 
> to 1.4.4-1 which is what I'm currently using.
> 
> Thanks!

Lisandro, could you please confirm this indeed was the issue with MAC
randomization and it indeed is solved by an NM update?

-- 
Cheers,
  Andrew

Bug#823542: marked as done (imagemagick-common: please mitigate CVE-2016-3714, remote arbitrary code execution during handling of delegates)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 16:27:26 +
with message-id <20170110162726.t4odjo57ujrco...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#823542: fixed in imagemagick 8:6.8.9.9-5+deb8u2
has caused the Debian Bug report #823542,
regarding imagemagick-common: please mitigate CVE-2016-3714, remote arbitrary 
code execution during handling of delegates
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.)


-- 
823542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick-common
Version: 8:6.8.9.9-7+b2
Severity: grave
Tags: security
Justification: user security hole

I'm sure you're already aware of
, the most serious
of the recent batch of ImageMagick vulnerabilities published at
.

There does not seem to be a full upstream fix yet, but it seems the
vulnerabilities can be mitigated by altering the policy.xml file in
imagemagick-common. The cost of this mitigation is that some obscure
file formats, and some features that perhaps shouldn't have been
implemented in the first place, are disabled.

Regards,
S

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
compare:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
convert:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
composite:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
conjure:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
display:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
identify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
import:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
mogrify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
montage:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
stream:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org

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

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

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.8.9.9-7+b2

imagemagick recommends no packages.

imagemagick suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 8:6.9.6.2+dfsg-2

Closing this RC bug for the testing/unstable branch too.

On Wed, 18 May 2016 at 21:51:15 +, Luciano Bello wrote:
>  imagemagick (8:6.8.9.9-5+deb8u2) jessie-security; urgency=high
>  .
>* ImageTragick: The coders EPHEMERAL, URL, HTTPS, MVG, MSL, TEXT,
>  SHOW, WIN, and PLT are disabled via policy.xml file, since they are
>  vulnerable to code injection. This mitigates CVE-2016-3714,
>  CVE-2016-3715, CVE-2016-3716, CVE-2016-3717, and CVE-2016-3718.

These appear to have been fixed upstream in the 6.9.3/6.9.4 era.

>  - Drop the PLT/Gnuplot decoder, which was vulnerable to command
>  injection.

Quietly fixed in 6.9.4-0 with commit
70a2cf326ed32bedee144b961005c63846541a16 "Update to the latest autoconf / 
automake"

>  - Some sanitization for input filenames in http/https delegates is
>  added.
>  - Indirect filename are now authorized by policy.
>  - Indirect reads with label:@ are prevented.
>  - Less secure coders (such as MVG, TEXT, and MSL) require explicit
>reference in the filename (e.g. mvg:my-graph.mvg).

Also all 6.9.3/6.9.4 era.

S--- End Message ---

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

On 2017-01-10 18:36:22 +0300, Sergey B Kirpichev wrote:
> On Tue, Jan 10, 2017 at 04:08:03PM +0100, Vincent Lefevre wrote:
> > I've noticed that the latest version of monit has overwritten
> > its log file (/var/log/monit.log). /var/log/monit.log.1 ends
> > on January 2 with:
> 
> How logging system configured?  journald?

Yes, the default with systemd + persistent logging.

> What happens with logfile if you do manual restart of the monit?  stop
> and start?  If you do reload?

No problems in all these cases:

# service monit restart

# service monit stop
# service monit start

# service monit reload

However...

# apt install --reinstall monit
[...]
Preparing to unpack .../monit_1%3a5.20.0-5_amd64.deb ...
Unpacking monit (1:5.20.0-5) over (1:5.20.0-5) ...
Setting up monit (1:5.20.0-5) ...
Processing triggers for systemd (232-8) ...
Processing triggers for man-db (2.7.6.1-2) ...
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
root@zira:/home/vinc17# cat /var/log/monit.log
[CET Jan 10 17:26:45] info : Starting Monit 5.20.0 daemon
[CET Jan 10 17:26:45] info : 'zira' Monit 5.20.0 started

The log file has been overwritten!

Something wrong in the postinst script?

Could this be:

install -o root -g adm -m 0640 /dev/null /var/log/monit.log

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

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

[Scott Mcdermott]

I will again reference my comment
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077#45

I'm encountering this bug without NetworkManager, wicd or anything else,
just a simple wpa_supplicant config file which has worked fine until
wpa_supplicant update and then stopped working, no other changes besides
wpa_supplicant version.

Bug#848809: Please confirm that you understood that cwltool is in danger to be removed from testing

[Andreas Tille]

Hi Michael,

I'd like to ask again whether you received my message that my attempts
to fix this bug remained unsuccessful and I gave up since I'm lacking
the needed knowledge about the upstream code.  Please make sure that
those bugs - which I consider easy to fix for an insider - will be fixed
right in time.

See you

Andreas.

-- 
http://fam-tille.de

Bug#850840: raptor: Please don't release this package with Stretch: Abandoned and unused

[Jonas Smedegaard]

Source: raptor
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Raptor 1.x has not had an upstream release in 6 years, is superceded by
Raptor 2.x, and since earlier today no other package depend on it.

Therefore, let's leave this package out of the upcoming stable release,
and since drop it altogether.

Severity set to a release-critical level.  Simply lower (or close) if
someone disagrees with this.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYdRNtAAoJECx8MUbBoAEhcbkP+wfZ/xrqwdA8+0BGuzpbEumt
wvnkQ2gqz7/WuBVF2mvdpuOv7DKxxgxqHnUL4BDblzkcdtTHp5fFEUaNyx/FcXv2
WL98JPCU+mjHcKQqm9HbA0IWn94t6dgU8welVgPdLmE2mXKFgkKjVVhJ1fac3LSK
wvJIo19/fQSr1ldTp704edFimlckl+HQeHvpPnRCPIYCbmdpy43mayBmo++5xGTu
QN9Br/H3WJN928iEuYlrTemf4yURzwh4MyraikGMo3Wb05jdnTHnH3lR9rMtj5//
AEIORwfnUuPR/n15Z4aFmrWMU+3CJZKSUI+azPJoo79NClcxG34pNoor+Cyr8d7D
tr4cMYc0Ra738KUoaLqoPGRNT38yfF0ehEgsptgaS8lM9SXkWPfo8eEMwvtCBHFm
GeCgGNG2SRjyCUqEjKofbevXrcNYVzxtnKUdepDJeBcoTC/pgLmv1xBUlvoKc2wh
VlFtjH8HRJ199a9RjD4kjfGn1o3UtzwDi6A8+6NOqRy8cB7y7gV8e+mLdsbTFUMg
dmy/cX3CSo66baAloQTj42oZ7C1LuNvxvyR0zEF0k+YTaFzxKo2rgPFf0mDY/kc6
G1Cn6mj8ENFn7W979/OO+yxGbYaEEm3aglRQtqT/AzMC/+7ruEku72YYiPRCCbkE
o6q+O6PTbLPLGBPjcU/c
=wSFn
-END PGP SIGNATURE-

Bug#850829: monit overwrites its log file

[Sergey B Kirpichev]

tags 850829 +pending
thanks

On Tue, Jan 10, 2017 at 05:28:27PM +0100, Vincent Lefevre wrote:
> However...
> 
> # apt install --reinstall monit

Oh, I see, this happens on reinstallation.

> Something wrong in the postinst script?
> Could this be:
> install -o root -g adm -m 0640 /dev/null /var/log/monit.log

Yes, thank you.  Apparently, this should be inside of "if else"
loop: logfile existence must be tested first.

Not sure what to do if it is exists.  Just nothing, or
secure file permissions and owner/group.  Probably second.

Processed: Re: Bug#850829: monit overwrites its log file

[Debian Bug Tracking System]

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

> tags 850829 +pending
Bug #850829 [monit] monit overwrites its log file
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828444: marked as done (myproxy: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 17:04:10 +
with message-id 
and subject line Bug#828444: fixed in myproxy 6.1.22-1
has caused the Debian Bug report #828444,
regarding myproxy: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: myproxy
Version: 6.1.18-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/myproxy_6.1.18-1_amd64-20160530-2112

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: myproxy
Source-Version: 6.1.22-1

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated myproxy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Dec 2016 18:34:03 +0100
Source: myproxy
Binary: myproxy libmyproxy6 libmyproxy-voms libmyproxy-dev myproxy-server 
myproxy-admin libmyproxy-doc libmyproxy-dbg myproxy-dbg
Architecture: source amd64 all
Version: 6.1.22-1
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 libmyproxy-dbg - Credential Management Service Debug Symbols
 libmyproxy-dev - Credential Management Service Development
 libmyproxy-doc - Credential Management Service Documentation
 libmyproxy-voms - Credential Management Service VOMS Library
 libmyproxy6 - Credential Management Service Library
 myproxy- Credential Management Service Client
 myproxy-admin - Credential Management Service Administration Tools
 myproxy-dbg - Credential Management Service Debug Symbols
 myproxy-server - Credential Management Service Server
Closes: 828444
Changes:
 myproxy (6.1.22-1) unstable; urgency=medium
 .
   * Update to 6.1.22
   * Port to openssl 1.1.0 (Closes: #828444)
Checksums-Sha1:
 99001fb2c96c53234101f94a2edf3a35fff7cb1b 2805 myproxy_6.1.22-1.dsc
 4dc3a6bbcd29bca5f164a3a8a21eeab637ec8ab3 653866 myproxy_6.1.22.orig.tar.gz
 4ce8e0632b15dcc6b5128fd4940ce40f1b3dc8d7 13240 myproxy_6.1.22-1.debian.tar.xz
 944c186a3f528974cc241aca8eb20b32949b7660 337560 
libmyproxy-dbg_6.1.22-1_amd64.deb
 bd5e42d81d8d92d3e7e1bc6e87dc023e608ffb60 15524 
libmyproxy-dev_6.1.22-1_amd64.deb
 975c3b6112ed09298eede973a4436e33fcaec5a1 26024 libmyproxy-doc_6.1.22-1_all.deb
 615e436ffe11aaceeff563afb93f151789942c0b 11944 
libmyproxy-voms_6.1.22-1_amd64.deb
 ea770cc51ffb5c3d2db75f2e219acc09306a742b 94424 libmyproxy6_6.1.22-1_amd64.deb
 30128ff33744497ad0de796052f484c3e7e97273 43084 myproxy-admin_6.1.22-1_amd64.deb
 c51086bd94ba6c718d3255fd08a85820473e51fe 205806 myproxy-dbg_6.1.22-1_amd64.deb
 1ab593af2819a994ceca5b1e7e5d168357d79a53 44680 
myproxy-server_6.1.22-1_amd64.deb
 3c724409efd308a326d3888bc3fb5742a42fef0d 8902 myproxy_6.1.22-1_amd64.buildinfo
 8a864a597f3225c34c9e1c42a5bb5be2a992ad49 47804 myproxy_6.1.22-1_amd64.deb
Checksums-Sha256:
 6c6bff3ce5cacfa222ed010186c2ae90640f864d74ce175a609d8254054dab92 2805 
myproxy_6.1.22-1.dsc
 7e55dcbf0f9447aa02bf0b4d5cb33e698bd331439ae9c0423c7fed454c51bf5b 653866 
myproxy_6.1.22.orig.tar.gz
 4a9285f78137c63cdff9e2a36f50c0437a8fa7512ea0c2c985879be22835b705 13240 
myproxy_6.1.22-1.debian.tar.xz
 286a5dbae04d3dafe51744b336a53482509745cfe5e778691e4c38bd5cf37ac2 337560 
libmyproxy-dbg_6.1.22-1_amd64.deb
 38dcc39a85e9c0df7726e0c04c4e21fc59f671be31c9bc56987477ab29c30

Bug#847526: marked as done (stimfit FTBFS on architectures where char is unsigned.)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 17:04:32 +
with message-id 
and subject line Bug#847526: fixed in stimfit 0.15.4-1
has caused the Debian Bug report #847526,
regarding stimfit FTBFS on architectures where char is unsigned.
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.)


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

Package: stimfit
Version: 0.15.3-1
Severity: serious
Tags: patch


From the armhf build log for the hdf5 binnmu

In file included from biosig4c++/t210/scp-decode.cpp:113:0:
biosig4c++/t210/codes.h:25:37: error: narrowing conversion of '-1' from 'int' 
to 'char' inside { } [-Wnarrowing]

arm64, armel, ppc64el, powerpc and ppc64 have the same problem.

I believe this was triggered by the move to gcc-6. At least on armhf the 
previous successful build was performed with gcc 5.


Adding an explicit typecast makes the package build. I took a quick look 
at the code to try to determine if this fix was correct but I was unable 
to determine what exactly the value in question was actually used for.


I uploaded the fix to raspbian and have attatched a debdiff.

No intent to NMU in debian.

diff -Nru stimfit-0.15.3/debian/changelog stimfit-0.15.3/debian/changelog
--- stimfit-0.15.3/debian/changelog 2016-07-14 10:12:45.0 +
+++ stimfit-0.15.3/debian/changelog 2016-12-09 00:34:10.0 +
@@ -1,3 +1,9 @@
+stimfit (0.15.3-1+rpi1) stretch-staging; urgency=medium
+
+  * Add typecast to fix build failure on architectures where char is unsigned..
+
+ -- Peter Michael Green   Fri, 09 Dec 2016 00:34:10 
+
+
 stimfit (0.15.3-1) unstable; urgency=low
 
   * Fix building with gcc-6 (Closes: #811904)
diff -Nru stimfit-0.15.3/debian/patches/fix-char-signedness.patch 
stimfit-0.15.3/debian/patches/fix-char-signedness.patch
--- stimfit-0.15.3/debian/patches/fix-char-signedness.patch 1970-01-01 
00:00:00.0 +
+++ stimfit-0.15.3/debian/patches/fix-char-signedness.patch 2016-12-09 
00:34:10.0 +
@@ -0,0 +1,14 @@
+Description: Add typecast to fix build failure on architectures where char is 
unsigned..
+Author: Peter Michael Green 
+
+--- stimfit-0.15.3.orig/src/libbiosiglite/biosig4c++/t210/codes.h
 stimfit-0.15.3/src/libbiosiglite/biosig4c++/t210/codes.h
+@@ -22,7 +22,7 @@ Foundation, Inc., 59 Temple Place - Suit
+ #ifndef __CODES_H__
+ #define __CODES_H__
+ 
+-static const char STR_END[]={-1,'\0'};
++static const char STR_END[]={(char)-1,'\0'};
+ static char STR_NULL[]=" unspecified/unknown ";
+ 
+ static alfabetic _special[]={
diff -Nru stimfit-0.15.3/debian/patches/series 
stimfit-0.15.3/debian/patches/series
--- stimfit-0.15.3/debian/patches/series1970-01-01 00:00:00.0 
+
+++ stimfit-0.15.3/debian/patches/series2016-12-09 00:34:10.0 
+
@@ -0,0 +1 @@
+fix-char-signedness.patch
--- End Message ---
--- Begin Message ---
Source: stimfit
Source-Version: 0.15.4-1

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

Debian distribution maintenance software
pp.
Christoph Schmidt-Hieber  (supplier of updated stimfit 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, 10 Dec 2016 16:55:51 +
Source: stimfit
Binary: stimfit stimfit-dbg python-stfio
Architecture: source amd64
Version: 0.15.4-1
Distribution: unstable
Urgency: low
Maintainer: Christoph Schmidt-Hieber 
Changed-By: Christoph Schmidt-Hieber 
Description:
 python-stfio - Python module to read common electrophysiology file formats.
 stimfit- Program for viewing and analyzing electrophysiological data
 stimfit-dbg - Debug symbols for stimfit
Closes: 847526
Changes:
 stimfit (0.15.4-1) unstable; urgency=low
 .
   * Fix building with gcc-6 on armhf (Closes: #847526)
   * Add channel scrolling
   * Upgrade libbiosiglite to 1.8.4
Checksums-Sha1:
 d481f6f858a82e8a1916b30e59385c9e83da2faa 2206 stimfit_0.15.4-1.dsc
 2b5577cf40cdef7ab2a975071f58ebad75f9b1d7 2599578 stimfit_0.15.4.orig.tar.gz
 a22ad

Bug#838210: marked as done (fuel-umm: fails to install: fuel-umm.postinst: cannot create /etc/init/rc-sysinit.override: Directory nonexistent)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 17:29:03 +
with message-id 
and subject line Bug#850817: Removed package(s) from unstable
has caused the Debian Bug report #838210,
regarding fuel-umm: fails to install: fuel-umm.postinst: cannot create 
/etc/init/rc-sysinit.override: Directory nonexistent
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.)


-- 
838210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fuel-umm
Version: 9.0+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package fuel-umm.
  (Reading database ... 
(Reading database ... 6852 files and directories currently installed.)
  Preparing to unpack .../fuel-umm_9.0+dfsg1-2_all.deb ...
  Unpacking fuel-umm (9.0+dfsg1-2) ...
  Setting up fuel-umm (9.0+dfsg1-2) ...
  /var/lib/dpkg/info/fuel-umm.postinst: 6: 
/var/lib/dpkg/info/fuel-umm.postinst: cannot create 
/etc/init/rc-sysinit.override: Directory nonexistent
  dpkg: error processing package fuel-umm (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   fuel-umm


cheers,

Andreas


fuel-umm_9.0+dfsg1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 9.0+dfsg1-2+rm

Dear submitter,

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

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

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

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

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

Bug#786566: schroot: Should mark bind mounts in the schroot as private

[Simon McVittie]

On Wed, 15 Jul 2015 at 12:47:48 -0500, Tyler Hicks wrote:
> Hello - I'm sending a friendly poke in hopes that I can get a review for
> my proposed patch.

This patch appears to have been applied in schroot 1.6.10-3.
However, it was marked as fixing #761435, which was previously closed
as "user mistake" (misconfiguration).

Raphaël, did you mix up the bug numbers here? I suspect you meant to
close #786566 instead?

Thanks,
S

Bug#850298: marked as pending

[Mike Gabriel]

tag 850298 pending
thanks

Hello,

Bug #850298 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:

http://git.debian.org/?p=pkg-mate/mate-polkit.git;a=commitdiff;h=a87cb7c

---
commit a87cb7ca4791b233a3d2ac7706310dca913d8a45
Author: Mike Gabriel 
Date:   Tue Jan 10 18:39:25 2017 +0100

upload to unstable (debian/1.16.0-2)

diff --git a/debian/changelog b/debian/changelog
index 918c8da..4df2719 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+mate-polkit (1.16.0-2) unstable; urgency=medium
+
+  * debian/control:
++ Drop P (mate-polkit): policykit-1-gnome, replace by polkit-1-auth-agent.
+  (Closes: #826488, #850298).
+
+ -- Mike Gabriel   Tue, 10 Jan 2017 18:37:26 +0100
+
 mate-polkit (1.16.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]

Processed: Bug#850298 marked as pending

[Debian Bug Tracking System]

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

> tag 850298 pending
Bug #850298 [src:mate-polkit] Provides: policykit-1-gnome breaks other desktop 
environments like Cinnamon
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#850843: dpkg-source in stretch cannot extract samba_3.6.5-2.dsc

[Ian Jackson]

Package: dpkg-dev
Version: 1.18.15
Severity: serious
Control: fixed -1 1.15.11

I assume that it is an important goal for dpkg-source that it should
be able to extract all source packages which previous versions of
dpkg-source created and which ended up in places like snapshot.d.o.

However, this is not the case.

I happened to have a 32-bit wheezy chroot lying around so tried it
there, and it worked.

Ian.

zealot:d> dget 
'http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc'
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  3091  100  30910 0  21626  0 --:--:-- --:--:-- --:--:-- 21767
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5.orig.tar.bz2
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100 23.3M0 23.3M0 0  2708k  0 --:--:--  0:00:08 --:--:-- 3015k
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.debian.tar.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  372k0  372k0 0  1193k  0 --:--:-- --:--:-- --:--:-- 1197k
samba_3.6.5-2.dsc:
  Good signature found
   validating samba_3.6.5.orig.tar.bz2
   validating samba_3.6.5-2.debian.tar.gz
All files validated successfully.
dpkg-source: info: extracting samba in samba-3.6.5
dpkg-source: info: unpacking samba_3.6.5.orig.tar.bz2
dpkg-source: info: unpacking samba_3.6.5-2.debian.tar.gz
dpkg-source: info: applying documentation.patch
dpkg-source: info: applying documentation2.patch
dpkg-source: info: applying fhs-filespaths.patch
dpkg-source: info: applying installswat.sh.patch
dpkg-source: info: applying pam-examples.patch
dpkg-source: info: applying README_nosmbldap-tools.patch
dpkg-source: info: applying smbclient-pager.patch
dpkg-source: info: applying undefined-symbols.patch
dpkg-source: info: applying VERSION.patch
dpkg-source: info: applying usershare.patch
dpkg-source: info: applying smbtar-bashism.patch
dpkg-source: info: applying autoconf.patch
dpkg-source: info: applying dont-build-VFS-examples.patch
dpkg-source: info: applying bug_221618_precise-64bit-prototype.patch
dpkg-source: info: applying initialize_password_db-null-deref
dpkg-source: info: applying fix-samba.ldif-syntax.patch
dpkg-source: info: applying 
bug_598313_upstream_7499-nss_wins-dont-clobber-daemons-logs.patch
dpkg-source: info: applying 
bug_387266_upstream_4104_mention-kerberos-in-smbspool-manpage.patch
dpkg-source: info: applying bug_604768_upstream_7826_drop-using-samba-link.patch
dpkg-source: info: applying bug_604768_upstream_7826_fix-WHATSNEW-link.patch
dpkg-source: info: applying waf-as-source.patch
patching file buildtools/README
patching file buildtools/bin/README
patching file buildtools/bin/waf-svn
Not deleting file buildtools/bin/waf-svn as content differs from patch
patching file buildtools/update-waf.sh
patching file buildtools/wafadmin/3rdparty/ParallelDebug.py
patching file buildtools/wafadmin/3rdparty/batched_cc.py
patching file buildtools/wafadmin/3rdparty/boost.py
patching file buildtools/wafadmin/3rdparty/fluid.py
patching file buildtools/wafadmin/3rdparty/gccdeps.py
patching file buildtools/wafadmin/3rdparty/go.py
patching file buildtools/wafadmin/3rdparty/lru_cache.py
patching file buildtools/wafadmin/3rdparty/paranoid.py
patching file buildtools/wafadmin/3rdparty/swig.py
patching file buildtools/wafadmin/3rdparty/valadoc.py
patching file buildtools/wafadmin/Build.py
patching file buildtools/wafadmin/Configure.py
patching file buildtools/wafadmin/Constants.py
patching file buildtools/wafadmin/Environment.py
patching file buildtools/wafadmin/Logs.py
patching file buildtools/wafadmin/Node.py
patching file buildtools/wafadmin/Options.py
patching file buildtools/wafadmin/Runner.py
patching file buildtools/wafadmin/Scripting.py
patching file buildtools/wafadmin/Task.py
patching file buildtools/wafadmin/TaskGen.py
patching file buildtools/wafadmin/Tools/__init__.py
patching file buildtools/wafadmin/Tools/ar.py
patching file buildtools/wafadmin/Tools/bison.py
patching file buildtools/wafadmin/Tools/cc.py
patching file buildtools/wafadmin/Tools/ccroot.py
patching file buildtools/wafadmin/Tools/compiler_cc.py
patching file buildtools/wafadmin/Tools/compiler_cxx.py
patching file buildtools/wafadmin/Tools/compiler_d.py
patching file buildtools/wafadmin/Tools/config_c.py
patching file buildtools/wafadmin/Tools/cs.py
patching file buildtools/wafadmin/Tools/cxx.py
patching file buildtools/wafadmin/Tools/d.py
patching file bu

Processed: dpkg-source in stretch cannot extract samba_3.6.5-2.dsc

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.15.11
Bug #850843 [dpkg-dev] dpkg-source in stretch cannot extract samba_3.6.5-2.dsc
Marked as fixed in versions dpkg/1.15.11.

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

Processed: dpkg-source fails to extract samba_3.6.5-2.dsc but exits status 0

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.15.11
Bug #850845 [dpkg-dev] dpkg-source fails to extract samba_3.6.5-2.dsc but exits 
status 0
Marked as fixed in versions dpkg/1.15.11.

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

Bug#850845: dpkg-source fails to extract samba_3.6.5-2.dsc but exits status 0

[Ian Jackson]

Package: dpkg-dev
Version: 1.18.15
Severity: grave
Justification: extracts with some patches unapplied - ie, data loss
Control: fixed -1 1.15.11

This bug is about the same situation as my previous bug report.  But
it is about a different problem.

Namely, dpkg-source -x on this package fails to apply all of the
patches, and then exits with status 0.

Ian.

zealot:d> dget 
'http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc'
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  3091  100  30910 0  21626  0 --:--:-- --:--:-- --:--:-- 21767
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5.orig.tar.bz2
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100 23.3M0 23.3M0 0  2708k  0 --:--:--  0:00:08 --:--:-- 3015k
dget: retrieving 
http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.debian.tar.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  372k0  372k0 0  1193k  0 --:--:-- --:--:-- --:--:-- 1197k
samba_3.6.5-2.dsc:
  Good signature found
   validating samba_3.6.5.orig.tar.bz2
   validating samba_3.6.5-2.debian.tar.gz
All files validated successfully.
dpkg-source: info: extracting samba in samba-3.6.5
dpkg-source: info: unpacking samba_3.6.5.orig.tar.bz2
dpkg-source: info: unpacking samba_3.6.5-2.debian.tar.gz
dpkg-source: info: applying documentation.patch
dpkg-source: info: applying documentation2.patch
dpkg-source: info: applying fhs-filespaths.patch
dpkg-source: info: applying installswat.sh.patch
dpkg-source: info: applying pam-examples.patch
dpkg-source: info: applying README_nosmbldap-tools.patch
dpkg-source: info: applying smbclient-pager.patch
dpkg-source: info: applying undefined-symbols.patch
dpkg-source: info: applying VERSION.patch
dpkg-source: info: applying usershare.patch
dpkg-source: info: applying smbtar-bashism.patch
dpkg-source: info: applying autoconf.patch
dpkg-source: info: applying dont-build-VFS-examples.patch
dpkg-source: info: applying bug_221618_precise-64bit-prototype.patch
dpkg-source: info: applying initialize_password_db-null-deref
dpkg-source: info: applying fix-samba.ldif-syntax.patch
dpkg-source: info: applying 
bug_598313_upstream_7499-nss_wins-dont-clobber-daemons-logs.patch
dpkg-source: info: applying 
bug_387266_upstream_4104_mention-kerberos-in-smbspool-manpage.patch
dpkg-source: info: applying bug_604768_upstream_7826_drop-using-samba-link.patch
dpkg-source: info: applying bug_604768_upstream_7826_fix-WHATSNEW-link.patch
dpkg-source: info: applying waf-as-source.patch
patching file buildtools/README
patching file buildtools/bin/README
patching file buildtools/bin/waf-svn
Not deleting file buildtools/bin/waf-svn as content differs from patch
patching file buildtools/update-waf.sh
patching file buildtools/wafadmin/3rdparty/ParallelDebug.py
patching file buildtools/wafadmin/3rdparty/batched_cc.py
patching file buildtools/wafadmin/3rdparty/boost.py
patching file buildtools/wafadmin/3rdparty/fluid.py
patching file buildtools/wafadmin/3rdparty/gccdeps.py
patching file buildtools/wafadmin/3rdparty/go.py
patching file buildtools/wafadmin/3rdparty/lru_cache.py
patching file buildtools/wafadmin/3rdparty/paranoid.py
patching file buildtools/wafadmin/3rdparty/swig.py
patching file buildtools/wafadmin/3rdparty/valadoc.py
patching file buildtools/wafadmin/Build.py
patching file buildtools/wafadmin/Configure.py
patching file buildtools/wafadmin/Constants.py
patching file buildtools/wafadmin/Environment.py
patching file buildtools/wafadmin/Logs.py
patching file buildtools/wafadmin/Node.py
patching file buildtools/wafadmin/Options.py
patching file buildtools/wafadmin/Runner.py
patching file buildtools/wafadmin/Scripting.py
patching file buildtools/wafadmin/Task.py
patching file buildtools/wafadmin/TaskGen.py
patching file buildtools/wafadmin/Tools/__init__.py
patching file buildtools/wafadmin/Tools/ar.py
patching file buildtools/wafadmin/Tools/bison.py
patching file buildtools/wafadmin/Tools/cc.py
patching file buildtools/wafadmin/Tools/ccroot.py
patching file buildtools/wafadmin/Tools/compiler_cc.py
patching file buildtools/wafadmin/Tools/compiler_cxx.py
patching file buildtools/wafadmin/Tools/compiler_d.py
patching file buildtools/wafadmin/Tools/config_c.py
patching file buildtools/wafadmin/Tools/cs.py
patching file buildtools/wafadmin/Tools/cxx.py
patching file buildtools/wafadmin/Tools/d.py
patching file buildtools/wafadmin/Tools/dbus.py
patching file buildt

Bug#839371: xine-lib-1.2: FTBFS: ./src/video_out/video_out_xcbshm.c:723: undefined reference to `xcb_poly_fill_rectangle'

[Andreas Beckmann]

Followup-For: Bug #839371
Control: tag -1 pending

Hi,

I just uploaded a NMU fixing this issue to DELAYED/2.

 xine-lib-1.2 (1.2.6-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * xcb.patch: New, from upstream, fix linking with new xcb versions.
 (Closes: #839371)
   * munmap.patch: New, correctly call munmap() on a previously mmap()ed
 location.  (Closes: #773966)
   * Drop -dbg package in favor of autogenerated -dbgsym packages.
   * Use dpkg default compression.


Andreas

Processed: Re: xine-lib-1.2: FTBFS: ./src/video_out/video_out_xcbshm.c:723: undefined reference to `xcb_poly_fill_rectangle'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #839371 [src:xine-lib-1.2] xine-lib-1.2: FTBFS: 
./src/video_out/video_out_xcbshm.c:723: undefined reference to 
`xcb_poly_fill_rectangle'
Added tag(s) pending.

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

Bug#850846: ansible: CVE-2016-9587: host to controller command execution vulnerability

[Salvatore Bonaccorso]

Source: ansible
Version: 2.2.0.0-1
Severity: grave
Tags: patch security upstream
Justification: user security hole

Hi,

the following vulnerability was published for ansible.

CVE-2016-9587[0]:
|Compromised remote hosts can lead to running commands on the Ansible
|controller

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-2016-9587
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9587
[1] https://bugzilla.novell.com/show_bug.cgi?id=1019021
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1404378
[3] 
https://github.com/ansible/ansible/commit/ec84ff6de6eca9224bf3f22b752bb8da806611ed

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#850845: dpkg-source fails to extract samba_3.6.5-2.dsc but exits status 0 [and 1 more messages]

[Ian Jackson]

Control: reassign -1 devscripts
Control: found -1 2.16.10

Ian Jackson writes ("dpkg-source fails to extract samba_3.6.5-2.dsc but exits 
status 0"):
> zealot:d> dget 
> 'http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc'
> dget: retrieving 
> http://snapshot.debian.org/archive/debian/20120513T033831Z/pool/main/s/samba/samba_3.6.5-2.dsc
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
...
> patching file buildtools/wafadmin/py3kfixes.py
> dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
> dpkg-source: info: if patch 'waf-as-source.patch' is correctly applied by 
> quilt, use 'quilt refresh' to update it
> dpkg-source: info: restoring quilt backup files for waf-as-source.patch
> dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B 
> .pc/waf-as-source.patch/ --reject-file=- < 
> samba-3.6.5/debian/patches/waf-as-source.patch gave error exit status 1
> zealot:d> echo $?
> 0

Following conversation on irc (thanks jrtc27!), this is actually not
in dpkg-source.

17:55  Diziet: the second is actually dget
17:55  dpkg-source exits with code 2 if I invoke it manually
17:55  Oh really ?
17:55  but dget swallows it
17:55  it calls system and doesn't check the result AFAICT
17:55  jrtc27: How exciting.
17:56  /usr/bin/dget:482

Indeed I have verified that dpkg-source -x on this package exits
status 2.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Processed: Re: dpkg-source fails to extract samba_3.6.5-2.dsc but exits status 0 [and 1 more messages]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 devscripts
Bug #850845 [dpkg-dev] dpkg-source fails to extract samba_3.6.5-2.dsc but exits 
status 0
Bug reassigned from package 'dpkg-dev' to 'devscripts'.
No longer marked as found in versions dpkg/1.18.15.
No longer marked as fixed in versions dpkg/1.15.11.
> found -1 2.16.10
Bug #850845 [devscripts] dpkg-source fails to extract samba_3.6.5-2.dsc but 
exits status 0
Marked as found in versions devscripts/2.16.10.

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

Bug#850298: marked as done (Provides: policykit-1-gnome breaks other desktop environments like Cinnamon)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 18:03:51 +
with message-id 
and subject line Bug#850298: fixed in mate-polkit 1.16.0-2
has caused the Debian Bug report #850298,
regarding Provides: policykit-1-gnome breaks other desktop environments like 
Cinnamon
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.)


-- 
850298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-polkit
Version: 1.16.0-1
Severity: serious

mate-polkit has Provides: policykit-1-gnome but the xdg autostart
contains
OnlyShowIn=Mate;

As a result, desktop environments like Cinnamon, which have a dependency
on policykit-1-gnome will be broken, unless the real policykit-1-gnome
package is installed.

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: mate-polkit
Source-Version: 1.16.0-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mate-polkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Jan 2017 18:37:26 +0100
Source: mate-polkit
Binary: mate-polkit-bin mate-polkit mate-polkit-common libpolkit-gtk-mate-1-0 
libmatepolkit-dev libmatepolkit-doc gir1.2-mate-polkit
Architecture: source
Version: 1.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 gir1.2-mate-polkit - GObject introspection data for mate-polkit
 libmatepolkit-dev - MATE authentication agent for PolicyKit-1 (development 
files)
 libmatepolkit-doc - MATE authentication agent for PolicyKit-1 (shared library 
API doc
 libpolkit-gtk-mate-1-0 - MATE authentication agent for PolicyKit-1 (library)
 mate-polkit - MATE authentication agent for PolicyKit-1
 mate-polkit-bin - MATE authentication agent for PolicyKit-1 (executable 
wrapper scr
 mate-polkit-common - MATE authentication agent for PolicyKit-1 (common files)
Closes: 826488 850298
Changes:
 mate-polkit (1.16.0-2) unstable; urgency=medium
 .
   * debian/control:
 + Drop P (mate-polkit): policykit-1-gnome, replace by polkit-1-auth-agent.
   (Closes: #826488, #850298).
Checksums-Sha1:
 0483f5078575fe3e9fc1465194145df6cf757831 2666 mate-polkit_1.16.0-2.dsc
 e2f5e08dfae7197efd628bb7f4658d571ad13520 6596 
mate-polkit_1.16.0-2.debian.tar.xz
Checksums-Sha256:
 9e5bc5b6f3e696a02573375a51b1355a026e0197fd4229348745eba6a2fd1b43 2666 
mate-polkit_1.16.0-2.dsc
 50b11388e642491f234e0ddc88dfb3fb6b4306e2dd92a2a9e915ab7781eb0be7 6596 
mate-polkit_1.16.0-2.debian.tar.xz
Files:
 77a896e6693ff0dc546c2ce1b0d680e1 2666 x11 optional mate-polkit_1.16.0-2.dsc
 5aff12c3a13c97703dda7dc57a9cdd58 6596 x11 optional 
mate-polkit_1.16.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYdRv0AAoJEJr0azAldxsxQzgQAKJtsctUlc+oxsMfpm8VCNXM
4GAyYhvtkhMLplxd7HdpdLiTinUkTIB0pg1cRER4RVWk5jcQcjDsAC3BbpI3FgiY
eL+Wn1hpWDNdtfkX3aJnBpx/kKTOAsSc+8jNnV0k4+0geDxzYUS9wu31I/TUe/Vb
Ry5Ar+IFp/DINxFCqGJE+56jSfd1Dq2CZCXMRctk8pJPpYXyRY5Q8+si2XHBlMXw
tRAKAkIwD2XEIYFtZRJMCZu3ls8QZ+sZgulsSCKyUKnzFqsWUs7ThXBo0fP36Rtb
kbeyQn9lJMwtyGzCfdZVSYwc0bEjd77SSJqu7UOZRf2CqR3wC9i9xU6eoymB2uSL
61S8PfmO1ADsFxzYKxwG+y2frphcXZIEgGpFLaRxTr/2+/I3lW1lTLwz72B9DR8d
t+aT+xI8NaJjPlLl3rElhRdSQDM/Zf/PtZNEX2VZ80odgm/EvbG+GAKi81i5A8vt
yLAPOROTCPlxma67+tgv3e6RyRYviNk8Eae56C+lQ1v+KtxQFgl7JmKiaJBEpMrl
qp86ZSlWTOqoj0i5WPZemrOeChfPPXhFXZTv59T8hTNe1RwVBDP1TNVcBdD3B4Cl
f9lZE/us/l62ulTKDNkrZwx6OK7pdYwjEXRd8s+uTVd9er3+1RiKIEBFqBYN4ocH
QX4Gr1dsm16gkjVE2nyl
=+dCU
-END PGP SIGNATURE End Message ---

Bug#850847: mydumper: FTBFS: unable to load addon sphinxdoc

[Aaron M. Ucko]

Source: mydumper
Version: 0.9.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of mydumper in minimal environments geared for building only
its main binary-dependent package (as on the autobuilders) have been
failing:

  dh clean --with sphinxdoc
  dh: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: ...) at (eval 
12) line 2.
  BEGIN failed--compilation aborted at (eval 12) line 2.
  
  debian/rules:13: recipe for target 'clean' failed
  make: *** [clean] Error 2

Please either conditionalize the usage of --with sphinxdoc
appropriately or move python-sphinx (and, if necessary,
python-docutils) back to the baseline Build-Depends field.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

[Lisandro Damián Nicanor Pérez Meyer]

On martes, 10 de enero de 2017 17:24:00 ART Andrew Shadura wrote:
[snip] 
> Lisandro, could you please confirm this indeed was the issue with MAC
> randomization and it indeed is solved by an NM update?

No, not solved by the NM update. To avoid the bug I still need to configure NM 
to disable randomization.

That being said I have no clue who's at fault: NM, wpa-supplicant, the wifi's 
driver or a specific mix of them.

-- 
http://www.phdcomics.com/comics/archive.php?comicid=56

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#850829: monit overwrites its log file

[Sergey B Kirpichev]

tags 850829 -pending +unreproducible
thanks

> On Tue, Jan 10, 2017 at 05:28:27PM +0100, Vincent Lefevre wrote:
> > However...
> > 
> > # apt install --reinstall monit
> 
> Oh, I see, this happens on reinstallation.

Hmm, I can't reproduce this as suggested by you.

# apt install monit
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libssl1.1
Suggested packages:
  exim4 | postfix | mail-transport-agent sysvinit-core
The following NEW packages will be installed:
  libssl1.1 monit
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,646 kB of archives.
After this operation, 4,502 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Preconfiguring packages ...
[...]
root@sid:~# systemctl restart monit
root@sid:~# cat /var/log/monit.log 
[MSK Jan 10 21:27:31] info :  New Monit id: 03a56de07d33c77d28b720c293e8b78a
 Stored in '/var/lib/monit/id'
[MSK Jan 10 21:27:31] info : Starting Monit 5.20.0 daemon
[MSK Jan 10 21:27:31] info : 'sid' Monit 5.20.0 started
[MSK Jan 10 21:28:03] info : Monit daemon with pid [971] stopped
[MSK Jan 10 21:28:03] info : 'sid' Monit 5.20.0 stopped
[MSK Jan 10 21:28:03] info : Starting Monit 5.20.0 daemon
[MSK Jan 10 21:28:03] info : 'sid' Monit 5.20.0 started
root@sid:~# apt install --reinstall monit
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/309 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 20013 files and directories currently installed.)
Preparing to unpack .../monit_1%3a5.20.0-4_amd64.deb ...
Unpacking monit (1:5.20.0-4) over (1:5.20.0-4) ...
Setting up monit (1:5.20.0-4) ...
Processing triggers for systemd (232-8) ...
root@sid:~# cat /var/log/monit.log 
[MSK Jan 10 21:27:31] info :  New Monit id: 03a56de07d33c77d28b720c293e8b78a
 Stored in '/var/lib/monit/id'
[MSK Jan 10 21:27:31] info : Starting Monit 5.20.0 daemon
[MSK Jan 10 21:27:31] info : 'sid' Monit 5.20.0 started
[MSK Jan 10 21:28:03] info : Monit daemon with pid [971] stopped
[MSK Jan 10 21:28:03] info : 'sid' Monit 5.20.0 stopped
[MSK Jan 10 21:28:03] info : Starting Monit 5.20.0 daemon
[MSK Jan 10 21:28:03] info : 'sid' Monit 5.20.0 started
[MSK Jan 10 21:30:52] info : Monit daemon with pid [1055] stopped
[MSK Jan 10 21:30:52] info : 'sid' Monit 5.20.0 stopped
[MSK Jan 10 21:30:58] info : Starting Monit 5.20.0 daemon
[MSK Jan 10 21:30:58] info : 'sid' Monit 5.20.0 started

As you can see, /var/log/monit.log was preserved.  This system was configured
with default systemd settings (i.e. no persistent logging).  Nothing wrong
happens also if I enable persistent logging, as documented in docs.

Processed: Re: Bug#850829: monit overwrites its log file

[Debian Bug Tracking System]

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

> tags 850829 -pending +unreproducible
Bug #850829 [monit] monit overwrites its log file
Removed tag(s) pending.
Bug #850829 [monit] monit overwrites its log file
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

On 2017-01-10 21:49:26 +0300, Sergey B Kirpichev wrote:
> Hmm, I can't reproduce this as suggested by you.

On my side, I've tried two other times, and each time it was
reproducible.

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

Bug#850829: monit overwrites its log file

[Sergey B Kirpichev]

On Tue, Jan 10, 2017 at 08:03:31PM +0100, Vincent Lefevre wrote:
> On 2017-01-10 21:49:26 +0300, Sergey B Kirpichev wrote:
> > Hmm, I can't reproduce this as suggested by you.
> 
> On my side, I've tried two other times, and each time it was
> reproducible.

Apparently, you have some local settings, different from
defaults.  For APT maybe or systemd/journald.

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

On 2017-01-10 17:28:27 +0100, Vincent Lefevre wrote:
> Could this be:
> 
> install -o root -g adm -m 0640 /dev/null /var/log/monit.log

According to strace, I confirm that this is executed and unlinks
the log file:

17197 execve("/usr/bin/install", ["install", "-o", "root", "-g", "adm", "-m", 
"0640", "/dev/null", "/var/log/monit.log"], [/* 140 vars */]) = 0
[...]
17197 lstat("/var/log/monit.log", {st_mode=S_IFREG|0640, st_size=255, ...}) = 0
17197 unlink("/var/log/monit.log")  = 0
17197 open("/dev/null", O_RDONLY)   = 3
17197 fstat(3, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 3), ...}) = 0
17197 open("/var/log/monit.log", O_WRONLY|O_CREAT|O_EXCL, 0600) = 4
17197 fstat(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
17197 fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
17197 mmap(NULL, 139264, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x7fdd739d5000
17197 read(3, "", 131072)   = 0
17197 fsetxattr(4, "system.posix_acl_access", 
"\2\0\0\0\1\0\6\0\377\377\377\377\4\0\0\0\377\377\377\377 
\0\0\0\377\377\377\377", 28, 0) = 0
17197 close(4)  = 0
17197 close(3)  = 0
17197 munmap(0x7fdd739d5000, 139264)= 0
17197 lchown("/var/log/monit.log", 0, 4) = 0
17197 chmod("/var/log/monit.log", 0640) = 0
17197 lseek(0, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
17197 close(0)  = 0
17197 close(1)  = 0
17197 close(2)  = 0
17197 exit_group(0) = ?
17197 +++ exited with 0 +++

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

Bug#850860: diaspora-installer: writes log files into /usr/share/diaspora/log rather than /var/log/diaspora

[Julian Gilbey]

Package: diaspora-installer
Version: 0.6.0.0+debian5
Severity: serious

This package writes its log files into /usr rather than /var/log,
which is a violation of the Debian policy.

I presume the simplest solution would be to make
/usr/share/diaspora/log be a symlink to /var/log/diaspora.  Then one
could suggest setting up a logrotate.d file to rotate the logs.

Best wishes,

   Julian

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages diaspora-installer depends on:
ii  build-essential  12.2
ii  diaspora-common  0.6.2.0+debian1+nmu1
ii  ghostscript  9.20~dfsg-1
ii  imagemagick  8:6.9.6.6+dfsg-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.6.6+dfsg-1
ii  libcurl4-openssl-dev 7.51.0-1
ii  libmagickwand-dev8:6.9.6.6+dfsg-1
ii  libpq-dev9.6.1-2
ii  libssl-dev   1.1.0c-2
ii  libxml2-dev  2.9.4+dfsg1-2.1
ii  libxslt1-dev [libxslt-dev]   1.1.29-2
ii  ruby 1:2.3.3
ii  ruby-dev 1:2.3.3
ii  ruby2.1 [ruby-interpreter]   2.1.5-4
ii  wget 1.18-4

diaspora-installer recommends no packages.

diaspora-installer suggests no packages.

-- no debconf information

Bug#848748: Sympy(+sagemath+nipy+~30 more) removal ahead

[Rebecca N. Palmer]

This involves a lot more than just sympy: the (build-)dependency chain is

execnet - sometimes FTBFS (3-4x unreproducible test failures, no known 
fix; disabling/ignoring the tests in question would probably make it 
build, but obviously isn't a real fix)

^
|
 pytest-xdist
^
|(apparently only for already-disabled tests)
|
wand <-- sorl-thumbnail willow
^
|
blockdiag - FTBFS (test mistakes annoying-but-harmless wand warning for 
an error) with patch

^
|(some indirectly)
|
actdiag brian cain chaussette dolfin fenics ffc fiat geophar ironic nipy 
nipype nova nwdiag octave-symbolic openstack-meta-packages 
python-measurement python-ws4py rabbit rabbiter sagemath seelablet 
seqdiag sfepy sphinxcontrib-actdiag sphinxcontrib-blockdiag 
sphinxcontrib-nwdiag sphinxcontrib-seqdiag sympy yt


Hence, we can save a lot more packages than just sympy by applying the 
blockdiag patch and either cutting wand->pytest-xdist or disabling 
execnet's problematic tests.

Bug#850858: diaspora-common: twitter_secret etc are stored in world-readable files

[Julian Gilbey]

Package: diaspora-common
Version: 0.6.0.0+debian5
Severity: serious

Hi Pirate,

I believe this is a security hole, but will not affect every user of
the package, hence why I have set it to Severity: serious.

During the debconf setup, you are asked (if twitter etc are selected)
for your Twitter Key and Twitter Secret (and likewise for the other
services).  (It is not immediately clear what these mean; the debconf
questions could be improved on this point, I guess.  But that's not
the focus of this bug report.)

The secret (and possibly the key as well) should not be
world-readable, but they are stored in the world-readable file
/var/cache/debconf/config.dat.  They (or at least the Secret) need to
be flagged as being passwords in the template file (Type: password
rather than Type: string).

In addition, these data are then stored in the configuration file
/var/lib/diaspora-common/diaspora.conf
However, this file is also world-readable and needs to be readable by
only those system users who need to be able to have access to this
data (perhaps the diaspora user or group www-data?).

Best wishes,

   Julian

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages diaspora-common depends on:
ii  adduser 3.115
ii  bc  1.06.95-9+b2
ii  ca-certificates 20161130
ii  curl7.51.0-1
ii  dbconfig-mysql  2.0.7
ii  debconf [debconf-2.0]   1.5.59
ii  default-mysql-server1.0.1
ii  exim4   4.88-2
ii  exim4-daemon-light [mail-transport-agent]   4.88-2
ii  lsb-base9.20161125
ii  mariadb-server-10.0 [virtual-mysql-server]  10.0.28-2
ii  net-tools   1.60+git20161116.90da8a0-1
ii  nginx-full [nginx]  1.10.2-3
ii  nodejs  4.6.1~dfsg-1
ii  postgresql  9.6+178
ii  rake10.5.0-2
ii  redis-server3:3.2.6-1
ii  ruby1:2.3.3
ii  ruby-rspec  3.5.0c3e0m0s0-1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  sudo1.8.19-1
ii  ucf 3.0036

diaspora-common recommends no packages.

Versions of packages diaspora-common suggests:
ii  easy-rsa  2.2.2-2

-- debconf information excluded

Bug#850829: monit overwrites its log file

[Vincent Lefevre]

On 2017-01-10 22:07:07 +0300, Sergey B Kirpichev wrote:
> On Tue, Jan 10, 2017 at 08:03:31PM +0100, Vincent Lefevre wrote:
> > On 2017-01-10 21:49:26 +0300, Sergey B Kirpichev wrote:
> > > Hmm, I can't reproduce this as suggested by you.
> > 
> > On my side, I've tried two other times, and each time it was
> > reproducible.
> 
> Apparently, you have some local settings, different from
> defaults.  For APT maybe or systemd/journald.

No, I don't think I have anything that should affect --reinstall.
Correct me if I'm wrong, but it seems normal that with --reinstall,
the package gets configured (ditto with an upgrade). So, it is
normal that

  install -o root -g adm -m 0640 /dev/null /var/log/monit.log

gets executed, which copies /dev/null to /var/log/monit.log, hence
the problem.

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

Bug#719401: marked as done (node-xmpp: FTBFS: Error: Module version mismatch. Expected 11, got 1.)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 20:13:49 +0100
with message-id <148407562932.2188.7841446707730483...@auryn.jones.dk>
and subject line 
has caused the Debian Bug report #719401,
regarding node-xmpp: FTBFS: Error: Module version mismatch. Expected 11, got 1.
to be marked as done.

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

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


-- 
719401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-xmpp
Version: 0.3.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130811 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> 
> WARNING: copyright-check disabled - licensecheck (from devscripts package) is 
> missing.
> 
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> vows --spec
> 
> module.js:356
>   Module._extensions[extension](this, filename);
>^
> Error: Module version mismatch. Expected 11, got 1.
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object. (/«PKGBUILDDIR»/lib/xmpp/stream_parser.js:3:13)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> make: *** [build/node-node-xmpp] Error 8

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/08/11/node-xmpp_0.3.2-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 ---
719...@bugs.debian.org
From: Jonas Smedegaard 
Subject: Re: [Pkg-javascript-devel] Bug#719401: node-xmpp: FTBFS: Error: Module 
version mismatch. Expected 11, got 1.

Version: 0.3.2-2

Quoting David Suárez (2013-08-11 13:55:18)
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

> > vows --spec
> > 
> > module.js:356
> >   Module._extensions[extension](this, filename);
> >^
> > Error: Module version mismatch. Expected 11, got 1.
> > at Module.load (module.js:356:32)
> > at Function.Module._load (module.js:312:12)
> > at Module.require (module.js:364:17)
> > at require (module.js:380:17)
> > at Object. (/«PKGBUILDDIR»/lib/xmpp/stream_parser.js:3:13)
> > at Module._compile (module.js:456:26)
> > at Object.Module._extensions..js (module.js:474:10)
> > at Module.load (module.js:356:32)
> > at Function.Module._load (module.js:312:12)
> > at Module.require (module.js:364:17)
> > make: *** [build/node-node-xmpp] Error 8

This bug seem fixed elsewhere in the chain: None of the changes for the 
subsequent 0.3.2-2 release affect the build itself.  Since this bug was 
discovered several years ago, the bug might be in vows, but hard to say 
by now.

Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private--- End Message ---

Bug#850863: node-rollup: FTBFS due to missing build-dependency on npm

[Andreas Beckmann]

Source: node-rollup
Version: 0.38.0-1
Severity: serious
Justification: fails to build from source

Hi,

node-rollup FTBFS in experimental:

 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-rollup-0.38.0'
dh_auto_build
npm install rollup rollup-plugin-buble rollup-plugin-node-resolve \
rollup-plugin-replace rollup-plugin-json rollup-plugin-string \
rollup-plugin-commonjs magic-string sourcemap-codec chalk minimist acorn \
require-relative is-reference
make[1]: npm: Command not found
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127
make[1]: Leaving directory '/build/node-rollup-0.38.0'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2


Andreas

Bug#830226: marked as done (node-xmpp: FTBFS: Cannot load StringPrep-0.6.2 bindings (using fallback). You may need to `npm install node-stringprep`)

[Debian Bug Tracking System]

Your message dated Tue, 10 Jan 2017 20:26:49 +0100
with message-id <148407640976.2188.1665937103441...@auryn.jones.dk>
and subject line Re: Bug#830226: node-xmpp: FTBFS: Cannot load StringPrep-0.6.2 
bindings (using fallback). You may need to `npm install node-stringprep`
has caused the Debian Bug report #830226,
regarding node-xmpp: FTBFS: Cannot load StringPrep-0.6.2 bindings (using 
fallback). You may need to `npm install node-stringprep`
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.)


-- 
830226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-xmpp
Version: 0.3.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

node-xmpp fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'node-xmpp-build-deps' in 
'../node-xmpp-build-deps_0.3.2-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package node-xmpp-build-deps.
  (Reading database ... 23095 files and directories currently installed.)
  Preparing to unpack node-xmpp-build-deps_0.3.2-2_all.deb ...
  Unpacking node-xmpp-build-deps (0.3.2-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
ca-certificates cdbs dh-buildinfo libicu52 libjs-inherits libssl-dev libuv1
libuv1-dev node-bindings node-debug node-diff node-eyes node-glob
node-inherits node-lru-cache node-ltx node-minimatch node-nan
node-node-expat node-node-stringprep node-once node-sax node-sigmund
node-vows nodejs nodejs-dev openssl zlib1g-dev
  Suggested packages:
node-easysax node-xml
  Recommended packages:
libssl-doc coffeescript
  The following NEW packages will be installed:
ca-certificates cdbs dh-buildinfo libicu52 libjs-inherits libssl-dev libuv1
libuv1-dev node-bindings node-debug node-diff node-eyes node-glob
node-inherits node-lru-cache node-ltx node-minimatch node-nan
node-node-expat node-node-stringprep node-once node-sax node-sigmund
node-vows nodejs nodejs-dev openssl zlib1g-dev
  0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 13.9 MB of archives.
  After this operation, 54.8 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 
[80.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 dh-buildinfo all 
0.11+nmu1 [18.1 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b1 [206 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libssl-dev amd64 
1.0.2h-1 [1544 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libuv1 amd64 1.9.1-1 
[84.3 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libuv1-dev amd64 
1.9.1-1 [102 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 openssl amd64 
1.0.2h-1 [681 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 ca-certificates all 
20160104 [200 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 nodejs amd64 
4.4.7~dfsg-2 [3408 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 nodejs-dev amd64 
4.4.7~dfsg-2 [496 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 node-eyes all 
0.1.8-1 [9602 B]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 node-diff all 
1.4.0~dfsg-1 [14.8 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 node-lru-cache all 
2.3.1-1 [5344 B]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 node-sigmund all 
1.0.0-1 [3750 B]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 node-minimatch all 
1.0.0-1 [13.9 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 libjs-inherits all 
2.0.1-3 [2682 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 node-inherits all 
2.0.1-3 [3568 B]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 node-once all 
1.1.1-1 [2552 B]
  Get:19 http://httpredir.debian.org/de

Bug#850229: dune-grid: FTBFS (not enough slots available)

[Graham Inggs]

On 5 January 2017 at 13:46, Ansgar Burchardt  wrote:
> On my laptop with 4 cores + HT (so 8 threads), I see `mpirun` complain
> once I start more than 4 processes, i.e. more processes than real
> cores.  Did you count threads or cores when you tried?

I haven't been able to duplicate that behaviour ('not enough slots
available' with more than enough CPUs available) on any real hardware.
I think I must have seen that message on the Ubuntu autopkgtest
runners which are single core cloud instances, not quad core machines
like their buildds, and been confused.

Bug#850874: ark: CVE-2017-5330: Unintended execution of scripts and executable files

[Salvatore Bonaccorso]

Source: ark
Version: 4:16.08.3-1
Severity: grave
Tags: upstream patch security fixed-upstream
Justification: user security hole
Forwarded: https://bugs.kde.org/show_bug.cgi?id=374572

Hi,

the following vulnerability was published for ark.

CVE-2017-5330[0]:
unintended execution of scripts and executable files

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-2017-5330
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5330
[1] https://bugs.kde.org/show_bug.cgi?id=374572
[2] 
https://cgit.kde.org/ark.git/commit/?id=82fdfd24d46966a117fa625b68784735a40f9065

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#848748: Sympy(+sagemath+nipy+~30 more) removal ahead

[Yaroslav Halchenko]

On Tue, 10 Jan 2017, Rebecca N. Palmer wrote:

> blockdiag - FTBFS (test mistakes annoying-but-harmless wand warning for an
> error) with patch
> ^
> |(some indirectly)

For me it FTBFS in a clean chroot with a gzillion of failed tests
-- all of those due to missing python{,3}-olefile in Build-Depends.

So is anyone up for preparing a quick NMU with Rebecca's patch and
olefile added, or I would do it...

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

Processed: reassign 850559 to libdune-common-dev, reassign 850229 to libdune-common-dev, merging 850229 850559

[Debian Bug Tracking System]

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

> reassign 850559 libdune-common-dev 2.5.0-1
Bug #850559 [src:dune-pdelab] dune-pdelab: FTBFS (not enough slots available)
Bug reassigned from package 'src:dune-pdelab' to 'libdune-common-dev'.
No longer marked as found in versions dune-pdelab/2.5.0~20161204gdb53a76-3.
Ignoring request to alter fixed versions of bug #850559 to the same values 
previously set
Bug #850559 [libdune-common-dev] dune-pdelab: FTBFS (not enough slots available)
Marked as found in versions dune-common/2.5.0-1.
> reassign 850229 libdune-common-dev 2.5.0-1
Bug #850229 [src:dune-grid] dune-grid: FTBFS (not enough slots available)
Bug reassigned from package 'src:dune-grid' to 'libdune-common-dev'.
No longer marked as found in versions dune-grid/2.5.0-1.
Ignoring request to alter fixed versions of bug #850229 to the same values 
previously set
Bug #850229 [libdune-common-dev] dune-grid: FTBFS (not enough slots available)
Marked as found in versions dune-common/2.5.0-1.
> merge 850229 850559
Bug #850229 [libdune-common-dev] dune-grid: FTBFS (not enough slots available)
Bug #850559 [libdune-common-dev] dune-pdelab: FTBFS (not enough slots available)
Merged 850229 850559
> thanks
Stopping processing here.

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