Bug#973981: elfutils FTCBFS: missing native dependencies for libdebuginfod
Source: elfutils Version: 0.182-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs elfutils fails to cross build from source. It has two build passes, a native one and a cross one. The native one misses dependencies for libdebuginfod. As it turns out, we don't actually need a full libdebuginfod nor a debuginfod in that native pass at all. elfutils consinders this a bootstrap build and supports it via --enable-libdebuginfod=dummy. That's what the attached patch passes. Please consider applying it. Helmut diff --minimal -Nru elfutils-0.182/debian/changelog elfutils-0.182/debian/changelog --- elfutils-0.182/debian/changelog 2020-11-07 10:22:37.0 +0100 +++ elfutils-0.182/debian/changelog 2020-11-08 15:38:00.0 +0100 @@ -1,3 +1,11 @@ +elfutils (0.182-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: perform bootstrap build with dummy libdebuginfod and without +debuginfod. (Closes: #-1) + + -- Helmut Grohne Sun, 08 Nov 2020 15:38:00 +0100 + elfutils (0.182-1) unstable; urgency=medium * New upstream release. diff --minimal -Nru elfutils-0.182/debian/rules elfutils-0.182/debian/rules --- elfutils-0.182/debian/rules 2020-11-07 10:22:37.0 +0100 +++ elfutils-0.182/debian/rules 2020-11-08 15:38:00.0 +0100 @@ -38,7 +38,8 @@ dh_autoreconf ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE)) ./configure --enable-maintainer-mode \ - --$(if $(filter pkg.elfutils.nodebuginfod,$(DEB_BUILD_PROFILES)),dis,en)able-debuginfod + --enable-libdebuginfod=dummy \ + --disable-debuginfod $(MAKE) $(MAKEFLAGS) $(MAKE) clean endif
Bug#973978: suitename FTCBFS: hard codes the build architecture compiler as linker
Source: suitename Version: 0.3.070919+git20180613.ebb1325-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs suitename fails to cross build from source, because its Makefiles hard code the build architecture compiler "cc" as linker. Replacing it with the $(CC) variable makes cross building work. Please consider applying the attached patch. Helmut --- suitename-0.3.070919+git20180613.ebb1325.orig/Makefile +++ suitename-0.3.070919+git20180613.ebb1325/Makefile @@ -18,10 +18,10 @@ suitenout.h suitename: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) debug: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) clean: rm -f *.o --- suitename-0.3.070919+git20180613.ebb1325.orig/Makefile.linux +++ suitename-0.3.070919+git20180613.ebb1325/Makefile.linux @@ -13,10 +13,10 @@ # - HEADERS = suitename.h suitenscrt.h suitenutil.h suiteninit.h suiteninpt.h suitenout.h suitename: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) $(LDFLAGS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) $(LDFLAGS) debug: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) clean: rm -f *.o --- suitename-0.3.070919+git20180613.ebb1325.orig/Makefile.macOSX +++ suitename-0.3.070919+git20180613.ebb1325/Makefile.macOSX @@ -18,10 +18,10 @@ suitenout.h suitename: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) debug: $(OBJS) - cc -o suitename $(CFLAGS) $(OBJS) $(LIBS) + $(CC) -o suitename $(CFLAGS) $(OBJS) $(LIBS) clean: rm -f *.o
Bug#972488: libgpiod FTCBFS: python + help2man
Control: reopen -1 On Mon, Oct 19, 2020 at 09:33:23AM +0200, Helmut Grohne wrote: > For libgpiod, by far the simplest option was using generated pages. The proposed patch was only partially applied. > +--- libgpiod-1.5.2.orig/man/Makefile.am > libgpiod-1.5.2/man/Makefile.am > +@@ -6,10 +6,10 @@ > + # Copyright (C) 2019 Bartosz Golaszewski > + # > + > +-if WITH_MANPAGES > +- > + dist_man1_MANS = gpiodetect.man gpioinfo.man gpioget.man gpioset.man > gpiofind.man gpiomon.man > + > ++if WITH_HELP2MAN > ++ > + %.man: $(top_builddir)/tools/$(*F) > + help2man $(top_builddir)/tools/$(*F) --include=$(srcdir)/template > --output=$(builddir)/$@ --no-info > + This is crucial and seems to be missing. Helmut
Bug#973980: crystal-facet-uml FTCBFS: runs cmake for the build architecture
Source: crystal-facet-uml Version: 1.25.1-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs crystal-facet-uml fails to cross build from source, because it does not pass cross flags to cmake. The easiest way of doing so - using dh_auto_configure - makes crystal-facet-uml cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru crystal-facet-uml-1.25.1/debian/changelog crystal-facet-uml-1.25.1/debian/changelog --- crystal-facet-uml-1.25.1/debian/changelog 2020-11-02 09:22:50.0 +0100 +++ crystal-facet-uml-1.25.1/debian/changelog 2020-11-07 12:33:00.0 +0100 @@ -1,3 +1,10 @@ +crystal-facet-uml (1.25.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1) + + -- Helmut Grohne Sat, 07 Nov 2020 12:33:00 +0100 + crystal-facet-uml (1.25.1-1) unstable; urgency=medium [ Andreas Warnke ] diff --minimal -Nru crystal-facet-uml-1.25.1/debian/rules crystal-facet-uml-1.25.1/debian/rules --- crystal-facet-uml-1.25.1/debian/rules 2020-11-02 09:02:03.0 +0100 +++ crystal-facet-uml-1.25.1/debian/rules 2020-11-07 12:32:59.0 +0100 @@ -15,12 +15,11 @@ dh $@ override_dh_auto_configure: - #dh_auto_configure -- # -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) - cmake -G 'Unix Makefiles' \ - -DCMAKE_INSTALL_PREFIX=/usr \ + dh_auto_configure -- \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DCMAKE_BUILD_TYPE=Release - DEB_BUILD_HARDENING=1 make VERBOSE=1 +override_dh_auto_build: + DEB_BUILD_HARDENING=1 dh_auto_build get-orig-source: uscan --noconf --force-download --rename --download-current-version --destdir=..
Bug#973982: xeus FTBFS with the nocheck build profile
Source: xeus Version: 0.24.2-2 Tags: ftbfs patch User: debian-cr...@lists.debian.org Usertags: ftcbfs xeus fails to build from source when built with the nocheck build profile, because doing so disables the googletest dependency, but passing GTEST_SRC_DIR still enables building tests, which fails due to the deactivated dependency. This happens to also break cross builds. Please consider applying the attached patch. Helmut diff --minimal -Nru xeus-0.24.2/debian/changelog xeus-0.24.2/debian/changelog --- xeus-0.24.2/debian/changelog2020-10-29 21:21:39.0 +0100 +++ xeus-0.24.2/debian/changelog2020-11-07 12:49:39.0 +0100 @@ -1,3 +1,10 @@ +xeus (0.24.2-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with nocheck profile. (Closes: #-1) + + -- Helmut Grohne Sat, 07 Nov 2020 12:49:39 +0100 + xeus (0.24.2-2) unstable; urgency=medium * Source-only upload diff --minimal -Nru xeus-0.24.2/debian/rules xeus-0.24.2/debian/rules --- xeus-0.24.2/debian/rules2020-10-29 21:21:39.0 +0100 +++ xeus-0.24.2/debian/rules2020-11-07 12:49:39.0 +0100 @@ -3,5 +3,10 @@ %: dh $@ +CMAKE_FLAGS = -DXEUS_DISABLE_ARCH_NATIVE=1 +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) +CMAKE_FLAGS += -DGTEST_SRC_DIR=/usr/src/googletest +endif + override_dh_auto_configure: - dh_auto_configure -- -DXEUS_DISABLE_ARCH_NATIVE=1 -DGTEST_SRC_DIR=/usr/src/googletest + dh_auto_configure -- $(CMAKE_FLAGS)
Bug#973979: dbmix FTCBFS: confuses build and host architecture
Source: dbmix Version: 0.9.8-7 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs dbmix fails to cross build from source, because it confuses the terms build architecture and host architecture in a quite obvious way. Please consider applying the attached patch. Helmut diff -u dbmix-0.9.8/debian/changelog dbmix-0.9.8/debian/changelog --- dbmix-0.9.8/debian/changelog +++ dbmix-0.9.8/debian/changelog @@ -1,3 +1,9 @@ +dbmix (0.9.8-8) UNRELEASED; urgency=medium + + * Fix FTCBFS: Fix build vs host confusion. (Closes: #-1) + + -- Helmut Grohne Sat, 07 Nov 2020 20:26:52 +0100 + dbmix (0.9.8-7) unstable; urgency=medium * QA upload. diff -u dbmix-0.9.8/debian/rules dbmix-0.9.8/debian/rules --- dbmix-0.9.8/debian/rules +++ dbmix-0.9.8/debian/rules @@ -13,7 +13,7 @@ ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) confflags += $(DEB_HOST_GNU_TYPE) else - confflags += --host $(DEB_BUILD_GNU_TYPE) --build $(DEB_HOST_GNU_TYPE) + confflags += --host $(DEB_HOST_GNU_TYPE) --build $(DEB_BUILD_GNU_TYPE) endif CFLAGS=-Wall -g
Bug#973977: centrifuge FTCBFS: uses uname for bits detection
Source: centrifuge Version: 1.0.3-6 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs centrifuge fails to cross build from source, because its Makefile detects a -m64 flag from uname and that can happen to be the wrong result. The attached patch passes dpkg's view of bits and generally removes any -m64 flag unneeded on Debian toolchains. Surprisingly it still fails to build due to narrowing conversions. I suspect that there is a difference in the cross toolchain. Please consider applying the attached patch and close this bug when doing so. Helmut diff --minimal -Nru centrifuge-1.0.3/debian/changelog centrifuge-1.0.3/debian/changelog --- centrifuge-1.0.3/debian/changelog 2020-11-07 07:26:48.0 +0100 +++ centrifuge-1.0.3/debian/changelog 2020-11-08 07:29:26.0 +0100 @@ -1,3 +1,10 @@ +centrifuge (1.0.3-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Improve cross building: Don't detect -m64 from uname. (Closes: #-1) + + -- Helmut Grohne Sun, 08 Nov 2020 07:29:26 +0100 + centrifuge (1.0.3-6) unstable; urgency=medium * Fix patch for other architectures than amd64 diff --minimal -Nru centrifuge-1.0.3/debian/rules centrifuge-1.0.3/debian/rules --- centrifuge-1.0.3/debian/rules 2020-11-07 07:26:48.0 +0100 +++ centrifuge-1.0.3/debian/rules 2020-11-08 07:29:24.0 +0100 @@ -11,6 +11,9 @@ %: dh $@ --with python3 +override_dh_auto_build: + dh_auto_build -- BITS=$(DEB_HOST_ARCH_BITS) BITS_FLAG= + override_dh_auto_install: dh_auto_install -- prefix=/usr/lib/centrifuge mv debian/$(DEB_SOURCE)/usr/lib/centrifuge/bin/* debian/$(DEB_SOURCE)/usr/lib/centrifuge/
Bug#973975: ITP: node-prompts -- Nodejs lightweight, beautiful and user-friendly interactive prompts
Package: wnpp Severity: wishlist Owner: Xavier Guimard X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: node-prompts Version : 2.4.0 Upstream Author : Terkel Gjervig Nielsen * URL : https://github.com/terkelg/prompts * License : Expat Programming Lang: JavaScript Description : Nodejs lightweight, beautiful and user-friendly interactive prompts prompts permits to easy use cli prompts to enquire users for information: * User friendly: prompt uses layout and colors to create beautiful cli interfaces. * Promised: uses promises and `async`/`await`. No callback hell. * Flexible: all prompts are independent and can be used on their own. * Testable: provides a way to submit answers programmatically. * Unified: consistent experience across all [prompts](#-types). node-prompts is a dependency of node-jest, needed to fix this package (2 RC bugs)
Bug#973894: rr: Improve reproducibility
Hello Chris,
thanks for the pointers.
By enabling fixfilepath [1] the build it is automatically using
-ffile-prefix-map.
This seems also the case for the reproducible-builds.org results already [2].
Therefore I assume the compilation of the .c* files is already good.
And the -ffile-prefix-map part is superfluous in my initial patch.
The remaining files embedding the build path have all a .S file ending.
When I tested to add dpkg-buildflags's CFLAGS to the command line for such a .S
file,
the build path still ended up in the .S.o file.
Therefore the attempt to use of "-Wa,--debug-prefix-map,${CMAKE_SOURCE_DIR}=.".
This leads to the question if /usr/bin/cc is on fault and should forward
the option -ffile-prefix-map as --debug-prefix-map to /usr/bin/as?
Or does dpkg provide other flags for assembly files?
Kind regards,
Bernhard
[1]
export DEB_BUILD_OPTIONS="reproducible=+fixfilepath"
dpkg-buildpackage -uc
[2]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/rr.html
DEB_BUILD_OPTIONS="buildinfo=+all reproducible=+all parallel=15"
[3]
$ pwd
/home/benutzer/source/rr/try3/rr-5.4.0/build
$ find -iname "*.o" | xargs -d\\n grep try3 -c | grep -v -E ":0$" | sort
./build/CMakeFiles/cpuid_32.dir/32/x86/cpuid_loop.S.o:3
./build/CMakeFiles/rraudit_32.dir/32/preload/raw_syscall.S.o:3
./build/CMakeFiles/rraudit.dir/src/preload/raw_syscall.S.o:3
./build/CMakeFiles/rrpreload_32.dir/32/preload/raw_syscall.S.o:3
./build/CMakeFiles/rrpreload_32.dir/32/preload/syscall_hook.S.o:3
./build/CMakeFiles/rrpreload.dir/src/preload/raw_syscall.S.o:3
./build/CMakeFiles/rrpreload.dir/src/preload/syscall_hook.S.o:3
Bug#973973: plasma-workspace: screen looking does not work: kscreenlocker: Greeter Process not available
Martin Steigerwald - 08.11.20, 14:24:11 CET: > On pressing Ctrl-Alt-L or using one of the 'qdbus' commands I see the > following messages in ~/.xsession-errors: > > kscreenlocker: Greeter Process not available […] After another apt dist-upgrade today and after rebooting screenlocking works as usual. Yet the relevant packages have been installed before, they were updated yesterday, maybe the issue happened due to the upgrade? I think I did not restart after this update as it appeared minor to me. If this is to be expected while upgrading while in the session, please close the bug. I will look how it works now. Start-Date: 2020-11-07 09:49:21 Commandline: apt dist-upgrade Requested-By: martin (1000) Install: […] libkscreenlocker5:amd64 (5.19.5-2, 5.19.5-3), […] kde- config-screenlocker:amd64 (5.19.5-2, 5.19.5-3), […] End-Date: 2020-11-07 09:57:55 Ciao, -- Martin
Bug#973974: RFP: grab -- simple but very fast grep
Package: wnpp Severity: wishlist * Package name: grab Upstream Author : Sebastian Krahmer * URL : https://github.com/stealth/grab * License : BSD Variant Programming Lang: C++ Description : simple but very fast grep https://github.com/stealth/grab > This is my own, experimental, parallel version of grep so I can test > various strategies to speed up access to large directory trees. On > Flash storage or SSDs, you can easily outsmart common greps by up a > factor of 8.
Bug#973973: plasma-workspace: screen looking does not work: kscreenlocker: Greeter Process not available
Package: plasma-workspace Version: 4:5.19.5-3 Severity: important Dear Maintainer, apparently it does not happen to everyone who updated to Plasma 5.19.5, but it definitely happened here: - The screen is not locked after standby or hibernating to disk although the option in Systemsettings is set - I cannot lock the screen manually by pressing Ctrl-Alt-L. - I cannot lock the screen with a DBUS command, I tried: - qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock - qdbus org.kde.ksmserver /ScreenSaver org.freedesktop.ScreenSaver.Lock On pressing Ctrl-Alt-L or using one of the 'qdbus' commands I see the following messages in ~/.xsession-errors: kscreenlocker: Greeter Process not available ktp-kded-module: "screen-saver-away" state change: TelepathyKDEDModulePlugin::Enabled ktp-kded-module: plugin queue activation: "unset" "" I think the issue is that the greeter process is not available. If Martin Graesslin's blog post is still up to date there should be a 'kscreenlocker_greet' process. I do not have this process. [1] https://blog.martin-graesslin.com/blog/2014/05/screenlocker-architecture-in-plasma-next/ Thanks, Martin -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.6-tp520 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-x11 [dbus-session-bus] 1.12.20-1 ii drkonqi 5.19.5-3 ii frameworkintegration 5.74.0-2 ii gdb 9.2-1 ii iso-codes4.5.0-1 ii kactivitymanagerd5.19.5-3 ii kded55.74.0-2 ii kinit5.74.0-2 ii kio 5.74.0-2 ii kpackagetool55.74.0-2 ii kwin-common 4:5.19.5-3 ii libappstreamqt2 0.12.11-1 ii libc62.31-4 ii libcolorcorrect5 4:5.19.5-3 ii libgcc-s110.2.0-16 ii libgps26 3.20-12+b1 ii libice6 2:1.0.10-1 ii libkf5activities55.74.0-2 ii libkf5activitiesstats1 5.74.0-2 ii libkf5authcore5 5.74.0-2 ii libkf5baloo5 5.74.0-2 ii libkf5bookmarks5 5.74.0-2 ii libkf5calendarevents55.74.0-2 ii libkf5completion55.74.0-2 ii libkf5config-bin 5.74.0-2 ii libkf5configcore55.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5configwidgets5 5.74.0-2 ii libkf5coreaddons55.74.0-2 ii libkf5crash5 5.74.0-2 ii libkf5dbusaddons55.74.0-2 ii libkf5declarative5 5.74.0-2 ii libkf5globalaccel-bin5.74.0-2 ii libkf5globalaccel5 5.74.0-2 ii libkf5guiaddons5 5.74.0-3 ii libkf5holidays5 1:5.74.0-2 ii libkf5i18n5 5.74.0-3 ii libkf5iconthemes55.74.0-2 ii libkf5idletime5 5.74.0-2 ii libkf5itemmodels55.74.0-2 ii libkf5jobwidgets55.74.0-2 ii libkf5kdelibs4support5 5.74.0-3 ii libkf5kiocore5 5.74.0-2 ii libkf5kiofilewidgets55.74.0-2 ii libkf5kiogui55.74.0-2 ii libkf5kiowidgets55.74.0-2 ii libkf5networkmanagerqt6 5.74.0-2 ii libkf5newstuff5 5.74.0-2 ii libkf5notifications5 5.74.0-2 ii libkf5notifyconfig5 5.74.0-2 ii libkf5package5 5.74.0-2 ii libkf5people55.74.0-2 ii libkf5peoplewidgets5 5.74.0-2 ii libkf5plasma55.74.0-2 ii libkf5plasmaquick5 5.74.0-2 ii libkf5prison55.74.0-2 ii libkf5quickaddons5 5.74.0-2 ii libkf5runner55.74.0-2 ii libkf5service-bin5.74.0-2 ii libkf5service5 5.74.0-2 ii libkf5solid5 5.74.0-2 ii
Bug#632438: [Popcon-developers] Bug#681721: #632438:
On Wed, 23 Sep 2020 16:33:54 +0200 Bill Allombert wrote: snip > Not always. Sometimes that points to packages that are missing in Debian > and should be packaged. I've missed this point of view. > But as soon as a single system report a package name, it appears in the > statistics. So unless everyone set up popcon to discard it, there is the > same amount of noise with less accurate statistics. As you mentioned, it may be meaningless unless everyone set up popcon to discard it. So, to make statistics accurately, it may be a bad idea to filter them. Regards,
Bug#973972: tpp: please rebuild with dh_elpa 2.x
Source: tpp Version: 1.3.1-7 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973970: js2-mode: please rebuild with dh_elpa 2.x
Source: js2-mode Version: 0~20180301-1 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973969: gramadoir: please rebuild with dh_elpa 2.x
Source: gramadoir Version: 0.7-4 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973971: lbdb: please rebuild with dh_elpa 2.x
Source: lbdb Version: 0.48.1 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973967: gocode: please rebuild with dh_elpa 2.x
Source: gocode Version: 20170907-3 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973968: gocode: please rebuild with dh_elpa 2.x
Source: gocode Version: 20170907-3 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973966: cxref: please rebuild with dh_elpa 2.x
Source: cxref Version: 1.6e-3 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973965: ccrypt: please rebuild with dh_elpa 2.x
Source: ccrypt Version: 1.11-1 Severity: important Tags: security X-Debbugs-Cc: debian-emac...@lists.debian.org, Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dh_elpa prior to 1.16 is vulnerable to a path-injection bug via $HOME. Please do a sourceful upload to rebuild against dh_elpa 2.x. This will have the additional advantage of allowing future maintainer script bugs to be fixed without a sourceful upload. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl+n6DAACgkQA0U5G1Wq FSFoIhAAuaz25PVwpoZYIv86KWqbWGsmG+RVKMXKbceM79ROVo8B7dbbN9TyyL28 gvVTUvccYRwwfGjuL0dmqtgyQRPfvbTAujDyy77ApcRRhRtiFZviaVIPhaeBb+v6 4vh7xruht9138v9HAqxrJ/vGZJ9ylQYqH7+m8iqU1jPoahFxqLWc3/ONn/XsatvZ TA/In9Chi7tVlf/VEyORQVAzK8dMwDNFrpcNlIQ6UaGLSW9511gXWSPfd1UKKU9m PITnU6+4PUa2PvwT8zKghzZXJM+JOqIKwjwQsB5YBKAaZJ+JiOILp2/5npl2r+MC D7wkeuHU5Tybc8VyNIUNj9t6FXf7m6w6NzgZbJw7g/01BYY+MxGW3rAglnuTzxeD Vbya7+gC5mVsU0cqhZgP8i0Wi7LU1ZLqR02hp4P1BewpXQs4WOxgERPiYHI9la9p Nh6DE4BXfREmmuRZRAjCxPpsvECFLZOqGDe2M/3J3Swkxnf6/OM8PHviwqxs/nAC GvjDcv8j5VcO2UEQZy7W+odqdB4l93t7SDBtrEdmtgcHaJf88DlbcFNPd9Ic5K1n 11t3su1hHbvguT0W1GM/KZRAqnHUgEQxd+iLx7LbKh9W2I+MM4DGKzjmmYtzK0YQ oHpCJ7Ry4q0wPwcWsSuR4a0i1XoHUvsUyAedBqzBnJqkhwR4FLg= =/N6n -END PGP SIGNATURE-
Bug#973414: libmozjs-78-0: invalid opcodes in libmozjs when launching GDM3
Control: retitle -1 libmozjs-78-0: invalid opcodes when launching GDM on AMD Geode Control: tags -1 = help On Fri, 30 Oct 2020 at 14:07:17 +0200, Martin-Éric Racine wrote: > pe 30. lokak. 2020 klo 13.50 Simon McVittie (s...@debian.org) kirjoitti: > > On Fri, 30 Oct 2020 at 10:35:21 +0200, Martin-Éric Racine wrote: > > > [ 165.903916] traps: gnome-shell[869] trap invalid opcode ip:b5518f8a > > > sp:b17d6d80 error:0 in libmozjs-78.so.78.3.0[b4b98000+98c000] > > > > Which specific x86 CPU is this? > > Geode LX800. This is technically a 686 but it doesn't support PAE, so > the CPU family remains 586. > > The /proc/cpuinfo would be useful information, since that includes a list > > of capability flags. > flags: fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext > 3dnowext 3dnow cpuid 3dnowprefetch vmmcall Notably, this doesn't include SSE (any version), or various smaller extensions like POPCNT. My guess would be that there's a hidden SSE assumption somewhere in mozjs. I'm fairly sure Mozilla upstream doesn't really support non-SSE CPUs any more (several tests fail because we're using i387 rather than SSE for arithmetic), so any porting to older x86 CPUs would be Debian-specific. The Debian GNOME team packages mozjs because we need it for GNOME Shell and gjs, but we don't really have the knowledge or resources to port it to (sub)architectures that don't meet upstream's assumptions - any help you can provide would be appreciated. Because your syslog also included similar crashes in librsvg, which is unrelated to mozjs except that both involve Rust code, I wonder whether it might be the rust compiler rather than mozjs' JIT that is emitting non-i586 opcodes on x86? smcv
Bug#973964: python-biom-format: please make the build reproducible
Source: python-biom-format
Version: 2.1.9-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
python-biom-format could not be built reproducibly.
This is because it ships a test ".coverage" file in the binary, and
these files are unreproducible. The "package-contains-python-coverage-file"
Lintian tag should have been triggered for this.
Patch attached.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/rules 2020-11-08 12:26:02.685952055 +
--- b/debian/rules 2020-11-08 12:30:19.221524553 +
@@ -10,6 +10,7 @@
export examplepkg=python-$(PYBUILD_NAME)-examples
export PYBUILD_AFTER_INSTALL_python3=dh_numpy3
export PYBUILD_BEFORE_TEST=cp -r {dir}/examples {build_dir}
+export PYBUILD_AFTER_TEST=find -name .coverage -delete
## When trying better hardening the build fails
# export DEB_BUILD_MAINT_OPTIONS = hardening=+all
Bug#973751: util-linux: flock --conflict-exit-code returns number modulus 255
tag -1 + upstream Done. I was lazy looking where exactly to report that. And thank you for pointing out this is a system limitation. signature.asc Description: This is a digitally signed message part.
Bug#973963: RFS: libonig/6.9.6-1 -- regular expressions library
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libonig": Package name: libonig Version : 6.9.6-1 Upstream Author : K.Kosako URL : https://github.com/kkos/oniguruma License : BSD-2-clause Vcs : https://jff.email/cgit/libonig.git Section : libs It builds those binary packages: libonig-dev - regular expressions library — development files libonig5 - regular expressions library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libonig/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libo/libonig/libonig_6.9.6-1.dsc or from git https://jff.email/cgit/libonig.git/?h=release%2Fdebian%2F6.9.6-1 Changes since the last upload: libonig (6.9.6-1) unstable; urgency=medium . * New upstream release. - Refresh symbols file. - Fix CVE-2020-26159 (Closes: #972113). * Migrate to debhelper-compat 13: - Bump debhelper-compat version in debian/control to = 13. * debian/rules: - Add remove for libonig.[la|a] to fix warning about missing installs. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#973960: ITP: ruby-tpm-key-attestation -- TPM Key Attestation verifier
Package: wnpp Severity: wishlist Owner: Pirate Praveen Packaging of https://rubygems.org/gems/tpm-key_attestation Dependency of gitlab 13.4.x
Bug#973961: node-original: please use packaged node-assume
Source: node-original Hello, 'node-original' embeds a copy of source code of 'assume' node module, which has recently entered Debian as 'node-assume'. Please switch from embedded code copy to Debian-packaged module. Best, Andrius
Bug#973962: node-url-parse: please use packaged node-assume
Source: node-url-parse Hello, 'node-url-parse' embeds a copy of source code of 'assume' node module, which has recently entered Debian as 'node-assume'. Please switch from embedded code copy to Debian-packaged module. Best, Andrius
Bug#933038: Hello my dearest,
Hello my dearest, Am a dying woman here in the hospital, i was Diagnose as a "cancer" patient 2 years ago. I am A business woman dealing with Gold Exportation. I have a charitable and unfulfillment project that am about to handover to you, if you are interested please Reply hope to hear from you. Regard Mrs.Elizabeth Abura,
Bug#973959: configure: error: unrecognized option: --runstatedir=/run
Package: autoconf
Version: 2.69-11.1
Severity: normal
Dear Maintainer,
I am getting
dh_auto_configure -- --with-gaproot=/usr/share/gap
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-
maintainer-mode --disable-dependency-tracking --with-gaproot=/usr/share/gap
configure: error: unrecognized option: `--runstatedir=/run'
Try `./configure --help' for more information
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-
maintainer-mode --disable-dependency-tracking --with-gaproot=/usr/share/gap
returned exit code 1
make[1]: *** [debian/rules:27: override_dh_auto_configure] Error 2
The symptoms are identical to #887390. Fortunately the workaround mentioned
there
override_dh_auto_configure:
DH_COMPAT=10 dh_auto_configure -- …
works for me, too.
-- System Information:
Debian Release: bullseye/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500,
'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages autoconf depends on:
ii debianutils 4.11.2
ii m4 1.4.18-4
ii perl 5.30.3-4
Versions of packages autoconf recommends:
ii automake [automaken] 1:1.16.2-4
Versions of packages autoconf suggests:
ii autoconf-archive 20190106-2.1
pn autoconf-doc
ii gettext 0.19.8.1-10
pn gnu-standards
ii libtool 2.4.6-14
-- no debconf information
Bug#973958: mpdscribble: New upstream version 0.23
Package: mpdscribble Version: 0.22-6 Severity: normal Dear Maintainer, A new version of mpdscribble is available, can you upload it :) https://www.musicpd.org/clients/mpdscribble/ Thanks k -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpdscribble depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii init-system-helpers1.56+nmu1 ii libc6 2.28-10 ii libglib2.0-0 2.58.3-2+deb10u2 ii libmpdclient2 2.16-1 ii libsoup2.4-1 2.64.2-2 ii lsb-base 10.2019051400 ii ucf3.0038+nmu1 mpdscribble recommends no packages. Versions of packages mpdscribble suggests: ii mpd 0.22.3-1~bpo10+1
Bug#973957: samba_dnsupdate gives depreacation warnings
Package: samba Version: 2:4.12.5+dfsg-3 Severity: important Tags: patch Dear maintainer, samba dumps lot of errors to syslog every 5 minutes: Nov 8 11:36:59 toy samba[2200]: [2020/11/08 11:36:59.605649, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) Nov 8 11:36:59 toy samba[2200]: /usr/sbin/samba_dnsupdate: /usr/sbin/samba_dnsupdate:274: DeprecationWarning: please use dns.resolver.Resolver.resolve() instead Nov 8 11:36:59 toy samba[2200]: [2020/11/08 11:36:59.605743, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) Nov 8 11:36:59 toy samba[2200]: /usr/sbin/samba_dnsupdate: return resolver.query(name, name_type) This bug is handled from upstream: https://bugzilla.samba.org/show_bug.cgi?id=14553 I've testet the patch from above bugzilla against 2:4.12.5+dfsg-3. It should fix this issue. So please attach proposed patch or either update to 4.13.2 which should include the fix. -- Thanks in advance Elimar -- Package-specific info: * /etc/samba/smb.conf present, but not attached * /var/lib/samba/dhcp.conf present, but not attached -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.74-toy-lxtec-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages samba depends on: ii adduser 3.118 ii dpkg 1.20.5 ii init-system-helpers 1.58 ii libbsd0 0.10.0-1 ii libc62.31-4 ii libglib2.0-0 2.66.2-1 ii libgnutls30 3.6.15-4 ii libldb2 2:2.1.4-2 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpopt0 1.18-2 ii libpython3.8 3.8.6-1 ii libtalloc2 2.3.1-1 ii libtasn1-6 4.16.0-2 ii libtdb1 1.4.3-1 ii libtevent0 0.10.2-1 ii libwbclient0 2:4.12.5+dfsg-3.1 ii lsb-base 11.1.0 ii procps 2:3.3.16-5 ii python3 3.8.6-1 ii python3-dnspython2.0.0-1 ii python3-samba2:4.12.5+dfsg-3.1 ii samba-common 2:4.12.5+dfsg-3.1 ii samba-common-bin 2:4.12.5+dfsg-3.1 ii samba-libs 2:4.12.5+dfsg-3.1 ii tdb-tools1.4.3-1 Versions of packages samba recommends: ii attr1:2.4.48-5 ii logrotate 3.17.0-1 pn python3-markdown ii samba-dsdb-modules 2:4.12.5+dfsg-3.1 ii samba-vfs-modules 2:4.12.5+dfsg-3.1 Versions of packages samba suggests: ii bind9 1:9.16.6-3 ii bind9-utils [bind9utils] 1:9.16.6-3 ii bind9utils1:9.16.6-3 pn ctdb ii ldb-tools 2:2.1.4-2 ii ntp 1:4.2.8p15+dfsg-1 ii smbldap-tools 0.9.11-1 pn ufw ii winbind 2:4.12.5+dfsg-3.1 -- no debconf information
Bug#973956: vienna-rna: build-depends on python3-all-dev, but only builds for the default python3 version
Source: vienna-rna Version: 2.4.14+dfsg-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 Hi Maintainer The vienna-rna package has a build-dependency on python3-all-dev, but its debian/rules only builds for the default python3 version. This causes issues for tracking transitions, since packages build-depending on python3-all-dev are expected to build for all supported python3 versions. The package should either build-depend only on python3-dev, or it should build for all supported python3 versions. Regards Graham
Bug#973955: bind9: flaky autopkgtest: DNS query rootserver
Source: bind9 Version: 1:9.16.6-3 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky Hi, the autopkg test validates DNSSEC of internetsociety.org for it requires unrestricted internet access. For this it is needed to specify Restrictions: needs-internet in the testfile as other worker may not provide internet access. Please see https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst search for "needs-internet" and the note about "Network access". The failed test: https://ci.debian.net/data/autopkgtest/testing/amd64/b/bind9/8020050/log.gz Sebastian
Bug#969656: util-linux: man page for zramctl is outdated about max_comp_streams' "default is one stream"
Hello Marcel Partap, * Marcel Partap [201108 10:40]: > Since Kernel 4.7, it defaults to one stream per CPU: > > > Regardless of the value passed to this attribute, ZRAM will always > > allocate multiple compression streams - one per online CPU - thus > > allowing several concurrent compression operations. The number of > > allocated compression streams goes down when some of the CPUs > > become offline. There is no single-compression-stream mode anymore, > > unless you are running a UP system or have only 1 CPU online. > > .. Best Regards! : ) Thank you for your report. I have very little idea what all of that means. However the man-page is not Debian-specific. Please raise this issue with upstream - maybe with a draft patch, as you seem to know what zramctl is and what exactly changed and how. You can find upstreams contact data here: https://github.com/karelzak/util-linux/blob/master/README Please let me know when upstream has been informed and/or accepted a patch. Many thanks, Chris
Bug#973954: ITP: node-sane -- Nodejs fast, small, and reliable file system watcher
Package: wnpp Severity: wishlist Owner: Xavier Guimard X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: node-sane Version : 4.1.0 Upstream Author : Amjad Masad * URL : https://github.com/amasad/sane * License : Expat Programming Lang: JavaScript Description : Nodejs fast, small, and reliable file system watcher Sane aims to be fast, small, and reliable file system watcher. It does that by: * By default stays away from fs polling because it's very slow and cpu intensive * Uses `fs.watch` by default and sensibly works around the various issues * Maintains a consistent API across different platforms * Where `fs.watch` is not reliable you have the choice of using the following alternatives: * the facebook watchman library (embedded) * the watchexec library (embedded) * polling This package is required to update node-jest: a powerful and widely used JavaScript test framework.
Bug#973909: libreoffice-impress: crash when exiting presentation mode
Hi, Am 08.11.20 um 11:26 schrieb Heinrich Schuchardt: > On 08.11.20 10:20, Rene Engelhard wrote: >> Hi, >> >> Am 07.11.20 um 19:11 schrieb Rene Engelhard: >>> Am 07.11.20 um 10:12 schrieb Heinrich Schuchardt: Everytime I leave the LibreOffice Impress presentation mode by pressing the ESC key the application crashes: >>> [...] > With > > libreoffice-impress_7.0.4~rc1~git20201107-1_amd64.deb > libreoffice-draw_7.0.4~rc1~git20201107-1_amd64.deb > libreoffice-core_7.0.4~rc1~git20201107-1_amd64.deb > > the reported crash in LibreOffice Impress is gone. Thanks for confirming. Regards, Rene
Bug#973471: look has unpredictable behavior
Hello Jamie Heilman, * Jamie Heilman [201031 09:33]: > look's behavior became really unpredictable when it migrated from > bsdmainutils to util-linux. Thank you for your report. > $ look achi [6 results] > $ grep -ci ^achi /usr/share/dict/words > 36 For one, you seem to be using a different words file than me: $ grep -ci '^achi' /usr/share/dict/words 16 Anyway, util-linux's look uses a binary search and has requirements on the input file. This is documented in the manpage look(1): | As look performs a binary search, the lines in file must be | sorted (where sort(1) was given the same options -d and/or -f | that look is invoked with) /usr/share/dict/words (in my case /usr/share/dict/american-english) does not follow these requirements. If you read the old look(1) manpage, it says under COMPATIBILITY: | look uses a linear search by default instead of a binary search, | which is what most other implementations use by default. Now we are back at "what most other implementations use", so one less compatibility issue. If you would like to see improvements over this, please talk to upstream about it. Their contacts are: E-MAIL: util-li...@vger.kernel.org Web:https://github.com/karelzak/util-linux/issues Best wishes, Chris
Bug#973950: rust-bat: FTBFS - unsat-dependency: librust-onig-5+default-dev
With a recent update, it broke bat: The error is: missing: pkg: package: librust-syntect+parsing-dev version: 3.3.0-3 architecture: amd64 unsat-dependency: librust-onig-5+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) | librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) Thanks, Sylvestre A new version of rust-syntect was uploaded, but it was rejected by the ftpmasters due to new featureset packages. If the upstream dependencies are to be believed, a new version of syntect would mean a new version of bat. That in turn means. * Updating console (which also looks like it will bring new featuresets :( ) * Packaging path_abs * Updating semver (which has several other reverse dependencies) * Updating git2 (which has several other reverse dependencies) It's possible this could be worked around by relaxing dependencies in either syntect or bat, but given neither of them seems to have functioning autopkgtests, this would likely require manual testing.
Bug#973909: libreoffice-impress: crash when exiting presentation mode
On 08.11.20 10:20, Rene Engelhard wrote: > Hi, > > Am 07.11.20 um 19:11 schrieb Rene Engelhard: >> Am 07.11.20 um 10:12 schrieb Heinrich Schuchardt: >>> Everytime I leave the LibreOffice Impress presentation mode by pressing >>> the ESC key the application crashes: >> In a just upgraded amd64 testing VM (inside KDE): >> >> 1. Start loimpress >> 2. F5 with that empty document >> 3. ESC >> >> Closes and I am fine in Impress again. No crash. > > Built a current snapshot anyway: > > deb [trusted=yes] > (not signed, so [trusted=yes]) > > Would you confirm it fixes it? > Thanks Rene for the packaging. With libreoffice-impress_7.0.4~rc1~git20201107-1_amd64.deb libreoffice-draw_7.0.4~rc1~git20201107-1_amd64.deb libreoffice-core_7.0.4~rc1~git20201107-1_amd64.deb the reported crash in LibreOffice Impress is gone. Best regards Heinrich
Bug#940329:
> Any progress? If not, I'm willing to package this. Looks like progress is being made: https://salsa.debian.org/debian/scantailor-advanced I was able to build + run the resulting package after adding the attached quilt patch. It avoids errors due to a missing QPainterPath include: src/core/filters/output/OutputGenerator.cpp: In member function ‘imageproc::BinaryThreshold output::OutputGenerator::Processor::calcBinarizationThreshold(const QImage&, const QPolygonF&, const imageproc::BinaryImage*) const’: src/core/filters/output/OutputGenerator.cpp:2111:16: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 2111 | QPainterPath path; |^~~~ Upstream has seen the compile errors as well and already fixed most of them: https://github.com/4lex4/scantailor-advanced/commit/3d1e74e6ace413733511086934a66f4e3f7a6027 Some others are added here: https://github.com/4lex4/scantailor-advanced/pull/158 Index: scantailor-advanced/src/core/filters/output/OutputGenerator.cpp === --- scantailor-advanced.orig/src/core/filters/output/OutputGenerator.cpp 2020-11-08 02:55:57.0 +0100 +++ scantailor-advanced/src/core/filters/output/OutputGenerator.cpp 2020-11-08 02:56:06.0 +0100 @@ -39,6 +39,7 @@ #include #include #include +#include #include #include #include Index: scantailor-advanced/src/core/filters/page_layout/ImageView.cpp === --- scantailor-advanced.orig/src/core/filters/page_layout/ImageView.cpp 2020-11-08 02:55:57.0 +0100 +++ scantailor-advanced/src/core/filters/page_layout/ImageView.cpp 2020-11-08 02:56:06.0 +0100 @@ -12,6 +12,7 @@ #include #include #include +#include #include #include #include "ImagePresentation.h" Index: scantailor-advanced/src/core/filters/select_content/ContentBoxFinder.cpp === --- scantailor-advanced.orig/src/core/filters/select_content/ContentBoxFinder.cpp 2020-11-07 16:48:34.597819755 +0100 +++ scantailor-advanced/src/core/filters/select_content/ContentBoxFinder.cpp 2020-11-08 02:59:49.839413792 +0100 @@ -20,6 +20,7 @@ #include #include #include +#include #include #include #include "DebugImages.h" Index: scantailor-advanced/src/app/ThumbnailSequence.cpp === --- scantailor-advanced.orig/src/app/ThumbnailSequence.cpp 2020-11-07 16:48:34.577819010 +0100 +++ scantailor-advanced/src/app/ThumbnailSequence.cpp 2020-11-08 03:00:47.206290290 +0100 @@ -7,6 +7,7 @@ #include #include #include +#include #include #include #include Index: scantailor-advanced/src/core/ImageViewBase.cpp === --- scantailor-advanced.orig/src/core/ImageViewBase.cpp 2020-11-07 16:48:34.581819159 +0100 +++ scantailor-advanced/src/core/ImageViewBase.cpp 2020-11-08 03:02:18.497525165 +0100 @@ -8,6 +8,7 @@ #include #include #include +#include #include #include #include Index: scantailor-advanced/src/core/IncompleteThumbnail.cpp === --- scantailor-advanced.orig/src/core/IncompleteThumbnail.cpp 2020-11-07 16:48:34.581819159 +0100 +++ scantailor-advanced/src/core/IncompleteThumbnail.cpp 2020-11-08 03:02:09.169257461 +0100 @@ -4,6 +4,7 @@ #include "IncompleteThumbnail.h" #include #include +#include #include QPainterPath IncompleteThumbnail::m_sCachedPath; Index: scantailor-advanced/src/core/ThumbnailBase.cpp === --- scantailor-advanced.orig/src/core/ThumbnailBase.cpp 2020-11-07 16:48:34.585819308 +0100 +++ scantailor-advanced/src/core/ThumbnailBase.cpp 2020-11-08 03:02:24.785698551 +0100 @@ -5,6 +5,7 @@ #include #include #include +#include #include #include #include Index: scantailor-advanced/src/core/filters/page_layout/Thumbnail.cpp === --- scantailor-advanced.orig/src/core/filters/page_layout/Thumbnail.cpp 2020-11-07 16:48:34.593819606 +0100 +++ scantailor-advanced/src/core/filters/page_layout/Thumbnail.cpp 2020-11-08 03:02:03.941101786 +0100 @@ -3,6 +3,7 @@ #include "Thumbnail.h" #include +#include #include #include "Utils.h" #include Index: scantailor-advanced/src/core/zones/ZoneContextMenuInteraction.cpp === --- scantailor-advanced.orig/src/core/zones/ZoneContextMenuInteraction.cpp 2020-11-07 16:48:34.597819755 +0100 +++ scantailor-advanced/src/core/zones/ZoneContextMenuInteraction.cpp 2020-11-08 03:02:35.393978551 +0100 @@ -6,6 +6,7 @@ #include #include #include +#include #include #include "ImageViewBase.h" #include "ZoneInteractionContext.h" Index:
Bug#973751: util-linux: flock --conflict-exit-code returns number modulus 255
Hi Jean-Michel Vourgère, * Jean-Michel Vourgère [201104 15:09]: > When using flock --nonblock --conflict-exit-code 600 on a locked file, the > returned value is 88. [..] > flock should fail immediatly if the number parameter is out of > acceptable range and will never be returned. > > Additionnally, flock(1) should document the fact that number must be <= > 255. Thank you for your report. As this is quite clearly an upstream bug, and not Debian-specific, could you please raise this with upstream[1] and report back? [1] E-MAIL: util-li...@vger.kernel.org Web:https://github.com/karelzak/util-linux/issues Thanks, Chris
Bug#973953: sddm: Implicitly defined onFoo properties
Package: sddm
Version: 0.18.1-1
Severity: minor
Since a few days I see the following messages in my logs:
Nov 7 21:02:49 samd sddm-greeter[380582]:
file:///usr/share/sddm/themes/debian-theme/Main.qml:452:5: QML Connections:
Implicitly defined onFoo properties in Connections are deprecated. Use this
syntax instead: function onFoo() { ... }
Nov 7 21:02:49 samd sddm-greeter[380582]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:196:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
Nov 7 21:02:49 samd sddm-greeter[380582]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:196:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
Nov 7 21:02:49 samd sddm-greeter[380582]:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:196:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
Nov 7 21:02:49 samd sddm-greeter[380582]:
file:///usr/share/sddm/themes/debian-theme/Login.qml:103:13: QML Connections:
Implicitly defined onFoo properties in Connections are deprecated. Use this
syntax instead: function onFoo() { ... }
If these messages are harmless, could you please provide
appropriate logcheck filters to avoid them ending up in the logs?
So far, neither myself nor my users have experienced anything strange.
Thanks
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sddm depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.74
ii libc6 2.31-4
ii libgcc-s1 10.2.0-16
ii libpam0g1.3.1-5
ii libqt5core5a5.15.1+dfsg-2
ii libqt5dbus5 5.15.1+dfsg-2
ii libqt5gui5 5.15.1+dfsg-2
ii libqt5network5 5.15.1+dfsg-2
ii libqt5qml5 5.15.1+dfsg-3
ii libqt5quick55.15.1+dfsg-3
ii libstdc++6 10.2.0-16
ii libsystemd0 246.6-2
ii libxcb-xkb1 1.14-2
ii libxcb1 1.14-2
ii qml-module-qtquick2 5.15.1+dfsg-3
ii x11-common 1:7.7+21
ii xauth 1:1.0.10-1
ii xserver-xorg [xserver] 1:7.7+21
Versions of packages sddm recommends:
pn haveged
ii libpam-systemd 246.6-2
ii sddm-theme-breeze [sddm-theme] 4:5.17.5-4
Versions of packages sddm suggests:
ii libpam-kwallet5 5.17.5-2
pn qtvirtualkeyboard-plugin
-- debconf information:
sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
Bug#973952: kde-baseapps: Problems with LogOutPrompt?
Package: kde-baseapps Version: 4:20.04.0+5.106 Severity: minor I'm not sure which package is responsible, please reassign as appropriate, thanks. For some time I see org.kde.LogoutPrompt complaining in the logs: Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :406:376: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :407:130: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :408:130: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :408:393: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :409:130: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :410:129: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :411:129: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :412:129: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :413:129: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :413:379: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: qt.svg: :413:631: Could not add child element to parent element because the types are incorrect. Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:41: ReferenceError: config is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:34: ReferenceError: model is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:0: ReferenceError: config is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:0: ReferenceError: config is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33: ReferenceError: config is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33: ReferenceError: config is not defined Nov 7 18:19:12 samd org.kde.LogoutPrompt[5102]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33: ReferenceError: config is not defined So far, my users did not report any issue. If these messages are harmless and cannot be avoided, could you add an appropriate logcheck filter rule? Thanks -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-baseapps depends on: ii dolphin 4:20.08.2-1 ii kdialog 4:20.08.2-1 ii keditbookmarks 20.04.0-1 ii kfind 4:20.04.3-1 ii konqueror 4:20.04.3-1 ii konsole 4:20.08.0-1 ii kwrite 4:20.08.2-1 kde-baseapps recommends no packages. kde-baseapps suggests no packages. -- no debconf information -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#968559: libhdf5-openmpi-dev: hdf5-mpi.pc alternative sometimes goes missing
Drew Parsons a écrit le 08/11/2020 à 05:17 : > Probably we should check with the update-alternatives developers first, > they may have some ideas. Certainly they should be able to explain > exactly why installing openmpi-bin or mpich causes the hdf5-mpi > alternative to disappear. Would you mind opening these discussions? Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#930931: [pkg-bacula-devel] Bug#930931: /usr/sbin/btape: btape crashes on "fill" test
Hi! For the avoidance of doubt: The bug I reported here and all the testing I did in 2019 around this bug report all took place on my Bacula production system. In the meantime, I did set up an independent test system in order to have more flexibility in testing and also to exclude hardware problems other than those I already tested. Here's a quick overview of the test system compared to the production system: - System main components (e.g. mainboard, CPU, ...): all different from production system. - Fibre Channel controler: different (production system: Emulex LPe11002; test system: QLogic QLE2460) - Tape Library: same type as production system - LTO5 drive: exact same drive as previously tested in production system - Basic operating system: same as production system (Debian Stretch) - Actual kernel running: different (production system: 4.9.0-12-amd64; test system: 4.9.0-14-amd64) - Bacula version: same as production system: - bacula: 7.4.4+dfsg-6+deb9u2 - bacula-bscan:9.4.2-1~bpo9+1 - bacula-client: 7.4.4+dfsg-6+deb9u2 - bacula-common: 9.4.2-1~bpo9+1 - bacula-common-mysql: 9.4.2-1~bpo9+1 - bacula-console: 9.4.2-1~bpo9+1 - bacula-director: 9.4.2-1~bpo9+1 - bacula-director-mysql: 9.4.2-1~bpo9+1 - bacula-fd: 9.4.2-1~bpo9+1 - bacula-sd: 9.4.2-1~bpo9+1 - bacula-sd-dbgsym:9.4.2-1~bpo9+1 - bacula-server: 7.4.4+dfsg-6+deb9u2 Now, when I run tests on the test system with btape, both the "test" test and the "fill" test work without any problems, i.e. no crash occurs. Regards Sebastian
Bug#973951: ipp-usb: Fails to restart
Package: ipp-usb Version: 0.9.14-1 Severity: important X-Debbugs-Cc: none, Tollef Fog Heen ipp-usb fails to restart for me, at least when restarted by needrestart: : tfheen@xoog ~ > systemctl status ipp-usb.service ● ipp-usb.service - Daemon for IPP over USB printer support Loaded: loaded (/lib/systemd/system/ipp-usb.service; static) Active: activating (start) since Sun 2020-11-08 10:03:33 CET; 41min ago Docs: man:ipp-usb(8) Main PID: 57922 (ipp-usb) Tasks: 11 (limit: 38371) Memory: 15.3M CGroup: /system.slice/ipp-usb.service └─57922 /sbin/ipp-usb udev as you can see, it's been «starting» for 40+ minutes. This is pretty annoying, since it makes my apt runs just hang whenever ipp-usb is restarted. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Versions of packages ipp-usb depends on: ii avahi-daemon 0.8-3 ii libavahi-client3 0.8-3 ii libavahi-common3 0.8-3 ii libc6 2.31-4 ii libusb-1.0-0 2:1.0.23-2 ipp-usb recommends no packages. ipp-usb suggests no packages. -- no debconf information -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Bug#973909: libreoffice-impress: crash when exiting presentation mode
Hi, Am 07.11.20 um 19:11 schrieb Rene Engelhard: > Am 07.11.20 um 10:12 schrieb Heinrich Schuchardt: >> Everytime I leave the LibreOffice Impress presentation mode by pressing >> the ESC key the application crashes: > In a just upgraded amd64 testing VM (inside KDE): > > 1. Start loimpress > > 2. F5 with that empty document > > 3. ESC > > Closes and I am fine in Impress again. No crash. Built a current snapshot anyway: deb [trusted=yes] http://people.debian.org/~rene/libreoffice/7.0/snapshots ./ (not signed, so [trusted=yes]) Would you confirm it fixes it? Regards, Rene
Bug#973936: RFS: hydrapaper/2.0.2-1 -- Utility that sets background independently for each monitor
Control: tags -1 moreinfo Hi Francisco, On Sat, Nov 07, 2020 at 05:20:13PM -0300, Francisco M Neto wrote: > Changes since the last upload: > > hydrapaper (2.0.2-1) unstable; urgency=medium > . >* New upstream version. >* debian/clean: created file to force manpage cleanup. - The changelog entry of 2.0-2, namely the timestamp, does not match the archive. Please fix that. --- /home/tobi/workspace/deb/mentors/fmneto/hydrapaper/archive/hydrapaper-2.0/debian/changelog +++ /home/tobi/workspace/deb/mentors/fmneto/hydrapaper/new/hydrapaper-2.0.2/debian/changelog @@ -1,8 +1,15 @@ +hydrapaper (2.0.2-1) unstable; urgency=medium + + * New upstream version. + * debian/clean: created file to force manpage cleanup. + + -- Francisco M Neto Wed, 28 Oct 2020 11:10:17 + + hydrapaper (2.0-2) unstable; urgency=medium * Source only upload for testing migration. - -- Francisco M Neto Wed, 28 Oct 2020 00:11:23 + + -- Francisco M Neto Wed, 28 Oct 2020 10:16:46 + hydrapaper (2.0-1) unstable; urgency=medium - The archive has already a d/clean, your changes actually is removing two lines: --- /home/tobi/workspace/deb/mentors/fmneto/hydrapaper/archive/hydrapaper-2.0/debian/clean +++ /home/tobi/workspace/deb/mentors/fmneto/hydrapaper/new/hydrapaper-2.0.2/debian/clean @@ -1,3 +1 @@ docs/hydrapaper.1 -clean/ -obj* Please sync your git repo with the archives's version. Beside that, looks good. Thanks, tobi signature.asc Description: PGP signature
Bug#972719: gnome-control-center: It can not start because segmentation fault occurs.
Dear Maintainer, I just want to add that I also run into the same problem. In addition to the error messages above I also observed the following backtrace: #0 cc_display_config_get_panel_orientation_managed (self=0x0) at ../panels/display/cc-display-config.h:139 #1 0x555d3c8c in reset_current_config (panel=0x565001c0) at ../panels/display/cc-display-panel.c:875 #2 0x555d4ee8 in on_screen_changed (panel=0x565001c0) at ../panels/display/cc-display-panel.c:911 #3 on_screen_changed (panel=0x565001c0) at ../panels/display/cc-display-panel.c:904 #4 0x77d67092 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x77d79403 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x77d7f69f in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x77d7fc0f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x555d8bbf in _cc_display_config_manager_emit_changed (self=) at ../panels/display/cc-display-config-manager.c:54 #9 0x555d8a2f in got_current_state (object=0x55ae9240, result=0x56712b40, data=0x5679ab00) at ../panels/display/cc-display-config-manager.h:29 #10 0x77e5e2e9 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77e5eddb in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x77eb98ac in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77e5e2e9 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x77e5e329 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x77c75a9f in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x77c75e48 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77c75eff in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x77e8c425 in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #19 0x555ac644 in main (argc=, argv=) at ../shell/main.c:65 Best regards, Michael
Bug#954613: rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev
Hello Wofgang, Do you have the intention to fix process-viewer? We have a RC bug from March on it. If you don't plan to, maybe we should just remove it from the Debian archive. Thanks Sylvestre
Bug#963916: rust-debcargo: Cannot build debcargo
Now, the error is: missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-semver-parser-0.9+default-dev:amd64
Bug#973950: rust-bat: FTBFS - unsat-dependency: librust-onig-5+default-dev
Source: rust-bat Severity: important Dear Maintainer, With a recent update, it broke bat: The error is: missing: pkg: package: librust-syntect+parsing-dev version: 3.3.0-3 architecture: amd64 unsat-dependency: librust-onig-5+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) | librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) Thanks, Sylvestre -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
Bug#973949: rust-spotify-tui: FTBFS - unsat-dependency: librust-foreign-types-shared-0.1+default-dev:amd64
Source: rust-spotify-tui Severity: important Dear Maintainer, With the recent foreign-types-shared update, it broke spotify-tui The error is: missing: pkg: package: librust-foreign-types-dev version: 0.3.2-1+b1 architecture: amd64 unsat-dependency: librust-foreign-types-shared-0.1+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-rspotify-0.7+default-dev:amd64 | librust-rspotify-0.7+default-dev:amd64 - package: librust-rspotify-dev version: 0.7.0-3 architecture: amd64 depends: librust-reqwest-0.9+default-dev:amd64 | librust-reqwest-0.9+default-dev:amd64 - package: librust-reqwest+default-tls-dev version: 0.9.19-4 architecture: amd64 depends: librust-native-tls-0.2+default-dev:amd64 | librust-native-tls-0.2+default-dev:amd64 - package: librust-native-tls-dev version: 0.2.4-1 architecture: amd64 depends: librust-openssl-0.10+default-dev:amd64 (>= 0.10.25-~~) | librust-openssl-0.10+default-dev:amd64 (>= 0.10.25-~~) - package: librust-openssl-dev version: 0.10.29-1 architecture: amd64 depends: librust-foreign-types-0.3+default-dev:amd64 (>= 0.3.1-~~) | librust-foreign-types-0.3+default-dev:amd64 (>= 0.3.1-~~) Thanks Sylvestre -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
Bug#973910: gpsprune: Missing tile cache root
Noted and understood, thanks for reporting this. Yes I agree the reaction to this situation isn't ideal. When the whole cache root goes missing it knows it _should_ use the disk cache but every attempt to use it silently fails. This will be improved with 20.1. Until then the best solution is to use the Settings -> Save maps to disk function, if you know that you need to.
Bug#973922: New upstream (2.19)
Control: tag -1 + confirmed On Sat, Nov 07, 2020 at 03:52:24PM +0100, Daniel Baumann wrote: > Package: radvd > > Hi Geert, ;-) > thank you for maintaining radvd. Unfortunately I'm hit by a bug that got > fixed in radvd which makes it unable for me to use it with my provider. > > It would be super nice if you could upgrade to version 2.19. Acknowledge > Regards, > Daniel Regards Geert Stappers Working on it
Bug#973948: RM: snort [s390x] -- RoQA; build dependency libluajit-5.1-dev is not available on s390x
Package: ftp.debian.org Severity: normal Snort now Build-Depends on libluajit-5.1-dev, libluajit-5.1-dev is not available on s390x, and so snort can't be built on s390x. I request this architecture-specific removal to allow snort to migrate to testing. Regards, Juhani
Bug#973947: python3-rna, librna-perl: Cannot fulfill the dependencies
Package: python3-rna Version: 2.4.14+dfsg-2 Severity: serious Control: affects -1 librna-perl The following packages have unmet dependencies: python3-rna : Depends: libvienna-rna but it is not installable librna-perl : Depends: libviennarna0 but it is not installable The library does not exist under either name. libRNA is only built (and linked) as a static library, therefore no additional runtime dependency is required.
Bug#973946: ITP: node-emittery -- Nodejs simple and modern async event emitter
Package: wnpp Severity: wishlist Owner: Xavier Guimard X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: node-emittery Version : 0.7.2 Upstream Author : Sindre Sorhus * URL : https://github.com/sindresorhus/emittery * License : Expat Programming Lang: JavaScript Description : Nodejs and browser simple and modern async event emitter Emitting events asynchronously is important for production code where you want the least amount of synchronous operations. Since JavaScript is single-threaded, no other code can run while doing synchronous operations. For Node.js, that means it will block other requests, defeating the strength of the platform, which is scalability through async. In the browser, a synchronous operation could potentially cause lags and block user interaction. emittery solves this providing a simple but powerful API. This package is a dependency of new node-jest. I think it should not be embedded since it's too big. Cheers, Xavier
Bug#973941: Pasted text looks same as cursor
On 2020-11-08 06:53 +0800, 積丹尼 Dan Jacobson wrote: > Package: xterm > Version: 361-1 > Severity: minor > > Lately when we paste with SHIFT+INSERT, the pasted text is in reverse > video. I presume you are using bash which added this feature in version 5.1, in zsh it has been available for a few years. > That's great, but that is the same color as our cursor, which "gets > lost" due to it. This can be irritating at first, although I have gotten used to it. > So perhaps make the text a different color. > > (I'm using > https://www.jidanni.org/comp/configuration/.Xresources > https://www.jidanni.org/comp/configuration/ etc. settings.) I have not looked at your settings, but xterm has command options and resources to change the color of either the cursor or selected text. >From the manpage: , | -cr color | This option specifies the color to use for text cursor. | The default is to use the same foreground color that is | used for text. It sets the cursorColor resource according | to the parameter. | | -hm Tells xterm to use highlightTextColor and highlightColor | to override the reversed foreground/background colors in a | selection. It sets the highlightColorMode resource to | “true”. | | -selbg color | This option specifies the color to use for the background | of selected text. If not specified, reverse video is | used. See the discussion of the highlightColor resource. | | -selfg color | This option specifies the color to use for selected text. | If not specified, reverse video is used. See the | discussion of the highlightTextColor resource. ` You might want to play with these options until you find some color combination that suits you. Cheers, Sven
