Bug#865838: dossizola: Should show up in board game submenu - need desktop category

[Petter Reinholdtsen]

Package: dossizola
Version: 1.0-9
Tags: patch

In KDE, the menu item for dossizola show up directly under the "Games"
menu, instead of showing up alongside the other board games in the Board
Game submenu.  The reason for this is the value in the Categories field
of the desktop file.  It currently look like this:

  Categories=Game;

Please change it to include the arcade category (and add the Application
category for good measure):

  Categories=Application;Game;BoardGame;

-- 
Happy hacking
Petter Reinholdtsen

Bug#865837: heroes: Should show up in arcade submenu - need desktop category

[Petter Reinholdtsen]

Package: heroes
Version: 0.21-15
Tags: patch

In KDE, the menu item for heroes show up directly under the "Games"
menu, instead of showing up alongside the other arcade games in the
Arcade submenu.  The reason for this is the value in the Categories
field of the desktop file.  It currently look like this:

  Categories=Application;Game;

Please change it to include the arcade category:

  Categories=Application;Game;ArcadeGame;

-- 
Happy hacking
Petter Reinholdtsen

Bug#865822: mutt: Enter key disabled with latest upgrade

[Jamie Heilman]

> It behaves like all the sane compile time defaults were replaced
> with something unusable.

I was able to restore most functionality by running mutt -D with
1.8.0, and then again with 1.8.3 and then sourcing a file that
restores all the settings I lost.  Hopefully that helps somebody else
who's trying to figure out all the regressions this version
introduced.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#865836: barrage: Should show up in arcade submenu - need desktop category

[Petter Reinholdtsen]

Package: barrage
Version: 1.0.4-2
Tags: patch

In KDE, the menu item for barrage show up directly under the "Games"
menu, instead of showing up alongside the other arcade games in the
Arcade submenu.  The reason for this is the value in the Categories
field of the desktop file.  It currently look like this:

  Categories=Game;ActionGame

Please change it to include the arcade category (and add the trailing
semicolon):

  Categories=Game;ActionGame;ArcadeGame;

-- 
Happy hacking
Petter Reinholdtsen

Bug#865835: wordwarvi: Should show up in arcade submenu - need desktop category

[Petter Reinholdtsen]

Package: wordwarvi
Version: 1.00+dfsg1-3
Tags: patch

In KDE, the menu iten for wordwarvi show up directly under the "Game"
menu, instead of showing up alongside the other arcade games in the
Arcade submenu.  The reason for this is the value in the Categories
field of the desktop file.  It currently look like this:

  Categories=Game;ActionGame

Please change it to include the arcade category (and add the trailing
semicolon):

  Categories=Game;ActionGame;ArcadeGame;

-- 
Happy hacking
Petter Reinholdtsen

Bug#865473: installation-reports, clean install debian-9.0.0-amd64-xfce-CD-1.iso, grub not working on /dev/sdc

[Rolf Reintjes]

Hello,

On 24.06.2017 18:34, Cyril Brulebois wrote:

Hi,

Rolf Reintjes  (2017-06-24):

Hello KiBi,

On 24.06.2017 18:02, Cyril Brulebois wrote:

Thanks for your report.

Can you please attach the installer's syslog, which might have some clue?

You'll find it under the /var/log/installer directory.


Please find attached the file syslog from /var/log/installer.


Thanks!

This looks weird:

Jun 20 18:33:58 grub-installer: info: Installing grub on ''


Are you sure you selected the /dev/sdc entry when you were prompted where
to install grub, and not the default “Enter manually” which comes with an
empty string by default?


I did the installation once again and had got the same problem. I 
downloaded the iso from another location:

http://debian.netcologne.de/debian-cd/9.0.0/amd64/iso-cd/debian-9.0.0-amd64-xfce-CD-1.iso
I took another USB-stick than before for installation. During 
installation this USB-stick was /dev/sdc and the debian system was 
/dev/sdb .

I selected /dev/sdb for grub install.
When rebooted grub came with this error message:
"error: file '/boot/grub/i386-pc/normal.mod' not found.
 Entering rescue mode...
 grub rescue> "

I solved the problem the same way as before.

Best regards

Rolf

Bug#830902: openBVE doesn't start

[Petter Reinholdtsen]

I also see the same behavior.  I tried to debug it, but have no idea how to
debug mono applications.

-- 
Happy hacking
Petter Reinholdtsen

Bug#865834: dar: fix Built-Using where libc has a SONAME different than libc6

[Pino Toscano]

Source: dar
Version: 2.5.8-3
Severity: important
Tags: patch

Hi,

currently dar fails to build on architectures where libc has a SONAME
different than libc6: alpha [1], kfreebsd-amd64 [2], kfreebsd-i386 [3],
and hurd-i386 (not yet attempted on buildds).

Since on those architectures the SONAME is different, then libc6 (and
libc6-dev) does not exist there, and thus causing the dpkg-query for
libc6-dev to fail. A better solution is to use libc-dev-bin, helper
development package installed at the same version by libc-dev.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=dar&arch=alpha&ver=2.5.8-3&stamp=1490841925&raw=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=dar&arch=kfreebsd-amd64&ver=2.5.8-3&stamp=1498347293&raw=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=dar&arch=kfreebsd-i386&ver=2.5.8-3&stamp=1498342322&raw=0

Thanks,
-- 
Pino
--- a/debian/rules
+++ b/debian/rules
@@ -10,7 +10,7 @@ DEB_DH_INSTALL_SOURCEDIR = debian/tmp
 
 DEB_INSTALL_DOCS_ALL =
 
-BUILT_USING_PACKAGES = libc6-dev libattr1-dev libbz2-dev libgcrypt20-dev 
libgpgme-dev liblzo2-dev zlib1g-dev
+BUILT_USING_PACKAGES = libc-dev-bin libattr1-dev libbz2-dev libgcrypt20-dev 
libgpgme-dev liblzo2-dev zlib1g-dev
 
 BUILT_USING=$(shell dpkg-query -f '$${source:Package} (= $${source:Version}), 
' -W $(BUILT_USING_PACKAGES))
 

Bug#865822: mutt: Enter key disabled with latest upgrade

[Jamie Heilman]

It goes beyond just the tmpdir setting; for those of us who start our
mutt configs with "reset all" we wind up with a more or less unusable
mail client.  In my case it screwed up decoding my aliases with
"Warning: Bad IDN" for every single alias I had, ment that I didn't
start in my inbox as defined by my $MAIL environment variable, and
couldn't decode html email despite having set a tmpdir ... and so
forth.  It behaves like all the sane compile time defaults were
replaced with something unusable.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#865833: libacpi FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: libacpi
Version: 0.2-4.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libacpi fails to cross build from source, because it uses the build
architecture compiler. Running make through dh_auto_build mostly fixes
that, because dh_auto_build knows how to pass cross compilers. The
makefile still invokes the build architecture strip (and fails). Such
stripping is normally done by dh_strip and this extra stripping breaks
-dbgsym packages. Thus it should simply be removed. Then it rebuilds the
shared library (without a cross compiler) during make install as the
depenencies are wrong. After addressing all of the above points in the
attached patch, it cross builds successfully. Please consider applying
the patch.

Helmut
diff --minimal -Nru libacpi-0.2/debian/changelog libacpi-0.2/debian/changelog
--- libacpi-0.2/debian/changelog2016-03-11 09:37:19.0 +0100
+++ libacpi-0.2/debian/changelog2017-06-25 07:48:27.0 +0200
@@ -1,3 +1,13 @@
+libacpi (0.2-4.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross compilers to make.
++ Add nostrip.patch.
++ Add cross.patch.
+
+ -- Helmut Grohne   Sun, 25 Jun 2017 07:48:27 +0200
+
 libacpi (0.2-4.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff --minimal -Nru libacpi-0.2/debian/patches/cross.patch 
libacpi-0.2/debian/patches/cross.patch
--- libacpi-0.2/debian/patches/cross.patch  1970-01-01 01:00:00.0 
+0100
+++ libacpi-0.2/debian/patches/cross.patch  2017-06-25 07:48:27.0 
+0200
@@ -0,0 +1,20 @@
+From: Helmut Grohne 
+Subject: do not rebuild libacpi.so during make install
+
+Index: libacpi-0.2/Makefile
+===
+--- libacpi-0.2.orig/Makefile
 libacpi-0.2/Makefile
+@@ -28,9 +28,10 @@
+   @${AR} $@ ${OBJ}
+   @${RANLIB} $@
+ 
+-libacpi.so: ${OBJ}
++libacpi.so: libacpi.so.${SOVERSION}
++libacpi.so.${SOVERSION}: ${OBJ}
+   @echo LD $@
+-  @${LD} ${SOFLAGS} -o $@.${SOVERSION} ${OBJ}
++  @${LD} ${SOFLAGS} -o $@ ${OBJ}
+ 
+ test-libacpi: ${OBJ_test}
+   @echo LD $@
diff --minimal -Nru libacpi-0.2/debian/patches/nostrip.patch 
libacpi-0.2/debian/patches/nostrip.patch
--- libacpi-0.2/debian/patches/nostrip.patch1970-01-01 01:00:00.0 
+0100
+++ libacpi-0.2/debian/patches/nostrip.patch2017-06-25 07:48:27.0 
+0200
@@ -0,0 +1,17 @@
+From: Helmut Grohne 
+Subject: do not strip during build
+
+Stripping breaks cross building and -dbgsym packages.
+
+Index: libacpi-0.2/Makefile
+===
+--- libacpi-0.2.orig/Makefile
 libacpi-0.2/Makefile
+@@ -35,7 +35,6 @@
+ test-libacpi: ${OBJ_test}
+   @echo LD $@
+   @${LD} -o $@ ${OBJ_test} ${LDFLAGS}
+-  @strip $@
+ 
+ install: all
+   @echo installing header to ${DESTDIR}${PREFIX}/include
diff --minimal -Nru libacpi-0.2/debian/patches/series 
libacpi-0.2/debian/patches/series
--- libacpi-0.2/debian/patches/series   2016-03-11 09:18:41.0 +0100
+++ libacpi-0.2/debian/patches/series   2017-06-25 07:48:27.0 +0200
@@ -1 +1,3 @@
 01-newer-linux-kernels.patch
+nostrip.patch
+cross.patch
diff --minimal -Nru libacpi-0.2/debian/rules libacpi-0.2/debian/rules
--- libacpi-0.2/debian/rules2016-03-11 09:32:03.0 +0100
+++ libacpi-0.2/debian/rules2017-06-25 07:48:12.0 +0200
@@ -12,7 +12,7 @@
 build: build-stamp
 build-stamp:
dh_testdir
-   $(MAKE)
+   dh_auto_build
 
touch $@
 

Bug#865577: cloud-init FTBFS: recipe for target 'pep8' failed

[Joonas Kylmälä]

Hey.

As there has not been yet a new release of the upstream package (current
one is 0.7.9) to which we could upgrade, I decided to create a patch
specifically for Debian. See it attached. The patch is pretty much the
same as Joshua Powers' upstream one. The only difference is the usage of
httplib instead of hclient.

Thanks,
Joonas Kylmälä
>From 8afb8941e696b74ca03a7c80e15eed320e1b8e72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Joonas=20Kylm=C3=A4l=C3=A4?= 
Date: Sun, 25 Jun 2017 07:42:13 +0200
Subject: [PATCH] Fix Python code style errors (Closes #865577)

This commit is based on Joshua Powers' upstream commit
with hash 5f14a0b1ca3079e4ab43d615840866a4b7d8df6a
(code-style: make master pass pycodestyle (2.3.1) cleanly).
---
 tools/make-mime.py | 2 +-
 tools/mock-meta.py | 5 -
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/tools/make-mime.py b/tools/make-mime.py
index 12727126..f6a72044 100755
--- a/tools/make-mime.py
+++ b/tools/make-mime.py
@@ -22,7 +22,7 @@ def file_content_type(text):
 try:
 filename, content_type = text.split(":", 1)
 return (open(filename, 'r'), filename, content_type.strip())
-except:
+except ValueError:
 raise argparse.ArgumentError("Invalid value for %r" % (text))
 
 
diff --git a/tools/mock-meta.py b/tools/mock-meta.py
index d74f9e31..2165d623 100755
--- a/tools/mock-meta.py
+++ b/tools/mock-meta.py
@@ -249,7 +249,10 @@ class MetaDataHandler(object):
 try:
 key_id = int(mybe_key)
 key_name = key_ids[key_id]
-except:
+except ValueError:
+raise WebException(httplib.BAD_REQUEST,
+   "%s: not an integer" % mybe_key)
+except KeyError:
 raise WebException(httplib.BAD_REQUEST,
"Unknown key id %r" % mybe_key)
 # Extract the possible sub-params
-- 
2.11.0

Bug#865832: tinyproxy FTCBFS: fails regex check

[Helmut Grohne]

Source: tinyproxy
Version: 1.8.4-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

tinyproxy fails to cross build from source, because its configure tests
the regex library using a AC_TRY_RUN check and assumes that it is
broken. The check doesn't have an influence on the build result
otherwise and can be opted out with --disable-regexcheck. Once doing
that (for cross builds only), tinyproxy cross successfully. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru tinyproxy-1.8.4/debian/changelog 
tinyproxy-1.8.4/debian/changelog
--- tinyproxy-1.8.4/debian/changelog2017-01-21 12:40:00.0 +0100
+++ tinyproxy-1.8.4/debian/changelog2017-06-25 07:37:47.0 +0200
@@ -1,3 +1,10 @@
+tinyproxy (1.8.4-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: --disable-regexcheck during cross builds (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 25 Jun 2017 07:37:47 +0200
+
 tinyproxy (1.8.4-2) unstable; urgency=medium
 
   * Remove obsolete preinst and postinst maintainer scripts.
diff --minimal -Nru tinyproxy-1.8.4/debian/rules tinyproxy-1.8.4/debian/rules
--- tinyproxy-1.8.4/debian/rules2017-01-20 02:39:38.0 +0100
+++ tinyproxy-1.8.4/debian/rules2017-06-25 07:37:45.0 +0200
@@ -2,17 +2,24 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
+include /usr/share/dpkg/architecture.mk
 
 %:
dh $@ --with autoreconf
 
+ifeq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+CONFIGURE_ARGS = --enable-regexcheck
+else
+# doesn't influence the built, but is an AC_TRY_RUN check
+CONFIGURE_ARGS = --disable-regexcheck
+endif
+
 override_dh_auto_configure:
dh_auto_configure -- \
--sysconfdir=/etc/tinyproxy \
--enable-filter \
--enable-transparent \
-   --enable-regexcheck \
+   $(CONFIGURE_ARGS) \
--enable-reverse \
--enable-upstream \
--enable-xtinyproxy

Bug#865831: cimg: please depend on libopencv-dev, not libcv-dev

[Steve Langasek]

Package: cimg
Version: 1.7.9+dfsg-1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hi Andreas,

The cimg-dev package depends on libcv-dev, which up to now has been provided
by the opencv package.  In the opencv 3.1.0 package in experimental,
libcv-dev has been dropped, leaving only libopencv-dev.  Please update cimg
to depend on this package instead of the libcv-dev compatibility package.

The attached patch has been uploaded to Ubuntu, since opencv 3.1.0 has been
synced there from experimental already.

This will become a serious bug once opencv 3.1.0 is uploaded to unstable.

Hope that helps,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru cimg-1.7.9+dfsg/debian/control cimg-1.7.9+dfsg/debian/control
--- cimg-1.7.9+dfsg/debian/control  2016-12-05 10:45:02.0 -0800
+++ cimg-1.7.9+dfsg/debian/control  2017-06-24 22:33:13.0 -0700
@@ -26,7 +26,7 @@
 Architecture: all
 Depends: libx11-dev,
  libxrandr-dev,
- libcv-dev,
+ libopencv-dev,
  ${misc:Depends},
  ${shlibs:Depends}
 Suggests: xmedcon,
@@ -83,7 +83,7 @@
 libgraphicsmagick++1-dev | libmagick++-dev,
 libfftw3-dev | fftw3-dev,
 libgimp2.0-dev,
-libcv-dev,
+libopencv-dev,
 libhighgui-dev
 Enhances: cimg-dev,
   cimg-doc

Bug#864195: closed by James Cowgill (Bug#864195: fixed in libopenmpt 0.2.8190~beta24-1)

[Jörn Heusipp]

On 06/19/2017 08:45 PM, Debian Bug Tracking System wrote:

#864195: libopenmpt: Security updates libopenmpt-0.2.7386-beta20.3-p7 available
It has been closed by James Cowgill .


As far as I can see, there is still no updated libopenmpt package in 
Stretch for any of the issues.


Jörn

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Hardy]

On Sat, Jun 24, 2017 at 8:07 PM, Paul Hardy  wrote:
> On Sat, Jun 24, 2017 at 7:12 PM, Paul Wise  wrote:
>> On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote:
>>
>>> For what it's worth, I agree that declaring the correct charset in HTTP
>>> metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK 
>>> SPACE
>>> (aka the "byte-order mark") in the file content.
>
> Yes, the BOM was only intended for UTF-16, which could actually have
> two different byte orders.  Because there is no such thing as "byte
> order" with UTF-8, the world wide web has rebranded the UTF-8
> three-byte version of U+FEFF as the "UTF-8 signature".  The original
> intention of The Unicode Consortium was that the sequence would never
> be used in a UTF-8 document.

Russ and I and one other person have alluded to this, but I thought
I'd give the exact text from the Unicode 10.0.0 Standard, which was
just released half a week ago.  The quote is on the bottom of page 67.
The Standard is available at

http://www.unicode.org/versions/Unicode10.0.0/UnicodeStandard-10.0.pdf

You can see that times (and attitudes towards the BOM) change (I added
the "0x" for hexadecimal; the Standard uses subscript 16):

"Unicode Signature. An initial BOM may also serve as an implicit
marker to identify a file as containing Unicode text. For UTF-16, the
sequence 0xFE 0xFF (or its byte-reversed counterpart, 0xFF 0xFE) is
exceedingly rare at the outset of text files that use other character
encodings. The corresponding UTF-8 BOM sequence, 0xEF 0xBB 0xBF, is
also exceedingly rare. In either case, it is therefore unlikely to be
confused with real text data. The same is true for both single-byte
and multibyte encodings.

"Data streams (or files) that begin with the U+FEFF byte order mark
are likely to contain Unicode characters. It is recommended that
applications sending or receiving untyped data streams of coded
characters use this signature. If other signaling methods are used,
signa- tures should not be employed."


Paul Hardy

Bug#802721: lintian: mojibake in HTML documentation

[Paul Hardy]

Another possible solution is to add this tag in the header section of
each Web page:

 

I didn't mention that at first because the tag endings/beginnings are
written in an unconventional way in the lintian HTML file that I
examined; a closing ">" appears at the start of a new line, with an
opening "<" for the next tag appearing right after that.  The easiest
way to handle it might be to spot the line that contains "

Bug#865541: [buildd-tools-devel] Bug#865541: sbuild --apt-distupgrade should not remove build-essential

[Johannes Schauer]

Hi Raphaël,

Quoting Raphael Hertzog (2017-06-23 15:17:50)
> No, I just want the integrated "dist-upgrade" feature to not break the
> build chroot. My definition of "breaking the build chroot" includes
> "removing build-essential".

right, that makes sense. Sbuild should never remove the build-essential package
from the chroot.

It should at least error out when it accidentally does remove it.

> It happens that the repository that I was using had a broken libc6-dev (until
> I updated linux-libc-dev to a newer version) but since libc6-dev was already
> installed in the build chroot, sbuild should be able to build the package
> anyway and just be happy to keep libc6 on hold instead of force-upgrading it
> by removing build-essential.

Yes, but by having the APT_DISTUPGRADE configuration option set to 1 (the
default), the user instructed sbuild to do a "apt-get distupgrade" before the
build. Imagine a user who not just implicitly (through the default) but
explicitly (for example via the ~/.sbuildrc) instructed sbuild to do a
distupgrade but then sbuild doesn't do that and some packages don't get
upgraded. I think as a user explicitly requiring a distupgrade I would expect
sbuild to fail if it cannot perform a distupgrade in a way that doesn't remove
an important package like build-essential. So I don't think it would be a good
solution to add code which by default does only part of a distupgrade.

> This works only if you are able to anticipate the problem. Once libc6-dev has
> been removed from the build chroot, you can't reinstall it as the version
> available in the repository is broken. So you are stuck and must somehow
> manually downgrade to another working version.
> 
> Note also that we are speaking of build daemons where our usual
> interaction is just to upload a package... temporarily modifying the
> sbuild configuration of the build daemon is painful.

Your problem sounds like a bootstrapping problem. You have a build-dependency
cycle between two source packages where each package needs each other to be
built. Thus, would a stage1 package built using build profiles not be able to
solve your situation?

Also, coming back to your first email (which I think I now understand better)

> This happens from time to time in Kali because we have forked linux (which
> builds linux-libc-dev) but not glibc (which builds libc6-dev).  libc6-dev
> embeds a >= dependency on linux-libc-dev on the version on which it was built
> against and is thus non-installable in Kali until we have updated the
> kernel...

So you are building src:glibc using a non-kali kernel?

Why is a >= dependency a problem? Isn't your fork of src:linux not having a
higher version number than the version it comes from?

> > Could you expand on your issue so that I can understand what exactly it is
> > that sbuild is either doing wrong or what you would like sbuild to be able
> > to do?
> 
> I would "sbuild-update -d" to ensure that it doesn't remove
> build-essential (assuming that's what sbuild calls when we use
> --apt-distupgrade).

Assuring to not remove build-essential is a good idea but it wouldn't solve
your problem if I would just ensure this by throwing an error if apt removes
build-essential because it wants to dist-upgrade.

I'm hesitant to add a --dont-distupgrade-if-removes-buildessential switch to
the command line options until I'm sure that there is no better way.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

[James McCoy]

On Sat, Jun 24, 2017 at 11:38:03PM -0400, Louis-Philippe Véronneau wrote:
> I don't feel suddenly changing this is a good move, even though it
> respects what upstream does. To me, this breaks user space big time and
> makes it harder to use vim.

Then make your argument upstream.  I did the same, although for
different reasons.  However, I'm not going to second guess upstream on
this.

There are many people that want the mouse enabled by default and many
people that don't.  The definite way to control an option that you care
about is to use put your preference in ~/.vimrc.

For this specific case, you can even just create a blank ~/.vimrc since
the mere presence of that file will cause Vim not to load defaults.vim.

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

Bug#837974: ftp.debian.org: please enable pdiffs for the debian-debug archive

[Paul Wise]

Control: reopen -1

On Sun, 18 Jun 2017 13:20:00 + Niels Thykier wrote:

> Merged into dak master[1].  Kudos to Ganneff for reviewing the patch. :)

I noticed that this doesn't seem to have taken effect for stretch,
stretch-pu and buster. I guess the stretch one will not happen until
the first point release but I would have expected stretch-pu and buster
would have had this enabled. Could you add those too?

http://debug.mirrors.debian.org/debian-debug/dists/stable-debug/main/
http://debug.mirrors.debian.org/debian-debug/dists/proposed-updates-debug/main/
http://debug.mirrors.debian.org/debian-debug/dists/testing-debug/main/
http://debug.mirrors.debian.org/debian-debug/dists/unstable-debug/main/
http://debug.mirrors.debian.org/debian-debug/dists/experimental-debug/main/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#865830: Please add also the Seafile server

[Bernhard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: seafile
Version: 6.0.6-1
Severity: wishlist

Dear maintainer

Please add also the seafile server in the debian distribution.

Best regards and thank you for your support
Bernhard
-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYvvxz3oQWp9oxCe+7FGr7aO6LbYFAllPOd8THGJld29lcm4x
QGdtYWlsLmNvbQAKCRDsUavto7ottsW+D/9ER3096/2EIU8AsdpwveLjYRgvnkIf
Banna5Z6b7JFV3QsU8hxq4RFcZLudlEQ4HhjOvTvPBcpKIL9KW93db9vHezlRiE+
phPTmaysf4Q/Hymu8jUHPYkcAibwqXjEGkkR2da5rL5DqDXYuIO/Cc2EMzWUb8pO
jxe3jd4V3KNa4RloM43fSU+UUs7YkJIer20xHB59gqT+vJAf0sbr9mDDWRXTBEkr
l5z4m/sUFhTNq5rPvtnbsrFzgHnRbSngKkIxEJyFp+ujKmON3aS2RZeoVUMbxL10
D5hSUiGqx+A9kPwmM2hLelw4/jYm0x5lhTggnZWYudzyfcjVBSIVyLq8lIroOrNP
mB9598Pi7vgVtge4be7FM74gdgx4XAL9cz8ZsvK39/6P48m1j9mOdrnlgLUdNQX5
KMq+CXafIl4rbhIksv8EdHEE0pe8kvxiiVYrHnt1G01DXXMqO9gup2w+OrMwqrqI
168AumMNMIss9CSQoKj65dTXcvI5J3cn5ffwRFhXAHpnTUqaDAS3FIA8dEQlIeKs
g1FhxDCW55KD12tEGOCjhAnJmY+s7UmkJ/LUDHjT/g4LUD8BuiBPLMgF642ZiJwh
/EBmTks5TH8/O0rd7zSP0J0gEvp16AsOBa+FXMF1wivBQ+d7gZFcwWVob7XSKjiy
NkqopYsCxMjQUA==
=d+H9
-END PGP SIGNATURE-

Bug#865829: ftp.debian.org: copy of the Debian constitution is very outdated

[Paul Wise]

Package: ftp.debian.org
Severity: important

The version of the Debian constitution in the archive is 1.3 from 2006
but the latest version on the website is 1.7 from 2016, please update:

http://ftp.debian.org/debian/doc/constitution.txt
https://www.debian.org/devel/constitution

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#837060: debootstrap: Do not install packages of Priority:required for buildd variant

[Johannes Schauer]

Hi,

Quoting Cyril Brulebois (2017-06-24 20:23:25)
> Julien Cristau  (2016-09-12):
> > This is a transient situation because some Essential packages'
> > dependencies changed.  I'd consider this a bug in the archive, not in
> > debootstrap.
> Any reasons to keep this bug report open then? Seen no objections, so I'm
> tempted to close it.

But... the buildd variant still explicitly (and not only implicitly through
dependencies of essential:yes packages) installs Priority:required packages,
no?

cheers, josch


signature.asc
Description: signature

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Hardy]

On Sat, Jun 24, 2017 at 8:13 PM, Russ Allbery  wrote:
>
> That's one of the things that confuses me a bit -- why not just use the
> existing HTML files?  ...
>
> I assume you're looking at:
>
> https://www.debian.org/doc/devel-manuals#policy

I did a StartPage search for "debian upgrade checklist" from past
experience, and a link to the ".txt" file was the very first link that
appeared, but I did not see  a link to the corresponding ".html" file.

To my previous list of three options, there is a fourth option, which
I would also be okay with: change nothing and close the bug.  But take
into consideration that ".txt" file is available on Debian via a web
link, so others are likely to see it.


Paul Hardy

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Wise]

On Sat, 2017-06-24 at 20:48 -0700, Russ Allbery wrote:

> Can't we just set the character set for the text files that come from
> Debian Policy?  At least with Apache you can set character sets with
> whatever granularity you want.

Doesn't look like there are any files within the Debian Policy
directory that are non-UTF-8, so that should be doable.

pabs@mirror-anu:/srv/static.debian.org/mirrors/www.debian.org/cur$ find -iname 
'*.txt' -print0 | xargs -0 isutf8 | grep policy
./doc/manuals/ddp-policy/ddp-policy.en.txt: line 1476, char 1, byte offset 22: 
invalid UTF-8 code

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#865828: ITP: libcryptx-perl -- Perl module that provides a self-contained crypto toolkit

[Lucas Kanashiro]

Package: wnpp
Owner: Lucas Kanashiro 
Severity: wishlist

* Package name: libcryptx-perl 
  Version : 0.27
  Upstream Author : Karel Miko
* URL : https://metacpan.org/release/CryptX  
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module that provides a self-contained crypto
toolkit

Crypt is a self-contained crypto toolkit based on https://github.com/li
btom/libtomcrypt. It provides cyphers, block cipher modes,
authenticated encryption modes, hash functions, message authentication
codes, public key cryptography, cryptographically secure random number
generators, key derivation functions.

This package is a dependency of libspreadsheet-parsexlsx-perl and will
be maintained under the Debian Perl Team umbrella.

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

Bug#865827: ITP: libcryptx-perl -- Perl module that provides a self-contained crypto toolkit

[Lucas Kanashiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: wnpp
Owner: Lucas Kanashiro 
Severity: wishlist

* Package name: libcryptx-perl 
  Version : 0.27
  Upstream Author : Karel Miko
* URL : https://metacpan.org/release/CryptX  
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module that provides a self-contained crypto
toolkit

Crypt is a self-contained crypto toolkit based on https://github.com/li
btom/libtomcrypt. It provides cyphers, block cipher modes,
authenticated encryption modes, hash functions, message authentication
codes, public key cryptography, cryptographically secure random number
generators, key derivation functions.

This package is a dependency of libspreadsheet-parsexlsx-perl and will
be maintained under the Debian Perl Team umbrella.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAllPMzgACgkQ+COicpiD
yXzithAAmchNxZgKyHAKFBLZcTw0uz5kWrsauQYFpAM5BEBO6/sYofZTLXuZZYgN
tcuwxFqQpoiusSmEu09oYFHyxaVwoFHZLthgTi/G3p42JjUrFJystUZOVSaP4CAT
8nJjw4gk76D57R5/EFeomV36jog2ZpZkGbS02u0A1gxVkWi1pACHgr9VaBadjN8m
EjY/Vx0swsXKKan/PZ6k1d9Qr2ZpSt6JQ5gxqOikDMXQkcaYQarxW9A/5e8KhCms
B5H/nrXbwWKofSJBU7skrpNirU/Z112iptzROHnHupSZmEq9CvHod00S9wA3tv/Y
pdq9JHZ5QGId/S7pHGlSFuyz/mxGyUyojfwJwdj1Z6N1SoNhCtQIxEodpZ2grlEo
rmQ5Wy3fWI0ySb3256KsxEMEZmn9k/8VzXDgslsJOUgXDYUiA+rW9Pv/hSx69K2V
IcbuIcHpERs/EX5pmBLmwSlDV/j93Ev8Gg44HYaYnu6NKTwNOJ29rdH+rRZFnpso
+eKro733h8svr9x+JkieFsXui6BEymJOiQLqZnW5n1oUdgKBvEfQgR4z+fFH4bQ0
dW6iOfU+cxDzvJ8a+2BMAvp7i6gzVocnGEC/01Xh60sfkaSUx403di9n0BHWjkmv
CjZio8pDvT7hvtCyhGlsGfv5lLEqvRFwzMOpldCo841kS9VRBQE=
=baEx
-END PGP SIGNATURE-

Bug#865826: ftp.debian.org: convert encoding of all text files to UTF-8

[Paul Wise]

Package: ftp.debian.org
Severity: wishlist

Please convert the following files to UTF-8 encoding:

pabs@mirror-anu:/srv/mirrors/debian$ find -iname '*.txt' -print0 | xargs -0 
isutf8  
./doc/constitution.txt: line 70, char 1, byte offset 65: invalid UTF-8 code
./doc/dedication/dedication-2.2.it.txt: line 3, char 1, byte offset 63: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.es.txt: line 4, char 1, byte offset 34: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.fr.txt: line 1, char 1, byte offset 2: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.ja.txt: line 1, char 1, byte offset 21: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.fi.txt: line 3, char 1, byte offset 5: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.cn.txt: line 1, char 1, byte offset 1: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.de.txt: line 5, char 1, byte offset 4: invalid 
UTF-8 code
./doc/dedication/dedication-2.2.pt_BR.txt: line 5, char 1, byte offset 55: 
invalid UTF-8 code

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#865711: haskell-yaml: FTBFS everywhere (except all)

[Gianfranco Costamagna]

Hello,

>I don't know what we should do here.  The behavior of the embedded
>libyaml differs from our libyaml and I'm not sure why, but it appears

>to be on purpose.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675
because the embedded yaml is more up-to-date wrt the Debian one, and for
this reason I opened a bug report.

Patching yaml in Ubuntu made the whole stuff migrate, however seems that
some unintended side-effects are possible, according to pyyaml regressions
on i386.

https://github.com/snoyberg/yaml/issues/110

G.

Bug#865713: Declaring a charset of UTF-8 for policy files

[Russ Allbery]

Paul Wise  writes:
> On Sat, 2017-06-24 at 20:07 -0700, Paul Hardy wrote:

>> 2) Set the HTTP headers for charset="UTF-8"

> FYI, there are 1018 non-UTF-8 out of 2605 total *.txt files on the
> Debian website and 9 non-UTF-8 out of 1102 total *.txt files in the
> Debian archive mirrors. It seems feasible to convert the files in the
> Debian archive to UTF-8 but it doesn't seem to be feasible to do that
> for www.debian.org.

Can't we just set the character set for the text files that come from
Debian Policy?  At least with Apache you can set character sets with
whatever granularity you want.

-- 
Russ Allbery (r...@debian.org)   

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Wise]

On Sat, 2017-06-24 at 20:07 -0700, Paul Hardy wrote:

> Three possibilities seem to exist, and I am fine with any one being chosen:
> 
> 1) Use the UTF-8 signature in UTF-8 text files

If this triggers browsers to use the right encoding, it seems
reasonable to add it in the situation where the files could be served
by any web server on the Internet. Right now all the mirrors of
www.debian.org are on Debian-controlled servers though, but there are
many non-UTF-8 text files so using the UTF-8 signature seems better.

> 2) Set the HTTP headers for charset="UTF-8"

FYI, there are 1018 non-UTF-8 out of 2605 total *.txt files on the
Debian website and 9 non-UTF-8 out of 1102 total *.txt files in the
Debian archive mirrors. It seems feasible to convert the files in the
Debian archive to UTF-8 but it doesn't seem to be feasible to do that
for www.debian.org.

pabs@mirror-anu:/srv/static.debian.org/mirrors/www.debian.org/cur$ find -iname 
'*.txt' | wc -l
2605
pabs@mirror-anu:/srv/static.debian.org/mirrors/www.debian.org/cur$ find -iname 
*.txt -print0 | xargs -0 isutf8  | wc -l
1018
pabs@mirror-anu:/srv/mirrors/debian$ find -iname '*.txt' | wc -l
1102
pabs@mirror-anu:/srv/mirrors/debian$ find -iname '*.txt' -print0 | xargs -0 
isutf8  | wc -l
9

> 3) Convert UTF-8 text files to HTML documents for web display

Sounds like this is already done.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

[Louis-Philippe Véronneau]

I completely agree with Gabriel on this one. All of a sudden the mouse
default changed and it took me a while to understand why vim had become
so annoying all of a sudden.

I don't feel suddenly changing this is a good move, even though it
respects what upstream does. To me, this breaks user space big time and
makes it harder to use vim.

Each and every time I load vim on a computer that is not mine I have to
make sure to disable the mouse and this can get very annoying when you
maintain a lot of desktop clients in an office.

Thanks for the work maintaining this package btw.

-- 
pollo

On Sat, 24 Jun 2017 21:59:58 -0400 James McCoy  wrote:
> On Sat, Jun 24, 2017 at 09:25:17PM -0400, Gabriel Filion wrote:
> > The default value for the mouse global variable has been changed from empty
> > string to "a" starting from stretch.
> > 
> > This is annoying and does not respect what is documented as the upstream
> > default value:
> > 
> > 'mouse' string  (default "", "a" for GUI, MS-DOS and Win32,
> >  set to "a" in defaults.vim)
> 
> It does respect upstream's default.  If you run ":verbose set mouse?"
> you'll see that it's being set by defaults.vim, as documented above.
> 
> See ":help defaults.vim", as described in
> /usr/share/doc/vim-common/NEWS.Debian.gz.
> 
> Cheers,
> -- 
> James
> GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#865824: gnupg hangs during import of keys (bis)

[Raphaël]

Package: gnupg
Version: 2.1.18-6
Severity: normal

Dear Maintainer,

While trying to convert pubring.gpg into pubring.kbx I did the following
$ gpg --import-options import-local-sigs --import /tmp/xxx
# /tmp/xxx being a copy of pubring.gpg
as advised here https://www.gnupg.org/faq/whats-new-in-2.1.html#keybox

I found that the import worked "once at a time", I mean it imports one
signature then hang => ^C and rerun.


Running using --debug-all, I found the following message just before it
hangs:

gpg: DBG: parse_packet(iob=107): type=2 length=79 (parse.../../g10/keydb.c.1177)
gpg: DBG: iobuf-107.0: underflow: buffer size: 8257; still buffered: 0 => space 
for 8257 bytes
gpg: DBG: iobuf-107.0: close '?

# or during the next run (one sig imported, the next one hanging):
gpg: DBG: parse_packet(iob=468): type=2 length=105 
(parse.../../g10/keydb.c.1177)
gpg: DBG: parse_packet(iob=468): type=14 length=269 
(parse.../../g10/keydb.c.1177)
gpg: DBG: parse_packet(iob=468): type=2 length=76 (parse.../../g10/keydb.c.1177)
gpg: DBG: iobuf-468.0: underflow: buffer size: 137594; still buffered: 0 => 
space for 137594 bytes
gpg: DBG: iobuf-468.0: close '?'

# another run (one sig imported, the next one hanging):
gpg: DBG: parse_packet(iob=287): type=14 length=1037 
(parse.../../g10/keydb.c.1177)
gpg: DBG: parse_packet(iob=287): type=2 length=76 (parse.../../g10/keydb.c.1177)
gpg: DBG: parse_packet(iob=287): type=2 length=88 (parse.../../g10/keydb.c.1177)
gpg: DBG: iobuf-287.0: underflow: buffer size: 64279; still buffered: 0 => 
space for 64279 bytes
gpg: DBG: iobuf-287.0: close '?'


Same result when removing gpg.conf or trying various import-options 
(import-minimal, import-clean)

But --import-options import-export successfully export a GPG traditional 
pubring file (not a GPG keybox) containing the 124 signatures.


See also: #841103


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnupg depends on:
ii  gnupg-agent2.1.18-6
ii  libassuan0 2.4.3-2
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-11+deb9u1
ii  libgcrypt201.7.6-2
ii  libgpg-error0  1.26-2
ii  libksba8   1.3.5-2
ii  libreadline7   7.0-3
ii  libsqlite3-0   3.16.2-5
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages gnupg recommends:
ii  dirmngr 2.1.18-6
pn  gnupg-l10n  

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information

Bug#865825: ITP: libgraphics-colorutils-perl -- Perl module to handle colors and color space conversions

[Lucas Kanashiro]

Package: wnpp
Owner: Lucas Kanashiro 
Severity: wishlist

* Package name: libgraphics-colorutils-perl
  Version : 0.17
  Upstream Author : Philipp K. Janert 
* URL : https://metacpan.org/release/Graphics-ColorUtils
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module to handle colors and color space
conversions

Graphics::ColorUtilss provides some utility functions to handle colors
and color space conversions.
The interface has been kept simple, so that most functions can be
called "inline" when making calls to graphics libraries such as GD, Tk,
or when generating HTML/CSS.

This package is a dependency of libspreadsheet-parsexlsx-perl and will
be maintained under Debian Perl Team umbrella.

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

Bug#865713: Declaring a charset of UTF-8 for policy files

[Russ Allbery]

Paul Hardy  writes:

> If using the UTF-8 signature in a document is too aesthetically
> distateful (and I don't disagree), and if setting the HTTP header to
> denote a UTF-8 charset is not a universal solution because it will only
> have effect on Debian's servers, would a tool that converted such text
> files to an HTML document be desirable?  Such a hypothetical tool would
> insert a meta tag in the header saying .

That's one of the things that confuses me a bit -- why not just use the
existing HTML files?  All the text files in Debian Policy (except for
virtual-package-names-list.txt, which doesn't have any UTF-8) are
generated by rendering the HTML to text.  The HTML is there alongside, and
if you're looking at things in a web browser, I'd think they'd be
preferrable.

I assume you're looking at:

https://www.debian.org/doc/devel-manuals#policy

All of the primary links are to HTML.

I'm certainly happy to try to get the text versions correct, but I would
expect most people would prefer to use the HTML versions.

-- 
Russ Allbery (r...@debian.org)   

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Hardy]

On Sat, Jun 24, 2017 at 7:12 PM, Paul Wise  wrote:
> On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote:
>
>> For what it's worth, I agree that declaring the correct charset in HTTP
>> metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK 
>> SPACE
>> (aka the "byte-order mark") in the file content.

Yes, the BOM was only intended for UTF-16, which could actually have
two different byte orders.  Because there is no such thing as "byte
order" with UTF-8, the world wide web has rebranded the UTF-8
three-byte version of U+FEFF as the "UTF-8 signature".  The original
intention of The Unicode Consortium was that the sequence would never
be used in a UTF-8 document.


In Firefox, if you press Ctrl+Shift+Q you will get an "Inspector".  Loading
https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt
with the Netowrk tab selected in the Inspector shows multiple tabs.
The "Console" tab gives this message, highlighted in pink [for
dramatic effect]:

"The character encoding of the plain text document was not declared.
The document will render with garbled text in some browser
configurations if the document contains characters from outside the
US-ASCII range. The character encoding of the file needs to be
declared in the transfer protocol or file needs to use a byte order
mark as an encoding signature."

So the browser is encouraging the use of this three-byte UTF-8 version
of U+FEFF, even though it was never supposed to be used in a document.
We live in an imperfect world.


Going to the Network tab, reloading the page, and clicking on "Raw
Headers" shows the following information (i just made the request
again):

Request Headers:
Host: www.debian.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Upgrade-Insecure-Requests: 1
If-Modified-Since: Sat, 24 Jun 2017 20:17:13 GMT
If-None-Match: "e965-552ba67456626-gzip"
Cache-Control: max-age=0

Response Headers:
Accept-Ranges: bytes
Cache-Control: max-age=86400
Connection: Keep-Alive
Content-Encoding: gzip
Content-Length: 18592
Content-Type: text/plain
Date: Sun, 25 Jun 2017 02:10:24 GMT
Etag: "e965-552ba67456626-gzip"
Expires: Mon, 26 Jun 2017 02:10:24 GMT
Keep-Alive: timeout=5, max=100
Last-Modified: Sat, 24 Jun 2017 20:17:13 GMT
Server: Apache
Strict-Transport-Security: max-age=15552000
Vary: Accept-Encoding
X-Clacks-Overhead: GNU Terry Pratchett
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
X-XSS-Protection: 1
referrer-policy: no-referrer

So the Content-Type is "text/plain", which results in the "garbled
characters", to quote the Firefox Console window in the Inspector.  As
an aside, the Content-Encoding is "gzip", which is a good thing.


On Sat, Jun 24, 2017 at 7:12 PM, Paul Wise  wrote:
> Forcing every text file to UTF-8 isn't the correct solution either,
> since it breaks text files that are not encoded in UTF-8 (such as old
> dedication texts) and does not work on Debian mirrors that are not
> controlled by us.

If using the UTF-8 signature in a document is too aesthetically
distateful (and I don't disagree), and if setting the HTTP header to
denote a UTF-8 charset is not a universal solution because it will
only have effect on Debian's servers, would a tool that converted such
text files to an HTML document be desirable?  Such a hypothetical tool
would insert a meta tag in the header saying .

If that is an acceptable solution, I could put together an awk script
for Debian (if it would get used) that would employ awk's BEGIN and
END sections to wrap a UTF-8 document in HTML tags, enclosing the text
itself in ... tags.  That would mean that Debian UTF-8
documents intended for being served on the web would have to run such
a utility and be converted into HTML pages for display.

Three possibilities seem to exist, and I am fine with any one being chosen:

1) Use the UTF-8 signature in UTF-8 text files
2) Set the HTTP headers for charset="UTF-8"
3) Convert UTF-8 text files to HTML documents for web display


Paul Hardy

Bug#864810: spamassassin: fails to initialize on IPv6 and then breaks

[Norbert Preining]

Hi Noah,

> It's worse than that. The spamassassin.service unit that we're shipping
> doesn't even have a dependency on the network at all. The improvements

Umpf, indeed, so my server was lucky that IPv4 was fast up and running.

> Specifically, what's missing is "After=syslog.target network.target"

Thanks, I have added that manually to the service file for now,
just to make sure that the next reboot doesn't create problems.

Thanks and all the best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#865823: ITP: libspreadsheet-parsexlsx-perl -- Perl module to parse XLSX files

[Lucas Kanashiro]

Package: wnpp
Owner: Lucas Kanashiro 
Severity: wishlist

* Package name: libspreadsheet-parsexlsx-perl
  Version : 0.27
  Upstream Author : Jesse Luehrs 
* URL : https://metacpan.org/release/Spreadsheet-ParseXLSX 
* License : Expat
  Programming Lang: Perl
  Description : Perl module to parse XLSX files

Spreadsheet::ParseXLSX is an adaptor for Spreadsheet::ParseExcel that
reads XLSX files. For documentation about the various data that you can
retrieve from these classes, please see Spreadsheet::ParseExcel,
Spreadsheet::ParseExcel::Workbook, Spreadsheet::ParseExcel::Worksheet,
and Spreadsheet::ParseExcel::Cell.

This package is a recommended dependency of new upstream version of
libspreadsheet-read-perl and will be maintained under Debian Perl Team
umbrella.

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

Bug#706902: bugs.debian.org: Adding an a11y tag?

[Don Armstrong]

On Sat, 18 May 2013 23:54:56 +0200 Samuel Thibault  wrote:
> I have just gone through the bugs I have submitted or dealt with which
> are on packages _not_ dealt by the Accessibility team, I have tagged
> those which are still opened, can be read on
> ebeb
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=a11y;users=debian-accessibil...@lists.debian.org
> 
> #359062 [i|+|  ] [bogl-bterm-udeb] debian-installer: bterm is not (yet) 
> accessible for brltty
> #551590 [n|  |  ] [metacity] metacity: system bell inaudible in X
> #598133 [n|  |  ] [gdm3] gdm3: Should provide shortcuts and configuration 
> snippets to enable accessibility
> #688045 [n|  |  ] [installation-reports] Installation report for Wheezy beta 
> 2 installer
> #696969 [n|  |  ] [rootskel-gtk] rootskel-gtk: Improve theme=dark, especially 
> the banner
> #696970 [n|  |  ] [cdebconf-gtk-udeb] cdebconf-gtk-udeb: Add support for an 
> alternate logo in the banner
> #487044 [m|+|  ] [grub] Add a "make grub beep" example
> #705802 [m|  |  ] [cdebconf] installation-reports: installation for blind 
> people
> #600488 [n|  |↝] [gnome-settings-daemon] gdm3: Should provide shortcuts and 
> configuration snippets to enable accessibility
> #705599 [i|+|☺] [finish-install] finish-install: 07speakup needs to be 
> updated for Wheezy and GNOME 3

Sorry that I haven't already created this tag; creating it seems
reasonable to me. Is it still wanted?


-- 
Don Armstrong  https://www.donarmstrong.com

First you take a drink,
then the drink takes a drink,
then the drink takes you.
 -- F. Scott Fitzgerald

Bug#865822: mutt: Enter key disabled with latest upgrade

[Norbert Preining]

retitle 865822 no compile time tmp dir
thanks

> today's mutt update to 1.8.3... rendered the Enter key unusable.

The reason was
reset tmpdir
in the config file, which uses the compiled in tmpdir, which seems to be
set to
/
because a trace reveils that mutt tries to create a tmp file in
mkdir("/.mutts9pGoo", 0700) = -1 EACCES (Permission denied)
root.

Please compile in a decent tmpdir like /tmp or /var/tmp

Thanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#865822: mutt: Enter key disabled with latest upgrade

[Norbert Preining]

Package: mutt
Version: 1.8.3+neomutt20170609-1
Severity: serious
Justification: renders unusable

Dear maintainers,

today's mutt update to 1.8.3... rendered the Enter key unusable.
I can navigate my inbox, but it is impossible to open any
mail, which was definitely possible till till morning when
I was reading email.

Removing my whole local configuration activates the Enter key again,
but that is not really optimal.

Thanks

Norbert

-- Package-specific info:
NeoMutt 20170609 (1.8.3)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.12.0-rc6 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-19' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--with-target-s
 ystem-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170618 (Debian 6.3.0-19) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-lua' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-dotlock' '--enable-notmuch' 
'--disable-fmemopen' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' 
'--with-mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' 
'--without-qdbm' '--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 
'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-fz46Ej/mutt-1.8.3+neomutt20170609=. 
-fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS
 =-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-fz46Ej/mutt-1.8.3+neomutt20170609=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-delete-null-pointer-checks

Compile options:
  +attach_headers_color +bkgdset +color +compose_to_sender +compress +cond_date 
  +curs_set +debug +dotlock +encrypt_to_self -exact_address +fcntl -flock 
  -fmemopen +forgotten_attachments +forwref +futimens +getaddrinfo +getsid 
  +gnutls +gpgme +gss +hcache -homespool -iconv_nontrans +ifdef +imap 
  +index_color +initials +keywords +libidn +limit_current_thread +lmdb 
  -locales_hack +lua +meta +mixmaster +multiple_fcc +nested_if +new_mail +nls 
  +nntp +notmuch -openssl +pgp +pop +progress +quasi_delete +regcomp 
  +reply_with_xorig +resizeterm +sasl +sensible_browser -setgid +sidebar 
  +skip_quoted +smime +smtp +start_color +status_color +sun_attachment +timeout 
  +tls_sni +trash +typeahead +wc_funcs 
EXECSHELL="/bin/sh"
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/mutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: http://www.neomutt.org/
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 


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

Kernel: Linux 4.12.0-rc6 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Bug#841842: debian-installer: should use EXT4's native file-system-level encryption

[Cyril Brulebois]

Control: tag -1 moreinfo

Hi Marcos,

Marcos Mobley  (2016-10-23):
> it would be nice to be able to use EXT4's native file-system-level
> encryption instead of LUKS.

As far as I understand it, this would only protect the contents of a
given directory instead of the whole filesystem, so that doesn't look
like a suitable replacement for LUKS?

If my quick research is correct (you didn't much information in your bug
report), then I think the admin is supposed to be setting this up; and
that's not really a job for the Debian Installer.


KiBi.


signature.asc
Description: Digital signature

Bug#865713: Declaring a charset of UTF-8 for policy files

[Paul Wise]

On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote:

> For what it's worth, I agree that declaring the correct charset in HTTP
> metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK SPACE
> (aka the "byte-order mark") in the file content.

Forcing every text file to UTF-8 isn't the correct solution either,
since it breaks text files that are not encoded in UTF-8 (such as old
dedication texts) and does not work on Debian mirrors that are not
controlled by us.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#865821: ITP: matrix-js-sdk -- JavaScript Client-Server SDK for the Matrix protocol

[Hubert Chathi]

Package: wnpp
Owner: Hubert Chathi 
Severity: wishlist

* Package name: matrix-js-sdk
  Version : 0.7.13
  Upstream Author : Vector Creations Limited
* URL or Web page : https://github.com/matrix-org/matrix-js-sdk/
* License : Apache-2.0
  Description : JavaScript Client-Server SDK for the Matrix protocol

matrix-js-sdk is an SDK that allows JavaScript programs to communicate over
Matrix, an open, federated communications protocol.

Note: build-depends on node-babel, which is not in Debian yet

Bug#865653: xrdp: X server timeout

[Stanislav Sinyagin]

Found a solution: after changing to "allowed_users=anybody" in
/etc/X11/Xwrapper.config , XRDP works as expected. So, the default
value ("console") supplied by xserver-xorg-legacy is not compatible
with XRDP, and needs to be adapted.

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

[Paul Wise]

On Sat, 2017-06-24 at 19:24 +0200, Dominique Dumont wrote:

> I find YAML easier to write by hand.

I would strongly suggest never using YAML if you can avoid it. The
parsers in multiple languages (at least Perl, Python) default to unsafe
loading that allows loading arbitrary code in some situations. This
makes YAML parsing a sharp edge that should be avoided when possible.

> That, YAML or JSON may be overkill to store only a list of package names.

For the virtual package names, a \n separated package list seems best,
since it is easy to implement code for loading it in every language.

For the sections, I guess you will be wanting a dict/hash structure, so
I suggest surveying the packages that hard-code the section information
and then deciding the right format based on what languages they use and
what libraries they use and how they store the info already.

https://wiki.debian.org/NewArchiveSections

Personally, I like the deb822 format. It is easy to write by hand for
the most part and has a number of implementations already.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

[Gabriel Filion]

Package: vim-common
Version: 2:8.0.0197-3
Severity: wishlist

Hello,

The default value for the mouse global variable has been changed from empty
string to "a" starting from stretch.

This is annoying and does not respect what is documented as the upstream
default value:

'mouse' string  (default "", "a" for GUI, MS-DOS and Win32,
 set to "a" in defaults.vim)


Can we bring back this variable to default to empty string?

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vim-common depends on:
ii  xxd  2:8.0.0197-3

Versions of packages vim-common recommends:
ii  vim-nox [vim]  2:8.0.0197-3
ii  vim-tiny   2:8.0.0197-3

vim-common suggests no packages.

-- no debconf information

Bug#865819: haskell-hackage-security FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: haskell-hackage-security
Version: 0.5.2.2-7
Severity: serious

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Bug#864810: spamassassin: fails to initialize on IPv6 and then breaks

[Noah Meyerhans]

Control: tags -1 + pending

On Thu, Jun 15, 2017 at 04:23:22AM -0400, Norbert Preining wrote:
> It seems that the systemctl service files do not require a working 
> ipv6 setup

It's worse than that. The spamassassin.service unit that we're shipping
doesn't even have a dependency on the network at all. The improvements
to the unit file were committed to git some time ago, but never made it
into an upload.

Specifically, what's missing is "After=syslog.target network.target"

This will be fixed in unstable shortly, and in an update to stable ASAP.

> Also, it seems that the /etc/default/spamassassin file is not used.

That does not seem to be the case:
root@stretch:~# grep OPTIONS /etc/default/spamassassin 
OPTIONS="--create-prefs --max-children 5 --helper-home-dir --min-children 7 
--timeout-child=360"
root@stretch:~# ps aux|grep spamassassin
root   493  4.8  8.2 162060 83924 ?Ss   17:38   0:00 
/usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid --create-prefs 
--max-children 5 --helper-home-dir --min-children 7 --timeout-child=360

Thanks for your report.
noah

Bug#865818: ganeti FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: ganeti
Version: 2.15.2-3
Severity: serious
Tags: buster sid

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Bug#865817: curry-frontend FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: curry-frontend
Version: 0.4.2-5
Severity: serious

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Bug#865013: [Pkg-utopia-maintainers] Bug#865013: Bug#865013: network-manager-gnome: Consistent segfault when connecting to WPA2 network

[Michael Biebl]

Am 25.06.2017 um 02:56 schrieb Michael Biebl:
> Fwiw, I'm not able to reproduce the crash
> 
> I can create new wifi (WPA2-PSK) connections without problems.
> 
> What kind of connection do you create?
> The backtrace suggests that it might be something WPA2-EAP
> 
> Would probably be a good idea if you file this bug upstream at
> https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager

You could try this patch

https://git.gnome.org/browse/network-manager-applet/commit/?id=b322931ea

It looks related


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



signature.asc
Description: OpenPGP digital signature

Bug#865713: Declaring a charset of UTF-8 for policy files

[Simon McVittie]

On Sat, 24 Jun 2017 at 15:04:41 -0700, Russ Allbery wrote:
> Stéphane Blondon  writes:
> > pabs added such configuration few days ago for Apache configuration:
> > https://anonscm.debian.org/cgit/mirror/dsa-puppet.git/commit/?id=5bcf8431d6b375d211a29f9d2c338e4400332e1a
> 
> Paul, does this resolve your original issue?  I'm a bit worried that it
> might not because this was a little bit ago, and I think it should have
> already been in place when you were testing.

That configuration change was for ftp.debian.org, not for www. A
similar change to apache-www.debian.org.erb would probably do the right
thing.

http://ftp.debian.org/debian/doc/bug-log-access.txt does look correct
to me (with a Unicode copyright symbol near the end) in Firefox 52.2.0.
Compare:

$ curl --silent -o /dev/null --dump-header - \
  http://ftp.debian.org/debian/doc/bug-log-access.txt \
  | grep Content-Type
X-Content-Type-Options: nosniff
Content-Type: text/plain; charset=utf-8

$ curl --silent -o /dev/null --dump-header - \
  https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt \
  | grep -i Content-Type
X-Content-Type-Options: nosniff
Content-Type: text/plain

For what it's worth, I agree that declaring the correct charset in HTTP
metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK SPACE
(aka the "byte-order mark") in the file content.

Regards,
S

Bug#835394: Info received ([pkg-gnupg-maint] Bug#835394: gnupg-agent: gpg agent refusing ssh agent work)

[Raphaël]

Running the agent --debug 4096 --debug-level guru --daemon --min-passphrase-len 0

$ ssh my-vm

gpg-agent[29336]: ssh handler 0x for fd 8 started
gpg-agent[29336]: ssh request handler for request_identities (11) started
gpg-agent[29336]: ssh request handler for request_identities (11) ready
gpg-agent[29336]: ssh request handler for sign_request (13) started
gpg-agent[29336]: DBG: agent_get_cache 
'4B9A' (mode 4) ...
gpg-agent[29336]: DBG: ... miss
gpg-agent[29336]: starting a new PIN Entry
gpg-agent[29336]: DBG: connection to PIN entry established
** Message: Remote error from secret service: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was 
not provided by any .service files
Failed to lookup password for key s/4B9A 
with secret service: The name org.freedesktop.secrets was not provided by any 
.service files
 here ssh key PINentry popup => just enter (no passphrase) 
gpg-agent[29336]: DBG: error calling pinentry: No passphrase given 
gpg-agent[29336]: failed to unprotect the secret key: No passphrase given
gpg-agent[29336]: failed to read the secret key


I guess there may be something "special" against passphrase-less ssh keys, but
couldn't find any documentation/hints about this.

Bug#865013: [Pkg-utopia-maintainers] Bug#865013: network-manager-gnome: Consistent segfault when connecting to WPA2 network

[Michael Biebl]

Fwiw, I'm not able to reproduce the crash

I can create new wifi (WPA2-PSK) connections without problems.

What kind of connection do you create?
The backtrace suggests that it might be something WPA2-EAP

Would probably be a good idea if you file this bug upstream at
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager




signature.asc
Description: OpenPGP digital signature

Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)

[Rick Thomas]

Oooops!

syslog is mode 600, and I wasn’t root when I created the cpio archive.

Here is is



syslog.gz
Description: GNU Zip compressed data


Sorry!
Rick

On Jun 24, 2017, at 2:23 PM, Cyril Brulebois  wrote:

> Hi again,
> 
> Rick Thomas  (2017-06-24):
>> I did attach all the log files to one of my messages — as a gzipped cpio 
>> archive.
>> 
>> The log files are at:
>>   
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77
>> 
>> The message itself with the attachment is at:
>>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77
>> 
>> Let me know if you would like me to perform further tests.
> 
> There's no syslog in there?
> 
>$ zcat installer-logs.cpio.gz | cpio -it | sort
>127 blocks
>.
>cdebconf
>hardware-summary
>lsb-release
>status
> 
> 
> KiBi.

Bug#865816: calibre: The latest release of calibre is 3.1.1. could we get an update

[dmm]

Package: calibre
Version: 2.75.1+dfsg-1
Severity: wishlist

Dear Maintainer,

The latest release of calibre is 3.1.1.
https://calibre-ebook.com/download_linux

Is there a reason why the unstable package is still 2.75?
I run the latest version on my windows machine, but the calibre-server
from my linux server. Fortunately this still works, but I worry I might
hit some inconsistancy in the database format etc.


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

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

Versions of packages calibre depends on:
ii  calibre-bin  2.75.1+dfsg-1
ii  fonts-liberation 1:1.07.4-2
ii  imagemagick  8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11
ii  libjs-mathjax2.7.0-2
ii  poppler-utils0.48.0-2
ii  python-apsw  3.16.2-r1-2
ii  python-beautifulsoup 3.2.1-1
ii  python-chardet   3.0.4-1
ii  python-cherrypy3 3.5.0-2
ii  python-cssselect 1.0.1-1
ii  python-cssutils  1.0-4.1
ii  python-dateutil  2.5.3-2
ii  python-dbus  1.2.4-1+b1
ii  python-feedparser5.1.3-3
ii  python-lxml  3.8.0-1
ii  python-markdown  2.6.8-1
ii  python-mechanize 1:0.2.5-3
ii  python-netifaces 0.10.4-0.1+b2
ii  python-pil   4.0.0-4
ii  python-pkg-resources 36.0.1-1
ii  python-pyparsing 2.1.10+dfsg1-1
ii  python-pyqt5 5.7+dfsg-5
ii  python-pyqt5.qtsvg   5.7+dfsg-5
ii  python-pyqt5.qtwebkit5.7+dfsg-5
ii  python-routes2.3.1-2
ii  python2.72.7.13-2
ii  xdg-utils1.1.1-1

Versions of packages calibre recommends:
ii  python-dnspython  1.15.0-1

calibre suggests no packages.

-- no debconf information

Bug#865577: cloud-init FTBFS: recipe for target 'pep8' failed

[Joonas Kylmälä]

This bug has been fixed in the upstream commit
.

Bug#865815: kernel-package missing in debian9

[jydcome]

Package: kernel-package Version: unknown

kernel-package missing in debian9 repo, so i cant install it & run make-kpkg to 
make a new kernel deb.

Debian stretch amd64, newly installed not upgrade.

Regards.

Bug#865649: cups HTTPS issues -- Lack of SHA-2 certificate, weak TLSv1.0 crypto)

[of....@protonmail.com]

Was TLSv.1.0 already disabled back in July 2015 and this is a regression or is 
it time now to disable it permanently and completely in the default config? See 
below a prior changelog.
cups (2.1~b1-1)
* New 2.1~b1 release
disable TLS/1.0 support.
-- Didier Raboud  Thu, 09 Jul 2015

Bug#855829: Where is the build log for django-tables2?

[Adrian Bunk]

On Fri, Jun 23, 2017 at 06:22:26PM +0100, Neil Williams wrote:
> severity 855829 normal
> retitle 855829 New upstream release needed in experimental for testing with 
> django 1.11
> tag 855829 - buster
> tag 855829 - sid
> thanks
> 
> Adrian - where is the FTBFS build log to justify increasing the
> severity of 855829 to RC?
> 
> I reported a different bug, nothing at all to do with building the package.
> 
> Please file a FTBFS bug explicitly and don't co-opt a different bug
> which relates to runtime issues, not build time.

Sorry for that, I've now reported the FTBFS as #865814.

cu
Adrian

-- 

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

Bug#865714: calibre: please package calibre 3 (patch included)

[Norbert Preining]

Hi Martin,

> Nice, thank you! I already had 3.0 staged in git with a lot of the same
> changes, but 3.0 didn't build. (See #865018). I'm glad that this got fixed in
> 3.1 again. Sorry for the duplicate work!

I was checking the git repo for changes, but you seem to haven't pushed them 
out.
No problem at all, if it helped a bit I'm happy.

> But you have some nice changes there, like using the system regex and
> coffee-script, and the README typo fix. I committed them separately.

All more or less lintian warnings/errors I wanted to get rid of.

> I'd like to drop cdbs, but I didn't get around/bother to actually convert
> debian/rules for it, so this part can't be applied.

Interestingly lintian told me that cdbs is not used and should be removed...?!?!

Thanks a lot and all the best!!!

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#865814: django-tables FTBFS with Django 1.11

[Adrian Bunk]

Source: django-tables
Version: 1.2.0-1
Severity: serious
Tags: buster sid

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} /usr/bin/py.test"
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 /usr/bin/py.test
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
django settings: tests.app.settings (from ini file)
rootdir: /build/1st/django-tables-1.2.0, inifile: tox.ini
plugins: django-2.9.1
collected 178 items

tests/test_config.py ..
tests/test_core.py .
tests/test_models.py 
tests/test_rows.py ..
tests/test_templates.py 
tests/test_templatetags.py .
tests/test_utils.py 
tests/test_views.py ...
tests/columns/test_booleancolumn.py ...
tests/columns/test_checkboxcolumn.py .
tests/columns/test_datecolumn.py 
tests/columns/test_datetimecolumn.py 
tests/columns/test_emailcolumn.py 
tests/columns/test_filecolumn.py 
tests/columns/test_general.py ..
tests/columns/test_linkcolumn.py 
tests/columns/test_templatecolumn.py F
tests/columns/test_timecolumn.py ..
tests/columns/test_urlcolumn.py 

=== FAILURES ===
_ test_should_handle_context_on_table __

def test_should_handle_context_on_table():
class TestTable(tables.Table):
col_code = tables.TemplateColumn(template_code='code:{{ record.col 
}}{{ STATIC_URL }}')
col_name = 
tables.TemplateColumn(template_name='test_template_column.html')

table = TestTable([{'col': 'brad'}])
assert table.rows[0].get_cell('col_code') == 'code:brad'
>   assert table.rows[0].get_cell('col_name') == 'name:brad'

tests/columns/test_templatecolumn.py:17: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
django_tables2/rows.py:150: in get_cell
return self._call_render(bound_column, value)
django_tables2/rows.py:170: in _call_render
return bound_column.render(**kwargs)
django_tables2/columns/templatecolumn.py:71: in render
return template.render(context)
/usr/lib/python2.7/dist-packages/django/template/backends/django.py:64: in 
render
context = make_context(context, request, 
autoescape=self.backend.engine.autoescape)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

context = [{'False': False, 'None': None, 'True': True}], request = None
kwargs = {'autoescape': True}

def make_context(context, request=None, **kwargs):
"""
Create a suitable Context from a plain dict and optionally an 
HttpRequest.
"""
if context is not None and not isinstance(context, dict):
>   raise TypeError('context must be a dict rather than %s.' % 
> context.__class__.__name__)
E   TypeError: context must be a dict rather than Context.

/usr/lib/python2.7/dist-packages/django/template/context.py:287: TypeError
= 1 failed, 177 passed in 2.44 seconds =
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
/usr/bin/py.test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} /usr/bin/py.test returned exit code 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#823508: Useless in Debian

[Michael Crusoe]

The khmer package latest upstream version now uses this theme. I would be
happy to take over maintenance.

On Thu, 5 May 2016 09:29:14 -0400 David =?iso-8859-1?Q?Pr=E9vot?= <
taf...@debian.org> wrote:
> Package: python-guzzle-sphinx-theme
> Version: 0.7.10-1
> Severity: serious
>
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>   from testing. ]
>
> I packaged python-guzzle-sphinx-theme in order to build php-guzzle-doc,
> but php-guzzle is going away, see #821698. There is a priori little
> point in shipping python-guzzle-sphinx-theme in any Debian stable
> release anymore.
>
> I intend to follow up with an RM request once php-guzzle is gone, unless
> anyone objects (but feel free to beat me to it).
>
> Regards
>
> David

Bug#865813: jumpnbump: Fix occasional parallel FTBFS

[Adrian Bunk]

Source: jumpnbump
Version: 1.60-1
Severity: serious
Tags: patch

debhelper compat 10 defaults to parallel building,
which exposed the bug fixed in the attached patch
that resulted in "cd modify && make" running up to
three times in prallel.

Depending on the timing this does sometimes FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=jumpnbump&arch=mips&ver=1.60-1&stamp=1498322671&raw=0

...
make -C modify
...
make -C modify
...
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
jnbunpack.o jnbunpack.c
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../gobpack gobpack.o -Wl,-z,relro 
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbpack jnbpack.o -Wl,-z,relro 
jnbunpack.c: In function 'main':
jnbunpack.c:65:5: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
 read(fd, &num_entries, 4);
 ^
jnbunpack.c:70:5: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
 read(fd, datafile, num_entries * sizeof(DirEntry));
 ^~
jnbunpack.c:100:2: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
  read(fd, buf, datafile[i].size);
  ^~~
jnbunpack.c:101:2: warning: ignoring return value of 'write', declared with 
attribute warn_unused_result [-Wunused-result]
  write(outfd, buf, datafile[i].size);
  ^~~
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
make -C modify
make[3]: Entering directory '/«PKGBUILDDIR»/modify'
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
jnbunpack.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:21: recipe for target '../jnbunpack' failed
make[3]: *** [../jnbunpack] Error 1
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
Makefile:36: recipe for target 'jnbunpack' failed
make[2]: *** [jnbunpack] Error 2
make[2]: *** Waiting for unfinished jobs
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
make[2]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j2 PREFIX=/usr BINDIR=/usr/games 
GAMEDATADIR=/usr/share/games returned exit code 2
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
Description: Fix occasional parallel FTBFS
 "cd modify && make" was running up to three times in parallel.
Author: Adrian Bunk 

--- jumpnbump-1.51+dfsg1.orig/Makefile
+++ jumpnbump-1.51+dfsg1/Makefile
@@ -12,14 +12,16 @@ BINARIES = $(TARGET) jumpnbump.svgalib j
jnbmenu.tcl
 PREFIX ?= /usr/local
 
-.PHONY: data
+.PHONY: data modify
 
 all: $(BINARIES)
 
 $(SDL_TARGET): globals.h
cd sdl && make
 
-$(MODIFY_TARGET): globals.h
+$(MODIFY_TARGET): modify
+
+modify: globals.h
cd modify && make
 
 $(TARGET): $(OBJS) $(SDL

Bug#865812: reportbug --from-buildd shouldn't include system information

[Adrian Bunk]

Package: reportbug
Version: 7.1.7
Severity: normal

When using --from-buildd, there is no point in including
the information from the system where reportbug is running.

Bug#865810: libjson-webtoken-perl FTBFS: test failures

[gregor herrmann]

Control: forcemerge 865563 -1
Control: affects 865563 + libjson-webtoken-perl
Control: retitle 865563 libmodule-build-perl: Issue with missing dot-in-inc; 
causes multiple build failures

On Sun, 25 Jun 2017 01:43:37 +0300, Adrian Bunk wrote:

> Source: libjson-webtoken-perl
> Version: 0.10-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes libjson-webtoken-perl FTBFS:

Yeah, that's #865563 again; which is a problem in Module::Build and
affects dozens (or hundreds) of packages.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: STS: Continental


signature.asc
Description: Digital Signature

Bug#865810: libjson-webtoken-perl FTBFS: test failures

[Adrian Bunk]

Source: libjson-webtoken-perl
Version: 0.10-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes libjson-webtoken-perl FTBFS:

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

...
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/01_basic.t 
line 3.
BEGIN failed--compilation aborted at t/01_basic.t line 3.
t/01_basic.t ... 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/02_rsa.t 
line 3.
BEGIN failed--compilation aborted at t/02_rsa.t line 3.
t/02_rsa.t . 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
t/03_add_signing_algorithm.t line 30.
BEGIN failed--compilation aborted at t/03_add_signing_algorithm.t line 30.
t/03_add_signing_algorithm.t ... 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
...
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t line 3.
BEGIN failed--compilation aborted at 
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t line 3.
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t  
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 

Test Summary Report
---
t/01_basic.t (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/02_rsa.t   (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/03_add_signing_algorithm.t (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t  (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=9, Tests=24,  1 wallclock secs ( 0.06 usr  0.02 sys +  0.42 cusr  0.09 
csys =  0.59 CPU)
Result: FAIL
Failed 4/9 test programs. 0/24 subtests failed.
/usr/share/cdbs/1/class/perl-build.mk:84: recipe for target 
'debian/stamp-perl-check' failed
make: *** [debian/stamp-perl-check] Error 2

Bug#865809: Very large e-mail messages with no attachments cause bugreport.cgi to fail

[Don Armstrong]

Package: debbugs
Severity: minor

Very large e-mail messages (for example, the report in #819083) can
cause bugreport.cgi to hit the apache time limites for CGI processes.

bugreport.cgi should just not display incredibly large messages (or
otherwise cut them down to a reasonable size) if it's displaying the
entire log.

-- 
Don Armstrong  https://www.donarmstrong.com

I cannot find rest
Because I am powerless
To amend a broken world.
 -- Guy Gavriel Kay _Under Heaven_ p295

Bug#862304: muh stability

[Андрей]

Yeah, keep dreaming. How do you think this crap got into Stable in the first 
place? They just don't give a fuck, that's how. Good job freezing with a broken 
primary GUI toolkit, geniuses. On the positive side, I won a bet.

Bug#865808: golang-github-urfave-cli FTBFS: FAIL: TestFlagsFromEnv

[Adrian Bunk]

Source: golang-github-urfave-cli
Version: 1.19.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-urfave-cli FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-urfave-cli.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-urfave-cli.html

...
=== RUN   TestFlagsFromEnv
--- FAIL: TestFlagsFromEnv (0.00s)
flag_test.go:102: expected error could not parse 1.2,2 as int slice 
value for flag seconds: strconv.ParseInt: parsing "1.2": invalid syntax, got 
error could not parse 1.2,2 as int slice value for flag seconds: strconv.Atoi: 
parsing "1.2": invalid syntax
flag_test.go:102: expected error could not parse foobar as int slice 
value for flag seconds: strconv.ParseInt: parsing "foobar": invalid syntax, got 
error could not parse foobar as int slice value for flag seconds: strconv.Atoi: 
parsing "foobar": invalid syntax
...

Bug#865795: radvd blocks when started over ssh

[Geert Stappers]

Control: tags -1 confirmed upstream


Hi Daniel,

Thanks for reporting. The bug  _and_ the workaround.
Karma bonus points for the git bisect.

We shall see what upstream says about it.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#865807: golang-github-coreos-go-oidc FTBFS: FAIL github.com/coreos/go-oidc/http

[Adrian Bunk]

Source: golang-github-coreos-go-oidc
Version: 0.0~git20160926.0.16c5ecc-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-coreos-go-oidc FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-coreos-go-oidc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-coreos-go-oidc.html

...
url_test.go:26: err: url is empty
url_test.go:26: err: url host is empty
url_test.go:26: err: url scheme is empty
url_test.go:26: err: url scheme is empty
FAIL
exit status 1
FAILgithub.com/coreos/go-oidc/http  0.013s
...

Bug#865290: RM: get-iplayer -- ROM; unsuitable for stable releases

[Scott Kitterman]

On June 24, 2017 4:03:05 PM EDT, Jack Underwood 
 wrote:
>My two cents:
>
>1) People can still install from unstable, so it does still provide a
>purpose, so long as the package stays up-to date to follow changes.
>
>2) The flash plugin also seems quite unstable and yet we have that in
>stable, I have lost track of how many times I have gone into firefox
>and seen the error message that it has blocked flash because of
>security, and no update available from the debian package, sometimesI
>have waited weeks for the update to make its way through to debian...

The current maintainer has decided not to maintain the package anymore and 
believes it is better to remove it.

Given the fast moving target it support, I agree that unmaintained, it is 
better to remove it.

Are you volunteering to take over package maintenence?

Scott K

Bug#865806: gnome-dictionary FTBFS: gdict-client-context.h:84:1: error: unknown type name 'GdictContext'

[Adrian Bunk]

Source: gnome-dictionary
Version: 3.20.0-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes gnome-dictionary FTBFS:

https://tests.reproducible-builds.org/debian/history/gnome-dictionary.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/gnome-dictionary.html

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict 
-DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" 
-DGNOMELOCALEDIR=\"/usr/share/locale\" 
-DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 
-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED 
-DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include
 /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
gdict-enum-types.c  -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-enum-types.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict 
-DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" 
-DGNOMELOCALEDIR=\"/usr/share/locale\" 
-DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 
-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED 
-DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include
 /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
gdict-utils.c  -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-utils.o
In file included from gdict-enum-types.c:6:0:
./gdict-client-context.h:84:1: error: unknown type name 'GdictContext'
 GdictContext *gdict_client_context_new  (const gchar
*hostname,
 ^~~~
Makefile:662: recipe for target 'libgdict_1_0_la-gdict-enum-types.lo' failed
make[4]: *** [libgdict_1_0_la-gdict-enum-types.lo] Error 1

Bug#865805: aiohttp-cors FTBFS: test failures

[Adrian Bunk]

Source: aiohttp-cors
Version: 0.5.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes aiohttp-cors FTBFS:

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

...
== 4 tests deselected ==
= 13 failed, 14 passed, 4 deselected, 4 error in 2.42 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/aiohttp-cors-0.5.0/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest 
-k-tests/integration/test_real_browser.py
dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25

Bug#865713: Declaring a charset of UTF-8 for policy files

[Russ Allbery]

Stéphane Blondon  writes:

> pabs added such configuration few days ago for Apache configuration:
> https://anonscm.debian.org/cgit/mirror/dsa-puppet.git/commit/?id=5bcf8431d6b375d211a29f9d2c338e4400332e1a

> The reason is a bad display in some browser for UTF-8 encoded txt file.
> The start of this thread:
> https://lists.debian.org/debian-www/2017/06/msg00068.html

Perfect, thank you!

Paul, does this resolve your original issue?  I'm a bit worried that it
might not because this was a little bit ago, and I think it should have
already been in place when you were testing.

-- 
Russ Allbery (r...@debian.org)   

Bug#865804: golang-github-ngaut-go-zookeeper FTBFS: local import "../zk" in non-local package

[Adrian Bunk]

Source: golang-github-ngaut-go-zookeeper
Version: 0.0~git20150813.0.9c3719e-1
Severity: serious

Some recent change in unstable makes golang-github-ngaut-go-zookeeper FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-ngaut-go-zookeeper.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-ngaut-go-zookeeper.html

...
dh build --buildsystem=golang --with=golang
   dh_testdir -O--buildsystem=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   dh_auto_configure -O--buildsystem=golang
   dh_auto_build -O--buildsystem=golang
go install -v -p 15 github.com/ngaut/go-zookeeper/examples 
github.com/ngaut/go-zookeeper/tracer github.com/ngaut/go-zookeeper/zk
src/github.com/ngaut/go-zookeeper/tracer/main.go:4:2: local import "../zk" in 
non-local package
dh_auto_build: go install -v -p 15 github.com/ngaut/go-zookeeper/examples 
github.com/ngaut/go-zookeeper/tracer github.com/ngaut/go-zookeeper/zk returned 
exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1

Bug#865713: Declaring a charset of UTF-8 for policy files

[Stéphane Blondon]

Le 24/06/2017 à 20:44, Russ Allbery a écrit :
> debian-www folks, is there a way to declare UTF-8 as the charset for all
> the *.txt files that originate from the debian-policy package and are
> served by www.debian.org?  I can guarantee that all the text files shipped
> as part of the Policy package will be valid UTF-8.
> 

pabs added such configuration few days ago for Apache configuration:
https://anonscm.debian.org/cgit/mirror/dsa-puppet.git/commit/?id=5bcf8431d6b375d211a29f9d2c338e4400332e1a


The reason is a bad display in some browser for UTF-8 encoded txt file.
The start of this thread:
https://lists.debian.org/debian-www/2017/06/msg00068.html

-- 
Stéphane



signature.asc
Description: OpenPGP digital signature

Bug#865803: libsoup2.4 FTBFS:

[Adrian Bunk]

Source: libsoup2.4
Version: 2.56.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes libsoup2.4 FTBFS:

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

...
PASS: misc-test 1 /misc/host
PASS: misc-test 2 /misc/msg-reuse
PASS: misc-test 3 /misc/accept-language
FAIL: misc-test 4 /misc/aliases
PASS: misc-test 5 /misc/idle-on-dispose
PASS: misc-test 6 /misc/pause-abort
PASS: misc-test 7 /misc/pause-cancel
PASS: misc-test 8 /misc/callback-unref/msg
PASS: misc-test 9 /misc/callback-unref/req
PASS: misc-test 10 /misc/early-abort/msg
PASS: misc-test 11 /misc/early-abort/req
PASS: misc-test 12 /misc/cancel-while-reading/msg
PASS: misc-test 13 /misc/cancel-while-reading/req/immediate
PASS: misc-test 14 /misc/cancel-while-reading/req/delayed
PASS: misc-test 15 /misc/cancel-while-reading/req/preemptive
PASS: misc-test 16 /misc/stealing/async
PASS: misc-test 17 /misc/stealing/sync
ERROR: misc-test - exited with status 1
...
PASS: server-test 1 /server/OPTIONS *
PASS: server-test 2 /server/aliases
PASS: server-test 3 /server/..-in-path
PASS: server-test 4 /server/ipv6
PASS: server-test 5 /server/multi/port
FAIL: server-test 6 /server/multi/scheme
PASS: server-test 7 /server/multi/family
PASS: server-test 8 /server/import/gsocket
PASS: server-test 9 /server/import/fd
PASS: server-test 10 /server/accept/iostream
PASS: server-test 11 /server/fail/404
PASS: server-test 12 /server/fail/500
PASS: server-test 13 /server/fail/500-pause
PASS: server-test 14 /server/early/stream
PASS: server-test 15 /server/early/respond
PASS: server-test 16 /server/early/multi
FAIL: server-test 17 /server/steal/CONNECT
ERROR: server-test - exited with status 1
...
PASS: ssl-test 1 /ssl/session-properties
FAIL: ssl-test 2 /ssl/tls-interaction
FAIL: ssl-test 3 /ssl/message-properties/async
FAIL: ssl-test 4 /ssl/message-properties/sync
FAIL: ssl-test 5 /ssl/strictness/async/strict/with-ca
PASS: ssl-test 6 /ssl/strictness/async/strict/without-ca
FAIL: ssl-test 7 /ssl/strictness/async/non-strict/with-ca
PASS: ssl-test 8 /ssl/strictness/async/non-strict/without-ca
FAIL: ssl-test 9 /ssl/strictness/sync/strict/with-ca
PASS: ssl-test 10 /ssl/strictness/sync/strict/without-ca
FAIL: ssl-test 11 /ssl/strictness/sync/non-strict/with-ca
PASS: ssl-test 12 /ssl/strictness/sync/non-strict/without-ca
ERROR: ssl-test - exited with status 1
...
==
   libsoup 2.56.0: tests/test-suite.log
==

# TOTAL: 526
# PASS:  461
# SKIP:  50
# XFAIL: 0
# FAIL:  10
# XPASS: 0
# ERROR: 5
...

Bug#865552: libbpp-phyl FTBFS with test failures

[Julien Yann Dutheil]

Dear Andreas,

Please find attached a patch that sets the timeout to 1s (default was
1500). Hope this improves things...

Best,

Julien.

On Fri, Jun 23, 2017 at 9:43 PM, Andreas Tille  wrote:

> Hi Julien,
>
> On Fri, Jun 23, 2017 at 09:02:30PM +0200, Julien Yann Dutheil wrote:
> > This is most strange indeed. The errors are all "time out" errors on unit
> > tests which take the longest time (several min or so). Looks like some
> > issues with the default value for the timeout setting in CTest... I would
> > suggest to simply skip the unit tests by running "cmake
> > -DBUILD_TESTING=FALSE ." .  Does this solve the problem?
>
> Hmmm, this would most probably lead to successfully built packages but I
> would prefer spending some additional thoughts on this.  It would
> explain the issue why the package has built before but does not any more
> without any visible change on "weak" architectures.  I could imagine
> that after stretch release the run on the build servers increased and
> that possibly parallel builds are happening which lead to performance
> loss for single packages.
>
> Do you see any chance to increase the timeout settings by one order of
> magnitude to test this hypothesis?
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE
commit 1d8fb92514f7cacfcf158de80b99cc13483437e7
Author: Julien Y. Dutheil 
Date:   Sat Jun 24 23:41:39 2017 +0200

Added longer timeout for tests.

diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt
index 206cef39..5e8cf244 100644
--- a/test/CMakeLists.txt
+++ b/test/CMakeLists.txt
@@ -21,4 +21,6 @@ foreach (test_cpp_file ${test_cpp_files})
 WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
 COMMAND ${test_name}
 )
+  set_tests_properties (${test_name} PROPERTIES TIMEOUT 1)
 endforeach (test_cpp_file)
+

Bug#865791: meld: Traceback error in diffmap.py

[Jason Crain]

Control: tags -1 + fixed-upstream patch upstream

On Sat, Jun 24, 2017 at 04:25:50PM -0500, Karl Schmidt wrote:
> On 06/24/2017 03:38 PM, Jason Crain wrote:
> > You could try to see if the change in this commit fixes it:
> > https://git.gnome.org/browse/meld/commit/?id=e7a35ad195688e6e376cc6187b4728ba36c87882
> > 
> 
> Yes - this patch fixes it. Thanks..

Bug#865802: django-filter FTBFS with Django 1.11

[Adrian Bunk]

Source: django-filter
Version: 0.13.0-1
Severity: serious

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} ./runtests.py"
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 ./runtests.py
Traceback (most recent call last):
  File "./runtests.py", line 14, in 
runtests()
  File "./runtests.py", line 10, in runtests
execute_from_command_line(argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 363, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 337, in execute
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 85, in 
populate
app_config = AppConfig.create(entry)
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 94, in 
create
module = import_module(entry)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/build/1st/django-filter-0.13.0/django_filters/__init__.py", line 3, in 

from .filterset import FilterSet
  File "/build/1st/django-filter-0.13.0/django_filters/filterset.py", line 19, 
in 
from .filters import (Filter, CharFilter, BooleanFilter, BaseInFilter, 
BaseRangeFilter,
  File "/build/1st/django-filter-0.13.0/django_filters/filters.py", line 16, in 

from .fields import (
  File "/build/1st/django-filter-0.13.0/django_filters/fields.py", line 14, in 

from .widgets import RangeWidget, LookupTypeWidget, CSVWidget
  File "/build/1st/django-filter-0.13.0/django_filters/widgets.py", line 13, in 

from django.forms.widgets import flatatt
ImportError: cannot import name flatatt
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
./runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} ./runtests.py returned exit code 13
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#865801: ovirt-guest-agent FTBFS: recipe for target 'check-local' failed

[Adrian Bunk]

Source: ovirt-guest-agent
Version: 1.0.12.2.dfsg-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes ovirt-guest-agent FTBFS:

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

...
/usr/bin/pep8 --exclude="ovirt-guest-agent/setup.py" --filename '*.py,*.py.in' \
ovirt-guest-agent/CredServer.py ovirt-guest-agent/GuestAgentLinux2.py 
ovirt-guest-agent/GuestAgentWin32.py ovirt-guest-agent/LockActiveSession.py 
ovirt-guest-agent/OVirtAgentLogic.py ovirt-guest-agent/OVirtGuestService.py 
ovirt-guest-agent/VirtIoChannel.py ovirt-guest-agent/WinFile.py 
ovirt-guest-agent/ovirt-guest-agent.py ovirt-guest-agent/version.py 
ovirt-guest-agent/hooks.py tests/*.py
ovirt-guest-agent/GuestAgentLinux2.py:218:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:349:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:359:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:382:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:409:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:136:5: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:308:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:313:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:415:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:491:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:550:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:556:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:579:21: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:583:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:682:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:705:9: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:269:9: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:285:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:317:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:321:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:325:13: E722 do not use bare except'
ovirt-guest-agent/OVirtGuestService.py:127:9: E722 do not use bare except'
ovirt-guest-agent/VirtIoChannel.py:184:9: E722 do not use bare except'
ovirt-guest-agent/WinFile.py:60:9: E722 do not use bare except'
ovirt-guest-agent/WinFile.py:72:9: E722 do not use bare except'
ovirt-guest-agent/ovirt-guest-agent.py:140:9: E722 do not use bare except'
ovirt-guest-agent/ovirt-guest-agent.py:146:9: E722 do not use bare except'
Makefile:904: recipe for target 'check-local' failed
make[3]: *** [check-local] Error 1
make[3]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
Makefile:770: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
Makefile:482: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:24: recipe for target 'build' failed
make: *** [build] Error 2

Bug#865800: golang-github-smartystreets-go-aws-auth FTBFS: test failure

[Adrian Bunk]

Source: golang-github-smartystreets-go-aws-auth
Version: 0.0~git20160722.0.2043e6d-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-smartystreets-go-aws-auth 
FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-smartystreets-go-aws-auth.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-smartystreets-go-aws-auth.html

...

   dh_auto_test -O--buildsystem=golang
go test -v -p 16 github.com/smartystreets/go-aws-auth
=== RUN   TestIntegration

  Given real credentials from environment variables 
A request (with out-of-order query string) with to IAM should succeed 
(assuming Administrator Access policy) ⚠
A request to S3 should succeed ⚠
A request to EC2 should succeed ⚠
A request to SQS should succeed ⚠
A request to SES should succeed ⚠
A request to Route 53 should succeed ⚠
A request to SimpleDB should succeed ⚠
If S3Resource env variable is set 
  A URL-signed request to that S3 resource should succeed ⚠


0 total assertions (one or more sections skipped)

--- PASS: TestIntegration (0.01s)
=== RUN   TestSign

  Requests to services using Version 2 should be signed accordingly ✔✔


2 total assertions (one or more sections skipped)


  Requests to services using Version 3 should be signed accordingly ✔✔


4 total assertions (one or more sections skipped)


  Requests to services using Version 4 should be signed accordingly ✔✔✔


7 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 2 should be signed 
accordingly ✔✔


9 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 3 should be signed 
accordingly ✔✔


11 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 4 should be signed 
accordingly ✔✔✔


14 total assertions (one or more sections skipped)

--- PASS: TestSign (0.00s)
=== RUN   TestExpiration

  Credentials without an expiration can't expire ✔


15 total assertions (one or more sections skipped)


  Credentials that expire in 5 minutes aren't expired ✔


16 total assertions (one or more sections skipped)


  Credentials that expire in 1 minute are expired ✔


17 total assertions (one or more sections skipped)


  Credentials that expired 2 hours ago are expired ✔


18 total assertions (one or more sections skipped)

--- PASS: TestExpiration (0.00s)
=== RUN   TestCommonFunctions

  Service and region should be properly extracted from host strings 
✔✔


32 total assertions (one or more sections skipped)


  MD5 hashes should be properly computed and base-64 encoded ✔


33 total assertions (one or more sections skipped)


  SHA-256 hashes should be properly hex-encoded (base 16) ✔


34 total assertions (one or more sections skipped)


  Given a key and contents 
HMAC-SHA256 should be properly computed ✔
HMAC-SHA1 should be properly computed ✔


36 total assertions (one or more sections skipped)


  Strings should be properly concatenated with a delimiter ✔✔✔


39 total assertions (one or more sections skipped)


  URI components should be properly encoded ✔✔✔


42 total assertions (one or more sections skipped)


  URI query strings should be properly encoded ✔


43 total assertions (one or more sections skipped)

--- PASS: TestCommonFunctions (0.00s)
=== RUN   TestSignatureS3

  Given a GET request to Amazon S3 
The request should be prepared with a Date header ✔
The CanonicalizedAmzHeaders should be built properly ✔
The CanonicalizedResource should be built properly ✔
The string to sign should be correct ✔
The final signature string should be exactly correct ✔


48 total assertions (one or more sections skipped)


  Given a GET request for a resource on S3 for query string authentication 
The string to sign should be correct ✔
The signature of string to sign should be correct ✔
The finished signed URL should be correct ✔


51 total assertions (one or more sections skipped)

--- PASS: TestSignatureS3 (0.00s)
=== RUN   TestS3STSRequestPreparer

  Given a plain request with no custom headers 
And a set of credentials with an STS token 
  It should include an X-Amz-Security-Token when the request is signed ✔✔


53 total assertions (one or more sections skipped)

--- PASS: TestS3STSRequestPreparer (0.00s)
=== RUN   TestCanonical
--- PASS: TestCanonical (0.00s)
=== RUN   TestSignature2

  Given bogus credentials 
Given a plain request that is unprepared 
  The request should be prepared to be signed ✔
Given a prepared, but unsigned, request 
  The canonical query string should be correct ✔
  The absolute path should be extracted correctly ✔
  The string to sign should be well-formed ✔
  The resulting signature should be correct ✔
  The final signed request should be correctly formed ✔


59 total assertions (one o

Bug#865799: python-django-openstack-auth FTBFS with Django 1.11

[Adrian Bunk]

Source: python-django-openstack-auth
Version: 2.4.1-2
Severity: serious
Tags: buster sid

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

...
set -e ; for pyversion in 2.7 3.5 ; do \
NOSE_WITH_OPENSTACK=1 \
NOSE_OPENSTACK_COLOR=1 \
NOSE_OPENSTACK_RED=0.05 \
NOSE_OPENSTACK_YELLOW=0.025 \
NOSE_OPENSTACK_SHOW_ELAPSED=1 \
PYTHONPATH=. python$pyversion openstack_auth/tests/run_tests.py ; \
done
No handlers could be found for logger "openstack_auth.utils"
.EE.
==
ERROR: test_websso_redirect_by_idp (tests.OpenStackAuthTestsWebSSO)
--
Traceback (most recent call last):
  File 
"/build/1st/python-django-openstack-auth-2.4.1/openstack_auth/tests/tests.py", 
line 916, in test_websso_redirect_by_idp
target_status_code=404)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 315, 
in assertRedirects
% (url, domain)
ValueError: The test client is unable to fetch remote URLs (got 
http://localhost:5000/v3/auth/OS-FEDERATION/identity_providers/158fb42243b744d1acc3300c5ab0ecc6/protocols/oidc/websso?origin=http://testserver/auth/websso/).
 If the host is served by Django, add 'localhost' to ALLOWED_HOSTS. Otherwise, 
use assertRedirects(..., fetch_redirect_response=False).

==
ERROR: test_websso_redirect_by_protocol (tests.OpenStackAuthTestsWebSSO)
--
Traceback (most recent call last):
  File 
"/build/1st/python-django-openstack-auth-2.4.1/openstack_auth/tests/tests.py", 
line 899, in test_websso_redirect_by_protocol
target_status_code=404)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 315, 
in assertRedirects
% (url, domain)
ValueError: The test client is unable to fetch remote URLs (got 
http://localhost:5000/v3/auth/OS-FEDERATION/websso/oidc?origin=http://testserver/auth/websso/).
 If the host is served by Django, add 'localhost' to ALLOWED_HOSTS. Otherwise, 
use assertRedirects(..., fetch_redirect_response=False).

--
Ran 52 tests in 12.500s

FAILED (errors=2)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2

Bug#865798: golang-github-shopify-sarama FTBFS: test failures

[Adrian Bunk]

Source: golang-github-shopify-sarama
Version: 1.9.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-shopify-sarama FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-shopify-sarama.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-shopify-sarama.html

...
--- FAIL: TestMessageEncoding (0.00s)
request_test.go:32: Encoding empty gzip failed
got  [132 99 80 148 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 0 
0 0 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0] 
want [97 79 149 90 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 9 
110 136 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0]
...
FAIL
exit status 1
FAILgithub.com/Shopify/sarama   4.201s
...

Bug#859652: mutt: Crashes when trying to display (or fetch) a specific S/MIME-signed message

[Antonio Radici]

Tags: moreinfo

On Wed, Apr 05, 2017 at 04:42:51PM +0200, Axel Beckert wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: important
> Tags: security
> 
> Dear Maintainer,
> 
> for the first time since upgrading to Stretch a few months ago, mutt
> crashed when I pressed enter on mail -- both when viewing locally as
> well as via IMAP). Starting up mutt again and trying to display that
> mail again crashes again, i.e. it seems to be reproducible.
> 
> Here's a backtrace made from the coredump:

Hi Axel,
could you send the mail in private assuming that this is still reproducible in
1.8.3+neomutt20170609-1? thanks!

Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)

[Cyril Brulebois]

Hi again,

Rick Thomas  (2017-06-24):
> I did attach all the log files to one of my messages — as a gzipped cpio 
> archive.
> 
> The log files are at:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77
> 
> The message itself with the attachment is at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77
> 
> Let me know if you would like me to perform further tests.

There's no syslog in there?

$ zcat installer-logs.cpio.gz | cpio -it | sort
127 blocks
.
cdebconf
hardware-summary
lsb-release
status


KiBi.


signature.asc
Description: Digital signature

Bug#865795: radvd blocks when started over ssh

[Daniel Reichelt]

> ssh returns immediately as expected when I run one of these:

Of course, when I tested the redirection to /dev/null happened on the
router, I forgot to type the quotes:

ssh router "radvd -u radvd -p /var/run/radvd/radvd.pid >/dev/null"
ssh router "radvd -u radvd -p /var/run/radvd/radvd.pid -d3"




signature.asc
Description: OpenPGP digital signature

Bug#865797: signond FTBFS: symbol changes

[Adrian Bunk]

Source: signond
Version: 8.59-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes signond FTBFS:

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

...
   dh_makeshlibs -O-Bbuild/qt5 -O--parallel
dpkg-gensymbols: warning: debian/libsignon-qt5-1/DEBIAN/symbols doesn't match 
completely debian/libsignon-qt5-1.symbols
--- debian/libsignon-qt5-1.symbols (libsignon-qt5-1_8.59-1_amd64)
+++ dpkg-gensymbolsMvafsq   2018-07-26 21:09:03.368772123 -1200
@@ -56,8 +56,8 @@
  _ZN6SignOn12IdentityInfoD1Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoD2Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoaSERKS0_@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 
8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 
8.57+20150423
  _ZN6SignOn5ErrorD0Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD1Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD2Ev@Base 8.57+20150423
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libsignon-plugins-common1/DEBIAN/symbols 
doesn't match completely debian/libsignon-plugins-common1.symbols
--- debian/libsignon-plugins-common1.symbols 
(libsignon-plugins-common1_8.59-1_amd64)
+++ dpkg-gensymbolsVmmzQ3   2018-07-26 21:09:03.756772123 -1200
@@ -1,9 +1,9 @@
 libsignon-plugins-common.so.1 libsignon-plugins-common1 #MINVER#
  (optional=templinst|arch=mips64el 
mipsel)_Z17qRegisterMetaTypeI13QDBusArgumentEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
  _Z23expandDBusArgumentValueRK8QVariantPb@Base 8.57+20150423
- 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE8DestructEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE9ConstructEPvPKv@Base
 8.57+20150423
  (optional=templinst)_ZN4QMapI7QString8QVariantE13detach_helperEv@Base 
8.57+20150423
@@ -30,6 +30,8 @@
  
(optional=templinst)_ZN7QVectorI10QByteArrayE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base
 8.57+20150423
  (optional=templinst)_ZN7QVectorI10QByteArrayE6appendERKS0_@Base 8.57+20150423
  (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 
8.57+20150423
+ _ZN9QtPrivate16StreamStateSaverD1Ev@Base 8.59-1
+ _ZN9QtPrivate16StreamStateSaverD2Ev@Base 8.59-1
  _ZNK6SignOn13BlobIOHandler10metaObjectEv@Base 8.57+20150423
  
(optional=templinst)_ZNK8QMapNodeI7QString8QVariantE4copyEP8QMapDataIS0_S1_E@Base
 8.57+20150423
  _ZTVN6SignOn13BlobIOHandlerE@Base 8.57+20150423
@@ -37,16 +39,16 @@
  
(optional=templinst)_ZrsI7QString8QVariantER11QDataStreamS3_R4QMapIT_T0_E@Base 
8.57+20150423
 libsignon-plugins.so.1 libsignon-plugins-common1 #MINVER#
  
(optional=templinst)_Z17qRegisterMetaTypeIN6SignOn5ErrorEEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6CreateEPKv@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6DeleteEPv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6CreateEPKv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6DeleteEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE8DestructEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFuncti

Bug#865444: Bug#842614: dgit quilt messages ("o+d/p" is misleading)

[Sean Whitton]

Hello Ian, Felipe,

On Wed, Jun 21, 2017 at 02:55:02PM +0100, Ian Jackson wrote:
> > It also creates a git object corresponding to the .orig.tar.gz but
> > with debian/ copied from your .debian.tar.gz.  That's a "patches
> > unapplied" tree.  That git object is 5c8951c97cef58952a93.
> > dgit calls this "o+d/p" in some of the next output.  TBH maybe it
> > ought to be called "o+d".
> 
> Or maybe "unap'd" ?  Sean, do you have an opinion ?  Whatever we
> choose for this part of the message:
> 
>  |  dgit: base trees orig=d510ca798480f37fc567 o+d/p=5c8951c97cef58952a93
> 
> needs to have an abbrevation which will fit here:
> 
>  |  dgit: quilt differences: src:  ## orig ## gitignores:  == orig ==
>  |  dgit: quilt differences:  HEAD ## o+d/p   HEAD == o+d/p

o+d for patches-unapplied makes sense to me: if the patches are
unapplied, they exist only inside the 'd', so it's confusing to
additionally add 'p', which makes me think something has been done to
them inside 'd', or they've been applied.

Also, an unapplied tree is what you get in the simplest additive
operation between the 'o' and the 'd': putting the 'd' inside the
expanded 'o'.

(Ignoring the subtlety of 3.0 (quilt) permitting you to overwrite a
debian/ found in upstream's source, but that is rare.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#865446: dgit: want improved quilt failure messages

[Sean Whitton]

Hello Ian and Felipe,

Ian Jackson writes ("dgit: want improved quilt failure messages"):
> Control: clone -1 -2
> Control: retitle -2 want improved quilt failure messages
> Control: severity -2 normal
...
> Felipe complains that these messages are not very easy to understand.
> Indeed things are complicated.
> 
> Would it be helpful to provide a git diff rune in the output ?
> Eg
> 
>   |  dgit: --quilt=gbp specified, implying patches-unapplied git tree
>   |  dgit:  but git tree differs from orig in upstream files.
> + |  dgit:  This command shows the troublesome differences:
> + |  dgit:   git-diff d510ca798480f37fc567 -- . ':!.gitignore' ':!debian'

Yes, this would be very helpful.

Previously, I've flailed and used various crude heuristics to try to
find out what was wrong, with no involvement from dgit, instead just
applying my knowledge of dgit's fundamental operating assumptions.

Indeed, I had no idea that dgit creates a commit matching the orig.tar.
If I'd known that, I'd probably have been able to find the discrepancy
much faster!

On Wed, Jun 21, 2017 at 03:45:21PM +0100, Ian Jackson wrote:
> They are a compat representation of which trees differ from which
> other treeshow.  It's two triangular pictures; `==' means `trees
> either side of this are the same in this respect' and `##' means they
> differ.

This paragraph, and the previous e-mail you wrote in which you walked
Felipe through the output, should be in one of dgit's manpages.  It
would be a shame if this information were not shared widely.

Since it might be a long explanation, perhaps it should go in a separate
manpage.  I'd suggest the name dgit-output(7) (or maybe section 5), in
case we want to add other explanations of other detailed output later.

> This information is extremely useful to a dgit developer and I don't
> want to drop it.  I'd be open to changing `quilt differences' to
> something more obviously inclined to have the user ignore it.

On Wed, Jun 21, 2017 at 03:47:30PM +0100, Ian Jackson wrote:
> How about
> 
>   | dgit: experts' info: src:  ## orig ## gitignores:  == orig ==
>   | dgit: experts' info:  HEAD ## o+d/p   HEAD == o+d/p

I find "experts' info" a bit off-putting.

If the git diff commands are added in plain sight at the bottom of the
output, IMHO no additional experts-only warning is required.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#865796: ginkgocadx FTBFS with libdcmtk-dev 3.6.1~20170228-2

[Adrian Bunk]

Source: ginkgocadx
Version: 3.8.4-1
Severity: serious
Tags: buster sid

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

...
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz 
-I/usr/include/x86_64-linux-gnu -I/<>/cadxcore/CADxCore 
-I/<>/cadxcore -I/<>/cadxcore/vtk 
-I/<>/cadxcore/itk -I/<>/cadxcore/wx 
-I/<>/cadxcore/wx/VTK -I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/us
 r/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python2.7 
-I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/tcl 
-I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libpng12 
-I/usr/lib/gtk-2.0/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC  -std=c++11 -o 
CMakeFiles/CADxCore.dir/api/dicom/icustomassociation.cpp.o -c 
/<>/cadxcore/api/dicom/icustomassociation.cpp
[ 11%] Building CXX object 
cadxcore/CMakeFiles/CADxCore.dir/api/dicom/idicom.cpp.o
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz 
-I/usr/include/x86_64-linux-gnu -I/<>/cadxcore/CADxCore 
-I/<>/cadxcore -I/<>/cadxcore/vtk 
-I/<>/cadxcore/itk -I/<>/cadxcore/wx 
-I/<>/cadxcore/wx/VTK -I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/us
 r/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64

Bug#865795: radvd blocks when started over ssh

[Daniel Reichelt]

Package: radvd
Version: 1:2.15-2
Severity: normal

Hi Geert,

radvd shows some strange behavior when it's started over ssh: even in
daemon-mode, ssh would block indefinitely when you execute something
that would be executed by the init script as well:

ssh router "radvd -u radvd -p /var/run/radvd/radvd.pid"



ssh returns immediately as expected when I run one of these:

ssh router radvd -u radvd -p /var/run/radvd/radvd.pid >/dev/null
ssh router radvd -u radvd -p /var/run/radvd/radvd.pid -d3



git-bisect'ing revealed the culprit as 5294e6f, see [1].

I've also opened an upstream bug report at [2].

Cheers
Daniel



[1] 
https://github.com/reubenhwk/radvd/commit/5294e6fc0cc033a8dde64d51eefdc4c1f80e4244
[2] https://github.com/reubenhwk/radvd/issues/71


-- System Information:
Debian Release: 9.0
  APT prefers proposed-updates
  APT policy: (990, 'proposed-updates'), (990, 'stable'), (500, 'testing'), 
(98, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages radvd depends on:
ii  adduser   3.115
ii  libc6 2.24-11+deb9u1
ii  lsb-base  9.20161125

radvd recommends no packages.

radvd suggests no packages.

-- no debconf information


$ dpkg -l | grep sysvinit
ii  live-config-sysvinit  5.20170112
ii  sysvinit-core 2.88dsf-59
ii  sysvinit-utils2.88dsf-59

Bug#836442: midori: cannot open local HTML files

[Vincent Lefevre]

This no longer matters, but just in case users still use midori
or see this issue with other applications (because this broke
xdg-open too), this was indeed a bug in wine, now fixed:

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

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

Bug#865552: libbpp-phyl FTBFS with test failures

[Adrian Bunk]

On Sat, Jun 24, 2017 at 10:39:15PM +0200, Andreas Tille wrote:
>...
> Thanks for the explanation.  Do you have a better idea what might lead
> to the test failures of the d/rules file is changing only things that
> are happening after the tests are runned?
> 
> I admit I'm quite clueless and just ignoring test errors on the
> affected architectures would be really the last resort.

Looking closer through the build history, it seems my 2.3.1-1/2.3.1-2
comparison in the bug report was wrong and misleading, sorry for that.

I was looking only at some architectures, looking through all 
architectures the situation based on all 3 2.3.1-* builds is:

2.3.1-* always FTBFS on armel with tests 5,6,11 failing
2.3.1-* always FTBFS on armhf with tests 5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips with tests 4,5,6 failing
2.3.1-* always FTBFS on mipsel with tests 4,5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips64el with tests 5,6 and sometimes 11 failing
2.3.1-* sometimes FTBFS on ppc64el with test 6 failing
2.3.1-* sometimes FTBFS on sometimes with test 5,6,11 failing

So the problems sterted with 2.2.0-1 -> 2.3.1-1,
which actually makes sense.

All test failures are timeouts except the test 4 failures on
mips/mipsel, which are "Failed" and likely a separate issue.

> Kind regards
> 
>   Andreas.

cu
Adrian

-- 

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

Bug#865713: Please Start UTF-8 debian-policy Text Files with UTF-8 Signature

[Russ Allbery]

Russ Allbery  writes:

> I did a bit more research, and apparently this approach has become more
> blessed again.  I'm glad I looked it up!  As of Unicode 5.0, the
> standard explicitly recommended against doing this, but the latest
> version of the standard is moderately positive about it (although
> doesn't require it):

> In UTF-8, the BOM corresponds to the byte sequence  BF16>. Although there are never any questions of byte order with UTF-8
> text, this sequence can serve as signature for UTF-8 encoded text
> where the character set is unmarked.

> (although it does strongly discourage it if there's any other signaling
> method available).

Okay, I experimented with this, but unfortunately less displays the BOM at
the start of the file as a very ugly reverse-video  at the top of
the screen.

I think this is arguably a bug in less; this is a control character in a
sense, but the whole point is for it to be invisible, particularly when
it's the first character of the file.  Nonetheless, that's how less
currently behaves.  My feeling is that good display in less is a more
important use case for us than enabling this autorecognition in web
browsers (which will normally be viewing the HTML versions).

Given that, I think the right fix here is to fix the declared charset on
www.debian.org for these files.

-- 
Russ Allbery (r...@debian.org)   

Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)

[Rick Thomas]

On Jun 24, 2017, at 8:41 AM, Cyril Brulebois  wrote:

> Hi Rick,
> 
> Rick Thomas  (2017-06-23):
>> I re-installed u-boot on the uSDcard.  And with that, it booted up a
>> treat.
>> 
>> So somehow the u-boot binary on the uSDcard is getting clobbered in
>> the installation process.
> 
> Thanks for your follow-ups.
> 
> Any chance you could attach the installer's syslog file? It should be
> stored under /var/log/installer.
> 
> 
> KiBi.

Hi KiBi,

I did attach all the log files to one of my messages — as a gzipped cpio 
archive.

The log files are at:
   
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77

The message itself with the attachment is at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77

Let me know if you would like me to perform further tests.

Hope that helps!
Rick

Bug#865672: Scilab starts normally on sid with linux-image 4.11.6-1

[Nrbrtx]

Thank you!

Scilab starts normally on sid with linux-image 4.11.6-1.

dpkg -S /boot/vmlinuz-4.11.0-1-686-pae
linux-image-4.11.0-1-686-pae: /boot/vmlinuz-4.11.0-1-686-pae

$ apt-cache policy linux-image-4.11.0-1-686-pae
linux-image-4.11.0-1-686-pae:
  Installed: 4.11.6-1
  Candidate: 4.11.6-1
  Version table:
 *** 4.11.6-1 500
500 http://ftp.debian.org/debian sid/main i386 Packages
100 /var/lib/dpkg/status


I hope you backport this fix to all supported Debian versions.

Bug#865794: ITP: octave-divand -- n-dimensional interpolation for Octave

[Rafael Laboissière]

Package: wnpp
Severity: wishlist
Owner: Rafael Laboissiere 

* Package name: octave-divand
  Version : 1.1.2
  Upstream Author : Alexander Barth 
* URL : http://modb.oce.ulg.ac.be/mediawiki/index.php/Divand
* License : GPL-2+
  Programming Lang: Octave
  Description : n-dimensional interpolation for Octave

This package contains functions for performing multidimensional 
variational analysis in Octave, a scientific computation software. 
They allow the interpolation and analysis of observations on 
curvilinear orthogonal grids in an arbitrary high dimensional space 
by minimizing a cost function.


This package introduces an original functionality to the Octave 
software and will be maintained by the Debian Octave Group. 
A preliminary version of the package can be built from 
https://anonscm.debian.org/gitweb/?p=pkg-octave/octave-divand.git