Processed: bug 844139 is forwarded to https://code.djangoproject.com/ticket/27526

[Debian Bug Tracking System]

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

> forwarded 844139 https://code.djangoproject.com/ticket/27526
Bug #844139 [src:python-django] python-django: FTBFS: Tests failures
Set Bug forwarded-to-address to 'https://code.djangoproject.com/ticket/27526'.
> thanks
Stopping processing here.

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

Bug#844922: [Pkg-javascript-devel] Bug#844922: Node-string-decoder

[Jérémy Lal]

2016-11-23 8:53 GMT+01:00 Ross Gammon :
> Hi,
>
> This node module was originally packaged as it was a dependency of something
> (I can't remember).
>
> If there is nothing depending on it, we should probably remove it from the
> archive. The string-decoder function from the core nodejs should be used
> instead (patching the module that needs it if required). Node-string-decoder
> is mainly used when a nodejs project wants to stick to an old version of
> this function.
>
> Regards,

All right, can you fill the ftp.debian.org RM request please ?

Jérémy

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018, 
>   please post to that bug. I know that my patch is not pretty, 
> but 
>   I did not find any better short-term solution.

Search for CURLOPT_SSL_CTX_FUNCTION on codesearch.debian.net produces
the following list of potentially affected packages:
cargo
chromium-browser
cmake
criticalmass
curl
curlpp
firefox
firefox-esr
fpc
hhvm
icedove
lastpass-cli
libapache2-mod-auth-cas
libwww-curl-perl
lua-curl
netcdf
netsurf
openjfx
r-cran-curl
r-cran-rcurl
ruby-curb
slcurl
sx
tclcurl
wpa
xmltooling
zurl

So the the alternative to you patch looks like:

fixing #828564 (fixed-upstream, new upstream version available),
fixing #828608 or removing xmltooling out of testing,
checking whether last apache2 upload fixed #844799,
fixing or ignoring #828259 (not in testing, fixed upstream version
available),
fixing #828371 (untested patch available) or removing lastpass-cli,
removing 3 characters from zurl's debian/control,
binnmu-ing affected packages that still depend on libssl1.0.2,
no need to ensure that applications (even if they are linked with
libcurl3 indirectly) are linked with the same libssl as libcurl3
(unlike with the patch),
more compatibility with applications from jessie than with the patch.

Bug#844856: flightcrew: FTBFS: CheckSymbolExists.cxx:8:19: error: 'Q_WS_WIN' was not declared in this scope

[Gianfranco Costamagna]

control: tags -1 patch

> Relevant part (hopefully):
> > /usr/bin/c++-I/usr/include/qt4  -g -O2 
> > -fdebug-prefix-map=/<>/flightcrew-0.7.2+dfsg=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2-o CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o 
> > -c 
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
> >  In function 'int main(int, char**)':
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
> >  error: 'Q_WS_WIN' was not declared in this scope
> >return ((int*)(&Q_WS_WIN))[argc];
> >^~~~
> > CMakeFiles/cmTC_aec35.dir/build.make:65: recipe for target 
> > 'CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o' failed
> > make[3]: *** [CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o] Error 1
> 

it wasn't the relevant part :p

CMake Error at src/FlightCrew/tests/CMakeLists.txt:67 (add_library):
  Cannot find source file:

/usr/src/gtest/src/gtest-all.cc

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx


CMake Error: Cannot determine link language for target "GOOGLE_MOCK_LIB".
CMake Error: CMake can not determine linker language for target: GOOGLE_MOCK_LIB

this is the correct one.

Adding libgtest-dev to build-dependencies solves the issue and brings that file 
back.
(this is probably something due to the recent introduction of the new 
src:googletest package.

cheers,

G.



signature.asc
Description: OpenPGP digital signature

Bug#811907: music: FTBFS with GCC 6: invalid conversion

[Graham Inggs]

Control: tags -1 patch

The patch below fixes the FTBFS with GCC 6.


--- a/src/connectivity.cc
+++ b/src/connectivity.cc
@@ -89,7 +89,7 @@
 std::map::iterator info
   = connectivityMap.find (portName);
 if (info == connectivityMap.end ())
-  return NO_CONNECTIVITY;
+  return (ConnectivityInfo*)NO_CONNECTIVITY;
 else
   return &connections_[info->second];
   }

Processed: Re: flightcrew: FTBFS: CheckSymbolExists.cxx:8:19: error: 'Q_WS_WIN' was not declared in this scope

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #844856 [src:flightcrew] flightcrew: FTBFS: CheckSymbolExists.cxx:8:19: 
error: 'Q_WS_WIN' was not declared in this scope
Added tag(s) patch.

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

Processed: music: FTBFS with GCC 6: invalid conversion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811907 [music] music: FTBFS with GCC 6: invalid conversion
Added tag(s) patch.

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

Bug#845420: can't add IRC nicks to a contact, Jabber is a trademark

[Daniel Pocock]

Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: serious

Editing a contact in Evolution, there is a section on the first tab,
"Instant Messaging" where it allows people to select options like "MSN"
or "Skype".

There is no apparent way to specify other contact types here.

Given that Debian and GNOME have a strong emphasis on using IRC, it
seems silly that IRC is not one of the options.

Jabber[1] is a Cisco trademark, this option could become "XMPP" or maybe
"XMPP (Jabber^TM)"

It would also be very desirable to permit SIP and Ring[2] addresses here
too.



1. https://xmpp.org/about/xsf/jabber-trademark
2. https://ring.cx/en/documentation/faq#node-88

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Adrian Bunk]

On Wed, Nov 23, 2016 at 11:59:16AM +0400, Stepan Golosunov wrote:
> 22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> > 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018, 
> >   please post to that bug. I know that my patch is not pretty, 
> > but 
> >   I did not find any better short-term solution.
> 
> Search for CURLOPT_SSL_CTX_FUNCTION on codesearch.debian.net produces
> the following list of potentially affected packages:
> cargo
> chromium-browser
> cmake
> criticalmass
> curl
> curlpp
> firefox
> firefox-esr
> fpc
> hhvm
> icedove
> lastpass-cli
> libapache2-mod-auth-cas
> libwww-curl-perl
> lua-curl
> netcdf
> netsurf
> openjfx
> r-cran-curl
> r-cran-rcurl
> ruby-curb
> slcurl
> sx
> tclcurl
> wpa
> xmltooling
> zurl
> 
> So the the alternative to you patch looks like:
>...
> fixing #828608 or removing xmltooling out of testing,
>...

"removing xmltooling out of testing" is not an option.

Either *all* packages in this cluster get fixes to work with 1.1,
or the whole cluster must stay at 1.0.2 in stretch.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?

[Michael Tokarev]

23.11.2016 05:34, NeilBrown wrote:
> On Tue, Nov 22 2016, Andy Smith wrote:
> 
>> Hi Neil,
>>
>> On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
>>> Thanks.  Sorry this is taking a lot of back-and-forth...
>>
>> No worries. This is very interesting to me and I'd also like to know
>> what is going wrong even if I have a work-around.
> 
> Thanks.
> I tried this on a scratch Debian VM I had lying around, and found I
> could exactly reproduce your symptoms.
> I found that, unlike on the first Debian system I looked at, there is a
> line in  /lib/udev/rules.d/64-md-raid-assembly.rules 
> 
>   # Disable incremental assembly to fix Debian bug #784070
>   GOTO="md_inc_end"
> 
> Remove that and the problem goes away.  Arrgg...
> 
> I wish people maintainers would *ask* upstream when they don't
> understand, rather than just breaking things.

Neil, with all my respect, this is a bit over-reaction :)

It was long ago when we disabled incremental assembly when
you turned it on by default, and kept old static way to
assemble arrays, because neither our initrd nor regular
userpsace weren't ready for that.  At the time jessie come
out, we didn't have enough time to sort it out, so we kept
it for jessie too.

After restoring your (upstream) rules, things WILL break in
other place.  Someone already tried that and had to revert
it back to what we have now. Initrd should have some
initial infrastructure for event-based work before this will
be possible.

I wanted to fix it all for stretch. But once I had a conflict
with the d-i team I don't work on mdadm (or any other package
touching d-i) anymore.

Thanks,

/mjt

Bug#845405: marked as done (x11-common: configure fails at "db_purge" with exit status 20 "Incorrect number of arguments")

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 09:04:35 +
with message-id 
and subject line Bug#845398: fixed in xorg 1:7.7+18
has caused the Debian Bug report #845398,
regarding x11-common: configure fails at "db_purge" with exit status 20 
"Incorrect number of arguments"
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.)


-- 
845398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-common
Version: 1:7.7+17

After today's upload, the configure step of "x11-common" fails
(presumably thanks to the addition of "set -x"):

> $ sudo DEBCONF_DEBUG=developer dpkg --configure x11-common
> Setting up x11-common (1:7.7+17) ...
> debconf (developer): frontend started
> debconf (developer): frontend running, package name is x11-common
> debconf (developer): starting /var/lib/dpkg/info/x11-common.postinst
> configure 1:7.7+16
> debconf (developer): <-- PURGE x11-common/xwrapper/allowed_users
> debconf (developer): --> 20 Incorrect number of arguments
> dpkg: error processing package x11-common (--configure):
>  subprocess installed post-installation script returned error exit status 20
> Errors were encountered while processing:
>  x11-common

It would appear that "db_purge" is only intended for use during
package removal, and that perhaps "db_unregister" was intended
instead?

>From the debconf-devel manpage:

>UNREGISTER question
>   This removes a question from the database.
>
>PURGE  Call this in your postrm when your package is purged. It removes
>   all of your package's questions from debconf's database.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
--- End Message ---
--- Begin Message ---
Source: xorg
Source-Version: 1:7.7+18

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg 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, 23 Nov 2016 08:50:50 +0100
Source: xorg
Binary: x11-common xserver-xorg xserver-xorg-video-all xserver-xorg-input-all 
xorg xorg-dev xbase-clients xutils
Architecture: source
Version: 1:7.7+18
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 x11-common - X Window System (X.Org) infrastructure
 xbase-clients - miscellaneous X clients - metapackage
 xorg   - X.Org X Window System
 xorg-dev   - X.Org X Window System development libraries
 xserver-xorg - X.Org X server
 xserver-xorg-input-all - X.Org X server -- input driver metapackage
 xserver-xorg-video-all - X.Org X server -- output driver metapackage
 xutils - X Window System utility programs metapackage
Closes: 845398
Changes:
 xorg (1:7.7+18) unstable; urgency=medium
 .
   * Call db_purge without arguments in postinst to fix error uncovered by
 adding "set -e" in 1:7.7+17 (closes: #845398).  Thanks, Samuel Thibault
 and Tianon Gravi!
Checksums-Sha1:
 1380713b8423ff6f2b181d5a65aa12760e0b0007 2016 xorg_7.7+18.dsc
 2b99c8175a2231e6ee36b9bf9ba353672b30fbc1 288649 xorg_7.7+18.tar.gz
Checksums-Sha256:
 c4153fe30e39514f42850fe755f6c3061d033cc39de1b0699fb323efb031965b 2016 
xorg_7.7+18.dsc
 5ad85af315eab218a146484a15297f3ded2aecb8e8504a110bb494ed09d24de2 288649 
xorg_7.7+18.tar.gz
Files:
 c2bf41a365f695adbf84c4b3e8b3576b 2016 x11 optional xorg_7.7+18.dsc
 7d5c72af26db853a718bc46de3402d7c 288649 x11 optional xorg_7.7+18.tar.gz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAlg1SvsUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z63QVQ//fCrvKvW6i8ib+Q1x5U0v4HuVDE7t
M1M2tC9F1UvmPOlqUHW6jn1hZ69QHUWCvbFQP7XQBUOp/Nr6872YEU2C7Gq6kTDy
kpkAW38zijpzX39BsSUCnrWXIzXreGiG1tKEvQ4LP2toxRBHIBRxwDS+2MS0VH3v
TUoWql/LLtBX8FP9cd2AJewPDL0vxuUJOZ3zFw7iimeHa6tyxfdyyg10KDL/KzbK
E2mlFblew4PmiK0g/ytE7wcWtM/4Ulr7EYn4pf8DOWz3W4YICQ55s7Up9dj6hcAA
CYgWjIlEOV7wNH3Kw7HVO2ZZ49F+hMewfjLmmYfuOXKP420KWUsm7QlSI0hZYLoF
2j06unl5/XNWgbkX8AENrsWGUtkdeLPbqH68K2TmRzeCxPUTENk6CHb

Bug#845398: marked as done (x11-common: Can't configure)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 09:04:35 +
with message-id 
and subject line Bug#845398: fixed in xorg 1:7.7+18
has caused the Debian Bug report #845398,
regarding x11-common: Can't configure
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.)


-- 
845398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-common
Version: 1:7.7+17
Severity: grave
Justification: renders package unusable

Hello,

x11-common can't be installed any more now that x11-common.postinst has
set -e:

Setting up x11-common (1:7.7+17) ...
dpkg: error processing package x11-common (--configure):
 subprocess installed post-installation script returned error exit status 20
Errors were encountered while processing:
 x11-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is because postinst calls

db_purge x11-common/xwrapper/allowed_users
db_purge x11-common/xwrapper/actual_allowed_users

According to debconf-devel(7), the PURGE command doesn't take any
parameter, it is not meant to remove just one entry.

I guess what was meant was rather

db_unregister x11-common/xwrapper/allowed_users
db_unregister x11-common/xwrapper/actual_allowed_users

to remove those old entries.

Samuel

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

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

Versions of packages x11-common depends on:
ii  lsb-base  9.20161101

x11-common recommends no packages.

x11-common suggests no packages.

-- debconf information:
  x11-common/xwrapper/actual_allowed_users: anybody
* x11-common/xwrapper/allowed_users: Anybody

-- 
Samuel
 je viens d'inventer mutt version magritte :D
 ?
 dans mutt
 tape "cceci" return
--- End Message ---
--- Begin Message ---
Source: xorg
Source-Version: 1:7.7+18

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg 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, 23 Nov 2016 08:50:50 +0100
Source: xorg
Binary: x11-common xserver-xorg xserver-xorg-video-all xserver-xorg-input-all 
xorg xorg-dev xbase-clients xutils
Architecture: source
Version: 1:7.7+18
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 x11-common - X Window System (X.Org) infrastructure
 xbase-clients - miscellaneous X clients - metapackage
 xorg   - X.Org X Window System
 xorg-dev   - X.Org X Window System development libraries
 xserver-xorg - X.Org X server
 xserver-xorg-input-all - X.Org X server -- input driver metapackage
 xserver-xorg-video-all - X.Org X server -- output driver metapackage
 xutils - X Window System utility programs metapackage
Closes: 845398
Changes:
 xorg (1:7.7+18) unstable; urgency=medium
 .
   * Call db_purge without arguments in postinst to fix error uncovered by
 adding "set -e" in 1:7.7+17 (closes: #845398).  Thanks, Samuel Thibault
 and Tianon Gravi!
Checksums-Sha1:
 1380713b8423ff6f2b181d5a65aa12760e0b0007 2016 xorg_7.7+18.dsc
 2b99c8175a2231e6ee36b9bf9ba353672b30fbc1 288649 xorg_7.7+18.tar.gz
Checksums-Sha256:
 c4153fe30e39514f42850fe755f6c3061d033cc39de1b0699fb323efb031965b 2016 
xorg_7.7+18.dsc
 5ad85af315eab218a146484a15297f3ded2aecb8e8504a110bb494ed09d24de2 288649 
xorg_7.7+18.tar.gz
Files:
 c2bf41a365f695adbf84c4b3e8b3576b 2016 x11 optional xorg_7.7+18.dsc
 7d5c72af26db853a718bc46de3402d7c 288649 x11 optional xorg_7.7+18.tar.gz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4

Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?

[SOUBEYRAND Yann - externe]

Le mercredi 23 novembre 2016 à 13:34 +1100, ne...@suse.com a écrit :
> On Tue, Nov 22 2016, Andy Smith wrote:
> 
> > Hi Neil,
> >
> > On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
> >> Thanks.  Sorry this is taking a lot of back-and-forth...
> >
> > No worries. This is very interesting to me and I'd also like to know
> > what is going wrong even if I have a work-around.
> 
> Thanks.
> I tried this on a scratch Debian VM I had lying around, and found I
> could exactly reproduce your symptoms.
> I found that, unlike on the first Debian system I looked at, there is a
> line in  /lib/udev/rules.d/64-md-raid-assembly.rules 
> 
>   # Disable incremental assembly to fix Debian bug #784070
>   GOTO="md_inc_end"
> 
> Remove that and the problem goes away.  Arrgg...
> 
> I wish people maintainers would *ask* upstream when they don't
> understand, rather than just breaking things.
> 
> NeilBrown

Hi Neil,

I encourage you to have a look at the full history of this bug to see
why this line was introduced. You will then see that it has been removed
in Stretch.

Regards

Yann



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à 
l'intention exclusive des destinataires et les informations qui y figurent sont 
strictement confidentielles. Toute utilisation de ce Message non conforme à sa 
destination, toute diffusion ou toute publication totale ou partielle, est 
interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le 
copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si 
vous avez reçu ce Message par erreur, merci de le supprimer de votre système, 
ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support 
que ce soit. Nous vous remercions également d'en avertir immédiatement 
l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie 
électronique arrivent en temps utile, sont sécurisées ou dénuées de toute 
erreur ou virus.


This message and any attachments (the 'Message') are intended solely for the 
addressees. The information contained in this Message is confidential. Any use 
of information contained in this Message not in accord with its purpose, any 
dissemination or disclosure, either whole or partial, is prohibited except 
formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any 
part of it. If you have received this message in error, please delete it and 
all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or 
virus-free.

Bug#828481: ori: staying with libssl1.0

[Afif Elghraoui]

Control: severity -1 important
Control: unblock 827061 by -1

This path of staying behind with openssl 1.0 was approved by the release
team [1]. Upstream has not moved on to openssl 1.1 and we aren't
equipped to make and test the required changes.

1. https://lists.debian.org/debian-release/2016/11/msg00573.html

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: ori: staying with libssl1.0

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#845379: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

[Pirate Praveen]

Control: tags -1 pending

On Wednesday 23 November 2016 03:04 AM, Chris Lamb wrote:
>   Warning: Task "coffee" not found. Use --force to continue.

missed builddeps on node-grunt-contrib-coffee. Fixed. But
node-grunt-contrib-coffee needs to clear NEW.




signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #845379 [src:node-fuzzaldrin-plus] node-fuzzaldrin-plus: FTBFS: Npm module 
"grunt-contrib-coffee" not found.
Added tag(s) pending.

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

Bug#845379: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

[Chris Lamb]

Pirate Praveen wrote:

> Control: tags -1 pending
> 
> On Wednesday 23 November 2016 03:04 AM, Chris Lamb wrote:
> >   Warning: Task "coffee" not found. Use --force to continue.
> 
> missed builddeps on node-grunt-contrib-coffee. Fixed. But
> node-grunt-contrib-coffee needs to clear NEW.

ACCEPTED.


Regards,

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

Bug#844963: marked as done (gnome-shell-extension-dashtodock: FTBFS: make[1]: git: Command not found)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 10:00:10 +
with message-id 
and subject line Bug#844963: fixed in gnome-shell-extension-dashtodock 55-3
has caused the Debian Bug report #844963,
regarding gnome-shell-extension-dashtodock: FTBFS: make[1]: git: Command not 
found
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.)


-- 
844963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Version: 55-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: git: Command not found
> rm -fR ./_build
> mkdir -p _build
> cp extension.js stylesheet.css metadata.json COPYING README.md convenience.js 
> dash.js docking.js appIcons.js intellihide.js prefs.js theming.js Settings.ui 
> _build
> mkdir -p _build/media
> cd media ; cp logo.svg ../_build/media/
> mkdir -p _build/schemas
> cp schemas/*.xml _build/schemas/
> cp schemas/gschemas.compiled _build/schemas/
> mkdir -p _build/locale
> for l in po/cs.mo po/hu.mo po/zh_CN.mo po/de.mo po/pt.mo po/ja.mo po/ar.mo 
> po/pl.mo po/it.mo po/ru.mo po/nl.mo po/s...@latin.mo po/sk.mo po/tr.mo 
> po/sr.mo po/es.mo po/sv.mo po/fr.mo po/pt_BR.mo ; do \
>   lf=_build/locale/`basename $l .mo`; \
>   mkdir -p $lf; \
>   mkdir -p $lf/LC_MESSAGES; \
>   cp $l $lf/LC_MESSAGES/dashtodock.mo; \
> done;
> sed -i 's/"version": -1/"version": ""/'  _build/metadata.json;
> rm -rf ~/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com
> mkdir -p ~/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com
> mkdir: cannot create directory '/sbuild-nonexistent': Permission denied
> Makefile:53: recipe for target 'install-local' failed
> make[1]: *** [install-local] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/gnome-shell-extension-dashtodock_55-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: gnome-shell-extension-dashtodock
Source-Version: 55-3

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-dashtodock 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, 16 Nov 2016 09:07:36 +0200
Source: gnome-shell-extension-dashtodock
Binary: gnome-shell-extension-dashtodock
Architecture: source all
Version: 55-3
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Description:
 gnome-shell-extension-dashtodock - dash-to-dock extension for GNOME shell
Closes: 844963
Changes:
 gnome-shell-extension-dashtodock (55-3) unstable; urgency=medium
 .
   * Re-apply path fix patch (Closes: #844963)
   * Upgrade debian/watch to version 4
Checksums-Sha1:
 a5ae7ee1eac3faf7d04dba06d498fe12e69b8bec 2081 
gnome-shell-extension-dashtodock_55-3.dsc
 6f2ea9edab313bd522045a6f171231e5d682b353 3048 
gnome-shell-extension-dashtodock_55-3.debian.tar.xz
 dd117633ee8d86d522b1dcca1e73051416a70150 219328 
gnome-shell-extension-dashtodock_55-3_all.deb
Checksums-Sha256:
 7d65842a85226f50e7de602d55833a988269f2d70cbdddac20a934a4b6326921 2081 
gnome-shell-extension-dashtodock_55-3.dsc
 a23fa7e5c65a865a30d782afb2437ef1330736e73405b9a4484c86d3a2d63045 3048 
gnome-shell-extension-dashtodock_55-3.debian.tar.xz
 1e636fe5a5e027f923a9b75ecf39d27a9d0231c6c61faaf7e3644ace8d3cd7c9 219328 
gnome-shell-extension-das

Bug#844275: [debian-mysql] Bug#844275: mysql_config injects build flags which breaks the build for other packages

[Norvald H. Ryeng]

mysql_config and mysqlclient.pc pick up compile flags from the build
environment. We have a fix for this upstream, and I've backported it to
5.7.16 (see attachment).

I haven't tested it with sbuild/dpkg, so when applying this, please
verify that mysql_config and mysqlclient.pc don't pick up any flags
they shouldn't.

Regards,

Norvalddiff -rup a/scripts/CMakeLists.txt b/scripts/CMakeLists.txt
--- a/scripts/CMakeLists.txt	2016-09-28 19:02:44.0 +0200
+++ b/scripts/CMakeLists.txt	2016-11-23 10:35:45.547116146 +0100
@@ -170,78 +170,42 @@ IF(MALLOC_LIB)
   INSTALL(FILES ${MALLOC_LIB} DESTINATION ${INSTALL_LIBDIR} OPTIONAL)
 ENDIF()
 
-IF(CMAKE_GENERATOR MATCHES "Makefiles")
-  # Strip maintainer mode options if necessary
-  STRING(REPLACE "${MY_C_WARNING_FLAGS}" "" CFLAGS
-"${CMAKE_C_FLAGS} ${CMAKE_C_FLAGS_RELWITHDEBINFO}")
-  STRING(REPLACE "${MY_CXX_WARNING_FLAGS}" "" CXXFLAGS
-"${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_RELWITHDEBINFO}")
-  FOREACH(ARCH ${CMAKE_OSX_ARCHITECTURES})
-SET(CFLAGS   "${CFLAGS} -arch ${ARCH}")
-SET(CXXFLAGS "${CXXFLAGS} -arch ${ARCH}")
-  ENDFOREACH()
-ELSE()
-  # Strip maintainer mode options if necessary
-  STRING(REPLACE "${MY_C_WARNING_FLAGS}" "" CFLAGS
-"${CMAKE_C_FLAGS_RELWITHDEBINFO}")
-  STRING(REPLACE "${MY_CXX_WARNING_FLAGS}" "" CXXFLAGS
-"${CMAKE_CXX_FLAGS_RELWITHDEBINFO}")
-ENDIF()
-
-# Add trailing whitespace, before substitution below.
-SET(CFLAGS "${CFLAGS} ")
-SET(CXXFLAGS "${CXXFLAGS} ")
-
-SET(REPLACE_OPTIONS
-  "-DDBUG_OFF "
-  "-DEXTRA_DEBUG "
-  "-DHAVE_VALGRIND "
-  "-DSAFE_MUTEX "
-  "-fPIC "
-  "-fno-inline "
-  "-fno-strict-aliasing "
-  "-fstack-protector-strong "
-  "-g "
-  "-grecord-gcc-switches "
-  "-ip "
-  "-mp "
-  "-pipe "
-  "-restrict "
-  "-unroll2 "
+SET(COMPILE_DEFINITIONS_WHITELIST
 )
 
-# Note sequence of -W options here, most specific first.
-SET(REPLACE_REGEX_OPTIONS
-  "-Wp,[-=_A-Za-z0-9]*"
-  "-Werror=[-A-Za-z]*"
-  "-W[-A-Za-z]*"
-  "--param=[-=a-z0-9]*"
-  "-O[0-9]"
-  "-march=[-A-Za-z0-9]*"
-  "-mcpu=[-A-Za-z0-9]*"
-  "-mtune=[-A-Za-z0-9]*"
-  "-specs=[-A-Za-z0-9/]*"
-  "-xO[0-9]"
+# In practice: only in use on Solaris
+SET(CMAKE_C_FLAGS_WHITELIST
+  "-m32"
+  "-m64"
 )
 
-FOREACH(option ${REPLACE_REGEX_OPTIONS})
-  STRING(REGEX REPLACE "${option}" "" CFLAGS   "${CFLAGS}")
-  STRING(REGEX REPLACE "${option}" "" CXXFLAGS "${CXXFLAGS}")
-ENDFOREACH()
+SET(CFLAGS "")
+SET(CXXFLAGS "")
 
-FOREACH(option ${REPLACE_OPTIONS})
-  STRING(REPLACE "${option}" " " CFLAGS   "${CFLAGS}")
-  STRING(REPLACE "${option}" " " CXXFLAGS "${CXXFLAGS}")
+GET_PROPERTY(cwd_definitions DIRECTORY PROPERTY COMPILE_DEFINITIONS)
+FOREACH(white_flag ${COMPILE_DEFINITIONS_WHITELIST})
+  FOREACH(flag ${cwd_definitions})
+IF (${flag} MATCHES ${white_flag})
+  SET(CFLAGS "-D${white_flag} ${CFLAGS}")
+  SET(CXXFLAGS "-D${white_flag} ${CXXFLAGS}")
+ENDIF()
+  ENDFOREACH()
 ENDFOREACH()
-STRING(REPLACE "-fexceptions " " " CFLAGS "${CFLAGS}")
 
-# Finally: strip away whitespace.
-STRING(REGEX REPLACE "[ ]+" " " CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "[ ]+" " " CXXFLAGS "${CXXFLAGS}")
-STRING(REGEX REPLACE "^[ ]+" "" CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "^[ ]+" "" CXXFLAGS "${CXXFLAGS}")
-STRING(REGEX REPLACE "[ ]+$" "" CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "[ ]+$" "" CXXFLAGS "${CXXFLAGS}")
+IF(CMAKE_BUILD_TYPE AND CMAKE_GENERATOR MATCHES "Makefiles")
+  STRING(TOUPPER "${CMAKE_BUILD_TYPE}" CMAKEBT)
+  SET(CMAKEBT_FLAGS "${CMAKE_C_FLAGS_${CMAKEBT}} ${CMAKE_C_FLAGS}")
+  SEPARATE_ARGUMENTS(CMAKEBT_FLAGS)
+ENDIF()
+
+FOREACH(white_flag ${CMAKE_C_FLAGS_WHITELIST})
+  FOREACH(flag ${CMAKEBT_FLAGS})
+IF (${flag} STREQUAL ${white_flag})
+  SET(CFLAGS "${white_flag} ${CFLAGS}")
+  SET(CXXFLAGS "${white_flag} ${CXXFLAGS}")
+ENDIF()
+  ENDFOREACH()
+ENDFOREACH()
 
 IF(UNIX)
   # FIND_PROC and CHECK_PID are used by mysqld_safe
@@ -387,6 +351,16 @@ IF(QUOTED_CMAKE_CXX_LINK_FLAGS)
   SET(CONFIG_EMBEDD_LIBS "${CONFIG_EMBEDD_LIBS} ${QUOTED_CMAKE_CXX_LINK_FLAGS}")
 ENDIF()
 
+SET(CONFIG_LIBS_PRIVATE "${CLIENT_LIBS}")
+SET(CONFIG_REQUIRES_PRIVATE "")
+# ssl.cmake should have used pkg-config rather than cmake to locate ssl
+IF (WITH_SSL STREQUAL "system")
+  SET(CONFIG_REQUIRES_PRIVATE "openssl")
+  STRING(REPLACE "-lssl" "" CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+  STRING(REPLACE "-lcrypto" "" CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+  STRING(REGEX REPLACE "[ ]+" " " CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+ENDIF()
+
 SET(LIBMYSQLD_LIBS_USAGE "
 --libmysqld-libs [$embedded_libs]")
 SET(DISABLE_EMBEDDED_SH "")
diff -rup a/scripts/mysqlclient.pc.in b/scripts/mysqlclient.pc.in
--- a/scripts/mysqlclient.pc.in	2016-09-28 19:02:44.0 +0200
+++ b/scripts/mysqlclient.pc.in	2016-11-23 10:29:27.372897342 +0100
@@ -1,4 +1,4 @@
-# Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2015, 2016, Oracle and/or its affiliates. All rights reserved.
 #
 # This

Bug#845379: marked as done (node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 10:19:21 +
with message-id 
and subject line Bug#845379: fixed in node-fuzzaldrin-plus 
0.3.1+git.20161008.da2cb58+dfsg-2
has caused the Debian Bug report #845379,
regarding node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not 
found.
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.)


-- 
845379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-fuzzaldrin-plus
Version: 0.3.1+git.20161008.da2cb58+dfsg-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-fuzzaldrin-plus fails to build from source in unstable/amd64:

  […]
 debian/rules override_dh_auto_clean
  make[1]: Entering directory '«BUILDDIR»'
  dh_auto_clean
  grunt clean
  >> Local Npm module "grunt-contrib-coffee" not found. Is it 
installed?
  >> Local Npm module "grunt-shell" not found. Is it installed?
  >> Local Npm module "grunt-browserify" not found. Is it installed?
  >> Local Npm module "grunt-contrib-uglify" not found. Is it 
installed?
  
  Running "clean" task
  
  Done.
  rm -rf dist-browser
  make[1]: Leaving directory '«BUILDDIR»'
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory '«BUILDDIR»'
  dh_auto_build
  grunt
  >> Local Npm module "grunt-contrib-coffee" not found. Is it 
installed?
  >> Local Npm module "grunt-shell" not found. Is it installed?
  >> Local Npm module "grunt-browserify" not found. Is it installed?
  >> Local Npm module "grunt-contrib-uglify" not found. Is it 
installed?
  Warning: Task "coffee" not found. Use --force to continue.
  
  Aborted due to warnings.
  debian/rules:11: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 3
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


node-fuzzaldrin-plus.0.3.1+git.20161008.da2cb58+dfsg-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: node-fuzzaldrin-plus
Source-Version: 0.3.1+git.20161008.da2cb58+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-fuzzaldrin-plus 
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, 23 Nov 2016 14:59:04 +0530
Source: node-fuzzaldrin-plus
Binary: node-fuzzaldrin-plus libjs-fuzzaldrin-plus
Architecture: source all
Version: 0.3.1+git.20161008.da2cb58+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 libjs-fuzzaldrin-plus - fuzzy search / highlight for programmer's text editor 
(browser)
 node-fuzzaldrin-plus - Fuzzy filtering and string scoring - compatible with 
fuzzaldrin
Closes: 845379
Changes:
 node-fuzzaldrin-plus (0.3.1+git.20161008.da2cb58+dfsg-2) unstable; 
urgency=medium
 .
   * Add node-grunt-contrib-coffee to build deps (Closes: #845379)
Checksums-Sha1:
 2b94896b7e2301e76e72eadb5494c893758a65a8 2413 
node-fuzzaldrin-plus_0.3.1+git.20161008.da2cb58+dfsg-2.dsc
 48283f54d37a1dc54e84bf84994c9404c45cbe12 2904 
node-fuzzaldrin-plus_0.3.1+git.20161008.da2cb58+dfsg-2.debian.tar.xz
 797812d1bc9df8454be5db218d71f1e200a05b52 7040 
libjs-fuzzaldrin-plus_0.3.1+git.20161008.da2cb58+dfsg-2_all.deb
 f68e95b769c02751ec45d692c75247da3789c05a 21170 
node-fuzzaldrin-plus_0.3.1+git.20161008.da2cb58+dfsg-2_all.deb
Ch

Processed: Only a problem for stretch+sid

[Debian Bug Tracking System]

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

> tags 843491 stretch sid
Bug #843491 [src:witty] witty: Depends on libmysqlclient18 which is no longer 
available
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + help moreinfo
Bug #845171 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Added tag(s) moreinfo.

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

Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Matthias Klose]

Control: tags -1 + help moreinfo

according to the logs, -Wl,--enable-new-dtags is already passed into the linker,
so I don't assume the defaults change in binutils is the root cause.

I'm unable to trigger the malloc error.  If you can, please run gcc with -v, and
then re-run the collect2/ld command and provide the object files and libraries
for the link.

Bug#844139: marked as done (python-django: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 10:34:07 +
with message-id 
and subject line Bug#844139: fixed in python-django 1:1.10.3-2
has caused the Debian Bug report #844139,
regarding python-django: FTBFS: Tests failures
to be marked as done.

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

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


-- 
844139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.10.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2016 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):
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/11/python-django_1.10.3-1_unstable.log

This failure happens on a CPU with TSX extensions available, but is not
reproducible on a machine without them. For context, I recommend reading the
thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html

The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
   model: 79
   model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
   stepping : 1

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: python-django
Source-Version: 1:1.10.3-2

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated python-django 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, 23 Nov 2016 10:45:50 +0100
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Architecture: source
Version: 1:1.10.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Raphaël Hertzog 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 844139
Changes:
 python-django (1:1.10.3-2) unstable; urgency=medium
 .
   * Add patch to fix tests running in parallel. Closes: #844139
   * Update copyright file (and drop new extra LICENSE.txt).
   * Adjust lintian overrides.
Checksums-Sha1:
 b0af752b91b116b0e0db532be36d871a96d0505c 2466 python-django_1.10.3-2.dsc
 5cc86a991dc283540bdc77c42f456a52475b9d15 30124 
python-django_1.10.3-2.debian.tar.xz
Checksums-Sha256:
 05ef05e93af9bf3c6dbfb36cd2548d3384c8bd1d9c8eff29d73c380d205d32e0 2466 
python-django_1.10.3-2.dsc
 6ff92dec7273f2418fd25ae11d

Processed: severity of 845423 is grave

[Debian Bug Tracking System]

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

> severity 845423 grave
Bug #845423 {Done: Gianfranco Costamagna } 
[virtualbox-ext-pack] virtualbox-ext-pack: hash mismatch 
Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: FTBFS with GCC 6: with patches

[Debian Bug Tracking System]

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

> tags 811593 patch
Bug #811593 [libgetopt++] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) patch.
> tags 811618 patch
Bug #811618 [dsc-statistics] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.
> tags 811740 patch
Bug #811740 [nautic] nautic: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.
> tags 811825 patch
Bug #811825 [ppl] ppl: FTBFS with GCC 6: no match for
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#841612: libmodpbase64-dev: modp_stdint.h is missing

[Lennart Weller]

The modp_stdint.h is not installed on non-Windows systems. It just defines some 
standard storage names also available in stdint.h. Including it in the install 
seems nonsensical.

Bug#817356: marked as done (aspell-el: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 11:33:21 +
with message-id 
and subject line Bug#817356: fixed in aspell-el 0.50-3-6.1
has caused the Debian Bug report #817356,
regarding aspell-el: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: aspell-el
Source-Version: 0.50-3-6.1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated aspell-el 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, 23 Nov 2016 12:06:36 +0100
Source: aspell-el
Binary: aspell-el
Architecture: source
Version: 0.50-3-6.1
Distribution: unstable
Urgency: medium
Maintainer: Brian Nelson 
Changed-By: Dr. Tobias Quathamer 
Description:
 aspell-el  - Greek dictionary for GNU Aspell
Closes: 817356
Changes:
 aspell-el (0.50-3-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use debhelper v10. (Closes: #817356)
Checksums-Sha1:
 e1d8aa3e84b5633cdd5c9286cd225d612a7d324f 1678 aspell-el_0.50-3-6.1.dsc
 7d23b88d07ec404141283e9cd81f595a3a1c8ed1 1800 aspell-el_0.50-3-6.1.diff.gz
Checksums-Sha256:
 af871639c269847dbe1036cb0076f1ba201a5624ade36a58099a603170dec013 1678 
aspell-el_0.50-3-6.1.dsc
 430d2b0bfce273e77c9d353a915368fb1f1299c20b014456137d0d1b7bdab6fb 1800 
aspell-el_0.50-3-6.1.diff.gz
Files:
 18d7cf78a2e794df70ae34713402008c 1678 text optional aspell-el_0.50-3-6.1.dsc
 47ff076c599d28bcfea1496da0320f88 1800 text optional 
aspell-el_0.50-3-6.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYNXiyAAoJEBMC8fA26+sZa5gQAJ0DSGCzubcsAuYwvI+7Ksdd
LOubzAvVbkeVqIqGJD6NkOoTroyXnTnWrHHToHmE6sDUIcKqPB33omK2lWsB1p8G
GVmnOBTO/HCkHbzoqdS20sQ1Xa97eqXh4rBE5dtLPjRdGZ1Ghh8XJf/7V7Z8NJ0v
hmEWi14Go9tgZF2WsSmeBywWoQUjIbhQyi7a/pIaV/AtzBMuIaqXODwGPn4GLsrq
SczRwR0AisXdCRU4shH3HzvWjW/168igi4QydWAXhkS/8EPjh2qxHngM0y7KoXkn
c8zYER3oq2ls0PUOHTCESiCbh6iZv+111X87Pe/XkQiX8kjL3TysNb5Euys+vzfr
4PDdVD4FuH2DMQPN/+8DqiPW61yEAS/pVorn1RO9TlCqdpV5FQXNg6Fk5wYOZOQX
3RMKfzkc81yfPBvYHhGnNcSTfQ48KY4rnQ2JeUkcyDFN9KjJFEFUND+pfErXYeLF
7c7bxJLPYAjUXB8To6FygLZhGHJ+yn+PvEn/mYsvsJqI24lBbrGaxpicy3oa9cHO
ZuCxHYcJOElxoVgh6wR7TdaHR/Ho/M6SBrs8+C/oOcBD3ayCzLghms9F1bCQOTWg
+9LIYZvcVAm/MDidv/RsD7a/O4IH2vy63uKSyNR64ZEACG4RVI6hR5DbGECPFaeR
qzBJerp963p41TwS9XxQ
=68nW
-END PGP SIGNATURE End Message ---

Processed (with 1 error): reassign 841612 to aseprite/1.1.6+ds-1, retitle 841612 to aseprite: FTBFS: modp_stdint.h is missing

[Debian Bug Tracking System]

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

> reassign 841612 aseprite/1.1.6+ds-1
Unknown command or malformed arguments to command.
> retitle 841612 aseprite: FTBFS: modp_stdint.h is missing
Bug #841612 [libmodpbase64-dev] libmodpbase64-dev: modp_stdint.h is missing
Changed Bug title to 'aseprite: FTBFS: modp_stdint.h is missing' from 
'libmodpbase64-dev: modp_stdint.h is missing'.
> thanks
Stopping processing here.

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

Processed: reassign 841612 to src:aseprite

[Debian Bug Tracking System]

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

> reassign 841612 src:aseprite
Bug #841612 [libmodpbase64-dev] aseprite: FTBFS: modp_stdint.h is missing
Bug reassigned from package 'libmodpbase64-dev' to 'src:aseprite'.
Ignoring request to alter found versions of bug #841612 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841612 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#844081: [Python-apps-team] Bug#844081: Which FS was this run on?

[Filip Pytloun]

Hello,

I am using ZFS and building in pbuilder chroot and wasn't able to reproduce it
this way.

This may be also related to caching of underlying host as reporter is running
the build in VM - having more info about environment may help to find
reproducer.

Filip

On 2016/11/21 15:52, Christian Geier wrote:
> Hi,
> what filesystem did you run this on?
> 
> The issue here is, that mtimes that should change, didn't (at least not
> as far as python is concerned), event though there is a sleep(0.01)
> (which does not *have* to be accurate, but usually is a bit larger)
> between reading the mtime, modifying the data and re-reading the mtime .
> 
> Best regards,
> Christian Geier
> 
> ___
> Python-apps-team mailing list
> python-apps-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team
> 


signature.asc
Description: Digital signature

Bug#843543: [Pkg-tigervnc-devel] Bug#843543: Bug#843543: tigervnc: FTBFS with xserver 1.19

[Ola Lundqvist]

Hi

Thank you for the information. Now we just have to fix it. :-)

// Ola

On 22 November 2016 at 23:57, Emilio Pozuelo Monfort 
wrote:

> Control: severity -1 serious
>
> On 08/11/16 22:04, Emilio Pozuelo Monfort wrote:
> > On 07/11/16 17:40, Ben Hildred wrote:
> >>
> >>
> >> On Mon, Nov 7, 2016 at 9:13 AM, Emilio Pozuelo Monfort <
> po...@debian.org
> >> > wrote:
> >>
> >> Source: tigervnc
> >> Version: 1.6.0+dfsg-4
> >> Severity: important
> >>
> >> Hi,
> >>
> >> I rebuilt your package against xserver 1.19 (2:1.18.99.901-1 to be
> precise,
> >> note we have 2:1.18.99.902-1 in experimental now) and it failed to
> build,
> >> particularly it failed to apply the patches to the new xserver:
> >>
> >> Hunk #1 succeeded at 161 with fuzz 2 (offset 36 lines).
> >> Hunk #2 FAILED at 153.
> >> Hunk #3 FAILED at 215.
> >> Hunk #4 FAILED at 226.
> >> 3 out of 4 hunks FAILED -- saving rejects to file os/WaitFor.c.rej
> >> debian/rules:126: recipe for target
> >> 'unix/xserver/.apply-patches-vnc-patch-xorg.stamp' failed
> >>
> >> (full log attached)
> >>
> >> I see there is a new upstream release, so it may be good to look at
> that
> >> for xserver 1.19 compatibility.
> >>
> >> I have seen a fix for this in the upstream change history. I cannot
> remember if
> >>   it made it into 1.7 or not from the top of my head.
> >
> > I saw some patches in upstream github too[1]. IIRC they were not in the
> last
> > release, but they can probably be backported?
> >
> > [1]
> > https://github.com/TigerVNC/tigervnc/commit/
> 3fed95eda27dfbeee6535f987f5d14a66f64749b
>
> I just uploaded xserver 1.19 to sid, so this is RC.
>
> Cheers,
> Emilio
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 844081 normal
Bug #844081 [src:khal] khal: FTBFS randomly (test_default_calendar fails)
Severity set to 'normal' from 'serious'
> tags 844081 + moreinfo upstream
Bug #844081 [src:khal] khal: FTBFS randomly (test_default_calendar fails)
Added tag(s) moreinfo and upstream.
> thanks
Stopping processing here.

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

Processed: fix #841612 versioning

[Debian Bug Tracking System]

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

> found 841612 1.1.6+ds-1
Bug #841612 [src:aseprite] aseprite: FTBFS: modp_stdint.h is missing
Marked as found in versions aseprite/1.1.6+ds-1.
> affects 841612 - src:aseprite
Bug #841612 [src:aseprite] aseprite: FTBFS: modp_stdint.h is missing
Removed indication that 841612 affects src:aseprite
> thanks
Stopping processing here.

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

Bug#835738: marked as done (kdepim: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 13:46:36 +0100
with message-id <6669597.HEFUF4MgfM@tuxin>
and subject line Re: Bug#835738: kdepim: FTBFS: dh_install: missing files, 
aborting
has caused the Debian Bug report #835738,
regarding kdepim: FTBFS: dh_install: missing files, aborting
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.)


-- 
835738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kdepim
Version: 4:16.04.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/etc/xdg/kdepim.categories
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkmailprivate.so.5.2.3
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkmailprivate.so.5
> -- Installing: /<>/debian/tmp/usr/bin/kmail
> -- Set runtime path of "/<>/debian/tmp/usr/bin/kmail" to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kmail.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/kmail_view.desktop
> -- Installing: /<>/debian/tmp/usr/share/config.kcfg/kmail.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kmail.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_misc.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_appearance.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_identity.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_accounts.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_composer.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_security.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmcomposerui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmmainwin.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmreadermainwin.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmail_part.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/knotifications5/kmail2.notifyrc
> -- Installing: 
> /<>/debian/tmp/usr/share/kservicetypes5/dbusmail.desktop
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmail.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmail.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/interfaces/org.kde.kmail.kmailpart.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/interfaces/org.kde.kmail.kmail.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/ServiceMenus/kmail_addattachmentservicemenu.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/messageviewer/about/default/introduction_kmail.html
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-thread-ignored.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-thread-watch.png
> -- Installing: /<>/debian/tmp/usr/share/kmail2/pics/pgp-keys.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-deleted.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kcm_kpimidentities.desktop
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kpimidentities.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kontact_kmailplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmailsummary.so
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kontact

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

[PICCA Frederic-Emmanuel]

Hello Luca

> This is very unfortunate, but as explained on the mailing list, this
> behaviour was an unintentional internal side effect. I didn't quite
> realise it was there, and so most other devs.

I understand, I just wanted to point that the synchrotron community invest a 
lot of efforts in order
to provide a tango stack into Debian Stretch.

(tango -> pytango -> spyder -> taurus -> hkl -> sardana)

It would a big fail for use if Debian stretch were released without tango.


> How much work would it be to change tango to avoid relying on aligned
> internal recv buffers?


I spoke with the tango upstream, and they told me that this change is not that 
trivial.
This is unfortunate that it is so late in the release cycle of Debian.
I think that they will not have the time to do this change before the 5 febuary.

I will keep you informed if something moves from their part.

BUT I beg the zeromq3 maintainer to stick with 4.1.5 for Stetch.

Thanks a lot for considering

Frederic

Processed: Bug#845361 marked as pending

[Debian Bug Tracking System]

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

> tag 845361 pending
Bug #845361 [src:gmerlin-avdecoder] gmerlin-avdecoder: removal of 
libschroedinger
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#845361: marked as pending

[IOhannes m zmölnig]

tag 845361 pending
thanks

Hello,

Bug #845361 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://git.debian.org/?p=pkg-multimedia/gmerlin-avdecoder.git;a=commitdiff;h=80fc9ac

---
commit 80fc9ac1317370a8f26838ffb696bc83aad6264c
Author: IOhannes m zmölnig 
Date:   Wed Nov 23 15:23:51 2016 +0100

Ready for upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index e25de93..63144ee 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+gmerlin-avdecoder (1.2.0~dfsg-8) unstable; urgency=medium
+
+  * Don't B-D on libschroedinger.
+Thanks to Andreas Cadhalpun 
+(Closes: #845361)
+  * Multi-arch hint for libgmerlin-avdec-doc
+  * Fixed references in doc-base
+  * Normalized Vcs-Browser stanza
+
+ -- IOhannes m zmölnig (Debian/GNU)   Wed, 23 Nov 2016 
15:23:25 +0100
+
 gmerlin-avdecoder (1.2.0~dfsg-7) unstable; urgency=medium
 
   * Dropped B-D on libopenjpeg (Closes: #826813)

Bug#845171: ld regression handling $ORIGIN in rpath

[Matthias Klose]

Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=20858
Control: tags -1 + upstream

This looks like another regression with handling $ORIGIN in the linker
(-rpath=\$ORIGIN/<...>).  The work around for the packages is to remove that
option, you don't need to relocate the binaries when shipped as a debian 
package.

Cloning the bugs for the original packages ...

Processed: ld regression handling $ORIGIN in rpath

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=20858
Bug #845171 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=20858'.
> tags -1 + upstream
Bug #845171 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Added tag(s) upstream.

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

Processed: Re: Bug#835811 closed by Dimitri John Ledkov (Bug#835811: fixed in libica 2.6.1-4)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #835811 {Done: Dimitri John Ledkov } [src:libica] libica: 
FTBFS with openssl 1.1.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libica/2.6.1-4.
> severity -1 important
Bug #835811 [src:libica] libica: FTBFS with openssl 1.1.0
Severity set to 'important' from 'serious'

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

Bug#835811: closed by Dimitri John Ledkov (Bug#835811: fixed in libica 2.6.1-4)

[Sebastian Andrzej Siewior]

control: reopen -1
control: severity -1 important

On 2016-11-22 17:06:05 [+], Debian Bug Tracking System wrote:
>* Build-depend on libssl1.0-dev, upgrade to 1.1 requires v3.0 upstream
>  release. Closes: #835811

please keep this bug open and close once it builds against openssl
1.1.0. If you choose to stay with 1.0.2 please lower the severity to
important and you may unblock the transition bug.

Sebastian

Bug#828329: [Pkg-gridengine-devel] Bug#828329: Bug#828329: forwarded to https://arc.liv.ac.uk/trac/SGE/ticket/1572

[Dave Love]

Afif Elghraoui  writes:

> Many thanks for working on this. I'd like to see what Dave says
> upstream. Otherwise, I'd rather stick with 1.0 if possible.

That's probably wise if you can.  I don't know when I'll be able to test
the change sensibly.

> I need to
> ask the release team if that's ok. So far, I've just been monitoring the
> transition hubbub on -devel to see what's going to happen.

Bug#845453: golang-github-googleapis-proto-client-go: FTBFS: logging.pb.go:216: undefined: grpc.SupportPackageIsVersion3

[Chris Lamb]

Source: golang-github-googleapis-proto-client-go
Version: 0.0~git20160726.0.e5790fe-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

golang-github-googleapis-proto-client-go fails to build from source in 
unstable/amd64:

  […]
 dh_auto_build -O--buildsystem=golang
go install -v -p 1 github.com/googleapis/proto-client-go/api 
github.com/googleapis/proto-client-go/logging/type_ 
github.com/googleapis/proto-client-go/logging/v2 
github.com/googleapis/proto-client-go/rpc
  github.com/golang/protobuf/proto
  github.com/googleapis/proto-client-go/api
  github.com/googleapis/proto-client-go/logging/type_
  github.com/golang/protobuf/ptypes/any
  github.com/golang/protobuf/ptypes/empty
  github.com/golang/protobuf/ptypes/struct
  github.com/golang/protobuf/ptypes/timestamp
  github.com/googleapis/proto-client-go/rpc
  golang.org/x/net/context
  golang.org/x/net/http2/hpack
  golang.org/x/net/idna
  golang.org/x/net/lex/httplex
  golang.org/x/net/http2
  golang.org/x/net/internal/timeseries
  golang.org/x/net/trace
  google.golang.org/grpc/codes
  google.golang.org/grpc/credentials
  google.golang.org/grpc/grpclog
  google.golang.org/grpc/internal
  google.golang.org/grpc/metadata
  google.golang.org/grpc/naming
  google.golang.org/grpc/peer
  google.golang.org/grpc/transport
  google.golang.org/grpc
  github.com/googleapis/proto-client-go/logging/v2
  # github.com/googleapis/proto-client-go/logging/v2
  src/github.com/googleapis/proto-client-go/logging/v2/logging.pb.go:216: 
undefined: grpc.SupportPackageIsVersion3
  
src/github.com/googleapis/proto-client-go/logging/v2/logging_config.pb.go:223: 
undefined: grpc.SupportPackageIsVersion3
  
src/github.com/googleapis/proto-client-go/logging/v2/logging_metrics.pb.go:183: 
undefined: grpc.SupportPackageIsVersion3
  dh_auto_build: go install -v -p 1 github.com/googleapis/proto-client-go/api 
github.com/googleapis/proto-client-go/logging/type_ 
github.com/googleapis/proto-client-go/logging/v2 
github.com/googleapis/proto-client-go/rpc returned exit code 2
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


golang-github-googleapis-proto-client-go.0.0~git20160726.0.e5790fe-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844797: marked as done (cabal-debian: FTBFS: build-dependency not installable: libghc-debian-doc)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 17:27:00 +0200
with message-id <20161123152700.m6whwlhnyjxnf...@gmail.com>
and subject line Re: Bug#844797: cabal-debian: FTBFS: build-dependency not 
installable: libghc-debian-doc
has caused the Debian Bug report #844797,
regarding cabal-debian: FTBFS: build-dependency not installable: 
libghc-debian-doc
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.)


-- 
844797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cabal-debian
Version: 4.33-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-do

Processed: limit source to postgresql-common, tagging 838812

[Debian Bug Tracking System]

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

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

> tags 838812 + pending
Bug #838812 [postgresql-common] pg_upgradecluster skips databases owned by a 
role who is not a user
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#733846: marked as done (pidgin: crash on startup: illegal hardware instruction / invalid opcode)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 17:59:42 +0200
with message-id <20161123155942.fso6zohoiev5v...@bunk.spdns.de>
and subject line Bug does not seem to be present in buzztrax
has caused the Debian Bug report #733846,
regarding pidgin: crash on startup: illegal hardware instruction / invalid 
opcode
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.)


-- 
733846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pidgin
Version: 2.10.7-2+b1
Severity: grave
Justification: renders package unusable

Hi,

Since my last dist-upgrade two days ago I'm not able to start pidgin
anymore, the console returns the following:

---
$ pidgin
zsh: illegal hardware instruction  pidgin
---

And dmesg says:
---
[31793.953373] traps: pidgin[21225] trap invalid opcode ip:7fab94540348 
sp:7fff3bbb8260 error:0 in libbuzztard-core.so.0.6.0[7fab94511000+59000]
---

Cheers, Linus


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

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

Versions of packages pidgin depends on:
ii  gconf2  3.2.6-1
ii  libatk1.0-0 2.10.0-2
ii  libc6   2.17-97
ii  libcairo2   1.12.16-2
ii  libdbus-1-3 1.6.18-2
ii  libdbus-glib-1-20.100.2-1
ii  libfontconfig1  2.11.0-2
ii  libfreetype62.5.2-1
ii  libgdk-pixbuf2.0-0  2.28.2-1+b1
ii  libglib2.0-02.36.4-1
ii  libgstreamer0.10-0  0.10.36-1.2
ii  libgtk2.0-0 2.24.22-1
ii  libgtkspell02.0.16-1
ii  libice6 2:1.0.8-2
ii  libpango-1.0-0  1.36.0-1+b1
ii  libpangocairo-1.0-0 1.36.0-1+b1
ii  libpangoft2-1.0-0   1.36.0-1+b1
ii  libpurple0  2.10.7-2+b1
ii  libsm6  2:1.2.1-2
ii  libx11-62:1.6.2-1
ii  libxml2 2.9.1+dfsg1-3
ii  libxss1 1:1.2.2-1
ii  perl-base [perlapi-5.18.1]  5.18.1-5
ii  pidgin-data 2.10.7-2

Versions of packages pidgin recommends:
ii  gstreamer0.10-plugins-base  0.10.36-1.1
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu2

Versions of packages pidgin suggests:
ii  libsqlite3-0  3.8.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
libbuzztard0 was removed from Debian, and I am not able to reproduce 
this problem with the successor buzztrax.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 844285 2.10.11-1
Bug #844285 [pidgin] pidgin: steals (warps) mouse cursor (not just focus) when 
new message comes in [SEC=UNCLASSIFIED]
Marked as found in versions pidgin/2.10.11-1.
> thanks
Stopping processing here.

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 789955 38.1.0esr-2
Bug #789955 [iceweasel] devscripts: [bts] "bts show" command displays error: 
(process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Bug #798988 [iceweasel] g_slice_set_config: assertion 'sys_page_size == 0' 
failed
Marked as found in versions iceweasel/38.1.0esr-2.
Marked as found in versions iceweasel/38.1.0esr-2.
> thanks
Stopping processing here.

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

Bug#843025: marked as done (metview: doesn't need to depend on zsh or ksh-variant shells)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 16:19:43 +
with message-id 
and subject line Bug#843025: fixed in metview 4.7.2-3
has caused the Debian Bug report #843025,
regarding metview: doesn't need to depend on zsh or ksh-variant shells
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.)


-- 
843025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: metview
Version: 4.7.0-1
Severity: normal

Dear Maintainer,

While this package depends on ksh | mksh | pdksh | zsh it seems to use
bash and any posix compliant shell, always provided by any sane debian
system.

$ dpkg -L metview | xargs  file | grep script
/usr/bin/metview:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/MarsOdbWrapper:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/MarsTiggeWrapper:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/compile:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/document_macros.pl:Perl script 
text executable
/usr/lib/x86_64-linux-gnu/metview/dump:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/generate_video:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/logrun:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/metview-mail:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/metview_create_user_dir:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/metview_help:  POSIX shell 
script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/metview_post_install_tests.sh: POSIX shell 
script, ASCII text executable, with very long lines
/usr/lib/x86_64-linux-gnu/metview/mv_compress:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_flexpart_run:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_flextra_prep:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_flextra_prep.mv:a 
/usr/bin/metview script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_flextra_run:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_grib_dump:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_mail:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_mars_catalog.py:Python script, 
ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_obstat: Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_odbsql: Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_rttov_run:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_scm_run:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_scm_vis.mv: a 
/usr/bin/metview  script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_uniquename: Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_vapor_gui:  Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mv_vapor_prep.mv:  a 
/usr/bin/magml script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mvrun: Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mvrun_c:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mvrun_lnx: Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/mvusage:   Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/select_mars_config:Bourne-Again 
shell script, ASCII text executable
/usr/lib/x86_64-linux-gnu/metview/set_mars_env:  Bourne-Again 
shell script, ASCII text executable


Please consider droppi

Bug#841609: marked as done (armory: FTBFS: eccrypto.h:19:18: fatal error: hmqv.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 21:30:30 +0500
with message-id <20161123163030.jgkfnnztrn3dh...@belkar.wrar.name>
and subject line 
has caused the Debian Bug report #841609,
regarding armory: FTBFS: eccrypto.h:19:18: fatal error: hmqv.h: No such file or 
directory
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.)


-- 
841609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: armory
Version: 0.92.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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++ -Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/cryptopp 
> -I/usr/include/leveldb -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -O2 -pipe -fPIC 
> -c EncryptionUtils.cpp
> In file included from EncryptionUtils.h:67:0,
>  from EncryptionUtils.cpp:8:
> /usr/include/cryptopp/eccrypto.h:19:18: fatal error: hmqv.h: No such file or 
> directory
>  #include "hmqv.h"
>   ^
> compilation terminated.
> Makefile:53: recipe for target 'EncryptionUtils.o' failed
> make[2]: *** [EncryptionUtils.o] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/armory_0.92.3-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
This was a bug in libcrypto++, #841443

-- 
WBR, wRAR


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

Bug#845458: python-protobix: FTBFS: error: Could not find suitable distribution for Requirement.parse('simplejson')

[Chris Lamb]

Source: python-protobix
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

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

  […]

 dh_auto_test -O--buildsystem=pybuild
  dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
  I: pybuild base:184: python2.7 setup.py test 
  running test
  Searching for simplejson
  
  Note: Bypassing https://pypi.python.org/simple/simplejson/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).
  
  Couldn't find index page for 'simplejson' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  
  Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  No local packages or working download links found for simplejson
  error: Could not find suitable distribution for 
Requirement.parse('simplejson')
  E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  […]

The full build log is attached.


Regards,

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


python-protobix.1.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844983: marked as done (zygrib: FTBFS: dpkg-buildpackage: error: dpkg-source -b zygrib-7.0.0 gave error exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 16:35:40 +
with message-id 
and subject line Bug#844983: fixed in zygrib 8.0.1-1
has caused the Debian Bug report #844983,
regarding zygrib: FTBFS: dpkg-buildpackage: error: dpkg-source -b zygrib-7.0.0 
gave error exit status 2
to be marked as done.

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

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


-- 
844983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zygrib
Version: 7.0.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>/src'
> rm -f objs/moc_PositionEditorWidget.cpp objs/moc_ColorEditorWidget.cpp 
> objs/moc_LineEditorWidget.cpp objs/moc_TextStyleEditorWidget.cpp 
> objs/moc_AngleConverterWidget.cpp objs/moc_AngleConverterDialog.cpp 
> objs/moc_CurveDrawer.cpp objs/moc_BoardPanel.cpp 
> objs/moc_ColorScaleWidget.cpp objs/moc_DataQString.cpp 
> objs/moc_DateChooser.cpp objs/moc_DialogBoxColumn.cpp 
> objs/moc_DialogFonts.cpp objs/moc_DialogGraphicsParams.cpp 
> objs/moc_DialogLoadGRIB.cpp objs/moc_DialogLoadIAC.cpp 
> objs/moc_DialogLoadMBLUE.cpp objs/moc_DialogProxy.cpp 
> objs/moc_DialogSelectMetar.cpp objs/moc_DialogServerStatus.cpp 
> objs/moc_DialogUnits.cpp objs/moc_FileLoaderGRIB.cpp 
> objs/moc_FileLoaderIAC.cpp objs/moc_FileLoaderMBLUE.cpp 
> objs/moc_GribAnimator.cpp objs/moc_ImageWriter.cpp 
> objs/moc_LongTaskProgress.cpp objs/moc_Metar.cpp objs/moc_MeteoTable.cpp 
> objs/moc_MeteoTableWidget.cpp objs/moc_MeteotableOptionsDialog.cpp 
> objs/moc_MainWindow.cpp objs/moc_MapDrawer.cpp objs/moc_MenuBar.cpp 
> objs/moc_POI.cpp objs/moc_POI_Editor.cpp objs/moc_PositionEditor.cpp 
> objs/moc_Projection.cpp objs/moc_SkewT.cpp objs/moc_Terrain.cpp 
> objs/moc_Util.cpp
> rm -f GUI/ui_PositionEditorWidget.h GUI/ui_PoiEditorDialog.h 
> GUI/ui_ColorEditorWidget.h GUI/ui_LineEditorWidget.h 
> GUI/ui_TextStyleEditorWidget.h GUI/ui_GraphicsParamsDialog.h 
> GUI/ui_MeteotableOptionsDialog.h GUI/ui_AngleConverterWidget.h
> rm -f objs/PositionEditorWidget.o objs/ColorEditorWidget.o 
> objs/LineEditorWidget.o objs/TextStyleEditorWidget.o 
> objs/AngleConverterWidget.o objs/AngleConverterDialog.o objs/BoatSpeed.o 
> objs/CurveDrawer.o objs/CustomQwtClasses.o objs/Astro.o objs/MbzFile.o 
> objs/MblueRecord.o objs/MblueReader.o objs/MbluePlot.o objs/BoardPanel.o 
> objs/ColorScale.o objs/ColorScaleWidget.o objs/DataColors.o 
> objs/DataQString.o objs/DataMeteoAbstract.o objs/DataPointInfo.o 
> objs/DateChooser.o objs/DialogBoxColumn.o objs/DialogFonts.o 
> objs/DialogGraphicsParams.o objs/DialogLoadGRIB.o objs/DialogLoadIAC.o 
> objs/DialogLoadMBLUE.o objs/DialogProxy.o objs/DialogSelectMetar.o 
> objs/DialogServerStatus.o objs/DialogUnits.o objs/FileLoaderGRIB.o 
> objs/FileLoaderIAC.o objs/FileLoaderMBLUE.o objs/Font.o objs/GriddedPlotter.o 
> objs/GriddedReader.o objs/GriddedRecord.o objs/GshhsRangsReader.o 
> objs/GshhsReader.o objs/GribAnimator.o objs/GribPlot.o objs/GisReader.o 
> objs/GribReader.o objs/GribRecord.o objs/IacPlot.o objs/IacReader.o 
> objs/IacReaderUtil.o objs/ImageWriter.o objs/IrregularGridded.o 
> objs/IsoLine.o objs/LongTaskProgress.o objs/LonLatGrid.o objs/main.o 
> objs/MainWindow.o objs/MapDrawer.o objs/MenuBar.o objs/Metar.o 
> objs/MeteoTable.o objs/MeteoTableWidget.o objs/MeteotableOptionsDialog.o 
> objs/Orthodromie.o objs/POI.o objs/POI_Editor.o objs/PositionEditor.o 
> objs/Projection.o objs/Projection_libproj.o objs/Settings.o objs/SkewT.o 
> objs/SkewTWindow.o objs/Terrain.o objs/Therm.o objs/Util.o objs/zuFile.o 
> objs/moc_PositionEditorWidget.o objs/moc_ColorEditorWidget.o 
> objs/moc_LineEditorWidget.o objs/moc_TextStyleEditorWidget.o 
> objs/moc_AngleConverterWidget.o objs/moc_AngleConverterDialog.o 
> objs/moc_CurveDrawer.o objs/moc_BoardPanel.o objs/moc_ColorScaleWidget.o 
> objs/moc_DataQString.o objs/moc_DateChooser.o objs/moc_DialogBoxColumn.o 
> objs/moc_DialogFonts.o objs/moc_DialogGraphicsParams.o 
> objs/moc_DialogLoadGRIB.o objs/moc_DialogLoadIAC.o objs/moc_DialogLoadMBLUE.o 
> objs/moc_DialogProxy.o objs/moc_DialogSelectMetar.o 
> objs/moc_DialogServerStatus.o objs/moc_DialogUnits.o 
> objs/moc_FileLoaderGRIB.o objs/moc_FileLoaderIAC.o objs/moc_FileLoaderMBLUE.o 
> objs/moc_GribAnimator.o objs/moc_ImageWriter.o objs/moc_LongTaskProgress.o 
> objs/moc_Metar.o objs/moc_MeteoTable.o objs/moc_MeteoTableWidget.o 
> objs/moc_MeteotableO

Bug#844884: marked as done (ggcov: FTBFS: cov.C:132:48: error: invalid conversion from 'void (*)(const char*, ...)' to 'bfd_error_handler_type {aka void (*)(const char*, __va_list_tag*)}' [-fpermissiv

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 16:33:31 +
with message-id 
and subject line Bug#844884: fixed in ggcov 0.9-13
has caused the Debian Bug report #844884,
regarding ggcov: FTBFS: cov.C:132:48: error: invalid conversion from 'void 
(*)(const char*, ...)' to 'bfd_error_handler_type {aka void (*)(const char*, 
__va_list_tag*)}' [-fpermissive]
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.)


-- 
844884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ggcov
Version: 0.9-12
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread 
> -I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 
> -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 
> -I/usr/include/libxml2 -I/usr/include/libgnome-2.0 
> -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 
> -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0 
> -I/usr/include/gail-1.0 -I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libpng16 -I/usr/include/gnome-vfs-2.0 
> -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/gconf/2 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DPKGDATADIR="\"/usr/share/ggcov\"" -DPREFIX="\"/usr\"" 
> -DDATADIR="\"/usr/share\"" -DLIBDIR="\"/usr/lib/x86_64-linux-gnu\"" 
> -DSYSCONFDIR="\"/etc\"" -DDEBUG=0 -DUI_DEBUG=0 -DCOV_AMD64 -DCOV_I386   
> -Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/libiberty  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wall -Wchar-subscripts -Wsign-compare -pedantic 
> -Wno-long-long  -fno-rtti -fno-exceptions -fno-implement-inlines -c -o cov.o 
> cov.C
> cov.C:626:14: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>   fprintf(fp, "COUNT="GNB_U64_DFMT"\n", ca->count);
>   ^
> cov.C:641:17: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>  fprintf(fp, "COUNT="GNB_U64_DFMT"\n", cn->count);
>  ^
> cov.C:663:17: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>  fprintf(fp, "COUNT="GNB_U64_DFMT"\n", 
> a->count());
>  ^
> cov.C:677:17: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>  fprintf(fp, "COUNT="GNB_U64_DFMT"\n", b->count());
>  ^
> cov.C: In function 'void cov_init()':
> cov.C:132:48: error: invalid conversion from 'void (*)(const char*, ...)' to 
> 'bfd_error_handler_type {aka void (*)(const char*, __va_list_tag*)}' 
> [-fpermissive]
>  bfd_set_error_handler(cov_bfd_error_handler);
> ^
> In file included from cov_bfd.H:27:0,
>  from cov_specific.H:29,
>  from cov.C:21:
> /usr/include/bfd.h:6978:24: note:   initializing argument 1 of 'void (* 
> bfd_set_error_handler(bfd_error_handler_type))(const char*, __va_list_tag*)'
>  bfd_error_handler_type bfd_set_error_handler (bfd_error_handler_type);
> ^
> cov.C: In function 'void dump_callarcs(FILE*, list_t&)':
> cov.C:626:61: warning: format '%llu' expects argument of type 'long long 
> unsigned int', but argument 3 has type 'count_t {aka long unsigned int}' 
> [-Wformat=]
>   fprintf(fp, "COUNT="GNB_U64_DFMT"\n", ca->count);
>  ^
> cov.C: In function 'void dump_callnode(cov_callnode_t*, FILE*)':
> cov.C:641:56: warning: format '%llu' expects argument of type 'long long 
> unsigned int', but argument 3 has type 'count_t {aka long unsigned int}' 
> [-Wformat=]
>  fprintf(

Bug#845460: Symbol disappeared without soname bump

[Andrey Rahmatullin]

Package: libcrypto++6
Version: 5.6.4-3
Severity: serious
Tags: upstream
Forwarded: https://github.com/weidai11/cryptopp/issues/337


The symbol _ZN8CryptoPP7IntegerC1EPKhmNS0_10SignednessE, which is

CryptoPP::Integer::Integer(unsigned char const*, unsigned long,
CryptoPP::Integer::Signedness)

is present in libcrypto++.so.6 in 5.6.3~rc6-1 and earlier and absent in 5.6.4-1
and newer. A 4th argument, CryptoPP::ByteOrder, was added to the function which
breaks ABI in C++.



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

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

Versions of packages libcrypto++6 depends on:
ii  libc6   2.24-5
ii  libgcc1 1:6.2.1-4
ii  libstdc++6  6.2.1-4

libcrypto++6 recommends no packages.

libcrypto++6 suggests no packages.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: Re: Bug#844081: Reproducer

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #844081 [src:khal] khal: FTBFS randomly (test_default_calendar fails)
Severity set to 'serious' from 'normal'
> tags -1 -moreinfo
Bug #844081 [src:khal] khal: FTBFS randomly (test_default_calendar fails)
Removed tag(s) moreinfo.

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

Bug#844423: armory crashes on start: undefined symbol

[Andrey Rahmatullin]

On Tue, Nov 15, 2016 at 04:13:27PM +0100, chymian wrote:
> starting armory after updating today 
> 2016-11-15 15:38:01 upgrade armory:amd64 0.92.3-1+b2 0.92.3-1+b2 
> it crashes with the following error: 
> 
> 
> Traceback (most recent call last): 
> File "/usr/lib/armory/ArmoryQt.py", line 34, in  
>  import CppBlockUtils as Cpp 
> File "/usr/lib/armory/CppBlockUtils.py", line 28, in  
>_CppBlockUtils = swig_import_helper() 
> file "/usr/lib/armory/cppblockutils.py", line 24, in swig_import_helper 
>_mod = imp.load_module('_cppblockutils', fp, pathname, description) 
> importerror: /usr/lib/armory/_cppblockutils.so: undefined symbol: 
> _ZN8CryptoPP7IntegerC1EPKhmNS0_10SignednessE 
This is an ABI breakage in libcrypto++6: #845460.
A simple rebuild should fix the problem but this bug shouldn't be closed
via a binNMU, the library should be fixed instead.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#845452: Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Jens Reyer]

Control: reassign 845171 winbind/2.27.51.20161118-2
Control: affects 845171 wine-development
Control: tags 845171 - help moreinfo
Control: tags 845452 = patch


[ Referencing the other related bug here. ]

Matthias Klose wrote in https://bugs.debian.org/844847#35
> This looks like another regression with handling $ORIGIN in the
> linker (-rpath=\$ORIGIN/<...>).  The work around for the packages
> is to remove that option, you don't need to relocate the binaries
> when shipped as a debian package.

Thanks a lot! I can confirm that wine-development builds again with
attached patch, which removes the rpath $ORIGIN in configure.ac.

I'll test that a bit more and then commit for wine-development.


Matthias Klose wrote in https://bugs.debian.org/844847#35
> Cloning the bugs for the original packages ...

#845171 was still assigned to wine-development. Fixing metadata to what
I think you wanted.

Greets!
jre


--- a/configure.ac
+++ b/configure.ac
@@ -887,12 +887,12 @@ case $host_os in
   WINE_TRY_CFLAGS([-fPIC -Wl,--export-dynamic],
   [LDEXECFLAGS="-Wl,--export-dynamic"])
 
-  WINE_TRY_CFLAGS([-fPIC -Wl,--rpath,\$ORIGIN/../lib],
-  [LDRPATH_INSTALL="-Wl,--rpath,\\\$\$ORIGIN/\`\$(MAKEDEP) -R \${bindir} \${libdir}\`"
-   LDRPATH_LOCAL="-Wl,--rpath,\\\$\$ORIGIN/\$(top_builddir)/libs/wine"],
-  [WINE_TRY_CFLAGS([-fPIC -Wl,-R,\$ORIGIN/../lib],
-   [LDRPATH_INSTALL="-Wl,-R,\\\$\$ORIGIN/\`\$(MAKEDEP) -R \${bindir} \${libdir}\`"
-LDRPATH_LOCAL="-Wl,-R,\\\$\$ORIGIN/\$(top_builddir)/libs/wine"])])
+  WINE_TRY_CFLAGS([-fPIC -Wl,--rpath,./lib],
+  [LDRPATH_INSTALL="-Wl,--rpath,\`\$(MAKEDEP) -R \${bindir} \${libdir}\`"
+   LDRPATH_LOCAL="-Wl,--rpath,\$(top_builddir)/libs/wine"],
+  [WINE_TRY_CFLAGS([-fPIC -Wl,-R,./lib],
+   [LDRPATH_INSTALL="-Wl,-R,\`\$(MAKEDEP) -R \${bindir} \${libdir}\`"
+LDRPATH_LOCAL="-Wl,-R,\$(top_builddir)/libs/wine"])])
 
   WINE_TRY_CFLAGS([-Wl,--enable-new-dtags],
   [LDRPATH_INSTALL="$LDRPATH_INSTALL -Wl,--enable-new-dtags"])

Processed (with 1 error): Re: Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Debian Bug Tracking System]

Processing control commands:

> reassign 845171 winbind/2.27.51.20161118-2
Unknown command or malformed arguments to command.

> affects 845171 wine-development
Bug #845171 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Added indication that 845171 affects wine-development
> tags 845171 - help moreinfo
Bug #845171 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Removed tag(s) help and moreinfo.
> tags 845452 = patch
Bug #845452 [src:wine-development] wine-development: FTBFS: ld aborts or 
segfaults
Added tag(s) patch; removed tag(s) moreinfo, help, and upstream.

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

Bug#845452: Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Matthias Klose]

On 23.11.2016 18:03, Jens Reyer wrote:
> Control: reassign 845171 winbind/2.27.51.20161118-2
> Control: affects 845171 wine-development
> Control: tags 845171 - help moreinfo
> Control: tags 845452 = patch
> 
> 
> [ Referencing the other related bug here. ]
> 
> Matthias Klose wrote in https://bugs.debian.org/844847#35
>> This looks like another regression with handling $ORIGIN in the
>> linker (-rpath=\$ORIGIN/<...>).  The work around for the packages
>> is to remove that option, you don't need to relocate the binaries
>> when shipped as a debian package.
> 
> Thanks a lot! I can confirm that wine-development builds again with
> attached patch, which removes the rpath $ORIGIN in configure.ac.
> 
> I'll test that a bit more and then commit for wine-development.
> 
> 
> Matthias Klose wrote in https://bugs.debian.org/844847#35
>> Cloning the bugs for the original packages ...
> 
> #845171 was still assigned to wine-development. Fixing metadata to what
> I think you wanted.

ta, and the fix will be in the next binutils upload too.

Bug#844503: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Emilio Pozuelo Monfort]

On Fri, 18 Nov 2016 15:22:07 +0100 Benjamin Drung
 wrote:
> tags 844503 upstream
> forwarded 844503 https://github.com/saltstack/salt/pull/37772
> thanks
> 
> Am Donnerstag, den 17.11.2016, 21:50 +0100 schrieb Sebastian Andrzej
> Siewior:
> > control: tags -1 patch
> > 
> > On 2016-11-16 12:14:43 [+0100], Filip Pytloun wrote:
> > > To reproduce the issue simply install salt-master and run salt-
> > > call:
> > > 
> > > Â Â Â Â apt-get install salt-master
> > > Â Â Â Â salt-call
> > > 
> > > Following exception will occur:
> > > 
> > > Traceback (most recent call last):
> > > Â  File "/usr/bin/salt-call", line 11, in 
> > > Â Â Â Â salt_call()
> > 
> > …
> > > Â  File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py",
> > > line 63, in _init_libcrypto
> > > Â Â Â Â libcrypto.OPENSSL_no_config()
> > > Â  File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in
> > > __getattr__
> > > Â Â Â Â func = self.__getitem__(name)
> > > Â  File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in
> > > __getitem__
> > > Â Â Â Â func = self._FuncPtr((name_or_ordinal, self))
> > > AttributeError: /lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined
> > > symbol: OPENSSL_no_config
> > 
> > the problem is that salt/rsax931.py loads the library manually and
> > expects certain symbols which are no longer available in OpenSSL
> > 1.1.0.
> > And it loads the first libcrypto it finds plus has no dependency on
> > openssl.
> 
> Instead of forcing salt to use OpenSSL 1.0, let's try to make it work
> with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1
> was quite easy. I forwarded the patch upstream to
> https://github.com/saltstack/salt/pull/37772 to get it reviewed and
> accepted.

Nice.

Do you want to wait for upstream before uploading this? It is going to block
openssl 1.1 from entering testing due to the Breaks that it got, which in turn
is blocking quite a bunch of stuff. So it'd be good to get this fixed soon.

Thanks,
Emilio

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

[GCS]

Hi Picca, Luca,

On Wed, Nov 23, 2016 at 3:25 PM, PICCA Frederic-Emmanuel
 wrote:
>> This is very unfortunate, but as explained on the mailing list, this
>> behaviour was an unintentional internal side effect. I didn't quite
>> realise it was there, and so most other devs.
>
> I understand, I just wanted to point that the synchrotron community invest a 
> lot of efforts in order
> to provide a tango stack into Debian Stretch.
 As I understand (and remember) tango uses internal structures of
zeromq. Am I right? If so, can it be rewritten in a way to be more
zeromq version independent?

> It would a big fail for use if Debian stretch were released without tango.
 I would like to keep it, even if popcon score seems to be low.

>> How much work would it be to change tango to avoid relying on aligned
>> internal recv buffers?
>
> I spoke with the tango upstream, and they told me that this change is not 
> that trivial.
> This is unfortunate that it is so late in the release cycle of Debian.
> I think that they will not have the time to do this change before the 5 
> febuary.
 But it's not the first time when they are asked not to use internal
zeromq structures - not the first time tango has problems after a
zeromq update[1].

> I will keep you informed if something moves from their part.
 Please do.

> BUT I beg the zeromq3 maintainer to stick with 4.1.5 for Stetch.
 It's a bit hard to be equitable, which hand to bite: have an old
zeromq version maybe without security support or lose tango from
Stretch. :(

Regards,
Laszlo/GCS
[1] https://bugs.debian.org/743508

Bug#845331: marked as done (xserver-xorg-video-omap: Compatibility with xserver 1.19)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 17:20:34 +
with message-id 
and subject line Bug#845331: fixed in xf86-video-omap 0.4.4-2
has caused the Debian Bug report #845331,
regarding xserver-xorg-video-omap: Compatibility with xserver 1.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.)


-- 
845331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-omap
Version: 0.4.4-1
Severity: normal
Tags: fixed-upstream patch

Dear Maintainer,

please make your package compatible with xserver 1.19. Cherry-picking
the commits [1] and [2] from upstream should be enough. There's
currently a pre-release of xserver 1.19 (2:1.18.99.902-1) in
experimental. We'll upload xserver 1.19 to unstable very soon. See
also the transition bug #843265.

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-omap/commit/?id=e2d44d7f8c50af6c4ff00479245e3b73d81f6141
[2] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-omap/commit/?id=b39262d13e036efdd9b8ebbea615dde0a1a3ca82


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: xf86-video-omap
Source-Version: 0.4.4-2

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

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

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

Debian distribution maintenance software
pp.
Sebastian Reichel  (supplier of updated xf86-video-omap 
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, 23 Nov 2016 17:09:26 +0100
Source: xf86-video-omap
Binary: xserver-xorg-video-omap
Architecture: source
Version: 0.4.4-2
Distribution: unstable
Urgency: low
Maintainer: Sebastian Reichel 
Changed-By: Sebastian Reichel 
Description:
 xserver-xorg-video-omap - X.Org X server -- OMAP display driver
Closes: 820321 845331
Changes:
 xf86-video-omap (0.4.4-2) unstable; urgency=low
 .
   * Remove staging note from package description (Closes: #820321)
   * Update Debian Standards Version to 3.9.8
   * Add upstream patches for ABI 23 support (Closes: #845331)
   * Switch to compat level 10
   * Enable bindnow hardening
Checksums-Sha1:
 87db47be2adb8a456a9943a363e6f337e1fcf376 2117 xf86-video-omap_0.4.4-2.dsc
 6ec7eb5627df1f0275f765033d276a478c3e7e27 3792 
xf86-video-omap_0.4.4-2.debian.tar.xz
Checksums-Sha256:
 e631ffec3a132839a135baece7995fa038f132e3dff730e097eed6efd1aa7536 2117 
xf86-video-omap_0.4.4-2.dsc
 3f310b53d830370d7c5510553278009498e4a552cf73f242b762146cf2afad49 3792 
xf86-video-omap_0.4.4-2.debian.tar.xz
Files:
 4a1c24281550667c823195711e1722fa 2117 x11 optional xf86-video-omap_0.4.4-2.dsc
 76aa9006c82c39cdcd4bd796a9d71de6 3792 x11 optional 
xf86-video-omap_0.4.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlg1yiEPHHNyZUBkZWJp
YW4ub3JnAAoJENju1/PIO/qa/McP+wbAZspOjjXAgyaNCsbwx+WivGb5i/KnP1ug
ArOCVHWMjQd8RwwyMR0S9e8ISCx4wdzPwyrFg63jel0NEKUm6hJMrNEDn8wJYtQQ
cINNwQQWYc/GKcOLwpVnFDiu2UkE/aYPHjlWAr2Q8AJ1XCyK097SUnOT/1zKf/wr
EfOgMKauEC/woj2JZ+1FJBsWw2Wfq2qTnx7YCTk/Fz7BjyU/r3wffAWzl7cCQG7F
ikf26vbJRaUb2kGVZ9sOrjwOTdKaUIgSYmKl4Ec9oKFbPczvjwM9yxH4kZ/EALPN
F1KXW72ClRlfMAK78AdDNRw+HU5IblxoSy3EHlc2MrxQ0HpMj2Hd0ORSPr84PCze
RGuIKHeJV7oGymnyNBxh3CkU4ziJjPiVwwy6cbR5Y8uYbATJMqbE6BUsIK+ZU73t
2ViGMZ24XIoY9QT9r4uD8bno6BaBk8exZCSQRHqrt86tgDPIlsy/UuZBkfIqZJPV
EFc38hU4B2HkIjRPQbmXncNmwS01/GuGvBZpQKNsgnQWXpDM1SvOuYQ3uZH0SB7Q
XXV9f/+uEiJxnK5zP3aPAG1WozJOX8OzcI6LuemcFdYKxBs1il2kzkcdBMh+/jwq
+Ovc07LkbVmapkWICwUrTxEmXFD2T7TMtAg11t0Bwwb2pvyeKny7c7iKkukgJzxx
F3WFZKiu
=3erl
-END PGP SIGNATURE End Message ---

Bug#841612: libmodpbase64-dev: modp_stdint.h is missing

[Adrian Bunk]

Control: reassign 841612 libmodpbase64-dev
Control: retitle 841612 libmodpbase64-dev: modp_stdint.h is missing
Control: affects 841612 src:aseprite

On Wed, Nov 23, 2016 at 11:29:14AM +, Lennart Weller wrote:
> The modp_stdint.h is not installed on non-Windows systems. It just defines 
> some standard storage names also available in stdint.h. Including it in the 
> install seems nonsensical.

It is possible that my suggested solution was not correct,
but the bug is definitely in libmodpbase64-dev.

aseprite does #include "modp_b64.h", and that header from 
libmodpbase64-dev does #include "modp_stdint.h"

Whether shipping modp_stdint.h or patching modp_b64.h is the
correct solution is for you to decide.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#841612: libmodpbase64-dev: modp_stdint.h is missing

[Debian Bug Tracking System]

Processing control commands:

> reassign 841612 libmodpbase64-dev
Bug #841612 [src:aseprite] aseprite: FTBFS: modp_stdint.h is missing
Bug reassigned from package 'src:aseprite' to 'libmodpbase64-dev'.
No longer marked as found in versions aseprite/1.1.6+ds-1.
Ignoring request to alter fixed versions of bug #841612 to the same values 
previously set
> retitle 841612 libmodpbase64-dev: modp_stdint.h is missing
Bug #841612 [libmodpbase64-dev] aseprite: FTBFS: modp_stdint.h is missing
Changed Bug title to 'libmodpbase64-dev: modp_stdint.h is missing' from 
'aseprite: FTBFS: modp_stdint.h is missing'.
> affects 841612 src:aseprite
Bug #841612 [libmodpbase64-dev] libmodpbase64-dev: modp_stdint.h is missing
Added indication that 841612 affects src:aseprite

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

Bug#841582: marked as pending

[Ghislain Antony Vaillant]

tag 841582 pending
thanks

Hello,

Bug #841582 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://git.debian.org/?p=python-modules/packages/sphinxcontrib-doxylink.git;a=commitdiff;h=3d52cbc

---
commit 3d52cbc331b4883f1652b24ef833237fca7bc22b
Author: Ghislain Antony Vaillant 
Date:   Tue Nov 22 19:34:23 2016 +

Release to unstable.

diff --git a/debian/changelog b/debian/changelog
index 5d867c0..51ca366 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+sphinxcontrib-doxylink (1.3-2) unstable; urgency=medium
+
+  * Add patch fixing FTBFS with recent versions of pyparsing.
+Thanks to Paul McGuire for the patch (Closes: #841582)
+  * Upgrade packaging to debhelper 10.
+  * Simplify the packaging testsuite.
+  * Drop superfluous Testsuite field.
+
+ -- Ghislain Antony Vaillant   Tue, 22 Nov 2016 19:33:50 
+
+
 sphinxcontrib-doxylink (1.3-1) unstable; urgency=low
 
   * Initial release. (Closes: #823581)

Bug#845452: Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Jens Reyer]

On 23.11.2016 18:06, Matthias Klose wrote:
> ta, and the fix will be in the next binutils upload too.

Great, given your recent binutils upload rate I expect that to happen
soon. So I'll probably stay lazy and avoid changing wine-development.

Processed: Bug#841582 marked as pending

[Debian Bug Tracking System]

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

> tag 841582 pending
Bug #841582 [src:sphinxcontrib-doxylink] sphinxcontrib-doxylink: FTBFS: 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841582: marked as done (sphinxcontrib-doxylink: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 17:34:42 +
with message-id 
and subject line Bug#841582: fixed in sphinxcontrib-doxylink 1.3-2
has caused the Debian Bug report #841582,
regarding sphinxcontrib-doxylink: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
841582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-doxylink
Version: 1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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 --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib
> creating /<>/.pybuild/pythonX.Y_2.7/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/tests
> copying tests/test_parser.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/tests
> creating /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/doxylink.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/parsing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> running egg_info
> writing requirements to sphinxcontrib_doxylink.egg-info/requires.txt
> writing sphinxcontrib_doxylink.egg-info/PKG-INFO
> writing namespace_packages to 
> sphinxcontrib_doxylink.egg-info/namespace_packages.txt
> writing top-level names to sphinxcontrib_doxylink.egg-info/top_level.txt
> writing dependency_links to 
> sphinxcontrib_doxylink.egg-info/dependency_links.txt
> reading manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'LICENSE'
> writing manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib
> creating /<>/.pybuild/pythonX.Y_3.5/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/tests
> copying tests/test_parser.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/tests
> creating /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/doxylink.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/parsing.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> running egg_info
> writing dependency_links to 
> sphinxcontrib_doxylink.egg-info/dependency_links.txt
> writing top-level names to sphinxcontrib_doxylink.egg-info/top_level.txt
> writing namespace_packages to 
> sphinxcontrib_doxylink.egg-info/namespace_packages.txt
> writing sphinxcontrib_doxylink.egg-info/PKG-INFO
> writing requirements to sphinxcontrib_doxylink.egg-info/requires.txt
> reading manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'LICENSE'
> writing manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> Fixing 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/test_parser.py 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/doxylink.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/__init__.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/parsing.py
> Skipping optional fixer: buffer
> Skipping optional fixer: idioms
> Skipping optional fixer: set_literal
> Skipping optional fixer: w

Processed: Problem for some users, not necessarily RC

[Debian Bug Tracking System]

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

> severity 792925 important
Bug #792925 [webalizer] webalizer: Webalizer stopped parsing squid logs (after 
1 may 2015) saying Invlid Date Format
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#844081: Reproducer

[Filip Pytloun]

On 2016/11/23 18:54, Adrian Bunk wrote:
> Control: severity -1 serious
> Control: tags -1 -moreinfo
> 
> On Sun, Nov 20, 2016 at 10:03:04AM +0100, Filip Pytloun wrote:
> >...
> > Unfortunately running tests during build is always fragile and it seems
> > that what's working in one environment may be FTBFS for anyone else :-(
> >...
> 
> Running tests during build is only fragile when the tests
> (or the code they test) are crap.
> 

I agree but still I think it's more important to pass Debian's CI and
reproducible tests than infinite number of environments that people may use.
That's the reason why lowering the priority down from serious (maybe to
important instead of normal) to avoid autoremoval. Moreover that I am not able
to reproduce the issue and therefore verify that fix or workaround will solve
it.

> If no, please at least enlarge the sleep time by a factor of 10 to 
> ensure that this won't be observed by anyone in practice.

I have done the patch but as I can't reproduce the issue, I can't verify it
will workaround it.
Santiago, can you please test build with attached patch?
From 5ae83765f03b4a05bdccbe0f88df15ac586c4ef5 Mon Sep 17 00:00:00 2001
From: Filip Pytloun 
Date: Wed, 23 Nov 2016 18:16:10 +0100
Subject: [PATCH] Raise sleep to ensure db update will get written

---
 tests/khalendar_test.py | 18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/tests/khalendar_test.py b/tests/khalendar_test.py
index fd8dcc6..560abdd 100644
--- a/tests/khalendar_test.py
+++ b/tests/khalendar_test.py
@@ -74,7 +74,7 @@ class TestCalendar(object):
 calendar, coll._local_ctag(calendar), coll._backend.get_ctag(calendar)))
 assert len(list(vdirs[cal1].list())) == 0
 assert coll._needs_update(cal1) is False
-sleep(0.01)
+sleep(0.1)
 
 vdirs[cal1].upload(item_today)
 print('upload')
@@ -327,17 +327,17 @@ def test_default_calendar(coll_vdirs):
 vdir = vdirs['foobar']
 event = coll.new_event(event_today, 'foobar')
 vdir.upload(event)
-sleep(0.01)
+sleep(0.1)
 href, etag = list(vdir.list())[0]
 assert len(list(coll.get_events_on(today))) == 0
 coll.update_db()
-sleep(0.01)
+sleep(0.1)
 assert len(list(coll.get_events_on(today))) == 1
 vdir.delete(href, etag)
-sleep(0.01)
+sleep(0.1)
 assert len(list(coll.get_events_on(today))) == 1
 coll.update_db()
-sleep(0.01)
+sleep(0.1)
 assert len(list(coll.get_events_on(today))) == 0
 
 
@@ -362,9 +362,9 @@ def test_only_update_old_event(coll_vdirs, monkeypatch):
 END:VEVENT
 """), cal1))
 
-sleep(0.01)
+sleep(0.1)
 coll.update_db()
-sleep(0.01)
+sleep(0.1)
 assert not coll._needs_update(cal1)
 
 old_update_vevent = coll._update_vevent
@@ -383,9 +383,9 @@ def test_only_update_old_event(coll_vdirs, monkeypatch):
 SUMMARY:third meeting
 END:VEVENT
 """), cal1))
-sleep(0.01)
+sleep(0.1)
 
 assert coll._needs_update(cal1)
 coll.update_db()
-sleep(0.01)
+sleep(0.1)
 assert updated_hrefs == [href_three]
-- 
2.1.4



signature.asc
Description: Digital signature

Processed: Add version information

[Debian Bug Tracking System]

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

> found 817356 0.50-3-6
Bug #817356 {Done: to...@debian.org (Dr. Tobias Quathamer)} [src:aspell-el] 
aspell-el: Removal of debhelper compat 4
Marked as found in versions aspell-el/0.50-3-6.
> thanks
Stopping processing here.

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

Processed: Re: Bug#845334: wine32: breaks xdg-open, which wants to start wine and crashes

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #845334 [wine32] wine32: breaks xdg-open, which wants to start wine and 
crashes
Severity set to 'important' from 'critical'

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

Bug#845334: wine32: breaks xdg-open, which wants to start wine and crashes

[Jens Reyer]

control: severity -1 important

Hi Vincent,

this only affects users that actually use Wine (if at all, see below).
Only then the .desktop file gets created (e.g. on running "winecfg" the
first time). Downgrading to important for now.

Funnily I can't reproduce this here. Despite having the problematic wine
entry in /home my system still uses firefox to open html files. Even
after removing and recreating the wine .desktop entries.

Therefore I also can't reproduce the specific crash.


I'm still working on understanding mime et al.:

AFAIK the .desktop files are somehow generated by winemenubuilder.

>From the .desktop files the system (not Wine itself) generates a
mimeinfo.cache file, which basically is a reverse index of them.

It seems the systemwide /usr/share/applications/mimeinfo.cache has
precendence over ~/.local/share/applications/mimeinfo.cache (here?):

$ grep htm ~/.local/share/applications/mimeinfo.cache
application/vnd.ms-htmlhelp=wine-extension-chm.desktop;
application/x-extension-htm=wine-extension-htm.desktop;
application/x-extension-html=wine-extension-html.desktop;
$ grep htm /usr/share/applications/mimeinfo.cache
application/xhtml+xml=firefox-esr.desktop;
application/xhtml_xml=chromium.desktop;
text/html=firefox-esr.desktop;chromium.desktop;
$ xdg-mime query default text/html
userapp-Firefox-1M35PY.desktop

No idea (yet) where/what this userapp-Firefox-1M35PY.desktop exactly is.


Outlook:

I think we want to keep winemenubuilder generally because that should be
used during the installation of Windows applications for creating
specific wanted file type associations.

But we want to patch out the generation of these general purpose file
type associations for e.g. *.html or (imo even more annoying) *.txt.
That might even be proposed to upstream.

Greets
jre

Bug#845412: marked as done (installation-guide: FTBFS in German pages after r70343)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 18:44:24 +0100
with message-id <20161123184424.0750719948eaa977c0ccd...@wansing-online.de>
and subject line Re: Bug#845412: installation-guide: FTBFS in German pages 
after r70343
has caused the Debian Bug report #845412,
regarding installation-guide: FTBFS in German pages after r70343
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.)


-- 
845412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: installation-guide
Severity: serious
Justification: FTBFS

Hi,

The installation guide can't be compiled from svn, see error messages
below. If my svn foo isn't too crappy, I've tracked it down to this
revision, which was supposed to add support for mips64el:
| 
| r70343 | holgerw | 2016-11-22 22:45:31 +0100 (Tue, 22 Nov 2016) | 2 lines
| 
| Update german d-i manual back to 100%
| 
| 

(Holger x-d-cc'd accordingly.)

For reference, when building amd64 for German:
| (sid-amd64-devel)kibi@wodi:~/debian-installer/manual$ ./build/buildone.sh 
amd64 de
| Info: creating temporary profiled .xml file...
| warning: failed to load external entity 
"/home/kibi/debian-installer/manual/de/hardware/supported/mips64el.xml"
| /home/kibi/debian-installer/manual/de/hardware/hardware-supported.xml:211: 
parser error : Failure to process entity supported-mips64el.xml
| &supported-mips64el.xml;
| ^
| /home/kibi/debian-installer/manual/de/hardware/hardware-supported.xml:211: 
parser error : Entity 'supported-mips64el.xml' not defined
| &supported-mips64el.xml;
| ^
| /home/kibi/debian-installer/manual/de/hardware/hardware-supported.xml:482: 
parser error : chunk is not well balanced
| 
| ^
| /home/kibi/debian-installer/manual/de/hardware/hardware.xml:15: parser error 
: Failure to process entity hardware-supported.xml
| &hardware-supported.xml;
| ^
| /home/kibi/debian-installer/manual/de/hardware/hardware.xml:15: parser error 
: Entity 'hardware-supported.xml' not defined
| &hardware-supported.xml;
| ^
| /home/kibi/debian-installer/manual/de/hardware/hardware.xml:21: parser error 
: chunk is not well balanced
| 
| ^
| build.tmp/install.de.xml:30: parser error : Failure to process entity 
hardware.xml
| &hardware.xml;
|   ^
| build.tmp/install.de.xml:30: parser error : Entity 'hardware.xml' not defined
| &hardware.xml;
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/x86.xml:4: element 
sect2: validity error : ID usb-boot already defined
|   
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/x86.xml:267: element 
sect2: validity error : ID boot-tftp already defined
|   Mit TFTP booten
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/x86.xml:489: element 
footnote: validity error : ID gtk-miniiso already defined
| mini ISO-Image
|^
| /home/kibi/debian-installer/manual/de/boot-installer/ia64.xml:332: element 
sect2: validity error : ID boot-tftp already defined
|   Booten per TFTP
|^
| /home/kibi/debian-installer/manual/de/boot-installer/mips.xml:5: element 
sect2: validity error : ID boot-tftp already defined
|   Booten per TFTP
|^
| /home/kibi/debian-installer/manual/de/boot-installer/mipsel.xml:4: element 
sect2: validity error : ID boot-tftp already defined
|   Per TFTP booten
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/powerpc.xml:142: element 
sect2: validity error : ID usb-boot already defined
|   
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/powerpc.xml:203: element 
sect2: validity error : ID boot-tftp already defined
|   Per TFTP booten
|   ^
| /home/kibi/debian-installer/manual/de/boot-installer/sparc.xml:4: element 
sect2: validity error : ID boot-tftp already defined
|   Booten per TFTP
| ^
| unable to parse build.tmp/install.de.xml


KiBi.
--- End Message ---
--- Begin Message ---
Hi,


Cyril Brulebois  wrote:
> Source: installation-guide
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> The ins

Bug#845464: debootstrap broken, rm libxtables11 1.6.0+snapshot20161117-1 from sid, at least

[Holger Levsen]

Package: itables,ftp.debian.org
Version: 1.6.0+snapshot20161117-1
Severity: serious

Currently bootstrapping sid is totally broken. I suppose/guess removing 
libxtables11 from sid will not fix things alone but is needed to fix things 
anyway:

libxtables is not build from src:iptables anymore since 
1.6.0+snapshot20161117-2, see 
https://tracker.debian.org/media/packages/i/iptables/changelog-1.6.0%2Bsnapshot20161117-4

several example debootstap logs can be found on jenkins, sadly
https://jenkins.debian.net/job/chroot-installation_sid_bootstrap/1519/console
(from just now) has not much details:

+ sudo debootstrap sid /chroots/chroot-installation-sid.trITGPs8f 
http://ftp.de.debian.org/debian
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...

I: Resolving dependencies of base packages...

I: Found additional required dependencies: libaudit-common libaudit1 libbz2-1.0 
libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 liblz4-1 
libncursesw5 libsemanage-common libsemanage1 libsystemd0 libudev1 libustr-1.0-1 
I: Found additional base dependencies: dmsetup gnupg-agent libapparmor1 
libassuan0 libbsd0 libcap2 libcryptsetup4 libdevmapper1.02.1 libdns-export162 
libelf1 libfastjson4 libffi6 libgmp10 libgnutls30 libhogweed4 libicu57 libidn11 
libip4tc0 libip6tc0 libiptc0 libisc-export160 libksba8 liblocale-gettext-perl 
liblognorm5 libmnl0 libnetfilter-conntrack3 libnettle6 libnfnetlink0 libnpth0 
libp11-kit0 libpsl5 libseccomp2 libsqlite3-0 libtasn1-6 libtext-charwidth-perl 
libtext-iconv-perl libtext-wrapi18n-perl libxtables12 pinentry-curses xxd


^^^ note how this has only libxtables12 but not 11…

then…

I: Retrieving iptables 1.6.0+snapshot20161117-4
I: Validating iptables 1.6.0+snapshot20161117-4
I: Retrieving libip4tc0 1.6.0+snapshot20161117-4
I: Validating libip4tc0 1.6.0+snapshot20161117-4
I: Retrieving libip6tc0 1.6.0+snapshot20161117-4
I: Validating libip6tc0 1.6.0+snapshot20161117-4
I: Retrieving libiptc0 1.6.0+snapshot20161117-4
I: Validating libiptc0 1.6.0+snapshot20161117-4
I: Retrieving libxtables11 1.6.0+snapshot20161117-1
I: Validating libxtables11 1.6.0+snapshot20161117-1
I: Retrieving libxtables12 1.6.0+snapshot20161117-4
I: Validating libxtables12 1.6.0+snapshot20161117-4

and then libxtables12 breaks libxtables11 and things go boom:

W: Failure while configuring base packages.  This will be re-attempted up to 
five times.
W: See /chroots/chroot-installation-sid.trITGPs8f/debootstrap/debootstrap.log 
for details (possibly the package libxtables11:amd64 is at fault)

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#844081: Reproducer

[Adrian Bunk]

On Wed, Nov 23, 2016 at 06:37:17PM +0100, Filip Pytloun wrote:
>...
> That's the reason why lowering the priority down from serious (maybe to
> important instead of normal) to avoid autoremoval.
>...

Your package can get scheduled for autoremoval due to this bug.

But when you get notified that your package got scheduled for 
autoremoval the initial target date for the actual removal
would be around New Year.

And this date gets pushed even further when there is activity
(e.g. comments) in the bug.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#842115: marked as done (partclone: FTBFS: Compiling: fail-mbr.S -> fail-mbr.o -> fail-mbr.image -> /usr/bin/ld: attempted static link of dynamic object `fail-mbr.o')

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 18:04:50 +
with message-id 
and subject line Bug#842115: fixed in partclone 0.2.89-2
has caused the Debian Bug report #842115,
regarding partclone: FTBFS: Compiling: fail-mbr.S -> fail-mbr.o -> 
fail-mbr.image -> /usr/bin/ld: attempted static link of dynamic object 
`fail-mbr.o'
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.)


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

Dear Maintainer,

partclone fails to build from source in unstable/amd64:

  […]

  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-partclone.o `test -f 'partclone.c' || echo './'`partclone.c
  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-progress.o `test -f 'progress.c' || echo './'`progress.c
  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-minixclone.o `test -f 'minixclone.c' || echo './'`minixclone.c
  gcc -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall  -Wl,-z,relro 
-o partclone.minix partclone_minix-main.o partclone_minix-partclone.o 
partclone_minix-progress.o partclone_minix-minixclone.o  -lncursesw -lpthread  
-ltinfo
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/src'
  Making all in docs
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/docs'
  make[3]: Nothing to be done for 'all'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/docs'
  Making all in tests
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/tests'
  make[3]: Nothing to be done for 'all'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/tests'
  Making all in fail-mbr
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/fail-mbr'
  sh compile-mbr.sh
  Compiling: fail-mbr.S -> fail-mbr.o -> fail-mbr.image -> /usr/bin/ld: 
attempted static link of dynamic object `fail-mbr.o'
  collect2: error: ld returned 1 exit status
  fail-mbr.bin [Done]. 
  objcopy: 'fail-mbr.image': No such file
  Checking the file:
  objdump: 'fail-mbr.bin': No such file
  files fail-mbr.bin and fail-mbr.bin.orig differ significantly:
  diff: f1.obj: No such file or directory
  diff: f2.obj: No such file or directory
  Makefile:501: recipe for target 'fail-mbr.bin' failed
  make[3]: *** [fail-mbr.bin] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/fail-mbr'
  Makefile:400: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88'
  Makefile:341: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:13: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


partclone.0.2.88-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End

Processed: Bug#844910 marked as pending

[Debian Bug Tracking System]

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

> tag 844910 pending
Bug #844910 [src:devscripts] devscripts: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844910: marked as pending

[James McCoy]

tag 844910 pending
thanks

Hello,

Bug #844910 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://git.debian.org/?p=collab-maint/devscripts.git;a=commitdiff;h=607c591

---
commit 607c5911b44ca61cf352e80397b5707ee23d9eec
Merge: 1f82d5b 064dc31
Author: James McCoy 
Date:   Wed Nov 23 12:53:49 2016 -0500

Merge branch 'debuild-slimming'

Refactor debuild to be a much thinner wrapper around dpkg-buildpackage.
There is no longer any emulation of dpkg-buildpackage, and unknown
options will be passed through to dpkg-buildpackage.

diff --cc debian/changelog
index cc4327e,cc4327e..8e833ad
--- a/debian/changelog
+++ b/debian/changelog
@@@ -9,6 -9,6 +9,18 @@@ devscripts (2.16.9) UNRELEASED; urgency
* bts:
  + Switch to Net::SMTPS to support STARTTLS.  Based on a patch by Andrew
Shadura.  (Closes: #518622)
++  * Refactor debuild to remove dpkg-buildpackage emulation and generally be a
++much thinner wrapper around dpkg-buildpackage.  (Closes: #789581)
+++ Remove claim from man page that dpkg-buildpackage doesn't support hooks.
++  (Closes: #765495)
+++ Remove handling of all dpkg-buildpackage options that aren't directly
++  used by debuild.
++  - This fixes the issue where debuild didn't understand "-Jauto", as
++debuild now just passes it through.  (Closes: #826508)
+++ Honor -a option regardless of which debuild mode is being used, since
++  both modes now invoke dpkg-buildpackage.  (Closes: #611896)
++  * Fix test debuild test failures due to new dpkg-genbuildinfo calls.
++(Closes: #844910)
  
[ Antonio Terceiro ]
* debrepro:

Bug#825086: marked as done (Package links against libmysqlclient_r)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 18:21:35 +
with message-id 
and subject line Bug#825086: fixed in mysql++ 3.2.2+pristine-2
has caused the Debian Bug report #825086,
regarding Package links against libmysqlclient_r
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.)


-- 
825086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmysql++3v5
Version: 3.2.2+pristine-1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

Please stop linking against libmysqlclient_r and link directly against
libmysqlclient instead.

Your package currently links against libmysqlclient_r. libmysqlclient_r
was the thread-safe version of libmysqlclient in previous MySQL
releases. However, libmysqlclient has been itself been made thread-safe
since before the current libmysqlclient18. Thus libmysqlclient_r is
currently deprecated and provided as a compatibility symlink only, and
will disappear in MySQL 5.7. This change can be made now, in advance of
a possible future transition to libmysqlclient20, which does not provide
the _r variant.

In Ubuntu, we have done this with the attached quilt patch, which I
believe is also applicable to Debian.

Thanks,

Robie Basak
Debian MySQL maintainers team
Ubuntu developer
Author: Robie Basak 
Bug-Ubuntu: https://launchpad.net/bugs/1564871
Forwarded: no
Last-Update: 2016-04-01
Description: use libmysqlclient instead of libmysqlclient_r
 The former supersedes the latter which no longer exists in MySQL 5.7. Patch
 both the m4 macro and the configure script directly since autoreconf fails
 (some m4 macros missing from the source tree?)

--- a/config/mysql_loc.m4
+++ b/config/mysql_loc.m4
@@ -35,7 +35,7 @@
#
if test "x$acx_pthread_ok" = xyes
then
-   MYSQL_C_LIB_NAME=mysqlclient_r
+   MYSQL_C_LIB_NAME=mysqlclient
else
MYSQL_C_LIB_NAME=mysqlclient
fi
--- a/configure
+++ b/configure
@@ -12195,7 +12195,7 @@
#
if test "x$acx_pthread_ok" = xyes
then
-   MYSQL_C_LIB_NAME=mysqlclient_r
+   MYSQL_C_LIB_NAME=mysqlclient
else
MYSQL_C_LIB_NAME=mysqlclient
fi
--- End Message ---
--- Begin Message ---
Source: mysql++
Source-Version: 3.2.2+pristine-2

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

Debian distribution maintenance software
pp.
Roberto C. Sanchez  (supplier of updated mysql++ 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, 23 Nov 2016 12:23:22 -0500
Source: mysql++
Binary: libmysql++-dev libmysql++3v5 libmysql++-doc
Architecture: source amd64 all
Version: 3.2.2+pristine-2
Distribution: unstable
Urgency: medium
Maintainer: Athena Capital Research 
Changed-By: Roberto C. Sanchez 
Description:
 libmysql++-dev - MySQL C++ library bindings (development)
 libmysql++-doc - MySQL C++ library bindings (documentation and examples)
 libmysql++3v5 - MySQL C++ library bindings (runtime)
Closes: 825086 845444
Changes:
 mysql++ (3.2.2+pristine-2) unstable; urgency=medium
 .
   * Avoid linking against libmysqlclient_r and link directly against
 libmysqlclient instead. Thanks Robie Basak 
 for the patch. (Closes: #825086)
   * Thanks to Michael Prokop  for preparing the upload
 (all I did was apply his patch integrating Robie's patch)
 (Closes: #845444)
   * Update to Standards-Version 3.9.8 (no changes)
   * Update to debhelper compatibility level 9 (no changes)
   * Change dependency on libmysqlclient-dev to default-libmysqlclient-dev
   * Enable hardening flags at build time
Checksums-Sha1:
 cbf1c7492bc4723f67aec68196e5e7a5ff70e23a 2013 mysql++_3.2.2+pristine-2.dsc
 fb88397dcc4dbd608c2d6dd4ed5953402643f902 8308 
mysql++_3.2.2+pristine-2.debian.tar.xz
 e59f049b66fd4d71de63b4c45c9b7cea3fd956a2 146778 
libmysql++-dev_3.2.2+pristine-2_amd64.deb
 d5aa8262ea3df21287e0be0544c7a6226ba737d0 1730060 
libmysql++-doc_3.2.2+pri

Bug#841621: marked as done (mysql++: FTBFS: checking for MySQL library directory... configure: error: Didn't find mysqlclient_r library in '/usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/lib64 /u

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 18:21:35 +
with message-id 
and subject line Bug#825086: fixed in mysql++ 3.2.2+pristine-2
has caused the Debian Bug report #825086,
regarding mysql++: FTBFS: checking for MySQL library directory... configure: 
error: Didn't find mysqlclient_r library in '/usr/lib/x86_64-linux-gnu 
/usr/lib/x86_64-linux-gnu/lib64 /usr/lib/x86_64-linux-gnu/lib 
/usr/lib/x86_64-linux-gnu/lib64/mysql /usr/lib/x86_64-linux-gnu/lib/mysql'
to be marked as done.

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

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


-- 
825086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql++
Version: 3.2.2+pristine-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> touch debian/stamp-autotools-files
> chmod a+x /build/mysql++-wwcIxo/mysql++-3.2.2+pristine/./configure
> mkdir -p .
> cd . && CFLAGS="-g -O2 
> -fdebug-prefix-map=/build/mysql++-wwcIxo/mysql++-3.2.2+pristine=. 
> -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
> -fdebug-prefix-map=/build/mysql++-wwcIxo/mysql++-3.2.2+pristine=. 
> -fstack-protector-strong -Wformat -Werror=format-security" 
> CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro -pthread" 
> /build/mysql++-wwcIxo/mysql++-3.2.2+pristine/./configure 
> --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/mysql++" 
> --srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
> --disable-silent-rules --enable-static --enable-thread-check 
> --with-mysql-lib=/usr/lib/x86_64-linux-gnu
> configure: WARNING: unrecognized options: --disable-maintainer-mode, 
> --disable-silent-rules
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... x86_64-pc-linux-gnu
> checking how to print strings... printf
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
> func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking for gawk... no
> checking for mawk... mawk
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for

Bug#835613: marked as done (golang-goyaml: FTBFS: FAIL: encode_test.go:217: S.TestMarshal)

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 20:53:41 +0200
with message-id <20161123185341.mvmljdhd2rjkn...@bunk.spdns.de>
and subject line src:golang-goyaml has been removed from unstable
has caused the Debian Bug report #835613,
regarding golang-goyaml: FTBFS: FAIL: encode_test.go:217: S.TestMarshal
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.)


-- 
835613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-goyaml
Version: 0.0~bzr50-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

golang-goyaml fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  golang-goyaml
   Version:  0.0~bzr50-1
   Build architecture:   amd64
   Date: Sat, 27 Aug 2016 16:41:31 +0100
   Hostname: c194ca82fcc4
   Uname:Linux c194ca82fcc4 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'golang-goyaml-build-deps' in 
'../golang-goyaml-build-deps_0.0~bzr50-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package golang-goyaml-build-deps.
  (Reading database ... 23251 files and directories currently installed.)
  Preparing to unpack golang-goyaml-build-deps_0.0~bzr50-1_all.deb ...
  Unpacking golang-goyaml-build-deps (0.0~bzr50-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.7-go golang-1.7-src golang-go golang-gocheck-dev
golang-src
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.7-go golang-1.7-src golang-go golang-gocheck-dev
golang-src
  0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 26.3 MB of archives.
  After this operation, 143 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.19 
[9548 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.7-src amd64 
1.7-3 [7643 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.7-go amd64 
1.7-3 [18.6 MB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
2:1.7~1 [3186 B]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
2:1.7~1 [22.3 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 golang-gocheck-dev 
all 0.0~bzr20131118+85-2 [27.4 kB]
  Fetched 26.3 MB in 0s (115 MB/s)
  Selecting previously unselected package dh-golang.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23255 files and directories currently installed.)
  Preparing to unpack .../0-dh-golang_1.19_all.deb ...
  Unpacking dh-golang (1.19) ...
  Selecting previously unselected package golang-1.7-src.
  Preparing to unpack 

Processed: debootstrap broken, rm libxtables11 1.6.0+snapshot20161117-1 from sid, at least

[Debian Bug Tracking System]

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

> reassign 845464 iptables,ftp.debian.org
Bug #845464 [itables,ftp.debian.org] debootstrap broken, rm libxtables11 
1.6.0+snapshot20161117-1 from sid, at least
Warning: Unknown package 'itables'
Bug reassigned from package 'itables,ftp.debian.org' to 
'iptables,ftp.debian.org'.
No longer marked as found in versions 1.6.0+snapshot20161117-1.
Ignoring request to alter fixed versions of bug #845464 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 844503

[Debian Bug Tracking System]

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

> tags 844503 + fixed-upstream
Bug #844503 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #843871 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844663 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844664 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844904 [salt-common] salt-formula-ceilometer: FTBFS: Tests failures
Bug #844906 [salt-common] salt-formula-swift: FTBFS: Tests failures
Bug #844916 [salt-common] salt-formula-horizon: FTBFS: Tests failures
Bug #844920 [salt-common] salt-formula-kubernetes: FTBFS: Tests failures
Bug #844926 [salt-common] salt-formula-nova: FTBFS: Tests failures
Bug #844945 [salt-common] salt-formula-keystone: FTBFS: Tests failures
Bug #844947 [salt-common] salt-formula-glance: FTBFS: Tests failures
Bug #844948 [salt-common] salt-formula-heat: FTBFS: Tests failures
Bug #844949 [salt-common] salt-formula-neutron: FTBFS: Tests failures
Bug #844951 [salt-common] salt-formula-cinder: FTBFS: Tests failures
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
843871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843871
844503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844503
844663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844663
844664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844664
844904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844904
844906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844906
844916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844916
844920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844920
844926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844926
844945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844945
844947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844947
844948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844948
844949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844949
844951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #844503 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #843871 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844663 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844664 [salt-common] salt-call fails with libcrypto.so.1.1: undefined 
symbol: OPENSSL_no_config
Bug #844904 [salt-common] salt-formula-ceilometer: FTBFS: Tests failures
Bug #844906 [salt-common] salt-formula-swift: FTBFS: Tests failures
Bug #844916 [salt-common] salt-formula-horizon: FTBFS: Tests failures
Bug #844920 [salt-common] salt-formula-kubernetes: FTBFS: Tests failures
Bug #844926 [salt-common] salt-formula-nova: FTBFS: Tests failures
Bug #844945 [salt-common] salt-formula-keystone: FTBFS: Tests failures
Bug #844947 [salt-common] salt-formula-glance: FTBFS: Tests failures
Bug #844948 [salt-common] salt-formula-heat: FTBFS: Tests failures
Bug #844949 [salt-common] salt-formula-neutron: FTBFS: Tests failures
Bug #844951 [salt-common] salt-formula-cinder: FTBFS: Tests failures
Ignoring request to alter tags of bug #844503 to the same tags previously set
Ignoring request to alter tags of bug #843871 to the same tags previously set
Ignoring request to alter tags of bug #844663 to the same tags previously set
Ignoring request to alter tags of bug #844664 to the same tags previously set
Ignoring request to alter tags of bug #844904 to the same tags previously set
Ignoring request to alter tags of bug #844906 to the same tags previously set
Ignoring request to alter tags of bug #844916 to the same tags previously set
Ignoring request to alter tags of bug #844920 to the same tags previously set
Ignoring request to alter tags of bug #844926 to the same tags previously set
Ignoring request to alter tags of bug #844945 to the same tags previously set
Ignoring request to alter tags of bug #844947 to the same tags previously set
Ignoring request to alter tags of bug #844948 to the same tags previously set
Ignoring request to alter tags of bug #844949 to the same tags previously set
Ignoring request to alter tags of bug #844951 to the same tags previously set

-- 
843871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843871
844503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844503
844663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844663
844664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844664
844904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844904
844906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844906
844916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844916
844920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844920
844926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844926
844945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844945
844947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844947
844948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844948
844949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844949
844951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844503: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Emilio Pozuelo Monfort]

Control: tags -1 fixed-upstream

On 23/11/16 18:09, Emilio Pozuelo Monfort wrote:
> On Fri, 18 Nov 2016 15:22:07 +0100 Benjamin Drung
>  wrote:
>> tags 844503 upstream
>> forwarded 844503 https://github.com/saltstack/salt/pull/37772
>> thanks
>>
>> Am Donnerstag, den 17.11.2016, 21:50 +0100 schrieb Sebastian Andrzej
>> Siewior:
>>> control: tags -1 patch
>>>
>>> On 2016-11-16 12:14:43 [+0100], Filip Pytloun wrote:
 To reproduce the issue simply install salt-master and run salt-
 call:

 Â Â Â Â apt-get install salt-master
 Â Â Â Â salt-call

 Following exception will occur:

 Traceback (most recent call last):
 Â  File "/usr/bin/salt-call", line 11, in 
 Â Â Â Â salt_call()
>>>
>>> …
 Â  File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py",
 line 63, in _init_libcrypto
 Â Â Â Â libcrypto.OPENSSL_no_config()
 Â  File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in
 __getattr__
 Â Â Â Â func = self.__getitem__(name)
 Â  File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in
 __getitem__
 Â Â Â Â func = self._FuncPtr((name_or_ordinal, self))
 AttributeError: /lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined
 symbol: OPENSSL_no_config
>>>
>>> the problem is that salt/rsax931.py loads the library manually and
>>> expects certain symbols which are no longer available in OpenSSL
>>> 1.1.0.
>>> And it loads the first libcrypto it finds plus has no dependency on
>>> openssl.
>>
>> Instead of forcing salt to use OpenSSL 1.0, let's try to make it work
>> with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1
>> was quite easy. I forwarded the patch upstream to
>> https://github.com/saltstack/salt/pull/37772 to get it reviewed and
>> accepted.
> 
> Nice.
> 
> Do you want to wait for upstream before uploading this? It is going to block
> openssl 1.1 from entering testing due to the Breaks that it got, which in turn
> is blocking quite a bunch of stuff. So it'd be good to get this fixed soon.

Just realised this is merged upstream.

So, can you upload it asap? :)

Thanks,
Emilio

Processed: found 845460 in 5.6.4-1

[Debian Bug Tracking System]

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

> found 845460 5.6.4-1
Bug #845460 [libcrypto++6] Symbol disappeared without soname bump
Marked as found in versions libcrypto++/5.6.4-1.
> thanks
Stopping processing here.

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

Processed: gnome-color-chooser: diff for NMU version 0.2.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 817295 + patch
Bug #817295 [src:gnome-color-chooser] gnome-color-chooser: Removal of dh_desktop
Added tag(s) patch.
> tags 817295 + pending
Bug #817295 [src:gnome-color-chooser] gnome-color-chooser: Removal of dh_desktop
Added tag(s) pending.

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

Bug#817295: gnome-color-chooser: diff for NMU version 0.2.5-1.1

[Andrey Rahmatullin]

Control: tags 817295 + patch
Control: tags 817295 + pending

Dear maintainer,

I've prepared an NMU for gnome-color-chooser (versioned as 0.2.5-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru gnome-color-chooser-0.2.5/debian/changelog gnome-color-chooser-0.2.5/debian/changelog
--- gnome-color-chooser-0.2.5/debian/changelog	2016-11-24 01:07:42.0 +0500
+++ gnome-color-chooser-0.2.5/debian/changelog	2016-11-24 00:46:16.0 +0500
@@ -1,3 +1,13 @@
+gnome-color-chooser (0.2.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to 3.0 (quilt).
+  * Bump debhlper compat level to 9.
+  * Replace d/rules with dh(1) invocation (Closes: #817295).
+  * Bump Standards-Version to 3.9.8.
+
+ -- Andrey Rahmatullin   Thu, 24 Nov 2016 00:46:16 +0500
+
 gnome-color-chooser (0.2.5-1) unstable; urgency=low
 
   * new upstream release
diff -Nru gnome-color-chooser-0.2.5/debian/compat gnome-color-chooser-0.2.5/debian/compat
--- gnome-color-chooser-0.2.5/debian/compat	2016-11-24 01:07:42.0 +0500
+++ gnome-color-chooser-0.2.5/debian/compat	2016-11-24 00:46:16.0 +0500
@@ -1 +1 @@
-5
+9
diff -Nru gnome-color-chooser-0.2.5/debian/control gnome-color-chooser-0.2.5/debian/control
--- gnome-color-chooser-0.2.5/debian/control	2016-11-24 01:07:42.0 +0500
+++ gnome-color-chooser-0.2.5/debian/control	2016-11-24 00:46:16.0 +0500
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: Werner Pantke 
 Homepage: http://gnomecc.sourceforge.net
-Build-Depends: debhelper (>= 5), autotools-dev, gnome-common (>= 2.20.0), gettext, intltool (>= 0.35.5), libgtkmm-2.4-dev (>= 2.8.0), libglademm-2.4-dev (>= 2.6.0), libgnome2-dev (>= 2.16.0), libgnomeui-dev (>= 2.14.0), libxml2-dev (>= 2.6.0)
-Standards-Version: 3.8.1
+Build-Depends: debhelper (>= 9), autotools-dev, gnome-common (>= 2.20.0), gettext, intltool (>= 0.35.5), libgtkmm-2.4-dev (>= 2.8.0), libglademm-2.4-dev (>= 2.6.0), libgnome2-dev (>= 2.16.0), libgnomeui-dev (>= 2.14.0), libxml2-dev (>= 2.6.0)
+Standards-Version: 3.9.8
 
 Package: gnome-color-chooser
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: gtk2-engines (>= 2.18.1)
 Suggests: nautilus (>= 2.18.2)
 Description: GTK+/GNOME desktop appearance customization tool
diff -Nru gnome-color-chooser-0.2.5/debian/docs gnome-color-chooser-0.2.5/debian/docs
--- gnome-color-chooser-0.2.5/debian/docs	1970-01-01 05:00:00.0 +0500
+++ gnome-color-chooser-0.2.5/debian/docs	2016-11-24 00:37:36.0 +0500
@@ -0,0 +1,2 @@
+NEWS
+THANKS
diff -Nru gnome-color-chooser-0.2.5/debian/rules gnome-color-chooser-0.2.5/debian/rules
--- gnome-color-chooser-0.2.5/debian/rules	2016-11-24 01:07:42.0 +0500
+++ gnome-color-chooser-0.2.5/debian/rules	2016-11-24 00:36:34.0 +0500
@@ -1,69 +1,7 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
-#export DH_VERBOSE=1
+export DEB_LDFLAGS_MAINT_APPEND=-Wl,-z,defs
 
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
-CFLAGS = -Wall -g
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-	CFLAGS += -O0
-else
-	CFLAGS += -O2
-endif
-
-config.status: configure
-	dh_testdir
-
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-	cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-	cp -f /usr/share/misc/config.guess config.guess
-endif
-	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info CFLAGS="$(CFLAGS)" LDFLAGS="-Wl,-z,defs"
-
-
-build: build-stamp
-
-build-stamp:  config.status
-	dh_testdir
-	$(MAKE)
-	touch $@
-
-clean:
-	dh_testdir
-	dh_testroot
-	[ ! -f Makefile ] || $(MAKE) distclean
-	rm -f build-stamp
-	rm -f config.sub config.guess
-	dh_clean
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_clean -k
-	dh_desktop
-	$(MAKE) DESTDIR=$(CURDIR)/debian/gnome-color-chooser install
-
-binary-indep: build install
-
-binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installchangelogs ChangeLog
-	dh_installdocs NEWS THANKS
-	dh_link
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+%:
+	dh $@
diff -Nru gnome-color-chooser-0.2.5/debian/source/format gnome-color-chooser-0.2.5/debian/source/format
--- gnome-color-chooser-0.2.5/debian/source/format	1970-01-01 05:00:00.0 +0500
+++ gnome-color-chooser-0.2.5/debian/source/format	2016-11-24 00:34:45.0 +0500
@@ -0,0 +1 @@
+3.0 (quilt)


signature.asc
Description: PGP signature

Processed: gtkterm: diff for NMU version 0.99.7~rc1-0.3

[Debian Bug Tracking System]

Processing control commands:

> tags 817489 + patch
Bug #817489 [src:gtkterm] gtkterm: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817489 + pending
Bug #817489 [src:gtkterm] gtkterm: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#817489: gtkterm: diff for NMU version 0.99.7~rc1-0.3

[Andrey Rahmatullin]

Control: tags 817489 + patch
Control: tags 817489 + pending

Dear maintainer,

I've prepared an NMU for gtkterm (versioned as 0.99.7~rc1-0.3) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u gtkterm-0.99.7~rc1/debian/compat gtkterm-0.99.7~rc1/debian/compat
--- gtkterm-0.99.7~rc1/debian/compat
+++ gtkterm-0.99.7~rc1/debian/compat
@@ -1 +1 @@
-4
+10
diff -u gtkterm-0.99.7~rc1/debian/control gtkterm-0.99.7~rc1/debian/control
--- gtkterm-0.99.7~rc1/debian/control
+++ gtkterm-0.99.7~rc1/debian/control
@@ -2,7 +2,7 @@
 Section: comm
 Priority: optional
 Maintainer: Sebastien Bacher 
-Build-Depends: cdbs, debhelper (>= 4.0), libgtk2.0-dev, libvte-dev, intltool
+Build-Depends: cdbs, debhelper (>= 10), libgtk2.0-dev, libvte-dev, intltool
 Standards-Version: 3.6.1.0
 
 Package: gtkterm
reverted:
--- gtkterm-0.99.7~rc1/debian/menu
+++ gtkterm-0.99.7~rc1.orig/debian/menu
@@ -1,5 +0,0 @@
-?package(gtkterm):\
-needs=X11\
-section=Apps/Technical\
-title="gtkterm"\
-command="/usr/bin/gtkterm"
diff -u gtkterm-0.99.7~rc1/debian/changelog gtkterm-0.99.7~rc1/debian/changelog
--- gtkterm-0.99.7~rc1/debian/changelog
+++ gtkterm-0.99.7~rc1/debian/changelog
@@ -1,3 +1,12 @@
+gtkterm (0.99.7~rc1-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to debhelper compat level 10 (Closes: #817489).
+  * Remove the menu file.
+  * Add explicit debian/source/format.
+
+ -- Andrey Rahmatullin   Thu, 24 Nov 2016 01:13:00 +0500
+
 gtkterm (0.99.7~rc1-0.2) unstable; urgency=low
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- gtkterm-0.99.7~rc1.orig/debian/source/format
+++ gtkterm-0.99.7~rc1/debian/source/format
@@ -0,0 +1 @@
+1.0


signature.asc
Description: PGP signature

Bug#835127: tellico: Tellico always crashes at boot time

[Andrey Rahmatullin]

On Mon, Aug 22, 2016 at 09:14:31PM +0200, Luigi wrote:
> Tellico always crashes at boot time, immediately. The package is totally 
> unusable.
It works for me on a clean install. You'll need to provide more info.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#843712: marked as done (biojava4-live: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 23 Nov 2016 21:37:33 +0100
with message-id <20161123203733.go10...@an3as.eu>
and subject line Closing since this bug was possibly caused by broken 
Build-Depends
has caused the Debian Bug report #843712,
regarding biojava4-live: FTBFS (failing tests)
to be marked as done.

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

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


-- 
843712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:biojava4-live
Version: 4.1.0+dfsg-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep  --with javahelper
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/biojava4-live-4.1.0+dfsg'
dh_auto_configure
sed -e 's/BJLIB/biojava4-forester/g' debian/build.xml > 
biojava-forester/build.xml
sed -e 's/BJLIB/biojava4-aa-prop/g' debian/build.xml > biojava-aa-prop/build.xml
sed -e 's/BJLIB/biojava4-core/g' debian/build.xml > biojava-core/build.xml
sed -e 's/BJLIB/biojava4-alignment/g' debian/build.xml > 
biojava-alignment/build.xml
sed -e 's/BJLIB/biojava4-genome/g' debian/build.xml > biojava-genome/build.xml
sed -e 's/BJLIB/biojava4-modfinder/g' debian/build.xml > 
biojava-modfinder/build.xml

[... snipped ...]

[junit] Testcase: testProteinSequenceFactoring[0] took 0 sec
[junit] Testcase: testFeatures[0] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[1] took 0 sec
[junit] Testcase: testFeatures[1] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[2] took 0 sec
[junit] Testcase: testFeatures[2] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[3] took 0 sec
[junit] Testcase: testFeatures[3] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[4] took 0 sec
[junit] Testcase: testFeatures[4] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[5] took 0 sec
[junit] Testcase: testFeatures[5] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[6] took 0 sec
[junit] Testcase: testFeatures[6] took 0 sec
[junit] Testcase: testProteinSequenceFactoring[7] took 0 sec
[junit] Testcase: testFeatures[7] took 0 sec
[junit] Running 
org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest
[junit] Testsuite: 
org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
0.592 sec
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
0.592 sec
[junit] - Standard Error -
[junit] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[junit] SLF4J: Defaulting to no-operation (NOP) logger implementation
[junit] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for 
further details.
[junit] -  ---
[junit] 
[junit] Testcase: testWrongSequence took 0.554 sec
[junit] Caused an ERROR
[junit] Unexpected exception, expected but 
was
[junit] java.lang.Exception: Unexpected exception, 
expected but 
was
[junit] Caused by: org.biojava.nbio.core.exceptions.ParserException: 
Section key was null
[junit] at 
org.biojava.nbio.core.sequence.io.GenbankSequenceParser.parse(GenbankSequenceParser.java:143)
[junit] at 
org.biojava.nbio.core.sequence.io.GenbankSequenceParser.getSequence(GenbankSequenceParser.java:368)
[junit] at 
org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReader.(GenbankProxySequenceReader.java:86)
[junit] at 
org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest.testWrongSequence(SimpleGenbankProxySequenceReaderTest.java:53)
[junit] 

BUILD FAILED
/<>/biojava4-live-4.1.0+dfsg/biojava-core/build.xml:101: Test 
org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest 
failed

Total time: 13 seconds
debian/rules:57: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/biojava4-live-4.1.0+dfsg'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
---

Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: procps
Version: 2:3.3.12-3
Severity: critical

ps is depending on /usr/lib/x86_64-linux-gnu/liblz4.so.1. As udev needs
ps to be started, it cannot make the devices available where /usr is on
so the boot fails completely.

Please make ps not to depend on libraries in /usr.

This drove me crazy today when I had to reboot my system to replace a
disk and after the replacement nothing worked anymore. In the end, I
copied /usr/lib/x86_64-linux-gnu/liblz4.so.1 to /lib to get my system
back. But this is just a shortterm solution.

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

Kernel: Linux 4.7.10 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages procps depends on:
ii  init-system-helpers  1.46
ii  libc62.24-5
ii  libncurses5  6.0+20160917-1
ii  libncursesw5 6.0+20160917-1
ii  libprocps6   2:3.3.12-3
ii  libtinfo56.0+20160917-1
ii  lsb-base 9.20161101

Versions of packages procps recommends:
ii  psmisc  22.21-2.1+b1

procps suggests no packages.

- -- Configuration Files:
/etc/sysctl.conf changed:
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.tcp_syncookies=1
net.ipv4.icmp_echo_ignore_broadcasts = 1
kernel.panic = 30
net.ipv4.tcp_ecn = 1
net.ipv4.tcp_fastopen = 1


- -- no debconf information

- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg1/vUACgkQpnwKsYAZ
9qw0lwv/XGHnlDDv8S8X/UrYNQlzNjys65fSbI87pyNexpI2PevgIiNmce3StwxO
+/+jEDF29+WCLCB5oFArfAtWIQmtxgHEaSn5IUp1ciJ8z4m72uxzP9muWLCMiLQh
IA048bAfMV157Cg0z1HJYFtOZi0nAkgGOlpDkfsiVdZz9yIqlNScB6bmZ7xdrvVC
P/9eLKBaasXUxpfyfxmN4/9Ti4OxMiGZDKto4706Ldzy5YyudFrJ+DXiavxSGif4
g3d+uoL8fdjrOBy/5WFn1XOeQ1gYewO/J2VMyOkWJCHWtB2AG+I/ZAaCB2QOdFji
1hRrYI5RTDeTJlL0enppqCC1pZFr/MU6oBI3pghr7M5CuOth1kHPyx/mNVIycdRs
d4oDV+o592UXqx7zF6jyI0+dEh929jadsK20vZ2rlTi1plYf3U1bdxwSstoMwm8G
7RhN6zTl7CIZzcCuJfG40dmNfvQtN7ns35m4pRraeP5NqcqH/CjHpFPH8ojSjYUU
TE/bNnXc
=1Jai
-END PGP SIGNATURE-

Bug#844938: The new node-tap is causing FTBFS in node-inline-source-map

[Ross Gammon]

tag 844938 + upstream
forwarded 844938 https://github.com/thlorenz/inline-source-map/issues/18
thanks

Hi,

I have just investigated what has changed that might be causing this
failure of the upstream testsuite, and it appears to be the recent
update of node-tap to Version 8.0.0.

The bug has been passed upstream
(https://github.com/thlorenz/inline-source-map/issues/18), but if there
are any node-tap experts reading this, I would be grateful for a patch
to send there (as the Stretch release is looming).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Processed: The new node-tap is causing FTBFS in node-inline-source-map

[Debian Bug Tracking System]

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

> tag 844938 + upstream
Bug #844938 [src:node-inline-source-map] node-inline-source-map: FTBFS: Tests 
failures
Added tag(s) upstream.
> forwarded 844938 https://github.com/thlorenz/inline-source-map/issues/18
Bug #844938 [src:node-inline-source-map] node-inline-source-map: FTBFS: Tests 
failures
Set Bug forwarded-to-address to 
'https://github.com/thlorenz/inline-source-map/issues/18'.
> thanks
Stopping processing here.

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

Bug#845484: libdpkg-perl: broken /usr/share/dpkg/no-pie-compile.specs

[Roman Tsisyk]

Package: libdpkg-perl
Version: 1.18.15
Severity: serious

Hi,

I use cdbs with cmake, which automatically adds the following compilation flags 
gcc/g++/ld:

-DCMAKE_C_FLAGS="-g -O2 -fdebug-prefix-map= =. 
-specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2" 
-DCMAKE_CXX_FLAGS="-g -O2 -fdebug-prefix-map==. 
-specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2" 
-DCMAKE_MODULE_LINKER_FLAGS="-specs=/usr/share/dpkg/no-pie-link.specs 
-Wl,-z,relro" 
-DCMAKE_SHARED_LINKER_FLAGS="-specs=/usr/share/dpkg/no-pie-link.specs 
-Wl,-z,relro" 

After the latest update of Stretch almost C/C++ packages fail to build with the 
following messages:

/usr/bin/ld: xxx.o: relocation R_X86_64_32S against `.rodata' can not be 
used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output

cat /usr/share/dpkg/no-pie-compile.specs
*self_spec:
+ %{!r:%{!fpie:%{!fPIE:%{!fpic:%{!fPIC:%{!fno-pic:-fno-PIE}}


gcc can't compile even a simple C program using this spec:

--
#include 

int
main(void)
{
    printf("hello\n");
    return 0;
}
--

--
gcc xx.c -o xx -specs=/usr/share/dpkg/no-pie-compile.specs
/usr/bin/ld: /tmp/ccEbzEVn.o: relocation R_X86_64_32 against `.rodata' can not 
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
--

This spec file is owned by libdpkg-perl package.  Please consider to fix this 
spec or to revert the latest changes.
Severity is serious because this spec file is completely unusable for everyone.

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

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

Versions of packages libdpkg-perl depends on:
ii  dpkg  1.18.15
ii  perl  5.22.2-3

Versions of packages libdpkg-perl recommends:
ii  bzip2   1.0.6-8
ii  libfile-fcntllock-perl  0.22-3+b1
ii  liblocale-gettext-perl  1.07-3
ii  xz-utils    5.2.2-1.2

Versions of packages libdpkg-perl suggests:
ii  binutils    2.27.51.20161108-1
ii  clang-3.6 [c-compiler]  1:3.6.2-3
ii  clang-3.7 [c-compiler]  1:3.7.1-3
ii  clang-3.8 [c-compiler]  1:3.8.1-16
ii  clang-3.9 [c-compiler]  1:3.9-6
ii  debian-keyring  2016.09.04
ii  gcc [c-compiler]    4:6.1.1-1
ii  gcc-4.9 [c-compiler]    4.9.3-14
ii  gcc-5 [c-compiler]  5.4.1-3
ii  gcc-6 [c-compiler]  6.2.0-13
ii  gnupg   1.4.20-6
ii  gnupg2  2.1.11-7
ii  gpgv    2.1.15-9
ii  patch   2.7.5-1

-- no debconf information

-- 
WBR,
     Roman Tsisyk 
     http://tarantool.org/ - an efficient in-memory data store and a Lua 
application server

Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable

[Craig Small]

Actually its not ps, its libsystemd that is pulling this dependency in. ps
is linked to libsystemd which is in /lib and
$ ldd /lib/x86_64-linux-gnu/libsystemd.so | grep usr
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fa2cf30)

There is also this on the systemd bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843809

I am not sure at this point where to go, but it is either intentional or a
bug, but its not ps' bug.

 - Craig



On Thu, Nov 24, 2016 at 7:42 AM Klaus Ethgen  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Package: procps
> Version: 2:3.3.12-3
> Severity: critical
>
> ps is depending on /usr/lib/x86_64-linux-gnu/liblz4.so.1. As udev needs
> ps to be started, it cannot make the devices available where /usr is on
> so the boot fails completely.
>
> Please make ps not to depend on libraries in /usr.
>
> This drove me crazy today when I had to reboot my system to replace a
> disk and after the replacement nothing worked anymore. In the end, I
> copied /usr/lib/x86_64-linux-gnu/liblz4.so.1 to /lib to get my system
> back. But this is just a shortterm solution.
>
> - -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.7.10 (SMP w/8 CPU cores)
> Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages procps depends on:
> ii  init-system-helpers  1.46
> ii  libc62.24-5
> ii  libncurses5  6.0+20160917-1
> ii  libncursesw5 6.0+20160917-1
> ii  libprocps6   2:3.3.12-3
> ii  libtinfo56.0+20160917-1
> ii  lsb-base 9.20161101
>
> Versions of packages procps recommends:
> ii  psmisc  22.21-2.1+b1
>
> procps suggests no packages.
>
> - -- Configuration Files:
> /etc/sysctl.conf changed:
> net.ipv4.conf.default.rp_filter=1
> net.ipv4.conf.all.rp_filter=1
> net.ipv4.tcp_syncookies=1
> net.ipv4.icmp_echo_ignore_broadcasts = 1
> kernel.panic = 30
> net.ipv4.tcp_ecn = 1
> net.ipv4.tcp_fastopen = 1
>
>
> - -- no debconf information
>
> - --
> Klaus Ethgen   http://www.ethgen.ch/
> pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
> Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
> -BEGIN PGP SIGNATURE-
> Comment: Charset: ISO-8859-1
>
> iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg1/vUACgkQpnwKsYAZ
> 9qw0lwv/XGHnlDDv8S8X/UrYNQlzNjys65fSbI87pyNexpI2PevgIiNmce3StwxO
> +/+jEDF29+WCLCB5oFArfAtWIQmtxgHEaSn5IUp1ciJ8z4m72uxzP9muWLCMiLQh
> IA048bAfMV157Cg0z1HJYFtOZi0nAkgGOlpDkfsiVdZz9yIqlNScB6bmZ7xdrvVC
> P/9eLKBaasXUxpfyfxmN4/9Ti4OxMiGZDKto4706Ldzy5YyudFrJ+DXiavxSGif4
> g3d+uoL8fdjrOBy/5WFn1XOeQ1gYewO/J2VMyOkWJCHWtB2AG+I/ZAaCB2QOdFji
> 1hRrYI5RTDeTJlL0enppqCC1pZFr/MU6oBI3pghr7M5CuOth1kHPyx/mNVIycdRs
> d4oDV+o592UXqx7zF6jyI0+dEh929jadsK20vZ2rlTi1plYf3U1bdxwSstoMwm8G
> 7RhN6zTl7CIZzcCuJfG40dmNfvQtN7ns35m4pRraeP5NqcqH/CjHpFPH8ojSjYUU
> TE/bNnXc
> =1Jai
> -END PGP SIGNATURE-
>