Bug#827800: calendar-exchange-provider: Description textbox missing

[Anders Boström]

Package: calendar-exchange-provider
Version: 3.5.0-1~bpo80+1
Severity: important

After upgrade to icedove 45.1, the description textbox is
missing when editing an event.

Same problem is reported upstream, see
https://github.com/Ericsson/exchangecalendar/issues/485 , and is
marked as fixed in the "latest 3.8 beta release".

/ Anders

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (94, 
'proposed-updates'), (60, 'testing'), (45, 'testing-proposed-updates'), (40, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages calendar-exchange-provider depends on:
ii  icedove   1:45.1.0-1~deb8u1
ii  iceowl-extension  1:45.1.0-1~deb8u1

calendar-exchange-provider recommends no packages.

calendar-exchange-provider suggests no packages.

-- no debconf information

Bug#827736: RFS: mpd-sima/0.14.1-2 [RC]

[Geoff]

Thanks very much for your review/upload.

Geoff

Le 20/06/2016 à 14:20, Gianfranco Costamagna a écrit :


   * Fixed insecure vcs-field uri




that commit was bad, missing a /git/ in path.

corrected, changed target from UNRELEASED to unstable, signed, uploaded
and committed on git.

G.

Bug#827799: libglm-dev: find_package(glm) in CMake fails

[Björn Steinbrink]

Package: libglm-dev
Version: 0.9.7.5-1
Severity: normal

Dear Maintainer,

trying to include glm in a project using CMake using:

find_package(glm REQUIRED)

results in the following error:


  File or directory //include referenced by variable GLM_INCLUDE_DIRS does
  not exist !
Call Stack (most recent call first):
  /usr/lib/cmake/glm/glmConfig.cmake:16 (set_and_check)
  CMakeLists.txt:14 (find_package)

The problem seems to be an extra set of "../" in
/usr/lib/cmake/glm/glmConfig.cmake


-- 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.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)

-- no debconf information

Bug#812079: apt-cacher-ng delivers outdated release files

[Joerg Dorchain]

On Wed, Jan 20, 2016 at 08:05:46PM +0100, Eduard Bloch wrote:
> > 
> > I am following debian testing, and do updates almost every other
> > day. I use apt-cacher-ng via the Acquire::http::Proxy setting in
> > apt.
> > 
> > Apt-cacher-ng seems not to expire the metadata, so doing apt-get
> > update does not show any new packages, not even after a week.
> 
Finally, I was able to track this behaviour down to a specific
mirror I had setup in /etc/apt-cacher-ng/backends_debian

When I use http://ftp.freenet.de/debian/ as a first line in it.
strange things (i.e. keeping outdated data in the cache) happen.
Other mirrors, e.g. http://ftp.uni-kl.de/debian/ work fine.

I was not able to dig into difference between those two mirror
servers.

Bye,

Joerg


signature.asc
Description: PGP signature

Bug#827801: gcc-5/gcc-6: Please enable the default optimize arch to mips32r2 for o32

[YunQiang Su]

Package: src:gcc-6

This patch switch the default arch for mips o32 to mips32r2.
We switch this so late due to the previous lack of build machines,
and we still had a loongson 2f machine.

And gcc support FPXX from 5.
We can support Loongson 3 only with FPXX support.

And now, the 2f machines has been removed from Debian,
so it is time for us to switch this.

Please also add this patch to gcc-5.

do *NOT* apply it to gcc-4.9.

-- 
YunQiang Su
diff --git a/debian/rules2 b/debian/rules2
index 0f3eddc..4753af2 100644
--- a/debian/rules2
+++ b/debian/rules2
@@ -633,11 +633,11 @@ ifneq (,$(findstring mips-linux,$(DEB_TARGET_GNU_TYPE)))
 endif
 
 ifneq (,$(findstring mipsel-linux,$(DEB_TARGET_GNU_TYPE)))
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32r2 --with-fp-32=xx
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch64),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64r2
+  CONFARGS += --with-arch-64=mips64r2
 endif
   endif
 endif
@@ -647,8 +647,8 @@ ifneq (,$(findstring 
mips64el-linux-gnuabin32,$(DEB_TARGET_GNU_TYPE)))
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch32),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32 --with-fp-32=xx
+  CONFARGS += --with-arch-64=mips64r2
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
 endif
   endif
 endif
@@ -657,8 +657,8 @@ ifneq (,$(findstring 
mips64-linux-gnuabin32,$(DEB_TARGET_GNU_TYPE)))
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch32),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32 --with-fp-32=xx
+  CONFARGS += --with-arch-64=mips64r2
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
 endif
   endif
 endif

Bug#827814: [uscan] Please always download the newest of all versions if more than one main upstream tarball is listed (i.e. consider it a feature, not a problem)

[Axel Beckert]

Package: devscripts
Version: 2.16.5
Severity: wishlist
File: /usr/bin/uscan

Hi,

I've got several upstreams which have several places where they publish tar
balls.

There are at least three kinds of cases:

1. Not that seldom it's a combination of sometimes less reliable (but
   earlier filled) developer-maintained/-centric primary server and a
   reliable mirror network.

   (More or less) example: screen

   https://ftp.gnu.org/gnu/screen/screen-([\d\.]+)\.tar\.gz
   http://download.savannah.gnu.org/releases/screen/screen-([\d\.]+)\.tar\.gz

2. Another case are beta releases and final releases being in
   different directories, but I want to track both.

   Example: zsh

   http://www.zsh.org/pub/zsh-(\d[^\sd]*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz))
   
http://www.zsh.org/pub/development/zsh-(\d[^\sd]*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz))

3. A third case are upstreams which sometimes forget to upload
   manually build tar balls to Github, but have already tagged their
   new upstream release.

   Example (from a recent NMU of mine, still waiting in DELAYED/10): flashbake

   http://github.com/commandline/flashbake/releases 
/commandline/flashbake/archive/(.*)\.tar\.gz
   http://github.com/commandline/flashbake/downloads 
/downloads/commandline/flashbake/flashbake-(.*)\.tar\.gz

>From my point of view, these are all perfectly sane usages of more
than one main upstream tarballs.

Unfortunately, at least in the 2rd case, if the first line finds a
newer version, an even newer version from the second line is ignored
and not the newest version is downloaded.

So please fully support such setups, always download the newest
version over all download sites specificed and don't emit "uscan warn:
more than one main upstream tarballs listed." about such setups
anymore.

Additionally, such watch files cause false positives in PTS and
Tracker because this warning is considered to be an error by PTS and
Tracker and shows up there as TODO. Examples:

  https://packages.qa.debian.org/s/screen.html
  https://tracker.debian.org/pkg/screen
  https://packages.qa.debian.org/z/zsh.html
  https://tracker.debian.org/pkg/zsh
  https://packages.qa.debian.org/f/flashbake.html
  https://tracker.debian.org/pkg/flashbake

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-k2FF9CD59612616B5 -i"
DSCVERIFY_KEYRINGS=/home/abe/.gnupg/pubring.gpg
DEBUILD_LINTIAN_OPTS="-iIE --pedantic"

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

Kernel: Linux 4.5.0-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.7
ii  libc62.22-12
ii  perl 5.22.2-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  apt 1.2.13
pn  at  
ii  curl7.47.0-1
ii  dctrl-tools 2.24-2
ii  debian-keyring  2016.06.19
ii  dput-ng [dput]  1.10
ii  dupload 2.7.0
ii  equivs  2.0.9+nmu1
ii  fakeroot1.20.2-2
ii  file1:5.25-2
ii  gnupg   1.4.20-6
ii  gnupg2  2.1.11-7
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.05-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.19-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  lintian 2.5.45
ii  man-db  2.7.5-1
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
ii  pseudo [fakeroot]   1.7.5-5
ii  python3-debian  0.1.28
ii  python3-magic   1:5.25-2
ii  sensible-utils  0.0.9
ii  strace  4.12-3
ii  unzip   6.0-20
ii  wdiff   1.2.2-1+b1
ii  wget1.18-1
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-3
ii  build-essential  12.2
ii  cvs-buildpackage 5.26
ii  devscripts-el35.12
ii  diffoscope   54
pn  dose-extra   
ii  gnuplot  5.0.3+dfsg3-7
ii  gpgv 1.4.20-6
ii  gpgv22.1.11-7
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.22-1
ii  libnet-smtp-ssl-perl 1.03-1
ii  libterm-size-perl0.207-1+b3
ii  libtimedate-perl  

Bug#826858: ostree: FTBFS due to test suite errors

[Simon McVittie]

Control: clone 826858 -2
Control: retitle 826858 ostree: FTBFS on i386, hppa: Opening objects/ 
directory: openat: No such file or directory
Control: tags 826858 + unreproducible
Control: retitle -2 ostree: FTBFS on sparc64: gjs: Segmentation fault
Control: notforwarded -2
Control: severity -2 normal

On Thu, 09 Jun 2016 at 10:35:48 -0400, Aaron M. Ucko wrote:
> - On i386:
...
> - On hppa (admittedly not a release architecture):
...

These share a symptom ("Opening objects/ directory: openat: No such file or
directory"), which wasn't seen again in 2016.5-4, and I couldn't reproduce it
on i386 locally. I assume this was either some transient infrastructure issue,
or an ostree bug that rarely occurs (perhaps a race condition).

> - On sparc64 (not a release architecture either):

This appears to be a separate issue, and was also visible in 2016.5-4.
Cloning a separate bug for this one.

S

Bug#33263: [dpkg] same as #30126

[Lorenz Wenner]

Package: dpkg
Version: 1.17.27

--- Please enter the report below this line. ---

i think this is the same as #30126 which i found to be fixed, since 
dpkg-divert puts out the info that directories are not supported.


--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: 8.5
  500 stable-updates  ftp.de.debian.org   500 stable 
security.debian.org   500 stable  packages.x2go.org   500 stable 
 ftp.de.debian.org   500 stable  dl.google.com   100 
jessie-backports ftp.de.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
apt | 1.0.9.8.3

Bug#756630: newusers fails adding multiple users

[Mònica Ramírez Arceda]

Hi,

I can confirm this bug. Using a file with 5 new users I get the
following error:

# newusers 5users.csv 
*** Error in `newusers': double free or corruption (!prev): 0x01ae2d10 
***
Aborted

A curious detail: if the first 4 users are already created and I run
newusers, the 5th one is added without problems. If I have 6 users in
the file and the first 5 users are already created the 6th one is added
without problems. And so on.

$ dpkg -s passwd | grep 'Version'
Version: 1:4.2-3.1

Bug#827803: Change default code size limit from 64k

[Dave Page]

Package: pnopaste
Version: 1.5-2
Severity: wishlist

Dear Maintainer,

The default paste size of 64k with silent truncation is 
counter-intuitive; many application logs etc. can easily be bigger than 
this.


It seems easy to change the "code" field from TEXT to MEDIUMTEXT, upping 
the limit to 16Mb - I suggest this would be a more appropriate setting.


Cheers,
Dave

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

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

Versions of packages pnopaste depends on:
ii  dbconfig-common   1.8.47+nmu3+deb8u1
ii  debconf [debconf-2.0] 1.5.56
ii  libgeo-ip-perl1.45-1
ii  libsyntax-highlight-engine-kate-perl  0.09+dfsg-1
ii  perl  5.20.2-3+deb8u5

Versions of packages pnopaste recommends:
ii  apache2 [httpd]  2.4.10-10+deb8u4

Versions of packages pnopaste suggests:
pn  pnopaste-cli  

-- debconf information:
  pnopaste/db/basepath:
  pnopaste/db/dbname: pnopaste
  pnopaste/dbconfig-remove:
  pnopaste/pgsql/changeconf: false
  pnopaste/remove-error: abort
  pnopaste/install-error: abort
  pnopaste/dbconfig-reinstall: false
  pnopaste/mysql/admin-user: root
  pnopaste/database-type: mysql
  pnopaste/dbconfig-upgrade: true
  pnopaste/db/app-user: pnopaste
  pnopaste/pgsql/authmethod-admin: ident
  pnopaste/pgsql/manualconf:
  pnopaste/internal/skip-preseed: false
  pnopaste/remote/newhost:
  pnopaste/dbconfig-install: true
  pnopaste/missing-db-package-error: abort
  pnopaste/remote/host:
  pnopaste/mysql/method: unix socket
  pnopaste/internal/reconfiguring: false
  pnopaste/pgsql/authmethod-user: password
  pnopaste/pgsql/no-empty-passwords:
  pnopaste/upgrade-backup: true
  pnopaste/purge: false
  pnopaste/passwords-do-not-match:
  pnopaste/remote/port:
  pnopaste/pgsql/admin-user: postgres
  pnopaste/pgsql/method: unix socket
  pnopaste/upgrade-error: abort

--
Dave Page, Operations Team Manager, Senior Systems Engineer, Codethink Ltd
Telephone: +44 7762 840 414  302 Ducie House, Ducie Street
http://www.codethink.co.uk/ Manchester, M1 2JW, United Kingdom

Bug#827817: openjdk-7-jre: .jar files cannot be opened with double-click

[Andreas Heinlein]

Package: openjdk-7-jre
Version: 7u101-2.6.6-2~deb8u1
Severity: normal

Dear Maintainer,

I used to be able to run Java .jar files by double clicking them, which is not
possible with debian 8. "OpenJDK runtime" is also not available when choosing
"Open With..."
There was once a file /usr/share/applications/openjdk-7-java.desktop, which is
not included in the package anymore. There are files in /usr/share/application-
registry (obsolete, AFAIK) and /usr/share/mime-info, but these alone obviously
don't work.
Google turns up several results on that matter, many of them ending up with
either re-creating openjdk-7-java.desktop or manually associating .jar files
with "java -jar...", but IMHO this should work out of the box.



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

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

Versions of packages openjdk-7-jre depends on:
ii  libasound21.0.28-1
ii  libatk-wrapper-java-jni   0.30.5-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u4
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libgif4   4.1.6-11+deb8u1
ii  libgl1-mesa-glx [libgl1]  11.1.3-1~bpo8+1
ii  libglib2.0-0  2.48.0-1~bpo8+1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libjpeg62-turbo   1:1.3.1-12
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpng12-01.2.50-2+deb8u2
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxext6  2:1.3.3-1
ii  libxi62:1.7.4-1+b2
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  libxrender1   1:0.9.8-1+b1
ii  libxtst6  2:1.2.2-1+b1
ii  openjdk-7-jre-headless7u101-2.6.6-2~deb8u1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openjdk-7-jre recommends:
ii  fonts-dejavu-extra  2.34-1
ii  libgconf2-4 3.2.6-3
ii  libgnome2-0 2.32.1-5
ii  libgnomevfs2-0  1:2.24.4-6+b1

Versions of packages openjdk-7-jre suggests:
pn  icedtea-7-plugin  

-- no debconf information

Bug#827816: reprepro: add mail-changes.example to notify when (at least) 'accepted' packages

[Luca Capello]

tags 827816 + patch
thanks

On Tue, 21 Jun 2016 13:07:17 +0200, Luca Capello wrote:
> Tested patch for ACTION=3Daccepted (thus to be extended later on) as soon
> as this bug get a number :-)

Here we are:

--8<---cut here---start->8---
From 044e268f9bd32f18165014667a8f3284cecab0ee Mon Sep 17 00:00:00 2001
From: Luca Capello 
Date: Tue, 21 Jun 2016 13:17:23 +0200
Subject: [PATCH] docs/mail-changes.example: (#827816) new file

---
 debian/changelog  |  7 +
 debian/examples   |  1 +
 docs/mail-changes.example | 69 +++
 3 files changed, 77 insertions(+)
 create mode 100755 docs/mail-changes.example

diff --git a/debian/changelog b/debian/changelog
index 1304fde..14c0ea3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+reprepro (4.17.1-2) UNRELEASED; urgency=medium
+
+  * debian/examples, docs/mail-changes.example:
++ new file to notify processing of .changes files (Closes: #827816).
+
+ -- Luca Capello   Tue, 21 Jun 2016 13:16:06 +0200
+
 reprepro (4.17.1-1) unstable; urgency=medium
 
   * new bugfix release
diff --git a/debian/examples b/debian/examples
index 8754d4d..afc97a7 100644
--- a/debian/examples
+++ b/debian/examples
@@ -7,3 +7,4 @@ docs/copybyhand.example
 docs/outstore.py
 docs/sftp.py
 docs/outsftphook.py
+docs/mail-changes.example
diff --git a/docs/mail-changes.example b/docs/mail-changes.example
new file mode 100755
index 000..2402aaf
--- /dev/null
+++ b/docs/mail-changes.example
@@ -0,0 +1,69 @@
+#!/bin/sh
+#
+#
+# Copyright 2016 Luca Capello 
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# 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 St, Fifth Floor, Boston, MA  02111-1301  USA
+#
+#
+# This is an example script that can be hooked into reprepro
+# to send an email after a .changes file is processed.
+#
+# All you have to do is to:
+# - copy it into you conf/ directory,
+# - add the following to any distribution in conf/distributions
+#   you want to have emails sent for:
+#Log:
+# --changes mail-changes.example
+# (note the space at the beginning of the second line).
+#
+# DEPENDENCIES: mailx
+
+
+set -e
+
+
+if test "x${REPREPRO_OUT_DIR:+set}" = xset ; then
+   # Note: due to cd, REPREPRO_*_DIR will no longer
+   # be usable. And only things relative to outdir will work...
+   cd "${REPREPRO_OUT_DIR}" || exit 1
+else
+   # this will also trigger if reprepro < 3.5.1 is used,
+   # in that case replace this with a manual cd to the
+   # correct directory...
+   cat "mail-accepted.example needs to be run by reprepro!" >&2
+   exit 1
+fi
+
+
+MAIL_TO="$USER"
+
+ACTION="$1"
+CODENAME="$2"
+PACKAGENAME="$3"
+PACKAGEVERSION="$4"
+CHANGESFILE="$5"
+
+if [ "x$ACTION" = "xaccepted" ]; then
+   MAIL_FROM="$(grep Changed-By $CHANGESFILE | \
+ sed -e 's/Changed-By/From/')"
+   ARCHITECTURE="$(grep Architecture $CHANGESFILE | \
+sed -e 's/Architecture: //')"
+   MAIL_SUBJECT="Accepted $PACKAGENAME $PACKAGEVERSION ($ARCHITECTURE) 
into $CODENAME"
+   cat "$CHANGESFILE" | \
+mail -a "$MAIL_FROM" -s "$MAIL_SUBJECT" "$MAIL_TO"
+fi
+
+
+exit 0
-- 
2.1.4

--8<---cut here---end--->8---

Thx, bye,
Gismo / Luca

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA


signature.asc
Description: Digital signature

Bug#817385: Moving Bytecode to Debian Med (or Java) Git

[Olivier Sallou]

I see that package is used at runtime only in reverse dependencies
(biojava), this is not a build dependency, so I have no way to validate
the library.

Compilation looks fine, and package looks ok.

should I go for a package upload (to prevent removal of other packages) ?

I have not tried to update to any recent release, focusing on getting
the same working release to fix bug.

Olivier

On 06/20/2016 09:51 PM, Andreas Tille wrote:
> On Mon, Jun 20, 2016 at 03:38:46PM +0200, Olivier Sallou wrote:
>> I made a quick fix to switch to compat 9 and fix Java version to current
>> jdk in sid.
>>
>> However, i cannot push to pkg-escience / bytecode (permission denied).
> Since pkg-escience is closed.
>  
>> It would be best to move package to pkg-java instead of debianmed
>> according to me, as it is pure Java package.
> That would be also my first idea.
>
>> Patching is quite easy:
>>
>> switch d/compat to 9 (no issue)
>>
>> d/control: update dependencies to use default-jdk and default-jre
>> instead of openjdk/sun-jdk/java2-compiler
>>
>> add a patch to build.xml to add in all javac commands :  source="1.6"
>> target="1.6"
>>
>> build is fine with no specific lintian error
> Would you volunteer to move it to pkg-java Git?
>
> Kind regards
>
>   Andreas.
>

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#827806: pyevolve: FTBFS: Program terminated with status: 1. stderr follows: Format: "jpeg" not recognized

[Chris Lamb]

Source: pyevolve
Version: 0.6~rc1+svn398+dfsg-9
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,

pyevolve fails to build from source in unstable/amd64:

  [..]

  Gen. 276 (55.20%): Max/Min/Avg Fitness(Raw) [0.48(1.00)/0.35(0.00)/0.40(0.40)]
  Gen. 277 (55.40%): Max/Min/Avg Fitness(Raw) [0.75(1.00)/0.42(0.00)/0.63(0.63)]
  Gen. 278 (55.60%): Max/Min/Avg Fitness(Raw) [0.51(1.00)/0.36(0.00)/0.43(0.43)]
  Gen. 279 (55.80%): Max/Min/Avg Fitness(Raw) [0.63(1.00)/0.41(0.00)/0.53(0.53)]
  Gen. 280 (56.00%): Max/Min/Avg Fitness(Raw) [0.69(1.00)/0.42(0.00)/0.58(0.58)]
  Gen. 281 (56.20%): Max/Min/Avg Fitness(Raw) [0.54(1.00)/0.38(0.00)/0.45(0.45)]
  Gen. 282 (56.40%): Max/Min/Avg Fitness(Raw) [0.50(1.00)/0.36(0.00)/0.41(0.41)]
  Gen. 283 (56.60%): Max/Min/Avg Fitness(Raw) [0.51(1.00)/0.36(0.00)/0.43(0.43)]
  Gen. 284 (56.80%): Max/Min/Avg Fitness(Raw) [0.47(1.00)/0.34(0.00)/0.39(0.39)]
  Gen. 285 (57.00%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 286 (57.20%): Max/Min/Avg Fitness(Raw) [0.59(1.00)/0.40(0.00)/0.49(0.49)]
  Gen. 287 (57.40%): Max/Min/Avg Fitness(Raw) [0.63(1.00)/0.41(0.00)/0.53(0.53)]
  Gen. 288 (57.60%): Max/Min/Avg Fitness(Raw) [0.71(1.00)/0.42(0.00)/0.59(0.59)]
  Gen. 289 (57.80%): Max/Min/Avg Fitness(Raw) [0.60(1.00)/0.40(0.00)/0.50(0.50)]
  Gen. 290 (58.00%): Max/Min/Avg Fitness(Raw) [0.69(1.00)/0.42(0.00)/0.58(0.58)]
  Gen. 291 (58.20%): Max/Min/Avg Fitness(Raw) [0.71(1.00)/0.42(0.00)/0.59(0.59)]
  Gen. 292 (58.40%): Max/Min/Avg Fitness(Raw) [0.53(1.00)/0.37(0.00)/0.44(0.44)]
  Gen. 293 (58.60%): Max/Min/Avg Fitness(Raw) [0.74(1.00)/0.42(0.00)/0.61(0.61)]
  Gen. 294 (58.80%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 295 (59.00%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 296 (59.20%): Max/Min/Avg Fitness(Raw) [0.66(1.00)/0.42(0.00)/0.55(0.55)]
  Gen. 297 (59.40%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 298 (59.60%): Max/Min/Avg Fitness(Raw) [0.57(1.00)/0.39(0.00)/0.48(0.48)]
  Gen. 299 (59.80%): Max/Min/Avg Fitness(Raw) [0.60(1.00)/0.40(0.00)/0.50(0.50)]
  Gen. 300 (60.00%): Max/Min/Avg Fitness(Raw) [0.63(1.00)/0.41(0.00)/0.53(0.53)]
  Gen. 301 (60.20%): Max/Min/Avg Fitness(Raw) [0.50(1.00)/0.36(0.00)/0.41(0.41)]
  Gen. 302 (60.40%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 303 (60.60%): Max/Min/Avg Fitness(Raw) [0.69(1.00)/0.42(0.00)/0.58(0.58)]
  Gen. 304 (60.80%): Max/Min/Avg Fitness(Raw) [0.60(1.00)/0.40(0.00)/0.50(0.50)]
  Gen. 305 (61.00%): Max/Min/Avg Fitness(Raw) [0.60(1.00)/0.40(0.00)/0.50(0.50)]
  Gen. 306 (61.20%): Max/Min/Avg Fitness(Raw) [0.68(1.00)/0.42(0.00)/0.56(0.56)]
  Gen. 307 (61.40%): Max/Min/Avg Fitness(Raw) [0.42(1.00)/0.31(0.00)/0.35(0.35)]
  Gen. 308 (61.60%): Max/Min/Avg Fitness(Raw) [0.74(1.00)/0.42(0.00)/0.61(0.61)]
  Gen. 309 (61.80%): Max/Min/Avg Fitness(Raw) [0.62(1.00)/0.41(0.00)/0.51(0.51)]
  Gen. 310 (62.00%): Max/Min/Avg Fitness(Raw) [0.47(1.00)/0.34(0.00)/0.39(0.39)]
  Gen. 311 (62.20%): Max/Min/Avg Fitness(Raw) [0.62(1.00)/0.41(0.00)/0.51(0.51)]
  Gen. 312 (62.40%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 313 (62.60%): Max/Min/Avg Fitness(Raw) [0.56(1.00)/0.38(0.00)/0.46(0.46)]
  Gen. 314 (62.80%): Max/Min/Avg Fitness(Raw) [0.53(1.00)/0.37(0.00)/0.44(0.44)]
  Gen. 315 (63.00%): Max/Min/Avg Fitness(Raw) [0.69(1.00)/0.42(0.00)/0.58(0.58)]
  Gen. 316 (63.20%): Max/Min/Avg Fitness(Raw) [0.59(1.00)/0.40(0.00)/0.49(0.49)]
  Gen. 317 (63.40%): Max/Min/Avg Fitness(Raw) [0.66(1.00)/0.42(0.00)/0.55(0.55)]
  Gen. 318 (63.60%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 319 (63.80%): Max/Min/Avg Fitness(Raw) [0.80(1.00)/0.40(0.00)/0.66(0.66)]
  Gen. 320 (64.00%): Max/Min/Avg Fitness(Raw) [0.60(1.00)/0.40(0.00)/0.50(0.50)]
  Gen. 321 (64.20%): Max/Min/Avg Fitness(Raw) [0.57(1.00)/0.39(0.00)/0.48(0.48)]
  Gen. 322 (64.40%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 323 (64.60%): Max/Min/Avg Fitness(Raw) [0.66(1.00)/0.42(0.00)/0.55(0.55)]
  Gen. 324 (64.80%): Max/Min/Avg Fitness(Raw) [0.63(1.00)/0.41(0.00)/0.53(0.53)]
  Gen. 325 (65.00%): Max/Min/Avg Fitness(Raw) [0.75(1.00)/0.42(0.00)/0.63(0.63)]
  Gen. 326 (65.20%): Max/Min/Avg Fitness(Raw) [0.66(1.00)/0.42(0.00)/0.55(0.55)]
  Gen. 327 (65.40%): Max/Min/Avg Fitness(Raw) [0.68(1.00)/0.42(0.00)/0.56(0.56)]
  Gen. 328 (65.60%): Max/Min/Avg Fitness(Raw) [0.57(1.00)/0.39(0.00)/0.48(0.48)]
  Gen. 329 (65.80%): Max/Min/Avg Fitness(Raw) [0.63(1.00)/0.41(0.00)/0.53(0.53)]
  Gen. 330 (66.00%): Max/Min/Avg Fitness(Raw) [0.71(1.00)/0.42(0.00)/0.59(0.59)]
  Gen. 331 (66.20%): Max/Min/Avg Fitness(Raw) [0.65(1.00)/0.41(0.00)/0.54(0.54)]
  Gen. 332 (66.40%): Max/Min/Avg Fitness(Raw) [0.56(1.00)/0.38(0.00)/0.46(0.46)]
  Gen. 333 (66.60%): Max/Min/Avg Fitness(Raw) 

Bug#827811: signond: FTBFS: dh_makeshlibs: failing due to earlier errors

[Chris Lamb]

Source: signond
Version: 8.57+20150423-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,

signond fails to build from source in unstable/amd64:

  [..]

  Running dot for graph 184/204
  Running dot for graph 185/204
  Running dot for graph 186/204
  Running dot for graph 187/204
  Running dot for graph 188/204
  Running dot for graph 189/204
  Running dot for graph 190/204
  Running dot for graph 191/204
  Running dot for graph 192/204
  Running dot for graph 193/204
  Running dot for graph 194/204
  Running dot for graph 195/204
  Running dot for graph 196/204
  Running dot for graph 197/204
  Running dot for graph 198/204
  Running dot for graph 199/204
  Running dot for graph 200/204
  Running dot for graph 201/204
  Running dot for graph 202/204
  Running dot for graph 203/204
  Running dot for graph 204/204
  Patching output file 1/104
  Patching output file 2/104
  Patching output file 3/104
  Patching output file 4/104
  Patching output file 5/104
  Patching output file 6/104
  Patching output file 7/104
  Patching output file 8/104
  Patching output file 9/104
  Patching output file 10/104
  Patching output file 11/104
  Patching output file 12/104
  Patching output file 13/104
  Patching output file 14/104
  Patching output file 15/104
  Patching output file 16/104
  Patching output file 17/104
  Patching output file 18/104
  Patching output file 19/104
  Patching output file 20/104
  Patching output file 21/104
  Patching output file 22/104
  Patching output file 23/104
  Patching output file 24/104
  Patching output file 25/104
  Patching output file 26/104
  Patching output file 27/104
  Patching output file 28/104
  Patching output file 29/104
  Patching output file 30/104
  Patching output file 31/104
  Patching output file 32/104
  Patching output file 33/104
  Patching output file 34/104
  Patching output file 35/104
  Patching output file 36/104
  Patching output file 37/104
  PatchingBuilding up file structure...
  Insert custom filters...
  Insert help data for filter section (1 of 1)...
  Insert files...
  Insert contents...
  Insert indices...
  Documentation successfully generated.
   output file 38/104
  Patching output file 39/104
  Patching output file 40/104
  Patching output file 41/104
  Patching output file 42/104
  Patching output file 43/104
  Patching output file 44/104
  Patching output file 45/104
  Patching output file 46/104
  Patching output file 47/104
  Patching output file 48/104
  Patching output file 49/104
  Patching output file 50/104
  Patching output file 51/104
  Patching output file 52/104
  Patching output file 53/104
  Patching output file 54/104
  Patching output file 55/104
  Patching output file 56/104
  Patching output file 57/104
  Patching output file 58/104
  Patching output file 59/104
  Patching output file 60/104
  Patching output file 61/104
  Patching output file 62/104
  Patching output file 63/104
  Patching output file 64/104
  Patching output file 65/104
  Patching output file 66/104
  Patching output file 67/104
  Patching output file 68/104
  Patching output file 69/104
  Patching output file 70/104
  Patching output file 71/104
  Patching output file 72/104
  Patching output file 73/104
  Patching output file 74/104
  Patching output file 75/104
  Patching output file 76/104
  Patching output file 77/104
  Patching output file 78/104
  Patching output file 79/104
  Patching output file 80/104
  Patching output file 81/104
  Patching output file 82/104
  Patching output file 83/104
  Patching output file 84/104
  Patching output file 85/104
  Patching output file 86/104
  Patching output file 87/104
  Patching output file 88/104
  Patching output file 89/104
  Patching output file 90/104
  Patching output file 91/104
  Patching output file 92/104
  Patching output file 93/104
  Patching output file 94/104
  Patching output file 95/104
  Patching output file 96/104
  Patching output file 97/104
  Patching output file 98/104
  Patching output file 99/104
  Patching output file 100/104
  Patching output file 101/104
  Patching output file 102/104
  Patching output file 103/104
  Patching output file 104/104
  Running qhelpgenerator...
  lookup cache used 2597/65536 hits=17363 misses=2656
  finished...
  cp -f -R 
/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423/build/qt5/doc/html
 
/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423/debian/tmp/usr/share/doc/signon/
  cp -f -R 
/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423/build/qt5/doc/qch
 
/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423/debian/tmp/usr/share/doc/signon/
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423/build/qt5'
  make[2]: Leaving directory 

Bug#827810: scanlogd: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

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

Dear Maintainer,

scanlogd fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  scanlogd
   Version:  2.2.5-3.2
   Build architecture:   amd64
   Date: Tue, 21 Jun 2016 10:50:16 +0100
   Hostname: fb14883e52d8
   Uname:Linux fb14883e52d8 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'scanlogd-build-deps' in 
'../scanlogd-build-deps_2.2.5-3.2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package scanlogd-build-deps.
  (Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack scanlogd-build-deps_2.2.5-3.2_all.deb ...
  Unpacking scanlogd-build-deps (2.2.5-3.2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up scanlogd-build-deps (2.2.5-3.2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=fb14883e52d8
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd/scanlogd-2.2.5
  OLDPWD=/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building scanlogd 2.2.5-3.2 on amd64   
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package scanlogd
  dpkg-buildpackage: info: source version 2.2.5-3.2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Andreas Beckmann 
   dpkg-source --before-build scanlogd-2.2.5
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp configure-stamp
  # Add here commands to clean up after the build process.
  /usr/bin/make clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd/scanlogd-2.2.5'
  rm -f scanlogd scanlogd.o in_linux.o in_nids.o in_pcap.o
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd/scanlogd-2.2.5'
  dh_clean
  dh_clean: Please specify the compatibility level in debian/compat
  debian/rules:32: recipe for target 'clean' failed
  make: *** [clean] Error 2

  [..]

The full build log is attached.


Regards,

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


scanlogd.2.2.5-3.2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#827804: breathe: FTBFS: ValueError: too many values to unpack (expected 2)

[Chris Lamb]

Source: breathe
Version: 4.2.0-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,

breathe fails to build from source in unstable/amd64:

  [..]

doctestto run all doctests embedded in the documentation (if enabled)
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160621103729.4bz1RgeTbD.breathe/breathe-4.2.0/documentation'
  /bin/sh: 1: cd: can't cd to ../../examples/tinyxml
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160621103729.4bz1RgeTbD.breathe/breathe-4.2.0/documentation'
  Please use `make ' where  is one of
html   to make standalone HTML files
dirhtmlto make HTML files named index.html in directories
singlehtml to make a single large HTML file
pickle to make pickle files
json   to make JSON files
htmlhelp   to make HTML files and a HTML help project
qthelp to make HTML files and a qthelp project
devhelpto make HTML files and a Devhelp project
epub   to make an epub
latex  to make LaTeX files, you can set PAPER=a4 or PAPER=letter
latexpdf   to make LaTeX files and run them through pdflatex
latexpdfja to make LaTeX files and run them through platex/dvipdfmx
text   to make text files
manto make manual pages
texinfoto make Texinfo files
info   to make Texinfo files and run them through makeinfo
gettextto make PO message catalogs
changesto make an overview of all changed/added/deprecated items
xmlto make Docutils-native XML files
pseudoxml  to make pseudoxml-XML files for display purposes
linkcheck  to check all external links for integrity
doctestto run all doctests embedded in the documentation (if enabled)
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160621103729.4bz1RgeTbD.breathe/breathe-4.2.0/documentation'
  building [mo]: targets for 0 po files that are out of date
  building [html]: targets for 36 source files that are out of date
  updating environment: 36 added, 0 changed, 0 removed
  reading sources... [  2%] autofile
  reading sources... [  5%] autoindex
  reading sources... [  8%] class
  Exception occurred while building, starting debugger:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/cmdline.py", line 244, in main
  app.build(opts.force_all, filenames)
File "/usr/lib/python3/dist-packages/sphinx/application.py", line 298, in 
build
  self.builder.build_update()
File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 
251, in build_update
  'out of date' % len(to_build))
File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 
265, in build
  self.doctreedir, self.app))
File "/usr/lib/python3/dist-packages/sphinx/environment.py", line 564, in 
update
  self._read_serial(docnames, app)
File "/usr/lib/python3/dist-packages/sphinx/environment.py", line 584, in 
_read_serial
  self.read_doc(docname, app)
File "/usr/lib/python3/dist-packages/sphinx/environment.py", line 737, in 
read_doc
  pub.publish()
File "/usr/lib/python3/dist-packages/docutils/core.py", line 217, in publish
  self.settings)
File "/usr/lib/python3/dist-packages/sphinx/io.py", line 49, in read
  self.parse()
File "/usr/lib/python3/dist-packages/docutils/readers/__init__.py", line 
78, in parse
  self.parser.parse(self.input, document)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/__init__.py", 
line 172, in parse
  self.statemachine.run(inputlines, document, inliner=self.inliner)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
171, in run
  input_source=document['source'])
File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239, 
in run
  context, state, transitions)
File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 460, 
in check_line
  return method(match, context, next_state)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
2727, in underline
  self.section(title, source, style, lineno - 1, messages)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
328, in section
  self.new_subsection(title, lineno, messages)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
396, in new_subsection
  node=section_node, match_titles=True)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
283, in nested_parse
  node=node, match_titles=match_titles)
File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 
196, in run
  results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239, 
in run
  context, state, 

Bug#827817: Additional info

[Andreas Heinlein]

I see that there is/was a fix for Ubuntu (LP #1448548) to install the
missing .desktop file when "cautious-launcher" is available. This
obviously isn't the case for debian.

Bug#827757: [Pkg-nagios-devel] Bug#827757: apt-get upgrade doesn't want to upgrade packages in need of an upgrade

[David Kalnischkies]

On Tue, Jun 21, 2016 at 12:15:14AM +0200, Christoph Anton Mitterer wrote:
> On Mon, 2016-06-20 at 23:35 +0200, Alexander Wirt wrote:
> > On Mon, 20 Jun 2016, David Kalnischkies wrote:
> > I guess the nagios check shouldn't use 'apt-get upgrade', but that
> > > depends on what it is supposed to show (aka what its users expect)
> > > and
> > > what it actually uses (based on "critical updates" I guess it is
> > > using
> > > its own code, perhaps a binding…) but both I don't know hence
> > > reassigning.
> > I don't think so. The plugin is expected to run on all distributions
> > having
> > apt-get, apt is fairly new. 
> 
> I don't think David implied it should use apt(8), did he?

He meant that he has no idea what should be used rather than whatever is
used at the moment as he doesn't even know what that is. He isn't even
sure its a bug in nagios, but it surely isn't one in apt where he would
have closed it if the mail hadn't implied that reassign would be an
option.

That said, I am NEVER advocating to use 'apt' in scripts. The command
itself will complain about being used in scripts…


> Also @David: Or is there any other, even more Or is there any other,
> Or is there any other, even more portable/reliable/ancient-versions-
> compatible way to determine from apt how many updates (normal/security)

APT doesn't make a difference between "normal" and "security" because
there isn't really one. Updates in stable aren't 'just for fun' anyhow
and any detection based on which repository the update comes from is
bound to fail as security updates eventually end up being distributed
over non-security sources, too.

> would be available & installed (when packages would also be
> added/removed to do that - of course, I don't think check_apt should

The obvious answer is "dist-upgrade" as it is the only command which is
allowed to install new/remove packages.


But as said, I have no idea where and how information is extracted from
and what users expect to be told by it (I don't even know if the display
is in text, as graph or as a dance-performance by a group of monkeys) so
I am really not the person to be asked about that stuff.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#827807: r-cran-sn: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: r-cran-sn
Version: 1.3-0-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,

r-cran-sn fails to build from source in unstable/amd64:

  [..]

  Selecting previously unselected package liblapack3.
  Preparing to unpack .../liblapack3_3.6.0-2_amd64.deb ...
  Unpacking liblapack3 (3.6.0-2) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack .../r-base-core_3.3.0.20160615-1_amd64.deb ...
  Unpacking r-base-core (3.3.0.20160615-1) ...
  Selecting previously unselected package libgfortran-5-dev:amd64.
  Preparing to unpack .../libgfortran-5-dev_5.4.0-4_amd64.deb ...
  Unpacking libgfortran-5-dev:amd64 (5.4.0-4) ...
  Selecting previously unselected package gfortran-5.
  Preparing to unpack .../gfortran-5_5.4.0-4_amd64.deb ...
  Unpacking gfortran-5 (5.4.0-4) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../gfortran_4%3a5.3.1-3_amd64.deb ...
  Unpacking gfortran (4:5.3.1-3) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../libblas-dev_3.6.0-2_amd64.deb ...
  Unpacking libblas-dev (3.6.0-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../liblapack-dev_3.6.0-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.0-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../libtinfo-dev_6.0+20160319-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160319-1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../libncurses5-dev_6.0+20160319-1_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160319-1) ...
  Selecting previously unselected package libreadline6-dev:amd64.
  Preparing to unpack 

Bug#827808: r-cran-xml: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: r-cran-xml
Version: 3.98-1.4-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,

r-cran-xml fails to build from source in unstable/amd64:

  [..]

  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package liblapack3.
  Preparing to unpack .../liblapack3_3.6.0-2_amd64.deb ...
  Unpacking liblapack3 (3.6.0-2) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack .../r-base-core_3.3.0.20160615-1_amd64.deb ...
  Unpacking r-base-core (3.3.0.20160615-1) ...
  Selecting previously unselected package libgfortran-5-dev:amd64.
  Preparing to unpack .../libgfortran-5-dev_5.4.0-4_amd64.deb ...
  Unpacking libgfortran-5-dev:amd64 (5.4.0-4) ...
  Selecting previously unselected package gfortran-5.
  Preparing to unpack .../gfortran-5_5.4.0-4_amd64.deb ...
  Unpacking gfortran-5 (5.4.0-4) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../gfortran_4%3a5.3.1-3_amd64.deb ...
  Unpacking gfortran (4:5.3.1-3) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../libblas-dev_3.6.0-2_amd64.deb ...
  Unpacking libblas-dev (3.6.0-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../liblapack-dev_3.6.0-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.0-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../libtinfo-dev_6.0+20160319-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160319-1) ...
  Selecting previously unselected package 

Bug#827809: rgl: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: rgl
Version: 0.95.1441-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,

rgl fails to build from source in unstable/amd64:

  [..]

  Unpacking libx11-xcb-dev:amd64 (2:1.6.3-1) ...
  Selecting previously unselected package libxcb-dri3-dev:amd64.
  Preparing to unpack .../libxcb-dri3-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri3-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-render0-dev:amd64.
  Preparing to unpack .../libxcb-render0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-render0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-randr0-dev:amd64.
  Preparing to unpack .../libxcb-randr0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-randr0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-shape0-dev:amd64.
  Preparing to unpack .../libxcb-shape0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-shape0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-xfixes0-dev:amd64.
  Preparing to unpack .../libxcb-xfixes0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-xfixes0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-sync-dev:amd64.
  Preparing to unpack .../libxcb-sync-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-sync-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-present-dev:amd64.
  Preparing to unpack .../libxcb-present-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-present-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxshmfence-dev:amd64.
  Preparing to unpack .../libxshmfence-dev_1.2-1_amd64.deb ...
  Unpacking libxshmfence-dev:amd64 (1.2-1) ...
  Selecting previously unselected package libxcb-dri2-0-dev:amd64.
  Preparing to unpack .../libxcb-dri2-0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri2-0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-glx0-dev:amd64.
  Preparing to unpack .../libxcb-glx0-dev_1.11.1-1_amd64.deb ...
  Unpacking libxcb-glx0-dev:amd64 (1.11.1-1) ...
  Selecting previously unselected package x11proto-xext-dev.
  Preparing to unpack .../x11proto-xext-dev_7.3.0-1_all.deb ...
  Unpacking x11proto-xext-dev (7.3.0-1) ...
  Selecting previously unselected package x11proto-fixes-dev.
  Preparing to unpack .../x11proto-fixes-dev_1%3a5.0-2_all.deb ...
  Unpacking x11proto-fixes-dev (1:5.0-2) ...
  Selecting previously unselected package libxfixes-dev:amd64.
  Preparing to unpack .../libxfixes-dev_1%3a5.0.1-2+b2_amd64.deb ...
  Unpacking libxfixes-dev:amd64 (1:5.0.1-2+b2) ...
  Selecting previously unselected package x11proto-damage-dev.
  Preparing to unpack .../x11proto-damage-dev_1%3a1.2.1-2_all.deb ...
  Unpacking x11proto-damage-dev (1:1.2.1-2) ...
  Selecting previously unselected package libxdamage-dev:amd64.
  Preparing to unpack .../libxdamage-dev_1%3a1.1.4-2+b1_amd64.deb ...
  Unpacking libxdamage-dev:amd64 (1:1.1.4-2+b1) ...
  Selecting previously unselected package libxext-dev:amd64.
  Preparing to unpack .../libxext-dev_2%3a1.3.3-1_amd64.deb ...
  Unpacking libxext-dev:amd64 (2:1.3.3-1) ...
  Selecting previously unselected package x11proto-xf86vidmode-dev.
  Preparing to unpack .../x11proto-xf86vidmode-dev_2.3.1-2_all.deb ...
  Unpacking x11proto-xf86vidmode-dev (2.3.1-2) ...
  Selecting previously unselected package libxxf86vm-dev:amd64.
  Preparing to unpack .../libxxf86vm-dev_1%3a1.1.4-1_amd64.deb ...
  Unpacking libxxf86vm-dev:amd64 (1:1.1.4-1) ...
  Selecting previously unselected package x11proto-dri2-dev.
  Preparing to unpack .../x11proto-dri2-dev_2.8-2_all.deb ...
  Unpacking x11proto-dri2-dev (2.8-2) ...
  Selecting previously unselected package x11proto-gl-dev.
  Preparing to unpack .../x11proto-gl-dev_1.4.17-1_all.deb ...
  Unpacking x11proto-gl-dev (1.4.17-1) ...
  Selecting previously unselected package libgl1-mesa-dev:amd64.
  Preparing to unpack .../libgl1-mesa-dev_11.2.2-1_amd64.deb ...
  Unpacking libgl1-mesa-dev:amd64 (11.2.2-1) ...
  Selecting previously unselected package libglu1-mesa:amd64.
  Preparing to unpack .../libglu1-mesa_9.0.0-2.1_amd64.deb ...
  Unpacking libglu1-mesa:amd64 (9.0.0-2.1) ...
  Selecting previously unselected package libglu1-mesa-dev:amd64.
  Preparing to unpack .../libglu1-mesa-dev_9.0.0-2.1_amd64.deb ...
  Unpacking libglu1-mesa-dev:amd64 (9.0.0-2.1) ...
  Selecting previously unselected package libice-dev:amd64.
  Preparing to unpack .../libice-dev_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice-dev:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libsm-dev:amd64.
  Preparing to unpack .../libsm-dev_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm-dev:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libxt-dev:amd64.
  Preparing to unpack .../libxt-dev_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt-dev:amd64 (1:1.1.5-1) ...
  Processing 

Bug#827805: onioncircuits: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details at /usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 192.

[Chris Lamb]

Source: onioncircuits
Version: 0.4-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,

onioncircuits fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../glib-networking-common_2.48.2-1_all.deb ...
  Unpacking glib-networking-common (2.48.2-1) ...
  Selecting previously unselected package glib-networking-services.
  Preparing to unpack .../glib-networking-services_2.48.2-1_amd64.deb ...
  Unpacking glib-networking-services (2.48.2-1) ...
  Selecting previously unselected package gsettings-desktop-schemas.
  Preparing to unpack .../gsettings-desktop-schemas_3.20.0-3_all.deb ...
  Unpacking gsettings-desktop-schemas (3.20.0-3) ...
  Selecting previously unselected package glib-networking:amd64.
  Preparing to unpack .../glib-networking_2.48.2-1_amd64.deb ...
  Unpacking glib-networking:amd64 (2.48.2-1) ...
  Selecting previously unselected package libsoup2.4-1:amd64.
  Preparing to unpack .../libsoup2.4-1_2.54.1-1_amd64.deb ...
  Unpacking libsoup2.4-1:amd64 (2.54.1-1) ...
  Selecting previously unselected package libsoup-gnome2.4-1:amd64.
  Preparing to unpack .../libsoup-gnome2.4-1_2.54.1-1_amd64.deb ...
  Unpacking libsoup-gnome2.4-1:amd64 (2.54.1-1) ...
  Selecting previously unselected package librest-0.7-0:amd64.
  Preparing to unpack .../librest-0.7-0_0.8.0-1_amd64.deb ...
  Unpacking librest-0.7-0:amd64 (0.8.0-1) ...
  Selecting previously unselected package libwayland-client0:amd64.
  Preparing to unpack .../libwayland-client0_1.11.0-2_amd64.deb ...
  Unpacking libwayland-client0:amd64 (1.11.0-2) ...
  Selecting previously unselected package libwayland-cursor0:amd64.
  Preparing to unpack .../libwayland-cursor0_1.11.0-2_amd64.deb ...
  Unpacking libwayland-cursor0:amd64 (1.11.0-2) ...
  Selecting previously unselected package libdrm2:amd64.
  Preparing to unpack .../libdrm2_2.4.68-1_amd64.deb ...
  Unpacking libdrm2:amd64 (2.4.68-1) ...
  Selecting previously unselected package libwayland-server0:amd64.
  Preparing to unpack .../libwayland-server0_1.11.0-2_amd64.deb ...
  Unpacking libwayland-server0:amd64 (1.11.0-2) ...
  Selecting previously unselected package libgbm1:amd64.
  Preparing to unpack .../libgbm1_11.2.2-1_amd64.deb ...
  Unpacking libgbm1:amd64 (11.2.2-1) ...
  Selecting previously unselected package libx11-xcb1:amd64.
  Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
  Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
  Selecting previously unselected package libxcb-dri2-0:amd64.
  Preparing to unpack .../libxcb-dri2-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri2-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-dri3-0:amd64.
  Preparing to unpack .../libxcb-dri3-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri3-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-present0:amd64.
  Preparing to unpack .../libxcb-present0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-present0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-randr0:amd64.
  Preparing to unpack .../libxcb-randr0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-randr0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-shape0:amd64.
  Preparing to unpack .../libxcb-shape0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-shape0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-sync1:amd64.
  Preparing to unpack .../libxcb-sync1_1.11.1-1_amd64.deb ...
  Unpacking libxcb-sync1:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-xfixes0:amd64.
  Preparing to unpack .../libxcb-xfixes0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-xfixes0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxshmfence1:amd64.
  Preparing to unpack .../libxshmfence1_1.2-1_amd64.deb ...
  Unpacking libxshmfence1:amd64 (1.2-1) ...
  Selecting previously unselected package libegl1-mesa:amd64.
  Preparing to unpack .../libegl1-mesa_11.2.2-1_amd64.deb ...
  Unpacking libegl1-mesa:amd64 (11.2.2-1) ...
  Selecting previously unselected package libwayland-egl1-mesa:amd64.
  Preparing to unpack .../libwayland-egl1-mesa_11.2.2-1_amd64.deb ...
  Unpacking libwayland-egl1-mesa:amd64 (11.2.2-1) ...
  Selecting previously unselected package libxcomposite1:amd64.
  Preparing to unpack .../libxcomposite1_1%3a0.4.4-1_amd64.deb ...
  Unpacking libxcomposite1:amd64 (1:0.4.4-1) ...
  Selecting previously unselected package libxfixes3:amd64.
  Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
  Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
  Selecting previously unselected package libxcursor1:amd64.
  Preparing to unpack .../libxcursor1_1%3a1.1.14-1+b1_amd64.deb ...
  Unpacking libxcursor1:amd64 (1:1.1.14-1+b1) ...
  Selecting previously unselected package libxdamage1:amd64.
  Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
  Unpacking 

Bug#827812: sogo: FTBFS: Ran 13 tests FAILED (4 failures, 0 errors)

[Chris Lamb]

Source: sogo
Version: 2.2.17a-1.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,

sogo fails to build from source in unstable/amd64:

  [..]

  if [ -r "" ]; then \
plmerge SchedulerUI.SOGo/Resources/Info-gnustep.plist ; \
  fi
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160621105635.AgOHzUmkUU.sogo/sogo-2.2.17a/UI/Scheduler'
  Making all in AdministrationUI ...
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160621105635.AgOHzUmkUU.sogo/sogo-2.2.17a/UI/AdministrationUI'
  cd .; \
  /usr/share/GNUstep/Makefiles/mkinstalldirs ./obj
  Making all for bundle AdministrationUI...
  cd .; \
  /usr/share/GNUstep/Makefiles/mkinstalldirs ./obj/AdministrationUI.obj/
  /usr/share/GNUstep/Makefiles/mkinstalldirs AdministrationUI.SOGo/.
  gcc AdministrationUIProduct.m -c \
-MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DSAML2_CONFIG=1 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 
-fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
-pthread -fPIC -DDEBUG -fno-omit-frame-pointer -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I../.. -I../../.. 
-I../../SoObjects -I../../SOPE -I../../SOPE/ -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
 -o obj/AdministrationUI.obj/AdministrationUIProduct.m.o
  gcc UIxAdministration.m -c \
-MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DSAML2_CONFIG=1 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 
-fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
-pthread -fPIC -DDEBUG -fno-omit-frame-pointer -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I../.. -I../../.. 
-I../../SoObjects -I../../SOPE -I../../SOPE/ -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
 -o obj/AdministrationUI.obj/UIxAdministration.m.o
  gcc UIxAdministrationFilterPanel.m -c \
-MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DSAML2_CONFIG=1 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 
-fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
-pthread -fPIC -DDEBUG -fno-omit-frame-pointer -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I../.. -I../../.. 
-I../../SoObjects -I../../SOPE -I../../SOPE/ -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
 -o obj/AdministrationUI.obj/UIxAdministrationFilterPanel.m.o
  UIxAdministrationFilterPanel.m: In function '+[UIxAdministrationFilterPanel 
initialize]':
  UIxAdministrationFilterPanel.m:39:2: warning: #warning how useful is this? 
[-Wcpp]
   #warning how useful is this?
^
  gcc -shared  -rdynamic -Wl,--rpath,/usr/lib/sogo -Wl,-z,relro -Wl,-z,now 
-pthread  -fexceptions -o ./AdministrationUI.SOGo/./AdministrationUI 
./obj/AdministrationUI.obj/AdministrationUIProduct.m.o 
./obj/AdministrationUI.obj/UIxAdministration.m.o 
./obj/AdministrationUI.obj/UIxAdministrationFilterPanel.m.o   
-L./../../SOPE/NGCards/obj -L./../../SoObjects/SOGo/SOGo.framework/sogo/ 
-L./../SOGoUI/obj -L../../SOPE/GDLContentStore/obj/-L/usr/local/lib 
-L/usr/lib   -L/usr/local/lib -L/usr/lib -lSOGoUI -lSOGo-lgnustep-base
-lobjc   -lm
  /usr/share/GNUstep/Makefiles/mkinstalldirs AdministrationUI.SOGo/Resources
  for f in product.plist Toolbars/UIxAdministration.toolbar; do \
if [ -f .//$f -o -d .//$f ]; then \
  cp -fr .//$f ./AdministrationUI.SOGo/Resources/; \
else \
  echo "Warning: .//$f not found - ignoring"; \
fi; \
  done
  for l in Arabic BrazilianPortuguese Catalan Czech Danish Dutch English 
Finnish French German Hungarian Italian NorwegianBokmal NorwegianNynorsk Polish 
Russian Slovak SpanishSpain SpanishArgentina Swedish Ukrainian Welsh; do \
if [ -d .//$l.lproj ]; then \
  /usr/share/GNUstep/Makefiles/mkinstalldirs 
./AdministrationUI.SOGo/Resources/$l.lproj; \
  for f in Localizable.strings; do \
if [ -f .//$l.lproj/$f -o -d .//$l.lproj/$f ]; then \
  cp -fr .//$l.lproj/$f \
./AdministrationUI.SOGo/Resources/$l.lproj/; \
else \
  echo "Warning: .//$l.lproj/$f not found - ignoring"; \
fi; \
  done; \
else \
  echo "Warning: .//$l.lproj not found - ignoring"; \
fi; \
  done
  echo "OLD_GNUSTEP_STAMP_ASTRING = _AdministrationUIProduct-" > 

Bug#827813: sphinx-argparse: FTBFS: ImportError: No module named sphinx_rtd_theme

[Chris Lamb]

Source: sphinx-argparse
Version: 0.1.15-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,

sphinx-argparse fails to build from source in unstable/amd64:

  [..]

  Unpacking python3-six (1.10.0-3) ...
  Selecting previously unselected package python3-roman.
  Preparing to unpack .../python3-roman_2.0.0-2_all.deb ...
  Unpacking python3-roman (2.0.0-2) ...
  Selecting previously unselected package python3-docutils.
  Preparing to unpack .../python3-docutils_0.12+dfsg-1_all.deb ...
  Unpacking python3-docutils (0.12+dfsg-1) ...
  Selecting previously unselected package python3-pygments.
  Preparing to unpack .../python3-pygments_2.1.3+dfsg-1_all.deb ...
  Unpacking python3-pygments (2.1.3+dfsg-1) ...
  Selecting previously unselected package python3-markupsafe.
  Preparing to unpack .../python3-markupsafe_0.23-2+b2_amd64.deb ...
  Unpacking python3-markupsafe (0.23-2+b2) ...
  Selecting previously unselected package python3-jinja2.
  Preparing to unpack .../python3-jinja2_2.8-1_all.deb ...
  Unpacking python3-jinja2 (2.8-1) ...
  Selecting previously unselected package python3-tz.
  Preparing to unpack .../python3-tz_2015.7+dfsg-0.1_all.deb ...
  Unpacking python3-tz (2015.7+dfsg-0.1) ...
  Selecting previously unselected package python3-babel.
  Preparing to unpack .../python3-babel_2.3.4+dfsg.1-2_all.deb ...
  Unpacking python3-babel (2.3.4+dfsg.1-2) ...
  Selecting previously unselected package python3-alabaster.
  Preparing to unpack .../python3-alabaster_0.7.8-1_all.deb ...
  Unpacking python3-alabaster (0.7.8-1) ...
  Selecting previously unselected package python3-imagesize.
  Preparing to unpack .../python3-imagesize_0.7.1-1_all.deb ...
  Unpacking python3-imagesize (0.7.1-1) ...
  Selecting previously unselected package python3-sphinx.
  Preparing to unpack .../python3-sphinx_1.4.4-1_all.deb ...
  Unpacking python3-sphinx (1.4.4-1) ...
  Selecting previously unselected package python3-py.
  Preparing to unpack .../python3-py_1.4.31-1_all.deb ...
  Unpacking python3-py (1.4.31-1) ...
  Selecting previously unselected package python3-pytest.
  Preparing to unpack .../python3-pytest_2.9.2-1_all.deb ...
  Unpacking python3-pytest (2.9.2-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up python-all (2.7.11-2) ...
  Setting up python-setuptools (20.10.1-1) ...
  Setting up python-alabaster (0.7.8-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up python-tz (2015.7+dfsg-0.1) ...
  Setting up python-babel (2.3.4+dfsg.1-2) ...
  update-alternatives: using /usr/bin/pybabel-python2 to provide 
/usr/bin/pybabel (pybabel) in auto mode
  Setting up python-roman (2.0.0-2) ...
  Setting up sgml-base (1.28) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up python-imagesize (0.7.1-1) ...
  Setting up python-markupsafe (0.23-2+b2) ...
  Setting up python-jinja2 (2.8-1) ...
  Setting up python-pygments (2.1.3+dfsg-1) ...
  Setting up libjs-jquery (1.12.4-1) ...
  Setting up libjs-underscore (1.7.0~dfsg-1) ...
  Setting up libjs-sphinxdoc (1.4.4-1) ...
  Setting up sphinx-common (1.4.4-1) ...
  Setting up python-py (1.4.31-1) ...
  Setting up python-pytest (2.9.2-1) ...
  Setting up python3-all (3.5.1-4) ...
  Setting up python3-pkg-resources (20.10.1-1) ...
  Setting up python3-setuptools (20.10.1-1) ...
  Setting up python3-six (1.10.0-3) ...
  Setting up python3-roman (2.0.0-2) ...
  Setting up python3-pygments (2.1.3+dfsg-1) ...
  Setting up python3-markupsafe (0.23-2+b2) ...
  Setting up python3-jinja2 (2.8-1) ...
  Setting up python3-tz (2015.7+dfsg-0.1) ...
  Setting up python3-babel (2.3.4+dfsg.1-2) ...
  Setting up python3-alabaster (0.7.8-1) ...
  Setting up python3-imagesize (0.7.1-1) ...
  Setting up python3-py (1.4.31-1) ...
  Setting up python3-pytest (2.9.2-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docutils-common (0.12+dfsg-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up python3-docutils (0.12+dfsg-1) ...
  update-alternatives: using /usr/share/docutils/scripts/python3/rst-buildhtml 
to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2html to 
provide /usr/bin/rst2html (rst2html) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2latex to 
provide /usr/bin/rst2latex (rst2latex) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2man to 
provide /usr/bin/rst2man (rst2man) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2odt to 
provide /usr/bin/rst2odt (rst2odt) in auto mode
  update-alternatives: using 
/usr/share/docutils/scripts/python3/rst2odt_prepstyles to provide 
/usr/bin/rst2odt_prepstyles (rst2odt_prepstyles) in auto mode
  update-alternatives: using 

Bug#664562: Dental Industry Professionals List

[Elana Justin]

Hi,



 Hope you doing well!



 We have a Newly Updated *OPT-IN* database which will help you in
reaching *Dental
Industry Professionals* across North America, UK, Europe and Global.



* Job Titles:*



   - General Dentist/Dental Specialist
   - Dental Nurse/Dental Assistant
   - Dental Hygienist/Dental Therapist
   - Dental Technician/Dental Radiologist
   - Dental Auxiliary/Staff/Dental Student
   - Dean of Dental University / School / College
   - Dental Faculty/Staff/Dental Manufacturer
   - Hospital Director/Administrator
   - Head of Dental Association / Society / Institution
   - Trade Commissioner/Ambassador/Commercial Attaché/Councillor’s
   - Affiliated Dental Event’s Representative
   - Dental Trader (Agent / Distributor / Supplier / Dealer / Retailer /
   Wholesaler)
   - Research & Development Staff
   - Pharmacist/Dental Publisher/Press and Media



The list includes Name, Company, Title, Employee & Revenue Size, and
Industry SIC Code, Fax, Website, *Physical Address, Phone Number and
Verified E mail Address.*



 Please fill in the below details and revert back on the same email, If you
would like to add any other criteria (Which mean business to you).



 *Target Criteria:*



   - Industry you would like to reach: ___?
   - Job title: ___?
   - Location: ___?


 We can also help you in E mail and data appending solutions which can help
in holding back your lost customers.

Look forward to hear from you. Thanks!!



Warm Regards,
Elana Justin
Lead Gen (B2B Division)
Marketing Executive (B2B List)
#3240 EAST STATE STREET EXT,
HAMILTON, NEW JERSEY 08619, USA

We respect your privacy, if you want to remove from this list. Please reply
back with the subject line as “Leave Out”.

Bug#827820: firefox-esr: iceweasel -> firefox-esr upgrade - menu entrys missing cinnamon

[Florian Lohoff]

Package: firefox-esr
Version: 45.2.0esr-1~deb8u1
Severity: normal

Dear Maintainer,

after a dist-upgrade which pulled in firefox-esr replacing iceweasel
the is no menu entry - neither for iceweasel nor for firefox (-esr).

Flo

-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: user-disabled

Name: Awesome screenshot: Capture and Annotate
Location: ${PROFILE_EXTENSIONS}/jid0-gxjllfbcoax0lcltedfrekqd...@jetpack.xpi
Status: enabled

Name: BetterPrivacy
Location: ${PROFILE_EXTENSIONS}/{d40f5e7b-d2cf-4856-b441-cc613eeffbe3}.xpi
Status: app-disabled

Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Deutsch (DE) Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-de
Status: enabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: FireGestures
Location: ${PROFILE_EXTENSIONS}/firegestu...@xuldev.org.xpi
Status: enabled

Name: German Dictionary dictionary
Location: ${PROFILE_EXTENSIONS}/de...@dictionaries.addons.mozilla.org
Status: enabled

Name: Ghostery
Location: ${PROFILE_EXTENSIONS}/fire...@ghostery.com.xpi
Status: user-disabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: user-disabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled

Name: Selenium IDE
Location: ${PROFILE_EXTENSIONS}/{a6fd85ed-e919-4a43-a5af-8da18bda539f}.xpi
Status: app-disabled

Name: Selenium IDE Button
Location: ${PROFILE_EXTENSIONS}/selenium_ide_butt...@egarracingteam.com.ar.xpi
Status: user-disabled

Name: Selenium IDE: C# Formatters
Location: ${PROFILE_EXTENSIONS}/csharpformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Java Formatters
Location: ${PROFILE_EXTENSIONS}/javaformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Python Formatters
Location: ${PROFILE_EXTENSIONS}/pythonformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Ruby Formatters
Location: ${PROFILE_EXTENSIONS}/rubyformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Telify
Location: ${PROFILE_EXTENSIONS}/{6c5f349a-ddda-49ad-bdf0-326d3fe1f938}
Status: user-disabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: user-disabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled

Name: YouTube ALL HTML5
Location: ${PROFILE_EXTENSIONS}/jid1-qj0w91o64n7...@jetpack.xpi
Status: user-disabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.5.3 (1.5.3-1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: enabled

Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: disabled


-- Addons package information
ii  firefox-esr45.2.0esr-1~ amd64Mozilla Firefox web browser - Ext
ii  firefox-esr-l1 45.2.0esr-1~ all  German language package for Firef
ii  icedtea-7-plug 1.5.3-1  amd64web browser plugin based on OpenJ
ii  rhythmbox-plug 3.1-1amd64plugins for rhythmbox music playe

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

Kernel: Linux 4.5.0-0.bpo.1-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/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox-esr depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u4
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10

Bug#30126: [dpkg] can be closed?

[Lorenz Wenner]

Package: dpkg
Version: 1.17.27

--- Please enter the report below this line. ---

when i type

dpkg-divert --rename /usr/include/linux

i get

dpkg-divert: error: cannot divert directories

Use --help for help about diverting files.

so i think this is fixed. i also think this the is same as bug #33263

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: 8.5
  500 stable-updates  ftp.de.debian.org   500 stable 
security.debian.org   500 stable  packages.x2go.org   500 stable 
 ftp.de.debian.org   500 stable  dl.google.com   100 
jessie-backports ftp.de.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
apt | 1.0.9.8.3

Bug#827819: ITP: timewarrior -- command line time tracking application, which allows you to record time spent on activities

[Sebastien Badia]

Package: wnpp
Severity: wishlist
Owner: Sebastien Badia 

* Package name: timewarrior
  Version : 0.9.5
  Upstream Author : Paul Beckingham, Federico Hernandez
* URL : https://taskwarrior.org/docs/timewarrior
* License : MIT
  Programming Lang: C
  Description : command line time tracking application, which allows you to
record time spent on activities

Timewarrior is a time tracking utility that offers simple stopwatch features as
well as sophisticated calendar-base backfill, along with flexible reporting. It
is a portable, well supported and very active, Open Source project.

We currently maintain with Gordon, taskd(server) and taskd(client) from
taskwarrior,
we may maybe create a team.

Bug#827787: gcc-6: improve gcj cross build

[YunQiang Su]

On Tue, 21 Jun 2016 10:17:45 +0800 YunQiang Su  wrote:
> Package: src:gcc-6
> Version: 6.1.1-7
>
> This patch produce gre/jdk/libgcj17 from cross build,
> and it also install libgcj.spec also.
> The above makes cross gcj works better.
>
> Please review this patch.
> I am not fully confident about it.

the this is the patch applied to gcc-6-cross

>
> --
> YunQiang Su
diff --git a/debian/control.alpha.in b/debian/control.alpha.in
index 34cf03d..af53cd2 100644
--- a/debian/control.alpha.in
+++ b/debian/control.alpha.in
@@ -2504,6 +2504,54 @@ Description: GNU Java compiler
  Java on platforms supported by the gcc compiler. It uses the
  gcc backend to generate optimized code.
 
+Package: gcj-GCC_VER-jre-CROSS_GNU_TYPE
+Architecture: @host_archs@
+Priority: extra
+Section: java
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE (= ${gcc:Version}), ${dep:libcdev}, 
${shlibs:Depends}, ${misc:Depends}
+Suggests: gcj-GCC_VER-doc
+Description: GNU Java compiler
+ This is the GNU Java compiler, which compiles
+ Java on platforms supported by the gcc compiler. It uses the
+ gcc backend to generate optimized code.
+
+Package: gcj-GCC_VER-jdk-CROSS_GNU_TYPE
+Architecture: @host_archs@
+Priority: extra
+Section: java
+Depends: gcj-GCC_VER-jre-CROSS_GNU_TYPE (= ${gcc:Version}), ${dep:libcdev}, 
${shlibs:Depends}, ${misc:Depends}
+Suggests: gcj-GCC_VER-doc
+Description: GNU Java compiler
+ This is the GNU Java compiler, which compiles
+ Java on platforms supported by the gcc compiler. It uses the
+ gcc backend to generate optimized code.
+
+Package: libgcj17-CROSS_ARCH-cross
+Architecture: all
+Section: devel
+Priority: extra
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE-base (= ${gcc:Version}), ${dep:libc}, 
${shlibs:Depends}, ${misc:Depends}
+Description: Java runtime library for use with gcj
+ This is the runtime that goes along with the gcj front end to gcc.
+ libgcj includes parts of the Java Class Libraries, 
+ plus glue to connect the libraries to the compiler and the underlying OS.
+ .
+ This package contains files for CROSS_ARCH architecture, for use in 
cross-compile
+ environment.
+
+Package: libgcj17-dev-CROSS_ARCH-cross
+Architecture: all
+Section: devel
+Priority: extra
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE-base (= ${gcc:Version}), ${dep:libc}, 
${shlibs:Depends}, ${misc:Depends}
+Description: Java development headers for use with gcj
+ These are the development headers that go along with the gcj front end to gcc.
+ libgcj includes parts of the Java Class Libraries, 
+ plus glue to connect the libraries to the compiler and the underlying OS.
+ .
+ This package contains files for CROSS_ARCH architecture, for use in 
cross-compile
+ environment.
+
 Package: gdc-GCC_VER-CROSS_GNU_TYPE
 Architecture: @host_archs@
 Priority: extra
diff --git a/debian/control.arm64.in b/debian/control.arm64.in
index 34cf03d..af53cd2 100644
--- a/debian/control.arm64.in
+++ b/debian/control.arm64.in
@@ -2504,6 +2504,54 @@ Description: GNU Java compiler
  Java on platforms supported by the gcc compiler. It uses the
  gcc backend to generate optimized code.
 
+Package: gcj-GCC_VER-jre-CROSS_GNU_TYPE
+Architecture: @host_archs@
+Priority: extra
+Section: java
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE (= ${gcc:Version}), ${dep:libcdev}, 
${shlibs:Depends}, ${misc:Depends}
+Suggests: gcj-GCC_VER-doc
+Description: GNU Java compiler
+ This is the GNU Java compiler, which compiles
+ Java on platforms supported by the gcc compiler. It uses the
+ gcc backend to generate optimized code.
+
+Package: gcj-GCC_VER-jdk-CROSS_GNU_TYPE
+Architecture: @host_archs@
+Priority: extra
+Section: java
+Depends: gcj-GCC_VER-jre-CROSS_GNU_TYPE (= ${gcc:Version}), ${dep:libcdev}, 
${shlibs:Depends}, ${misc:Depends}
+Suggests: gcj-GCC_VER-doc
+Description: GNU Java compiler
+ This is the GNU Java compiler, which compiles
+ Java on platforms supported by the gcc compiler. It uses the
+ gcc backend to generate optimized code.
+
+Package: libgcj17-CROSS_ARCH-cross
+Architecture: all
+Section: devel
+Priority: extra
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE-base (= ${gcc:Version}), ${dep:libc}, 
${shlibs:Depends}, ${misc:Depends}
+Description: Java runtime library for use with gcj
+ This is the runtime that goes along with the gcj front end to gcc.
+ libgcj includes parts of the Java Class Libraries, 
+ plus glue to connect the libraries to the compiler and the underlying OS.
+ .
+ This package contains files for CROSS_ARCH architecture, for use in 
cross-compile
+ environment.
+
+Package: libgcj17-dev-CROSS_ARCH-cross
+Architecture: all
+Section: devel
+Priority: extra
+Depends: gcj-GCC_VER-CROSS_GNU_TYPE-base (= ${gcc:Version}), ${dep:libc}, 
${shlibs:Depends}, ${misc:Depends}
+Description: Java development headers for use with gcj
+ These are the development headers that go along with the gcj front end to gcc.
+ libgcj includes parts of the Java Class Libraries, 
+ plus glue to connect the libraries to the compiler and the underlying OS.
+ .
+ This package contains files for 

Bug#817550: Any news?

[Niels Thykier]

Michael Meskes:
> Any news on this? I don't like seeing my packages removed from testing
> because of this. Obviously I'd be willing to sponsor (or NMU) if
> needed.
> 
> Michael
> 

Sorry, I have not heard anything since I requested more information
about the patch from José.

Thanks,
~Niels

Bug#817385: Moving Bytecode to Debian Med (or Java) Git

[Olivier Sallou]

On 06/20/2016 09:51 PM, Andreas Tille wrote:
> On Mon, Jun 20, 2016 at 03:38:46PM +0200, Olivier Sallou wrote:
>> I made a quick fix to switch to compat 9 and fix Java version to current
>> jdk in sid.
>>
>> However, i cannot push to pkg-escience / bytecode (permission denied).
> Since pkg-escience is closed.
>  
>> It would be best to move package to pkg-java instead of debianmed
>> according to me, as it is pure Java package.
> That would be also my first idea.
>
>> Patching is quite easy:
>>
>> switch d/compat to 9 (no issue)
>>
>> d/control: update dependencies to use default-jdk and default-jre
>> instead of openjdk/sun-jdk/java2-compiler
>>
>> add a patch to build.xml to add in all javac commands :  source="1.6"
>> target="1.6"
>>
>> build is fine with no specific lintian error
> Would you volunteer to move it to pkg-java Git?
hi all,
I have moved bytecode from escience svn to pkg-java git
(ssh://git.debian.org/git/pkg-java/bytecode)
I have not pushed package yet , would need testing against package using it.
Code repo is up-to-date with fixes to close to issue, and updates to
switch to debhelper. Package builds fine and "looks" fine.

Olivier


>
> Kind regards
>
>   Andreas.
>

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#827802: glibc/mips o32: please use the default march level for mips o32

[YunQiang Su]

Package: src:glibc

Since we have removed the 2f machines from Debian officially,
and gcc-5+ also support FPXX which can help to workaround
Loongson 3A bugs.

And now we have some more UTM8 machines, which
can be used to build package ftbfs on Loongson 3A.

So it is time for us to upgrade to mips32r2.

-- 
YunQiang Su
diff --git a/debian/sysdeps/mips64el.mk b/debian/sysdeps/mips64el.mk
index d6fffbe..b80230e 100644
--- a/debian/sysdeps/mips64el.mk
+++ b/debian/sysdeps/mips64el.mk
@@ -3,16 +3,14 @@ extra_cflags = -mno-plt
 
 # main library
 libc_rtlddir = /lib64
-libc_CC = $(CC) -march=mips3 -mtune=mips64r2
-libc_CXX = $(CXX) -march=mips3 -mtune=mips64r2
 
 # build 32-bit (n32) alternative library
 GLIBC_MULTILIB_PASSES += mipsn32
 DEB_ARCH_MULTILIB_PACKAGES += libc6-mipsn32 libc6-dev-mipsn32
 libc6-mipsn32_shlib_dep = libc6-mipsn32 (>= $(shlib_dep_ver))
 mipsn32_configure_target = mips64el-linux-gnuabin32
-mipsn32_CC = $(CC) -mabi=n32 -march=mips3 -mtune=mips64r2
-mipsn32_CXX = $(CXX) -mabi=n32 -march=mips3 -mtune=mips64r2
+mipsn32_CC = $(CC) -mabi=n32
+mipsn32_CXX = $(CXX) -mabi=n32
 mipsn32_rtlddir = /lib32
 mipsn32_slibdir = /lib32
 mipsn32_libdir = /usr/lib32
diff --git a/debian/sysdeps/mipsel.mk b/debian/sysdeps/mipsel.mk
index d573d97..8571734 100644
--- a/debian/sysdeps/mipsel.mk
+++ b/debian/sysdeps/mipsel.mk
@@ -1,17 +1,13 @@
 # configuration options for all flavours
 extra_cflags = -mno-plt
 
-# main library
-libc_CC = $(CC) -march=mips2 -mtune=mips32r2
-libc_CXX = $(CXX) -march=mips2 -mtune=mips32r2
-
 # build 32-bit (n32) alternative library
 GLIBC_MULTILIB_PASSES += mipsn32
 DEB_ARCH_MULTILIB_PACKAGES += libc6-mipsn32 libc6-dev-mipsn32
 libc6-mipsn32_shlib_dep = libc6-mipsn32 (>= $(shlib_dep_ver))
 mipsn32_configure_target = mips64el-linux-gnuabin32
-mipsn32_CC = $(CC) -mabi=n32 -march=mips3 -mtune=mips64r2
-mipsn32_CXX = $(CXX) -mabi=n32 -march=mips3 -mtune=mips64r2
+mipsn32_CC = $(CC) -mabi=n32
+mipsn32_CXX = $(CXX) -mabi=n32
 mipsn32_rtlddir = /lib32
 mipsn32_slibdir = /lib32
 mipsn32_libdir = /usr/lib32
@@ -21,8 +17,8 @@ GLIBC_MULTILIB_PASSES += mips64
 DEB_ARCH_MULTILIB_PACKAGES += libc6-mips64 libc6-dev-mips64
 libc6-mips64_shlib_dep = libc6-mips64 (>= $(shlib_dep_ver))
 mips64_configure_target = mips64el-linux-gnuabi64
-mips64_CC = $(CC) -mabi=64 -march=mips3 -mtune=mips64r2
-mips64_CXX = $(CXX) -mabi=64 -march=mips3 -mtune=mips64r2
+mips64_CC = $(CC) -mabi=64
+mips64_CXX = $(CXX) -mabi=64
 mips64_rtlddir = /lib64
 mips64_slibdir = /lib64
 mips64_libdir = /usr/lib64

Bug#816097: Seeing same behaviour on fresh xenial installation

[Alexander Lampret]

I’m seeing the same behaviour, running Ubuntu Xenial in Virtualbox with OSX 
host.
pbuilder works fine with xenial amd64 but xenial armhf throws segmentation 
fault.

Unfortunately, xenial-armhf_results/*.build file does not show core dump

Best regards,
Alexander


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#110919: [dpkg] can be closed?

[Lorenz Wenner]

Package: dpkg
Version: 1.17.27

--- Please enter the report below this line. ---

i think this bug can be closed because dpkg doesn't have the 
--reconfigure option any more. i don't know since which version.



--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: 8.5
  500 stable-updates  ftp.de.debian.org   500 stable 
security.debian.org   500 stable  packages.x2go.org   500 stable 
 ftp.de.debian.org   500 stable  dl.google.com   100 
jessie-backports ftp.de.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
apt | 1.0.9.8.3

Bug#827818: mirror submission for alcateia.ufscar.br

[Depto de Infraestrutura e Servicos de TI]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: alcateia.ufscar.br
Aliases: mirror.ufscar.br
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x 
Archive-http: /debian/
IPv6: no
Archive-upstream: ftp.br.debian.org
Updates: four
Maintainer: Depto de Infraestrutura e Servicos de TI 
Country: BR Brazil
Sponsor: UFSCar - Federal University of Sao Carlos http://www.ufscar.br

Bug#827802: glibc/mips o32: please use the default march level for mips o32

[YunQiang Su]

On Tue, 21 Jun 2016 17:23:34 +0800 YunQiang Su  wrote:
> Package: src:glibc
>
> Since we have removed the 2f machines from Debian officially,
> and gcc-5+ also support FPXX which can help to workaround
> Loongson 3A bugs.
>
> And now we have some more UTM8 machines, which
> can be used to build package ftbfs on Loongson 3A.
>
> So it is time for us to upgrade to mips32r2.

Sorry, the previous attached patch have something mistake.
This patch also effects mips64el.

>
> --
> YunQiang Su
diff --git a/debian/rules2 b/debian/rules2
index 0f3eddc..4753af2 100644
--- a/debian/rules2
+++ b/debian/rules2
@@ -633,11 +633,11 @@ ifneq (,$(findstring mips-linux,$(DEB_TARGET_GNU_TYPE)))
 endif
 
 ifneq (,$(findstring mipsel-linux,$(DEB_TARGET_GNU_TYPE)))
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32r2 --with-fp-32=xx
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch64),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64r2
+  CONFARGS += --with-arch-64=mips64r2
 endif
   endif
 endif
@@ -647,8 +647,8 @@ ifneq (,$(findstring 
mips64el-linux-gnuabin32,$(DEB_TARGET_GNU_TYPE)))
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch32),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32 --with-fp-32=xx
+  CONFARGS += --with-arch-64=mips64r2
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
 endif
   endif
 endif
@@ -657,8 +657,8 @@ ifneq (,$(findstring 
mips64-linux-gnuabin32,$(DEB_TARGET_GNU_TYPE)))
   ifeq ($(multilib),yes)
 ifeq ($(biarchn32)-$(biarch32),yes-yes)
   CONFARGS += --enable-targets=all
-  CONFARGS += --with-arch-64=mips3 --with-tune-64=mips64
-  CONFARGS += --with-arch-32=mips2 --with-tune-32=mips32 --with-fp-32=xx
+  CONFARGS += --with-arch-64=mips64r2
+  CONFARGS += --with-arch-32=mips32r2 --with-fp-32=xx
 endif
   endif
 endif

Bug#825015:

[Sam Morris]

On Tue, 2016-06-21 at 00:51 -0400, Dr Wanderlust wrote:
> Unfortunately, this bug still persists after updating to vim-command-
> t 4.0-1.
> 
> command-t.vim could not load the C extension 
> Please see INSTALLATION and TROUBLE-SHOOTING in the help
> Vim Ruby version: 2.3.1-p112
> Expected version: 2.3.0-p0
> 
> Would you consider reopening this bug-report?

Can you please check which versions of the following packages you have
installed?

vim-athena, vim-gnome, vim-gtk, vim-gtk3, vim-nox

-- 

Sam Morris 
CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

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

Bug#826749: RE: clang: enable FPXX for o32 by default

[Pablo Oliveira]

Dear all,

Thanks for clarifying the issue. Having support for a configure-time
option would be great. In the meantime I have applied YunQiang Su's
patch on 3.7/3.8 and snapshot in the package svn,

  [ YunQiang Su ]
  * Enable FPXX by default on mips/mipsel (Closes: #826749)

Thanks !

Pablo


On Mon, 13 Jun 2016 16:34:42 + Daniel Sanders
 wrote:
> > -Original Message-
> > From: Matthew Fortune
> > Sent: 13 June 2016 16:55
> > To: YunQiang Su; Pablo Oliveira
> > Cc: 826...@bugs.debian.org; Sylvestre Ledru; Daniel Sanders
> > Subject: RE: clang: enable FPXX for o32 by default
> > 
> > YunQiang Su  writes:
> > > On Fri, Jun 10, 2016 at 12:10 AM, Pablo Oliveira 
> > > wrote:
> > > > Dear YunQiang Su,
> > > >
> > > > On Wed, 8 Jun 2016 23:49:17 +0800 YunQiang Su 
> > > wrote:
> > > >> Package: src:llvm-toolchain-snapshot
> > > >>
> > > >> We are working on moving all packages mips/mipsel built with
> > > >> fpxx-enabled by default.
> > > >>
> > > >> While, now fpxx is not enabled by default in clang.
> > > >> So please apply the attached patch to 3.5/3.6/3.7/3.8/snapshot.
> > > >>
> > > >> About FPXX and the transaction, please see:
> > > >>
> > > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825342
> > > >
> > > > Are you sure it is ok to modify the default behavior of FPXXDefault
> > > > only for Debian clang packages (this could lead to surprise and hard
> > > > to track bugs for users) ?
> > >
> > > The clang guy in IMG told me that this the only way currently.
> > >
> > > >
> > > > To me it makes more sense to:
> > > >
> > > > 1) either submit this patch upstream, so that every clang distribution
> > > > has the same common behavior regarding FPXX
> > >
> > > I also prefer this way.
> > 
> > We cannot do this as the topic we are discussing here is inherently a
> > decision for distributions and not upstream. Please note the setting for
> > this in GCC is a build time setting so upstream GCC does not set FPXX
> > by default. Fedora or other distros can choose different compatibility
> > levels that suit their user base and hence may not use FPXX.
> > 
> > There is a longer term plan to get a build time configuration option into
> > CLANG/LLVM but this will take time to plan and implement. When ready
> > you can switch to it but there is no ETA.
> 
> My plan on this is a bit of a compromise between these two positions so I 
> think I
> should elaborate a little. I aim to collect all the distribution specific 
> behaviours
> upstream and have each distribution use a configure-time option to pick 
> between
> them. This allows people to cross compile to specific distributions and should
> help limit any confusion caused by the configure-time option.
> 
> One possible way of going about this is to have a mips-debian-linux-gnu 
> triple in
> upstream clang that has all the Debian-specific behaviours and have Debian 
> use a
> configure-time option to map mips-linux-gnu to mips-debian-linux-gnu.
> 

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

[Roger Shimizu]

Control: retitle -1 RFS: libcorkipset/1.1.1+20150311-1 [ITP] -- C
library to store sets/maps of IP address

Dear G,

I think you didn't review since you did last time, and I did some
changes based on some changes in previous post, so here I *rewrite*
the previous post.

On Mon, Jun 20, 2016 at 10:03 PM, Gianfranco Costamagna
 wrote:
> control: owner -1 !
> control: tags -1 moreinfo
>
> Hi, lets see
>
> 1) control: why the -dev package is not multiarch?
> sounds like it is multiarch ready to me
> (I didn't check but include/* seems to have the same md5sum on different archs

Yes, it's multi-arch, just forgot to mark it in d/control.
Fixed.

> 2) the dev package should suggest the doc one

Fixed.

> 3) d/p/0002-fix-build-with-static-libcheck-library.patch
>
> I can't complain here, I seem to know the author of that patch :p

Thanks for your great help!
This convinced me that this library can be packaged, too.

> 3) d/p/0004-remove-test-of-python-cram.patch
>
> why? python-cram is available on Debian

Yes, I used python3-cram in libcork, but this time it just doesn't work.
Without my patch, python-cram just report "no test" error.
I guess upstream didn't finish the test case of cram.
So I removed it.

> 4) d/p/0007-*
> why? please be more verbose on patches, otherwise I find difficult to 
> understand why you are using sphinx instead
> of pandoc to build documentation

upstream's docs/CMakeLists.txt just output nothing.
You can see "set(MAN_PAGES)", the target is empty!

So I used the same way in libcork to generate docs.
Actually the upstream was during the transition from sphinx to pandoc.
They removed sphinx setting, added pandoc setting, but didn't remove
sphinx docs.
So I patched back sphinx setting, just works.

(docs from upstream just poor, even I wrote a patch to add index page)

> 5) rules:
> I don't like hacks
> and your sed makes the package non-rebuildable.
>
> maybe overriding the
>
> dh_install target, and acting under debian/libfoo-dev/usr/include
>
> is a "better" way (also, a mv instead of ln -s since this old directory 
> should go away)

After reading your comment for three time, now I understand it.
I put it under dh_install as you recommend.
Now it's rebuildable.

> --buildsystem=cmake --builddirectory=build should be useless

I removed "--buildsystem=cmake"
Thanks for your suggestion!

Without "--builddirectory=build", the docs will be built under
/docs/
This make install file hard to write.
So here I keep as it was.

> also
> DPKG_EXPORT_BUILDFLAGS = 1
> include /usr/share/dpkg/buildflags.mk

Removed.
Thanks for your suggestion!

> 6) did you forward the rename to upstream?

Since the most authors quit redjack, and they're almost not active,
I consider it should be called libcorkipset.

> 7) libredjackipset-docs.docs
> is it useful? there is no package with that name, so probably the file can be 
> removed

Fixed.

> 8) I'm not a fan of dh-exec, and your patch about multiarch seems incomplete
>
> +include(GNUInstallDirs)
>
> this has to be done *before*
>
> "set(CMAKE_INSTALL_LIBDIR lib${LIB_SUFFIX} CACHE STRING"
> note the LIB_SUFFIX
>
> and then the install files can change from
> usr/lib/lib*.so usr/lib/${DEB_HOST_MULTIARCH}
> to
> usr/lib/*/*.so
> and similar for others

Yes, moving "include(GNUInstallDirs)" makes dh-exec useless.
My mistake forced me to introduced this complex. Sorry about that.

> 9)
>
> did you try compat level 10?
> it should speed up the build by running dh --parallel :)
> (you can also experiment with --parallel on the default dh call in rules file)

Tried, just added a lintian warning.
Should be fixed when debhelper 10 released.
So I keep as it is.

Thanks again!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Bug#827473: ostree: FTBFS on mipsel: "ostree pull" sometimes gets SIGBUS, SIGSEGV

[Simon McVittie]

On Thu, 16 Jun 2016 at 12:06:12 -0400, Simon McVittie wrote:
> I'm trying to reproduce this failure on the porterbox etler.debian.org
> by rebuilding the package or by using the installed-tests from 2016.5-3.

I can reproduce it eventually, but the gdb report is unhelpful. Is there
anything special that I'd need to do to get a useful backtrace on mipsel?

(gdb) thread apply all bt full

Thread 3 (LWP 4232):
#0  0x775b697c in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (LWP 4215):
#0  0xec60 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (LWP 4231):
#0  0x777d151c in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

To reproduce:

* build ostree (I used 2016.5-4)
* while TEST_SKIP_CLEANUP=1 make check-TESTS 
TESTS=tests/test-pull-archive-z.sh; do :; done
  (and let it run for a while until it fails)
* look for a line like "Skipping cleanup of /var/tmp/tap-test.7eaT36" in
  test-suite.log
* ./libtool --mode=execute gdb ostree /var/tmp/tap-test.7eaT36/core

I'm going to try with valgrind, and if I can't get anything useful out of
that, either ignore the test failure on mipsel, or ask for the 2016.5-3
binaries to be removed so they don't block ostree migrating to testing
on other architectures.

S

Bug#827816: reprepro: add mail-changes.example to notify when (at least) 'accepted' packages

[Luca Capello]

Package: reprepro
Version: 4.16.0-1
Severity: wishlist
User: luca.cape...@infomaniak.com
Usertags: infomaniak.com-packaging

Hello,

as the title suggests, I would like to have a way to get an email
every time a .changes file is processed, similar to what happens for the
official Debian archive:

  

Tested patch for ACTION=3Daccepted (thus to be extended later on) as soon
as this bug get a number :-)

Thx, bye,
Gismo / Luca

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

Kernel: Linux 3.18.30-imu (SMP w/1 CPU core)
Locale: LANG=3DC, LC_CTYPE=3DC (charmap=3DANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages reprepro depends on:
ii  libarchive13 3.1.2-11+deb8u1
ii  libbz2-1.0   1.0.6-7+b3
ii  libc62.19-18+deb8u4
ii  libdb5.3 5.3.28-9
ii  libgpg-error01.17-3
ii  libgpgme11   1.5.1-6
ii  liblzma5 5.1.1alpha+20120614-2+b3
ii  pinentry-curses  0.8.3-2
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages reprepro recommends:
ii  apt  1.0.9.8.3

Versions of packages reprepro suggests:
ii  gnupg-agent  2.0.26-6
pn  inoticoming  
pn  lzip 

-- no debconf information

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA


signature.asc
Description: Digital signature

Bug#827487: bytes-circle_2.2-1_amd64.changes REJECTED

[Adam Borowski]

On Tue, Jun 21, 2016 at 09:38:46AM +0200, Roberto S. Galende wrote:
> Hi Adam,
> It appears as just amd64, when it's marked "any", but I don't know if it'll
> be compiled for other architectures or I'm just too impatient :-)

It will, you can watch the current progress, failures and logs at:
https://buildd.debian.org/status/package.php?p=bytes-circle=unstable

Debian is currently moving towards source-only uploads, but at the moment
binaries of at least one architecture are still required for NEW packages. 
This is bad, as I could have snuck some nefarious code through, be it
accidentally (like, via having an experimental or out-of-Debian compiler or
a library installed) or to subvert security.  Sure, it is possible to sneak
something nasty in the source (the Underhanded C Contest has some nice ideas
how, even in face of thorough review) but it's MASSIVELY easier to do it
undetected by uploading a binary that doesn't correspond to the source. 
Thus, you have no assurance bytes-circle:amd64 is untainted.

Any subsequent uploads can be source-only.


Meow!
-- 
An imaginary friend squared is a real enemy.

Bug#60528: [dpkg] can be closed

[Lorenz Wenner]

Package: dpkg
Version: 1.17.27

--- Please enter the report below this line. ---

dpkg -l

lists only installed packages. i did not find out that you would have to 
do to get a list of all available packages.


--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: 8.5
  500 stable-updates  ftp.de.debian.org   500 stable 
security.debian.org   500 stable  packages.x2go.org   500 stable 
 ftp.de.debian.org   500 stable  dl.google.com   100 
jessie-backports ftp.de.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
apt | 1.0.9.8.3

Bug#827805: [Pkg-privacy-maintainers] Bug#827805: onioncircuits: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details at /usr/share/perl5/Debian/Debhelper/B

[Sascha Steinbiss]

I already noticed this and will look at it later today.

Cheers
Sascha

On 21/06/2016 10:59, Chris Lamb wrote:
> Source: onioncircuits
> Version: 0.4-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,
> 
> onioncircuits fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   Preparing to unpack .../glib-networking-common_2.48.2-1_all.deb ...
>   Unpacking glib-networking-common (2.48.2-1) ...
>   Selecting previously unselected package glib-networking-services.
>   Preparing to unpack .../glib-networking-services_2.48.2-1_amd64.deb ...
>   Unpacking glib-networking-services (2.48.2-1) ...
>   Selecting previously unselected package gsettings-desktop-schemas.
>   Preparing to unpack .../gsettings-desktop-schemas_3.20.0-3_all.deb ...
>   Unpacking gsettings-desktop-schemas (3.20.0-3) ...
>   Selecting previously unselected package glib-networking:amd64.
>   Preparing to unpack .../glib-networking_2.48.2-1_amd64.deb ...
>   Unpacking glib-networking:amd64 (2.48.2-1) ...
>   Selecting previously unselected package libsoup2.4-1:amd64.
>   Preparing to unpack .../libsoup2.4-1_2.54.1-1_amd64.deb ...
>   Unpacking libsoup2.4-1:amd64 (2.54.1-1) ...
>   Selecting previously unselected package libsoup-gnome2.4-1:amd64.
>   Preparing to unpack .../libsoup-gnome2.4-1_2.54.1-1_amd64.deb ...
>   Unpacking libsoup-gnome2.4-1:amd64 (2.54.1-1) ...
>   Selecting previously unselected package librest-0.7-0:amd64.
>   Preparing to unpack .../librest-0.7-0_0.8.0-1_amd64.deb ...
>   Unpacking librest-0.7-0:amd64 (0.8.0-1) ...
>   Selecting previously unselected package libwayland-client0:amd64.
>   Preparing to unpack .../libwayland-client0_1.11.0-2_amd64.deb ...
>   Unpacking libwayland-client0:amd64 (1.11.0-2) ...
>   Selecting previously unselected package libwayland-cursor0:amd64.
>   Preparing to unpack .../libwayland-cursor0_1.11.0-2_amd64.deb ...
>   Unpacking libwayland-cursor0:amd64 (1.11.0-2) ...
>   Selecting previously unselected package libdrm2:amd64.
>   Preparing to unpack .../libdrm2_2.4.68-1_amd64.deb ...
>   Unpacking libdrm2:amd64 (2.4.68-1) ...
>   Selecting previously unselected package libwayland-server0:amd64.
>   Preparing to unpack .../libwayland-server0_1.11.0-2_amd64.deb ...
>   Unpacking libwayland-server0:amd64 (1.11.0-2) ...
>   Selecting previously unselected package libgbm1:amd64.
>   Preparing to unpack .../libgbm1_11.2.2-1_amd64.deb ...
>   Unpacking libgbm1:amd64 (11.2.2-1) ...
>   Selecting previously unselected package libx11-xcb1:amd64.
>   Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
>   Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
>   Selecting previously unselected package libxcb-dri2-0:amd64.
>   Preparing to unpack .../libxcb-dri2-0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-dri2-0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-dri3-0:amd64.
>   Preparing to unpack .../libxcb-dri3-0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-dri3-0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-present0:amd64.
>   Preparing to unpack .../libxcb-present0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-present0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-randr0:amd64.
>   Preparing to unpack .../libxcb-randr0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-randr0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-shape0:amd64.
>   Preparing to unpack .../libxcb-shape0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-shape0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-sync1:amd64.
>   Preparing to unpack .../libxcb-sync1_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-sync1:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxcb-xfixes0:amd64.
>   Preparing to unpack .../libxcb-xfixes0_1.11.1-1_amd64.deb ...
>   Unpacking libxcb-xfixes0:amd64 (1.11.1-1) ...
>   Selecting previously unselected package libxshmfence1:amd64.
>   Preparing to unpack .../libxshmfence1_1.2-1_amd64.deb ...
>   Unpacking libxshmfence1:amd64 (1.2-1) ...
>   Selecting previously unselected package libegl1-mesa:amd64.
>   Preparing to unpack .../libegl1-mesa_11.2.2-1_amd64.deb ...
>   Unpacking libegl1-mesa:amd64 (11.2.2-1) ...
>   Selecting previously unselected package libwayland-egl1-mesa:amd64.
>   Preparing to unpack .../libwayland-egl1-mesa_11.2.2-1_amd64.deb ...
>   Unpacking libwayland-egl1-mesa:amd64 (11.2.2-1) ...
>   Selecting previously unselected package libxcomposite1:amd64.
>   Preparing to unpack .../libxcomposite1_1%3a0.4.4-1_amd64.deb ...
>   Unpacking libxcomposite1:amd64 (1:0.4.4-1) ...
>   Selecting previously unselected package libxfixes3:amd64.
>   Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
>   Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
>   Selecting previously unselected 

Bug#817550: Any news?

[Michael Meskes]

Any news on this? I don't like seeing my packages removed from testing
because of this. Obviously I'd be willing to sponsor (or NMU) if
needed.

Michael
-- 

Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#827879: dgit should perhaps override dput config run_lintian

[Sean Whitton]

Package: dgit
Version: 1.4
Severity: wishlist

If the user has run-lintian=1 in their ~/.dput.cf, a dgit push could
fail if Lintian exits non-zero.  This is more likely if the user has
configured lintian to exit non-zero on warnings as well as errors.  Note
that this failure would occur after pushing to the dgit repos, so the
user would have to do some fixing up.

Perhaps dgit should override this dput configuration option, or refuse
to push if it is present, or run lintian itself before pushing to
dgit-repos if the option is present (dput's -o option might be of use).

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

Kernel: Linux 4.6.0-1-686-pae (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 dgit depends on:
ii  ca-certificates   20160104
ii  coreutils 8.25-2
ii  curl  7.47.0-1
ii  devscripts2.16.5
ii  dpkg-dev  1.18.7
ii  dput  0.9.6.4
ii  git [git-core]1:2.8.1-1
ii  libdpkg-perl  1.18.7
ii  libjson-perl  2.90-1
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-1
ii  libwww-perl   6.15-1
ii  perl  5.22.2-1

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.2p2-5

Versions of packages dgit suggests:
ii  sbuild  0.69.0-2

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#827875: RFP: python-bugzilla -- Python library and command line tool for interacting with Bugzilla

[Sergio Durigan Junior]

Control: retitle -1 ITP: python-bugzilla -- Python library and command line 
tool for interacting with Bugzilla
Control: owner -1 !

On Tuesday, June 21 2016, Iain R. Learmonth wrote:

> * Package name: python-bugzilla
>   Version : 1.2.2
>   Upstream Author : Cole Robinson
> * URL : https://github.com/python-bugzilla/python-bugzilla
> * License : GPL-2
>   Programming Lang: Python
>   Description : Python library and command line tool for interacting with 
> Bugzilla
>
> This package provides two features, a 'bugzilla' python module for
> talking to a Bugzilla instance over XMLRPC and /usr/bin/bugzilla command
> line tool for performing actions from the command line: create or edit
> bugs, various queries, etc.
>
> Releases are available at: https://pypi.python.org/pypi/python-bugzilla/1.2.2

I'll give this a try.  Probably should have something by the weekend.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#827880: devscripts: [debrelease] [debsign] DEBRELEASE_DEBS_DIR ignored while --debs-dir works

[Carl Suster]

Package: devscripts
Version: 2.16.5
Severity: normal

Dear Maintainer,

Both debrelease and debsign claim in their documentation that the environment
variable DEBRELEASE_DEBS_DIR is equivalent to setting the command line option
--debs-dir, however both scripts seem to ignore the env variable.

$ DEBRELEASE_DEBS_DIR=../build-area debsign -S
debsign: Can't find or can't read changes file !
$ debsign --debs-dir=../build-area -S


$ DEBRELEASE_DEBS_DIR=../build-area debrelease -S mentors
debrelease: could not find/read changes file ../_source.changes!
$ debrelease --debs-dir=../build-area -S mentors


As an aside I note that the two scripts report the same error with different
text, and that the message given by debrelease is more helpful in that it
includes the exact filename it's looking for.

Cheers,
Carl


-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBRELEASE_UPLOADER="dput"

-- 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.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.7
ii  libc62.22-12
ii  perl 5.22.2-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  apt 1.2.13
ii  at  3.1.18-2
ii  curl7.47.0-1
ii  dctrl-tools 2.24-2
ii  debian-keyring  2016.06.19
ii  dput0.9.6.4
ii  equivs  2.0.9+nmu1
ii  fakeroot1.20.2-2
ii  file1:5.25-2
ii  gnupg   1.4.20-6
ii  gnupg2  2.1.11-7
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.05-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.19-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  lintian 2.5.45
ii  man-db  2.7.5-1
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
ii  python3-debian  0.1.28
ii  python3-magic   1:5.25-2
ii  sensible-utils  0.0.9
ii  strace  4.12-3
ii  unzip   6.0-20
ii  wdiff   1.2.2-1+b1
ii  wget1.18-1
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-3
ii  build-essential  12.2
pn  cvs-buildpackage 
pn  devscripts-el
pn  diffoscope   
pn  dose-extra   
pn  gnuplot  
ii  gpgv 1.4.20-6
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.22-1
ii  libnet-smtp-ssl-perl 1.03-1
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mozilla-devscripts   
ii  mutt 1.6.0-1
ii  openssh-client [ssh-client]  1:7.2p2-5
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-28

-- no debconf information

Bug#827700: RFS: cplay/1.50-1 [NMU]

[Sean Whitton]

control: tag -1 +moreinfo

Dear David,

Thanks for working to fix up this package.

On Sun, Jun 19, 2016 at 09:41:02PM +0100, David Jones wrote:
>  * New upstream release (Closes: #279000, #375060, #413738)
>  * Converted to quilt (3.0) (Closes: #664311)
>  * Updated standards version to 3.9.8
>  * Updated menu file
>  * Updated watch file (Closes: #449776, #691239)
>  * Converted copyright to DEP-5

The changes I have quoted above are not usually appropriate for NMUs.
In particular, changing from a version 1.0 to a 3.0 source package could
annoy the current package maintainers a great deal.

In this case, it looks like those package maintainers are inactive (no
uploads since 2005).  You should contact the MIA team to have the
package orphaned.  Then you can either adopt the package, or make your
changes as a QA upload.

Tagging bug as moreinfo in case there is something about the NMU policy
I'm misunderstanding, so David can offer a justification.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#748014: clementine: Nothing shows in the song/artist information panel.

[Carl Suster]

Package: clementine
Version: 1.3~rc1-1+b1
Followup-For: Bug #748014

For me the info panels are also blank when I am connected to particular
networks. There is issue 1483 [1] claiming that this should no longer be an
issue under proxies, but on my university network with no proxy I'm still
seeing this.

I would suggest that it could be something network related, but I also might be
seeing a distinct issue.

[1] https://github.com/clementine-player/Clementine/issues/1483

Bug#827843: ITP: xlogo -- XLogo is an interpreter for the Logo programming language, written in Java.

[Josh Triplett]

On Tue, 21 Jun 2016 18:18:09 +0200 Wolf Bergenheim  wrote:
> * Package name: xlogo

Note that x11-apps ships /usr/bin/xlogo (a tiny toy app that displays
the X Window System logo), so you'll want to avoid a binary name
conflict.

Bug#783044: ITP: busted -- Lua unit testing framework focused on ease of use

[James McCoy]

On Tue, Jun 21, 2016 at 09:58:34PM +0100, Phil Morrell wrote:
> Is there any news on this? I note neovim has been packaged anyway and
> that the last of the reported blocking bugs was marked done on
> 2016-01-01.

The current state of the packaging is in collab-maint.  I intend to
review it in the next couple days and, if things look good, upload it.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#827843: ITP: xlogo -- XLogo is an interpreter for the Logo programming language, written in Java.

[Adam Borowski]

On Tue, Jun 21, 2016 at 06:18:09PM +0200, Wolf Bergenheim wrote:
> * Package name: xlogo
> * URL : http://xlogo.tuxfamily.org
>   Description : XLogo is an interpreter for the Logo programming 
> language, written in Java.

This name conflicts with existing "xlogo", the thingy people use mostly to
check whether their X forwarding works.

-- 
An imaginary friend squared is a real enemy.

Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings

[Carl Suster]

Has there been any progress on this?

Getting this package into the archive is blocking the upgrade of beets
(#775719) which is by now lagging far behind upstream, so it would be nice to
have this obstacle out of the way.

Since python3-jellyfish from the DNA package has been in the archive for a
little while, it seems like it would be a bad idea to use that name and hence
the only real option is to differ from upstream here. Maybe
python*-jellyfish-strings (or -matching)?

Cheers,
Carl

Bug#798864: version 5.2 is out now

[Bdale Garbee]

Upstream is now at version 5.2.

Bdale

Bug#827017: thanks

[Bdale Garbee]

Thanks for pointing this out.  It will take a bit of work to implement, since
the way I split the tar upstream source to create the tar and non-free tar-doc
packages will need to be updated.  But I agree using upstream's man pages is
a worthwhile change, and they do not appear to have license issues, so I'll
work on this soon.

Bdale

Bug#827700: RFS: cplay/1.50-1 [NMU]

[David Jones]

My apologies, I am still getting my head around everything. It had occurred
to me not long after I uploaded but I thought it was worth a shot. I shall
get in touch with the MIA team and make it a QA upload, assuming #817410
hasn't resulted in it being removed from the archive by then

On 22 June 2016 at 03:22, Sean Whitton  wrote:

> control: tag -1 +moreinfo
>
> Dear David,
>
> Thanks for working to fix up this package.
>
> On Sun, Jun 19, 2016 at 09:41:02PM +0100, David Jones wrote:
> >  * New upstream release (Closes: #279000, #375060, #413738)
> >  * Converted to quilt (3.0) (Closes: #664311)
> >  * Updated standards version to 3.9.8
> >  * Updated menu file
> >  * Updated watch file (Closes: #449776, #691239)
> >  * Converted copyright to DEP-5
>
> The changes I have quoted above are not usually appropriate for NMUs.
> In particular, changing from a version 1.0 to a 3.0 source package could
> annoy the current package maintainers a great deal.
>
> In this case, it looks like those package maintainers are inactive (no
> uploads since 2005).  You should contact the MIA team to have the
> package orphaned.  Then you can either adopt the package, or make your
> changes as a QA upload.
>
> Tagging bug as moreinfo in case there is something about the NMU policy
> I'm misunderstanding, so David can offer a justification.
>
> --
> Sean Whitton
>

Bug#826004: Update arcmsr to include support for newer controller types (ARC1203)

[黃清隆]

Hi there,

I am the developer of Areca Raid controller device driver, arcmsr.
I have reviewed the source code of after patched this backport to arcmsr
for Debian Jessie.
I also have test the binary code of patched arcmsr driver.
It works very well for all Areca Raid controllers.
This patch is awesome. Thanks for Salvatore's effort.

Regards,
Ching

Bug#827705: (no subject)

[inkbottle]

When I did look at sysvinit-utils from Aptitude GUI, the problem was obvious, 
there was a deadlock, and of course the installation would not be possible.
However this is what happened:

# aptitude -t stretch install sysvinit-utils
The following packages will be upgraded: 
  initscripts sysvinit-utils 
2 packages upgraded, 0 newly installed, 0 to remove and 370 not upgraded.
Need to get 0 B/151 kB of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y
Retrieving bug reports... Done   
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 190131 files and directories currently installed.)
Preparing to unpack .../initscripts_2.88dsf-59.6_amd64.deb ...
Unpacking initscripts (2.88dsf-59.6) over (2.88dsf-59.4) ...
Preparing to unpack .../sysvinit-utils_2.88dsf-59.6_amd64.deb ...
Unpacking sysvinit-utils (2.88dsf-59.6) over (2.88dsf-59.4) ...
Processing triggers for systemd (230-1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up sysvinit-utils (2.88dsf-59.6) ...
Setting up initscripts (2.88dsf-59.6) ...
 
Current status: 370 (-2) upgradable.

So, nothing special happened: the dreaded bug didn't show.
I did the rest of the upgrade, and rebooted before sending this mail, to be 
sure... no problem arose.

Chris

Bug#827844: git: man git: dead link

[Jonathan Nieder]

tags 827844 + upstream patch
forwarded 827844 http://mid.gmane.org/20160622024151.ga20...@google.com
quit

Andrea Stacchiotti wrote:

> In the git manual (`man git`), the documentation link:
>> http://git-htmldocs.googlecode.com/git/git.html
> is broken.

Thanks for reporting.  Let's take this upstream.

Bug#827517: [Pkg-mozext-maintainers] Bug#827517: xul-ext-ublock-origin: Missing icons in uBlock's popup UI

[Sean Whitton]

Hello,

On Tue, Jun 21, 2016 at 12:08:55AM +0200, Hartmut Buhrmester wrote:
> I also noticed, that the icons from the extension uBlock Origin are missing,
> if the Debian version of the extension is installed, and I like to offer
> another explanation:
> 
> When searching for instances of the Font Awesome, I found a symbolic link in
> the extension uBlock itself:
> 
> /usr/share/xul-ext/ublock-origin/css/fonts/fontawesome-webfont.ttf
> 
> The symbolic link uses a double redirection to finally point to the real
> font file at:
> 
> /usr/share/fonts/truetype/font-awesome/fontawesome-webfont.ttf
> 
> Now it seems, that the extension simply doesn't resolve that symbolic link.
> I deleted the symbolic link and replaced it with the original font file, and
> then everything worked fine!

Thanks for performing that investigation.  I don't find any mention of
symlinks in the upstream bug report,[1] but I guess it's a side-effect
of the fix.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1245811

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#826027: Error: "This program requires Python requests 2.2.0 or later.". But I have requests 2.10.0-1.

[Nigel Horne]

Package: linkchecker
Version: 9.3-1.1
Followup-For: Bug #826027

The same thing with an earlier version of Python:

$ linkchecker index.html 
This program requires Python requests 2.2.0 or later.
$ python --version
Python 2.7.12rc1
$ dpkg -l linkchecker
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  linkchecker9.3-1.1  amd64check websites and HTML documents


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

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

Versions of packages linkchecker depends on:
ii  libc62.22-11
ii  python   2.7.11-2
ii  python-requests  2.10.0-1

linkchecker recommends no packages.

Versions of packages linkchecker suggests:
pn  clamav-daemon   
ii  linkchecker-gui 9.3-1.1
ii  linkchecker-web 9.3-1.1
ii  python-argcomplete  1.0.0-1
ii  python-cssutils 1.0-4.1
ii  python-gconf2.28.1+dfsg-1.1
ii  python-geoip1.3.2-1+b2
ii  python-meliae   0.4.0+bzr199-1
ii  python-twill0.9-3

-- no debconf information

Bug#827783: qtwebkit-opensource-src: FTBFS on sparc64 due to mismatched symbols file

[John David Anglin]

Source: qtwebkit-opensource-src
Version: 5.6.1+dfsg-3
Followup-For: Bug #827783

Likewise on hppa.  See:
https://buildd.debian.org/status/fetch.php?pkg=qtwebkit-opensource-src=hppa=5.6.1%2Bdfsg-3=1466535251

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

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

Bug#797959: likwid: FTBFS: unconditional amd64 assembly

[Aaron M. Ucko]

found 797959 4.1.0+dfsg1-1
notfixed 797959 4.1.0+dfsg1-1
thanks

"Aaron M. Ucko"  writes:

> Builds of likwid for non-amd64 processors (even i386) fail due to the
> unconditional use of amd64 assembly, as detailed at

This is still a problem on i386, per
https://buildd.debian.org/status/fetch.php?pkg=likwid=i386=4.1.0%2Bdfsg1-1=1466549869

  ===>  ASSEMBLE  GCC/stream_sse.o
  ./GCC/stream_sse.s: Assembler messages:
  ./GCC/stream_sse.s:26: Error: too many memory references for `mov'
  ./GCC/stream_sse.s:33: Error: too many memory references for `xor'
  ./GCC/stream_sse.s:52: Error: invalid instruction suffix for `add'
  ./GCC/stream_sse.s:53: Error: too many memory references for `cmp'
  ./GCC/stream_sse.s:61: Error: too many memory references for `mov'
  ./GCC/stream_sse.s:32: Error: invalid operands (*UND* and .data sections) for 
`+'
  ./GCC/stream_sse.s:36: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:37: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:38: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:39: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:41: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:43: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:45: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:47: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:48: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:49: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:50: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  ./GCC/stream_sse.s:51: Error: invalid operands (*UND* and *ABS* sections) for 
`*'
  Makefile:119: recipe for target 'GCC/stream_sse.o' failed
  make[3]: *** [GCC/stream_sse.o] Error 1
  Makefile:173: recipe for target 'bench/likwid-bench' failed
  make[2]: *** [bench/likwid-bench] Error 2

You might need to enable -msse or -msse2 for at least this file. :-/
Could you please take another look?

Thanks!

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

Bug#825015: vim-command-t: does not work with vim 7.4.1829-1

[Dr Wanderlust]

Great! Thank you for all your work. Glad I could help.

On 21 June 2016 at 15:33, Sam Morris  wrote:

> On Tue, 2016-06-21 at 14:51 -0400, sbi wrote:
> > Package: vim-command-t
> > Version: 4.0-1
> > Followup-For: Bug #825015
> >
> > Dear Maintainer,
> >
> > I'm using x86_64 architecture.
>
> Thanks for that. I have figured out what was going on; I had a local
> build of vim-command-t that had been rebuilt against ruby2.3-dev 2.3.1,
> and I didn't notice that the package in unstable needs to be rebuilt.
>
> I'll try to get a new version uploaded, rebuilt against ruby 2.3.1,
> soon; in the meantime, you can rebuild the package on your own system
> and you'll be able to use the addon.
>
> --
>
> Sam Morris 
> CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

Bug#827878: dgit push can fail if user has push.followTags=true

[Sean Whitton]

Package: dgit
Version: 1.4
Severity: normal
Tags: patch

Hello,

`dgit push` can fail if the user has the push.followTags=true git
configuration setting.  When dgit invokes git to push the dgit refs, git
will also try to push lots of tags, which the dgit-repos pre-receive
hook will reject.

The attached patch probably fixes the problem, although I haven't tested
it because I don't have any uploads that I can make via dgit at present.

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

Kernel: Linux 4.6.0-1-686-pae (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 dgit depends on:
ii  ca-certificates   20160104
ii  coreutils 8.25-2
ii  curl  7.47.0-1
ii  devscripts2.16.5
ii  dpkg-dev  1.18.7
ii  dput  0.9.6.4
ii  git [git-core]1:2.8.1-1
ii  libdpkg-perl  1.18.7
ii  libjson-perl  2.90-1
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-1
ii  libwww-perl   6.15-1
ii  perl  5.22.2-1

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.2p2-5

Versions of packages dgit suggests:
ii  sbuild  0.69.0-2

-- no debconf information

-- 
Sean Whitton
From edaa40430041b53eab55e45b30877d55248fb108 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Wed, 22 Jun 2016 10:10:16 +0900
Subject: [PATCH] unset push.followTags when pushing in `dgit push`

Otherwise, the push to dgit-repos might fail because git will push lots
of tags that the dgit-repos post-receive hook will reject.
---
 dgit | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dgit b/dgit
index e02a6bd..6182ddc 100755
--- a/dgit
+++ b/dgit
@@ -2061,7 +2061,7 @@ END
 if (!check_for_git()) {
 	create_remote_git_repo();
 }
-runcmd_ordryrun @git, qw(push),access_giturl(),
+runcmd_ordryrun @git, qw(-c push.followTags=false push),access_giturl(),
 $forceflag."HEAD:".rrref(), $forceflag."refs/tags/$tag";
 runcmd_ordryrun @git, qw(update-ref -m), 'dgit push', lrref(), 'HEAD';
 
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#827881: #827881: using sysctl on Linux is bogus

[Adam Borowski]

> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Builds of likwid 4.1 on x32 fail:

Usually, FTBFS on a non-release architecture is not a RC bug.
However, in this case, the new code is so bogus that IMHO keeping this
severity is warranted.

You're supposed to never use the sysctl syscall on Linux.  It hasn't been
removed outright only because ancient glibc uses it to query kernel's
version and "we don't break userspace".  Any other use will spam syslog.
"man 2 sysctl" has some information.

So how come likwid calls it?  Turns out someone had the brilliant idea of
using autoconf... once.  The resultant config from some random machine is
hardcoded in the source.  This syscall does exist on darwin and freebsd.

If you want a dirty patch that solves symptoms but not the cause, fixing
FTBFS on x32 and syslog spam on amd64:

--- a/ext/hwloc/include/private/autogen/config.h
+++ b/ext/hwloc/include/private/autogen/config.h
@@ -330,7 +330,9 @@
 #define HAVE_SYNC_BUILTINS 1
 
 /* Define to '1' if sysctl is present and usable */
+#ifndef __linux__
 #define HAVE_SYSCTL 1
+#endif
 
 /* Define to '1' if sysctlbyname is present and usable */
 /* #undef HAVE_SYSCTLBYNAME */
@@ -359,7 +361,9 @@
 #define HAVE_SYS_STAT_H 1
 
 /* Define to 1 if you have the  header file. */
+#ifndef __linux__
 #define HAVE_SYS_SYSCTL_H 1
+#endif
 
 /* Define to 1 if you have the  header file. */
 #define HAVE_SYS_TIME_H 1

-- 
An imaginary friend squared is a real enemy.

Bug#827881: likwid: FTBFS: sysctl system call is unsupported in x32 kernel

[Aaron M. Ucko]

Source: likwid
Version: 4.1.0+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of likwid 4.1 on x32 fail:

  In file included from /usr/include/x86_64-linux-gnux32/sys/sysctl.h:63:0,
   from ./hwloc/topology.c:45:
  /usr/include/x86_64-linux-gnux32/bits/sysctl.h: At top level:
  /usr/include/x86_64-linux-gnux32/bits/sysctl.h:19:3: error: #error "sysctl 
system call is unsupported in x32 kernel"
   # error "sysctl system call is unsupported in x32 kernel"

It looks like hwloc_fallback_nbprocessors should wind up using sysconf
anyway, making this header (and hwloc_get_sysctl*) unnecessary; please
conditionalize them more tightly.

Thanks!

Bug#747672: Dropping patch

[Sean Whitton]

control: found -1 burp/1.4.40-1

Dear Svante,

Although the burp 1.4.40 test suite passes with this patch applied,
upstream reports that the 2.0.x series test suite finds a problem.  The
patch causes this problem when applied to burp 1.4.40, even though the
older test suite passes.

Since this is an old bug, I am preparing a QA upload to drop the patch
for now.

Burp's author Graham Keeling explains:

> Here is the code in 1.4.40.
>
> // Return 0 for lock got, 1 for lock not got, -1 for error.
> int get_lock(const char *path)
> {
> ... some set up
> if(lockf(fdlock, F_TLOCK, 0))
> {
> if(errno==EACCES || errno==EAGAIN)
> return 1; // Lock not got.
> logp("Could not get lock %s: %s\n", path, strerror(errno));
> return -1; // Some other error.
> }
> ...some more code...
> return 0;
> }
>
>
> As you can see, get_lock() has three different return codes that mean
> different things.
> If you check 'man 2 flock', you will see that flock() will never set errno
> to EACCES or EAGAIN. This means that get_lock() will never detect the
> difference between a lock existing, or some error.

Thanks to Graham for letting me reproduce this explanation.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#827882: clementine: Newer upstream release 1.3.1 available

[Carl Suster]

Package: clementine
Severity: wishlist

Dear Maintainer,

There is a newer upstream release of Clementine available [1], version 1.3.1
released on April 20th.

There do not appear to be many changes since the release candidate which is
currently in the archives, but it would be nice to have the latest version all
the same. Thanks!

[1] https://github.com/clementine-player/Clementine/releases/tag/1.3.1

Bug#827873: RFP: python-pytz -- World timezone definitions, modern and historical

[Julien Puydt]

Hi,

On 22/06/2016 01:57, Iain R. Learmonth wrote:

Package: wnpp
Severity: wishlist
Control: block 810629 by -1

* Package name: python-pytz
  Version : 2016.4
  Upstream Author : Stuart Bishop
* URL : http://pythonhosted.org/pytz
* License : MIT
  Programming Lang: Python
  Description : World timezone definitions, modern and historical

pytz brings the Olson tz database into Python. This library allows
accurate and cross platform timezone calculations using Python 2.4
or higher. It also solves the issue of ambiguous times at the end
of daylight saving time, which you can read more about in the Python
Library Reference (``datetime.tzinfo``).

Almost all of the Olson timezones are supported.

Releases are available at: https://pypi.python.org/pypi/pytz



Notice that Debian already has it under the name python-tz -- it just 
needs updating to the latest version (I filled a bug about it...).


Snark on #debian-python

Bug#827883: tellico: unused nepomuk-core-dev build dependency

[Pino Toscano]

Source: tellico
Version: 2.3.9+dfsg.1-1
Severity: wishlist
Tags: patch

Hi,

the nepomuk-core-dev build dependency is not used, since tellico uses
the old nepomuk libraries available in kdelibs.

Can you please remote it, so in the future mepomuk-core might be
removed? Patch attached for it.

Thanks,
-- 
Pino
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: tellico
 Section: kde
 Priority: optional
 Maintainer: Regis Boudin 
-Build-Depends: debhelper (>= 9), cmake, pkg-config, pkg-kde-tools (>= 0.9), kdelibs5-dev (>=4:4.7), libxml2-dev, libxslt1-dev, libtag1-dev, libyaz4-dev, libkcddb-dev, kdepimlibs5-dev (>=4:4.7), libpoppler-qt4-dev, libexempi-dev, libqimageblitz-dev, nepomuk-core-dev, libksane-dev, shared-desktop-ontologies, libqjson-dev
+Build-Depends: debhelper (>= 9), cmake, pkg-config, pkg-kde-tools (>= 0.9), kdelibs5-dev (>=4:4.7), libxml2-dev, libxslt1-dev, libtag1-dev, libyaz4-dev, libkcddb-dev, kdepimlibs5-dev (>=4:4.7), libpoppler-qt4-dev, libexempi-dev, libqimageblitz-dev, libksane-dev, shared-desktop-ontologies, libqjson-dev
 Standards-Version: 3.9.6
 Homepage: http://tellico-project.org/
 Vcs-Git: git://anongit.kde.org/tellico.git

Bug#827821: kicad: Python error by opening Pcbnew

[Erik Schick]

Package: kicad
Version: 4.0.2+dfsg1-2~bpo8+1-1
Severity: normal

Dear Maintainer,

i get the following error, when I start Pcbnew. It seems to don't have any
effects to usage of the program.

Python error -1 occurred running string `import wxversion;
wxversion.select('3.0')`
pcbnewInitPythonScripting() failed.

Greetings
Erik Schick



-- System Information:
Debian Release: 8.5
  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/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kicad depends on:
ii  kicad-common4.0.2+dfsg1-2~bpo8+1-1
ii  libboost-context1.55.0  1.55.0+dfsg-3
ii  libboost-date-time1.55.01.55.0+dfsg-3
ii  libboost-filesystem1.55.0   1.55.0+dfsg-3
ii  libboost-iostreams1.55.01.55.0+dfsg-3
ii  libboost-locale1.55.0   1.55.0+dfsg-3
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-regex1.55.01.55.0+dfsg-3
ii  libboost-system1.55.0   1.55.0+dfsg-3
ii  libboost-thread1.55.0   1.55.0+dfsg-3
ii  libc6   2.19-18+deb8u4
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libgcc1 1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]10.3.2-1+deb8u1
ii  libglew1.10 1.10.0-3
ii  libglu1-mesa [libglu1]  9.0.0-2
ii  libgomp14.9.2-10
ii  libice6 2:1.0.9-1+b1
ii  libpython2.72.7.9-2
ii  libsm6  2:1.2.2-1+b1
ii  libstdc++6  4.9.2-10
ii  libwxbase3.0-0  3.0.2-1+b1
ii  libwxgtk3.0-0   3.0.2-1+b1
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1

kicad recommends no packages.

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-4
ii  kicad-doc-en 4.0.2+dfsg1-2~bpo8+1-1

-- no debconf information

Bug#827822: Poor error message in debootstrap invocation

[Alex Gaynor]

Package: debootstrap
Severity: normal
thanks

If debootstrap is invoked like so: `sudo debootstrap jessie jessie
--include=openssh-server` it errors out with `/usr/sbin/debootstrap: 314:
set: Illegal option --`. The correct invocation is to move teh `--include`
before `jessi`, but it'd be nice if a readable error message was emitted.
(I'm using an older tutorial for invoking debootstrap which suggested the
original invocation, I'm not sure if debootstrap's syntax has changed since
then, or that post never worked)

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6

Bug#827828: Package: installation-reports

[George Vasiliou (GMAIL)]

Package: installation-reports

Hi there,
I would like to mention a kind of bug in your net-install iso image.

When tried to install Debian on my net book (Toshiba Radius 11 L10WC10C)
using the debian-8.5.0-amd64-netinst.iso image i got the following error:

Installer was prompting me to provide proprietary drivers for
rtlwifi/rtl8723befw.bin.

As a new user that i thought to try Debian, i didn't had this driver to
feed the installer and as a resut the installation made was a basic one
without internet connection.

Although i succeed to find this driver on web, i was not capable to make
the installer load this rtl8723 driver.
Maybe a kind of typical file browser within the Debian Installer could be a
good idea, to allow me to drive Debian Installer to where this driver file
is.

On the other hand consider a new user trying to test Debian, and the whole
thing collapses for a missing driver (while other distros like Ubuntu
provide that driver out-of-the-box).

Regards,
George Vasiliou
Greece

Bug#827823: --xwayland: command not found

[Martin Insulander]

Package: plasma-workspace-wayland

Version: 4:5.6.4-2

Starting Plasma with wayland doesn't work. ~/.wayland-errors contains the
error:
--xwayland: command not found

I looked at /usr/bin/startplasmacompositor and would say the line 222 is
faulty:
--xwayland --libinput
--exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma

Just for testing I tried to change it to:
/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma
Which seems closer to for example:
https://github.com/KDE/plasma-workspace/blob/master/startkde/startplasmacompositor.cmake

And did it work? well, a bit further at least ;)

Best regards from Martin Insulander

I am using Debian testing (2016-06-06) amd64

Bug#827826: xul-ext-spdy-indicator: Dependency problem @ Sid

[Roman Horn�k]

Package: xul-ext-spdy-indicator
Version: 2.2-1
Severity: normal

Hi,

When trying to install the xul-ext-spdy-indicator package, the Iceweasel is 
marked for installation as well.
It would be good to change dependencies of this package to Iceweasel OR Firefox.

Thanks
Roman


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

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

Bug#827825: linux-image-4.6.0-1-amd64: nouveau does not recognized my graphic card anymore

[Vincent Danjean]

Package: src:linux
Version: 4.6.2-1
Severity: important

  Hi,

  The 4.6.2-1 version has a regression about the nouveau driver. I can load and
unload it (I've a main Intel graphic card and a NVidia (optimus) one) but, on
load, I get:
[ 4878.113784] MXM: GUID detected in BIOS
[ 4878.113822] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - 
Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
[ 4878.113948] ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
[ 4878.114259] ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
[ 4878.114629] pci :01:00.0: optimus capabilities: enabled, status dynamic 
power, hda bios codec supported
[ 4878.114632] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEGP.DGFX 
handle
[ 4878.114670] nouveau :01:00.0: unknown chipset ()
[ 4878.114673] nouveau: probe of :01:00.0 failed with error -12

And xrandr confirm this:
$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x46 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 
4 outputs: 3 associated providers: 0 name:Intel
$ 

  The previous kernel I was using (linux-image-4.5.0-1-amd64/4.5.1-1) worked
(my graphic card detected and usable : I need it for my external screen on
DisplayPort), so I put the 'important' severity (ie regression)

  Regards
Vincent

-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-1 (2016-06-15)

** Command line:
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 root=/dev/mapper/eyak-root ro acpi_osi=Linux 
"acpi_osi=!Windows 2012" apparmor=1 security=apparmor swapaccount=1 
cgroup_enable=memory quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[ 4834.488307] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4834.488313] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4834.488316] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4834.788260] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4834.788266] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4834.788269] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.088267] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.088272] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.088275] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.388242] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.388248] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.388250] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.688223] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.688228] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.688231] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.988168] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.988174] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4835.988177] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
[ 4837.269018] en-wifi: authenticate with 00:c8:8b:68:4f:cf
[ 4837.271844] en-wifi: send auth to 00:c8:8b:68:4f:cf (try 1/3)
[ 4837.297968] en-wifi: authenticated
[ 4837.300047] en-wifi: associate with 00:c8:8b:68:4f:cf (try 1/3)
[ 4837.404082] en-wifi: associate with 00:c8:8b:68:4f:cf (try 2/3)
[ 4837.405465] en-wifi: RX AssocResp from 00:c8:8b:68:4f:cf (capab=0x101 
status=12 aid=0)
[ 4837.405468] en-wifi: 00:c8:8b:68:4f:cf denied association (code=12)
[ 4837.688962] en-wifi: authenticate with 00:c8:8b:68:4f:c0
[ 4837.691584] en-wifi: send auth to 00:c8:8b:68:4f:c0 (try 1/3)
[ 4837.694200] en-wifi: authenticated
[ 4837.695991] en-wifi: associate with 00:c8:8b:68:4f:c0 (try 1/3)
[ 4837.699579] en-wifi: RX AssocResp from 00:c8:8b:68:4f:c0 (capab=0x421 
status=12 aid=0)
[ 4837.699581] en-wifi: 00:c8:8b:68:4f:c0 denied association (code=12)
[ 4837.953013] en-wifi: authenticate with 00:c8:8b:e6:58:df
[ 4837.955628] en-wifi: send auth to 00:c8:8b:e6:58:df (try 1/3)
[ 4838.031740] en-wifi: authenticated
[ 4838.031975] en-wifi: associate with 00:c8:8b:e6:58:df (try 1/3)
[ 4838.033281] en-wifi: RX AssocResp from 00:c8:8b:e6:58:df (capab=0x101 
status=12 aid=0)
[ 4838.033283] en-wifi: 00:c8:8b:e6:58:df denied association (code=12)
[ 4838.226952] en-wifi: authenticate with 00:c8:8b:e6:58:d0
[ 4838.229655] en-wifi: send auth to 00:c8:8b:e6:58:d0 (try 1/3)
[ 4838.232269] en-wifi: authenticated
[ 4838.235949] en-wifi: associate with 00:c8:8b:e6:58:d0 (try 1/3)
[ 4838.238925] en-wifi: RX AssocResp from 00:c8:8b:e6:58:d0 (capab=0x421 
status=12 aid=0)
[ 4838.238927] en-wifi: 

Bug#555116: Shouldn't Debian Perl team take over libgetopt-mixed-perl

[Andreas Tille]

Hi,

I'm a bit astonished that there exist de-facto orphaned Perl packages
inside Debian and Debian Perl team has no grip on it ...

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#827798: package mame FTBFS on mips64el (unrecognized command line option '-m64')

[James Cowgill]

Hi,

On Tue, 2016-06-21 at 08:06 +, Daniel Knezevic wrote:
> Package: mame
> Version: 0.173-6
> Severity: important
> Tags: sid + patch
> Justification: FTBFS
> User: debian-m...@lists.debian.org
> Usertags: mips-patch
> 
> Hello,
> Package mame FTBFS on mips64el with following error:
> g++: error: unrecognized command line option '-m64'
> 
> build log:
> https://buildd.debian.org/status/fetch.php?pkg=mame=mips64el
> =0.173-6=1464007306
> 
> -m64 flag is not supported on mips64el.
> 
> I have created two patches. One patch is to remove -m64 flag for
> mips64el. The other patch is for debian/rules, it adds -no-keep-
> memory flag for mips64el to fix linker issues with memory
> consumption.
> 
> Patches are tested on mips64el, i386 and amd64.
> With these patches package was build successfully.

Did you test the patches on mipsel as well? Your patch uses 'uname -m'
to determine if it's building for mips64, but a lot (I think all?) of
the mipsel buildds run 64-bit kernels and would match your check as
well.

Thanks,
James

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

Bug#827824: libopenmpi1.10: libmca_common_verbs.so.7 missing in installation

[Matthias Liertzer]

Package: libopenmpi1.10
Version: 1.10.3-2
Severity: important

Dear Maintainer,

when trying to run the standard mpi petsc test case after compilation,
mpiexec gives the following warning:

mca: base: component_find: unable to open
/usr/lib/openmpi/lib/openmpi/mca_btl_openib: libmca_common_verbs.so.7:
cannot open shared object file: No such file or directory

According to `dpkg -L', libmca_common_verbs.so.7 should be installed
in /usr/lib, however, it bizarrely does not seem to be installed there
as verified by a reinstall:

$ sudo apt-get install --reinstall libopenmpi1.10
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,110 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 420483 files and directories currently installed.)
Preparing to unpack .../libopenmpi1.10_1.10.3-2_amd64.deb ...
Unpacking libopenmpi1.10 (1.10.3-2) over (1.10.3-2) ...
Processing triggers for libc-bin (2.22-12) ...
Setting up libopenmpi1.10 (1.10.3-2) ...
Processing triggers for libc-bin (2.22-12) ...
$ dpkg -L libopenmpi1.10 | grep common_verbs.so.7
/usr/lib/libmca_common_verbs.so.7
/usr/lib/libmca_common_verbs.so.7.0.0
$ ls /usr/lib | grep common_verbs.so.7
$

Best regards,
Matthias Liertzer

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

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 libopenmpi1.10 depends on:
ii  libc6 2.22-12
ii  libfabric11.3.0-2
ii  libgcc1   1:6.1.1-7
ii  libgfortran3  6.1.1-7
ii  libhwloc-plugins  1.11.3-2
ii  libhwloc5 1.11.3-2
ii  libibverbs1   1.2.0-1
ii  libquadmath0  6.1.1-7
ii  libstdc++66.1.1-7

Versions of packages libopenmpi1.10 recommends:
ii  openmpi-bin  1.10.3-2

libopenmpi1.10 suggests no packages.

-- no debconf information

Bug#827827: ERROR: php-elisp is broken - called emacs-package-install as a new-style add-on, but has no compat file.

[積丹尼 Dan Jacobson]

Package: php-elisp
Version: 1.13.5-3

Setting up php-elisp (1.13.5-3) ...
Installing new version of config file /etc/emacs/site-start.d/50php-elisp.el ...
ERROR: php-elisp is broken - called emacs-package-install as a new-style 
add-on, but has no compat file.
Install php-elisp for emacs
Install php-elisp for emacs24
install/php-elisp: Handling install for emacsen flavor emacs24

Bug#827843: ITP: xlogo -- XLogo is an interpreter for the Logo programming language, written in Java.

[Wolf Bergenheim]

Package: wnpp
Severity: wishlist
Owner: Wolf Bergenheim 

* Package name: xlogo
  Version : 0.9.95
  Upstream Author : Loïc Le Coq 
* URL : http://xlogo.tuxfamily.org
* License : GPL
  Programming Lang: Java
  Description : XLogo is an interpreter for the Logo programming language, 
written in Java.

XLogo is an interpreter for the Logo programming language, written in Java.
It supports nine languages, (French, English, Spanish, Arabic, Portugese,
German, Esperanto, Galacian and Greek) and is licensed under the GPL.
Logo is a programming language developed in the 1970's by Seymour Papert.
It is an excellent language to begin learning with, as it teaches the basics
of things like loops, tests, procedures, etc. The user moves an object called
a "turtle" around the screen using commands as simple as forward, back, right,
and so on. As it moves, the turtle leaves a trail behind it, and so it is
therefore possible to create drawings. Operations on lists and words are also
possible.
For example,  forward 100 right 90 will first make the turtle move 100 steps
forward, and then turn the turtle 90° to the right.
This very intuitive graphical approach makes Logo an ideal language for
beginners, especially children!
 
The debian-live-based distribution Lernstick, that focuses on education,
wants to include XLogo. So I thought I'll add it to Debian to give XLogo
to even more people.

I plan to maintain it on my own, with the help of the Lernstick team or under
collab-maint.

Bug#794316: can't unlock desktop

[Quentin BUISSON-DEBON]

Package: gdm3
Version: 3.14.1-7
Followup-For: Bug #794316

Hi,

>>My laptop screen had been locked for a while.  I typed the password and
>>nothing happened.  After a few seconds, the screen went blank again.

Same issue here but without the blank screen --> Just a freeze of gdm3 with the
login screen.

when i do a "CTRL+ALT+F2", log in with my user then type "sudo servie gdm3
restart", my laptop in unfreeze, I can log in again on Gnome3, but i loose my
sessins windows with this way

Hope it will help you



-- System Information:
Debian Release: 8.5
  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/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 gdm3 depends on:
ii  accountsservice   0.6.37-3+b1
ii  adduser   3.113+nmu3
ii  cinnamon [x-window-manager]   2.2.16-5
ii  dconf-cli 0.22.0-1
ii  dconf-gsettings-backend   0.22.0-1
ii  debconf [debconf-2.0] 1.5.56
ii  gir1.2-gdm3   3.14.1-7
ii  gnome-session [x-session-manager] 3.14.0-2
ii  gnome-session-bin 3.14.0-2
ii  gnome-settings-daemon 3.14.2-3
ii  gnome-shell   3.14.4-1~deb8u1
ii  gnome-terminal [x-terminal-emulator]  3.14.1-1+deb8u1
ii  gsettings-desktop-schemas 3.14.1-1
ii  kde-window-manager [x-window-manager] 4:4.11.13-2
ii  konsole [x-terminal-emulator] 4:4.14.2-1
ii  libaccountsservice0   0.6.37-3+b1
ii  libaudit1 1:2.4-1+b1
ii  libc6 2.19-18+deb8u4
ii  libcanberra-gtk3-00.30-2.1
ii  libcanberra0  0.30-2.1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libgdm1   3.14.1-7
ii  libglib2.0-0  2.42.1-1+b1
ii  libglib2.0-bin2.42.1-1+b1
ii  libgtk-3-03.14.5-1+deb8u1
ii  libpam-modules1.1.8-3.1+deb8u1+b1
ii  libpam-runtime1.1.8-3.1+deb8u1
ii  libpam-systemd215-17+deb8u4
ii  libpam0g  1.1.8-3.1+deb8u1+b1
ii  librsvg2-common   2.40.5-1+deb8u2
ii  libselinux1   2.3-2
ii  libsystemd0   215-17+deb8u4
ii  libwrap0  7.6.q-25
ii  libx11-6  2:1.6.2-3
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  lxsession [x-session-manager] 0.5.1-2
ii  lxterminal [x-terminal-emulator]  0.2.0-1
ii  marco [x-window-manager]  1.8.2+dfsg1-6
ii  mate-session-manager [x-session-manager]  1.8.1-8
ii  mate-terminal [x-terminal-emulator]   1.8.1+dfsg1-4
ii  metacity [x-window-manager]   1:3.14.3-1
ii  muffin [x-window-manager] 2.2.6-4
ii  mutter [x-window-manager] 3.14.4-1~deb8u1
ii  openbox [x-window-manager]3.5.2-8
ii  policykit-1   0.105-8
ii  terminator [x-terminal-emulator]  0.97-4
ii  ucf   3.0030
ii  x11-common1:7.7+7
ii  x11-xserver-utils 7.7+3+b1
ii  xfce4-session [x-session-manager] 4.10.1-10
ii  xfce4-terminal [x-terminal-emulator]  0.6.3-1+b1
ii  xfwm4 [x-window-manager]  4.10.1-3
ii  xterm [x-terminal-emulator]   312-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.14.0-1
ii  desktop-base   8.0.2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils  7.7+1
ii  xserver-xephyr 2:1.16.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4+deb8u1
ii  libpam-gnome-keyring  3.14.0-1+b1

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3

Bug#827834: ruby-state-machine: FTBFS: machine_test.rb:3264:in `': uninitialized constant MachineDrawingTest::Constants (NameError)

[Chris Lamb]

Source: ruby-state-machine
Version: 1.2.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-state-machine fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../ruby-activemodel_2%3a4.2.6-1_all.deb ...
  Unpacking ruby-activemodel (2:4.2.6-1) ...
  Selecting previously unselected package ruby-arel.
  Preparing to unpack .../ruby-arel_6.0.3-2_all.deb ...
  Unpacking ruby-arel (6.0.3-2) ...
  Selecting previously unselected package ruby-activerecord.
  Preparing to unpack .../ruby-activerecord_2%3a4.2.6-1_all.deb ...
  Unpacking ruby-activerecord (2:4.2.6-1) ...
  Selecting previously unselected package ruby-sqlite3.
  Preparing to unpack .../ruby-sqlite3_1.3.11-2_amd64.deb ...
  Unpacking ruby-sqlite3 (1.3.11-2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-12) ...
  Processing triggers for systemd (230-2) ...
  Setting up openssl (1.0.2h-1) ...
  Setting up ca-certificates (20160104) ...
  Setting up rubygems-integration (1.10) ...
  Setting up ruby-did-you-mean (1.0.0-2) ...
  Setting up ruby-minitest (5.9.0-1) ...
  Setting up ruby-net-telnet (0.1.1-2) ...
  Setting up ruby-power-assert (0.3.0-1) ...
  Setting up ruby-test-unit (3.1.7-2) ...
  Setting up libyaml-0-2:amd64 (0.1.6-3) ...
  Setting up libgmpxx4ldbl:amd64 (2:6.1.0+dfsg-2) ...
  Setting up libgmp-dev:amd64 (2:6.1.0+dfsg-2) ...
  Setting up libcdt5 (2.38.0-14) ...
  Setting up libcgraph6 (2.38.0-14) ...
  Setting up libgts-0.7-5:amd64 (0.7.6+darcs121130-1.2) ...
  Setting up libpng16-16:amd64 (1.6.23-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1) ...
  Setting up libwebp5:amd64 (0.4.4-1+b2) ...
  Setting up libxpm4:amd64 (1:3.5.11-1+b1) ...
  Setting up libgd3:amd64 (2.2.1-1) ...
  Setting up libltdl7:amd64 (2.4.6-0.1) ...
  Setting up fontconfig (2.11.0-6.4) ...
  Regenerating fonts cache... done.
  Setting up libthai-data (0.1.24-2) ...
  Setting up libdatrie1:amd64 (0.2.10-2) ...
  Setting up libthai0:amd64 (0.1.24-2) ...
  Setting up libpango-1.0-0:amd64 (1.40.1-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.6-2) ...
  Setting up libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpathplan4 (2.38.0-14) ...
  Setting up libxdot4 (2.38.0-14) ...
  Setting up libgvc6 (2.38.0-14) ...
  Setting up libgvpr2 (2.38.0-14) ...
  Setting up x11-common (1:7.7+15) ...
  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 libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up graphviz (2.38.0-14) ...
  Setting up rake (10.5.0-2) ...
  Setting up libruby2.3:amd64 (2.3.1-5) ...
  Setting up ruby2.3 (2.3.1-5) ...
  Setting up ruby2.3-dev:amd64 (2.3.1-5) ...
  Setting up ruby-all-dev:amd64 (1:2.3.0+4) ...
  Setting up ruby (1:2.3.0+4) ...
  Setting up gem2deb-test-runner (0.30.3) ...
  Setting up ruby-setup (3.4.1-9) ...
  Setting up gem2deb (0.30.3) ...
  Setting up ruby-graphviz (1.2.2-1) ...
  Setting up ruby-i18n (0.7.0-2) ...
  Setting up ruby-json (1.8.3-1+b3) ...
  Setting up ruby-atomic (1.1.16-2+b6) ...
  Setting up ruby-thread-safe (0.3.5-3) ...
  Setting up ruby-tzinfo (1.2.2-1) ...
  Setting up ruby-activesupport (2:4.2.6-1) ...
  Setting up ruby-blankslate (3.1.3-1) ...
  Setting up ruby-builder (3.2.2-4) ...
  Setting up ruby-activemodel (2:4.2.6-1) ...
  Setting up ruby-arel (6.0.3-2) ...
  Setting up ruby-activerecord (2:4.2.6-1) ...
  Setting up ruby-sqlite3 (1.3.11-2) ...
  Setting up ruby-state-machine-build-deps (1.2.0-2) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in 

Bug#827839: gl2ps: Remove redundant 1000_gl2ps_tikz-fix-rotated-text.patch. Causes now an extra brace.

[Agustin Martin]

Source: gl2ps
Version: 1.3.9-2
Severity: normal

Dear Maintainers,

Just noticed that gl2ps still has 1000_gl2ps_tikz-fix-rotated-text.patch
enabled. This is not only redundant but wrong.

It was extracted from 1.3.9 for 1.3.8-1 to handle a missing brace
problem for rotated text in octave->pgf output, but fix is already
in 1.3.9. Keeping this patch enabled causes an extra brace added,
one by 1.3.9 code and another one by the patch, resulting in buggy
pgf output, now with an error about extra brace.

Please remove it.

Patch attached just for completeness, removal is trivial.

Regards,

-- 
Agustin
>From c88ff10eb94582f693876d0a27667a5a8db68344 Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo 
Date: Tue, 21 Jun 2016 17:08:16 +0200
Subject: [PATCH] 1000_gl2ps_tikz-fix-rotated-text.patch: Remove. Applied
 upstream in 1.3.9.

This patch was taken from upstream 1.3.9 and incorporated to 1.3.8-1.3 NMU
to fix #820930.

While it originally fixed a missing brace, keeping it now results in an
extra brace added in #820930 conditions, one by the fixed code in 1.3.9
and another by the applied patch.

Remove it.
---
 .../patches/1000_gl2ps_tikz-fix-rotated-text.patch | 33 --
 debian/patches/series  |  1 -
 2 files changed, 34 deletions(-)
 delete mode 100644 debian/patches/1000_gl2ps_tikz-fix-rotated-text.patch

diff --git a/debian/patches/1000_gl2ps_tikz-fix-rotated-text.patch b/debian/patches/1000_gl2ps_tikz-fix-rotated-text.patch
deleted file mode 100644
index bb6ff0c..000
--- a/debian/patches/1000_gl2ps_tikz-fix-rotated-text.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-Description: gl2psPrintPGFPrimitive misses closing braces for rotated text
- In function gl2psPrintPGFPrimitive, switch case GL2PS_TEXT opens a curly
- brace which is never closed again, if the text is rotated: I discovered
- the problem when trying to produce tikz output with octave, which produced
- broken output when inserting labels to the y -axis.
- Hopes this helps, with kind regards,
- Felix
-Author: Felix
-Bug: https://geuz.org/trac/gl2ps/ticket/11
-Upstream-Commit: https://geuz.org/trac/gl2ps/changeset/601
-Bug-Debian: https://bugs.debian.org/820930
-
-Index: gl2ps/gl2ps.c
-===
 gl2ps.orig/gl2ps.c
-+++ gl2ps/gl2ps.c
-@@ -5483,11 +5483,16 @@ static void gl2psPrintPGFPrimitive(void
- prim->verts[0].rgba[2], prim->data.text->str);
- 
- fprintf(gl2ps->stream, "}{}{\\pgfusepath{discard}}}");
-+if(prim->data.text->angle)
-+   fprintf(gl2ps->stream, "}");
-+
-+fprintf(gl2ps->stream, "\n");
- 
- if(prim->data.text->angle)
-fprintf(gl2ps->stream, "}");
- 
- fprintf(gl2ps->stream, "\n");
-+
- break;
-   case GL2PS_SPECIAL :
- /* alignment contains the format for which the special output text
diff --git a/debian/patches/series b/debian/patches/series
index b320a7b..20745d0 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1 @@
-1000_gl2ps_tikz-fix-rotated-text.patch
 2000_FixTestLinkage.patch
-- 
2.8.1

Bug#827831: python-proliantutils: FTBFS: ImportError: No module named 'mock'

[Chris Lamb]

Source: python-proliantutils
Version: 2.1.5-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,

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

  [..]

  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource_fail
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource_fail
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource_key_error
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_bios_settings_resource_key_error
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource_fail
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource_fail
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource_key_error
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_iscsi_settings_resource_key_error
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices_no_boot_order
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices_no_boot_order
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices_no_bootsources
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_persistent_boot_devices_no_bootsources
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_device_missing
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_device_missing
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_fail
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_fail
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_invalid_device
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_invalid_device
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_vmedia_not_supported
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__get_vm_device_status_vmedia_not_supported
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__is_boot_mode_uefi_bios
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__is_boot_mode_uefi_bios
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__is_boot_mode_uefi_uefi
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__is_boot_mode_uefi_uefi
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_continous_redirection
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_continous_redirection
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_okay
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_okay
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_one_redirection
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_one_redirection
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_request_error
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_request_error
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_response_decode_error
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_response_decode_error
 ... ok
  
proliantutils.tests.ilo.test_ris.TestRISOperationsPrivateMethods.test__rest_op_response_gzipped_response
  

Bug#827832: python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found

[Chris Lamb]

Source: python-pytc
Version: 0.8-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  python-pytc
   Version:  0.8-2
   Build architecture:   amd64
   Date: Tue, 21 Jun 2016 16:06:13 +0100
   Hostname: 9f757beb9639
   Uname:Linux 9f757beb9639 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'python-pytc-build-deps' in 
'../python-pytc-build-deps_0.8-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package python-pytc-build-deps.
  (Reading database ... 23084 files and directories currently installed.)
  Preparing to unpack python-pytc-build-deps_0.8-2_all.deb ...
  Unpacking python-pytc-build-deps (0.8-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs libexpat1-dev libpython-all-dbg libpython-all-dev libpython-dbg
libpython-dev libpython2.7 libpython2.7-dbg libpython2.7-dev
libtokyocabinet-dev libtokyocabinet9 python-all python-all-dbg
python-all-dev python-dbg python-dev python2.7-dbg python2.7-dev
  Suggested packages:
python2.7-gdbm-dbg python2.7-tk-dbg python-gdbm-dbg python-tk-dbg
  The following NEW packages will be installed:
cdbs libexpat1-dev libpython-all-dbg libpython-all-dev libpython-dbg
libpython-dev libpython2.7 libpython2.7-dbg libpython2.7-dev
libtokyocabinet-dev libtokyocabinet9 python-all python-all-dbg
python-all-dev python-dbg python-dev python2.7-dbg python2.7-dev
  0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 42.4 MB of archives.
  After this operation, 86.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 
[80.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-2 [938 B]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libpython2.7 amd64 
2.7.12~rc1-2 [1068 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.1.1-3 [127 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dev 
amd64 2.7.12~rc1-2 [27.8 MB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libpython-dev amd64 
2.7.11-2 [19.8 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dev 
amd64 2.7.11-2 [952 B]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python2.7-dev amd64 
2.7.12~rc1-2 [281 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 python-dev amd64 
2.7.11-2 [1128 B]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 python-all-dev amd64 
2.7.11-2 [954 B]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dbg 
amd64 2.7.12~rc1-2 [4409 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libpython-dbg amd64 
2.7.11-2 [19.8 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dbg 
amd64 2.7.11-2 [1074 B]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 python2.7-dbg amd64 
2.7.12~rc1-2 [7768 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 python-dbg amd64 
2.7.11-2 [1204 B]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 python-all-dbg amd64 
2.7.11-2 [956 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libtokyocabinet9 
amd64 1.4.48-10 [366 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 libtokyocabinet-dev 
amd64 1.4.48-10 [441 kB]
  Fetched 42.4 MB in 0s (55.6 MB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 

Bug#827833: rglpk: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: rglpk
Version: 0.6-1-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,

rglpk fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../liblapack-dev_3.6.0-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.0-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../libtinfo-dev_6.0+20160319-2_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160319-2) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../libncurses5-dev_6.0+20160319-2_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160319-2) ...
  Selecting previously unselected package libreadline6-dev:amd64.
  Preparing to unpack .../libreadline6-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline6-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libreadline-dev:amd64.
  Preparing to unpack .../libreadline-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libjpeg62-turbo-dev:amd64.
  Preparing to unpack .../libjpeg62-turbo-dev_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package libjpeg-dev.
  Preparing to unpack .../libjpeg-dev_1%3a1.5.0-1_all.deb ...
  Unpacking libjpeg-dev (1:1.5.0-1) ...
  Selecting previously unselected package libpcre16-3:amd64.
  Preparing to unpack .../libpcre16-3_2%3a8.38-3.1_amd64.deb ...
  Unpacking libpcre16-3:amd64 (2:8.38-3.1) ...
  Selecting previously unselected package libpcre32-3:amd64.
  Preparing to unpack .../libpcre32-3_2%3a8.38-3.1_amd64.deb ...
  Unpacking libpcre32-3:amd64 (2:8.38-3.1) ...
  Selecting previously unselected package libpcrecpp0v5:amd64.
  Preparing to unpack .../libpcrecpp0v5_2%3a8.38-3.1_amd64.deb ...
  Unpacking libpcrecpp0v5:amd64 (2:8.38-3.1) ...
  Selecting previously unselected package libpcre3-dev:amd64.
  Preparing to unpack .../libpcre3-dev_2%3a8.38-3.1_amd64.deb ...
  Unpacking libpcre3-dev:amd64 (2:8.38-3.1) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libpng-dev:amd64.
  Preparing to unpack .../libpng-dev_1.6.23-1_amd64.deb ...
  Unpacking libpng-dev:amd64 (1.6.23-1) ...
  Selecting previously unselected package libbz2-dev:amd64.
  Preparing to unpack .../libbz2-dev_1.0.6-8_amd64.deb ...
  Unpacking libbz2-dev:amd64 (1.0.6-8) ...
  Selecting previously unselected package liblzma-dev:amd64.
  Preparing to unpack .../liblzma-dev_5.1.1alpha+20120614-2.1_amd64.deb ...
  Unpacking liblzma-dev:amd64 (5.1.1alpha+20120614-2.1) ...
  Selecting previously unselected package icu-devtools.
  Preparing to unpack .../icu-devtools_55.1-7_amd64.deb ...
  Unpacking icu-devtools (55.1-7) ...
  Selecting previously unselected package libicu-dev:amd64.
  Preparing to unpack .../libicu-dev_55.1-7_amd64.deb ...
  Unpacking libicu-dev:amd64 (55.1-7) ...
  Selecting previously unselected package cdbs.
  Preparing to unpack .../archives/cdbs_0.4.142_all.deb ...
  Unpacking cdbs (0.4.142) ...
  Selecting previously unselected package r-base-dev.
  Preparing to unpack .../r-base-dev_3.3.0.20160615-1_all.deb ...
  Unpacking r-base-dev (3.3.0.20160615-1) ...
  Selecting previously unselected package r-cran-slam.
  Preparing to unpack .../r-cran-slam_0.1-34-1_amd64.deb ...
  Unpacking r-cran-slam (0.1-34-1) ...
  Selecting previously unselected package libsuitesparseconfig4:amd64.
  Preparing to unpack .../libsuitesparseconfig4_1%3a4.5.3-1_amd64.deb ...
  Unpacking libsuitesparseconfig4:amd64 (1:4.5.3-1) ...
  Selecting previously unselected package libamd2:amd64.
  Preparing to unpack .../libamd2_1%3a4.5.3-1_amd64.deb ...
  Unpacking libamd2:amd64 (1:4.5.3-1) ...
  Selecting previously unselected package libcolamd2:amd64.
  Preparing to unpack .../libcolamd2_1%3a4.5.3-1_amd64.deb ...
  Unpacking libcolamd2:amd64 (1:4.5.3-1) ...
  Selecting previously unselected package libltdl7:amd64.
  Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
  Unpacking libltdl7:amd64 (2.4.6-0.1) ...
  Selecting previously unselected package libglpk40:amd64.
  Preparing to unpack .../libglpk40_4.60-2+b1_amd64.deb ...
  Unpacking libglpk40:amd64 (4.60-2+b1) ...
  Selecting previously unselected package libgmpxx4ldbl:amd64.
  Preparing to unpack .../libgmpxx4ldbl_2%3a6.1.0+dfsg-2_amd64.deb ...
  Unpacking libgmpxx4ldbl:amd64 (2:6.1.0+dfsg-2) ...
  Selecting previously unselected package libgmp-dev:amd64.
  Preparing to unpack .../libgmp-dev_2%3a6.1.0+dfsg-2_amd64.deb ...
  Unpacking libgmp-dev:amd64 (2:6.1.0+dfsg-2) ...
  Selecting previously unselected package libcamd2:amd64.
  Preparing to unpack .../libcamd2_1%3a4.5.3-1_amd64.deb 

Bug#827830: libzmq5 4.1.5-1 lost libsodium18 dependency

[Adrian Bunk]

Package: libzmq5
Version: 4.1.5-1
Severity: normal

https://buildd.debian.org/status/fetch.php?pkg=zeromq3=i386=4.1.5-1=1466268230
...
configure: Using tweetnacl for CURVE security
...

This might be related to the following entry in the upstream changelog:
* Fixed #1850 - detection issues with tweetnacl/libsodium.

This looks like an (intentionally or unintentionally) changed default
upstream, configuring with --with-libsodium seems to do the right thing.

I do not know which of tweetnacl/libsodium is better, but a change
that seems to have happened only by accident should be double-checked
and either libsodium used again or the build dependency dropped.

Bug#817532: Shouldn't Debian Perl team take over libgetopt-mixed-perl

[Axel Beckert]

Hi,

Andreas Tille wrote:
> I'm a bit astonished that there exist de-facto orphaned Perl packages

Maybe I'm just a little bit more cautious about the "de-facto" part of
that sentence...

> inside Debian and Debian Perl team has no grip on it ...

My first goal was to fix the issue, especially because multiple of my
packages are affected by this RC bug.

A potential takeover needs less streamlined politics than just an NMU.
But yes, a takeover is something I already thought about.

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#827797: ncurses-bin: The files under /usr/bin/ are missing.

[Sven Joachim]

Control: severity -1 grave

On 2016-06-21 15:40 +0800, Steven Shiau wrote:

> After upgrading ncurses-bin to 6.0+20160319-2, the binary files in
> /usr/bin/ are gone. No more command "clear", etc. After inspecting the
> files from ncurses-bin, they are not included:
> $ dpkg -L ncurses-bin
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/ncurses-bin
> /usr/share/doc/ncurses-bin/FAQ
> /usr/share/doc/ncurses-bin/changelog.Debian.gz
> /usr/share/doc/ncurses-bin/changelog.gz
> /usr/share/doc/ncurses-bin/copyright
> /usr/share/man

That's because of the findutils bug #827724[1].  From the build log[2]:

,
| dh_install -pncurses-bin -Xncurses5-config -Xncursesw5-config
| find: Duplicate file type 'l' in the argument list to -type.
| find: Duplicate file type 'l' in the argument list to -type.
| find: Duplicate file type 'l' in the argument list to -type.
| find: Duplicate file type 'l' in the argument list to -type.
`

Unfortunately the findutils bug did not cause the build to fail, since
"dh_install -X" runs find in a shell pipe. :-/

I'll ask for a binNMU on the affected architectures.

Cheers,
   Sven


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827724
2. 
https://buildd.debian.org/status/fetch.php?pkg=ncurses=i386=6.0%2B20160319-2=1466430130

Bug#827837: python3-binwalk: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python3/dist-packages/binwalk/__init__.py

[Andreas Beckmann]

Package: python3-binwalk
Version: 2.1.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package python3-binwalk.
  Preparing to unpack .../python3-binwalk_2.1.1-7_all.deb ...
  Unpacking python3-binwalk (2.1.1-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-binwalk_2.1.1-7_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/binwalk/__init__.py', 
which is also in package binwalk 2.1.1-6
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-binwalk_2.1.1-7_all.deb

cheers,

Andreas


binwalk=2.1.1-6_python3-binwalk=2.1.1-7.log.gz
Description: application/gzip

Bug#825015:

[Dr Wanderlust]

I have vim-gtk3 7.4.1829-1 installed.

On 21 June 2016 at 05:49, Sam Morris  wrote:

> On Tue, 2016-06-21 at 00:51 -0400, Dr Wanderlust wrote:
> > Unfortunately, this bug still persists after updating to vim-command-
> > t 4.0-1.
> >
> > command-t.vim could not load the C extension
> > Please see INSTALLATION and TROUBLE-SHOOTING in the help
> > Vim Ruby version: 2.3.1-p112
> > Expected version: 2.3.0-p0
> >
> > Would you consider reopening this bug-report?
>
> Can you please check which versions of the following packages you have
> installed?
>
> vim-athena, vim-gnome, vim-gtk, vim-gtk3, vim-nox
>
> --
>
> Sam Morris 
> CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

Bug#827841: ITP: mocassin -- Monte Carlo simulations of ionised nebulae

[Roger Wesson]

Package: wnpp
Severity: wishlist
Owner: Roger Wesson 

* Package name: mocassin
  Version : 2.02.70
  Upstream Author : Barbara Ercolano
* URL : http://www.3d-mocassin.net
* License : GPL-2+
  Programming Lang: fortran
  Description : Monte Carlo simulations of ionised nebulae

MOCASSIN is a fully 3D or 2D photoionisation and dust radiative transfer code 
which employs a Monte Carlo approach to the transfer of radiation through media 
of arbitrary geometry and density distribution. It was originally developed for 
the modelling of photoionised regions like HII regions and planetary nebulae 
and has since expanded and been applied to a variety of astrophysical problems, 
including modelling clumpy dusty supernova envelopes, star forming galaxies, 
protoplanetary disks and inner shell fluorence emission in the photospheres of 
stars and disk atmospheres. The code can deal with arbitrary Cartesian grids of 
variable resolution, it has successfully been used to model complex density 
fields from SPH calculations and can deal with ionising radiation extending 
from Lyman edge to the X-ray. The dust and gas microphysics is fully coupled 
both in the radiation transfer and in the thermal balance.

Mocassin is a widely used code, with papers describing it having nearly 200 
citations in the astronomical literature.  The source code is available from 
3d-mocassin.net and is licensed under GPL-v2+.  I propose to create a debian 
package which can be maintained within the Debian Astronomy Team.

Bug#827829: giza-dev: file conflict with pgplot5: /usr/include/cpgplot.h

[Andreas Beckmann]

Package: giza-dev
Version: 0.9.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package giza-dev.
  Preparing to unpack .../giza-dev_0.9.4-1_amd64.deb ...
  Unpacking giza-dev (0.9.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/giza-dev_0.9.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/cpgplot.h', which is also in package 
pgplot5 5.2.2-19.2+b1
  Processing triggers for libc-bin (2.22-11) ...
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/giza-dev_0.9.4-1_amd64.deb


cheers,

Andreas

Bug#827829: giza-dev: file conflict with pgplot5: /usr/include/cpgplot.h

[Ole Streicher]

Control: severity -1 important

Hi Andreas,

to justify the severity: Since pgplot5 is in non-free which is formally
not part of Debian, why do you think it is a policy violation when
giza-dev has an undeclared conflict with it?

https://www.debian.org/doc/debian-policy/ch-archive.html#s-main

"The main archive area comprises the Debian distribution. Only the
packages in this area are considered part of the distribution."

Therefore, I would consider this as non-RC.

Best regards

Ole

Bug#827836: kde-l10n: missing Breaks+Replaces against kde-telepathy-call-ui

[Andreas Beckmann]

Source: kde-l10n
Version: 4:16.04.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package kde-l10n-bg.
  Preparing to unpack .../kde-l10n-bg_4%3a16.04.2-1_all.deb ...
  Unpacking kde-l10n-bg (4:16.04.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-l10n-bg_4%3a16.04.2-1_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/bg/LC_MESSAGES/ktp-call-ui.mo', which 
is also in package kde-telepathy-call-ui 0.9.0-2+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kde-l10n-bg_4%3a16.04.2-1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)


This happens in all kde-l10n-XX packages.


cheers,

Andreas

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

[Gianfranco Costamagna]

Hi Roger,

>Control: retitle -1 RFS: libcorkipset/1.1.1+20150311-1 [ITP] -- C
>library to store sets/maps of IP address


thanks for that!
>I think you didn't review since you did last time, and I did some
>changes based on some changes in previous post, so here I *rewrite*
>the previous post.


thanks
>Fixed.
>Fixed.


ok

>This convinced me that this library can be packaged, too.


:)
>Yes, I used python3-cram in libcork, but this time it just doesn't work.
>Without my patch, python-cram just report "no test" error.
>I guess upstream didn't finish the test case of cram.
>So I removed it.


ok


>upstream's docs/CMakeLists.txt just output nothing.
>You can see "set(MAN_PAGES)", the target is empty!


lol ok :)
>So I used the same way in libcork to generate docs.
>Actually the upstream was during the transition from sphinx to pandoc.
>They removed sphinx setting, added pandoc setting, but didn't remove
>sphinx docs.
>So I patched back sphinx setting, just works.
>
>(docs from upstream just poor, even I wrote a patch to add index page)


I was already ok with the patch, just adding some Description makes the
review easier ;)


>After reading your comment for three time, now I understand it.
>I put it under dh_install as you recommend.
>Now it's rebuildable.


:)

>Without "--builddirectory=build", the docs will be built under
>/docs/
>This make install file hard to write.
>So here I keep as it was.


mmm strange...
this is what I have in the docs file
cat debian/libcorkipset-doc.docs 
build-*/docs/html


:)

>Removed.
>Thanks for your suggestion!


wonderful! you are welcome!
>Since the most authors quit redjack, and they're almost not active,

>I consider it should be called libcorkipset.

I see activity upstream, lets wait for the rename to be effective then!
>Fixed.


ok

>> "set(CMAKE_INSTALL_LIBDIR lib${LIB_SUFFIX} CACHE STRING"
>> note the LIB_SUFFIX
>>
>> and then the install files can change from
>> usr/lib/lib*.so usr/lib/${DEB_HOST_MULTIARCH}
>> to
>> usr/lib/*/*.so
>> and similar for others
>
>Yes, moving "include(GNUInstallDirs)" makes dh-exec useless.
>My mistake forced me to introduced this complex. Sorry about that.


the missing LIB_SUFFIX makes it FTBFS on Ubuntu, where cmake has a little
different implementation.

(and a non-defined variable is just a no-op in Debian)

>Tried, just added a lintian warning.
>Should be fixed when debhelper 10 released.
>So I keep as it is.


yes, thanks!

(BTW compat 10 works great)

Gianfranco