Bug#894832: marked as done (CVE-2018-1002150)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 10:34:59 +0200
with message-id <20180408083459.GA23589@eldamar.local>
and subject line Re: Bug#894832: CVE-2018-1002150
has caused the Debian Bug report #894832,
regarding CVE-2018-1002150
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.)


-- 
894832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: koji
Severity: grave
Tags: security

http://www.openwall.com/lists/oss-security/2018/04/04/1

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Control: forwarded -1 https://pagure.io/koji/issue/850

Hi

There is some further information on that issue in the upstrema bug at
https://pagure.io/koji/issue/850 and the
https://docs.pagure.org/koji/CVE-2018-1002150/ . Versions prior to
1.12.0 are not vulnerable because they do not have the dist-repo
feature.

Regards,
Salvatore--- End Message ---

Bug#895149: marked as done (cinnamon-screensaver: Fails to lock the screen if a menu is selected)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:47:11 +0200
with message-id <6340e52e12a36d88d0a65ff83cc94...@debian.org>
and subject line Bug#895149: cinnamon-screensaver: Fails to lock the screen if 
a menu  is selected
has caused the Debian Bug report #895149,
regarding cinnamon-screensaver: Fails to lock the screen if a menu is selected
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.)


-- 
895149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cinnamon-screensaver
Version: 3.6.1-2
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I found that cinnamon-screensaver does not start if a window menu is clicked.
This can be a security problem as users unaware of this can leave their
computer unlocked unwillingly if they clicked a menu before abandoning or
trusting that their computer will be locked.

To reproduce this, just click the "File" menu in a window. For example, gnome-
terminal's "File" menu.

Starting cinnamon-screensaver in a terminal and looking at its log, I see the
following when the screensaver tries to start:



couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab mouse
couldn't grab mouse
couldn't grab mouse
couldn't grab mouse
Can't fade in screensaver, unable to grab the keyboard

.

If I unselect the "File" menu and wait for the screensaver to trigger again, it
is then able to do it.

I'm reporting this as a security issue but I understand having this exploited
is somewhat unlikely: it would require the attacker to somehow make (or wait
for) the victim to click a menu and ensuring that he leaves his computer
unlocked and unattended without noticing the screen lock was not triggered.

Thanks and best regards,
Luís Picciochi Oliveira



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

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

Versions of packages cinnamon-screensaver depends on:
ii  cinnamon-desktop-data   3.6.2-2
ii  gir1.2-accountsservice-1.0  0.6.45-1
ii  gir1.2-cinnamondesktop-3.0  3.6.2-2
ii  gir1.2-gkbd-3.0 3.26.0-3
ii  gir1.2-glib-2.0 1.56.0-2
ii  gir1.2-gtk-3.0  3.22.29-2
ii  gir1.2-xapp-1.0 1.0.4-2
ii  iso-flags-png-320x240   1.0.1-1
ii  libc6   2.27-3
ii  libcscreensaver03.6.1-2
ii  libglib2.0-02.56.0-4
ii  libgtk-3-0  3.22.29-2
ii  python3 3.6.4-1
ii  python3-gi  3.28.1-1
ii  python3-gi-cairo3.28.1-1
ii  python3-setproctitle1.1.10-1+b1
ii  python3-xapp1.0.1-1
ii  python3-xlib0.20-3

Versions of packages cinnamon-screensaver recommends:
pn  cinnamon-screensaver-x-plugin  

Versions of packages cinnamon-screensaver suggests:
pn  cinnamon-screensaver-webkit-plugin  

-- no debconf information
--- End Message ---
--- Begin Message ---

Hi!

I found that cinnamon-screensaver does not start if a window menu is 
clicked.


This is a known issue with X11.  All screensavers running under X are 
affected.  The only solution is to move to Wayland (cinnamon does not 
yet support Wayland, but I hope it will happen in the not so distant 
future).


See for example this very old gnome-screensaver bug, where there is some 
discussion of the issue:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579

This is the existing bug of the X11 package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514036

The issue is that the screensaver should grab the keyboard and mouse 
before starting, and when there's an X11 popup, the popup holds keyboard 
and mouse, not allowing the screensaver to do it.



This can be a security problem as users unaware of this can leave their
computer unlocked unwillingly if they clicked a menu before abandoning 
or

trusting that their computer will be locked.


There are plenty of things that could cause your screensaver not to 
start (on top of this one, the key combination that triggers it can 
sometimes be received by a different program, you could have a video 
playing on one screen, preventing the 

Bug#831975: marked as done (ci.debian.net: Run test for packages in suites other than unstable)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 09:23:23 +0200
with message-id 
and subject line Re: ci.debian.net: Run test for packages in suites other than 
unstable
has caused the Debian Bug report #831975,
regarding ci.debian.net: Run test for packages in suites other than unstable
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.)


-- 
831975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debci
Version: 1.3
Severity: wishlist

Dear Terceiro,

As discussed during Debconf16, it would be great if ci.debian.net also
runs tests for packages in suites other than unstable. This could
include experimental, stable{,-proposed-updates}, oldstable and so on.

Thanks!

Santiago
--- End Message ---
--- Begin Message ---
On Thu, 15 Mar 2018 10:53:11 +0100 Paul Gevers  wrote:
> The API branch of debci¹ has just been merged into the master branch,
> and deployment on ci.d.n is pending. After deployment this is possible
> and in fact will be triggered by britney soon. Every DD should be able
> to trigger tests in other suits as well, see ².
> 
> Paul
> 
> ¹ https://salsa.debian.org/ci-team/debci
> ² https://staging-ci.debian.net/doc/file.API.html

As announced on debian-release@l.d.o³, I have started to run a shadow
britney until the changes have been merged. So, let's close this bug.

Paul

³ https://lists.debian.org/debian-release/2018/04/msg5.html



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#895077: marked as done (freeradius: Please replace 'c_rehash' with 'openssl rehash')

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 15:42:37 +0200
with message-id 

Bug#885663: marked as done (gnucash-docs: Please drop Build-Depends on rarian-compat)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:21:15 +
with message-id 
and subject line Bug#885663: fixed in gnucash-docs 2.6.19-1
has caused the Debian Bug report #885663,
regarding gnucash-docs: 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.)


-- 
885663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash-docs
Version: 2.6.17-1
Severity: important
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 from gnucash-docs' Build-Depends. You'll also
need to add a Build-Depends on docbook-xml.

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: gnucash-docs
Source-Version: 2.6.19-1

We believe that the bug you reported is fixed in the latest version of
gnucash-docs, 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.
Dmitry Smirnov  (supplier of updated gnucash-docs 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: Sun, 08 Apr 2018 21:05:11 +1000
Source: gnucash-docs
Binary: gnucash-docs
Architecture: source all
Version: 2.6.19-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash-docs - Documentation for gnucash, a personal finance tracking program
Closes: 885663
Changes:
 gnucash-docs (2.6.19-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depends += "docbook-xml".
   * Removed "rarian-compat" from Build-Depends (Closes: #885663).
 Thanks, Jeremy Bicha.
   * Standards-Version: 4.1.4.
   * debhelper & compat to version 11.
Checksums-Sha1:
 5147430afb5e719ab67293bcab1d1d94577a 1953 gnucash-docs_2.6.19-1.dsc
 f09f3d718887943602067609bec607fbed6ee05e 92214378 
gnucash-docs_2.6.19.orig.tar.gz
 ff547294cf684682047ac0c9e06018e2ba784906 13108 
gnucash-docs_2.6.19-1.debian.tar.xz
 4e89aa6521d4c57d5069b5e797e90749c32f4a1e 115114068 
gnucash-docs_2.6.19-1_all.deb
 ade3f5df428fedf82d9d20cde92df83151f35d76 7557 
gnucash-docs_2.6.19-1_amd64.buildinfo
Checksums-Sha256:
 384cd9202dd77a11aaa3bc028262268962c2e4a9d990ec0593d65db838532fca 1953 
gnucash-docs_2.6.19-1.dsc
 268415157d80ea70f339e74d1bd05e4550d36f77b22aa98aadeadec04a4ba9c7 92214378 
gnucash-docs_2.6.19.orig.tar.gz
 b2e2eb5b5a935644d735af20574518af6c9d610a35d980f7a8e6d45286786f80 13108 
gnucash-docs_2.6.19-1.debian.tar.xz
 92c39801f6631c635ef8de927ff3b16765d8f8e876bf37d6660a33e156f8bf57 115114068 
gnucash-docs_2.6.19-1_all.deb
 85ce1849283321bbc40a53467b49dd70e5960313c07d2c77ca6ee65575b27aef 7557 
gnucash-docs_2.6.19-1_amd64.buildinfo
Files:
 02720ee609ace5c141d2bf1d4ac8baff 1953 doc optional gnucash-docs_2.6.19-1.dsc
 f45d36089315ff3fb2be86414560968b 92214378 doc optional 
gnucash-docs_2.6.19.orig.tar.gz
 8352cc69cfc5ecca6c3198a6e57f4401 13108 doc optional 
gnucash-docs_2.6.19-1.debian.tar.xz
 09d48bcc183fd213c4617dbc4427e721 115114068 doc optional 
gnucash-docs_2.6.19-1_all.deb
 f17cbd66344ee8e055a406eaebda9d4c 7557 doc optional 
gnucash-docs_2.6.19-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlrJ/RcACgkQUra72VOW
jRvDQhAAggjLDFHOve89CnsSr7GJsTm/f8xkualXqFIa6Kl/HQjQLTAeSiPf6AJz
NrfsyVOWkyK1UcrTnXuM/qmX7DuqCIkHskkiN20YgbiZGzUhomyuDIES9QeGpHJ5
Nck5l/y6RPZ1znMHQhWmx60U6kHPoLWRMvUmiwjzDMiu/aOzN4gcKTSABb3jaJgz
9/UtzAj/OnF4ZcBkiMBuys1CCZO/cIG68DpXhuwEWEGFNFWDyxoj1UQyLf6BOzG9
BAcq7PKUV4GHf9XKe6Juyp8xWS5vtor90GCuaGtzAUPXRpauQvx1Bv+lKHWC8135

Bug#895174: marked as done (glib2.0 FTBFS: fails to execute ninja)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:05:17 +
with message-id 
and subject line Bug#895174: fixed in debhelper 11.2.1
has caused the Debian Bug report #895174,
regarding glib2.0 FTBFS: fails to execute ninja
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.)


-- 
895174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.56.0-6
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 FTBFS during dh_auto_clean. Including the full build log:

| dpkg-buildpackage: info: source package glib2.0
| dpkg-buildpackage: info: source version 2.56.0-6
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Simon McVittie 
|  dpkg-source --before-build glib2.0-2.56.0
| dpkg-buildpackage: info: host architecture amd64
|  debian/rules clean
| dh clean --with gnome,python3
|dh_auto_clean
|   LC_ALL=C.UTF-8 ninja clean
| Can't exec "ninja": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 356.
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean failed to execute: No child 
processes
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean returned exit code 10
| make: *** [debian/rules:24: clean] Error 2
| dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

I guess this is connected to debhelper 11.2 (as the failure surfaced
close to the upload). Since I'm unsure whether this is a debhelper or
glib2.0 problem, I'm filing it with glib2.0 and trust that you know how
to reassign.

Helmut
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2.1

We believe that the bug you reported is fixed in the latest version of
debhelper, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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: Sun, 08 Apr 2018 08:47:35 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 895174 895181
Changes:
 debhelper (11.2.1) unstable; urgency=medium
 .
   * Buildsystem.pm: Correctly pass build directory values to
 target buildsystems.  Thanks to Helmut Grohne, Adrian Bunk
 and Tobias Frost for the reports and debugging.
 (Closes: #895174, #895181)
   * Buildsystems: Avoid choosing a build system for the clean
 step if it is not necessary.  Previously, debhelper could
 choose a "random" build system that would prefer building
 in a separate build directory on the basis that the build
 directory should be removed.  With this, change we only
 choose such a build system if there is a build directory
 to remove.
Checksums-Sha1:
 ddf845168510585021d9299e618f63b0b0d4eaab 1689 debhelper_11.2.1.dsc
 e1626da376d6e594e262cdbde3914a9c2e103777 456036 debhelper_11.2.1.tar.xz
 2d58c4211d38e4198f41638727657115664f8c46 4554 debhelper_11.2.1_source.buildinfo
Checksums-Sha256:
 2380aee11355a444da3e9f17bcefcd8c4063c65a7df6a6176742b3911310cec7 1689 
debhelper_11.2.1.dsc
 d969476a748f024381fa985813ac444eddd73995700109c3f304de711251010b 456036 
debhelper_11.2.1.tar.xz
 5a862896d758a8f26b8b2ac9b3ce83971ef4aef2da9c0743686385fdd24dc4d1 4554 
debhelper_11.2.1_source.buildinfo
Files:
 f958818ca0108a2b038f2d766d218e45 1689 devel optional debhelper_11.2.1.dsc
 34eb8e89f848e2bc39b9c4072938b036 456036 devel optional debhelper_11.2.1.tar.xz
 727b2c114df3d57747b7a2bc8be3233a 4554 devel optional 
debhelper_11.2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlrJ12cACgkQBUu7n32A
ZEISURAAsaLrgp4F28ct/an0rwWzXhWOiIYN4e4YSUTdMLp5r4b5CsxymluesU9+

Bug#895181: marked as done (debhelper: cmake-based projects broken)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:05:17 +
with message-id 
and subject line Bug#895181: fixed in debhelper 11.2.1
has caused the Debian Bug report #895181,
regarding debhelper: cmake-based projects broken
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.)


-- 
895181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.2
Severity: serious

Dear Maintainer,

since yesterday evening all cmake-based projects fails to compile.
Symptom is that it looks like that debhelper skips the build step.

Example buildlogs are for my expermential builds of cppds:
https://buildd.debian.org/status/package.php?p=cppdb=experimental

Locally, I can reproduce this behaviour also on my other packages
employing cmake (e.g dhewm3, rbfdoom3): it works with 11.1.6, it breaks
with 11.2.

--
tobi

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf17
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.5
ii  dpkg-dev 1.19.0.5
ii  file 1:5.32-2
ii  libdpkg-perl 1.19.0.5
ii  man-db   2.8.3-1
ii  perl 5.26.1-5
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  
pn  dwz  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2.1

We believe that the bug you reported is fixed in the latest version of
debhelper, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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: Sun, 08 Apr 2018 08:47:35 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 895174 895181
Changes:
 debhelper (11.2.1) unstable; urgency=medium
 .
   * Buildsystem.pm: Correctly pass build directory values to
 target buildsystems.  Thanks to Helmut Grohne, Adrian Bunk
 and Tobias Frost for the reports and debugging.
 (Closes: #895174, #895181)
   * Buildsystems: Avoid choosing a build system for the clean
 step if it is not necessary.  Previously, debhelper could
 choose a "random" build system that would prefer building
 in a separate build directory on the basis that the build
 directory should be removed.  With this, change we only
 choose such a build system if there is a build directory
 to remove.
Checksums-Sha1:
 ddf845168510585021d9299e618f63b0b0d4eaab 1689 debhelper_11.2.1.dsc
 e1626da376d6e594e262cdbde3914a9c2e103777 456036 debhelper_11.2.1.tar.xz
 2d58c4211d38e4198f41638727657115664f8c46 4554 debhelper_11.2.1_source.buildinfo
Checksums-Sha256:
 2380aee11355a444da3e9f17bcefcd8c4063c65a7df6a6176742b3911310cec7 1689 
debhelper_11.2.1.dsc
 d969476a748f024381fa985813ac444eddd73995700109c3f304de711251010b 456036 
debhelper_11.2.1.tar.xz
 5a862896d758a8f26b8b2ac9b3ce83971ef4aef2da9c0743686385fdd24dc4d1 4554 
debhelper_11.2.1_source.buildinfo
Files:
 f958818ca0108a2b038f2d766d218e45 1689 devel optional debhelper_11.2.1.dsc
 34eb8e89f848e2bc39b9c4072938b036 456036 devel optional debhelper_11.2.1.tar.xz
 727b2c114df3d57747b7a2bc8be3233a 4554 devel 

Bug#867167: marked as done (chronic: document return value semantics of -e option)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:22:01 +
with message-id 
and subject line Bug#867167: fixed in moreutils 0.62-1
has caused the Debian Bug report #867167,
regarding chronic: document return value semantics of -e option
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.)


-- 
867167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moreutils
Version: 0.60-1
Tags: patch
Severity: wishlist

Dear Maintainer,

Please find attached a trivial documentation patch for chronic.

[[[
diff -ru moreutils-0.60.orig/debian/patches/series 
moreutils-0.60/debian/patches/series
--- moreutils-0.60.orig/debian/patches/series   2017-01-01 21:20:01.0 
+
+++ moreutils-0.60/debian/patches/series2017-07-04 12:30:41.665914021 
+
@@ -1,2 +1,3 @@
 001-is-utf8--allow-hardening-flags.patch
 002-Makefile--call-is-utf8-clean.patch
+003-chronic-document-return-value.patch
diff -ru -N 
moreutils-0.60.orig/debian/patches/003-chronic-document-return-value.patch 
moreutils-0.60/debian/patches/003-chronic-document-return-value.patch
--- moreutils-0.60.orig/debian/patches/003-chronic-document-return-value.patch  
1970-01-01 00:00:00.0 +
+++ moreutils-0.60/debian/patches/003-chronic-document-return-value.patch   
2017-07-04 12:32:48.917252744 +
@@ -0,0 +1,19 @@
+Description: chronic: Document return value semantics of -e
+Author: Daniel Shahaf 
+Bug-Debian: https://bugs.debian.org/-1
+Last-Update: 2017-07-04
+
+--- moreutils-0.60.orig/chronic
 moreutils-0.60/chronic
+@@ -33,8 +33,12 @@ Verbose output (distinguishes between ST
+ 
+ =item -e
+ 
+ Stderr triggering. Triggers output when stderr output length is non-zero.
+ Without -e chronic needs non-zero return value to trigger output.
++
++In this mode, chronic's return value will be C<2> if the command's return
++value is C<0> but the command printed to stderr.
+ 
+ =back
+ 
]]]

Cheers,

Daniel
--- End Message ---
--- Begin Message ---
Source: moreutils
Source-Version: 0.62-1

We believe that the bug you reported is fixed in the latest version of
moreutils, 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.
Nicolas Schier  (supplier of updated moreutils 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: Fri, 06 Apr 2018 22:21:07 +0200
Source: moreutils
Binary: moreutils
Architecture: source amd64
Version: 0.62-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier 
Changed-By: Nicolas Schier 
Description:
 moreutils  - additional Unix utilities
Closes: 697052 867167 885221 893880
Changes:
 moreutils (0.62-1) unstable; urgency=medium
 .
   * New upstream version (0.62):
 + chronic: Flush output more often to better preserve stdout,err ordering.
 + ts: Add -m option to use monotonic clock.
 + ts: Added %.T format like %T but with hi-res.
 + pee: Ignore SIGPIPE and write errors caused by the command not
   consuming all its input. Closes: #697052
 + chronic: document return value semantics of -e option. Closes: #867167
 + vidir: reword man page to more explicit mention 'file' args.
   Closes: #885221
 + pee: Don't buffer input, bringing behavior into line with tee.
   * Remove obsolete is-utf8 patch
   * Mark moreutils Multi-Arch: foreign. Closes: #893880,
 thanks to Helmut Grohne 
   * debian/copyright: update URI: http → https
   * Bump standards to 4.1.3 (no changes required)
   * Use debhelper 11
   * debian/rules: use dpkg-buildflags for hardening
   * parallel: fix minor typo (patch)
   * Use https in homepage URI
   * is_utf8: fix allow-hardening-flags patch
   * Override lintian tag hardening-no-fortify functions for usr/bin/ifne
Checksums-Sha1:
 be7f1cbe8cab4cef06acd76f346c446be24f0d63 1783 moreutils_0.62-1.dsc
 e1167351127aad1d661b987245e619f737a2fc0c 80364 moreutils_0.62.orig.tar.xz
 a7cbd043381c8e6e07b731b8b765dd2a5feed83e 

Processed: Re: Bug#895223: debhelper: Many packages using cmake failed to build from source since upgrade to 11.2

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 11.1.6
Bug #895223 [debhelper] debhelper: Many packages using cmake failed to build 
from source since upgrade to 11.2
No longer marked as found in versions debhelper/11.1.6.
> forcemerge 895181 -1
Bug #895181 {Done: Niels Thykier } [debhelper] debhelper: 
cmake-based projects broken
Bug #895223 [debhelper] debhelper: Many packages using cmake failed to build 
from source since upgrade to 11.2
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions debhelper/11.2.1.
Marked as found in versions debhelper/11.2.
Merged 895181 895223

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

Bug#895169: marked as done (nmu: dune-grid-glue_2.6~20171108-1)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 11:31:46 +0200
with message-id 
and subject line Re: Bug#895169: nmu: dune-grid-glue_2.6~20171108-1
has caused the Debian Bug report #895169,
regarding nmu: dune-grid-glue_2.6~20171108-1
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.)


-- 
895169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu dune-grid-glue_2.6~20171108-1 . ANY . experimental . -m "Rebuild against 
libdune-common-2.6.0"

Dependencies are realized via virtual packages for tracking the abi.


Andreas
--- End Message ---
--- Begin Message ---
On 08/04/18 04:57, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu dune-grid-glue_2.6~20171108-1 . ANY . experimental . -m "Rebuild against 
> libdune-common-2.6.0"
> 
> Dependencies are realized via virtual packages for tracking the abi.

Scheduled.

Emilio--- End Message ---

Bug#894526: marked as done (scikit-learn build depends on the removed python-imaging)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:30:50 +
with message-id 
and subject line Bug#894526: fixed in scikit-learn 0.19.1-4
has caused the Debian Bug report #894526,
regarding scikit-learn build depends on the removed python-imaging
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.)


-- 
894526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn
Version: 0.19.1-3
Severity: serious

The following packages have unmet dependencies:
 builddeps:scikit-learn : Depends: python-imaging but it is not installable

python-pil should be used instead of python-imaging.
--- End Message ---
--- Begin Message ---
Source: scikit-learn
Source-Version: 0.19.1-4

We believe that the bug you reported is fixed in the latest version of
scikit-learn, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated scikit-learn 
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: Sun, 08 Apr 2018 10:02:12 -0400
Source: scikit-learn
Binary: python-sklearn python-sklearn-lib python3-sklearn python3-sklearn-lib 
python-sklearn-doc python-scikits-learn
Architecture: source all amd64
Version: 0.19.1-4
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-scikits-learn - transitional compatibility package for scikits.learn -> 
sklearn m
 python-sklearn - Python modules for machine learning and data mining
 python-sklearn-doc - documentation and examples for scikit-learn
 python-sklearn-lib - low-level implementations and bindings for scikit-learn
 python3-sklearn - Python modules for machine learning and data mining
 python3-sklearn-lib - low-level implementations and bindings for scikit-learn 
- Python
Closes: 894526
Changes:
 scikit-learn (0.19.1-4) unstable; urgency=medium
 .
   * debian/control
 - build-depends on python-pil not deprecating -imaging (Closes: #894526)
Checksums-Sha1:
 a62b475093b5036de635dff7527aa7aa992d4aab 2804 scikit-learn_0.19.1-4.dsc
 1d447f64613248007cbdd720d419d69ab099c1f3 1294852 
scikit-learn_0.19.1-4.debian.tar.xz
 47a712bfa7493e27d0a41e055901aee29bb863f5 85464 
python-scikits-learn_0.19.1-4_all.deb
 c64e210b997ce5e776ad756df18685a6eec765d6 5098876 
python-sklearn-doc_0.19.1-4_all.deb
 06c50a9bd8fc4fa4c2778b25e30beb0616eb7a09 6103932 
python-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 41f9fcaf6616cda8533affedfb26ff9309abef6a 1599380 
python-sklearn-lib_0.19.1-4_amd64.deb
 94cb6702eaa80ed55c0eaf8f35a151ef79278ff3 1455120 
python-sklearn_0.19.1-4_all.deb
 2d04be25cbc2d7d0e0747aa2b5d1ba6c80e38965 6469588 
python3-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 5d82b73007f916ca427352c56378fc28d1032633 1508112 
python3-sklearn-lib_0.19.1-4_amd64.deb
 df8f3b170d9c7b474d813618509f579a1bc1751f 1454884 
python3-sklearn_0.19.1-4_all.deb
 dcc08c1239d79277e002f2fb438f832cc585833c 12614 
scikit-learn_0.19.1-4_amd64.buildinfo
Checksums-Sha256:
 abf03cf5a91a8865736a3f83fa9b2bb00f3cdba28936dea759f7d891d85069c8 2804 
scikit-learn_0.19.1-4.dsc
 3ee7af5c1efe435399ca35a2fcae72955d5d5af6219d146968c374b4a3ec7330 1294852 
scikit-learn_0.19.1-4.debian.tar.xz
 0ed905d6940b4582b1d84a189281aedb2fe2e3a889ef6278ed4eb2b893b2587d 85464 
python-scikits-learn_0.19.1-4_all.deb
 ab54b327af6aa2a51c068e53a9e0d11df812616f8e2d94b3ad620cc1c102975c 5098876 
python-sklearn-doc_0.19.1-4_all.deb
 78fd30eee11400851e3c881825dd7d35bee19941d27d973b64c9a1c142b50ae0 6103932 
python-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 67dee1afec4c9357ab9bd1d752c7c4df3960f841db643064e67e6717671d3514 1599380 
python-sklearn-lib_0.19.1-4_amd64.deb
 cadbfcee2307b681ed720637faf0f0240579a5094909202e7aff2e04bd7fc6a3 1455120 
python-sklearn_0.19.1-4_all.deb
 761f3ab8a3c71beb55d8d7b7ddd3eb48de429023fc5e67b7d2b475b7a4b4d73b 6469588 
python3-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 a062c56219779bcecb1e956d66146e5f31b329819578b50fcdb6a92c4024a773 1508112 

Bug#895145: marked as done (virt-manager: fails to start networks)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:21:50 +
with message-id 
and subject line Bug#895145: fixed in libvirt 4.2.0-2
has caused the Debian Bug report #895145,
regarding virt-manager: fails to start networks
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.)


-- 
895145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virt-manager
Version: 1:1.4.3-1
Severity: important


Hi.

Since the most recent upgrade, when I try to start a network from the GUI:
Error starting network 'main': internal error: Failed to initialize a valid 
firewall backend

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/network.py", line 81, in start
self._backend.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2947, in create
if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirtError: internal error: Failed to initialize a valid firewall backend


Cheers,
Chris


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

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

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  gir1.2-gtk-3.0   3.22.29-3
ii  gir1.2-gtk-vnc-2.0   0.7.2-1
ii  gir1.2-libosinfo-1.0 1.1.0-1
ii  gir1.2-libvirt-glib-1.0  1.0.0-1
ii  gir1.2-vte-2.91  0.52.0-1
ii  librsvg2-common  2.40.20-2
ii  python   2.7.14-4
ii  python-dbus  1.2.6-1
ii  python-gi3.28.1-1
ii  python-gi-cairo  3.28.1-1
ii  python-libvirt   4.0.0-1
ii  python-requests  2.18.4-2
ii  python2.72.7.14-8
ii  virtinst 1:1.4.3-1

Versions of packages virt-manager recommends:
ii  gir1.2-spiceclientglib-2.0  0.34-1.1
ii  gir1.2-spiceclientgtk-3.0   0.34-1.1
ii  libvirt-daemon-system   4.2.0-1

Versions of packages virt-manager suggests:
ii  gir1.2-secret-1  0.18.6-1
ii  gnome-keyring3.28.0.2-1
pn  python-guestfs   
pn  ssh-askpass  
pn  virt-viewer  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.2.0-2

We believe that the bug you reported is fixed in the latest version of
libvirt, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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: Sun, 08 Apr 2018 11:05:14 +0200
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 libnss-libvirt - nss plugin providing IP add ress resolution for virtual 

Bug#817903: marked as done (network-manager: doesn't recognize WPA* Enterprise private key file with .p12 extension)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 17:50:24 +0200
with message-id <333903b9-5d20-bebb-3ebc-4ad85f3f8...@debian.org>
and subject line Re: network-manager: doesn't recognize WPA* Enterprise private 
key file with .p12 extension
has caused the Debian Bug report #817903,
regarding network-manager: doesn't recognize WPA* Enterprise private key file 
with  .p12 extension
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.)


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

Package: network-manager
Version: 1.1.91-1
Severity: normal

Dear Maintainer,

I want to configure a wireless connection provided by
my institution --- meaning that I have no degrees of freedom
in what I have to do to complete the procedure.

That said, the institution gives me two files, a CA certificate

  ca.pem

and a private key file with an associated private key

  wifiCert.p12

I had placed those files in a generic subfolder (~/Documents/.certificates)
and then I tried to configure the connection using Network Manager.

I access the Network Connections window, I Add a new (wireless)
connection, in the Editing New Connection window I access the Wi-Fi
Security tab, select WPA & WPA2 Enterprise from the Security menu, I use
the CA Certificate menu to access the ~/Documents/.certificates folder,
I'm shown the ca.pem file, I select it and proceed, using the Private key
menu, I access ~/Documents/.certificates, at the bottom I see the list of 
correct file extensions (comprising the .p12 extension!) but the file
wifiCert.p12 is not shown (no file at all is shown as selectable).

At his point I cannot complete the configuration.

I have to mention that this is a new laptop (my previuos laptop
has been stolen) and that on my previous laptop I configured the same
wireless network w/o any problem. Previous laptop, btw, was running sid as well.

thank you in advance,
  gb

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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.8-1
ii  init-system-helpers1.29
ii  isc-dhcp-client4.3.3-9
ii  libbluetooth3  5.36-1
ii  libc6  2.22-1
ii  libglib2.0-0   2.46.2-3
ii  libgnutls303.4.9-2
ii  libgudev-1.0-0 230-3
ii  libmm-glib01.4.12-1
ii  libndp01.4-2
ii  libnewt0.520.52.18-3
ii  libnl-3-2003.2.27-1
ii  libnm0 1.1.91-1
ii  libpam-systemd 229-2
ii  libpolkit-agent-1-00.105-14.1
ii  libpolkit-gobject-1-0  0.105-14.1
ii  libreadline6   6.3-8+b4
ii  libsoup2.4-1   2.52.2-1
ii  libsystemd0229-2
ii  libteamdctl0   1.23-1
ii  libuuid1   2.27.1-4
ii  lsb-base   9.20160110
ii  policykit-10.105-14.1
ii  udev   229-2
ii  wpasupplicant  2.3-2.3

Versions of packages network-manager recommends:
ii  crda3.13-1+b1
ii  dnsmasq-base2.75-1
ii  iptables1.6.0-2
ii  iputils-arping  3:20150815-2
ii  modemmanager1.4.12-1
ii  ppp 2.4.7-1+2

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

-- no debconf information--- End Message ---
--- Begin Message ---
Version: 1.2.4-1

This is supposed to be fixed by a new upstream release, thus closing the
bug report.

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#895178: marked as done (libosmocore-dev: missing dependency on libtalloc-dev)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:50:07 +
with message-id 
and subject line Bug#895178: fixed in libosmocore 0.10.2-6
has caused the Debian Bug report #895178,
regarding libosmocore-dev: missing dependency on libtalloc-dev
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.)


-- 
895178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libosmocore-dev
Version: 0.10.2-5
Severity: serious
Control: affects -1 src:libosmo-netif src:libosmo-abis src:openggsn

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libosmo-netif.html

...
make[5]: Entering directory '/build/1st/libosmo-netif-0.0.6/src/channel/abis'
/bin/bash ../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../..  -I../../../include -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Wall -I/usr/include/ -I/usr/include/   -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o ipa_stream_server.lo ipa_stream_server.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include 
-I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -I/usr/include/ 
-I/usr/include/ -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c ipa_stream_server.c  -fPIC -DPIC -o 
.libs/ipa_stream_server.o
In file included from ipa_stream_server.c:8:0:
/usr/include/osmocom/core/talloc.h:5:10: fatal error: talloc.h: No such file or 
directory
 #include 
  ^~
compilation terminated.
Makefile:392: recipe for target 'ipa_stream_server.lo' failed
make[5]: *** [ipa_stream_server.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: libosmocore
Source-Version: 0.10.2-6

We believe that the bug you reported is fixed in the latest version of
libosmocore, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libosmocore 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, 08 Apr 2018 12:05:14 +0100
Source: libosmocore
Binary: libosmocore libosmocodec0 libosmocodec-doc libosmocore9 libosmocore-doc 
libosmogb5 libosmogsm8 libosmogsm-doc libosmovty4 libosmovty-doc libosmoctrl0 
libosmosim0 libosmocore-dev libosmocore-utils
Architecture: source all amd64
Version: 0.10.2-6
Distribution: sid
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 libosmocodec-doc - Documentation for the osmo codec library
 libosmocodec0 - Osmo codec library
 libosmocore - Open Source MObile COMmunications CORE library (metapackage)
 libosmocore-dev - Development headers for Open Source MObile COMmunications 
CORE li
 libosmocore-doc - Documentation for the Osmo Core library
 libosmocore-utils - Utilities for gsm
 libosmocore9 - Osmo Core library
 libosmoctrl0 - Osmo control library
 libosmogb5 - Osmo GPRS GB library
 libosmogsm-doc - Documentation for the Osmo GSM utility library
 libosmogsm8 - Osmo GSM utility library
 libosmosim0 - Osmo SIM library
 libosmovty-doc - Documentation for the Osmo VTY library
 libosmovty4 - Osmo VTY library
Closes: 895178
Changes:
 libosmocore (0.10.2-6) unstable; urgency=medium
 .
   * add dependency of libtalloc-dev to libsomocore-dev (Closes: #895178)
Checksums-Sha1:
 3277d8643d88a4f0134aadd4c221939c81d8fc33 3010 libosmocore_0.10.2-6.dsc
 d838ff0e6566289918b25a7abc90c1a1c370e0a8 543196 libosmocore_0.10.2.orig.tar.xz
 46939750b8537e1e7d115ab937a1cdb50f8b6f3a 17784 
libosmocore_0.10.2-6.debian.tar.xz
 a6a5c196196f8bf53956c1ebb5a96adf385e8235 102276 
libosmocodec-doc_0.10.2-6_all.deb
 044d14f5bb244af4a02a3d82c9d978e996d66f20 6612 
libosmocodec0-dbgsym_0.10.2-6_amd64.deb
 b2e271d548ec36af8e06174fad9da105e2f1e21b 9956 libosmocodec0_0.10.2-6_amd64.deb
 6588e53b3af133ef5432710bd968d8202734b0b6 106692 
libosmocore-dev_0.10.2-6_amd64.deb
 a5454496fbcc94b2fc110e893934a086b2e22928 429888 
libosmocore-doc_0.10.2-6_all.deb
 

Bug#745811: marked as done (/usr/bin/nm-applet: nm-applet: CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 17:51:37 +0200
with message-id <6919fb04-b600-3372-abec-3cc829e24...@debian.org>
and subject line Re: /usr/bin/nm-applet: nm-applet: CRITICAL **: 
nm_secret_agent_register: assertion 'priv->registered == FALSE' failed
has caused the Debian Bug report #745811,
regarding /usr/bin/nm-applet: nm-applet: CRITICAL **: nm_secret_agent_register: 
assertion 'priv->registered == FALSE' failed
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.)


-- 
745811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 0.9.8.8-5
Severity: normal
File: /usr/bin/nm-applet

Dear Maintainer,

With Debian Jessie and XFCE, nm-applet reports:

** (nm-applet:3534): CRITICAL **: nm_secret_agent_register: assertion
'priv->registered == FALSE' failed

Bug already upstream: https://bugzilla.gnome.org/show_bug.cgi?id=727923

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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 1.8.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  gconf-service3.2.6-2
ii  gnome-icon-theme 3.12.0-1
ii  libatk1.0-0  2.12.0-1
ii  libc62.18-4
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libdbus-1-3  1.8.0-3
ii  libdbus-glib-1-2 0.102-1
ii  libgconf-2-4 3.2.6-2
ii  libgdk-pixbuf2.0-0   2.30.6-1
ii  libglib2.0-0 2.40.0-2
ii  libgnome-bluetooth11 3.8.1-2
ii  libgnome-keyring03.4.1-1
ii  libgtk-3-0   3.12.0-4
ii  libmm-glib0  1.0.0-4
ii  libnm-glib-vpn1  0.9.8.8-7
ii  libnm-glib4  0.9.8.8-7
ii  libnm-gtk0   0.9.8.8-5
ii  libnm-util2  0.9.8.8-7
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libsecret-1-00.18-1
ii  network-manager  0.9.8.8-7
ii  policykit-1-gnome0.105-2

Versions of packages network-manager-gnome recommends:
ii  gnome-bluetooth  3.8.1-2
ii  gnome-keyring3.8.2-2+b1
ii  iso-codes3.52-1
ii  mobile-broadband-provider-info   20140317-1
ii  notification-daemon  0.7.6-1
ii  xfce4-notifyd [notification-daemon]  0.2.4-2

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.0-1

This is supposed to be fixed by a new upstream release.
Thus closing this bug report.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#762894: marked as done (directory '/usr/lib/i386-linux-gnu/samba' not empty so not removed)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 11:47:48 +0200
with message-id 

Bug#741492: marked as done (samba: all process have same title (setproctitle not working))

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 11:44:40 +0200
with message-id 

and subject line setproctitle_init used in 4.8
has caused the Debian Bug report #741492,
regarding samba: all process have same title (setproctitle not working)
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.)


-- 
741492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.5+dfsg-1
Severity: minor
Tags: upstream patch

Dear Maintainer,

Process titles remain the same as the parent even though libbsd and
and setproctitle support are correctly detected during package build.

Additionally log.samba contains a number of ominous messages:
samba: setproctitle not initialized, please either call setproctitle_init() or 
link against libbsd-ctor.

Attached patch completes the setproctitle support when using libbsd.
There may be a way to link libbsd-ctor.a and elminiate the extra defines,
but my wscript foo is lacking.

without attached patch:

24650 ?Ss 0:00 /usr/sbin/samba -D
24661 ?S  0:00  \_ /usr/sbin/samba -D
24663 ?Ss 0:00  |   \_ /usr/sbin/smbd -D --option=server role 
check:inhibit=yes --foreground
24715 ?S  0:00  |   \_ /usr/sbin/smbd -D --option=server role 
check:inhibit=yes --foreground
28724 ?S  0:00  |   \_ /usr/sbin/smbd -D --option=server role 
check:inhibit=yes --foreground
24662 ?S  0:00  \_ /usr/sbin/samba -D
24664 ?S  0:00  \_ /usr/sbin/samba -D
24665 ?S  0:00  \_ /usr/sbin/samba -D
24666 ?S  0:00  \_ /usr/sbin/samba -D
24667 ?S  0:00  \_ /usr/sbin/samba -D
24668 ?S  0:00  \_ /usr/sbin/samba -D
24669 ?S  0:00  \_ /usr/sbin/samba -D
24670 ?S  0:00  \_ /usr/sbin/samba -D
24671 ?S  0:00  \_ /usr/sbin/samba -D
24672 ?S  0:00  \_ /usr/sbin/samba -D
24673 ?S  0:00  \_ /usr/sbin/samba -D
24676 ?S  0:00  \_ /usr/sbin/samba -D

with attached patch:

 9660 ?Ss 0:00 /usr/sbin/samba -D
 9697 ?S  0:00  \_ samba: task[s3fs_parent]
 9699 ?Ss 0:00  |   \_ /usr/sbin/smbd -D --option=server role 
check:inhibit=yes --foreground
10126 ?S  0:00  |   \_ /usr/sbin/smbd -D --option=server role 
check:inhibit=yes --foreground
 9698 ?S  0:00  \_ samba: task[dcesrv]
 9700 ?S  0:00  \_ samba: task[nbtd]
 9701 ?S  0:00  \_ samba: task wrepl server_id[9701]
 9702 ?S  0:00  \_ samba: task[ldapsrv]
 9703 ?S  0:00  \_ samba: task[cldapd]
 9704 ?S  0:00  \_ samba: task[kdc]
 9706 ?S  0:00  \_ samba: task[dreplsrv]
 9709 ?S  0:00  \_ samba: task[winbind]
 9710 ?S  0:00  \_ samba: task[ntp_signd]
 9714 ?S  0:00  \_ samba: task[kccsrv]
 9715 ?S  0:00  \_ samba: task[dnsupdate]
 9716 ?S  0:00  \_ samba: task[dns]
--- a/lib/replace/wscript
+++ b/lib/replace/wscript
@@ -265,6 +265,8 @@
 conf.CHECK_FUNCS_IN('getpeereid', 'bsd', headers='sys/types.h bsd/unistd.h')
 if not conf.CHECK_FUNCS_IN('setproctitle', 'bsd', headers='sys/types.h bsd/unistd.h'):
 conf.CHECK_FUNCS_IN('setproctitle', 'setproctitle', headers='setproctitle.h')
+else:
+conf.CHECK_FUNCS_IN('setproctitle_init', 'bsd', headers='sys/types.h bsd/unistd.h')
 
 conf.CHECK_CODE('''
 struct ucred cred;
--- a/lib/replace/replace.c
+++ b/lib/replace/replace.c
@@ -900,3 +900,8 @@
 {
 }
 #endif
+#ifndef HAVE_SETPROCTITLE_INIT
+void rep_setproctitle_init(int argc, const char *argv[], char *envp[])
+{
+}
+#endif
--- a/lib/replace/replace.h
+++ b/lib/replace/replace.h
@@ -898,5 +898,9 @@
 #define setproctitle rep_setproctitle
 void rep_setproctitle(const char *fmt, ...) PRINTF_ATTRIBUTE(1, 2);
 #endif
+#ifndef HAVE_SETPROCTITLE_INIT
+#define setproctitle_init rep_setproctitle_init
+void rep_setproctitle_init(int argc, const char *argv[], char *envp[]);
+#endif
 
 #endif /* _LIBREPLACE_REPLACE_H */
--- a/source4/smbd/server.c
+++ b/source4/smbd/server.c
@@ -509,7 +509,8 @@
 	return 0;
 }
 
-int main(int argc, const char *argv[])
+int main(int argc, const char *argv[], const char *envp[])
 {
+	setproctitle_init(argc, argv, envp);
 	return binary_smbd_main("samba", argc, argv);
 }
--- End Message ---
--- Begin Message ---
Version: 2:4.8.0+dfsg-1

Probably fixed by 4f84b6dfa87964d8b99a45021fa51835c962876c 

Bug#697052: marked as done (moreutils: 'pee' with 'echo' buggy.)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:22:01 +
with message-id 
and subject line Bug#697052: fixed in moreutils 0.62-1
has caused the Debian Bug report #697052,
regarding moreutils: 'pee' with  'echo' buggy.
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.)


-- 
697052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moreutils
Version: 0.47
Severity: normal

Dear Maintainer,

This should print 3 "foo"s, but doesn't:

% echo foo | pee cat echo cat cat | nl -b a
 1  
 2  foo

Discovered the above, while trying to print "hi\nho\n":

% echo hi | pee cat "echo ho"
hi
ho
# add a 'cat' and the order changes.
% echo hi | pee cat "echo ho" cat
ho
hi

HTH...



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages moreutils depends on:
ii  libc62.13-35
ii  libipc-run-perl  0.92-1
ii  perl 5.14.2-12

moreutils recommends no packages.

Versions of packages moreutils suggests:
pn  libtime-duration-perl  
ii  libtimedate-perl   1.2000-1

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: moreutils
Source-Version: 0.62-1

We believe that the bug you reported is fixed in the latest version of
moreutils, 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 697...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Schier  (supplier of updated moreutils 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: Fri, 06 Apr 2018 22:21:07 +0200
Source: moreutils
Binary: moreutils
Architecture: source amd64
Version: 0.62-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier 
Changed-By: Nicolas Schier 
Description:
 moreutils  - additional Unix utilities
Closes: 697052 867167 885221 893880
Changes:
 moreutils (0.62-1) unstable; urgency=medium
 .
   * New upstream version (0.62):
 + chronic: Flush output more often to better preserve stdout,err ordering.
 + ts: Add -m option to use monotonic clock.
 + ts: Added %.T format like %T but with hi-res.
 + pee: Ignore SIGPIPE and write errors caused by the command not
   consuming all its input. Closes: #697052
 + chronic: document return value semantics of -e option. Closes: #867167
 + vidir: reword man page to more explicit mention 'file' args.
   Closes: #885221
 + pee: Don't buffer input, bringing behavior into line with tee.
   * Remove obsolete is-utf8 patch
   * Mark moreutils Multi-Arch: foreign. Closes: #893880,
 thanks to Helmut Grohne 
   * debian/copyright: update URI: http → https
   * Bump standards to 4.1.3 (no changes required)
   * Use debhelper 11
   * debian/rules: use dpkg-buildflags for hardening
   * parallel: fix minor typo (patch)
   * Use https in homepage URI
   * is_utf8: fix allow-hardening-flags patch
   * Override lintian tag hardening-no-fortify functions for usr/bin/ifne
Checksums-Sha1:
 be7f1cbe8cab4cef06acd76f346c446be24f0d63 1783 moreutils_0.62-1.dsc
 e1167351127aad1d661b987245e619f737a2fc0c 80364 moreutils_0.62.orig.tar.xz
 a7cbd043381c8e6e07b731b8b765dd2a5feed83e 11008 moreutils_0.62-1.debian.tar.xz
 13fe57d982c6ff847e07344da95ed4d36e99d8ea 65932 
moreutils-dbgsym_0.62-1_amd64.deb
 9f811130bbf955f16a9855d32245efb6b987e4b6 5905 moreutils_0.62-1_amd64.buildinfo
 beb0c50b74b4b13fa417b6ddae42853f91c703cd 73108 moreutils_0.62-1_amd64.deb
Checksums-Sha256:
 84cd89f47f6af51cf958499dde292c83e4f855f4c5af6f614547094aae78b045 1783 
moreutils_0.62-1.dsc
 ffd0bfb2e490db63355e1a7d168c6f3f9802ee2c5e80880ca632e603b4b67d88 80364 
moreutils_0.62.orig.tar.xz
 9b362cfac2f38af04e65c21a2405edd6cf46ce4fa2bdc48dd733a97f2f729899 11008 

Bug#885221: marked as done (moreutils: vidir: man page does not document meaning of 'vidir I')

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:22:01 +
with message-id 
and subject line Bug#885221: fixed in moreutils 0.62-1
has caused the Debian Bug report #885221,
regarding moreutils: vidir: man page does not document meaning of 'vidir 
I'
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.)


-- 
885221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moreutils
Version: 0.60-1
Severity: minor
File: /usr/bin/vidir
Tags: upstream

Dear Maintainer,

vidir(1) reads:

> =head1 SYNOPSIS
> 
> B [--verbose] [directory|file|-] ...

However, the "DESCRIPTION" section does not explain how a I
argument is handled:

> =head1 DESCRIPTION
> 
> vidir allows editing of the contents of directory in a text editor. If no
> directory is specified, the current directory is edited. 
> 
> When editing a directory, each item in the directory will appear on its own
> numbered line. These numbers are how vidir keeps track of what items are
> changed. Delete lines to remove files from the directory, or
> edit filenames to rename files. You can also switch pairs of numbers to
> swap filenames.
> 
> Note that if "-" is specified as the directory to edit, it reads a list of
> filenames from stdin and displays those for editing. Alternatively, a list
> of files can be specified on the command line.

I'm guessing that «vidir *.jpeg» is for renaming/deleting just *.jpeg
files, but that's not clear from the text.

Cheers,

Daniel

P.S. As a separate / secondary issue, it would also be nice if the
"DESCRIPTION" used B<>/I<>/C<> POD markup around the terms "directory"
and "file" when they are used not as common nouns, but to refer to the
placeholders from the synopsis; for example, change

vidir editing the contents of directory.  … the current directory is edited 
…

to

vidir editing the contents of I.  … the current directory is 
edited …
--- End Message ---
--- Begin Message ---
Source: moreutils
Source-Version: 0.62-1

We believe that the bug you reported is fixed in the latest version of
moreutils, 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.
Nicolas Schier  (supplier of updated moreutils 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: Fri, 06 Apr 2018 22:21:07 +0200
Source: moreutils
Binary: moreutils
Architecture: source amd64
Version: 0.62-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier 
Changed-By: Nicolas Schier 
Description:
 moreutils  - additional Unix utilities
Closes: 697052 867167 885221 893880
Changes:
 moreutils (0.62-1) unstable; urgency=medium
 .
   * New upstream version (0.62):
 + chronic: Flush output more often to better preserve stdout,err ordering.
 + ts: Add -m option to use monotonic clock.
 + ts: Added %.T format like %T but with hi-res.
 + pee: Ignore SIGPIPE and write errors caused by the command not
   consuming all its input. Closes: #697052
 + chronic: document return value semantics of -e option. Closes: #867167
 + vidir: reword man page to more explicit mention 'file' args.
   Closes: #885221
 + pee: Don't buffer input, bringing behavior into line with tee.
   * Remove obsolete is-utf8 patch
   * Mark moreutils Multi-Arch: foreign. Closes: #893880,
 thanks to Helmut Grohne 
   * debian/copyright: update URI: http → https
   * Bump standards to 4.1.3 (no changes required)
   * Use debhelper 11
   * debian/rules: use dpkg-buildflags for hardening
   * parallel: fix minor typo (patch)
   * Use https in homepage URI
   * is_utf8: fix allow-hardening-flags patch
   * Override lintian tag hardening-no-fortify functions for usr/bin/ifne
Checksums-Sha1:
 be7f1cbe8cab4cef06acd76f346c446be24f0d63 1783 moreutils_0.62-1.dsc
 e1167351127aad1d661b987245e619f737a2fc0c 80364 moreutils_0.62.orig.tar.xz
 a7cbd043381c8e6e07b731b8b765dd2a5feed83e 11008 moreutils_0.62-1.debian.tar.xz
 

Bug#895084: marked as done (mosquitto: Please replace 'c_rehash' with 'openssl rehash')

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:22:08 +
with message-id 
and subject line Bug#895084: fixed in mosquitto 1.4.15-2
has caused the Debian Bug report #895084,
regarding mosquitto: Please replace 'c_rehash' with 'openssl rehash'
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.)


-- 
895084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mosquitto
Version: 1.4.15-1
Severity: normal
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: c_rehash

This package is using the c_rehash command which is part of the
openssl package. The c_rehash script is considered by upstream as a
fallback script and will disappear at some point. The recommended way
is to use the "openssl rehash" command instead which appeared in
1.1.0. Please make sure that this package does not use the c_rehash
command anymore.

The "openssl rehash" command creates half that many symlinks (one per
certificate instead of two) because it uses only the newer hash.
There is also the -compat option which creates both symlinks (and
behaves like c_rehash currently does). The hash changed from md5 to
sha1 during the 0.9.8 to 1.0.0 transition so I doubt that the
"compat" mode will be required.

Should the c_rehash script be mentioned in the source code or script
of this package but is not used during the build process or in the
final package then feel free to close the bug saying so.

Sebastian 
--- End Message ---
--- Begin Message ---
Source: mosquitto
Source-Version: 1.4.15-2

We believe that the bug you reported is fixed in the latest version of
mosquitto, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger A. Light  (supplier of updated mosquitto 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, 07 Apr 2018 11:16:43 +0100
Source: mosquitto
Binary: mosquitto mosquitto-dev libmosquitto1 libmosquitto-dev libmosquittopp1 
libmosquittopp-dev mosquitto-clients mosquitto-dbg libmosquitto1-dbg 
libmosquittopp1-dbg
Architecture: source
Version: 1.4.15-2
Distribution: unstable
Urgency: low
Maintainer: Roger A. Light 
Changed-By: Roger A. Light 
Description:
 libmosquitto-dev - MQTT version 3.1/3.1.1 client library, development files
 libmosquitto1 - MQTT version 3.1/3.1.1 client library
 libmosquitto1-dbg - debugging symbols for libmosquitto binaries
 libmosquittopp-dev - MQTT version 3.1 client C++ library, development files
 libmosquittopp1 - MQTT version 3.1/3.1.1 client C++ library
 libmosquittopp1-dbg - debugging symbols for libmosquittopp binaries
 mosquitto  - MQTT version 3.1/3.1.1 compatible message broker
 mosquitto-clients - Mosquitto command line MQTT clients
 mosquitto-dbg - debugging symbols for mosquitto binaries
 mosquitto-dev - Development files for Mosquitto
Closes: 895084
Changes:
 mosquitto (1.4.15-2) unstable; urgency=low
 .
   * Replace mentions of 'c_rehash' with 'openssl rehash'. (Closes: #895084).
Checksums-Sha1:
 c7eb6462f8deb207a72ab97045e0ec27d494a0e5 2492 mosquitto_1.4.15-2.dsc
 300b7d345433506a6eb7cb2bbcc0dcfe6f209038 26528 mosquitto_1.4.15-2.debian.tar.xz
 9d11aee55b50bb20f7711e6bd90ba6a51bc7e2ab 6725 
mosquitto_1.4.15-2_source.buildinfo
Checksums-Sha256:
 6061a7f8b6f06949bd305501212811bc5b0b3b5efd1860f811fe5349cf6ed402 2492 
mosquitto_1.4.15-2.dsc
 6b5e5c073ff4262cb062fba8ee3207d02b5e5201d9a70ae33af4ddb29bca9846 26528 
mosquitto_1.4.15-2.debian.tar.xz
 27653f9e33c85d6d2885a8cb4db932a69964b2d1b0b1e62d7bd7a7888d85fc2f 6725 
mosquitto_1.4.15-2_source.buildinfo
Files:
 d1f558362ce34c6d331c00d69b3f3aab 2492 net optional mosquitto_1.4.15-2.dsc
 d57cf699ca90218713b50b70a58fad3c 26528 net optional 
mosquitto_1.4.15-2.debian.tar.xz
 e7f69a00550219ea05a8736aeabbb091 6725 net optional 
mosquitto_1.4.15-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJayeqYAAoJEPNPCXROn13ZJ+kP/2DWC+dacjzFr9a1/ebYgqft
irZn+zzf+mTy+kfQJPlrKIQcGGWmp3E/Tq0fzp2qHmMw+5Ejr/2nmFvmGnUtr8IP

Bug#815005: marked as done (gnucash: dbus-x11 dependency missing (gnucash dconf settings not working on headless machine))

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:19:58 +
with message-id 
and subject line Bug#815005: fixed in gnucash 1:3.0-1
has caused the Debian Bug report #815005,
regarding gnucash: dbus-x11 dependency missing (gnucash dconf settings not 
working on headless machine)
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.)


-- 
815005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnucash
Version: 1:2.6.4-3
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
 
 Installing gnucash on headless machine without desktop environment but 
with x2go-server

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 
 gnucash starts with x2go-client but gnucash settings are not clickable. 
(For example "Tipf of the day" option)

   * What was the outcome of this action?
 options not clickable
   * What outcome did you expect instead?
 clickable options

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

After 
$ aptitude install dbus-x11 
everything works as expected.

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

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

Versions of packages gnucash depends on:
ii  gnucash-common 1:2.6.4-3
ii  guile-2.0  2.0.11+1-9
ii  guile-2.0-libs 2.0.11+1-9
ii  libaqbanking34 5.4.3beta-2+b1
ii  libaqbanking34-plugins 5.4.3beta-2+b1
ii  libc6  2.19-18+deb8u3
ii  libcairo2  1.14.0-2.1
ii  libcrypt-ssleay-perl   0.58-1+b2
ii  libdate-manip-perl 6.47-1
ii  libdbi10.9.0-4
ii  libfinance-quote-perl  1.35-1
ii  libgdk-pixbuf2.0-0 2.31.1-2+deb8u4
ii  libglib2.0-0   2.42.1-1
ii  libgnome-keyring0  3.12.0-1+b1
ii  libgnomecanvas2-0  2.30.3-2
ii  libgoffice-0.8-8   0.8.17-3
ii  libgtk2.0-02.24.25-3
ii  libgwengui-gtk2-0  4.12.0beta-3+b1
ii  libgwenhywfar604.12.0beta-3+b1
ii  libhtml-tableextract-perl  2.11-1
ii  libhtml-tree-perl  5.03-1
ii  libktoblzcheck1c2a 1.47-1
ii  libofx61:0.9.10-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpython2.7   2.7.9-2
ii  libwebkitgtk-1.0-0 2.4.9-1~deb8u1
ii  libwww-perl6.08-1
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-5+deb8u1
ii  libxslt1.1 1.1.28-2+b2
ii  perl   5.20.2-3+deb8u3
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnucash recommends:
ii  gnucash-docs  2.6.4-1
ii  yelp  3.14.1-1

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.0-1

We believe that the bug you reported is fixed in the latest version of
gnucash, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash 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: Sun, 08 Apr 2018 18:14:53 +1000
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.0-1
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 

Bug#892177: marked as done (Please package stable GnuCash 3.0 release)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:19:58 +
with message-id 
and subject line Bug#892177: fixed in gnucash 1:3.0-1
has caused the Debian Bug report #892177,
regarding Please package stable GnuCash 3.0 release
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.)


-- 
892177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Version: 1:2.7.3-1
Severity: wishlist

2.7.5 was released. Please package it.

https://github.com/Gnucash/gnucash/releases

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.0-1

We believe that the bug you reported is fixed in the latest version of
gnucash, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash 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: Sun, 08 Apr 2018 18:14:53 +1000
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.0-1
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 python3-gnucash - Gnucash interface for Python
Closes: 815005 885204 892177
Changes:
 gnucash (1:3.0-1) experimental; urgency=medium
 .
   * New upstream release [April 2018]. (Closes: #892177).
   * control: removed dbus recommends, as advised by Laurent Bigonville
 (Closes: #815005).
   * Recommends: python-gnucash --> python3-gnucash.
 Thanks, Laurent Bigonville.
   * Install python examples.
 Thanks, Laurent Bigonville.
   * watch: minor pattern correction/update.
   * Build with guile-2.2-dev (Closes: #885204);
 Pass "-X.go" to dh_strip which is "Unable to recognise the format of
 the input file" of *.go files...
Checksums-Sha1:
 9b19e8ce9c9f7d9a508f9ab6b0533a4462aadd23 2394 gnucash_3.0-1.dsc
 a575e853668b93b34dcd94f0ef0d1fee25b0165f 13366724 gnucash_3.0.orig.tar.bz2
 7d570cf5bd1c19a34aac177c90f2b64681507140 34564 gnucash_3.0-1.debian.tar.xz
 3f2c83590e9ec83da904af799478e8f00f314fd4 4895708 gnucash-common_3.0-1_all.deb
 5de70f51fa2ac887072518de1388ef8c2270478d 15708464 
gnucash-dbgsym_3.0-1_amd64.deb
 1d8c18d7c5543271ca88428b6ae863ef85c7c2be 19083 gnucash_3.0-1_amd64.buildinfo
 5659d270b8b4cc3c3867c247d768bfac93c22ea9 4448428 gnucash_3.0-1_amd64.deb
 f9b72ce26e4e3872bd1154385153f4ac8d2bbd71 631564 
python3-gnucash-dbgsym_3.0-1_amd64.deb
 b98c2f98a01886d0a1733af98aed8ede3561bcd6 286384 python3-gnucash_3.0-1_amd64.deb
Checksums-Sha256:
 05b9d7f8f96b39097149b22c1672da16b9522ce296286fe96f75daab92364629 2394 
gnucash_3.0-1.dsc
 4c754476a5b80a97abacaeadac64fefc5a68fcfec15967908dbe3c9f7370dbb9 13366724 
gnucash_3.0.orig.tar.bz2
 6664b8e6a68f472792f0ab52e6b2e125657857acf6bcc3293d3fe052bb00543d 34564 
gnucash_3.0-1.debian.tar.xz
 2e84a091ad8eb1e4ec5c8935a723a78500adf6b1c79bc35d53f85562dd231100 4895708 
gnucash-common_3.0-1_all.deb
 60e0538347320971cc0bce52ebbfb3f0b9989fdc6d4cfd07ec9458ee5ee633c3 15708464 
gnucash-dbgsym_3.0-1_amd64.deb
 77cb0c87e88eaabbe767d5fd6f0ccdcd80d48630cd80e0878fad5f99feef6d8f 19083 
gnucash_3.0-1_amd64.buildinfo
 3964b878f24f949077fe5bd7a2a4152e5ab4bd9b67ce1e5b14b567181a233e81 4448428 
gnucash_3.0-1_amd64.deb
 266d6c97e27c5c8035f9f15b4bba5e0c2ed70921f5c0d6529d2b3a6c4399cd85 631564 
python3-gnucash-dbgsym_3.0-1_amd64.deb
 fcca3402c8a57c43ebeeb6a274bbde604ccffe4decdf01aa7246fc7d585c9063 286384 
python3-gnucash_3.0-1_amd64.deb
Files:
 e9dad75f11e8d61e5814e11724d1c23a 2394 gnome optional gnucash_3.0-1.dsc
 57b0fdbfde05454e03a3fa6102ddd0f3 13366724 gnome optional 
gnucash_3.0.orig.tar.bz2
 4c3eb8119f352b3844cc56def808001d 34564 gnome optional 
gnucash_3.0-1.debian.tar.xz
 511f63861c5139441ee7270e9b392813 4895708 gnome optional 
gnucash-common_3.0-1_all.deb
 

Bug#885204: marked as done (gnucash: please migrate to guile-2.2)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:19:58 +
with message-id 
and subject line Bug#885204: fixed in gnucash 1:3.0-1
has caused the Debian Bug report #885204,
regarding gnucash: please migrate to guile-2.2
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.)


-- 
885204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Severity: normal

I'd like to remove guile-2.0 before the buster release, so please
migrate to guile-2.2 when you can.

Thanks 
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.0-1

We believe that the bug you reported is fixed in the latest version of
gnucash, 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.
Dmitry Smirnov  (supplier of updated gnucash 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: Sun, 08 Apr 2018 18:14:53 +1000
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.0-1
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 python3-gnucash - Gnucash interface for Python
Closes: 815005 885204 892177
Changes:
 gnucash (1:3.0-1) experimental; urgency=medium
 .
   * New upstream release [April 2018]. (Closes: #892177).
   * control: removed dbus recommends, as advised by Laurent Bigonville
 (Closes: #815005).
   * Recommends: python-gnucash --> python3-gnucash.
 Thanks, Laurent Bigonville.
   * Install python examples.
 Thanks, Laurent Bigonville.
   * watch: minor pattern correction/update.
   * Build with guile-2.2-dev (Closes: #885204);
 Pass "-X.go" to dh_strip which is "Unable to recognise the format of
 the input file" of *.go files...
Checksums-Sha1:
 9b19e8ce9c9f7d9a508f9ab6b0533a4462aadd23 2394 gnucash_3.0-1.dsc
 a575e853668b93b34dcd94f0ef0d1fee25b0165f 13366724 gnucash_3.0.orig.tar.bz2
 7d570cf5bd1c19a34aac177c90f2b64681507140 34564 gnucash_3.0-1.debian.tar.xz
 3f2c83590e9ec83da904af799478e8f00f314fd4 4895708 gnucash-common_3.0-1_all.deb
 5de70f51fa2ac887072518de1388ef8c2270478d 15708464 
gnucash-dbgsym_3.0-1_amd64.deb
 1d8c18d7c5543271ca88428b6ae863ef85c7c2be 19083 gnucash_3.0-1_amd64.buildinfo
 5659d270b8b4cc3c3867c247d768bfac93c22ea9 4448428 gnucash_3.0-1_amd64.deb
 f9b72ce26e4e3872bd1154385153f4ac8d2bbd71 631564 
python3-gnucash-dbgsym_3.0-1_amd64.deb
 b98c2f98a01886d0a1733af98aed8ede3561bcd6 286384 python3-gnucash_3.0-1_amd64.deb
Checksums-Sha256:
 05b9d7f8f96b39097149b22c1672da16b9522ce296286fe96f75daab92364629 2394 
gnucash_3.0-1.dsc
 4c754476a5b80a97abacaeadac64fefc5a68fcfec15967908dbe3c9f7370dbb9 13366724 
gnucash_3.0.orig.tar.bz2
 6664b8e6a68f472792f0ab52e6b2e125657857acf6bcc3293d3fe052bb00543d 34564 
gnucash_3.0-1.debian.tar.xz
 2e84a091ad8eb1e4ec5c8935a723a78500adf6b1c79bc35d53f85562dd231100 4895708 
gnucash-common_3.0-1_all.deb
 60e0538347320971cc0bce52ebbfb3f0b9989fdc6d4cfd07ec9458ee5ee633c3 15708464 
gnucash-dbgsym_3.0-1_amd64.deb
 77cb0c87e88eaabbe767d5fd6f0ccdcd80d48630cd80e0878fad5f99feef6d8f 19083 
gnucash_3.0-1_amd64.buildinfo
 3964b878f24f949077fe5bd7a2a4152e5ab4bd9b67ce1e5b14b567181a233e81 4448428 
gnucash_3.0-1_amd64.deb
 266d6c97e27c5c8035f9f15b4bba5e0c2ed70921f5c0d6529d2b3a6c4399cd85 631564 
python3-gnucash-dbgsym_3.0-1_amd64.deb
 fcca3402c8a57c43ebeeb6a274bbde604ccffe4decdf01aa7246fc7d585c9063 286384 
python3-gnucash_3.0-1_amd64.deb
Files:
 e9dad75f11e8d61e5814e11724d1c23a 2394 gnome optional gnucash_3.0-1.dsc
 57b0fdbfde05454e03a3fa6102ddd0f3 13366724 gnome optional 
gnucash_3.0.orig.tar.bz2
 

Bug#601392: marked as done (cl-ptester: referenced homepage does not exist anymore)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:19:21 +
with message-id 
and subject line Bug#601392: fixed in cl-ptester 2.1.2-8
has caused the Debian Bug report #601392,
regarding cl-ptester: referenced homepage does not exist anymore
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.)


-- 
601392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-ptester
Version: 2.1.2-6
Severity: minor


% apt-cache show cl-ptester
[...]
Description: Test suite for Common Lisp programs
 ptester is portable version of Franz's. opensource testing suite.
 It is designed for writing regression test suites for
 Common Lisp packages.
Homepage: http://opensource.franz.com/test/test-dist/tester.cl

http://opensource.franz.com/test/test-dist/tester.cl == 404
AFAICS it's located at http://github.com/franzinc/tester now.

PS: IMHO the "ptester is portable version of Franz's. opensource
testing suite." should be "ptester is a portable version of Franz's
opensource testing suite.", though I'm not a native speaker.

regards,
-mika-


--- End Message ---
--- Begin Message ---
Source: cl-ptester
Source-Version: 2.1.2-8

We believe that the bug you reported is fixed in the latest version of
cl-ptester, 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 601...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-ptester 
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: Sun, 08 Apr 2018 10:52:36 +0200
Source: cl-ptester
Binary: cl-ptester
Architecture: source
Version: 2.1.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Description:
 cl-ptester - Test suite for Common Lisp programs
Closes: 601392
Changes:
 cl-ptester (2.1.2-8) unstable; urgency=medium
 .
   * Team upload.
   * Update Vcs-* fields for move to salsa.
   * Remove ${shlibs:Depends}, since this is an arch:all package.
   * Set Maintainer to debian-common-lisp@l.d.o.
   * Use Kevin M. Rosenberg's git repository as the Homepage.
 (Closes: #601392)
   * Remove spurious dot in long description.
   * Move to 3.0 (quilt) source format.
   * Remove Build-Depends on dh-lisp.
   * Remove obsolete README.building.
   * Update d/watch using uscan git HEAD mode.
Checksums-Sha1:
 46e571094f1db8f3e4eaac15f1c667719c09d3d9 1926 cl-ptester_2.1.2-8.dsc
 1a4f3cadc5059abd4a41b9cd38e36437c330020f 4524 cl-ptester_2.1.2-8.debian.tar.xz
 2789259047f981761de88711159d8cb033b36d9c 5398 
cl-ptester_2.1.2-8_amd64.buildinfo
Checksums-Sha256:
 858d37e7a5bc665314e51a0ad132025f56363d603a247d8bfb47a7d753dbd5b6 1926 
cl-ptester_2.1.2-8.dsc
 3570f6b17552d5bb8841aa24af43b6fa7b86555af5323e824dd233078b80514b 4524 
cl-ptester_2.1.2-8.debian.tar.xz
 1fea807d5dae42dfdc872ccd50bfd710920a6fb72c25d302b7ab6fc83d557181 5398 
cl-ptester_2.1.2-8_amd64.buildinfo
Files:
 d9c2fe8c4cbbd8ae0c039973f4276968 1926 devel optional cl-ptester_2.1.2-8.dsc
 0fd4a9ab59d1b87d1f9e9dcfd998c94a 4524 devel optional 
cl-ptester_2.1.2-8.debian.tar.xz
 5958d81cd6c66c03760bc6ca90cd49ae 5398 devel optional 
cl-ptester_2.1.2-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlrJ2W0ACgkQLOzpNQ7O
vkoh5Q//eL3+3Pf3lfPb2VQV9HFVBsrrRsMNAqU63L5XgiJE/2kjIwt+B8VM717Q
Idfq60xcI0otWagIu+nytGCcxvpYRTDWEaKHLVRSqJL1Qgpq2goKyHndrGYHtQVK
GgPamlKNdTxWZ/ikDJe/c8hQBDGhWcP4nCnJhyZCwckiS0ht0q1+7Ky+42xTJb2U
2KSOPrA7j9o1SYGGAFONiOl5w4PScQY4Sp/Kzc3AJR/zhB6/0S1tqEK5Np7J0Hic
I4/tzNw0Zw44kn4s7HsNQfAOE9y+XVm0W7mKusruDUpIOBR67nTJ8PnQtl0rDvv0
u7VhH8kn5Y/v4EXBI6fMU13sOURPW5DNodLbOthqvOoNb3tflq3oim+OWUm2isZW
/qZCDCBcEVtIHS3amjL9UdVvG/hC8hKZmkQ5eMr8iXvjDpEfVm1cCUbfVLdjQtVK
Vh+p0bqyCAWP/Lbr0TwbX8G3m3WMCQInlTeamtA0CilPcrL+801Z/lE2sVbtnu4J
ZS5HloHc9JP4lE+XFpkimUrpdFalpapSJ5hZSu6Mqdz56S7Bv5pvIVAY/1vDepgf
VuM+eL6lXhX3MBu/XmE9OSSXIjG/qJNG7Yp+upr8/oZOAAzytW+R51z5Ei5p4tfZ
FoN59AmBqkPqxXFwMfhaSCCOcyiSZQV+/RXe9u11FoZICcgDy2k=
=IDds
-END PGP SIGNATURE 

Bug#894816: marked as done ([ruby-gtk2] mikutter doesn't start with error)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:50:16 +
with message-id 
and subject line Bug#894816: fixed in ruby-gnome2 3.2.3-2
has caused the Debian Bug report #894816,
regarding [ruby-gtk2] mikutter doesn't start with error
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.)


-- 
894816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mikutter
Version: 3.6.5+dfsg-1
Severity: important

--- Please enter the report below this line. ---

mikutter doesn't start.

Followings are console message.

$ mikutter 
Traceback (most recent call last):
54: from /usr/share/mikutter/mikutter.rb:42:in `'
53: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
52: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
51: from /usr/share/mikutter/core/miquire.rb:75:in `each'
50: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
49: from /usr/share/mikutter/core/miquire.rb:95:in 
`file_or_directory_require'
48: from /usr/share/mikutter/core/miquire.rb:98:in 
`miquire_original_require'
47: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
46: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
45: from /usr/share/mikutter/core/boot/load_plugin.rb:10:in `'
44: from /usr/share/mikutter/core/miquire_plugin.rb:96:in `load_all'
43: from /usr/share/mikutter/core/miquire_plugin.rb:36:in `each_spec'
42: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
41: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
40: from /usr/share/mikutter/core/miquire_plugin.rb:38:in `block in 
each_spec'
39: from /usr/share/mikutter/core/miquire_plugin.rb:98:in `block in 
load_all'
38: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
37: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
36: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
35: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
34: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
33: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
32: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
31: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
30: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
29: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
28: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
27: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
26: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
25: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
24: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
23: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
22: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
21: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
20: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `block in 
load'
19: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `load'
18: from /usr/share/mikutter/core/plugin/gtk/gtk.rb:7:in `'
17: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
16: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
15: from /usr/share/mikutter/core/miquire.rb:75:in `each'
14: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
13: from /usr/share/mikutter/core/miquire.rb:95:in 
`file_or_directory_require'
12: from /usr/share/mikutter/core/miquire.rb:98:in 
`miquire_original_require'
11: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
10: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 9: from 
/usr/share/mikutter/core/mui/cairo_cell_renderer_message.rb:3:in `'
 8: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
 7: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
 6: from /usr/share/mikutter/core/miquire.rb:75:in `each'
 5: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
 4: from /usr/share/mikutter/core/miquire.rb:95:in 

Bug#894745: marked as done (cross-gcc-dev patches misapply for recent gcc-7 and gcc-8)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:49:26 +
with message-id 
and subject line Bug#894745: fixed in cross-gcc 185
has caused the Debian Bug report #894745,
regarding cross-gcc-dev patches misapply for recent gcc-7 and gcc-8
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.)


-- 
894745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cross-gcc-dev
Version: 184
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

The recent gcc-7 and gcc-8 uploads add a feature called
FORCE_CROSS_LAYOUT. After these uploads, the cross-gcc-dev patches still
apply, but they apply in a useless way. Part of their effect is moved
from the cross compiler branch to the new FORCE_CROSS_LAYOUT branch and
thus rendered ineffective. The attached patch fixes that.

Helmut
--- cross-gcc-184/debian/changelog
+++ cross-gcc-184+nmu1/debian/changelog
@@ -1,3 +1,10 @@
+cross-gcc (184+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for FORCE_CROSS_LAYOUT. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 03 Apr 2018 21:34:54 +0200
+
 cross-gcc (184) unstable; urgency=medium
 
   * rebuild for 8-20180331-1
--- 
cross-gcc-184/patches/gcc-7/0005-setting-all-the-various-paths-options-for-with_deps_.patch
+++ 
cross-gcc-184+nmu1/patches/gcc-7/0005-setting-all-the-various-paths-options-for-with_deps_.patch
@@ -83,11 +83,18 @@
 index caa8b5e..e9eaf0f 100644
 --- a/debian/rules.defs
 +++ b/debian/rules.defs
-@@ -209,6 +209,9 @@ else
+@@ -209,10 +209,16 @@ else
  # cross compiler, sets WITH_SYSROOT on it's own
  DEB_CROSS = yes
  build_type = build-cross
 +ifeq ($(with_deps_on_target_arch_pkgs),yes)
++  with_sysroot = /
++endif
+   else ifeq ($(FORCE_CROSS_LAYOUT),yes)
+ # a native build with a cross layout
+ DEB_CROSS = yes
+ build_type = build-cross
++ifeq ($(with_deps_on_target_arch_pkgs),yes)
 +  with_sysroot = /
 +endif
else
--- 
cross-gcc-184/patches/gcc-8/0005-setting-all-the-various-paths-options-for-with_deps_.patch
+++ 
cross-gcc-184+nmu1/patches/gcc-8/0005-setting-all-the-various-paths-options-for-with_deps_.patch
@@ -83,11 +83,18 @@
 index c63af56..3690f1b 100644
 --- a/debian/rules.defs
 +++ b/debian/rules.defs
-@@ -209,6 +209,9 @@ else
+@@ -209,10 +209,16 @@ else
  # cross compiler, sets WITH_SYSROOT on it's own
  DEB_CROSS = yes
  build_type = build-cross
 +ifeq ($(with_deps_on_target_arch_pkgs),yes)
++  with_sysroot = /
++endif
+   else ifeq ($(FORCE_CROSS_LAYOUT),yes)
+ # a native build with a cross layout
+ DEB_CROSS = yes
+ build_type = build-cross
++ifeq ($(with_deps_on_target_arch_pkgs),yes)
 +  with_sysroot = /
 +endif
else
--- End Message ---
--- Begin Message ---
Source: cross-gcc
Source-Version: 185

We believe that the bug you reported is fixed in the latest version of
cross-gcc, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated cross-gcc 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: Sun, 08 Apr 2018 02:02:29 -0700
Source: cross-gcc
Binary: cross-gcc-dev
Architecture: source all
Version: 185
Distribution: unstable
Urgency: medium
Maintainer: Debian Cross-Toolchain Team 
Changed-By: Dima Kogan 
Description:
 cross-gcc-dev - Tools for building cross-compilers and cross-compiler packages
Closes: 894745
Changes:
 cross-gcc (185) unstable; urgency=medium
 .
   * rebuild for 5.5.0-11
   * rebuild for 6.4.0-16
   * rebuild for 7.3.0-15
   * rebuild for 8-20180402-1
   * gcc 6,7,8: patches handle FORCE_CROSS_LAYOUT. Thanks to
 Helmut Grohne for the patch. (Closes: #894745)
Checksums-Sha1:
 f9a84a224a5078f865c903fd10767875529393af 1669 cross-gcc_185.dsc
 9c4b0785c66744d3dcd979c91466f8b49b4d0c44 30688 cross-gcc_185.tar.xz
 377e525621dcc3b37a3635d144e7940a69bb4a86 35400 

Bug#893880: marked as done (mark moreutils Multi-Arch: foreign)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 10:22:01 +
with message-id 
and subject line Bug#893880: fixed in moreutils 0.62-1
has caused the Debian Bug report #893880,
regarding mark moreutils Multi-Arch: foreign
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.)


-- 
893880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moreutils
Version: 0.60-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:norwegian src:quagga src:syncmaildir

The affected packages cannot satify their cross Build-Depends, because
their dependency on moreutils is not satisfiable. moreutils depends on
libipc-run-perl, which is Architecture: all and (implicitly) Multi-Arch:
no. It thus is not satisfiable. Now the primary way to interface with
moreutils is to run commands from the package. It only contains commands
and no libraries. Its commands have architecture-independent interfaces
(not dealing with architecture-dependent binary formats). That makes it
a good candidate for being marked Multi-Arch: foreign. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru moreutils-0.60/debian/changelog 
moreutils-0.60/debian/changelog
--- moreutils-0.60/debian/changelog 2017-01-01 22:20:01.0 +0100
+++ moreutils-0.60/debian/changelog 2018-03-23 06:33:07.0 +0100
@@ -1,3 +1,10 @@
+moreutils (0.60-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark moreutils Multi-Arch: foreign. Closes: #-1
+
+ -- Helmut Grohne   Fri, 23 Mar 2018 06:33:07 +0100
+
 moreutils (0.60-1) unstable; urgency=medium
 
   * New upstream version (0.60):
diff --minimal -Nru moreutils-0.60/debian/control moreutils-0.60/debian/control
--- moreutils-0.60/debian/control   2017-01-01 22:19:51.0 +0100
+++ moreutils-0.60/debian/control   2018-03-23 06:33:05.0 +0100
@@ -8,6 +8,7 @@
 
 Package: moreutils
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${perl:Depends}, libipc-run-perl
 Suggests: libtime-duration-perl, libtimedate-perl
 Conflicts: lckdo
--- End Message ---
--- Begin Message ---
Source: moreutils
Source-Version: 0.62-1

We believe that the bug you reported is fixed in the latest version of
moreutils, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Schier  (supplier of updated moreutils 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: Fri, 06 Apr 2018 22:21:07 +0200
Source: moreutils
Binary: moreutils
Architecture: source amd64
Version: 0.62-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier 
Changed-By: Nicolas Schier 
Description:
 moreutils  - additional Unix utilities
Closes: 697052 867167 885221 893880
Changes:
 moreutils (0.62-1) unstable; urgency=medium
 .
   * New upstream version (0.62):
 + chronic: Flush output more often to better preserve stdout,err ordering.
 + ts: Add -m option to use monotonic clock.
 + ts: Added %.T format like %T but with hi-res.
 + pee: Ignore SIGPIPE and write errors caused by the command not
   consuming all its input. Closes: #697052
 + chronic: document return value semantics of -e option. Closes: #867167
 + vidir: reword man page to more explicit mention 'file' args.
   Closes: #885221
 + pee: Don't buffer input, bringing behavior into line with tee.
   * Remove obsolete is-utf8 patch
   * Mark moreutils Multi-Arch: foreign. Closes: #893880,
 thanks to Helmut Grohne 
   * debian/copyright: update URI: http → https
   * Bump standards to 4.1.3 (no changes required)
   * Use debhelper 11
   * debian/rules: use dpkg-buildflags for hardening
   * parallel: fix minor typo (patch)
   * Use https in homepage URI
   * is_utf8: fix allow-hardening-flags patch
   * Override lintian tag hardening-no-fortify functions for usr/bin/ifne
Checksums-Sha1:
 

Bug#895008: marked as done (kicad: can't start pcbnew)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 12:04:18 +
with message-id 
and subject line Bug#895008: fixed in kicad 5.0.0~rc1+dfsg1+20180318-2
has caused the Debian Bug report #895008,
regarding kicad: can't start pcbnew
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.)


-- 
895008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad
Version: 4.0.7+dfsg1-1
Severity: important

Dear Maintainer,
when running pcbnew within kicad or on the command line I get lots of
errors lihe this one (both in a dialog and in the shell):

Assertion failed!
../src/common/object.cpp(251): assert "classTable->Get(m_className) == NULL" 
failed in Register(): Class "wxCommandEvent" already in RTTI table - have you 
used IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some object file twice)?

Many more errors come after, all reporting 
"../src/common/object.cpp(251): assert "classTable->Get(m_className) == NULL"

Anyway pcbnew doesn't start.

I've tried installing kicad 5 from experimental but pcbnew won't start
either.  

A backtrace is attached for the first error.

Leonardo


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kicad depends on:
ii  kicad-common4.0.7+dfsg1-1
ii  libboost-atomic1.62.0   1.62.0+dfsg-5
ii  libboost-chrono1.62.0   1.62.0+dfsg-5
ii  libboost-context1.62.0  1.62.0+dfsg-5
ii  libboost-date-time1.62.01.62.0+dfsg-5
ii  libboost-filesystem1.62.0   1.62.0+dfsg-5
ii  libboost-iostreams1.62.01.62.0+dfsg-5
ii  libboost-locale1.62.0   1.62.0+dfsg-5
ii  libboost-program-options1.62.0  1.62.0+dfsg-5
ii  libboost-regex1.62.01.62.0+dfsg-5
ii  libboost-system1.62.0   1.62.0+dfsg-5
ii  libboost-thread1.62.0   1.62.0+dfsg-5
ii  libc6   2.27-3
ii  libcairo2   1.15.10-2
ii  libcurl37.58.0-2
ii  libgcc1 1:8-20180402-1
ii  libgl1  1.0.0+git20180308-1
ii  libglew2.0  2.0.0-5
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgomp18-20180402-1
ii  libpython2.72.7.14-8
ii  libssl1.1   1.1.0h-2
ii  libstdc++6  8-20180402-1
ii  libwxbase3.0-0v53.0.4+dfsg-3
ii  libwxgtk3.0-0v5 3.0.4+dfsg-3
ii  python  2.7.14-4
ii  python-wxgtk3.0 3.0.2.0+dfsg-7

Versions of packages kicad recommends:
ii  xsltproc  1.1.29-5

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-4
ii  kicad-doc-en 4.0.7+dfsg1-1
ii  kicad-doc-it 4.0.7+dfsg1-1

-- no debconf information
ASSERT INFO:
../src/common/object.cpp(251): assert "classTable->Get(m_className) == NULL" 
failed in Register(): Class "wxCommandEvent" already in RTTI table - have you 
used IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some object file twice)?

BACKTRACE:
[1] wxClassInfo::Register()
[2] _dl_catch_exception
[3] _dl_catch_exception
[4] _dl_catch_error
[5] dlopen
[6] _PyImport_GetDynLoadFunc
[7] _PyImport_LoadDynamicModule
[8] PyImport_ImportModuleLevel
[9] PyObject_Call
[10] PyEval_CallObjectWithKeywords
[11] PyEval_EvalFrameEx
[12] PyEval_EvalCodeEx
[13] PyEval_EvalCode
[14] PyImport_ExecCodeModuleEx
[15] PyImport_ImportModuleLevel
[16] PyObject_Call
[17] PyEval_CallObjectWithKeywords
[18] PyEval_EvalFrameEx
[19] PyEval_EvalCodeEx
[20] PyEval_EvalCode
[21] PyImport_ExecCodeModuleEx
[22] PyImport_ImportModuleLevel
[23] PyObject_Call
[24] PyObject_CallFunction
[25] PyImport_Import
[26] PyImport_ImportModule
[27] PyCObject_Import
[28] wxEntry(int&, wchar_t**)
[29] __libc_start_main
[30] _start
--- End Message ---
--- Begin Message ---
Source: kicad
Source-Version: 5.0.0~rc1+dfsg1+20180318-2

We believe that the bug you reported is fixed in the latest version of
kicad, 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, 

Bug#894896: marked as done (please drop the python3-distutils dependency again)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 12:04:48 +
with message-id 
and subject line Bug#894896: fixed in pyregion 2.0-3
has caused the Debian Bug report #894896,
regarding please drop the python3-distutils dependency again
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.)


-- 
894896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyregion
Version: 2.0-2
Tags: patch

Please drop the python3-distutils dependency again. I cannot find any code in
python3-region that uses distutils.

patch at
http://launchpadlibrarian.net/363349591/pyregion_2.0-2_2.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: pyregion
Source-Version: 2.0-3

We believe that the bug you reported is fixed in the latest version of
pyregion, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Prat  (supplier of updated pyregion 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, 08 Apr 2018 13:05:37 +0200
Source: pyregion
Binary: python-pyregion python-pyregion-doc python3-pyregion
Architecture: source
Version: 2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Vincent Prat 
Description:
 python-pyregion - Python module to parse ds9 region files (Python 2)
 python-pyregion-doc - Python module to parse ds9 region files (documentation)
 python3-pyregion - Python module to parse ds9 region files (Python 3)
Closes: 894896
Changes:
 pyregion (2.0-3) unstable; urgency=medium
 .
   * Drop dependency on python3-distutils (Closes: #894896)
   * Bump Standards-Version to 4.1.4
   * Add d/upstream/metadata file
Checksums-Sha1:
 e4592483aea9c7a9da790d0a77657409e7912e7e 2511 pyregion_2.0-3.dsc
 edafaeeefc62cf599a4575f9c6ffc8d9a1d75c98 3808 pyregion_2.0-3.debian.tar.xz
 603bd0132c8c388f61dd2a8533e3755c3b4c8c42 11746 pyregion_2.0-3_source.buildinfo
Checksums-Sha256:
 35e4461fcf5c3c996e90709077a8d499bda2d7623892dafc6d730070bfd16b41 2511 
pyregion_2.0-3.dsc
 508ed33a84e2ed0e223f1fcfb3ede8db8268f57433bb1fca506262fb2c1cec41 3808 
pyregion_2.0-3.debian.tar.xz
 36cb0813b0683ab1e4568273f74645857e358b29e43f2e7a171fd4f4264b1975 11746 
pyregion_2.0-3_source.buildinfo
Files:
 3a1ddd382757431efef45d470abdc1c3 2511 python optional pyregion_2.0-3.dsc
 64c418ed074efcd7cf82502e8019df80 3808 python optional 
pyregion_2.0-3.debian.tar.xz
 668210dd1810269b13ee486ca85098a9 11746 python optional 
pyregion_2.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEwN+g0Kj2VQgeB/icBzHNjq6Fm38FAlrKAXMSHHZpbmNlcHJh
dEBmcmVlLmZyAAoJEAcxzY6uhZt/jVQQAKX3X3j1CSaV+u2Mp6o00HHZpQXfZMO4
CAfftVMGEYWWR5JQ+UWWNtl9PiPkiC2EpfhmzLgAifuJHSp6lOlaDq6JHNTxvpIW
iClWU97uere/yyDKsgHRniwSh0B0TZXQWRGaHHnbqgpaccC0xNz2rnSbJQWR75We
GNKtDOvsVxiiNWqHRbzZdyFZFfqxN2RP3DBq1GtZRgGfRZ+kb4vy4aSJQS3EH42W
gecA8Fwq1m6HzVkx4r0PgguvlrubGjv9fDBdy+JxSy1EWqCXj2oGbQ2J85vnCc/e
lS1hxnCp/k1/uexQsFB9uLOiVHFnOAWtc439dBsHtDU9fmwLJ7MnxFxfJ3HIApa8
c6x3E7leg/QwtxRGTernip0yUAqvZrSHyyhX8zihKbX4SYJJUKijnOqz5ExHHmfX
ZKvDpH5EEl0Cs/iB7TXkR+IWB/uU3riR/hsjuQ74WZAQh+9LkMMAqW+7/+v3hhrz
+ligmOSMM2X19OL9F5DeKE7tFQSyJeUlpptN+RbR6NkxcjAhAX08bTrhVmyRErUs
YpQwnVLn51sx1ECBOV4kYyaBUB/FZQ886SGLpGTFGmYnCXC8qUMOlrZWECNOUt1k
S1c4fXkLTU543oJFmhB/H5M7Ma2hGsevYHyA8PyJm7ueF9/CduQA8qtURd3P3shh
R+YgrB3iJQhL
=G0b2
-END PGP SIGNATURE End Message ---

Bug#895060: marked as done (openjdk-11: Please drop obsolete patch hotspot-disable-jvmtihtml.diff)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 11:22:44 +
with message-id 
and subject line Bug#895060: fixed in openjdk-11 11~8-1
has caused the Debian Bug report #895060,
regarding openjdk-11: Please drop obsolete patch hotspot-disable-jvmtihtml.diff
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.)


-- 
895060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-11
Version: 11~7-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

The patch hotspot-disable-jvmtihtml.diff doesn't apply anymore,
please remove it completely. It also seems we don't need it
anymore at all, but I am checking openjdk-10 (and -11) on m68k
now to see whether we need another patch. I will open another bug
report for that if necessary.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: openjdk-11
Source-Version: 11~8-1

We believe that the bug you reported is fixed in the latest version of
openjdk-11, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-11 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: Sun, 08 Apr 2018 10:58:36 +0200
Source: openjdk-11
Binary: openjdk-11-jdk-headless openjdk-11-jre-headless openjdk-11-jdk 
openjdk-11-jre openjdk-11-demo openjdk-11-source openjdk-11-doc openjdk-11-dbg 
openjdk-11-jre-zero
Architecture: source
Version: 11~8-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-11-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-11-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-11-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-11-jdk - OpenJDK Development Kit (JDK)
 openjdk-11-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-11-jre - OpenJDK Java runtime, using
 openjdk-11-jre-headless - OpenJDK Java runtime, using  (headless)
 openjdk-11-jre-zero - Alternative JVM for OpenJDK, using Zero
 openjdk-11-source - OpenJDK Development Kit (JDK) source files
Closes: 895060
Changes:
 openjdk-11 (11~8-1) unstable; urgency=medium
 .
   * OpenJDK 11 build 8.
   * Update the s390x-zEC12 patch.
   * Drop obsolete patches. Closes: #895060.
Checksums-Sha1:
 52c44bde134a6f9ea7312d9e788d571d8cc9308a 4534 openjdk-11_11~8-1.dsc
 6f73669a5449d5584d21467b40b91144bb9e3f78 72561968 openjdk-11_11~8.orig.tar.xz
 be3883a12473c58ee5326a04def640d6de16211f 167560 openjdk-11_11~8-1.debian.tar.xz
 cd541ace4ec5d08ddeb8535f70f443b34b8e7ea6 16792 
openjdk-11_11~8-1_source.buildinfo
Checksums-Sha256:
 404a0900468329d447f87707d32f21b6821eff796f7bf95f48cae1f5dfb1596c 4534 
openjdk-11_11~8-1.dsc
 1096f743c015acdd3ddcd8be2e221709be479d6dd8d84976dca9502b2ad4c340 72561968 
openjdk-11_11~8.orig.tar.xz
 c11b135d7713ceb576ad4b31c33fe425166257d165af26ca3b3964da00952c22 167560 
openjdk-11_11~8-1.debian.tar.xz
 5d0d649da3f1dc6af04f7c956955897ecbd382832a6c934a4ed385658fa0178d 16792 
openjdk-11_11~8-1_source.buildinfo
Files:
 b7809cf6565d17aad459744624b9f797 4534 java optional openjdk-11_11~8-1.dsc
 0195ebab93ac051249c9e0ed5113795c 72561968 java optional 
openjdk-11_11~8.orig.tar.xz
 826e5091f42fd0a8ae2175871260d70f 167560 java optional 
openjdk-11_11~8-1.debian.tar.xz
 04b56d1fa42d10d214c8f60b8b904965 16792 java optional 
openjdk-11_11~8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlrJ9z8QHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9e7dEACPkF7B5dkWH3I9waFB7kY6WgwDqIVqS6YW
cNZT6vDxhmvohnp1KJ5r/2Sdrc3UuQ/0Z2iajRL4vZ080uim/tHsiLHVr7mRHeX4
oAJajfrDFV8X+wlo5M9ucZrlYdXDCY6CWBcIgUXHq0eV2XnlNQ+mO/ncM3b2FqG9
H8EhN8DVBlKoHXScc57nJTaeaFuYtEpxr7z35Y3sOAdb94bXj4DwwUHPtRhLUIRx

Processed: closing 893436

[Debian Bug Tracking System]

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

> close 893436 5.4.1-1
Bug #893436 [src:jupyter-notebook] jupyter-notebook: CVE-2018-8768
Marked as fixed in versions jupyter-notebook/5.4.1-1.
Bug #893436 [src:jupyter-notebook] jupyter-notebook: CVE-2018-8768
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#830036: marked as done (gobby: Uses deprecated gnome-common macros/variables)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 15:23:10 +0200
with message-id <45cfaa40-afd4-363d-fe0e-5d3443abc...@debian.org>
and subject line #830036 solved in 0.6.0~20170204~e5c2d1-3
has caused the Debian Bug report #830036,
regarding gobby: Uses deprecated gnome-common macros/variables
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.)


-- 
830036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gobby
Version: 0.5.0-8
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-common

Hi,

gnome-common did a cleanup upstream and deprecated quite a few macros
and variables.

gnome-doc-utils removal
===
The gnome-doc-utils build infrastructure was removed completely along
with the following macros:

 GNOME_DOC_INIT [1]
 GNOME_COMMON_INIT [2]


deprecated variables

The following variables used in gnome-autogen.sh have been declared
deprecated [3]:

 REQUIRED_GNOME_DOC_UTILS_VERSION
 REQUIRED_DOC_COMMON_VERSION
 USE_COMMON_DOC_BUILD
 FORBIDDEN_M4MACROS
 GNOME2_DIR
 GNOME2_PATH
 USE_GNOME2_MACROS

deprecated macros
=
The following macros have also been declared deprecated:

 GNOME_COMPILE_WARNINGS [4]
 GNOME_CXX_WARNINGS [5]

Upstream has documentation at [6] with how you can fix your package and
why those particular changes were made.

According to codesearch.d.n your package gobby uses one of the macros or
variables so might be affected, especially once you run autoreconf. Please
update your package accordingly and forward it to upstream if possible.

If you have further question, please don't hesitate to ask.

Regards,
Michael

[1] https://git.gnome.org/browse/gnome-common/commit/?id=6684e2fa5
[2] https://git.gnome.org/browse/gnome-common/commit/?id=1f60e9536
[3] https://git.gnome.org/browse/gnome-common/commit/?id=4c8d8ad93
[4] https://git.gnome.org/browse/gnome-common/commit/?id=b57bae0be
[5] https://git.gnome.org/browse/gnome-common/commit/?id=2bffd7e1u
[6] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Version: 0.6.0~20170204~e5c2d1-3

0.6.0~20170204~e5c2d1-3 includes a patch to use yelp instead of
gnome-doc infrastructure because of #888953. This bug has been solved as
a side-effect.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#895190: marked as done (pkg-perl-autopkgtest: allow configurable xvfb-run invocation)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:25:28 +
with message-id 
and subject line Bug#895190: fixed in pkg-perl-tools 0.44
has caused the Debian Bug report #895190,
regarding pkg-perl-autopkgtest: allow configurable xvfb-run invocation
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.)


-- 
895190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwx-perl
Version: 1:0.9932-3
Severity: important
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Control: clone -1 -2
Control: reassign -2 pkg-perl-autopkgtest
Control: retitle -2 pkg-perl-autopkgtest: allow configurable xvfb-run invocation
Control: severity -2 wishlist
Control: block -1 with -2

The autopkgtest checks of this package regressed with 1:0.9932-3.

 https://ci.debian.net/packages/libw/libwx-perl/unstable/amd64/

This is because the pkg-perl-autopkgtest scripts run the test suite with
'xvfb-run' defaults, but this package now needs 16-bit colour depth,
as provided at build time by debian/rules:

  # xvfb-run defaults to 8-bit colour depth, which causes some tests to fail.
  override_dh_auto_test:
  xvfb-run -s '-screen 0 640x480x16' -a dh_auto_test --max-parallel=1

Unfortunately it's not currently possible to supply xvfb arguments in
pkg-perl-autopkgtest, so cloning a separate bug for that and blocking.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: pkg-perl-tools
Source-Version: 0.44

We believe that the bug you reported is fixed in the latest version of
pkg-perl-tools, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated pkg-perl-tools 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: Sun, 08 Apr 2018 16:18:02 +0300
Source: pkg-perl-tools
Binary: pkg-perl-tools pkg-perl-autopkgtest
Architecture: source
Version: 0.44
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 pkg-perl-autopkgtest - collection of autopktest scripts for Perl packages
 pkg-perl-tools - collection of tools to aid packaging Perl modules in Debian
Closes: 895190
Changes:
 pkg-perl-tools (0.44) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Add a "TIPS & TRICKS" section to dpt-config(5).
   * dpt-import-orig: remove check for gbp vs. git-import-orig.
 gbp(1) is old enough.
 .
   [ Niko Tyni ]
   * autopkgtest/smoke: support xvfb configuration in smoke-env.
 (Closes: #895190)
Checksums-Sha1:
 da95aa4258093916b4910d73017706a1f5b906a3 2575 pkg-perl-tools_0.44.dsc
 ffbb13935b6e0c696b2aaa71c953ca9692cb0c6e 74520 pkg-perl-tools_0.44.tar.xz
 2f31b6bcb984841bf0f677ecd9e47e3ddbbeb05a 5799 
pkg-perl-tools_0.44_source.buildinfo
Checksums-Sha256:
 f3a2b4f4ea65eb5e1d2dbcc3483ef828479a377416a77f3b0b4b46823bcdf540 2575 
pkg-perl-tools_0.44.dsc
 4f5b055003d5d5fefaa2d6266a55e44b187a0b39f55f03cb888d1ad9e588af43 74520 
pkg-perl-tools_0.44.tar.xz
 c66e2cbb5d2932d500814b0027bc97204bbb8a9a9e96f19d54ea5d278ff0f1d4 5799 
pkg-perl-tools_0.44_source.buildinfo
Files:
 70d7ab09aa8471a4c814e32b94f3f5cb 2575 devel optional pkg-perl-tools_0.44.dsc
 3f039942a84556f867bc26f7880fabff 74520 devel optional 
pkg-perl-tools_0.44.tar.xz
 aeadd1495769790a0a1397104a045f83 5799 devel optional 
pkg-perl-tools_0.44_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlrKGJwACgkQLsD/s7cw
Gx/iug//WA20MQthzKt/yCS3M2Nq/3VaEzXwZdOQ1VBGwghvWWo4jleenaOU6meI
bHPWqBzl47oPrnycujYfRbYBfSTbp0Tq8JO7UKFiC+Ygn1iYk9mzD8pMdG/Upziz
kQVZgf40SHUSrQhp3NabNS90NJmUCkhX11F6Nefsg8ttvkH8IfV+vU5zyZGCVnLz
7GOynOMVKp6gQxq8nFqa84AvQ6wgSTbbeRbbba6KfLJaS4k/faNnVpOBscJvfw8p
wrK/fd+uhjZyxHiCT95KXIPm0eVBNc+jTWZ1s7I6nqSJ6n6cWqGrr6NKdg36ggBn
nCVbf/WxsKZDrxWanqf1ym7ejzcM3QonKwZkMafVwzADBWFxvacN56ueJzvopKGF
Oxfvn7wM19ZBC0uIlugHt7I3XpGTFplm9jKCsoo6DnUQVnl/GjDm2hRqdSYoi/xY

Bug#894091: marked as done (bind-dyndb-ldap FTBFS with bind9 9.11.3)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:19:09 +
with message-id 
and subject line Bug#894091: fixed in bind-dyndb-ldap 11.1-2
has caused the Debian Bug report #894091,
regarding bind-dyndb-ldap FTBFS with bind9 9.11.3
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.)


-- 
894091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind-dyndb-ldap
Version: 11.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid

...
../../src/bindcfg.c: In function 'get_type_from_tuplefield':
../../src/bindcfg.c:27:2: error: implicit declaration of function 'REQUIRE'; 
did you mean 'ISC_REQUIRE'? [-Werror=implicit-function-declaration]
  REQUIRE(cfg_type != NULL && cfg_type->of != NULL);
  ^~~
--- End Message ---
--- Begin Message ---
Source: bind-dyndb-ldap
Source-Version: 11.1-2

We believe that the bug you reported is fixed in the latest version of
bind-dyndb-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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated bind-dyndb-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: SHA512

Format: 1.8
Date: Sun, 08 Apr 2018 21:59:56 +0300
Source: bind-dyndb-ldap
Binary: bind9-dyndb-ldap
Architecture: source
Version: 11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 bind9-dyndb-ldap - LDAP back-end plug-in for BIND
Closes: 894091
Changes:
 bind-dyndb-ldap (11.1-2) unstable; urgency=medium
 .
   * Fix build with bind 9.11.3. (Closes: #894091)
Checksums-Sha1:
 5c6b2f699af641018e8bbf127aed04baa466e40c 2082 bind-dyndb-ldap_11.1-2.dsc
 6f39f8ece22c7859d5005c8aac03d47ca63d4b5d 5420 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 a4f290aac23c951e2c6d06286c91da0868d0b1c3 5942 
bind-dyndb-ldap_11.1-2_source.buildinfo
Checksums-Sha256:
 84747360a62c663d4c35e0a54f8787e9cb2b8ede9af53e5bae112718923fdf0b 2082 
bind-dyndb-ldap_11.1-2.dsc
 0542a652a4786be0c771d692d5f5fb5be24da8a480ed774040a05f9b0e3c05ef 5420 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 23d7e88ebd6eca661784a70044ff4fc720f48546831428af6edbef1cb61b7536 5942 
bind-dyndb-ldap_11.1-2_source.buildinfo
Files:
 f6753aabbf0d2d5769205980762e0309 2082 net optional bind-dyndb-ldap_11.1-2.dsc
 00d49609933b16d3d312999af2466a1c 5420 net optional 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 a346d06b6763ef09afe35d89233291dd 5942 net optional 
bind-dyndb-ldap_11.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlrKZroACgkQy3AxZaiJ
hNwdcRAAms5yK25lKW5JtTWckUBaZHSIpzPH7RYX7nDty0+LFsvtWIb53rjEpd8d
+R15NlmAeEafIqaxKBlN0/sv1evroBQIriQ2pP6WMQ4uD2wTxxMQgOD2lLJNRMbw
+64gYlaJwrn3ZJzssKs6K5EupLFJb5Z+tdvEq7bn7A2OJd4US2e6LtPmsXGwbrzK
o7qzoGcUYa9pgNd7MzuF0A4ZsNc17eR8yByCjPeukFOCQCqxZoEzpXHQ/jqP2x0/
oQb/FN4zMW6ZpYEb76kMua5KPV3GqbziQzlTQdX4ZP+2GJoZaLGBWgvihPoOnmvI
IzxHgpO2+m3yipXQWgwrku6DGPAgLOn60W6bOtB5jzErQTkLP1/zDMxLEFU79rf0
7DNHhtcDyw5yI1d6qY9Tly3vqJEo+l4WWymGd77VEORdD5v2YKoDPt1XqvI2hJrX
byx8f/hYNnbBaVCuvhQE65CowUXnDocEgmTNn0SGDqrQd4Dt08fgQgzNn7D0Ckr+
1alKUjAh2MNkx1XhJ0ZOS8Fq56ECOPFT/Qt24MhzAf4cYVplPHBFknMZMDUWsVmA
qO3HWzhI9MAkaBAEPE6ahd+99MYZFnCNY0MiGjbfpP0ahhgytvfggO7UX4+beknc
NWlXLCNmhCaFeoYTmOtNUgiqPs9OKLc+1U7t011qNkWRQLIsvhg=
=lSb8
-END PGP SIGNATURE End Message ---

Bug#892641: marked as done (python-xarray: FTBFS and Debci failure with pandas 0.22.0)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:48:57 +0300
with message-id <20180408194857.GI9516@localhost>
and subject line Seems to be fixed in 0.10.2-1
has caused the Debian Bug report #892641,
regarding python-xarray: FTBFS and Debci failure with pandas 0.22.0
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.)


-- 
892641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.9.6-1
Severity: serious

https://ci.debian.net/packages/p/python-xarray/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-xarray.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-xarray-0.9.6/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
pytest 
= test session starts ==
platform linux -- Python 3.6.4+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /build/1st/python-xarray-0.9.6, inifile: setup.cfg
collected 2460 items / 1 skipped

xarray/tests/test_accessors.py s...  [  0%]
xarray/tests/test_backends.py .ss.ss [  1%]
s.ss [  4%]
sss. [  7%]
.ss..... [ 10%]
s.s...s. [ 13%]
 [ 16%]
ss.s..ss.ss.s..ss.ss [ 19%]
 [ 22%]
 [ 25%]
s.s..[ 27%]
xarray/tests/test_combine.py s   [ 28%]
xarray/tests/test_computation.py ..s [ 29%]
xarray/tests/test_conventions.py .ss [ 30%]
ss.s.sss [ 31%]
xarray/tests/test_dask.py ss [ 33%]
xarray/tests/test_dataarray.py .s... [ 35%]
sFF. [ 38%]
...s...F [ 41%]
..s. [ 43%]
 [ 46%]
 [ 49%]
 [ 52%]
...  [ 53%]
xarray/tests/test_dataset.py ..s.s.. [ 54%]
F... [ 57%]
.F.F.s..s..s [ 60%]
...s..s..s.s [ 63%]
 [ 66%]
 [ 69%]
 [ 72%]
 [ 75%]
 [ 78%]
 [ 81%]
 [ 82%]
xarray/tests/test_duck_array_ops.py .[ 83%]
xarray/tests/test_extensions.py  [ 83%]
xarray/tests/test_formatting.py  [ 84%]
xarray/tests/test_groupby.py .   [ 84%]
xarray/tests/test_indexing.py .F..   [ 84%]
xarray/tests/test_merge.py . [ 85%]
xarray/tests/test_options.py ..  [ 85%]
xarray/tests/test_plot.py .. [ 87%]
 [ 90%]

Bug#683772: marked as done (gpscorrelate: provide a --force option to overwrite existing GPS tags)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:22:08 +
with message-id 
and subject line Bug#683772: fixed in gpscorrelate 1.6.1-6
has caused the Debian Bug report #683772,
regarding gpscorrelate: provide a --force option to overwrite existing GPS tags
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.)


-- 
683772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpscorrelate
Version: 1.6.1-4
Severity: wishlist

I've recently acquired a camera that writes GPS data to its images.
But the positioning data are quite often a bit off, because it only
infrequently updates itself (to conserve battery, I presume).

Therefore, I want to overwrite the image data with a GPS position
taken from my separate recorder, if that was on at the time of the
photo.

I could use a two-pass approach, using the -r option, but that would
mean that I'd completely lose geodata where it's not present in the
tracklog.  Which is undesirable, really.

N.B. the GPSDateTime records the time of acquisition of geodata, and
 can be minutes behind Date/Time Original; I think the camera
 interpolates but haven't checked.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armel

Kernel: Linux 3.2.9-balti (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gpscorrelate depends on:
ii  libc62.13-33
ii  libexiv2-12  0.23-1
ii  libgcc1  1:4.7.1-2
ii  libstdc++6   4.7.1-2
ii  libxml2  2.8.0+dfsg1-5

gpscorrelate recommends no packages.

gpscorrelate suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gpscorrelate
Source-Version: 1.6.1-6

We believe that the bug you reported is fixed in the latest version of
gpscorrelate, 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 683...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mònica Ramírez Arceda  (supplier of updated gpscorrelate 
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, 08 Apr 2018 22:28:23 +0200
Source: gpscorrelate
Binary: gpscorrelate gpscorrelate-gui
Architecture: source amd64
Version: 1.6.1-6
Distribution: unstable
Urgency: medium
Maintainer: Mònica Ramírez Arceda 
Changed-By: Mònica Ramírez Arceda 
Description:
 gpscorrelate - correlates digital photos with GPS data filling EXIF fields 
(comm
 gpscorrelate-gui - correlates digital photos with GPS data filling EXIF fields 
(GUI)
Closes: 683772 779390
Changes:
 gpscorrelate (1.6.1-6) unstable; urgency=medium
 .
   * Bump to Standard-Version 4.1.3. No changes required.
   * 60-gpstimestamp-unsigned.patch: Write the GPSTimeStamp tag as unsigned,
 as per spec. (Closes: #779390)
   * 70-option-overwrite-gpstags.patch: Add ability to force overwriting of
 existing tags. (Closes: #683772)
   * Update compatibility level to 11.
   * Use HTTPS in copyright format URL.
   * Migrate Vcs-* to salsa.debian.org.
Checksums-Sha1:
 9e23373485b03dbcdc8b2c29b50058d1d3d0fbfd 2083 gpscorrelate_1.6.1-6.dsc
 706117ce6a36363519ce94e0e80c55fbcfae37f9 10944 
gpscorrelate_1.6.1-6.debian.tar.xz
 f40ecc550a8677932829d16548a999d76b827724 92992 
gpscorrelate-dbgsym_1.6.1-6_amd64.deb
 362cfe87e6ec2af7dd4a7026731bc2e3c6d8948e 115852 
gpscorrelate-gui-dbgsym_1.6.1-6_amd64.deb
 2d2fcc805fd7876aa5a168026364300ae64f6f83 42424 
gpscorrelate-gui_1.6.1-6_amd64.deb
 21bfb9441c7f0c754fce596dde9da9abd1f6d097 11286 
gpscorrelate_1.6.1-6_amd64.buildinfo
 34be4f9f6a9ab70c49c0f68635e0ce120ad4005a 109136 gpscorrelate_1.6.1-6_amd64.deb
Checksums-Sha256:
 8dd9940868663cca487ffc026365d588482c6c4745b40f54df7ec9713309a6cb 2083 
gpscorrelate_1.6.1-6.dsc
 1fafabe23f2aa3ee55a069ca005a2df220ebe83e51eb5cb8b2ab894b36d61d58 10944 
gpscorrelate_1.6.1-6.debian.tar.xz
 

Bug#878209: marked as done (apcupsd: please provide a split package without X11 deps)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#889670: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #889670,
regarding apcupsd: please provide a split package without X11 deps
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.)


-- 
889670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.14-1
Severity: normal

The new package adds in a dependecy on x11 for a package with heavy
server use. Please split the package so that servers do not need to add
an extra 65MB of x11 libs that they dont really need.

-- apt output below 

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following NEW packages will be installed:
   fontconfig (2.12.3-0.2)
   gconf-service (3.2.6-4+b1)
   gconf2-common (3.2.6-4)
   gnome-icon-theme (3.12.0-2)
   gtk-update-icon-cache (3.22.24-1)
   hicolor-icon-theme (0.17-1)
   libatk1.0-0 (2.26.0-2)
   libatk1.0-data (2.26.0-2)
   libavahi-client3 (0.7-3)
   libavahi-common-data (0.7-3)
   libavahi-common3 (0.7-3)
   libcairo2 (1.14.10-1)
   libcroco3 (0.6.12-1)
   libcups2 (2.2.4-8)
   libdatrie1 (0.2.10-5)
   libdbus-1-3 (1.11.20-1)
   libdbus-glib-1-2 (0.108-2)
   libgconf-2-4 (3.2.6-4+b1)
   libgdk-pixbuf2.0-0 (2.36.11-1)
   libgdk-pixbuf2.0-common (2.36.11-1)
   libgraphite2-3 (1.3.10-5)
   libgtk2.0-0 (2.24.31-2)
   libgtk2.0-common (2.24.31-2)
   libharfbuzz0b (1.5.1-1)
   libpango-1.0-0 (1.40.12-1)
   libpangocairo-1.0-0 (1.40.12-1)
   libpangoft2-1.0-0 (1.40.12-1)
   libpixman-1-0 (0.34.0-1)
   librsvg2-2 (2.40.18-1)
   librsvg2-common (2.40.18-1)
   libthai-data (0.1.26-3)
   libthai0 (0.1.26-3)
   libxcb-render0 (1.12-1)
   libxcb-shm0 (1.12-1)
   libxcomposite1 (1:0.4.4-2)
   libxcursor1 (1:1.1.14-3)
   libxdamage1 (1:1.1.4-3)
   libxext6 (2:1.3.3-1+b2)
   libxfixes3 (1:5.0.3-1)
   libxi6 (2:1.7.9-1)
   libxinerama1 (2:1.1.3-1+b3)
   libxrandr2 (2:1.5.1-1)
   libxrender1 (1:0.9.10-1)
The following packages will be upgraded:
   apcupsd (3.14.14-0.3 => 3.14.14-1)
1 upgraded, 43 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/22.5 MB of archives.
After this operation, 65.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do 

Bug#878209: marked as done (apcupsd: please provide a split package without X11 deps)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#878209: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #878209,
regarding apcupsd: please provide a split package without X11 deps
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.)


-- 
878209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.14-1
Severity: normal

The new package adds in a dependecy on x11 for a package with heavy
server use. Please split the package so that servers do not need to add
an extra 65MB of x11 libs that they dont really need.

-- apt output below 

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following NEW packages will be installed:
   fontconfig (2.12.3-0.2)
   gconf-service (3.2.6-4+b1)
   gconf2-common (3.2.6-4)
   gnome-icon-theme (3.12.0-2)
   gtk-update-icon-cache (3.22.24-1)
   hicolor-icon-theme (0.17-1)
   libatk1.0-0 (2.26.0-2)
   libatk1.0-data (2.26.0-2)
   libavahi-client3 (0.7-3)
   libavahi-common-data (0.7-3)
   libavahi-common3 (0.7-3)
   libcairo2 (1.14.10-1)
   libcroco3 (0.6.12-1)
   libcups2 (2.2.4-8)
   libdatrie1 (0.2.10-5)
   libdbus-1-3 (1.11.20-1)
   libdbus-glib-1-2 (0.108-2)
   libgconf-2-4 (3.2.6-4+b1)
   libgdk-pixbuf2.0-0 (2.36.11-1)
   libgdk-pixbuf2.0-common (2.36.11-1)
   libgraphite2-3 (1.3.10-5)
   libgtk2.0-0 (2.24.31-2)
   libgtk2.0-common (2.24.31-2)
   libharfbuzz0b (1.5.1-1)
   libpango-1.0-0 (1.40.12-1)
   libpangocairo-1.0-0 (1.40.12-1)
   libpangoft2-1.0-0 (1.40.12-1)
   libpixman-1-0 (0.34.0-1)
   librsvg2-2 (2.40.18-1)
   librsvg2-common (2.40.18-1)
   libthai-data (0.1.26-3)
   libthai0 (0.1.26-3)
   libxcb-render0 (1.12-1)
   libxcb-shm0 (1.12-1)
   libxcomposite1 (1:0.4.4-2)
   libxcursor1 (1:1.1.14-3)
   libxdamage1 (1:1.1.4-3)
   libxext6 (2:1.3.3-1+b2)
   libxfixes3 (1:5.0.3-1)
   libxi6 (2:1.7.9-1)
   libxinerama1 (2:1.1.3-1+b3)
   libxrandr2 (2:1.5.1-1)
   libxrender1 (1:0.9.10-1)
The following packages will be upgraded:
   apcupsd (3.14.14-0.3 => 3.14.14-1)
1 upgraded, 43 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/22.5 MB of archives.
After this operation, 65.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do 

Bug#576703: marked as done (apcupsd: variable PWRFAILDIR is not used by the supplied scripts)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#572727: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #572727,
regarding apcupsd: variable PWRFAILDIR is not used by the supplied scripts
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.)


-- 
572727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.8-2
Severity: wishlist


hi folks

i want to use apcupsd on a read-only root, only /var is writeable.
apcupsd.conf lets me configure the directory for the powerfail flag to
be written info via PWRFAILDIR. sadly this configuration is not used
by the supplied scripts apccontrol and ups-monitor.

greatings
arne wichmann


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'oldstable'), (800, 'experimental'), 
(800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apcupsd depends on:
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libwrap0  7.6.q-18   Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.8-2   APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.14-2   Hardware Abstraction Layer
ii  udev  151-2  /dev/ and hotplug management daemo

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 572...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 

Bug#779390: marked as done (gpscorrelate: Does not properly set the GPSTimeStamp tag)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:22:08 +
with message-id 
and subject line Bug#779390: fixed in gpscorrelate 1.6.1-6
has caused the Debian Bug report #779390,
regarding gpscorrelate: Does not properly set the GPSTimeStamp tag
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.)


-- 
779390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpscorrelate
Version: 1.6.1-4
Severity: normal
Tags: patch

Dear Maintainer,

After tagging some images with gpscorrelate, I figured out that the exif 
program complains with:

| Corrupt data
| The data provided does not follow the specification.
| ExifEntry: The tag 'GPSTimeStamp' contains data of an invalid format 
('SRational', expected 'Rational').

According to the EXIF standard, found at
  http://www.cipa.jp/std/documents/e/DC-008-2012_E.pdf
(page 68) the GPSTimeStamp tag is really supposed to be made of 3
RATIONAL values.

The attached patch fixes the problem.


Cheers,

-- 
Nicolas Boullis


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

Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gpscorrelate depends on:
ii  libc62.13-38+deb7u8
ii  libexiv2-12  0.23-1
ii  libgcc1  1:4.7.2-5
ii  libstdc++6   4.7.2-5
ii  libxml2  2.8.0+dfsg1-7+wheezy3

gpscorrelate recommends no packages.

gpscorrelate suggests no packages.

-- no debconf information
Index: gpscorrelate-1.6.1/exif-gps.cpp
===
--- gpscorrelate-1.6.1.orig/exif-gps.cpp	2009-04-05 03:08:45.0 +0200
+++ gpscorrelate-1.6.1/exif-gps.cpp	2015-02-28 00:27:02.355955052 +0100
@@ -620,7 +620,7 @@
 		memcpy(, tmp2, sizeof(struct tm));
 	}
 
-	Value = Exiv2::Value::create(Exiv2::signedRational);
+	Value = Exiv2::Value::create(Exiv2::unsignedRational);
 	snprintf(ScratchBuf, 100, "%d/1 %d/1 %d/1",
 			TimeStamp.tm_hour, TimeStamp.tm_min,
 			TimeStamp.tm_sec);


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: gpscorrelate
Source-Version: 1.6.1-6

We believe that the bug you reported is fixed in the latest version of
gpscorrelate, 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 779...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mònica Ramírez Arceda  (supplier of updated gpscorrelate 
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, 08 Apr 2018 22:28:23 +0200
Source: gpscorrelate
Binary: gpscorrelate gpscorrelate-gui
Architecture: source amd64
Version: 1.6.1-6
Distribution: unstable
Urgency: medium
Maintainer: Mònica Ramírez Arceda 
Changed-By: Mònica Ramírez Arceda 
Description:
 gpscorrelate - correlates digital photos with GPS data filling EXIF fields 
(comm
 gpscorrelate-gui - correlates digital photos with GPS data filling EXIF fields 
(GUI)
Closes: 683772 779390
Changes:
 gpscorrelate (1.6.1-6) unstable; urgency=medium
 .
   * Bump to Standard-Version 4.1.3. No changes required.
   * 60-gpstimestamp-unsigned.patch: Write the GPSTimeStamp tag as unsigned,
 as per spec. (Closes: #779390)
   * 70-option-overwrite-gpstags.patch: Add ability to force overwriting of
 existing tags. (Closes: #683772)
   * Update compatibility level to 11.
   * Use HTTPS in copyright format URL.
   * Migrate Vcs-* to salsa.debian.org.
Checksums-Sha1:
 9e23373485b03dbcdc8b2c29b50058d1d3d0fbfd 2083 gpscorrelate_1.6.1-6.dsc
 706117ce6a36363519ce94e0e80c55fbcfae37f9 10944 
gpscorrelate_1.6.1-6.debian.tar.xz
 f40ecc550a8677932829d16548a999d76b827724 92992 
gpscorrelate-dbgsym_1.6.1-6_amd64.deb
 362cfe87e6ec2af7dd4a7026731bc2e3c6d8948e 115852 
gpscorrelate-gui-dbgsym_1.6.1-6_amd64.deb
 2d2fcc805fd7876aa5a168026364300ae64f6f83 42424 
gpscorrelate-gui_1.6.1-6_amd64.deb
 21bfb9441c7f0c754fce596dde9da9abd1f6d097 

Bug#885820: marked as done (apcupsd: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#885820: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #885820,
regarding apcupsd: Depends on gconf
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.)


-- 
885820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

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

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

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 ab9895e1291d9e270969c3c48dc106dccb1f4c057b2229b6c992be5b33316993 2270 
apcupsd_3.14.14-2.dsc
 37a266d5dc3240227ff2f8d02fdf608a48d82f90665931ea315558b96f23b1ec 1816338 
apcupsd_3.14.14.orig.tar.gz
 ca44d511103ac8c0c26f5a10e54547474fe24a7112fc76166f05c2e395a9d67e 20480 
apcupsd_3.14.14-2.debian.tar.xz
 acf4f141c2a92ee9b37097c9c667cc55044ee82429afc82aae49c0cfc24a76c6 

Bug#541660: marked as done (powerfail file on read-only rootfs prevents apcupsd to start)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#572727: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #572727,
regarding powerfail file on read-only rootfs prevents apcupsd to start
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.)


-- 
572727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1
Severity: wishlist

- a powerfail file located on read-only roofs in /etc/apcupsd prevents apcupsd 
to start
- located under /var or using the configuration from /etc/apcupsd/apcupsd.conf 
in the
  /etc/init.d file would be more friendly to this systems.

  greetings, tobias


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-xen-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apcupsd depends on:
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libsnmp15   5.4.1~dfsg-12SNMP (Simple Network Management Pr
ii  libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.4-1lenny1 APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.11-8   Hardware Abstraction Layer
ii  udev  0.125-7+lenny1 /dev/ and hotplug management daemo

-- no debconf information

-- 
|--
| Tobias Becker - Bethesdaweg 14 - 33617 Bielefeld
| phone: +491705504552 | mail: tob...@tb-home.de


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 572...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 

Bug#889670: marked as done (GNOME required to run apcupsd?! really!?)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#889670: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #889670,
regarding GNOME required to run apcupsd?! really!?
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.)


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

Package: apcupsd
Version: 3.14.14-1

i believe package maintainer probably forgot (or never even thought) 
that apcupsd often used on servers which have no Xorg or GNOME! i will 
never install any part of GNOME (gconf-service, libatk1.0-0, libcairo, 
etc, etc) on any server of mine, so this new version of apcupsd package 
is no use to me. and i know for sure it's not just me


i propose removal of the following dependencies which are unnecessary to 
utilize apcupsd:


gconf-service, libatk1.0-0 (>= 1.12.4), libcairo2 (>= 1.2.4), 
ibfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgconf-2-4 (>= 
3.2.5), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk2.0-0 (>= 2.8.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 
(>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), libx11-6, libxext6


--
Vladislav Artemyev
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 

Bug#576703: marked as done (apcupsd: variable PWRFAILDIR is not used by the supplied scripts)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#541660: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #541660,
regarding apcupsd: variable PWRFAILDIR is not used by the supplied scripts
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.)


-- 
541660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.8-2
Severity: wishlist


hi folks

i want to use apcupsd on a read-only root, only /var is writeable.
apcupsd.conf lets me configure the directory for the powerfail flag to
be written info via PWRFAILDIR. sadly this configuration is not used
by the supplied scripts apccontrol and ups-monitor.

greatings
arne wichmann


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'oldstable'), (800, 'experimental'), 
(800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apcupsd depends on:
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libwrap0  7.6.q-18   Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.8-2   APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.14-2   Hardware Abstraction Layer
ii  udev  151-2  /dev/ and hotplug management daemo

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 

Bug#541660: marked as done (powerfail file on read-only rootfs prevents apcupsd to start)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#576703: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #576703,
regarding powerfail file on read-only rootfs prevents apcupsd to start
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.)


-- 
576703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1
Severity: wishlist

- a powerfail file located on read-only roofs in /etc/apcupsd prevents apcupsd 
to start
- located under /var or using the configuration from /etc/apcupsd/apcupsd.conf 
in the
  /etc/init.d file would be more friendly to this systems.

  greetings, tobias


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-xen-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apcupsd depends on:
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libsnmp15   5.4.1~dfsg-12SNMP (Simple Network Management Pr
ii  libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.4-1lenny1 APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.11-8   Hardware Abstraction Layer
ii  udev  0.125-7+lenny1 /dev/ and hotplug management daemo

-- no debconf information

-- 
|--
| Tobias Becker - Bethesdaweg 14 - 33617 Bielefeld
| phone: +491705504552 | mail: tob...@tb-home.de


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 576...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 

Bug#572727: marked as done (Fails If / is Read-Only)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#572727: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #572727,
regarding Fails If / is Read-Only
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.)


-- 
572727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1

The subject line tells the story. The scripts with apcupsd all assume
they can write to /etc/apcupsd/powerfail, which only works if / is
mounted read-write.


Two solutions jump to mind:
First solution, `init` has powerfail/powerok states; if that state is
passed to invoked scripts, then that can be used to decide whether an
attached UPS should powerdown or not.

Second solution, it might be better to tell init to change to state 6
(reboot), rather than 0 (halt) in case of power failure. This seems a
better description of a power failure situation, the system will try to
reboot ASAP, not the system is going down while someone plays with
hardware. In this case, whenever the system is rebooted, the driver for
the UPS would tell the UPS to power down if AC power is absent (or
batteries are too far depleted due to power restoration between reboot
request and calling the driver).


I'm wondering if #492094 is a similar situation?


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0




--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 572...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 

Bug#889670: marked as done (GNOME required to run apcupsd?! really!?)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#878209: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #878209,
regarding GNOME required to run apcupsd?! really!?
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.)


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

Package: apcupsd
Version: 3.14.14-1

i believe package maintainer probably forgot (or never even thought) 
that apcupsd often used on servers which have no Xorg or GNOME! i will 
never install any part of GNOME (gconf-service, libatk1.0-0, libcairo, 
etc, etc) on any server of mine, so this new version of apcupsd package 
is no use to me. and i know for sure it's not just me


i propose removal of the following dependencies which are unnecessary to 
utilize apcupsd:


gconf-service, libatk1.0-0 (>= 1.12.4), libcairo2 (>= 1.2.4), 
ibfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgconf-2-4 (>= 
3.2.5), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk2.0-0 (>= 2.8.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 
(>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), libx11-6, libxext6


--
Vladislav Artemyev
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 

Bug#572727: marked as done (Fails If / is Read-Only)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#576703: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #576703,
regarding Fails If / is Read-Only
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.)


-- 
576703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1

The subject line tells the story. The scripts with apcupsd all assume
they can write to /etc/apcupsd/powerfail, which only works if / is
mounted read-write.


Two solutions jump to mind:
First solution, `init` has powerfail/powerok states; if that state is
passed to invoked scripts, then that can be used to decide whether an
attached UPS should powerdown or not.

Second solution, it might be better to tell init to change to state 6
(reboot), rather than 0 (halt) in case of power failure. This seems a
better description of a power failure situation, the system will try to
reboot ASAP, not the system is going down while someone plays with
hardware. In this case, whenever the system is rebooted, the driver for
the UPS would tell the UPS to power down if AC power is absent (or
batteries are too far depleted due to power restoration between reboot
request and calling the driver).


I'm wondering if #492094 is a similar situation?


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0




--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 576...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 

Bug#572727: marked as done (Fails If / is Read-Only)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#541660: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #541660,
regarding Fails If / is Read-Only
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.)


-- 
541660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1

The subject line tells the story. The scripts with apcupsd all assume
they can write to /etc/apcupsd/powerfail, which only works if / is
mounted read-write.


Two solutions jump to mind:
First solution, `init` has powerfail/powerok states; if that state is
passed to invoked scripts, then that can be used to decide whether an
attached UPS should powerdown or not.

Second solution, it might be better to tell init to change to state 6
(reboot), rather than 0 (halt) in case of power failure. This seems a
better description of a power failure situation, the system will try to
reboot ASAP, not the system is going down while someone plays with
hardware. In this case, whenever the system is rebooted, the driver for
the UPS would tell the UPS to power down if AC power is absent (or
batteries are too far depleted due to power restoration between reboot
request and calling the driver).


I'm wondering if #492094 is a similar situation?


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0




--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 

Bug#541660: marked as done (powerfail file on read-only rootfs prevents apcupsd to start)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#541660: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #541660,
regarding powerfail file on read-only rootfs prevents apcupsd to start
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.)


-- 
541660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.4-1lenny1
Severity: wishlist

- a powerfail file located on read-only roofs in /etc/apcupsd prevents apcupsd 
to start
- located under /var or using the configuration from /etc/apcupsd/apcupsd.conf 
in the
  /etc/init.d file would be more friendly to this systems.

  greetings, tobias


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-xen-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apcupsd depends on:
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libsnmp15   5.4.1~dfsg-12SNMP (Simple Network Management Pr
ii  libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.4-1lenny1 APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.11-8   Hardware Abstraction Layer
ii  udev  0.125-7+lenny1 /dev/ and hotplug management daemo

-- no debconf information

-- 
|--
| Tobias Becker - Bethesdaweg 14 - 33617 Bielefeld
| phone: +491705504552 | mail: tob...@tb-home.de


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 

Bug#576703: marked as done (apcupsd: variable PWRFAILDIR is not used by the supplied scripts)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#576703: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #576703,
regarding apcupsd: variable PWRFAILDIR is not used by the supplied scripts
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.)


-- 
576703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apcupsd
Version: 3.14.8-2
Severity: wishlist


hi folks

i want to use apcupsd on a read-only root, only /var is writeable.
apcupsd.conf lets me configure the directory for the powerfail flag to
be written info via PWRFAILDIR. sadly this configuration is not used
by the supplied scripts apccontrol and ups-monitor.

greatings
arne wichmann


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'oldstable'), (800, 'experimental'), 
(800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apcupsd depends on:
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libwrap0  7.6.q-18   Wietse Venema's TCP wrappers libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.8-2   APC UPS Power Management (document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
ii  hal   0.5.14-2   Hardware Abstraction Layer
ii  udev  151-2  /dev/ and hotplug management daemo

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 576...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 

Bug#892950: marked as done (apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:22 +
with message-id 
and subject line Bug#892950: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #892950,
regarding apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1
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.)


-- 
892950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

apcupsd fails to build from source in unstable. Its Build-Depends are no
longer satisfiable, because python-imaging was removed from
pillow/5.0.0-1.

Helmut
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

We believe that the bug you reported is fixed in the latest version of
apcupsd, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd 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, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 ab9895e1291d9e270969c3c48dc106dccb1f4c057b2229b6c992be5b33316993 2270 
apcupsd_3.14.14-2.dsc
 37a266d5dc3240227ff2f8d02fdf608a48d82f90665931ea315558b96f23b1ec 1816338 
apcupsd_3.14.14.orig.tar.gz
 ca44d511103ac8c0c26f5a10e54547474fe24a7112fc76166f05c2e395a9d67e 20480 
apcupsd_3.14.14-2.debian.tar.xz
 acf4f141c2a92ee9b37097c9c667cc55044ee82429afc82aae49c0cfc24a76c6 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 2729f1db121568fa88565b874ee1e0e589552fe1c1a3d2fdc0c08eecce7d08be 94260 
apcupsd-cgi_3.14.14-2_amd64.deb
 462819bc2101a001e9f2a2d22282cbe49caab60382817377703253ff1b5325da 964504 

Bug#895213: marked as done (libbpp-popgen ftbfs on all architectures except on amd64)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:04:45 +
with message-id 
and subject line Bug#895213: fixed in libbpp-popgen 2.4.0-2
has caused the Debian Bug report #895213,
regarding libbpp-popgen ftbfs on all architectures except on amd64
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.)


-- 
895213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbpp-popgen
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-popgen ftbfs on all architectures except on amd64, please update the
symbols file
--- End Message ---
--- Begin Message ---
Source: libbpp-popgen
Source-Version: 2.4.0-2

We believe that the bug you reported is fixed in the latest version of
libbpp-popgen, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Dutheil  (supplier of updated 
libbpp-popgen 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: Sun, 08 Apr 2018 18:40:50 +0200
Source: libbpp-popgen
Binary: libbpp-popgen-dev libbpp-popgen8
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Dutheil 
Description:
 libbpp-popgen-dev - Bio++ Population Genetics library development files
 libbpp-popgen8 - Bio++ Population Genetics library
Closes: 895213
Changes:
 libbpp-popgen (2.4.0-2) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Provide symbols file only for amd64
 Closes: #895213
 .
   [ Andreas Tille ]
   * Provide full license text of CeCILL license
   * Point Vcs fields to salsa.debian.org
Checksums-Sha1:
 59efd2fd78f2329ecfae0f8148507a6248963723 2201 libbpp-popgen_2.4.0-2.dsc
 f2b3c72ef591819cc28be8908e7f0adf71642b63 18340 
libbpp-popgen_2.4.0-2.debian.tar.xz
 a106f288fd365ddd94baaf05218fbf1ba29c9332 13720 
libbpp-popgen_2.4.0-2_source.buildinfo
Checksums-Sha256:
 970d3c73c43b76db4343d33781e2fcbe8a4e93d02485bdee52f0486339dc22c8 2201 
libbpp-popgen_2.4.0-2.dsc
 4b0600a40f9568d5f54360dfa40b42925c29fc4e39573730d97d36a4f112e64d 18340 
libbpp-popgen_2.4.0-2.debian.tar.xz
 76797d071b15f4ed5369fc369a4149b7a6bedac13008656befdb6b123d7042dc 13720 
libbpp-popgen_2.4.0-2_source.buildinfo
Files:
 63f5eee0c6aac89f09e3eed95520e0b8 2201 science optional 
libbpp-popgen_2.4.0-2.dsc
 43c50b0070e5319dd341c854e4e3c30d 18340 science optional 
libbpp-popgen_2.4.0-2.debian.tar.xz
 9171df8695aaba9d105fb4fde6029d26 13720 science optional 
libbpp-popgen_2.4.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrKRnMOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEVcg//VSFByGDcJvwWP8klOUWCKT6rU98ogNiWKYFS
+y3e8My6tKC38eWXUe4hC/0iXVgY7XNdD2FLJeQraVuUyGS1CXKDd64GnEjkYAlf
bYkBdxr4Q7OxqxdEBDLjerH+tvvFJr9cKsHDVOXzggP6YaTDDGDKbX6ow7HC18j4
vuaPpX4D03sq9acz+pmQ6sX827DjQmDGgfDRnCetxe00j99+rpSxES7zlo5jRbke
A8c9UYjCyTui8jrf+2vhwGoKDhSKFfaRqtHU6lKhQRulGYZM+TygfMg1BR0ONgm9
4oJxK1bvWBqz3NPSbzUFPDSj2j5ptHko3ymd0DBQI/vOZ7bAVn8vHAHS/ebA5C7b
D5HgHGHs//HtXn64wOmkXqFO78TcUv+5xih0uhHrbXqCQeeO4W1ZhPuqyxO9CBqw
nZbSaDYgWa8YPhSB98l61WzDuwAoFHponX/BwnEUwVVqA+xR/H72ORpgVvcrYlFX
HhrBXykfKhAsuo5bjNb5/BECg0E3bYCL1oAdc6gBJ18CU0W786K9NHgWDcS46LCS
hXRd0RV7dME5djO8S3uuN89/TQX9bW/TY5XpiYUmNahE+xfG86ko3p2H2uLn4Toq
q8SZtyWbnVWgDwezYldtlgDuPACbpUZiyKedMmPjbZbr9ethlUWRBr65X74Pncvd
JRtYGnc=
=hbOP
-END PGP SIGNATURE End Message ---

Bug#624364: marked as done (samba4: Samba daemon doesn't removes its temporary files)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:04:50 +0200
with message-id 

and subject line Done in 4.0.0
has caused the Debian Bug report #624364,
regarding samba4: Samba daemon doesn't removes its temporary files
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.)


-- 
624364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba4
Version: 4.0.0~alpha15.dfsg1-1
Severity: normal


Every 10 min samba daemon creates temporary file (/tmp/tmp*) but does not
removes it.

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

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages samba4 depends on:
ii  debconf [debc 1.5.38 Debian configuration management sy
ii  libasn1-8-hei 1.4.0+git20110411.dfsg.1-1 Heimdal Kerberos - ASN.1 library
ii  libc6 2.11.2-13  Embedded GNU C Library: Shared lib
ii  libcomerr21.41.14-1  common error description library
ii  libdcerpc04.0.0~alpha15.dfsg1-1  DCE/RPC client library
ii  libgensec04.0.0~alpha15.dfsg1-1  Generic Security Library
ii  libhdb9-heimd 1.4.0+git20110411.dfsg.1-1 Heimdal Kerberos - kadmin server l
ii  libkdc2-heimd 1.4.0+git20110411.dfsg.1-1 Heimdal Kerberos - KDC support lib
ii  libkrb5-26-he 1.4.0+git20110411.dfsg.1-1 Heimdal Kerberos - libraries
ii  libldb1   1:1.1.0-1  LDAP-like embedded database - shar
ii  libndr-standa 4.0.0~alpha15.dfsg1-1  Standard NDR interfaces
ii  libndr0   4.0.0~alpha15.dfsg1-1  NDR marshalling library
ii  libpopt0  1.16-1 lib for parsing cmdline parameters
ii  libpython2.6  2.6.6-10   Shared Python runtime library (ver
ii  libroken18-he 1.4.0+git20110411.dfsg.1-1 Heimdal Kerberos - roken support l
ii  libsamba-host 4.0.0~alpha15.dfsg1-1  Samba host configuration library
ii  libsamba-util 4.0.0~alpha15.dfsg1-1  Samba utility function library
ii  libsamdb0 4.0.0~alpha15.dfsg1-1  SAM database
ii  libtalloc22.0.5-1hierarchical pool based memory all
ii  libtdb1   1.2.9-1Trivial Database - shared library
ii  libtevent00.9.11~git20110311-1   talloc-based event loop library - 
ii  python2.6.6-14   interactive high-level object-orie
ii  python-dnspyt 1.8.0-1DNS toolkit for Python
ii  python-samba  4.0.0~alpha15.dfsg1-1  Python bindings for Samba
ii  samba4-common 4.0.0~alpha15.dfsg1-1  Samba 4 common files used by both 

Versions of packages samba4 recommends:
ii  ldb-tools 1:1.1.0-1  LDAP-like embedded database - tool

Versions of packages samba4 suggests:
ii  bind9  1:9.7.3.dfsg-1+b1 Internet Domain Name Server
pn  phpldapadmin   (no description available)
pn  samba-gtk  (no description available)
pn  swat2  (no description available)

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Version: 2:4.1.3+dfsg-1

This was fixed by afd291b1dee44b2400bed119bccfc0b722d8cc9c in 4.0.0

Regards

-- 
Mathieu Parent

Ref: 
https://git.samba.org/?p=samba.git;a=commitdiff;h=afd291b1dee44b2400bed119bccfc0b722d8cc9c--- End Message ---

Bug#865013: marked as done (network-manager-gnome: Consistent segfault when connecting to WPA2 network)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:21:08 +
with message-id 
and subject line Bug#865013: fixed in network-manager-applet 1.8.10-3
has caused the Debian Bug report #865013,
regarding network-manager-gnome: Consistent segfault when connecting to WPA2 
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.)


-- 
865013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 1.4.6-1
Severity: important

Dear Maintainer,
After upgrading network-manager-gnome to 1.8.2-1, the network manager applet
segfaults every time I attempt to connect to a WPA network.

Sample output:
$ nm-applet
Segmentation fault


$ gdb nm-applet
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nm-applet...(no debugging symbols found)...done.
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n])
Starting program: /usr/bin/nm-applet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffebea6700 (LWP 2912)]
[New Thread 0x7fffeb6a5700 (LWP 2913)]
[New Thread 0x7fffea625700 (LWP 2914)]
[New Thread 0x7fffe9b5a700 (LWP 2915)]

Thread 1 "nm-applet" received signal SIGSEGV, Segmentation fault.
0x77ba87a2 in ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0
(gdb) c
Continuing.
Couldn't get registers: No such process.
Couldn't get registers: No such process.
Couldn't get registers: No such process.
(gdb) [Thread 0x7fffe9b5a700 (LWP 2915) exited]
[Thread 0x7fffea625700 (LWP 2914) exited]
[Thread 0x7fffeb6a5700 (LWP 2913) exited]
[Thread 0x7fffebea6700 (LWP 2912) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists

Attempting to dpkg-reconfigure network-manager-gnome and libnma0 had no effect.

Downgrading network-manager-gnome and libnma0 to 1.4.6-1 via `dpkg -i
/var/cache/apt/archives/network-manager-gnome_1.4.6-1_amd64.deb
/var/cache/apt/archives/libnma0_1.4.6-1_amd64.deb`, and restarting nm-applet,
immediately restored the ability to connect to the network.

I've only been able to test on a single WPA network.



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

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

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.18-1
ii  dbus-x11 [dbus-session-bus]   1.10.18-1
ii  dconf-gsettings-backend [gsettings-backend]   0.26.0-2+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11
ii  libcairo2 1.14.8-1
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.12-1
ii  libjansson4   2.9-1
ii  libmm-glib0   1.6.8-1
ii  libnm01.8.0-4
ii  libnma0   1.4.6-1
ii  libnotify40.7.7-2
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libsecret-1-0 0.18.5-3.1
ii  mate-polkit [polkit-1-auth-agent] 1.16.0-2
ii  network-manager   1.8.0-4

Versions of packages network-manager-gnome recommends:
pn  gnome-keyring   

Bug#743450: marked as done (Update README wrt netdev group and logind session)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:21:08 +
with message-id 
and subject line Bug#743450: fixed in network-manager-applet 1.8.10-3
has caused the Debian Bug report #743450,
regarding Update README wrt netdev group and logind session
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.)


-- 
743450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 0.9.8.8-1
Severity: normal

Dear Maintainer,

I just updated network-manager-gnome to find that nm-applet no longer worked.
After searching around for quite a long time, I found that I now need to be a
member of netdev to use nm-applet, which wasn't the case before (my upgrade was
from 0.9.8.4-1 to 0.9.8.8-1).
While this is documented in the README, which is laudable, I assume it will
still screw over many people when they upgrade.

Maybe it has to be this way. I'm just letting you know.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 1.8.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  gconf-service3.2.6-2
ii  gnome-icon-theme 3.12.0-1
ii  libatk1.0-0  2.10.0-2
ii  libc62.18-4
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libdbus-1-3  1.8.0-3
ii  libdbus-glib-1-2 0.102-1
ii  libgconf-2-4 3.2.6-2
ii  libgdk-pixbuf2.0-0   2.30.6-1
ii  libglib2.0-0 2.38.2-5
ii  libgnome-bluetooth11 3.8.1-2
ii  libgnome-keyring03.4.1-1
ii  libgtk-3-0   3.10.7-1
ii  libnm-glib-vpn1  0.9.8.0-5
ii  libnm-glib4  0.9.8.0-5
ii  libnm-gtk0   0.9.8.8-1
ii  libnm-util2  0.9.8.0-5
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libsecret-1-00.15-2
ii  network-manager  0.9.8.0-5
ii  policykit-1-gnome0.105-2

Versions of packages network-manager-gnome recommends:
ii  dunst [notification-daemon] 1.0.0-2
ii  gnome-bluetooth 3.8.1-2
ii  gnome-keyring   3.8.2-2+b1
ii  iso-codes   3.51-1
ii  mobile-broadband-provider-info  20130915-1
ii  notification-daemon 0.7.6-1

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
ii  network-manager-openvpn-gnome  0.9.8.4-1
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager-applet
Source-Version: 1.8.10-3

We believe that the bug you reported is fixed in the latest version of
network-manager-applet, 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 743...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager-applet 
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: Sun, 08 Apr 2018 18:58:14 +0200
Source: network-manager-applet
Binary: network-manager-gnome libnm-gtk0 libnm-gtk-dev gir1.2-nmgtk-1.0 libnma0 
libnma-dev gir1.2-nma-1.0
Architecture: source
Version: 1.8.10-3
Distribution: unstable
Urgency: medium

Bug#895056: marked as done (Dh_Lib.pm: avoid creating empty log of installed files)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 13:00:22 +0200
with message-id <20180408110022.ga16...@nicolasthinkpad.home>
and subject line close 895056
has caused the Debian Bug report #895056,
regarding Dh_Lib.pm: avoid creating empty log of installed files
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.)


-- 
895056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.6
Severity: wishlist
Tags: patch

In Dh_Lib.pm, "sub log_installed_files" starts with:
  return if $dh{NO_ACT};
I suggest
  return if $dh{NO_ACT} or not @patterns;
instead so that the file is only created if it is useful.
(seen with DEB_BUILD_OPTIONS=nodoc dh_installinfo).
--- End Message ---
--- Begin Message ---
My mistake.
Sorry for the noise.--- End Message ---

Bug#895082: marked as done (sendmail: Please replace 'c_rehash' with 'openssl rehash')

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:14:28 +0200
with message-id <20180408201426.oncza6pxltem2...@mikejones.breakpoint.cc>
and subject line Re: Bug#895082: sendmail: Please replace 'c_rehash' with 
'openssl rehash'
has caused the Debian Bug report #895082,
regarding sendmail: Please replace 'c_rehash' with 'openssl rehash'
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.)


-- 
895082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Version: 8.15.2-11
Severity: normal
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: c_rehash

This package is using the c_rehash command which is part of the
openssl package. The c_rehash script is considered by upstream as a
fallback script and will disappear at some point. The recommended way
is to use the "openssl rehash" command instead which appeared in
1.1.0. Please make sure that this package does not use the c_rehash
command anymore.

The "openssl rehash" command creates half that many symlinks (one per
certificate instead of two) because it uses only the newer hash.
There is also the -compat option which creates both symlinks (and
behaves like c_rehash currently does). The hash changed from md5 to
sha1 during the 0.9.8 to 1.0.0 transition so I doubt that the
"compat" mode will be required.

Should the c_rehash script be mentioned in the source code or script
of this package but is not used during the build process or in the
final package then feel free to close the bug saying so.

Sebastian 
--- End Message ---
--- Begin Message ---
On 2018-04-08 00:56:31 [+0200], Andreas Beckmann wrote:
> The only occurrence I could find is in some documentation:

I'm sorry. I actually tried / intended to skip doc-only packages. Here I
failed.

> ./doc/op/op.me:
> ...
> A better way to do this is to use the
> .b c_rehash
> command that is part of the OpenSSL distribution
> because it handles subject hash collisions
> by incrementing the number in the suffix of the filename of the symbolic
> link,
> e.g.,
> .b \&.0
> to
> .b \&.1 ,
> and so on.
> ...
> 
> Should I change that sentence? How?

c_rehash -> openssl rehash

but forget about it. I closed the bug. Sorry for the noise.

> Andreas

Sebastian--- End Message ---

Bug#895219: marked as done (lebiniou: Erreur premier lancement)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 23:13:24 +0200
with message-id <37d8687b-4516-d778-1382-df106fd13...@biniou.info>
and subject line Re: Bug#895219: lebiniou: Erreur premier lancement
has caused the Debian Bug report #895219,
regarding lebiniou: Erreur premier lancement
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.)


-- 
895219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lebiniou
Version: 3.24-1
Severity: minor

Bonjour Olivier,

Je viens d'installer le paquet lebiniou sur ma Debian testing mais lors du 
lancement du programme, j'ai le message d'erreur ci-dessous :

nicolas@celine:~$ lebiniou
[!] System error: creat: Permission denied
nicolas@celine:~$ lebiniou -v
Le Biniou version 3.24

Est-il possible d'identifier le problème svp ?
Je ne vois rien de particulier dans les logs.

Merci d'avance.
Cordialement,
Nicolas.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'oldstable')
Architecture: i386 (i686)

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

Versions of packages lebiniou depends on:
ii  fonts-freefont-ttf20120503-7
ii  lebiniou-data 3.11-1
ii  libasound21.1.3-5
ii  libavutil55   10:3.4.2-dmo3
ii  libc6 2.25-3
ii  libfftw3-double3  3.3.7-1
ii  libglib2.0-0  2.56.0-4
ii  libjack-jackd2-0 [libjack-0.116]  1.9.12~dfsg-2
ii  libpnglite0   0.1.17-2
ii  libpulse0 11.1-4
ii  libsdl-ttf2.0-0   2.0.11-4
ii  libsdl1.2debian   1.2.15+dfsg2-0.1
ii  libswscale4   10:3.4.2-dmo3
ii  libxml2   2.9.4+dfsg1-6.1

lebiniou recommends no packages.

lebiniou suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 87852--- End Message ---

Bug#895238: marked as done (postfix: consider changing the default mailer type to "Local only" instead of "Internet site")

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:41:01 +
with message-id <8c867c8d-0a56-40cc-8c33-473ae2960...@kitterman.com>
and subject line Re: Bug#895238: postfix: consider changing the default mailer 
type to "Local only" instead of "Internet site"
has caused the Debian Bug report #895238,
regarding postfix: consider changing the default mailer type to "Local only" 
instead of "Internet site"
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.)


-- 
895238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.3.0-1
Severity: wishlist

Hi,

I report this bug following my own advice in [1].

I have set the severity to wishlist, but from a security point of view,
it could be considered much higher.

The default Postfix configuration, when keeping the default debconf
answers, listens on all network interfaces. Unlike what's said in
#418511, this doesn't make it an open relay though, since mynetworks is
restricted to localhost. Nevertheless, OP in [1] is IMHO quite right,
this is still a "network-exposed attack surface".

My rationale is : until Stretch, the "standard" installation comprised
exim4-daemon-light, which fulfilled all dependencies on the
"mail-transport-agent" virtual package, which in turn implicated that
users installing Postfix did so manually, and knew what they were doing.

Unfortunately, from Stretch onward, now that no MTA is present in the
standard installation, some dependencies chains can end up installing a
random MTA "unexpectedly" (I put quotes around "unexpectedly", because
one should always carefully read the list of installed dependencies when
installing a package, but we all know that users are not always that
careful).

IMHO it would be wise to change the default answer to the debconf
question "postfix/main_mailer_type" to "Local only" instead of "Internet
site", in order to limit the security risk in case Postfix was installed
"unexpectedly" due of an overlooked dependency chain.

[1] https://bugs.launchpad.net/debian/+source/tlp/+bug/1758798

Regards,

-- 
Raphaël Halimi
--- End Message ---
--- Begin Message ---


On April 8, 2018 6:31:25 PM UTC, "Raphaël Halimi"  
wrote:
>Le 08/04/2018 à 20:26, Scott Kitterman a écrit :
>> Your example isn't relevant to Debian.  In Ubuntu, Postfix is the
>> default MTA.  In Debian, it's not.  If a non-default MTA is being
>> pulled in by a package that only needs a generic MTA, then it's buggy
>> and should be fixed.
>
>Ah, sorry, I don't use Ubuntu, so I didn't know.
>
>Feel free to close the bug then, if you think it's not relevant.

Closing then.

Thanks,

Scott K--- End Message ---

Bug#831306: marked as done (Updating the libnet-arp-perl Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 16:34:29 +
with message-id 
and subject line Bug#831306: fixed in libnet-arp-perl 1.0.9-1
has caused the Debian Bug report #831306,
regarding Updating the libnet-arp-perl Uploaders list
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.)


-- 
831306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-arp-perl
Version: 1.0.8-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Franck Joncourt  has retired, so can't work on
the libnet-arp-perl package anymore (at least with this address).

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

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

Thanks.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libnet-arp-perl
Source-Version: 1.0.9-1

We believe that the bug you reported is fixed in the latest version of
libnet-arp-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 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-arp-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: SHA512

Format: 1.8
Date: Sun, 08 Apr 2018 18:17:18 +0200
Source: libnet-arp-perl
Binary: libnet-arp-perl
Architecture: source
Version: 1.0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 831306
Description: 
 libnet-arp-perl - module to create ARP packets and lookup for ARP information
Changes:
 libnet-arp-perl (1.0.9-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ gregor herrmann ]
   * Add debian/gbp.conf to filter out .git from upstream tarball.
   * New upstream release.
   * Drop debian/patches/bsd-missing-includes.patch, merged upstream.
   * Don't install README anymore.
   * Update years of packaging copyright.
   * Mark package as autopkgtest-able.
   * Declare compliance with Debian Policy 3.9.6.
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Remove Franck Joncourt from Uploaders.
 Thanks to Tobias Frost (Closes: #831306)
 .
   [ gregor herrmann ]
   * Remove Ryan Niebur from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.1.4.
   * Bump debhelper compatibility level to 10.
   * Set bindnow linker flag in debian/rules.
   * autopkgtest: activate use.t test by adding debian/tests/pkg-perl/use-
 name.
Checksums-Sha1: 
 5c1971b0d615afe2887a27baf692cdc9204656cf 2220 libnet-arp-perl_1.0.9-1.dsc
 bd8067ec9cae6693e9c038df35e3c7415eedfaf4 71377 
libnet-arp-perl_1.0.9.orig.tar.gz
 0c278b0e267a23feffc451e2088b4d575c98914a 4984 
libnet-arp-perl_1.0.9-1.debian.tar.xz
Checksums-Sha256: 
 a10a5044ef43e3a5ef0a1d1db0e68274e6fba5d111460ab28ce9147088e5706f 2220 
libnet-arp-perl_1.0.9-1.dsc
 53fc3883755d75bed1671f9844f131ad364bdfb18313ed1ea78dc67b6901b18e 71377 
libnet-arp-perl_1.0.9.orig.tar.gz
 2b1141bc05034a8acaa105b68b07dbaf4cecc313d6def27eb1851657368aa1fe 4984 
libnet-arp-perl_1.0.9-1.debian.tar.xz
Files: 
 e4646809ba52fa7178acad78e96260e7 2220 perl optional libnet-arp-perl_1.0.9-1.dsc
 bb693890d93bc84831663edb1a5c5d45 71377 perl optional 
libnet-arp-perl_1.0.9.orig.tar.gz
 b45780808f9bb6f07ff06a7f87a366c3 4984 perl optional 
libnet-arp-perl_1.0.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#502644: marked as done (network-manager-gnome: keyring prompts should be optional)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 18:21:02 +0200
with message-id <98b9b531-c132-1045-338e-1f64b4eee...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#502644: 
network-manager-gnome: keyring prompts should be optional
has caused the Debian Bug report #502644,
regarding network-manager-gnome: keyring prompts should be optional
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.)


-- 
502644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 0.6.6-2
Severity: minor

n-m-g should provide an option to disable integration with the GNOME keyring, 
since some users (myself included) prefer to manually 
store their passwords and network credentials in a third-party password manager.

Thanks,
N.D.

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

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager-gnome depends on:
ii  libc6 2.7-15 GNU C Library: Shared libraries
ii  libdbus-1-3   1.2.1-3simple interprocess messaging syst
ii  libdbus-glib-1-2  0.76-1 simple interprocess messaging syst
ii  libgconf2-4   2.22.0-1   GNOME configuration database syste
ii  libglade2-0   1:2.6.2-1  library to load .glade files at ru
ii  libglib2.0-0  2.16.6-1   The GLib library of C routines
ii  libgnome-keyring0 2.22.3-2   GNOME keyring services library
ii  libgnome2-0   2.20.1.1-1 The GNOME 2 library - runtime file
ii  libgnomeui-0  2.20.1.1-2 The GNOME 2 libraries (User Interf
ii  libgtk2.0-0   2.12.11-4  The GTK+ graphical user interface 
ii  libnm-util0   0.6.6-2network management framework (shar
ii  libnotify1 [libnotify1-gtk2.1 0.4.4-3sends desktop notifications to a n
ii  libpango1.0-0 1.20.5-3   Layout and rendering of internatio
ii  libx11-6  2:1.1.5-2  X11 client-side library
ii  network-manager   0.6.6-2network management framework daemo

Versions of packages network-manager-gnome recommends:
pn  libpam-keyring (no description available)
ii  network-manager-openvpn 0.3.2svn2855-1.1 network management framework (Open
pn  network-manager-vpnc-gn(no description available)
ii  notification-daemon 0.3.7-1+b1   a daemon that displays passive pop

network-manager-gnome suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On Fri, 26 Dec 2008 17:57:00 +0100 Michael Biebl  wrote:
> tags 502644 wontfix
> thanks
> 
> Nathan Davidson wrote:
> > Package: network-manager-gnome
> > Version: 0.6.6-2
> > Severity: minor
> > 
> > n-m-g should provide an option to disable integration with the GNOME 
> > keyring, since some users (myself included) prefer to manually 
> > store their passwords and network credentials in a third-party password 
> > manager.
> 
> Hi,
> 
> I don't see the value in needlessly complicating the code for no real gain. So
> I'm marking this bug wontfix, as I'm not going to implement this myself.
> 
> I would take a look at a patch, if provided.
> 

Such a patch was never submitted, so closing this bug report.

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#680288: marked as done (network-manager-gnome: options dialog of mobile broadband can not be accessed if connection can not be established?)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 18:20:00 +0200
with message-id 
and subject line Re: network-manager-gnome: options dialog of mobile broadband 
can not be accessed if connection can not be established?
has caused the Debian Bug report #680288,
regarding network-manager-gnome: options dialog of mobile broadband can not be 
accessed if connection can not be established?
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.)


-- 
680288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 0.9.4.1-1+b1
Severity: normal

I recorded a screencast that shows how the bug occurs:

http://lindi.iki.fi/lindi/screencast/network-manager-gnome-fixing-APN-not-possible-after-mistake.webm

Steps to reproduce:
1) setup usb 3G modem and use it
2) go to "Options..." of the broadband connection and change the APN to
   something invalid.
3) unplug and replug the modem
4) Try to go to the "Options..." to fix the APN.

Expected results:
4) The "Options..." dialog can be accessed and the mistake made by the
   user in step 2) can be corrected.

Actual results:
4) The "Options..." dialog is grayed out. The user is helpless and the
   only way to fix the situation seems to be to edit /etc/ from command
   line.


but 
-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-gnome depends on:
ii  dbus-x11  1.6.0-1
ii  dpkg  1.16.4.3
ii  gconf-service 3.2.5-1
ii  gconf23.2.5-1
ii  gnome-icon-theme  3.4.0-2
ii  libatk1.0-0   2.4.0-2
ii  libc6 2.13-33
ii  libcairo-gobject2 1.12.2-1
ii  libcairo2 1.12.2-1
ii  libdbus-1-3   1.6.0-1
ii  libdbus-glib-1-2  0.98-1
ii  libgconf-2-4  3.2.5-1
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libglib2.0-0  2.32.3-1
ii  libgnome-bluetooth10  3.4.1-1
ii  libgnome-keyring0 3.4.1-1
ii  libgtk-3-03.4.2-1
ii  libnm-glib-vpn1   0.9.4.0-5
ii  libnm-glib4   0.9.4.0-5
ii  libnm-gtk00.9.4.1-1+b1
ii  libnm-util2   0.9.4.0-5
ii  libnotify40.7.5-1
ii  libpango1.0-0 1.30.0-1
ii  network-manager   0.9.4.0-5
ii  policykit-1-gnome 0.105-2

Versions of packages network-manager-gnome recommends:
ii  gnome-bluetooth3.4.1-1
ii  iso-codes  3.36-1
ii  libpam-gnome-keyring [libpam-keyring]  3.4.1-4
ii  mobile-broadband-provider-info 20120402-1
ii  notification-daemon0.7.5-1

Versions of packages network-manager-gnome suggests:
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information


--- End Message ---
--- Begin Message ---
On Wed, 04 Jul 2012 22:59:49 +0300 Timo Juhani Lindfors
 wrote:
> Package: network-manager-gnome
> Version: 0.9.4.1-1+b1
> Severity: normal
> 
> I recorded a screencast that shows how the bug occurs:
> 
> http://lindi.iki.fi/lindi/screencast/network-manager-gnome-fixing-APN-not-possible-after-mistake.webm
> 
> Steps to reproduce:
> 1) setup usb 3G modem and use it
> 2) go to "Options..." of the broadband connection and change the APN to
>something invalid.
> 3) unplug and replug the modem
> 4) Try to go to the "Options..." to fix the APN.
> 
> Expected results:
> 4) The "Options..." dialog can be accessed and the mistake made by the
>user in step 2) can be corrected.
> 
> Actual results:
> 4) The "Options..." dialog is grayed out. The user is helpless and the
>only way to fix the situation seems to be to edit /etc/ from command
>line.

This seems to have been a gnome-control-center issue which is supposed
to be fixed since version 3.6. Thus closing this bug report.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#893238: marked as done (libgoogle-gson-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:34:22 +
with message-id 
and subject line Bug#893238: fixed in libgoogle-gson-java 2.8.2-1
has caused the Debian Bug report #893238,
regarding libgoogle-gson-java FTBFS with openjdk-9
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.)


-- 
893238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgoogle-gson-java
Version: 2.4-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgoogle-gson-java.html

...
[ERROR] Failures: 
[ERROR]   
DefaultDateTypeAdapterTest.testFormatUsesDefaultTimezone:119->assertFormatted:155
 expected: but was:
[ERROR]   
DefaultDateTypeAdapterTest.testFormattingInEnUs:34->assertFormattingAlwaysEmitsUsLocale:47->assertFormatted:155
 expected: but was:
[ERROR]   
DefaultDateTypeAdapterTest.testFormattingInFr:38->assertFormattingAlwaysEmitsUsLocale:47->assertFormatted:155
 expected: but was:
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateSerialization:332 
expected:<"Sep 11, 2011[] 10:55:03 PM"> but was:<"Sep 11, 2011[,] 10:55:03 PM">
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateSerializationUsingBuilder:399 
expected:<"Sep 11, 2011[] 10:55:03 PM"> but was:<"Sep 11, 2011[,] 10:55:03 PM">
[ERROR]   DefaultTypeAdaptersTest.testDefaultJavaSqlTimestampSerialization:373 
expected:<"Dec 3, 2009[] 1:18:02 PM"> but was:<"Dec 3, 2009[,] 1:18:02 PM">
[ERROR]   ObjectTest.testDateAsMapObjectField:485 expected:<..."date":"Dec 31, 
1969[] 4:00:00 PM"}}> but was:<..."date":"Dec 31, 1969[,] 4:00:00 PM"}}>
[ERROR] Errors: 
[ERROR]   
DefaultDateTypeAdapterTest.testParsingDatesFormattedWithSystemLocale:71->assertParsed:159
 ? JsonSyntax
[ERROR]   
DefaultDateTypeAdapterTest.testParsingDatesFormattedWithUsLocale:95->assertParsed:159
 ? JsonSyntax
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateDeserialization:337 ? 
JsonSyntax Dec 13...
[ERROR]   
DefaultTypeAdaptersTest.testDefaultJavaSqlTimestampDeserialization:378 ? 
JsonSyntax
[INFO] 
[ERROR] Tests run: 966, Failures: 7, Errors: 4, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 13.058 s
[INFO] Finished at: 2018-03-17T01:41:55-12:00
[INFO] Final Memory: 17M/56M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project gson: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/build/1st/libgoogle-gson-java-2.4/gson/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/libgoogle-gson-java-2.4 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/libgoogle-gson-java-2.4/debian 
-Dmaven.repo.local=/build/1st/libgoogle-gson-java-2.4/debian/maven-repo 
--batch-mode --file gson/pom.xml returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: libgoogle-gson-java
Source-Version: 2.8.2-1

We believe that the bug you reported is fixed in the latest version of
libgoogle-gson-java, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libgoogle-gson-java 
package)

(This message was generated 

Bug#821121: marked as done (samba-libs: libsamba-debug.so unavailable)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:22:16 +0200
with message-id 

and subject line Closing
has caused the Debian Bug report #821121,
regarding samba-libs: libsamba-debug.so unavailable
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.)


-- 
821121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-libs
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: important

Dear Maintainer,

   * What led up to the situation?
The samba-libs package renders greyhole (redundant storage pooling using Samba) 
nonfunctional.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

The readelf command shows a dependency of the greyhole VFS module upon 
libsamba-debug-samba4.so, which is not provided by the samba-libs package. By 
comparison, it is provided in the stretch (testing) package, and in 
corresponding RPMs for other linux distros.

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

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

Versions of packages samba-libs depends on:
ii  libacl12.2.52-2
ii  libattr1   1:2.4.47-2
ii  libbsd00.7.0-2
ii  libc6  2.19-18+deb8u4
ii  libcap21:2.24-8
ii  libcups2   1.7.5-11+deb8u1
ii  libgnutls-deb0-28  3.3.8-6+deb8u3
ii  libldap-2.4-2  2.4.40+dfsg-1+deb8u2
ii  libldb12:1.1.20-0+deb8u1
ii  libntdb1   1.0-5
ii  libpam0g   1.1.8-3.1+deb8u1+b1
ii  libpopt0   1.16-10
ii  libpython2.7   2.7.9-2
ii  libtalloc2 2.1.2-0+deb8u1
ii  libtdb11.3.6-0+deb8u1
ii  libtevent0 0.9.25-0+deb8u1
ii  libwbclient0   2:4.2.10+dfsg-0+deb8u2
ii  multiarch-support  2.19-18+deb8u4
ii  python-talloc  2.1.2-0+deb8u1
ii  zlib1g 1:1.2.8.dfsg-2+b1

samba-libs recommends no packages.

samba-libs suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug, as we won't make any major change in jessie (oldstable).

Apparently this bug is fixed in stretch, but as noted, we won't
support out-of-tree vfs modules .

Regards

-- 
Mathieu Parent--- End Message ---

Bug#895212: marked as done (libbpp-seq-omics ftbfs on all archs except amd64)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 16:49:33 +
with message-id 
and subject line Bug#895212: fixed in libbpp-seq-omics 2.4.0-2
has caused the Debian Bug report #895212,
regarding libbpp-seq-omics ftbfs on all archs except amd64
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.)


-- 
895212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbpp-seq-omics
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-seq-omics ftbfs on all archs except amd64. an update of the symbols file
is in order.
--- End Message ---
--- Begin Message ---
Source: libbpp-seq-omics
Source-Version: 2.4.0-2

We believe that the bug you reported is fixed in the latest version of
libbpp-seq-omics, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Dutheil  (supplier of updated 
libbpp-seq-omics 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: Sun, 08 Apr 2018 18:29:27 +0200
Source: libbpp-seq-omics
Binary: libbpp-seq-omics-dev libbpp-seq-omics3
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Dutheil 
Description:
 libbpp-seq-omics-dev - Bio++ Sequence library: genomics components 
(development files)
 libbpp-seq-omics3 - Bio++ Sequence library: genomics components
Closes: 895212
Changes:
 libbpp-seq-omics (2.4.0-2) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Provide symbols file only for amd64
 Closes: #895212
   * Versioned Build-Depends: d-shlibs (>= 0.82)
 .
   [ Andreas Tille ]
   * Provide full license text of CeCILL license
   * Point Vcs fields to salsa.debian.org
Checksums-Sha1:
 9a7710575a33af0720787d4a9bb35282d07dced1 2212 libbpp-seq-omics_2.4.0-2.dsc
 40aa361faaa82eb47820ef0dde4258a2fe518789 16836 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 7c6e8d5307295bbb2bd35808075f0fe1fa826ad8 13738 
libbpp-seq-omics_2.4.0-2_source.buildinfo
Checksums-Sha256:
 bfe032c93fc87dda8b011732fcb775623fe803f6fac80e8c774dee77b401f865 2212 
libbpp-seq-omics_2.4.0-2.dsc
 7c1a765402ea9893b618365a4625a4384e244f8bf8181f9bd92cd015c4ecd48e 16836 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 07eca4a1b54f16797080e0dc7d0e0330b326f48d9c4b9a2c4835df7aa4cb0ed2 13738 
libbpp-seq-omics_2.4.0-2_source.buildinfo
Files:
 6bebaa48be781b3901c85662ce121389 2212 science optional 
libbpp-seq-omics_2.4.0-2.dsc
 c3492ec3d93bc9f95f9e8257a174dad1 16836 science optional 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 5726dc7365c45bd6806b931745e3a09c 13738 science optional 
libbpp-seq-omics_2.4.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrKQ6UOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHx0g//WvZV9opGUVYOu0BY0jhLRGa4N5yWKEf74F4Y
28vmix3ovN6cpffH1RmdToGODJKWaDiM3L2lQiwTxYYMlPZ+Qrcd9pXbT8UQRNlz
xUbxYpAeDh9WdlKCmMXYtJZX4Y0QvP1eN/IQywI6kojje989LnN2MeeCeGihacXE
odSOInaqLS1q5IGnRjFTadDjjn0GC1z82inQWAntN9fcb2lGhSVXNUZH20716I6z
j/rYc2X3pm2dsTgZ1t/lztKfqbmtDD1683kIAz8U/rcrV7dphmWznnJfOe3gpkvW
LjlRtTLfEGe66cCcjb1L6LLX/vDAfygP7bkA93KFgEJ03YCo1bD4OI1GME9wXBpn
pBEXJqMB7EvYBdqL2X59yTCr9Y54wLBvQ0CZoAqzMzNpUlu8uI+7cFlxssqmR9r5
FKgxv9g4ppB0LteVSRCfzUHLkKJoDudDvwaDWjDpQ8pI6H6dwNhY84RPx+7EQ5xM
WgJkyRKa9Nf9F7O8qtLGtSyCTmHfGbgBBhO7my84gTU/B/ssFnD/ZiyB4YxXQU/Y
1laPmE6T9dYEnOrMdWJRZw2h630jPJwnT4jYdOojFgx+m3a7ueaq2zZLuWzVWR96
FhAfvQwEQgD6MBG7dJQYVX+DLhW2sEKZd5mzndttoO3PI517fHPjEFZjmosLbQQi
wJkny18=
=0hfd
-END PGP SIGNATURE End Message ---

Bug#883965: marked as done (nm-connection-editor crashes when opening a connection)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:21:08 +
with message-id 
and subject line Bug#865013: fixed in network-manager-applet 1.8.10-3
has caused the Debian Bug report #865013,
regarding nm-connection-editor crashes when opening a connection
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.)


-- 
865013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 1.8.6-1
Severity: important

Since 1-2 months, nm-connection-editor immediately crashes when I click 
on the "modify" button.

(gdb) run
Starting program: /usr/bin/nm-connection-editor 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeade2700 (LWP 29377)]
[New Thread 0x7fffea5e1700 (LWP 29378)]
[New Thread 0x7fffe9542700 (LWP 29379)]
[New Thread 0x7fffe8d41700 (LWP 29380)]

Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault.
0x77bab4d3 in modules_initialized (object=, 
res=0x55f21f40, user_data=user_data@entry=0x55fac380) at 
src/libnma/nma-cert-chooser-button.c:98
98  src/libnma/nma-cert-chooser-button.c: No such file or directory.
(gdb) bt
#0  0x77bab4d3 in modules_initialized (object=, 
res=0x55f21f40, user_data=user_data@entry=0x55fac380) at 
src/libnma/nma-cert-chooser-button.c:98
#1  0x754ecd23 in process_result (unused=0x0, call=0x55f21f40) at 
gck/gck-call.c:151
#2  process_completed (klass=) at gck/gck-call.c:165
#3  0x754ed65c in _gck_call_async_go (call=0x55fbb1d0) at 
gck/gck-call.c:498
#4  0x766d6745 in g_type_create_instance (type=) at 
../../../../gobject/gtype.c:1866
#5  0x766b75e8 in g_object_new_internal 
(class=class@entry=0x55f22400, params=params@entry=0x7fffb080, 
n_params=n_params@entry=2) at ../../../../gobject/gobject.c:1797
#6  0x766b9460 in g_object_new_valist (object_type=93825003062448, 
first_property_name=first_property_name@entry=0x77eb "model", 
var_args=var_args@entry=0x7fffb1d0) at ../../../../gobject/gobject.c:2120
#7  0x766b97d9 in g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x77eb "model") at 
../../../../gobject/gobject.c:1640
#8  0x77babe12 in nma_cert_chooser_button_new 
(flags=flags@entry=NMA_CERT_CHOOSER_BUTTON_FLAG_NONE) at 
src/libnma/nma-cert-chooser-button.c:447
#9  0x77bac8ae in init (cert_chooser=0x5588c3c0) at 
src/libnma/nma-pkcs11-cert-chooser.c:481
#10 0x77ba7eab in constructor (type=, 
n_construct_properties=, construct_properties=) 
at src/libnma/nma-cert-chooser.c:635
#11 0x766b741e in g_object_new_with_custom_constructor (n_params=2, 
params=0x7fffb550, class=0x55fa7ca0) at 
../../../../gobject/gobject.c:1715
#12 g_object_new_internal (class=class@entry=0x55fa7ca0, 
params=params@entry=0x7fffb550, n_params=n_params@entry=2) at 
../../../../gobject/gobject.c:1795
#13 0x766b9460 in g_object_new_valist (object_type=93825003059152, 
first_property_name=, var_args=var_args@entry=0x7fffb6a0) at 
../../../../gobject/gobject.c:2120
#14 0x766b97d9 in g_object_new (object_type=, 
first_property_name=) at ../../../../gobject/gobject.c:1640
#15 0x555a25fc in ?? ()
#16 0x5559e427 in ?? ()
#17 0x555a05af in ?? ()
#18 0x555746a3 in ?? ()
#19 0x766b1f9d in g_closure_invoke (closure=0x55d9e0d0, 
return_value=0x0, n_param_values=2, param_values=0x7fffbaf0, 
invocation_hint=0x7fffba70) at ../../../../gobject/gclosure.c:804
#20 0x766c4cae in signal_emit_unlocked_R 
(node=node@entry=0x55c14d40, detail=detail@entry=0, 
instance=instance@entry=0x55bcdba0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffbaf0) at 
../../../../gobject/gsignal.c:3635
#21 0x766cd485 in g_signal_emit_valist (instance=0x55bcdba0, 
signal_id=, detail=0, var_args=var_args@entry=0x7fffbcc0) at 
../../../../gobject/gsignal.c:3391
#22 0x766cde9f in g_signal_emit (instance=, 
signal_id=, detail=) at 
../../../../gobject/gsignal.c:3447
#23 0x55571453 in ?? ()
#24 0x5556beed in ?? ()
#25 0x5556d746 in ?? ()
#26 0x766b1f9d in g_closure_invoke (closure=0x55acaeb0, 
return_value=0x0, n_param_values=1, param_values=0x7fffc030, 
invocation_hint=0x7fffbfb0) at ../../../../gobject/gclosure.c:804
#27 

Bug#890713: marked as done (ftp.debian.org: please allow mipsel uploads with mips64el GPG keys)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 23:13:13 +0200
with message-id <20180408211313.ga14...@aurel32.net>
and subject line Bug#890713: ftp.debian.org: please allow mipsel uploads with 
mips64el GPG keys
has caused the Debian Bug report #890713,
regarding ftp.debian.org: please allow mipsel uploads with mips64el GPG keys
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.)


-- 
890713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: wishlist

It is currently not possible to sign a mipsel upload with the mips64el
GPG key. Could you please allow that, similarly to what is already done
with armel/armhf, or amd64/i386? That would allow us to use only one GPG
key per buildd, simplifying the maintenance a lot.
--- End Message ---
--- Begin Message ---
On 2018-02-17 22:32, Aurelien Jarno wrote:
> Package: ftp.debian.org
> Severity: wishlist
> 
> It is currently not possible to sign a mipsel upload with the mips64el
> GPG key. Could you please allow that, similarly to what is already done
> with armel/armhf, or amd64/i386? That would allow us to use only one GPG
> key per buildd, simplifying the maintenance a lot.

This has now been done. Closing the bug.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---

Bug#895103: marked as done (why3 server broken on multiple architectures)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 18:23:27 +
with message-id 
and subject line Bug#895103: fixed in why3 0.88.3-2
has caused the Debian Bug report #895103,
regarding why3 server broken on multiple architectures
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.)


-- 
895103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: why3
Version: 0.88.3-1
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch autopkgtest

Dear Ralf,

The 0.88.3 version of why3 has been blocked for a while from being included
in the upcoming Ubuntu 18.04 release due to failing autopkgtests on multiple
architectures, e.g.:

autopkgtest [08:58:21]: test why3+alt-ergo: [---
client_connect: connection failed: Connection refused (connect,) 
(socket_name=/tmp/why3server3f8c61sock)
autopkgtest [08:58:57]: test why3+alt-ergo: ---]
why3+alt-ergoFAIL non-zero exit status 1

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/w/why3/20180405_094212_aa650@/log.gz

I finally had a chance to track this down, and it turns out why3 0.88.3 is
completely broken upstream on various architectures (arm64, armhf, ppc64el,
and s390x, at least) due to wrong handling of return values from
getopt_long() that prevents why3-server from ever starting.

This issue was not seen in Debian's automated test runs because Debian only
runs autopkgtests for amd64: https://ci.debian.net/packages/w/why3/ but in
any case this would not have prevented the why3 package from being broken in
Debian testing because Debian unfortunately does not gate testing on
autopkgtest failures.

The attached patch fixes the trivial portability issue in why3, and as seen
at http://autopkgtest.ubuntu.com/packages/w/why3 the tests are now passing
for 0.88.3 on all architectures where they previously passed.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru why3-0.88.3/debian/patches/portable-getopt.patch 
why3-0.88.3/debian/patches/portable-getopt.patch
--- why3-0.88.3/debian/patches/portable-getopt.patch1969-12-31 
16:00:00.0 -0800
+++ why3-0.88.3/debian/patches/portable-getopt.patch2018-04-06 
17:22:54.0 -0700
@@ -0,0 +1,19 @@
+Description: fix unportable assumptions in getopt_long() handling
+ Don't store an int in a char and expect comparison to -1 to work across
+ architectures.
+Author: Steve Langasek 
+Last-Modified: 2018-04-06
+
+Index: why3-0.88.3/src/server/options.c
+===
+--- why3-0.88.3.orig/src/server/options.c
 why3-0.88.3/src/server/options.c
+@@ -30,7 +30,7 @@ void parse_options(int argc, char **argv
+   };
+   while (1) {
+  int option_index = 0;
+- char c = 0;
++ int c = 0;
+  c = getopt_long (argc, argv, "j:s:",
+   long_options, _index);
+  /* Detect the end of the options. */
diff -Nru why3-0.88.3/debian/patches/series why3-0.88.3/debian/patches/series
--- why3-0.88.3/debian/patches/series   2018-01-14 14:46:38.0 -0800
+++ why3-0.88.3/debian/patches/series   2018-04-06 17:20:54.0 -0700
@@ -0,0 +1 @@
+portable-getopt.patch
--- End Message ---
--- Begin Message ---
Source: why3
Source-Version: 0.88.3-2

We believe that the bug you reported is fixed in the latest version of
why3, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated why3 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, 07 Apr 2018 11:54:01 

Bug#895164: marked as done (linux: Power management support for GPD Pocket UMPC systems)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:00:11 +
with message-id 
and subject line Bug#895164: fixed in linux 4.16-1~exp1
has caused the Debian Bug report #895164,
regarding linux: Power management support for GPD Pocket UMPC systems
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.)


-- 
895164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 4.16~rc5-1~exp2
Severity: wishlist

Power management for GPD Pocket UMPC systems requires kernel driver
modules built by setting CONFIG_PWM_LPSS_PLATFORM,
CONFIG_INTEL_INT0002_VGPIO, CONFIG_INTEL_CHT_INT33FE,
CONFIG_TYPEC_FUSB302, CONFIG_BATTERY_MAX17042 and
CONFIG_CHARGER_BQ24190 along with a variety of related dependencies.
These are all supported in current mainline 4.16 release candidates,
they just need to be enabled.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.16-1~exp1

We believe that the bug you reported is fixed in the latest version of
linux, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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, 08 Apr 2018 14:44:18 +0200
Source: linux
Binary: linux-source-4.16 linux-support-4.16.0-trunk linux-doc-4.16 
linux-kbuild-4.16 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.16 
usbip hyperv-daemons lockdep liblockdep4.16 liblockdep-dev 
linux-headers-4.16.0-trunk-common linux-libc-dev linux-headers-4.16.0-trunk-all 
linux-headers-4.16.0-trunk-all-alpha kernel-image-4.16.0-trunk-alpha-generic-di 
nic-modules-4.16.0-trunk-alpha-generic-di 
nic-wireless-modules-4.16.0-trunk-alpha-generic-di 
nic-shared-modules-4.16.0-trunk-alpha-generic-di 
serial-modules-4.16.0-trunk-alpha-generic-di 
usb-serial-modules-4.16.0-trunk-alpha-generic-di 
ppp-modules-4.16.0-trunk-alpha-generic-di 
pata-modules-4.16.0-trunk-alpha-generic-di 
cdrom-core-modules-4.16.0-trunk-alpha-generic-di 
scsi-core-modules-4.16.0-trunk-alpha-generic-di 
scsi-modules-4.16.0-trunk-alpha-generic-di 
loop-modules-4.16.0-trunk-alpha-generic-di 
btrfs-modules-4.16.0-trunk-alpha-generic-di 
ext4-modules-4.16.0-trunk-alpha-generic-di
 isofs-modules-4.16.0-trunk-alpha-generic-di 
jfs-modules-4.16.0-trunk-alpha-generic-di 
xfs-modules-4.16.0-trunk-alpha-generic-di 
fat-modules-4.16.0-trunk-alpha-generic-di 
md-modules-4.16.0-trunk-alpha-generic-di 
multipath-modules-4.16.0-trunk-alpha-generic-di 
usb-modules-4.16.0-trunk-alpha-generic-di 
usb-storage-modules-4.16.0-trunk-alpha-generic-di 
input-modules-4.16.0-trunk-alpha-generic-di 
event-modules-4.16.0-trunk-alpha-generic-di 
mouse-modules-4.16.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.16.0-trunk-alpha-generic-di 
pcmcia-modules-4.16.0-trunk-alpha-generic-di 
nic-usb-modules-4.16.0-trunk-alpha-generic-di 
sata-modules-4.16.0-trunk-alpha-generic-di 
i2c-modules-4.16.0-trunk-alpha-generic-di 
crc-modules-4.16.0-trunk-alpha-generic-di 
crypto-modules-4.16.0-trunk-alpha-generic-di 
crypto-dm-modules-4.16.0-trunk-alpha-generic-di 
ata-modules-4.16.0-trunk-alpha-generic-di 
nbd-modules-4.16.0-trunk-alpha-generic-di 
squashfs-modules-4.16.0-trunk-alpha-generic-di
 virtio-modules-4.16.0-trunk-alpha-generic-di 
zlib-modules-4.16.0-trunk-alpha-generic-di 
fuse-modules-4.16.0-trunk-alpha-generic-di 
srm-modules-4.16.0-trunk-alpha-generic-di 
linux-image-4.16.0-trunk-alpha-generic linux-headers-4.16.0-trunk-alpha-generic 
linux-image-4.16.0-trunk-alpha-generic-dbg linux-image-4.16.0-trunk-alpha-smp 
linux-headers-4.16.0-trunk-alpha-smp linux-image-4.16.0-trunk-alpha-smp-dbg 
linux-headers-4.16.0-trunk-all-amd64 kernel-image-4.16.0-trunk-amd64-di 
nic-modules-4.16.0-trunk-amd64-di nic-wireless-modules-4.16.0-trunk-amd64-di 
nic-shared-modules-4.16.0-trunk-amd64-di serial-modules-4.16.0-trunk-amd64-di 
usb-serial-modules-4.16.0-trunk-amd64-di ppp-modules-4.16.0-trunk-amd64-di 
pata-modules-4.16.0-trunk-amd64-di 

Bug#876774: marked as done (linux-image-4.9.0-3-armmp: please enable missing configuration options for dove cubox)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:00:11 +
with message-id 
and subject line Bug#876774: fixed in linux 4.16-1~exp1
has caused the Debian Bug report #876774,
regarding linux-image-4.9.0-3-armmp: please enable missing configuration 
options for dove cubox
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.)


-- 
876774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.30-2+deb9u5
Severity: wishlist
Tags: patch

Dear Maintainer,

Please enable the required config options for supporting the SolidRun CuBox 
(Dove).
This machine is extremely well supported in Mainline and it would be great if 
it could become a first-class citizen of Debian.

Note that not only the 4.9.0-armmp is affected, but also any later kernel 
package at this point.
I'd be happy to test any version after enabling the missing options!
But getting it into stretch would be supreme.

I have collected these missing options:
CONFIG_MACH_DOVE=y
CONFIG_CACHE_TAUROS2=y
CONFIG_CPU_PJ4=y
CONFIG_DOVE_CLK=y
CONFIG_DOVE_THERMAL=n
CONFIG_MMC_SDHCI_DOVE=n
CONFIG_ORION_IRQCHIP=y
CONFIG_ORION_TIMER=y
CONFIG_PHY_MVEBU_SATA=y
CONFIG_PINCTRL_DOVE=y

CONFIG_COMMON_CLK_SI5351=m
CONFIG_I2C_MUX_PINCTRL=m
CONFIG_MMC_SDHCI_DOVE=m
CONFIG_MV643XX_ETH=m
CONFIG_PHY_MVEBU_SATA=m
CONFIG_SND_KIRKWOOD_SOC=m
CONFIG_DOVE_THERMAL=m

# This one is not needed, it is present on the SoC, but not exposed by the Cubox
CONFIG_DRM_ARMADA=m

I have built mainline 4.9.45 from the armmp .config, and above options to 
verify that it actually does work!

Yours sincerely
Josua Mayer


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Hardware: Marvell Dove
Revision: 
Device Tree model: SolidRun CuBox

** PCI devices:

** USB devices:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.9.45-dove-cubox (SMP w/1 CPU core)
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-image-4.9.0-3-armmp depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-3-armmp recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.9.0-3-armmp suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-3-armmp is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.16-1~exp1

We believe that the bug you reported is fixed in the latest version of
linux, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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, 08 Apr 2018 14:44:18 +0200
Source: linux
Binary: linux-source-4.16 

Bug#890235: marked as done (Please enable DRM_DP_AUX_CHARDEV)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:00:11 +
with message-id 
and subject line Bug#890235: fixed in linux 4.16-1~exp1
has caused the Debian Bug report #890235,
regarding Please enable DRM_DP_AUX_CHARDEV
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.)


-- 
890235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal

Hey,

The DRM_DP_AUX_CHARDEV exposes the DP aux channel to userspace, this is used by
e.g. fwupmgr to allow it to upgrade firmware of Dell Type-C Docking stations.
Please enable this option :)

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

Kernel: Linux 4.15.0-rc8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.16-1~exp1

We believe that the bug you reported is fixed in the latest version of
linux, 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 890...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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, 08 Apr 2018 14:44:18 +0200
Source: linux
Binary: linux-source-4.16 linux-support-4.16.0-trunk linux-doc-4.16 
linux-kbuild-4.16 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.16 
usbip hyperv-daemons lockdep liblockdep4.16 liblockdep-dev 
linux-headers-4.16.0-trunk-common linux-libc-dev linux-headers-4.16.0-trunk-all 
linux-headers-4.16.0-trunk-all-alpha kernel-image-4.16.0-trunk-alpha-generic-di 
nic-modules-4.16.0-trunk-alpha-generic-di 
nic-wireless-modules-4.16.0-trunk-alpha-generic-di 
nic-shared-modules-4.16.0-trunk-alpha-generic-di 
serial-modules-4.16.0-trunk-alpha-generic-di 
usb-serial-modules-4.16.0-trunk-alpha-generic-di 
ppp-modules-4.16.0-trunk-alpha-generic-di 
pata-modules-4.16.0-trunk-alpha-generic-di 
cdrom-core-modules-4.16.0-trunk-alpha-generic-di 
scsi-core-modules-4.16.0-trunk-alpha-generic-di 
scsi-modules-4.16.0-trunk-alpha-generic-di 
loop-modules-4.16.0-trunk-alpha-generic-di 
btrfs-modules-4.16.0-trunk-alpha-generic-di 
ext4-modules-4.16.0-trunk-alpha-generic-di
 isofs-modules-4.16.0-trunk-alpha-generic-di 
jfs-modules-4.16.0-trunk-alpha-generic-di 
xfs-modules-4.16.0-trunk-alpha-generic-di 
fat-modules-4.16.0-trunk-alpha-generic-di 
md-modules-4.16.0-trunk-alpha-generic-di 
multipath-modules-4.16.0-trunk-alpha-generic-di 
usb-modules-4.16.0-trunk-alpha-generic-di 
usb-storage-modules-4.16.0-trunk-alpha-generic-di 
input-modules-4.16.0-trunk-alpha-generic-di 
event-modules-4.16.0-trunk-alpha-generic-di 
mouse-modules-4.16.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.16.0-trunk-alpha-generic-di 
pcmcia-modules-4.16.0-trunk-alpha-generic-di 
nic-usb-modules-4.16.0-trunk-alpha-generic-di 
sata-modules-4.16.0-trunk-alpha-generic-di 
i2c-modules-4.16.0-trunk-alpha-generic-di 
crc-modules-4.16.0-trunk-alpha-generic-di 
crypto-modules-4.16.0-trunk-alpha-generic-di 
crypto-dm-modules-4.16.0-trunk-alpha-generic-di 
ata-modules-4.16.0-trunk-alpha-generic-di 
nbd-modules-4.16.0-trunk-alpha-generic-di 
squashfs-modules-4.16.0-trunk-alpha-generic-di
 virtio-modules-4.16.0-trunk-alpha-generic-di 
zlib-modules-4.16.0-trunk-alpha-generic-di 
fuse-modules-4.16.0-trunk-alpha-generic-di 
srm-modules-4.16.0-trunk-alpha-generic-di 
linux-image-4.16.0-trunk-alpha-generic linux-headers-4.16.0-trunk-alpha-generic 
linux-image-4.16.0-trunk-alpha-generic-dbg linux-image-4.16.0-trunk-alpha-smp 
linux-headers-4.16.0-trunk-alpha-smp linux-image-4.16.0-trunk-alpha-smp-dbg 
linux-headers-4.16.0-trunk-all-amd64 kernel-image-4.16.0-trunk-amd64-di 
nic-modules-4.16.0-trunk-amd64-di nic-wireless-modules-4.16.0-trunk-amd64-di 

Bug#894769: marked as done (arduino: serial communication/uploader not working)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:27:13 +0200
with message-id <20180408202713.gb30...@gpm.stappers.nl>
and subject line closing the oldest of the duplicates
has caused the Debian Bug report #894769,
regarding arduino: serial communication/uploader not working
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.)


-- 
894769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arduino
Version: 2:1.0.5+dfsg2-4.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

normal use of arduino program
however at the moment the serial connection selection is greyed out

connect to arduino via serial port not working, cannot upload code to arduino

get the following error
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

this is the same on two different machines running buster
where serial upload was previously working without a problem

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

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

Versions of packages arduino depends on:
ii  arduino-core   2:1.0.5+dfsg2-4.1
ii  default-jre [java6-runtime]2:1.9-62
ii  libjna-java4.5.1-1
ii  librxtx-java   2.2pre2+dfsg1-1
ii  openjdk-8-jre [java6-runtime]  8u162-b12-1
ii  openjdk-9-jre [java6-runtime]  9.0.4+12-3

Versions of packages arduino recommends:
ii  extra-xdg-menus  1.0-4
ii  policykit-1  0.105-20

arduino suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Apr 08, 2018 at 08:18:03PM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > unmerge 894769
> Bug #894769 [arduino] arduino: serial communication/uploader not working
> Bug #894770 [arduino] arduino: serial communication/uploader not working
> Disconnected #894769 from all other report(s).
> > stop
> Stopping processing here.
> 
> 894769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769

Closing that one


> 894770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770

Using that one for further discussion.



Groeten
Geert Stappers
-- 
Leven en laten leven--- End Message ---

Bug#895244: marked as done (ocrmypdf seems to have a flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 14:33:33 -0700
with message-id <871sfp1iz6@iris.silentflame.com>
and subject line Re: Bug#895244: ocrmypdf seems to have a flaky autopkgtest
has caused the Debian Bug report #895244,
regarding ocrmypdf seems to have a flaky autopkgtest
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.)


-- 
895244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocrmypdf
Version: 5.5-2
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: flaky

Hi Sean,

While inspecting regressions in autopkgtest results¹², I noticed that
your package ocrmypdf fails regularly, without obvious changes. At times
when these tests fail, they also take considerably longer, i.e. more
than 1 hour instead of around 15 minutes.

While it maybe so that your latest version fixes the issue, I didn't
spot anything in the changelog to warrant that, so I am filing this bug
to prevent us from forgetting it. If you believe the issue is fixed,
please don't hesitate to close this bug immediately.

Paul

¹ https://ci.debian.net/packages/o/ocrmypdf/unstable/amd64/
² https://ci.debian.net/packages/o/ocrmypdf/testing/amd64/



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 6.1.2-1

On Sun, Apr 08 2018, Paul Gevers wrote:

> While inspecting regressions in autopkgtest results¹², I noticed that
> your package ocrmypdf fails regularly, without obvious changes. At
> times when these tests fail, they also take considerably longer,
> i.e. more than 1 hour instead of around 15 minutes.
>
> While it maybe so that your latest version fixes the issue, I didn't
> spot anything in the changelog to warrant that, so I am filing this
> bug to prevent us from forgetting it. If you believe the issue is
> fixed, please don't hesitate to close this bug immediately.

Upstream believes this to be fixed in the latest release.

See: https://bugs.debian.org/888917#58

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#873086: marked as done (ifupdown script disables IPv6 on parent of VLAN interface)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 02:55:08 +
with message-id 
and subject line Bug#873086: fixed in bridge-utils 1.5-16
has caused the Debian Bug report #873086,
regarding ifupdown script disables IPv6 on parent of VLAN interface
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.)


-- 
873086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.5-14

Well, what the subject says, this just killed my IPv6 connectivity on a
machine that's untagged on the same interface on which a VLAN is supposed
to be attached to a bridge. I guess at the very least, bride-utils should
avoid touching the configuration of interfaces that are managed by
ifupdown and that aren't even supposed to be attached to a bridge?
--- End Message ---
--- Begin Message ---
Source: bridge-utils
Source-Version: 1.5-16

We believe that the bug you reported is fixed in the latest version of
bridge-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 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Garcia Mantinan  (supplier of updated bridge-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: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 23:06:30 +0200
Source: bridge-utils
Binary: bridge-utils
Architecture: source amd64
Version: 1.5-16
Distribution: unstable
Urgency: medium
Maintainer: Santiago Garcia Mantinan 
Changed-By: Santiago Garcia Mantinan 
Description:
 bridge-utils - Utilities for configuring the Linux Ethernet bridge
Closes: 873086
Changes:
 bridge-utils (1.5-16) unstable; urgency=medium
 .
   * Don't set dev globally at bridge-utils.sh. Closes: #873086.
Checksums-Sha1:
 0299724f5ba93d55de72e4036c393aefff2d42e6 1718 bridge-utils_1.5-16.dsc
 a68b85285800d2fdf96e8634d944c0fbaffb0a90 17039 bridge-utils_1.5-16.diff.gz
 63e1e6a74c61ddb633433c77f3b7754f8fa0ea62 36012 
bridge-utils-dbgsym_1.5-16_amd64.deb
 9e8ae1344a103fe1b1b3063f1a3f9e7421105c9b 5981 
bridge-utils_1.5-16_amd64.buildinfo
 0d78b32a97af44549bc862fcf8d124e5ee579c9a 34236 bridge-utils_1.5-16_amd64.deb
Checksums-Sha256:
 48b481b3deb4e71dbbc62aa4ccd8f426512b88f39ca6bfa12b2a42f1c66e16cd 1718 
bridge-utils_1.5-16.dsc
 e841aae4c7feccc4fb719a0a93397c3182dba5e9d20b4a2eae7c3b80dbd0cdf5 17039 
bridge-utils_1.5-16.diff.gz
 336d8a6ff2a285582d111c87b28cdeb96c34325187409e7dd6ea34956acc7ac2 36012 
bridge-utils-dbgsym_1.5-16_amd64.deb
 fcef9e28c352d4ee040e587cb2233a43f7f25e7462d60f8c7d509695ca41695e 5981 
bridge-utils_1.5-16_amd64.buildinfo
 a6d57a9b057e50ec7fa186f6b58562b92e8b85618d87743902446cbda57ee974 34236 
bridge-utils_1.5-16_amd64.deb
Files:
 50c163bbb4bec2a4472c8ec3076b180e 1718 net optional bridge-utils_1.5-16.dsc
 57c8c7e04a984d743d1972a02c8e869b 17039 net optional bridge-utils_1.5-16.diff.gz
 d8dd6a91ada6597cc788df64452c792a 36012 debug optional 
bridge-utils-dbgsym_1.5-16_amd64.deb
 7d0628b171f717bed8b18e49f3c82b74 5981 net optional 
bridge-utils_1.5-16_amd64.buildinfo
 7cc08bba4f4f3badc298e9ea337ba74b 34236 net optional 
bridge-utils_1.5-16_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEBqPldg9hG0uxqQ5ouGiMo9h21aMFAlrKj7MACgkQuGiMo9h2
1aNDkhAAjlIrWJoDsxJ9EqgacQHMKZV+nYu4fOWTlJgi9794QGstZYGlcrxbVDCS
OB2z3N7vY5XKgID5fa2w7zu939CxXuxSjsG0p8ELm5LShhqN57/qJ3bI3qwJ0OZm
G6kvKad9fm+mJsY5xDCbtTZ0IFuV21ZFX8dGW4fkG1KDiKPG8yOfuBIRfkh+hRCH
+vS7Pj/qIpLjJaVicod6wBiY7s0OoVwuNzLmUllPndBf5ZCP7+mewukBzBTRDPKn
b37P4/TVZbtTxYq2qhXy+j3tF2Trw2640HKNDHltcJPS/ujeIV/VAHntWajIck/Q
B5zCYkGVNGSuIjZgZwCSbtP+4mOnKxE/zAkDjYKqNVaEcl1SsORN46wgr+7D/vrB
8vFKXHYvhuH2Z9XzlCX3ZktZ8RvMlXkuvJjfe35zG8Z3w/mmAn9za6zMB9QvhgJd
m5AY6ArYh5ZRTNPmJuJEWi0iur/1FpOAxJYAWKmIKVtt8JEMT7OEmRtg51FVqLoX
XazllrMmUdb7tYRFjoLEYKeUqZtmSo77MdT75pzU6c2Z2noGEB+rHUdrgYJLA9Oq
UqjpVLZB9c+BgEmq8RfF4i2ZYNGPfSo6iISm/XP8Ai+f3BV0IGx2pALl1wC3lKGf
CKktqiZFWzUVRiqNcFqidZQKSiy5lnUw3V7LO9/o2r6OfAfEmnU=
=0Cad
-END PGP SIGNATURE End Message ---

Bug#895236: marked as done (maven-javadoc-plugin checks SystemUtils.IS_JAVA_1_9, but not for 10 and 11)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 03:03:39 +
with message-id 
and subject line Bug#895236: fixed in maven-javadoc-plugin 3.0.0-4
has caused the Debian Bug report #895236,
regarding maven-javadoc-plugin checks SystemUtils.IS_JAVA_1_9, but not for 10 
and 11
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.)


-- 
895236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:maven-javadoc-plugin
Version: 3.0.0-3
Severity: important
Tags: sid buster

maven-javadoc-plugin only checks SystemUtils.IS_JAVA_1_9 and fails with 10 and
11.  It should check for 10 and 11 as well.

This needs an update for libcommons-lang3-java first.
--- End Message ---
--- Begin Message ---
Source: maven-javadoc-plugin
Source-Version: 3.0.0-4

We believe that the bug you reported is fixed in the latest version of
maven-javadoc-plugin, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated maven-javadoc-plugin 
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, 08 Apr 2018 23:17:47 +0200
Source: maven-javadoc-plugin
Binary: libmaven-javadoc-plugin-java
Architecture: source
Version: 3.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libmaven-javadoc-plugin-java - Maven Javadoc Plugin
Closes: 895236
Changes:
 maven-javadoc-plugin (3.0.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Modified the patches to work with Java 9 or later (Closes: #895236)
   * Standards-Version updated to 4.1.4
Checksums-Sha1:
 313d12af74059ce1a681e748dd192a4d0e65ce73 2655 maven-javadoc-plugin_3.0.0-4.dsc
 a3395cd95b86db8e11d6886015e42457b30b0e7b 7796 
maven-javadoc-plugin_3.0.0-4.debian.tar.xz
 a2b2f523f3b0c38a211e7505125d253796702ce7 15884 
maven-javadoc-plugin_3.0.0-4_source.buildinfo
Checksums-Sha256:
 989551baeb37d160104e89979b09354542e1dfc244a160467d8d67e13133854a 2655 
maven-javadoc-plugin_3.0.0-4.dsc
 37a17bfe46c9535e044aefed7c463e7fa91f04618eb03793b39330fe1722866c 7796 
maven-javadoc-plugin_3.0.0-4.debian.tar.xz
 e5c8709c05e2c553c9a5b8dc61985af1631467dc6639655e098b61c8ff86b149 15884 
maven-javadoc-plugin_3.0.0-4_source.buildinfo
Files:
 6c27c4bac733984bbe2c19463ba8412a 2655 java optional 
maven-javadoc-plugin_3.0.0-4.dsc
 8de22d1ca0fdcd7ce09821337083e605 7796 java optional 
maven-javadoc-plugin_3.0.0-4.debian.tar.xz
 43a15a98d52cbb20d38a06d46f8c2e91 15884 java optional 
maven-javadoc-plugin_3.0.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlrKiAgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsKxEP/03LTWtR0bHe4ijmgPI+ij94OQzGX19z
+Zg+DyOrVN2LE75lKa+vPMRmqo81PTIgsoN9Dq02QR+rH0ATqmOMXdAK82OmnUbJ
DhXQxakr8T5OYp9IQRmeCNcoo9PWEdZXS+B8I1SnrV0rwX73dsUdKcwAvg7DB1mT
oR0LlVBDO4l0SOpBIovsY8Vux/9ouG+IPZB7x53lIENLV3VC7qzMZe/DQPeyYEUZ
HENtMbcB3jmi7/cuQwSi7eKjPPNuNi7D/5FYD/eQeI+Q+YJKb35qhRecsOOfDjZQ
4EyTOnp8+37446WP6H33AwPaddyqB4sMPhQ5WQioL+wWMfR3RdoH2H/H3VwxhibS
Cpy+GlFMAAj3OIVVHNFckUHD0hBPztJdKK5bTQ5hPW5SJXFQTMn2co+n75vgbUNr
h88LZricYy88xP2UFVbnaCyQxY4pP656Lwxm3Pd0w2pc4SXKs9unCmsauHl8TpbL
lKjK8rBejyWUYdrufrPAhto/JJm+4TquTlibMCDHtq8vQ4v+8N1cuvrtBSWz//Md
h80MNrWCl38cK5Q7tgDoAZhUMl67IUoa6cKwjTcLCc32DBUmZ6osIAlT3ReDsj5I
8Vt/cqT7FmWCKQs3tRSj+WDMmgoNJHW26OSZ2mLRiyyeC5tCXrqp5kmYxQpNZiZz
TM5I3cdkUHup
=nbK2
-END PGP SIGNATURE End Message ---

Bug#895153: marked as done (zsh-common: /usr/local/share/zsh/site-functions is owned by root:staff)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 03:10:00 +
with message-id 
and subject line Bug#895153: fixed in zsh 5.5-1
has caused the Debian Bug report #895153,
regarding zsh-common: /usr/local/share/zsh/site-functions is owned by root:staff
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.)


-- 
895153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zsh-common
Version: 5.4.2-4
Severity: normal

Your package declares compliance with Debian Policy 4.1.4, claiming that
"no other changes were required", but this is not actually true.
The upgrading-checklist states

,
| 9.1.2
|If "/etc/staff-group-for-usr-local" does not exist, "/usr/local"
|and all subdirectories created by packages should have permissions
|0755 and be owned by "root:root".  If the file exists, the old
|permissions of 2775 and ownership of root:staff should remain.
`

The zsh-common postinst script does not respect this policy though,
using root:staff unconditionally.

,
| mkdir -m2775 -p /usr/local/share/zsh/site-functions && chown root:staff \
|/usr/local/share/zsh/site-functions || true
`

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

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


zsh-common depends on no packages.

Versions of packages zsh-common recommends:
ii  zsh  5.4.2-4

Versions of packages zsh-common suggests:
ii  zsh-doc  5.4.2-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: zsh
Source-Version: 5.5-1

We believe that the bug you reported is fixed in the latest version of
zsh, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated zsh 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: Mon, 09 Apr 2018 01:17:56 +0200
Source: zsh
Binary: zsh-common zsh zsh-doc zsh-static zsh-dev
Architecture: source all amd64
Version: 5.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Zsh Maintainers 
Changed-By: Axel Beckert 
Description:
 zsh- shell with lots of features
 zsh-common - architecture independent files for Zsh
 zsh-dev- shell with lots of features (development files)
 zsh-doc- zsh documentation - info/HTML format
 zsh-static - shell with lots of features (static link)
Closes: 895153 895225
Changes:
 zsh (5.5-1) unstable; urgency=medium
 .
   [ Axel Beckert ]
   * [fe36c1ad] Import new upstream release.
 + [31f72205] CVE-2018-1100: check bounds on buffer in mail
   checking. (Closes: #895225)
 .
   [ Sven Joachim ]
   * [1521c7d0] Handle /usr/local/share/zsh with dh_usrlocal.
 (Closes: #895153)
Checksums-Sha1:
 f2ed83f519aae5537197a46cc8536732b1adc735 2461 zsh_5.5-1.dsc
 1f7ae7488530d1e65483d43af8dc887b8a63fbc7 2682068 zsh_5.5.orig.tar.xz
 fd7f681691a63b88396c0846b5f304e401972f15 76180 zsh_5.5-1.debian.tar.xz
 428a2913c4f6238d6b19ece09953d3b127f2e378 3597636 zsh-common_5.5-1_all.deb
 9841df26bae9d927c77097dfe8153aaa8165d3a4 2164840 zsh-dbgsym_5.5-1_amd64.deb
 ab9837f30d6a1b86bcbea3003ddf9b51c79d64c0 254044 zsh-dev_5.5-1_amd64.deb
 8ba1a49dbd01d425e90f85026ea0fbcdd3d9d2ef 2675160 zsh-doc_5.5-1_all.deb
 74ee0cb9ce1a8a71a80b4d415313b9b38eec74fd 1573316 
zsh-static-dbgsym_5.5-1_amd64.deb
 2aa638d84bc164994a8c6214a3ccdfeefbeb5eee 1102900 zsh-static_5.5-1_amd64.deb
 cabcd4e4b1d4ff4c5ff2faba7fa1d4c14f415ea6 9710 zsh_5.5-1_amd64.buildinfo
 893394bdfb02da17989672073ee9fcf1b8721326 859164 zsh_5.5-1_amd64.deb
Checksums-Sha256:
 b2a279ed6a46a156e9c129e30aab8110607ef584a530f4c0a527ca0ed7e6978f 2461 
zsh_5.5-1.dsc
 

Bug#895225: marked as done (zsh: CVE-2018-1100: check bounds on buffer in mail checking)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 03:10:01 +
with message-id 
and subject line Bug#895225: fixed in zsh 5.5-1
has caused the Debian Bug report #895225,
regarding zsh: CVE-2018-1100: check bounds on buffer in mail checking
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.)


-- 
895225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zsh
Version: 3.1.7-1
Severity: normal
Tags: security fixed-upstream patch
Control: forwarded -1 
https://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=42607

Hi,

there happened another security fix at zsh upstream:
https://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=42607
https://sourceforge.net/p/zsh/code/ci/31f72205630687c1cef89347863aab355296a27f/

git.code.sf.net is currently unreachable for me (ping
timeout), but the mirror at GitHub already has it, too:
https://github.com/zsh-users/zsh/commit/31f72205630687c1cef89347863aab355296a27f

That way I could attach the upstream patch to this mail:

commit 31f72205630687c1cef89347863aab355296a27f
Author: Oliver Kiddle 
Date:   Sat Apr 7 18:28:38 2018 +0200

42607, CVE-2018-1100: check bounds on buffer in mail checking

diff --git a/ChangeLog b/ChangeLog
index 60ec155d7..2cc699b67 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2018-04-07  Oliver Kiddle  
 
+	* 42607, CVE-2018-1100: Src/utils.c: check bounds on buffer
+	in mail checking
+
 	* 42600: Src/Zle/computil.c: error paths for _values leaked
 	the exclusion list array
 
diff --git a/Src/utils.c b/Src/utils.c
index c544b81bf..180693d67 100644
--- a/Src/utils.c
+++ b/Src/utils.c
@@ -1653,7 +1653,7 @@ checkmailpath(char **s)
 	LinkList l;
 	DIR *lock = opendir(unmeta(*s));
 	char buf[PATH_MAX * 2 + 1], **arr, **ap;
-	int ct = 1;
+	int buflen, ct = 1;
 
 	if (lock) {
 		char *fn;
@@ -1662,9 +1662,11 @@ checkmailpath(char **s)
 		l = newlinklist();
 		while ((fn = zreaddir(lock, 1)) && !errflag) {
 		if (u)
-			sprintf(buf, "%s/%s?%s", *s, fn, u);
+			buflen = snprintf(buf, sizeof(buf), "%s/%s?%s", *s, fn, u);
 		else
-			sprintf(buf, "%s/%s", *s, fn);
+			buflen = snprintf(buf, sizeof(buf), "%s/%s", *s, fn);
+		if (buflen < 0 || buflen >= (int)sizeof(buf))
+			continue;
 		addlinknode(l, dupstring(buf));
 		ct++;
 		}

This will likely be part of the upcoming 5.5 release, maybe also of an
potential further release candidate. JFTR: It is not fixed in zsh
5.4.2-test-2-1 which I uploaded yesterday to experimental as the
upstream git tag for that release candidate is from Thursday while the
commit mentioned above is from Saturday.

According to "git blame", this code has been touched last time between
the 3.1.6 and 3.17 releases (i.e. in April 2000), so declaring it as
introduced with 3.1.7 for now. The bug itself might affect even older
releases since the commit db663c824a (which last touched these lines)
seems to be primarily change code indentation. But for Debian it does
not really matter how early it has been introduced, so I stop digging
here.

-- Package-specific info:
Packages which depend, recommend, suggest or enhance a zsh package and hence 
may provide code meant to be sourced in .zshrc:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   Description
+++-===-==-==-===
ii  abe-commandline 17.5   allMetapackage of 
commandline tools Axel usual
ii  abe-desktop-common  13.1.1 allCommon packages for all 
of Axel's desktop s
ii  autojump22.5.0-2   allshell extension to jump 
to frequently used 
ii  fizsh   1.0.9-1allFriendly Interactive 
ZSHell
ii  flowscan1.006-13.2 allflow-based IP traffic 
analysis and visualiz
ii  powerline   2.6-1  amd64  prompt and statusline 
utility
ii  shellex 0.2-1  amd64  shell-based launcher
ii  tomb2.5+dfsg1-1allcrypto undertaker
ii  zomg0.8-3  amd64  console-based libre.fm 
submission and radio
ii  zplug   2.4.2-1allnext-generation plugin 
manager for zsh
ii  zsh-antigen 2.2.3-1

Bug#875653: marked as done (golang-github-aws-aws-sdk-go: New upstream release (>=1.8.4))

[Debian Bug Tracking System]

Your message dated Mon, 9 Apr 2018 10:48:35 +1000
with message-id <8058c380-1c47-bce5-6170-86aaaee99...@debian.org>
and subject line Done: golang-github-aws-aws-sdk-go: New upstream release 
(>=1.8.4)
has caused the Debian Bug report #875653,
regarding golang-github-aws-aws-sdk-go: New upstream release (>=1.8.4)
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.)


-- 
875653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-aws-aws-sdk-go
Severity: wishlist

Dear Maintainer,

We still have a version gap between upstream, which is v1.10.43 at the
time of writing.

When build packer new version, I need at lease 1.7.0 version of
aws-sdk-go. The feature I needed is added in
https://github.com/aws/aws-sdk-go/pull/1088

Thanks
Shengjing Zhu


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: golang-github-aws-aws-sdk-go
Version: 1.12.79+dfsg-1

Uploaded.

Thanks, Shengjing Zhu.

Regards,
 Dmitry.--- End Message ---

Processed: Re: groovy: GCJ java.lang.ArrayIndexOutOfBoundsException

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + wontfix
Bug #877799 [groovy] groovy: GCJ java.lang.ArrayIndexOutOfBoundsException
Added tag(s) wontfix.
> close -1
Bug #877799 [groovy] groovy: GCJ java.lang.ArrayIndexOutOfBoundsException
Marked Bug as done

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

Bug#895188: marked as done (asciidoctor: E-mail addresses are rendered twice [manpage backend])

[Debian Bug Tracking System]

Your message dated Mon, 9 Apr 2018 01:11:46 +0200
with message-id <20180408231146.GM22805@debian>
and subject line Re: [DRE-maint] Bug#895188: asciidoctor: E-mail addresses are 
rendered twice [manpage backend]
has caused the Debian Bug report #895188,
regarding asciidoctor: E-mail addresses are rendered twice [manpage backend]
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.)


-- 
895188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asciidoctor
Version: 1.5.5-1
Severity: normal

Dear Maintainer,



ASCIIPATIENT(1)
===

NAME

asciipatient - E-mail addresses are rendered twice [manpage backend]


DESCRIPTION
---

Comparing the output of the *roff created by asciidoc and asciidoctor,
I found e-mail addresses are rendered twice for no appearent reason.


HOW TO REPEAT
-

Run this document through "asciidoctor --backend manpage", then execute
"MANWIDTH=80 man./asciipatient.1". Look at the way the address below is
rendered.


EXAMPLE
---

This bugreport was written for the Debian project by Christoph Biedl
 but may be used by others (although
there should be no need for this).


EXPECTED



This manpage was written for the Debian project by Christoph Biedl
 but may be used by others (although
there should be no need for this).



GOT
---


This manpage was written for the Debian project by Christoph Biedl
> but
may be used by others (although there should be no need for this).




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

Kernel: Linux 4.14.32 (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: unable to detect

Versions of packages asciidoctor depends on:
ii  ruby  1:2.5.1

asciidoctor recommends no packages.

asciidoctor suggests no packages.

-- no debconf information



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 18-04-08 20:03:35, Christoph Biedl wrote:
> Joseph Herlant wrote...
> 
> > To achieve your goal you would need to use the following:
> > mailto:debian.a...@manchmal.in-ulm.de[Christoph Biedl]
> (...)
> > Is that acceptable?
> 
> Certainly.
> 
> Christoph, should actually be able to read documentation on his
> own

...accordingly, marking as done.

Cheers,
Georg


signature.asc
Description: Digital signature
--- End Message ---

Bug#892494: marked as done (diceware: "diceware" name violates trademark)

[Debian Bug Tracking System]

Your message dated Mon, 9 Apr 2018 01:20:51 -0400
with message-id <20180409052051.l2fglguq6hr3k...@curie.anarc.at>
and subject line Re: Bug#892494: diceware: "diceware" name violates trademark
has caused the Debian Bug report #892494,
regarding diceware: "diceware" name violates trademark
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.)


-- 
892494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diceware
Severity: serious
Tags: upstream
Justification: Policy 2.1

As stated in the footer of http://world.std.com/%7Ereinhold/diceware.html the 
original creator of diceware claims a trademark on the name. I've filed a bug 
with upstream here: https://github.com/ulif/diceware/issues/48

Upstream does not have permission from Arnold Reinhold to use the trademark, 
but is aware of the issue and has reached out to Reinhold with no response. 
This package should probably be removed or renamed if upstream does not get a 
response soon.
--- End Message ---
--- Begin Message ---
Control: forwarded 892494 https://github.com/ulif/diceware/issues/48

On Fri, Mar 09, 2018 at 12:27:19PM -0500, Simon Fondrie-Teitler wrote:
> As stated in the footer of http://world.std.com/%7Ereinhold/diceware.html the 
> original creator of diceware claims a trademark on the name. I've filed a bug 
> with upstream here: https://github.com/ulif/diceware/issues/48
> 
> Upstream does not have permission from Arnold Reinhold to use the trademark, 
> but is aware of the issue and has reached out to Reinhold with no response. 
> This package should probably be removed or renamed if upstream does not get a 
> response soon.

On Thu, Mar 22, 2018 at 02:17:48PM +0100, Uli Fouquet wrote:
> this issue can be closed. I got a message from Mr. Reinhold granting me
> use of "diceware" explicitly, given that I keep the Python system as
> default source of randomness.

After reviewing the above issue, I agree this should be resolved, and
have (hopefully) done so in this message.

This should let the package trickle back down into testing from here on.

A.


signature.asc
Description: PGP signature
--- End Message ---