Bug#892711: python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/python-pymodbus/examples/common/README.rst

[Andreas Beckmann]

Package: python-pymodbus-doc
Version: 1.4.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package python-pymodbus-doc.
  Preparing to unpack .../6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb ...
  Unpacking python-pymodbus-doc (1.4.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/python-pymodbus/examples/common/README.rst', which is also in 
package python-pymodbus 1.2.0+git20151013-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb


cheers,

Andreas


python-pymodbus=1.2.0+git20151013-1_python-pymodbus-doc=1.4.0+dfsg-1.log.gz
Description: application/gzip

Bug#892709: libgtk2-imageview-perl: Remove libgtk2-imageview-perl during the Buster cycle

[Jeremy Bicha]

Source: libgtk2-imageview-perl
Version: 0.05-2
Severity: serious
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Tags: sid buster
Control: blocked -1 by 870418

Since shutter is the only reverse depends for libgtk2-imageview-perl
and shutter is being removed from Testing (it needs to be ported to
maintained libraries like gtk3 and GObject Introspection), I think we
might as well remove this package from Testing too.

Thanks,
Jeremy Bicha

Bug#892710: {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}

[Andreas Beckmann]

Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip

Bug#892708: kicad-demos: missing Breaks+Replaces: kicad-common (<< 5)

[Andreas Beckmann]

Package: kicad-demos
Version: 5.0.0~rc1+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package kicad-demos.
  Preparing to unpack .../kicad-demos_5.0.0~rc1+dfsg1-1_all.deb ...
  Unpacking kicad-demos (5.0.0~rc1+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', 
which is also in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-demos=5.0.0~rc1+dfsg1-1.log.gz
Description: application/gzip

Bug#698032: gkdebconf: raising severity of gconf dependency bug

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we are working to remove gconf from Debian. As part
of this process, I am now raising the severity of this bug.

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#892707: ufraw: Depends on gconf

[Jeremy Bicha]

Source: ufraw
Version: 0.22-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html
https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#886072: gnome-xcf-thumbnailer: raising severity of gconf dependency bug

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we are working to remove gconf from Debian. As part
of this process, I am now raising the severity of this bug.

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#886044: syncmaildir: raising severity of gconf dependency bug

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we are working to remove gconf from Debian. As part
of this process, I am now raising the severity of this bug.

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#892706: guake-indicator: Depends on gconf

[Jeremy Bicha]

Source: guake-indicator
Version: 1.1-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html
https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#375500: xchat: raising severity of gconf dependency bug

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we are working to remove gconf from Debian. As part
of this process, I am now raising the severity of this bug.

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#892705: ITP: golang-github-aead-chacha20 -- ChaCha20 and XChaCha20 stream ciphers

[Eric Dorland]

Package: wnpp
Severity: wishlist
Owner: Eric Dorland 

* Package name: golang-github-aead-chacha20
  Version : 0.0~git20180214.c8d2937-1
  Upstream Author : Andreas Auernhammer
* URL : https://github.com/aead/chacha20
* License : MIT
  Programming Lang: Go
  Description : ChaCha20 and XChaCha20 stream ciphers go library

 The ChaCha20 stream cipher ChaCha is a stream cipher family
 created by Daniel J. Bernstein.  The most common ChaCha cipher
 is ChaCha20 (20 rounds). ChaCha20 is standardized in RFC 7539
 (https://tools.ietf.org/html/rfc7539).
 .
 This package provides implementations of three ChaCha versions: -
 ChaCha20 with a 64 bit nonce (can en/decrypt up to 2^64 * 64 bytes
 for one key-nonce combination) - ChaCha20 with a 96 bit nonce (can
 en/decrypt up to 2^32 * 64 bytes ~ 256 GB for one key-nonce combination)
 - XChaCha20 with a 192 bit nonce (can en/decrypt up to 2^64 * 64 bytes
 for one key-nonce combination)
 

Bug#892704: ITP: golang-github-aead-poly1305 -- The poly1305 message authentication code

[Eric Dorland]

Package: wnpp
Severity: wishlist
Owner: Eric Dorland 

* Package name: golang-github-aead-poly1305
  Version : 0.0~git20170715.6cf43fd-1
  Upstream Author : Andreas Auernhammer
* URL : https://github.com/aead/poly1305
* License : MIT
  Programming Lang: Go
  Description : The poly1305 message authentication code

 Poly1305 is a fast, one-time authentication function created by 
 Daniel J. Bernstein.  It is infeasible for an attacker to generate
 an authenticator for a message without the key.  However, a key must
 only be used for a single message. Authenticating two different
 messages with the same key allows an attacker to forge authenticators
 for other messages with the same key.

Bug#892703: nmu: uriparser_0.8.4-1 on mips and mipsel

[YunQiang Su]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

For mips and mipsel, we are working on FPXX migration, and this package
seems quite old,
So the rebuilding is needed to use the current default gcc options.

-- 
YunQiang Su

Bug#892153: Objective-C libraries (was: Bug#892153: marked as done (RFS: addresses-for-gnustep/0.4.8-3 [RC]))

[Paul Wise]

On Mon, Mar 12, 2018 at 2:02 AM, Yavor Doganov wrote:

> If -initWithAddressBook:readOnly: is removed in a new version of the
> library, that's an API/ABI break but again, it won't be reflected in
> the symbols table.  In a C/C++ library you'll see a symbol
> disappearing but it won't happen here.  So even the secondary reason
> for using symbols files (detecting ABI breaks, although that's really
> a weak test) is not applicable.

Is there some public indicator of the actual symbols changes? It
sounds like Debian's core dependencies infrastructure needs to be
extended to understand Objective C ABIs.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#892417: RFS: streamlink/0.11.0+dfsg-1

[Paul Wise]

On Mon, Mar 12, 2018 at 1:31 AM, Alexis Murzeau wrote:

> Shouldn't not so much used packages preferably not be backported (to
> avoid maintenance costs to other involved parties) ?

The backports policy says "Please only upload package with a notable
userbase. User request for the package may be an indicator.", but I
guess this package qualifies based on the popcon information for
streamlink and livestreamer:

https://backports.debian.org/Contribute/
https://qa.debian.org/popcon.php?package=streamlink
https://qa.debian.org/popcon.php?package=livestreamer

> Also, why should backports be uploaded after the unstable package enter
> testing ?
> To ensure there is a clean upgrade path from stable / stable-backport to
> testing ?

The backports policy says "To guarantee an upgrade path from
stable+backports to the next stable, the package should be in
testing."

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#884940: goldencheetah: diff for NMU version 1:3.5~DEV1710-1.2

[Satoru KURASHIKI]

hi,

On Sun, Mar 11, 2018 at 1:27 AM, Sebastian Ramacher
 wrote:
> Control: tags 884940 + patch
> Control: tags 884940 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for goldencheetah (versioned as 1:3.5~DEV1710-1.2) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
>
> Cheers
> --
> Sebastian Ramacher

Thank you for your work.

I'm also preparing this fix at salsa.d.o, but being blocked by
building new upstream.
I will rewind commits after I can make time.

regards,
-- 
KURASHIKI Satoru

Bug#861141: enchant: New upstream release (2.1.0)

[Tim Lunn]

Since version 2.1.3 enchant 2 has support for parallel installation.

Given the API/ABI breaks it would probably be best to package this as a 
separate enchant2 source package



NEWS:

2.1.3 (November 26, 2017)
--

This release adds support for parallel installation with other major
versions of Enchant, and fixes a crash in the Voikko provider when it has no
supported languages.

Bug#892702: cloudkitty: Fails to build, syntax error in po/it.po

[Jeremy Bicha]

Source: cloudkitty
Version: 7.0.0-3
Severity: serious

cloudkitty fails to build from source in a clean unstable chroot. This
is a regression from 7.0.0-2.

There's a build log at
https://launchpad.net/ubuntu/+source/cloudkitty/7.0.0-3/+build/14443658

build log excerpt
=
Merging it.po...
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:22:1: syntax error
msgmerge: found 19 fatal errors

Other Info

I guess this might actually be the fault of today's
openstack-pkg-tools 71 with "Updated Italian debconf translation".
Feel free to reassign and fix. :)


Thanks,
Jeremy Bicha

Bug#892597: depends-on-build-essential-package-without-using-version not emited when alternative deps are defined

[Chris Lamb]

tags 892597 + pending
thanks

Hi Sven and Luarent,

Thanks for your input. I've gone ahead and renamed the tag and updated the
description to match:

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

:)


Regards,

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

Bug#892700: metview: FTBFS, probably missing B-D: libfftw3-dev

[Andreas Beckmann]

Source: metview
Version: 5.0.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

metview/experimental FTFBS:
https://buildd.debian.org/status/package.php?p=metview=experimental

make[3]: *** No rule to make target '/usr/lib/aarch64-linux-gnu/libfftw3.so', 
needed by 'lib/libMvMars.so.0.0.0'.  Stop.

This is probably a missing Build-Depends: libfftw3-dev


Andreas

Bug#880842: gnome-twitch FTBFS with meson 0.43.0: "descritpion"

[Jeremy Bicha]

Control: forwarded -1 https://github.com/vinszent/gnome-twitch/commit/6bee8bc0
Control: tags -1 fixed-upstream patch

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

[Michael Biebl]

Control: retitle -1 Switch from network-manager-dev to libnm-dev

Hi Ari

Am 11.03.2018 um 22:16 schrieb Ari Pollak:
> On Sun, Mar 11, 2018 at 5:15 PM Ari Pollak  > wrote:
> 
> On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl  > wrote:
> 
> By that I mean: If you don't have a runtime requirement, do you
> only use
> the D-Bus API? If so, why is network-manager-dev required as build
> dependency at all?
> 
> 
> Right, it's just using the D-Bus API during runtime, but still uses
> the headers during compilation for state constants.
> 
> 
> Oops, meant to include a link too:
> https://anonscm.debian.org/cgit/collab-maint/pidgin.git/tree/libpurple/network.c

Thanks for the additional information. Seems I mistitled the bug report,
so fixing that. As I didn't see a runtime dependency on either
libnm-glib or libnm-util, I wrongly concluded, that network-manager-dev
was a left-over build depdendency.

So, back to the issue:

The successor of libnm-glib/libnm-util is libnm.

If you are only interested in NM state constants, you should be able to
simply use NetworkManager.h which is also provided by libnm-dev.
While the APIs of libnm and libnm-glib/libnm-util are not completely the
same, I think in your case it might be sufficiently compatible:

> michael@pluto:~$ grep NM_STATE /usr/include/libnm/*
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_UNKNOWN: Networking state 
> is unknown. This indicates a daemon error
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_ASLEEP: Networking is not 
> enabled, the system is being suspended or
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_DISCONNECTED: There is no 
> active network connection.
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_DISCONNECTING: Network 
> connections are being cleaned up.
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_CONNECTING: A network 
> connection is being started
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_CONNECTED_LOCAL: There is 
> only local IPv4 and/or IPv6 connectivity,
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_CONNECTED_SITE: There is 
> only site-wide IPv4 and/or IPv6 connectivity.
> /usr/include/libnm/nm-dbus-interface.h: * @NM_STATE_CONNECTED_GLOBAL: There 
> is global IPv4 and/or IPv6 Internet connectivity
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_UNKNOWN  = 0,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_ASLEEP   = 10,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_DISCONNECTED = 20,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_DISCONNECTING= 30,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_CONNECTING   = 40,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_CONNECTED_LOCAL  = 50,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_CONNECTED_SITE   = 60,
> /usr/include/libnm/nm-dbus-interface.h:   NM_STATE_CONNECTED_GLOBAL = 70,

nm-dbus-interface.h is included by /usr/include/libnm/NetworkManager.h

> michael@pluto:~$ grep NM_STATE /usr/include/NetworkManager/*
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_UNKNOWN: networking 
> state is unknown
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_ASLEEP: networking 
> is not enabled
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_DISCONNECTED: there 
> is no active network connection
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_DISCONNECTING: 
> network connections are being cleaned up
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_CONNECTING: a 
> network connection is being started
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_CONNECTED_LOCAL: 
> there is only local IPv4 and/or IPv6 connectivity
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_CONNECTED_SITE: 
> there is only site-wide IPv4 and/or IPv6 connectivity
> /usr/include/NetworkManager/NetworkManager.h: * @NM_STATE_CONNECTED_GLOBAL: 
> there is global IPv4 and/or IPv6 Internet connectivity
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_UNKNOWN  = 0,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_ASLEEP   = 10,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_DISCONNECTED = 20,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_DISCONNECTING= 30,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_CONNECTING   = 40,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_CONNECTED_LOCAL  = 50,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_CONNECTED_SITE   = 60,
> /usr/include/NetworkManager/NetworkManager.h: NM_STATE_CONNECTED_GLOBAL = 70,
> /usr/include/NetworkManager/NetworkManager.h:#define NM_STATE_CONNECTED 
> NM_STATE_CONNECTED_GLOBAL


The only tricky part in  libpurple/network.c is

> if (prev != NM_STATE_CONNECTED && prev != NM_STATE_UNKNOWN)

NM_STATE_CONNECTED 

Bug#892645: [gnome-twitch] Segfault on json node

[Jeremy Bicha]

Is this reproducible with gnome-twitch 0.4.1-1 from experimental?

Thanks,
Jeremy Bicha

Bug#889016: lintian: Please update dh_commands for scour 0.36-2

[Chris Lamb]

tags 889016 + pending
thanks

Hi James,

Thanks for the reopening this. I've updated all the debhelper data. Can
you check the scour changes over for sanity? We seem to have changed
them a number of times in the past 6 months!

You can see the diff here:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=115ce429ef09111ba8d04ebe23bbacb3a1de26c7

Do note that lintian.debian.org is not updating at the moment due
to #890873.


Regards,

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

Bug#892699: doris: switch B-D to libepr-api-dev

[Andreas Beckmann]

Source: doris
Version: 5.0.3~beta+dfsg-3
Severity: serious
Justification: fails to build from source

Hi,

the transitional package libepr-api2-dev has been removed, please update
your Build-Depends to use libepr-api-dev instead.


Andreas

Bug#891996: closed by Sven Hoexter <s...@timegate.de> (Re: Bug#891996: RFS: btrfsmaintenance/0.4-1 [I maintain the package])

[Nicholas D Steeves]

On Sun, Mar 04, 2018 at 06:12:38PM +, Debian Bug Tracking System wrote:
> Date: Sun, 4 Mar 2018 19:06:19 +0100
> From: Sven Hoexter 
> To: Nicholas D Steeves , 891996-d...@bugs.debian.org
> Subject: Re: Bug#891996: RFS: btrfsmaintenance/0.4-1 [I maintain the
>  package]
> User-Agent: Mutt/1.9.3 (2018-01-21)
> 
> 
> Hi Nicholas,
> since I did not see any action by someone else I've just uploaded
> it to unstable. I think folks committed to use btrfs engage with the toolchain
> more then people like me, who's still riding on this boring ext4. ;)
> 
> Sven

Hi Sven,

Thank you for uploading!

I totally understand riding on boring ext4, and it's what I still
recommend for friends, family, and colleagues (especially for laptops)
:-) I wonder if ext4 will gain metadata checksums by default before
XFS gains ext4's reputation for resiliency to powerloss and memory
bitflips?  I hope btrfs soon stabilizes to the point where it can be
recommended as a general purpose default...with a wiki page more along
the lines of "use it, it works" than "here are all the things that
could go wrong, and how to work around them".

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#892657: enlightenment should be built with Wayland support and enable x11 or Wayland selection for GDN login

[Ross Vandegrift]

Control: severity -1 wishlist

On Sun, Mar 11, 2018 at 08:43:14PM +0100, wei hong wrote:
> The new version of enlightenment in the experimental Debian repo does not
> appear to be built with Wayland support

That's correct - I'd like to support Wayland, but so far I've been unable to
get a Wayland enabled build working with X11.

A work-in-progress patch is in #891392.  Fixes welcome!

> Ideally, enlightenment would be built to support both Wayland and X11
> variants and by default allow selecting one of the two options (similar to
> Gnome) via the GDM login prompt options.

This is the approach in the patch mentioned above.

Ross

Bug#892698: Add master.cf.d directory to postfix to avoid manual master.cf configuration for packages

[Magnus Danielson]

Package: postfix
Version: 3.3.0-1
Severity: wishlist

When adding other packages to a Debian installed postfix, manual edit of
master.cf is needed to connect them. This is not the modern style of
Debian packaging, which have added separate directory for which other
package maintainers can add their configuration for each package.
I thus propose that the postfix package also adds a master.cf.d for
which other packages can add their specific hooks into postfix
configuration.

Among packages that should be relevant to add their hooks into
master.cf.d I find spamassassin, amavis, openspf, opendkim, opendmarc,
milter. Thus, it would enable much more of a drop-in configuration than
the current state of affairs.

The existing master.cf would remain, but the service script should upon
postfix start or reload of configuration append any of the files in
master.cf.d into a generated master.cf which is then used. The generated
file should have a first line of comment
"# Do not edit this file, automatically generated"
and then for each file included, the included part should be prepended
with a comment with filename for the source.
This will ease debugging.

With this in place, package maintainers can drop in the package
maintained master.cf.d file suitable, for instance the openspf package
would add master.cf.d/openspf. The user doing "apt-get install openspf"
would then not need to alter the postfix configuration by hand, but get
the openspf operating.

The expected implementation impact would be creating a directory and
some selected scripting to build the aggregated master.cf file and then
change the postfix call to use the aggregated master.cf file.

Similarly may main.cf need main.cf.d. This may however need some more
work, since some packages wants to add values into the middle of
existing values lists. Beyond that the same logic applies.

Best Regards,
Magnus

Bug#873250: Pending fixes for bugs in the xml-commons-external package

[pkg-java-maintainers]

tag 873250 + pending
thanks

Some bugs in the xml-commons-external package are closed in revision
ed4edb806366fd9aa6ccad92f8a5f528c418ce50 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/xml-commons-external.git/commit/?id=ed4edb8

Commit message:

No longer generate the javadoc for the javax.xml and org.w3c.dom packages 
(Closes: #873250)

Bug#889354: Pending fixes for bugs in the xml-commons-external package

[pkg-java-maintainers]

tag 889354 + pending
thanks

Some bugs in the xml-commons-external package are closed in revision
0c1c268f745dee074d6fb22563ce26d3c2f371a8 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/xml-commons-external.git/commit/?id=0c1c268

Commit message:

Removed Damien Raude-Morvan from the uploaders (Closes: #889354)

Bug#865585: tagging 859841, tagging 892415, tagging 892529, tagging 865585, tagging 865606, tagging 891307 ...

[Andreas Beckmann]

On 2018-03-11 20:04, Adrian Bunk wrote:
> Did you try building apex in stretch?
> 
> It didn't build for me when I reported the bug.

No, I just concluded this from the fact that we
a) have binaries in stretch and
b) have only a failing buildlog from a post-stretch binNMU in sid

I tried now on abel and can confirm the problem in stretch.


Andreas

Bug#745696: Please split system-wide configuration into a separate package or remove it

[Samuel Thibault]

Hello,

Josh Triplett, on lun. 23 nov. 2015 22:11:18 -0800, wrote:
> one of the few packages left in a default desktop install that runs an
> init script with a default file disabling it.  I'd like to remove that
> if possible.

AIUI, with the addition of a systemd service file in version 0.8.8-3,
the actual concern here is avoided and thus the bug could be closed?

Samuel

Bug#892670: Updating the d-feet Uploaders list

[Simon McVittie]

Control: tags -1 + pending

On Sun, 11 Mar 2018 at 21:59:02 +0100, Tobias Frost wrote:
> Thomas Bechtold  wishes no longer to be uploader of 
> d-feet.

I've updated d/control in the git repository for the next upload,
removing Thomas from the Uploaders list.

Thanks,
smcv

Bug#892696: backup2l: Cannot restore files with '[' or ']' characters in the filename

[Maciej Delmanowski]

Package: backup2l
Version: 1.6-1
Severity: important
Tags: upstream

Dear Maintainer,

The backup2l script cannot correctly restore files with '[' or ']' brackets in
the filename. Example output:

#v+
backup2l v1.5 by Gundolf Kiefer

Active files in : 69665
  found in all.1:  69665   (0 left)

Restoring 13359 directories...
Restoring files...
  all.1.tar.gz: 69665 file(s) using 'DRIVER_TAR_GZ'
tar: path/to/file/with/filename-with-\\[brackets\\]: Not found in archive
tar: Exiting with failure status due to previous errors
#v-

The problem is already reported multiple times in the upstream issue page on
GitHub:

https://github.com/gkiefer/backup2l/issues/4
https://github.com/gkiefer/backup2l/issues/5
https://github.com/gkiefer/backup2l/issues/12

This issue makes the script useful only in certain cases, it seems that if the
file with brackets is early enough in the tarball archive, the only way to
restore the files is to do it manually by hand.

Thanks for your work on Debian,
Maciej Delmanowski


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

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

backup2l depends on no packages.

Versions of packages backup2l recommends:
ii  bzip2  1.0.6-8.1

Versions of packages backup2l suggests:
ii  xz-utils  5.2.2-1.2+b1

-- Configuration Files:
/etc/backup2l.conf changed [not included]

-- no debconf information

Bug#892697: openstack-pkg-tools: Italian debconf translation update appears to be broken

[Adrian Bunk]

Package: openstack-pkg-tools
Version: 71
Severity: serious
Control: affects -1 src:heat

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/heat-10.0.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-common.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-common.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func heat-api.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func heat-api.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-api-cfn.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-api-cfn.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_postrm 
heat-common.postrm
pkgos-merge-templates heat-api heat endpoint
Merging cs.po...
Merging da.po...
Merging de.po...
Merging es.po...
Merging fr.po...
Merging gl.po...
Merging it.po...
Merging ja.po...
Merging nl.po...
Merging pl.po...
Merging pt.po...
Merging pt_BR.po...
Merging ru.po...
Merging sv.po...
Merging zh_CN.po...
pkgos-merge-templates heat-api-cfn heat-api-cfn endpoint
Merging cs.po...
Merging da.po...
Merging de.po...
Merging es.po...
Merging fr.po...
Merging gl.po...
Merging it.po...
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:22:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:32:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:44:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:77:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:120:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:145:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:152:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:159:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:166:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:173:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:180:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:253:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:263:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:282:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:291:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:312:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:337:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:344:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:366:1: syntax error
msgmerge: found 19 fatal errors
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 1



Builds with openstack-pkg-tools 70, so seems to be caused by

openstack-pkg-tools (71) unstable; urgency=medium
...
  * Updated Italian debconf translation, thanks to Daniele Mazzocchio
.
...

Bug#892695: [node-acorn] Create failure in other package

[Bastien ROUCARIÈS]

Package: node-acorn
Version: 5.5.3+ds1-1
Severity: serious

According to debci it create failure on at least:
node-astw
node-browser-unpack
node-falafel
node-lexical-scope


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

Bug#884775: [Pkg-rust-maintainers] Bug#884775: /usr/bin/rustc: Error Compiling Code: "attempt to use impure library"

[Angus Lees]

tags 884775 + unreproducible notabug
close 884775
thanks

I suspect the original issue was caused by having a non-standard "ld" in
your $PATH - specifically, I suspect it was the guix ld-wrapper[1].  (Or
perhaps a non-standard "cc" that in turn uses this guix ld)

The reply to your stack overflow question[2] suggests
that GUIX_LD_WRAPPER_ALLOW_IMPURITIES=y should disable this assertion in
ld-wrapper.  .. Or of course fiddling with $PATH such that you return to
using the standard Debian gcc/binutils binaries.

If any of that sounds incorrect, please reopen this bug.

[1]
https://github.com/drewc/guix/blob/d34c0ac6e9c669702bc4957faa5ee51f2b9465c3/gnu/packages/ld-wrapper.scm#L142
[2]
https://stackoverflow.com/questions/47737761/rust-on-debian-9-2-error-due-to-impure-library

 - Gus

Bug#892690: Autoconf-archive bug

[Bastien ROUCARIES]

Hi,

Could you recheck with newer version just uploaded ?

And close if not found

Bastien

Bug#892593: [PATCH] libverto: FTCBFS / Please add a pkg.libverto.noglib build profile

[Sam Hartman]

this approach seems a bit strange.
Why would we want a package specific build profile rather than excluding
glib from a stage1 build of libverto.

Also, note that I'm about to update to a new version of libverto and
start building for libevent.
I wonder if for bootstrapping we want to pick one single event backend
and build against that in a stage 1 build?

I need to check this, but the probable reason that I included the event
backends in the -dev package is that it is permissible to  link directly
against a plugin.
I think policy strongly implies that if a -dev package is going to have
a .so symlink for a shared library it needs to have a hard depends on
that package.
Obviously we could remove the depends when we're not building against
glib on the glib plugin, although I think that technically means that
the -dev package has different functionality depending on what build
profile is used.
Which I think is problematic for some people's view of the build profile
spec.
I think this may be an argument for revising that.

Thoughts?

Bug#892694: dput-ng: bash-completion is totally broken

[Matteo F. Vescovi]

Package: dput-ng
Version: 1.18
Severity: important

Hi!

Mattia and I were trying to figure out why, since 1.16 at least,
bash-completion on both dput and dcut commands is completely broken.
Profiles are not recognized anymore. And it's really frustrating.

Thanks a lot for your efforts in fixing this issue asap.

Cheers.


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

Kernel: Linux 4.15.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dput-ng depends on:
ii  python3   3.6.4-1
ii  python3-dput  1.18

Versions of packages dput-ng recommends:
ii  bash-completion  1:2.7-1

dput-ng suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#888663: libtemplate-perl: FTBFS with debhelper/11.1

[gregor herrmann]

On Sat, 10 Mar 2018 19:07:27 -0800, Benj. Mako Hill wrote:

> 
> > Is there something where the Debian Perl Group can help?
> Apologies for the slow response. The package needed a major
> overhaul. I've done that now and fixed this issue and quite a few
> others.

Thanks, that's excellent news.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: The Dubliners: Wild rover


signature.asc
Description: Digital Signature

Bug#888126: [patch] Please enable systemd-sysusers unit

[Martin Pitt]

Hello all,

Michael Vogt [2018-02-01  7:39 +0100]:
> just a small update on this. systemd git master has the needed support
> to reproduce the base-passwd passwd and group files now.

Many thanks for driving this! Now that 238 is released and has all the
necessary support, I've done another attempt at this:

  https://salsa.debian.org/systemd-team/systemd/merge_requests/4

This generates the files from base-file's {passwd,group}.master.

I tested this on a Debian sid container in LXC -  pretty cool to see the
container boot with a completely absent /etc! I diffed the original and
sysusers-generated passwd/group/shadow files and they are sufficiently similar.

>
> https://github.com/systemd/systemd/blob/master/test/TEST-21-SYSUSERS/test-5.input

Nice that there is an upstream test for this now!

> The only remaining problem is that it generates /sbin/nologin which we
> do not have (we use /usr/sbin/nologin).

As sysusers.d now supports specifying a shell, the above just uses the value
from the *.master file, so this isn't a problem.

Martin

Bug#892653: gretl FTBFS with glibc 2.27

[Dirk Eddelbuettel]

On 11 March 2018 at 21:31, Adrian Bunk wrote:
| Source: gretl
| Version: 2017d-3
| Severity: serious
| Tags: fixed-upstream patch
| 
| https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gretl.html
| 
| ...
| ../cephes/iv.c: In function 'cephes_bessel_Iv':
| ../cephes/iv.c:70:19: error: 'DOMAIN' undeclared (first use in this function)
|   mtherr("iv", DOMAIN);
|^~
| ../cephes/iv.c:70:19: note: each undeclared identifier is reported only once 
for each function it appears in
| make[2]: *** [Makefile:312: iv.lo] Error 1
| 
| 
| Upstream fix:
| 
https://sourceforge.net/p/gretl/git/ci/aec91eededdf618d42923276094b7c1b57dc034e/

Thanks for that.  Should now be fixed in 2017d-4 which I just uploaded.

Dirk


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

Bug#890237: closed by Anton Gladky <gl...@debian.org> (Bug#890237: fixed in yade 2018.02b-1)

[Adrian Bunk]

Control: reopen -1

On Tue, Feb 20, 2018 at 07:42:07PM +, Debian Bug Tracking System wrote:
>...
>  yade (2018.02b-1) unstable; urgency=medium
>...
>[ Adrian Bunk ]
>* [a5eddfb] Fix compilation on weak archs. (Closes: #890237)
>...

It did build for me with 2018.02a-2, but for 2018.02b-1 I need -g0:

--- debian/rules.old2018-02-22 22:06:44.675263179 +
+++ debian/rules2018-02-22 22:07:26.598594150 +
@@ -11,10 +11,10 @@
 
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed,-no-keep-memory
 
-# less debug info to avoid running
+# no debug info to avoid running
 # out of address space when linking
 ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
-   export DEB_CXXFLAGS_MAINT_APPEND += -g1
+   export DEB_CXXFLAGS_MAINT_APPEND += -g0
 endif
 
 # Check, whether Build-Depends-Indep are installed


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#862678: #862678 Drop leftover Build-Depends on network-manager-dev

[Ari Pollak]

On Sun, Mar 11, 2018 at 5:15 PM Ari Pollak  wrote:

> On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl  wrote:
>
>> By that I mean: If you don't have a runtime requirement, do you only use
>> the D-Bus API? If so, why is network-manager-dev required as build
>> dependency at all?
>>
>
> Right, it's just using the D-Bus API during runtime, but still uses the
> headers during compilation for state constants.
>

Oops, meant to include a link too:
https://anonscm.debian.org/cgit/collab-maint/pidgin.git/tree/libpurple/network.c

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

[Ari Pollak]

On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl  wrote:

> By that I mean: If you don't have a runtime requirement, do you only use
> the D-Bus API? If so, why is network-manager-dev required as build
> dependency at all?
>

Right, it's just using the D-Bus API during runtime, but still uses the
headers during compilation for state constants.

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[enyone]

My apologies.

I will drop acpi_call(O) vboxpci(O) vboxnetadp(O) vboxnetflt(O) 
vboxdrv(O) and will report back asap with more evidence.


--
Juho

Bug#892693: ITP: opcua-widgets -- common widgets for opcua-modeler and opcua-client-gui

[W. Martin Borgert]

Package: wnpp
Severity: wishlist
Owner: "W. Martin Borgert" 

* Package name: opcua-widgets
  Version : 0.5.0
  Upstream Author : Olivier Roulet-Dubonnet 
* URL : https://github.com/FreeOpcUa/opcua-widgets
* License : GPL3
  Programming Lang: Python
  Description : common widgets for opcua-modeler and opcua-client-gui

This is a dependency for opcua-client-gui (#841978).

The library uses Qt5.

Bug#892691: gnome-session: SIGSEGV in _gtk_style_provider_private_get_settings

[Nathaniel Morck Beaver]

Package: gnome-session
Version: 3.22.3-1
Severity: normal

Appears to trigger a segfault when switching to TTY using Ctrl-Alt-F1 
during login.


Possibly relevant links:

https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1552577

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

https://bugzilla.redhat.com/show_bug.cgi?id=1395968

https://bugzilla.redhat.com/show_bug.cgi?id=1384508

Both backtraces are attached.


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

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.22.3-1
ii  gnome-session-common   3.22.3-1
ii  gnome-settings-daemon  3.22.2-2+deb9u2
ii  gnome-shell3.22.3-3

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base  9.0.2+deb9u1
ii  gnome-keyring 3.20.0-3
ii  gnome-user-guide  3.22.0-1

-- no debconf information
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/gnome-session/gnome-session-failed...Reading 
symbols from 
/usr/lib/debug/.build-id/76/3adef6d5af5a95a844e49cd1986ea89efda9be.debug...done.
done.

warning: core file may not match specified executable file.
[New LWP 15696]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/gnome-session/gnome-session-failed --debug 
--allow-logout'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fdb788f6e19 in _gtk_style_provider_private_get_settings (
provider=0x0) at ././gtk/gtkstyleproviderprivate.c:123
123 ././gtk/gtkstyleproviderprivate.c: No such file or directory.
(gdb) info proc
exe = '/usr/lib/gnome-session/gnome-session-failed --debug --allow-logout'
(gdb) info locals
iface = 
(gdb) info args
provider = 0x0
(gdb) info frame
Stack level 0, frame at 0x7ffe4ca787f0:
 rip = 0x7fdb788f6e19 in _gtk_style_provider_private_get_settings 
(././gtk/gtkstyleproviderprivate.c:123); saved rip = 0x7fdb78792a78
 called by frame at 0x7ffe4ca78820
 source language c.
 Arglist at 0x7ffe4ca787d8, args: provider=0x0
 Locals at 0x7ffe4ca787d8, Previous frame's sp is 0x7ffe4ca787f0
 Saved registers:
  rbx at 0x7ffe4ca787e0, rip at 0x7ffe4ca787e8
(gdb) info threads
  Id   Target Id Frame 
* 1Thread 0x7fdb790cfa40 (LWP 15696) 0x7fdb788f6e19 in 
_gtk_style_provider_private_get_settings (provider=0x0) at 
././gtk/gtkstyleproviderprivate.c:123
(gdb) thread apply all backtrace full

Thread 1 (Thread 0x7fdb790cfa40 (LWP 15696)):
#0  0x7fdb788f6e19 in _gtk_style_provider_private_get_settings 
(provider=0x0) at ././gtk/gtkstyleproviderprivate.c:123
iface = 
#1  0x7fdb78792a78 in gtk_css_value_initial_compute (value=, 
property_id=1, provider=0x0, style=0x555ad0978020 [GtkCssStaticStyle], 
parent_style=0x0) at ././gtk/gtkcssinitialvalue.c:52
settings = 
#2  0x7fdb787a7b84 in gtk_css_static_style_compute_value 
(style=0x555ad0978020 [GtkCssStaticStyle], provider=, 
parent_style=, id=1, specified=0x7fdb78f23200 , 
section=0x0) at ././gtk/gtkcssstaticstyle.c:237
value = 
#3  0x7fdb78793dac in _gtk_css_lookup_resolve 
(lookup=lookup@entry=0x555ad0976800, provider=provider@entry=0x0, 
style=style@entry=0x555ad0978020 [GtkCssStaticStyle], 
parent_style=parent_style@entry=0x0) at ././gtk/gtkcsslookup.c:122
i = 1
#4  0x7fdb787a7aac in gtk_css_static_style_new_compute 
(provider=provider@entry=0x0, matcher=matcher@entry=0x0, 
parent=parent@entry=0x0) at ././gtk/gtkcssstaticstyle.c:195
result = 0x555ad0978020 [GtkCssStaticStyle]
lookup = 0x555ad0976800
change = 4294967295
#5  0x7fdb787a7b05 in gtk_css_static_style_get_default () at 
././gtk/gtkcssstaticstyle.c:164
settings = 0x0
#6  0x7fdb78794712 in gtk_css_node_init (cssnode=0x555ad0964690 
[GtkCssNode]) at ././gtk/gtkcssnode.c:663
#7  0x7fdb780fd32f in 

Bug#892671: [Pkg-nagios-devel] Bug#892671: Updating the check-mk Uploaders list

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 03/11/2018 09:59 PM, Tobias Frost wrote:
> Thomas Bechtold  wishes no longer to be uploader of 
> check-mk.
> 
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.

Fixed in git. No idea when a new upload to unstable will happen though.

Kind Regards,

Bas

Bug#892692: RM: gnome-software-plugin-snap [mips mips64el mipsel powerpc] -- ANAIS; no longer built for these arches

[Jeremy Bicha]

Package: ftp.debian.org
X-Debbugs-CC: gnome-softw...@packages.debian.org

snapd is not available on mips, mips64el, mipel and powerpc. To avoid
an unsatisfiable dependency, gnome-software-plugin-snap is no longer
built on those architectures. Please remove the
gnoem-software-plugin-snap package from those architectures.

Thanks,
Jeremy Bicha

Bug#875336: FTBFS with Java 9: _ as identifier

[Emmanuel Bourg]

Le 10/03/2018 à 08:57, Emmanuel Bourg a écrit :

> I'll upgrade Groovy, we'll see if that helps.

Groovy 2.4.14 is now in unstable. Is it any better?

Bug#881216: sagemath: Not using standard LaTeX fonts with plots using text()

[Jaimos Skriletz]

On Sun, Mar 11, 2018 at 9:28 AM, Ximin Luo  wrote:
> Resending to the submitter as the BTS does not do that automatically
>
> Ximin Luo:
>> Hi Jaimos, you can force use of the latex fonts by passing typeset="latex" 
>> as a parameter to any one of the three functions plot(), text() or show() 
>> that you're using.


This is indeed the case, setting the typeset option to latex fixed the
issue. Maybe it is some difference in how the sage provided and Debian
provided matplotlib differ. Anyways since this is just a configuration
issue, I no longer see this as a bug and it can be closed.

Thanks,

jaimos

Bug#887940: [Pkg-postgresql-public] Bug#887940: libpq-dev:

[Adrian Bunk]

Control: clone -1 -2
Control: reopen -2
Control: reassign -2 autoconf-archive 20170321-1
Control: retitle -2 autoconf-archive: ax_lib_postgresql.m4 must be updated to 
work with the Debian-specific version string

On Tue, Jan 30, 2018 at 12:14:53AM +0100, Thomas Andrejak wrote:
> On Tue, 23 Jan 2018 09:50:32 +0100 Christoph Berg  wrote:
> > Control: reassign -1 src:libpreludedb
> >
> > Re: Adrian Bunk 2018-01-23 <20180123043023.GA11847@localhost>
> > > > > ./configure: line 19300: test: too many arguments
> > > > > ...
> > > >
> > > > Looks like the ax_lib_postgresql.m4 macro should be fixed with some
> > > > additional shell quoting.
> > >
> > > This is not about quoting, the pg_config output changed:
> > >
> > > 10.1-3:
> > > $ pg_config --version
> > > PostgreSQL 10.1 (Debian 10.1-3)
> >
> > The macro is buggy anyway, it decomposes the string into
> > major/minor/micro, but the middle component doesn't exist anymore with
> > PostgreSQL 10. That was fine with 10.0, but with 10.1, it will think
> > there was a new major release "10.1".
> >
> > Both issues need to be fixed on the libpreludedb side.
> >
> 
> OK but m4 came from autoconf-archive, they have to provide a new m4
> not buggy so we can update it inside libpreludedb.

I'm cloning a bug to autoconf-archive, that the master version of this 
macro there needs updating for the Debian-specific version string.

> Regards
> 
> Thomas

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#892688: Updating the ruby-base62 Uploaders list

[Tobias Frost]

Source: ruby-base62
Version: 1.0.0-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
ruby-base62.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892687: Updating the pidgin-gnome-keyring Uploaders list

[Tobias Frost]

Source: pidgin-gnome-keyring
Version: 2.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
pidgin-gnome-keyring.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892689: Updating the requests-aws Uploaders list

[Tobias Frost]

Source: requests-aws
Version: 0.1.5-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
requests-aws.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892682: Updating the puppet-module-saz-memcached Uploaders list

[Tobias Frost]

Source: puppet-module-saz-memcached
Version: 2.6.0-1 2.8.1-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-saz-memcached.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892686: Updating the puppet-module-puppetlabs-xinetd Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-xinetd
Version: 1.3.1-1 1.5.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-xinetd.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892683: Updating the puppet-module-puppetlabs-apache Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-apache
Version: 1.1.1-1 1.10.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-apache.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892676: Updating the puppet-module-puppetlabs-mysql Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-mysql
Version: 2.3.1-1 3.10.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-mysql.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892685: Updating the ruby-puppetlabs-spec-helper Uploaders list

[Tobias Frost]

Source: ruby-puppetlabs-spec-helper
Version: 0.4.1-2 0.10.3-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
ruby-puppetlabs-spec-helper.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892675: Updating the puppet-module-puppetlabs-inifile Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-inifile
Version: 1.1.4-1 1.6.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-inifile.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892674: Updating the libzypp Uploaders list

[Tobias Frost]

Source: libzypp
Version: 14.29.1-2 15.3.0-1 16.4.3-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of libzypp.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

[Michael Biebl]

Am 11.03.2018 um 21:56 schrieb Michael Biebl:
> Am 11.03.2018 um 21:10 schrieb Ari Pollak:
>> Pidgin is still using network-manager-dev to have NetworkManager support
>> without requiring an extra runtime dependency. 
> 
> How does that work?

By that I mean: If you don't have a runtime requirement, do you only use
the D-Bus API? If so, why is network-manager-dev required as build
dependency at all?


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



signature.asc
Description: OpenPGP digital signature

Bug#892684: Updating the python-scripttest Uploaders list

[Tobias Frost]

Source: python-scripttest
Version: 1.3-1 1.3-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
python-scripttest.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892680: Updating the flask-script Uploaders list

[Tobias Frost]

Source: flask-script
Version: 0.6.7-1 2.0.5-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
flask-script.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892670: Updating the d-feet Uploaders list

[Tobias Frost]

Source: d-feet
Version: 0.3.9-1 0.3.13-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of d-feet.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892673: Updating the billiard Uploaders list

[Tobias Frost]

Source: billiard
Version: 3.3.0.18-2 3.5.0.3-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
billiard.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892681: Updating the python-unicodecsv Uploaders list

[Tobias Frost]

Source: python-unicodecsv
Version: 0.9.4-1 0.14.1-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
python-unicodecsv.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892671: Updating the check-mk Uploaders list

[Tobias Frost]

Source: check-mk
Version: 1.4.0p9-1 1.2.8p26-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
check-mk.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892672: Updating the billiard Uploaders list

[Tobias Frost]

Source: billiard
Version: 3.3.0.18-2 3.5.0.3-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
billiard.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892677: Updating the puppet-module-puppetlabs-postgresql Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-postgresql
Version: 4.0.0-2 4.8.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-postgresql.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892669: Updating the flask-migrate Uploaders list

[Tobias Frost]

Source: flask-migrate
Version: 1.2.0-1 2.1.1-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
flask-migrate.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892678: Updating the puppet-module-puppetlabs-concat Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-concat
Version: 1.1.1-1 2.2.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-concat.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892679: Updating the flask-sqlalchemy Uploaders list

[Tobias Frost]

Source: flask-sqlalchemy
Version: 1.0-2 2.1-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
flask-sqlalchemy.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892665: Updating the puppet-module-puppetlabs-stdlib Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-stdlib
Version: 4.3.2-1 4.24.0-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-stdlib.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892667: Updating the puppet-module-puppetlabs-firewall Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-firewall
Version: 1.1.3-1 1.11.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-firewall.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892666: Updating the puppet-module-puppetlabs-ntp Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-ntp
Version: 3.2.1-1 7.0.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-ntp.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892668: Updating the puppet-module-puppetlabs-apt Uploaders list

[Tobias Frost]

Source: puppet-module-puppetlabs-apt
Version: 1.4.2-1 4.4.1-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Thomas Bechtold  wishes no longer to be uploader of 
puppet-module-puppetlabs-apt.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[Bastian Blank]

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

On Sun, Mar 11, 2018 at 07:57:11PM +0200, enyone wrote:
[ no text] 

> ** Tainted: O (4096)
>  * Out-of-tree module has been loaded.

Please drop this modules, they are not supported by us.  After you do,
please show new evidence.

Bastian

Bug#879789: Fixed in stretch by binNMU

[Adrian Bunk]

Control: tags -1 buster sid

This was now fixed in stretch with a binNMU (#891585).

This tagging is not completely correct, but closing bugs with binNMU 
versions does not work.

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#876112: fvwm: buffer overflow crash after opening lots of clients

[Jaimos Skriletz]

On Mon, 18 Sep 2017 15:54:41 +0100 "Jonathan David Amery"
 wrote:
> Hi,
>
>  Oops, there's a bug in the steps to reproduce there introduced while I
> sanitized the filename of my png file.  The steps should be:
>
> 1. start fvwm2
> 2. find a small png file
> 3. for x in $(seq 1 2000); do display small.png & done
> 4. fvwm crashes
>

I am unable to reproduce this bug. When I run this command I hit the
Maximum number of clients reached limit, so only some of the windows
open, but no crash.

In addition your system info seems to be outdated (your fvwm version is)
and maybe a stretch/sid mix.

I am going to close this bug. If you can reproduce it in a clean stretch or sid
environment with current patches, you can reopen the bug. Including the
.png file that cause the problem could also help.

jaimos

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

[Menno Finlay-Smits]

On Mon, 12 Mar 2018, at 00:06, Yves-Alexis Perez wrote:
> On Mon, 2018-03-12 at 00:02 +1300, Menno Finlay-Smits wrote:
> > Do you want me to help figure out which change to the kernel fixed the
> > problem?
> 
> As far as I can tell and if I'm not mistaken, the fix is already identified
> and is included in 4.9.86.
> 
> I've started working on it for Stretch, and at one point it will be uploaded
> to -proposed-updates for inclusion in the next point release (9.5). When it's
> done I'll probably ask you to try a test kernel to make sure it's really
> fixed.

I'm happy to try it out when it's available.

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

[Michael Biebl]

Am 11.03.2018 um 21:10 schrieb Ari Pollak:
> Pidgin is still using network-manager-dev to have NetworkManager support
> without requiring an extra runtime dependency. 

How does that work?

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



signature.asc
Description: OpenPGP digital signature

Bug#892599: afflib: CVE-2018-8050

[Phillip Hellewell]

I checked in the fix for this in commit 435a2ca (
https://github.com/sshock/AFFLIBv3/commit/435a2ca).  (Sorry I didn't have a
CVE id yet so that was not included in the commit comment.)

What needs to happen now?  Do I need to do anything or can you guys take it
from here?

Phillip

On Sun, Mar 11, 2018 at 3:40 AM, Salvatore Bonaccorso 
wrote:

> Source: afflib
> Version: 3.7.5-1
> Severity: important
> Tags: patch security upstream
>
> Hi,
>
> the following vulnerability was published for afflib.
>
> CVE-2018-8050[0]:
> | The af_get_page() function in lib/afflib_pages.cpp in AFFLIB (aka
> | AFFLIBv3) through 3.7.16 allows remote attackers to cause a denial of
> | service (segmentation fault) via a corrupt AFF image that triggers an
> | unexpected pagesize value.
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2018-8050
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8050
> [1] https://github.com/sshock/AFFLIBv3/commit/
> 435a2ca802358a3debb6d164d2c33049131df81c
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore
>
>

Bug#892664: dpkg: Please add support for zstd (Zstandard) compressed packages

[Balint Reczey]

Package: dpkg
Version: 1.19.0.5
Severity: wishlist
Tags: patch

Dear Dpkg Developers,

Please add support for Zstandard compression to dpkg and other
programs generated by the dpkg source package [1].

Tests on packages repackaged with zstd -19 show little increase in
compressed package size compared to xz -6 while decompression speed
decreased dramatically.

For the recompressed firefox .deb (Ubuntu's
firefox_58.0.2+build1-0ubuntu0.17.10.1_amd64.deb) increased ~9% in
size but decompressed in <20% of the original time:

$ du -s firefox-*deb
43960 firefox-xz.deb
47924 firefox-zstd.deb

$ rm -rf firefox-xz/* ;time  dpkg-deb -R firefox-xz.deb firefox-xz/
real 0m4,270s
user 0m4,220s
sys 0m0,630s
$ rm -rf firefox-zstd/* ;time  dpkg-deb -R firefox-zstd.deb firefox-zstd/
real 0m0,765s
user 0m0,556s
sys 0m0,462s

Tests on the full Ubuntu main archive showed ~6% average increase in
the size of the binary packages.

The patches are also available on Salsa [2].

Cheers,
Balint

--
Balint Reczey
Ubuntu & Debian Developer

[1] http://facebook.github.io/zstd/
[2] https://salsa.debian.org/rbalint/dpkg/commits/zstd
From 79aad733cbc7edd44e124702f82b8a46a3a4aea9 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Thu, 8 Mar 2018 09:53:36 +0100
Subject: [PATCH 1/4] dpkg: Add Zstandard compression support

---
 README  |   1 +
 configure.ac|   2 +
 debian/control  |   3 ++
 debian/rules|   1 +
 dpkg-deb/Makefile.am|   1 +
 dpkg-deb/extract.c  |   1 +
 dpkg-deb/main.c |   2 +-
 lib/dpkg/compress.c | 127 +++-
 lib/dpkg/compress.h |   1 +
 m4/dpkg-libs.m4 |   7 +++
 man/deb.man |   6 ++-
 man/dpkg-deb.man|   2 +-
 man/dpkg-source.man |   2 +-
 scripts/Dpkg/Compression.pm |   6 +++
 14 files changed, 156 insertions(+), 6 deletions(-)

diff --git a/README b/README
index 348f8e700..b0cf0a528 100644
--- a/README
+++ b/README
@@ -72,6 +72,7 @@ To enable optional functionality or programs, this software might be needed:
 
   libmd (used by libdpkg, currently falling back to embedded code)
   libz (from zlib, used instead of gzip command-line tool)
+  libzstd (from libzstd, used instead of zstd command-line tool)
   liblzma (from xz utils, used instead of xz command-line tool)
   libbz2 (from bzip2, used instead of bzip2 command-line tool)
   libselinux
diff --git a/configure.ac b/configure.ac
index f6dff9f5e..2fbff6759 100644
--- a/configure.ac
+++ b/configure.ac
@@ -75,6 +75,7 @@ AC_SYS_LARGEFILE
 # Checks for libraries.
 DPKG_LIB_MD
 DPKG_LIB_Z
+DPKG_LIB_ZSTD
 DPKG_LIB_BZ2
 DPKG_LIB_LZMA
 DPKG_LIB_SELINUX
@@ -251,6 +252,7 @@ Configuration:
 libselinux  . . . . . . . . . : $have_libselinux
 libmd . . . . . . . . . . . . : $have_libmd
 libz  . . . . . . . . . . . . : $have_libz
+libzstd  . . . . . . . . . .  : $have_libzstd
 liblzma . . . . . . . . . . . : $have_liblzma
 libbz2  . . . . . . . . . . . : $have_libbz2
 libcurses . . . . . . . . . . : ${have_libcurses:-no}
diff --git a/debian/control b/debian/control
index c73f79762..833f6c2b7 100644
--- a/debian/control
+++ b/debian/control
@@ -20,6 +20,7 @@ Build-Depends:
  po4a (>= 0.43),
  zlib1g-dev,
  libbz2-dev,
+ libzstd-dev,
  liblzma-dev,
  libselinux1-dev [linux-any],
  libncursesw5-dev,
@@ -67,6 +68,7 @@ Multi-Arch: same
 Depends:
  ${misc:Depends},
  zlib1g-dev,
+ libzstd-dev,
  liblzma-dev,
  libbz2-dev,
 Description: Debian package management static library
@@ -132,6 +134,7 @@ Recommends:
 # Used by Dpkg::Gettext.
  liblocale-gettext-perl,
  bzip2,
+ zstd,
  xz-utils,
 Suggests:
  debian-keyring,
diff --git a/debian/rules b/debian/rules
index 27a2499ef..92f1d1c48 100755
--- a/debian/rules
+++ b/debian/rules
@@ -64,6 +64,7 @@ build-tree/config.status: configure
 		--with-devlibdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
 		--without-libmd \
 		--with-libz \
+		--with-libzstd \
 		--with-liblzma \
 		--with-libbz2
 
diff --git a/dpkg-deb/Makefile.am b/dpkg-deb/Makefile.am
index 02d79ed7d..bbd30e02c 100644
--- a/dpkg-deb/Makefile.am
+++ b/dpkg-deb/Makefile.am
@@ -21,5 +21,6 @@ dpkg_deb_LDADD = \
 	../lib/dpkg/libdpkg.la \
 	$(LIBINTL) \
 	$(Z_LIBS) \
+	$(ZSTD_LIBS) \
 	$(LZMA_LIBS) \
 	$(BZ2_LIBS)
diff --git a/dpkg-deb/extract.c b/dpkg-deb/extract.c
index dba15dedb..7fd4b2b67 100644
--- a/dpkg-deb/extract.c
+++ b/dpkg-deb/extract.c
@@ -179,6 +179,7 @@ extracthalf(const char *debar, const char *dir,
   decompressor = compressor_find_by_extension(extension);
   if (decompressor != COMPRESSOR_TYPE_NONE &&
   decompressor != COMPRESSOR_TYPE_GZIP &&
+  decompressor != COMPRESSOR_TYPE_ZSTD &&
   decompressor != COMPRESSOR_TYPE_XZ)
 ohshit(_("archive '%s' uses unknown compression for member '%.*s', "
  "giving up"),
diff --git a/dpkg-deb/main.c 

Bug#892663: ITP: node-keyv -- Simple key-value storage with support for multiple backends

[mohit phulera]

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

* Package name: node-keyv
  Version : 3.0.0
  Upstream Author : Luke Childs  (
http://lukechilds.co.uk)
* URL  : https://github.com/lukechilds/keyv
* License : Expat
  Programming Lang: JavaScript
  Description: Simple key-value storage with support for multiple
backends.
  Keyv provides a consistent interface for key-value storage across
multiple backends via storage adapters. It supports TTL based expiry,
making it suitable as a cache or a persistent key-value store.
Node.js is an event-based server-side JavaScript engine.

Bug#892662: uglifyjs FTBFS:

[Adrian Bunk]

Source: uglifyjs
Version: 2.8.29-3
Severity: serious
Control: fixed -1 3.3.10-1
Control: close -1

https://tests.reproducible-builds.org/debian/history/uglifyjs.html
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/i386/uglifyjs.html

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

...
  7 passing (3m)
  103 failing

  1) Accessor tokens
   Should fill the token information for accessors (issue #1492):
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) arguments
   Should recognize when a function uses arguments:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  3) bin/uglifyjs
   should produce a functional build when using --self:
 Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  4) bin/uglifyjs
   Should be able to filter comments correctly with `--comment all`:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:30:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  5) bin/uglifyjs
   Should be able to filter comments correctly with `--comment `:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:40:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  6) bin/uglifyjs
   Should be able to filter comments correctly with just `--comment`:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:50:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  7) bin/uglifyjs
   Should append source map to output when using --source-map-inline:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:61:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Socket.stream.socket.on (internal/child_process.js:346:11)

  8) bin/uglifyjs
   should not append source map to output when not using 
--source-map-inline:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:71:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit 

Bug#891628: Processed: diodon: Fails to build with vala 0.40

[Oliver Sauder]

I have addressed this issue and uploaded a new package to mentors.

See sponsorship request at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892660

Oliver

Bug#892661: node-static-extend: FTBFS and Debci failure

[Adrian Bunk]

Source: node-static-extend
Version: 0.1.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-static-extend FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-static-extend/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-static-extend.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-static-extend.html

...
  9 passing (18ms)
  2 failing

  1) extend
   should add `Parent.prototype` to `Ctor` instances as `_parent_`:

  AssertionError [ERR_ASSERTION]: { configurable: true,
  set: [Function: set],
  get: [Function: get] } deepEqual Parent { a: [Function], b: [Function], c: 
[Function] }
  + expected - actual

   {
  -  "configurable": true
  -  "get": [Function]
  -  "set": [Function]
  +  "a": [Function]
  +  "b": [Function]
  +  "c": [Function]
   }
  
  at Context. (test.js:38:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) extend
   should access `Parent` methods through `_parent_`:
 TypeError: this._parent_.upper is not a function
  at Ctor.instance.upper (test.js:58:28)
  at Context. (test.js:60:27)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2

Bug#892280: libcdk5: library package needs to be renamed for libncurses6 transition

[Sven Joachim]

On 2018-03-11 10:57 -0300, Herbert Fortes wrote:

> Em 10-03-2018 15:24, Sven Joachim escreveu:
>> On 2018-03-10 09:31 -0300, Herbert Fortes wrote:
>> 
>>> Em 09-03-2018 17:03, Sven Joachim escreveu:
 On 2018-03-09 15:18 -0300, Herbert Fortes wrote:

> Hi Sven Joachim,
>
>>> My conclusion is that it is very risky to allow such combinations, and
>>> to rule them out I propose to change the package name of the cdk
>>> library, say to libcdk5a.  It would then have to build-depend on
>>> libncurses-dev (>= 6.1+20180210) to ensure that it is linked against
>>> libncurses6 and not libncurses5.  Of course this can only be uploaded
>>> to experimental for now, but should go to unstable when the ncurses
>>> transition starts there.
>
>
> I am OK with changing the name. But libcdk5a does not say 
> much about why the change.
>
> Since the package name will change because of SONAME of 
> libncurses, I thought to follow the SONAME of the library.

 Well, the SONAME of the cdk library does not change with my proposal.

> libcdk5-6

 If you like that better than libcdk5a, choose it.  Or any other name,
 it's rather arbitrary anyway.

> But maybe this will cause misunderstanding. The change is
> on version 6.1+20180210.

 That's why the build-dependency on libncurses-dev (>= 6.1+20180210) is
 needed.

 I am not sure we understand each other yet, but I'm happy to answer
 questions.

>>>
>>> Good! I am searching for a name. And talk about it could
>>> help.
>>>
>>> cdk library had problems before (about name), and I belive
>>> the number "5" (cdk SONAME) was the choice to differ from the
>>> other package. That's what I remember.
>>>
>>>  - libcdk-java
>>>  - libcdk-perl
>>>  - libcdk5
>>>
>>> The "5" was accepted because the SONAME does not change much.
>> 
>> The "5" is there because it is the standard convention for shared
>> library packages: if you ship libfoo.so.5 in your package, the package
>> is supposed to be called libfoo5.  See the chapter in the Policy about
>> shared libraries.[1]
>> 
>> Now, the "chtype" change in ncurses changes the ABI of the cdk library,
>> and hence the package name must change to not break reverse dependencies
>> (e.g. gphoto2).  Ideally, the SONAME would also change, but this means
>> you would have to invent your own SONAME since upstream did not take it
>> into account.  Therefore I proposed to only change the package name,
>> from libcdk5 to libcdk5a (or any other name, it's really arbitrary).
>> This means that the reverse dependencies have to be upgraded in
>> lock-step, but since there are only three of them (cpm, libcdk-perl and
>> gphoto2), that looks manageable.
>
> OK. I read what I wanted (SONAME part) and understood why the 
> change. Thanks for that!
>
> I only managed one SONAME change (libgphoto2), more than a year ago.
> After change the name I must email the reverse_dependencies and
> ask them to use the new package and let the old one die. Is that
> it?

No, reverse dependencies just have to be binNMU'ed.  For cpm and gphoto2
this will happen anyway as part of the ncurses transition, for
libcdk-perl we'll have to ask the release team separately.  But I can
take care of that.

> (new package - add break, replaces)

Or Conflicts+Replaces as in my original patch.

> I also have to deal with the repo name. I created it two years ago.
> Named libcdk5 (libcdk5.git).

It probably should have been named cdk instead, but I would postpone
renaming the source package until the SONAME actually changes.  But
that's up to you.  The downside (if you rename the source package now)
is that the FTP masters may take longer to review it than if there's
just a new binary package.
 
>>> The number "6" is from libncurses. If the two projects have
>>> a strong link, it could be used. But seeing the two numbers,
>>> which of them refers to what. I can put an explanation on 
>>> debian/README.Debian file. But maybe the name will be changed
>>> more than expected.
>> 
>> Well, you could use libcdk5nc6 or something like that to indicate that
>> the package name change is related to libncurses6, but there is no need
>> to explain this in a README.Debian, since shared libraries are usually
>> automatically installed as a dependency of some other package and not
>> for their own merits.
>> 
>
> libcdk5nc6 sounds good to me.

Fine with me, I have attached an updated patch for that new name.

Cheers,
   Sven

>From 201a8f92b2bfacdc912096a60777693937f3007f Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 7 Mar 2018 19:02:30 +0100
Subject: [PATCH] Rename the library package to libcdk5nc6

The change of the "chtype" data type in libncurses6 means that it is
not safe to have the cdk library and applications using it linked
against different ncurses versions.

To ensure that both the library and the application are linked against

Bug#876885: fvwm: FvwmConsole can't be configured with X resources

[Jaimos Skriletz]

On Mon, Oct 9, 2017 at 1:43 PM, Jaimos Skriletz
 wrote:
> On Tue, Sep 26, 2017 at 11:05 PM, Danek Duvall  wrote:
>>> I see this as a bug in the man page to clarify this. Namely the
>>> default is FvwmConsole's resource is that of the terminal
>>> x-terminal-emulator points uses. Also clarify that the example
>>> resources were written for xterm with the -name FvwmConsole flag.
>>
>> I figured that would be the likely outcome.  That'd be okay by me.  But see
>> below.
>>
>> However, it occurred to me that there might be another way to do this.  I
>> discovered the RESOURCE_NAME environment variable, which I'd never used
>> before, but if I put
>>
>> setenv("RESOURCE_NAME", "FvwmConsole", 1);
>>

I tested this out, and it appears to be specific to xterm. I was not
able to get any
terminal except xterm to set the resource using that environment variable. Since
this doesn't seem to be supported for other terminals, I don't see it
being much use
either in Debian or upstream over just using the -name flag. I will
add clarification to
the manpage to use the -name option if supported to set the resource
to FvwmConsole.

jaimos

Bug#892660: Subject: RFS: diodon/1.8.0-1

[Oliver Sauder]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: diodon
   Version : 1.8.0-1
   Upstream Author : Oliver Sauder 
 * URL : https://launchpad.net/diodon/
 * License : GPLv2
   Section : utils

It builds those binary packages:

 diodon - GTK+ Clipboard manager
 diodon-dev - GTK+ Clipboard manager (development files)
 gir1.2-diodon-1.0 - GTK+ Clipboard manager (GObject introspection data)
 libdiodon0 - GTK+ Clipboard manager (main library)

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

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


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

  dget -x
https://mentors.debian.net/debian/pool/main/d/diodon/diodon_1.8.0-1.dsc

Changes since the last upload:

  * New upstream release.
  * Remove gee dependency (LP: #1745877)
  * Add support for valac 0.40 (Closes: #891628)
  * Set Section of libdiodon to libs
  * Set Section of diodon-dev to libdevel
  * Bump Standard Version to 4.1.3
  * Fix debian-watch-uses-insecure-uri
  * Use compat version 11

Regards,
 Oliver Sauder








signature.asc
Description: OpenPGP digital signature

Bug#857090: update-command-not-found does nothing

[Roland Hieber]

On Tue, 29 Aug 2017 11:14:47 +0200 Christian Schrötter wrote:
> > I think update-command-not-found should make it clearer that you need to
> > update the apt-cache prior to running it.
> 
> Indeed, that would be great.

I was running into this problem just now, and after remembering how to
write Python 2 code, here is a small patch that should do the job :-)

Cheers,
 - Roland

--- /usr/sbin/update-command-not-found  2016-11-15 20:39:52.0 +0100
+++ debian/update-command-not-found 2018-03-11 21:01:32.084066383 +0100
@@ -69,7 +69,13 @@

 def write_db_apt_file():
import glob
-   for fname in glob.glob('/var/lib/apt/lists/*Contents*.*'):
+   content_files = glob.glob('/var/lib/apt/lists/*Contents*.*')
+   if len(content_files) == 0:
+   print 'No files /var/lib/apt/lists/*Contents*.* found.'
+   print 'Please run "apt update" before using this command.'
+   sys.exit()
+
+   for fname in content_files:
if "Contents-source" in fname:
continue
if fname.endswith(".diff_Index"):

Bug#883425: stale Android device entries in Thunar after USB disconnection

[Ben Caradoc-Davies]

Confirmed fixed by gvfs 1.35.90-1.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#892502: bluefish: Non English characters in html document breaks zen coding

[Goran Vulić]

On Sun, 11 Mar 2018 20:43:36 +0100 Innocent De Marchi  wrote:
> Hi Goran Vulić,
> 
> Thank you so much for your explanation, but, does not this seem more
> like a problem with Zen coding? Have you tried in another HTML
editor?
> It could be ruled out that it is Zen coding that fails.
> 
> Regards!
> 
> I. De Marchi
> 
> 


I checked in other text editors and Zen coding works. 

So, it is not Zen coding that fails, but Bluefish implementation of Zen
coding.

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

Control: tags -1 moreinfo

Am 11.03.2018 um 03:34 schrieb johnw:
> Package: systemd
> Version: 238-2
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>   I noticed, my system(xfce4, slim) can not create user.slice /
>   user session,
> 
>   and start-pulseaudio-x11 can not start
>   (start-pulseaudio-x11 error message:
>Connection failure: Connection refused
>pa_context_connect() failed: Connection refuse)
>   and the system become no sound
> 
>   systemctl --user status
>   Failed to read server status: Process org.freedesktop.systemd1 exited 
> with status 1
> 
>   All work well before systemd =< 237-4
> 
>   Please help, thanks.
> 

Please provide the output of
systemctl status
journalctl -alb (as root)

Have you rebooted after the upgrade?

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



signature.asc
Description: OpenPGP digital signature

Bug#883425: stale Android device entries in Thunar after USB disconnection

[Ben Caradoc-Davies]

This is almost certainly the same bug as:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882353
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1739537
https://bugzilla.gnome.org/show_bug.cgi?id=789491

If so, it should be fixed by gvfs (1.35.90-1) (currently in in 
experimental), which includes the upstream fix:

https://git.gnome.org/browse/gvfs/commit/?id=0c7f803b592a2f472714c5e7c97b92515aef0620

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#892370: Aerial Bold chosen when it should not be

[Fabian Greffrath]

Hi guys,

Am Sonntag, den 11.03.2018, 21:05 +0530 schrieb Vasudev Kamath:
> Mean while any one else from fonts team have any idea on this issue?.
> Is it related to fontconfig configurations?

I don't think it is related to the fontconfig config file that we
patch/ship, but have a look at this:

 fc-match -a aerial | head -n 2
Aerial.ttf: "sans" "Regular"
AerialBd.ttf: "Aerial" "Bold"

The regular variant doesn't identify itself as "Aerial" but merely as
"sans", so the Bold variant is the first one known by the name
"Aerial".

Looks like the regular font is broken. Anyway, didn't we decide earlier
in #872766 to drop this package from Debian altogether in favour of
fonts-liberation or fonts-croscore?

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