Processed: Tags

[Debian Bug Tracking System]

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

> tags 859294 + patch upstream fixed-upstream
Bug #859294 [src:hunspell-dict-ko] hunspell-dict-ko: FTBFS: UnicodeDecodeError: 
'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)
Added tag(s) fixed-upstream, upstream, and patch.
> forwarded 859294 https://github.com/spellcheck-ko/hunspell-dict-ko/issues/26
Bug #859294 [src:hunspell-dict-ko] hunspell-dict-ko: FTBFS: UnicodeDecodeError: 
'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)
Set Bug forwarded-to-address to 
'https://github.com/spellcheck-ko/hunspell-dict-ko/issues/26'.
> thanks
Stopping processing here.

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

Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)

[Changwoo Ryu]

OK I found a way of specifying the encoding of the I/O files.


diff --git a/make-aff-dic.py b/make-aff-dic.py
index 47dff10..98aba41 100644
--- a/make-aff-dic.py
+++ b/make-aff-dic.py
@@ -308,9 +308,9 @@ if __name__ == '__main__':
 dic = Dictionary()
 for filename in infilenames:
 if filename.endswith('.json'):
-dic.load_json(open(filename))
+dic.load_json(open(filename, encoding='utf-8'))
 else:
 print('ERROR: unknown file type: ' + filename)
 sys.exit(1)
 dic.process()
-dic.output(open(afffilename, 'w'), open(dicfilename, 'w'))
+dic.output(open(afffilename, 'w', encoding='utf-8'),
open(dicfilename, 'w', encoding='utf-8'))


2017-04-05 12:44 GMT+09:00 Changwoo Ryu :
> It only fails on a legacy non-Unicode locale, such as "C".
>
> So what is a solution? Specifying a UTF-8 locale and Build-Depending
> on locales-all do not seems to be a right way.

Bug#715066: marked as done (libindicate-gtk3-dev: missing Depends: libindicate-gtk3-3 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Wed, 05 Apr 2017 03:48:52 +
with message-id 
and subject line Bug#715066: fixed in libindicate 0.6.92-4
has caused the Debian Bug report #715066,
regarding libindicate-gtk3-dev: missing Depends: libindicate-gtk3-3 (= 
${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.)


-- 
715066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libindicate-gtk3-dev
Version: 0.6.92-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/libindicate-gtk3.so
-> libindicate-gtk3.so.3.0.3


[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:54:52 EST

Package: libindicate-gtk3-dev
Source: libindicate
Version: 0.6.92-1
Installed-Size: 88
Maintainer: The Ayatana Packagers 
Architecture: amd64
Depends: libindicate-gtk3 (= 0.6.92-1), libindicate-dev (= 0.6.92-1), 
libdbus-glib-1-dev (>= 0.76), libgtk-3-dev (>= 3.0)
Description: library for raising indicators via DBus - GTK bindings development 
files
Homepage: https://launchpad.net/libindicate
Description-md5: db4ba01cea52e73b63c4da26bdc8fc5c
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/libi/libindicate/libindicate-gtk3-dev_0.6.92-1_amd64.deb
Size: 36668
MD5sum: fe8a6dd96f010c259c1d02f6f505cfb0
SHA1: 7c4bab1cad63f20a0e0249cf782f9901cad27509
SHA256: a365796226f0e76b69d9a8b6bd49eca779b57e059b8a5f2c0e64e15ccc612ef5

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 
libindicate-gtk3-dev=0.6.92-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' 'libindicate-gtk3-dev=0.6.92-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/tmp8Um1eu
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp8Um1eu
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp8Um1eu', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp8Um1eu', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp8Um1eu', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']

Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)

[Changwoo Ryu]

It only fails on a legacy non-Unicode locale, such as "C".

So what is a solution? Specifying a UTF-8 locale and Build-Depending
on locales-all do not seems to be a right way.

Bug#857923: marked as done (golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev)

[Debian Bug Tracking System]

Your message dated Wed, 05 Apr 2017 03:03:59 +
with message-id 
and subject line Bug#857923: fixed in golang-go-dbus 1~bzr20150122-2
has caused the Debian Bug report #857923,
regarding golang-go-dbus: build-depend on obsoleted package golang-gocheck-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.)


-- 
857923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-go-dbus
Severity: serious
Version: 1~bzr20150122-1

This package build-depends on (FTBFS-ed) package golang-gocheck-dev. Please 
switch to build depend on golang-gopkg-check.v1-dev.

--
Sincerely,
Boyuan Yang

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: golang-go-dbus
Source-Version: 1~bzr20150122-2

We believe that the bug you reported is fixed in the latest version of
golang-go-dbus, 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.
Roger Shimizu  (supplier of updated golang-go-dbus 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 01 Apr 2017 19:45:08 +0900
Source: golang-go-dbus
Binary: golang-go-dbus-dev
Architecture: source all
Version: 1~bzr20150122-2
Distribution: unstable
Urgency: medium
Maintainer: Sergio Schvezov 
Changed-By: Roger Shimizu 
Description:
 golang-go-dbus-dev - Go interface for D-Bus
Closes: 857923
Changes:
 golang-go-dbus (1~bzr20150122-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Paul Tagliamonte ]
   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
 .
   [ Roger Shimizu ]
   * debian/control:
 - Update Build-Depends on golang-check.v1-dev, instead of
   golang-gocheck-dev which is already non-active upstream.
 - Use cgit URL for Vcs-Browser.
   * debian/patches:
 - Add a patch to use golang-check.v1-dev (Closes: #857923).
Checksums-Sha1:
 6462e5169d8d935ba3bf1224d66e5af2a466bd74 1993 
golang-go-dbus_1~bzr20150122-2.dsc
 f3c354979dba8f86e138ccebc7220ed8d4fbe89b 26657 
golang-go-dbus_1~bzr20150122.orig.tar.gz
 9ed9cdf6be6ef10dfaf4749920c3f2beae1bd8c5 3224 
golang-go-dbus_1~bzr20150122-2.debian.tar.xz
 fee6956fd6ae132243820401a8dd209fd4f92e20 25676 
golang-go-dbus-dev_1~bzr20150122-2_all.deb
 524c0dbc19c3b1947b784d033ece35f8a0dc4200 4917 
golang-go-dbus_1~bzr20150122-2_amd64.buildinfo
Checksums-Sha256:
 945187d34fd98c1c1c59bc1fcf9f6989b5d061bcb2381a52e8a6b86bc084ac85 1993 
golang-go-dbus_1~bzr20150122-2.dsc
 a2644d8a50577bae6cf850908ffa433ed73b9e507be32e925fc1cd8feb8c67c7 26657 
golang-go-dbus_1~bzr20150122.orig.tar.gz
 47d701e6a2f96415115eccf6b1a20b39159ce5eb7105dbef0efc63fd26e9a96d 3224 
golang-go-dbus_1~bzr20150122-2.debian.tar.xz
 2ed0743f21c99018414b6807ccc1962177c4169831e08bfd5ad5de1956728bba 25676 
golang-go-dbus-dev_1~bzr20150122-2_all.deb
 77080dbd42e5e79fbd21c8a586e285ff2519e149f90e45d748e595033748e27c 4917 
golang-go-dbus_1~bzr20150122-2_amd64.buildinfo
Files:
 02e3c764e51dc25f8cdcb3e492a06fd0 1993 devel extra 
golang-go-dbus_1~bzr20150122-2.dsc
 ae85d0afc6d054ad6f7b825c778f31dd 26657 devel extra 
golang-go-dbus_1~bzr20150122.orig.tar.gz
 5f9ab04a9c56201266126a7416c4ed5c 3224 devel extra 
golang-go-dbus_1~bzr20150122-2.debian.tar.xz
 d4894b93829767d2dab122dabeb72968 25676 devel extra 
golang-go-dbus-dev_1~bzr20150122-2_all.deb
 ada533243768497a91737f4cfdd2a274 4917 devel extra 
golang-go-dbus_1~bzr20150122-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY5E7ZAAoJELJMpj9uu+hNzcUQAKwMVjWvSiHSvzbE84uUl2FC
3+bBpMvuLGJVNrt7G0uuSxfcu8txl+gJ+CvDY0Q6802R06SL8qIgWUohdRpP18HX
u0T0QvvhxYYNYqKurBEeJ5rKTE3XM/dUie7ldE5Te4L1Gnw2oU1MHIulFVURxLo3
6uK79X5juyMf/ObzoVg+LmbwVBV3L4UELc/YTVRBhEU9PTmfTaF74ov6ykG8jsla
yigThV0aKS1w8y4gme/BuXKTcIUdeQF3VHubIf373Gr6WoZl9UGGDPRwa4aHgETx
Z9zQ9YORiUEz75IBrMxca7V9fb5QX8P24aKyp0egKsls4r5bdZoMCml6PTPGlClU
WeMAgxGN9L086Nedwv2RUq3DsGKBbFHKzYdb/hqVbkrRifTKDGRk0PpV2/CphFkV

Bug#859588: libgpod-nogtk-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libgpod-nogtk-dev
Version: 0.8.3-8.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch->sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

0m41.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libgpod-nogtk-dev/changelog.Debian.gz (libgpod-nogtk-dev) != 
/usr/share/doc/libgpod4-nogtk/changelog.Debian.gz (libgpod4-nogtk:amd64)
/usr/share/doc/libgpod-nogtk-dev -> libgpod4-nogtk
  /usr/share/doc/libgpod-nogtk-dev/changelog.gz (libgpod-nogtk-dev) != 
/usr/share/doc/libgpod4-nogtk/changelog.gz (libgpod4-nogtk:amd64)
/usr/share/doc/libgpod-nogtk-dev -> libgpod4-nogtk
  /usr/share/doc/libgpod-nogtk-dev/copyright (libgpod-nogtk-dev) != 
/usr/share/doc/libgpod4-nogtk/copyright (libgpod4-nogtk:amd64)
/usr/share/doc/libgpod-nogtk-dev -> libgpod4-nogtk


cheers,

Andreas


libgpod-nogtk-dev_0.8.3-8.1.log.gz
Description: application/gzip

Bug#859587: x2goserver-fmbindings: fails to install: x2goserver-fmbindings.postinst: update-mime-database: not found

[Andreas Beckmann]

Package: x2goserver-fmbindings
Version: 4.0.1.20-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package x2goserver-fmbindings.
  (Reading database ... 
(Reading database ... 8233 files and directories currently installed.)
  Preparing to unpack .../x2goserver-fmbindings_4.0.1.20-1_all.deb ...
  Unpacking x2goserver-fmbindings (4.0.1.20-1) ...
  Processing triggers for desktop-file-utils (0.23-1) ...
  Setting up x2goserver-fmbindings (4.0.1.20-1) ...
  /var/lib/dpkg/info/x2goserver-fmbindings.postinst: 24: 
/var/lib/dpkg/info/x2goserver-fmbindings.postinst: update-mime-database: not 
found
  dpkg: error processing package x2goserver-fmbindings (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   x2goserver-fmbindings


cheers,

Andreas


x2goserver-fmbindings_4.0.1.20-1.log.gz
Description: application/gzip

Bug#859583: marked as done (golang-1.7: ftbfs due to tzdata change)

[Debian Bug Tracking System]

Your message dated Wed, 05 Apr 2017 00:33:58 +
with message-id 
and subject line Bug#859583: fixed in golang-1.7 1.7.4-2
has caused the Debian Bug report #859583,
regarding golang-1.7: ftbfs due to tzdata change
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.)


-- 
859583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-1.7
Version: 1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

tzdata 2017a-1 broke one of the Go tests:

--- FAIL: TestParseInLocation (0.00s)
format_test.go:263: ParseInLocation(Feb 01 2013 AST, Baghdad) = 
2013-02-01 00:00:00 + AST, want 2013-02-01 00:00:00 +0300 +03
FAIL
FAILtime2.550s

It has been fixed upstream so I will backport the patch (and file an unblock
bug once that's built).

Cheers,
mwh

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages golang-1.7 depends on:
ii  golang-1.7-doc  1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
ii  golang-1.7-go   1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
ii  golang-1.7-src  1.7.3-0ubuntu1~ppa0~ubuntu16.04.1

golang-1.7 recommends no packages.

golang-1.7 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: golang-1.7
Source-Version: 1.7.4-2

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

Debian distribution maintenance software
pp.
Michael Hudson-Doyle  (supplier of updated 
golang-1.7 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, 05 Apr 2017 11:53:49 +1200
Source: golang-1.7
Binary: golang-1.7-go golang-1.7-src golang-1.7-doc golang-1.7
Architecture: source
Version: 1.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Michael Hudson-Doyle 
Description:
 golang-1.7 - Go programming language compiler - metapackage
 golang-1.7-doc - Go programming language - documentation
 golang-1.7-go - Go programming language compiler, linker, compiled stdlib
 golang-1.7-src - Go programming language - source files
Closes: 859583
Changes:
 golang-1.7 (1.7.4-2) unstable; urgency=medium
 .
   * Backport CL 37964 for tzdata 2017a changes (Closes: #859583)
Checksums-Sha1:
 51b1bc373ba2cfb63951bc7e4525cd90ba1dc068 2445 golang-1.7_1.7.4-2.dsc
 a3e9ee1f4303266caa417dbdbf13cd6947cf5ea5 30320 golang-1.7_1.7.4-2.debian.tar.xz
Checksums-Sha256:
 b4fcc52c0827d0f6d4afbe9230f5fe2426572ee6054c325b73876332f713c0d4 2445 
golang-1.7_1.7.4-2.dsc
 c9fe8b21c3a82c51bbbe46fccdc1bfe7ab8ae8fa7fc348e9c17d61d106757836 30320 
golang-1.7_1.7.4-2.debian.tar.xz
Files:
 d20a59b53c2a6ad53516ec338b0933ae 2445 devel optional golang-1.7_1.7.4-2.dsc
 c10a39915f8e1273642d2cbebe52cf2a 30320 devel optional 
golang-1.7_1.7.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJY5DilAAoJEBHfQpTMo5iTaOgP/1htAane+1oTduO8E5Qg+k2n
t+gxeWQ9j3nHjxyaCWgTE/pWSzlz4CTx9f9QkRRTEcARW9bGCXyOCcq6/LQgelGu
awK5MfdEg4SlkupdGzvm0nziKRoBurYKIy4KGqHG19x2ISVSy1c4g39TH5M3+7pT
30pHvAXwdT4DP/3CY19BghZdJYjvkxPtG5U2Er0cfNbI7f2PulyV1GP5Pl2qcuPI
JxtVaelgOzP2gjf70PbSKlfbICw1+Inwbo0hziFzfrovCHCWOYqhaktOINAIrZeI
npW7+sBE9EIN3paNwQy40yFHL7U93dgd9rk0+K6JfwPZEjI5TESFPRWAreXaK2qA
JXralGExXtz7/NR0wwVElVp3mB/OLzDtC0WDo1umuDKU9Y745sVutzVlX2sJHTFh
fOoRWie+kWbPCc4oWjtDbbDQv+ZlEdMrgNWxQfTwIzh5dZu/6n3vTAtZTjHFQLY6
KRf0KdZiVyk4/aam2RW2ThE7aVgsx2kxgTL+lx3iMoxLydMJKEif0ionkaDeXE2u

Bug#857923: golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev

[Roger Shimizu]

On Tue, 4 Apr 2017 20:11:36 +0200
Mattia Rizzolo  wrote:

> How is it going the look for a sponsor?
> I can sponsor it if you want (just I do not have commit rights to the
> repo, so you should preper everything - also note that it would be an
> NMU, as for some reason the package is not formally team maintained, I
> wonder if it should be hijacked into the team).

Thanks, Mattia!

I emailed my go-pkg sponsor, but hasn't got a reply.

I already checked in the final releasing commit into mentors branch.
I didn't go for master branch, in case anything missing before this release.

Instead of NMU, maybe QA upload is more proper for this purpose?

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


pgp660GTOBO2G.pgp
Description: PGP signature

Bug#859583: golang-1.7: ftbfs due to tzdata change

[Michael Hudson-Doyle]

Package: golang-1.7
Version: 1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

tzdata 2017a-1 broke one of the Go tests:

--- FAIL: TestParseInLocation (0.00s)
format_test.go:263: ParseInLocation(Feb 01 2013 AST, Baghdad) = 
2013-02-01 00:00:00 + AST, want 2013-02-01 00:00:00 +0300 +03
FAIL
FAILtime2.550s

It has been fixed upstream so I will backport the patch (and file an unblock
bug once that's built).

Cheers,
mwh

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages golang-1.7 depends on:
ii  golang-1.7-doc  1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
ii  golang-1.7-go   1.7.3-0ubuntu1~ppa0~ubuntu16.04.1
ii  golang-1.7-src  1.7.3-0ubuntu1~ppa0~ubuntu16.04.1

golang-1.7 recommends no packages.

golang-1.7 suggests no packages.

-- no debconf information

Bug#859569: marked as done (ublock-origin-doc: missing Breaks+Replaces: xul-ext-ublock-origin (<< 1.11.4+dfsg))

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 23:33:51 +
with message-id 
and subject line Bug#859569: fixed in ublock-origin 1.11.4+dfsg-2
has caused the Debian Bug report #859569,
regarding ublock-origin-doc: missing Breaks+Replaces: xul-ext-ublock-origin (<< 
1.11.4+dfsg)
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.)


-- 
859569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ublock-origin-doc
Version: 1.11.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package ublock-origin-doc.
  Preparing to unpack .../26-ublock-origin-doc_1.11.4+dfsg-1_all.deb ...
  Unpacking ublock-origin-doc (1.11.4+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8kD5uL/26-ublock-origin-doc_1.11.4+dfsg-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/xul-ext-ublock-origin/benchmarks/cpu-usage-overall-20141226.ods.gz',
 which is also in package xul-ext-ublock-origin 1.10.4+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8kD5uL/26-ublock-origin-doc_1.11.4+dfsg-1_all.deb


cheers,

Andreas


xul-ext-ublock-origin=1.10.4+dfsg-1_ublock-origin-doc=1.11.4+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.11.4+dfsg-2

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated ublock-origin 
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, 04 Apr 2017 16:13:19 -0700
Source: ublock-origin
Binary: xul-ext-ublock-origin chromium-ublock-origin ublock-origin-doc
Architecture: all source
Version: 1.11.4+dfsg-2
Distribution: experimental
Urgency: high
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Sean Whitton 
Closes: 859569
Description: 
 chromium-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Chrom
 ublock-origin-doc - general-purpose lightweight ads, malware, trackers blocker 
- docu
 xul-ext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker
Changes:
 ublock-origin (1.11.4+dfsg-2) experimental; urgency=high
 .
   * Add missing Breaks/Replaces of ublock-origin-doc (Closes: #859569).
 Thanks Andreas Beckmann for reporting this error.
Checksums-Sha1: 
 5b2ec804e0d041985edf9b94f17b7c63954cc66d 2347 ublock-origin_1.11.4+dfsg-2.dsc
 7388009baa2ea02858555ecfb8e1d4f50c039963 66632 
ublock-origin_1.11.4+dfsg-2.debian.tar.xz
 e0f8dca11dd3d446325f72924b4c5e5036c4967f 1081376 
chromium-ublock-origin_1.11.4+dfsg-2_all.deb
 603cc2764a57842aee7b7c4faa0bdbb38dd2b220 5760580 
ublock-origin-doc_1.11.4+dfsg-2_all.deb
 06bd3355fc56683d6dad63b1344a542dcaadbab8 7315 
ublock-origin_1.11.4+dfsg-2_amd64.buildinfo
 0a6c2cd053fae6e41b44d8ffe07b8573b21db4a8 1081606 
xul-ext-ublock-origin_1.11.4+dfsg-2_all.deb
Checksums-Sha256: 
 98f4ed7460bc15839b4e6fbebc816829639e197fd56a4d362e58de5482666e59 2347 
ublock-origin_1.11.4+dfsg-2.dsc
 0720b38a748186cc256f26ec64ff0dfcf6c8d992becc1d014d1a6570cb964be3 66632 
ublock-origin_1.11.4+dfsg-2.debian.tar.xz
 48e14e33e8488db5682f28c9c31f9ec1df6f9734d205022674bf607c41af5846 1081376 
chromium-ublock-origin_1.11.4+dfsg-2_all.deb
 ec1c0d6c2596f7caac895e4befec7a1e1d93b5179b32b30d5afeca0743cfab17 5760580 

Bug#858553: [Lazarusdev] [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

[Mattias Gaertner]

Hi Abou,

I will check the fpdoc files.

Mattias

On Tue, 04 Apr 2017 00:27:54 +0200
Abou Al Montacir  wrote:

> Hi Lazarus Developers List,
> 
> Can you please help on this issue?
> fpdoc fails when building Laazarus 1.6.2 documentation. This leads to a 
> serious
> (RC) bug that may lead to remove Lazarus form next Debian release which will 
> be
> really a pity.
> 
> On Sat, 2017-04-01 at 21:45 +0200, Paul Gevers wrote:
> > First shot at debugging from my side.
> > 
> > Because the error says:
> > Exception at 004BDB6C: EDOMError:
> > EDOMError in DOMDocument.CreateElement.
> > 
> > I searched for "DOMDocument.CreateElement". Low and behold, I find
> > something interesting in fpcsrc/packages/fcl-xml/src/dom.pp:
> > 
> > function TDOMDocument.CreateElement(const tagName: DOMString): TDOMElement;
> > begin
> >   if not IsXmlName(tagName) then
> > raise EDOMError.Create(INVALID_CHARACTER_ERR,
> > 'DOMDocument.CreateElement');
> >   TDOMNode(Result) := Alloc(TDOMElement);
> > 
> > Result.Create(Self);
> >   Result.FNSI.QName := FNames.FindOrAdd(DOMPChar(tagName), Length(tagName));
> >   Result.AttachDefaultAttrs;
> > end;
> > 
> > First idea that pops into my mind is: it looks like the source of
> > lazarus has characters that fp-docs can't convert. Apparently an error
> > is raised, but converted by fp-docs into exit code 0.
> > 
> > Interesting to note, is the delta between 2.4.6 and 3.0.0:
> > -  if not IsXmlName(tagName, FXMLVersion = xmlVersion11) then
> > +  if not IsXmlName(tagName) then
> > which was done in this commit:
> > http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision=20422
> > 
> > Sending now as I am about to stop for today, but summary as I currently
> > suspect the situation is:
> > 1) fp-doc fails to create error exit code during error
> > 2) lazarus may have xml files that need updating.
> > 
> > Probably the next time I spend time on this will be to bisect the
> > documentation creation to see which file(s) need fixing -> to
> > potentially solve issue 2 if that is indeed the issue.  
> It looks like the file extctrls.pp or the corresponding xml is not supported 
> by
> the used version of fpdoc.
> ]$fpdoc --content=lcl.xct --package=lcl --descr=../../xml/lcl/lcl.xml --
> input='../../../lcl/extctrls.pp -Fi../../../lcl/include'  --format=html --
> descr=../../xml/lcl/extctrls.xmlFPDoc - Free Pascal Documentation ToolVersion
> 3.0.0 [2017/02/08](c) 2000 - 2003 Areca Systems GmbH / Sebastian Guenther, 
> sg@fr
> eepascal.org(c) 2005 - 2012 various FPC contributors
> Writing 757 pages...Exception at 004BDACC: EDOMError:EDOMError in
> DOMDocument.CreateElement.While with an other page this leads to:
> $fpdoc --content=lcl.xct --package=lcl --descr=../../xml/lcl/lcl.xml --
> input='../../../lcl/interfaces/gtk/gtkwsextctrls.pp -Fi../../../lcl/include'  
> --format=html --descr=../../xml/lcl/interfaces/gtk/gtkwsextctrls.xmlFPDoc - 
> Free
> Pascal Documentation ToolVersion 3.0.0 [2017/02/08](c) 2000 - 2003 Areca 
> Systems
> GmbH / Sebastian Guenther, s...@freepascal.org(c) 2005 - 2012 various FPC
> contributors
> Writing 128 pages...Using built-in CSS fileCreating plus imageCreating minus
> imageDone.Here there are no errors. Just goes fine to end.
> -- 
> Cheers,
> Abou Al Montacir

Bug#859581: quagga-core: fails to upgrade from 'jessie' - trying to overwrite /etc/pam.d/quagga

[Andreas Beckmann]

Package: quagga-core
Version: 1.1.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package quagga-core.
  Preparing to unpack .../quagga-core_1.1.1-2_amd64.deb ...
  addgroup: The group `quaggavty' already exists as a system group. Exiting.
  addgroup: The group `quagga' already exists as a system group. Exiting.
  Adding user `quagga' to group `quaggavty' ...
  Adding user quagga to group quaggavty
  Done.
  Unpacking quagga-core (1.1.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/quagga-core_1.1.1-2_amd64.deb (--unpack):
   trying to overwrite '/etc/pam.d/quagga', which is also in package quagga 
0.99.23.1-1+deb8u3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


quagga=0.99.23.1-1+deb8u3_quagga-core=1.1.1-2.log.gz
Description: application/gzip

Processed: limit source to ublock-origin, tagging 859569

[Debian Bug Tracking System]

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

> limit source ublock-origin
Limiting to bugs with field 'source' containing at least one of 'ublock-origin'
Limit currently set to 'source':'ublock-origin'

> tags 859569 + pending
Bug #859569 [ublock-origin-doc] ublock-origin-doc: missing Breaks+Replaces: 
xul-ext-ublock-origin (<< 1.11.4+dfsg)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#859579: python-cvxopt-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/cvxopt

[Andreas Beckmann]

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

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package python-cvxopt-doc.
  Preparing to unpack .../10-python-cvxopt-doc_1.1.8+dfsg-1_all.deb ...
  Unpacking python-cvxopt-doc (1.1.8+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-zhgQWq/10-python-cvxopt-doc_1.1.8+dfsg-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc-base/cvxopt', which is also in package 
python-cvxopt 1.1.4-1.5
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-zhgQWq/10-python-cvxopt-doc_1.1.8+dfsg-1_all.deb


cheers,

Andreas


python-cvxopt=1.1.4-1.5_python-cvxopt-doc=1.1.8+dfsg-1.log.gz
Description: application/gzip

Bug#859578: libmia-2.4-4: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/mia-2.4/plugins/1d/cmeans/1d-cmeans-kmeans.mia

[Andreas Beckmann]

Package: libmia-2.4-4
Version: 2.4.4-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libmia-2.4-4.
  Preparing to unpack .../libmia-2.4-4_2.4.4-1~exp1_amd64.deb ...
  Unpacking libmia-2.4-4 (2.4.4-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmia-2.4-4_2.4.4-1~exp1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/mia-2.4/plugins/1d/cmeans/1d-cmeans-kmeans.mia', 
which is also in package libmia-2.4-0 2.4.3-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libmia-2.4-4_2.4.4-1~exp1_amd64.deb


cheers,

Andreas


libmia-2.4-0=2.4.3-5_libmia-2.4-4=2.4.4-1~exp1.log.gz
Description: application/gzip

Bug#859559: marked as done (horizon: CVE-2017-7400: XSS in federation mappings UI)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 23:04:06 +
with message-id 
and subject line Bug#859559: fixed in horizon 3:10.0.1-1
has caused the Debian Bug report #859559,
regarding horizon: CVE-2017-7400: XSS in federation mappings UI
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.)


-- 
859559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: horizon
Version: 3:10.0.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.launchpad.net/horizon/+bug/1667086

Hi,

the following vulnerability was published for horizon.

CVE-2017-7400[0]:
| OpenStack Horizon 9.x through 9.1.1, 10.x through 10.0.2, and 11.0.0
| allows remote authenticated administrators to conduct XSS attacks via a
| crafted federation mapping.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7400
[1] https://bugs.launchpad.net/horizon/+bug/1667086

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 3:10.0.1-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated horizon 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, 04 Apr 2017 23:47:20 +0200
Source: horizon
Binary: python-django-horizon openstack-dashboard openstack-dashboard-apache 
horizon-doc
Architecture: source all
Version: 3:10.0.1-1
Distribution: unstable
Urgency: high
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack cloud
 openstack-dashboard-apache - web application to control an OpenStack cloud - 
Apache support
 python-django-horizon - Django module providing web interaction with OpenStack
Closes: 846931 859559
Changes:
 horizon (3:10.0.1-1) unstable; urgency=high
 .
   [ Ivan Udovichenko ]
   * Sync to the latest version from stable/newton.
 .
   [ Thomas Goirand ]
   * CVE-2017-7400: XSS in federation mappings UI. Applied upstream patch:
 Remove dangerous safestring declaration (Closes: #859559).
   * Updated Italian translation of debconf messages (Closes: #846931).
Checksums-Sha1:
 9cba451018f9f0be59c7770d9921aac126985976 4441 horizon_10.0.1-1.dsc
 261e08ba07e0bfdf944522a8300b75dc8844904f 2437216 horizon_10.0.1.orig.tar.xz
 9c8765f9a13ae0898cada0b44cca90c1df3d5beb 26036 horizon_10.0.1-1.debian.tar.xz
 a75cdfd15378d297eeec272203c308707082244a 1382524 horizon-doc_10.0.1-1_all.deb
 23566d345dd9b09e0f0d07e2c387a3c6605140a4 16875 horizon_10.0.1-1_amd64.buildinfo
 d2b3e7b1cf8e335eaf84b13dd9c1967daca9c584 13988 
openstack-dashboard-apache_10.0.1-1_all.deb
 20545adc9a02c0bc2abad97f88b23532b7ddf010 2652626 
openstack-dashboard_10.0.1-1_all.deb
 0ca1634810118ed8a8aa0d017eb750029749931e 2224626 
python-django-horizon_10.0.1-1_all.deb
Checksums-Sha256:
 0f27a46ebed0ef41314bf174f1728f644b0b810b9fa4e38e9420bfc08f4746eb 4441 
horizon_10.0.1-1.dsc
 2e2e00a62968f290e78befb08867d808e869146a73323f824bf07e2a3507694c 2437216 
horizon_10.0.1.orig.tar.xz
 b6876503adce5e84f4dea75883d556d9ea7dda8086fa5c46a992f1841e0ff44c 26036 
horizon_10.0.1-1.debian.tar.xz
 25576ba986a0950ea6026386ec98f9bc000f657baee755b963cee9e28dea6e34 1382524 
horizon-doc_10.0.1-1_all.deb
 4a1e3282a052345e6faac0f2634f3222acbdf8d5f3cd8883e038c36ff4c76f22 16875 
horizon_10.0.1-1_amd64.buildinfo
 a913480908a74da107d3a9bb6ae4ebe2413ffa96ac6484c54496241fa47ea1c1 13988 
openstack-dashboard-apache_10.0.1-1_all.deb
 9ab6bc207920953a1b97b0e7ae9a74abd2aa0f3bc2c106eec5c09c8baea8979a 2652626 
openstack-dashboard_10.0.1-1_all.deb
 

Bug#859577: golang-github-syndtr-goleveldb-dev: file conflict with golang-goleveldb-dev

[Hilko Bengen]

Package: golang-github-syndtr-goleveldb-dev
Version: 0.0~git20170302.0.3c5717c-1
Severity: grave

Dear Maintainer,

while trying to install golang-github-syndtr-goleveldb-dev, I got the
following error message.

Preparing to unpack 
.../golang-github-syndtr-goleveldb-dev_0.0~git20170302.0.3c5717c-1_all.deb ...
Unpacking golang-github-syndtr-goleveldb-dev (0.0~git20170302.0.3c5717c-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-github-syndtr-goleveldb-dev_0.0~git20170302.0.3c5717c-1_all.deb
 (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/github.com/syndtr/goleveldb/leveldb/batch.go', which is 
also in package golang-goleveldb-dev 0+git20160825.6ae1797-2

Looks like a Conflicts/Replaces is needed, you may also want to consider
taking over the golang-goleveldb source package since the two packages
seem to cover the same namespace.

Cheers,
-Hilko

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

Bug#859569: ublock-origin-doc: missing Breaks+Replaces: xul-ext-ublock-origin (<< 1.11.4+dfsg)

[Andreas Beckmann]

Package: ublock-origin-doc
Version: 1.11.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package ublock-origin-doc.
  Preparing to unpack .../26-ublock-origin-doc_1.11.4+dfsg-1_all.deb ...
  Unpacking ublock-origin-doc (1.11.4+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8kD5uL/26-ublock-origin-doc_1.11.4+dfsg-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/xul-ext-ublock-origin/benchmarks/cpu-usage-overall-20141226.ods.gz',
 which is also in package xul-ext-ublock-origin 1.10.4+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8kD5uL/26-ublock-origin-doc_1.11.4+dfsg-1_all.deb


cheers,

Andreas


xul-ext-ublock-origin=1.10.4+dfsg-1_ublock-origin-doc=1.11.4+dfsg-1.log.gz
Description: application/gzip

Bug#859539: Downloaded sources also fail

[Sergio Costas]

Hi again:

I also tried to download the sources from filezilla.org and install them
(both filezilla and libfilezilla), and also crashes...

-- 
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Bug#859539: filezilla: Filezilla crashes at startup

[Sergio Costas]

Hi John:

This?

raster@rasterhost:~$ gdb filezilla
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from filezilla...Reading symbols from
/usr/lib/debug/.build-id/31/c201bdd8cd0fed8dfd5bb02b38cdfbe4567309.debug...done.
done.
(gdb) r
Starting program: /usr/bin/filezilla
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading locale option from /home/raster/.filezilla/filezilla.xml
[New Thread 0x7fffe8eb5700 (LWP 24494)]
[New Thread 0x7fffe3fff700 (LWP 24496)]
[New Thread 0x7fffe2f27700 (LWP 24497)]
[New Thread 0x7fffe2726700 (LWP 24498)]
[New Thread 0x7fffe1f25700 (LWP 24499)]
[New Thread 0x7fffe1724700 (LWP 24500)]

Thread 1 "filezilla" received signal SIGSEGV, Segmentation fault.
0x761bd386 in wxGenericTreeCtrl::Expand(wxTreeItemId const&) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
(gdb) bt
#0  0x761bd386 in wxGenericTreeCtrl::Expand(wxTreeItemId const&)
() from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#1  0x761b6a97 in wxGenericTreeCtrl::EnsureVisible(wxTreeItemId
const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#2  0x761bd9bc in wxGenericTreeCtrl::DoSelectItem(wxTreeItemId
const&, bool, bool) () from
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#3  0x761bde09 in wxGenericTreeCtrl::SelectItem(wxTreeItemId
const&, bool) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#4  0x55872acc in wxTreeCtrlEx::SafeSelectItem
(this=0x56304660, item=...) at treectrlex.cpp:50
#5  0x55715a86 in CLocalTreeView::SetDir
(this=this@entry=0x56304660, localDir=...) at LocalTreeView.cpp:333
#6  0x55715c78 in CLocalTreeView::OnStateChange
(this=0x56304660, notification=) at LocalTreeView.cpp:871
#7  0x55841ca5 in CState::NotifyHandlers
(this=this@entry=0x562fcc00,
notification=notification@entry=STATECHANGE_LOCAL_DIR, data=...,
data2=data2@entry=0x0) at state.cpp:638
#8  0x5584913b in CState::SetLocalDir
(this=this@entry=0x562fcc00, dir=..., error=error@entry=0x0,
rememberPreviousSubdir=rememberPreviousSubdir@entry=true) at state.cpp:299
#9  0x55849a02 in CState::SetLocalDir
(this=this@entry=0x562fcc00,
dir=L"/home/raster/workspace/pagina_local/html/", error=error@entry=0x0,
rememberPreviousSubdir=rememberPreviousSubdir@entry=true)
at state.cpp:227
#10 0x55674ae0 in CContextControl::CreateTab
(this=0x56167620) at context_control.cpp:119
#11 0x5572d8a7 in CMainFrame::CMainFrame (this=0x5615de90)
at Mainfrm.cpp:352
#12 0x556aa27f in CFileZillaApp::OnInit (this=0x55d4b530) at
FileZilla.cpp:275
#13 0x756f7c12 in wxEntry(int&, wchar_t**) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#14 0x55625059 in main (argc=,
argv=0x7fffe668) at locale_initializer.cpp:98
(gdb)


El 04/04/17 a las 23:14, John Paul Adrian Glaubitz escribió:
> Control: tags -1 moreinfo
>
> Hi Sergio!
>
> I just tried to reproduce the crash on amd64 but without success.
>
> I added ftp.debian.org as a remote site and added my home directory as the
> local and /debian/ as the remote directories for a bookmark, saved the book-
> mark, connected to ftp.debian.org, then chose the newly generated bookmark
> without any problems.
>
> Could you please install the dbgsym package for filezilla [1],  run filezilla
> within gdb and provide a backtrace.
>
> Thanks,
> Adrian
>
>> [1] https://wiki.debian.org/AutomaticDebugPackages


-- 
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Processed: Re: filezilla: Filezilla crashes at startup

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #859539 [filezilla] filezilla: Filezilla crashes at startup
Added tag(s) moreinfo.

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

Bug#859539: filezilla: Filezilla crashes at startup

[John Paul Adrian Glaubitz]

Control: tags -1 moreinfo

Hi Sergio!

I just tried to reproduce the crash on amd64 but without success.

I added ftp.debian.org as a remote site and added my home directory as the
local and /debian/ as the remote directories for a bookmark, saved the book-
mark, connected to ftp.debian.org, then chose the newly generated bookmark
without any problems.

Could you please install the dbgsym package for filezilla [1],  run filezilla
within gdb and provide a backtrace.

Thanks,
Adrian

> [1] https://wiki.debian.org/AutomaticDebugPackages

-- 
 .''`.  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

Bug#858189: marked as done (execnet: testing/test_xspec.py::TestMakegateway::test_popen_nice FAILED)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 21:03:50 +
with message-id 
and subject line Bug#858189: fixed in execnet 1.4.1-3.1
has caused the Debian Bug report #858189,
regarding execnet: testing/test_xspec.py::TestMakegateway::test_popen_nice 
FAILED
to be marked as done.

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

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


-- 
858189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:execnet
Version: 1.4.1-3
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=pybuild --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/execnet

[... snipped ...]

SKIP [16] /<>/testing/conftest.py:148: no python3.3 found
SKIP [16] /<>/testing/conftest.py:148: no jython found
SKIP [237] /<>/testing/conftest.py:200: could not import 'gevent'
SKIP [52] /usr/lib/python3/dist-packages/_pytest/config.py:1193: no 'gspecs' 
option found
SKIP [1] testing/test_channel.py:344: condition: sys.version>="3.0"
SKIP [16] /<>/testing/conftest.py:148: no python3.2 found
SKIP [16] /<>/testing/conftest.py:148: no pypy found
SKIP [16] /<>/testing/conftest.py:148: no python2.6 found
SKIP [237] /<>/testing/conftest.py:200: could not import 'eventlet'

=== FAILURES ===
___ TestPopenGateway.test_waitclose_on_remote_killed ___

self = 
makegateway = >

def test_waitclose_on_remote_killed(self, makegateway):
gw = makegateway('popen')
channel = gw.remote_exec("""
import os
import time
channel.send(os.getpid())
time.sleep(100)
""")
remotepid = channel.receive()
py.process.kill(remotepid)
py.test.raises(EOFError, "channel.waitclose(TESTTIMEOUT)")
>   py.test.raises(IOError, channel.send, None)
E   Failed: DID NOT RAISE 

testing/test_gateway.py:251: Failed
 pytest-warning summary 
WI1 /<>/testing/conftest.py:21 'pytest_runtest_setup' hook uses 
deprecated __multicall__ argument
WC1 None pytest_funcarg__specsocket: declaring fixtures using 
"pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 
4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.
WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" 
prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove 
the prefix and use the @pytest.fixture decorator instead.
 Interrupted: stopping after 1 failures 
 1 failed, 222 passed, 607 skipped, 5 xfailed, 3 pytest-warnings in 11.16 
seconds 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python3.5 
-m pytest -v -x -rs testing/
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/execnet/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).

Thanks.
--- End Message ---
--- Begin Message ---
Source: execnet
Source-Version: 1.4.1-3.1

We believe that the bug you reported is fixed in the latest version of
execnet, which is due 

Bug#854494: marked as done (execnet: testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed FAILED/PASSEDSegmentation fault)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 21:03:50 +
with message-id 
and subject line Bug#854494: fixed in execnet 1.4.1-3.1
has caused the Debian Bug report #854494,
regarding execnet: 
testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed 
FAILED/PASSEDSegmentation fault
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.)


-- 
854494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:execnet
Version: 1.4.1-3
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=pybuild --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/execnet

[... snipped ...]

SKIP [16] /<>/testing/conftest.py:148: no python3.3 found
SKIP [16] /<>/testing/conftest.py:148: no jython found
SKIP [237] /<>/testing/conftest.py:200: could not import 'gevent'
SKIP [52] /usr/lib/python3/dist-packages/_pytest/config.py:1193: no 'gspecs' 
option found
SKIP [1] testing/test_channel.py:344: condition: sys.version>="3.0"
SKIP [16] /<>/testing/conftest.py:148: no python3.2 found
SKIP [16] /<>/testing/conftest.py:148: no pypy found
SKIP [16] /<>/testing/conftest.py:148: no python2.6 found
SKIP [237] /<>/testing/conftest.py:200: could not import 'eventlet'

=== FAILURES ===
___ TestPopenGateway.test_waitclose_on_remote_killed ___

self = 
makegateway = >

def test_waitclose_on_remote_killed(self, makegateway):
gw = makegateway('popen')
channel = gw.remote_exec("""
import os
import time
channel.send(os.getpid())
time.sleep(100)
""")
remotepid = channel.receive()
py.process.kill(remotepid)
py.test.raises(EOFError, "channel.waitclose(TESTTIMEOUT)")
>   py.test.raises(IOError, channel.send, None)
E   Failed: DID NOT RAISE 

testing/test_gateway.py:251: Failed
 pytest-warning summary 
WI1 /<>/testing/conftest.py:21 'pytest_runtest_setup' hook uses 
deprecated __multicall__ argument
WC1 None pytest_funcarg__specsocket: declaring fixtures using 
"pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 
4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.
WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" 
prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove 
the prefix and use the @pytest.fixture decorator instead.
 Interrupted: stopping after 1 failures 
 1 failed, 222 passed, 607 skipped, 5 xfailed, 3 pytest-warnings in 11.16 
seconds 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python3.5 
-m pytest -v -x -rs testing/
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/execnet/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).

Thanks.
--- End Message ---
--- Begin Message ---
Source: execnet
Source-Version: 1.4.1-3.1

We believe that the bug you reported is fixed 

Bug#859563: mrboom: Incomplete debian/copyright?

[Chris Lamb]

Source: mrboom
Version: 3.1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Gürkan Myczko 

Hi,

I just ACCEPTed mrboom from NEW but noticed it was missing 
attribution in debian/copyright for at least the embedded
zlib library.

(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#748808: marked as done (libapache2-mod-auth-memcookie: libmemcache seems obsolete, can this package use libmemcached instead?)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:09 +
with message-id 
and subject line Bug#859534: Removed package(s) from unstable
has caused the Debian Bug report #748808,
regarding libapache2-mod-auth-memcookie: libmemcache seems obsolete, can this 
package use libmemcached instead?
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.)


-- 
748808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-auth-memcookie
Version: 1.0.2-8
Severity: normal

See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499480

Since this package seems to be obsolete, it would be good if this
package could depend on another one providing the same functionality but
was actually maintained upstream, and we could remove the obsolete one
from Debian.

I don't know if this is possible, but package maintainers would be in a
good position to decide about this.


Cheers.
--
Manuel
--- End Message ---
--- Begin Message ---
Version: 1.0.2-8+rm

Dear submitter,

as the package libapache2-mod-auth-memcookie has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859534

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#821975: marked as done (cook: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:05:02 +
with message-id 
and subject line Bug#859483: Removed package(s) from unstable
has caused the Debian Bug report #821975,
regarding cook: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
821975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cook
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package cook builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that cook builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to cook at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, cook will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 2.33-2+rm

Dear submitter,

as the package cook has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859483

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#797320: marked as done (cook: FTBFS under some locales (eg. fr_CH.UTF-8))

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:05:02 +
with message-id 
and subject line Bug#859483: Removed package(s) from unstable
has caused the Debian Bug report #797320,
regarding cook: FTBFS under some locales (eg. fr_CH.UTF-8)
to be marked as done.

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

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


-- 
797320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cook
Version: 2.33-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cook fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8"):

  [..]

  CC="gcc" /bin/sh test/01/t0199a.sh
  1c1
  < bar1 bar2
  ---
  > bar1 bar2 bar3
  FAILED test of the ingredients-fingerprint functionality
  Makefile:4714: recipe for target 't0199a' failed
  make[1]: *** [t0199a] Error 1
  make[1]: Leaving directory '/tmp/buildd/cook-2.33'
  debian/rules:18: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/cook_2.33-2.build2.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: samedi 22 août 2015, 09:07:23 (UTC+1400)
I: pbuilder-time-stamp: 1440184043
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
I: user script 
/var/cache/pbuilder/build//10427/tmp/hooks/D01_modify_environment starting
I: Changing hostname to test build reproducibility
I: user script 
/var/cache/pbuilder/build//10427/tmp/hooks/D01_modify_environment finished
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7), bison, groff, gettext, sharutils, ed
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on bison; however:
  Package bison is not installed.
 pbuilder-satisfydepends-dummy depends on groff; however:
  Package groff is not installed.
 pbuilder-satisfydepends-dummy depends on sharutils; however:
  Package sharutils is not installed.
 pbuilder-satisfydepends-dummy depends on ed; however:
  Package ed is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
  bison{a} ed{a} groff{a} libbison-dev{a} libice6{a} libsigsegv2{a} 
  libsm6{a} libx11-6{a} libx11-data{a} libxau6{a} libxaw7{a} libxcb1{a} 
  libxdmcp6{a} libxext6{a} libxmu6{a} libxpm4{a} libxt6{a} m4{a} 
  sharutils{a} x11-common{a} 
0 packages upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 7'045 kB of archives. After unpacking 21.0 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main x11-common all 1:7.7+9 
[287 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libice6 amd64 
2:1.0.9-1+b1 [58.8 kB]
Get: 3 http://ftp.de.debian.org/debian/ 

Bug#850925: marked as done (coq-highschoolgeometry: FTBFS: Syntax error: [tactic:ltac_use_default] expected after [tactic:tactic] (in [vernac:tactic_command]).)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:44 +
with message-id 
and subject line Bug#855564: Removed package(s) from unstable
has caused the Debian Bug report #850925,
regarding coq-highschoolgeometry: FTBFS: Syntax error: 
[tactic:ltac_use_default] expected after [tactic:tactic] (in 
[vernac:tactic_command]).
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.)


-- 
850925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coq-highschoolgeometry
Version: 8.4+20150620-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

coq-highschoolgeometry fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
 dh_auto_build
make -j1
  make[1]: Entering directory '«BUILDDIR»'
  coqdep -c -glob -slash -R . HighSchoolGeometry "complements_cercle.v" > 
"complements_cercle.v.d" || ( RV=$?; rm -f "complements_cercle.v.d"; exit ${RV} 
)
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "complexes_analytique.v" > 
"complexes_analytique.v.d" || ( RV=$?; rm -f "complexes_analytique.v.d"; exit 
${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "complexes_inversion.v" > 
"complexes_inversion.v.d" || ( RV=$?; rm -f "complexes_inversion.v.d"; exit 
${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "contact.v" > "contact.v.d" || 
( RV=$?; rm -f "contact.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "equations_cercles.v" > 
"equations_cercles.v.d" || ( RV=$?; rm -f "equations_cercles.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "inversion.v" > 
"inversion.v.d" || ( RV=$?; rm -f "inversion.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "puissance_cercle.v" > 
"puissance_cercle.v.d" || ( RV=$?; rm -f "puissance_cercle.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "transformations_contact.v" > 
"transformations_contact.v.d" || ( RV=$?; rm -f "transformations_contact.v.d"; 
exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "vecteur.v" > "vecteur.v.d" || 
( RV=$?; rm -f "vecteur.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "trigo.v" > "trigo.v.d" || ( 
RV=$?; rm -f "trigo.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "similitudes_directes.v" > 
"similitudes_directes.v.d" || ( RV=$?; rm -f "similitudes_directes.v.d"; exit 
${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "Rutile.v" > "Rutile.v.d" || ( 
RV=$?; rm -f "Rutile.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "rotation_plane.v" > 
"rotation_plane.v.d" || ( RV=$?; rm -f "rotation_plane.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "representant_unitaire.v" > 
"representant_unitaire.v.d" || ( RV=$?; rm -f "representant_unitaire.v.d"; exit 
${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "repere_plan.v" > 
"repere_plan.v.d" || ( RV=$?; rm -f "repere_plan.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "repere_ortho_plan.v" > 
"repere_ortho_plan.v.d" || ( RV=$?; rm -f "repere_ortho_plan.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "reflexion_plane.v" > 
"reflexion_plane.v.d" || ( RV=$?; rm -f "reflexion_plane.v.d"; exit ${RV} )
  warning: option -slash has no effect and is deprecated.
  coqdep -c -glob -slash -R . HighSchoolGeometry "projection_orthogonale.v" > 
"projection_orthogonale.v.d" || ( RV=$?; rm -f 

Bug#728861: marked as done (ardesia: Does not display UI elements and crashes)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:57 +
with message-id 
and subject line Bug#840959: Removed package(s) from unstable
has caused the Debian Bug report #728861,
regarding ardesia: Does not display UI elements and crashes
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.)


-- 
728861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ardesia
Version: 1.1-1
Severity: important

Hi,

Running ardesia yields a uniform gray screen with the mouse pointer
changes to the "edit pen". Other than that I can perform any action.
Stopping ardesia in this state only works by Ctrl-C in a terminal, upon
which ardesia segfaults.

This is on Debian jessie + GNOME3.

Please let me know if I can contribute more information.


Thanks!


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-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

Versions of packages ardesia depends on:
ii  libatk1.0-0 2.10.0-2
ii  libc6   2.17-93
ii  libcairo-gobject2   1.12.16-2
ii  libcairo2   1.12.16-2
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.4-1
ii  libgsf-1-1141.14.28-1
ii  libgsl0ldbl 1.16+dfsg-1
ii  libgtk-3-0  3.8.4-1
ii  libpango1.0-0   1.32.5-5+b1
ii  libxml2 2.9.1+dfsg1-3
ii  vlc 2.0.8-1+b2
ii  xdg-utils   1.1.0~rc1+git20111210-7

ardesia recommends no packages.

ardesia suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 1.1-2.1+rm

Dear submitter,

as the package ardesia has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/840959

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#811891: marked as done (FTBFS: dereferencing pointer to incomplete type 'struct addrinfo')

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:51 +
with message-id 
and subject line Bug#846801: Removed package(s) from unstable
has caused the Debian Bug report #811891,
regarding FTBFS: dereferencing pointer to incomplete type 'struct addrinfo'
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.)


-- 
811891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmemcache
Version: 1.4.0.rc2-1.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-storage-size

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> memcache.c: In function 'mcm_server_connect':
> memcache.c:2214:43: error: dereferencing pointer to incomplete type 'struct 
> addrinfo'
>if (ms->hostinfo == NULL || ms->hostinfo->ai_addrlen == 0) {
>^~
> 
> In file included from memcache.c:65:0:
> ../include/memcache.h:1071:101: warning: comparison between pointer and 
> integer
>  #define MCM_ERR_MSG(_code, _msg) mcm_err(ctxt, ERR_FLAG, __FUNCTION__, 
> __LINE__, _code, _msg, (_msg != NULL ? strlen(_msg) : 0), 0)
>   
>^
> 
> memcache.c:2217:7: note: in expansion of macro 'MCM_ERR_MSG'
>MCM_ERR_MSG(MCM_ERR_NET_HOST, gai_strerror(i));
>^~~
> 
> memcache.c:2217:37: warning: passing argument 1 of 'strlen' makes pointer 
> from integer without a cast [-Wint-conversion]
>MCM_ERR_MSG(MCM_ERR_NET_HOST, gai_strerror(i));
>  ^
> 
> ../include/memcache.h:1071:118: note: in definition of macro 'MCM_ERR_MSG'
>  #define MCM_ERR_MSG(_code, _msg) mcm_err(ctxt, ERR_FLAG, __FUNCTION__, 
> __LINE__, _code, _msg, (_msg != NULL ? strlen(_msg) : 0), 0)
>   
> ^~~~
> 
> In file included from memcache.c:35:0:
> /usr/include/string.h:394:15: note: expected 'const char *' but argument is 
> of type 'int'
>  extern size_t strlen (const char *__s)
>^~
> 
> In file included from memcache.c:65:0:
> memcache.c:2217:37: warning: passing argument 6 of 'mcm_err' makes pointer 
> from integer without a cast [-Wint-conversion]
>MCM_ERR_MSG(MCM_ERR_NET_HOST, gai_strerror(i));
>  ^
> 
> ../include/memcache.h:1071:89: note: in definition of macro 'MCM_ERR_MSG'
>  #define MCM_ERR_MSG(_code, _msg) mcm_err(ctxt, ERR_FLAG, __FUNCTION__, 
> __LINE__, _code, _msg, (_msg != NULL ? strlen(_msg) : 0), 0)
>   
>^~~~
> 
> memcache.c:773:1: note: expected 'const char *' but argument is of type 'int'
>  mcm_err(const struct memcache_ctxt *ctxt, const u_int32_t flags, const char 
> *funcname, const u_int32_t lineno,
>  ^~~
> 
> memcache.c:2223:66: warning: left-hand operand of comma expression has no 
> effect [-Wunused-value]
>for (i = 0, res = ms->hostinfo; res != NULL; res = res->ai_next, i++) {
>   ^
> 
> memcache.c: In function 'mcm_server_free':
> memcache.c:2457:5: warning: implicit declaration of function 'freeaddrinfo' 
> [-Wimplicit-function-declaration]
>  freeaddrinfo(ms->hostinfo);
>  ^~~~
> 
> memcache.c: In function 'mcm_server_resolve':
> memcache.c:2602:19: error: storage size of 'hints' isn't known
>struct addrinfo hints, *res;
>^
> 
> memcache.c:2618:24: error: invalid application of 'sizeof' to incomplete type 
> 'struct addrinfo'
>bzero(, sizeof(struct addrinfo));
> ^~
> 
> memcache.c:2622:9: warning: implicit declaration of function 'getaddrinfo' 
> [-Wimplicit-function-declaration]
>ret = getaddrinfo(ms->hostname, ms->port, , >hostinfo);
>  ^~~
> 
> memcache.c:2602:19: warning: unused variable 'hints' [-Wunused-variable]
>struct addrinfo hints, *res;
>   

Bug#734837: marked as done (tk8.4: Time to remove from testing)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:39 +
with message-id 
and subject line Bug#858681: Removed package(s) from unstable
has caused the Debian Bug report #734837,
regarding tk8.4: Time to remove from testing
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.)


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

Dear Maintainer,

It's time to remove Tk 8.4 from testing.

-- System Information:
Debian Release: 7.3
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 8.4.20-8+rm

Dear submitter,

as the package tk8.4 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/858681

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#499480: marked as done (libmemcache0 obsolete)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 20:06:51 +
with message-id 
and subject line Bug#846801: Removed package(s) from unstable
has caused the Debian Bug report #499480,
regarding libmemcache0 obsolete
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.)


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

Greetings,

  As stated by the author of memcached, libmemcache0 in debian is no
longer under active development, the newer libmemcached is now the
better alternative in terms of both feature and performace.[1]
  So I think the library should be included ASAP since newer web
applications are using libmemcached exclusively.
  I've already filed a RFP,[2] Sandro sugguests to file a bug here to gain
more attention.

Difei

1. http://tangent.org/552/libmemcached.html
2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499400

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

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

Versions of packages libmemcache0 depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries

libmemcache0 recommends no packages.

Versions of packages libmemcache0 suggests:
ii  memcached 1.2.2-1A high-performance memory object c


--- End Message ---
--- Begin Message ---
Version: 1.4.0.rc2-1.1+rm

Dear submitter,

as the package libmemcache has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/846801

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#859560: xen: CVE-2017-7228: x86: broken check in memory_exchange() permits PV guest breakout (XSA-212)

[Salvatore Bonaccorso]

Source: xen
Version: 4.8.1~pre.2017.01.23-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for xen.

CVE-2017-7228[0]:
| An issue (known as XSA-212) was discovered in Xen, with fixes available
| for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. The earlier XSA-29 fix
| introduced an insufficient check on XENMEM_exchange input, allowing the
| caller to drive hypervisor memory accesses outside of the guest
| provided input/output arrays.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7228
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7228
[1] https://xenbits.xen.org/xsa/advisory-212.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#849932: marked as done (gtk-sharp2-gapi: gapi2-codegen generates fields with void type)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:48:54 +
with message-id 
and subject line Bug#849932: fixed in gtk-sharp2 2.12.40-1.1
has caused the Debian Bug report #849932,
regarding gtk-sharp2-gapi: gapi2-codegen generates fields with void type
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.)


-- 
849932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libindicate
Version: 0.6.92-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
test -x debian/rules
mkdir -p "build"
CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
mkdir -p debian/stamp-makefile-build debian/stamp-makefile-install
mkdir -p debian/stamp-makefile-check
mkdir -p debian/stamp-autotools
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory '/<>'
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
set -e;
if test -e debian/autoreconf.before; then \

[... snipped ...]

&& touch generated-stamp
Name: propertydata Type: GVariant*  in callback 
indicate_listener_get_property_variant_cb
Name: value Type: GVariant**  in callback 
indicate_server_get_indicator_property_group_slot_t
rettype: GVariant* in method GetPropertyVariant in type Indicate.Indicator
Name: value Type: GVariant* in indicate_indicator_set_property_variant  in 
method SetPropertyVariant in type Indicate.Indicator
Name: menu Type: DbusmenuServer* in indicate_server_set_menu  in method SetMenu 
in type Indicate.Server
Name: propertydata Type: GVariant*  in callback GetPropertyVariantCallback
Defaulting GetPropertyTimeCallback param to 'call' scope in method 
Listener.GetPropertyTime
Defaulting GetPropertyIntCallback param to 'call' scope in method 
Listener.GetPropertyInt
Defaulting GetPropertyCallback param to 'call' scope in method 
Listener.GetProperty
Defaulting GetPropertyBoolCallback param to 'call' scope in method 
Listener.GetPropertyBool
Defaulting GetCountCallback param to 'call' scope in method 
ListenerServer.GetCount
Defaulting GetDesktopCallback param to 'call' scope in method 
ListenerServer.GetDesktop
Defaulting GetTypeCallback param to 'call' scope in method 
ListenerServer.GetGType
Defaulting GetMenuCallback param to 'call' scope in method 
ListenerServer.GetMenu
Defaulting GetIconThemeCallback param to 'call' scope in method 
ListenerServer.GetIconTheme

Generation Summary:
  Enums: 1  Structs: 0  Boxed: 0  Opaques: 2  Interfaces: 0  Objects: 3  
Callbacks: 18
  Properties: 0  Signals: 2  Methods: 54  Constructors: 3  Throttled: 5
Total Nodes: 88

/usr/bin/mono-csc  
-keyfile:/<>/./bindings/mono/indicate/indicate.snk 
-nowarn:0169,0612,0618 -unsafe -out:indicate-sharp.dll -target:library 
-r:/usr/lib/pkgconfig/../../lib/cli/pango-sharp-2.0/pango-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/cli/atk-sharp-2.0/atk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/cli/gdk-sharp-2.0/gdk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll 
-r:/usr/lib/pkgconfig/../../lib/cli/glib-sharp-2.0/glib-sharp.dll 
./generated/*.cs AssemblyInfo.cs
./generated/ListenerServer.cs(62,10): error CS0670: Fields cannot have void type
./generated/ListenerServer.cs(62,28): error CS1547: Keyword `void' cannot be 
used in this context
Compilation failed: 2 error(s), 0 warnings
Makefile:854: recipe for target 'indicate-sharp.dll' failed
make[6]: *** [indicate-sharp.dll] Error 1
make[6]: Leaving directory '/<>/build/gtk2/bindings/mono/indicate'
Makefile:546: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory '/<>/build/gtk2/bindings/mono/indicate'
Makefile:426: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/build/gtk2/bindings/mono'
Makefile:428: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/build/gtk2/bindings'
Makefile:489: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>/build/gtk2'
Makefile:421: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving 

Bug#859559: horizon: CVE-2017-7400: XSS in federation mappings UI

[Salvatore Bonaccorso]

Source: horizon
Version: 3:10.0.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.launchpad.net/horizon/+bug/1667086

Hi,

the following vulnerability was published for horizon.

CVE-2017-7400[0]:
| OpenStack Horizon 9.x through 9.1.1, 10.x through 10.0.2, and 11.0.0
| allows remote authenticated administrators to conduct XSS attacks via a
| crafted federation mapping.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7400
[1] https://bugs.launchpad.net/horizon/+bug/1667086

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed (with 1 error): clone ossl 1.1 bugs

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

Bug#859080: marked as done (spyder-memory-profiler: FTBFS: AttributeError: 'NoneType' object has no attribute 'toUtf8')

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:34:31 +
with message-id 
and subject line Bug#859080: fixed in spyder 3.1.3+dfsg1-3
has caused the Debian Bug report #859080,
regarding spyder-memory-profiler: FTBFS: AttributeError: 'NoneType' object has 
no attribute 'toUtf8'
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.)


-- 
859080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-memory-profiler
Version: 0.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

spyder-memory-profiler fails to build from source in unstable/amd64:

  […]

  = test session starts 
==
  platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
  PyQt5 5.7 -- Qt runtime 5.7.1 -- Qt compiled 5.7.1
  rootdir: «BUILDDIR», inifile: 
  plugins: xvfb-1.0.0, qt-2.1.0
  collected 0 items / 1 errors
  
   ERRORS 

   ERROR collecting 
.pybuild/pythonX.Y_3.5/build/spyder_memory_profiler/widgets/tests/test_memoryprofiler.py
 
  /usr/lib/python3/dist-packages/py/_path/local.py:662: in pyimport
  __import__(modname)
  spyder_memory_profiler/__init__.py:12: in 
  from .memoryprofiler import MemoryProfiler
  spyder_memory_profiler/memoryprofiler.py:14: in 
  from spyder.utils.qthelpers import qapplication
  /usr/lib/python3/dist-packages/spyder/utils/qthelpers.py:26: in 
  from spyder.config.gui import get_shortcut
  /usr/lib/python3/dist-packages/spyder/config/gui.py:26: in 
  from spyder.config.main import CONF
  /usr/lib/python3/dist-packages/spyder/config/main.py:22: in 
  from spyder.config.user import UserConfig
  /usr/lib/python3/dist-packages/spyder/config/user.py:26: in 
  from spyder.utils.programs import check_version
  /usr/lib/python3/dist-packages/spyder/utils/programs.py:33: in 
  username = encoding.to_unicode_from_fs(os.environ.get('USER'))
  /usr/lib/python3/dist-packages/spyder/utils/encoding.py:65: in 
to_unicode_from_fs
  string = to_text_string(string.toUtf8(), 'utf-8')
  E   AttributeError: 'NoneType' object has no attribute 'toUtf8'
  !!! Interrupted: 1 errors during collection 

  === 1 error in 0.32 seconds 

  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=2: cd 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


spyder-memory-profiler.0.1.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: spyder
Source-Version: 3.1.3+dfsg1-3

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated spyder 
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, 04 Apr 2017 12:05:55 +0100
Source: spyder
Binary: spyder python-spyderlib python-spyder python-spyderlib-doc spyder-doc 
spyder3 python3-spyderlib python3-spyder spyder-common
Architecture: source
Version: 3.1.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-spyder - Python IDE for scientists (Python 2 modules)
 

Bug#811888: marked as done (aegis: FTBFS with GCC 6: declaration of ... has a different exception specifier)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:28 +
with message-id 
and subject line Bug#859482: Removed package(s) from unstable
has caused the Debian Bug report #811888,
regarding aegis: FTBFS with GCC 6: declaration of ... has a different exception 
specifier
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.)


-- 
811888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aegis
Version: 4.24.3-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-exception-specifier

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> mv libdir.o common/libdir.o
> g++ -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall  -I/usr/include/libxml2 -c 
> common/mem.cc
> In file included from /usr/include/string.h:25:0,
>  from ./common/ac/string.h:26,
>  from common/mem.cc:21:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> 
> common/mem.cc: In function 'void* operator new(size_t)':
> common/mem.cc:246:1: error: declaration of 'void* operator new(size_t) throw 
> (std::bad_alloc)' has a different exception specifier
>  operator new(size_t nbytes)
>  ^~~~
> 
> In file included from common/mem.cc:26:0:
> ./common/mem.h:134:7: note: from previous declaration 'void* operator 
> new(std::size_t)'
>  void *operator new(size_t nbytes) THROW_BAD_ALLOC;
>^~~~
> 
> common/mem.cc: In function 'void* operator new [](size_t)':
> common/mem.cc:266:1: error: declaration of 'void* operator new [](size_t) 
> throw (std::bad_alloc)' has a different exception specifier
>  operator new[](size_t nbytes)
>  ^~~~
> 
> In file included from common/mem.cc:26:0:
> ./common/mem.h:141:7: note: from previous declaration 'void* operator new 
> [](std::size_t)'
>  void *operator new[](size_t nbytes) THROW_BAD_ALLOC;
>^~~~
> 
> Makefile:9040: recipe for target 'common/mem.o' failed
> make[1]: *** [common/mem.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 4.24.3-3+rm

Dear submitter,

as the package aegis has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859482

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#837915: marked as done (aster: FTBFS due to install failures)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:08 +
with message-id 
and subject line Bug#859406: Removed package(s) from unstable
has caused the Debian Bug report #837915,
regarding aster: FTBFS due to install failures
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.)


-- 
837915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aster
Version: 11.5.0+dfsg2-4
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1

Dear Maintainer,

The upload of openmpi (2.0.1-3) to unstable has triggered an
uncoordinated transition (#836917). Unfortunately your package FTBFS due
to install failures:

 stdout: 
--
 It looks like orte_init failed for some reason; your parallel process is
 likely to abort.  There are many reasons that a parallel process can
 fail during orte_init; some of which are due to configuration or
 environment problems.  This failure appears to be an internal failure;
 here's some additional information (which may only be relevant to an
 Open MPI developer):
 
   init pmix failed
   --> Returned value Unreachable (-12) instead of ORTE_SUCCESS
 --
 --
 It looks like orte_init failed for some reason; your parallel process is
 likely to abort.  There are many reasons that a parallel process can
 fail during orte_init; some of which are due to configuration or
 environment problems.  This failure appears to be an internal failure;
 here's some additional information (which may only be relevant to an
 Open MPI developer):
 
   orte_ess_init failed
   --> Returned value Unreachable (-12) instead of ORTE_SUCCESS
 --
 --
 It looks like MPI_INIT failed for some reason; your parallel process is
 likely to abort.  There are many reasons that a parallel process can
 fail during MPI_INIT; some of which are due to configuration or environment
 problems.  This failure appears to be an internal failure; here's some
 additional information (which may only be relevant to an Open MPI
 developer):
 
   ompi_mpi_init: ompi_rte_init failed
   --> Returned "Unreachable" (-12) instead of "Success" (0)
 --
 
 stderr: [babin:16923] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c 
at line 983
 [babin:16924] PMIX ERROR: INVALID-CREDENTIAL in file 
src/server/pmix_server_listener.c at line 540
 [babin:16923] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 
199
 *** An error occurred in MPI_Init
 *** on a NULL communicator
 *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
 ***and potentially your MPI job)
 [babin:16923] Local abort before MPI_INIT completed completed successfully, 
but am not able to aggregate error messages, and not able to guarantee that all 
other processes were killed!
 
 To run manually, set:
 BINDIR="/«BUILDDIR»/aster-11.5.0+dfsg2/debian/tmp/usr/bin"
 PYTHONDIR="/usr/lib/python2.7/dist-packages"
 and copy/paste the command line below:
 Command 
'LD_LIBRARY_PATH="/«BUILDDIR»/aster-11.5.0+dfsg2/debian/tmp/usr/lib:/usr/lib/x86_64-linux-gnu/libfakeroot:/usr/lib64/libfakeroot:/usr/lib32/libfakeroot"
 ${BINDIR}/aster 
/«BUILDDIR»/aster-11.5.0+dfsg2/debian/tmp/usr/lib/aster/Execution/E_SUPERV.py 
-commandes /«BUILDDIR»/aster-11.5.0+dfsg2/build/release/fort.1 -memjeveux 500 
-tpmax 120 --bibpyt /«BUILDDIR»/aster-11.5.0+dfsg2/debian/tmp/usr/lib/aster' 
returned 1
 debian/rules:45: recipe for target 'override_dh_auto_install' failed

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Version: 11.5.0+dfsg2-4+rm

Dear submitter,

as the package aster has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859406

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Bug#800254: marked as done (jbofihe: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:35:56 +
with message-id 
and subject line Bug#859530: Removed package(s) from unstable
has caused the Debian Bug report #800254,
regarding jbofihe: Please migrate a supported debhelper compat level
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.)


-- 
800254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jbofihe
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package jbofihe is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.38-5.1+rm

Dear submitter,

as the package jbofihe has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859530

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#857385: marked as done (jablicator: should it be removed from the archive?)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:37:18 +
with message-id 
and subject line Bug#859347: Removed package(s) from unstable
has caused the Debian Bug report #857385,
regarding jablicator: should it be removed from the archive?
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.)


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

Dear maintainer,

The package doesn't seem to have much popularity these days, with a
popcon of only 20 (recent: 0).

There has been an open RC bug for 1 year, and a patch since January.
Also there is another unacknowledged bug since 2006.

What would you think about removing it from the archive?

-- 
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
--- End Message ---
--- Begin Message ---
Version: 1.0.1+rm

Dear submitter,

as the package jablicator has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859347

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#817467: marked as done (gaim-librvp: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:13 +
with message-id 
and subject line Bug#859522: Removed package(s) from unstable
has caused the Debian Bug report #817467,
regarding gaim-librvp: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gaim-librvp
Severity: important
Usertags: compat-4-removal

Hi,

The package gaim-librvp uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.9.5-3+rm

Dear submitter,

as the package gaim-librvp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859522

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#848436: marked as done (facturlinex2: Should Depends/Recommends the metapackage default-mysql-*)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:01 +
with message-id 
and subject line Bug#859518: Removed package(s) from unstable
has caused the Debian Bug report #848436,
regarding facturlinex2: Should Depends/Recommends the metapackage 
default-mysql-*
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.)


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

User: pkg-mysql-ma...@lists.alioth.debian.org Usertags: default-mysql
default-mysql-depends-recommends 

Hi! 

This package depends (or recommends) direclty on Oracle MySQL. It
should instead depend on the default-mysql-* metapackages, and end up
being installed with the MySQL implementation Debian has chosen to
use, currently MariaDB instead of Oracle MySQL. 

Announcement of the new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change follows this pattern: 

* BEFORE: Depends: mysql-server | virtual-mysql-server 

* AFTER: Depends: default-mysql-server | virtual-mysql-server 

As this is a mass bug filing, the exact solution above might not
apply to directly. For example, if your package depends on some other
Oracle MySQL package, like mysql-client, then use to
default-mysql-client. 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Version: 2.2.2-2+rm

Dear submitter,

as the package facturlinex2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859518

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#817506: marked as done (jablicator: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:37:18 +
with message-id 
and subject line Bug#859347: Removed package(s) from unstable
has caused the Debian Bug report #817506,
regarding jablicator: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jablicator
Severity: important
Usertags: compat-4-removal

Hi,

The package jablicator uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.0.1+rm

Dear submitter,

as the package jablicator has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859347

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#799313: marked as done (jbofihe: FTBFS under some locales (eg. fr_CH.UTF-8))

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:35:56 +
with message-id 
and subject line Bug#859530: Removed package(s) from unstable
has caused the Debian Bug report #799313,
regarding jbofihe: FTBFS under some locales (eg. fr_CH.UTF-8)
to be marked as done.

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

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


-- 
799313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jbofihe
Version: 0.38-5.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

jbofihe fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8"). Not immediately clear why as
CODE_OFFSET looks perfectly fine.

  [..]

  General-purpose automaton builder
  Copyright (C) Richard P. Curnow  2000-2001
  Parsing input...
  Computing epsilon closure...
  Building DFA...
Adding DFA state 260
  Compressing DFA...
Found 20 equivalence classess
  Compressing transition tables...
  Writing outputs...
  gcc -O2  -DHAVE_MMAP=1
  -DDEFAULT_DICTIONARY=\"/usr/lib/jbofihe/smujmaji.dat\" -c bccheck.c
  perl output2table.pl norm < rpc2x_act.output > trctabs.c
  perl output2table.pl full < rpc2x_full_act.output > trcftabs.c
  gcc -O2  -DHAVE_MMAP=1
  -DDEFAULT_DICTIONARY=\"/usr/lib/jbofihe/smujmaji.dat\" -c tracebk.c
  perl output2elide.pl < rpc2x_act.output > elitabs.c
  gcc -O2  -DHAVE_MMAP=1
  -DDEFAULT_DICTIONARY=\"/usr/lib/jbofihe/smujmaji.dat\" -c elide.c
  elide.c: In function ‘can_shift_in_state’:
  elide.c:129:35: error: expected expression before ‘;’ token
 int offset = value - CODE_OFFSET;
 ^
  elide.c: In function ‘elide_trace_reduce’:
  elide.c:594:27: error: expected expression before ‘)’ token
 if ((yyn >= LO_SUBSCRIPT) && (yyn <= HI_SUBSCRIPT)) {
 ^
  Makefile:62: recipe for target 'elide.o' failed
  make[1]: *** [elide.o] Error 1
  make[1]: Leaving directory '/tmp/buildd/jbofihe-0.38'
  debian/rules:22: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2
  dpkg-buildpackage: erreur: debian/rules build a produit une erreur de
  sortie de type 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/jbofihe_0.38-5.1.build2.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Version: 0.38-5.1+rm

Dear submitter,

as the package jbofihe has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859530

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#807966: marked as done (drift: FTBFS with ghc 7.10)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:18 +
with message-id 
and subject line Bug#859484: Removed package(s) from unstable
has caused the Debian Bug report #807966,
regarding drift: FTBFS with ghc 7.10
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.)


-- 
807966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drift
Version: 2.2.3-2.3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

drift currently fails to build from source with GHC 7.10 due to an unresolved
System.Time reference. A build dependency on libghc-old-time-dev is probably
necessary here, but adding that just exposes more issues.

Here's a pastebin of the log, done in an amd64 unstable pbuilder:
http://paste.ubuntu.com/14013137/

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-19-generic (SMP w/1 CPU core)
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)
--- End Message ---
--- Begin Message ---
Version: 2.2.3-2.3+rm

Dear submitter,

as the package drift has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859484

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#816994: marked as done (aegis: FTBFS in stretch, build dependencies not in stretch)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:36:28 +
with message-id 
and subject line Bug#859482: Removed package(s) from unstable
has caused the Debian Bug report #816994,
regarding aegis: FTBFS in stretch, build dependencies not in stretch
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.)


-- 
816994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aegis
Version: 4.24.3-3
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.

But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.


[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-kSYTkY/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 7), bison, zlib1g-dev, groff, gettext, 
uuid-dev, libcurl4-gnutls-dev, perl, libmagic-dev, gawk, cdbs (>= 0.4.23-1.1), 
rcs, ed, patchutils (>= 0.2.25), libxml2-dev, libbz2-dev, bzip2, po-debconf, 
cook, fhist, subversion, cvs, cssc, flex
Filtered Build-Depends: debhelper (>= 7), bison, zlib1g-dev, groff, gettext, 
uuid-dev, libcurl4-gnutls-dev, perl, libmagic-dev, gawk, cdbs (>= 0.4.23-1.1), 
rcs, ed, patchutils (>= 0.2.25), libxml2-dev, libbz2-dev, bzip2, po-debconf, 
cook, fhist, subversion, cvs, cssc, flex
dpkg-deb: building package 'sbuild-build-depends-aegis-dummy' in 
'/<>/resolver-T87lQk/apt_archive/sbuild-build-depends-aegis-dummy.deb'.
OK
Get:1 file:/<>/resolver-T87lQk/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-T87lQk/apt_archive ./ InRelease
Get:2 file:/<>/resolver-T87lQk/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-T87lQk/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-T87lQk/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-T87lQk/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-T87lQk/apt_archive ./ Sources [352 B]
Get:5 file:/<>/resolver-T87lQk/apt_archive ./ Packages [658 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install aegis build dependencies (apt-based resolver)|
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-aegis-dummy : Depends: cook but it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed
Reading package lists...
Building dependency 

Bug#815605: marked as done (kon2: Removal dh_undocumented debhelper command)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 19:37:11 +
with message-id 
and subject line Bug#859532: Removed package(s) from unstable
has caused the Debian Bug report #815605,
regarding kon2: Removal dh_undocumented debhelper command
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.)


-- 
815605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kon2
Severity: important
Tags: sid stretch
Usertags: dh_undocumented-removal

Hi,

The package kon2 is one of less than 10 packages still using
dh_undocumented according to lintian.  This command was obsoleted in
2003 and has since then done nothing but print a warning.

 * Please remove all remaining calls to dh_undocumented at your
   earliest convenience.

 * I will remove dh_undocumented from debhelper in the first upload
   after 9th of March.



If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   in Stretch.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * If your package uses dh_desktop, please remove all calls to it
   from the rules files.  Like dh_undocumented, it does not do
   anything except warning about its deprecation.

 * If your package does *not* have a debian/compat, please add one with
   the correct compat level.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.3.9b-20+rm

Dear submitter,

as the package kon2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859532

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#859539: filezilla: Filezilla crashes at startup

[Sergio Costas]

Package: filezilla
Version: 3.24.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After updating my Debian SID system, filezilla stopped working. Launching it
from a command line returns a segmentation fault almost inmediatly:

raster@rasterhost:~/.config$ filezilla
Reading locale option from /home/raster/.filezilla/filezilla.xml
Segmentation fault
raster@rasterhost:~/.config$

Removing the file .filezilla/filezilla.xml allows to launch it, but as soon as
a server is chosen in the bookmarks, it crashes again.

raster@rasterhost:~$ filezilla
Reading locale option from /home/raster/.filezilla/filezilla.xml
wxD-Bus: Signal from /org/freedesktop/DBus, member NameAcquired
wxD-Bus: Reply with serial 2
wxD-Bus: Reply to RegisterClient, our object path is
/org/gnome/SessionManager/Client33

** (filezilla:18791): WARNING **: invalid source position for vertical
gradient

** (filezilla:18791): WARNING **: invalid source position for vertical
gradient

** (filezilla:18791): WARNING **: invalid source position for vertical
gradient

** (filezilla:18791): WARNING **: invalid source position for vertical
gradient
wxD-Bus: CPowerManagementInhibitor: Requesting busy
Segmentation fault
raster@rasterhost:~$




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

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

Versions of packages filezilla depends on:
ii  filezilla-common 3.24.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.16-1
ii  libfilezilla00.9.0-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3+b2
ii  libgcc1  1:6.3.0-11
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5
ii  libgtk2.0-0  2.24.31-2
ii  libnettle6   3.3-1+b1
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpangoft2-1.0-01.40.4-1
ii  libpugixml1v51.7-2
ii  libsqlite3-0 3.16.2-3
ii  libstdc++6   6.3.0-11
ii  libwxbase3.0-0v5 3.0.2+dfsg-3
ii  libwxgtk3.0-0v5  3.0.2+dfsg-3

Versions of packages filezilla recommends:
ii  xdg-utils  1.1.1-1

filezilla suggests no packages.

-- no debconf information

Bug#858553: [Pkg-pascal-devel] Bug#858553: Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

[Paul Gevers]

Hi all,

On 04-04-17 00:27, Abou Al Montacir wrote:
> Can you please help on this issue?
> It looks like the file extctrls.pp or the corresponding xml is not
> supported by the used version of fpdoc.

In our version, on line 1400 (or line 1437 in current HEAD version¹) we
have the following:
  TCtrlBands = class (specialize TFPGObjectList)

It is the < and > that cause the issue. My assumption is that when
converted to xml, they need to be escaped/converted to  and .

If I remove either (not necessary both) of them, the fpdoc conversion of
extctrls.pp succeeds.

Paul

¹
http://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/lcl/extctrls.pp?view=markup=53634=lazarus



signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> # it's a regression of the unstable package, testing's fine.
> notfound 859514 4.09-2
Bug #859514 [manpages] file conflict with keyutils
Bug #859536 [manpages] manpages-4.10-1: Overwrite file from other package
No longer marked as found in versions manpages/4.09-2.
No longer marked as found in versions manpages/4.09-2.
> --
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 859536 manpages
Bug #859536 [manpages-4.10-1] manpages-4.10-1: Overwrite file from other package
Warning: Unknown package 'manpages-4.10-1'
Bug reassigned from package 'manpages-4.10-1' to 'manpages'.
No longer marked as found in versions 4.10-1.
Ignoring request to alter fixed versions of bug #859536 to the same values 
previously set
> forcemerge 859514 859536
Bug #859514 [manpages] file conflict with keyutils
Bug #859536 [manpages] manpages-4.10-1: Overwrite file from other package
Added indication that 859536 affects keyutils
Marked as found in versions manpages/4.09-2 and manpages/4.10-1.
Merged 859514 859536
> --
Stopping processing here.

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

Bug#859472: Upstream issue

[Filip Pytloun]

Tests are also failing upstream: https://travis-ci.org/pimutils/khal
But didn't fail on my workstation :-/
Reported upstream and waiting for fix.


signature.asc
Description: PGP signature

Processed: tagging 857238

[Debian Bug Tracking System]

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

> tags 857238 + fixed-upstream
Bug #857238 [libwww-dict-leo-org-perl] /usr/bin/leo: throws HTTP 404 (needs 
update to new remote API)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#859536: manpages-4.10-1: Overwrite file from other package

[Michael Rasmussen]

Package: manpages-4.10-1
Version: 4.10-1
Severity: serious
Justification: Policy 7.6.1

Dear Maintainer,

Installing package will overwrite files from another package:
dpkg: error processing archive /var/cache/apt/archives/manpages_4.10-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man7/keyrings.7.gz', which is also in 
package keyutils 1.5.9-9
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/manpages_4.10-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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



This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

Processed: Re: your mail

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #859019 {Done: Julian Taylor } 
[python-numpy] new bugfix release available
Severity set to 'normal' from 'serious'

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

Bug#859019: your mail

[Ivo De Decker]

Control: severity -1 normal

Hi,

On Sat, Apr 01, 2017 at 01:18:08PM +0200, Julian Taylor wrote:
> severity 859019 serious
> thanks
> 
> the issues are very much RC, stretch should not be stuck with a .0 numpy
> release.

Just stating that won't make it RC. If you want your upload unblocked, the
proper way to do that is to file an unblock request with an explanation, not
by filing random RC bugs for stuff that is not RC. Do not inflate the severity
of this bug again.

Cheers,

Ivo

Bug#857923: golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev

[Mattia Rizzolo]

Sergio: a question: given that the package lives in the pkg-go namespace
(I mean, the git repository does), why isn't the pkg-go team set as
maintainer of it?

On Sat, Apr 01, 2017 at 07:57:21PM +0900, Roger Shimizu wrote:
> Control: tags -1 +patch pending
> 
> Just pushed a fix to git repo:
>   
> https://anonscm.debian.org/cgit/pkg-go/packages/golang-go-dbus.git/commit/?id=7dd07f6
> 
> I'll ask sponsor to upload later.

How is it going the look for a sponsor?
I can sponsor it if you want (just I do not have commit rights to the
repo, so you should preper everything - also note that it would be an
NMU, as for some reason the package is not formally team maintained, I
wonder if it should be hijacked into the team).

-- 
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#857994: marked as done (qtwebchannel-opensource-src: Please do not depend on npm)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 18:05:00 +
with message-id 
and subject line Bug#857994: fixed in qtwebchannel-opensource-src 5.7.1-2
has caused the Debian Bug report #857994,
regarding qtwebchannel-opensource-src: Please do not depend on npm
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.)


-- 
857994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebchannel-opensource-src
Severity: important

I intend to remove npm from testing.

Would qtwebchannel5-examples be broken without npm ?

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: qtwebchannel-opensource-src
Source-Version: 5.7.1-2

We believe that the bug you reported is fixed in the latest version of
qtwebchannel-opensource-src, 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.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtwebchannel-opensource-src 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, 04 Apr 2017 14:33:24 -0300
Source: qtwebchannel-opensource-src
Binary: qtwebchannel5-doc qtwebchannel5-doc-html libqt5webchannel5-dev 
qtwebchannel5-examples libqt5webchannel5 qml-module-qtwebchannel
Architecture: source
Version: 5.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5webchannel5 - Web communication library for Qt
 libqt5webchannel5-dev - Web communication library for Qt - development files
 qml-module-qtwebchannel - Web communication library for Qt - QML module
 qtwebchannel5-doc - Web communication library for Qt - Documentation
 qtwebchannel5-doc-html - Web communication library for Qt - HTML Documentation
 qtwebchannel5-examples - Web communication library for Qt - Examples
Closes: 857994
Changes:
 qtwebchannel-opensource-src (5.7.1-2) unstable; urgency=medium
 .
   [ Lisandro Damián Nicanor Pérez Meyer ]
   * Team upload.
   * Do not depend upon npm (Closes: #857994). It is used just by some examples
 and currently not on all archs, so while removing it is not the ideal
 solution is the only one we have available right now.
Checksums-Sha1:
 d59f5c4fd13eda0045c75811af5f7035ae27cf52 2890 
qtwebchannel-opensource-src_5.7.1-2.dsc
 1702fcb7b0372132c500eb30c4e60876a81794ba 7160 
qtwebchannel-opensource-src_5.7.1-2.debian.tar.xz
Checksums-Sha256:
 b07a209aee3c134959659d001268644fbb18244e8acd827922b77e8e41ceba22 2890 
qtwebchannel-opensource-src_5.7.1-2.dsc
 c88996bf82ef07f925233d8c8c1b8c188d5da391583301f799ebcab15afdc6da 7160 
qtwebchannel-opensource-src_5.7.1-2.debian.tar.xz
Files:
 3e88081005b47c59cb5a44ce9a1b0a9d 2890 libs optional 
qtwebchannel-opensource-src_5.7.1-2.dsc
 f5fc0856956a5eb91d36e30e9adfc52e 7160 libs optional 
qtwebchannel-opensource-src_5.7.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAljj2YAUHGxpc2FuZHJv
QGRlYmlhbi5vcmcACgkQq2RfQGKGp9D+5g/8CatNoQi/vc9iWWxkiASfCGmyYpBf
iDjfZx7i0SlGZmuszB4f0GGy1aCsJlRkZGZJgjodAW0vGPCT6J9jmIJyxVfUOnvX
uXTm91E3R25t5SANksJpWI9XQHZFGVYgd0by01m/V3B7FQX9YHV0Yk3TsdYQRu3R
T471NlFG00BDE8PkhrBrEeb0Sy9fdjHfoSf92j15fe4BnaYRyAalh/COPb/0gxoJ
nACl3tVPMyPGvIHdK1WN6K4CdfjtiwuWNsVKJ7127FVBalzIFcJ/Iv3iUTC8l8hu
Iz5wMgtBQZ0glM6FtyERv5hiN6WUD5F+pZwgh77iResy7Yk/34NTjnibl91KiHZY
FUIaOz6khQCvNJKuiVpfBBlhEULFUGpwVGqu+vyoH9/R7WSVvISYAwrpBMKr//sL
qa5dy93OjAJRylYhBmEayjz5FMxs4ue9wJhpsnwRxXvcEH+qoeWLpRhyHknMn1vT
fnVDnnsIHQEnAPEYUNy6BB1PDkMNdNPhooLbs67CctWxvHiQB1SKye9DuWjHT4eG
q3sZ3IRTHxerL90daLrYraBwMGLB4Wcn6ffn3ExRO+VKhkpoWPzD1KLbi7j5gIIW

Bug#859514: file conflict with keyutils

[Alf Gaida]

There are some more conflicting files:
* man/keyrings.7
* man/persistent-keyring.7
* man/process-keyring.7
* man/session-keyring.7
* man/thread-keyring.7
* man/user-keyring.7
* man/user-session-keyring.7

All man-pages conflicting with the current keyutils.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#857994: Please don't remove npm from Stretch

[Debian Bug Tracking System]

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

> tag 857994 pending
Bug #857994 [src:qtwebchannel-opensource-src] qtwebchannel-opensource-src: 
Please do not depend on npm
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#857994: Please don't remove npm from Stretch

[Lisandro Damián Nicanor Pérez Meyer]

tag 857994 pending
thanks

On martes, 4 de abril de 2017 12:27:00 -03 Niels Thykier wrote:
[snip] 
> @QT/KDE maintainers: A timely upload for #857994 would greatly be
> appreciated, so we can finish up this soon.

It seems the people listed in Uploaders are kind of MIA and I was busy with 
non-Debian stuff (actually I'm still quite busy).

I have just uploaded a fixed version just removing the dependency. It's an 
example so it should not be a significant issue. Not ideal but good enough for 
now.


-- 
She got her good looks from her father. He's a plastic surgeon.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#857238: fixed in 2.00

[Roland Hieber]

For reference, this is fixed in version 2.00 at CPAN which got uploaded
yesterday.

 - Roland

Bug#859019: marked as done (new bugfix release available)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 17:36:44 +
with message-id 
and subject line Bug#859019: fixed in python-numpy 1:1.12.1-1
has caused the Debian Bug report #859019,
regarding new bugfix release available
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.)


-- 
859019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.12.1-1

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

Debian distribution maintenance software
pp.
Julian Taylor  (supplier of updated python-numpy 
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, 04 Apr 2017 15:08:27 +0200
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source
Version: 1:1.12.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Julian Taylor 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 859019
Changes:
 python-numpy (1:1.12.1-1) unstable; urgency=medium
 .
   * New upstream bugfix release (Closes: #859019)
   * 
debian/patches/0007-BUG-fix-wrong-masked-median-for-some-special-cases.patch
 dropped, applied upstream
Checksums-Sha1:
 8291660899b942238907cc688a21d6cc4b0612cf 2863 python-numpy_1.12.1-1.dsc
 582568e43126d9e1f57755caa1bb774e3967b960 4344068 
python-numpy_1.12.1.orig.tar.gz
 f92842786c035d1cd4ba3abde5856f02299bd567 140688 

Processed: user release.debian....@packages.debian.org, usertagging 766397, tagging 766397

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 766397 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 766397 + stretch-ignore
Bug #766397 [emacs24] emacs/gnus: Uses s_client to for SSL.
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Bug#859478: offlineimap: 'maxage' comments are wrong, offlineimap DELETES your mails

[Cyril Brulebois]

Ilias Tsitsimpis  (2017-04-04):
> Control: fixed -1 6.6.0~rc3+dfsg1-1
> 
> Hi Cyril,
> 
> On Tue, Apr 04, 2017 at 01:28AM, Cyril Brulebois wrote:
> > Looking at the code, it seems “is that older than maxage?” is
> > implemented by looking at the timestamp in the filename for local
> > mails, which happens to be October 2016 for a mail received in 2015!
> 
> Your analysis is correct. Here is a blog post which explains in depth
> the above bug:
> 
> http://www.offlineimap.org/devel/2015/04/14/why-we-changed-maxage.html

Yes I've read this.

> This should be fixed in newer versions of OfflineIMAP. Could you please
> give it a try?

Well, trying out new versions is something I can do, but it really doesn't
help with the fact that offlineimap in stable is responsible for data loss.

> You may also be interested in the 'sync_deletes' feature, introduced in
> version 7.0.6+dfsg1-1. Copying from the docs:
> 
> This option stands in the [Repository RemoteExample] section.
> 
> Propagate deletions from remote to local. Messages deleted in this 
> repository
> won't get deleted on the local repository if set to "no". Default is yes.

This looks like an ideal solution to my initial problem, thanks!


KiBi.


signature.asc
Description: Digital signature

Bug#859529: should we RM imview-doc ?

[Mattia Rizzolo]

Source: imview-doc
Version: 1.0.1-3
Severity: serious
X-Debbugs-cc: debian-scie...@lists.debian.org

should we remove imview-doc ?
It has an outstanding license issue https://bugs.debian.org/708955
and it seems nobody cared about it since 2008.

-- 
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#858133: marked as done (python-tz: FTBFS with tzdata/2017a-1)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 17:05:22 +
with message-id 
and subject line Bug#858133: fixed in python-tz 2016.7-0.3
has caused the Debian Bug report #858133,
regarding python-tz: FTBFS with tzdata/2017a-1
to be marked as done.

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

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


-- 
858133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tz
Version: 2016.7-0.2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

python-tz fails to build from source in unstable/amd64:

  […]

  tzname, str(utc_dt), dt.tzname()
  E   AssertionError: Expected WSDT as tzname for 2011-12-30 11:00:00+00:00. 
Got +14
  _ SamoaInternationalDateLineChange.testTwoHoursBefore 
__
  
  self = 
  
  def testTwoHoursBefore(self):
  self._test_all(
  >   self.transition_time - timedelta(hours=2), self.before
  )
  
  pytz/tests/test_tzinfo.py:302: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  pytz/tests/test_tzinfo.py:292: in _test_all
  self._test_tzname(utc_dt, wanted)
  pytz/tests/test_tzinfo.py:241: in _test_tzname
  tzname, str(utc_dt), dt.tzname()
  E   AssertionError: Expected SDT as tzname for 2011-12-30 08:00:00+00:00. Got 
-10
  __ LocalTestCase.testLocalize 
__
  
  self = 
  
  def testLocalize(self):
  loc_tz = pytz.timezone('Europe/Amsterdam')
  
  loc_time = loc_tz.localize(datetime(1930, 5, 10, 0, 0, 0))
  # Actually +00:19:32, but Python datetime rounds this
  self.assertEqual(loc_time.strftime('%Z%z'), 'AMT+0020')
  
  loc_time = loc_tz.localize(datetime(1930, 5, 20, 0, 0, 0))
  # Actually +00:19:32, but Python datetime rounds this
  self.assertEqual(loc_time.strftime('%Z%z'), 'NST+0120')
  
  loc_time = loc_tz.localize(datetime(1940, 5, 10, 0, 0, 0))
  >   self.assertEqual(loc_time.strftime('%Z%z'), 'NET+0020')
  E   AssertionError: '+0020+0020' != 'NET+0020'
  
  pytz/tests/test_tzinfo.py:614: AssertionError
   38 failed, 196 passed in 2.54 seconds 
=
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
«BUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--before-test=   cp «BUILDDIR»/README.txt {build_dir};   cp -r 
/home/lamby/temp/cdt.20170318181551.yfmWAMyfvQ.db.python-tz/python-tz-2016.7/pytz/tests
 {build_dir}/pytz/ --after-test=rm -rf {build_dir}/README.txt 
{build_dir}/pytz/tests returned exit code 13
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


python-tz.2016.7-0.2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-tz
Source-Version: 2016.7-0.3

We believe that the bug you reported is fixed in the latest version of
python-tz, 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.
Simon McVittie  (supplier of updated python-tz 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, 02 Apr 2017 17:20:24 +0100
Source: python-tz
Binary: python-tz python3-tz
Architecture: source
Version: 2016.7-0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Ubuntu Zope Team 

Changed-By: Simon 

Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

[Andreas Beckmann]

Source: libpfm4
Version: 4.8.0-1
Severity: serious
Tags: upstream
Forwarded: https://sourceforge.net/p/perfmon2/mailman/message/35744830

An unintended abi change between libpfm 4.7 (compatible with libpfm 4.5+git
in stable) and libpfm 4.8 (in stretch/sid) has been reported upstream
(changed a struct member from int to uint64_t, moving offsets of further
members).
A new upstream release 4.9 reverting this change (and implementing a
different solution for its internal needs) is being prepared.


Andreas

Bug#848773: marked as done (fped: FTBFS: ld: cannot find -lfl)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 16:48:54 +
with message-id 
and subject line Bug#846426: fixed in fped 0.1+201210-1.1
has caused the Debian Bug report #846426,
regarding fped: FTBFS: ld: cannot find -lfl
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.)


-- 
846426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fped
Version: 0.1+201210-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/fped-0.1+201210'
> /bin/bash: git: command not found
> /bin/bash: git: command not found
>   CCfped.o
>   CCexpr.o
>   CCcoord.o
>   CCobj.o
>   CCdelete.o
>   CCinst.o
> inst.c: In function 'inst_find_point_selected':
> inst.c:377:32: warning: 'd_min' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
>  if (d != -1 && (!best || d < d_min)) {
>   ~~^~~
>   CCutil.o
>   CCerror.o
>   CCunparse.o
>   CCfile.o
>   CCdump.o
>   CCkicad.o
>   CCpostscript.o
>   CCgnuplot.o
>   CCmeas.o
>   CClayer.o
>   CCoverlap.o
>   CChole.o
>   CCtsort.o
>   CCbitset.o
>   CCcpp.o
>   YACC  y.tab.h
>   LEX   lex.yy.c
>   CClex.yy.o
>   CCy.tab.o
>   GENERATE  icons/point.ppm
>   GENERATE  icons/point.xpm
>   GENERATE  icons/delete.ppm
>   GENERATE  icons/delete.xpm
>   GENERATE  icons/delete_off.ppm
>   GENERATE  icons/delete_off.xpm
>   GENERATE  icons/vec.ppm
>   GENERATE  icons/vec.xpm
>   GENERATE  icons/frame.ppm
>   GENERATE  icons/frame.xpm
>   GENERATE  icons/line.ppm
>   GENERATE  icons/line.xpm
>   GENERATE  icons/rect.ppm
>   GENERATE  icons/rect.xpm
>   GENERATE  icons/pad.ppm
>   GENERATE  icons/pad.xpm
>   GENERATE  icons/rpad.ppm
>   GENERATE  icons/rpad.xpm
>   GENERATE  icons/hole.ppm
>   GENERATE  icons/hole.xpm
>   GENERATE  icons/arc.ppm
>   GENERATE  icons/arc.xpm
>   GENERATE  icons/circ.ppm
>   GENERATE  icons/circ.xpm
>   GENERATE  icons/meas.ppm
>   GENERATE  icons/meas.xpm
>   GENERATE  icons/meas_x.ppm
>   GENERATE  icons/meas_x.xpm
>   GENERATE  icons/meas_y.ppm
>   GENERATE  icons/meas_y.xpm
>   GENERATE  icons/stuff.ppm
>   GENERATE  icons/stuff.xpm
>   GENERATE  icons/stuff_off.ppm
>   GENERATE  icons/stuff_off.xpm
>   GENERATE  icons/meas_off.ppm
>   GENERATE  icons/meas_off.xpm
>   GENERATE  icons/bright.ppm
>   GENERATE  icons/bright.xpm
>   GENERATE  icons/bright_off.ppm
>   GENERATE  icons/bright_off.xpm
>   GENERATE  icons/all.ppm
>   GENERATE  icons/all.xpm
>   GENERATE  icons/all_off.ppm
>   GENERATE  icons/all_off.xpm
>   CCgui.o
>   CCgui_util.o
>   CCgui_style.o
>   CCgui_inst.o
>   CCgui_status.o
>   CCgui_canvas.o
>   CCgui_tool.o
>   CCgui_over.o
>   CCgui_meas.o
>   CCgui_frame.o
>   CCgui_frame_drag.o
>   CCfped
> /usr/bin/ld: cannot find -lfl
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/fped_0.1+201210-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: fped
Source-Version: 0.1+201210-1.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated fped 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 

Bug#848015: marked as done (ciphersaber: Fails to build from source, missing dependency on libtest-warn-perl)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 16:48:49 +
with message-id 
and subject line Bug#848015: fixed in ciphersaber 1.01-2.1
has caused the Debian Bug report #848015,
regarding ciphersaber: Fails to build from source, missing dependency on 
libtest-warn-perl
to be marked as done.

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

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


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

ciphersaber fails to build from source in a clean sid chroot. Adding
libtest-warn-perl  to Build-Depends fixes this.

Thanks,
Jeremy Bicha

Excerpt from build log below:

   dh_auto_configure
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2"
--config "ld=x86_64-linux-gnu-gcc -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wl,-z,relro"
Checking prerequisites...
  build_requires:
!  Test::Warn is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Crypt-CipherSaber' version '1.01'
   dh_auto_build
perl Build
Building Crypt-CipherSaber
   dh_auto_test
perl Build test --verbose 1
t/CS2.t .
1..2
ok 1 - use Crypt::CipherSaber;
ok 2 - CS-2 should work on texts longer than IV
ok
Can't locate Test/Warn.pm in @INC (you may need to install the
Test::Warn module) (@INC contains: /<>/blib/lib
/<>/blib/arch /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
/usr/share/perl/5.24 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at t/base.t line 11.
BEGIN failed--compilation aborted at t/base.t line 11.
# Looks like your test exited with 2 before it could output anything.
--- End Message ---
--- Begin Message ---
Source: ciphersaber
Source-Version: 1.01-2.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ciphersaber 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, 04 Apr 2017 06:59:05 +0200
Source: ciphersaber
Binary: libcrypt-ciphersaber-perl
Architecture: source
Version: 1.01-2.1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Mattia Rizzolo 
Description:
 libcrypt-ciphersaber-perl - Perl module implementing CipherSaber encryption
Closes: 848015
Changes:
 ciphersaber (1.01-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build-dependency on libtest-warn-perl to fix FTBFS (Closes: #848015).
Checksums-Sha1:
 54e54532df2ea9cadefbbc350d520fc22728e043 1915 ciphersaber_1.01-2.1.dsc
 f2488df90b72a05a2830664966273efeae87a431 1966 ciphersaber_1.01-2.1.diff.gz
 d41beaa3249630d59c176aaa992e9eb12ae45fc6 5578 
ciphersaber_1.01-2.1_amd64.buildinfo
Checksums-Sha256:
 ac13af6dc713d6b7dce5e0bcf59b77acb4d02a62da58b3a6af23bc6e35ea32ba 1915 
ciphersaber_1.01-2.1.dsc
 61f9cbbe20d04c1aca34e0a1420a82ce1bc0094e4db4b644ecb1156aed1608e1 1966 
ciphersaber_1.01-2.1.diff.gz
 1d1f4a01142549bc55b6f58b05f1d75a32717f31573d974eada9e420d221d848 5578 
ciphersaber_1.01-2.1_amd64.buildinfo
Files:
 4a7b2bbfbb630314759b71cf8474780d 1915 interpreters optional 
ciphersaber_1.01-2.1.dsc
 159bcf0dfa29ad11f98192856ec275f5 1966 interpreters optional 
ciphersaber_1.01-2.1.diff.gz
 f921e8212e944636f5467a39747d7a53 5578 interpreters optional 
ciphersaber_1.01-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAljjKKUSHG1hdHRpYUBk

Bug#846426: marked as done (fped: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 16:48:54 +
with message-id 
and subject line Bug#846426: fixed in fped 0.1+201210-1.1
has caused the Debian Bug report #846426,
regarding fped: add libfl-dev to Build-Depends
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.)


-- 
846426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fped
Severity: important
User: helm...@debian.org
Usertags: libfldep

fped will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since fped uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: fped
Source-Version: 0.1+201210-1.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated fped 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, 04 Apr 2017 18:17:39 +0200
Source: fped
Binary: fped
Architecture: source
Version: 0.1+201210-1.1
Distribution: unstable
Urgency: medium
Maintainer: Xiangfu Liu 
Changed-By: Mattia Rizzolo 
Description:
 fped   - Footprint editor
Closes: 846426
Changes:
 fped (0.1+201210-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing Build-Depends on libfl-dev. (Closes: #846426)
Checksums-Sha1:
 1cfbd8b372849bb253381f33fc71aeb0d46e0163 2077 fped_0.1+201210-1.1.dsc
 b6e1218e1187e98c93820155dc705ee2d35e260c 4328 fped_0.1+201210-1.1.debian.tar.xz
 70b0c4302c25289503e74f2f4b0738c5131eb38b 11072 
fped_0.1+201210-1.1_amd64.buildinfo
Checksums-Sha256:
 95315c642022821a2d22892eb3b714e1e0c0194d12453809888211fa9cc6a051 2077 
fped_0.1+201210-1.1.dsc
 62eec937c0a806c4267b07d2c943627c167ef818f02e153dd92b35f5b1f5e811 4328 
fped_0.1+201210-1.1.debian.tar.xz
 22397120027e22e46ae3d1b3407e571d5312c3d3f0b0b07c5b5fb0d808312c0a 11072 
fped_0.1+201210-1.1_amd64.buildinfo
Files:
 63b3e1699ea50fa2c3ce5ec2ab95ba20 2077 electronics extra fped_0.1+201210-1.1.dsc
 2a7d86a1f1de3e7d0ba393a6a2cf71f9 4328 electronics extra 
fped_0.1+201210-1.1.debian.tar.xz
 2fe13e2456e138ff562fa3b6b5456020 11072 electronics extra 
fped_0.1+201210-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAljjx9ASHG1hdHRpYUBk
ZWJpYW4ub3JnAAoJEAgWueGMdiut8JEP/j6wfGtrzJqWsTxDqlLiRwXXH4oKw0bm
gsIcp/EbAlmXDKcThLeutMP2THPcXLs3luOA8UrrIOjU3AexuRNLAWQT2wIOd/mt
FszKfA3hK5mxkfGqkiFjHPKtGcHyktxHCKbolRqVUa6j4z/OkhH8aFX8eLPmPoYB
x2cHslRk2VIkCOcP7y7M4HQ7OfeWhxUJhUaRYsLkp4KBYdcehFN0KSNkpIr9hmj8
ORUvPC2Tko1fodAHoti+g+rkVWR05TvNPzyhaBxsZp+cx//zMORVUk8MKruKx0TY
LviEm58mkbGAoaYdkK6QrUj9SBSpx2CTPhGOGFdzY1Ceacmmex0q3LCfLE1Y/D3N
ED2/OVKvtsZSJaLXjh0iyzc+wAdkt4LxJgoMXCFvSvUoK0Y8v4xTl4lQ0MSypcXP
xST8/8AvEgSJljhlcbhsZ3JjbZ1RTbq29JzXwG4YSXCaE9wZ708Q9r/vQEaSBKtb
GKK4qss8f8mArl+mnKv1J7T+avptoPVKi9fqJ0crL+Zq9MwclzBi69tdWFJ+C0MH
18tci7uJ9PCdHB10sGtUFwPbUmkMydN8ewwdaRnM3v/jQF+sTQSck+1cX1JUxOFe
WOjLwQimEKAJslZ+1XWSulqL4ciGxIZWZbnweCO6WgSW00Pj9o6i6Bg2vmBOl6Nj
c/BrhvyeEHPe
=4y68
-END PGP SIGNATURE End Message ---

Processed: retitle 844810 to libghc-lambdabot-haskell-plugins-dev: insane memory usage during profiling build

[Debian Bug Tracking System]

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

> retitle 844810 libghc-lambdabot-haskell-plugins-dev: insane memory usage 
> during profiling build
Bug #844810 [libghc-lambdabot-haskell-plugins-dev] lambdabot: FTBFS: 
unsatisfiable build-dependencies: libghc-lambdabot-haskell-plugins-dev (< 5.2), 
libghc-lambdabot-haskell-plugins-dev (>= 5.1)
Bug #842740 [libghc-lambdabot-haskell-plugins-dev] 
libghc-lambdabot-haskell-plugins-dev: insane memory usage during profiling build
Bug #846752 [libghc-lambdabot-haskell-plugins-dev] lambdabot: FTBFS: 
unsatisfiable build-dependencies: libghc-lambdabot-haskell-plugins-dev (< 5.2), 
libghc-lambdabot-haskell-plugins-dev (>= 5.1)
Changed Bug title to 'libghc-lambdabot-haskell-plugins-dev: insane memory usage 
during profiling build' from 'lambdabot: FTBFS: unsatisfiable 
build-dependencies: libghc-lambdabot-haskell-plugins-dev (< 5.2), 
libghc-lambdabot-haskell-plugins-dev (>= 5.1)'.
Ignoring request to change the title of bug#842740 to the same title
Changed Bug title to 'libghc-lambdabot-haskell-plugins-dev: insane memory usage 
during profiling build' from 'lambdabot: FTBFS: unsatisfiable 
build-dependencies: libghc-lambdabot-haskell-plugins-dev (< 5.2), 
libghc-lambdabot-haskell-plugins-dev (>= 5.1)'.
> thanks
Stopping processing here.

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

Bug#859511: libbsd-dev: trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also in package manpages-dev 4.10-1

[Sven Joachim]

Control: reassign -1 manpages-dev 4.10-1
Control: affects -1 libbsd-dev

On 2017-04-04 16:29 +0100, Chris Lamb wrote:

> Package: libbsd-dev
> Version: 0.8.3-1
> Severity: serious
>
> Hi,
>
> I'm seeing:
>
> […]
>
> Unpacking libbsd-dev:amd64 (0.8.3-1) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-tduipc/101-libbsd-dev_0.8.3-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also 
> in package manpages-dev 4.10-1

It's libbsd-dev which came first to ship that manpage, manpages-dev only
added it in the 4.10-1 upload.

Cheers,
   Sven

Processed: Re: Bug#859511: libbsd-dev: trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also in package manpages-dev 4.10-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 manpages-dev 4.10-1
Bug #859511 [libbsd-dev] libbsd-dev: trying to overwrite 
'/usr/share/man/man3/explicit_bzero.3.gz', which is also in package 
manpages-dev 4.10-1
Bug reassigned from package 'libbsd-dev' to 'manpages-dev'.
No longer marked as found in versions libbsd/0.8.3-1.
Ignoring request to alter fixed versions of bug #859511 to the same values 
previously set
Bug #859511 [manpages-dev] libbsd-dev: trying to overwrite 
'/usr/share/man/man3/explicit_bzero.3.gz', which is also in package 
manpages-dev 4.10-1
Marked as found in versions manpages/4.10-1.
> affects -1 libbsd-dev
Bug #859511 [manpages-dev] libbsd-dev: trying to overwrite 
'/usr/share/man/man3/explicit_bzero.3.gz', which is also in package 
manpages-dev 4.10-1
Added indication that 859511 affects libbsd-dev

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

Processed: Fix version info

[Debian Bug Tracking System]

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

> notfound 859514 4.9-2
Bug #859514 [manpages] file conflict with keyutils
There is no source info for the package 'manpages' at version '4.9-2' with 
architecture ''
Unable to make a source version for version '4.9-2'
Ignoring request to alter found versions of bug #859514 to the same values 
previously set
> found 859514 4.10-1
Bug #859514 [manpages] file conflict with keyutils
Marked as found in versions manpages/4.10-1.
> affects 859514 keyutils
Bug #859514 [manpages] file conflict with keyutils
Added indication that 859514 affects keyutils
> severity 859514 serious
Bug #859514 [manpages] file conflict with keyutils
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#847282: marked as done (imagemagick-doc: fails to upgrade wheezy -> jessie -> stretch)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 16:33:54 +
with message-id 
and subject line Bug#847282: fixed in imagemagick 8:6.9.7.4+dfsg-3
has caused the Debian Bug report #847282,
regarding imagemagick-doc: fails to upgrade wheezy -> jessie -> stretch
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.)


-- 
847282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick-doc
Version: 8:6.9.6.6+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch'.
It installed fine in 'wheezy', and upgraded to 'jessie' successfully,
but then the upgrade to 'stretch' failed.

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

  Preparing to unpack .../imagemagick-doc_8%3a6.9.6.6+dfsg-1_all.deb ...
  dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick-doc' 
contains files not owned by package imagemagick-doc:all, cannot switch to 
symlink
  dpkg: error processing archive 
/var/cache/apt/archives/imagemagick-doc_8%3a6.9.6.6+dfsg-1_all.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1


Let's see what we have there:

# ls -la /usr/share/doc/imagemagick-doc
total 176
drwxr-xr-x   4 root root   220 Dec  6 22:15 .
drwxr-xr-x 117 root root  2500 Dec  6 22:16 ..
-rw-r--r--   1 root root   991 Aug 16 12:13 NEWS.Debian.gz
-rw-r--r--   1 root root 31950 Aug 16 12:13 changelog.Debian.gz
-rw-r--r--   1 root root 77347 Oct 25  2014 changelog.gz
-rw-r--r--   1 root root 42835 Aug 16 12:13 copyright
drwxr-xr-x   3 root root  1040 Dec  6 22:15 images
lrwxrwxrwx   1 root root21 Apr  7  2016 images.dpkg-backup -> 
../imagemagick/images
-rw-r--r--   1 root root 18947 Aug 25 12:05 index.html
drwxr-xr-x   5 root root  1340 Dec  6 22:15 www
lrwxrwxrwx   1 root root18 Apr  7  2016 www.dpkg-backup -> 
../imagemagick/www

# dpkg -S /usr/share/doc/imagemagick-doc/*
imagemagick-doc: /usr/share/doc/imagemagick-doc/NEWS.Debian.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.Debian.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/copyright
imagemagick-doc: /usr/share/doc/imagemagick-doc/images
dpkg-query: no path found matching pattern 
/usr/share/doc/imagemagick-doc/images.dpkg-backup
imagemagick-doc: /usr/share/doc/imagemagick-doc/index.html
imagemagick-doc: /usr/share/doc/imagemagick-doc/www
dpkg-query: no path found matching pattern 
/usr/share/doc/imagemagick-doc/www.dpkg-backup


So it's probably the .dpkg-backup files left from the wheezy->jessie upgrade
that are now causing problems.


cheers,

Andreas


imagemagick-doc_8:6.9.6.6+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.7.4+dfsg-3

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick 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, 04 Apr 2017 15:05:41 +0200
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-3 
libmagickcore-6.q16-3-extra libmagickcore-6.q16-dev libmagickwand-6.q16-3 
libmagickwand-6.q16-dev libmagick++-6.q16-7 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-3 
libmagickcore-6.q16hdri-3-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-3 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-7 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source
Version: 

Bug#848015: ciphersaber: diff for NMU version 1.01-2.1

[Mattia Rizzolo]

On Tue, Apr 04, 2017 at 08:27:55AM +0200, Stefan Hornburg (Racke) wrote:
> On 04/04/2017 07:01 AM, Mattia Rizzolo wrote:
> > Control: tags 848015 + patch
> > Control: tags 848015 + pending
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for ciphersaber (versioned as 1.01-2.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> > 
> > Regards.
> > 
> 
> Dear Mattia,
> 
> the patch looks good to me.

Thank you!

mattia@warren ~ % dcut reschedule -d 0 -f ciphersaber_1.01-2.1_source.changes
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Uploading mattia-1491323492.commands to ftp-master
mattia@warren ~ % 

-- 
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#859512: marked as done (heaptrack: Could not find heaptrack interpreter executable: heaptrack_interpret)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 16:18:47 +
with message-id 
and subject line Bug#859512: fixed in heaptrack 1.0.0-2
has caused the Debian Bug report #859512,
regarding heaptrack: Could not find heaptrack interpreter executable: 
heaptrack_interpret
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.)


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

Dear Maintainer,

sorry I cannot be of more help since I was merely evaluating the
package, but when I try to trace the execution of any program, I get
the error:

$ heaptrack /bin/ls
Could not find heaptrack interpreter executable: 
/usr/bin/../lib/heaptrack/libexec/heaptrack_interpret

Certainly, I cannot find any heaptrack_interpret file on my system.

I am using the fish shell, but nothing changed when using bash.

Thanks!

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

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

Versions of packages heaptrack depends on:
ii  libboost-iostreams1.62.01.62.0+dfsg-4
ii  libboost-program-options1.62.0  1.62.0+dfsg-4
ii  libboost-regex1.62.01.62.0+dfsg-4
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-11
ii  libstdc++6  6.3.0-11
ii  zlib1g  1:1.2.8.dfsg-5

heaptrack recommends no packages.

heaptrack suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: heaptrack
Source-Version: 1.0.0-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated heaptrack 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, 04 Apr 2017 18:09:48 +0200
Source: heaptrack
Binary: heaptrack heaptrack-gui libheaptrack
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 heaptrack  - Heap memory profiler for Linux
 heaptrack-gui - Heap memory profiler for Linux
 libheaptrack - Heap memory profiler for Linux
Closes: 859512
Changes:
 heaptrack (1.0.0-2) unstable; urgency=medium
 .
   * [cf6520a] Add kio-dev as a build-dependency.
   * [8879be4] Add libheaptrack as a dependency of (Closes: #859512)
Checksums-Sha1:
 69d4fdae92561f18de14db29a388327f5906007d 2380 heaptrack_1.0.0-2.dsc
 ebdfc869fc2cefffcf12ec89312e69021575bc5d 4976 heaptrack_1.0.0-2.debian.tar.xz
 cd6ceabef47045b63dfd69e4a28df65979ceab17 26198 
heaptrack_1.0.0-2_source.buildinfo
Checksums-Sha256:
 fd241272ad0f23335d3d8f50526689474cd8d1b32f358161e911292f98c4 2380 
heaptrack_1.0.0-2.dsc
 b3eede7bad68922409c9f22973575d5bae116597bf11ab091df1b6e63252f9b3 4976 
heaptrack_1.0.0-2.debian.tar.xz
 937e4419516504df7221504333489f8b2015a1230dd309bfd613bee249673039 26198 
heaptrack_1.0.0-2_source.buildinfo
Files:
 202efbd8fffe523fe6987f5301005b42 2380 devel optional heaptrack_1.0.0-2.dsc
 771bf091d94697c46331870060c1dec8 4976 devel optional 
heaptrack_1.0.0-2.debian.tar.xz
 97fb11198e780759bc447e7132497b92 26198 devel optional 
heaptrack_1.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAljjxasACgkQ0+Fzg8+n
/wbJCQ/+IUTpHLKnulFU72smxgXdbK2NqNJR62gE7gURzDN9fBlcnh36xG2ZNZRk
rqL3bBUbsQGoFZlseFt3lfif/HVdHC98doBj3kaLjSd94dFJm8lfEHdf1QFbuF6N
au1PjrCX0uhzopsJADxEWixV21sPUOkqUBSRdFLwpgf18XQOv8j/sLQu7VDIc9Rr
MAJG3OyGp65fAwzZkvKtfXTElMq7xXRWW4UXA5nilisvbiOmekLtgMkjXjxABObw

Bug#859514: file conflict with keyutils

[Alf Gaida]

Package: manpages
Version: 4.09-2
Severity: grave

Unpacking manpages (4.10-1) over (4.09-2) ...
dpkg: error processing archive /var/cache/apt/archives/manpages_4.10-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man7/keyrings.7.gz', which is also in 
package keyutils 1.5.9-9
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)



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

Kernel: Linux 4.10.8-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

manpages depends on no packages.

manpages recommends no packages.

Versions of packages manpages suggests:
it  man-db [man-browser]  2.7.6.1-2

-- no debconf information

Bug#859512: heaptrack: Could not find heaptrack interpreter executable: heaptrack_interpret

[Alberto Luaces]

Package: heaptrack
Version: 1.0.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

sorry I cannot be of more help since I was merely evaluating the
package, but when I try to trace the execution of any program, I get
the error:

$ heaptrack /bin/ls
Could not find heaptrack interpreter executable: 
/usr/bin/../lib/heaptrack/libexec/heaptrack_interpret

Certainly, I cannot find any heaptrack_interpret file on my system.

I am using the fish shell, but nothing changed when using bash.

Thanks!

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

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

Versions of packages heaptrack depends on:
ii  libboost-iostreams1.62.01.62.0+dfsg-4
ii  libboost-program-options1.62.0  1.62.0+dfsg-4
ii  libboost-regex1.62.01.62.0+dfsg-4
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-11
ii  libstdc++6  6.3.0-11
ii  zlib1g  1:1.2.8.dfsg-5

heaptrack recommends no packages.

heaptrack suggests no packages.

-- no debconf information

Bug#859511: libbsd-dev: trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also in package manpages-dev 4.10-1

[Chris Lamb]

Package: libbsd-dev
Version: 0.8.3-1
Severity: serious

Hi,

I'm seeing:

[…]

Unpacking libbsd-dev:amd64 (0.8.3-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-tduipc/101-libbsd-dev_0.8.3-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also 
in package manpages-dev 4.10-1


Regards,

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

Processed: severity of 451535 is important

[Debian Bug Tracking System]

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

> severity 451535 important
Bug #451535 [partman-crypto] debian-installer: allow to 'reuse' encrypted 
volumes
Bug #498199 [partman-crypto] d-i cannot use existing encrypted partition
Bug #529343 [partman-crypto] debian-installer: physical volume for encryption: 
doesnt care if already encrypted and kills data
Bug #566497 [partman-crypto] install: Please support reusing existing crypt-lvm 
partitions
Bug #641264 [partman-crypto] debian-installer: cannot install to already 
encrypted partitions
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: severity of 857450 is important

[Debian Bug Tracking System]

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

> # Missing updates from OP + moreinfo + unreproducible
> severity 857450 important
Bug #857450 [libxcb1] libxcb1: many segfaults -gnome and such- related to libxcb
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#859219: phpmyadmin: Fails to build from source, illegal character in input string

[Niels Thykier]

Michal Čihař:
> Hi
> 
> Niels Thykier píše v Út 04. 04. 2017 v 12:37 +:
>> Would it be possible to use a short term work around by using a
>> different locale during the tests (e.g. en_US.UTF-8)? Then we can use
>> look at a better long term solution after stretch has been released.
> 
> I've done that just now (I would have done that on previous upload if I
> didn't forget).
> 

Thanks, much appreciated. :)

Unfortunately, I am told that "en_US.UTF-8" is not guaranteed to exist
(despite that it is there on our buildds) unless you B-D on locales-all.

If you don't want that, you can use:

"""
Build-Depends: locales


test:
  localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias \
   --quiet debian/en_US.UTF-8 || exit 1
  LOCPATH=debian LC_ALL=en_US.UTF-8 phpunit --config \
phpunit.xml.nocoverage --exclude-group selenium \
--exclude-group network

clean:
  rm -f debian/en_US.UTF-8
"""

Mind you though, that this assumes "locales" and *not* locales-all.  At
least back in the Squeeze/Wheezy days, locales-all was not a substitute
for locales IRT to code-snippet above.

Thanks,
~Niels

Bug#858914: marked as done (CVE-2017-5929: serialization vulnerability in SocketServer and ServerSocketReceiver)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 14:49:44 +
with message-id 
and subject line Bug#857343: fixed in logback 1:1.1.9-3
has caused the Debian Bug report #857343,
regarding CVE-2017-5929: serialization vulnerability in SocketServer and 
ServerSocketReceiver
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.)


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

Hi,

the following vulnerability was published for logback.

CVE-2017-5929[0]:
| QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting
| the SocketServer and ServerSocketReceiver components.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-5929
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929
Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: logback
Source-Version: 1:1.1.9-3

We believe that the bug you reported is fixed in the latest version of
logback, 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.
Markus Koschany  (supplier of updated logback 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, 04 Apr 2017 14:49:44 +0200
Source: logback
Binary: liblogback-java liblogback-java-doc
Architecture: source
Version: 1:1.1.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 liblogback-java - flexible logging library for Java
 liblogback-java-doc - flexible logging library for Java - documentation
Closes: 857343
Changes:
 logback (1:1.1.9-3) unstable; urgency=medium
 .
   * Team upload.
   * The patch for CVE-2017-5929 was incomplete. Add CVE-2017-5929-part2.patch
 and really fix the issue. (Closes: #857343)
   * Remove all test cases from CVE-2017-5929.patch and only apply the minimal
 changes to make it easier to review the package. Tests are disabled anyway.
Checksums-Sha1:
 0f818b40addffd9000c2ae5bf85a8fadf183e321 2408 logback_1.1.9-3.dsc
 439c5a96a938124118754750fe6f6c17871c7475 13524 logback_1.1.9-3.debian.tar.xz
 7d59e7da161541f30327e9ab3a5cd82a90c03cd8 15164 logback_1.1.9-3_amd64.buildinfo
Checksums-Sha256:
 889b956159efc88f2afd1274f7677a6ec2953ce21e22aff3fed58f8c3fa19325 2408 
logback_1.1.9-3.dsc
 cfdb6de7a2d5dd2c7cb004ec8309fa56b241c329a85984170eb85332a28db6b5 13524 
logback_1.1.9-3.debian.tar.xz
 3e2bfa71d2a5677bb73d2f1c2f06388cdf57aca676f88623dc498fa8ca8bfd70 15164 
logback_1.1.9-3_amd64.buildinfo
Files:
 7fe1580466b7fe6eb34d08ed8f5f5578 2408 java optional logback_1.1.9-3.dsc
 a2442304b426b0755a3e98419a0b44d0 13524 java optional 
logback_1.1.9-3.debian.tar.xz
 deb12871e55f268fd8cf88be8ffaf836 15164 java optional 
logback_1.1.9-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAljjpn9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkjvIP/jixGBcpyP0MvSrtixrZRGjU8Ht+5zwma85H
Pd5fU6nziTHqJhaWxQrTicWijRLl73LQPLcOSU6CrJAHs1RlOhWKNUWExW5tUz+w
A5/c1YhXrQ1uTCM0RZKPk58ovnVL6GOZxtWbOPLQaTBW10rRHcnDsA26HW6AJjQX
W/3w1XXvcnoQV22hypN4lF5B8hwQC57xlM8v8FHzucrypTdmkwWBQDy3KI5p+AAE
dnL0SCrszazJSVNmfgMYlGM2FmQFkJVyS7zHUd45hUv6y9g6D4QNCmj5tHc7qQ2u
IYS+nPy/9xFANN2wj8l7WBsEai40uVc9vnrkb4piUYZzsAbKCNRx15U/EuzPE6tC
W44iUDBPPvVIxDlp1/FDekKGg6UMrB0Wt0hS2Kw9k5MViA50FZK4nTeyqwPfXqMe
f5FdE9exhNFvidQgyIy4elEjuShFUGMAaXpsWnaUpURbnT02Go/9TMWTjeRAzG6Q
OLTJcP8xIeeOJGnaZL6olkwPkR8p5ZoMzSZKurfvTpD93ABhRnO6jd9IOLtsc15R
1Z2sRNSkiuBN+reSpbmtXZz+7gsF16XH5ug5pCfXQ84M1XonGLiyGqbweQ0sPrFJ
n2coSjV+hryUnhdldCSQNMs0Ssc3Z+OSk3okmGz0jDgrklE6k0bjVXH5QEfQXN/b
13aFLPTN
=bpU+
-END PGP SIGNATURE 

Bug#857343: marked as done (logback: CVE-2017-5929: serialization vulnerability affecting the SocketServer and ServerSocketReceiver components)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 14:49:44 +
with message-id 
and subject line Bug#857343: fixed in logback 1:1.1.9-3
has caused the Debian Bug report #857343,
regarding logback: CVE-2017-5929: serialization vulnerability affecting the 
SocketServer and ServerSocketReceiver components
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.)


-- 
857343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblogback-java
Version: 1:1.1.2-1
Severity: important
Tags: upstream patch

Dear Maintainer,

logback versions in wheezy, jessie and stretch are vulnerable to a
deserialization issue.
Logback would try to deserialize data from a socket, but it can't be trusted.
Upstream mitigates this issue by adding a whitelist of allowed classes to be
deserialized.

I've prepared a patch for jessie.

Regards

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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)

Versions of packages liblogback-java depends on:
ii  libslf4j-java  1.7.7-1

liblogback-java recommends no packages.

Versions of packages liblogback-java suggests:
ii  glassfish-javaee  1:2.1.1-b31g+dfsg1-2
ii  libjanino-java2.7.0-2
diff -rPu logback.orig/logback-access/src/main/java/ch/qos/logback/access/net/HardenedAccessEventInputStream.java logback/logback-access/src/main/java/ch/qos/logback/access/net/HardenedAccessEventInputStream.java
--- logback.orig/logback-access/src/main/java/ch/qos/logback/access/net/HardenedAccessEventInputStream.java	1970-01-01 01:00:00.0 +0100
+++ logback/logback-access/src/main/java/ch/qos/logback/access/net/HardenedAccessEventInputStream.java	2017-03-04 15:39:00.0 +0100
@@ -0,0 +1,16 @@
+package ch.qos.logback.access.net;
+
+import java.io.IOException;
+import java.io.InputStream;
+
+import ch.qos.logback.access.spi.AccessEvent;
+import ch.qos.logback.core.net.HardenedObjectInputStream;
+
+public class HardenedAccessEventInputStream extends HardenedObjectInputStream {
+
+public HardenedAccessEventInputStream(InputStream in) throws IOException {
+super(in, new String[] {AccessEvent.class.getName(), String[].class.getName()});
+}
+
+}
+
diff -rPu logback.orig/logback-access/src/main/java/ch/qos/logback/access/net/SocketNode.java logback/logback-access/src/main/java/ch/qos/logback/access/net/SocketNode.java
--- logback.orig/logback-access/src/main/java/ch/qos/logback/access/net/SocketNode.java	2013-09-07 12:44:46.0 +0200
+++ logback/logback-access/src/main/java/ch/qos/logback/access/net/SocketNode.java	2017-03-05 15:09:48.0 +0100
@@ -15,7 +15,6 @@
 
 import java.io.BufferedInputStream;
 import java.io.IOException;
-import java.io.ObjectInputStream;
 import java.net.Socket;
 
 import ch.qos.logback.access.spi.AccessContext;
@@ -42,16 +41,15 @@
 
   Socket socket;
   AccessContext context;
-  ObjectInputStream ois;
+  HardenedAccessEventInputStream hardenedOIS;
 
   public SocketNode(Socket socket, AccessContext context) {
 this.socket = socket;
 this.context = context;
 try {
-  ois = new ObjectInputStream(new BufferedInputStream(socket
-  .getInputStream()));
+  hardenedOIS = new HardenedAccessEventInputStream(new BufferedInputStream(socket.getInputStream()));
 } catch (Exception e) {
-  System.out.println("Could not open ObjectInputStream to " + socket + e);
+  System.out.println("Could not open HardenedObjectInputStream to " + socket + e);
 }
   }
 
@@ -61,7 +59,7 @@
 try {
   while (true) {
 // read an event from the wire
-event = (IAccessEvent) ois.readObject();
+event = (IAccessEvent) hardenedOIS.readObject();
 //check that the event should be logged
 if (context.getFilterChainDecision(event) == FilterReply.DENY) {
   break;
@@ -81,7 +79,7 @@
 }
 
 try {
-  ois.close();
+  hardenedOIS.close();
 } catch (Exception e) {
   System.out.println("Could not close connection." + e);
 }
diff -rPu logback.orig/logback-classic/src/main/java/ch/qos/logback/classic/net/HardenedLoggingEventInputStream.java logback/logback-classic/src/main/java/ch/qos/logback/classic/net/HardenedLoggingEventInputStream.java
--- 

Bug#847715: marked as done (node-resumer depends on node-through2 (>= 2.3.4), but only 2.0.3-1 is in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 14:49:50 +
with message-id 
and subject line Bug#847715: fixed in node-resumer 0.0.0-2
has caused the Debian Bug report #847715,
regarding node-resumer depends on node-through2 (>= 2.3.4), but only 2.0.3-1 is 
in unstable
to be marked as done.

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

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


-- 
847715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-resumer
Version: 0.0.0-1
Severity: serious

node-resumer depends on node-through2 (>= 2.3.4),
but only 2.0.3-1 is in the archive.
--- End Message ---
--- Begin Message ---
Source: node-resumer
Source-Version: 0.0.0-2

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-resumer 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, 04 Apr 2017 00:12:33 +0200
Source: node-resumer
Binary: node-resumer
Architecture: source
Version: 0.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-resumer - through stream that starts paused and resumes on the next tick
Closes: 847715
Changes:
 node-resumer (0.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Bug fix: "node-resumer depends on node-through2 (>= 2.3.4), but
 only 2.0.3-1 is in unstable", thanks to Adrian Bunk (Closes: #847715).
   * Fix breakage by depending on through instead of through2.
Checksums-Sha1:
 a6d2aeab72e57b09e1132e16e56968a456d2e377 2025 node-resumer_0.0.0-2.dsc
 8071d3350d838a661d75590afe6e2052fab125a7 3056 
node-resumer_0.0.0-2.debian.tar.xz
 55a0780c8178ddce19ed06515d814fd6123e9b35 5633 
node-resumer_0.0.0-2_amd64.buildinfo
Checksums-Sha256:
 d402027aa61d7676de884861bb0537783ae2980e03a3f653e2de7a354b4a1e89 2025 
node-resumer_0.0.0-2.dsc
 fc9cb20c62977f5ce52f267725ea39874709759af0621f458bf70a397a6d21c9 3056 
node-resumer_0.0.0-2.debian.tar.xz
 6aa676c14870b32945af76e5bee799922818f20bb6db9a1793341ab0efdc7cea 5633 
node-resumer_0.0.0-2_amd64.buildinfo
Files:
 533fa9160963d8a480b682dad8f47c6b 2025 web optional node-resumer_0.0.0-2.dsc
 6c51ac0b04e7d9d0aca393b015d598b8 3056 web optional 
node-resumer_0.0.0-2.debian.tar.xz
 ef4cd11806bdcf0ccb612fa96041d548 5633 web optional 
node-resumer_0.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAljjpXEACgkQADoaLapB
CF/jNw/+KZoM3z130drFC7M3U8r+UbObzITbv5BpGC994YdzeXuQtbvZfqMOEIMc
xbWzzHGfV0AR0x3VzHBFXRb/llaCZB9Ot+HpSS8kLAhA1l7AGGf8Ac1Ki2ZbVgOe
ckrjbtv0p5Trne1oIOzmLRKizQNO1nxywb5xyy+O3zNpBP5VJlTyb9QXdytz4RDx
RkBc9kgsrGJKWsYQ3L+lI6wQMfsAtz8duK1omH+MNC/L2RZi+ZyqeMSmOkcN7hgI
psj/A5eNuT1wAXOg0UHrYYbpvUs6w0MVoYIxwUwGqYdbMndzFNnN0M664MVS/k3Z
0xX7cnCbA0Cx9HEZZbclC3MIA015eprKvzddKpHiJXJKwTocp7zKjLkANN/d80KW
rL96QBMyh82BwhdOjgnAgkG8OB0wleP/vknkEDZ76v8mhFVkzwyAQiPNgBjdQbcN
94v4pmZnNsk4KzYTtrEs6bn3/WuvSMP1QsJHpjWKs3TWEiUwq61ISWoTZKsYNax1
VW2dYzv7GZSJQhDjvc73PtE3sUfnHZKovh+G1ETdLlrQd8FK7fIxE7Pqn3WiSWYX
3vwJPsn+4/SMQQ8qGxMjiXQqoqEjTvw8ulDA0CupxY+hxPNZEn7GuUgDz/4O+OGS
ZeuZgoN4ELStPlMsmxv+QLIMw2J4l7BtVn5EhJAz5OUO7udJTBA=
=sPvq
-END PGP SIGNATURE End Message ---

Bug#859510: Generated header file without means to regenerate

[James Clarke]

Source: ruby-unf-ext
Version: 0.0.7.2-2
Severity: serious

Hi,
While investigating #859463 with Niels, we noticed that the file in
question, ext/unf_ext/unf/table.hh, is pre-generated, but the original
sources[1] (and script used to process the sources[2]) are not present
in main.

Regards,
James

[1] https://github.com/sile/unf/tree/master/data
[2] https://github.com/sile/unf/blob/master/lisp/gen-table.lisp

Bug#859463: ruby-unf-ext FTBFS on ppc64el: unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to 'char' inside { } [-Wnarrowing]

[Niels Thykier]

On Mon, 03 Apr 2017 23:38:48 +0300 Adrian Bunk  wrote:
> Source: ruby-unf-ext
> Version: 0.0.7.2-2
> Severity: serious
> 
> ruby-unf-ext FTBFS on ppc64el (originally reported by Frederic Bonnard):
> 
> ...
> unf/table.hh:13539:25: error: narrowing conversion of '-51' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> unf/table.hh:13539:25: error: narrowing conversion of '-123' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> unf/table.hh:13539:25: error: narrowing conversion of '-50' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> unf/table.hh:13539:25: error: narrowing conversion of '-105' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> ...
> 
> 
> Complete log is attached.

This is caused by ppc64el having "char" being unsigned by default.
Beyond the table that needs to be converted/dealt with, there are about
20 -Wsign-conversion issues in the code that smells like they may cause
issues as well.

That said, a short term fix may be to revert:
https://github.com/knu/ruby-unf_ext/commit/1e2d2bc29798342ab2616eb3d74ea36c793a33e4

Thanks,
~Niels

Bug#859219: marked as done (phpmyadmin: Fails to build from source, illegal character in input string)

[Debian Bug Tracking System]

Your message dated Tue, 04 Apr 2017 13:48:50 +
with message-id 
and subject line Bug#859219: fixed in phpmyadmin 4:4.6.6-3
has caused the Debian Bug report #859219,
regarding phpmyadmin: Fails to build from source, illegal character in input 
string
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.)


-- 
859219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpmyadmin
Version: 4:4.6.6-1
Severity: serious

phpmyadmin 4:4.6.6-1 and 4:4.6.6-2 fail to build from source in a
clean sid chroot (and in Ubuntu 17.04).

Build log excerpt


There was 1 error:

1) PMA_Charset_Conversion_Test::testCharsetConversion
iconv(): Detected an illegal character in input string

/<>/libraries/charset_conversion.lib.php:111
/<>/test/libraries/PMA_charset_conversion_test.php:61


Other info
---
Full build log at
https://launchpad.net/ubuntu/+source/phpmyadmin/4:4.6.6-2/+build/12383267

I encourage you to use a source-only upload when possible so that you
will see this kind of problem sooner.

https://wiki.debian.org/SourceOnlyUpload

Thanks,
Jeremy
--- End Message ---
--- Begin Message ---
Source: phpmyadmin
Source-Version: 4:4.6.6-3

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

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated phpmyadmin 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, 04 Apr 2017 15:19:53 +0200
Source: phpmyadmin
Binary: phpmyadmin
Architecture: source
Version: 4:4.6.6-3
Distribution: unstable
Urgency: medium
Maintainer: Thijs Kinkhorst 
Changed-By: Michal Čihař 
Description:
 phpmyadmin - MySQL web administration tool
Closes: 859219
Changes:
 phpmyadmin (4:4.6.6-3) unstable; urgency=medium
 .
   * Set locales for tests to avoid problems with transliteration in glibc for
 C.UTF-8 (Closes: #859219).
Checksums-Sha1:
 d5b165b0a3149fe82fc09d4d5087080770262306 2082 phpmyadmin_4.6.6-3.dsc
 73e98564754296e06f002ace1e36cd78dd68 79472 phpmyadmin_4.6.6-3.debian.tar.xz
 2f42bc126d9ced9771af2ad50d12aa41fe4ce24c 8228 
phpmyadmin_4.6.6-3_amd64.buildinfo
Checksums-Sha256:
 fc86e27bcb9a42568556ec8ea6a6cba6954d64a575d27329f4834cb42530c630 2082 
phpmyadmin_4.6.6-3.dsc
 a749c21876b5c4e5b50ef9fa7c385fd98db4c38eadbe977ec3f2ec74d4a7c57c 79472 
phpmyadmin_4.6.6-3.debian.tar.xz
 6cc20e870fb7576bd1d55c295b496d7a353fa2b7c2d3f913d17266418a22bfb0 8228 
phpmyadmin_4.6.6-3_amd64.buildinfo
Files:
 fbf12dd9e20ca28155e521dc0e40958d 2082 web extra phpmyadmin_4.6.6-3.dsc
 5320fef5e1663550660e45392fe30999 79472 web extra 
phpmyadmin_4.6.6-3.debian.tar.xz
 35ca978bb3f86b2f2347abf16976b491 8228 web extra 
phpmyadmin_4.6.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEh+Zzr4P2w6DDRMjD9KoinU1YwkUFAljjn04ACgkQ9KoinU1Y
wkWJwg//UssprK+pizzO6U2TmXx6H755olpl6vA9zUfIOUf7PNsNRzZlccAB8xau
jFF1vAErX4gl0oEJSGPXErZRyGjP5UFUGmQ9e7QKArP04otjD/V4Vf8rhhVKJCxI
NHQl1hq00cNQ74t4XGAFomjgSNkChtJpwjxPAFl294iWlXYX6zcBUIZTWha3/4Cd
vTv4IULzXmorp+QkzML8WEVrAv44QhvvU/cNTHQymD+QDyN34ZVOg9/1OiVt4sW/
dNovWfdWKPRqxkbj0YlkHcTRjPc05fEzdXjLDaWNhdq8iUa8c7GmpcfVAkG7nbS1
1EDC6Hpf9OnPZiA2DhY7chaLN1XlMe3T5pwbpbYBzlCERd4gWSGGo3Q2AVC/CW0P
i5ZaX6YS/ZanVpaJrV6pJQJJZi3cpQPEV7ETSa6ge6/YGe86qWb+olrOGGYEDd25
51jqNwfKf+RcSLviwOjt26PKn85Z8B9RmN3PduIF3T9Mo6sqGYf4MOBvuA0w/TY1
uQU8Sx8BqKDAoksl/1XD0Fobx1rj28Na/59ic4uiwYYgVKRaK/S3iPofQbM1/8Lt
g3L0uzsT9NJ1Yc4zqMVSGz4x1AKoLeVwkz+F5lzvKAeY7lPrfDZ70UiSoGRoenuz
58D0yBTQAbFD1mFrjFfZFAdWVZVp+w3F17RoF2ByGK071ZJ966M=
=1UEc
-END PGP SIGNATURE End Message ---

Bug#857343: closed by Markus Koschany <a...@debian.org> (Bug#857343: fixed in logback 1:1.1.9-2)

[Markus Koschany]

Am 01.04.2017 um 08:20 schrieb Fabrice Dagorn:
> The POC is a simple Eclipse java project.
> 
> UnsafeReceiver will open a ServerSocketReceiver on  port and wait
> forever.
> 
> Injector will then open a client Socket to the ServerSocketReceiver and
> serialize a Calculator instance through the wire.
> 
> Calculator implements ILoggingEvent to prevent ClassCastException on
> deserialization but Logback won't check more and getLoggerName() is called.
> 
> In this case, the gnome calculator is executed.

Thank you for the reproducer. I believe the issue is fixed now and I am
going to upload the new revision soon.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#859219: phpmyadmin: Fails to build from source, illegal character in input string

[Michal Čihař]

Hi

Niels Thykier píše v Út 04. 04. 2017 v 12:37 +:
> Would it be possible to use a short term work around by using a
> different locale during the tests (e.g. en_US.UTF-8)? Then we can use
> look at a better long term solution after stretch has been released.

I've done that just now (I would have done that on previous upload if I
didn't forget).

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


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

Bug#859262: Re: freezes Orca screen reader

[Niels Thykier]

On Sat, 01 Apr 2017 13:54:17 +0300 Mika Hanhijärvi wrote:
> Package: synaptic
> Version: 0.84.2
> Severity: grave
> 


Hi Mika,

Sorry to hear that synaptic is causing you issues.

I am CC'ing the accessibility list hoping that they might have an
insight to what is happening.  I have quoted the original mail in full
below for their sake.

Thanks,
~Niels

(PS: Please CC me on replies if you need my attention.  I am not the
maintainer of synaptic)

On Sat, 01 Apr 2017 13:54:17 +0300 Mika Hanhijärvi wrote:
> Synaptic often freezes the Orca screen reader so that Orca speaks nothing 
> until
> Synaptic is closed. The same happens on both of my laptops running Debian
> Stretch.
> 
> I am blind so I have to use computer using Orca screen reader. It happens wery
> often that when I e.g click the Reload button in Synaptic, or select Reload
> from the Synaptic menu, then Orca screen reader stops speaking. Synapticdoes
> not freeze the whole desktop, just Orca.  This problem seems to happen
> randomly, sometimes it happens sometimes it does not. When Synaptic has
> finished reloading the package database information Orca may start speaking
> again, but often it does not. If it does not then I have to close the Synaptic
> by pressing alt + F4 after which Orca starts to speak again.
> 
> It also happens sometimes that if I have reloaded repository package database
> information and click Mark all updades after that then Orca stops speaking. On
> my second laptop it currently happens almost every time that Orca stops
> speaking when I click the Mark all updates or select it from the menu. Tkhat
> also seems to happen randomly, sometimes it happens sometimes not.
> 
> I have not noticed any problems like that when I have used other applications,
> this happns only when I am using Synaptic.
> 
> As I said I have two laptops running Debian Stretch and both have the same
> problems. Both laptops have been upgraded from Jessie to Stretch. The first
> laptop was almost clean Jessie installation before it was upgraded to Stretch,
> it still has wery little apps installed.
> 
> I am using Gnome desktop. I am blind so it is difficult for me to try to 
> figure
> out what is wrong. I I have used both espeak and espeak-ng speech synthetisers
> with Orca screen reader, the same problem exists notmatter which of those is 
> in
> use.
> 
> [...]

Processed: user release.debian....@packages.debian.org, usertagging 816063, tagging 816063

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 816063 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 816063 + stretch-ignore
Bug #816063 [emacs24] emacs24: TLS certificate validation is silently broken
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Bug#859111: [Debian-med-packaging] Bug#859111: ariba: FTBFS: FAIL: Test run_bowtie2 unsorted

[Sascha Steinbiss]

forwarded 859111 https://github.com/sanger-pathogens/ariba/issues/170
tags 859111 upstream
thanks

Hi all,

> On Thu, Mar 30, 2017 at 06:20:16PM +0300, Adrian Bunk wrote:
>> Control: retitle -1 ariba FTBFS with bowtie2 2.3.1-1
> [...]
>> This is actually not related to the ariba version but to the bowtie2 version,
>> ariba 2.6.1+ds-1 in stretch builds with the stretch bowtie2 2.3.0-2 but 
>> FTBFS with the sid bowtie2 2.3.1-1
> 
> Do we already know whether the newer upstream version fixes this?

No, it doesn't. I just tested it. Given that the test failure seems to
be caused by differences between result and reference, and bowtie2 2.3.1
introduced different default values for one of the parameters [1], it
might be likely that it's connected to that. I have contacted upstream
[2] -- they are usually quite responsive.

Cheers
Sascha

[1] http://bowtie-bio.sourceforge.net/bowtie2/index.shtml
[2] https://github.com/sanger-pathogens/ariba/issues/170

Processed: Re: [Debian-med-packaging] Bug#859111: ariba: FTBFS: FAIL: Test run_bowtie2 unsorted

[Debian Bug Tracking System]

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

> forwarded 859111 https://github.com/sanger-pathogens/ariba/issues/170
Bug #859111 [src:ariba] ariba FTBFS with bowtie2 2.3.1-1
Set Bug forwarded-to-address to 
'https://github.com/sanger-pathogens/ariba/issues/170'.
> tags 859111 upstream
Bug #859111 [src:ariba] ariba FTBFS with bowtie2 2.3.1-1
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: severity of 859308 is important, tagging 859308

[Debian Bug Tracking System]

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

> # Sounds like a stable + stable-backports issue
> severity 859308 important
Bug #859308 [reportbug] reportbug breaks after installing some backported 
packages
Severity set to 'important' from 'grave'
> tags 859308 + jessie
Bug #859308 [reportbug] reportbug breaks after installing some backported 
packages
Added tag(s) jessie.
> thanks
Stopping processing here.

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