Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)

[Paul Wise]

On Mon, Oct 30, 2017 at 9:45 PM, Nicolas Braud-Santoni wrote:

> This RFS is a pretty good example: there was no new upstream version, and
> no review (or any sort of activity on the RFS) since June, while the timeout
> on mentors.debian.net is only 20 days.

The best you can do in that situation is bump the changelog date and reupload.

> I appreciate that Bart was likely trying to triage RFSes, but closing it
> rather than asking to reupload to mentors.d.n feels somewhat unfriendly,
> especially when the packaging repo is available, and up-to-date, on alioth.

That is a cron job that syncs the state of RFSes with the archive and
mentors. The maintainer of the cron job is fairly MIA, so I'm not sure
it will change any time soon.

> Note that I'm not mentionning that to complain or vent, but to report a
> problem that I'm encountering, as a non-DD contributor, in the hopes that
> it might be possible to fix it rather than let it affect other people.

Given the current general package sponsorship resources don't appear
to be increasing much year on year, I doubt it will ever be possible
for Debian to accept all proposed packages in a timely manner, sorry.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#879900: apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced

[Jason Cohen]

Package: apparmor-profiles-extra
Version: 1.11
Followup-For: Bug #879900

I am seeing the same behavior in Stretch:

jason@jason-desktop:/etc/apparmor.d$ /usr/bin/totem

(totem:14579): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
Segmentation fault

Syslog:

Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-0: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-0: Internal TMDS
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-1: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-1: Internal TMDS
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): Acer XB271HU (DFP-2): connected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): Acer XB271HU (DFP-2): Internal DisplayPort
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): Acer XB271HU (DFP-2): 1440.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-3: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-3: Internal TMDS
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DELL U2713HM (DFP-4): connected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DELL U2713HM (DFP-4): Internal DisplayPort
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DELL U2713HM (DFP-4): 1440.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-5: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-5: Internal TMDS
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-6: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-6: Internal DisplayPort
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-7: disconnected
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-7: Internal TMDS
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-7: 330.0 MHz maximum pixel clock
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0):
Oct 27 00:29:25 jason-desktop kernel: [   96.503531] audit_printk_skb: 10
callbacks suppressed
Oct 27 00:29:25 jason-desktop kernel: [   96.503533] audit: type=1400
audit(1509078565.921:86): apparmor="DENIED" operation="open"
profile="/usr/bin/totem" name="/proc/modules" pid=5467 comm="totem"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Oct 27 00:29:25 jason-desktop kernel: [   96.504412] audit: type=1400
audit(1509078565.921:87): apparmor="DENIED" operation="exec"
profile="/usr/bin/totem" name="/usr/bin/nvidia-modprobe" pid=5470 comm="totem"
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Oct 27 00:29:25 jason-desktop kernel: [   96.507159] audit: type=1400
audit(1509078565.925:88): apparmor="DENIED" operation="open"
profile="/usr/bin/totem" name="/proc/modules" pid=5467 comm="totem"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Oct 27 00:29:25 jason-desktop kernel: [   96.507855] audit: type=1400
audit(1509078565.925:89): apparmor="DENIED" operation="exec"
profile="/usr/bin/totem" name="/usr/bin/nvidia-modprobe" pid=5471 comm="totem"
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Oct 27 00:29:25 jason-desktop /usr/lib/gdm3/gdm-x-session[3332]: (--)
NVIDIA(GPU-0): DFP-0: disconnected
Oct 27 00:29:25 jason-desktop 

Bug#880193: Switch to Ayatana Indicators

[Mike Gabriel]

Package: mate-polkit
Version: 1.16.0-2
Severity: wishlist
Tags: patch upstream
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatanaindicators

Hi,

attached is the patch to switch over to Ayatana Indicators. This patch
also enables AppIndicator support in the code which, however, also
disables the xembed code path.

This should be improved upstream. Ideally, mate-polkit attempts to place
an Indicator icon into the indicator-renderer and if that fails it falls
back to gtk_status_icon (xembed API).

light+love,
Mike

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

Kernel: Linux 4.9.0-4-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 mate-polkit depends on:
ii  accountsservice0.6.43-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-11+deb9u1
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libgdk-pixbuf2.0-0 2.36.5-2+deb9u1
ii  libglib2.0-0   2.50.3-2
ii  libgtk-3-0 3.22.11-1
ii  libpango-1.0-0 1.40.5-1
ii  libpangocairo-1.0-01.40.5-1
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  mate-polkit-common 1.16.0-2
ii  policykit-10.105-18

mate-polkit recommends no packages.

mate-polkit suggests no packages.

-- no debconf information
diff -Nru mate-polkit-1.18.1/debian/changelog 
mate-polkit-1.18.1/debian/changelog
--- mate-polkit-1.18.1/debian/changelog 2017-07-24 15:28:52.0 +0200
+++ mate-polkit-1.18.1/debian/changelog 2017-10-30 14:39:28.0 +0100
@@ -1,3 +1,15 @@
+mate-polkit (1.18.1-2) UNRELEASED; urgency=medium
+
+  * debian/patches:
++ Add 1001_switch-to-ayatana-indicators.patch. Switch to Ayatana 
Indicators.
+  * debian/control:
++ Switch from libappindicator3-dev to libayatana-appindicator3-dev.
+  * debian/rules:
++ Set configure option --enable-appindicator to auto (which enables
+  the AppIndicator code path).
+
+ -- Mike Gabriel   Mon, 30 Oct 2017 14:39:28 +0100
+
 mate-polkit (1.18.1-1) unstable; urgency=medium
 
   [ Aron Xu ]
diff -Nru mate-polkit-1.18.1/debian/control mate-polkit-1.18.1/debian/control
--- mate-polkit-1.18.1/debian/control   2017-07-24 15:28:52.0 +0200
+++ mate-polkit-1.18.1/debian/control   2017-10-30 14:31:58.0 +0100
@@ -11,7 +11,7 @@
dpkg-dev (>= 1.16.1.1),
gobject-introspection,
gtk-doc-tools,
-   libappindicator3-dev,
+   libayatana-appindicator3-dev,
libgirepository1.0-dev,
libgtk-3-dev (>= 3.14),
libpolkit-agent-1-dev,
diff -Nru 
mate-polkit-1.18.1/debian/patches/1001_switch-to-ayatana-indicators.patch 
mate-polkit-1.18.1/debian/patches/1001_switch-to-ayatana-indicators.patch
--- mate-polkit-1.18.1/debian/patches/1001_switch-to-ayatana-indicators.patch   
1970-01-01 01:00:00.0 +0100
+++ mate-polkit-1.18.1/debian/patches/1001_switch-to-ayatana-indicators.patch   
2017-10-30 14:38:36.0 +0100
@@ -0,0 +1,44 @@
+--- a/configure.ac
 b/configure.ac
+@@ -148,10 +148,10 @@
+ AM_CONDITIONAL([HAVE_ACCOUNTSSERVICE], [test "x$enable_accountsservice" = 
xyes])
+ 
+ # Application indicator
+-APPINDICATOR_PKG=appindicator3-0.1
++APPINDICATOR_PKG=ayatana-appindicator3-0.1
+ 
+ AC_ARG_ENABLE([appindicator],
+-
AS_HELP_STRING([--enable-appindicator[=@<:@no/auto/yes@:>@]],[Build support for 
application indicators]),
++
AS_HELP_STRING([--enable-appindicator[=@<:@no/auto/yes@:>@]],[Build support for 
Ayatana Indicators]),
+ [enable_appindicator=$enableval],
+ [enable_appindicator="auto"])
+ 
+@@ -165,7 +165,7 @@
+ if test "x$enable_appindicator" = "xyes"; then
+   PKG_CHECK_MODULES(APPINDICATOR,
+ [$APPINDICATOR_PKG >= $APPINDICATOR_REQUIRED],
+-[AC_DEFINE(HAVE_APPINDICATOR, 1, [Have 
AppIndicator])])
++[AC_DEFINE(HAVE_APPINDICATOR, 1, [Have Ayatana 
AppIndicator])])
+ fi
+ 
+ AM_CONDITIONAL(HAVE_APPINDICATOR, test "x$enable_appindicator" = "xyes")
+@@ -247,7 +247,7 @@
+ cppflags:   ${CPPFLAGS}
+ 
+ Accountsservice:${enable_accountsservice}
+-Application indicator:  ${enable_appindicator}
++Ayatana AppIndicator:   ${enable_appindicator}
+ Maintainer mode:${USE_MAINTAINER_MODE}
+ Building api docs:  ${enable_gtk_doc}
+ GObject Introspection:  ${enable_introspection}
+--- a/src/main.c
 b/src/main.c
+@@ -30,7 +30,7 @@
+ #include 
+ 
+ #ifdef HAVE_APPINDICATOR
+-#include 
++#include 
+ #endif
+ 
+ #include 

Bug#880192: xrootconsole: UTF-8

[Ricardo Fabian Peliquero]

Package: xrootconsole
Version: 1:0.6-4
Severity: minor

Dear Maintainer,

Please consider adding support for Unicode symbols. E.g.: for properly 
displaying ansiweather(1) output.

Kindest regards,

Ricardo

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

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

Versions of packages xrootconsole depends on:
ii  libc6 2.25-0experimental3
ii  libx11-6  2:1.6.4-3

xrootconsole recommends no packages.

Versions of packages xrootconsole suggests:
pn  ccze | logo  

-- no debconf information

Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)

[Nicolas Braud-Santoni]

Hi pabs,

On Sat, Oct 28, 2017 at 08:51:03PM +0800, Paul Wise wrote:
> 
> Even if you haven't got a sponsor yet, RFS submitters should still be
> maintaining the packages as they would if they were in the archive.
> That means updating to new upstreams, fixing any review comments,
> checking with new versions of lintian, running static analysis tools
> and fixing issues etc.

That's entirely fair.
(And I've done that much, though I recently discovered my lintian setup
 was suboptimal, and didn't report some issues, which are since fixed.)


> Those updates should prevent you from ever hitting the inactivity timeout
> on mentors.

This RFS is a pretty good example: there was no new upstream version, and
no review (or any sort of activity on the RFS) since June, while the timeout
on mentors.debian.net is only 20 days.

I appreciate that Bart was likely trying to triage RFSes, but closing it
rather than asking to reupload to mentors.d.n feels somewhat unfriendly,
especially when the packaging repo is available, and up-to-date, on alioth.


Note that I'm not mentionning that to complain or vent, but to report a
problem that I'm encountering, as a non-DD contributor, in the hopes that
it might be possible to fix it rather than let it affect other people.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#880191: python-os-win: FTBFS: ImportError: No module named pep8

[Andreas Beckmann]

Source: python-os-win
Version: 2.2.0-1
Severity: serious

Hi,

python-os-win/experimental FTBFS in a clean minimal sid+experimental
environment:

==
FAIL: unittest2.loader._FailedTest.os_win.tests.unit.test_hacking
unittest2.loader._FailedTest.os_win.tests.unit.test_hacking
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: os_win.tests.unit.test_hacking
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "os_win/tests/unit/test_hacking.py", line 21, in 
import pep8
ImportError: No module named pep8


--
Ran 766 tests in 6.330s

FAILED (failures=1, skipped=1)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas


python-os-win_2.2.0-1.log.gz
Description: application/gzip

Bug#687421: printer-driver-hpcups: cannot set reverse-order printing in ppd

[Sanjoy Mahajan]

On 2017-10-30 13:19, Brian Potkin  wrote:

>> The printer is an HP PSC 2710 all-in-one scanner/fax/inkjet printer.
>> I'm filing the bug against printer-driver-hpcups because the PPD has
>> this line:
>
> HP Photosmart 2700?

Pretty much -- it was actually a PhotoSmart 2710:



> I reckon page management is more the province of the pdftopdf filter
> than the hpcups driver. Anyway, I set up a print queue and did (as
> root) on unstable:
>
>  cupsfilter -p /etc/cups/ppd/2700.ppd -m application/vnd.cups-pdf 
> /etc/services > test.pdf
>
> with *DefaultOutputOrder: "reverse" in the PPD. The PDF shows the pages
> in reverse order. Perhaps you could actually print some small file to
> the printer, which I cannot do, to test this observation.

I wrote "was" above, because in the intervening years I gave away the
PSC 2710 (and now use a USB scanning stick for that functionality).  So,
I am in the same boat as you are.

-Sanjoy

Bug#880190: python-karborclient: missing B-D: openstack-pkg-tools

[Andreas Beckmann]

Source: python-karborclient
Version: 0.6.0-1
Severity: serious
Justification: fails to build from source

python-karborclient FTBFS with

 fakeroot debian/rules clean
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
dh clean --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_auto_clean -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
ERROR:root:Error parsing
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pbr/core.py", line 111, in pbr
attrs = util.cfg_to_args(path, dist.script_args)
  File "/usr/lib/python2.7/dist-packages/pbr/util.py", line 249, in cfg_to_args
pbr.hooks.setup_hook(config)
  File "/usr/lib/python2.7/dist-packages/pbr/hooks/__init__.py", line 25, in 
setup_hook
metadata_config.run()
  File "/usr/lib/python2.7/dist-packages/pbr/hooks/base.py", line 27, in run
self.hook()
  File "/usr/lib/python2.7/dist-packages/pbr/hooks/metadata.py", line 26, in 
hook
self.config['name'], self.config.get('version', None))
  File "/usr/lib/python2.7/dist-packages/pbr/packaging.py", line 755, in 
get_version
name=package_name))
Exception: Versioning for this project requires either an sdist tarball, or 
access to an upstream git repository. It's also possible that there is a 
mismatch between the package name in setup.cfg and the argument given to 
pbr.version.VersionInfo. Project name python-karborclient was given, but was 
not able to be found.
error in setup command: Error parsing 
/build/python-karborclient-0.6.0/setup.cfg: Exception: Versioning for this 
project requires either an sdist tarball, or access to an upstream git 
repository. It's also possible that there is a mismatch between the package 
name in setup.cfg and the argument given to pbr.version.VersionInfo. Project 
name python-karborclient was given, but was not able to be found.
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 1


Andreas


python-karborclient_0.6.0-1.log.gz
Description: application/gzip

Bug#879916: Debian mirror debian.mirror.su.se: inconsistent view between backends - SRQ-1283517

[Johan Wassberg]

> If you look at our monitoring result page for your mirror right now:
>  
> https://mirror-master.debian.org/status/mirror-info/debian.mirror.su.se.html
> 
> you'll notice that our script sees two different trace files from your
> mirror, alternatingly.
> 
> One from 2017-10-27 04:21:39 and one from 2017-10-27 04:21:40.
> 
> If you load balance behind a single name, is there any way you can
> ensure that all instances provide the same content?

Yes, the service is load balanced between two hosts. I didn't thought
that should be a problem.

> 
> Alternatively, is there a way we can access the backends indivually for
> our checks?

We can go either way, which ever you prefer.
1. Set up a master-slave senario where we only sync upstream from one
   of our machines and only front machines that are up to date.
2. Allow http access directly to the machines without the load balancer.

How do you normally handle this kind of issues?

--
jocar

Bug#880164: Debian mirror mirror.sucs.swan.ac.uk: unavailable

[Imran Hussain]

Hello,

Yeah our upstream connection died taking our whole /24 off the internet 
:(


All stable since about 11AM GMT.

I've also added an alias - http://mirror.sucs.org/debian/

Thanks,
Imran

On 30.10.2017 08:48, Peter Palfrader wrote:

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org

Hi!

It seems your Debian mirror mirror.sucs.swan.ac.uk is currently
not available.

Status:

https://mirror-master.debian.org/status/mirror-info/mirror.sucs.swan.ac.uk.html

Please investigate.


Also, almost all Debian mirrors offer the debian tree as /debian.
Could you create an alias for /pub/linux/debian/ as /debian/?  This 
will

make it easier for people to switch between mirrors.

Cheers,


--
Imran Hussain
https://sucs.org

Bug#880189: python-oslo.privsep: FTBFS: no theme named 'openstackdocs' found (missing theme.conf?)

[Andreas Beckmann]

Source: python-oslo.privsep
Version: 1.22.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.privsep/experimental FTBFS in a clean minimal
sid+experimental environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.privsep-1.22.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.privsep-doc/usr/share/doc/python-oslo.privsep-doc/html
Running Sphinx v1.6.3
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt
loading pickled environment... not yet created

Theme error:
no theme named 'openstackdocs' found (missing theme.conf?)
debian/rules:31: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1
make[1]: Leaving directory '/build/python-oslo.privsep-1.22.0'


Andreas


python-oslo.privsep_1.22.0-1.log.gz
Description: application/gzip

Bug#880186: Acknowledgement (gimp: screenshot does not work with wayland)

[Scott Moser]

The gimp upstream bug is 757687.
It has more information on the fix.

https://bugzilla.gnome.org/show_bug.cgi?id=757687

Bug#880187: Switch to Ayatana Indicators

[Mike Gabriel]

Package: mate-indicator-applet
Version: 1.18.0-1
Severity: wishlist
Tags: upstream patch
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatanaindicators

Attached is the patch for building MATE's Indicator Applet against
Ayatana Indicators.

light+love
Mike

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

Kernel: Linux 4.9.0-4-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 mate-indicator-applet depends on:
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u1
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u1
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libindicator3-7   0.5.0-3+b1
ii  libmate-panel-applet-4-1  1.16.2-1
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libx11-6  2:1.6.4-3
ii  mate-indicator-applet-common  1.18.0-1
ii  mate-panel1.16.2-1

mate-indicator-applet recommends no packages.

mate-indicator-applet suggests no packages.

-- no debconf information
diff -Nru mate-indicator-applet-1.18.1/debian/changelog 
mate-indicator-applet-1.18.1/debian/changelog
--- mate-indicator-applet-1.18.1/debian/changelog   2017-10-30 
14:11:23.0 +0100
+++ mate-indicator-applet-1.18.1/debian/changelog   2017-10-30 
14:19:40.0 +0100
@@ -1,3 +1,13 @@
+mate-indicator-applet (1.18.1-2) UNRELEASED; urgency=medium
+
+  * debian/patches:
++ Add 1001_AyatanaIndicators-support.patch. Switch to Ayatana Indicators.
+  * debian/control:
++ Switch to Ayatana Indicators (libido -> libayatana-ido, libindicator ->
+  libayatana-indicator).
+
+ -- Mike Gabriel   Mon, 30 Oct 2017 14:19:40 +0100
+
 mate-indicator-applet (1.18.1-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru mate-indicator-applet-1.18.1/debian/control 
mate-indicator-applet-1.18.1/debian/control
--- mate-indicator-applet-1.18.1/debian/control 2017-07-27 23:20:22.0 
+0200
+++ mate-indicator-applet-1.18.1/debian/control 2017-10-30 14:19:24.0 
+0100
@@ -11,8 +11,8 @@
dpkg-dev (>= 1.16.1.1),
intltool,
libgtk-3-dev,
-   libido3-0.1-dev,
-   libindicator3-dev,
+   libayatana-ido3-0.1-dev,
+   libayatana-indicator3-dev,
libmate-panel-applet-dev (>= 1.18),
libtool,
libx11-dev,
diff -Nru 
mate-indicator-applet-1.18.1/debian/patches/2001_AyatanaIndicators-support.patch
 
mate-indicator-applet-1.18.1/debian/patches/2001_AyatanaIndicators-support.patch
--- 
mate-indicator-applet-1.18.1/debian/patches/2001_AyatanaIndicators-support.patch
1970-01-01 01:00:00.0 +0100
+++ 
mate-indicator-applet-1.18.1/debian/patches/2001_AyatanaIndicators-support.patch
2017-10-30 14:18:58.0 +0100
@@ -0,0 +1,123 @@
+--- a/configure.ac
 b/configure.ac
+@@ -27,7 +27,7 @@
+ GTK_REQUIRED_VERSION=3.14.0
+ PANEL_REQUIRED_VERSION=1.17.0
+ INDICATOR_REQUIRED_VERSION=0.3.90
+-INDICATOR_NG_VERSION=12.10.2
++INDICATOR_NG_VERSION=0.6.0
+ 
+ PKG_CHECK_MODULES(APPLET, gtk+-3.0 >= $GTK_REQUIRED_VERSION
+   x11
+@@ -37,16 +37,16 @@
+ AC_SUBST(APPLET_CFLAGS)
+ AC_SUBST(APPLET_LIBS)
+ 
+-PKG_CHECK_EXISTS(indicator3-0.4 >= $INDICATOR_NG_VERSION,
++PKG_CHECK_EXISTS(ayatana-indicator3-0.4 >= $INDICATOR_NG_VERSION,
+  [have_indicator_ng="yes"],
+  [have_indicator_ng="no"])
+ 
+ if test "x$have_indicator_ng" = "xyes"; then
+-PKG_CHECK_MODULES(INDICATOR, indicator3-0.4 >= $INDICATOR_NG_VERSION
+-  libido3-0.1 >= 13.10,
++PKG_CHECK_MODULES(INDICATOR, ayatana-indicator3-0.4 >= 
$INDICATOR_NG_VERSION
++  libayatana-ido3-0.4 >= 0.4.0,
+   [AC_DEFINE(HAVE_INDICATOR_NG, 1, "New style indicators 
support")])
+ else
+-PKG_CHECK_MODULES(INDICATOR, indicator3-0.4 >= 
$INDICATOR_REQUIRED_VERSION)
++PKG_CHECK_MODULES(INDICATOR, ayatana-indicator3-0.4 >= 
$INDICATOR_REQUIRED_VERSION)
+ fi
+ 
+ AC_SUBST(INDICATOR_CFLAGS)
+@@ -64,11 +64,11 @@
+ ###
+ 
+ if test "x$with_localinstall" = "xyes"; then
+-  INDICATORDIR="${libdir}/indicators/2/"
+-  INDICATORICONSDIR="${datadir}/indicator-applet/icons/"
++  INDICATORDIR="${libdir}/ayatana-indicators3/7/"
++  INDICATORICONSDIR="${datadir}/libayatana-indicator/icons/"
+ else
+-  INDICATORDIR=`$PKG_CONFIG --variable=indicatordir indicator3-0.4`
+-  INDICATORICONSDIR=`$PKG_CONFIG 

Bug#880188: python-oslo.middleware: FTBFS: Could not import extension openstackdocstheme

[Andreas Beckmann]

Source: python-oslo.middleware
Version: 3.30.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.middleware/experimental FTBFS in a clean minimal
sid+experimental environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.middleware-3.30.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.middleware-doc/usr/share/doc/python-oslo.middleware-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt

Extension error:
Could not import extension openstackdocstheme (exception: No module named 
openstackdocstheme)
debian/rules:48: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1


Andreas


python-oslo.middleware_3.30.0-1.log.gz
Description: application/gzip

Bug#880186: gimp: screenshot does not work with wayland

[Scott Moser]

Package: gimp
Version: 2.8.20-1
Severity: important

Dear Maintainer,

If you are running gimp under wayland, and you select
  Create -> Screenshot

It is not able to select X windows, and a screenshot of the whole
screen will be completely black.

There is a fedora bug covering this at
  https://bugzilla.redhat.com/show_bug.cgi?id=1398556

This is reported to be fixed in the latest upstream release (2.9.4).
Fedora seems to have the patch to add support against their 2.8.22
version at
 
http://pkgs.fedoraproject.org/cgit/rpms/gimp.git/tree/gimp-2.8.22-fix-screenshot-in-wayland.patch


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

Kernel: Linux 4.13.0-16-generic (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 gimp depends on:
ii  gimp-data2.8.20-1
ii  libaa1   1.4p5-44build1
ii  libbabl-0.1-00.1.30-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.26-0ubuntu2
ii  libcairo21.15.8-2
ii  libdbus-1-3  1.10.22-1ubuntu1
ii  libdbus-glib-1-2 0.108-2
ii  libexif120.6.21-2.1
ii  libfontconfig1   2.12.6-0ubuntu1
ii  libfreetype6 2.8-0.2ubuntu2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libgegl-0.3-00.3.20-1
ii  libgimp2.0   2.8.20-1
ii  libglib2.0-0 2.54.1-1ubuntu1
ii  libgs9   9.21~dfsg+1-0ubuntu3
ii  libgtk2.0-0  2.24.31-2ubuntu1
ii  libgudev-1.0-0   1:232-1
ii  libjpeg8 8c-2ubuntu8
ii  liblcms2-2   2.7-1ubuntu1
ii  libmng2  2.0.2-0ubuntu3
ii  libpango-1.0-0   1.40.12-1
ii  libpangocairo-1.0-0  1.40.12-1
ii  libpangoft2-1.0-01.40.12-1
ii  libpng16-16  1.6.34-1
ii  libpoppler-glib8 0.57.0-2ubuntu4
ii  librsvg2-2   2.40.18-1
ii  libtiff5 4.0.8-6
ii  libwmf0.2-7  0.2.8.4-10.6ubuntu2
ii  libx11-6 2:1.6.4-3
ii  libxcursor1  1:1.1.14-3
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  python   2.7.14-2ubuntu1
ii  python-gtk2  2.24.0-5.1ubuntu1
ii  python2.72.7.14-2ubuntu2
ii  zlib1g   1:1.2.11.dfsg-0ubuntu2

Versions of packages gimp recommends:
ii  ghostscript  9.21~dfsg+1-0ubuntu3

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
ii  gvfs-backends 1.34.1-1ubuntu1
ii  libasound21.1.3-5

-- no debconf information

Bug#880157: freerdp2: Please disable ffmpeg on Ubuntu

[Jeremy Bicha]

On Mon, Oct 30, 2017 at 5:15 AM, Mike Gabriel
 wrote:
> Thanks for those patches. And what about debian/control? There is still a
> B-D on libgsm1-dev in debian/control.

The Build-Depends are fine as is. Shortly before the Ubuntu 16.04 LTS
release, Ubuntu changed policy to allow universe build dependencies as
long as the resulting binaries don't end up with dependencies on
universe packages.

Here's a build log in Ubuntu with the patch I submitted here (click
amd64 then build log):

https://launchpad.net/ubuntu/+source/freerdp2/2.0.0~git20170725.1.1648deb+dfsg1-5ubuntu2

Thanks,
Jeremy Bicha

Bug#880159: Pending

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 pending

The bug is already fixed and uploaded to the archive, will arrive soon.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#880185: python-oslo.service: FTBFS: Could not import extension openstackdocstheme

[Andreas Beckmann]

Source: python-oslo.service
Version: 1.25.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.service/experimental FTBFS in a minimal clean
sid+experimental environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.service-1.25.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.service-doc/usr/share/doc/python-oslo.service-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt

Extension error:
Could not import extension openstackdocstheme (exception: No module named 
openstackdocstheme)
debian/rules:41: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1
make[1]: Leaving directory '/build/python-oslo.service-1.25.0'


Andreas


python-oslo.service_1.25.0-1.log.gz
Description: application/gzip

Bug#687421: printer-driver-hpcups: cannot set reverse-order printing in ppd

[Brian Potkin]

Thank you for the re-submission of your report, Sanjoy,



On Wed 12 Sep 2012 at 11:17:18 -0400, Sanjoy Mahajan wrote:

> Package: printer-driver-hpcups
> Version: 3.12.6-3
> Severity: normal
> 
> From Bug#522595 (closed by Brian Potkin):
> 
> > This bug report was submitted against a version of CUPS that is no
> > longer supported in Debian.
> 
> Fair enough.

Your understanding is appreciated.

> I just retested it with cups 1.5.3-1 and cups-filters 1.0.18-2+b1 (both
> from testing/unstable).  The problem is the same -- repeated below for
> convenience:
> 
> With or without the magic line
> 
>   *DefaultOutputOrder: "reverse"
> 
> in /etc/cups/psc.ppd, the pages come out in 'normal' order (first page
> first).  However, the lp option '-o output-order=reverse' does reverse
> the order. e.g. this works fine:
> 
>   lp -o output-order=reverse -o page-ranges=123-184 book-indexing.pdf
> 
> (but it doesn't matter whether the ppd has the DefaultOutputOrder line).
> 
> The printer is an HP PSC 2710 all-in-one scanner/fax/inkjet printer.
> I'm filing the bug against printer-driver-hpcups because the PPD has
> this line:

HP Photosmart 2700?
 
>   *cupsFilter: "application/vnd.cups-raster 0 hpcups"
> 
> and hpcups is in the printer-driver-hpcups package.

I reckon page management is more the province of the pdftopdf filter
than the hpcups driver. Anyway, I set up a print queue and did (as
root) on unstable:

 cupsfilter -p /etc/cups/ppd/2700.ppd -m application/vnd.cups-pdf /etc/services 
> test.pdf

with *DefaultOutputOrder: "reverse" in the PPD. The PDF shows the pages
in reverse order. Perhaps you could actually print some small file to
the printer, which I cannot do, to test this observation.

Cheers,

Brian.

Bug#880184: ITP: python-twilio -- Twilio API client and TwiML generator

[Sophie Brun]

Package: wnpp
Severity: wishlist
Owner: Sophie Brun 

* Package name: python-twilio
  Version : 6.8.2
  Upstream Author : Twilio, Inc.
* URL : https://github.com/twilio/twilio-python
* License : MIT
  Programming Lang: Python
  Description : Twilio API client and TwiML generator

This package is a Python module for communicating with the Twilio API and
generating valid TwiML.

It's a dependency for elastalert package (ITP #876963).
I plan to maintain this package in the Python Modules Team.

Bug#848327: RFS: libu2f-host/1.1.4-1 [RC]

[Nicolas Braud-Santoni]

Control: tags -1 + pending

This has been uploaded to NEW by jcc@

Thanks  <3


signature.asc
Description: PGP signature

Bug#880183: python-oslo.log: FTBFS with sphinx 1.6.5

[Andreas Beckmann]

Source: python-oslo.log
Version: 3.30.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.log/experimental FTBFS in a clean minimal sid+experimental
environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.log-3.30.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.log-doc/usr/share/doc/python-oslo.log-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt
connecting events for openstackdocstheme
loading pickled environment... not yet created
Using openstackdocstheme Sphinx theme from 
/usr/lib/python2.7/dist-packages/openstackdocstheme/theme
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 21 source files that are out of date
updating environment: 21 added, 0 changed, 0 removed
reading sources... [  4%] admin/advanced_config
reading sources... [  9%] admin/example_nova
reading sources... [ 14%] admin/index
reading sources... [ 19%] admin/journal
reading sources... [ 23%] configuration/index
reading sources... [ 28%] contributor/index
reading sources... [ 33%] index
reading sources... [ 38%] install/index
reading sources... [ 42%] reference/fixtures
reading sources... [ 47%] reference/formatters
reading sources... [ 52%] reference/handlers
reading sources... [ 57%] reference/helpers
reading sources... [ 61%] reference/index
reading sources... [ 66%] reference/log
reading sources... [ 71%] reference/versionutils
reading sources... [ 76%] reference/watchers
reading sources... [ 80%] user/examples
reading sources... [ 85%] user/history
reading sources... [ 90%] user/index
reading sources... [ 95%] user/migration
reading sources... [100%] user/usage

WARNING: Could not load oslo.log
/build/python-oslo.log-3.30.0/doc/source/user/history.rst:7: WARNING: Problems 
with "include" directive path:
InputError: [Errno 2] No such file or directory: 'ChangeLog'.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  4%] admin/advanced_config
fatal: Not a git repository (or any of the parent directories): .git
writing output... [  9%] admin/example_nova
writing output... [ 14%] admin/index
writing output... [ 19%] admin/journal
writing output... [ 23%] configuration/index
writing output... [ 28%] contributor/index
writing output... [ 33%] index
writing output... [ 38%] install/index
writing output... [ 42%] reference/fixtures
writing output... [ 47%] reference/formatters
writing output... [ 52%] reference/handlers
writing output... [ 57%] reference/helpers
writing output... [ 61%] reference/index
writing output... [ 66%] reference/log
writing output... [ 71%] reference/versionutils
writing output... [ 76%] reference/watchers
writing output... [ 80%] user/examples
writing output... [ 85%] user/history
writing output... [ 90%] user/index
writing output... [ 95%] user/migration
writing output... [100%] user/usage
WARNING: Cannot get gitsha from git repository.
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated
/build/python-oslo.log-3.30.0/doc/source/user/index.rst:7: WARNING: toctree 
contains reference to document u'user/history' that doesn't have a title: no 
link will be generated

Exception occurred:
  File "/usr/lib/python2.7/dist-packages/oslo_config/sphinxext.py", line 435, 
in resolve_xref
env.domaindata['oslo.config']['options'][target],
KeyError: u'DEFAULT.logging_default_format_string'
The full traceback has been saved in /tmp/sphinx-err-TXkf99.log, if you want to 
report the issue to the developers.
Please also report this if it 

Bug#880182: python-os-api-ref: FTBFS: tests fail with UnicodeDecodeError

[Andreas Beckmann]

Source: python-os-api-ref
Version: 1.4.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-os-api-ref/experimental FTBFS in a clean minimal sid+experimental
environment:

==
FAIL: os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
--
_StringException: Empty attachments:
  stderr
  stdout

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line 143, in 
decorator
func(*(args + (app, status, warning)), **kwargs)
  File "/build/python-os-api-ref-1.4.0/os_api_ref/tests/test_warnings.py", line 
41, in setUp
self.html = (app.outdir / 'index.html').read_text()
  File "/usr/lib/python3/dist-packages/sphinx_testing/path.py", line 161, in 
read_text
return f.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 5094: 
ordinal not in range(128)


--
Ran 17 tests in 5.951s

FAILED (failures=16)
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas


python-os-api-ref_1.4.0-1.log.gz
Description: application/gzip

Bug#880181: gnome-shell-extension-tilix-dropdown: Reacts in german Umlaut "ä"

[Christian Lauinger]

Package: gnome-shell-extension-tilix-dropdown
Version: 5.1-1
Severity: normal
Tags: upstream

Dear Maintainer,


   * What led up to the situation?
configured the dead circumflex ("^") key to open the dropdown terminal
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
NA
   * What was the outcome of this action?
it also opens when I press the german Umlaut "ä"
   * What outcome did you expect instead?
it only reacts on dead circumflex and no other keys




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

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

Versions of packages gnome-shell-extension-tilix-dropdown depends on:
ii  gnome-shell  3.26.1-3
ii  tilix1.6.4-2

gnome-shell-extension-tilix-dropdown recommends no packages.

gnome-shell-extension-tilix-dropdown suggests no packages.

-- debconf-show failed

Bug#877350: Suggested wording

[Clint Adams]

On Sun, Oct 29, 2017 at 06:51:43PM +, Jonathan Wiltshire (Front Desk) wrote:
> Too many 'unfortunately's here; I suggest just to drop the first word of
> the latter paragraph.

I agree.

Bug#880152: flash-kernel: please echo cmdline before starting the kernel

[eamanu15 .]

Hello,
It would be interest have  I litle more information when Debian boot.

I have some questions:

* Booting is really quickly, does the user have time to read this line?
What is the advantage?
* Is this information written in any file that the user could  read when
Debian is running already?


El dom., 29 de oct. de 2017 a la(s) 22:39, Adam Borowski <
kilob...@angband.pl> escribió:

> Package: flash-kernel
> Version: 3.87
> Severity: wishlist
>
> Hi!
> It would be nice if you could echo kernel cmdline before passing control.
> Currently there's:
> echo "Booting Debian from ${devtype} ${devnum}:${partition}..."
> I can edit the bootscript myself, but having this by default would help
> anyone who sees:
>
> .
> Found U-Boot script /boot.scr
> 3075 bytes read in 17 ms (175.8 KiB/s)
> ## Executing script at 5000
> 4883208 bytes read in 191 ms (24.4 MiB/s)
> 54983 bytes read in 28 ms (1.9 MiB/s)
> 5465464 bytes read in 204 ms (25.5 MiB/s)
> Booting Debian 4.14.0-rc7-01315-g371bf91a0a3f from mmc 0:1...
> Kernel image @ 0x4200 [ 0x00 - 0x4a8308 ]
> ## Flattened Device Tree blob at 4300
>Booting using the fdt blob at 0x4300
>Loading Ramdisk to 4fac9000, end 4578 ... OK
>Loading Device Tree to 4fab8000, end 4fac86c6 ... OK
>
> Starting kernel ...
>
> `
> then nothing.
>
> (This particular board uses bootscript.odroid, but this extra line can't
> hurt elsewhere.)
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500,
> 'testing'), (1, 'experimental')
> Architecture: armhf (armv7l)
>
> Kernel: Linux 4.14.0-rc3-00467-gdcd7e571b12b (SMP w/4 CPU cores; PREEMPT)
> 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)
>
> Versions of packages flash-kernel depends on:
> ii  debconf [debconf-2.0]  1.5.64
> ii  devio  1.2-1.2+b1
> ii  initramfs-tools0.130
> ii  linux-base 4.5
> ii  mtd-utils  1:2.0.1-1
> ii  ucf3.0036
>
> Versions of packages flash-kernel recommends:
> ii  u-boot-tools  2017.09+dfsg1-3
>
> flash-kernel suggests no packages.
>
> -- debconf information:
>   flash-kernel/linux_cmdline: quiet
>
> --
Arias Emmanuel
http://eamanu.com

Bug#880180: python-searchlightclient: missing B-D: openstack-pkg-tools

[Andreas Beckmann]

Source: python-searchlightclient
Version: 1.2.0-1
Severity: serious
Justification: fails to build from source

python-searchlightclient FTBFS with

 fakeroot debian/rules clean
debian/rules:4: /usr/share/openstack-pkg-tools/pkgos.make: No such file or 
directory
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
debian/rules:7: recipe for target '/usr/share/openstack-pkg-tools/pkgos.make' 
failed
make: *** [/usr/share/openstack-pkg-tools/pkgos.make] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


Andreas


python-searchlightclient_1.2.0-1.log.gz
Description: application/gzip

Bug#880179: python-saharaclient: FTBFS: ImportError: No module named pep8

[Andreas Beckmann]

Source: python-saharaclient
Version: 1.3.0-2
Severity: serious
Justification: fails to build from source

Hi,

python-saharaclient/experimental FTBFS in a clean minimal
sid+experimental environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-saharaclient-1.3.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pkgos-dh_auto_test 'saharaclient\.tests\.unit.*'
+ pyversions -vr
+ PYTHONS=2.7
+ py3versions -vr
+ PYTHON3S=3.6
+ echo 2.7
+ cut -d. -f1
+ PYMAJOR=2
+ echo ===> Testing with python (python2)
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.MF8YRjq5z3
+ + subunit2pyunit
+ pwd
tee /tmp/tmp.MF8YRjq5z3
+ PYTHONPATH=/build/python-saharaclient-1.3.0 PYTHON=python2.7 testr-python2 
run --subunit saharaclient\.tests\.unit.*
Non-zero exit code (2) from test listing.
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover $DISCOVER_DIRECTORY --list 
--- import errors ---
Failed to import test module: saharaclient.tests.unit.test_hacking
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "saharaclient/tests/unit/test_hacking.py", line 17, in 
from saharaclient.tests.hacking import checks
  File "saharaclient/tests/hacking/checks.py", line 19, in 
import pep8
ImportError: No module named pep8

--
Ran 0 tests in 0.697s

OK
+ cat /tmp/tmp.MF8YRjq5z3
+ subunit-filter -s --no-passthrough
+ subunit-stats
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.MF8YRjq5z3
+ testr-python2 slowest
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 3


Andreas


python-saharaclient_1.3.0-2.log.gz
Description: application/gzip

Bug#880178: python-openstacksdk: FTBFS with sphinx 1.6.5

[Andreas Beckmann]

Source: python-openstacksdk
Version: 0.9.17-1
Severity: serious
Justification: fails to build from source

Hi,

python-openstacksdk/experimental FTBFS in a clean minimal
sid+experimental environment:

[...]
/build/python-openstacksdk-0.9.17/doc/source/index.rst:30: WARNING: toctree 
contains reference to document u'history' that doesn't have a title: no link 
will be generated
/build/python-openstacksdk-0.9.17/doc/source/index.rst:30: WARNING: toctree 
contains reference to document u'history' that doesn't have a title: no link 
will be generated
generating indices... 
genindex/build/python-openstacksdk-0.9.17/doc/source/index.rst:30: WARNING: 
toctree contains reference to document u'history' that doesn't have a title: no 
link will be generated
 py-modindex/build/python-openstacksdk-0.9.17/doc/source/index.rst:30: WARNING: 
toctree contains reference to document u'history' that doesn't have a title: no 
link will be generated

writing additional pages... 
search/build/python-openstacksdk-0.9.17/doc/source/index.rst:30: WARNING: 
toctree contains reference to document u'history' that doesn't have a title: no 
link will be generated

copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 179 warnings.
ENFORCER: 626 proxy methods exist
ENFORCER: 653 proxy methods written
ENFORCER: Ignoring wait_for_* names...
ENFORCER: Found 0 missing proxy methods in the output
dh_sphinxdoc -O--buildsystem=python_distutils
dh_sphinxdoc: 
debian/python-openstacksdk-doc/usr/share/doc/python-openstacksdk-doc/html/search.html
 does not load searchindex.js
debian/rules:21: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 255
make[1]: Leaving directory '/build/python-openstacksdk-0.9.17'
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 2


Andreas


python-openstacksdk_0.9.17-1.log.gz
Description: application/gzip

Bug#880177: python-neutron-lib: missing B-D: openstack-pkg-tools

[Andreas Beckmann]

Source: python-neutron-lib
Version: 1.9.1-1
Severity: serious
Justification: fails to build from source

Hi,

python-neutron-lib/experimental FTBFS with

 fakeroot debian/rules clean
debian/rules:4: /usr/share/openstack-pkg-tools/pkgos.make: No such file or 
directory
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
debian/rules:7: recipe for target '/usr/share/openstack-pkg-tools/pkgos.make' 
failed
make: *** [/usr/share/openstack-pkg-tools/pkgos.make] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


Andreas


python-neutron-lib_1.9.1-1.log.gz
Description: application/gzip

Bug#871459: [Pkg-javascript-devel] vue.js

[Pirate Praveen]

On തിങ്കള്‍ 30 ഒക്ടോബര്‍ 2017 04:18 വൈകു, Paolo Greppi wrote:
> BTW this is only Vue core, there are also some supporting libraries which may 
> need packaging:
> vue-router, vuex, vue-cli, vue-loader, vue-server-renderer, 
> vue-class-component, vue-rx and vue-devtools.
> 
> Any help or suggestion is welcome !

I have also been working on vue packages for gitlab
(https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab) and some of
them are already in NEW.

https://github.com/vuejs/vue-template-es2015-compiler/issues/10 is a
blocker.

prettier needs chalk 2, which is in git repo, but even require test is
failing (needs to fix it). See if you can make some progress on
node-chalk and node-prettier in alioth.




signature.asc
Description: OpenPGP digital signature

Bug#877840: python-magnumclient: FTBFS ImportError: No module named oslo_log, openstackclient.tests.unit

[Andreas Beckmann]

Followup-For: Bug #877840
Control: found -1 2.7.0-2

openstackclient.tests.unit is still missing:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-magnumclient-2.7.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pkgos-dh_auto_test 
'magnumclient\.tests\.(?!.*test_utils\.CliUtilsTest\.test_keys_and_vals_to_strs.*)'
+ pyversions -vr
+ PYTHONS=2.7
+ py3versions -vr
+ PYTHON3S=3.6
+ echo 2.7
+ cut -d. -f1
+ PYMAJOR=2
+ echo ===> Testing with python (python2)
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.TWvsqxvrmJ
+ subunit2pyunit
+ tee /tmp/tmp.TWvsqxvrmJ
+ pwd
+ PYTHONPATH=/build/python-magnumclient-2.7.0 PYTHON=python2.7 testr-python2 
run --subunit 
magnumclient\.tests\.(?!.*test_utils\.CliUtilsTest\.test_keys_and_vals_to_strs.*)
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ . --list 
--- import eNon-zero exit code (2) from test listing.
rrors ---
Failed to import test module: 
magnumclient.tests.osc.unit.v1.test_cluster_templates
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "magnumclient/tests/osc/unit/v1/test_cluster_templates.py", line 21, in 

from magnumclient.tests.osc.unit.v1 import fakes as magnum_fakes
  File "magnumclient/tests/osc/unit/v1/fakes.py", line 20, in 
from magnumclient.tests.osc.unit import osc_utils
  File "magnumclient/tests/osc/unit/osc_utils.py", line 21, in 
from openstackclient.tests.unit import fakes
ImportError: No module named openstackclient.tests.unit


Failed to import test module: magnumclient.tests.osc.unit.v1.test_clusters
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "magnumclient/tests/osc/unit/v1/test_clusters.py", line 21, in 
from magnumclient.tests.osc.unit.v1 import fakes as magnum_fakes
  File "magnumclient/tests/osc/unit/v1/fakes.py", line 20, in 
from magnumclient.tests.osc.unit import osc_utils
  File "magnumclient/tests/osc/unit/osc_utils.py", line 21, in 
from openstackclient.tests.unit import fakes
ImportError: No module named openstackclient.tests.unit

--
Ran 0 tests in 0.958s

OK
+ cat /tmp/tmp.TWvsqxvrmJ
+ subunit-stats
+ subunit-filter -s --no-passthrough
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.TWvsqxvrmJ
+ testr-python2 slowest
debian/rules:16: recipe for target 'override_dh_auto_test' failed


Andreas


python-magnumclient_2.7.0-2.log.gz
Description: application/gzip

Bug#862115: Bug #862115: RFS: lr/0.4-1 [ITP] -- list files, recursively

[Nicolas Braud-Santoni]

Control: retitle -1 RFS: lr/1.1-1 [ITP] -- list files, recursively

Upstream made a new release yesterday, so I updated the package.
It is (again) on mentors.d.n and alioth.

On Sat, Oct 28, 2017 at 12:17:00PM +0200, Nicolas Braud-Santoni wrote:
> Control: retitle -1 Re: RFS: lr/1.0-1 [ITP] -- list files, recursively
> 
> I updated the package to the latest upstream version
> and uploaded it to alioth and mentors.d.n.
> 
> On Sat, Oct 28, 2017 at 11:38:33AM +0200, Nicolas Braud-Santoni wrote:
> > X-Debbugs-CC: ba...@quantz.debian.org
> > 
> > Hi,
> > 
> > I reopened those 2 RFSes, as Bart closed them over the
> > packages not being on mentors.d.n anymore (due to a 20
> > days timeout).
> > 
> > I will reupload them momentarily, but as mentionned
> > in the previous emails they are available anyhow on
> > 
> >   https://nicolas.braud-santoni.eu/tmp/deb/
> > 
> > 
> > As an aside, I find it very weird to close a RFS due to
> > the inactivity of would-be sponsors: from the packager's
> > side, it feels like a double punishment (getting ignored,
> > then getting your RFS closed because you got ignored)...
> > 
> > 
> > Best,
> > 
> >   nicoo
> 
> 




signature.asc
Description: PGP signature

Bug#880176: gtk-doc-tools: crashes if a devhelp2.gz file is present

[Alban Browaeys]

Package: gtk-doc-tools
Version: 1.26-2.1
Severity: important


May you apply upstream patches:
https://git.gnome.org/browse/gtk-doc/commit/?id=d6a75bdf26f61889e5d01e8af499b59b2de011b0
https://git.gnome.org/browse/gtk-doc/commit/?id=6c7c1e571f91997d0895ac6a87f3a417376d0536

I also attach a local patch to fix the testsuite (not yet sent upstream).
I add 18 to the expected log lines count to account for
the upstream patches restored 6 warnings:
"
Please fix https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/1466210 . For 
now run:
gunzip /usr/share/gtk-doc/html/ogmrip/ogmdvd-gtk/ogmdvd-gtk.devhelp2.gz

"


Local NetworkManager build fails with:
gtkdoc-fixxref --module=libnm --module-dir=html 
--html-dir=/usr/share/gtk-doc/html 
Traceback (most recent call last):
  File "/usr/bin/gtkdoc-fixxref", line 57, in 
fixxref.Run(options)
  File "/usr/share/gtk-doc/python/gtkdoc/fixxref.py", line 96, in Run
ScanIndices(options.html_dir, 0)
  File "/usr/share/gtk-doc/python/gtkdoc/fixxref.py", line 153, in ScanIndices
ScanIndices(subdir, use_absolute_links)
  File "/usr/share/gtk-doc/python/gtkdoc/fixxref.py", line 148, in ScanIndices
''' % full_entry)
TypeError: %d format: a number is required, not str
Makefile:869 : la recette pour la cible « html-build.stamp » a échouée
make[3]: *** [html-build.stamp] Erreur 1
make[3] : on quitte le répertoire « 
/home/prahal/nm-online/network-manager-1.8.4/docs/libnm »
Makefile:15802 : la recette pour la cible « all-recursive » a échouée
make[2]: *** [all-recursive] Erreur 1
make[2] : on quitte le répertoire « 
/home/prahal/nm-online/network-manager-1.8.4 »
Makefile:6532 : la recette pour la cible « all » a échouée
make[1]: *** [all] Erreur 2
make[1] : on quitte le répertoire « 
/home/prahal/nm-online/network-manager-1.8.4 »
dh_auto_build: make -j10 returned exit code 2
debian/rules:8 : la recette pour la cible « build » a échouée
make: *** [build] Erreur 2
dpkg-buildpackage: erreur: debian/rules build subprocess returned exit status 2


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

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

Versions of packages gtk-doc-tools depends on:
ii  docbook-to-man  1:2.0.0-39
ii  docbook-xml 4.5-8
ii  docbook-xsl 1.79.1+dfsg-2
ii  highlight   3.39-1
ii  libglib2.0-dev  2.54.2-1.1
ii  pkg-config  0.29-4+b1
ii  python  2.7.14-1
ii  python-mock 2.0.0-3
ii  python-six  1.11.0-1
ii  xsltproc1.1.29-2.2

gtk-doc-tools recommends no packages.

Versions of packages gtk-doc-tools suggests:
ii  dblatex  0.3.10-2

-- no debconf information
--- a/tests/sanity.sh
+++ b/tests/sanity.sh
@@ -82,15 +82,17 @@
 tested=`expr $tested + 1`
 
 # check that log files have only one line (the command)
+# and the 6 references to launchapd bug 1466210
+# which makes up 19 lines
 nok=0
 for file in $dir/*/docs/gtkdoc-*.log; do
-  expected_lines="1"
+  expected_lines="19"
   # adjust for known files
   if test $file = "$dir/fail/docs/gtkdoc-mkdb.log"; then
-expected_lines="16"
+expected_lines="34"
   fi
   if test $file = "$dir/gobject/docs/gtkdoc-fixxref.log"; then
-expected_lines="2"
+expected_lines="20"
   fi
   case $file in
   *gtkdoc-fixxref.log)

Bug#729899: catch: Warnings triggered by -Wconversion and -Wshadow

[Pander]

Hi all,

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729899 was reported 
almost four years ago for version 1.0+m10git1e2f1d16-1 If this bug is 
still valid for the latest stable version of catch, please report it at 
https://github.com/philsquared/Catch and close the report here at Debian.


Best,

Pander

Bug#390582: Fixed

[Teus Benschop]

fixed 390582 2.11.0
thanks

Bug#390582: Cannot reproduce

[Teus Benschop]

Running version 2.11.0 in Debian, everything works okay on startup. The
application behaves normally.

Thank you for reporting this bug. It helps us to improve the software.

I will close this bug now.

If there's any further updates on this, please submit this information, and
re-open the bug.

Bug#880175: debci: Default debci_suite incorrectly configured

[Андрей Родионов]

Package: debci
Version: 1.5.1
Severity: normal

Dear Maintainer,

I'm trying to run debci setup on stretch and seeing the following in the logs:

lxc-create: lxccontainer.c: lxc_container_new: 4151 Error: adt-sid-armhf.new 
creation was not completed
  Volume group "lxc" not found
  Cannot process volume group lxc
lxc-create: bdev/lxclvm.c: lvm_create: 414 Error creating new lvm blockdev 
/dev/lxc/adt-sid-armhf.new size 1073741824 bytes

I don't have any custom configs, just ran "apt install debci". According to the 
./lib/environment.sh it will pick up "unstable" which will be converted to 
"sid". I'm running on stretch (stable).

I was wondering if default debci_suite value could be taken from the 
"lsb_release -a" output.
 
-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

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

Versions of packages debci depends on:
ii  adduser 3.115
ii  amqp-tools  0.8.0-1+b3
ii  bsdmainutils9.0.12+nmu1
ii  dctrl-tools 2.24-2+b1
ii  debootstrap 1.0.89
ii  devscripts  2.17.6+deb9u1
ii  fonts-font-awesome  4.7.0~dfsg-1
ii  jq  1.5+dfsg-1.3
ii  libjs-bootstrap 3.3.7+dfsg-2
ii  libjs-jquery3.1.1-2
ii  libjs-jquery-flot   0.8.3+dfsg-1
ii  patchutils  0.3.4-2
ii  ruby1:2.3.3
ii  sudo1.8.19p1-2.1

Versions of packages debci recommends:
ii  moreutils  0.60-1
ii  ntp1:4.2.8p10+dfsg-3

Versions of packages debci suggests:
ii  apt-cacher-ng  2-2

-- no debconf information

Bug#744161: This package seems abandoned

[Salvo Tomaselli]

Hello,

This package seems abandoned, this bug has been open for quite a while
without any activity.

I would be interested in adopting the package.

If this doesn't get any answer within 3 months, I'll be
orphaning the package by myself.

Best.

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/

Bug#871459: vue.js

[Paolo Greppi]

As discussed (some time ago..) with Michael, I have taken over the ITP for 
vue.js.

I'll try to package it within the javascript maintainers team.

I have started work on this repo on alioth:
https://anonscm.debian.org/git/pkg-javascript/vue.js.git

It build-depends on a few packages:
https://anonscm.debian.org/git/pkg-javascript/vue.js.git/tree/package.json#n59
so it'll take some time before I can ask someone to sponsor the upload..

BTW this is only Vue core, there are also some supporting libraries which may 
need packaging:
vue-router, vuex, vue-cli, vue-loader, vue-server-renderer, 
vue-class-component, vue-rx and vue-devtools.

Any help or suggestion is welcome !

Paolo

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

On 30/10/17 09:13, Dmitry Shachnev wrote:
> The attached small patch fixes the issue for me. Tested with libjpeg-turbo,
> where one symbol was deliberately removed.
> 
> The previous if (defined $state) check was always true, because a //=
> operator is used to define $state two lines above.
> 
> --
> Dmitry Shachnev
> 

This patch appears to fix the issue for me on the libjpeg-turbo test
case, and builds on the kubuntu CI which was having issues on not seeing
the correct output in build logs.

Bug#880174: snapd: swrast error (nvidia-legacy-340xx) while launching UI installed-snaps

[Samuel A.]

Package: snapd
Version: 2.27.6-2
Severity: important
Tags: d-i

Dear Maintainer,

When executing UI snaps (like Hiri, for instance) with the default nvidia 
legacy driver 340xx installed, I get the following error:
~$ LIBGL_DEBUG=verbose hiri
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying 
/snap/hiri/19/usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying 
/snap/hiri/19/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
libGL: Can’t open configuration file /.drirc: No such file or directory.
libGL: Can’t open configuration file /.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
function is no-op

Instead, executing a text-only snap (like Hello) it works fine:
~$ snap run hello
Hello, world!


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (1000, 'stable'), (900, 'stable'), (750, 'testing'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages snapd depends on:
ii  adduser  3.115
ii  apparmor 2.11.0-3
ii  ca-certificates  20161130+nmu1
ii  gnupg2.1.18-8~deb9u1
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libseccomp2  2.3.1-2.1
ii  libudev1 232-25+deb9u1
ii  openssh-client   1:7.4p1-10+deb9u1
ii  squashfs-tools   1:4.3-3+deb9u1
ii  systemd  232-25+deb9u1

snapd recommends no packages.

snapd suggests no packages.

-- no debconf information

Bug#879810: mirror submission for mirrors.nxthost.com

[Mirrors List]

Hi,

We moved to an include configuration: amd64 arm64 i386 mips64el ppc64el

The sync issue has been resolved.

Thanks,
Ciprian Popa

On 27.10.2017 12:01, Peter Palfrader wrote:

Control: retitle -1 mirror submission for mirrors.nxthost.com [out of date]

On Thu, 26 Oct 2017, Ciprian Popa wrote:


Site: mirrors.nxthost.com
Archive-architecture: amd64 i386

Hi!

According to

Trace Url: http://mirrors.nxthost.com/debian/project/trace/mirrors.nxthost.com

you mirror more than those two architectures -- you might want to update
your config to match (maybe change to an include based setting).

Also, your mirror has not updated since Wednesday.

We expect mirrors on our mirrorlist to match the update frequency of the
archive, which currently is four times a day (every 6 hours).

Cheers,

Bug#880169: Patch for building against Ayatana Indicators

[Mike Gabriel]

By some reason, reportbug did not attache the .debdiff file... Now it  
should be there.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

diff -Nru network-manager-applet-1.8.4/debian/changelog 
network-manager-applet-1.8.4/debian/changelog
--- network-manager-applet-1.8.4/debian/changelog   2017-09-20 
20:22:26.0 +
+++ network-manager-applet-1.8.4/debian/changelog   2017-05-22 
13:40:43.0 +
@@ -1,3 +1,16 @@
+network-manager-applet (1.8.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches:
++ Add Ayatana-Indicators-support.patch. Allow building against Ayatana
+  Indicators as an alternative to Ubuntu's indicators.
+  * debian/control:
++ Add B-Ds: libayatana-appindicator3-dev, libdbusmenu-gtk3-dev.
+  * debian/rules:
++ Switch on --with-ayatana-appindicator configure option.
+
+ -- Mike Gabriel   Mon, 22 May 2017 15:40:43 +0200
+
 network-manager-applet (1.8.4-1) unstable; urgency=medium
 
   * New upstream version 1.8.4
diff -Nru network-manager-applet-1.8.4/debian/control 
network-manager-applet-1.8.4/debian/control
--- network-manager-applet-1.8.4/debian/control 2017-09-20 20:22:26.0 
+
+++ network-manager-applet-1.8.4/debian/control 2017-05-22 13:40:43.0 
+
@@ -9,6 +9,8 @@
libsecret-1-dev,
libgtk-3-dev (>= 3.4),
libglib2.0-dev (>= 2.38),
+   libayatana-appindicator3-dev,
+   libdbusmenu-gtk3-dev (>= 16.04.0),
libnotify-dev (>= 0.7),
libnm-util-dev (>= 1.8),
libnm-glib-dev (>= 1.8),
diff -Nru 
network-manager-applet-1.8.4/debian/patches/Ayatana-Indicator-support.patch 
network-manager-applet-1.8.4/debian/patches/Ayatana-Indicator-support.patch
--- network-manager-applet-1.8.4/debian/patches/Ayatana-Indicator-support.patch 
1970-01-01 00:00:00.0 +
+++ network-manager-applet-1.8.4/debian/patches/Ayatana-Indicator-support.patch 
2017-05-22 13:40:43.0 +
@@ -0,0 +1,57 @@
+Description: Support building against Ayatana Indicators and Ubuntu Indicators 
alike
+Author: Mike Gabriel 
+
+--- a/configure.ac
 b/configure.ac
+@@ -135,7 +135,15 @@
+ if test "$with_appindicator" == "yes"; then
+   PKG_CHECK_MODULES(APPINDICATOR, appindicator3-0.1)
+   PKG_CHECK_MODULES(DBUSMENU, dbusmenu-gtk3-0.4 >= 16.04.0)
+-  AC_DEFINE([WITH_APPINDICATOR], 1, [Enable using libappindicator])
++  AC_DEFINE([WITH_APPINDICATOR], 1, [Enable appindicator support, use 
Ubuntu's libappindicator])
++fi
++
++AC_ARG_WITH([ayatana-appindicator], 
AS_HELP_STRING([--with-ayatana-appindicator|--without-ayatana-appindicator], 
[Build with libayatana-appindicator support instead of Ubuntu's indicators.]))
++if test "$with_ayatana_appindicator" == "yes"; then
++  PKG_CHECK_MODULES(AYATANAAPPINDICATOR, ayatana-appindicator3-0.1)
++  PKG_CHECK_MODULES(DBUSMENU, dbusmenu-gtk3-0.4 >= 16.04.0)
++  AC_DEFINE([WITH_APPINDICATOR], 1, [Enable appindicator support])
++  AC_DEFINE([USE_AYATANA_INDICATORS], 1, [Use Ayatana Indicators])
+ fi
+ 
+ AM_CONDITIONAL(HAVE_GBT, test x"$have_gbt" = "xyes")
+--- a/src/applet.h
 b/src/applet.h
+@@ -32,7 +32,11 @@
+ #include 
+ 
+ #ifdef WITH_APPINDICATOR
+-#include 
++# ifdef USE_AYATANA_INDICATORS
++#  include 
++# else
++#  include 
++# endif
+ #endif
+ 
+ #include 
+--- a/Makefile.am
 b/Makefile.am
+@@ -825,7 +825,8 @@
+   $(LIBSECRET_CFLAGS) \
+   $(NOTIFY_CFLAGS) \
+   $(MM_GLIB_CFLAGS) \
+-  $(APPINDICATOR_CFLAGS)
++  $(APPINDICATOR_CFLAGS) \
++  $(AYATANAAPPINDICATOR_CFLAGS)
+ 
+ src_nm_applet_LDADD = \
+   src/wireless-security/libwireless-security-libnm.la \
+@@ -836,6 +837,7 @@
+   $(NOTIFY_LIBS) \
+   $(MM_GLIB_LIBS) \
+   $(APPINDICATOR_LIBS) \
++  $(AYATANAAPPINDICATOR_LIBS) \
+   -lm
+ 
+ $(src_nm_applet_OBJECTS): $(nm_applet_h_gen)
diff -Nru network-manager-applet-1.8.4/debian/patches/series 
network-manager-applet-1.8.4/debian/patches/series
--- network-manager-applet-1.8.4/debian/patches/series  2017-09-20 
20:22:26.0 +
+++ network-manager-applet-1.8.4/debian/patches/series  2017-05-22 
13:40:43.0 +
@@ -1,2 +1,3 @@
 Allow-to-create-connections-without-admin-privileges.patch
 Force-online-state-with-unmanaged-devices.patch
+Ayatana-Indicator-support.patch
diff -Nru network-manager-applet-1.8.4/debian/rules 
network-manager-applet-1.8.4/debian/rules
--- network-manager-applet-1.8.4/debian/rules   2017-09-20 20:22:26.0 
+
+++ network-manager-applet-1.8.4/debian/rules   2017-05-22 13:40:43.0 
+
@@ -12,6 +12,7 @@
 
 override_dh_auto_configure:

Bug#880159: qtchooser: Make plain "qmake" invocation fail

[Antonio]

edit /usr/lib/x86_64-linux-gnu/qtchooser//default.conf and add this line
solve the problem:

+/usr/lib/qt5/bin/
/usr/lib/x86_64-linux-gnu/qt5/bin
/usr/lib/x86_64-linux-gnu

Bug#880173: kate: Kate in experimental cannot be installed

[valette]

Package: kate
Version: 4:17.08.1-1
Severity: important

apt-get  -s -t experimental install kate
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kate : Depends: libgit2-24 (>= 0.24.0) but it is not installable
E: Unable to correct problems, you have held broken packages.


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

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

Versions of packages kate depends on:
ii  kate5-data   4:17.08.1-1
ii  kio  5.37.0-2
ii  ktexteditor-katepart 5.37.0-2+b1
ii  libc62.25-0experimental3
ii  libgit2-26   0.26.0+dfsg.1-1.1
ii  libkf5activities55.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5guiaddons5 5.37.0-2
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5itemmodels55.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5newstuff5  5.37.0-2
ii  libkf5parts5 5.37.0-2
ii  libkf5plasma55.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5texteditor55.37.0-2+b1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5threadweaver5  5.37.0-2
ii  libkf5wallet-bin 5.37.0-2
ii  libkf5wallet55.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5windowsystem5  5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libqt5core5a 5.9.2+dfsg-4
ii  libqt5dbus5  5.9.2+dfsg-4
ii  libqt5gui5   5.9.2+dfsg-4
ii  libqt5sql5   5.9.2+dfsg-4
ii  libqt5widgets5   5.9.2+dfsg-4
ii  libqt5xml5   5.9.2+dfsg-4
ii  libstdc++6   7.2.0-12
ii  plasma-framework 5.37.0-2
ii  qml-module-org-kde-kquickcontrolsaddons  5.37.0-2+b1
ii  qml-module-qtquick-layouts   5.9.2-3
ii  qml-module-qtquick2  5.9.2-3

kate recommends no packages.

Versions of packages kate suggests:
ii  ispell 3.4.00-6
ii  khelpcenter4:17.08.1-1
ii  konsole-kpart  4:17.08.1-1

-- no debconf information

Bug#880172: alot: UnicodeEncodeError for search queries with non-ascii characters

[Johannes Schauer]

Package: alot
Version: 0.6-1
Severity: normal
Tags: patch

Hi,

steps to reproduce:

 1. search for a query string containing non-ascii characters

 2. try opening any of the resulting threads

 3. the following will be output in the debug log:

ERROR:ui:Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 651, 
in _runCallbacks
current.result = callback(current.result, *args, **kw)
  File "/usr/share/alot/alot/ui.py", line 679, in call_apply
return defer.maybeDeferred(cmd.apply, self)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 150, 
in maybeDeferred
result = f(*args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1445, 
in unwindGenerator
return _inlineCallbacks(None, gen, Deferred())
---  ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1299, 
in _inlineCallbacks
result = g.send(result)
  File "/usr/share/alot/alot/commands/globals.py", line 77, in apply
ui.cleanup()
  File "/usr/share/alot/alot/ui.py", line 711, in cleanup
self._cmd_hist_file, size=size)
  File "/usr/share/alot/alot/ui.py", line 764, in _save_history_to_file
histfile.write(line)
exceptions.UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in 
position 11: ordinal not in range(128)


alot will not crash but the result of this exception is, that all
messages in the thread are unfolded and not only those matching the
query terms. Naturally this is undesirable. To fix this problem, the
following patch to alot/db/message.py suffices:

@@ -254,5 +254,5 @@
 
 def matches(self, querystring):
 """tests if this messages is in the resultset for `querystring`"""
-searchfor = '( {} ) AND id:{}'.format(querystring, self._id)
+searchfor = u'( {} ) AND id:{}'.format(querystring, self._id)
 return self._dbman.count_messages(searchfor) > 0



Please consider applying it.

Thanks!

cheers, josch



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

Kernel: Linux 4.9.0-3-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 alot depends on:
ii  python   2.7.13-2
ii  python-configobj 5.0.6-2
ii  python-gpg   1.8.0-3+b2
ii  python-gpgme 0.3-1.2
ii  python-magic 1:5.30-1
ii  python-notmuch   0.23.7-3
ii  python-twisted   16.6.0-2
ii  python-twisted-core  16.6.0-2
ii  python-urwid 1.3.1-2+b1
ii  python-urwidtrees1.0.1.1-1

Versions of packages alot recommends:
ii  links2.14-2+b1
ii  links2   2.14-2+b1
ii  notmuch  0.23.7-3
ii  w3m  0.5.3-34

Versions of packages alot suggests:
pn  alot-doc  

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/alot/alot/db/message.py (from alot package)

Bug#880092: [Pkg-electronics-devel] Bug#880092: Bug#880092: Error: libusb_open() failed with LIBUSB_ERROR_ACCESS

[Jonathan McDowell]

On Mon, Oct 30, 2017 at 10:48:13AM +0100, Ivan Sergio Borgonovo wrote:
> /lib/udev/rules.d/60-openocd.rules
> 
> just contains the string
> 
> contrib/60-openocd.rules

Ah! I see the problem now (though am confused as to why I don't see it
on my system); the contents of the /lib/udev/rules.d/60-openocd.rules
file is incorrect. I suspect that's something to do with the changes I
made to switch to pure debhelper in -2. I'll investigate.

> I've upgraded openocd at least a couple of times in the past, and I
> can't see many updates in Debian changelog. According to the aptitude
> logs I still have on my system the oldest openocd I had installed was
> 
> 0.9.0-1+b2
> 
> but it is not listed in the debian changelog.

It's a binary rebuild; no source changes, just picking up newer
build dependencies. In general there'll be a changelog.amd64.gz in such
packages that will tell you what the rebuild is for (but it won't be
present in later versions of the package).

J.

-- 
"evilwm - we sold our souls to the window manager" --
http://www.6809.org.uk/evilwm/

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

> Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:

I really spend more than 4 weeks in discussions with upstream
about license and copyright clarifications. Now it is finished. I
uploaded a new hol-light version to DOM git yesterday. Please
review and upload.

If you think I fulfill the conditions for directly uploading
hol-light, I would appreciate, if somebody could execute

dcut dm --uid "Hendrik Tews" --allow hol-light

Bye,

Hendrik

Bug#880092: [Pkg-electronics-devel] Bug#880092: Error: libusb_open() failed with LIBUSB_ERROR_ACCESS

[Ivan Sergio Borgonovo]

Hi,

Everything was working fine before update, I was able to upload firmware 
to an stm32 and debug with an olimex arm-usb-ocd-h.


The user was already in plugdev.

I sincerely can't remember for sure if I had 60-openocd.rules in my 
/etc/udev/rules.d directory before but I presume I didn't have it and 
everything was working.
But I've had openocd working on my system for so long I don't remember 
if I had to do some manual setup, so I can't assure I manually copied 
any rule 2 years ago.


After upgrade I surely didn't have an 60-openocd.rules there.
After downgrade I still didn't have it there.

So last upgrade deleted it or something else started to require it.

/lib/udev/rules.d/60-openocd.rules

just contains the string

contrib/60-openocd.rules

In the openocd binary package I can't find any udev rule other than the 
"empty" one above.
In the openocd_0.10.0.orig.tar.bz2 there is a contrib/60-openocd.rules 
and that's the one I copied and placed in /etc/udev/rules.d


I've upgraded openocd at least a couple of times in the past, and I 
can't see many updates in Debian changelog. According to the aptitude 
logs I still have on my system the oldest openocd I had installed was


0.9.0-1+b2

but it is not listed in the debian changelog.

Thanks

On 10/29/2017 01:42 PM, Jonathan McDowell wrote:

On Sun, Oct 29, 2017 at 01:12:27PM +0100, Ivan Sergio Borgonovo wrote:

Package: openocd
Version: 0.10.0-2

After a cycle of upgrades listed below I got
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
using openocd


Was it working before the upgrade (presumably on version 0.10.0-1+b1
from your log below)? Is the user in question in the plugdev group?


I downgraded to the previous version without improvement.

Googled and find a reference to udev rules.
Nor the old neither the new openocd package copy any rule in
/etc/udev/rules.d
Binary package contains /lib/udev/rules.d/60-openocd.rules

cat /lib/udev/rules.d/60-openocd.rules
contrib/60-openocd.rules

Downloaded openocd debian source package and copied

60-openocd.rules

in /etc/udev/rules.d


Is there any difference between the file you put in /etc/udev/rules.d/
and the shipped file in /lib/udev/rules.d/ ? The file from contrib/ in
the source package is exactly the same as what's installed in
/lib/udev/rules.d/ for me, and when I plug in a JTAG device it's
correctly assigned to the plugdev group. /lib/udev/rules.d/ is the
appropriate directory for a system shipped set of udev rules.


Things started to work again.
I'm not sure to which of the below upgraded packages I can attribute the
problem.

thanks

[REMOVE, NOT USED] libbind9-140:amd64 1:9.10.3.dfsg.P4-12.6
[REMOVE, NOT USED] libdns-export162:amd64 1:9.10.3.dfsg.P4-12.6
[REMOVE, NOT USED] libdns162:amd64 1:9.10.3.dfsg.P4-12.6
[REMOVE, NOT USED] libisc-export160:amd64 1:9.10.3.dfsg.P4-12.6
[REMOVE, NOT USED] libisc160:amd64 1:9.10.3.dfsg.P4-12.6
[REMOVE, NOT USED] libisccfg140:amd64 1:9.10.3.dfsg.P4-12.6
[INSTALL, DEPENDENCIES] libbind9-141:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libdns-export190:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libdns190:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libisc-export189:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libisc189:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libisccfg144:amd64 1:9.10.6+dfsg-4
[INSTALL, DEPENDENCIES] libjaylink0:amd64 0.1.0-1
[UPGRADE] appstream:amd64 0.11.6-2 -> 0.11.7-1
[UPGRADE] autotools-dev:amd64 20161112.1 -> 20161112.1+nmu1
[UPGRADE] bind9-host:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
[UPGRADE] dnsutils:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
[UPGRADE] fonts-arphic-uming:amd64 0.2.20080216.2-9 -> 0.2.20080216.2-10
[UPGRADE] freerdp2-wayland:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
2.0.0~git20170725.1.1648deb+dfsg1-5
[UPGRADE] gir1.2-gtk-3.0:amd64 3.22.24-2 -> 3.22.24-3
[UPGRADE] gtk-update-icon-cache:amd64 3.22.24-2 -> 3.22.24-3
[UPGRADE] init:amd64 1.50 -> 1.51
[UPGRADE] init-system-helpers:amd64 1.50 -> 1.51
[UPGRADE] isc-dhcp-client:amd64 4.3.5-3 -> 4.3.5-3+b1
[UPGRADE] isc-dhcp-common:amd64 4.3.5-3 -> 4.3.5-3+b1
[UPGRADE] libappstream4:amd64 0.11.6-2 -> 0.11.7-1
[UPGRADE] libappstreamqt2:amd64 0.11.6-2 -> 0.11.7-1
[UPGRADE] libexttextcat-2.0-0:amd64 3.4.4-2+b1 -> 3.4.5-1
[UPGRADE] libexttextcat-data:amd64 3.4.4-2 -> 3.4.5-1
[UPGRADE] libfreerdp-client2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
2.0.0~git20170725.1.1648deb+dfsg1-5
[UPGRADE] libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
2.0.0~git20170725.1.1648deb+dfsg1-5
[UPGRADE] libfreetype6:amd64 2.8-0.2 -> 2.8.1-0.1
[UPGRADE] libgd3:amd64 2.2.5-3 -> 2.2.5-4
[UPGRADE] libgtk-3-0:amd64 3.22.24-2 -> 3.22.24-3
[UPGRADE] libgtk-3-bin:amd64 3.22.24-2 -> 3.22.24-3
[UPGRADE] libgtk-3-common:amd64 3.22.24-2 -> 3.22.24-3
[UPGRADE] libisccc140:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
[UPGRADE] libjs-sphinxdoc:amd64 1.6.4-2 -> 1.6.5-1
[UPGRADE] liblwres141:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
[UPGRADE] 

Bug#848327: RFS: libu2f-host/1.1.4-1 [RC]

[Nicolas Braud-Santoni]

X-Debbugs-CC: si...@josefsson.org, pkg-auth-maintain...@lists.alioth.debian.org
Control: reopen   -1 =
Control: retitle  -1 RFS: libu2f-host/1.1.4-1 [RC]
Control: severity -1 important
Control: block 846358 by -1
Control: tags  846358 fixed pending
Control: block 846359 by -1
Control: tags  846359 fixed pending
Control: block 824532 by -1
Control: tags  824532 fixed pending
Control: block 876579 by -1
Control: tags  876579 fixed pending


Hi,

@Simon: you pushed a different package for the same version,
this summer, that didn't include my fixes.

I merged the work on alioth (now directly on branch `master`,
to avoid a repeat of this confusion) and prepared a new upload
that includes the new release (1.1.4) and a fix for #876579 (FTBFS).


Please consider sponsoring this upload, as it closes a number
of bugs, including a FTBFS.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#703941: -p (path) option clashes with generic debhelper -p (package) option

[Simon McVittie]

On Tue, 26 Mar 2013 at 00:27:07 +0100, Michael Biebl wrote:
> Using -p as option to specify the path is a poor choice since it clashes
> with the generic -p option which is used to specify the package.
> 
> Looking at e.g. gnome-shell's debian/rules, I'm actually not sure what
> the result of this call will be:
> dh_girepository -p$(cdbs_curpkg) -l src -p /usr/lib/mutter

The answer seems to be that -p is always interpreted as dh_girepository's
local -p option, and the second -p overwrites the first, so it's
equivalent to dh_girepository -l src -p /usr/lib/mutter. To get the
effect that was intended, write:
dh_girepository --package=$(cdbs_curpkg) -l src -p /usr/lib/mutter

Regards,
smcv

Bug#871469: Status of llvm-toolchain-3.8?

[Stéphane Glondu]

On 20/10/2017 10:27, Sylvestre Ledru wrote:

At the moment, llvm-toolchain-3.8 FTBFS with "gcc-7.2: Command not
found" and this blocks the OCaml transition.

I see there are already bugs open related to gcc-7 (#871011 and
#853523), but these do not have recent activity.

I also see that this package has been requested to be removed
(#873331), but again no recent activity on this bug.

Is there any plans to fix llvm-toolchain-3.8?


I wish we could removed it but it is far from ready (we were blocked by
the ocaml transition but I dropped the ocaml support to mitigate that)
I will try to fix that in the next few days.
Sorry about that


I saw that you removed the OCaml bindings (libllvm-3.8-ocaml-dev) from 
llvm-toolchain-3.8, but there is still libllvm-ocaml-dev (from 
llvm-defaults) that depends on libllvm-3.8-ocaml-dev.


I think you need to remove libllvm-ocaml-dev from llvm-defaults to 
disentangle LLVM and OCaml.


Cheers,

--
Stéphane

Bug#880171: ITP: perse -- Permission settings GUI for udev devices

[Ville Ranki]

Package: wnpp
Severity: wishlist
Owner: Ville Ranki 

* Package name: perse
  Version : 1.0.2
  Upstream Author : Ville Ranki 
* URL : https://github.com/vranki/perse
* License : GPLv3
  Programming Lang: C++
  Description : Permission settings GUI for udev devices

Got a USB gadget which won't work unless you chmod it's device
file to be writable, suchas Arduino or USB-serial adapter?

Hate writing udev rules for those gadgets?

Perse is a easy GUI tool to make devices writable in Linux. Just
select the devices you want to be world writable and Perse creates
persistent udev rules for them.



I've been using Perse for some years and found it useful in
many situations. I would be nice to be able to apt install
it easily from debian repos.

Bug#880170: aptitude: Read error (-5: DATA_ERROR_MAGIC)

[Mykola Nikishov]

Package: aptitude
Version: 0.8.9-1
Severity: normal

$ sudo aptitude update 
...
W: Failed to fetch 
tor+http://security.debian.org/dists/stable/updates/contrib/i18n/Translation-en:
 BZ2_bzread: 
/var/lib/apt/lists/partial/security.debian.org_dists_stable_updates_contrib_i18n_Translation-en.bz2
 Read error (-5: DATA_ERROR_MAGIC)
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

Removing the file in question doesn't help, an error persists.

-- Package-specific info:
Terminal: screen-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.9
Compiler: g++ 7.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7fffdbb25000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f6eacfe5000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f6eacdb5000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f6eacb8b000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f6eac984000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f6eac689000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f6eac381000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f6eac169000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f6eabf5)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f6eabd4c000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f6eab941000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f6eab724000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f6eab3a2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6eab09e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f6eaae87000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6eaaae8000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f6eaa8d1000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6eaa6b7000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f6eaa4a7000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f6eaa281000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f6eaa06c000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f6ea9e4e000)
/lib64/ld-linux-x86-64.so.2 (0x7f6ead9a2000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6ea9c4a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f6ea9a42000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f6ea983d000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.9-1
ii  libapt-pkg5.0  1.5
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4+b2
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4+b2
ii  libboost-system1.62.0  1.62.0+dfsg-4+b2
ii  libc6  2.24-11+deb9u1
ii  libcwidget3v5  0.5.17-6
ii  libgcc11:6.3.0-18
ii  libncursesw5   6.0+20161126-1+deb9u1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.20.1-2
ii  libstdc++6 6.3.0-18
ii  libtinfo5  6.0+20161126-1+deb9u1
ii  libxapian301.4.4-3

Versions of packages aptitude recommends:
pn  libparse-debianchangelog-perl  
ii  sensible-utils 0.0.10

Versions of packages aptitude suggests:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  debtags 
pn  tasksel 

-- no debconf information

Bug#877172: closed by Jonathan McDowell <nood...@earth.li> (Re: Bug#877172: nm.debian.org: emeritus mails: please add the login name to the subject)

[Holger Levsen]

On Sun, Oct 29, 2017 at 02:27:08PM +, Debian Bug Tracking System wrote:
> > Currently these emeritus mails only contain the email forwarding addresses
> > which most people dont know from other DDs, so it would be really nice
> > to also show the login name somewhere.
> Seems like a good idea; fixed in
> https://anonscm.debian.org/git/nm/nm2.git/commit/?id=d135c8d9a2a959670dbf815197184027ae36083f

thank you!

:)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#880169: Please enable Indicator support and build against Ayatana Indicators

[Mike Gabriel]

Source: network-manager-applet
Version: 1.8.4-1
Severity: wishlist
Tags: upstream patch
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatanaindicators

Dear maintainer,

attached you find a .debdiff that enables Indicator support in Network
Manager Applet (GNOME) on Debian.

The Debian + Ubuntu MATE Packaging Team are currently working on porting
Ubuntu Indicators to a distro-independent state. This is done under a new
upstream umbrella (https://github.com/AyatanaIndicators).

For Network Manager Applet (GNOME), we would love to see Indicator
support being enabled on Debian systems. As the Ubuntu Indicators in
Debian are severely unmaintained, please switch to Ayatana Indicators
when enabling Indicator support for your package.

A Network Manager Applet that has been built against Ayatana Indicators will
also work as-is on top of Ubuntu Indicators as found in Ubuntu.

light+love
Mike Gabriel


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

Kernel: Linux 4.9.0-4-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)

Bug#880168: RFS: libu2f-server/1.0.1-4 [RC]

[Nicolas Braud-Santoni]

Package: sponsorship-requests
Severity: important
Control: blocks 876580 by -1
Control: tags   876580 fixed pending
X-Debbugs-CC: si...@josefsson.org, pkg-auth-maintain...@lists.alioth.debian.org

Dear mentors,

I am looking for a sponsor for my package "libu2f-server"

 * Package name: libu2f-server
   Version : 1.0.1-4
 * URL : https://developers.yubico.com/libu2f-server/
 * License : Expat
   Section : utils

This upload fixes a FTBFS bug (#876580),
so please consider sponsoring it soon.


The package can be found on mentors.d.n:

  https://mentors.debian.net/package/libu2f-server

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

dget -x 
https://mentors.debian.net/debian/pool/main/libu/libu2f-server/libu2f-server_1.0.1-4.dsc


The corresponding source has been pushed to the packaging repository on alioth.

Best,

  nicoo


signature.asc
Description: PGP signature

Bug#880167: fp-utils-3.0.0: package installs lstlang[123].sty that hide files in texlive-latex-recommended

[Andrius Merkys]

Package: fp-utils-3.0.0
Version: 3.0.0+dfsg-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I have installed texlive-latex-recommended and fp-utils-3.0.0. Files 
lstlang[123].sty are installed
by both packages in different destinations, however, ones that are 
brought by fp-utils-3.0.0 are
older, but are found first in TeX path (I use pdflatex). I was trying 
to get 'bash' syntax
highlight, but it is not found in lstlang1.sty of fp-utils-3.0.0.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I have removed fp-utils-3.0.0, that solved the problem.
   * What was the outcome of this action?
TeX document compiled successfully.
   * What outcome did you expect instead?
I expected 'bash' syntax highlight coming from 
texlive-latex-recommended.


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fp-utils-3.0.0 depends on:
ii  fpc-source-3.0.0  3.0.0+dfsg-2
ii  libc6 2.23-0ubuntu9

Versions of packages fp-utils-3.0.0 recommends:
ii  fp-compiler-3.0.0  3.0.0+dfsg-2

fp-utils-3.0.0 suggests no packages.

-- no debconf information

Bug#880157: freerdp2: Please disable ffmpeg on Ubuntu

[Mike Gabriel]

Hi Jeremy,

On  Mo 30 Okt 2017 06:41:26 CET, Jeremy Bicha wrote:


Please use this patch to replace the first patch. We found another
unnecessary universe dependency: libgsm.

Thanks,
Jeremy Bicha


Thanks for those patches. And what about debian/control? There is  
still a B-D on libgsm1-dev in debian/control.


How do we address that for cross-distro builds?

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpvOqYWtpsG2.pgp
Description: Digitale PGP-Signatur

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Dmitry Shachnev]

On Mon, Oct 30, 2017 at 09:03:06AM +, Rik Mills wrote:
> The output of dpkg-gensymbols has regressed when reporting new or
> changed symbols
>
> Previously the output stated:
>
> dpkg-gensymbols: debian/libnameDEBIAN/symbols doesn't match completely
> debian/libname.symbols
>
> this now incorrectly states:
>
> dpkg-gensymbols: warning: no debian/symbols file used as basis for
> generating debian/libname/DEBIAN/symbols

The attached small patch fixes the issue for me. Tested with libjpeg-turbo,
where one symbol was deliberately removed.

The previous if (defined $state) check was always true, because a //=
operator is used to define $state two lines above.

--
Dmitry Shachnev
diff --git a/scripts/Dpkg/Shlibs/SymbolFile.pm b/scripts/Dpkg/Shlibs/SymbolFile.pm
index d03ce2598..b36d542ce 100644
--- a/scripts/Dpkg/Shlibs/SymbolFile.pm
+++ b/scripts/Dpkg/Shlibs/SymbolFile.pm
@@ -204,7 +204,7 @@ sub parse {
 my ($self, $fh, $file, %opts) = @_;
 my $state = $opts{state} //= {};
 
-if (defined $state) {
+if (exists $state->{seen}) {
 	return if exists $state->{seen}{$file}; # Avoid include loops
 } else {
 	$self->{file} = $file;


signature.asc
Description: PGP signature

Bug#838817: Cannot reproduce

[intrigeri]

intrigeri:
> I *thought* I had fixed this bug already:

> torbrowser-launcher (0.2.5-1) unstable; urgency=medium
> […]
>   * Remove obsolete conffile /etc/apparmor.d/torbrowser.start-tor-browser
> thanks to Paul Wise. (Closes: #805706)

> … but apparently I failed to get the rm_conffile line right.

FWIW I think I understood the problem… after seeing something very
similar while trying to stop installing
/etc/apparmor.d/usr.bin.torbrowser-launcher: upstream's setup.py still
installs that file, so removing the corresponding cp command from
debian/rules is not enough, and rm_conffile is effectively a noop
given the version number we pass to it. To really get rid of it I had
to:

 - remove the file from the cp command in debian/rules
 - add "rm 
debian/torbrowser-launcher/etc/apparmor.d/usr.bin.torbrowser-launcher"
   in debian/rules' override_dh_install
 - use rm_conffile

Now, this works because I've noticed this before uploading.

For this very bug I'm not sure. But I suspect that bumping the version
number passed to rm_conffile might be enough (we don't ship
torbrowser.start-tor-browser anymore).

Cheers!
-- 
intrigeri

Bug#760307: specto: Does not recognize network connection when using network-manager

[Leandro Noferini]

Package: specto
Version: 0.2.2-3.3
Followup-For: Bug #760307

I can confirm this report

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

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

Versions of packages specto depends on:
ii  gconf23.2.6-4+b1
ii  gnome-icon-theme  3.12.0-2
ii  librsvg2-common   2.40.18-2
ii  python2.7.14-1
ii  python-dbus   1.2.4-1+b3
ii  python-glade2 2.24.0-5.1
ii  python-gnome2 2.28.1+dfsg-1.2
ii  python-gtk2   2.24.0-5.1
ii  python-notify 0.1.1-4
ii  zenity3.24.0-1

specto recommends no packages.

specto suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#868499: osmose-emulator: No sound

[James Cowgill]

Hi,

On 30/10/17 07:33, Carlos Donizete Froes wrote:
> Em dom, 2017-10-29 às 10:22 +, James Cowgill escreveu:
>> Did you read my previous email where I explained what the problem was
>> and gave a patch?
> 
> Sorry, I did not pay attention to your explanation. :(
> 
>> The issue is that osmose-emulator opens the "plughw:0,0" device which
>> might not exist and in any case is incompatible with PulseAudio.
> 
> As the emulator is worked in the old configuration with 'alsa', even changing 
> from 'plughw: 0,0' to
> 'default', will not get audio. Only if 'asoundrc' is set.

I think your reasoning is incorrect. The "default" device should already
be setup in the global "/usr/share/alsa/alsa.conf" file so it works even
if asoundrc does not exist. The reason you should use "default" is
because pulseaudio, if installed, will automatically override it for you.

> But I'll work on changing the emulator audio from "alsa" to "pulseaudio".

While that improves the situation, it doesn't fix the fact that running
the emulator "alsa" mode is still broken.

James



signature.asc
Description: OpenPGP digital signature

Bug#879935: closed by Chris Lamb <la...@debian.org> (Bug#879935: fixed in lintian 2.5.56)

[Chris Lamb]

retitle 879935 Please warn on packages using getconf(1) to get PATH, 
_NPROCESSORS_{CONF,ONLN} etc.
thanks

Hey Guillem,

> Well this only got the patch I supplied to be applied, it didn't implement
> the requested new tag for getconf(1) usage. :)

Okay, let's give this bug a nicer title .. and I await your patch for
the tag ;-)


Best wishes,

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

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

Package: dpkg
Version: 1.19.0.4

The output of dpkg-gensymbols has regressed when reporting new or
changed symbols

Previously the output stated:

dpkg-gensymbols: debian/libnameDEBIAN/symbols doesn't match completely
debian/libname.symbols

this now incorrectly states:

dpkg-gensymbols: warning: no debian/symbols file used as basis for
generating debian/libname/DEBIAN/symbols

Bug#879171: cups: failed to recognize a driver of CP310dm

[Brian Potkin]

On Mon 30 Oct 2017 at 13:10:05 +0900, Atsuhito Kohda wrote:

> Hi Brian,
> 
> On Fri, 27 Oct 2017 11:07:07 +0100, Brian Potkin wrote:
> 
> > There is something wrong with your CUPS installation (or the file
> > itself). I've never seen this in normal operation. It indicates that
> > a simple text file will not be printed. Try to rectify this with
> > 
> >  apt-get --reinstall install cups-daemon
> >  apt-get --reinstall install cups-core-drivers
> > 
> > to install the package versions of mime.types and mime.convs in
> > /usr/share/cups/mime.
> 
> > Remove the .deb you downloaded from fujixerox and install the package
> > printer-driver-fujixerox from the Debian archives. It also comes from
> > fujixerox but it puts files in the right places on the system. Set up
> > the printer as before. This works for me to get a printable version
> > of nsswitch.
> 
> I did reinstall cups-daemon and cups-core-drivers (2.2.5-2),
> then removed (purged in fact) fxlinuxprint and then installed
> printer-driver-fujixerox.
> But when I try to add printer CP310 it failed because
> cups claimed "can't copy PPD file".

This is usually an indication that cups cannot find that PPD. But it
should be installed in /usr/libcups/driver by printer-driver-fujixerox
as fujixerox with a datestamp of Dec 11 2016. Is it?
> 
> So I removed printer-driver-fujixerox then installed
> fxlinuxprint.  Then cups added a printer CP310 but
> its printer driver was show as "Local Raw Printer" wrongly.
> 
> But if I downgraded cups to 2.2.4-7, then cups can add
> a printer CP310 and its printer driver is correctly
> "FX Printer Driver for Linux".
> 
> Further, under this situation, the command
> cupsfilter -p /etc/cups/ppd/CP310.ppd -m printer/CP310 -e /etc/nsswitch  
> 2>log.stretch
> produced a line:
> 
> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
> 
> so I doubt this is any problem.  I can print a test file
> with CP310 (under cups 2.2.4-7).
> It looks to me that cups 2.2.5 has some regression.

Atsuhito, let's stick with testing using cups 2.2.5-2. I assume the
printer is connected by USB. Fing its URI with 'lpinfo -v'. It begins
with "usb://". Now locate the PPD with 'lpinfo -m | grep fujixerox'
Then set up the printer with

 lpadmin -p fuji -v usb://. -E -m fujixerox:/0/cups/model..ppd

(Replace . with what you get from the two lpinfo commands).


Do

 cupsfilter -p /etc/cups/ppd/fuji.ppd -m printer/foo -e --list-filters 
/etc/nsswitch

Or use any other text or image file or a PDF instead of nsswitch. If
that is without error, try printing with

 lp -d fuji /etc/nsswitch

-- 
Brian.

Bug#879935: closed by Chris Lamb <la...@debian.org> (Bug#879935: fixed in lintian 2.5.56)

[Guillem Jover]

Control: reopen -1

On Fri, 2017-10-27 at 19:06:56 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the lintian package:
> 
> #879935: lintian: Please strongly discourage cross-unsafe getconf(1) interface
> 
> It has been closed by Chris Lamb .

Well this only got the patch I supplied to be applied, it didn't implement
the requested new tag for getconf(1) usage. :)

Thanks,
Guillem

Bug#786644: reproducible builds should vary whether nocheck is added to DEB_BUILD_OPTIONS

[Vagrant Cascadian]

Some elements of this issue have changed in the last couple years, so
following up with a few updated points below...

On 2015-05-24, Stuart Prescott wrote:
>> > > I'd expect that setting DEB_BUILD_OPTIONS=nocheck on a package build
>> > > should not change the resulting binary packages. It might make the build
>> > > succeed despite being broken, but if it succeeds without nocheck, it
>> > > should be no different when enabled.
>> > 
>> > Policy is, however, silent on whether that is the correct behaviour or
>> > not.
>> 
>> Policy is silent on many aspects of the distribution, in many cases
>> because they are obviously correct or buggy. Here I'd say the former.
>
> I would disagree that it is obvious that nocheck should not change the 
> contents of the package. I think it's entirely reasonable that test results 
> or 
> test outputs could be shipped as examples or in the documentation. I think 
> it's entirely reasonable that nocheck would thus cause a difference in the 
> package.
>
> Other DEB_BUILD_OPTIONS are supposed to cause the resultant .deb to be 
> different (nostrip and noopt) so it's not true that the package contents have 
> to be invariant on DEB_BUILD_OPTIONS. I can even conceive of situations (such 
> as parallel compressors) where parallel=n could change the output.

The reproducible builds infrastructure does now vary parallelism, fwiw.


>> > Clarifying policy as to what the correct behaviour should be seems to be a
>> > necessary first step.
>> 
>> I don't see why, in this specific case less so when the request is
>> being done on a feature (reproducibility) that is neither in policy.
>
> Precisely because reproducibility is not mandated in policy or even 
> encouraged 
> in devref, I think it is important to only test variations that are commonly 
> agreed-upon as being worth being robust to. Agreement can be evidenced by 
> discussion on mailing lists or by codifying in Policy.

As of debian-policy 4.1, reproducibility is in policy, so this has
changed in the intervening years... though without any specific mention
of DEB_BUILD_OPTIONS.


> So far, there is broad agreement that builds should be robust to when the 
> build was started, the path to the build, the user that runs the build etc. 
> Rapid progress has been made in improving the robustness against variations 
> on 
> these things with the cooperation of many maintainers precisely because they 
> are widely agreed.
...
>> The check does not impose anything on package maintainers, like
>> migration blocking or similar. So even if there was a substantial
>> amount of packages that would fail that test, it would still be useful
>> information for the reproducible effort IMO.
>
> Except that reproducibility is boolean valued and this boolean is exposed to 
> maintainers. There is either a nice little tick on the maintainer's QA page 
> or 
> there is a nasty little cross. If nasty little crosses come from what is 
> considered to be poor tests generating incorrect results, history tells us 
> that the entire column will be ignored. That makes including tests for which 
> there is not broad agreement a net loss for each maintainer, for 
> reproducible.d.n, and for the project.

Now, the qa pages only expose the results of the testing suite
(currently "buster") to the end-users, which is more conservative and
varies fewer things.

If nocheck variation was added to the reproducible builds test
infrastructure, it could be added to tests only on unstable and
experimental.


Some packages take considerably longer running the testsuite than
building the actual package, although I don't have any specific
references at this point off the top of my head.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#879830: [Pkg-privacy-maintainers] Bug#879830: Bug#879830: torbrowser-launcher: AppArmor profiles break torbrowser-launcher when running Linux 4.14

[intrigeri]

Roger Shimizu:
> On Thu, Oct 26, 2017 at 8:44 PM,   wrote:
>> Do you folks think you could upload this within 1-2 weeks, before
>> Linux 4.14 reaches sid? Otherwise, let me know and I'll upload myself.

> You know torbrowser + apparmor better than most of us, so I think you
> just go ahead uploading when you feel OK.

Sure, I'll do it.

Bug#880165: equivs: Please use dpkg-buildpackage instead of debian/rules

[Guillem Jover]

Package: equivs
Version: 2.1.0
Severity: wishlist
X-Debbugs-Cc: Niels Thykier 

Hi!

Niels Thykier noticed that equivs makes direct use of debian/rules, in
reference to the discussion about a possible switch of official build
entry point.

But when I checked the code, I didn't see why this would be even ideal
right now? Doing the direct call means it will be missing several checks,
and possible optimizations.

Why not replace the «fakeroot debian/rules binary» executed possibly
via dpkg-architecture -c, with a proper call to «dpkg-buildpackage -b»?
Possibly with just -a appended?

Thanks,
Guillem

Bug#880164: Debian mirror mirror.sucs.swan.ac.uk: unavailable

[Peter Palfrader]

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org

Hi!

It seems your Debian mirror mirror.sucs.swan.ac.uk is currently
not available.

Status: 
https://mirror-master.debian.org/status/mirror-info/mirror.sucs.swan.ac.uk.html

Please investigate.


Also, almost all Debian mirrors offer the debian tree as /debian.
Could you create an alias for /pub/linux/debian/ as /debian/?  This will
make it easier for people to switch between mirrors.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#880161: www.debian.org: Get rid of the "tidy validation errors" forcing a rebuild of certain files

[Paul Wise]

On Mon, Oct 30, 2017 at 4:09 PM, Paul Wise wrote:

> I'm running it now.

All done. I've also run the tidy scripts and all the errors you
mentioned are gone now, the remaining ones are unrelated to link
attributes.

https://www-master.debian.org/build-logs/tidy/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#880163: xxdiff: utf-8 characters replaced with "?"

[Rod Tye]

Package: xxdiff
Version: 1:4.0.1+dfsg-1+b1
Severity: important
Tags: l10n

Dear Maintainer,

When merging files containing utf-8 characters, xxdiff replaces them with the 
character "?",
even when there are no differences on that line.  Previous versions (for 
example the current
stretch version) save utf-8 characters to the output file unchanged.  

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

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

Versions of packages xxdiff depends on:
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-11
ii  libqtcore4  4:4.8.7+dfsg-11
ii  libqtgui4   4:4.8.7+dfsg-11
ii  libstdc++6  7.2.0-11

xxdiff recommends no packages.

Versions of packages xxdiff suggests:
ii  xterm [x-terminal-emulator]  330-1
pn  xxdiff-scripts   

-- no debconf information

Bug#880161: www.debian.org: Get rid of the "tidy validation errors" forcing a rebuild of certain files

[Paul Wise]

On Mon, Oct 30, 2017 at 3:41 PM, Laura Arjona Reina wrote:

> but many files still need to be rebuilt to use the updated template.

I don't think we need to rebuild the whole website, this script will do:

find -type f -iname '*.html' -print0 |
xargs -0 grep -lZF 'mailto:webmas...@debian.org;' |
xargs -0 echo sed -i 's|mailto:webmas...@debian.org;|mailto:webmas...@debian.org;|g'

I'm running it now.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#880162: The mobile broadband is missing in the network-manager since upgrading it yesterday

[gulfstream]

Package: network-manager
Version: 1.8.4-4
Severity: important


Hi, the package network-manager was upgraded yesterday, and I find it can not 
control my mobile broadband in my laptop today. The mobile broadband is missing 
in the network-manager UI. This function works fine before the upgrading.

Would you please resolve this problem soon? Thank you very much!



Best regards,
Gulfstream




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

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

Versions of packages network-manager depends on:
ii  adduser3.116
ii  dbus   1.11.22-1
ii  libaudit1  1:2.8.1-1
ii  libbluetooth3  5.47-1
ii  libc6  2.24-17
ii  libcurl3-gnutls7.56.1-1
ii  libglib2.0-0   2.54.1-1
ii  libgnutls303.5.16-1
ii  libjansson42.10-1
ii  libmm-glib01.6.8-2
ii  libndp01.6-1+b1
ii  libnewt0.520.52.20-1+b1
ii  libnl-3-2003.2.27-2
ii  libnm0 1.8.4-4
ii  libpam-systemd 235-2
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  libpsl50.18.0-4
ii  libreadline7   7.0-3
ii  libselinux12.7-2
ii  libsystemd0235-2
ii  libteamdctl0   1.26-1+b1
ii  libudev1   235-2
ii  libuuid1   2.30.2-0.1
ii  lsb-base   9.20170808
ii  policykit-10.105-18
ii  udev   235-2
ii  wpasupplicant  2:2.4-1.1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base 2.78-1
ii  iptables 1.6.1-2+b1
ii  iputils-arping   3:20161105-1
ii  isc-dhcp-client  4.3.5-3+b1
ii  modemmanager 1.6.8-2
ii  ppp  2.4.7-1+4

Versions of packages network-manager suggests:
pn  libteam-utils  

-- no debconf information

Bug#879720: RFS: runescape/0.2-1 [QA] -- Multiplayer online game set in a fantasy world

[Tobias Frost]

On Sun, Oct 29, 2017 at 10:24:29PM -0200, Carlos Donizete Froes wrote:
> Em dom, 2017-10-29 às 15:30 +0100, Tobias Frost escreveu:
> > Good!
> > 
> > Sorry for bringing up another issue, but I completly missed that
> > before: The Debian changelog's purpose is not to document changes made
> > to upstream code but only to document changes made to the Debian
> > package. (It is in Debian Policy 4.4)
> > 
> > So in your case those lines should not be d/changelog:
> > 
> >   * Changed icon format and fixed bug in desktop file (Closes:
> > Bug#866227)
> >   * Replaced command line to create temporary directory (Closes:
> > Bug#879784)
> > 
> > Instead of those two lines you would write:
> >   * New upstream release. (Closes: #866227, #879784)
> > 
> > Please fix this and I'll upload.
> 
> Done changes as requested.

Uploaded! Many thanks for your contributions to Debian!

tobi
 
> Thanks!
> 
> -- 
> ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
> ⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
> ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
> ⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

Bug#880161: www.debian.org: Get rid of the "tidy validation errors" forcing a rebuild of certain files

[Laura Arjona Reina]

Package: www.debian.org
Severity: normal
Tags: l10n

With the migration of the website build server from jessie to stretch, we are
using a new version of the "tidy" tool, and now we are getting "Tidy validation
errors" for some webpages containing  tag without .

We have updated the template file that was causing these errors:

https://anonscm.debian.org/viewvc/webwml/webwml/english/template/debian/basic.wml?view=log

but many files still need to be rebuilt to use the updated template.

This is an easy task and do-able for anybody with commit permissions in the
website repo. It's just that there are many files to touch.

How can you help?

Go to the tidy logs
https://www-master.debian.org/build-logs/tidy/

and open a language file having a log file with more than 0 KB.
If you see errors like:

*** /srv/www.debian.org/www/path/to/file.cc.html
line 6 column 3 - Warning:  lacks "rel" attribute

Then the file language/path/to/file.wml needs to be touch:

touch language/path/to/file.wml
cvs commit language/path/to/file.wml

wait for the next tidy check (with the lessoften build) and the next tidy log
should not show that error for that page.

Thanks for your help!

Best regards

Laura Arjona Reina
https://wiki.debian.org/LauraArjona



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

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

Bug#880160: dh-python: dh --with python2 invokes python3 config

[Drew Parsons]

p.s. the code involved is l.174 in
/usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm

Bug#868499: osmose-emulator: No sound

[Carlos Donizete Froes]

Em dom, 2017-10-29 às 10:22 +, James Cowgill escreveu:
> Did you read my previous email where I explained what the problem was
> and gave a patch?

Sorry, I did not pay attention to your explanation. :(

> The issue is that osmose-emulator opens the "plughw:0,0" device which
> might not exist and in any case is incompatible with PulseAudio.

As the emulator is worked in the old configuration with 'alsa', even changing 
from 'plughw: 0,0' to
'default', will not get audio. Only if 'asoundrc' is set.

But I'll work on changing the emulator audio from "alsa" to "pulseaudio".

> It's still broken in 1.2

As of version 1.3, I will change the emulator audio standard to "pulseaudio".

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#879265: Bug#880155: mirror listing update for ftp.tku.edu.tw

[Peter Palfrader]

On Mon, 30 Oct 2017, wisely wrote:

> Submission-Type: update
> Site: ftp.tku.edu.tw
> Type: leaf
> Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 
> kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
> Archive-http: /debian/
> Archive-rsync: debian/
> Maintainer: wisely 
> Country: TW Taiwan
> Comment: According Bug#879265,my site coming back!

Thanks, re-added your site.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#880124: devscripts: [debuild] Please print the actual arguments we make to lintian

[Chris Lamb]

Hi Mattia,

> I applied it after making a small edit (I disliked the idea of printing the
> opts also when finished)

That's a great idea; I agree. Many thanks :)

(The only thing "missing" for me in this area is learning which Lintian version
we are seeing the output of; we could either fix it here or in lintian itself.
Any quick thoughts?)


Regards,

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

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Ximin Luo]

Hendrik Tews:
> Upstream does indeed fix this problem. However, it also contains
> a few files with unclear license and copyright, currently
> preventing to package it. I am trying to solve these license and
> copyright issues with upstream.
> 

Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:

https://release.debian.org/transitions/html/ocaml.html

hol-light is one of the ones near the top, although marked (sid only) so it 
only affects other (sid only) stuff beneath it.

Let me know if I can help with anything.

Ximin

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#878173: stretch-pu: package pdns/4.0.3-1+deb9u1

[Chris Hofstaedtler]

* Adam D. Barratt  [171029 19:16]:
> Control: tags -1 + confirmed

> Please make the changelog distribution "stretch", and feel free to
> upload.

Changed and uploaded, thanks.

> Does this also affect the package in jessie?

After asking upstream about this and checking the code in jessie,
this appears to be a regression in stretch; jessie should be good.

Best,
Chris

Bug#880160: dh-python: dh --with python2 invokes python3 config

[Drew Parsons]

The misconfiguration is triggered by
Build-Depends: python3-all, python3-setuptools

When I remove this reference to python3 then build proceeds normally
under python2.

That's good enough as a work around. But the bug still remains, that
python3 is used (if the python3-all Build-Depends is present) even if
dh --with python3 is not specified. Regardless of the Build-Depends
settings, the dh configuration is ignored.

Drew

Bug#880124: devscripts: [debuild] Please print the actual arguments we make to lintian

[Mattia Rizzolo]

On Sun, 29 Oct 2017, 8:03 p.m. Chris Lamb,  wrote:

> Package: devscripts
> Tags: patch
> Severity: wishlist
>
> Hi,
>
> Attached is the following:
>
>   commit 0b53a5df8297337c50d2aab067598cfd2d6e2159
>   Author: Chris Lamb 
>   Date:   Sun Oct 29 18:54:53 2017 +
>
>   debuild: Print the actual arguments we make to lintian.
>


Thank you for your patch! :)
I applied it after making a small edit (I disliked the idea of printing the
opts also when finished), I hope that's fine with you!

Bug#880160: dh-python: dh --with python2 invokes python3 config

[Drew Parsons]

Package: dh-python
Version: 2.20170125
Severity: normal

I'm packaging sasview
(https://anonscm.debian.org/cgit/debian-science/packages/sasview.git/)

sasview supports python2 only at the moment, so I've configured
debian/rules with
  dh $@ --with python2 --buildsystem=pybuild
  
However when I build, it fails at dh_auto_configure:
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.6 setup.py config 
  File "setup.py", line 55
print "Removing existing build directory", SASVIEW_BUILD, "for a clean 
build"
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(print "Removing existing build directory", SASVIEW_BUILD, "for a clean 
build")?

sasview's setup.py of course has not yet been ported to python3, which
is why I've only set --with python2.

Since I specified a python2 build, then why is 
"python3.6 setup.py config" getting called?



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

Versions of packages dh-python depends on:
ii  python3  3.6.3-2

dh-python recommends no packages.

Versions of packages dh-python suggests:
ii  libdpkg-perl  1.19.0.4

-- no debconf information