Bug#909387: erlang-mode: fails to install with xemacs21

2019-02-08 Thread Andreas Beckmann
Followup-For: Bug #909387
Control: tag -1 pending

Hi,

I've backported the fix from sid to stretch and filed a stretch-pu
request: https://bugs.debian.org/921811


Andreas



Processed: Re: erlang-mode: fails to install with xemacs21

2019-02-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #909387 {Done: Sergei Golovan } [erlang-mode] 
erlang-mode: fails to install with xemacs21
Added tag(s) pending.

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



Bug#921725: libu2f-host: CVE-2018-20340

2019-02-08 Thread Salvatore Bonaccorso
Hi Nicolas,

On Fri, Feb 08, 2019 at 08:23:10PM +0100, Nicolas Braud-Santoni wrote:
> On Fri, Feb 08, 2019 at 02:08:40PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> > 
> > The following vulnerability was published for libu2f-host.
> > 
> > CVE-2018-20340[0]:
> > buffer overflow
> 
> 
> Hi Salvatore & Sébastien,
> 
> Thanks a lot for the swift report(s).  :)
> 
> I just uploaded a fixed version to unstable.

Thank you, tracker information is updated already.

> I will see about backporting the fix to stretch.

while the issue was not yet public, Sébastien did work on an update
for stretch-security. Lets see if he would like to release his version
of the upload.

Regards,
Salvatore



Bug#920227: marked as done (invalid file format generated for dependencies)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 06:52:11 +
with message-id 
and subject line Bug#920227: fixed in sbuild 0.78.1-1
has caused the Debian Bug report #920227,
regarding invalid file format generated for dependencies
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.)


-- 
920227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild
Version: 0.78.0-2
Severity: grave
Tags: upstream

Since the 0.78 upgrade, sbuild cannot build packages in jessie (and
maybe other suites). The build during the setup phase, while trying to
install the build-dependencies, with this error message:

W: Failed to fetch 
gzip:/var/lib/apt/lists/partial/_build_systemd-asEYMr_resolver-48eHqy_apt%5farchive_._Sources.gz
 Invalid file format

It looks like the Sources.gz generated for the build-dependencies
resolver is incorrectly formatted, which freaks out apt in the chroot.

This does not happen with sbuild 0.77.1-2. This seems to be a
regression introduced in this commit:

https://salsa.debian.org/debian/sbuild/commit/18f423619c176471d2adaafb7742cb204951a10c

... which was implemented to close bug #909847. In there, sbuild
reimplements dpkg-scanpackages and dpkg-scansources internally, but it
seems to do so incorrectly.

Attached are the build logs and the faulty Sources.gz files.

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

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

Versions of packages sbuild depends on:
ii  adduser 3.118
ii  libsbuild-perl  0.78.0-2
ii  perl5.28.1-3

Versions of packages sbuild recommends:
ii  autopkgtest  5.8
ii  debootstrap  1.0.114
ii  schroot  1.6.10-6+b1

Versions of packages sbuild suggests:
ii  deborphan  1.7.31
ii  e2fsprogs  1.44.5-1
ii  kmod   25-2
ii  wget   1.20.1-1

-- debconf-show failed


sources.gz
Description: application/gzip
sbuild (Debian sbuild) 0.78.0 (09 January 2019) on curie.anarc.at

+==+
| systemd 215-17+deb8u9 (amd64)Tue, 22 Jan 2019 21:39:27 + |
+==+

Package: systemd
Version: 215-17+deb8u9
Source Version: 215-17+deb8u9
Distribution: UNRELEASED
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/jessie-amd64-sbuild-3b476c6c-1cda-4a37-bd77-e77297a487a8'
 with '<>'
I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1/resolver-0MCIZ4' 
with '<>'

+--+
| Update chroot|
+--+

Ign http://deb.debian.org jessie InRelease
Hit http://security.debian.org jessie/updates InRelease
Hit http://deb.debian.org jessie-backports InRelease
Hit http://deb.debian.org jessie Release.gpg
Hit http://security.debian.org jessie/updates/main amd64 Packages
Get:1 http://deb.debian.org jessie-backports/main amd64 Packages/DiffIndex 
[27.8 kB]
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://deb.debian.org jessie Release
Hit http://security.debian.org jessie/updates/non-free amd64 Packages
Hit http://deb.debian.org jessie/main Sources
Hit http://deb.debian.org jessie/main amd64 Packages
Fetched 27.8 kB in 2s (12.7 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/anarcat/dist/systemd_215-17+deb8u9.dsc exists in /home/anarcat/dist; 
copying to chroot
I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1/systemd-215' with 
'<>'
I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1' with '<>'

+--

Bug#921738: marked as done (chromium-widevine: Widevine does not work with Netflix)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 9 Feb 2019 07:44:29 +0100
with message-id 

and subject line Re: chromium-widevine: Widevine does not work with Netflix
has caused the Debian Bug report #921738,
regarding chromium-widevine: Widevine does not work with Netflix
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.)


-- 
921738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-widevine
Version: 71.0.3578.80-1~deb9u1
Severity: grave
Justification: renders package unusable

Netflix keeps saying:
Your web browser is missing a digital rights component. Go to
chrome://components and under WidevineCdm, click Check for update.

I have installed the chromium-widevine package, together with the correct
version of chromium, and still complains about the missing plugin.

To solve it, I need to download a binary blob from Google:
wget https://dl.google.com/widevine-cdm/1.4.8.1008-linux-x64.zip
unzip 1.4.8.1008-linux-x64.zip
sudo mkdir /usr/lib/chromium
sudo mv libwidevinecdm.so /usr/lib/chromium
sudo chmod 644 /usr/lib/chromium/libwidevinecdm.so

Looks like I'm not the only one having this problem:
https://unix.stackexchange.com/questions/385880/using-the-chromium-widevine-
debian-package

Thanks!



-- System Information:
Debian Release: 9.7
  APT prefers stable
  APT policy: (750, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.20-grsec-botto+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages chromium-widevine depends on:
ii  chromium  71.0.3578.80-1~deb9u1

chromium-widevine recommends no packages.

chromium-widevine suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
tags 921738 + wontfix
bye

This package is *not* widevine. It is the *support* for the legacy
widevine cdm. You still have to download the widevine cdm from
widevine.com/google. Google prohibits its distribution without a
license:

> "Google Inc. and its affiliates ("Google") own all legal right, title and
> interest in and to the content decryption module software ("Software") and
> related documentation, including any intellectual property rights in the
> Software. You may not use, modify, sell, or otherwise distribute the Software
> without a separate license agreement with Google.  The Software is not open
> source software.
>
> If you are interested in licensing the Software, please contact
> widev...@google.com.

This package was removed from newer releases of the chromium package.
The new widevine cdm module (4.10.1196.0) will be loaded directly by
the browser from /usr/lib/chromium/libwidevinecdm.so when you have a
version installed which isn't affected by
https://bugs.debian.org/916058 - you still have to get
libwidevinecdm.so

If you are interested in automatically installing this plugin then
please use the approach by
https://tracker.debian.org/pkg/pepperflashplugin-nonfree and upload
the download helper to contrib/web.

As far as I know, Mozilla has a license to use widevine but not a
license to distribute it. Steam/Valve maybe has a license to
redistribute it (I could be wrong but I thought that it was in their
steam runtime) and the chrome team definitely has a license to
distribute it.

You have to contact netflix directly about their wrong help message--- End Message ---


Processed (with 5 errors): Re: chromium-widevine: Widevine does not work with Netflix

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 921738 + wontfix
Bug #921738 [chromium-widevine] chromium-widevine: Widevine does not work with 
Netflix
Added tag(s) wontfix.
> bye
Unknown command or malformed arguments to command.
> This package is *not* widevine. It is the *support* for the legacy
Unknown command or malformed arguments to command.
> widevine cdm. You still have to download the widevine cdm from
Unknown command or malformed arguments to command.
> widevine.com/google. Google prohibits its distribution without a
Unknown command or malformed arguments to command.
> license:
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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



Bug#921738: chromium-widevine: Widevine does not work with Netflix

2019-02-08 Thread Charlemagne Lasse
tags 921738 + wontfix
bye

This package is *not* widevine. It is the *support* for the legacy
widevine cdm. You still have to download the widevine cdm from
widevine.com/google. Google prohibits its distribution without a
license:

> "Google Inc. and its affiliates ("Google") own all legal right, title and
> interest in and to the content decryption module software ("Software") and
> related documentation, including any intellectual property rights in the
> Software. You may not use, modify, sell, or otherwise distribute the Software
> without a separate license agreement with Google.  The Software is not open
> source software.
>
> If you are interested in licensing the Software, please contact
> widev...@google.com.

This package was removed from newer releases of the chromium package.
The new widevine cdm module (4.10.1196.0) will be loaded directly by
the browser from /usr/lib/chromium/libwidevinecdm.so when you have a
version installed which isn't affected by
https://bugs.debian.org/916058 - you still have to get
libwidevinecdm.so

If you are interested in automatically installing this plugin then
please use the approach by
https://tracker.debian.org/pkg/pepperflashplugin-nonfree and upload
the download helper to contrib/web.

As far as I know, Mozilla has a license to use widevine but not a
license to distribute it. Steam/Valve maybe has a license to
redistribute it (I could be wrong but I thought that it was in their
steam runtime) and the chrome team definitely has a license to
distribute it.

You have to contact netflix directly about their wrong help message



Processed: doxygen: cascade of FTBFS

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 921779 cascade of FTBFS
Bug #921779 [src:doxygen] doxygen: FTBFS (LaTeX error)
Changed Bug title to 'cascade of FTBFS' from 'doxygen: FTBFS (LaTeX error)'.
> affects 921779 primesieve bliss librostlab-blast doxygen
Bug #921779 [src:doxygen] cascade of FTBFS
Added indication that 921779 affects primesieve, bliss, librostlab-blast, and 
doxygen
> reassign 921802 doxygen
Bug #921802 [src:primesieve] primesieve: FTBFS (LaTeX error)
Bug reassigned from package 'src:primesieve' to 'doxygen'.
No longer marked as found in versions primesieve/7.3+ds-1.
Ignoring request to alter fixed versions of bug #921802 to the same values 
previously set
> reassign 921776 doxygen
Bug #921776 [src:bliss] bliss: FTBFS (LaTeX error)
Bug reassigned from package 'src:bliss' to 'doxygen'.
No longer marked as found in versions bliss/0.73-2.
Ignoring request to alter fixed versions of bug #921776 to the same values 
previously set
> reassign 921789 doxygen
Bug #921789 [src:librostlab-blast] librostlab-blast: FTBFS (LaTeX error)
Bug reassigned from package 'src:librostlab-blast' to 'doxygen'.
No longer marked as found in versions librostlab-blast/1.0.1-9.
Ignoring request to alter fixed versions of bug #921789 to the same values 
previously set
> thanks
Stopping processing here.

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



Bug#921779: doxygen: FTBFS (LaTeX error)

2019-02-08 Thread Jerome BENOIT
Dear All,

I think there is a major issue with doxygen:
#921802 , #921776, #921789, and certainly other seem affected by a recent bug 
that affect doxygen.

For #921776, I cannot compose the PDF in a Sid environment, but I can compose 
it on my Stretch box.

Jerome

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature


Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-08 Thread Andreas Tille
Hi,

that's caused by missing icu-config (#920900)


On Sat, Feb 09, 2019 at 12:15:16AM +, Santiago Vila wrote:
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> 
> [... snipped ...]

... the relevant part was snipped here:


-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
--> OS = Linux / ARCH = x86_64
-- Bootstraping from pre-generated sources.
CMake Error at CMakeLists.txt:756 (message):
  Unable to find 'icu-config'.  Set ICUCONFIG in CMake cache.


I need to check how to work around this.  Its a bit ugly to
drop something with "wontfix" in this release state ...

Kind regards

 Andreas.

-- 
http://fam-tille.de



Bug#921473: [deb...@kitterman.com: Bug#921473: calibre: Invalid maintainer address]

2019-02-08 Thread Nicholas D Steeves
Hi Scott, please let us know if you'd us to stop CCing you, I imagine
you're very busy right now!

Hi Norbert,

On Fri, Feb 08, 2019 at 05:32:34PM +0900, Norbert Preining wrote:
> Hi Nicholas,
> 
> I just want to be sure that despite "interesting" decisions I can have
> access to the repositories I maintain. Which is not the case on salsa.

:-o Oh, now I see...  You lost access to preining, and thus
maintainer-level access to both the repository and messages. :-(

> > It would have been nice to have received notification of the new
> > project location...but at any rate, for the purposes of reintegrating
> 
> Sorry, I posted a blog about it, but did not inform you personally. My
> failure.

P.S. No worries, we're resolving it now.  P.S. I'm terrible about
following even the blogs of close friends, but I've enjoyed several of
your articles over the years!

> > Would you like to work on the integration or shall I?  No idea about
> 
> I will cum grano salis take over the master/upstream/pristine-tar branch
> from your work, because this is what is in Debian uploaded.
> 
> For future work, I have added you to the collaborators of my
> calibre-debian git, so you can pull/push directly to the github repo.
> 
> But please wait until I have updated the gh to match salsa, thanks.

Do you still have a copy of your branch?  I'm interested in diffing
between them to check if I missed something.

> > Also, at the moment are you able to dput the next upload of Calibre,
> > or will I need to?
> 
> I can do that. I have DM rights for all my packages. I just couldn't
> upload cssparser which I had packaged also already 2 months ago, but
> wasn't able to upload since I am no DD.

Oh my, more duplicated work :-p  That's something you should have
gotten credit for...

> Thanks for your understanding and help!

You're welcome :-)  By the way, thank you for maintaining TeX for all
these years...that package must have been a TONNE of work.


Cheers,
Nicholas


signature.asc
Description: PGP signature


Processed: tagging 921767, found 921767 in 5.0.30-1

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 921767 + upstream
Bug #921767 [src:passenger] CVE-2018-12029
Added tag(s) upstream.
> found 921767 5.0.30-1
Bug #921767 [src:passenger] CVE-2018-12029
Marked as found in versions passenger/5.0.30-1.
> thanks
Stopping processing here.

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



Processed: tagging 921772, bug 921772 is forwarded to https://github.com/JabRef/jabref/issues/4229 ...

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 921772 + upstream
Bug #921772 [jabref] CVE-2018-1000652
Added tag(s) upstream.
> forwarded 921772 https://github.com/JabRef/jabref/issues/4229
Bug #921772 [jabref] CVE-2018-1000652
Set Bug forwarded-to-address to 'https://github.com/JabRef/jabref/issues/4229'.
> found 921772 3.8.2+ds-11
Bug #921772 [jabref] CVE-2018-1000652
Marked as found in versions jabref/3.8.2+ds-11.
> found 921772 3.8.1+ds-3
Bug #921772 [jabref] CVE-2018-1000652
Marked as found in versions jabref/3.8.1+ds-3.
> thanks
Stopping processing here.

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



Bug#918604: marked as done (ruby-markerb FTBFS: Expected file "app/views/notifier/foo.markerb" to exist, but does not)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 03:49:50 +
with message-id 
and subject line Bug#918604: fixed in ruby-markerb 1.1.0-3
has caused the Debian Bug report #918604,
regarding ruby-markerb FTBFS: Expected file "app/views/notifier/foo.markerb" to 
exist, but does not
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.)


-- 
918604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-markerb
Version: 1.1.0-2
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-markerb.html

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-markerb-1.1.0/debian/ruby-markerb/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-markerb/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/generator_test.rb" 
"test/markdown_test.rb" "test/markerb_test.rb" 
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59: warning: loading in 
progress, circular require considered harmful - 
/usr/lib/ruby/vendor_ruby/redcarpet.rb
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in  `'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in  `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in  `block 
in '
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /build/1st/ruby-markerb-1.1.0/test/generator_test.rb:1:in  `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /build/1st/ruby-markerb-1.1.0/test/test_helper.rb:12:in  `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/vendor_ruby/redcarpet.rb:2:in  `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/vendor_ruby/redcarpet/compat.rb:1:in  `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in  
`require'
/usr/lib/ruby/vendor_ruby/mail/fields/common/address_container.rb:11: warning: 
parentheses after method name is interpreted as an argument list, not a 
decomposed argument
Run options: --seed 28374

# Running:

F

Failure:
GeneratorTest#test_assert_all_views_are_properly_created_with_given_name 
[/build/1st/ruby-markerb-1.1.0/test/generator_test.rb:12]:
Expected file "app/views/notifier/foo.markerb" to exist, but does not

bin/rails test build/1st/ruby-markerb-1.1.0/test/generator_test.rb:9

../build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
./build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
./build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
/build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
./build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
/build/1st/ruby-markerb-1.1.0/lib/markerb/markdown.rb:9: warning: instance 
variable @options not initialized
.

Finished in 0.565871s, 19.4390 runs/s, 38.8781 assertions/s.
11 runs, 22 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/generator_test.rb" 
"test/markdown_test.rb" "test/markerb_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-markerb-1.1.0/debia

Bug#921164: marked as done (kubectx: FTBFS in sid)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 03:49:13 +
with message-id 
and subject line Bug#921164: fixed in kubectx 0.6.3-2
has caused the Debian Bug report #921164,
regarding kubectx: FTBFS in sid
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.)


-- 
921164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kubectx
Version: 0.6.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
bats test/kubectx.bats
1..16
ok 1 --help should not fail
ok 2 -h should not fail
ok 3 switch to previous context when no one exists
not ok 4 list contexts when no kubeconfig exists
# (in test file test/kubectx.bats, line 32)
#   `[[ "$output" = "" ]]' failed

[... snipped ...]

# (in test file test/kubectx.bats, line 151)
#   `[[ "$output" = "user2@cluster1" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.x9iuA0so15/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user2@cluster1
not ok 13 delete current context
# (in test file test/kubectx.bats, line 169)
#   `[[ "$output" = "user1@cluster1" ]]' failed
# Switched to context "user2@cluster1".
# Deleting context "user2@cluster1"...
# warning: this removed your active context, use "kubectl config use-context" 
to select a different one
# deleted context user2@cluster1 from /tmp/tmp.Bcwc8cKMwj/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user1@cluster1
ok 14 delete non existent context
not ok 15 delete several contexts
# (in test file test/kubectx.bats, line 190)
#   `[[ "$output" = "" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.u0qR27XfVH/config
# Deleting context "user2@cluster1"...
# deleted context user2@cluster1 from /tmp/tmp.u0qR27XfVH/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
not ok 16 delete several contexts including a non existent one
# (in test file test/kubectx.bats, line 203)
#   `[[ "$output" = "user2@cluster1" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.P7RwbY7pJw/config
# Deleting context "non-existent"...
# error: cannot delete context non-existent, not in /tmp/tmp.P7RwbY7pJw/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user2@cluster1
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

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 BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: kubectx
Source-Version: 0.6.3-2

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated kubectx 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: Sat, 09 Feb 2019 11:35:49 +0800
Source: kubectx
Arc

Bug#921164: kubectx: FTBFS in sid

2019-02-08 Thread 陳昌倬
On Fri, Feb 08, 2019 at 05:31:02PM +0100, Santiago Vila wrote:
> Hi. The following patch may help, but I have not tested it
> (please double-check before uploading).
> 
> Thanks.
> 
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,5 +1,5 @@
>  #!/usr/bin/make -f
> -#export DH_VERBOSE = 1
> +export TERM=dumb
>  
>  %:
>   dh $@

This patch is okay in sbuild, thanks for the help. I will upload it
later.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature


Bug#921800: marked as done (nvchecker: FTBFS (failing tests))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 03:05:34 +
with message-id 
and subject line Bug#921800: fixed in nvchecker 1.3-2
has caused the Debian Bug report #921800,
regarding nvchecker: 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.)


-- 
921800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvchecker
Version: 1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/slogconf.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/sortversion.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/core.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker

[... snipped ...]

async with session.get(url) as res:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

async def __aenter__(self):
> return await to_asyncio_future(client.fetch(self.req))
E tornado.httpclient.HTTPClientError: HTTP 502: Proxy Error

nvchecker/source/tornado_httpclient.py:62: HTTPClientError
===Flaky Test Report===

test_archpkg passed 1 out of the required 1 times. Success!
test_archpkg_strip_release passed 1 out of the required 1 times. Success!
test_aur passed 1 out of the required 1 times. Success!
test_aur_strip_release passed 1 out of the required 1 times. Success!
test_aur_use_last_modified passed 1 out of the required 1 times. Success!
test_debianpkg passed 1 out of the required 1 times. Success!
test_debianpkg_strip_release passed 1 out of the required 1 times. Success!
test_debianpkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg passed 1 out of the required 1 times. Success!
test_ubuntupkg_strip_release passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite_with_paging passed 1 out of the required 1 times. Success!

===End Flaky Test Report===
=== warnings summary ===
tests/test_regex.py:12
  /<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:12: 
DeprecationWarning: invalid escape sequence \w
"regex": '"User-Agent": "(\w+)"',

tests/test_regex.py:19
  /<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:19: 
DeprecationWarning: invalid escape sequence \w
"regex": 'for (\w+) examples',

tests/test_substitute.py:20
  /<>/.pybuild/cpython3_3.7/build/tests/test_substitute.py:20: 
DeprecationWarning: invalid escape sequence \d
assert await get_version("example", {"manual": "r15", "prefix": "r", 
"from_pattern": "r(\d+)", "to_pattern": "R\1"}) == "15"

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 1 failed, 40 passed, 18 skipped, 3 warnings in 13.15 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7/build; python3.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
exit code 13
make: *** [debian/rules:6: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: nvchecker
Source-Version: 1.3-2

We believe that the bug you reported is fixed in the latest version of
nvchecker, 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#921807: marked as done (sketch: FTBFS (LaTeX error))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 03:05:47 +
with message-id 
and subject line Bug#921807: fixed in sketch 1:0.3.7-11
has caused the Debian Bug report #921807,
regarding sketch: FTBFS (LaTeX error)
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.)


-- 
921807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sketch
Version: 1:0.3.7-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
perl makever.pl
not generating web page
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
make -j1
make[2]: Entering directory '/<>'

[... snipped ...]

(/usr/share/texlive/texmf-dist/tex/generic/pst-node/pst-node.tex)))
(/usr/share/texlive/texmf-dist/tex/latex/pst-text/pst-text.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-text/pst-text.tex
 v1.01, 2018/12/22(tvz,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/pst-3d/pst-3d.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-3d/pst-3d.tex))
(/usr/share/texlive/texmf-dist/tex/latex/pst-eps/pst-eps.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-eps/pst-eps.tex
 v1.00, 2006/11/04))
(/usr/share/texlive/texmf-dist/tex/latex/pst-fill/pst-fill.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-fill/pst-fill.tex
`PST-Fill' v1.01, 2007/03/10 (tvz,dg,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/pstricks-add/pstricks-add.sty
(/usr/share/texlive/texmf-dist/tex/latex/pst-math/pst-math.sty
(/usr/share/texlive/texmf-dist/tex/latex/pst-calculate/pst-calculate.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3dvips.def)))
(/usr/share/texlive/texmf-dist/tex/latex/siunitx/siunitx.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty)
(/usr/share/texlive/texmf-dist/tex/latex/translator/translator.sty)))
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)

! LaTeX Error: File `xstring.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
! Emergency stop.
 
 
l.19 \input
pst-math.tex^^M
No pages of output.
Transcript written on ex000-tmp.log.
Inappropriate ioctl for device at make.pl line 34,  line 1.
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: sketch
Source-Version: 1:0.3.7-11

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated sketch 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: Fri, 08 Feb 20

Bug#915172: marked as done (id-utils FTBFS with glibc 2.28)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 01:35:31 +
with message-id 
and subject line Bug#915172: fixed in id-utils 4.6+git20190113-1
has caused the Debian Bug report #915172,
regarding id-utils FTBFS with glibc 2.28
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.)


-- 
915172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: id-utils
Version: 4.6+git20120811-4
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/id-utils.html

...
  CC   fseterr.o
fseterr.c: In function 'fseterr':
fseterr.c:74:3: error: #error "Please port gnulib fseterr.c to your platform! 
Look at the definitions of ferror and clearerr on your system, then report this 
to bug-gnulib."
  #error "Please port gnulib fseterr.c to your platform! Look at the 
definitions of ferror and clearerr on your system, then report this to 
bug-gnulib."
   ^
make[4]: *** [Makefile:1590: fseterr.o] Error 1


See #915151 for background.
--- End Message ---
--- Begin Message ---
Source: id-utils
Source-Version: 4.6+git20190113-1

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

Debian distribution maintenance software
pp.
Bradley A. Bosch  (supplier of updated id-utils 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, 07 Feb 2019 21:10:38 -0600
Source: id-utils
Binary: id-utils
Architecture: source amd64
Version: 4.6+git20190113-1
Distribution: unstable
Urgency: low
Maintainer: Bradley A. Bosch 
Changed-By: Bradley A. Bosch 
Description:
 id-utils   - Fast, high-capacity, identifier database tool
Closes: 727388 736912 749412 777663 915172
Changes:
 id-utils (4.6+git20190113-1) unstable; urgency=low
 .
   * New upstream version from git 9a4ea9a365589ba52b4b020800e7b9718697989e
 with updated libgnu from git master 
3043e43a7c30516482725c69b36f8feb4846f819
 (Closes: #915172)
 .
   * Patch to work around hurd build failure from Svante Signell
  (Closes: #736912)
 .
   * Call dh_autotools-dev_updateconfig from rules (Closes: #727388)
 .
   * Eliminate ambiguous duplicate hash_free() functions (Closes: #749412)
 .
   * Add usage hint for emacs users from Francois Marier 
 (Closes: #777663)
Checksums-Sha1:
 c2c8d1be70d93a7a8acd4fee067699cfd6360c8e 1750 id-utils_4.6+git20190113-1.dsc
 7334a195b348cc85c8deadb471a0f554c98407d5 8437472 
id-utils_4.6+git20190113.orig.tar.gz
 ed272693d64f1dece357e48bf5852920f3e7ae18 117895 
id-utils_4.6+git20190113-1.diff.gz
 705ec61348f0ef2710325ad4c72aade25196a362 856532 
id-utils-dbgsym_4.6+git20190113-1_amd64.deb
 0db60318a9279f71b2a4b9fd41d874e6dbe158c8 5927 
id-utils_4.6+git20190113-1_amd64.buildinfo
 b9ab3e6a483cae9f7401b144e35049bbf1e3cb32 206508 
id-utils_4.6+git20190113-1_amd64.deb
Checksums-Sha256:
 975513a9bf3bff44b52b02ee6650fcee94ee1c6610b25fc25c5a48007d96cdf3 1750 
id-utils_4.6+git20190113-1.dsc
 96c3105f82966c8ebde3bd149cd7bc208ac151e5c260519d98da63c6b9acda96 8437472 
id-utils_4.6+git20190113.orig.tar.gz
 957b184f4566156298c78c857a66209e792d6931030bec9a89ca9200cfa2ff5a 117895 
id-utils_4.6+git20190113-1.diff.gz
 9fc5d1bc7fa3c4f4152d7e8cb1b3a7f7ecdfa5ff89ff7a4a5db7a77197a3f007 856532 
id-utils-dbgsym_4.6+git20190113-1_amd64.deb
 a7ffb6ec6cd9e133f1bbbe8c49bd01757cbcb80814998298a95964d055988043 5927 
id-utils_4.6+git20190113-1_amd64.buildinfo
 32a50eaa133b40696dbda9c2a0084b92ff1f7a33ae410857617f13da1132621e 206508 
id-utils_4.6+git20190113-1_amd64.deb
Files:
 bfd87e150fba8879672677226f9d9f90 1750 devel optional 
id-utils_4.6+git20190113-1.dsc
 ac832040d78f979aeafbb4cf32a9 8437472 devel optional 
id-utils_4.6+git20190113.orig.tar.gz
 32ea88fd7eaa072b0196d7fa0de017b1 117895 devel optional 
id-utils_4.6+git20190113-1.diff.gz
 4a607302747fe258f8065595041df4f9 856532 debug optional 
id-utils-dbgsym_4.6+git20190113-1_amd64.deb
 ac3a2df762b0f6f2a12f1167fcf9b0b5 5927 devel optional 
id-utils_4.6+git20190113-1_amd64.buildinfo
 6462033415d473111d7ae07ca2869eea 206508 devel optional 
id-uti

Bug#921800: nvchecker: FTBFS (failing tests)

2019-02-08 Thread Afif Elghraoui



On February 8, 2019 7:59:10 PM EST, Santiago Vila  wrote:
>> It looks like a network access problem. The whole point of this
>> package is to check online sources, so it's hard to test it without
>> network access. I was able to build it just fine in my schroot, but I
>> may have to disable the tests so the buildds can operate...
>
>If you have to do that, please do so.

fair enough

> Packages must not use the
>network during the build, other than installing the build-dependencies.
>This is actually written in Release Policy.
>
>Think about somebody building packages in a desert island and the
>package failing because it can't connect to the outside world.
>
>However, I don't deliberately disable network access in my
>autobuilders, so if just by looking at my build log you remembered
>that your package was doing network access, that's a good thing anyway
>:-)
>
>[ While we are at it, please try uploading in source-only form
>  (dpkg-buildpackage -S). It helps me a lot by preventing certain kind
>  of bugs to propagate to testing (where I usually do my test builds).
> This also creates and keeps archived official build logs for the "all"
>  architecture ].
>

I'm with you. I always do so whenever I can, but this was the first upload and 
needed to be a binary upload to go through NEW...

regards
Afif



Processed: affects 921637

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Actually affects the source and not the bbinary package
> affects 921637 + src:git-lfs
Bug #921637 [ronn] ronn 0.8.0-1 breaks man pages with numbered lists
Added indication that 921637 affects src:git-lfs
> thanks
Stopping processing here.

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



Bug#921800: nvchecker: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Hi.

Correction: I can't find the network issue in Release Policy right now
but it's a Debian Policy violation anyway.

(In other words: please don't do it :-)

Thanks.



Processed: severity of 917723 is normal

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 917723 normal
Bug #917723 [golang-github-mitchellh-mapstructure-dev] 
golang-github-mitchellh-mapstructure-dev: regression in 1.1.2 caused packer 
FTBFS
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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



Bug#921800: nvchecker: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
> It looks like a network access problem. The whole point of this
> package is to check online sources, so it's hard to test it without
> network access. I was able to build it just fine in my schroot, but I
> may have to disable the tests so the buildds can operate...

If you have to do that, please do so. Packages must not use the
network during the build, other than installing the build-dependencies.
This is actually written in Release Policy.

Think about somebody building packages in a desert island and the
package failing because it can't connect to the outside world.

However, I don't deliberately disable network access in my
autobuilders, so if just by looking at my build log you remembered
that your package was doing network access, that's a good thing anyway :-)

[ While we are at it, please try uploading in source-only form
  (dpkg-buildpackage -S). It helps me a lot by preventing certain kind
  of bugs to propagate to testing (where I usually do my test builds).
  This also creates and keeps archived official build logs for the "all"
  architecture ].

Thanks.



Bug#917723: golang-github-mitchellh-mapstructure-dev: regression in 1.1.2 caused packer FTBFS

2019-02-08 Thread Shengjing Zhu
Package: golang-github-mitchellh-mapstructure-dev
Version: 1.1.2-1
Followup-For: Bug #917723

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: severity -1 normal

I just found one critical library[1][2] was already patched to depend
on this bug behaviour.

So I vendored the old mapstructure in packer, to ease the stress before
buster freeze.

[1] https://tracker.debian.org/pkg/golang-github-spf13-viper
[2] https://github.com/spf13/viper/issues/579

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxeJPkQHHpoc2pAZGVi
aWFuLm9yZwAKCRA40A8AGL4+NTkTCACMBFOvl2b3Q9BLRmkQUSoFw7GbK0glRXd0
4W5FMZPbVk8Y4BO+F9tOcHipv6GZZrsptwAnkuTkhlfRmPGxgUu0RAInE9ce9+2v
L064i7BLdqVIhMLLRIvazLSBtRUSTw5ZgaBaI1Zs9LQjLHI7CEwf3+U5e7nRfh3E
t2ZYgRa3G8vvmOaWYPEFpuIje640WJjvPmhcNfX2Pqkgqckej/6IP+tDxQgT/abz
+wRmaBbkVcsJK4sYHwTTQf34ZtP9vK2kNnYlqV18OIMc1J+b3sOQ/lFOojOgTeVo
07Qyy81xsub+PGwkRSZhvsQFtP3BSMGM+vCiUb/zxP9RnJIw7jPv
=Uc6v
-END PGP SIGNATURE-



Bug#921791: marked as done (litl: FTBFS (LaTeX error))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 00:50:56 +
with message-id 
and subject line Bug#921791: fixed in litl 0.1.9-4
has caused the Debian Bug report #921791,
regarding litl: FTBFS (LaTeX error)
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.)


-- 
921791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:litl
Version: 0.1.9-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with autoreconf
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'

[... snipped ...]




LaTeX Warning: Reference `litl__write_8h' on page 5 undefined on input line 18.



LaTeX Warning: Reference `utils_2litl__merge_8c' on page 5 undefined on input l
ine 19.


LaTeX Warning: Reference `litl__print_8c' on page 5 undefined on input line 20.



LaTeX Warning: Reference `utils_2litl__split_8c' on page 5 undefined on input l
ine 21.

) [5] [6]
Chapter 4.
(./group__litl__merge.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
 
}
l.32 \end{DoxyParams}
 
? 
! Emergency stop.
 
}
l.32 \end{DoxyParams}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/doc/latex'
make[2]: *** [Makefile:539: latex/refman.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:444: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: litl
Source-Version: 0.1.9-4

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated litl 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: Sat, 09 Feb 2019 01:25:39 +0100
Source: litl
Binary: liblitl-dev liblitl0 liblitl0-dbgsym litl-doc litl-tools 
litl-tools-dbgsym
Architecture: source
Version: 0.1.9-4
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 liblitl-dev - Lightweight Trace Library - development files
 liblitl0   - Lightweight Trace Library - shared library
 litl-doc   - Lightweight Trace Library - documentation
 litl-tools - Lightweight Trace Library - tools
Closes: 921791
Changes:
 litl (0.1.9-4) unstable; urgency=medium
 .
   * doc-nopdf: Disable building the pdf version of the
 documentation (Closes: Bug#921791)
Checksums-Sha1:
 5ff50e4369232cead8360e4f2efd939cf86a6ecc 2140 litl_0.1.9-4.dsc
 86f7834bf6859b23f7654f170a99d59caeb8cef6 5108 litl_0.

Bug#921800: nvchecker: FTBFS (failing tests)

2019-02-08 Thread Afif Elghraoui
Hello,

On February 8, 2019 7:15:55 PM EST, Santiago Vila  wrote:
>Package: src:nvchecker
>Version: 1.3-1
>Severity: serious
>Tags: ftbfs
>
>Dear maintainer:
>
>I tried to build this package in buster but it failed:
>
>
[...]
>
>async with session.get(url) as res:
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>_ _ _ _ 
>
>self = 0x7f4ba58c7c50>
>
>async def __aenter__(self):
>> return await to_asyncio_future(client.fetch(self.req))
>E tornado.httpclient.HTTPClientError: HTTP 502: Proxy Error
>
>nvchecker/source/tornado_httpclient.py:62: HTTPClientError
...
>The build was made in my autobuilder with "dpkg-buildpackage -A"
>and it also fails here:
>
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nvchecker.html
>
>where you can get a full build log if you need it.
>
>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 BTS web page for this package.
>

It looks like a network access problem. The whole point of this package is to 
check online sources, so it's hard to test it without network access. I was 
able to build it just fine in my schroot, but I may have to disable the tests 
so the buildds can operate...

regards
Afif



Bug#905697: kdepimlibs: don't depend on libical

2019-02-08 Thread Scott Kitterman
What about porting it to libical3?  That might be easier.  I tried to build it 
and it does need some changes, but I don't think keeping libical2 is feasible.  
See the attached for the error.

Scott K

On Friday, February 08, 2019 10:46:21 PM Sandro Knauß wrote:
> Hey,
> 
> for me it looks like we won't be able to get kdepimlibs without libical 2
> for buster.
> Keep in mind, that kdepimlibs is an old grufted lib set that we also would
> like to kill. But we also have other packages depending on it like:
> * basket
> * kopete (it has a QT5 version in experimental, but this is suitable as
> replacement yet).
>  and other that may can be killed.
> 
> extract libical 2 out of kdepimlibs is not that simple, as the whole
> interface will leak into akonadi-calendar, calcore, calutils,...
> 
> In short I won't have the time to do the work and test it in the near
> future.
> 
> I added pino to this bug report, as pino successfully extracted other parts
> of old kdelibs/kdepimlibs.
> 
> hefee
> 
> --
> 
> On Donnerstag, 17. Januar 2019 12:11:46 CET Emilio Pozuelo Monfort wrote:
> > On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote:
> > > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote:
> > >> Source: kdepimlibs
> > >> Version: 4:4.14.10-10
> > >> Severity: serious
> > >> Control: block 884128 with -1
> > >> 
> > >> Hi,
> > >> 
> > >> libical2 from src:libical is superseded by libical3 (src:libical3).
> > >> 
> > >> Please either port kdepimlibs to libical3 or try to disable the
> > >> libical support, so that we can only ship src:libical3 in buster.
> > > 
> > > Could someone who knows kdepimlibs take a look at this? Can we disable
> > > libical support in kdepimlibs for buster? This is the last blocker for
> > > the libical 2 removal.
> > 
> > Hi Sandro,
> > 
> > Lisandro said you may be able to help with this. Do you know if libical
> > support could be disabled in kdepimlibs, or if the newer version libical3
> > could be used?
> > 
> > >From [1] it seems that libical is kind of optional, though I don't know
> > >if
> > >we
> > 
> > can disable the bits to drop that or if those bits have rdeps. Since
> > kdepimlibs is the last rdep of the old libical version, fixing this would
> > allow us to drop that one from buster. Otherwise the RC bugs that it has
> > will need to be fixed and we'll have to ship with two versions of the
> > library.
> > 
> > Thanks,
> > Emilio
> > 
> > [1]
> > https://sources.debian.org/src/kdepimlibs/4:4.14.10-10/CMakeLists.txt/#L81
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function 
'static icaltimetype KCalCore::ICalFormatImpl::writeICalDate(const QDate&)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2304:7: error: 
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did 
you mean 'is_date'?
 t.is_utc = 0;
   ^~
   is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function 
'static icaltimetype KCalCore::ICalFormatImpl::writeICalDateTime(const 
KDateTime&)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2326:7: error: 
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did 
you mean 'is_date'?
 t.is_utc = datetime.isUtc() ? 1 : 0;
   ^~
   is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function 
'static icalproperty* 
KCalCore::ICalFormatImpl::writeICalDateTimeProperty(icalproperty_kind, const 
KDateTime&, KCalCore::ICalTimeZones*, KCalCore::ICalTimeZones*)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2401:12: error: 
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did 
you mean 'is_date'?
 if (!t.is_utc) {
^~
is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function 
'static KDateTime KCalCore::ICalFormatImpl::readICalDateTime(icalproperty*, 
const icaltimetype&, KCalCore::ICalTimeZones*, bool)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2434:11: error: 'const 
icaltimetype' {aka 'const struct icaltimetype'} has no member named 'is_utc'; 
did you mean 'is_date'?
 if (t.is_utc  ||  t.zone == icaltimezone_get_utc_timezone()) {
   ^~
   is_date


Bug#921807: sketch: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:sketch
Version: 1:0.3.7-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
perl makever.pl
not generating web page
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
make -j1
make[2]: Entering directory '/<>'

[... snipped ...]

(/usr/share/texlive/texmf-dist/tex/generic/pst-node/pst-node.tex)))
(/usr/share/texlive/texmf-dist/tex/latex/pst-text/pst-text.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-text/pst-text.tex
 v1.01, 2018/12/22(tvz,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/pst-3d/pst-3d.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-3d/pst-3d.tex))
(/usr/share/texlive/texmf-dist/tex/latex/pst-eps/pst-eps.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-eps/pst-eps.tex
 v1.00, 2006/11/04))
(/usr/share/texlive/texmf-dist/tex/latex/pst-fill/pst-fill.sty
(/usr/share/texlive/texmf-dist/tex/generic/pst-fill/pst-fill.tex
`PST-Fill' v1.01, 2007/03/10 (tvz,dg,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/pstricks-add/pstricks-add.sty
(/usr/share/texlive/texmf-dist/tex/latex/pst-math/pst-math.sty
(/usr/share/texlive/texmf-dist/tex/latex/pst-calculate/pst-calculate.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3dvips.def)))
(/usr/share/texlive/texmf-dist/tex/latex/siunitx/siunitx.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty)
(/usr/share/texlive/texmf-dist/tex/latex/translator/translator.sty)))
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)

! LaTeX Error: File `xstring.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
! Emergency stop.
 
 
l.19 \input
pst-math.tex^^M
No pages of output.
Transcript written on ex000-tmp.log.
Inappropriate ioctl for device at make.pl line 34,  line 1.
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921789: librostlab-blast: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'

[... snipped ...]

LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input 
line 5.


LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.


LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.


LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.


) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)

LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font)  using `T1/pcr/m/n' instead on input line 27.

[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
 
}
l.253 \end{DoxyParams}
  
? 
! Emergency stop.
 
}
l.253 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librostlab-blast.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921802: primesieve: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --builddirectory=_build
   dh_update_autotools_config -i -O--builddirectory=_build
   dh_autoreconf -i -O--builddirectory=_build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON 
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works

[... snipped ...]

LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.


LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.


LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.


LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.



LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input 
line 7.

) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
 
}
l.175 \end{DoxyParams}
  
? 
! Emergency stop.
 
}
l.175 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory 
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921799: node-serve-index: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-serve-index
Version: 1.4.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -C --reporter spec --bail --check-leaks test/


  serveIndex(root)
✓ should require root
✓ should serve text/html without Accept header (139ms)
✓ should serve a directory index
✓ should work with HEAD requests
✓ should work with OPTIONS requests
✓ should deny POST requests
✓ should deny path will NULL byte
✓ should deny path outside root
✓ should skip non-existent paths
1) should treat an ENAMETOOLONG as a 414


  9 passing (329ms)
  1 failing

  1) serveIndex(root)
   should treat an ENAMETOOLONG as a 414:
 Error: expected 414 "URI Too Long", got 400 "Bad Request"
  at Test.assert (/usr/lib/nodejs/supertest/lib/test.js:205:15)
  at Server.assert (/usr/lib/nodejs/supertest/lib/test.js:132:12)
  at emitCloseNT (net.js:1616:8)
  at process._tickCallback (internal/process/next_tick.js:63:19)



make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-serve-index.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921792: log4c: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:log4c
Version: 1.2.1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --list-missing
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--list-missing
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoreconf --verbose --force --install --include=config
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal -I config --force 
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
autoreconf: configure.in: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.

[... snipped ...]



LaTeX Warning: Reference `rollingpolicy__type__sizewin_8h' on page 6 undefined 
on input line 23.


Underfull \vbox (badness 1308) has occurred while \output is active [6]

LaTeX Warning: Reference `version_8h' on page 7 undefined on input line 24.

) (./structlog4c__appender__type.tex) (./structlog4c__buffer__t.tex)
(./structlog4c__layout__type.tex [7]) (./structlog4c__location__info__t.tex)
(./structlog4c__logging__event__t.tex [8]) (./structlog4c__rc__t.tex

LaTeX Warning: Reference `init_8h_aaa454b3272145399cf10a897819c8a05' on page 9 
undefined on input line 20.

[9]) (./structlog4c__rollingpolicy__type.tex) (./appender_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--11

[10] [11]
! Missing } inserted.
 
}
l.87 \end{DoxyParams}
 
? 
! Emergency stop.
 
}
l.87 \end{DoxyParams}
 
Output written on refman.dvi (12 pages, 31964 bytes).
Transcript written on refman.log.
make[4]: *** [Makefile:19: refman.dvi] Error 1
make[4]: Leaving directory '/<>/doc/latex'
make[3]: *** [Makefile:482: log4c.pdf] Error 2
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:530: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:394: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921800: nvchecker: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:nvchecker
Version: 1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/slogconf.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/sortversion.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/core.py -> 
/<>/.pybuild/cpython3_3.7/build/nvchecker

[... snipped ...]

async with session.get(url) as res:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

async def __aenter__(self):
> return await to_asyncio_future(client.fetch(self.req))
E tornado.httpclient.HTTPClientError: HTTP 502: Proxy Error

nvchecker/source/tornado_httpclient.py:62: HTTPClientError
===Flaky Test Report===

test_archpkg passed 1 out of the required 1 times. Success!
test_archpkg_strip_release passed 1 out of the required 1 times. Success!
test_aur passed 1 out of the required 1 times. Success!
test_aur_strip_release passed 1 out of the required 1 times. Success!
test_aur_use_last_modified passed 1 out of the required 1 times. Success!
test_debianpkg passed 1 out of the required 1 times. Success!
test_debianpkg_strip_release passed 1 out of the required 1 times. Success!
test_debianpkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg passed 1 out of the required 1 times. Success!
test_ubuntupkg_strip_release passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite_with_paging passed 1 out of the required 1 times. Success!

===End Flaky Test Report===
=== warnings summary ===
tests/test_regex.py:12
  /<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:12: 
DeprecationWarning: invalid escape sequence \w
"regex": '"User-Agent": "(\w+)"',

tests/test_regex.py:19
  /<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:19: 
DeprecationWarning: invalid escape sequence \w
"regex": 'for (\w+) examples',

tests/test_substitute.py:20
  /<>/.pybuild/cpython3_3.7/build/tests/test_substitute.py:20: 
DeprecationWarning: invalid escape sequence \d
assert await get_version("example", {"manual": "r15", "prefix": "r", 
"from_pattern": "r(\d+)", "to_pattern": "R\1"}) == "15"

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 1 failed, 40 passed, 18 skipped, 3 warnings in 13.15 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7/build; python3.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
exit code 13
make: *** [debian/rules:6: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921803: python-scrapy: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:python-scrapy
Version: 1.5.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,bash_completion,sphinxdoc 
--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_scrapy/build/scrapy

[... snipped ...]

  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:24:
 ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed 
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()

.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::SgmlLinkExtractorTestCase::test_xhtml
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:421:
 ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed 
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:432:
 ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed 
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()

.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::RegexLinkExtractorTestCase::test_html_base_href
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py:228:
 ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed 
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = RegexLinkExtractor()

.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::RegexLinkExtractorTestCase::test_link_wrong_href
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py:210:
 ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed 
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = RegexLinkExtractor()

.pybuild/cpython2_2.7_scrapy/build/tests/test_spider.py::CrawlSpiderTest::test_follow_links_attribute_deprecated_population
  
/<>/.pybuild/cpython2_2.7_scrapy/build/scrapy/spiders/crawl.py:106:
 ScrapyDeprecationWarning: set_crawler is deprecated, instantiate and bound the 
spider to this crawler with from_crawler method instead.
super(CrawlSpider, self).set_crawler(crawler)
  
/<>/.pybuild/cpython2_2.7_scrapy/build/scrapy/spiders/crawl.py:106:
 ScrapyDeprecationWarning: set_crawler is deprecated, instantiate and bound the 
spider to this crawler with from_crawler method instead.
super(CrawlSpider, self).set_crawler(crawler)

.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_deprecate.py::WarnWhenSubclassedTest::test_warning_on_instance
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_deprecate.py:115:
 MyWarning: tests.test_utils_deprecate.UserClass inherits from deprecated class 
tests.test_utils_deprecate.Deprecated, please inherit from 
tests.test_utils_deprecate.NewName. (warning only on first subclass, there may 
be others)
class UserClass(Deprecated):

.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:157:
 ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(d, keys_only=False)

.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict_keys_only
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:176:
 ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(d)

.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict_tuples
  
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:167:
 ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(tuples, keys_only=False)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 1 failed, 1648 passed, 13 skipped, 14 xfailed, 427 warnings in 373.86 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_scrapy/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:9: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2
---

Bug#921806: ruby-api-pagination: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:ruby-api-pagination
Version: 4.2.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

  ArgumentError:
unknown keywords: count, page
  Shared Example Group: "an endpoint with a middle page" called from 
./spec/rails_spec.rb:58
  # ./spec/rails_spec.rb:56:in `block (5 levels) in '

Finished in 0.20069 seconds (files took 1.92 seconds to load)
56 examples, 27 failures

Failed examples:

rspec ./spec/rails_spec.rb:30 # NumbersController GET #index without enough 
items to give more than one page should list all numbers in the response body
rspec ./spec/rails_spec.rb:26 # NumbersController GET #index without enough 
items to give more than one page should give a Per-Page header
rspec ./spec/rails_spec.rb:22 # NumbersController GET #index without enough 
items to give more than one page should give a Total header
rspec ./spec/rails_spec.rb:18 # NumbersController GET #index without enough 
items to give more than one page should not paginate
rspec ./spec/rails_spec.rb:91 # NumbersController GET #index with custom 
response headers should give a X-Total-Count header
rspec ./spec/rails_spec.rb:99 # NumbersController GET #index with custom 
response headers should give a X-Per-Page header
rspec ./spec/rails_spec.rb:107 # NumbersController GET #index with custom 
response headers should give a X-Page header
rspec ./spec/rails_spec.rb:118 # NumbersController GET #index configured not to 
include the total should not include a Total header
rspec ./spec/rails_spec.rb:63 # NumbersController GET #index providing a block 
yields to the block instead of implicitly rendering
rspec './spec/rails_spec.rb[1:1:2:1:3]' # NumbersController GET #index with 
existing Link headers behaves like an endpoint with existing Link headers 
should give a Total header
rspec './spec/rails_spec.rb[1:1:2:1:1]' # NumbersController GET #index with 
existing Link headers behaves like an endpoint with existing Link headers 
should keep existing Links
rspec './spec/rails_spec.rb[1:1:2:1:2]' # NumbersController GET #index with 
existing Link headers behaves like an endpoint with existing Link headers 
should contain pagination Links
rspec './spec/rails_spec.rb[1:1:3:1:1:3]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should give a link with rel "last"
rspec './spec/rails_spec.rb[1:1:3:1:1:6]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should list the first page of numbers in the response body
rspec './spec/rails_spec.rb[1:1:3:1:1:4]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should give a link with rel "next"
rspec './spec/rails_spec.rb[1:1:3:1:1:5]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should give a Total header
rspec './spec/rails_spec.rb[1:1:3:1:1:1]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should not give a link with rel "first"
rspec './spec/rails_spec.rb[1:1:3:1:1:2]' # NumbersController GET #index with 
enough items to paginate when on the first page behaves like an endpoint with a 
first page should not give a link with rel "prev"
rspec './spec/rails_spec.rb[1:1:3:2:1:2]' # NumbersController GET #index with 
enough items to paginate when on the last page behaves like an endpoint with a 
last page should not give a link with rel "next"
rspec './spec/rails_spec.rb[1:1:3:2:1:3]' # NumbersController GET #index with 
enough items to paginate when on the last page behaves like an endpoint with a 
last page should give a link with rel "first"
rspec './spec/rails_spec.rb[1:1:3:2:1:6]' # NumbersController GET #index with 
enough items to paginate when on the last page behaves like an endpoint with a 
last page should list the last page of numbers in the response body
rspec './spec/rails_spec.rb[1:1:3:2:1:5]' # NumbersController GET #index with 
enough items to paginate when on the last page behaves like an endpoint with a 
last page should give a Total header
rspec './spec/rails_spec.rb[1:1:3:2:1:4]' # NumbersController GET #index with

Bug#921794: node-cross-spawn-async: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-cross-spawn-async
Version: 2.2.5-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/prepare && mocha -C -R spec test/test
Copied "prepare_()%!^&;, .sh" to "()%!^&;, "


  cross-spawn-async
1) should support shebang in executables with /usr/bin/env
2) should support shebang in executables without /usr/bin/env
3) should support shebang in executables with relative path
✓ should support shebang in executables with relative path that starts 
with `..` (1538ms)
4) should support shebang in executables with extensions
✓ should expand using PATHEXT properly
✓ should handle commands with spaces
✓ should handle commands with special shell chars
✓ should handle arguments with quotes (1744ms)
✓ should handle empty arguments (1244ms)
✓ should handle non-string arguments (1236ms)
✓ should handle arguments with spaces (1196ms)
✓ should handle arguments with \" (1237ms)
✓ should handle arguments that end with \ (1213ms)
✓ should handle arguments that contain shell special chars (1202ms)
✓ should handle special arguments when using echo
✓ should handle optional args correctly (63ms)
✓ should not mutate args nor options
✓ should give correct exit code (1216ms)
✓ should work with a relative command
✓ should emit "error" and "close" if command does not exist (1024ms)
✓ should NOT emit "error" if shebang command does not exist (1013ms)
✓ should NOT emit "error" if the command actual exists but exited with 1 
(1012ms)


  19 passing (23s)
  4 failing

  1) cross-spawn-async
   should support shebang in executables with /usr/bin/env:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  2) cross-spawn-async
   should support shebang in executables without /usr/bin/env:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  3) cross-spawn-async
   should support shebang in executables with relative path:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  4) cross-spawn-async
   should support shebang in executables with extensions:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)



make[1]: *** [debian/rules:11: override_dh_auto_test] Error 4
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cross-spawn-async.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921798: node-mocha: FTBFS (Module not found: Error: Recursion in resolving)

2019-02-08 Thread Santiago Vila
Package: src:node-mocha
Version: 4.1.0+ds3-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-mocha-4.1.0+ds3'
NODE_PATH='/usr/share/nodejs:/usr/lib/nodejs' webpack --verbose --config 
debian/webpack.config.js
Hash: 87cc69c5bf02c862585f
Version: webpack 3.5.6
Time: 2463ms
   AssetSize  ChunksChunk Names
mocha.js  458 kB   0  [emitted]  [big]  main
Entrypoint main [big] = mocha.js

[... snipped ...]

  raw-module: (/<>/node-mocha-4.1.0+ds3) buffer
  module: (/<>/node-mocha-4.1.0+ds3) buffer
  resolve: (/usr/share/nodejs) ./buffer
  new-resolve: (/usr/share/nodejs) ./buffer
  parsed-resolve: (/usr/share/nodejs) ./buffer
  described-resolve: (/usr/share/nodejs) ./buffer
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
 @ /usr/lib/nodejs/core-util-is/lib/util.js 1:0-79
 @ /usr/lib/nodejs/readable-stream/lib/_stream_duplex.js
 @ /usr/lib/nodejs/readable-stream/readable-browser.js
 @ /usr/lib/nodejs/stream-browserify/index.js
 @ /usr/lib/nodejs/browser-stdout/index.js
 @ ./browser-entry.js

ERROR in /usr/share/javascript/util/support/isBuffer.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  new-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  parsed-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  described-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  relative: (/<>/node-mocha-4.1.0+ds3/buffer) 
  described-relative: (/<>/node-mocha-4.1.0+ds3/buffer) 
  raw-file: (/<>/node-mocha-4.1.0+ds3/buffer) 
  file: (/<>/node-mocha-4.1.0+ds3/buffer) 
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
  new-resolve: (/<>/node-mocha-4.1.0+ds3) buffer
  parsed-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module
  described-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module
  raw-module: (/<>/node-mocha-4.1.0+ds3) buffer
  module: (/<>/node-mocha-4.1.0+ds3) buffer
  resolve: (/usr/share/nodejs) ./buffer
  new-resolve: (/usr/share/nodejs) ./buffer
  parsed-resolve: (/usr/share/nodejs) ./buffer
  described-resolve: (/usr/share/nodejs) ./buffer
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
 @ /usr/share/javascript/util/support/isBuffer.js 1:0-79
 @ /usr/share/javascript/util/util.js
 @ ./lib/utils.js
 @ ./lib/mocha.js
 @ ./browser-entry.js
make[1]: *** [debian/rules:23: mocha.js] Error 2
make[1]: Leaving directory '/<>/node-mocha-4.1.0+ds3'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921804: rt-extension-jsgantt: FTBFS (mv: cannot stat 'Makefile': No such file or directory)

2019-02-08 Thread Santiago Vila
Package: src:rt-extension-jsgantt
Version: 1.03-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RT/Extension/JSGantt.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-jsgantt.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921793: mono-tools: FTBFS (error CS0618: Warning as Error)

2019-02-08 Thread Santiago Vila
Package: src:mono-tools
Version: 4.2-2.2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf,xsp,cli
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_autoreconf -i
sh: 1: ACLOCAL_FLAGS: not found
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libexecdir=\${prefix}/lib/mono-tools 
--disable-maintainer-mode --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

[... snipped ...]

Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature 
Subscript;
Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature Sort;
Member Added: public override void Initialize (Gendarme.Framework.IRunner 
runner);
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseIsOperatorRule
Member Added: public UseIsOperatorRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseStringEmptyRule
Member Added: public UseStringEmptyRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseTypeEmptyTypesRule
Member Added: public UseTypeEmptyTypesRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
Members Added: 86, Members Deleted: 0
touch doc/generated/index.xml
mdoc assemble -f ecma -o doc/Gendarme.Rules.Performance doc/generated 
echo -e "\n\n\t\n\t\n" > 
doc/Gendarme.Rules.Performance.source 
make[5]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Performance'
make[4]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Performance'
Making all in Gendarme.Rules.Portability
make[4]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
Making all in Test
make[5]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
/usr/bin/mono-csc -target:library -debug+ -d:TRACE -optimize+ -nowarn:1591  
-warn:4 -warnaserror+ -r:ICSharpCode.SharpZipLib.dll -r:System.Web.Services.dll 
-nowarn:1591 -doc:../../bin/Gendarme.Rules.Portability.dll.doc \
-r:/usr/lib/mono-cecil/Mono.Cecil.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Mdb.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Pdb.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Rocks.dll -r:../../bin/Gendarme.Framework.dll 
-out:../../bin/Gendarme.Rules.Portability.dll ./DoNotHardcodePathsRule.cs 
./ExitCodeIsLimitedOnUnixRule.cs ./FeatureRequiresRootPrivilegeOnUnixRule.cs 
./MoMAWebService.cs ./MonoCompatibilityReviewRule.cs ./NewLineLiteralRule.cs 
../../AssemblyInfo.cs ./../../AssemblyStaticInfo.cs
./MonoCompatibilityReviewRule.cs(179,11): error CS0618: Warning as Error: 
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has 
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ 
instead.'
./MonoCompatibilityReviewRule.cs(179,35): error CS0618: Warning as Error: 
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has 
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ 
instead.'
./MonoCompatibilityReviewRule.cs(181,5): error CS0618: Warning as Error: 
`ICSharpCode.SharpZipLib.Zip.ZipEntry' is obsolete: `This assembly has been 
deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ instead.'
Compilation failed: 3 error(s), 0 warnings
make[5]: *** [Makefile:795: ../../bin/Gendarme.Rules.Portability.dll] Error 1
make[5]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
make[4]: *** [Makefile:516: all-recursive] Error 1
make[4]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
make[3]: *** [Makefile:400: all-recursive] Error 1
make[3]: Leaving directory '/<>/gendarme/rules'
make[2]: *** [Makefile:487: all-recursive] Error 1
make[2]: Leaving directory '/<>/gendarme'
make[1]: *** [Makefile:408: all-recursive] Error 1
make[1]: Leaving directory '/<>'
d

Bug#921782: gmpc: FTBFS (error: Assigning delegate without required target)

2019-02-08 Thread Santiago Vila
Package: src:gmpc
Version: 11.8.16-14
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:44: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
configure.ac:44: the top level

[... snipped ...]


Widgets/GmpcVolume.vala:111.40-111.70: warning: use of possibly unassigned 
parameter `requisition'
public override void size_request (out Gtk.Requisition requisition) {
   ^^^
Providers/music-tree.vala:212.8-212.32: warning: use of possibly unassigned 
parameter `list'

list.append((owned)item);

^
Providers/music-tree.vala:176.3-176.30: warning: use of possibly unassigned 
parameter `list'
out List list,

Providers/music-tree.vala:244.3-244.27: warning: use of possibly unassigned 
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:250.4-250.28: warning: use of possibly unassigned 
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:256.5-256.29: warning: use of possibly unassigned 
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:233.3-233.35: warning: use of possibly unassigned 
parameter `list'
out List list,
^
Widgets/gmpc-widgets-qtable.vala:26.2-26.8: warning: attribute `compact' never 
used
[compact]
 ^^^
Providers/HTBackdrops.vala:186.23-186.30: warning: copying delegates is not 
supported
Providers/LyrDB.vala:240.17-240.24: warning: copying delegates is not supported
Providers/ChartLyrics.vala:109.23-109.30: warning: copying delegates is not 
supported
vala/gmpc-easy-command.vala:213.6-213.79: error: Assigning delegate without 
required target in scope
model.get(iter, 1, out name, 2, out 
pattern, 3, out callback, 4, out data);

^^
vala/gmpc-url-fetching-gui.vala:88.26-88.39: warning: copying delegates is not 
supported
vala/gmpc-url-fetching-gui.vala:89.29-89.45: warning: copying delegates is not 
supported
Compilation failed: 1 error(s), 667 warning(s)
make[4]: *** [Makefile:2201: gmpc_vala.stamp] Error 1
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:849: all] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:498: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:426: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-08 Thread Santiago Vila
Package: src:fis-gtm
Version: 6.3-005-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 
-DCMAKE_BUILD_TYPE=Release
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 
-DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is GNU 8.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]


Run Build Command:"/usr/bin/make" "cmTC_76390/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_76390.dir/build.make 
CMakeFiles/cmTC_76390.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_76390.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_76390.dir/feature_tests.c.o  
 -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c
Linking C executable cmTC_76390
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_76390.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_76390.dir/feature_tests.c.o  -o cmTC_76390 
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:1c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:1c_variadic_macros


Detecting C [-std=c90] compiler features compiled with the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_da08a/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_da08a.dir/build.make 
CMakeFiles/cmTC_da08a.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_da08a.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_da08a.dir/feature_tests.c.o  
 -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c
Linking C executable cmTC_da08a
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_da08a.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_da08a.dir/feature_tests.c.o  -o cmTC_da08a 
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:0c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:0c_variadic_macros
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 
-DCMAKE_BUILD_TYPE=Release .. returned exit code 1
make[1]: *** [debian/rules:24: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The bui

Bug#921780: esajpip: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:esajpip
Version: 0.1~bzr33-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
/usr/bin/make documentation
make[2]: Entering directory '/<>'
make -C doc
make[3]: Entering directory '/<>/doc'
fig2dev -L pstex jpip_fig.fig > jpip_fig.eps
(fig2dev -L pstex_t -p jpip_fig jpip_fig.fig | sed 
's/includegraphics{/includegraphics{..\//g') > jpip_fig.tex
epstopdf jpip_fig.eps
fig2dev -L pstex partition.fig > partition.eps

[... snipped ...]


LaTeX Warning: Reference `socket_8h' on page 10 undefined on input line 92.


LaTeX Warning: Reference `socket__stream_8cc' on page 10 undefined on input lin
e 93.


LaTeX Warning: Reference `socket__stream_8h' on page 10 undefined on input line
 94.

) [10]
Chapter 5.
(./namespacedata.tex (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
[11]
Underfull \hbox (badness 1) detected at line 68
[][][]

Underfull \hbox (badness 1) detected at line 83
[][][]
) (./namespacehttp.tex [12]) (./namespaceipc.tex [13]
! Missing } inserted.
 
}
l.58 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.58 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory '/<>/doc/latex'
make[3]: *** [Makefile:23: documentation] Error 2
rm codestream.eps partition.eps client_manager.eps architecture.eps jpip_fig.eps
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:111: documentation] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:29: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921779: doxygen: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:doxygen
Version: 1.8.13-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
/usr/bin/make -C jquery install
make[1]: Entering directory '/<>/jquery'
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > 
jquery-1.7.1-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js 
> jquery.ui-1.8.18.core-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js 
> jquery.scrollTo-1.4.2-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js 
> jquery.powertip-1.2.0-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js

[... snipped ...]

[100%] Generating trouble.doc
cd /<>/build/doc && /usr/bin/cmake -E copy 
/<>/doc/trouble.doc /<>/build/doc/
[100%] Generating xmlcmds.doc
cd /<>/build/doc && /usr/bin/cmake -E copy 
/<>/doc/xmlcmds.doc /<>/build/doc/
[100%] Generating Latex and HTML documentation.
cd /<>/build/doc && /<>/build/bin/doxygen
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./_formulas.tex
LaTeX2e <2018-12-01>

make[4]: Leaving directory '/<>/build'
[100%] Built target run_doxygen
/usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make 
doc/CMakeFiles/doxygen_pdf.dir/depend
make[4]: Entering directory '/<>/build'
cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/<> /<>/doc /<>/build 
/<>/build/doc 
/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color=
Dependee 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is 
newer than depender 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal".
Dependee 
"/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is 
newer than depender 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal".
Scanning dependencies of target doxygen_pdf
make[4]: Leaving directory '/<>/build'
/usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make 
doc/CMakeFiles/doxygen_pdf.dir/build
make[4]: Entering directory '/<>/build'
[100%] Generating Doxygen Manual PDF.
cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex
cd /<>/build/latex && /usr/bin/cmake -E copy 
/<>/build/doc/doxygen_manual.tex .
cd /<>/build/latex && /usr/bin/cmake -E copy 
/<>/build/doc/manual.sty .
cd /<>/build/latex && /usr/bin/epstopdf 
/<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf
cd /<>/build/latex && /usr/bin/pdflatex -shell-escape 
doxygen_manual.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 \write18 enabled.
entering extended mode
(./doxygen_manual.tex
LaTeX2e <2018-12-01>

make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: 
doc/CMakeFiles/doxygen_pdf] Error 1
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] 
Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2
make[2]: Leaving directory '/<>/build'
make[1]: *** [Makefile:301: docs] Error 2
make[1]: Leaving directory '/<>/build'
make: *** [debian/rules:60: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921783: graphite2: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:graphite2
Version: 1.3.13-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=cmake --builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release 
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu 
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON 
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2", 
minimum required is "3.6") 
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.


LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.


LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.


LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.

) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
 
}
l.84 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.84 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90: 
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921788: libdc1394-22: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:libdc1394-22
Version: 2.2.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:29: installing './compile'

[... snipped ...]

[][][]
[30] [31]) (./control_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--9

[32]
Underfull \hbox (badness 776) in paragraph at lines 67--69
[] \T1/phv/b/n/10 dc1394error[]_[]t  dc1394[]_[]feature[]_[]set[]_[]value \T1/p
hv/m/n/10 ( \T1/phv/b/n/10 dc1394camera[]_[]t $\OMS/cmsy/m/n/10 ^^C$\T1/phv/m/n
/10 camera,  \T1/phv/b/n/10 dc1394feature[]_[]t \T1/phv/m/n/10 fea-ture,
[33]
Underfull \hbox (badness 5893) in paragraph at lines 117--119
[] \T1/phv/b/n/10 dc1394error[]_[]t  dc1394[]_[]external[]_[]trigger[]_[]get[]_
[]supported[]_[]sources \T1/phv/m/n/10 ( \T1/phv/b/n/10 dc1394camera[]_[]t $\OM
S/cmsy/m/n/10 ^^C$\T1/phv/m/n/10 camera,

Underfull \hbox (badness 1) detected at line 142
[][][]
[34] [35] [36] [37] [38] [39] [40] [41] [42]) (./conversions_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--9

[43]
Underfull \hbox (badness 1) detected at line 42
[][][]
[44] [45]
! Missing } inserted.
 
}
l.123 \end{DoxyParams}
  
? 
! Emergency stop.
 
}
l.123 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:1048: doc/libdc1394.pdf] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 all doxygen-pdf returned exit code 2
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdc1394-22.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921784: gromacs: FTBFS (ld returned 1 exit status)

2019-02-08 Thread Santiago Vila
Package: src:gromacs
Version: 2019-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh_testdir
(mkdir -p build/basic; cd build/basic; cmake /<> 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_RULE_MESSAGES=OFF 
-DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed" -DGMX_EXTERNAL_ZLIB=ON -DGMX_SIMD=SSE2  -DGMX_MPI=OFF 
-DGMX_X11=ON -DBUILD_SHARED_LIBS=ON)
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info

[... snipped ...]

[ 84%] Built target testutils-mpi-test
/usr/bin/make -f src/testutils/tests/CMakeFiles/testutils-test.dir/build.make 
src/testutils/tests/CMakeFiles/testutils-test.dir/depend
make[4]: Entering directory '/<>/build/openmpi-dp'
cd /<>/build/openmpi-dp && /usr/bin/cmake -E cmake_depends "Unix 
Makefiles" /<> /<>/src/testutils/tests 
/<>/build/openmpi-dp 
/<>/build/openmpi-dp/src/testutils/tests 
/<>/build/openmpi-dp/src/testutils/tests/CMakeFiles/testutils-test.dir/DependInfo.cmake
 --color=
Scanning dependencies of target testutils-test
make[4]: Leaving directory '/<>/build/openmpi-dp'
/usr/bin/make -f src/testutils/tests/CMakeFiles/testutils-test.dir/build.make 
src/testutils/tests/CMakeFiles/testutils-test.dir/build
make[4]: Entering directory '/<>/build/openmpi-dp'
cd /<>/build/openmpi-dp/src/testutils/tests && 
/usr/bin/mpicxx.openmpi  -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H 
-DTEST_DATA_PATH=\"src/testutils/tests\" 
-DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\"
 -I/<>/build/openmpi-dp/src -I/<>/src -isystem 
/<>/src/external/googletest/googletest/include -isystem 
/<>/src/external/googletest/googlemock/include -isystem 
/<>/src/testutils/../external/tinyxml2 -isystem 
/<>/src/external/thread_mpi/include  -msse2   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11   -O3 
-DNDEBUG -funroll-all-loops -fexcess-precision=fast -o 
CMakeFiles/testutils-test.dir/interactivetest.cpp.o -c 
/<>/src/testutils/tests/interactivetest.cpp
cd /<>/build/openmpi-dp/src/testutils/tests && 
/usr/bin/mpicxx.openmpi  -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H 
-DTEST_DATA_PATH=\"src/testutils/tests\" 
-DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\"
 -I/<>/build/openmpi-dp/src -I/<>/src -isystem 
/<>/src/external/googletest/googletest/include -isystem 
/<>/src/external/googletest/googlemock/include -isystem 
/<>/src/testutils/../external/tinyxml2 -isystem 
/<>/src/external/thread_mpi/include  -msse2   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11   -O3 
-DNDEBUG -funroll-all-loops -fexcess-precision=fast -o 
CMakeFiles/testutils-test.dir/refdata_tests.cpp.o -c 
/<>/src/testutils/tests/refdata_tests.cpp
cd /<>/build/openmpi-dp/src/testutils/tests && 
/usr/bin/mpicxx.openmpi  -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H 
-DTEST_DATA_PATH=\"src/testutils/tests\" 
-DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\"
 -I/<>/build/openmpi-dp/src -I/<>/src -isystem 
/<>/src/external/googletest/googletest/include -isystem 
/<>/src/external/googletest/googlemock/include -isystem 
/<>/src/testutils/../external/tinyxml2 -isystem 
/<>/src/external/thread_mpi/include  -msse2   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11   -O3 
-DNDEBUG -funroll-all-loops -fexcess-precision=fast -o 
CMakeFiles/testutils-test.dir/testasserts_tests.cpp.o -c 
/<>/src/testutils/tests/testasserts_tests.cpp
cd /<>/build/openmpi-dp/src/testutils/tests && 
/usr/bin/mpicxx.openmpi  -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H 
-DTEST_DATA_PATH=\"src/testutils/tests\" 
-DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\"
 -I/<>/build/openmpi-dp/src -I/<>/src -isystem 
/<>/src/external/googletest/googletest/include -isystem 
/<>/src/external/googletest/googlemock/include -isystem 
/<>/src/testutils/../external/tinyxml2 -isystem 
/<>/src/external/thread_mpi/include  -msse2   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11   -O3 
-DNDEBUG -funroll-all-loops -fexcess-precision=fast -o 
CMakeFiles/testutils-test.dir/x

Bug#921787: kombu: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:kombu
Version: 4.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_kombu/build/kombu

[... snipped ...]

t/unit/utils/test_div.py ..  [ 91%]
t/unit/utils/test_encoding.py    [ 92%]
t/unit/utils/test_functional.py ..   [ 95%]
t/unit/utils/test_imports.py .   [ 95%]
t/unit/utils/test_json.py ...[ 96%]
t/unit/utils/test_objects.py ..  [ 97%]
t/unit/utils/test_scheduling.py ...  [ 97%]
t/unit/utils/test_time.py    [ 98%]
t/unit/utils/test_url.py ..  [ 99%]
t/unit/utils/test_utils.py ..[ 99%]
t/unit/utils/test_uuid.py .. [100%]

=== FAILURES ===
_ test_Channel.test_basic_consume_registers_ack_status _

self = 

def test_basic_consume_registers_ack_status(self):
self.channel.wait_returns = 'my-consumer-tag'
self.channel.basic_consume('foo', no_ack=True)
>   assert 'my-consumer-tag' in self.channel.no_ack_consumers
E   AssertionError: assert 'my-consumer-tag' in set(['m'])
E+  where set(['m']) = .no_ack_consumers
E+where  = .channel

t/unit/transport/test_pyamqp.py:73: AssertionError
=== warnings summary ===
t/unit/test_serialization.py::test_Serialization::()::test_msgpack_loads
  /<>/kombu/serialization.py:373: PendingDeprecationWarning: 
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')

t/unit/test_serialization.py::test_Serialization::()::test_msgpack_dumps
  /<>/kombu/serialization.py:373: PendingDeprecationWarning: 
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')
  /<>/kombu/serialization.py:373: PendingDeprecationWarning: 
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=== 1 failed, 1005 passed, 130 skipped, 3 warnings in 22.79 seconds 
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: python2.7 
setup.py test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--system=custom "--test-args={interpreter} setup.py test" returned exit code 13
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921797: node-lru-cache: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-lru-cache
Version: 5.1.1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tap -R spec test/*.js

test/basic.js
  basic

✓ should be equal

✓ should be equal

[... snipped ...]


✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

  dumpLru

✓ type is Yallist


  650 passing (14s)
  1 failing

  1) test/foreach.js expires should be equal:

  Error: should be equal
  + expected - actual

  -3
  +5
  
  at Timeout._onTimeout (test/foreach.js:125:7)

make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-lru-cache.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921796: node-libnpx: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-libnpx
Version: 10.2.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tail -n +2 README.md | marked-man --manual 'User Commands' --version 
libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir node_modules
ln -s /usr/lib/nodejs/npm node_modules
ln -s .. node_modules/libnpx

[... snipped ...]

1..10
ok 15 - treats directory-type commands specially # time=39.876ms

# Subtest: -n and --node-arg special parsing rules
ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - should match pattern provided
ok 4 - should match pattern provided
ok 5 - should match pattern provided
ok 6 - should match pattern provided
ok 7 - should match pattern provided
ok 8 - should match pattern provided
ok 9 - should match pattern provided
ok 10 - should match pattern provided
1..10
ok 16 - -n and --node-arg special parsing rules # time=75.918ms

1..16
# time=708.137ms
ok 5 - test/parse-args.js # time=2287.591ms

# Subtest: test/util.js
# Subtest: promisify with existing util.promisify
ok 1 - used existing promisify fn
1..1
ok 1 - promisify with existing util.promisify # time=33.67ms

# Subtest: promisify without existing util.promisify
ok 1 - got a thenable
ok 2 - value passed through successfully
ok 3 - got the error!
1..3
ok 2 - promisify without existing util.promisify # time=22.968ms

1..2
# time=109.629ms
ok 6 - test/util.js # time=1657.342ms

1..6
# failed 1 of 6 tests
# time=49363.288ms
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-libnpx.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921805: rt-extension-nagios: FTBFS (you may need to install the Capture::Tiny module)

2019-02-08 Thread Santiago Vila
Package: src:rt-extension-nagios
Version: 1.01-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Cannot determine perl version info from lib/RT/Extension/Nagios.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-nagios.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921795: node-flagged-respawn: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-flagged-respawn
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec


  flaggedRespawn
isV8flags
  ✓ should return true when flag is in v8flags
  ✓ should ignore separator differences of "-" and "_"
  ✓ should return false when flag is not in v8flags

[... snipped ...]

 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  7) flaggedRespawn
   force and forbid respawning
 always forbid respawning with inner --no-respawning:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  8) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (array):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  9) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (string):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  10) flaggedRespawn
   force and forbid respawning
 should take priority to forbidding than forcing:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  11) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  12) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when not respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 12
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-flagged-respawn.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921801: packaging-tutorial: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:packaging-tutorial
Version: 0.21
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep 
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# version check
if [ 0.21 != 0.21 ]; then echo "Wrong version in .tex: 0.21 != 0.21"; exit 1; fi
#translate source files before building pdf
po4a po4a/po4a.cfg --verbose --keep 50
Updating po4a/po//packaging-tutorial.pot:
 (628 entries)
Updating po4a/po//de.po: 
... done.

[... snipped ...]

debiantutorial.zh_TW.sty is 100% translated (1 strings).
dh_auto_build
make -j1
make[2]: Entering directory '/<>'
make LU_REC_MASTER="packaging-tutorial.de" LU_REC_FLAVOR="PDF" 
LU_REC_TARGET="packaging-tutorial.de.pdf" LU_WATCH_FILES_SAVE
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'LU_WATCH_FILES_SAVE'.
make[3]: Leaving directory '/<>'
 ==> building  packaging-tutorial.de.pdf <==
Running: 'pdflatex' '--interaction' 'errorstopmode' '--jobname' 
'packaging-tutorial.de' 
'\RequirePackage[extension=.pdf]{texdepends}\input{packaging-tutorial.de.tex}'
LaTeX Warning: You have requested package 
`beamerthemedebian',*
Building packaging-tutorial.de.pdf fails
*
Here are the last lines of the log file
If this is not enought, try to
call 'make' with 'VERB=verbose' option
*
==> Last lines in packaging-tutorial.de.log <==
\beamer@dima=\dimen185
\beamer@dimb=\dimen186
)
(/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerouterthemedefault.sty)))
(./beamerthemedebian.sty

LaTeX Warning: You have requested package `beamerthemedebian',
   but the package provides `$'.

Package: $ 2019/01/05 v3.1 (3.1)

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.1 \ProvidesPackageRCS $H
  eader: /cvsroot/latex-beamer/latex-beamer/themes/t...

make[2]: *** [LaTeX.mk:823: packaging-tutorial.de.pdf] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/packaging-tutorial.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921775: avr-libc: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:avr-libc
Version: 1:2.0.0+Atmel3.6.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -f debian/rules
cd libc/avr-libc && ./bootstrap
+ rm -rf avr/lib
+ ./devtools/gen-avr-lib-tree.sh
Generating source directories:
  avr/lib/avr2/
  avr/lib/avr2/at90s1200
  avr/lib/avr2/attiny11
  avr/lib/avr2/attiny12
  avr/lib/avr2/attiny15
  avr/lib/avr2/attiny28
  avr/lib/avr2/at90s4414
  avr/lib/avr2/at90s4434

[... snipped ...]

pnmtopng: 12 colors found
Fixing transparency for open.png
pnmtopng: 2 colors found
Fixing transparency for releases.png
pnmtopng: 2 colors found
Fixing transparency for splitbar.png
pnmtopng: 7 colors found
Fixing transparency for sync_off.png
pnmtopng: 54 colors found
Fixing transparency for sync_on.png
pnmtopng: 57 colors found
Fixing transparency for tab_a.png
pnmtopng: 27 colors found
Fixing transparency for tab_b.png
pnmtopng: 30 colors found
Fixing transparency for tab_h.png
pnmtopng: 32 colors found
Fixing transparency for tab_s.png
pnmtopng: 35 colors found
echo timestamp > fix_png
cd latex_src && make refman.pdf
make[5]: Entering directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>

make[5]: *** [Makefile:6: refman.pdf] Error 1
make[5]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src'
make[4]: [Makefile:653: avr-libc-user-manual.pdf] Error 2 (ignored)
cp latex_src/refman.pdf avr-libc-user-manual.pdf
cp: cannot stat 'latex_src/refman.pdf': No such file or directory
make[4]: *** [Makefile:654: avr-libc-user-manual.pdf] Error 1
make[4]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api'
make[3]: *** [Makefile:380: all-recursive] Error 1
make[3]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc'
make[2]: *** [Makefile:435: all-recursive] Error 1
make[2]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc'
make[1]: *** [Makefile:374: all] Error 2
make[1]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc'
make: *** [debian/rules:14: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avr-libc.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921786: kim-api: FTBFS (F90-F-0000-Internal compiler error. process_formal_arguments: Function argument with mismatched size that is neither integer nor floating-point)

2019-02-08 Thread Santiago Vila
Package: src:kim-api
Version: 2.0~beta2.gita734d1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p /<>/debian/home
dh_auto_configure -- -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DKIM_API_BUILD_MODELS_AND_DRIVERS=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- The Fortran compiler identification is Flang 99.99.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works

[... snipped ...]

/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_length_unit_f.f90.o.provides.build
[ 24%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_log_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_f_module.mod 
CMakeFiles/kim-api.dir/kim_log_f_module.mod.stamp Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o.provides.build
[ 25%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_log_verbosity_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod 
Fortran_MODULES/kim_log_verbosity_f_module.mod 
CMakeFiles/kim-api.dir/kim_log_verbosity_f_module.mod.stamp Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o.provides.build
[ 25%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_model_compute_arguments_create_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod 
Fortran_MODULES/kim_model_compute_arguments_create_f_module.mod 
CMakeFiles/kim-api.dir/kim_model_compute_arguments_create_f_module.mod.stamp 
Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o.provides.build
[ 26%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_model_compute_arguments_destroy_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod 
Fortran_MODULES/kim_model_compute_arguments_destroy_f_module.mod 
CMakeFiles/kim-api.dir/kim_model_compute_arguments_destroy_f_module.mod.stamp 
Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o.provide

Bug#921778: deap: FTBFS (Could not import extension sphinx.ext.pngmath)

2019-02-08 Thread Santiago Vila
Package: src:deap
Version: 1.0.2.post2-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
warning: pypandoc module not found, could not convert Markdown to RST
running config
I: pybuild base:217: python3.7 setup.py config 
warning: pypandoc module not found, could not convert Markdown to RST
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
warning: pypandoc module not found, could not convert Markdown to RST

[... snipped ...]

copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/gp.cpython-37.pyc
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/__init__.cpython-37.pyc
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/base.cpython-37.pyc
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/creator.cpython-37.pyc
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__
creating 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/__init__.py 
-> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/movingpeaks.py
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/binary.py -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/tools.py -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/gp.py 
-> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks
creating 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__pycache__
copying 
/<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/__pycache__/__init__.cpython-37.pyc
 -> 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__pycache__
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__init__.py
 to __init__.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/emo.py
 to emo.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/migration.py
 to migration.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/__init__.py
 to __init__.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/mutation.py
 to mutation.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/selection.py
 to selection.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/crossover.py
 to crossover.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/init.py
 to init.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/support.py
 to support.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/base.py
 to base.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/__init__.py
 to __init__.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/test_logbook.py
 to test_logbook.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/test_pickle.py
 to test_pickle.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/algorithms.py
 to algorithms.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/cma.py
 to cma.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/creator.py
 to creator.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/gp.py 
to gp.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__init__.py
 to __init__.cpython-37.pyc
byte-compiling 
/<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/movingpeaks.py
 to movingpeaks.cpython-37.pyc
byte-compiling 
/<>/deb

Bug#921785: gtk-sharp3: FTBFS ('MONO_PROFILE_ENTER_LEAVE' undeclared)

2019-02-08 Thread Santiago Vila
Package: src:gtk-sharp3
Version: 2.99.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with cli
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--libdir=/usr/lib \
--enable-debug \
CSC=/usr/bin/mono-csc
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --libdir=/usr/lib --enable-debug 
CSC=/usr/bin/mono-csc
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no

[... snipped ...]

libtool: link: ( cd ".libs" && rm -f "libgtksharpglue-3.la" && ln -s 
"../libgtksharpglue-3.la" "libgtksharpglue-3.la" )
make[4]: Leaving directory '/<>/gtk/glue'
Making all in gui-thread-check
make[4]: Entering directory '/<>/gtk/gui-thread-check'
Making all in profiler
make[5]: Entering directory '/<>/gtk/gui-thread-check/profiler'
/bin/bash ../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../..  -D_REENTRANT -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/lib/pkgconfig/../../include/mono-2.0 -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall -Wunused 
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes  
-Wmissing-prototypes -Wnested-externs  -Wshadow -Wpointer-arith -Wno-cast-qual 
-Wcast-align -Wwrite-strings -c -o gui-thread-check.lo gui-thread-check.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -D_REENTRANT 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/lib/pkgconfig/../../include/mono-2.0 -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall -Wunused 
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes 
-Wmissing-prototypes -Wnested-externs -Wshadow -Wpointer-arith -Wno-cast-qual 
-Wcast-align -Wwrite-strings -c gui-thread-check.c  -fPIC -DPIC -o 
.libs/gui-thread-check.o
gui-thread-check.c:90:1: warning: no previous prototype for 
'mono_profiler_startup' [-Wmissing-prototypes]
 mono_profiler_startup (const char *desc)
 ^
gui-thread-check.c: In function 'mono_profiler_startup':
gui-thread-check.c:94:2: warning: implicit declaration of function 
'mono_profiler_install'; did you mean 'mono_profiler_startup'? 
[-Wimplicit-function-declaration]
  mono_profiler_install (NULL, NULL);
  ^
  mono_profiler_startup
gui-thread-check.c:94:2: warning: nested extern declaration of 
'mono_profiler_install' [-Wnested-externs]
gui-thread-check.c:95:2: warning: implicit declaration of function 
'mono_profiler_install_enter_leave'; did you mean 
'mono_profiler_enable_coverage'? [-Wimplicit-function-declaration]
  mono_profiler_install_enter_leave (simple_method_enter, NULL);
  ^
  mono_profiler_enable_coverage
gui-thread-check.c:95:2: warning: nested extern declaration of 
'mono_profiler_install_enter_leave' [-Wnested-externs]
gui-thread-check.c:96:2: warning: implicit declaration of function 
'mono_profiler_set_events'; did you mean 'mono_profiler_startup'? 
[-Wimplicit-function-declaration]
  mono_profiler_set_events (MONO_PROFILE_ENTER_LEAVE);
  ^~~~
  mono_profiler_startup
gui-thread-check.c:96:2: warning: nested extern declaration of 
'mono_profiler_set_events' [-Wnested-externs]
gui-thread-check.c:96:28: error: 'MONO_PROFILE_ENTER_LEAVE' undeclared (first 
use in this function); did you mean 'MONO_NATIVE_INTERFACE'?
  mono_profiler_set_events (MONO_PROFILE_ENTER_LEAVE);
^~~~
MONO_NATIVE_INTERFACE
gui-thread-check.c:96:28: note: each undeclared identifier is reported only 
once for each function it appears in
make[5]: *** [Makefile:454: gui-thread-check.lo] Error 1
make[5]: Leaving directory '/<>/gtk/gui-thread-check/profiler'
make[4]: *** [Makefile:377: all-recursive] Error 1
make[4]: Leaving directory '/<>/gtk/gui-thread-check'
make[3]: *** [Makefile:593: all-recursive] Error 1
make[3]: Leaving directory '/<>/gtk'
make[2]: *** [Makefile:438: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:365: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:20: build-inde

Bug#921791: litl: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:litl
Version: 0.1.9-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with autoreconf
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'

[... snipped ...]




LaTeX Warning: Reference `litl__write_8h' on page 5 undefined on input line 18.



LaTeX Warning: Reference `utils_2litl__merge_8c' on page 5 undefined on input l
ine 19.


LaTeX Warning: Reference `litl__print_8c' on page 5 undefined on input line 20.



LaTeX Warning: Reference `utils_2litl__split_8c' on page 5 undefined on input l
ine 21.

) [5] [6]
Chapter 4.
(./group__litl__merge.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
 
}
l.32 \end{DoxyParams}
 
? 
! Emergency stop.
 
}
l.32 \end{DoxyParams}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/doc/latex'
make[2]: *** [Makefile:539: latex/refman.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:444: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921776: bliss: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:bliss
Version: 0.73-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf --builddirectory=_build --parallel
   dh_update_autotools_config -i -O--builddirectory=_build -O--parallel
   dh_autoreconf -i -O--builddirectory=_build -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:19: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'

[... snipped ...]

Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 185/65536 hits=1285 misses=221
finished...
cd /<>/_build/DEBIAN/doc/html && { \
rm -f *.md5 jquery.js ; \
rdfind -outputname /dev/null -makesymlinks true . ; \
symlinks -r -c -s -v . ; \
ln -sf /usr/share/javascript/jquery/jquery.js ; \
}
Now scanning ".", found 60 files.
Now have 60 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 384954 bytes or 376 KiB
Removed 60 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0 
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making results file /dev/null
Now making symbolic links. creating 
Making 0 links.
cd /<>/_build/DEBIAN/doc/latex && { \
make && mv refman.pdf bliss_refman.pdf ; \
}
make[3]: Entering directory '/<>/_build/DEBIAN/doc/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>

make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:30: doc] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921790: liquidsoap: FTBFS (ld: cannot find -lexif)

2019-02-08 Thread Santiago Vila
Package: src:liquidsoap
Version: 1.3.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with elpa,ocaml
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
./bootstrap
make[1]: Leaving directory '/<>'
   dh_ocamlinit -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- 
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking 
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c

[... snipped ...]

OCAMLOPT -c decoder/image/ppm_decoder.ml
OCAMLOPT -c decoder/external_decoder.ml
OCAMLOPT -c decoder/raw_audio_decoder.ml
OCAMLOPT -c decoder/flac_decoder.ml
OCAMLOPT -c decoder/aac_decoder.ml
OCAMLOPT -c decoder/ogg_decoder.ml
OCAMLOPT -c decoder/mad_decoder.ml
OCAMLOPT -c decoder/vorbisduration.ml
OCAMLOPT -c decoder/flacduration.ml
OCAMLOPT -c decoder/ogg_flac_duration.ml
OCAMLOPT -c decoder/taglib_plug.ml
OCAMLOPT -c decoder/image/camlimages_decoder.ml
OCAMLOPT -c decoder/image/sdlimage_decoder.ml
OCAMLOPT -c decoder/gstreamer_decoder.ml
OCAMLOPT -c shebang.ml
OCAMLOPT -c lang/lang_builtins.ml
OCAMLOPT -c lang/builtins_json.ml
OCAMLOPT -c lang/builtins_harbor.ml
OCAMLOPT -c lang/builtins_dtools.ml
OCAMLOPT -c lang/builtins_time.ml
OCAMLOPT -c lang/builtins_callbacks.ml
OCAMLOPT -c lang/builtins_lo.mli
OCAMLOPT -c lang/builtins_lo.ml
OCAMLOPT -c lang/builtins_magic.ml
OCAMLOPT -c lang/builtins_cry.ml
OCAMLOPT -c lang/builtins_lastfm.ml
OCAMLOPT -c main.ml
OCAMLOPT -c runner.ml
CC -c tools/unix_c.c
CC -c io/oss_io_c.c
OCAMLOPT -o liquidsoap
/usr/bin/ld: cannot find -lexif
collect2: error: ld returned 1 exit status
File "caml_startup", line 1:
Error: Error during linking
make[4]: *** [../Makefile.rules:110: liquidsoap] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [../Makefile.rules:67: all-auto-ocaml-prog] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile.rules:27: all-subdirs] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921777: bugwarrior: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:bugwarrior
Version: 1.6.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml bugwarrior/docs/ 
bugwarrior/docs/_build/html # HTML generator
Running Sphinx v1.7.9
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/objects.inv...

[... snipped ...]

Traceback (most recent call last):
  File "/<>/tests/test_db.py", line 78, in test_synchronize
db.synchronize(iter((issue,)), config, 'general')
  File "/<>/bugwarrior/db.py", line 289, in synchronize
key_list = build_key_list(services)
  File "/<>/bugwarrior/db.py", line 459, in build_key_list
keys[target] = get_service(target).ISSUE_CLASS.UNIQUE_KEY
  File "/<>/bugwarrior/services/__init__.py", line 41, in 
get_service
return epoint.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345, 
in load
self.require(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368, 
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in 
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages), 
Requirement.parse('future!=0.16.0'))

==
ERROR: test_udas (tests.test_db.TestUDAs)
--
Traceback (most recent call last):
  File "/<>/tests/test_db.py", line 146, in test_udas
udas = sorted(list(db.get_defined_udas_as_strings(config, 'general')))
  File "/<>/bugwarrior/db.py", line 466, in 
get_defined_udas_as_strings
uda_list = build_uda_config_overrides(services)
  File "/<>/bugwarrior/db.py", line 507, in 
build_uda_config_overrides
targets_udas.update(get_service(target).ISSUE_CLASS.UDAS)
  File "/<>/bugwarrior/services/__init__.py", line 41, in 
get_service
return epoint.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345, 
in load
self.require(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368, 
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in 
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages), 
Requirement.parse('future!=0.16.0'))

--
Ran 117 tests in 0.666s

FAILED (SKIP=4, errors=2)
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921774: ask: FTBFS (LaTeX error)

2019-02-08 Thread Santiago Vila
Package: src:ask
Version: 1.1.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
make -C doc/
make[2]: Entering directory '/<>/doc'
pdflatex -shell-escape ask-manual.tex 
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 \write18 enabled.
entering extended mode
(./ask-manual.tex
LaTeX2e <2018-12-01>

[... snipped ...]

(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.sty
(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.tex))
(/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)
(/usr/share/texlive/texmf-dist/tex/latex/float/float.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))system 
returned with code 256


! Package minted Error: You must have `pygmentize' installed to use this packag
e.

See the minted package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.17 \begin{document}
 
? 
! Emergency stop.
 ...  
  
l.17 \begin{document}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on ask-manual.log.
make[2]: *** [Makefile:22: ask-manual-1.1.1.pdf] Error 1
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:18: doc] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921772: Bug #921772 in jabref marked as pending

2019-02-08 Thread gregor herrmann
Control: tag -1 pending

Hello,

Bug #921772 in jabref reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/jabref/commit/3252637a5d4ca4f93591ce9ac8d5a0d8458930e6


Add patch from upstream commit to fix CVE-2018-1000652: XML External Entity 
attack.

Closes: #921772
Thanks: Moritz Muehlenhoff for the bug report.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/921772



Bug#921772: CVE-2018-1000652

2019-02-08 Thread gregor herrmann
On Fri, 08 Feb 2019 23:37:20 +0100, Moritz Muehlenhoff wrote:

> This was assigned CVE-2018-1000652:
> https://github.com/JabRef/jabref/issues/4229
> https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e

Thanks Moritz.

I've added a slightly adjusted and trimmed-down version of the of
upstream commit to git.

Which fails to build with

/build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:16:
 error: package org.slf4j does not exist
import org.slf4j.Logger;
^
/build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:17:
 error: package org.slf4j does not exist
import org.slf4j.LoggerFactory;
^
/build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:29:
 error: cannot find symbol
private static final Logger LOGGER = 
LoggerFactory.getLogger(MsBibImporter.class);
 ^
  symbol:   class Logger
  location: class MsBibImporter


Seems like we either need a new build dependency, or remove the
logging part, or rewrite it … I'd be grateful for help from Java
experts :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Eagles


signature.asc
Description: Digital Signature


Bug#921768: marked as done (gtg-trace: FTBFS (mv: cannot stat './latex/refman.pdf': No such file or directory))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 23:50:30 +
with message-id 
and subject line Bug#921768: fixed in gtg-trace 0.2-2+dfsg-5
has caused the Debian Bug report #921768,
regarding gtg-trace: FTBFS (mv: cannot stat './latex/refman.pdf': 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.)


-- 
921768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtg-trace
Version: 0.2-2+dfsg-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch  --with autotools-dev,autoreconf
dh: The autotools-dev sequence is deprecated and replaced by dh in debhelper 
(>= 9.20160115)
dh: This feature will be removed in compat 12.
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'
src/Makefile.am: installing './depcomp'

[... snipped ...]


LaTeX Warning: Reference `GTGPaje_8h' on page 7 undefined on input line 12.


LaTeX Warning: Reference `GTGPaje__Basic_8h' on page 7 undefined on input line 
13.


LaTeX Warning: Reference `GTGReplay_8h' on page 7 undefined on input line 14.


LaTeX Warning: Reference `GTGStack_8h' on page 7 undefined on input line 15.


LaTeX Warning: Reference `GTGTypes_8h' on page 7 undefined on input line 16.

) [7] [8]
Chapter 5.
(./group__traceType.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
 
}
l.56 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.56 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
/<>/gtg-trace-0.2-2+dfsg/doc
mv: cannot stat './latex/refman.pdf': No such file or directory
make[3]: *** [Makefile:592: gtg_refmanual.pdf] Error 1
make[3]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[2]: *** [Makefile:476: install-am] Error 2
make[2]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[1]: *** [Makefile:447: install-recursive] Error 1
make[1]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg'
dh_auto_install: make -j1 install 
DESTDIR=/<>/gtg-trace-0.2-2\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no 
returned exit code 2
make: *** [debian/rules:4: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gtg-trace.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: gtg-trace
Source-Version: 0.2-2+dfsg-5

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated gtg-trace 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: Sat, 09 Feb 2019 00:30:44 +0100
Source: gtg-trace
Binary: libgtg-dev libgtg0 libgtg0-dbgsym
Architecture: source
Version: 0.2-2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libgtg-dev - Gener

Processed: found 909387 in 1:19.2.1+dfsg-1

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 909387 1:19.2.1+dfsg-1
Bug #909387 {Done: Sergei Golovan } [erlang-mode] 
erlang-mode: fails to install with xemacs21
Marked as found in versions erlang/1:19.2.1+dfsg-1.
> thanks
Stopping processing here.

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



Bug#921661: marked as done (openstack-dashboard: fails to upgrade from 'testing': No such file or directory: '/usr/lib/python3/dist-packages/openstack_dashboard/themes/default')

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 23:19:31 +
with message-id 
and subject line Bug#921661: fixed in horizon 3:14.0.2-2
has caused the Debian Bug report #921661,
regarding openstack-dashboard: fails to upgrade from 'testing': No such file or 
directory: '/usr/lib/python3/dist-packages/openstack_dashboard/themes/default'
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.

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

  Setting up openstack-dashboard (3:14.0.2-1) ...
  FutureWarning: Possible nested set at position 329Traceback (most recent call 
last):
File "/usr/share/openstack-dashboard/manage.py", line 23, in 
  execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
  utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 356, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
283, in run_from_argv
  self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
330, in execute
  output = self.handle(*args, **options)
File 
"/usr/lib/python3/dist-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 199, in handle
  collected = self.collect()
File 
"/usr/lib/python3/dist-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 115, in collect
  for path, storage in finder.list(self.ignore_patterns):
File 
"/usr/lib/python3/dist-packages/django/contrib/staticfiles/finders.py", line 
112, in list
  for path in utils.get_files(storage, ignore_patterns):
File "/usr/lib/python3/dist-packages/django/contrib/staticfiles/utils.py", 
line 28, in get_files
  directories, files = storage.listdir(location)
File "/usr/lib/python3/dist-packages/django/core/files/storage.py", line 
397, in listdir
  for entry in os.listdir(path):
  FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/lib/python3/dist-packages/openstack_dashboard/themes/default'
  dpkg: error processing package openstack-dashboard (--configure):
   installed openstack-dashboard package post-installation script subprocess 
returned error exit status 1


cheers,

Andreas


openstack-dashboard_3:14.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 3:14.0.2-2

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

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

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

Debian distribution maintenance software
pp.
Michal Arbet  (supplier of updated horizon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 13:36:59 +0100
Source: horizon
Binary: horizon-doc openstack-dashboard openstack-dashboard-apache 
python3-django-horizon
Architecture: source all
Version: 3:14.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Michal Arbet 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack cloud
 openstack-dashboard-apache - web application to control an OpenStack cloud - 
Apache support
 python3-django-horizon - Django module providing web interaction with OpenStack
Closes: 921661
Changes:
 horizon (3:14.0.2-2) unstable; urgency=medium
 .
   [ Michal Arbet ]
   * d/openstack-dashboard.postinst:
   - Make symlinks creation dynamically (Closes: #921661).
   * d/control:
   - openstack-dashboard-apache: Update dependenc

Bug#921756: closed by Alf Gaida (Re: libfm-qt: FTBFS (dh_auto_configure fails))

2019-02-08 Thread Alf Gaida
To be more verbose - libfm-qt don't depend on libfm anymore (no part of
LXQt does directly anymore) - so we removed the cmake find for from the
build tools. Even if we would find libfm-dev it wouldn't build anymore
because of some now deprecated things we don't allow anymore in the
code. So waiting is the only chance.

Alf



Bug#867671: closed by Stephen Kitt (Bug#867671: fixed in libratbag 0.9.904-3)

2019-02-08 Thread Andreas Beckmann
On 2019-02-08 21:27, Stephen Kitt wrote:
> It was staring me in the face: you tested with 0.9.904-2 and marked the bug

Damned race conditions ...
I didn't realize that there were two uploads in a short timeframe. I
first saw your closing message, then I found the bug showing up again in
my latest test run (but your -3 upload hadn't reached my mirror, yet,
even at the time I reopened the bug), so it was only -2 getting tested

Running tests again, but the package itself looks good now in -3 :-)

> as found in 0.9.904-3 (which is where the bug was fixed).

copy+paste from the subject, since that obviously must have been the
failing version :-(

> There’s a few hours I won’t be getting back :-(.

Sorry for that.


Andreas



Bug#921772: CVE-2018-1000652

2019-02-08 Thread Moritz Muehlenhoff
Package: jabref
Severity: grave
Tags: security

This was assigned CVE-2018-1000652:
https://github.com/JabRef/jabref/issues/4229
https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e

Cheers,
Moritz
  



Processed: Re: Bug#921756 closed by Alf Gaida (Re: libfm-qt: FTBFS (dh_auto_configure fails))

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 921756 0.14.0-3
Bug #921756 {Done: Alf Gaida } [src:libfm-qt] libfm-qt: 
FTBFS (dh_auto_configure fails)
Marked as fixed in versions libfm-qt/0.14.0-3.
> thanks
Stopping processing here.

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



Bug#921756: closed by Alf Gaida (Re: libfm-qt: FTBFS (dh_auto_configure fails))

2019-02-08 Thread Santiago Vila
fixed 921756 0.14.0-3
thanks

> thanks for filing this - i suggest to do nothing, just wait a bit, btw.
> this would be the relevant lines of the build log:

Oh, I see. Forgot to check the package in unstable, sorry.

Nevertheless, I'm going to mark this as "fixed" in the unstable
version. That way, anybody doing QA rebuilds of buster (not that
there is a lot of people doing that, but who knows) will see that the
problem is already solved.

Thanks a lot.



Bug#921301: marked as done (starpu: FTBFS while building documentation)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 22:25:31 +
with message-id 
and subject line Bug#921301: fixed in starpu-contrib 1.2.6+dfsg-6
has caused the Debian Bug report #921301,
regarding starpu: FTBFS while building documentation
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.)


-- 
921301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starpu
Severity: serious

Dear Maintainer,

I tested your package against a draft package for doxygen 1.8.15:
https://bugs.debian.org/919413

and it FTBFS with this error:
mv: cannot stat 'latex/refman.pdf': No such file or directory

Paolo

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: starpu-contrib
Source-Version: 1.2.6+dfsg-6

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated starpu-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: Tue, 05 Feb 2019 19:57:23 +0200
Source: starpu-contrib
Binary: libsocl-contrib-1.2-0 libsocl-contrib-1.2-0-dbgsym 
libstarpu-contrib-1.2-5 libstarpu-contrib-1.2-5-dbgsym libstarpu-contrib-dev 
libstarpu-contribfft-1.2-0 libstarpu-contribfft-1.2-0-dbgsym 
libstarpu-contribmpi-1.2-3 libstarpu-contribmpi-1.2-3-dbgsym 
starpu-contrib-examples starpu-contrib-examples-dbgsym starpu-contrib-tools 
starpu-contrib-tools-dbgsym
Architecture: source amd64
Version: 1.2.6+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libsocl-contrib-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-1.2-5 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-dev - Task scheduler for heterogeneous multicore machines - 
dev
 libstarpu-contribfft-1.2-0 - Task scheduler for heterogeneous multicore 
machines
 libstarpu-contribmpi-1.2-3 - Task scheduler for heterogeneous multicore 
machines
 starpu-contrib-examples - Task scheduler for heterogeneous multicore machines 
- exs
 starpu-contrib-tools - Task scheduler for heterogeneous multicore machines - 
tools
Closes: 921301 921766
Changes:
 starpu-contrib (1.2.6+dfsg-6) unstable; urgency=medium
 .
   * patches/doc-nopdf: Disable building pdf version of doxygen documentation
 (Closes: Bug#921301, Bug#921766).
   * rules: Fix docdir.
Checksums-Sha1:
 1f44700a618f3ad2768911b11963f5dc59bdd4f8 3174 starpu-contrib_1.2.6+dfsg-6.dsc
 2128e2c0ed847352c0a3a3c8e963f59a10a71d0d 13656 
starpu-contrib_1.2.6+dfsg-6.debian.tar.xz
 66b0999c085ad1403d2ae663f3674bcd1c55d90d 243448 
libsocl-contrib-1.2-0-dbgsym_1.2.6+dfsg-6_amd64.deb
 e9a322c7a05a3458523f6b53b1311f3185172990 47020 
libsocl-contrib-1.2-0_1.2.6+dfsg-6_amd64.deb
 bc18bd5e6cae47e1c9a6b92bab63a41b096e5106 2428116 
libstarpu-contrib-1.2-5-dbgsym_1.2.6+dfsg-6_amd64.deb
 2cd08b6accbe6444002041f73d98af2f582048c7 387604 
libstarpu-contrib-1.2-5_1.2.6+dfsg-6_amd64.deb
 cbac7bc01a6e02c3b053824b9efc9e8db8fd3864 1431976 
libstarpu-contrib-dev_1.2.6+dfsg-6_amd64.deb
 97ad4b0ee8920c7caee9bb1208ecd097314eb15d 99664 
libstarpu-contribfft-1.2-0-dbgsym_1.2.6+dfsg-6_amd64.deb
 9b32b06db4a9864d84f9fe07d874507bc78e1dc9 39100 
libstarpu-contribfft-1.2-0_1.2.6+dfsg-6_amd64.deb
 7a45b5698fe1b0030603ced95536c5870a5d77dd 323884 
libstarpu-contribmpi-1.2-3-dbgsym_1.2.6+dfsg-6_amd64.deb
 9cef27fb61d6b1a96aa54b2696b57bb060c976d7 75304 
libstarpu-contribmpi-1.2-3_1.2.6+dfsg-6_amd64.deb
 4f94449b2c9c7eb92450227cdb4ca769b7973d8b 5219032 
starp

Bug#921766: marked as done (starpu-contrib: FTBFS (mv: cannot stat 'latex/refman.pdf': No such file or directory))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 22:25:31 +
with message-id 
and subject line Bug#921766: fixed in starpu-contrib 1.2.6+dfsg-6
has caused the Debian Bug report #921766,
regarding starpu-contrib: FTBFS (mv: cannot stat 'latex/refman.pdf': 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.)


-- 
921766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:starpu-contrib
Version: 1.2.6+dfsg-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel -Bbuild --with autoreconf
   dh_testdir -a -O--parallel -O-Bbuild
   dh_update_autotools_config -a -O--parallel -O-Bbuild
   dh_autoreconf -a -O--parallel -O-Bbuild
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,

[... snipped ...]

gcc-7 -DHAVE_CONFIG_H -I. -I../../tests -I../src/common -I../include 
-I../gcc-plugin/include/starpu-gcc -I../starpu-top  -I../../include/ -I../src 
-I../../src/ -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE  -D_FORTIFY_SOURCE=1 
  -Wall  -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS   -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g  -c 
-o simple_cpu_gpu_sched.o `test -f 'sched_policies/simple_cpu_gpu_sched.c' || 
echo '../../tests/'`sched_policies/simple_cpu_gpu_sched.c
:0:0: warning: "_FORTIFY_SOURCE" redefined
:0:0: note: this is the location of the previous definition
/bin/bash ../libtool  --tag=CC   --mode=link gcc-7   -Wall  
-DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS   -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g  
-lOpenCL -lcudart -lcublas -lcudart -lstdc++-Wl,-z,relro -gdwarf-2 -g3 -g  
-o sched_policies/simple_cpu_gpu_sched simple_cpu_gpu_sched.o  
../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread  
libtool: link: gcc-7 -Wall -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g 
-Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o sched_policies/.libs/simple_cpu_gpu_sched 
simple_cpu_gpu_sched.o  -lOpenCL -lcublas -lcudart -lstdc++ 
../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread
gfortran-7  -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -c -o starpu_mod.o '../../'include/starpu_mod.f90
gfortran-7  -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -c -o init_01.o `test -f 'fortran90/init_01.f90' || 
echo '../../tests/'`fortran90/init_01.f90
/bin/bash ../libtool  --tag=FC   --mode=link gfortran-7  -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -lOpenCL -lcudart -lcublas -lcudart -lstdc++
-Wl,-z,relro -gdwarf-2 -g3 -g  -o fortran90/init_01 starpu_mod.o init_01.o  
../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread  
libtool: link: gfortran-7 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o 
fortran90/.libs/init_01 starpu_mod.o init_01.o  -lOpenCL -lcublas -lcudart 
-lstdc++ ../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread
make[4]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
make[3]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
make[2]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
Making all in doc
make[2]: Entering directory '/<>/starpu-contrib-1.2.6+dfsg/build/doc'
Making all in doxygen
make[3]: Entering dir

Processed: severity of 868466 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 868466 grave
Bug #868466 [src:php-cas] php-cas: CVE-2017-171
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Bug#921756: marked as done (libfm-qt: FTBFS (dh_auto_configure fails))

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Feb 2019 23:09:16 +0100
with message-id 
and subject line Re: libfm-qt: FTBFS (dh_auto_configure fails)
has caused the Debian Bug report #921756,
regarding libfm-qt: FTBFS (dh_auto_configure fails)
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.)


-- 
921756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libfm-qt
Version: 0.13.1-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem cmake
   dh_update_autotools_config -a -O--buildsystem=cmake
   dh_autoreconf -a -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DPULL_TRANSLATIONS=OFF \
-DUPDATE_TRANSLATIONS=OFF \
-DCMAKE_BUILD_TYPE=RelWithDebInfo
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPULL_TRANSLATIONS=OFF 
-DUPDATE_TRANSLATIONS=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc

[... snipped ...]

Feature record: CXX_FEATURE:0cxx_deleted_functions
Feature record: CXX_FEATURE:0cxx_digit_separators
Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
Feature record: CXX_FEATURE:0cxx_explicit_conversions
Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
Feature record: CXX_FEATURE:0cxx_extern_templates
Feature record: CXX_FEATURE:0cxx_final
Feature record: CXX_FEATURE:0cxx_func_identifier
Feature record: CXX_FEATURE:0cxx_generalized_initializers
Feature record: CXX_FEATURE:0cxx_generic_lambdas
Feature record: CXX_FEATURE:0cxx_inheriting_constructors
Feature record: CXX_FEATURE:0cxx_inline_namespaces
Feature record: CXX_FEATURE:0cxx_lambdas
Feature record: CXX_FEATURE:0cxx_lambda_init_captures
Feature record: CXX_FEATURE:0cxx_local_type_template_args
Feature record: CXX_FEATURE:0cxx_long_long_type
Feature record: CXX_FEATURE:0cxx_noexcept
Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
Feature record: CXX_FEATURE:0cxx_nullptr
Feature record: CXX_FEATURE:0cxx_override
Feature record: CXX_FEATURE:0cxx_range_for
Feature record: CXX_FEATURE:0cxx_raw_string_literals
Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
Feature record: CXX_FEATURE:0cxx_return_type_deduction
Feature record: CXX_FEATURE:0cxx_right_angle_brackets
Feature record: CXX_FEATURE:0cxx_rvalue_references
Feature record: CXX_FEATURE:0cxx_sizeof_member
Feature record: CXX_FEATURE:0cxx_static_assert
Feature record: CXX_FEATURE:0cxx_strong_enums
Feature record: CXX_FEATURE:1cxx_template_template_parameters
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPULL_TRANSLATIONS=OFF 
-DUPDATE_TRANSLATIONS=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo .. returned exit 
code 1
make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Bug#921768: gtg-trace: FTBFS (mv: cannot stat './latex/refman.pdf': No such file or directory)

2019-02-08 Thread Santiago Vila
Package: src:gtg-trace
Version: 0.2-2+dfsg-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch  --with autotools-dev,autoreconf
dh: The autotools-dev sequence is deprecated and replaced by dh in debhelper 
(>= 9.20160115)
dh: This feature will be removed in compat 12.
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'
src/Makefile.am: installing './depcomp'

[... snipped ...]


LaTeX Warning: Reference `GTGPaje_8h' on page 7 undefined on input line 12.


LaTeX Warning: Reference `GTGPaje__Basic_8h' on page 7 undefined on input line 
13.


LaTeX Warning: Reference `GTGReplay_8h' on page 7 undefined on input line 14.


LaTeX Warning: Reference `GTGStack_8h' on page 7 undefined on input line 15.


LaTeX Warning: Reference `GTGTypes_8h' on page 7 undefined on input line 16.

) [7] [8]
Chapter 5.
(./group__traceType.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
 
}
l.56 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.56 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
/<>/gtg-trace-0.2-2+dfsg/doc
mv: cannot stat './latex/refman.pdf': No such file or directory
make[3]: *** [Makefile:592: gtg_refmanual.pdf] Error 1
make[3]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[2]: *** [Makefile:476: install-am] Error 2
make[2]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[1]: *** [Makefile:447: install-recursive] Error 1
make[1]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg'
dh_auto_install: make -j1 install 
DESTDIR=/<>/gtg-trace-0.2-2\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no 
returned exit code 2
make: *** [debian/rules:4: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gtg-trace.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#905697: kdepimlibs: don't depend on libical

2019-02-08 Thread Sandro Knauß
Hey,

for me it looks like we won't be able to get kdepimlibs without libical 2 for 
buster.
Keep in mind, that kdepimlibs is an old grufted lib set that we also would 
like to kill. But we also have other packages depending on it like:
* basket 
* kopete (it has a QT5 version in experimental, but this is suitable as 
replacement yet).
 and other that may can be killed.

extract libical 2 out of kdepimlibs is not that simple, as the whole interface 
will leak into akonadi-calendar, calcore, calutils,...

In short I won't have the time to do the work and test it in the near future.

I added pino to this bug report, as pino successfully extracted other parts of 
old kdelibs/kdepimlibs. 

hefee

--

On Donnerstag, 17. Januar 2019 12:11:46 CET Emilio Pozuelo Monfort wrote:
> On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote:
> > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote:
> >> Source: kdepimlibs
> >> Version: 4:4.14.10-10
> >> Severity: serious
> >> Control: block 884128 with -1
> >> 
> >> Hi,
> >> 
> >> libical2 from src:libical is superseded by libical3 (src:libical3).
> >> 
> >> Please either port kdepimlibs to libical3 or try to disable the
> >> libical support, so that we can only ship src:libical3 in buster.
> > 
> > Could someone who knows kdepimlibs take a look at this? Can we disable
> > libical support in kdepimlibs for buster? This is the last blocker for
> > the libical 2 removal.
> 
> Hi Sandro,
> 
> Lisandro said you may be able to help with this. Do you know if libical
> support could be disabled in kdepimlibs, or if the newer version libical3
> could be used?
> >From [1] it seems that libical is kind of optional, though I don't know if
> >we
> can disable the bits to drop that or if those bits have rdeps. Since
> kdepimlibs is the last rdep of the old libical version, fixing this would
> allow us to drop that one from buster. Otherwise the RC bugs that it has
> will need to be fixed and we'll have to ship with two versions of the
> library.
> 
> Thanks,
> Emilio
> 
> [1]
> https://sources.debian.org/src/kdepimlibs/4:4.14.10-10/CMakeLists.txt/#L81



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


Bug#921769: moarvm: FTBFS (error: 'MP_GEN_RANDOM_MAX' undeclared)

2019-02-08 Thread Santiago Vila
Package: src:moarvm
Version: 2018.12+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/moarvm-2018.12+dfsg'
perl Configure.pl  \
--prefix=/usr \
--libdir=/usr/lib/moar \
--debug \
--has-libtommath \
--has-libuv \
--has-libatomic_ops \
--has-libffi
Welcome to MoarVM!

[... snipped ...]

 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:512:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(or , { sc = sa | sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_xor':
src/math/bigintops.c:447:42: warning: passing argument 4 of 
'two_complement_bitop' from incompatible pointer type 
[-Wincompatible-pointer-types]
 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:513:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(xor, { sc = sa ^ sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_and':
src/math/bigintops.c:447:42: warning: passing argument 4 of 
'two_complement_bitop' from incompatible pointer type 
[-Wincompatible-pointer-types]
 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:514:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(and, { sc = sa & sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_rand':
src/math/bigintops.c:1166:13: error: 'MP_GEN_RANDOM_MAX' undeclared (first use 
in this function); did you mean 'UV_ERRNO_MAX'?
 if (MP_GEN_RANDOM_MAX >= abs(smallint_max)) {
 ^
 UV_ERRNO_MAX
src/math/bigintops.c:1166:13: note: each undeclared identifier is reported only 
once for each function it appears in
src/math/bigintops.c:1167:35: warning: implicit declaration of function 
'MP_GEN_RANDOM'; did you mean 'UV_FS_O_RANDOM'? 
[-Wimplicit-function-declaration]
 mp_digit result_int = MP_GEN_RANDOM();
   ^
   UV_FS_O_RANDOM
make[2]: *** [Makefile:621: src/math/bigintops.o] Error 1
make[2]: Leaving directory '/<>/moarvm-2018.12+dfsg'
dh_auto_build: make -j1 NOISY=1 returned exit code 2
make[1]: *** [debian/rules:51: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/moarvm-2018.12+dfsg'
make: *** [debian/rules:37: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921766: starpu-contrib: FTBFS (mv: cannot stat 'latex/refman.pdf': No such file or directory)

2019-02-08 Thread Santiago Vila
Package: src:starpu-contrib
Version: 1.2.6+dfsg-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel -Bbuild --with autoreconf
   dh_testdir -a -O--parallel -O-Bbuild
   dh_update_autotools_config -a -O--parallel -O-Bbuild
   dh_autoreconf -a -O--parallel -O-Bbuild
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,

[... snipped ...]

gcc-7 -DHAVE_CONFIG_H -I. -I../../tests -I../src/common -I../include 
-I../gcc-plugin/include/starpu-gcc -I../starpu-top  -I../../include/ -I../src 
-I../../src/ -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE  -D_FORTIFY_SOURCE=1 
  -Wall  -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS   -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g  -c 
-o simple_cpu_gpu_sched.o `test -f 'sched_policies/simple_cpu_gpu_sched.c' || 
echo '../../tests/'`sched_policies/simple_cpu_gpu_sched.c
:0:0: warning: "_FORTIFY_SOURCE" redefined
:0:0: note: this is the location of the previous definition
/bin/bash ../libtool  --tag=CC   --mode=link gcc-7   -Wall  
-DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS   -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g  
-lOpenCL -lcudart -lcublas -lcudart -lstdc++-Wl,-z,relro -gdwarf-2 -g3 -g  
-o sched_policies/simple_cpu_gpu_sched simple_cpu_gpu_sched.o  
../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread  
libtool: link: gcc-7 -Wall -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl 
-DCL_USE_DEPRECATED_OPENCL_1_1_APIS -Wall -Werror=implicit 
-Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g 
-Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o sched_policies/.libs/simple_cpu_gpu_sched 
simple_cpu_gpu_sched.o  -lOpenCL -lcublas -lcudart -lstdc++ 
../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread
gfortran-7  -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -c -o starpu_mod.o '../../'include/starpu_mod.f90
gfortran-7  -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -c -o init_01.o `test -f 'fortran90/init_01.f90' || 
echo '../../tests/'`fortran90/init_01.f90
/bin/bash ../libtool  --tag=FC   --mode=link gfortran-7  -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -lOpenCL -lcudart -lcublas -lcudart -lstdc++
-Wl,-z,relro -gdwarf-2 -g3 -g  -o fortran90/init_01 starpu_mod.o init_01.o  
../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread  
libtool: link: gfortran-7 -g -O2 
-fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. 
-fstack-protector-strong -Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o 
fortran90/.libs/init_01 starpu_mod.o init_01.o  -lOpenCL -lcublas -lcudart 
-lstdc++ ../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread
make[4]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
make[3]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
make[2]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests'
Making all in doc
make[2]: Entering directory '/<>/starpu-contrib-1.2.6+dfsg/build/doc'
Making all in doxygen
make[3]: Entering directory 
'/<>/starpu-contrib-1.2.6+dfsg/build/doc/doxygen'
warning: Tag `SYMBOL_CACHE_SIZE' at line 370 of file 
`../../../doc/doxygen/doxygen.cfg' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag `XML_SCHEMA' at line 1507 of file 
`../../../doc/doxygen/doxygen.cfg' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
warning: Tag `XML_DTD' at line 1513 of file `../../../doc/doxygen/doxygen.cfg' 
has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
/<>/starpu-contrib-1.2.6+dfsg/doc/doxygen/chapters/api/codelet_and_tasks.doxy:673:
 warning: explicit link request to 'STARPU_TASK_TYPE_

Processed: severity of 868988 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 868988 grave
Bug #868988 [src:phamm] phamm: CVE-2017-0378 reflected XSS in phamm
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Bug#921767: CVE-2018-12029

2019-02-08 Thread Moritz Muehlenhoff
Source: passenger
Severity: grave
Tags: security

This was assigned CVE-2018-12029:
https://blog.phusion.nl/2018/06/12/passenger-5-3-2-various-security-fixes/
https://github.com/phusion/passenger/commit/207870f5b7f5cc240587ab0977d6046782ae1d86

Cheers,
Moritz



Bug#917584: marked as done (FTBFS: test failures on multiple arches)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 21:49:43 +
with message-id 
and subject line Bug#917584: fixed in mod-gnutls 0.9.0-1
has caused the Debian Bug report #917584,
regarding FTBFS: test failures on multiple arches
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.)


-- 
917584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mod-gnutls
Version: 0.8.4-2
Severity: serious
Tags: ftbfs

I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.

I've tried to build mod-gnutls like this, and it's provoking test
failures. Having tweaked around #917582 (installing extra build-deps),
I find similar-looking test failures building all of the following
ways:

 * amd64 on amd64
 * arm64 on arm64
 * armel on arm64

I have a full logfile of this last one - see

  
https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/mod-gnutls_0.8.4-2_armel.log

...
make[6]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/test'
PASS: test-03_cachetimeout_in_vhost.bash
PASS: test-02_cache_in_vhost.bash
PASS: test-01_serverwide_priorities.bash
PASS: test-00_basic.bash
PASS: test-06_verify_sni_a.bash
PASS: test-04_basic_nosni.bash
PASS: test-08_verify_no_sni_fallback_to_first_vhost.bash
PASS: test-09_verify_no_sni_fails_with_wrong_order.bash
PASS: test-07_verify_sni_b.bash
PASS: test-05_mismatched-priorities.bash
PASS: test-10_basic_client_verification.bash
SKIP: test-14_basic_openpgp.bash
PASS: test-11_basic_client_verification_fail.bash
FAIL: test-12_cgi_variables.bash
PASS: test-13_cgi_variables_no_client_cert.bash
FAIL: test-16_view-status.bash
PASS: test-18_client_verification_wrong_cert.bash
PASS: test-19_TLS_reverse_proxy.bash
FAIL: test-17_cgi_vars_large_cert.bash
PASS: test-15_basic_msva.bash
PASS: test-20_TLS_reverse_proxy_client_auth.bash
PASS: test-24_pkcs11_cert.bash
PASS: test-25_Disable_TLS_1.0.bash
PASS: test-26_redirect_HTTP_to_HTTPS.bash
PASS: test-27_OCSP_server.bash
SKIP: test-28_HTTP2_support.bash
PASS: test-21_TLS_reverse_proxy_wrong_cert.bash
PASS: test-22_TLS_reverse_proxy_crl_revoke.bash
PASS: test-23_TLS_reverse_proxy_mismatched_priorities.bash
...

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated mod-gnutls 
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: Fri, 08 Feb 2019 16:27:06 -0500
Source: mod-gnutls
Binary: libapache2-mod-gnutls
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 libapache2-mod-gnutls - Apache module for TLS encryption with GnuTLS
Closes: 917582 917584
Changes:
 mod-gnutls (0.9.0-1) unstable; urgency=medium
 .
   [ Fiona Klute ]
   * New upstream version
 - drops OpenPGP support (Closes: #917584)
 - background OCSP stapling
   * Drop 0001-Fix-test-16-view-status-by-changing-priority-string.patch
   * Update Standards-Version and Description fields
   * Disable building PDF documentation (Closes: #917582)
Checksums-Sha1:
 1eac3c850c4bc0266ea58adc18ec6dd6d48e2e8d 1989 mod-gnutls_0.9.0-1.dsc
 e586996e7aea1f3479bb6859b1d9c6355f0a25e6 43586

Processed: severity of 884463 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 884463 grave
Bug #884463 [src:passenger] passenger: CVE-2017-16355: arbitrary file read
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Bug#917582: marked as done (FTBFS: failure to build manual)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 21:49:43 +
with message-id 
and subject line Bug#917582: fixed in mod-gnutls 0.9.0-1
has caused the Debian Bug report #917582,
regarding FTBFS: failure to build manual
to be marked as done.

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

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


-- 
917582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mod-gnutls
Version: 0.8.4-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!

I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.

However, mod-gnutls fails to build in sid at the moment for amd64:

...
Error producing PDF.
! LaTeX Error: File `lmodern.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
! Emergency stop.
 
 
l.6 \usepackage

make[2]: *** [Makefile:610: mod_gnutls_manual.pdf] Error 43
make[2]: Leaving directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/doc'
make[1]: *** [Makefile:505: all-recursive] Error 1
make[1]: Leaving directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4'

Full log attached.


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
 dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package mod-gnutls
dpkg-buildpackage: info: source version 0.8.4-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Daniel Kahn Gillmor 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
dh clean --with apache2
   dh_auto_clean
make -j4 distclean
make[1]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4'
Making distclean in src
make[2]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/src'
test -z "mod_gnutls.la" || rm -f mod_gnutls.la
rm -rf .libs _libs
rm -f *.o
rm -f *.lo
rm -f *.tab.c
test -z "" || rm -f 
rm -f ./so_locations
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
test . = "." || test -z "" || rm -f 
rm -f ./.deps/mod_gnutls_la-gnutls_cache.Plo
rm -f ./.deps/mod_gnutls_la-gnutls_config.Plo
rm -f ./.deps/mod_gnutls_la-gnutls_hooks.Plo
rm -f ./.deps/mod_gnutls_la-gnutls_io.Plo
rm -f ./.deps/mod_gnutls_la-gnutls_ocsp.Plo
rm -f ./.deps/mod_gnutls_la-gnutls_util.Plo
rm -f ./.deps/mod_gnutls_la-mod_gnutls.Plo
rm -f Makefile
make[2]: Leaving directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/src'
Making distclean in test
make[2]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/test'
Making distclean in tests
make[3]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/test/tests'
rm -rf .libs _libs
rm -f *.lo
test -z "" || rm -f 
test . = "." || test -z "" || rm -f 
rm -f Makefile
make[3]: Leaving directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/test/tests'
make[3]: Entering directory 
'/home/steve/debian/build/mod-gnutls/mod-gnutls-0.8.4/test'
test -z "server/secret.key authority/secret.key client/secret.key 
imposter/secret.key rogueca/secret.key rogueclient/secret.key 
ocsp-responder/secret.key authority/random_seed" || rm -f server/secret.key 
authority/secret.key client/secret.key imposter/secret.key rogueca/secret.key 
rogueclient/secret.key ocsp-responder/secret.key authority/random_seed
rm -rf .libs _libs
 rm -f pgpcrc gnutls_openpgp_support gen_ocsp_index
rmdir server authority client imposter rogueca rogueclient ocsp-responder || 
true
rm -f *.o
rmdir: failed to remove 'server': No such file or directory
rmdir: failed to remove 'authority': No such file or directory
rmdir: failed to remove 'client': No such file or directory
rmdir: failed to remove 'imposter': No such file or directory
rmdir: test -z "cache/* logs/* outputs/* server/crl.pem */x509.pem 
authority.template client.template imposter.template rogueclient.template 
server.template *.uid */*.pgp */*.pgp.raw */*.

Processed: severity of 870406 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 870406 grave
Bug #870406 [mpg321] CVE-2017-11552
Bug #887057 [mpg321] CVE-2017-11552
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Processed: notfound 867671 in 0.9.904-3, fixed 867671 in 0.9.904-3

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 867671 0.9.904-3
Bug #867671 {Done: Stephen Kitt } [libratbag-tools] 
libratbag-tools: removal of libratbag-tools/sid makes files disappear from 
liblur3/testing
No longer marked as found in versions libratbag/0.9.904-3.
> fixed 867671 0.9.904-3
Bug #867671 {Done: Stephen Kitt } [libratbag-tools] 
libratbag-tools: removal of libratbag-tools/sid makes files disappear from 
liblur3/testing
Marked as fixed in versions libratbag/0.9.904-3.
> thanks
Stopping processing here.

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



Processed: severity of 884693 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 884693 grave
Bug #884693 [src:ruby-net-ldap] ruby-net-ldap: CVE-2017-17718: missing 
certificate validation
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Processed: severity of 910757 is grave

2019-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 910757 grave
Bug #910757 [gnulib] gnulib: CVE-2018-17942 heap-based buffer overflow
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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



Bug#921745: marked as done (src:datalad: Build-depends/Recommends uninstallable packages)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 8 Feb 2019 16:20:37 -0500
with message-id <20190208212037.gu3...@hopa.kiewit.dartmouth.edu>
and subject line Re: Bug#921745: src:datalad: Build-depends/Recommends 
uninstallable packages
has caused the Debian Bug report #921745,
regarding src:datalad: Build-depends/Recommends uninstallable packages
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.)


-- 
921745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:datalad
Version: 0.11.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

This package both build-depends and recommends python-libxmp/python3-libxmp,
They are not installable and do not appear to be reasonable fixable to work
with libexempi8 (thus removal has been requested).

They either need to be fixed or datalad needs to drop using them.

>From a current sid chroot:

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

The following packages have unmet dependencies:
 python-libxmp : Depends: libexempi3 but it is not installable
E: Unable to correct problems, you have held broken packages.

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

The following packages have unmet dependencies:
 python3-libxmp : Depends: libexempi3 but it is not installable
E: Unable to correct problems, you have held broken packages.

Scott K
--- End Message ---
--- Begin Message ---
Version: 0.11.1-2

Thanks Scott

I've just uploaded -2 which removes *libxmp from Build-Depends.  Remains
present only in Recommends for now

Cheers,

On Fri, 08 Feb 2019, Scott Kitterman wrote:

> Package: src:datalad
> Version: 0.11.1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)

> This package both build-depends and recommends python-libxmp/python3-libxmp,
> They are not installable and do not appear to be reasonable fixable to work
> with libexempi8 (thus removal has been requested).

> They either need to be fixed or datalad needs to drop using them.

> >From a current sid chroot:

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

> The following packages have unmet dependencies:
>  python-libxmp : Depends: libexempi3 but it is not installable
> E: Unable to correct problems, you have held broken packages.

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

> The following packages have unmet dependencies:
>  python3-libxmp : Depends: libexempi3 but it is not installable
> E: Unable to correct problems, you have held broken packages.

> Scott K


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik--- End Message ---


Bug#918437: marked as done (ring-clojure: FTBFS randomly due to filesystem ordering)

2019-02-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Feb 2019 21:22:11 +
with message-id 
and subject line Bug#918437: fixed in ring-clojure 1.6.2-2
has caused the Debian Bug report #918437,
regarding ring-clojure: FTBFS randomly due to filesystem ordering
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.)


-- 
918437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ring-clojure
Version: 1.6.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper --with maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
jar cf ring-core.jar -C ring-core/src .
jar cf ring-servlet.jar -C ring-servlet/src .
jar cf ring-jetty-adapter.jar -C ring-jetty-adapter/src .
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
find ring-core/test -name '*.clj' | \
xargs --verbose clojure -cp 
ring-core.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/ring-codec.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-fileupload.jar:/usr/share/java/clj-time.jar:/usr/share/java/crypto-random.jar:/usr/share/java/crypto-equality.jar
clojure -cp 
ring-core.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/ring-codec.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-fileupload.jar:/usr/share/java/clj-time.jar:/usr/share/java/crypto-random.jar:/usr/share/java/crypto-equality.jar
 ring-core/test/ring/middleware/multipart_params/test/request_context.clj 
ring-core/test/ring/middleware/multipart_params/test/temp_file.clj 
ring-core/test/ring/middleware/multipart_params/test/byte_array.clj 
ring-core/test/ring/middleware/session/test/memory.clj 
ring-core/test/ring/middleware/session/test/cookie.clj 
ring-core/test/ring/middleware/test/session.clj 
ring-core/test/ring/middleware/test/flash.clj 
ring-core/test/ring/middleware/test/keyword_params.clj 
ring-core/test/ring/middleware/test/multipart_params.clj 
ring-core/test/ring/middleware/test/file_info.clj 
ring-core/test/ring/middleware/test/nested_params.clj 
ring-core/test/ring/middleware/test/params.clj 
ring-core/test/ring/middleware/test/
 file.clj ring-core/test/ring/middleware/test/head.clj 
ring-core/test/ring/middleware/test/content_type.clj 
ring-core/test/ring/middleware/test/resource.clj 
ring-core/test/ring/middleware/test/cookies.clj 
ring-core/test/ring/middleware/test/not_modified.clj 
ring-core/test/ring/util/test/time.clj 
ring-core/test/ring/util/test/mime_type.clj 
ring-core/test/ring/util/test/io.clj ring-core/test/ring/util/test/request.clj 
ring-core/test/ring/util/test/response.clj 
ring-core/test/ring/core/test/protocols.clj 
Exception in thread "main" java.lang.NoClassDefFoundError: 
javax/servlet/http/HttpServletRequest, 
compiling:(ring/middleware/multipart_params.clj:54:20)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:7010)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyze(Compiler.java:6729)
at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6102)
at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6420)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyze(Compiler.java:6729)
at clojure.lang.Compiler$IfExpr$Parser.parse(Compiler.java:2822)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.access$300(Compiler.java:38)
at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6368)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003)
at clojure.lang.Compiler.analyze(Compiler.java:6773)
at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991)
at cl

Bug#921763: weston: FTBFS (dh_install: missing files)

2019-02-08 Thread Santiago Vila
Package: src:weston
Version: 5.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with quilt
   dh_quilt_patch -a
No series file found
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'

[... snipped ...]

libtool: install: /usr/bin/install -c .libs/desktop-shell.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/weston/desktop-shell.la
libtool: warning: relinking 'fullscreen-shell.la'
libtool: install: (cd /<>; /bin/bash "/<>/libtool"  
--tag CC --mode=relink gcc -Wall -Wextra -Wno-unused-parameter 
-Wno-shift-negative-value -Wno-missing-field-initializers -g 
-fvisibility=hidden -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare 
-I/usr/include/pixman-1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -module 
-avoid-version -Wl,-z,relro -o fullscreen-shell.la -rpath 
/usr/lib/x86_64-linux-gnu/weston fullscreen-shell/la-fullscreen-shell.lo 
protocol/fullscreen_shell_la-fullscreen-shell-unstable-v1-protocol.lo 
libweston-5.la -lwayland-server -lpixman-1 -lxkbcommon -inst-prefix-dir 
/<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  
fullscreen-shell/.libs/la-fullscreen-shell.o 
protocol/.libs/fullscreen_shell_la-fullscreen-shell-unstable-v1-protocol.o   
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lweston-5 -lwayland-server -lpixman-1 -lxkbcommon  
-g -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,fullscreen-shell.so -o .libs/fullscreen-shell.so
libtool: install: /usr/bin/install -c .libs/fullscreen-shell.soT 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/weston/fullscreen-shell.so
libtool: install: /usr/bin/install -c .libs/fullscreen-shell.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/weston/fullscreen-shell.la
libtool: warning: relinking 'ivi-shell.la'
libtool: install: (cd /<>; /bin/bash "/<>/libtool"  
--tag CC --mode=relink gcc -Wall -Wextra -Wno-unused-parameter 
-Wno-shift-negative-value -Wno-missing-field-initializers -g 
-fvisibility=hidden -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare 
-I/usr/include/pixman-1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -module 
-avoid-version -Wl,-z,relro -o ivi-shell.la -rpath 
/usr/lib/x86_64-linux-gnu/weston ivi-shell/la-ivi-layout.lo 
ivi-shell/la-ivi-layout-transition.lo ivi-shell/la-ivi-shell.lo 
ivi-shell/la-input-panel-ivi.lo 
protocol/ivi_shell_la-ivi-application-protocol.lo libshared.la libweston-5.la 
-lwayland-server -lpixman-1 -lxkbcommon -inst-prefix-dir 
/<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  ivi-shell/.libs/la-ivi-layout.o 
ivi-shell/.libs/la-ivi-layout-transition.o ivi-shell/.libs/la-ivi-shell.o 
ivi-shell/.libs/la-input-panel-ivi.o 
protocol/.libs/ivi_shell_la-ivi-application-protocol.o  -Wl,--whole-archive 
./.libs/libshared.a -Wl,--no-whole-archive  
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lweston-5 -lwayland-server -lpixman-1 -lxkbcommon  
-g -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,ivi-shell.so -o .libs/ivi-shell.so
libtool: install: /usr/bin/install -c .libs/ivi-shell.soT 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/weston/ivi-shell.so
libtool: install: /usr/bin/install -c .libs/ivi-shell.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/weston/ivi-shell.la
libtool: warning: relinking 'hmi-controller.la'
libtool: install: (cd /<>; /bin/bash "/<>/libtool"  
--tag CC --mode=relink gcc -Wall -Wextra -Wno-unused-parameter 
-Wno-shift-negative-value -Wno-missing-field-initializers -g 
-fvisibility=hidden -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare 
-I/usr/include/pixman-1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -module 
-avoid-version -Wl,-z,relro -o hmi-controller.la -rpath 
/usr/lib/x86_64-linux-gnu/weston ivi-shell/hmi_controller_la-hmi-controller.lo 
protocol/hmi_controller_la-ivi-hmi-controller-protocol.lo libshared.la 
libweston-5.la -lwayland-server -lpixman-1 -lxkbcommon -inst-prefix-dir 
/<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  
ivi-shell/.libs/hmi_controller_la-hmi-controller.o 
protocol/.libs/hmi_controller_la-ivi-hmi-controller-protocol.o  
-Wl,--whole-archive ./.libs/libshared.a -Wl,--no-whole-archive  
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lweston-5 -lwayland-server -lpixman-1 -lxkbcommon  
-g -g -O2 -fstack-protector-strong -Wl,-z -W

Bug#921761: sssd: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:sssd
Version: 1.16.3-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with quilt,autoreconf,python2,python3,systemd \
--builddirectory=build
   dh_quilt_patch -a -O--builddirectory=build
Applying patch fix-curl-ftbfs.diff
patching file src/util/tev_curl.c

Now at patch fix-curl-ftbfs.diff
   dh_update_autotools_config -a -O--builddirectory=build
   dh_autoreconf -a -O--builddirectory=build
Creating directory build
Copying file build/config.rpath
Copying file build/mkinstalldirs
Copying file po/Makevars.template

[... snipped ...]


 1 FAILED TEST(S)
FAIL test_copy_ccache (exit status: 1)

SKIP: src/tests/whitespace_test
===

Git repository is required for this test!
SKIP src/tests/whitespace_test (exit status: 77)

SKIP: src/tests/double_semicolon_test
=

Git repository is required for this test!
SKIP src/tests/double_semicolon_test (exit status: 77)


Testsuite summary for sssd 1.16.3

# TOTAL: 99
# PASS:  96
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to sssd-de...@lists.fedorahosted.org

make[6]: *** [Makefile:35425: test-suite.log] Error 1
make[6]: Leaving directory '/<>/build'
make[5]: *** [Makefile:35533: check-TESTS] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [Makefile:36409: check-am] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [Makefile:35310: check-recursive] Error 1
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:36411: check] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_test: cd build && make -j1 check VERBOSE=1 VERBOSE=yes returned exit 
code 2
make[1]: *** [debian/rules:46: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:3: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921755: ibus-rime: FTBFS (Syntax error in cmake code)

2019-02-08 Thread Santiago Vila
Package: src:ibus-rime
Version: 1.3.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --libexecdir=/usr/lib/ibus
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
mkdir -p build
(cd build; cmake -DCMAKE_BUILD_TYPE=Release .. && make)
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
-- Checking for module 'ibus-1.0'
--   Found ibus-1.0, version 1.5.19
-- Checking for module 'libnotify'
--   Found libnotify, version 0.7.7
-- Checking for module 'rime'
CMake Error at /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:54 (set):
  Syntax error in cmake code at

/usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:54

  when parsing string

$/usr/{LIB_INSTALL_DIR}

  Syntax $/usr/{} is not supported.  Only ${}, $ENV{}, and $CACHE{} are
  allowed.
Call Stack (most recent call first):
  /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:81 (_pkgconfig_set)
  /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:103 (_pkgconfig_invoke)
  /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:473 (pkg_get_variable)
  /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:622 
(_pkg_check_modules_internal)
  /usr/share/cmake/rime/RimeConfig.cmake:22 (PKG_CHECK_MODULES)
  CMakeLists.txt:21 (find_package)


-- Configuring incomplete, errors occurred!
See also "/<>/build/CMakeFiles/CMakeOutput.log".
make[1]: *** [Makefile:15: ibus-engine-rime] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit 
code 2
make: *** [debian/rules:11: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ibus-rime.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921756: libfm-qt: FTBFS (dh_auto_configure fails)

2019-02-08 Thread Santiago Vila
Package: src:libfm-qt
Version: 0.13.1-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem cmake
   dh_update_autotools_config -a -O--buildsystem=cmake
   dh_autoreconf -a -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DPULL_TRANSLATIONS=OFF \
-DUPDATE_TRANSLATIONS=OFF \
-DCMAKE_BUILD_TYPE=RelWithDebInfo
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPULL_TRANSLATIONS=OFF 
-DUPDATE_TRANSLATIONS=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc

[... snipped ...]

Feature record: CXX_FEATURE:0cxx_deleted_functions
Feature record: CXX_FEATURE:0cxx_digit_separators
Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
Feature record: CXX_FEATURE:0cxx_explicit_conversions
Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
Feature record: CXX_FEATURE:0cxx_extern_templates
Feature record: CXX_FEATURE:0cxx_final
Feature record: CXX_FEATURE:0cxx_func_identifier
Feature record: CXX_FEATURE:0cxx_generalized_initializers
Feature record: CXX_FEATURE:0cxx_generic_lambdas
Feature record: CXX_FEATURE:0cxx_inheriting_constructors
Feature record: CXX_FEATURE:0cxx_inline_namespaces
Feature record: CXX_FEATURE:0cxx_lambdas
Feature record: CXX_FEATURE:0cxx_lambda_init_captures
Feature record: CXX_FEATURE:0cxx_local_type_template_args
Feature record: CXX_FEATURE:0cxx_long_long_type
Feature record: CXX_FEATURE:0cxx_noexcept
Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
Feature record: CXX_FEATURE:0cxx_nullptr
Feature record: CXX_FEATURE:0cxx_override
Feature record: CXX_FEATURE:0cxx_range_for
Feature record: CXX_FEATURE:0cxx_raw_string_literals
Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
Feature record: CXX_FEATURE:0cxx_return_type_deduction
Feature record: CXX_FEATURE:0cxx_right_angle_brackets
Feature record: CXX_FEATURE:0cxx_rvalue_references
Feature record: CXX_FEATURE:0cxx_sizeof_member
Feature record: CXX_FEATURE:0cxx_static_assert
Feature record: CXX_FEATURE:0cxx_strong_enums
Feature record: CXX_FEATURE:1cxx_template_template_parameters
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPULL_TRANSLATIONS=OFF 
-DUPDATE_TRANSLATIONS=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo .. returned exit 
code 1
make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libfm-qt.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921762: timeshift: FTBFS (error: The type name `AppExcludeEntry' could not be found)

2019-02-08 Thread Santiago Vila
Package: src:timeshift
Version: 18.9+ds-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   dh_auto_build -a
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/timeshift-18.9+ds'
cd src; make all
make[2]: Entering directory '/<>/timeshift-18.9+ds/src'
#timeshift-gtk
valac -g -X -D'GETTEXT_PACKAGE="timeshift"' \
--Xcc="-lm" --Xcc="-O3" -D VTE_291 -D GTK3_18  --thread \
Core/*.vala Gtk/*.vala Utility/*.vala Utility/Gtk/*.vala \
-o timeshift-gtk \
--pkg glib-2.0 --pkg gio-unix-2.0 --pkg posix \
--pkg gee-0.8 --pkg json-glib-1.0 \
--pkg gtk+-3.0 --pkg vte-2.91 
Core/Main.vala:64.23-64.37: error: The type name `AppExcludeEntry' could not be 
found
public Gee.ArrayList exclude_list_apps;
 ^^^
Core/Main.vala:528.41-528.55: error: The type name `AppExcludeEntry' could not 
be found
exclude_list_apps = new Gee.ArrayList();
  ^^^
Gtk/ExcludeAppsBox.vala:102.4-102.18: error: The type name `AppExcludeEntry' 
could not be found
AppExcludeEntry entry;
^^^
Gtk/ExcludeAppsBox.vala:113.4-113.18: error: The type name `AppExcludeEntry' 
could not be found
AppExcludeEntry entry;
^^^
Gtk/ExcludeAppsBox.vala:126.4-126.18: error: The type name `AppExcludeEntry' 
could not be found
AppExcludeEntry entry;
^^^
Gtk/ExcludeAppsBox.vala:150.43-150.57: error: The type name `AppExcludeEntry' 
could not be found
var model = new Gtk.ListStore(3, typeof(AppExcludeEntry), 
typeof(bool), typeof(string));
^^^
Command-line option `--thread` is deprecated and will be ignored
Compilation failed: 6 error(s), 0 warning(s)
make[2]: *** [makefile:50: all] Error 1
make[2]: Leaving directory '/<>/timeshift-18.9+ds/src'
make[1]: *** [makefile:2: all] Error 2
make[1]: Leaving directory '/<>/timeshift-18.9+ds'
dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit 
code 2
make: *** [debian/rules:12: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921760: shim-signed: FTBFS (shimx64.efi.signed build/shimx64.efi.signed differ)

2019-02-08 Thread Santiago Vila
Package: src:shim-signed
Version: 1.28+nmu1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>/shim-signed-1.28+nmu1'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>/shim-signed-1.28+nmu1'
   dh_auto_test -a
make -j1 check
make[1]: Entering directory '/<>/shim-signed-1.28+nmu1'
mkdir -p build
# Verifying that the image is signed with the correct key.
sbverify --cert MicCorUEFCA2011_2011-06-27.crt shimx64.efi.signed
warning: data remaining[1044456 vs 1169528]: gaps between PE/COFF sections?
Signature verification OK
# Verifying that we have the correct binary.
sbattach --detach build/detached-sig shimx64.efi.signed 
warning: data remaining[1044456 vs 1169528]: gaps between PE/COFF sections?
cp /usr/lib/shim/shimx64.efi build/shimx64.efi.signed
sbattach --attach build/detached-sig build/shimx64.efi.signed
warning: data remaining[1035776 vs 1160847]: gaps between PE/COFF sections?
warning: data remaining[1035776 vs 1160848]: gaps between PE/COFF sections?
Signing Unsigned original image
cmp shimx64.efi.signed build/shimx64.efi.signed
shimx64.efi.signed build/shimx64.efi.signed differ: char 217, line 2
make[1]: *** [Makefile:11: check] Error 1
make[1]: Leaving directory '/<>/shim-signed-1.28+nmu1'
dh_auto_test: make -j1 check returned exit code 2
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/shim-signed.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921757: os-autoinst: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:os-autoinst
Version: 4.5.1527308405.8b586d5-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:25: installing './compile'
configure.ac:25: installing './config.guess'

[... snipped ...]

[2019-01-06T11:53:34.0129 UTC] [debug] cannot access 'image.qcow2'
[2019-01-06T11:53:34.0129 UTC] [debug] : No such file or directory
[2019-01-06T11:53:34.0129 UTC] [debug] 

not ok 3 - command failed and calls die
#   Failed test 'command failed and calls die'
#   at ./13-osutils.t line 167.
#   ''
# doesn't match '(?^u:runcmd failed with exit code \d+)'
1..3
# Looks like you failed 1 test of 3.
not ok 6 - runcmd
#   Failed test 'runcmd'
#   at ./13-osutils.t line 168.
1..6
# Looks like you failed 1 test of 6.
FAIL 13-osutils.t (exit status: 1)


Testsuite summary for os-autoinst 1.1.0

# TOTAL: 18
# PASS:  17
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See t/test-suite.log
Please report to https://github.com/os-autoinst/os-autoinst

make[5]: *** [Makefile:530: test-suite.log] Error 1
make[5]: Leaving directory '/<>/t'
make[4]: *** [Makefile:638: check-TESTS] Error 2
make[4]: Leaving directory '/<>/t'
make[3]: *** [Makefile:830: check-am] Error 2
make[3]: Leaving directory '/<>/t'
make[2]: *** [Makefile:872: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:19: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/os-autoinst.html

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921759: sdaps: FTBFS (Error running "pdflatex" to compile the LaTeX file)

2019-02-08 Thread Santiago Vila
Package: src:sdaps
Version: 1.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with python2 --buildsystem=pybuild
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_sdaps/build/sdaps
copying sdaps/defs.py -> 
/<>/.pybuild/cpython2_2.7_sdaps/build/sdaps
copying sdaps/paths.py -> 
/<>/.pybuild/cpython2_2.7_sdaps/build/sdaps

[... snipped ...]

(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exromp.mf
 Ok [38] [63] [190])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrulett.mf
 Ok [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78]
[79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrllett.mf
 Ok [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108]
[109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120]
[121] [122])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrdigit.mf
 Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrligtb.mf
 Ok) ) ) )
(some charht values had to be adjusted by as much as 0.08084pt)
Font metrics written on ecrm1440.tfm.
Output written on ecrm1440.600gf (256 characters, 71064 bytes).
Transcript written on ecrm1440.log.
mktexpk: /tmp/texfonts/pk/ljfour/jknappen/ec/ecrm1440.600pk: successfully 
generated.
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
Running pdflatex now twice to generate the report.
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
Error: An error occured in the setup routine. The survey directory still 
exists. You can for example check the questionnaire.log file for LaTeX compile 
errors.
Running pdflatex now twice to generate the questionnaire.
Error running "pdflatex" to compile the LaTeX file.
Traceback (most recent call last):
  File "../sdaps.py", line 23, in 
sys.exit(sdaps.main(local_run = True))
  File "/<>/sdaps/__init__.py", line 64, in main
return cmdline['_func'](cmdline)
  File "/<>/sdaps/cmdline/setuptex.py", line 47, in setup_tex
return setuptex.setup(survey, cmdline['questionnaire.tex'], 
cmdline['additional_questions'], cmdline['add'])
  File "/<>/sdaps/setuptex/__init__.py", line 100, in setup
raise AssertionError('PDF file not generated')
AssertionError: PDF file not generated
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



Bug#921758: rcs: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:rcs
Version: 5.9.4-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes

[... snipped ...]

PASS: t410
PASS: t420
PASS: t430
PASS: t440
PASS: t450
PASS: t460
PASS: t470
PASS: t510
PASS: t511
PASS: t600
PASS: t601
PASS: t602
PASS: t603
PASS: t604
PASS: t605
PASS: t606
PASS: t607
PASS: t608
PASS: t609
PASS: t620
PASS: t630
PASS: t780
PASS: t790
PASS: t800
PASS: t801
PASS: t802
PASS: t803
PASS: t804
PASS: t805
FAIL: t810
PASS: t900
PASS: t999

1 of 51 tests failed
Please report to bug-...@gnu.org

make[3]: *** [Makefile:1510: check-TESTS] Error 1
make[3]: Leaving directory '/<>/tests'
make[2]: *** [Makefile:1637: check-am] Error 2
make[2]: Leaving directory '/<>/tests'
make[1]: *** [Makefile:1393: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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 BTS web page for this package.

Thanks.



  1   2   >