Bug#916768: closed by Mark Hindley (Re: Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1))
Control: reopen 916750 Hi Mark, On Wed, Dec 19, 2018 at 06:39:04PM +, Debian Bug Tracking System wrote: > Package: libelogind-dev-doc > Version: 239.3-4+debian1 > > Closing manually as upload had typo in bug number. > > Sorry. If you noticed your mistake and closed the right bug now, why didn't you reopen the bug you erroneously closed? Doing so now. Helmut
Bug#916683: libgnutls30: breaks msmtp 1.6.7-1
On 2018-12-18 Andreas Metzler wrote: > On 2018-12-17 Jonas Smedegaard wrote: [...] > > The hosts I experienced problems with are mail.jones.dk and > > mail.homebase.dk - both running Postfix on Debian stable (which made me [...] > Thanks! FWIW as a temporary workaround you can invoke msmtp with > --tls-priorities=NORMAL:-VERS-TLS1.3 I have just tested with msmtp 1.8.1, it works. cu Andreas -- `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'
Processed: Re: Bug#916799: dpkg: update-alternatives does not properly deregister obsolete slaves if the link group is currently broken
Processing control commands: > severity -1 normal Bug #916799 [dpkg] dpkg: update-alternatives does not properly deregister obsolete slaves if the link group is currently broken Severity set to 'normal' from 'serious' -- 916799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916799: dpkg: update-alternatives does not properly deregister obsolete slaves if the link group is currently broken
Control: severity -1 normal
Hi!
On Tue, 2018-12-18 at 19:28:35 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.19.2
> Severity: serious
> Control: found -1 1.18.25
> there is a problem with update-alternatives not properly deregistering
> obsolete slaves:
> ==
> #!/bin/sh
>
> update-alternatives --version
> update-alternatives --remove-all foobar
>
> set -x
> touch /foo /foo.1
> touch /bar /bar.1
> update-alternatives --display foobar
> update-alternatives --install /foobar foobar /foo 23 --slave /foobar.1
> foobar-1 /foo.1 --slave /barfoo barfoo /bar --slave /barfoo.1 barfoo-1 /bar.1
> update-alternatives --display foobar
> rm /bar /bar.1
> update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1
> foobar-1 /foo.1
> update-alternatives --display foobar
> update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1
> foobar-1 /foo.1
> update-alternatives --display foobar
> ==
Thanks for the reproducer, much appreciated!
> # ./foobar.sh
[…]
> So this is reproducible in stretch, too, but not in jessie.
It is actually reproducible in both, it is just not obviosly visible
in jessie. What made this visible was the change from commit
55661248cc3028446b9e73eb17e41fa12aad2b54 which started printing the
master and slave links on --display. But if you check the database
(/var/lib/dpkg/alternatives/foobar) you'll see they are present even
in 1.17.x and earlier. I've not checked whether the perl implementation
suffered the same problem, but I assume it did not, and it seems this
was a regression from the C rewrite.
> The problem does not occur if there is only a single broken slave to be
> removed.
Right, because this is a problem with the way the slave links are
removed from the single linked list.
I've lowered the severity, because this is a self-healing problem, and
on each new call the remaining obsolete slave links will get removed,
even if slowly. :)
The attached patch should fix it.
Thanks,
Guillem
diff --git i/utils/update-alternatives.c w/utils/update-alternatives.c
index 88db6e274..79dbd10c7 100644
--- i/utils/update-alternatives.c
+++ w/utils/update-alternatives.c
@@ -1373,7 +1373,7 @@ alternative_save(struct alternative *a)
/* Cleanup unused slaves before writing admin file. */
sl_prev = NULL;
- for (sl = a->slaves; sl; sl_prev = sl, sl = sl->next) {
+ for (sl = a->slaves; sl; ) {
bool has_slave = false;
for (fs = a->choices; fs; fs = fs->next) {
@@ -1393,10 +1393,11 @@ alternative_save(struct alternative *a)
else
a->slaves = sl->next;
sl_rm = sl;
- sl = sl_prev ? sl_prev : a->slaves;
+ sl = sl->next;
slave_link_free(sl_rm);
- if (!sl)
-break; /* No other slave left. */
+ } else {
+ sl_prev = sl;
+ sl = sl->next;
}
}
Bug#916900: Fails to install: installed dash package post-installation script subprocess returned error exit status 1
Package: dash Version: 0.5.10.2-3 Severity: serious When running "debootstrap sid /path/to/chroot", dash fails to install Setting up dash (0.5.10.2-3) ... dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x No diversion 'diversion of /bin/sh by dash', none removed. This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Setting up init-system-helpers (1.56+nmu1) ... Setting up libpam0g:amd64 (1.1.8-3.8) ... Setting up libpam-modules-bin (1.1.8-3.8) ... Setting up libpam-modules:amd64 (1.1.8-3.8) ... Setting up libpam-runtime (1.1.8-3.8) ... Setting up passwd (1:4.5-1.1) ... Shadow passwords are now on. Setting up login (1:4.5-1.1) ... Setting up adduser (3.118) ... Setting up util-linux (2.33-0.2) ... update-alternatives: using /bin/more to provide /usr/bin/pager (pager) in auto mode Setting up mount (2.33-0.2) ... Setting up sysvinit-utils (2.93-1) ... Setting up apt (1.8.0~alpha3) ... Processing triggers for libc-bin (2.28-3) ... Errors were encountered while processing: dash Full debootstrap log attached. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dash depends on: ii debconf [debconf-2.0] 1.5.69 ii debianutils4.8.6 ii dpkg 1.19.2+test3 ii libc6 2.28-3 dash recommends no packages. dash suggests no packages. -- debconf information: * dash/sh: true amd64: ok 2018-12-20 04:24:57 URL:http://cdn-fastly.deb.debian.org/debian/dists/sid/InRelease [237339/237339] -> "/srv/chroot/sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_InRelease" [1] gpgv: Signature made Wed Dec 19 21:25:00 2018 CET gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553 gpgv: Can't check signature: No public key gpgv: Signature made Wed Dec 19 21:25:00 2018 CET gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010 gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) " gpgv: Signature made Wed Dec 19 21:25:00 2018 CET gpgv:using RSA key 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC gpgv: Good signature from "Debian Archive Automatic Signing Key (9/stretch) " 2018-12-20 04:25:00 URL:http://cdn-fastly.deb.debian.org/debian/dists/sid/main/binary-amd64/by-hash/SHA256/34a6a23bd86422b82eb3b10fa606fdc78ad949bf7fee82bfda7a0487cc0a73fb [8313264/8313264] -> "/srv/chroot/sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_main_binary-amd64_Packages.xz" [1] 2018-12-20 04:25:54 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/acl/libacl1_2.2.52-3+b1_amd64.deb [28110/28110] -> "/srv/chroot/sid//var/cache/apt/archives/partial/libacl1_2.2.52-3+b1_amd64.deb" [1] 2018-12-20 04:25:54 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/adduser/adduser_3.118_all.deb [240384/240384] -> "/srv/chroot/sid//var/cache/apt/archives/partial/adduser_3.118_all.deb" [1] 2018-12-20 04:25:55 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/apparmor/libapparmor1_2.13.1-3+b1_amd64.deb [92824/92824] -> "/srv/chroot/sid//var/cache/apt/archives/partial/libapparmor1_2.13.1-3+b1_amd64.deb" [1] 2018-12-20 04:25:55 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/apt/apt_1.8.0~alpha3_amd64.deb [1307568/1307568] -> "/srv/chroot/sid//var/cache/apt/archives/partial/apt_1.8.0~alpha3_amd64.deb" [1] 2018-12-20 04:25:56 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/apt/apt-utils_1.8.0~alpha3_amd64.deb [421680/421680] -> "/srv/chroot/sid//var/cache/apt/archives/partial/apt-utils_1.8.0~alpha3_amd64.deb" [1] 2018-12-20 04:25:56 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/apt/libapt-inst2.0_1.8.0~alpha3_amd64.deb [202792/202792] -> "/srv/chroot/sid//var/cache/apt/archives/partial/libapt-inst2.0_1.8.0~alpha3_amd64.deb" [1] 2018-12-20 04:25:56 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/apt/libapt-pkg5.0_1.8.0~alpha3_amd64.deb [958172/958172] -> "/srv/chroot/sid//var/cache/apt/archives/partial/libapt-pkg5.0_1.8.0~alpha3_amd64.deb" [1] 2018-12-20 04:25:57 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/argon2/libargon2-1_0~20171227-0.1_amd64.deb [20600/20600] -> "/srv/chroot/sid//var/cache/apt/archives/partial/libargon2-1_0~20171227-0.1_amd64.deb" [1] 2018-12-20 04:25:57 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/a/attr/libattr1_2.4.47-2+b2_amd64.deb [18356/18356] ->
Processed: Re: dash: Update dpkg-divert usage
Processing control commands: > severity -1 minor Bug #916319 [src:dash] dash: Update dpkg-divert usage Severity set to 'minor' from 'serious' -- 916319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916319: dash: Update dpkg-divert usage
Control: severity -1 minor Am 20.12.18 um 04:31 schrieb Michael Biebl: . > Errors were encountered while processing: > dash > > Bumping the bug report to serious given this failure. > > Hm, probably better to file a new bug report with proper version tracking to prevent testing migration. Restoring original severity. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916879: qtox: missing library libsodium.so.18
$ sudo apt install --reinstall qtox [...] $ ldd /usr/bin/qtox | grep sod libsodium.so.23 => /usr/lib/x86_64-linux-gnu/libsodium.so.23 (0x7f8415cc9000) $ ll /usr/lib/x86_64-linux-gnu/libsodium.so* lrwxrwxrwx 1 root root 19 12月 26 2017 /usr/lib/x86_64-linux-gnu/libsodium.so.23 -> libsodium.so.23.1.0 -rw-r--r-- 1 root root 331K 12月 26 2017 /usr/lib/x86_64-linux-gnu/libsodium.so.23.1.0
Processed: Re: dash: Update dpkg-divert usage
Processing control commands: > severity -1 serious Bug #916319 [src:dash] dash: Update dpkg-divert usage Severity set to 'serious' from 'minor' -- 916319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915886: Workaround
So, yes, the workaround Ben posted will work, but that's fixing the symptom, not the problem. I'd still like to know what the enum-extract.pl script says for you (Ben) if you try invoking it (or what's in config.log when it fails). Because the problem with the common/amd64 headers location should be fixed already [1], it's possible you're having a separate problem; that error output is just what happens when enum-extract.pl doesn't output what's expected. - Rich [1] - https://github.com/zfsonlinux/zfs/issues/7358
Bug#916061: marked as done (diod FTBFS with glibc 2.28)
Your message dated Thu, 20 Dec 2018 01:50:28 + with message-id and subject line Bug#916061: fixed in diod 1.0.24-4 has caused the Debian Bug report #916061, regarding diod FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: diod Version: 1.0.24-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diod.html ... ops.c: In function 'diod_mknod': ops.c:808:38: warning: implicit declaration of function 'makedev' [-Wimplicit-function-declaration] if (mknod (path_s (npath), mode, makedev (major, minor)) < 0 ^~~ gcc -Wall -g -O2 -ffile-prefix-map=/build/1st/diod-1.0.24=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o diod diod.o ops.o exp.o ioctx.o fid.o xattr.o ../libdiod/libdiod.a ../libnpclient/libnpclient.a ../libnpfs/libnpfs.a ../liblsd/liblsd.a -lwrap -lpthread -llua5.1 -lm -ldl -lmunge -lcap /usr/bin/ld: ops.o: in function `diod_mknod': ./diod/ops.c:808: undefined reference to `makedev' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:460: diod] Error 1 --- End Message --- --- Begin Message --- Source: diod Source-Version: 1.0.24-4 We believe that the bug you reported is fixed in the latest version of diod, 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. Євгеній Мещеряков (supplier of updated diod package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 20 Dec 2018 02:04:48 +0100 Source: diod Binary: diod Architecture: source Version: 1.0.24-4 Distribution: unstable Urgency: medium Maintainer: Євгеній Мещеряков Changed-By: Євгеній Мещеряков Description: diod - I/O forwarding server for 9P Closes: 916061 Changes: diod (1.0.24-4) unstable; urgency=medium . * New patches: - include-sysmacros_h.diff - fix FTBFS because of undefined reference to makedev (closes: #916061) * Depend on lsb-base, this fixes a lintian warning * Standards-Version 4.2.1 - no changes needed * Move packaging to salsa.debian.org and update Vcs fields accordingly Checksums-Sha1: 7cf3ca768a914227a74f83a7050a9d554187d0cf 2004 diod_1.0.24-4.dsc 88c07d161104b15c391eb84e72e1a1cb4ced3569 6488 diod_1.0.24-4.debian.tar.xz 46b36966b6a22edd5e9906aa37aa8d0de0754234 6362 diod_1.0.24-4_source.buildinfo Checksums-Sha256: 865f70a3d8b2e92da51ecc16478f0d9f67e1b24b87ac8dc946609adbf8323021 2004 diod_1.0.24-4.dsc 39d314958d45722ba01628218e3e617b286a691ee395d2acb489c470040d891c 6488 diod_1.0.24-4.debian.tar.xz 7ed970ec247ec900ce9af1885ec11f3e2071f7f9236412139c5865f4f9fbe48d 6362 diod_1.0.24-4_source.buildinfo Files: 5a2684cd00bb7c68bff04ca310f23c5a 2004 admin optional diod_1.0.24-4.dsc 26a618be5d7aa19d99ab7846471be515 6488 admin optional diod_1.0.24-4.debian.tar.xz 5a218e37ed8c174b9216b1dadd678a28 6362 admin optional diod_1.0.24-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErJ1oMWkY5MAmVndnwW2o5/RRuTwFAlwa77AACgkQwW2o5/RR uTzP6RAAldQHjRpIIL++8yZJJSJOj3miR/O/ZexgqYN0MjkH74otC8wti9o8CQrS i2YREqNUPhzHt8Xw2VN0fKzAzE7qHLqUFRKu80nE5H81wIkjIQX7DC8TrrayDFwJ ZNQxDSic3wuGw4upsLncsi6Szrorhpr3NzpGxHblP6OArSf3F2dDREnhMw1q8Roy q1FM1YmoE9oU27y3q/oAZ6oKRjSK/dO8UCIHj03/z2WC4bnhdBU4+gYIh/+0ech7 AgrJjMep+3uojDoa1eUXeMphtq+wCpZQkzhAkcEgrATyanVQsu88vdlpc/T2vgca luT8Ltz7WVl3iSoTmB0pE2k4ZMcPleE+GF7wwSOn1TdKNeCYyWWxUblhiCeJy4Af +vHqII3+0ITY3y+HXkNry5+XpEI7D+pK7M5q3JgtJ+EH1/WtZavm5l/Svi1/N1iX DeluSgIALvDFiJxLUGlXsikzXUJcWCiucB/1cnwe6X1N7T128Q9N7DXh3pGwnyKs 5fFA1A+HuH56FDxVd5ejTDg6tz3cNqYB1jfv91QzU44YR2tZXmN7tS3yeQdQFI6K zUD86YceJjml+bKNtIGOFV6PTEAsbaiQhzIK5Qz1M+89EXS4Yom3ibJfxn8GiLNB YHL3CB/8Sbi19cNKZ9fOIY+YjbosGzP1nFs4wzQKne01Ilv+CF8= =CFxU -END PGP SIGNATURE End Message ---
Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386
On Wed, Dec 19, 2018 at 12:09 PM Balint Reczey wrote: > > Package: imagemagick > Version: 8:6.9.10.14+dfsg-1 > Severity: grave > Control: forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31 > Control: tags -1 upstream fixed-upstream > Control: affects -1 ruby-rmagick > > Hi, > > The ABI broke in 6.9.10-11 due to changing MagickDoubleType to double > from long double. > This breaks ruby-rmagick and possibly other reverse dependencies, thus > after fixing imagemagick please check if some reverse dependencies > need to be rebuilt. The fix will be available in the .18 upstream > release. Exact, this will need a so bump I suppose... Bastien > > Cheers, > Balint > > -- > Balint Reczey > Ubuntu & Debian Developer >
Processed: Re: Bug#789008: At least on Debian testing it upgraded without an issue.
Processing control commands: > tags -1 +moreinfo Bug #789008 [insserv] dbus: Unable to configure package (dpkg) Bug #746170 [insserv] insserv: Still fails due to rpcbind/nfs Ignoring request to alter tags of bug #789008 to the same tags previously set Ignoring request to alter tags of bug #746170 to the same tags previously set -- 746170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746170 789008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#789008: At least on Debian testing it upgraded without an issue.
control: tags -1 +moreinfo [2018-12-18 12:10] shirish शिरीष > > Dear all, > > At least here it updated without any issues - > > $ sudo aptitude install insserv -y > The following packages will be upgraded: > insserv > [...] Thank you for help with bug triage, shirish. Dear submitter, can you reproduce issue? Note, that insserv=1.16 is no longer relevant, since now insserv=1.18 in sid and insserv=1.14 in stable.
Processed: Re: Bug#789008: At least on Debian testing it upgraded without an issue.
Processing control commands: > tags -1 +moreinfo Bug #789008 [insserv] dbus: Unable to configure package (dpkg) Bug #746170 [insserv] insserv: Still fails due to rpcbind/nfs Added tag(s) moreinfo. Added tag(s) moreinfo. -- 746170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746170 789008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to diod, tagging 916061
Processing commands for cont...@bugs.debian.org: > limit source diod Limiting to bugs with field 'source' containing at least one of 'diod' Limit currently set to 'source':'diod' > tags 916061 + pending Bug #916061 [src:diod] diod FTBFS with glibc 2.28 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 916061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915886: Probable work-around
The issue is that Debian delivers Linux headers in two directories, each of which is linked under /lib/modules. On my system, with 4.14, these symlinks are under /lib/modules/4.14.0-3-amd64: cd /lib/modules/4.14.0-3-amd64 ls -ld build source lrwxrwxrwx 1 root root 37 Jan 25 2018 build -> /usr/src/linux-headers-4.14.0-3-amd64 lrwxrwxrwx 1 root root 38 Jan 25 2018 source -> /usr/src/linux-headers-4.14.0-3-common The zfs-dkms 'configure' script assumes the Linux include files are accessible via the 'build' symlink but that only provides access to amd64 CPU dependent files. All the rest of the linux header files are accessible via 'source' which points to the 'common' header files. That breaks the zfs-dkms build when 'dkms' runs the 'configure' command. The work-around creates a symlink to /usr/src/linux-headers-4.14.0-3-common/include/linux under linux-headers-4.14.0--amd64 so the configure script can find the files it needs: cd /usr/src/linux-headers-4.14.0-3-amd64 ln -s /usr/src/linux-headers-4.14.0-3-common/include/linux . Now 'build/include/linux' points to the linux headers: ls -l /lib/modules/4.14.0-3-amd64/build/include/ total 76 drwxr-xr-x 698 root root 69632 Dec 19 09:54 config drwxr-xr-x 3 root root 4096 Dec 19 09:54 generated lrwxrwxrwx 1 root root 52 Dec 19 11:22 linux -> /usr/src/linux-headers-4.14.0-3-common/include/linux Substitute your kernel version du jour for 4.14.0-3. I've only tested this with 4.14 so YMMV with other kernel versions.
Bug#913050: marked as done (batik: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal)
Your message dated Wed, 19 Dec 2018 23:49:09 + with message-id and subject line Bug#913050: fixed in batik 1.10-2 has caused the Debian Bug report #913050, regarding batik: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal 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.) -- 913050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: batik Version: 1.10-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/batik.html ... [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/1st/batik-1.10/batik-swing/src/main/java/org/apache/batik/swing/gvt/JGVTComponent.java:[1275,35] error: cannot find symbol symbol: method checkSystemClipboardAccess() location: variable securityManager of type SecurityManager [INFO] 1 error --- End Message --- --- Begin Message --- Source: batik Source-Version: 1.10-2 We believe that the bug you reported is fixed in the latest version of batik, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated batik 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, 20 Dec 2018 00:28:22 +0100 Source: batik Binary: libbatik-java Architecture: source Version: 1.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libbatik-java - xml.apache.org SVG Library Closes: 902532 913050 Changes: batik (1.10-2) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 11 (Closes: #913050) * Tightened the version of maven-debian-helper required to build batik (Closes: #902532) * Standards-Version updated to 4.2.1 * Use salsa.debian.org Vcs-* URLs Checksums-Sha1: 597e7dde08dae3dec6faa907f4b8a435d3c36a8a 2174 batik_1.10-2.dsc c045314ea9f46c5ad613bdfe0d3116b95905902e 31920 batik_1.10-2.debian.tar.xz 5ce4d2e6124932b9ea70fd371d289fe5cf131dfb 17084 batik_1.10-2_source.buildinfo Checksums-Sha256: 92ad7d2c6f56ed90b6137ce529e3c17a769b1a7c15575f758a150ec580f4ef3f 2174 batik_1.10-2.dsc dd06ef4a99b430c34be79e92489635c1749b1a42ed866b7b9c3389b49045b31f 31920 batik_1.10-2.debian.tar.xz 0de386c53344f41333b19684585017140f4cee50bcd3be6249676ac5135647db 17084 batik_1.10-2_source.buildinfo Files: 3fe1bc76b810b7c5bfc099e979d6a213 2174 java optional batik_1.10-2.dsc 0d45cd3d9e1625b5b182239de1f542b1 31920 java optional batik_1.10-2.debian.tar.xz 25fe861d1547d4cfe6dfc1d588813c17 17084 java optional batik_1.10-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwa1NUSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs1g0P/1bHmNQOi+zkQK0NnwRM9PrVqnKU0Ntn +wl4ify2TGvluN+HHLv811r6BtI8uXQu7hkAVdFE+8rY5xMsHT4mGhYBqqMOtpNb SkBEuUWXsem9fVIN/KWL/ZWksywXJw9m1UPCJBA9mFT4y6Czn+XGrxxQ9Es3qKWZ V0eMM3P+37M2VEK/CwG2yNwuZnQB85ng7fsP5OjvS34vl3Ul1JLkImhN+2pXbmT9 g/GAdv74UrHftG4v+AK4iu8FNg3k0uvG7kpT0BDLUx1nBOm5GfqC0zdQBU1sXxHk 858KYluPCShtJCsPiN6+Lt8yiTxeuH1JZ1sYxXUBxfu7FS9EwTJsrl0hoaV+O0yw iq8Vp8JvHZdSjDM2LQMQ0fyig7H9Za4higKvdiGPYEEGi86STvNqQ1esAS9NhfpA 1D2YBbxulRS/hXVEhLWcvl+cFH3M6A4bf/PkYeobP0UQodIOgAyLUENMQ6170CJQ QjG41PgyxUMvGV0Df0viflqgosc3Y66TuVL4F/SCkbw2JRx7cIjOwRe2TRSX1hPZ laYYwWsIh3otl49fNJ0GTHRgQMdpZm45UC2eDrdegRgp2m5KR6CQJeC5MZx1rVoY xr581uSGHXp/RkXLkokhhXIeqFvjhDlKzP4geSGWVjuZO4JMD6W5BQgYlw7Fv7WB S5YQP3NbvCA5 =UQwx -END PGP SIGNATURE End Message ---
Bug#836934: Does it make sense to keep frobtads?
Hi, frobtads wasn't part of Stretch and has two RC bugs open with no action in over a year. Can it be removed or is somehow important? Sebastian
Bug#915804: Should this package be removed?
On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote: > Source: cfengine2 > Severity: serious > > This is replaced by src:cfengine2 and stretch has both cfengine2 and > cfengine3, > so users can migrate within a stable release to 3. > > The current version is also RC-buggy for a long time and blocks the removal > of OpenSSL 1.0. cfengine2 is like a decade old. I found nothing in their blog. Only the convert tool: https://cfengine.com/company/blog-detail/cfengine-2-conversion-tool/ popcon wise there are more 2 installation than 3. Is there a reason to still keep it around rather than RM it and let the users switch to 3? > Cheers, > Moritz > Sebastian
Bug#915994: marked as done (spooles FTBFS with multiarchified openmpi >= 3.1.3-3)
Your message dated Wed, 19 Dec 2018 23:34:51 + with message-id and subject line Bug#915994: fixed in spooles 2.2-14 has caused the Debian Bug report #915994, regarding spooles FTBFS with multiarchified openmpi >= 3.1.3-3 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.) -- 915994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spooles Version: 2.2-13 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/spooles.html ... In file included from aggListMPI.c:3: ../spoolesMPI.h:6:10: fatal error: mpi.h: No such file or directory #include ^~~ compilation terminated. make[5]: *** [makeG:38: aggListMPI.o] Error 1 --- End Message --- --- Begin Message --- Source: spooles Source-Version: 2.2-14 We believe that the bug you reported is fixed in the latest version of spooles, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated spooles package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 19 Dec 2018 23:56:58 +0100 Source: spooles Binary: libspooles-dev libspooles2.2 spooles-doc Architecture: source Version: 2.2-14 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Description: libspooles-dev - SPOOLES SParse Object Oriented Linear Equations Solver developmen libspooles2.2 - SPOOLES SParse Object Oriented Linear Equations Solver shared lib spooles-doc - SPOOLES numerical simulation pre- and post-processor documentatio Closes: 915994 Changes: spooles (2.2-14) unstable; urgency=medium . * Team upload. * update MPI paths in makefiles.patch for multiarch. Closes: #915994. * Standards-Version: 4.2.1 Checksums-Sha1: 4564448cf10f9f3708592109504e261bcd590bab 2163 spooles_2.2-14.dsc 1abc52109839869bedcef324729f80a58261ffe8 58784 spooles_2.2-14.debian.tar.xz Checksums-Sha256: 665ffba0714c1dcba1f6c19fdd2ee5cedf63df2961e58f5864d789664a193fda 2163 spooles_2.2-14.dsc de4dbe2ef28320d1b58a1e5ca2b0bccd413039e8b769f7ba97658d0bf34900b4 58784 spooles_2.2-14.debian.tar.xz Files: 19d74476ba41a6c3b3fb9e52b64c2ada 2163 math optional spooles_2.2-14.dsc 0870ba14b8345c1ed91a79c04f7f6ffc 58784 math optional spooles_2.2-14.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlwaz+cACgkQVz7x5L1a AfoZGhAAjS7tac+02pIEeoNZG/wiwLgKbF16e+CMC2gaIf1D6AIgmbcsss/PcdkF zL60g66qSAQ/rajGrZ42oALQb8wL4RNHRDT9i/Ocqe/WCpJCwKG8V6vyRCBgLYRU MkEVtdXutz9jUPZWvye0M3ZhpuNiVbCy1om9mLIyf+dtCXZGaygn2oKF2wyBwm1d WIbgkQi7MvJiZgUXQOHe6PDFh5DC1mDxg5M3f+oy6f7HQeNNX/i0tU2pZHQgilKt RwqS+HHbt0PWldelDrzEa80qfu0c4LcytRJX99JTFXE6kkrFchdEoDhHRu/ZVx8J SgVHG6/UP/Mn0CupPgdIJv/0tGfNRkJvqgG9bdC0qwbYsxuRGBBIVjmWP3CDMnpa WYYaCRwuFigxr6qa3euLsqaw5s1yD2XraA8kGPDYiEZUxqG9LCVex2uRbhVf+g3d 8e4bhCq/ISfwQ4GSfL1avwH7WWDSi26TfmyEDbb9Jc9qn77pWZtqgUgsfKiqwhc7 YGBhhOe/AqiQCz0uD3hNHUvZrOXjPmbPflNNT5yyRnXhW4oTRhI5qWbzy3JEN7cP D4qasJoeNyaL743WCvpor0Ohe0H3IRouZMb5FJG7QU69yhtPuJaXO1+1SfUu1qg+ CSUAPhKQDUrziQWZjTTaEWpWdMAtErX5hIfrtSzfB4hYaxNmPbA= =CdvD -END PGP SIGNATURE End Message ---
Processed: Bug #913050 in batik marked as pending
Processing control commands: > tag -1 pending Bug #913050 [src:batik] batik: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal Added tag(s) pending. -- 913050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913050: Bug #913050 in batik marked as pending
Control: tag -1 pending Hello, Bug #913050 in batik 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/batik/commit/117eff76db3ff30a4b3423e0175b2927167da552 Fixed the build failure with Java 11 (Closes: #913050) (this message was generated automatically) -- Greetings https://bugs.debian.org/913050
Bug#907624: What ffindex do we want to package
Hi Andreas, the reverse dependency HH-suite failed to compile with the ffindex version Debian shipped. I have no feelings about it. It should just work :) The HH-suite is about structure prediction from sequence homology, which I found we should continue to offer in our distribution https://en.wikipedia.org/wiki/HH-suite https://tracker.debian.org/pkg/hhsuite . Are there other reverse dependencies for ffindex in our distribution? Priority is the HH-suite. Then ffindex. If difficulties surface anywhere then we have initiate some head scratching / banging. If there is nothing happening somewhere that I don't know about then I would leave it as it is. Cheers, Steffen On 19.12.18 09:53, Andreas Tille wrote: Hi, after reading https://github.com/soedinglab/ffindex_soedinglab/issues/4 I came to the conclusion that we somehow picked the wrong fork of ffindex. For me it seems very probable that if we pick the old codebase bug #907624 which was introduced when choosing this will vanish if we revert to the previously packaged code base. I have a local commit which is doing this: diff --git a/debian/changelog b/debian/changelog index 6a26115..c409f4f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +ffindex (0.9.9.7+sog+git20160415.14274c9-1) UNRELEASED; urgency=medium + + * The previous location on Github was an improperly choosen fork +(see https://github.com/soedinglab/ffindex_soedinglab/issues/4) +Here the version is now named "0.9.9.7+sog" (Saved On Github) +to make it alphabethically later than the previous one. + + -- Andreas Tille Wed, 19 Dec 2018 09:16:09 +0100 + ffindex (0.9.9.7+soedinglab+git20180802.74550c8-1) unstable; urgency=medium * Fix watch file (version should actually be +git20171201.74550c8 but diff --git a/debian/watch b/debian/watch index 91b4f38..b47f123 100644 --- a/debian/watch +++ b/debian/watch @@ -1,4 +1,4 @@ version=4 -opts="mode=git,pretty=0.9.9.7+soedinglab+git%cd.%h" \ -https://github.com/soedinglab/ffindex_soedinglab.git HEAD +opts="mode=git,pretty=0.9.9.7+sog+git%cd.%h" \ +https://github.com/ahcm/ffindex.git HEAD Upstream at github.com/ahcm/ffindex was extremely quick to tag a release and so it is at least active. Steffen, was your pick intentional or did you just stumbled by chance over the other fork? Are you OK with reverting to the old code? Kind regards Andreas. PS: I reported the segfault issue to the according fork anyway https://github.com/soedinglab/ffindex_soedinglab/issues/7
Bug#916565: closed by Alastair McKinstry (Bug#916565: fixed in dh-fortran-mod 0.6)
Control: clone -1 -2
Control: reopen -2
Control: reassign -2 libopenmpi3,openmpi-common,openmpi-doc
Control: found -2 3.1.3-5
Control: retitle -2 libopenmpi3,openmpi-{common,doc}: needs to be rebuilt with
dh-fortran-mod 0.6
Since this bugs affects arch:all packages, binNMUs are not sufficient,
but a sourceful upload is needed (which of course should be source-only)
(Maybe bump the version of the dh-fortran-mod B-D to be sure to get the
right one)
But this rises the question: Why does dh-fortran-mod insert its code
snippets into the arch:all openmpi-doc and openmpi-common packages, that
don't seem to contain fortran bits?
And libopenmpi3 does neither ...
Andreas
Processed: Re: Bug#916565 closed by Alastair McKinstry (Bug#916565: fixed in dh-fortran-mod 0.6)
Processing control commands:
> clone -1 -2
Bug #916565 {Done: Alastair McKinstry } [dh-fortran-mod]
libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script
subprocess returned error exit status 1
Bug 916565 cloned as bug 916890
> reopen -2
Bug #916890 {Done: Alastair McKinstry } [dh-fortran-mod]
libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script
subprocess returned error exit status 1
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dh-fortran-mod/0.6.
> reassign -2 libopenmpi3,openmpi-common,openmpi-doc
Bug #916890 [dh-fortran-mod] libopenmpi3,openmpi-{common,doc}: fails to remove:
post-removal script subprocess returned error exit status 1
Bug reassigned from package 'dh-fortran-mod' to
'libopenmpi3,openmpi-common,openmpi-doc'.
Ignoring request to alter found versions of bug #916890 to the same values
previously set
Ignoring request to alter fixed versions of bug #916890 to the same values
previously set
> found -2 3.1.3-5
Bug #916890 [libopenmpi3,openmpi-common,openmpi-doc]
libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script
subprocess returned error exit status 1
Marked as found in versions openmpi/3.1.3-5.
> retitle -2 libopenmpi3,openmpi-{common,doc}: needs to be rebuilt with
> dh-fortran-mod 0.6
Bug #916890 [libopenmpi3,openmpi-common,openmpi-doc]
libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script
subprocess returned error exit status 1
Changed Bug title to 'libopenmpi3,openmpi-{common,doc}: needs to be rebuilt
with dh-fortran-mod 0.6' from 'libopenmpi3,openmpi-{common,doc}: fails to
remove: post-removal script subprocess returned error exit status 1'.
--
916565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916565
916890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 840748
Processing commands for cont...@bugs.debian.org: > tags 840748 + stretch Bug #840748 [edb] edb: install script failed for emacs25 because of :indent keyword Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 840748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916885: pass-tomb: depends on kcov which is not in testing
Package: pass-tomb Version: 1.1-2 Severity: serious pass-tomb build-depends on kcov which is not in testing. britney migrated the package to testing regardless. However the package is not fit for a release because it can not be built in testing as of now [0]. This bug can be closed either once kcov migrates to testing or if pass-tomb drops the build-dependency on kcov. [0] https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/pass-tomb.html Sebastian
Bug#912231: marked as done (bnd: FTBFS with Java 11 due to conflict with OutputStream.nullOutputStream())
Your message dated Wed, 19 Dec 2018 22:04:07 +
with message-id
and subject line Bug#912231: fixed in bnd 3.5.0-4
has caused the Debian Bug report #912231,
regarding bnd: FTBFS with Java 11 due to conflict with
OutputStream.nullOutputStream()
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.)
--
912231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bnd
Version: 3.5.0-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bnd.html
...
Compiling with JDK Java compiler API.
Generated bundles:
[/build/1st/bnd-3.5.0/biz.aQute.tester/generated/biz.aQute.tester.jar]
:biz.aQute.tester:jar (Thread[Task worker for ':' Thread 9,5,main]) completed.
Took 0.132 secs.
/build/1st/bnd-3.5.0/biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java:41:
error: nullOutputStream() in RedirectOutput cannot override nullOutputStream()
in OutputStream
private static PrintStream nullOutputStream() {
^
attempting to assign weaker access privileges; was public
1 error
:biz.aQute.remote:compileJava FAILED
:biz.aQute.remote:compileJava (Thread[Task worker for ':' Thread 3,5,main])
completed. Took 0.596 secs.
:biz.aQute.repository:compileJava (Thread[Task worker for ':' Thread
11,5,main]) completed. Took 1.962 secs.
FAILURE: Build failed with an exception.
--- End Message ---
--- Begin Message ---
Source: bnd
Source-Version: 3.5.0-4
We believe that the bug you reported is fixed in the latest version of
bnd, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated bnd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 19 Dec 2018 22:48:21 +0100
Source: bnd
Binary: bnd
Architecture: source
Version: 3.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Description:
bnd- tool to create and diagnose OSGi bundles
Closes: 912231
Changes:
bnd (3.5.0-4) unstable; urgency=medium
.
* Fixed the build failure with Java 11 (Closes: #912231)
* Fixed the build failure caused by gradle-debian-helper 2.0.1
* Ignore the dependency on xml-apis
* Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
c262e5ebfa26752138082b26d5274ea178a7fb60 2377 bnd_3.5.0-4.dsc
4d3d237122915d38a7e1f0eb62f7f647e47e254b 15772 bnd_3.5.0-4.debian.tar.xz
8df73ec6d69b7f4ead69014d88ca1b791530fb5d 16698 bnd_3.5.0-4_source.buildinfo
Checksums-Sha256:
83087762c9969baf0356bfe19c840bd2c6f123b011c353fe9b185d64dcdbe983 2377
bnd_3.5.0-4.dsc
92ed5cfc8b5fee7c99456f0417aeceb6426b33f7106a0c659f216ee9b8ff7f15 15772
bnd_3.5.0-4.debian.tar.xz
c6c6efb80bc5c420e85ad6eea3aeef015e028a9d41f3a5ebda3ed6a021a6e01a 16698
bnd_3.5.0-4_source.buildinfo
Files:
bbe3955daf155e1ac8722a47547a446c 2377 java optional bnd_3.5.0-4.dsc
a1c48fcd848c01745abd4280a34b89e6 15772 java optional bnd_3.5.0-4.debian.tar.xz
2fc95327b49d59e9bd04bf93d466cb52 16698 java optional
bnd_3.5.0-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwavMUSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCssS8P/RlD+GXy12zuhxRkWWRhdEMk7xs2BkbE
Z0wFrqgksCRMNGDuesMCpjSoJhH6LbG8Smas2BHCveJJwmJu9g2QP6GwW+/cjiB/
CSXxyADzJGQX6tu3b/qm5M7cagrttG+pQg2HiJg0MFxtU2goxYxUSQz/DG6QTYQE
2OysDho4+6B2D9sodomi6MompY8woHb09O86rYG7NJKZucXIaKYp4LPCupjChdlZ
d098EQRpIB0fVgwLvSo1PmEHgKi+7vg1DQZFxGi7hUa+i/WEXQXDGcfOHhswgeMa
izZ8OMyWy4tbx9fa9yB0oJYBb9z6geuF/4MBLKGKb9KA38/sH1w2if1bJInGLAAg
YVNeETDLxe7/5XunKzZyjAgc4PYySmV9IxX4PoyuPxiUaP3jPQpH5vFnzNxlLX2z
z5aM8e0tFLbBD0eeMY2O5pvfhRMAtGiFRlUMJEYkSXZMZqvvG5Z1aagizYGfs2ry
XJGW4tPTZTJbxDL/BzdfSC15VVtRSPd8fP7zUkOG+pqW2BpglewgEf8IC8teh3tQ
wkf/5DyqkkDSO8ZSgbwW1X6J90kesvvEZfHbC67ithje0TwFFWy4C2Crbdf+VI3e
PuN3Qr16GxsafKXBzSNu7vQbdaaVBuD0aK9nY3Tm4LxhLdJCWMcQXTbxwS90Fv6Z
MXjNn4+/2LBg
=yBWS
-END PGP SIGNATURE End Message ---
Bug#916606: lbreakout2: randomly pauses ingame without external actions
Hi, after compiling the game myself I've done some tests. The pause occurs in game.c line 1171. If got there by the SDL_ACTIVEEVENT with state 2 (SDL_APPINPUTFOCUS) and gain 0. See: https://www.libsdl.org/release/SDL-1.2.15/docs/html/sdlactiveevent.html Kind regards, bitfreak25
Bug#912231: Bug #912231 in bnd marked as pending
Control: tag -1 pending Hello, Bug #912231 in bnd 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/bnd/commit/50d45ef12b357a36aa7906e221f79301eba334f8 Fixed the build failure with Java 11 (Closes: #912231) (this message was generated automatically) -- Greetings https://bugs.debian.org/912231
Bug#913397: marked as done (ucommon FTBFS: new symbols)
Your message dated Wed, 19 Dec 2018 21:49:36 + with message-id and subject line Bug#913397: fixed in ucommon 7.0.0-15 has caused the Debian Bug report #913397, regarding ucommon FTBFS: new symbols 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.) -- 913397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ucommon Version: 7.0.0-14 Severity: serious Tags: ftbfs Some recent change in unstable makes ucommon FTBFS: https://tests.reproducible-builds.org/debian/history/ucommon.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ucommon.html ... debian/rules override_dh_strip make[1]: Entering directory '/build/1st/ucommon-7.0.0' dh_strip --dbgsym-migration='libucommon8-dbg (<< 7.0.0-7~)' make[1]: Leaving directory '/build/1st/ucommon-7.0.0' dh_makeshlibs dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libucommon8/DEBIAN/symbols doesn't match completely debian/libucommon8.symbols --- debian/libucommon8.symbols (libucommon8_7.0.0-14_amd64) +++ dpkg-gensymbolsLvPJvE 2019-12-13 07:43:27.773789987 -1200 @@ -14,6 +14,8 @@ (c++)"VTT for ost::TTYStream@Base" 7.0.0 (c++)"VTT for ost::ThreadQueue@Base" 7.0.0 (c++)"VTT for ost::ttystream@Base" 7.0.0 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3ost4Slog5LevelEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSJ_PSt13_Rb_tree_nodeISB_E@Base 7.0.0-14 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3ost4Slog5LevelEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 7.0.0-14 (c++)"non-virtual thunk to ost::AppLog::~AppLog()@Base" 7.0.0 (c++)"non-virtual thunk to ost::SerialService::~SerialService()@Base" 7.0.0 (c++)"non-virtual thunk to ost::SharedMemPager::~SharedMemPager()@Base" 7.0.0 @@ -717,7 +719,7 @@ (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator, std::allocator > const, ost::Slog::Level> >, std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_get_insert_unique_pos(std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::find(std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 - (c++|optional)"std::_Rb_tree_iterator > std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_emplace_hint_unique, std::tuple<> >(std::_Rb_tree_const_iterator >, std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base" 7.0.0 +#MISSING: 7.0.0-14# (c++|optional)"std::_Rb_tree_iterator > std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_emplace_hint_unique, std::tuple<> >(std::_Rb_tree_const_iterator >, std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base" 7.0.0 (c++|optional)"std::_Rb_tree_iterator, std::allocator > const, ost::Slog::Level> > std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_emplace_hint_unique, std::allocator > const&>, std::tuple<> >(std::_Rb_tree_const_iterator, std::allocator > const, ost::Slog::Level> >, std::piecewise_construct_t const&, std::tuple, std::allocator > const&>&&, std::tuple<>&&)@Base" 7.0.0 (c++|optional=templinst)"std::__cxx11::basic_stringbuf, std::allocator >::~basic_stringbuf()@Base" 7.0.0 (c++|optional=templinst)"std::ctype::do_widen(char) const@Base" 7.0.0 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:11:
Bug#909865: marked as done (openexr FTBFS on i386 with gcc 8)
Your message dated Wed, 19 Dec 2018 21:49:29 +
with message-id
and subject line Bug#909865: fixed in openexr 2.3.0-3
has caused the Debian Bug report #909865,
regarding openexr FTBFS on i386 with gcc 8
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.)
--
909865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openexr
Version: 2.2.1-4
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/openexr.html
...
compression 6, x sampling 2, y sampling 2: writing reading comparing
compression 7, x sampling 2, y sampling 2: writing reading comparing
compression 8, x sampling 2, y sampling 2: writing reading comparing
compression 9, x sampling 2, y sampling 2: writing reading comparing
random bits
compression 0, x sampling 1, y sampling 1: writing reading comparingIlmImfTest:
testCompression.cpp:330: void {anonymous}::writeRead(const
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const
Imf_2_2::Array2D&, const char*, int, int, int, int,
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x],
comp)' failed.
FAIL IlmImfTest (exit status: 134)
Testsuite summary for OpenEXR 2.2.1
# TOTAL: 1
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
See IlmImfTest/test-suite.log
make[5]: *** [Makefile:966: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: openexr
Source-Version: 2.3.0-3
We believe that the bug you reported is fixed in the latest version of
openexr, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Malaterre (supplier of updated openexr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 19 Dec 2018 21:41:08 +0100
Source: openexr
Binary: openexr openexr-doc libopenexr-dev libopenexr23
Architecture: source
Version: 2.3.0-3
Distribution: experimental
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
Changed-By: Mathieu Malaterre
Description:
libopenexr-dev - development files for the OpenEXR image library
libopenexr23 - runtime files for the OpenEXR image library
openexr- command-line tools for the OpenEXR image format
openexr-doc - documentation and examples for the OpenEXR image format
Closes: 909865
Changes:
openexr (2.3.0-3) experimental; urgency=medium
.
* Make sure to use float-store when compiling tests. Closes: #909865
Checksums-Sha1:
ea1cd2dbae5a4138a7a30a6cd5d5ab75431fe68c 2543 openexr_2.3.0-3.dsc
c3300752e21e7874645251289f7261d0193cf015 19772 openexr_2.3.0-3.debian.tar.xz
0f486421095911993d17a7a78a7b323ad9cda052 5098 openexr_2.3.0-3_source.buildinfo
Checksums-Sha256:
cb6df383cc848d1ed1796e9ec5583055df6ea7ac2fdbd521b74aac81045f0953 2543
openexr_2.3.0-3.dsc
f0831b4dacdd85fd5100d13a9856effb0ce9a11cb610c44c7eacf47eeb2f2b7e 19772
openexr_2.3.0-3.debian.tar.xz
a56626399564f76c4bac039efdf9983d44f3f0b627381af084ea048eacb33a74 5098
openexr_2.3.0-3_source.buildinfo
Files:
14134984c4cc4358b0e33a28bb66e59a 2543 graphics optional openexr_2.3.0-3.dsc
344ca369d8a1e5493672b46552361b71 19772 graphics optional
openexr_2.3.0-3.debian.tar.xz
bc2da73beed021b4886c9871a1ddcdc1 5098 graphics optional
openexr_2.3.0-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAlwauksRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0V9Cg//egS7RnDLRwbtyWWb5xWwaMyNQApFcgci
M4j8ad+pf7LOtqMUgxHV4L6NNqgQdNgyKAWcvwRVcsS9qg/HFBlmOoegWRU1m9IS
VbkkfRyXBGJlr1RxaAq22C7nShiEIh4ph80iHL+6xvAATRxIsXx7F7zHw7IVMQA6
4FpPswmJESBSLKTx2LeVdSIAOBwY4bW4F8Tr784Mb+HI2klEAAo/PDIxIUmyVoXM
JQqcBSrpgCuROehCgUxglX40zXDffU18gLFrD3P5Pnat3TeOPeFjWgRYabg9ITr+
avFfbI4twxofgw3iWNXFPGCwsdnJoSbIO+BdebmfqQw66QTk1Arrc3Vw6MrtemYU
Processed: Bug #912231 in bnd marked as pending
Processing control commands: > tag -1 pending Bug #912231 [src:bnd] bnd: FTBFS with Java 11 due to conflict with OutputStream.nullOutputStream() Added tag(s) pending. -- 912231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912231: bnd FTBFS with OpenJDK 11
Le 29/10/2018 à 23:32, Markus Koschany a écrit : > The OpenJDK 11 issue is rather simple to fix, however the build fails > later on with this error message, a Gradle issue? I've figured out what is causing the second issue, the poms are installed into .gradle/daemon/4.4.1/debian/.m2/ instead of debian/.m2/. Due to the way gradle-debian-helper 2.0.1 injects its code in the Gradle classpath the Gradle daemon is always started, and the daemon uses a different working directory (.gradle/daemon/4.4.1/). Since the location of the Maven repository where the artifacts are installed is specified as a relative path, it's shifted under the daemon working directory and maven-repo-helper no longer finds the artifacts at the expected path. This can be fixed by setting the repository location with an absolute path (the HOME variable in debian/rules). Emmanuel Bourg
Bug#916800: marked as done (phybin: FTBFS with newer GHC)
Your message dated Wed, 19 Dec 2018 21:19:25 + with message-id and subject line Bug#916800: fixed in phybin 0.3-3 has caused the Debian Bug report #916800, regarding phybin: FTBFS with newer GHC 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.) -- 916800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phybin Version: 0.3-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear maintainer, phybin FTBFS with newer versions of GHC (>= 8.4) with the following error: [1 of 9] Compiling Bio.Phylogeny.PhyBin.CoreTypes ( Bio/Phylogeny/PhyBin/CoreTypes.hs, dist-ghc/build/test-phybin/test-phybin-tmp/Bio/Phylogeny/PhyBin/CoreTypes.o ) Bio/Phylogeny/PhyBin/CoreTypes.hs:112:35: error: Ambiguous occurrence `<>' It could refer to either `Prelude.<>', imported from `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37 (and originally defined in `GHC.Base') or `Text.PrettyPrint.HughesPJClass.<>', imported from `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58 (and originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ') | 112 | displayDefaultTree orig = loop tr <> ";" | ^^ Bio/Phylogeny/PhyBin/CoreTypes.hs:120:27: error: Ambiguous occurrence `<>' It could refer to either `Prelude.<>', imported from `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37 (and originally defined in `GHC.Base') or `Text.PrettyPrint.HughesPJClass.<>', imported from `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58 (and originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ') | 120 | Just val -> base <> text ":[" <> text (show val) <> text "]" | ^^ Bio/Phylogeny/PhyBin/CoreTypes.hs:120:40: error: Ambiguous occurrence `<>' It could refer to either `Prelude.<>', imported from `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37 (and originally defined in `GHC.Base') or `Text.PrettyPrint.HughesPJClass.<>', imported from `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58 (and originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ') | 120 | Just val -> base <> text ":[" <> text (show val) <> text "]" |^^ Bio/Phylogeny/PhyBin/CoreTypes.hs:120:59: error: Ambiguous occurrence `<>' It could refer to either `Prelude.<>', imported from `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37 (and originally defined in `GHC.Base') or `Text.PrettyPrint.HughesPJClass.<>', imported from `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58 (and originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ') | 120 | Just val -> base <> text ":[" <> text (show val) <> text "]" | ^^
Bug#916800: phybin: FTBFS with newer GHC
Hi Joachim, On Wed, Dec 19, 2018 at 06:11:40PM +0100, Joachim Breitner wrote: > > On Tue, Dec 18, 2018 at 10:57:15PM +0100, Joachim Breitner wrote: > > > Would not be hard to fix, but is there a chance that upstream could just > > > release a version that works with a current compiler? > > > > I'm afraid upstream is not very active but would be happy about a patch. > > I submitted a patch to upstream, feel fee to get it from github if you > need it earlier: > https://github.com/rrnewton/PhyBin/pull/13 > > https://patch-diff.githubusercontent.com/raw/rrnewton/PhyBin/pull/13.patch I've applied it (with slight change that was needed) as quilt patch. Thanks a lot. Kind regards Andreas. -- http://fam-tille.de
Bug#913843: [DRE-maint] Bug#913843: ruby-mail-gpg FTBFS with gpgme 1.12.0
Control: severity -1 important Will take care of this (non-critical) bug at the end of January; I'm currently on travel. Up until then, downgrading the severity to prevent autoremoval. Cheers, Georg signature.asc Description: Digital signature
Processed: Re: [DRE-maint] Bug#913843: ruby-mail-gpg FTBFS with gpgme 1.12.0
Processing control commands: > severity -1 important Bug #913843 [src:ruby-mail-gpg] ruby-mail-gpg FTBFS with gpgme 1.12.0 Severity set to 'important' from 'serious' -- 913843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916879: qtox: missing library libsodium.so.18
Package: qtox Version: 1.16.3-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, when trying to start qtox it fails with a missing shared library: qtox: error while loading shared libraries: libsodium.so.18: cannot open shared object file: No such file or directory -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qtox depends on: ii libavcodec587:4.0.3-1 ii libavdevice58 7:4.0.3-1 ii libavformat58 7:4.0.3-1 ii libavutil56 7:4.0.3-1 ii libc6 2.28-3 ii libcairo2 1.16.0-1 ii libexif12 0.6.21-5 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6 ii libglib2.0-02.58.1-2 ii libgtk2.0-0 2.24.32-3 ii libopenal1 1:1.19.1-1 ii libqrencode44.0.2-1 ii libqt5core5a5.11.2+dfsg-7 ii libqt5gui5 5.11.2+dfsg-7 ii libqt5network5 5.11.2+dfsg-7 ii libqt5svg5 5.11.2-2 ii libqt5widgets5 5.11.2+dfsg-7 ii libqt5xml5 5.11.2+dfsg-7 ii libsodium23 1.0.16-2 ii libsqlcipher0 3.4.1-1+b1 ii libstdc++6 8.2.0-13 ii libswscale5 7:4.0.3-1 ii libtoxcore2 0.2.8-1 ii libx11-62:1.6.7-1 ii libxss1 1:1.2.3-1 qtox recommends no packages. qtox suggests no packages. -- no debconf information
Bug#893409: pixelmed FTBFS with openjdk-9
Hi Olivier, On Wed, Dec 19, 2018 at 06:37:04PM +0100, Olivier Sallou wrote: > >> Adding this lib to deps should fix the pb > > - I have fixed the problem, updating patch (lib needed to be added to > other Makefile) Cool! Thanks a lot for your work. Its really appreciated. > - There were some other issues with an old jdk package moved to an other > location, from JDK 9 in 2016, which is not exported [0]. Surprisingly it > compiles anyway, but does it work as expected?? I have no idea at all. I do not even have an expectation what the program should do. I simply inherited the maintenance from Mathieu Malaterre who injected a lot of medical imaging stuff and decided to leave the team later. The package has quite a number of users (compared to other specialised software) - so I expect users to report issues if it does not work. > It seems there is a > new API (java.lang.ref.Cleaner) but I'm not sure it could be replaced as > easily (and without knowing side effects), it should be updated by upstream Upstream is dead. > In the meanwhile I renamed the related package in patch. > > - vecmath needed to be added as well in Makefile (done) > > - javadoc generation classpath needed to be updated as well (done) > > - I think that vecmath and jaxb-api jars will need to be added in > runtime classpath (debian/DicomXX etc..) as well (NOT done) > > - 4 tests are failing (surprisingly, packaging continues) > > - lintian: some errors, documentation is not in correct directory > (libpixelmed-java-doc expects files in > /usr/share/doc/libpixelmed-java-doc but doc is in > /usr/share/doc/libpixelmed-java) (NOT fixed) The latter is caused by the debhelper switch. I'll care for this. > I have pushed my updates to git (file not found , certainly a result not > generated, but no additional info) Thanks again. I'll have a look tomorrow and will ask back in case of further issues. Kind regards Andreas. > [0] https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8148117 -- http://fam-tille.de
Bug#916846: [libreoffice-ogltrans] Blank screen with OpenGL transitions
Hi, On Wed, Dec 19, 2018 at 10:04:34PM +0300, Alexander Kernozhitsky wrote: > > So it probably some system library at fault. Or some integration, though > > apparently it happens with both gtk3 and "gen"... In both cases that is > > still a upstream bug (, too). > > Please read the upstream bug report carefully. It's said there that the fault I read it. LO upstream is quite fast on blaming upstream bugs to distributions if it doesn't work on their shipped binaries - even if it was a bug in their code only exhibiting on newer systems with newer libs. > is in Debian version of LibreOffice, official LibreOffice debs work fine on > Debian. So, LibreOffice is at fault, not system libraries. LO ships all possible (including stuff available on every Linux) libraries internally while we aren't. Including stuff like cairo etc. And no, I am so not going to use gazillions of (old, (security buggy at times) internal libraries. So still, it can be an issue of us using some (newer) system library. Regards, Rene
Processed: bug 916846 is forwarded to https://bugs.documentfoundation.org/show_bug.cgi?id=115716
Processing commands for cont...@bugs.debian.org: > forwarded 916846 https://bugs.documentfoundation.org/show_bug.cgi?id=115716 Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with OpenGL transitions Set Bug forwarded-to-address to 'https://bugs.documentfoundation.org/show_bug.cgi?id=115716'. > thanks Stopping processing here. Please contact me if you need assistance. -- 916846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915831: [Pkg-zfsonlinux-devel] Bug#915831: zfs init file upgrade
[Chris Zubrzycki] > I would like to amend my reply. The files are no longer in the deb, > however they are still listed by dpkg -L zfsutils-linux. I do not > understand how the solution to an ordering issue is to remove needed > init files that have been fought to be included for literally years. See https://manpages.debian.org/unstable/dpkg/dpkg-maintscript-helper.1.en.html > for information on how to remove conffiles. If the files have incorrect init dependencies and are no longer in the deb, the only way to update them is to manually edit them or add them back into the deb. -- Happy hacking Petter Reinholdtsen
Bug#916855: marked as done (glewlwyd: FTBFS: no dependency information found for /build/ulfius-build/libulfius.so.2.3)
Your message dated Wed, 19 Dec 2018 19:04:16 + with message-id and subject line Bug#916855: fixed in glewlwyd 1.4.9-1 has caused the Debian Bug report #916855, regarding glewlwyd: FTBFS: no dependency information found for /build/ulfius-build/libulfius.so.2.3 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.) -- 916855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glewlwyd Version: 1.4.6-3 Severity: serious Tags: ftbfs Hi, On a rebuild against libulfius2.5, your package failed to build: dh_shlibdeps -a -O--buildsystem=cmake -O--builddirectory=build dpkg-shlibdeps: error: no dependency information found for /<>/build/ulfius-build/libulfius.so.2.3 (used by debian/glewlwyd/usr/bin/glewlwyd) Hint: check if the library actually comes from a package. dh_shlibdeps: dpkg-shlibdeps -Tdebian/glewlwyd.substvars debian/glewlwyd/usr/bin/glewlwyd returned exit code 25 dh_shlibdeps: Aborting due to earlier error >From the build log it looks like glewlwyd is building its own (old) version of libulfius, rather than dynamically linking to the one from the Debian package. Full logs: https://buildd.debian.org/status/package.php?p=glewlwyd Cheers, Emilio --- End Message --- --- Begin Message --- Source: glewlwyd Source-Version: 1.4.9-1 We believe that the bug you reported is fixed in the latest version of glewlwyd, 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. Nicolas Mora (supplier of updated glewlwyd 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, 15 Dec 2018 12:58:37 -0500 Source: glewlwyd Binary: glewlwyd glewlwyd-common fonts-glewlwyd Architecture: source all amd64 Version: 1.4.9-1 Distribution: unstable Urgency: medium Maintainer: Debian IoT Maintainers Changed-By: Nicolas Mora Description: fonts-glewlwyd - OAuth2 authentication server providing Json Web Tokens - font fil glewlwyd - OAuth2 authentication server providing Json Web Tokens glewlwyd-common - OAuth2 authentication server providing Json Web Tokens - common f Closes: 916855 Changes: glewlwyd (1.4.9-1) unstable; urgency=medium . * New upstream release (Closes: #916855) Checksums-Sha1: aba8bc2903a8ee485fcb99a9cee9242644b154a9 2364 glewlwyd_1.4.9-1.dsc 77215c75af95c3f8cc3b7d23eba0ba763873979b 3420208 glewlwyd_1.4.9.orig.tar.gz 04feeb270f792126d4afa8b2c3d8aa1a2172722b 665408 glewlwyd_1.4.9-1.debian.tar.xz 0ffb287e5dd062de83dd88d8830feec55ad50d55 402668 fonts-glewlwyd_1.4.9-1_all.deb 0825d11d86c99a6e6aa2f22a9d81c89faeea6ab9 1219560 glewlwyd-common_1.4.9-1_all.deb f78d53a5d70c8ba50f27e6d2cf712568addd31ed 240388 glewlwyd-dbgsym_1.4.9-1_amd64.deb 2a2c1d87867bd312e86aff0ac6e58ebeda33f620 8346 glewlwyd_1.4.9-1_amd64.buildinfo 7b0ae0ce0608c6b9a8d0d80eef60387f7a9a240d 121600 glewlwyd_1.4.9-1_amd64.deb Checksums-Sha256: 295a8e3cacb65d24fc41118b249bedad3512edbb502299fef0f141408df3ef96 2364 glewlwyd_1.4.9-1.dsc b1f1797e3f306a52d67f00dab35a9ce2929d7f7f565f64117ac7d7b77b1f9e98 3420208 glewlwyd_1.4.9.orig.tar.gz 70b3165bb912f4247e20855736ed234898e08bf24e949f1ede6a7bde900ac6cb 665408 glewlwyd_1.4.9-1.debian.tar.xz 542f46e300916ce346e5dfa3a52b3d3cddcf98dd259b5dae22abd51e7d04775d 402668 fonts-glewlwyd_1.4.9-1_all.deb 6651f997fb8deb564e737c93ce9befccb68b90f3b6ff079bd243f1685675c429 1219560 glewlwyd-common_1.4.9-1_all.deb e33d86bfc41f3346ba7868a031c1b0ec470ffeab7307cff703ac2a222531f77a 240388 glewlwyd-dbgsym_1.4.9-1_amd64.deb cac5e86ba7bfb3f5edac70ba7d1e71666c32ef34efb4624d5e3a172409b1bac9 8346 glewlwyd_1.4.9-1_amd64.buildinfo 29c45ce00c3b6b2c8d4e266c217ae44e9af6ae03811155675e979fe5e936eb5f 121600 glewlwyd_1.4.9-1_amd64.deb Files: 4c338b95cbd6bdff5937c8f542b249a3 2364 web optional glewlwyd_1.4.9-1.dsc e941f5a92f51be42384210136c71cf48 3420208 web optional glewlwyd_1.4.9.orig.tar.gz d7ef4f360070c12d3c10eb9b2cb2f9c5 665408 web optional glewlwyd_1.4.9-1.debian.tar.xz 59b9dc25c7cf7d1193d6f272426e3abf 402668 fonts optional fonts-glewlwyd_1.4.9-1_all.deb 74311076222c0391be0bf1166a18f1cb
Bug#916873: python-twisted-core: Incorrect versioned dependency on python-attr
Package: python-twisted-core Version: 18.7.0-2~bpo9+1 Severity: serious Hi, With python-twisted-core and python-attr 16.3.0-1, I get the following error: [...] File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 100, in from twisted.internet import interfaces, protocol, address File "/usr/lib/python2.7/dist-packages/twisted/internet/address.py", line 23, in class IPv4Address(object): File "/usr/lib/python2.7/dist-packages/twisted/internet/address.py", line 37, in IPv4Address type = attr.ib(validator=attr.validators.in_(["TCP", "UDP"])) AttributeError: 'module' object has no attribute 'in_' Upgrading python-attr to the version from backports (17.4.0-2~bpo9+1) works. Kurt
Bug#916781: marked as done (slack-desktop: Segmentation fault)
Your message dated Wed, 19 Dec 2018 20:57:57 +0200 with message-id <20181219185757.GC20084@localhost> and subject line Re: Bug#916781: slack-desktop: Segmentation fault has caused the Debian Bug report #916781, regarding slack-desktop: Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slack-desktop Version: 3.3.3 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to run slack I recive a segmentation fault. It seems to be related to libnode. I ran valgrind slack and get: ==14607== Process terminating with default action of signal 11 (SIGSEGV) ==14607== Bad permissions for mapped region at address 0xDBF060 ==14607==at 0xDBF060: ??? (in /usr/lib/slack/slack) ==14607==by 0x710F071: node::http2::Http2Session::Callbacks::Callbacks(bool) (in /usr/lib/slack/libnode.so) ==14607==by 0x710F134: ??? (in /usr/lib/slack/libnode.so) ==14607==by 0x5853399: call_init.part.0 (dl-init.c:72) ==14607==by 0x5853495: call_init (dl-init.c:118) ==14607==by 0x5853495: _dl_init (dl-init.c:119) ==14607==by 0x58450C9: ??? (in /lib/x86_64-linux-gnu/ld-2.28.so) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (2, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages slack-desktop depends on: pn apt-transport-https ii gconf-service3.2.6-5 ii gconf2 3.2.6-5 ii gvfs-bin 1.38.1-1 ii libappindicator1 0.4.92-7 ii libcurl4 7.62.0-1 ii libgcrypt20 1.8.4-4 ii libgtk2.0-0 2.24.32-3 ii libnotify4 0.7.7-3 ii libnss3 2:3.41-1 ii libsecret-1-00.18.6-3 ii libudev1 239-15 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii python 2.7.15-3 ii xdg-utils1.1.3-1 slack-desktop recommends no packages. slack-desktop suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- On Tue, Dec 18, 2018 at 09:39:17AM -0500, Eric Taylor wrote: > Package: slack-desktop > Version: 3.3.3 > Severity: grave > Justification: renders package unusable >... There is no package slack-desktop in Debian, please report the problem to the provider of this package. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#916768: marked as done (libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1))
Your message dated Wed, 19 Dec 2018 18:53:41 + with message-id <20181219185340.ga10...@hindley.org.uk> and subject line Re: Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1) has caused the Debian Bug report #916768, regarding libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libelogind-dev-doc Version: 239.3-3+debian1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libelogind-dev-doc_239.3-3+debian1_all.deb ... Unpacking libelogind-dev-doc (239.3-3+debian1) ... dpkg: error processing archive /var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/sd-bus.3.gz', which is also in package libelogind-dev:amd64 239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb cheers, Andreas PS: please use a normal debian revision in the version, i.e. only number libelogind-dev=239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1_libelogind-dev-doc=239.3-3+debian1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Package: elogind Version: 239.3-4+debian1--- End Message ---
Bug#916855: [Debian-iot-maintainers] Bug#916855: glewlwyd: FTBFS: no dependency information found for /build/ulfius-build/libulfius.so.2.3
Hello, Thanks for the report. It's due to a change in the librairies header files recently. This change is incompatible with older glewlwyd cmake scripts. Glewlwyd 1.4.9 fixes that and the package will be uploaded soon.
Bug#916768: marked as done (libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1))
Your message dated Wed, 19 Dec 2018 18:29:30 + with message-id <20181219182930.ga9...@hindley.org.uk> and subject line Re: Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1) has caused the Debian Bug report #916768, regarding libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libelogind-dev-doc Version: 239.3-3+debian1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libelogind-dev-doc_239.3-3+debian1_all.deb ... Unpacking libelogind-dev-doc (239.3-3+debian1) ... dpkg: error processing archive /var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/sd-bus.3.gz', which is also in package libelogind-dev:amd64 239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb cheers, Andreas PS: please use a normal debian revision in the version, i.e. only number libelogind-dev=239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1_libelogind-dev-doc=239.3-3+debian1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Package: libelogind-dev-doc Version: 239.3-4+debian1 Closing manually as upload had typo in bug number. Sorry. Mark--- End Message ---
Processed: found 909385 in 8.2.0b-1, found 909383 in 1:6.1.3-2
Processing commands for cont...@bugs.debian.org: > found 909385 8.2.0b-1 Bug #909385 [vm] vm: fails to install with xemacs21 Marked as found in versions vm/8.2.0b-1. > found 909383 1:6.1.3-2 Bug #909383 [python-mode] python-mode: fails to install with xemacs21 Marked as found in versions python-mode/1:6.1.3-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 909383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909383 909385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896025: Segfault in test suite of new upstream version (Was: python-mne FTBFS with python-matplotlib 2.2.2-1)
Dear Andreas Thank you for taking a stab at this! I will try to not forget to look at it tomorrow (need to meet some other deadlines today). If you had a chance to try figuring out in what part segfault happens (I would just strace -f -o /tmp/strace.log python -m pytest ...) it might give a clue. Might as well be an xvfb issue On Wed, 19 Dec 2018, Andreas Tille wrote: > Control: tags -1 help > Control: tags -1 upstream > Control: forwarded -1 https://github.com/mne-tools/mne-python/issues/5806 > Hi, > it seems the matplotlib issue reported here is solved in the last > upstream version which I commited to packaging Git[1]. Unfortunately > there is another issue which I reported upstream[2]: > ... > make[1]: Entering directory '/build/python-mne-0.17+dfsg' > mkdir -p build > HOME=/build/python-mne-0.17+dfsg/build \ > MNE_DONTWRITE_HOME=true MNE_SKIP_SAMPLE_DATASET_TESTS=true > MNE_FORCE_SERIAL=true MNE_SKIP_NETWORK_TESTS=1 \ > xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac > +extension GLX +render -noreset" \ > py.test -s -v mne > = test session starts > == > platform linux2 -- Python 2.7.15+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 > -- /usr/bin/python2 > cachedir: .pytest_cache > rootdir: /build/python-mne-0.17+dfsg, inifile: setup.cfg > plugins: cov-2.6.0 > collecting ... Using default location ~/mne_data for testing... > Creating ~/mne_data > Using default location ~/mne_data for testing... > Using default location ~/mne_data for testing... > ... > Using default location ~/mne_data for testing... > Using default location ~/mne_data for testing... > Segmentation fault > make[1]: *** [debian/rules:26: override_dh_auto_test] Error 139 > make[1]: Leaving directory '/build/python-mne-0.17+dfsg' > I wonder whether one of the Uploaders (in CC) will be able to > fix this since I feel absolutely incompetent to solve this. > Kind regards >Andreas. > [1] https://salsa.debian.org/med-team/python-mne > [2] https://github.com/mne-tools/mne-python/issues/5806 -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Processed: Re: Bug#916846: [libreoffice-ogltrans] Blank screen with OpenGL transitions
Processing commands for cont...@bugs.debian.org: > found 916846 1:6.0.1-1 Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with OpenGL transitions Marked as found in versions libreoffice/1:6.0.1-1. > tag 916846 + confirmed Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with OpenGL transitions Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 916846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916846: [libreoffice-ogltrans] Blank screen with OpenGL transitions
found 916846 1:6.0.1-1 tag 916846 + confirmed thanks Hi, On Wed, Dec 19, 2018 at 04:51:58PM +0300, Alexander Kernozhitsky wrote: > Package: libreoffice-ogltrans [...] > Severity: grave > Justification: renders package unusable Sigh. And "just" becaus it's in an own package and that packages solely purpose is this... :( > When I try to use OpenGL transitions in LibreOffice Impress, I get a bank > screen for several seconds instead of a transition. This issue seems to be ^^ OpenGL, so 3D, so slow(er) :) > Debian-specific; I was trying the upstream version and it works fine. And when the actual transition should happen I get "blurry" stuff until the next slide is there. So yes, confirmed :-( > Hardware acceleration is enabled in configuration; renderer I use is Which does not do what you think it does. It does not to "hardware acceleration" in the first place. It afaicr is "Use cairo". > Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) here, whatever that is exactly :-) > Upstream bug report: > https://bugs.documentfoundation.org/show_bug.cgi?id=115716 Ah, so since 6.0.1? If you know such stuff, please mark it correctly... That said, we don't patch OpenGL parts or parts which could possibly affect it and don't do a "custom" splitout of this either... So it probably some system library at fault. Or some integration, though apparently it happens with both gtk3 and "gen"... In both cases that is still a upstream bug (, too). Maybe we should just stop shipping them, no one needs it. Regards, Rene
Bug#915831: [Pkg-zfsonlinux-devel] Bug#915831: zfs init file upgrade
On Thu, Dec 20, 2018 at 1:15 AM Chris Zubrzycki wrote:
>
> I would like to amend my reply. The files are no longer in the deb, however
> they are still listed by dpkg -L zfsutils-linux. I do not understand how the
> solution to an ordering issue is to remove needed init files that have been
> fought to be included for literally years.
>
The init.d scripts are not present in zfsutils-linux/0.7.12-1~bpo9+1,
see: https://packages.debian.org/stretch-backports/amd64/zfsutils-linux/filelist
Literal reasons about whether init.d scripts should be included in
stretch-backports version do not make sense to such a serious storage
package, which may cause interruptions (or data loss in extreme
situation) when unexpected conditions occur. I'm temped to not ship
init.d scripts for Buster if there is any important issue open when
freeze approaches (e.g. bug #915831).
It's not a fight for any literal reason about init.d scripts but I
don't want to ship something known to be breaking existing stuff, also
I wish the package behaves (almost) identically on all supported init
(systemd, sysv/insserv, sysv/openrc, if desired). Because I don't have
an enterprise environment to battle test these stuff, I can't promise
to test and fix issues in non-stable branches. Stable branches I
consider are: stable, stable-bpo, oldstable-bpo{,-sloppy}.
Let me clarify about what is needed: please anyone interested, step in
and take care of init.d scripts by upstreaming any changes needed,
also make sure to test them extensively and continuously. I'm happy to
apply init.d changes ack'ed by upstream, but will discard any
non-trivial feature-wise debian change (i.e. the OpenRC patch).
Regards,
Aron
Bug#893409: pixelmed FTBFS with openjdk-9
On 12/19/18 11:46 AM, Andreas Tille wrote:
> Hi,
>
> On Wed, Dec 19, 2018 at 10:39:55AM +0100, Olivier Sallou wrote:
>>> The missing class is in libjaxb-api-java. Just make sure it's on the
>>> CLASSPATH.
>> yeap, an other issue at java migration to openjdk 10/11
>>
>> Adding this lib to deps should fix the pb
- I have fixed the problem, updating patch (lib needed to be added to
other Makefile)
- There were some other issues with an old jdk package moved to an other
location, from JDK 9 in 2016, which is not exported [0]. Surprisingly it
compiles anyway, but does it work as expected?? It seems there is a
new API (java.lang.ref.Cleaner) but I'm not sure it could be replaced as
easily (and without knowing side effects), it should be updated by upstream
In the meanwhile I renamed the related package in patch.
- vecmath needed to be added as well in Makefile (done)
- javadoc generation classpath needed to be updated as well (done)
- I think that vecmath and jaxb-api jars will need to be added in
runtime classpath (debian/DicomXX etc..) as well (NOT done)
- 4 tests are failing (surprisingly, packaging continues)
- lintian: some errors, documentation is not in correct directory
(libpixelmed-java-doc expects files in
/usr/share/doc/libpixelmed-java-doc but doc is in
/usr/share/doc/libpixelmed-java) (NOT fixed)
I have pushed my updates to git (file not found , certainly a result not
generated, but no additional info)
[0] https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8148117
Olivier
> Thanks for the quick help. I tried:
>
>
> diff --git a/debian/control b/debian/control
> index e0548ee..3f8b86c 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -14,7 +14,8 @@ Build-Depends-Indep: default-jdk,
> libjmdns-java,
> libvecmath-java,
> libpixelmed-codec-java,
> - libjsonp-java
> + libjsonp-java,
> + libjaxb-api-java
> Standards-Version: 4.2.1
> Vcs-Browser: https://salsa.debian.org/med-team/pixelmed
> Vcs-Git: https://salsa.debian.org/med-team/pixelmed.git
> diff --git a/debian/patches/fixdoc.patch b/debian/patches/fixdoc.patch
> index 752b78c..1737f5f 100644
> --- a/debian/patches/fixdoc.patch
> +++ b/debian/patches/fixdoc.patch
> @@ -11,7 +11,7 @@ Index: pixelmed-20140326/Makefile
> rm -rf docs/javadoc
> javadoc \
> - -classpath
> .:lib/additional/excalibur-bzip2-1.0.jar:lib/additional/hsqldb.jar:lib/additional/vecmath1.2-1.14.jar:lib/additional/commons-codec-1.3.jar:lib/additional/commons-net2.jar:lib/additional/jmdns.jar:lib/additional/jpedalSTD.jar:lib/junit/junit-4.8.1.jar
> \
> -+ -classpath
> .:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar
> \
> ++ -classpath
> .:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar:/usr/share/java/jaxb-api.jar
> \
> -link http://download.oracle.com/javase/1.5.0/docs/api/ \
> -link http://jpedal.org/javadoc/ \
> -link http://www.hsqldb.org/doc/src/ \
> diff --git a/debian/patches/jaxb-api.patch b/debian/patches/jaxb-api.patch
> new file mode 100644
> index 000..85760dd
> --- /dev/null
> +++ b/debian/patches/jaxb-api.patch
> @@ -0,0 +1,16 @@
> +Description: For OpenJDK 11 jaxb needs to be in classpath
> +Bug-Debian: https://bugs.debian.org/893409
> +Author: Andreas Tille
> +Last-Update: Wed, 19 Dec 2018 08:53:43 +0100
> +
> +--- a/Makefile.common.mk
> b/Makefile.common.mk
> +@@ -65,7 +65,7 @@ JAVACOPTIONS = -O ${JAVACTARGETOPTIONS}
> +
> + .java.class:
> + export JAVAVERSIONTARGETJARFILE=${JAVA_HOME}/jre/lib/rt.jar; javac
> ${JAVACOPTIONS} \
> +- -classpath
> ${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}
> \
> ++ -classpath
> ${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}:/usr/share/java/jaxb-api.jar
> \
> + -sourcepath ${PATHTOROOT} $<
> +
> + .png.ico:
> diff --git a/debian/patches/series b/debian/patches/series
> index 10286d4..6abfc45 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -16,3 +16,4 @@ set_java_home.patch
> imageio.patch
> no_Xdiags_verbose.patch
> do_not_set_bootclasspath.patch
> +jaxb-api.patch
>
>
>
> I've pushed these changes but unfortunately it does not help. :-(
>
> Any further hints?
>
> Kind regards
>
> Andreas.
>
>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Bug#916800: phybin: FTBFS with newer GHC
Hi, Am Dienstag, den 18.12.2018, 23:35 +0100 schrieb Andreas Tille: > Hi Joachim, > > On Tue, Dec 18, 2018 at 10:57:15PM +0100, Joachim Breitner wrote: > > Would not be hard to fix, but is there a chance that upstream could just > > release a version that works with a current compiler? > > I'm afraid upstream is not very active but would be happy about a patch. I submitted a patch to upstream, feel fee to get it from github if you need it earlier: https://github.com/rrnewton/PhyBin/pull/13 https://patch-diff.githubusercontent.com/raw/rrnewton/PhyBin/pull/13.patch Cheers, Joachim -- Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/ signature.asc Description: This is a digitally signed message part
Bug#915831: zfs init file upgrade
I would like to amend my reply. The files are no longer in the deb, however they are still listed by dpkg -L zfsutils-linux. I do not understand how the solution to an ordering issue is to remove needed init files that have been fought to be included for literally years.
Bug#916778: marked as done (cylc: FTBFS when built with dpkg-buildpackage -A)
Your message dated Wed, 19 Dec 2018 17:04:13 +
with message-id
and subject line Bug#916778: fixed in cylc 7.8.0-4
has caused the Debian Bug report #916778,
regarding cylc: FTBFS when built with dpkg-buildpackage -A
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.)
--
916778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cylc
Version: 7.8.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster with dpkg-buildpackage -A but it failed:
[...]
dh binary-indep --with python2
dh_testroot -i
dh_prep -i
dh_installdirs -i
debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
# Don't support gpanel. Requires gnome2's gnomeapplet.
rm -rf bin/cylc-gpanel conf/gpanel
mkdir -p debian/tmp/usr/bin
mkdir -p debian/tmp/etc/cylc/gcylcrc
cp bin/cylc debian/tmp/usr//bin/cylc
cp etc/gcylc.rc.eg debian/tmp/etc/cylc/gcylcrc/gcylc.rc
cp etc/global-tests.rc.eg debian/tmp/etc/cylc/gcylcrc/global-tests.rx
cp etc/gcylc-themes.rc debian/tmp/etc/cylc/gcylcrc
find . -name '*.t' -exec chmod +x {} \;
find . -name test_header -exec chmod +x {} \;
chmod +x bin/*
install -d -m 0755
/<>/debian/cylc-el/usr/share/emacs/site-lisp/cylc
install-m 0644 etc/syntax/cylc-mode.el \
/<>/debian/cylc-el/usr/share/emacs/site-lisp/cylc/cylc-mode.el
# Do this part if full build (not just arch-dependent)
make[1]: Leaving directory '/<>'
dh_install -i
dh_installdocs -i
dh_installchangelogs -i
dh_installexamples -i
dh_installexamples: Cannot find (any matches for) "examples/*" (tried in .)
dh_python2 -i
E: dh_python2 dh_python2:408: no package to act on (python-foo or one with
${python:Depends} in Depends)
dh_perl -i
dh_link -i
dh_strip_nondeterminism -i
dh_compress -i
debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
# Delete after install. Use packages instead.
for p in Pyro cherrypy markupsafe jinja2 ; do \
rm -rf debian/python-cylc/usr/lib/python2.7/dist-packages/$p ; \
done
# shipped separately
find debian/python-cylc -name glyphicons-halflings-regular.ttf -delete
find: 'debian/python-cylc': No such file or directory
make[1]: *** [debian/rules:38: override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
The usual recipe is to split override_dh_foo into override_dh_foo-arch
and override_dh_foo-indep, but in this case it seems a little bit strange
that you are deleting things in the fixperms target (which is usually
for fixing perms).
Also, please consider uploading in source-only form (dpkg-buildpackage -S)
so that this kind of bugs do not propagate to testing and we have official
build logs for the arch:all autobuilder, currently missing here:
https://buildd.debian.org/status/package.php?p=cylc
Thanks.
--- End Message ---
--- Begin Message ---
Source: cylc
Source-Version: 7.8.0-4
We believe that the bug you reported is fixed in the latest version of
cylc, 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.
Alastair McKinstry (supplier of updated cylc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 19 Dec 2018 16:38:19 +
Source: cylc
Binary: cylc python-cylc
Architecture: source all amd64
Version: 7.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry
Changed-By: Alastair McKinstry
Description:
cylc - Workflow scheduler
python-cylc - Python libraries for cylc workflow scheduler
Closes: 916778
Changes:
cylc (7.8.0-4) unstable; urgency=medium
.
* Fix FTBFS with -A. Closes: #916778
Checksums-Sha1:
b3f84f3000f9d1c0d2e935485bd79cab6f367de4 2098 cylc_7.8.0-4.dsc
d56461586e8d496787d706c62ac26733e480b81d
Bug#915831: zfs upgrade
I was able to upgrade from 0.7.11 to 0.7.12 without any issues, using stretch-backports. Thankfully, the init.d scripts are still there, contrary to Aron’s changelog entry. -chris zubrzycki - -- PGP ID: 0xA2ABC070 Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070 "Sadly, text alone cannot convey the depths of my sarcasm."
Bug#916565: marked as done (libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script subprocess returned error exit status 1)
Your message dated Wed, 19 Dec 2018 16:49:12 +
with message-id
and subject line Bug#916565: fixed in dh-fortran-mod 0.6
has caused the Debian Bug report #916565,
regarding libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal
script subprocess returned error exit status 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
916565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi3,openmpi-common,openmpi-doc
Version: 3.1.3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
>From the attached log (scroll to the bottom...):
Removing libopenmpi3:amd64 (3.1.3-5) ...
dpkg: error processing package libopenmpi3:amd64 (--remove):
installed libopenmpi3:amd64 package post-removal script subprocess returned
error exit status 1
Removing openmpi-common (3.1.3-5) ...
dpkg: error processing package openmpi-common (--remove):
installed openmpi-common package post-removal script subprocess returned
error exit status 1
Removing openmpi-doc (3.1.3-5) ...
dpkg: error processing package openmpi-doc (--remove):
installed openmpi-doc package post-removal script subprocess returned error
exit status 1
cheers,
Andreas
libopenmpi3_3.1.3-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dh-fortran-mod
Source-Version: 0.6
We believe that the bug you reported is fixed in the latest version of
dh-fortran-mod, 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.
Alastair McKinstry (supplier of updated dh-fortran-mod
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 19 Dec 2018 15:40:05 +
Source: dh-fortran-mod
Binary: dh-fortran-mod
Architecture: source all
Version: 0.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Alastair McKinstry
Description:
dh-fortran-mod - debhelper add-on to handle Fortran '.mod' files
Closes: 916565
Changes:
dh-fortran-mod (0.6) unstable; urgency=medium
.
* Add spaces into preinst / postrm fragments. Closes: #916565
Checksums-Sha1:
fd79c936521004dcacec27822e0b700aecc3c02c 1693 dh-fortran-mod_0.6.dsc
d3c30044eb468905c11ab257acfb1f743d5c6cc2 6132 dh-fortran-mod_0.6.tar.xz
75ee60f784d53411291065306f1e47a8551af8c7 9584 dh-fortran-mod_0.6_all.deb
e903ae7d0b2e2d55ce3278ea5d73a4fc72b26b22 5199
dh-fortran-mod_0.6_amd64.buildinfo
Checksums-Sha256:
6f0ba8d19cdb93ab26a4a515f40626c2d98940e0099d01d1076487a1acfa5db9 1693
dh-fortran-mod_0.6.dsc
b22cfdb1d3004071d27f8d00dd07090c5054868ea6a558aa1c53fae50e1dcebe 6132
dh-fortran-mod_0.6.tar.xz
d833729a36070fbf8a80294db1100ae5bd7398be0b6ae370262bea756c33f9d8 9584
dh-fortran-mod_0.6_all.deb
72f7b4e989275f93ff0671d7f3f21cceb7fdeb67494d681b39ca06d61e663000 5199
dh-fortran-mod_0.6_amd64.buildinfo
Files:
5367034eff3ff2af2f98b48860b74a8b 1693 devel optional dh-fortran-mod_0.6.dsc
92c5676ba344539031863174c8b5794d 6132 devel optional dh-fortran-mod_0.6.tar.xz
056f208ddd87297cfe69d0989c468ca3 9584 devel optional dh-fortran-mod_0.6_all.deb
39084dcb6d8646e6305403ca24b9ca73 5199 devel optional
dh-fortran-mod_0.6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAlwacZEACgkQy+a7Tl2a
06WDbhAAmR0A5OKv7eVn75yXAozFO13GIJ4AxihKppl8rL7+HGKUQatsFGFNPSjl
ZbzaUz34em41x8j/adMP98AoPY51V30RxaZbCfuhDtiUG7AIdY2FsUSBkyU/1uWT
v7rR4vb93P6U3RiXUB4kcaaqfWyq7ABJ7gZcC+vgqgqZJoqWO4hiLzd8y6xbSR0Y
CRCVs4oNjRoOEuyhqwBa7hnxg2vUzf3ACsMDPXFU0AFgNNuxMeBxEqITdtl6oq6o
EXXU2D+0P5uK9cb+S7c7pr4UWbH99p0mkY4fM674HxfOUhNirSQNBHNaRo37pp9k
dr0UqWlF3axQIN/4qVU5CaHp3HJqUBHuTRGtqgZht6CeNg3PUYA43yyMUFlEhE1q
0ZDqUVUP9LBlXK9PdodJ/8OkplfY8v+ldNJvuan06ey+J139f3q4z6Bk1MQk4h94
l2uR6CbwZq16ZRhgAl/O1poKI6mwIbx77syEw/vN95jEzrWvlfsj9zTqLSAgSnGW
hWBgpZe4GEbLax4x7LfTGd4lSAH7b3T8csD6JBy/i8YIL9J+sPos5/HBuVwG2ztz
Yahcl5w8+DvLK9O7kIK2cIaF8DVmgTLXHCKQzIzhAh2kboWtNheuz5zgd24AZvlQ
Bug#893409: pixelmed FTBFS with openjdk-9
On 12/19/18 11:46 AM, Andreas Tille wrote:
> Hi,
>
> On Wed, Dec 19, 2018 at 10:39:55AM +0100, Olivier Sallou wrote:
>>> The missing class is in libjaxb-api-java. Just make sure it's on the
>>> CLASSPATH.
>> yeap, an other issue at java migration to openjdk 10/11
>>
>> Adding this lib to deps should fix the pb
> Thanks for the quick help. I tried:
>
>
> diff --git a/debian/control b/debian/control
> index e0548ee..3f8b86c 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -14,7 +14,8 @@ Build-Depends-Indep: default-jdk,
> libjmdns-java,
> libvecmath-java,
> libpixelmed-codec-java,
> - libjsonp-java
> + libjsonp-java,
> + libjaxb-api-java
> Standards-Version: 4.2.1
> Vcs-Browser: https://salsa.debian.org/med-team/pixelmed
> Vcs-Git: https://salsa.debian.org/med-team/pixelmed.git
> diff --git a/debian/patches/fixdoc.patch b/debian/patches/fixdoc.patch
> index 752b78c..1737f5f 100644
> --- a/debian/patches/fixdoc.patch
> +++ b/debian/patches/fixdoc.patch
> @@ -11,7 +11,7 @@ Index: pixelmed-20140326/Makefile
> rm -rf docs/javadoc
> javadoc \
> - -classpath
> .:lib/additional/excalibur-bzip2-1.0.jar:lib/additional/hsqldb.jar:lib/additional/vecmath1.2-1.14.jar:lib/additional/commons-codec-1.3.jar:lib/additional/commons-net2.jar:lib/additional/jmdns.jar:lib/additional/jpedalSTD.jar:lib/junit/junit-4.8.1.jar
> \
> -+ -classpath
> .:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar
> \
> ++ -classpath
> .:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar:/usr/share/java/jaxb-api.jar
> \
> -link http://download.oracle.com/javase/1.5.0/docs/api/ \
> -link http://jpedal.org/javadoc/ \
> -link http://www.hsqldb.org/doc/src/ \
> diff --git a/debian/patches/jaxb-api.patch b/debian/patches/jaxb-api.patch
> new file mode 100644
> index 000..85760dd
> --- /dev/null
> +++ b/debian/patches/jaxb-api.patch
> @@ -0,0 +1,16 @@
> +Description: For OpenJDK 11 jaxb needs to be in classpath
> +Bug-Debian: https://bugs.debian.org/893409
> +Author: Andreas Tille
> +Last-Update: Wed, 19 Dec 2018 08:53:43 +0100
> +
> +--- a/Makefile.common.mk
> b/Makefile.common.mk
> +@@ -65,7 +65,7 @@ JAVACOPTIONS = -O ${JAVACTARGETOPTIONS}
> +
> + .java.class:
> + export JAVAVERSIONTARGETJARFILE=${JAVA_HOME}/jre/lib/rt.jar; javac
> ${JAVACOPTIONS} \
> +- -classpath
> ${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}
> \
> ++ -classpath
> ${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}:/usr/share/java/jaxb-api.jar
> \
> + -sourcepath ${PATHTOROOT} $<
> +
> + .png.ico:
> diff --git a/debian/patches/series b/debian/patches/series
> index 10286d4..6abfc45 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -16,3 +16,4 @@ set_java_home.patch
> imageio.patch
> no_Xdiags_verbose.patch
> do_not_set_bootclasspath.patch
> +jaxb-api.patch
>
>
>
> I've pushed these changes but unfortunately it does not help. :-(
I'm looking at the issue
>
> Any further hints?
>
> Kind regards
>
> Andreas.
>
>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Bug#916666: marked as done (python-pip's autopkg tests are failing (blocking python3.7))
Your message dated Wed, 19 Dec 2018 16:04:49 + with message-id and subject line Bug#91: fixed in python-pip 18.1-3 has caused the Debian Bug report #91, regarding python-pip's autopkg tests are failing (blocking python3.7) 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.) -- 91: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=91 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pythonn-pip Version: 18.1-2 Severity: serious Tags: sid buster python-pip's autopkg tests are failing (blocking python3.7): autopkgtest [14:05:30]: summary pip2-root.sh PASS pip3-root.sh PASS pip2-user.sh FAIL stderr: The script world is installed in '/tmp/autopkgtest-lxc.a8273n4w/downtmp/autopkgtest_tmp/.local/bin' which is not on PATH. pip3-user.sh FAIL stderr: The script world is installed in '/tmp/autopkgtest-lxc.a8273n4w/downtmp/autopkgtest_tmp/.local/bin' which is not on PATH. pip3-editable.sh PASS --- End Message --- --- Begin Message --- Source: python-pip Source-Version: 18.1-3 We believe that the bug you reported is fixed in the latest version of python-pip, 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. Andrej Shadura (supplier of updated python-pip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 19 Dec 2018 16:49:19 +0100 Source: python-pip Binary: python-pip python3-pip python-pip-whl Architecture: source Version: 18.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Andrej Shadura Description: python-pip - Python package installer python-pip-whl - Python package installer python3-pip - Python package installer Closes: 91 Changes: python-pip (18.1-3) unstable; urgency=medium . * Add gitlab-ci.yml. * Fix autopkgtests (Closes: #91): - Add $HOME/.local/bin to PATH to prevent pip’s warnings. - Make sure user tests always run as non-root to test that pip automatically enables --user. Checksums-Sha1: fdb2303b5decaba93debcdb3fb9ec6692b9691d1 2457 python-pip_18.1-3.dsc 05b9b1800bc7f5dd7e842d238f6049e09800fb80 18012 python-pip_18.1-3.debian.tar.xz Checksums-Sha256: 254898a324555f61f739b06221eeed9a7259f58843cca06c5dea2815e7f03a1b 2457 python-pip_18.1-3.dsc 0a44f3e3ed290057e62a3e3e5e7c75c611c467baaf6bf0e81c3e9ff503b54b33 18012 python-pip_18.1-3.debian.tar.xz Files: 0a116b9b1fbf0671766c3ab94241cb2f 2457 python optional python-pip_18.1-3.dsc 072a42cf33d25eeebd018e9a7a97023e 18012 python optional python-pip_18.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlwaabkACgkQXkCM2RzY OdJa9Af9HwmGpHj/ViugvDMyIf1dTuyHPyAsNJVtwvBzS6nbwoZSHnTs+MwXdacn n+5o8Nt/iAneVTFl+JmzEfLWZiEv4bpGBGPH+k8UkpxrNPFUzPY7u6a+Dch6jmio KrMM5Lt81/lkjCfuw0X2yNjX7aiizegi+gwH60bsKncgnPAqNf2T6h0zTJ+BpAEF WozkkAhAV4+2NC9acnDxjqyMfeoJMQH+IsoDoDYHC+myY7KMvUV+weKOAwXqCLF/ cCTFw3ZamQXN1LnQvj7pi1plM+z2rJ+cRhVCCdlMwvi1E+aDIquGcDV8Auxu6lgp TV0L3d8qlQcEGVNAP3fShcq/4eBhkw== =lvff -END PGP SIGNATURE End Message ---
Bug#916858: supercollider-emacs: fails to install with xemacs21
Package: supercollider-emacs
Version: 1:3.7.0~repack-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1:3.6.6~repack-2-1
Control: found -1 1:3.8.0~repack-2
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 supercollider-emacs (1:3.7.0~repack-4) ...
Install supercollider-emacs for xemacs21
install/SuperCollider: Handling install for emacsen flavor xemacs21
Loading /usr/share/emacs/site-lisp/debian-startup...
Loading 00debian...
Loading site-start...
Loading 00debian-vars...
Loading 50supercollider-emacs...
Error while loading 50supercollider-emacs: Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-browser.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-browser.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-browser.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-dev.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-dev.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-dev.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-document.el...
Wrote /usr/share/xemacs21/site-lisp/SuperCollider/sclang-document.elc
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-help.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-help.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-help.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-interp.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-interp.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-interp.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-keys.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-keys.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-keys.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-language.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-language.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-language.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-menu.el...
Wrote /usr/share/xemacs21/site-lisp/SuperCollider/sclang-menu.elc
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-minor-mode.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-minor-mode.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-minor-mode.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-mode.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-mode.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-mode.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-server.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-server.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-server.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-util.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-util.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-util.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-vars.el...
Wrote /usr/share/xemacs21/site-lisp/SuperCollider/sclang-vars.elc
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang-widgets.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang-widgets.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang-widgets.el:
Invalid read syntax: "#"
Compiling /usr/share/xemacs21/site-lisp/SuperCollider/sclang.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/SuperCollider/sclang.el:
!! Invalid read syntax (("#"))
>>Error occurred processing sclang.el:
Invalid read syntax: "#"
Done
ERROR: install script from supercollider-emacs package failed
dpkg: error processing package supercollider-emacs (--configure):
subprocess installed post-installation script returned
Processed: supercollider-emacs: fails to install with xemacs21
Processing control commands: > found -1 1:3.6.6~repack-2-1 Bug #916858 [supercollider-emacs] supercollider-emacs: fails to install with xemacs21 Marked as found in versions supercollider/1:3.6.6~repack-2-1. > found -1 1:3.8.0~repack-2 Bug #916858 [supercollider-emacs] supercollider-emacs: fails to install with xemacs21 Marked as found in versions supercollider/1:3.8.0~repack-2. -- 916858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915692: debdiff for 915692, 915419
Dear Maintainer, In order to allow the DPDK 17.11 -> 18.11 transition to happen [1], I intend to upload a source NMU fixing 915692 and 915419 (debdiff attached) either at the end of this week or at the beginning of the next to DELAYED/1. I hope this does not cause any troubles, and please let me know if this would be an issue, and/or if you prefer an alternative solution. Thank you! -- Kind regards, Luca Boccassi [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916351diff -Nru collectd-5.8.1/debian/changelog collectd-5.8.1/debian/changelog --- collectd-5.8.1/debian/changelog 2018-11-23 00:01:43.0 +0100 +++ collectd-5.8.1/debian/changelog 2018-12-19 15:52:36.0 +0100 @@ -1,3 +1,15 @@ +collectd (5.8.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Stop building lvm plugin and remove dependency from liblvm2-dev, +which is deprecated. +(Closes: #915692) + * Backport dpdk_configure_check.patch from the upstream 5.8 release +branch to fix build with DPDK 18.11. +(Closes: #915419) + + -- Luca Boccassi Wed, 19 Dec 2018 15:52:36 +0100 + collectd (5.8.1-1) unstable; urgency=medium * New upstream release. diff -Nru collectd-5.8.1/debian/control collectd-5.8.1/debian/control --- collectd-5.8.1/debian/control 2018-11-23 00:01:43.0 +0100 +++ collectd-5.8.1/debian/control 2018-12-19 15:51:04.0 +0100 @@ -28,7 +28,6 @@ libkvm-dev [kfreebsd-any], libldap2-dev, liblua5.3-dev, - liblvm2-dev [linux-any], libmemcached-dev, libmicrohttpd-dev, libmodbus-dev, @@ -156,7 +155,6 @@ * logging to files, STDOUT and STDERR: logfile * logging in logstash's JSON event format: log_logstash * embedded Lua interpreter: lua - * Logical Volume Manager usage: lvm * Machine Check Exceptions notifications: mcelog * Atheros wireless LAN chipset statistics: madwifi * motherboard monitor: mbmon diff -Nru collectd-5.8.1/debian/patches/dpdk_configure_check.patch collectd-5.8.1/debian/patches/dpdk_configure_check.patch --- collectd-5.8.1/debian/patches/dpdk_configure_check.patch 1970-01-01 01:00:00.0 +0100 +++ collectd-5.8.1/debian/patches/dpdk_configure_check.patch 2018-12-19 15:52:03.0 +0100 @@ -0,0 +1,44 @@ +Author: Luca Boccassi +Origin: https://github.com/collectd/collectd/commit/b29454cdf22a197924d35bb2da0840df9cbd65f6 +Forwarded: https://github.com/collectd/collectd/pull/3015 +Description: do not use -ldpdk for configure check + The AC_CHECK_LIB test runs unconditionally, and fails with DPDK 18.11 + when built with Meson as there is no longer a libdpdk.so linker script, + but only a pkg-config file, so -ldpdk (which is what AC_CHECK_LIB runs) + fails. + Use AC_LINK_IFELSE instead, with compiler and linker flags set + appropriately. +--- a/configure.ac b/configure.ac +@@ -2380,13 +2380,30 @@ if test "x$with_libdpdk" != "xno"; then + fi + + if test "x$with_libdpdk" = "xyes"; then ++ SAVE_LIBS="$LIBS" ++ LIBS="$LIBDPDK_LIBS $LIBS" + SAVE_LDFLAGS="$LDFLAGS" + LDFLAGS="$LIBDPDK_LDFLAGS $LDFLAGS" +- AC_CHECK_LIB([dpdk], [rte_eal_init], ++ SAVE_CPPFLAGS="$CPPFLAGS" ++ CPPFLAGS="$LIBDPDK_CPPFLAGS $CPPFLAGS" ++ SAVE_CFLAGS="$CFLAGS" ++ CFLAGS="$LIBDPDK_CFLAGS $CFLAGS" ++ AC_LINK_IFELSE( ++[ ++ AC_LANG_PROGRAM( ++[[ ++ #include ++]], ++[[return rte_eal_init(0, NULL);]] ++ ) ++], + [with_libdpdk="yes"], + [with_libdpdk="no (symbol 'rte_eal_init' not found)"] + ) ++ LIBS="$SAVE_LIBS" + LDFLAGS="$SAVE_LDFLAGS" ++ CPPFLAGS="$SAVE_CPPFLAGS" ++ CFLAGS="$SAVE_CFLAGS" + fi + + # }}} diff -Nru collectd-5.8.1/debian/patches/series collectd-5.8.1/debian/patches/series --- collectd-5.8.1/debian/patches/series 2018-11-22 23:22:49.0 +0100 +++ collectd-5.8.1/debian/patches/series 2018-12-19 15:52:28.0 +0100 @@ -4,3 +4,4 @@ nagios-debian-paths.patch i2c_detection.patch liblvm2app_depreciation_warning.patch +dpdk_configure_check.patch diff -Nru collectd-5.8.1/debian/rules collectd-5.8.1/debian/rules --- collectd-5.8.1/debian/rules 2018-11-23 00:01:43.0 +0100 +++ collectd-5.8.1/debian/rules 2018-12-19 15:51:28.0 +0100 @@ -96,6 +96,10 @@ # migrating to testing. confflags += --disable-mqtt +# disable lvm plugin, liblvm2app is deprecated upstream, #915692 +# Cf. https://github.com/collectd/collectd/issues/2647 +confflags += --disable-lvm + # These plugins are Linux-specific. ifeq ($(DEB_HOST_ARCH_OS),kfreebsd) confflags += \ @@ -109,7 +113,6 @@ --disable-ipc \ --disable-iptables \ --disable-ipvs \ - --disable-lvm \ --disable-madwifi \ --disable-md \ --disable-netlink \ signature.asc Description: This is a digitally signed message part
Bug#915171: Upstream ticket
control: tag -1 + patch On 2018-12-19 10:23, Juhani Numminen wrote: > forwarded 915171 https://github.com/kjn/lbzip2/issues/22 > stop > Note that the patch has been committed a few months ago in the upstream gnulib repository: http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#916857: el-get: fails to install with xemacs21
Package: el-get Version: 3.1-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts 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...): [...] Selecting previously unselected package el-get. (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35% ^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 13211 files and directories currently installed. ) Preparing to unpack .../el-get_3.1-1.1_all.deb ... Unpacking el-get (3.1-1.1) ... Setting up el-get (3.1-1.1) ... ERROR: el-get is broken - called emacs-package-install as a new-style add-on, but has no compat file. Install el-get for emacs Install el-get for xemacs21 install/el-get: Handling install for emacsen flavor xemacs21 Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Loading site-start... Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Loading site-start... [...] Loading 00debian... Loading site-start... Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Loading site-start... Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Error while loading 00debian: Variable binding depth exceeds max-specpdl-size Compiling /usr/share/xemacs21/site-lisp/el-get/el-get.el... Ignoring `eval:' in file's local variables Ignoring `eval:' in file's local variables Ignoring `eval:' in file's local variables Ignoring `eval:' in file's local variables Loading dired-mule... While compiling toplevel forms in file /usr/share/xemacs21/site-lisp/el-get/el-get.el: !! Wrong number of arguments ((require 3)) >>Error occurred processing el-get.el: Wrong number of arguments: require, 3 Done ERROR: install script from el-get package failed dpkg: error processing package el-get (--configure): installed el-get package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: el-get Cheers, Andreas el-get=3.1-1.1_xemacs21.log.gz Description: application/gzip
Processed: Re: Upstream ticket
Processing control commands: > tag -1 + patch Bug #915171 [src:lbzip2] lbzip2 FTBFS with glibc 2.28 Added tag(s) patch. -- 915171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915151: 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."
On 2018-12-06 23:57, Rene Luria wrote: > Hello, > > On Sat, 1 Dec 2018 08:07:24 +0100 Helmut Grohne wrote: > > gzip fails to build from source in unstable (since the glibc upgrade to > > 2.28): > > (…) > > > gnulib likes to use this construct to detect glibc: > > > > | #if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, > > Haiku, Linux libc5 */ > > > > Unfortunately, _IO_ftrylockfile got removed from glibc/2.28 and > > __GNU_LIBRARY__ is 6, so glibc is not a GNU libc. > > > > gnulib has a history of breaking packages frequently. What makes matters > > worse is that gnulib gets embedded rather than used like any other > > component. So fixing this bug in gnulib does not fix gzip. I therefore > > cloned a separate instance as it still breaks e.g. lbzip2. > > Would the here attached patch help ? > On most files in lib we can use the == 6 construct. Only for fflush.c this > can’t be done because it uses removed libio.h references. I think you should use the patch that has been committed to the upstream gnulib: http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#916565: libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script subprocess returned error exit status 1
Control: reassign -1 dh-fortran-mod Control: affects -1 + openmpi Control: tags -1 + patch > rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such > file or directory > rm: cannot remove 'End': No such file or directory > rm: cannot remove 'automatically': No such file or directory > rm: cannot remove 'added': No such file or directory > rm: cannot remove 'section': No such file or directory Looking at the postrm script, I see rmdir --ignore-fail-on-non-empty --parents /usr/lib/$multiarch/fortran/$base [ -d /usr/lib/$multiarch/fortran/$base ] && rm /usr/lib/$multiarch/fortran/$cmplr# End automatically added section Its seems to be coming from dh-fortran-mod: the postrm-fortran-mod does not have a \n on the last line. Could you apply the attached patch? Then we'll have to rebuild openmpi and possibly others with the same resulting issue. Samuel --- postrm-fortran-mod.orig 2018-12-19 16:20:54.080650624 +0100 +++ postrm-fortran-mod 2018-12-19 16:20:57.120660630 +0100 @@ -3,4 +3,4 @@ cmplr="#FCOMPILER#" rmdir --ignore-fail-on-non-empty --parents /usr/lib/$multiarch/fortran/$base -[ -d /usr/lib/$multiarch/fortran/$base ] && rm /usr/lib/$multiarch/fortran/$cmplr \ No newline at end of file +[ -d /usr/lib/$multiarch/fortran/$base ] && rm /usr/lib/$multiarch/fortran/$cmplr
Processed: Re: Bug#916565: libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script subprocess returned error exit status 1
Processing control commands:
> reassign -1 dh-fortran-mod
Bug #916565 [libopenmpi3,openmpi-common,openmpi-doc]
libopenmpi3,openmpi-{common,doc}: fails to remove: post-removal script
subprocess returned error exit status 1
Bug reassigned from package 'libopenmpi3,openmpi-common,openmpi-doc' to
'dh-fortran-mod'.
No longer marked as found in versions 3.1.3-5.
Ignoring request to alter fixed versions of bug #916565 to the same values
previously set
> affects -1 + openmpi
Bug #916565 [dh-fortran-mod] libopenmpi3,openmpi-{common,doc}: fails to remove:
post-removal script subprocess returned error exit status 1
Added indication that 916565 affects openmpi
> tags -1 + patch
Bug #916565 [dh-fortran-mod] libopenmpi3,openmpi-{common,doc}: fails to remove:
post-removal script subprocess returned error exit status 1
Added tag(s) patch.
--
916565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915150: gzip: FTBFS with glibc 2.28
On 2018-12-01 16:05, Santiago Vila wrote: > FWIW: I found a fix for m4 and sharutils in this commit by Paul Eggert: > > https://lists.gnu.org/r/bug-gnulib/2018-03/msg2.html > > Based on the same commit, the attached patch should work for gzip. This patch has been committed in the upstream gnulib repository, so it's definitely the right way to fix the bug: http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#916840: marked as done (groovy: FTBFS with Java 11 due to polymorphic signature calls & SecurityManager changes)
Your message dated Wed, 19 Dec 2018 15:20:05 + with message-id and subject line Bug#916840: fixed in groovy 2.4.16-1 has caused the Debian Bug report #916840, regarding groovy: FTBFS with Java 11 due to polymorphic signature calls & SecurityManager changes 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.) -- 916840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:groovy Version: 2.4.15-3 Severity: serious User: debian-j...@lists.debian.org Usertags: default-java11 groovy fails to build with Java 11, there are two different errors. The first one: groovy-2.4.15/src/main/org/codehaus/groovy/vmplugin/v7/IndyInterface.java:236: error: polymorphic signature calls are not supported in -target 1.6 return call.invokeExact(arguments); ^ (use -target 1.7 or higher to enable polymorphic signature calls) and the second one: groovy-2.4.15/subprojects/groovy-console/src/main/groovy/groovy/ui/text/StructuredSyntaxResources.java:44: error: cannot find symbol mgr.checkSystemClipboardAccess(); ^ symbol: method checkSystemClipboardAccess() location: variable mgr of type SecurityManager --- End Message --- --- Begin Message --- Source: groovy Source-Version: 2.4.16-1 We believe that the bug you reported is fixed in the latest version of groovy, 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. Emmanuel Bourg (supplier of updated groovy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Dec 2018 14:42:03 +0100 Source: groovy Binary: groovy groovy-doc Architecture: source Version: 2.4.16-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: groovy - Agile dynamic language for the Java Virtual Machine groovy-doc - Agile dynamic language for the Java Virtual Machine (documentatio Closes: 879892 910098 916840 Changes: groovy (2.4.16-1) unstable; urgency=medium . * Team upload . [ Tiago Stürmer Daitx ] * Replace HTTP URLs with local files: (Closes: #910098) - debian/control: build depends on -doc packages so javadoc can properly link the apis. - debian/patches/10_fix_javadoc_links.patch: include javadoc apis locally; since openjdk 10 any invalid, unreacheable, or nonexistent doc link causes the build to fail. . [ tony mancill ] * Add groovyConsole desktop file. (Closes: #879892) Thank you to Dirk Heinrichs for the patch and reminder. . [ Emmanuel Bourg ] * New upstream release - Refreshed the patches - Updated the poms * Fixed the build failure with Java 11 (Closes: #916840) Checksums-Sha1: 93e246569c7801ff27d18f3ab4c44937e9932a24 2403 groovy_2.4.16-1.dsc 1bcbf80223ddd2d4188fd8377e9c40957e47d12a 3039780 groovy_2.4.16.orig.tar.xz dc07d2fea208631cf54ac9f5f2eb129e85044376 29044 groovy_2.4.16-1.debian.tar.xz 2fc3469824fa69d63512d7e6a805b72fc2e72338 14428 groovy_2.4.16-1_source.buildinfo Checksums-Sha256: 066e7d182ad313833638334bf607f0a790f410ec48f6877e7393714b58ab89dc 2403 groovy_2.4.16-1.dsc 0833e0bdc7222708eb1e4c19a197a66a452e2cfb4f1a4f951a5e80be380fef4f 3039780 groovy_2.4.16.orig.tar.xz 556c5b7b816fe80081f5be9ec675aa02109529d775de32f108f9bcfe9691dd8d 29044 groovy_2.4.16-1.debian.tar.xz 292884717484ff06a7d6e5f8b9237ea65a1e92f66382448bf04f5000855abfb4 14428 groovy_2.4.16-1_source.buildinfo Files: eaaf1801c6bf30a4e3d88cd1821cf547 2403 java optional groovy_2.4.16-1.dsc 187b77ff7bac94e75dbac0977a67478c 3039780 java optional groovy_2.4.16.orig.tar.xz 79d7ae4495becc70213d70a3c7fa15ff 29044 java optional groovy_2.4.16-1.debian.tar.xz 1a8f6babb0c955a9f65fb01bd9f32646 14428 java optional groovy_2.4.16-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwaW8gSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs4koP/RZ67UgR6Q5uvyrenyz6b4ATxhiOBbke
Processed: Re: erlang-mode: fails to install with xemacs21
Processing control commands: > notfixed -1 1:20.3.8.5+dfsg-1 Bug #909387 [erlang-mode] erlang-mode: fails to install with xemacs21 No longer marked as fixed in versions erlang/1:20.3.8.5+dfsg-1. > found -1 1:21.2+dfsg-1 Bug #909387 [erlang-mode] erlang-mode: fails to install with xemacs21 Marked as found in versions erlang/1:21.2+dfsg-1. -- 909387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909387: erlang-mode: fails to install with xemacs21
Followup-For: Bug #909387
Control: notfixed -1 1:20.3.8.5+dfsg-1
Control: found -1 1:21.2+dfsg-1
That wasn't working previously in sid, my test was just not running
properly and the package was skipped in sid ...
[...]
Selecting previously unselected package erlang-mode.
Preparing to unpack .../erlang-mode_1%3a21.2+dfsg-1_all.deb ...
Unpacking erlang-mode (1:21.2+dfsg-1) ...
Setting up erlang-mode (1:21.2+dfsg-1) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Loading site-start...
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Loading site-start...
[...]
Loading site-start...
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Loading site-start...
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Error while loading 00debian: Variable binding depth exceeds max-specpdl-size
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install erlang-mode for xemacs21
install/erlang: Handling install for emacsen flavor xemacs21
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-eunit.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/erlang/erlang-eunit.el:
!! error (("Unknown keyword" :safe))
>>Error occurred processing erlang-eunit.el:
Unknown keyword: :safe
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-skels-old.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-skels-old.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-skels.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-skels.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-start.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-start.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-test.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/erlang/erlang-test.el:
!! File error (("Cannot open load file" "ert"))
>>Error occurred processing erlang-test.el: Cannot open load file: ert
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/erlang/erlang.el:
** Third arg to defvar erlang-font-lock-keywords-1 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-2 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-3 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-4 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords is not a string:
erlang-font-lock-descr-string
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang_appwiz.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang_appwiz.elc
Done
ERROR: install script from erlang-mode package failed
dpkg: error processing package erlang-mode (--configure):
installed erlang-mode package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
erlang-mode
Andreas
erlang-mode=1:21.2+dfsg-1_xemacs21.log.gz
Description: application/gzip
Processed: Bug #916840 in groovy marked as pending
Processing control commands: > tag -1 pending Bug #916840 [src:groovy] groovy: FTBFS with Java 11 due to polymorphic signature calls & SecurityManager changes Added tag(s) pending. -- 916840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916840: Bug #916840 in groovy marked as pending
Control: tag -1 pending Hello, Bug #916840 in groovy 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/groovy/commit/b8d7ec119014a95450f9357efddc250e3888f030 Fixed the build failure with Java 11 (Closes: #916840) (this message was generated automatically) -- Greetings https://bugs.debian.org/916840
Bug#916855: glewlwyd: FTBFS: no dependency information found for /build/ulfius-build/libulfius.so.2.3
Source: glewlwyd Version: 1.4.6-3 Severity: serious Tags: ftbfs Hi, On a rebuild against libulfius2.5, your package failed to build: dh_shlibdeps -a -O--buildsystem=cmake -O--builddirectory=build dpkg-shlibdeps: error: no dependency information found for /<>/build/ulfius-build/libulfius.so.2.3 (used by debian/glewlwyd/usr/bin/glewlwyd) Hint: check if the library actually comes from a package. dh_shlibdeps: dpkg-shlibdeps -Tdebian/glewlwyd.substvars debian/glewlwyd/usr/bin/glewlwyd returned exit code 25 dh_shlibdeps: Aborting due to earlier error >From the build log it looks like glewlwyd is building its own (old) version of libulfius, rather than dynamically linking to the one from the Debian package. Full logs: https://buildd.debian.org/status/package.php?p=glewlwyd Cheers, Emilio
Bug#916342: marked as done (segyio FTBFS: test failure)
Your message dated Wed, 19 Dec 2018 14:47:16 +
with message-id
and subject line Bug#916342: fixed in segyio 1.8.1-1
has caused the Debian Bug report #916342,
regarding segyio FTBFS: test failure
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.)
--
916342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: segyio
Version: 1.7.1-2
Severity: serious
Tags: ftbfs
Some recent change in unstable makes segyio FTBFS:
https://tests.reproducible-builds.org/debian/history/segyio.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/segyio.html
...
dh_auto_test --buildsystem=pybuild -- --test-args=test/*
I: pybuild pybuild:269: cp -r /build/1st/segyio-1.7.1/python/test
/build/1st/segyio-1.7.1/test-data
/build/1st/segyio-1.7.1/.pybuild/cpython3_3.6_segyio/build
I: pybuild base:217: cd
/build/1st/segyio-1.7.1/.pybuild/cpython3_3.6_segyio/build; python3.6 -m pytest
test/*
= test session starts ==
platform linux -- Python 3.6.8rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/segyio-1.7.1, inifile: setup.cfg
= no tests ran in 0.08 seconds =
ERROR: not found:
/build/1st/segyio-1.7.1/.pybuild/cpython3_3.6_segyio/build/test/segy.py
(no name
'/build/1st/segyio-1.7.1/.pybuild/cpython3_3.6_segyio/build/test/segy.py' in
any of ())
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=4: cd
/build/1st/segyio-1.7.1/.pybuild/cpython3_3.6_segyio/build; python3.6 -m pytest
test/*
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.7"
--test-args=test/\* returned exit code 13
make[1]: *** [debian/rules:41: override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Source: segyio
Source-Version: 1.8.1-1
We believe that the bug you reported is fixed in the latest version of
segyio, 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.
Jørgen Kvalsvik (supplier of updated segyio package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 19 Dec 2018 13:28:54 +0100
Source: segyio
Binary: libsegyio1 libsegyio-dev segyio-bin python3-segyio
Architecture: source
Version: 1.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Jørgen Kvalsvik
Description:
libsegyio-dev - SEG-Y read/write library for seismic processing (development)
libsegyio1 - SEG-Y read/write library for seismic processing (runtime)
python3-segyio - SEG-Y read/write library for seismic processing (python3
bindings
segyio-bin - SEG-Y read/write library for seismic processing (shell utilities)
Closes: 916342
Changes:
segyio (1.8.1-1) unstable; urgency=medium
.
* New upstream release
* Ignore python_files from setup.cfg (Closes: #916342)
Checksums-Sha1:
2910ab6e84db42e9de3026d1e61c8477bfbf7570 2267 segyio_1.8.1-1.dsc
04b517ffec03da7871249f53f03c189e8643034c 436447 segyio_1.8.1.orig.tar.gz
f19ed00720acf206d2df141977914a99169e444e 4580 segyio_1.8.1-1.debian.tar.xz
d27dfdb3a71bc4812025197433edcb27de25ee76 9099 segyio_1.8.1-1_amd64.buildinfo
Checksums-Sha256:
848afc103cef5d99599465a7e14995eb412d7220430fea00763c55f1bba8bd83 2267
segyio_1.8.1-1.dsc
42f1cf864ce66244b17b526302e3c36f42ef88aba1df29b7df0983606250b7c9 436447
segyio_1.8.1.orig.tar.gz
f1bb522aabce8e172f73cddcce1ffa6a6ffb1ee8283aac16e978eda6f335eb07 4580
segyio_1.8.1-1.debian.tar.xz
969404b0823f1b716d0ba34445e4a90d884289b8f868843e93f092f62043ee24 9099
segyio_1.8.1-1_amd64.buildinfo
Files:
6eed3f624347f744fbe6c9593be4 2267 science optional segyio_1.8.1-1.dsc
42a572c7f256856bb5b290e390dc7f3b 436447 science optional
segyio_1.8.1.orig.tar.gz
ad6dd4cda39e0871dd1b7b617782d13b 4580 science optional
segyio_1.8.1-1.debian.tar.xz
9e7cde8bbd1d0e275676795b69f126be 9099 science optional
segyio_1.8.1-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlwaTO8ACgkQLOzpNQ7O
Bug#916683: libgnutls30: breaks msmtp 1.6.7-1
The issue is caused by a bug in msmtp which is already fixed in 1.8.1 https://gitlab.marlam.de/marlam/msmtp/issues/21 After I removed the patch in debian/patches that fixes only some typos in the manpage but does not apply any longer with 1.8.1 sources the package builds just fine. So hopefully the maintainer finds some time to package the new release soon. Until then just grab the sources from the repo and fetch the new upstream sources with uscan, remove the patch and build it locally. Best regards Fritz -- Fritz Reichwald Linux Consultant Tel: +49 160 8452444 Mail: reichw...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 signature.asc Description: PGP signature
Bug#916846: [libreoffice-ogltrans] Blank screen with OpenGL transitions
Package: libreoffice-ogltrans Version: 1:6.1.3-2 Severity: grave Justification: renders package unusable When I try to use OpenGL transitions in LibreOffice Impress, I get a bank screen for several seconds instead of a transition. This issue seems to be Debian-specific; I was trying the upstream version and it works fine. Hardware acceleration is enabled in configuration; renderer I use is Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Upstream bug report: https://bugs.documentfoundation.org/show_bug.cgi?id=115716 --- System information. --- Architecture: Kernel: Linux 4.18.0-3-amd64 Debian Release: buster/sid 990 testing ftp.by.debian.org 500 unstableftp.by.debian.org --- Package information. --- Depends(Version) | Installed -+-= libreoffice-common | 1:6.1.3-2 libreoffice-core (= 1:6.1.3-2) | 1:6.1.3-2 libreoffice-impress | 1:6.1.3-2 libc6 (>= 2.14) | libepoxy0 (>= 1.0) | libgcc1 (>= 1:3.0) | libstdc++6(>= 5) | uno-libs3 (>= 4.4.0~alpha) | ure | libreoffice-core (= 1:6.1.3-2) | 1:6.1.3-2 libreoffice-draw (= 1:6.1.3-2) | libc6 (>= 2.14) | libepoxy0 (>= 1.0) | libetonyek-0.1-1 | libgcc1 (>= 1:3.0) | libmwaw-0.3-3| libodfgen-0.1-1 | librevenge-0.0-0 | libstaroffice-0.0-0 | libstdc++6(>= 5) | libxml2 (>= 2.6.27) | uno-libs3 (>= 5.3.0~alpha) | ure | zlib1g (>= 1:1.1.4) | Recommends (Version) | Installed -+-=== libreoffice-avmedia-backend-gstreamer| 1:6.1.3-2 OR libreoffice-avmedia-backend-vlc | Suggests (Version) | Installed ===-+-=== bluez | 5.50-1 -- Alexander Kernozhitsky
Processed: affects 915469
Processing commands for cont...@bugs.debian.org: > affects 915469 src:gwave Bug #915469 [g-wrap] gwave FTBFS: error: found development files for Guile 2.0, but /usr/bin/guile has effective version 2.2 Added indication that 915469 affects src:gwave > thanks Stopping processing here. Please contact me if you need assistance. -- 915469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916840: groovy: FTBFS with Java 11 due to polymorphic signature calls & SecurityManager changes
Package: src:groovy Version: 2.4.15-3 Severity: serious User: debian-j...@lists.debian.org Usertags: default-java11 groovy fails to build with Java 11, there are two different errors. The first one: groovy-2.4.15/src/main/org/codehaus/groovy/vmplugin/v7/IndyInterface.java:236: error: polymorphic signature calls are not supported in -target 1.6 return call.invokeExact(arguments); ^ (use -target 1.7 or higher to enable polymorphic signature calls) and the second one: groovy-2.4.15/subprojects/groovy-console/src/main/groovy/groovy/ui/text/StructuredSyntaxResources.java:44: error: cannot find symbol mgr.checkSystemClipboardAccess(); ^ symbol: method checkSystemClipboardAccess() location: variable mgr of type SecurityManager
Bug#916345: libmodbus: FTBFS on mips, s390x: test failure
Hi, SZ Lin (林上智) 於 2018年12月18日 週二 下午2:18寫道： > > Hi, > > Ivo De Decker 於 2018年12月13日 週四 下午8:03寫道： > > > > package: src:libmodbus > > version: 3.1.4-1 > > severity: serious > > tags: ftbfs > > > > Hi, > > > > The latest version of libmodbus in unstable fails on mips, s390x: > > > > https://buildd.debian.org/status/package.php?p=libmodbus > > > > The failure happens in the testsuite. > > > > Based on the failing architectures, it might be an endianess issue. > > I've reproduced this issue with MIPS architecture. > > === > TEST FLOATS > 1/4 Set/get float ABCD: > Line 289: assertion error for 'equal_dword(tab_rp_registers, > UT_IREAL_ABCD)': FAILED Set float ABCD > ** > === > > According to above information, it might be a float endianess issue > and there is a potential fix for it [1]. > > I will continually squeeze my time to track this issue. > > Any feedback is welcome. > > [1] https://github.com/stephane/libmodbus/issues/358 > > SZ I've patched float endianness issue [1] and built successfully on mips, s390x, amd64 architecture. [1] https://salsa.debian.org/debian/libmodbus/blob/debian/master/debian/patches/Fix-float-endianness-issue-on-big-endian-arch.patch The new version of libmodbus will be uploaded if you don't have any concerns. Thanks. SZ > > > > > > Also, please note this error: > > > > ./unit-tests.sh: 17: ./unit-tests.sh: killall: not found > > > > This doesn't happen for the builds that succeed. I guess the killall is done > > when the tests fail. This means a dependency on psmisc is missing. > > Now fixed, thanks, > > SZ > > > > Thanks, > > > > Ivo
Bug#910786: opensc: No longer recognizes Yubikey NEO after upgrade to 0.16.0-3+deb9u1
* Gianfranco Costamagna: > I see this code changed a lot in 0.19... is this still a problem? It is still a problem with opensc/0.16.0-3+deb9u1 as currently available from stretch. Backporting opensc/0.19.0-1 for stretch is trivial and has resolved the problem for me and my colleagues. I suggest fixing the problem in stretch via an update to 0.19 as suggested by Adam D. Barratt in #913674. Cheers, -Hilko
Bug#909909: marked as done (groovy FTBFS)
Your message dated Wed, 19 Dec 2018 12:25:11 +0100 with message-id <32d757da-797a-96fa-3a25-f3125fa88...@apache.org> and subject line Re: Bug#909909: groovy FTBFS has caused the Debian Bug report #909909, regarding groovy FTBFS 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.) -- 909909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: groovy Version: 2.4.15-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/groovy.html ... :groovy:compileGroovy FAILED :compileGroovy (Thread[Task worker for ':groovy',5,main]) completed. Took 15.222 secs. :jarAllWithIndy FAILED :jarAllWithIndy (Thread[Task worker for ':' Thread 12,5,main]) completed. Took 31.776 secs. FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':groovy:compileGroovy'. > org/codehaus/groovy/control/Phases * Try: Run with --debug option to get more log output. Run with --scan to get full insights. * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':groovy:compileGroovy'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581) at
Bug#916766: marked as done (libucto3: missing Breaks+Replaces: libucto2)
Your message dated Wed, 19 Dec 2018 11:21:02 + with message-id and subject line Bug#916766: fixed in ucto 0.14-2 has caused the Debian Bug report #916766, regarding libucto3: missing Breaks+Replaces: libucto2 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.) -- 916766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libucto3 Version: 0.14-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libucto3:amd64. Preparing to unpack .../libucto3_0.14-1_amd64.deb ... Unpacking libucto3:amd64 (0.14-1) ... dpkg: error processing archive /var/cache/apt/archives/libucto3_0.14-1_amd64.deb (--unpack): trying to overwrite '/usr/share/ucto/textcat.cfg', which is also in package libucto2:amd64 0.9.6-1+b1 Errors were encountered while processing: /var/cache/apt/archives/libucto3_0.14-1_amd64.deb cheers, Andreas libucto2=0.9.6-1+b1_libucto3=0.14-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ucto Source-Version: 0.14-2 We believe that the bug you reported is fixed in the latest version of ucto, 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. Maarten van Gompel (supplier of updated ucto package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Dec 2018 12:01:32 +0100 Source: ucto Binary: ucto libucto-dev libucto3 Architecture: source Version: 0.14-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Maarten van Gompel Description: libucto-dev - Unicode Tokenizer - development libucto3 - Unicode Tokenizer - runtime ucto - Unicode Tokenizer Closes: 916766 Changes: ucto (0.14-2) unstable; urgency=medium . * Re-added Breaks+Replace libucto3 <- libucto2 (Closes: #916766). Thanks to Andreas Beckmann. Checksums-Sha1: 56d7b5766bab5bdb3a09772fe835d0398aaeb1fa 1802 ucto_0.14-2.dsc 2d6f1960f9f0f6c16053e5b963428198a1707727 5788 ucto_0.14-2.debian.tar.xz 4d357c6eb986eee4eb5a288c1f20e392cd6c9ac0 5385 ucto_0.14-2_source.buildinfo Checksums-Sha256: 456c7417ce11feda6a1ed8805a00d0d9c8336794ac9f9728bb958ae9046f668c 1802 ucto_0.14-2.dsc 79ec9abfba013097e3a4b22befb658f076d365393eb6e40e4b7a24725d4649eb 5788 ucto_0.14-2.debian.tar.xz a12754ffd836b89b41bec84408a50c7efc026ed54f57a0021fabea2ebf820220 5385 ucto_0.14-2_source.buildinfo Files: 98cc810b44f1e59c2b3d90b31d4df34b 1802 science optional ucto_0.14-2.dsc 180ef00f940a8af68fbc124dc7ea9a80 5788 science optional ucto_0.14-2.debian.tar.xz 8176b451a8fe847ea7ee8d91fdd753ea 5385 science optional ucto_0.14-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEisYkiB7yrDDA5o4sOf4RIBoxVVwFAlwZVb4ACgkQOf4RIBox VVybFQf+IdPiUEfVNe5UF3tqHNEMWpCeOxbr7ZMgesUDCvuSQqMix7Q+vAhjQibA JIz93amr58kR4PuhP/2QGa83sVJsyCE0IeQLtxsVjaI9ND1oJEEGgRUxtd8daIpl PCompf6mCvR/BrzfAyBHhvTqsKTdTbp16e+gtVtEByOtRSNUcuVvs6IbJDZYRCMk AOBBzpI/duB/mpdV6iDDTOHQkT8/4o3dluEzlvolr/rsV1OtfCd5pTLVXvja127l VksBeTWiTcL50Io8Q5Hm7ujtcPmlYl/YojfoeGXvGwMsrS9FoZUnbwzcpcvmNjtx /fcwhYyFdNwmMZo6kqOg3JCktPLOCQ== =+qwG -END PGP SIGNATURE End Message ---
Processed (with 1 error): imagemagick: Silent ABI break in 6.9.10-11 on i386
Processing control commands: > forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31 Unknown command or malformed arguments to command. > tags -1 upstream fixed-upstream Bug #916839 [imagemagick] imagemagick: Silent ABI break in 6.9.10-11 on i386 Added tag(s) fixed-upstream and upstream. > affects -1 ruby-rmagick Bug #916839 [imagemagick] imagemagick: Silent ABI break in 6.9.10-11 on i386 Added indication that 916839 affects ruby-rmagick -- 916839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386
Package: imagemagick Version: 8:6.9.10.14+dfsg-1 Severity: grave Control: forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31 Control: tags -1 upstream fixed-upstream Control: affects -1 ruby-rmagick Hi, The ABI broke in 6.9.10-11 due to changing MagickDoubleType to double from long double. This breaks ruby-rmagick and possibly other reverse dependencies, thus after fixing imagemagick please check if some reverse dependencies need to be rebuilt. The fix will be available in the .18 upstream release. Cheers, Balint -- Balint Reczey Ubuntu & Debian Developer
Bug#910786: opensc: No longer recognizes Yubikey NEO after upgrade to 0.16.0-3+deb9u1
On Thu, 11 Oct 2018 23:32:49 +0200 Hilko Bengen wrote:
> Hi,
>
> after some digging and testing, I come to the conclusion that the the
> immediate cause for the breakage I reported is the change made to the
> piv_general_io() function (src/libopensc/card-piv.c, expanded for
> context): Because rbuflen is set to zero, sc_asn1_read_tag will never
> read/parse an ASN.1 tag.
>
> Reverting this single change seems to fix my problems, however this
> leaves the clear possibility for overflowing receive buffers that are
> passed into the function, this has so far only worked by accident...
>
> Cheers,
> -Hilko
>
> @@ -525,15 +525,16 @@ static int piv_general_io(sc_card_t *card, int ins, int
> p1, int p2,
> rbuflen = 0; /* in case rseplen < 3 i.e. not parseable */
> if ( recvbuflen && recvbuf && apdu.resplen > 3) {
> *recvbuflen = 0;
> /* we should have all the tag data, so we have to tell
> sc_asn1_find_tag
>* the buffer is bigger, so it will not produce "ASN1.tag too
> long!" */
>
> body = rbuf;
> - if (sc_asn1_read_tag(, 0x, _out, _out,
> ) != SC_SUCCESS) {
> + if (sc_asn1_read_tag(, rbuflen, _out, _out,
> ) != SC_SUCCESS
> + || body == NULL) {
> /* only early beta cards had this problem */
> sc_debug(card->ctx, SC_LOG_DEBUG_NORMAL, "*
> received buffer tag MISSING ");
> body = rbuf;
> /* some readers/cards might return 6c 00 */
> if (apdu.sw1 == 0x61 || apdu.sw2 == 0x6c )
> bodylen = 12000;
> else
>
I see this code changed a lot in 0.19... is this still a problem?
G.
>
Bug#912184: marked as done (python-testfixtures FTBFS with python 3.7 as supported version)
Your message dated Wed, 19 Dec 2018 10:52:15 +
with message-id
and subject line Bug#912184: fixed in python-testfixtures 4.14.3-2
has caused the Debian Bug report #912184,
regarding python-testfixtures FTBFS with python 3.7 as supported version
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.)
--
912184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testfixtures
Version: 4.14.3-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-testfixtures.html
...
I: pybuild base:217: python3.7 /usr/bin/zope-testrunner
--path=/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build
testfixtures
Running zope.testrunner.layer.UnitTests tests:
Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
Failure in test test_exception_diff
(testfixtures.tests.test_compare.TestCompare)
Traceback (most recent call last):
File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.7/unittest/case.py", line 615, in run
testMethod()
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 170, in test_exception_diff
"ValueError('some message',) != ValueError('some other message',)"
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 51, in check_raises
compare(actual, expected=message, show_whitespace=True)
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/comparison.py",
line 485, in compare
raise AssertionError(message)
AssertionError:
"ValueError('some message',) != ValueError('some other message',)" (expected)
!=
"ValueError('some message') != ValueError('some other message')" (actual)
Failure in test test_exception_diff_c_wrapper
(testfixtures.tests.test_compare.TestCompare)
Traceback (most recent call last):
File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.7/unittest/case.py", line 615, in run
testMethod()
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 184, in test_exception_diff_c_wrapper
).format(exception_module))
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 51, in check_raises
compare(actual, expected=message, show_whitespace=True)
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/comparison.py",
line 485, in compare
raise AssertionError(message)
AssertionError:
--- expected
+++ actual
@@ -1,4 +1,4 @@
'\n'
' \n'
" args:('some message',) != ('some other message',)\n"
-" != ValueError('some other message',)"
+" != ValueError('some other message')"
Failure in test test_exception_different_object
(testfixtures.tests.test_compare.TestCompare)
Traceback (most recent call last):
File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.7/unittest/case.py", line 615, in run
testMethod()
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 157, in test_exception_different_object
"ValueError('some message',) != ValueError('some message',)"
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/tests/test_compare.py",
line 51, in check_raises
compare(actual, expected=message, show_whitespace=True)
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/testfixtures/comparison.py",
line 485, in compare
raise AssertionError(message)
AssertionError:
"ValueError('some message',) != ValueError('some message',)" (expected)
!=
"ValueError('some message') != ValueError('some message')" (actual)
Failure in test
/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/docs/warnings.txt
--
File
"/build/1st/python-testfixtures-4.14.3/.pybuild/cpython3_3.7_testfixtures/build/docs/warnings.txt",
line 26, in warnings.txt
Failed example:
with ShouldWarn(UserWarning('you should fix that')):
warn("sorry dave, I can't let you do that")
Differences (ndiff with
Bug#893409: pixelmed FTBFS with openjdk-9
Hi,
On Wed, Dec 19, 2018 at 10:39:55AM +0100, Olivier Sallou wrote:
> > The missing class is in libjaxb-api-java. Just make sure it's on the
> > CLASSPATH.
>
> yeap, an other issue at java migration to openjdk 10/11
>
> Adding this lib to deps should fix the pb
Thanks for the quick help. I tried:
diff --git a/debian/control b/debian/control
index e0548ee..3f8b86c 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,8 @@ Build-Depends-Indep: default-jdk,
libjmdns-java,
libvecmath-java,
libpixelmed-codec-java,
- libjsonp-java
+ libjsonp-java,
+ libjaxb-api-java
Standards-Version: 4.2.1
Vcs-Browser: https://salsa.debian.org/med-team/pixelmed
Vcs-Git: https://salsa.debian.org/med-team/pixelmed.git
diff --git a/debian/patches/fixdoc.patch b/debian/patches/fixdoc.patch
index 752b78c..1737f5f 100644
--- a/debian/patches/fixdoc.patch
+++ b/debian/patches/fixdoc.patch
@@ -11,7 +11,7 @@ Index: pixelmed-20140326/Makefile
rm -rf docs/javadoc
javadoc \
- -classpath
.:lib/additional/excalibur-bzip2-1.0.jar:lib/additional/hsqldb.jar:lib/additional/vecmath1.2-1.14.jar:lib/additional/commons-codec-1.3.jar:lib/additional/commons-net2.jar:lib/additional/jmdns.jar:lib/additional/jpedalSTD.jar:lib/junit/junit-4.8.1.jar
\
-+ -classpath
.:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar
\
++ -classpath
.:/usr/share/java/excalibur-bzip2-1.0.jar:/usr/share/java/hsqldb.jar:/usr/share/java/vecmath.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-net2.jar:/usr/share/java/jmdns.jar:/usr/share/java/jpedalSTD.jar:/usr/share/java/junit4.jar:/usr/share/java/jaxb-api.jar
\
-link http://download.oracle.com/javase/1.5.0/docs/api/ \
-link http://jpedal.org/javadoc/ \
-link http://www.hsqldb.org/doc/src/ \
diff --git a/debian/patches/jaxb-api.patch b/debian/patches/jaxb-api.patch
new file mode 100644
index 000..85760dd
--- /dev/null
+++ b/debian/patches/jaxb-api.patch
@@ -0,0 +1,16 @@
+Description: For OpenJDK 11 jaxb needs to be in classpath
+Bug-Debian: https://bugs.debian.org/893409
+Author: Andreas Tille
+Last-Update: Wed, 19 Dec 2018 08:53:43 +0100
+
+--- a/Makefile.common.mk
b/Makefile.common.mk
+@@ -65,7 +65,7 @@ JAVACOPTIONS = -O ${JAVACTARGETOPTIONS}
+
+ .java.class:
+ export JAVAVERSIONTARGETJARFILE=${JAVA_HOME}/jre/lib/rt.jar; javac
${JAVACOPTIONS} \
+- -classpath
${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}
\
++ -classpath
${PATHTOROOT}:${DICOMADDITIONALJARS}:${VIEWERADDITIONALJARS}:${FTPADDITIONALJARS}:${JUNITJAR}:/usr/share/java/jaxb-api.jar
\
+ -sourcepath ${PATHTOROOT} $<
+
+ .png.ico:
diff --git a/debian/patches/series b/debian/patches/series
index 10286d4..6abfc45 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -16,3 +16,4 @@ set_java_home.patch
imageio.patch
no_Xdiags_verbose.patch
do_not_set_bootclasspath.patch
+jaxb-api.patch
I've pushed these changes but unfortunately it does not help. :-(
Any further hints?
Kind regards
Andreas.
--
http://fam-tille.de
Processed: Segfault in test suite of new upstream version (Was: python-mne FTBFS with python-matplotlib 2.2.2-1)
Processing control commands: > tags -1 help Bug #896025 [src:python-mne] python-mne FTBFS with python-matplotlib 2.2.2-1 Added tag(s) help. > tags -1 upstream Bug #896025 [src:python-mne] python-mne FTBFS with python-matplotlib 2.2.2-1 Added tag(s) upstream. > forwarded -1 https://github.com/mne-tools/mne-python/issues/5806 Bug #896025 [src:python-mne] python-mne FTBFS with python-matplotlib 2.2.2-1 Set Bug forwarded-to-address to 'https://github.com/mne-tools/mne-python/issues/5806'. -- 896025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896025: Segfault in test suite of new upstream version (Was: python-mne FTBFS with python-matplotlib 2.2.2-1)
Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 https://github.com/mne-tools/mne-python/issues/5806 Hi, it seems the matplotlib issue reported here is solved in the last upstream version which I commited to packaging Git[1]. Unfortunately there is another issue which I reported upstream[2]: ... make[1]: Entering directory '/build/python-mne-0.17+dfsg' mkdir -p build HOME=/build/python-mne-0.17+dfsg/build \ MNE_DONTWRITE_HOME=true MNE_SKIP_SAMPLE_DATASET_TESTS=true MNE_FORCE_SERIAL=true MNE_SKIP_NETWORK_TESTS=1 \ xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" \ py.test -s -v mne = test session starts == platform linux2 -- Python 2.7.15+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- /usr/bin/python2 cachedir: .pytest_cache rootdir: /build/python-mne-0.17+dfsg, inifile: setup.cfg plugins: cov-2.6.0 collecting ... Using default location ~/mne_data for testing... Creating ~/mne_data Using default location ~/mne_data for testing... Using default location ~/mne_data for testing... ... Using default location ~/mne_data for testing... Using default location ~/mne_data for testing... Segmentation fault make[1]: *** [debian/rules:26: override_dh_auto_test] Error 139 make[1]: Leaving directory '/build/python-mne-0.17+dfsg' I wonder whether one of the Uploaders (in CC) will be able to fix this since I feel absolutely incompetent to solve this. Kind regards Andreas. [1] https://salsa.debian.org/med-team/python-mne [2] https://github.com/mne-tools/mne-python/issues/5806 -- http://fam-tille.de
Processed: affects 916548
Processing commands for cont...@bugs.debian.org: > affects 916548 pyzo Bug #916548 [python3.7] python3.7: Version constraint in pyzo breaks is too strict Added indication that 916548 affects pyzo > thanks Stopping processing here. Please contact me if you need assistance. -- 916548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916835: gemma ftbfs on arm64 and mips64el where it built before
Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 https://github.com/genetics-statistics/GEMMA/issues/189
Processed: Re: Bug#916835: gemma ftbfs on arm64 and mips64el where it built before
Processing control commands: > tags -1 help Bug #916835 [src:gemma] gemma ftbfs on arm64 and mips64el where it built before Added tag(s) help. > tags -1 upstream Bug #916835 [src:gemma] gemma ftbfs on arm64 and mips64el where it built before Added tag(s) upstream. > forwarded -1 https://github.com/genetics-statistics/GEMMA/issues/189 Bug #916835 [src:gemma] gemma ftbfs on arm64 and mips64el where it built before Set Bug forwarded-to-address to 'https://github.com/genetics-statistics/GEMMA/issues/189'. -- 916835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893409: pixelmed FTBFS with openjdk-9
On 12/19/18 10:03 AM, Markus Koschany wrote: > Hi, > > Am 19.12.18 um 09:58 schrieb Andreas Tille: > [...] >> Any hint how to fix this? > The missing class is in libjaxb-api-java. Just make sure it's on the > CLASSPATH. yeap, an other issue at java migration to openjdk 10/11 Adding this lib to deps should fix the pb > Regards, > > Markus > > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- Olivier Sallou Univ Rennes, Inria, CNRS, IRISA Irisa, Campus de Beaulieu F-35042 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 signature.asc Description: OpenPGP digital signature
Bug#916835: gemma ftbfs on arm64 and mips64el where it built before
Package: src:gemma Version: 0.98.1+dfsg-1 Severity: serious Tags: sid buster gemma ftbfs on arm64 and mips64el where it built before (test failures) arm64: Ran 12 tests. FAILED (failures=13) tail -n 1 dev_test.log | grep -q 'OK' make[2]: *** [Makefile:231: fast-check] Error 1 mips64el: Ran 12 tests. FAILED (failures=2) tail -n 1 test.log | grep -q 'OK' test.log make[2]: *** [Makefile:236: slow-check] Error 1
