Bug#870036: Please build-depend on ocamlbuild

[Stéphane Glondu]

Package: src:dochelp
Version: 0.1.5
Severity: important
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.05.0-transition

Dear maintainer,

dochelp uses ocamlbuild. To ease a future transition to ocaml 4.05.0,
where ocamlbuild is a separate package, please add it to
Build-Depends. The dependency is fullfilled by ocaml-nox 4.02.3-10 at
the moment.

Cheers,

-- 
Stéphane

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

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

Bug#870037: Please build-depend on ocamlbuild

[Stéphane Glondu]

Package: src:zeroinstall-injector
Version: 2.12-4
Severity: important
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.05.0-transition

Dear maintainer,

zeroinstall-injector uses ocamlbuild. To ease a future transition to
ocaml 4.05.0, where ocamlbuild is a separate package, please add it to
Build-Depends. The dependency is fullfilled by ocaml-nox 4.02.3-10 at
the moment.

Cheers,

-- 
Stéphane

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

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

Bug#859177: meson is unuseable for package cross compilation

[Michael Biebl]

Am 28.07.2017 um 22:06 schrieb Helmut Grohne:

>  2. The debcrossgen.py script needs some place to live. When debhelper
> and meson are installed together, it needs to be in the filesystem.
> An easy approach to do so is to put it into the meson binary
> package. We should probably spend a little discussing bike shedding
> questions such as:
>  a. What path/filename to use?
>  b. What options/arguments should it take?
>  3. debhelper needs to call debcrossgen.py during cross compilation and
> add the --cross-file option. This one is straight forward to
> implement once the questions from 2. are answered.

My gut feeling is, that this functionality should be shipped in
debhelper directly, specifically in the meson build system class [1].
debhelper is written in perl, and I don't think we want to add a
dependency on Python. But the  debcrossgen.py code looks straightforward
enough to be ported to perl.

That said, if Jussi thinks that this script might be useful for other
distros / use cases, then shipping it upstream in the meson package
might be an option as well.

Jussi, what would you prefer?

Michael


[1]
https://anonscm.debian.org/git/debhelper/debhelper.git/tree/Debian/Debhelper/Buildsystem/meson.pm


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



signature.asc
Description: OpenPGP digital signature

Bug#870018: [Pkg-openssl-devel] Bug#870018: openssl: SIGSEGV/coredump on process stop when TLS is enabled in kamailio

[Kurt Roeckx]

On Sat, Jul 29, 2017 at 12:12:16AM +0200, Michael Prokop wrote:
> 
> Kurt, do you have any ideas what might go wrong in OPENSSL_cleanup
> here and how this could be fixed? We'd appreciate any hints. Thanks!

I don't see anything obvious wrong. From what I understand it
calls exit(0) from a SIGTERM handler.

The only suggestion I have is that you try to run this under
valgrind or something.

Also feel free to open a github issue about this.


Kurt

Bug#870038: python-future: please prefer Python3 binding when both versions are installed

[Gianfranco Costamagna]

Package: python-future
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch
Version: 0.15.2-4
Severity: important
Tags: patch

  * d/*.postinst: Prefer Python 3 version if both versions installed.


Thanks for considering the attached patch.

We don't want more Python2 stuff pulled in in our systems :)

thanks

Gianfranco
diff -Nru python-future-0.15.2/debian/python3-future.postinst 
python-future-0.15.2/debian/python3-future.postinst
--- python-future-0.15.2/debian/python3-future.postinst 2016-09-23 
13:53:41.0 +0200
+++ python-future-0.15.2/debian/python3-future.postinst 2017-07-27 
14:22:52.0 +0200
@@ -3,8 +3,8 @@
 set -e
 
 if [ "$1" = "configure" ] ; then
-   update-alternatives --install /usr/bin/futurize futurize 
/usr/bin/python3-futurize 200
-   update-alternatives --install /usr/bin/pasteurize pasteurize 
/usr/bin/python3-pasteurize 200
+   update-alternatives --install /usr/bin/futurize futurize 
/usr/bin/python3-futurize 300
+   update-alternatives --install /usr/bin/pasteurize pasteurize 
/usr/bin/python3-pasteurize 300
 fi
 
 #DEBHELPER#
diff -Nru python-future-0.15.2/debian/python-future.postinst 
python-future-0.15.2/debian/python-future.postinst
--- python-future-0.15.2/debian/python-future.postinst  2016-09-23 
13:53:41.0 +0200
+++ python-future-0.15.2/debian/python-future.postinst  2017-07-27 
14:22:44.0 +0200
@@ -3,8 +3,8 @@
 set -e
 
 if [ "$1" = "configure" ] ; then
-   update-alternatives --install /usr/bin/futurize futurize 
/usr/bin/python2-futurize 300
-   update-alternatives --install /usr/bin/pasteurize pasteurize 
/usr/bin/python2-pasteurize 300
+   update-alternatives --install /usr/bin/futurize futurize 
/usr/bin/python2-futurize 200
+   update-alternatives --install /usr/bin/pasteurize pasteurize 
/usr/bin/python2-pasteurize 200
 fi
 
 #DEBHELPER#


signature.asc
Description: OpenPGP digital signature

Bug#859177: meson is unuseable for package cross compilation

[Michael Biebl]

Am 29.07.2017 um 09:12 schrieb Michael Biebl:

> My gut feeling is, that this functionality should be shipped in
> debhelper directly, specifically in the meson build system class [1].
> debhelper is written in perl, and I don't think we want to add a
> dependency on Python. But the  debcrossgen.py code looks straightforward
> enough to be ported to perl.

While generating a (temporary) cross.txt file is not a huge deal, being
able to directly pass the necessary options to meson via command line
options would be a tad nicer.

Jussi, would this be hard to implement? Is there a good reason why
cross-compilation uses a separate file?


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



signature.asc
Description: OpenPGP digital signature

Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

[Neil Redgate]

On Fri, 28 Jul 2017 14:03:29 -0400 gregor herrmann 
wrote:
> Control: reassign -1 sql-ledger 3.0.8-1
> Control: tag -1 + upstream buster sid
> 
> On Fri, 28 Jul 2017 16:05:11 +0100, Dominic Hargreaves wrote:
> 
> > > > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231]
[client ::1:40500]
> > > > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC
contains: /etc/perl
> > > > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0
/usr/local/share/perl/5.26.0
> > > > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5
/usr/lib/x86_64-linux-
> > > > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > > > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-
ledger/login.pl line
> > > > 119.: /usr/local/sql-ledger/login.pl
> > > > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231]
[client ::1:40500] End
> > > > of script output before headers: login.pl
> 
> [..]
> 
> > I noticed that we do have an sql-ledger package in Debian, but that
> > hasn't been updated since before the @INC fix was made, so it's
quite
> > likely to also be completely broken there.
> 
> Sorry for missing the (not used by the reporter) packaged version;
> and yes, AFAICS it has the same problem:
> 
> https://sources.debian.net/src/sql-ledger/3.0.8-1/login.pl/
> line 120
> 
> Reassigning the bug now.
>  
> Cheers,
> gregor
> 
> -- 
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801
8649 AA06
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software
Foundation Europe
>`-   

Gregor / Dominic

Thank you for your quick reply.

I am disappointed to learn that this problem is not fixable but at
least I know what the situation is.
I will attempt to let the sql-ledger developer know of the situation
though I am not a subscriber to their forum.
The alternative is to try and find an equal alternative to sql-ledger
(not very hopeful)

Can you confirm that perl 5.26 is being applied on all OS - windows,
mac & linux?
Is it possible to have both perl 5.24 and 5.26 running on the same
linux system?

very many thanks for all your help
Neil


-- 

  
  


Neil Redgate

Bug#870039: cmake-extras: please fix testsuite or switch back to Python2 implementation

[Gianfranco Costamagna]

Package: cmake-extras
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch
Version: 1.3+17.04.20170310-1
Severity: important
Tags: patch


Hello, seems that the Python3 patch makes the testsuite fail at least in 
includechecker test
Test project /tmp/autopkgtest.9GbBdi/autopkgtest_tmp/tmp.ElVNN8WK3w/build
Start 1: good-header-test
1/3 Test #1: good-header-test .   Passed0.00 sec
Start 2: bad-header-test
2/3 Test #2: bad-header-test ..   Passed0.00 sec
Start 3: demolib-include-check
3/3 Test #3: demolib-include-check ***Failed0.22 sec

67% tests passed, 1 tests failed out of 3

Total Test time (real) =   0.22 sec

The following tests FAILED:
  3 - demolib-include-check (Failed)
Errors while running CTest
Makefile:72: recipe for target 'test' failed
Failed: Unexpected exit value 2, expected 0
make: *** [test] Error 8


Can you please fix or revert?

You might find useful my trick to have a more verbose test output, otherwise it 
might be not trivial to understand/fix

debdiff attached

G.
diff -Nru cmake-extras-1.3+17.04.20170310/debian/changelog 
cmake-extras-1.3+17.04.20170310/debian/changelog
--- cmake-extras-1.3+17.04.20170310/debian/changelog2017-07-21 
11:43:00.0 +0200
+++ cmake-extras-1.3+17.04.20170310/debian/changelog2017-07-28 
19:49:19.0 +0200
@@ -1,3 +1,11 @@
+cmake-extras (1.3+17.04.20170310-1ubuntu1) artful; urgency=medium
+
+  * Switch back to Python2 implementation, the Python3 switch breaks
+testsuite.
+  * More verbosity in failing test.
+
+ -- Gianfranco Costamagna   Fri, 28 Jul 2017 
19:49:19 +0200
+
 cmake-extras (1.3+17.04.20170310-1) unstable; urgency=medium
 
   * Initial upload to Debian. (Closes: #863191).
diff -Nru cmake-extras-1.3+17.04.20170310/debian/control 
cmake-extras-1.3+17.04.20170310/debian/control
--- cmake-extras-1.3+17.04.20170310/debian/control  2017-05-23 
12:16:00.0 +0200
+++ cmake-extras-1.3+17.04.20170310/debian/control  2017-07-28 
19:49:19.0 +0200
@@ -16,7 +17,7 @@
 Multi-Arch: foreign
 Depends: ${misc:Depends},
  cmake (>= 3.1),
- python3,
+ python,
 Description: Extra CMake utility modules
  CMake modules which are used for Ubuntu development. In Debian, this package 
is
  helpful when porting Ubuntu originated software to Debian.
diff -Nru cmake-extras-1.3+17.04.20170310/debian/patches/series 
cmake-extras-1.3+17.04.20170310/debian/patches/series
--- cmake-extras-1.3+17.04.20170310/debian/patches/series   2017-05-23 
10:26:03.0 +0200
+++ cmake-extras-1.3+17.04.20170310/debian/patches/series   2017-07-28 
19:49:19.0 +0200
@@ -1,3 +1,3 @@
 0001_73_72.patch
 0002_74_73.patch
-1001_ensure-python3-usage.patch
+#1001_ensure-python3-usage.patch
diff -Nru cmake-extras-1.3+17.04.20170310/debian/tests/includechecker 
cmake-extras-1.3+17.04.20170310/debian/tests/includechecker
--- cmake-extras-1.3+17.04.20170310/debian/tests/includechecker 2017-05-23 
09:40:12.0 +0200
+++ cmake-extras-1.3+17.04.20170310/debian/tests/includechecker 2017-07-28 
19:49:17.0 +0200
@@ -28,10 +28,10 @@
 
   (
 cd "${bindir}"
-cmake $@ -DCMAKE_INSTALL_PREFIX="${installdir}" "${srcdir}" > /dev/null
-make > /dev/null
+cmake $@ -DCMAKE_INSTALL_PREFIX="${installdir}" "${srcdir}"
+make
 set +e
-make test &> /dev/null
+make test
 retval=$?
 set -e
 


signature.asc
Description: OpenPGP digital signature

Bug#870040: eccodes FTBFS with cmake 3.9.0

[Adrian Bunk]

Source: eccodes
Version: 2.4.0-2
Severity: serious

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

...
CMake Error at cmake/contrib/FindNetCDF4.cmake:206 (else):
  A duplicate ELSE command was found inside an IF block.
Call Stack (most recent call first):
  cmake/FindNetCDF.cmake:94 (find_package)
  cmake/ecbuild_add_option.cmake:266 (find_package)
  CMakeLists.txt:60 (ecbuild_add_option)


-- Configuring incomplete, errors occurred!

Bug#870041: ceres-solver FTBFS on mips*: bundle_adjustment_test (OTHER_FAULT)

[Adrian Bunk]

Source: ceres-solver
Version: 1.13.0~rc1~dfsg0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=ceres-solver&suite=sid

...
E0728 13:40:49.988039 29822 trust_region_minimizer.cc:91] Terminating: Number 
of consecutive invalid steps more than 
Solver::Options::max_num_consecutive_invalid_steps: 5
F0728 13:40:50.103992 29822 test_util.h:175] Check failed: 
summary.termination_type != ceres::FAILURE (2 vs. 2) 
*** Check failure stack trace: ***
@ 0x77271880  google::LogMessage::Fail()
@ 0x7727440c  google::LogMessage::SendToLog()
@ 0x772712cc  google::LogMessage::Flush()
@ 0x77274f5c  google::LogMessageFatal::~LogMessageFatal()
@ 0x55a64ea0  (unknown)
@ 0x55a5cc5c  (unknown)
@ 0x55bf934c  (unknown)
@ 0x55be6e70  (unknown)
@ 0x55be7298  (unknown)
@ 0x55be7588  (unknown)
@ 0x55be8648  (unknown)
@ 0x55be8b48  (unknown)
@ 0x55a5c10c  (unknown)
@ 0x76e964c8  __libc_start_main


99% tests passed, 1 tests failed out of 75

Total Test time (real) = 902.60 sec

The following tests FAILED:
 75 - bundle_adjustment_test (OTHER_FAULT)
Errors while running CTest
Makefile:76: recipe for target 'test' failed
make[1]: *** [test] Error 8

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Lisandro Damián Nicanor Pérez Meyer wrote:

> forwarded 841951 https://bugreports.qt.io/browse/QTBUG-58910
> thanks
> 
> Erik: if possible please subscribe to the upstream bug, maybe we can
> iron out another bug in the process.

To fix this issue locally, I have force (ie, quick and dirty) installed a
patched version of libqxcb-glx-integration.so, but every time I update that
package it breaks bitcoin-qt.

Since upstream seem to be in no hurry to fix this, can debian not ship 
a patched version, at least until upstream fixes it?

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: czc...@debian.org debian-qt-...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "gsettings-qt".

 * Package name: gsettings-qt
   Version : 0.1+16.04.20170729-1
   Upstream Author : Canonical Ltd.
 * URL : https://launchpad.net/gsettings-qt
 * License : LGPL-3
   Section : libs


  It builds those binary packages:

 libgsettings-qt-dev - Library to access GSettings from Qt - devel
 libgsettings-qt1 - Library to access GSettings from Qt
 qtdeclarative5-gsettings1.0 - QML Bindings for GSettings

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/gsettings-qt

  Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/g/gsettings-qt/
gsettings-qt_0.1+16.04.20170729-1.dsc

  Alternatively, one can view build status on deb-o-matic amd64:
dget -x http://debomatic-amd64.debian.net/debomatic/unstable/pool/
gsettings-qt_0.1+16.04.20170729-1/gsettings-qt_0.1+16.04.20170729-1.dsc

  Git packaging repository can be found on Alioth:
https://anonscm.debian.org/git/collab-maint/gsettings-qt.git

  Changes since last upload:

 gsettings-qt (0.1+16.04.20170729-1) unstable; urgency=medium
 .
   * Initial Release in Debian. (Closes: #870031)
   * Fix FTBFS problem due to incorrect link path. (LP: #1706682)

Regards,
Boyuan Yang

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

Bug#870043: ruby-psych FTBFS: It seems your ruby installation is missing psych (for YAML output).

[Adrian Bunk]

Source: ruby-psych
Version: 2.2.4-2
Severity: serious

https://buildd.debian.org/status/package.php?p=ruby-psych&suite=sid

...
dh_auto_clean
dh_ruby --clean
   dh_ruby --clean
jruby -S rake clean
/usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in 
`require':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
rake aborted!
LoadError: no such file to load -- psych
/<>/Rakefile:1:in `(root)'
/<>/Rakefile:13:in `block in (root)'
(See full trace by running task with --trace)
debian/rules:24: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1

Bug#867017: src:python-pysam: FTBFS during rebuild for python3.6 transition

[Andreas Tille]

Hi Steve,

thanks a lot for your investigations.  I just uploaded.

Kind regards

  Andreas.

On Fri, Jul 28, 2017 at 11:37:38PM -0700, Steve Langasek wrote:
> 
> Well, and one more.  This package now built fine, but the autopkgtests
...

-- 
http://fam-tille.de

Bug#865417: Reply to bud 865417

[Jan Leinveber]

Hello
I had same problem. Solved with restoring bios secure boot to setup mode.

Bug#870044: src:python-django-extra-views: Please adopt the git repo to the policy

[Jochen Sprickerhof]

Package: src:python-django-extra-views
Severity: minor

Dear Maintainer,

Could you please adopt the git tags in your repo in [1] to the policy [2]?

Thanks!

Jochen

[1] 
https://anonscm.debian.org/cgit/python-modules/packages/python-django-extra-views.git
[2] https://python-modules.alioth.debian.org/policy.html#id6

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#870045: pbuilder: Fail to create an i386 build under amd64

[Christian Marillat]

Package: pbuilder
Version: 0.228.7
Severity: normal

Dear Maintainer,

I've several pbuilder build and today I need to install an i386 build for my
amd64 machine and pbuilder fail :

I: Extracting zlib1g...
W: Failure trying to run: chroot /home/marillat/src/unstable/build//22489 
dpkg-deb -f /var/cache/apt/archives/dpkg_1.18.24_i386.deb Version
W: See /home/marillat/src/unstable/build//22489/debootstrap/debootstrap.log for 
details
W: Failure trying to run: chroot /home/marillat/src/unstable/build//22489 mount 
-t proc proc /proc
W: See /home/marillat/src/unstable/build//22489/debootstrap/debootstrap.log for 
details
E: debootstrap failed
W: Aborting with an error
I: cleaning the build env 
I: removing directory /home/marillat/src/unstable/build//22489 and its 
subdirectories


Christian

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

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

Versions of packages pbuilder depends on:
ii  debconf  1.5.63
ii  debootstrap  1.0.91
ii  dpkg-dev 1.18.24
ii  wget 1.19.1-4

Versions of packages pbuilder recommends:
ii  devscripts  2.17.9
pn  eatmydata   
ii  fakeroot1.21-3.1
ii  iproute24.9.0-1
ii  net-tools   1.60+git20161116.90da8a0-1
ii  sudo1.8.20p2-1

Versions of packages pbuilder suggests:
pn  cowdancer   
pn  gdebi-core  

-- debconf information excluded

Bug#845054: openscenegraph-3.4 FTBFS on armel

[Alberto Luaces]

Emilio Pozuelo Monfort writes:

> I believe the attached patch should fix this bug (untested). The problem is 
> that
> Qt is using GLES on armel, but you're using big GL, and you can't mix them.

Emilio, thank you for investigating the issue and for the patch.  It
will be included in the next 3.4.1 release.

Bug#869742: openscenegraph-3.4: GLESv2 detection compatibility with cmake >= 3.8

[Alberto Luaces]

Steve Langasek writes:

> The attached patch maintains compatibility with current cmake, while
> continuing to use GLES instead of GL on armhf.  Despite the hard-coding of
> paths this should remain fairly reliable on Debian armhf systems.
>

Thank you for the patch, Steve.  I will apply it in the incoming 3.4.1
release.

>
> You also have bug #852423 filed which is asking to use libGL instead of
> libGLESv2.  I think that would be generally disadvantageous for ARM users of
> Debian, since there exist hardware-accelerated GLES drivers for ARM but
> TTBOMK no hardware-accelerated GL drivers.  If you did decide to switch back
> to libGL, then you could also close this bug (though Ubuntu would carry a
> delta in order to continue leveraging GLES).

I agree with you.  I have done some additional research, and I will post
the conclusions there.

Bug#870046: deutex: missing build dependency on docbook-xml

[Adrian Bunk]

Source: deutex
Version: 5.0.0~beta.25.0.0~beta.2-2
Severity: serious

https://buildd.debian.org/status/package.php?p=deutex&suite=sid

...
   dh_auto_build -a -O--with-autoreconf
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in man
make[3]: Entering directory '/<>/man'
a2x -f manpage deutex.txt
a2x: ERROR: "xmllint" --nonet --noout --valid "/<>/man/deutex.xml" 
returned non-zero exit status 4
Makefile:481: recipe for target 'deutex.6' failed
make[3]: *** [deutex.6] Error 1

Bug#870047: imagemagick FTBFS: coders/mat.c:1372:3: error: 'else' without a previous 'if'

[Adrian Bunk]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-14
Severity: serious

https://buildd.debian.org/status/package.php?p=imagemagick&suite=sid

...
../../coders/mat.c: In function 'ReadMATImage':
../../coders/mat.c:1372:3: error: 'else' without a previous 'if'
   else
   ^~~~
Makefile:7883: recipe for target 'coders/coders_mat_la-mat.lo' failed
make[3]: *** [coders/coders_mat_la-mat.lo] Error 1

Bug#865866: libreoffice-writer crash on startup Debian 9 i386 arch

[Martin Steigerwald]

Aaron Valdes - 28.07.17, 19:49:
> How do I edit my /etc/apt/source.list in order to see older kernel versions?
> 
> # apt-cache  policy linux-image-`uname -r`
[…]

I think its best to use snapshot.debian.org for that

Thanks,
-- 
Martin

Bug#870048: ffmpeg FTBFS on big endian: test failures

[Adrian Bunk]

Source: ffmpeg
Version: 7:3.3.2-1
Severity: serious

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

...
--- /<>/tests/ref/fate/sws-pixdesc-query   2017-06-07 
02:03:56.0 +
+++ tests/data/fate/sws-pixdesc-query   2017-07-26 23:25:39.32796 +
@@ -407,8 +407,8 @@
   rgb8
   rgb4
   rgb4_byte
-  abgr
-  bgra
+  argb
+  rgba
   rgb48be
   rgb48le
   rgb565be
@@ -427,8 +427,8 @@
   bgr8
   bgr4
   bgr4_byte
-  argb
-  rgba
+  abgr
+  bgra
   bgr565be
   bgr565le
   bgr555be
Test sws-pixdesc-query failed. Look at tests/data/fate/sws-pixdesc-query.err 
for details.
/<>/tests/Makefile:219: recipe for target 'fate-sws-pixdesc-query' 
failed
make[2]: *** [fate-sws-pixdesc-query] Error 1
...
--- /<>/tests/ref/fate/filter-pixfmts-scale2017-06-07 
02:03:56.0 +
+++ tests/data/fate/filter-pixfmts-scale2017-07-26 23:48:40.358210317 
+
@@ -23,8 +23,8 @@
 gbrap10le   cf974e23f485a10740f5de74a5c8c3df
 gbrap12be   1d9b57766ba9c2192403f43967cb9af0
 gbrap12le   bb1ba1c157717db3dd612a76d38a018e
-gbrap16be   81542b96575d1fe3b239d23899f5ece3
-gbrap16le   6feb8b9da131917abe867e0eaaf07b90
+gbrap16be   a0ef6e8e79fa685fbbf9ebd6f99fe624
+gbrap16le   3d99c63ce971b645b77995017a99ac5e
 gbrpdc3387f925f972c61aae7eb23cdc19f0
 gbrp10be0277d4c3a8498d75e2783fb81379e481
 gbrp10lef3d70f8ab845c3c9b8f7452e4a6e285a
 /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
-threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
-fflags +bitexact -f image2 -vcodec pgmyuv -hwaccel none -threads 1 
-thread_type frame+slice -i 
/<>/debian/standard/tests/vsynth1/%02d.pgm -flags +bitexact 
-sws_flags +accurate_rnd+bitexact -fflags +bitexact -threads 1 -idct simple 
-dct fastint -vf format=yuv444p10be,vflip= -vcodec rawvideo -frames:v 5 
-pix_fmt yuv444p10be -frames:v 1 -f nut md5:
Test filter-pixfmts-scale failed. Look at 
tests/data/fate/filter-pixfmts-scale.err for details.
...
/<>/tests/Makefile:219: recipe for target 
'fate-filter-pixfmts-scale' failed
make[2]: *** [fate-filter-pixfmts-scale] Error 1
...
make[2]: Target 'check' not remade because of errors.
make[2]: Leaving directory '/<>/debian/standard'
dh_auto_test: make -j4 check -k returned exit code 2
debian/rules:231: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 2

Bug#870050: ffmpeg FTBFS on arm64: test failure

[Adrian Bunk]

Source: ffmpeg
Version: 7:3.3.2-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=arm64&ver=7%3A3.3.2-1&stamp=1501109730&raw=0

...
ffmpeg DCT/IDCT test

  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
  0   0   0   0   0   0   0   0 
IDCT REF-DBL: max_err=0 omse=0. ome=0. syserr=0. 
maxout=288 blockSumErr=0

 54 -33  10  21  24  33  13  -2 
 23  36  -6   1  12  13  34  33 
  5  37  18  38 -13  41  38  32 
 -4  22  28  11  13  18  10  18 
 -2   9  38 -12  10  18  -5  50 
 32  43   5  23  17  36  25 -11 
 18   9  33  -1  17   3  34 -10 
  5  23  41   0  15  10  23  29 
IDCT INT: max_err=1 omse=0.01303203 ome=0.00086172 syserr=0.0027 maxout=288 
blockSumErr=64

  1 -15  -2   2  -2  -2  -4  14 
-12  -5   2  -5  -4  -5 -16 -10 
  9  -6   5 -19  -3   7  -4   5 
 -7   5  11 -19 -18 -11  -4  -2 
-19  -6   4  19  -7  -6  -2  -3 
 -8   9  20 -13  -3  13   9  -6 
 16   8 -17 -11   4 -17   5  -7 
 -7  15  17 -16   1  16  -6  -8 
IDCT SIMPLE-C: max_err=1 omse=0.00675937 ome=-0.9375 syserr=0.0010 
maxout=288 blockSumErr=64

 44 -10  15  21  26  39  16   5 
 24  32  -5  -7  16   4  18  26 
  8  23  14  39  10  36  26  39 
 -3  24  20   1   9   7  17  32 
 -6  10  31  -9  11  30   0  51 
 33  39  -4  21  22  33  39 -24 
 20  10  46  -6  32  -9  17  -6 
 15   8  36   0   6  16  19  27 
IDCT SIMPLE-C10: max_err=1 omse=0.01278125 ome=0.00083906 syserr=0.00255000 
maxout=288 blockSumErr=64

389 498 384 389 518 345 410 436 
-95 -55-178-169 -24-105 -99-112 
 86  78  35 140  81 130  87  69 
-60 -19 -16   6 -61  14  27-109 
-38  23  20  31  84  71  70  51 
-29  44  73 -37  42  27  -2 -48 
 -6  83  16   5  18  78 134   7 
-17  20 -49 -40 -26 -86  70  63 
IDCT SIMPLE-C12: max_err=1 omse=0.11856094 ome=0.00286875 syserr=0.0259 
maxout=288 blockSumErr=64

 19 -18   5  38  75  29   2  47 
 40  77  25  18  30  19 -13  29 
 28  43 -13  31  25  18  -6  32 
 22  48  66  12   8  14  11  25 
  1   3  28   0  22  31  48  55 
 20  17  40   8  45  52  21   4 
 16  28  36   2  45  34  69  33 
 42  21   9  36  -3  17  31  24 
IDCT PR-C: max_err=1 omse=0.02551797 ome=0.00126641 syserr=0.00385000 
maxout=288 blockSumErr=64

  2  -3   0   1   2   0   0   1 
 -5  -4  -2   0  -4  -4  -4   1 
  0   1   2  -1   0  -1  -1   3 
  1   1  -2   2  -1   1   1   2 
  2  -1   0  -1   2   1   1   1 
  2  -2  -1   3   2  -2  -2   3 
  2  -2  -1   3   2  -2  -2   3 
  1   1   2   2   1   1   1   2 
IDCT FAANI: max_err=1 omse=0.00046484 ome=0.0859 syserr=0.00025000 
maxout=288 blockSumErr=64

364 346 377 372 368 377 344 368 
151 144 125 164 155 166 138 155 
152 152 143 143 146 149 145 160 
   -129-140-116-131-152-133-124-122 
   -137-142-108-144-129-151-138-138 
203 225 230 223 208 208 204 208 
225 219 258 200 213 214 244 237 
 52  53

Bug#870049: diffoscope: hangs on some LLVM bytecode files and maybe other files

[Ximin Luo]

Package: diffoscope
Version: 84
Severity: important

Dear Maintainer,

When testing rustc reproducibility:

$ for i in {1..10}; do diffoscope core-fcc113aeec9d4b78.0.bytecode.0 
core-fcc113aeec9d4b78.0.bytecode.1 | wc -l; done
# hangs first time

$ for i in {1..10}; do diffoscope --max-diff-input-lines 0 
core-fcc113aeec9d4b78.0.bytecode.0 core-fcc113aeec9d4b78.0.bytecode.1 | wc -l; 
done
# hangs after a few (3-30) tries, seems random

$ for i in {1..10}; do diff -ru <(llvm-bcanalyzer -dump 
core-fcc113aeec9d4b78.0.bytecode.0) <(llvm-bcanalyzer -dump 
core-fcc113aeec9d4b78.0.bytecode.1) | wc -l; done
# succeeds every time

When running `pstree -alup` one can see either one or both llvm-bcanalyzer 
processes running. I guess there's a race condition to do with filtering 
command output.

X

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

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

Versions of packages diffoscope depends on:
ii  python33.5.3-3
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  1:5.30-1
ii  python3-pkg-resources  36.0.1-1

Versions of packages diffoscope recommends:
ii  acl  2.2.52-3+b1
ii  apktool  2.2.3+dfsg-1
ii  binutils-multiarch   2.28-6
ii  bzip21.0.6-8.1
ii  caca-utils   0.99.beta19-2+b2
ii  colord   1.3.3-2
ii  default-jdk [java-sdk]   2:1.8-59
ii  default-jdk-headless 2:1.8-59
ii  device-tree-compiler 1.4.2-1
ii  docx2txt 1.4-0.2
ii  enjarify 1:1.0.3-3
ii  fontforge-extras 0.3-4
ii  fp-utils-3.0.2 [fp-utils]3.0.2+dfsg-4
ii  genisoimage  9:1.1.11-3+b2
ii  gettext  0.19.8.1-2+b1
ii  ghc  8.0.1-17+b1
ii  ghostscript  9.21~dfsg-1
ii  giflib-tools 5.1.4-0.4
ii  gnupg2.1.18-8
ii  imagemagick  8:6.9.7.4+dfsg-12
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-12
ii  jsbeautifier 1.6.4-6
ii  libarchive-tools 3.2.2-2
ii  llvm 1:3.8-36
ii  mono-utils   4.6.2.7+dfsg-1
ii  odt2txt  0.5-1+b2
ii  oggvideotools0.9.1-4
ii  openjdk-8-jdk [java-sdk] 8u131-b11-2
ii  openssh-client   1:7.5p1-5
ii  pdftk2.02-4+b2
ii  pgpdump  0.31-0.2
ii  poppler-utils0.48.0-2
ii  python3-argcomplete  1.8.1-1
ii  python3-debian   0.1.30
ii  python3-guestfs  1:1.34.6-2+b1
ii  python3-progressbar  2.3-4
ii  python3-rpm  4.12.0.2+dfsg1-2+b1
ii  python3-tlsh 3.4.4+20151206-1+b3
ii  r-base-core  3.3.3-1
ii  rpm2cpio 4.12.0.2+dfsg1-2+b1
ii  sng  1.1.0-1+b1
ii  sqlite3  3.19.3-3
ii  squashfs-tools   1:4.3-4
ii  tcpdump  4.9.0-3
ii  unzip6.0-21
ii  vim-common   2:8.0.0197-5
ii  xxd  2:8.0.0197-5
ii  xz-utils 5.2.2-1.3

Versions of packages diffoscope suggests:
ii  libjs-jquery  3.1.1-2

-- no debconf information

Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]

[Pino Toscano]

Hi,

I'm not uploading it myself, but there are various things that ought to
be fixed:

a) qtchooser is not needed in Build-Depends, it's an "implementation
   detail"

b) we don't use a "qtdeclarative5-" prefix for QML modules, but
   "qml-module-"

c) seen while building:
dpkg-gencontrol: warning: Depends field of package libgsettings-qt-dev: unknown 
substitution variable ${shlibs:Depends}

d) lines like "usr/lib/*/lib*.so*" are way too generic, and they will
   silently adapt to breaking changes like library renaming, or even
   SONAME bump; a way better option is:
   - libfoo1.install: "usr/lib/*/libfoo.so.1" + "usr/lib/*/libfoo.so.1.*"
   - libfoo-dev.install: "usr/lib/*/libfoo.so"

e) the descriptions could be improved:
   - short descriptions don't start with an uppercase letter
   - longer description could say something more...

f) there is no watch file, so upstream does not do releases at all?
   in this case, you need to specify in changelog that you did a new
   upstream snapshot

g) the QML example in the -dev package? that does not seem to logic to
   me, since you would install the QML package to run it, not the -dev
   (which is needed for using the C++ library)

h) all the "Pre-Depends" fields in control should not be needed anymore
   at this point

i) "Format" in copyright should be https now

j) the symbols file needs "Build-Depends-Package:"; also you added an
   entry as mangled (line 35), while the rest of the file is with
   unmangled symbols (and no old commented entries, please)

k) the tests don't seem to be run at all?

l) the package with the QML module could be "Multi-Arch: same", and
   most probably the -dev package too (but needs to be checked)

m) strictly speaking, there is no need to have this under the qt-kde
   umbrella, since you already put it under collab-maint, and the
   prospected users are other packages in the pkg-deepin team;
   collab-maint with you as single maintainer, or pkg-deepin, would
   be better choices IMHO

n) considering (f) above, the patches, and the logs of the upstream
   repository (especially that few names are not Canonical employees
   anymore), I have some doubt whether this software is still
   maintained/fixed/worked on at all, and thus that it would be
   unmaintained code in Debian right from the first upload

That should be enough notes for now; as general recommendation, please
check the build logs, and fix the lintian issues when possible (info
tags included).

-- 
Pino Toscano

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

Bug#841670: marked as done (lintian: Check udev rules and AppStream metadata)

[Niels Thykier]

Debian Bug Tracking System:
> Your message dated Sun, 23 Jul 2017 10:45:49 +
> with message-id 
> and subject line Bug#841670: fixed in lintian 2.5.52
> has caused the Debian Bug report #841670,
> regarding lintian: Check udev rules and AppStream metadata
> 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.)
> 
> 

FYI, lintian has now processed the archive with these tags enabled.

Thanks,
~Niels

Bug#837548: lintian: Should warn about PE/Windows binaries lacking security features

[Petter Reinholdtsen]

I had a look at this, but am unsure where in the lintian code it is best
to implement such change.  It would be useful with some input from the
Lintian developers on this.  The issue is still relevant, even though
the latest ming compiler changed its default, making rebuilds solve the
issue.  Here is the state from a rebuilt gzip-win32 and the version in
the archive:

% pesec gzip-1.6/debian/gzip-win32/usr/share/win32/gzip.exe
ASLR:yes
DEP/NX:  yes
SEH: yes
Stack cookies (EXPERIMENTAL):yes
% pesec /usr/share/win32/gzip.exe
ASLR:no
DEP/NX:  no
SEH: yes
Stack cookies (EXPERIMENTAL):yes
% file --mime-type /usr/share/win32/gzip.exe
/usr/share/win32/gzip.exe: application/x-dosexec
% file /usr/share/win32/gzip.exe
/usr/share/win32/gzip.exe: PE32 executable (console) Intel 80386 (stripped to 
external PDB), for MS Windows
%

The lintian check should run pesec on all Windows binaries and warn if
any of the security features are turned off.

-- 
Happy hacking
Petter Reinholdtsen

Bug#861378: lists.debian.org: Please update list description for debian-chinese-{gb,big5}

[Boyuan Yang]

在 2017年4月28日星期五 CST 下午3:25:48，Boyuan Yang 写道：
> Package: lists.debian.org
> Severity: normal
> X-Debbugs-CC: debian-chinese-b...@lists.debian.org,
> debian-chinese...@lists.debian.org
> 
> Description words for debian-chinese-gb and debian-chinese-big5 are severely
> outdated. Thus I'm seeking help to update those words.
[...]
> --
> Sincerely,
> Boyuan Yang

Ping? Is there any listmaster alive?

The need of updating list descriptions is still valid. Please try to fix them 
when possible. See Bug #861378 for details.

Sincerely,
Boyuan Yang

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

Bug#870051: qile FTBFS: test_thermalsensor_regex_compatibility failure

[Adrian Bunk]

Source: qtile
Version: 0.10.7-2
Severity: serious

https://buildd.debian.org/status/package.php?p=qtile&suite=sid

...
=== FAILURES ===
 test_thermalsensor_regex_compatibility 

def test_thermalsensor_regex_compatibility():
>   sensors = ThermalSensor()

test/test_widget.py:62: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
libqtile/widget/sensors.py:73: in __init__
temp_values = self.get_temp_sensors()
libqtile/utils.py:202: in wrapper
return_value = func(*args, **kwargs)
libqtile/widget/sensors.py:93: in get_temp_sensors
sensors_out = self.call_process(command)
libqtile/widget/base.py:262: in call_process
output = subprocess.check_output(command, **kwargs)
/usr/lib/python3.6/subprocess.py:336: in check_output
**kwargs).stdout
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

input = None, timeout = None, check = True, popenargs = (['sensors'],)
kwargs = {'stdout': -1}, process = 
stdout = b'', stderr = None, retcode = 1

def run(*popenargs, input=None, timeout=None, check=False, **kwargs):
"""Run command with arguments and return a CompletedProcess instance.

The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those 
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture 
them.

If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return 
code
in the returncode attribute, and output & stderr attributes if those 
streams
were captured.

If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.

There is an optional argument "input", allowing you to
pass a string to the subprocess's stdin.  If you use this argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.

The other arguments are the same as for the Popen constructor.

If universal_newlines=True is passed, the "input" argument must be a
string and stdout/stderr in the returned object will be strings rather 
than
bytes.
"""
if input is not None:
if 'stdin' in kwargs:
raise ValueError('stdin and input arguments may not both be 
used.')
kwargs['stdin'] = PIPE

with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired:
process.kill()
stdout, stderr = process.communicate()
raise TimeoutExpired(process.args, timeout, output=stdout,
 stderr=stderr)
except:
process.kill()
process.wait()
raise
retcode = process.poll()
if check and retcode:
raise CalledProcessError(retcode, process.args,
>output=stdout, stderr=stderr)
E   subprocess.CalledProcessError: Command '['sensors']' returned 
non-zero exit status 1.

/usr/lib/python3.6/subprocess.py:418: CalledProcessError
- Captured stderr call -
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
== 1 failed, 180 passed, 1 skipped in 352.98 seconds ===
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 
returned exit code 13
debian/rules:4: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25


You cannot expect availability and permission to access
hw sensors when building the package.

Bug#870052: git: RPC failed; curl 56 GnuTLS recv error

[Konstantin Manna]

Package: git
Version: 1:2.13.2-3
Severity: normal

Cloning a git repo via https failes with the error below.
I think it's a bug with git/it's used libaries, since reportedly running the 
same with a recompiled git with openssl instead of gnutls does not lead to an 
error.
(See 
https://stackoverflow.com/questions/38378914/git-error-rpc-failed-curl-56-gnutls)
I am not sure if this is the right place to report the error.
If so, I'd be glad if anyone refers me to the correct place.

LC_ALL=C git clone -v https://***.git
Cloning into '***'...
POST git-upload-pack (gzip 5341 to 2695 bytes)
remote: Counting objects: 226702, done.
remote: Compressing objects: 100% (62511/62511), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected 
length was received.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed


-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages git depends on:
ii  dpkg 1.18.24
ii  git-man  1:2.13.2-3
ii  libc62.24-12
ii  libcurl3-gnutls  7.52.1-5
ii  liberror-perl0.17024-1
ii  libexpat12.2.2-2
ii  libpcre3 2:8.39-3
ii  perl 5.26.0-4
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages git recommends:
ii  less 481-2.1
ii  openssh-client [ssh-client]  1:7.5p1-5
ii  patch2.7.5-1+b2

Versions of packages git suggests:
ii  gettext-base  0.19.8.1-2+b1
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#870053: Please update to recent git version

[Andrey Gursky]

Source: libstrophe
Version: 0.9.1-1
Severity: important
Tags: security

Dear maintainer,

On 4 July 2017 libstrophe has got a security update (see changelog in 
[1]). Due to missing it, profanity was thrown out from Debian Stable. 
Please consider updating libstrophe to a recent 0.9.1+git... version 
(bug fixes, new OpenSSL 1.1.0 support, compilation fix with GCC 7), 
which will also resolve [2].


[1] 
https://github.com/strophe/libstrophe/commit/666995531afc610e9fb48049c7134fe45bde0c13
[2] https://bugs.debian.org/857546   (profanity: Server certificates are 
not verified)


Thanks,
Andrey


P.S. Please reply-all or bugnumber-submit...@bugs.debian.org, so that I 
also get a reply.
P.P.S. I still cannot find what field I must set during submission to 
tell BTS to subscribe me, reporter, for this new bug, without knowing 
yet the bug number or sending additional messages later.

Bug#864884: Firefox-esr 52.2 fails to start

[Lia Williams]

Followup-For: Bug #864884
Package: firefox-esr
Version: 52.2.0esr-1~deb8u1
Severity: important

Dear Maintainer,

After updating firefox-esr from 49.9.0esr-1~deb8u1 to
52.2.0esr-1~deb8u1, I experienced
the exact same problem as Mr. Walton.  Firefox always immediately
crashes on startup,
-safe-mode or not, with the error:

(firefox-esr:8273): GLib-GObject-CRITICAL **: g_object_ref: assertion
'object->ref)count
> 0' failed
ExceptionHandler::GenerateDump cloned child 8317
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

followed by the Mozilla crash reporter dialog.  Restarting produces
the same error.

Downgrading back to 49.9.0esr-1deb8u1 resolves the issue.

I did not get the error message Mr. Levasseur received, neither did
his suggestion of
tinkering with KDE's GTK settings make any difference. However, he was
using Wheezy,
whereas Mr. Walton and I experienced this on Jessie.

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-0.bpo.3-amd64 (SMP w/2 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 firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.14.5-1+deb8u1
ii  libgtk2.0-0   2.24.25-3+deb8u2
ii  libhunspell-1.3-0 1.3.3-3
ii  libjsoncpp0   0.6.0~rc2-3.1
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.16.2-4
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-5

firefox-esr recommends no packages.

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1
pn  mozplugger 

-- no debconf information

Bug#857546: profanity: Server certificates are not verified

[Andrey Gursky]

Followup-For: Bug #857546

Hi,

libstrophe has got a fix on 4. July 2017 and I've submitted a 
corresponding bug reported [1]. So thanks to Dmitry Podgorny (pasis) 
there is no need anymore to make a package for a forked version. 
Hopefully development continues on the original libstrophe.


Regards,
Andrey

[1] https://bugs.debian.org/870053

Bug#841670: marked as done (lintian: Check udev rules and AppStream metadata)

[Petter Reinholdtsen]

[Niels Thykier]
> FYI, lintian has now processed the archive with these tags enabled.

Thank you very much!

-- 
Happy hacking
Petter Reinholdtsen

Bug#870054: freefem++: scalapack and blacs not found at build time

[Drew Parsons]

Source: freefem++
Version: 3.47+dfsg1-1
Severity: normal

blacs is about to be removed from the Debian archives, replaced by
scalapack2.0 (now in experimental).  So the configuration for the
freefem++ build will need to be updated to match. configure will need
to point the blacs library at -lscalapack$ff_with_mpi instead of
-lblacsCinit$ff_with_mpi, etc.

Actually there's another problem. Inspecting the current build logs,
neither blacs nor scalapack (the old versions currently still in
unstable) are currently being found at build time.  The logs (amd64)
report:
checking check hypre... yes
checking check superlu_dist... no
checking check superlu... yes
checking check superlu4... no
checking check blacs... no
checking check scalapack... no
checking check scotch... no
checking check ptscotch... no
checking check metis... no
checking check metis... yes
checking check parmetis... no

That should be fixed first, then it will be more clear how to
reconfigure for blacs in scalapack2.0.

Cheers,
Drew


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

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

Bug#870055: bls should also check for -mtune=native

[Adrian Bunk]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org 
Usertags: bls

The Build Log Scanner already checks for -march=native:
https://qa.debian.org/bls/bytag/E-march-native.html

It would be useful to have a similar check and error for the
(slightly less severe) -mtune=native

Bug#870056: nmu: robustirc-bridge_1.7-1

[Michael Stapelberg]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

This is the first binNMU I schedule, mostly to see how this all works before I
file a larger one.

I realized that robustirc-bridge (and other Go binary packages) were built using
the Go 1.7 compiler, and not uploaded since the Go 1.8 release. Hence, we need a
binNMU to pick up changes in the standard library between Go 1.7 and Go 1.8.

  nmu robustirc-bridge_1.7-1 . ANY . unstable . -m "rebuild using golang 1.8"

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

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

Bug#870027: shotwell: Fails to build with appstream-glib 0.7

[Jörg Frings-Fürst]

severity 870027 normal
thanks

Hello Jeremy,

thank you for spending your time helping to make Debian better with
this bug report. 

The commit will be included in the next stable version. Therefore, I
set the severity to normal.


CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#870047: imagemagick FTBFS: coders/mat.c:1372:3: error: 'else' without a previous 'if'

[Gianfranco Costamagna]

control: tags -1 patch

This should fix the issue:
https://github.com/ImageMagick/ImageMagick/pull/627

I just uploaded the patch in Ubuntu
https://launchpad.net/ubuntu/+source/imagemagick/8:6.9.7.4+dfsg-14ubuntu2

G.



signature.asc
Description: OpenPGP digital signature

Bug#870057: fail2ban: systemd kills running sendmail when stopping fail2ban.service

[Michael Lass]

Package: fail2ban
Version: 0.9.6-2
Severity: normal
Tags: upstream patch

Dear Maintainer,

fail2ban typically send emails on exit to inform about all stopped
jails. This is done by running sendmail or mail. When fail2ban.service
is stopped by systemd, it kills remaining processes in the cgroup after
the main process has exited. This can abort ongoing transfers of
outgoing mail.

In my case (running exim4), this lead to emails that were delivered
multiple times: Since exim4 was killed during mail transfer, mails
remained in the queue even if the transmission was already complete.
Mails then got resent from the queue by the running exim4 daemon.

As a workaround, "KillMode=none" can be added to fail2ban.service. I'm
not sure if this is the best solution for the problem. Since upstream
provides a similar service file, this bug may apply to upstream as well.

(Please ignore the broken debsums on
/lib/systemd/system/fail2ban.service as I temporarily implemented the
workaround directly in that file)


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.48
ii  lsb-base 9.20161125
ii  python3  3.5.3-1

Versions of packages fail2ban recommends:
ii  iptables   1.6.0+snapshot20161117-6
ii  python 2.7.13-2
ii  python3-pyinotify  0.9.6-1
ii  python3-systemd233-1
ii  whois  5.2.15

Versions of packages fail2ban suggests:
ii  mailutils [mailx]1:3.1.1-1
pn  monit
ii  rsyslog [system-log-daemon]  8.24.0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /lib/systemd/system/fail2ban.service (from fail2ban 
package)

Bug#870058: xsane failing since stretch upgrade

[Daniel Pocock]

Package: xsane
Version: 0.999-5
Severity: serious

Since upgrading to stetch, the system won't scan with xsane.

scanimage works from the command line.

In gimp, I choose my device and the popup appears:


Title: xsane 0.999
Message: scanning for devices



and then after a few seconds:


Title: Error
Message: Failed to open device
`hpaio:/net/HP_LaserJet_?zc=abcd1234': Invalid argument.




Looking at /var/log/syslog I find this:

12:45:26 xsane: io/hpmud/pml.c 348: SetPml failed ret=12
12:45:54 xsane: io/hpmud/hpmud.c 373: device_cleanup: device
uri=hp:/net/HP_LaserJet_?zc=abcd1234
12:45:54 xsane: io/hpmud/hpmud.c 385: device_cleanup: close device dd=1...
12:45:54 xsane: io/hpmud/hpmud.c 387: device_cleanup: done closing
device dd=1

Bug#870059: qupzilla: on some websites, when pressing the back-button, qupzilla crashes reproducably.

[Bernd Gruber]

Package: qupzilla
Version: 1.8.9~dfsg1-3.1
Severity: important

Dear Maintainer,

on some websites, when pressing the "Back"- button, qupzilla crashes, On these 
sites, the bug was reproducable. Re-Installing qupzilla didn't solve the 
problem. No Problem on firefox.
I have  report from kcrash.



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

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

Versions of packages qupzilla depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5script5 5.7.1~20161021+dfsg-2
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5webkit5 5.7.1+dfsg-1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqupzilla1  1.8.9~dfsg1-3.1
ii  libstdc++66.3.0-18

qupzilla recommends no packages.

qupzilla suggests no packages.

-- no debconf information

Bug#870060: bcftools FTBFS on big endian: 107 tests failed

[Adrian Bunk]

Source: bcftools
Version: 1.3.1-1
Severity: important

https://buildd.debian.org/status/package.php?p=bcftools&suite=sid

...
Number of tests:
total   .. 617
passed  .. 510
failed  .. 107

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

Bug#870061: src:humanfriendly: missing documentation package

[Ghislain Antony Vaillant]

Package: src:humanfriendly
Severity: wishlist

Dear Maintainer,

Upstream seems to provide the source for the documentation of
humanfriendly, at least in the GitHub release tarballs. I have submitted
a PR [1] to include the docs to the release tarball on PyPI.

Regardless of what source you are tracking, please consider providing a
corresponding package (python-humanfriendly-doc) with the HTML
documentation generated with Sphinx. The documentation of coloredlogs
is linked to humanfriendly's via intersphinx.

[1] https://github.com/xolox/python-humanfriendly/pull/18

Thanks,
Ghis


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Bug#857891: [logrotate does not rotate logs]

[Alessandro Vesely]

On Mon, 20 Mar 2017 21:14:39 +0100 Andreas Henriksson  wrote:
> [...]
> 
> I thus very much suspect this is an already fixed bug.

So is this bug confirmed?

TIA
Ale

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Andrey Rahmatullin]

Control: tags -1 + moreinfo
Control: owner -1 !

The project license is GPL-2 while debian/copyright says GPL-2+.
Please update to the current Standards-Version.
Please switch tot he debhelper compat level 10.
Otherwise the package seems good.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Andrey Rahmatullin]

Also, usually the License blocks are put after the Files blocks in
d/copyright.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#869198: RFS: golang-github-shibukawa-configdir/0.0~git20170330.0.e180dbd-1 [ITP]

[Andreas Moog]

On Fri, Jul 21, 2017 at 02:19:20PM +0200, Diego M. Rodriguez wrote:

I'm not a DD so can't sponsor your package. Here is a comment:

>  * Package name: golang-github-shibukawa-configdir

Your watch-file seems to be not working:

$ uscan --report
uscan warn: unrecognised option \\
uscan warn: Filename pattern missing version delimiters () without 
filenamemangle in debian/watch, skipping:  
uversionmangle=s/(\d)[_\.\-\+]?(RC|rc|pre|dev|beta|alpha)[.]?(\d*)$/\$1~\$2\$3/ 
\\
uscan warn: In debian/watch no matching files for watch line
  https://github.com/shibukawa/configdir/tags .*/v?(\d\S*)\.tar\.gz

And since on that github-page there aren't any releases, a watchfile doesn't 
seem to be needed and could just be removed?

Cheers,
  Andreas

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature

Bug#870063: ITP: node-json-schema-traverse -- Dependency of npm

[Amal Shehu]

Package: wnpp
Severity: wishlist
Owner: Amal Shehu 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-json-schema-traverse
  Version : 0.3.1
  Upstream Author : Evgeny Poberezkin
* URL :
https://github.com/epoberezkin/json-schema-traverse#readme
* License : Expat
  Programming Lang: JavaScript
  Description : This library is a dependency of npm.Traverse JSON
Schema passing each schema object to callback
 .

Bug#867145: RFS: fancon/0.11.13

[Andreas Moog]

On Tue, Jul 04, 2017 at 05:35:15PM +1000, Hayden Briese wrote:

I'm not a DD, so can't sponsor your package. Here are some comments:

> * Package name: fancon
>   Version : 0.11.13
>   Upstream Author : Hayden Briese (haydenbri...@gmail.com)
> * URL : https://github.com/hbriese/fancon
> * License : Apache Version 2.0
>   Section : utils

1. The package you created is a native package. This generally is only useful 
for software that are specifically targeted for Debian. In this case non-native 
would be the better choice. (See [1] for an explanation of native/non-native)

2. The files README and README.source still contain default text, either remove 
the files or fill them with useful information.

3. debian/fancon-docs.docs: This file is named wrong. Either name it just 
"docs" or "fancon.docs". The part before the ".docs" is the package name it 
applies to and you don't build a package named fancon-docs. (See "man 
dh_installdocs"). Also, the contents are wrong, the man-page has more
information about that as well.

4. debian/manpage.1: That doesn't look useful at all.

5. debian/copyright: the files under the cmake-directory have different 
copyright information, you need to record that as well.

6. debian/rules: Are all the overrides really needed? Then you should document 
why they are there and delete the non-used comments.

7. debian/control: 
   a) Carefully look at the Build-Depends again, some of the packages you 
  specified are already in build-essential so no need to specify them
  again.
   b) The current Standards version is 4.0.0
   c) Consider running "wrap-and-sort" from devscripts to make the 
  Depends/Build-Depends more readable

8. The package doesn't build:
In file included from /<>/src/Controller.hpp:4:0,
 from /<>/src/main.hpp:4,
 from /<>/src/main.cpp:1:
/<>/src/Devices.hpp:18:15: error: 'fancon::FanNV' has not been 
declared using fancon::FanNV;
/<>/src/Devices.hpp:21:15: error: 'fancon::SensorNV' has not been 
declared using fancon::SensorNV;

(Full buildlog at https://warperbbs.de/buildlogs/fancon.build)

Cheers,
  Andreas

[1] 
https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature

Bug#864944: RFS: zimg/2.5.1-1 [ITP]

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

Please update to the current Standards-Version.
Please switch to the debhelper compat level 10.
${shlibs:Depends} for libzimg-examples does nothing and there is a warning
about that in the build log.
Files: src/* doc/* test/* m4/* * should be replaced with just Files: *.
*.la files should not be installed.
You should disable compression for the example files.
test/extra/* should be covered in d/copyright.
The package seems to contain tests but they are not run during the build
process.
Consider providing a symbols file for the lib.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#870065: CVE-2017-11639

[Bastien ROUCARIES]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-13
Severity: important
Tags: security upstream
X-Debbugs-CC: t...@security.debian.org
control: found -1 8:6.8.9.9-5+deb8u8
control: found -1 8:6.8.9.9-5+deb8u9
control: found -1 8:6.7.7.10-5+deb7u14
control: found -1 8:6.7.7.10-5+deb9u1
forwarded: https://github.com/ImageMagick/ImageMagick/issues/588

When ImageMagick 7.0.6-1 processes a crafted file in convert, it can
lead to a heap-based buffer over-read in the WriteCIPImage() function
in coders/cip.c, related to the GetPixelLuma function in
MagickCore/pixel-accessor.h.

Bug#867009: RFS: fzf/0.16.8-2 [ITP]

[Andrey Rahmatullin]

The initial upload should have the debian revision of -1.
Please update to the current Standards-Version.
Please use the priority optional.
The .dsc file is wrong: "dpkg-source: error: file ./fzf_0.16.8.orig.tar.gz
has size 128895 instead of expected 128889".

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#870064: redir: service names from /etc/services not recognized anymore for --lport=

[Marko von Oppen]

Package: redir
Version: 3.1-1~exp1
Severity: important

Dear Maintainer,

specifying a port as a name from /etc/services does not work in Stretch version 
anymore.

In Jessie it was working fine.

Sample:
/etc/services contains
minecraft   10001/tcp   # Minecraft Server
minecraft   10001/udp   # Minecraft Server

redir ... --lport=minecraft ...
was working in Jessie but does not work in stretch

redir ... --lport=10001 ...
also works fine in Stretch

I suppose deactivating support for service names was not intended.

Best regards
Marko


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages redir depends on:
ii  libc6  2.24-11+deb9u1

redir recommends no packages.

redir suggests no packages.

-- no debconf information

Bug#868431: wmaker: uses static upstream menu

[Andreas Metzler]

On 2017-07-24 Doug Torrance  wrote:
> On 07/23/2017 08:58 PM, Doug Torrance wrote:
> > I'll work on a draft and push it to git for review.

> Done.

Hello,

Thank you, I have not yet completely tested the menu content, but I have
some thoughts:

#1 Providing a new full menu in /etc/GNUstep/Defaults/WMRootMenu does
not make the new content available to users. Anybody who has started
wmaker before will continue using ~/GNUstep/Defaults/WMRootMenu which
references "menu.hook". So I think we need to provide a file named
menu.hook in wmaker's search path with the new content.

#2 Installing wmaker/sid and menu, followed by upgrade to wmaker/git,
purging wmaker and then purging menu leaves
/etc/GNUstep/Defaults/appearance.menu
/etc/GNUstep/Defaults/menu.hook
behind.

#3 The orphaned conffiles /etc/menu-methods/wmaker
/etc/menu-methods/wmappearance are not removed on upgrades and
menu.hook/appearance.menu will continue to be generated by update-menus.
(this is related to #2)

Find attached a proposed patch for fixing #2 and #3.

Afaict #1 only has an imperfect solution, shipping the menu in
/usr/share/WindowMaker/menu.hook. It is imperfect because I would
definitely categorize this as "configuration file" and should therefore
live in /etc (policy "must"). However we have configured wmaker to not
not look in /etc. Resurrecting 50_def_config_paths.diff would not help
for menu.hook because replacing the autogenerated
/etc/GNUstep/Defaults/menu.hook with a dpkg-conffile and keeping
update-menus from overwriting it could be very tricky.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
>From 5c84b57382339d10c7b73612f74d32199534aa89 Mon Sep 17 00:00:00 2001
From: Andreas Metzler 
Date: Sat, 29 Jul 2017 13:44:18 +0200
Subject: [PATCH] Handle removal of menu-methods and generated menus.

On upgrades remove menu-methods (orphaned conffiles) with
debian/wmaker{,-common}.maintscript. Remove generated menufiles
(etc/GNUstep/Defaults/appearance.menu and /etc/GNUstep/Defaults/menu.hook
on upgrades (only if they are autogenerated) and purge.
---
 debian/changelog |  7 +++
 debian/wmaker-common.maintscript |  1 +
 debian/wmaker-common.postinst| 14 ++
 debian/wmaker-common.postrm  |  6 ++
 debian/wmaker.maintscript|  1 +
 debian/wmaker.postinst   | 14 ++
 debian/wmaker.postrm |  6 ++
 7 files changed, 49 insertions(+)
 create mode 100644 debian/wmaker-common.postinst
 create mode 100644 debian/wmaker-common.postrm
 create mode 100644 debian/wmaker.maintscript
 create mode 100644 debian/wmaker.postinst
 create mode 100644 debian/wmaker.postrm

diff --git a/debian/changelog b/debian/changelog
index c85f4689..0df59bef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
 wmaker (0.95.8-2) UNRELEASED; urgency=medium
 
+  [ Doug Torrance ]
   * Remove and replace the deprecated Debian menu.  The list of
 applications is now generated by the wmmenugen utility (with some
 patches from upstream's development branch) from .desktop files in
@@ -18,6 +19,12 @@ wmaker (0.95.8-2) UNRELEASED; urgency=medium
   * Remove explicit call to dh_autoreconf; enabled by default in
 debhelper 10.
 
+  [ Andreas Metzler ]
+  * Handle removal of menu-methods on upgrades (orphaned conffiles) with
+debian/wmaker{,-common}.maintscript. Remove generated menufiles
+(etc/GNUstep/Defaults/appearance.menu and /etc/GNUstep/Defaults/menu.hook
+on upgrades and purge.
+
  -- Doug Torrance   Mon, 24 Jul 2017 22:34:23 -0400
 
 wmaker (0.95.8-1) unstable; urgency=low
diff --git a/debian/wmaker-common.maintscript b/debian/wmaker-common.maintscript
index 5fece828..0aad6554 100644
--- a/debian/wmaker-common.maintscript
+++ b/debian/wmaker-common.maintscript
@@ -3,3 +3,4 @@ mv_conffile /etc/X11/WindowMaker/wmmacros /usr/share/WindowMaker/wmmacros 0.95.7
 rm_conffile /etc/X11/WindowMaker/appearance.menu 0.95.7-5~
 rm_conffile /etc/X11/WindowMaker/menu.posthook 0.95.7-5~
 rm_conffile /etc/X11/WindowMaker/menu.prehook 0.95.7-5~
+rm_conffile /etc/menu-methods/wmappearance 0.95.8-2~
diff --git a/debian/wmaker-common.postinst b/debian/wmaker-common.postinst
new file mode 100644
index ..b0b22b69
--- /dev/null
+++ b/debian/wmaker-common.postinst
@@ -0,0 +1,14 @@
+#!/bin/sh
+set -e
+#DEBHELPER#
+
+# run after debhelper code, which removes menu-methods.
+if [ "$1" = "configure" ] &&
+	[ x"$2" != "x" ] && 
+	test -e /etc/GNUstep/Defaults/appearance.menu &&
+	dpkg --compare-versions "$2" '<<' '0.95.8-2~' ; then
+	if head -n1 /etc/GNUstep/Defaults/appearance.menu |
+	grep -q 'Automatically generated file. Do not edit.' ; then
+		rm /etc/GNUstep/Defaults/appearance.menu
+	fi
+fi
diff --git a/debian/wmaker-common.postrm b/debian/wmaker-common.postrm
new file mode 100644
index ..49ecaec7
--- /dev/null
+++ b/debian/wmaker-common.postrm
@@ -0,0 +1,6 

Bug#870066: python-flask-sockets: please support Python 3 and PyPy

[Dominik George]

Source: python-flask-sockets
Version: 0.2.1-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please enable building the python3- and pypy- variants of the package.

I'd also propose moving the package under the Python Modules team for
team maintenance.

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAll8ejMxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pZ7yxAAwUF0RbMkmetkP1GWJtteAAFNLTbx
mKfexYXiLlTP9F7mhEuJ3ch+uTLeugft9/sxIzVlIxntMtbUJSyQmRCzWjAP3Yko
oKuS0wbICLUthRywXikwFzZENLduFUYqr8VaaVNc4TkL6cMtd7Sl1QY8upIlrF26
WHtko1sdHv4xaMfSwqlrig9fkoKjrcRzDfVgdlT6iLwlcVPErr+sYHvnNZX/H1c7
15R5ODn4VUcEaan1eM7S5advwy24ERJdMrrNrdtVpkmTKvaUSYb69NrO+R7guIVC
jOWVmn0mvWQLpCgzR4qxLtgAIy6R0Ql5cwfiVPZ7KB7k6fOuXTQ2ivQ7F1sKsH23
8RumSlEaNw/joT31oBwZc17d6t/Lh57KGxGV7OGilovYJnv6Fh8dDQTsITwM82HP
aFOk9q5Pxwb0xXKbkR46fSq9UQBmGWoEWSnFltis6hxakjsYIp2KnMV1F+gzXsDW
lxASZ7DuZG+HKh6+6hM/jHM1EMuu7Mm9FgUqYAzYEmKNHFd4sSzhldiwoN1GluiF
/RpbNMXuwP2ZYJtLNm6950e/M8w3pUI6DfnUFCt25rylPVh5abd2/keV0Fzs4oQF
V05qM+ZWR9Qxt2SL2M0huDT0u/TqAKhY/ldrU6mHW7cpX6xUjLi3XmNlHYCuuwYp
8RE0vluiUixjmvY=
=AYSa
-END PGP SIGNATURE-

Bug#870067: CVE-2017-11640

[Bastien ROUCARIES]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-13
Severity: important
Tags: security upstream
X-Debbugs-CC: t...@security.debian.org
control: found -1 8:6.8.9.9-5+deb8u8
control: found -1 8:6.8.9.9-5+deb8u9
control: found -1 8:6.7.7.10-5+deb7u14
control: found -1 8:6.7.7.10-5+deb9u1
forwarded: https://github.com/ImageMagick/ImageMagick/issues/584

When ImageMagick 7.0.6-1 processes a crafted file in convert, it can
lead to an address access exception in the WritePTIFImage() function
in coders/tiff.c.

Bug#866123: RFS: fbkeyboard/0.1-1 [ITP]

[Andrey Rahmatullin]

Please update to the current Standards-Version.
Please switch to the debhelper compat level 10.
You don't need DPKG_EXPORT_BUILDFLAGS and /usr/share/dpkg/default.mk.
The upstream build system ignores CPPFLAGS.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#870068: kde4libs FTBFS with cmake 3.9.0

[Adrian Bunk]

Source: kde4libs
Version: 4:4.14.26-2
Severity: serious
Tags: buster sid fixed-upstream patch

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

...
CMake Error at kdeui/CMakeLists.txt:316 (else):
  A duplicate ELSE command was found inside an IF block.


-- Configuring incomplete, errors occurred!



Fixed upstream in:
https://cgit.kde.org/kdelibs.git/commit/?h=KDE/4.14&id=57eaf65accb8d058644dc8eee7332e0ec0c1952f

Bug#870070: Debian 9.1 stretch: LibreOffice Writer crashes at startup

[Carmelo C]

Package: libreoffice-writer
Version: 1:5.2.7-1
Severity: critical
Tags: security
Justification: LibreOffice Writer crashes at startup

OS: Debian GNU/Linux 9.1 (stretch) (debian-9.1.0-i386-netinst.iso)

Other packages:
libreoffice-base 1:5.2.7-1
libreoffice-base-core 1:5.2.7-1
libreoffice-common 1:5.2.7-1
libreoffice-core 1:5.2.7-1

Hi, libreoffice writer does not start, problem persists only in writer,
calc and impress start correctly with exit code 0

I tried to reinstall the libreoffice-writer package from synaptic and
remove the "/home/carmelo/.config/libreoffice" folder but nothing, does not
start

Attached the output of the command:
strace -o libreoffice_writer_output.txt -tt libreoffice --writer

Bug#870069: orig-tarball-missing-upstream-signature error breaks rebuilding existing packages and more

[Stefan Bühler]

Package: lintian
Version: 2.5.52

Hi,

I think "error" is a rather unfortunate choice for the severity level of
"orig-tarball-missing-upstream-signature".

* I have some (existing) packages uploaded on build.opensuse.org, and
  they now fail to build for "Debian_Next" (buster).  I'd rather avoid
  modifying the upstream debian package just for this.

* I also generate snapshot builds automatically.  These are (on purpose)
  not signed with the "upstream key" - because they are automatically
  generated.

  I want to stay as close as possible to the debian package, and this
  error makes this a lot harder.

I like the check, but would prefer to see it downgraded to a warning.

I already had to enable lintian manually for my build.opensuse.org
projects (I was told they disabled it because it broke too many builds
[1]); I'd prefer to keep it enabled at least for my projects.

cheers,
Stefan

[1]: https://build.opensuse.org/project/prjconf/Debian:8.0
 https://build.opensuse.org/project/prjconf/Debian:9.0
 https://build.opensuse.org/project/prjconf/Debian:Next

Bug#869574: stretch-pu: package kdepim/4:16.04.3-4

[Sandro Knauß]

Hey,

> currently in stretch is 4:16.04.3-3. Thus the version which should
> preferably be used would be 4:16.04.3-3+deb9u1.

just to understand the process better:
* Do I need to send another debdiff with the corrected versionnumber first 
before uploading?
* Do I need to close this bug within the changelog entry?
* Are there any further issues with my debdiff?

Best Regards,

sandro



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

Bug#870070: Debian 9.1 stretch: LibreOffice Writer crashes at startup

[Carmelo C]

Attached...
13:27:16.054098 execve("/usr/bin/libreoffice", ["libreoffice", "--writer"], [/* 
41 vars */]) = 0
13:27:16.055107 brk(NULL)   = 0x80fa5000
13:27:16.055282 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
13:27:16.055420 mmap2(NULL, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb770a000
13:27:16.055564 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
13:27:16.055695 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
13:27:16.055826 fstat64(3, {st_mode=S_IFREG|0644, st_size=87475, ...}) = 0
13:27:16.055946 mmap2(NULL, 87475, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb76f4000
13:27:16.056060 close(3)= 0
13:27:16.056181 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
13:27:16.056329 open("/lib/i386-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
13:27:16.056460 read(3, 
"\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\203\1\0004\0\0\0"..., 512) 
= 512
13:27:16.056584 fstat64(3, {st_mode=S_IFREG|0755, st_size=1791908, ...}) = 0
13:27:16.056704 mmap2(NULL, 1800732, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb753c000
13:27:16.056821 mprotect(0xb76ed000, 4096, PROT_NONE) = 0
13:27:16.056939 mmap2(0xb76ee000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b1000) = 0xb76ee000
13:27:16.057089 mmap2(0xb76f1000, 10780, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb76f1000
13:27:16.057233 close(3)= 0
13:27:16.057400 set_thread_area({entry_number:-1, base_addr:0xb770c840, 
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, 
seg_not_present:0, useable:1}) = 0 (entry_number:6)
13:27:16.058501 mprotect(0xb76ee000, 8192, PROT_READ) = 0
13:27:16.058731 mprotect(0x8005a000, 4096, PROT_READ) = 0
13:27:16.058877 mprotect(0xb7734000, 4096, PROT_READ) = 0
13:27:16.058995 munmap(0xb76f4000, 87475) = 0
13:27:16.059104 getpid()= 32582
13:27:16.059150 rt_sigaction(SIGCHLD, {sa_handler=0x8004ca30, sa_mask=~[RTMIN 
RT_1], sa_flags=0}, NULL, 8) = 0
13:27:16.059200 geteuid32() = 1000
13:27:16.059285 brk(NULL)   = 0x80fa5000
13:27:16.059321 brk(0x80fc6000) = 0x80fc6000
13:27:16.059397 getppid()   = 32580
13:27:16.059435 stat64("/home/carmelo", {st_mode=S_IFDIR|0755, st_size=4096, 
...}) = 0
13:27:16.059486 stat64(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13:27:16.059534 open("/usr/bin/libreoffice", O_RDONLY) = 3
13:27:16.059584 fcntl64(3, F_DUPFD, 10) = 10
13:27:16.059622 close(3)= 0
13:27:16.059658 fcntl64(10, F_SETFD, FD_CLOEXEC) = 0
13:27:16.059695 rt_sigaction(SIGINT, NULL, {sa_handler=SIG_DFL, sa_mask=[], 
sa_flags=0}, 8) = 0
13:27:16.059736 rt_sigaction(SIGINT, {sa_handler=0x8004ca30, sa_mask=~[RTMIN 
RT_1], sa_flags=0}, NULL, 8) = 0
13:27:16.059778 rt_sigaction(SIGQUIT, NULL, {sa_handler=SIG_DFL, sa_mask=[], 
sa_flags=0}, 8) = 0
13:27:16.059818 rt_sigaction(SIGQUIT, {sa_handler=SIG_DFL, sa_mask=~[RTMIN 
RT_1], sa_flags=0}, NULL, 8) = 0
13:27:16.059858 rt_sigaction(SIGTERM, NULL, {sa_handler=SIG_DFL, sa_mask=[], 
sa_flags=0}, 8) = 0
13:27:16.059898 rt_sigaction(SIGTERM, {sa_handler=SIG_DFL, sa_mask=~[RTMIN 
RT_1], sa_flags=0}, NULL, 8) = 0
13:27:16.059939 read(10, "#!/bin/sh\n#\n# This file is part "..., 8192) = 5875
13:27:16.060031 pipe([3, 4])= 0
13:27:16.060079 clone(child_stack=NULL, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb770c8a8) 
= 32583
13:27:16.060184 close(4)= 0
13:27:16.060227 read(3, "/home/carmelo\n", 128) = 14
13:27:16.060380 read(3, "", 128)= 0
13:27:16.060475 close(3)= 0
13:27:16.060513 wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 
32583
13:27:16.060574 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, 
si_pid=32583, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
13:27:16.060603 sigreturn({mask=[]})= 32583
13:27:16.060676 lstat64("/usr/bin/libreoffice", {st_mode=S_IFLNK|0777, 
st_size=34, ...}) = 0
13:27:16.060731 pipe([3, 4])= 0
13:27:16.060787 clone(child_stack=NULL, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb770c8a8) 
= 32584
13:27:16.060874 close(4)= 0
13:27:16.060915 read(3, "/usr/bin\n", 128) = 9
13:27:16.061525 read(3, "", 128)= 0
13:27:16.061578 close(3)= 0
13:27:16.061619 wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 
32584
13:27:16.061747 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, 
si_pid=32584, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
13:27:16.061776 sigreturn({mask=[]})= 32584
13:27:16.061828 chdir("/usr/bin")   = 0
13:27:16.061878 pipe([3, 4])= 0
13:27:16.061923 clone(child_stack=NULL, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb770c8a8) 
= 32585
13:27:16.062015 close(4)= 0
13:27:16.062057 r

Bug#833594: fizmo: please make the build reproducible

[Christoph Ender]

Hi,

sorry it took some time to bring the package up to date regarding
reproducible builds.

The patch has been introduced some while ago into libfizmo 0.7.12 /
fizmo 0.8.2. Since the package is however currently in the process of
being split up into separate libraries and frontends it took much longer
than anticipated to bring these new versions into debian.

Today, a patched version of libfizmo finally made it into the testing
branch. As soon as all the other parts are completed and the old version
has been completely replaced I'll mark this bug as closed.


Best regards,
Christoph.

Bug#870071: linux-image-4.9.0-3-arm64: Kconfig option for console on frame buffer device is missing

[Ard Biesheuvel]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal

Dear Maintainer,

Please enable CONFIG_FRAMEBUFFER_CONSOLE (preferably as a builtin) in the 
arm64's kernel image configuration so that systems with a graphics card 
installed can get a console on the frame buffer rather than only via serial.

-- Package-specific info:
** Version:
Linux version 4.9.0-3-arm64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-arm64 
root=UUID=f3b7c265-d79f-4dce-8c44-d6120d9111e7 ro console=ttyAMA0 console=tty0

** Not tainted

** Kernel log:
[2.477111] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[2.631395] usb 1-1: New USB device found, idVendor=05ac, idProduct=1006
[2.638097] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[2.645227] usb 1-1: Product: Keyboard Hub
[2.649319] usb 1-1: Manufacturer: Apple, Inc.
[2.653757] usb 1-1: SerialNumber: 
[2.660074] hub 1-1:1.0: USB hub found
[2.664135] hub 1-1:1.0: 3 ports detected
[2.783268] ata2: SATA link down (SStatus 0 SControl 300)
[2.957106] usb 1-1.1: new low-speed USB device number 3 using xhci_hcd
[3.072863] usb 1-1.1: New USB device found, idVendor=413c, idProduct=3012
[3.079735] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[3.087042] usb 1-1.1: Product: Dell USB Optical Mouse
[3.092175] usb 1-1.1: Manufacturer: Dell
[3.100842] hidraw: raw HID events driver (C) Jiri Kosina
[3.103266] ata3: SATA link down (SStatus 0 SControl 300)
[3.115764] usbcore: registered new interface driver usbhid
[3.121341] usbhid: USB HID core driver
[3.125960] input: Dell Dell USB Optical Mouse as 
/devices/platform/smb/f000.pcie/pci:00/:00:02.2/:02:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:413C:3012.0001/input/input0
[3.142168] hid-generic 0003:413C:3012.0001: input,hidraw0: USB HID v1.11 
Mouse [Dell Dell USB Optical Mouse] on usb-:02:00.0-1.1/input0
[3.177110] usb 1-1.2: new low-speed USB device number 4 using xhci_hcd
[3.294036] usb 1-1.2: New USB device found, idVendor=05ac, idProduct=024f
[3.300910] usb 1-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[3.308217] usb 1-1.2: Product: Apple Keyboard
[3.312656] usb 1-1.2: Manufacturer: Apple Inc.
[3.327778] input: Apple Inc. Apple Keyboard as 
/devices/platform/smb/f000.pcie/pci:00/:00:02.2/:02:00.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:05AC:024F.0002/input/input1
[3.401366] apple 0003:05AC:024F.0002: input,hidraw1: USB HID v1.11 Keyboard 
[Apple Inc. Apple Keyboard] on usb-:02:00.0-1.2/input0
[3.414198] input: Apple Inc. Apple Keyboard as 
/devices/platform/smb/f000.pcie/pci:00/:00:02.2/:02:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:05AC:024F.0003/input/input2
[3.415263] ata4: SATA link down (SStatus 0 SControl 300)
[3.493164] apple 0003:05AC:024F.0003: input,hidraw2: USB HID v1.11 Device 
[Apple Inc. Apple Keyboard] on usb-:02:00.0-1.2/input1
[3.727269] ata5: SATA link down (SStatus 0 SControl 300)
[4.209110] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[4.216467] ata6.00: ATA-9: SanDisk Ultra II 240GB, X41200RL, max UDMA/133
[4.223345] ata6.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 31/32)
[4.231248] ata6.00: configured for UDMA/133
[4.235759] scsi 5:0:0:0: Direct-Access ATA  SanDisk Ultra II 00RL 
PQ: 0 ANSI: 5
[4.587265] ata7: SATA link down (SStatus 0 SControl 300)
[4.907267] ata8: SATA link down (SStatus 0 SControl 300)
[4.920097] sd 5:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224 
GiB)
[4.927659] sd 5:0:0:0: [sda] Write Protect is off
[4.932451] sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00
[4.932474] sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.948846]  sda: sda1 sda2 sda3 sda4
[4.953073] sd 5:0:0:0: [sda] Attached SCSI disk
[4.994067] PM: Starting manual resume from disk
[4.998724] PM: Hibernation image partition 8:3 present
[4.998726] PM: Looking for hibernation image.
[4.998871] random: fast init done
[5.002349] PM: Image not found (code -22)
[5.002351] PM: Hibernation image not present or could not be loaded.
[5.053585] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: 
(null)
[5.158112] ip_tables: (C) 2000-2006 Netfilter Core Team
[5.171529] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[5.189751] systemd[1]: Detected architecture arm64.
[5.196476] systemd[1]: Set hostname to .
[5.210572] uart-pl011 e101.serial: no DMA platform data
[5.253903] systemd[1]: Listening on Journal Socket (/dev/log).
[5.260032] sys

Bug#870072: Add support for AllowExtraction back

[Timo Aaltonen]

Package: opendnssec
Severity: normal


Hi,

The new version doesn't support AllowExtraction like 1.4 did:

https://lists.opendnssec.org/pipermail/opendnssec-user/2017-July/004086.html

this is needed by FreeIPA, please add it back as a patch until a new
upstream release has it.


-- 
t

Bug#760370: libpcap0.8-dev is still not Multi-Arch compatible

[Hugh McMaster]

Dear Maintainer,


libpcap0.8-dev is very close to being multi-arch compatible. As Francois 
pointed out back in February 2015,

the only problem is in pcap-config.


Francois' patch also remains a valid solution. Have you made any progress on 
resolving this issue?

Or do you need help with testing or anything else?


Regards,

Hugh

Bug#849240: marked as done (auto-complete-el: ac-menu-delete setq of 1 arg)

[Ignasi Ferrer Sabrià - Àrea Tècnica SW Hosting]

unsuscribe



Ignasi Ferrer Sabrià
Área de Sistemas · SWHosting

T: +34 972 010 550
F: +34 972 010 555
www.swhosting.com

  Antes de imprimir este e-mail, piense bien si es necesario hacerlo.


-Missatge original-
De: Debian Bug Tracking System [mailto:ow...@bugs.debian.org] 
Enviat: dissabte, 29 de juliol de 2017 14:06
Per a: Adrian Bunk 
Tema: Bug#849240: marked as done (auto-complete-el: ac-menu-delete setq of 1 
arg)

Your message dated Sat, 29 Jul 2017 12:03:53 + with message-id 

and subject line Bug#849240: fixed in auto-complete-el 1.3.1-2.1 has caused the 
Debian Bug report #849240, regarding auto-complete-el: ac-menu-delete setq of 1 
arg 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.)


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


smime.p7s
Description: S/MIME cryptographic signature

Bug#859177: meson is unuseable for package cross compilation

[Jussi Pakkanen]

On Sat, Jul 29, 2017 at 10:19 AM, Michael Biebl  wrote:

> Jussi, would this be hard to implement? Is there a good reason why
> cross-compilation uses a separate file?

There are many reasons. The fils contains a lot of options and passing
all those in command line arguments would make for very bloated
command lines. Since the data in cross files rarely changes, having it
a standalone file makes it easy to share between projects, commit them
in revision control, and so on.

Bug#870073: enigmail: Does not encrypt and gives alerts after upgrade to Thunderbird 52

[Paul van der Vlis]

Package: enigmail
Version: 2:1.9.8.1-1~deb8u1
Severity: important

Dear Maintainer,

After the security upgrade to Thunderbird version 52.2.1 Enigmail did not work
anymore. I've tried now Enigmail version 2:1.9.8.1-1~deb8u1 but it has the same
problem.  Because I could not install this version of Enigmail using apt, I've
downloaded it from here:
http://security.debian.org/debian-
security/pool/updates/main/e/enigmail/enigmail_1.9.8.1-1~deb8u1_all.deb
And installed it with "dpkg -i".

When I read an encrypted message in Thunderbird, I get this warning:
--
Enigmail Alert:
GnuPG reported an error in the communication with gpg-agent (a component of
GnuPG).
This is a system setup or configuration error that prevents Enigmail from
working properly and cannot be fixed automatically.
We strongly recommend that you consult our support web site at
https://enigmail.net/faq.
--
After this, the message is decrypted.

But when I sent a message to somebody with a PGP key in my keyring, the message
is normally encrypted. But not now, and I do not get a warning about that.

With Thunderbird 45 I did not have these problems.

With regards,
Paul van der Vlis



-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages enigmail depends on:
ii  gnupg  1.4.18-7+deb8u3
ii  gnupg-agent2.0.26-6+deb8u1
ii  gnupg2 2.0.26-6+deb8u1
ii  icedove1:52.2.1-4~deb8u1
ii  thunderbird [icedove]  1:52.2.1-4~deb8u1

Versions of packages enigmail recommends:
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

enigmail suggests no packages.

Bug#870070: Debian 9.1 stretch: LibreOffice Writer crashes at startup

[Rene Engelhard]

severity 870070 grave
tag 870070 - security
tag 870070 + moreinfo
thanks

Hi,

On Sat, Jul 29, 2017 at 02:19:04PM +0200, Carmelo C wrote:
>Package: libreoffice-writer
>Version: 1:5.2.7-1
>Severity: critical

No? How does it break your whole system?

See https://www.debian.org/Bugs/Developer.en.html#severities

>Tags: security

No? Why? (Well, it got broken by the kernel security update I believey,
es, but still.)

>Justification: LibreOffice Writer crashes at startup

Yes, and? That would be grave.

>OS: Debian GNU/Linux 9.1 (stretch) (debian-9.1.0-i386-netinst.iso)

Aha. Why on earth do people still install i386?

I *believe* you ran into

https://lwn.net/Articles/727206/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
and "friends" merged to it.
https://lwn.net/Articles/727703/ (ttbok unforunatel subscriber-only by now.)

You wouldn't have this problem if you used amd64...

And you obviously didn't even dare to look whether the bug already was
reported:

Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)

#865303 [G|MRu|=☣] [src:linux] libreoffice: Libreoffice Java features crash 
with Linux 3.16.43-2+deb8u1

and friends are visible in bugs.debian.org/libreoffice-writer

>Attached the output of the command:
>strace -o libreoffice_writer_output.txt -tt libreoffice --writer

No, there isn't. (And a gdb bt would be better anyways).

Regards,

Rene

Bug#870058: xsane failing since stretch upgrade

[Jörg Frings-Fürst]

tags 870058 + moreinfo
thanks


Hello Daniel,

thank you for spending your time helping to make Debian better with
this bug report.

Please can you check your system as described in[1]?

CU
Jörg

[1] http://hplipopensource.com/node/205


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  330dfaa3e4985d5c45f5730bd2c21693c2c5e04e

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#870045: pbuilder: Fail to create an i386 build under amd64

[Mattia Rizzolo]

Control: clone -1 -2
Control: retitle -2 pbuilder: print the tail of debootstrap.log on create
failure
Control: severity -2 wishlist

Please run pbuilder create with --debug (note that it won't remove the
chroot once failed), and share that debugging log.  Also then have a look
at the mentioned debootstrap.log.

On Sat, 29 Jul 2017, 10:51 a.m. Christian Marillat, 
wrote:

> Package: pbuilder
> Version: 0.228.7
> Severity: normal
>
> Dear Maintainer,
>
> I've several pbuilder build and today I need to install an i386 build for
> my
> amd64 machine and pbuilder fail :
>
> I: Extracting zlib1g...
> W: Failure trying to run: chroot /home/marillat/src/unstable/build//22489
> dpkg-deb -f /var/cache/apt/archives/dpkg_1.18.24_i386.deb Version
> W: See
> /home/marillat/src/unstable/build//22489/debootstrap/debootstrap.log for
> details
> W: Failure trying to run: chroot /home/marillat/src/unstable/build//22489
> mount -t proc proc /proc
> W: See
> /home/marillat/src/unstable/build//22489/debootstrap/debootstrap.log for
> details
> E: debootstrap failed
> W: Aborting with an error
> I: cleaning the build env
> I: removing directory /home/marillat/src/unstable/build//22489 and its
> subdirectories
>
>
> Christian
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.1.42 (SMP w/8 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages pbuilder depends on:
> ii  debconf  1.5.63
> ii  debootstrap  1.0.91
> ii  dpkg-dev 1.18.24
> ii  wget 1.19.1-4
>
> Versions of packages pbuilder recommends:
> ii  devscripts  2.17.9
> pn  eatmydata   
> ii  fakeroot1.21-3.1
> ii  iproute24.9.0-1
> ii  net-tools   1.60+git20161116.90da8a0-1
> ii  sudo1.8.20p2-1
>
> Versions of packages pbuilder suggests:
> pn  cowdancer   
> pn  gdebi-core  
>
> -- debconf information excluded
>
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
>

Bug#870070: Debian 9.1 stretch: LibreOffice Writer crashes at startup

[Rene Engelhard]

On Sat, Jul 29, 2017 at 02:29:38PM +0200, Carmelo C wrote:
>Attached...

Useless, afaics. libreoffice is a shell script which runs an other shell script
(soffice) which runs the real office. You always need -f to strace here.

Anyway, as said in my initial reply: gdb backtrace please:

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information

Regards,

Rene

Bug#870070: Debian 9.1 stretch: LibreOffice Writer crashes at startup

[Rene Engelhard]

Hi,

On Sat, Jul 29, 2017 at 03:23:46PM +0200, Rene Engelhard wrote:
> https://lwn.net/Articles/727206/
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
> and "friends" merged to it.
> https://lwn.net/Articles/727703/ (ttbok unforunatel subscriber-only by now.)

Ah, no, it's public now.

> Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)
> 
> #865303 [G|MRu|=☣] [src:linux] libreoffice: Libreoffice Java features crash 
> with Linux 3.16.43-2+deb8u1
> 
> and friends are visible in bugs.debian.org/libreoffice-writer

BTW, if you installed "libreoffice" you _do_ get Java based components
installed which might be initialized at startup in writer (e.g.
-wiki-publisher) or at any other time one of these is needed, thus you maybe
even don't know you use Java features, but still.

Regards,
 
Rene

Bug#867009: RFS: fzf/0.16.8-2 [ITP]

[Tom Fitzhenry]

Hi Andrey,

Thank you for the feedback.

> The initial upload should have the debian revision of -1.

The latest revision is revision 1.[0]

> Please update to the current Standards-Version.

The latest revision uses Standards-Version 4.0.0, though mentors.debian.net
does not recognise 4.0.0, which I have raised as a bug.[1]

> Please use the priority optional.
Done. The latest revision now has priority optional.

> The .dsc file is wrong: "dpkg-source: error: file
./fzf_0.16.8.orig.tar.gz has size 128895 instead of expected 128889"

I cannot reproduce this. I recall my first release had some problems
relating to how I used pristine-tar, which I fixed, which might have fixed
this size mismatch.

Additionally, I need to update to latest upstream: 0.16.10.

Regards,
Tom Fitzhenry

0. https://mentors.debian.net/package/fzf
1.
https://alioth.debian.org/tracker/index.php?func=detail&aid=315789&group_id=100127&atid=413115


On Sat, 29 Jul 2017 at 22:02 Andrey Rahmatullin  wrote:

> The initial upload should have the debian revision of -1.
> Please update to the current Standards-Version.
> Please use the priority optional.
> The .dsc file is wrong: "dpkg-source: error: file ./fzf_0.16.8.orig.tar.gz
> has size 128895 instead of expected 128889".
>
> --
> WBR, wRAR
>

Bug#870075: src:pdf-presenter-console: maintainer address bounces

[Ansgar Burchardt]

Source: pdf-presenter-console
Tags: sid
Severity: serious

The maintainer address for pdf-presenter-console bounces, see below.

Ansgar

Mail Delivery System  writes:

> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   ba...@pearlmutter.net
> SMTP error from remote mail server after end of data:
> host eforward1.registrar-servers.com [162.255.118.61]:
> 550 The sending IP (209.87.16.33) is listed on https://spamrl.com as a 
> source of viruses.
>
> -- This is a copy of the message, including all the headers. --
>
> Return-path: 
> Received: from [138.16.160.17] (helo=fasolo.debian.org)
>   from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP 
> CA,CN=fasolo.debian.org,EMAIL=hostmas...@fasolo.debian.org (verified)
>   by muffat.debian.org with esmtps 
> (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
>   (Exim 4.84_2)
>   (envelope-from )
>   id 1da8ve-0007gk-Aw; Tue, 25 Jul 2017 23:07:50 +
> Received: from dak by fasolo.debian.org with local (Exim 4.84_2)
>   (envelope-from )
>   id 1da8vd-0007ze-69; Tue, 25 Jul 2017 23:07:49 +
> From: Debian FTP Masters 
> To: b...@debian.org (Barak A. Pearlmutter)
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: pdf-presenter-console
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: pdf-presenter-console_4.0.7-2_amd64.changes ACCEPTED into unstable
> Message-Id: 
> Date: Tue, 25 Jul 2017 23:07:49 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Tue, 25 Jul 2017 11:52:59 +0100
> Source: pdf-presenter-console
> Binary: pdf-presenter-console
> Architecture: source amd64
> Version: 4.0.7-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Barak A. Pearlmutter 
> Changed-By: Barak A. Pearlmutter 
> Description:
>  pdf-presenter-console - multi-monitor presentation tool (ala Keynote) for 
> PDF files
> Changes:
>  pdf-presenter-console (4.0.7-2) unstable; urgency=medium
>  .
>* Merge upstream fixes, should address various video bugs
> Checksums-Sha1:
>  07614ac6e31622d9898e813ce83b3b4ddc7ae4dc 2121 
> pdf-presenter-console_4.0.7-2.dsc
>  94f9ae370a0b72a0025f0a744bad77f8683a2db2 22752 
> pdf-presenter-console_4.0.7-2.debian.tar.xz
>  3b8a9698fd6cdfa26663c3133d73680a5c312ff4 511658 
> pdf-presenter-console-dbgsym_4.0.7-2_amd64.deb
>  eda545d2c0a411d5ab345cc2ceea22b475c4c2a2 13625 
> pdf-presenter-console_4.0.7-2_amd64.buildinfo
>  6b5a6ab31ce9b45b05132a59fddfda905f560544 122206 
> pdf-presenter-console_4.0.7-2_amd64.deb
> Checksums-Sha256:
>  aa86b068ae4d6dfc09eac11144cc8bd9f77a3f032af1b8d75244949216be342a 2121 
> pdf-presenter-console_4.0.7-2.dsc
>  00efc12400b5008d3920a2193de9d9493b5ed85c511a5e403893dae8bf35e028 22752 
> pdf-presenter-console_4.0.7-2.debian.tar.xz
>  f205ad19715c4ff8411c02da0efe5cd958e49c33464a42daa23ffea6b3bfd6aa 511658 
> pdf-presenter-console-dbgsym_4.0.7-2_amd64.deb
>  9222700cac8c1419d9938b4fb5b9c607de096349e076878f25628d68efcd7acf 13625 
> pdf-presenter-console_4.0.7-2_amd64.buildinfo
>  f849f0da91a69ea812e49f1348214b9eb25b2dd93b6c966cfc2c1e5856eb3407 122206 
> pdf-presenter-console_4.0.7-2_amd64.deb
> Files:
>  887ed1868a6d1ecaff73a4e375e1d8fc 2121 graphics extra 
> pdf-presenter-console_4.0.7-2.dsc
>  96d01013e0df59e2d3fdc3f72647987b 22752 graphics extra 
> pdf-presenter-console_4.0.7-2.debian.tar.xz
>  ce72664bdc2cde39fa350c707cfb5146 511658 debug extra 
> pdf-presenter-console-dbgsym_4.0.7-2_amd64.deb
>  54490afddb34e7e04416389e45d3dffc 13625 graphics extra 
> pdf-presenter-console_4.0.7-2_amd64.buildinfo
>  54332e294f9acbb379a0e4b664ef0bda 122206 graphics extra 
> pdf-presenter-console_4.0.7-2_amd64.deb
>
>
>
> Thank you for your contribution to Debian.

Bug#870076: src:chrony: maintainer address bounces

[Ansgar Burchardt]

Source: chrony
Severity: serious
Tags: sid

The maintainer address for chrony bounces, see below.

Ansgar

Mail Delivery System  writes:

> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   vincent.deb...@free.fr
> all hosts for 'free.fr' have been failing for a long time and were last 
> tried after this message arrived
>
> Reporting-MTA: dns; mailly.debian.org
>
> Action: failed
> Final-Recipient: rfc822;vincent.deb...@free.fr
> Status: 5.0.0
>
> From: Debian FTP Masters 
> Subject: chrony_3.2~pre1-1_source.changes ACCEPTED into experimental
> To: Vincent Blut ,  
> Date: Wed, 26 Jul 2017 09:49:13 + (3 days, 3 hours, 58 minutes ago)
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Tue, 25 Jul 2017 21:13:22 +0200
> Source: chrony
> Binary: chrony
> Architecture: source
> Version: 3.2~pre1-1
> Distribution: experimental
> Urgency: medium
> Maintainer: Vincent Blut 
> Changed-By: Vincent Blut 
> Description:
>  chrony - Versatile implementation of the Network Time Protocol
> Changes:
>  chrony (3.2~pre1-1) experimental; urgency=medium
>  .
>* Import upstream version 3.2-pre1:
>  - Please see /usr/share/doc/chrony/changelog.gz for the release notes.
>  .
>* debian/patches/*:
>  - Remove allow_getpid_in_seccomp_filter.patch and update the series file
>  accordingly.
>  .
>* debian/tests/upstream-simulation-test-suite:
>  - Run tests in multiple iterations.
> Checksums-Sha1:
>  c143c9dd7137693a6f7926408f37a7b2231c5a49 1921 chrony_3.2~pre1-1.dsc
>  7c58a02ae12bcb79c02317f21ba2b109c510d04b 431211 chrony_3.2~pre1.orig.tar.gz
>  8caa238c519bc1ce4cf95da2fff8e49b838671c1 26840 
> chrony_3.2~pre1-1.debian.tar.xz
> Checksums-Sha256:
>  57459cec5ba526d3109c55ed75db474bb285b9a4bd34b25961fa3f191c5d0ba0 1921 
> chrony_3.2~pre1-1.dsc
>  3c6fa2fe71ba670955498dcecab6a57c0b4ed8bc5a761629e96cd6038946942f 431211 
> chrony_3.2~pre1.orig.tar.gz
>  91e3ba7b227341f1d546d402f8a9723878770c99be5a11dda531def9d04cbce1 26840 
> chrony_3.2~pre1-1.debian.tar.xz
> Files:
>  f86c00f85f65a62944962753bdb3e3f3 1921 net optional chrony_3.2~pre1-1.dsc
>  58f8b1b439f5d1a8084a2668b8284b25 431211 net optional 
> chrony_3.2~pre1.orig.tar.gz
>  d30b8043850bcd2cabbbf03cacd30bb0 26840 net optional 
> chrony_3.2~pre1-1.debian.tar.xz
>
>
>
> Thank you for your contribution to Debian.
> --

Bug#868115: Patch to fix this

[Ole Streicher]

Control: tags -1 patch

Hi,

I just found that this is fixed upstream and extracted the changes that
are required. Would you consider creating a new Debian release that
included this patch?

Thank you

Ole
--- a/gwcs/utils.py
+++ b/gwcs/utils.py
@@ -161,15 +161,24 @@
 """
 if isinstance(skycoord, coords.SkyCoord):
 lat = skycoord.spherical.lat
+unit = u.deg
 else:
-lat = skycoord[1]
-if isinstance(projection, projections.Zenithal):
-if lat < 0:
-lon_pole = 180
+lon, lat = skycoord
+if isinstance(lat, u.Quantity):
+unit = u.deg
 else:
+unit = None
+if isinstance(projection, projections.Zenithal):
+lon_pole = 180
+elif isinstance(projection, projections.Cylindrical):
+if lat >= 0:
 lon_pole = 0
+else:
+lon_pole = 180
 else:
 raise UnsupportedProjectionError("Projection {0} is not supported.".format(projection))
+if unit is not None:
+lon_pole = lon_pole * unit
 return lon_pole
 
 

Bug#868558: nmu: multiple r-* packages

[Dirk Eddelbuettel]

Dear release team,

On 16 July 2017 at 10:40, Dirk Eddelbuettel wrote:
| 
| Package: release.debian.org
| User: release.debian@packages.debian.org
| Usertags: binnmu
| Severity: normal
| 
| R 3.4.0, which was released in April, made one subtle breaking change
| affecting how (optional) compiled code in contributed package is loaded,
| affecting the older two of the three (plus one internal) available
| mechanisms:  .C() and .Fortran().  Packages still load and run parts of
| their code, they just can no longer access this compiled code---unless
| rebuilt. 
| 
| This has been discussed in #86133 at https://bugs.debian.org/861333
| 
| I have now prepared a fine-grained set of packages requiring a NMU, narrowing
| the actual set of required rebuilds down from an unconditional 514 packages
| (all reverse depends of r-base-core) to 92 packages meeting all requirements.
| 
|   nmu r-bioc-makecdfenv_1.50.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-bioc-multtest_2.30.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-bioc-edger_3.14.0+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-boolnet_2.1.3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-tikzdevice_0.10-1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-logspline_2.1.9-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-genabel_1.8-0-1+b1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-lhs_0.14-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-bioc-limma_3.30.8+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-coin_1.1-3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-other-iwrlars_0.9-5-2 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-mnp_2.6-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-msm_1.6.4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-fields_8.10-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-desolve_1.14-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-adephylo_1.1-10-2 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-dosefinding_0.9-15-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-deldir_0.1-12-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-rniftilib_0.0-35.r79-2 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-data.table_1.10.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-qtl_1.40-8-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-bioc-preprocesscore_1.36.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-contfrac_1.1-10-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-glmnet_2.0-5-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-bitops_1.0-6-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-sp_1:1.2-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-spc_1:0.5.3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-bioc-snpstats_1.24.0+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-tgp_2.4-14-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-brglm_0.5-9-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-cmprsk_2.2-7-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-bioc-affy_1.52.0-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-ncdf4_1.15-1+b2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-treescape_1.10.18-6 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-bioc-rbgl_1.50.0+dfsg1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-bioc-rtracklayer_1.34.1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-hexbin_1.27.1-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-princurve_1.1-12-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-mapproj_1.2-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-blockmodeling_0.1.8-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-hdf5_1.6.10-4+b1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-pscl_1.4.9-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-ade4_1.7-5-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-vgam_1.0-3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-adegenet_2.0.1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-mixtools_1.0.4-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-phylobase_0.8.2-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
|   nmu r-cran-amelia_1.7.4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-spam_1.4-0-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
|   nmu r-cran-medadherence_1.03-2 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'

Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later

[Paul van der Vlis]

Op 27-07-17 om 20:52 schreef Daniel Kahn Gillmor:
> On Thu 2017-07-27 17:23:25 +0200, Paul van der Vlis wrote:
>> On Thu, 27 Jul 2017 09:59:46 -0400 Daniel Kahn Gillmor
>>  wrote:
>>
>>> I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs
>>> successfully on jessie and that it appears to fix the underlying
>>> problem.
>>
>> My experience is different: it installs without a problem, it gives
>> warnings while decrypting. And it looks-like it encrypts, but it sent
>> plain text.
> 
> yikes.  this is a particularly scary failure mode, and i think it is
> distinct from the report here, which includes messages simply failing to
> send (esp. those with attachments) and some buttons or UI elements being
> unresponsive.
> 
> Could you open this as a separate issue in the debian BTS?  can you help
> me to reproduce the behavior you're describing?  I haven't see that yet.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870073

>> When I install it from Mozilla, it has the same problem on my machine, I
>> am now back to Thunderbird 45 as a work-arround, what works fine.
> 
> glad there's a workaround, but it doesn't sound like something
> particularly sustainable long term.  if you can help me replicate the
> "looks-encrypted-but-sends-in-the-clear" failure mode?
When I answer an encrypted message of somebody in my keyring, I expect
that the message will become encrypted. But that's not the case. It's
sent unencrypted without a warning.

With regards,
Paul van der Vlis

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Bug#869774: [SECURITY] [DSA 3921-1] enigmail update

[Paul van der Vlis]

Hello,

I've tried today the upgrade, but there was no new version.

When I look at the end of this page:
https://packages.debian.org/jessie/enigmail

Then I see architecture "all" with version 2:1.9.8.1-1~deb8u1, and e.g.
architecture amd64 with version 2:1.8.2-4~deb8u1. I think the last one
is used, and that's the old one.

For Stretch, there is only an architecture "all".

With regards,
Paul van der Vlis.

Op 28-07-17 om 21:16 schreef Moritz Muehlenhoff:
> -
> Debian Security Advisory DSA-3921-1   secur...@debian.org
> https://www.debian.org/security/   Moritz Muehlenhoff
> July 28, 2017 https://www.debian.org/security/faq
> -
> 
> Package: enigmail
> Debian Bug : 869774
> 
> In DSA 3918 Thunderbird was upgraded to the latest ESR series. This
> update upgrades Enigmail, the OpenPGP extention for Thunderbird,
> to version 1.9.8.1 to restore full compatibility.
> 
> For the oldstable distribution (jessie), this problem has been fixed
> in version 2:1.9.8.1-1~deb8u1.
> 
> For the stable distribution (stretch), this problem has been fixed in
> version 2:1.9.8.1-1~deb9u1.
> 
> We recommend that you upgrade your enigmail packages.
> 
> Further information about Debian Security Advisories, how to apply
> these updates to your system and frequently asked questions can be
> found at: https://www.debian.org/security/
> 
> Mailing list: debian-security-annou...@lists.debian.org
> 

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Bug#861378: Disable debian-chinese-b...@lists.debian.org list

[陳昌倬]

Hi All,

I would like to propose to disable debian-chinese-b...@lists.debian.org
for the following reasons:

* For Chinese translation related discuss, we already have
  debian-l10n-chinese@l.d.o

* For Debian user in Taiwan, A new list debian-dug-taiwan has been
  requested (#847950).

* Big5 encoding is deprecated long time ago.


Please raise your concern if you think we shall keep
debian-chinese-big5@l.d.o.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#870045: pbuilder: Fail to create an i386 build under amd64

[Christian Marillat]

On 29 juil. 2017 13:32, Mattia Rizzolo  wrote:

> Control: clone -1 -2
> Control: retitle -2 pbuilder: print the tail of debootstrap.log on create
> failure
> Control: severity -2 wishlist
>
> Please run pbuilder create with --debug (note that it won't remove the
> chroot once failed), and share that debugging log.  Also then have a look
> at the mentioned debootstrap.log.

My own kernel was not build with 32-bits support.

Sorry for the noise. You can close this bug.

Christian

Bug#861378: Disable debian-chinese-b...@lists.debian.org list

[Kan-Ru Chen]

On Sat, Jul 29, 2017, at 10:32 PM, ChangZhuo Chen (陳昌倬) wrote:
> 
> Hi All,
> 
> I would like to propose to disable debian-chinese-b...@lists.debian.org
> for the following reasons:
> 
> * For Chinese translation related discuss, we already have
>   debian-l10n-chinese@l.d.o
> 
> * For Debian user in Taiwan, A new list debian-dug-taiwan has been
>   requested (#847950).
> 
> * Big5 encoding is deprecated long time ago.
> 
> 
> Please raise your concern if you think we shall keep
> debian-chinese-big5@l.d.o.

Thanks for bringing this up!

I concur we can decommission the debian-chinese-big5 list.

Kanru

> -- 
> ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
> http://czchen.info/
> Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B

Bug#870077: ITP: html5-parser -- necessary dependency for calibre

[Norbert Preining]

Package: wnpp
Severity: wishlist
Owner: Norbert Preining 

* Package name: html5-parser
  Version : 0.4.3
  Upstream Author : Kovid Goyal 
* URL : https://github.com/kovidgoyal/html5-parser
* License : Apache
  Programming Lang: Python
  Description : necessary dependency for calibre

A fast implementation of the HTML 5 parsing spec for Python. Parsing is
done in C using a variant of the gumbo parser. The gumbo parse tree is
then transformed into an lxml tree, also in C, yielding parse times that
can be a thirtieth of the html5lib parse times. That is a speedup of 30x.
This differs, for instance, from the gumbo python bindings, where the
initial parsing is done in C but the transformation into the final
tree is done in python.

Will be maintained in collab-maint.

Bug#870078: libsane1 breaks all 3rd party scanner drivers

[Gunter Königsmann]

Package: libsane1
Version: 1.0.27-1~experimental1ubuntu2
Severity: important

Dear Maintainer,

There are wishlist bugs already about individual packages no more
working after switching from libsane1 to libsane but I think the
situation is more grave than that: All 3rd-party scanner drivers that
are shipped in .deb packages depend on libsane. Renaming the package to
libsane1 without adding a "provides" breaks that dependency and it seems
like merely adding the "provides" does not get them into a working order
again. On my part both epson scanners I own and the
brother scanner are broken since the library has changed which leaves me
with no access to any scanner - and Ubuntu has pulled the libsane1 from
debian which means that ubuntu will havve the same problem, as well.

Bug#870079: hdf4: Please enable SZIP support (libaec library)

[Alastair McKinstry]

Package: hdf4
Severity: wishlist
Tags: patch

Debdiff attached. This enables HDF4 to read/write compressed files

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

Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_IE.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libhdf4-4.2.13/debian/changelog libhdf4-4.2.13/debian/changelog
--- libhdf4-4.2.13/debian/changelog 2017-06-28 22:30:05.0 +0100
+++ libhdf4-4.2.13/debian/changelog 2017-07-25 15:58:54.0 +0100
@@ -1,3 +1,10 @@
+libhdf4 (4.2.13-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Enable SZIP support
+
+ -- Alastair McKinstry   Tue, 25 Jul 2017 15:58:54 +0100
+
 libhdf4 (4.2.13-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru libhdf4-4.2.13/debian/control libhdf4-4.2.13/debian/control
--- libhdf4-4.2.13/debian/control   2017-06-28 22:29:26.0 +0100
+++ libhdf4-4.2.13/debian/control   2017-07-25 15:58:54.0 +0100
@@ -11,6 +11,7 @@
chrpath,
flex,
gfortran,
+   libaec-dev,
libjpeg-dev,
sharutils,
zlib1g-dev
diff -Nru libhdf4-4.2.13/debian/rules libhdf4-4.2.13/debian/rules
--- libhdf4-4.2.13/debian/rules 2017-06-28 22:02:11.0 +0100
+++ libhdf4-4.2.13/debian/rules 2017-07-25 15:58:54.0 +0100
@@ -87,6 +87,7 @@
 --libdir=/usr/lib \
 --enable-shared \
 --enable-fortran \
+--with-szip \
 F77="$(F77)" CC="$(CC)" CXX="$(CXX)" \
 CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)"
 
@@ -99,6 +100,7 @@
 --enable-shared \
 --disable-fortran \
 --disable-netcdf \
+--with-szip \
 CC="$(CC)" CXX="$(CXX)" \
 CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)"
 

Bug#870080: igtf-policy-bundle: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: igtf-policy-bundle
Version: 1.85-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for samba's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org






# Translation of igtf-policy-bundle's debconf messages to Portuguese
# Copyright (C) 2014 THE igtf-policy-bundle'S COPYRIGHT HOLDER
# This file is distributed under the same license as the igtf-policy-bundle package.
#
# Américo Monteiro , 2014.
# Rui Branco - DebianPT , 2017.
msgid ""
msgstr ""
"Project-Id-Version: igtf-policy-bundle 1.85-1\n"
"Report-Msgid-Bugs-To: igtf-policy-bun...@packages.debian.org\n"
"POT-Creation-Date: 2017-07-24 17:44+0200\n"
"PO-Revision-Date: 2017-07-29 15:33+\n"
"Last-Translator: Rui Branco - DebianPT \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid "Trust IGTF @PROFILE@ CAs by default?"
msgstr "Confiar em IGTF @PROFILE@ CAs por predefinição?"

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid ""
"Trusted IGTF Certification Authority certificates are installed in "
"${location}."
msgstr ""
"Os certificados da Trusted IGTF Certification Authority estão instalados em "
"${location}."

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid ""
"Accept this option to have certificates included by default unless they are "
"explicitly excluded. Reject it to choose the reverse policy, excluding them "
"unless explicitly included."
msgstr ""
"Aceite esta opção para ter os certificados incluídos por predefinição a "
"menos que eles sejam excluídos explicitamente. Rejeite-a para escolher a "
"política reversa, excluindo-os a menos que sejam incluídos explicitamente."

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid "You will then have the opportunity to define the list of exceptions."
msgstr "Você terá a oportunidade de definir a lista de excepções."

#. Type: multiselect
#. Description
#: ../templates.in:3001
msgid "Certificates to explicitly exclude:"
msgstr "Certificados a excluir explicitamente:"

#. Type: multiselect
#. Description
#: ../templates.in:3001
msgid ""
"Please select which certificates should not be installed in ${location}."
msgstr ""
"Por favor seleccione quais certificados não deverão ser instalados em "
"${location}."

#. Type: multiselect
#. Description
#: ../templates.in:4001
msgid "Certificates to explicitly include:"
msgstr "Certificados a incluir explicitamente:"

#. Type: multiselect
#. Description
#: ../templates.in:4001
msgid "Please select which certificates should be installed in ${location}."
msgstr ""
"Por favor seleccione quais certificados deverão ser instalados em "
"${location}."

#. Type: string
#. Description
#: ../templates.in:5001
msgid "Installation directory of the certificates:"
msgstr "Directório de instalação dos certificados:"

#. Type: string
#. Description
#: ../templates.in:5001
msgid ""
"The default location /etc/grid-security/certificates should work fine in "
"most cases."
msgstr ""
"O local por predefinição /etc/grid-security/certificates deverá funcionar "
"correctamente na maior parte dos casos."

#. Type: string
#. Description
#: ../templates.in:5001
msgid "An alternative location can be given here if needed."
msgstr "Um local alternativo pode ser fornecido se necessário."

Bug#870081: electrum: Cold Storage wallet unusable due to upstream bug

[Vaclav Synacek]

Package: electrum
Version: 2.7.9-1
Severity: important

Dear Maintainer,

Cold Storage wallets are unable to sign a transaction in electrum version
2.7.9. This is an upstrem bug described in
https://github.com/spesmilo/electrum/issues/2508
and fixed in version 2.7.11
( https://github.com/spesmilo/electrum/blob/283/RELEASE-NOTES#L77 )

The impact of this issue is serious for users using cold storage electrum
as they are unable to spend any bitcoins in their cold wallets with this
version of this package.



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

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

Versions of packages electrum depends on:
ii  python   2.7.13-2
ii  python-electrum  2.7.9-1

Versions of packages electrum recommends:
ii  python-qt4  4.11.4+dfsg-2+b2

Versions of packages electrum suggests:
pn  python-btchip  
pn  python-trezor  
pn  python-zbar

-- no debconf information

Bug#869974: boinc: World Community Grid returns "Computation error" Job does not process

[Gianfranco Costamagna]

control: tags -1 moreinfo

Hello,
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Installed Boinc, no problems. Processes jobs from pogs (the Skynet) no 
> problems. Jobs from World Community Grid won't process.
>   
> 

I don't think this is a boinc issue, if you look at the computation error log 
(on website, or boinc-manager), 
you can actually have some more details on the issue.

However, I don't think this is a boinc problem, because the application is 
downloaded from the software itself, and it is built
by WGC people

G.



signature.asc
Description: OpenPGP digital signature

Bug#861378: Disable debian-chinese-b...@lists.debian.org list

[林上智]

CZ,

I agree with that.

Thanks for your effort.

--

SZ Lin (林上智) , *http://people.debian.org/~szlin
*

*Debian Developer*, debian.org.tw Administrator

4096R/ 178F 8338 B314 01E3 04FC 44BA A959 B38A 9561 F3F9


2017-07-29 22:38 GMT+08:00 Kan-Ru Chen :

> On Sat, Jul 29, 2017, at 10:32 PM, ChangZhuo Chen (陳昌倬) wrote:
> >
> > Hi All,
> >
> > I would like to propose to disable debian-chinese-b...@lists.debian.org
> > for the following reasons:
> >
> > * For Chinese translation related discuss, we already have
> >   debian-l10n-chinese@l.d.o
> >
> > * For Debian user in Taiwan, A new list debian-dug-taiwan has been
> >   requested (#847950).
> >
> > * Big5 encoding is deprecated long time ago.
> >
> >
> > Please raise your concern if you think we shall keep
> > debian-chinese-big5@l.d.o.
>
> Thanks for bringing this up!
>
> I concur we can decommission the debian-chinese-big5 list.
>
> Kanru
>
> > --
> > ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
> > http://czchen.info/
> > Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B
>

Bug#869689: Bug#870080: igtf-policy-bundle: [INTL:pt] Updated Portuguese translation for debconf messages

[Dennis van Dok]

Thanks, but now I have two translations. The earlier translation is tracked in 
bug 
#869689. Below is the diff; could you help sort out what to do about it?

Cheers,

Dennis


@@ -1,22 +1,22 @@
-# Translation of igtf-policy-bundle's debconf messages to European Portuguese
+# Translation of igtf-policy-bundle's debconf messages to Portuguese
 # Copyright (C) 2014 THE igtf-policy-bundle'S COPYRIGHT HOLDER
 # This file is distributed under the same license as the igtf-policy-bundle 
package.
 #
-# Américo Monteiro , 2014, 2017.
+# Américo Monteiro , 2014.
+# Rui Branco - DebianPT , 2017.
 msgid ""
 msgstr ""
 "Project-Id-Version: igtf-policy-bundle 1.85-1\n"
 "Report-Msgid-Bugs-To: igtf-policy-bun...@packages.debian.org\n"
 "POT-Creation-Date: 2017-07-24 17:44+0200\n"
-"PO-Revision-Date: 2017-07-25 17:59+\n"
-"Last-Translator: Américo Monteiro \n"
-"Language-Team: Portuguese <>\n"
+"PO-Revision-Date: 2017-07-29 17:05+0200\n"
+"Last-Translator: Rui Branco - DebianPT \n"
+"Language-Team: Portuguese \n"
 "Language: pt\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
-"X-Generator: Lokalize 2.0\n"
 
 #. Type: boolean
 #. Description
@@ -94,14 +94,12 @@ msgid ""
 "The default location /etc/grid-security/certificates should work fine in "
 "most cases."
 msgstr ""
-"A localização predefinida /etc/grid-security/certificates deverá funcionar "
-"bem na maioria dos casos."
+"O local por predefinição /etc/grid-security/certificates deverá funcionar "
+"correctamente na maior parte dos casos."
 
 #. Type: string
 #. Description
 #: ../templates.in:5001
 msgid "An alternative location can be given here if needed."
-msgstr ""
-"Pode ser fornecida aqui uma localização alternativa se tal for necessário."
-
+msgstr "Um local alternativo pode ser fornecido se necessário."
 

Bug#870083: prometheus-node-exporter: Inappropriate depends on daemon

[Tollef Fog Heen]

Package: prometheus-node-exporter
Version: 0.13.0+ds-1+b2
Severity: normal

Most systems don't need the daemon dependency since it's only used with
non-systemd setups.  It should be demoted to a Suggests or Recommends
rather than a depends.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#869574: stretch-pu: package kdepim/4:16.04.3-4

[Adam D. Barratt]

On Sat, 2017-07-29 at 14:24 +0200, Sandro Knauß wrote:
> Hey,
> 
> > currently in stretch is 4:16.04.3-3. Thus the version which should
> > preferably be used would be 4:16.04.3-3+deb9u1.
> 
> just to understand the process better:
> * Do I need to send another debdiff with the corrected versionnumber first 
> before uploading?

If by that you mean taking the previously incorrectly generated diff and
simply changing the version number it contains, then no.

> * Do I need to close this bug within the changelog entry?

No. The bug will be closed by us once the package is actually in stable.
Until that point, the process is incomplete, so closing the bug would be
illogical.

> * Are there any further issues with my debdiff?

Besides not being what has been requested multiple times?

The point of the process is to demonstrate that you can build - and have
built - your proposed upload against the release that you're proposing
to upload it to and to confirm what the debdiff of the resulting package
against the target release looks like.

It's entirely possible that it will be the same as the diff between the
stable and testing packages that you previously provided. That's by no
means certain, however, and in any case diffing things that aren't what
you're proposing to upload misses the point of the review step.

This isn't theoretical nitpicking. We've seen there be a distinct
difference between what people propose and what they actually upload
enough times in the past that there's no way we'll agree an update based
on a hypothetical diff rather than an actually built and tested one.

Regards,

Adam

Bug#861378: Disable debian-chinese-b...@lists.debian.org list

[Andrew Lee]

Thanks for bring up this proposal.
* I fully agree to disable -big5 list if we may keep the list archive for
old mail threads.
* Why do we use -dug-taiwan and not just simply use -taiwan for the list
name?

Best regards,
-Andrew

2017-07-29 22:32 GMT+08:00 ChangZhuo Chen (陳昌倬) :

>
> Hi All,
>
> I would like to propose to disable debian-chinese-b...@lists.debian.org
> for the following reasons:
>
> * For Chinese translation related discuss, we already have
>   debian-l10n-chinese@l.d.o
>
> * For Debian user in Taiwan, A new list debian-dug-taiwan has been
>   requested (#847950).
>
> * Big5 encoding is deprecated long time ago.
>
>
> Please raise your concern if you think we shall keep
> debian-chinese-big5@l.d.o.
>
>
> --
> ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
> http://czchen.info/
> Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B
>



-- 
-Andrew

Bug#870084: apt-listchanges: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: apt-listchanges
Version: 3.14
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for samba's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org







# Portuguese translation of apt-listchanges's debconf messages.
# 2007, Rui Branco 
# Rui Branco - DebianPT , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: apt-listchanges 3.14\n"
"Report-Msgid-Bugs-To: apt-listchan...@packages.debian.org\n"
"POT-Creation-Date: 2017-07-08 22:37+0200\n"
"PO-Revision-Date: 2017-07-29 16:28+\n"
"Last-Translator: Rui Branco - DebianPT \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: select
#. Choices
#: ../templates:2001
msgid "pager"
msgstr "pager"

#. Type: select
#. Choices
#: ../templates:2001
msgid "browser"
msgstr "browser"

#. Type: select
#. Choices
#: ../templates:2001
msgid "xterm-pager"
msgstr "xterm-pager"

#. Type: select
#. Choices
#: ../templates:2001
msgid "xterm-browser"
msgstr "xterm-browser"

#. Type: select
#. Choices
#: ../templates:2001
msgid "gtk"
msgstr "gtk"

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../templates:2001 ../templates:4001
msgid "text"
msgstr "texto"

#. Type: select
#. Choices
#: ../templates:2001
msgid "mail"
msgstr "mail"

#. Type: select
#. Choices
#: ../templates:2001
msgid "none"
msgstr "nenhum"

#. Type: select
#. Description
#: ../templates:2002
msgid "Method to be used to display changes:"
msgstr "Método de visualização das modificações:"

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"Changes in packages can be displayed in various ways by apt-listchanges:"
msgstr ""
"Modificações nos pacotes podem ser visualizadas de variados modos pelo apt-"
"listchanges:"

#. Type: select
#. Description
#: ../templates:2002
msgid ""
" pager: display changes one page at a time;\n"
" browser  : display HTML-formatted changes using a web browser;\n"
" xterm-pager  : like pager, but in an xterm in the background;\n"
" xterm-browser: like browser, but in an xterm in the background;\n"
" gtk  : display changes in a GTK window;\n"
" text : print changes to the terminal (without pausing);\n"
" mail : only send changes via e-mail;\n"
" none : do not run automatically from APT."
msgstr ""
" pager : visualizar modificações uma página de cada vez;\n"
" browser   : visualizar modificações em HTML com um browser web;\n"
" xterm-pager   : como um pager, mas com uma consola xterm em fundo;\n"
" xterm-browser : como um browser, mas·com·uma·consola·xterm·em·fundo;\n"
" gtk   : visualizar modificações numa janela GTK;\n"
" text  : envia as modificações para o seu terminal (sem pausa);\n"
" mail  : apenas envia as modificações via mail;\n"
" none  : não corre automaticamente a partir do APT."

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"This setting can be overridden at execution time. By default, all the "
"options except for 'none' will also send copies by mail."
msgstr ""
"Esta opção pode ser ultrapassada durante a execução. Por omissão, todas as "
"opções excepto 'none' podem também enviar uma cópia por mail."

#. Type: string
#. Description
#: ../templates:3001
msgid "E-mail address(es) which will receive changes:"
msgstr "Endereço(s) e-mail que receberá as modificações:"

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"Optionally, apt-listchanges can e-mail a copy of displayed changes to a "
"specified address."
msgstr ""
"Em opção, o apt-listchanges pode enviar por email uma cópia das modificações "
"visualizadas para um endereço específico."

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"Multiple addresses may be specified, delimited by commas. Leaving this field "
"empty disables mail notifications."
msgstr ""
"Podem ser especificados múltiplos endereços, delimitados por vírgulas. Deixe "
"este espaço vazio se não quiser que seja enviado qualquer notificação por "
"email."

#. Type: select
#. Choices
#: ../templates:4001
msgid "html"
msgstr "html"

#. Type: select
#. Description
#: ../templates:4002
msgid "Format of e-mail messages:"
msgstr "Formato das mensagens de e-mail:"

#. Type: select
#. Description
#: ../templates:4002
#| msgid "Please choose which type of changes should be displayed with APT."
msgid "Please choose a format of e-mail copies of the displayed changes."
msgstr ""
"Por favor escolha o formato das cópias de e-mail para visualização das"
" modificações."

#. Type: select
#. Description
#: ../templates:4002
msgid ""
" text  : plain text message;\n"
" html  : html data with clickable links."
msgstr ""
" texto 

Bug#859213: x11vnc: stack smashing detected: x11vnc terminated

[Octocrobe Pigloo]

I just had the problem at least 20 times today.


If the problem is corrected upstream since middle of 2016 I'm not sure to 
understand why it's still waiting for something before entering into debian 9. 
Some validation ? Obviously, the current one does not work, it cannot be worst.


Thank you !

Bug#870085: trackballs-data needs to replace trackballs << 1.2.3-1

[Stephen Kitt]

Package: trackballs-data
Version: 1.1.4-4.3
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

/usr/share/applications/trackballs.desktop moved from trackballs to
trackballs-data, but trackballs-data doesn’t break/replace trackballs,
resulting in

Preparing to unpack .../trackballs-data_1.2.3-1_all.deb ...
Unpacking trackballs-data (1.2.3-1) over (1.1.4-4.3) ...
dpkg: error processing archive 
/var/cache/apt/archives/trackballs-data_1.2.3-1_all.deb (--unpack):
 trying to overwrite '/usr/share/applications/trackballs.desktop', which is 
also in package trackballs 1.1.4-4.3
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

during upgrade attempts.

Please add the appropriate Breaks/Replaces relationships.

Regards,

Stephen


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

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

-- no debconf information