Bug#858920: neurodebian-desktop: Trigger cycle via interest(-await) on /usr/share/icons/gnome while depending (in)directly on gnome-icon-theme - please use interest-noawait

[Niels Thykier]

Yaroslav Halchenko:
> 
> [...]
> 
> so, smth like
> 
> diff --git a/debian/changelog b/debian/changelog
> index 6ecf20f..1952eca 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +neurodebian (0.37.6) unstable; urgency=medium
> +
> +  * Switch to use interest-noawait for neurodebian-desktop.trigger
> +to avoid a circular deadlock (Closes: #858920)
> +
> + -- Yaroslav Halchenko   Tue, 28 Mar 2017 13:53:19 
> -0400
> +
>  neurodebian (0.37.5) unstable; urgency=medium
>  
>* debian/control
> diff --git a/debian/neurodebian-desktop.triggers 
> b/debian/neurodebian-desktop.triggers
> index 44fdcbd..2adc7ee 100644
> --- a/debian/neurodebian-desktop.triggers
> +++ b/debian/neurodebian-desktop.triggers
> @@ -1 +1 @@
> -interest /usr/share/icons/gnome
> +interest-noawait /usr/share/icons/gnome
> 
> should resolve this issue, correct? ;)
> 

Basically, yes.

Thanks,
~Niels

Bug#858530: marked as done (linux: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Thu, 30 Mar 2017 04:20:26 +
with message-id 
and subject line Bug#858530: fixed in linux 4.9.18-1
has caused the Debian Bug report #858530,
regarding linux: FTBFS on ppc64el
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.)


-- 
858530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.9.16-1
Severity: serious
Justification: FTBFS on ppc64el

linux/4.9.16-1 FTBFS on ppc64el due to an unnoticed ABI change while
updating to the various 4.9. stable releases up from 4.9.13.

https://buildd.debian.org/status/fetch.php?pkg=linux&arch=ppc64el&ver=4.9.16-1&stamp=1490212252&raw=0

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.18-1

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 858...@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: Thu, 30 Mar 2017 02:16:33 +0100
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 
linux-image-4.9.0-2-alpha-smp-dbgsym linux-headers-4.9.0-2-all-amd64 
linux-image-4.9.0-2-amd64-unsigned linux-headers-4.9.0-2-amd64 
linux-image-4.9.0-2-amd64-dbgsym linux-image-4.9.0-2-rt-amd64-unsigned 
linux-headers-4.9.0-2-rt-amd64 linux-image-4.9.0-2-rt-amd64-dbgsym 
linux-headers-4.9.0-2-all-arm64 linux-image-4.9.0-2-arm64-unsigned 
linux-headers-4.9.0-2-arm64 linux-image-4.9.0-2-arm64-dbgsym 
linux-headers-4.9.0-2-all-armel kernel-image-4.9.0-2-marvell-di 
nic-modules-4.9.0-2-marvell-di nic-shared-modules-4.9.0-2-marvell-di 
usb-serial-modules-4.9.0-2-marvell-di ppp-modules-4.9.0-2-marvell-di 
cdrom-core-modules-4.9.0-2-marvell-di scsi-core-modules-4.9.0-2-marvell-di 
loop-modules-4.9.0-2-marvell-di ipv6-modules-4.9.0-2-marvell-di 
btrfs-modules-4.9.0-2-marvell-di ext4-modules-4.9.0-2-marvell-di 
isofs-modules-4.9.0-2-marvell-di
 jffs2-modules-4.9

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

[Potter, Tim]

On 30 Mar 2017, at 3:54 AM, Michael Stapelberg  wrote:
> 
> Hi Tim,
> 
> "Potter, Tim"  writes:
>> Hi Ricardo.  Thanks for the bug report.  I messed up by uploading some of 
>> the Docker 1.13
>> dependencies to unstable instead of experimental - my apologies.
>> 
>> I've done a new upload with a Breaks line to avoid this bug occurring until 
>> I finish testing
>> 1.13 and uploading to unstable.
> 
> I’m still running into this issue (or a very similar one?) with:
> 
> docker.io 1.13.0~ds1-2
> runc 0.1.1+dfsg1-2+b1
> containerd 0.2.3~git20161117.78.03e5862~ds1-2
> golang-libnetwork 0.8.0~dev.2+git20161130.568.fd27f22-4
> 
> I installed these packages from Debian unstable, but AFAICT, no newer
> version is available in experimental.
> 
> The symptom is:
> $ docker run -t -i debian:sid /bin/bash
> docker: Error response from daemon: containerd: container not started.
> 
> In the journal, I can’t see any errors from containerd itself.
> 
> Should docker be working in Debian at the moment? If not, is there a
> workaround?

Hi Michael.  I did an upload yesterday to unstable and things should be working 
again.
Sorry about the mess in experimental vs unstable.  I was trying to keep both 
the old
and new version working but failed miserably.

Please let me know if you find any more brokenness.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#858918: marked as done (dochelp: Introduces a trigger cycle via interest on /usr/share/doc-base - please migrate to interest-noawait)

[Debian Bug Tracking System]

Your message dated Thu, 30 Mar 2017 03:04:15 +
with message-id 
and subject line Bug#858918: fixed in dochelp 0.1.5
has caused the Debian Bug report #858918,
regarding dochelp: Introduces a trigger cycle via interest on 
/usr/share/doc-base - please migrate to interest-noawait
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.)


-- 
858918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dochelp
Version: 0.1.4
Severity: serious

Hi,

dochelp registers an "interest(-await)" trigger on /usr/share/doc-base.
At the same time, it depends on findutils and base-passwd, which provides
files in /usr/share/doc-base, triggering said interest trigger.

"""
The cycle is created because when findutils+base-passwd are put
into the triggers-awaited state (because it triggers dochelp), then it
cannot satisfy dependencies until it leaves that state. But:

 - for findutils+base-passwd to leave the triggers-awaited state, the
   trigger has to be resolved by dochelp, which cannot happen unless
   dochelp gets configured

 - to configure dochelp, its dependency on findutils+base-passwd have
   to be resolved which cannot happen unless findutils+base-passwd
   leave the triggers-awaited state

This creates the cycle if the packages are installed in a certain order.
"""

If at all possible, please migrate to an "interest-noawait" trigger.
This permits dpkg to defer the trigger to whenever it is convenient in
the install/upgrade process and is often a much better choice.

AFAICT, dochelp does not appear to be a package where deferring the
trigger would cause major issues (I assumed it to be similar to
man-db, which also uses an -noawait trigger).

Admittedly, this particular case *might* be saved by the fact that
findutils and base-passwd are essential.  I haven't tested that.
However, if any of the transitive dependencies of dochelp starts to
provide a doc-base file it will trigger this as well.  Given the
purpose of doc-base, that seems rather likely which is why I have
decided to keep this as "Severity: serious".

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: dochelp
Source-Version: 0.1.5

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated dochelp 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: Thu, 30 Mar 2017 03:59:43 +0200
Source: dochelp
Binary: dochelp
Architecture: source amd64
Version: 0.1.5
Distribution: unstable
Urgency: medium
Maintainer: Mehdi Dogguy 
Changed-By: Mehdi Dogguy 
Description:
 dochelp- Utility to browse system documentation
Closes: 858918
Changes:
 dochelp (0.1.5) unstable; urgency=medium
 .
   * Use "interest-noawait" instead of "interest" in dochelp's dpkg
 trigger (Closes: #858918).
Checksums-Sha1:
 f0dfb80be8c8f816cb4c1a34015261dd9752fc37 1737 dochelp_0.1.5.dsc
 f947ab900bda701323c546b1b1058b24f7d4576a 19016 dochelp_0.1.5.tar.xz
 16d96409c7e629518f5ccfc9434c12883f06381b 82002 dochelp-dbgsym_0.1.5_amd64.deb
 69e0dc511ef7158b5a95114b04deb6247e3783c7 6393 dochelp_0.1.5_amd64.buildinfo
 95db6308396bfda6b6311005bf5783d41634940d 332900 dochelp_0.1.5_amd64.deb
Checksums-Sha256:
 8def3b7c594eaeaa30965de649abc51a110cab00e4ea7572871151d4c1a9aa48 1737 
dochelp_0.1.5.dsc
 1c969a691ab0e453711088217aaa4f1d46c6849ebf44f606a16d6eec50a88620 19016 
dochelp_0.1.5.tar.xz
 479d320d82768d8ed2d9c9b58ddf6a288fc9d75942e8d3a2e33ae87d13a46469 82002 
dochelp-dbgsym_0.1.5_amd64.deb
 f265c940433ebedd17c04079e02a2dcf746502352ba21932033140efba80cc22 6393 
dochelp_0.1.5_amd64.buildinfo
 c04732bcb51409d8fd76676bae5c4ccd7f2705531f240d86653e523a17f8ff27 332900 
dochelp_0.1.5_amd64.deb
Files:
 106750e354a8f521f59397467bb38e2b 1737 doc optional dochelp_0.1.5.dsc
 98199ff2984186f99600e0d8d67d5be2 19016 doc optional dochelp_0.1.5.tar.xz
 2914c228d809954f236793c580be24de 82002 debug extra 
dochelp-dbgsym_0.1.5_amd64.deb
 a9bbe75143216d7f1144f04a9f93b486 6393 doc optional 
doc

Bug#715088: marked as done (Broken library symlink detected in libjack-jackd2-dev)

[Debian Bug Tracking System]

Your message dated Thu, 30 Mar 2017 01:36:36 +
with message-id 
and subject line Bug#858525: fixed in jackd2 1.9.10+20150825git1ed50c92~dfsg-5
has caused the Debian Bug report #858525,
regarding Broken library symlink detected in libjack-jackd2-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.)


-- 
858525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjack-jackd2-dev
Version: 1.9.9.5+20130622git7de15e7a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states "Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available".

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for "Warn: Broken
Symlinks" to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libjackserver.so
-> libjackserver.so.0.1.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:48:19 EST

Package: libjack-jackd2-dev
Source: jackd2
Version: 1.9.9.5+20130622git7de15e7a-1
Installed-Size: 285
Maintainer: Debian Multimedia Maintainers 

Architecture: amd64
Replaces: libjack0.71.2-0 (<< 0.75.0-1)
Provides: libjack-dev, libjack-dev-session, libjack0.100.0-dev
Depends: libjack-jackd2-0 (= 1.9.9.5+20130622git7de15e7a-1), pkg-config, 
libdbus-1-dev
Conflicts: libjack-dev, libjack0.100.0-dev (<< 0.102.20-2)
Description: JACK Audio Connection Kit (development files)
Multi-Arch: same
Homepage: http://jackaudio.org/
Description-md5: 5769772c9db90298e719eeef115bed03
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: 
pool/main/j/jackd2/libjack-jackd2-dev_1.9.9.5+20130622git7de15e7a-1_amd64.deb
Size: 95910
MD5sum: eaa44e40f8fea8f65e49ee63bc1794d8
SHA1: 9db552fb1617a9285e7ab9a278d03f759d19b043
SHA256: 8570947d60d1f0a183332ed2201173f81e666d5b8f1e0fddaa2ab7f6f86fe4d0

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libjack-jackd2-dev=1.9.9.5+20130622git7de15e7a-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 
'libjack-jackd2-dev=1.9.9.5+20130622git7de15e7a-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp46yoDY
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp46yoDY
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp46yoDY', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp46yoDY', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m

Bug#858525: marked as done (libjack-jackd2-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libjackserver.so -> libjackserver.so.0.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 30 Mar 2017 01:36:36 +
with message-id 
and subject line Bug#858525: fixed in jackd2 1.9.10+20150825git1ed50c92~dfsg-5
has caused the Debian Bug report #858525,
regarding libjack-jackd2-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libjackserver.so -> libjackserver.so.0.1.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.)


-- 
858525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjack-jackd2-dev
Version: 1.9.10+20150825git1ed50c92~dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m32.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libjackserver.so -> libjackserver.so.0.1.0


The symlink target is in jackd2. Why isn't that in a library package?
If it is a private library, there should be no public .so symlink being
shipped. Otherwise libjack-jackd2-dev needs to add
  Depends: jackd2 (= ${binary:Version})
(or rather the libpkg where libjackserver.so.0.1.0 gets moved to).


cheers,

Andreas


libjack-jackd2-dev_1.9.10+20150825git1ed50c92~dfsg-4+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.10+20150825git1ed50c92~dfsg-5

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated jackd2 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: Mon, 27 Mar 2017 22:44:11 -0400
Source: jackd2
Binary: jackd2 libjack-jackd2-0 jackd2-firewire libjack-jackd2-dev
Architecture: source
Version: 1.9.10+20150825git1ed50c92~dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Reinhard Tartler 
Description:
 jackd2 - JACK Audio Connection Kit (server and example clients)
 jackd2-firewire - JACK Audio Connection Kit (FFADO and FreeBoB backends)
 libjack-jackd2-0 - JACK Audio Connection Kit (libraries)
 libjack-jackd2-dev - JACK Audio Connection Kit (development files)
Closes: 858525
Changes:
 jackd2 (1.9.10+20150825git1ed50c92~dfsg-5) unstable; urgency=medium
 .
   * Move libjackserver into package libjack-jackd2-0.  This avoids a
 dangling symbolic link in the package libjack-jackd2-dev.
 (Closes: #858525)
Checksums-Sha1:
 c9b6d8335105f168c65ec11f2618f173922bffa6 2692 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.dsc
 15868f47e8b6be08604e98461afec0ba031b0930 40188 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.debian.tar.xz
Checksums-Sha256:
 b14ad633aa2edf943bfd7de664fa832ae93b9191a6c083f5f88ed3938d45ee00 2692 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.dsc
 17e7641eecaf680278e98611a1ae65dbe0a32eb45eeded8c1215cf0821ac74ce 40188 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.debian.tar.xz
Files:
 b35165190e64d53384107f82c3071481 2692 sound optional 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.dsc
 2f8e851871f7a69d324fb342c54daaf4 40188 sound optional 
jackd2_1.9.10+20150825git1ed50c92~dfsg-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEG346Wlh+vrSwRQnyYQkqu5dBnfMFAljcXZkUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQYQkqu5dBnfOdyQ//TgiaLNritYhdbE0Qp523Kbc42tue
ihRTh/rft4ADZaSkv9yRJFfc1XlIoKlQMOvFwaagdZzkSyB9R6Cm9EAeJYeRrf83
+YC4afXbF9FyOa0dHem5tFqPBxH4jTZbjB6cscSwi07BsCqHdyu72vYu4lFTUiOg
SHqznrN4zUZeIcDt74n7Os3IYUrdUmw/c9/8zh7ceCF4B7w/a8TYTadm85kxArWm
+7mqApgE9oSqTiyAvBTv/B7OoRsm4DsG/lPOPGLuxwwkk2FnK88dV345rTCWV32k
+z+vvmHLkwiIVlSIXsGY1ngomrWbv9aCChKDSNTl2GOohwAazUS5mMv/Kdcilzgg
k8lqH6SuGS4C3wFtqJ0Du7tPE0qK3nFAt3oAZ/uigmN6OCRwih4EbnaK3+gojKzq
lWUMx2envSEv6hiCFdDIgCUPPIL7jig5EWjgT0b6M501+S1EFNNhu53JMDHo2GnR
V525CnpcLAfDNnSlf8lB7tc0ycAcA3EHiAS3qDg1PY/9RWJlpydBOIOT2Q1jESvb
voIRurjwA2oCEBouzaUhVXKssYciPJJSLCP4ufpyKfSvam11PSa/LzWEdAt3QHWz
+rPDjJEUa+F/s4okGzz7QvaEBFSZIZQLVcJYpyZPikA8MLuWg4oDw7tRO2byO6j1
ei+eQUcuCTI35zM=
=JTXn
-END PGP SIGNATURE End Message ---

Bug#858525: marked as pending

[Reinhard Tartler]

On 03/29/2017 06:20 AM, Andreas Beckmann wrote:
> On 2017-03-29 03:09, Reinhard Tartler wrote:
>> tag 858525 pending
>> thanks
>>
>> Hello,
>>
>> Bug #858525 reported by you has been fixed in the Git repository. You can
>> see the changelog below, and you can check the diff of the fix at:
>>
>> 
>> http://anonscm.debian.org/git/pkg-multimedia/jackd2.git/commit/?id=cbbda8d
> 
> That misses Breaks+Replaces for the moved library.

Thanks for the review.

The Conflicts is already in place, but the Replaces was indeed missing.
I'll add the Replaces, and avoid exposing libjackserver.so as public
library.

Best,
Reinhard

Bug#859064: mypaint: It does not start on Wayland (fixed upstream)

[Claudio Sacerdoti Coen]

Package: mypaint
Version: 1.2.0-4
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Starting mypaint on Wayland:
claudio@zenone:/tmp/libmypaint$ mypaint
INFO: mypaint: Installation layout: conventional POSIX-like structure
with prefix u'/usr'
INFO: lib.i18n: POSIX: LANG='en_US.UTF-8'
INFO: lib.i18n: POSIX: LANGUAGE='en_US:en'
Gdk-Message: Unable to load bogosity from the cursor theme
Traceback (most recent call last):
  File "/usr/bin/mypaint", line 462, in 
main.main(datapath, iconspath, old_confpath, version=version)
  File "/usr/share/mypaint/gui/main.py", line 95, in main
from gui import application
  File "/usr/share/mypaint/gui/application.py", line 53, in 
import gui.device
  File "/usr/share/mypaint/gui/device.py", line 25, in 
import gui.mode
  File "/usr/share/mypaint/gui/mode.py", line 809, in 
class SingleClickMode (InteractionMode):
  File "/usr/share/mypaint/gui/mode.py", line 813, in SingleClickMode
cursor = gdk.Cursor(gdk.BOGOSITY)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gdk.py", line 329,
in __new__
return cls.new(*args, **kwds)
TypeError: constructor returned NULL

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

Just launch it

   * What was the outcome of this action?

It does not start (see backtrace above)

   * What outcome did you expect instead?

It should start.

Note: the bug was reported and fixed upstream some time ago.
I tried compiling mypaint 1.3.0-alpha (from upstream git repository) and
it works perfectly.

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


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

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

Versions of packages mypaint depends on:
ii  gir1.2-gtk-3.0   3.22.9-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgcc1  1:6.3.0-10
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-1
ii  libgomp1 6.3.0-10
ii  libgtk-3-0   3.22.9-4
ii  libjson-c3   0.12.1-1.1
ii  liblcms2-2   2.8-4
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpng16-16  1.6.28-1
ii  libpython2.7 2.7.13-2
ii  libstdc++6   6.3.0-10
ii  mypaint-data 1.2.0-4
ii  python-gi-cairo  3.22.0-2
ii  python-numpy 1:1.12.0-2
pn  python2.7:any
pn  python:any   

Versions of packages mypaint recommends:
ii  shared-mime-info  1.8-1

Versions of packages mypaint suggests:
ii  mypaint-data-extras  1.2.0-4

-- no debconf information

Processed: severity of 858078 is important, found 858078 in 4.9.16-1

[Debian Bug Tracking System]

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

> severity 858078 important
Bug #858078 [src:linux] Kernel hangs most of the times when modeset=1 on the 
i915
Severity set to 'important' from 'critical'
> found 858078 4.9.16-1
Bug #858078 [src:linux] Kernel hangs most of the times when modeset=1 on the 
i915
Marked as found in versions linux/4.9.16-1.
> thanks
Stopping processing here.

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

Bug#858865: marked as done (dar-static: hard-coded built-using)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 22:34:09 +
with message-id 
and subject line Bug#858865: fixed in dar 2.5.8-3
has caused the Debian Bug report #858865,
regarding dar-static: hard-coded built-using
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.)


-- 
858865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: dar-static
version: 2.5.8-1
severity: serious

Hi,

The build-using line for dar-static contains hard-coded versions for the
built-dependencies that are used in the build, even if the actual build used
different (usually newer) versions of these packages. The versions listed
must be the actual versions of the packages installed when the package is
built.

https://sources.debian.net/src/dar/2.5.8-2/debian/control/#L33

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: dar
Source-Version: 2.5.8-3

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated dar 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: Tue, 28 Mar 2017 20:28:46 +
Source: dar
Binary: libdar-dev libdar64-5000 dar-static dar dar-docs
Architecture: source amd64 all
Version: 2.5.8-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 dar- Disk ARchive: Backup directory tree and files
 dar-docs   - Disk ARchive: Backup directory tree and files
 dar-static - Disk ARchive: Backup directory tree and files
 libdar-dev - Disk ARchive: Development files for shared library
 libdar64-5000 - Disk ARchive: Shared library
Closes: 858865
Changes:
 dar (2.5.8-3) unstable; urgency=medium
 .
   * Auto generate built-using for dar-static (closes: #858865).
   * Use real packages for build dependency.
Checksums-Sha1:
 199ddae1c00e80568400200ec06ab77ea7794938 2026 dar_2.5.8-3.dsc
 a40c3213515b62cacd53a010451cace185e59b6c 6268 dar_2.5.8-3.debian.tar.xz
 4a22a063920a332eae30c81f7440f044735feaa7 2651740 dar-dbgsym_2.5.8-3_amd64.deb
 ea9f9356ae1442fc956fce5205aaab6e3f9e21e8 1044082 dar-docs_2.5.8-3_all.deb
 c3696edbb1eb60195ae820f646f5046fe3822385 7773850 
dar-static-dbgsym_2.5.8-3_amd64.deb
 3787884fc8d31e24cf4860485d13cb991ba40f93 1738116 dar-static_2.5.8-3_amd64.deb
 6a2b0f58f6156a157df35625e569674dcf0b3545 9066 dar_2.5.8-3_amd64.buildinfo
 5c8eeedaddbea24bdac76dcebfdadfa50f8f58fb 365104 dar_2.5.8-3_amd64.deb
 408998070bb3cbee49492f0224f6d32c0ee303f2 921958 libdar-dev_2.5.8-3_amd64.deb
 69222924e6c5d0fe6f3a93269c056075f5efdbb0 7222338 
libdar64-5000-dbgsym_2.5.8-3_amd64.deb
 fd6d322360624751cfd726cf5ac2e93707ae48d4 630246 libdar64-5000_2.5.8-3_amd64.deb
Checksums-Sha256:
 8ab5808ef61ffb2aedadb516e7a40cc6ed592805dfdc7046de4e8b6f923219e0 2026 
dar_2.5.8-3.dsc
 3543ff7abb5a97d7e76077c99761cd467d517a20f9851c1d6dd2141dcd5ac419 6268 
dar_2.5.8-3.debian.tar.xz
 ccec016960e2b624fa89e03de514a57cf0ee3ac5150ed6621f76de3023da9806 2651740 
dar-dbgsym_2.5.8-3_amd64.deb
 70350e27e4ed5d7f649a0cda8db15d989bd0073b5120b454d7e0179197f6564a 1044082 
dar-docs_2.5.8-3_all.deb
 3ef4d70d5212501f1131c9e4c8656d6d54f39f817742750d2b8ed5fb8bb13442 7773850 
dar-static-dbgsym_2.5.8-3_amd64.deb
 89120102123b987402d436dd6b594f5dd7f0ee8224131e2728d335e3692f9b8b 1738116 
dar-static_2.5.8-3_amd64.deb
 4d708a94b658b98e1335de28581285bb6eb6ee54fec9dce4015d2d9bb9021d15 9066 
dar_2.5.8-3_amd64.buildinfo
 7071299f596da5be7430b95128c073e697335590fc0b342c1a11175444686f17 365104 
dar_2.5.8-3_amd64.deb
 602a3f00ae07ea009b7e66383e55837745abe2a3d24aa24f00424819bc95b92d 921958 
libdar-dev_2.5.8-3_amd64.deb
 746f9fca0934e220e52ee2a8dc259dcb4f3154587a07856b0fbed44ad975996d 7222338 
libdar64-5000-dbgsym_2.5.8-3_amd64.deb
 45458d458fc8b8f918e193301ab7e50aafbcad541213bfada39987f2cd0c485b 630246 
libdar64-5000_2.5.8-3_amd64.deb
Files:
 70f5bae3e9b2900fcefc39fc9bb49d0a 2026 utils optional dar_2.5.8-3.dsc
 dfb44c7cc20562f744ceac1655078192 6268 utils optional dar_2.5.8-3.debi

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

The patches in SVN have a bug: 4.0 is using LLVM_3.9 for libllvm 
(simple_version_script.map), though the correct LLVM_4.0 elsewhere 
(AddLLVM.cmake).


The override_dh_makeshlibs/1:x symbols minimum version are needed in all 
versions, not just 3.8.



Also, #857623 (the OpenCL bug) also affects 3.8 and 4.0; the same fix
should work.

This has not yet been done.

Bug#857811: marked as done (synaptic: On Launch Synaptic Immediately Shuts Down w/Error)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 22:57:11 +0100
with message-id <20170329215711.aqx3tr2kw3nm4...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#857811: synaptic: On Launch Synaptic Immediately Shuts 
Down w/Error
has caused the Debian Bug report #857811,
regarding synaptic: On Launch Synaptic Immediately Shuts Down w/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.)


-- 
857811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.84.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The following error is shown, once it's OK'd, Synaptic closes.

E: The value 'testing-proposed-updates' is invalid for APT::Default-Release as
such a release is not available in the sources
E: _cache->open() failed, please report.

That is a source that Synaptic picked itself, not me - and damned if I can find
where this is configured on my system, in order to delete the offending line in
order to relaunch/use Synaptic Package Manager. This app needs some love, see
previous bug filed (not as serious as this one, but a usability bug).



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4~rc2
ii  libapt-pkg5.01.4~rc2
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-6
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-1
ii  libgnutls30  3.5.8-3
ii  libgtk-3-0   3.22.8-1
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpcre2-8-0 10.22-2+b1
ii  libstdc++6   6.3.0-6
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-1
ii  policykit-1  0.105-17
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.49
pn  deborphan
pn  dwww 
ii  menu 2.1.47+b1
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.84.2

On Sat, 18 Mar 2017 at 11:38:26 +0100, Jörg Frings-Fürst wrote:
> on several installations the error could not be confirmed.
> I therefore go along with the bugreporter to close this bug.

SDA wrote

> since update after reportbug report

so I'm going to assume that means the latest version available is fixed.
Closing the bug.

S--- End Message ---

Bug#832128: freespace2: Bad symlinks /usr/games/fs2_open{,_DEBUG}

[Simon McVittie]

On Wed, 29 Mar 2017 at 21:27:26 +1100, Dmitry Smirnov wrote:
> On Wednesday, 29 March 2017 8:42:38 AM AEDT Simon McVittie wrote:
> > Please ask the release team to remove it if that's the case.
> 
> It is already scheduled for removal because of this bug's severity...

If you don't want it in stable, waiting for autoremoval leaves the bug
on the lists seen by people doing bug squashing (like me in this case),
whereas asking for it to be removed would take it off those lists sooner.

> > I've cancelled my delayed NMU.
> 
> OK. So you've decided not to save the package for stable? Fair enough.

You said "I'd rather drop it from Stretch" which I thought meant you
specifically didn't want it to be saved, so I went along with what I
thought was your request as maintainer. Was that a misinterpretation?

I can NMU or not NMU, whichever you prefer; please let me know. You're also
welcome to apply the patch that I attached a couple of messages ago if you
want to do a MU.

I'm not going to upload a new upstream version or other larger changes,
because I don't think the release team are likely to accept an upload not
based on 3.7.2+repack during the freeze.

S

Bug#834686: marked as done (ruby-httpclient: FTBFS randomly (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 21:04:43 +
with message-id 
and subject line Bug#834686: fixed in ruby-httpclient 2.7.1-1.1
has caused the Debian Bug report #834686,
regarding ruby-httpclient: FTBFS randomly (failing tests)
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.)


-- 
834686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-httpclient
Version: 2.7.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

  test_debug_dev:   .: (1.147961)
  test_no_sslv3:F
===
Failure: test_no_sslv3(TestSSL)
/<>/test/test_ssl.rb:221:in `test_no_sslv3'
 218: 
 219:   def test_no_sslv3
 220: teardown_server
  => 221: assert_raise(ArgumentError) do
 222:   setup_server_with_ssl_version(:SSLv3)
 223:   @client.ssl_config.verify_mode = nil
 224:   @client.get("https://localhost:#{serverport}/hello";)

 expected but was
)>

diff:
? ArgumentErrno::EADDRINUSE()
===
: (1.109614)
  test_options: .: (0.101632)
  test_proxy_ssl:   .: (1.284714)
  test_set_default_paths:   .: (1.151999)
  test_sync:.: (1.191771)
  test_use_higher_TLS:  O
===
TODO: it does not pass with Java 7 or old openssl  
[test_use_higher_TLS(TestSSL)]
/<>/test/test_ssl.rb:238:in `test_use_higher_TLS'
===
: (1.102445)
  test_verification:.: (0.197484)

Finished in 183.685536657 seconds.
--
221 tests, 747 assertions, 1 failures, 7 errors, 0 pendings, 1 omissions, 0 
notifications
96.3636% passed
--
1.20 tests/s, 4.07 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_auth.rb" 
"test/test_cookie.rb" "test/test_hexdump.rb" "test/test_http-access2.rb" 
"test/test_httpclient.rb" "test/test_include_client.rb" 
"test/test_jsonclient.rb" "test/test_ssl.rb" "test/test_webagent-cookie.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-httpclient 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-httpclient
Source-Version: 2.7.1-1.1

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated 

Processed: downgrade 859019

[Debian Bug Tracking System]

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

> # "new bugfix release available" is not RC
> severity 859019 normal
Bug #859019 [python-numpy] new bugfix release available
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: ruby-httpclient: diff for NMU version 2.7.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 834686 + patch
Bug #834686 [src:ruby-httpclient] ruby-httpclient: FTBFS randomly (failing 
tests)
Added tag(s) patch.

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

Bug#859027: telegram-desktop: Incomplete debian/copyright?

[Mattia Rizzolo]

On Wed, Mar 29, 2017 at 06:18:35PM +0100, Chris Lamb wrote:
> I just ACCEPTed telegram-desktop from NEW but noticed it was missing 
> attribution in debian/copyright for at least:
> 
>   Telegram/Patches/qtbase_5_6_2.diff
>   debian/patches/Avoid-depending-on-static-libraries.patch

About this last one, this remark is about the change of copyright that
is done in the patch.  Please add a comment in d/copyright about it.

Actually, Nicholas, what's the state of your endeavour to improve the
upstream situation, and reduce the patching done on the Debian site?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#834686: ruby-httpclient: diff for NMU version 2.7.1-1.1

[Paul Gevers]

Control: tags 834686 + patch

Dear maintainer,

I've prepared an NMU for ruby-httpclient (versioned as 2.7.1-1.1). The
diff is below (sorry for in-line, nmudiff failed to work properly for me).

Due to the nature of the bug and the current freeze, I'll upload after
sending this e-mail.

Regards.
diff -Nru ruby-httpclient-2.7.1/debian/changelog
ruby-httpclient-2.7.1/debian/changelog
--- ruby-httpclient-2.7.1/debian/changelog  2016-02-29
21:18:36.0 +0100
+++ ruby-httpclient-2.7.1/debian/changelog  2017-03-29
20:38:15.0 +0200
@@ -1,3 +1,12 @@
+ruby-httpclient (2.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update 0001-Fix-port-allocation-in-tests.patch and
+0003-Try-to-wait-until-socket-is-free.patch to include missing
+instances of port 0 added in upstream 2.6.0.1-1~exp1 (Closes: #834686)
+
+ -- Paul Gevers   Wed, 29 Mar 2017 20:38:15 +0200
+
 ruby-httpclient (2.7.1-1) unstable; urgency=medium

   * New upstream release
diff -Nru
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
---
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
   2016-02-29 21:18:36.0 +0100
+++
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
   2017-03-29 20:38:15.0 +0200
@@ -83,3 +83,23 @@
:AccessLog => [],
:DocumentRoot => DIR,
:SSLEnable => true,
+@@ -293,7 +293,7 @@ private
+ @server = WEBrick::HTTPServer.new(
+   :BindAddress => "localhost",
+   :Logger => logger,
+-  :Port => 0,
++  :Port => 50001,
+   :AccessLog => [],
+   :DocumentRoot => DIR,
+   :SSLEnable => true,
+--- a/test/test_jsonclient.rb
 b/test/test_jsonclient.rb
+@@ -69,7 +69,7 @@ class TestJSONClient < Test::Unit::TestC
+ @server = WEBrick::HTTPServer.new(
+   :BindAddress => "localhost",
+   :Logger => @logger,
+-  :Port => 0,
++  :Port => 5,
+   :AccessLog => [],
+   :DocumentRoot => File.dirname(File.expand_path(__FILE__))
+ )
diff -Nru
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
---
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
   2016-02-29 21:18:36.0 +0100
+++
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
   2017-03-29 20:38:15.0 +0200
@@ -112,3 +112,24 @@
end

def setup_server_with_ssl_version(ssl_version)
+@@ -310,6 +313,9 @@ private
+   )
+ end
+ @server_thread = start_server_thread(@server)
++  rescue Errno::EADDRINUSE
++sleep 1
++retry
+   end
+
+   def do_hello(req, res)
+--- a/test/test_jsonclient.rb
 b/test/test_jsonclient.rb
+@@ -76,5 +76,8 @@ class TestJSONClient < Test::Unit::TestC
+ @serverport = @server.config[:Port]
+ @server.mount('/json', JSONServlet.new(@server))
+ @server_thread = start_server_thread(@server)
++  rescue Errno::EADDRINUSE
++sleep 1
++retry
+   end
+ end



signature.asc
Description: OpenPGP digital signature

Bug#857026: marked as done (wordpress: 4.7.3 security release)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 19:32:15 +
with message-id 
and subject line Bug#857026: fixed in wordpress 4.1+dfsg-1+deb8u13
has caused the Debian Bug report #857026,
regarding wordpress: 4.7.3 security 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.)


-- 
857026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wordpress
Version: 4.7.2
Severity: grave
Tags: upstream security
Justification: user security hole

There are six security issues with wordpress 4.7.2 that wordpress 4.7.3
fixes.

* Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè 
Dale, Yorick Koster, and Simon P. Briggs.
3.6.0 - 4.7.2
https://github.com/WordPress/WordPress/commit/28f838ca3ee205b6f39cd2bf23eb4e5f52796bd7

* Control characters can trick redirect URL validation.  Reported by Daniel 
Chatfield.
2.8.1 - 4.7.2
https://github.com/WordPress/WordPress/commit/288cd469396cfe7055972b457eb589cea51ce40e

* Unintended files can be deleted by administrators using the plugin deletion 
functionality.  Reported by xuliang.
4.7.0 - 4.7.2
https://github.com/WordPress/WordPress/commit/4d80f8b3e1b00a3edcee0774dc9c2f4c78f9e663

* Cross-site scripting (XSS) via video URL in YouTube embeds.  Reported by Marc 
Montpas.
4.0 - 4.7.2
https://github.com/WordPress/WordPress/commit/419c8d97ce8df7d5004ee0b566bc5e095f0a6ca8

* Cross-site scripting (XSS) via taxonomy term names.  Reported by Delta.
4.7 - 4.7.2
no patch supplied

* Cross-site request forgery (CSRF) in Press This leading to excessive use of 
server resources.  Reported by Sipke Mellema.
4,2 - 4.7.2
https://github.com/WordPress/WordPress/commit/263831a72d08556bc2f3a328673d95301a152829


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.1+dfsg-1+deb8u13

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress 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: Thu, 16 Mar 2017 06:19:41 +1100
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentyfifteen 
wordpress-theme-twentyfourteen wordpress-theme-twentythirteen
Architecture: source all
Version: 4.1+dfsg-1+deb8u13
Distribution: jessie-security
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentythirteen - weblog manager - twentythirteen theme files
Closes: 857026
Changes:
 wordpress (4.1+dfsg-1+deb8u13) jessie-security; urgency=medium
 .
   * Backport patches from 4.7.3 Closes: #857026
 - CVE-2017-6814
   Cross-site scripting (XSS) via media file metadata.
   Changeset 40155
 - CVE-2017-6815
   Control characters can trick redirect URL validation.
   Changeset 40190
 - CVE-2017-6816
   Unintended files can be deleted by administrators using the plugin
   deletion functionality.
   Changeset 40176
 - CVE-2017-6817
   Cross-site scripting (XSS) via video URL in YouTube embeds.
   Chamgeset 40167
   * Not vulnerable:
 - CVE-2017-6819
   Cross-site request forgery (CSRF) in Press This leading to excessive
   use of server resources.
   Press This introduced in 4.2
 - CVE-2017-6818
   Cross-site scripting (XSS) via taxonomy term names.
Checksums-Sha1:
 9dc6a86e174682f3449cd58be79d84eb3449e13c 2551 wordpress_4.1+dfsg-1+deb8u13.dsc
 c5eb50e0d

Bug#857651: marked as done (Multiple security issues)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 19:32:08 +
with message-id 
and subject line Bug#857651: fixed in audiofile 0.3.6-2+deb8u2
has caused the Debian Bug report #857651,
regarding Multiple security issues
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.)


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

Hi,
please see these security tracker entries for details, which
have all the links to the reports, github issues and patches:

https://security-tracker.debian.org/tracker/CVE-2017-6829
https://security-tracker.debian.org/tracker/CVE-2017-6831
https://security-tracker.debian.org/tracker/CVE-2017-6832
https://security-tracker.debian.org/tracker/CVE-2017-6833
https://security-tracker.debian.org/tracker/CVE-2017-6834
https://security-tracker.debian.org/tracker/CVE-2017-6835
https://security-tracker.debian.org/tracker/CVE-2017-6836
https://security-tracker.debian.org/tracker/CVE-2017-6837
https://security-tracker.debian.org/tracker/CVE-2017-6838
https://security-tracker.debian.org/tracker/CVE-2017-6839

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: audiofile
Source-Version: 0.3.6-2+deb8u2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated audiofile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 18 Mar 2017 19:28:56 +0100
Source: audiofile
Binary: audiofile-tools libaudiofile-dev libaudiofile1 libaudiofile-dbg
Architecture: source
Version: 0.3.6-2+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Debian Multimedia Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 857651
Description: 
 audiofile-tools - sfinfo and sfconvert tools
 libaudiofile-dbg - Open-source version of SGI's audiofile library (debug)
 libaudiofile-dev - Open-source version of SGI's audiofile library (header 
files)
 libaudiofile1 - Open-source version of SGI's audiofile library
Changes:
 audiofile (0.3.6-2+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Address several vulnerabilities (Closes: #857651)
 - Always check the number of coefficients (CVE-2017-6827 CVE-2017-6828
   CVE-2017-6832 CVE-2017-6833 CVE-2017-6835 CVE-2017-6837)
 - clamp index values to fix index overflow in IMA.cpp (CVE-2017-6829)
 - Check for multiplication overflow in sfconvert (CVE-2017-6830
   CVE-2017-6834 CVE-2017-6836 CVE-2017-6838)
 - Actually fail when error occurs in parseFormat (CVE-2017-6831)
 - Check for multiplication overflow in MSADPCM decodeSample
   (CVE-2017-6839)
   * Fix signature of multiplyCheckOverflow. It returns a bool, not an int
   * Check for division by zero in BlockCodec::runPull
Checksums-Sha1: 
 9ef62372482313a1af0c8f669410d51822ee0230 2385 audiofile_0.3.6-2+deb8u2.dsc
 3aba3ef724b1b5f88cfc20ab9f8ce098e6c35a0e 811733 audiofile_0.3.6.orig.tar.gz
 110bf58c6c24d698eb55aa19894f77907517ac22 15512 
audiofile_0.3.6-2+deb8u2.debian.tar.xz
Checksums-Sha256: 
 381b03e1b3f7270bcca367769b685e3e6a461cfb5a9ff2f30a72bf9e60205e6b 2385 
audiofile_0.3.6-2+deb8u2.dsc
 cdc60df19ab08bfe55344395739bb08f50fc15c92da3962fac334d3bff116965 811733 
audiofile_0.3.6.orig.tar.gz
 6f08b8d898317e92b42722f8040d1c6c42ceb717068f40b66251486656910738 15512 
audiofile_0.3.6-2+deb8u2.debian.tar.xz
Files: 
 d5ac09ee6abc76c7f1cd46187d9d1763 2385 libs optional 
audiofile_0.3.6-2+deb8u2.dsc
 2731d79bec0acef3d30d2fc86b0b72fd 811733 libs optional 
audiofile_0.3.6.orig.tar.gz
 ed19806ebe18badf2256636de983482c 15512 libs optional 
audiofile_0.3.6-2+deb8u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAljNgMxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ER1UQAINRqHyi+BqRt85Aw7FrivdNCGd3WOBG
bU92

Bug#857313: marked as done (cylc can FTBFS when build directory contains underscore)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 18:18:54 +
with message-id 
and subject line Bug#857313: fixed in cylc 6.11.2-6
has caused the Debian Bug report #857313,
regarding cylc can FTBFS when build directory contains underscore
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.)


-- 
857313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cylc
Version: 6.11.2-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that cylc could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/VERSION   1970-01-01 01:00:00.0 +0100
--- b/VERSION   2017-03-09 22:08:04.026090348 +
@@ -0,0 +1 @@
+6.11.2
--- a/debian/rules  2017-03-09 21:39:39.863360902 +
--- b/debian/rules  2017-03-09 22:07:52.194043486 +
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+VERSION = $(shell dpkg-parsechangelog --show-field Version)
+
 # The magic debhelper rule:
 %:
dh  $@ --with python2
@@ -8,6 +10,7 @@
PATH=$(PATH):$(CURDIR)/bin && $(MAKE)
 
 override_dh_auto_install:
+   echo $(VERSION) > VERSION
# Don't support gpanel. Requires gnome2's gnomeapplet.
rm -rf  bin/cylc-gpanel conf/gpanel
mkdir -p debian/tmp/usr/bin
--- End Message ---
--- Begin Message ---
Source: cylc
Source-Version: 6.11.2-6

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated cylc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 29 Mar 2017 18:54:07 +0100
Source: cylc
Binary: cylc python-cylc
Architecture: source amd64
Version: 6.11.2-6
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 cylc   - Workflow scheduler
 python-cylc - Python libraries for cylc workflow scheduler
Closes: 857313
Changes:
 cylc (6.11.2-6) unstable; urgency=medium
 .
   * Patch to fix FTBFS when version includes an underscore.
 Thanks to Chris Lamb. Closes: #857313
Checksums-Sha1:
 dc96d36a1a22f4a0d9e091a5f6fe3b7b3ca298c8 1983 cylc_6.11.2-6.dsc
 4e0d44b41b5942f2beb1ffb699b8188eff897a35 14848 cylc_6.11.2-6.debian.tar.xz
 ddf5b2bcac162b242ed622f24e250bafb34e59e6 10199 cylc_6.11.2-6_amd64.buildinfo
 507fcf5fa43dc9f148f656550a4516895265e47f 95730 cylc_6.11.2-6_amd64.deb
 3e2d4e30a9f634b43a2615eedefb8b69966ed903 342708 python-cylc_6.11.2-6_amd64.deb
Checksums-Sha256:
 72133034409bf3a06a208fc96d128127028614d5b68febf9deb85b45e71c4797 1983 
cylc_6.11.2-6.dsc
 298b21695766e5b29992c692f2b435dde847bc59293f55cdb491e088a8b62101 14848 
cylc_6.11.2-6.debian.tar.xz
 c5f141b4e7f5cfb9c03c1ff409ca912f653736f19fefb752fe0146a64f8034ba 10199 
cylc_6.11.2-6_amd64.buildinfo
 a7d98cf63c9be188650db39b08db11bafe7ed08a92252c170a9c504d3a95fc4b 95730 
cylc_6.11.2-6_amd64.deb
 79574db051fb86b3a85724ceb8bac9f30c1704c38cefd069680b5a7a39be0b97 342708 
python-cylc_6.11.2-6_amd64.deb
Files:
 79971f29aca5a40544988444853cbb94 1983 utils optional cylc_6.11.2-6.dsc
 11ebc654d427f30e4abd612ca025e6be 14848 utils optional 
cylc_6.11.2-6.debian.tar.xz
 18c548bb595623e7b84aa79dd263f392 10199 utils optional 
cylc_6.11.2-6_amd64.buildinfo
 be1f20e75353655b94eedf508d9d554c 95730 utils optional cylc_6.11.2-6_amd64.deb
 7fc219e87ec902b2715395986a18e403 342708 python optional 
python-cylc_6.11.2-6_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAljb9pwACgkQy+a7Tl2a
06Vy0Q/9Fa95SyHbZT0qvRunjmyfoMoRuIUZk3PrDbmH19DAqwPJyApxLHRmrSDc
4ytJCrw8zusJStRpEXb2JuMJfuOk/WaTtcX8+VRIeLI0W00lF/OG6MxTt0SUROi6
gwcNf2zT0oLC+ng4p//Sn9TXBvTrF3gEwY6sRWaxbjLJXK6Y87eUbRi22e7Ze0r0
zDGHsfpPOoAzLsHA12EHbqFjAFf8azvjCVR8PAER68l5Hf0+rS7vL99Neo+1t

Bug#859032: hfst-ospell: Incomplete debian/copyright?

[Tino Didriksen]

On 29 March 2017 at 19:43, Chris Lamb  wrote:

> I just ACCEPTed hfst-ospell from NEW but noticed it was missing
> attribution in debian/copyright for at least:
>
>   office.cc:4:  Copyright 2015 Tino Didriksen 
>
> (This is not exhaustive so please check over the entire package
> carefully and address these on your next upload.)



As the author of both office.cc and debian/*, I'd say it's fine.

I mostly put myself in office.cc so people would know who to direct bug
reports to, but the file is copyright-assigned to the HFST project, as the
first line says.

I did however miss attribution for a file in m4/ - will fix for next time.

-- Tino Didriksen

Bug#859032: hfst-ospell: Incomplete debian/copyright?

[Chris Lamb]

Source: hfst-ospell
Version: 0.4.3~r338-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Kartik Mistry 

Hi,

I just ACCEPTed hfst-ospell from NEW but noticed it was missing 
attribution in debian/copyright for at least:

  office.cc:4:  Copyright 2015 Tino Didriksen 

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


Regards,

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

Bug#858500: marked as done (libsanlock-dev: missing Depends: libsanlock1 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 17:34:16 +
with message-id 
and subject line Bug#858500: fixed in sanlock 3.3.0-2.1
has caused the Debian Bug report #858500,
regarding libsanlock-dev: missing Depends: libsanlock1 (= ${binary:Version})
to be marked as done.

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

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


-- 
858500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsanlock-dev
Version: 3.3.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m18.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/sanlock/libsanlock.so -> libsanlock.so.1.0
  /usr/lib/sanlock/libwdmd.so -> libwdmd.so.1.0


cheers,

Andreas


libsanlock-dev_3.3.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sanlock
Source-Version: 3.3.0-2.1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated sanlock 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, 24 Mar 2017 13:11:12 +0100
Source: sanlock
Binary: sanlock libsanlock-client1 libsanlock1 libsanlock-dev python-sanlock
Architecture: source
Version: 3.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Milan Zamazal 
Changed-By: Anton Gladky 
Description:
 libsanlock-client1 - Shared storage lock manager (client library)
 libsanlock-dev - Shared storage lock manager (development files)
 libsanlock1 - Shared storage lock manager (shared library)
 python-sanlock - Python bindings to shared storage lock manager
 sanlock- Shared storage lock manager
Closes: 858500
Changes:
 sanlock (3.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add libsanlock1 as a dependency of libsanlock-dev. (Closes: #858500)
   * Move libsanlock.so and libwdmd.so out of /usr/lib/sanlock into
 /usr/lib to fix broken symlinks.
Checksums-Sha1:
 b73ac1700d44d4df61862af8f4b171af68daeb45 2035 sanlock_3.3.0-2.1.dsc
 921dfeea39e99f3f49c97a7fdb299833d76dc08d 8008 sanlock_3.3.0-2.1.debian.tar.xz
 4ce99ce4ac4c68077ec23f3b9a9fb7f09c5e 6729 
sanlock_3.3.0-2.1_source.buildinfo
Checksums-Sha256:
 c6b4bbc9abd489d936640b2d8971a50d67470e7520dd59cece414286f4dbc4a7 2035 
sanlock_3.3.0-2.1.dsc
 d75809ccc28edce76fad01397b920dd072c64c86fc263a2bcc27ff48c2a02dfd 8008 
sanlock_3.3.0-2.1.debian.tar.xz
 1aba1f761103ae8a4875d892969127db1229b263db332d8631c1017d452b11c1 6729 
sanlock_3.3.0-2.1_source.buildinfo
Files:
 285cf03c5cf096ed0550b0c83361c009 2035 libs optional sanlock_3.3.0-2.1.dsc
 bae8e2c6c74ab273bd4346eced8c0bf0 8008 libs optional 
sanlock_3.3.0-2.1.debian.tar.xz
 bd18bf91f1bd8e987b50a7fb745e5479 6729 libs optional 
sanlock_3.3.0-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAljWF3MACgkQ0+Fzg8+n
/wbjMg/8CHgee4yNzKC/+vovEG1JWEcx6SHEozq/rgUSi43YC88XEqOVqXD8C+8n
pR0h7K4d4AyxWQFE1JvQkBgmjjCgg+7AdBNBDbcQ0ggZEOUOJGVvB3dY7Qvgf/M/
lHTf3ov7uImRyOLWeUGGsY2yQMPaBvE+8OjJXve7Btn1f7SIJ2iK3yf7JUjvvqqs
MX6XDGsCPCsFU1GfQdQSFHtMYgaNgUjr83M9lDQd0AfRDMHqj0z/5+fvTT13e5WA
ii3uJ0oreyr9yS1+F6yotyHNSEa27iYTAhP2myvPr4oZnYjDEF3q8cAedfy3A4Vk
ArMGeDjwh+q8tG39Jrqmbp1qNbVWzTgNDgNre3DXahWLcrRMOJjG1f5FNMyIs4mv
nbyrade3ER5crrLdZkamNarLY67psbYC8QkIsRTTBmxrEfG/+GePAv5xdir/L0cd
79Y6NSFxIB6g5dSojjD7+QGk+GKoeuK3gXm/ThAPJyHOJ5H/oXqIvql+lZRsyvnV
gaKSnPvdgQB1ozvsgDA04O1xnhsGuFN219OQ+iAK/ypg4WEVM8bRHJTHTVqsl6kp
2836G45509S7JFVAV8jm4vPZxbYu7o+g/hAUVO7w1kYGXrL/fnoDgmqJSFzqZ2Av
j2FsB1iGWA/pvp/Uis1+OMdnWCRpABdFWCQQXOFag5gtKSPq+j8=
=iZz2
-END PGP SIGNATURE End Message ---

Bug#859027: telegram-desktop: Incomplete debian/copyright?

[Chris Lamb]

Source: telegram-desktop
Version: 1.0.14-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Nicholas Guriev 

Hi,

I just ACCEPTed telegram-desktop from NEW but noticed it was missing 
attribution in debian/copyright for at least:

  Telegram/Patches/qtbase_5_6_2.diff
  debian/patches/Avoid-depending-on-static-libraries.patch

etc.

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


Regards,

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

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

[Michael Stapelberg]

Hi Tim,

"Potter, Tim"  writes:
> Hi Ricardo.  Thanks for the bug report.  I messed up by uploading some of the 
> Docker 1.13
> dependencies to unstable instead of experimental - my apologies.
>
> I've done a new upload with a Breaks line to avoid this bug occurring until I 
> finish testing
> 1.13 and uploading to unstable.

I’m still running into this issue (or a very similar one?) with:

docker.io 1.13.0~ds1-2
runc 0.1.1+dfsg1-2+b1
containerd 0.2.3~git20161117.78.03e5862~ds1-2
golang-libnetwork 0.8.0~dev.2+git20161130.568.fd27f22-4

I installed these packages from Debian unstable, but AFAICT, no newer
version is available in experimental.

The symptom is:
$ docker run -t -i debian:sid /bin/bash
docker: Error response from daemon: containerd: container not started.

In the journal, I can’t see any errors from containerd itself.

Should docker be working in Debian at the moment? If not, is there a
workaround?

Thanks!

-- 
Best regards,
Michael

Bug#859026: Uses uscan in the clean target and passes its output to rm

[Andrey Rahmatullin]

Package: src:sugar-physics-activity
Version: 7+dfsg-1.3
Severity: critical

UPSTREAM_VERSION ?=$(shell uscan --dehs | sed -n 's/.*\(.*\)<\/upstream-version>.*/\1/p')
[...]
clean::
[...]
rm -rf Physics-${UPSTREAM_VERSION}

So, it uses network (the build without network doesn't fail though), it
downloads an unnecessary file, it looks for a latest version instead of the
package version and it puts untrusted network input right into an rm command.



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

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

Bug#857988: marked as done (libjs-jquery-selectize.js: Build-Depends on npm uselessly)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 16:18:53 +
with message-id 
and subject line Bug#857988: fixed in libjs-jquery-selectize.js 0.12.3+dfsg-1.1
has caused the Debian Bug report #857988,
regarding libjs-jquery-selectize.js: Build-Depends on npm uselessly
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.)


-- 
857988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-jquery-selectize.js
Severity: important

Please remove the useless Build-Depends: npm,
for i intend to ask removal of npm from testing.

Usually nodejs and/or nodejs-dev or node-gyp or node-nan are the packages
you need to Build-Depend on.

Jérémy.

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libjs-jquery-selectize.js
Source-Version: 0.12.3+dfsg-1.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated 
libjs-jquery-selectize.js 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: Wed, 29 Mar 2017 20:50:45 +0500
Source: libjs-jquery-selectize.js
Binary: libjs-jquery-selectize.js
Architecture: source
Version: 0.12.3+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Sergio Durigan Junior 
Changed-By: Andrey Rahmatullin 
Description:
 libjs-jquery-selectize.js - Extensible jQuery-based custom select UI control
Closes: 857988
Changes:
 libjs-jquery-selectize.js (0.12.3+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop unused B-D: npm (Closes: #857988).
Checksums-Sha1:
 318163c1910e4a862b53c5c851059d58013cc2fd 2171 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.dsc
 0e9b6edecfb8cb4ec5f19e7b4f70d919d26cb3df 5672 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.debian.tar.xz
 c6deb0ca989d600f181388db82de3bb236211419 7136 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1_amd64.buildinfo
Checksums-Sha256:
 3b1c5e0f980255ef37fc32cac5e19b80af8391b40f758d9efb799acd1d52bd4f 2171 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.dsc
 220a05b946d11b13aa2f4cafad01fa129d3275672be1883d9afcf618414dbd39 5672 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.debian.tar.xz
 8836a2b2c8f537fa382adcc2854677eb43c1fe685c2ac42620cc14c5274ddad7 7136 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1_amd64.buildinfo
Files:
 4b1fbbff01cdc1299ff3c408556d5961 2171 web optional 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.dsc
 bfea84bd4b3f989a3692676a9be29b73 5672 web optional 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1.debian.tar.xz
 6e3593b7e98cede6a1e7ed6fae966346 7136 web optional 
libjs-jquery-selectize.js_0.12.3+dfsg-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAljb2RsACgkQM2L3AxpJ
kuFT8hAApyzl94sQBHPwlJm8Miv5sv0VKWfCrSQ50V2WWdRYcB3XAx2hdjbrlGDq
prkMl3ed2Vx98JjBrt5/oYMq6lOk7zWRi1vT5JDTMCoX+zTC97JrBZNOLMQkbZDr
phRubT8efnYIZYrS9VAiTl/hyAPJh+/HEv6bqmZM1d5Vze9T79WbiqWsqzNfOtP3
ngF0TS+iqHkCq+QLerXiPx653kZ/aniBLBeIwjJH2xhXT3bv52uTTnl5VtnAuDt3
1t9wZZqaQrIcB/ZastTWo6EasFxJVNcwKr9Qn3MsvgQKOHwkwxhkzrSRYGTtk8Lu
MvCdfz/B6PiOSPGTNq3V6RqNiJJChS6H+K8SgLzv+2YOXrYYBmn7gPQwYPFplqG/
Uj+8ezj/3EPuNfGt9X5Iab5ewGDYFXcu6bodvyadjjkZANbrWRJmL66nwGu/ouSf
6INnRiCMzOZ9K9B+w+OtwpQ+n6RsY6bJaJcytPxbh3E7dQjduaYnDFOMEGqYF1pw
yxy/sRugti8QazQulw0I0PSVbFnfuyUQDZ8F4+3+unpKnv8iWzGZx7NMoLEg7Enh
vsEDykTDG/N2nulnivm3cWDka5knIUs/reGgFtEk5u4lIcGsbRD6xyfLM5xkL3dw
jaCIn7+3KcUueFIhGGZUC5JAfngroMFqSmjWteQRkM1WsbZsbQw=
=6rp3
-END PGP SIGNATURE End Message ---

Processed: libjs-jquery-selectize.js: diff for NMU version 0.12.3+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 857988 + patch
Bug #857988 [libjs-jquery-selectize.js] libjs-jquery-selectize.js: 
Build-Depends on npm uselessly
Added tag(s) patch.

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

Bug#859019: new bugfix release available

[Julian Taylor]

Package: python-numpy
Version:  1:1.12.0-2
Severity: serious

hi,
A new bug release is available for numpy. It is almost exclusively regression 
fixes in 1.12.0 and should be included in stretch.
In case you want to go with backports I have marked the issues I consider 
important.

* `#8483 `__: BUG: Fix wrong future 
nat warning and equiv type logic error...

important (already in debian package)
* `#8489 `__: BUG: Fix wrong masked 
median for some special cases

* `#8490 `__: DOC: Place np.average 
in inline code
* `#8491 `__: TST: Work around 
isfinite inconsistency on i386

important
* `#8494 `__: BUG: Guard against 
replacing constants without '_' spec in f2py.
* `#8524 `__: BUG: Fix mean for float 
16 non-array inputs for 1.12
* `#8571 `__: BUG: Fix calling python 
api with error set and minor leaks for...

important
* `#8602 `__: BUG: Make iscomplexobj 
compatible with custom dtypes again
* `#8618 `__: BUG: Fix undefined 
behaviour induced by bad __array_wrap__

important
* `#8648 `__: BUG: Fix 
MaskedArray.__setitem__
* `#8659 `__: BUG: PPC64el machines 
are POWER for Fortran in f2py
* `#8665 `__: BUG: Look up methods on 
MaskedArray in `_frommethod`
* `#8674 `__: BUG: Remove extra digit 
in binary_repr at limit

important
* `#8704 `__: BUG: Fix deepcopy 
regression for empty arrays.

important
* `#8707 `__: BUG: Fix ma.median for 
empty ndarrays

cheers,
Julian



signature.asc
Description: OpenPGP digital signature

Bug#832931: Investigation confirms building without Jemalloc fixes the problem

[Vicențiu Ciorbaru]

I've investigated this myself and have come to the conclusion that the only
feasible way to fix this for this release is to disable building MariaDB
with Jemalloc for this platform only. Thanks a lot for the work done
by Thadeu Lima de Souza Cascardo this was easier to figure out.

I'm concerned that a lot of users will be affected by this jemalloc
package, not just MariaDB users. Otto will adjust the build process to
refrain from using jemalloc in this case.

Thanks,
Vicentiu

Bug#858957: marked as done (libstk0-dev: broken symlinks: /usr/include/stk/Rt{audio, Midi}.h -> ../Rt{audio, Midi}.h)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 15:11:53 +
with message-id 
and subject line Bug#858957: fixed in stk 4.5.2+dfsg-5
has caused the Debian Bug report #858957,
regarding libstk0-dev: broken symlinks: /usr/include/stk/Rt{audio, Midi}.h -> 
../Rt{audio, Midi}.h
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.)


-- 
858957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstk0-dev
Version: 4.5.2+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m18.5s ERROR: FAIL: Broken symlinks:
  /usr/include/stk/RtMidi.h -> ../RtMidi.h
  /usr/include/stk/RtAudio.h -> ../RtAudio.h

Maybe you wanted to target ../rtmidi/*.h ?


cheers,

Andreas


libstk0-dev_4.5.2+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: stk
Source-Version: 4.5.2+dfsg-5

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated stk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 29 Mar 2017 10:39:43 -0300
Source: stk
Binary: libstk0-dev libstk-4.5.0 stk stk-doc
Architecture: source
Version: 4.5.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 libstk-4.5.0 - Sound Synthesis Toolkit
 libstk0-dev - Sound Synthesis Toolkit (development files)
 stk- Sound Synthesis Toolkit (example applications)
 stk-doc- Sound Synthesis Toolkit (documentation)
Closes: 858895 858957
Changes:
 stk (4.5.2+dfsg-5) unstable; urgency=medium
 .
   * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
   * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)
Checksums-Sha1:
 f5b681d0f2b3c67adb29954bab8cbda91cd3deb8 2395 stk_4.5.2+dfsg-5.dsc
 62ac737276a47328ac6058955397079cc734fd1c 15432 stk_4.5.2+dfsg-5.debian.tar.xz
 b5de477f86b0522915fdecdabde0cbbe837a7310 5337 stk_4.5.2+dfsg-5_source.buildinfo
Checksums-Sha256:
 012729d9fc11a2abc3e67409d3243c0fbea15072a1b2b9c7ef1f95364fcde7b7 2395 
stk_4.5.2+dfsg-5.dsc
 12b1bc580da837cda22eb96afcc3f9e430a789be2aacf6bd63bf8c458e347e32 15432 
stk_4.5.2+dfsg-5.debian.tar.xz
 73f75d7b1ffc42d461de5a145cefbcbfb65c6b7dddcb682c02721ffd1fc1c5e2 5337 
stk_4.5.2+dfsg-5_source.buildinfo
Files:
 ab360cfd849f90becdf54db97574da80 2395 sound optional stk_4.5.2+dfsg-5.dsc
 689e7d5ce3e1d4efd105fae7659c5f41 15432 sound optional 
stk_4.5.2+dfsg-5.debian.tar.xz
 5b1850c9a5c029a9887e984cb93174f9 5337 sound optional 
stk_4.5.2+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAljbukAUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s/MGw/8CkBA89IM/PWrFloAa021H4OECkfs
5CvSPnQIZgjlu5KUP6GIC83+/wUJ2PZd0HksXTaAQIjLVBwbLe0qfmR+OcUNjdHl
wgxY6yUWACSNvLeCm1JpoEa7qdzobpK+Sx6ccayrQiXlOskkIhXbhm59sLZHRBEh
+n/JD8pLLGWn7a4b02sHWIiNQznRPKZITjja2x4St0JB/xzYDPo56TEUACl+ioc7
ljm2fgHl3UdCDfj8qRWn7Xgm+tNGcfRO41M59p+U22pPbY1FgpjO3yjpaByIqa7y
MvEXlNbmenVHLbQC4lmsUNNMycGLJEeCwlUsz/VYi/z+/+y24zqX/w9efdgCvbJf
9fEeA6tU8b9XkK3cuP1G/gLlhMZleCCGEzCuKOx2GLNtUqpBh/5S+jJc7zdhGob2
GcTBNLZwVeDvc2xIvJb6Uo/KgPybUI/RF+mk9bk74CB0Wo5c9/VgeC1lmFNngGvN
rvhhrf1QGRKPnUEIUYWyT/2vQd+ThMdcKAyaY9fzrAEosoz5rWb2pp+TvPx/vmx+
LkEurTQti0moWL33q3J3GSOM5cT9iOkuMko2YWr6jJDWvU/CPLc7gtzDzC/K25Us
ZC91jKkwZSORUjCC/uDD5qIAUezCWxsCWxrmv6Pp7NdQ2hm7q2A94M1hlP7H6jG+
KadD1z6Tw+BiiFY=
=v+Fr
-END PGP SIGNATURE End Message ---

Bug#858895: marked as done (stk: fails to find soundfile)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 15:11:53 +
with message-id 
and subject line Bug#858895: fixed in stk 4.5.2+dfsg-5
has caused the Debian Bug report #858895,
regarding stk: fails to find soundfile
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.)


-- 
858895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stk
Version: 4.5.2+dfsg-4
Severity: serious
Justification: grave

Dear Maintainer,

Launching 
stk-demo TubeBell -or
throws an error
FileRead::open: could not open or find file 
(../../rawwaves/sinewave.raw)!
while the file searched for is in place in
/usr/share/stk/rawwaves/sinewave.raw

Most likely the source of the error is
http://sources.debian.net/src/stk/unstable/projects/demo/demo.cpp/#L216

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages stk depends on:
ii  libasound21.1.3-5
ii  libc6 2.24-9
ii  libgcc1   1:6.3.0-10
ii  libjack0 [libjack-0.125]  1:0.125.0-2
ii  librtaudio5a  4.1.2~ds0-4
ii  librtmidi32.1.1~ds0-4
ii  libstdc++66.3.0-10
ii  libstk-4.5.0  4.5.2+dfsg-4
ii  tk8.6.0+9

stk recommends no packages.

stk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: stk
Source-Version: 4.5.2+dfsg-5

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated stk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 29 Mar 2017 10:39:43 -0300
Source: stk
Binary: libstk0-dev libstk-4.5.0 stk stk-doc
Architecture: source
Version: 4.5.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 libstk-4.5.0 - Sound Synthesis Toolkit
 libstk0-dev - Sound Synthesis Toolkit (development files)
 stk- Sound Synthesis Toolkit (example applications)
 stk-doc- Sound Synthesis Toolkit (documentation)
Closes: 858895 858957
Changes:
 stk (4.5.2+dfsg-5) unstable; urgency=medium
 .
   * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
   * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)
Checksums-Sha1:
 f5b681d0f2b3c67adb29954bab8cbda91cd3deb8 2395 stk_4.5.2+dfsg-5.dsc
 62ac737276a47328ac6058955397079cc734fd1c 15432 stk_4.5.2+dfsg-5.debian.tar.xz
 b5de477f86b0522915fdecdabde0cbbe837a7310 5337 stk_4.5.2+dfsg-5_source.buildinfo
Checksums-Sha256:
 012729d9fc11a2abc3e67409d3243c0fbea15072a1b2b9c7ef1f95364fcde7b7 2395 
stk_4.5.2+dfsg-5.dsc
 12b1bc580da837cda22eb96afcc3f9e430a789be2aacf6bd63bf8c458e347e32 15432 
stk_4.5.2+dfsg-5.debian.tar.xz
 73f75d7b1ffc42d461de5a145cefbcbfb65c6b7dddcb682c02721ffd1fc1c5e2 5337 
stk_4.5.2+dfsg-5_source.buildinfo
Files:
 ab360cfd849f90becdf54db97574da80 2395 sound optional stk_4.5.2+dfsg-5.dsc
 689e7d5ce3e1d4efd105fae7659c5f41 15432 sound optional 
stk_4.5.2+dfsg-5.debian.tar.xz
 5b1850c9a5c029a9887e984cb93174f9 5337 sound optional 
stk_4.5.2+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAljbukAUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s/MGw/8CkBA89IM/PWrFloAa021H4OECkfs
5CvSPnQIZgjlu5KUP6GIC83+/wUJ2PZd0HksXTaAQIjLVBwbLe0qfmR+OcUNjdHl
wgxY6yUWACSNvLeCm1JpoEa7qdzobpK+Sx6ccayrQiXlOskkIhXbhm59sLZHRBEh
+n/JD8pLLGWn7a4b02sHWIiNQznRPKZITjja2x4St0JB/xzYDPo56TEUACl+ioc7
ljm2fgHl3UdCDfj8qRWn7Xgm+tNGcfRO41M59p+U22pPbY1FgpjO3yjpaByIqa7y
MvEXlNbmenVHLbQC4lmsUNNMycGLJEeCwlUsz/VYi/z+/+y24zqX/w9efdgCvbJf
9fEeA6tU8b9XkK3cuP1G/gLlhMZleCCGEzCuKOx2GLNtUqpBh

Bug#859001: Pending fixes for bugs in the libbrowserlauncher-java package

[pkg-java-maintainers]

tag 859001 + pending
thanks

Some bugs in the libbrowserlauncher-java package are closed in
revision e8e93af065fad9135162bcb18f57d03861d49f91 in branch 'master'
by Ole Streicher

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

Commit message:

Remove release number from jar name

Closes: #859001

Processed: Pending fixes for bugs in the libbrowserlauncher-java package

[Debian Bug Tracking System]

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

> tag 859001 + pending
Bug #859001 [libbrowserlauncher-java] libbrowserlauncher-java: No jar file 
without version number
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#859001: libbrowserlauncher-java: No jar file without version number

[Ole Streicher]

Hi Markus,

Am 29.03.2017 um 15:46 schrieb Markus Koschany:
> In the case of backports you would probably backport jmodeltest as well,
> so both could be easily kept in sync. AFAICT both packages seem to work
> well together and librowserlauncher-java was only packaged to build
> jmodeltest from source.

Not necessarily. I am currently preparing another dependency (topcat,
#855797) and plan to backport it later to Stretch -- this is why I look
into browserlauncher2.

Cheers

Ole

Bug#858957: marked as pending

[Felipe Sateler]

tag 858957 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/stk.git/commit/?id=7b2ec31

---
commit 7b2ec31c8f7bbdcad893502e21533056ad5a26b9
Author: Felipe Sateler 
Date:   Wed Mar 29 10:40:12 2017 -0300

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index d293d44..29fcf7d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.5.2+dfsg-5) unstable; urgency=medium
+
+  * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
+  * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)
+
+ -- Felipe Sateler   Wed, 29 Mar 2017 10:39:43 -0300
+
 stk (4.5.2+dfsg-4) unstable; urgency=medium
 
   [ Petter Reinholdtsen ]

Processed: Bug#858895 marked as pending

[Debian Bug Tracking System]

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

> tag 858895 pending
Bug #858895 [stk] stk: fails to find soundfile
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#858895: marked as pending

[Felipe Sateler]

tag 858895 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/stk.git/commit/?id=7b2ec31

---
commit 7b2ec31c8f7bbdcad893502e21533056ad5a26b9
Author: Felipe Sateler 
Date:   Wed Mar 29 10:40:12 2017 -0300

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index d293d44..29fcf7d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.5.2+dfsg-5) unstable; urgency=medium
+
+  * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
+  * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)
+
+ -- Felipe Sateler   Wed, 29 Mar 2017 10:39:43 -0300
+
 stk (4.5.2+dfsg-4) unstable; urgency=medium
 
   [ Petter Reinholdtsen ]

Bug#859005: libbrowserlauncher-java: properties file not included

[Markus Koschany]

Am 29.03.2017 um 15:50 schrieb Ole Streicher:
> The properties file also contains a bug the prevents from using
> IceWeasel even when it would be included. So, when fixing this, the
> attached patch should be applied as well.
> 
> I can't do this myself since I just realized that I am not in the
> java-maintainers group.
> 
> Cheers
> 
> Ole

I can grant you access to pkg-java, if you like. Just click on the
"request to join" link on this site [1] bottom corner.

https://alioth.debian.org/projects/pkg-java/




signature.asc
Description: OpenPGP digital signature

Processed: Bug#858957 marked as pending

[Debian Bug Tracking System]

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

> tag 858957 pending
Bug #858957 [libstk0-dev] libstk0-dev: broken symlinks: 
/usr/include/stk/Rt{audio, Midi}.h -> ../Rt{audio, Midi}.h
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#859005: libbrowserlauncher-java: properties file not included

[Ole Streicher]

The properties file also contains a bug the prevents from using
IceWeasel even when it would be included. So, when fixing this, the
attached patch should be applied as well.

I can't do this myself since I just realized that I am not in the
java-maintainers group.

Cheers

Ole
>From 69e74fe6a26e7ce4a3716607b2330d5fbe8b76b2 Mon Sep 17 00:00:00 2001
From: Ole Streicher 
Date: Wed, 29 Mar 2017 15:41:52 +0200
Subject: [PATCH] Fix typo for browser start

---
 debian/patches/browser_choice.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/patches/browser_choice.patch b/debian/patches/browser_choice.patch
index 3c90687..bf5539b 100644
--- a/debian/patches/browser_choice.patch
+++ b/debian/patches/browser_choice.patch
@@ -12,7 +12,7 @@ Last-Update: Wed, 11 May 2016 13:31:20 +0200
 -browser.mozilla=Mozilla;mozilla; ; -remote openURL()
 -browser.netscape=Netscape;netscape; ; -remote openURL()
  browser.firefox=FireFox;firefox; ; -new-tab ; -new-window 
-+browser.ceweasel=IceWeasel;iceweasel; ; -new-tab ; -new-window 
++browser.iceweasel=IceWeasel;iceweasel; ; -new-tab ; -new-window 
  browser.mozilla-firefox=FireFox;mozilla-firefox; ; -remote openURL(); -new-window 
  browser.konqueror=Konqueror;kfmclient; openURL ; newTab ; openURL 
  browser.opera=Opera;opera; ; -newpage ; -newwindow 
-- 
2.11.0

Bug#859001: libbrowserlauncher-java: No jar file without version number

[Markus Koschany]

Am 29.03.2017 um 15:30 schrieb Ole Streicher:
> Hi Markus,
> 
> Am 29.03.2017 um 15:15 schrieb Markus Koschany:
>>> There is no jar without a version number. This makes it impossible to
>>> add the jar to the CLASSPATH of other packages,
>>
>> This is not true. You can add such jar files to your CLASSPATH.
>>> since the file name will change silently with the next version.
>>
>> This is true.
> 
> This is my point: we cannot rely on it.
> 
>>> Therefore, please include also a versionless jar file
>>> BrowserLauncher2.jar. This is also requested by Java policy.
>>
>> Java Policy is more like Parley from Pirates of the Caribbean and
>> incomplete by the way. I suggest to downgrade the bug to "important"
>> because it does not affect jmodeltest, the only reverse-dependency at
>> the moment and a missing symlink is not release critical in this case
>> and can be trivially worked around.
> 
> It affects the package: in the moment when a new version is uploaded (my
> it be via backports), it will silently break jmodeltest. It will also
> silently break local usage, even if the new version would be otherwise
> compatible. Both is not acceptable for a release, hence the RC status.
> 
> Best regards
> 
> Ole

In the case of backports you would probably backport jmodeltest as well,
so both could be easily kept in sync. AFAICT both packages seem to work
well together and librowserlauncher-java was only packaged to build
jmodeltest from source. Looking at the issue at hand I still think that
you don't need to choose RC severity but I honestly don't care enough
about it and just wanted to give some feedback. #859005 is probably more
important. I would talk to Andreas about it directly (in case he missed
it somehow).

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#859001: libbrowserlauncher-java: No jar file without version number

[Ole Streicher]

Hi Markus,

Am 29.03.2017 um 15:15 schrieb Markus Koschany:
>> There is no jar without a version number. This makes it impossible to
>> add the jar to the CLASSPATH of other packages,
> 
> This is not true. You can add such jar files to your CLASSPATH.
>> since the file name will change silently with the next version.
> 
> This is true.

This is my point: we cannot rely on it.

>> Therefore, please include also a versionless jar file
>> BrowserLauncher2.jar. This is also requested by Java policy.
> 
> Java Policy is more like Parley from Pirates of the Caribbean and
> incomplete by the way. I suggest to downgrade the bug to "important"
> because it does not affect jmodeltest, the only reverse-dependency at
> the moment and a missing symlink is not release critical in this case
> and can be trivially worked around.

It affects the package: in the moment when a new version is uploaded (my
it be via backports), it will silently break jmodeltest. It will also
silently break local usage, even if the new version would be otherwise
compatible. Both is not acceptable for a release, hence the RC status.

Best regards

Ole

Bug#859005: libbrowserlauncher-java: properties file not included

[Ole Streicher]

Package: libbrowserlauncher-java
Version: 1.3+dfsg-1
Severity: serious

When using the package, I get the following exception:

edu.stanford.ejalbert.exception.BrowserLaunchingInitializingException:
  unable to find config file: 
/edu/stanford/ejalbert/launching/misc/linuxUnixConfig.properties
 at 
edu.stanford.ejalbert.launching.misc.UnixNetscapeBrowserLaunching.initialize(UnixNetscapeBrowserLaunching.java:171)
 at 
edu.stanford.ejalbert.BrowserLauncher.initBrowserLauncher(BrowserLauncher.java:240)
 at edu.stanford.ejalbert.BrowserLauncher.(BrowserLauncher.java:216)
 at edu.stanford.ejalbert.BrowserLauncher.(BrowserLauncher.java:153)
 at 
uk.ac.starlink.topcat.BrowserHelpAction.createBrowserLauncher(BrowserHelpAction.java:62)
[...]

It seems that the properties are not included in the package,
which makes it quite useless:

$ unzip -l /usr/share/java/BrowserLauncher2-1_3.jar |fgrep properties

Please include at least the properties relevant for Debian here.

Cheers

Ole

Bug#859001: libbrowserlauncher-java: No jar file without version number

[Markus Koschany]

Hi Ole,

Am 29.03.2017 um 14:56 schrieb Ole Streicher:
> Package: libbrowserlauncher-java
> Version: 1.3+dfsg-1
> Severity: serious
> 
> The package contents are (mainly):
> 
> /usr/share/java/BrowserLauncher2-1_3-1.3.jar
> /usr/share/java/BrowserLauncher2-1_3.jar -> BrowserLauncher2-1_3-1.3.jar
> 
> There is no jar without a version number. This makes it impossible to
> add the jar to the CLASSPATH of other packages,

This is not true. You can add such jar files to your CLASSPATH.

> since the file name will
> change silently with the next version.

This is true.

> Therefore, please include also a versionless jar file
> BrowserLauncher2.jar. This is also requested by Java policy.

Java Policy is more like Parley from Pirates of the Caribbean and
incomplete by the way. I suggest to downgrade the bug to "important"
because it does not affect jmodeltest, the only reverse-dependency at
the moment and a missing symlink is not release critical in this case
and can be trivially worked around.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#852495: marked as done (mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 13:04:11 +
with message-id 
and subject line Bug#852495: fixed in mariadb-10.1 10.1.22-3
has caused the Debian Bug report #852495,
regarding mariadb-server-10.[01]: purging old mariadb-server shuts down 
mariadb-server and removes init.d links
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.)


-- 
852495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.21-1
Severity: normal

After upgrading to 10.1 from 10.0, I purged the old
mariadb-server-10.0 package, but this had two quite unpleasant
effects: it shut down the server and it removed the init.d links.
This is because:

(a) In the purge|remove|upgrade|... case, stop_server is executed
unconditionally.  It is not obvious to me under what conditions
the server should be stopped, but I would presume that at the very
least, it should only be stopped if the running server is the same
version as the package.  This could be tested (somewhat slowly but
quite safely) by running:

if [ -x /usr/sbin/mysqld ]
then
serverpackage=$(dpkg -S /usr/sbin/mysqld | cut -d: -f1)
if [ $serverpackage = mariadb-server-core-$this_version ]
then
stop_server
sleep 2
fi
fi

The whole server-stopping is probably also in general somewhat
unnecessary, as the server will have been stopped in the prerm
anyway by the dh_installinit snippet.  And this may suffer from
the same issue (though I am less convinced about this), and should
probably be replaced by your stop_server script anyway.

Oh, and for stretch, you don't need to test for the existence of
invoke-rc.d, as it is now in the essential init-system-helpers
package, so you can just do invoke-rc.d mysql stop
unconditionally.

(b) The dh_installinit snippet unconditionally runs update-rc.d mysql
remove.

The only way I can think to fix this is to run dh_installinit with
--no-scripts and then manually insert the necessary snippets into
the postinst/postrm/prerm scripts.  In the postrm script, it
should be protected by the same checks as in (a).

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.22-3

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated mariadb-10.1 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: Tue, 28 Mar 2017 22:59:06 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.22-3
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Ondřej Surý 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plu

Bug#859001: libbrowserlauncher-java: No jar file without version number

[Ole Streicher]

Package: libbrowserlauncher-java
Version: 1.3+dfsg-1
Severity: serious

The package contents are (mainly):

/usr/share/java/BrowserLauncher2-1_3-1.3.jar
/usr/share/java/BrowserLauncher2-1_3.jar -> BrowserLauncher2-1_3-1.3.jar

There is no jar without a version number. This makes it impossible to
add the jar to the CLASSPATH of other packages, since the file name will
change silently with the next version.

Therefore, please include also a versionless jar file
BrowserLauncher2.jar. This is also requested by Java policy.

Best regards

Ole

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

[PICCORO McKAY Lenz]

2017-03-28 23:04 GMT-04:00 James McCoy :

> This discussion is specifically talking about when a 411 status is
> returned, not a 413.
>
the document only cited 411 error as example, could not cover all the cases
due there are more, if u understand how to work http 1.1 vs other http 1.X
and 2

You talked about building subversion locally fixing the behavior, but
> that wouldn't have changed the default value for the
> http-chunked-requests configuration.
>
umm i build only 1.8.0, but 1.8.10, so then ok there a upstream bug here..
but debian could made something for users in transition...


>   Subversion 1.8.1 fixes this issue by detecting automatically whether
>   chunked requests are supported at the set up of a session. This is
>   done by issuing one additional request at the start of the session.
>
> Subversion 1.8.10 is newer than 1.8.1 and therefore has the above
> mentioned fix.
>
as u said, i compiled 1.8.0 not 1.8.10, so these setting now its not work
any more..

also documentation do not mention those problem in svn mail list:

well ist not working, i provide not only one, i provide two urls where u
come and get to test.. once with svn 1.6.12 and once with svn 1.7.0 rc1 and
theres no work

seend to you in private mail:

Bug#856936: marked as done (quagga: libquagga0 contains libraries with different SOVERSIONS)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 11:49:52 +
with message-id 
and subject line Bug#856936: fixed in quagga 1.1.1-2
has caused the Debian Bug report #856936,
regarding quagga: libquagga0 contains libraries with different SOVERSIONS
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.)


-- 
856936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed libquagga-dev contains a
a broken symlink: /usr/lib/x86_64-linux-gnu/libzebra.so -> libzebra.so.0
because libquagga0 ships the following files:

lrwxrwxrwx   1 root root 18 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libfpm_pb.so.0 -> libfpm_pb.so.0.0.0
-rw-r--r--   1 root root   5832 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libfpm_pb.so.0.0.0
lrwxrwxrwx   1 root root 16 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libospf.so.0 -> libospf.so.0.0.0
-rw-r--r--   1 root root 616048 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libospf.so.0.0.0
lrwxrwxrwx   1 root root 25 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libospfapiclient.so.0 -> libospfapiclient.so.0.0.0
-rw-r--r--   1 root root  14176 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libospfapiclient.so.0.0.0
lrwxrwxrwx   1 root root 21 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libquagga_pb.so.0 -> libquagga_pb.so.0.0.0
-rw-r--r--   1 root root   5832 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libquagga_pb.so.0.0.0
lrwxrwxrwx   1 root root 17 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libzebra.so.1 -> libzebra.so.1.0.0
-rw-r--r--   1 root root 443792 Jan 26 23:48 
/usr/lib/x86_64-linux-gnu/libzebra.so.1.0.0

Please split the package to provide only one library per package
(or at least only one SOVERSION per package, if these are supposed
to not change independently).


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 1.1.1-2

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

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

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

Debian distribution maintenance software
pp.
Scott Leggett  (supplier of updated quagga 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, 26 Mar 2017 23:04:32 +1100
Source: quagga
Binary: quagga quagga-core quagga-doc quagga-bgpd quagga-isisd quagga-ospf6d 
quagga-ospfd quagga-pimd quagga-ripd quagga-ripngd
Architecture: source amd64 all
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Scott Leggett 
Changed-By: Scott Leggett 
Description:
 quagga - network routing daemons (metapackage)
 quagga-bgpd - BGP4/BGP4+ routing daemon
 quagga-core - network routing daemons (core abstraction layer)
 quagga-doc - network routing daemons (documentation)
 quagga-isisd - IS-IS routing daemon
 quagga-ospf6d - OSPF6 routing daemon
 quagga-ospfd - OSPF routing daemon
 quagga-pimd - PIM routing daemon
 quagga-ripd - RIPv1 routing daemon
 quagga-ripngd - RIPng routing daemon
Closes: 856936
Changes:
 quagga (1.1.1-2) unstable; urgency=medium
 .
   * Remove libquagga0 and libquagga-dev binary packages (Closes: #856936).
 - Move shared objects into quagga-core, as they are currently intended
   by upstream to be private.
 - Avoid shipping headers and static libraries at all.
 - Upstream plans to ship with a stable API/ABI in future, and these
   changes will be reviewed then.
Checksums-Sha1:
 eba4970432ad815860384597a0de77903c3c59cb 2608 quagga_1.1.1-2.dsc
 3eb23263f757ee3229afffd34f22de7bc4232f79 32084 quagga_1.1.1-2.debian.tar.xz
 a1bc2eb3ce9e9411e0448b433fd4c1f938e9c08c 686462 
quagga-bgpd-dbgsym_1.1.1-2_amd64.deb
 48ba712400a37da9910f626bfdffd228798d39c2 246314 quagga-bgpd_1.1.1-2_amd64.deb
 c433da5e89e207ad901b01b19897a27b9bf1efd6 1375768 
quagga-core-dbgsym_1.1.1-2_amd64.deb
 7efb0794eb9115d1ea43dd8686e57fc122fb098d 531794 quagga-core_1.1.1-2_amd64.deb
 19f557efdc9d109b78721aa6c4508cecdb8063b6 1025920 quagga-doc_1.1.1-2_all.deb
 0cd467dd645463157e261dc6fc71c18854c89957 324530 
quagga-isisd-dbg

Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Ondřej Surý]

Hi Julian (and anybody else reading this bugreport),

I have a testing versions ready here: https://packages.sury.org/mariadb/
 The repository provides updated package for jessie and updated package
for stretch.

I have tested it in a clean system in all ways I could imagine, and it
looks to me it works very well, but I would really appreciate if
somebody else could test this as well.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Sun, Mar 26, 2017, at 15:18, Ondřej Surý wrote:
> Hi Julian,
> 
> I am looking into the jessie->stretch updates and I think we can make
> this simpler without mangling other packages' maintscripts.
> 
> mariadb-10.0 gets updates (via security/release team), so we can just
> update the mariadb-10.0 postinst script for jessie package.
> 
> Same needs to be done for: mysql-5.5 and anything else currently present
> in jessie-backports (mysql-5.6 would be problematic, since it doesn't
> exist in the unstable anymore).
> 
> After stretch release, I think that each package should provide it's
> version specific init scripts. It's easy to add Alias in the systemd
> unit, and I am sure we can think of something similar for sysvrc
> (something like update-alternatives might possibly work).
> 
> Would you be willing to help me clean your patches to not include the
> other packages' maintscripts mangling?
> 
> Cheers,
> -- 
> Ondřej Surý 
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
> Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
> fast DNS(SEC) resolver
> Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
> pečení chleba všeho druhu
> 

Processed: clone bugs ossl 1.1

[Debian Bug Tracking System]

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

> user pkg-openssl-de...@lists.alioth.debian.org
Setting user to pkg-openssl-de...@lists.alioth.debian.org (was 
sebast...@breakpoint.cc).
> # kvirc
> unarchive 828370
Bug #828370 {Done: Andrey Rahmatullin } [src:kvirc] kvirc: 
FTBFS with openssl 1.1.0
Unarchived Bug 828370
> clone 828370 -1
Bug #828370 {Done: Andrey Rahmatullin } [src:kvirc] kvirc: 
FTBFS with openssl 1.1.0
Bug 828370 cloned as bug 858990
827061 was blocked by: 828509 828287 828530 828405 844926 828554 828511 828585 
850881 828514 828615 844948 828534 828294 828252 828371 828445 828591 828243 
828568 828526 828580 828322 828323 828280 828528 828416 844347 828264 828313 
828478 828499 828365 828276 828616 828588 828384 844949 828367 828482 828586 
828454 828374 828592 828271 828291 846908 828578 828253 828476 828544 828401 
828343 828248 828417 828335 828286 828303 828385 828359 841635 828465 828485 
828418 828547 828541 828521 828601 828250 828562 828340 828487 828397 844936 
828315 828610 828505 828442 828470 828297 828256 828284 828406 828378 828377 
828491 828617 828555 828462 828261 828436 828310 828083 828240 850880 828432 
828556 835789 845030 814600 828469 828267 828492 828246 828331 845016 828268 
828536 828238 828237 828501 828389 828523 828395 828552 828516 828459 828269 
828390 828484 828427 828382 828612 828495 828233 828283 828496 844663 828139 
828275 844870 828272 855007 844366 828333 828301 845729 843871 828361 828494 
828285 828489 844234 828239 828277 809271 828452 828587 828429 828438 854470 
828338 828527 828474 844951 828254 828309 828537 828613 828502 828235 828414 
828376 828611 828334 828350 828564 828231 828306 828257 828450 828604 828597 
828270 828082 827068 844534 828574 828543 828619 828598 828295 835585 828455 
828380 828444 828360 828426 828504 828352 828346 829465 828448 828603 844920 
828326 828461 844213 828330 844907 828493 828296 828497 844906 843988 828614 
828488 828290 828383 828362 828519 844947 828561 828244 828539 828545 844975 
828232 828369 828529 828558 835786 828605 828344 828550 828433 828571 828435 
828305 828423 828581 828341 828325 844877 828357 828368 828590 828228 828565 
828421 844945 828304 828229 828480 828533 828358 845106 828379 828347 828259 
828311 828599 828308 837960 828412 828559 828387 828464 828298 828517 844018 
828348 828540 828576 843682 828595 828373 828391 828424 844311 828609 828510 
828500 828258 828404 844916 828570 828551 828467 828317 828337 828512 828575 
828584 828281 828490 828410 828593 828402 828292 828566 828589 844301 828265 
828546 828508 828553 854468 828524 828319 828607 828366 844845 846769 828415 
828249 828411 844664 828328 828472 828618 828466 835800 828398 829452 828351 
828420 828463 835785 844904 844833 822380 828549 828468 828608 828278 828363 
828457 828288 844503 828525 828453 828567 857199 843852 828394 828515 828563 
828577 828439 828349 828437 828293 844345 828242 828355 828241 828388 844706 
844909 828386 828342 828456 835796 828606 828579 828503 844254 828399 808669 
828582 828314 828538 828354 844271 835797 828569 828316 828440 835799 828255 
828518 828279 828274 828393 854257 828473 828251 835794 828364 828321 828535 
828260 828419 828620 828447 828431 828458 828339 828548 835549 828400 828531 
844928 835798 835811 828336 828506 836419 828446 828428 828370 828602 828422 
828596 844931 828234 828320 828302 828127 828396 828409 835790 828318 828375 
828307 828460 844838 828542 828356 828262 854253 844800 835804 828345 850883 
843532 844836 828407 828573 835793 828372 828300 828532 828600 828324 828479 
828443 828230 828282 828289 828434 828403 828381 850882 846113 828263 828430 
828583 828392 828594 828507 844815
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 858990
> archive 828370
Bug #828370 {Done: Andrey Rahmatullin } [src:kvirc] kvirc: 
FTBFS with openssl 1.1.0
archived 828370 to archive/70 (from 828370)
> reopen -1
Bug #858990 {Done: Andrey Rahmatullin } [src:kvirc] kvirc: 
FTBFS with openssl 1.1.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions kvirc/4:4.2.0-3.
> retitle -1 kvirc: Please migrate to openssl1.1 in buster
Bug #858990 [src:kvirc] kvirc: FTBFS with openssl 1.1.0
Changed Bug title to 'kvirc: Please migrate to openssl1.1 in buster' from 
'kvirc: FTBFS with openssl 1.1.0'.
> unblock 827061 with -1
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828434 828523 828526 828514 828507 835799 845030 828286 
828500 828435 828590 828447 828575 828355 828585 844947 828553 828462 828473 
828284 828376 846769 828244 828527 835804 828405 828302 828597 827068 844018 
814600 828256 828595 828540 850880 828568 835811 828436 828528 828489 828278 
828488 828343 828508 843852 844254 828567 828591 828291 828404 828490 836419 
828529 828519 844945 828341 843988 828360 828587 828283 828586 828387 828396 
8283

Bug#852303: marked as done (pywavelets FTBFS on all architectures)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 11:18:50 +
with message-id 
and subject line Bug#852303: fixed in pywavelets 0.5.1-1.1
has caused the Debian Bug report #852303,
regarding pywavelets FTBFS on all 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.)


-- 
852303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pywavelets
Version: 0.5.1-1
Severity: serious

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

...
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_fixperms
# Remove execution flag set by upstream for all files.
find debian/python*-pywt -type f -exec chmod -x {} \;
# Remove execution flag set by upstream also on examples.
find debian/python-pywt-doc -type f -exec chmod -x {} \;
find: 'debian/python-pywt-doc': No such file or directory
debian/rules:32: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
--- End Message ---
--- Begin Message ---
Source: pywavelets
Source-Version: 0.5.1-1.1

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated pywavelets 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: Mon, 27 Mar 2017 07:42:33 +
Source: pywavelets
Binary: python-pywt python3-pywt python-pywt-doc
Architecture: source
Version: 0.5.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Balint Reczey 
Description:
 python-pywt - Python extension implementing of wavelet transformations
 python-pywt-doc - Python extension implementing of wavelet transformations 
(Documen
 python3-pywt - Python3 extension implementing of wavelet transformations
Closes: 852303
Changes:
 pywavelets (0.5.1-1.1) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Non-maintainer upload.
   * Fix clean target to allow dpkg-buildpackage -S succeed
 .
   [ Bhavani Shankar ]
   * Fix dh_fixperms override to work properly with
 architecture-independent-only builds. (Closes: #852303)
Checksums-Sha1:
 ab0840ee9676efeb6c1940ab0c50ad89120217ad 2341 pywavelets_0.5.1-1.1.dsc
 c4a275a20d35e930abcbcb13f949fcb16ecf40d9 7556 
pywavelets_0.5.1-1.1.debian.tar.xz
 3afe6e6758679f38d77574c44f180eeefd6db883 6646 
pywavelets_0.5.1-1.1_source.buildinfo
Checksums-Sha256:
 10b26eb7e2c39ff1d3400302db843b0a71c49809143f13897933459a15f8a426 2341 
pywavelets_0.5.1-1.1.dsc
 d6472f712d08d5c5874ba77ceb823063e165434467d396b9ddf90eeb29cebb4c 7556 
pywavelets_0.5.1-1.1.debian.tar.xz
 be60347b86bdfa94b028a3109a5ac8dec8514a315fae19b7134d13b04fc03e31 6646 
pywavelets_0.5.1-1.1_source.buildinfo
Files:
 1180eda2c9d625be08d49356d61ad4ca 2341 python optional pywavelets_0.5.1-1.1.dsc
 a9eccf82cd10e083e11f7851f08ff795 7556 python optional 
pywavelets_0.5.1-1.1.debian.tar.xz
 1c70c9a42cb94407914a6336f481f22c 6646 python optional 
pywavelets_0.5.1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJY2MhSAAoJEPZk0la0aRp9OX8QAMoejGfbw6SiSQlewDjBr938
6hjDNlGZJ+Fo1k6j0NdUnBuH7P70GgCdQhRE2sfgOc5/+ieyFrZmJ8i5J8YCmdCQ
/JsR/Xbb6eniP6SjSe98DSRPbZW1L8Qcfz5UufUDgSDydFc8TQ23GkL6IxL2neVd
hZ/tp7dY91kBawlL6l6UpymhZgh662gbpptGp4gZcjm108QjI+o07Z7WHtrHSnBN
4SQOSJb7lhF3wbZpjK8F70N/oCDmRdDmi0mHGf2lwjiI+WbQszoCekLbjusX19v4
TSEU5MI+Ag1va6/du0C9jDPcqfpYIUcMdIqqCX1dSUwPhOiEXA3D9ou7d3Ki1xhR
xLPI46OeOSjgDVO0Vyx1WRL2eQzdLGoL/bfjdmCJe7ixBrWZkLNy0LrB7++/g9AF
4SknCBWt+GKbB8gdbKsNA+lWaQO/2xpN3Nku1jtGN9M1OGcz0bKblevsTnDR1aGn
lerQ2E0g1FlLroRqPFfbahQGTvVJCEogTP5lOJDe9BVIKfqeByU5TYkGyrxlpdOq
U7w6XrWeB6Su5uYLxwRaKLJW6lFQCyb1cSqVg0ugiDE4CmxxGw9DXIB+P/b9Yrnx
PP9yCjEaLxbLnvvdLfALr6WCod3dHNelY08gRLVF4fvcmlm+RHhm4qIVuBTmpfYa
sAAcEMvL3Og8BjD7dUWk
=j0wH
-END PGP SIGNATURE End Message ---

Processed: python-tz: FTBFS with tzdata/2017a-1

[Debian Bug Tracking System]

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

> retitle 858133 python-tz: FTBFS with tzdata/2017a-1
Bug #858133 [src:python-tz] python-tz: FTBFS: AssertionError: '+0020+0020' != 
'NET+0020'
Changed Bug title to 'python-tz: FTBFS with tzdata/2017a-1' from 'python-tz: 
FTBFS: AssertionError: '+0020+0020' != 'NET+0020''.
> forwarded 858133 https://bugs.launchpad.net/pytz/+bug/1677177
Bug #858133 [src:python-tz] python-tz: FTBFS with tzdata/2017a-1
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/pytz/+bug/1677177'.
> thanks
Stopping processing here.

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

Bug#832128: freespace2: Bad symlinks /usr/games/fs2_open{,_DEBUG}

[Dmitry Smirnov]

On Wednesday, 29 March 2017 8:42:38 AM AEDT Simon McVittie wrote:
> Please ask the release team to remove it if that's the case.

It is already scheduled for removal because of this bug's severity...


> The
> version in stable is always going to be outdated, given the length of
> our freeze, so it seems odd to remove an otherwise working package;
> but if that's what you want...

I don't insist on removal... As my ability to respond to this issue were 
limited there is only little I could do to ensure that we won't end up with 
broken package in stable. I don't have strong opinion whether to remove or 
keep it.


> I've cancelled my delayed NMU.

OK. So you've decided not to save the package for stable? Fair enough.

Anyway I much appreciate your NMU. Thank you for your care and help.

-- 
Regards,
 Dmitry Smirnov.

---

Platitude: an idea (a) that is admitted to be true by everyone, and (b)
that is not true.
-- H. L. Mencken


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

Bug#858525: marked as pending

[Andreas Beckmann]

On 2017-03-29 03:09, Reinhard Tartler wrote:
> tag 858525 pending
> thanks
> 
> Hello,
> 
> Bug #858525 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
> 
> http://anonscm.debian.org/git/pkg-multimedia/jackd2.git/commit/?id=cbbda8d

That misses Breaks+Replaces for the moved library.


Andreas

Bug#858525: libjack-jackd2-dev: Depend on jackd2

[James Cowgill]

Control: forcemerge -1 715088

Hi,

On 29/03/17 01:23, Reinhard Tartler wrote:
> On 2017-03-28 04:04, Mattia Rizzolo wrote:
>> On Mon, Mar 27, 2017 at 11:22:41PM -0400, Reinhard Tartler wrote:
>>> I think the approach of adding a 'depends' to jackd2 is the simplest.
>>> Moving the shared library to the -dev packages doesn't work, because
>>> /usr/bin/jackd2 and netserver.so link against it.
>>
>> Why not moving the file to libjack-jackd2-0 instead?
> 
> I don't know what I was thinking, this is of course the correct solution.
> Possibly I was confused by a dpkg-shlibdeps failure caused by me missing to
> update the debian/libjack-jackd2-0.shlibs file.
> 
> I'll upload a fixed packages shortly. Thanks for your help!

FYI this is a duplicate of #715088 and also note there is an identical
bug affecting libjack-dev (#715087).

Do we know that libjackserver.so is a public library?

James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#858525: libjack-jackd2-dev: Depend on jackd2

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 715088
Bug #858525 [libjack-jackd2-dev] libjack-jackd2-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libjackserver.so -> libjackserver.so.0.1.0
Bug #858525 [libjack-jackd2-dev] libjack-jackd2-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libjackserver.so -> libjackserver.so.0.1.0
Marked as found in versions jackd2/1.9.9.5+20130622git7de15e7a-1.
Bug #715088 [libjack-jackd2-dev] Broken library symlink detected in 
libjack-jackd2-dev
Severity set to 'serious' from 'normal'
Marked as found in versions jackd2/1.9.10+20150825git1ed50c92~dfsg-4.
Added tag(s) patch and pending.
Merged 715088 858525

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

Processed: Re: Bug#857343: closed by Markus Koschany (Bug#857343: fixed in logback 1:1.1.9-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #857343 {Done: Markus Koschany } [liblogback-java] 
logback: CVE-2017-5929: serialization vulnerability affecting the SocketServer 
and ServerSocketReceiver components
Bug #858914 {Done: Markus Koschany } [liblogback-java] 
CVE-2017-5929: serialization vulnerability in SocketServer and 
ServerSocketReceiver
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions logback/1:1.1.9-2.
No longer marked as fixed in versions logback/1:1.1.9-2.

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

Bug#857343: closed by Markus Koschany (Bug#857343: fixed in logback 1:1.1.9-2)

[Markus Koschany]

Control: reopen -1

Am 29.03.2017 um 08:11 schrieb Fabrice Dagorn:
> Thank you for your upload.
> 
> But i think that the issue is not completely solved, upstream made it in
> several commits (https://github.com/qos-ch/logback/commits/v_1.2.0).
> 
> The comment is not meaningful but this one is related to the
> vulnerability :
> https://github.com/qos-ch/logback/commit/979b042cb1f0b4c1e5869ccc8912e68c39f769f9

Hi,

I am not sure because they have also included a lot of cosmetic changes
but there might be even more relevant commits hence I have asked for a
clarification from upstream. [1]

I keep this bug report open until we know more about it.

Regards,

Markus

[1] http://mailman.qos.ch/pipermail/logback-user/2017-March/004875.html



signature.asc
Description: OpenPGP digital signature

Bug#832128: freespace2: Bad symlinks /usr/games/fs2_open{,_DEBUG}

[Simon McVittie]

On Wed, 29 Mar 2017 at 10:22:49 +1100, Dmitry Smirnov wrote:
> 3.7.2 is already obsolete so I'd rather drop it from Stretch.

Please ask the release team to remove it if that's the case. The
version in stable is always going to be outdated, given the length of
our freeze, so it seems odd to remove an otherwise working package;
but if that's what you want...

I've cancelled my delayed NMU. Please try building the updated package
as though it was a binNMU to confirm that it doesn't have this bug,
something like this:

sbuild --make-binNMU="Test" -m"Not for upload " -d 
unstable freespace2_*.dsc

Thanks,
S

Bug#858948: marked as done (python-ginga: Drop obsolete recommends on pywebkitgtk)

[Debian Bug Tracking System]

Your message dated Wed, 29 Mar 2017 07:33:47 +
with message-id 
and subject line Bug#858948: fixed in ginga 2.6.1-2
has caused the Debian Bug report #858948,
regarding python-ginga: Drop obsolete recommends on pywebkitgtk
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.)


-- 
858948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ginga
Version: 2.6.1-1
Severity: serious
Justification: blocks removal of no longer supported packages

python-ginga has an alternate recommends on pywebkitgtk, but
pywebkitgtk has been removed from Debian stretch. (See
https://bugs.debian.org/790218 ).

I believe this is a Release Critical bug because as long as something
installed still recommends the package, it will stay installed on
users' computers even though the package is no longer built in Debian
or supported.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: ginga
Source-Version: 2.6.1-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated ginga package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 29 Mar 2017 08:51:21 +0200
Source: ginga
Binary: python-ginga python3-ginga ginga
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Description:
 ginga  - Astronomical image viewer
 python-ginga - Astronomical image toolkit for Python 2
 python3-ginga - Astronomical image toolkit for Python 3
Closes: 858948
Changes:
 ginga (2.6.1-2) unstable; urgency=medium
 .
   * Remove python-webkit from Recommends. Closes: #858948
Checksums-Sha1:
 a2ee446ee85c0c5cd721cdbaec6d003f6795e1eb 2447 ginga_2.6.1-2.dsc
 4475810fc178dbaae0c67b722261d8b1002064ba 5100 ginga_2.6.1-2.debian.tar.xz
Checksums-Sha256:
 7f4019307a940945743c46b5aa95b422045d39098eb76816cc8d6f8b0199c568 2447 
ginga_2.6.1-2.dsc
 124f4da79a8f4ce56b2a2f1b36e356374866271d978791f5213370e5a58795e8 5100 
ginga_2.6.1-2.debian.tar.xz
Files:
 bca98e1ed83d39aa17529aef693aea72 2447 python optional ginga_2.6.1-2.dsc
 3833a36eb95aad5db997a59bc93e7682 5100 python optional 
ginga_2.6.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAljbWnwACgkQcRWv0HcQ
3PcyqRAAtdQvdFOh2Wbus/AG5cyNXRDHOJSXjijG5P+l1j+wH7ge9iWMiUU7n01r
Hm4zPplM67OeVDwIEmlRV5PcIf6zkGgQGXFhRJ5xO7B50WK/i/x3djribT3xna9K
LFIVnTdToOs3BfYn5t8GXdhvMUT3PKZzz5iGTyExZSDh4fdtzGhlvPGhQK/cdGVD
RZ+xWF6U9ClT5/Y5g2HDa2kCwry9GjUpqnfLPoV1eyI7f4+i7td/sSSFdsqQNnNa
TP9bdEBaxWQ7M5+gFoDoNRD5oiz/YdDCFX63ClZApqld9viuy4IxGV93HTuJdT0k
k6gJA5tI4FgVVkrc/SC3ZE9ksnmbsNLvrJRgSUqKc0Pw+1cGcaqrxMaV8oa+7lok
vdSUJwWpJFDgchVXAyOmz6LOEuYTJpqXbzwNGrtfGrOEpp85J3KiRbjjdtdOeEl7
K5CKNjNuqykMnrCZ9bz6TJg/7NSlGhXS/mnQA2PtmVgJehWwsogtOvys/lJK69af
F2ZlqKI3ZC0KCiiJbyIAjHdd5WBW+w1JEmeWk5cyK0Q7U+EP0cAqRSvvuhHcxhnv
Yz6C1NQMIrn98QHP+9QfAhF3XwcWklhqmDvUV6xvjF2uzUI+GH0wGggkoaY82leA
3tcQh3TpYdrPV6UHTq/71WtVkGLaWohI+yGRP5+OZhVDVVZWfkk=
=qe4j
-END PGP SIGNATURE End Message ---

Bug#858596: plasma-desktop: screen lock crashes entire session

[Salvo Tomaselli]

Do you think the size of .xsession-error could have triggered this?

I deleted the file on my machine, to have something smaller to send,
and restarted the session to make sure that the file was closed.

After doing this, I can't seem to reproduce the issue, while before it
would happen by keeping my screen locked for less than 1h.

I'll keep trying and see if I manage to make it happen again.

2017-03-24 23:55 GMT+01:00 John Paul Adrian Glaubitz
:
> On 03/24/2017 11:53 PM, John Paul Adrian Glaubitz wrote:
>> OK, so you actually have to wait for hours. I will try to reproduce
>> this. I normally suspend my computer when I lock the machine for a
>> longer period to consume energy.
>
> Btw, could you please provide Xorg.0.log and ${HOME}/.xsession-errors
> with the contents after the crash? The crash should actually show
> up in the logs and it's not easy to debug the problem without any debug
> information to know what actually happened.
>
> 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