Bug#879731: ITP: node-cosmiconfig -- Find and load configuration from different locations

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-cosmiconfig
  Version : 3.1.0
  Upstream Author : David Clark 
* URL : https://github.com/davidtheclark/cosmiconfig#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Find and load configuration from different locations

 Find and load a configuration object from
  - a `package.json` property (anywhere up the directory tree)
  - a JSON or YAML "rc file" (anywhere up the directory tree)
  - a `.config.js` CommonJS module (anywhere up the directory tree)
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain for gitlab 9.5



signature.asc
Description: OpenPGP digital signature

Bug#879730: ITP: node-postcss-load-plugins -- Autoload Plugins for PostCSS

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-postcss-load-plugins
  Version : 2.3.0
  Upstream Author : Michael Ciniawky 
* URL :
https://github.com/michael-ciniawsky/postcss-load-plugins#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Autoload Plugins for PostCSS

 Install plugins and save them to your package.json dependencies/
 devDependencies.
 .
 PostCSS is a tool for transforming styles with JS plugins.  These
plugins can
 lint your CSS, support variables and mixins, transpile future CSS syntax,
 inline images, and more.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain for gitlab 9.5



signature.asc
Description: OpenPGP digital signature

Bug#879728: mysqld fails to start not finding messagefile when started by systemd

[Thomas DEBESSE]

Package: mariadb-server-10.1
Version: 10.1.26-0+deb9u1
Severity: grave

Hi, I just upgraded my server from jessie to stretch and I face a bug
I already reported 13 month ago as bug #837166 but unfortunately this
bug was closed when the related package (mysql-server-5.6) was removed
from archive. But the bug is still present in mariadb-server-10.1
shiped within stretch repository (no backport).

What is expected: “systemctl start mariadb” starts mariadb server.

What is happening: mariadb server shutdowns at startup printing
“[ERROR] Can't find messagefile '/usr/share/mysql/errmsg.sys'” error
message.

Another interesting fact: starting “/usr/sbin/mysqld” from command
line in an interactive shell leads to a working mysql server, but the
exact same command started by systemd leads to a instantaneous
shutdown with error reporting as stated.

Output of “systemctl status mariadb.service” command:

oct. 25 06:49:35 machine mysqld[4868]: 2017-10-25  4:49:35
140131405656640 [Note] /usr/sbin/mysqld (mysqld
10.1.26-MariaDB-0+deb9u1) starting as process 4868 ...
oct. 25 06:49:35 machine mysqld[4868]: 2017-10-25  4:49:35
140131405656640 [ERROR] Can't find messagefile
'/usr/share/mysql/errmsg.sys'

For rerefence, the initial bug report (now closed and archived) with
some detailed explanations:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837166

I set the severity of this bug to “grave” since this bug makes
the package unusable.

The package mariadb-server-10.1=10.1.26-0+deb9u1 is unusable since the
service is not startable.

The mysql-server-5.5=5.5.58-0+deb8u1 package from jessie is known to
not be affected by the bug.

A prior occurrence to this bug was reported on
mysql-server-5.6=5.6.30-1~bpo8+1 at the date of 2016-09-09.

The mariadb-server-10.1=10.1.26-0+deb9u1 package is known to still be
affected by the bug at the date of 2017-10-25.

Previous bug report #837166 says the bug was fixed in version
5.6.35-1+rm, but it's now verified the bug is still there in lately
versions.

-- 
Thomas Debesse

Bug#879193: unable to exit mouse grab, segfaults

[Stéphane Glondu]

Le 22/10/2017 à 19:33, Cesare Leonardi a écrit :
> Stéphane, what's your qemu's commandline?

qemu-system-i386 -enable-kvm \
  -m 4G \
  -hda disk.qcow2 \
  -device e1000,netdev=net0 \
  -netdev user,id=net0,hostfwd=tcp::-:22 \
  -usbdevice host:1050:0010

-- 
Stéphane

Bug#879729: pk4-replace discards the build commands output

[Guido Günther]

Package: pk4
Version: 3
Severity: wishlist

Hi,
a "pk4-replace" discards the builds output. To diagnose problems it
would be nice to have stdout/stderr either print to stdout/stderr as
well or at least logged to file.
Cheers
 -- Guido

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

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

Versions of packages pk4 depends on:
ii  debian-keyring  2017.08.28
ii  devscripts  2.17.10
ii  dpkg-dev1.18.24
ii  libc6   2.24-17
ii  systemd-sysv235-2

Versions of packages pk4 recommends:
ii  sbuild  0.73.0-4

pk4 suggests no packages.

-- no debconf information

Bug#879727: debhelper: dh_systemd_start script fails to start new units when an existing unit is updated (LP#1707880)

[Niels Thykier]

Package: debhelper
Version: 10.10.3
Severity: important

Quote from [LP#1707880]:

"""
Upon upgrading apt from a version that only ships apt-daily.timer to the one 
that ships apt-daily.timer and apt-daily-upgrade.timer, the latter is not 
started on zesty and later.

I believe this may be a bug in dh_systemd_start:

# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
 systemctl --system daemon-reload >/dev/null || true
 if [ -n "$2" ]; then
  _dh_action=try-restart
 else
  _dh_action=start
 fi
 deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
fi
# End automatically added section

This reduces to:
deb-systemd-invoke try-restart apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true

which is (after calling/checking policy-rc.d) is:
systemctl try-restart apt-daily-upgrade.timer apt-daily.timer >/dev/null || true

This is correct, for the apt-daily.timer and does nothing for the 
apt-daily-upgrade.timer. Since apt-daily-upgrade.timer is not active, 
try-restart does not start it.

Imho, there should be an extra snippet in apt.postinst which does this:

if [ -d /run/systemd/system ]; then
 if dpkg --compare $2 with version that introduces apt-daily-upgrade.timer; then
 deb-systemd-invoke start apt-daily-upgrade.timer >/dev/null || true
 fi
fi
"""

I am not entirely sure this can be solved in debhelper, so we may need
some extra functionality from deb-systemd-invoke (as debhelper does
not know when a service was introduced and when it wasn't).

Thanks,
~Niels

[LP#1707880]: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1707880

Bug#772812:

[Bernhard Schmidt]

Control: tags -1 + upstream
Control: found -1 2.4.3-4
Control: forwarded -1 https://community.openvpn.net/openvpn/ticket/538


Hi Nikola,

> The upstream bug (https://community.openvpn.net/openvpn/ticket/538) is
> not fixed, and I can still reproduce this on Ubuntu 17.10 with openvpn
> 2.4.3.

Thanks, tagging accordingly.

Bernhard

Bug#879725: #879725

[Paul Wise]

On Wed, 2017-10-25 at 07:01 +0200, Adam Borowski wrote:

> It's not supported by Firefox 57, yeah.

The removal of XUL support in Firefox 57 is irrelevant to the removal
of Firebug from Debian, which is more about DevTools replacing Firebug.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#877470: bsh; please make the build reproducible (timestamps)

[jathan]

On Wed, 04 Oct 2017 07:27:08 +0100 Chris Lamb  wrote:
> Hi,
> 
> > bsh; please make the build reproducible (timestamps)
> 
> +SOURCE_DATE_EPOCH   ?= $(shell dpkg-parsechangelog -STimestamp)
> 
> I'd actually use /usr/share/dpkg/pkg-info.mk for this :)
> 
> +   --clamp-mtime --mtime="$(SOURCE_DATE_EPOCH)"
> 
> Shouldn't this be --mtime="@$(SOURCE_DATE_EPOCH)" (nb. with the @?)
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> 
> Hi,

I have rewrited the bsh patch based on the observations and suggestions
of Lamby, sending a new bsh_2.0b4-18_2.0b4-18.1.debdiff file. The
attached patch clamps the timestamps to the changelog timestamp when
creating the source archive using SOURCE_DATE_EPOCH variable. Once
applied, bsh can be built reproducibly in our current experimental
framework. Cheers.

Jathan

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es
diff -Nru bsh-2.0b4/debian/changelog bsh-2.0b4/debian/changelog
--- bsh-2.0b4/debian/changelog  2016-05-30 12:14:02.0 -0500
+++ bsh-2.0b4/debian/changelog  2017-10-24 23:46:23.0 -0500
@@ -1,3 +1,10 @@
+bsh (2.0b4-18.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix timestamps_in_tarball reproducible build issue. 
+
+ -- Jonathan Bustillos   Tue, 24 Oct 2017 
23:46:23 -0500
+
 bsh (2.0b4-18) unstable; urgency=medium
 
   * Team upload.
diff -Nru bsh-2.0b4/debian/rules bsh-2.0b4/debian/rules
--- bsh-2.0b4/debian/rules  2016-05-30 12:06:22.0 -0500
+++ bsh-2.0b4/debian/rules  2017-10-24 23:44:07.0 -0500
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 # debian/rules file for bsh (uses cdbs)
 
+include /usr/share/dpkg/pkg-info.mk
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/ant.mk
 
@@ -29,6 +30,7 @@
 install/bsh-src:: binary-install/bsh-doc
mkdir -p debian/bsh-src/usr/src/bsh-src
tar --exclude debian --exclude classes --exclude dist --exclude api \
+   --clamp-mtime --mtime="@$(SOURCE_DATE_EPOCH)" \ 
-zcf debian/bsh-src/usr/src/bsh-src/bsh.tar.gz *
 
 binary-fixup/bsh-doc::


signature.asc
Description: OpenPGP digital signature

Bug#879725: #879725

[Adam Borowski]

> Should firebug be removed from Debian? According to Mozilla it has been
> replaced by the standard Firefox DevTools:

> https://hacks.mozilla.org/2017/10/saying-goodbye-to-firebug/

It's not supported by Firefox 57, yeah.

Because FF57 lost most of its functionality, though, there's a good chance
one of projects to fork Firefox may succeed.  At the moment, Waterfox looks
promising, and as it has a history as a custom patch set, it might stay at
least in the medium term.

Firefox 52 is supported until mid-2018, I think it'd be a good idea to wait
until then and see what happens.  It's possible that WebExtension APIs
required to reimplement a significant part of XUL extensions would be added,
but I'm somehow not holding my breath.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. 
⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift
⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters
⠈⠳⣄ relevant to duties], shall be punished by death by shooting.

Bug#879726: ITP: node-is-directory -- checks if a given path is directory

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-is-directory
  Version : 0.3.1
  Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert)
* URL : https://github.com/jonschlinkert/is-directory
* License : Expat
  Programming Lang: JavaScript
  Description : checks if a given path is directory

 Returns true if a filepath exists on the file system and it's directory
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain for gitlab 9.5



signature.asc
Description: OpenPGP digital signature

Bug#879725: firebug: remove from Debian? replaced by Firefox DevTools

[Paul Wise]

Source: firebug
Severity: wishlist

Should firebug be removed from Debian? According to Mozilla it has been
replaced by the standard Firefox DevTools:

https://hacks.mozilla.org/2017/10/saying-goodbye-to-firebug/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#879667: [debhelper-devel] Bug#879667: Missing component in generated control file Section: line for dbgsym packages

[Mihai Moldovan]

On 10/24/2017 06:40 PM, Niels Thykier wrote:
> I have attached a patch that I hope you can test to see if it fixes your
> problem.

I've rebuilt the debhelper package in sid with the patch applied and inserted it
forcefully into an sbuild build environment.

Seems to work, the dbgsym packages now all have a component in their Section
again (if the source package defined one).


I'd really appreciate an upload to unstable!



Mihai



signature.asc
Description: OpenPGP digital signature

Bug#879724: gphotofs FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: gphotofs
Version: 0.5-4
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap

gphotofs fails to cross build from source, because it uses the build
architecture pkg-config and thus fails finding required packages that
are only requested for the host architecture. Its own m4 macros set up
the PKG_CONFIG environment variable to point to the build architecture
pkg-config and thus make the standard PKG_* macros use the wrong
pkg-config. Calling back into PKG_PROG_PKG_CONFIG fixes the issue as the
latter takes $ac_tool_prefix into account.  Please consider applying the
attached patch.

Helmut
Index: gphotofs-0.5/m4m/gp-pkg-config.m4
===
--- gphotofs-0.5.orig/m4m/gp-pkg-config.m4
+++ gphotofs-0.5/m4m/gp-pkg-config.m4
@@ -19,8 +19,8 @@
 fi
 
 dnl AC_REQUIRE([PKG_CHECK_MODULES])
-AC_PATH_PROG([PKG_CONFIG],[pkg-config],[false])
-if test "$PKG_CONFIG" = "false"; then
+PKG_PROG_PKG_CONFIG
+if test "x$PKG_CONFIG" = "x"; then
 AC_MSG_ERROR([
 *** Build requires pkg-config
 ***

Bug#879723: can get stuck in state INSANE and stop responding

[Joey Hess]

Package: netplug
Version: 1.2.9.2-3
Severity: normal

If the netplug script fails to bring up the interface, netplug can
put it into state INSANE. Unfortunately, it never leaves that state,
preventing netplug from responding to further link changes.

This log shows the problem occurring. Probably the link was lost while
the dhclient was trying to up the interface. It remained in state INSANE
for hours, and the daemon had to be restarted to clear it up.

Oct 24 11:36:30 honeybee netplugd[650]: eth0: state INACTIVE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1
Oct 24 11:36:30 honeybee netplugd[2115]: /etc/netplug/netplug eth0 in -> pid 
2115
Oct 24 11:36:30 honeybee dhclient[2132]: Internet Systems Consortium DHCP 
Client 4.3.5
Oct 24 11:36:30 honeybee dhclient[2132]: Copyright 2004-2016 Internet Systems 
Consortium.
Oct 24 11:36:30 honeybee dhclient[2132]: All rights reserved.
Oct 24 11:36:30 honeybee dhclient[2132]: For info, please visit 
https://www.isc.org/software/dhcp/
Oct 24 11:36:30 honeybee dhclient[2132]: 
Oct 24 11:36:30 honeybee dhclient[2132]: Listening on LPF/eth0/02:93:05:81:f2:aa
Oct 24 11:36:30 honeybee dhclient[2132]: Sending on   LPF/eth0/02:93:05:81:f2:aa
Oct 24 11:36:30 honeybee dhclient[2132]: Sending on   Socket/fallback
Oct 24 11:36:30 honeybee dhclient[2132]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 3
Oct 24 11:36:33 honeybee dhclient[2132]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 5
Oct 24 11:36:39 honeybee dhclient[2132]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 7
Oct 24 11:36:46 honeybee dhclient[2132]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 14
Oct 24 11:37:00 honeybee dhclient[2132]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 21
Oct 24 11:37:20 honeybee netplugd[650]: eth0: state INNING pid 2115 exited 
status 256
Oct 24 11:39:27 honeybee netplugd[650]: eth0: state INSANE flags 0x00011043 
UP,BROADCAST,RUNNING,MULTICAST,1 -> 0x1003 UP,BROADCAST,MULTICAST
Oct 24 11:39:28 honeybee netplugd[650]: eth0: state INSANE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1
Oct 24 11:39:38 honeybee netplugd[650]: eth0: state INSANE flags 0x00011043 
UP,BROADCAST,RUNNING,MULTICAST,1 -> 0x1003 UP,BROADCAST,MULTICAST
Oct 24 11:39:40 honeybee netplugd[650]: eth0: state INSANE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1
Oct 24 22:40:43 honeybee netplugd[650]: eth0: state INSANE flags 0x00011043 
UP,BROADCAST,RUNNING,MULTICAST,1 -> 0x1003 UP,BROADCAST,MULTICAST
Oct 24 23:37:30 honeybee netplugd[650]: eth0: state INSANE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1
Oct 24 23:37:55 honeybee netplugd[650]: eth0: state INSANE flags 0x00011043 
UP,BROADCAST,RUNNING,MULTICAST,1 -> 0x1003 UP,BROADCAST,MULTICAST
Oct 24 23:37:56 honeybee netplugd[650]: eth0: state INSANE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1
Oct 24 23:39:35 honeybee netplugd[650]: eth0: state INSANE flags 0x00011043 
UP,BROADCAST,RUNNING,MULTICAST,1 -> 0x1003 UP,BROADCAST,MULTICAST
Oct 24 23:39:37 honeybee netplugd[650]: eth0: state INSANE flags 0x1003 
UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,1

In if_info.c, line 351, this code gets it into INSANE:

case ST_INNING:
if (exitok)
info->state = ST_ACTIVE;
else
info->state = ST_INSANE; /* ??? */
break;

There is no way out of INSANE once entered. ifsm_flagchange, there is this:

case ST_INSANE:
/* stay insane until there's been quiet for a while, then
   down interface and switch to ST_DOWN */
break;

That might be the right place to fix it, but as far as I can see, there's
no code following through on that comment.

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

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

Versions of packages netplug depends on:
ii  iproute   1:4.9.0-2
ii  iproute2  4.9.0-2
ii  libc6 2.24-17
ii  lsb-base  9.20170808

netplug recommends no packages.

netplug suggests no packages.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#879722: lintian: W-shlibs-symbol-not-found: false positive

[Shawn Landden]

Package: lintian
Version: 2.5.55
Severity: normal

dpkg-shlibdeps: warning: symbol __aeabi_atexit@CXXABI_ARM_1.3.3 used by 
debian/libkyotocabinet16v5/usr/lib/arm-linux-gnueabi/libkyotocabinet.so.16.13.0 
found in none of the libraries

dpkg-shlibdeps: warning: symbol __aeabi_atexit@CXXABI_ARM_1.3.3 used by 
debian/libkyotocabinet16v5/usr/lib/arm-linux-gnueabihf/libkyotocabinet.so.16.13.0
 found in none of the libraries

armel and armhf

-- 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_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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29.1-6
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.4
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.19.0.4
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-8
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-2
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-8
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.4
ii  libhtml-parser-perl3.72-3+b2
pn  libtext-template-perl  

-- no debconf information

Bug#879721: debian-handbook: missing link in 5.2.1.1. Dependencies: the Depends Field

[Xiao Shengwen]

Package: debian-handbook
Version: 8.20170125
Severity: normal

5.2.1.1. Dependencies: the Depends Field

http://www.debian.org/doc/debian-policy/ch-relationships.html

This link is missing.

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

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

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

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: runescape
   Version : 0.2-1
   Upstream Author : Carlos Donizete Froes 
 * URL : https://github.com/coringao/runescape/wiki
 * License : BSD-2-Clause
   Section : games

  It builds those binary packages:

runescape  - Multiplayer online game set in a fantasy world

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

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

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

   dget -x 
https://mentors.debian.net/debian/pool/non-free/r/runescape/runescape_0.2-1.dsc

  More information about Runescape can be obtained from 
https://github.com/coringao/runescape

  Changes since the last upload:

  changelog version: 0.2
  * Fixed desktop file
  * Added initial file transfer progress bar
  * Updated game executable script
  * Changed makefile version

  Regards,
   Carlos Donizete Froes

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

[Gedalya]

Package: libsane-hpaio
Version: 3.17.9+repack0-1

Just tried using simple-scan with my new HP OfficeJet Pro 8710. The AIO is 
connected by ethernet.

simple-scan says no scanner is detected. Syslog says:

simple-scan: io/hpmud/model.c 532: no officejet_pro_8710 attributes found in 
/usr/share/hplip/data/models/models.dat
simple-scan: io/hpmud/model.c 543: no officejet_pro_8710 attributes found in 
/usr/share/hplip/data/models/unreleased/unreleased.dat

I was able to fix the problem by duplicating the [hp_officejet_pro_8710] secion 
in /usr/share/hplip/data/models/models.dat, starting on line 59706, and 
renaming it to [officejet_pro_8710] as the log suggests. That works fine.

Regards,

Gedalya

Bug#878515: lintian: Use of uninitialized value in string eq at …/checks/fields.pm line 512. / Use of uninitialized value in string ne at …/checks/fields.pm lines 521 and 537.

[Chris Lamb]

tags 878515 + pending
thanks

Fixed in Git. Thanks for the report, Axel :)

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=8e5b05587f58c757cfe88cb095ca77805c181c66


Regards,

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

Bug#870078: libsane1 breaks all 3rd party scanner drivers

[Jeremy Bicha]

Control: tags -1 +patch

Ok, with help from infinity and RAOF, this solution appears to work. You
can keep the libsane1 package name and you don't have to add a transitional
package.

infinity strongly recommended the Conflicts instead of Breaks for this
situation.

https://irclogs.ubuntu.com/2017/10/25/%23ubuntu-release.html


--- a/debian/control2017-10-24 15:15:49 +
+++ b/debian/control2017-10-25 01:42:21 +
@@ -77,8 +77,9 @@
 Section: libs
 Architecture: any
 Multi-Arch: same
-Breaks: libsane (<< 1.0.27-1)
-Replaces: libsane (<< 1.0.27-1)
+Conflicts: libsane (<< 1.0.27-1~)
+Replaces: libsane (<< 1.0.27-1~)
+Provides: libsane (= ${binary:Version})
 Pre-Depends: ${misc:Pre-Depends}
 Depends:
  acl [linux-any],


Thanks,
Jeremy Bicha

Bug#806515: ITP: pyclipper -- Cython wrapper for the C++ translation of the Angus Johnson's Clipper library

[Jeremy Bicha]

retitle -1 ITP: pyclipper -- Cython wrapper for the C++ translation of the
Angus Johnson's Clipper library
owner -1 Jeremy Bicha 
block 848206 by -1

I will be working on this with Ming-ting Yao Wei (魏銘廷) since it's
needed for fonts-noto-color-emoji. It willl be maintained by the pkg-fonts
team.

Packaging is at
https://anonscm.debian.org/git/pkg-fonts/pyclipper.git

Thanks,
Jeremy Bicha

Bug#806516: ITP: python-booleanoperations -- Boolean operations on paths

[Jeremy Bicha]

retitle -1 ITP: python-booleanoperations -- Boolean operations on paths
owner -1 Jeremy Bicha 
block 848206 by -1

I will be working on this with Ming-ting Yao Wei (魏銘廷) since it's
needed for fonts-noto-color-emoji. It willl be maintained by the pkg-fonts team.

The source package is such a long name that it feels like it would be
fairly unique now.

The old packaging  was at
https://anonscm.debian.org/git/pkg-fonts/booleanoperations.git

but we might be moving it to
https://anonscm.debian.org/git/pkg-fonts/python-booleanoperations.git

Thanks,
Jeremy Bicha

Bug#879663: remmina: [regression] cannot type letters in Firefox in VMware vSphere Web Client in console views

[Paul Wise]

On Tue, 2017-10-24 at 22:51 +0200, Matteo F. Vescovi wrote:

> So, upstream says, the only solution so far is to disable the 'Use
> client keyboard mapping' setting.

That worked for me, thanks.

I don't think I ever changed that setting, so I am assuming that the
default is to have 'Use client keyboard mapping' turned on. Upstream
might want to add a FAQ entry about this issue.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#879718: aptly: Aptly can't handle deb packages built using dpkg 1.19.0+

[Boyuan Yang]

Package: aptly
Version: 0.8-3
Severity: important
Tags: jessie stretch sid
X-Debbugs-CC: debian-d...@lists.debian.org

Dear maintainer,

Current aptly cannot handle deb packages built using dpkg (>= 1.19.0~) since 
the new deb files now use "control.tar.xz" instead of "control.tar.gz". The 
root cause is that dpkg-deb (>= 1.19.0~) now enables "--uniform-compression" 
by default.

This bug is already reported upstream:
https://github.com/smira/aptly/issues/655

This bug is pretty serious since all new packages built on new Debian-based 
systems will not be compatible with aptly. I will keep tracking this bug and 
raise severity when upstream releases the fix.

CC-ing debian-dpkg maillist to make dpkg staff aware of this side-effect. We 
could expect that other Debian archive management tools break as well.

Regards,
Boyuan Yang

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

Bug#878271: Update ledmon to 0.80

[Anthony Wong]

Hi Jared,

Yes, we can help to do that.

Thanks,
Anthony

On 25 October 2017 at 03:50,  wrote:

> Hi Anthony,
>
> I will try to get to this this week. Can Canonical Taipei help validate? I
> currently don't have hardware to do so.
>
> --
> Jared Domínguez
> OS Architect
> Linux Engineering
> Dell | Client Product Group
>
> From: Anthony Wong [mailto:anthony.w...@canonical.com]
> Sent: Wednesday, October 11, 2017 5:47 PM
> To: Debian Bug Tracking System 
> Subject: Bug#878271: Update ledmon to 0.80
>
> Package: ledmon
> Version: 0.79-2+b2
> X-Debbugs-CC: mailto:yc.ch...@canonical.com, mailto:Mario.Limonciello@
> dell.com
>
> Please update ledmon to 0.80, per Intel this version is required for RSTe.
>
> https://qa.debian.org/cgi-bin/watch?pkg=ledmon
> https://sourceforge.net/p/ledmon/code/ci/be5c7bf743b421a21be93791c40dd4
> ca91c87315/log/?path=
> Thanks,
> Anthony
>

Bug#878031: [pkg-cryptsetup-devel] Bug#878031: cryptsetup: Freeze while typing decryption password

[Doug S]

So far I've failed to run the cryptsetup command. I type the UUID for the
encrypted partition and also tried the /dev/sda3 way, but the initramfs
prompt says it doesn't exist. I must be doing something wrong. I will check
the partition path and UUID again later.

How do I boot normally now? From the initramfs prompt? I suppose the
cryptsetup command is necessary, therefore I am locked out. I don't mind
reinstalling Debian though. I'll do it now.

The reason why I don't think this is a hardware issue is because the other
laptop I have here started having the same issue at the same time, probably
after some update. They are both Dell Inspirons. In Arch Linux, for
instance, the problem is gone. It works normally.


Em terça-feira, 17 de outubro de 2017, Jonas Meurer 
escreveu:

> Hi Doug,
>
> please send a copy of your replies to the bugreport (use reply to all),
> so others than me (e.g. co-maintainers of the package) can read them as
> well.
>
> Am 10.10.2017 um 23:19 schrieb Doug S:
> > Should I try "cryptsetup open /dev/sda2 cryptolvm --debug" ? I really
> > don't know the command. It's what the Debian installer sets by default.
> > But how could I open the device at runtime? Debian needs the partition
> > to be open in order to keep running, right? How would I close it and
> > open again?
>
> So you're talking about the disk unlocking that's happening early in the
> boot process? Apparently you have your root disk encrypted so the
> unlocking happens in initramfs.
>
> In that case you're right, it's impossible to re-lock and re-unlock the
> device while running the system.
>
> In case that you're able to, please do the following:
>
> * boot your system with the kernel commandline 'break=top'. An initramfs
>   emergency shell should be spawned.
> * Inside the initramfs emergency shell, run the cryptsetup command
>   manually:
>
>   # cryptsetup --debug luksOpen \
> UUID=e12ee94c-924e-43c2-8578-276388731e95 sda3_crypt
>
> * Save the output to some persistant storage and send it to us.
>
> The fact that you encounter the same freeze with Fedora sounds
> suspicious. Probably it's some hardware issues?
>
> You could also remove the 'quiet' kernel commandline option and see
> whether you see any useful boot logging messages.
>
> Cheers,
>  jonas
>
> > 2017-10-08 19:57 GMT-03:00 Jonas Meurer  
> > >:
> >
> > Hi Doug,
> >
> > Am 08.10.2017 um 23:42 schrieb Doug S.:
> > >   As I begin typing the first characters of my decryption
> > password, the prompt
> > > seems to freeze and ignore some of those characters, which leads
> > to typing the
> > > wrong password every first attempt. It does not happen again for
> the
> > > consecutive attempts.
> > >
> > >   I do not use Plymouth in Debian. This is also reproducible in
> Fedora
> > > Workstation 26 (with Plymouth, which lets me see the freeze
> > happening).
> >
> > Can you please provide the exact commands that you use to unlock your
> > dm-drypt volume? Also, please run them with '--debug' and attach the
> > output.
> >
> > Cheers
> >  jonas
> >
> > > -- Package-specific info:
> > > -- /proc/cmdline
> > > BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/alq14--vg-root
> > ro quiet
> > >
> > > -- /etc/crypttab
> > > sda3_crypt UUID=e12ee94c-924e-43c2-8578-276388731e95 none luks
> > >
> > > -- /etc/fstab
> > > # /etc/fstab: static file system information.
> > > #
> > > # Use 'blkid' to print the universally unique identifier for a
> > > # device; this may be used with UUID= as a more robust way to name
> > devices
> > > # that works even if disks are added and removed. See fstab(5).
> > > #
> > > #  
> 
> > > /dev/mapper/alq14--vg-root /   ext4
> > errors=remount-ro 0   1
> > > # /boot was on /dev/sda2 during installation
> > > UUID=d8773f5e-4431-4ee2-bdcf-309fd1dfd507 /boot   ext2
> > defaults0   2
> > > # /boot/efi was on /dev/sda1 during installation
> > > UUID=F673-568B  /boot/efi   vfatumask=0077  0   1
> > > /dev/mapper/alq14--vg-home /home   ext4defaults
> > 0   2
> > > /dev/mapper/alq14--vg-swap_1 noneswapsw
> >   0   0
> > >
> > > -- lsmod
> > > Module  Size  Used by
> > > fuse   98304  3
> > > ctr16384  4
> > > ccm20480  2
> > > nls_ascii  16384  1
> > > nls_cp437  20480  1
> > > vfat   20480  1
> > > fat69632  1 vfat
> > > snd_hda_codec_hdmi 49152  1
> > > iTCO_wdt   16384  0
> > > iTCO_vendor_support16384  1 iTCO_wdt
> > > dell_wmi   16384  0
> > > arc4   16384  2
> > > sparse_keymap  1

Bug#879717: Wallpapers should have a better quality

[Axel Beckert]

Control: tag -1 + moreinfo

Hi Frank,

Frank Brütting wrote:
> Package: dwallpaper-debian
> 
> I hope this is the right package…

Unfortunately not. There is no package named "dwallpaper-debian", not
even similar one.

> The wallpapers are actually pretty nice, but the color transition of
> the backgrounds sadly isn’t, because I can see steps of color,
> instead of a smooth gradient. Could you therefore please raise the
> color depth

Please figure out the path name to the affected file (example:
/usr/share/lxqt/themes/dark/wallpaper.png) and then run "dpkg -S" with
that path as parameter. Example:

$ dpkg -S /usr/share/lxqt/themes/dark/wallpaper.png
lxqt-common: /usr/share/lxqt/themes/dark/wallpaper.png

In that example "lxqt-common" would be the right package.

In case the "dpkg -S" command yields no result, symbolic links
may be parts of the path to the file as you found it. In that case
call "readlink -f" on that path first. Example:

$ dpkg -S 
/usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg
dpkg-query: no path found matching pattern 
/usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg
$ readlink -f 
/usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg
/usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1920x1080.svg
$ dpkg -S 
/usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1920x1080.svg
desktop-base: 
/usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1920x1080.svg

In that case "desktop-base" would be the correct package.

You don't need to file a new bug report for that, just tell us the
package and we'll reassign your bug report to the correct package.

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

Bug#879713: Acknowledgement (konsole: Konsole freezes for a minute when I press backspace in empty command line)

[wzabo...@elektron.elka.pw.edu.pl]

Hi,
I have checked, that other terminals available in MATE like

  * xterm
  * mate-terminal
  * xfce4-terminal

are not affected by the above problem. Only konsole windows freeze when
I press backspace in the empty commandline.

Regards,

Wojtek

-- 
Wojciech M Zabolotny, PhD
Institute of Electronic Systems
Faculty of Electronics and Information Technology
Warsaw University of Technology

Bug#879717: Wallpapers should have a better quality

[Frank Brütting]

Package: dwallpaper-debian

I hope this is the right package…

The wallpapers are actually pretty nice, but the color transition of 
the backgrounds sadly isn’t, because I can see steps of color, 
instead of a smooth gradient. Could you therefore please raise the 
color depth?



I am using Debian GNU/Linux Stretch.

Bug#878926: Users of btrfs-progs from stretch-backports will need a bpo of btrbk (>= 0.25.1)

[Nicholas D Steeves]

On Wed, Oct 25, 2017 at 12:39:45AM +0200, Axel Burri wrote:
> Here's a quick summary of the btrbk dependencies:
> 
> all versions of btrbk >= 0.23.0 require btrfs-progs >= 3.18.2
> 
> btrbk-0.25.0 supports ALL versions of btrfs-progs <= 4.11.1
> btrbk-0.25.1 supports ALL versions of btrfs-progs <= 4.13.1
> btrbk-0.26.0 supports ALL versions of btrfs-progs >= 3.18.2
> 
> 
> > To prevent this, please provide a bpo of btrbk-0.25.1.
> 
> Unfortunately I'm not a debian user myself and don't know much about all
> this. If I understand it correctly, this is not needed now?

If you'd like to support all Debian users of btrbk, then it is
needed, but if you don't want to maintain a backported package please
let me know, so I can forward this info to debian-backports.  Here is
the rationale:

Currently in stretch/stable: btrfs-progs-4.7.3-1 and btrbk-0.24.0-1
  * no problems
Currently in sid/unstable: btrfs-progs-4.13.3-1 and btrbk-0.26.0-1
  * no problems
Stretch user with btrfs-progs-4.9.1~bpo9+1 and btrbk-0.24.0-1
  * no problems (I think)
Stretch user who has btrfs-progs-4.9.1~bpo9+1, who receives automatic
upgrade to btrfs-progs-4.13.3~bpo9+1, or who enables stretch-backports
specifically to install a newer btrfs-progs (this is recommended by
upstream btrfs devs, as I'm sure you know ;-) )
  - has btrbk-0.24.0-1
  - Dependency resolution does one of these, because "Breaks" was
added to btrfs-progs:
  1) blocks upgrade to btrfs-progs-4.13.3~bpo9+1
  2) removes btrbk-0.24.0-1 (btrbk is uninstalled but not purged)
  3) user forces upgrade, breaking dependency resolution and
 backups stop working.
  4) installs btrbk-0.26.0-1~bpo9+1
  * Apt will chose #4 as the optimal resolution 100% of the time
if a bpo of btrbk is available.  I believe #1 is its first
choice if a bpo of btrbk is not available and #2 would be the
second choice resolution offered by aptitude.  Additionally, I
think that apt will also put btrfs-progs-4.9.1~bpo9+1 into the
"held state" if a bpo of btrbk is not available.
  
If a backport of btrbk-0.26.0 is made, a user can use
btrfs-progs-4.7.3-1 from stable with btrbk-0.26.0-1~bpo9+1.  So there
is always one reason (or three reasons, depending on how you count)
why a backport is needed, and no reasons against.

If you don't tag Debian releases then you can merge commit@point to
a stretch-backports branch.  I like to use tags, because then I don't
have to remember which commit I uploaded to unstable.  You can even
script it.  eg, after the stretch-backports branch is set up:

#!/bin/sh
git tag -l
echo -n "what is the version in testing? "
read testing_version
git merge debian/$testing_version
git mergetool
dch --bpo
# remove extra line that looks like "  *   "
git add debian/changelog
git commit
echo -n "what is version in backports, or in stable if NEW"
read bpo_version
# copy and paste the tag you want
gbp buildpackage --git-pbuilder \
--git-debian-branch=stretch-backports \
--git-dist=stretch-backports \
--git-tag \
-v${bpo_version}
# I think the following will also work, but I haven't tested it
# dpkg-buildpackage -v${bpo_version}
# git clean -fd
# head -1 debian/changelog
# echo -n "what is the new version? "
# read new_version
# paste the version from first entry of changelog
# new_version=$(echo $new_version | sed s:\~:_:)
# git tag debian/$new_version


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#879716: ITP: usbauth-notifier -- Notifier for USB Firewall to use with desktop environments

[Stefan Koch]

Package: wnpp
Severity: wishlist
Owner: Stefan Koch 

* Package name: usbauth-notifier
  Version : 1.0
  Upstream Author : Stefan Koch 
* URL : https://github.com/kochstefan/usbauth-all/usbauth-notifier
* License : GPL-2.0
  Programming Lang: C
  Description : Notifier for USB Firewall to use with desktop environments

A notifier for the usbauth firewall against BadUSB attacks. The user could 
manually allow or deny USB devices.
Every user that wants use the notifier must be added to the usbauth group.

This work was initially created for SUSE in 2015. Part of it was the USB 
interface authorization for the Linux kernel. It's contained in Linux since 
kernel version 4.4.

Please add the packages libusbauth-configparser, usbauth, usbauth-notifier to 
debian unstable.

See also: openSUSE package request 
(https://build.opensuse.org/request/show/533514)

Bug#879203: ITP: redisearch -- search engine on top of Redis

[Chris Lamb]

tags 879203 + pending
thanks

This is now in NEW.


Regards,

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

Bug#879715: ITP: usbauth -- USB firewall against BadUSB attacks

[Stefan Koch]

Package: wnpp
Severity: wishlist
Owner: Stefan Koch 

* Package name: usbauth
  Version : 1.0
  Upstream Author : Stefan Koch 
* URL : https://github.com/kochstefan/usbauth-all/usbauth
* License : GPL-2.0
  Programming Lang: C
  Description : USB firewall against BadUSB attacks

It is a firewall against BadUSB attacks. A config file descibes in which way 
USB interfaces would be accepted or denied.
To the kernel an interface authorization was developed with this firewall.
The firewall sets the authorization mask according to the rules.

This work was initially created for SUSE in 2015. Part of it was the USB 
interface authorization for the Linux kernel. It's contained in Linux since 
kernel version 4.4.

Please add the packages libusbauth-configparser, usbauth, usbauth-notifier to 
debian unstable.

See also: openSUSE package request 
(https://build.opensuse.org/request/show/533513)

Bug#878926: Users of btrfs-progs from stretch-backports will need a bpo of btrbk (>= 0.25.1)

[Axel Burri]

Here's a quick summary of the btrbk dependencies:

all versions of btrbk >= 0.23.0 require btrfs-progs >= 3.18.2

btrbk-0.25.0 supports ALL versions of btrfs-progs <= 4.11.1
btrbk-0.25.1 supports ALL versions of btrfs-progs <= 4.13.1
btrbk-0.26.0 supports ALL versions of btrfs-progs >= 3.18.2


> To prevent this, please provide a bpo of btrbk-0.25.1.

Unfortunately I'm not a debian user myself and don't know much about all
this. If I understand it correctly, this is not needed now?

Bug#877541: [pkg-go] Bug#877541: prometheus FTBFS on i386: FAIL github.com/prometheus/prometheus/storage/local [build failed]

[Martín Ferrari]

forwarded 877541 https://github.com/golang/go/issues/22429
thanks

I have opened an issue in upstream's tracker:
https://github.com/golang/go/issues/22429

-- 
Martín Ferrari (Tincho)

Bug#879714: ITP: libusbauth-configparser1 -- Library for USB Firewall including flex/bison parser

[Stefan Koch]

Package: wnpp
Severity: wishlist
Owner: Stefan Koch 

* Package name: libusbauth-configparser1
  Version : 1.0
  Upstream Author : Stefan Koch 
* URL : 
https://github.com/kochstefan/usbauth-all/libusbauth-configparser
* License : LGPL-2.1
  Programming Lang: C
  Description : Library for USB Firewall including flex/bison parser

The library is used to read the usbauth config file into data structures and is 
used by usbauth and YaST.

This work was initially created for SUSE in 2015. Part of it was the USB 
interface authorization for the Linux kernel. It's contained in Linux since 
kernel version 4.4.
Please add the packages libusbauth-configparser, usbauth, usbauth-notifier to 
debian unstable.

See also: openSUSE package request 
(https://build.opensuse.org/request/show/533512)

Bug#877541: [pkg-go] Bug#877541: prometheus FTBFS on i386: FAIL github.com/prometheus/prometheus/storage/local [build failed]

[Martín Ferrari]

If I disable optimizations (-N option for go tool compile), the error
disappears. I think this confirms it is a compiler bug.

$ GOPATH=$PWD/build go test -c -v -gcflags=-N
github.com/prometheus/prometheus/storage/local
$ GOPATH=$PWD/build go test -c -v
github.com/prometheus/prometheus/storage/local
# github.com/prometheus/prometheus/storage/local
build/src/github.com/prometheus/prometheus/storage/local/storage_test.go:2028:26:
invalid instruction: 01483
(/tmp/buildd/prometheus-1.8.1+ds/build/src/github.com/prometheus/prometheus/storage/local/storage_test.go:2029)
FMOVD   ""..autotmp_78+176(DX)(SP*1), F0
$

Bug#874321: backtraces from generic extractor: "Compressed file ended before the end-of-stream marker was reached"

[Joey Hess]

Rogério Brito wrote:
> I believe that you meant to file this as a Python bug and I think that the
> severity is, quite frankly, lower than normal...

I don't think this is a python bug. It's reasonable for pythons's gzip
library to fail when presented with corrupted data. It does not know
it's being used to download an url. Perhaps it should have a mode where
it tries to extract as much data is it can, in case its caller wants to
try to be robust.

I think this is a bug in youtube-dl though, because of this code:

std_headers = {
...
'Accept-Encoding': 'gzip, deflate',
}

if resp.headers.get('Content-encoding', '') == 'gzip':
content = resp.read()
gz = gzip.GzipFile(fileobj=io.BytesIO(content), mode='rb')
try:
uncompressed = io.BytesIO(gz.read())
except IOError as original_ioerror:
# There may be junk add the end of the file
# See http://stackoverflow.com/q/4928560/35070 for details
for i in range(1, 1024):
try:
gz = gzip.GzipFile(fileobj=io.BytesIO(content[:-i]), 
mode='rb')
uncompressed = io.BytesIO(gz.read())
except IOError:
continue
break
else:
raise original_ioerror

It's encouraging gzip to be used (rather than deflate or no compression),
and it already contains workarounds for similar problems. This code
smells.

There is probably a python library that implements this robustly.
I tried python-urllib3:

joey@darkstar:~>python
Python 2.7.14 (default, Sep 17 2017, 18:50:44) 
[GCC 7.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import urllib3
>>> http = urllib3.PoolManager()
>>> headers = {'Accept-Encoding': 'gzip'}
>>> r = http.request('GET', 'http://www.debian.org/', headers=headers)
>>> r.headers.get("Content-Encoding")
'gzip'
>>> len(r.data)
14871

So that seems to work. I think because it uses zlib to decompress the data,
not gzip.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#617856: apt-show-versions: does not see gzipped Packages files when uncompressed are not available

[Julian Andres Klode]

On Fri, Mar 11, 2011 at 06:56:58PM -0300, Rogério Brito wrote:
> Package: apt-show-versions
> Version: 0.17
> Severity: important
> 
> Hi.
> 
> On my system, apt-show-versions started complaining with the message:
> 
> Error: No information about packages! (Maybe no deb entries?)
> 
> Of course, I do have deb entries in my system. Reading the source code, I
> saw that there was this snippet of code:
> 
> ,
> | @files = map { $list_dir . $_} grep /Packages$/, readdir(DIR);
> `
> 
> right there in the initialization of the cache. Since my system only has
> gzipped files as shown by "ls /var/lib/apt/lists/*Packages*",
> apt-show-versions goes on to say that it found no informations about the
> packages, but the files are there, only gzipped (that is, ending with
> Packages.gz extension, instead of only Packages).
> 
> If you need any further information, please let me know.

Please fix that and use apt-get indextargets 'Created-By: Packages'
combined with /usr/lib/apt/apt-helper cat-file to read the file - I
added the appropriate apt-internals usertag for de...@lists.debian.org
in a separate messages. I expect to turn compressed indexes on by default
this release cycle, this bug will become release-critical at that point.

Users might want to use apt list instead which basically provides a
similar output with colors. I'd also be happy to take over apt-show-versions
and replace it with the fully compatible C++ version I developed 4 years
ago (it's much faster and does not need a cache, it only needs access
to the apt cache, output wise it's the same as 0.21 AFAICT), and move it
into the apt team.

Thanks.

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

Bug#654041: Pending fixes for bugs in the junit package

[pkg-java-maintainers]

tag 654041 + pending
thanks

Some bugs in the junit package are closed in revision
e1f051da140712613b211519fe34e1b4f72bd758 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/junit.git/commit/?id=e1f051d

Commit message:

Removed Michael Koch from the uploaders (Closes: #654041)

Bug#879713: konsole: Konsole freezes for a minute when I press backspace in empty command line

[Wojciech Zabołotny]

Package: konsole
Version: 4:16.12.0-4
Severity: important

Dear Maintainer,

Since a few days (or weeks?) I experience a strange behavior in konsole.
When editing a command line, if I press backspace too many times finally
trying to delete a character from an empty line, konsole freezes for ca.
one minute. The CPU load is almost 0%, other programs in the X windows
session work corectly. Even other konsole windows work correctly.

The interesting thing is that the problem occurs exactly ones in each
konsole window. It doesn't matter how many tabs I open. If I press backspace
in the empty command line for the first time in one of open tabs, the whole
window freezes. After it recovers, I can safely press backspace in all tabs
without any problems.
In fact it looks like konsole gets blocked trying to connect to certain not
running network service.

I don't know it it matters, but I use konsole in the MATE session.

Regards,
Wojtek

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

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

Versions of packages konsole depends on:
ii  kio   5.37.0-2
ii  konsole-kpart 4:16.12.0-4
ii  libc6 2.24-17
ii  libkf5completion5 5.37.0-2
ii  libkf5configcore5 5.37.0-2
ii  libkf5configgui5  5.37.0-2
ii  libkf5configwidgets5  5.37.0-2
ii  libkf5coreaddons5 5.37.0-2
ii  libkf5crash5  5.37.0-2
ii  libkf5dbusaddons5 5.37.0-2
ii  libkf5i18n5   5.37.0-2
ii  libkf5iconthemes5 5.37.0-2
ii  libkf5kiowidgets5 5.37.0-2
ii  libkf5notifyconfig5   5.37.0-2
ii  libkf5widgetsaddons5  5.37.0-2
ii  libkf5windowsystem5   5.37.0-2
ii  libkf5xmlgui5 5.37.0-2
ii  libqt5core5a  5.9.1+dfsg-9
ii  libqt5gui55.9.1+dfsg-9
ii  libqt5widgets55.9.1+dfsg-9
ii  libstdc++67.2.0-11

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information

Bug#873986: Pending fixes for bugs in the junit package

[pkg-java-maintainers]

tag 873986 + pending
thanks

Some bugs in the junit package are closed in revision
a3ae949850cf908bb26656604eb1a387c3274dc9 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/junit.git/commit/?id=a3ae949

Commit message:

Fixed the build failure with Java 9 (Closes: #873986)

Bug#566998: perforate: This bug is a misunderstanding combined with a misfeature

[Reuben Thomas]

Package: perforate
Version: 1.2-5
Followup-For: Bug #566998

The reason that finddup fails in this case is that it was run in verbose
mode (in two ways: first by passing the -v option, and secondly by passing
the -n option, which implies -v).

The verbose mode’s messages are sent to stdout, and so get into the output
file finddup.out.

finddup does not know how to parse this, so it doesn’t work properly when it
is run on that file.

Finally, the -o option does not take an argument; rather, the old output
must be supplied on stdin.

The following two commands work correctly, after the test setup given by the
reporter:

# finddup -d test > finddup.out
# finddup -o < finddup.out

To make it less likely to get into this mess, I’ve changed -v to print to
stderr in my recent improvements (shortly coming as version 1.3).

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

Versions of packages perforate depends on:
ii  libc6  2.23-0ubuntu9

perforate recommends no packages.

perforate suggests no packages.

-- no debconf information

Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Adrian Bunk]

On Tue, Oct 24, 2017 at 05:50:05PM -0400, Jeremy Bicha wrote:
> On Tue, Oct 24, 2017 at 5:34 PM, Adrian Bunk  wrote:
> > Any fix for swt-gtk should also include fixing the other RC bug #879170,
> > and that would keep webkitgtk in buster - removing webkitgtk from buster
> > without also removing libswt-webkit-gtk-3-jni is simply wrong.
> >
> > An actual fix has to include either updating Eclipse or removing
> > Eclipse from buster.
> 
> Yeah, um, I looked into removing Eclipse from Buster and from what I
> saw, it did not appear practical. See my report at comment #130
> https://bugs.debian.org/681726
> 
> Eclipse is the only remaining reverse-depends of #879170 in Testing
> once tuxguitar migrates soon. So if we ignore Eclipse, we're left with
> the RC bug I am fixing in my NMU being the only thing keeping
> webkitgtk from being removed from Buster.
>...

Your "if we ignore Eclipse" is not a valid approach.

If removing Eclipse from buster is not practical, then removing a
(transitive) dependency of Eclipse is not practical.

> Thanks,
> Jeremy Bicha

cu
Adrian

-- 

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

Bug#879712: python-wokkel: please use new upstream code with support for Python 3

[W. Martin Borgert]

Package: python-wokkel
Version: 0.7.1-1
Severity: wishlist

There is new code by upstream here:
https://github.com/ralphm/wokkel
It seems to support Python 3.
Please consider packaging the new code, even if no formal release has been made.
Thanks!

Bug#879170: Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Jeremy Bicha]

On Tue, Oct 24, 2017 at 5:34 PM, Adrian Bunk  wrote:
> Any fix for swt-gtk should also include fixing the other RC bug #879170,
> and that would keep webkitgtk in buster - removing webkitgtk from buster
> without also removing libswt-webkit-gtk-3-jni is simply wrong.
>
> An actual fix has to include either updating Eclipse or removing
> Eclipse from buster.

Yeah, um, I looked into removing Eclipse from Buster and from what I
saw, it did not appear practical. See my report at comment #130
https://bugs.debian.org/681726

Eclipse is the only remaining reverse-depends of #879170 in Testing
once tuxguitar migrates soon. So if we ignore Eclipse, we're left with
the RC bug I am fixing in my NMU being the only thing keeping
webkitgtk from being removed from Buster.

There's also https://bugs.debian.org/879228 but I'm hoping that will
be solvable and in my opinion it doesn't need to block webkitgtk's
removal. I am mentioning both of these outstanding RC bugs in the RM
bug I plan to file with the Release Team next week so it will be up to
them to decide.

Thanks,
Jeremy Bicha

Bug#614505: Patch for this feature request

[Emmanuel Bourg]

Le 24/10/2017 à 23:43, Thomas Goirand a écrit :

> Here's the patch, sorry for this.
> 
> Let me know if I can upload as per this debdiff.

Could you rebase it against the version 2.7.7+dfsg-8 please?

Bug#614505: Patch for this feature request

[Thomas Goirand]

On 10/24/2017 10:02 PM, Emmanuel Bourg wrote:
> Le 24/10/2017 à 19:16, Thomas Goirand a écrit :
> 
>> Here's a patch adding Python 3 support to the package. This also patches
>> antlr.py, and also packages the proper way, ie with a produced egg-info
>> file as it should.
>>
>> Please consider uploading this fix. This is needed, and would allow
>> adding Python 3 support to 2 other packages which indirectly need this.
>>
>> Alternatively, please allow me to NMU.
> 
> Thank you for the help Thomas. I can't see the patch attached, could you
> send it again please?
> 
> A team upload would be preferable to a NMU. You are already a member of
> the pkg-java group, so feel free to commit to the repository directly
> and upload the update.
> 
> The repository has been migrated to Git today:
> 
> https://anonscm.debian.org/cgit/pkg-java/antlr.git

Here's the patch, sorry for this.

Let me know if I can upload as per this debdiff.

Cheers,

Thomas Goirand
diff -Nru antlr-2.7.7+dfsg/debian/changelog antlr-2.7.7+dfsg/debian/changelog
--- antlr-2.7.7+dfsg/debian/changelog   2016-01-27 08:27:30.0 +
+++ antlr-2.7.7+dfsg/debian/changelog   2017-10-24 14:46:42.0 +
@@ -1,3 +1,10 @@
+antlr (2.7.7+dfsg-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Python 3 support.
+
+ -- Thomas Goirand   Tue, 24 Oct 2017 14:46:42 +
+
 antlr (2.7.7+dfsg-7) unstable; urgency=medium
 
   * Team upload.
diff -Nru antlr-2.7.7+dfsg/debian/control antlr-2.7.7+dfsg/debian/control
--- antlr-2.7.7+dfsg/debian/control 2016-01-27 08:01:06.0 +
+++ antlr-2.7.7+dfsg/debian/control 2017-10-24 14:46:42.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Java Maintainers 

 Uploaders: Torsten Werner 
-Build-Depends: debhelper (>= 9), default-jdk, python (>= 2.6.6-3~), 
autotools-dev, python-all-dev (>= 2.3.5-11), sharutils
+Build-Depends: debhelper (>= 9), default-jdk, python (>= 2.6.6-3~), 
autotools-dev, python-all-dev (>= 2.3.5-11), sharutils, python3-all-dev, 
python-setuptools, python3-setuptools, dh-python
 Build-Depends-Indep: maven-repo-helper
 Standards-Version: 3.9.6
 Vcs-Svn: svn://anonscm.debian.org/pkg-java/trunk/antlr
@@ -74,12 +74,21 @@
 Package: python-antlr
 Section: python
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: python-six, ${misc:Depends}, ${python:Depends}
 Replaces: antlr (<< 2.7.7-10)
 Breaks: antlr (<< 2.7.7-10)
-Description: language tool for constructing recognizers, compilers etc
- This package contains the Python version of antlr. ANTLR stands for
+Description: language tool for constructing recognizers, compilers etc - 
Python 2.7
+ This package contains the Python 2.7 version of antlr. ANTLR stands for
  ANother Tool for Language Recognition, (formerly PCCTS).
  .
  See antlr package for a complete description.
 
+Package: python3-antlr
+Section: python
+Architecture: all
+Depends: python3-six, ${misc:Depends}, ${python3:Depends}
+Description: language tool for constructing recognizers, compilers etc - 
Python 3.x
+ This package contains the Python 3.x version of antlr. ANTLR stands for
+ ANother Tool for Language Recognition, (formerly PCCTS).
+ .
+ See antlr package for a complete description.
diff -Nru antlr-2.7.7+dfsg/debian/patches/python3-compat.patch 
antlr-2.7.7+dfsg/debian/patches/python3-compat.patch
--- antlr-2.7.7+dfsg/debian/patches/python3-compat.patch1970-01-01 
00:00:00.0 +
+++ antlr-2.7.7+dfsg/debian/patches/python3-compat.patch2017-10-24 
14:46:42.0 +
@@ -0,0 +1,297 @@
+Description: Python3 compat
+Author: Thomas Goirand 
+Bug-Debian: https://bugs.debian.org/614505
+Forwarded: no
+Last-Update: 2017-10-24
+
+--- antlr-2.7.7+dfsg.orig/lib/python/antlr/antlr.py
 antlr-2.7.7+dfsg/lib/python/antlr/antlr.py
+@@ -2,13 +2,11 @@
+ ## details..Copyright (C) Wolfgang Haefelinger, 2004.
+ 
+ ## get sys module
++from __future__ import print_function
+ import sys
+ 
+-version = sys.version.split()[0]
+-if version < '2.2.1':
+-False = 0
+-if version < '2.3':
+-True = not False
++import six
++from six.moves import range
+ 
+ ######
+ ### global symbols ###
+@@ -45,7 +43,7 @@ def version():
+ 
+ def error(fmt,*args):
+ if fmt:
+-print "error: ", fmt % tuple(args)
++print("error: ", fmt % tuple(args))
+ 
+ def ifelse(cond,_then,_else):
+ if cond :
+@@ -55,7 +53,7 @@ def ifelse(cond,_then,_else):
+ return r
+ 
+ def is_string_type(x):
+-return  (isinstance(x,str) or isinstance(x,unicode))
++return  (isinstance(x,str) or isinstance(x,six.text_type))
+ 
+ def assert_string_type(x):
+ assert is_string_type(x)
+@@ -549,9 +547,9 @@ class Token(object):
+ Token.badToken = Token( type=INVALID_TYPE, text="")
+ 
+ if __name__ == "__main__":
+-print "testing .."
++print("testing ..")
+ T = Token.b

Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Adrian Bunk]

On Tue, Oct 24, 2017 at 03:26:06PM -0400, Jeremy Bicha wrote:
> Control: tags -1 pending
> 
> I am uploading a NMU now that is numbered as swt-gtk 3.8.2-4.1 to drop
> the unnecessary build-depends since this is the last thing keeping
> webkitgtk in Buster. I am uploading to DELAYED/2. Please let me know
> if I should delay this fix any further. git patch attached.

I fail to see how this makes sense.

Any fix for swt-gtk should also include fixing the other RC bug #879170, 
and that would keep webkitgtk in buster - removing webkitgtk from buster 
without also removing libswt-webkit-gtk-3-jni is simply wrong.

An actual fix has to include either updating Eclipse or removing 
Eclipse from buster.

> Thanks,
> Jeremy Bicha

cu
Adrian

-- 

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

Bug#877541: [pkg-go] Bug#877541: prometheus FTBFS on i386: FAIL github.com/prometheus/prometheus/storage/local [build failed]

[Martín Ferrari]

reassign 877541 golang-1.9
retitle 877541 golang-1.9: Invalid instruction error in i386
thanks

This seems to be an issue with go 1.9, this error is not reproducible
with other versions of go:

$ /usr/lib/go-1.7/bin/go test -c -v
github.com/prometheus/prometheus/storage/local
$ /usr/lib/go-1.8/bin/go test -c -v
github.com/prometheus/prometheus/storage/local
$ /usr/lib/go-1.9/bin/go test -c -v
github.com/prometheus/prometheus/storage/local
# github.com/prometheus/prometheus/storage/local
build/src/github.com/prometheus/prometheus/storage/local/storage_test.go:2028:26:
invalid instruction: 01483
(/tmp/buildd/prometheus-1.8.1+ds/build/src/github.com/prometheus/prometheus/storage/local/storage_test.go:2029)
FMOVD   ""..autotmp_78+176(DX)(SP*1), F0


I can't find any reference listing this instruction as valid i386, but
maybe I am not looking correctly.

It is the same issue as #877319. Also, I don't see anything weird in the
code (it faults at the for):

got := it.RangeValues(metric.Interval{OldestInclusive: 0,
NewestInclusive: 3})
// Note that we cannot just reflect.DeepEqual(want, got) because
it has
// the semantics of NaN != NaN.
for i, gotSamplePair := range got {
wantSamplePair := want[i]
if !wantSamplePair.Equal(&gotSamplePair) {
t.Fatalf("want %v, got %v", wantSamplePair,
gotSamplePair)
}
}


On 02/10/17 13:45, Adrian Bunk wrote:
> Source: prometheus
> Version: 1.7.2+ds-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=prometheus&arch=i386&ver=1.7.2%2Bds-1&stamp=1506959630&raw=0
> 
> ...
> FAIL  github.com/prometheus/prometheus/storage/local [build failed]
> ...
> dh_auto_test: cd build && go test -v -p 4 -timeout 20m 
> github.com/prometheus/prometheus/cmd/prometheus 
> github.com/prometheus/prometheus/cmd/promtool 
> github.com/prometheus/prometheus/config 
> github.com/prometheus/prometheus/discovery 
> github.com/prometheus/prometheus/discovery/azure 
> github.com/prometheus/prometheus/discovery/consul 
> github.com/prometheus/prometheus/discovery/dns 
> github.com/prometheus/prometheus/discovery/ec2 
> github.com/prometheus/prometheus/discovery/file 
> github.com/prometheus/prometheus/discovery/gce 
> github.com/prometheus/prometheus/discovery/marathon 
> github.com/prometheus/prometheus/discovery/openstack 
> github.com/prometheus/prometheus/discovery/triton 
> github.com/prometheus/prometheus/discovery/zookeeper 
> github.com/prometheus/prometheus/notifier 
> github.com/prometheus/prometheus/promql 
> github.com/prometheus/prometheus/relabel 
> github.com/prometheus/prometheus/retrieval 
> github.com/prometheus/prometheus/rules 
> github.com/prometheus/prometheus/storage github.com/prometheus/pr
>  ometheus/storage/fanin github.com/prometheus/prometheus/storage/local 
> github.com/prometheus/prometheus/storage/local/chunk 
> github.com/prometheus/prometheus/storage/local/codable 
> github.com/prometheus/prometheus/storage/local/index 
> github.com/prometheus/prometheus/storage/local/storagetool 
> github.com/prometheus/prometheus/storage/metric 
> github.com/prometheus/prometheus/storage/remote 
> github.com/prometheus/prometheus/template 
> github.com/prometheus/prometheus/util/cli 
> github.com/prometheus/prometheus/util/flock 
> github.com/prometheus/prometheus/util/httputil 
> github.com/prometheus/prometheus/util/promlint 
> github.com/prometheus/prometheus/util/stats 
> github.com/prometheus/prometheus/util/strutil 
> github.com/prometheus/prometheus/util/testutil 
> github.com/prometheus/prometheus/util/treecache 
> github.com/prometheus/prometheus/web 
> github.com/prometheus/prometheus/web/api/v1 
> github.com/prometheus/prometheus/web/ui returned exit code 2
> debian/rules:46: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 2
> 
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> 


-- 
Martín Ferrari (Tincho)

Bug#844268: [pkg-boost-devel] Bug#844268: libboost1.62-doc doesn't contain the actual documentation

[Dimitri John Ledkov]

On 24 October 2017 at 16:07, Steve M. Robbins  wrote:
> On Tue, Oct 24, 2017 at 02:04:44PM +0100, Dimitri John Ledkov wrote:
>> On 24 October 2017 at 04:00, Steve M. Robbins  wrote:
>
>
>> > If I re-enable the doc packages and build, lintian spews dozens of
>> > errors of three kinds: privacy-breach-logo, privacy-breach-generic,
>> > privacy-breach-uses-embedded-file.
>> >
>> > E: libboost1.65-doc: privacy-breach-logo 
>> > usr/share/doc/libboost1.65-doc/HTML/doc/html/quickbook/syntax/block.html 
>> > (http://sourceforge.net/sflogo.php?group_id=28447&type=1)
>> > W: libboost1.65-doc: privacy-breach-generic 
>> > usr/share/doc/libboost1.65-doc/HTML/libs/assert/doc/html/assert.html 
>> > (https://fonts.googleapis.com/css?family=open+sans:300,300italic,400,400italic,600,600italic%7cnoto+serif:400,400italic,700,700italic%7cdroid+sans+mono:400,700)
>> > E: libboost1.65-doc: privacy-breach-uses-embedded-file 
>> > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/accessors_8hpp.html 
>> > You may use the libjs-mathjax package. 
>> > (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
>> > E: libboost1.65-doc: privacy-breach-uses-embedded-file 
>> > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adapt__adt_8hpp.html
>> >  You may use the libjs-mathjax package. 
>> > (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
>> > E: libboost1.65-doc: privacy-breach-uses-embedded-file 
>> > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adapt__struct_8hpp.html
>> >  You may use the libjs-mathjax package. 
>> > (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
>> > E: libboost1.65-doc: privacy-breach-uses-embedded-file 
>> > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adjust_8hpp.html 
>> > You may use the libjs-mathjax package. 
>> > (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
>> >
>> >  etc.
>> >
>>
>> The google fonts in assert appear to be generated by calling asciidoc
>> -> i wonder if debian's asciidoc can be made to not generate those
>> and/or use local fonts?
>>
>> For the mathjax, there appears to be support in Doxygen files to
>> specify a url from libjs-mathjax package.
>>
>> Let's see if we can fix up these docs to be offline, and also file
>> issues as appropriate about things we cannot offline.
>
> OK.  So the original approach -- the one that generated the big
> lintian list -- is to simply use the files as they appear in the
> source distribution.  To do what you suggest, I think we need to move
> to a strategy that actually generates documentation during the package
> build.  Will you look into setting that up?  The 1.65.1 is otherwise
> ready to go, from my point of view.

Yes indeed it should be actually rebuilt. I've patched the asciidoctor
and the doxygen files but i'm failing to figure out how to rebuild all
the .html files.

It seems like the preffered form of modification is not the source
tarball we use, as all the paths in this tarball with pre-built .html
documentation are not those that are expected by Jamfiles to build the
docs.

After bootstrapping b2 / bjam using all the documentation toolchain it
fails to build by not able to find the right paths to all the
split-modules in the assembled tarball =/

I wonder if we should start generating our own tarballs from git
checkouts out boost. In which case having our packaging as a debian
submodule may makes sense as well..

I'm not sure i will be able to tackle this in a day. Can we upload
1.65.1 as is now, and I'll work on building the docs on a long weekend
or some such?


-- 
Regards,

Dimitri.

Bug#854414: screen: after sshing, some commands give error "Error opening terminal: screen.xterm-256color."

[Egmont Koblinger]

Hi guys,

Quickly glazing through the thread, a couple of remarks:

- screen/tmux indeed needs that TERM inside them is something
screen-related. Forget xterm or xterm-256color, go with screen,
screen-256color or screen.xterm-256color or alike. This is properly
documented in their docs/faqs and answered on hundreds of random forums
(whereas, of course, the opposite is also answered on random forums, you
should use common sense which answers to trust :)) The most notable
difference is the lack of "bce" causing colored lines (e.g. in midnight
commander) not to fill the entire line, but there are other differences as
well.

- The most standard setup according to my experiences is that TERM=xterm of
the graphical terminal emulator (8/16 colors) translates into TERM=screen
inside (also 8/16 colors), whereas TERM=xterm-256color of the external
emulator ideally translates into TERM=screen-256color. I haven't heard of
any problems with this approach. (Well, strictly speaking you're still in
trouble if you launch screen from a 256-color emulator, detach and then
re-attach from an 8/16-color one.)

- Then ncurses added screen.xterm-256color, which, according to screen's
old-time behavior of prepending "screen." if such a definition is
available, messed up ssh'ing and friends. Of course given screen's
behavior, there's no way such a change could've been introduced without
such breakages.

- I don't understand why you're reluctant moving screen.xterm and
screen.xterm-256color from ncurses-term into ncurses-base. Of course it
wouldn't fix a thing now, but it's not clear to me what it'd break, and
it's desired to make screen.xterm{,-256color} widely available in the long
run. Please do it as soon as possible.

- On my machine (Ubuntu Artful) screen-256color and screen.xterm-256color
are not exactly the same file. We should investigate what's the difference
and why, and which one's the better to have.

- 256 colors became pretty standard perhaps like 5-7 years ago. Since then,
some of us put noticeable effort into pushing even further and have
truecolor support here and there (with less limited success than 256
colors, but it's already available at many places). Please, pretty please
don't make a step backwards and don't advocate solutions/workaround that
reduce the available colors to 8/16. Please don't recommend TERM=xterm or
TERM=screen as a workaround where the underlying terminal is known to
support 256 colors.

- A proper workaround might be to set screen-256color from screenrc, or
translate TERM=screen.xterm-256color into TERM=screen-256color in
/etc/bashrc.

- I've never seen anyone quoting from me; Sven, I'm happy to see you did :)
I can't remember where I wrote those exact words, but I've sure written
something analogous at multiple places. One day I might write a standalone
page summarizing all the issues and outlining a recommendation for
something better.

cheers,
egmon

Bug#877582: ls quoting redamaged

[Wyatt Ward]

Michael Stone wrote:
>
> Or you could set an environment variable, but if you want to patch it instead 
> that's your choice.
>
> Mike Stone
I have no desire to do this on every system I maintain for the remainder of 
eternity. This should not be a default - it should be opted into, for the 
reasons given on the mailing list last time this mess came up.
I'm disappointed; I thought Debian was doing the right thing, but it turned out 
to just be a stopgap measure.
I'll stop complaining about this here, since I assume there are better places 
to argue about it.

Bug#879709: [Aptitude-devel] Bug#879709: cannot install unar

[Axel Beckert]

Control: tag -1 unreproducible
Control: close -1

Hi Jidanni,

積丹尼 Dan Jacobson wrote:
> Package: aptitude
> Version: 0.8.9-1
> 
> Cannot install unar

Works fine for me on both Debian Sid amd64 and i386.

Such issues are likely caused by either broken package dependencies,
not uptodate package lists or by packages from experimental
incompatible with versions from unstable..

In this case this looks like inconsistent versions of binary packages
build by the gcc-8 being available.

For example there is no version 8-20171016-1 of gcc-8-base in Debian
anymore since Monday morning (i.e. 1.5 days ago).

Updating your package lists (or switching the mirror if that one is
out-of-date) should fix your issue.

And refrain from reporting uninstallablity bug reports against
aptitude (or apt) without having tested your issue against uptodate
package lists beforehand. In most cases, such cases are no bug in the
packaging tools, but either packages or the local system.

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

Bug#879711: bash: Annoying "bad substitution" warning when tab-completing inside backquotes

[Benjamin Moody]

Package: bash
Version: 4.4-5
Severity: minor

Dear Maintainer,

When, at the bash prompt, I type something like:

   g c c  ` / u  b  p k g - c 

I expect this to be completed as:

   $ gcc `/usr/bin/pkg-config

(this is a somewhat silly example, but should give you the idea...)

However, every time I press Tab in this example, it displays a warning
message such as:

   bash: bad substitution: no closing "`" in `/usr

which is extremely annoying, because this message appears in the
middle of the text I'm trying to type.  So my screen looks like this:

   $ gcc `/ubash: bad substitution: no closing "`" in `/usr
   sr/bbash: bad substitution: no closing "`" in `/usr/bin
   in/pkg-cbash: bad substitution: no closing "`" in `/usr/bin/pkg-config
   onfig

This problem has been around for a while, but not forever (just tested
bash 4.2.37 from wheezy and it doesn't have this issue.)

It appears to be independent of whether the bash-completion package is
installed.  I usually disable completion entirely ('complete -r' in my
.bashrc), and that seems to make no difference.


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/40 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 bash depends on:
ii  base-files   9.9+deb9u1
ii  dash 0.5.8-2.4
ii  debianutils  4.8.1.1
ii  libc62.24-11+deb9u1
ii  libtinfo56.0+20161126-1+deb9u1

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- debconf-show failed

Bug#879710: ser-player: FTBFS on hurd-i386: pipp_get_filename, {fopen,remove}_utf8 undefined

[Aaron M. Ucko]

Source: ser-player
Version: 1.7.0-3
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org

Thanks for fully addressing #879126; the latest kfreebsd-i386 build of
ser-player succeeded, and I expect the next kfreebsd-amd64 build will
too.

Meanwhile, I see that builds for hurd-i386 (not a release architecture
either) are failing with "undefined reference" errors, as detailed
below.

Could you please take a look?

Thanks!



build/o/unix/ser_player.o: In function `c_ser_player::open_ser_file(QString 
const&)':
./src/ser_player.cpp:2088: undefined reference to 
`pipp_get_filename_from_filepath(std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/pipp_ser.o: In function 
`c_pipp_ser::fix_broken_ser_file(std::__cxx11::basic_string, std::allocator > const&)':
./src/pipp_ser.cpp:335: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/pipp_ser.o: In function 
`c_pipp_ser::open(std::__cxx11::basic_string, 
std::allocator > const&, int, int)':
./src/pipp_ser.cpp:58: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/pipp_ser_write.o: In function `c_pipp_ser_write::create(QString 
const&, int, int, bool, int)':
./src/pipp_ser_write.cpp:52: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
./src/pipp_ser_write.cpp:67: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/pipp_ser_write.o: In function `c_pipp_ser_write::close()':
./src/pipp_ser_write.cpp:236: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
./src/pipp_ser_write.cpp:256: undefined reference to 
`remove_utf8(std::__cxx11::basic_string, 
std::allocator > const&)'
build/o/unix/pipp_avi_write.o: In function `c_pipp_avi_write::create(char 
const*, int, int, bool, int, int, int, int, void*)':
./src/pipp_avi_write.cpp:535: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/pipp_avi_write.o: In function `c_pipp_avi_write::split_create()':
./src/pipp_avi_write.cpp:592: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
build/o/unix/gif_write.o: In function `c_gif_write::create(QString const&, int, 
int, int, bool, int, c_gif_write::e_colour_quant_type, int, bool, int, int, 
int)':
./src/gif_write.cpp:183: undefined reference to 
`fopen_utf8(std::__cxx11::basic_string, 
std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&)'
collect2: error: ld returned 1 exit status
Makefile:280: recipe for target 'bin/ser-player' failed
make[1]: *** [bin/ser-player] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:12: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

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

Bug#848833: dh-make: change default debhelper compat level to 10

[Craig Small]

A year ago? Wow I better get to it.

On Wed, 25 Oct. 2017, 04:48 Jack Bates,  wrote:

> On Tue, 20 Dec 2016 10:58:47 +0800 Paul Wise  wrote:
> > Package: dh-make
> > Severity: wishlist
> >
> > Please change the default debhelper compat level to 10. This has a
> > number of changes but important one is parallel building by default.
>
> +1
>
-- 
Craig Small https://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linuxhttps://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#879709: cannot install unar

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.8.9-1

Cannot install unar

# aptitude install unar
The following NEW packages will be installed:
  libgnustep-base1.24{ab} (D: gnustep-base-common) (unar D: libgnustep-base1.24)
  libobjc4{a} (D: libgnustep-base1.24, D: unar) (unar D: libobjc4)  unar
The following packages will be upgraded:
  gcc-8-base (unar D: libobjc4 D: gcc-8-base)
The following packages will NOT be UPGRADED:
  libatomic1{ab} (D: gcc-8-base)  libcc1-0{ab} (D: gcc-8-base)  libcilkrts5{ab} 
(D: gcc-8-base)
  libgcc1{ab} (D: gcc-8-base)  libgomp1{ab} (D: gcc-8-base)  libitm1{ab} (D: 
gcc-8-base)  libmpx2{ab} (D: gcc-8-base)
  libquadmath0{ab} (D: gcc-8-base)  libstdc++6{ab} (D: gcc-8-base)
1 packages upgraded, 3 newly installed, 0 to remove and 9 not upgraded.
Need to get 234 kB/2,662 kB of archives. After unpacking 11.5 MB will be used.
The following packages have unmet dependencies:
 libmpx2 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libitm1 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libcilkrts5 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libasan4 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libquadmath0 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libgcc1 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libubsan0 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libgnustep-base1.24 : Depends: gnustep-base-common (= 1.24.9-3.1) but it is 
not going to be installed
 libgomp1 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libatomic1 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libcc1-0 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
 libstdc++6 : Depends: gcc-8-base (= 8-20171016-1) but 8-20171023-1 is to be 
installed
open: 44; closed: 76; defer: 2; conflict: 5 
   oThe following actions will resolve 
these dependencies:

 Keep the following packages at their current version:
1) gcc-8-base [8-20171016-1 (now)]
2) libgnustep-base1.24 [Not Installed]
3) libobjc4 [Not Installed]
4) unar [Not Installed]



Accept this solution? [Y/n/q/?] n
open: 72; closed: 147; defer: 5; conflict: 9
   .The following actions will resolve 
these dependencies:

  Remove the following packages:
1)  g++ [4:7.2.0-1d1 (now, unstable)]
2)  g++-7 [7.2.0-11 (now, unstable)]
3)  gcc [4:7.2.0-1d1 (now, unstable)]
4)  gcc-7 [7.2.0-11 (now, unstable)]
5)  libasan4 [8-20171016-1 (now)]
6)  libgcc-7-dev [7.2.0-11 (now, unstable)]
7)  libstdc++-7-dev [7.2.0-11 (now, unstable)]
8)  libubsan0 [8-20171016-1 (now)]

  Keep the following packages at their current version:
9)  libgnustep-base1.24 [Not Installed]
10) unar [Not Installed]

  Upgrade the following packages:
11) libatomic1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
12) libcc1-0 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
13) libcilkrts5 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
14) libgcc1 [1:8-20171016-1 (now) -> 1:8-20171023-1 (experimental)]
15) libgomp1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
16) libitm1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
17) libmpx2 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
18) libquadmath0 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
19) libstdc++6 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages:
1)  g++ [4:7.2.0-1d1 (now, unstable)]
2)  g++-7 [7.2.0-11 (now, unstable)]
3)  gcc [4:7.2.0-1d1 (now, unstable)]
4)  gcc-7 [7.2.0-11 (now, unstable)]
5)  libasan4 [8-20171016-1 (now)]
6)  libgcc-7-dev [7.2.0-11 (now, unstable)]
7)  libmpx2 [8-20171016-1 (now)]
8)  libstdc++-7-dev [7.2.0-11 (now, unstable)]
9)  libubsan0 [8-20171016-1 (now)]

  Keep the following packages at their current version:
10) libgnustep-base1.24 [Not Installed]
11) unar [Not Installed]

  Upgrade the following packages:
12) libatomic1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
13) libcc1-0 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
14) libcilkrts5 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
15) libgcc1 [1:8-20171016-1 (now) -> 1:8-20171023-1 (experimental)]
16) libgomp1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
17) libitm1 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
18) libquadmath0 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]
19) libstdc++6 [8-20171016-1 (now) -> 8-20171023-1 (experimental)]



Accept t

Bug#879708: CVE-2017-12613 CVE-2017-12618

[Moritz Muehlenhoff]

On Tue, Oct 24, 2017 at 10:28:02PM +0200, Moritz Muehlenhoff wrote:
> Source: apr-util
> Severity: important
> Tags: security
> 
> I'm sure you're aware, but filing for completeness in the BTS anyway:
> http://mail-archives.apache.org/mod_mbox/apr-dev/201710.mbox/%3CCACsi252POs4toeJJciwg09_eu2cO3XFg%3DUqsPjXsfjDoeC3-UQ%40mail.gmail.com%3E
>  

Actually CVE-2017-12618 is in apr-util and CVE-2017-12613 in apr

I don't think any of those need a DSA, but let me know if you disagree.

Cheers,
Moritz

Bug#879708: CVE-2017-12613 CVE-2017-12618

[Moritz Muehlenhoff]

Source: apr-util
Severity: important
Tags: security

I'm sure you're aware, but filing for completeness in the BTS anyway:
http://mail-archives.apache.org/mod_mbox/apr-dev/201710.mbox/%3CCACsi252POs4toeJJciwg09_eu2cO3XFg%3DUqsPjXsfjDoeC3-UQ%40mail.gmail.com%3E
 

Cheers,
Moritz

Bug#879268: btrbk: Failed to parse subvolume list

[Nicholas D Steeves]

Hi Axel,

On Tue, Oct 24, 2017 at 09:02:58PM +0200, Axel Burri wrote:
> On 2017-10-24 18:32, Nicholas D Steeves wrote:
> > Dear Ritesh,
> > 
> > Would you please confirm that btrbk-0.26.0-1 (released yesterday) is
> > able to parse btrfs-progs (>= 4.13) subvolume list output?  I believe
> > you will find that "sudo btrbk list snapshots" now succeeds.
> > 
> > Thank you,
> > Nicholas
> > 
> I can confirm that btrbk-0.26.0 works with ALL versions of btrfs-progs
> >= 3.18.2, up to the latest version (4.13.3).
> 
> - Axel (the author of btrbk)
> 

Awesome!  Would you please close this bug so that 0.26.0-1 can migrate
to testing?  Also, would you please look at bug #878926 ?

Thank you,
Nicholas


signature.asc
Description: PGP signature

Bug#879707: nautilus-share: Wrong russian translation

[Mykola Driuchatyi]

Package: nautilus-share
Version: 0.7.3-2
Severity: minor

Dear Maintainer,

I found several spelling mistakes in russian translation:

1. When I open directory properties in Nautilus, Share tab has wrong spelling.
It contains "Общий до_ступ" instead of "Общий доступ".

2. When I click from context menu "Share" for some directory, window caption
contains HTML tags:
"Общий доступ к папке". I think they should be removed.



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

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

Versions of packages nautilus-share depends on:
ii  gnome-session-bin3.22.3-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.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  libnautilus-extension1a  3.22.3-1+deb9u1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  nautilus 3.22.3-1+deb9u1
ii  samba-common 2:4.5.12+dfsg-2
ii  samba-common-bin 2:4.5.12+dfsg-2

nautilus-share recommends no packages.

Versions of packages nautilus-share suggests:
ii  samba  2:4.5.12+dfsg-2

-- no debconf information

Bug#878271: Update ledmon to 0.80

[Jared.Dominguez]

Hi Anthony,

I will try to get to this this week. Can Canonical Taipei help validate? I 
currently don't have hardware to do so.

--
Jared Domínguez
OS Architect
Linux Engineering
Dell | Client Product Group

From: Anthony Wong [mailto:anthony.w...@canonical.com] 
Sent: Wednesday, October 11, 2017 5:47 PM
To: Debian Bug Tracking System 
Subject: Bug#878271: Update ledmon to 0.80

Package: ledmon
Version: 0.79-2+b2
X-Debbugs-CC: mailto:yc.ch...@canonical.com, mailto:mario.limoncie...@dell.com

Please update ledmon to 0.80, per Intel this version is required for RSTe.

https://qa.debian.org/cgi-bin/watch?pkg=ledmon
https://sourceforge.net/p/ledmon/code/ci/be5c7bf743b421a21be93791c40dd4ca91c87315/log/?path=
Thanks,
Anthony

Bug#614505: Patch for this feature request

[Emmanuel Bourg]

Le 24/10/2017 à 19:16, Thomas Goirand a écrit :

> Here's a patch adding Python 3 support to the package. This also patches
> antlr.py, and also packages the proper way, ie with a produced egg-info
> file as it should.
> 
> Please consider uploading this fix. This is needed, and would allow
> adding Python 3 support to 2 other packages which indirectly need this.
> 
> Alternatively, please allow me to NMU.

Thank you for the help Thomas. I can't see the patch attached, could you
send it again please?

A team upload would be preferable to a NMU. You are already a member of
the pkg-java group, so feel free to commit to the repository directly
and upload the update.

The repository has been migrated to Git today:

https://anonscm.debian.org/cgit/pkg-java/antlr.git

Bug#879667: [debhelper-devel] Bug#879667: Acknowledgement (Missing component in generated control file Section: line for dbgsym packages)

[Niels Thykier]

Control: tags -1 patch
Control: severity -1 serious

Hi Mihai,

Thanks for reporting the issue. :)

I have attached a patch that I hope you can test to see if it fixes your
problem.

Thanks,
~Niels

From bc86837c5c217e88d981103532083c270806e3b7 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Tue, 24 Oct 2017 16:33:15 +
Subject: [PATCH] Dh_Lib: Fix regression in parsing of the source section

Signed-off-by: Niels Thykier 
---
 debian/changelog   | 4 
 lib/Debian/Debhelper/Dh_Lib.pm | 5 +++--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c17641a1..06458425 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,10 @@ debhelper (10.10.4) UNRELEASED; urgency=medium
 called as otherwise ninja tries and fails to regenerate the
 build rules.  Thanks to Helmut Grohne for reporting the
 bug.  (Closes: #879658)
+  * Dh_Lib.pm: Fix regression where the source section would not
+be parsed leading to dbgsym packages possibly getting an
+incorrect value in the Section field.  Thanks to Mihai
+Moldovan for reporting the issue.  (Closes: #879667)
 
  -- Niels Thykier   Tue, 24 Oct 2017 05:45:09 +
 
diff --git a/lib/Debian/Debhelper/Dh_Lib.pm b/lib/Debian/Debhelper/Dh_Lib.pm
index 2ee29c1d..1fbcb101 100644
--- a/lib/Debian/Debhelper/Dh_Lib.pm
+++ b/lib/Debian/Debhelper/Dh_Lib.pm
@@ -1351,6 +1351,9 @@ sub getpackages {
 $rrr{$keyword} = 1;
 			}
 			next;
+		} elsif (/^Section:\s(.*)$/i) {
+			$source_section = $1;
+			next;
 		}
 		last if (!$_ or eof); # end of stanza.
 	}
@@ -1414,8 +1417,6 @@ sub getpackages {
 		push(@{$packages_by_type{'both'}}, $package);
 	}
 }
-			} elsif ($section and not defined($source_section)) {
-$source_section = $section;
 			}
 			$package='';
 			$package_type=undef;
-- 
2.14.2

Bug#879706: mikmod FTCBFS: --- ERROR: No suitable libmikmod library found.

[Helmut Grohne]

Source: mikmod
Version: 3.2.8-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

mikmod fails to build from source (natively):

| checking for libmikmod-config... /usr/bin/libmikmod-config
| checking for libmikmod - version >= 3.1.5... no
| *** Could not run libmikmod test program, checking why...
| *** The test program failed to compile or link. See the file config.log for 
the
| *** exact error that occured. This usually means libmikmod was incorrectly 
installed
| *** or that you have moved libmikmod since it was installed. In the latter 
case, you
| *** may want to edit the libmikmod-config script: /usr/bin/libmikmod-config
| configure: error: 
| --- ERROR: No suitable libmikmod library found.
|You need at least libmikmod 3.1.5 for this program to work.
| 
|   cd build && tail -v -n \+0 config.log
| ==> config.log <==
| ...
| configure:5165: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread 
-D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  -lmikmod 
-ldl -lSDL2 -lopenal -lpulse-simple -lpulse -lm >&5
| /usr/bin/ld: cannot find -lSDL2
| /usr/bin/ld: cannot find -lopenal
| /usr/bin/ld: cannot find -lpulse-simple
| /usr/bin/ld: cannot find -lpulse
| collect2: error: ld returned 1 exit status
| configure:5165: $? = 1
| configure: failed program was:
| ...
| configure: exit 1
| dh_auto_configure: cd build && ../configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-color-interface returned exit code 1
| debian/rules:6: recipe for target 'override_dh_auto_configure' failed
| make[1]: *** [override_dh_auto_configure] Error 2
| make[1]: Leaving directory '/<>'
| debian/rules:11: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

I guess it is related to the output of libmikmod-config --libs. It seems
that -lSDL2 was not always part of the output.

Helmut

Bug#879661: lintian: Fail to process ser-player due to invalid XML

[Chris Lamb]

tags 879661 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=463b6c4c642f11e3bde41aefb7d714cfffc315c6


Regards,

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

Bug#879705: remotehost/transporttunnel "fix" breaks remotehost/preauthtunnel

[martin f krafft]

Package: offlineimap
Version: 7.1.3+dfsg1-1
Severity: important

According to the changelog, the latest version introduced some
"fixes" relating to remotehost and transporttunnel.

Unfortunately, it broke setups with preauthtunnel, it seems:

  ERROR: No remote host for repository 'madduck.net' specified.

If I add a dummy

  remotehost = notrequired

then it works again. Seems like it should be an easy fix, but it
meant I saw no new mail for a day, which makes this bug a bit more
severe. Or well, actually, it was a great day. Don't fix it. ;)

-- 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_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages offlineimap depends on:
ii  python   2.7.14-1
ii  python-imaplib2  2.57-1
ii  python-six   1.11.0-1

Versions of packages offlineimap recommends:
pn  python-socks  

Versions of packages offlineimap suggests:
pn  python-kerberos  

-- no debconf information


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#879704: meson: nocheck build profile still requires rustc and c++-compiler-arm-linux-gnueabihf

[Daniel Schepler]

Source: meson
Version: 0.43.0-1
Severity: minor

Currently, if you build meson with the nocheck build profile, it still
requires rustc and c++-compiler-arm-linux-gnueabihf.  That looks like
a mistake, that the  was probably intended to apply to both
alternatives in e.g. "rustc | bash-doc " - but as written,
it only applies to bash-doc, so the effect is actually that in stage1
rustc is required (and bash-doc is not sufficient to satisfy the entry
as it is in a regular build).
-- 
Daniel

Bug#875927: perl: SIGUNUSED removal in glibc 2.26 changes PL_sig_name / SIG_SIZE

[Niko Tyni]

On Tue, Oct 24, 2017 at 03:34:10PM +0100, Dominic Hargreaves wrote:
> On Sun, Oct 22, 2017 at 08:57:59PM +0300, Niko Tyni wrote:

> > I'm tempted to just declare that anything relying on these parts of the
> > ABI is buggy and get the known affected modules/packages fixed.
> 
> This does seem like the correct approach, given that all the alternatives
> are going against upstream, and are varying levels of hackiness (and remain
> fragile).

Yes. This is all unfortunate of course. Relying on the SIG_SIZE constant
staying constant doesn't seem too unreasonable an assumption...

> Am I correct that implementing Tony's suggestion is in itself
> a complete fix for the issue?

I'm not sure which suggestion that is. Tony had some ideas about turning
SIG_SIZE into a variable rather than a constant on the Perl core side,
but noted that they would still break Async::Interrupt as it uses SIG_SIZE
in another place (see sig_async[] in Interrupt.xs, which would probably
need a change too.)

To reiterate a bit, there are two relevant C arrays, PL_sig_name[]
and PL_sig_num[]. Both are NULL terminated, but the "fragile" schmorp.h
s_signum() implementations bake in the array size at compile time and use
that to iterate the PL_sig_name[] array at run time rather than looking
for the terminating NULL. This breaks if the array size at run time is
different from the size at compile time.

Tony noted that they also have an unrelated bug: they do not use
PL_sig_num[] at all, but assume that the index in PL_sig_name[] is
equivalent to the signal number. This is a false assumption. There are
some signal names that map to the same number (for instance, on amd64
SIGIO == SIGPOLL == 29 and SIGSYS == SIGUNUSED == 31.)

OTOH Leon noted that making the implementations use the whichsig() /
whichsig_sv() Perl core API functions would solve the whole thing in a
cleaner way while avoiding the above bug.  So that seems the way to go
(but I don't have a patch ready, and I haven't looked at how the other
use of SIG_SIZE in Async::Interrupt could be avoided.)

> I'm adding debian-p...@lists.debian.org for wider visibility of this
> issue, which might include patching these four packages:

Thanks. I dropped the other cc's at this point.

> libasync-interrupt-perl, libio-aio-perl, libcoro-perl and libev-perl.

libio-aio-perl and libcoro-perl are probably not affected after all, given
they don't seem to use s_signum() or SIG_SIZE anywhere in the actual code.
-- 
Niko

Bug#877419: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

[Andreas Tille]

Hi Steve,

On Tue, Oct 24, 2017 at 10:44:53AM -0700, Steve Langasek wrote:
> 
> (https://launchpad.net/ubuntu/+source/pandas/0.19.2-5.1ubuntu4/+build/13337694)
> 
> This is not a problem with the Debian autobuilder.  Something is attempting
> an unaligned access, which is not portable on armhf.

Thanks for the hint.  Since there is the need to do another round of
test exclusion I'll exclude the test in question as well and we'll see
how far the build might go.  I'm absolutely unhappy with this "just
ignore the test" approach but I personally see no other chance to deal
with this and nobody else seems to care for a more sophisticated
approach (=volunteers more than welcome).

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#879703: gcc-7: static development libraries miss debug information

[Norbert Lange]

Package: gcc-7
Version: 7.2.0-11
Severity: wishlist

Dear Maintainer,

the static libraries, most importantly libstdc++, miss debug informations.
This is not ideal, and the debuginfo should be available for developers
by default. 

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

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

Versions of packages gcc-7 depends on:
ii  binutils  2.29.1-5
ii  cpp-7 7.2.0-11
ii  gcc-7-base7.2.0-11
ii  libc6 2.24-17
ii  libcc1-0  7.2.0-11
ii  libgcc-7-dev  7.2.0-11
ii  libgcc1   1:7.2.0-11
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-11
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6-dev  2.24-17

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
ii  gcc-7-multilib7.2.0-11
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
ii  libgcc1-dbg   1:7.2.0-11
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

Bug#879695: doxygen: Make source package bootstrappable

[Daniel Schepler]

On Tue, Oct 24, 2017 at 11:49 AM, Helmut Grohne  wrote:
> I've been bitten by pregenerated files more than once and dislike your
> sketched solution. At the same time I acknowledge that it may be
> unavoidable. [...]

I see what you mean: The choice would be whether or not to add code to
error out if the pregenerated files don't match what was actually
generated.  If you don't, you risk people forgetting to update the
files and therefore having the bootstrap build be broken.  If you do,
then you risk the normal package build breaking unnecessarily because
of some change in a newer version of yui-compressor or ruby-compass /
sass.

> The other major alternative is moving doxygen to Build-Depends-Indep and
> thus move the generated documentation to arch:all packages. This makes
> more sense conceptually as it would remove doxygen from the bootstrap
> set entirely, but results in more work and more binary packages.

I agree that would be the optimal solution.  Practically, though, as
you already hinted, I think there are probably enough packages in the
core bootstrap set that would need to be updated, that it might take a
while and having some interim measure in the meantime would be good.
(And if eventually we want Architecture: all packages also to be
bootstrappable from a minimal starting set, then there would be some
cases also requiring a "nodocs" build profile, so for example you
could build libasound2-data or libthai-data without needing to build
libasound2-doc or libthai-doc.  And this point would also be the
biggest issue I would have with the solution of moving the JS stuff
into separate files and a separate package: you would still need to
bootstrap the JS files somehow in this scenario, until all the source
packages that need to would provide a bootstrap build without doxygen
docs.)
-- 
Daniel

Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Jeremy Bicha]

Control: tags -1 pending

I am uploading a NMU now that is numbered as swt-gtk 3.8.2-4.1 to drop
the unnecessary build-depends since this is the last thing keeping
webkitgtk in Buster. I am uploading to DELAYED/2. Please let me know
if I should delay this fix any further. git patch attached.

Thanks,
Jeremy Bicha
From 89a84e10dd70b681cfa523462e5918850efbfde6 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Tue, 24 Oct 2017 15:25:30 -0400
Subject: [PATCH] Drop unnecessary Build-Depends on libwebkitgtk-dev Closes:
 #871964

---
 debian/changelog | 7 +++
 debian/control   | 1 -
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index b334072..7840165 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+swt-gtk (3.8.2-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unnecessary Build-Depends on libwebkitgtk-dev (Closes: #871964)
+
+ -- Jeremy Bicha   Tue, 24 Oct 2017 15:18:42 -0400
+
 swt-gtk (3.8.2-4) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/control b/debian/control
index 2dbbe38..f6a9f83 100644
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,6 @@ Build-Depends:
  libglib2.0-dev (>= 2.35),
  libglu1-mesa-dev | libglu-dev,
  libgnomeui-dev,
- libwebkitgtk-dev,
  libxcb-render-util0-dev,
  libxt-dev,
  libxtst-dev,
-- 
2.14.1

Bug#879702: stretch-pu: package python-tablib/0.9.11-2 (CVE-2017-2810)

[Thomas Goirand]

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

Hi,

The attached debdiff shows the fix for CVE-2017-2810. The package is
available here:

http://sid.gplhost.com/stretch-proposed-updates/python-tablib/

The security team thinks we should go for a stretch-pu. Please allow me
to upload the fix.

Should I upload the .changes including the orig file?

Cheers,

Thomas Goirand (zigo)
diff -Nru python-tablib-0.9.11/debian/changelog 
python-tablib-0.9.11/debian/changelog
--- python-tablib-0.9.11/debian/changelog   2013-05-12 14:21:10.0 
+0200
+++ python-tablib-0.9.11/debian/changelog   2017-10-24 21:15:19.0 
+0200
@@ -1,3 +1,9 @@
+python-tablib (0.9.11-2+deb9u1) stretch; urgency=low
+
+  * CVE-2017-2810: apply upstream patch: use safe load (Closes: #864818).
+
+ -- Thomas Goirand   Tue, 24 Oct 2017 21:15:19 +0200
+
 python-tablib (0.9.11-2) unstable; urgency=low
 
   * Uploading to unstable.
diff -Nru python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch 
python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch
--- python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch   
1970-01-01 01:00:00.0 +0100
+++ python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch   
2017-10-24 21:15:19.0 +0200
@@ -0,0 +1,17 @@
+Description: use safe load
+Author: Kenneth Reitz 
+Origin: 
https://github.com/kennethreitz/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e
+Bug-Debian: https://bugs.debian.org/864818
+Last-Update: 2017-10-24
+
+--- python-tablib-0.9.11.orig/tablib/formats/_yaml.py
 python-tablib-0.9.11/tablib/formats/_yaml.py
+@@ -46,7 +46,7 @@ def import_book(dbook, in_stream):
+ 
+ dbook.wipe()
+ 
+-for sheet in yaml.load(in_stream):
++for sheet in yaml.safe_load(in_stream):
+ data = tablib.Dataset()
+ data.title = sheet['title']
+ data.dict = sheet['data']
diff -Nru python-tablib-0.9.11/debian/patches/series 
python-tablib-0.9.11/debian/patches/series
--- python-tablib-0.9.11/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ python-tablib-0.9.11/debian/patches/series  2017-10-24 21:15:19.0 
+0200
@@ -0,0 +1 @@
+CVE-2017-2810-use_safe_load.patch

Bug#816872: wmbattery: memory leak in wmbattery

[David Johnson]

I've concluded libupower-glib is just super leaky.  The below patch
moves the upower API calls into a child process that doesn't exist for
long to keep the leaks out of the main process.

Tested against stretch versions, looks good.

--- wmbattery-2.50.orig/upower.c2015-08-30 19:58:13.0 -0400
+++ wmbattery-2.50/upower.c 2017-10-24 15:19:46.474102031 -0400
@@ -6,13 +6,15 @@
 #include 
 #include 
 #include 
+#include 
+#include 
+#include 
+#include 
 #include 
 #include "apm.h"
 
 #define MAX_RETRIES 3
 
-static UpClient * up;
-
 struct context {
int current;
int needed;
@@ -54,29 +56,11 @@
}
 }
 
-int upower_supported(void)
-{
-   up = up_client_new();
-
-   if (!up) {
-   return 0;
-   } else {
-   GPtrArray *devices = up_client_get_devices(up);
-
-   if (!devices) {
-   return 0;
-   } else {
-   g_ptr_array_unref(devices);
-   return 1;
-   }
-   }
-}
-
 /* Fill the passed apm_info struct. */
-int upower_read(int battery, apm_info *info)
+static int upower_read_child(int battery, apm_info *info)
 {
+   UpClient * up;
GPtrArray *devices = NULL;
-   static int retries = 0;
 
up = up_client_new();
 
@@ -90,15 +74,9 @@
 
devices = up_client_get_devices(up);
 
-   if (!devices) {
-   retries++;
-   if (retries < MAX_RETRIES)
-   return 0; /* fine immediately after hibernation */
-   else
-   return -1;
-   }
+   if (!devices)
+   return -1;
 
-   retries = 0;
info->battery_flags = 0;
info->using_minutes = 0;
 
@@ -143,6 +121,92 @@
info->battery_status = BATTERY_STATUS_ABSENT;
}
 
-   g_ptr_array_free(devices, TRUE);
+   g_ptr_array_unref(devices);
+   return 0;
+}
+
+static int upower_read_work(int battery, apm_info *info)
+{
+   int sp[2];
+   int child;
+   int status;
+   ssize_t cv;
+
+   if (socketpair(AF_UNIX, SOCK_DGRAM, 0, sp) < 0) {
+   fprintf(stderr, "socketpair: %s", strerror(errno));
+   goto fail;
+   }
+
+   child = fork();
+   if (child < 0) {
+   fprintf(stderr, "fork: %s", strerror(errno));
+   goto fail_close;
+   }
+
+   if (child == 0) {
+   /* child process does work, writes failure or result back to 
parent */
+   close(sp[0]);
+   status = upower_read_child(battery, info);
+   if (status < 0) {
+   cv = send(sp[1], &status, sizeof(status), 0);
+   }
+   else {
+   cv = send(sp[1], info, sizeof(*info), 0);
+   }
+   exit(cv < 0);
+   }
+   close(sp[1]);
+
+   child = waitpid(child, &status, 0);
+   if (child < 0) {
+   fprintf(stderr, "waitpid: %s status=%d", strerror(errno), 
status);
+   goto fail_close0;
+   }
+
+   cv = recv(sp[0], info, sizeof(*info), 0);
+   if (cv < 0) {
+   fprintf(stderr, "recv: %s", strerror(errno));
+   goto fail_close0;
+   }
+   else if (cv == sizeof(status)) {
+   memcpy(&status, info, sizeof(status));
+   goto fail_close0;
+   }
+   else if (cv != sizeof(*info)) {
+   fprintf(stderr, "recv: unexpected size %d", cv);
+   goto fail_close0;
+   }
+
+   close(sp[0]);
+   return 0;
+
+   fail_close:
+   close(sp[1]);
+   fail_close0:
+   close(sp[0]);
+   fail:
+   return -1;
+}
+
+int upower_supported(void)
+{
+   apm_info info;
+   return !(upower_read_work(1, &info) < 0);
+}
+
+
+int upower_read(int battery, apm_info *info)
+{
+   static int retries = 0;
+
+   if (upower_read_work(battery, info) < 0) {
+   retries++;
+   if (retries < MAX_RETRIES)
+   return 0; /* fine immediately after hibernation */
+   else
+   return -1;
+   }
+
+   retries = 0;
return 0;
 }

Bug#879701: ITP: node-mutate-fs -- Mutates the node.js file-system behavior for tests

[Akhil Varkey]

Package: wnpp
Severity: wishlist
Owner: Akhil Varkey 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name    : node-mutate-fs
  Version : 2.1.0
  Upstream Author : Isaac Z. Schlueter  (http://blog.izs.me/)
* URL : https://github.com/isaacs/mutate-fs#readme
* License : ISC
  Programming Lang: JavaScript  
  Description : Mutates the node.js file-system behavior for tests

 Node utility that mutates the node.js file-system behavior for tests to
be used in a
 test environment. 
 .
 Node.js is an event-based server-side JavaScript engine.
 
 This package is required to run build time tests for node-ignore-walk.

 I'd like to maintain this with the Javascript packaging team and
Praveen has agreed to sponsor this package.

Bug#879700: ITP: node-require-from-string -- Require module from string

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-require-from-string
  Version : 2.0.1
  Upstream Author : Vsevolod Strukchinsky 
(github.com/floatdrop)
* URL : https://github.com/floatdrop/require-from-string#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Require module from string

 This module can be used to avoid creating files for small modules and
instead,
 the content of the module can be passed as a string.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain for gitlab 9.5



signature.asc
Description: OpenPGP digital signature

Bug#879268: btrbk: Failed to parse subvolume list

[Axel Burri]

I can confirm that btrbk-0.26.0 works with ALL versions of btrfs-progs
>= 3.18.2, up to the latest version (4.13.3).

- Axel (the author of btrbk)

On 2017-10-24 18:32, Nicholas D Steeves wrote:
> Dear Ritesh,
> 
> Would you please confirm that btrbk-0.26.0-1 (released yesterday) is
> able to parse btrfs-progs (>= 4.13) subvolume list output?  I believe
> you will find that "sudo btrbk list snapshots" now succeeds.
> 
> Thank you,
> Nicholas
> 

Bug#879660: Pending fixes for bugs in the rabbitmq-java-client package

[pkg-java-maintainers]

tag 879660 + pending
thanks

Some bugs in the rabbitmq-java-client package are closed in revision
18551cc480ffde882430e67f9055fc2411f7ceeb in branch 'master' by
Christopher Hoskin

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/rabbitmq-java-client.git/commit/?id=18551cc

Commit message:

Initial release (Closes: #879660)

Bug#879697: RFS: opencsg/1.4.2-1 [RC]

[John Paul Adrian Glaubitz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Christian!

I'm going to sponsor this for you.

Is there any other package you need sponsoring for?

I think I forgot to reply to your previous RFS request, very sorry for
that. I have to take care of the OpenSCAD dependencies otherwise Torsten
gets mad at me :-).

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlnvjOQACgkQdCY7N/W1
+RNHAg//c3sy+jC7jy+Nl8yFmFjdwAQ+r31PJBYP7LqKUa11f6y8gfz8r5Qv+KSi
LCAPfMkj5cPMBcUcBoyQvfa7Ze9ZP8+dYfowF44T9sFY1DeefrRDdqDvm7pXbNYi
3KnMGLvz/IhzMGHCEhO0SKGqkqoYTQYC67je0MoAGaUV4dyz11kChf5ly1vkyiNY
vseEl4r28yLb4HIuZcyqiNI4h8Rhow8jT0+lVPyvaLE/BqOkgUta9Ir7Lq7A2L5V
T32uW27oRvCBz6i8uJPrd77GyfL26XzPoWXTQb4P7gXcXcLotLe9kXIVOiowyrNq
40ph1++vIA+6LaIRnqGy7TeksQqsRpM1wjXN95u52CmaZ/o0E0/4dDuoLFJFCH8u
0WNXMPX800kggo6WbSLdhLt0mj9zMjyEGuEN843/bUZsAhDFsOO3ezTNmLAOc5xX
+Nk+T8kufH8g/cyspkO2xVQ1KYj5S+gm5MhN8A7TWnQk3aLlLrh6IMHmkq6z3xqT
3Sd631/cuoDrKao09abjYwhQLPDqJ8/igfztxaRP/di1QwwcOAktpSjfPRI/TkBQ
D3a/RY9q5qty6eyADb609sXCbms3IWO0nRK/eHsePY5ibNbgba2755tI/D6HN1fX
29YMLDYItA+w7Y4LzRFUXKh2bo2oj1Hht4wme+zFSkR10ghQETc=
=+iW8
-END PGP SIGNATURE-

Bug#879698: slashtime: will not start with Wayland

[Markus Koschany]

Package: slashtime
Version: 0.5.13-1
Severity: normal

Slashtime won't start and throws an exception with Wayland. This is
probably a bug in libjava-gnome-java but maybe some adjustments in
slashtime are required as well.

Warning: ~/.tzlist not found. Using fallback Place list instead.
Exception in thread "main" org.gnome.glib.FatalError:
No mapping for GdkWaylandScreen (yet!)
at org.gnome.glib.Plumbing.lookupType(Plumbing.java:314)
at org.gnome.glib.Plumbing.objectFor(Plumbing.java:270)
at org.gnome.gtk.GtkWindow.getScreen(GtkWindow.java:633)
at org.gnome.gtk.Window.getScreen(Window.java:388)
at slashtime.ui.ZonesWindow.toggle(ZonesWindow.java:716)
at slashtime.ui.ZonesWindow.initialPresentation(ZonesWindow.java:684)
at slashtime.ui.ZonesWindow.(ZonesWindow.java:141)
at slashtime.ui.UserInterface.setupWindows(UserInterface.java:64)
at slashtime.ui.UserInterface.(UserInterface.java:59)
at slashtime.client.Master.main(Master.java:74)


-- 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/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#879697: RFS: opencsg/1.4.2-1 [RC]

[chrysn]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: opencsg
   Version : 1.4.2-1
   Upstream Author : Florian Kirsch (mail at opencsg dot org)
 * URL : http://opencsg.org/
 * License : GPL-2 with CGAL exception, and some ZLIB & similar
   Section : libs

The package provides the graphics library for the OpenSCAD programmatic
3D modelling tool. The library flips around the Z buffer so that CSG
(constructive solid geometry) compositions can be shown without
explicitly calculating their meshes.

It builds those binary packages:

libopencsg1
libopencsg-example - a small GLUT demo program whose practical
  importance in Debian is to answers the question of "is it a library or
  an OpenSCAD bug?"
libopencsg-dev
libopencsg1-dbg

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/opencsg/opencsg_1.4.2-1.dsc

For Sponsors who prefer to sponsor from git-buildpackage sources:

  git clone ssh://git.debian.org/git/collab-maint/opencsg.git

The package was built from 266c730b5c4b192be18d78bacc176961edfbe8f5.

Changes since the last upload:

  * New upstream version 1.4.2 (Closes: #861244)
  * Update copyright file
  * Drop old dependency names from squeeze or earlier
  * Modernize VCS-* and DEP URIs
  * Drop obsolete lintian override
  * Bump Standards-Version (no changes)

(up to here it has been sitting around for a while), and the RC bugfix:)

  * Make build dependency on rename explicit (Closes: #876676)

I'm aware that the Standards-Version is not the latest, but that would
better be fixed with other pending updates (eg. dbgsym migration), while
right now I'd like to get this through to resolve the FTBFS situation
with imminent testing removal.

Thanks for your consideration,
 chrysn


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

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

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#879695: doxygen: Make source package bootstrappable

[Helmut Grohne]

Hi Daniel,

On Tue, Oct 24, 2017 at 10:27:37AM -0700, Daniel Schepler wrote:
> Currently, doxygen's Build-Depends on yui-compressor creates build
> dependency cycles such as:

I no longer have a doxygen hat, but I was responsible for adding the
dependency, so I should likely answer.

> It would be nice if there were a way to bootstrap doxygen without
> needing Java.  For example, maybe the debian/ directory could contain
> pregenerated versions of the relevant files and then copy those into
> place in a stage1 build where the normal build would run
> yui-compressor and ruby-compass.

I've been bitten by pregenerated files more than once and dislike your
sketched solution. At the same time I acknowledge that it may be
unavoidable. Let me try to propose an alternatives nonetheless:

If the javascript stuff was somehow moved to an arch:all package, then
yui-compressor could be demoted to Build-Depends-Indep. The reason why
it is not currently there is that /usr/bin/doxygen embeds the compressed
javascript. So unembedding it and loading it from actual files would
make doxygen less self-contained, but it would also enable building a
libjs-doxygen package containing the js blobs for (potentially) multiple
releases such that documentation packages could symlink those files
rather than copy them. Bastien Roucaries attempted to implement that
unembedding but never finished that work.

The other major alternative is moving doxygen to Build-Depends-Indep and
thus move the generated documentation to arch:all packages. This makes
more sense conceptually as it would remove doxygen from the bootstrap
set entirely, but results in more work and more binary packages.

Did you try either of these already?

Helmut

Bug#879642: simple-cdd: build-simple-cdd fails with unsigned local repository

[Austin Roach]

Austin Roach  wrote:
> Currently, this fails on sid because of an unsigned local repository (logfile
> attached).

One note on that logfile: I added a 'printenv' to tmp/debian-cd/Makefile before
the first 'apt-get update' call to help myself in debugging, and
forgot to re-run
without it before submitting the log. So this log has a dump of environment
variables that you wouldn't expect to see in the standard log.

> apt [...] now issues an error instead of a warning for insecure repositories.

To add a little more detail, here is a snippet of the logfile from
'build-simple-cdd' executed on a machine running stretch, during the first
apt-get update executed by tmp/debian-cd/Makefile:

[...]
2017-10-21 07:33:20,578 DEBUG build/debian-cd stdout: # Updating the
apt database
2017-10-21 07:33:20,610 DEBUG build/debian-cd stdout: Get:1
file:/home/testuser/scdd/tmp/mirror stretch InRelease
2017-10-21 07:33:20,610 DEBUG build/debian-cd stdout: Ign:1
file:/home/testuser/scdd/tmp/mirror stretch InRelease
2017-10-21 07:33:20,611 DEBUG build/debian-cd stdout: Get:2
file:/home/testuser/scdd/tmp/mirror stretch Release [1,482 B]
2017-10-21 07:33:20,621 DEBUG build/debian-cd stdout: Get:2
file:/home/testuser/scdd/tmp/mirror stretch Release [1,482 B]
2017-10-21 07:33:20,626 DEBUG build/debian-cd stdout: Get:3
file:/home/testuser/scdd/tmp/mirror stretch Release.gpg
2017-10-21 07:33:20,626 DEBUG build/debian-cd stdout: Ign:3
file:/home/testuser/scdd/tmp/mirror stretch Release.gpg
2017-10-21 07:33:20,629 DEBUG build/debian-cd stdout: Get:4
file:/home/testuser/scdd/tmp/mirror stretch/main amd64 Packages [129
kB]
2017-10-21 07:33:20,644 DEBUG build/debian-cd stdout: Get:5
file:/home/testuser/scdd/tmp/mirror stretch/main/debian-installer
amd64 Packages [79.8 kB]
2017-10-21 07:33:20,697 DEBUG build/debian-cd stdout: Reading package lists...
2017-10-21 07:33:20,704 DEBUG build/debian-cd stderr: W: The
repository 'file:/home/testuser/scdd/tmp/mirror stretch Release' is
not signed.
[...]

Contrast this with the equivalent logfile from a machine running sid:

[...]
2017-10-23 14:28:59,005 DEBUG build/debian-cd stdout: # Updating the
apt database
2017-10-23 14:28:59,077 DEBUG build/debian-cd stdout: Get:1
file:/home/testuser/scdd/tmp/mirror sid InRelease
2017-10-23 14:28:59,078 DEBUG build/debian-cd stdout: Ign:1
file:/home/testuser/scdd/tmp/mirror sid InRelease
2017-10-23 14:28:59,078 DEBUG build/debian-cd stdout: Get:2
file:/home/testuser/scdd/tmp/mirror sid Release [1,474 B]
2017-10-23 14:28:59,097 DEBUG build/debian-cd stdout: Get:2
file:/home/testuser/scdd/tmp/mirror sid Release [1,474 B]
2017-10-23 14:28:59,099 DEBUG build/debian-cd stdout: Get:3
file:/home/testuser/scdd/tmp/mirror sid Release.gpg
2017-10-23 14:28:59,099 DEBUG build/debian-cd stdout: Ign:3
file:/home/testuser/scdd/tmp/mirror sid Release.gpg
2017-10-23 14:28:59,143 DEBUG build/debian-cd stdout: Reading package lists...
2017-10-23 14:28:59,143 DEBUG build/debian-cd stderr: E: The
repository 'file:/home/testuser/scdd/tmp/mirror sid Release' is not
signed.
[...]

On stretch, debian-cd successfully fetches the package lists from the local
repo and stores them in tmp/cd-build/apt/$THIS_PKGSET/apt-state/lists/. On
sid, the error prevents the package lists from being retrieved. You can observe
the difference in behavior of apt-get directly by running the update command
with the arguments as specified in tmp/debian-cd/tools/apt-selection:

apt-get -q -o Dir::State::status=$APTTMP/$THIS_PKGSET/status \
-o Dir::State=$APTTMP/$THIS_PKGSET/apt-state/ \
-o Dir::Cache=$APTTMP/$THIS_PKGSET/apt-cache/ \
-o Dir::Etc=$APTTMP/$THIS_PKGSET/apt/ \
-o APT::Cache::AllVersions=0 \
-o APT::Cache::ShowVersion=1 \
-o APT::Architecture=$ARCH \
-o APT::Architectures::=$ARCH \
-o Acquire::Languages=none \
update

Cheers,
Austin

Bug#879696: RFS: xerces-c/3.2.0+debian-1

[Bill Blough]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor and/or someone to grant upload permissions 
  (I am a DM) for my package "xerces-c"

  NOTE:  Due to the SONAME change, this will require a transition.  Therefore
  this this package should be uploaded to experimental rather than unstable.


 * Package name: xerces-c
   Version : 3.2.0+debian-1
   Upstream Author : Apache Xerces Team
 * URL : https://xerces.apache.org/xerces-c/
 * License : Apache 2.0
   Section : libs

  It builds those binary packages:

libxerces-c-dev - validating XML parser library for C++ (development files)
libxerces-c-doc - validating XML parser library for C++ (documentation)
libxerces-c-samples - validating XML parser library for C++ (compiled 
samples)
libxerces-c3.2 - validating XML parser library for C++

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

  https://mentors.debian.net/package/xerces-c


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

dget -x 
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.2.0+debian-1.dsc

  More information about xerces-c can be obtained from  
https://xerces.apache.org/xerces-c/

  Changes since the last upload:

  * New upstream version
  * Update to policy 4.1.1
- Change d/copyright Format URL to use https
  * Remove patches that have been applied upstream
  * Set dh compat to 10
  * Patch: Fix test failures for parallel builds (forwarded)

  Regards,
   Bill Blough


signature.asc
Description: PGP signature

Bug#772812:

[Nikola Kovacs]

The upstream bug (https://community.openvpn.net/openvpn/ticket/538) is not
fixed, and I can still reproduce this on Ubuntu 17.10 with openvpn 2.4.3.

Bug#879264: cannot enter the desktop environment

[Luca Boccassi]

On Tue, 2017-10-24 at 15:23 +0200, Andreas Beckmann wrote:
> On 10/23/2017 10:16 PM, Luca Boccassi wrote:
> > > Am 21.10.2017 um 12:10 schrieb Lu Wang:
> > > > Oct 21 16:58:56 lenovo /usr/lib/gdm3/gdm-x-session[16569]:
> > > > Couldn't
> > 
> > open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined
> > symbol: _glapi_tls_Current
> > Shall we remove the provides? It looks like, for whatever reasons,
> > not
> 
> or lower the provided version ?

I thought virtual packages were unversioned? How could we do it?

> > all the symbols are exported by nvidia. Perhaps the bundled glvnd
> > libraries are too old?
> > 
> > libGLdispatch.so.0 in libglvnd0 exports that symbol.
> 
> Do we have missing symbols in other packages mirroring libglvnd?
> 
> 
> Andreas

It's the only one in libglvnd0 - it's missing even in the very latest
387.xx release which is strange.

libegl1-glvnd-nvidia is missing eglCreatePlatformPixmapSurfaceEXT@ and 
eglCreatePlatformWindowSurfaceEXT

libglx0-glvnd-nvidia is missing __GLXGL_CORE_FUNCTIONS

Curiously libgl1-glvnd-nvidia-glx has more symbols than libgl1:

+AllocExecPages@Base
+FindNextStringToken@Base
+FreeExecPages@Base
+IntersectionExtensionStrings@Base
+IsTokenInString@Base
+SplitString@Base
+UnionExtensionStrings@Base
+__glXWrapperInit@Base
+entry_generate_default_code@Base
+entry_get_patch_addresses@Base
+entry_get_public@Base
+entry_init_public@Base
+entry_patch_finish@Base
+entry_patch_start@Base
+entry_stub_size@Base
+entry_type@Base
+glvnd_asprintf@Base
+glvnd_byte_swap16@Base
+glvnd_vasprintf@Base
+stub_find_public@Base
+stub_get_addr@Base
+stub_get_patch_callbacks@Base
+stub_get_slot@Base

Kind regards,
Luca Boccassi

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

Bug#810145: Pbuilder and /run/shm

[Dirk Eddelbuettel]

Any news on that /run/shm issue for pbuilder?  It is currently blocking me
from building packages as I can't upgrade my pbuilder tarball (as easily at
least).

I tried Jo's "proof of concept" patch, but no luck either.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#799270: Pending fixes for bugs in the java-wrappers package

[pkg-java-maintainers]

tag 799270 + pending
thanks

Some bugs in the java-wrappers package are closed in revision
63b338f95a8b71a9063f6609207adea155992384 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java-wrappers.git/commit/?id=63b338f

Commit message:

Support the JVMs installed by the webupd8 installer (Closes: #799270)

Bug#834552: Pending fixes for bugs in the java-wrappers package

[pkg-java-maintainers]

tag 834552 + pending
thanks

Some bugs in the java-wrappers package are closed in revision
a36d81303b35723c5a3cb39754b1fbc927d7bdd6 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java-wrappers.git/commit/?id=a36d813

Commit message:

Added OpenJDK 8 as an alternative alias for openjdk (Closes: #834552)

Bug#855346: thunderbird: Can't open attachments with AppArmor profile enforced

[Vincas Dargis]

Patch snippet:

+  # Allow opening attachments
+  /{usr/,}bin/* Cx -> sanitized_helper,
+  /{usr/,}sbin/* Cx -> sanitized_helper,
+  /usr/local/{bin,sbin}/* Cx -> sanitized_helper,
+  /usr/lib/libreoffice/program/soffice Cxr -> sanitized_helper,
+  /usr/bin/evince Pix,
+  /usr/bin/totem Pix,

Do we really need sbin? I kind doubt there will be "document viewers", and it has setuid applications like pppd and 
exim4, which is not comforting.


Also, if sanitized_helper contains:

`/{usr/,}bin/* Pixr,`

Doesn't this automatically mean that this line in usr.bin.thunderbird profile

`/{usr/,}bin/* Cx -> sanitized_helper,`

will in result launch /usr/bin/totem with it's *P*rofile?

I wonder, because `abstractions/ubuntu-media-players has `/usr/bin/totem Cxr -> 
sanitized_helper,`, maybe that would work?

I'll do some testing tomorrow. If there's extra rules for XFCE, maybe I should 
try Thunderbird on several DE.

Bug#873245: Pending fixes for bugs in the yecht package

[pkg-java-maintainers]

tag 873245 + pending
thanks

Some bugs in the yecht package are closed in revision
83c1aa762e4a78acb89c52be2541ee247d17f287 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/yecht.git/commit/?id=83c1aa7

Commit message:

Add yecht-java9.patch and fix FTBFS with Java 9.

Thanks: Chris West for the report and patch.
Closes: #873245

Bug#848833: dh-make: change default debhelper compat level to 10

[Jack Bates]

On Tue, 20 Dec 2016 10:58:47 +0800 Paul Wise  wrote:

Package: dh-make
Severity: wishlist

Please change the default debhelper compat level to 10. This has a
number of changes but important one is parallel building by default.


+1

Bug#877419: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

[Steve Langasek]

On Tue, Oct 24, 2017 at 02:15:15PM +0200, Andreas Tille wrote:
> Hi,

> I made some progress with excluding some tests on some architectures.  The
> last target I was trying to tackle was s390x which builds now.  Not all
> architectures have finished [1] currently but armhf has now failed with

> ...
> ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_pytables.py::TestHDFStore::test_append_all_nans
>  PASSED
> ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_pytables.py::TestHDFStore::test_append_frame_column_oriented
>  Bus error
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"

> debian/rules:112: recipe for target 'python-test2.7' failed
>   after 15 requests (13 known processed) with 0 events remaining.

> make[1]: *** [python-test2.7] Error 135

> (see build log[2]).  My suspicion is that this is not really an error in
> the test suite but some problem with the autobuilder?  Could somebody
> please have a look?  If not the only chance I see is to deactivate armhf
> for pandas.

test_api_default_format (pandas.io.tests.test_pytables.TestHDFStore) ... ok
test_append (pandas.io.tests.test_pytables.TestHDFStore) ... ok
test_append_all_nans (pandas.io.tests.test_pytables.TestHDFStore) ... Bus error 
(core dumped)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"
  after 15 requests (13 known processed) with 0 events remaining.
debian/rules:114: recipe for target 'python-test2.7' failed
make[1]: *** [python-test2.7] Error 135

(https://launchpad.net/ubuntu/+source/pandas/0.19.2-5.1ubuntu4/+build/13337694)

This is not a problem with the Debian autobuilder.  Something is attempting
an unaligned access, which is not portable on armhf.  Historically, the
Linux armhf kernel would fix up these unaligned accesses by default; but
Android kernel builds, for example, would not, and Linux arm64 kernels also
do not, and while we could enforce that Debian kernels fix up unaligned
access on armhf, the reason they don't all do this is that the fixups are
expensive and it's better to fix the code.

(I am somewhat surprised to see that this particular package build is an
armhf build on an "armel" host; but I'm not sure that's material here.)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#878771: golang-github-spf13-cobra FTBFS on mips: error: redefinition of 'AF_ALG'

[Anthony Fok]

Hi Adrian and Shengjing,

On Mon, Oct 16, 2017 at 10:25 AM, Shengjing Zhu  wrote:
> Control: reassign -1 golang-golang-x-sys
>
> On Mon, Oct 16, 2017 at 11:26 PM, Adrian Bunk  wrote:
>> Source: golang-github-spf13-cobra
>> Version: 0.0~git20170731.0.b26b538-1
>> Severity: serious
>>
>> https://buildd.debian.org/status/fetch.php?pkg=golang-github-spf13-cobra&arch=mips&ver=0.0~git20170731.0.b26b538-2&stamp=1508109561&raw=0
>>
>> ...
>> src/golang.org/x/sys/unix/zerrors_linux_mips_mipso32.go:15:2: error: 
>> redefinition of 'AF_ALG'
>>   AF_ALG   = 0x26
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips.go:14:2: note: previous 
>> definition of 'AF_ALG' was here
>>   AF_ALG   = 0x26
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips_mipso32.go:16:2: error: 
>> redefinition of 'AF_APPLETALK'
>>   AF_APPLETALK = 0x5
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips.go:15:2: note: previous 
>> definition of 'AF_APPLETALK' was here
>>   AF_APPLETALK = 0x5
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips_mipso32.go:17:2: error: 
>> redefinition of 'AF_ASH'
>>   AF_ASH   = 0x12
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips.go:16:2: note: previous 
>> definition of 'AF_ASH' was here
>>   AF_ASH   = 0x12
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips_mipso32.go:18:2: error: 
>> redefinition of 'AF_ATMPVC'
>>   AF_ATMPVC= 0x8
>>   ^
>> src/golang.org/x/sys/unix/zerrors_linux_mips.go:17:2: note: previous 
>> definition of 'AF_ATMPVC' was here
>>   AF_ATMPVC= 0x8
>>   ^
>> ...
>>
>> I've reproduced the FTBFS with 0.0~git20170731.0.b26b538-1,
>> so that's likely triggered by some change elsewhere (gccgo 7?).
>
> It should be caused by gcc-7 7.2.0-10 which fixed #876639
> We need to revert the commits in golang/x/sys package,
> https://anonscm.debian.org/cgit/pkg-go/packages/golang-golang-x-sys.git/commit/?id=bb8f8e16490ce03ce084c8e170ea4c9e79f53ba2

Thank you for bringing this issue to my attention, and sorry for my absence.
I'll get this fixed right away.

Shengjing, thank you for pointing out the solution, otherwise I would
be at a lost too,
and thank you for filing #876639 etc. to have the proper fix
backported into gccgo-7 upstream.

Cheers,
Anthony

Bug#548501: apt: undocumented feature: autoremove works like remove --autoremove

[Axel Beckert]

Control: found -1 1.6~alpha1

Dear APT Developers,

Vincenzo Tibullo wrote 8 years ago:
> apt-get man page says autoremove does not want any package parameter, 
> but passing one or more packages as parameter it works the same way as
> 
> apt-get --autoremove remove pkgs
> 
> This useful feature is undocumented, please document it.

Ping! This is still the case.

I just wanted to explain a coworker that "apt-get autoremove" doesn't
take any parameter, but it indeed does. And until I found this bug
report it was not clear to me what "apt-get automremove "
really does.

So please document optional parameters for "apt-get automremove" (and
"apt autoremove").

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

Bug#879695: doxygen: Make source package bootstrappable

[Daniel Schepler]

Source: doxygen
Version: 1.8.13-9
Severity: wishlist

Currently, doxygen's Build-Depends on yui-compressor creates build
dependency cycles such as:

yui-compressor Depends on default-jre-headless
default-jre-headless Depends on openjdk-8-jre-headless
openjdk-8 Build-Depends on cups
cups Build-Depends on dh-apparmor
apparmor Build-Depends on apache2-dev
apache2 Build-Depends on libapr1-dev
apr Build-Depends on doxygen

It would be nice if there were a way to bootstrap doxygen without
needing Java.  For example, maybe the debian/ directory could contain
pregenerated versions of the relevant files and then copy those into
place in a stage1 build where the normal build would run
yui-compressor and ruby-compass.
-- 
Daniel

Bug#614505: Patch for this feature request

[Thomas Goirand]

Hi,

Here's a patch adding Python 3 support to the package. This also patches
antlr.py, and also packages the proper way, ie with a produced egg-info
file as it should.

Please consider uploading this fix. This is needed, and would allow
adding Python 3 support to 2 other packages which indirectly need this.

Alternatively, please allow me to NMU.

Cheers,

Thomas Goirand (zigo)