Bug#886120: FTBFS: chown: cannot access '..._cgraph.dot': No such file or directory

[Vasudev Kamath]

Adam Borowski  writes:

> On Tue, Jan 09, 2018 at 10:42:19PM +0530, Vasudev Kamath wrote:
>> Control: tag -1 +moreinfo +unreproducible
>> 
>> Adam Borowski  writes:
>> > Source: ctpp2
>> > Version: 2.8.3-23
>> >
>> > Hi!
>> > I'm afraid your package fails to build:
>> >
>> > dh_fixperms -pctpp2-doc 
>> > chown: cannot access 
>> > 'debian/ctpp2-doc/usr/share/doc/ctpp2-doc/html/a01323_acf0137f96d20b71a2e2e18b489d1a33e_cgraph.dot':
>> >  No such file or directory
>> > chown: cannot access 
>> > 'debian/ctpp2-doc/usr/share/doc/ctpp2-doc/html/inherit_graph_65.md5': No 
>> > such file or directory
>> > dh_fixperms: find debian/ctpp2-doc -true -print0 2>/dev/null | xargs -0r 
>> > chown --no-dereference 0:0 returned exit code 123
>> > dh_fixperms: Aborting due to earlier error
>> >
>> > Tried on armhf amd64.  Log attached.
>> 
>> Could not reproduce on amd64, it built fine. Was not able to check on
>> armhf yet. Attaching my build log for reference.
>
> Sorry for the delay.  I haven't found the cause yet, but here's my progress:
>
> It looks like kernel version is a factor.  All my test machines run current
> 4.15-rc, so that was common to all builds.
>
> On amd64, with today's unstable:
> ✓ 4.9.76, self-compiled
> ✗ 4.14.13, self-compiled
> ✗ linux-image-4.14.0-3-amd64 (4.14.12-2)
> ✗ 4.15.0-rc7-debug-00137, self-compiled
>
> You do run some version of 4.14.0-3-amd64, though.  Hrm...  Lemme poke more.

Yeah. Since you mentioned its random can we reduce the severity of the
bug?.

Meow,

Bug#886119: WORKSFORME mac-ppc32

[Boyd Waters]

WORKSFORME mac-ppc32

Linux ppc32mini 3.16.0-5-powerpc #1 Debian 3.16.51-3+deb8u1 (2018-01-08) ppc 
7447A, altivec supported PowerMac10,1 GNU/Linux

I will test the Gentoo system next.

My Mac Mini G4 — PowerPC 7447a — is happy.  Many thanks.

Bug#886120: FTBFS: chown: cannot access '..._cgraph.dot': No such file or directory

[Adam Borowski]

On Sun, Jan 14, 2018 at 02:25:44AM +0100, Adam Borowski wrote:
> Sorry for the delay.  I haven't found the cause yet, but here's my progress:
> 
> It looks like kernel version is a factor.  All my test machines run current
> 4.15-rc, so that was common to all builds.
> 
> On amd64, with today's unstable:
> ✓ 4.9.76, self-compiled
> ✗ 4.14.13, self-compiled
> ✗ linux-image-4.14.0-3-amd64 (4.14.12-2)
> ✗ 4.15.0-rc7-debug-00137, self-compiled

Scratch this... turns out it's random.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...

Bug#856048: Hello,

[mallory genest]

--
 Hello Dear

I have a business proposal to present to you please reply me for more 
info.




Regards
Melisa Mehmet

Bug#887095: marked as done (mali-midgard-driver: missing B-D: chrpath)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 04:05:05 +
with message-id 
and subject line Bug#887095: fixed in mali-midgard-driver 0.1-2
has caused the Debian Bug report #887095,
regarding mali-midgard-driver: missing B-D: chrpath
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mali-midgard-driver
Version: 0.1-1
Severity: serious
Justification: fails to build from source

Hi,

mali-midgard-driver FTBFS due to a missing Build-Depends: chrpath:

[...]
install -d debian/.debhelper/generated/mali-t76x-wayland-driver
find debian -type f -name "*.so" | xargs -t -n 1 chrpath -d
chrpath -d 
debian/mali-t76x-wayland-driver/usr/lib/arm-linux-gnueabihf/liboffline_compiler_api.so
 
/usr/bin/xargs: chrpath: No such file or directory
debian/rules:10: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 127
make[1]: Leaving directory '/build/mali-midgard-driver-0.1'
debian/rules:7: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


Andreas


mali-midgard-driver_0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mali-midgard-driver
Source-Version: 0.1-2

We believe that the bug you reported is fixed in the latest version of
mali-midgard-driver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wookey  (supplier of updated mali-midgard-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Jan 2018 19:42:02 +
Source: mali-midgard-driver
Binary: mali-t62x-fbdev-driver mali-t62x-wayland-driver 
mali-t62x-wayland-fbdev-driver mali-t62x-fbdev-wayland-driver 
mali-t62x-x11-driver mali-t76x-fbdev-driver mali-t76x-x11-driver 
mali-t76x-wayland-driver
Architecture: source armhf
Version: 0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 mali-t62x-fbdev-driver - Mali binary framebuffer driver for t62x
 mali-t62x-fbdev-wayland-driver - Mali binary fbdev-wayland driver for t62x
 mali-t62x-wayland-driver - Mali binary wayland driver for t62x
 mali-t62x-wayland-fbdev-driver - Mali binary wayland driver for t62x
 mali-t62x-x11-driver - Mali binary x11 driver for t62x
 mali-t76x-fbdev-driver - Mali binary framebuffer driver for t76x
 mali-t76x-wayland-driver - Mali binary wayland driver for t76x
 mali-t76x-x11-driver - Mali binary x11 driver for t76x
Closes: 887095
Changes:
 mali-midgard-driver (0.1-2) unstable; urgency=medium
 .
   * Add missing chrpath build-dep Closes: #887095
   * Clarify non-free status in copyright file
Checksums-Sha1:
 92d54d0f77aa0bdda23f3b76edcdce30b949ee88 2565 mali-midgard-driver_0.1-2.dsc
 6fb7c15fef28cdcafe53810ff8fae4bb6201360a 8124 
mali-midgard-driver_0.1-2.debian.tar.xz
 b69fd2a209132fc67594a88eda077194bca7232f 8060 
mali-midgard-driver_0.1-2_armhf.buildinfo
 1e1b40a7cb4c962c2b025a9689101f58a5b85436 654104 
mali-t62x-fbdev-driver-dbgsym_0.1-2_armhf.deb
 eeed6addadf83050d5744f9253f67b5a236f58c9 6864692 
mali-t62x-fbdev-driver_0.1-2_armhf.deb
 1c17512befb5fc42b0ee12fb765e1a0d5d731d3d 655068 
mali-t62x-wayland-driver-dbgsym_0.1-2_armhf.deb
 bad342127b85bac44691a336795d7279e179afc9 6865392 
mali-t62x-wayland-driver_0.1-2_armhf.deb
 aa9addaa4ee10ad95258005d1956af22ba227b64 683984 
mali-t62x-x11-driver-dbgsym_0.1-2_armhf.deb
 9b73b5acba4ab644db5d00e38e6011936d9479ec 7673164 
mali-t62x-x11-driver_0.1-2_armhf.deb
 92d3cd0a4752b988cdfc34d01b9f812eab738359 715548 
mali-t76x-fbdev-driver-dbgsym_0.1-2_armhf.deb
 5c5d9c28349968181e0608d983c5d5ea3d0434e4 7940680 
mali-t76x-fbdev-driver_0.1-2_armhf.deb
 0d61aee5bc9600824fc8b937ca41b9c0469c62ec 686608 
mali-t76x-wayland-driver-dbgsym_0.1-2_armhf.deb
 edf3a6723e79802608fa6a556d196a2413872b8c 7687356 
mali-t76x-wayland-driver_0.1-2_armhf.deb
 

Bug#845949: marked as done (guake: depends on python-gnome2 which deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 02:50:21 +
with message-id 
and subject line Bug#845949: fixed in guake 3.0.0.b2-1
has caused the Debian Bug report #845949,
regarding guake: depends on python-gnome2 which deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guake
Version: 0.8.7-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

guake depends on python-gnome2 or python-gconf, or has a
build-dependency on one those packages. Those are built from
gnome-python which is long deprecated and going to be removed from
the archive. guake should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove gnome-python this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Source: guake
Source-Version: 3.0.0.b2-1

We believe that the bug you reported is fixed in the latest version of
guake, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Echeverry  (supplier of updated guake package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Jan 2018 18:20:21 -0500
Source: guake
Binary: guake
Architecture: source
Version: 3.0.0.b2-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry 
Changed-By: Daniel Echeverry 
Description:
 guake  - Drop-down terminal for GNOME Desktop Environment
Closes: 721554 790176 829969 845949
Changes:
 guake (3.0.0.b2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #829969)
 + Guake gtk3 now is in unstable. (Closes: #721554)
   * debian/copyright
 + Extend copyright holder years.
   + Update path to simplegladeapp.py file.
   * debian/control
 + Bump Standards-Version 4.1.3 (no changes).
 + Remove gconf2, intltool, libgconf2-dev, libgtk2.0-dev,
   libxml-parser-perl, pkg-config, python, python-dev,
   python-gnome2, python-gtk2-dev, python-vte, python-xdg
   from B-D (Closes: #790176, #845949).
 + Add python3-all, python3-pbr, python3-setuptools, libglib2.0-dev,
   python3-gi to B-D.
 + Change debhelper to 11 in B-D.
 + Update X-Python3-Version to >= 3.0.
 + remove gconf2, libgtk2.0-0, notification-daemon,
   python, python-dbus, python-gconf, python-glade2,
   python-keybinder, python-notify, python-vte,
   python-xdg from Depends.
 + Add libgtk-3-dev, libkeybinder-3.0-0, gir1.2-keybinder-3.0,
   libvte-common, libvte-2.91-dev, python3, python3-pbr, libutempter0
   ${python3:Depends} to depends.
 * debian/patches
   + Refresh 01_fix_desktop_file.diff patch.
   + Add 02_use_correct_data_path.diff path.
 + Use path where data files was installed.
   + Add 03_remove_description_field_from_setup.diff patch.
 + Because README.rst have non-valid characters and causes FTBFS.
 * debian/rules
   + Rewritten to build with pybuild and python3.
 * Add debian/guake.install file.
   + Install data files to /usr/share.
 * Add debian/guake.links.
 * debian/watch
   + Use HTTPS in url.
 * debian/compat
   + Switch compat level 10 to 11.
 * Add d/guake.1 file
   + Upstream remove from tarball.
   + Add guake.manpages file.
 * debian/changelog
   + Remove some whitespaces.
 * Remove guake.lintian-override file.
   + Because isn't necessary
 * Update *.prerm and postinst scripts.
 * Update debian/guake.docs file.
Checksums-Sha1:
 b78b733dea65df2752c297b695b622f3e9a507a4 

Bug#790176: marked as done (guake: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 02:50:21 +
with message-id 
and subject line Bug#790176: fixed in guake 3.0.0.b2-1
has caused the Debian Bug report #790176,
regarding guake: depends on vte which is deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
790176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guake
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

Hi,

guake depends on python-vte / libvte9, which are deprecated in favor
of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove src:vte
from the archive. guake should switch to the new vte version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Source: guake
Source-Version: 3.0.0.b2-1

We believe that the bug you reported is fixed in the latest version of
guake, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 790...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Echeverry  (supplier of updated guake package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Jan 2018 18:20:21 -0500
Source: guake
Binary: guake
Architecture: source
Version: 3.0.0.b2-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry 
Changed-By: Daniel Echeverry 
Description:
 guake  - Drop-down terminal for GNOME Desktop Environment
Closes: 721554 790176 829969 845949
Changes:
 guake (3.0.0.b2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #829969)
 + Guake gtk3 now is in unstable. (Closes: #721554)
   * debian/copyright
 + Extend copyright holder years.
   + Update path to simplegladeapp.py file.
   * debian/control
 + Bump Standards-Version 4.1.3 (no changes).
 + Remove gconf2, intltool, libgconf2-dev, libgtk2.0-dev,
   libxml-parser-perl, pkg-config, python, python-dev,
   python-gnome2, python-gtk2-dev, python-vte, python-xdg
   from B-D (Closes: #790176, #845949).
 + Add python3-all, python3-pbr, python3-setuptools, libglib2.0-dev,
   python3-gi to B-D.
 + Change debhelper to 11 in B-D.
 + Update X-Python3-Version to >= 3.0.
 + remove gconf2, libgtk2.0-0, notification-daemon,
   python, python-dbus, python-gconf, python-glade2,
   python-keybinder, python-notify, python-vte,
   python-xdg from Depends.
 + Add libgtk-3-dev, libkeybinder-3.0-0, gir1.2-keybinder-3.0,
   libvte-common, libvte-2.91-dev, python3, python3-pbr, libutempter0
   ${python3:Depends} to depends.
 * debian/patches
   + Refresh 01_fix_desktop_file.diff patch.
   + Add 02_use_correct_data_path.diff path.
 + Use path where data files was installed.
   + Add 03_remove_description_field_from_setup.diff patch.
 + Because README.rst have non-valid characters and causes FTBFS.
 * debian/rules
   + Rewritten to build with pybuild and python3.
 * Add debian/guake.install file.
   + Install data files to /usr/share.
 * Add debian/guake.links.
 * debian/watch
   + Use HTTPS in url.
 * debian/compat
   + Switch compat level 10 to 11.
 * Add d/guake.1 file
   + Upstream remove from tarball.
   + Add guake.manpages file.
 * debian/changelog
   + Remove some whitespaces.
 * Remove guake.lintian-override file.
   + Because isn't necessary
 * Update *.prerm and postinst scripts.
 * Update debian/guake.docs file.
Checksums-Sha1:
 b78b733dea65df2752c297b695b622f3e9a507a4 1936 guake_3.0.0.b2-1.dsc
 9b4256191d980883b0b8795f7cbb1dc34a0e3c55 276707 guake_3.0.0.b2.orig.tar.gz
 0e7fecea86d02ccb8e5920dcfebcdb5cab9e530f 7068 guake_3.0.0.b2-1.debian.tar.xz
 85777ea0bc670ff859fdb12b54493ca5adb36c2d 

Processed: Re: Bug#887040: RFS: reptyr/0.6.2-1.1 [RC] [NMU]

[Debian Bug Tracking System]

Processing control commands:

> block 853640 by -1
Bug #853640 [src:reptyr] reptyr: ftbfs with GCC-7
853640 was not blocked by any bugs.
853640 was not blocking any bugs.
Added blocking bug(s) of 853640: 887040
> tag 853640 pending
Bug #853640 [src:reptyr] reptyr: ftbfs with GCC-7
Added tag(s) pending.

-- 
853640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853640
887040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886120: FTBFS: chown: cannot access '..._cgraph.dot': No such file or directory

[Adam Borowski]

On Tue, Jan 09, 2018 at 10:42:19PM +0530, Vasudev Kamath wrote:
> Control: tag -1 +moreinfo +unreproducible
> 
> Adam Borowski  writes:
> > Source: ctpp2
> > Version: 2.8.3-23
> >
> > Hi!
> > I'm afraid your package fails to build:
> >
> > dh_fixperms -pctpp2-doc 
> > chown: cannot access 
> > 'debian/ctpp2-doc/usr/share/doc/ctpp2-doc/html/a01323_acf0137f96d20b71a2e2e18b489d1a33e_cgraph.dot':
> >  No such file or directory
> > chown: cannot access 
> > 'debian/ctpp2-doc/usr/share/doc/ctpp2-doc/html/inherit_graph_65.md5': No 
> > such file or directory
> > dh_fixperms: find debian/ctpp2-doc -true -print0 2>/dev/null | xargs -0r 
> > chown --no-dereference 0:0 returned exit code 123
> > dh_fixperms: Aborting due to earlier error
> >
> > Tried on armhf amd64.  Log attached.
> 
> Could not reproduce on amd64, it built fine. Was not able to check on
> armhf yet. Attaching my build log for reference.

Sorry for the delay.  I haven't found the cause yet, but here's my progress:

It looks like kernel version is a factor.  All my test machines run current
4.15-rc, so that was common to all builds.

On amd64, with today's unstable:
✓ 4.9.76, self-compiled
✗ 4.14.13, self-compiled
✗ linux-image-4.14.0-3-amd64 (4.14.12-2)
✗ 4.15.0-rc7-debug-00137, self-compiled

You do run some version of 4.14.0-3-amd64, though.  Hrm...  Lemme poke more.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...

Bug#885633: marked as done (gnome-chemistry-utils: Please drop Build-Depends on rarian-compat)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 00:49:47 +
with message-id 
and subject line Bug#885633: fixed in gnome-chemistry-utils 0.14.17-1
has caused the Debian Bug report #885633,
regarding gnome-chemistry-utils: Please drop Build-Depends on rarian-compat
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-chemistry-utils
Version: 0.14.15-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs rarian
Tags: sid buster patch

scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too. More
importantly, it doesn't seem to be needed at all. yelp can easily
display Docbook help files without any .omf files.

We do not intend to ship rarian in Debian 10 "Buster". Therefore,
please drop "rarian-compat | scrollkeeper" from gnome-system-tools'
Build-Depends. You'll also need to add --disable-scrollkeeper to the
configure flags.

I'm not actually attaching a patch, but the fix seems pretty trivial
here.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-chemistry-utils
Source-Version: 0.14.17-1

We believe that the bug you reported is fixed in the latest version of
gnome-chemistry-utils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated gnome-chemistry-utils 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jan 2018 00:50:37 +0100
Source: gnome-chemistry-utils
Binary: libgcu0v5 gcu-bin gcu-plugin gcrystal gchempaint
Architecture: source amd64
Version: 0.14.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Description:
 gchempaint - 2D chemical structures editor for the GNOME2 desktop
 gcrystal   - lightweight crystal structures visualizer
 gcu-bin- GNOME chemistry utils (helper applications)
 gcu-plugin - GNOME chemistry utils (browser plugin)
 libgcu0v5  - GNOME chemistry utils (library)
Closes: 845141 885633
Changes:
 gnome-chemistry-utils (0.14.17-1) unstable; urgency=medium
 .
   * New upstream release.
 - Removed 'weak bond' feature from gchempaint (closes: #845141).
   * debian/control (Standards-Version): Bumped to 4.1.3.
 (Build-Depends): Drop rarian/scrollkeeper (closes: #885633).
 (Vcs-Browser): Use secure URL.
   * debian/copyright: Minor updates.
   * debian/gchempaint.install, debian/gcrystal.install,
 debian/gcu-bin.install: Fixed appstream-metadata-in-legacy-location.
   * debian/gchempaint.menu, debian/gcrystal.menu,
 debian/gcu-bin.menu: Removed in accordance to policy.
   * debian/rules: Enable hardening.
 (override_dh_auto_install): Added to fix lintian warning
 appstream-metadata-in-legacy-location.
 path in the added override_dh_auto_install target.
 (override_dh_auto_configure): Disable scrollkeeper.
   * debian/watch: Fixed.
Checksums-Sha1:
 6b6b3a0d849aa26c91a154a9eccbbe40ab021c68 3174 
gnome-chemistry-utils_0.14.17-1.dsc
 d9fa7e80d411f830e251a0d8e6abd3859e897c18 6712457 
gnome-chemistry-utils_0.14.17.orig.tar.bz2
 05e41fe0fff0398915f2343e2eb3794bae418d7b 241 
gnome-chemistry-utils_0.14.17.orig.tar.bz2.asc
 a862a327f3de73002c1db85d91ace4e3f403bfda 21128 
gnome-chemistry-utils_0.14.17-1.debian.tar.xz
 e99534c3eaeb432eabb833f45b5cbf09434b61fe 2304584 
gchempaint-dbgsym_0.14.17-1_amd64.deb
 3df46bb63ad56d514c8a6e10b93388bf1f122524 1592000 gchempaint_0.14.17-1_amd64.deb
 11b77ba6b1b6b96c8745d666484e938c8763c145 146460 
gcrystal-dbgsym_0.14.17-1_amd64.deb
 f958c03e2b72cda6a26a9794d6f073934dc926f2 472828 gcrystal_0.14.17-1_amd64.deb
 2cf740a32f5bd3f58ec6636c44b20b7799691488 660176 
gcu-bin-dbgsym_0.14.17-1_amd64.deb
 1ac4cd2e07e8b73d0c2d7ad32ccf256668d76776 1086600 gcu-bin_0.14.17-1_amd64.deb
 

Bug#885826: marked as done (linux-igd: /etc/init.d/linux-igd requires $network)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 00:50:03 +
with message-id 
and subject line Bug#885826: fixed in linux-igd 1.0+cvs20070630-6
has caused the Debian Bug report #885826,
regarding linux-igd: /etc/init.d/linux-igd requires $network
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-igd
Version: 1.0+cvs20070630-5
Severity: serious
Tags: patch
Justification: Policy 9.3.2

/etc/init.d/linux-igd requires $network or it will fail to start.

--- linux-igd.dist  2017-12-28 22:07:28.512055702 -0800
+++ linux-igd   2016-09-22 09:01:57.0 -0700
@@ -1,8 +1,8 @@
 #! /bin/sh
 ### BEGIN INIT INFO
 # Provides:  linux-igd
-# Required-Start:$remote_fs $syslog
-# Required-Stop: $remote_fs $syslog
+# Required-Start:$remote_fs $syslog $network
+# Required-Stop: $remote_fs $syslog $network
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 # Short-Description: UPnP Internet Gateway Device

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

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

Versions of packages linux-igd depends on:
ii  iptables  1.6.1-2+b1
ii  libc6 2.25-5
ii  libupnp6  1:1.6.24-4
ii  lsb-base  9.20170808

linux-igd recommends no packages.

linux-igd suggests no packages.

-- Configuration Files:
/etc/default/linux-igd changed [not included]
/etc/init.d/linux-igd changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux-igd
Source-Version: 1.0+cvs20070630-6

We believe that the bug you reported is fixed in the latest version of
linux-igd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated linux-igd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jan 2018 01:25:32 +0100
Source: linux-igd
Binary: linux-igd
Architecture: source
Version: 1.0+cvs20070630-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 linux-igd  - Linux UPnP Internet Gateway Device
Closes: 885826
Changes:
 linux-igd (1.0+cvs20070630-6) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to the QA group.
   * dh 11.
   * Make the init script require $network; patch by Nye Liu (Closes: #885826)
   * Typo in README.Debian: "Conections".
   * R³.
Checksums-Sha1:
 4094f71a41dd1482df7fa2aa885c2a178cd443bc 1873 linux-igd_1.0+cvs20070630-6.dsc
 cc075b87c6d5b3a92db0eaac2be6d459fb594b1f 25440 
linux-igd_1.0+cvs20070630-6.debian.tar.xz
 9c85405386d5aa33c97f3fa459c48e025953fddb 5402 
linux-igd_1.0+cvs20070630-6_source.buildinfo
Checksums-Sha256:
 16cbe5cd558e4f4c81ad0c4e18d8d74ed6607c5850c2605db7ec0b209523bde2 1873 
linux-igd_1.0+cvs20070630-6.dsc
 f610395befcf373d4b864c843f72d1bd451ec52ce62a676052cf8f5b9acade8e 25440 
linux-igd_1.0+cvs20070630-6.debian.tar.xz
 cca222cdfd5f9b7511d92be4b11d952dcb33f1c6ff9bd6dabb7a524392ea3ea1 5402 
linux-igd_1.0+cvs20070630-6_source.buildinfo
Files:
 442518d42c3fa4d27058df13f8ba88dd 1873 net optional 
linux-igd_1.0+cvs20070630-6.dsc
 6aecafee54c17adcd06658fabf3d1c6e 25440 net optional 
linux-igd_1.0+cvs20070630-6.debian.tar.xz
 6e199daa5c4bb15090374988dd3f27a6 5402 net optional 
linux-igd_1.0+cvs20070630-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlpao4oUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH60cQ/+OZK6L3yWZeCvUwCdQk92sZ0O4+RC
ROnBs99XTq0moMMQ7IS6M23b8V8AnBjujI0D1Mq/g/tYzgpGi2P3bRPCwp9R8fTY

Bug#886901: base-files: FTBFS: cannot remove '/etc/debian_version'

[Santiago Vila]

> [ snipped wonderful explanation of debhelper internals
>   regarding those debian/rules targets ]
  
Thanks a lot, Niels!

(This should now be fixed in base-files 10.1)

Bug#886901: marked as done (base-files: FTBFS: cannot remove '/etc/debian_version')

[Debian Bug Tracking System]

Your message dated Sun, 14 Jan 2018 00:19:16 +
with message-id 
and subject line Bug#886901: fixed in base-files 10.1
has caused the Debian Bug report #886901,
regarding base-files: FTBFS: cannot remove '/etc/debian_version'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
886901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: base-files
Version: 10
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
dh build
  dh_update_autotools_config
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/base-files-10'
sh debian/check-md5sum-etc profile
sed -e "s

Processed: Re: activity-log-manager: Missing dependency against python-zeitgeist

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #881438 {Done: Laurent Bigonville } 
[activity-log-manager] activity-log-manager: Missing dependency against 
python-zeitgeist
Added tag(s) pending.

-- 
881438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#881438: activity-log-manager: Missing dependency against python-zeitgeist

[Andreas Beckmann]

Followup-For: Bug #881438
Control: tag -1 pending

Hi,

this is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru activity-log-manager-0.8.0/debian/changelog 
activity-log-manager-0.8.0/debian/changelog
--- activity-log-manager-0.8.0/debian/changelog 2015-08-18 17:28:36.0 
+0200
+++ activity-log-manager-0.8.0/debian/changelog 2018-01-14 00:57:20.0 
+0100
@@ -1,3 +1,17 @@
+activity-log-manager (0.8.0-1.2~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 14 Jan 2018 00:57:20 +0100
+
+activity-log-manager (0.8.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dependency against python-zeitgeist (Closes: #881438)
+
+ -- Laurent Bigonville   Sun, 12 Nov 2017 18:05:38 +0100
+
 activity-log-manager (0.8.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru activity-log-manager-0.8.0/debian/control 
activity-log-manager-0.8.0/debian/control
--- activity-log-manager-0.8.0/debian/control   2015-08-18 17:30:06.0 
+0200
+++ activity-log-manager-0.8.0/debian/control   2017-11-12 18:04:24.0 
+0100
@@ -17,7 +17,8 @@
  python,
  zeitgeist-core (>= 0.7~) | zeitgeist (>= 0.7~),
  python-gtk2,
- python-cairo
+ python-cairo,
+ python-zeitgeist
 Description: blacklist configuration user interface for Zeitgeist
  Zeitgeist is a service which logs the user's activities and events (files
  opened, websites visited, conversations held with other people, etc.) and

Bug#867431: python3-hacking: incorrect dependencies

[Andreas Beckmann]

Followup-For: Bug #867431
Control: tag -1 pending

Hi,

this is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-hacking-0.11.0/debian/changelog 
python-hacking-0.11.0/debian/changelog
--- python-hacking-0.11.0/debian/changelog  2016-10-04 13:21:49.0 
+0200
+++ python-hacking-0.11.0/debian/changelog  2018-01-14 00:46:21.0 
+0100
@@ -1,3 +1,17 @@
+python-hacking (0.11.0-2.1~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 14 Jan 2018 00:46:21 +0100
+
+python-hacking (0.11.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the python3-hacking dependencies. (Closes: #867431)
+
+ -- Adrian Bunk   Tue, 17 Oct 2017 09:38:55 +0300
+
 python-hacking (0.11.0-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-hacking-0.11.0/debian/control 
python-hacking-0.11.0/debian/control
--- python-hacking-0.11.0/debian/control2016-10-04 13:21:49.0 
+0200
+++ python-hacking-0.11.0/debian/control2017-10-17 08:38:53.0 
+0200
@@ -55,13 +55,13 @@
 
 Package: python3-hacking
 Architecture: all
-Depends: pyflakes,
+Depends: pyflakes3,
  python3-flake8 (>= 3.0.0),
  python3-pbr (>= 1.8),
  python3-pep8 (>= 1.5.7),
  python3-six (>= 1.9.0),
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
 Recommends: ${python3:Recommends},
 Description: Flake8 OpenStack Hacking Guidelines Enforcement plugins - Python 
3.x
  Hacking is a set of flake8 plugins that test and enforce the OpenStack Style

Processed: Re: python3-hacking: incorrect dependencies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867431 {Done: Adrian Bunk } [python3-hacking] 
python3-hacking: incorrect dependencies
Added tag(s) pending.

-- 
867431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867439: python3-mimeparse: missing dependencies

[Andreas Beckmann]

Followup-For: Bug #867439
Control: tag -1 pending

Hi,

this is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-mimeparse-0.1.4/debian/changelog 
python-mimeparse-0.1.4/debian/changelog
--- python-mimeparse-0.1.4/debian/changelog 2016-12-26 20:13:35.0 
+0100
+++ python-mimeparse-0.1.4/debian/changelog 2018-01-14 00:37:15.0 
+0100
@@ -1,3 +1,17 @@
+python-mimeparse (0.1.4-3.1~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 14 Jan 2018 00:37:15 +0100
+
+python-mimeparse (0.1.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the python3-mimeparse dependencies. (Closes: #867439)
+
+ -- Adrian Bunk   Tue, 17 Oct 2017 09:49:45 +0300
+
 python-mimeparse (0.1.4-3) unstable; urgency=medium
 
   [ Mathias Ertl ]
diff -Nru python-mimeparse-0.1.4/debian/control 
python-mimeparse-0.1.4/debian/control
--- python-mimeparse-0.1.4/debian/control   2016-12-26 20:13:35.0 
+0100
+++ python-mimeparse-0.1.4/debian/control   2017-10-17 08:49:28.0 
+0200
@@ -25,7 +25,7 @@
 
 Package: python3-mimeparse
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Parse mime-types and quality parameters - python 3.x
  This module provides basic functions for parsing mime-type names and
  matching them against a list of media-ranges.

Processed: Re: python3-mimeparse: missing dependencies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867439 {Done: Adrian Bunk } [python3-mimeparse] 
python3-mimeparse: missing dependencies
Added tag(s) pending.

-- 
867439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886998: List of sigs for microcode with regressions

[Henrique de Moraes Holschuh]

The VMWare KB52345 article at:
https://kb.vmware.com/s/article/52345

Includes an _incomplete_ list of signatures for the microcode updates
that are problematic in release 20180108:

Processor name
(non-exhaustive) signature   stepping name

Intel Xeon E3-1200-v3,
Intel i3-4300,
Intel i5-4500-TE,
Intel i7-4700-EQ:0x000306C3  C0

Intel Xeon E5-1600-v3,
Intel Xeon E5-2400-v3,
Intel Xeon E5-2600-v3,
Intel Xeon E5-4600-v3:   0x000306F2  C0/C1, M0/M1, R1/R2

Intel Xeon E7-8800/4800-v3:  0x000306F4  E0

Intel Xeon E3-1200-v4:   0x00040671  G0

ntel Xeon E5-1600-v4,
Intel Xeon E5-2600-v4,
Intel Xeon E5-4600-v4:   0x000406F1  B0/M0/R0

Intel Xeon E7-8800/4800-v4:  0x000406F1  B0/M0/R0
Intel Xeon D-1500:   0x00050663  V2

This list is only relevant for server processors.  Desktop/mobile
processors were not included, and we cannot assume anything about
updates for such processors that were deployed in release 20180108.

-- 
  Henrique Holschuh

Bug#867433: python3-hkdf: missing dependencies

[Andreas Beckmann]

Followup-For: Bug #867433
Control: tag -1 pending

Hi,

this is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-hkdf-0.0.3/debian/changelog python-hkdf-0.0.3/debian/changelog
--- python-hkdf-0.0.3/debian/changelog  2016-06-04 23:06:45.0 +0200
+++ python-hkdf-0.0.3/debian/changelog  2018-01-14 00:25:36.0 +0100
@@ -1,3 +1,24 @@
+python-hkdf (0.0.3-3~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 14 Jan 2018 00:25:36 +0100
+
+python-hkdf (0.0.3-3) unstable; urgency=medium
+
+  * QA upload.
+  * Fix the python3-hkdf dependencies. (Closes: #867433)
+
+ -- Adrian Bunk   Thu, 06 Jul 2017 19:16:59 +0300
+
+python-hkdf (0.0.3-2) unstable; urgency=medium
+
+  * Add missing URL to package descriptions.  closes: #864149.
+  * Set maintainer to Debian QA Group.
+
+ -- Clint Adams   Sun, 04 Jun 2017 10:59:31 -0400
+
 python-hkdf (0.0.3-1) unstable; urgency=low
 
   * Initial release.
diff -Nru python-hkdf-0.0.3/debian/control python-hkdf-0.0.3/debian/control
--- python-hkdf-0.0.3/debian/control2016-06-04 23:21:51.0 +0200
+++ python-hkdf-0.0.3/debian/control2017-07-06 18:16:52.0 +0200
@@ -1,5 +1,5 @@
 Source: python-hkdf
-Maintainer: Clint Adams 
+Maintainer: Debian QA Group 
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9),
@@ -18,6 +18,7 @@
 Depends: ${misc:Depends}, ${python:Depends}
 Description: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
  This module implements the HMAC Key Derivation function, defined at
+ http://tools.ietf.org/html/draft-krawczyk-hkdf-01
  .
  There are two interfaces: a functional interface, with separate
  extract and expand functions as defined in the draft RFC, and a
@@ -25,9 +26,10 @@
 
 Package: python3-hkdf
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
  This module implements the HMAC Key Derivation function, defined at
+ http://tools.ietf.org/html/draft-krawczyk-hkdf-01
  .
  There are two interfaces: a functional interface, with separate
  extract and expand functions as defined in the draft RFC, and a

Processed: Re: python3-hkdf: missing dependencies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867433 {Done: Adrian Bunk } [python3-hkdf] python3-hkdf: 
missing dependencies
Added tag(s) pending.

-- 
867433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867457: python3-spake2: missing dependencies

[Andreas Beckmann]

Followup-For: Bug #867457
Control: tag -1 pending

This is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-spake2-0.7/debian/changelog python-spake2-0.7/debian/changelog
--- python-spake2-0.7/debian/changelog  2016-06-08 19:05:58.0 +0200
+++ python-spake2-0.7/debian/changelog  2018-01-14 00:16:34.0 +0100
@@ -1,3 +1,18 @@
+python-spake2 (0.7-3~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 14 Jan 2018 00:16:34 +0100
+
+python-spake2 (0.7-3) unstable; urgency=high
+
+  * QA upload.
+  * Set maintainer to Debian QA Group. (see #833947)
+  * Fix the python3-spake2 dependencies. (Closes: #867457)
+
+ -- Adrian Bunk   Thu, 06 Jul 2017 20:32:40 +0300
+
 python-spake2 (0.7-2) unstable; urgency=medium
 
   * Add src/spake2/six.py to debian/copyright.
diff -Nru python-spake2-0.7/debian/control python-spake2-0.7/debian/control
--- python-spake2-0.7/debian/control2016-06-05 01:34:25.0 +0200
+++ python-spake2-0.7/debian/control2017-07-06 19:32:40.0 +0200
@@ -1,5 +1,5 @@
 Source: python-spake2
-Maintainer: Clint Adams 
+Maintainer: Debian QA Group 
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9),
@@ -40,7 +40,7 @@
 
 Package: python3-spake2
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: SPAKE2 password-authenticated key exchange (pure python)
  This library implements the SPAKE2 password-authenticated key
  exchange ("PAKE") algorithm. This allows two parties, who share a

Processed: Re: python3-spake2: missing dependencies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867457 {Done: Adrian Bunk } [python3-spake2] 
python3-spake2: missing dependencies
Added tag(s) pending.

-- 
867457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867450: python3-pyperclip: missing python3 dependency

[Andreas Beckmann]

Followup-For: Bug #867450
Control: tag -1 pending

This will be fixed in the next stretch point release with the
attached patch.


Andreas
diff -Nru python-pyperclip-1.5.27/debian/changelog 
python-pyperclip-1.5.27/debian/changelog
--- python-pyperclip-1.5.27/debian/changelog2016-07-01 17:47:10.0 
+0200
+++ python-pyperclip-1.5.27/debian/changelog2018-01-13 23:56:47.0 
+0100
@@ -1,3 +1,16 @@
+python-pyperclip (1.5.27-3~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sat, 13 Jan 2018 23:56:47 +0100
+
+python-pyperclip (1.5.27-3) unstable; urgency=medium
+
+  * Fix typo in Depends for python3 package (Closes: #867450)
+
+ -- Sebastien Delafond   Fri, 07 Jul 2017 10:38:02 +0200
+
 python-pyperclip (1.5.27-2) unstable; urgency=medium
 
   * Relax dependencies on python QT libraries (Closes: #816821)
diff -Nru python-pyperclip-1.5.27/debian/control 
python-pyperclip-1.5.27/debian/control
--- python-pyperclip-1.5.27/debian/control  2016-07-01 17:47:10.0 
+0200
+++ python-pyperclip-1.5.27/debian/control  2017-07-07 10:38:02.0 
+0200
@@ -20,7 +20,7 @@
 
 Package: python3-pyperclip
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, xclip | xsel | 
python3-pyqt4
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, xclip | xsel 
| python3-pyqt4
 Description: Cross-platform clipboard module for Python3
  This module is a cross-platform Python3 module for copy and paste clipboard
  functions. Currently only handles plaintext.

Processed: Re: python3-pyperclip: missing python3 dependency

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #867450 {Done: Sebastien Delafond } [python3-pyperclip] 
python3-pyperclip: missing python3 dependency
Added tag(s) pending.

-- 
867450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887072: marked as done (src:libratbag: FTBFS with UnicodeDecodeError)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 22:34:25 +
with message-id 
and subject line Bug#887072: fixed in libratbag 0.9.901-2
has caused the Debian Bug report #887072,
regarding src:libratbag: FTBFS with UnicodeDecodeError
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libratbag
Version: 0.9.901-1
Severity: serious
Justification: FTBFS

Dear Maintainer,

Builds fail with

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 4836: 
ordinal not in range(128)

Regards,

Stephen


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

Kernel: Linux 4.9.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libratbag
Source-Version: 0.9.901-2

We believe that the bug you reported is fixed in the latest version of
libratbag, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libratbag package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jan 2018 23:15:49 +0100
Source: libratbag
Binary: liblur3 liblur-dev lur-command libratbag-tools ratbagd
Architecture: source
Version: 0.9.901-2
Distribution: experimental
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 liblur-dev - Logitech Unifying Receiver access library - dev files
 liblur3- Logitech Unifying Receiver access library
 libratbag-tools - configuration tools for gaming mice (transitional package)
 lur-command - Logitech Unifying Receiver control tool
 ratbagd- D-Bus daemon handling mouse configuration
Closes: 887072
Changes:
 libratbag (0.9.901-2) experimental; urgency=medium
 .
   * Enforce a UTF-8 locale (the Python source uses UTF-8). Closes:
 #887072.
Checksums-Sha1:
 6ed2a511d20ad920cec05acd3ea5297fa2e8ed72 2299 libratbag_0.9.901-2.dsc
 0163541f4d96339c5e05926ed591450d3ebf9631 4856 libratbag_0.9.901-2.debian.tar.xz
 6c5b60c07e750741cbd8e18b4359492e29ec5ecd 8637 
libratbag_0.9.901-2_source.buildinfo
Checksums-Sha256:
 85ea8b66ba6d6b5295f794352ee4fd3151e4d02f7b3832528eb46c9ffebec4b3 2299 
libratbag_0.9.901-2.dsc
 981a1956b0cdaefd3af1c63352d2ff7823177afa37f6e007aa5daf5583544671 4856 
libratbag_0.9.901-2.debian.tar.xz
 4e8a7c163db22f09e2c197e301f1682636a9fce381a3131fa2960e47550fbc4a 8637 
libratbag_0.9.901-2_source.buildinfo
Files:
 d0214fcbc9ec7949d408acd52ecab261 2299 libs optional libratbag_0.9.901-2.dsc
 4cf3a5bde74b6b13f992d5dc8ccbbe03 4856 libs optional 
libratbag_0.9.901-2.debian.tar.xz
 c1aa235fd0c7dddb9e21845e94520cb7 8637 libs optional 
libratbag_0.9.901-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlpahTwACgkQgNMC9Yht
g5yaUg/+PG/t/OdrEg7QMwuFuzO0DFbEJCbz4d3wSCpeSXgEu00QWBaoVrZgaUtP
d6LaW+zZDVX94aWgyYuAMS/Qlnsnm+RzzzHLTyWp6WEUpAdJ6tKv7vS3ZNH3Ka/X
SJqGIYk/mgcuZBGgrtYF0mfNGYM7+z3OOIXg0hcAC2RQLScrZOddw4zUhQJxLKfT
gp9RJgWPDWun6oWRbCI8LNbHBXoYpm4DtNE9llgRJVCc4BT1dln+vDabm/DpeiKK
kMBytoccsYhvK1O0KkgdylDOvzluVkdI+kuB1hPyw8vf48yCgfFAZR3q2irtnYKz
IavxOAQfzeaRy1Aes4xOaRQyumS6q6bzademfGe85dCr4kR7dXbLBFDIMR8XDvtU
R0ijAXU9kJ4fNI5HGYin6uqpR33rHXWCE6ZEe8n8f5P8jb1cOOYlWFKB8QflqOC9
dtyv1mbqQEiuClJh16IaJilq2fySpPDnBPQ4e4QyZGc0/kKjemtZv1eb8Jn7XvSF
wp2D6gxciFm+nADwjUV4lOPnIlHt08A3TYPebcfZdWHi/C6KiMOk5QGUJloEKbLs
Y41yBr5nPGqZGMvP/bBrU8uYBf8ZNbb6DAIXDnJuqSVSeVTrh20NZwR3ammRsD4I
uyl3s9GuIPYutipbM77FZyhrtBP9ksjfDkPhXucCeiP1SjZ63Ms=
=aU5u
-END PGP SIGNATURE End Message ---

Bug#886901: base-files: FTBFS: cannot remove '/etc/debian_version'

[Niels Thykier]

Santiago Vila:
> On Thu, Jan 11, 2018 at 08:10:00PM +, Niels Thykier wrote:
> 
>>> I'm confused. Do you mean that the install target is "taken"
>>> and packages may not freely use it in debian/rules?
>>>
>>
>> Afraid so; it occurred before my involvement in debhelper, but I think
>> it used to be more common for packages to also have an "install" target
>> and debhelper basically mirrored that (with -arch + -indep variants).
> 
> I must be missing something, then, because today I've checked that
> "dpkg-buildpackage":
> 
> - Works ok in stretch.
> - Does only fail in buster/sid (I actually tried it in sid).
> 
> ("dpkg-buildpackage -B" works ok in both stretch and buster/sid).
> 

debhelper before 11.1 had a very suboptimal handling of sequence targets
in debian/rules (reported in #880840).  In debhelper/11.1, this was
fixed by properly treating d/rules targets as opaque and assuming that
the target will properly delegate tasks on as necessary.
  This bug has been present more or less since compat 9 was introduced,
but we have not noticed until now.  I suspect it is related to how
dpkg-buildpackage calls d/rules, which somehow hides the issue in
base-files (but shows a bug in the behaviour of debhelper/10.2.5).

In a clean base-files source checkout, you can see that dh thinks it
should run "debian/rules install":

$ dh binary --no-act | grep 'debian/rules install'
   debian/rules install
$

(You can see the suboptimal handling of this target by looking at the
full sequence.  dh actually wants to run "debian/rules install" as the
very first thing before calling any of the build commands and will then
follow it by calling the build + install commands *again*)

But if you emulate the way dpkg-buildpackage calls the rules file, then
the "debian/rules install" call disappears in debhelper/10.2.5:

$ dpkg-buildpackage -us -uc -T build
[...]
$ dh binary --no-act | grep 'debian/rules install'
$

The absence of the "debian/rules install" is a technically a violation
of the API that debhelper promises for compat 9 packages, which says:

"""
>-   dh is aware of the usual dependencies between targets in 
> debian/rules.  So, "dh binary" will run any build, build-arch, build-indep, 
> install,
>etc targets that exist in the rules file. There's no need 
> to define an explicit binary target with explicit dependencies on the other 
> targets"""

(Turns out that Joey happened to list "install" explicitly before the
"etc.".  I had not noticed that until now.)

For the record, debhelper recognises the following sequence targets:

 * build, build-arch and build-indep
 * install, install-arch and install-indep
 * binary, binary-arch and binary-indep
 * clean

They were present for as long as I mentioned debhelper and I assume they
were present since debhelper/9 (but I haven't bothered digging in the
git log to confirm that).

> Fixing this is base-files would be trivial, of course, but before I do
> that I'd like to confirm that it's a bug in base-files.
> 
> Considering that this used to work in stretch, are you sure that
> debhelper is following the "specs"?
> 
> Thanks.
> 


I believe debhelper finally follows the spec it set for itself and I
would appreciate if we fixed it in base-files.  Apologies for the extra
work on your end.

Thanks,
~Niels

Bug#887084: marked as done (libmoosex-xsaccessor-perl: FTBFS: t/moose_accessor_overwrite_warning.t broken by new libmoose-perl)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 20:51:51 +
with message-id 
and subject line Bug#887084: fixed in libmoosex-xsaccessor-perl 0.008-1
has caused the Debian Bug report #887084,
regarding libmoosex-xsaccessor-perl: FTBFS: 
t/moose_accessor_overwrite_warning.t broken by new libmoose-perl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmoosex-xsaccessor-perl
Version: 0.007-1
Severity: serious
Tags: fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=120155

This package fails its test suite on current sid, apparently
due to a libmoose-perl update.

The problem should be fixed in 0.008 as seen in the upstream bug.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libmoosex-xsaccessor-perl
Source-Version: 0.008-1

We believe that the bug you reported is fixed in the latest version of
libmoosex-xsaccessor-perl, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated libmoosex-xsaccessor-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Jan 2018 20:03:37 +
Source: libmoosex-xsaccessor-perl
Binary: libmoosex-xsaccessor-perl
Architecture: source
Version: 0.008-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 887084
Description: 
 libmoosex-xsaccessor-perl - use Class::XSAccessor to speed up Moose accessors
Changes:
 libmoosex-xsaccessor-perl (0.008-1) unstable; urgency=medium
 .
   * Team upload
 .
   * gbp.conf: rename 'git-import-orig' section to 'import-orig'
   * New upstream version 0.008
 + Fixes tests with new Moose (Closes: #887084)
   * update years of upstream copyright
   * use https in CPAN's URL in debian/watch
   * use secure protocol for the Vcs-Git URL
   * drop CONTRIBUTING from d/copyright (gone upstream)
   * bump debhelper compatibility level from 8 to 10
   * add Testsuote header; skip runtime-deps test
   * declare conformance with Policy 4.1.3
Checksums-Sha1: 
 92ec8dfadf34a91ae7018f483b05c170f9f87a47 2426 
libmoosex-xsaccessor-perl_0.008-1.dsc
 1119d865d83973c0bf0e63fa1c3cef707fb25360 44396 
libmoosex-xsaccessor-perl_0.008.orig.tar.gz
 7fc6d224fb784e41908ad6863f80974d707e8345 3884 
libmoosex-xsaccessor-perl_0.008-1.debian.tar.xz
Checksums-Sha256: 
 22798a923a7971d4c8a6719eace36b3913a26aeff3a0f1ea73f13ba0a9c10746 2426 
libmoosex-xsaccessor-perl_0.008-1.dsc
 5174327df7c4e8ab31a166b5ec678fc374963e1e9ccaad39743a380e73408f59 44396 
libmoosex-xsaccessor-perl_0.008.orig.tar.gz
 71d928001ab24bb3505d59a87e0d257cce872f7c6bf337f3c5ccbbec24726206 3884 
libmoosex-xsaccessor-perl_0.008-1.debian.tar.xz
Files: 
 9db1166286191f764d13be6c8d562390 2426 perl optional 
libmoosex-xsaccessor-perl_0.008-1.dsc
 49e6eb04982365ca361f655383b9b489 44396 perl optional 
libmoosex-xsaccessor-perl_0.008.orig.tar.gz
 0cbea01f51568ffe43ee4f2bd585afcf 3884 perl optional 
libmoosex-xsaccessor-perl_0.008-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAlpaZp4ACgkQ276dTZnS
oAQ4Ww/7B9RNLD1YLcB+KlbAZO/fk1nV7Og9jSw1tO36UY4HoFPMQVycALgsH7sE
qmJLSf0XYxy4oJ3Hemwb5z/RnS7jX/d6nqTpzqRUwMjxeYqgjEtVc4jWmpQyvIXx
rtgamedRx6Gfvice3fAt48szH7RHRe9Gx3zDwFmcsjzwxMErqhJ+kWir4Uw/Rt2r
bsxwoUqzP0K5GXDfXGYdHujtUpW2rF42H2MfHQuzPbjood3yH9ZRXC4n9Ns+gw1v
aUgweBSyHGk4CdgDY9Wm8fICrJof5mfTpTv5GsmFsRcurOomZQ/GI1p8VBAt//Kt
0sFexlth/a8/1JQfbs/i8DuJAAeuuzfe6j62ZUwAdIIF6iJa7Bn466Hsh03RQ12v
+zSHD8exDno9bFW+LdZLrpsg1YCDPIx39ZDkScBTku+lJx3KJP8slZ2I2OfiNRcg
9+8l+TM8w26ijoDPZ/RHx64i+EFFUyWPO5ryep7vaFBrTvBXyQo3afKSwnyx0jf3
2p69fCzEiXeHNTYlMOki5y9GP4GbBiEMp1x4S4BcnGvIg2XSge3ssbYpIPslZIGj
mEcZ1DjTWSlPkcGUrTa1nGEZyDAdouUF+bkQfUMOmGCPp+OJ3umjCvxMfJknhQSp
OQPXwo+1aPcMDKHxncu2ECzo1zI/Kq7lHB1fooC8yLeO1dHh+84=
=T6V4
-END PGP SIGNATURE End Message ---

Bug#887095: mali-midgard-driver: missing B-D: chrpath

[Wookey]

On 2018-01-13 19:58 +0100, Andreas Beckmann wrote:

> mali-midgard-driver FTBFS due to a missing Build-Depends: chrpath:


Doh. Yes. Thanks for reporting that.  

I added that late to deal with the rpaths shipped by upstream, and
then forgot to add it to the build-deps.

For disk-space reasons I couldn't check an sbuild build on my armhf
device so there was a risk of bugs like this.

Update coming shortly.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#885010: marked as done (python-ldap: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 19:05:09 +
with message-id 
and subject line Bug#885010: fixed in python-ldap 3.0.0~b4-1
has caused the Debian Bug report #885010,
regarding python-ldap: Incomplete debian/copyright?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ldap
Version: 3.0.0~b3-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Willem van den Akker 

Hi,

I just ACCEPTed python-ldap from NEW but noticed it was missing 
attribution in debian/copyright for at least the code copy of
shutil.which in Lib/ldap/compat.py.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-ldap
Source-Version: 3.0.0~b4-1

We believe that the bug you reported is fixed in the latest version of
python-ldap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Willem van den Akker  (supplier of updated python-ldap 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Jan 2018 07:38:36 +0100
Source: python-ldap
Binary: python-ldap python3-ldap python-ldap-dbg python3-ldap-dbg
Architecture: source
Version: 3.0.0~b4-1
Distribution: unstable
Urgency: medium
Maintainer: Willem van den Akker 
Changed-By: Willem van den Akker 
Description:
 python-ldap - LDAP interface module for Python
 python-ldap-dbg - LDAP interface module for Python (debug extension)
 python3-ldap - LDAP interface module for Python3
 python3-ldap-dbg - LDAP interface module for Python3 (debug extension)
Closes: 885010
Changes:
 python-ldap (3.0.0~b4-1) unstable; urgency=medium
 .
   * New upstream version.
   * debian/control
 - VCS*: migrate to salsa.debian.org
 - bump to standard version 4.1.3
   * debian/copyright
 - fixed incomplete entry (Closes: #885010)
   * debian/compat
 - bump to 11
Checksums-Sha1:
 393721756d34d63fa371914242766e42510ee624 2245 python-ldap_3.0.0~b4-1.dsc
 c6a589bc49f14786948f948571ac5f97d813591f 363829 
python-ldap_3.0.0~b4.orig.tar.gz
 9c0c97e8d36d6a161e9cc8aef5615845d604c155 7384 
python-ldap_3.0.0~b4-1.debian.tar.xz
 32e63797fd716bd4354b3243a897d5ce65776f21 8083 
python-ldap_3.0.0~b4-1_source.buildinfo
Checksums-Sha256:
 8d76ab72fb7990c1e0bc4cfb8e9b6a215c48612487dfa266ab3aa71375af92e0 2245 
python-ldap_3.0.0~b4-1.dsc
 0a7e39a47c356050977613e00be64f09f47adef0e26ed40c6303c41d534066c6 363829 
python-ldap_3.0.0~b4.orig.tar.gz
 283ae6dac59d15e506f325aaa5456db61c923de244dc0c6df2e6b4e43cb97251 7384 
python-ldap_3.0.0~b4-1.debian.tar.xz
 690c4a21471ef7e479e9dc4ce291ab0b5e411ad2a6ecc267798438f3011b9381 8083 
python-ldap_3.0.0~b4-1_source.buildinfo
Files:
 ea6500a1885f93332ac85a9ea7a2f9fd 2245 python optional 
python-ldap_3.0.0~b4-1.dsc
 7f6a9690f613c8c6c7fe448a96564537 363829 python optional 
python-ldap_3.0.0~b4.orig.tar.gz
 1f587df329a9b77ddc35fa38027313be 7384 python optional 
python-ldap_3.0.0~b4-1.debian.tar.xz
 022e54c2c8b0204272c9a5a8f599defe 8083 python optional 
python-ldap_3.0.0~b4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaWlRaAAoJEMtwMWWoiYTceY8P/1HzYi42s9fQRqX9UYdzg26s
+k9aciF2k03lZxyL59ZPhXT7pWpCYsHBF1pAgqixQ6ETbdMYYS+oz+3v19VzX49J
9S/qHUgqnTNMGysWNvg/W8d15/BGHj+8RIqgWALR7WVcHSTDoix5dwlnRPylOWeu
aCPT5BjwOO3LQ/FD1RCITcgfc8Ao3QqY/BakQV+j5BeBp4k3dlXP45Nt+vgj+oIv
fHuirQrtik0MQBc9ByX1pQ6AQbatlKG+QQHP+2UjpB9htR0R87T+TQ1bi2uOeoQg
jYitVaIW14Zdk9akhn35zVTGGgFUJ8MiI2jbi+XV3VGpWchrF5RgPeawh6mCSbRm
9zB/alIjIkJGzdh7lNsWpFoAL5esbSfNPjNBfVnFV+s24iPXgjB01z8/TxywcpvM
F0zHrL37Ma7vwZmzucsUJreCS3973b5SgrtMy35yhqe3znvQjOOfX0d6fZGJ+EFG
bZS8WrtWWfabzI0iD5nJgdJWClRcOcQafPiSAGj3TrLXe4eOoT5OJNuTSWCoYKHA

Bug#887095: mali-midgard-driver: missing B-D: chrpath

[Andreas Beckmann]

Source: mali-midgard-driver
Version: 0.1-1
Severity: serious
Justification: fails to build from source

Hi,

mali-midgard-driver FTBFS due to a missing Build-Depends: chrpath:

[...]
install -d debian/.debhelper/generated/mali-t76x-wayland-driver
find debian -type f -name "*.so" | xargs -t -n 1 chrpath -d
chrpath -d 
debian/mali-t76x-wayland-driver/usr/lib/arm-linux-gnueabihf/liboffline_compiler_api.so
 
/usr/bin/xargs: chrpath: No such file or directory
debian/rules:10: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 127
make[1]: Leaving directory '/build/mali-midgard-driver-0.1'
debian/rules:7: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


Andreas


mali-midgard-driver_0.1-1.log.gz
Description: application/gzip

Bug#886901: base-files: FTBFS: cannot remove '/etc/debian_version'

[Santiago Vila]

On Thu, Jan 11, 2018 at 08:10:00PM +, Niels Thykier wrote:

> > I'm confused. Do you mean that the install target is "taken"
> > and packages may not freely use it in debian/rules?
> > 
> 
> Afraid so; it occurred before my involvement in debhelper, but I think
> it used to be more common for packages to also have an "install" target
> and debhelper basically mirrored that (with -arch + -indep variants).

I must be missing something, then, because today I've checked that
"dpkg-buildpackage":

- Works ok in stretch.
- Does only fail in buster/sid (I actually tried it in sid).

("dpkg-buildpackage -B" works ok in both stretch and buster/sid).

Fixing this is base-files would be trivial, of course, but before I do
that I'd like to confirm that it's a bug in base-files.

Considering that this used to work in stretch, are you sure that
debhelper is following the "specs"?

Thanks.

Processed: tagging 887084

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 887084 + buster sid
Bug #887084 [libmoosex-xsaccessor-perl] libmoosex-xsaccessor-perl: FTBFS: 
t/moose_accessor_overwrite_warning.t broken by new libmoose-perl
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867722: marked as done (xul-ext-imap-acl: please depend on icedove | thunderbird)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 17:34:40 +
with message-id 
and subject line Bug#867722: fixed in imap-acl-extension 0.2.7-2
has caused the Debian Bug report #867722,
regarding xul-ext-imap-acl: please depend on icedove | thunderbird
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
867722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-imap-acl
Version: 0.2.7-1
Severity: normal

Dear Maintainer,

Icedove has since been re-rebranded to Thunderbird, but xul-ext-imap-acl still
depends on icedove only. Please change the dependency accordingly.

Cheers,

 - Roland

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

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

Versions of packages xul-ext-imap-acl depends on:
ii  icedove1:45.8.0-3
ii  thunderbird [icedove]  1:45.8.0-3

xul-ext-imap-acl recommends no packages.

xul-ext-imap-acl suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: imap-acl-extension
Source-Version: 0.2.7-2

We believe that the bug you reported is fixed in the latest version of
imap-acl-extension, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated imap-acl-extension 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jan 2018 18:06:25 +0100
Source: imap-acl-extension
Binary: xul-ext-imap-acl
Architecture: source all
Version: 0.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Michael Fladischer 
Description:
 xul-ext-imap-acl - extension to manage ACLs on IMAP folders
Closes: 867722
Changes:
 imap-acl-extension (0.2.7-2) unstable; urgency=medium
 .
   * Rebuild for thunderbird (Closes: #867722).
   * Add debian/gbp.conf.
   * Bump debhelper compatibility and version to 11.
   * Run wrap-and-sort -bast to reduce diff size of future changes.
   * Bump Standards-Version to 4.1.3.
   * Use https:// for copyright-format 1.0 URL and for Vcs-Git field.
Checksums-Sha1:
 96c4d0e08926e2411af70d64e7e934ca62355767 1747 imap-acl-extension_0.2.7-2.dsc
 67cdf47edaa3a9a93ddbe8b141d71a99dd1521b9 20402 
imap-acl-extension_0.2.7.orig.tar.gz
 672f8a8d285ffd5f28ffcf33bf512967b4cedbf1 2808 
imap-acl-extension_0.2.7-2.debian.tar.xz
 404679b8867f3aafa60bdc583e06d1614eb74c53 6984 
imap-acl-extension_0.2.7-2_amd64.buildinfo
 6857554fbe888052a7b0c3c6a423c87b8206fb81 22836 xul-ext-imap-acl_0.2.7-2_all.deb
Checksums-Sha256:
 94095ce97f63efb9d8e7833c05ab49f57b20b786d5e8e8874d0df90c11d09c7f 1747 
imap-acl-extension_0.2.7-2.dsc
 4bc9aa7dde39753c5a61b5e113ec467bca4a476ea9caa223bbdfbbe6a92c852a 20402 
imap-acl-extension_0.2.7.orig.tar.gz
 f1c321f10be93c7fce3c01bc40fec5bd39c8099e69d94c94ddfe884b67e7bc8c 2808 
imap-acl-extension_0.2.7-2.debian.tar.xz
 37eaf7c61889f2949b5a1b59b693aeb42a47e6e60324ed4ffb4ae1de8266 6984 
imap-acl-extension_0.2.7-2_amd64.buildinfo
 38e35baa544cfa0030e7adf7bdaa69fb0c8bfbb5478c05cb2f0073c57f76cdb4 22836 
xul-ext-imap-acl_0.2.7-2_all.deb
Files:
 681c5bc6b860473bab2fda5e3e07749c 1747 mail optional 
imap-acl-extension_0.2.7-2.dsc
 c2e0d46c9cca8129da26bfee64eeaf69 20402 mail optional 
imap-acl-extension_0.2.7.orig.tar.gz
 d6d2c584691cf8ece4437dadb5390258 2808 mail optional 
imap-acl-extension_0.2.7-2.debian.tar.xz
 a7c63f5eb62950520b037eca7d1e0adf 6984 mail optional 
imap-acl-extension_0.2.7-2_amd64.buildinfo
 e4e79694b26c8ee2d7645468153dca0d 22836 mail optional 
xul-ext-imap-acl_0.2.7-2_all.deb

-BEGIN 

Bug#887084: libmoosex-xsaccessor-perl: FTBFS: t/moose_accessor_overwrite_warning.t broken by new libmoose-perl

[Niko Tyni]

Package: libmoosex-xsaccessor-perl
Version: 0.007-1
Severity: serious
Tags: fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=120155

This package fails its test suite on current sid, apparently
due to a libmoose-perl update.

The problem should be fixed in 0.008 as seen in the upstream bug.
-- 
Niko Tyni   nt...@debian.org

Bug#885835: awstats: CVE-2017-1000501: path traversals in config and migrate parameter

[Abhijith PA]

Hello.

I am working on updating awstats for jessie and stretch.

--
Abhijith PA

Processed: Not a problem in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 887076 buster sid
Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused 
build-dependency on libxatracker-dev
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#881301: marked as pending

[Simon McVittie]

On Sat, 13 Jan 2018 at 20:38:39 +0900, Mike Hommey wrote:
> On Sat, Jan 13, 2018 at 11:35:08AM +, Simon McVittie wrote:
> > On Sat, 13 Jan 2018 at 08:50:14 +0900, Mike Hommey wrote:
> > > When can this reach unstable?

The source packages have now been accepted. The buildds haven't picked
them up yet, but you should see binaries later today.

> > Huh. Did you recently enable any new Shell extensions, or update
> > existing extensions, or anything like that?
> 
> I've had extensions enabled for a while, and reading this bug I disabled
> them all. That didn't stop.

As a general note, disabling an extension at runtime does not guarantee to
unload it fully (it's meant to, but bugs in the extension can mean that
its actions are not completely undone) so to be completely sure please
disable extensions, log out and log back in. (But if the Shell crashes,
that's also sufficient!)

> What /does/ seem to have stopped it is me killing my script that
> overwrites the background image every ~10 minutes. But I've been running
> that for well over a year.

Based on this, it's very likely that in the new version, you'll get
warnings logged (in the systemd journal if you're using systemd; I
don't know where they end up on non-systemd machines) with a JavaScript
stack trace. This will hopefully be more useful in tracking down the root
cause than the C backtraces we've already seen, which mostly just say
"I'm interpreting some JavaScript" without indicating what.

Please report each distinct stack trace as a separate bug, similar
to the one I just reported at
.

Since you have a reproducer (your background-changing script) it would
be great if you could run without that script for a couple of hours,
report any stack traces you see with a note that they are *not* caused by
your background-changing script, then re-enable your script and report
any new stack traces that are well-correlated with background changes,
this time mentioning what your script does/how it works. There's probably
a bug in the code that sets the background.

Thanks,
smcv

Bug#881301: marked as done (gnome-shell: intermittent "invalid unclassed pointer in cast to 'ClutterText'" + segfault)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 16:19:35 +
with message-id 
and subject line Bug#881301: fixed in gnome-shell 3.26.2-3
has caused the Debian Bug report #881301,
regarding gnome-shell: intermittent "invalid unclassed pointer in cast to 
'ClutterText'" + segfault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
881301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.26.2-1
Severity: grave
Justification: causes non-serious data loss

Dear maintainers,

Sometimes gnome-shell crashes, randomly while using the computer or not.
Also happens when the screen is locked, even without any programs running.

The file /var/log/syslog has a lot of lines like:
gnome-shell[]: clutter_actor_insert_child_at_index: assertion 
'child->priv->parent == NULL' failed
gnome-shell[]: clutter_text_get_editable: assertion 'CLUTTER_IS_TEXT 
(self)' failed
gnome-shell[]: clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' 
failed
gnome-shell[]: clutter_text_set_text: assertion 'CLUTTER_IS_TEXT (self)' 
failed
gnome-shell[]: invalid unclassed pointer in cast to 'ClutterText'

And sometimes in place of that last line it has:

gnome-shell[]: invalid uninstantiatable type '(null)' in cast to 
'ClutterText'

Attached are three syslog files of the last times the segfault occurred.

Regards,
LD


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

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

Versions of packages gnome-shell depends on:
ii  caribou  0.4.21-2
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-1
ii  evolution-data-server3.26.2.1-1
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.26.2-1
ii  gir1.2-caribou-1.0   0.4.21-2
ii  gir1.2-freedesktop   1.54.1-2
ii  gir1.2-gcr-3 3.20.0-5.1
ii  gir1.2-gdesktopenums-3.0 3.24.1-1
ii  gir1.2-gdm-1.0   3.26.2.1-2
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.54.1-2
ii  gir1.2-gnomebluetooth-1.03.26.1-1
ii  gir1.2-gnomedesktop-3.0  3.26.2-1
ii  gir1.2-gtk-3.0   3.22.25-1
ii  gir1.2-gweather-3.0  3.26.0-1
ii  gir1.2-ibus-1.0  1.5.14-3
ii  gir1.2-mutter-1  3.26.2-1
ii  gir1.2-networkmanager-1.01.9.90-1
ii  gir1.2-nmgtk-1.0 1.8.6-1
ii  gir1.2-pango-1.0 1.40.13-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.18-2
ii  gir1.2-soup-2.4  2.60.2-1
ii  gir1.2-upowerglib-1.00.99.6-1
ii  gjs  1.50.2-1
ii  gnome-backgrounds3.26.2-1
ii  gnome-settings-daemon3.26.2-1
ii  gnome-shell-common   3.26.2-1
ii  gsettings-desktop-schemas3.24.1-1
ii  libasound2   1.1.3-5
ii  libatk-bridge2.0-0   2.26.0-2
ii  libatk1.0-0  2.26.1-1
ii  libc62.24-17
ii  libcairo21.15.8-2
ii  libcanberra-gtk3-0   0.30-4
ii  libcanberra0 0.30-4
ii  libcroco30.6.12-1
ii  libdbus-glib-1-2 0.108-3
ii  libecal-1.2-19   3.26.2.1-1
ii  libedataserver-1.2-223.26.2.1-1
ii  libgcr-base-3-1  3.20.0-5.1
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libgirepository-1.0-11.54.1-2
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.50.2-1
ii  libglib2.0-0 2.54.2-1
ii  

Bug#886858:

[Dennis Heddicke]

I tested the 3.16.53 upstream kernel and got the same problem.
Will you do something against this? Shall i report upstream?

Bug#887001: marked as pending

[Aurelien Jarno]

tag 887001 pending
thanks

Hello,

Bug #887001 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-glibc/glibc.git/commit/?id=82a8885

---
commit 82a888594125b1d05bed4092b23af44fc23907a2
Author: Aurelien Jarno 
Date:   Sat Jan 13 16:14:06 2018 +0100

debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - Fix a buffer underflow in getcwd() (CVE-2018-101).  Closes:
#887001.

diff --git a/debian/changelog b/debian/changelog
index f72b868..f1cebf4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,9 @@ glibc (2.26-4) UNRELEASED; urgency=medium
 the multilib flavours, simplify the mips* entries into mips*, mips be and
 mips le, instead of trying to keep all the flavours in sync. Remove
 XFAILs for tests that have been fixed.
+  * debian/patches/git-updates.diff: update from upstream stable branch:
+- Fix a buffer underflow in getcwd() (CVE-2018-101).  Closes:
+  #887001.
 
  -- Aurelien Jarno   Fri, 12 Jan 2018 22:26:33 +0100
 

Processed: Bug#887001 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 887001 pending
Bug #887001 [src:glibc] glibc: CVE-2018-101: realpath() buffer underflow 
when getcwd() returns relative path allows privilege escalation
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887070: marked as done (prometheus-blackbox-exporter FTBFS on armhf/mips*: FAIL github.com/prometheus/blackbox_exporter/prober)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 15:11:53 +
with message-id 
and subject line Bug#887070: fixed in prometheus-blackbox-exporter 0.11.0+ds-4
has caused the Debian Bug report #887070,
regarding prometheus-blackbox-exporter FTBFS on armhf/mips*: FAIL 
github.com/prometheus/blackbox_exporter/prober
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-blackbox-exporter
Version: 0.11.0+ds-3
Severity: serious

https://buildd.debian.org/status/package.php?p=prometheus-blackbox-exporter=sid

...
=== RUN   TestTCPConnectionQueryResponseIRC
panic: Error accepting on socket: accept tcp 127.0.0.1:39921: use of closed 
network connection

goroutine 1568 [running]:
github.com/prometheus/blackbox_exporter/prober.TestTCPConnectionQueryResponseStartTLS.func1(0x6036a8,
 0x12075110, 0x124c, 0x47b, 0x7c0, 0x124c0800, 0x68f, 0x7c0, 0x12070480)

/<>/prometheus-blackbox-exporter-0.11.0+ds/obj-arm-linux-gnueabihf/src/github.com/prometheus/blackbox_exporter/prober/tcp_test.go:231
 +0x798
created by 
github.com/prometheus/blackbox_exporter/prober.TestTCPConnectionQueryResponseStartTLS

/<>/prometheus-blackbox-exporter-0.11.0+ds/obj-arm-linux-gnueabihf/src/github.com/prometheus/blackbox_exporter/prober/tcp_test.go:228
 +0x4d8
FAILgithub.com/prometheus/blackbox_exporter/prober  15.831s
dh_auto_test: cd obj-arm-linux-gnueabihf && go test -v -p 4 
github.com/prometheus/blackbox_exporter 
github.com/prometheus/blackbox_exporter/config 
github.com/prometheus/blackbox_exporter/prober returned exit code 1
debian/rules:23: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1
--- End Message ---
--- Begin Message ---
Source: prometheus-blackbox-exporter
Source-Version: 0.11.0+ds-4

We believe that the bug you reported is fixed in the latest version of
prometheus-blackbox-exporter, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
prometheus-blackbox-exporter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Jan 2018 13:41:14 +
Source: prometheus-blackbox-exporter
Binary: prometheus-blackbox-exporter
Architecture: source amd64
Version: 0.11.0+ds-4
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 prometheus-blackbox-exporter - Blackbox prober for Prometheus
Closes: 887070
Changes:
 prometheus-blackbox-exporter (0.11.0+ds-4) unstable; urgency=high
 .
   * Disable completely tcp_test.go until upstream fixes the tests.
 Closes: 887070
Checksums-Sha1:
 f15d13375f0c7d2b7518f831fad53937ffe4fb5c 2595 
prometheus-blackbox-exporter_0.11.0+ds-4.dsc
 f584b5a36f193605433d245a1566945bf8686369 4684 
prometheus-blackbox-exporter_0.11.0+ds-4.debian.tar.xz
 3226c2d206b74a3e7eb53516d8d3a5cc081eac45 7943 
prometheus-blackbox-exporter_0.11.0+ds-4_amd64.buildinfo
 4526a89a35363041191205ccebd0b121bf19858b 2455756 
prometheus-blackbox-exporter_0.11.0+ds-4_amd64.deb
Checksums-Sha256:
 31bda0114cef261b2f3dc724613dfa8ed0261f7ed91a72d367a1634292201194 2595 
prometheus-blackbox-exporter_0.11.0+ds-4.dsc
 ff7e3c33629ccd9448b4a048558a58950a3c22d483da370c4bf912464ee88ec1 4684 
prometheus-blackbox-exporter_0.11.0+ds-4.debian.tar.xz
 0f68fe2ddf236c103b36e0ca7ccc4c431774f7ccb03ae587cc37e9837b8e60b5 7943 
prometheus-blackbox-exporter_0.11.0+ds-4_amd64.buildinfo
 d2a3e4cd71079bda8ba6713691587c06a0241d73b8d66dd4af8ce39193a7642b 2455756 
prometheus-blackbox-exporter_0.11.0+ds-4_amd64.deb
Files:
 24b319f6b695dac5cfb3885fbdc4f9dc 2595 devel optional 
prometheus-blackbox-exporter_0.11.0+ds-4.dsc
 136dbf6c5735c559645f6816e751d171 4684 devel optional 
prometheus-blackbox-exporter_0.11.0+ds-4.debian.tar.xz
 7958f076ddc6bef709d733bac6f0b43f 7943 devel optional 

Bug#884542: [pkg-go] Bug#884542: prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics

[Martín Ferrari]

Status update: still waiting for upstream's fix.

On 18/12/17 04:55, Martín Ferrari wrote:
> Adrian,
> 
> Thanks for the report. I presume this error is due to the change in the
> Prometheus' common library. I am already preparing a new upstream
> release, but that is waiting on an upstream bug:
> https://github.com/prometheus/mysqld_exporter/issues/251
> 
> 
> On 16/12/17 12:03, Adrian Bunk wrote:
>> Source: prometheus-mysqld-exporter
>> Version: 0.9.0+ds-3
>> Severity: serious
>> Tags: buster sid
>>
>> Some recent change in unstable makes prometheus-mysqld-exporter FTBFS:
>>
>> https://tests.reproducible-builds.org/debian/history/prometheus-mysqld-exporter.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-mysqld-exporter.html
>>
>> ...
>> === RUN   TestScrapeInnodbMetrics
>> --- FAIL: TestScrapeInnodbMetrics (0.00s)
>>  info_schema_innodb_metrics_test.go:17: no such flag -log.level
> 
> 
> 


-- 
Martín Ferrari (Tincho)

Bug#886670: libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that shouldn't be there

[Joachim Reichel]

severity 886670 normal
unblock 883986 by 886670
tag 886670 upstream
forwarded 886670 https://github.com/CGAL/cgal/issues/2734
thanks

On 08.01.2018 20:35, Adrian Bunk wrote:
> While looking into fixing #883986 I ran into the following problem
> due to openscad using CGAL_CXX_FLAGS_INIT:
> 
> /usr/lib/x86_64-linux-gnu/cmake/CGAL/CGALConfig.cmake:
> set(CGAL_CXX_FLAGS_INIT   "-g -O2 
> -fdebug-prefix-map=/build/cgal-d6DBFP/cgal-4.11=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -frounding-math" )
> 
> The only flag that might be correct in this place is -frounding-math,
> in case that is required for using CGAL.
> 
> Exposing flags like -fdebug-prefix-map is simply wrong.
> 
> (For #883986 the problem is the -g, that is also wrong here.)

I agree and I have forwarded this as
https://github.com/CGAL/cgal/issues/2734

> The severity might seem inflated, but this should be fixed
> for fixing the RC #883986 FTBFS in openscad.

However, I disagree about the severity. Since there is a simple workaround I've
reset the severity to normal and removed the block relation.

  Joachim

Processed: Re: Bug#886670: libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that shouldn't be there

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 886670 normal
Bug #886670 [libcgal-dev] libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that 
shouldn't be there
Severity set to 'normal' from 'serious'
> unblock 883986 by 886670
Bug #883986 [src:openscad] openscad: FTBFS on mips/mipsel: virtual memory 
exhausted: Cannot allocate memory
883986 was blocked by: 886670
883986 was not blocking any bugs.
Removed blocking bug(s) of 883986: 886670
> tag 886670 upstream
Bug #886670 [libcgal-dev] libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that 
shouldn't be there
Added tag(s) upstream.
> forwarded 886670 https://github.com/CGAL/cgal/issues/2734
Bug #886670 [libcgal-dev] libcgal-dev: CGAL_CXX_FLAGS_INIT contains flags that 
shouldn't be there
Set Bug forwarded-to-address to 'https://github.com/CGAL/cgal/issues/2734'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883986
886670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#883986: Don't drop -frounding-math

[Joachim Reichel]

You shouldn't drop ${CGAL_CXX_FLAGS_INIT} completely. If you want to avoid the
troublesome flags, you should at least include -frounding-math, which is
strictly needed for CGAL.

  Joachim

Bug#886852: NVidia driver : upgrade to version 384.111

[Luca Boccassi]

On Sat, 2018-01-13 at 14:59 +0100, Andreas Beckmann wrote:
> On 2018-01-11 23:26, Luca Boccassi wrote:
> > The new meta packages for switching over are handy, unfortunately
> > apt
> > chokes on them - aptitude is able to figure it out though.
> > 
> > I suspect it's again due to multiarch - seems to be a recurring
> > problem
> > with apt. So don't think there's anything we can do.
> 
> Do you have more details? What does not work with apt?

It cannot find a resolution (with hints it gets to a point where it
present removing half of the GUI packages as a solution) - if you
remember we had the same problem a month ago or so, and it looked like
it was due to having both amd64 and i386 installed - as with only one
arch (in a chroot) it couldn't be reproduced:

$ dpkg -l | grep nvidia-driver
ii  nvidia-driver 384.111-1~bpo9+1  
  amd64NVIDIA metapackage
ii  nvidia-driver-bin 384.111-1~bpo9+1  
  amd64NVIDIA driver support binaries
ii  nvidia-driver-libs:amd64  384.111-1~bpo9+1  
  amd64NVIDIA metapackage (OpenGL/GLX/EGL/GLES 
libraries)
ii  nvidia-driver-libs:i386   384.111-1~bpo9+1  
  i386 NVIDIA metapackage (OpenGL/GLX/EGL/GLES 
libraries)
ii  nvidia-driver-libs-i386:i386  384.111-1~bpo9+1  
  i386 NVIDIA metapackage (OpenGL/GLX/EGL/GLES 
32-bit libraries)
$ sudo apt install -t stretch-backports nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386
[sudo] password for luca: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgl1 : Depends: libglx0 (= 1.0.0-1) but it is not going to be installed
 libpurple0 : Depends: libfarstream-0.2-5 (>= 0.2.7) but it is not going to be 
installed
  Recommends: libpurple-bin but it is not going to be installed
 nvidia-driver-libs-nonglvnd : Depends: libgl1-nvidia-glx (= 384.111-1~bpo9+1) 
but it is not going to be installed
   Depends: libegl1-nvidia (= 384.111-1~bpo9+1) but 
it is not going to be installed
   Recommends: libglx-nvidia0 (= 384.111-1~bpo9+1) 
but it is not going to be installed
   Recommends: libgles-nvidia1 (= 384.111-1~bpo9+1) 
but it is not going to be installed
   Recommends: libgles-nvidia2 (= 384.111-1~bpo9+1) 
but it is not going to be installed
   Recommends: libnvidia-cfg1 (= 384.111-1~bpo9+1) 
but it is not going to be installed
   Recommends: nvidia-egl-wayland-icd (= 
384.111-1~bpo9+1) but it is not going to be installed
   Recommends: nvidia-nonglvnd-vulkan-icd (= 
384.111-1~bpo9+1) but it is not going to be installed
 nvidia-driver-libs-nonglvnd-i386:i386 : Depends: 
nvidia-driver-libs-nonglvnd:i386 but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

$ sudo aptitude install -t stretch-backports nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386
Note: selecting "nvidia-driver-libs-nonglvnd-i386:i386" instead of the virtual 
package "nvidia-driver-libs-nonglvnd-i386"
The following NEW packages will be installed:
  libegl1-nvidia{a} libegl1-nvidia:i386{a} libgl1-nvidia-glx{ab} 
libgl1-nvidia-glx:i386{ab} libgles-nvidia1{a} 
  libgles-nvidia1:i386{a} libgles1-glvnd-nvidia{a} 
libgles1-glvnd-nvidia:i386{a} nvidia-driver-libs-nonglvnd{b} 
  nvidia-driver-libs-nonglvnd:i386{ab} nvidia-driver-libs-nonglvnd-i386:i386 
nvidia-nonglvnd-vulkan-common{ab} 
  nvidia-nonglvnd-vulkan-icd{ab} nvidia-nonglvnd-vulkan-icd:i386{ab} 
0 packages upgraded, 14 newly installed, 0 to remove and 169 not upgraded.
Need to get 3,382 kB of archives. After unpacking 5,976 kB will be used.
The following packages have unmet dependencies:
 nvidia-vulkan-icd : Conflicts: nvidia-nonglvnd-vulkan-icd but 384.111-1~bpo9+1 
is to be installed
 Conflicts: nvidia-nonglvnd-vulkan-icd:i386 but 
384.111-1~bpo9+1 is to be installed
 nvidia-vulkan-icd:i386 : Conflicts: nvidia-nonglvnd-vulkan-icd but 
384.111-1~bpo9+1 is to be installed
  Conflicts: nvidia-nonglvnd-vulkan-icd:i386 but 
384.111-1~bpo9+1 is to be installed
 nvidia-nonglvnd-vulkan-icd : Conflicts: nvidia-vulkan-icd but 384.111-1~bpo9+1 
is installed
 

Bug#886852: NVidia driver : upgrade to version 384.111

[Andreas Beckmann]

On 2018-01-11 23:26, Luca Boccassi wrote:
> The new meta packages for switching over are handy, unfortunately apt
> chokes on them - aptitude is able to figure it out though.
> 
> I suspect it's again due to multiarch - seems to be a recurring problem
> with apt. So don't think there's anything we can do.

Do you have more details? What does not work with apt?


Andreas

Processed: Re: [pkg-go] Bug#887070: prometheus-blackbox-exporter FTBFS on armhf/mips*: FAIL github.com/prometheus/blackbox_exporter/prober

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 887070 https://github.com/prometheus/blackbox_exporter/issues/285
Bug #887070 [src:prometheus-blackbox-exporter] prometheus-blackbox-exporter 
FTBFS on armhf/mips*: FAIL github.com/prometheus/blackbox_exporter/prober
Set Bug forwarded-to-address to 
'https://github.com/prometheus/blackbox_exporter/issues/285'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887070: [pkg-go] Bug#887070: prometheus-blackbox-exporter FTBFS on armhf/mips*: FAIL github.com/prometheus/blackbox_exporter/prober

[Martín Ferrari]

forwarded 887070 https://github.com/prometheus/blackbox_exporter/issues/285
thanks

On 13/01/18 14:10, Adrian Bunk wrote:
> === RUN   TestTCPConnectionQueryResponseIRC
> panic: Error accepting on socket: accept tcp 127.0.0.1:39921: use of closed 
> network connection
Thanks for the report Adrian, this seems like a CPU contention issue; I
have just reported it upstream. I will disable these flakey tests for
now to fix the build.

-- 
Martín Ferrari (Tincho)

Bug#887075: marked as done (redis FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 13:51:09 +
with message-id 
and subject line Bug#887075: fixed in redis 5:4.0.6-4
has caused the Debian Bug report #887075,
regarding redis FTBFS: test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redis
Version: 5:4.0.6-3
Severity: serious

https://buildd.debian.org/status/package.php?p=redis=sid

...
Testing integration/psync2-reg
[ok]: PSYNC2 #3899 regression: setup
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave

Logged warnings (pid 821):
(none)


Logged warnings (pid 812):
(none)


Logged warnings (pid 803):
(none)

[exception]: Executing test client: couldn't execute "kill": no such file or 
directory.
couldn't execute "kill": no such file or directory
while executing
"exec kill -9 $bench_pid"
("uplevel" body line 47)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug messages

set no_exit 0   ; # Do no..."
("uplevel" body line 2)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {} {
start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug messages

set no_exit 0  ..."
("uplevel" body line 2)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {tags {"psync2"}} {
start_server {} {
start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug mess..."
(file "tests/integration/psync2-reg.tcl" line 7)
invoked from within
"source $path"
(procedure "execute_tests" line 4)
invoked from within
"execute_tests $data"
(procedure "test_client_main" line 10)
invoked from within
"test_client_main $::test_server_port "
Killing still running Redis server 30598
Killing still running Redis server 30608
Killing still running Redis server 30617
Killing still running Redis server 30631
Killing still running Redis server 30641
Killing still running Redis server 30662
Killing still running Redis server 30672
Killing still running Redis server 30682
Killing still running Redis server 30692
Killing still running Redis server 30702
Killing still running Redis server 30712
Killing still running Redis server 30722
Killing still running Redis server 30732
Killing still running Redis server 30742
Killing still running Redis server 30753
Killing still running Redis server 30763
Killing still running Redis server 30773
Killing still running Redis server 30783
Killing still running Redis server 30793
Killing still running Redis server 30803
Killing still running Redis server 30813
Killing still running Redis server 30827
Killing still running Redis server 30837
Killing still running Redis server 30852
Killing still running Redis server 30875
Killing still running Redis server 30956
Killing still running Redis server 31557
Killing still running Redis server 31573
Killing still running Redis server 31584
Killing still running Redis server 31615
Killing still running Redis server 31640
Killing still running Redis server 31660
Killing still running Redis server 31674
Killing still running Redis server 31684
Killing still running Redis server 31780
Killing still running Redis server 31829
Killing still running Redis server 31838
Killing still running Redis server 31860
Killing still running Redis server 31869
Killing still running Redis server 31881
Killing still running Redis server 31890
Killing still running Redis server 31902
Killing still running Redis server 31916
Killing still running Redis server 31925
Killing still running Redis server 31934
Killing still running Redis server 32213
Killing still running Redis server 32227
Killing still running Redis server 32236
Killing still running Redis server 

Bug#887076: xserver-xorg-video-ast: unused build-dependency on libxatracker-dev

[Julien Cristau]

Source: xserver-xorg-video-ast
Version: 1.1.5-1
Severity: serious

xserver-xorg-video-ast build-depends on libxatracker-dev [linux-any],
but:
1) it doesn't use it anywhere
2) libxatracker-dev is x86 only nowadays

Please get rid of that build-dependency.

Cheers,
Julien

Bug#887075: redis FTBFS: test failure

[Adrian Bunk]

Source: redis
Version: 5:4.0.6-3
Severity: serious

https://buildd.debian.org/status/package.php?p=redis=sid

...
Testing integration/psync2-reg
[ok]: PSYNC2 #3899 regression: setup
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill first slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave
[ok]: PSYNC2 #3899 regression: kill chained slave

Logged warnings (pid 821):
(none)


Logged warnings (pid 812):
(none)


Logged warnings (pid 803):
(none)

[exception]: Executing test client: couldn't execute "kill": no such file or 
directory.
couldn't execute "kill": no such file or directory
while executing
"exec kill -9 $bench_pid"
("uplevel" body line 47)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug messages

set no_exit 0   ; # Do no..."
("uplevel" body line 2)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {} {
start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug messages

set no_exit 0  ..."
("uplevel" body line 2)
invoked from within
"uplevel 1 $code "
(procedure "start_server" line 3)
invoked from within
"start_server {tags {"psync2"}} {
start_server {} {
start_server {} {
# Config
set debug_msg 0 ; # Enable additional debug mess..."
(file "tests/integration/psync2-reg.tcl" line 7)
invoked from within
"source $path"
(procedure "execute_tests" line 4)
invoked from within
"execute_tests $data"
(procedure "test_client_main" line 10)
invoked from within
"test_client_main $::test_server_port "
Killing still running Redis server 30598
Killing still running Redis server 30608
Killing still running Redis server 30617
Killing still running Redis server 30631
Killing still running Redis server 30641
Killing still running Redis server 30662
Killing still running Redis server 30672
Killing still running Redis server 30682
Killing still running Redis server 30692
Killing still running Redis server 30702
Killing still running Redis server 30712
Killing still running Redis server 30722
Killing still running Redis server 30732
Killing still running Redis server 30742
Killing still running Redis server 30753
Killing still running Redis server 30763
Killing still running Redis server 30773
Killing still running Redis server 30783
Killing still running Redis server 30793
Killing still running Redis server 30803
Killing still running Redis server 30813
Killing still running Redis server 30827
Killing still running Redis server 30837
Killing still running Redis server 30852
Killing still running Redis server 30875
Killing still running Redis server 30956
Killing still running Redis server 31557
Killing still running Redis server 31573
Killing still running Redis server 31584
Killing still running Redis server 31615
Killing still running Redis server 31640
Killing still running Redis server 31660
Killing still running Redis server 31674
Killing still running Redis server 31684
Killing still running Redis server 31780
Killing still running Redis server 31829
Killing still running Redis server 31838
Killing still running Redis server 31860
Killing still running Redis server 31869
Killing still running Redis server 31881
Killing still running Redis server 31890
Killing still running Redis server 31902
Killing still running Redis server 31916
Killing still running Redis server 31925
Killing still running Redis server 31934
Killing still running Redis server 32213
Killing still running Redis server 32227
Killing still running Redis server 32236
Killing still running Redis server 32245
Killing still running Redis server 409
Killing still running Redis server 420
Killing still running Redis server 432
Killing still running Redis server 443
Killing still running Redis server 470
Killing still running Redis server 479
Killing still running Redis server 505
Killing still running Redis server 514
Killing still running Redis server 527
Killing still running Redis server 536
Killing still running Redis server 548
Killing still running Redis server 556
Killing still running Redis server 565
Killing still running Redis server 573
Killing still running Redis server 582
Killing still running Redis server 591
Killing still running Redis server 601
Killing still running Redis server 609
Killing still running Redis server 617
Killing still running Redis server 625
Killing still running Redis server 633

Bug#880898: marked as done (ratbagd FTBFS with meson 0.43.0: Invalid kwargs for option "systemd-unit-dir": "default")

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 13:19:36 +
with message-id 
and subject line Bug#880898: fixed in ratbagd 0.4-3
has caused the Debian Bug report #880898,
regarding ratbagd FTBFS with meson 0.43.0: Invalid kwargs for option 
"systemd-unit-dir": "default"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
880898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ratbagd
Version: 0.4-2
Severity: serious

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

...
The Meson build system
Version: 0.43.0
Source dir: /build/1st/ratbagd-0.4
Build dir: /build/1st/ratbagd-0.4/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson_options.txt, line 1, column 0:
Invalid kwargs for option "systemd-unit-dir": "default"
--- End Message ---
--- Begin Message ---
Source: ratbagd
Source-Version: 0.4-3

We believe that the bug you reported is fixed in the latest version of
ratbagd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated ratbagd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jan 2018 14:05:04 +0100
Source: ratbagd
Binary: ratbagd
Architecture: source
Version: 0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 ratbagd- D-Bus daemon handling mouse configuration
Closes: 880898
Changes:
 ratbagd (0.4-3) unstable; urgency=medium
 .
   * Fix Meson options to allow building with 0.43. Closes: #880898.
   * Switch to debhelper compatibility level 11.
   * Standards-Version 4.1.3, no further change required.
Checksums-Sha1:
 4d5acc0d0adf791c0baf7cd1878e8f7fef236bde 1933 ratbagd_0.4-3.dsc
 328ff9b7f846ec6ea225765d53ffafc58057f520 2748 ratbagd_0.4-3.debian.tar.xz
 c8598d5bab977d76824d7e4b17a829bdc77e12a9 6896 ratbagd_0.4-3_source.buildinfo
Checksums-Sha256:
 ccc3c6e3904e4efc8f5ab90dcc334a5070de22464b019da8779ee2c6b6d4614e 1933 
ratbagd_0.4-3.dsc
 869047ae5fcbb9695425ada59c62c7ba932fc760bdb36faefcef04690880c4cf 2748 
ratbagd_0.4-3.debian.tar.xz
 c7889fe2f09360879167c7a3c5e60a7e43db7ece3326de4a73d0431efd6e10c9 6896 
ratbagd_0.4-3_source.buildinfo
Files:
 06d1778c11dfb5d39663e91c18058b5d 1933 utils optional ratbagd_0.4-3.dsc
 f13ff2e8850e6329db03c9bbb827ba43 2748 utils optional 
ratbagd_0.4-3.debian.tar.xz
 75360eaf5692c6bda3f5b263280f52bf 6896 utils optional 
ratbagd_0.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlpaBBsACgkQgNMC9Yht
g5zHUw/+NsZnnUQHjIlopcDrgAVH75XdlOGIz7pxeTA5l30PspBhAYKcU7E+EqK1
TcANBaDHKKMYmFJe3nTKJSsLIqGiA5jBFStVyBB6tyWASqwctPtJQEZannJCdgpU
GTFvkeW4eUF3NX8SeWGxlhgdcCYuN2j1QGPvjuTEF25RQXYmCuQVCMKzB9zoAd9K
GOK5JJkN1n0BBgjtDxgXL2aBg1ogVdtl2VXesNCXVr/v7JGUr+jkc1mr7zgvtWHN
7cSDSseX6xsblnv+6ODj9WFV9e3KB5VW996+N7PCtLbVjJ5iiQBbw67ePkWtWA/i
KrHe14tF1vxQuQSPkhKEIrV3Vv8G5ISQCRpioVpz0X/dBs9yGG3+41ro6DEnq85W
ueIEtISgvdNd71UqqYN+BsJqkjCKUX//3YMwajTYvkU45NYxoywySvpSmtxnilqd
Tzf4LhkW0WHLqRDBpGUDysd0Mjc4em+yTdkGGpwsQplUvD6TYlp+1PpJ57etV3zw
uOr+nweoN6hgfqJBqfJ3ZxteCMjio0fcxu+r9Lpoo/B9ZPPajbuWe2N0+wETzZmL
uzqn6tIjsQVRDIy3aN6K/e5KAppmSlmZ/W2pw+Rezj/EH4VNJoNFa3XCu6O97GPJ
0MdQEpWVsVSZ9vc+uVKYtr3sfCKz+PzwOAUDW4j7NH56+hKCV9c=
=63Be
-END PGP SIGNATURE End Message ---

Bug#873341: Scala Build Tool (sbt) status ?

[Adam Cécile]

Hello,


I need to use sbt tool and from what I see it's very closed being 
included in Debian.


Most of the package are already available in experimental, except 
libscala-tools-sbinary-java



Is there anyway a git or something containing "not-yet-uploaded" package ?


Thanks in advance,


Adam.

Bug#887072: src:libratbag: FTBFS with UnicodeDecodeError

[Stephen Kitt]

Package: src:libratbag
Version: 0.9.901-1
Severity: serious
Justification: FTBFS

Dear Maintainer,

Builds fail with

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 4836: 
ordinal not in range(128)

Regards,

Stephen


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

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

Bug#887070: prometheus-blackbox-exporter FTBFS on armhf/mips*: FAIL github.com/prometheus/blackbox_exporter/prober

[Adrian Bunk]

Source: prometheus-blackbox-exporter
Version: 0.11.0+ds-3
Severity: serious

https://buildd.debian.org/status/package.php?p=prometheus-blackbox-exporter=sid

...
=== RUN   TestTCPConnectionQueryResponseIRC
panic: Error accepting on socket: accept tcp 127.0.0.1:39921: use of closed 
network connection

goroutine 1568 [running]:
github.com/prometheus/blackbox_exporter/prober.TestTCPConnectionQueryResponseStartTLS.func1(0x6036a8,
 0x12075110, 0x124c, 0x47b, 0x7c0, 0x124c0800, 0x68f, 0x7c0, 0x12070480)

/<>/prometheus-blackbox-exporter-0.11.0+ds/obj-arm-linux-gnueabihf/src/github.com/prometheus/blackbox_exporter/prober/tcp_test.go:231
 +0x798
created by 
github.com/prometheus/blackbox_exporter/prober.TestTCPConnectionQueryResponseStartTLS

/<>/prometheus-blackbox-exporter-0.11.0+ds/obj-arm-linux-gnueabihf/src/github.com/prometheus/blackbox_exporter/prober/tcp_test.go:228
 +0x4d8
FAILgithub.com/prometheus/blackbox_exporter/prober  15.831s
dh_auto_test: cd obj-arm-linux-gnueabihf && go test -v -p 4 
github.com/prometheus/blackbox_exporter 
github.com/prometheus/blackbox_exporter/config 
github.com/prometheus/blackbox_exporter/prober returned exit code 1
debian/rules:23: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1

Bug#887069: node-node-uuid installs a broken link and making dependencies like npm broken

[Pirate Praveen]

package: node-node-uuid
version: 1.4.7-1
severity: grave

it also breaks packages that depend on it like npm.


node -e "require('node-uuid');"
module.js:538
throw err;
^

Error: Cannot find module 'node-uuid'
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at [eval]:1:1
at ContextifyScript.Script.runInThisContext (vm.js:50:33)
at Object.runInThisContext (vm.js:139:38)
at Object. ([eval]-wrapper:6:22)
at Module._compile (module.js:635:30)
at evalScript (bootstrap_node.js:462:27)


It is installing a broken link. Adding a simple require test can find
such errors (npm2deb adds such tests by default).

ls -l /usr/lib/nodejs/node-uuid/index.js lrwxrwxrwx 1 root root 48 Jan
11 01:54 /usr/lib/nodejs/node-uuid/index.js ->
../../../share/javascript/node-uuid/node-uuid.js



signature.asc
Description: OpenPGP digital signature

Bug#887068: psi4 FTBFS: cp: cannot stat 'builddir/doc/sphinxman/html': No such file or directory

[Adrian Bunk]

Source: psi4
Version: 1:1.1-4
Severity: serious

https://buildd.debian.org/status/package.php?p=psi4=sid

...
mkdir -p debian/tmp/usr/share/doc/psi4/examples
cp -a builddir/doc/sphinxman/html /<>/debian/tmp/usr/share/doc/psi4
cp: cannot stat 'builddir/doc/sphinxman/html': No such file or directory
debian/rules:29: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1

Bug#887067: snapd FTBFS on i386: FAIL: devicestate_test.go:766: deviceMgrSuite.TestDoRequestSerialErrorsOnNoHost

[Adrian Bunk]

Source: snapd
Version: 2.30-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=snapd=i386=2.30-3=1515462684=0

...
--
FAIL: devicestate_test.go:766: deviceMgrSuite.TestDoRequestSerialErrorsOnNoHost

devicestate_test.go:808:
c.Check(chg.Status(), Equals, state.ErrorStatus)
... obtained state.Status = 3 ("Doing")
... expected state.Status = 9 ("Error")

OOPS: 45 passed, 1 skipped, 1 FAILED
--- FAIL: TestDeviceManager (6.75s)
FAIL
exit status 1
FAILgithub.com/snapcore/snapd/overlord/devicestate  7.107s
AppArmor status: apparmor not enabled

Processed: fixed 886990 in 2.84-0.2+deb8u1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # pending for DSA
> fixed 886990 2.84-0.2+deb8u1
Bug #886990 [src:transmission] transmission: rpc session-id mechanism design 
flaw results in RCE
The source 'transmission' and version '2.84-0.2+deb8u1' do not appear to match 
any binary packages
Marked as fixed in versions transmission/2.84-0.2+deb8u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#880869: marked as done (libratbag FTBFS with meson 0.43.0: Invalid kwargs for option "udev-dir": "default")

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 12:34:48 +
with message-id 
and subject line Bug#880869: fixed in libratbag 0.9.901-1
has caused the Debian Bug report #880869,
regarding libratbag FTBFS with meson 0.43.0: Invalid kwargs for option 
"udev-dir": "default"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
880869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libratbag
Version: 0.9-2
Severity: serious

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

...
The Meson build system
Version: 0.43.0
Source dir: /build/1st/libratbag-0.9
Build dir: /build/1st/libratbag-0.9/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson_options.txt, line 1, column 0:
Invalid kwargs for option "udev-dir": "default"
--- End Message ---
--- Begin Message ---
Source: libratbag
Source-Version: 0.9.901-1

We believe that the bug you reported is fixed in the latest version of
libratbag, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libratbag package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jan 2018 13:19:09 +0100
Source: libratbag
Binary: liblur3 liblur-dev lur-command libratbag-tools ratbagd
Architecture: source
Version: 0.9.901-1
Distribution: experimental
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 liblur-dev - Logitech Unifying Receiver access library - dev files
 liblur3- Logitech Unifying Receiver access library
 libratbag-tools - configuration tools for gaming mice (transitional package)
 lur-command - Logitech Unifying Receiver control tool
 ratbagd- D-Bus daemon handling mouse configuration
Closes: 880869
Changes:
 libratbag (0.9.901-1) experimental; urgency=medium
 .
   * New upstream pre-release, including the Meson 0.43 fix. Closes:
 #880869.
   * Switch to debhelper compatibility level 11.
   * Standards-Version 4.1.3, no further change required.
Checksums-Sha1:
 c7c6cc08e6c44005e116e5476fc0a2fb7c48b25a 2299 libratbag_0.9.901-1.dsc
 46c359caf5aa64113a9ce484146956d75de0c948 901070 libratbag_0.9.901.orig.tar.gz
 4284d9f45a6d67a056cb330f7b0ba9fb68134759 4804 libratbag_0.9.901-1.debian.tar.xz
 a68e9631ed76dd11b360218e5d3415889cd00f86 8637 
libratbag_0.9.901-1_source.buildinfo
Checksums-Sha256:
 68b463c7ef58dc03a07c7b2816a8425ac4379cb3d5d68b73ff64f444ad2d86bd 2299 
libratbag_0.9.901-1.dsc
 fe432cdcc8ce6e6b33d1dea4b8d94997cb8e89b1eaab52e723fcc60c35e5d17b 901070 
libratbag_0.9.901.orig.tar.gz
 be46f0e40992d0ee3095511c80116b58d776c8878a3894d99e9fb8b45c138136 4804 
libratbag_0.9.901-1.debian.tar.xz
 6c91137e048f9ba0202426f4456674bc5bbea989cfd716a259f8c7b7c3700c2a 8637 
libratbag_0.9.901-1_source.buildinfo
Files:
 0d8487051485bcd5a194a9c25ca632a3 2299 libs optional libratbag_0.9.901-1.dsc
 8a07866d58ef88d860118ba7922d6a41 901070 libs optional 
libratbag_0.9.901.orig.tar.gz
 eb9ec19746983956ef08cc0c426ca09f 4804 libs optional 
libratbag_0.9.901-1.debian.tar.xz
 15b03c8beb31d2f7ead864a826529879 8637 libs optional 
libratbag_0.9.901-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlpZ+VUACgkQgNMC9Yht
g5zUpQ/+OWj6HmqFg0usU25A9c7ow9Fz7wiGLvWXpS2KuDVIYkznvx7GXtTziJhy
rjStGQs9wnPSYydmb9SJPuS/M9DRDSFn6+APOcrBRalrjX9mtwDgB4kENXsOjQuD
9f+BlUNPjjIq1pwv370M07m0OjQoqdRptXM47c7Vj0ms59RWFvp7HDoKwXaHDcNb
I9shQ/OZLBjU7yE61jINHFvZAJKFtKmuKZxWoOOIy/PTWDuLXLEHGqqP2BoTxn+x
85A+1NeAbAmgLPzuHs9noqTkS4gYOqTk2EdK3I96AoMwHDvrrNtv/P96Xj64iJo/
BTVcRgIuH7oTtLsRJTzAv1XVGYWWKrOzZ4a21HYx4tSf7iSPQyURU48rNgpCTJTR
LDWR+tro1IdSqanHmvd/X+jxeYtVJdBQFp/EL3QLOeLq3Lk4zanCNE2M7iQ2Xlcl
10en9Y2L/jeVEiRhX1I05WJ6XRHgBR6yCTOJWeehSb/hAsCgnzyuE5i0zuPzAMiy
cpnBX41ByHPnpr8lZiDK750h4U7Wg/dGIipejQhn9OT5CXIXX/ZMzgEa7EQi6hxB
40L5Vp9OiYYEVSVN9RAOfb2vQuZihYJnCBx7CPmUhIsLwsCWSdhc21+DscFPpMSY
hl33NFdWdOOv0llViMRQo9Wak/bMNfbHOoQYLuWCrL7UguuLjyo=
=O3J6

Bug#881301: marked as pending

[Mike Hommey]

On Sat, Jan 13, 2018 at 11:35:08AM +, Simon McVittie wrote:
> On Sat, 13 Jan 2018 at 08:50:14 +0900, Mike Hommey wrote:
> > When can this reach unstable? Somehow, I've started hitting this bug
> > yesterday
> 
> Huh. Did you recently enable any new Shell extensions, or update
> existing extensions, or anything like that?

I've had extensions enabled for a while, and reading this bug I disabled
them all. That didn't stop.

What /does/ seem to have stopped it is me killing my script that
overwrites the background image every ~10 minutes. But I've been running
that for well over a year.

Mike

Bug#881301: marked as pending

[Simon McVittie]

On Sat, 13 Jan 2018 at 08:50:14 +0900, Mike Hommey wrote:
> When can this reach unstable? Somehow, I've started hitting this bug
> yesterday

Huh. Did you recently enable any new Shell extensions, or update
existing extensions, or anything like that?

I'll upload the new Shell and gjs when I next have time to do builds and
uploads, hopefully today.

smcv

Bug#856082: marked as done (libao: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jan 2018 10:49:20 +
with message-id <e1eajni-000c3j...@fasolo.debian.org>
and subject line Bug#856082: fixed in libao 1.2.2+20180113-1
has caused the Debian Bug report #856082,
regarding libao: Please drop the (build-)dependency against esound
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
856082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libao
Version: 1.2.2-1
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: libao
Source-Version: 1.2.2+20180113-1

We believe that the bug you reported is fixed in the latest version of
libao, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ron Lee <r...@debian.org> (supplier of updated libao package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Jan 2018 20:28:42 +1030
Source: libao
Binary: libao4 libao-dev libao-dbg libao-common
Architecture: source all amd64
Version: 1.2.2+20180113-1
Distribution: unstable
Urgency: medium
Maintainer: Ron Lee <r...@debian.org>
Changed-By: Ron Lee <r...@debian.org>
Description:
 libao-common - Cross Platform Audio Output Library (Common files)
 libao-dbg  - Cross Platform Audio Output Library Debug Symbols
 libao-dev  - Cross Platform Audio Output Library Development
 libao4 - Cross Platform Audio Output Library
Closes: 638741 856082
Changes:
 libao (1.2.2+20180113-1) unstable; urgency=medium
 .
   * Cherry pick upstream fix for the pulse plugin, and proposed upstream patch
 to better sanity check all memory allocations.
   * Don't build the esd plugin anymore, the GNOME maintainers want to kill off
 esound for Buster.  Closes: #856082
   * Build for multiarch.  Closes: #638741
Checksums-Sha1:
 8ec8b654ca942f92243b471b336455fef8fc7b8b 2114 libao_1.2.2+20180113-1.dsc
 7e2840ac21a426fface56e0bef6e86e3411d6dcb 477155 
libao_1.2.2+20180113.orig.tar.gz
 df20683d172b6656a317a25c7c1072bdba338d6c 7147 libao_1.2.2+20180113-1.diff.gz
 dbf1a2f3da906839367e57c364306805f9ebb127 11584 
libao-common_1.2.2+20180113-1_all.deb
 7546d6323e1d6f3748f26eafd26fc9a50c82cd3f 93164 
libao-dbg_1.2.2+20180113-1_amd64.deb
 9027ddaa42660eff35e98aed9daef709e5426372 28784 
libao-dev_1.2.2+20180113-1_amd64.deb
 7ca1961ee62dc62f9a5a389ab23ddcc90d49e73b 39772 
libao4_1.2.2+20180113-1_amd64.deb
 fc2aebefcd4b227c69a9ddc276c0b301fbbc9fe2 8162 
libao_1.2.2+20180113-1_amd64.buildinfo
Checksums-Sha256:
 b7f329052c4e060050f7dc817d43ffd47256275220ebfc4979a3d24e0e047dda 2114 
libao_1.2.2+20180113-1.dsc
 cc9e68134e74f62a1feb6d07e4a0fb565351d80205d1e5d48d540b6abc4cf07d 477155 
libao_1.2.2+20180113.orig.tar.gz
 7ff5a332e241f63a6f602a4840ed0c0c83b2152460020c4da5f122404435 7147 
libao_1.2.2+20180113-1.diff.gz
 c391b030a159eef94a1bba42efdc55877a23630a9fdeb6b8ebdb75cba4baeb74 11584 
libao-common_1.2.2+20180113-1_all.deb
 d8717d74f8d12019cb94f14f04dbc18f1c35c41d6b0712ffcd062b960715b9bc 93164 
libao-dbg_1.2.2+20180113-1_amd64.deb
 62cb67572544e5b647192ee48601b831285915ca2692b95dd1b280f3d2733570 28784 
libao-dev_1.2.2+20180113-1_amd64.deb
 4a1a1aff98d9f1e7c9a89fcd9873bedf58a501c09f3e4e293d024c438a22caf2 39772 
libao4_1.2.2+20180113-1_amd64.deb
 e55edcb8eec2f53521d11b1b22b6c8413e3220aebcb5e7fa6513f6eda51cb600 8162 
libao_1.2.2+20180113-1_amd64.buildinfo
Files:
 993e6780dad2b4fe9c330ade26c15e60 2114 libs optional libao_1.2.2+20180113-1.dsc
 0c324623e93fd43a932a71606e897280 477155 libs optional 
libao_1.2.2+20180113.orig.tar.gz
 f9b0d69230e96ef07ef792cb546e468c 7147 libs optional 
libao_

Processed: fixed 886990 in 2.92-2+deb9u1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # pending via DSA but bug closer not added
> fixed 886990 2.92-2+deb9u1
Bug #886990 [src:transmission] transmission: rpc session-id mechanism design 
flaw results in RCE
The source 'transmission' and version '2.92-2+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions transmission/2.92-2+deb9u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887062: [Pkg-raspi-maintainers] Bug#887062: raspi3-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

[Michael Stapelberg]

The only change that seems in any way related to me is
https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/commit/?id=c977f0210ab5c577b9d5296e4e4391225a7f85ca

Have a look at the log at
https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/

I only have bandwidth to support the Debian raspi3 image, and I wasn’t even
aware of any other usages of this package. I’ll have to rely on external
contributions to fix this issue. Thanks.

On Sat, Jan 13, 2018 at 10:34 AM, Raphaël Hertzog 
wrote:

> Package: raspi3-firmware
> Version: 1.20171201-2
> Severity: serious
> User: de...@kali.org
> Usertags: origin-kali
>
> My dailay builds of Kali armhf live images are now failing with this
> version of
> raspi3-firmware with this error:
>
> Setting up raspi3-firmware (1.20171201-2) ...
> cp: cannot create regular file '/boot/firmware/bootcode.bin': No such file
> or directory
> dpkg: error processing package raspi3-firmware (--configure):
>
> I did not check the code but it looks like it assumes that /boot/firmware/
> does exist
> while it doesn't (at least not in the context of the chroot where the live
> image is being built).
>
> This was working fine a few days ago with the previous version that was in
> testing
> (1.20171006-1, Kali is based on Debian Testing).
>
> Cheers,
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers oldoldstable
>   APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'),
> (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> ___
> Pkg-raspi-maintainers mailing list
> pkg-raspi-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers
>



-- 
Best regards,
Michael

Processed: severity of 827297 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 827297 important
Bug #827297 [deborphan] deborphan: No support for versioned provides
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
827297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 859263 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 859263 normal
Bug #859263 [bash] maintain PIE enabled bash
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
859263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887062: raspi3-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

[Raphaël Hertzog]

Package: raspi3-firmware
Version: 1.20171201-2
Severity: serious
User: de...@kali.org
Usertags: origin-kali

My dailay builds of Kali armhf live images are now failing with this version of
raspi3-firmware with this error:

Setting up raspi3-firmware (1.20171201-2) ...
cp: cannot create regular file '/boot/firmware/bootcode.bin': No such file or 
directory
dpkg: error processing package raspi3-firmware (--configure):

I did not check the code but it looks like it assumes that /boot/firmware/ does 
exist
while it doesn't (at least not in the context of the chroot where the live
image is being built).

This was working fine a few days ago with the previous version that was in 
testing
(1.20171006-1, Kali is based on Debian Testing).

Cheers,

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

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

Processed: bug 876541 is forwarded to https://github.com/thsmi/sieve/issues/67

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 876541 https://github.com/thsmi/sieve/issues/67
Bug #876541 [xul-ext-sieve] "SyntaxError: missing ] after element list" in 
SieveFilterEditor.js (fixed upstream 0.2.3k)
Set Bug forwarded-to-address to 'https://github.com/thsmi/sieve/issues/67'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
876541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems