Bug#902487: stretch-pu: package ruby-encryptor/3.0.0-1+deb9u1

[Manas Kashyap]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Fixes the rc bug #880276

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Bug#902486: RFS: node-macaddress/0.2.9-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: sunwea...@debian.org pkg-javascript-de...@lists.alioth.debian.org


Hi Mike, Debian JavaScript Team and mentors,


I am looking for a sponsor for team-maintained package "node-macaddress".

* Package name: node-macaddress
  Version : 0.2.9-1
  Upstream Author : Julian Fleischer
* URL : https://github.com/scravy/node-macaddress
* License : Expat
  Section : javascript


  It builds those binary packages:

node-macaddress - Get MAC addresses of host network interfaces in Node.js

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

  https://mentors.debian.net/package/node-macaddress


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-macaddress/node-macaddress_0.2.9-1.dsc


  Git packaging repository:

https://salsa.debian.org/js-team/node-macaddress.git


  Changes since the last upload:

 node-macaddress (0.2.9-1) unstable; urgency=medium
 .
   * New upstream release.
 + Fix a vulnerability to arbitrary code execution attack.
   * Bump Standards-Version to 4.1.4 (no changes needed).
   * d/rules: Use "dh_missing --fail-missing".
   * d/copyright: Refresh copyright information.

--
Regards,
Boyuan Yang

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

Bug#902485: stretch-pu: package ruby-encryptor/3.0.0-1

[Manas Kashyap]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Fixes the rc bug #880276

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash

Bug#902442: givaro: autopkgtest regression: /usr/bin/ld: cannot find tests/: File format not recognized

[Doug Torrance]

Control: tags -1 pending

On 06/26/2018 04:03 PM, Paul Gevers wrote:

Source: givaro
Version: 4.0.4-1
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

Since the upload of 4.0.4-1, your package fails its autopkgtest in
testing, with the error copied below.

Could you please investigate the situation and fix it. This regression
is causing your package to have to wait 13 extra days to migrate to testing.

[snip]

>

g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/ -lgivaro -lgmp
-lgmpxx -o test-modularmulprecomp
/usr/bin/ld: cannot find tests/: File format not recognized
collect2: error: ld returned 1 exit status
/tmp/autopkgtest-lxc.z23z52td/downtmp/build.rww/src/debian/tests/upstream-tests:190:
recipe for target 'test-modularmulprecomp' failed
make: *** [test-modularmulprecomp] Error 1
autopkgtest [15:44:00]: test upstream-tests: ---]


Thanks for the report!

I've fixed the issue (just a silly typo) in git [1].

I'm CC'ing the Sage list -- would anyone be able to sponsor?

Thanks!
Doug

[1] https://salsa.debian.org/science-team/givaro

Bug#901991: LogLevel vs log_level vs --log-level

[Harald Dunkel]

Done, see https://github.com/systemd/systemd/issues/9439 .

But I am not very optimistic about this.


Regards
Harri

Bug#902441: fflas-ffpack: autopkgtest regression: make: *** No rule to make target 'test-multifile'

[Doug Torrance]

Control: tags -1 pending

On 06/26/2018 03:55 PM, Paul Gevers wrote:

Source: fflas-ffpack
Version: 2.3.2-1
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

Since the upload of 2.3.2-1, your package fails its autopkgtest in
both unstable and testing, with the error copied below.

Could you please investigate the situation and fix it. This regression
is causing your package to have to wait 13 extra days to move to testing.

[snip]

>

make: *** No rule to make target 'test-multifile', needed by 'all'.  Stop.
autopkgtest [14:59:09]: test upstream-tests: ---]


Thanks for the report!

I've fixed this issue (and a couple other autopkgtest problems I 
discovered along the way) in git [1].


I'm CC'ing the Sage list -- would anyone be able to sponsor?

Thanks!
Doug

[1] https://salsa.debian.org/science-team/fflas-ffpack

Bug#902484: ITP: cowpatty - Brute-force dictionary attack against WPA-PSK

[Samuel Henrique]

Package: wnpp
Owner: "Samuel Henrique" 
Severity: wishlist
User: samuel...@debian.org
Usertags: gsoc2018-portkalipackages

* Package name: cowpatty
* URL : https://github.com/joswr1ght/cowpatty
* License : BSD-3-clause
  Programming Lang: C
  Description :
Implementation of an offline dictionary attack against WPA/WPA2 networks
using PSK-based authentication (e.g. WPA-Personal). Many enterprise
networks deploy PSK-based authentication mechanisms for WPA/WPA2 since it
is much easier than establishing the necessary RADIUS, supplicant and
certificate authority architecture needed for WPA-Enterprise
authentication. Cowpatty can implement an accelerated attack if a
precomputed PMK file is available for the SSID that is being assessed.

I intend to maintain this package under the pkg-security team.

-- 
Samuel Henrique 

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Christian PERRIER]

Quoting Cyril Brulebois (k...@debian.org):

> The use of “you” seems to be one of the common errors I mentioned above.
> We tend to avoid pointing fingers at users.
> 
> Hrm. Grepping across our packages' templates, I see a lot of “you”s so I
> might just be misremembering. Or maybe we've tried hard not to introduce
> new occurrences while not actively fixing pre-existing entries.


The use of "you" is, I would say, tolerated. What we tried to avoid
(at least when I was a PITA for people wanting to introduce new
templates) was what I called "personnalization" of the computer :
"your machine", for instance. Everything that seems to impply that the
machine being installed belongs to the person who is installing it.

Addressing the user has been accepted : "you should do this", "you
need to do thaat".

In this case, I would try avoiding to imply that the person
installingn the machine will be the person who has to review security
chnges when they happen, so I'd probably use the passive form
"Security updates should be reviewed before they are applied"..os
something like this.

But you're right : we used debian-l10n-english for reviewing
templates. If someone is still alive there, (s)he may help.




signature.asc
Description: PGP signature

Bug#902483: proot FTCBFS: uses the build architecture strip

[Helmut Grohne]

Source: proot
Version: 5.1.0-1.2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

proot fails to cross build from source. Its build system is well
prepared for cross compilation, but does not work immediately with
dh_auto_build as proot expects one to supply the toolchain prefix via
the CROSS_COMPILE variable, which dh_auto_build does not set. Since
prefixing build tools even works for native builds, we can just export
it unconditionally to make cross builds work. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru proot-5.1.0/debian/changelog proot-5.1.0/debian/changelog
--- proot-5.1.0/debian/changelog2017-01-14 16:58:21.0 +0100
+++ proot-5.1.0/debian/changelog2018-06-27 06:20:56.0 +0200
@@ -1,3 +1,10 @@
+proot (5.1.0-1.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass CROSS_COMPILE to make. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Jun 2018 06:20:56 +0200
+
 proot (5.1.0-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru proot-5.1.0/debian/rules proot-5.1.0/debian/rules
--- proot-5.1.0/debian/rules2017-01-14 16:58:21.0 +0100
+++ proot-5.1.0/debian/rules2018-06-27 06:20:56.0 +0200
@@ -1,5 +1,9 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
+
+include /usr/share/dpkg/architecture.mk
+export CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)-
+
 %:
dh $@ --sourcedirectory=src
 

Bug#902482: rifiuti FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: rifiuti
Version: 20040505-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

rifiuti fails to cross build from source, because uses the build
architecture compiler. It builds only during make install, but
dh_auto_install (unlike dh_auto_build) does not pass cross compilers to
make. The solution - quite simply - is to build during dh_auto_build.
In fact there no longer is any double build, as you fixed the Makefile
properly in #900177, so removing the empty override is sufficient to
make rifiuti cross build. Please consider applying the attached patch.

Helmut
diff --minimal -Nru rifiuti-20040505/debian/changelog 
rifiuti-20040505/debian/changelog
--- rifiuti-20040505/debian/changelog   2018-05-27 21:42:32.0 +0200
+++ rifiuti-20040505/debian/changelog   2018-06-27 06:08:16.0 +0200
@@ -1,3 +1,10 @@
+rifiuti (20040505-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Don't build during make install. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Jun 2018 06:08:16 +0200
+
 rifiuti (20040505-2) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru rifiuti-20040505/debian/rules rifiuti-20040505/debian/rules
--- rifiuti-20040505/debian/rules   2018-05-27 21:42:32.0 +0200
+++ rifiuti-20040505/debian/rules   2018-06-27 06:08:14.0 +0200
@@ -11,6 +11,3 @@
dh_clean
if [ -f $(CURDIR)/bin ]; then rm -f $(CURDIR)/bin; fi
if [ -d $(CURDIR)/bin ]; then rm -f $(CURDIR)/bin/*; fi
-
-# Added to avoid a double build.
-override_dh_auto_build:

Bug#902481: eterm FTCBFS: apt fails installing man2html

[Helmut Grohne]

Source: eterm
Version: 0.9.6-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

eterm fails to cross build from source, because apt has difficulties
finding an installation set with man2html as it depends on apache2 and a
whole host of stuff. However, eterm only actually uses the man2html
binary and not the cgi interface. It actually builds with the dependency
demoted to man2html-base. Please consider applying the attached patch.

Helmut
diff --minimal -Nru eterm-0.9.6/debian/changelog eterm-0.9.6/debian/changelog
--- eterm-0.9.6/debian/changelog2017-01-29 19:02:04.0 +0100
+++ eterm-0.9.6/debian/changelog2018-06-27 05:43:59.0 +0200
@@ -1,3 +1,10 @@
+eterm (0.9.6-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote man2html dependency to man2html-base. Closes: #-1.
+
+ -- Helmut Grohne   Wed, 27 Jun 2018 05:43:59 +0200
+
 eterm (0.9.6-5) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru eterm-0.9.6/debian/control eterm-0.9.6/debian/control
--- eterm-0.9.6/debian/control  2017-01-29 18:00:00.0 +0100
+++ eterm-0.9.6/debian/control  2018-06-27 05:43:57.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Debian QA Group 
 Homepage: http://www.eterm.org/
 Standards-Version: 3.9.3
-Build-Depends: man2html, libxmu-dev,libsm-dev, libice-dev, libxext-dev, 
libx11-dev, libxt-dev, libimlib2-dev, libast2-dev (>= 0.7), libpcre3-dev, 
debhelper (>=9), automake, autoconf, libtool, gettext, cvs, chrpath
+Build-Depends: man2html-base, libxmu-dev,libsm-dev, libice-dev, libxext-dev, 
libx11-dev, libxt-dev, libimlib2-dev, libast2-dev (>= 0.7), libpcre3-dev, 
debhelper (>=9), automake, autoconf, libtool, gettext, cvs, chrpath
 
 Package: eterm
 Pre-Depends: ${misc:Pre-Depends}

Bug#902480: [skimage] autopkgtest failure

[Lumin]

Package: python-skimage-doc
Version: 0.14.0-1
Severity: normal
Justification: Severity is raised from wishlist to normal because autopkgtest 
affects migration now.

http://debomatic-amd64.debian.net/distribution#unstable/skimage/0.14.0-1/autopkgtest


Setting up xvfb (2:1.20.0-2) ...
Setting up autopkgtest-satdep (0) ...
Processing triggers for libc-bin (2.27-3) ...
(Reading database ... 18444 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [05:00:55]: test python3: [---
=== python3.6 ===
/tmp/autopkgtest.hvdeQq/build.6xl/src/debian/tests/python3: 18: 
/tmp/autopkgtest.hvdeQq/build.6xl/src/debian/tests/python3: PYTHONPATH: 
parameter not set
autopkgtest [05:00:55]: test python3: ---]
python3  FAIL non-zero exit status 2
autopkgtest [05:00:55]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
autopkgtest [05:00:55]: test python3:  - - - - - - - - - - stderr - - - - - - - 
- - -
/tmp/autopkgtest.hvdeQq/build.6xl/src/debian/tests/python3: 18: 
/tmp/autopkgtest.hvdeQq/build.6xl/src/debian/tests/python3: PYTHONPATH: 
parameter not set
autopkgtest [05:00:55]:  summary
python2  FAIL non-zero exit status 2
python3  FAIL non-zero exit status 2


Reference fix:


```
diff --git a/debian/tests/python2 b/debian/tests/python2
index 47ba7d8d..d5e0dbe7 100755
--- a/debian/tests/python2
+++ b/debian/tests/python2
@@ -1,5 +1,5 @@
 #!/bin/sh
-set -efu
+set -efux

 pys="$(pyversions -rv 2>/dev/null)"
 pkgbuild=${pkgbuild:-no}
@@ -10,11 +10,12 @@ srcdir=$PWD
 for py in $pys; do
 echo "=== python$py ==="
 if [ "$pkgbuild" = "yes" ]; then
-export PYTHONPATH="$srcdir/debian/tmp/usr/lib/python$py/dist-packages"
+module="$srcdir/debian/tmp/usr/lib/python$py/dist-packages/skimage"
 cd "$srcdir/build/"
 else
+module="/usr/lib/python$py/dist-packages/skimage"
 cd "$ADTTMP"
 fi

-xvfb-run -a python$py /usr/bin/pytest -s -v -k "$keyword" skimage 2>&1
+xvfb-run -a python$py /usr/bin/pytest -s -v -k "$keyword" $module 2>&1
 done
diff --git a/debian/tests/python3 b/debian/tests/python3
index abc21bf6..6625bc94 100755
--- a/debian/tests/python3
+++ b/debian/tests/python3
@@ -9,11 +9,12 @@ srcdir=$PWD
 for py in $pys; do
 echo "=== python$py ==="
 if [ "$pkgbuild" = "yes" ]; then
-export PYTHONPATH="$srcdir/debian/tmp/usr/lib/python3/dist-packages"
+module="$srcdir/debian/tmp/usr/lib/python3/dist-packages/skimage"
 cd "$srcdir/build/"
 else
+module="/usr/lib/python3/dist-packages/skimage"
 cd "$ADTTMP"
 fi

-xvfb-run -apython$py /usr/bin/pytest-3 -s -v skimage 2>&1
+xvfb-run -apython$py /usr/bin/pytest-3 -s -v $module 2>&1
 done
```

Bug#902479: [skimage] python-skimage-doc: 35 lintian Errors

[Lumin]

Package: python-skimage-doc
Version: 0.14.0-1
Severity: normal

E: python-skimage-doc: privacy-breach-uses-embedded-file 
usr/share/doc/python-skimage-doc/html/cell_profiler.html You may use the 
libjs-mathjax package. 
(https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/mathjax.js?config=tex-ams-mml_htmlormml)

Patch

```
diff --git a/debian/rules b/debian/rules
index 82c3ed98..784c3e19 100755
--- a/debian/rules
+++ b/debian/rules
@@ -83,6 +83,9 @@ ifneq (,$(findstring -a,$(DH_INTERNAL_OPTIONS)))
: # no documentation in -a -- surprised that sphinxdoc doesn't know that
 else
dh_sphinxdoc -ppython-skimage-doc
+   find debian -type f -exec sed -i -e \
+   
's@https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js@file:///usr/share/javascript/mathjax/MathJax.js@g'
 \
+   '{}' +
 endif
 endif
```

And the doc package should depend on libjs-mathjax.

Bug#902478: [skimage] broken documentation package

[Lumin]

Package: python-skimage-doc
Version: 0.14.0-1
Severity: normal

from 0.14.0-1 debian/rules:

```
@@ -15,0 +16,2 @@ skimage (0.14.0-1) unstable; urgency=medium
 cd doc; test -d build/html || $(MAKE) html
 cd doc; test -d build/html || $(MAKE) html PYTHON=python3
```

This actually didn't work properly, because sphinx (python3)
failed to grab python3 package from python2 import path.

```
export PYTHONPATH=$(PKG_TMP)/usr/lib/python$(PYVER)/dist-packages;
```

Consequence: API documents are missing from python-skimage-doc.

reference solution:

   export PYTHONPATH=$(PKG_TMP)/usr/lib/python3/dist-packages;

reference buildlog:

   : # Build Documentation
   export 
PYTHONPATH=/<>/debian/tmp/usr/lib/python2.7/dist-packages; \
cd doc; test -d build/html || /usr/bin/make html PYTHON=python3
   make[2]: Entering directory '/<>/doc'
   python3 tools/build_modref_templates.py
   *WARNING* API documentation not generated: Can not import skimage
   Build API docs...done.
   Copying release notes
   python /usr/bin/sphinx-build -b html -d build/doctrees  -j 1 source 
build/html
   Running Sphinx v1.7.5
   making output directory...
   loading pickled environment... not yet created

   
http://debomatic-amd64.debian.net/distribution#unstable/skimage/0.14.0-1/buildlog

Bug#889854: RFS: lxml/4.2.1-1~bpo9+1 [intent to maintain bpo]

[Nicholas D Steeves]

Hi Chris,

On Tue, Apr 24, 2018 at 04:16:19PM -0400, Nicholas D Steeves wrote:
> Dear Backports Team and Mentors,
> 
> I am still pursuing sponsorship of a stretch-backport of calibre and
> its dependencies.
> 
> On Wed, Feb 07, 2018 at 05:15:26PM -0500, Nicholas D Steeves wrote:
> > Package: sponsorship-requests
> > Severity: normal
> > 
> > Dear mentors,
> > 
> > I am looking for a sponsor for my backport of "lxml".  It is needed
> > for a bpo of calibre.  I am collaborating with Norbert Preining for
> > the calibre and html5-parser backports, but have not received a reply
> > from Matthias Klose wrt lxml.

If you have time, would you please sponsor this lxml bpo?  It is
needed for a bpo of lxml, which is needed for a bpo of calibre.  I
have been using local bpos of all of these since Christmas, when I was
given a Kobo that didn't work well with the calibre in stretch.

Bug report URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889854

Up-to-date link to dsc:

  dget 
https://mentors.debian.net/debian/pool/main/l/lxml/lxml_4.2.1-1~bpo9+1.dsc

Other URLS:

  https://mentors.debian.net/package/lxml
  https://mentors.debian.net/package/html5-parser
  https://mentors.debian.net/package/calibre

And if you'd prefer to upload everything all at once, there is also:

  dget 
https://mentors.debian.net/debian/pool/main/h/html5-parser/html5-parser_0.4.4-1~bpo9+1.dsc
  dget 
https://mentors.debian.net/debian/pool/main/c/calibre/calibre_3.26.0+dfsg-1~bpo9+1.dsc


Kind regards,
Nicholas


signature.asc
Description: PGP signature

Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Vincent Lefevre]

Control: severity -1 important

On 2018-06-26 23:23:16 +0200, Axel Beckert wrote:
> Control: tag -1 - moreinfo
> Comtrol: severity -1 important
  ^^^ typo

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

Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Vincent Lefevre]

On 2018-06-26 23:23:16 +0200, Axel Beckert wrote:
> > Another issue is that here, it was a *new* BSSID (well, I assume
> > because it is a place where I had never came before).

Actually, I think that the issue occurs only in that case.
Once a config with the BSSID has been created, the behavior
is reproducible with the same BSSID.

FYI, in the wicd logs:

[...]
2018/06/25 09:21:53 :: Putting interface up...
2018/06/25 09:21:53 :: ifconfig wlp61s0 up
2018/06/25 09:21:55 :: enctype is peap-eduroam
2018/06/25 09:21:55 :: Attempting to authenticate...
2018/06/25 09:21:55 :: ['wpa_supplicant', '-B', '-i', 'wlp61s0', '-c', 
'/var/lib/wicd/configurations/04bd882b5811', '-Dwext']
2018/06/25 09:21:55 :: ['iwconfig', 'wlp61s0', 'essid', '--', 'eduroam']
2018/06/25 09:21:55 :: iwconfig wlp61s0 channel 36
2018/06/25 09:21:55 :: iwconfig wlp61s0 ap 04:BD:88:2B:58:11
2018/06/25 09:21:55 :: WPA_CLI RESULT IS DISCONNECTED
2018/06/25 09:21:56 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:21:57 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:21:58 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:21:59 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:00 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:01 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:02 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:03 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:04 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:05 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:06 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:07 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:08 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:09 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:10 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:11 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:12 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:13 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:14 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:15 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:16 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:17 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:18 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:20 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:21 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:22 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:23 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:24 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:25 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:26 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:27 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:28 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:29 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:30 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:31 :: wpa_supplicant authentication may have failed.
2018/06/25 09:22:31 :: connect result is failed
2018/06/25 09:22:31 :: exiting connection thread
2018/06/25 09:22:31 :: Sending connection attempt result bad_pass
[...]

(This was the first time 04:BD:88:2B:58:11 was seen.)

[...]
2018/06/25 09:22:38 :: enctype is peap-eduroam
2018/06/25 09:22:38 :: Attempting to authenticate...
2018/06/25 09:22:38 :: ['wpa_supplicant', '-B', '-i', 'wlp61s0', '-c', 
'/var/lib/wicd/configurations/04bd882b5811', '-Dwext']
2018/06/25 09:22:38 :: ['iwconfig', 'wlp61s0', 'essid', '--', 'eduroam']
2018/06/25 09:22:38 :: iwconfig wlp61s0 channel 36
2018/06/25 09:22:38 :: iwconfig wlp61s0 ap 04:BD:88:2B:58:11
2018/06/25 09:22:38 :: WPA_CLI RESULT IS DISCONNECTED
2018/06/25 09:22:39 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:40 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:41 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:42 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:43 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:44 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:45 :: WPA_CLI RESULT IS ASSOCIATED
2018/06/25 09:22:46 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:47 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:48 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:49 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:50 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:51 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:52 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:53 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:54 :: WPA_CLI RESULT IS SCANNING
2018/06/25 09:22:55 :: WPA_CLI RESULT IS SCANNING
2018/06/25 10:20:03 :: wpa_supplicant authentication may have failed.
2018/06/25 10:20:03 :: connect result is failed
2018/06/25 10:20:03 :: exiting connection thread
2018/06/25 10:20:03 :: Sending connection attempt result bad_pass
[...]

and so on with this BSSID. After I had removed all the old settings
from /etc/wicd/wireless-settings.conf, everything was OK.

> That sounds strange. I wonder if that could be triggered, if e.g. two
> different eduroam APs/BSSIDs are ticked with "use these settings
> for all wifis with this ESSID" but have different settings and it is
> e.g. luck which one is used (unless the BSSID fits).

That's possible. That would be the best explanation.

> As far as I 

Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

[Eli Schwartz]

Please note also that this commit was cherry-picked upstream for the
network-manager 1.6 and 1.8 maintenance branches.

See
https://github.com/NetworkManager/NetworkManager/commit/b2af5f7ab676675a496adfa08541ecca43a9d9f8

It would be nice to have this fixed, for reasons similar to 896818

It's a maintenance branch fix which results in software working as it
was always intended to, instead of crashing (which it was not intended
to do).

It makes users' custom scripts no longer crash and burn, and it makes
developers of software that runs on stretch, more comfortable about
considering improvements to their software which rely on libnm not being
broken.

Even if it is unlikely that newer versions of Cinnamon itself will be
backported to stretch, Linux Mint Debian Edition which is a respin of
stretch, will have those packages, Cinnamon developers will likely want
to make personal builds for testing purposes, etc. so having this not
crash can only be a good thing...

And it means upstream software can get developed faster, which in the
long run means that newer versions of Debian are more likely to see
useful improvements faster, and other distros with newer versions of
networkmanager that don't crash because of this bug, will be able to see
those improvements immediately.

-- 
Eli Schwartz
Bug Wrangler and Trusted User

Bug#902477: open-iscsi: long wait on reboot

[Heinrich Schuchardt]

Package: open-iscsi
Version: 2.0.874-5
Severity: normal

Dear Maintainer,

when rebooting the system waits 50 seconds to synchronzize a disconnected
iSCSI drive:

[  464.538835] systemd-shutdown[1]: All filesystems unmounted.
[  464.538881] systemd-shutdown[1]: Deactivating swaps.
[  464.543864] systemd-shutdown[1]: All swaps deactivated.
[  464.548880] systemd-shutdown[1]: Detaching loop devices.
[  464.554513] systemd-shutdown[1]: All loop devices detached.
[  464.575951] kvm: exiting hardware virtualization
[  464.576045] sd 0:0:0:1: [sda] Synchronizing SCSI cache
[  473.818361]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4295008175, last ping 4295009472, now 422
[  473.824605]  connection1:0: detected conn error (1022)
[  525.274120] sd 0:0:0:1: [sda] Synchronize Cache(10) failed: Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  525.306298] reboot: Restarting system

If before rebooting I execute

sudo umount -f /mnt/iscsi
sudo iscsiadm -m node -T iqn.2000-01.de.xypron:odroid-c2 -p 192.168.0.1:3260 
--logout
sudo reboot

this waiting time does not occur.

Looking at the /lib/systemd/system/open-iscsi.service it seems that we already
try to logout before shutdown. So it seems unclear what makes the difference.

Below you will find that reportbug tried to read /etc/iscsi/iscsid.conf.
As this file contains passwords it is only accessible to root. Do you
need any information out of it for the analysis?

Best regards

Heinrich Schuchardt

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

Kernel: Linux 4.16.0-2-arm64 (SMP w/4 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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages open-iscsi depends on:
ii  debconf [debconf-2.0]  1.5.67
ii  libc6  2.27-3
ii  libisns0   0.97-2
ii  libmount1  2.32-0.1
ii  lsb-base   9.20170808
ii  udev   238-5

Versions of packages open-iscsi recommends:
ii  busybox  1:1.27.2-2

open-iscsi suggests no packages.

-- Configuration Files:
/etc/iscsi/iscsid.conf [Errno 13] Permission denied: '/etc/iscsi/iscsid.conf'

-- debconf information:
  open-iscsi/upgrade_recovery_error:
* open-iscsi/remove_even_with_active_sessions: true
  open-iscsi/downgrade_and_break_system:
  open-iscsi/upgrade_even_with_failed_sessions:

Bug#896818: [Pkg-utopia-maintainers] Bug#896818: libnma over GI not working

[Eli Schwartz]

On Tue, 24 Apr 2018 23:07:25 +0200 Michael Biebl  wrote:
> Thanks for the bug report.
> Seems we don't have any package in stretch yet, which uses
> gir1.2-nma-1.0, which is probably why this issue has went unnoticed.
> 
> But that also means, it's probably not that important to fix this via a
> stable upload. Or put this differently: Why do you want to have this
> fixed in stretch, is there any software you use in stretch that requires
> gir1.2-nma-1.0?
One possibly good reason to get this fixed is because, Cinnamon will not
merge this PR until you do: https://github.com/linuxmint/Cinnamon/pull/7486

And this PR makes Cinnamon work better and support new features, like
https://github.com/linuxmint/Cinnamon/pull/7118

Since the current state of things is that the bindings are badly broken,
and this does nothing other than to make things work the way they were
always meant to, I think it is reasonable to backport this pretty minor fix.


End result: peoples' custom scripts no longer crash and burn.

Also, downstream developers of software that is in fact in stretch, do
not need to burden themselves by refusing to improve their software on
the grounds that it will crash and burn on stretch. This affects both
people who build their own packages for testing, and people who develop
a respin of stretch, which is supposed to showcase their software.

Like Linux Mint Debian Edition, which is based on stretch, but includes
the latest Cinnamon packages.

Also, if downstream developers are afraid to use non-deprecated
libraries like libnma because it will break on Debian, it means other
distros which use more recent networkmanager versions cannot benefit
from fixes and improvements, which in its own small way drags down the
entire Linux ecosystem. As an Arch Linux user (and maintainer of the
Cinnamon desktop on Arch) I'd like to see Cinnamon be improved...

It's such a simple fix...

Please note also that the commit has been backported to
network-manager-applet's *maintenance* 1.4 branch, and is available in
1.4.8 (released 3 weeks ago on 01 Jun 2018).

Upstream-sanctioned maintenance releases which fix bugs resulting in
completely broken package components, are good candidates for inclusion. :)

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User



signature.asc
Description: OpenPGP digital signature

Bug#902476: RFS: libzc/0.4.1-1

[Marc Ferland]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libzc"

 * Package name: libzc
   Version : 0.4.1-1
   Upstream Author : Marc Ferland 
 * URL : https://github.com/mferland/libzc
 * License : GPL-3+
   Section : libs

It builds those binary packages:

libzc-dev  - fast password cracking library for zip archives (dev)
libzc4 - fast password cracking library for zip archives
yazc  - Command line tool for the libzc library

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

https://mentors.debian.net/package/libzc

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

dget -x 
https://mentors.debian.net/debian/pool/main/libz/libzc/libzc_0.4.1-1.dsc

More information about libzc can be obtained from
https://github.com/mferland/libzc.

Changes since the last upload:

  libzc (0.4.1-1) unstable; urgency=low

* New upstream release.
* Stop checking for host os (Closes: #884792).
* Fix tests failures on big-endian machines (Closes: #884385)

   -- Marc Ferland   Sat, 23 Jun 2018 21:49:20 -0500

Regards,
   Marc Ferland

Bug#902475: gcl: GCL fails to load .o files it generates

[Gong-Yi Liao]

Package: gcl
Version: 2.6.12-76
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * GCL fails to load .o file it compiles/generates
   * Create a lisp file, say hw3.lisp, with content as '(print "test")'
   * Compile this lisp file with '(compile-file "hw3.lisp")'
   * Load the "hw3.o" file generated by GCL using '(load "hw3.o")'
   * GCL shows the following error message:
   ;; Loading "hw3.o"
   Unknown reloc type 4
  
  Error: 
  Fast links are on: do (si::use-fast-links nil) for debugging
  Signalled by LOAD.
  Condition in LOAD [or a callee]: INTERNAL-SIMPLE-ERROR: The assertion 
!emsg("Unknown reloc type %lu\n", tp) on line 186 of sfaslelf.c in function 
relocate failed: Success
  
  Broken at LOAD.  Type :H for Help.
  1  Return to top level. 

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.16.0-0.bpo.2-amd64 (SMP w/4 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/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcl depends on:
ii  debconf 1.5.67
ii  emacs-snapshot-lucid [emacsen]  2:20180619+emacs-26.1-2309-g3057260b476-1
ii  gcc 4:8-20180425-2
ii  libc6   2.27-3
ii  libgmp102:6.1.2+dfsg-3
ii  libreadline77.0-5
ii  libtcl8.6   8.6.8+dfsg-4
ii  libtk8.68.6.8-4
ii  libx11-62:1.6.5-1
ii  ucf 3.0038

gcl recommends no packages.

Versions of packages gcl suggests:
ii  gcl-doc  2.6.12-76

-- debconf information:
  gcl/default_gcl_ansi:
  gcl/default_gcl_prof:

Bug#902474: policykit-1 postinst fails with "--runtime cannot be used with unmask"

[Daniel Kahn Gillmor]

Package: policykit-1
Version: 0.105-20
Severity: normal

root@clyde:~# apt -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up policykit-1 (0.105-20) ...
--runtime cannot be used with unmask
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 policykit-1
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@clyde:~# 

-- System Information: 
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-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/dash
Init: systemd (via /run/systemd/system)
LSM: 
AppArmor: enabled
Versions of packages policykit-1 depends on:
ii dbus 1.12.8-3
ii libc6 2.27-3
ii libglib2.0-0 2.56.1-2
ii libpam-systemd 239-1
ii libpam0g 1.1.8-3.7
ii libpolkit-agent-1-0 0.105-20
ii libpolkit-backend-1-0 0.105-20
ii libpolkit-gobject-1-0 0.105-20

policykit-1 recommends no packages.
policykit-1 suggests no packages.
no debconf information

Bug#862873: RFA: vblade-persist

[Aurelio Juarez]

On Wed, 17 May 2017 18:28:16 -0400 Daniel Kahn Gillmor <
d...@fifthhorseman.net> wrote:
> Package: wnpp
> Severity: normal
>
> I'm both upstream and the debian maintainer for vblade-persist.  I
> don't currently use it, and i don't have much time for it.
> Furthermore, it relies on runit because i didn't trust sysvinit.  with
> the advent of systemd, i think that vblade-persist would be better
> implemented as a vblade-launch script and a vblade@.service systemd
> template that invokes vblade-launch.  Then the standard systemctl
> mechanisms could be used to control arbitrary vblade processes.
>
> this would remove the dependency on runit, and would allow local
> sysadmins to control persistent units like so:
>
>   systemctl install vblade@eth0.2.3-dev-sda2.service
>
> this would mean a systemd template file like (untested):
>
> ---
> [Unit]
> Description=vblade AOE exporter %i
>
> [Service]
> type=simple
> ExecStart=/usr/bin/vblade-launch %i
>
> [Install]
> WantedBy=multi-user.target
> ---
>
> It'd take a bit of thinking about how to handle mac address
> limitations, and the decision about whether to place the symlink or
> not, to bring this up to parity with the current implementation, but
> then this work could be donated directly to the vblade upstream, and
> we could leave it at that.
>
> If someone wants to adopt vblade-persist, that would be fine with me.
> If someone wants to take the systemd approach i describe above, i'd be
> happy to ask for an RM: for vblade-persist as well.
>
>   --dkg
>
> #1AurelioJuarezCortez

Bug#902473: myrepos: Suggests transitional package ack-grep which is going away very soon

[Axel Beckert]

Package: myrepos
Version: 1.20160123
Severity: normal

Hi,

myrepos has a package relation "Suggests: ack-grep, …", but ack-grep is
a transitional package for a few years now and will vanish with the next
(imminent) upload of ack.

So please replace "ack-grep" with just "ack" where ever it appears in
your package.

TIA!

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

myrepos depends on no packages.

Versions of packages myrepos recommends:
ii  libhtml-parser-perl  3.72-3+b2
ii  libio-pty-easy-perl  0.10-1
ii  libwww-perl  6.34-1
ii  perl 5.26.2-6

Versions of packages myrepos suggests:
ii  ack [ack-grep]2.22-1
ii  ack-grep  2.22-1
ii  bzr   2.7.0+bzr6622-11
ii  curl  7.60.0-2
ii  cvs   2:1.12.13+real-26
ii  darcs 2.14.0-1
ii  fossil1:2.5-1
ii  git [git-core]1:2.18.0-1
pn  kdesdk-scripts
ii  liburi-perl   1.74-1
ii  mercurial 4.6.1-1
ii  subversion1.10.0-2
pn  subversion-tools  
ii  vcsh  1.20151229-1

-- no debconf information

Bug#850873: move libglademm-2.4.pc to a multiarch path

[Felipe Sateler]

Control: affects -1 - src:paprefs

On Tue, 10 Jan 2017 21:00:56 +0100 Helmut Grohne  wrote:
> Package: libglademm-2.4-dev
> Version: 2.6.7-5
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> Control: affects -1 + src:paman src:paprefs

Since 0.9.10-3 paprefs no longer depends on libglademm so it is no longer
affected.

Saludos

Bug#891031: dgit: Please make the unavoidable error message on first push more user-friendly

[Ian Jackson]

I'm changing the messages so it looks like this:

  [lots of blather]
  Checking that HEAD inciudes all changes in archive...
  dgit: error: Wanted tag maintainer view tag (test-dummy/1.0-1) on dgit 
server, but not found
  | Not fast forward; maybe --overwrite is needed, see dgit(1)
  ! Push failed, while preparing your push.
  ! You can retry the push, after fixing the problem, if you like.
  $

And I have added a note to dgit(1) saying:

  This  option  is also usually necessary the first time a package
  is pushed with dgit push to a particular suite.  See dgit-
  maint-*(7).

Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#714572: emacs-goodies-el: csv-mode customize-mode

[Nicholas D Steeves]

Hi Kevin,

On Mon, Jul 01, 2013 at 08:17:27AM +1000, Kevin Ryde wrote:
> Package: emacs-goodies-el
> Version: 35.4
> Severity: wishlist
> File: /usr/share/emacs/site-lisp/emacs-goodies-el/csv-mode.el
> 
> In emacs24
> 
> M-x csv-mode
> M-x customize-mode
> 
> prompts for a "Major mode" where I hoped it would go straight to the
> "CSV" customize defgroup.
> 
> This can be setup with the ":group" of define-derived-mode,
> 
> (define-derived-mode csv-mode ...
>   "Docstring"
> 
>   :group 'CSV
> 
>   (body forms...))
> 
> customize-mode looks for a group "csv" for "csv-mode" but if the group
> name is capitalized etc then it needs to be told with :group.  :group is
> new in emacs22 but quietly does nothing in emacs21 and xemacs21.

Thank you for reporting this bug, and sorry it took so long to receive
a follow-up.  Emacs-goodies-el was recently adopted by the Debian
Emacsen Team, and csv-mode has been elpafied and is currently waiting in
  NEW https://ftp-master.debian.org/new.html

This bug will be closed with the next upload of emacs-goodies-el.  If
the issue you reported still exists, please file a new bug against the
package elpa-csv-mode.

Sincerely,
Nicholas


signature.asc
Description: PGP signature

Bug#901534: mp4h statically links libpcre

[Axel Beckert]

Hi Helmut,

Helmut Grohne wrote:
> mp4h statically links libpcre.

Good catch!

> Quite simply, I propose linking mp4h dynamically to solve all of these
> issues.

Thanks for the bug report and patch!

> Please consider applying the attached patch.

Done. Upload imminent.

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

Bug#639221: replace folding.el with elpa-folding

[Nicholas D Steeves]

Control: owner -1 !

On Tue, Jun 26, 2018 at 08:48:39PM -0300, David Bremner wrote:
> Nicholas D Steeves  writes:
> 
> >
> > I'm not convinced this one is more suitable for the Debian archive
> > than the alternatives, but if you consent to being an Uploader for
> > Jaalto's folding-mode (continuation of the goodies one) then I'm
> > willing to package it:
> >   https://github.com/jaalto/project-emacs--folding-mode/
> >
> 
> Our (or at least my) goal in this instance is not to package the best
> possible things, but to provide the smoothest transition for users of
> emacs-goodies-el. That means having the keybindings they are used to
> work in the same way (to the degree that is possible even with the same
> package).

100% clear now.  None of those "Use X, X is the future!" shenanigans,
when a living upstream for an existing goodies subpackage is available
;-)

I plan to have the packaging done within 24h, and will add you as an
additional Uploader.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#639221: replace folding.el with elpa-folding

[David Bremner]

Nicholas D Steeves  writes:

>
> I'm not convinced this one is more suitable for the Debian archive
> than the alternatives, but if you consent to being an Uploader for
> Jaalto's folding-mode (continuation of the goodies one) then I'm
> willing to package it:
>   https://github.com/jaalto/project-emacs--folding-mode/
>

Our (or at least my) goal in this instance is not to package the best
possible things, but to provide the smoothest transition for users of
emacs-goodies-el. That means having the keybindings they are used to
work in the same way (to the degree that is possible even with the same
package).

Bug#902472: sdl2: can deadlock after hiding a window

[ydirson]

Package: libsdl2
Version: 2.0.5+dfsg1-3
Tags: stretch patch

It can happen that SDL gets stuck waiting for X to accept a grab request, when 
the
window has already been hidden with SDL_HideWindow.

This behaviour has been fixed in 2.0.6 with commit 8f0a002 "x11: Don't loop 
forever
if the X server refuses a pointer grab", and does fix the problem for me when 
cherry-picking
that commit.

It would be great if that patch could find its way in a stretch update.  In any 
case since
it would take some time to get the fix to users, it would be good to get a 
backport to point
impacted users to.  Would you mind if I uploaded a 2.0.8 backport ?

Bug#869146: dgit: should never add .orig to the .changes more than once

[Ian Jackson]

Ian Jackson writes ("dgit: should never add .orig to the .changes more than 
once"):
> Anyway, I will fix the bug.

Having investigated, I have discovered that this might also happen if
you didn't use dgit build, and whatever build process you used
included some .origs.  dgit would probably try to add them again.

I mention this in case it should come up in a future bug report
against an older version of dgit.

Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#882792: xfce4-panel: some icons not appearing in notification panel

[Shannon Dealy]

Package: xfce4-panel
Version: 4.12.1-2
Followup-For: Bug #882792

Dear Maintainer,

I am experiencing this problem as well. It started after I logged out and
rebooted the system for the first time in many weeks (I'm not sure exactly
how long). During that time many packages were installed / removed / upgraded,
though I am not sure if any of them are relevant to the problem.

Specifics:

  The following no longer display in the notification area, though they did
  before the reboot:

 vlc 3.0.2-0+deb
 remmina 1.2.30.1+dfsg-1~bpo9+1  

  The following all continue to work fine with the notification area:

 network-manager-gnome (nm-applet) 1.4.4-1
 xfce4-clipman 2:1.4.1-1
 hamster-applet 2.91.3+git2
 alltray 0.71b-1+b2

Worthy of note, vlc is QT based and remmina is GTK based, so it appears the
framework used may not matter.

I have tried rebooting, reinstalling recently deleted packages, deleting
recently installed packages, so far, nothing I can think of works. I didn't
bother with some of the things that had been tried above.

etckeeper is installed, and in reviewing the git log of package changes, I
didn't see any obvious issues, though perhaps someone with a better knowledge
of the notification area code might see something (a relevant library?), but
the section of the log that might apply (after stripping extraneous commits)
is about 800 lines long.


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

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

Versions of packages xfce4-panel depends on:
ii  exo-utils0.10.7-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libdbus-glib-1-2 0.108-2
ii  libexo-1-0   0.10.7-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgarcon-1-00.4.0-2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libice6  2:1.0.9-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libsm6   2:1.2.2-1+b3
ii  libwnck222.30.7-5.1
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfce4ui-1-0   4.12.1-2
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.

-- debconf-show failed

Bug#902471: ipywidgets: FTBFS in buster/sid (error TS2352: Type 'HTMLButtonElement' cannot be converted to type 'HTMLInputElement')

[Santiago Vila]

Package: src:ipywidgets
Version: 6.0.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
dh_auto_configure -- -d ./widgetsnbextension
I: pybuild base:217: python2.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
I: pybuild base:217: python3.6 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make -C debian -f fakewebpack.mk all
make[2]: Entering directory '/<>/debian'
/usr/bin/make -f "fakewebpack-prep-unpacked.mk" all
make[3]: Entering directory '/<>/debian'
cd "fakewebpack-unpacked/phosphor/" && tsc --project src
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. 
fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/phosphor/styles/base.css.real" > 
"fakewebpack-unpacked/phosphor/styles/base.css"
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. 
-DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/phosphor/styles/base.css?f74d"
printf "module.exports = $(cat 
"fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > 
"fakewebpack-unpacked/jupyter-js-widgets/package.json"
cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --project src
src/widget_selection.ts(366,30): error TS2352: Type 'HTMLButtonElement' cannot 
be converted to type 'HTMLInputElement'.
  Property 'accept' is missing in type 'HTMLButtonElement'.
fakewebpack-prep-unpacked.mk:33: recipe for target 
'fakewebpack-unpacked/jupyter-js-widgets/lib.stamp' failed
make[3]: *** [fakewebpack-unpacked/jupyter-js-widgets/lib.stamp] Error 1
make[3]: Leaving directory '/<>/debian'
fakewebpack.mk:73: recipe for target 
'fakewebpack/widgetsnbextension-unpacked.stamp' failed
make[2]: *** [fakewebpack/widgetsnbextension-unpacked.stamp] Error 2
make[2]: Leaving directory '/<>/debian'
debian/rules:15: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#639221: replace folding.el with elpa-folding

[Nicholas D Steeves]

Hi Reuben,

On Tue, Jun 26, 2018 at 10:52:21AM +0100, Reuben Thomas wrote:
>On Mon, 25 Jun 2018, 23:47 Nicholas D Steeves,  wrote:
> 
>  Given that whatever we do will require a new source package in the
>  archive, maybe it would be a good time to consider alternative folding
>  addons?  Jaalto's project of course wins for backwards-compatibility
>  ;-)
> 
>For my purposes, an alternative is fine.

Awesome :-)

>In general I'm not sure there's much value in packaging Emacs lisp in
>Debian, given the availability and ease of use of package.el and the
>various package archives.

Yeah, this is a long-running debate...should Debian provide only the
basics and let users install everything else from the internet, or
should Debian provide a curated and supported subset of various
package archives.  I'm in the latter camp, but personally I think that
it would be wonderful if it was easier to grab up-to-date browser
plugins and ELPA packages on Debian stable

Re: the value in a Debian-packaged curated subset of MELPA and GNU
Elpa: Trust (not random unsigned code off of github), and
compatibility--we have a team dedicated to making sure they work
properly with each other, and to work with all of the upstreams to
make this a reality.  Worst-case scenario explicit breaks would be
declared.  

Sean, did you ever write a blog post or short paper about the vision
and scope of dh-elpa?  It would be nice if this was more visible to
users.  I've been asked about it at least a dozen times this last
year ;-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#902469: golang-gopkg-hlandau-easyconfig.v1: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-gopkg-hlandau-easyconfig.v1
Version: 1.0.15-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf 
gopkg.in/hlandau/easyconfig.v1/adaptenv 
gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag 
gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual
gopkg.in/hlandau/configurable.v1
github.com/BurntSushi/toml
gopkg.in/hlandau/easyconfig.v1/cflag
gopkg.in/hlandau/svcutils.v1/exepath
gopkg.in/hlandau/easyconfig.v1/adaptconf
gopkg.in/hlandau/easyconfig.v1/adaptenv
github.com/ogier/pflag
github.com/alecthomas/units
gopkg.in/alecthomas/kingpin.v2
gopkg.in/hlandau/easyconfig.v1/adaptflag
# gopkg.in/hlandau/easyconfig.v1/adaptflag
src/gopkg.in/hlandau/easyconfig.v1/adaptflag/adaptflag.go:227:22: cannot use 
byte(r) (type byte) as type rune in argument to fl.Short
gopkg.in/hlandau/easyconfig.v1/cstruct
gopkg.in/hlandau/easyconfig.v1/manual
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf 
gopkg.in/hlandau/easyconfig.v1/adaptenv 
gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag 
gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual 
returned exit code 2
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-hlandau-easyconfig.v1.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902465: golang-github-armon-go-metrics: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-armon-go-metrics
Version: 0.0~git20170601.0.f036747-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus
github.com/armon/go-metrics
github.com/hashicorp/go-cleanhttp
github.com/hashicorp/go-retryablehttp
github.com/circonus-labs/circonus-gometrics/api
github.com/circonus-labs/circonus-gometrics/checkmgr
github.com/circonus-labs/circonusllhist
github.com/circonus-labs/circonus-gometrics

[... snipped ...]

--- PASS: TestNewStatsdSinkFromURL (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_includes_port (0.00s)
=== RUN   TestStatsite_Flatten
--- PASS: TestStatsite_Flatten (0.00s)
=== RUN   TestStatsite_PushFullQueue
--- PASS: TestStatsite_PushFullQueue (0.00s)
=== RUN   TestStatsite_Conn
--- SKIP: TestStatsite_Conn (0.00s)
statsite_test.go:46: 
=== RUN   TestNewStatsiteSinkFromURL
=== RUN   TestNewStatsiteSinkFromURL/address_is_populated
=== RUN   TestNewStatsiteSinkFromURL/address_includes_port
--- PASS: TestNewStatsiteSinkFromURL (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_includes_port (0.00s)
FAIL
FAILgithub.com/armon/go-metrics 0.230s
=== RUN   TestNewCirconusSink
--- PASS: TestNewCirconusSink (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestSetGauge
--- SKIP: TestSetGauge (0.00s)
circonus_test.go:72: 
=== RUN   TestIncrCounter
--- PASS: TestIncrCounter (0.00s)
=== RUN   TestAddSample
--- PASS: TestAddSample (0.00s)
PASS
ok  github.com/armon/go-metrics/circonus0.003s
=== RUN   TestParseKey
--- PASS: TestParseKey (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestMetricSink
--- PASS: TestMetricSink (0.00s)
=== RUN   TestTaggableMetrics
--- PASS: TestTaggableMetrics (0.00s)
PASS
ok  github.com/armon/go-metrics/datadog 0.002s
?   github.com/armon/go-metrics/prometheus  [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus 
returned exit code 1
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-armon-go-metrics.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902468: golang-github-mwitkow-go-conntrack: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-mwitkow-go-conntrack
Version: 0.0~git20161129.cc309e4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
dh_auto_configure: "github.com/mwitkow/go-conntrack" is already installed. 
Please check for circular dependencies.

   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/mwitkow/go-conntrack 
github.com/mwitkow/go-conntrack/connhelpers
github.com/beorn7/perks/quantile
github.com/golang/protobuf/proto
github.com/prometheus/client_model/go
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
github.com/prometheus/common/model
github.com/prometheus/common/expfmt
github.com/prometheus/procfs/internal/util
github.com/prometheus/procfs/nfs
github.com/prometheus/procfs/xfs
github.com/prometheus/procfs
github.com/prometheus/client_golang/prometheus
golang.org/x/net/internal/timeseries
golang.org/x/net/trace
github.com/mwitkow/go-conntrack
github.com/mwitkow/go-conntrack/connhelpers
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers
=== RUN   TestDialerWrapper
=== RUN   
TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff
=== RUN   TestDialerWrapper/TestDialerMetricsArePreregistered
=== RUN   TestDialerWrapper/TestDialerRefusedFailure
=== RUN   TestDialerWrapper/TestDialerResolutionFailure
=== RUN   TestDialerWrapper/TestDialerUnderNormalConnection
=== RUN   TestDialerWrapper/TestDialerWithContextName
--- PASS: TestDialerWrapper (0.12s)
--- PASS: 
TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff (0.01s)
--- PASS: TestDialerWrapper/TestDialerMetricsArePreregistered (0.02s)
--- PASS: TestDialerWrapper/TestDialerRefusedFailure (0.01s)
--- PASS: TestDialerWrapper/TestDialerResolutionFailure (0.04s)
--- PASS: TestDialerWrapper/TestDialerUnderNormalConnection (0.02s)
--- PASS: TestDialerWrapper/TestDialerWithContextName (0.01s)
dialer_test.go:186: stopped http.Server at: 127.0.0.1:46241
=== RUN   TestListenerTestSuite
=== RUN   TestListenerTestSuite/TestDialerTracingCapturedInPage
=== RUN   TestListenerTestSuite/TestMonitoringNormalConns
=== RUN   TestListenerTestSuite/TestTracingNormalComms
=== RUN   TestListenerTestSuite/TestTrackingMetricsPreregistered
--- FAIL: TestListenerTestSuite (0.05s)
--- PASS: TestListenerTestSuite/TestDialerTracingCapturedInPage (0.01s)
--- FAIL: TestListenerTestSuite/TestMonitoringNormalConns (0.01s)
listener_test.go:81: 
Error Trace:listener_test.go:81
Error:  Not equal: 
expected: 2
actual  : 1
Test:   
TestListenerTestSuite/TestMonitoringNormalConns
Messages:   the closed conn counter must be 
incremented after connection was closed
--- PASS: TestListenerTestSuite/TestTracingNormalComms (0.01s)
--- PASS: TestListenerTestSuite/TestTrackingMetricsPreregistered (0.01s)
listener_test.go:97: stopped http.Server at: 127.0.0.1:41893
FAIL
FAILgithub.com/mwitkow/go-conntrack 0.180s
?   github.com/mwitkow/go-conntrack/connhelpers [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers 
returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-mwitkow-go-conntrack.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-kardianos-osext
Version: 0.0~git20170510.0.ae77be6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/kardianos/osext
github.com/kardianos/osext
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext
=== RUN   TestPrintExecutable
--- PASS: TestPrintExecutable (0.00s)
osext_test.go:32: Executable: /tmp/go-build962600465/b001/osext.test
=== RUN   TestPrintExecutableFolder
--- PASS: TestPrintExecutableFolder (0.00s)
osext_test.go:39: Executable Folder: /tmp/go-build962600465/b001
=== RUN   TestExecutableFolder
--- PASS: TestExecutableFolder (0.00s)
=== RUN   TestExecutableMatch
--- PASS: TestExecutableMatch (0.00s)
=== RUN   TestExecutableDelete
--- FAIL: TestExecutableDelete (0.00s)
osext_test.go:135: Child returned 
"/tmp/go-build962600465/b001/osext.test (deleted)", not the same file as 
"/tmp/go-build962600465/b001/osext.test"
FAIL
FAILgithub.com/kardianos/osext  0.004s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-kardianos-osext.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902466: golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-grpc-ecosystem-go-grpc-prometheus
Version: 1.1+git20170826.0dafe0d-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d'
cd 
obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto
 && \
GOPATH=obj-x86_64-linux-gnu make 
make[2]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d/obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto'
PATH="obj-x86_64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 protoc \
  -I. \
-Iobj-x86_64-linux-gnu/src \

[... snipped ...]

=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.08s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.02s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:218: 
Error Trace:server_test.go:218
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:186: 
Error Trace:server_test.go:186
Error:  Not equal: 
expected: 2
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList OK
server_test.go:193: 
Error Trace:server_test.go:193
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:168: 
Error Trace:server_test.go:168
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:86: stopped grpc.Server at: 127.0.0.1:33315
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.124s
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/grpc-ecosystem/go-grpc-prometheus 
github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto returned exit 
code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-go-grpc-prometheus.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902470: influxdb-python: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:influxdb-python
Version: 4.1.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_influxdb/build/influxdb

[... snipped ...]

SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
test_create_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_admin 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_password 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_username 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user_nonexisting 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_fresh_server_no_db 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users_empty 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_invalid_port_fails 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail_ignore_errors 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_admin_privileges 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
Ensure precision is preserved when casting floats into strings. ... ok
test_make_lines (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_make_lines_unicode (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_quote_ident (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_quote_literal (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_string_val_newline (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_timezone (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok

==
FAIL: test_write_points_from_dataframe_with_numeric_precision 
(influxdb.tests.dataframe_client_test.TestDataFrameClient)
--
Traceback (most recent call last):
  File "/<>/influxdb/tests/dataframe_client_test.py", line 294, in 
test_write_points_from_dataframe_with_numeric_precision
self.assertEqual(m.last_request.body, expected_default_precision)
AssertionError: 'foo,hello=there 0="1",1=1i,2=1.1 
0\nfoo,hello=there 0="2",1=2i,2=2.2 36000\n' != 
'foo,hello=there 0="1",1=1i,2=1.111 0\nfoo,hello=there 
0="2",1=2i,2=2.222 36000\n'

--
Ran 190 tests in 0.634s

FAILED (SKIP=23, failures=1)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_influxdb/build; python2.7 -m nose {dir} 
--verbose
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for 

Bug#902463: flask-script: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-script
Version: 2.0.5-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/commands.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/_compat.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/cli.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/__init__.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/commands.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/_compat.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/cli.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/__init__.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
py.test tests.py
= test session starts ==
platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0
rootdir: /<>, inifile:
collected 0 items / 1 errors

 ERRORS 
__ ERROR collecting tests.py ___
ImportError while importing test module '/<>/tests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests.py:8: in 
from flask.ext.script._compat import StringIO, text_type
E   ImportError: No module named ext.script._compat
!!! Interrupted: 1 errors during collection 
=== 1 error in 0.21 seconds 
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902454: bochs: FTBFS in buster/sid ('AmlCode' undeclared)

[Santiago Vila]

Package: src:bochs
Version: 2.6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
libtoolize -c
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './compile'
libtoolize: copying file './config.guess'
libtoolize: copying file './config.sub'
libtoolize: copying file './depcomp'
libtoolize: copying file './install-sh'
libtoolize: copying file './missing'
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'libltdl/m4'.
libtoolize: copying file 'libltdl/m4/libtool.m4'

[... snipped ...]


acpi-dsdt.dsl.i631: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0E)

acpi-dsdt.dsl.i634: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0F)


Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation

ASL Input: acpi-dsdt.dsl.i - 639 lines, 29236 bytes, 707 keywords
AML Output:acpi-dsdt.aml - 7585 bytes, 253 named objects, 454 executable 
opcodes
Hex Dump:  acpi-dsdt.hex - 71586 bytes

Compilation complete. 0 Errors, 51 Warnings, 10 Remarks, 494 Optimizations, 93 
Constants Folded
rm acpi-dsdt.dsl.i
sed -i -e's/^unsigned/const unsigned/' acpi-dsdt.hex
gcc -m32 -fno-stack-protector -O2 -Wall -c -o rombios32.o rombios32.c
rombios32.c: In function 'setup_mtrr':
rombios32.c:501:23: warning: variable 'wc' set but not used 
[-Wunused-but-set-variable]
 int i, vcnt, fix, wc;
   ^~
In file included from rombios32.c:1454:0:
acpi-dsdt.hex: At top level:
acpi-dsdt.hex:13:15: warning: extra tokens at end of #ifndef directive
 #ifndef __ACPI-DSDT_HEX__
   ^
acpi-dsdt.hex:14:15: warning: ISO C99 requires whitespace after the macro name
 #define __ACPI-DSDT_HEX__
   ^
acpi-dsdt.hex:16:25: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '-' token
 const unsigned char acpi-dsdt_aml_code[] =
 ^
rombios32.c: In function 'acpi_bios_init':
rombios32.c:1609:20: error: 'AmlCode' undeclared (first use in this function)
 addr += sizeof(AmlCode);
^~~
rombios32.c:1609:20: note: each undeclared identifier is reported only once for 
each function it appears in
Makefile:125: recipe for target 'rombios32.o' failed
make[1]: *** [rombios32.o] Error 1
make[1]: Leaving directory '/<>/bios'
debian/rules:135: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902464: flask-silk: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-silk
Version: 0.2-12
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2,python3,sphinxdoc,linktree --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build

[... snipped ...]

make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test 
running test
running egg_info
writing requirements to Flask_Silk.egg-info/requires.txt
writing Flask_Silk.egg-info/PKG-INFO
writing top-level names to Flask_Silk.egg-info/top_level.txt
writing dependency_links to Flask_Silk.egg-info/dependency_links.txt
reading manifest file 'Flask_Silk.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'Flask_Silk.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
  File "setup.py", line 46, in 
'Topic :: Software Development :: Libraries :: Python Modules'
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 129, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 226, 
in run
self.run_tests()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 248, 
in run_tests
exit=False,
  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
  File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
  File "/usr/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
module = __import__('.'.join(parts_copy))
  File "/<>/test.py", line 5, in 
from flask.ext.silk import Silk
ImportError: No module named ext.silk
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902461: flask-oauthlib: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-oauthlib
Version: 0.9.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib
copying flask_oauthlib/client.py -> 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib
copying flask_oauthlib/__init__.py -> 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib

[... snipped ...]

return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_oauth2/test_refresh.py",
 line 5, in 
from .base import TestCase
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_oauth2/base.py",
 line 8, in 
from flask_sqlalchemy import SQLAlchemy
ModuleNotFoundError: No module named 'flask_sqlalchemy'

==
ERROR: Failure: ModuleNotFoundError (No module named 'mock')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 235, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_utils.py",
 line 4, in 
import mock
ModuleNotFoundError: No module named 'mock'

--
Ran 11 tests in 0.004s

FAILED (errors=9)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902462: flask-restful: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-restful
Version: 0.3.6-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=pybuild --with=python2,python3,sphinxdoc
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build 

[... snipped ...]

checking consistency... done
preparing documents... done
writing output... [ 11%] api
writing output... [ 22%] extending
writing output... [ 33%] fields
writing output... [ 44%] index
writing output... [ 55%] installation
writing output... [ 66%] intermediate-usage
writing output... [ 77%] quickstart
writing output... [ 88%] reqparse
writing output... [100%] testing

/<>/docs/reqparse.rst:41: WARNING: undefined label: error-messages 
(if the link has no caption the label must precede a section header)
generating indices... genindex py-modindex
writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 5 warnings.

The HTML pages are in _build/html.

Build finished. The HTML pages are in _build/html.
make[2]: Leaving directory '/<>/docs'
make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd 
/<>/.pybuild/cpython2_2.7_flask-restful/build; python2.7 -m nose 
tests
...E...
==
ERROR: test_fr_405 (tests.test_api.APITestCase)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython2_2.7_flask-restful/build/tests/test_api.py", 
line 787, in test_fr_405
set(['HEAD', 'OPTIONS'] + HelloWorld.methods))
TypeError: can only concatenate list (not "set") to list

--
Ran 395 tests in 0.228s

FAILED (errors=1)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_flask-restful/build; python2.7 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902459: faumachine: FTBFS in buster/sid (error: 'faum_dsdt' undeclared)

[Santiago Vila]

Package: src:faumachine
Version: 20180503-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
./autogen.sh
configure.ac:140: installing 'scripts/compile'
configure.ac:142: installing 'scripts/config.guess'
configure.ac:142: installing 'scripts/config.sub'
configure.ac:20: installing 'scripts/install-sh'
configure.ac:20: installing 'scripts/missing'
chips/Makefile.am: installing 'scripts/depcomp'
lib/Makefile.am:174: warning: source file 'pattern-matcher/patternm.c' is in a 
subdirectory,
lib/Makefile.am:174: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'

[... snipped ...]

../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-print.o -MD -MP 
-MF .deps/libinit_rm_a-print.Tpo -c -o libinit_rm_a-print.o `test -f 
'../mb_template_bios/print.c' || echo './'`../mb_template_bios/print.c
mv -f .deps/libinit_rm_a-print.Tpo .deps/libinit_rm_a-print.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-vsprintf.o -MD -MP 
-MF .deps/libinit_rm_a-vsprintf.Tpo -c -o libinit_rm_a-vsprintf.o `test -f 
'../mb_template_bios/vsprintf.c' || echo './'`../mb_template_bios/vsprintf.c
mv -f .deps/libinit_rm_a-vsprintf.Tpo .deps/libinit_rm_a-vsprintf.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-debug.o -MD -MP 
-MF .deps/libinit_rm_a-debug.Tpo -c -o libinit_rm_a-debug.o `test -f 
'../mb_template_bios/debug.c' || echo './'`../mb_template_bios/debug.c
mv -f .deps/libinit_rm_a-debug.Tpo .deps/libinit_rm_a-debug.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses 

Bug#902455: ccdproc: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ccdproc
Version: 1.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  ccdproc/core.py:1568: RuntimeWarning: invalid value encountered in greater
crarr = (rarr > thresh)

ccdproc/tests/test_ccdproc.py::test_flat_correct_does_not_change_input
  /usr/lib/python2.7/dist-packages/astropy/units/quantity.py:641: 
RuntimeWarning: invalid value encountered in true_divide
*arrays, **kwargs)

ccdproc/tests/test_ccdproc.py::test_transform_image_does_not_change_input
  ccdproc/core.py:841: RuntimeWarning: invalid value encountered in sqrt
nccd.data = transform_func(nccd.data, **kwargs)

ccdproc/tests/test_ccdproc.py::test_wcs_project_onto_shifted_wcs
  ccdproc/core.py:921: RuntimeWarning: invalid value encountered in greater
reprojected_mask = reprojected_mask > 1e-8

ccdproc/tests/test_ccdproc.py::test_wcs_project_onto_scale_wcs
  ccdproc/core.py:921: RuntimeWarning: invalid value encountered in greater
reprojected_mask = reprojected_mask > 1e-8

docs/ccdproc/image_combination.rst
  -c:1: RuntimeWarning: divide by zero encountered in divide
  -c:1: RuntimeWarning: divide by zero encountered in divide
  -c:1: RuntimeWarning: divide by zero encountered in divide
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)

docs/ccdproc/image_management.rst
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 4 failed, 370 passed, 3 skipped, 17 warnings in 6.83 seconds =
debian/rules:16: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902453: aff4: FTBFS in buster/sid

[Santiago Vila]

Package: src:aff4
Version: 0.24.post1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with autoreconf,python2 --parallel
   dh_update_autotools_config -i -O--parallel
   dh_autoreconf -i -O--parallel
configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...
m4/uriparser.m4:1: URIPARSER_CHECK is expanded from...
configure.ac:104: the top level
configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "AFF4"
#define PACKAGE_TARNAME "aff4"
#define PACKAGE_VERSION "0.1"
#define PACKAGE_STRING "AFF4 0.1"
#define PACKAGE_BUGREPORT "aff4-us...@googlegroups.com"
#define PACKAGE_URL "http://www.aff4.org/;
#define PACKAGE "aff4"
#define VERSION "0.1"
#define HAVE_LIBRAPTOR2 1
#define HAVE_LIBUUID 1
#define HAVE_LIBZ 1
#define HAVE_LIBGLOG 1
#define HAVE_LIBSNAPPY 1
#define HAVE_LIBPTHREAD 1
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_UNISTD_H 1
#define SIZEOF_OFF_T 8
#define SIZEOF_SIZE_T 8
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"

configure: exit 1
dh_auto_configure: ./configure --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 returned exit code 1
debian/rules:14: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902460: flask-assets: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-assets
Version: 0.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
copying src/flask_assets.py -> 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build; python3.6 -m nose 
tests

[... snipped ...]


==
ERROR: Make sure url generation works with globs.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 31, in setup
self.app = Flask(__name__, static_path='/app_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

==
ERROR: Test how urls are generated via the Flask static system
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 31, in setup
self.app = Flask(__name__, static_path='/app_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

==
ERROR: Make sure the "url" and "directory" config values are
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 153, in setup
self.app = Flask(__name__, static_path='/initapp_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

--
Ran 29 tests in 0.066s

FAILED (errors=9)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902457: cupt: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:cupt
Version: 2.10.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep -Bb/ --parallel --with bash-completion
   dh_testdir -i -O-Bb/ -O--parallel
   dh_update_autotools_config -i -O-Bb/ -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -Bb/ -- -DCMAKE_BUILD_TYPE=RelWithDebInfo
cd b && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=RelWithDebInfo
-- The C compiler identification is GNU 7.3.0
-- The CXX compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

[03:42:41] tt/query/show/package-existance.t 
.. ok   92 ms ( 
0.00 usr  0.00 sys +  0.05 cusr  0.02 csys =  0.07 CPU)
[03:42:41] tt/query/show/status-of-installed-package.t 
 ok  261 ms ( 0.00 usr  
0.00 sys +  0.08 cusr  0.05 csys =  0.13 CPU)
[03:42:41] tt/query/show/version-merging/architecture.t 
... ok  129 ms ( 0.00 usr  
0.00 sys +  0.07 cusr  0.02 csys =  0.09 CPU)
[03:42:42] tt/query/show/version-merging/version-hash-release.t 
... ok  195 ms ( 0.00 usr  0.00 sys 
+  0.08 cusr  0.03 csys =  0.11 CPU)
[03:42:43] tt/query/version-string/compare.t 
.. ok 1230 ms ( 
0.02 usr  0.00 sys +  0.23 cusr  0.19 csys =  0.44 CPU)
[03:42:43] tt/query/version-string/invalid.t 
.. ok  195 ms ( 
0.00 usr  0.00 sys +  0.08 cusr  0.03 csys =  0.11 CPU)
[03:42:43] tt/query/why/basic.t 
... ok  
120 ms ( 0.01 usr  0.00 sys +  0.06 cusr  0.03 csys =  0.10 CPU)
[03:42:44] tt/query/why/endurance.t 
... ok  
955 ms ( 0.00 usr  0.00 sys +  0.68 cusr  0.21 csys =  0.89 CPU)
[03:42:44] tt/query/why/from-specific-packages.t 
.. ok  152 ms ( 
0.00 usr  0.00 sys +  0.07 cusr  0.02 csys =  0.09 CPU)
[03:42:44] tt/query/why/loop.t 
 ok 
  93 ms ( 0.00 usr  0.00 sys +  0.07 cusr  0.01 csys =  0.08 CPU)
[03:42:45] tt/query/why/priorities.t 
.. ok  
311 ms ( 0.01 usr  0.00 sys +  0.11 cusr  0.04 csys =  0.16 CPU)
[03:42:45] tt/query/why/recommends-and-suggests.t 
. ok   98 ms ( 0.00 
usr  0.00 sys +  0.06 cusr  0.02 csys =  0.08 CPU)
[03:42:45] tt/query/why/traverse-order.t 
.. ok   86 
ms ( 0.00 usr  0.00 sys +  0.06 cusr  0.02 csys =  0.08 CPU)



[03:42:45] tt/shell/basic.t 
... 
ok  217 ms ( 0.00 usr  0.01 sys +  0.11 cusr  0.04 csys =  0.16 CPU)
[03:42:45] tt/shell/cache-reload.t 
 ok 
 387 ms ( 0.01 usr  0.00 sys +  0.15 cusr  0.09 csys =  0.25 CPU)
[03:42:46] tt/shell/error-handling.t 
.. ok  
278 ms ( 0.01 usr  0.00 sys +  0.12 cusr  0.03 csys =  0.16 CPU)
[03:42:46] tt/shell/tokenising.t 
.. ok   
   178 ms ( 0.00 usr  0.00 sys +  0.10 cusr  0.04 csys =  0.14 CPU)
[03:42:46] tt/version.t 
...
 ok   94 ms ( 0.00 usr  0.01 sys +  0.06 cusr  0.02 csys =  0.09 CPU)
[03:42:46]

Test Summary Report
---
tt/query/repo-signatures/validation-errors.t
 (Wstat: 768 Tests: 9 Failed: 3)
  Failed tests:  1-2, 9
  Non-zero exit status: 3
Files=181, Tests=2072, 63 wallclock secs ( 0.87 usr  0.22 sys + 36.62 cusr  
7.04 csys = 44.75 CPU)
Result: FAIL
test/CMakeFiles/test.dir/build.make:60: recipe for target 
'test/CMakeFiles/test' failed
make[4]: *** [test/CMakeFiles/test] Error 1
make[4]: Leaving directory '/<>/b'
CMakeFiles/Makefile2:637: recipe for target 

Bug#902456: cf-python: FTBFS in buster/sid (AttributeError: 'module' object has no attribute 'netcdftime')

[Santiago Vila]

Package: src:cf-python
Version: 1.3.2+dfsg1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with python2,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>/cf-python-1.3.2+dfsg1'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -E -b html docs/source 
docs/build/html
Running Sphinx v1.7.5

Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 161, in 
__init__
execfile_(filename, config)
  File "/usr/lib/python2.7/dist-packages/sphinx/util/pycompat.py", line 150, in 
execfile_
exec_(code, _globals)
  File "/usr/lib/python2.7/dist-packages/six.py", line 709, in exec_
exec("""exec _code_ in _globs_, _locs_""")
  File "", line 1, in 
  File "conf.py", line 340, in 
import inspect, cf
  File "/<>/cf-python-1.3.2+dfsg1/cf/__init__.py", line 81, in 

from .variable import Variable
  File "/<>/cf-python-1.3.2+dfsg1/cf/variable.py", line 21, in 

from .query  import Query
  File "/<>/cf-python-1.3.2+dfsg1/cf/query.py", line 10, in 
from .cfdatetime import Datetime, dt
  File "/<>/cf-python-1.3.2+dfsg1/cf/cfdatetime.py", line 12, in 

from .unitsimport Units
  File "/<>/cf-python-1.3.2+dfsg1/cf/units.py", line 259, in 
_netCDF4_netcdftime_utime = netCDF4.netcdftime.utime
AttributeError: 'module' object has no attribute 'netcdftime'

debian/rules:14: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/cf-python-1.3.2+dfsg1'
debian/rules:11: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902458: django-countries: FTBFS in buster/sid ("BAD" is not a valid choice)

[Santiago Vila]

Package: src:django-countries
Version: 5.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

copying django_countries/ioc_data.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries
copying django_countries/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries
creating 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_fields.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_widgets.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_tags.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/custom_countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_settings.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/settings.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/models.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_drf.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/forms.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_admin_filters.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
creating 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
copying django_countries/templatetags/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
copying django_countries/templatetags/countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
set -e; \
for python in python2.7 python3.6; do \
  PYTHONPATH="." DJANGO_SETTINGS_MODULE=django_countries.tests.settings $python 
/usr/bin/django-admin test django_countries.tests;\
done
..F.
==
FAIL: test_multi_deserialize_invalid (django_countries.tests.test_drf.TestDRF)
--
Traceback (most recent call last):
  File "/<>/django_countries/tests/test_drf.py", line 147, in 
test_multi_deserialize_invalid
['"BAD" is not a valid choice.'])
AssertionError: {1: [ErrorDetail(string=u'"BAD" is not a valid choice.', 
code=u'invalid_choice')]} != [u'"BAD" is not a valid choice.']

--
Ran 144 tests in 0.442s

FAILED (failures=1)
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 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902401: gfsview: missing source: debian/Makefile.in

[Adrian Bunk]

On Tue, Jun 26, 2018 at 11:02:11PM +0200, Christoph Berg wrote:
> Re: Anton Gladky 2018-06-26 
> 
> > thank you for bug report. Makefile.in was needed for some reasons.
> > If it will be removed, not sure the package will compile, needs to be
> > checked.

Upstream ships debian/ and the toplevel Makefile.am has debian in SUBDIRS.

Patching the toplevel Makefile.am is an option,
but the resulting patch not be upstreamable.

I'd suggest fixing this bug with:
  rm debian/Makefile.in
  touch debian/Makefile.am
  echo debian/Makefile.in > debian/clean

> > Anyway, the file is in a human-readable format, though generated.
> > I do not think there are some legal problems with it. Thus I have
> > reduced the bug`s severity.
> 
> What about debian/Makefile.am? Does that still exist somewhere?

http://gerris.dalembert.upmc.fr/darcs/gfsview-stable/debian/Makefile.am

> Can Makefile.in be generated from it?

Yes.

> Christoph

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#639221: replace folding.el with elpa-folding

[Nicholas D Steeves]

Hi David,

On Tue, Jun 26, 2018 at 08:35:10AM -0300, David Bremner wrote:
> Nicholas D Steeves  writes:
> 
> > On Mon, Jun 25, 2018 at 02:10:22PM -0300, David Bremner wrote:
> >> 
> >> Reuben Thomas  writes:
> >> 
> >> > On 25 June 2018 at 11:50, David Bremner  wrote:
> >> >
> >> >>
> >> >> control: tag -1 moreinfo
> >> >>
> >> >> Can you confirm that this old bug is present in
> >> >>
> >> >> https://github.com/jaalto/project-emacs--folding-mode/
> >> >> blob/master/folding.el
> >> >
> >> >
> >> > ​No, I can't reproduce it. Thanks for looking into this!
> >> >
> >> 
> >> Great, thanks. I'll propose we replace folding.el with a seperate
> >> package that tracks that repo.
> >
> > Given that whatever we do will require a new source package in the
> > archive, maybe it would be a good time to consider alternative folding
> > addons?  Jaalto's project of course wins for backwards-compatibility ;-)
> 
> Let's not bring new complications into an already complicated
> project. If the same package looks viable upstream let's package that;
> it it doesn't, let's not delay things for finding/packaging
> alternatives.  Chances are the users are in a much better position to
> nominate a replacement package.

I'm not convinced this one is more suitable for the Debian archive
than the alternatives, but if you consent to being an Uploader for
Jaalto's folding-mode (continuation of the goodies one) then I'm
willing to package it:
  https://github.com/jaalto/project-emacs--folding-mode/

Going from MELPA stats (thank you again for the link):
  https://melpa.org/download_counts.json

 "folding": 3179, 
 "origami": 21948, 
 "vimish-fold": 11063,
 "yafolding": 5459, 

Origami is almost 2x more popular than the closest runner-up...  Yes,
Jaalto's folding-mode's stats are undefined, so it might be equally or
more popular.

Would you still prefer if I get to work on Jaalto's folding-mode,
and comaintain it (under team maintenance, of course)?


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#902452: Kamailio TLS module in Debian Stretch is unusable

[Pali Rohár]

Package: kamailio-tls-modules
Version: 4.4.4-2+deb9u1
Severity: grave

After installation of kamailio-tls-modules package on Debian Stretch and
enabling TLS support in kamailio.cfg via #!define WITH_TLS I'm just
getting following fatal error (in syslog):

Jun 27 00:19:57 pali /usr/sbin/kamailio[15055]: : tls [tls_init.c:651]: 
init_tls_h(): ERROR: tls: init_tls_h: openssl compile options mismatch: library 
has kerberos support disabled and Kamailio tls enabled (unstable 
configuration)#012 (tls_force_run in kamailio.cfg will override this check)
Jun 27 00:19:57 pali /usr/sbin/kamailio[15055]: CRITICAL:  [main.c:2592]: 
main(): could not initialize tls, exiting...

And kamailio refuse to start.

Therefore current version of kamailio-tls-modules package in Debian
Stretch is unusable as TLS support which it provides cannot be enabled.

It looks like this package needs to be (re)compiled against correct
version of openssl with correct configure options or it needs to runtime
depends on correct version of openssl libraries.

As package currently does not work at all, I'm marking this issue with
severity grave.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

Bug#902451: ITP: golang-github-syncthing-notify -- File system event notification library on steroids

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-syncthing-notify
  Version : 0.0~git20180626.cdf89c4-1
  Upstream Author : The Syncthing Project
* URL : https://github.com/syncthing/notify
* License : Expat
  Programming Lang: Go
  Description : File system event notification library on steroids.

This is needed for syncthing

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Alexis Murzeau]

Le 26/06/2018 à 04:13, vasudev-debian a écrit :
> I'll have a look. if possible clone from team repo and raise a pr on it.
> 

I've created 3 PR at [0], one for each branch (in this order: upstream,
pristine-tar and master).
The 5.0.10+really4.7.0~dfsg orig tar I imported is the same as the one
used for 4.7.0~dfsg.
Debian/watch file tracks the v4 branch (ignoring v5.*)
I've also added a autopkgtest test to ensure symlinks are not broken.

[0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests

Le 26/06/2018 à 09:26, Sean Whitton a écrit :
>
> The git history is up to you but resetting the changelog seems like a
> really bad idea -- it is confusing to see that there are uploads to the
> archive that are not present in the changelog.
>
> I think you should at least retain d/changelog, even if you reset
> everything else (personally, I would keep all the git history).
>

I finally kept the full changelog and git history, to not lie the past
:) if someone wonders what happened.
Thanks for your advices.

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



signature.asc
Description: OpenPGP digital signature

Bug#902450: Please install bash completion file

[Laurent Bigonville]

Package: libvirt-clients
Version: 4.3.0-1
Severity: wishlist

Hi,

During the configure you can see:

configure: bash_completion: no

And indeed, the bash completion file is not installed

Adding "bash-completion" to the build-dependencies should do the
necessary thing.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.17.0-rc5+ (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages libvirt-clients depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.12-4
ii  libaudit1   1:2.8.3-1
ii  libavahi-client30.7-4
ii  libavahi-common30.7-4
ii  libc6   2.27-3
ii  libcap-ng0  0.7.9-1
ii  libcurl3-gnutls 7.60.0-2
ii  libdbus-1-3 1.12.8-3
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libgnutls30 3.5.18-1
ii  libnl-3-200 3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libnuma12.0.11-2.2
ii  libreadline77.0-5
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3.1
ii  libselinux1 2.8-1
ii  libssh2-1   1.8.0-1
ii  libvirt04.3.0-1
ii  libxml2 2.9.4+dfsg1-7
ii  libyajl22.1.0-2+b3

libvirt-clients recommends no packages.

Versions of packages libvirt-clients suggests:
ii  libvirt-daemon  4.3.0-1

-- no debconf information

Bug#895156: easyloggingpp package

[Stephen Kitt]

Hi Hilko,

Le 26/06/2018 13:01, Hilko Bengen a écrit :

I have had a look at your effort to package easyloggingpp
(https://salsa.debian.org/debian/easyloggingpp). Apart from a missing
build-dependency on cmake, it seems to build fine, even on stretch. I
have been able to use the resulting package for building LIEF.

Are you going to upload soon?


I was waiting for clarification on the provenance of some files in the 
upstream source; I’ll remove those and upload the package in the next 
few days.


Regards,

Stephen

Bug#901952: new info

[Tomasz Buchert]

Control: reassign 901952 tar 1.30+dfsg-1

On 26/06/18 20:23, Tomasz Buchert wrote:
> On 20/06/18 21:18, Hans-Christoph Steiner wrote:
> >
> > [...]
>
> This seems to be a regression caused by tar.
>
> I can successfully checkout the tarball, but with the version tar_1.29b-2.
> When I install tar_1.30+dfsg-1, I cannot checkout anymore.
>
> I guess we'll need to find the real cause in tar then.

I believe I have a repro case extracted from this bug report showing
that #897653 was not actually fixed. It can be downloaded from:
http://ivyzdokx5queplps.onion/repro.tar.xz

It has a number of files generated with tar 1.30, with all
combinations of reproducibility related flags and none of them
reproduces the tarball produced by the version 1.29.

I'm reassigning this to tar.


signature.asc
Description: PGP signature

Bug#877418: closed by Chris Lamb (Bug#877418: fixed in strip-nondeterminism 0.039-1)

[Chris Lamb]

tags 877418 + moreinfo
thanks

Hi Rob,

> Hmm, it looks like the fix may not have been sufficient, or there's been
> a regression.
[…]
> Looking inside the jar, core.clj and derived class files, for example,
> do appear to have the same timestamps:
> 
>  580 Mon Mar 19 16:59:46 CDT 2018 clojure/core$interleave$fn__5149.class
> 1138 Mon Mar 19 16:59:46 CDT 2018 clojure/core$interleave$fn__5151.class
> 1740 Mon Mar 19 16:59:46 CDT 2018 clojure/core$interleave$fn__5154.class
> 1826 Mon Mar 19 16:59:46 CDT 2018 clojure/core$interleave.class
>   251643 Mon Mar 19 16:59:46 CDT 2018 clojure/core.clj

I can't reproduce this with strip-nondeterminism 0.042-1 and
src:clojure 1.8.0-6:

   580 Mon Jun 25 00:02:08 BST 2018 clojure/core$interleave$fn__5149.class
  1138 Mon Jun 25 00:02:08 BST 2018 clojure/core$interleave$fn__5151.class
  1740 Mon Jun 25 00:02:08 BST 2018 clojure/core$interleave$fn__5154.class
  1826 Mon Jun 25 00:02:08 BST 2018 clojure/core$interleave.class
251643 Mon Jun 25 00:02:06 BST 2018 clojure/core.clj
^^

I also can't reproduce this with src:clojure1.9 1.9.0-4:

   580 Mon Jun 25 00:56:18 BST 2018 clojure/core$interleave$fn__8515.class
  1140 Mon Jun 25 00:56:18 BST 2018 clojure/core$interleave$fn__8517.class
  1742 Mon Jun 25 00:56:18 BST 2018 clojure/core$interleave$fn__8520.class
  1826 Mon Jun 25 00:56:18 BST 2018 clojure/core$interleave.class
259697 Mon Jun 25 00:56:16 BST 2018 clojure/core.clj
^^

Any ideas? :)


Regards,

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

Bug#902449: cryptsetup-initramfs: auto-detection of zfs pool(s)

[Fabian Grünbichler]

Package: cryptsetup-initramfs
Version: 2:2.0.3-4

hello again!

still running the same setup with a fully encrypted single vdev used as
rpool. since the recent refactoring and split into
cryptsetup-{run,initramfs}, I now get the following messages on every
initramfs generation:

cryptsetup: ERROR: Couldn't normalise device rpool/ROOT/debian
cryptsetup: ERROR: Couldn't find sysfs directory corresponding to 
rpool/ROOT/debian

the initramfs is still correctly generated because I specified the
underlying physical disk in my /etc/crypttab.

I wonder whether you'd accept a patch contributing detection of zpool
devices in the cryptroot hook? it is a bit cumbersome, as the only way to
get this information from ZFS is by parsing 'zpool status' output, which
contains a lot of extra information and is not very well-defined (thus,
potential for breakage in the future).

the output looks roughly like this for a single vdev pool:

$ zpool status -P rpool
  pool: rpool
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 0h6m with 0 errors on Sun May 13 00:30:27 2018
config:

NAMESTATE READ WRITE CKSUM
rpool   ONLINE   0 0 0
  /dev/mapper/root  ONLINE   0 0 0

errors: No known data errors


for more complicated pool setups, there is an additional level of
nesting in the config section, e.g. like this:

 NAME   STATE READ WRITE CKSUM
 rpool  ONLINE   0 0 0
   mirror-0 ONLINE   0 0 0
 /dev/mapper/disk0  ONLINE   0 0 0
 /dev/mapper/disk1  ONLINE   0 0 0
   mirror-1 ONLINE   0 0 0
 /dev/mapper/disk2  ONLINE   0 0 0
 /dev/mapper/disk3  ONLINE   0 0 0

mirror-\d can alse have other forms, like raidz[23]-\d, log, cache, spare, ..

and of course some of those are optional for booting (cache, spare,
redundant vdevs depending on level of redundancy) - not sure whether the
current infrastructure is able to handle that properly?

there already is C code for parsing this exact output to retrieve a list
of underlying devices in grub2[1], which could serve as a base for
re-implementing in sh for cryptsetup-initramfs.

I'd be willing and able to whip a patch in case you are interested ;)

at the very least, it would be nice to detect this unsupported situation
and print a proper warning instead of the generic one.

1: 
https://salsa.debian.org/grub-team/grub/blob/4600d592f6eac6141e8efa503d7ef8cd9e79a3b5/grub-core/osdep/unix/getroot.c#L225

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/ROOT/debian/@/vmlinuz root=ZFS=rpool/ROOT/debian boot=zfs ro

-- /etc/crypttab
root UUID=XXX none luks,initramfs

-- /etc/fstab

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cryptsetup-initramfs depends on:
ii  busybox-static [busybox]1:1.27.2-2
ii  cryptsetup-run  2:2.0.3-4
ii  initramfs-tools [linux-initramfs-tool]  0.130

Versions of packages cryptsetup-initramfs recommends:
ii  console-setup  1.184
ii  kbd2.0.4-3

cryptsetup-initramfs suggests no packages.

-- Configuration Files:
/etc/cryptsetup-initramfs/conf-hook changed [not included]

-- no debconf information

Bug#822551: [octave] Octave crashes when user clicks plot figures

[Rafael Laboissière]

Control: tags -1 unreproducible moreinfo

* Abou Al Montacir  [2016-04-25 12:11]:


Package: octave
Version: 4.0.1-1
Severity: normal

When clicking a plot figure using big number of points (few hundreds to a few 
thousands) Octave crashes after two or three clicks. The crash is almost 
systematic on my project plots that it makes it really unusable.


There is however a workaround by exporting: LIBGL_ALWAYS_SOFTWARE=1

This looks like an issue with GL interface but I'm not sure how to debug this.

Can anyone help how to provide more information about this bug?


This problem does not seem to affect Octave 4.4.  I am tagging this 
bug report accordingly.  If no further information is provided in a 
reasonable amount of time, this bug report will be closed.


Rafael

Bug#902446: wish: delete old jackson-module-jaxb-annotations salsa repo

[Emmanuel Bourg]

Le 26/06/2018 à 23:30, Geert Stappers a écrit :

> Any hard objections  on updating obsolete repos
> with a pointer to the new git repository?

Adding a reference to the new repository in the description of the old
repository is a good idea.

Emmanuel Bourg

Bug#899269: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8

[Chad William Seys]

Thanks Dan!
  I was able to follow your tips to get Samba working again!
  I posted the config files for smb.conf and sssd.conf on the samba 
mailing list: https://lists.samba.org/archive/samba/2018-June/216623.html
  I guess this isn't really a Samba or Debian packaging bug as we're 
not following instructions from any official Samba Howto.


Chad.

Bug#902446: wish: delete old jackson-module-jaxb-annotations salsa repo

[Geert Stappers]

On Tue, Jun 26, 2018 at 11:07:16PM +0200, Emmanuel Bourg wrote:
> Le 26/06/2018 à 22:32, Geert Stappers a écrit:
> 
> > The goal is cruft reduction at Salsa
> > and prevent that time is lost on deprecated git repositories.
> 
> I don't think there is time lost on deprecated repositories, they just
> sit there for future references. I personally like preserving the
> history of what we've done in the past, so IMHO repositories shouldn't
> be deleted.

Yeah, that makes sense.


Any hard objections  on updating obsolete repos
with a pointer to the new git repository?


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Luca Boccassi]

On Sun, 2018-06-24 at 11:49 +0200, floris wrote:
> > 
> > What about the following 
> > /etc/nvidia/current/nvidia-drm-outputclass.conf
> > 
> > ---
> > Section "Files"
> > ModulePath "/usr/lib/xorg/modules/linux"
> > ModulePath "/usr/lib/xorg/modules"
> > EndSection
> > 
> > Section "OutputClass"
> > Identifier "nvidia"
> > MatchDriver"nvidia-drm"
> > Driver "nvidia"
> > EndSection
> > ---
> > 
> > That seems to work for stable ... what about sid?
> > 
> > 
> > Andreas
> 
> Hmmm, this should work, but the NVidia glx module will always be
> loaded 
> for all screens by the xserver. This will break a multiseat system
> with 
> multiple gpu vendors and maybe other glvnd dispatch goodness.

Tried this with nonglvnd + optimus + bumblebee and it works fine as far
as I can see

> Is the following situation a possibility?
> 
> Stable -> nvidia-driver (up to version 390.xx in backports),
> compatible 
> with all versions of the xserver
>   This version is shipped with a separate Files section in 
> nvidia-drm-outputclass.conf
>   If xserver 1.20 is in backports, this version can be upgraded to
> match 
> the new Testing/Sid version
> 
> Testing and Sid -> nvidia-legacy-390xx-driver, xserver > 1.20
>  -> nvidia-driver (version > 396.xx), xserver > 1.20
>   These versions will have the ModulePath option in the OutputClass 
> section. (and we can drop the glx-alternative system)
> ---
> Floris

-- 
Kind regards,
Luca Boccassi

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

Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Axel Beckert]

Control: tag -1 - moreinfo
Comtrol: severity -1 important

Hi Vincent,

Vincent Lefevre wrote:
> On 2018-06-26 16:38:05 +0200, Axel Beckert wrote:
> > Are you aware that you need to explicitly configure if a configuration
> > needs to be solely based on the ESSID? It's called "use these settings
> > for all wifis with this ESSID" or similar.
> 
> I have "Use these settings for all networks sharing this essid"
> ticked for eduroam, but it is apparently not honored.

Ok, thanks for that detail.

> > And IMNSHO it's a security feature and not a bug that wicd does use
> > only the BSSID by default. That way credentials can't be leaked to to
> > rogue access points which share the same ESSID (which is easy to do).
> 
> ... unless a certificate is used, which is my case.

Granted.

> Another issue is that here, it was a *new* BSSID (well, I assume
> because it is a place where I had never came before).

That sounds strange. I wonder if that could be triggered, if e.g. two
different eduroam APs/BSSIDs are ticked with "use these settings
for all wifis with this ESSID" but have different settings and it is
e.g. luck which one is used (unless the BSSID fits).

Will eventually test for that corner case.

> > > and when one updates the eduroam config, some old configs are not
> > > updated, and wicd can randomly use them later.
> > 
> > In which case did this happen? With an ESSID where you had the "use
> > these settings for all wifis with this ESSID" flag set or not?
> 
> See above. But I'm not aware if there is a global setting (in any
> case the local setting should have the precedence).

>From what I gather, it's just a per-ESSID setting, but I haven't yet
looked at the code how it is implemented. Will do.

> > Am I right that you say that it's not an outdated password which might
> > be leaked, but the current password which is sent in an insecure way,
> > like WEP instead of WPA?
> 
> There were some old settings with the new password and no
> certificate.

I see.

> This could have leaked. I never use WEP, always WPA2.

As far as I remember from some discussions about potential rogue
access points in general, at least WPA2 Enterprise (like with eduroam)
uses some challenge/response methods for authentication, so a leaking
of passwords should not be possible.

OTOH I know there are tons of ways how a WPA Enterprise setup can be
done (and especially that you might need to modify your eduroam ESSID
settings when moving from one university to another) and I'm
definitely not sure if all of them use challenge/response methods.

Will try to figure out if there's really a chance to leak credentials.
(I still have my doubts, but at least not honouring that "use these
settings for all wifis with this ESSID" flag is at least a not so nice
usability bug, so setting to severity to "important" for now.)

> > Which UI? WICD has several UIs (Gtk, Curses, CLI) and you filed that
> > bug report against wicd-daemon. (→ moreinfo, too)
> 
> Gtk.

Ok. I use mostly wicd-curses which IIRC shows the BSSID. Will have a
look at the Gtk interface with a focus on the BSSID.

Thanks for the additional details!

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

Bug#902410: redis: CVE-2018-12326

[Chris Lamb]

Hi security-team,

Not sure why but in an automatic update of data/CVE/list,
CVE-2018-12326 was marked as being fixed in DSA-4230-1. However, this
only fixes CVE-2018-11218 & CVE-2018-11219.

As I understand it, this therefore means we need to do the following:

 a) Release 3:3.2.6-3+deb9u2 with the additional change for
CVE-2018-12326?

 b) Update the CVE list manually?

 --- a/data/CVE/list
 +++ b/data/CVE/list
 @@ -1461,7 +1461,6 @@ CVE-2018-12327 (Stack-based buffer overflow in ntpq 
and ntpdc of NTP version 4.2
 NOTE: 
https://gist.github.com/fakhrizulkifli/9b58ed8e0354e8deee50b0eebd1c011f
 NOTE: Negligible security impact
  CVE-2018-12326 (Buffer overflow in redis-cli of Redis before 4.0.10 and 
5.x before 5.0 ...)
 -   {DSA-4230-1}
 - redis 5:4.0.10-1 (bug #902410)
 NOTE: 
https://gist.github.com/fakhrizulkifli/f831f40ec6cde4f744c552503d8698f0
 NOTE: 
https://github.com/antirez/redis/commit/9fdcc15962f9ff4baebe6fdd947816f43f730d50

 c) ... & ensure that this doesn't clobber the 3:3.2.6-3+deb9u2 upload in
stretch-proposed-updates (what happens in this case out of
interest?)


Best wishes,

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

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Cyril Brulebois]

Hi Raphaël,

Raphael Hertzog  (2018-06-26):
> I reverted the change in git:
> https://salsa.debian.org/installer-team/pkgsel/commit/2b9b594855a409fa6d03f259ccca4b1a1bd4727b

ACK, thanks for the notice.

> I haven't uploaded the package yet. I had to reword the debconf
> template.  Is the modified template fine?

I think it really should get reviewed through the usual channel
(debian-l10n-english@ if memory serves, but don't trust me on this), so
that we avoid common errors.

> _Description: Updates management on this system:
>  Applying updates on a frequent basis is an important part of keeping the
>  system secure.
>  .
>  By default, security updates are not automatically installed as you
>  have to review the security advisories before installing the updates
>  using standard package management tools. Alternatively you can install
>  the unattended-upgrades package which will install security updates
>  automatically.

The use of “you” seems to be one of the common errors I mentioned above.
We tend to avoid pointing fingers at users.

Hrm. Grepping across our packages' templates, I see a lot of “you”s so I
might just be misremembering. Or maybe we've tried hard not to introduce
new occurrences while not actively fixing pre-existing entries.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#869146: dgit: should never add .orig to the .changes more than once

[Ian Jackson]

Control: tags -1 confirmed

I managed to repro this in the test suite by passing
   -cdgit-distro.test-dummy.git-url=file:///dev/enoent/fail

(It's quite a lot of faff to arrange a situation where
--deliberately-include-questionable-history would help,
but when it is needed its lack also causes "git push" to fail.)

I observe that when I do this, I see this message:

! Push failed, while updating the remote git repository - see messages above.
! If you want to try again, you should use a new version number.

Of course if you had followed dgit's advice you would not have
experienced this but :-).  Anyway, I will fix the bug.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#902448: timidity: Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be installed

[Sven Joachim]

Package: timidity
Version: 2.14.0-5
Severity: serious

In this version, timidity-daemon has become uninstallable:

,
| $ LANG=C aptitude -s install timidity-daemon
| The following packages will be upgraded: 
|   timidity{b} timidity-daemon 
| The following packages are RECOMMENDED but will NOT be installed:
|   fluid-soundfont-gm 
| 2 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
| Need to get 676 kB of archives. After unpacking 49.2 kB will be used.
| The following packages have unmet dependencies:
|  timidity : Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be 
installed
| The following actions will resolve these dependencies:
| 
|  Keep the following packages at their current version:
| 1) timidity [2.14.0-4 (now)]  
| 2) timidity-daemon [2.14.0-4 (now)]   
| 
| 
| 
| Accept this solution? [Y/n/q/?] q
| Abandoning all efforts to resolve these dependencies.
| Abort.
`

Most likely you meant to break timidity-daemon (<= 2.14.0-1~) rather
than (>= 2.14.0-1~).


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

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

Bug#902446: wish: delete old jackson-module-jaxb-annotations salsa repo

[Emmanuel Bourg]

Le 26/06/2018 à 22:32, Geert Stappers a écrit :

> The goal is cruft reduction at Salsa
> and prevent that time is lost on deprecated git repositories.

I don't think there is time lost on deprecated repositories, they just
sit there for future references. I personally like preserving the
history of what we've done in the past, so IMHO repositories shouldn't
be deleted.

Emmanuel Bourg

Bug#902401: gfsview: missing source: debian/Makefile.in

[Christoph Berg]

Re: Anton Gladky 2018-06-26 

> thank you for bug report. Makefile.in was needed for some reasons.
> If it will be removed, not sure the package will compile, needs to be
> checked. Anyway, the file is in a human-readable format, though generated.
> I do not think there are some legal problems with it. Thus I have
> reduced the bug`s severity.

What about debian/Makefile.am? Does that still exist somewhere? Can
Makefile.in be generated from it?

Christoph

Bug#902185:

[Kyle Edwards]

On 06/26/2018 04:45 PM, Christopher Obbard wrote:

A reinstall of Debian on my main PC seemed to fix it.


I was able to fix it by booting into a recovery shell and running:

$ apt-get install systemd

which updates systemd to the latest version. I then ran

$ apt-get install

to finish reconfiguring udev.

YMMV.


My laptop boots to the WM but with no keyboard/mouse.


This is because udev is failing to start. A text-based recovery console 
will still work, and udev will work properly again once systemd is fully 
upgraded.



This is a grave bug.


Agreed.

Bug#902447: clevis-udisks2: /usr/lib/x86_64-linux-gnu/clevis-luks-udisks2 is not setuid/setgid

[Jochen Hein]

Package: clevis-udisks2
Severity: normal

Dear Maintainer,

[I'm running my tests on Ubuntu 18.04, but I'm pretty sure
it hits Debian too]

I'm playing with clevis and encrypted disks and tried to automatically
decrypt an USB stick - which did not work.

/usr/lib/x86_64-linux-gnu/clevis-luks-udisks2 will be started when
logging in according to /etc/xdg/autostart/clevis-luks-udisks2.desktop.
The program will be started with my user and fails:

$ /usr/lib/x86_64-linux-gnu/clevis-luks-udisks2
Root privileges required!

When looking at the source we have in clevis-luks-udisks2.c, line 314:


if (setgid(gid) != 0 || setegid(gid) != 0)
return EXIT_FAILURE;

if (setuid(uid) != 0 || seteuid(uid) != 0)
return EXIT_FAILURE;

After "hmod u+s /usr/lib/x86_64-linux-gnu/clevis-luks-udisks2" I can
at least start the program.  Upstream has the following report
concerning Fedora for a similar problem:
https://github.com/latchset/clevis/issues/28
https://github.com/latchset/clevis/pull/45

I think we need to install clevis-luks-udisks2 setuid root on
Debian/Ubuntu too.  Did I miss something else?

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

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

Bug#900911: ~/.cache/gnome-control-center has mode "d-w-r-xr-T" (0o1254)

[Alexander Kurtz]

On Wed, 06 Jun 2018 18:09:44 +0200 Alexander Kurtz  wrote:
> Since you already committed the fix to the packaging repo [1],
> would you maybe consider uploading a fixed version soon-ish?

Ping?

Alexander Kurtz

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

Bug#902185:

[Christopher Obbard]

this has happened to me on both my laptop and pc when doing an upgrade.

A reinstall of Debian on my main PC seemed to fix it.

My laptop boots to the WM but with no keyboard/mouse.

This is a grave bug.

Bug#902446: wish: delete old jackson-module-jaxb-annotations salsa repo

[Geert Stappers]

Package: jackson-module-jaxb-annotations
Version: 2.8.10-2
Severity: minor

Hi,

When https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901569
 ( "jackson-module-jaxb-annotations has a new home" )
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901354
 ( "RFP: jackson-modules-base -- JAVA XML libraries" )
are closed then please remove the obsolete git repos
 https://salsa.debian.org/java-team/jackson-module-jaxb-annotations
 

This bug report is a reminder, a shared ToDo item.

The goal is cruft reduction at Salsa
and prevent that time is lost on deprecated git repositories.


Cheers
Geert Stappers
DD

Bug#902445: libclojure-java: Upgrading fails in preinst

[Adrian Bunk]

Package: libclojure-java
Version: 1.9.0-4
Severity: serious

On 1.9.0-2 -> 1.9.0-4 upgrade:

Preparing to unpack .../00-libclojure-java_1.9.0-4_all.deb ...
update-alternatives: error: no alternatives for clojure
dpkg: error processing archive 
/tmp/apt-dpkg-install-Z53q9V/00-libclojure-java_1.9.0-4_all.deb (--unpack):
 new libclojure-java package pre-installation script subprocess returned error 
exit status 2

Bug#901717: closed by Hideki Yamane (Bug#901717: fixed in debootstrap 1.0.104)

[Christopher Obbard]

Hi Hideki,

I can confirm this patch fixes the initial issue, but installing some
packages with apt after gives me some issues:

/lib/ld-linux-ar/lib/ld-linux-armhf.so.3: No such file or directory

Version 1.0.101 does not cause these issues.

I will investigate this more this week and get back to you. This may
be a separate issue, though.

Cheers!

On 26 June 2018 at 13:21, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the debootstrap package:
>
> #901717: debootstrap: Version 1.0.102 breaks use of file mirrors
>
> It has been closed by Hideki Yamane .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Hideki Yamane 
>  by
> replying to this email.
>
>
> --
> 901717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901717
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Hideki Yamane 
> To: 901717-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 26 Jun 2018 12:19:15 +
> Subject: Bug#901717: fixed in debootstrap 1.0.104
> Source: debootstrap
> Source-Version: 1.0.104
>
> We believe that the bug you reported is fixed in the latest version of
> debootstrap, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 901...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Hideki Yamane  (supplier of updated debootstrap package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sun, 24 Jun 2018 20:41:13 +0900
> Source: debootstrap
> Binary: debootstrap debootstrap-udeb
> Architecture: source
> Version: 1.0.104
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Install System Team 
> Changed-By: Hideki Yamane 
> Description:
>  debootstrap - Bootstrap a basic Debian system
>  debootstrap-udeb - Bootstrap the Debian system (udeb)
> Closes: 899155 901717
> Changes:
>  debootstrap (1.0.104) unstable; urgency=medium
>  .
>* Fix /etc/machine-id mount issue (Closes: #899155)
>* Fix regression with file:/// mirror (Closes: #901717)
> Checksums-Sha1:
>  d3d1af265af066a248def5f59ed60549ca5301d1 2017 debootstrap_1.0.104.dsc
>  6dce2e5390dc1d1bdcf6ca270615775c9f14be14 73264 debootstrap_1.0.104.tar.gz
>  074ab4b2560e4e1bb2f08e1fa35850447236ebb5 5854 
> debootstrap_1.0.104_amd64.buildinfo
> Checksums-Sha256:
>  8b95ca08935bb002d726ff5c12ff99e0a5e37a1f0267d5ebd38cecefb17bc9c7 2017 
> debootstrap_1.0.104.dsc
>  fd01743c9d87aef2621c88420f896c67342c85ce24d289fad021518755801b28 73264 
> debootstrap_1.0.104.tar.gz
>  9ee32dc182365e05cb9a97bc44e44b83ce78c565d2dd575e880abb71e95b5441 5854 
> debootstrap_1.0.104_amd64.buildinfo
> Files:
>  3643a66fb173b612b5765e6a05c5b28b 2017 admin optional debootstrap_1.0.104.dsc
>  10743679b4121c9a70a0ac9690882b5f 73264 admin optional 
> debootstrap_1.0.104.tar.gz
>  bba1d6c61b1ae14983721047f9cddda2 5854 admin optional 
> debootstrap_1.0.104_amd64.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQJHBAEBCgAxFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAlsvhQsTHGhlbnJpY2hA
> ZGViaWFuLm9yZwAKCRBdMo0IKqqxQKU7EAC39+bVPMgYAMKPt7+Ke0hrya914noZ
> BuZaaVaV/3vBFfWT5qsYQDw0W6gx3FBwlD7vSBpFb8uv4XmLLtkn6cOEgfXrfPvZ
> dv8Y6G/UdT3cyggrlwM0fzI0jECVpx6pqk5/M8q44A+JoyU82M9sB4/FCQ/TLSM6
> 6tcAkJfoMNff3gUVvQ4UhYZfN1gEq2g/+l+wazh4D47d17gx0FSAlr6q40RP6nGn
> CNG4DackiuiBdQI/z77pK5SqdXrhvGw7qKyFg1vKHVR6sh5fvKS+WXhvaziEXC3v
> f8ixEBmNCtX6zxdGJt+eS8CERJtjcHscwsDMljZo8MuKxCDLiVamYq0JjHjPiB7p
> 5LiLjvpdytI2oueo1omp2Io97L3aBnxAg5i+D7nDL0Z4/xuHsf5+CGAndkiPVSuC
> NQF69zzY43wiaxUKDVyAnJ8qz/gb4Ao733255dBOYyN9ZbXHnMBJU46f17reM/Eg
> hNR185Yvdjq0WewG4957rUyW9OVUxWaBzqSHltSb0qBhC2BuNittupdiHlTzagPe
> 9a/sIw4bpyUIUE/4lGtLaAr+INPP3gk5ExksBe2yYEudUNTXwNnZvyODFww4NFK8
> Kxy/B31BP4tQutzrnmvoBIgSA/ObrbQyJWfyNcMT8KvWsiJll0Rgm3bsr3xhjoja
> 7RwX8G/BXlYp8Q==
> =GELe
> -END PGP SIGNATURE-
>
> -- Forwarded message --
> From: Christopher Obbard 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 17 Jun 2018 12:07:22 +0100
> Subject: debootstrap: Version 1.0.102 breaks use of file mirrors
> Package: debootstrap
> Version: 1.0.102
> Severity: important
>
> This is a new bug introduced in 1.0.101
>
> We use debootstrap with a custom file:// mirror to strap cross-arch
> images for SBCs, with a second call to debootstrap --second-stage.
>
> in this format:
> debootstrap --foreign --arch="armhf" "buster" 

Bug#826994: Patch updated for 0.7.9-3

[Richard Laager]

I can't speak to why this isn't being included, so I'm staying out of
that issue.

I do see one possible technical error:

/etc/init.d/zfs-share is installed in zfs-zed per the .install file, but
the debian/rules has it as -pzfsutils-linux rather than -pzfs-zed.

-- 
Richard

Bug#902444: findutils: -print0 breaks -name conditions

[Jean-Michel Vourgère]

Package: findutils
Version: 4.6.0+git+20161106-2
Severity: normal

Dear Maintainer,

I am runing periodically
> find "$dir" -type f -print0 ! -name clamav.log | xargs -0 clamdscan 
> -log="$dir/clamav.log"

But the file clamav.log is added to the list while it should be
excluded.

I traced the issue to a -print0 problem.

> find -type f -print0 ! -name clamav.log
do not remove clamav.log from the list

> find -type f ! -name clamav.log
works ok.

I expected the -print0 option not to change the logic of the -name
conditions.

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

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

Versions of packages findutils depends on:
ii  libc62.24-11+deb9u3
ii  libselinux1  2.6-3+b3

findutils recommends no packages.

Versions of packages findutils suggests:
ii  mlocate  0.26-2

-- no debconf information

Bug#902443: Please add DAEMON_OPS to the service file

[Alf Gaida]

Package: quasselcore
Severity: normal
Tags: patch

Dear maintainer,

please add DAEMON_OPTS to the service file similar to the init:

start_server() {
 start-stop-daemon --start --quiet --pidfile $PIDFILE --make-pidfile \
 --background --chuid $DAEMONUSER --exec $DAEMON \
 -- --logfile=$LOGFILE --loglevel=$LOGLEVEL --configdir=$DATADIR \
 --port=$PORT \
 $DAEMON_OPTS }

ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} --logfile=${LOGFILE} 
--loglevel=${LOGLEVEL} --port=${PORT}

should be

ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} --logfile=${LOGFILE} 
--loglevel=${LOGLEVEL} --port=${PORT} ${DAEMON_OPTS}


Cheers Alf

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

Kernel: Linux 4.17.2-towo.2-siduction-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/quassel-core.quasselcore.service 
b/debian/quassel-core.quasselcore.service
index 1bb9910..9465575 100644
--- a/debian/quassel-core.quasselcore.service
+++ b/debian/quassel-core.quasselcore.service
@@ -10,7 +10,7 @@ Group=quassel
 WorkingDirectory=/var/lib/quassel
 Environment="DATADIR=/var/lib/quassel" "LOGFILE=/var/log/quassel/core.log" 
"LOGLEVEL=Info" "PORT=4242" "LISTEN=::,0.0.0.0"
 EnvironmentFile=-/etc/default/quasselcore
-ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} --logfile=${LOGFILE} 
--loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN}
+ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} --logfile=${LOGFILE} 
--loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} ${DAEMON_OPTS}
 Restart=on-failure
 
 [Install]

Bug#902442: givaro: autopkgtest regression: /usr/bin/ld: cannot find tests/: File format not recognized

[Paul Gevers]

Source: givaro
Version: 4.0.4-1
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

Since the upload of 4.0.4-1, your package fails its autopkgtest in
testing, with the error copied below.

Could you please investigate the situation and fix it. This regression
is causing your package to have to wait 13 extra days to migrate to testing.

Thanks for consideration.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/g/givaro/511648/log.gz

autopkgtest [15:43:22]: test upstream-tests: [---
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-random.C
-lgivaro -lgmp -lgmpxx -o test-random
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-ifactor.C
-lgivaro -lgmp -lgmpxx -o test-ifactor
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-ffarith.C
-lgivaro -lgmp -lgmpxx -o test-ffarith
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-ringarith.C
-lgivaro -lgmp -lgmpxx -o test-ringarith
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-mod.C -lgivaro
-lgmp -lgmpxx -o test-mod
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-modsqroot.C
-lgivaro -lgmp -lgmpxx -o test-modsqroot
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-trunc.C
-lgivaro -lgmp -lgmpxx -o test-trunc
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-poly.C
-lgivaro -lgmp -lgmpxx -o test-poly
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-crt.C -lgivaro
-lgmp -lgmpxx -o test-crt
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-geom.C
-lgivaro -lgmp -lgmpxx -o test-geom
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-integer.C
-lgivaro -lgmp -lgmpxx -o test-integer
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-conversion.C
-lgivaro -lgmp -lgmpxx -o test-conversion
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/test-ratrecon.C
-lgivaro -lgmp -lgmpxx -o test-ratrecon
g++ -std=gnu++11 -DNDEBUG -DSTD_RECINT_SIZE=8  tests/ -lgivaro -lgmp
-lgmpxx -o test-modularmulprecomp
/usr/bin/ld: cannot find tests/: File format not recognized
collect2: error: ld returned 1 exit status
/tmp/autopkgtest-lxc.z23z52td/downtmp/build.rww/src/debian/tests/upstream-tests:190:
recipe for target 'test-modularmulprecomp' failed
make: *** [test-modularmulprecomp] Error 1
autopkgtest [15:44:00]: test upstream-tests: ---]



signature.asc
Description: OpenPGP digital signature

Bug#902441: fflas-ffpack: autopkgtest regression: make: *** No rule to make target 'test-multifile'

[Paul Gevers]

Source: fflas-ffpack
Version: 2.3.2-1
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

Since the upload of 2.3.2-1, your package fails its autopkgtest in
both unstable and testing, with the error copied below.

Could you please investigate the situation and fix it. This regression
is causing your package to have to wait 13 extra days to move to testing.

Thanks for consideration.

Paul

autopkgtest [14:55:38]: test upstream-tests: [---
g++  -fopenmp -fabi-version=6   tests/test-fdot.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fdot
g++  -fopenmp -fabi-version=6   tests/test-finit.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-finit
g++  -fopenmp -fabi-version=6   tests/test-fscal.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fscal
g++  -fopenmp -fabi-version=6   tests/test-fadd.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fadd
g++  -fopenmp -fabi-version=6   tests/test-fger.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fger
g++  -fopenmp -fabi-version=6   tests/test-ftrsv.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-ftrsv
g++  -fopenmp -fabi-version=6   tests/test-ftrtri.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-ftrtri
g++  -fopenmp -fabi-version=6   tests/test-ftrmv.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-ftrmv
g++  -fopenmp -fabi-version=6   tests/test-ftrsm.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-ftrsm
g++  -fopenmp -fabi-version=6   tests/test-ftrsm-check.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-ftrsm-check
g++  -fopenmp -fabi-version=6   tests/test-ftrmm.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-ftrmm
g++  -fopenmp -fabi-version=6   tests/test-fgemm.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fgemm
g++  -fopenmp -fabi-version=6   tests/test-fgemm-check.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-fgemm-check
g++  -fopenmp -fabi-version=6   tests/test-permutations.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-permutations
g++  -fopenmp -fabi-version=6   tests/test-compressQ.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-compressQ
g++  -fopenmp -fabi-version=6   tests/test-lu.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-lu
g++  -fopenmp -fabi-version=6   tests/test-pluq-check.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-pluq-check
g++  -fopenmp -fabi-version=6   tests/test-fsyrk.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fsyrk
g++  -fopenmp -fabi-version=6   tests/test-fsytrf.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-fsytrf
g++  -fopenmp -fabi-version=6   tests/test-invert-check.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-invert-check
g++  -fopenmp -fabi-version=6   tests/test-rankprofiles.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-rankprofiles
g++  -fopenmp -fabi-version=6   tests/test-det.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-det
g++  -fopenmp -fabi-version=6   tests/test-det-check.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-det-check
g++  -fopenmp -fabi-version=6   tests/test-echelon.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-echelon
g++  -fopenmp -fabi-version=6   tests/test-charpoly.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-charpoly
g++  -fopenmp -fabi-version=6   tests/test-charpoly-check.C  -fopenmp
-lblas -llapack -lgivaro -lgmp -lgmpxx -o test-charpoly-check
g++  -fopenmp -fabi-version=6   tests/test-minpoly.C  -fopenmp -lblas
-llapack -lgivaro -lgmp -lgmpxx -o test-minpoly
make: *** No rule to make target 'test-multifile', needed by 'all'.  Stop.
autopkgtest [14:59:09]: test upstream-tests: ---]



signature.asc
Description: OpenPGP digital signature

Bug#851677: dgit: future transforming git attributes should be disabled too

[Ian Jackson]

Control: block -1 by 851679

-- 
Ian JacksonThese opinions are my own.

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

Bug#902440: c-sig: Homepage field leads to 404 Not Found

[Ben Finney]

Source: c-sig
Version: 3.8-22
Severity: minor
Tags: upstream

The Homepage field specifies a URL that today leads to a 404 Not Found
error response.

This same URL is also mentioned in the upstream documentation, and
perhaps elsewhere in the source package; it should be changed or
removed wherever it is mentioned.

Today, the correct Homepage field value seems to be the URL
‘https://github.com/yasuhirokimura/c-sig’.

-- 
 \  “… a Microsoft Certified System Engineer is to information |
  `\ technology as a McDonalds Certified Food Specialist is to the |
_o__)   culinary arts.” —Michael Bacarella |
Ben Finney 


signature.asc
Description: PGP signature

Bug#901789: mesa: white screen when running Xfwm4 with compositing

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2018-06-19 at 20:30 +0200, Yves-Alexis Perez wrote:
> > Yves-Alexis, which xfwm4 version do you use ?
> 
> Indeed that's a good point, I'm also using xfwm4 4.13 from experimental.

I've uploaded xfwm4 4.13.0-2 which disables GL support through libepoxy (and
mesa), so the problems is workarounded, but it'd be nice if mesa could be
fixed.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlsykfEACgkQ3rYcyPpX
RFtnegf/WATo1xT7B1I4GnOpVFwGm7KSMxoTj3QX36s5dWPAVvPBcsK+M3c8GbSy
FLUkagGozPo5EqfXkviS39UJLMLAeO1eSsqrY6fOEY5IVSuFcvceD5FPYu7ughGZ
0291GvDWSTxr5+I/P4k2Mw7boPOWu6XBf4vsK/rTkJ/KsUAY+4DwdoIwG3kexIke
VqTJDrkMXT86W3sqXJYgUi7AsuoxJrE+uagdnWF8nx1cRn5jTwbUewGuRsp41pHK
RgIyp/F/BP9m9Q+pktT1fpwQKTHCZznEdMwm57Z/kDWUVFHy0RMgwrowP4bC4Mz6
nNr48yzYmseUSUYeJtoDU48YoXhsXA==
=gLwi
-END PGP SIGNATURE-

Bug#902437: xwayland: Firefox crashes Wayland on some web pages

[Steve McIntyre]

On Tue, Jun 26, 2018 at 08:50:10PM +0300, Lars Wirzenius wrote:
>Package: xwayland
>Version: 2:1.20.0-2
>Severity: important
>
>Dear Maintainer,
>
>My apologies for ruining your day with what looks like a tricky driver
>bug. I hate debugging such things, myself.
>
>I'm marking this "important", because the issue makes me not dare to
>browse the web: I've had to reboot my system several times a day
>lately. If you think it should be a lower severity, please downgrade.
>
>Also, I made a wild guess at which package to report this issue
>against, and I am so utterly, comically ignorant of everything in a
>modern Debian desktop system that I may have guessed wrongly; please
>reassign if so.
>
>I run Debian sid on two different laptops: a Lenovo Thinkpad X220, and
>a Lenovo Yoga 900. Both use an Intel graphics card or chip. For the
>past week or two, the X220 has been crashing from time to time. I
>thought it might be bad memory in the laptop, so I switched to the
>Yoga. Then the Yoga started crashing.
>
>After much headbanging and wailing, I've manged to find way to
>reproduce the crash. I use Firefox as my web browser, and certain web
>pages trigger the crash reproducibly. One such web page is here:
>
>http://johannesbrodwall.com/2018/06/24/forget-about-clean-code-lets-embrace-compassionate-code/
>
>What happens is that Firefox does not render that page, only updates
>the page title in the window title, and then becomes unresponsive.
>Menus don't react in anyway. i can't close the tab or window with
>Ctrl-W, or by clicking on the window close button. After a few more
>seconds, the whole desktop stops working, meaning that pressing the
>capslock key no longer toggles the LED. The mouse cursor may or may
>not work. If it does work, moving it to the top left corner of the
>GNOME desktop makes the mouse not work anymore. Also, the desktop does
>not do the "whoosh" feature of GNOME where it shows all windows on the
>current virtual desktop, and the "dock" on the left side of the
>screen.
>
>The machine seems to work otherwise: I can log into it via ssh, and
>run commands on the command line. I can restart gdm3 from the ssh
>session, but if I log back in, it doesn't work: I get a dark grey
>screen, no windows, and nothing else for about half a minute, and then
>it's back to the gdm3 login screen. Logging in as a different user
>seems to work.
>
>There's nothing new in dmesg output, when the crash happens. I've run
>the in-kernel memtest on the Yoga, and it resports no problems. (I've
>not bothered to run it on the X220 yet. I can, if it'd be helpful to
>you.)
>
>I reconfigured gdm3 on the Yoga to start Xorg instead of Wayland, and
>now the web page above works fine in Firefox. No crash.. The webpage
>renders fine under Wayland using Chromium.
>
>I am OK with this workaround, but I assume the bug should be fixed if
>Wayland is to be the default in Debian. The problem is reproducible
>for me. If others can reproduce it, it should be doable on any X220,
>which is, or used to be, a common laptop. I will be keeping mine
>in storage for a while, so that if there's a need, I can try new
>package versions to see if they fix the problem.
>
>Happy hunting.
>
>
>
>-- System Information:
>Debian Release: buster/sid
>  APT prefers unstable
>  APT policy: (500, 'unstable'), (500, 'stable')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
>Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
>LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>Versions of packages xwayland depends on:
>ii  libaudit1   1:2.8.3-1
>ii  libbsd0 0.9.1-1
>ii  libc6   2.27-3
>ii  libdrm2 2.4.92-1
>ii  libegl1 1.0.0+git20180308-3
>ii  libepoxy0   1.4.3-1
>ii  libgbm1 18.1.2-1
>ii  libgcrypt20 1.8.3-1
>ii  libgl1  1.0.0+git20180308-3
>ii  libpixman-1-0   0.34.0-2
>ii  libselinux1 2.8-1
>ii  libsystemd0 239-1
>ii  libwayland-client0  1.15.0-2
>ii  libxau6 1:1.0.8-1+b2
>ii  libxdmcp6   1:1.1.2-3
>ii  libxfont2   1:2.0.3-1
>ii  libxshmfence1   1.3-1
>ii  xserver-common  2:1.20.0-2

Confirmed here on a fresh install of sid on another X220...

-- 
Steve

Bug#826994: [zfsutils-linux]

[Chris Zubrzycki]

That's a workaround at best, not a solution. The scripts aren't configured with 
the Debian package so the macros are not expanded. The update-defaults command 
doesn't get run on new systems, nor do we get any upstream modifications or 
fixes.  It seems to be a well-done patch for an officially supported init 
system, I haven't heard any reason yet to not merge it.


Sent from my iPhone

> On Jun 25, 2018, at 17:23, Antonio Russo  wrote:
> 
> [snip]
>> I shouldn’t have to keep building custom versions so my pools import on 
>> boot...
> 
> If you just install the regular Debian zfs packaging, and then make sure the 
> init
> scripts are installed an enabled, they will stay enabled. (upgrading the zfs
> packaging won't disable init scripts it knows nothing about).
> 
> As frustrating as this all is, you do not need to rebuild the package just to
> install a few init scripts once per machine. If you're provisioning a large 
> number
> of machines regularly, I also sympathize, but it's still just a couple more 
> lines
> in Ansible.

Bug#902439: libpython3.7-testsuite: fails during install

[Paul Gevers]

Package: libpython3.7-testsuite
Version: 3.7.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear Python maintainers,

python3.7 is blocked¹ from migration to testing because it fails its
piuparts (and autopkgtest) test with the error below. This happens
during package installation.

Please fix libpython3.7-testsuite.

Paul

¹ https://qa.debian.org/excuses.php?package=python3.7

https://piuparts.debian.org/sid/fail/libpython3.7-testsuite_3.7.0~rc1-3.log

  Preparing to unpack .../libpython3.7-testsuite_3.7.0~rc1-3_all.deb ...
  Unpacking libpython3.7-testsuite (3.7.0~rc1-3) ...
  Setting up libpython3.7-testsuite (3.7.0~rc1-3) ...
File "/usr/lib/python3.7/idlelib/idle_test/template.py", line 3
  from idlelib import
^
  SyntaxError: invalid syntax

  dpkg: error processing package libpython3.7-testsuite (--configure):
   installed libpython3.7-testsuite package post-installation script
subprocess returned error exit status 1
  Errors were encountered while processing:
   libpython3.7-testsuite





signature.asc
Description: OpenPGP digital signature

Bug#901408: closed by Brian Potkin (Re: Bug#901408: ppd file and examples)

[Mark Copper]

The solution works for me.  Thank you. Though the necessary option,
'nopdfautorotate fit-to-page' might be a challenge for someone in userland
like me to figure out.

I should also mention again the problem arose with Stretch, not with
Jessie.  These labels printed as desired in Jessie without this option.

Thanks again.

On Tue, Jun 26, 2018 at 12:15 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the cups-filters package:
>
> #901408: cups-filters: gstoraster orientation problem
>
> It has been closed by Brian Potkin .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Brian Potkin <
> claremont...@gmail.com> by
> replying to this email.
>
>
> --
> 901408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901408
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Brian Potkin 
> To: 901408-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 26 Jun 2018 18:11:03 +0100
> Subject: Re: Bug#901408: ppd file and examples
> On Mon 25 Jun 2018 at 15:14:44 -0500, Mark Copper wrote:
>
> > Attached are two examples of pdf files that are auto-rotated 90 degrees
> no
> > matter the Custom pagesize or orientation requested on the command line.
> >
> > Also attached is the PPD file that comes with Stretch although it bears
> > mentioning that neither the Wheezy nor the Zebra supplied PPD files fare
> > any better.
> >
> > These files print either in landscape or portrait orientation as
> requested
> > by custom pagesize in Wheezy.
>
> I am working on stretch with the PPD as-provided, and using rasterview
> v1.7. tag_generator.pdf is a portrait PDF page:
>
> Page size:  90 x 144 pts
> Page rot:   0
>
> On conversion from pdf to vnd.cups-pdf the page will not be rotated by
> pdftopdf and the short edge will be fed through the printer first, as is
> the case with most printers. (The -o orientation-requested=3 option
> produces no rotation). For out.pdf
>
> Page size:  90 x 144 pts
>
> Page rot:   0
>
> For belt_advisory.pdf:
>
> Page size:  162 x 90 pts
> Page rot:   0
>
> This is a landscape PDF page. On conversion from pdf to vnd.cups-pdf the
> page will be rotated by pdftopdf and the short edge will be fed through
> the printer first. For out.pdf:
>
> Page size:  162 x 90 pts
> Page rot:   270
>
> The PPD has *LandscapeOrientation: Plus90, so the rotation is 90 degrees
> anticlockwise.
>
> I observe the behaviour you describe with both your sample PDFs. For
> example:
>
> /usr/sbin/cupsfilter -p ~/Zebra.ppd  -m application/vnd.cups-raster
> belt_advisory.pdf > out.ras
>
> The behaviour occurs because of Zebra.ppd and pdftopdf and gstoraster
> merely act on what is in that file. A solution is:
>
> /usr/sbin/cupsfilter -p ~/Zebra.ppd -m application/vnd.cups-raster -o
> 'nopdfautorotate fit-to-page' belt_advisory.pdf > out.ras
>
> Because this solution exists within the framework of cups-filters I am
> closing this report.
>
> I'll point out that wheezy CUPS is EOL and that PDF rotation is treated
> there quite differently compared to what happens on jessie and stretch.
>
> Cheers,
>
> Brian.
>
> -- Forwarded message --
> From: Mark Copper 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Tue, 12 Jun 2018 12:40:14 -0500
> Subject: cups-filters: gstoraster orientation problem
> Package: cups-filters
> Version: 1.11.6-3
> Severity: normal
>
> Dear Maintainer,
>
> This problem arose with upgrade from Jessie to Stretch.
>
> The problem I'm seeing seems to be in the CUPS filter gstoraster. That is,
> all is well at the preceding step:
>
> # /usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m
> application/vnd.cups-pdf -o orientation-requested=3 tag_generator.pdf >
> out.pdf
>
> Well, almost. It was necessary to include the "orientation-requested=3"
> option to keep the document from rotating.
>
> But at the next step, the document is laid on its side no matter the
> orientation requested:
>
> # /usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m
> application/vnd.cups-raster  out.pdf > out.ras
>
>
> Or, in more detail,
>
> # pdfinfo out.pdf
> Producer:   PDF::API2 2.023 [linux]
> Tagged: no
> UserProperties: no
> Suspects:   no
> Form:   none
> JavaScript: no
> Pages:  1
> Encrypted:  no
> Page size:  90 x 144 pts
> Page rot:   0
> File size:  14151 bytes
> Optimized:  no
> PDF version:1.4
>
> output of "/usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m
> application/vnd.cups-raster  out.pdf > out.ras" to standard error says this:
>
> DEBUG: argv[0]="cupsfilter"
> DEBUG: argv[1]="1"
> DEBUG: argv[2]="root"
> DEBUG: argv[3]="out.pdf"
> DEBUG: argv[4]="1"
> DEBUG: argv[5]=""
> DEBUG: argv[6]="out.pdf"

Bug#902438: tracker.debian.org: broken links in VCS field

[Sven Joachim]

Package: tracker.debian.org
Severity: normal

In the VCS field on https://tracker.debian.org/pkg/$package there are
three new links labeled changelog_distribution, changelog_version and
package_version.  Unfortunately they are all 404 compliant.

Bug#901952: new info

[Tomasz Buchert]

On 20/06/18 21:18, Hans-Christoph Steiner wrote:
>
> [...]

This seems to be a regression caused by tar.

I can successfully checkout the tarball, but with the version tar_1.29b-2.
When I install tar_1.30+dfsg-1, I cannot checkout anymore.

I guess we'll need to find the real cause in tar then.


signature.asc
Description: PGP signature

Bug#897928:

[Andrea Villa]

What about a package for stable?

On Tue, Jun 26, 2018 at 6:12 PM James Lu 
wrote:

> Hello,
>
> Unstable has version 5.2.12-dfsg-3 right now which supersedes[1] the
> version you mentioned. This version seems to be be blocked from testing
> because of an Xserver migration, see [2].
>
> [1]:
>
> http://metadata.ftp-master.debian.org/changelogs/contrib/v/virtualbox/unstable_changelog
> [2]: https://tracker.debian.org/pkg/virtualbox
>
> Best,
> James
>
> On 2018-06-26 05:42 AM, Andrea Villa wrote:
> > Any news on when virtualbox/5.2.10-dfsg-7 will be uploaded to the Debian
> > FTP?
> > This bug is marked as resolved, but there is no package available to
> > users with this bug fixed.
> >
> > Sincerely,
> >
> > Andrea
>

Bug#902185: (no subject)

[Kyle Edwards]

This bug broke my Sid instance, I had to use a recovery shell to 
manually upgrade systemd because udev wouldn't start. This is a 
system-breaking bug.

Bug#902399: autopkgtest --help usage differs from manpage (order of testsrc and [testbinary...])

[Paul Gevers]

Control: forcemerge 901643 -1

Hi Daniel,

Thanks for reporting issues. This one was already reported (and pending).

On 26-06-18 04:20, Daniel Kahn Gillmor wrote:
> It's quite possible that both are intended to work.  however, it would
> be cleaner if the documentation would pick one form and stick to it
> to avoid confusion.

Agreed. And indeed both work.

Paul



signature.asc
Description: OpenPGP digital signature