date:20170809

Processed (with 1 error): unarchiving 863584, fixed 863584 in 1:2.2.7+dfsg-2+deb8u3, found 863584 in 1:2.2.7+dfsg-2

2017-08-09 Thread Debian Bug Tracking System

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

> unarchive 863584
> fixed 863584 1:2.2.7+dfsg-2+deb8u3
Bug #863584 {Done: Dmitry Smirnov } [src:zabbix] zabbix: 
CVE-2017-2824 CVE-2017-2825
The source 'zabbix' and version '1:2.2.7+dfsg-2+deb8u3' do not appear to match 
any binary packages
Ignoring request to alter fixed versions of bug #863584 to the same values 
previously set
> found 863584 1:2.2.7+dfsg-2
Bug #863584 {Done: Dmitry Smirnov } [src:zabbix] zabbix: 
CVE-2017-2824 CVE-2017-2825
Marked as found in versions zabbix/1:2.2.7+dfsg-2.
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 863584, fixed 863584 in 1:2.2.7+dfsg-2+deb8u3, found 863584 in :2.2.7+dfsg-2

2017-08-09 Thread Debian Bug Tracking System

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

> unarchive 863584
Bug #863584 {Done: Dmitry Smirnov } [src:zabbix] zabbix: 
CVE-2017-2824 CVE-2017-2825
Unarchived Bug 863584
> fixed 863584 1:2.2.7+dfsg-2+deb8u3
Bug #863584 {Done: Dmitry Smirnov } [src:zabbix] zabbix: 
CVE-2017-2824 CVE-2017-2825
The source 'zabbix' and version '1:2.2.7+dfsg-2+deb8u3' do not appear to match 
any binary packages
Marked as fixed in versions zabbix/1:2.2.7+dfsg-2+deb8u3.
> found 863584 :2.2.7+dfsg-2
Bug #863584 {Done: Dmitry Smirnov } [src:zabbix] zabbix: 
CVE-2017-2824 CVE-2017-2825
The source 'zabbix' and version ':2.2.7+dfsg-2' do not appear to match any 
binary packages
Failed to add found on 863584: bad version number ':2.2.7+dfsg-2'.

> thanks
Stopping processing here.

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

Bug#871629: thunderbird UI unusable with many widgets not drawn

2017-08-09 Thread Ben Caradoc-Davies

Package: thunderbird
Version: 1:52.2.1-4+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the thunderbird UI is unusable with many widgets not drawn. See attached 
screenshot. Mouse hover causes some to be drawn.

Using XFCE with Clearlooks Phenix theme. Changing theme causes all widgets to 
be redrawn, but mouse activity causes them to disappear again.

Unusable. Downgrading.

Kind regards,
Ben.


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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.2
ii  fontconfig2.12.3-0.2
ii  libatk1.0-0   2.24.0-1
ii  libc6 2.24-14
ii  libcairo-gobject2 1.14.10-1
ii  libcairo2 1.14.10-1
ii  libdbus-1-3   1.11.16+really1.10.22-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-6
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.8-0.2
ii  libgcc1   1:7.1.0-13
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.53.4-3
ii  libgtk-3-03.22.17-1
ii  libhunspell-1.6-0 1.6.1-2
ii  libpango-1.0-01.40.6-1
ii  libpangocairo-1.0-0   1.40.6-1
ii  libpangoft2-1.0-0 1.40.6-1
ii  libpixman-1-0 0.34.0-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++67.1.0-13
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.2.5-1
ii  lightning 1:52.2.1-4+b1

Versions of packages thunderbird suggests:
pn  apparmor  
ii  fonts-lyx 2.2.3-1
ii  libgssapi-krb5-2  1.15.1-2

-- no debconf information

Bug#868469: Upstream commits for CVE-2017-11352

2017-08-09 Thread Roberto C . Sánchez

Here are the upstream commits that fix CVE-2017-11352:

ImageMagick-6:
https://github.com/ImageMagick/ImageMagick/commit/7f1f01b695e869c410ee10e2176f8fd764f09373

ImageMagick-7:
https://github.com/ImageMagick/ImageMagick/commit/86cb33143c5b21912187403860a7c26761a3cd23

Regards,

-Roberto
-- 
Roberto C. Sánchez


signature.asc
Description: Digital signature

Bug#867101: marked as done (refcard: Build-dependency pdfjam no longer available)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Thu, 10 Aug 2017 03:38:50 +
with message-id 
and subject line Bug#867101: fixed in refcard 10.0
has caused the Debian Bug report #867101,
regarding refcard: Build-dependency pdfjam no longer 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.)


-- 
867101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: refcard
Version: 9.0.4
Severity: serious
Tags: buster sid

The texlive-extra-utils package ships still ships pdfjam but
no longer provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: refcard
Source-Version: 10.0

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

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

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated refcard 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, 09 Aug 2017 06:49:11 +
Source: refcard
Binary: debian-refcard
Architecture: source all
Version: 10.0
Distribution: unstable
Urgency: low
Maintainer: Debian Documentation Project 
Changed-By: W. Martin Borgert 
Description:
 debian-refcard - printable reference card for the Debian system
Closes: 753492 867101 869485 869997
Changes:
 refcard (10.0) unstable; urgency=low
 .
   [ Holger Wansing ]
   * Change package dependency: pdfjam has been removed from unstable,
 was already an transitional package for and has been superseded by
 texlive-extra-utils. Closes: 867101
   * Update ifup|ifdown command to ip link set. Closes: 869485
   * Fix several issues (Debian GNU/Linux -> Debian; switch from debsums
 to dpkg -V; update links; updates/fixes for new apt command).
 Closes: 753492
   * Some minor fixups in wording.
   * Translation updates:
 - Portuguese: Miguel Figueiredo. Closes: #869997
 - German: Holger Wansing.
   * Change versioning scheme from 10.0.0 to 10.0.
 .
   [ W. Martin Borgert ]
   * Remove fop from Makefile and add variable for disabling languages
   * Fix metadata.xsl for newer pdftk
   * Move from CDBS to dh
   * Set compat level to 10
   * Bump standards version to 4.0.1 (no changes)
Checksums-Sha1:
 268fed4d6eb3560f1a1f2f60ff4b7a9293737627 2191 refcard_10.0.dsc
 5ba75ae42b05c637864e9ace9eaf58fe723a4620 171856 refcard_10.0.tar.xz
 ca0b03146edacf76f12973126e466df75c58307a 2813304 debian-refcard_10.0_all.deb
 29c71fd83bf6a2b0068baf2668ee05416d5e282d 11425 refcard_10.0_amd64.buildinfo
Checksums-Sha256:
 20e6c2bb47fa1651b2204e22a9d767b7c171b681794096d15c36986344ec6c85 2191 
refcard_10.0.dsc
 f4e01b5939f529bd5989e72312db7691879009146182d8e09237b502f52c6670 171856 
refcard_10.0.tar.xz
 12da691c8c35d1860699d126729ce887394c92186312235ee7940297611a9ac6 2813304 
debian-refcard_10.0_all.deb
 4dabf248da413f401293008666a4115ebb601ee9595af1b58bc7a883879bebe5 11425 
refcard_10.0_amd64.buildinfo
Files:
 34091bce6eba2acbf5d1a0a952ea3ed0 2191 doc optional refcard_10.0.dsc
 48b79ebe95fdb533272b92e8c8fa5f8f 171856 doc optional refcard_10.0.tar.xz
 be54fe56a431ea8f67dea43a9d203bb6 2813304 doc optional 
debian-refcard_10.0_all.deb
 83b367fad3d4b25ab3d5f774685a8bb9 11425 doc optional 
refcard_10.0_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlmL0esACgkQ4+Chwoa5
Y+pJzw/+NUmLYhYuy3I3r1AI53wM8oRK3wdr9LYaEHkHE2OYOvYtAlSXe2QsIF7p
6DTTsYVMKk5AbkgK4nJJdzQuVwX41dht01KfBfSbzav3X9NLASGPZBH25K6j2LWP
dRjPP2cyBbo/MM8kFIjOSi0yQBBIrw4R+xSU2nhOMfrBwfKyjYDDuFP4ets92HJB
FeDXTgACet2zdeTnaUlowKFZoAVjzZv2FIqD8bOpJjoUKJhhnv8c1AnTzu4NAASw
H1lAP2Hvx5OvyNv4Qu/8NlS+odXxRS8yzxxMq/YWCJrMmXqlqL50nZCvHywRTufS
G9vTqUYBRsDeHKlTVAEHkNmytsfdPr/A13nfBC33Cs7VROszkQYkzZf7e+iNkNWf
1MRssmHVQGxinKxhZlruwxdigQTo8JfYtF3iKez4BUStsxuEIstlblMvo/GOY3I1
eOLar2Egrc0zMDIx5cziO/aAoaXA56Sd3NBs5/9t2/INJyPFSMlFdHnHxfmHBIpo
qHJ96LpBtdsz58xFXcdRg2eX/I9ti0ITNxx1pRgpQh+jhpo5sy2X1Ja5Juf8dfEA
2EilCvQ8uYlc5PwMBO9lRL7irmGsAYDOSuBYa/hWUgK1JyY0H8BvGrWrC9NZonc5

Processed (with 1 error): unarchiving 863901, found 863901 in 2.1.0.0.ast20130823-1, unarchiving 863902 ...

2017-08-09 Thread Debian Bug Tracking System

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

> unarchive 863901
> found 863901 2.1.0.0.ast20130823-1
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in PJSIP transaction 
layer
Ignoring request to alter found versions of bug #863901 to the same values 
previously set
> unarchive 863902
Bug #863902 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: AST-2017-003: Crash in PJSIP multi-part body parser
Unarchived Bug 863902
> found 863902 2.1.0.0.ast20130823-1
Bug #863902 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: AST-2017-003: Crash in PJSIP multi-part body parser
Marked as found in versions pjproject/2.1.0.0.ast20130823-1.
> # fixed version for the pending DSA
> fixed 863901 2.1.0.0.ast20130823-1+deb8u1
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in PJSIP transaction 
layer
The source 'pjproject' and version '2.1.0.0.ast20130823-1+deb8u1' do not appear 
to match any binary packages
Ignoring request to alter fixed versions of bug #863901 to the same values 
previously set
> fixed 863902 2.1.0.0.ast20130823-1+deb8u1
Bug #863902 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: AST-2017-003: Crash in PJSIP multi-part body parser
The source 'pjproject' and version '2.1.0.0.ast20130823-1+deb8u1' do not appear 
to match any binary packages
Marked as fixed in versions pjproject/2.1.0.0.ast20130823-1+deb8u1.
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 863901, found 863901 in 2.1.0.0.ast20130823-1 ...

2017-08-09 Thread Debian Bug Tracking System

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

> unarchive 863901
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in PJSIP transaction 
layer
Unarchived Bug 863901
> found 863901 2.1.0.0.ast20130823-1
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in PJSIP transaction 
layer
Marked as found in versions pjproject/2.1.0.0.ast20130823-1.
> # fixed version for the pending DSA
> fixed 863901 2.1.0.0.ast20130823-1+deb8u1
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject] 
pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in PJSIP transaction 
layer
The source 'pjproject' and version '2.1.0.0.ast20130823-1+deb8u1' do not appear 
to match any binary packages
Marked as fixed in versions pjproject/2.1.0.0.ast20130823-1+deb8u1.
> fixed 863902 2.1.0.0.ast20130823-1+deb8u1
Failed to add fixed on 863902: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

2017-08-09 Thread Steven Jones

Sorry unable to capture an output

I have tried to use pastebin but the case isnt being updated with the links.

regards

Steven

From: Colin Watson 
Sent: Monday, 7 August 2017 8:28 p.m.
To: steven.jo...@vuw.ac.nz; 871...@bugs.debian.org
Subject: Re: Bug#871229: /usr/sbin/update-grub: running update-grub segment 
faults

On Mon, Aug 07, 2017 at 02:15:46PM +1200, steven.jo...@vuw.ac.nz wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***

Neither your bug report nor any of your follow-ups includes the actual
output from update-grub.  Please run the following as root and post the
*exact* output (there will be quite a lot of it):

  sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg

--
Colin Watson   [cjwat...@debian.org]

Bug#871623: glewlwyd: FTBFS: cannot remove .../fonts-glewlwyd/...

2017-08-09 Thread Aaron M. Ucko

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

Builds of glewlwyd covering only its main architecture-dependent
binary package have been failing:

  rm ./debian/fonts-glewlwyd/usr/share/glewlwyd/webapp/fonts/FontAwesome.otf
  rm: cannot remove 
'./debian/fonts-glewlwyd/usr/share/glewlwyd/webapp/fonts/FontAwesome.otf': No 
such file or directory
  debian/rules:24: recipe for target 'override_dh_installinit' failed
  make[1]: *** [override_dh_installinit] Error 1

Could you please run these font-related commands only when actually
building fonts-glewlwyd, for instance by moving them out of
override_dh_installinit(!) into a suitable override_dh_*-indep target?

Thanks!

FTR, I'm treating this bug as a regression because it would affect any
needed binNMUs.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#871288: libzeroc-ice3.6: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-09 Thread James Cowgill

Hi,

On 09/08/17 10:07, Jose Gutierrez de la Concha wrote:
> On Tue, Aug 8, 2017 at 6:07 PM, James Cowgill  > wrote:
> 
>On 08/08/17 11:29, Jose Gutierrez de la Concha wrote:
>> On Tue, Aug 8, 2017 at 5:01 PM, James Cowgill > 
>> >> wrote:
>>[...]
>>>- If your package does not provide a symbols file, add a dh_makeshlibs
>>>  override so that tight enough dependencies are generated.
>>>
>>>  Using libebml as an example (debian/rules):
>>>  + override_dh_makeshlibs:
>>>  + # For new symbols when compiled with GCC 7
>>>  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
>>> 
> 
> Any ideas how should I handle multiple packages in override_dh_makeshlibs
> zeroc-ice has several packages that include libzeroc-ice3.6,
> libzeroc-freeze3.6
> so I cannot really pass a single package name in -V 

Here's an example. SFML has 5 libraries and 2 of them have specific
dh_makeshlibs calls.

https://sources.debian.net/src/libsfml/2.4.2%2Bdfsg-4/debian/rules/#L18

In short, you use the -p option to apply a -V to a specific package and
then use --remaining-packages if there are any left.

I think that only the libzeroc-ice3.6 package is affected by this
(although you may want to double check) so you may only need to set the
dependencies for that package.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#871305: marked as done (libmuparserx4.0.7: requires rebuild against GCC 7 and symbols/shlibs bump)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Thu, 10 Aug 2017 02:51:08 +
with message-id 
and subject line Bug#871305: fixed in muparserx 4.0.7+dfsg-3
has caused the Debian Bug report #871305,
regarding libmuparserx4.0.7: requires rebuild against GCC 7 and symbols/shlibs 
bump
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.)


-- 
871305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmuparserx4.0.7
Version: 4.0.7+dfsg-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: muparserx
Source-Version: 4.0.7+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Bombe  (supplier of updated muparserx 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, 09 Aug 2017 22:10:58 -0400
Source: muparserx
Binary: libmuparserx4.0.7 libmuparserx-dev
Architecture: source amd64
Version: 4.0.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Andreas Bombe 
Changed-By: Andreas Bombe 
Description:
 libmuparserx-dev - mathematical expression parser library (development files)
 libmuparserx4.0.7 - mathematical expression parser library
Closes: 871305
Changes:
 muparserx (4.0.7+dfsg-3) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.0.1, no changes necessary
   * Adapt to changed conversion operator name mangling in gcc 7
 (Closes: 871305):
 - Add Build-Depends on g++ (>= 4:7)
 - Make dh_makeshlibs depend on 'libmuparserx4.0.7 (>= 4.0.7+dfsg-3~)'
Checksums-Sha1:
 eb7003d14eb04ef24d0c7199400ec9939725bd9b 2039 muparserx_4.0.7+dfsg-3.dsc
 d0cc1a36b577a4730542e4f24724794578d241ed 2636 
muparserx_4.0.7+dfsg-3.debian.tar.xz
 fa61b0aaf7ec5d0d9e0435f4b4cef598cd73fbc0 35014

Bug#865439: marked as done (csound FTBFs on 32bit: "Build killed with signal TERM after 150 minutes of inactivity" during tests)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Thu, 10 Aug 2017 01:49:25 +
with message-id 
and subject line Bug#865439: fixed in csound 1:6.09.1~dfsg-1
has caused the Debian Bug report #865439,
regarding csound FTBFs on 32bit: "Build killed with signal TERM after 150 
minutes of inactivity" during tests
to be marked as done.

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

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


-- 
865439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csound
Version: 1:6.09.0~dfsg-1
Severity: serious

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

...
   dh_auto_test -a -O--parallel
make -j4 test ARGS\+=-j4
make[1]: Entering directory '/<>/obj-i686-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/obj-i686-linux-gnu
  Start  1: testCsoundTypeSystem
  Start  2: testCsoundMessageBuffer
  Start  3: testCsoundOrcSemantics
  Start  4: testCsoundOrcCompileTest
 1/11 Test  #2: testCsoundMessageBuffer ..   Passed0.23 sec
 2/11 Test  #3: testCsoundOrcSemantics ...   Passed0.28 sec
  Start  5: testChannels
  Start  6: testCsoundDataStructures
 3/11 Test  #1: testCsoundTypeSystem .   Passed0.39 sec
 4/11 Test  #5: testChannels .   Passed0.20 sec
 5/11 Test  #6: testCsoundDataStructures .   Passed0.19 sec
  Start  7: testIo
  Start  8: testCircularBuffer
  Start  9: testPerfThread
 6/11 Test  #8: testCircularBuffer ...   Passed0.01 sec
  Start 10: testDebugger
 7/11 Test #10: testDebugger .   Passed0.08 sec
 8/11 Test  #7: testIo ...   Passed0.49 sec
  Start 11: testEngine
 9/11 Test  #4: testCsoundOrcCompileTest .   Passed5.05 sec
10/11 Test  #9: testPerfThread ...   Passed   13.09 sec
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: csound
Source-Version: 1:6.09.1~dfsg-1

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated csound 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, 09 Aug 2017 21:27:24 -0400
Source: csound
Binary: csound csound-data csound-utils libcsound64-6.0 libcsnd6-java 
libcsound64-dev libcsnd-dev libcsoundac-dev pd-csound python-csound 
libcsnd6-6.0v5 liblua5.1-luacsnd libcsoundac6.0v5 python-csoundac csladspa 
libcsound64-doc
Architecture: source
Version: 1:6.09.1~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 csladspa   - LADSPA plugin for Csound
 csound - powerful and versatile sound synthesis software
 csound-data - data files used by the csound library
 csound-utils - miscellaneous utilities for the Csound system
 libcsnd-dev - development files for Csound -- C++ API
 libcsnd6-6.0v5 - C++ bindings for the Csound API
 libcsnd6-java - Java bindings for the Csound API
 libcsound64-6.0 - main library for Csound
 libcsound64-dev - development files for Csound
 libcsound64-doc - Csound API documentation
 libcsoundac-dev - development files for CsoundAC
 libcsoundac6.0v5 - Csound Algorithmic Composition library
 liblua5.1-luacsnd - Lua bindings for the Csound API
 pd-csound  - Csound external for PureData
 python-csound - Python bindings for Csound
 python-csoundac - Python bindings for CsoundAC
Closes: 865439
Changes:
 csound (1:6.09.1~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 6.09.1~dfsg
 - Fixes build failure on 32bit. Closes: #865439
 - Remove unused cmake options from build script
 - Refresh patches
   * Override *_MODULE_INSTALL_DIR to set it to global install dir
   * Add new functions to symbols file
   * Bump standards version

Bug#871578: marked as done (winff: fails to upgrade from 'testing' - trying to overwrite /usr/share/applications/winff.desktop)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Thu, 10 Aug 2017 01:50:30 +
with message-id 
and subject line Bug#871578: fixed in winff 1.5.5-4
has caused the Debian Bug report #871578,
regarding winff: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/applications/winff.desktop
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.)


-- 
871578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: winff
Version: 1.5.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package winff.
  Preparing to unpack .../202-winff_1.5.5-3_all.deb ...
  Unpacking winff (1.5.5-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gux07i/202-winff_1.5.5-3_all.deb (--unpack):
   trying to overwrite '/usr/share/applications/winff.desktop', which is also 
in package winff-data 1.5.5-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gux07i/202-winff_1.5.5-3_all.deb


cheers,

Andreas


winff-data=1.5.5-2_winff=1.5.5-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: winff
Source-Version: 1.5.5-4

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated winff 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, 09 Aug 2017 16:05:27 -0400
Source: winff
Binary: winff winff-gtk2 winff-qt winff-data winff-doc
Architecture: source
Version: 1.5.5-4
Distribution: unstable
Urgency: medium
Maintainer: Paul Gevers 
Changed-By: Paul Gevers 
Description:
 winff  - graphical video and audio batch converter using ffmpeg or avconv
 winff-data - winff data files
 winff-doc  - winff documentation
 winff-gtk2 - GTK+ variant of winff
 winff-qt   - Qt variant of winff
Closes: 871578
Changes:
 winff (1.5.5-4) unstable; urgency=medium
 .
   * Add breaks/replaces in winff binary on winff-data which I forgot to do
 in the previous upload (Closes: #871578) Thanks to Andreas Beckmann
Checksums-Sha1:
 fa327388778859d693947321bb9c5029d8bdab11 1940 winff_1.5.5-4.dsc
 1707ef1f26010d40447e942d177997917874c357 83024 winff_1.5.5-4.debian.tar.xz
Checksums-Sha256:
 40352e58f5380cb6d98c94340c4e5b9ddc17708cf2a08d2d5cee79d6ddff651d 1940 
winff_1.5.5-4.dsc
 3693a147b4604754d227d005080a186079dcc0e3f141c5c24c7efcb32fc95761 83024 
winff_1.5.5-4.debian.tar.xz
Files:
 a4b739c0640a044f51c0d755cbf27354 1940 video optional winff_1.5.5-4.dsc
 28642322e01ace153b002ef04d90c60a 83024 video optional 
winff_1.5.5-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlmMWecACgkQnFyZ6wW9
dQoMTAf+KQ89iX7H3mBsBqeiW+BhS/Wn2jhsu0FJVEn9jQmEFD2F6oQJFp1kBQLH
87a8iSHlSRHuhQMtsI8GtGr63xDOEujx0XCLWQDF+8Z5rJ5Msy7/8gQPeNfZs9uk
njbD06WGB7J+eQCixPoQgvkizLTA9cL+ZrGx2iMLSSBORf5hHZRWij7C02+qzlBh
zSLeG6rLp9+GuOnBbpC8iVFawLNWZMPdbsl4kXTYWUx1fJKAbpSY5GSpfvGGiKF3
d+4ZD+m8qiMTp6L3POY4WQBVkggCqSmEEsSYvalmuPwPd8BhQ5CfvC+FdaUjJlMk
IcZewWHbd5bnyReK30nN2y2ZVp8rCQ==
=IHY1
-END PGP SIGNATURE End Message ---

Processed: Bug#865439 marked as pending

2017-08-09 Thread Debian Bug Tracking System

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

> tag 865439 pending
Bug #865439 [src:csound] csound FTBFs on 32bit: "Build killed with signal TERM 
after 150 minutes of inactivity" during tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865439: marked as pending

2017-08-09 Thread Felipe Sateler

tag 865439 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/csound.git/commit/?id=57e0082

---
commit 57e0082975b7359a681fe975f94ab36c4e5c3978
Author: Felipe Sateler 
Date:   Wed Aug 9 21:28:19 2017 -0400

Release

diff --git a/debian/changelog b/debian/changelog
index c8dbf32..364c9b5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,16 @@
-csound (1:6.09.1~dfsg-1) UNRELEASED; urgency=medium
+csound (1:6.09.1~dfsg-1) unstable; urgency=medium
 
   * New upstream version 6.09.1~dfsg
+- Fixes build failure on 32bit. Closes: #865439
+- Remove unused cmake options from build script
+- Refresh patches
+  * Override *_MODULE_INSTALL_DIR to set it to global install dir
+  * Add new functions to symbols file
+  * Bump standards version
+  * Fix symbols file version for csoundA4.
+Remove debian revision
 
- -- Felipe Sateler   Wed, 12 Jul 2017 21:11:45 -0400
+ -- Felipe Sateler   Wed, 09 Aug 2017 21:27:24 -0400
 
 csound (1:6.09.0~dfsg-1) unstable; urgency=medium

Processed: severity of 864829 is important

2017-08-09 Thread Debian Bug Tracking System

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

> severity 864829 important
Bug #864829 [espeakup] espeakup is incompatible with default pulseaudio
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: retitle 871465 to python3-gpg: depends on, but does not install, ‘tofu’ module

2017-08-09 Thread Debian Bug Tracking System

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

> retitle 871465 python3-gpg: depends on, but does not install, ‘tofu’ module
Bug #871465 [python3-gpg] python3-gpg doesn't ship tofu
Bug #871609 [python3-gpg] dput fails to start with ImportError: cannot import 
name 'tofu'
Changed Bug title to 'python3-gpg: depends on, but does not install, ‘tofu’ 
module' from 'python3-gpg doesn't ship tofu'.
Changed Bug title to 'python3-gpg: depends on, but does not install, ‘tofu’ 
module' from 'dput fails to start with ImportError: cannot import name 'tofu''.
> thanks
Stopping processing here.

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

Processed: retitle 871609 to python3-gpg: depends on, but does not install, ‘tofu’ module

2017-08-09 Thread Debian Bug Tracking System

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

> retitle 871609 python3-gpg: depends on, but does not install, ‘tofu’ module
Bug #871609 [python3-gpg] python3-gpg: depends on, but does not install, ‘tofu’ 
module
Bug #871465 [python3-gpg] python3-gpg: depends on, but does not install, ‘tofu’ 
module
Ignoring request to change the title of bug#871609 to the same title
Ignoring request to change the title of bug#871465 to the same title
> thanks
Stopping processing here.

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

Bug#869000: marked as done (maven-invoker-plugin: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/t

2017-08-09 Thread Debian Bug Tracking System

Your message dated Thu, 10 Aug 2017 00:03:57 +0200
with message-id 
and subject line Re: maven-invoker-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
has caused the Debian Bug report #869000,
regarding maven-invoker-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 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.)


-- 
869000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-invoker-plugin
Version: 2.0.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-invoker-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Apache Maven Invoker Plugin 2.0.0[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:xpp3-reader[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:xpp3-writer[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:java[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 4 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m---

Processed: Re: Bug#864829: screen reader stops speaking

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 - moreinfo
Bug #864829 [pulseaudio] screen reader stops speaking
Removed tag(s) moreinfo.
> reassign -1 espeakup 1:0.80-5
Bug #864829 [pulseaudio] screen reader stops speaking
Bug reassigned from package 'pulseaudio' to 'espeakup'.
No longer marked as found in versions pulseaudio/10.0-1.
Ignoring request to alter fixed versions of bug #864829 to the same values 
previously set
Bug #864829 [espeakup] screen reader stops speaking
Marked as found in versions espeakup/1:0.80-5.
> retitle -1 espeakup is incompatible with default pulseaudio
Bug #864829 [espeakup] screen reader stops speaking
Changed Bug title to 'espeakup is incompatible with default pulseaudio' from 
'screen reader stops speaking'.

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

Bug#864829: screen reader stops speaking

2017-08-09 Thread Felipe Sateler

Control: tags -1 - moreinfo
Control: reassign -1 espeakup 1:0.80-5
Control: retitle -1 espeakup is incompatible with default pulseaudio
configuration

On Thu, Jun 15, 2017 at 6:18 PM, Luke Yelavich  wrote:

> On Thu, Jun 15, 2017 at 11:39:35PM AEST, Mika Hanhijärvi wrote:
> > I am using the Gnome desktop.
> > I have espeakup and Orca installed. I would like to use espeakup on
> console and
> > Orca on desktop. I also would like to be able to switch between text mode
> > console and graphical nome desktop without logging out from the desktop.
>
> ESpeakup is running as root, and everything is running as a user. I think
> the
> easiest solution here is to configure Pulse to run system-wide. I know
> there
> is an option in one of the Pulse configuration files to enable this, but I
> don't think Debian ships a startup script or systemd service file to use
> PulseAudio in system mode. Happy to be corrected.
>

If that is so, then espeakup is incompatible with a default pulseaudio
configuration. Maybe this should be documented somewhere.


On Mon, Jul 3, 2017 at 7:52 AM, Scott Leggett  wrote:

> Hi,
>
> I've been able to reproduce this bug. A not-very-helpful workaround is
> to restart espeakup whenever sound goes missing.
>
> I've dug into the issue a bit and found it discussed on
> pulseaudio-discuss back in 2010. The discussion on the thread seems to
> indicate that espeakup and pulseaudio couldn't coexist at the time due
> to espeakup not being multi-seat aware. Lennart summarised what needs to
> be done to get them working together[0].
>
> I'm not sure what the situation is now. Looking briefly at espeakup
> upstream [1], it doesn't seem to be very active, so maybe the situation is
> the same?
>
> [0]
> https://lists.freedesktop.org/archives/pulseaudio-discuss/20
> 10-January/006033.html
> [1] https://github.com/williamh/espeakup


I'm reassigning this bug to espeakup because it should really be modified
to work as non-root as Lennart suggested. AFAICT, the only reasong for
running as root is to access the softsynth device, but that could be
managed via regular uaccess and group mechanism like /dev/snd/* does. We
shouldn't require running pulseaudio as root, as it would be better if
espeakup would run unprivileged.

I'll leave it to the espeakup maintainers to adjust severity.


-- 

Saludos,
Felipe Sateler

Bug#766298: An update on trust router and release status

2017-08-09 Thread Sam Hartman

> "Petter" == Petter Reinholdtsen  writes:

>> I think shortly after the release of buster, we can close this
>> bug and let moonshot-trust-router migrate into testing.

Petter> Did this time arrive?
Mostly.
I'm working through all the moonshot software  and updating it to new
upstream versions.
moonshot-ui has a new version in experimental.
Working on moonshot-gss-eap, then will work on moonshot-trust-router.

I don't see a reason not to let the new moonshot-trust-router into
testing at least for now.
Near the freeze I'll coordinate with upstream about whether we're
willing to support that version of the protocol for a full Debian
release.

Petter> There is also the OpenSSL 1.1 issue, bug #828441.  -- Happy
Petter> hacking Petter Reinholdtsen

Yep.
That shouldn't be a big problem.

Processed: Re: Bug#871609: dput fails to start with ImportError: cannot import name 'tofu'

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 python3-gpg
Bug #871609 [dput] dput fails to start with ImportError: cannot import name 
'tofu'
Bug reassigned from package 'dput' to 'python3-gpg'.
No longer marked as found in versions dput/1.0.0.
Ignoring request to alter fixed versions of bug #871609 to the same values 
previously set
> forcemerge 871465 -1
Bug #871465 [python3-gpg] python3-gpg doesn't ship tofu
Bug #871609 [python3-gpg] dput fails to start with ImportError: cannot import 
name 'tofu'
Severity set to 'serious' from 'grave'
Added indication that 871609 affects dput
Marked as found in versions gpgme1.0/1.9.0-2.
Merged 871465 871609

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

Bug#871609: dput fails to start with ImportError: cannot import name 'tofu'

2017-08-09 Thread Ben Finney

Control: reassign -1 python3-gpg
Control: forcemerge 871465 -1

On 09-Aug-2017, Aurélien COUDERC wrote:
> After upgrading to 1.0.0 form experimental, dput fails to start with
> the following stack trace:

Thank you for the report.

This has already been reported as bug#871465.

-- 
 \“The restriction of knowledge to an elite group destroys the |
  `\   spirit of society and leads to its intellectual |
_o__)impoverishment.” —Albert Einstein |
Ben Finney 


signature.asc
Description: PGP signature

Bug#871167: marked as done (ros-std-msgs: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-std-msgs: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-std-msgs
Version: 0.5.11-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  1%] Generating Lisp code from std_msgs/Bool.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/Bool.msg -Istd_msgs:/<>/msg -p std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> [  2%] Generating Lisp code from std_msgs/Int32.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/Int32.msg -Istd_msgs:/<>/msg -p std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> [  3%] Generating Lisp code from std_msgs/String.msg
> [  4%] Generating Python from MSG std_msgs/String
> [  6%] Generating C++ code from std_msgs/String.msg
> [  6%] Generating Python from MSG std_msgs/ByteMultiArray
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/String.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> [  7%] Generating Lisp code from std_msgs/Int64MultiArray.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/String.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/ByteMultiArray.msg -Istd_msgs:/<>/msg -p 
> std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/String.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o /<>/obj-x86_64-linux-gnu/devel/include/std_msgs -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/Int64MultiArray.msg -Istd_msgs:/<>/msg -p 
> std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> [  8%] Generating Lisp code from std_msgs/ByteMultiArray.msg
> [ 10%] Generating Python from MSG std_msgs/Bool
> [ 14%] Generating C++ code from std_msgs/ByteMultiArray.msg
> [ 14%] Generating Python from MSG std_msgs/Float32
> [ 14%] Generating Lisp code from std_msgs/Float32.msg
> [ 14%] Generating C++ code from std_msgs/Float32.msg
> [ 14%] Generating Python from MSG std_msgs/Int64MultiArray
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/ByteMultiArray.msg -Istd_msgs:/<>/msg -p 
> std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/Float32.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/ByteMultiArray.msg -Istd_msgs:/<>/msg -p 
> std_msgs -o /<>/obj-x86_64-linux-gnu/devel/include/std_msgs -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/Bool.msg -Istd_msgs:/<>/msg -p std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/Float32.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/std_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/Float32.msg -Istd_msgs:/<>/msg -p std_msgs 
> -o /<>/obj-x86_64-linux-gnu/devel/include/std_msgs -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/Int64MultiArray.msg -Istd_msgs:/<>/msg -p 
> std_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/std_msgs/msg
> [ 15%] Generating C++ code from

Bug#871063: marked as done (ros-navigation-msgs: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-navigation-msgs: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-navigation-msgs
Version: 1.13.0-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 16%] Generating Python from MSG map_msgs/PointCloud2Update
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/map_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/map_msgs/msg/PointCloud2Update.msg 
> -Imap_msgs:/<>/map_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Inav_msgs:/usr/share/nav_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg -p map_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/map_msgs/msg
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 16%] Built target 
> _move_base_msgs_generate_messages_check_deps_MoveBaseResult
> [ 18%] Generating C++ code from map_msgs/PointCloud2Update.msg
> cd /<>/obj-x86_64-linux-gnu/map_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/map_msgs/msg/PointCloud2Update.msg 
> -Imap_msgs:/<>/map_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Inav_msgs:/usr/share/nav_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg -p map_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/map_msgs -e 
> /usr/share/gencpp/cmake/..
> [ 18%] Built target _move_base_msgs_generate_messages_check_deps_MoveBaseGoal
> [ 18%] Built target 
> _move_base_msgs_generate_messages_check_deps_MoveBaseFeedback
> [ 18%] Built target 
> _move_base_msgs_generate_messages_check_deps_MoveBaseAction
> [ 20%] Generating Python from MSG map_msgs/OccupancyGridUpdate
> [ 20%] Built target 
> _move_base_msgs_generate_messages_check_deps_MoveBaseActionGoal
> [ 20%] Built target 
> _move_base_msgs_generate_messages_check_deps_MoveBaseActionFeedback
> make -f 
> move_base_msgs/CMakeFiles/move_base_msgs_generate_messages_lisp.dir/build.make
>  move_base_msgs/CMakeFiles/move_base_msgs_generate_messages_lisp.dir/depend
> cd /<>/obj-x86_64-linux-gnu/map_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/map_msgs/msg/OccupancyGridUpdate.msg 
> -Imap_msgs:/<>/map_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Inav_msgs:/usr/share/nav_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg -p map_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/map_msgs/msg
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> /<>/move_base_msgs 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/move_base_msgs 
> /<>/obj-x86_64-linux-gnu/move_base_msgs/CMakeFiles/move_base_msgs_generate_messages_lisp.dir/DependInfo.cmake
>  --color=
> map_msgs/CMakeFiles/map_msgs_generate_messages_py.dir/build.make:78: recipe 
> for target 
> 'devel/lib/python2.7/dist-packages/map_msgs/msg/_PointCloud2Update.py' failed
> make[3]: *** 
>

Bug#871073: marked as done (ros-geometry-experimental: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-geometry-experimental: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-geometry-experimental
Version: 0.5.13-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  2%] Generating Python from MSG tf2_msgs/LookupTransformActionFeedback
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg/LookupTransformActionFeedback.msg
>  -Itf2_msgs:/<>/tf2_msgs/msg 
> -Itf2_msgs:/<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p tf2_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/tf2_msgs/msg
> [  4%] Generating Lisp code from tf2_msgs/LookupTransformActionGoal.msg
> [  6%] Generating Lisp code from tf2_msgs/LookupTransformActionFeedback.msg
> [  8%] Generating Lisp code from tf2_msgs/TF2Error.msg
> [ 10%] Generating C++ code from tf2_msgs/LookupTransformActionFeedback.msg
> [ 12%] Generating C++ code from tf2_msgs/LookupTransformActionGoal.msg
> [ 14%] Generating Lisp code from tf2_msgs/LookupTransformFeedback.msg
> [ 16%] Generating Lisp code from tf2_msgs/LookupTransformAction.msg
> [ 18%] Generating Python from MSG tf2_msgs/TF2Error
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py 
> /<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg/LookupTransformActionGoal.msg
>  -Itf2_msgs:/<>/tf2_msgs/msg 
> -Itf2_msgs:/<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p tf2_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/tf2_msgs/msg
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py 
> /<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg/LookupTransformActionFeedback.msg
>  -Itf2_msgs:/<>/tf2_msgs/msg 
> -Itf2_msgs:/<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p tf2_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/tf2_msgs/msg
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/tf2_msgs/msg/TF2Error.msg 
> -Itf2_msgs:/<>/tf2_msgs/msg 
> -Itf2_msgs:/<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p tf2_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/tf2_msgs/msg
> [ 20%] Generating Lisp code from tf2_msgs/LookupTransformActionResult.msg
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg/LookupTransformActionFeedback.msg
>  -Itf2_msgs:/<>/tf2_msgs/msg 
> -Itf2_msgs:/<>/obj-x86_64-linux-gnu/devel/share/tf2_msgs/msg 
> -Iactionlib_msgs:/usr/share/actionlib_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p tf2_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/tf2_msgs -e 
> /usr/share/gencpp/cmake/..
> [ 22%] Generating C++ code from tf2_msgs/TF2Error.msg
> [ 28%] Generating C++ code from tf2_msgs/LookupTransformAction.msg
> [ 28%] Generating C++ code from tf2_msgs/LookupTransformFeedback.msg
> [ 28%] Generating Python from MSG tf2_msgs/LookupTransformFeedback
> cd /<>/obj-x86_64-linux-gnu/tf2_msgs && 
>

Bug#871042: marked as done (python-genpy: missing dependency on python-yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding python-genpy: missing dependency on python-yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-genpy
Version: 0.6.6-1
Severity: serious
Control: affects -1 src:ros-bond-core

https://tests.reproducible-builds.org/debian/history/ros-bond-core.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ros-bond-core.html

...
cd /build/1st/ros-bond-core-1.7.18/obj-x86_64-linux-gnu/bond && 
../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
/build/1st/ros-bond-core-1.7.18/bond/msg/Constants.msg 
-Ibond:/build/1st/ros-bond-core-1.7.18/bond/msg 
-Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
/build/1st/ros-bond-core-1.7.18/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/bond/msg
Traceback (most recent call last):
  File "/usr/lib/genpy/genmsg_py.py", line 44, in 
import genpy.generator
  File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 

from . message import Message, SerializationError, DeserializationError, 
MessageException, struct_I
  File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
import yaml
ImportError: No module named yaml
Traceback (most recent call last):
  File "/usr/lib/genpy/genmsg_py.py", line 44, in 
import genpy.generator
  File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 

from . message import Message, SerializationError, DeserializationError, 
MessageException, struct_I
  File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
import yaml
ImportError: No module named yaml
bond/CMakeFiles/bond_generate_messages_py.dir/build.make:66: recipe for target 
'devel/lib/python2.7/dist-packages/bond/msg/_Constants.py' failed
make[3]: *** [devel/lib/python2.7/dist-packages/bond/msg/_Constants.py] Error 1


python-genpy seems to lack a dependency on python-yaml.
--- End Message ---
--- Begin Message ---
Source: ros-genpy
Source-Version: 0.6.6-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-genpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Aug 2017 22:43:19 +0200
Source: ros-genpy
Binary: python-genpy
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-genpy - Python Robot OS message and service generators
Closes: 871042
Changes:
 ros-genpy (0.6.6-2) unstable; urgency=medium
 .
   * Add python-yaml dependency (Closes: #871042)
   * Fix typo
Checksums-Sha1:
 0e9f8d4046b9ea851a02ac10ec90a838dd1dd450 2196 ros-genpy_0.6.6-2.dsc
 3312ffdba60e01bf5eb9ab1ed9eb2cd952c8b309 3316 ros-genpy_0.6.6-2.debian.tar.xz
 5e0c168649db02bbb6c27cd9894de2a51f8f54b9 7146 
ros-genpy_0.6.6-2_source.buildinfo
Checksums-Sha256:
 ed5d156b0fa450d8b27709755d052b8cc301a140850487d3629456e73186afda 2196 
ros-genpy_0.6.6-2.dsc
 a606251178932e067fde8b5027bbcfe0079a417ec5f3f4d393424c9d10c0b2bc 3316 
ros-genpy_0.6.6-2.debian.tar.xz
 51362a7167a182450ba2d75d2b33c3d59dc33dde4510983c727a2d2bde718546 7146 
ros-genpy_0.6.6-2_source.buildinfo
Files:
 8039e84ddd0b3d903f56374cbac2bf15 2196 python optional ros-genpy_0.6.6-2.dsc
 39af3045d7a58a730f81fd224bc2c16b 3316 python optional 
ros-genpy_0.6.6-2.debian.tar.xz
 b26352b7bae638685c921c3d9eb1e371 7146 python optional 
ros-genpy_0.6.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlmLg1oUHGpzcHJpY2tl

Bug#871165: marked as done (ros-ros-comm: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-ros-comm: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-ros-comm
Version: 1.12.6-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/build'
> cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
> /<> /<>/tools/topic_tools /<>/build 
> /<>/build/tools/topic_tools 
> /<>/build/tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/DependInfo.cmake
>  --color=
> [  9%] Generating Lisp code from roscpp/Logger.msg
> cd /<>/build/clients/roscpp && 
> ../../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/clients/roscpp/msg/Logger.msg 
> -Iroscpp:/<>/clients/roscpp/msg -p roscpp -o 
> /<>/build/devel/share/common-lisp/ros/roscpp/msg
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> Scanning dependencies of target topic_tools_generate_messages_py
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> make[3]: Leaving directory '/<>/build'
> make -f 
> tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/build.make 
> tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/build
> clients/roscpp/CMakeFiles/roscpp_generate_messages_py.dir/build.make:69: 
> recipe for target 'devel/lib/python2.7/dist-packages/roscpp/msg/_Logger.py' 
> failed
> make[3]: *** [devel/lib/python2.7/dist-packages/roscpp/msg/_Logger.py] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/ros-ros-comm_1.12.6-2_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: ros-genpy
Source-Version: 0.6.6-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-genpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Aug 2017 22:43:19 +0200
Source: ros-genpy
Binary: python-genpy
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-genpy - Python Robot OS message and service generators
Closes: 871042
Changes:
 ros-genpy (0.6.6-2) unstable; urgency=medium
 .
   * Add python-yaml dependency (Closes: #871042)
   * Fix typo
Checksums-Sha1:
 0e9f8d4046b9ea851a02ac10ec90a838dd1dd450 2196 ros-genpy_0.6.6-2.dsc
 3312ffdba60e01bf5eb9ab1ed9eb2cd952c8b309 3316 ros-genpy_0.6.6-2.debian.tar.xz
 5e0c168649db02bbb6c27cd9894de2a51f8f54b9 7146 
ros-genpy_0.6.6-2_source.buildinfo
Checksums-Sha256:
 ed5d156b0fa450d8b27709755d052b8cc301a140850487d3629456e73186afda 2196 
ros-genpy_0.6.6-2.dsc
 a606251178932e067fde8b5027bbcfe0079a417ec5f3f4d393424c9d10c0b2bc 3316

Bug#871090: marked as done (ros-common-msgs: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-common-msgs: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-common-msgs
Version: 1.12.5-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  3%] Generating C++ code from diagnostic_msgs/DiagnosticStatus.msg
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/diagnostic_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/diagnostic_msgs/msg/DiagnosticStatus.msg 
> -Idiagnostic_msgs:/<>/diagnostic_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p diagnostic_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/diagnostic_msgs -e 
> /usr/share/gencpp/cmake/..
> [  3%] Built target _visualization_msgs_generate_messages_check_deps_Marker
> [  3%] Generating C++ code from diagnostic_msgs/KeyValue.msg
> cd /<>/obj-x86_64-linux-gnu/diagnostic_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/diagnostic_msgs/msg/KeyValue.msg 
> -Idiagnostic_msgs:/<>/diagnostic_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p diagnostic_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/diagnostic_msgs -e 
> /usr/share/gencpp/cmake/..
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> actionlib_msgs/CMakeFiles/actionlib_msgs_generate_messages_py.dir/build.make:68:
>  recipe for target 
> 'devel/lib/python2.7/dist-packages/actionlib_msgs/msg/_GoalStatus.py' failed
> make[3]: *** 
> [devel/lib/python2.7/dist-packages/actionlib_msgs/msg/_GoalStatus.py] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/ros-common-msgs_1.12.5-3_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: ros-genpy
Source-Version: 0.6.6-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-genpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Aug 2017 22:43:19 +0200
Source: ros-genpy
Binary: python-genpy
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers

Bug#871071: marked as done (ros-geometry: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-geometry: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-geometry
Version: 1.11.8-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 19%] Generating C++ code from tf/tfMessage.msg
> [ 19%] Generating Python code from SRV tf/FrameGraph
> [ 19%] Generating Lisp code from tf/tfMessage.msg
> [ 19%] Generating Lisp code from tf/FrameGraph.srv
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/tf/msg/tfMessage.msg 
> -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/tf/msg
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/tf/msg/tfMessage.msg -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/include/tf -e 
> /usr/share/gencpp/cmake/..
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/gensrv_py.py 
> /<>/tf/srv/FrameGraph.srv -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/tf/srv
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/tf/srv/FrameGraph.srv 
> -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/tf/srv
> [ 25%] Generating Python from MSG tf/tfMessage
> [ 25%] Generating C++ code from tf/FrameGraph.srv
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/tf/msg/tfMessage.msg -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/tf/msg
> cd /<>/obj-x86_64-linux-gnu/tf && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/tf/srv/FrameGraph.srv -Itf:/<>/tf/msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p tf -o 
> /<>/obj-x86_64-linux-gnu/devel/include/tf -e 
> /usr/share/gencpp/cmake/..
> Traceback (most recent call last):
>   File "/usr/lib/genpy/gensrv_py.py", line 43, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> tf/CMakeFiles/tf_generate_messages_py.dir/build.make:77: recipe for target 
> 'devel/lib/python2.7/dist-packages/tf/srv/_FrameGraph.py' failed
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
> make[3]: *** [devel/lib/python2.7/dist-packages/tf/srv/_FrameGraph.py] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/ros-geometry_1.11.8-4_unstable.log

A

Bug#871084: marked as done (ros-pcl-msgs: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-pcl-msgs: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-pcl-msgs
Version: 0.2.0-6
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  7%] Generating Python from MSG pcl_msgs/PolygonMesh
> [ 15%] Generating C++ code from pcl_msgs/PolygonMesh.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/PolygonMesh.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/pcl_msgs/msg
> [ 23%] Generating Lisp code from pcl_msgs/Vertices.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/PolygonMesh.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/pcl_msgs -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/Vertices.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/pcl_msgs/msg
> [ 30%] Generating Python from MSG pcl_msgs/PointIndices
> [ 38%] Generating Lisp code from pcl_msgs/PointIndices.msg
> [ 46%] Generating Python from MSG pcl_msgs/ModelCoefficients
> [ 53%] Generating C++ code from pcl_msgs/PointIndices.msg
> [ 61%] Generating Python from MSG pcl_msgs/Vertices
> [ 69%] Generating Lisp code from pcl_msgs/ModelCoefficients.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/PointIndices.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/pcl_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/PointIndices.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/pcl_msgs/msg
> [ 84%] Generating Lisp code from pcl_msgs/PolygonMesh.msg
> [ 84%] Generating C++ code from pcl_msgs/Vertices.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/ModelCoefficients.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/pcl_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/PointIndices.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/pcl_msgs -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/Vertices.msg -Ipcl_msgs:/<>/msg 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p pcl_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/pcl_msgs/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/ModelCoefficients.msg -Ipcl_msgs:/<>/msg 
>

Bug#871081: marked as done (ros-image-common: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-image-common: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-image-common
Version: 1.11.11-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 32%] Generating C++ code from polled_camera/GetPolledImage.srv
> [ 35%] Generating Lisp code from polled_camera/GetPolledImage.srv
> cd /<>/obj-x86_64-linux-gnu/polled_camera && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/polled_camera/srv/GetPolledImage.srv 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p polled_camera -o 
> /<>/obj-x86_64-linux-gnu/devel/include/polled_camera -e 
> /usr/share/gencpp/cmake/..
> cd /<>/obj-x86_64-linux-gnu/polled_camera && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py 
> /<>/polled_camera/srv/GetPolledImage.srv 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p polled_camera -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/polled_camera/srv
> [ 37%] Generating Python code from SRV polled_camera/GetPolledImage
> cd /<>/obj-x86_64-linux-gnu/polled_camera && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/gensrv_py.py 
> /<>/polled_camera/srv/GetPolledImage.srv 
> -Isensor_msgs:/usr/share/sensor_msgs/cmake/../msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -Igeometry_msgs:/usr/share/geometry_msgs/cmake/../msg -p polled_camera -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/polled_camera/srv
> Traceback (most recent call last):
>   File "/usr/lib/genpy/gensrv_py.py", line 43, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> polled_camera/CMakeFiles/polled_camera_generate_messages_py.dir/build.make:66:
>  recipe for target 
> 'devel/lib/python2.7/dist-packages/polled_camera/srv/_GetPolledImage.py' 
> failed
> make[3]: *** 
> [devel/lib/python2.7/dist-packages/polled_camera/srv/_GetPolledImage.py] 
> Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/ros-image-common_1.11.11-2_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: ros-genpy
Source-Version: 0.6.6-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-genpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Aug 2017 22:43:19 +0200
Source: ros-genpy
Binary: python-genpy
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers

Bug#871174: marked as done (ros-dynamic-reconfigure: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-dynamic-reconfigure: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-dynamic-reconfigure
Version: 1.5.46-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  5%] Generating C++ code from dynamic_reconfigure/IntParameter.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/IntParameter.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/include/dynamic_reconfigure -e 
> /usr/share/gencpp/cmake/..
> [  8%] Generating Python from MSG dynamic_reconfigure/ConfigDescription
> [ 10%] Generating Lisp code from dynamic_reconfigure/ConfigDescription.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/ConfigDescription.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/dynamic_reconfigure/msg
> [ 13%] Generating Python from MSG dynamic_reconfigure/StrParameter
> [ 18%] Generating Lisp code from dynamic_reconfigure/IntParameter.msg
> [ 18%] Generating C++ code from dynamic_reconfigure/SensorLevels.msg
> [ 21%] Generating Python from MSG dynamic_reconfigure/SensorLevels
> [ 24%] Generating Lisp code from dynamic_reconfigure/SensorLevels.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/ConfigDescription.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/dynamic_reconfigure/msg
> [ 27%] Generating Python from MSG dynamic_reconfigure/IntParameter
> [ 29%] Generating Lisp code from dynamic_reconfigure/StrParameter.msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/IntParameter.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/dynamic_reconfigure/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/StrParameter.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/dynamic_reconfigure/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/msg/SensorLevels.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/include/dynamic_reconfigure -e 
> /usr/share/gencpp/cmake/..
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/SensorLevels.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/dynamic_reconfigure/msg
> [ 35%] Generating C++ code from dynamic_reconfigure/ParamDescription.msg
> [ 35%] Generating Python from MSG dynamic_reconfigure/ParamDescription
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/SensorLevels.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/dynamic_reconfigure/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/msg/IntParameter.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/dynamic_reconfigure/msg
> catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genlisp/gen_lisp.py 
> /<>/msg/StrParameter.msg 
> -Idynamic_reconfigure:/<>/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p dynamic_reconfigure -o 
>

Bug#871123: marked as done (ros-bond-core: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-bond-core: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-bond-core
Version: 1.7.18-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  9%] Generating Lisp code from bond/Status.msg
> [ 18%] Generating C++ code from bond/Status.msg
> [ 27%] Generating Python from MSG bond/Constants
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/bond/msg/Status.msg 
> -Ibond:/<>/bond/msg -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/bond/msg
> [ 36%] Generating Lisp code from bond/Constants.msg
> [ 45%] Generating Python from MSG bond/Status
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/bond/msg/Status.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/include/bond -e 
> /usr/share/gencpp/cmake/..
> [ 54%] Generating C++ code from bond/Constants.msg
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/bond/msg/Constants.msg 
> -Ibond:/<>/bond/msg -Istd_msgs:/usr/share/std_msgs/cmake/../msg 
> -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/bond/msg
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/bond/msg/Status.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
> cd /<>/obj-x86_64-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-x86_64-linux-gnu/devel/include/bond -e 
> /usr/share/gencpp/cmake/..
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> Traceback (most recent call last):
>   File "/usr/lib/genpy/genmsg_py.py", line 44, in 
> import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in 
> 
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in 
> 
> import yaml
> ImportError: No module named yaml
> bond/CMakeFiles/bond_generate_messages_py.dir/build.make:66: recipe for 
> target 'devel/lib/python2.7/dist-packages/bond/msg/_Constants.py' failed
> make[3]: *** [devel/lib/python2.7/dist-packages/bond/msg/_Constants.py] Error 
> 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/ros-bond-core_1.7.18-2_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: ros-genpy
Source-Version: 0.6.6-2

We believe that the bug

Bug#871103: marked as done (ros-ros-comm-msgs: FTBFS: ImportError: No module named yaml)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 22:07:01 +
with message-id 
and subject line Bug#871042: fixed in ros-genpy 0.6.6-2
has caused the Debian Bug report #871042,
regarding ros-ros-comm-msgs: FTBFS: ImportError: No module named yaml
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.)


-- 
871042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-ros-comm-msgs
Version: 1.11.2-6
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  5%] Generating Lisp code from rosgraph_msgs/Clock.msg
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/rosgraph_msgs/msg/Clock.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/rosgraph_msgs/msg
> [ 10%] Generating Lisp code from rosgraph_msgs/TopicStatistics.msg
> [ 15%] Generating Python from MSG rosgraph_msgs/TopicStatistics
> [ 20%] Generating Python from MSG rosgraph_msgs/Clock
> [ 25%] Generating Lisp code from rosgraph_msgs/Log.msg
> [ 30%] Generating Python from MSG rosgraph_msgs/Log
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py 
> /<>/rosgraph_msgs/msg/TopicStatistics.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/rosgraph_msgs/msg
> [ 35%] Generating C++ code from rosgraph_msgs/TopicStatistics.msg
> [ 40%] Generating C++ code from rosgraph_msgs/Log.msg
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/rosgraph_msgs/msg/TopicStatistics.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/rosgraph_msgs/msg
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/rosgraph_msgs/msg/Clock.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/rosgraph_msgs/msg
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python 
> /usr/lib/genlisp/gen_lisp.py /<>/rosgraph_msgs/msg/Log.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/rosgraph_msgs/msg
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/rosgraph_msgs/msg/Log.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/rosgraph_msgs/msg
> [ 45%] Generating Lisp code from std_srvs/Empty.srv
> [ 50%] Generating C++ code from std_srvs/Trigger.srv
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/rosgraph_msgs/msg/TopicStatistics.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/rosgraph_msgs -e 
> /usr/share/gencpp/cmake/..
> [ 55%] Generating Lisp code from std_srvs/Trigger.srv
> [ 60%] Generating C++ code from std_srvs/SetBool.srv
> cd /<>/obj-x86_64-linux-gnu/rosgraph_msgs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/rosgraph_msgs/msg/Log.msg 
> -Irosgraph_msgs:/<>/rosgraph_msgs/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p rosgraph_msgs -o 
> /<>/obj-x86_64-linux-gnu/devel/include/rosgraph_msgs -e 
> /usr/share/gencpp/cmake/..
> [ 65%] Generating C++ code from std_srvs/Empty.srv
> cd /<>/obj-x86_64-linux-gnu/std_srvs && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py 
> /<>/std_srvs/srv/Trigger.srv -p std_srvs -o 
>

Processed: forcibly merging 871583 871607

2017-08-09 Thread Debian Bug Tracking System

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

> forcemerge 871583 871607
Bug #871583 {Done: Mike Hommey } [firefox-esr] 
firefox-esr: OOOBUpdate to 52.3.0 borks Firefox graphics
Bug #871607 [firefox-esr] firefox-esr: the display of the menu and the tabs is 
completely broken
Severity set to 'important' from 'grave'
Marked Bug as done
The source firefox-esr and version 52.3.0esr-2 do not appear to match any 
binary packages
Marked as fixed in versions firefox-esr/52.3.0esr-2.
Merged 871583 871607
> thanks
Stopping processing here.

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

Processed: Re: unattended-upgrades FTBFS: FAIL: test_untrusted_check_without_conffile_check

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> fixed -1 0.94
Bug #869088 [src:unattended-upgrades] unattended-upgrades FTBFS: FAIL: 
test_untrusted_check_without_conffile_check
Marked as fixed in versions unattended-upgrades/0.94.

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

Bug#869088: unattended-upgrades FTBFS: FAIL: test_untrusted_check_without_conffile_check

2017-08-09 Thread Balint Reczey

Control: fixed -1 0.94

On Sun, 6 Aug 2017 16:31:54 +0200 Andreas Beckmann  wrote:
> Hi Julian,
>
> are you aware of the FTBFS in your NMU?

It is now fixed in the latest upload.

Thanks,
Balint

>
> Andreas
>
> On Thu, 20 Jul 2017 15:00:58 +0300 Adrian Bunk  wrote:
> > Source: unattended-upgrades
> > Version: 0.93.1+nmu2
> > Severity: serious
> >
> >
https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.93.1%2Bnmu2=1500545189=0
> >
> > ...
> > ==
> > FAIL: test_untrusted_check_without_conffile_check
(__main__.TestUntrusted)
> > --
> > Traceback (most recent call last):
> > File "./test_untrusted.py", line 49, in
test_untrusted_check_without_conffile_check
> > "Can not find '%s' in '%s'" % (needle, haystack))
> > AssertionError: False is not true : Can not find 'DEBUG InstCount=0
DelCount=0 BrokenCount=0' in '2017-07-20 10:06:26,539 INFO Initial
blacklisted packages:
> > 2017-07-20 10:06:26,539 INFO Initial whitelisted packages:
> > 2017-07-20 10:06:26,539 INFO Starting unattended upgrades script
> > 2017-07-20 10:06:26,540 INFO Allowed origins are:
['o=Ubuntu,a=lucid-security']
> > 2017-07-20 10:06:26,560 DEBUG pkgs that look like they should be
upgraded:
> > 2017-07-20 10:06:26,561 DEBUG fetch.run() result: 0
> > 2017-07-20 10:06:26,562 DEBUG dpkg is configured not to cause
conffile prompts
> > 2017-07-20 10:06:26,562 INFO No packages found that can be upgraded
unattended and no pending auto-removals
> > '
> >
> > --
> > Ran 1 test in 0.026s
> >
> > FAILED (failures=1)
> > Makefile:6: recipe for target 'check' failed
> > make[2]: *** [check] Error 1
> > make[2]: Leaving directory
'/<>/unattended-upgrades-0.93.1+nmu2/test'
> > debian/rules:15: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 2
> >
> >
>
>

Bug#869088: marked as done (unattended-upgrades FTBFS: FAIL: test_untrusted_check_without_conffile_check)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 9 Aug 2017 17:58:46 -0400
with message-id <4fb7b2ac-dbf3-167f-200b-530c6072c...@canonical.com>
and subject line Re: unattended-upgrades FTBFS: FAIL: 
test_untrusted_check_without_conffile_check
has caused the Debian Bug report #869088,
regarding unattended-upgrades FTBFS: FAIL: 
test_untrusted_check_without_conffile_check
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.)


-- 
869088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unattended-upgrades
Version: 0.93.1+nmu2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.93.1%2Bnmu2=1500545189=0

...
==
FAIL: test_untrusted_check_without_conffile_check (__main__.TestUntrusted)
--
Traceback (most recent call last):
  File "./test_untrusted.py", line 49, in 
test_untrusted_check_without_conffile_check
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'DEBUG InstCount=0 DelCount=0 
BrokenCount=0' in '2017-07-20 10:06:26,539 INFO Initial blacklisted packages: 
2017-07-20 10:06:26,539 INFO Initial whitelisted packages: 
2017-07-20 10:06:26,539 INFO Starting unattended upgrades script
2017-07-20 10:06:26,540 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-07-20 10:06:26,560 DEBUG pkgs that look like they should be upgraded: 
2017-07-20 10:06:26,561 DEBUG fetch.run() result: 0
2017-07-20 10:06:26,562 DEBUG dpkg is configured not to cause conffile prompts
2017-07-20 10:06:26,562 INFO No packages found that can be upgraded unattended 
and no pending auto-removals
'

--
Ran 1 test in 0.026s

FAILED (failures=1)
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/<>/unattended-upgrades-0.93.1+nmu2/test'
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Control: fixed -1 0.94

On Sun, 6 Aug 2017 16:31:54 +0200 Andreas Beckmann  wrote:
> Hi Julian,
>
> are you aware of the FTBFS in your NMU?

It is now fixed in the latest upload.

Thanks,
Balint

>
> Andreas
>
> On Thu, 20 Jul 2017 15:00:58 +0300 Adrian Bunk  wrote:
> > Source: unattended-upgrades
> > Version: 0.93.1+nmu2
> > Severity: serious
> >
> >
https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.93.1%2Bnmu2=1500545189=0
> >
> > ...
> > ==
> > FAIL: test_untrusted_check_without_conffile_check
(__main__.TestUntrusted)
> > --
> > Traceback (most recent call last):
> > File "./test_untrusted.py", line 49, in
test_untrusted_check_without_conffile_check
> > "Can not find '%s' in '%s'" % (needle, haystack))
> > AssertionError: False is not true : Can not find 'DEBUG InstCount=0
DelCount=0 BrokenCount=0' in '2017-07-20 10:06:26,539 INFO Initial
blacklisted packages:
> > 2017-07-20 10:06:26,539 INFO Initial whitelisted packages:
> > 2017-07-20 10:06:26,539 INFO Starting unattended upgrades script
> > 2017-07-20 10:06:26,540 INFO Allowed origins are:
['o=Ubuntu,a=lucid-security']
> > 2017-07-20 10:06:26,560 DEBUG pkgs that look like they should be
upgraded:
> > 2017-07-20 10:06:26,561 DEBUG fetch.run() result: 0
> > 2017-07-20 10:06:26,562 DEBUG dpkg is configured not to cause
conffile prompts
> > 2017-07-20 10:06:26,562 INFO No packages found that can be upgraded
unattended and no pending auto-removals
> > '
> >
> > --
> > Ran 1 test in 0.026s
> >
> > FAILED (failures=1)
> > Makefile:6: recipe for target 'check' failed
> > make[2]: *** [check] Error 1
> > make[2]: Leaving directory
'/<>/unattended-upgrades-0.93.1+nmu2/test'
> > debian/rules:15: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 2
> >
> >
>
>--- End Message ---

Bug#871085: [lu...@debian.org: Bug#871085: libbpp-phyl: FTBFS: collect2: error: ld returned 1 exit status]

2017-08-09 Thread Julien Yann Dutheil

Dear all,

I have committed a fix to the libraries. I propagated the
unforce-cxxflags.patch which was in libbpp-core to the other libs.
Hopefully this should remove the -Wall tags and allow the libraries to
compile smoothly. The deprecation warning is already addressed upstream and
modifications will be included in the next version.

Best,

Julien.

On Tue, Aug 8, 2017 at 4:09 PM, Andreas Tille  wrote:

> Hi Julien,
>
> On Mon, Aug 07, 2017 at 10:31:08PM +0200, Julien Yann Dutheil wrote:
> > These are deprecation warnings that we have now fixed upstream, but
> > including those fixes would mean making a new release. Would it be ok to
> > simply make a patch to remove the very strict -W g++ tags that we use
> > instead, for this version at least?
>
> Either way is fine.  If you think a new release is sensible - just do it
> as upstream.  A quilt patch fixing the actual problem in Debian is fine
> as well for sure.
>
> > Will investigate how to subscribe to the bug feeds.
>
> You can subscribe to single packages here:
>
>https://packages.qa.debian.org/common/index.html
>
> Alternatively you can subscribe the Debian Med maintainers list
>
>https://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> debian-med-packaging
>
> and get notification about all packages maintained by the Debian Med
> team which could be interesting but might be a bit noisy for your taste.
> Just check the archive of the list if you can bear that amount.
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#869015: marked as done (maven-deploy-plugin: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/to

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 9 Aug 2017 23:55:40 +0200
with message-id 
and subject line Re: maven-deploy-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
has caused the Debian Bug report #869015,
regarding maven-deploy-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 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.)


-- 
869015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-deploy-plugin
Version: 2.8.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-deploy-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Apache Maven Deploy Plugin 2.8.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:helpmojo[m 
> [1m(help-goal)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if

Bug#871066: marked as done (scummvm-tools: FTBFS: cc1plus: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 21:44:27 +
with message-id 
and subject line Bug#871066: fixed in scummvm-tools 1.9.0-2
has caused the Debian Bug report #871066,
regarding scummvm-tools: FTBFS: cc1plus: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
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.)


-- 
871066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scummvm-tools
Version: 1.9.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
> g++ -Wall -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -W -Wno-unused-parameter -Wno-empty-body -std=c++11  
> -Wno-long-long -Wno-multichar -Wno-unknown-pragmas -Wno-reorder 
> -Wpointer-arith -Wcast-qual -Wshadow -Wnon-virtual-dtor -Wwrite-strings 
> -fcheck-new -DHAVE_CONFIG_H -DPOSIX -I. -I.  -lboost_program_options  
> -Wl,-z,relro -Wl,-z,now -lm -I./decompiler/test/cxxtest -Wno-format -o 
> decompiler/test/runner decompiler/test/runner.cpp common/file.o 
> decompiler/codegen.o decompiler/control_flow.o decompiler/disassembler.o 
> decompiler/instruction.o decompiler/simple_disassembler.o decompiler/value.o 
> decompiler/scummv6/disassembler.o decompiler/scummv6/codegen.o 
> decompiler/scummv6/engine.o decompiler/kyra/disassembler.o 
> decompiler/kyra/codegen.o decompiler/kyra/engine.o 
> decompiler/test/disassembler/pasc.o decompiler/test/disassembler/subopcode.o 
> decompiler/unknown_opcode.o
> cc1plus: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> In file included from ./decompiler/instruction.h:32:0,
>  from ./decompiler/graph.h:25,
>  from ./decompiler/control_flow.h:25,
>  from ./decompiler/test/cfg_test.h:24,
>  from decompiler/test/runner.cpp:18:
> ./decompiler/value.h:93:31: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual bool isSignedValue() throw(WrongTypeException);
>^
> ./decompiler/value.h:101:28: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual int32 getSigned() throw(WrongTypeException);
> ^
> ./decompiler/value.h:109:31: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual uint32 getUnsigned() throw(WrongTypeException);
>^
> ./decompiler/value.h:140:28: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual ValuePtr negate() throw(WrongTypeException);
> ^
> ./decompiler/value.h:189:23: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   bool isSignedValue() throw(WrongTypeException);
>^
> ./decompiler/value.h:190:20: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   int32 getSigned() throw(WrongTypeException);
> ^
> ./decompiler/value.h:191:23: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   uint32 getUnsigned() throw(WrongTypeException);
>^
> ./decompiler/value.h:211:20: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   int32 getSigned() throw(WrongTypeException);
> ^
> In file included from ./decompiler/instruction.h:32:0,
>  from ./decompiler/graph.h:25,
>  from ./decompiler/control_flow.h:25,
>  from ./decompiler/test/cfg_test.h:24,
>  from decompiler/test/runner.cpp:18:
> ./decompiler/value.h:235:23: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   uint32 getUnsigned() throw(WrongTypeException);
>^
> ./decompiler/value.h:338:28: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual ValuePtr negate() throw(WrongTypeException);
> ^
> ./decompiler/value.h:380:28: warning: dynamic exception specifications are 
> deprecated in C++11 [-Wdeprecated]
>   virtual

Bug#871609: dput fails to start with ImportError: cannot import name 'tofu'

2017-08-09 Thread Aurélien COUDERC

Package: dput
Version: 1.0.0
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading to 1.0.0 form experimental, dput fails to start with the
following stack trace:

Traceback (most recent call last):
  File "/usr/bin/dput", line 11, in 
load_entry_point('dput==1.0.0', 'console_scripts', 'execute-dput')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 561, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2649,
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2303,
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2309,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/dput/dput/dput.py", line 28, in 
from . import crypto
  File "/usr/share/dput/dput/crypto.py", line 14, in 
import gpg
  File "/usr/lib/python3/dist-packages/gpg/__init__.py", line 101, in 
from . import core
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 36, in 
from . import constants
  File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line 28, in

from . import data, keylist, sig, tofu # The subdirs.
ImportError: cannot import name 'tofu'



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

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

Versions of packages dput depends on:
ii  python33.5.3-3
ii  python3-debian 0.1.30
ii  python3-gpg1.9.0-2
ii  python3-pkg-resources  36.0.1-1

dput recommends no packages.

Versions of packages dput suggests:
ii  lintian 2.5.52
pn  mini-dinstall   
ii  openssh-client  1:7.5p1-5
ii  rsync   3.1.2-2

-- no debconf information

Bug#871607: firefox-esr: the display of the menu and the tabs is completely broken

2017-08-09 Thread Vincent Lefevre

On 2017-08-09 22:45:11 +0200, Vincent Lefevre wrote:
> Package: firefox-esr
> Version: 52.3.0esr-1
> Severity: grave
> Justification: renders package unusable
> 
> The display of the menu and the tabs is completely broken
> (partly invisible).

I've attached a snapshot of the top of my browser window.

This problem also occurs with -safe-mode.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#871586: courier FTBFS with libcourier-unicode-dev 2.0-1

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +confirmed +pending
Bug #871586 [src:courier] courier FTBFS with libcourier-unicode-dev 2.0-1
Added tag(s) confirmed.
Bug #871586 [src:courier] courier FTBFS with libcourier-unicode-dev 2.0-1
Added tag(s) pending.

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

Bug#871586: courier FTBFS with libcourier-unicode-dev 2.0-1

2017-08-09 Thread Markus Wanner

Control: tags -1 +confirmed +pending

Hi,

thanks for filing this issue. Looks like courier 0.77.0 is required
together with the newer libcourier-unicode version. An upload of the
former should be ready soon-ish.

Kind Regards

Markus Wanner

Bug#871334: marked as done (erlang-cherly: FTBFS: ERROR: OTP release 20 does not match required regex R14B04|R15B02|R15B03|R16B|17|18|19)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 20:53:55 +
with message-id 
and subject line Bug#871334: fixed in erlang-cherly 0.12.8+dfsg-7
has caused the Debian Bug report #871334,
regarding erlang-cherly: FTBFS: ERROR: OTP release 20 does not match required 
regex R14B04|R15B02|R15B03|R16B|17|18|19
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.)


-- 
871334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cherly
Version: 0.12.8+dfsg-6
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
>  debian/rules build
> dh build --buildsystem=rebar --with rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> configure
> make[1]: Nothing to be done for 'configure'.
>dh_auto_build -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> build
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-cherly-0.12.8+dfsg/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file 
> "/<>/erlang-cherly-0.12.8+dfsg/src/cherly.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps  : []
> DEBUG: Plugins requested while processing 
> /<>/erlang-cherly-0.12.8+dfsg: []
> DEBUG: Predirs: []
> ==> erlang-cherly-0.12.8+dfsg (compile)
> DEBUG: Matched required ERTS version: 9.0.1 -> .*
> ERROR: OTP release 20 does not match required regex 
> R14B04|R15B02|R15B03|R16B|17|18|19
> ERROR: compile failed while processing 
> /<>/erlang-cherly-0.12.8+dfsg: rebar_abort
> /usr/share/dh-rebar/make/dh-rebar.Makefile:125: recipe for target 
> 'rebar_compile' failed
> make[1]: *** [rebar_compile] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/erlang-cherly_0.12.8+dfsg-6_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: erlang-cherly
Source-Version: 0.12.8+dfsg-7

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated erlang-cherly 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Aug 2017 04:29:57 +0900
Source: erlang-cherly
Binary: erlang-cherly
Architecture: source amd64
Version: 0.12.8+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: LeoFS maintainers team 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-cherly - Cherly (sher-lee) is an in-VM caching library for Erlang
Closes: 871334
Changes:
 erlang-cherly (0.12.8+dfsg-7) unstable; urgency=medium
 .
   * Support OTP release 20. (Closes: #871334)
 - Update patches/add_support_r17_and_r18.
   * Update debian/control.
 - Bump Standards-Version to 4.0.0.
 - Cleanup debian/control by cme.
Checksums-Sha1:
 762d137d6da764eeb873b662b52948bf8711f1de 2108 erlang-cherly_0.12.8+dfsg-7.dsc
 78089d86602be3da5576d6e86aad36220235aa94 3936 
erlang-cherly_0.12.8+dfsg-7.debian.tar.xz
 50ff8b42a0a9dd26f91fc2fd53d1e22858095010 35388 
erlang-cherly-dbgsym_0.12.8+dfsg-7_amd64.deb
 625acb1d411c03f6d1d0b2165e321ac9a4fe9868 9516 
erlang-cherly_0.12.8+dfsg-7_amd64.buildinfo
 609dd376f4236f3c3b50a6ee7a338639d081ae4d 25690 
erlang-cherly_0.12.8+dfsg-7_amd64.deb
Checksums-Sha256:

Bug#871607: firefox-esr: the display of the menu and the tabs is completely broken

2017-08-09 Thread Vincent Lefevre

Package: firefox-esr
Version: 52.3.0esr-1
Severity: grave
Justification: renders package unusable

The display of the menu and the tabs is completely broken
(partly invisible).

-- Package-specific info:

-- Extensions information
Name: -Global Styles- userstyle
Status: enabled

Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: AlloCiné userstyle
Status: enabled

Name: allocine-imdb greasemonkey-user-script
Status: enabled

Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: cac-imdb greasemonkey-user-script
Status: enabled

Name: Cinémathèque Française userstyle
Status: enabled

Name: Classic Theme Restorer
Location: ${PROFILE_EXTENSIONS}/classicthemeresto...@arist2noia4dev.xpi
Status: enabled

Name: Combine Stop/Reload buttons userstyle
Status: enabled

Name: Config Descriptions
Location: ${PROFILE_EXTENSIONS}/{1823e248-6bf4-f6f1-7901-65a68e8b6c1e}.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Dictionnaire français dictionary
Location: ${PROFILE_EXTENSIONS}/fr-dicolle...@dictionaries.addons.mozilla.org
Status: enabled

Name: Different cursor for links that open in new windows userstyle
Status: enabled

Name: Disable autocomplete userstyle
Status: user-disabled

Name: Disable marquee userstyle
Status: user-disabled

Name: Filmsite.org userstyle
Status: enabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Flagfox
Location: ${PROFILE_EXTENSIONS}/{1018e4d6-728f-4b20-ad56-37578a4de76b}.xpi
Status: enabled

Name: FlashStopper
Location: ${PROFILE_EXTENSIONS}/flashstop...@byo.co.il.xpi
Status: enabled

Name: Font Finder
Location: ${PROFILE_EXTENSIONS}/{a658a273-612e-489e-b4f1-5344e672f4f5}.xpi
Status: enabled

Name: FxIF
Location: ${PROFILE_EXTENSIONS}/{11483926-db67-4190-91b1-ef20fcec5f33}.xpi
Status: enabled

Name: Gecko Profiler
Location: ${PROFILE_EXTENSIONS}/jid0-edalmuivkozlouyij0lpdx54...@jetpack.xpi
Status: user-disabled

Name: GLPI - assistance.ens-lyon.fr userstyle
Status: enabled

Name: Google Search userstyle
Status: enabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled

Name: gtranslate
Location: ${PROFILE_EXTENSIONS}/{aff87fa2-a58e-4edd-b852-0a20203c1e17}.xpi
Status: enabled

Name: HeadingsMap
Location: ${PROFILE_EXTENSIONS}/headi...@niquelheadings.net.xpi
Status: enabled

Name: HTML5 Video Everywhere!
Location: ${PROFILE_EXTENSIONS}/html5-video-everywh...@lejenome.me.xpi
Status: enabled

Name: IMDb userstyle
Status: enabled

Name: itt-datetimes greasemonkey-user-script
Status: enabled

Name: Link Widgets
Location: ${PROFILE_EXTENSIONS}/linkwid...@clav.mozdev.org
Status: enabled

Name: Live HTTP headers
Location: ${PROFILE_EXTENSIONS}/{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Status: enabled

Name: Move tabbar to the bottom userstyle
Status: user-disabled

Name: Move tabbar to the left userstyle
Status: user-disabled

Name: Move tabbar to the right userstyle
Status: user-disabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Multiple row bookmark toolbar userstyle
Status: user-disabled

Name: Nerim userstyle
Status: enabled

Name: Nimbus Screen Capture - editable screenshots.
Location: ${PROFILE_EXTENSIONS}/nimbusscreencaptur...@everhelper.me.xpi
Status: enabled

Name: Open in Browser
Location: ${PROFILE_EXTENSIONS}/openinbrow...@www.spasche.net.xpi
Status: enabled

Name: PeopleForCinema userstyle
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: QuickWiki
Location: ${PROFILE_EXTENSIONS}/{EE223D7A-F30F-11DD-8F0A-D2AD55D89593}.xpi
Status: enabled

Name: Slashdot.org - Remove ads userstyle
Status: enabled

Name: SourceForge font size in comments userstyle
Status: enabled

Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: enabled

Name: Tab Mix Plus
Location: ${PROFILE_EXTENSIONS}/{dc572301-7619-498c-a57d-39143191b318}.xpi
Status: enabled

Name: twitter-times greasemonkey-user-script
Status: enabled

Name: us-to-iso8601 greasemonkey-user-script
Status: user-disabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

Name: Web Developer
Location: ${PROFILE_EXTENSIONS}/{c45c406e-ab73-11d8-be73-000a95be3b12}.xpi
Status: enabled

Name: Wikipedia font size userstyle
Status: enabled

Name: X-Ray
Location: ${PROFILE_EXTENSIONS}/{3f1182ea-3243-4d32-8826-71fb1cc9c328}.xpi
Status: enabled

Name: youtube-html5 greasemonkey-user-script
Status: enabled

-- Plugins information

-- Addons package

Processed: tagging 871066

2017-08-09 Thread Debian Bug Tracking System

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

> tags 871066 + pending
Bug #871066 [src:scummvm-tools] scummvm-tools: FTBFS: cc1plus: error: 
-Wformat-security ignored without -Wformat [-Werror=format-security]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 870673 is minor

2017-08-09 Thread Debian Bug Tracking System

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

> severity 870673 minor
Bug #870673 {Done: Guilhem Moulin } [cryptsetup] cryptsetup 
causes piuparts test to fail
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#871514: clamav: FTBFS on mips64el

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 gcc-7 7.1.0-12
Bug #871514 [clamav] clamav: FTBFS on mips64el
Bug reassigned from package 'clamav' to 'gcc-7'.
No longer marked as found in versions clamav/0.99.2+dfsg-6.
Ignoring request to alter fixed versions of bug #871514 to the same values 
previously set
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Marked as found in versions gcc-7/7.1.0-12.
> affects -1 clamav
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Added indication that 871514 affects clamav

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

Bug#871514: clamav: FTBFS on mips64el

2017-08-09 Thread Sebastian Andrzej Siewior

control: reassign -1 gcc-7 7.1.0-12
control: affects -1 clamav

On 2017-08-09 16:43:29 [+0200], Aurelien Jarno wrote:
> I got a quick look. It's indeed a regression introduced by GCC 7. It can
> be workarounded by building the file with -O0, but already appears with
> -O1 optimization.
> 
> I got a quick look with gdb and it seems that loading either the rc
> (enum) or infect (bool variable to test it against 0, the load is done 
> with the ld instruction instead of the lw instruction. It means garbage
> from another local variable is loaded into the high 32 bits, which
> causes the comparison against 0 to be false instead of true.

Thanks for looking at this. I reassinged this bug to gcc-7. Would
forwarding the bug gcc upstream with the mbox.i be any help? I could a
label around the check so the comparison could be located in .S easier,
just don't know if this helps.

> Aurelien
> 

Sebastian

Bug#821883: marked as done (ImportError: When using gi.repository you must not import static modules like "gobject")

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 9 Aug 2017 22:47:33 +0300
with message-id <20170809194733.23fhszsahphgewh7@localhost>
and subject line Closing bugs in morituri
has caused the Debian Bug report #821883,
regarding ImportError: When using gi.repository you must not import static 
modules like "gobject"
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.)


-- 
821883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: morituri
Version: 0.2.3-2
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After a recent apt-get upgrade, appears morituri (from experimental) no
longer works at all (traceback below). I attempted to fix it myself, but
I don't know Python so I didn't really get anywhere...

$ rip cd rip
Using configured read offset 6
Checking device /dev/sr0
CDDB disc id: 3d0cb416
MusicBrainz disc id fmCeZFVMZYuZ5ZGySzKhWgDlNNM-
MusicBrainz lookup URL 
https://musicbrainz.org/cdtoc/attach?toc=1+22+244050+150+17881+24489+34744+62335+65971+67088+70519+74719+86494+93347+98152+104826+128780+146665+148207+152406+162293+176335+193912+204024+233637=22=fmCeZFVMZYuZ5ZGySzKhWgDlNNM-
Disc duration: 00:54:12.000, 22 audio tracks

Matching releases:

Artist  : Richard Strauss; Staatskapelle Weimar, Antoni Wit
Title   : An Alpine Symphony
Duration: 00:54:11.992
URL : https://musicbrainz.org/release/084a9bbb-c722-40ad-8f32-097d697b7b09
Release : 084a9bbb-c722-40ad-8f32-097d697b7b09
Type: Album

Traceback (most recent call last):
  File "/usr/bin/rip", line 46, in 
h.handleImportError(e)
  File "/usr/bin/rip", line 41, in 
sys.exit(main.main(sys.argv[1:]))
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 50, in main
h.handleImportError(e)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 45, in main
ret = c.parse(argv)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 123, in 
parse
logcommand.LogCommand.parse(self, argv)
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 401, in parse
return self.subCommands[command].parse(args[1:])
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 401, in parse
return self.subCommands[command].parse(args[1:])
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 363, in parse
ret = self.do(args)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/cd.py", line 160, in do
self.doCommand()
  File "/usr/lib/python2.7/dist-packages/morituri/rip/cd.py", line 276, in 
doCommand
self.program.result.gstreamerVersion = gstreamer.gstreamerVersion()
  File "/usr/lib/python2.7/dist-packages/morituri/common/gstreamer.py", line 
59, in gstreamerVersion
import gi
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 39, in 
raise ImportError(_static_binding_error)
ImportError: When using gi.repository you must not import static modules like 
"gobject". Please change all occurrences of "import gobject" to "from 
gi.repository import GObject". See: 
https://bugzilla.gnome.org/show_bug.cgi?id=709183




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

Kernel: Linux 4.4.0-1-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/bash
Init: systemd (via /run/systemd/system)

Versions of packages morituri depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-2+b1
ii  gstreamer1.0-plugins-good  1.8.0-1+b1
ii  python 2.7.11-1
ii  python-cddb1.4-5.2
ii  python-gi  3.18.2-2+b1
ii  python-gobject 3.18.2-2
ii  python-gst-1.0 1.8.0-1
ii  python-musicbrainzngs  0.5-2
ii  python-pkg-resources   18.8-1

Versions of packages morituri recommends:
ii  gstreamer1.0-libav  1:1.8.0-1+b1
ii  gstreamer1.0-tools  1.8.0-2
ii  python-xdg  0.25-4

Versions of packages morituri suggests:
ii  gstreamer1.0-plugins-ugly  1.8.0-1
ii  python-gtk22.24.0-4
pn  python-pycdio  

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlcXMmIACgkQ+z+IwlXqWf5tuQCfRpYKL8hVlkjvPczvzrSQOt66
tiYAn1XyXHpFtX7G5/7pxkLzH3T//gGQ
=zOKV
-END PGP

Bug#871601: ansible-2.3.1.0+dfsg-1 is uninstallable

2017-08-09 Thread Robbie Harwood

Package: ansible
Version: 2.3.1.0+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

ansible-2.3.1.0+dfsg-1 depends on python-jinja2 < 2.9.  However, this is not
available in testing/unstable/experimental.  As a result,
ansible-2.3.1.0+dfsg-1 is uninstallable, and its migration from unstable has
been blocked.

Thanks,
--Robbie

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

Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ansible depends on:
ii  python2.7.13-2
ii  python-crypto 2.6.1-7+b1
ii  python-httplib2   0.9.2+dfsg-1
ii  python-jinja2 2.9.6-1
ii  python-netaddr0.7.18-2
ii  python-paramiko   2.0.0-1
ii  python-pkg-resources  36.0.1-1
ii  python-yaml   3.12-1+b1

Versions of packages ansible recommends:
ii  python-kerberos   1.1.5-2+b3
ii  python-selinux2.6-3+b2
pn  python-winrm  
ii  python-xmltodict  0.11.0-1

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information

Bug#871600: memcached frequently FTBFS: t/stats.t failure

2017-08-09 Thread Adrian Bunk

Source: memcached
Version: 1.5.0-1
Severity: serious

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

...
t/stats-conns.t . ok
t/stats-detail.t  ok

#   Failed test 'after flush and a get, get_flushed is 1'
#   at t/stats.t line 178.
#  got: '0'
# expected: '1'
# Looks like you failed 1 test of 108.
t/stats.t ... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/108 subtests 
t/touch.t ... ok
t/udp.t . ok
t/unixsocket.t .. ok
t/watcher.t . ok

Test Summary Report
---
t/stats.t (Wstat: 256 Tests: 108 Failed: 1)
  Failed test:  108
  Non-zero exit status: 1
Files=58, Tests=25712, 216 wallclock secs ( 7.28 usr  0.46 sys + 16.40 cusr  
5.46 csys = 29.60 CPU)
Result: FAIL
Makefile:1654: recipe for target 'test' failed
make[1]: *** [test] Error 1

Processed: found 868839 in 1.0.0-3

2017-08-09 Thread Debian Bug Tracking System

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

> found 868839 1.0.0-3
Bug #868839 [ruby-mustermann,ruby-mustermann19] 
ruby-mustermann,ruby-mustermann19: error when trying to install together
There is no source info for the package 'ruby-mustermann19' at version 
'1.0.0-3' with architecture ''
Marked as found in versions ruby-mustermann/1.0.0-3.
> thanks
Stopping processing here.

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

Processed: Already fixed in 2:1.9.8.1-1

2017-08-09 Thread Debian Bug Tracking System

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

> fixed 869774 2:1.9.8.1-1
Bug #869774 {Done: Daniel Kahn Gillmor } [enigmail] 
thunderbird 52 needs enigmail 1.9.8.1 or later
Marked as fixed in versions enigmail/2:1.9.8.1-1.
> thanks
Stopping processing here.

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

Processed: Perl 5.26 problem

2017-08-09 Thread Debian Bug Tracking System

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

> tags 871558 buster sid
Bug #871558 [echolot] echolot: pingd fail to start
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: closing 861567

2017-08-09 Thread Debian Bug Tracking System

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

> close 861567
Bug #861567 [src:dask] dask: FTBFS with Sphinx 1.5: MathJax.js is missing
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#861567: closing 861567

2017-08-09 Thread Diane Trout

close 861567 
thanks

Pages with formula render correctly using MathJax at
file:///usr/share/javascript/mathjax/MathJax.js?config=TeX-AMS-MML_HTMLorMML

Bug#871269: missing Replaces

2017-08-09 Thread Andreas Beckmann

On 2017-08-09 19:09, Andreas Beckmann wrote:
> I can't find a *gsl*prof* package in the archive, so this indeed seems
> to be a new one. And should be totally unrelated to the splitting of the
> library package.

That's an interesting one. Above analysis was without looking at the
source. It's in the source package, but did not get built so far,
except for your last upload. Let me see what happens in my local build ... 

In the i386 build log from the buildd I see:

dpkg-genchanges: warning: package libgsl-prof in control file but not in 
files list

BTW, you should use source-only uploads nowadays (unless you have
something that needs to go through NEW).

Looking at the source now:

$ grep -r libgsl-prof debian/
debian/rules:profpack := libgsl-prof
debian/control:Package: libgsl-prof
$ grep -r profpack debian/
debian/rules:#profpack := libgsl$(sonum)-prof
debian/rules:profpack := libgsl-prof
debian/rules:debprof := $(CURDIR)/debian/$(profpack)
debian/rules:export DH_OPTIONS =-N$(libpack) -N$(libcblas) -N$(devpack) 
-N$(binpack) -N$(dbgpack) -p$(profpack)
debian/rules:export DH_OPTIONS =-N$(profpack)
debian/rules:   $(MAKE) -f debian/rules DH_OPTIONS="-i -N$(profpack)" 
binary-common
debian/rules:   $(MAKE) -f debian/rules DH_OPTIONS="-a -N$(profpack)" 
binary-common

and without even doing '$PAGER debian/rules' I'd recommend:
* switch to dh
gsl is probably a long grown packaging ... according to the
changelog the package origin predates my first potato system
in 1999 :-)

So something changed on your build machine and libgsl-prof
got built this time.

... local rebuild of -5 finished:

dpkg-genchanges: warning: package libgsl-prof in control file but not in files 
list

Andreas

Bug#871573: insighttoolkit4 fails to build from source

2017-08-09 Thread Gianfranco Costamagna

Hello,

> /usr/include/c++/7/bits/std_abs.h:103:16: error: invalid operands to binary
> expression ('__castxml__float128' (aka '__castxml__float128_s') and 'int')
>   { return __x < 0 ? -__x : __x; }
>~~~ ^ ~
> /usr/include/c++/7/bits/stl_pair.h:449:5: note: candidate template ignored:
> could not match 'pair' against
> '__castxml__float128_s'
> operator<(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
> ^

somewhat I'm smelling a castxml bug here, but I don't have enough info to prove 
it.

G.



signature.asc
Description: OpenPGP digital signature

Bug#871269: missing Replaces

2017-08-09 Thread Dirk Eddelbuettel


On 9 August 2017 at 19:09, Andreas Beckmann wrote:
| On 2017-08-09 18:52, Dirk Eddelbuettel wrote:
| > Uploaded a -6 with the versioned Replaces but just got a note it is in NEW
| > because of libgsl-prof -- which seems strange.  Any idea?
| 
| Since the packaging is not in git (or another vcs), I can't review the
| diff ... and NEW is not accessible AFAIK.

Only one line change in debian/control, plus the debian/changelog entry.
 
| I can't find a *gsl*prof* package in the archive, so this indeed seems
| to be a new one. And should be totally unrelated to the splitting of the
| library package.

Yes. It is a ghost. I think I experimented with that once, and then on
subsequent builds falsely convinced myself it was part of the regular build.

Will adjust debian/{rules,control}.

Dirk

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

Bug#871591: [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7

2017-08-09 Thread Sylvestre Ledru


> I've noticed that llvm-toolchain-snapshot goes FTBFS because
> `debian/rules' in the packge fails to detect gcc-7 (it tries to use
> gcc-7.1). The Jenkins builds seem to be failing due to the same bug.
> http://llvm-jenkins.debian.net/view/Debian%20unstable/job/llvm-toolchain-binaries/architecture=amd64,distribution=unstable/898/console
>
> Here I send a patch to fix this by ensuring the existence of
> /usr/bin/g++-$(GCC_VERSION) on the build system.
>
> Could you take a look at it please?
Interesting approach! Thanks, I will try it!

S




signature.asc
Description: OpenPGP digital signature

Bug#871269: missing Replaces

2017-08-09 Thread Andreas Beckmann

On 2017-08-09 18:52, Dirk Eddelbuettel wrote:
> Uploaded a -6 with the versioned Replaces but just got a note it is in NEW
> because of libgsl-prof -- which seems strange.  Any idea?

Since the packaging is not in git (or another vcs), I can't review the
diff ... and NEW is not accessible AFAIK.

I can't find a *gsl*prof* package in the archive, so this indeed seems
to be a new one. And should be totally unrelated to the splitting of the
library package.

Andreas

Bug#871591: [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7

2017-08-09 Thread Katsuhiko Nishimra

Package: src:llvm-toolchain-snapshot
Version: 1:5.0~svn305653-1
Severity: serious
Tags: patch sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Dear LLVM packagers,

I've noticed that llvm-toolchain-snapshot goes FTBFS because
`debian/rules' in the packge fails to detect gcc-7 (it tries to use
gcc-7.1). The Jenkins builds seem to be failing due to the same bug.
http://llvm-jenkins.debian.net/view/Debian%20unstable/job/llvm-toolchain-binaries/architecture=amd64,distribution=unstable/898/console

Here I send a patch to fix this by ensuring the existence of
/usr/bin/g++-$(GCC_VERSION) on the build system.

Could you take a look at it please?
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/changelog llvm-toolchain-snapshot-5.0~svn305653/debian/changelog
--- llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-08-09 23:32:40.0 +0900
@@ -1,3 +1,10 @@
+llvm-toolchain-snapshot (1:5.0~svn305653-1.1) UNRELEASED; urgency=medium
+
+  * Ensure /usr/bin/g++-$(GCC_VERSION) exists
+
+ -- Katsuhiko Nishimra   Wed, 09 Aug 2017 23:32:40 +0900
+
 llvm-toolchain-snapshot (1:5.0~svn305653-1) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/rules llvm-toolchain-snapshot-5.0~svn305653/debian/rules
--- llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-08-09 23:32:40.0 +0900
@@ -2,9 +2,11 @@
 
 TARGET_BUILD	:= build-llvm
 DEB_INST		:= $(CURDIR)/debian/tmp/
-# The 5|6| in the regexp is a crappy workaround. g++ 5.2 in Debian is not providing a g++-5.2 binary (only g++-5)
-# accomodate that by hardcoding the 5 detection
-GCC_VERSION := $(shell dpkg-query -W -f '$${Version}' g++ | sed -rne 's,^([0-9]+:)?(5|6|[0-9]+\.[0-9]+|[0-9]+).*$$,\2,p')
+
+GXX_VERSIONED_PACKAGE:= $(shell dpkg-query -W -f '$${Depends}' g++ | grep -o 'g++-[0-9][0-9.]*' | tail -n1 )
+GXX_VERSIONED_EXECUTABLE := $(shell dpkg -L $(GXX_VERSIONED_PACKAGE) | grep '/usr/bin/g++-[0-9][0-9.]*' | xargs ls -d | tail -n1 )
+GCC_VERSION  := $(subst /usr/bin/g++-,,$(GXX_VERSIONED_EXECUTABLE))
+
 LLVM_VERSION	:= 5.0
 LLVM_VERSION_FULL := $(LLVM_VERSION).0
 


signature.asc
Description: PGP signature

Bug#859327: marked as done (fastforward: Fastforward segfaults)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 16:36:55 +
with message-id 
and subject line Bug#859327: fixed in fastforward 1:0.51-3.1
has caused the Debian Bug report #859327,
regarding fastforward: Fastforward segfaults
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.)


-- 
859327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fastforward
Version: 1:0.51-3+b2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 4.10.1 (SMP w/8 CPU cores; PREEMPT)
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 fastforward depends on:
ii  libc6  2.24-9

Versions of packages fastforward recommends:
ii  qmail  1.06-6+b1

fastforward suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fastforward
Source-Version: 1:0.51-3.1

We believe that the bug you reported is fixed in the latest version of
fastforward, 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.
Adrian Bunk  (supplier of updated fastforward package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jul 2017 18:15:43 +0300
Source: fastforward
Binary: fastforward
Architecture: source
Version: 1:0.51-3.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Adrian Bunk 
Description:
 fastforward - handles qmail forwarding according to a cdb database
Closes: 859327
Changes:
 fastforward (1:0.51-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Harry Sintonen to fix segfaults on 64bit.
 (Closes: #859327)
Checksums-Sha1:
 fbd62ac2e2ee88ffe558d72becfe6ee5872a246c 1652 fastforward_0.51-3.1.dsc
 0c63979a00e11a308fc71578e75f491da4544893 5194 fastforward_0.51-3.1.diff.gz
Checksums-Sha256:
 2e14a79767a7b2eed8c9adfa36f72283e2d4410fb1f2c8147064721dc7e2c0a3 1652 
fastforward_0.51-3.1.dsc
 aa4d924036daf918e8b339b6013fd103483747338d3e049c5a982100153103cb 5194 
fastforward_0.51-3.1.diff.gz
Files:
 003366782460c21c65e74f0a6b46d370 1652 mail extra fastforward_0.51-3.1.dsc
 94ed2a22dcfe034ccf54e98f4dbab3d4 5194 mail extra fastforward_0.51-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAll4s2sACgkQiNJCh6LY
mLHbdg//fc2LqEuSNSxV23Q9QjPLcVuA1ZjouIQAX+9jMtiMQNdn8NokQTs21Sqo
OkFcy6CU4eHJybL1x5baPGnV+1kd5b36pI7ZseAeGC+qH1np1idNoCb0gIAXZEjB
8HzqGOyKIYfJgHOmpOqkc/4A6XBSfVTWg+ddghsqEjNtm/Xxo4GDpPikDfyM6HoU
9yUxyPEln5hdJ+gA6sZ1za/RkT6q02r7u4rhh0X1hXPrpNyrM1wd21p8XH5UOoDi
xhckaozoXI9pfQbJbBnar/9rqgY+n1YVOPXU2xYYN0zU9MWSYUxi4rqPmpxEihjx
y4pT3imawPrge3l7Fq1lDxe9JLJY4Zaw21coqfo1xVGZaov1dOJfplMa4A1dqClF
VKq/xYXVgFOaQ7iycLd/Kx7WEAWmKnQrpGmBi1eF0rKnX1Mj9lofU+K4l4rqoxZm
fYVVBB/EKtAqyYzsT4bkykibDY0VKzSMkfj+zXS6XZWZi2pC6zD0wvn5B7wIlrs+
BLNCBV9+XAaIIb1ygTc7M4u+ki5GmXsQHRSnho6uHuWbPJ8m0aMUZ4mzXFXF+3Bv
xwbMb4k0TybvBKUqqrYIX9fcTQqF/NmIlmFzZSzusifhgU8sjKJALMhWggpjzp63
GoyVHS827CPLd6c6oJ4CkNv7vh9zIWSOH5NzboYh/RlM55LJ988=
=kVaW
-END PGP SIGNATURE End Message ---

Bug#870129: marked as done (auto-multiple-choice broken with perl 5.26)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 16:35:09 +
with message-id 
and subject line Bug#870129: fixed in auto-multiple-choice 1.3.0-4
has caused the Debian Bug report #870129,
regarding auto-multiple-choice broken with perl 5.26
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.)


-- 
870129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auto-multiple-choice
Version: 1.3.0-3
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hi Alexis, Georges,

The auto-multiple-choice package is broken in unstable now that perl 5.26
has landed, because it uses obsolete syntax.  'use encoding "utf8"' is
obsolete, replaced by 'use utf8'.

This shows up in the form of failing autopkgtests:

https://ci.debian.net/packages/a/auto-multiple-choice/unstable/amd64/

The attached patch corrects this problem, and I have uploaded it to Ubuntu's
devel series.

Hope that helps,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru auto-multiple-choice-1.3.0/debian/patches/perl-5.26-compat.patch 
auto-multiple-choice-1.3.0/debian/patches/perl-5.26-compat.patch
--- auto-multiple-choice-1.3.0/debian/patches/perl-5.26-compat.patch
1969-12-31 16:00:00.0 -0800
+++ auto-multiple-choice-1.3.0/debian/patches/perl-5.26-compat.patch
2017-07-29 23:56:30.0 -0700
@@ -0,0 +1,58 @@
+Description: fix compatibility with perl 5.26
+ 'use encoding "utf8"' is obsolete in perl 5.26, returning an error:
+ Error:  The encoding pragma is no longer supported at [...]
+ replace with 'use utf8'.
+Author: Steve Langasek 
+
+Index: auto-multiple-choice-1.3.0/AMC-prepare.pl
+===
+--- auto-multiple-choice-1.3.0.orig/AMC-prepare.pl
 auto-multiple-choice-1.3.0/AMC-prepare.pl
+@@ -18,7 +18,7 @@
+ # along with Auto-Multiple-Choice.  If not, see
+ # .
+ 
+-use encoding "utf-8";
++use utf8;
+ 
+ use File::Copy;
+ use File::Spec::Functions qw/splitpath catpath splitdir catdir catfile 
rel2abs tmpdir/;
+Index: auto-multiple-choice-1.3.0/AMC-note.pl
+===
+--- auto-multiple-choice-1.3.0.orig/AMC-note.pl
 auto-multiple-choice-1.3.0/AMC-note.pl
+@@ -25,7 +25,7 @@
+ use AMC::Scoring;
+ use AMC::Data;
+ 
+-use encoding 'utf8';
++use utf8;
+ 
+ my $darkness_threshold=0.1;
+ my $darkness_threshold_up=1.0;
+Index: auto-multiple-choice-1.3.0/AMC-annote.pl
+===
+--- auto-multiple-choice-1.3.0.orig/AMC-annote.pl
 auto-multiple-choice-1.3.0/AMC-annote.pl
+@@ -35,7 +35,7 @@
+ use AMC::DataModule::layout qw/:flags/;
+ use AMC::Substitute;
+ 
+-use encoding 'utf8';
++use utf8;
+ 
+ my $cr_dir="";
+ my $rep_projet='';
+Index: auto-multiple-choice-1.3.0/AMC-perl/AMC/Annotate.pm
+===
+--- auto-multiple-choice-1.3.0.orig/AMC-perl/AMC/Annotate.pm
 auto-multiple-choice-1.3.0/AMC-perl/AMC/Annotate.pm
+@@ -36,7 +36,7 @@
+ use AMC::DataModule::layout qw/:flags/;
+ use AMC::Gui::Avancement;
+ 
+-use encoding 'utf8';
++use utf8;
+ 
+ sub new {
+ my (%o)=(@_);
diff -Nru auto-multiple-choice-1.3.0/debian/patches/series 
auto-multiple-choice-1.3.0/debian/patches/series
--- auto-multiple-choice-1.3.0/debian/patches/series2017-06-20 
14:18:05.0 -0700
+++ auto-multiple-choice-1.3.0/debian/patches/series2017-07-29 
23:50:13.0 -0700
@@ -2,3 +2,4 @@
 tests-INC-fix.diff
 fix-build-with-opencv-3.1.diff
 bugfix-412.diff
+perl-5.26-compat.patch
--- End Message ---
--- Begin Message ---
Source: auto-multiple-choice
Source-Version: 1.3.0-4

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

Debian

Bug#871586: courier FTBFS with libcourier-unicode-dev 2.0-1

2017-08-09 Thread Adrian Bunk

Source: courier
Version: 0.76.3-5
Severity: serious
Tags: buster sid

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

...
rfc2047.c:379:30: error: unknown type name 'unicode_char'
 static int encode_word(const unicode_char *uc,
  ^~~~
rfc2047.c:412:31: error: unknown type name 'unicode_char'
 static int encode_words(const unicode_char *uc,
   ^~~~
rfc2047.c:457:41: error: unknown type name 'unicode_char'
 static int do_encode_words_method(const unicode_char *uc,
 ^~~~
...

Bug#871587: maildrop FTBFS with libcourier-unicode-dev 2.0-1

2017-08-09 Thread Adrian Bunk

Source: maildrop
Version: 2.8.4-2
Severity: serious
Tags: buster sid

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

...
rfc2047.c:379:30: error: unknown type name 'unicode_char'
 static int encode_word(const unicode_char *uc,
  ^~~~
rfc2047.c:412:31: error: unknown type name 'unicode_char'
 static int encode_words(const unicode_char *uc,
   ^~~~
rfc2047.c:457:41: error: unknown type name 'unicode_char'
 static int do_encode_words_method(const unicode_char *uc,
 ^~~~
...

Bug#871269: missing Replaces

2017-08-09 Thread Dirk Eddelbuettel


On 9 August 2017 at 16:55, Andreas Beckmann wrote:
| On 2017-08-09 16:49, Dirk Eddelbuettel wrote:
| > | All the Conflicts can probably be turned into Breaks (which will make 
apt's life
| > | easier for distupgrades involving this transition) and Breaks and Replaces
| > | need to match w.r.t. to the versioning (otherwise you might run into
| > | weird corner cases).
| > 
| > Can the Breaks be similarly versioned?  Let me get a versioned Replaces out,
| > and maybe we can review then?
| 
| Breaks can be versioned in the same way as Conflicts or Replaces (or
| nearly anything else).

Ok.

Uploaded a -6 with the versioned Replaces but just got a note it is in NEW
because of libgsl-prof -- which seems strange.  Any idea?

Dirk

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

Bug#871585: python-apt: FTBFS: Test failure

2017-08-09 Thread Daniel Schepler

Source: python-apt
Version: 1.4.0~beta3
Severity: serious

>From my pbuilder build log:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-apt-1.4.0~beta3'
set -e; for python in python2.7 python3.6 python3.5 ; do \
   $python tests/test_all.py -q || [ "linux" = "hurd" ]; \
done;
[tests] Running on 2.7.13+ (default, Jul 19 2017, 18:15:03) [GCC 6.4.0 20170704]
Using library_dir:
'/build/python-apt-1.4.0~beta3/build/lib.linux-x86_64-2.7'WARNING:
Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
==
ERROR: testAddKeyFromServer (test_auth.TestAuthKeys)
Install a GnuPG key from a remote server.
--
Traceback (most recent call last):
 File "/build/python-apt-1.4.0~beta3/tests/test_auth.py", line 239, in
testAddKeyFromServer
   "hkp://localhost:%d" % self.keyserver_port)
 File "/build/python-apt-1.4.0~beta3/build/lib.linux-x86_64-2.7/apt/auth.py",
line 137, in add_key_from_keyserver
   shutil.rmtree(tmp_keyring_dir)
 File "/usr/lib/python2.7/shutil.py", line 266, in rmtree
   onerror(os.remove, fullname, sys.exc_info())
 File "/usr/lib/python2.7/shutil.py", line 264, in rmtree
   os.remove(fullname)
OSError: [Errno 2] No such file or directory: '/tmp/tmpVdpO4x/S.gpg-agent.extra'

--
Ran 97 tests in 21.771s

FAILED (errors=1, skipped=2)
debian/rules:50: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/python-apt-1.4.0~beta3'
debian/rules:16: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#867065: marked as done (asn1c: build dependency on texlive-math-extra can no longer be fulfilled)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 15:06:13 +
with message-id 
and subject line Bug#867065: fixed in asn1c 0.9.28+dfsg-1
has caused the Debian Bug report #867065,
regarding asn1c: build dependency on texlive-math-extra can no longer be 
fulfilled
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.)


-- 
867065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asn1c
Version: 0.9.27+dfsg-5
Severity: serious
Tags: buster sid

texlive-science does no longer provide texlive-math-extra.
--- End Message ---
--- Begin Message ---
Source: asn1c
Source-Version: 0.9.28+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Eugene Seliverstov  (supplier of updated asn1c package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Jul 2017 20:20:00 +0300
Source: asn1c
Binary: asn1c asn1c-doc
Architecture: source
Version: 0.9.28+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Eugene Seliverstov 
Changed-By: Eugene Seliverstov 
Description:
 asn1c  - ASN.1 compiler for C
 asn1c-doc  - Documentation for asn1c
Closes: 867065
Changes:
 asn1c (0.9.28+dfsg-1) unstable; urgency=medium
 .
   * Fixed dependency on texlive-math-extra (closes: #867065)
   * New upstream release 0.9.28
   * Updated policy version to 4.0.0
   * Removed obsolete patch 13_manmacro
   * Updated patches to fulfil build scripts
Checksums-Sha1:
 e4a8766b554bafd3bfcafecadccbab921cacee0f 2056 asn1c_0.9.28+dfsg-1.dsc
 714b44d075e82879be0051a4b741312605eaa805 733773 asn1c_0.9.28+dfsg.orig.tar.gz
 f9fe3c733c71b346d8204c3258340ed388a16c1e 6928 asn1c_0.9.28+dfsg-1.debian.tar.xz
Checksums-Sha256:
 8c9552bdbefd921d95ccfb064f1965433a2002edfa65be6feced3aaec768c3c9 2056 
asn1c_0.9.28+dfsg-1.dsc
 b77423d9577a99139448bcf5b6aec61a92ef6b45236e50ba431143cb35da4d39 733773 
asn1c_0.9.28+dfsg.orig.tar.gz
 d4f3a023648be17941cc175a12c64246df4e7c319e2ac93688a8f4a7220f128b 6928 
asn1c_0.9.28+dfsg-1.debian.tar.xz
Files:
 fd85bf20c5fae3099c5c97defd16f649 2056 devel extra asn1c_0.9.28+dfsg-1.dsc
 be488adc651a2fff4ebf47e1008728fb 733773 devel extra 
asn1c_0.9.28+dfsg.orig.tar.gz
 03e557a21dde40472ce048af5c82bacd 6928 devel extra 
asn1c_0.9.28+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZixh7AAoJEPNPCXROn13Z69IQALbgDchrK8lbsoE8jaJIJyPR
k4G1U3MRCz13NC+LYtrksMWtToVl/7V0c5Z6qTTAMGIkHAjidulN4Sm6p2VwPeja
XKTDX1kGl5AAWLrdMyEZgqux4UuzAEAhQkOMJCiu3Qzv61OtXa4/QfaC7om0wV02
mv5OYPZIWcmGwv82MWM1p/wSBSIMTqqQIVMAwRHdha/panKHBnqnN/qRvaGGnwgE
o4YbuldNzF8rNhYhg/85nQY18AP/mXoWWOP4q2t66mZkcFr8mqTcsyPrgEp0r2rx
7gIOwu43SCNWq+4cGDLIhdBKMpH0ehmwQuB+a84NcuLbak+MdA0nPpM58GRPdeZL
5iT7t6TSVdVVAjFzky2YEYNfzateGjMugpOfCrWuC/TwCgm/kU2KWJ9k8pgBUpts
yN4VRfUfjLbkVWBNzRNR7QtoaV7KJCKb9NJPPn0smbXhTUciT7+tw5NYaoJO20Rg
dvgqBr8SG5cOBBPEU8GX+MRnd4XgvG0lOW7d50TwkN+se2f7lLqDrarIQfntHRRK
aEi0k2W85Pe0HPmT1AkL+WcHUoPw1T0F7W0k1NTWl7PFxfOJjv0t6774AOZxtMWj
eeloYVWadVXEUtd3A4++C6GCKyjSRRUcXgO3T40OiIkZLNAxvRyueCNKpbuGjrKj
uMvinAktlctC46e3kS50
=1S3/
-END PGP SIGNATURE End Message ---

Bug#868856: marked as done (emacs25: Logic for "nocheck" is inverted in debian/rules)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 9 Aug 2017 11:03:31 -0400
with message-id 

and subject line Re: emacs25: Logic for "nocheck" is inverted in debian/rules
has caused the Debian Bug report #868856,
regarding emacs25: Logic for "nocheck" is inverted in debian/rules
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.)


-- 
868856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.2+1-2
Severity: serious
Justification: builds without testsuite

Hi!

I'm not 100% sure whether this bug warrents the severity serious, but
since running the testsuites is normally mandatory on all release
architectures, I figured the priority should be high.  Feel free to
downgrade the severity if necessary.

The debian/rules of emacs25 has:

ifneq (,$(filter nocheck, $(DEB_BUILD_OPTIONS)))
$(MAKE) -C debian/build-lucid check
$(MAKE) -C debian/build-nox check
$(MAKE) -C debian/build-x check
endif

This reads as "if DEB_BUILD_OPTIONS contains 'nocheck' don't run the
testsuite". This is, of course, wrong. It should be the other way
around, i.e. the testsuite should be run by default and be disabled
if "nocheck" is found in DEB_BUILD_OPTIONS. The fix is trivial:
Just replace the "ifneq" with "ifeq".

On a sidenote: I did that and noticed that the testsuite actually
fails. If that is the original reason for this bug, I would like
to ask to either temporarily comment out the section above or
disable the individual tests which are failing.

Either way, passing "nocheck" should never run the testsuite.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Wrong bug number mentioned in changelog but this should be fixed now.

emacs25 (25.2+1-3) unstable; urgency=medium
 .
   * Actually run tests by default (fix DEB_BUILD_OPTIONS nocheck test)
 Fix the inverted logic.  Thanks to John Paul Adrian Glaubitz for
 reporting the problem.  (Closes: 869328)--- End Message ---

Bug#871269: missing Replaces

2017-08-09 Thread Andreas Beckmann

On 2017-08-09 16:49, Dirk Eddelbuettel wrote:
> | All the Conflicts can probably be turned into Breaks (which will make apt's 
> life
> | easier for distupgrades involving this transition) and Breaks and Replaces
> | need to match w.r.t. to the versioning (otherwise you might run into
> | weird corner cases).
> 
> Can the Breaks be similarly versioned?  Let me get a versioned Replaces out,
> and maybe we can review then?

Breaks can be versioned in the same way as Conflicts or Replaces (or
nearly anything else).


Andreas

Bug#871269: missing Replaces

2017-08-09 Thread Dirk Eddelbuettel


Hi Andreas,

Thanks for the note.

On 9 August 2017 at 15:58, Andreas Beckmann wrote:
| Followup-For: Bug #871269
| 
| Hi Dirk,
| 
| for libgslcblas0 the Replaces on libgsl23 needs to be versioned (<< 
2.4+dfsg-4).

Oh, right.  

| All the Conflicts can probably be turned into Breaks (which will make apt's 
life
| easier for distupgrades involving this transition) and Breaks and Replaces
| need to match w.r.t. to the versioning (otherwise you might run into
| weird corner cases).

Can the Breaks be similarly versioned?  Let me get a versioned Replaces out,
and maybe we can review then?

Thanks so much,  Dirk

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

Bug#871579: libpython3.5-stdlib: removal of libpython3.5-stdlib makes files disappear from libpython3.5-testsuite

2017-08-09 Thread Andreas Beckmann

Package: libpython3.5-stdlib
Version: 3.5.4-1~rc1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libpython3.5-testsuite/stretch
  # (1)
  apt-get install libpython3.5-stdlib/buster
  apt-get remove libpython3.5-stdlib
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/lib/python3.5/test/test_support.py

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The libpython3.5-stdlib package has the following relationships with 
libpython3.5-testsuite:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libpython3.5-testsuite (<< 3.5.4~rc1-1)

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

0m52.2s ERROR: FAIL: After purging files have disappeared:
  /usr/lib/python3.5/test/__pycache__/test_support.cpython-35.pycnot 
owned
  /usr/lib/python3.5/test/test_support.pyowned by: 
libpython3.5-stdlib:amd64

0m52.2s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libpython3.5-testsuite.list not owned


cheers,

Andreas


libpython3.5-testsuite=3.5.3-1_libpython3.5-stdlib=3.5.4-1.log.gz
Description: application/gzip

Bug#871514: clamav: FTBFS on mips64el

2017-08-09 Thread Aurelien Jarno

On 2017-08-08 20:41, Sebastian Andrzej Siewior wrote:
> On 2017-08-08 20:34:37 [+0200], To sub...@bugs.debian.org wrote:
> …
> > returned (the important part):
> > |LibClamAV debug: parseEmailBody() rc 1 infect 0
> > |LibClamAV debug: parseEmailBody() returning 3
> …
> > The exp build passed with gcc-6_6.4.0-1 [0]. Is there an easy way to
> > downgrade the compiler on eller/porterbox? Or could a porter double
> > check this please?
> 
> on eller in a buster chroot:
> |LibClamAV debug: parseEmailBody() rc 1 infect 0
> |LibClamAV debug: parseEmailBody() returning 1
> 
> further suggestions?

I got a quick look. It's indeed a regression introduced by GCC 7. It can
be workarounded by building the file with -O0, but already appears with
-O1 optimization.

I got a quick look with gdb and it seems that loading either the rc
(enum) or infect (bool variable to test it against 0, the load is done 
with the ld instruction instead of the lw instruction. It means garbage
from another local variable is loaded into the high 32 bits, which
causes the comparison against 0 to be false instead of true.

Aurelien

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

Bug#871578: winff: fails to upgrade from 'testing' - trying to overwrite /usr/share/applications/winff.desktop

2017-08-09 Thread Andreas Beckmann

Package: winff
Version: 1.5.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package winff.
  Preparing to unpack .../202-winff_1.5.5-3_all.deb ...
  Unpacking winff (1.5.5-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gux07i/202-winff_1.5.5-3_all.deb (--unpack):
   trying to overwrite '/usr/share/applications/winff.desktop', which is also 
in package winff-data 1.5.5-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gux07i/202-winff_1.5.5-3_all.deb


cheers,

Andreas


winff-data=1.5.5-2_winff=1.5.5-3.log.gz
Description: application/gzip

Bug#871577: nano: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/nano.info.gz

2017-08-09 Thread Andreas Beckmann

Package: nano
Version: 2.8.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package nano.
  Preparing to unpack .../nano_2.8.6-2_amd64.deb ...
  Unpacking nano (2.8.6-2) ...
  dpkg: error processing archive /var/cache/apt/archives/nano_2.8.6-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/info/nano.info.gz', which is also in package 
nano-tiny 2.8.6-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/nano_2.8.6-2_amd64.deb

This bug is the opposite direction of #869876. Since you obviously moved
a file from nano-tiny to nano, you need corresponding versioned Breaks+Replaces.


cheers,

Andreas


nano-tiny=2.8.6-1_nano=2.8.6-2.log.gz
Description: application/gzip

Bug#871576: cinnamon-screensaver-x-plugin: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/cinnamon-screensaver/cinnamon-screensaver-dialog

2017-08-09 Thread Andreas Beckmann

Package: cinnamon-screensaver-x-plugin
Version: 3.4.1-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 cinnamon-screensaver-x-plugin.
  Preparing to unpack .../181-cinnamon-screensaver-x-plugin_3.4.1-1_all.deb ...
  Unpacking cinnamon-screensaver-x-plugin (3.4.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-1LDY9X/181-cinnamon-screensaver-x-plugin_3.4.1-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/cinnamon-screensaver/cinnamon-screensaver-dialog', 
which is also in package cinnamon-screensaver 3.2.13-4
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-1LDY9X/181-cinnamon-screensaver-x-plugin_3.4.1-1_all.deb


cheers,

Andreas


cinnamon-screensaver-x-plugin=3.4.1-1_cinnamon-screensaver=3.4.1-1.log.gz
Description: application/gzip

Bug#871288: libzeroc-ice3.6: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-09 Thread Jose Gutierrez de la Concha

Hi James

On Tue, Aug 8, 2017 at 6:07 PM, James Cowgill  wrote:

> On 08/08/17 11:29, Jose Gutierrez de la Concha wrote:
> > On Tue, Aug 8, 2017 at 5:01 PM, James Cowgill  > > wrote:
> > [...]
> > > - If your package does not provide a symbols file, add a
> dh_makeshlibs
> > >   override so that tight enough dependencies are generated.
> > >
> > >   Using libebml as an example (debian/rules):
> > >   + override_dh_makeshlibs:
> > >   + # For new symbols when compiled with GCC 7
> > >   + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
> > >
>

Any ideas how should I handle multiple packages in override_dh_makeshlibs
zeroc-ice has several packages that include libzeroc-ice3.6,
libzeroc-freeze3.6
so I cannot really pass a single package name in -V

> > Does this work with dbgsym generated packages?
> >
> > dh_makeshlibs has nothing to do with dbgsym packages. I'm not sure I
> > quite understand your question.
> >
> > As far as I can tell libzeroc-ice3.6 currently does not provide a shlibs
> > or symbols
> > file, so I guess we can skip this for now?
>
> It provides an shlibs file:
> $ dpkg-deb -I libzeroc-ice3.6_3.6.3-5_amd64.deb
>  new debian package, version 2.0.
>  size 1905864 bytes: control archive=1639 bytes.
>  728 bytes,18 lines  control
> 1293 bytes,16 lines  md5sums
>  471 bytes,18 lines   *  postinst #!/bin/sh
>  273 bytes,16 lines   *  postrm   #!/bin/sh
>  398 bytes,12 lines  shlibs
>   60 bytes, 2 lines  triggers
>
> James
>
>

Regards,
José

-- 
José Gutiérrez de la Concha
ZeroC, Inc.

Bug#871269: missing Replaces

2017-08-09 Thread Andreas Beckmann

Followup-For: Bug #871269

Hi Dirk,

for libgslcblas0 the Replaces on libgsl23 needs to be versioned (<< 2.4+dfsg-4).
All the Conflicts can probably be turned into Breaks (which will make apt's life
easier for distupgrades involving this transition) and Breaks and Replaces
need to match w.r.t. to the versioning (otherwise you might run into
weird corner cases).


Andreas

Bug#870227: marked as done (openbox-gnome-session: Adapt to gnome-settings-daemon 3.24)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 13:36:05 +
with message-id 
and subject line Bug#870227: fixed in openbox 3.6.1-4.1
has caused the Debian Bug report #870227,
regarding openbox-gnome-session: Adapt to gnome-settings-daemon 3.24
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.)


-- 
870227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openbox-gnome-session
Version: 3.6.1-4
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gsd324
Tags: buster sid

openbox-gnome-sessions includes gnome-session files to allow users to
easily log in to a GNOME Flashback session running openbox.
gnome-settings-daemon 3.24 has split itself into separate binaries and
the gnome-session files will no longer work. The new version of
gnome-settings-daemon is available for testing now in Debian
experimental.

In my next email, I will attach a patch that can fix this issue.

We intend to upload gnome-settings-daemon 3.24 to Debian unstable
about a week from now on Sunday, August 6.

I suggest uploading the fix to the DELAYED queue for that date so that
this transition will be easy and smooth.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: openbox
Source-Version: 3.6.1-4.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated openbox 
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, 08 Aug 2017 15:53:13 +0200
Source: openbox
Binary: openbox libobt2v5 libobrender32v5 openbox-dev gnome-panel-control 
openbox-gnome-session openbox-kde-session
Architecture: source
Version: 3.6.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Mateusz Łukasik 
Changed-By: Gianfranco Costamagna 
Description:
 gnome-panel-control - command line utility to invoke GNOME panel run 
dialog/menu
 libobrender32v5 - rendering library for openbox themes
 libobt2v5  - parsing library for openbox
 openbox- standards-compliant, fast, light-weight and extensible window man
 openbox-dev - development files for the openbox window manager
 openbox-gnome-session - command line utility to run Openbox as GNOME session
 openbox-kde-session - command line utility to run Openbox as KDE SC session
Closes: 870227
Changes:
 openbox (3.6.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Jeremy Bicha  ]
   * Adapt to gnome-settings-daemon 3.24 (Closes: #870227)
Checksums-Sha1:
 8ba11553eba48dcc302d729def10bdaa66fc78e4 2440 openbox_3.6.1-4.1.dsc
 b710008f9867628a7506c961b18b4ca8d71db742 35776 openbox_3.6.1-4.1.debian.tar.xz
Checksums-Sha256:
 441623d300c5ff1d5bcab460ea5e24882b8a43d5a66b44e94dfe8b00e771384f 2440 
openbox_3.6.1-4.1.dsc
 38c86828573df5fc2827352cfa99940fefcd06558bdf6e90f05b746a33bcef03 35776 
openbox_3.6.1-4.1.debian.tar.xz
Files:
 c643db49a5666118a7bcc83b59ef15c9 2440 x11 optional openbox_3.6.1-4.1.dsc
 0260e149b0cc79576a9008ab55d22c3c 35776 x11 optional 
openbox_3.6.1-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZicJvAAoJEPNPCXROn13Z+moP/iCG2PpkmiO+oibr99Zd7r+6
g7bN5LHIO8/w63If0R5dzxx67/sxMnd3cyxl8VVlvJERWk22JVb+40oa5yy0A/SD
+OrtLeGGb7tyZ1XXncDtpw5NOW5koNdCPgiY0yuNs/D8ek7GQyYVvvyaxVLruMPf
CCnwc73E5oEbBJyyzH2Xb78lhyGhq/IXzDfkWu1F7pbTIhEl90y0FJbYnmuUm0Do
BhMAZX01s7ysk8pRc3qQXOjNJDmTWWHhhYPEkyas/H1p/hVkcHsqN7+kQ+fBRPOC
E0HE3+zBo2Miu7WjU8hTt8HWc5DfN6NgHnddpUfIjmr7g8KEnPKnkUPUEe5ViTRg
PXzSdxfG/B9qvxraOI47VcTiWiqh/PeQyyLz7omKXZ/fwX6+Z83O7i4B1/tPs0fh
0UCdvTAQmqPDdejCVqT8XJnMzJzuOJaloRAV6ua6RAA0Ob+dlX+NnVUdnTE3eEWN
QlVh/FUG0xWtcSiIbq2hvZuV5u/rRvuP+f1aHYu9qvml17MZRWZjsVaw4VfNdIA4
RPff3SKGUQ6cifMgRK0DLwxJNUzN9eCeRVUJfYC6mtlb42sMpl2UFR6SKQDqZ2cK
hK3XXKYge/xCavgy0qg4L106tRUijNTd/4bWiqldIQwznhJac7vWkgJao74LZ8WV
nn5ECVhi8BPxlVKZpI4q
=HbPt
-END PGP SIGNATURE

Bug#871075: marked as done (musescore: FTBFS: make[4]: *** No rule to make target 'all.h', needed by 'thirdparty/singleapp/src/CMakeFiles/qtsingleapp_autogen'. Stop.)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 13:35:12 +
with message-id 
and subject line Bug#871075: fixed in musescore 2.1.0+dfsg1-0.2
has caused the Debian Bug report #871075,
regarding musescore: FTBFS: make[4]: *** No rule to make target 'all.h', needed 
by 'thirdparty/singleapp/src/CMakeFiles/qtsingleapp_autogen'.  Stop.
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.)


-- 
871075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musescore
Version: 2.0.3+dfsg1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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[4]: Entering directory 
> '/<>/musescore-2.0.3+dfsg1/obj-x86_64-linux-gnu'
> make[4]: *** No rule to make target 'all.h', needed by 
> 'thirdparty/singleapp/src/CMakeFiles/qtsingleapp_autogen'.  Stop.
> make[4]: Leaving directory 
> '/<>/musescore-2.0.3+dfsg1/obj-x86_64-linux-gnu'
> make[4]: Leaving directory 
> '/<>/musescore-2.0.3+dfsg1/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:7521: recipe for target 
> 'thirdparty/singleapp/src/CMakeFiles/qtsingleapp_autogen.dir/all' failed
> make[3]: *** 
> [thirdparty/singleapp/src/CMakeFiles/qtsingleapp_autogen.dir/all] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/musescore_2.0.3+dfsg1-2_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: musescore
Source-Version: 2.1.0+dfsg1-0.2

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

Debian distribution maintenance software
pp.
Thorsten Glaser  (supplier of updated musescore 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: SHA384

Format: 1.8
Date: Wed, 09 Aug 2017 14:11:19 +0200
Source: musescore
Binary: musescore musescore-common
Architecture: source
Version: 2.1.0+dfsg1-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Thorsten Glaser 
Description:
 musescore  - Free music composition and notation software
 musescore-common - Free music composition and notation software (common files)
Closes: 871075
Changes:
 musescore (2.1.0+dfsg1-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload (could conceivably be team, though).
   * Further update lintian overrides.
   * Upload to unstable. (Closes: #871075)
   * Add Keywords to desktop file, thanks lintian.
Checksums-Sha1:
 dd69356511df31d12f75b46803192406ababbd78 2454 musescore_2.1.0+dfsg1-0.2.dsc
 53c41ad3fe17fb123271a01a5c596f6406257eff 27756 
musescore_2.1.0+dfsg1-0.2.debian.tar.xz
Checksums-Sha256:
 d11cb268451ae970f520ca4390f25b23042ece9817599c9de6c4c63182b04335 2454 
musescore_2.1.0+dfsg1-0.2.dsc
 39110283b523dd5715892f61ed7c3d1b86405a57a0c109083b39845d61466769 27756 
musescore_2.1.0+dfsg1-0.2.debian.tar.xz
Files:
 99e6bff62564035eeb8c2d546b09dc74 2454 sound optional 
musescore_2.1.0+dfsg1-0.2.dsc
 d3881ee07656b773ccb30aba9488d2a8 27756 sound optional 
musescore_2.1.0+dfsg1-0.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJZiwbyAAoJEHa1NLLpkAfg74kQAMWyf+ZMRcisMAIiz/NJ0hOF
CUveqe9i1fU7J/wB1oo41EDcB+HbNaPT4U2x2PCFOD9ISqAIR8BpxXzzNTRODAip
E9ps5XkI0FvJSjBiR+nWscaFnqL5e8BuRXp1cBH4EfJtGouWGjaE0AjQXr9VoSLn
v7aa+0j5J2nzasKkdoiIjvBuqaZ5y72lNZYV4vjgkc92+fu8JKru42BbLr3W5OUd
o6epHsDLOwflE1UzQGxxoWoXrDExFSzNUVxbsk6gPcdlUK3+9DstpUk3cUh34698

Bug#867088: gucharmap build-depends on unicode-data (< 9.1) but 10.0.0-1 is to be installed

2017-08-09 Thread Jeremy Bicha

Control: tags -1 +pending

This bug is fixed in gucharmap 10. The update was ready a month ago; I
just need a sponsor.

It's in pkg-gnome svn.

Thanks,
Jeremy Bicha

Processed: Re: gucharmap build-depends on unicode-data (< 9.1) but 10.0.0-1 is to be installed

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +pending
Bug #867088 [src:gucharmap] gucharmap build-depends on unicode-data (< 9.1) but 
10.0.0-1 is to be installed
Added tag(s) pending.

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

Processed: Bug#871339 marked as pending

2017-08-09 Thread Debian Bug Tracking System

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

> tag 871339 pending
Bug #871339 [src:ipywidgets] ipywidgets: FTBFS: dh_sphinxdoc: 
debian/python-ipywidgets-doc/usr/share/doc/python-ipywidgets-doc/html/_static/bootstrap-3/js/bootstrap.min.js
 is missing
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871339: marked as pending

2017-08-09 Thread Ximin Luo

tag 871339 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/ipywidgets.git/commit/?id=a9ea22e

---
commit a9ea22e23a8036d24274ec6fffd2e2386d3937a6
Author: Ximin Luo 
Date:   Wed Aug 9 14:40:06 2017 +0200

Prepare for uploading to unstable

diff --git a/debian/changelog b/debian/changelog
index 305bcec..f300629 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
 ipywidgets (6.0.0-2) UNRELEASED; urgency=medium
 
+  [ Tobias Hansen ]
   * Add Breaks: sagemath-jupyter (<< 8.0~) to prevent testing migration
 before sagemath 8.0.
 
- -- Tobias Hansen   Wed, 26 Jul 2017 10:28:11 +0100
+  [ Ximin Luo ]
+  * Upload to unstable. (Closes: #871339)
+
+ -- Ximin Luo   Wed, 09 Aug 2017 14:39:55 +0200
 
 ipywidgets (6.0.0-1) experimental; urgency=medium

Bug#871573: insighttoolkit4 fails to build from source

2017-08-09 Thread Matthias Klose

Package: src:insighttoolkit4
Version: 4.12.0-dfsg1-1
Severity: serious
Tags: sid buster

[...]
[ 55%] Generating ../../itkFixedArray.xml
cd
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/Modules/ITKCommon
&& /usr/bin/castxml -o
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/itkFixedArray.xml
--castxml-gccxml --castxml-start _wrapping_ --castxml-cc-gnu "(" /usr/bin/c++ -g
-O2 -fdebug-prefix-map=/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -I/usr/include/nifti -Wall -Wcast-align
-Wdisabled-optimization -Wextra -Wformat=2 -Winvalid-pch -Wno-format-nonliteral
-Wpointer-arith -Wshadow -Wunused -Wwrite-strings -funit-at-a-time
-Wno-strict-overflow -Wno-deprecated -Wno-invalid-offsetof -Woverloaded-virtual
-Wstrict-null-sentinel ")" -w -c
@/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/ITKCommon.castxml.inc
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/itkFixedArray.cxx
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/itkFixedArray.cxx:1:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkCommand.h:21:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkObject.h:31:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkLightObject.h:21:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkMacro.h:47:
In file included from /usr/include/c++/7/string:52:
In file included from /usr/include/c++/7/bits/basic_string.h:6159:
In file included from /usr/include/c++/7/ext/string_conversions.h:41:
In file included from /usr/include/c++/7/cstdlib:77:
/usr/include/c++/7/bits/std_abs.h:103:16: error: invalid operands to binary
expression ('__castxml__float128' (aka '__castxml__float128_s') and 'int')
  { return __x < 0 ? -__x : __x; }
   ~~~ ^ ~
/usr/include/c++/7/bits/stl_pair.h:449:5: note: candidate template ignored:
could not match 'pair' against
'__castxml__float128_s'
operator<(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
^
/usr/include/c++/7/bits/stl_iterator.h:305:5: note: candidate template ignored:
could not match 'reverse_iterator' against
'__castxml__float128_s'
operator<(const reverse_iterator<_Iterator>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:343:5: note: candidate template ignored:
could not match 'reverse_iterator' against
'__castxml__float128_s'
operator<(const reverse_iterator<_IteratorL>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:1142:5: note: candidate template ignored:
could not match 'move_iterator' against 
'__castxml__float128_s'
operator<(const move_iterator<_IteratorL>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:1148:5: note: candidate template ignored:
could not match 'move_iterator' against 
'__castxml__float128_s'
operator<(const move_iterator<_Iterator>& __x,
^
/usr/include/c++/7/bits/basic_string.h:5892:5: note: candidate template ignored:
could not match 'basic_string' against '__castxml__float128_s'
operator<(const basic_string<_CharT, _Traits, _Alloc>& __lhs,
^
/usr/include/c++/7/bits/basic_string.h:5905:5: note: candidate template ignored:
could not match 'basic_string' against '__castxml__float128_s'
operator<(const basic_string<_CharT, _Traits, _Alloc>& __lhs,
^
/usr/include/c++/7/bits/basic_string.h:5917:5: note: candidate template ignored:
could not match 'const _CharT *' against '__castxml__float128' (aka
'__castxml__float128_s')
operator<(const _CharT* __lhs,
^
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/BUILD/Wrapping/itkFixedArray.cxx:1:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkCommand.h:21:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkObject.h:31:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkLightObject.h:21:
In file included from
/home/packages/tmp/insighttoolkit4-4.12.0-dfsg1/Modules/Core/Common/include/itkMacro.h:47:
In file included from /usr/include/c++/7/string:52:
In file included from /usr/include/c++/7/bits/basic_string.h:6159:
In file included from /usr/include/c++/7/ext/string_conversions.h:41:
In file included from /usr/include/c++/7/cstdlib:77:
/usr/include/c++/7/bits/std_abs.h:103:22: error: invalid argument type
'__castxml__float128' (aka '__castxml__float128_s') to unary expression
  { return __x < 0 ? -__x : __x; }
 ^~~~
/usr/include/c++/7/bits/std_abs.h:102:3: error: no return statement in constexpr
function

Bug#871572: urweb FTBFS with gcc 7 on arm64 and mips64el: test failure

2017-08-09 Thread Adrian Bunk

Source: urweb
Version: 20170720+dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/history/urweb.html
https://buildd.debian.org/status/package.php?p=urweb=sid

...
   dh_auto_test -a -O--parallel
make -j6 test VERBOSE=1
make[1]: Entering directory '/<>/urweb-20170720+dfsg'
bin/urweb -boot -noEmacs -dbms sqlite -db /tmp/urweb.db -demo /Demo demo
Unresolved constraint in top.ur
loc: 
/<>/urweb-20170720+dfsg/lib/ur/top.ur:391:4-391:12
 c1:  
 c2:  [#B = ()]
unhandled exception: Fail: Unresolved constraint in top.ur
Makefile:935: recipe for target 'test' failed
make[1]: *** [test] Error 1

Bug#871509: marked as done (hides build failures: mklib exit code not checked)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 12:36:03 +
with message-id 
and subject line Bug#871509: fixed in xpa 2.1.18-2
has caused the Debian Bug report #871509,
regarding hides build failures: mklib exit code not checked
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.)


-- 
871509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpa
Version: 2.1.18-1
Tags: upstream
Severity: serious
Justification: policy 4.6

The shlib target in xpa's Makefile.in says:

|   ./mklib -ldflags "$(LDFLAGS)" -o $(PACKAGE) `LC_ALL=C ls 
lib$(PACKAGE).tmp/*.o`; \
|   rm -rf lib$(PACKAGE).tmp)

If mklib fails, the error is ignored and the build continues potentially
creating broken packages. This violates the Debian policy section 4.6. I
learned it the hard way as mklib did fail here (though that's not a
fault of xpa).

Helmut
--- End Message ---
--- Begin Message ---
Source: xpa
Source-Version: 2.1.18-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated xpa 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, 09 Aug 2017 13:32:17 +0200
Source: xpa
Binary: libxpa1 libxpa-dev xpa-tools tcl-xpa
Architecture: source
Version: 2.1.18-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 libxpa-dev - Seamless communication between Unix programs (development files)
 libxpa1- Seamless communication between Unix programs (shared library)
 tcl-xpa- Seamless communication between Unix programs (Tcl interface)
 xpa-tools  - Tools for seamless communication between Unix programs
Closes: 871509
Changes:
 xpa (2.1.18-2) unstable; urgency=medium
 .
   * Recognise the exit status of mklibs (Closes: #871509)
   * Push Standards-Version to 4.0.0. No changes required.
Checksums-Sha1:
 d20284eae18196da4b102550e2fb26423a64323e 2173 xpa_2.1.18-2.dsc
 aa87b454906ce660013ea3c8f4078c07a4ebdadd 10768 xpa_2.1.18-2.debian.tar.xz
Checksums-Sha256:
 9d1b5513bcab37bc6a49a925ae5891540628934361a12cebb268d60dac291e7e 2173 
xpa_2.1.18-2.dsc
 0bc71334e04140d638774a79f5e2258a7810fa80b11a7da0ae6c6a3652e55ee5 10768 
xpa_2.1.18-2.debian.tar.xz
Files:
 142d1db2c075009705672ce1c159a433 2173 science optional xpa_2.1.18-2.dsc
 3be304b43c4fca9f6a90c669c4d1b6b5 10768 science optional 
xpa_2.1.18-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlmK86IACgkQcRWv0HcQ
3PdDsA//TyC91mFIeun5bmF+NngdT3gUwhesRphaBSVh8lA6pMhQr7Lt/OoxkJyY
Y9ekHzk/MjPPRn7y97aLwHrPfj/TS9+n+9mGh3Ol+O/Oye+0BEWqDNLIOjdp8gOS
VS5zncakxjMyplNA594VtJ07faIeh8CMxOv1ZKOThYnnW+RnZh68RdIkIwV6XWV8
mssY/MRvEOKc9jTCBsDikca/RQTfVo6XU2xUfXgQp6ACe9YG0vz1yaY5iqdR4tJ1
l4pSejpeDkD+0KUT6f2PLvlPj2ifOJR+sX7EsJjSEO0wcM6CgX1iEaMNOJd6W2YM
hp1w5YpEn9of20PAw/1lR1DsXEIWkVltlV5Oufolx8PRHQ/7yLbL5P91KB6ZkG6F
oPKVNuj0SkZsjnS7UcWOfzy6wpWENN1nIe09k9sIhyQPgyx316FmAYFzod/INGLt
y4YSKO/WksYcZzt7GmdmTSrjpJGkvlMkG7DScGbnlwwOq3fuK1tRT4aNgxjUc65O
+qIT3wD8iPzEkD+NRj5CvJT58kidc0VhF/imw9rBY73VPImXIdKvfVauFqPccpGW
aY05rqEMVbPX2wmGSroGnjiiawb6mTwn7Hlc1w6zlJZ2Wj3/hezIyG9oAplRoCQS
MlztcKbldNWEPoVJh0IT8xr+r45ITlvkzXczX3yPPxat6zim6ss=
=prQp
-END PGP SIGNATURE End Message ---

Bug#871282: insighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-09 Thread Gert Wollny

Control: tags -1 wontfix 

Version 4.12 is in unstable, was already build using gcc-7, and will
soon transition to testing thereby removing v4.10 from the archives. 

Best, 
Gert

Processed: Re: insighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 wontfix
Bug #871282 [libinsighttoolkit4.10] libinsighttoolkit4.10: requires rebuild 
against GCC 7 and symbols/shlibs bump
Added tag(s) wontfix.

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

Bug#864822: marked as done (firefox: FTBFS: Don't know how to translate powerpc64le-unknown-linux-gnu for rustc)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 12:26:58 +
with message-id 
and subject line Bug#864822: fixed in firefox 55.0-1
has caused the Debian Bug report #864822,
regarding firefox: FTBFS: Don't know how to translate 
powerpc64le-unknown-linux-gnu for rustc
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.)


-- 
864822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox
Version: 54.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

The ppc64el build of firefox failed, apparently because the build
system didn't know how to work with rustc there:

  checking for rustc... /usr/bin/rustc
  checking for cargo... /usr/bin/cargo
  checking rustc version... 1.16.0
  checking cargo version... 0.17.0
  ERROR: Don't know how to translate powerpc64le-unknown-linux-gnu for rustc
  debian/rules:213: recipe for target 'stamps/configure-browser' failed
  make[1]: *** [stamps/configure-browser] Error 1
  make[1]: Leaving directory '/<>'
  debian/rules:358: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 55.0-1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox 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, 09 Aug 2017 20:21:59 +0900
Source: firefox
Binary: firefox firefox-l10n-all firefox-l10n-ach firefox-l10n-af 
firefox-l10n-an firefox-l10n-ar firefox-l10n-as firefox-l10n-ast 
firefox-l10n-az firefox-l10n-be firefox-l10n-bg firefox-l10n-bn-bd 
firefox-l10n-bn-in firefox-l10n-br firefox-l10n-bs firefox-l10n-ca 
firefox-l10n-cak firefox-l10n-cs firefox-l10n-cy firefox-l10n-da 
firefox-l10n-de firefox-l10n-dsb firefox-l10n-el firefox-l10n-en-gb 
firefox-l10n-en-za firefox-l10n-eo firefox-l10n-es-ar firefox-l10n-es-cl 
firefox-l10n-es-es firefox-l10n-es-mx firefox-l10n-et firefox-l10n-eu 
firefox-l10n-fa firefox-l10n-ff firefox-l10n-fi firefox-l10n-fr 
firefox-l10n-fy-nl firefox-l10n-ga-ie firefox-l10n-gd firefox-l10n-gl 
firefox-l10n-gn firefox-l10n-gu-in firefox-l10n-he firefox-l10n-hi-in 
firefox-l10n-hr firefox-l10n-hsb firefox-l10n-hu firefox-l10n-hy-am 
firefox-l10n-id firefox-l10n-is firefox-l10n-it firefox-l10n-ja firefox-l10n-ka 
firefox-l10n-kab firefox-l10n-kk firefox-l10n-km firefox-l10n-kn firefox-l10n-ko
 firefox-l10n-lij firefox-l10n-lt firefox-l10n-lv firefox-l10n-mai 
firefox-l10n-mk firefox-l10n-ml firefox-l10n-mr firefox-l10n-ms firefox-l10n-my 
firefox-l10n-nb-no firefox-l10n-nl firefox-l10n-nn-no firefox-l10n-or 
firefox-l10n-pa-in firefox-l10n-pl firefox-l10n-pt-br firefox-l10n-pt-pt 
firefox-l10n-rm firefox-l10n-ro firefox-l10n-ru firefox-l10n-si firefox-l10n-sk 
firefox-l10n-sl firefox-l10n-son firefox-l10n-sq firefox-l10n-sr 
firefox-l10n-sv-se firefox-l10n-ta firefox-l10n-te firefox-l10n-th 
firefox-l10n-tr firefox-l10n-uk firefox-l10n-ur firefox-l10n-uz firefox-l10n-vi 
firefox-l10n-xh firefox-l10n-zh-cn
 firefox-l10n-zh-tw
Architecture: source
Version: 55.0-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 firefox- Mozilla Firefox web browser
 firefox-l10n-ach - Acoli language package for Firefox
 firefox-l10n-af - Afrikaans language package for Firefox
 firefox-l10n-all - All language packages for Firefox (meta)
 firefox-l10n-an - Aragonese language package for Firefox
 firefox-l10n-ar - Arabic language package for Firefox
 firefox-l10n-as - Assamese language package for Firefox
 firefox-l10n-ast - Asturian language package for Firefox
 firefox-l10n-az - Azerbaijani language package for Firefox
 firefox-l10n-be - Belarusian language

Bug#871386: marked as done (firefox: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 12:26:58 +
with message-id 
and subject line Bug#871386: fixed in firefox 55.0-1
has caused the Debian Bug report #871386,
regarding firefox: FTBFS: cc1: error: -Wformat-security ignored without 
-Wformat [-Werror=format-security]
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.)


-- 
871386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox
Version: 54.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> /usr/bin/gcc -std=gnu99 -o nr_crypto.o -c 
> -I/<>/build-browser/dist/system_wrappers -include 
> /<>/config/gcc_hidden.h -DNDEBUG -DTRIMMED=1 
> -D_FILE_OFFSET_BITS=64 -DCHROMIUM_BUILD -DUSE_LIBJPEG_TURBO=1 -DUSE_NSS=1 
> -DENABLE_ONE_CLICK_SIGNIN -DGTK_DISABLE_SINGLE_INCLUDES=1 -D_ISOC99_SOURCE=1 
> -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_CONFIGURATION_POLICY 
> -DENABLE_INPUT_SPEECH -DENABLE_NOTIFICATIONS -DENABLE_GPU=1 
> -DENABLE_EGLIMAGE=1 -DUSE_SKIA=1 -DENABLE_TASK_MANAGER=1 
> -DENABLE_WEB_INTENTS=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGIN_INSTALLATION=1 
> -DENABLE_PROTECTOR_SERVICE=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 
> -DENABLE_BACKGROUND=1 -DENABLE_AUTOMATION=1 -DENABLE_PRINTING=1 
> -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DSANITY_CHECKS -DUSE_TURN -DUSE_ICE 
> -DUSE_RFC_3489_BACKWARDS_COMPATIBLE -DUSE_STUND_0_96 -DUSE_STUN_PEDANTIC 
> -DNR_SOCKET_IS_VOID_PTR -Drestrict= '-DR_PLATFORM_INT_TYPES=' 
> -DR_DEFINED_INT2=int16_t -DR_DEFINED_UINT2=uint16_t -DR_DEFINED_INT4=int32_t 
> -DR_DEFINED_UINT4=uint32_t -DR_DEFINED_INT8=int64_t 
> -DR_DEFINED_UINT8=uint64_t -DLINUX -DHAVE_LIBM=1 -DHAVE_STRDUP=1 
> -DHAVE_STRLCPY=1 -DHAVE_SYS_TIME_H=1 -DHAVE_VFPRINTF=1 
> -DNEW_STDIORETSIGTYPE=void -DTIME_WITH_SYS_TIME_H=1 
> '-D__UNUSED__=__attribute__((unused))' -DNVALGRIND 
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE 
> -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL 
> -I/<>/media/mtransport/third_party/nICEr 
> -I/<>/build-browser/media/mtransport/third_party/nICEr/nicer_nicer
>  -I/<>/media/mtransport/third_party/nrappkit/src/event 
> -I/<>/media/mtransport/third_party/nrappkit/src/log 
> -I/<>/media/mtransport/third_party/nrappkit/src/plugin 
> -I/<>/media/mtransport/third_party/nrappkit/src/registry 
> -I/<>/media/mtransport/third_party/nrappkit/src/share 
> -I/<>/media/mtransport/third_party/nrappkit/src/stats 
> -I/<>/media/mtransport/third_party/nrappkit/src/util 
> -I/<>/media/mtransport/third_party/nrappkit/src/util/libekr 
> -I/<>/media/mtransport/third_party/nrappkit/src/port/generic/include
>  -I/<>/media/mtransport/third_party/nICEr/src/crypto 
> -I/<>/media/mtransport/third_party/nICEr/src/ice 
> -I/<>/media/mtransport/third_party/nICEr/src/net 
> -I/<>/media/mtransport/third_party/nICEr/src/stun 
> -I/<>/media/mtransport/third_party/nICEr/src/util 
> -I/<>/media/mtransport/third_party/nrappkit/src/port/linux/include
>  -I/<>/build-browser/ipc/ipdl/_ipdlheaders 
> -I/<>/ipc/chromium/src -I/<>/ipc/glue 
> -I/<>/build-browser/dist/include-fPIC  -include 
> /<>/build-browser/mozilla-config.h -DMOZILLA_CLIENT -MD -MP -MF 
> .deps/nr_crypto.o.pp -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body 
> -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits 
> -Wunreachable-code -Wno-error=maybe-uninitialized 
> -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wformat 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-schedule-insns2 -fno-lifetime-dse -fno-delete-null-pointer-checks 
> -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno 
> -pthread -pipe  -g -freorder-blocks -Os -fomit-frame-pointer -Wall 
> -Wno-parentheses -Wno-strict-prototypes -Wmissing-prototypes -Wno-format  
> /<>/media/mtransport/third_party/nICEr/src/crypto/nr_crypto.c
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> /<>/config/rules.mk:886: recipe for target 'nr_crypto.o' failed
> make[6]: *** [nr_crypto.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/firefox_54.0-2_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

Bug#866024: Followup for removal of pygpgme from unstable

2017-08-09 Thread Dr. Tobias Quathamer

Dear Jonathan,

a few days ago, pygpgme has been autoremoved from testing. Are you going
to ask ftpmaster to remove it from unstable now, as announced in #846314
and #866026? Or does anything still prevent this?

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#865814: marked as done (django-tables FTBFS with Django 1.11)

2017-08-09 Thread Debian Bug Tracking System

Your message dated Wed, 09 Aug 2017 11:39:56 +
with message-id 
and subject line Bug#865814: fixed in django-tables 1.10.0-1
has caused the Debian Bug report #865814,
regarding django-tables FTBFS with Django 1.11
to be marked as done.

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

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


-- 
865814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-tables
Version: 1.2.0-1
Severity: serious
Tags: buster sid

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} /usr/bin/py.test"
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 /usr/bin/py.test
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
django settings: tests.app.settings (from ini file)
rootdir: /build/1st/django-tables-1.2.0, inifile: tox.ini
plugins: django-2.9.1
collected 178 items

tests/test_config.py ..
tests/test_core.py .
tests/test_models.py 
tests/test_rows.py ..
tests/test_templates.py 
tests/test_templatetags.py .
tests/test_utils.py 
tests/test_views.py ...
tests/columns/test_booleancolumn.py ...
tests/columns/test_checkboxcolumn.py .
tests/columns/test_datecolumn.py 
tests/columns/test_datetimecolumn.py 
tests/columns/test_emailcolumn.py 
tests/columns/test_filecolumn.py 
tests/columns/test_general.py ..
tests/columns/test_linkcolumn.py 
tests/columns/test_templatecolumn.py F
tests/columns/test_timecolumn.py ..
tests/columns/test_urlcolumn.py 

=== FAILURES ===
_ test_should_handle_context_on_table __

def test_should_handle_context_on_table():
class TestTable(tables.Table):
col_code = tables.TemplateColumn(template_code='code:{{ record.col 
}}{{ STATIC_URL }}')
col_name = 
tables.TemplateColumn(template_name='test_template_column.html')

table = TestTable([{'col': 'brad'}])
assert table.rows[0].get_cell('col_code') == 'code:brad'
>   assert table.rows[0].get_cell('col_name') == 'name:brad'

tests/columns/test_templatecolumn.py:17: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
django_tables2/rows.py:150: in get_cell
return self._call_render(bound_column, value)
django_tables2/rows.py:170: in _call_render
return bound_column.render(**kwargs)
django_tables2/columns/templatecolumn.py:71: in render
return template.render(context)
/usr/lib/python2.7/dist-packages/django/template/backends/django.py:64: in 
render
context = make_context(context, request, 
autoescape=self.backend.engine.autoescape)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

context = [{'False': False, 'None': None, 'True': True}], request = None
kwargs = {'autoescape': True}

def make_context(context, request=None, **kwargs):
"""
Create a suitable Context from a plain dict and optionally an 
HttpRequest.
"""
if context is not None and not isinstance(context, dict):
>   raise TypeError('context must be a dict rather than %s.' % 
> context.__class__.__name__)
E   TypeError: context must be a dict rather than Context.

/usr/lib/python2.7/dist-packages/django/template/context.py:287: TypeError
= 1 failed, 177 passed in 2.44 seconds =
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
/usr/bin/py.test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} /usr/bin/py.test returned exit code 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: django-tables
Source-Version: 1.10.0-1

We believe that the bug you reported is fixed in the latest version of
django-tables, 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 865...@bugs.debian.org,
and the

Bug#871570: git FTBFS on i386: t7006-pager.sh test failure

2017-08-09 Thread Adrian Bunk

Source: git
Version: 1:2.14.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=git=i386=1%3A2.14.0-1=1502132890=0

...
expecting success: 
(
sane_unset LESS LV &&
PAGER="env >pager-env.out; wc" &&
export PAGER &&
PATH="$(git --exec-path):$PATH" &&
export PATH &&
test_terminal sh -c ". git-sh-setup && git_pager"
) &&
grep ^LESS= pager-env.out &&
grep ^LV= pager-env.out

wc: 'standard input': Input/output error
  0   0   0
not ok 6 - LESS and LV envvars set by git-sh-setup
...
# still have 3 known breakage(s)
# failed 1 among remaining 75 test(s)
1..78
Makefile:49: recipe for target 't7006-pager.sh' failed
make[4]: *** [t7006-pager.sh] Error 1

1 2 >

1 - 100 of 128 matches

Mail list logo