Bug#841341: closed by Paulo Henrique de Lima Santana (phls) <p...@softwarelivre.org> (Bug#841341: fixed in bd 1.01-2)

[Vigneshwaran]

Hi Paulo,

I have accepted the pull request and released version v1.02

Link: https://github.com/vigneshwaranr/bd/releases/tag/v1.02

Please let me know if you need anything else.

Thank you,
Vigneshwaran

2016-11-04 2:03 GMT+08:00 Paulo Henrique de Lima Santana <
p...@softwarelivre.org>:

> Hi Gerardo,
>
> - Mensagem original -
> > De: "Gerardo Martín Chaves" 
> > Para: 841...@bugs.debian.org, p...@softwarelivre.org,
> eribe...@debian.org
> > Enviadas: Quinta-feira, 3 de novembro de 2016 15:41:29
> > Assunto: Bug#841341: closed by Paulo Henrique de Lima Santana (phls) <
> p...@softwarelivre.org> (Bug#841341: fixed in bd
> > 1.01-2)
>
> > Paulo, the current fix just add bash as a dependency, but the problem
> > persist.
> >
> > IMO the proper fix should be change the shebang to /bin/bash as bd is a
> > bash script.
> >
> > I submit a pull request to upstream to change it (
> > https://github.com/vigneshwaranr/bd/pull/31)
>
> It's clear to me now how to solve this.
> I'm copying Vigneshwaran to accept your pull request and I will can update
> the package.
>
> Best regards,
>
> --
> Paulo Henrique de Lima Santana (phls)
> Membro da Comunidade Curitiba Livre
> Fone: +55 (41) 9198-1897
> Site: http://www.phls.com.br
> GNU/Linux user: 228719  GPG ID: 0443C450
>
> Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)
> http://www.heforshe.org/pt
>

Bug#842939: WOT found guilty to sell user data

[ilf]

kpcyrd:
I think this project doesn't align with the debian goals and I would 
welcome if it's getting removed from current and future releases.


Mozilla removed it from addons.mozilla.org: 
http://www.faz.net/aktuell/politik/skandal-um-datenschnueffler-mozilla-loescht-web-of-trust-erweiterung-14511304.html


I think Debian should do the same.

--
ilf

Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg!
-- Eine Initiative des Bundesamtes für Tastaturbenutzung


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> found 841341 1.01-2
Bug #841341 [bd] bd "Bad substitution" if /bin/sh is not bash
Marked as found in versions bd/1.01-2.
>
End of message, stopping processing here.

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

Bug#841299: marked as done (patsy: FTBFS (AssertionError))

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 21:22:07 -0400
with message-id <20161104012207.5eyr4fit56xbm...@hopa.kiewit.dartmouth.edu>
and subject line Re: Bug#841299: patsy: FTBFS (AssertionError)
has caused the Debian Bug report #841299,
regarding patsy: FTBFS (AssertionError)
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.)


-- 
841299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:patsy
Version: 0.4.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
: # Explicit build system to avoid use of all-in-1 Makefile
dh build-indep --buildsystem=python_distutils --with python2,python3
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
python3.5 setup.py build
running build
running build_py

[... snipped ...]

0.0  0  19,   0   1
0.052632  1  18,   0   1
0.105263  2  17,   0   1
0.157895  3  16,   0   1
0.210526  4  15,   0   1
0.263158  5  14,   0   1
0.315789  6  13,   0   1
0.368421  7  12,   0   1
0.421053  8  11,   0   1
0.473684  9  10,0  1
0.526316  10  9,0  1
0.578947  11  8,0  1
0.631579  12  7,0  1
0.6842ok

==
FAIL: patsy.test_build.test_return_type_pandas
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/patsy/test_build.py",
 line 428, in test_return_type_pandas
assert int_df.index.equals([10, 20, 30])
AssertionError

==
FAIL: patsy.test_highlevel.test_dmatrix_NA_action
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/patsy/test_highlevel.py",
 line 675, in test_dmatrix_NA_action
assert mat.index.equals([1, 2])
AssertionError

--
Ran 39 tests in 49.540s

FAILED (failures=2)
11  13  6,0  1
0.736842  14  5,0  1
0.789474  15  4,0  1
0.842105  16  3,0  1
0.894737  17  2,0  1
0.947368  18  1,   0  1
1.0  19  0]
debian/rules:56: recipe for target 'python-test2.7' failed
make[1]: *** [python-test2.7] Error 1
make[1]: Leaving directory '/<>'
debian/rules:33: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The relevant part of the build log is included above.

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

BTW: If you are looking for some build-depends to blame, "patsy" used to
build ok in stretch on 20161010, so it would be some package that
entered testing between 20161010 and 20161019.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.4.1+git34-ga5b54c2-1

I have just uploaded the snapshot of patsy, which built for me just fine
on sid and any other recent debian/ubuntu release for neurodebian.  So I
guess issue was resolved one way or another.  reopen if I am mistaken

On Wed, 19 Oct 2016, Santiago Vila wrote:

> Package: src:patsy
> Version: 0.4.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:

> 
> [...]
>  

Bug#840229: marked as done (texlive-latex-extra should Breaks: dblatex (<< 0.3.9-1~))

[Debian Bug Tracking System]

Your message dated Fri, 4 Nov 2016 02:19:49 +0100
with message-id <20161104011949.gc4...@zira.vinc17.org>
and subject line Re: Bug#840189: fixed in texlive-extra 2016.20161103-1
has caused the Debian Bug report #840229,
regarding texlive-latex-extra should Breaks: dblatex (<< 0.3.9-1~)
to be marked as done.

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

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


-- 
840229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840229
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 ---
Version: 2016.20161103-1

On 2016-11-04 09:34:05 +0900, Norbert Preining wrote:
> The version is still correct, as between the fixed version and 
> the version against the package breaks there is no other version
> in existence.

Indeed.

> So I consider this a bug that should be closed (with the correct
> bug number, though ;-)
> 
> Don't you agree?

Doing it now.

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

Bug#840189: fixed in texlive-extra 2016.20161103-1

[Norbert Preining]

> #840189 was the bug in dblatex itself (already closed in October).
> This should have been #840229:

Argg, indeed.

> fixed: the bug title says "dblatex (<< 0.3.9-1~)", but I can see for
> texlive-latex-extra 2016.20161103-1:
> 
> Breaks: dblatex (<< 0.3.8-2~), [...]

Well, when I committed the change it was 0.3.8-2~, and nobody informed
me that there was 0.3.9-1 since then.

The version is still correct, as between the fixed version and 
the version against the package breaks there is no other version
in existence.

So I consider this a bug that should be closed (with the correct
bug number, though ;-)

Don't you agree?

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Processed: Add the source version

[Debian Bug Tracking System]

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

> found 828332 0.11.1-1
Bug #828332 [src:grpc] grpc: FTBFS with openssl 1.1.0
Marked as found in versions grpc/0.11.1-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#840189: fixed in texlive-extra 2016.20161103-1

[Debian Bug Tracking System]

Processing control commands:

> notfixed 840189 texlive-extra/2016.20161103-1
Bug #840189 {Done: Norbert Preining } [dblatex] dblatex 
fails in pdflatex: Use of \@xmultirow doesn't match its definition
Bug #840291 {Done: Norbert Preining } [dblatex] 
auto-multiple-choice: FTBFS: ! Use of \@xmultirow doesn't match its definition.
Ignoring request to alter fixed versions of bug #840189 to the same values 
previously set
Ignoring request to alter fixed versions of bug #840291 to the same values 
previously set

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

Processed: Re: Bug#840189: fixed in texlive-extra 2016.20161103-1

[Debian Bug Tracking System]

Processing control commands:

> notfixed 840189 texlive-extra/2016.20161103-1
Bug #840189 {Done: Norbert Preining } [dblatex] dblatex 
fails in pdflatex: Use of \@xmultirow doesn't match its definition
Bug #840291 {Done: Norbert Preining } [dblatex] 
auto-multiple-choice: FTBFS: ! Use of \@xmultirow doesn't match its definition.
No longer marked as fixed in versions texlive-extra/2016.20161103-1.
No longer marked as fixed in versions texlive-extra/2016.20161103-1.

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

Bug#840189: fixed in texlive-extra 2016.20161103-1

[Vincent Lefevre]

Control: notfixed 840189 texlive-extra/2016.20161103-1

(wrong bug number, see below)

Hi Norbert,

On 2016-11-03 07:56:07 +, Norbert Preining wrote:
> 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.
[...]
>* break against old dblatex (Closes: #840189)

#840189 was the bug in dblatex itself (already closed in October).
This should have been #840229:

  texlive-latex-extra should Breaks: dblatex (<< 0.3.9-1~)

But before closing this bug, I'm wondering whether it has really been
fixed: the bug title says "dblatex (<< 0.3.9-1~)", but I can see for
texlive-latex-extra 2016.20161103-1:

Breaks: dblatex (<< 0.3.8-2~), [...]

This doesn't match!

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

Processed: Not relevant for jessie

[Debian Bug Tracking System]

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

> tags 808850 sid stretch
Bug #808850 [src:xfonts-wqy] xfonts-wqy: FTBFS: Type of arg 1 to shift must be 
array (not constant item) at ./bdfmerge.pl line 35, near "ARGV)"
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Processed: Bug is also in the stretch version

[Debian Bug Tracking System]

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

> tags 804585 stretch
Bug #804585 [src:pywbem] pywbem: FTBFS: ssl3 is gone from openssl
Added tag(s) stretch.
> tags 808517 stretch
Bug #808517 [src:ruby-rails-autolink] ruby-rails-autolink: FTBFS: uninitialized 
constant ActionDispatch::Assertions::DomAssertions (NameError)
Added tag(s) stretch.
> found 808850 0.9.9-7
Bug #808850 [src:xfonts-wqy] xfonts-wqy: FTBFS: Type of arg 1 to shift must be 
array (not constant item) at ./bdfmerge.pl line 35, near "ARGV)"
Marked as found in versions xfonts-wqy/0.9.9-7.
> tags 810349 stretch
Bug #810349 [src:linux-patch-grsecurity2] linux-patch-grsecurity2: removal of 
linux-patch-grsecurity2?
Added tag(s) stretch.
> reassign 812304 libv8-3.14 3.14.5.8-8.1
Bug #812304 [libv8-3.14] libv8-3.14: FTBFS with GCC 6: x64.release.check crashed
Ignoring request to reassign bug #812304 to the same package
Bug #812304 [libv8-3.14] libv8-3.14: FTBFS with GCC 6: x64.release.check crashed
There is no source info for the package 'libv8-3.14' at version '3.14.5.8-8.1' 
with architecture ''
Unable to make a source version for version '3.14.5.8-8.1'
Marked as found in versions 3.14.5.8-8.1; no longer marked as found in versions 
3.14.5.8-10.
> found 813412 0.86.5+build1
Bug #813412 [src:unattended-upgrades] unattended-upgrades: FTBFS with testsuite 
errors
Marked as found in versions unattended-upgrades/0.86.5+build1.
> found 818327 0.11.1-1
Bug #818327 [libgrpc-dev] missing protoc plugin
Marked as found in versions grpc/0.11.1-1.
> tags 825608 stretch
Bug #825608 [libnet-jifty-perl] libnet-jifty-perl: FTBFS: t/006-uploads.t 
failure
Added tag(s) stretch.
> found 828332 0.11.1-1+b1
Bug #828332 [src:grpc] grpc: FTBFS with openssl 1.1.0
The source 'grpc' and version '0.11.1-1+b1' do not appear to match any binary 
packages
Marked as found in versions grpc/0.11.1-1+b1.
> found 835811 2.5.0-2
Bug #835811 [src:libica] libica: FTBFS with openssl 1.1.0
Marked as found in versions libica/2.5.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
804585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804585
808517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808517
808850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808850
810349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810349
812304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812304
813412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813412
818327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818327
825608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825608
828332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828332
835811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#843079: Bug#843107: python-mpop: FTBFS: ImportError: No module named trollsift.parser

[Antonio Valentino]

Il 03/11/2016 22:52, Sebastiaan Couwenberg ha scritto:
> severity 843079 serious
> merge 843079 843107
> thanks
> 
> On 11/03/2016 10:30 PM, Chris Lamb wrote:
>> python-mpop fails to build from source in unstable/amd64:
>> [...]
>> File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 2001, in 
>> _check_size
>>   raise ValueError("Width and Height must be > 0")
> 
> On Thu, 3 Nov 2016 18:44:47 +0100 Matthias Klose wrote:
>> the autopkg tests are failing:
>> [...]
>>   File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 2001, in
> _check_size
>> raise ValueError("Width and Height must be > 0")
> 
> You can thank yesterdays Pillow 3.4.2 upload for that.
> 
> Antonio, can you have a look at this?
> 
> Kind Regards,
> 
> Bas
> 


New bug opened to upstream:

https://github.com/pytroll/mpop/issues/38

-- 
Antonio Valentino

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-11-03 23:39:32 [+0100], László Böszörményi (GCS) wrote:
>  OK, it remained the same then. May you try the work in progress
> update[1]? I'm off for sleeping. :-/

yup, worked.

> Thanks,
> Laszlo/GCS

Sebastian

Bug#843111: llvm-toolchain-3.7: FTBFS on i386

[Emilio Pozuelo Monfort]

Source: llvm-toolchain-3.7
Version: 1:3.7.1-3
Severity: serious

Hi,

Your package failed to build on i386. We need llvm 3.7 in testing/stretch
for ghc 8 (then we can remove llvm 3.5), thus opening this bug.

Cheers,
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#828299: fetchmail: FTBFS with openssl 1.1.0

[GCS]

On Thu, Nov 3, 2016 at 11:16 PM, Sebastian Andrzej Siewior
 wrote:
> On 2016-11-03 22:02:23 [+0100], László Böszörményi (GCS) wrote:
>>  Nope. Tried in a loop of ten with -j2, other ten with -j4 and another
>> ten with -j8 and it was working correctly. What's the result / current
>> problem at your end?
>
> As you see in [0]:
 OK, it remained the same then. May you try the work in progress
update[1]? I'm off for sleeping. :-/

Thanks,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/fetchmail_6.3.26-3.dsc

Processed: Re: Processed (with 1 error): this and that

[Debian Bug Tracking System]

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

> forwarded 828477 https://community.openvpn.net/openvpn/ticket/759
Bug #828477 [src:openvpn] openvpn: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://community.openvpn.net/openvpn/ticket/759'.
> thanks
Stopping processing here.

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

Processed (with 1 error): this and that

[Debian Bug Tracking System]

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

> forward 828477 https://community.openvpn.net/openvpn/ticket/759
Unknown command or malformed arguments to command.
> retitle 828299 fetchmail: FTBFS if building in parallel
Bug #828299 [src:fetchmail] fetchmail: FTBFS with openssl 1.1.0
Changed Bug title to 'fetchmail: FTBFS if building in parallel' from 
'fetchmail: FTBFS with openssl 1.1.0'.
> thanks
Stopping processing here.

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

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-11-03 22:02:23 [+0100], László Böszörményi (GCS) wrote:
> On Thu, Nov 3, 2016 at 8:48 PM, Sebastian Andrzej Siewior
>  wrote:
> > On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> > fetchmail builds against openssl 1.1.0. So we are good here.
> > fetchmail fails to build with -j4.
> > What do we do now? I retitled the bug. Can you reproduce this on your
> > end?
>  Nope. Tried in a loop of ten with -j2, other ten with -j4 and another
> ten with -j8 and it was working correctly. What's the result / current
> problem at your end?

As you see in [0]:

|dpkg-buildpackage: info: host architecture amd64
| fakeroot debian/rules clean
|dh_testdir
|dh_testroot
|rm -f build-stamp configure-stamp
|[ ! -f Makefile ] || /usr/bin/make distclean
|rm -f po/*.gmo config.sub config.guess config.status
|dh_clean -X.orig -X.rej
| debian/rules build-arch
|set -e
|set -e
|dh_testdir
|dh_testdir
|/usr/bin/make
|make[1]: Entering directory '/<>'
|make[1]: *** No targets specified and no makefile found.  Stop.
|make[1]: Leaving directory '/<>'
|cp /usr/share/misc/config.sub config.sub
|debian/rules:138: recipe for target 'build-stamp' failed
|make: *** [build-stamp] Error 2
|make: *** Waiting for unfinished jobs
|cp /usr/share/misc/config.guess config.guess
|./configure  --build x86_64-linux-gnu --prefix=/usr --enable-nls \
|   --disable-fallback  --with-ssl=/usr --enable-NTLM --enable-SDPS 
--with-kerberos5 --with-gssapi=/usr
…
|sed -e "s/-lcrypt//; s/-lk5crypto//g;"  < Makefile > Makefile.tmp
|mv Makefile.tmp Makefile
|touch configure-stamp
|dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
|
|Build finished at 2016-08-26T18:31:07Z

The build-arch and clean rule run in parallel. This was triggered by "sbuild 
-j4 fetch….dsc"

[0] 
https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/fetchmail_6.3.26-2_amd64-2016-08-26T18%3A30%3A26Z

> Laszlo/GCS

Sebastian

Bug#843107: python-mpop: FTBFS: ImportError: No module named trollsift.parser

[Sebastiaan Couwenberg]

severity 843079 serious
merge 843079 843107
thanks

On 11/03/2016 10:30 PM, Chris Lamb wrote:
> python-mpop fails to build from source in unstable/amd64:
> [...]
> File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 2001, in 
> _check_size
>   raise ValueError("Width and Height must be > 0")

On Thu, 3 Nov 2016 18:44:47 +0100 Matthias Klose wrote:
> the autopkg tests are failing:
> [...]
>   File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 2001, in
_check_size
> raise ValueError("Width and Height must be > 0")

You can thank yesterdays Pillow 3.4.2 upload for that.

Antonio, can you have a look at this?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#835437: pycurl: FTBFS too much often (failing tests)

[Sandro Tosi]

> I believe this bug to be essentially the same as the one regarding
> network access.

yeah i believe that's the case too, as looking at the logs you
attached to the bug there are several instances of trying to access
remote resources and the error out.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Processed: Re: Bug#843107: python-mpop: FTBFS: ImportError: No module named trollsift.parser

[Debian Bug Tracking System]

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

> severity 843079 serious
Bug #843079 [src:python-mpop] python-mpop's autopkg tests are failing
Severity set to 'serious' from 'important'
> merge 843079 843107
Bug #843079 [src:python-mpop] python-mpop's autopkg tests are failing
Bug #843107 [src:python-mpop] python-mpop: FTBFS: ImportError: No module named 
trollsift.parser
Merged 843079 843107
> thanks
Stopping processing here.

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

Bug#842891: marked as done (libimage-info-perl: XXE in SVG files)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 21:53:41 +
with message-id 
and subject line Bug#842891: fixed in libimage-info-perl 1.39-1
has caused the Debian Bug report #842891,
regarding libimage-info-perl: XXE in SVG files
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.)


-- 
842891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-info-perl
Version: 1.28-1
Severity: grave
Tags: security upstream fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=118099

Hi

[N.B.: Agreed, the severity might be set too high, but I think it
would be good to have the fix for stretch, thus the RC severity].

It was reported that Image::Info is suspectible to  XXE in SVG files.
Cf.

https://rt.cpan.org/Public/Bug/Display.html?id=118099
https://bugzilla.redhat.com/show_bug.cgi?id=1379556

It was already fixed in 1.39 upstream.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libimage-info-perl
Source-Version: 1.39-1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
libimage-info-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 22:34:29 +0100
Source: libimage-info-perl
Binary: libimage-info-perl
Architecture: source
Version: 1.39-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Salvatore Bonaccorso 
Closes: 840470 840471 842891
Description: 
 libimage-info-perl - allows extraction of meta information from image files
Changes:
 libimage-info-perl (1.39-1) unstable; urgency=medium
 .
   * Team upload.
   * Take over for the Debian Perl Group
   * debian/control: Added: Vcs-Git field (source stanza); Vcs-Browser
 field (source stanza); Homepage field (source stanza);
 ${misc:Depends} to Depends: field. Changed: Maintainer set to Debian
 Perl Group  (was: Don
 Armstrong ); Don Armstrong  moved to
 Uploaders.
   * debian/watch: use metacpan-based URL (Closes: #840471)
   * Remove deprecation note in long description (Closes: #840470)
   * Convert debian/copyright to format as specified by copyright-format 1.0
   * Convert source package to '3.0 (quilt)' source package format
   * Remove commentes from debian/watch file
   * Replace versioned Build-Depends-Indep on perl with unversioned dependency.
 Replace the versioned Build-Depeneds-Indep on perl (>= 5.6.0-17) with an
 unversioned Build-Depends-Indep on perl only.
   * New upstream version 1.39
 - Fixes XXE in SVG files (Closes: #842891)
   * Add debian/upstream/metadata for upstream meta-information
   * debian/rules: Simplify rules file to a tiny rules makefile
   * Declare compliance with Debian policy 3.9.8
   * Add (preferred) (Build-)Depends(-Indep) on libxml-libxml-perl.
 Image::Info can use both XML::LibXML::Reader or XML::Simple, but
 XML::LibXML::Reader is preferred.
   * debian/copyright: Add stanzas for new files included upstream
   * Declare package as autopkgtest'able
   * debian/control: Wrap and sort (Build-)Depends(-Indep) fields
   * Add alternative (Build-)Depends(-Indep) for PerlIO::scalar.
 The module requires either PerlIO::scalar 0.21 (which is in Perl core
 5.21.7) or if not present IO::Scalar. Add the alternative
 (Build-)Depends(-Indep) for easier backporting.
   * debian/control: Remove Priority and Section filed in binary package stanza
   * Mention Perl module name in long description
   * Add fix-spelling-error-in-manpage.patch patch
   * Add fix-manpage-has-errors-from-pod2man.patch patch
   * Add dh_auto_install override to not install Bundle:: modules.
 Avoid as well installing the generated manpages for the Bundle::
 modules. They 

Bug#828550: socat: FTBFS with openssl 1.1.0

[Sandro Tosi]

On Thu, Nov 3, 2016 at 3:59 PM, László Böszörményi (GCS)  
wrote:
> On Thu, Nov 3, 2016 at 8:42 PM, Sandro Tosi  wrote:
>> On Mon, 5 Sep 2016 10:53:05 +0200 Gerhard Rieger
>>  wrote:
>>> Thank you, I will check!
>>
>> hey Gerhard, do you have a plan to look at this soon (now that openssl
>> 1.1.0 bugs are RC)? thanks!
>  Anything wrong with Sebastian Andrzej Siewior's patch? I plan to use
> if no one objects.

not from me (but i dont know anything about it :) ) i was just
checking if there was some problem that prevented Gerhard to update
the pkg. László if you have time and can prepare an updated pkg that'd
be great!

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#843107: python-mpop: FTBFS: ImportError: No module named trollsift.parser

[Chris Lamb]

Source: python-mpop
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,

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

  […]

  creating build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_geo_image.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_doc.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/__init__.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_mipp.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_scene.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_plugin.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_seviri.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_channel.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_image.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_visir.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_satin_helpers.py -> 
build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_nc_pps_l2.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_satellites.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_pp_core.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_projector.py -> build/lib.linux-x86_64-2.7/mpop/tests
  copying mpop/tests/test_viirs_sdr.py -> build/lib.linux-x86_64-2.7/mpop/tests
  env 
PYTHONPATH=/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0
 
PPP_CONFIG_DIR=/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/etc
 \
/usr/bin/make -C doc html
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/doc'
  sphinx-build -b html -d build/doctrees   source build/html
  Running Sphinx v1.4.8
  making output directory...
  loading pickled environment... not yet created
  loading intersphinx inventory from 
/usr/share/doc/python-doc/html/objects.inv...
  building [mo]: targets for 0 po files that are out of date
  building [html]: targets for 7 source files that are out of date
  updating environment: 7 added, 0 changed, 0 removed
  reading sources... [ 14%] image
  reading sources... [ 28%] index
  reading sources... [ 42%] input
  reading sources... [ 57%] install
  reading sources... [ 71%] pp
  reading sources... [ 85%] quickstart
  reading sources... [100%] saturn
  
  
/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/mpop/satin/viirs_sdr.py:docstring
 of mpop.satin.viirs_sdr.ViirsSDRReader.get_sunsat_angles:4: ERROR: Unexpected 
indentation.
  
/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/mpop/satin/viirs_sdr.py:docstring
 of mpop.satin.viirs_sdr.ViirsSDRReader.get_sunsat_angles:5: WARNING: Block 
quote ends without a blank line; unexpected unindent.
  
/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/doc/source/input.rst:58:
 WARNING: autodoc: failed to import module u'mpop.satin.hdfeos_l1b'; the 
following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
import_object
  __import__(self.modname)
File 
"/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/mpop/satin/hdfeos_l1b.py",
 line 41, in 
  from trollsift.parser import Parser, globify
  ImportError: No module named trollsift.parser
  
/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/doc/source/input.rst:85:
 WARNING: autodoc: failed to import module u'mpop.satin.hrpt'; the following 
exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
import_object
  __import__(self.modname)
File 
"/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/mpop/satin/hrpt.py",
 line 48, in 
  SATPOS_DIR = 
os.path.sep.join(os.environ["AAPP_PREFIX"].split(os.path.sep)[:-1])
File "/usr/lib/python2.7/UserDict.py", line 40, in __getitem__
  raise KeyError(key)
  KeyError: 'AAPP_PREFIX'
  
/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/doc/source/input.rst:94:
 WARNING: autodoc: failed to import module u'mpop.satin.eps1a'; the following 
exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
import_object
  __import__(self.modname)
File 
"/home/lamby/temp/cdt.20161103212915.XxOo8TNjqe.db.python-mpop/python-mpop-1.3.0/mpop/satin/eps1a.py",
 line 45, in 
  SATPOS_DIR = 
os.path.sep.join(os.environ["AAPP_PREFIX"].split(os.path.sep)[:-1])
File 

Bug#828495: marked as done (pgadmin3: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 21:30:47 +
with message-id 
and subject line Bug#828495: fixed in pgadmin3 1.22.1-2
has caused the Debian Bug report #828495,
regarding pgadmin3: 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.)


-- 
828495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgadmin3
Version: 1.22.1-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/pgadmin3_1.22.1-1_amd64-20160530-2114

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: pgadmin3
Source-Version: 1.22.1-2

We believe that the bug you reported is fixed in the latest version of
pgadmin3, 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.
Christoph Berg  (supplier of updated pgadmin3 
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:43:12 +0100
Source: pgadmin3
Binary: pgadmin3 pgadmin3-dbg pgadmin3-data
Architecture: source
Version: 1.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 pgadmin3   - graphical administration tool for PostgreSQL
 pgadmin3-data - graphical administration tool for PostgreSQL - documentation
 pgadmin3-dbg - graphical administration tool for PostgreSQL (debugging symbols)
Closes: 828495
Changes:
 pgadmin3 (1.22.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Switch to libssl1.0-dev. (Closes: #828495)
   * Bump maximum supported version to 9.6.
Checksums-Sha1:
 6e87191696b41483764dc926822eca2733424c31 2291 pgadmin3_1.22.1-2.dsc
 bb539ea5ccbdbe9cef0ca6a52cfefb167a559e07 18980 pgadmin3_1.22.1-2.debian.tar.xz
Checksums-Sha256:
 18036c371347b3e5e7d2f3b87d995c119e63609b90ac26caf43bbdee4088b230 2291 
pgadmin3_1.22.1-2.dsc
 ef12791bf49c84fb948f9333f932664916c1b737ec7210931b47b6604f874d30 18980 
pgadmin3_1.22.1-2.debian.tar.xz
Files:
 28d8d01dd804d28a0f9b8c0c04b59f9f 2291 database optional pgadmin3_1.22.1-2.dsc
 0c9307ed7a3767eb3c9c9142c65d9ef2 18980 database optional 
pgadmin3_1.22.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYG6GkAAoJEExaa6sS0qeuYZwQAJCA8d0YjW+R8R32JBP88tRS
hqlyHRORiQYAQCAgTxA6jcevoSFrsrGIljuf+UGJ03AFDqbtzFq6VgA8L1ZBr5gE
wxVEQ5ZpMa44qTxOpmxxPhkI/Sg+r+NvbzFWxT2BTHhgIQeRegQeTbr9wjTvesd9
PG3P5PFByGiVQsKYY5IAq3rHH9LnwcC7m4zXf4WlmNGObUKYbefJyU8dtHuEPHPx
IY7k053tk+QkuYtOB9IPnUkWQZx1cv2a6Sl1HVBkAHhtnAlu03W3tHYGD02sy5hW
W0ahUesjiIAP2/fA/72P0rE6U9JJiLEJtrLW4JHKfDS5ew8kHSog6hMyQi6GweMJ
ZTce3xyWHdYEdKfS2UJ4KlpOzZXdE7ea5TVQYKsj5/DVVsgCkYNqe/xZwOhhv/c8
25v+JLRNXPBAt1asNIOk9WxJfLlbXNAUbNfTwA6Y12tHV0+EcA6RpUxHLAWm7dA5
kUqDP17R2KUnY9xZMQsjUPJSBEbdbKLL9c05S8ND3+ilQpL7vyTEnwencUxr8S+s
yK9AIacp/luczGVYNwDY1n6PmsOfsS5Gm2ubeM+WwFiK2fux4j67SHHlyChVA+Sb
QQJHabcr7ZHcAQETKLqzHIeiX3XfnM3PbwIc/hXQzvqN4smDQl1cRFUbfTVF38D7
vJCVXZV0dEPNT0v6YfOR
=CRmc
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 21:31:27 +
with message-id 
and subject line Bug#843036: fixed in python-flake8 3.0.4+dfsg1-3
has caused the Debian Bug report #843036,
regarding python-flake8: FTBFS (failing tests)
to be marked as done.

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

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


-- 
843036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

Bug#828383: marked as done (libclamunrar: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 21:28:08 +
with message-id 
and subject line Bug#828383: fixed in libclamunrar 0.99-2
has caused the Debian Bug report #828383,
regarding libclamunrar: 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.)


-- 
828383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libclamunrar
Version: 0.99-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/libclamunrar_0.99-1_amd64-20160530-2111

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: libclamunrar
Source-Version: 0.99-2

We believe that the bug you reported is fixed in the latest version of
libclamunrar, 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.
Sebastian Andrzej Siewior  (supplier of updated 
libclamunrar 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 21:39:40 +0100
Source: libclamunrar
Binary: libclamunrar7
Architecture: source
Version: 0.99-2
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Description:
 libclamunrar7 - anti-virus utility for Unix - unrar support
Closes: 828383
Changes:
 libclamunrar (0.99-2) unstable; urgency=medium
 .
   * Add patches from upstream bugzilla bb11600 and bb11601 to fix out of band
 access
   * drop openssl check (Closes: #828383).
Checksums-Sha1:
 5fa5507b8c489ce27ba06d3c3f687d59c61765bb 2140 libclamunrar_0.99-2.dsc
 b379f74f88491c502f632525902a961f1e224dbd 7460 libclamunrar_0.99-2.debian.tar.xz
Checksums-Sha256:
 4915c0d8cba152b64c840cf6fdd8c0d8307ed34dcd34882bae57d5b1faee635c 2140 
libclamunrar_0.99-2.dsc
 cc1cc634d92d4a96af2fdb4ed7d01216968c1aec226ccd23467ae1dfd7068cd8 7460 
libclamunrar_0.99-2.debian.tar.xz
Files:
 b3df8167fa0dcbd8cdf42d8673bd5da0 2140 non-free/libs extra 
libclamunrar_0.99-2.dsc
 30d75f33ae342507a26db2098b8867a4 7460 non-free/libs extra 
libclamunrar_0.99-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQI1BAEBCgAfBQJYG6ICGBxzZWJhc3RpYW5AYnJlYWtwb2ludC5jYwAKCRB7lugW
Koz10fzJD/9sEkDEMQxQqlCsvgJTcrLr79x3GrPaMkecl9NZ+KhZ/kU3tiM6kgEH
RaMkyDeDX5uQLGNTa0o1QkYiob7lluFyTZOTczjmuRFp+i7GPAU3083MTIzo03YL
N7PXsHOcdfncDeBxLsYwaqZzLOVD/frOnncpFJxuYHHpswH7CQpsyQ6pegnjC9zg
7XPING/GLIKmNwZesWT5zb8Xiu3rkmbQuHgTjkAKrhjzIovZKlC2ckal0zmxU0rR
8UvScH11CD65sqzCIPClPeWtJmc7gWFCQand+5mx/lT2Jbfi+SjOq8JP4+QrS/yS
rTBsy+VBTIDUp8Xj8SWNy/iGWl+G6849aLncl2oEj1RBFytW7UGu7FiZne4XkD3P
xaSJ7g6NmtvDlr0KBWC04cqNZF5ovJOwOjdgyvizAUnYLYQ91N+klC2I54ySKlOY
PMNdHJ0mAnIbS2FpoGd3ppuyAIKSVfCxAMNo3aZyEqd/4oe8tippSdKn7WrCfSM9
ybC8xwS3sYnbTJkRDMJj7Yut9vvdAOdD2NThIDldEaFzEaXvGHlnFEpak4BsgcUL
IPKU0rJ8d/gCKNn/TJvKV5Rm96Jdtq9KUVvobJRdBwANVZD0F+fHOqWVt/GjF3iP
1rv/rcO+TMBbvsTkGKu4fmUYJhdm7X5dgm8B551RYQf8Q3pTL8woVg==
=aiCI
-END PGP SIGNATURE End Message ---

Processed: Bug is also in stretch

[Debian Bug Tracking System]

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

> tags 806544 +stretch
Bug #806544 [libical-parser-sax-perl] libical-parser-sax-perl: FTBFS: 
t/01parse.t failure
Added tag(s) stretch.
> tags 841302 +stretch
Bug #841302 [ngraph-gtk] ngraph-gtk: FTBFS on mips*:  ngraph segfaults on 
testing
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#841705: marked as done ([lshw] lshw 02.18-0.1 hangs Stretch)

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 17:19:47 -0400
with message-id 

and subject line Re: [lshw] lshw 02.18-0.1 hangs Stretch
has caused the Debian Bug report #841705,
regarding [lshw] lshw 02.18-0.1 hangs Stretch
to be marked as done.

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

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


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

--- Please enter the report below this line. ---
Just executing lshw as root causes the monitor to go blank, after a few
seconds the desktop reappears but it's unresponsive. The desktop
disappearing and reappearing repeats for a minute or two before
rebooting.

The Magic Sys Rq key combination allows me to reboot the PC.

There's nothing in /var/log/* that relates to the hang.

Please ask if there's anything I can do to provide more information.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.7.0-1-amd64

Debian Release: stretch/sid
  500 testing ftp.uk.debian.org 
  500 stable  ftp.videolan.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends (Version) | Installed
=-+-===
libc6   (>= 2.14) | 
libgcc1(>= 1:3.0) | 
libstdc++6   (>= 5.2) | 


Recommends  (Version) | Installed
=-+-===
pciutils  | 1:3.3.1-1.1
usbutils  | 1:007-4


Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Thu, Nov 3, 2016 at 4:15 PM, Derek  wrote:
> I've tried lshw again but now there's plenty of
> info being logged and it is a problem with Radeon.

perfect, closing this bug then!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi--- End Message ---

Bug#817389: marked as done (cdbackup: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 21:20:38 +
with message-id 
and subject line Bug#817389: fixed in cdbackup 0.7.1-1
has caused the Debian Bug report #817389,
regarding cdbackup: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: cdbackup
Source-Version: 0.7.1-1

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

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

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

Debian distribution maintenance software
pp.
David William Richmond Jones  (supplier of updated cdbackup 
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:01:26 +
Source: cdbackup
Binary: cdbackup
Architecture: source
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: David William Richmond Jones 
Description:
 cdbackup   - CD-R(W) backup utility
Closes: 647972 783453 817389
Changes:
 cdbackup (0.7.1-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release
   * Set maintainer to Debian QA Group
   * Updated to debhelper 9 (Closes: #817389)
   * Converted to quilt (3.0)
   * Added misc depends
   * Fix FTBFS on hurd-i386 (Closes: #647972)
   * Make build reproducible (Closes: #783453)
   * Converted debian/copyright to DEP-5
Checksums-Sha1:
 1a111ed35b1724c21e6363bedbcfcc2d5b771da0 1681 cdbackup_0.7.1-1.dsc
 64d4a647a1ba248e727dc93f3410c757f8e17d96 22710 cdbackup_0.7.1.orig.tar.gz
 ab36e496de703dab17c9d5b357be74791d93044c 5592 cdbackup_0.7.1-1.debian.tar.xz
Checksums-Sha256:
 6fd4e84a70d7b06d2edd01a9d43bc2cf93f5e6302e7e782346cddc5eab40eb81 1681 
cdbackup_0.7.1-1.dsc
 b9d94acd0065c243b2a9d5a47af768ddae003f81a181a61155065a11bb59449c 22710 
cdbackup_0.7.1.orig.tar.gz
 2045ed53f1cbef5e5566296310a950dc6a130c78b68ae3743469925ce4c3d916 5592 
cdbackup_0.7.1-1.debian.tar.xz
Files:
 475d479339012bf24209325f91ffd563 1681 admin extra cdbackup_0.7.1-1.dsc
 92913f7c8850ae38cce86da4014e967c 22710 admin extra cdbackup_0.7.1.orig.tar.gz
 324910b3e4db7e5cc06dfb362d4b7197 5592 admin extra 
cdbackup_0.7.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYG6IoAAoJEPNPCXROn13Z7EsP/3BKznE2p0CKOfqKh6/xDJ2+
Sovj3CrYLHOBwWU+A9qGf21Mfjtboe0X+z/6dxuEd0ccUxQlbN54dL/TZ8yvEYoq
63KuaCYCv2xW6cmest/+R/JhFGY+M938mYUXj+aEEgYzRHJ11X86vskN8hhK5aIA
SmjjtGrAgnKldZPgGlEXXHwO3vhWGW9wWGL9hallsI2BrOx94qsNQKQqNty/j50w
rVQcWm1IijFMQqSz7rQBXKX9hrfx56KykP3kt68wlGx5L+te0ZpJVS4H/w2judPk
2kBTOoc/l9arbNIls5vjBU2KBCBSscSU81LdjG/OOe9nIcjuXV8+r13ziEouoNU0
1+j9q3djvf7x5hZidsXj7UhaWmj1pNteCr77NWNfkvNJ5Q0ZliBdcNpYtjzZ82+Q
OHNfazeWCYkPry+mRNJ4PfVBR78RhIk6P8e+qfLHMwZrwQbNWpjUPp6kK2hyW2Vo
djq0PWMI4mNy3eZurAGvttZxxIhnmuA/Xf2KMe+hvSp84ba2ZHSruASdI0a3bejT
Ij5LK8unwM8Y7DE3qC0SO2nh3YsUACTbRSptpMam9Q+Bv8zViJ50v3Mxwc7aJJo9
xT0TIAvkMIYW6YX7po1cja29BzlbcykkRBOBwdp50TagQOi5g2w6kS2mbu8HVbsI
bWk1icy70pnjd2+bjvZ1
=BPa5
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#819488: gparted crash with a libparted backtrace

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #819488 [src:parted] gparted crash with a libparted backtrace
Severity set to 'important' from 'grave'

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

Bug#819488: gparted crash with a libparted backtrace

[Sandro Tosi]

control: severity -1 important

On Thu, Nov 3, 2016 at 1:48 PM, Mattia Rizzolo  wrote:
> On Thu, Nov 03, 2016 at 11:37:02AM -0400, Sandro Tosi wrote:
>> Mattia, do you still consider this bug RC? thanks!
>
> I don't think so, no.  Though it's still a crash, it's important, but
> probably not RC indeed.

yup agreed on this, setting the severity accordingly


On Thu, Nov 3, 2016 at 4:34 PM, Phil Susi  wrote:
> On 11/3/2016 11:37 AM, Sandro Tosi wrote:
>> 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!
>
> I have not had time to work on it yet.

no worries!


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#819488: gparted crash with a libparted backtrace

[Phil Susi]

On 11/3/2016 11:37 AM, Sandro Tosi wrote:
> 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!

I have not had time to work on it yet.

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[GCS]

On Thu, Nov 3, 2016 at 8:48 PM, Sebastian Andrzej Siewior
 wrote:
> On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> fetchmail builds against openssl 1.1.0. So we are good here.
> fetchmail fails to build with -j4.
> What do we do now? I retitled the bug. Can you reproduce this on your
> end?
 Nope. Tried in a loop of ten with -j2, other ten with -j4 and another
ten with -j8 and it was working correctly. What's the result / current
problem at your end?

Laszlo/GCS

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Andreas Henriksson]

Hello Sebastian Andrzej Siewior.

On Thu, Nov 03, 2016 at 08:48:04PM +0100, Sebastian Andrzej Siewior wrote:
> control: retitle: -1 fetchmail: FTBFS if building in parallel
> 
> On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> > Hello Kurt Roeckx.
> Hi,
> 
> > 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?
> 
> fetchmail builds against openssl 1.1.0. So we are good here.
> fetchmail fails to build with -j4.
> What do we do now? I retitled the bug. Can you reproduce this on your
> end?

Disclaimer: I'm not the maintainer.

(And your retitle seems to have failed? One too many : after retitle?)
(And as already mentioned to Kurt, you might want to unblock the openssl
transition as well as this bug is not related to openssl.)

It seems build-arch depends on configure-stamp and build-stamp. The
latter two gets executed in parallel which results in build-stamp
getting executer before configure-stamp and thus the failure.

Since the fetchmail packaging currently uses a deprecated debhelper compat
level 7, preferrably it would get updated to a current level (and
switched to use the debhelper sequencer while at it).
While doing that upgrading/cleanup work on the packaging this bug will
likely go away.

Another (quick and dirty) option would be to completely disable parallel
execution of debian/rules, eg. by adding ".NOTPARALLEL:".

Another option that could also work is to make the build-stamp target
depend on configure-stamp hopefully fixes the parallelism bug and
probably a theoretically correct change no matter what.

Regards,
Andreas Henriksson

PS. Not volunteering for any of the above myself.

Processed: Fix from Ubuntu for the libgraphite-php FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #821517 [libgraphite-php] libgraphite-php: PHP 7.0 Transition
Added tag(s) patch.

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

Bug#821517: Fix from Ubuntu for the libgraphite-php FTBFS

[Adrian Bunk]

Control: tags -1 patch

The fix I found in Ubuntu for this bug is attached.

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

diff -pruN 1.5-1/debian/control 1.5-1ubuntu1/debian/control
--- 1.5-1/debian/control	2012-07-05 16:13:37.0 +
+++ 1.5-1ubuntu1/debian/control	2016-03-24 23:30:00.0 +
@@ -11,7 +12,7 @@ Homepage: http://graphite.ecs.soton.ac.u
 
 Package: libgraphite-php
 Architecture: all
-Depends: ${misc:Depends}, php5 (>= 5.0.0), libarc-php
+Depends: ${misc:Depends}, php, libarc-php
 Description: PHP Linked Data Library
  Graphite is a PHP RDF library, built on top of ARC2, which has been
  developed to make working with RDF easier and more fun.

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Sandro Tosi]

On Mon, 8 Aug 2016 13:24:48 + Mattia Rizzolo  wrote:
> source: xerces-c
> version: 3.1.3+debian-2.1
> severity: serious
>
> Dear maintainer,
>
> your package failed to build on buildds on the s390x architecure only
> during a rebuild for the transition to icu57, using gcc6 as compiler.
> You can see the build log at:
> https://buildd.debian.org/status/fetch.php?pkg=xerces-c=s390x=3.1.3%2Bdebian-2.1%2Bb1=1470418530

Hey William, did you have a chance to look at this bug? i couldnt find
much on the upstream bug tracker but there is also a 3.1.4 new release
you might want to test if fixes this bug else report it upstream.
thanks!!

Processed: closing 788862

[Debian Bug Tracking System]

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

> # won't fix in stable
> close 788862
Bug #788862 {Done: Vincent Bernat } [libevhtp-dev] 
libevhtp-dev: missing dependency to libonig-dev
Bug 788862 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#828550: socat: FTBFS with openssl 1.1.0

[GCS]

On Thu, Nov 3, 2016 at 8:42 PM, Sandro Tosi  wrote:
> On Mon, 5 Sep 2016 10:53:05 +0200 Gerhard Rieger
>  wrote:
>> Thank you, I will check!
>
> hey Gerhard, do you have a plan to look at this soon (now that openssl
> 1.1.0 bugs are RC)? thanks!
 Anything wrong with Sebastian Andrzej Siewior's patch? I plan to use
if no one objects.

Laszlo/GCS

Bug#842909: marked as done (freeplane: FTBFS: Execution failed for task ':freeplane:debianMavenPom'. > java.lang.NullPointerException (no error message))

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 20:50:53 +0100
with message-id <87lgx08hr6@bitburger.home.felix>
and subject line Fixed by gradle-debian-helper upload
has caused the Debian Bug report #842909,
regarding freeplane: FTBFS: Execution failed for task 
':freeplane:debianMavenPom'. > java.lang.NullPointerException (no error message)
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.)


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

freeplane fails to build from source in unstable/amd64:

  […]

  Compiling build file 
'/home/lamby/temp/cdt.20161102092707.463VoM229Y.db.freeplane/freeplane-1.5.16/freeplane_plugin_svg/build.gradle'
 using BuildScriptTransformer.
Replacing org.apache.xmlgraphics:batik-anim:jar:1.7  ->  
org.apache.xmlgraphics:batik-anim:jar:debian
Replacing org.apache.xmlgraphics:batik-awt-util:jar:1.7  ->  
org.apache.xmlgraphics:batik-awt-util:jar:debian
Replacing org.apache.xmlgraphics:batik-bridge:jar:1.7  ->  
org.apache.xmlgraphics:batik-bridge:jar:debian
Replacing org.apache.xmlgraphics:batik-codec:jar:1.7  ->  
org.apache.xmlgraphics:batik-codec:jar:debian
Replacing org.apache.xmlgraphics:batik-css:jar:1.7  ->  
org.apache.xmlgraphics:batik-css:jar:debian
Replacing org.apache.xmlgraphics:batik-dom:jar:1.7  ->  
org.apache.xmlgraphics:batik-dom:jar:debian
Replacing org.apache.xmlgraphics:batik-extension:jar:1.7  ->  
org.apache.xmlgraphics:batik-extension:jar:debian
Replacing org.apache.xmlgraphics:batik-ext:jar:1.7  ->  
org.apache.xmlgraphics:batik-ext:jar:debian
Replacing org.apache.xmlgraphics:batik-gui-util:jar:1.7  ->  
org.apache.xmlgraphics:batik-gui-util:jar:debian
Replacing org.apache.xmlgraphics:batik-gvt:jar:1.7  ->  
org.apache.xmlgraphics:batik-gvt:jar:debian
Replacing org.apache.xmlgraphics:batik-parser:jar:1.7  ->  
org.apache.xmlgraphics:batik-parser:jar:debian
Replacing org.apache.xmlgraphics:batik-script:jar:1.7  ->  
org.apache.xmlgraphics:batik-script:jar:debian
Replacing org.apache.xmlgraphics:batik-svg-dom:jar:1.7  ->  
org.apache.xmlgraphics:batik-svg-dom:jar:debian
Replacing org.apache.xmlgraphics:batik-svggen:jar:1.7  ->  
org.apache.xmlgraphics:batik-svggen:jar:debian
Replacing org.apache.xmlgraphics:batik-swing:jar:1.7  ->  
org.apache.xmlgraphics:batik-swing:jar:debian
Replacing org.apache.xmlgraphics:batik-transcoder:jar:1.7  ->  
org.apache.xmlgraphics:batik-transcoder:jar:debian
Replacing org.apache.xmlgraphics:batik-util:jar:1.7  ->  
org.apache.xmlgraphics:batik-util:jar:debian
Replacing org.apache.xmlgraphics:batik-xml:jar:1.7  ->  
org.apache.xmlgraphics:batik-xml:jar:debian
Replacing rhino:js:jar:1.7R4  ->  rhino:js:jar:debian
Replacing :fop:jar:  ->  :fop:jar:
Replacing xml-apis:xml-apis:jar:1.4.01  ->  xml-apis:xml-apis:jar:debian
Replacing xml-apis:xml-apis-ext:jar:1.3.04  ->  
xml-apis:xml-apis-ext:jar:debian
Replacing xerces:xercesImpl:jar:2.11.0  ->  xerces:xercesImpl:jar:debian
Adding task debianMavenPom to project 'freeplane_plugin_svg'
Configuring javadoc links
  All projects evaluated.
  Selected primary task 'build' from project :
  Tasks to be executed: [task ':assemble', task ':check', task ':build', task 
':JOrtho_0.4_freeplane:compileJava', task 
':JOrtho_0.4_freeplane:processResources', task ':JOrtho_0.4_freeplane:classes', 
task ':JOrtho_0.4_freeplane:debianMavenPom', task ':JOrtho_0.4_freeplane:jar', 
task ':JOrtho_0.4_freeplane:assemble', task ':JOrtho_0.4_freeplane:check', task 
':JOrtho_0.4_freeplane:build', task ':freeplane:compileJava', task 
':freeplane:processResources', task ':freeplane:classes', task 
':freeplane:debianMavenPom', task ':freeplane:editorJar', task 
':freeplane:osgiJar', task ':freeplane:viewerJar', task ':freeplane:jar', task 
':freeplane:assemble', task ':freeplane:check', task ':freeplane:copyDoc', task 
':freeplane:copyGitProperty', task ':freeplane:copyGitTxt', task 
':freeplane:createGitProperty', task ':freeplane:copyExternalResources', task 
':freeplane:doNotSignViewerJar', task ':freeplane:signViewerJarNoTsa', task 
':freeplane:signViewerJarTsa', task ':freeplane:copyOSGiJars', task 

Processed: forwarded 828565 https://github.com/balabit/syslog-ng/issues/1234

[Debian Bug Tracking System]

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

> forwarded 828565 https://github.com/balabit/syslog-ng/issues/1234
Bug #828565 [src:syslog-ng] syslog-ng: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://github.com/balabit/syslog-ng/issues/1234'.
> thanks
Stopping processing here.

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

Processed: fixed 842979 in 0.18.0-2

[Debian Bug Tracking System]

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

> fixed 842979 0.18.0-2
Bug #842979 [python-napalm-base] Missing dependency on python-jtextfsm
Marked as fixed in versions napalm-base/0.18.0-2.
> thanks
Stopping processing here.

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

Bug#841610: statsmodels: FTBFS: TypeError: cannot sort an Index object in-place, use sort_values instead

[Sandro Tosi]

* the Anova errors seem related to
https://github.com/statsmodels/statsmodels/issues/3228

* "ValueError: Inferred frequency MS from passed dates does not
conform to passed frequency M" could be related to the absence of
tzdata (but the last function of the stacktrace is in pandas so the
bug may be there)

* "TypeError: cannot sort an Index object in-place, use sort_values
instead" may or may not be a problem in pandas (since there was a
recent update of pandas you might want to retry and see if that fixed
them, if not maybe you can ask statsmodels upstream what they think

thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: retitle: -1 fetchmail: FTBFS if building in parallel

On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> Hello Kurt Roeckx.
Hi,

> 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?

fetchmail builds against openssl 1.1.0. So we are good here.
fetchmail fails to build with -j4.
What do we do now? I retitled the bug. Can you reproduce this on your
end?

> Regards,
> Andreas Henriksson

Sebastian

Bug#828550: socat: FTBFS with openssl 1.1.0

[Sandro Tosi]

On Mon, 5 Sep 2016 10:53:05 +0200 Gerhard Rieger
 wrote:
> Thank you, I will check!

hey Gerhard, do you have a plan to look at this soon (now that openssl
1.1.0 bugs are RC)? thanks!

Bug#828388: marked as done (libcrypt-openssl-x509-perl: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 Nov 2016 19:35:54 +
with message-id 
and subject line Bug#828388: fixed in libcrypt-openssl-x509-perl 1.8.7-2
has caused the Debian Bug report #828388,
regarding libcrypt-openssl-x509-perl: 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.)


-- 
828388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-openssl-x509-perl
Version: 1.8.6-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/libcrypt-openssl-x509-perl_1.8.6-1_amd64-20160529-1439

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: libcrypt-openssl-x509-perl
Source-Version: 1.8.7-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcrypt-openssl-x509-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 20:09:04 +0100
Source: libcrypt-openssl-x509-perl
Binary: libcrypt-openssl-x509-perl
Architecture: source
Version: 1.8.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 828388
Description: 
 libcrypt-openssl-x509-perl - Perl extension to OpenSSL's X509 API
Changes:
 libcrypt-openssl-x509-perl (1.8.7-2) unstable; urgency=medium
 .
   * Remove Micah Anderson from Uploaders. Thanks for your work!
   * Cherry-pick two commits from upstream Git repo for OpenSSL 1.1.0
 compatibility (and 1.0.2 backwards compatibility). (Closes: #828388)
   * Update years of packaging copyright.
Checksums-Sha1: 
 39dde0e01d5022ccb89640437724f33fa92d5e18 2456 
libcrypt-openssl-x509-perl_1.8.7-2.dsc
 c14341c0bba2b3c1c3a00d1014d04df7b099ab26 7776 
libcrypt-openssl-x509-perl_1.8.7-2.debian.tar.xz
Checksums-Sha256: 
 1be93973d8548ea9b81f1284785828a8e6ab25f4d38de06b687ae4ce81c2d13b 2456 
libcrypt-openssl-x509-perl_1.8.7-2.dsc
 ceb431fc40ec363557ba67e95cd5897a2f6ee0cceb80194a934eedff2f651ac6 7776 
libcrypt-openssl-x509-perl_1.8.7-2.debian.tar.xz
Files: 
 15733266f665ba0d85eff3cc284f7133 2456 perl optional 
libcrypt-openssl-x509-perl_1.8.7-2.dsc
 8429b42295a27cfe068ae88a82939d28 7776 perl optional 
libcrypt-openssl-x509-perl_1.8.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYG4uqXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGVVEP/iQQJ1LwtT5RCvAvnbEwJAZB
qLqYLM0f1MakR4PZ4nzn+8PvtvPkLN0F4hFPn7Z3ZEt8j0KbsoEuclMJiy7IyZ5Z
xVuQgyIF77SqbKoppWjriSjQqKd23E3DSF5aG2vyfDZaimKP/AzBcnVzdEv1hCmV
izAZ+NY8ecxFsE725NnOLhJ6tzNf7A776N0t3Vwk8MOckCEA3km3KJmRuAZsivm1
jwnWUQotiNzLh1tvz83J5vy8EvpsDsb2U/ZCCmAX+R1BgUaLpcZOAd9d2Wtlq/8r
BMcgPknHdGBXGDmo8yqzqWpXx1QLMxVvodQlI2Dzin7yGd/FUa3p8Wx6EMl0z64b
h1B0AuSY2DaARveNQvZlKGYDUSY63QlCZH677aBaUd6CcaJId+luWspEnLj+OsUO
BiBD1RHoQUCXXWDBCZGRdhprEH/Rc94nt/ApcrYOqoOyPixjdN0t/W8YndqW2p9u
XwOhZ7uuVnpTrIM3+RBHViXlPm9c+BwTU1Vy/TLYPUKYXQ3RIK4Hk+R/wqThpjbu
x+t31fP4meW/NK9jKm/TJejGbYHz/rgHiRHDoyLScOJYAWoDEwu3YjX1RT3UA9ov
0eTcCYHPbFPGieVp8kXUoY1d18Qj2djKORSHgB8AdOPO/e672D6i8HqP5XkQG6nz
JGbWniTJYDueB0mqmdVr
=7Wmz
-END PGP SIGNATURE End Message ---

Bug#835437: pycurl: FTBFS too much often (failing tests)

[Santiago Vila]

Hi.

I believe this bug to be essentially the same as the one regarding
network access.

Chris downgraded the other bug to "important" because he was filing
serious bugs on the only basis that there was "network activity".

In this case, however, network access (and to be precise, expecting a
reply from the other side) is what makes the package to fail (it seems).

My recommendation: Please find the way to disable any tests which
perform network access, I have the strong feeling that the build would
never hang if those tests are disabled.

Thanks.

Bug#841420:

[Fabrizio]

I have same error with Debian testinh

This is my nvidia installer log:
https://goo.gl/hb1J3e

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Tianon Gravi]

On 31 October 2016 at 17:50, Tianon Gravi  wrote:
> Checking reverse dependencies...
> # Broken Build-Depends:
> golang-github-docker-go: golang-1.6-go
>  golang-1.6-src
>
> Dependency problem found.

After that last golang-github-docker-go upload, we're in better shape now:

$ ssh mirror.ftp-master.debian.org dak rm -Rn golang-1.6
Will remove the following packages from unstable:

golang-1.6 |1.6.3-2 | source, all
golang-1.6-doc |1.6.3-2 | all
golang-1.6-go |1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el
golang-1.6-src |1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el

Maintainer: Go Compiler Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Julian Taylor]

On 03.11.2016 20:17, Sandro Tosi wrote:
>> Looks like your last upload fixed the build on most architectures. However 
>> the
>> package still failed to build on arm64.
>>
>> https://buildd.debian.org/status/package.php?p=pyzmq
> 
> Hey Julian, do you have time to look at the failures in the
> https://buildd.debian.org/status/package.php?p=pyzmq ? it looks like
> upstream released 16.0.0 so it might worth a shot packaging it to see
> if that solves them. thanks!!
> 

I have packaged it though the tests are also unreliable on x86, still
needs to be looked at.

Bug#835437: pycurl: FTBFS too much often (failing tests)

[Barry Warsaw]

On Nov 03, 2016, at 02:03 PM, Sandro Tosi wrote:

>Hey Barry, did you have a chance to look at this? might be also just
>forward it upstream and see how that goes. Thanks!

I'm sorry, I haven't. :(


pgpI4eitBenxl.pgp
Description: OpenPGP digital signature

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/03/2016 07:39 AM, Bernhard Schmidt wrote:
> 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.

Hi,

I decided to try this: I made a sid chroot, manually downgraded to libssl-dev 
1.0.2j-1 from stretch, and built asterisk from the current packaging git head 
(ec0143a).
I actually enabled OpenSSL-1.1.0-support.patch while I was at it.

Ultimately, running this with pjproject 2.5.5~dfsg-2 failed at the same stage, 
but with a different assert:

asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: Assertion 
`sess && sess->endpt' failed.
Aborted

Processed: found 828393 in 2.1.4~alpha-0.1

[Debian Bug Tracking System]

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

> found 828393 2.1.4~alpha-0.1
Bug #828393 {Done: Helmut Grohne } [src:libevent] libevent: 
FTBFS with openssl 1.1.0
Marked as found in versions libevent/2.1.4~alpha-0.1 and reopened.
> thanks
Stopping processing here.

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

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Sandro Tosi]

> Looks like your last upload fixed the build on most architectures. However the
> package still failed to build on arm64.
>
> https://buildd.debian.org/status/package.php?p=pyzmq

Hey Julian, do you have time to look at the failures in the
https://buildd.debian.org/status/package.php?p=pyzmq ? it looks like
upstream released 16.0.0 so it might worth a shot packaging it to see
if that solves them. thanks!!

Bug#839460: python-tz: FTBFS: Tests failures

[Sandro Tosi]

> 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

this looks a lot like the reason this is happening. it might be also
worth to upgrade to the latest version of pytz: pytz maintainers, are
you planning on update this package soon? thanks!

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

[Adrian Bunk]

Control: retitle -1 pokerth: -std=gnu++98 workaround no longer works with Qt 5.7

Thanks for your report.

The core of the problem is:

g++ -c -m64 -pipe -std=gnu++98 ...
...
/usr/include/x86_64-linux-gnu/qt5/QtCore/qcompilerdetection.h:562:6: 
error: #error Qt requires a C++11 compiler and yours does not seem to be that.
 #error Qt requires a C++11 compiler and yours does not seem to be that.
  ^

This package uses -std=gnu++98 as workaround for code that is not 
valid C++11 code, but the headers of Qt 5.7 (that just entered unstable) 
require a compiler in C++11 (or higher) mode.


> Regards,

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: pokerth: FTBFS: qobjectdefs_impl.h:72:88: error: '>>' should be '> >' within a nested template argument list

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 pokerth: -std=gnu++98 workaround no longer works with Qt 5.7
Bug #843078 [src:pokerth] pokerth: FTBFS: qobjectdefs_impl.h:72:88: error: '>>' 
should be '> >' within a nested template argument list
Changed Bug title to 'pokerth: -std=gnu++98 workaround no longer works with Qt 
5.7' from 'pokerth: FTBFS: qobjectdefs_impl.h:72:88: error: '>>' should be '> 
>' within a nested template argument list'.

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

Bug#842844: marked as done (slang2: FTBFS on all buildds: No rule to make target '/«PKGBUILDDIR»/src/elfobjs', needed by '/«PKGBUILDDIR»/src/elfobjs/libslang.so.2.3.1'. Stop.)

[Debian Bug Tracking System]

Your message dated Thu, 3 Nov 2016 18:52:07 +
with message-id <20161103185207.bygni2foib3lh...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#842844: slang2: FTBFS on all buildds: No rule to make 
target '/«PKGBUILDDIR»/src/elfobjs', needed by 
'/«PKGBUILDDIR»/src/elfobjs/libslang.so.2.3.1'. Stop.
has caused the Debian Bug report #842844,
regarding slang2: FTBFS on all buildds: No rule to make target 
'/«PKGBUILDDIR»/src/elfobjs', needed by 
'/«PKGBUILDDIR»/src/elfobjs/libslang.so.2.3.1'. Stop.
to be marked as done.

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

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


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

slang2 failed to build from source on all the official buildds, all of
which appear to carry out parallel builds, and on most unofficial buildds.
It succeeded on the unofficial hurd-i386 and m68k buildds, which (unusually)
only have one core each and do not attempt parallel builds. sh4 has not been
tried at the time I write this email; it could go either way.

If this package is sufficiently fast to build that you do not feel a need to
use parallel builds (which I suspect is the case, since the maintainer's build
succeeded), the quickest short-term fix would be this pseudo-patch, expanding
what I did in my recent NMU to cover the whole build:

-dh $@ --with autotools_dev
+dh $@ --with autotools_dev --no-parallel

I'll do another NMU with that change if necessary.

The ideal solution would be to fix the upstream build system to succeed
reliably with "make -j8" (or other large numbers of threads) and send that
fix upstream, but that's likely to be a more involved task.

For your information, maintainer uploads of packages where the build
system is parallel-safe, from any reasonable hardware, would go quicker
with "dpkg-buildpackage -Jauto" (or debuild -Jauto or whatever), which
is probably equivalent to what the official buildds are doing. Using
that command to build would also have detected this bug.

Regards,
S
--- End Message ---
--- Begin Message ---
Version: 2.3.1-2

On Tue, 01 Nov 2016 at 17:47:37 +, Simon McVittie wrote:
> the quickest short-term fix would be this pseudo-patch, expanding
> what I did in my recent NMU to cover the whole build:
> 
> -dh $@ --with autotools_dev
> +dh $@ --with autotools_dev --no-parallel

This seems to have been done; closing the bug.

S--- End Message ---

Bug#837008: python-astropy: FTBFS: test failure

[Sandro Tosi]

On Thu, 8 Sep 2016 08:51:56 +0200 Ole Streicher  wrote:
> Control: reassign -1 src:python-scipy 0.18.0-1
> Control: affects -1 python-astropy
> Control: forwarded -1 https://github.com/scipy/scipy/issues/6420
> Control: tags -1 patch
>
>
> >> === FAILURES 
> >> ===
> >> _ test_circmean_against_scipy 
> >> __
> >>
> >> @pytest.mark.skipif('not HAS_SCIPY')
> >> def test_circmean_against_scipy():
> >> # testing against scipy.stats.circmean function
> >> data = np.random.uniform(-np.pi, np.pi, size=(100, 5))
> >> answer = scipy.stats.circmean(data, np.pi, -np.pi)
> >>>   assert_equal(np.around(answer, 2), np.around(circmean(data), 2))
> >> E   AssertionError:
> >> E   Items are not equal:
> >> EACTUAL: -4.3096
> >> EDESIRED: 1.97
>
> This is actually a regression bug in scipy; see the github issue. A
> patch is available at https://github.com/scipy/scipy/pull/6543

That regression is said to be fixed in scipy 0.18.1, which was
uploaded on Oct 7 - could you verify this bug is actually fixed
rebuilding astropy? thanks!

Bug#843086: mdk3: FTBFS: No rule to make target 'osdep/libosdep.a'

[Aaron M. Ucko]

Source: mdk3
Version: 6.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

[Filing as a regression due to the likelihood of affecting any binNMUs.]

Builds of mdk3 that use parallel make have been failing:

  make -C osdep
  make[1]: *** No rule to make target 'osdep/libosdep.a', needed by 'mdk3'.  
Stop.
  make[1]: *** Waiting for unfinished jobs
  make[2]: Entering directory '/«PKGBUILDDIR»/osdep'

The issue appears to be a typo in the top-level Makefile, which only
supplies a rule for osdep/libosdep.so even though libosdep is always
static.

Could you please take a look?

Thanks!

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

Processed: Re: php-memcached: FTBFS: conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 php-memcached must build-depend on zlib1g-dev
Bug #843077 [src:php-memcached] php-memcached: FTBFS: conftest.c:9:28: fatal 
error: ac_nonexistent.h: No such file or directory
Changed Bug title to 'php-memcached must build-depend on zlib1g-dev' from 
'php-memcached: FTBFS: conftest.c:9:28: fatal error: ac_nonexistent.h: No such 
file or directory'.

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

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

[Adrian Bunk]

Control: retitle -1 php-memcached must build-depend on zlib1g-dev

Thanks for your report.

The error message for the actual bug is:
checking for ZLIB... yes, shared
checking for pkg-config... /usr/bin/pkg-config
checking for zlib location... configure: error: memcached support requires 
ZLIB. Use --with-zlib-dir= to specify the prefix where ZLIB headers and 
library are located

The problem is that libssl-dev 1.1.0 no longer depends on zlib1g-dev, 
and packages that fail to declare an explicit dependency no longer get 
that installed.

> Regards,

cu
Adrian

-- 

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

Processed: Re: Bug#841341 closed by Paulo Henrique de Lima Santana (phls) <p...@softwarelivre.org> (Bug#841341: fixed in bd 1.01-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen 841341 !
Bug #841341 {Done: Paulo Henrique de Lima Santana (phls) 
} [bd] bd "Bad substitution" if /bin/sh is not bash
'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
Changed Bug submitter to 'eribe...@debian.org' from 'Gerardo Martin Chaves 
'.
No longer marked as fixed in versions bd/1.01-2.
> severity 841341 grave
Bug #841341 [bd] bd "Bad substitution" if /bin/sh is not bash
Severity set to 'grave' from 'normal'

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

Bug#843053: This looks like a libfolia ABI breakage

[Adrian Bunk]

Control: reassign -1 libfolia4 1.4-1
Control: affects -1 frog

This looks as if the libfolia ABI changed in 1.4 (or earlier) without 
changing the soname.

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: This looks like a libfolia ABI breakage

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libfolia4 1.4-1
Bug #843053 [frog] frog does not start
Bug reassigned from package 'frog' to 'libfolia4'.
No longer marked as found in versions frog/0.13.5-1.
Ignoring request to alter fixed versions of bug #843053 to the same values 
previously set
Bug #843053 [libfolia4] frog does not start
Marked as found in versions libfolia/1.4-1.
> affects -1 frog
Bug #843053 [libfolia4] frog does not start
Added indication that 843053 affects frog

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

Bug#807994: python-django-south: Incompatable with Django >= 1.7

[Sandro Tosi]

On Tue, 15 Dec 2015 16:40:34 +1100 Brian May  wrote:
> Source: python-django-south
> Version: 1.0.0-1
> Severity: grave
> Justification: renders package unusable
>
> Package is broken with Django 1.7+ in Debian and not fit for release. It
> will not get fixed, as the functionality has been replaced by the Django
> 1.7 migration mechanism.
>
> I was going to file a bug report to remove the package, however then I
> noticed there are packages that still depend on this package.
>
> (sid-amd64)root@prune:/home/brian# apt-cache rdepends
> python-django-south
> python-django-south
> Reverse Depends:
>   bcfg2-web
>   python-django-voting
>   python-django-threadedcomments
>   lava-server
>   python-django-sitetree
>   python-django-picklefield

What is the plan here? Brian/David, maybe you could just file RC bugs
on the rdepends to move away from django-south? thanks!

Bug#843083: brial: FTBFS: hash discrepancies in UnitTests

[Aaron M. Ucko]

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

Automated builds of brial have been failing with test suite
discrepancies, as detailed at

https://buildd.debian.org/status/logs.php?pkg=brial=0.8.5-1

The observed hash values still appear to vary only by word size, but
are different from what the tests expect.  Could you please take a look?

Thanks!

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

Bug#828665: FTBFS under Django 1.10

[Sandro Tosi]

On Sun, 26 Jun 2016 17:14:38 +0100 Chris Lamb  wrote:
> Whilst rebuilding all reverse build-dependencies of python-django
> with the latest beta, I noticed that python-django-extensions FTBFS with 1.10.
>
> Please update your package to work with Django 1.10 (in experimental)
> as I will uploading it to unstable once it is released (and at the same
> time raising the severity of this bug to RC).

Hey Brian it looks like 1.7.4 supports django 1.10 (inferred as
https://github.com/django-extensions/django-extensions/commit/a0e6fb8619d90afe6a81a77059895ead3524707d
is right after the tag to release 1.7.4) so could you try to package
the latest version and verify it works with django 1.10? thanks!!

Bug#835437: pycurl: FTBFS too much often (failing tests)

[Sandro Tosi]

On Thu, 25 Aug 2016 19:21:18 +0200 (CEST) Santiago Vila  wrote:
> Package: src:pycurl
> Version: 7.43.0-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:
>
> 
> [...]

Hey Barry, did you have a chance to look at this? might be also just
forward it upstream and see how that goes. Thanks!

Bug#826728: percona-toolkit: (CVE-2014-2029) scripts call back home and leak information

[Sandro Tosi]

On Wed, 8 Jun 2016 14:21:14 +0200 Guillem Jover  wrote:
> This package contains many scripts which call back home to check for
> a new upstream versions. In addition they also report back things such
> as hostname and port and similar. It seems this was previously disabled
> or removed due to CVE-2014-2029 (#740846), but the patch got lost
> somewhere?

hello Guillem,
can you clarify what you see and/or in which scripts you saw the
callback happening automatically?

i had a quick look and it appears this feature is not enabled by
default (as also clarified at https://www.percona.com/version-check);
for example in pt-duplicate-key-checker i can see:

   # 
   # Do the version-check
   # 
   if ( $o->get('version-check') && (!$o->has('quiet') || !$o->get('quiet')) ) {
  VersionCheck::version_check(
 force => $o->got('version-check'),
 instances => [ {dbh => $dbh, dsn => $dsn} ],
  );
   }

which only triggers the version check if the `version-check` cli
switch/config parameters are set.

Dario, side question: if you want a hand co-maintain percona-toolkit id be
happy to help as we use them at work so we do care about those tools.

thanks,
sandro

Processed: [bts-link] source package src:gdcm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:gdcm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828308 (http://bugs.debian.org/828308)
> # Bug title: missing include for 'X509_STORE_CTX cert_ctx'
> #  * https://sourceforge.net/p/gdcm/bugs/397/
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 828308 + fixed-upstream
Bug #828308 [src:gdcm] missing include for 'X509_STORE_CTX cert_ctx'
Added tag(s) fixed-upstream.
> usertags 828308 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#819488: gparted crash with a libparted backtrace

[Mattia Rizzolo]

On Thu, Nov 03, 2016 at 11:37:02AM -0400, Sandro Tosi wrote:
> Mattia, do you still consider this bug RC? thanks!

I don't think so, no.  Though it's still a crash, it's important, but
probably not RC indeed.

Furthermore I'm not affected by this anymore, since I "fixed" my
partition table to have libparted like it more.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#828299: fetchmail: FTBFS with openssl 1.1.0

[Andreas Henriksson]

On Thu, Nov 03, 2016 at 05:44:54PM +0100, Kurt Roeckx wrote:
> On Thu, Nov 03, 2016 at 07:45:16AM +0100, Andreas Henriksson wrote:
[...]
> > 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.

There might still be an issue here sure, but this is not my package and
I won't dive into that. Just saying that you might want to unmark
fetchmail as an openssl 1.1.0 transition blocker.

Regards,
Andreas Henriksson

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 { 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 &, const ApplyReturnValue ) {
^~
  /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 &, const ApplyReturnValue ) {
 ^
  /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::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 

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 

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#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: 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#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.

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#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

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-

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

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#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

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#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: #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#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/

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!

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

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

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

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#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=e96d2e1c963b668e09cc5075cbdf947880bfd14f
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828521

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