Bug#965164: policykit-1: fails to install
Package: policykit-1 Version: 0.105-27 Followup-For: Bug #965164 I confirm the bug. I did a dist-up anyway. Now, no sound via pulseaudio, mocp in/decreasing volume not working, cmus won't play audio files... Not sure what kind of info i can provide :) Cheers " apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up policykit-1 (0.105-27) ... chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file or directory dpkg: error processing package policykit-1 (--configure): installed policykit-1 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: policykit-1 Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) " -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages policykit-1 depends on: ii dbus 1.12.20-1 ii libc62.31-1 ii libexpat12.2.9-1 ii libglib2.0-0 2.64.4-1 ii libpam-systemd [logind] 245.6-3 ii libpam0g 1.3.1-5 ii libpolkit-agent-1-0 0.105-27 ii libpolkit-gobject-1-00.105-27 ii libsystemd0 245.6-3 policykit-1 recommends no packages. policykit-1 suggests no packages. Versions of packages policykit-1 is related to: pn elogind pn libpam-elogind ii libpam-systemd 245.6-3 ii systemd 245.6-3 -- no debconf information
Bug#961811: baresip: diff for NMU version 0.6.1-1.1
Hi On 2020-07-17 00:02:17 +0100, peter green wrote: > (note: I am not the maintainer) > Sebastian Ramacher wrote: > > I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and > > uploaded it to DELAYED/2. > > While I have not tested, I am 99% sure your fix for make 4.3 will break the > build with make 4.2 in testing. > > Since I wrote the post in response to your proposed gst-plugins-bad1.0 NMU I > have done some more searching, > and apparently the solution to this is to use a variable. > https://lwn.net/Articles/826217/ > > I applied that technique and was able to get succesful builds in both > raspbian bullseye-staging and Debian > sid. A debdiff of what I uploaded to raspbian is attatched. Please feel free to cancel my NMU and upload your's instead. Cheers > diff -Nru baresip-0.6.1/debian/changelog baresip-0.6.1/debian/changelog > --- baresip-0.6.1/debian/changelog2019-02-18 12:30:38.0 + > +++ baresip-0.6.1/debian/changelog2020-07-16 19:44:03.0 + > @@ -1,3 +1,16 @@ > +baresip (0.6.1-1+rpi1) bullseye-staging; urgency=medium > + > + * Raspbian upload based on Sebastian Ramacher's proposed NMU > + [Sebastian Ramacher] > + * debian/patches: > +- Unbreak patch 1002 with make 4.3 (Closes: #961811) > +- Apply upstream patch to fix build of selftest > + [Peter Michael Green] > + * Further adjust patch 1002 so it is compatible with both make 4.2 > (bullseye) > +and make 4.3 (sid) > + > + -- Peter Michael Green Thu, 16 Jul 2020 19:44:03 > + > + > baresip (0.6.1-1) unstable; urgency=medium > >[ upstream ] > diff -Nru baresip-0.6.1/debian/patches/1002_system_header_locations.patch > baresip-0.6.1/debian/patches/1002_system_header_locations.patch > --- baresip-0.6.1/debian/patches/1002_system_header_locations.patch > 2019-02-11 19:42:25.0 + > +++ baresip-0.6.1/debian/patches/1002_system_header_locations.patch > 2020-07-16 19:37:33.0 + > @@ -14,15 +14,29 @@ > Last-Update: 2018-11-29 > --- > This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ > a/mk/modules.mk > -+++ b/mk/modules.mk > -@@ -67,46 +67,36 @@ > +Index: baresip-0.6.1/mk/modules.mk > +=== > +--- baresip-0.6.1.orig/mk/modules.mk > baresip-0.6.1/mk/modules.mk > +@@ -59,6 +59,11 @@ > + # Default is enabled > + MOD_AUTODETECT := 1 > + > ++# GNU make 4.3 changes the escaping rules for the hash sign, the reccomended > ++# way to maintain compatibility with both 4.2 and 4.3 is to use a variable > ++# see https://lwn.net/Articles/810071/ > ++HASHINCLUDE:=\#include > ++ > + ifneq ($(MOD_AUTODETECT),) > + > + USE_CONS := 1 > +@@ -67,46 +72,36 @@ USE_L16 := 1 > > ifneq ($(OS),win32) > > -USE_ALSA := $(shell [ -f $(SYSROOT)/include/alsa/asoundlib.h ] || \ > -[ -f $(SYSROOT_ALT)/include/alsa/asoundlib.h ] && echo "yes") > -+USE_ALSA := $(shell echo '\#include ' | \ > ++USE_ALSA := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > +USE_AMR := $(shell pkg-config --exists opencore-amrnb && echo "yes") > +ifeq ($(USE_AMR),) > @@ -39,9 +53,9 @@ > -[ -f $(SYSROOT)/include/$(MACHINE)/libavformat/avformat.h ] || \ > -[ -f $(SYSROOT_ALT)/include/libavformat/avformat.h ] && echo "yes") > +endif > -+USE_AVCODEC := $(shell echo '\#include ' | \ > ++USE_AVCODEC := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_AVFORMAT := $(shell echo '\#include ' | \ > ++USE_AVFORMAT := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > USE_AVAHI := $(shell pkg-config --exists avahi-client && echo "yes") > -USE_BV32 := $(shell [ -f $(SYSROOT)/include/bv32/bv32.h ] || \ > @@ -69,26 +83,26 @@ > -[ -f $(SYSROOT)/include/gsm/gsm.h ] || \ > -[ -f $(SYSROOT)/local/include/gsm.h ] || \ > -[ -f $(SYSROOT)/local/include/gsm/gsm.h ] && echo "yes") > -+USE_BV32 := $(shell echo '\#include ++USE_BV32 := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_CAIRO := $(shell echo '\#include ' |\ > ++USE_CAIRO := $(shell echo '$(HASHINCLUDE) ' |\ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_DTLS := $(shell echo '\#include ' | \ > ++USE_DTLS := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_DTLS_SRTP := $(shell echo '\#include ' | \ > ++USE_DTLS_SRTP := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_G722 := $(shell echo '\#include ' | \ > ++USE_G722 := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_G722_1 := $(shell echo '\#include ' | \ > ++USE_G722_1 := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null 2>&1 && echo yes) > -+USE_G726 := $(shell echo '\#include ' | \ > ++USE_G726 := $(shell echo '$(HASHINCLUDE) ' | \ > +$(CC) -E - >/dev/null
Bug#965168: mysql-5.7: Security fixes from the July 2020 CPU
Source: mysql-5.7 Version: 5.7.26-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Hi See https://www.oracle.com/security-alerts/cpujul2020.html#AppendixMSQL for a list of CVEs affecting src:mysql-5.7. Regards, Salvatore
Bug#937397: marked as done (pycairo: Python2 removal in sid/bullseye)
Your message dated Fri, 17 Jul 2020 04:18:44 + with message-id and subject line Bug#937397: fixed in pycairo 1.16.2-4 has caused the Debian Bug report #937397, regarding pycairo: Python2 removal in sid/bullseye 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.) -- 937397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pycairo Version: 1.16.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pycairo If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pycairo Source-Version: 1.16.2-4 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of pycairo, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pycairo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 16 Jul 2020 23:49:54 -0400 Source: pycairo Architecture: source Version: 1.16.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937397 Changes: pycairo (1.16.2-4) unstable; urgency=medium . * Drop python2 support; Closes: #937397 Checksums-Sha1: 2b4550602b837befed889d71f275a307d6493846 2345 pycairo_1.16.2-4.dsc c239626e6f94000979bbf6762ecb41c2b2d7837c 15040 pycairo_1.16.2-4.debian.tar.xz b756373d0f2a6221aa09b654fc81c558be5fa6b0 10199 pycairo_1.16.2-4_source.buildinfo Checksums-Sha256: a4f81494a3987495962b9ea3b3c12de0ecd93316b472b749b47ad8ae34b1a4c7 2345 pycairo_1.16.2-4.dsc b64287fd881bc1a5d72bbea6a06577a7c55612948e26f26182f97c9ce542e9d6 15040 pycairo_1.16.2-4.debian.tar.xz bcbb61df430789797e26ce2dba2a5cfa759da189082f1c267bf18ec6567cda47 10199 pycairo_1.16.2-4_source.buildinfo Files: 8a8e745777d7aa696c54b7e774f85165 2345 python optional pycairo_1.16.2-4.dsc
Bug#937397: marked as pending in pycairo
Control: tag -1 pending Hello, Bug #937397 in pycairo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pycairo/-/commit/dbde254bdfaf0df046982215dd5f65b879391200 Drop python2 support; Closes: #937397 (this message was generated automatically) -- Greetings https://bugs.debian.org/937397
Processed: Bug#937397 marked as pending in pycairo
Processing control commands: > tag -1 pending Bug #937397 [src:pycairo] pycairo: Python2 removal in sid/bullseye Added tag(s) pending. -- 937397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-07-17 03:34:23.546032+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-cairo is a module and has 0 external rdeps or not in testing > # python-cairo-dev is a module and has 0 external rdeps or not in testing > severity 937397 serious Bug #937397 [src:pycairo] pycairo: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965164: policykit-1: fails to install
Package: policykit-1 Version: 0.105-27 Severity: grave Justification: renders package unusable On install: Setting up policykit-1 (0.105-27) ... chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file or directory > dpkg -L policykit-1 | grep help /usr/libexec/polkit-agent-helper-1
Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
On Thu, 16 Jul 2020 23:33:11 +0200, Rene Engelhard wrote: > Am 16.07.20 um 23:28 schrieb Rene Engelhard: > > tag 964706 + patch > [...] > > This is what I did now... > [...] > > https://salsa.debian.org/java-team/jabref/-/merge_requests/2 Thanks Rene! I've been playing around with those jars from libreoffice myself a couple of days ago but didn't find a way to put all the pieces together. I'm glad you were successful! Merged and uploaded. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Zueriwest: Zorro signature.asc Description: Digital Signature
Bug#964706: marked as pending in jabref
Control: tag -1 pending Hello, Bug #964706 in jabref reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/jabref/-/commit/8acca4158aec32715dcd4d5194daa85f967fdf39 use org.libreoffice:libreoffice:7.0.0 and build-depend on liblibreoffice-java instead of the compatiblity libraries (closes: #964706, #965133) (this message was generated automatically) -- Greetings https://bugs.debian.org/964706
Processed: Bug#964706 marked as pending in jabref
Processing control commands: > tag -1 pending Bug #964706 [src:jabref] jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist Added tag(s) pending. -- 964706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2
Rob Browning writes: > Bdale Garbee writes: > >> However, I see little chance of geda-gaf upstream working on the things >> needed to keep it viable in Debian any time soon, and with lepton-eda in >> my mind a complete replacement that still works with the same file >> formats, etc, I see no reason to go nuts trying to make geda-gaf better. >> >> I'll file a removal request for geda-gaf. > > OK, thanks for the help. See #965098. Bdale signature.asc Description: PGP signature
Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2
Bdale Garbee writes: > However, I see little chance of geda-gaf upstream working on the things > needed to keep it viable in Debian any time soon, and with lepton-eda in > my mind a complete replacement that still works with the same file > formats, etc, I see no reason to go nuts trying to make geda-gaf better. > > I'll file a removal request for geda-gaf. OK, thanks for the help. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#961811: baresip: diff for NMU version 0.6.1-1.1
(note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. While I have not tested, I am 99% sure your fix for make 4.3 will break the build with make 4.2 in testing. Since I wrote the post in response to your proposed gst-plugins-bad1.0 NMU I have done some more searching, and apparently the solution to this is to use a variable. https://lwn.net/Articles/826217/ I applied that technique and was able to get succesful builds in both raspbian bullseye-staging and Debian sid. A debdiff of what I uploaded to raspbian is attatched. diff -Nru baresip-0.6.1/debian/changelog baresip-0.6.1/debian/changelog --- baresip-0.6.1/debian/changelog 2019-02-18 12:30:38.0 + +++ baresip-0.6.1/debian/changelog 2020-07-16 19:44:03.0 + @@ -1,3 +1,16 @@ +baresip (0.6.1-1+rpi1) bullseye-staging; urgency=medium + + * Raspbian upload based on Sebastian Ramacher's proposed NMU + [Sebastian Ramacher] + * debian/patches: +- Unbreak patch 1002 with make 4.3 (Closes: #961811) +- Apply upstream patch to fix build of selftest + [Peter Michael Green] + * Further adjust patch 1002 so it is compatible with both make 4.2 (bullseye) +and make 4.3 (sid) + + -- Peter Michael Green Thu, 16 Jul 2020 19:44:03 + + baresip (0.6.1-1) unstable; urgency=medium [ upstream ] diff -Nru baresip-0.6.1/debian/patches/1002_system_header_locations.patch baresip-0.6.1/debian/patches/1002_system_header_locations.patch --- baresip-0.6.1/debian/patches/1002_system_header_locations.patch 2019-02-11 19:42:25.0 + +++ baresip-0.6.1/debian/patches/1002_system_header_locations.patch 2020-07-16 19:37:33.0 + @@ -14,15 +14,29 @@ Last-Update: 2018-11-29 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ a/mk/modules.mk -+++ b/mk/modules.mk -@@ -67,46 +67,36 @@ +Index: baresip-0.6.1/mk/modules.mk +=== +--- baresip-0.6.1.orig/mk/modules.mk baresip-0.6.1/mk/modules.mk +@@ -59,6 +59,11 @@ + # Default is enabled + MOD_AUTODETECT := 1 + ++# GNU make 4.3 changes the escaping rules for the hash sign, the reccomended ++# way to maintain compatibility with both 4.2 and 4.3 is to use a variable ++# see https://lwn.net/Articles/810071/ ++HASHINCLUDE:=\#include ++ + ifneq ($(MOD_AUTODETECT),) + + USE_CONS := 1 +@@ -67,46 +72,36 @@ USE_L16 := 1 ifneq ($(OS),win32) -USE_ALSA := $(shell [ -f $(SYSROOT)/include/alsa/asoundlib.h ] || \ - [ -f $(SYSROOT_ALT)/include/alsa/asoundlib.h ] && echo "yes") -+USE_ALSA := $(shell echo '\#include ' | \ ++USE_ALSA := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) +USE_AMR := $(shell pkg-config --exists opencore-amrnb && echo "yes") +ifeq ($(USE_AMR),) @@ -39,9 +53,9 @@ - [ -f $(SYSROOT)/include/$(MACHINE)/libavformat/avformat.h ] || \ - [ -f $(SYSROOT_ALT)/include/libavformat/avformat.h ] && echo "yes") +endif -+USE_AVCODEC := $(shell echo '\#include ' | \ ++USE_AVCODEC := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_AVFORMAT := $(shell echo '\#include ' | \ ++USE_AVFORMAT := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) USE_AVAHI := $(shell pkg-config --exists avahi-client && echo "yes") -USE_BV32 := $(shell [ -f $(SYSROOT)/include/bv32/bv32.h ] || \ @@ -69,26 +83,26 @@ - [ -f $(SYSROOT)/include/gsm/gsm.h ] || \ - [ -f $(SYSROOT)/local/include/gsm.h ] || \ - [ -f $(SYSROOT)/local/include/gsm/gsm.h ] && echo "yes") -+USE_BV32 := $(shell echo '\#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_CAIRO := $(shell echo '\#include ' |\ ++USE_CAIRO := $(shell echo '$(HASHINCLUDE) ' |\ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_DTLS := $(shell echo '\#include ' | \ ++USE_DTLS := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_DTLS_SRTP := $(shell echo '\#include ' | \ ++USE_DTLS_SRTP := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G722 := $(shell echo '\#include ' | \ ++USE_G722 := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G722_1 := $(shell echo '\#include ' | \ ++USE_G722_1 := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G726 := $(shell echo '\#include ' | \ ++USE_G726 := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_GSM := $(shell echo '\#include ' | \ ++USE_GSM := $(shell echo '$(HASHINCLUDE) ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) USE_GST := $(shell pkg-config --exists gstreamer-0.10 && echo "yes") USE_GST1 := $(shell pkg-config --exists gstreamer-1.0 && echo "yes") USE_GST_VIDEO := \ -@@ -117,100 +107,81 @@ +@@ -117,100
Bug#965154: maxima: insecure use of /tmp
Package: maxima Version: 5.43.2-3 Severity: grave Tags: security Maxima uses /tmp in an insecure way. In particular, when creating plots, files are written to maxima_tempdir (which defaults to /tmp) with predictable names, and there is no check that the files do not exist. An attacker could use symlinks to redirect the writes to an arbitrary file.
Processed: libocxl: diff for NMU version 1.1.0-1.1
Processing control commands: > tags 963364 + patch Bug #963364 [src:libocxl] libocxl: FTBFS: Makefile:27: *** 'ocxl.h is non-existant or out of date, Download from http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/ocxl.h and place in /kernel/include/misc/ocxl.h'. Stop. Added tag(s) patch. > tags 963364 + pending Bug #963364 [src:libocxl] libocxl: FTBFS: Makefile:27: *** 'ocxl.h is non-existant or out of date, Download from http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/ocxl.h and place in /kernel/include/misc/ocxl.h'. Stop. Added tag(s) pending. -- 963364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963364: libocxl: diff for NMU version 1.1.0-1.1
Control: tags 963364 + patch
Control: tags 963364 + pending
Dear maintainer,
I've prepared an NMU for libocxl (versioned as 1.1.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru libocxl-1.1.0/debian/changelog libocxl-1.1.0/debian/changelog
--- libocxl-1.1.0/debian/changelog 2018-09-11 11:38:41.0 +0100
+++ libocxl-1.1.0/debian/changelog 2020-07-16 22:37:44.0 +0100
@@ -1,3 +1,11 @@
+libocxl (1.1.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS. (Closes: #963364)
+- Use local header file.
+
+ -- Sudip Mukherjee Thu, 16 Jul 2020 22:37:44
+0100
+
libocxl (1.1.0-1) unstable; urgency=medium
* Fix d/gbp.conf
diff -Nru libocxl-1.1.0/debian/patches/series
libocxl-1.1.0/debian/patches/series
--- libocxl-1.1.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libocxl-1.1.0/debian/patches/series 2020-07-16 22:30:38.0 +0100
@@ -0,0 +1 @@
+use_local.patch
diff -Nru libocxl-1.1.0/debian/patches/use_local.patch
libocxl-1.1.0/debian/patches/use_local.patch
--- libocxl-1.1.0/debian/patches/use_local.patch1970-01-01
01:00:00.0 +0100
+++ libocxl-1.1.0/debian/patches/use_local.patch2020-07-16
22:35:31.0 +0100
@@ -0,0 +1,27 @@
+Description: Use local copy ocxl.h
+ Only check online if local copy is not found.
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/963364
+Forwarded: not-needed
+
+---
+
+--- libocxl-1.1.0.orig/Makefile
libocxl-1.1.0/Makefile
+@@ -24,14 +24,13 @@ CHECK_OCXL_HEADER_IS_UP_TO_DATE = $(shel
+ check_ocxl_header:
+ ifeq ($(call CHECK_OCXL_HEADER_IS_UP_TO_DATE,''),n)
+ mkdir -p kernel/include/misc
+-ifeq (${HAS_WGET},y)
++else ifeq (${HAS_WGET},y)
+ $(call Q,WGET kernel/include/misc/ocxl.h, wget -O
kernel/include/misc/ocxl.h -q
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/ocxl.h)
+ else ifeq (${HAS_CURL},y)
+ $(call Q,CURL kernel/include/misc/ocxl.h, curl -o
kernel/include/misc/ocxl.h -s
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/ocxl.h)
+ else
+ $(error 'ocxl.h is non-existant or out of date, Download from
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/ocxl.h
and place in ${PWD}/kernel/include/misc/ocxl.h')
+ endif
+-endif
+
+ src/libocxl_info.h: version.pl
+ VERSION_MAJOR=${VERSION_MAJOR} VERSION_MINOR=${VERSION_MINOR} \
Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
Hi, Am 16.07.20 um 23:28 schrieb Rene Engelhard: > tag 964706 + patch [...] > This is what I did now... [...] https://salsa.debian.org/java-team/jabref/-/merge_requests/2 Regards, Rene
Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
tag 964706 + patch
thanks
Hi,
Am 16.07.20 um 17:27 schrieb Rene Engelhard:
>
>>> Replacing org.openoffice:juh:jar:4.1.2 ->
>>> org.libreoffice:juh:jar:debian
>>> Replacing org.openoffice:jurt:jar:4.1.2 ->
>>> org.libreoffice:jurt:jar:debian
>>> Replacing org.openoffice:ridl:jar:4.1.2 ->
>>> org.libreoffice:ridl:jar:debian
>>> Replacing org.openoffice:unoil:jar:4.1.2 ->
>>> org.libreoffice:unoil:jar:debian
> So they are found there...
This sounded like maven stuff so I tried
https://gerrit.libreoffice.org/c/core/+/98929 (hacked into the local
/usr/share/maven-repo poms), but still it failed.
> All of thse libs above are now dummy libs for liblibreoffice.jar. They
> are empty and just contain Class-Path:
> [...]
> As a workaround one might patch jabref to use libreoffice.jar directly
> - which is the library to use anyway. (the others are still packaged for
> compatibility with old packages and third-party stuff which doesn't know
> about libreoffice.jar...) but...
This is what I did now...
diff --git a/debian/changelog b/debian/changelog
index 8a56e6c..459513d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,12 +2,13 @@ jabref (3.8.2+ds-14) unstable; urgency=medium
* Team upload.
- * add explicit dependencies to libjuh-java, libjurt-java,
- libridl-java, libunoil-java (closes: #965133)
+ * use org.libreoffice:libreoffice:7.0.0 and build-depend on
+ liblibreoffice-java instead of the compatiblity libraries
+ (closes: #964706, #965133)
* only recommend libreoffice-java-common and remove it from
Build-Depends:
(unneeded)
- -- Rene Engelhard Thu, 09 Jul 2020 21:19:22 +
+ -- Rene Engelhard Thu, 16 Jul 2020 23:19:05 +0200
jabref (3.8.2+ds-13) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 33977ba..fe9a312 100644
--- a/debian/control
+++ b/debian/control
@@ -35,10 +35,7 @@ Build-Depends-Indep: ant,
libpdfbox-java,
libpostgresql-jdbc-java (>= 9.4.1212),
librelaxng-datatype-java,
- libjuh-java,
- libjurt-java,
- libridl-java,
- libunoil-java,
+ liblibreoffice-java,
libscram-java,
libspin-java,
libswingx-java,
@@ -78,10 +75,7 @@ Depends: ${misc:Depends},
liblog4j2-java (>= 2.10.0-2) | liblog4j2-java (<< 2.10),
libmicroba-java,
libpdfbox-java (<< 1:2),
- libjuh-java,
- libjurt-java,
- libridl-java,
- libunoil-java,
+ liblibreoffice-java,
libspin-java,
libswing-layout-java,
libswingx-java (<< 1:1.6.4),
diff --git a/debian/patches/010_gradle_build.patch
b/debian/patches/010_gradle_build.patch
index 3d19f7e..0797b5f 100644
--- a/debian/patches/010_gradle_build.patch
+++ b/debian/patches/010_gradle_build.patch
@@ -64,6 +64,18 @@ Forwarded: not-needed
compile 'com.jgoodies:jgoodies-common:1.8.1'
compile 'com.jgoodies:jgoodies-forms:1.9.0'
compile 'com.jgoodies:jgoodies-looks:2.7.0'
+@@ -86,10 +86,7 @@ dependencies {
+
+ compile 'commons-cli:commons-cli:1.3.1'
+
+- compile 'org.openoffice:juh:4.1.2'
+- compile 'org.openoffice:jurt:4.1.2'
+- compile 'org.openoffice:ridl:4.1.2'
+- compile 'org.openoffice:unoil:4.1.2'
++ compile 'org.libreoffice:libreoffice:7.0.0'
+
+ compile 'com.github.bkromhout:java-diff-utils:2.1.1'
+
@@ -97,9 +106,8 @@
antlr4 'org.antlr:antlr4:4.6'
compile 'org.antlr:antlr4-runtime:4.6'
Regards,
Rene
Processed: Re: Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
Processing commands for cont...@bugs.debian.org: > tag 964706 + patch Bug #964706 [src:jabref] jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 964706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965153: gscan2pdf: "fails to open device" for Epson NX100
Package: gscan2pdf Version: 2.8.0-1, 2.8.1-1 Severity: grave Except for a couple of times I've been able to get it to work (without knowing what it was that made it finally work after minutes of battle)... * when I start gscan2pdf it claims it does not see my scanner and offers to rescan or continue without * rescanning sometimes get me back to this window, sometimes to main screen * from main screen when I click the scan button, I often get the same complaint * sometimes I get to the scan dialog with "Epson NX100" properly selected, but then launching the scan it complains that it "first has to open the device" (good guess, but I'd thought it would do that for me). After which the UI is completely unresponsive and I have to kill the app Upgrading to unstable just adds me a "restart gscan2pdf" in the initial failure dialog, but that does not help either. Downgrading to stable's 2.3.0-1 gets me back a fully working version.
Bug#965151: afdko-bin: /usr/bin/tx is already shipped by transifex-client
Package: afdko-bin Version: 3.4.0+dfsg1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + src:transifex-client Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../afdko-bin_3.4.0+dfsg1-2_amd64.deb ... Unpacking afdko-bin (3.4.0+dfsg1-2) ... dpkg: error processing archive /var/cache/apt/archives/afdko-bin_3.4.0+dfsg1-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/tx', which is also in package transifex-client 0.13.9-1 Errors were encountered while processing: /var/cache/apt/archives/afdko-bin_3.4.0+dfsg1-2_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/tx Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html transifex-client=0.13.9-1_afdko-bin=3.4.0+dfsg1-2.log.gz Description: application/gzip
Processed: afdko-bin: /usr/bin/tx is already shipped by transifex-client
Processing control commands: > affects -1 + src:transifex-client Bug #965151 [afdko-bin] afdko-bin: /usr/bin/tx is already shipped by transifex-client Added indication that 965151 affects src:transifex-client -- 965151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libtomcat10{,-embed}-java: install files in 9.x paths
Processing control commands:
> found -1 10.0.0~M7-1
Bug #965006 [libtomcat10-java,libtomcat10-embed-java]
libtomcat10{,-embed}-java: install files in 9.x paths
Marked as found in versions tomcat10/10.0.0~M7-1.
--
965006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965006: libtomcat10{,-embed}-java: install files in 9.x paths
Followup-For: Bug #965006
Control: found -1 10.0.0~M7-1
Hi,
while the conflict in 9.x paths is gone in 10.0.0~M7-1,
libtomcat{9,10}-java still have some conflicting files:
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-cs/debian/tomcat-i18n-cs-debian.jar
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-cs/debian/tomcat-i18n-cs-debian.pom
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-de/debian/tomcat-i18n-de-debian.jar
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-de/debian/tomcat-i18n-de-debian.pom
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-ko/debian/tomcat-i18n-ko-debian.jar
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-ko/debian/tomcat-i18n-ko-debian.pom
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-pt-BR/debian/tomcat-i18n-pt-BR-debian.jar
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-pt-BR/debian/tomcat-i18n-pt-BR-debian.pom
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-zh-CN/debian/tomcat-i18n-zh-CN-debian.jar
usr/share/maven-repo/org/apache/tomcat/tomcat-i18n-zh-CN/debian/tomcat-i18n-zh-CN-debian.pom
If they cannot be moved to a versioned location, you'll have to add
Breaks+Replaces to libtomcat10-java, giving up co-installability.
Andreas
Bug#965033: debdiff
and looking at the commit ids, the responsible might be this commit https://github.com/mesonbuild/meson/commit/57b468c75ae90e09f8bd98da12a5c420ab49cd79 (not sure if only that one) G.
Bug#965033: marked as done (meson: Missing dependency on python3-pkg-resources)
Your message dated Thu, 16 Jul 2020 19:33:54 + with message-id and subject line Bug#965033: fixed in meson 0.55.0-2 has caused the Debian Bug report #965033, regarding meson: Missing dependency on python3-pkg-resources 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.) -- 965033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: meson Version: 0.55.0-1 Severity: serious Tags: ftbfs Control: affects -1 src:systemd $ meson Traceback (most recent call last): File "/usr/bin/meson", line 17, in from mesonbuild import mesonmain File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 25, in from . import mconf, mdist, minit, minstall, mintro, msetup, mtest, rewriter, msubprojects, munstable_coredata, mcompile File "/usr/lib/python3/dist-packages/mesonbuild/mconf.py", line 16, in from . import coredata, environment, mesonlib, build, mintro, mlog File "/usr/lib/python3/dist-packages/mesonbuild/build.py", line 26, in from . import dependencies File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/__init__.py", line 15, in from .boost import BoostDependency File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/boost.py", line 25, in from .base import DependencyException, ExternalDependency, PkgConfigDependency File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/base.py", line 32, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' $ --- End Message --- --- Begin Message --- Source: meson Source-Version: 0.55.0-2 Done: Jussi Pakkanen We believe that the bug you reported is fixed in the latest version of meson, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jussi Pakkanen (supplier of updated meson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Jul 2020 22:15:06 +0300 Source: meson Architecture: source Version: 0.55.0-2 Distribution: unstable Urgency: medium Maintainer: Jussi Pakkanen Changed-By: Jussi Pakkanen Closes: 963546 965033 Changes: meson (0.55.0-2) unstable; urgency=medium . * Fix crossbuild test from Gianfranco Costamagna. Closes: #963546 * Add dep to Python pkg resources from Kunal Mehta. Closes: #965033. Checksums-Sha1: 416525ac2526aacd15feac1b9906abed81b19ca6 3433 meson_0.55.0-2.dsc 604a93643c127d32912da978dbdc7a94a43836ee 13832 meson_0.55.0-2.debian.tar.xz 093961d050b6ec6f8883df879f4e5832fe372a84 6176 meson_0.55.0-2_source.buildinfo Checksums-Sha256: 74c5d3dcdd7c5f8eb8a07c9f7b5c0d8c8492436ceaef4266b17155283a0796ad 3433 meson_0.55.0-2.dsc 6c808fc8fb729d73e596a6d5b4ddfad1466609d5494a33076c18f1678371dbba 13832 meson_0.55.0-2.debian.tar.xz 761e3862e3af5b6d9166419ef24fec46b67987618630904c88dcfbb43d853151 6176 meson_0.55.0-2_source.buildinfo Files: 6395d069eb69ed0afa9146597de05153 3433 devel optional meson_0.55.0-2.dsc c1bcc2dd85bd74a4ebac8bf804d7c5e3 13832 devel optional meson_0.55.0-2.debian.tar.xz 8a891b48d3a92ae0366e6a9b43169d30 6176 devel optional meson_0.55.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAl8QqHYACgkQ0U7xXa/h E0cVww/+IO0hz2+YxtBVRmoEobUwE0uEz/9gujU4d06ZhwfKWThf7Mqi3lx+UOBz 3qjqKqnmJo/50FbjdGU5fMoFLPs7o1gxOxCwi9R4Eo3M9MQ1jvBRY1uq+scoEkqm /B4DO07VY8/q0MLC/nRGCSUnejobqz8/az+e0xVSaOnvWT3a6Il7/oAw1HA3UL6b TQkCoXdWIxRw6veNE0Psuh1xZLjM/5YwFQzJ4xFSU3+zYGO5hhHcXMkRe6k2vwV0 DNQonnsgDsHlMLsaB5WtfTwz2crgKY7ni+Zm1jcEa1vpyoUBOK8cJ78It3081y+U SczHfHu7EYyqOOplMsIqhBP+gd83WoSqmxOhzpChpHNdjfyKzpML7Cq2mdDsjk67 8OVDMX2+qayiTeEOCA2FCfvh27eNXr/OmkARAnsDhjB80YCRVXurkMBfCzL1Mt5J udnexk/jdZSWDQ//SSFWuhZjxp9gkKpI9konLSGtEAPIUFIae5hxdehkgnDk3S1c eeVw9OtMa9JceJjAoDXlLpq/i/BezqRrWEfMvxGK+CjnoN2iShX5eKggqofM03XM VdvxOoL0m6Wp9B8gEjrmXi6duStXysaU9jbqMrM2MYeA4/dmQiJ4fT1MvD4xFGkR 3707Kl+bDxVHGyw5M+0+Irmi07mkuM6iXWttdZIidMnzmWVRiuU= =4msu -END PGP SIGNATURE End Message ---
Bug#963546: marked as done (meson: autopkgtest failures)
Your message dated Thu, 16 Jul 2020 19:33:54 + with message-id and subject line Bug#963546: fixed in meson 0.55.0-2 has caused the Debian Bug report #963546, regarding meson: autopkgtest failures 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.) -- 963546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: meson Version: 0.54.3-1 Severity: serious Hello, as you can see, two tests can't be run on ppc64el and s390x, because of missing: g++-arm-linux-gnueabihf and ldc https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz Marking the two tests as "skip-not-installed" works diff -Nru meson-0.54.3/debian/tests/control meson-0.54.3/debian/tests/control --- meson-0.54.3/debian/tests/control 2020-03-27 23:40:23.0 + +++ meson-0.54.3/debian/tests/control 2020-06-23 13:25:22.0 + @@ -10,6 +10,8 @@ # tests are run and thus block broken uploads. Tests: exhaustive Depends: meson, @builddeps@, valac, rustc, ldc +Restrictions: skip-not-installable Tests: crossbuild Depends: meson, g++, g++-arm-linux-gnueabihf +Restrictions: skip-not-installable Also, I noticed a failure on Ubuntu: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/m/meson/20200616_020946_f376b@/log.gz Failed test during build: 'test cases/frameworks/1 boost (static=false)' Reason: Compiling source code failed. Skipping: test cases/frameworks/1 boost (static=false b_vscrt=md) Skipping: test cases/frameworks/1 boost (static=false b_vscrt=mdd) Succeeded test: test cases/frameworks/1 boost (static=true) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=md) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mdd) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mt) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mtd) Mesonlogs of failing tests The Meson build system Version: 0.54.3 Source dir: /tmp/autopkgtest.u568ol/build.zhB/src/test cases/frameworks/1 boost Build dir: /tmp/autopkgtest.u568ol/build.zhB/src/b 125f976e40 Build type: native build Project name: boosttest Project version: undefined C++ compiler for the host machine: c++ (gcc 9.3.0 "c++ (Ubuntu 9.3.0-13ubuntu1) 9.3.0") C++ linker for the host machine: c++ ld.bfd 2.34 Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency Boost found: YES 1.71.0 (/usr/include) Run-time dependency Boost (found: date_time, system, thread) found: YES 1.71.0 (/usr) Run-time dependency Boost (found: unit_test_framework) found: YES 1.71.0 (/usr) Dependency boost found: YES 1.71.0 (cached) Run-time dependency Boost (found: date_time, filesystem, log, log_setup, regex, system, thread) found: YES 1.71.0 (/usr) Run-time dependency Boost (missing: this_should_not_exist_on_any_systen) found: NO Program python2 found: YES (/usr/bin/python2) Program python3 found: YES (/usr/bin/python3) test cases/frameworks/1 boost/meson.build:27: WARNING: Passed invalid keyword argument "disabler". WARNING: This will become a hard error in the future. Dependency python found: NO test cases/frameworks/1 boost/meson.build:28: WARNING: Passed invalid keyword argument "disabler". WARNING: This will become a hard error in the future. Dependency python found: YES (pkgconfig) Run-time dependency Boost (found: python38) found: YES 1.71.0 (/usr) Program /usr/bin/python2 found: YES (/usr/bin/python2) Program /usr/bin/python3 found: YES (/usr/bin/python3) Run-time dependency Boost found: YES 1.71.0 (/usr/include) Dependency boost found: YES 1.71.0 (cached) Build targets in project: 7 Found ninja-1.10.0 at /usr/bin/ninja [1/14] Compiling C++ object 'utf@exe/unit_test.cpp.o' [2/14] Linking target utf [3/14] Compiling C++ object 'nomod@exe/nomod.cpp.o' [4/14] Linking target nomod [5/14] Compiling C++ object 'linkedexe@exe/linkexe.cc.o' [6/14] Linking target linkedexe [7/14] Compiling C++ object 'extralibexe@exe/extralib.cpp.o' FAILED: extralibexe@exe/extralib.cpp.o c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' -I/usr/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++14 -g -pthread -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_SETUP_DYN_LINK=1 -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 -DBOOST_LOG_DYN_LINK=1 -DBOOST_ALL_NO_LIB -MD -MQ 'extralibexe@exe/extralib.cpp.o'
Processed: severity of 964908 is grave
Processing commands for cont...@bugs.debian.org: > severity 964908 grave Bug #964908 [tomcat9] tomcat9: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 964908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 965143, bug 965143 is forwarded to https://github.com/SSSD/sssd/issues/5247
Processing commands for cont...@bugs.debian.org: > tags 965143 + upstream Bug #965143 [sssd] sssd: SSSD 2.3 won't let log in or use sudo Added tag(s) upstream. > forwarded 965143 https://github.com/SSSD/sssd/issues/5247 Bug #965143 [sssd] sssd: SSSD 2.3 won't let log in or use sudo Set Bug forwarded-to-address to 'https://github.com/SSSD/sssd/issues/5247'. > thanks Stopping processing here. Please contact me if you need assistance. -- 965143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Quoting Adrian Bunk (2020-07-16 19:32:41) > On Thu, Jul 16, 2020 at 07:25:28PM +0200, Jonas Smedegaard wrote: > > Control: found -1 > > > > Quoting Adrian Bunk (2020-07-16 17:53:44) > > > On Thu, Jul 16, 2020 at 05:34:46PM +0200, Jonas Smedegaard wrote: > > > > Quoting Adrian Bunk (2020-07-16 17:29:17) > > > > > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > > > > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > > > > > Hi, > > > > > > > > > > > > > > Does disabling optimization help? I have it disabled for > > > > > > > these architectures in haskell-lambdahack and it did help > > > > > > > in that case. > > > > > > > > > > > > I will try. Thanks for the suggestion! > > > > > > > > > > "-O0 -g0" worked for me on armel, I am currently trying on > > > > > mipsel what the minimum required change is. > > > > > > > > As I understand it, "-O0 -g0" is not the most minimally > > > > intrusive, > > > > > > "-O0 -g0" is nearly the biggest possible hammer. > > > > > > It was my starting point for seeing that there is some possible > > > solution available this way. > > > > > > > instead (as I also posted separately in more detail a moment > > > > ago) that is --ghc-options="-optc--param -optcggc-min-expand=5" > > > > > > If that is sufficient it is great. > > > > > > Unless something changed recently no debug info is distributed for > > > Haskell-built binaries, so -g1/-g0 does not actually make anything > > > worse. This is what I am currently trying on eller. > > > > My tweak wasn't adequate. > > > > I am open to suggestions. > > Give me 1-3 days (test builds take time) and I can send a patch. Awesome. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965143: sssd: SSSD 2.3 won't let log in or use sudo
Package: sssd Version: 2.3.0-2 Severity: grave Justification: renders package unusable This locks me out of my systems. $ sudo -l [sudo] password for sam.morris@ad.domain.example: Sorry, try again. [sudo] password for sam.morris@ad.domain.example: Sorry, try again. [sudo] password for sam.morris@ad.domain.example: sudo: 3 incorrect password attempts Each authentication attempt logs the following in sssd_pam.log: (2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn_res] (0x0040): Search for upn [sam.morris@ad.domain.example] returns more than one result. One of the possible reasons can be that several users share the same email address. (2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn] (0x0040): Error: 22 (Invalid argument) (2020-07-16 18:08:38): [pam] [sysdb_initgroups_by_upn] (0x0040): sysdb_search_user_by_upn() failed. (2020-07-16 18:08:38): [pam] [cache_req_search_cache] (0x0020): CR #12: Unable to lookup [sam.morris@ad.domain.example] in cache [22]: Invalid argument (2020-07-16 18:08:38): [pam] [pam_check_user_search_next] (0x0020): Fatal error, killing connection! My user exists in an Active Directory domain that has a one-way trust established via FreeIPA. We do indeed have several users with the same email address. That's (until now) been a perfectly valid setup (one human has several accounts for performing different roles and they all have the same email address). Downgrading to 2.2.3-3 fixes the problem. It's necessary to remove the sssd database after downgrading. I've had a quick scan of the commits between 2.2.3 and 2.3.0 and nothing's jumped out at me yet. I'll take another look later... -- System Information: Debian Release: 10.3 APT prefers stable-debug APT policy: (570, 'stable-debug'), (570, 'stable'), (550, 'testing-debug'), (550, 'testing'), (530, 'unstable-debug'), (530, 'unstable'), (500, 'stable-updates'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: default Versions of packages sssd depends on: ii python3-sss 2.3.0-2 ii sssd-ad 2.3.0-2 ii sssd-common 2.3.0-2 ii sssd-ipa 2.3.0-2 ii sssd-krb52.3.0-2 ii sssd-ldap2.3.0-2 ii sssd-proxy 2.3.0-2 sssd recommends no packages. sssd suggests no packages. -- no debconf information
Bug#952673: does not start automatically anymore on fresh installs
On 7/16/20 9:37 AM, Santiago Ruano Rincón wrote: > I leave this as a note: kresd upstream removed systemd sockets support > since 5.0: > https://gitlab.nic.cz/knot/knot-resolver/-/issues/485 I'm afraid I don't understand what this has to with the original problem. the original problem is the following: * user did 'apt install knot-resolver' on buster, edited resolv.conf to point to 127.0.0.1 * user upgrades from buster to bullseye and has no working DNS anymore. there is no warning or anything. I suggest to, please: * either fix the package so that 'apt install knot-resolver' in bullseye is again resulting in a working DNS resolver on localhost * or, add a prominent warning note via debconf so people know that they have to fix it manually and document the required steps to configure knot-resolver to be used as a local resolver. unless either of which is done, knot-resolver from bullseye *breaks* peoples systems without saying so and in an unexpected way, which deserves severity serious. Regards, Daniel
Bug#962720: gst-plugins-bad1.0: diff for NMU version 1.16.2-2.2
(note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for gst-plugins-bad1.0 (versioned as 1.16.2-2.2) and uploaded it to DELAYED/2. Hi, I tried adding your proposed NMU to raspbian as part of trying to get the x265 transition to go through there. Unfortunately it looks like the included fix for make 4.3 (sid) breaks builds with make 4.2 (buster/bullseye). https://buildd.raspbian.org/status/fetch.php?pkg=gst-plugins-bad1.0=armhf=1.16.2-2.2=1594916528 If possible it would be preferable to have a fix that works with both make versions. It looks like there are currently multiple issues blocking the migration of make-dfsg 4.3 to testing. Also I notice that your NMU fixes bug 962725 but does not mention the bug number in the changelog and the NMU diff was not sent to that bug. P.S. I still think the propsed NMU is an improvement over the status quo, since it is currently not possible to build gst-plugins-bad1.0 in either bullseye or sid.
Bug#965033: debdiff
Hello again, On Wed, 15 Jul 2020 17:02:36 -0700 Kunal Mehta wrote: > I'm happy to NMU this since it's affecting some of my packages (zimlib, > libkiwix, zim-tools, etc.). debdiff is attached. > > It's not clear to me why the dependency was commented out in the first > place, but it fixes the immediate issue. Let me know if that's OK and if > you'd like me to go ahead. > this is probably the rationale for it https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909440 G.
Bug#965033: debdiff
Hello, On Wed, 15 Jul 2020 17:02:36 -0700 Kunal Mehta wrote: > I'm happy to NMU this since it's affecting some of my packages (zimlib, > libkiwix, zim-tools, etc.). debdiff is attached. > > It's not clear to me why the dependency was commented out in the first > place, but it fixes the immediate issue. Let me know if that's OK and if > you'd like me to go ahead. > I'm not the maintainer, but in case you want to NMU, please add also this patch: from the other RC bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963546#50 diff -Nru meson-0.55.0/debian/tests/control meson-0.55.0/debian/tests/control --- meson-0.55.0/debian/tests/control 2020-07-12 16:29:07.0 +0200 +++ meson-0.55.0/debian/tests/control 2020-07-14 13:06:32.0 +0200 @@ -12,4 +12,4 @@ Depends: meson, @builddeps@, valac, rustc, ldc [!s390x !ppc64el] Tests: crossbuild -Depends: meson, g++, g++-arm-linux-gnueabihf +Depends: meson, g++, g++-arm-linux-gnueabihf [!s390x] thanks! G.
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
On Thu, Jul 16, 2020 at 07:25:28PM +0200, Jonas Smedegaard wrote: > Control: found -1 > > Quoting Adrian Bunk (2020-07-16 17:53:44) > > On Thu, Jul 16, 2020 at 05:34:46PM +0200, Jonas Smedegaard wrote: > > > Quoting Adrian Bunk (2020-07-16 17:29:17) > > > > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > > > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > > > > Hi, > > > > > > > > > > > > Does disabling optimization help? I have it disabled for these > > > > > > architectures in haskell-lambdahack and it did help in that > > > > > > case. > > > > > > > > > > I will try. Thanks for the suggestion! > > > > > > > > "-O0 -g0" worked for me on armel, I am currently trying on mipsel > > > > what the minimum required change is. > > > > > > As I understand it, "-O0 -g0" is not the most minimally intrusive, > > > > "-O0 -g0" is nearly the biggest possible hammer. > > > > It was my starting point for seeing that there is some possible > > solution available this way. > > > > > instead (as I also posted separately in more detail a moment ago) > > > that is --ghc-options="-optc--param -optcggc-min-expand=5" > > > > If that is sufficient it is great. > > > > Unless something changed recently no debug info is distributed for > > Haskell-built binaries, so -g1/-g0 does not actually make anything > > worse. This is what I am currently trying on eller. > > My tweak wasn't adequate. > > I am open to suggestions. Give me 1-3 days (test builds take time) and I can send a patch. > - Jonas cu Adrian
Bug#964044: mrpt: FTBFS: test failure
Hello, On Mon, 13 Jul 2020 21:20:41 +0200 Sebastian Ramacher wrote: > On 2020-06-30 22:37:57 +0200, Sebastian Ramacher wrote: > > Source: mrpt > > Version: 1:2.0.4-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source (but built successfully in the > > past) > > > > binNMUs of mrpt failed to build: > > | [--] 1 test from RawlogGrabberApp > > | [ RUN ] RawlogGrabberApp.CGenericCamera_AVI > > | [CCameraSensor::initialize] Opening camera... > > | [CCameraSensor::initialize] FFmpeg stream: > > /<>/share/mrpt/datasets/dummy_video.avi... > > | [CCameraSensor::initialize] Done! > > | Rawlog grabbed objects: 1 > > | /<>/libs/apps/src/RawlogGrabberApp_unittest.cpp:94: Failure > > | Expected: (app.rawlog_saved_objects) >= (REQUIRED_GRAB_OBS), actual: 1 vs > > 3 > > | [ FAILED ] RawlogGrabberApp.CGenericCamera_AVI (1511 ms) > > | [--] 1 test from RawlogGrabberApp (1511 ms total) > > > > See > > https://buildd.debian.org/status/fetch.php?pkg=mrpt=amd64=1%3A2.0.4-1%2Bb1=1593549279=0 > > for example > > This issue has been fixed upstream: > https://github.com/MRPT/mrpt/commit/15234dc335c2413e3fd41021f7511f1d36fe915b. > Could you please apply the fix to the Debian package so that > ros-geometry2 transition can be completed? Thanks looks like that commit is already part of 2.0.4? G. > > Cheers > -- > Sebastian Ramacher
Processed: Re: Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Processing control commands:
> found -1
Bug #965121 {Done: Jonas Smedegaard } [src:pandoc] pandoc: FTBFS
on armel, armhf, mipsel: out of memory
No longer marked as fixed in versions pandoc/2.9.1.1-2 and reopened.
--
965121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Control: found -1 Quoting Adrian Bunk (2020-07-16 17:53:44) > On Thu, Jul 16, 2020 at 05:34:46PM +0200, Jonas Smedegaard wrote: > > Quoting Adrian Bunk (2020-07-16 17:29:17) > > > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > > > Hi, > > > > > > > > > > Does disabling optimization help? I have it disabled for these > > > > > architectures in haskell-lambdahack and it did help in that > > > > > case. > > > > > > > > I will try. Thanks for the suggestion! > > > > > > "-O0 -g0" worked for me on armel, I am currently trying on mipsel > > > what the minimum required change is. > > > > As I understand it, "-O0 -g0" is not the most minimally intrusive, > > "-O0 -g0" is nearly the biggest possible hammer. > > It was my starting point for seeing that there is some possible > solution available this way. > > > instead (as I also posted separately in more detail a moment ago) > > that is --ghc-options="-optc--param -optcggc-min-expand=5" > > If that is sufficient it is great. > > Unless something changed recently no debug info is distributed for > Haskell-built binaries, so -g1/-g0 does not actually make anything > worse. This is what I am currently trying on eller. My tweak wasn't adequate. I am open to suggestions. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: [bts-link] source package src:gtk+3.0
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gtk+3.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #964679 (http://bugs.debian.org/964679) > # Bug title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols > appeared in the symbols file: see diff output below > # * https://gitlab.gnome.org/GNOME/gtk/-/issues/2919 > # * remote status changed: (?) -> closed > # * closed upstream > tags 964679 + fixed-upstream Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Added tag(s) fixed-upstream. > usertags 964679 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 964679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965136: marked as done (libselinux: Newly versioned symbols did not bump dependency version in .symbols)
Your message dated Thu, 16 Jul 2020 16:48:38 + with message-id and subject line Bug#965136: fixed in libselinux 3.1-2 has caused the Debian Bug report #965136, regarding libselinux: Newly versioned symbols did not bump dependency version in .symbols to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libselinux Version: 3.1-1 Severity: grave Tags: patch Hi, The switch to versioned symbols did not bump the version of the now versioned symbols thus packages built against 3.1-1 would pick up a dependency on the older libselinux1 package where versioned symbols were not available causing programs to fail. I've filed an MR in Salsa: https://salsa.debian.org/selinux-team/libselinux/-/merge_requests/3 . The failure can be observed at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/s/systemd/20200716_044131_250e2@/log.gz Cheers, Balint -- Balint Reczey Ubuntu & Debian Developer --- End Message --- --- Begin Message --- Source: libselinux Source-Version: 3.1-2 Done: Laurent Bigonville We believe that the bug you reported is fixed in the latest version of libselinux, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated libselinux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 16 Jul 2020 18:28:55 +0200 Source: libselinux Architecture: source Version: 3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian SELinux maintainers Changed-By: Laurent Bigonville Closes: 965136 Changes: libselinux (3.1-2) unstable; urgency=medium . [ Laurent Bigonville ] * debian/control: Bump libselinux1-dev dependency on libsepol1-dev to 3.1 . [ Balint Reczey ] * debian/libselinux1.symbols: Versioned symbols are available starting with 3.1~ (Closes: #965136) Checksums-Sha1: d617d9f1fb2060079d9fab6e4ad5fbbe90367861 2310 libselinux_3.1-2.dsc b9e0bc61b20d08f07226d7c55805ac03ba3b0da5 23788 libselinux_3.1-2.debian.tar.xz 3dfd69d5010c5dddbc8fee8b320a7262a6413e1f 11977 libselinux_3.1-2_source.buildinfo Checksums-Sha256: 9d9a31ac3e11dcaa1bbdaa28c3bdc7dc44a94b0b3d6b380e5c5e69f6f57c5901 2310 libselinux_3.1-2.dsc 336c6df026daf947f37c74d3e3efdfc6b235491d402096f050ce2c9d8bbad415 23788 libselinux_3.1-2.debian.tar.xz 8f44b758dfb4a9b42e02e77c757e4b36543eb0708ee93f75df91a0bda2cec50f 11977 libselinux_3.1-2_source.buildinfo Files: 73328c715a3c9cc4996332a20e32151b 2310 libs optional libselinux_3.1-2.dsc 177b0d38f392f49eb6ce25283df819e6 23788 libs optional libselinux_3.1-2.debian.tar.xz e615f2150227bc6f801d9f23a8e2f148 11977 libs optional libselinux_3.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl8QgScRHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9W5ZAf6AkSsmeIH6LpJYv05cEpu2nZqwVRcc0hi FwcyaPwr28M00YxP9Gfs3zKo4dy10c5R2Us4K9+heY/zJ8ivF6hOGZ1tZ3KdnALC E/MU12V4qSUkvR0xEVEWwpKXUJttYyA+eEJkMbVmhdREVqA6i1p2NIgv22o0jUk9 lyRSEZfzVCy13t5hBeZ+noBg/ARzgyJdcvAkKOxfUS5IYc2KQDu3QHDoEn1egbqn Papp5Ge0VtWiNXxX3IwOOL15N0QLX8IXrmGDiF/XObDz5nDIf8J2YTM2Piue0Ipp Lk1NkKcmZEIDjAcLQrSSdpuiKMF6f/l9Os43miLH8M4zD2W17Ny5jA== =srx6 -END PGP SIGNATURE End Message ---
Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
Hi, Am 16.07.20 um 17:27 schrieb Rene Engelhard: > All of thse libs above are now dummy libs for liblibreoffice.jar. They > are empty and just contain Class-Path: Should be obvious from the rest but this of course should read "All of thse libs above are now dummy libs for libreoffice.jar." Regards, Rene
Bug#965121: marked as done (pandoc: FTBFS on armel, armhf, mipsel: out of memory)
Your message dated Thu, 16 Jul 2020 16:05:59 + with message-id and subject line Bug#965121: fixed in pandoc 2.9.1.1-2 has caused the Debian Bug report #965121, regarding pandoc: FTBFS on armel, armhf, mipsel: out of memory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pandoc Version: 2.9.1.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Thanks for fixing #964822. Unfortunately pandoc now fails to build on armel, armhf and mipsel: | [112 of 158] Compiling Text.Pandoc.Writers.Markdown | ghc: out of memory (requested 2097152 bytes) | make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 251 See https://buildd.debian.org/status/fetch.php?pkg=pandoc=armel=2.9.1.1-1=1594837537=0 for example Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: pandoc Source-Version: 2.9.1.1-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of pandoc, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated pandoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Jul 2020 17:13:21 +0200 Source: pandoc Architecture: source Version: 2.9.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Jonas Smedegaard Closes: 965121 Changes: pandoc (2.9.1.1-2) unstable; urgency=medium . * reduce compile-time memory utilization on armel and armhf (in addition to mips and mipsel), and reduce further (begin garbage-collect at 5% memory utilization not 10%); closes: bug#965121, thanks to Sebastian Ramacher Checksums-Sha1: 84b89b893853db5bbd07f796898e052f672ad764 8324 pandoc_2.9.1.1-2.dsc 17392ae653e7337fd151cff3523dc6457d14b94d 53404 pandoc_2.9.1.1-2.debian.tar.xz 92e85947badfddd2662d51b046bf0ce331097530 20284 pandoc_2.9.1.1-2_amd64.buildinfo Checksums-Sha256: d2cc21a9efcfa979586200ae06c76d4f566e25fdc390fd784e1ceeb4ed643c45 8324 pandoc_2.9.1.1-2.dsc 51ab4e507f91c391d8a7ba60b9503e41fe3987e6914e7d04c5f77da8d65fbaf3 53404 pandoc_2.9.1.1-2.debian.tar.xz 0c477b1f38a3cc58ed31599bb941bc6b757b37f9f3d623956fd5e1b8053f4b3a 20284 pandoc_2.9.1.1-2_amd64.buildinfo Files: 6bcf88a6eeff6e64b17f39caaa10518d 8324 text optional pandoc_2.9.1.1-2.dsc b19c9d8016e20cf956c67abd2a5641a0 53404 text optional pandoc_2.9.1.1-2.debian.tar.xz 3c4d43d6ebf18565f56525bba5163406 20284 text optional pandoc_2.9.1.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8QdqMACgkQLHwxRsGg ASGYlQ/9H/r2ZiTjVMsP5dAKDElCF+oPuh15uLp3JvLWxBkYFVUZ5BZFBjFa7mQr anYl8mmSJQAj1FdpzuUv8Zg2IrApLq0NVw7WGSvG/yFSq09ncrFueqa84oFVekp0 53HokJATBogNdwkZEfQ3NNYJRN57Oq5X/SaaeVKMQ/XIsAD38sJrBTBTQ0XQtz7L GtbuzaDwzZbj9dLZzXaow75Nq1xVXK5V6CL8ZDulElyxQXlKi/keEwEofyT7/+1t fEC5DFYx+vH0bRkvRyzxK2cHo+uszGj32C6fM4G6cjN5iDh7zPBYffMVq+vEhGa5 isRq+1RZhu1j/fiZIY4/NDinIU0Yse4g17LXuTba9t85ghiIPlJf4vW9U1XWu1nM Rcdpv/UMzOd1CiNo/FdI72x4rYrl6PcF0ojzsxmZvl/HYfCokxCTs+lAa+6wipoI oEMCyM2dUbVvZUGJ6yiOJRvQwGrR03wnuTMR4BKFiM+S7SmIcD8Eqp18L1b/mU7w O/E2LKtGhAtHRL0D4xhHiWGIte0OvdQkEbVEqlnjsGNC1B9ZKZXO7iBrnBNt+aAq XgW/63JiLV9KC7PEcLi/gGUjjg6tD2hb7HDWY0o1Hwf9YSjUCN6giX1V1l1qmdIn DFSZ7RCAMtVYutcXxGW+iVQdI8kIadljV684ycHu3DGQMyhY9iA= =a3OM -END PGP SIGNATURE End Message ---
Bug#965136: libselinux: Newly versioned symbols did not bump dependency version in .symbols
Source: libselinux Version: 3.1-1 Severity: grave Tags: patch Hi, The switch to versioned symbols did not bump the version of the now versioned symbols thus packages built against 3.1-1 would pick up a dependency on the older libselinux1 package where versioned symbols were not available causing programs to fail. I've filed an MR in Salsa: https://salsa.debian.org/selinux-team/libselinux/-/merge_requests/3 . The failure can be observed at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/s/systemd/20200716_044131_250e2@/log.gz Cheers, Balint -- Balint Reczey Ubuntu & Debian Developer
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Quoting Adrian Bunk (2020-07-16 17:53:44) > On Thu, Jul 16, 2020 at 05:34:46PM +0200, Jonas Smedegaard wrote: > > Quoting Adrian Bunk (2020-07-16 17:29:17) > > > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > > > Hi, > > > > > > > > > > Does disabling optimization help? I have it disabled for these > > > > > architectures in haskell-lambdahack and it did help in that case. > > > > > > > > I will try. Thanks for the suggestion! > > > > > > "-O0 -g0" worked for me on armel, I am currently trying on mipsel what > > > the minimum required change is. > > > > As I understand it, "-O0 -g0" is not the most minimally intrusive, > > "-O0 -g0" is nearly the biggest possible hammer. Ohh, sorry: I totally misread your previous message. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
On Thu, Jul 16, 2020 at 05:34:46PM +0200, Jonas Smedegaard wrote: > Quoting Adrian Bunk (2020-07-16 17:29:17) > > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > > Hi, > > > > > > > > Does disabling optimization help? I have it disabled for these > > > > architectures in haskell-lambdahack and it did help in that case. > > > > > > I will try. Thanks for the suggestion! > > > > "-O0 -g0" worked for me on armel, I am currently trying on mipsel what > > the minimum required change is. > > As I understand it, "-O0 -g0" is not the most minimally intrusive, "-O0 -g0" is nearly the biggest possible hammer. It was my starting point for seeing that there is some possible solution available this way. > instead (as I also posted separately in more detail a moment ago) that > is --ghc-options="-optc--param -optcggc-min-expand=5" If that is sufficient it is great. Unless something changed recently no debug info is distributed for Haskell-built binaries, so -g1/-g0 does not actually make anything worse. This is what I am currently trying on eller. > - Jonas cu Adrian
Processed: affects 965033
Processing commands for cont...@bugs.debian.org: > affects 965033 src:kiwix-tools src:libeconf src:drm-info src:zim-tools Bug #965033 [meson] meson: Missing dependency on python3-pkg-resources Added indication that 965033 affects src:kiwix-tools, src:libeconf, src:drm-info, and src:zim-tools > thanks Stopping processing here. Please contact me if you need assistance. -- 965033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Quoting Adrian Bunk (2020-07-16 17:29:17) > On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > > Hi, > > > > > > Does disabling optimization help? I have it disabled for these > > > architectures in haskell-lambdahack and it did help in that case. > > > > I will try. Thanks for the suggestion! > > "-O0 -g0" worked for me on armel, I am currently trying on mipsel what > the minimum required change is. As I understand it, "-O0 -g0" is not the most minimally intrusive, instead (as I also posted separately in more detail a moment ago) that is --ghc-options="-optc--param -optcggc-min-expand=5" - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#964706: jabref: FTBFS: OOUtil.java:13: error: package com.sun.star.beans does not exist
Hi, just saw this bug while working on a patch which properly documents the library dependencies (aka "replace libreoffice-java-common in build-depends with explicit libjuh-java, libjurt-java, libridl-java, libunoil-java and add these as explicit Depends/Recommends in addition to libreoffice-java-common)... On Thu, Jul 09, 2020 at 12:45:21PM +0200, Lucas Nussbaum wrote: [...] > > Get:284 http://127.0.0.1:12990/debian sid/main amd64 liblibreoffice-java > > all 1:7.0.0~rc1-5 [1807 kB] > > Get:285 http://127.0.0.1:12990/debian sid/main amd64 libjuh-java all > > 1:7.0.0~rc1-5 [198 kB] > > Get:286 http://127.0.0.1:12990/debian sid/main amd64 libjurt-java all > > 1:7.0.0~rc1-5 [198 kB] [...] > > Get:297 http://127.0.0.1:12990/debian sid/main amd64 libridl-java all > > 1:7.0.0~rc1-5 [198 kB] > > Get:298 http://127.0.0.1:12990/debian sid/main amd64 libunoil-java all > > 1:7.0.0~rc1-5 [198 kB] > > Get:299 http://127.0.0.1:12990/debian sid/main amd64 > > libreoffice-java-common all 1:7.0.0~rc1-5 [915 kB] [...] All needed libs are installed... > > Replacing org.openoffice:juh:jar:4.1.2 -> > > org.libreoffice:juh:jar:debian > > Replacing org.openoffice:jurt:jar:4.1.2 -> > > org.libreoffice:jurt:jar:debian > > Replacing org.openoffice:ridl:jar:4.1.2 -> > > org.libreoffice:ridl:jar:debian > > Replacing org.openoffice:unoil:jar:4.1.2 -> > > org.libreoffice:unoil:jar:debian So they are found there... > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:13: > > error: package com.sun.star.beans does not exist > > import com.sun.star.beans.PropertyVetoException; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:14: > > error: package com.sun.star.beans does not exist > > import com.sun.star.beans.UnknownPropertyException; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:15: > > error: package com.sun.star.beans does not exist > > import com.sun.star.beans.XPropertySet; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:16: > > error: package com.sun.star.lang does not exist > > import com.sun.star.lang.IllegalArgumentException; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:17: > > error: package com.sun.star.lang does not exist > > import com.sun.star.lang.WrappedTargetException; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:18: > > error: package com.sun.star.text does not exist > > import com.sun.star.text.ControlCharacter; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:19: > > error: package com.sun.star.text does not exist > > import com.sun.star.text.XParagraphCursor; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:20: > > error: package com.sun.star.text does not exist > > import com.sun.star.text.XText; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:21: > > error: package com.sun.star.text does not exist > > import com.sun.star.text.XTextCursor; > > ^ > > /<>/src/main/java/net/sf/jabref/logic/openoffice/OOUtil.java:22: > > error: package com.sun.star.uno does not exist > > import com.sun.star.uno.UnoRuntime; ... but not here anymore. All of thse libs above are now dummy libs for liblibreoffice.jar. They are empty and just contain Class-Path: root@frodo:/usr/share/java# unzip juh.jar Archive: juh.jar creating: META-INF/ inflating: META-INF/MANIFEST.MF root@frodo:/usr/share/java# cat META-INF/MANIFEST.MF Manifest-Version: 1.0 Class-Path: libreoffice.jar Solar-Version: 7.0.0.2 UNO-Type-Path: Created-By: 11.0.7 (Debian) So why does the build not find it? (It might be that the Maven POMs don't specify that variable properly, but should that affect actual compilation? Is Class-Path: used?) [ When I first saw this I wondered whether the "wrong" Class-Path: in juh.jar might have to do with it. But writer2latex built fine with that and 1:7.0.0~rc2-1 (which fixed the Class-Path:) doesn't help here either.] As a workaround one might patch jabref to use libreoffice.jar directly - which is the library to use anyway. (the others are still packaged for compatibility with old packages and third-party stuff which doesn't know about libreoffice.jar...) but... Regards, Rene
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Quoting Jonas Smedegaard (2020-07-16 16:02:53) > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > Hi, > > > > Does disabling optimization help? I have it disabled for these > > architectures in haskell-lambdahack and it did help in that case. > > I will try. Thanks for the suggestion! Looking closer, it seems the better approach is to not disable optimizations completely but instead tune GCC garbage-collection. 5 years ago, Joachim suggested¹ to apply that generally to Haskell build framework but it was suggested that "[t]here are only few Haskell packages with this issue" and apparently it ended there. So I suggest to try change lambdacheck to this: # Reduce compile-time memory utilization on low-memory architectures ifneq (,$(filter $(DEB_BUILD_ARCH),mips mipsel)) DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc--param -optcggc-min-expand=5" endif Above seems to most common settings. Some has the threshold more relaxed at at 20. For pandoc I now try include armel and armhf, and lower threshold to 5. - Jonas ¹ https://bugs.debian.org/783126#10 -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
On Thu, Jul 16, 2020 at 04:02:53PM +0200, Jonas Smedegaard wrote: > Quoting Mikolaj Konarski (2020-07-16 15:50:53) > > Hi, > > > > Does disabling optimization help? I have it disabled for these > > architectures in haskell-lambdahack and it did help in that case. > > I will try. Thanks for the suggestion! "-O0 -g0" worked for me on armel, I am currently trying on mipsel what the minimum required change is. > - Jonas cu Adrian
Bug#964810: gimp: Unable to start gimp in debian unstable
Package: gimp Version: 2.10.18-1 Followup-For: Bug #964810 X-Debbugs-Cc: ze...@riseup.net Dear Maintainer, I am also affected by this bug, but starting from console, the error output is: $ gimp : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.18-1 ii libaa1 1.4p5-46+b1 ii libbabl-0.1-00.1.78-1 ii libbz2-1.0 1.0.8-3 ii libc62.31-1 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.2+dfsg-3 ii libgcc-s110.1.0-6 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgegl-0.4-00.4.24-1 ii libgexiv2-2 0.12.1-1 ii libgimp2.0 2.10.18-1 ii libglib2.0-0 2.64.4-1 ii libgs9 9.52~dfsg-1 ii libgtk2.0-0 2.24.32-4 ii libgudev-1.0-0 233-1 ii libharfbuzz0b2.6.7-1 ii libheif1 1.6.1-1+b1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:2.0.5-1 ii libjson-glib-1.0-0 1.4.4-2 ii liblcms2-2 2.9-4+b1 ii liblzma5 5.2.4-1+b1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.5-1 1.6.0-1 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.1-1 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii libpangoft2-1.0-01.44.7-4 ii libpng16-16 1.6.37-2 ii libpoppler-glib8 0.71.0-6 ii librsvg2-2 2.48.7-1 ii libstdc++6 10.1.0-6 ii libtiff5 4.1.0+git191117-2 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libwmf0.2-7 0.2.8.4-17 ii libx11-6 2:1.6.9-2+b1 ii libxcursor1 1:1.2.0-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gimp recommends: ii ghostscript 9.52~dfsg-1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help ii gvfs-backends 1.44.1-1 ii libasound21.2.2-2.3 -- no debconf information
Processed: Re: extlib: FTBFS in sid (dh_dwz failure)
Processing control commands: > affects -1 ocaml-mccs Bug #965115 [src:extlib] extlib: FTBFS in sid (dh_dwz failure) Added indication that 965115 affects ocaml-mccs -- 965115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965115: extlib: FTBFS in sid (dh_dwz failure)
control: affects -1 ocaml-mccs for some reasons, the new binutils changed the dwarf version from 2 to 0 (I tested on stretch, upgraded dwz and binutils to bullseye and reproduced the issue) readelf --debug-dump=info src/extLib.cmxs | grep -A 2 'Compilation Unit @' readelf: Warning: CU at offset 0 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 2e contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 5c contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 8a contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset b8 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset e6 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 114 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 142 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 170 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 19e contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 1cc contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 1fa contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 228 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 256 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 284 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 2b2 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 2e0 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 30e contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 33c contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 36a contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 398 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 3c6 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 0 contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 2e contains corrupt or unsupported version number: 0. readelf: Warning: CU at offset 5c contains corrupt or unsupported version number: 0. readelf: Warning: Compilation Unit @ offset 0x0: CU at offset 8a contains corrupt or unsupported version number: 0. Length:0x2a (32-bit) Version: 0 readelf: Warning: -- CU at offset b8 contains corrupt or unsupported version number: 0. Compilation Unit @ offset 0x2e: Length:0x2a (32-bit) readelf: Warning:Version: 0 CU at offset e6 contains corrupt or unsupported version number: 0. -- Compilation Unit @ offset 0x5c: readelf: Warning:Length:0x2a (32-bit)
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Quoting Mikolaj Konarski (2020-07-16 15:50:53) > Hi, > > Does disabling optimization help? I have it disabled for these > architectures in haskell-lambdahack and it did help in that case. I will try. Thanks for the suggestion! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Hi, Does disabling optimization help? I have it disabled for these architectures in haskell-lambdahack and it did help in that case. Cheers, Mikolaj On Thu, Jul 16, 2020 at 3:30 PM Sebastian Ramacher wrote: > > Source: pandoc > Version: 2.9.1.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Thanks for fixing #964822. Unfortunately pandoc now fails to build on > armel, armhf and mipsel: > | [112 of 158] Compiling Text.Pandoc.Writers.Markdown > | ghc: out of memory (requested 2097152 bytes) > | make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error > 251 > > See > https://buildd.debian.org/status/fetch.php?pkg=pandoc=armel=2.9.1.1-1=1594837537=0 > for example > > Cheers > -- > Sebastian Ramacher >
Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory
Source: pandoc Version: 2.9.1.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Thanks for fixing #964822. Unfortunately pandoc now fails to build on armel, armhf and mipsel: | [112 of 158] Compiling Text.Pandoc.Writers.Markdown | ghc: out of memory (requested 2097152 bytes) | make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 251 See https://buildd.debian.org/status/fetch.php?pkg=pandoc=armel=2.9.1.1-1=1594837537=0 for example Cheers -- Sebastian Ramacher
Bug#965111: searx: autopkgtests fails with newer python-werkzeug
Hi Ondřej, thanks for reporting that bug! Quoting Ondřej Nový (2020-07-16 12:08:04) > autopkgtests of searx fails with python-werkzeug 1.0.1+dfsg1-2. > > Details: > https://ci.debian.net/data/autopkgtest/testing/amd64/o/searx/6271348/log.gz > > Thanks for fixing. Fortunately it has already been fixed with my upload of the latest upstream version 0.17.0 yesterday: https://tracker.debian.org/news/1160354/accepted-searx-0170dfsg1-1-source-into-unstable/ And part of the upload was a version constraint on python-werkzeug >= 0.16 because searx needs werkzeug/middleware/proxy_fix.py. The autopkgtest seems to pass just fine on salsa CI: https://salsa.debian.org/debian/searx/-/jobs/868457 I guess we just wait for new results on ci.debian.net and if that passes we close the bug? The log you link to doesn't show werkzeug as being the reason (I added more debug output for the autopkgtest of 0.17.0) and I suspect the actual reason for failure was flask-babel which did: from werkzeug import ImmutableDict which is wrong for newer versions of werkzeug and has been filed as a bug here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965050 But I already did an NMU of flask-babel also yesterday, so this should also be fixed: https://tracker.debian.org/news/1160183/accepted-flask-babel-0122-1-source-into-unstable/ Thanks! cheers, josch signature.asc Description: signature
Bug#965115: extlib: FTBFS in sid (dh_dwz failure)
Source: extlib
Version: 1.7.7-1
Severity: serious
Hello, as you can see in the attached build log, the package now FTBFS.
Honestly I don't know if the error
dwz: debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs: DWARF version 0
unhandled
dh_dwz: error: dwz -- debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs
returned exit code 1
is a fault on dwz or extlib, this is why I'm ccing doko, please reassign to
binutils/dwz or whenever you think its
more appropriate
thanks
G.
[0;34mD: cmdline: build --distribution sid --buildresult
/home/locutus/pbuilder/sid_result --basetgz /home/locutus/pbuilder/sid-base.tgz
--logfile /home/locutus/pbuilder/sid_result/extlib_1.7.7-1_amd64.build --mirror
http://deb.debian.org/debian --debootstrapopts
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache
/home/locutus/pbuilder/aptcache/debian --components main contrib non-free
extlib_1.7.7-1.dsc[0m
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Thu Jul 16 12:53:15 CEST 2020[0m
[0mI: pbuilder-time-stamp: 1594896795[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz][0m
[0mI: copying local configuration[0m
[1;33mW: No local /etc/mailname to copy, relying on
/tmp/build/11969/etc/mailname to be correct[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [extlib_1.7.7-1.dsc][0m
[0mI: copying [./extlib_1.7.7.orig.tar.gz][0m
[0mI: copying [./extlib_1.7.7-1.debian.tar.xz][0m
[0mI: Extracting source[0m
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.TYiqKJZL/trustedkeys.kbx':
General error
gpgv: Signature made Tue May 19 06:38:02 2020 UTC
gpgv:using RSA key 6DE24E97ECA886CC56E6250E21B8EEF1B1893081
gpgv:issuer "glo...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./extlib_1.7.7-1.dsc
dpkg-source: info: extracting extlib in extlib-1.7.7
dpkg-source: info: unpacking extlib_1.7.7.orig.tar.gz
dpkg-source: info: unpacking extlib_1.7.7-1.debian.tar.xz
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 12)
-> Trying to add debhelper-compat=12
-> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> =
-> (not adding to debhelper-compat=12)
-> Cannot install debhelper-compat=12; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> Considering debhelper to satisfy the dependency
-> Considering build-dep ocaml-nox
-> Trying to add ocaml-nox
-> Considering build-dep cppo
-> Trying to add cppo
-> Considering build-dep ocaml-findlib
-> Trying to add ocaml-findlib
-> Considering build-dep libfindlib-ocaml-dev
-> Trying to add libfindlib-ocaml-dev
-> Considering build-dep dh-ocaml
-> Trying to add dh-ocaml
-> Installing debhelper ocaml-nox cppo ocaml-findlib libfindlib-ocaml-dev
dh-ocaml
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils dh-autoreconf
dh-strip-nondeterminism dwz file gettext gettext-base groff-base
intltool-debian libarchive-zip-perl libcroco3 libdebhelper-perl libelf1
libfile-stripnondeterminism-perl libfindlib-ocaml libglib2.0-0 libicu67
libmagic-mgc libmagic1 libncurses-dev libncurses5-dev libncurses6
libpipeline1 libsigsegv2 libsub-override-perl libtool libuchardet0 libxml2
m4 man-db ocaml-base-nox ocaml-compiler-libs ocaml-interp po-debconf
sensible-utils
Suggested packages:
autoconf-archive gnu-standards autoconf-doc dh-make git gettext-doc
libasprintf-dev libgettextpo-dev groff ncurses-doc libtool-doc gfortran
| fortran95-compiler gcj-jdk m4-doc apparmor less www-browser camlp4
ocaml-doc tuareg-mode libmail-box-perl
Recommended packages:
curl | wget | lynx libarchive-cpio-perl libglib2.0-data shared-mime-info
xdg-user-dirs libgpm2 libltdl-dev ocaml-man ledit | readline-editor
libmail-sendmail-perl
The following NEW packages will be installed:
autoconf automake autopoint autotools-dev
Bug#965114: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency
Package: golang-github-shenwei356-bwt Severity: serious Justification: FTBFS While trying to rebuild this package, it appears it build depends on the package golang-github-shenwei356-bpool-dev Find the buildlog attached to this email. golang-github-shenwei356-bwt_0.0~git20200418.ae79c98-2 Description: Binary data -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: closing 964628
Processing commands for cont...@bugs.debian.org: > close 964628 Bug #964628 [src:python3-stdlib-extensions] python3-stdlib-extensions: FTBFS: unsatisfiable build-dependencies: libpython3.9-dev, libpython3.9-dbg, python3.9-dev:any, python3.9-dbg:any Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 964628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965111: searx: autopkgtests fails with newer python-werkzeug
correct link, sorry: https://ci.debian.net/data/autopkgtest/testing/amd64/s/searx/6271353/log.gz -- Best regards Ondřej Nový
Bug#965110: oca-core: autopkgtests fails with newer python-werkzeug
Package: oca-core Version: 11.0.20191007-4 Severity: serious Hi, autopkgtests of oca-core fails with python-werkzeug 1.0.1+dfsg1-2. Details: https://ci.debian.net/data/autopkgtest/testing/amd64/o/oca-core/6271348/log.gz Thanks for fixing. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages oca-core depends on: ii adduser 3.118 pn fonts-font-awesome pn fonts-glyphicons-halflings pn fonts-inconsolata ii libjs-underscore1.9.1~dfsg-1 ii lsb-base11.1.0 pn node-less pn postgresql-client ii python3 3.8.2-3 ii python3-babel 2.8.0+dfsg.1-3 ii python3-dateutil2.8.1-4 pn python3-decorator ii python3-docutils0.16+dfsg-2 pn python3-feedparser pn python3-gevent pn python3-html2text ii python3-jinja2 2.11.2-1 ii python3-lxml4.5.0-1.2 pn python3-mako ii python3-mock4.0.2-1 pn python3-ofxparse pn python3-passlib ii python3-pil 7.0.0-4+b1 pn python3-psutil pn python3-psycopg2 pn python3-pydot pn python3-pyldap ii python3-pyparsing 2.4.7-1 pn python3-pypdf2 pn python3-qrcode pn python3-reportlab ii python3-requests2.23.0+dfsg-2 pn python3-serial pn python3-suds ii python3-tz 2020.1-2 pn python3-usb pn python3-vatnumber pn python3-vobject pn python3-werkzeug pn python3-xlsxwriter pn python3-xlwt ii python3-yaml5.3.1-2 Versions of packages oca-core recommends: pn postgresql pn python3-num2words pn wkhtmltopdf oca-core suggests no packages.
Bug#964670: marked as done (gsettings-qt: FTBFS: QQmlComponent: Component is not ready)
Your message dated Thu, 16 Jul 2020 09:34:44 + with message-id and subject line Bug#964670: fixed in gsettings-qt 0.2-2 has caused the Debian Bug report #964670, regarding gsettings-qt: FTBFS: QQmlComponent: Component is not ready 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.) -- 964670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gsettings-qt Version: 0.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/GSettings' > /usr/lib/qt5/bin/qmake -install qinstall -exe libGSettingsQmlPlugin.so > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/GSettings.1.0/libGSettingsQmlPlugin.so > /usr/lib/qt5/bin/qmake -install qinstall /<>/GSettings/qmldir > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/GSettings.1.0/qmldir > export LD_PRELOAD=../src/libgsettings-qt.so.1; /usr/lib/qt5/bin/qmlplugindump > -notrelocatable GSettings 1.0 .. > > /<>/debian/tmp//usr/lib/x86_64-linux-gnu/qt5/qml/GSettings.1.0/plugins.qmltypes > : --strip-unneeded > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/GSettings.1.0/libGSettingsQmlPlugin.so > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42' > QQmlComponent: Component is not ready > make[2]: *** [Makefile.gsettings-qt:440: install_qmltypes] Error 3 The full build log is available from: http://qa-logs.debian.net/2020/07/09/gsettings-qt_0.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: gsettings-qt Source-Version: 0.2-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of gsettings-qt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated gsettings-qt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Jul 2020 10:59:41 + Source: gsettings-qt Architecture: source Version: 0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 964670 Changes: gsettings-qt (0.2-2) unstable; urgency=medium . * debian/upstream/metadata: + Drop obsolete Name: field. * debian/rules: + Don't run dh_auto_install in parallel. (Closes: #964670) Checksums-Sha1: 911e4571305d58b3dc2e5d8f29ecc6cc1f269ffb 2467 gsettings-qt_0.2-2.dsc 2e93e1305905f6e6f6d647d798136248d97375ae 9332 gsettings-qt_0.2-2.debian.tar.xz e9a7aabaa87e87c13755ed3dd2017787372d739b 12784 gsettings-qt_0.2-2_source.buildinfo Checksums-Sha256: 9a0073e75fa2a0ce1195741ce72d7227a175106a3697c38e371c9cdd6af4816c 2467 gsettings-qt_0.2-2.dsc d8f1e818239fd2f8b693b6d267e7d2ed05bc6df5307355c8bc898a9df0384eec 9332 gsettings-qt_0.2-2.debian.tar.xz 5c2fdecfe986a46a9f79c866e6a7d59930d02ff284ea64c1b17488cb1372e7f4 12784 gsettings-qt_0.2-2_source.buildinfo Files: 0714cb0639bbc604300933a0479744ed 2467 libs optional gsettings-qt_0.2-2.dsc 73dcf57cabb788a7beabd1ff5e377b71 9332 libs optional gsettings-qt_0.2-2.debian.tar.xz da1cdcbf63f10c2dd081876ec398cf7e 12784 libs optional gsettings-qt_0.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl8QGtAVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxtP4P8wUo43sEm8EJtAYlIwg6bie18+/K MyO/JpwMJWEn9j8Wk4XpD+eQaVw/hK9RQH7wLxtRdq60vlhS0CHPVgzc16QVYTOI /at/N8Ofkb4L5aDhF1TbIkmKCDOZHfOTI2vPWKEl5Gk+aXq9+jVgBQp/0b7isuCG mM+ky293tFSLV9i3Xu3x9LaTsr6nEFB8DxJsMCS/0hghcRjl76QFyEp70eM66vxQ lu5oX6QT5jgnfaw6m6UBwoSJk+D3TGYjwkVwlJKyqjd9vKnnPFA3Glpje+VpBViK
Bug#965106: marked as done (node-iconv-lite FTBFS: test failure)
Your message dated Thu, 16 Jul 2020 09:37:31 + with message-id and subject line Bug#965106: fixed in node-iconv-lite 0.5.1-3 has caused the Debian Bug report #965106, regarding node-iconv-lite FTBFS: test failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-iconv-lite Version: 0.5.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/node-iconv-lite.html https://buildd.debian.org/status/fetch.php?pkg=node-iconv-lite=all=0.5.1-2=1594818900=0 ... 36 passing (31s) 1 failing 1) Full DBCS encoding tests Decode DBCS encoding 'gb18030': Error: Timeout of 1ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/<>/test/dbcs-test.js) at Test.Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:463:10) at done (/usr/share/nodejs/mocha/lib/runnable.js:333:18) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:418:7) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:382:7) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:541:10) at /usr/share/nodejs/mocha/lib/runner.js:667:12 at next (/usr/share/nodejs/mocha/lib/runner.js:450:14) at /usr/share/nodejs/mocha/lib/runner.js:460:7 at next (/usr/share/nodejs/mocha/lib/runner.js:362:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:428:5) at processImmediate (internal/timers.js:456:21) dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary-indep] Error 25 --- End Message --- --- Begin Message --- Source: node-iconv-lite Source-Version: 0.5.1-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-iconv-lite, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-iconv-lite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Jul 2020 11:01:00 +0200 Source: node-iconv-lite Architecture: source Version: 0.5.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 965106 Changes: node-iconv-lite (0.5.1-3) unstable; urgency=medium . * Team upload * Increase test timeout (Closes: #965106) Checksums-Sha1: 9e61cc7b41e516c9d65905eea1efb3fbb0eac08d 2451 node-iconv-lite_0.5.1-3.dsc 02a0434c33dc8774a65d1ccb9079f1480aae6f33 3696 node-iconv-lite_0.5.1-3.debian.tar.xz Checksums-Sha256: 3b25c7029dbfb8868a6eded56df266e1482921238139d38b5da0e8087bd3d5b6 2451 node-iconv-lite_0.5.1-3.dsc bed9e27b93d5a214bd736acbef4efc71c38f518842ffb7e8fac163ab1aa57ccc 3696 node-iconv-lite_0.5.1-3.debian.tar.xz Files: 6bcd1374ec35430c2cac1b15f7ccb76f 2451 javascript optional node-iconv-lite_0.5.1-3.dsc b226bbf931abfacecf6ec44b7235f1b5 3696 javascript optional node-iconv-lite_0.5.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl8QGoMACgkQ9tdMp8mZ 7unSDA//ULxizWmW0cXdA5NE8lxJJ9tUMMOi3/EOKva8XnQC4KCk6MtExYduIZeX 6RIxwgwv/z4J1S0/kZTe2pE7BGBdFVAu2FP6GclEDSa78UX27F3W1ZSpFSGJ6WC9 mitjEioLacYZqS4LYs2p4c1OngZ2WQUoZt+xdkWtY8iv4FPxbVqefoJRf9LLUJHe IIc4QOZkUEU0HAUXfOPRqi90zbIuZIPfNU6VIh8vnNN0qNlWDFO8WtRaG26jXFQa WM4C4yNZ1NDitF1i1Lkl9kMnWK4SHfbwi7EywJpTvKRPMI/N1NUTY2yhyFwbm0HB aNtRXn2q6v5TEuumGSem2CKWBLLbxlTVtamqaMgf1qbyiUqQwOl3yeXjZppMLXc2 j4z5v34ZvYWlITnIFknn0Ff3eYH2fxqOv2WAoBbFx+Vo1PNNqQ0vEv06ztaSAT9g KGd6H8rSxHslahO6MVazSNa6UZEjnG5DJ0CrdEyTb08nd0hpyRvaGZHCbjtnKAfJ xhHvXZ2P0kYDaYHM9G1imSdeSX/xJIPZMgZeIFQxP6yeYi+3YWpqpAHKGxG/rtTx xeoTgADyg98m2VZiYQ2IjZrOaRnrebRpOApeXwfWxdnOSQ4+k4j2L3rYiawEzZih uZo6Q8CR0mwJ9ERZnKakiH6RxIBeIwk//KXOueWFg7yVf0pc5hw= =Skhq -END PGP SIGNATURE End Message ---
Processed: Bug#965106 marked as pending in node-iconv-lite
Processing control commands: > tag -1 pending Bug #965106 [src:node-iconv-lite] node-iconv-lite FTBFS: test failure Added tag(s) pending. -- 965106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965106: marked as pending in node-iconv-lite
Control: tag -1 pending Hello, Bug #965106 in node-iconv-lite reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-iconv-lite/-/commit/9df715ee69cc266bab612392dd4c45a57fb90698 Increase test timeout Closes: #965106 (this message was generated automatically) -- Greetings https://bugs.debian.org/965106
Bug#915761: marked as done (libosl FTBFS with boost 1.67)
Your message dated Thu, 16 Jul 2020 09:00:14 + with message-id and subject line Bug#915761: fixed in libosl 0.8.0-2 has caused the Debian Bug report #915761, regarding libosl FTBFS with boost 1.67 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.) -- 915761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libosl Version: 0.8.0-1.4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libosl.html ... /build/1st/libosl-0.8.0/full/osl/game_playing/weightTracer.cc: In member function 'virtual const osl::Move osl::game_playing::DeterminateWeightTracer::selectMove() const': /build/1st/libosl-0.8.0/full/osl/game_playing/weightTracer.cc:200:30: error: 'next' is not a member of 'boost' if (it->weight != boost::next(it)->weight) ^~~~ The Ubuntu diff seems to contain a fix. --- End Message --- --- Begin Message --- Source: libosl Source-Version: 0.8.0-2 Done: Yann Dirson We believe that the bug you reported is fixed in the latest version of libosl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Dirson (supplier of updated libosl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Jul 2020 00:26:45 +0200 Source: libosl Binary: libosl-dev libosl-doc libosl1v5 libosl1v5-dbgsym Architecture: source amd64 all Version: 0.8.0-2 Distribution: unstable Urgency: medium Maintainer: Yann Dirson Changed-By: Yann Dirson Description: libosl-dev - library for Shogi playing programs libosl-doc - library for Shogi playing programs libosl1v5 - library for Shogi playing programs Closes: 915761 964732 Changes: libosl (0.8.0-2) unstable; urgency=medium . * New maintainer, raise package from the grave (Closes: #964732). * Add 0001-Import-svn-r4566.patch to sync with upstream svn. * Fix build with boost 1.67+ (Closes: #915761). * Set DH_VERBOSE=1. * Switch to debhelper compat v12, * remove non-matching install patterns * update doc-base to point to doc in doc/libosl-dev/ * remove now-unnecessary dh '--parallel' option * Update Vcs-* for new salsa repo. * Explicitly link with relevant boost libraries. * Bump Standards-Version to 4.5.0. * Fix 'unkown' typo (lintian). Checksums-Sha1: 49bdacc5fbc32c70e87c41e8b5346d5696ca7a5e 2035 libosl_0.8.0-2.dsc 91375efc2ff8155ff13c6354f7a530a484d55093 1027125 libosl_0.8.0.orig.tar.gz e2721b41da89d00c940363be804cf748cb1ca638 10524 libosl_0.8.0-2.debian.tar.xz 3b10a2a2cb7c74351bc2e4d225647f59bdee3bac 1830860 libosl-dev_0.8.0-2_amd64.deb 8536caafe9c5d50ecaceeb09cb0d1a657ed367d9 2302268 libosl-doc_0.8.0-2_all.deb 162cf7f7bbd33e803b1e7175ed9f33411146cb86 24912204 libosl1v5-dbgsym_0.8.0-2_amd64.deb f6f32e491df4facdb1fe75cfa1d663a696707b3a 1321092 libosl1v5_0.8.0-2_amd64.deb c80da69261dd73366edd40024a7f64a92907822b 13496 libosl_0.8.0-2_amd64.buildinfo Checksums-Sha256: 158df5b63af042a235c08832e174893f4ec36121f481077a13ca5efa234dcd1b 2035 libosl_0.8.0-2.dsc 96c888da70a7031468cf20f7762b667a7dd39ee33de95a085b09d0cf3875c1c0 1027125 libosl_0.8.0.orig.tar.gz 7eed7dd21d3eae1f3901930edfb3c1bb4fd52761eeefeb4a226d3e40d11262db 10524 libosl_0.8.0-2.debian.tar.xz ce7b0403aa8d744456d1cdb1815cf2efec203da5f41312538b18838536762fd8 1830860 libosl-dev_0.8.0-2_amd64.deb 53ce8e3ef04215932ec7c434b307c29e657b21a42df16143c7b3152e95651936 2302268 libosl-doc_0.8.0-2_all.deb 3f6b8fa6f9e623c99b589ecfc9e648182930980ce47fdb9e679ae0a868982b09 24912204 libosl1v5-dbgsym_0.8.0-2_amd64.deb 234e95575b49a9d1245233d8c7bf53c80760d7a0c1ec5f8e1b4e0d6fc3bf3dda 1321092 libosl1v5_0.8.0-2_amd64.deb 5d91e243b35d41e3d0a9d044a3936fb69bf8d0b586eb2af2a2a777adfc497237 13496 libosl_0.8.0-2_amd64.buildinfo Files: a2da03923a738ede352b9dc62f4026b3 2035 libs optional libosl_0.8.0-2.dsc 9cecc8221c773277640556f5352851e2 1027125 libs optional libosl_0.8.0.orig.tar.gz ae0b2e5b6fadaab509de77fc723e20b1 10524 libs optional libosl_0.8.0-2.debian.tar.xz
Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error
Hi, thanks for your bugreport! Quoting Joseph Nuthalapati (2020-07-16 04:06:35) > There appears to be a missing Python dependency (werkzeug.contrib) in > the new Searx 17.0 package uploaded to unstable. > > Tested in Debian unstable container. > > Error log from /var/log/uwsgi/app/searx.log > > --- > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in > > from werkzeug.contrib.fixers import ProxyFix > ModuleNotFoundError: No module named 'werkzeug.contrib' > Thu Jul 16 07:22:32 2020 - unable to load app 0 (mountpoint='') > (callable not found or import error) > Thu Jul 16 07:22:32 2020 - *** no app loaded. going in full dynamic mode *** > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in > > from werkzeug.contrib.fixers import ProxyFix > ModuleNotFoundError: No module named 'werkzeug.contrib' can you tell me how to reproduce the error? Weirdly, line 40 in webapp.py does not contain the line from your backtrace above: https://sources.debian.org/src/searx/0.17.0+dfsg1-1/searx/webapp.py/ Also, the autopkgtest is passing just fine: https://salsa.debian.org/debian/searx/-/pipelines/156223 So I wonder how it can be that it runs fine for me and on salsa ci. Maybe some additional tests should be added which trigger your problem? Also weird, then I don't find the string "werkzeug.contrib" at all in the searx sources in Debian or in the upstream git: https://github.com/asciimoo/searx/search?q=werkzeug.contrib_q=werkzeug.contrib Do you have an idea? Thanks! cheers, josch signature.asc Description: signature
Bug#965106: node-iconv-lite FTBFS: test failure
Source: node-iconv-lite Version: 0.5.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/node-iconv-lite.html https://buildd.debian.org/status/fetch.php?pkg=node-iconv-lite=all=0.5.1-2=1594818900=0 ... 36 passing (31s) 1 failing 1) Full DBCS encoding tests Decode DBCS encoding 'gb18030': Error: Timeout of 1ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/<>/test/dbcs-test.js) at Test.Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:463:10) at done (/usr/share/nodejs/mocha/lib/runnable.js:333:18) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:418:7) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:382:7) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:541:10) at /usr/share/nodejs/mocha/lib/runner.js:667:12 at next (/usr/share/nodejs/mocha/lib/runner.js:450:14) at /usr/share/nodejs/mocha/lib/runner.js:460:7 at next (/usr/share/nodejs/mocha/lib/runner.js:362:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:428:5) at processImmediate (internal/timers.js:456:21) dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary-indep] Error 25
Processed: tagging 965091
Processing commands for cont...@bugs.debian.org: > tags 965091 + upstream Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 965091 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=26248
Processing commands for cont...@bugs.debian.org: > forwarded 965091 https://sourceware.org/bugzilla/show_bug.cgi?id=26248 Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=26248'. > thanks Stopping processing here. Please contact me if you need assistance. -- 965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 959544
Processing commands for cont...@bugs.debian.org: > tags 959544 + fixed-upstream Bug #959544 [src:python-maxminddb] python-maxminddb: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 959544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952673: does not start automatically anymore on fresh installs
El 10/07/20 a las 18:50, Daniel Baumann escribió: > On 7/10/20 3:13 PM, Santiago Ruano Rincón wrote: > > I'd rather downgrade severity to important. > > i'd rather not - either it's a bug and then it should be fixed, or, if > the new behaviour is on purpose, then it needs to be documented and > handled for upgrades. > > in either way, upgrading buster->bullseye leaves systems without working > DNS, which deserves severity serious. Ah, you're right. I thought kresd continued to be enabled when upgrading to 5.x. I leave this as a note: kresd upstream removed systemd sockets support since 5.0: https://gitlab.nic.cz/knot/knot-resolver/-/issues/485 From NEWS: Knot Resolver 5.0.0 (2020-01-27) Incompatible changes - see upgrading guide: https://knot-resolver.readthedocs.io/en/stable/upgrading.html - systemd sockets are no longer supported (#485) ... Also, upstream includes maintainer scripts to handle changes during upgrading. Cheers, -- Santiago signature.asc Description: PGP signature
