Bug#917266: [debian-mysql] Bug#917266: Bug#917266: missing /usr/include/mysql

[Scott Kitterman]

On Fri, 28 Dec 2018 16:41:33 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= 
 wrote:
> Hello!
> 
> pe 28. jouluk. 2018 klo 15.33 Scott Kitterman (deb...@kitterman.com) 
kirjoitti:
> >
> > I did add a symlink as in the attached patch and postfix builds again.  I
> > don't have a good way to do run-time testing, so I don't know if there are 
any
> > further changes needed, but this at least fixes package building.
> 
> If you use Salsa to make a merge request you will get gitlab-ci
> testing for free, also run-time.
> 
> See easy instructions at https://wiki.debian.org/Teams/MySQL/patches
> 
> I really strongly recommend you take a shot at using Salsa and
> Gitlab-CI that it has built-in.

I've submitted the merge request:

https://salsa.debian.org/mariadb-team/mariadb-10.3/merge_requests/8

Setting up CI on my branch to test something I've already built and tested 
locally seems overkill.  The run-time testing I was referring to was of 
postfix using the mysql compatibility links, not mariadb.

Scott K

Bug#917593: mpd: FTBFS ('_IO_off64_t' has not been declared)

[Max Kellermann]

On 2018/12/29 01:25, Santiago Vila  wrote:
> In file included from /usr/include/libroar/libroar.h:173,
>  from /usr/include/roaraudio.h:133,
>  from src/output/plugins/RoarOutputPlugin.cxx:36:
> /usr/include/libroar/vio_stdio.h:50:46: error: '_IO_off64_t' has not been 
> declared
>  int roar_vio_to_stdio_lseek (void *__cookie, _IO_off64_t *__pos, int __w);

This is clearly a libroar bug and has nothing to do with MPD.

Upstream bug report (for MPD):
https://github.com/MusicPlayerDaemon/MPD/issues/377

See https://github.com/MusicPlayerDaemon/MPD/commit/06ca08ce555 for my
opinion on this bug.

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

[積丹尼 Dan Jacobson]

Indeed with G_SLICE=debug-blocks it starts, but still says
 
GEGL-Message: 15:02:47.435: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 15:02:47.499: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
Failed to execute child process “dbus-launch” (No such file or directory)
(gimp:7862): Gtk-WARNING **: 15:02:47.681: Unable to locate theme engine in 
module_path: "pixmap",
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file or 
directory
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
(gimp:7862): GLib-GObject-CRITICAL **: 15:02:55.648: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

G_SLICE=debug-blocks G_MESSAGES_DEBUG=all gave:

GEGL-Message: 15:07:29.514: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 15:07:29.578: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
(gimp:8067): GLib-DEBUG: 15:07:29.580: posix_spawn avoided (fd close requested) 
Failed to execute child process “dbus-launch” (No such file or directory)
(gimp:8067): GLib-DEBUG: 15:07:29.652: posix_spawn avoided (fd close requested) 
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: gdk_pixbuf_from_pixdata() called on:
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Encoding raw
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Dimensions: 64 x 64
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Rowstride: 256, Length: 16408
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Copy pixels == false
(gimp:8067): Gtk-WARNING **: 15:07:29.664: Unable to locate theme engine in 
module_path: "pixmap",
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: gdk_pixbuf_from_pixdata() called on:
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Encoding rle
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Dimensions: 22 x 22
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Rowstride: 88, Length: 1606
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Copy pixels == true
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file or 
directory
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
(file-rawtherapee:8080): GLib-DEBUG: 15:07:30.160: posix_spawn avoided (fd 
close requested) 
(file-darktable:8082): GLib-DEBUG: 15:07:30.172: posix_spawn avoided (fd close 
requested) 
(gimp:8067): GLib-GObject-CRITICAL **: 15:07:34.515: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

The rest of the commands you gave me failed to start gimp. I did add the
symbols packages yet.

Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)

[Matteo F. Vescovi]

Andreas,

I'll open a specific transition bug report for that, once I've tested all
r-deps but not earlier.

Thus, I'll leave this bug report closed since it tracks another issue (or
feature, at your choice ;) ).

Cheers.

Il giorno sab 29 dic 2018, 07:19 Andreas Metzler  ha
scritto:

> On 2018-12-27 "Matteo F. Vescovi"  wrote:
> > Hi!
>
> > On 2018-12-27 at 19:38 (+01), Eric Valette wrote:
> >> Package: libilmbase23
> >> Version: 2.3.0-3
> >> Severity: critical
> >> Justification: breaks unrelated software
>
> > [...]
>
> > Well, 2.3.0-3 revision is still in the experimental suite.
> > That's the right place to prepare a transition, indeed.
> > We're working on it, along with openexr.
>
> Hello,
>
> please re-open. The package is in Debian. We have a bug tracking system
> for packages in Debian, where we track open issues and users can check
> for known breakage.
>
> cu Andreas
>
> PS: Thanks, Eric for testing packages in experimental!
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>

Bug#917588: marked as done (ding-libs: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 29 Dec 2018 07:04:00 +
with message-id 
and subject line Bug#917588: fixed in ding-libs 0.6.1-2
has caused the Debian Bug report #917588,
regarding ding-libs: 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.)


-- 
917588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ding-libs
Version: 0.6.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 quilt
   dh_quilt_patch -a
No patches in series
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
libtoolize: copying file 'build/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 ...]

PASS: ini_configmod_ut
PASS: ini_save_ut
===
   ding-libs 0.6.1: ./test-suite.log
===

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: ini_validators_ut_check
=

Running suite(s): ini_validators
94%: Checks: 18, Failures: 1, Errors: 0
ini/ini_validators_ut_check.c:610:F:ini_allowed_options:test_ini_allowed_options_wrong_regex:0:
 Got msg: [[rule/options_for_foo]: Cannot compile regular expression from 
option 'section_re'. Error: 'Unmatched [, [^, [:, [., or [=']
FAIL ini_validators_ut_check (exit status: 1)


Testsuite summary for ding-libs 0.6.1

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to sssd-de...@lists.fedorahosted.org

make[3]: *** [Makefile:1744: test-suite.log] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:1852: check-TESTS] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:2192: check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ding-libs.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: ding-libs
Source-Version: 0.6.1-2

We believe that the bug you reported is fixed in the latest version of
ding-libs, 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.
Timo Aaltonen  (supplier of updated ding-libs 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, 29 Dec 2018 08:50:04 +0200
Source: ding-libs
Binary: libpath-utils-dev libpath-utils1 libdhash-dev libdhash1 
libcollection-dev libcollection4 libref-array-dev libref-array1 
libini-config-dev libini-config5 libbasicobjects-dev libbasicobjects0
Architecture: source
Version: 0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian SSSD Team 
Changed-By: Timo Aaltonen 
Description:
 libbasicobjects-dev - Basic object types for C -- development files

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Tommi Höynälänmaa]

Sorry, I misinterpreted the log. The error is probably caused by missing 
dependencies in gnome/Makefile.am. A fix is coming soon.


 - Tommi


On 28.12.2018 20:00, Santiago Vila wrote:

On Fri, Dec 28, 2018 at 07:51:27PM +0200, Tommi Höynälänmaa wrote:

Hi


Is there a pending upload of guile-gnome-platform for unstable which
is required for theme-d-gnome to build properly also in unstable?

Note: The build log says --with-guile-gnome=2.16.5 but current version
is 2.16.4-5. Could this small mismatch be the problem?

This may cause problems but the main thing is that packages
theme-d-translator and theme-d-stdlib are not present in the build
environment (at least the correct versions are not).

Hmm, but I'm not installing build-dependencies by hand.

I'm using sbuild (and reproducible-builds is using pbuilder)
which should already ensure that the "correct" versions are installed.

Actually, either the version currently available in unstable is ok,
or otherwise the build would fail with "unsatisfiable build-depends".

So: How do you know that the build is using "incorrect versions" and
what exactly do you mean by "incorrect versions"?

I'm a little bit confused.

Thanks.

Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)

[Andreas Metzler]

On 2018-12-27 "Matteo F. Vescovi"  wrote:
> Hi!

> On 2018-12-27 at 19:38 (+01), Eric Valette wrote:
>> Package: libilmbase23
>> Version: 2.3.0-3
>> Severity: critical
>> Justification: breaks unrelated software

> [...]

> Well, 2.3.0-3 revision is still in the experimental suite.
> That's the right place to prepare a transition, indeed.
> We're working on it, along with openexr.

Hello,

please re-open. The package is in Debian. We have a bug tracking system
for packages in Debian, where we track open issues and users can check
for known breakage.

cu Andreas

PS: Thanks, Eric for testing packages in experimental!
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#917605: rainloop: Depends on libphp-predis, which is scheduled for removal (per #915069)

[Niels Thykier]

Package: rainloop
Version: 1.11.1-1
Severity: serious

Hi,

The rainloop package currently depends on libphp-predis, which is
scheduled for removal (see #915069 for the details).  AFAICT, the
replacement for libphp-predis is php-nrk-predis (which is a newer
version of the same code just using a different package name).

Please consider migrating rainloop to php-nrk-predis soon.  As it is,
rainloop plus libphp-predis will be removed from testing before buster
is released.

Thanks,
~Niels

Bug#917562: [Pkg-javascript-devel] Bug#917562: data/features directory is missing in node-caniuse-lite

[Pirate Praveen]

On 2018, ഡിസംബർ 29 12:29:12 AM IST, Jonas Smedegaard  wrote:
>Quoting Pirate Praveen (2018-12-28 19:19:12)
>> When trying to build autoprefixer.js which build depends on
>> node-caniuse-lite, I got this error and upon inspection I found
>> data/features directory is missing.
>> 
>> ERROR in /usr/lib/nodejs/caniuse-lite/data/features.js
>> Module not found: Error: Can't resolve './features/aac' in
>> '/usr/lib/nodejs/caniuse-lite/data'
>>  @ /usr/lib/nodejs/caniuse-lite/data/features.js 1:22-47
>>  @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/features.js
>>  @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/index.js
>>  @ /usr/lib/nodejs/autoprefixer/lib/autoprefixer.js
>> 
>> I was not able to figure out why this is not working now. Need help.
>
>Upstream source seems to include some tests not tried during build.
>
>I suggest to enable those during build and the autopkgtest framework.
>
>I mean, make sure that something works - anything at all - before 
>debugging why integration with something specific like autoprefixer.

We are regenerating files in data directory for dfsg, now we already know 
data/features is not generated (data/region was regenerated as expected). There 
was no error or useful messages during generation of these.

>
> - Jonas

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

[Niels Thykier]

gregor herrmann:
> On Sat, 29 Dec 2018 00:25:25 +, Santiago Vila wrote:
> 
>> Package: src:libterm-termkey-perl
>> Version: 0.16-3
>> Severity: serious
>> Tags: ftbfs
> 
>> I tried to build this package in buster but it failed:
> 
>> Test Summary Report
>> ---
>> t/05flags.t   (Wstat: 11 Tests: 2 Failed: 0)
>>   Non-zero wait status: 11
>>   Parse errors: Bad plan.  You planned 4 tests but ran 2.
> 
> Same in #917497.
> 
> Both tests fail during build and not during autopkgtests (locally and
> on r-b/ci.debian.net).
> 
> After thinking a bit I tried:
> 
> #v+
> --- a/debian/rules
> +++ b/debian/rules
> @@ -4,4 +4,4 @@
> dh $@
> 
>  override_dh_auto_test:
> -   TERM=vt100 dh_auto_test
> +   TERM=vt100 prove --blib --verbose t/*.t
> #v-
> 
> [...] 
> 
> From the debhelper changelog:
> 
> debhelper (11.5.4) unstable; urgency=medium
> 
>   [ Niels Thykier ]
>   * Dh_Lib.pm: Reopen stdin to read from /dev/null in doit (and its sibling
> functions) to prevent issues when stdin is open in write-only mode
> (which is what nohup(1) does).  Thanks to Julian Gilbey for reporting
> the issue and providing a sample patch for it as well.
> (Closes: #913663)
> 
> 
> Can this be related? (The failing test operate on \*STDIN.)
> Cc'ing the debhelper bug and debhelper maintainers …
> 
> 
> Cheers,
> gregor
> 
> 

Hi gregor,

Indeed, that could be related.

To confirm it, please consider editing/patching
lib/Debian/Debhelper/Dh_Lib.pm by finding the "_doit" function and
commenting out the following line[1]:

"""
open(STDIN, '<', '/dev/null') or error("redirect STDIN failed: $!");
"""

If your test starts working again after that has been removed, then we
confirmed that is the problem.

Can you elaborate a bit more on what libterm-termkey-perl expects from
STDIN here?  A tty perhaps?  Does/did it work under nohup (without the
debhelper work around to make nohup work)?

Thanks,
~Niels

[1] Introduced in fff0f01c4ceb910ec4d0455718a2f60e22463792 but the
entire commit is not directly revertable.

Bug#914985: marked as done (tensorflow: FTBFS: /usr/bin/ld: cannot find -lhighwayhash)

[Debian Bug Tracking System]

Your message dated Sat, 29 Dec 2018 04:20:05 +
with message-id 
and subject line Bug#914985: fixed in tensorflow 1.10.1+dfsg-A2
has caused the Debian Bug report #914985,
regarding tensorflow: FTBFS: /usr/bin/ld: cannot find -lhighwayhash
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.)


-- 
914985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tensorflow
Version: 1.10.1+dfsg-A1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

tensorflow FTBFS on most architectures with

/usr/bin/ld: cannot find -lhighwayhash
collect2: error: ld returned 1 exit status

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


Andreas
--- End Message ---
--- Begin Message ---
Source: tensorflow
Source-Version: 1.10.1+dfsg-A2

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated tensorflow package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Dec 2018 05:31:39 +
Source: tensorflow
Binary: tensorflow-doc libtensorflow-framework1.10 libtensorflow1.10 
libtensorflow-cc1.10 libtensorflow-dev
Architecture: source
Version: 1.10.1+dfsg-A2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 libtensorflow-cc1.10 - Computation using data flow graphs for scalable machine 
learning
 libtensorflow-dev - Computation using data flow graphs for scalable machine 
learning
 libtensorflow-framework1.10 - Computation using data flow graphs for scalable 
machine learning
 libtensorflow1.10 - Computation using data flow graphs for scalable machine 
learning
 tensorflow-doc - Computation using data flow graphs for scalable machine 
learning
Closes: 914985
Changes:
 tensorflow (1.10.1+dfsg-A2) experimental; urgency=medium
 .
   * Require B-D highwayhash-dev on all architectures. (Closes: #914985)
   * Add Yunqiang Su (syq) to Uploaders.
 .
   [ BuildSystem ]
   * Significantly simplified code of shogun.py .
   * Add -DNDEBUG and -pipe to default CXXFLAGS.
   * Work-In-Progress support for the python interface. (Disabled by default)
   * Create version_info.cc by ninja target instead of patch.
   * Fix installation path for the embedded Eigen3 library.
   + See git history for detailed changes.
   + The build system is feature-frozen. It will be replaced by a new one
 for the upcoming TensorFlow 2.X series.
Checksums-Sha1:
 29fc6605f3964e1b2314b6d8476cc38e4d038338 3012 tensorflow_1.10.1+dfsg-A2.dsc
 75f337bd74e08942f6e82980a55abc023b722cad 2451232 
tensorflow_1.10.1+dfsg-A2.debian.tar.xz
 83abb4f6443a6739584e6f4e1c6f8935546b15f5 9316 
tensorflow_1.10.1+dfsg-A2_source.buildinfo
Checksums-Sha256:
 46d6fa56b5671a26f4e0cb3470ad3d1badb171f30c14a7017e79152940c973aa 3012 
tensorflow_1.10.1+dfsg-A2.dsc
 f7eb60277bf82e32818ec952f046f113b2d5474fb0caec6be95fe01964d6c38a 2451232 
tensorflow_1.10.1+dfsg-A2.debian.tar.xz
 faa6516a5920053e876c7695439868fffdd349fe84d548063246cb0db9973142 9316 
tensorflow_1.10.1+dfsg-A2_source.buildinfo
Files:
 6d302d31b9e8c4a0c6fdf47a62cab6e4 3012 science optional 
tensorflow_1.10.1+dfsg-A2.dsc
 c5359842e3f5bd401b635a7b15a59c65 2451232 science optional 
tensorflow_1.10.1+dfsg-A2.debian.tar.xz
 d7eba401aef495433b728f6c9933a433 9316 science optional 
tensorflow_1.10.1+dfsg-A2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlwm5osACgkQYmRes19o
aorekhAAjNDBbU4UXid1GdkRQiAJ4cmCDpW1aOzCW/KwV/ZKrTlo3Gyqw/3/bEub
fHU0wiJE8V1VxIhnJFvYcQ/9bIxyqdc5zL2GM6R18HHCRJM88gsmolaKE19DS5JF
SlrG7bDp0COcYL5LZ0v4Riz6VDL9I3ET18lLm33zCcpJmY5eh8nCZCmoUQ7seTxu
vDLmhZj6ms9AeYN6r4gbSZxE4F6b0Qir5FDHzmQvKs1CbXblBmQjKTZc7VTLvNip
Cnk5ASHFmrrsUVlQPockOeeGagYbhMGbCP11Wobg+9MTcoNW4TivFlH8Y8RJ3Ors
JoroP+Dtbtf2dU9cg6D2s3F0OFS93agKwAyst3aFEX++HNb6etPzpvPW/O6MwbPy
ViTss/a3mKniJ9PSDIo91mZxREHD5DthnknljRGMPmiYBkQcy1S2bvSwOwVtbnAy

Processed: unmerging 917524, reassign 917524 to initramfs-tools-core

[Debian Bug Tracking System]

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

> unmerge 917524
Bug #917524 {Done: Michael Biebl } [udev] initramfs-tools: 
Upgrade from initramfs-tools package fails
Bug #917124 {Done: Michael Biebl } [udev] lvm2 logical 
volumes are not properly initialized
Bug #917136 {Done: Michael Biebl } [udev] udev: LVM volumes 
fail to initialize properly with udev 240-1
Bug #917166 {Done: Michael Biebl } [udev] Errors on and after 
upgrade to 2.03.01-2, swap on lvm not mounted
Bug #917261 {Done: Michael Biebl } [udev] 
linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing 
/ not created on system startup
Disconnected #917524 from all other report(s).
> reassign 917524 initramfs-tools-core 0.132
Bug #917524 {Done: Michael Biebl } [udev] initramfs-tools: 
Upgrade from initramfs-tools package fails
Bug reassigned from package 'udev' to 'initramfs-tools-core'.
No longer marked as found in versions systemd/240-1.
No longer marked as fixed in versions systemd/240-2.
Bug #917524 {Done: Michael Biebl } [initramfs-tools-core] 
initramfs-tools: Upgrade from initramfs-tools package fails
Marked as found in versions initramfs-tools/0.132.
> thanks
Stopping processing here.

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

Bug#884509: marked as done (openscad: (Build-)Depends on ttf-marvosym which is going to be removed)

[Debian Bug Tracking System]

Your message dated Sat, 29 Dec 2018 03:04:30 +
with message-id 
and subject line Bug#884509: fixed in openscad 2015.03-2+dfsg-2.1
has caused the Debian Bug report #884509,
regarding openscad: (Build-)Depends on ttf-marvosym which is going to be removed
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.)


-- 
884509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openscad
Version: 2015.03-2+dfsg-2
Severity: serious
Tags: sid buster
Control: block 881704 with -1

ttf-marvosym is planned for removal, see #881704, #820231 and
http://www.martinvogel.de/blog/index.php?/archives/131-Marvosym.ttf.html

Please drop the Build-Depends and the Depends in openscad-testing-data
and switch to a different font.


Andreas
--- End Message ---
--- Begin Message ---
Source: openscad
Source-Version: 2015.03-2+dfsg-2.1

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
openscad 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: Sat, 29 Dec 2018 02:32:32 +0100
Source: openscad
Binary: openscad openscad-testing openscad-testing-data openscad-dbg
Architecture: source
Version: 2015.03-2+dfsg-2.1
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Description:
 openscad   - script file based graphical CAD environment
 openscad-dbg - script file based graphical CAD environment (debugging symbols)
 openscad-testing - script file based graphical CAD environment (test suite)
 openscad-testing-data - script file based graphical CAD environment (test 
suite data)
Closes: 809634 883986 884509 885429
Changes:
 openscad (2015.03-2+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add emacsen-startup file (Closes: #809634)
   * Add Debian DEP-8 test control file (Closes: #885429)
   * Drop ttf-marvosym from Build-Depends (Closes: #884509)
   * New patch
 * Build system: Strip -g -O2 from CGAL_CXX_FLAGS_INIT in testsuite
   * Reduce generated debug info during build by passing -g1 to the
 compiler on mips and mipsel to avoid OOM issues (Closes: #883986)
Checksums-Sha1:
 4c587d518cb28376f6e26ef794e9663c84badb7d 2809 openscad_2015.03-2+dfsg-2.1.dsc
 d05cd4c2423cfb1861931794c082014e2d9afaf9 30048 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 3f023288d8c608f82c24b059c26be2bfff25d840 15091 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo
Checksums-Sha256:
 d6d378cd9aeebecd5c50ac9248c5d70ecca8529cc7dac56410e2ab4296e609d7 2809 
openscad_2015.03-2+dfsg-2.1.dsc
 745f2dc15d8ab401a15d26875b8dda3aeefe99ed6e3d91193a0f1b1e7e587134 30048 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 45894e50e7475e595ea5c5f4cf7b0654dedebf1571ea00876cb169a9153f4723 15091 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo
Files:
 5e4b9ec6105ca4f76f97cdd4847d3cb3 2809 graphics optional 
openscad_2015.03-2+dfsg-2.1.dsc
 053ce4561670920dcc82b03b35b69426 30048 graphics optional 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 3ec0e341e8fc00c8309438fef70bd126 15091 graphics optional 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlwm0KsACgkQdCY7N/W1
+RMrVBAAunk1PbrucrtuzJptHdaC3gtaw3V0jYX6rgZBTcqnb1dj4/Fco46cjnYK
2bf+3pL5YI3fmES2vYXgNYwSo0z9IASPdw8GnMcibFCidEBvr2tYGVfKMUJQ2Kh6
CjwBm+i+zfgLjCWw4T2J0/ueY4frHbAY7DB03c74BQOSDErekJdqjPhhMpS4LOnE
HwuJc2yD7QHDRiMaSkP8mxlisUiqzFIvt7KK8ZfjGo+6W9WXj3jgE2jV2MbD5O66
EDlFlWkVAMmtyAHgqUBpN2JE/RkgwaLCWnvtF9ZQVxBQDPegud9fOgQ6Jl8whkph
It4nDYOfR4TkUrXUaCiiVVg5PR7O3mGUj725wTvN9ADAalPDSvrPjgbp8NACvYJd
e4/sfxtLfF95ugA4rmVPzxDUqoQPgJrHPJ8nO65n3yrv6o6t+itxWqS5YAUgi3Sk
fOznKBCtpHQsLp4uJo2FgT8nwzwcp4R6EmDKgIRhBiMiA5XjqtGHJT6/BNDgQaHQ
zQukBtuPQUgcV/lHrLVWY9r7pG+JK/5sHlruYoI8jOAhME61lDk2YfrcJ8oijpmY
WYfF1ppZU/d3pjtnQTnGyw2N+GRYdf61yt9xwQQ9gXVd8AQ81CZtJMd0YIz2sAYF
funAKQXh3+wGaO4MBtbg5uMA/yi+U/RXdtUbpal4eEbJjm5hZjk=
=qIMF
-END PGP SIGNATURE End Message ---

Bug#883986: marked as done (openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory)

[Debian Bug Tracking System]

Your message dated Sat, 29 Dec 2018 03:04:30 +
with message-id 
and subject line Bug#883986: fixed in openscad 2015.03-2+dfsg-2.1
has caused the Debian Bug report #883986,
regarding openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot 
allocate memory
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.)


-- 
883986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openscad
Version: 2015.03-2+dfsg-2
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

openscad did run out of memory during the recent binNMU on mips/mipsel:

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


Andreas
--- End Message ---
--- Begin Message ---
Source: openscad
Source-Version: 2015.03-2+dfsg-2.1

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
openscad 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: Sat, 29 Dec 2018 02:32:32 +0100
Source: openscad
Binary: openscad openscad-testing openscad-testing-data openscad-dbg
Architecture: source
Version: 2015.03-2+dfsg-2.1
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Description:
 openscad   - script file based graphical CAD environment
 openscad-dbg - script file based graphical CAD environment (debugging symbols)
 openscad-testing - script file based graphical CAD environment (test suite)
 openscad-testing-data - script file based graphical CAD environment (test 
suite data)
Closes: 809634 883986 884509 885429
Changes:
 openscad (2015.03-2+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add emacsen-startup file (Closes: #809634)
   * Add Debian DEP-8 test control file (Closes: #885429)
   * Drop ttf-marvosym from Build-Depends (Closes: #884509)
   * New patch
 * Build system: Strip -g -O2 from CGAL_CXX_FLAGS_INIT in testsuite
   * Reduce generated debug info during build by passing -g1 to the
 compiler on mips and mipsel to avoid OOM issues (Closes: #883986)
Checksums-Sha1:
 4c587d518cb28376f6e26ef794e9663c84badb7d 2809 openscad_2015.03-2+dfsg-2.1.dsc
 d05cd4c2423cfb1861931794c082014e2d9afaf9 30048 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 3f023288d8c608f82c24b059c26be2bfff25d840 15091 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo
Checksums-Sha256:
 d6d378cd9aeebecd5c50ac9248c5d70ecca8529cc7dac56410e2ab4296e609d7 2809 
openscad_2015.03-2+dfsg-2.1.dsc
 745f2dc15d8ab401a15d26875b8dda3aeefe99ed6e3d91193a0f1b1e7e587134 30048 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 45894e50e7475e595ea5c5f4cf7b0654dedebf1571ea00876cb169a9153f4723 15091 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo
Files:
 5e4b9ec6105ca4f76f97cdd4847d3cb3 2809 graphics optional 
openscad_2015.03-2+dfsg-2.1.dsc
 053ce4561670920dcc82b03b35b69426 30048 graphics optional 
openscad_2015.03-2+dfsg-2.1.debian.tar.xz
 3ec0e341e8fc00c8309438fef70bd126 15091 graphics optional 
openscad_2015.03-2+dfsg-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlwm0KsACgkQdCY7N/W1
+RMrVBAAunk1PbrucrtuzJptHdaC3gtaw3V0jYX6rgZBTcqnb1dj4/Fco46cjnYK
2bf+3pL5YI3fmES2vYXgNYwSo0z9IASPdw8GnMcibFCidEBvr2tYGVfKMUJQ2Kh6
CjwBm+i+zfgLjCWw4T2J0/ueY4frHbAY7DB03c74BQOSDErekJdqjPhhMpS4LOnE
HwuJc2yD7QHDRiMaSkP8mxlisUiqzFIvt7KK8ZfjGo+6W9WXj3jgE2jV2MbD5O66
EDlFlWkVAMmtyAHgqUBpN2JE/RkgwaLCWnvtF9ZQVxBQDPegud9fOgQ6Jl8whkph
It4nDYOfR4TkUrXUaCiiVVg5PR7O3mGUj725wTvN9ADAalPDSvrPjgbp8NACvYJd
e4/sfxtLfF95ugA4rmVPzxDUqoQPgJrHPJ8nO65n3yrv6o6t+itxWqS5YAUgi3Sk
fOznKBCtpHQsLp4uJo2FgT8nwzwcp4R6EmDKgIRhBiMiA5XjqtGHJT6/BNDgQaHQ
zQukBtuPQUgcV/lHrLVWY9r7pG+JK/5sHlruYoI8jOAhME61lDk2YfrcJ8oijpmY
WYfF1ppZU/d3pjtnQTnGyw2N+GRYdf61yt9xwQQ9gXVd8AQ81CZtJMd0YIz2sAYF
funAKQXh3+wGaO4MBtbg5uMA/yi+U/RXdtUbpal4eEbJjm5hZjk=
=qIMF
-END PGP SIGNATURE End Message ---

Bug#917524: initramfs-tools: Upgrade from initramfs-tools package fails

[Jürgen Göricke]

Hello Ben,

I already installed udev 240-2, but the bug in the initramfs-tools package 
still exists.
This is not surprising, because udev was installed a few days ago without any 
errors.
Only by installing the package "initramfs-tools" (version: 0.132: all) the 
installation error occurred.

Can you please check again where exactly the error is?
Thanks a lot!

Below I have listed the packages installed on my system.


$  dpkg -l | grep udev
ii udev 240-2 amd64 /dev/ and hotplug management daemon

$  dpkg -l | grep initramfs-tools
iF initramfs-tools 0.132 all generic modular initramfs generator (automation)

Best regards


Jürgen


pgpFecJ1zSvNN.pgp
Description: Digitale Signatur von OpenPGP

Bug#917497: Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

[gregor herrmann]

On Sat, 29 Dec 2018 00:25:25 +, Santiago Vila wrote:

> Package: src:libterm-termkey-perl
> Version: 0.16-3
> Severity: serious
> Tags: ftbfs

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

> Test Summary Report
> ---
> t/05flags.t   (Wstat: 11 Tests: 2 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: Bad plan.  You planned 4 tests but ran 2.

Same in #917497.

Both tests fail during build and not during autopkgtests (locally and
on r-b/ci.debian.net).

After thinking a bit I tried:

#v+
--- a/debian/rules
+++ b/debian/rules
@@ -4,4 +4,4 @@
dh $@

 override_dh_auto_test:
-   TERM=vt100 dh_auto_test
+   TERM=vt100 prove --blib --verbose t/*.t
#v-

(which happens during autopkgtest), and, tataa!, the tests also pass
during build.

So the question is why dh_auto_test fails.


For dh_auto_test we have:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/libterm-termkey-perl-0.16'
TERM=vt100 dh_auto_test
perl Build test --verbose 1


Sticking `TERM=vt100 perl Build test --verbose 1' into debian/rules
also makes the test pass. -- Ok …


So why does dh_auto_test fail? What has changed here? perl?
debhelper? Something else?


From the debhelper changelog:

debhelper (11.5.4) unstable; urgency=medium

  [ Niels Thykier ]
  * Dh_Lib.pm: Reopen stdin to read from /dev/null in doit (and its sibling
functions) to prevent issues when stdin is open in write-only mode
(which is what nohup(1) does).  Thanks to Julian Gilbey for reporting
the issue and providing a sample patch for it as well.
(Closes: #913663)


Can this be related? (The failing test operate on \*STDIN.)
Cc'ing the debhelper bug and debhelper maintainers …


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: Victor Wooten: Me & My Bass Guitar


signature.asc
Description: Digital Signature

Processed: Re: Bug#917600: puppetlabs-ring-middleware-clojure: FTBFS (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #917600 [src:puppetlabs-ring-middleware-clojure] 
puppetlabs-ring-middleware-clojure: FTBFS (failing tests)
Added tag(s) patch.

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

Bug#917600: puppetlabs-ring-middleware-clojure: FTBFS (failing tests)

[Cyril Brulebois]

Control: tag -1 patch

Hi,

Santiago Vila  (2018-12-29):
>   xargs --verbose clojure -cp 
> /<>/puppetlabs-ring-middleware.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/cheshire.jar:/usr/share/java/tools.logging.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/puppetlabs-http-client.jar:/usr/share/java/kitchensink.jar:/usr/share/java/ssl-utils.jar:/usr/share/java/ring-core.jar:/usr/share/java/slingshot.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/trapperkeeper-webserver-jetty9.jar:/usr/share/java/kitchensink-test.jar:/usr/share/java/compojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/tools.macro.jar)
> clojure -cp 
> /<>/puppetlabs-ring-middleware.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/cheshire.jar:/usr/share/java/tools.logging.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/puppetlabs-http-client.jar:/usr/share/java/kitchensink.jar:/usr/share/java/ssl-utils.jar:/usr/share/java/ring-core.jar:/usr/share/java/slingshot.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/trapperkeeper-webserver-jetty9.jar:/usr/share/java/kitchensink-test.jar:/usr/share/java/compojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/tools.macro.jar
>  ./puppetlabs/ring_middleware/core_test.clj 
> ./puppetlabs/ring_middleware/utils_test.clj 
> ./puppetlabs/ring_middleware/testutils/common.clj 
> WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: 
> puppetlabs.kitchensink.core, being replaced by: 
> #'puppetlabs.kitchensink.core/boolean?
> WARNING: uuid? already refers to: #'clojure.core/uuid? in namespace: 
> puppetlabs.kitchensink.core, being replaced by: 
> #'puppetlabs.kitchensink.core/uuid?
> Exception in thread "main" java.io.FileNotFoundException: Could not locate 
> puppetlabs/ring_middleware/testutils/common__init.class or 
> puppetlabs/ring_middleware/testutils/common.clj on classpath. Please check 
> that namespaces with dashes use underscores in the Clojure file name., 
> compiling:(/<>/test/./puppetlabs/ring_middleware/core_test.clj:1:1)
>   at clojure.lang.Compiler.load(Compiler.java:7526)
>   at clojure.lang.Compiler.loadFile(Compiler.java:7452)
>   at clojure.main$load_script.invokeStatic(main.clj:278)
>   at clojure.main$script_opt.invokeStatic(main.clj:338)
>   at clojure.main$script_opt.invoke(main.clj:333)
>   at clojure.main$main.invokeStatic(main.clj:424)
>   at clojure.main$main.doInvoke(main.clj:387)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.lang.Var.applyTo(Var.java:702)
>   at clojure.main.main(main.java:37)
> Caused by: java.io.FileNotFoundException: Could not locate 
> puppetlabs/ring_middleware/testutils/common__init.class or 
> puppetlabs/ring_middleware/testutils/common.clj on classpath. Please check 
> that namespaces with dashes use underscores in the Clojure file name.
>   at clojure.lang.RT.load(RT.java:463)
>   at clojure.lang.RT.load(RT.java:426)
>   at clojure.core$load$fn__9115.invoke(core.clj:6046)
>   at clojure.core$load.invokeStatic(core.clj:6045)
>   at clojure.core$load.doInvoke(core.clj:6029)
>   at clojure.lang.RestFn.invoke(RestFn.java:408)
>   at clojure.core$load_one.invokeStatic(core.clj:5848)
>   at clojure.core$load_one.invoke(core.clj:5843)
>   at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
>   at clojure.core$load_lib.invokeStatic(core.clj:5887)
>   at clojure.core$load_lib.doInvoke(core.clj:5868)
>   at clojure.lang.RestFn.applyTo(RestFn.java:142)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$load_libs.invokeStatic(core.clj:5925)
>   at clojure.core$load_libs.doInvoke(core.clj:5909)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$require.invokeStatic(core.clj:5947)
>   at clojure.core$require.doInvoke(core.clj:5947)
>   at clojure.lang.RestFn.invoke(RestFn.java:2422)
>   at 
> puppetlabs.ring_middleware.core_test$eval2694$loading__9001__auto2695.invoke(core_test.clj:1)
>   at 
> puppetlabs.ring_middleware.core_test$eval2694.invokeStatic(core_test.clj:1)
>   at puppetlabs.ring_middleware.core_test$eval2694.invoke(core_test.clj:1)
>   at clojure.lang.Compiler.eval(Compiler.java:7062)
>   at clojure.lang.Compiler.eval(Compiler.java:7051)
>   at clojure.lang.Compiler.load(Compiler.java:7514)
>   ... 9 more
> make[1]: *** [debian/rules:27: override_dh_auto_test] Error 123
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:12: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 

Please find attached a patch similar to those submitted in #907765,
#880320, #880351. I intend to NMU this package in a 

Bug#917600: puppetlabs-ring-middleware-clojure: FTBFS (failing tests)

[Santiago Vila]

Package: src:puppetlabs-ring-middleware-clojure
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 --with javahelper --with jh_maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
cat debian/header.html > /<>/CHANGELOG.html
sed -i'' -e 's#@TITLE@#1.0.0#g' /<>/CHANGELOG.html
markdown /<>/CHANGELOG.md >> /<>/CHANGELOG.html
cat debian/footer.html >> /<>/CHANGELOG.html
cat debian/header.html > /<>/CONTRIBUTING.html
sed -i'' -e 's#@TITLE@#How to contribute#g' /<>/CONTRIBUTING.html
markdown /<>/CONTRIBUTING.md >> /<>/CONTRIBUTING.html

[... snipped ...]

xargs --verbose clojure -cp 
/<>/puppetlabs-ring-middleware.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/cheshire.jar:/usr/share/java/tools.logging.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/puppetlabs-http-client.jar:/usr/share/java/kitchensink.jar:/usr/share/java/ssl-utils.jar:/usr/share/java/ring-core.jar:/usr/share/java/slingshot.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/trapperkeeper-webserver-jetty9.jar:/usr/share/java/kitchensink-test.jar:/usr/share/java/compojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/tools.macro.jar)
clojure -cp 
/<>/puppetlabs-ring-middleware.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/cheshire.jar:/usr/share/java/tools.logging.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/puppetlabs-http-client.jar:/usr/share/java/kitchensink.jar:/usr/share/java/ssl-utils.jar:/usr/share/java/ring-core.jar:/usr/share/java/slingshot.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/trapperkeeper-webserver-jetty9.jar:/usr/share/java/kitchensink-test.jar:/usr/share/java/compojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/tools.macro.jar
 ./puppetlabs/ring_middleware/core_test.clj 
./puppetlabs/ring_middleware/utils_test.clj 
./puppetlabs/ring_middleware/testutils/common.clj 
WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: 
puppetlabs.kitchensink.core, being replaced by: 
#'puppetlabs.kitchensink.core/boolean?
WARNING: uuid? already refers to: #'clojure.core/uuid? in namespace: 
puppetlabs.kitchensink.core, being replaced by: 
#'puppetlabs.kitchensink.core/uuid?
Exception in thread "main" java.io.FileNotFoundException: Could not locate 
puppetlabs/ring_middleware/testutils/common__init.class or 
puppetlabs/ring_middleware/testutils/common.clj on classpath. Please check that 
namespaces with dashes use underscores in the Clojure file name., 
compiling:(/<>/test/./puppetlabs/ring_middleware/core_test.clj:1:1)
at clojure.lang.Compiler.load(Compiler.java:7526)
at clojure.lang.Compiler.loadFile(Compiler.java:7452)
at clojure.main$load_script.invokeStatic(main.clj:278)
at clojure.main$script_opt.invokeStatic(main.clj:338)
at clojure.main$script_opt.invoke(main.clj:333)
at clojure.main$main.invokeStatic(main.clj:424)
at clojure.main$main.doInvoke(main.clj:387)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.lang.Var.applyTo(Var.java:702)
at clojure.main.main(main.java:37)
Caused by: java.io.FileNotFoundException: Could not locate 
puppetlabs/ring_middleware/testutils/common__init.class or 
puppetlabs/ring_middleware/testutils/common.clj on classpath. Please check that 
namespaces with dashes use underscores in the Clojure file name.
at clojure.lang.RT.load(RT.java:463)
at clojure.lang.RT.load(RT.java:426)
at clojure.core$load$fn__9115.invoke(core.clj:6046)
at clojure.core$load.invokeStatic(core.clj:6045)
at clojure.core$load.doInvoke(core.clj:6029)
at clojure.lang.RestFn.invoke(RestFn.java:408)
at clojure.core$load_one.invokeStatic(core.clj:5848)
at clojure.core$load_one.invoke(core.clj:5843)
at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
at clojure.core$load_lib.invokeStatic(core.clj:5887)
at clojure.core$load_lib.doInvoke(core.clj:5868)
at clojure.lang.RestFn.applyTo(RestFn.java:142)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$load_libs.invokeStatic(core.clj:5925)
at clojure.core$load_libs.doInvoke(core.clj:5909)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$require.invokeStatic(core.clj:5947)
at clojure.core$require.doInvoke(core.clj:5947)
at clojure.lang.RestFn.invoke(RestFn.java:2422)
at 
puppetlabs.ring_middleware.core_test$eval2694$loading__9001__auto2695.invoke(core_test.clj:1)
at 

Processed: Re: Bug#917524: initramfs-tools: Upgrade from initramfs-tools package fails

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 udev
Bug #917524 [initramfs-tools] initramfs-tools: Upgrade from initramfs-tools 
package fails
Bug reassigned from package 'initramfs-tools' to 'udev'.
No longer marked as found in versions initramfs-tools/0.132.
Ignoring request to alter fixed versions of bug #917524 to the same values 
previously set
> forcemerge 917261 -1
Bug #917261 {Done: Michael Biebl } [udev] 
linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing 
/ not created on system startup
Bug #917124 {Done: Michael Biebl } [udev] lvm2 logical 
volumes are not properly initialized
Bug #917136 {Done: Michael Biebl } [udev] udev: LVM volumes 
fail to initialize properly with udev 240-1
Bug #917166 {Done: Michael Biebl } [udev] Errors on and after 
upgrade to 2.03.01-2, swap on lvm not mounted
Bug #917524 [udev] initramfs-tools: Upgrade from initramfs-tools package fails
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/11255'.
Severity set to 'grave' from 'important'
Marked Bug as done
Added indication that 917524 affects lvm2
Marked as fixed in versions systemd/240-2.
Marked as found in versions systemd/240-1.
Bug #917124 {Done: Michael Biebl } [udev] lvm2 logical 
volumes are not properly initialized
Bug #917136 {Done: Michael Biebl } [udev] udev: LVM volumes 
fail to initialize properly with udev 240-1
Bug #917166 {Done: Michael Biebl } [udev] Errors on and after 
upgrade to 2.03.01-2, swap on lvm not mounted
Merged 917124 917136 917166 917261 917524

-- 
917124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917124
917136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917136
917166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917166
917261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917261
917524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#880320: ssl-utils-clojure: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #880320 [src:ssl-utils-clojure] ssl-utils-clojure: FTBFS: Test failures
Added tag(s) patch.

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

Bug#880320: ssl-utils-clojure: FTBFS: Test failures

[Cyril Brulebois]

Control: tag -1 patch

Cyril Brulebois  (2018-12-29):
> Reopening as I was finally able to reproduce this issue on a test
> machine kindly provided by Santiago[1], but also locally by adding a
> “| sort -R” call after the “find” one in override_dh_auto_test and
> trying a build a few times.
> 
>  1. https://bugs.debian.org/907765#15
> 
> I've checked that using “sort” or “sort -r” both give positive results,
> and I'll propose a patch encoding one of the known-good sequence, as
> already done in other packages[2,3].
> 
>  2. https://bugs.debian.org/907765#25
>  3. https://bugs.debian.org/880351#19

[…]

> I intend to NMU this package in a few days, like the other ones.

You'll find attached the prospective patch.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru ssl-utils-clojure-0.8.3/debian/changelog ssl-utils-clojure-0.8.3/debian/changelog
--- ssl-utils-clojure-0.8.3/debian/changelog	2017-08-05 17:17:48.0 +
+++ ssl-utils-clojure-0.8.3/debian/changelog	2018-12-29 00:54:20.0 +
@@ -1,3 +1,13 @@
+ssl-utils-clojure (0.8.3-2) UNRELEASED; urgency=medium
+
+  * Fix FTBFS by running tests in a specific order. Instead of blindly
+sorting the results of the find command and trusting it to be right,
+encode a suitable sequence of tests (Closes: #880320). Also make sure
+to error out when tests are added or removed, to make sure this
+sequence get refreshed when needed.
+
+ -- Cyril Brulebois   Sat, 29 Dec 2018 00:54:20 +
+
 ssl-utils-clojure (0.8.3-1) unstable; urgency=medium
 
   * Initial release (Closes: #855740)
diff -Nru ssl-utils-clojure-0.8.3/debian/rules ssl-utils-clojure-0.8.3/debian/rules
--- ssl-utils-clojure-0.8.3/debian/rules	2017-08-05 17:17:48.0 +
+++ ssl-utils-clojure-0.8.3/debian/rules	2018-12-29 00:54:02.0 +
@@ -24,10 +24,21 @@
 	rm -f $(CURDIR)/$(PRODUCED_JAR)
 	rm -rf $(CURDIR)/doc/html
 
+# Tests can't run in a random order (#880320):
+override_dh_auto_test: ORDERED_TESTS=puppetlabs/ssl_utils/core_test.clj puppetlabs/ssl_utils/extensions_utils_test.clj puppetlabs/ssl_utils/simple_test.clj
+override_dh_auto_test: EXPECTED=$(shell echo "$(ORDERED_TESTS)" | sed 's/ /\n/g' | sort | xargs)
+override_dh_auto_test: FOUND=$(shell cd test && find -name '*.clj' | sed 's,^[.]/,,' | sort | xargs)
 override_dh_auto_test:
-	dh_auto_test
-	(cd test && find . -name "*_test.clj" | \
-		xargs --verbose clojure -cp $(CURDIR)/$(PRODUCED_JAR):$(CLASSPATH):$(TEST_CLASSPATH))
+	# Make sure to detect when tests appear or disappear:
+	@if [ "$(FOUND)" != "$(EXPECTED)" ]; then \
+		echo "E: sanity check failed, available tests don't match known tests:"; \
+		echo "- found:$(FOUND)"; \
+		echo "- expected: $(EXPECTED)"; \
+		echo "=> Please update ORDERED_TESTS in debian/rules accordingly"; \
+		exit 1; \
+	fi
+	# Run tests:
+	(cd test && clojure -cp $(CURDIR)/$(PRODUCED_JAR):$(CLASSPATH):$(TEST_CLASSPATH) $(ORDERED_TESTS))
 
 get-orig-source:
 	uscan --download-version $(DEB_VERSION_UPSTREAM) --force-download --rename


signature.asc
Description: PGP signature

Processed: Re: Bug#880320: ssl-utils-clojure: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #880320 {Done: Cyril Brulebois } [src:ssl-utils-clojure] 
ssl-utils-clojure: FTBFS: Test failures
Bug reopened
Ignoring request to alter fixed versions of bug #880320 to the same values 
previously set
> found -1 0.8.3-1
Bug #880320 [src:ssl-utils-clojure] ssl-utils-clojure: FTBFS: Test failures
Ignoring request to alter found versions of bug #880320 to the same values 
previously set

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

Bug#880320: ssl-utils-clojure: FTBFS: Test failures

[Cyril Brulebois]

Control: reopen -1
Control: found -1 0.8.3-1

Cyril Brulebois  (2018-12-28):
> > Relevant part (hopefully):
> > >   at clojure.core$load_libs.invokeStatic(core.clj:5775)
> > >   at clojure.core$load_libs.doInvoke(core.clj:5758)
> > >   at clojure.lang.RestFn.applyTo(RestFn.java:137)
> > >   at clojure.core$apply.invokeStatic(core.clj:648)
> > >   at clojure.core$apply.invoke(core.clj:641)
> > >   at clojure.core$require.invokeStatic(core.clj:5858)
> > >   at clojure.core$require.doInvoke(core.clj:5796)
> > >   at clojure.lang.RestFn.invoke(RestFn.java:457)
> > >   at 
> > > puppetlabs.ssl_utils.extensions_utils_test$eval4329$loading__1497__auto4330.invoke(extensions_utils_test.clj:1)
> > >   at 
> > > puppetlabs.ssl_utils.extensions_utils_test$eval4329.invokeStatic(extensions_utils_test.clj:1)
> > >   at 
> > > puppetlabs.ssl_utils.extensions_utils_test$eval4329.invoke(extensions_utils_test.clj:1)
> > >   at clojure.lang.Compiler.eval(Compiler.java:6927)
> > >   at clojure.lang.Compiler.eval(Compiler.java:6916)
> > >   at clojure.lang.Compiler.load(Compiler.java:7379)
> > >   ... 12 more
> > > debian/rules:28: recipe for target 'override_dh_auto_test' failed

[…]

> I can't reproduce this issue in sid today, so I'm closing this bug
> report for the time being. Feel free to cc me, should this FTBFS
> be reproducible on your side.

Reopening as I was finally able to reproduce this issue on a test
machine kindly provided by Santiago[1], but also locally by adding a
“| sort -R” call after the “find” one in override_dh_auto_test and
trying a build a few times.

 1. https://bugs.debian.org/907765#15

I've checked that using “sort” or “sort -r” both give positive results,
and I'll propose a patch encoding one of the known-good sequence, as
already done in other packages[2,3].

 2. https://bugs.debian.org/907765#25
 3. https://bugs.debian.org/880351#19

(This package and a few others migrated to testing while this RC bug
was closed, but they'll get kicked out again if this bug doesn't get
resolved.)

I intend to NMU this package in a few days, like the other ones.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#916673: mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed

[Steinar H. Gunderson]

On Mon, Dec 17, 2018 at 10:57:44AM +0200, Adrian Bunk wrote:
> Package: mandos
> Version: 1.7.20-1
> Severity: serious
> 
> The following packages have unmet dependencies:
>  mandos : Depends: libgnutls28-dev (< 3.6.0) but 3.6.5-2 is to be installed or
>libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed
> 
> 
> Additionally, the libgnutls28-dev alternative of the dependencies
> looks wrong - this should likely just be libgnutls30.

The reason for the -dev dependency appears to be that the Python code does
something like

  from ctypes.util import find_library
  find_library('gnutls')

but that works just fine even without the -dev package installed (so either
libgnutls28 or libgnutls30 ought to do).

Actually, I wonder if using ${shlibs:Depends} would be fine, even for the
Python code. At least it would make transitioning this package much easier. :-)
Or move back to using python-gnutls; NEWS indicates that ctypes was used
because python-gnutls didn't support GnuTLS 3.3 at the time, but
python-gnutls indicates it has supported GnuTLS 3.4 since 2016.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Processed: Re: Bug#904363: python3-applicationinsights: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +ftbfs
Bug #904363 [python3-applicationinsights] python3-applicationinsights: fails to 
install with Python 3.7
Added tag(s) ftbfs.

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

Bug#917598: petsc4py FTBFS error: ‘SNESTEST’ undeclared

[peter green]

package: petsc4py
version: 3.10.0-2
severity: serious

While trying to get the petsc/slepc/etc stack in raspbian buster into a 
consistent state I ran into the following error with petsc4py. I was also able 
to reproduce this in a Debian sid amd64 environment, so it's not raspbian 
specific.

mpicc -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DPETSC_DIR=/usr/lib/petscdir/petsc3.10/arm-linux-gnueabihf-real 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi -I/usr/include/hypre 
-I/usr/include/superlu-dist -I/usr/include/superlu -I/usr/include/suitesparse 
-I/usr/lib/petscdir/petsc3.10/arm-linux-gnueabihf-real/include -Isrc/include 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 -c 
src/PETSc.c -o build/temp.linux-armhf-2.7/src/PETSc.o
In file included from src/PETSc.c:4:
src/petsc4py.PETSc.c: In function 'initPETSc':
src/petsc4py.PETSc.c:284319:43: error: 'SNESTEST' undeclared (first use in this 
function); did you mean 'SNESType'?
   __pyx_t_7 = __pyx_f_8petsc4py_5PETSc_S_(SNESTEST); if (unlikely(!__pyx_t_7)) 
__PYX_ERR(37, 7, __pyx_L1_error)
   ^~~~
   SNESType
src/petsc4py.PETSc.c:284319:43: note: each undeclared identifier is reported 
only once for each function it appears in
error: command 'mpicc' failed with exit status 1

Searching for SNESTEST on codesearch.debian.net reveals the following in the 
dolfin changelog.

  * create patch PETSc_3.10_SNESTEST_removed.patch to work with
*PETSc 3.10 (SNESTEST has been removed). Thanks Jed Brown. Presumablly a 
similar fix is needed in petsc4py. *

Bug#880351: trapperkeeper-status-clojure: FTBFS: Test failures

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2018-12-28):
> It was a bit curious at first since I couldn't reproduce it in my sid
> amd64 devel chroot, but could in my sid amd64 sbuild chroot… Checking
> strace's output, it seemed like it might be that some leftover from a
> previous test might have been missing:
> 
> […]/test/./target/empty.ini
> 
> so I've tried sorting the tests to run, and I've got a reproducible
> success, both inside devel & sbuild chroots.

Based on slightly different results in #907765 (where order matters but
natural sorting doesn't work[1]), I've decided to propose a different
patch: I've chosen to encode a sequence of tests that makes the test
suite run OK. This way, it should be obvious when new tests are added,
so that one can find and document a suitable sequence of tests.

 1. https://bugs.debian.org/907765#25


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru trapperkeeper-status-clojure-0.7.1/debian/changelog trapperkeeper-status-clojure-0.7.1/debian/changelog
--- trapperkeeper-status-clojure-0.7.1/debian/changelog	2017-08-05 22:05:17.0 +
+++ trapperkeeper-status-clojure-0.7.1/debian/changelog	2018-12-29 00:14:15.0 +
@@ -1,3 +1,13 @@
+trapperkeeper-status-clojure (0.7.1-2) UNRELEASED; urgency=medium
+
+  * Fix FTBFS by running tests in a specific order. Instead of blindly
+sorting the results of the find command and trusting it to be right,
+encode a suitable sequence of tests (Closes: #880351). Also make sure
+to error out when tests are added or removed, to make sure this
+sequence get refreshed when needed.
+
+ -- Cyril Brulebois   Sat, 29 Dec 2018 00:14:15 +
+
 trapperkeeper-status-clojure (0.7.1-1) unstable; urgency=medium
 
   * Initial release (Closes: #855744)
diff -Nru trapperkeeper-status-clojure-0.7.1/debian/rules trapperkeeper-status-clojure-0.7.1/debian/rules
--- trapperkeeper-status-clojure-0.7.1/debian/rules	2017-08-05 22:05:17.0 +
+++ trapperkeeper-status-clojure-0.7.1/debian/rules	2018-12-29 00:13:56.0 +
@@ -40,6 +40,18 @@
 	markdown $< >> $@
 	cat debian/footer.html >> $@
 
+# Tests can't run in a random order (#880351):
+override_dh_auto_test: ORDERED_TESTS=puppetlabs/trapperkeeper/services/status/check_test.clj puppetlabs/trapperkeeper/services/status/status_core_test.clj puppetlabs/trapperkeeper/services/status/status_proxy_service_test.clj puppetlabs/trapperkeeper/services/status/status_service_test.clj
+override_dh_auto_test: EXPECTED=$(shell echo "$(ORDERED_TESTS)" | sed 's/ /\n/g' | sort | xargs)
+override_dh_auto_test: FOUND=$(shell cd test && find -name '*.clj' | sed 's,^[.]/,,' | sort | xargs)
 override_dh_auto_test:
-	(cd test && find . -name "*.clj" | \
-		xargs --verbose clojure -cp $(CURDIR)/$(PRODUCED_JAR):$(CLASSPATH):$(TEST_CLASSPATH))
+	# Make sure to detect when tests appear or disappear:
+	@if [ "$(FOUND)" != "$(EXPECTED)" ]; then \
+		echo "E: sanity check failed, available tests don't match known tests:"; \
+		echo "- found:$(FOUND)"; \
+		echo "- expected: $(EXPECTED)"; \
+		echo "=> Please update ORDERED_TESTS in debian/rules accordingly"; \
+		exit 1; \
+	fi
+	# Run tests:
+	(cd test && clojure -cp $(CURDIR)/$(PRODUCED_JAR):$(CLASSPATH):$(TEST_CLASSPATH) $(ORDERED_TESTS))


signature.asc
Description: PGP signature

Bug#904363: python3-applicationinsights: fails to install with Python 3.7

[Steve McIntyre]

Control: tag -1 +ftbfs

This same problem also makes the package FTBFS:

...
  File 
"/build/python-applicationinsights-0.11.0/applicationinsights/channel/contracts/__init__.py",
 line 7, in 
from .RemoteDependencyData import RemoteDependencyData
  File 
"/build/python-applicationinsights-0.11.0/applicationinsights/channel/contracts/RemoteDependencyData.py",
 line 256
def async(self):
^
SyntaxError: invalid syntax
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:6: build] Error 25
...

On Mon, Jul 23, 2018 at 04:32:16PM +0200, Andreas Beckmann wrote:
>Package: python3-applicationinsights
>Version: 0.11.0-1
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts
>Control: block 902788 with -1 
>
>Hi,
>
>during a test with piuparts I noticed your package failed to install. As
>per definition of the release team this makes the package too buggy for
>a release, thus the severity.
>
>From the attached log (scroll to the bottom...):
>
>  Setting up python3-applicationinsights (0.11.0-1) ...
>File 
> "/usr/lib/python3/dist-packages/applicationinsights/channel/contracts/RemoteDependencyData.py",
>  line 256
>  def async(self):
>  ^
>  SyntaxError: invalid syntax
>  
>  dpkg: error processing package python3-applicationinsights (--configure):
>   installed python3-applicationinsights package post-installation script 
> subprocess returned error exit status 1
>
>
>"async" has become a reserved keyword in Python 3.7
>
>
>cheers,
>
>Andreas


-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra

Bug#917597: FTBFS: test failures

[Steve McIntyre]

Package: src:pytest-qt
Version: 2.3.1-2
Severity: serious
Tags: ftbfs
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.

While doing that, I've found that pytest-qt fails multiple tests in
its testsuite. I've tested further and I can reproduce the same thing
in a normal amd64 build too, so it's not an architecture-specific
problem.

...
tests/test_basics.py [ 10%]
tests/test_exceptions.py .   [ 14%]
tests/test_logging.py ...F.  [ 23%]
tests/test_modeltest.py .[ 33%]
tests/test_qtest_proxies.py ..x. [ 36%]
tests/test_wait_signal.py .. [ 51%]
 [ 74%]
..s...ss [ 97%]
.[ 98%]
tests/test_wait_until.py ..  [100%]

=== FAILURES ===
___ test_logging_mark_with_invalid_argument 

testdir = 

def test_logging_mark_with_invalid_argument(testdir):
"""
Test qt_log_ignore mark with invalid keyword argument.

:type testdir: _pytest.pytester.TmpTestdir
"""
testdir.makepyfile(
"""
import pytest

@pytest.mark.qt_log_ignore('match-mark', does_not_exist=True)
def test1():
pass
"""
)
res = testdir.runpytest()
lines = [
'*= ERRORS =*',
'*_ ERROR at setup of test1 _*',
"*ValueError: Invalid keyword arguments in {'does_not_exist': True} 
"
"for qt_log_ignore mark.",

# summary
'*= 1 error in*',
]
>   res.stdout.fnmatch_lines(lines)
E   Failed: nomatch: '*= ERRORS =*'
E   and: '= test session starts 
=='
E   and: '= test session starts 
=='
E   and: 'platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, 
pluggy-0.8.0'
E   and: 'PyQtAPI 1.0 -- Qt runtime 2.5 -- Qt compiled 3.5'
E   and: 'rootdir: 
/tmp/pytest-of-sbuild/pytest-0/test_logging_mark_with_invalid_argument0, 
inifile:'
E   and: 'plugins: qt-2.3.1'
E   and: 'collected 1 item'
E   and: ''
E   and: 'test_logging_mark_with_invalid_argument.py E  
   [100%]'
E   and: ''
E   fnmatch: '*= ERRORS =*'
E  with: ' ERRORS 
'
E   fnmatch: '*_ ERROR at setup of test1 _*'
E  with: '___ ERROR at setup of test1 
'
E   nomatch: "*ValueError: Invalid keyword arguments in {'does_not_exist': 
True} for qt_log_ignore mark."
E   and: ''
E   and: 'self = '
E   and: "item = "
E   and: ''
E   and: 'def pytest_runtest_setup(self, item):'
E   and: "if item.get_marker('no_qt_log'):"
E   and: 'return'
E   and: "m = item.get_marker('qt_log_ignore')"
E   and: 'if m:'
E   and: "if not set(m.kwargs).issubset(set(['extend'])):"
E   and: 'raise ValueError("Invalid keyword arguments 
in {0!r} for "'
E   and: '>"qt_log_ignore 
mark.".format(m.kwargs))'
E   fnmatch: "*ValueError: Invalid keyword arguments in {'does_not_exist': 
True} for qt_log_ignore mark."
E  with: "E   ValueError: Invalid keyword arguments in 
{'does_not_exist': True} for qt_log_ignore mark."
E   nomatch: '*= 1 error in*'
E   and: ''
E   and: 
'/<>/.pybuild/cpython3_3.7_pytestqt/build/pytestqt/logging.py:28: 
ValueError'
E   and: '=== warnings summary 
==='
E   and: 'test_logging_mark_with_invalid_argument.py::test1'
E   and: '  
/<>/.pybuild/cpython3_3.7_pytestqt/build/pytestqt/logging.py:26: 
RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged 
marks which are hard to deal with correctly.'
E   and: '  Please use 

Bug#917595: umoci: FTBFS (cannot find package "github.com/fatih/color")

[Santiago Vila]

Package: src:umoci
Version: 0.4.0+dfsg-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 --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_autoreconf -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/umoci-0.4.0+dfsg'
COMMIT=1 COMMIT_NO=1 /usr/bin/make doc
make[2]: Entering directory '/<>/umoci-0.4.0+dfsg'
go-md2man -in doc/man/umoci-unpack.1.md -out doc/man/umoci-unpack.1
go-md2man -in doc/man/umoci-raw-runtime-config.1.md -out 
doc/man/umoci-raw-runtime-config.1
go-md2man -in doc/man/umoci-config.1.md -out doc/man/umoci-config.1
go-md2man -in doc/man/umoci-ls.1.md -out doc/man/umoci-ls.1
go-md2man -in doc/man/umoci-remove.1.md -out doc/man/umoci-remove.1

[... snipped ...]

src/github.com/openSUSE/umoci/oci/config/generate/save.go
src/github.com/openSUSE/umoci/oci/config/generate/spec.go
src/github.com/openSUSE/umoci/oci/config/generate/spec_test.go
src/github.com/openSUSE/umoci/oci/layer/generate.go
src/github.com/openSUSE/umoci/oci/layer/generate_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_extract.go
src/github.com/openSUSE/umoci/oci/layer/tar_extract_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_generate.go
src/github.com/openSUSE/umoci/oci/layer/tar_generate_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_unix.go
src/github.com/openSUSE/umoci/oci/layer/unpack.go
src/github.com/openSUSE/umoci/oci/layer/unpack_test.go
src/github.com/openSUSE/umoci/oci/layer/utils.go
src/github.com/openSUSE/umoci/oci/layer/utils_test.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval_default.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval_rootless.go
src/github.com/openSUSE/umoci/pkg/idtools/idtools.go
src/github.com/openSUSE/umoci/pkg/idtools/idtools_test.go
src/github.com/openSUSE/umoci/pkg/mtreefilter/mask.go
src/github.com/openSUSE/umoci/pkg/mtreefilter/mask_test.go
src/github.com/openSUSE/umoci/pkg/rootlesscontainers-proto/rootlesscontainers_generate.go
src/github.com/openSUSE/umoci/pkg/system/mknod_linux.go
src/github.com/openSUSE/umoci/pkg/system/mknod_linux_test.go
src/github.com/openSUSE/umoci/pkg/system/utime_linux.go
src/github.com/openSUSE/umoci/pkg/system/utime_linux_test.go
src/github.com/openSUSE/umoci/pkg/system/xattr_linux.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv_test.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv_utimes_test.go
src/github.com/openSUSE/umoci/third_party/shared/util.go
src/github.com/openSUSE/umoci/third_party/user/lookup.go
src/github.com/openSUSE/umoci/third_party/user/lookup_unix.go
src/github.com/openSUSE/umoci/third_party/user/user.go
src/github.com/openSUSE/umoci/third_party/user/user_test.go
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/openSUSE/umoci/cmd/umoci github.com/openSUSE/umoci/mutate 
github.com/openSUSE/umoci/oci/cas github.com/openSUSE/umoci/oci/cas/dir 
github.com/openSUSE/umoci/oci/casext 
github.com/openSUSE/umoci/oci/config/convert 
github.com/openSUSE/umoci/oci/config/generate 
github.com/openSUSE/umoci/oci/layer github.com/openSUSE/umoci/pkg/fseval 
github.com/openSUSE/umoci/pkg/idtools github.com/openSUSE/umoci/pkg/mtreefilter 
github.com/openSUSE/umoci/pkg/rootlesscontainers-proto 
github.com/openSUSE/umoci/pkg/system github.com/openSUSE/umoci/pkg/unpriv 
github.com/openSUSE/umoci/third_party/shared 
github.com/openSUSE/umoci/third_party/user
src/github.com/apex/log/handlers/cli/cli.go:12:2: cannot find package 
"github.com/fatih/color" in any of:
/usr/lib/go-1.10/src/github.com/fatih/color (from $GOROOT)

/<>/umoci-0.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/fatih/color 
(from $GOPATH)
src/github.com/apex/log/handlers/cli/cli.go:13:2: cannot find package 
"github.com/mattn/go-colorable" in any of:
/usr/lib/go-1.10/src/github.com/mattn/go-colorable (from $GOROOT)

/<>/umoci-0.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/mattn/go-colorable
 (from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/openSUSE/umoci/cmd/umoci github.com/openSUSE/umoci/mutate 
github.com/openSUSE/umoci/oci/cas github.com/openSUSE/umoci/oci/cas/dir 
github.com/openSUSE/umoci/oci/casext 
github.com/openSUSE/umoci/oci/config/convert 
github.com/openSUSE/umoci/oci/config/generate 
github.com/openSUSE/umoci/oci/layer github.com/openSUSE/umoci/pkg/fseval 

Bug#917591: libbpp-seq-omics: FTBFS (dh_makeshlibs fails)

[Santiago Vila]

Package: src:libbpp-seq-omics
Version: 2.4.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
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
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 ..
-- 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
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- bpp-core 4.1.0 found:

[... snipped ...]

  _ZNK3bpp13AlphabetState5cloneEv@Base 2.4.1
  _ZNK3bpp13CodonAlphabet23getUnknownCharacterCodeEv@Base 2.4.1
  
_ZNK3bpp14LetterAlphabet16isCharInAlphabetERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
@@ -991,9 +991,9 @@
  
_ZThn8_N3bpp22SequenceWithAnnotation10setContentERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
 2.4.1
  _ZThn8_N3bpp22SequenceWithAnnotation10setContentERKSt6vectorIiSaIiEE@Base 
2.4.1
  _ZTv0_n112_NK3bpp23VectorSequenceContainer20getNumberOfSequencesEv@Base 2.4.1
- _ZTv0_n144_NK3bpp12SequenceMask7getTypeB5cxx11Ev@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTv0_n144_NK3bpp12SequenceMask7getTypeB5cxx11Ev@Base 2.4.1
  _ZTv0_n144_NK3bpp15SequenceQuality7getTypeB5cxx11Ev@Base 2.4.1
- 
_ZTv0_n152_NK3bpp12SequenceMask11isValidWithERKNS_22SequenceWithAnnotationEb@Base
 2.4.1
+#MISSING: 2.4.1-1# 
_ZTv0_n152_NK3bpp12SequenceMask11isValidWithERKNS_22SequenceWithAnnotationEb@Base
 2.4.1
  
_ZTv0_n152_NK3bpp15SequenceQuality11isValidWithERKNS_22SequenceWithAnnotationEb@Base
 2.4.1
  _ZTv0_n168_NK3bpp12EdSymbolListixEm@Base 2.4.1
  _ZTv0_n168_NK3bpp15BasicSymbolListixEm@Base 2.4.1
@@ -1003,7 +1003,7 @@
  _ZTv0_n24_N3bpp10BppIntegerD1Ev@Base 2.4.1
  _ZTv0_n24_N3bpp11MafSequenceD0Ev@Base 2.4.1
  _ZTv0_n24_N3bpp11MafSequenceD1Ev@Base 2.4.1
- _ZTv0_n24_N3bpp12SequenceMaskD0Ev@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTv0_n24_N3bpp12SequenceMaskD0Ev@Base 2.4.1
  _ZTv0_n24_N3bpp13AlphabetStateD0Ev@Base 2.4.1
  _ZTv0_n24_N3bpp13AlphabetStateD1Ev@Base 2.4.1
  _ZTv0_n24_N3bpp13BasicSequenceD0Ev@Base 2.4.1
@@ -1142,7 +1142,7 @@
  
_ZTv0_n48_N3bpp25SimpleMafStatisticsResult8setValueERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base
 2.4.1
  _ZTv0_n48_N3bpp36CsvStatisticsOutputIterationListener14iterationStopsEv@Base 
2.4.1
  _ZTv0_n48_NK3bpp12EdSymbolList11getAlphabetEv@Base 2.4.1
- _ZTv0_n48_NK3bpp12SequenceMask11isRemovableEv@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTv0_n48_NK3bpp12SequenceMask11isRemovableEv@Base 2.4.1
  _ZTv0_n48_NK3bpp15SequenceQuality11isRemovableEv@Base 2.4.1
  _ZTv0_n48_NK3bpp21AbstractMafStatistics9getResultEv@Base 2.4.1
  _ZTv0_n48_NK3bpp22SequenceWithAnnotation7getNameB5cxx11Ev@Base 2.4.1
@@ -1162,7 +1162,7 @@
  
_ZTv0_n56_N3bpp34SiteFrequencySpectrumMafStatistics7computeERKNS_8MafBlockE@Base
 2.4.1
  
_ZTv0_n56_N3bpp37FourSpeciesPatternCountsMafStatistics7computeERKNS_8MafBlockE@Base
 2.4.1
  _ZTv0_n56_NK3bpp12EdSymbolList4sizeEv@Base 2.4.1
- _ZTv0_n56_NK3bpp12SequenceMask8isSharedEv@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTv0_n56_NK3bpp12SequenceMask8isSharedEv@Base 2.4.1
  _ZTv0_n56_NK3bpp15BasicSymbolList4sizeEv@Base 2.4.1
  _ZTv0_n56_NK3bpp15SequenceQuality8isSharedEv@Base 2.4.1
  
_ZTv0_n64_N3bpp16GffFeatureReader21getFeaturesOfSequenceERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base
 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbpp-seq-omics.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#917592: libterm-termkey-perl: FTBFS (failing tests)

[Santiago Vila]

Package: src:libterm-termkey-perl
Version: 0.16-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
   dh_update_autotools_config -a
   dh_auto_configure -a
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Use of uninitialized value $cflags in split at Build.PL line 42.
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Term-TermKey' version '0.16'
   dh_auto_build -a
perl Build
Building Term-TermKey
x86_64-linux-gnu-gcc -I/usr/lib/x86_64-linux-gnu/perl/5.28/CORE 
-DVERSION="0.16" -DXS_VERSION="0.16" -fPIC -c -D_REENTRANT -D_GNU_SOURCE 
-DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o lib/Term/TermKey.o lib/Term/TermKey.c
lib/Term/TermKey.xs: In function 'XS_Term__TermKey_set_buffer_size':
lib/Term/TermKey.xs:525:13: warning: too many arguments for format 
[-Wformat-extra-args]

[... snipped ...]

ok 6 - $key->col after mouse press
ok
t/07position.t .. 
1..4
ok 1 - getkey yields RES_KEY after cursor position report
ok 2 - $key->type_is_position after cursor position report
ok 3 - $key->line after cursor position report
ok 4 - $key->col after cursor position report
ok
t/08modereport.t  
1..10
ok 1 - getkey yields RES_KEY after ANSI mode report
ok 2 - $key->type_is_modereport after ANSI mode report
ok 3 - $key->initial after ANSI mode report
ok 4 - $key->mode after ANSI mode report
ok 5 - $key->value after ANSI mode report
ok 6 - getkey yields RES_KEY after DEC mode report
ok 7 - $key->type_is_modereport after DEC mode report
ok 8 - $key->initial after DEC mode report
ok 9 - $key->mode after DEC mode report
ok 10 - $key->value after DEC mode report
ok
t/09unknown_csi.t ... 
1..7
ok 1 - getkey yields RES_KEY after unrecognised CSI > v
ok 2 - $key->type_is_unknown_csi after unrecognised CSI > v
ok 3 - $cmd for unrecognised CSI > v
ok 4 - @args for unrecognised CSI > v
ok 5 - getkey yields RES_KEY after unrecognised CSI ? Sp w
ok 6 - $cmd for unrecognised CSI ? Sp w
ok 7 - @args for unrecognised CSI ? Sp w
ok
t/99pod.t ... skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
---
t/05flags.t   (Wstat: 11 Tests: 2 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 4 tests but ran 2.
Files=11, Tests=100,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.50 cusr  0.04 
csys =  0.58 CPU)
Result: FAIL
Failed 1/11 test programs. 0/100 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libterm-termkey-perl.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#917594: sparse: FTBFS (failing tests)

[Santiago Vila]

Package: src:sparse
Version: 0.5.2-2
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
   dh_auto_configure -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- SPARSE_VERSION="\$(VERSION) (Debian: 0.5.2-2)" PREFIX=/usr 
PKGCONFIGDIR=/usr/lib/x86_64-linux-gnu/pkgconfig V=1
make -j1 "SPARSE_VERSION=\$(VERSION) (Debian: 0.5.2-2)" PREFIX=/usr 
PKGCONFIGDIR=/usr/lib/x86_64-linux-gnu/pkgconfig V=1
make[2]: Entering directory '/<>'
gcc-8 -o test-lexing.o -c -O2 -finline-functions -fno-strict-aliasing -g -Wall 
-Wwrite-strings -DGCC_BASE=\"/usr/lib/gcc/x86_64-linux-gnu/8/\" 
-DMULTIARCH_TRIPLET=\"x86_64-linux-gnu\" -Wp,-MD,./.test-lexing.o.d  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 test-lexing.c
gcc-8 -o target.o -c -O2 -finline-functions -fno-strict-aliasing -g -Wall 
-Wwrite-strings -DGCC_BASE=\"/usr/lib/gcc/x86_64-linux-gnu/8/\" 
-DMULTIARCH_TRIPLET=\"x86_64-linux-gnu\" -Wp,-MD,./.target.o.d  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 target.c
gcc-8 -o parse.o -c -O2 -finline-functions -fno-strict-aliasing -g -Wall 
-Wwrite-strings -DGCC_BASE=\"/usr/lib/gcc/x86_64-linux-gnu/8/\" 
-DMULTIARCH_TRIPLET=\"x86_64-linux-gnu\" -Wp,-MD,./.parse.o.d  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 parse.c
gcc-8 -o tokenize.o -c -O2 -finline-functions -fno-strict-aliasing -g -Wall 
-Wwrite-strings -DGCC_BASE=\"/usr/lib/gcc/x86_64-linux-gnu/8/\" 
-DMULTIARCH_TRIPLET=\"x86_64-linux-gnu\" -Wp,-MD,./.tokenize.o.d  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 tokenize.c

[... snipped ...]

error: actual error text does not match expected error text.
error: see typeof-noderef.c.error.* for further investigation.
--- typeof-noderef.c.error.expected 2018-12-26 21:08:15.289676014 +
+++ typeof-noderef.c.error.got  2018-12-26 21:08:15.289676014 +
@@ -0,0 +1,6 @@
+typeof-noderef.c:7:30: warning: incorrect type in initializer (different 
modifiers)
+typeof-noderef.c:7:30:expected int *ptr3
+typeof-noderef.c:7:30:got int [noderef] *ptr
+typeof-noderef.c:8:29: warning: incorrect type in initializer (different 
modifiers)
+typeof-noderef.c:8:29:expected int *ptr4
+typeof-noderef.c:8:29:got int [noderef] *ptr
info: test 'typeof-noderef.c' is known to fail
 TESTtypeof-safe (typeof-safe.c)
Using command   : ../sparse typeof-safe.c
Expecting exit value: 0
error: actual error text does not match expected error text.
error: see typeof-safe.c.error.* for further investigation.
--- typeof-safe.c.error.expected2018-12-26 21:08:15.297675854 +
+++ typeof-safe.c.error.got 2018-12-26 21:08:15.297675854 +
@@ -0,0 +1,9 @@
+typeof-safe.c:9:30: warning: incorrect type in initializer (different 
modifiers)
+typeof-safe.c:9:30:expected int *ptr3
+typeof-safe.c:9:30:got int [safe] *ptr
+typeof-safe.c:10:29: warning: incorrect type in initializer (different 
modifiers)
+typeof-safe.c:10:29:expected int *ptr4
+typeof-safe.c:10:29:got int [safe] *ptr
+typeof-safe.c:13:13: warning: incorrect type in assignment (different 
modifiers)
+typeof-safe.c:13:13:expected int [safe] *[assigned] ptr
+typeof-safe.c:13:13:got int *
info: test 'typeof-safe.c' is known to fail
 TEST-Wtypesign (typesign.c)
Using command   : ../sparse -Wtypesign typesign.c
Expecting exit value: 0
 TESTVarargs bogus warning regression test #1 (varargs1.c)
Using command   : ../sparse varargs1.c
Expecting exit value: 0
 TESTwide character constants (wide.c)
Using command   : ../sparse wide.c
Expecting exit value: 0
Out of 288 tests, 277 passed, 11 failed (10 of them are known to fail)
make[2]: *** [Makefile:242: check] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check "SPARSE_VERSION=\$(VERSION) (Debian: 0.5.2-2)" 
PREFIX=/usr PKGCONFIGDIR=/usr/lib/x86_64-linux-gnu/pkgconfig V=1 returned exit 
code 2
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


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

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

where you can get a full 

Bug#917596: vuls: FTBFS

[Santiago Vila]

Package: src:vuls
Version: 0.4.2+git20180531.0.399a087-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 --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   dh_auto_build -a -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/future-architect/vuls 
github.com/future-architect/vuls/cache 
github.com/future-architect/vuls/commands 
github.com/future-architect/vuls/config 
github.com/future-architect/vuls/contrib/owasp-dependency-check/parser 
github.com/future-architect/vuls/models github.com/future-architect/vuls/oval 
github.com/future-architect/vuls/report github.com/future-architect/vuls/scan 
github.com/future-architect/vuls/util
errors
internal/race
runtime/internal/atomic
runtime/internal/sys
runtime
sync/atomic
sync
io

[... snipped ...]

github.com/aws/aws-sdk-go/service/sts
github.com/aws/aws-sdk-go/aws/credentials/stscreds
github.com/aws/aws-sdk-go/aws/credentials/endpointcreds
github.com/aws/aws-sdk-go/aws/defaults
github.com/aws/aws-sdk-go/aws/session
github.com/aws/aws-sdk-go/private/protocol/restxml
github.com/aws/aws-sdk-go/service/s3
github.com/google/subcommands
github.com/mattn/go-runewidth
github.com/gosuri/uitable/util/strutil
github.com/gosuri/uitable/util/wordwrap
github.com/gosuri/uitable
os/signal
github.com/nsf/termbox-go
github.com/jroimartin/gocui
github.com/kotakanbe/go-cve-dictionary/log
github.com/kotakanbe/go-cve-dictionary/config
github.com/kotakanbe/go-cve-dictionary/util
gopkg.in/cheggaaa/pb.v1
github.com/kotakanbe/go-cve-dictionary/jvn
github.com/kotakanbe/go-cve-dictionary/nvd
github.com/kotakanbe/go-cve-dictionary/db
golang.org/x/net/websocket
github.com/nlopes/slack
net/mail
net/smtp
text/template/parse
text/template
hash/fnv
runtime/debug
github.com/boltdb/bolt
github.com/future-architect/vuls/cache
os/exec
github.com/mitchellh/go-homedir
golang.org/x/crypto/curve25519
golang.org/x/crypto/ed25519/internal/edwards25519
golang.org/x/crypto/ed25519
golang.org/x/crypto/internal/subtle
golang.org/x/crypto/internal/chacha20
golang.org/x/crypto/poly1305
golang.org/x/crypto/ssh
golang.org/x/crypto/ssh/agent
github.com/howeyc/gopass
github.com/kotakanbe/go-pingscanner
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/future-architect/vuls 
github.com/future-architect/vuls/cache 
github.com/future-architect/vuls/commands 
github.com/future-architect/vuls/config 
github.com/future-architect/vuls/contrib/owasp-dependency-check/parser 
github.com/future-architect/vuls/models github.com/future-architect/vuls/oval 
github.com/future-architect/vuls/report github.com/future-architect/vuls/scan 
github.com/future-architect/vuls/util returned exit code 2
make: *** [debian/rules:4: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vuls.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#917588: ding-libs: FTBFS (failing tests)

[Santiago Vila]

Package: src:ding-libs
Version: 0.6.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 quilt
   dh_quilt_patch -a
No patches in series
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
libtoolize: copying file 'build/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 ...]

PASS: ini_configmod_ut
PASS: ini_save_ut
===
   ding-libs 0.6.1: ./test-suite.log
===

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: ini_validators_ut_check
=

Running suite(s): ini_validators
94%: Checks: 18, Failures: 1, Errors: 0
ini/ini_validators_ut_check.c:610:F:ini_allowed_options:test_ini_allowed_options_wrong_regex:0:
 Got msg: [[rule/options_for_foo]: Cannot compile regular expression from 
option 'section_re'. Error: 'Unmatched [, [^, [:, [., or [=']
FAIL ini_validators_ut_check (exit status: 1)


Testsuite summary for ding-libs 0.6.1

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to sssd-de...@lists.fedorahosted.org

make[3]: *** [Makefile:1744: test-suite.log] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:1852: check-TESTS] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:2192: check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ding-libs.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#917593: mpd: FTBFS ('_IO_off64_t' has not been declared)

[Santiago Vila]

Package: src:mpd
Version: 0.20.23-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 -- --without-tremor --enable-vorbis --disable-shine-encoder 
--enable-systemd-daemon --with-systemdsystemunitdir=/lib/systemd/system 
--with-systemduserunitdir=/usr/lib/systemd/user --enable-alsa \
--enable-test \
--enable-bzip2 --enable-iso9660 --enable-zlib --enable-zzip \
--enable-neighbor-plugins --enable-upnp --with-zeroconf=avahi \
--enable-ipv6 --enable-tcp --enable-un \
--enable-nfs --enable-smbclient --enable-webdav \
--enable-aac --enable-adplug --enable-sidplay --enable-ffmpeg 
--enable-flac --enable-fluidsynth --enable-gme --enable-sndfile --enable-mikmod 
--enable-modplug --enable-mad --enable-mpg123 --enable-mpc --enable-opus 
--enable-audiofile --enable-wavpack --enable-wildmidi \
--with-boost --enable-cue --enable-database --enable-expat --enable-icu 
--enable-lsr --enable-libmpdclient --enable-libwrap --enable-inotify 
--enable-soxr --enable-sqlite --enable-syslog \

[... snipped ...]

g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -I/usr/include/x86_64-linux-gnu 
-I/usr/include/samba-4.0   -I/usr/include/x86_64-linux-gnu -I/usr/include/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -ffast-math -ftree-vectorize -funwind-tables 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare 
-Wno-noexcept-type -c -o src/input/plugins/libinput_a-SmbclientInputPlugin.o 
`test -f 'src/input/plugins/SmbclientInputPlugin.cxx' || echo 
'./'`src/input/plugins/SmbclientInputPlugin.cxx
g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -I/usr/include/x86_64-linux-gnu 
-I/usr/include/samba-4.0   -I/usr/include/x86_64-linux-gnu -I/usr/include/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -ffast-math -ftree-vectorize -funwind-tables 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare 
-Wno-noexcept-type -c -o src/lib/nfs/libinput_a-Connection.o `test -f 
'src/lib/nfs/Connection.cxx' || echo './'`src/lib/nfs/Connection.cxx
g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -I/usr/include/x86_64-linux-gnu 
-I/usr/include/samba-4.0   -I/usr/include/x86_64-linux-gnu -I/usr/include/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -ffast-math -ftree-vectorize -funwind-tables 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare 
-Wno-noexcept-type -c -o src/lib/nfs/libinput_a-Error.o `test -f 
'src/lib/nfs/Error.cxx' || echo './'`src/lib/nfs/Error.cxx
g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -I/usr/include/x86_64-linux-gnu 
-I/usr/include/samba-4.0   -I/usr/include/x86_64-linux-gnu -I/usr/include/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -ffast-math -ftree-vectorize -funwind-tables 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare 
-Wno-noexcept-type -c -o src/lib/nfs/libinput_a-Manager.o `test -f 
'src/lib/nfs/Manager.cxx' || echo './'`src/lib/nfs/Manager.cxx
g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -I/usr/include/x86_64-linux-gnu 
-I/usr/include/samba-4.0   -I/usr/include/x86_64-linux-gnu -I/usr/include/ 
-I/usr/include/glib-2.0 

Bug#917590: ffms2: FTBFS (No module named 'headerid')

[Santiago Vila]

Package: src:ffms2
Version: 2.23-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
   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:37: installing './compile'
configure.ac:5: installing './missing'

[... snipped ...]

 ^~~~
In file included from src/vapoursynth/vapoursynth.cpp:24:
src/vapoursynth/../core/utils.h:130:91: warning: 'void 
avresample_free(AVAudioResampleContext**)' is deprecated 
[-Wdeprecated-declarations]
 typedef unknown_size FFResampleContext;

   ^
In file included from src/vapoursynth/../core/utils.h:36,
 from src/vapoursynth/vapoursynth.cpp:24:
/usr/include/x86_64-linux-gnu/libavresample/avresample.h:258:6: note: declared 
here
 void avresample_free(AVAudioResampleContext **avr);
  ^~~
/bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=c++11 -fvisibility=hidden 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -version-info 4:0:0 -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o src/core/libffms2.la -rpath /usr/lib/x86_64-linux-gnu 
src/core/audiosource.lo src/core/ffms.lo src/core/filehandle.lo 
src/core/indexing.lo src/core/lavfaudio.lo src/core/lavfindexer.lo 
src/core/lavfvideo.lo src/core/track.lo src/core/utils.lo 
src/core/videosource.lo src/core/videoutils.lo src/core/wave64writer.lo 
src/core/zipfile.lo src/vapoursynth/vapoursource.lo 
src/vapoursynth/vapoursynth.lo -lavformat -lavcodec -lswscale -lavutil 
-lavresample  -lz  
libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crti.o 
/usr/lib/gcc/x86_64-linux-gnu/8/crtbeginS.o  src/core/.libs/audiosource.o 
src/core/.libs/ffms.o src/core/.libs/filehandle.o src/core/.libs/indexing.o 
src/core/.libs/lavfaudio.o src/core/.libs/lavfindexer.o 
src/core/.libs/lavfvideo.o src/core/.libs/track.o src/core/.libs/utils.o 
src/core/.libs/videosource.o src/core/.libs/videoutils.o 
src/core/.libs/wave64writer.o src/core/.libs/zipfile.o 
src/vapoursynth/.libs/vapoursource.o src/vapoursynth/.libs/vapoursynth.o   
-lavformat -lavcodec -lswscale -lavutil -lavresample -lz 
-L/usr/lib/gcc/x86_64-linux-gnu/8 
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/x86_64-linux-gnu/8/crtendS.o /usr/lib/gcc/x86_64-li
 nux-gnu/8/../../../x86_64-linux-gnu/crtn.o  -g -O2 -fstack-protector-strong 
-Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed   -Wl,-soname -Wl,libffms2.so.4 
-o src/core/.libs/libffms2.so.4.0.0
libtool: link: (cd "src/core/.libs" && rm -f "libffms2.so.4" && ln -s 
"libffms2.so.4.0.0" "libffms2.so.4")
libtool: link: (cd "src/core/.libs" && rm -f "libffms2.so" && ln -s 
"libffms2.so.4.0.0" "libffms2.so")
libtool: link: ( cd "src/core/.libs" && rm -f "libffms2.la" && ln -s 
"../libffms2.la" "libffms2.la" )
/bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=c++11 -fvisibility=hidden 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
src/index/ffmsindex src/index/ffmsindex.o src/core/libffms2.la 
libtool: link: g++ -std=c++11 -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o 
src/index/.libs/ffmsindex src/index/ffmsindex.o  src/core/.libs/libffms2.so
make[2]: Leaving directory '/<>'
python3 -m markdown doc/ffms2-api.md \
-x fenced_code -x headerid >doc/ffms2-api.html
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/markdown/__main__.py", line 144, in 

run()
  File "/usr/lib/python3/dist-packages/markdown/__main__.py", line 138, in run
markdown.markdownFromFile(**options)
  File "/usr/lib/python3/dist-packages/markdown/core.py", line 408, in 
markdownFromFile
md = Markdown(**kwargs)
  File "/usr/lib/python3/dist-packages/markdown/core.py", line 100, in __init__

Bug#917587: colmap: FTBFS (dh_auto_configure fails)

[Santiago Vila]

Package: src:colmap
Version: 3.5-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
   dh_auto_configure -a
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 ..
-- 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

[... snipped ...]

arg [/lib64/ld-linux-x86-64.so.2] ==> ignore
arg [-pie] ==> ignore
arg [-o] ==> ignore
arg [cmTC_5fed7] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/Scrt1.o] ==> 
ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crti.o] ==> 
ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/crtbeginS.o] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/crtoffloadbegin.o] ==> ignore
arg [-L/usr/lib/gcc/x86_64-linux-gnu/8] ==> dir 
[/usr/lib/gcc/x86_64-linux-gnu/8]
arg [-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu] ==> dir 
[/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu]
arg [-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib] ==> dir 
[/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib]
arg [-L/lib/x86_64-linux-gnu] ==> dir [/lib/x86_64-linux-gnu]
arg [-L/lib/../lib] ==> dir [/lib/../lib]
arg [-L/usr/lib/x86_64-linux-gnu] ==> dir [/usr/lib/x86_64-linux-gnu]
arg [-L/usr/lib/../lib] ==> dir [/usr/lib/../lib]
arg [-L/usr/lib/gcc/x86_64-linux-gnu/8/../../..] ==> dir 
[/usr/lib/gcc/x86_64-linux-gnu/8/../../..]
arg [-zrelro] ==> ignore
arg [-znow] ==> ignore
arg [CMakeFiles/cmTC_5fed7.dir/OpenMPTryFlag.cpp.o] ==> ignore
arg [-lstdc++] ==> lib [stdc++]
arg [-lm] ==> lib [m]
arg [-lgomp] ==> lib [gomp]
arg [-lgcc_s] ==> lib [gcc_s]
arg [-lgcc] ==> lib [gcc]
arg [-lpthread] ==> lib [pthread]
arg [-lc] ==> lib [c]
arg [-lgcc_s] ==> lib [gcc_s]
arg [-lgcc] ==> lib [gcc]
arg [/usr/lib/gcc/x86_64-linux-gnu/8/crtendS.o] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crtn.o] ==> 
ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/8/crtoffloadend.o] ==> ignore
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/8] ==> 
[/usr/lib/gcc/x86_64-linux-gnu/8]
  collapse library dir 
[/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu] ==> 
[/usr/lib/x86_64-linux-gnu]
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib] ==> 
[/usr/lib]
  collapse library dir [/lib/x86_64-linux-gnu] ==> [/lib/x86_64-linux-gnu]
  collapse library dir [/lib/../lib] ==> [/lib]
  collapse library dir [/usr/lib/x86_64-linux-gnu] ==> 
[/usr/lib/x86_64-linux-gnu]
  collapse library dir [/usr/lib/../lib] ==> [/usr/lib]
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/8/../../..] ==> [/usr/lib]
  implicit libs: [stdc++;m;gomp;gcc_s;gcc;pthread;c;gcc_s;gcc]
  implicit dirs: 
[/usr/lib/gcc/x86_64-linux-gnu/8;/usr/lib/x86_64-linux-gnu;/usr/lib;/lib/x86_64-linux-gnu;/lib]
  implicit fwks: []


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 .. returned exit code 1
make: *** [debian/rules:28: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/colmap.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#917589: erlang-p1-pkix: FTBFS (failing tests)

[Santiago Vila]

Package: src:erlang-p1-pkix
Version: 0.2018.11.12-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 --buildsystem=rebar --with rebar
   dh_update_autotools_config -a -O--buildsystem=rebar
   dh_autoreconf -a -O--buildsystem=rebar
   dh_auto_configure -a -O--buildsystem=rebar
make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
configure
make[1]: Nothing to be done for 'configure'.
   dh_auto_build -a -O--buildsystem=rebar
make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
build
echo rebar_compile
rebar_compile
rebar compile skip_deps=true -vv
DEBUG: Consult config file "/<>/rebar.config"
DEBUG: Rebar location: "/usr/bin/rebar"

[... snipped ...]

pkix_test: unexpected_info_test...ok
  pkix_test: format_error_test...[0.007 s] ok
  pkix_test: removed_before_commit_test...*failed*
in function pkix_test:'-removed_before_commit_test/0-fun-3-'/0 
(test/pkix_test.erl, line 369)
in call from eunit_test:'-mf_wrapper/2-fun-0-'/2 (eunit_test.erl, line 273)
in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71)
in call from eunit_proc:run_test/1 (eunit_proc.erl, line 510)
in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 335)
in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 493)
in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 435)
in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 325)
**error:{assertMatch,[{module,pkix_test},
  {line,369},
  {expression,"pkix : commit ( test_dir ( ) )"},
  {pattern,"{ ok , [ { _ , enoent } ] , [ ] , undefined }"},
  {value,{ok,[{<<"/build/erlang-p1-pkix-cR"...>>,enoent}],
 [{<<"/build/erlang-p1-pki"...>>,
   {invalid_cert,1,selfsigned_peer}}],
 {<<"/build/erlang-p1-pki"...>>,enoent}}}]}
  output:<<"">>

  pkix_test: stop_test...=INFO REPORT 26-Dec-2018::21:10:33.545671 ===
application: pkix
exited: stopped
type: temporary
[0.014 s] ok
  [done in 0.857 s]
module 'pkix'
===
  Failed: 14.  Skipped: 0.  Passed: 30.
Cover analysis: /<>/.eunit/index.html
Coverdata export: /<>/.eunit/cover.coverdata
DEBUG: Reconstruct crypto [{fips_mode,false},{rand_cache_size,896}]
DEBUG: Reconstruct public_key []
DEBUG: Reconstruct kernel [{logger_level,notice},
   {logger_sasl_compatible,false}]
DEBUG: Reconstruct rebar []
DEBUG: Reconstruct pkix []
DEBUG: Reconstruct asn1 []
DEBUG: Reconstruct stdlib []
DEBUG: No processes to kill
ERROR: One or more eunit tests failed.
ERROR: eunit failed while processing /<>: rebar_abort
make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:138: rebar_eunit] 
Error 1
dh_auto_test: make --no-print-directory -f 
/usr/share/dh-rebar/make/dh-rebar.Makefile test 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 build was made in my autobuilder with "dpkg-buildpackage -B"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/erlang-p1-pkix.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.

Processed: tagging 915514

[Debian Bug Tracking System]

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

> tags 915514 + ftbfs
Bug #915514 [pysph] pysph: Missing build-dependency on python-pytest-runner, 
Debian builds pulling source from network?
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Cyril Brulebois]

Control: tag -1 patch

Cyril Brulebois  (2018-12-28):
> Santiago Vila  (2018-12-28):
> > I can offer a test machine where this happens all the time if you
> > need it to reproduce it. Please contact me privately for details.
> 
> This would be super-useful, as I might have a tentative patch but
> can't reproduce the issue in various setups. Will follow-up privately.

Thanks to Santiago, I've managed to reproduce the issue on that test
machine, but also to test a tentative patch, inspired by positive
results there:

  https://bugs.debian.org/880351#12

The attached patch does the trick, but instead of sorting (or here,
reverse-sorting) the list of tests to run, I've chosen to encode a
sequence of tests that makes the test suite run OK. This way, it should
be obvious when new tests are added, so that one can find and document
a suitable sequence of tests.

I intend to NMU the package in the upcoming days (or team-upload it,
as proposed in #88035 already), with this patch or with a more simple
one based on a simpler “| LC_ALL=C sort -r” addition, as you wish.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru honeysql-clojure-0.8.2/debian/changelog honeysql-clojure-0.8.2/debian/changelog
--- honeysql-clojure-0.8.2/debian/changelog	2017-08-04 19:40:33.0 +
+++ honeysql-clojure-0.8.2/debian/changelog	2018-12-28 23:35:12.0 +
@@ -1,3 +1,13 @@
+honeysql-clojure (0.8.2-2) UNRELEASED; urgency=medium
+
+  * Fix FTBFS by running tests in a specific order. Instead of blindly
+(reverse-)sorting the results of the find command and trusting it to
+be right, encode a suitable sequence of tests (Closes: #907765). Also
+make sure to error out when tests are added or removed, to make sure
+this sequence get refreshed when needed.
+
+ -- Cyril Brulebois   Fri, 28 Dec 2018 23:35:12 +
+
 honeysql-clojure (0.8.2-1) unstable; urgency=medium
 
   * Initial release (Closes: #855757)
diff -Nru honeysql-clojure-0.8.2/debian/rules honeysql-clojure-0.8.2/debian/rules
--- honeysql-clojure-0.8.2/debian/rules	2017-08-04 19:40:33.0 +
+++ honeysql-clojure-0.8.2/debian/rules	2018-12-28 23:35:12.0 +
@@ -22,9 +22,21 @@
 	rm -f $(CURDIR)/$(PRODUCED_JAR)
 	rm -rf $(CURDIR)/doc/html
 
+# Tests can't run in a random order (#907765):
+override_dh_auto_test: ORDERED_TESTS=honeysql/format_test.cljc honeysql/core_test.cljc
+override_dh_auto_test: EXPECTED=$(shell echo "$(ORDERED_TESTS)" | sed 's/ /\n/g' | sort | xargs)
+override_dh_auto_test: FOUND=$(shell cd test && find -name '*.cljc' | sed 's,^[.]/,,' | sort | xargs)
 override_dh_auto_test:
-	(cd test && find . -name '*.cljc' | \
-		xargs clojure -cp $(CURDIR)/$(PRODUCED_JAR))
+	# Make sure to detect when tests appear or disappear:
+	@if [ "$(FOUND)" != "$(EXPECTED)" ]; then \
+		echo "E: sanity check failed, available tests don't match known tests:"; \
+		echo "- found:$(FOUND)"; \
+		echo "- expected: $(EXPECTED)"; \
+		echo "=> Please update ORDERED_TESTS in debian/rules accordingly"; \
+		exit 1; \
+	fi
+	# Run tests:
+	(cd test && clojure -cp $(CURDIR)/$(PRODUCED_JAR) $(ORDERED_TESTS))
 
 %.html:%.md
 	cat debian/header.html > $@


signature.asc
Description: PGP signature

Bug#917585: FTBFS: Multiple test failures

[Steve McIntyre]

Package: src:plainbox
Version: 0.25-1
Severity: serious
Tags: ftbfs
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.

While doing that, I've found that plainbox fails multiple tests in its
testsuite. I've tested further and I can reproduce the same thing on
amd64 too, so it's not an architecture-specific problem.

...
==
ERROR: test_run_invalid_env (plainbox.impl.secure.test_launcher1.MainTests)
--
Traceback (most recent call last):
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/test_launcher1.py",
 line 326, in test_run_invalid_env
main(['--target=1234', '-T', 'blarg'])
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/launcher1.py",
 line 259, in main
ns = parser.parse_args(argv)
  File "/usr/lib/python3.7/argparse.py", line 1758, in parse_args
args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.7/argparse.py", line 1790, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.7/argparse.py", line 1996, in _parse_known_args
start_index = consume_optional(start_index)
  File "/usr/lib/python3.7/argparse.py", line 1936, in consume_optional
take_action(action, args, option_string)
  File "/usr/lib/python3.7/argparse.py", line 1864, in take_action
action(self, namespace, argument_values, option_string)
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/launcher1.py",
 line 175, in __call__
items = copy.copy(argparse._ensure_value(namespace, self.dest, {}))
AttributeError: module 'argparse' has no attribute '_ensure_value'

==
ERROR: test_run_valid_hash (plainbox.impl.secure.test_launcher1.MainTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/mock.py", line 1195, in patched
return func(*args, **keywargs)
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/test_launcher1.py",
 line 239, in test_run_valid_hash
'--target=1234', '-T', 'key=value', '-T', 'other=value'])
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/launcher1.py",
 line 259, in main
ns = parser.parse_args(argv)
  File "/usr/lib/python3.7/argparse.py", line 1758, in parse_args
args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.7/argparse.py", line 1790, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.7/argparse.py", line 1996, in _parse_known_args
start_index = consume_optional(start_index)
  File "/usr/lib/python3.7/argparse.py", line 1936, in consume_optional
take_action(action, args, option_string)
  File "/usr/lib/python3.7/argparse.py", line 1864, in take_action
action(self, namespace, argument_values, option_string)
  File 
"/home/steve/debian/build/plainbox/plainbox-0.25/plainbox/impl/secure/launcher1.py",
 line 175, in __call__
items = copy.copy(argparse._ensure_value(namespace, self.dest, {}))
AttributeError: module 'argparse' has no attribute '_ensure_value'

...

(more failures follow).

Full log online at

  
https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/plainbox_0.25-1_armel.log

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

Processed: Re: Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #907765 [src:honeysql-clojure] honeysql-clojure: FTBFS in buster/sid (Could 
not locate honeysql/format_test__init.class or honeysql/format_test.clj on 
classpath.)
Added tag(s) patch.

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

Bug#917582: FTBFS: failure to build manual

[Steve McIntyre]

On Fri, Dec 28, 2018 at 10:29:35PM +, Steve McIntyre wrote:
>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'

A quick fix seems to be to install texlive-fonts-recommended and
lmodern. I don't know if that's needed for your package or something
you build-dep on - pandoc?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I used to be the first kid on the block wanting a cranial implant,
 now I want to be the first with a cranial firewall. " -- Charlie Stross

Bug#917584: FTBFS: test failures on multiple arches

[Steve McIntyre]

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)

Bug#917501: meson: FTBFS (failing tests)

[Jussi Pakkanen]

On Fri, Dec 28, 2018 at 1:57 AM Santiago Vila  wrote:

> The build was made in my autobuilder with "dpkg-buildpackage -A"
> but it also fails here:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html
>
> where you can get a full build log if you need it.

The actual error message was not in your snippet, but from the log it is this:

Traceback (most recent call last):
  File "run_unittests.py", line 2044, in test_rpath_uses_ORIGIN
self.assertTrue(rpath)
AssertionError: None is not true

The test is verifying that libraries and executables have the correct
rpath. However in this case, for some reason I don't understand, the
files built in the second step do not have rpaths at all. I made a PR
improving the message here:

https://github.com/mesonbuild/meson/pull/4684

It's probably not particulary useful but still. Does anyone have any
suggestions on what the second build setup has would cause rpaths to
not be there?

Processed: tagging 917582

[Debian Bug Tracking System]

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

> tags 917582 + ftbfs
Bug #917582 [src:mod-gnutls] FTBFS: failure to build manual
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#917369: python-cymruwhois: diff for NMU version 1.6-3.1

[Mattia Rizzolo]

On Fri, Dec 28, 2018 at 10:28:05PM +, Ana C. Custura wrote:
> This is ok, thanks for letting me know.

Are you picking up the changes and doing a maintainer upload, or may I
go ahead and let my NMU enter unstable sooner than the current 5-days
delay (i.e., let it enter now)?

Thank you for your answer.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#917369: python-cymruwhois: diff for NMU version 1.6-3.1

[Ana C. Custura]

Hi Mattia,

This is ok, thanks for letting me know.

Ana

On Fri, Dec 28, 2018, at 6:09 PM, Mattia Rizzolo wrote:
> Control: tags 917369 + patch
> Control: tags 917369 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for python-cymruwhois (versioned as 1.6-3.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
> 
> diffoscope'ing the .debs the changes are only:
> 
> ├── python3-cymruwhois_1.6-3.1_all.deb
> │ ├── file list
> │ │ @@ -1,3 +1,3 @@
> │ │  -rw-r--r--   0004 2018-12-28 
> 18:02:39.00 debian-binary
> │ │ --rw-r--r--   000 1384 2018-12-28 
> 18:02:39.00 control.tar.xz
> │ │ +-rw-r--r--   000 1372 2018-12-28 
> 18:02:39.00 control.tar.xz
> │ │  -rw-r--r--   000 6756 2018-12-28 
> 18:02:39.00 data.tar.xz
> │ ├── control.tar.xz
> │ │ ├── control.tar
> │ │ │ ├── file list
> │ │ │ │ @@ -1,5 +1,5 @@
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./
> │ │ │ │ --rw-r--r--   0 root (0) root (0)  525 2018-
> 12-28 18:02:39.00 ./control
> │ │ │ │ +-rw-r--r--   0 root (0) root (0)  510 2018-
> 12-28 18:02:39.00 ./control
> │ │ │ │  -rw-r--r--   0 root (0) root (0)  894 2018-
> 12-28 18:02:39.00 ./md5sums
> │ │ │ │  -rwxr-xr-x   0 root (0) root (0)  545 2018-
> 12-28 18:02:39.00 ./postinst
> │ │ │ │  -rwxr-xr-x   0 root (0) root (0)  561 2018-
> 12-28 18:02:39.00 ./prerm
> │ │ │ ├── ./control
> │ │ │ │ @@ -1,14 +1,14 @@
> │ │ │ │  Package: python3-cymruwhois
> │ │ │ │  Source: python-cymruwhois
> │ │ │ │  Version: 1.6-3.1
> │ │ │ │  Architecture: all
> │ │ │ │  Maintainer: Ana Custura 
> │ │ │ │  Installed-Size: 36
> │ │ │ │ -Depends: python3.7:any, python3:any
> │ │ │ │ +Depends: python3:any
> │ │ │ │  Suggests: python-cymruwhois-doc
> │ │ │ │  Section: python
> │ │ │ │  Priority: optional
> │ │ │ │  Homepage: https://pythonhosted.org/cymruwhois/
> │ │ │ │  Description: Python library for interfacing with the 
> whois.cymru.com service (Python 3)
> │ │ │ │   Perform lookups by ip address and return ASN,
> │ │ │ │   Country Code, and Netblock Owner.
> │ │ │ ├── ./md5sums
> │ │ │ │ ├── ./md5sums
> │ │ │ │ │┄ Files differ
> │ ├── data.tar.xz
> │ │ ├── data.tar
> │ │ │ ├── file list
> │ │ │ │ @@ -1,11 +1,11 @@
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/bin/
> │ │ │ │ --rwxr-xr-x   0 root (0) root (0)  393 2018-
> 12-28 18:02:39.00 ./usr/bin/python3-cymruwhois
> │ │ │ │ +-rwxr-xr-x   0 root (0) root (0)  391 2018-
> 12-28 18:02:39.00 ./usr/bin/python3-cymruwhois
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/lib/
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/dist-packages/
> │ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/dist-packages/
> cymruwhois-1.6.egg-info/
> │ │ │ │  -rw-r--r--   0 root (0) root (0) 1101 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/dist-packages/
> cymruwhois-1.6.egg-info/PKG-INFO
> │ │ │ │  -rw-r--r--   0 root (0) root (0)1 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/dist-packages/
> cymruwhois-1.6.egg-info/dependency_links.txt
> │ │ │ │  -rw-r--r--   0 root (0) root (0)   56 2018-
> 12-28 18:02:39.00 ./usr/lib/python3/dist-packages/
> cymruwhois-1.6.egg-info/entry_points.txt
> │ │ │ ├── ./usr/bin/python3-cymruwhois
> │ │ │ │ @@ -1,8 +1,8 @@
> │ │ │ │ -#!/usr/bin/python3.7
> │ │ │ │ +#!/usr/bin/python3
> │ │ │ │  # EASY-INSTALL-ENTRY-SCRIPT: 
> 'cymruwhois==1.6','console_scripts','cymruwhois'
> │ │ │ │  __requires__ = 'cymruwhois==1.6'
> │ │ │ │  import re
> │ │ │ │  import sys
> │ │ │ │  from pkg_resources import load_entry_point
> │ │ │ │
> │ │ │ │  if __name__ == '__main__':
> 
> 
> And similarly for the python2 one.
> 
> 
> 
> Regards.
> 
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
> Email had 2 attachments:
> + python-cymruwhois-1.6-3.1-nmu.diff
>   2k (text/x-diff)
> 

Bug#917582: FTBFS: failure to build manual

[Steve McIntyre]

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 */*.gpg */*.gpg~ */gpg.conf 
authority/lock */*.kbx */*.kbx~ */S.gpg-agent */private-keys-v1.d/* 
authority/tofu.db *.lock msva.gnupghome/trustdb.gpg authority/ocsp_index.txt 
authority/ocsp_index.txt.attr server/x509-chain.pem server/softhsm.db" || rm -f 
cache/* logs/* outputs/* server/crl.pem */x509.pem authority.template 
client.template imposter.template rogueclient.template server.template *.uid 
*/*.pgp */*.pgp.raw */*.gpg */*.gpg~ */gpg.conf authority/lock */*.kbx */*.kbx~ 
*/S.gpg-agent */private-keys-v1.d/* authority/tofu.db *.lock 
msva.gnupghome/trustdb.gpg authority/ocsp_index.txt 
authority/ocsp_index.txt.attr server/x509-chain.pem server/softhsm.db
failed to remove 'rogueca': No such file or directory
rmdir: failed to remove 'rogueclient': No such file or directory
rmdir: 

Processed: Re: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #912631 [liblwjgl-java-jni] liblwjgl-java-jni: Missing symbols in 
liblwjgl.so, stretch-sid, 386, amd64, mips
Severity set to 'grave' from 'important'

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

Bug#917577: jameica: depends on libswt-gtk2 which is no longer built

[Jeremy Bicha]

Source: jameica
Version: 2.8.2+dfsg-5
Severity: serious

jameica depends on libswt-gtk4-jni but that package is no longer built
by swt4-gtk.

Please switch to using libswt-gtk-4-jni instead (which uses gtk3
instead of gtk2).

Thanks,
Jeremy Bicha

Bug#917576: stegosuite: depends on libswt-gtk2 which is no longer built

[Jeremy Bicha]

Source: stegosuite
Version: 0.8.0-1
Severity: serious

jameica depends on libswt-gtk2-4-jni but that package is no longer
built by swt4-gtk.

Please switch to using libswt-gtk-4-jni instead (which uses gtk3
instead of gtk2).

Thanks,
Jeremy Bicha

Bug#917554: marked as done (zutils: Fails to upgrade: preinst called with unknown argument `upgrade')

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 21:22:15 +
with message-id 
and subject line Bug#917554: fixed in zutils 1.7-8
has caused the Debian Bug report #917554,
regarding zutils: Fails to upgrade: preinst called with unknown argument 
`upgrade'
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.)


-- 
917554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zutils
Version: 1.7-7
Severity: serious

zutils fails to upgrade from 1.7-6 to 1.7-7 as follows for me:

Preparing to unpack .../60-zutils_1.7-7_amd64.deb ...
preinst called with unknown argument `upgrade'
dpkg: error processing archive 
/tmp/apt-dpkg-install-9FRsIU/60-zutils_1.7-7_amd64.deb (--unpack):
 new zutils package pre-installation script subprocess returned error exit 
status 1
Errors were encountered while processing:
 /tmp/apt-dpkg-install-9FRsIU/60-zutils_1.7-7_amd64.deb

I suspect that this is caused by this change in 1.7-7:

  * Dropping temporary upgrade handling from 1.7-2, not needed anymore.

Probably too much has been removed from preinst.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages zutils depends on:
ii  libc6   2.28-3
ii  libgcc1 1:8.2.0-13
ii  libstdc++6  8.2.0-13

Versions of packages zutils recommends:
ii  bzip2 1.0.6-9
ii  lzip  1.20-4
ii  xz-utils  5.2.2-1.3

zutils suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: zutils
Source-Version: 1.7-8

We believe that the bug you reported is fixed in the latest version of
zutils, 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 Baumann  (supplier of updated zutils 
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, 28 Dec 2018 21:33:41 +0100
Source: zutils
Binary: zutils
Architecture: source amd64
Version: 1.7-8
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Description:
 zutils - utilities for dealing with compressed files transparently
Closes: 917554
Changes:
 zutils (1.7-8) unstable; urgency=medium
 .
   * Uploading to sid.
   * Adding upgrade target to preinst dummy targets (Closes: #917554).
Checksums-Sha1:
 9099fedbb1d38000260d9836f99be24afb3b732b 1893 zutils_1.7-8.dsc
 dd89f704bf25065fd45f20235652af90d4ab52e0 6968 zutils_1.7-8.debian.tar.xz
 49143f2702cec818bb6f1c202467e992228b8453 880812 zutils-dbgsym_1.7-8_amd64.deb
 5a67d304a712e93702dc8e0f04ba71b3cd8f88d5 5949 zutils_1.7-8_amd64.buildinfo
 dbb33151f821be969d84804c94eed7eb334d6aab 471976 zutils_1.7-8_amd64.deb
Checksums-Sha256:
 d81b52881979460629f4494992e3445597eddca653fc85c84db0097416c7878b 1893 
zutils_1.7-8.dsc
 29b2982a7dd5c81ae9a39f10779204e564cba2f3f63e64ce4cf22a90898d42dd 6968 
zutils_1.7-8.debian.tar.xz
 4ef9e09ab6abf92435925f29826cd353565b31110688f828122dcb0a2a43ae63 880812 
zutils-dbgsym_1.7-8_amd64.deb
 f15677d6817baab8b01c07616be443c5b27a0f0f4dc4cd5052fa15e37f060bff 5949 
zutils_1.7-8_amd64.buildinfo
 6e9deb641096c2ee102da4bbac3bb71847e102d5822c85444f002c69157a8a53 471976 
zutils_1.7-8_amd64.deb
Files:
 db48950d25668cd1d09d64a219fd9d8d 1893 utils optional zutils_1.7-8.dsc
 75cd04f80ce0b12236612bf55c017cfa 6968 utils optional zutils_1.7-8.debian.tar.xz
 ffdd4681cbcb8e18f1fd08c0161c2a2f 880812 debug optional 
zutils-dbgsym_1.7-8_amd64.deb
 088b536e3efedde3c640816ad8cacd31 5949 utils optional 
zutils_1.7-8_amd64.buildinfo
 b65a54e741a4c0733ecf91d7c27a0601 471976 utils optional zutils_1.7-8_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#916777: marked as done (activemq: broken symlinks: /usr/share/activemq/lib/{geronimo-jacc_1.1_spec,optional/{commons-httpclient,stax-api}}.jar)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 21:19:27 +
with message-id 
and subject line Bug#916777: fixed in activemq 5.15.8-2
has caused the Debian Bug report #916777,
regarding activemq: broken symlinks: 
/usr/share/activemq/lib/{geronimo-jacc_1.1_spec,optional/{commons-httpclient,stax-api}}.jar
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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m53.7s ERROR: FAIL: Broken symlinks:
  /usr/share/activemq/lib/geronimo-jacc_1.1_spec.jar -> 
../../java/geronimo-jacc_1.1_spec.jar (activemq)
  /usr/share/activemq/lib/optional/stax-api.jar -> ../../../java/stax-api.jar 
(activemq)
  /usr/share/activemq/lib/optional/commons-httpclient.jar -> 
../../../java/commons-httpclient.jar (activemq)

Given that one .jar file is not marked as optional, I set the severity
to serious, since there seems to be a dependency missing.

Should activemq Recommends/Suggests the packages providing the optional
.jar files?


cheers,

Andreas


activemq_5.15.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: activemq
Source-Version: 5.15.8-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated activemq 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, 28 Dec 2018 21:39:42 +0100
Source: activemq
Binary: libactivemq-java activemq
Architecture: source
Version: 5.15.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 activemq   - Java message broker - server
 libactivemq-java - Java message broker core libraries
Closes: 916777
Changes:
 activemq (5.15.8-2) unstable; urgency=medium
 .
   * Team upload
   * Replace commons-httpclient symlink with httpclient and remove libstax-java
 from Build-Depends because this package is only required for activemq-rar
 which we currently ignore.
   * activemq: Explicitly depend on libgeronimo-jacc-1.1-spec-java to fix a
 broken symlink. Thanks to Andreas Beckmann for the report.
 (Closes: #916777)
   * Declare compliance with Debian Policy 4.3.0.
Checksums-Sha1:
 5ea42d4bcc64eefb8f6e421c52446d6b2194192b 3590 activemq_5.15.8-2.dsc
 f9cf62e88510ce3fa41158d32317381e130e23b8 16648 activemq_5.15.8-2.debian.tar.xz
 175e7717136fabc4b9b4c3ba0725d951dd9198e1 18001 
activemq_5.15.8-2_amd64.buildinfo
Checksums-Sha256:
 b790884dd1b6605c0a8a817c4d71917bc91448996cc5766577136f6b62c8088e 3590 
activemq_5.15.8-2.dsc
 d841e3972cb0ee07a921af5d791cc99da20e8c1099d2b848a754c90af5cce3fe 16648 
activemq_5.15.8-2.debian.tar.xz
 ccb30f725d6798df57b06b50aa7dbce959ac3b44d339fdeaf8cc25c90bfc71a0 18001 
activemq_5.15.8-2_amd64.buildinfo
Files:
 10b78e9523946d29799f9c24e3603617 3590 java optional activemq_5.15.8-2.dsc
 7d0cd07b9adc79ff086e17707d21bf65 16648 java optional 
activemq_5.15.8-2.debian.tar.xz
 9145a54cb327f2f2930e6b8fb405ecee 18001 java optional 
activemq_5.15.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlwmjfhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkDgQQANFTKTODFjMQaeGcTXvhaRUUS9qWZmfUYbdj
asaNYQDGEeN0GaDD/IqmWUDdN9IZl9qZfwp0HJtgCmFIlc71NYK00D3lEZrHNTFJ
3Z53PaOmI2iKy4BvllPCfcyg6RGjgmBHEakcg238TMLQxg3TCH1ofl7EDRhOF+Hk
yptXMbjYjuq06P0XPMgelpJz3QlNRlYaDubODITQosjZP2nbAS2KOssQuAbf1H5D
2VteQvHNGls+HFXRMMFoYhugQrXKRZ2bwYWneI9gT9qvg/NDMDF9il5U55bcSULt
rsGIlYY3b6QnJJx44o4uchCeMWucgtY7HPtf+34iqEkvoJec4HpdMV8h59GbdGYQ
35JozPv8GA/hJt1EsUZlFw8FN29m4A6y4bToFYzT4XHeD+VGH18MvOsfpwhu7WOQ

Bug#916184: marked as done (fswatch FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 21:19:55 +
with message-id 
and subject line Bug#916184: fixed in fswatch 1.14.0+repack-1
has caused the Debian Bug report #916184,
regarding fswatch FTBFS: symbol differences
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.)


-- 
916184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fswatch
Version: 1.13.0+repack-1
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -O--as-needed
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libfswatch11/DEBIAN/symbols doesn't match 
completely debian/libfswatch11.symbols
--- debian/libfswatch11.symbols (libfswatch11_1.13.0+repack-1_amd64)
+++ dpkg-gensymbolsZqx8uC   2020-01-05 21:58:17.643092338 -1200
@@ -1,6 +1,7 @@
 libfswatch.so.11 libfswatch11 #MINVER#
  FSW_ALL_EVENT_FLAGS@Base 1.11.2
- (optional|c++)"__gnu_cxx::__enable_if::__value, 
bool>::__type std::operator==(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.13.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 1.13.0+repack-1
+#MISSING: 1.13.0+repack-1# 
(optional|c++)"__gnu_cxx::__enable_if::__value, 
bool>::__type std::operator==(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.13.0
  (c++)"__gnu_cxx::__normal_iterator > > std::__unique<__gnu_cxx::__normal_iterator > >, 
__gnu_cxx::__ops::_Iter_equal_to_iter>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, 
__gnu_cxx::__ops::_Iter_equal_to_iter)@Base" 1.10.0
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__ops::_Iter_equals_val, std::allocator > const> 
>(__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__ops::_Iter_equals_val, std::allocator > const>, 
std::random_access_iterator_tag)@Base" 1.10.0
  (c++)"bool std::__detail::_Compiler 
>::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher, false, 
false>&)@Base" 1.10.0
@@ -243,7 +244,7 @@
  (c++)"std::__detail::_BracketMatcher, true, 
false>::_M_ready()@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
false>::~_BracketMatcher()@Base" 1.10.0
  (optional|c++|arch= arm64 armel armhf mips mips64el mipsel ppc64el s390x 
alpha ia64 powerpc powerpcspe ppc64 riscv64 sparc64 
)"std::__detail::_BracketMatcher, true, 
true>::_M_add_char(char)@Base" 1.12.0
- 
(optional|c++)"std::__detail::_BracketMatcher, 
true, true>::_M_add_character_class(std::__cxx11::basic_string, std::allocator > const&, bool)@Base" 1.12.0
+#MISSING: 1.13.0+repack-1# 
(optional|c++)"std::__detail::_BracketMatcher, 
true, true>::_M_add_character_class(std::__cxx11::basic_string, std::allocator > const&, bool)@Base" 1.12.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::_M_make_range(char, char)@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::_M_ready()@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::~_BracketMatcher()@Base" 1.10.0
@@ -339,7 +340,7 @@
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.10.0
  (optional|c++|arch= armel riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace
 >, std::allocator > >, 
(__gnu_cxx::_Lock_policy)1>@Base" 1.11.2
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace
 >, std::allocator > >, 
(__gnu_cxx::_Lock_policy)2>@Base" 1.10.0
- (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 1.10.0
+#MISSING: 1.13.0+repack-1# (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 
1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, false, 
false>@Base" 1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, false, 
true>@Base" 1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, true, 
false>@Base" 1.10.0
dh_makeshlibs: failing due to earlier 

Processed: Bug #916961 in octave-symbolic marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916961 [src:octave-symbolic] octave-symbolic FTBFS: test failures
Added tag(s) pending.

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

Bug#916961: Bug #916961 in octave-symbolic marked as pending

[Mike Miller]

Control: tag -1 pending

Hello,

Bug #916961 in octave-symbolic 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/pkg-octave-team/octave-symbolic/commit/bb6cf6e8d2759f401652ad8b87713b1f0a98edf9


Fix newly failing unit tests

- d/p/linspace-drop-test.patch: New patch from upstream git.
- d/p/pochhammer-test-tolerance.patch: New patch from upstream git.

Gbp-Dch: Full
Closes: #916961


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916961

Processed: Bug #916777 in activemq marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916777 [activemq] activemq: broken symlinks: 
/usr/share/activemq/lib/{geronimo-jacc_1.1_spec,optional/{commons-httpclient,stax-api}}.jar
Added tag(s) pending.

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

Bug#916777: Bug #916777 in activemq marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #916777 in activemq 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/activemq/commit/a386e176617af909ee1b0a34138c9578e9506046


activemq: Explicitly depend on libgeronimo-jacc-1.1-spec-java to fix a broken

symlink.

I don't know why maven-debian-helper doesn't add this one automatically but
hey...

Closes: #916777
Thanks: Andreas Beckmann for the report.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916777

Bug#912361: marked as done (taglibs-standard FTBFS: java.lang.UnsupportedOperationException: This feature requires ASM7)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 21:15:37 +0100
with message-id <86220aa3-1f63-203e-173e-c1916f27b...@debian.org>
and subject line Re: taglibs-standard FTBFS: 
java.lang.UnsupportedOperationException: This feature requires ASM7
has caused the Debian Bug report #912361,
regarding taglibs-standard FTBFS: java.lang.UnsupportedOperationException: This 
feature requires ASM7
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.)


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

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.taglibs.standard.resources.ResourcesTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 s 
- in org.apache.taglibs.standard.resources.ResourcesTest
[INFO] Running org.apache.taglibs.standard.functions.FunctionsTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s 
- in org.apache.taglibs.standard.functions.FunctionsTest
[INFO] Running org.apache.taglibs.standard.util.EscapeXMLTest
[ERROR] Tests run: 16, Failures: 0, Errors: 16, Skipped: 0, Time elapsed: 0.126 
s <<< FAILURE! - in org.apache.taglibs.standard.util.EscapeXMLTest
[ERROR] testEmitEmptyString(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0.11 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] 
testEmitEscapedStringEnd(org.apache.taglibs.standard.util.EscapeXMLTest)  Time 
elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] 
testEmitEscapedStringAdjacent(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] 
testEmitEscapedStringMiddle(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEscapeString(org.apache.taglibs.standard.util.EscapeXMLTest)  Time 
elapsed: 0.001 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEmitEntireString(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] 
testEmitReaderUnbuffered(org.apache.taglibs.standard.util.EscapeXMLTest)  Time 
elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEmitReaderUnescaped(org.apache.taglibs.standard.util.EscapeXMLTest) 
 Time elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] 
testEmitEscapedStringBeginning(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEmitInteger(org.apache.taglibs.standard.util.EscapeXMLTest)  Time 
elapsed: 0 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEmitEscapedChars(org.apache.taglibs.standard.util.EscapeXMLTest)  
Time elapsed: 0.001 s  <<< ERROR!
java.lang.UnsupportedOperationException: This feature requires ASM7
at 
org.apache.taglibs.standard.util.EscapeXMLTest.setup(EscapeXMLTest.java:45)

[ERROR] testEmitChars(org.apache.taglibs.standard.util.EscapeXMLTest)  Time 
elapsed: 0.004 s  <<< ERROR!

Bug#917562: [Pkg-javascript-devel] Bug#917562: data/features directory is missing in node-caniuse-lite

[Jonas Smedegaard]

Quoting Pirate Praveen (2018-12-28 19:19:12)
> When trying to build autoprefixer.js which build depends on
> node-caniuse-lite, I got this error and upon inspection I found
> data/features directory is missing.
> 
> ERROR in /usr/lib/nodejs/caniuse-lite/data/features.js
> Module not found: Error: Can't resolve './features/aac' in
> '/usr/lib/nodejs/caniuse-lite/data'
>  @ /usr/lib/nodejs/caniuse-lite/data/features.js 1:22-47
>  @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/features.js
>  @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/index.js
>  @ /usr/lib/nodejs/autoprefixer/lib/autoprefixer.js
> 
> I was not able to figure out why this is not working now. Need help.

Upstream source seems to include some tests not tried during build.

I suggest to enable those during build and the autopkgtest framework.

I mean, make sure that something works - anything at all - before 
debugging why integration with something specific like autoprefixer.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: tagging 888619, tagging 914907, tagging 915150

[Debian Bug Tracking System]

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

> # Per #917550
> tags 888619 + pending
Bug #888619 [src:gzip] gzip: please add Homepage field
Added tag(s) pending.
> tags 914907 + pending
Bug #914907 [gzip] gzip: reproducible build (usrmerge): zgrep embeds path of 
grep found via PATH
Added tag(s) pending.
> tags 915150 + pending
Bug #915150 [src:gzip] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error 
"Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, 
then report this to bug-gnulib."
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

[Celejar]

On Fri, 28 Dec 2018 12:00:14 +0100
Michael Biebl  wrote:

> Am 28.12.18 um 07:04 schrieb Ben Hutchings:
> 
> > And if you downgrade udev and libudev1 to version 239-15, that will
> > trigger an update of the 4.19 initramfs (only) and you should then be
> > able to boot with Linux 4.19.
> 
> Or upgrade to udev 240-2, which should fix this issue.

I'm on 240-2 now, and the issue does indeed seem to be fixed. Thanks
much to both of you!

Celejar

Bug#917483: marked as done (tangerine-icon-theme: FTBFS in buster at least since 2018-12-06)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 18:21:16 +
with message-id 
and subject line Bug#917483: fixed in tangerine-icon-theme 0.26.debian-5
has caused the Debian Bug report #917483,
regarding tangerine-icon-theme: FTBFS in buster at least since 2018-12-06
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.)


-- 
917483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tangerine-icon-theme
Version: 0.26.debian-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]

dpkg-buildpackage
-

dpkg-buildpackage: info: source package tangerine-icon-theme
dpkg-buildpackage: info: source version 0.26.debian-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Biebl 
 dpkg-source --before-build .
 fakeroot debian/rules clean
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
debian/rules:7: /usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk: No 
such file or directory
make: *** No rule to make target 
'/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but I don't think such detail is really relevant.

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: tangerine-icon-theme
Source-Version: 0.26.debian-5

We believe that the bug you reported is fixed in the latest version of
tangerine-icon-theme, 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.
Jeremy Bicha  (supplier of updated tangerine-icon-theme 
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, 28 Dec 2018 10:31:46 -0500
Source: tangerine-icon-theme
Binary: tangerine-icon-theme
Architecture: source all
Version: 0.26.debian-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jeremy Bicha 
Description:
 tangerine-icon-theme - Tangerine Icon theme
Closes: 917483
Changes:
 tangerine-icon-theme (0.26.debian-5) unstable; urgency=medium
 .
   * QA upload
   * Drop obsolete ubuntu-get-source rule (Closes: #917483)
   * Drop obsolete simple-patchsys rule
   * Switch to source format 3.0 (quilt)
Checksums-Sha1:
 9c40206f44bed7d6df4d1be592fa2f647b6df69e 2125 
tangerine-icon-theme_0.26.debian-5.dsc
 fb4350f4729d0f9ac190064064a89e5877746646 27200 
tangerine-icon-theme_0.26.debian-5.debian.tar.xz
 aeb5c58aef730bbc4a80e3582f1bcc5cbe6d0577 11229 
tangerine-icon-theme_0.26.debian-5_all.buildinfo
 e1ffab2802a791ca131be55adc19c48034e795cb 377492 
tangerine-icon-theme_0.26.debian-5_all.deb
Checksums-Sha256:
 fe6c7cfb9afd6d1b8773f5258b279cc4570e03e744492f34cdd2ea410be56351 2125 
tangerine-icon-theme_0.26.debian-5.dsc
 b9f8724b2527ef2abf2da213071b41270b0e45f1a5e059d4067ebb2a328e32d6 27200 
tangerine-icon-theme_0.26.debian-5.debian.tar.xz
 b938b5f69d491a1878264969d3bc5c08a78127aa56873ff9e646308b3d174924 11229 
tangerine-icon-theme_0.26.debian-5_all.buildinfo
 2243ca282225b277701fec600c5a43b3ca57004b6c3d425ae00960d0a06804db 377492 
tangerine-icon-theme_0.26.debian-5_all.deb
Files:
 c4c498efd1c6dc5c54305a9e3b6a6d82 2125 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-5.dsc
 77b9a8b66df0526b02de8c5c4de81790 27200 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-5.debian.tar.xz
 d7ad8678463e4c1abe3077f898346c35 11229 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-5_all.buildinfo
 25a81fda55b68d8d781e2f54f7b16ea6 377492 non-free/x11 optional 
tangerine-icon-theme_0.26.debian-5_all.deb

-BEGIN PGP SIGNATURE-

Bug#916463: marked as done (human-icon-theme: FTBFS (No rule to make target '/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk'))

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 18:19:50 +
with message-id 
and subject line Bug#916463: fixed in human-icon-theme 0.28.debian-6
has caused the Debian Bug report #916463,
regarding human-icon-theme: FTBFS (No rule to make target 
'/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk')
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.)


-- 
916463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:human-icon-theme
Version: 0.28.debian-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]

dpkg-buildpackage
-

dpkg-buildpackage: info: source package human-icon-theme
dpkg-buildpackage: info: source version 0.28.debian-5
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Biebl 
 dpkg-source --before-build .
 fakeroot debian/rules clean
debian/rules:6: /usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk: No 
such file or directory
make: *** No rule to make target 
'/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


This used to build ok in the past, so apparently some of the
build-depends changed behaviour recently. In case it helps,
this is part of my build history for buster:

Status: successful human-icon-theme_0.28.debian-5_amd64-20181011T022111Z
Status: successful human-icon-theme_0.28.debian-5_amd64-20181022T020029Z
Status: failed human-icon-theme_0.28.debian-5_amd64-20181206T092923.282Z
Status: failed human-icon-theme_0.28.debian-5_amd64-20181208T113657.747Z

Thanks.
--- End Message ---
--- Begin Message ---
Source: human-icon-theme
Source-Version: 0.28.debian-6

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated human-icon-theme 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, 28 Dec 2018 10:34:16 -0500
Source: human-icon-theme
Binary: human-icon-theme
Architecture: source all
Version: 0.28.debian-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jeremy Bicha 
Description:
 human-icon-theme - Human Icon theme
Closes: 916463
Changes:
 human-icon-theme (0.28.debian-6) unstable; urgency=medium
 .
   * QA upload
   * Drop obsolete ubuntu-get-source rule (Closes: #916463)
Checksums-Sha1:
 83e3ec4d6079bf1ae5bea792106c919713a68fd8 2073 
human-icon-theme_0.28.debian-6.dsc
 9facfd68a32f59147464023b3102b480f645033a 27880 
human-icon-theme_0.28.debian-6.debian.tar.xz
 aae36719d90204ac09acfa5c4c5aa4fb3054ddca 11189 
human-icon-theme_0.28.debian-6_all.buildinfo
 75ef463bb83984ae40aa16a24057b08aea09218d 607272 
human-icon-theme_0.28.debian-6_all.deb
Checksums-Sha256:
 d1f4768ee19022acb6f83e80c77f63715d92077baf082551886aaac874f39f23 2073 
human-icon-theme_0.28.debian-6.dsc
 35674342c9c622dd303e88aa2253936b6e0640cf72d8ca70a99ee4b33e4bba92 27880 
human-icon-theme_0.28.debian-6.debian.tar.xz
 ae17d92025a3c4f0907bba08c91b85165577dfb06919aa0be7d33855a6607f16 11189 
human-icon-theme_0.28.debian-6_all.buildinfo
 fc135dc024ed52040a59e4a6a4bb378b32fa3f695b04f589ffa86771f539b612 607272 
human-icon-theme_0.28.debian-6_all.deb
Files:
 3b58f51651797bc2726069b587006467 2073 non-free/x11 optional 
human-icon-theme_0.28.debian-6.dsc
 4e3a9abf396a720166ed6e586decfc09 27880 non-free/x11 optional 
human-icon-theme_0.28.debian-6.debian.tar.xz
 01d767300b1dd475ca7ab4e20d4f1c10 11189 non-free/x11 optional 
human-icon-theme_0.28.debian-6_all.buildinfo
 6789b1f5d6b99c40cd1c366a5f8f2e34 607272 non-free/x11 optional 
human-icon-theme_0.28.debian-6_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlwmY1AACgkQ5mx3Wuv+

Processed: data/features directory is missing in node-caniuse-lite

[Debian Bug Tracking System]

Processing control commands:

> block 837463 by -1
Bug #837463 [ruby-autoprefixer-rails] ruby-autoprefixer-rails: contains 
embedded code copy of Javascript library Autoprefixer
837463 was not blocked by any bugs.
837463 was not blocking any bugs.
Added blocking bug(s) of 837463: 917562
> tag -1 help
Bug #917562 [node-caniuse-lite] data/features directory is missing in 
node-caniuse-lite
Added tag(s) help.

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

Bug#917562: data/features directory is missing in node-caniuse-lite

[Pirate Praveen]

Package: node-caniuse-lite
version: 1.0.3915+dfsg-1
severity: grave
Justification: Makes it unusable
Control: block 837463 by -1
Control: tag -1 help


When trying to build autoprefixer.js which build depends on
node-caniuse-lite, I got this error and upon inspection I found
data/features directory is missing.

ERROR in /usr/lib/nodejs/caniuse-lite/data/features.js
Module not found: Error: Can't resolve './features/aac' in
'/usr/lib/nodejs/caniuse-lite/data'
 @ /usr/lib/nodejs/caniuse-lite/data/features.js 1:22-47
 @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/features.js
 @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/index.js
 @ /usr/lib/nodejs/autoprefixer/lib/autoprefixer.js

I was not able to figure out why this is not working now. Need help.



signature.asc
Description: OpenPGP digital signature

Bug#917491: debian-installer-netboot-images: FTBFS (BAD signature from "Debian Archive Automatic Signing Key (8/jessie) ")

[Cyril Brulebois]

Hi Santiago,

Santiago Vila  (2018-12-27):
> Package: src:debian-installer-netboot-images
> Version: 20170615+deb9u5
> Severity: serious
> Tags: ftbfs

Thanks for the notice.

> gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
> gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
> gpgv: Can't check signature: No public key
> gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
> gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
> gpgv: BAD signature from "Debian Archive Automatic Signing Key (8/jessie) 
> "
> make[1]: *** [debian/rules:20: get-images-amd64] Error 1
> make[1]: Leaving directory 
> '/<>/debian-installer-netboot-images-20170615+deb9u5'
> make: *** [debian/rules:15: binary-indep] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
> returned exit status 2
> 

At first I thought this would be easily solved by moving from tracking
Debian 9 to tracking Debian 10, but here's what we get after the update:

+ gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg 
/home/kibi/debian-installer/packages/debian-installer-netboot-images/Release.gpg
 /home/kibi/debian-installer/packages/debian-installer-netboot-images/Release
gpgv: Signature made Sat 10 Nov 2018 10:12:51 UTC
gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
gpgv: Can't check signature: No public key
gpgv: Signature made Sat 10 Nov 2018 10:12:51 UTC
gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) 
"
gpgv: Signature made Sat 10 Nov 2018 10:18:21 UTC
gpgv:using RSA key 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500
gpgv: Good signature from "Debian Stable Release Key (9/stretch) 
"
make[1]: *** [debian/rules:19: get-images-amd64] Error 2

So gpgv exits with 2 because one of the signature couldn't be checked
due to a missing public key?

A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553 is:

Debian Archive Automatic Signing Key (7.0/wheezy) https://tracker.debian.org/news/998794/accepted-debian-archive-keyring-20181-source-into-unstable/


Back to reading the actual failure in the log you pasted, it's actually
a BAD signature, which is a bit worrying. I'll have to get back to that
later on.


In the meanwhile, I've pushed this:
  
https://salsa.debian.org/installer-team/debian-installer-netboot-images/commit/c59c0c2335052dce98810ce99775621292e630ec
  
https://salsa.debian.org/installer-team/debian-installer-netboot-images/commit/650baa18dba7f28db72c2f46b5dc82b0526c02e4

On a side note, there are a few things that needs getting done in d-a-k:

  https://bugs.debian.org/917535
  https://bugs.debian.org/917536

So possibly we're currently lacking a newer key, so ftp-master still
uses an old (Debian 7) key instead of a newer one, which explains the
failure to verify the buster builds?

Cc-ing packages@r.d.o for input.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#916452: gnome-shell: "Activities" and Dash freeze occasionally on Debian 9.6

[Jeremy Bicha]

Control: severity -1 normal

This kind of issue is often caused by using an incompatible GNOME
Shell extension.

Please try disabling all your GNOME Shell extensions, log out then log
back in and see if that fixes your issue. Or create a new user account
and log in with that account.

Please don't use a higher severity for your bug reports than is
appropriate. See https://www.debian.org/Bugs/Developer#severities

Thanks,
Jeremy Bicha

Processed: python-cymruwhois: diff for NMU version 1.6-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 917369 + patch
Bug #917369 [python3-cymruwhois] python-cymruwhois: please rebuild to remove 
dependency on Python 3.6
Added tag(s) patch.
> tags 917369 + pending
Bug #917369 [python3-cymruwhois] python-cymruwhois: please rebuild to remove 
dependency on Python 3.6
Added tag(s) pending.

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

Processed: Re: gnome-shell: "Activities" and Dash freeze occasionally on Debian 9.6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #916452 [gnome-shell] gnome-shell: "Activities" and Dash freeze 
occasionally on Debian 9.6
Severity set to 'normal' from 'grave'

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

Bug#917369: python-cymruwhois: diff for NMU version 1.6-3.1

[Mattia Rizzolo]

Control: tags 917369 + patch
Control: tags 917369 + pending


Dear maintainer,

I've prepared an NMU for python-cymruwhois (versioned as 1.6-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

diffoscope'ing the .debs the changes are only:

├── python3-cymruwhois_1.6-3.1_all.deb
│ ├── file list
│ │ @@ -1,3 +1,3 @@
│ │  -rw-r--r--   0004 2018-12-28 18:02:39.00 
debian-binary
│ │ --rw-r--r--   000 1384 2018-12-28 18:02:39.00 
control.tar.xz
│ │ +-rw-r--r--   000 1372 2018-12-28 18:02:39.00 
control.tar.xz
│ │  -rw-r--r--   000 6756 2018-12-28 18:02:39.00 
data.tar.xz
│ ├── control.tar.xz
│ │ ├── control.tar
│ │ │ ├── file list
│ │ │ │ @@ -1,5 +1,5 @@
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./
│ │ │ │ --rw-r--r--   0 root (0) root (0)  525 2018-12-28 
18:02:39.00 ./control
│ │ │ │ +-rw-r--r--   0 root (0) root (0)  510 2018-12-28 
18:02:39.00 ./control
│ │ │ │  -rw-r--r--   0 root (0) root (0)  894 2018-12-28 
18:02:39.00 ./md5sums
│ │ │ │  -rwxr-xr-x   0 root (0) root (0)  545 2018-12-28 
18:02:39.00 ./postinst
│ │ │ │  -rwxr-xr-x   0 root (0) root (0)  561 2018-12-28 
18:02:39.00 ./prerm
│ │ │ ├── ./control
│ │ │ │ @@ -1,14 +1,14 @@
│ │ │ │  Package: python3-cymruwhois
│ │ │ │  Source: python-cymruwhois
│ │ │ │  Version: 1.6-3.1
│ │ │ │  Architecture: all
│ │ │ │  Maintainer: Ana Custura 
│ │ │ │  Installed-Size: 36
│ │ │ │ -Depends: python3.7:any, python3:any
│ │ │ │ +Depends: python3:any
│ │ │ │  Suggests: python-cymruwhois-doc
│ │ │ │  Section: python
│ │ │ │  Priority: optional
│ │ │ │  Homepage: https://pythonhosted.org/cymruwhois/
│ │ │ │  Description: Python library for interfacing with the whois.cymru.com 
service (Python 3)
│ │ │ │   Perform lookups by ip address and return ASN,
│ │ │ │   Country Code, and Netblock Owner.
│ │ │ ├── ./md5sums
│ │ │ │ ├── ./md5sums
│ │ │ │ │┄ Files differ
│ ├── data.tar.xz
│ │ ├── data.tar
│ │ │ ├── file list
│ │ │ │ @@ -1,11 +1,11 @@
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/bin/
│ │ │ │ --rwxr-xr-x   0 root (0) root (0)  393 2018-12-28 
18:02:39.00 ./usr/bin/python3-cymruwhois
│ │ │ │ +-rwxr-xr-x   0 root (0) root (0)  391 2018-12-28 
18:02:39.00 ./usr/bin/python3-cymruwhois
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/lib/
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/lib/python3/
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/lib/python3/dist-packages/
│ │ │ │  drwxr-xr-x   0 root (0) root (0)0 2018-12-28 
18:02:39.00 ./usr/lib/python3/dist-packages/cymruwhois-1.6.egg-info/
│ │ │ │  -rw-r--r--   0 root (0) root (0) 1101 2018-12-28 
18:02:39.00 ./usr/lib/python3/dist-packages/cymruwhois-1.6.egg-info/PKG-INFO
│ │ │ │  -rw-r--r--   0 root (0) root (0)1 2018-12-28 
18:02:39.00 
./usr/lib/python3/dist-packages/cymruwhois-1.6.egg-info/dependency_links.txt
│ │ │ │  -rw-r--r--   0 root (0) root (0)   56 2018-12-28 
18:02:39.00 
./usr/lib/python3/dist-packages/cymruwhois-1.6.egg-info/entry_points.txt
│ │ │ ├── ./usr/bin/python3-cymruwhois
│ │ │ │ @@ -1,8 +1,8 @@
│ │ │ │ -#!/usr/bin/python3.7
│ │ │ │ +#!/usr/bin/python3
│ │ │ │  # EASY-INSTALL-ENTRY-SCRIPT: 
'cymruwhois==1.6','console_scripts','cymruwhois'
│ │ │ │  __requires__ = 'cymruwhois==1.6'
│ │ │ │  import re
│ │ │ │  import sys
│ │ │ │  from pkg_resources import load_entry_point
│ │ │ │
│ │ │ │  if __name__ == '__main__':


And similarly for the python2 one.



Regards.


-- 
regards,
Mattia Rizzolo

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

 changelog |8 
 rules |   14 +-
 2 files changed, 9 insertions(+), 13 deletions(-)

diff -Nru python-cymruwhois-1.6/debian/changelog python-cymruwhois-1.6/debian/changelog
--- python-cymruwhois-1.6/debian/changelog	2018-07-24 17:20:02.0 +0200
+++ python-cymruwhois-1.6/debian/changelog	2018-12-28 19:07:06.0 +0100
@@ -1,3 +1,11 @@

Bug#910075: evolution crash on interact

[Jeremy Bicha]

Control: severity -1 important

There isn't enough information here for us to do anything.

Can you still reproduce this issue with the newest evolution in
Debian? Can you reproduce from a clean user profile and install?

Can you provide a test case?

I'm lowering the severity of this issue since there have been no other
similar reports in 3 months. And there isn't a clear fixable bug here.

Thanks,
Jeremy Bicha

Processed: Re: evolution crash on interact

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #910075 [evolution] evolution crash on interact
Severity set to 'important' from 'grave'

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

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Santiago Vila]

On Fri, Dec 28, 2018 at 07:51:27PM +0200, Tommi Höynälänmaa wrote:
> Hi
> 
> > Is there a pending upload of guile-gnome-platform for unstable which
> > is required for theme-d-gnome to build properly also in unstable?
> > 
> > Note: The build log says --with-guile-gnome=2.16.5 but current version
> > is 2.16.4-5. Could this small mismatch be the problem?
> 
> This may cause problems but the main thing is that packages
> theme-d-translator and theme-d-stdlib are not present in the build
> environment (at least the correct versions are not).

Hmm, but I'm not installing build-dependencies by hand.

I'm using sbuild (and reproducible-builds is using pbuilder)
which should already ensure that the "correct" versions are installed.

Actually, either the version currently available in unstable is ok,
or otherwise the build would fail with "unsatisfiable build-depends".

So: How do you know that the build is using "incorrect versions" and
what exactly do you mean by "incorrect versions"?

I'm a little bit confused.

Thanks.

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Tommi Höynälänmaa]

Hi again


On 28.12.2018 19:14, Santiago Vila wrote:


Is there a pending upload of guile-gnome-platform for unstable which
is required for theme-d-gnome to build properly also in unstable?


Yes, version 2.6.15-2. However, it might be possible to build (but not 
use) theme-d-gnome without guile-gnome-platform.




Note: The build log says --with-guile-gnome=2.16.5 but current version
is 2.16.4-5. Could this small mismatch be the problem?

Thanks.


Generally, the argument of --with-guile-gnome should be the version of 
guile-gnome-platform in the build environment.


 - Tommi

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Tommi Höynälänmaa]

Hi

Actually, correct version of debhelper is not installed either.

 - Tommi

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Tommi Höynälänmaa]

Hi


Is there a pending upload of guile-gnome-platform for unstable which
is required for theme-d-gnome to build properly also in unstable?

Note: The build log says --with-guile-gnome=2.16.5 but current version
is 2.16.4-5. Could this small mismatch be the problem?




This may cause problems but the main thing is that packages 
theme-d-translator and theme-d-stdlib are not present in the build 
environment (at least the correct versions are not).  Those packages are 
listed in build-depends of package theme-d-gnome.


 - Tommi

Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Cyril Brulebois]

Hi,

Santiago Vila  (2018-12-28):
> On Fri, Dec 28, 2018 at 03:48:06AM +0100, Cyril Brulebois wrote:
> 
> > > but it also fails here:
> > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/honeysql-clojure.html
> > 
> > Last build there seems OK as well.
> 
> Yes, but only the last amd64 build. The last i386 build, which is not
> very old, shows the same kind of failure I reported, which suggests
> that the problem, random in nature, still seems to be there.

Oh sorry, was only discovering the r-b.o interface and I seem to have
missed it…

> Double-checked today on both 1-XS and 1-S instances from Scaleway and
> I still get a 100% failure rate. I've put a bunch of build logs here:
> 
> https://people.debian.org/~sanvila/build-logs/honeysql-clojure/
> 
> I can offer a test machine where this happens all the time if you need
> it to reproduce it. Please contact me privately for details.

This would be super-useful, as I might have a tentative patch but can't
reproduce the issue in various setups. Will follow-up privately.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#917518: marked as done (python-matplotlib: WxAgg backend cannot find fonts)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 17:22:41 +
with message-id 
and subject line Bug#917518: fixed in matplotlib2 2.2.3-5
has caused the Debian Bug report #917518,
regarding python-matplotlib: WxAgg backend cannot find fonts
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.)


-- 
917518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-matplotlib
Version: 2.2.3-4
Severity: important

Dear Maintainers,

Since the update to python-matplotlib2, the WxAgg backend is unable to find any
fonts. The following code used to work just fine (and works fine in buster
with python-matplotlib 2.2.2-4+b1):

# apt-get install python-matplotlib python-wxgtk3.0
# python -c 'import matplotlib.backends.backend_wxagg.FigureCanvasWxAgg'
/usr/lib/python2.7/dist-packages/matplotlib/__init__.py:1005: UserWarning: 
could not find rc file; returning defaults
  warnings.warn(message)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_wxagg.py", 
line 11, in 
from .backend_agg import FigureCanvasAgg
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_agg.py", 
line 36, in 
from matplotlib.backend_bases import (
  File "/usr/lib/python2.7/dist-packages/matplotlib/backend_bases.py", line 53, 
in 
from matplotlib import (
  File "/usr/lib/python2.7/dist-packages/matplotlib/textpath.py", line 17, in 

import matplotlib.font_manager as font_manager
  File "/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py", line 
1472, in 
_rebuild()
  File "/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py", line 
1453, in _rebuild
fontManager = FontManager()
  File "/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py", line 
1057, in __init__
paths = [os.path.join(rcParams['datapath'], 'fonts', 'ttf'),
  File "/usr/lib/python2.7/posixpath.py", line 70, in join
elif path == '' or path.endswith('/'):
AttributeError: 'NoneType' object has no attribute 'endswith'

The WxAgg backend is used by python-bumps and sasmodels; the inability to
import the module means that these packages FTBFS and their autopkgtest tests
fail.

I can't see any changes in the packaging that would cause this but I also
can't see any relevant changes in the upstream backend or font handling code.
There are some changes in the initialisation of the matplotlib config but I
don't see any documented changes in the upstream changelog for requiring
initialisation of rcParams prior to importing backends.

If changes in the rdeps are needed, I can make them, but hints would be
gratefully received.

thanks
Stuart

Comparison logs from ci.d.n:

buster
https://ci.debian.net/data/autopkgtest/testing/amd64/s/sasview/1563832/log.gz

unstable
https://ci.debian.net/data/autopkgtest/testing/amd64/s/sasview/1563833/log.gz

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python-matplotlib depends on:
ii  libc6 2.28-3
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-13
ii  libjs-jquery  3.2.1-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libpng16-16   1.6.36-1
ii  libstdc++68.2.0-13
ii  python2.7.15-3
ii  python-backports.functools-lru-cache  1.5-1
ii  python-cycler 0.10.0-1
ii  python-dateutil   2.7.3-1
ii  python-kiwisolver 1.0.1-2+b1
ii  python-matplotlib2-data   2.2.3-4
ii  python-numpy [python-numpy-abi9]  1:1.16.0~rc1-2
ii  python-pyparsing  2.2.0+dfsg1-2
ii  python-six1.12.0-1
ii  python-subprocess32   3.5.3-1
ii  python-tz 2018.7-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages python-matplotlib recommends:
ii  python-pil  5.3.0-1
ii  python-tk   2.7.15-1+b1

Versions of packages python-matplotlib suggests:
pn  dvipng  
pn  ffmpeg  
pn  ghostscript 
pn  gir1.2-gtk-3.0  
pn  inkscape
pn  ipython   

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Santiago Vila]

> > However, I see that 0.7.4-1 still fails in reproducible-builds.
> > 
> > Is the failure in reproducible-builds different than the one I got in
> > testing? Can you take a look at the failure in reproducible-builds?
> > 
> > Thanks.
> 
> Which version of guile-gnome-platform do you use?

Hmm, I don't really know. I specifically refer to the latest build of
theme-d-gnome in unstable in reproducible-builds, namely:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/theme-d-gnome_0.7.4-1.rbuild.log.gz

So the answer would be "whatever version of guile-gnome-platform is
also in unstable".

Is there a pending upload of guile-gnome-platform for unstable which
is required for theme-d-gnome to build properly also in unstable?

Note: The build log says --with-guile-gnome=2.16.5 but current version
is 2.16.4-5. Could this small mismatch be the problem?

Thanks.

Processed: Bug #888549 in chrome-gnome-shell marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888549 [chrome-gnome-shell] chrome-gnome-shell: Please don't use /etc/opt, 
it's not FHS-compliant
Added tag(s) pending.

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

Bug#888549: Bug #888549 in chrome-gnome-shell marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #888549 in chrome-gnome-shell 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/gnome-team/chrome-gnome-shell/commit/680b73733e541c146d0c5c073cf738a8327d1c2d


Use debian/postinst and debian/postrm to handle the Chrome conffile

Closes: #888549


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/888549

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Tommi Höynälänmaa]

Hi


On 28.12.2018 12:36, Santiago Vila wrote:


However, I see that 0.7.4-1 still fails in reproducible-builds.

Is the failure in reproducible-builds different than the one I got in
testing? Can you take a look at the failure in reproducible-builds?

Thanks.


Which version of guile-gnome-platform do you use?

  - Tommi

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[Georg Richter]

About the reconnect bug:

Latest code is setting the reconnect flag correctly via mysql_options
(instead of accessing internal member), so I need to  debug why it's
failing.

/Georg

On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann  wrote:

> On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen wrote:
>
> > pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com)
> kirjoitti:
> > > no clue about dbd-mysql - we reported several bugs (and sent
> > > fixes), but didn't get feedback since more than a year. Why don't
> > > you ship DBD-mariadb instead?
> > Gregor Hermann, do you want to switch to DBD-mariadb instead?
>
> DBD-mariadb is in the archive since a couple of months:
> https://tracker.debian.org/libdbd-mariadb-perl
>
> Unfortunately, it's not a 1:1 replacement for DBD-mysql and many user
> will want to continue using the latter in their existing codebase.
>
> Georg, maybe you can give us pointers to the bugs and fixes you
> mentioned above?
>
>
> 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: Penelope Swales: Turning Point
>


-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[Georg Richter]

Hi,

the zerofill test fails, since dbd-mysql binds a buffer with
buffer_length=1, so MariaDB Connector/C can't add leading zeros and just
returns 1.

Perl seems to retrieve the information from metadata after
mysql_stmt_store_result() call. According to the documentation (
https://dev.mysql.com/doc/refman/8.0/en/mysql-stmt-attr-set.html) you have
to call mysql_stmt_attr_set(stmt, STMT_ATTR_UPDATE_MAX_LENGTH, ) to
force mysql_stmt_store_result to update the max_length value in metadata -
however its not set and therefore Connector/C doesn't return expected value.

The correct behavior would be to check the metadata after
mysql_stmt_prepare() and calculate the buffer_size or to force Connector/C
to calculate the size via STMT_ATTR_UPDATE_MAX_LENGTH. I would prefer the
latter one, since in some cases metadata after prepare can't be calculated
correctly, e.g. for a "SELECT ? FROM DUAL"

/Georg

On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann  wrote:

> On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen wrote:
>
> > pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com)
> kirjoitti:
> > > no clue about dbd-mysql - we reported several bugs (and sent
> > > fixes), but didn't get feedback since more than a year. Why don't
> > > you ship DBD-mariadb instead?
> > Gregor Hermann, do you want to switch to DBD-mariadb instead?
>
> DBD-mariadb is in the archive since a couple of months:
> https://tracker.debian.org/libdbd-mariadb-perl
>
> Unfortunately, it's not a 1:1 replacement for DBD-mysql and many user
> will want to continue using the latter in their existing codebase.
>
> Georg, maybe you can give us pointers to the bugs and fixes you
> mentioned above?
>
>
> 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: Penelope Swales: Turning Point
>


-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#893821: marked as done (ruby-shindo FTBFS with Ruby 2.5)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 16:32:59 +
with message-id 
and subject line Bug#893821: fixed in ruby-shindo 0.3.8-2
has caused the Debian Bug report #893821,
regarding ruby-shindo FTBFS with Ruby 2.5
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.)


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

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

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

RUBYLIB=/build/1st/ruby-shindo-0.3.8/debian/ruby-shindo/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-shindo/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 debian/ruby-tests.rb
  
  Shindo build errors (build_error)
another + returns true
  
  tag
negative -negative
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "+ is tested"
expected "" to include "+ is tested"
  - includes "skipped (negative)"
expected "" to include "skipped (negative)"
  $?.exitstatus - returns 0
expected => 0
returned => 1
positive +positive
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "+ is tested"
expected "" to include "+ is tested"
  - includes "skipped"
expected "" to include "skipped"
  $?.exitstatus - returns 0
expected => 0
returned => 1
  
  basics
+ returns false
+ raises StandardError
+ returns true
  
  bin
exception
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "- exception"
expected "" to include "- exception"
  $?.exitstatus + returns 1
failure
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "- failure"
expected "" to include "- failure"
  $?.exitstatus + returns 1
pending
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "# test implicit pending"
expected "" to include "# test implicit pending"
  - includes "# test explicit pending"
expected "" to include "# test explicit pending"
  - includes "# tests explicit pending"
expected "" to include "# tests explicit pending"
  $?.exitstatus - returns 0
expected => 0
returned => 1
success
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
  - includes "+ success"
expected "" to include "+ success"
  - includes "inline tests"
expected "" to include "inline tests"
  - includes "+ returns false"
expected "" to include "+ returns false"
  $?.exitstatus - returns 0
expected => 0
returned => 1
  
  16 failed, 6 succeeded in 20.775533539 seconds
  
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-shindo-0.3.8/debian/ruby-shindo returned exit code 1
make: *** [debian/rules:17: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-shindo
Source-Version: 0.3.8-2

We believe that the bug you reported is fixed in the latest version of
ruby-shindo, 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 

Bug#917554: zutils: Fails to upgrade: preinst called with unknown argument `upgrade'

[Axel Beckert]

Package: zutils
Version: 1.7-7
Severity: serious

zutils fails to upgrade from 1.7-6 to 1.7-7 as follows for me:

Preparing to unpack .../60-zutils_1.7-7_amd64.deb ...
preinst called with unknown argument `upgrade'
dpkg: error processing archive 
/tmp/apt-dpkg-install-9FRsIU/60-zutils_1.7-7_amd64.deb (--unpack):
 new zutils package pre-installation script subprocess returned error exit 
status 1
Errors were encountered while processing:
 /tmp/apt-dpkg-install-9FRsIU/60-zutils_1.7-7_amd64.deb

I suspect that this is caused by this change in 1.7-7:

  * Dropping temporary upgrade handling from 1.7-2, not needed anymore.

Probably too much has been removed from preinst.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages zutils depends on:
ii  libc6   2.28-3
ii  libgcc1 1:8.2.0-13
ii  libstdc++6  8.2.0-13

Versions of packages zutils recommends:
ii  bzip2 1.0.6-9
ii  lzip  1.20-4
ii  xz-utils  5.2.2-1.3

zutils suggests no packages.

-- no debconf information

Bug#916158: marked as done (libfm-qt FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 16:24:06 +
with message-id 
and subject line Bug#916158: fixed in libfm-qt 0.13.1-10
has caused the Debian Bug report #916158,
regarding libfm-qt FTBFS: symbol differences
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.)


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

Some recent change in unstable makes libfm-qt FTBFS:

https://tests.reproducible-builds.org/debian/history/libfm-qt.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libfm-qt.html

...
   dh_makeshlibs -O--buildsystem=cmake
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libfm-qt5/DEBIAN/symbols doesn't match 
completely debian/libfm-qt5.symbols
--- debian/libfm-qt5.symbols (libfm-qt5_0.13.1-9_amd64)
+++ dpkg-gensymbolsN4ByOk   2020-01-12 12:43:01.058509823 -1200
@@ -1051,6 +1051,7 @@
  (c++)"Fm::uidFromName(QString)@Base" 0.10.0
  (c++)"Fm::uidToName(unsigned int)@Base" 0.10.0
  (c++)"Fm::uriExists(char const*)@Base" 0.10.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 0.13.1-9
  (c++)"non-virtual thunk to 
Fm::AppChooserComboBox::~AppChooserComboBox()@Base" 0.10.0
  (c++)"non-virtual thunk to Fm::AppChooserDialog::~AppChooserDialog()@Base" 
0.10.0
  (c++)"non-virtual thunk to Fm::AppMenuView::~AppMenuView()@Base" 0.10.0
@@ -1350,7 +1351,7 @@
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, (__gnu_cxx::_Lock_policy)2>@Base" 0.12.0
  (optional|c++|arch=  armel  riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, 
std::allocator >, std::allocator, std::allocator > >, 
(__gnu_cxx::_Lock_policy)1>@Base" 0.12.0
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, 
std::allocator >, std::allocator, std::allocator > >, 
(__gnu_cxx::_Lock_policy)2>@Base" 0.12.0
- (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 0.12.0
+#MISSING: 0.13.1-9# (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 0.12.0
  (c++)"typeinfo name for Fm::AppChooserComboBox@Base" 0.10.0
  (c++)"typeinfo name for Fm::AppChooserDialog@Base" 0.10.0
  (c++)"typeinfo name for Fm::AppMenuView@Base" 0.10.0
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:9: binary] Error 2
--- End Message ---
--- Begin Message ---
Source: libfm-qt
Source-Version: 0.13.1-10

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated libfm-qt 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, 28 Dec 2018 16:41:09 +0100
Source: libfm-qt
Binary: libfm-qt5 libfm-qt-dev
Architecture: source
Version: 0.13.1-10
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 libfm-qt-dev - file management support library for pcmanfm-qt (development 
files
 libfm-qt5  - file management support for pcmanfm-qt
Closes: 916158
Changes:
 libfm-qt (0.13.1-10) unstable; urgency=medium
 .
   * Added Build-Depends-Package: libfm-qt-dev to libfm-qt-dev.symbols
   * Bumped Standards to 4.2.1
   * Fixed the first symbols (Closes: #916158)
Checksums-Sha1:
 c3bcb4df10127e4717ff37e7f566ca7c69c15575 1945 libfm-qt_0.13.1-10.dsc
 65a67ed153e10d20fec2b551579305da62f7a261 19656 libfm-qt_0.13.1-10.debian.tar.xz
 b4453c786b75af0629aba1b0477970cdd0ee2aac 12942 
libfm-qt_0.13.1-10_source.buildinfo
Checksums-Sha256:
 0bb3dee47d0b8f52e08af00df37d4ff66aa8fad8c0ea9006b528a09a3418cc04 1945 
libfm-qt_0.13.1-10.dsc
 eac2a00f078c698ef356669ee30a4b6727bc78db3809f369a34a7e54a78800f8 19656 
libfm-qt_0.13.1-10.debian.tar.xz
 52d3c55ed68c6d5c5c07053b32a1df2e21e462fe840808e1085ec4a7ed68b792 12942 
libfm-qt_0.13.1-10_source.buildinfo
Files:
 

Bug#917518: python-matplotlib: WxAgg backend cannot find fonts

[Sandro Tosi]

> # python -c 'import matplotlib.backends.backend_wxagg.FigureCanvasWxAgg'
> /usr/lib/python2.7/dist-packages/matplotlib/__init__.py:1005: UserWarning: 
> could not find rc file; returning defaults

during the split of src:matplotlib and src:matplotlib2, now
/etc/matplotlibrc belongs to python-matplotlib-data, which is only
pulled in by python3-matplotlib.

I'm going to install a new /etc/matplotlibrc2 file in python-matplotlib.

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

Bug#917124: fixed in systemd 240-2

[Steven Monai]

On Thu, 27 Dec 2018 13:55:36 + Michael Biebl  wrote:
> Source: systemd
> Source-Version: 240-2
> 
> We believe that the bug you reported is fixed in the latest version of
> systemd, which is due to be installed in the Debian FTP archive.

I confirm that udev 240-2 fixes the problem of my root LV going "missing".

The (less pressing) problem of the lvm2-activation-generator failing
with non-zero exit status remains, but, as was mentioned in a reply to
another bug respondent, that issue is covered by a different bug (#917164).

Thanks to all for their efforts!

/-S.M.

Bug#917493: fenix: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Hi.

I wonder why generating an arch:all package would require to compile
anything at all.

Is fenix-dev_0.92a.dfsg1-11.1_all.deb still the one it should be
when the package is modified with the attached patch?

(Also: Is the i386 package still generated correctly?)

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -14,7 +14,9 @@ CFLAGS += -DUSE_GETTEXT
 LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS)
 LDFLAGS += -Wl,-z,defs
 
-override_dh_auto_configure:
+override_dh_auto_configure-indep:
+
+override_dh_auto_configure-arch:
chmod +x configure
dh_auto_configure -- \
--enable-fxc \
@@ -27,7 +29,9 @@ override_dh_auto_configure:
LDFLAGS="$(LDFLAGS)" \
LIBS="-lm -ldl"
 
-override_dh_auto_build:
+override_dh_auto_build-indep:
+
+override_dh_auto_build-arch:
dh_auto_build -- CFLAGS="$(CFLAGS)"
$(MAKE) -C debian/i18n
 
@@ -35,7 +39,9 @@ override_dh_auto_clean:
dh_auto_clean
$(MAKE) -C debian/i18n clean
 
-override_dh_auto_install:
+override_dh_auto_install-indep:
+
+override_dh_auto_install-arch:
dh_auto_install
cd $(CURDIR)/debian/tmp/usr/bin/ && \
for f in *; do \

Bug#917266: [debian-mysql] Bug#917266: Bug#917266: missing /usr/include/mysql

[Otto Kekäläinen]

Hello!

pe 28. jouluk. 2018 klo 15.33 Scott Kitterman (deb...@kitterman.com) kirjoitti:
>
> I did add a symlink as in the attached patch and postfix builds again.  I
> don't have a good way to do run-time testing, so I don't know if there are any
> further changes needed, but this at least fixes package building.

If you use Salsa to make a merge request you will get gitlab-ci
testing for free, also run-time.

See easy instructions at https://wiki.debian.org/Teams/MySQL/patches

I really strongly recommend you take a shot at using Salsa and
Gitlab-CI that it has built-in.

Bug#916764: znc-backlog: overly strict dependency on znc?

[Patrick Matthäi]

Am 28.12.2018 um 15:02 schrieb Felipe Sateler:
>
>
> On Fri, Dec 28, 2018 at 10:33 AM Patrick Matthäi  > wrote:
>
> Hola,
>
> Am 24.12.2018 um 12:44 schrieb Felipe Sateler:
>> > Perhaps znc could Provide: znc-plugin-$somenumber, which could
>> be used by
>>
>> > out-of-tree plugins? Adding the znc maintainers to the loop
>> for their input
>>
>> That's being used successfully by some packages ...
>>
>>
>> I'm creating a new bug for tracking this (better) solution.
>
>
> I dont know how this would help now after the relaxed dependency
> from znc-backlog, because..:
>
> * on changes znc-backlog still needs a binNMU or code changes,
> like now
>
>
> Right. But the current solution is still suboptimal. For example, if
> you upload a new package changing only metadata (say, the Vcs-*
> fields), znc-backlog would need a binNMU. In the more general case, a
> new upstream version of znc might not break the plugin ABI.
>  
>
> * I can provide a znc-plugin-$foobar package, but who ensures at
> an non stable api, if a change is necessary or not? I think it
> will make it more complicated or is there a nice solution for it?
>
> Indeed, this implies a lot more work for you.
>
>
Where a binNMU would be more safe and less work

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Processed: Marking ebtables & arptables bugs as pending

[Debian Bug Tracking System]

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

> tags 916106 + pending
Bug #916106 [arptables] arptables provides the same executables as iptables 
packages without using alternatives
Added tag(s) pending.
> tags 912046 + pending
Bug #912046 [ebtables] ebtables provides the same executables as iptables 
packages without using alternatives
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#917493: fenix: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

I wrote:

> but it also fails here:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fenix.html

Please disregard this part of my report.

Reproducible builds always do "dpkg-buildpackage", so whatever
happens in reproducible-builds is irrelevant in this case, because we
know no amd64 .deb will be generated.

This report is only about "dpkg-buildpackage -A", which in theory must
still work and in practice should not be very difficult to achieve
(well, I hope so).

Tbanks.

Processed: Bug#917493

[Debian Bug Tracking System]

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

> retitle 917493 fenix: FTBFS when built with dpkg-buildpackage -A
Bug #917493 [src:fenix] fenix: FTBFS (conflicting types for 'fmul')
Changed Bug title to 'fenix: FTBFS when built with dpkg-buildpackage -A' from 
'fenix: FTBFS (conflicting types for 'fmul')'.
> thanks
Stopping processing here.

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

Bug#917493:

[Santiago Vila]

retitle 917493 fenix: FTBFS when built with dpkg-buildpackage -A
thanks

This title reflects a lot better what I was really reporting.

I'm not really asking this package to be buildable on 64-bit archs,
I'm just trying to ensure that every package generating arch:all
packages is buildable on the official buildds. This is still RC
but hopefully easier to achieve than #456037.

Thanks.