Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable
Package: libglvnd0-nvidia Version: 375.82-5 Severity: critical Dear Maintainer, after updating some packages this morning, X11 did not come up any more and the system was completely unusable. Apparently gdm was restarting continuously, making it impossible to enter anything in a terminal window. I needed to boot in recovery mode to get access again. The syslog contains /usr/lib/gdm3/gdm-x-session[2703]: (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current and I get the same undefined symbol error when I try startx. After installing libglvnd0 (and purging libglvnd0-nvidia) everything is fine again. In contrast to what is reported in https://lists.debian.org/debian-kde/2017/10/msg00028.html, the problem appears again, when I reinstall libglvnd0-nvidia. Bye, Hendrik -- Package-specific info: uname -a: Linux cert 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 GNU/Linux /proc/version: Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01) lspci 'VGA compatible controller [0300]': 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5056] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Oct 17 21:58 /dev/dri/card0 crw-rw+ 1 root video 226, 128 Oct 17 21:58 /dev/dri/renderD128 /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Oct 17 21:58 pci-:00:02.0-card -> ../card0 lrwxrwxrwx 1 root root 13 Oct 17 21:58 pci-:00:02.0-render -> ../renderD128 video:x:44:tews OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libEGL.so.1 -> libEGL.so.1.0.0 -rw-r--r-- 1 root root 76344 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libEGL.so.1.0.0 lrwxrwxrwx 1 root root 14 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> libGL.so.1.0.0 -rw-r--r-- 1 root root 567624 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0 lrwxrwxrwx 1 root root 18 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.0.0 -rw-r--r-- 1 root root 55616 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0 -rw-r--r-- 1 root root 29 Jul 7 07:31 /usr/lib/xorg/modules/extensions/libglx.so -rw-r--r-- 1 root root 5883 Oct 17 09:07 /var/log/Xorg.0.log /etc/modprobe.d: total 24 drwxr-xr-x 2 root root 4096 Sep 18 13:14 . drwxr-xr-x 162 root root 12288 Oct 17 21:55 .. -rw-r--r-- 1 root root 154 Nov 30 2016 amd64-microcode-blacklist.conf -rw-r--r-- 1 root root 154 Nov 9 2016 intel-microcode-blacklist.conf /etc/modules-load.d: -rw-r--r-- 1 root root 195 Mar 1 2017 /etc/modules /etc/modules-load.d/: total 20 drwxr-xr-x 2 root root 4096 Oct 17 08:42 . drwxr-xr-x 162 root root 12288 Oct 17 21:55 .. -rw-r--r-- 1 root root 119 Jan 19 2017 cups-filters.conf lrwxrwxrwx 1 root root10 Oct 11 00:46 modules.conf -> ../modules Files from nvidia-installer: Config and logfiles: << /home/tews/.local/share/xorg/Xorg.0.log >> [32.985] X.Org X Server 1.19.3 Release Date: 2017-03-15 [32.991] X Protocol Version 11, Revision 0 [32.992] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian [32.994] Current Operating System: Linux cert 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 [32.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-1-amd64 root=/dev/mapper/cert--vg-root1 ro single [32.998] Build Date: 07 July 2017 06:22:09AM [33.000] xorg-server 2:1.19.3-2 (https://www.debian.org/support) [33.001] Current version of pixman: 0.34.0 [33.005]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [33.005] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [33.012] (==) Log file: "/home/tews/.local/share/xorg/Xorg.0.log", Time: Tue Oct 17 21:58:39 2017 [33.019] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [33.024] (==) No Layout section. Using the first Screen section. [33.024] (==) No screen section available. Using defaults. [33.024] (**) |-->Screen "Default Screen Section" (0) [33.024] (**) | |-->Monitor "" [33.024] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [33.024] (==) Automatically adding devices [33.024] (==) Automatically enabling
Bug#877322: git-buildpackage autoremoval
Hi,
On Tue, Oct 17, 2017 at 10:27:03PM +0100, Ian Jackson wrote:
> Guido Günther writes ("Re: Bug#877322: git-buildpackage autoremoval"):
> > On Tue, Oct 17, 2017 at 02:57:33PM +0100, Ian Jackson wrote:
> > > This bug means that the autoremoval robot wants to remove
> > > git-buildpackage. I'm getting mails about it planning to remove dgit,
> > > to clear the way.
> > >
> > > Do you intend to upload the docs change to sid soon ?
> >
> > Yes, before the autoremoval for sure. Sorry for being a pain here but I
> > wanted to give gbp as much exposure as possible in experimental.
>
> OK, fine. Thanks for the reassurance. If the deadline gets closer I
> may ping you again :-).
Sure. I have 1 more bug to go that affects 0.9.x but not 0.8.x that I
want to get done before moving to sid.
Cheers,
-- Guido
Bug#878935: Unsatisfiable dependencies on !amd64
Thanks for reporting this bug.
On Tue, 2017-10-17 at 21:23 +0200, Alexander Kurtz wrote:
> Package: libbpfcc
> Version: 0.3.0-3
> Severity: serious
> Justification: Makes the package uninstallable on most architectures
>
> Hi!
>
> As [0] shows, libbpfcc has unsatisfiable dependencies on everything
> but
> amd64. This is because [1] is inherently wrong, "linux-headers-amd64"
> is of course only available on amd64, the other architectures have
> their own meta-packages [2]. Unfortunately there is (AFAIK) no good
> way
> to properly solve the "this package needs the current kernel headers
> installed" problem in Debian because
>
>1. There are no (real or virtual) "linux-{image,headers}-
> generic" packages (like in Ubuntu [3,4]) which have the same
> name on
> all architectures.
>2. Even if there were such packages, there's no guarantee that
> "linux-
> headers-generic" would point to the headers matching the
> *currently
> running* kernel (which is what libbcc needs). In fact, with
> partial
> upgrades, migrations from unstable to testing, upgraded-but-
> not-yet-
> rebooted machines, etc., it is quite likely that libbpfcc will
> be
> broken even if all its dependencies are fulfilled.
>
> I therefore ask you to
>
>1. Revert [1].
>2. Reopen [5] and put a note regarding the requirements of the
> kernel
> headers in README.Debian and/or the package description.
>3. Talk to the Debian Linux maintainers to find a proper solution
> to
> this problem. It's probably not going to be easy, but these
> kinds of
> problems really deserve to be fixed properly.
>
Yes. My bad. I completely missed about the dependency's limitation
across architectures. I'll fix it soon.
README.Debian is the wise way to deal with it. There were similar
situation with systemtap too.
> Yes, this sucks. I have run into #877925 myself and also thought that
> this should be simply solvable with a dependency. Oh, well, at least
> you may take comfort in the fact that others [6] have also run into
> this problem... ;-)
>
> Best regards
>
> Alexander Kurtz
>
> [0] https://tracker.debian.org/pkg/bpfcc
> [1] https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=
> f73049e48fd98dd01d4475f88f6b490e6a1b34bb
> [2] https://packages.debian.org/source/sid/linux
> [3] https://packages.ubuntu.com/artful/linux-image-generic
> [4] https://packages.ubuntu.com/artful/linux-headers-generic
> [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925
> [6] https://anonscm.debian.org/git/pkg-dkms/dkms.git/tree/debian/cont
> rol#n24
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
Bug#878966: nagios-plugins-contrib FTBFS with libvarnishapi-dev 5.2.0-1
Source: nagios-plugins-contrib Version: 21.20170222 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nagios-plugins-contrib.html ... check_varnish.c: In function 'check_stats_cb': check_varnish.c:193:33: error: 'const struct VSC_point' has no member named 'section' assert(sizeof(tmp) > (strlen(pt->section->fantom->type) + 1 + ^ check_varnish.c:194:19: error: 'const struct VSC_point' has no member named 'section' strlen(pt->section->fantom->ident) + 1 + ^ check_varnish.c:195:21: error: 'const struct VSC_point' has no member named 'desc'; did you mean 'sdesc'? strlen(pt->desc->name) + 1)); ^ ...
Bug#878402: [debian-mysql] Bug#878402: Security fixes from the October 2017 CPU
CVE List for 5.5: CVE-2017-10268 CVE-2017-10378 CVE-2017-10379 CVE-2017-10384 -- Lars On 13. okt. 2017 12:34, Norvald H. Ryeng wrote: Source: mysql-5.5 Version: 5.5.57-0+deb8u1 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for October 2017 will be released on Tuesday, October 17. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.5.58. The CVE numbers will be available when the CPU is released. Regards, Norvald H. Ryeng [1] http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.alioth.debian.org_cgi-2Dbin_mailman_listinfo_pkg-2Dmysql-2Dmaint&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=HPjEzLhETPj8fl9HCxxISaaV3f5tXDpGXDR3R2IELxg&m=dEyRpHvFwIr1RTEceqC6iy_yrzTaCF3pVSkZ3JFfOe4&s=0PVa9j2CKG1CAypoPA9B0-RLcMLbS5ifPg3jULC2EMw&e=
Bug#878744: close request :(
Sorry...It may not the bug of libinput, i've downgrade my libinput to the version 1.8.2-1, but the bug still exists... Probably the problem has caughted by KDE, so just close this bug tracking for sure ...
Processed: found 878402 in 5.5.42-1
Processing commands for cont...@bugs.debian.org: > found 878402 5.5.42-1 Bug #878402 [src:mysql-5.5] Security fixes from the October 2017 CPU Marked as found in versions mysql-5.5/5.5.42-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 878402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878948:
I can also confirm encountering this bug on testing. Downgrading the above-mentioned packages works for me too. Thanks!
Bug#878899: marked as done (dpkg-buildpackage no longer calls build, only binary)
Your message dated Wed, 18 Oct 2017 00:19:01 + with message-id and subject line Bug#878899: fixed in dpkg 1.19.0.2 has caused the Debian Bug report #878899, regarding dpkg-buildpackage no longer calls build, only binary 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.) -- 878899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dpkg-dev Version: 1.19.0.1 Severity: serious 14:39 < _rene_> hmm. dpkg-dev 1.19.0.1 broken for anyone else? looks like it doesn't call build(-arch,indep) anymore at dpkg-buildpackage -b, but just binary? I seen the same debugging a FTBFS. --- End Message --- --- Begin Message --- Source: dpkg Source-Version: 1.19.0.2 We believe that the bug you reported is fixed in the latest version of dpkg, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated dpkg 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, 18 Oct 2017 01:28:20 +0200 Source: dpkg Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect Architecture: source Version: 1.19.0.2 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect- Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 878899 878919 Changes: dpkg (1.19.0.2) unstable; urgency=medium . * Fix logic in dpkg-buildpackage to decide whether to run build targets, which broke tons of packages that are violating Debian policy MUSTs. Thanks to James Clarke . Closes: #878899 * Do not try to recompute hashes for the .dsc file when signing binary-only builds in dpkg-buildpackage. Reported by Ximin Luo . * Packaging: - Add Breaks to libdpkg-perl against pkg-kde-tools (<< 0.15.28~), as that package is using private modules with no API guarantees, that obviously broke due to recent changes in 1.19.0. Closes: #878919 Checksums-Sha1: b2f6d9173af40a17b02d94b16b0145ec9429e160 1977 dpkg_1.19.0.2.dsc 45119dfd8048a3e1a69de62f160f10b4ba746586 4558044 dpkg_1.19.0.2.tar.xz 8aac5d479df5a8d537c9c40ab9c373024d52e6fb 7288 dpkg_1.19.0.2_amd64.buildinfo Checksums-Sha256: d84249ca302d687e90f62b396e45b3ae6d24f6a6113353be5022aa985e475b78 1977 dpkg_1.19.0.2.dsc 1436cd75d3910e32d1366fff9b1ec7cfb154bc0d63c035e22dba76fdd06ad6a2 4558044 dpkg_1.19.0.2.tar.xz 170a5d55e11e097a3f907809b0560a026351c342de0632b87eb39d028e07df0d 7288 dpkg_1.19.0.2_amd64.buildinfo Files: 114f6254ea009b78ebe11b295241a6b8 1977 admin required dpkg_1.19.0.2.dsc 49dc1fb11d434784ca002fe93af8eaa6 4558044 admin required dpkg_1.19.0.2.tar.xz 82865dbd20a886364495439fcb754bfc 7288 admin required dpkg_1.19.0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAlnmmaAACgkQuXK/PqSu V6N8UQ/9Hxb1afXmr5vfb9BENvZgWhd6oedtp+pjeRRn9T3OOMF1OQuG+HG1EOjJ HYzbNWziupHtoU8Iqly1ClD0qPwpGCR14+K9MIYltQ4b5Fo1qeaDB5ATHFV8/FZk i6UsZxz5IQ+s7R0eUMs8pGkrIpAMv3qXrKKuRYyUihTQFRCIv9MQyoHCuDzuHNtT 8j+HSf8e+svWiYnllC6i8UTVZHBHK7OsoyPgyhiuS/OHLJUJhV/AYBBiyHJap13b FYfdyWIRPfQa73L+QHWZUkWMdcdVS6fEckNfJ8tULeV7A3l7aP6rBGuAcpkxo94p boj0Hpq+GrA3FORtCfcgQ/7lr23yx56BUDIXjlYXyyi11bBiOTo9BzE0oMCyCyzg awKjiXS4LOdMOKlF3y/pymFW9mgr2asiKLgCXDcKa+apf18gZzA8QHv1w2hx/yCk EYR86v88TVBhToBuRg0HEvDdXP+/Od0pHPULcPhlr3n50uDOhZpnHpRs9bOYHgVc 4sZ6veoMpmCP6FZDmQ31Q8dyBsYyrX4H45z6RVIA+UPsZ2z2MWXqY6ePRgAPe4Dc ClS0Id8L2exK4x/ppQTT9NcsasHfnNuBIh64M19w0AQKOJVSvEoNR2P9luGS1p3H HEjg0tD4LH5FFklKFrvZzVPgTNUYSWQxitJuLD75gY5Cc5leLBI= =zEg+ -END PGP SIGNATURE End Message ---
Bug#878899: in package dpkg marked as pending
Control: tag 878899 pending Hi! Bug #878899 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=029aa41 --- commit 029aa41244e44c6d4675ac7af69df4ce29bbe2b0 Author: Guillem Jover Date: Tue Oct 17 21:20:53 2017 +0200 dpkg-buildpackage: Fix logic to decide whether to call the build targets The build targets never require root, so checking them will always return false. We need to key on the binary target instead. This broke tons of packages that are violating Debian policy MUSTs. Thanks-to: James Clarke Closes: #878899 (cherry picked from commit a3a9527efb1345ac71014dd59da911db05e99ea0) diff --git a/debian/changelog b/debian/changelog index 9724658..2d81348 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,8 @@ dpkg (1.19.0.2) UNRELEASED; urgency=medium + * Fix logic in dpkg-buildpackage to decide whether to run build targets, +which broke tons of packages that are violating Debian policy MUSTs. +Thanks to James Clarke . Closes: #878899 * Packaging: - Add Breaks to libdpkg-perl against pkg-kde-tools (<< 0.15.28~), as that package is using private modules with no API guarantees, that
Processed: Bug#878899 in package dpkg marked as pending
Processing control commands: > tag 878899 pending Bug #878899 [dpkg-dev] dpkg-buildpackage no longer calls build, only binary Added tag(s) pending. -- 878899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fix syntax error...
Processing commands for cont...@bugs.debian.org: > severity 878912 normal Bug #878912 [docker.io] docker.io: docker run fails saying that containerd-shim not installed Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 878912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878899: in package dpkg marked as pending
Control: tag 878899 pending Hi! Bug #878899 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=a3a9527 --- commit a3a9527efb1345ac71014dd59da911db05e99ea0 Author: Guillem Jover Date: Tue Oct 17 21:20:53 2017 +0200 dpkg-buildpackage: Fix logic to decide whether to call the build targets The build targets never require root, so checking them will always return false. We need to key on the binary target instead. This broke tons of packages that are violating Debian policy MUSTs. Thanks-to: James Clarke Closes: #878899 diff --git a/debian/changelog b/debian/changelog index b0d8ca6..fd9c8a8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,8 @@ dpkg (1.19.1) UNRELEASED; urgency=medium + * Fix logic in dpkg-buildpackage to decide whether to run build targets, +which broke tons of packages that are violating Debian policy MUSTs. +Thanks to James Clarke . Closes: #878899 * Packaging: - Install update-alternatives policykit-1 file. - Add Breaks to libdpkg-perl against pkg-kde-tools (<< 0.15.28~), as
Processed: Bug#878899 in package dpkg marked as pending
Processing control commands: > tag 878899 pending Bug #878899 [dpkg-dev] dpkg-buildpackage no longer calls build, only binary Ignoring request to alter tags of bug #878899 to the same tags previously set -- 878899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#878912: docker.io: docker run fails saying that containerd-shim not installed
Processing commands for cont...@bugs.debian.org: > tags 878912 + moreinfo unreproducible Bug #878912 [docker.io] docker.io: docker run fails saying that containerd-shim not installed Added tag(s) moreinfo and unreproducible. > severity normal Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 878912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878912: docker.io: docker run fails saying that containerd-shim not installed
tags 878912 + moreinfo unreproducible severity normal thanks On 17 October 2017 at 10:05, Antonio Terceiro wrote: > On a completely up to date sid system: > > $ docker run -it --rm debian:sid > docker: Error response from daemon: containerd-shim not installed on system. I can't seem to reproduce; created a completely fresh Sid instance, installed docker.io, and got the following result: The following NEW packages will be installed: dmsetup (2:1.02.142-1) docker-containerd (0.2.3+git+docker1.13.1~ds1-1) docker-runc (1.0.0~rc2+git+docker1.13.1~ds1-2) docker.io (1.13.1~ds2-3) golang-libnetwork (0.8.0-dev.2+git20170202.599.45b4086-3) iptables (1.6.1-2) libapparmor1 (2.11.0-11) libdevmapper1.02.1 (2:1.02.142-1) libip4tc0 (1.6.1-2) libip6tc0 (1.6.1-2) libiptc0 (1.6.1-2) libnetfilter-conntrack3 (1.0.6-2) libnfnetlink0 (1.0.1-3+b1) libseccomp2 (2.3.1-2.1) libsqlite3-0 (3.20.1-2) libxtables12 (1.6.1-2) 0 upgraded, 16 newly installed, 0 to remove and 25 not upgraded. $ docker version Client: Version: 1.13.1 API version: 1.26 Go version: go1.9.1 Git commit: 092cba3 Built:Sat Oct 14 16:54:40 2017 OS/Arch: linux/amd64 Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Go version: go1.9.1 Git commit: 092cba3 Built:Sat Oct 14 16:54:40 2017 OS/Arch: linux/amd64 Experimental: false $ docker run -it --rm debian:sid Unable to find image 'debian:sid' locally sid: Pulling from library/debian 3a8649ffa174: Pull complete Digest: sha256:58c8f0c963c0813cbad2809a12b1ca9031e3ab5aa31258f2675c65a42475dc23 Status: Downloaded newer image for debian:sid root@b9ed033bd019:/# ls -l total 48 lrwxrwxrwx 1 root root7 Oct 9 00:00 bin -> usr/bin drwxr-xr-x 2 root root 4096 Jun 25 22:19 boot drwxr-xr-x 5 root root 360 Oct 17 23:54 dev drwxr-xr-x 30 root root 4096 Oct 17 23:54 etc drwxr-xr-x 2 root root 4096 Jun 25 22:19 home lrwxrwxrwx 1 root root7 Oct 9 00:00 lib -> usr/lib lrwxrwxrwx 1 root root9 Oct 9 00:00 lib32 -> usr/lib32 lrwxrwxrwx 1 root root9 Oct 9 00:00 lib64 -> usr/lib64 lrwxrwxrwx 1 root root 10 Oct 9 00:00 libx32 -> usr/libx32 drwxr-xr-x 2 root root 4096 Oct 9 00:00 media drwxr-xr-x 2 root root 4096 Oct 9 00:00 mnt drwxr-xr-x 2 root root 4096 Oct 9 00:00 opt dr-xr-xr-x 440 root root0 Oct 17 23:54 proc drwx-- 2 root root 4096 Oct 9 00:00 root drwxr-xr-x 4 root root 4096 Oct 9 00:00 run lrwxrwxrwx 1 root root8 Oct 9 00:00 sbin -> usr/sbin drwxr-xr-x 2 root root 4096 Oct 9 00:00 srv dr-xr-xr-x 12 root root0 Oct 17 23:54 sys drwxrwxrwt 2 root root 4096 Oct 9 00:00 tmp drwxr-xr-x 13 root root 4096 Oct 9 00:00 usr drwxr-xr-x 11 root root 4096 Oct 9 00:00 var Have you restarted your Docker daemon since upgrading? If not, it's likely still running the old daemon referencing the older packages, and the package tries to be careful about automatically restarting your daemon because that can cause downtime for your containers. Since this looks to be environmental, I've downgraded the severity and updated the tags of this bug accordingly. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
Bug#878912: Works for me
$ apt list --installed 'docker*' Listando... Hecho docker-containerd/unstable,now 0.2.3+git+docker1.13.1~ds1-1 amd64 [instalado, automático] docker-runc/unstable,now 1.0.0~rc2+git+docker1.13.1~ds1-2 amd64 [instalado, automático] docker.io/unstable,now 1.13.1~ds2-3 amd64 [instalado] $ dpkg -S /usr/bin/containerd-shim /usr/bin/docker-containerd-shim containerd: /usr/bin/containerd-shim docker-containerd: /usr/bin/docker-containerd-shim But : $ aptitude why containerd Automatically installed, current version 0.2.3+git20170126.85.aa8187d~ds1-2, priority opcional No dependencies require to install containerd $ sudo apt remove containerd ... And $ docker container [ stop / start ] idcontainer work # work before and after removing containerd I do not want to tag this bug as fixed, maybe work for me but not for you Regards
Bug#877075: sikulix: hard coded dependency on libopencv2.4-java
Mattia Rizzolo a écrit le 18/10/2017 à 01:11 :
> On Wed, Oct 18, 2017 at 12:58:32AM +0200, Gilles Filippini wrote:
>> On Tue, 17 Oct 2017 12:48:29 +0200 Mattia Rizzolo wrote:
>>> On Tue, Oct 17, 2017 at 10:26:11AM +0200, Gilles Filippini wrote:
How about mavenizing OpenCV Java lib so that ${maven:Depends} would find
out the right libopencvX.Y-java dependency?
>>>
>>> I'll happily accept patches for that.
>>
>> Attached.
>
> Thank you!
>
> It will definitely be part of the next upload, although I'd like to
> avoid to do a 4th upload in just 3 days… OpenCV is not exactly light,
> there are several architectures where it takes more than 12h to build.
> Could you consider keeping the hardconded lib just a little longer and
> bump the version?
Will do it by tomorrow.
> We will have to do another opencv transition soon after this one ended
> anyway (if we manage to get it build right the way we want it…), so we
> will have ways to employ this thing soon enough.
Thanks,
_g.
signature.asc
Description: OpenPGP digital signature
Bug#877075: sikulix: hard coded dependency on libopencv2.4-java
On Wed, Oct 18, 2017 at 12:58:32AM +0200, Gilles Filippini wrote:
> On Tue, 17 Oct 2017 12:48:29 +0200 Mattia Rizzolo wrote:
> > On Tue, Oct 17, 2017 at 10:26:11AM +0200, Gilles Filippini wrote:
> > > How about mavenizing OpenCV Java lib so that ${maven:Depends} would find
> > > out the right libopencvX.Y-java dependency?
> >
> > I'll happily accept patches for that.
>
> Attached.
Thank you!
It will definitely be part of the next upload, although I'd like to
avoid to do a 4th upload in just 3 days… OpenCV is not exactly light,
there are several architectures where it takes more than 12h to build.
Could you consider keeping the hardconded lib just a little longer and
bump the version?
We will have to do another opencv transition soon after this one ended
anyway (if we manage to get it build right the way we want it…), so we
will have ways to employ this thing soon enough.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Processed: libopencv3.2-java - Please install maven artifacts
Processing control commands: > block 877075 by -1 Bug #877075 [libsikulixapi-java] sikulix: hard coded dependency on libopencv2.4-java 877075 was blocked by: 877073 877075 was blocking: 841733 Added blocking bug(s) of 877075: 878949 > tags -1 + patch Bug #878949 [libopencv3.2-java] libopencv3.2-java - Please install maven artifacts Added tag(s) patch. -- 877075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877075 878949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > found -1 17.2.2-1 Bug #878948 [libgl1-mesa-glx] Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current Marked as found in versions mesa/17.2.2-1. -- 878948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878948:
Control: found -1 17.2.2-1
Bug#878841: marked as done (clips FTBFS: uudecode: not found)
Your message dated Tue, 17 Oct 2017 21:49:46 +
with message-id
and subject line Bug#878841: fixed in clips 6.30-2
has caused the Debian Bug report #878841,
regarding clips FTBFS: uudecode: not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
878841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clips
Version: 6.30-1
Severity: serious
https://buildd.debian.org/status/package.php?p=clips&suite=sid
...
cd doc && /usr/bin/make -f Makefile all
make[1]: Entering directory '/<>/doc'
uudecode -o advanced_programming_guide.pdf --- End Message ---
--- Begin Message ---
Source: clips
Source-Version: 6.30-2
We believe that the bug you reported is fixed in the latest version of
clips, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña (supplier of updated clips
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: Tue, 17 Oct 2017 01:26:11 +0200
Source: clips
Binary: clips libclips libclips-dev clips-common clips-doc
Architecture: source all i386
Version: 6.30-2
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernandez-Sanguino Peña
Changed-By: Javier Fernández-Sanguino Peña
Description:
clips - "C" Language Integrated Production System
clips-common - CLIPS common files and examples
clips-doc - "C" Language Integrated Production System Documentation
libclips - CLIPS shared libraries
libclips-dev - CLIPS shared libraries
Closes: 436632 878841
Changes:
clips (6.30-2) unstable; urgency=medium
.
* debian/control:
- Add sharutils to Build-Deps as it is required for building the
documentation (Closes: #878841)
- Include contents from clips-doc package
- Adjust description of clips-common to highlight that it provides the
examples
- Adjust description of clips-doc to highlight that it provides the
documentation, and not the examples
- Updated Standards Version, no changes required
- Add ${misc:Depends} to packages (lintian fix)
- Change Recommended package from 'gv' to 'evince' for pdf reader
* debian/changelog:
- Integrate history of the clips-doc package
- Document two Launchpad bugs which have been closed in previous
package versions
* debian/rules:
- Replace dh_clean -k with dh_prep (lintian fix)
- Replace definition of INSTALL PROGRAM from 'install -c -s' to
simply 'install' to prevent stripping the binaries (let dh_strip
do it, which honos the nostrip build option (Closes: #436632)
- Create clips-doc.docs and clips-common.examples so we call
simply dh_installdocs and dh_installexamples (without -p) in the
binary indep target
* debian/clips.1:
- Comment reference to help file as it is not currently provided
- Remove reference to the clips-doc package, refer to clips-common instead
- Adjust reference to documentation, FAQ is no longer provided but PDF and
HTML manuals area
* debian/clips-doc.doc-base.{abstracts,apg,architecture,bpg,ig,usrguide}:
Move here from the clips-doc package to keep all the content in the same
location. Add references to HTML documentation.
* debian/README.Debian: adjust references, improve wording and update
HTTP links
* debian/patches/clips_improved_build.diff: Do not strip binaries in
libraries, let dh_strip do it for us. This makes it possible to honor
the nostrip build option (Closes: #436632)
* debian/watch: Add based on the patch provided by Joao Eriberto Mota Filho
for the clips-doc package
Checksums-Sha1:
aa5f629ba243555ab69444133bc9f147ba2ab3f1 1965 clips_6.30-2.dsc
20d3745f6aa8911dbac0836f1dbfd75a80a0b3a2 21896708 clips_6.30-2.debian.tar.xz
2c1df76bcc0a437049038b6d4407dba622867d68 138446 clips-common_6.30-2_all.deb
9ba687735919b06bbe608a9baae42d1150e54ef3 2216 clips-dbgsym_6.30-2_i386.deb
b271e019322097db8538fcb9ac09aefee6a53ca5 28872194 clips-doc_6.30-2_all.deb
53
Bug#877322: git-buildpackage autoremoval
Guido Günther writes ("Re: Bug#877322: git-buildpackage autoremoval"):
> On Tue, Oct 17, 2017 at 02:57:33PM +0100, Ian Jackson wrote:
> > This bug means that the autoremoval robot wants to remove
> > git-buildpackage. I'm getting mails about it planning to remove dgit,
> > to clear the way.
> >
> > Do you intend to upload the docs change to sid soon ?
>
> Yes, before the autoremoval for sure. Sorry for being a pain here but I
> wanted to give gbp as much exposure as possible in experimental.
OK, fine. Thanks for the reassurance. If the deadline gets closer I
may ping you again :-).
Regards,
Ian.
Processed: Re: Bug#869586: botch: Fails ADT tests with python3.6
Processing control commands: > retitle -1 botch FTBFS with Python 3.6 as default Bug #869586 [src:botch] botch: Fails ADT tests with python3.6 Changed Bug title to 'botch FTBFS with Python 3.6 as default' from 'botch: Fails ADT tests with python3.6'. > severity -1 serious Bug #869586 [src:botch] botch FTBFS with Python 3.6 as default Severity set to 'serious' from 'important' > tags -1 - moreinfo Bug #869586 [src:botch] botch FTBFS with Python 3.6 as default Removed tag(s) moreinfo. > found -1 0.21-4 Bug #869586 [src:botch] botch FTBFS with Python 3.6 as default Marked as found in versions botch/0.21-4. -- 869586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#873118: marked as done (commons-io: FTBFS: Several failed unit tests)
Your message dated Tue, 17 Oct 2017 21:19:49 + with message-id and subject line Bug#873118: fixed in commons-io 2.5-2 has caused the Debian Bug report #873118, regarding commons-io: FTBFS: Several failed unit tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 873118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:commons-io Version: 2.5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) [...] Results : Tests in error: FileUtilsTestCase.testCopyDirectoryToDirectory_NonExistingDest:1323 ?? IO Unab... FileUtilsTestCase.testCopyDirectoryToExistingDest:1409 ?? IO Unable to delete ... FileUtilsTestCase.testCopyDirectoryToNonExistingDest:1367 ?? IO Unable to dele... Tests run: 1157, Failures: 0, Errors: 3, Skipped: 4 [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 02:01 min [[1;34mINFO[m] Finished at: 2017-08-24T09:16:19Z [[1;34mINFO[m] Final Memory: 14M/276M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-surefire-plugin:2.19.1:test[m [1m(default-test)[m on project [36mcommons-io[m: [1;31mThere are test failures.[m [[1;31mERROR[m] [1;31m[m [[1;31mERROR[m] [1;31mPlease refer to /<>/target/surefire-reports for the individual test results.[m [[1;31mERROR[m] -> [1m[Help 1][m [[1;31mERROR[m] [[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch. [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug logging. [[1;31mERROR[m] [[1;31mERROR[m] For more information about the errors and possible solutions, please read the following articles: [[1;31mERROR[m] [1m[Help 1][m http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche commons-io_2.5-1_amd64-2017-08-24T09:13:55Z.build.gz Description: application/gzip signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: commons-io Source-Version: 2.5-2 We believe that the bug you reported is fixed in the latest version of commons-io, 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 873...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated commons-io package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Oct 2017 22:03:07 +0200 Source: commons-io Binary: libcommons-io-java libcommons-io-java-doc Architecture: source Version: 2.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: l
Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated
On Sat, Aug 12, 2017 at 11:43:58PM -0400, Jeremy Bicha wrote: >... > The package does build successfully without the libwebkitgtk-dev > build-dependency. But the resulting library will still dynamically load it. > It feels to me like the libswt-webkit-gtk-3-jni was already broken > since it doesn't have a dependency on any webkitgtk library The missing dependency sounds like a bug. > (I think > the correct one would be libwebkitgtk-3.0-0 but that is still part of > the deprecated libraries which are being removed.) It does use libwebkitgtk-1.0-0: https://sources.debian.net/src/swt-gtk/3.8.2-4/webkitgtk.h/ I just tried, and it does work when libwebkitgtk-1.0-0 is installed (and fails without). >... > On behalf of the Debian WebKit Maintainers, > Jeremy Bicha 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
Bug#876033: primusrun doesn't find libGL.so.1
On martedì 17 ottobre 2017 20:53:49 CEST Luca Boccassi wrote: > What's the output of: > > dpkg -l | grep 375.82-5 $ dpkg -l | grep 375.82-5 ii libegl-nvidia0:amd64375.82-5 amd64 NVIDIA binary EGL library ii libegl-nvidia0:i386 375.82-5 i386NVIDIA binary EGL library ii libgl1-nvidia-glx:amd64 375.82-5 amd64 NVIDIA binary OpenGL/GLX... ii libglx-nvidia0:amd64375.82-5 amd64 NVIDIA binary GLX library ii libglx-nvidia0:i386 375.82-5 i386NVIDIA binary GLX library ii libnvidia-eglcore:amd64 375.82-5 amd64 NVIDIA binary EGL core l... ii libnvidia-eglcore:i386 375.82-5 i386NVIDIA binary EGL core l... ii libnvidia-glcore:amd64 375.82-5 amd64 NVIDIA binary OpenGL/GLX... ii libnvidia-glcore:i386 375.82-5 i386NVIDIA binary OpenGL/GLX... ii libnvidia-ml1:amd64 375.82-5 amd64 NVIDIA Management Librar... ii nvidia-alternative 375.82-5 amd64 allows the selection of ... ii nvidia-egl-common 375.82-5 amd64 NVIDIA binary EGL driver... ii nvidia-egl-icd:amd64375.82-5 amd64 NVIDIA EGL installable c... ii nvidia-egl-icd:i386 375.82-5 i386NVIDIA EGL installable c... ii nvidia-kernel-dkms 375.82-5 amd64 NVIDIA binary kernel mod... ii nvidia-kernel-support 375.82-5 amd64 NVIDIA binary kernel mod... ii nvidia-legacy-check 375.82-5 amd64 check for NVIDIA GPUs re... ii nvidia-vdpau-driver:amd64 375.82-5 amd64 Video Decode and Present... ii xserver-xorg-video-nvidia 375.82-5 amd64 NVIDIA binary Xorg driver Thanks.
Processed: Pending fixes for bugs in the commons-io package
Processing commands for cont...@bugs.debian.org: > tag 873118 + pending Bug #873118 [src:commons-io] commons-io: FTBFS: Several failed unit tests Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 873118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"
Hi!
On Tue, 2017-10-17 at 19:48:07 +0300, Niko Tyni wrote:
> On Tue, Oct 17, 2017 at 05:44:26PM +0200, gregor herrmann wrote:
> > Package: dh-make-perl
> > Version: 0.95
> > Severity: serious
> > Tags: buster sid
> > Justification: fails to build from source
>
> > As first seen on ci.debian.net, dh-make-perl's test suite fails with
> > libdpkg-perl 1.19.0 and 1.19.0.1:
> >
> > Insecure dependency in eval while running with -T switch at
> > /usr/share/perl5/Dpkg/Vendor.pm line 164.
>
> > The -T seems to come from t/debian-version.t itself; no idea yet why
> > it is a problem now and why it's used here in the first place.
> It looks like Dpkg::Vendor::get_vendor_info() contents have become
> tainted, probably due to changes in Dpkg::Control::HashCore. It used to
> dig the values out with regexp captures but now uses split.
>
>
> https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?h=sid&id=9e5e03e9a6ddf74bb22ffc5ea8794a14a592d6b6
>
> A test case is
>
> perl -T -MDpkg::Vendor=get_vendor_info -MScalar::Util=tainted -e 'die if
> tainted get_vendor_info()->{Vendor}'
>
> which dies on libdpkg-perl 1.19.0.1 but not 1.18.24.
>
> I don't know if the earlier untainting was accidental or intended.
> Copying the dpkg maintainers.
TBH, I was not aware that anyone was running Dpkg modules in taint
mode. And I don't think anyone has writen code for the modules with
that in mind. I'm not sure either how much of it is taint clean, for
example.
If people are really running this code in taint mode, I'm willing to
discuss which parts of the API would make sense to cover or not, and
what tradeoffs related to performance to take, etc.
Thanks,
Guillem
Bug#873118: Pending fixes for bugs in the commons-io package
tag 873118 + pending thanks Some bugs in the commons-io package are closed in revision 190076e2660c9c7b1e68993f2ead7925909ef48f in branch 'master' by Markus Koschany The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/commons-io.git/commit/?id=190076e Commit message: Ignore test failures. Could be a problem with file permissions in the build environment. It doesn't look that serious to me. Closes: #873118
Bug#878899: dpkg-buildpackage no longer calls build, only binary
Hi!
On Tue, 2017-10-17 at 16:31:05 +0100, James Clarke wrote:
> On Tue, Oct 17, 2017 at 06:03:20PM +0300, Adrian Bunk wrote:
> > Package: dpkg-dev
> > Version: 1.19.0.1
> > Severity: serious
> >
> > 14:39 < _rene_> hmm. dpkg-dev 1.19.0.1 broken for anyone else? looks like
> > it doesn't call build(-arch,indep) anymore at
> > dpkg-buildpackage -b, but just binary?
> >
> > I seen the same debugging a FTBFS.
>
> I believe this is caused by [0]:
>
> [16:26:57]my understanding is that rules_requires_root is going
> to be returning 0 for the build-* targets
> [16:27:06]jrtc27: clearly the default tries to be binary-targets
> which would preserve the original behaviour
> [16:27:19]since $rules_requires_root{'binary-targets'} will be
> set, but $target_legacy_root{'build'} will be false
> [16:27:33]aha
> [16:28:17]so I think the two instances of
> rules_requires_root($buildtarget) should be rules_requires_root($binarytarget)
> [16:28:33]jrtc27: thank you. so it should say "return if not
> any_target_requires_root;" in build_target_fallback
> [16:28:43]or that
> [16:28:53]rules_requires_root('build') is correct to return 0
> [16:28:58]build doesn't need root :P
> [16:29:08]no package building today I guess
Right, thanks for the analisys! I've fixed this locally now, and will
be included in 1.19.0.2.
Although, I've to say, the Severity looks a bit unfair (while practically
correct), because any package that gets broken due to build rules not
being called is violating several Debian policy MUSTS anyway.
I'll open a discussion on d-d later today.
Thanks,
Guillem
Bug#878919: libdpkg-perl needs Breaks: pkg-kde-tools (<< 0.15.28~)
Control: severity -1 important Hi! On Tue, 2017-10-17 at 20:23:46 +0300, Adrian Bunk wrote: > Package: libdpkg-perl > Version: 1.19.0.1 > Severity: serious > > Due to #878892 That package is using a private module with no API guarantees, as stated in README.api and marked as such via its version. I'll add the Breaks, but meh. :) Thanks, Guillem
Processed: Re: Bug#878919: libdpkg-perl needs Breaks: pkg-kde-tools (<< 0.15.28~)
Processing control commands: > severity -1 important Bug #878919 [libdpkg-perl] libdpkg-perl needs Breaks: pkg-kde-tools (<< 0.15.28~) Severity set to 'important' from 'serious' -- 878919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#876033: primusrun doesn't find libGL.so.1
On Tue, 2017-10-17 at 17:08 +0200, devfra wrote: > Hello > > The new version of primus have arrived today in Testing, everything > works but > there is still a problem with the 32 bit version of LibGL.so.1. > > I have a couple of 32-bit only applications that I run with wine, > they give me > the following message: > > primus: fatal: failed to load any of the libraries: /usr/lib/x86_64- > linux-gnu/ > nvidia/libGL.so.1:/usr/lib/i386-linux- > gnu/nvidia/libGL.so.1:/usr/lib/nvidia/ > libGL.so.1 > /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: wrong ELF class: > ELFCLASS64 > /usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object > file: No > such file or directory > /usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such > file or > directory > > Other 64 bit applications work with bumblebee as expected. What's the output of: dpkg -l | grep 375.82-5 -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#877613: marked as done (icewm: FTBFS: icesound.cc:360:25: error: 'write' was not declared in this scope)
Your message dated Tue, 17 Oct 2017 19:49:30 +
with message-id
and subject line Bug#877613: fixed in icewm 1.4.3.0~pre-20171017-1
has caused the Debian Bug report #877613,
regarding icewm: FTBFS: icesound.cc:360:25: error: 'write' was not declared in
this scope
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.)
--
877613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icewm
Version: 1.4.3.0~pre-20171002-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
icewm FTBFS in experimental:
https://buildd.debian.org/status/package.php?p=icewm&suite=experimental
from
https://buildd.debian.org/status/fetch.php?pkg=icewm&arch=i386&ver=1.4.3.0%7Epre-20171002-2&stamp=1506990247&raw=0
[...]
/<>/src/icesound.cc: In member function 'virtual bool
YOSSAudio::play(int)':
/<>/src/icesound.cc:360:25: error: 'write' was not declared in
this scope
int wrote = write(device, sbuf, bytes);
^
/<>/src/icesound.cc:360:25: note: suggested alternative: 'fwrite'
int wrote = write(device, sbuf, bytes);
^
fwrite
/<>/src/icesound.cc: In member function 'virtual int
YOSSAudio::init(SoundConf*)':
/<>/src/icesound.cc:401:43: error: 'O_WRONLY' was not declared in
this scope
if ((device = open(conf->ossDevice(), O_WRONLY)) == -1) {
^~~~
[...]
A local build om amd64 compiled successfully, but failed later on with
debian/rules override_dh_install
make[1]: Entering directory '/build/icewm-1.4.3.0~pre-20171002'
dh /usr/share/quilt/quilt.make --parallel
dh: Unknown sequence /usr/share/quilt/quilt.make (choose from: binary
binary-arch binary-indep build build-arch build-indep clean install
install-arch install-indep)
dh_install
dh_install: Cannot find (any matches for) "usr/bin/icesound" (tried in .,
debian/tmp)
dh_install: icewm missing files: usr/bin/icesound
dh_install: missing files, aborting
debian/rules:64: recipe for target 'override_dh_install' failed
Andreas
--- End Message ---
--- Begin Message ---
Source: icewm
Source-Version: 1.4.3.0~pre-20171017-1
We believe that the bug you reported is fixed in the latest version of
icewm, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Eduard Bloch (supplier of updated icewm 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: Tue, 17 Oct 2017 19:49:37 +0200
Source: icewm
Binary: icewm-common icewm icewm-lite icewm-experimental
Architecture: source
Version: 1.4.3.0~pre-20171017-1
Distribution: experimental
Urgency: low
Maintainer: Eduard Bloch
Changed-By: Eduard Bloch
Description:
icewm - wonderful Win95-OS/2-Motif-like window manager
icewm-common - wonderful Win95-OS/2-Motif-like window manager
icewm-experimental - wonderful Win95-OS/2-Motif-like window manager
icewm-lite - wonderful Win95-OS/2-Motif-like window manager
Closes: 174712 711603 850919 877613
Changes:
icewm (1.4.3.0~pre-20171017-1) experimental; urgency=low
.
* New upstream snapshot
+ includes FTBFS fixes (closes: #877613)
+ various fixes for colormap handling (#261876 related)
+ manpage updates (mostly in the previous snapshots, closes: #711603)
+ taskbar shouldn't be focusable anymore (closes: #174712)
.
[ Helmut Grohne ]
* Fix FTCBFS: Let dh_auto_configure pass cross compilers (closes: #850919)
Checksums-Sha1:
e2762b77bfb503cad7ae0830762c105eec0499e0 2293 icewm_1.4.3.0~pre-20171017-1.dsc
f9552d3afe060d5a1f0c4a5691473ffa9e021f53 1225156
icewm_1.4.3.0~pre-20171017.orig.tar.xz
e0a7629d855e8e8d85e7e2a6ea393cf873187c2e 110464
icewm_1.4.3.0~pre-20171017-1.debian.tar.xz
894c66b91abb4e3403bf55ac8a45918d4c7ee617 11455
icewm_1.4.3.0~pre-20
Processed: closing 814775
Processing commands for cont...@bugs.debian.org: > # Closing bug; previously I accidentally only marked it fixed without closing > close 814775 Bug #814775 [electrum] electrum: Missing dependency to python-pbkdf2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 814775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed
Hi! (Applications linked against) libbpfcc will dynamically compile and load C source code into eBPF byte code at runtime and load the result into the kernel for various purposes (e.g. socket filtering, tracing, etc.). For this to work, it needs the kernel headers of the *currently running kernel* [0,1]. Therefore, the maintainer of libbpfcc in Debian added a corresponding dependency [2] which unfortunately breaks everything but amd64 [3] and does also not quite fix the original bug [4]. Please comment on bug #877925 [4] and/or #878922 [3] regarding on how to solve the "this package needs the current kernel's headers installed" problem! Best regards Alexander Kurtz [0] https://github.com/iovisor/bcc/issues/397 [1] https://github.com/iovisor/bcc/issues/743 [2] https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=f73049e48fd98dd01d4475f88f6b490e6a1b34bb [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878935 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#878932: generator-scripting-language: Incomplete debian/copyright?
Processing control commands: > tags -1 pending Bug #878932 [src:generator-scripting-language] generator-scripting-language: Incomplete debian/copyright? Warning: Unknown package 'src:generator-scripting-language' Added tag(s) pending. Warning: Unknown package 'src:generator-scripting-language' -- 878932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878932: generator-scripting-language: Incomplete debian/copyright?
Control: tags -1 pending On Tue, 2017-10-17 at 20:08 +0100, Chris Lamb wrote: > Source: generator-scripting-language > Version: 4.1.5-1 > Severity: serious > Justication: Policy 12.5 > X-Debbugs-CC: Luca Boccassi > > Hi, > > I just ACCEPTed generator-scripting-language from NEW but noticed it > was missing attribution in debian/copyright for at least Todd Miller > within sflstr.c. > > (This is not exhaustive so please check over the entire package > carefully and address these on your next upload.) > > > Regards, Hi Chris, Thank you, and good catch! I ran licensecheck but it only reported GPL-3 for that file. I had done some manual greps but evidently failed to notice it. $ licensecheck -r . | grep sflstr ./src/sflstr.c: GPL (v3 or later) ./src/sflstr.h: GPL (v3 or later) I've now done some more grepping for common terms and I cannot see other copyright/licenses. I'll upload as soon as I get the confirmation email. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#878937: visp: port baseline violation on i386+amd64 (also causes FTBFS on amd64)
Source: visp Version: 3.0.1-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=visp&arch=i386&ver=3.0.1-2&stamp=1487064152&raw=0 ... -- Performing Test HAVE_CXX_MSSE2 -- Performing Test HAVE_CXX_MSSE2 - Success -- Performing Test HAVE_C_MSSE2 -- Performing Test HAVE_C_MSSE2 - Success -- Performing Test HAVE_CXX_MSSE3 -- Performing Test HAVE_CXX_MSSE3 - Success -- Performing Test HAVE_C_MSSE3 -- Performing Test HAVE_C_MSSE3 - Success -- Performing Test HAVE_CXX_MSSSE3 -- Performing Test HAVE_CXX_MSSSE3 - Success -- Performing Test HAVE_C_MSSSE3 -- Performing Test HAVE_C_MSSSE3 - Success ... -- C++ flags (Release): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -fopenmp -fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -- C++ flags (Debug): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -fopenmp -fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g -- C Compiler: /usr/bin/cc -- C flags (Release): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -fopenmp -fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -- C flags (Debug): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -fopenmp -fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g ... The following tests FAILED: 2 - testConversion (ILLEGAL) 4 - testCropAdvanced (ILLEGAL) 14 - testIoPPM (ILLEGAL) 16 - testReadImage (ILLEGAL) 37 - testHistogram (ILLEGAL) 71 - testKeyPoint-5 (ILLEGAL) 72 - testKeyPoint-6 (ILLEGAL) 73 - testKeyPoint-7 (ILLEGAL) 100 - imageDiskRW (ILLEGAL) Errors while running CTest Makefile:107: recipe for target 'test' failed make[2]: *** [test] Error 8 The baseline of the amd64 port includes nothing higher than SSE2. The baseline of the i386 port includes no SSE (not even MMX).
Bug#878935: Unsatisfiable dependencies on !amd64
Package: libbpfcc
Version: 0.3.0-3
Severity: serious
Justification: Makes the package uninstallable on most architectures
Hi!
As [0] shows, libbpfcc has unsatisfiable dependencies on everything but
amd64. This is because [1] is inherently wrong, "linux-headers-amd64"
is of course only available on amd64, the other architectures have
their own meta-packages [2]. Unfortunately there is (AFAIK) no good way
to properly solve the "this package needs the current kernel headers
installed" problem in Debian because
1. There are no (real or virtual) "linux-{image,headers}-
generic" packages (like in Ubuntu [3,4]) which have the same name on
all architectures.
2. Even if there were such packages, there's no guarantee that "linux-
headers-generic" would point to the headers matching the *currently
running* kernel (which is what libbcc needs). In fact, with partial
upgrades, migrations from unstable to testing, upgraded-but-not-yet-
rebooted machines, etc., it is quite likely that libbpfcc will be
broken even if all its dependencies are fulfilled.
I therefore ask you to
1. Revert [1].
2. Reopen [5] and put a note regarding the requirements of the kernel
headers in README.Debian and/or the package description.
3. Talk to the Debian Linux maintainers to find a proper solution to
this problem. It's probably not going to be easy, but these kinds of
problems really deserve to be fixed properly.
Yes, this sucks. I have run into #877925 myself and also thought that
this should be simply solvable with a dependency. Oh, well, at least
you may take comfort in the fact that others [6] have also run into
this problem... ;-)
Best regards
Alexander Kurtz
[0] https://tracker.debian.org/pkg/bpfcc
[1]
https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=f73049e48fd98dd01d4475f88f6b490e6a1b34bb
[2] https://packages.debian.org/source/sid/linux
[3] https://packages.ubuntu.com/artful/linux-image-generic
[4] https://packages.ubuntu.com/artful/linux-headers-generic
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925
[6] https://anonscm.debian.org/git/pkg-dkms/dkms.git/tree/debian/control#n24
signature.asc
Description: This is a digitally signed message part
Bug#878933: seqan2 FTBFS on mips64el
Source: seqan2 Version: 2.3.2+dfsg2-2 Severity: serious Tags: patch Changes: - don't add the CFLAGS/CPPFLAGS again when appending (cosmetic issue resulting in some options being set twice) - pass -mxgot to fix link error on mips64el (re-using code for the no longer built mips/mipsel) - don't overwrite CXXFLAGS with setting -DSEQAN_ASYNC_IO=0 one of the unintended side effects was building without any optimization at all --- debian/rules.old2017-10-17 08:01:14.653184226 + +++ debian/rules2017-10-17 08:05:18.754594240 + @@ -11,8 +11,8 @@ # See https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk -CFLAGS+=$(CPPFLAGS) -O3 -CXXFLAGS+=$(CPPFLAGS) -O3 +CFLAGS+=-O3 +CXXFLAGS+=-O3 # Droping -fstack-protector flag helps **drastically** reducing memory consumption when building the package # export CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS | sed 's/-fstack-protector *//') ## don't do this, it simply triggers #759978 @@ -22,8 +22,8 @@ DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) -ifneq (,$(filter mips mipsel,$(DEB_BUILD_ARCH))) -export CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS | sed 's/-O[1-9]//') -O1 -mxgot +ifneq (,$(filter mips64el,$(DEB_BUILD_ARCH))) +export CXXFLAGS+=-mxgot endif # Disable parallel building on some build archs to save memory ifneq (,$(filter armhf mips kfreebsd%,$(DEB_BUILD_ARCH))) @@ -41,7 +41,7 @@ ifneq (,$(filter mips64el ppc64el s390x alpha hppa powerpc ppc64 sparc64,$(DEB_HOST_ARCH))) # Disable async io on certain target archs, as per upstream # https://github.com/seqan/seqan/issues/1861#issuecomment-336484553 -NOASYNC=-DCMAKE_CXX_FLAGS="-DSEQAN_ASYNC_IO=0" +CXXFLAGS+=-DSEQAN_ASYNC_IO=0 endif pkgapps=seqan-apps @@ -54,7 +54,7 @@ # dh_auto_configure -- -DSEQAN_BUILD_SYSTEM=SEQAN_RELEASE_APPS -DSEQAN_STATIC_APPS=False # skip the tests for now dh_auto_configure -- -DSEQAN_BUILD_SYSTEM=DEVELOP \ -DSEQAN_STATIC_APPS=False -DSEQAN_NO_DOX=1 \ - -DSEQAN_DISABLE_VERSION_CHECK=YES $(NOASYNC) + -DSEQAN_DISABLE_VERSION_CHECK=YES override_dh_auto_configure-indep: ;
Bug#878932: generator-scripting-language: Incomplete debian/copyright?
Source: generator-scripting-language Version: 4.1.5-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Luca Boccassi Hi, I just ACCEPTed generator-scripting-language from NEW but noticed it was missing attribution in debian/copyright for at least Todd Miller within sflstr.c. (This is not exhaustive so please check over the entire package carefully and address these on your next upload.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#876832: These bugs
These bugs can be fixed by changing the build dependency from fonttools to python-fonttools background is in #876439 and #877165. 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
Bug#878922: libbpfcc-dev does not depend on libbpfcc
On Tue, 2017-10-17 at 23:43 +0545, Ritesh Raj Sarraf wrote: > After installing the libbpfcc package manually, does it build proper ? Yes. Best regards Alexander Kurtz signature.asc Description: This is a digitally signed message part
Bug#871069: marked as done (maven-archiver: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.j
Your message dated Tue, 17 Oct 2017 20:56:42 +0200 with message-id and subject line Re: maven-archiver: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1 has caused the Debian Bug report #871069, regarding maven-archiver: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1 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.) -- 871069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: maven-archiver Version: 3.1.1-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170805 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibmaven-archiver-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar > javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [[1;34mINFO[m] Scanning for projects... > [[1;33mWARNING[m] The project org.apache.maven:maven-archiver:jar:3.1.1 > uses prerequisites which is only intended for maven-plugin projects but not > for non maven-plugin projects. For such purposes you should use the > maven-enforcer-plugin. See > https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html > [[1;33mWARNING[m] The POM for > org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 is missing, no > dependency information available > [[1;33mWARNING[m] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-install-plugin:2.5.2: Plugin > org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its > dependencies could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 has not been > downloaded from it before. > [[1;33mWARNING[m] The POM for > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no > dependency information available > [[1;33mWARNING[m] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin > org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies > could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded > from it before. > [[1;33mWARNING[m] The POM for > org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency > information available > [[1;33mWARNING[m] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-site-plugin:3.3: Plugin > org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies > could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded > from it before. > [[1;33mWARNING[m] The POM for
Processed: fixed 878925 in 5.1.30-2
Processing commands for cont...@bugs.debian.org:
> fixed 878925 5.1.30-2
Bug #878925 {Done: Gianfranco Costamagna }
[virtualbox-ext-pack] Installation hangs on license
Marked as fixed in versions virtualbox-ext-pack/5.1.30-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
878925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#878923: vlc: starting video crashes KDE session
Processing control commands: > severity -1 important Bug #878923 [src:vlc] vlc: starting video crashes KDE session Severity set to 'important' from 'grave' > tags -1 + moreinfo Bug #878923 [src:vlc] vlc: starting video crashes KDE session Added tag(s) moreinfo. -- 878923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878923: vlc: starting video crashes KDE session
Control: severity -1 important Control: tags -1 + moreinfo On 2017-10-17 20:38:12, Vincas Dargis wrote: > Package: src:vlc > Version: 2.2.6-6 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Probably after some recent package upgrades, I cannot launch video with VLC > as it > crashes whoe X session: > > LANG=en_US vlc ~/Parsiuntimai/David\ Stone\ Exceptional\ Performance_48_20.mp4 > VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c) > [5591942d8538] [http] lua interface: Lua HTTP interface > [5591941d3258] core libvlc: Running vlc with the default interface. Use > 'cvlc' to use vlc without interface. > Qt: Session management error: Could not open network socket A quick internet search suggests that is caused by old sessions and cleaning them should help getting rid of this error. > libva info: VA-API version 0.40.0 > The X11 connection broke: I/O error (code 1) > XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" > after 11 requests (11 known processed) with 0 events remaining. > QObject::~QObject: Timers cannot be stopped from another thread > What I get is login prompt as if manually log-outed/rebooted. > > If I launch VLC without specifying (or clicking on) video file, itdisplays > it's GUI > without a crash. Does it happen only with that file or any video? > Meanwhile, Dragon player works fine. > > That video is downloaded form Youtube using Download Helper, with title > visible > in mentioned copy-paste. In any case, please attach vlc -vvv of a crashing run and I guess we'd also need the X server log. Please also tell us more about your hardware and if you use any propriety drivers. Cheers > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages vlc depends on: > ii vlc-bin 2.2.6-6 > ii vlc-l10n 2.2.6-6 > ii vlc-plugin-base 2.2.6-6 > ii vlc-plugin-qt2.2.6-6 > ii vlc-plugin-video-output 2.2.6-6 > > Versions of packages vlc recommends: > ii vlc-plugin-notify 2.2.6-6 > ii vlc-plugin-samba 2.2.6-6 > ii vlc-plugin-skins2 2.2.6-6 > ii vlc-plugin-video-splitter 2.2.6-6 > ii vlc-plugin-visualization 2.2.6-6 > > vlc suggests no packages. > > Versions of packages libvlc-bin depends on: > ii libc62.24-17 > ii libvlc5 2.2.6-6 > > Versions of packages libvlc5 depends on: > ii libc62.24-17 > ii libvlccore8 2.2.6-6 > > Versions of packages libvlc5 recommends: > ii libvlc-bin 2.2.6-6 > > Versions of packages libvlccore8 depends on: > ii libc62.24-17 > ii libdbus-1-3 1.11.20-1 > ii libidn11 1.33-2 > > Versions of packages libvlccore8 recommends: > ii libproxy-tools 0.4.14-3 > > Versions of packages vlc-bin depends on: > ii libc6 2.24-17 > ii libvlc-bin 2.2.6-6 > ii libvlc5 2.2.6-6 > > Versions of packages vlc-plugin-base depends on: > ii liba52-0.7.4 0.7.4-19 > ii libasound2 1.1.3-5 > ii libass91:0.13.7-2 > ii libavahi-client3 0.7-3 > ii libavahi-common3 0.7-3 > ii libavc1394-0 0.5.4-4+b1 > ii libbasicusageenvironment1 2017.09.12-1 > ii libbluray2 1:1.0.1.deb1-2 > ii libbz2-1.0 1.0.6-8.1 > ii libc6 2.24-17 > ii libcairo2 1.14.10-1 > ii libcddb2 1.3.2-5 > ii libcdio13 0.83-4.3+b1 > ii libchromaprint11.4.2-1 > ii libcrystalhd3 1:0.0~git20110715.fdd2f19-12 > ii libdbus-1-31.11.20-1 > ii libdc1394-22 2.2.5-1 > ii libdca00.0.5-10 > ii libdvbpsi101.3.1-2 > ii libdvdnav4 5.0.3-3 > ii libdvdread45.0.3-2 > ii libebml4v5 1.3.5-2 > ii libfaad2 2.8.5-1 > ii libflac8 1.3.2-1 > ii libfontconfig1 2.12.3-0.2 > ii libfreetype6 2.8-0.2 > ii libfribidi00.19.7-1+b1 > ii libgcc11:7.2.0-8 > ii libgcrypt201.7.9-1 > ii libglib2.0-0 2.54.1-1 > ii libgme00.6.1-1 > ii libgnutls303.5.15-2 > ii libgpg-error0 1.27-3 > ii libgroupsock8 2017.09.12-1 > ii libgsm11.0.13-4+b2 > ii libjpeg62-turbo1:1.5.2-2 > ii libkate1 0.4.1-7+b1 > ii liblirc-client00.10.0-2+b1 > ii liblivemedia58 2017.
Bug#877322: git-buildpackage autoremoval
Hi Ian, On Tue, Oct 17, 2017 at 02:57:33PM +0100, Ian Jackson wrote: > This bug means that the autoremoval robot wants to remove > git-buildpackage. I'm getting mails about it planning to remove dgit, > to clear the way. > > Do you intend to upload the docs change to sid soon ? Yes, before the autoremoval for sure. Sorry for being a pain here but I wanted to give gbp as much exposure as possible in experimental. Cheers, -- Guido > > Regards, > Ian. > > -- > Ian JacksonThese opinions are my own. > > If I emailed you from an address @fyvzl.net or @evade.org.uk, that is > a private address which bypasses my fierce spamfilter. >
Bug#878925: marked as done (Installation hangs on license)
Your message dated Tue, 17 Oct 2017 20:04:48 +0200 with message-id <47f5f426-aa74-4a88-c769-25e46c18b...@debian.org> and subject line closing: already fixed has caused the Debian Bug report #878925, regarding Installation hangs on license 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.) -- 878925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virtualbox-ext-pack Version: 5.1.30-1 Severity: serious I'm updating virtualbox-ext-pack from 5.1.28-1 to 5.1.30-1 during a dist- upgrade. virtualbox-ext-pack: downloading: http://download.virtualbox.org/virtualbox/5.1.30/Oracle_VM_VirtualBox_Extension_Pack-5.1.30.vbox- extpack The file will be downloaded into /usr/share/virtualbox-ext-pack VirtualBox Extension Pack Personal Use and Evaluation License (PUEL) License version 10, 20 July 2017 PLEASE READ THE FOLLOWING ORACLE VM VIRTUALBOX EXTENSION PACK PERSONAL USE AND EVALUATION LICENSE [...] This seems to hang here. There is a process spawned by apt which hangs on unfinished read(2): /usr/lib/virtualbox/VBoxManage extpack install --replace --accept- license=715c7246dc0f779ceab39446812362b2f9bf64a55ed5d3a905f053cfab36da9e Oracle_VM_VirtualBox_Extension_Pack-5.1.30.vbox-extpack -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox-ext-pack depends on: ii debconf [debconf-2.0] 1.5.64 iu virtualbox 5.1.30-dfsg-1 ii wget 1.19.1-4 virtualbox-ext-pack recommends no packages. virtualbox-ext-pack suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- already fixed in -2 thanks G. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#878889: marked as done (icu: recent security upload FTBFS on i386 and others with testsuite failure)
Your message dated Tue, 17 Oct 2017 18:05:05 + with message-id and subject line Bug#878889: fixed in icu 57.1-8 has caused the Debian Bug report #878889, regarding icu: recent security upload FTBFS on i386 and others with testsuite 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.) -- 878889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icu Version: 57.1-7 Severity: serious Justification: fails to build from source (but built successfully in the past) = ERRS: cintltst Makefile:83: recipe for target 'check-recursive' failed see https://buildd.debian.org/status/fetch.php?pkg=icu&arch=i386&ver=57.1-7&stamp=1508221550&raw=0 --- End Message --- --- Begin Message --- Source: icu Source-Version: 57.1-8 We believe that the bug you reported is fixed in the latest version of icu, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated icu 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: Tue, 17 Oct 2017 15:44:40 + Source: icu Binary: libicu57 libicu57-dbg libicu-dev icu-devtools icu-devtools-dbg icu-doc Architecture: source amd64 all Version: 57.1-8 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: icu-devtools - Development utilities for International Components for Unicode icu-devtools-dbg - Development utilities for International Components for Unicode (d icu-doc- API documentation for ICU classes and functions libicu-dev - Development files for International Components for Unicode libicu57 - International Components for Unicode libicu57-dbg - International Components for Unicode (debug symbols) Closes: 878889 Changes: icu (57.1-8) unstable; urgency=medium . * Disable self-test failure on x86 architectures due to French locale problems (closes: #878889). * Update Standards-Version to 4.1.1: - change libicu57-dbg priority to optional, - change icu-devtools-dbg priority to optional. * Update debhelper level to 10: - remove autotools-dev build dependency. Checksums-Sha1: 34bea8287e5c269d9292240c2841f26d1937d916 2085 icu_57.1-8.dsc 31dd148fc6c309bedc9db0be25ee566feee8fc90 33076 icu_57.1-8.debian.tar.xz e9e1dacd8556b347d6dfcc124c3fb2fa88243bbf 640300 icu-devtools-dbg_57.1-8_amd64.deb 89bed2a48960021fab2e0148c768ad151c5cc4d0 177260 icu-devtools_57.1-8_amd64.deb 4b57149ffc77024ca3ef4f1cc9fb4cdfb5bb130a 2394020 icu-doc_57.1-8_all.deb f94fb313821551eadd13e298c80d49f337d92329 7657 icu_57.1-8_amd64.buildinfo aa152ca2b24252344578511429a063ab8989d457 16575224 libicu-dev_57.1-8_amd64.deb 80bdf96542dd3b0b7ba7c5623d4e7101caad1708 7366888 libicu57-dbg_57.1-8_amd64.deb 278d7510b6c5b51940f7ded1a3e84b4d4d15934e 7699284 libicu57_57.1-8_amd64.deb Checksums-Sha256: 1c2b2f330ef095ad875a56b453c1f00bf560a04e8e9c9dce093024ee81908598 2085 icu_57.1-8.dsc ec594621cea01f69457cea01b4c19715f9952778bd217ea6cd0099975031fb4f 33076 icu_57.1-8.debian.tar.xz 3a324e808f30a8b5bf6a9628f0d31c62750be3beaf2ed678e8c63c422ec938ed 640300 icu-devtools-dbg_57.1-8_amd64.deb 22b2a435fd9efe61b01237774cbda2ce23d480297cd9219293122c7ec2e09536 177260 icu-devtools_57.1-8_amd64.deb b2b910d4f34018cf66353649d0e321c9fbbf67d811a2221de9167aec705390d7 2394020 icu-doc_57.1-8_all.deb 410bc968a01beb82292075653b85747e668e0dba558c8f1b7fcdac2c926b66e7 7657 icu_57.1-8_amd64.buildinfo 2814b1c89e9fe6839354159c501da42b26f25ee85386a0dd21a6a518d182cc4d 16575224 libicu-dev_57.1-8_amd64.deb ced97159e013c5da6b8f5d04a85836c06363c637e92a58dfb669dc3bc36348fd 7366888 libicu57-dbg_57.1-8_amd64.deb 1438266bfbd1e343dfa8236a2a23e935565d2040285d65dc946f096f03484c52 7699284 libicu57_57.1-8_amd64.deb Files: a8119e15c9608d25aee0a59ea43b7554 2085 libs optional icu_57.1-8.dsc 146848e62dfb4886be64f1e9737e1fef 33076
Bug#874521: 1.0.0
I've uploaded 1.0.0-1 into unstable recently. Although the patch that was submitted didn't work for you on top of 0.9.7, can you please check if the problem persists in 1.0.0? There have been other changes that may affect this. If not, please continue with debugging upstream.
Bug#878922: libbpfcc-dev does not depend on libbpfcc
Hello, Thanks for the bug report. On Tue, 2017-10-17 at 19:31 +0200, Alexander Kurtz wrote: > Please fix this by making libbpfcc-dev depend on libbpfcc. After installing the libbpfcc package manually, does it build proper ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#878925: Installation hangs on license
Package: virtualbox-ext-pack Version: 5.1.30-1 Severity: serious I'm updating virtualbox-ext-pack from 5.1.28-1 to 5.1.30-1 during a dist- upgrade. virtualbox-ext-pack: downloading: http://download.virtualbox.org/virtualbox/5.1.30/Oracle_VM_VirtualBox_Extension_Pack-5.1.30.vbox- extpack The file will be downloaded into /usr/share/virtualbox-ext-pack VirtualBox Extension Pack Personal Use and Evaluation License (PUEL) License version 10, 20 July 2017 PLEASE READ THE FOLLOWING ORACLE VM VIRTUALBOX EXTENSION PACK PERSONAL USE AND EVALUATION LICENSE [...] This seems to hang here. There is a process spawned by apt which hangs on unfinished read(2): /usr/lib/virtualbox/VBoxManage extpack install --replace --accept- license=715c7246dc0f779ceab39446812362b2f9bf64a55ed5d3a905f053cfab36da9e Oracle_VM_VirtualBox_Extension_Pack-5.1.30.vbox-extpack -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox-ext-pack depends on: ii debconf [debconf-2.0] 1.5.64 iu virtualbox 5.1.30-dfsg-1 ii wget 1.19.1-4 virtualbox-ext-pack recommends no packages. virtualbox-ext-pack suggests no packages. -- debconf-show failed
Processed: tagging 853348
Processing commands for cont...@bugs.debian.org: > tags 853348 + patch Bug #853348 [src:clementine] clementine: ftbfs with GCC-7 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 853348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878923: vlc: starting video crashes KDE session
Package: src:vlc Version: 2.2.6-6 Severity: grave Justification: renders package unusable Dear Maintainer, Probably after some recent package upgrades, I cannot launch video with VLC as it crashes whoe X session: LANG=en_US vlc ~/Parsiuntimai/David\ Stone\ Exceptional\ Performance_48_20.mp4 VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c) [5591942d8538] [http] lua interface: Lua HTTP interface [5591941d3258] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. Qt: Session management error: Could not open network socket libva info: VA-API version 0.40.0 The X11 connection broke: I/O error (code 1) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 11 requests (11 known processed) with 0 events remaining. QObject::~QObject: Timers cannot be stopped from another thread What I get is login prompt as if manually log-outed/rebooted. If I launch VLC without specifying (or clicking on) video file, it displays it's GUI without a crash. Meanwhile, Dragon player works fine. That video is downloaded form Youtube using Download Helper, with title visible in mentioned copy-paste. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vlc depends on: ii vlc-bin 2.2.6-6 ii vlc-l10n 2.2.6-6 ii vlc-plugin-base 2.2.6-6 ii vlc-plugin-qt2.2.6-6 ii vlc-plugin-video-output 2.2.6-6 Versions of packages vlc recommends: ii vlc-plugin-notify 2.2.6-6 ii vlc-plugin-samba 2.2.6-6 ii vlc-plugin-skins2 2.2.6-6 ii vlc-plugin-video-splitter 2.2.6-6 ii vlc-plugin-visualization 2.2.6-6 vlc suggests no packages. Versions of packages libvlc-bin depends on: ii libc62.24-17 ii libvlc5 2.2.6-6 Versions of packages libvlc5 depends on: ii libc62.24-17 ii libvlccore8 2.2.6-6 Versions of packages libvlc5 recommends: ii libvlc-bin 2.2.6-6 Versions of packages libvlccore8 depends on: ii libc62.24-17 ii libdbus-1-3 1.11.20-1 ii libidn11 1.33-2 Versions of packages libvlccore8 recommends: ii libproxy-tools 0.4.14-3 Versions of packages vlc-bin depends on: ii libc6 2.24-17 ii libvlc-bin 2.2.6-6 ii libvlc5 2.2.6-6 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-19 ii libasound2 1.1.3-5 ii libass91:0.13.7-2 ii libavahi-client3 0.7-3 ii libavahi-common3 0.7-3 ii libavc1394-0 0.5.4-4+b1 ii libbasicusageenvironment1 2017.09.12-1 ii libbluray2 1:1.0.1.deb1-2 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.24-17 ii libcairo2 1.14.10-1 ii libcddb2 1.3.2-5 ii libcdio13 0.83-4.3+b1 ii libchromaprint11.4.2-1 ii libcrystalhd3 1:0.0~git20110715.fdd2f19-12 ii libdbus-1-31.11.20-1 ii libdc1394-22 2.2.5-1 ii libdca00.0.5-10 ii libdvbpsi101.3.1-2 ii libdvdnav4 5.0.3-3 ii libdvdread45.0.3-2 ii libebml4v5 1.3.5-2 ii libfaad2 2.8.5-1 ii libflac8 1.3.2-1 ii libfontconfig1 2.12.3-0.2 ii libfreetype6 2.8-0.2 ii libfribidi00.19.7-1+b1 ii libgcc11:7.2.0-8 ii libgcrypt201.7.9-1 ii libglib2.0-0 2.54.1-1 ii libgme00.6.1-1 ii libgnutls303.5.15-2 ii libgpg-error0 1.27-3 ii libgroupsock8 2017.09.12-1 ii libgsm11.0.13-4+b2 ii libjpeg62-turbo1:1.5.2-2 ii libkate1 0.4.1-7+b1 ii liblirc-client00.10.0-2+b1 ii liblivemedia58 2017.09.12-1 ii liblua5.2-05.2.4-1.1+b2 ii liblzma5 5.2.2-1.3 ii libmad00.15.1b-8+b2 ii libmatroska6v5 1.4.8-1.1 ii libmp3lame03.99.5+repack1-9+b2 ii libmpcdec6 2:0.1~r495-1+b1 ii libmpeg2-4 0.5.1-8 ii libmtp91.1.13-1 ii libncursesw5 6.0+20170902-1 ii libogg01.3.2-1+b1 ii libopenmpt-modplug10.3.1-1 ii libopus0 1.2.1-1 ii libpng16-161.6.34-1 ii libpulse0 11.1-1 ii libraw1394-11 2.1.2-1+b1 ii libresid-builder0c2a 2.1.1-15 ii librsvg2-2 2.40.18-1 ii
Bug#878922: libbpfcc-dev does not depend on libbpfcc
Package: libbpfcc-dev
Version: 0.3.0-3
Severity: serious
Justification: Policy violation
Hi!
Debian Policy, section 8.4 ("Development files") [0] says:
Installing the development package must result in installation
of all the development files necessary for compiling programs
against that shared library.
However, libbpfcc-dev does not depend on libbpfcc. This makes
compilation fail, for example like this:
root@riga:~/alfwrapper# make
cc -std=gnu11 -Iinclude -O2 -Wall -Wextra -Werror --output='alfwrapper'
src/alfwrapper.c lib/bcc.c lib/die.c lib/env.c lib/pid.c lib/string.c
lib/cleanup.c lib/path.c lib/fd.c lib/parse.c lib/argv.c lib/socket.c -lbcc
/usr/bin/ld: cannot find -lbcc
collect2: error: ld returned 1 exit status
Makefile:9: recipe for target 'alfwrapper' failed
make: *** [alfwrapper] Error 1
root@riga:~/alfwrapper#
Please fix this by making libbpfcc-dev depend on libbpfcc.
Best regards
Alexander Kurtz
[0] https://www.debian.org/doc/debian-policy/#development-files
signature.asc
Description: This is a digitally signed message part
Bug#878919: libdpkg-perl needs Breaks: pkg-kde-tools (<< 0.15.28~)
Package: libdpkg-perl Version: 1.19.0.1 Severity: serious Due to #878892
Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"
On Tue, Oct 17, 2017 at 05:44:26PM +0200, gregor herrmann wrote:
> Package: dh-make-perl
> Version: 0.95
> Severity: serious
> Tags: buster sid
> Justification: fails to build from source
> As first seen on ci.debian.net, dh-make-perl's test suite fails with
> libdpkg-perl 1.19.0 and 1.19.0.1:
>
> Insecure dependency in eval while running with -T switch at
> /usr/share/perl5/Dpkg/Vendor.pm line 164.
> The -T seems to come from t/debian-version.t itself; no idea yet why
> it is a problem now and why it's used here in the first place.
It looks like Dpkg::Vendor::get_vendor_info() contents have become
tainted, probably due to changes in Dpkg::Control::HashCore. It used to
dig the values out with regexp captures but now uses split.
https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?h=sid&id=9e5e03e9a6ddf74bb22ffc5ea8794a14a592d6b6
A test case is
perl -T -MDpkg::Vendor=get_vendor_info -MScalar::Util=tainted -e 'die if
tainted get_vendor_info()->{Vendor}'
which dies on libdpkg-perl 1.19.0.1 but not 1.18.24.
I don't know if the earlier untainting was accidental or intended.
Copying the dpkg maintainers.
Hope this helps a bit,
--
Niko
Bug#878892: marked as done (dpkg-gensymbols: (subst) handling missing)
Your message dated Tue, 17 Oct 2017 17:04:58 +
with message-id
and subject line Bug#878892: fixed in pkg-kde-tools 0.15.28
has caused the Debian Bug report #878892,
regarding dpkg-gensymbols: (subst) handling missing
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.)
--
878892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.19.0.1
Severity: serious
Control: affects -1 src:libgc
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgc.html
...
dh_makeshlibs
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 7 in use)
Odd number of elements in hash assignment at
/usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204.
Odd number of elements in hash assignment at
/usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204.
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: no debian/symbols file used as basis for generating
debian/libgc1c2/DEBIAN/symbols
--- new_symbol_file (libgc1c2_1:7.4.2-8_amd64)
+++ dpkg-gensymbolsbROBiA 2018-11-19 08:40:18.674023442 -1200
@@ -647,7 +647,9 @@
libgccpp.so.1 libgc1c2 #MINVER#
_ZdaPv@Base 1:7.2d
_ZdlPv@Base 1:7.2d
- (subst)_Zna{size_t}@Base 1:7.2d
- (subst)_Znw{size_t}@Base 1:7.2d
+ _Znam@Base 1:7.4.2-8
+#MISSING: 1:7.4.2-8# (subst)_Zna{size_t}@Base 1:7.2d
+ _Znwm@Base 1:7.4.2-8
+#MISSING: 1:7.4.2-8# (subst)_Znw{size_t}@Base 1:7.2d
(arch=sparc sparc64)_etext@Base 1:7.2d
(arch=kfreebsd-amd64 kfreebsd-i386)etext@Base 1:7.2d
dh_makeshlibs: failing due to earlier errors
debian/rules:11: recipe for target 'binary' failed
make: *** [binary] Error 2
Works with 1.18.24
--- End Message ---
--- Begin Message ---
Source: pkg-kde-tools
Source-Version: 0.15.28
We believe that the bug you reported is fixed in the latest version of
pkg-kde-tools, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated pkg-kde-tools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 17 Oct 2017 19:52:53 +0300
Source: pkg-kde-tools
Binary: pkg-kde-tools libdlrestrictions1 libdlrestrictions-dev
Architecture: source
Version: 0.15.28
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Description:
libdlrestrictions-dev - development files for the DLRestrictions library
libdlrestrictions1 - library that implements library compatibility checks for
dlopen()
pkg-kde-tools - various packaging tools and scripts for KDE Applications
Closes: 878892
Changes:
pkg-kde-tools (0.15.28) unstable; urgency=medium
.
* Bump libdpkg-perl build-dependency too, to make the tests pass.
* Adapt to SymbolFile API changes in libdpkg-perl 1.19.0 (Closes: #878892).
Checksums-Sha1:
1b38f57d5939c1c5be9da8ed66fdd63998ef5501 2062 pkg-kde-tools_0.15.28.dsc
668036a50107a9656a61da001c5c806c63d33906 99404 pkg-kde-tools_0.15.28.tar.xz
10fe3357cab61018e3a61e5a07d00f7656423f4a 6330
pkg-kde-tools_0.15.28_source.buildinfo
Checksums-Sha256:
47f028b7eba6f52174528adbb9d6762bd3809279bae26851127b5f498de4a68c 2062
pkg-kde-tools_0.15.28.dsc
21f6398b9125c601b5d0ba1bf388ad2de72d1786ba6a0e3f03efda0e231f6260 99404
pkg-kde-tools_0.15.28.tar.xz
2e47ddbc71c0f8c760c12e9653cd9198eb0d82b87d3e884813b2af8d38bcfb0a 6330
pkg-kde-tools_0.15.28_source.buildinfo
Files:
e47e28352755ec275f667ef8ab776fd7 2062 devel optional pkg-kde-tools_0.15.28.dsc
c190b5235387bdf0c136cee37a3114d1 99404 devel optional
pkg-kde-tools_0.15.28.tar.xz
0a157e265e9009a26e1a07be7c3de7b6 6330 devel optional
pkg-kde-tools_0.15.28_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJHBAEBCgAxFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlnmNZYTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRDW/nEDY/hd0ymaD/0avX5Y7ovsDImutLwek7BD39VJcIvd
uyAHzd18cwEy7j5KDLYzhsc09OzU6fuPlOOz5s48CD0KGAKNlcE4qzlREa5tiRtX
KiqHwr+R/mSO3T1HLEcxvqekq0pCSfmDa4skn46ws0RJZSoMq
Bug#878912: docker.io: docker run fails saying that containerd-shim not installed
Package: docker.io Version: 1.13.1~ds2-3 Severity: grave Justification: renders package unusable On a completely up to date sid system: $ docker run -it --rm debian:sid docker: Error response from daemon: containerd-shim not installed on system. I tried to be a smart ass and symlink containerd-shim to docker-containerd-shim, only to have it fail differently. $ sudo ln -s /usr/bin/docker-containerd-shim /usr/bin/containerd-shim $ docker run -it --rm debian:sid docker: Error response from daemon: shim error: runc not installed on system. Right now docker does not work at all. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.116 ii docker-containerd 0.2.3+git+docker1.13.1~ds1-1 ii docker-runc 1.0.0~rc2+git+docker1.13.1~ds1-2 ii golang-libnetwork 0.8.0-dev.2+git20170202.599.45b4086-3 ii iptables1.6.1-2 ii libapparmor12.11.0-11 ii libc6 2.24-17 ii libdevmapper1.02.1 2:1.02.142-1 ii libsqlite3-03.20.1-2 ii libsystemd0 235-2 ii lsb-base9.20170808 Versions of packages docker.io recommends: ii ca-certificates 20170717 ii cgroupfs-mount 1.4 ii git 1:2.15.0~rc1-1 ii xz-utils 5.2.2-1.3 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs 4.12-1 ii debootstrap 1.0.91 pn docker-doc pn rinse pn zfs-fuse | zfsutils -- no debconf information signature.asc Description: PGP signature
Bug#878911: avahi FTBFS with debhelper 10.9.2
Source: avahi Version: 0.7-3 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avahi.html ... dh_systemd_start dh_systemd_start: Could not find "avahi-daemon.socket" in the /lib/systemd/system directory of avahi-dnsconfd. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless. dh_systemd_start: Cannot open(avahi-daemon.socket) for extracting the Also= line(s) debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 2 19:35 < nthykier> bunk: Ideally, avahi would fix this on their end. Without the fail-on-error, debhelper will silently "not do things" when the file is unreadable (even if only temporarily). I.e. a "fail-to-fail"-case
Processed: Version tracking fix
Processing commands for cont...@bugs.debian.org: > found 878892 0.15.25 Bug #878892 [pkg-kde-tools] dpkg-gensymbols: (subst) handling missing Marked as found in versions pkg-kde-tools/0.15.25. > thanks Stopping processing here. Please contact me if you need assistance. -- 878892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878892: dpkg-gensymbols: (subst) handling missing
Control: reassign -1 pkg-kde-tools 0.15.27 On Tue, Oct 17, 2017 at 05:30:24PM +0300, Adrian Bunk wrote: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgc.html > > ... > Odd number of elements in hash assignment at > /usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204. > Odd number of elements in hash assignment at > /usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204. > ... > dh_makeshlibs: failing due to earlier errors > debian/rules:11: recipe for target 'binary' failed > make: *** [binary] Error 2 Looks like pkgkde-symbolshelper needs to be updated for API changes in dpkg commit 0d2b3cee25b74dd3. I will fix this soon. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#878892: dpkg-gensymbols: (subst) handling missing
Processing control commands: > reassign -1 pkg-kde-tools 0.15.27 Bug #878892 [dpkg-dev] dpkg-gensymbols: (subst) handling missing Bug reassigned from package 'dpkg-dev' to 'pkg-kde-tools'. No longer marked as found in versions dpkg/1.19.0.1. Ignoring request to alter fixed versions of bug #878892 to the same values previously set Bug #878892 [pkg-kde-tools] dpkg-gensymbols: (subst) handling missing There is no source info for the package 'pkg-kde-tools' at version '0.15.27' with architecture '' Unable to make a source version for version '0.15.27' Marked as found in versions 0.15.27. -- 878892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878906: love must be package in each versioned,not only one version
Source: love Version: 0.9.1-4 Severity: serious every new mayor release of love, the compatibility are breack with old .. so installed games in system comes unusable! in conclusion: love engine in debian are not so used! so packaging seem are waste of time and resources if are no useless for the users so then, love must be offered in versioned! so even a only one package "love", we must provide "love09" and/or "love10" for love 0.9.X and 0.10.X It's been many years since LÖVE 0.9.X was released, and it's already on version 0.10.2, which is not fully compatible with 0.9.x. so if some user have a game with 0.9 working, and updated, the game will not work without reason event the user are a expert.. as example, golang are packaged in this way.. versioned! i'm mading my own work in venenux repository.. maybe need to track those changes Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot
Bernhard, could you try to run a git bisect to find the relevant change which broke fsck for you. https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log/disk-utils/fsck.c?h=stable/v2.30 There aren't that many changes for fsck. -- 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#870860: openjfx: CVE-2017-10086 CVE-2017-10114
Am 17.10.2017 um 17:20 schrieb Moritz Muehlenhoff: > On Tue, Oct 17, 2017 at 04:30:16PM +0200, Emmanuel Bourg wrote: >> I ran the Oracle JavaFX demos with the new version and it worked fine >> (except the media player but this isn't a regression, something is >> probably misconfigured on my machine). >> >> Should I proceed with the upload, or do you want to do it directly? > > Please go ahead with the upload. I'll also test this with mediathekview > (which is the only reverse dependency in stretch IIRC). Unfortunately > it's geoblocked, so one can't test unless you have a German IP address :-/ There are some streams that are not geoblocked and there is also ARTE.FR. :) signature.asc Description: OpenPGP digital signature
Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"
Package: dh-make-perl Version: 0.95 Severity: serious Tags: buster sid Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, dh-make-perl's test suite fails with libdpkg-perl 1.19.0 and 1.19.0.1: Insecure dependency in eval while running with -T switch at /usr/share/perl5/Dpkg/Vendor.pm line 164. Compilation failed in require at /usr/share/perl5/Dpkg/Control/Hash.pm line 25. BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Control/Hash.pm line 25. Compilation failed in require at /usr/share/perl5/Dpkg/Control.pm line 47. BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Control.pm line 47. Compilation failed in require at /usr/share/perl5/Dpkg/Source/Package.pm line 51. BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Source/Package.pm line 51. Compilation failed in require at /build/dh-make-perl-0.96/blib/lib/DhMakePerl/Config.pm line 15. BEGIN failed--compilation aborted at /build/dh-make-perl-0.96/blib/lib/DhMakePerl/Config.pm line 15. Compilation failed in require at /build/dh-make-perl-0.96/blib/lib/DhMakePerl.pm line 50. BEGIN failed--compilation aborted at /build/dh-make-perl-0.96/blib/lib/DhMakePerl.pm line 50. Compilation failed in require at t/debian-version.t line 5. BEGIN failed--compilation aborted at t/debian-version.t line 5. t/debian-version.t .. Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run The -T seems to come from t/debian-version.t itself; no idea yet why it is a problem now and why it's used here in the first place. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlnmJVpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgY0HBAAiO0zrOzykMoimHJ7qPtFG/4F4TY1xZu1IpLO9Nf/ey0yTZQx5qCwX7QU L+sSCHvdjYF4niDS0EgdHhYVB1AC5dAtEwSeeRzC9HQ0xLBtgagjisVmP2QQjfXu X3hf486O6nxvMeZxdpLV2VzyMSX5kNpEOie4gwgbyYtAUbsmIzLyGgGnjsR/bKJL N6c9eQmBSmfav6edVzjAf5rPNTA+pASCZ87hCKeaaI7It3KbkimJbhqnpDBkOOn9 5+rbhgkMmdiOSqi0WfJj437XsRyKpAIkPhivjbPUOkqv7gQg9J0JZpEuwkwYzQ4T dHd+n3jQlvS5PRpfY8PpZ+sUeP+7FETd9oIrFLTTcdMJi0UFZ2Yqp/eljWimgNWY ovQPuoQ9Fg3ykbPV17AwjJbsA0rr8ges4Vxoj2egAivVKxvdAQrAyLiqlaYdk0+Y fxRCho3/M29+z1pIhH6zLzlYAS9s26dtcIbJ9EAWCZoGiALXtZRJWp8jFanAK09N KlMQvUkVUVNPczWdv33eS9rBlqg3lwuAnm0yJHA6DPSxeJFczIUdtD1rugKBMyUx hTUZg0jEdk7vIEu1wMW52Ef7Py89E1tcoVodVsTlsg7UklrplU9mfUQqvQBi+6eO g/XATPDOE1/oVOWfr3V4Huc78LKHcKXpH1/yfbZFFYAmwpFYGIw= =yIT6 -END PGP SIGNATURE-
Bug#878899: dpkg-buildpackage no longer calls build, only binary
On Tue, Oct 17, 2017 at 06:03:20PM +0300, Adrian Bunk wrote:
> Package: dpkg-dev
> Version: 1.19.0.1
> Severity: serious
>
> 14:39 < _rene_> hmm. dpkg-dev 1.19.0.1 broken for anyone else? looks like it
> doesn't call build(-arch,indep) anymore at
> dpkg-buildpackage -b, but just binary?
>
> I seen the same debugging a FTBFS.
I believe this is caused by [0]:
[16:26:57] my understanding is that rules_requires_root is going
to be returning 0 for the build-* targets
[16:27:06] jrtc27: clearly the default tries to be binary-targets
which would preserve the original behaviour
[16:27:19] since $rules_requires_root{'binary-targets'} will be
set, but $target_legacy_root{'build'} will be false
[16:27:33] aha
[16:28:17] so I think the two instances of
rules_requires_root($buildtarget) should be rules_requires_root($binarytarget)
[16:28:33] jrtc27: thank you. so it should say "return if not
any_target_requires_root;" in build_target_fallback
[16:28:43] or that
[16:28:53] rules_requires_root('build') is correct to return 0
[16:28:58] build doesn't need root :P
[16:29:08] no package building today I guess
Regards,
James
[0]
https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=fca1bfe8406898105d1d724fb808f0cbcf985ae4
Bug#870860: openjfx: CVE-2017-10086 CVE-2017-10114
On Tue, Oct 17, 2017 at 04:30:16PM +0200, Emmanuel Bourg wrote: > I ran the Oracle JavaFX demos with the new version and it worked fine > (except the media player but this isn't a regression, something is > probably misconfigured on my machine). > > Should I proceed with the upload, or do you want to do it directly? Please go ahead with the upload. I'll also test this with mediathekview (which is the only reverse dependency in stretch IIRC). Unfortunately it's geoblocked, so one can't test unless you have a German IP address :-/ Cheers, Moritz
Bug#877672: [systemd] System Stalled at Pam-nologon
Control: severity -1 normal Due to lack of feedback I'm downgrading the severity to normal and will close the bug report in two weeks if no further information is provided. -- 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
Processed: Re: [systemd] System Stalled at Pam-nologon
Processing control commands: > severity -1 normal Bug #877672 [systemd] [systemd] System Stalled at Pam-nologon Severity set to 'normal' from 'critical' -- 877672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878632: marked as done (libfont-freetype-perl: FTBFS and Debci failure with libfreetype6 2.8.1-0.1)
Your message dated Tue, 17 Oct 2017 15:08:12 + with message-id and subject line Bug#878632: fixed in libfont-freetype-perl 0.07-2 has caused the Debian Bug report #878632, regarding libfont-freetype-perl: FTBFS and Debci failure with libfreetype6 2.8.1-0.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.) -- 878632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfont-freetype-perl Version: 0.07-1 Severity: serious Tags: buster sid https://ci.debian.net/packages/libf/libfont-freetype-perl/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libfont-freetype-perl.html ... Can't call method "bitmap" on an undefined value at t/20bitmap.t line 61, <$bmp_file> line 8. # Looks like your test exited with 25 just after 12. t/20bitmap.t ... 1..21 ok 1 - bdf format font, glyph 0020: bitmap image matches ok 2 - bdf format font, glyph 0020: bitmap starts 0 pixels to left of origin ok 3 - bdf format font, glyph 0020: bitmap starts 6 pixels above origin ok 4 - bdf format font, glyph 0041: bitmap image matches ok 5 - bdf format font, glyph 0041: bitmap starts 0 pixels to left of origin ok 6 - bdf format font, glyph 0041: bitmap starts 6 pixels above origin ok 7 - bdf format font, glyph 00FE: bitmap image matches ok 8 - bdf format font, glyph 00FE: bitmap starts 0 pixels to left of origin ok 9 - bdf format font, glyph 00FE: bitmap starts 6 pixels above origin ok 10 - bdf format font, glyph 2588: bitmap image matches ok 11 - bdf format font, glyph 2588: bitmap starts 0 pixels to left of origin ok 12 - bdf format font, glyph 2588: bitmap starts 6 pixels above origin Dubious, test returned 25 (wstat 6400, 0x1900) Failed 9/21 subtests ... Test Summary Report --- t/20bitmap.t (Wstat: 6400 Tests: 12 Failed: 0) Non-zero exit status: 25 Parse errors: Bad plan. You planned 21 tests but ran 12. Files=7, Tests=2595, 1 wallclock secs ( 0.32 usr 0.02 sys + 1.14 cusr 0.12 csys = 1.60 CPU) Result: FAIL Failed 1/7 test programs. 0/2595 subtests failed. Makefile:1038: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 --- End Message --- --- Begin Message --- Source: libfont-freetype-perl Source-Version: 0.07-2 We believe that the bug you reported is fixed in the latest version of libfont-freetype-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libfont-freetype-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Oct 2017 16:40:30 +0200 Source: libfont-freetype-perl Binary: libfont-freetype-perl Architecture: source Version: 0.07-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 802771 878632 Description: libfont-freetype-perl - module to read font files and render glyphs from Perl using FreeT Changes: libfont-freetype-perl (0.07-2) unstable; urgency=medium . * Team upload. . [ gregor herrmann ] * Fix typo in long description. Thanks to Dmitry Smirnov for the bug report. (Closes: #802771) . [ Salvatore Bonaccorso ] * debian/control: Use HTTPS transport protocol for Vcs-Git URI . [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. * Add patch from upstream pukk request for freetype6 2.8.1 compatibility. Thanks to Adrian Bunk for the bug report. (Closes: #878632) * Set bindnow linker flag in debian/rules. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.1.1. Checksums-Sha1: 9318e7b43747e78e3f9694e643f554ace08845bb 2332 libfont-freetype-perl_0.07-2.dsc a77f9e09c37886cd512394fb72a452242a06035e 5000 libfont-freetype-perl_0.07-2.debian.tar.xz Checksums-Sha256: ee47f3618b9cbf4979508b7a206940b3ab7ba68e3f5df8b93355c38c680f5b5d 2332 libfont-freetype-perl_0.07-2.dsc dfaa9a100b9d8af6aa00f677037460445ca726203b76699f08b4ea4692cda788 5000 libfont-freetype-perl_0.07-2.debia
Bug#876672: marked as done (e2fsprogs: FTBFS: Unknown package libblkid1-udeb given via -N/--no-package)
Your message dated Tue, 17 Oct 2017 15:05:46 + with message-id and subject line Bug#876551: fixed in e2fsprogs 1.43.7-1 has caused the Debian Bug report #876551, regarding e2fsprogs: FTBFS: Unknown package libblkid1-udeb given via -N/--no-package 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.) -- 876551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: e2fsprogs Version: 1.43.6-1 Severity: serious >From my pbuilder build log: ... dh_testdir dh_testroot dh_lintian mkdir -p /build/e2fsprogs-1.43.6/debian/libss2/usr/share/doc/libss2 mkdir -p /build/e2fsprogs-1.43.6/debian/ss-dev/usr/share/doc ln -sf libss2 /build/e2fsprogs-1.43.6/debian/ss-dev/usr/share/doc/ss-dev mkdir -p /build/e2fsprogs-1.43.6/debian/libcomerr2/usr/share/doc/libcomerr2 mkdir -p /build/e2fsprogs-1.43.6/debian/comerr-dev/usr/share/doc ln -sf libcomerr2 /build/e2fsprogs-1.43.6/debian/comerr-dev/usr/share/doc/comerr-dev mkdir -p /build/e2fsprogs-1.43.6/debian/e2fslibs/usr/share/doc/e2fslibs mkdir -p /build/e2fsprogs-1.43.6/debian/e2fslibs-dev/usr/share/doc ln -sf e2fslibs /build/e2fsprogs-1.43.6/debian/e2fslibs-dev/usr/share/doc/e2fslibs-dev dh_installdocs -Ne2fsprogs-udeb -Nlibblkid1-udeb -Nlibuuid1-udeb dh_installdocs: Unknown package libblkid1-udeb given via -N/--no-package, expected one of: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs dh_installdocs: Unknown package libuuid1-udeb given via -N/--no-package, expected one of: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs dh_installdocs: unknown option or error during option parsing; aborting debian/rules:372: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- Source: e2fsprogs Source-Version: 1.43.7-1 We believe that the bug you reported is fixed in the latest version of e2fsprogs, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Theodore Y. Ts'o (supplier of updated e2fsprogs 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: Mon, 16 Oct 2017 01:20:54 -0400 Source: e2fsprogs Binary: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs Architecture: source Version: 1.43.7-1 Distribution: unstable Urgency: medium Maintainer: Theodore Y. Ts'o Changed-By: Theodore Y. Ts'o Description: comerr-dev - common error description library - headers and static libraries e2fsck-static - statically-linked version of the ext2/ext3/ext4 filesystem checke e2fslibs - ext2/ext3/ext4 file system libraries e2fslibs-dev - ext2/ext3/ext4 file system libraries - headers and static librari e2fsprogs - ext2/ext3/ext4 file system utilities e2fsprogs-l10n - ext2/ext3/ext4 file system utilities - translations e2fsprogs-udeb - stripped-down versions of e2fsprogs, for debian-installer (udeb) fuse2fs- ext2 / ext3 / ext4 file system driver for FUSE libcomerr2 - common error description library libss2 - command-line interface parsing library ss-dev - command-line interface parsing library - headers and static libra Closes: 833514 873757 873812 873813 876551 878104 Changes: e2fsprogs (1.43.7-1) unstable; urgency=medium . * New upstream version * Fix error handling in debugfs, fuse2fs, and tune2fs so errors while replaying the journal will not cause a segfault in some corner cases * Fix resize2fs to avoid it from either failing or corrupting the file system image in certain corner cases when doing an off-line resize * Fix many spelling mistakes in various man pages, code comments, and program messages. * Fix e2fsck and debugfs so that maliciously corrupted file systems will not cause buffer overflows (Closes: #873757, #878104) * Update German translatio
Bug#876033: primusrun doesn't find libGL.so.1
Hello The new version of primus have arrived today in Testing, everything works but there is still a problem with the 32 bit version of LibGL.so.1. I have a couple of 32-bit only applications that I run with wine, they give me the following message: primus: fatal: failed to load any of the libraries: /usr/lib/x86_64-linux-gnu/ nvidia/libGL.so.1:/usr/lib/i386-linux-gnu/nvidia/libGL.so.1:/usr/lib/nvidia/ libGL.so.1 /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: wrong ELF class: ELFCLASS64 /usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No such file or directory /usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such file or directory Other 64 bit applications work with bumblebee as expected.
Bug#876551: marked as done (dh_installdocs: Unknown package libblkid1-udeb given via -N/--no-package)
Your message dated Tue, 17 Oct 2017 15:05:46 + with message-id and subject line Bug#876551: fixed in e2fsprogs 1.43.7-1 has caused the Debian Bug report #876551, regarding dh_installdocs: Unknown package libblkid1-udeb given via -N/--no-package 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.) -- 876551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: e2fsprogs Version: 1.43.6-1 Sources: https://packages.debian.org/source/sid/e2fsprogs Building with: dpkg-buildpackage --no-sign --build=binary leads to: ... dh_installdocs -Ne2fsprogs-udeb -Nlibblkid1-udeb -Nlibuuid1-udeb dh_installdocs: Unknown package libblkid1-udeb given via -N/--no-package, expected one of: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs dh_installdocs: Unknown package libuuid1-udeb given via -N/--no-package, expected one of: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs dh_installdocs: unknown option or error during option parsing; aborting debian/rules:372: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- Jean-Christophe Manciot --- End Message --- --- Begin Message --- Source: e2fsprogs Source-Version: 1.43.7-1 We believe that the bug you reported is fixed in the latest version of e2fsprogs, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Theodore Y. Ts'o (supplier of updated e2fsprogs 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: Mon, 16 Oct 2017 01:20:54 -0400 Source: e2fsprogs Binary: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs Architecture: source Version: 1.43.7-1 Distribution: unstable Urgency: medium Maintainer: Theodore Y. Ts'o Changed-By: Theodore Y. Ts'o Description: comerr-dev - common error description library - headers and static libraries e2fsck-static - statically-linked version of the ext2/ext3/ext4 filesystem checke e2fslibs - ext2/ext3/ext4 file system libraries e2fslibs-dev - ext2/ext3/ext4 file system libraries - headers and static librari e2fsprogs - ext2/ext3/ext4 file system utilities e2fsprogs-l10n - ext2/ext3/ext4 file system utilities - translations e2fsprogs-udeb - stripped-down versions of e2fsprogs, for debian-installer (udeb) fuse2fs- ext2 / ext3 / ext4 file system driver for FUSE libcomerr2 - common error description library libss2 - command-line interface parsing library ss-dev - command-line interface parsing library - headers and static libra Closes: 833514 873757 873812 873813 876551 878104 Changes: e2fsprogs (1.43.7-1) unstable; urgency=medium . * New upstream version * Fix error handling in debugfs, fuse2fs, and tune2fs so errors while replaying the journal will not cause a segfault in some corner cases * Fix resize2fs to avoid it from either failing or corrupting the file system image in certain corner cases when doing an off-line resize * Fix many spelling mistakes in various man pages, code comments, and program messages. * Fix e2fsck and debugfs so that maliciously corrupted file systems will not cause buffer overflows (Closes: #873757, #878104) * Update German translation (Closes: #833514) * Update debian policy version to 4.1.1 * Fix FTBFS caused by debhelper/10.9 and references to obsolete packages in the rules file (Closes: #876551) * Promote e2fsprogs-l10n from suggests to recommends (Closes: #873812) * Make e2fsprogs-l10n be arch:all (Closes: #873813) Checksums-Sha1: cd12334376f667a771bd627ddc33cdc5871cf49d 2328 e2fsprogs_1.43.7-1.dsc 8ecc75252d8fabd1b6e4f63fddb276ec11e787c4 7492811 e2fsprogs_1.43.7.orig.tar.gz 611d14707d3e98a7fd3e7d5e849077e68b96c90c 488 e2fsprogs_1.43.7.orig.tar.gz.asc 8f7749f87cdd6b6b6e6fb2e2352f8c15e3a7cb55 75428
Bug#878870: freetype 2.8.1 breaks font rendering
Le 17/10/17 à 13:22, Laurent Bigonville a écrit : Package: thunderbird,libfreetype6 Version: libfreetype6/2.8.1-0.1 Severity: serious Tags: patch fixed-upstream upstream Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1409188 Hi, freetype 2.8.1 breaks fonts when using subpixel rendering. This is already fixed in firefox[1], the same code is also present in thunderbird and I guess the same patch can be used there. Could you please have a look at fixing thunderbird? FTR, the mentioned patch is already in 52.4.0 that has been released the 4th of October. Regards, Laurent Bigonville [1] https://hg.mozilla.org/releases/mozilla-release/rev/8fe8227e5080
Bug#878899: dpkg-buildpackage no longer calls build, only binary
Package: dpkg-dev Version: 1.19.0.1 Severity: serious 14:39 < _rene_> hmm. dpkg-dev 1.19.0.1 broken for anyone else? looks like it doesn't call build(-arch,indep) anymore at dpkg-buildpackage -b, but just binary? I seen the same debugging a FTBFS.
Bug#878896: liquidsoap with OCaml 4.05.0
Source: liquidsoap Version: 1.1.1-7.2 Severity: serious Tags: buster sid https://buildd.debian.org/status/package.php?p=liquidsoap&suite=sid ... OCAMLOPT -c stream/generator.mli OCAMLOPT -c stream/generator.ml OCAMLOPT -c stream/aFrame.mli OCAMLOPT -c stream/aFrame.ml OCAMLOPT -c decoder/decoder.mli OCAMLOPT -c request.mli OCAMLOPT -c source.mli OCAMLOPT -c stream/vFrame.mli OCAMLOPT -c stream/vFrame.ml OCAMLOPT -c stream/mFrame.mli OCAMLOPT -c stream/mFrame.ml OCAMLOPT -c decoder/decoder.ml File "decoder/decoder.ml", line 280, characters 10-14: Error: Multiple definition of the extension constructor name Exit. Names must be unique in a given structure or signature. ../Makefile.rules:192: recipe for target 'decoder/decoder.cmx' failed make[3]: *** [decoder/decoder.cmx] Error 2
Processed: Pending fixes for bugs in the libfont-freetype-perl package
Processing commands for cont...@bugs.debian.org: > tag 878632 + pending Bug #878632 [src:libfont-freetype-perl] libfont-freetype-perl: FTBFS and Debci failure with libfreetype6 2.8.1-0.1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 878632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878632: Pending fixes for bugs in the libfont-freetype-perl package
tag 878632 + pending thanks Some bugs in the libfont-freetype-perl package are closed in revision 52bc083ac863609c2f74dc90ec3538153b1e021b in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libfont-freetype-perl.git/commit/?id=52bc083 Commit message: Add patch from upstream pukk request for freetype6 2.8.1 compatibility. Thanks: Adrian Bunk for the bug report. Closes: #878632
Bug#870860: openjfx: CVE-2017-10086 CVE-2017-10114
I ran the Oracle JavaFX demos with the new version and it worked fine (except the media player but this isn't a regression, something is probably misconfigured on my machine). Should I proceed with the upload, or do you want to do it directly? Emmanuel Bourg
Processed: dpkg-gensymbols: (subst) handling missing
Processing control commands: > affects -1 src:libgc Bug #878892 [dpkg-dev] dpkg-gensymbols: (subst) handling missing Added indication that 878892 affects src:libgc -- 878892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878892: dpkg-gensymbols: (subst) handling missing
Package: dpkg-dev
Version: 1.19.0.1
Severity: serious
Control: affects -1 src:libgc
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgc.html
...
dh_makeshlibs
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 7 in use)
Odd number of elements in hash assignment at
/usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204.
Odd number of elements in hash assignment at
/usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm line 204.
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: no debian/symbols file used as basis for generating
debian/libgc1c2/DEBIAN/symbols
--- new_symbol_file (libgc1c2_1:7.4.2-8_amd64)
+++ dpkg-gensymbolsbROBiA 2018-11-19 08:40:18.674023442 -1200
@@ -647,7 +647,9 @@
libgccpp.so.1 libgc1c2 #MINVER#
_ZdaPv@Base 1:7.2d
_ZdlPv@Base 1:7.2d
- (subst)_Zna{size_t}@Base 1:7.2d
- (subst)_Znw{size_t}@Base 1:7.2d
+ _Znam@Base 1:7.4.2-8
+#MISSING: 1:7.4.2-8# (subst)_Zna{size_t}@Base 1:7.2d
+ _Znwm@Base 1:7.4.2-8
+#MISSING: 1:7.4.2-8# (subst)_Znw{size_t}@Base 1:7.2d
(arch=sparc sparc64)_etext@Base 1:7.2d
(arch=kfreebsd-amd64 kfreebsd-i386)etext@Base 1:7.2d
dh_makeshlibs: failing due to earlier errors
debian/rules:11: recipe for target 'binary' failed
make: *** [binary] Error 2
Works with 1.18.24
Processed: rdkit: diff for NMU version 201603.5-2.1
Processing control commands: > tags 872246 + patch Bug #872246 [src:rdkit] rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk Added tag(s) patch. > tags 872246 + pending Bug #872246 [src:rdkit] rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk Added tag(s) pending. -- 872246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872246: rdkit: diff for NMU version 201603.5-2.1
Control: tags 872246 + patch Control: tags 872246 + pending Dear maintainer, I've prepared an NMU for rdkit (versioned as 201603.5-2.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru rdkit-201603.5/debian/changelog rdkit-201603.5/debian/changelog --- rdkit-201603.5/debian/changelog 2016-11-07 14:16:00.0 +0200 +++ rdkit-201603.5/debian/changelog 2017-10-17 16:38:20.0 +0300 @@ -1,3 +1,12 @@ +rdkit (201603.5-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add the build dependency on latexmk required with Sphinx 1.6. +(Closes: #872246) + * Fix a typo in the package descriptions. + + -- Adrian Bunk Tue, 17 Oct 2017 16:38:20 +0300 + rdkit (201603.5-2) unstable; urgency=medium * Team upload. diff -Nru rdkit-201603.5/debian/control rdkit-201603.5/debian/control --- rdkit-201603.5/debian/control 2016-11-07 13:50:00.0 +0200 +++ rdkit-201603.5/debian/control 2017-10-17 16:38:20.0 +0300 @@ -22,6 +22,7 @@ python-numpy, python-pandas, python-sphinx, + latexmk, texlive-fonts-recommended, texlive-generic-extra, texlive-latex-base, @@ -60,7 +61,7 @@ * Chirality support, including calculation of (R/S) stereochemistry codes * 2D pharmacophore searching * Fingerprinting, including Daylight-like, atom pairs, topological -torsions, Morgan alogrithm and MACCS keys +torsions, Morgan algorithm and MACCS keys * Calculation of shape similarity * Multi-molecule maximum common substructure * Machine-learning via clustering and information theory algorithms @@ -109,7 +110,7 @@ * Chirality support, including calculation of (R/S) stereochemistry codes * 2D pharmacophore searching * Fingerprinting, including Daylight-like, atom pairs, topological -torsions, Morgan alogrithm and MACCS keys +torsions, Morgan algorithm and MACCS keys * Calculation of shape similarity * Multi-molecule maximum common substructure * Machine-learning via clustering and information theory algorithms @@ -141,7 +142,7 @@ * Chirality support, including calculation of (R/S) stereochemistry codes * 2D pharmacophore searching * Fingerprinting, including Daylight-like, atom pairs, topological -torsions, Morgan alogrithm and MACCS keys +torsions, Morgan algorithm and MACCS keys * Calculation of shape similarity * Multi-molecule maximum common substructure * Machine-learning via clustering and information theory algorithms
Bug#877322: git-buildpackage autoremoval
This bug means that the autoremoval robot wants to remove git-buildpackage. I'm getting mails about it planning to remove dgit, to clear the way. Do you intend to upload the docs change to sid soon ? Regards, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#869013: marked as done (sisu-guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)
Your message dated Tue, 17 Oct 2017 15:52:34 +0200 with message-id and subject line Re: sisu-guice FTBFS: Sisu Guice - Core Library FAILURE has caused the Debian Bug report #868611, regarding sisu-guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sisu-guice Version: 3.2.6-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170719 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_testdir -O--buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No > such file or directory > find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': > No such file or directory > find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': > No such file or directory > mh_patchpoms -plibsisu-guice-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests > -Dnotimestamp=true -Dlocale=en_US > [[1;34mINFO[m] Scanning for projects... > [[1;33mWARNING[m] > [[1;33mWARNING[m] Some problems were encountered while building the > effective model for org.sonatype.sisu.inject:guice-testlib:jar:3.2.6 > [[1;33mWARNING[m] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-surefire-plugin is missing. @ > org.sonatype.sisu.inject:guice-testlib:[unknown-version], > /<>/extensions/testlib/pom.xml, line 18, column 15 > [[1;33mWARNING[m] > [[1;33mWARNING[m] It is highly recommended to fix these problems because > they threaten the stability of your build. > [[1;33mWARNING[m] > [[1;33mWARNING[m] For this reason, future Maven versions might no longer > support building such malformed projects. > [[1;33mWARNING[m] > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] [1mReactor Build Order:[m > [[1;34mINFO[m] > [[1;34mINFO[m] Sisu Guice > [[1;34mINFO[m] Sisu Guice - Bill of Materials > [[1;34mINFO[m] Sisu Guice - Core Library > [[1;34mINFO[m] Sisu Guice - Extensions > [[1;34mINFO[m] Sisu Guice - Extensions - AssistedInject > [[1;34mINFO[m] Sisu Guice - Extensions - TestLib > [[1;34mINFO[m] > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] [1mBuilding Sisu Guice 3.2.6[m > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] [1mBuilding Sisu Guice - Bill of Materials 3.2.6[m > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] [1mBuilding Sisu Guice - Core Library 3.2.6[m > [[1;34mINFO[m] > [1m[m > [[1;34mINFO[m] > [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m > [1m(default-resources)[m @ [36msisu-guice[0;1m ---[m > [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources. > [[1;34mINFO[m] Copying 0 resource > [[1;34mINFO[m] > [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m > [1m(default-compile)[m @ [36msisu-guice[0;1m ---[m > [[1;33mWARNING[m] The POM for > org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive
Bug#868611: marked as done (sisu-guice FTBFS: Sisu Guice - Core Library FAILURE)
Your message dated Tue, 17 Oct 2017 15:52:34 +0200 with message-id and subject line Re: sisu-guice FTBFS: Sisu Guice - Core Library FAILURE has caused the Debian Bug report #868611, regarding sisu-guice FTBFS: Sisu Guice - Core Library 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.) -- 868611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sisu-guice Version: 3.2.6-3 Severity: serious Tags: buster sid Some recent change in unstable makes sisu-guice FTBFS: https://tests.reproducible-builds.org/debian/history/sisu-guice.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sisu-guice.html ... dh_auto_build -O--buildsystem=maven /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/sisu-guice-3.2.6 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/1st/sisu-guice-3.2.6/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/sisu-guice-3.2.6/debian -Dmaven.repo.local=/build/1st/sisu-guice-3.2.6/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US [[1;34mINFO[m] Scanning for projects... [[1;33mWARNING[m] [[1;33mWARNING[m] Some problems were encountered while building the effective model for org.sonatype.sisu.inject:guice-testlib:jar:3.2.6 [[1;33mWARNING[m] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. @ org.sonatype.sisu.inject:guice-testlib:[unknown-version], /build/1st/sisu-guice-3.2.6/extensions/testlib/pom.xml, line 18, column 15 [[1;33mWARNING[m] [[1;33mWARNING[m] It is highly recommended to fix these problems because they threaten the stability of your build. [[1;33mWARNING[m] [[1;33mWARNING[m] For this reason, future Maven versions might no longer support building such malformed projects. [[1;33mWARNING[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mReactor Build Order:[m [[1;34mINFO[m] [[1;34mINFO[m] Sisu Guice [[1;34mINFO[m] Sisu Guice - Bill of Materials [[1;34mINFO[m] Sisu Guice - Core Library [[1;34mINFO[m] Sisu Guice - Extensions [[1;34mINFO[m] Sisu Guice - Extensions - AssistedInject [[1;34mINFO[m] Sisu Guice - Extensions - TestLib [[1;34mINFO[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mBuilding Sisu Guice 3.2.6[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mBuilding Sisu Guice - Bill of Materials 3.2.6[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mBuilding Sisu Guice - Core Library 3.2.6[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:2.6:resources[m [1m(default-resources)[m @ [36msisu-guice[0;1m ---[m [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources. [[1;34mINFO[m] Copying 0 resource [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m [1m(default-compile)[m @ [36msisu-guice[0;1m ---[m [[1;33mWARNING[m] The POM for org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [[1;33mWARNING[m] The POM for org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [[1;34mINFO[m] Changes detected - recompiling the module! [[1;34mINFO[m] Compiling 193 source files to /build/1st/sisu-guice-3.2.6/core/target/classes [[1;34mINFO[m] /build/1st/sisu-guice-3.2.6/core/src/com/google/inject/internal/BindingImpl.java: Some input files use or override a deprecated API. [[1;34mINFO[m] /build/1st/sisu-guice-3.2.6/core/src/com/google/inject/internal/BindingImpl.java: Recompile with -Xli
Bug#878889: icu: recent security upload FTBFS on i386 and others with testsuite failure
On Tue, Oct 17, 2017 at 3:32 PM, Thorsten Glaser wrote: > Source: icu > Version: 57.1-7 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > = ERRS: cintltst > Makefile:83: recipe for target 'check-recursive' failed > > see > https://buildd.debian.org/status/fetch.php?pkg=icu&arch=i386&ver=57.1-7&stamp=1508221550&raw=0 Thanks. I do follow the build process of my uploads, especially if it's a security related one. You are the third to ping me about it. :) Fix is on the way and will be uploaded once I'm at home from work. Regards, Laszlo/GCS
Processed: fixed 841412 in 4:5.6.0-3
Processing commands for cont...@bugs.debian.org:
> fixed 841412 4:5.6.0-3
Bug #841412 {Done: Adrian Bunk } [src:digikam] digikam: FTBFS:
error with opencv 3.1
Marked as fixed in versions digikam/4:5.6.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
841412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 841412 in 5.6.0-3
Processing commands for cont...@bugs.debian.org:
> fixed 841412 5.6.0-3
Bug #841412 {Done: Adrian Bunk } [src:digikam] digikam: FTBFS:
error with opencv 3.1
The source 'digikam' and version '5.6.0-3' do not appear to match any binary
packages
Marked as fixed in versions digikam/5.6.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
841412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot
On 10/17/2017 2:42 AM, Bernhard Schmidt wrote:
> close(3)= 0
> open("/home", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXECstrace: Process 1677
> detached
>
So it hangs in a call to open() on /home? That looks like a kernel bug.
Is /home mounted at the time, or is it just the container directory in
your root filesystem? If it is the latter then you may want to run
e2fsck -f on your root filesystem.
Bug#878889: icu: recent security upload FTBFS on i386 and others with testsuite failure
Source: icu Version: 57.1-7 Severity: serious Justification: fails to build from source (but built successfully in the past) = ERRS: cintltst Makefile:83: recipe for target 'check-recursive' failed see https://buildd.debian.org/status/fetch.php?pkg=icu&arch=i386&ver=57.1-7&stamp=1508221550&raw=0
Bug#878883: stoken FTBFS with libtomcrypt 1.18
Source: stoken Version: 0.91-1 Severity: serious Tags: buster sid https://buildd.debian.org/status/package.php?p=stoken&suite=sid ... src/stc-tomcrypt.c: In function 'stc_rsa_sha1_sign_digest': src/stc-tomcrypt.c:193:9: error: 'LTC_LTC_PKCS_1_V1_5' undeclared (first use in this function); did you mean 'LTC_PKCS_1_V1_5'? LTC_LTC_PKCS_1_V1_5, NULL, 0, ^~~ LTC_PKCS_1_V1_5 src/stc-tomcrypt.c:193:9: note: each undeclared identifier is reported only once for each function it appears in Makefile:951: recipe for target 'src/libstoken_la-stc-tomcrypt.lo' failed make[2]: *** [src/libstoken_la-stc-tomcrypt.lo] Error 1
Bug#878852: Remove postgresql-9.6 from testing
Re: To Debian Bug Tracking System 2017-10-17 <20171017091121.565iurh4mohq7...@msg.df7cb.de> > There's a few dependencies that are updated in unstable, but have not > transitioned yet: > postgresql-mysql-fdw > orafce > postgresql-pllua > > Waiting for NEW processing: > pgextwlist pgextwlist has just passed NEW, so would need an urgency bump as well. Christoph
Bug#709198: marked as done (debconf: should not use python in maintainer scripts)
Your message dated Tue, 17 Oct 2017 12:00:11 + with message-id and subject line Bug#709198: fixed in debconf 1.5.64 has caused the Debian Bug report #709198, regarding debconf: should not use python in maintainer scripts 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.) -- 709198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: upgrade-reports Severity: grave Justification: renders package unusable Broken Python upgrade left me without working debconf. Full log at http://paste.debian.net/5060/ Fixed by manually installing libc6 packages and locales*.deb Fetched 520 MB in 21min 17s (407 kB/s) Reading changelogs... Done apt-listchanges: Mailing root: apt-listchanges: news for rockhopper Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 212752 files and directories currently installed.) Preparing to replace libpython2.7 2.7.3-8 (using /libpython2.7_2.7.5-2_i386.deb) ... Unpacking replacement libpython2.7 ... Preparing to replace python2.7 2.7.3-8 (using /python2.7_2.7.5-2_i386.deb) ... Unpacking replacement python2.7 ... Preparing to replace python2.7-minimal 2.7.3-8 (using /python2.7-minimal_2.7.5-2_i386.deb) ... Unpacking replacement python2.7-minimal ... dpkg: warning: unable to delete old directory '/etc/python2.7': Directory not empty Selecting previously unselected package libpython2.7-minimal. Unpacking libpython2.7-minimal (from /libpython2.7-minimal_2.7.5-2_i386.deb) ... Preparing to replace mime-support 3.52-2 (using /mime-support_3.54_all.deb) ... Unpacking replacement mime-support ... Preparing to replace debconf 1.5.49 (using .../debconf_1.5.50_all.deb) /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.16' not found (required by /usr/bin/python) dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.16' not found (required by /usr/bin/python) dpkg: error processing /var/cache/apt/archives/debconf_1.5.50_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) /usr/bin/python: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.16' not found (required by /usr/bin/python) dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Processing triggers for desktop-file-utils ... Errors were encountered while processing: /var/cache/apt/archives/debconf_1.5.50_all.deb -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.7-trunk-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: debconf Source-Version: 1.5.64 We believe that the bug you reported is fixed in the latest version of debconf, 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 709...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated debconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Oct 2017 11:52:50 +0100 Source: debconf Binary: debconf debconf-i18n debconf-doc debconf-utils python-debconf python3-debconf Architecture: source all Version: 1.5.64 Distribution: unstable Urgency: medium Maintainer: Debconf Developers Changed-By: Colin Watson Description: debconf- Debian configuration management system debconf-doc - debconf documentation debconf-i18n - full internationali
