Processed: your mail

[Debian Bug Tracking System]

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

> notfound 828260 2.9.0-3
Bug #828260 [src:casablanca] casablanca: FTBFS with openssl 1.1.0
Ignoring request to alter found versions of bug #828260 to the same values 
previously set
> reassign 828260 src:boost1.61
Bug #828260 [src:casablanca] casablanca: FTBFS with openssl 1.1.0
Bug reassigned from package 'src:casablanca' to 'src:boost1.61'.
No longer marked as found in versions casablanca/2.8.0-2.
Ignoring request to alter fixed versions of bug #828260 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#828440: moonshot-gss-eap: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-11-01 17:41:27 [-0400], Sam Hartman wrote:
> Hi.
Hi,

> I'm sorry I didn't get a chance to respond to your other mail.
> upstream has dealt with moonshot-gss-eap and moonshot-ui and I plan to
> address the bugs there with a new upstream version.

You could point that out in the relevant bug report before someone
spends time trying to help you. It sounded like nobody has time for this
and now I learn that upstream already fixed it.

Sebastian

Bug#840189: marked as done (dblatex fails in pdflatex: Use of \@xmultirow doesn't match its definition)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 07:56:07 +
with message-id 
and subject line Bug#840189: fixed in texlive-extra 2016.20161103-1
has caused the Debian Bug report #840189,
regarding dblatex fails in pdflatex: Use of \@xmultirow doesn't match its 
definition
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.)


-- 
840189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dblatex
Version: 0.3.8-1
Severity: grave

dblatex in sid fails on every document as follows:

$ echo 'Hello, world!' > 
hello.xml
$ dblatex hello.xml
Build the book set list...
Build the listings...
XSLT stylesheets DocBook - LaTeX 2e (0.3.8-1)
===
Build hello.pdf
pdflatex failed
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: Use of \@xmultirow 
doesn't match its definition.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: Missing 
\begin{document}.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: You can't use `macro 
parameter character #' in horizontal mode.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[#
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: You can't use `macro 
parameter character #' in horizontal mode.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[#2]{#
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: You can't use `macro 
parameter character #' in horizontal mode.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[#2]{#3}[#
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: You can't use `macro 
parameter character #' in horizontal mode.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[#2]{#3}[#4]{#
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: Too many }'s.
/usr/share/texmf/tex/latex/dblatex/style/dbk_table.sty:32: leading text: 
\expandafter{\@xmultirow{#1}[#2]{#3}[#4]{#5}}
Unexpected error occured
Error: pdflatex compilation failed

This causes openafs to FTBFS.

The problem seems to have been triggered by texlive-latex-extra 
2016.20161008-1, whose multirow.sty has a different \@xmultirow macro that 
takes six arguments rather than five.  Downgrading to texlive-latex-extra 
2016.20160819-1 from stretch makes the problem goes away.

Since \@xmultirow is a private internal macro, dblatex should not rely on 
it.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2016.20161103-1

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Nov 2016 11:51:11 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-generic-extra texlive-plain-extra 
texlive-latex-extra texlive-fonts-extra texlive-music texlive-games 
texlive-pstricks texlive-publishers texlive-humanities texlive-science 
texlive-htmlxml etoolbox texlive-fonts-extra-doc texlive-humanities-doc 
texlive-latex-extra-doc texlive-science-doc texlive-pstricks-doc 
texlive-publishers-doc
Architecture: source all
Version: 2016.20161103-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 etoolbox   - TeX Live: transitional dummy package
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 tex

Bug#840291: marked as done (auto-multiple-choice: FTBFS: ! Use of \@xmultirow doesn't match its definition.)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 07:56:07 +
with message-id 
and subject line Bug#840189: fixed in texlive-extra 2016.20161103-1
has caused the Debian Bug report #840189,
regarding auto-multiple-choice: FTBFS: ! Use of \@xmultirow doesn't match its 
definition.
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.)


-- 
840189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: auto-multiple-choice
Version: 1.3.0-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,

auto-multiple-choice fails to build from source in unstable/amd64:

  [..]

  rm -f lang/ja.mo lang/es.mo lang/fr.mo lang/ar.mo lang/de.mo
  rm -f *.bpot
  rm -f *.po
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0/I18N'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0'
 dh_clean
   debian/rules build
  AMCCONF=deb dh build --with tex
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0'
  Recording substitution variables from ./Makefile.versions ./Makefile.conf 
./Makefile-deb.conf
  perl -p vars-subs.pl auto-multiple-choice.in > auto-multiple-choice
  perl -p vars-subs.pl auto-multiple-choice.desktop.in > 
auto-multiple-choice.desktop
  perl -p vars-subs.pl AMC-gui-apropos.glade.in > AMC-gui-apropos.glade
  perl -p vars-subs.pl AMC-gui.pl.in > AMC-gui.pl
  perl -p vars-subs.pl AMC-latex-link.pl.in > AMC-latex-link.pl
  perl -p vars-subs.pl AMC-perl/AMC/Basic.pm.in > AMC-perl/AMC/Basic.pm
  perl -p vars-subs.pl doc/doc-xhtml-site.fr.xsl.in > doc/doc-xhtml-site.fr.xsl
  perl -p vars-subs.pl doc/doc-xhtml-site.ja.xsl.in > doc/doc-xhtml-site.ja.xsl
  perl -p vars-subs.pl doc/doc-xhtml-site.en.xsl.in > doc/doc-xhtml-site.en.xsl
  perl -p vars-subs.pl doc/amcdocstyle.sty.in > doc/amcdocstyle.sty
  perl -p vars-subs.pl doc/doc-xhtml.xsl.in > doc/doc-xhtml.xsl
  perl -p vars-subs.pl doc/auto-multiple-choice.en.in.xml > 
doc/auto-multiple-choice.en.xml
  perl -p vars-subs.pl doc/auto-multiple-choice.fr.in.xml > 
doc/auto-multiple-choice.fr.xml
  perl -p vars-subs.pl doc/auto-multiple-choice.ja.in.xml > 
doc/auto-multiple-choice.ja.xml
  perl -p vars-subs.pl doc/sty/automultiplechoice.dtx.in > 
doc/sty/automultiplechoice.dtx
  gcc -o AMC-detect AMC-detect.cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro  
-lstdc++ -lm -I /usr/include/opencv -lopencv_core -lopencv_highgui 
-lopencv_imgproc
  gcc -o AMC-buildpdf AMC-buildpdf.cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro  
-lstdc++ -lm -pthread -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/poppler/glib -I/usr/include/poppler 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -lpangocairo-1.0 -lpango-1.0 
-lpoppler-glib -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lcairo -I 
/usr/include/opencv -lopencv_core -lopencv_highgui -lopencv_imgproc
  rsvg-convert -w 32 -h 32 icons/auto-multiple-choice.svg -o 
icons/auto-multiple-choice.png
  pngtopnm icons/auto-multiple-choice.png | ppmtoxpm > 
icons/auto-multiple-choice.xpm
  ppmtoxpm: (Computing colormap...
  ppmtoxpm: ...Done.  41 colors found.)
  
  make -C doc
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161010102028.urpidXRVJT.db.auto-multiple-choice/auto-multiple-choice-1.3.0/doc'
  case auto-multiple-choice.en.xml in \
 *.ja.xml) dblatex -P latex.encoding=utf8 -b xetex -t tex -p custom.xsl 
--texstyle=amcdocstyle --xslt-opts="--nonet" --xslt-opts="--catalogs"  
auto-multiple-choice.en.xml -o auto-multiple-choice.en.tex ;; \
 *.xml) dblatex -t tex -p custom.xsl --texstyle=amcdocstyle 
--xslt-opts="--nonet" --xslt-opts="--catalogs"  auto-multiple-choice.en.xml 

Bug#840200: marked as done (texlive-lang-arabic: tries to overwrite file from texlive-xetex)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 07:59:21 +
with message-id 
and subject line Bug#840200: fixed in texlive-lang 2016.20161103-1
has caused the Debian Bug report #840200,
regarding texlive-lang-arabic: tries to overwrite file from texlive-xetex
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.)


-- 
840200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-lang-arabic
Version: 2016.20161008-1
Severity: serious
Justification: fails to install

Hi,

from 
https://jenkins.debian.net/job/chroot-installation_stretch_install_full_desktop_upgrade_to_sid_aptdpkg_first/262//console

Preparing to unpack .../132-texlive-lang-arabic_2016.20161008-1_all.deb ...
Unpacking texlive-lang-arabic (2016.20161008-1) over (2016.20160819-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-OUzNcU/132-texlive-lang-arabic_2016.20161008-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/doc/texlive-doc/xelatex/xepersian/README', 
which is also in package texlive-xetex 2016.20160819-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
[...]
Errors were encountered while processing:
 /tmp/apt-dpkg-install-OUzNcU/132-texlive-lang-arabic_2016.20161008-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Thanks for maintaining texlive!

-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: texlive-lang
Source-Version: 2016.20161103-1

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-lang 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Nov 2016 11:51:19 +0900
Source: texlive-lang
Binary: texlive-lang-african texlive-lang-arabic texlive-lang-cjk 
texlive-lang-korean texlive-lang-chinese texlive-lang-japanese 
texlive-lang-cyrillic texlive-lang-czechslovak texlive-lang-english 
texlive-lang-european texlive-lang-french texlive-lang-german 
texlive-lang-greek texlive-lang-indic texlive-lang-italian texlive-lang-other 
texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish 
texlive-lang-all
Architecture: source all
Version: 2016.20161103-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-lang-african - TeX Live: African scripts
 texlive-lang-all - TeX Live: metapackage depending on all TeX Live language 
packages
 texlive-lang-arabic - TeX Live: Arabic
 texlive-lang-chinese - TeX Live: Chinese
 texlive-lang-cjk - TeX Live: Chinese/Japanese/Korean (base)
 texlive-lang-cyrillic - TeX Live: Cyrillic
 texlive-lang-czechslovak - TeX Live: Czech/Slovak
 texlive-lang-english - TeX Live: US and UK English
 texlive-lang-european - TeX Live: Other European languages
 texlive-lang-french - TeX Live: French
 texlive-lang-german - TeX Live: German
 texlive-lang-greek - TeX Live: Greek
 texlive-lang-indic - TeX Live: Indic scripts
 texlive-lang-italian - TeX Live: Italian
 texlive-lang-japanese - TeX Live: Japanese
 texlive-lang-korean - TeX Live: Korean
 texlive-lang-other - TeX Live: Other languages
 texlive-lang-polish - TeX Live: Polish
 texlive-lang-portuguese - TeX Live: Portuguese
 texlive-lang-spanish - TeX Live: Spanish
Closes: 753143 840200
Changes:
 texlive-lang (2016.20161103-1) unstable; urgency=medium
 .
   * xepersian moved from texlive-xetex to texlive-lang-arabian.
 Conflict added (Closes: #840200)
   * new upstream checkout:
 - fix missing shorthands in German dialects (Closes: #753143)
Checksums-Sha1:
 de37bf256c41331062e0e1635f6c610209abc18c 2905 texlive-lang_2016.20161103-1.dsc
 29770f463bb8d67b40950cd385151df5ae38 453323828 
texlive-lang_2016.20161103.orig.tar.xz
 5ed5a5f80d7647a9c9e793668575749a641dcbcb 87560 
texlive-lang_2016.20161103-1.debian.tar.xz
 420768d30b5ae910e3f9f619872868b63f1dfece 5910340 
texlive-lang-african_2016.20161103-1_all.deb
 

Processed: reopening 828378

[Debian Bug Tracking System]

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

> reopen 828378
Bug #828378 {Done: Thijs Kinkhorst } 
[src:libapache2-mod-auth-cas] libapache2-mod-auth-cas: 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 libapache2-mod-auth-cas/1.1-1.
> thanks
Stopping processing here.

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

Processed: Bug#841581 marked as pending

[Debian Bug Tracking System]

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

> tag 841581 pending
Bug #841581 [src:pycryptopp] pycryptopp: FTBFS: eccrypto.h:19:18: fatal error: 
hmqv.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841581: marked as pending

[Sophie Brun]

tag 841581 pending
thanks

Hello,

Bug #841581 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-security/patator.git;a=commitdiff;h=c9f9fa8

---
commit c9f9fa8bd64b6d34e092f01bcc436cc3997910de
Author: Sophie Brun 
Date:   Mon Oct 31 15:08:48 2016 +0100

Drop useless dependency on python-pycrytopp (Closes: #841581)

diff --git a/debian/changelog b/debian/changelog
index 5d41ced..9912a9d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
 patator (0.6-2) UNRELEASED; urgency=medium
 
+  [ Gianfranco Costamagna ]
   * Team upload.
   * Add gbp.conf file
 
+  [ Sophie Brun ]
+  * Drop useless dependency on python-pycrytopp (Closes: #841581)
+
  -- Gianfranco Costamagna   Mon, 22 Aug 2016 
17:37:45 +0200
 
 patator (0.6-1) unstable; urgency=low

Processed: Re: Bug#828240: asterisk: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #828240 [src:asterisk] asterisk: FTBFS with openssl 1.1.0
Added tag(s) help.

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

Bug#828240: asterisk: FTBFS with openssl 1.1.0

[Bernhard Schmidt]

Control: tags -1 help

Hi,

current state on this:

- There is no progress visible in the upstream bugtracker, I have also
  not found anything in other distros (Fedora etc.)

- switching to libssl1.0-dev does not work for now because the
  build-deps

libc-client2007e-dev
libpjproject-dev
libsnmp-dev

  depend on the conflicting libssl-dev. 

  libpjproject has already switched to libssl1.0-dev, so the dependency
  looks like a bug in d-devlibdeps. That could be easily overridden.

  libc-client2007e-dev has an open FTBFS against OpenSSL 1.1.0 anyway,
  but there is a patch in the BTS.

  Maybe one could just drop the libssl-dev dependency from
  libc-client2007e-dev and libsnmp-dev, as done for libpq-dev?

- Asterisk is doing some weird stuff with macros in
  
https://sources.debian.net/src/asterisk/1:13.11.2~dfsg-1/main/libasteriskssl.c/
  that causes the build against 1.1.0 to fail. This is beyond my C
  knowledge. I will gladly test and accept any patch for that.

Best Regards,
Bernhard


signature.asc
Description: Digital signature

Processed: tagging 842891

[Debian Bug Tracking System]

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

> tags 842891 + confirmed pending
Bug #842891 [src:libimage-info-perl] libimage-info-perl: XXE in SVG files
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#773205: libatomic-ops-dev: FTBFS on mips64el

[Tobias Hansen]

Hi Ian,

the response on the upstream bug report looks like it could take a while
with the new release. With regard to the upcoming freeze, could you
please apply the patches so that the package can migrate to testing?

Best,
Tobias

On Tue, 1 Nov 2016 11:23:19 +1100 Ian Wienand  wrote:
> I'm sorry about this. I must have misread the history of that branch
> 
> My preference is to be in sync with upstream, so I have asked if we
> can get this in a 7.4.5 release [1]
> 
> If no response, or not possible, I'll add these back in
> 
> Thanks,
> 
> -i
> 
> [1] https://github.com/ivmai/libatomic_ops/issues/20
> 
> On Fri, Oct 28, 2016 at 8:31 PM, James Cowgill  wrote:
> > Control: found -1 7.4.4-1
> > Control: severity -1 serious
> >
> > Hi,
> >
> > In 7.4.4-1 the patches adding mips64el support were removed from the
> > package. While they've applied upstream in the 'master' branch not all
> > of them were applied to the 'release-7_4' branch and libatomic-ops FTBFS
> > on mips64el again.
> >
> > These have been applied to 7.4.4-1 (which is good):
> >  0002-Remove-inclusion-of-acquire_release_volatile.h-on-mi.patch
> >  0003-Minor-fix-of-code-alignment-in-mips-AO_compare_and_s.patch
> >
> > Please reapply these patches from 7.4.2-3:
> >  0001-Use-LLD-and-SCD-instructions-on-mips64.patch
> >  0004-Support-n32-ABI-for-mips64.patch
> >
> > Thanks,
> > James
> >
> 
> 

Processed: Re: dependency formats are not converted

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #840207 [npm2deb] dependency formats are not converted
Severity set to 'important' from 'grave'

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

Bug#840207: dependency formats are not converted

[Pirate Praveen]

Control: severity -1 important

On Sun, 9 Oct 2016 20:36:06 +0530 Pirate Praveen  wrote:
> severity: grave
> justification: it breaks build

Only affects newly created packages



signature.asc
Description: OpenPGP digital signature

Bug#843024: libqpid-proton8-dev: missing Breaks+Replaces: libqpid-proton2-dev

[Andreas Beckmann]

Package: libqpid-proton8-dev
Version: 0.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libqpid-proton8-dev.
  Preparing to unpack .../1-libqpid-proton8-dev_0.14.0-2_amd64.deb ...
  Unpacking libqpid-proton8-dev (0.14.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/proton/cid.h', which is also in package 
libqpid-proton2-dev 0.10-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb


cheers,

Andreas


libqpid-proton2-dev=0.10-2_libqpid-proton8-dev=0.14.0-2.log.gz
Description: application/gzip

Bug#828378: marked as done (libapache2-mod-auth-cas: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 09:20:03 +
with message-id 
and subject line Bug#828378: fixed in libapache2-mod-auth-cas 1.1-2
has caused the Debian Bug report #828378,
regarding libapache2-mod-auth-cas: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-auth-cas
Version: 1.0.9.1-4
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libapache2-mod-auth-cas_1.0.9.1-4_amd64-20160529-1438

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-auth-cas
Source-Version: 1.1-2

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

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated libapache2-mod-auth-cas 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 08:41:34 +
Source: libapache2-mod-auth-cas
Binary: libapache2-mod-auth-cas
Architecture: source amd64
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: CAS packaging team 
Changed-By: Thijs Kinkhorst 
Description:
 libapache2-mod-auth-cas - CAS authentication module for Apache2
Closes: 828378
Changes:
 libapache2-mod-auth-cas (1.1-2) unstable; urgency=medium
 .
   * Update configure for OpenSSL 1.1 (closes: #828378).
   * Add libpcre3-dev build-depends.
Checksums-Sha1:
 981ef4a5d1cf42139c15c74c6c8df9321697c11a 1893 libapache2-mod-auth-cas_1.1-2.dsc
 36d1b5e8862cb74940221fd71c903fec05bdf62f 7712 
libapache2-mod-auth-cas_1.1-2.debian.tar.xz
 a5dd72fbd5c3fb33928905fe3ec7f0ed91146d2f 52226 
libapache2-mod-auth-cas-dbgsym_1.1-2_amd64.deb
 7667f571916947b3df4864acdacf4da2dfb4684b 35436 
libapache2-mod-auth-cas_1.1-2_amd64.deb
Checksums-Sha256:
 3b8ad854a41245157faabd45a7c7e65048a4c5347c25f08085302a21baf313dc 1893 
libapache2-mod-auth-cas_1.1-2.dsc
 2550f0805f53cf599d3d082949b3a24247cbfe4ae610dbe4980159f0d35ba974 7712 
libapache2-mod-auth-cas_1.1-2.debian.tar.xz
 9f3d7873a6090b5c613dffebbe76f299e611f56213d94ce7300cca8db892827d 52226 
libapache2-mod-auth-cas-dbgsym_1.1-2_amd64.deb
 ce9df96039a2e71d03179bdfeb111a0e1a748e4b4879d398d080947b9e6f5096 35436 
libapache2-mod-auth-cas_1.1-2_amd64.deb
Files:
 9764182f8456d40715237ba5c1218447 1893 httpd extra 
libapache2-mod-auth-cas_1.1-2.dsc
 6a5b76930df41fb43ab869e05e2b3e7a 7712 httpd extra 
libapache2-mod-auth-cas_1.1-2.debian.tar.xz
 85dedb9491aea48540a03de258a20ceb 52226 debug extra 
libapache2-mod-auth-cas-dbgsym_1.1-2_amd64.deb
 e2ea4283daf9b2741a7db53e8a2d96e5 35436 httpd extra 
libapache2-mod-auth-cas_1.1-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJYGvtRAAoJEFb2GnlAHawEFYkH/iNlOs1RWcIduZAVnOS1hfZq
G+5xT6ihiJowa+1OklylLXtTsMxzW7jaCKD45a1Pq/MxrlRRyJ8LAajc2y5o8bre
i5HnwSt66ZVdDIGGLGG+DN2btB4E05maQR2VLpvmiIS87r0OtaWnsCAyl5e831ln
bIbyOr6WwOyVWR0XSaM2nJ6mwAIfQ27K2GsNiHRC4cTOjKqF9OP3d2K/bJbzLoIa
vB1PmuFuIuZd2YKvcVhA95J1E1OD+f66TDJPBfzAx6Ea07Q5zcNmjDMPtAgyBaq6
Sl5XzycERmLgXuh/vcE9ayxbQZXMhUupi01dDCPUQHVqtfA++ZiPXgRfiuFlPts=
=tgk9
-END PGP SIGNATURE End Message ---

Bug#843027: libc++abi-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/c++/v1/cxxabi.h

[Andreas Beckmann]

Package: libc++abi-dev
Version: 3.9.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libc++abi-dev:amd64.
  Preparing to unpack .../libc++abi-dev_3.9.0-2_amd64.deb ...
  Unpacking libc++abi-dev:amd64 (3.9.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libc++abi-dev_3.9.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/c++/v1/cxxabi.h', which is also in package 
libc++-dev:amd64 3.5-2
  Processing triggers for libc-bin (2.19-18+deb8u6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libc++abi-dev_3.9.0-2_amd64.deb


cheers,

Andreas


libc++-dev=3.5-2_libc++abi-dev=3.9.0-2.log.gz
Description: application/gzip

Bug#828393: marked as done (libevent: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 09:20:08 +
with message-id 
and subject line Bug#828393: fixed in libevent 2.0.21-stable-2.1
has caused the Debian Bug report #828393,
regarding libevent: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libevent
Version: 2.0.21-stable-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libevent_2.0.21-stable-2_amd64-20160529-1440

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libevent
Source-Version: 2.0.21-stable-2.1

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

Debian distribution maintenance software
pp.
Helmut Grohne  (supplier of updated libevent package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Nov 2016 08:43:46 +0100
Source: libevent
Binary: libevent-dev libevent-dbg libevent-2.0-5 libevent-core-2.0-5 
libevent-extra-2.0-5 libevent-pthreads-2.0-5 libevent-openssl-2.0-5
Architecture: source
Version: 2.0.21-stable-2.1
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Helmut Grohne 
Description:
 libevent-2.0-5 - Asynchronous event notification library
 libevent-core-2.0-5 - Asynchronous event notification library (core)
 libevent-dbg - Asynchronous event notification library (debug symbols)
 libevent-dev - Asynchronous event notification library (development files)
 libevent-extra-2.0-5 - Asynchronous event notification library (extra)
 libevent-openssl-2.0-5 - Asynchronous event notification library (openssl)
 libevent-pthreads-2.0-5 - Asynchronous event notification library (pthreads)
Closes: 828393
Changes:
 libevent (2.0.21-stable-2.1) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Non-maintainer upload.
 .
   [ Kurt Roeckx ]
   * Add openssl_1.1.patch. Closes: #828393
Checksums-Sha1:
 cdef395042858d80a31160b0b2afc78a04284b20 2400 libevent_2.0.21-stable-2.1.dsc
 3efb9adc238026e37a91c6ada848cde025d74bc9 12352 
libevent_2.0.21-stable-2.1.debian.tar.xz
Checksums-Sha256:
 01f74091b5d2fdf96ca24716f3a77496222fa8532f9e6c01779def03fc1f0823 2400 
libevent_2.0.21-stable-2.1.dsc
 aba684c33027324f0e45c87af018573fd29e5806063cb5f8bdd63dbaaf0567e8 12352 
libevent_2.0.21-stable-2.1.debian.tar.xz
Files:
 1d0d052dee12cf25c603c06188ef4554 2400 libs optional 
libevent_2.0.21-stable-2.1.dsc
 380cc06acbea9a135225a5ac40f7a52b 12352 libs optional 
libevent_2.0.21-stable-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYGuvgAAoJEC0aqs8kRERCOx0QAJrq/mNf+0XWpis0GXOYYUr/
MiMxOcmGvch+5R9zPYKs4QtSLxp6ogMpPTZLa5T7kYUor8nQGsBN0NhQR7ugvOHz
Dhx7d1AEtSsKEHNq998WVnNr7bPUsGEDCA/nwNDMwn0V5f17nx7GumYszYYl/DYZ
7p3CtmeNYLLXOn7L/DPzXkne4dH760gjx4LLvhS3mPamLd3rFP9PCTG4d6wRlyfA
itYjyGCdeURpctDL36DOr+yPefI2QPrilWrmaJRVC96T0t2SaUsyKUtKunB7vBU3
lSO2YmHKLle4v+5XvIZqPQ1qZoM6FdkcmYCmyiP47LrJ0ciR6ANZBkB87z8Vda5B
L55wyB20aPqGR+YFAfEdS6xrUJ+/uNcw6hfcezBt4v42PEtFr8Tdwf5kWZqfPDvC
NspS97DshvIU2NTc0TYL4pC05gHCjYGfgxJJxSaslxvBhgGZMSycLsHSQMYe4bGL
TSPkZS9fVcBH6jah+ZNGyOcGluGe0xgxLf6MfQZo7Qwg/oZd3MBVFQklFFm70MLA
6V+YygnQ4tIy62ZpnC0x36pxIW195PG1NsP6HViTVJVM7hvLWWL1BDkL5NzqOBnz
SNZScUN3NJHblUMHpoI0tocG0EVdPa9ifQVRAtLl+1PCsa/wiwFvNSTCYcbxgs0Y
udjq0k9OKE047htOx3s+
=8dCw
-END PGP SIGNATURE End Message ---

Bug#843028: dovecot-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/aclocal/dovecot-pigeonhole.m4

[Andreas Beckmann]

Package: dovecot-dev
Version: 1:2.2.26.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package dovecot-dev.
  Preparing to unpack .../1-dovecot-dev_1%3a2.2.26.0-1_amd64.deb ...
  Unpacking dovecot-dev (1:2.2.26.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-cbXNE2/1-dovecot-dev_1%3a2.2.26.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/aclocal/dovecot-pigeonhole.m4', which is 
also in package dovecot-core 1:2.2.25-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-cbXNE2/1-dovecot-dev_1%3a2.2.26.0-1_amd64.deb


cheers,

Andreas


dovecot-core=1%2.2.25-1_dovecot-dev=1%2.2.26.0-1.log.gz
Description: application/gzip

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 09:24:06 +
with message-id 
and subject line Bug#825083: fixed in sysbench 0.4.12-1.2
has caused the Debian Bug report #825083,
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.)


-- 
825083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysbench
Version: 0.4.12-1.1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch
Control: block -1 by 797260

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. Please note that this requires
autoreconf so will only work if applied after my patch for bug 797260.

Thanks,

Robie Basak
Debian MySQL maintainers team
Ubuntu developer
Author: Robie Basak 
Description: use libmysqlclient instead of libmysqlclient_r
 The former supersedes the latter which no longer exists in MySQL 5.7.
Forwarded: no
Last-Update: 2016-04-14

--- a/acinclude.m4
+++ b/acinclude.m4
@@ -51,7 +51,7 @@
 ac_cv_mysql_libs=`echo ${ac_cv_mysql_libs} | sed -e 's/.libs$//' \
   -e 's+.libs/$++'`
 AC_CACHE_CHECK([MySQL libraries], [ac_cv_mysql_libs], 
[ac_cv_mysql_libs=""])
-MYSQL_LIBS="-L$ac_cv_mysql_libs -lmysqlclient_r"
+MYSQL_LIBS="-L$ac_cv_mysql_libs -lmysqlclient"
 fi
 
 # If some path is missing, try to autodetermine with mysql_config
@@ -82,8 +82,7 @@
 if test [ -z "$ac_cv_mysql_libs" ]
 then
 AC_MSG_CHECKING(MySQL linker flags)
-MYSQL_LIBS=`${mysqlconfig} --libs | sed -e \
-'s/-lmysqlclient /-lmysqlclient_r /' -e 
's/-lmysqlclient$/-lmysqlclient_r/'`
+MYSQL_LIBS=`${mysqlconfig} --libs`
 AC_MSG_RESULT($MYSQL_LIBS)
 fi
 fi
--- End Message ---
--- Begin Message ---
Source: sysbench
Source-Version: 0.4.12-1.2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 05:28:52 +0200
Source: sysbench
Binary: sysbench
Architecture: source
Version: 0.4.12-1.2
Distribution: unstable
Urgency: medium
Maintainer: Hendrik Frenzel 
Changed-By: Fathi Boudra 
Description:
 sysbench   - Cross-platform and multi-threaded benchmark tool
Closes: 790475 797260 825083
Changes:
 sysbench (0.4.12-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/{rules,control}:
 - drop DEB_AUTO_UPDATE and use dh-autoreconf instead to fix FTBFS.
   This should stop needing packaging updates every time the archive
   verisons of autotools change. (Closes: #797260)
 - drop conditional build-depend on libmysqlclient15-dev and
   build-depend on default-libmysqlclient-dev instead. (Closes: #790475)
   * d/p/libmysqlclient_r: link against libmysqlclient instead of
 libmysqlclient_r. The former supersedes the latter which no longer
 exists in MySQL 5.7. (Closes: #825083)
Checksums-Sha1:
 9fe5f133f92fbc43462df5d231e4471913fc4d4c 1964 sysbench_0.4.12-1.2.dsc
 a2da9dc2fc85a82bc9d470c85114eb64b911e7a8 11088 
sysbench_0.4.12-1.2.debian.tar.xz
Checksums-Sha256:
 9b0a723908dd3554d5f08a2b46c52c7215fafa3680b20461e16f7578fb05c3c6 1964 
sysbench_0.4.12-1.2.dsc
 640567ac88ec1147e33a2b6d3666217855c5

Bug#797260: marked as done (sysbench: FTBFS: aclocal-1.14: not found)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 09:24:06 +
with message-id 
and subject line Bug#797260: fixed in sysbench 0.4.12-1.2
has caused the Debian Bug report #797260,
regarding sysbench: FTBFS: aclocal-1.14: 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.)


-- 
797260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysbench
Version: 0.4.12-1.1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

cd . && libtoolize -c -f
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: copying file `config/ltmain.sh'
libtoolize: You should add the contents of the following files to `aclocal.m4':
libtoolize:   `/usr/share/aclocal/libtool.m4'
libtoolize:   `/usr/share/aclocal/ltoptions.m4'
libtoolize:   `/usr/share/aclocal/ltversion.m4'
libtoolize:   `/usr/share/aclocal/ltsugar.m4'
libtoolize:   `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
cd . && aclocal-1.14 
/bin/sh: 1: aclocal-1.14: not found
/usr/share/cdbs/1/class/autotools-files.mk:62: recipe for target 
'debian/stamp-autotools-files' failed
make: *** [debian/stamp-autotools-files] Error 127
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/sysbench.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: sysbench
Source-Version: 0.4.12-1.2

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

Debian distribution maintenance software
pp.
Fathi Boudra  (supplier of updated sysbench package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 05:28:52 +0200
Source: sysbench
Binary: sysbench
Architecture: source
Version: 0.4.12-1.2
Distribution: unstable
Urgency: medium
Maintainer: Hendrik Frenzel 
Changed-By: Fathi Boudra 
Description:
 sysbench   - Cross-platform and multi-threaded benchmark tool
Closes: 790475 797260 825083
Changes:
 sysbench (0.4.12-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/{rules,control}:
 - drop DEB_AUTO_UPDATE and use dh-autoreconf instead to fix FTBFS.
   This should stop needing packaging updates every time the archive
   verisons of autotools change. (Closes: #797260)
 - drop conditional build-depend on libmysqlclient15-dev and
   build-depend on default-libmysqlclient-dev instead. (Closes: #790475)
   * d/p/libmysqlclient_r: link against libmysqlclient instead of
 libmysqlclient_r. The former supersedes the latter which no longer
 exists in MySQL 5.7. (Closes: #825083)
Checksums-Sha1:
 9fe5f133f92fbc43462df5d231e4471913fc4d4c 1964 sysbench_0.4.12-1.2.dsc
 a2da9dc2fc85a82bc9d470c85114eb64b911e7a8 11088 
sysbench_0.4.12-1.2.debian.tar.xz
Checksums-Sha256:
 9b0a723908dd3554d5f08a2b46c52c7215fafa3680b20461e16f7578fb05c3c6 1964 
sysbench_0.4.12-1.2.dsc
 640567ac88ec1147e33a2b6d3666217855c5d4f11ae0705196def2c6cf99ded7 11088 
sysbench_0.4.12-1.2.debian.tar.xz
Files:
 926dfc7f3c001ab0e7c32c666a2b3bd1 1964 misc extra sysbench_0.4.12-1.2.dsc
 7188e0564ecca24fa88297469bc2e98c 11088 misc extra 
sysbench_0.4.12-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYGvZyAAoJELRIkN7ePJvAs9QP/0rPBkHHK/U/Om6y53ltU5iw
IQzIfmWXKEFLnYXewRJxhghUK3M4mpe9374x+tIEqMISATVhbg4zxp6eyOJ+9J9j
ilQm7EbARrYOx8X7mu/JS5L0HmVtZajRH0uyaUjhuAE0u1rJFBhyxs8/IL4VVjX8
xUlNtc87lt3tLVE5ZiS7i4P01eOiFekwLVGGsGgMSOjvmyglIQBRzZOJE9RvzI94
16wMn7GUxTfGaGvjNxE0Y2bhDljUn8iMrqnYAVy8341amTmT+qNQKzk6E+0LgA3w
+

Bug#843030: snap-templates: fails to upgrade from 'testing' - trying to overwrite /usr/bin/snap-framework

[Andreas Beckmann]

Package: snap-templates
Version: 1.0.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package snap-templates.
  Preparing to unpack .../1-snap-templates_1.0.0.0-2_amd64.deb ...
  Unpacking snap-templates (1.0.0.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GuJr0J/1-snap-templates_1.0.0.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/snap-framework', which is also in package 
libghc-snap-dev 0.14.0.7-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-GuJr0J/1-snap-templates_1.0.0.0-2_amd64.deb


cheers,

Andreas


libghc-snap-dev=0.14.0.7-2_snap-templates=1.0.0.0-2.log.gz
Description: application/gzip

Processed: bug 828590 is forwarded to https://github.com/unbit/uwsgi/issues/1395

[Debian Bug Tracking System]

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

> forwarded 828590 https://github.com/unbit/uwsgi/issues/1395
Bug #828590 [src:uwsgi] uwsgi: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 'https://github.com/unbit/uwsgi/issues/1395'.
> thanks
Stopping processing here.

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

Bug#843031: golang-github-nsf-termbox-go-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/gocode/src/github.com/nsf/termbox-go/_demos/editbox.go

[Andreas Beckmann]

Package: golang-github-nsf-termbox-go-dev
Version: 0.0~git20160914-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package golang-github-nsf-termbox-go-dev.
  Preparing to unpack 
.../golang-github-nsf-termbox-go-dev_0.0~git20160914-1_all.deb ...
  Unpacking golang-github-nsf-termbox-go-dev (0.0~git20160914-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-nsf-termbox-go-dev_0.0~git20160914-1_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/nsf/termbox-go/_demos/editbox.go', which is 
also in package golang-termbox-dev 0.0~git20140119-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-nsf-termbox-go-dev_0.0~git20160914-1_all.deb


cheers,

Andreas


golang-termbox-dev=0.0~git20140119-1_golang-github-nsf-termbox-go-dev=0.0~git20160914-1.log.gz
Description: application/gzip

Bug#831833: [Debian-med-packaging] Bug#831833: Tagged as fixed-upstream - do you intend to upload?

[Charles Plessy]

> On Wed, Nov 02, 2016 at 09:03:45PM +0900, Charles Plessy wrote:
> > 
> > I was hoping that Upstream would make a new release with the fix :(
> > 
> > So one would need to check if the following commit would be enough as a 
> > patch...
> > 
> > https://github.com/arq5x/bedtools2/commit/be2633d4951328264611e4cabc65e12fa8fef1cd

Hi again,

it turns out that the patch representing the commit be2633d fixing the issue
can not be applied alone; the package fails to build.

Then, I tried to look for other commits to apply in order to make the patched
package buildable, and I realised that first, there has been only 16 commits in
total since the last upstream release, and second, some of these commits do fix
other bugs, less severe, but real bugs.  None of them introduce novel
unreleased features.

So I am tempted to propose to distribute the current contents of Upstream's
master branch in Squeeze.  Technically, I can:

 - Just drop a big monolithic patch in debian/patches, or
 - drop the patches produced by `git format-patch v2.26.0, or
 - make a new tarball, version 2.26.0-19-g6bf23c4 (`git describe --tags`).

What do other people think about this ?

Have a nice day,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Bug#843028: dovecot-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/aclocal/dovecot-pigeonhole.m4

[Andreas Beckmann]

Followup-For: Bug #843028
Control: affects -1 + dovecot-imapd dovecot-ldap dovecot-sieve

Hi,

more dovecot related file overwrite problems:

  Preparing to unpack .../1-dovecot-sieve_1%3a2.2.26.0-1_amd64.deb ...
  Unpacking dovecot-sieve (1:2.2.26.0-1) over (1:2.2.25-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7oCUjf/1-dovecot-sieve_1%3a2.2.26.0-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so', 
which is also in package dovecot-imapd 1:2.2.25-1

  Preparing to unpack .../1-dovecot-ldap_1%3a2.2.26.0-1_amd64.deb ...
  Unpacking dovecot-ldap (1:2.2.26.0-1) over (1:2.2.25-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-hv2MZP/1-dovecot-ldap_1%3a2.2.26.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/dovecot/libdovecot-ldap.so.0.0.0', which is 
also in package dovecot-core 1:2.2.25-1


Andreas

Processed: Re: dovecot-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/aclocal/dovecot-pigeonhole.m4

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + dovecot-imapd dovecot-ldap dovecot-sieve
Bug #843028 [dovecot-dev] dovecot-dev: fails to upgrade from 'testing' - trying 
to overwrite /usr/share/aclocal/dovecot-pigeonhole.m4
Added indication that 843028 affects dovecot-imapd, dovecot-ldap, and 
dovecot-sieve

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

Bug#841677: mysql-connector-python: CVE-2016-5598

[Guido Günther]

Hi,
On Sat, Oct 22, 2016 at 08:27:56AM +0200, Salvatore Bonaccorso wrote:
> Source: mysql-connector-python
> Version: 2.1.3-1
> Severity: grave
> Tags: security upstream
> 
> Hi,
> 
> the following vulnerability was published for mysql-connector-python.
> 
> CVE-2016-5598[0].
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2016-5598
> [1] 
> http://www.oracle.com/technetwork/security-advisory/cpuoct2016verbose-2881725.html#MSQL
> 
> Please adjust the affected versions in the BTS as needed.

While 2.1.4 has other changes the only change in 2.0.5 is the CVE
fix. It seems this is caused by format string expansion in
_format_params_dict. I've attached the diff between 2.0.4 → 2.0.5. I
think wheezy is affected since it uses pythons format expansion there
but I'd be glad about a second opinion.
Cheers,
 -- Guido
diff --git a/CHANGES.txt b/CHANGES.txt
index 7ee20de..fbdca18 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,11 +3,16 @@ MySQL Connector/Python 2.0 - Release Notes & Changes
 
 
 MySQL Connector/Python
-Copyright (c) 2009, 2015, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2009, 2016, Oracle and/or its affiliates. All rights reserved.
 
 Full release notes:
  http://dev.mysql.com/doc/relnotes/connector-python/en/
 
+
+v2.0.5
+==
+- BUG22529828: Fix potencial SQL injection
+
 v2.0.4
 ==
 
diff --git a/PKG-INFO b/PKG-INFO
index de8b3a5..46adcb2 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 1.0
 Name: mysql-connector-python
-Version: 2.0.4
+Version: 2.0.5
 Summary: MySQL driver written in Python
 Home-page: http://dev.mysql.com/doc/connector-python/en/index.html
 Author: Oracle and/or its affiliates
diff --git a/README.txt b/README.txt
index 2f88034..99be628 100644
--- a/README.txt
+++ b/README.txt
@@ -3,7 +3,7 @@ MySQL Connector/Python 2.0
 ==
 
 MySQL Connector/Python
-Copyright (c) 2009, 2015, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2009, 2016, Oracle and/or its affiliates. All rights reserved.
 
 License information can be found in the LICENSE.txt file.
 
@@ -28,7 +28,7 @@ doubt, this particular copy of the software is released
 under the version 2 of the GNU General Public License.
 MySQL Connector/Python is brought to you by Oracle.
 
-Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2011, 2016, Oracle and/or its affiliates. All rights reserved.
 
 License information can be found in the LICENSE.txt file.
 
diff --git a/lib/mysql/connector/cursor.py b/lib/mysql/connector/cursor.py
index 3e6a2b4..b9bfd9a 100644
--- a/lib/mysql/connector/cursor.py
+++ b/lib/mysql/connector/cursor.py
@@ -1,5 +1,5 @@
 # MySQL Connector/Python - MySQL driver written in Python.
-# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2009, 2016, Oracle and/or its affiliates. All rights reserved.
 
 # MySQL Connector/Python is licensed under the terms of the GPLv2
 # , like most
@@ -29,6 +29,7 @@ import re
 import weakref
 
 from . import errors
+from .catch23 import PY2
 
 SQL_COMMENT = r"\/\*.*?\*\/"
 RE_SQL_COMMENT = re.compile(
@@ -42,6 +43,14 @@ RE_SQL_INSERT_STMT = re.compile(
 re.I | re.M | re.S)
 RE_SQL_INSERT_VALUES = re.compile(r'.*VALUES\s*(\(.*\)).*', re.I | re.M | re.S)
 RE_PY_PARAM = re.compile(b'(%s)')
+RE_PY_MAPPING_PARAM = re.compile(
+br'''
+%
+\((?P[^)]+)\)
+(?P[diouxXeEfFgGcrs%])
+''',
+re.X
+)
 RE_SQL_SPLIT_STMTS = re.compile(
 b''';(?=(?:[^"'`]*["'`][^"'`]*["'`])*[^"'`]*$)''')
 RE_SQL_FIND_PARAM = re.compile(
@@ -73,6 +82,35 @@ class _ParamSubstitutor(object):
 return len(self.params) - self.index
 
 
+def _bytestr_format_dict(bytestr, value_dict):
+"""
+>>> _bytestr_format_dict(b'%(a)s', {b'a': b'foobar'})
+b'foobar
+>>> _bytestr_format_dict(b'%%(a)s', {b'a': b'foobar'})
+b'%%(a)s'
+>>> _bytestr_format_dict(b'%%%(a)s', {b'a': b'foobar'})
+b'%%foobar'
+>>> _bytestr_format_dict(b'%(x)s %(y)s',
+...  {b'x': b'x=%(y)s', b'y': b'y=%(x)s'})
+b'x=%(y)s y=%(x)s'
+"""
+def replace(matchobj):
+value = None
+groups = matchobj.groupdict()
+if groups["conversion_type"] == b"%":
+value = b"%"
+if groups["conversion_type"] == b"s":
+key = groups["mapping_key"].encode("utf-8") \
+  if PY2 else groups["mapping_key"]
+value = value_dict[key]
+if value is None:
+raise ValueError("Unsupported conversion_type: {0}"
+ "".format(groups["conversion_type"]))
+return value.decode("utf-8") if PY2 else value
+

Bug#842982: lua-sec update prevents ssl connections with prosody

[Adrien CLERC]

Reply-To: 842...@bugs.debian.org

This is the same as #842906.

Adrien

Bug#832340: marked as done (poco: FTBFS: undefined reference to `_pcre_ucd_...)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:02:17 +
with message-id 
and subject line Bug#832340: fixed in poco 1.7.6+dfsg1-1
has caused the Debian Bug report #832340,
regarding poco: FTBFS: undefined reference to `_pcre_ucd_...
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.)


-- 
832340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poco
Version: 1.4.6p1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

poco/experimental FTBFS:

/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_stage1'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_records'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucp_gentype'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_stage2'
collect2: error: ld returned 1 exit status
/build/poco-1.4.6p1/build/rules/exec:58: recipe for target 
'/build/poco-1.4.6p1/PageCompiler/bin/Linux/x86_64/cpspc' failed
make[3]: *** [/build/poco-1.4.6p1/PageCompiler/bin/Linux/x86_64/cpspc] Error 1
make[3]: Leaving directory '/build/poco-1.4.6p1/PageCompiler'
Makefile:152: recipe for target 'PageCompiler-libexec' failed
make[2]: *** [PageCompiler-libexec] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: poco
Source-Version: 1.7.6+dfsg1-1

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated poco 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, 02 Nov 2016 08:23:48 +0100
Source: poco
Binary: libpoco-dev libpococrypto46 libpocodata46 libpocomongodb46 
libpocodatamysql46 libpocodataodbc46 libpocodatasqlite46 libpocofoundation46 
libpoconet46 libpoconetssl46 libpocoutil46 libpocoxml46 libpocozip46
Architecture: source amd64
Version: 1.7.6+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt 
Changed-By: Jochen Sprickerhof 
Description:
 libpoco-dev - C++ Portable Components (POCO) Development files
 libpococrypto46 - C++ Portable Components (POCO) Crypto library
 libpocodata46 - C++ Portable Components (POCO) Data library
 libpocodatamysql46 - C++ Portable Components (POCO) Data MySQL library
 libpocodataodbc46 - C++ Portable Components (POCO) ODBC library
 libpocodatasqlite46 - C++ Portable Components (POCO) Data SQLite library
 libpocofoundation46 - C++ Portable Components (POCO) Foundation library
 libpocomongodb46 - C++ Portable Components (POCO) Data MySQL library
 libpoconet46 - C++ Portable Components (POCO) Network library
 libpoconetssl46 - C++ Portable Components (POCO) Network library with SSL
 libpocoutil46 - C++ Portable Components (POCO) Util library
 libpocoxml46 - C++ Portable Components (POCO) XML library
 libpocozip46 - C++ Portable Components (POCO) Zip library
Closes: 671477 677039 786498 803642 828507 832340
Changes:
 poco (1.7.6+dfsg1-1) experimental; urgency=medium
 .
   * Update watch file
   * New upstream version 1.7.6+dfsg1 (Closes: #832340, #671477, #677039,
 #786498)
   * rebase patches
   * Remove dbg packages
   * Remove replaces for libpoco5-dev (package not even in old-stable)
   * Move to debhelper compat 10
   * Update standards version (no changes needed)
   * Update homepage and vcs tags (Closes: #803642)
   * Update build dependencies
   * Update lib names due to Soname change
   * Add new libraries
   * Update copyright file
   * Remove JSON lib, as it's not DFSG-complaint
   * Add lintian overrides
   * Add patch for OpenSSL 1.1.0 (Closes: #828507)
   * Add myself to uploaders
Checksums-Sha1:
 fa961538d5a8c2022c99f742d7c3cffe9d2ab648 2841 poco_1.7.6+dfsg1-1.dsc
 97ffb4b371e3112bae8b3f7cc1577bf9f8d44bfa 4249425 poco_1.7.6+dfsg1.orig.tar.bz2
 3d9f3654b4041ee89b55aeb5303b40c7d995eb00 13620 poco_1.7.6+dfsg1-1.debian.tar.xz
 457744869532a0dddf515750525e

Bug#828507: marked as done (poco: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:02:17 +
with message-id 
and subject line Bug#828507: fixed in poco 1.7.6+dfsg1-1
has caused the Debian Bug report #828507,
regarding poco: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poco
Version: 1.3.6p1-5.1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/poco_1.3.6p1-5.1_amd64-20160529-1509

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: poco
Source-Version: 1.7.6+dfsg1-1

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated poco 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, 02 Nov 2016 08:23:48 +0100
Source: poco
Binary: libpoco-dev libpococrypto46 libpocodata46 libpocomongodb46 
libpocodatamysql46 libpocodataodbc46 libpocodatasqlite46 libpocofoundation46 
libpoconet46 libpoconetssl46 libpocoutil46 libpocoxml46 libpocozip46
Architecture: source amd64
Version: 1.7.6+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt 
Changed-By: Jochen Sprickerhof 
Description:
 libpoco-dev - C++ Portable Components (POCO) Development files
 libpococrypto46 - C++ Portable Components (POCO) Crypto library
 libpocodata46 - C++ Portable Components (POCO) Data library
 libpocodatamysql46 - C++ Portable Components (POCO) Data MySQL library
 libpocodataodbc46 - C++ Portable Components (POCO) ODBC library
 libpocodatasqlite46 - C++ Portable Components (POCO) Data SQLite library
 libpocofoundation46 - C++ Portable Components (POCO) Foundation library
 libpocomongodb46 - C++ Portable Components (POCO) Data MySQL library
 libpoconet46 - C++ Portable Components (POCO) Network library
 libpoconetssl46 - C++ Portable Components (POCO) Network library with SSL
 libpocoutil46 - C++ Portable Components (POCO) Util library
 libpocoxml46 - C++ Portable Components (POCO) XML library
 libpocozip46 - C++ Portable Components (POCO) Zip library
Closes: 671477 677039 786498 803642 828507 832340
Changes:
 poco (1.7.6+dfsg1-1) experimental; urgency=medium
 .
   * Update watch file
   * New upstream version 1.7.6+dfsg1 (Closes: #832340, #671477, #677039,
 #786498)
   * rebase patches
   * Remove dbg packages
   * Remove replaces for libpoco5-dev (package not even in old-stable)
   * Move to debhelper compat 10
   * Update standards version (no changes needed)
   * Update homepage and vcs tags (Closes: #803642)
   * Update build dependencies
   * Update lib names due to Soname change
   * Add new libraries
   * Update copyright file
   * Remove JSON lib, as it's not DFSG-complaint
   * Add lintian overrides
   * Add patch for OpenSSL 1.1.0 (Closes: #828507)
   * Add myself to uploaders
Checksums-Sha1:
 fa961538d5a8c2022c99f742d7c3cffe9d2ab648 2841 poco_1.7.6+dfsg1-1.dsc
 97ffb4b371e3112bae8b3f7cc1577bf9f8d44bfa 4249425 poco_1.7.6+dfsg1.orig.tar.bz2
 3d9f3654b4041ee89b55aeb5303b40c7d995eb00 13620 poco_1.7.6+dfsg1-1.debian.tar.xz
 457744869532a0dddf515750525e0d0db7491f03 539368 
libpoco-dev_1.7.6+dfsg1-1_amd64.deb
 5e81245727a312e4ba0cbb799ce99059e4c36040 394090 
libpococrypto46-dbgsym_1.7.6+dfsg1-1_amd64.deb
 d2c22faa5a807f46f2db010df0e7c85bd1cd0e60 93610 
libpococrypto46_1

Bug#841470: marked as done (witty: build-depends on firebird2.5-dev, which is no longer available)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:02:22 +
with message-id 
and subject line Bug#841470: fixed in witty 3.3.6+dfsg-1
has caused the Debian Bug report #841470,
regarding witty: build-depends on firebird2.5-dev, which is no longer available
to be marked as done.

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

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


-- 
841470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: witty
Version: 3.3.5+dfsg-1.1
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: witty
Source-Version: 3.3.6+dfsg-1

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

Debian distribution maintenance software
pp.
Pau Garcia i Quiles  (supplier of updated witty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 9 Oct 2016 22:16:40 +0200
Source: witty
Binary: libwt-common libwt40 libwt-dev libwthttp40 libwthttp-dev libwtfcgi40 
libwtfcgi-dev libwttest10 libwttest-dev libwtext40 libwtext-dev libwtdbo40 
libwtdbo-dev libwtdbosqlite40 libwtdbosqlite-dev libwtdbopostgres40 
libwtdbopostgres-dev libwtdbofirebird40 libwtdbofirebird-dev libwtdbomysql40 
libwtdbomysql-dev libwt-dbg libwt-doc witty-examples witty witty-dbg witty-dev 
witty-doc
Architecture: source all amd64
Version: 3.3.6+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Pau Garcia i Quiles 
Changed-By: Pau Garcia i Quiles 
Description:
 libwt-common - C++ library and application server for web applications [common]
 libwt-dbg  - C++ library and application server for web applications [debug]
 libwt-dev  - C++ library and application server for web applications [developm
 libwt-doc  - C++ library and application server for web applications [doc]
 libwt40- C++ library and application server for web applications [runtime]
 libwtdbo-dev - Wt::Dbo ORM library for Wt [development]
 libwtdbo40 - Wt::Dbo ORM library for Wt [runtime]
 libwtdbofirebird-dev - Firebird backend for Wt::Dbo [development]
 libwtdbofirebird40 - Firebird backend for Wt::Dbo [runtime]
 libwtdbomysql-dev - MySQL/MariaDB backend for Wt::Dbo [development]
 libwtdbomysql40 - MySQL/MariaDB backend for Wt::Dbo [runtime]
 libwtdbopostgres-dev - PostgreSQL backend for Wt::Dbo [development]
 libwtdbopostgres40 - PostgreSQL backend for Wt::Dbo [runtime]
 libwtdbosqlite-dev - sqlite3 backend for Wt::Dbo [development]
 libwtdbosqlite40 - sqlite3 backend for Wt::Dbo [runtime]
 libwtext-dev - additional widgets for Wt, based on ExtJS 2.0.x [development]
 libwtext40 - additional widgets for Wt, based on ExtJS 2.0.x [runtime]
 libwtfcgi-dev - FastCGI connector library for Wt [development]
 libwtfcgi40 - FastCGI connector library for Wt [runtime]
 libwthttp-dev - HTTP(S) connector library for Wt [development]
 libwthttp40 - HTTP(S) connector library for Wt [runtime]
 libwttest-dev - test connector library for Wt [development]
 libwttest10 - test connector library for Wt [runtime]
 witty  - C++ library for webapps [runtime] (transition package)
 witty-dbg  - C++ library for webapps [debug] (transition package)
 witty-dev  - C++ library for webapps [devel] (transition package)
 witty-doc  - C++ library for webapps [doc] (transition package)
 witty-examples - C++ library for webapps [examples]
Closes: 831552 841470
Changes:
 witty (3.3.6+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
   * Install DomElement.h and EscapeOStream.h (LP: #1585225)
   * Fix some lintian-overrides 

Bug#833055: Packaging of mongoclient replacement library: mongocxx

[Raphael Hertzog]

Hello Apollon,

mongodb dropped the C++ client driver that it used to provide in
mongodb-dev in favor of https://github.com/mongodb/mongo-cxx-driver

Do you plan (or know someone who plans) to package this one?

Is there ane alternate client library that you recommend?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: bug 833055 is forwarded to https://github.com/unbit/uwsgi/issues/1395

[Debian Bug Tracking System]

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

> forwarded 833055 https://github.com/unbit/uwsgi/issues/1395
Bug #833055 [src:uwsgi] uwsgi: B-D mongodb-dev is no longer built by mongodb
Set Bug forwarded-to-address to 'https://github.com/unbit/uwsgi/issues/1395'.
> thanks
Stopping processing here.

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

Bug#833055: [pkg-uWSGI-devel] Any news on uwsgi bug fixes?

[Raphael Hertzog]

Hi,

On Wed, 28 Sep 2016, Jonas Smedegaard wrote:
> > > https://bugs.debian.org/833055 - B-D mongodb-dev is no longer built by 
> > > mongodb
> > 
> > The mongodb bug is believed fixed locally on my machine (not pushed to 
> > the public git yet).
> 
> Unfortunately that build didn't succeed :-(

What did you try to fix to mongodb bug? I see nothing relevant in git
and besides entirely disabling MongoDB support I don't see what you
could have tried given that the library is gone and that the replacement
library[1] is not packaged in Debian currently AFAIK. I filed an upstream
ticket[2] to get the ball rolling upstream.

[1] https://github.com/mongodb/mongo-cxx-driver
[2] https://github.com/unbit/uwsgi/issues/1396

> I am travelling till the end of the week, so most likely won't find time 
> to dive into this again before monday.

More than a month went by since that monday :-) Do you plan to work on
the package to bring it back into testing?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#773205: marked as done (libatomic-ops-dev: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:22:07 +
with message-id 
and subject line Bug#773205: fixed in libatomic-ops 7.4.4-2
has caused the Debian Bug report #773205,
regarding libatomic-ops-dev: FTBFS on mips64el
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.)


-- 
773205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatomic-ops-dev
Version: 7.4.2-1
Severity: important
Tags: upstream patch

Hi,

libatomic-ops FTBFS on mips64el due to the testsuite hanging. The code
in the mips specific header assumes that sizeof(AO_t) == 4, which isn't
the case on mips64el which is 64-bits.

I've attached a patch to fix this. Instead of using the 32-bit LL and SC
instructions, it uses the 64-bit LLD and SCD instructions when compiled
on mips64.

Thanks,
James

From 80e8ad2494db151fa35843a2908ff7f11d278ce0 Mon Sep 17 00:00:00 2001
From: James Cowgill 
Date: Mon, 15 Dec 2014 14:42:15 +
Subject: [PATCH] Use LLD / SCD instructions on mips64

---
 src/atomic_ops/sysdeps/gcc/mips.h | 54 ++-
 1 file changed, 30 insertions(+), 24 deletions(-)

diff --git a/src/atomic_ops/sysdeps/gcc/mips.h b/src/atomic_ops/sysdeps/gcc/mips.h
index a891de6..83a6bd3 100644
--- a/src/atomic_ops/sysdeps/gcc/mips.h
+++ b/src/atomic_ops/sysdeps/gcc/mips.h
@@ -15,7 +15,6 @@
  * FIXME:  This should probably make finer distinctions.  SGI MIPS is
  * much more strongly ordered, and in fact closer to sequentially
  * consistent.  This is really aimed at modern embedded implementations.
- * It looks to me like this assumes a 32-bit ABI.  -HB
  */
 
 #include "../all_aligned_atomic_load_store.h"
@@ -27,14 +26,24 @@
 /* Data dependence does not imply read ordering.  */
 #define AO_NO_DD_ORDERING
 
+#ifdef __mips64
+# define AO_MIPS_SET_ISA"   .set mips3\n"
+# define AO_MIPS_LL_1(args) "   lld " args "\n"
+# define AO_MIPS_SC(args)   "   scd " args "\n"
+#else
+# define AO_MIPS_SET_ISA"   .set mips2\n"
+# define AO_MIPS_LL_1(args) "   ll " args "\n"
+# define AO_MIPS_SC(args)   "   sc " args "\n"
+# define AO_T_IS_INT
+#endif
+
 #ifdef AO_ICE9A1_LLSC_WAR
   /* ICE9 rev A1 chip (used in very few systems) is reported to */
   /* have a low-frequency bug that causes LL to fail.   */
   /* To workaround, just issue the second 'LL'. */
-# define AO_MIPS_LL_FIX(args_str) \
-  "   ll   " args_str "\n"
+# define AO_MIPS_LL(args) AO_MIPS_LL_1(args) AO_MIPS_LL_1(args)
 #else
-# define AO_MIPS_LL_FIX(args_str) ""
+# define AO_MIPS_LL(args) AO_MIPS_LL_1(args)
 #endif
 
 AO_INLINE void
@@ -42,7 +51,7 @@ AO_nop_full(void)
 {
   __asm__ __volatile__(
   "   .set push   \n"
-  "   .set mips2  \n"
+  AO_MIPS_SET_ISA
   "   .set noreorder  \n"
   "   .set nomacro\n"
   "   sync\n"
@@ -60,13 +69,13 @@ AO_fetch_and_add(volatile AO_t *addr, AO_t incr)
 
   __asm__ __volatile__(
   "   .set push\n"
-  "   .set mips2\n"
+  AO_MIPS_SET_ISA
   "   .set noreorder\n"
   "   .set nomacro\n"
-  "1: ll   %0, %2\n"
-  AO_MIPS_LL_FIX("%0, %2")
+  "1: "
+  AO_MIPS_LL("%0, %2")
   "   addu %1, %0, %3\n"
-  "   sc   %1, %2\n"
+  AO_MIPS_SC("%1, %2")
   "   beqz %1, 1b\n"
   "   nop\n"
   "   .set pop "
@@ -85,13 +94,13 @@ AO_test_and_set(volatile AO_TS_t *addr)
 
   __asm__ __volatile__(
   "   .set push\n"
-  "   .set mips2\n"
+  AO_MIPS_SET_ISA
   "   .set noreorder\n"
   "   .set nomacro\n"
-  "1: ll   %0, %2\n"
-  AO_MIPS_LL_FIX("%0, %2")
+  "1: "
+  AO_MIPS_LL("%0, %2")
   "   move %1, %3\n"
-  "   sc   %1, %2\n"
+  AO_MIPS_SC("%1, %2")
   "   beqz %1, 1b\n"
   "   nop\n"
   "   .set pop "
@@ -114,14 +123,14 @@ AO_test_and_set(volatile AO_TS_t *addr)
 
 __asm__ __volatile__(
 "   .set push   \n"
-"   .set mips2  \n"
+AO_MIPS_SET_ISA
 "   .set noreorder  \n"
 "   .set nomacro\n"
-"1: ll  %0, %1  \n"
-AO_MIPS_LL_FIX("%0, %1")
+"1: "
+AO_MIPS_LL("%0, %1")
 "   bne %0, %4, 2f  \n"
 "move   %0, %3  \n"
-"   sc  %0, %1  \n"
+AO_MIPS_SC("%0, %1")
 "   .set pop\n"
 "   beqz%0, 1b  \n"
  

Bug#839379: marked as done (yelp: FTBFS: segmentation fault)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:25:07 +
with message-id 
and subject line Bug#839379: fixed in webkit2gtk 2.14.2-1
has caused the Debian Bug report #839379,
regarding yelp: FTBFS: segmentation fault
to be marked as done.

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

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


-- 
839379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yelp
Version: 3.22.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 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[5]: Entering directory '/<>/docs/libyelp'
> if test "/<>/docs/libyelp" != "/<>/docs/libyelp" ; 
> then \
> files=`echo version.xml  libyelp-docs.xml libyelp-sections.txt 
> libyelp-overrides.txt libyelp.types`; \
> if test "x$files" != "x" ; then \
> for file in $files ; do \
> destdir=`dirname /<>/docs/libyelp/$file`; \
> test -d "$destdir" || mkdir -p "$destdir"; \
> test -f /<>/docs/libyelp/$file && \
> cp -pf /<>/docs/libyelp/$file 
> /<>/docs/libyelp/$file || true; \
> done; \
> fi; \
> fi
> touch setup-build.stamp
> _source_dir='' ; \
> for i in ../../libyelp ; do \
> _source_dir="${_source_dir} --source-dir=$i" ; \
> done ; \
> gtkdoc-scan --module=libyelp --ignore-headers="yelp-common-types.h 
> yelp-debug.h yelp-types.h ../../libyelp/yelp-bz2-decompressor.h 
> ../../libyelp/yelp-lzma-decompressor.h 
> ../../libyelp/yelp-magic-decompressor.h" ${_source_dir} 
> --deprecated-guards="G_DISABLE_DEPRECATED" --rebuild-types 
> if grep -l '^..*$' libyelp.types > /dev/null 2>&1 ; then \
> scanobj_options=""; \
> gtkdoc-scangobj 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
> if test "$?" = "0"; then \
> if test "x" = "x1"; then \
> scanobj_options="--verbose"; \
> fi; \
> fi; \
> CC="/bin/bash ../../libtool --tag=CC --mode=compile gcc  
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fPIE -fstack-protector-strong -Wformat -Werror=format-security -g" 
> LD="/bin/bash ../../libtool --tag=CC --mode=link gcc -lgobject-2.0 -lglib-2.0 
>  -g -O2 -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -g  -fPIE -pie -Wl,-z,relro -Wl,-z,now 
> -Wl,-z,defs -Wl,-O1 -Wl,--as-needed" RUN="/bin/bash ../../libtool 
> --mode=execute" CFLAGS="-pthread -I/usr/include/gtk-3.0/unix-print 
> -I/usr/include/webkitgtk-4.0 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
> -I/usr/include/webkitgtk-4.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../libyelp -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -g" LDFLAGS="-lbz2 -llzma -lgio-2.0 -lxslt -lxml2 
> -lexslt -lxslt -lxml2 -lsqlite3 -lwebkit2gtk-4.0 -lgtk-3 -lgdk-3 
> -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo 
> -lgdk_pixbuf-2.0 -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -ljavascriptcoregtk-4.0 
> -lglib-2.0 ../../libyelp/libyelp.la -fPIE -pie -Wl,-z,relro -Wl,-z,now 
> -Wl,-z,defs -Wl,-O1 -Wl,--as-needed" \
> gtkdoc-scangobj  $scanobj_options --module=libyelp; \
> else \
> for i in libyelp.args libyelp.hierarchy libyelp.interfaces 
> libyelp.prerequisites libyelp.signals ; do \
> test -f $i || touch $i ; \
> done \
> fi
> 
> (process:32124): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 
> 'GDK_IS_SCREEN (screen)' failed
> 
> ** (process:32124): WARNING **: Unable to connect to dbus: Cannot spawn a 
> message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or 
> /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file 
> or directory
> Segmentation fault
> Scan failed: 
> Makefile:647: recipe for target 'scan-build.stamp' failed
> make[5]: *** [scan-build.stamp] Error 139

If the failure looks som

Bug#837241: marked as done (rabbitmq-server: FTBFS: src/gen_server2.erl:231: syntax error before: '/')

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 10:50:07 +
with message-id 
and subject line Bug#837241: fixed in rabbitmq-server 3.6.5-1
has caused the Debian Bug report #837241,
regarding rabbitmq-server: FTBFS: src/gen_server2.erl:231: syntax error before: 
'/'
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.)


-- 
837241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rabbitmq-server
Version: 3.5.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 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 '/<>'
> Makefile:434: deps.mk: No such file or directory
> python codegen.py body codegen/amqp-rabbitmq-0.9.1.json 
> codegen/credit_extension.json src/rabbit_framing_amqp_0_9_1.erl
> python codegen.py body codegen/amqp-rabbitmq-0.8.json 
> src/rabbit_framing_amqp_0_8.erl
> xsltproc --novalid --stringparam modulename "`basename 
> src/rabbit_ctl_usage.erl .erl`" \
>   docs/usage.xsl docs/rabbitmqctl.1.xml > src/rabbit_ctl_usage.erl.tmp
> sed -e 's/"/\\"/g' -e 's/%QUOTE%/"/g' src/rabbit_ctl_usage.erl.tmp > 
> src/rabbit_ctl_usage.erl.tmp2
> fold -s src/rabbit_ctl_usage.erl.tmp2 > src/rabbit_ctl_usage.erl.tmp3
> mv src/rabbit_ctl_usage.erl.tmp3 src/rabbit_ctl_usage.erl
> rm src/rabbit_ctl_usage.erl.tmp src/rabbit_ctl_usage.erl.tmp2
> xsltproc --novalid --stringparam modulename "`basename 
> src/rabbit_plugins_usage.erl .erl`" \
>   docs/usage.xsl docs/rabbitmq-plugins.1.xml > 
> src/rabbit_plugins_usage.erl.tmp
> sed -e 's/"/\\"/g' -e 's/%QUOTE%/"/g' src/rabbit_plugins_usage.erl.tmp > 
> src/rabbit_plugins_usage.erl.tmp2
> fold -s src/rabbit_plugins_usage.erl.tmp2 > src/rabbit_plugins_usage.erl.tmp3
> mv src/rabbit_plugins_usage.erl.tmp3 src/rabbit_plugins_usage.erl
> rm src/rabbit_plugins_usage.erl.tmp src/rabbit_plugins_usage.erl.tmp2
> python codegen.py --ignore-conflicts header codegen/amqp-rabbitmq-0.9.1.json 
> codegen/credit_extension.json codegen/amqp-rabbitmq-0.8.json 
> include/rabbit_framing.hrl
> rm -f deps.mk
> echo 
> src/rabbit_msg_store_index.erl:src/rabbit_exchange_type_fanout.erl:src/rabbit_framing.erl:src/rabbit_mirror_queue_slave.erl:src/background_gc.erl:src/rabbit_command_assembler.erl:src/rabbit_exchange_type_headers.erl:src/supervisor2.erl:src/rabbit_heartbeat.erl:src/rabbit_amqqueue_process.erl:src/rabbit_channel_interceptor.erl:src/pg2_fixed.erl:src/delegate_sup.erl:src/rabbit_priority_queue.erl:src/vm_memory_monitor.erl:src/rabbit_auth_backend_dummy.erl:src/rabbit.erl:src/rabbit_sasl_report_file_h.erl:src/rabbit_channel_sup_sup.erl:src/pmon.erl:src/rabbit_registry.erl:src/rabbit_queue_index.erl:src/mirrored_supervisor.erl:src/rabbit_alarm.erl:src/rabbit_access_control.erl:src/rabbit_amqqueue_sup_sup.erl:src/rabbit_version.erl:src/rabbit_net.erl:src/rabbit_auth_mechanism.erl:src/rabbit_trace.erl:src/rabbit_ctl_misc.erl:src/rabbit_backing_queue.erl:src/rabbit_authn_backend.erl:src/rabbit_auth_mechanism_cr_demo.erl:src/mochijson2.erl:src/rabbit_autoheal.erl:src/file_handle_cache.erl:src/rabbit_upgrade_functions.erl:src/rabbit_mnesia_rename.erl:src/rabbit_guid.erl:src/rabbit_auth_mechanism_amqplain.erl:src/rabbit_diagnostics.erl:src/gen_server2.erl:src/rabbit_runtime_parameter.erl:src/priority_queue.erl:src/tcp_acceptor.erl:src/app_utils.erl:src/rabbit_misc.erl:src/rabbit_mnesia.erl:src/rabbit_connection_sup.erl:src/rabbit_table.erl:src/rabbit_queue_consumers.erl:src/rabbit_mirror_queue_master.erl:src/credit_flow.erl:src/supervised_lifecycle.erl:src/tcp_listener.erl:src/rabbit_sup.erl:src/rabbit_networking.erl:src/rabbit_prelaunch.erl:src/gatherer.erl:src/rabbit_client_sup.erl:src/rabbit_variable_queue.erl:src/rabbit_queue_decorator.erl:src/rabbit_event.erl:src/worker_pool_worker.erl:src/pg_local.erl:src/rabbit_node_monitor.erl:src/rabbit_runtime_parameters.erl:src/rabbit_exchange_type.erl:src/mochinum.erl:src/rabbit_authz_backend.erl:src/rabbit_exchange_type_invalid.erl:src/rabbit_policies.erl:src/rabbit_binary_parser.erl:src/tcp_acceptor_sup.erl:src/rabbit_msg_store.erl:src/delegate.erl:src/rabbit_error_logger_file_h.erl:src/file_handle_cache_stats.erl:src/rabbit_reader.erl:src/rabbit_direct.erl:src/rabbit_memory_monitor.erl:src/rabbit_policy.erl:src/rabbit_exchange_type_direct.erl:src/rabbit_vm.erl:src/rabbit_limiter.erl:src/rabbit_mirror_queue_misc.erl:src/mnesia_sync.erl:src/tcp_listener_sup.erl:src/rabbit_mirror_queue_mode_node

Bug#841616: marked as done (golang-github-azure-azure-sdk-for-go: FTBFS: src/github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined: jwt.MapClaims)

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 11:48:56 +0100
with message-id <4af19ebe-63f5-fa12-f900-9ef1b98c7...@tincho.org>
and subject line Fixed already
has caused the Debian Bug report #841616,
regarding golang-github-azure-azure-sdk-for-go: FTBFS: 
src/github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined: 
jwt.MapClaims
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.)


-- 
841616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-azure-azure-sdk-for-go
Version: 2.1.1~beta-2
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 --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/Azure/azure-sdk-for-go/arm/authorization 
> github.com/Azure/azure-sdk-for-go/arm/cdn 
> github.com/Azure/azure-sdk-for-go/arm/compute 
> github.com/Azure/azure-sdk-for-go/arm/dns 
> github.com/Azure/azure-sdk-for-go/arm/examples 
> github.com/Azure/azure-sdk-for-go/arm/examples/helpers 
> github.com/Azure/azure-sdk-for-go/arm/intune 
> github.com/Azure/azure-sdk-for-go/arm/logic 
> github.com/Azure/azure-sdk-for-go/arm/network 
> github.com/Azure/azure-sdk-for-go/arm/notificationhubs 
> github.com/Azure/azure-sdk-for-go/arm/redis 
> github.com/Azure/azure-sdk-for-go/arm/resources/authorization 
> github.com/Azure/azure-sdk-for-go/arm/resources/features 
> github.com/Azure/azure-sdk-for-go/arm/resources/resources 
> github.com/Azure/azure-sdk-for-go/arm/resources/subscriptions 
> github.com/Azure/azure-sdk-for-go/arm/scheduler 
> github.com/Azure/azure-sdk-for-go/arm/search 
> github.com/Azure/azure-sdk-for-go/arm/storage 
> github.com/Azure/azure-sdk-for-go/arm/web 
> github.com/Azure/azure-sdk-for-go/core/http 
> github.com/Azure/azure-sdk-for-go/core/tls 
> github.com/Azure/azure-sdk-for-go/management 
> github.com/Azure/azure-sdk-for-go/management/affinitygroup 
> github.com/Azure/azure-sdk-for-go/management/hostedservice 
> github.com/Azure/azure-sdk-for-go/management/location 
> github.com/Azure/azure-sdk-for-go/management/networksecuritygroup 
> github.com/Azure/azure-sdk-for-go/management/osimage 
> github.com/Azure/azure-sdk-for-go/management/sql 
> github.com/Azure/azure-sdk-for-go/management/storageservice 
> github.com/Azure/azure-sdk-for-go/management/testutils 
> github.com/Azure/azure-sdk-for-go/management/virtualmachine 
> github.com/Azure/azure-sdk-for-go/management/virtualmachinedisk 
> github.com/Azure/azure-sdk-for-go/management/virtualmachineimage 
> github.com/Azure/azure-sdk-for-go/management/virtualnetwork 
> github.com/Azure/azure-sdk-for-go/management/vmutils 
> github.com/Azure/azure-sdk-for-go/storage
> github.com/Azure/go-autorest/autorest
> github.com/Azure/go-autorest/autorest/date
> github.com/dgrijalva/jwt-go
> github.com/Azure/go-autorest/autorest/azure
> # github.com/Azure/go-autorest/autorest/azure
> src/github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined: 
> jwt.MapClaims
> github.com/Azure/go-autorest/autorest/to
> github.com/Azure/azure-sdk-for-go/core/tls
> github.com/Azure/azure-sdk-for-go/core/http
> golang.org/x/crypto/pkcs12/internal/rc2
> golang.org/x/crypto/pkcs12
> github.com/Azure/azure-sdk-for-go/management
> github.com/Azure/azure-sdk-for-go/management/affinitygroup
> github.com/Azure/azure-sdk-for-go/management/hostedservice
> github.com/Azure/azure-sdk-for-go/management/location
> github.com/Azure/azure-sdk-for-go/management/networksecuritygroup
> github.com/Azure/azure-sdk-for-go/management/osimage
> github.com/Azure/azure-sdk-for-go/management/sql
> github.com/Azure/azure-sdk-for-go/management/storageservice
> github.com/Azure/azure-sdk-for-go/management/testutils
> github.com/Azure/azure-sdk-for-go/management/virtualmachinedisk
> github.com/Azure/azure-sdk-for-go/management/virtualmachine
> github.com/Azure/azure-sdk-for-go/management/virtualmachineimage
> github.com/Azure/azure-sdk-for-go/management/virtualnetwork
> github.com/Azure/azure-sdk-for-go/management/vmutils
> github.com/Azure/azure-sdk-for-go/storage
> dh_auto_build: go install -v -p 1 
> github.com/Azure/azure-sdk-for-go/arm/authorization 
> github.com/Azure/azure-sdk-for-go/a

Bug#828369: marked as done (krb5: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 11:00:15 +
with message-id 
and subject line Bug#828369: fixed in krb5 1.15~beta1-1
has caused the Debian Bug report #828369,
regarding krb5: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5
Version: 1.13.2+dfsg-5
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/krb5_1.13.2+dfsg-5_amd64-20160529-1436

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.15~beta1-1

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated krb5 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, 02 Nov 2016 00:12:46 -0400
Source: krb5
Binary: krb5-user krb5-kdc krb5-kdc-ldap krb5-admin-server krb5-kpropd 
krb5-multidev libkrb5-dev libkrb5-dbg krb5-pkinit krb5-otp krb5-k5tls krb5-doc 
libkrb5-3 libgssapi-krb5-2 libgssrpc4 libkadm5srv-mit11 libkadm5clnt-mit11 
libk5crypto3 libkdb5-8 libkrb5support0 libkrad0 krb5-gss-samples krb5-locales 
libkrad-dev
Architecture: source amd64 all
Version: 1.15~beta1-1
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Description:
 krb5-admin-server - MIT Kerberos master server (kadmind)
 krb5-doc   - documentation for MIT Kerberos
 krb5-gss-samples - MIT Kerberos GSS Sample applications
 krb5-k5tls - TLS plugin for MIT Kerberos
 krb5-kdc   - MIT Kerberos key server (KDC)
 krb5-kdc-ldap - MIT Kerberos key server (KDC) LDAP plugin
 krb5-kpropd - MIT Kerberos key server (KDC)
 krb5-locales - internationalization support for MIT Kerberos
 krb5-multidev - development files for MIT Kerberos without Heimdal conflict
 krb5-otp   - OTP plugin for MIT Kerberos
 krb5-pkinit - PKINIT plugin for MIT Kerberos
 krb5-user  - basic programs to authenticate using MIT Kerberos
 libgssapi-krb5-2 - MIT Kerberos runtime libraries - krb5 GSS-API Mechanism
 libgssrpc4 - MIT Kerberos runtime libraries - GSS enabled ONCRPC
 libk5crypto3 - MIT Kerberos runtime libraries - Crypto Library
 libkadm5clnt-mit11 - MIT Kerberos runtime libraries - Administration Clients
 libkadm5srv-mit11 - MIT Kerberos runtime libraries - KDC and Admin Server
 libkdb5-8  - MIT Kerberos runtime libraries - Kerberos database
 libkrad-dev - MIT Kerberos RADIUS Library Development
 libkrad0   - MIT Kerberos runtime libraries - RADIUS library
 libkrb5-3  - MIT Kerberos runtime libraries
 libkrb5-dbg - debugging files for MIT Kerberos
 libkrb5-dev - headers and development libraries for MIT Kerberos
 libkrb5support0 - MIT Kerberos runtime libraries - Support library
Closes: 828369
Changes:
 krb5 (1.15~beta1-1) unstable; urgency=low
 .
   [ Benjamin Kaduk ]
   * New upstream version
 - Upstream's tarball is now DFSG-free
 - Builds against openssl 1.1.0, Closes: #828369
 - Add support for the AES-SHA2 enctypes
 - Add support to kadmin for remote extraction of current keys
   and principal attributes to prevent such extraction
 - Add DNS auto-discovery using URI records in addition to SRV records
 - Improve LDAP backend to contain some features previously only
   present in the BDB backend
 - Use the getrandom system call on supported Linux kern

Bug#812303: synergy: diff for NMU version 1.4.16-1.1

[Arturo Borrero Gonzalez]

On Mon, 24 Oct 2016 00:33:44 -0500 Joshua Honeycutt
 wrote:
> Control: tags 812303 + patch
> Control: tags 812303 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for synergy (versioned as 1.4.16-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Regards.

Hi,

ping me if you need sponsor for this upload.

best regards.

Processed: found 836859 in 9.2.0-1, tagging 842682, found 837628 in 0.08-4, tagging 837628 ..., tagging 841313 ...

[Debian Bug Tracking System]

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

> found 836859 9.2.0-1
Bug #836859 [python-tango-doc] python-tango-doc: fails to upgrade from 'sid' - 
trying to overwrite /usr/share/doc-base/pytango-manual
Marked as found in versions pytango/9.2.0-1.
> tags 842682 + sid stretch
Bug #842682 [mp3splt] mp3splt: depending libmp3splt version not available yet 
(0.7.3 vs 0.9.2)
Added tag(s) stretch and sid.
> found 837628 0.08-4
Bug #837628 [libheimdal-kadm5-perl] Removal of Heimdal from testing
Marked as found in versions libheimdal-kadm5-perl/0.08-4.
> tags 837628 + sid stretch
Bug #837628 [libheimdal-kadm5-perl] Removal of Heimdal from testing
Added tag(s) stretch and sid.
> found 836885 2.4.42+dfsg-2
Bug #836885 [src:openldap] please stop building against Heimdal
Marked as found in versions openldap/2.4.42+dfsg-2.
> tags 841313 + sid stretch
Bug #841313 {Done: Norbert Preining } 
[src:latex-cjk-japanese-wadalab] latex-cjk-japanese-wadalab: FTBFS: Create .afm 
and .pfa fonts from dg. \n Segmentation fault (core dumped)
Added tag(s) sid and stretch.
> tags 842387 + sid
Bug #842387 [src:zeroc-icee] zeroc-icee: FTBFS in amd64 clean jail
Added tag(s) sid.
> tags 842326 + sid stretch
Bug #842326 [ncmpc] [PATCH] [RC] Fix FTBS for when building against upcoming 
lirc-0.9.4
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
836859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836859
836885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836885
837628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837628
841313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841313
842326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842326
842387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842387
842682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#843036: python-flake8: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-flake8
Version: 3.0.4+dfsg1-2
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 python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/processor.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/utils.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/__main__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/statistics.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/exceptions.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/style_guide.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/defaults.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/checker.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
copying src/flake8/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/api
copying src/flake8/api/legacy.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/api
copying src/flake8/api/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/api
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/formatting
copying src/flake8/formatting/base.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/formatting
copying src/flake8/formatting/default.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/formatting
copying src/flake8/formatting/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/formatting
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/git.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/vcs.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/options.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/setuptools_command.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/cli.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/mercurial.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
copying src/flake8/main/application.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/main
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/options
copying src/flake8/options/manager.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/options
copying src/flake8/options/config.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/options
copying src/flake8/options/aggregator.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/options
copying src/flake8/options/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/options
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
copying src/flake8/plugins/manager.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
copying src/flake8/plugins/pyflakes.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
copying src/flake8/plugins/_trie.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
copying src/flake8/plugins/__init__.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
copying src/flake8/plugins/notifier.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_2.7/build/flake8/plugins
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_3.5/build/flake8
copying src/flake8/processor.py -> 
/<>/python-flake8-3.0.4+dfsg1/.pybuild/pythonX.Y_3.5/build/flake8
copying

Bug#835793: marked as done (python2.7: FTBFS with openssl 1.1.2)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 11:19:56 +
with message-id 
and subject line Bug#835793: fixed in python2.7 2.7.12-4
has caused the Debian Bug report #835793,
regarding python2.7: FTBFS with openssl 1.1.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.)


-- 
835793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python2.7
Version: 2.7.12-2
Severity: important
Control: block 827061 by -1
Control: forwarded -1 https://bugs.python.org/issue26470

OpenSSL 1.1.0 has been released. During a rebuild of all packages using
OpenSSL this package succeeded to build but it should have failed. That is why
this bug is comming so late. The build is missing the modules _hashlib and
_ssl. A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/python2.7_2.7.12-2_amd64-2016-08-26T19%3A34%3A18Z

Upstream seems to have a patch in their BTS.

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains the 1.1
release. I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.

Sebastian
--- End Message ---
--- Begin Message ---
Source: python2.7
Source-Version: 2.7.12-4

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python2.7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 11:11:39 +0100
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal 
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev 
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg 
libpython2.7-dbg
Architecture: source
Version: 2.7.12-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 libpython2.7-dev - Header files and a static library for Python (v2.7)
 libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
 libpython2.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 python2.7-dev - Header files and a static library for Python (v2.7)
 python2.7-doc - Documentation for the high-level object-oriented language 
Python
 python2.7-examples - Examples for the Python language (v2.7)
 python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 835793
Changes:
 python2.7 (2.7.12-4) unstable; urgency=medium
 .
   * Update to 20161103 from the 2.7 branch.
 - Issue #21720: Improve exception message when the type of fromlist is
   unicode.  fromlist parameter of __import__() only accepts str in Python 2
   and this will help to identify the problem especially when the
   unicode_literals future import is used.
 - Issue #26906: Resolving special methods of uninitialized type now causes
   implicit initialization of the type instead of a fail.
 - Issue #18287: PyType_Ready() now checks that tp_name is not NULL.
 - Issue #24098: Fixed possible crash when AST is changed in process of
   compiling it.
 - Issue #28350: String constants with null character no longer interned.
 - Issue #27942: String constants now interned recursively in tuples and
   frozensets.
 - Issue #15578: Correctly incref the parent module while

Bug#843038: elki: FTBFS (failing tests)

[Santiago Vila]

Package: src:elki
Version: 0.7.1-2
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 --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# Remove unneded executable bits:
find elki addons data -type f -executable -exec chmod -x {} \+
dh_auto_configure -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -pelki --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo

[... snipped ...]

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
de.lmu.ifi.dbs.elki.evaluation.scores.ROCEvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
Running de.lmu.ifi.dbs.elki.evaluation.paircounting.ClusterContingencyTableTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec - in 
de.lmu.ifi.dbs.elki.evaluation.paircounting.ClusterContingencyTableTest

Results :

Tests in error: 
  IntegerArrayQuickSortTest.testSorted:130 TestTimedOut test timed out after 
500...

Tests run: 348, Failures: 0, Errors: 1, Skipped: 1

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ELKI Data Mining Framework - Parent Project  SUCCESS [  0.389 s]
[INFO] ELKI Data Mining Framework . FAILURE [02:01 min]
[INFO] ELKI Data Mining Framework - Batik Visualization ... SKIPPED
[INFO] ELKI Data Mining Framework - Tutorial Algorithms ... SKIPPED
[INFO] ELKI Data Mining Framework - LibSVM based extensions SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:02 min
[INFO] Finished at: 2016-11-02T00:48:31+01:00
[INFO] Final Memory: 14M/36M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project elki: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/elki/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :elki
dh_auto_test: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I attach two different build logs.

Apparently some test expect a certain task to be executed in a certain
time. This is usually not a good idea for a Debian source package,
because there is not any guarantee anywhere that the CPU performance
will remain constant during the package build. The same machine could
well be doing many other things in parallel.

Thanks.

elki_0.7.1-2_amd64-20161101T185439Z.gz
Description: application/gzip


elki_0.7.1-2_amd64-20161101T234307Z.gz
Description: application/gzip

Bug#843039: repmgr: depends on postgresql-9.5-repmgr which is no longer built

[Emilio Pozuelo Monfort]

Source: repmgr
Version: 3.2.1-1
Severity: serious

The new version of repmgr builds postgresql-9.6-repmgr for postgresql-9.6.
However repmgr still depends on postgresql-9.5-repmgr (or older). Please
make it depend on postgresql-9.6-repmgr now.

Thanks,
Emilio

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

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

Bug#843039: repmgr: depends on postgresql-9.5-repmgr which is no longer built

[Marco Nenciarini]

Il 03/11/16 12:25, Emilio Pozuelo Monfort ha scritto:
> Source: repmgr
> Version: 3.2.1-1
> Severity: serious
> 
> The new version of repmgr builds postgresql-9.6-repmgr for postgresql-9.6.
> However repmgr still depends on postgresql-9.5-repmgr (or older). Please
> make it depend on postgresql-9.6-repmgr now.
> 

Thanks for the report. I'll upload a new version ASAP.

Regards,
Marco

-- 
Marco Nenciarini - mnen...@kcore.it
7C23 B804 3E65 D298 0A21  B6E2 589F 03F0 1BA5 5038



signature.asc
Description: OpenPGP digital signature

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Bernhard Schmidt]

Control: tags -1 confirmed

> >   == Begin MixMonitor Recording PJSIP/trunk-vitelity-in-
> > asterisk*CLI>
> > Disconnected from Asterisk server
> > Asterisk cleanly ending (0).
> > Executing last minute cleanups
> > 
> > That's all. Nothing in the log either.
> > 
> > After going back to pjproject 2.5.1~dfsg-4 everything works again.
> > 
> > Maybe asterisk just needs to be rebuilt against 2.5.5? I could try this 
> > later perhaps.
> 
> Thanks for the report. Unfortunately as of tonight rebuilding is not an
> option anymore, because it FTBFSes against OpenSSL 1.1.0 (see
> Bug#816042). I'm reassigning this to pjproject to prevent testing
> migration for now.

Confirmed. If you start Asterisk in the foreground you actually get an
assertion

asterisk: ../src/pj/os_core_unix.c:1254: pj_mutex_lock: Assertion
`mutex' failed.
Aborted

Haven't done any further debugging until now, since we can't build
asterisk.

Bernhard


signature.asc
Description: Digital signature

Bug#843041: pacemaker: CVE-2016-7035

[Salvatore Bonaccorso]

Source: pacemaker
Version: 1.1.15-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for pacemaker. Setting RC
severity since I do not know how frequent such configrations are, but
should be fixed for stretch. Patch is at [1].

CVE-2016-7035[0]:
improper IPC guarding

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7035
[1] 
https://github.com/ClusterLabs/pacemaker/pull/1166/commits/5a20855d6054ebaae590c09262b328d957cc1fc2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Processed: Re: Bug#842878: Asterisk crashes with pjproject 2.5.5

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #842878 [src:pjproject] Asterisk crashes with pjproject 2.5.5
Added tag(s) confirmed.

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

Bug#843039: marked as done (repmgr: depends on postgresql-9.5-repmgr which is no longer built)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 12:05:04 +
with message-id 
and subject line Bug#843039: fixed in repmgr 3.2.1-2
has caused the Debian Bug report #843039,
regarding repmgr: depends on postgresql-9.5-repmgr which is no longer built
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.)


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

The new version of repmgr builds postgresql-9.6-repmgr for postgresql-9.6.
However repmgr still depends on postgresql-9.5-repmgr (or older). Please
make it depend on postgresql-9.6-repmgr now.

Thanks,
Emilio

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: repmgr
Source-Version: 3.2.1-2

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

Debian distribution maintenance software
pp.
Marco Nenciarini  (supplier of updated repmgr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 12:35:10 +0100
Source: repmgr
Binary: repmgr-common repmgr repmgr-dbg postgresql-9.6-repmgr 
postgresql-9.6-repmgr-dbg
Architecture: source amd64 all
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Marco Nenciarini 
Description:
 postgresql-9.6-repmgr - replication manager for PostgreSQL 9.6
 postgresql-9.6-repmgr-dbg - debug symbols for repmgr for PostgreSQL 9.6
 repmgr - replication manager for PostgreSQL (metapackage)
 repmgr-common - replication manager for PostgreSQL common files
 repmgr-dbg - transitional dummy package
Closes: 843039
Changes:
 repmgr (3.2.1-2) unstable; urgency=medium
 .
   * Depends on postgresql-9.6.
 Thanks to Emilio Pozuelo Monfort  (Closes: 843039)
Checksums-Sha1:
 c3eaada2ec1d964daabff4020deb53cc191113e2 2220 repmgr_3.2.1-2.dsc
 1dc3b6e667e5a3f75cc46600bfe442ba96950dfb 7720 repmgr_3.2.1-2.debian.tar.xz
 372513bf4535794901b549540839b26fc6777ade 253722 
postgresql-9.6-repmgr-dbg_3.2.1-2_amd64.deb
 7abbb3c104ed06783f6273ff7d8c4a98845de41b 98062 
postgresql-9.6-repmgr_3.2.1-2_amd64.deb
 490527a3e574a4977032fcc176e4aff1b0bcee48 43506 repmgr-common_3.2.1-2_all.deb
 cb7acec6eb0bcf293807c887151cd222dfbd9bdc 8482 repmgr-dbg_3.2.1-2_all.deb
 96c1ac051ae7caeab5499b33386e0cd46cca5c13 8676 repmgr_3.2.1-2_all.deb
Checksums-Sha256:
 c6a522cc529d38cb2f410676068fbe831d794bbc983f77f3caa250deae92cf2f 2220 
repmgr_3.2.1-2.dsc
 50b1d11445310c520d37f79ac50cea1ea9f68db59c98d48d00f3b964b86eeadb 7720 
repmgr_3.2.1-2.debian.tar.xz
 05b1bbe11ddc079f457bd6ce7da2d7e5f6cf615cabe015982a69d7417b544781 253722 
postgresql-9.6-repmgr-dbg_3.2.1-2_amd64.deb
 ed6ca7aa69897ffe4a64c99b4477923f16dcc3b245fde26005ccc1f934231d25 98062 
postgresql-9.6-repmgr_3.2.1-2_amd64.deb
 13ae06768d2a9841b0e857bec99c4e6b32409423d7c365dbc86b067bf38a812d 43506 
repmgr-common_3.2.1-2_all.deb
 f114b27bbb5f40181a6fbad3a718f0726df546ef274b0f6fed6141203b21e143 8482 
repmgr-dbg_3.2.1-2_all.deb
 96bc385a147a74f58fc178489bec1660ddec9800269e09cf3e3a48e88477b9ad 8676 
repmgr_3.2.1-2_all.deb
Files:
 12d729dd13cff1f074aa2ebe4ea6941c 2220 database extra repmgr_3.2.1-2.dsc
 137696a9da61fc21390517fa234ecbd0 7720 database extra 
repmgr_3.2.1-2.debian.tar.xz
 00d12833b3dddb5e560b6656da98bf49 253722 debug extra 
postgresql-9.6-repmgr-dbg_3.2.1-2_amd64.deb
 fc25d11fe90b949a820dd157db4f4d81 98062 database extra 
postgresql-9.6-repmgr_3.2.1-2_amd64.deb
 aa1421e7ab112910467bcf94bfe90283 43506 database extra 
repmgr-common_3.2.1-2_all.deb
 a8e4cf8d74e8a9ca54dc090f357f9db4 8482 debug extra repmgr-dbg_3.2.1-2_all.deb
 4d58c5c4230df6c153c72cd3a4c1e92a 8676 datab

Bug#843038: elki: FTBFS (failing tests)

[Erich Schubert]

severity 843038 wishlist
thanks

Hi,
The test that failed is CPU sensitive.
Yes, it should probably be disabled, but does not any "serious" bug if it
fails on a heavily loaded machine.
In particular, the solution obviously is to just not run the test at all.
That is not really an improvement either...


On Thu, Nov 3, 2016 at 12:16 PM, Santiago Vila  wrote:

> Package: src:elki
> Version: 0.7.1-2
> 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 --buildsystem=maven
>dh_testdir -i -O--buildsystem=maven
>dh_update_autotools_config -i -O--buildsystem=maven
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> # Remove unneded executable bits:
> find elki addons data -type f -executable -exec chmod -x {} \+
> dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar':
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar':
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar':
> No such file or directory
> mh_patchpoms -pelki --debian-build --keep-pom-version
> --maven-repo=/<>/debian/maven-repo
>
> [... snipped ...]
>
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.ROCEvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.scores.
> AveragePrecisionEvaluationTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.paircounting.
> ClusterContingencyTableTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
> - in de.lmu.ifi.dbs.elki.evaluation.paircounting.
> ClusterContingencyTableTest
>
> Results :
>
> Tests in error:
>   IntegerArrayQuickSortTest.testSorted:130 TestTimedOut test timed out
> after 500...
>
> Tests run: 348, Failures: 0, Errors: 1, Skipped: 1
>
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ELKI Data Mining Framework - Parent Project  SUCCESS [
> 0.389 s]
> [INFO] ELKI Data Mining Framework . FAILURE [02:01
> min]
> [INFO] ELKI Data Mining Framework - Batik Visualization ... SKIPPED
> [INFO] ELKI Data Mining Framework - Tutorial Algorithms ... SKIPPED
> [INFO] ELKI Data Mining Framework - LibSVM based extensions SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 02:02 min
> [INFO] Finished at: 2016-11-02T00:48:31+01:00
> [INFO] Final Memory: 14M/36M
> [INFO] 
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-surefire-plugin:2.17:test (default-test) on project elki: There are
> test failures.
> [ERROR]
> [ERROR] Please refer to /<>/elki/target/surefire-reports for
> the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :elki
> dh_auto_test: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/
> jvm/java-8-openjdk-amd64/lib/tools.jar -Dmaven.home=/usr/share/maven
> -Dmaven.multiModuleProjectDirectory=/<>
> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<<
> PKGBUILDDIR>>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
> -Dmaven.repo.local=/<>/debian/maven-repo test returned exit
> code 1
> debian/rules:10: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 1
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 
> --

Processed: Re: Bug#843038: elki: FTBFS (failing tests)

[Debian Bug Tracking System]

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

> severity 843038 wishlist
Bug #843038 [src:elki] elki: FTBFS (failing tests)
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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

Bug#843045: open-infrastructure-system-images: FTBFS with bash as /bin/sh

[Chris Lamb]

Source: open-infrastructure-system-images
Version: 20161101-lts1-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,

open-infrastructure-system-images fails to build from source in unstable/amd64 
when 
/bin/sh is set to bash:

  […]

 dh_auto_test
make -j9 test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  Checking for syntax errors.images/base-system/config/hooks/normal: 
images/base-system/config/hooks/normal: Is a directory
  Makefile:20: recipe for target 'test' failed
  make[1]: *** [test] Error 126
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  dh_auto_test: make -j9 test 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
   `-


open-infrastructure-system-images.20161101-lts1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#843046: open-infrastructure-system-images: FTBFS with bash as /bin/sh

[Chris Lamb]

Source: open-infrastructure-system-images
Version: 20161101-lts1-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,

open-infrastructure-system-images fails to build from source in unstable/amd64 
when 
/bin/sh is set to bash:

  […]

 dh_auto_test
make -j9 test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  Checking for syntax errors.images/base-system/config/hooks/normal: 
images/base-system/config/hooks/normal: Is a directory
  Makefile:20: recipe for target 'test' failed
  make[1]: *** [test] Error 126
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  dh_auto_test: make -j9 test 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
   `-

Bug#835794: marked as done (python3.5: FTBFS with openssl 1.1.2)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 12:20:51 +
with message-id 
and subject line Bug#835794: fixed in python3.5 3.5.2-7
has caused the Debian Bug report #835794,
regarding python3.5: FTBFS with openssl 1.1.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.)


-- 
835794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.5
Version: 3.5.2-3
Severity: important
Control: block 827061 by -1
Control: forwarded -1 https://bugs.python.org/issue26470

OpenSSL 1.1.0 has been released. During a rebuild of all packages using
OpenSSL this package succeeded to build but it should have failed. That is why
this bug is comming so late. The build is missing the modules _hashlib and
_ssl. A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/python3.5_3.5.2-3_amd64-2016-08-26T19%3A34%3A38Z

Upstream seems to have a patch in their BTS.

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains the 1.1
release. I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.

Sebastian
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.2-7

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 12:10:16 +0100
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.2-7
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language (version 3.5)
 python3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 python3.5-dev - Header files and a static library for Python (v3.5)
 python3.5-doc - Documentation for the high-level object-oriented language 
Python
 python3.5-examples - Examples for the Python language (v3.5)
 python3.5-minimal - Minimal subset of the Python language (version 3.5)
 python3.5-venv - Interactive high-level object-oriented language (pyvenv 
binary, v
Closes: 835794
Changes:
 python3.5 (3.5.2-7) unstable; urgency=medium
 .
   * Update to 20161103 from the 3.5 branch.
 - Issue #28426: Fixed potential crash in PyUnicode_AsDecodedObject() in
   debug build.
 - Issue #23782: Fixed possible memory leak in _PyTraceback_Add() and
   exception loss in PyTraceBack_Here().
 - Issue #28379: Added sanity checks and tests for
   PyUnicode_CopyCharacters().
 - Issue #28376: The type of long range iterator is now registered as
   Iterator.
 - Issue #28376: The constructor of range_iterator now checks that step is
   not 0.
 - Issue #26906: Resolving special methods of uninitialized type now causes
   implicit initialization of the type instead of a fail.
 - Issue #18287: PyType_Ready() now checks that tp_name is not NULL.
 - Issue #24098: Fixed

Bug#843046: marked as done (open-infrastructure-system-images: FTBFS with bash as /bin/sh)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 12:23:33 +
with message-id 
<1478175813.445563.776178593.1c116...@webmail.messagingengine.com>
and subject line closing duplicate
has caused the Debian Bug report #843046,
regarding open-infrastructure-system-images: FTBFS with bash as /bin/sh
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.)


-- 
843046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: open-infrastructure-system-images
Version: 20161101-lts1-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,

open-infrastructure-system-images fails to build from source in unstable/amd64 
when 
/bin/sh is set to bash:

  […]

 dh_auto_test
make -j9 test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  Checking for syntax errors.images/base-system/config/hooks/normal: 
images/base-system/config/hooks/normal: Is a directory
  Makefile:20: recipe for target 'test' failed
  make[1]: *** [test] Error 126
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161103121624.MTC73aK81v.db.open-infrastructure-system-images/open-infrastructure-system-images-20161101-lts1'
  dh_auto_test: make -j9 test 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
   `-
--- End Message ---
--- Begin Message ---


Regards,

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

Processed: closing 842682

[Debian Bug Tracking System]

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

> close 842682 2.6.2-0.1
Bug #842682 [mp3splt] mp3splt: depending libmp3splt version not available yet 
(0.7.3 vs 0.9.2)
Marked as fixed in versions mp3splt/2.6.2-0.1.
Bug #842682 [mp3splt] mp3splt: depending libmp3splt version not available yet 
(0.7.3 vs 0.9.2)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#842682: closing 842682

[Jan Luca Naumann]

close 842682 2.6.2-0.1
thanks

Bug#842682: mp3splt: depending libmp3splt version not available yet (0.7.3 vs 0.9.2)

[Jan Luca Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Sorry, forgot to add a description in the message before: The bug
should be closed in version 2.6.2-0.1

Best regards,
Jan

On Mon, 31 Oct 2016 11:39:10 +0100 der_...@opentrash.com wrote:
> Package: mp3spltVersion: 2.4.2-2mp3splt in sid depends on version
> of libmp3splt0 (<<0.7.3~) that is not longer available in sid
> (0.9.2-0.1):#LANG=C apt install -s mp3spltReading package lists...
> DoneBuilding dependency tree  
> Reading state information... DoneSome packages could not be
> installed. This may mean that you haverequested an impossible
> situation or if you are using the unstabledistribution that some
> required packages have not yet been createdor been moved out of
> Incoming.The following information may help to resolve the
> situation:The following packages have unmet
> dependencies: mp3splt : Depends: libmp3splt0 (< 0.7.3~) but
> 0.9.2-0.1 is to be installedE: Unable to correct problems, you have
> held broken packages.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYGy/DAAoJEH4R1/EZ+XG7wWsQAI8cYe23AZWj4OZw5enNZ/yp
BHqJcJAsOuiEZMfEsYmlO6lUuAD3HZ0rnacvVfSoa4ewmbdPdNAvg5gqNLlNSZdp
rkryIRf6PNgDy6YRoSJSgWiWcRdxmB5JAaknfD6nnDtjzE+vda2vsO3eITTjCyt8
hhXekb2wVj/OTUQUpcTJWM0aaAsIim/LbnOI40UfaFiVkutkT4ME0COZJIVVONcT
IdLTfrpDIjhA5N7UvrQMrT4E0cQn/Icmj8eezSEA6/fLlSk5E6TeGEYpXXcdLWEv
/46h0ZIGcHA5hDE+2VLIWCnHDh+DKWRco0Xwck1jaQ3d1pGjtdnUcAihXP5/GOwZ
0zbRUNUkuqk4VpfhSP4hO1B3rdPeYi74RBOnYbZ0Lm62ab22smvUVYexQXenEGLn
a7OOuplhYSc1X2HOTG04gkmN5GpyQnlR+v2B5NzFEVbLkM9JBMvUwG58h4+GsABl
Mk/6kaYsD3ANPywhxBsR37Y1pISebYvdE+6U3CYXZCN69r7I2/R8YGrYpXl1Y8NM
KlgrYpLnzBCBXl7N9wWxM8X7oMgQttv86LYhzQK8kK6lZFJM9qDREi7HAz0ZPMgk
HyrMxSawfSTAoiRFPz6GgJcOwnQUrci8dC9EDfBRESneK9r3ZbP41SqZttC3tRrZ
RieLMUIRrBNqfP1a7QR0
=Nz8q
-END PGP SIGNATURE-

Bug#836859: marked as done (python-tango-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/pytango-manual)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 12:51:12 +
with message-id 
and subject line Bug#836859: fixed in pytango 9.2.0-2
has caused the Debian Bug report #836859,
regarding python-tango-doc: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/doc-base/pytango-manual
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.)


-- 
836859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tango-doc
Version: 9.2.0-1~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-tango-doc.
  Preparing to unpack .../1-python-tango-doc_9.2.0-1~exp2_all.deb ...
  Unpacking python-tango-doc (9.2.0-1~exp2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sbKRNt/1-python-tango-doc_9.2.0-1~exp2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/pytango-manual', which is also in 
package python-pytango-doc 8.1.8-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-sbKRNt/1-python-tango-doc_9.2.0-1~exp2_all.deb


cheers,

Andreas


python-pytango-doc=8.1.8-2_python-tango-doc=9.2.0-1~exp2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pytango
Source-Version: 9.2.0-2

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pytango package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 11:22:02 +0100
Source: pytango
Binary: python-pytango python-tango python3-pytango python3-tango 
python-tango-doc
Architecture: source
Version: 9.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-pytango - transitional dummy package for python-tango
 python-tango - API for the TANGO control system (Python 2)
 python-tango-doc - API for the TANGO control system
 python3-pytango - transitional dummy package for python3-tango
 python3-tango - API for the TANGO control system (Python 3)
Closes: 836859
Changes:
 pytango (9.2.0-2) unstable; urgency=medium
 .
   * Add Breaks and Replace for python-pytango-doc (Closes: #836859)
Checksums-Sha1:
 4b768865bb64c55d79c593fd7fd9be1ef502c268 2536 pytango_9.2.0-2.dsc
 ba7143fac87c791d04319cf6933f29a6c4c94953 5768 pytango_9.2.0-2.debian.tar.xz
Checksums-Sha256:
 b9805fadea43b7aad357b70d78445cb395886567c1e9150d43e13fd4869a617e 2536 
pytango_9.2.0-2.dsc
 7f94691a0cc544751b277abe7c81344b2dac3f14043725b8326166e6f11014a7 5768 
pytango_9.2.0-2.debian.tar.xz
Files:
 8127d722638b0e0471beff09be79b470 2536 science extra pytango_9.2.0-2.dsc
 7c82cf4dbc90a4c05d57ebd94bd0b1e7 5768 science extra 
pytango_9.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYGy9GAAoJEFYykG9GluAVKJoP/2u305LKmYpJiRrGN6jdw3fn
oZ0GmDR3ou8Qaurg8dn7r5j+51jkIGIMvN41dn2azZyDq9l9bnhrsOeYSwi0RNSw
eEKJBEUsn5BYY9p8siuiMvCfnVivQtVDjHz1Vm7yjBSXLy84grOV1H3/6G1SWJF1
GmGtqV11TWQYwLUNjI3SuJLot8OYe7ILRAr/+6jGUIPD4Kad0BnPWCiqFJEC8fzx
4go0Uz86Lp3frFA0or+Mrxv1mdoah/HMtrTRPVFwoTN2zGwwqyXW+LsAigGApD3H
3FzqZFo7kyisfpqsPByfkbeJ3npP0C1ZMdEtBnc9onlu89rE0X5C+1bAXVavT21Y
ckR7iGafeNSWAtDgLobkpVgpWGUws8O6XBYGJlQy0Ra8gzlSKHt+PRoXyk96h1tg
QORQBen9IYxdJl3Kif/IbHzImrjVm98QCuNlEfLWuDHZg8h21K/4hO67XFghH+rO
FcqU374yctN5JyWbzP3nnEWpeMvc28JwC+h4GlgPdXcgRzo7d3J+pSCiEzxsztuR
ICMiGv0yYKenwSSKNYN4wOzDyEZVtvd/Wdrwn5yJGxvRQBGjNzkiS61AfrJs0ipx
Lnd6+WBZKqRatcUQDXuXE6F/I9ddQf6zzRsCpFC6LC3gq8f1WZHCB9lelzz6BPk7
LanK/1V//JrdIfdw7o2K
=Q1VS
-END PGP SIGNATURE

Bug#843052: libterm-filter-perl: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:libterm-filter-perl
Version: 0.03-1
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
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
perl -I. Makefile.PL INSTALLDIRS=vendor
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Term::Filter
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1
make[1]: Entering directory '/<>'
cp lib/Term/Filter.pm blib/lib/Term/Filter.pm
cp lib/Term/Filter/Callback.pm blib/lib/Term/Filter/Callback.pm
Manifying 2 pod documents
make[1]: Leaving directory '/<>'
   dh_auto_test -i
dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
t/00-compile.t  
1..2
ok 1 - Term::Filter loaded ok
ok 2 - Term::Filter::Callback loaded ok
ok
t/basic.t . 
ok 1
ok 2
ok 3
1..3
ok
t/callbacks.t . 
ok 1 - setup callback got a Term::Filter::Callback object
ok 2 - munge_input and munge_output got the right arguments
ok 3 - cleanup got the right arguments
1..3
ok
t/extra-pty.t . 
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
1..6
ok
t/release-eol.t ... skipped: these tests are for release candidate 
testing
t/release-no-tabs.t ... skipped: these tests are for release candidate 
testing
t/release-pod-coverage.t .. skipped: these tests are for release candidate 
testing
t/release-pod-syntax.t  skipped: these tests are for release candidate 
testing
t/requires-tty.t .. 
ok 1 - requires a terminal
ok 2 - requires a terminal
1..2
ok

#   Failed test 'munge_input and munge_output got the right arguments'
#   at t/role.t line 79.
#   'MUNGE_INPUT: My::Term::Filter=HASH(0x23a3110) 
(My::Term::Filter): fOo
# 
# MUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): FOO

# 
# foo

# MUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): FOO
# fooMUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): 

# 
# 

# '
# doesn't match '(?^sx:
# ^
# MUNGE_INPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s 
\(My::Term::Filter\): \s fOo\n
# \n
# (?:
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s 
\(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s 
\(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# |
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s 
\(My::Term::Filter\): \s FOO(?^:\x0d\x0a) FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# foo(?^:\x0d\x0a)
# )
# $
# )'
# Looks like you failed 1 test of 3.
t/role.t .. 
ok 1 - setup callback got a My::Term::Filter object
not ok 2 - munge_input and munge_output got the right arguments
ok 3 - cleanup got the right arguments
1..3
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/3 subtests 

Test Summary Report
---
t/role.t(Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
Files=10, Tests=19, 16 wallclock secs ( 0.05 usr  0.01 sys +  2.60 cusr  0.23 
csys =  2.89 CPU)
Result: FAIL
Failed 1/10 test programs. 1/19 subtests failed.
Makefile:849: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I'm attaching eight different build logs.

Thanks.

libterm-filter-perl.build.tar.gz
Description: application/gzip

Bug#843053: frog does not start

[Rahiel Kasim]

Package: frog
Version: 0.13.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing the frog package, and executing frog on the command-line, I'm
greeted with the following error:

frog: symbol lookup error: /usr/lib/libfrog.so.1: undefined symbol: 
_ZNK5folia24AbstractStructureElement3strERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE

and the program exits.


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

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

Versions of packages frog depends on:
ii  libc62.24-5
ii  libfolia41.4-1
ii  libfrog1 0.13.5-1
ii  libgcc1  1:6.2.0-10
ii  libgomp1 6.2.0-10
ii  libicu57 57.1-4
ii  libmbt1  3.2.16-1
ii  libstdc++6   6.2.0-10
ii  libticcutils2v5  0.14-1
ii  libtimbl46.4.8-1
ii  libucto2 0.9.3-1
ii  libxml2  2.9.4+dfsg1-2

Versions of packages frog recommends:
ii  ucto  0.9.3-1

frog suggests no packages.

-- no debconf information

Bug#828522: Reducing severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 828522 important
thanks

Qt4 has been uploaded with it's dependency on libssl-dev switched to 
libssl1.0-dev so I'm downgrading this bug.

We will happily push the patch when the Buster cycle starts.

Kinds regards, Lisandro.


-- 
http://xkcd.com/150/
Personas como ésta no se encuentran todos los días. Y cuando uno las
encuentra, suelen no estar disponibles.
Si encontrás una, no la pierdas.

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


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

Bug#776118: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/cgi.cfg

[Sandro Tosi]

On Sat, 24 Jan 2015 02:37:38 +0100 Andreas Beckmann  wrote:
> Package: nagios3-cgi
> Version: 3.4.1-3+deb7u1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 nagios3
>
> Hi,
>
> during a test with piuparts I noticed your package failed the piuparts
> upgrade test because dpkg detected a conffile as being modified and then
> prompted the user for an action. As there is no user input, this fails.
> But this is not the real problem, the real problem is that this prompt
> shows up in the first place, as there was nobody modifying this conffile
> at all, the package has just been installed and upgraded...

Hello, this bug was reported against the wheezy version, is it still
happening in more recent releases? thanks!

Bug#841607: mydumper: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/

[Gianfranco Costamagna]

control: tags -1 patch

> CMake Error: The following variables are used in this project, but
> they are set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the
> CMake files:
> MYSQL_LIBRARIES_atomic
> linked by target "mydumper" in directory /<>
> linked by target "myloader" in directory /<>
> 
> -- Configuring incomplete, errors occurred!
> 
> It turns out that mysql_config returns as a necessary lib on amd64 in
> sid. libatomic1 package is properly installed as a dependancy, but it
> installs atomic.so.1 library symlink which isn't detected by cmake. I
> am not sure if this is the desired behaviour, but I would assume so,
> since atomic.so (which seems to be required for cmake detection to
> work) is part of libgcc-{5,6}-dev packages. So possible solutions are:
> 
> a) patch cmake/modules/FindMySQL.cmake to find atomic.so.1
> b) add proper libgcc-{5,6}-dev package dependancy
> 
> I am not quite sure how to determine which libgcc-dev version I should
> use, also I think that this dependancy is not required on i386 (and
> possibly other architectures as well). Will update this bug after I
> find some more info.

I didn't find a reason for such atomic being included
printing some debug seems to introduce it at the very end of that 
FindMySql.cmake file

anyway, there is a better and working Find module by cmake fols

https://cmake.org/Wiki/CMakeUserFindMySQL

Just replace it as a patch and everything will work.

G.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#841607: mydumper: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #841607 [src:mydumper] mydumper: FTBFS: dh_auto_configure: cmake .. 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
Added tag(s) patch.

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

Processed: Lowering the severity to important

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #840454 [src:fflas-ffpack] fflas-ffpack: FTBFS: several tests fail
Severity set to 'important' from 'serious'

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

Bug#840454: Lowering the severity to important

[Tobias Hansen]

Control: severity -1 important

I'm lowering the severity to important to allow testing migration.
fflas-ffpack 1.6.0 in testing is broken since it build-depends on givaro
3.7.2, which is not in testing anymore. For now it is best to have a
working package for the architectures that work (and no package for the
other architectures).

Bug#828457: nodejs: FTBFS with openssl 1.1.0

[Sandro Tosi]

On Sun, 11 Sep 2016 20:10:53 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?=
 wrote:
> 2016-09-11 14:25 GMT+02:00 Kurt Roeckx :
>
> > tags 828457 + patch
> >
> > A patch for it is available at:
> > https://github.com/nodejs/node/pull/8491
> >
> >
> Wonderful, and thank you.
> I'll upload nodejs 6.x in experimental with your patch applied.

Hello Jérémy, it looks like in 6.8.0 you decided to go in the opposite
direction ad "Build-Depends openssl 1.0.2 (Closes: #821403)" - is this
patch still something you plan to apply to the experimental version of
nodejs? any plan to move 6.x to unstable and/or get this bug fixed in
sid? thanks!

Bug#837674: marked as done (parmap: FTBFS: ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 15:39:55 +0100
with message-id 

and subject line Re: Bug#837674: parmap: FTBFS with bindnow and PIE enabled
has caused the Debian Bug report #837674,
regarding parmap: FTBFS: ocamlfind: Cannot mkdir 
/usr/local/lib/ocaml/4.02.3/parmap: Permission denied
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.)


-- 
837674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parmap
Version: 1.0~rc7-1
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
ocamlfind remove parmap
ocamlfind: [WARNING] No such directory: /usr/local/lib/ocaml/4.02.3/parmap
ocamlfind install parmap META bytearray.cmi parmap_utils.cmi parmap.cmi
setcore.cmi parmap.cma parmap.cmxa parmap.cmxs *.a *.mli
bytearray_stubs.o setcore_stubs.o *.so
ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission
denied
Makefile:34: recipe for target 'install' failed
make[2]: *** [install] Error 2
make[2]: Leaving directory '/<>'
debian/rules:9: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 2
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/parmap_1.0~rc7-1_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Hi,

2016-11-03 1:07 GMT+01:00 Mehdi Dogguy :
> Hi,
>
> On 13/09/2016 14:12, Balint Reczey wrote:
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64 with patched GCC and dpkg.
>>
>> The rebuild tested if packages are ready for a transition
>> enabling PIE and bindnow for amd64.
>>
>
> FWIW, I've tried to rebuild parmap in a clean Sid chroot and I am unable
> to reproduce the build failure. You can find attached my build log.
>
> Does it still fail for you?

No, it does build for me now.

Cheers,
Balint

>
> Regards,
>
> --
> Mehdi--- End Message ---

Bug#837674: parmap: FTBFS with bindnow and PIE enabled

[Bálint Réczey]

Hi,

2016-11-03 1:07 GMT+01:00 Mehdi Dogguy :
> Hi,
>
> On 13/09/2016 14:12, Balint Reczey wrote:
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64 with patched GCC and dpkg.
>>
>> The rebuild tested if packages are ready for a transition
>> enabling PIE and bindnow for amd64.
>>
>
> FWIW, I've tried to rebuild parmap in a clean Sid chroot and I am unable
> to reproduce the build failure. You can find attached my build log.
>
> Does it still fail for you?

No, it does build for me now.

Cheers,
Balint

>
> Regards,
>
> --
> Mehdi

Bug#841542: marked as done (parmap: FTBFS: ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 15:39:55 +0100
with message-id 

and subject line Re: Bug#837674: parmap: FTBFS with bindnow and PIE enabled
has caused the Debian Bug report #837674,
regarding parmap: FTBFS: ocamlfind: Cannot mkdir 
/usr/local/lib/ocaml/4.02.3/parmap: Permission denied
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.)


-- 
837674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parmap
Version: 1.0~rc7-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):
> make[2]: Entering directory '/<>'
> ocamlfind ocamlopt -shared -o parmap.cmxs bytearray_stubs.o setcore_stubs.o 
> bytearray.cmx parmap_utils.cmx parmap.cmx
> ocamlfind remove parmap
> ocamlfind: [WARNING] No such directory: /usr/local/lib/ocaml/4.02.3/parmap
> ocamlfind install parmap META bytearray.cmi parmap_utils.cmi parmap.cmi 
> setcore.cmi parmap.cma parmap.cmxa parmap.cmxs *.a *.mli bytearray_stubs.o 
> setcore_stubs.o *.so
> ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied
> Makefile:34: recipe for target 'install' failed
> make[2]: *** [install] Error 2

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/parmap_1.0~rc7-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 ---
Hi,

2016-11-03 1:07 GMT+01:00 Mehdi Dogguy :
> Hi,
>
> On 13/09/2016 14:12, Balint Reczey wrote:
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64 with patched GCC and dpkg.
>>
>> The rebuild tested if packages are ready for a transition
>> enabling PIE and bindnow for amd64.
>>
>
> FWIW, I've tried to rebuild parmap in a clean Sid chroot and I am unable
> to reproduce the build failure. You can find attached my build log.
>
> Does it still fail for you?

No, it does build for me now.

Cheers,
Balint

>
> Regards,
>
> --
> Mehdi--- End Message ---

Bug#814952: numactl: Fix FTBS when all file timestamps are updated

[Sandro Tosi]

On Mon, 14 Mar 2016 14:31:41 -0700 Nish Aravamudan
 wrote:
> On 13.03.2016 [12:50:29 +1100], Ian Wienand wrote:
> > On Tue, Feb 16, 2016 at 03:11:04PM -0800, Nishanth Aravamudan wrote:
> > > # find . -exec touch {} \;
> > > # debian/rules build
> >
> > > /root/numactl-2.0.11/build-aux/missing: line 81: aclocal-1.14: command 
> > > not found
> > > WARNING: 'aclocal-1.14' is missing on your system.
> >
> > I'm not sure this is unexpected; if you go and touch all the generated
> > files and configure thinks they have been modified, it will try to
> > regenerate them.
>
> I think I wasn't quite clear in my original report.
>
> > I don't understand why you would want to do this and why it would make
> > it a FTBFS bug?
>
> The above quote is a way to reproduce the issue, in my experience, but I
> saw it specifically after:

just touching the source files shouldnt result in the package failing
to build, and there is also a recent discussion in d-devel about it:
https://lists.debian.org/debian-devel/2016/10/msg00846.html

Ian, do you plan to add the autoreconf and fix this bug soon? Nish
would you be interested in preparing a NMU for this bug? I'd sponsor
it

thanks!!

Bug#828521: still exists in 0.14.0-2, reported upstream

[Daniel Pocock]

I tried to make a build 0.14.0-3 to fix #843024

I encountered the same FTBFS caused by incompatibility with OpenSSL
1.1.0b headers in sid.

/tmp/buildd/qpid-proton-0.14.0/proton-c/src/ssl/openssl.c: In function
'get_dh2048':
/tmp/buildd/qpid-proton-0.14.0/proton-c/src/ssl/openssl.c:406:5: error:
dereferencing pointer to incomplete type 'DH {aka struct dh_st}'
   dh->p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
 ^~
proton-c/CMakeFiles/qpid-proton.dir/build.make:1105: recipe for target
'proton-c/CMakeFiles/qpid-proton.dir/src/ssl/openssl.c.o' failed



Looking at the pdebuild output, I notice it fetched the following
apparently inconsistent libssl package versions:


Get: 4 http://mirror.switch.ch/ftp/mirror/debian sid/main amd64
libssl1.0.2 amd64 1.0.2j-3 [1291 kB]
...
Get: 35 http://mirror.switch.ch/ftp/mirror/debian sid/main amd64
libssl-dev amd64 1.1.0b-2 [1566 kB]


I had a quick look at upstream master and it doesn't appear to be fixed
in there either so packaging 0.15.0 won't help.

Reported upstream

https://issues.apache.org/jira/browse/PROTON-1341

Processed: confirmed, forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 828521 https://issues.apache.org/jira/browse/PROTON-1341
Bug #828521 [src:qpid-proton] qpid-proton: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/PROTON-1341'.
> found 828521 0.14.0-2
Bug #828521 [src:qpid-proton] qpid-proton: FTBFS with openssl 1.1.0
Marked as found in versions qpid-proton/0.14.0-2.
>
End of message, stopping processing here.

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

Bug#843024: [Pkg-middleware-maintainers] Bug#843024: libqpid-proton8-dev: missing Breaks+Replaces: libqpid-proton2-dev

[Daniel Pocock]

On 03/11/16 10:11, Andreas Beckmann wrote:
> Package: libqpid-proton8-dev
> Version: 0.14.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> 
>>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libqpid-proton8-dev.
>   Preparing to unpack .../1-libqpid-proton8-dev_0.14.0-2_amd64.deb ...
>   Unpacking libqpid-proton8-dev (0.14.0-2) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb 
> (--unpack):
>trying to overwrite '/usr/include/proton/cid.h', which is also in package 
> libqpid-proton2-dev 0.10-2
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb
> 


Thanks for the bug report

I tried fixing this, the fix[1] is in Git

However, I couldn't build and upload the fix because of FTBFS[2] with
OpenSSL 1.1.0 in sid

Regards,

Daniel


1.
https://anonscm.debian.org/cgit/pkg-middleware/qpid-proton.git/commit/?h=debian/sid&id=e96d2e1c963b668e09cc5075cbdf947880bfd14f
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828521

Bug#828464: omniorb-dfsg: FTBFS with openssl 1.1.0

[Sandro Tosi]

On Sun, 26 Jun 2016 12:23:18 +0200 Kurt Roeckx  wrote:
> Source: omniorb-dfsg
> Version: 4.1.6-2
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/omniorb-dfsg_4.1.6-2_amd64-20160529-1458
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.
>
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.

(trying to forward this bug upstream without subscribing to their mailinglist).

Hello omniORB developers! in Debian we're trying to migrate to openssl
1.1.0 but it appears omniorb is not compatible with it: could you have
a look at porting your project to that version of openssl? thanks a
lot in advance!

Bug#828453: marked as pending

[Christos Trochalakis]

tag 828453 pending
thanks

Hello,

Bug #828453 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/nginx.git;a=commitdiff;h=424f50a

---
commit 424f50a53b532f552261df7102adcc8d64881c10
Author: Christos Trochalakis 
Date:   Thu Nov 3 16:50:33 2016 +0200

Fix FTBFS for OpenSSL 1.1.0

diff --git a/debian/changelog b/debian/changelog
index 5101bbb..470a04a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,8 @@
 nginx (1.10.2-2) UNRELEASED; urgency=medium
 
+  * Build against OpenSSL 1.1.0. (Closes: #828453)
++ Patch for nginx-lua by Alessandro Ghedini.
++ Patch for nginx-upstream-fair by Kurt Roeckx.
   * debian/modules:
 + Rethink module patching logic.
 + Convert dav-ext to a dynamic module package:

Processed: Bug#828453 marked as pending

[Debian Bug Tracking System]

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

> tag 828453 pending
Bug #828453 {Done: Christos Trochalakis } [src:nginx] 
nginx: FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: forwarded 828475 https://github.com/openssh/openssh-portable/pull/48

[Debian Bug Tracking System]

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

> forwarded 828475 https://github.com/openssh/openssh-portable/pull/48
Bug #828475 [src:openssh] openssh: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://github.com/openssh/openssh-portable/pull/48'.
> thanks
Stopping processing here.

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

Processed: Really send the commands

[Debian Bug Tracking System]

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

> severity 828522 important
Bug #828522 [src:qt4-x11] qt4-x11: FTBFS with openssl 1.1.0
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#819488: gparted crash with a libparted backtrace

[Sandro Tosi]

On Mon, 11 Apr 2016 21:00:41 -0400 Phillip Susi  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 04/11/2016 02:13 PM, Mattia Rizzolo wrote:
> > On Mon, Apr 11, 2016 at 11:52:32AM -0600, Curtis Gedak wrote:
> >> If I recall correctly, libparted was not able to handle when
> >> there was only one unallocated sector between logical partitions
> >> (it expects at least two).
>
> I believe that is exactly it Curtis.
>
> > well, that's really not a reason to crash like that! ;)
>
> For the last 3 decades, it has not been a problem since every disk
> partitioner has worked this way.  I have sen a few bug reports about
> this recently though, and the others have reported using something
> called Easeus disk partitioning software.  Have you used this?  It
> would be good to confirm this is the source of the problem and I'll
> see if I can't fix parted to handle it.

Phillip, did you have a chance to look at making parted not crashing
if there is only one unallocated sector between partitions? Mattia, do
you still consider this bug RC? thanks!

Bug#828434: marked as done (megatools: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 15:49:10 +
with message-id 
and subject line Bug#828434: fixed in megatools 1.9.98-1
has caused the Debian Bug report #828434,
regarding megatools: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: megatools
Version: 1.9.97-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/megatools_1.9.97-1_amd64-20160529-1450

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: megatools
Source-Version: 1.9.98-1

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

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated megatools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Nov 2016 16:02:16 +0200
Source: megatools
Binary: megatools
Architecture: source
Version: 1.9.98-1
Distribution: unstable
Urgency: medium
Maintainer: Alberto Garcia 
Changed-By: Alberto Garcia 
Description:
 megatools  - Command-line client for the Mega cloud storage service
Closes: 828434 838651
Changes:
 megatools (1.9.98-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #828434, #838651).
   * debian/control:
 - Update Standards-Version to 3.9.8 (no changes).
 - Drop build dependency on libfuse-dev and don't recommend fuse
   anymore, this package no longer ships the megafs binary.
 - Add build dependency on asciidoc.
 - Replace dependency on glib-networking with ca-certificates.
   * debian/{control,copyright,watch}:
 - Use https://megatools.megous.com.
   * debian/watch, debian/upstream/signing-key.asc:
 - Add upstream signing key.
   * debian/copyright:
 - libtools/* is now lib/*.
   * debian/rules:
 - No need to override dh_auto_configure in order to pass
   --disable-silent-rules.
   * make-verbose.patch:
 - Don't run make silently.
   * debian/source/lintian-overrides:
 - This override is no longer necessary.
   * Megatools no longer ships libmega.so:
 - libmega-tools.patch:
   + Drop this patch.
 - debian/install:
   + Don't try to install the file.
 - debian/lintian-overrides:
   + This override is no longer necessary.
Checksums-Sha1:
 d4b570ebb53d54138ec3290bfe56818866964534 1796 megatools_1.9.98-1.dsc
 8a5ce733abeee78913d9f4a467fd8b49bbcffda3 285805 megatools_1.9.98.orig.tar.gz
 dbb2cac83446e75c04de89549867bd7525ef0965 6204 megatools_1.9.98-1.debian.tar.xz
Checksums-Sha256:
 cb4bee52be2e6e3eadb02b02ca58d5cc116b6559245ea616ef37d3331c9f0df6 1796 
megatools_1.9.98-1.dsc
 9b0521a4d27dbc417fc8e12610ac1e1da729bf6d6eb5bef927ef3670b372a16f 285805 
megatools_1.9.98.orig.tar.gz
 6193d45b197c24159237ef49a93c5c98840860497dac8f1dc90b188f148e68f9 6204 
megatools_1.9.98-1.debian.tar.xz
Files:
 a3439d2086ad20fbcf0af2f4e4558dac 1796 utils optional megatools_1.9.98-1.dsc
 3106965745940197497902719df20a7a 285805 utils optional 
megatools_1.9.98.orig.tar.gz
 5067df5e6f1439e0f8016470b444379b 6204 utils optional 
megatools_1.9.98-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYG1YpAAoJEL4yGa8+1BNBh9kP/R5OQcDIniT85NV49z+GSPFi
y2MFLtDWUqhy9yCR786wVdFwTVy8BPecGgRczFUF7oGTTrWRoMIbpZkqaDvNxrQ/
B83+KL6rJAI9ObawG5WoH5AQ+yAcrUs4CGz9D9sieydy+/5QLwQkqiABH/AXKbSE
nBqOfQNjmo5+UPiPxJBleOLSQXIxxD

Processed: #843028 affects education-main-server

[Debian Bug Tracking System]

Processing control commands:

> affects -1 education-main-server
Bug #843028 [dovecot-dev] dovecot-dev: fails to upgrade from 'testing' - trying 
to overwrite /usr/share/aclocal/dovecot-pigeonhole.m4
Added indication that 843028 affects education-main-server

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

Bug#843028: #843028 affects education-main-server

[Holger Levsen]

control: affects -1 education-main-server

see 
https://jenkins.debian.net/job/chroot-installation_stretch_install_education-main-server_upgrade_to_sid/266//consoleFull


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: tagging 841581

[Debian Bug Tracking System]

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

> tags 841581 - pending
Bug #841581 [src:pycryptopp] pycryptopp: FTBFS: eccrypto.h:19:18: fatal error: 
hmqv.h: No such file or directory
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Thu, Nov 03, 2016 at 07:45:16AM +0100, Andreas Henriksson wrote:
> Hello Kurt Roeckx.
> 
> On Sun, Jun 26, 2016 at 12:21:39PM +0200, Kurt Roeckx wrote:
> > Source: fetchmail
> > Version: 6.3.26-2
> > Severity: important
> > Control: block 827061 by -1
> > 
> > Hi,
> > 
> > OpenSSL 1.1.0 is about to released.
> [...]
> > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/fetchmail_6.3.26-2_amd64-20160529-1418
> [...]
> 
> The failure in this build log didn't look like it was really openssl related.
> I've tried rebuilding the package which succeded for me.
> 
> Could you please double-check here and possibly close this bug report
> if there's no issue?

It might have been caused by calling dpkg-buildpackage -j8. If
that's the case you could look into that your debian/rules files
actually has all the proper dependecies. This isn't really
something that should be supported.


Kurt

Bug#828457: nodejs: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Thu, Nov 03, 2016 at 10:42:50AM -0400, Sandro Tosi wrote:
> On Sun, 11 Sep 2016 20:10:53 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?=
>  wrote:
> > 2016-09-11 14:25 GMT+02:00 Kurt Roeckx :
> >
> > > tags 828457 + patch
> > >
> > > A patch for it is available at:
> > > https://github.com/nodejs/node/pull/8491
> > >
> > >
> > Wonderful, and thank you.
> > I'll upload nodejs 6.x in experimental with your patch applied.
> 
> Hello Jérémy, it looks like in 6.8.0 you decided to go in the opposite
> direction ad "Build-Depends openssl 1.0.2 (Closes: #821403)" - is this
> patch still something you plan to apply to the experimental version of
> nodejs? any plan to move 6.x to unstable and/or get this bug fixed in
> sid? thanks!

Note that at least 1 problem has been pointed out in the pull
request. And I understand that they did other changes to make it
work, but I didn't really have time to look at it again.


Kurt

Bug#754036: marked as done (tdiary-contrib: please switch to emacs24)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 16:50:43 +
with message-id 
and subject line Bug#754036: fixed in tdiary-contrib 5.0.2-2
has caused the Debian Bug report #754036,
regarding tdiary-contrib: please switch to emacs24
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.)


-- 
754036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tdiary-contrib
Severity: normal
Tags: patch
User: r...@debian.org
Usertags: emacs24
Control: block 753885 by -1

Dear maintainer,

we're hoping to remove emacs23 from unstable/testing in future:

  https://bugs.debian.org/753885

Please migrate your dependencies to "emacs | emacsen" (or whatever's
more appropriate for your package) as soon as possible.  The attached
patch may help.

Thanks for considering.

--
mass bug filer on behalf of Rob Browning, emacs maintainer
--- debian/control.orig	2014-07-06 13:09:01.939502237 +0200
+++ debian/control	2014-07-06 13:09:21.251737086 +0200
@@ -20,7 +20,7 @@
 
 Package: tdiary-mode
 Architecture: all
-Depends: ${misc:Depends}, emacs24 | emacsen, apel, psgml
+Depends: ${misc:Depends}, emacs | emacsen, apel, psgml
 Suggests: tdiary
 Description: tDiary editing mode for Emacsen
  This package provides Emacs major mode to edit and post entries to tDiary.
--- End Message ---
--- Begin Message ---
Source: tdiary-contrib
Source-Version: 5.0.2-2

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated tdiary-contrib 
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, 02 Nov 2016 19:03:08 +0900
Source: tdiary-contrib
Binary: tdiary-contrib tdiary-mode
Architecture: source all
Version: 5.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Youhei SASAKI 
Description:
 tdiary-contrib - Plugins of tDiary to add functionalities
 tdiary-mode - tDiary editing mode for Emacsen
Closes: 749994 754036 829448
Changes:
 tdiary-contrib (5.0.2-2) unstable; urgency=medium
 .
   * Move old packaging tools to d/packaging-tools/old
   * Update d/copyright: format 1.0
   * Bump Standard Version: 3.9.8
   * Update Depends: bump tdiary version number >= 5
   * The comment_emoji_autocomplete.js is moved into
 tdiary-core (Closes: #829448)
   * Depends emacs | emacsen instead of emacs23
 (Closes: #754036)
   * Fix tdiary-mode installation (Closes: #749994)
Checksums-Sha1:
 843dd069799793b220e2da462c32cae17a2e25f7 2134 tdiary-contrib_5.0.2-2.dsc
 b219d8fac0422c3552c255d21ee5ae997acdfe63 46900 
tdiary-contrib_5.0.2-2.debian.tar.xz
 b87596c1d48cebcecb2f0beacfae12a02f2fff21 254388 tdiary-contrib_5.0.2-2_all.deb
 671dec51df7a339ed135ad829c1625b746e71613 18190 tdiary-mode_5.0.2-2_all.deb
Checksums-Sha256:
 a8b824bc53a032fcde361218ebca0a67690a9a45b6b9f4a7230e24d303addd8b 2134 
tdiary-contrib_5.0.2-2.dsc
 380ac83b94b505e42a584cc834d4c8cce98a5209cea5e6e2fc1517f3c36b2c06 46900 
tdiary-contrib_5.0.2-2.debian.tar.xz
 f6e733ba6157a184df10b398af9c0ba83865c871758821eb09faa101eb784cd0 254388 
tdiary-contrib_5.0.2-2_all.deb
 181d9a499875687638aee0f73b929a109fa6fdb56c2d2cb18c18a82f485fc35c 18190 
tdiary-mode_5.0.2-2_all.deb
Files:
 8798211573ee5a379f9ede21a514310d 2134 web extra tdiary-contrib_5.0.2-2.dsc
 acfa62041dd4ee24e9d247a9a4d7c77b 46900 web extra 
tdiary-contrib_5.0.2-2.debian.tar.xz
 6d505dda82410fa2d1f586cbc39d97e4 254388 web extra 
tdiary-contrib_5.0.2-2_all.deb
 166dec6db264eeaa4b0ce267e6e201d3 18190 web extra tdiary-mode_5.0.2-2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYG2UBAAoJEJOU81SJHX4HCGwQAIfFV2A5MYPQUCjWefLPQTsy
29485ajUwk9+bYbhVDbO+0urXa1ofON6ECTLKdL5wzPaDa0NORuwEKL98HsDylf4
F1CgBN1BN1WeIu6wslqiqTc2iTe7RAZ9I0N+FtRjzHrq4wsN7oWWX4bWLZWhgOsY
K11egtWga3T27VfJVkPcSLVbaYB2n5wraZChEmVVZOux0qXeGAceaErj7kCc5b8J
fUYMKH+xA/6wFAWdPjYofsCks4LeQN8+QcRn4dCGujjkiM/Ckm4oCoM/czVjDJMy
ZocBJJJqbTGWyse/3iBycpcDYBQCRRQd/cF5o2acdNcnLL4EL9xElwadOEki7WaC
7FyXCRM4c6bIKRswHa+Gwyc0JQw2per

Bug#829448: marked as done (tdiary-core: fails to upgrade from 'sid' - trying to overwrite /usr/share/tdiary/js/comment_emoji_autocomplete.js)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 16:50:43 +
with message-id 
and subject line Bug#829448: fixed in tdiary-contrib 5.0.2-2
has caused the Debian Bug report #829448,
regarding tdiary-core: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/tdiary/js/comment_emoji_autocomplete.js
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.)


-- 
829448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tdiary-core
Version: 4.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package tdiary-core.
  Preparing to unpack .../tdiary-core_4.2.1-1_all.deb ...
  Unpacking tdiary-core (4.2.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tdiary-core_4.2.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/tdiary/js/comment_emoji_autocomplete.js', 
which is also in package tdiary-contrib 3.2.2-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


tdiary-contrib=3.2.2-1_tdiary-core=4.2.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tdiary-contrib
Source-Version: 5.0.2-2

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated tdiary-contrib 
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, 02 Nov 2016 19:03:08 +0900
Source: tdiary-contrib
Binary: tdiary-contrib tdiary-mode
Architecture: source all
Version: 5.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Youhei SASAKI 
Description:
 tdiary-contrib - Plugins of tDiary to add functionalities
 tdiary-mode - tDiary editing mode for Emacsen
Closes: 749994 754036 829448
Changes:
 tdiary-contrib (5.0.2-2) unstable; urgency=medium
 .
   * Move old packaging tools to d/packaging-tools/old
   * Update d/copyright: format 1.0
   * Bump Standard Version: 3.9.8
   * Update Depends: bump tdiary version number >= 5
   * The comment_emoji_autocomplete.js is moved into
 tdiary-core (Closes: #829448)
   * Depends emacs | emacsen instead of emacs23
 (Closes: #754036)
   * Fix tdiary-mode installation (Closes: #749994)
Checksums-Sha1:
 843dd069799793b220e2da462c32cae17a2e25f7 2134 tdiary-contrib_5.0.2-2.dsc
 b219d8fac0422c3552c255d21ee5ae997acdfe63 46900 
tdiary-contrib_5.0.2-2.debian.tar.xz
 b87596c1d48cebcecb2f0beacfae12a02f2fff21 254388 tdiary-contrib_5.0.2-2_all.deb
 671dec51df7a339ed135ad829c1625b746e71613 18190 tdiary-mode_5.0.2-2_all.deb
Checksums-Sha256:
 a8b824bc53a032fcde361218ebca0a67690a9a45b6b9f4a7230e24d303addd8b 2134 
tdiary-contrib_5.0.2-2.dsc
 380ac83b94b505e42a584cc834d4c8cce98a5209cea5e6e2fc1517f3c36b2c06 46900 
tdiary-contrib_5.0.2-2.debian.tar.xz
 f6e733ba6157a184df10b398af9c0ba83865c871758821eb09faa101eb784cd0 254388 
tdiary-contrib_5.0.2-2_all.deb
 181d9a499875687638aee0f73b929a109fa6fdb56c2d2cb18c18a82f485fc35c 18190 
tdiary-mode_5.0.2-2_all.deb
Files:
 8798211573ee5a379f9ede21a514310d 2134 web extra tdiary-contrib_5.0.2-2.dsc
 acfa62041dd4ee24e9d247a9a4d7c77b 46900 web extra 
tdiary-contrib_5.0.2-2.debian.tar.xz
 6d505dda82410fa2d1f586cbc39d97e4 254388 web extra 
tdiary-contrib_5.0.2-2_all.deb
 166dec6db264eeaa4b0ce267e6e201d3 18190 web extra tdiary-mode_5.0.2-2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYG2UBAAoJEJOU81SJHX4HCGwQAIfFV2A5MYPQUCjWefLPQTsy
29485ajUwk9+bYbhVDbO+0urXa1ofON6ECTLKdL5wzPaDa0NORuwEKL98HsDylf4
F1CgBN1BN1WeIu6wslqiqTc2iTe7RAZ9I0N+FtRjzHrq4wsN7oWWX4bWLZW

Bug#840689: marked as done (libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 16:49:00 +
with message-id 
and subject line Bug#840689: fixed in libterm-readline-gnu-perl 1.35-1
has caused the Debian Bug report #840689,
regarding libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures
to be marked as done.

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

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


-- 
840689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libterm-readline-gnu-perl
Version: 1.34-1
Severity: serious

Hi,

On a rebuild against libreadline7, your package failed to build on
big-endian, 64-bit architectures:

# 2.4 History Variables
ok 86 - history_inhibit_expansion_function
ok 87
ok 88
ok
Use of uninitialized value in string eq at t/readline.t line 119.
Use of uninitialized value in string eq at t/readline.t line 119.

#   Failed test 'readline_state'
#   at t/readline.t line 152.

Full logs at:

https://buildd.debian.org/status/package.php?p=libterm-readline-gnu-perl

Emilio
--- End Message ---
--- Begin Message ---
Source: libterm-readline-gnu-perl
Source-Version: 1.35-1

We believe that the bug you reported is fixed in the latest version of
libterm-readline-gnu-perl, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
libterm-readline-gnu-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Nov 2016 17:36:31 +0100
Source: libterm-readline-gnu-perl
Binary: libterm-readline-gnu-perl
Architecture: source
Version: 1.35-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Salvatore Bonaccorso 
Closes: 840689
Description: 
 libterm-readline-gnu-perl - Perl extension for the GNU ReadLine/History Library
Changes:
 libterm-readline-gnu-perl (1.35-1) unstable; urgency=medium
 .
   [ Martín Ferrari ]
   * Remove myself from Uploaders.
 .
   [ gregor herrmann ]
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
   * Remove Ryan Niebur from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * New upstream version 1.35
 - Fixes "FTBFS on 64-bit big endian architectures" (Closes: #840689)
Checksums-Sha1: 
 3f635f905df7843ef584d4bb25edcc1ef05b5e17 2433 
libterm-readline-gnu-perl_1.35-1.dsc
 1f57fe986d56c6afa5eb868ca36dc5f0f8dcc3b6 127376 
libterm-readline-gnu-perl_1.35.orig.tar.gz
 a493f909ec270598014749e5638d96e274ba1812 8120 
libterm-readline-gnu-perl_1.35-1.debian.tar.xz
Checksums-Sha256: 
 d4da2be476efe95bdeb7896d90e26e144a4c6e3f816327d6ebcd44d0660da032 2433 
libterm-readline-gnu-perl_1.35-1.dsc
 575d32d4ab67cd656f314e8d0ee3d45d2491078f3b2421e520c4273e92eb9125 127376 
libterm-readline-gnu-perl_1.35.orig.tar.gz
 f8e92cc53b815d1d4f5ddb7f1b7315025c9efee090c6b7ffef62db08411ddcf6 8120 
libterm-readline-gnu-perl_1.35-1.debian.tar.xz
Files: 
 4a4e01b6e5e68367d036f69356473721 2433 perl optional 
libterm-readline-gnu-perl_1.35-1.dsc
 514619d68bda1618da61b19d04b5cefe 127376 perl optional 
libterm-readline-gnu-perl_1.35.orig.tar.gz
 0b2a5205f0c3ef705c7cfb7069fa7065 8120 perl optional 
libterm-readline-gnu-perl_1.35-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKPBAEBCgB5BQJYG2gJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NjQ0NDA5ODA4QzE3MUUwNTUzMURERUUw
NTRDQjhGMzEzNDNDRjQ0EhxjYXJuaWxAZGViaWFuLm9yZwAKCRAFTLjzE0PPRNPd
D/9OfiAg3e9GhhuMeSrjoZ+m5OGsxNCu0pl9/yOnoGQBvFnmS0b3onaOc9gOvo7g
EBb+rh82hPEnnf8s3Wyw8h/7SQyMk+VB6BERSg34YrXmGOMCiGQJtElGwkmk4WP0
EiFfv0VhyEGDrMq9/3vN0gJNy0gdO2codNs7r5Ed1T7yzDV35M7/hYdZ6qC3TRVm
AHx4jCvib1isu4z4/du3N/rs9wccM4sAdtMYPV6Ht/m+8uqz1VXHcVOCd8aK7n6Q
X4HXV3jwpW5TxYvVl2P21YaebBLXNfp7LWU3jMU/PdkQ0e14xNu4Bj3IUqZwC5fv
Kk89b/jcbXp0KWzlEg9b1Ljj75SpAkfz2K4cV61RrDX1ZbMsV61X+dOa9+fiplJy
QhtytFFigChME/UwbKc7xqKHqTiaHC53gJYv5Uakjo86J/UclzOz5ueQPbWw0/7x
7hVT87Cl9Nn5FSP07OCP2OHgT4pyl0kpkZKgWPXV/6+WN2TYd8ShtW39gL/eCehr
yk5QLA0rzaBcnEjqPjLLhM1dT8vKig8djAZkdBpqJo7ExakKf5gVArJV3j2hrHuX
1fyDAHNXg/on5rAQ+cD4yImOTtPUbbq4yaPJ3oM7Tnv1HEy2crEkBq2ek0iNw2Rq
2KZBq05SjjgfCue+XfAPKpEPYKwpRjazBKzfpnfjEnAOHg==
=dLp5
-END PGP SIGNATURE--

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

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 17:59:30 +0100
with message-id <20161103165930.omsvznfjoc2np...@home.ouaza.com>
and subject line Re: pycryptopp: FTBFS: eccrypto.h:19:18: fatal error: hmqv.h
has caused the Debian Bug report #841581,
regarding pycryptopp: 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.)


-- 
841581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycryptopp
Version: 0.6.0.20120313-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):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-EkQe1J/python2.7-2.7.12=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -DDISABLE_EMBEDDED_CRYPTOPP=1 -I/usr/include -I/usr/include/python2.7 -c 
> src/pycryptopp/publickey/ecdsamodule.cpp -o 
> build/temp.linux-x86_64-2.7/src/pycryptopp/publickey/ecdsamodule.o -w
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> In file included from src/pycryptopp/publickey/ecdsamodule.cpp:42:0:
> /usr/include/cryptopp/eccrypto.h:19:18: fatal error: hmqv.h: No such file or 
> directory
>  #include "hmqv.h"
>   ^
> compilation terminated.
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> debian/rules:25: recipe for target 'build-python2.7' failed
> make: *** [build-python2.7] 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/pycryptopp_0.6.0.20120313-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 ---
Hi,

On Wed, 02 Nov 2016, Ramakrishnan Muthukrishnan wrote:
> It looks like this bug is already fixed by the libcrypto++ Debian
> maintainer.
> 
>  
> 
> Is there a way to rebuild the affected packages and see if it closes
> this bug?

Yes, with sbuild's --extra-package parameter for example. I just did it
and I confirm that this bug is fixed in stretch with libcrypto++ 5.6.4-3.
I'm closing this bug since we will already ensure that libcrypto++
migrates to testing with the above RC bug.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/--- End Message ---

Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google.

[Matthew Gabeler-Lee]

Package: pepperflashplugin-nonfree
Followup-For: Bug #833741

This is a grave issue for existing installations as well, as it is thus
impossible to upgrade them away from the releases that have critical
security vulnerabilities actively being exploited in the wild.

Processed: Fix for the kvirc FTBFS

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#828244: bacula: FTBFS with openssl 1.1.0

[Carsten Leonhardt]

Control: severity -1 important

bacula 7.4.4+dfsg-3 switched to using libssl1.0-dev, so the release
critical severity no longer applies.

Bug#811908: Fix for the kvirc FTBFS

[Adrian Bunk]

Control: tags -1 patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code 
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible 
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.


--- debian/rules.old2016-11-03 17:21:49.0 +
+++ debian/rules2016-11-03 17:21:49.0 +
@@ -2,6 +2,8 @@
 #
 DH_ALWAYS_EXCLUDE:=CVS:.svn:.svnignore:.hg:.hgignore
 
+export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98
+
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-undefined -Wl,--as-needed
 
 DEBVERSION = $(shell head -n 1 debian/changelog | sed -e 
's/^[^(]*(\([^)]*\)).*/\1/')


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: bacula: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #828244 [src:bacula] bacula: FTBFS with openssl 1.1.0
Severity set to 'important' from 'serious'

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

Bug#843078: pokerth: FTBFS: qobjectdefs_impl.h:72:88: error: '>>' should be '> >' within a nested template argument list

[Chris Lamb]

Source: pokerth
Version: 1.1.1-6
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,

pokerth fails to build from source in unstable/amd64:

  […]

  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:72:88: error: 
'>>' should be '> >' within a nested template argument list
   template  struct List_Append, 
List> { typedef List Value; };

  ^~
  In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:50:0,
   from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46,
   from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:46,
   from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qapplication.h:43,
   from src/pokerth.cpp:35:
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:98:22: error: 
expected ',' or '...' before '&&' token
   void operator,(T &&value, const ApplyReturnValue &container) {
^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:98:67: error: 
'void QtPrivate::operator,(T)' must take exactly two arguments
   void operator,(T &&value, const ApplyReturnValue &container) {
 ^
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:215:62: error: 
'>>' should be '> >' within a nested template argument list
   template <> struct CheckCompatibleArguments, List<>> { enum { 
value = true }; };
^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:216:75: error: 
'>>' should be '> >' within a nested template argument list
   template  struct CheckCompatibleArguments> 
{ enum { value = true }; };
 ^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:218:78: error: 
'>>' should be '> >' within a nested template argument list
   struct CheckCompatibleArguments, List>

^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:221:78: error: 
'>>' should be '> >' within a nested template argument list
   && CheckCompatibleArguments, 
List>::value };

^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:238:113: error: 
'>>' should be '> >' within a nested template argument list
   template  struct 
ComputeFunctorArgumentCount>

   ^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:241:56: error: 
expected type-specifier before 'decltype'
   template  static auto test(F f) -> 
decltype(((f.operator()((dummy())...)), int()));
  ^~~~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:241:56: error: 
expected initializer before 'decltype'
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:251:104: error: 
'>>' should be '> >' within a nested template argument list
   template  struct 
FunctorReturnType> {

  ^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:26: error: 
expected identifier
   typedef decltype(dummy().operator()((dummy())...)) 
Value;
^~
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:40: error: 
expected unqualified-id before '(' token
   typedef decltype(dummy().operator()((dummy())...)) 
Value;
  ^
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:40: error: 
expected ')' before '(' token
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:41: error: 
'decltype' declared as function returning a function
   typedef decltype(dummy().operator()((dummy())...)) 
Value;
   ^
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:41: error: 
expected ';' at end of member declaration
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:42: error: 
expected unqualified-id before '.' token
   typedef decltype(dummy().operator()((dummy())...)) 
Value;
^
  In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:56:0,
   from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:46,
   from 
/usr/include/x8

Bug#843077: php-memcached: FTBFS: conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory

[Chris Lamb]

Source: php-memcached
Version: 3.0.0a1-13-g6ee96ca+2.2.0-3
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,

php-memcached fails to build from source in unstable/amd64:

  […]

  configure:2866: result: o
  configure:2870: checking whether we are using the GNU C compiler
  configure:2889: cc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:2889: $? = 0
  configure:2898: result: yes
  configure:2907: checking whether cc accepts -g
  configure:2927: cc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:2927: $? = 0
  configure:2968: result: yes
  configure:2985: checking for cc option to accept ISO C89
  configure:3048: cc  -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3048: $? = 0
  configure:3061: result: none needed
  configure:3087: checking how to run the C preprocessor
  configure:3118: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  configure:3118: $? = 0
  configure:3132: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
   #include 
  ^
  compilation terminated.
  configure:3132: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | /* end confdefs.h.  */
  | #include 
  configure:3157: result: cc -E
  configure:3177: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  configure:3177: $? = 0
  configure:3191: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
   #include 
  ^
  compilation terminated.
  configure:3191: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | /* end confdefs.h.  */
  | #include 
  configure:3222: checking for icc
  configure:3231: result: no
  configure:3245: checking for suncc
  configure:3254: result: no
  configure:3272: checking whether cc understands -c and -o together
  configure:3300: cc -c conftest.c -o conftest2.o >&5
  configure:3304: $? = 0
  configure:3310: cc -c conftest.c -o conftest2.o >&5
  configure:3314: $? = 0
  configure:3369: result: yes
  configure:3383: checking for system library directory
  configure:3398: result: lib
  configure:3405: checking if compiler supports -R
  configure:3424: cc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed conftest.c -R /usr/lib  >&5
  cc: error: unrecognized command line option '-R'; did you mean '-R'?
  configure:3424: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | /* end confdefs.h.  */
  | 
  | int
  | main ()
  | {
  | 
  |   ;
  |   return 0;
  | }
  configure:3434: result: no
  configure:3439: checking if compiler supports -Wl,-rpath,
  configure:3458: cc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed conftest.c -Wl,-rpath,/usr/lib  >&5
  configure:3458: $? = 0
  configure:3468: result: yes
  configure:3513: checking build system type
  configure:3527: result: x86_64-pc-linux-gnu
  configure:3547: checking host system type
  configure:3560: result: x86_64-pc-linux-gnu
  configure:3580: checking target system type
  configure:3593: result: x86_64-pc-linux-gnu
  configure:3696: checking for PHP prefix
  configure:3698: result: /usr
  configure:3700: checking for PHP includes
  configure:3702: result: -I/usr/include/php/20151012 
-I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM 
-I/usr/include