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#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#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#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#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#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#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#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
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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#973808: pipwire: WebRTC support broken
Control: tags -1 + moreinfo On Thu, 05 Nov 2020 at 10:50:15 +, Claudio Sacerdoti Coen wrote: > After upgrading from 0.3.12-1 WebRTC support stopped working in > firefox, Teams, etc. Downgrading resolves the issue. Does 0.3.15-1 resolve this? smcv
Bug#973983: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit : > did you try to set onne of them in debian/nodejs/main ? Oh, dear... putting one of them in there did make things go through, but checking the resulting package : all the other components ended up in a node_modules directory within the chosen one's directory! That's definitely not correct. Cheers, JP
Bug#936268: caldav-tester: Python2 removal in sid/bullseye
Quoting Jonas Smedegaard (2020-10-11 03:48:54) > Quoting Jann Haber (2020-10-11 03:26:04) > > This bug does not seem to be fixed. There is still a dependency on > > python2. Reopening. > > Right - I am sorry I processed it wrongly: I have now applied a usertag > as instructed. Seems a usertag is unacceptable: popcon of its reverse dependency radicale is below the required 300 :-( I am now working on migrating the code to Python3... - 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#973924: cfdisk: display more free space than actually available, and partition not resizable
Hello gregoire roumache, Thank you for your report. * gregoire roumache [201108 14:52]: > I installed this debian with a HDD of 20 Gio, and partitioned it manually. > > Here are the partitions I made, in order: > >1. 256 MB - primary - beginning - ext4 – /boot – bootable flag = on >2. 1 GB - primary - beginning - swap area >3. 10 GB - primary - end - ext4 - / >4. 2 GB - logical - beginning - ext4 - /home >5. 2 GB - logical - beginning - ext4 - /tmp > > [..] I don't understand your bug report. Could you please do these things / answer these questions: 1) Make a detailed reproduction steps list. What does "installed... and partitioned manually" mean? Partitioned using cfdisk? 2) Provide output of fdisk -l before/after each step. 3) Do you think, this is a) a bug in cfdisk? b) your partition table? c) in whatever tool that partitioned this disk initially? 4) Does the same problem appear if you use fdisk instead of cfdisk? 5) Does parted show the same problem? Chris
Bug#973983: pkg-js-tools tries to require a non-existing name
Package: pkg-js-tools
Version: 0.9.45
I'm trying to package lumino (ITP 972487), which has a pretty special
structure:
- no main module ;
- only packages.
My d/control has a build dep on pkg-js-tools, and uses "Provides:
${nodejs:Provides}" ; I have a d/nodejs/additional_components with
packages/* to find the packages and my d/tests/pkg-js/test is only an
"echo FIXME".
When building the package, I get strange warnings, but they seem pretty
harmless :
dh_auto_install: warning: # /! "types" field should be replaced by
"typings" in packages/algorithm/package.json
Please report this bug
Things get bad when autopkgtest kicks in and tries to require:
autopkgtest [15:44:43]: test pkg-js-autopkgtest-require: [-
--
Using package.json
Node module name is
Test: require
internal/modules/cjs/loader.js:898
throw new ERR_INVALID_ARG_VALUE('id', id,
^
TypeError [ERR_INVALID_ARG_VALUE]: The argument 'id' must be a non-
empty string. Received ''
at Module.require (internal/modules/cjs/loader.js:898:11)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at evalScript (internal/process/execution.js:94:25)
at internal/main/eval_string.js:23:3 {
code: 'ERR_INVALID_ARG_VALUE'
}
indeed, the main package.json has no 'name' field. It should instead
try to require the packages listed in d/nodejs/additional_components.
Is it possible to get around it?
Cheers,
JP
Bug#973958: mpdscribble: New upstream version 0.23
On Sun, 08 Nov 2020 12:14:30 +0100 kaliko wrote: Dear Maintainer, A new version of mpdscribble is available, can you upload it :) I started working on it, here it is on salsa: https://salsa.debian.org/kaliko/mpdscribble Hope I did not break too much your gbp workflow. Mainly I migrate the package to meson build, still need to update copyright. I also left alone the debconf part, I have no expertise with it. Cheers k OpenPGP_0x065FE53932DC551D.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Bug#961154: debarchiver: needs a build dependency on libpod-parser-perl
Hi, Could you please upload this soon? We've just kicked off the transition so this will prevent your package from being buildable in unstable soon. Cheers Dominic On Thu, May 21, 2020 at 08:56:35AM +0200, Ola Lundqvist wrote: > Thank you. Will add on next ipload. > > Den ons 20 maj 2020 22:06Niko Tyni skrev: > > > Package: debarchiver > > Version: 0.11.5 > > Severity: normal > > User: debian-p...@lists.debian.org > > Usertags: perl-5.32-transition > > > > This package uses /usr/bin/podselect, part of the Pod-Parser distribution > > which will be removed from the Perl core in upcoming version 5.32. > > It is being packaged separately for Debian as libpod-parser-perl > > (#960790), and affected packages need to declare appropriate dependencies > > on that. > > > > As the perl core packages already Provide libpod-parser-perl, these > > dependencies can be added at any time and do not need to wait for the > > separate package to enter sid. > > > > Please consider adding a build dependency sooner rather than later, > > to help our testing efforts. > > > > make[3]: Entering directory '/<>/po4a' > > podselect ../src/debarchiver.pl > debarchiver.pod > > > > -- > > Niko Tyni nt...@debian.org > >
Bug#973943: Test_compiler sporadically fails
On Sat, Nov 07, 2020 at 09:33:22PM -0500, James McCoy wrote:
> On Sat, Nov 07, 2020 at 12:59:48PM +0200, Graham Inggs wrote:
> > /<>/src/vim-gtk3/testdir/runtest.vim[461]..function
> > RunTheTest[39]..Test_compiler line 23: command did not fail: clist
> > command line..script
> > /<>/src/vim-gtk3/testdir/runtest.vim[461]..function
> > RunTheTest[39]..Test_compiler line 29: Pattern '\\n \\d\\+ Xfoo.pl:3:
> > Global symbol "$foo" requires explicit package name' does not match
> > '\n18 Xfoo.pl:3: Global symbol "$foo" requires explicit package name
> > (did you forget to declare "my $foo"?)'
>
> This is unrelated to the Python 3.9 transition and appears to just be a
> flaky test.
I haven't been able to reproduce this locally and the "line 23" error
is likely related to "line 29" failing.
Would you be able to reproduce the failure with the attached patch
applied? That should give more insight into what's going on.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
diff --git i/debian/patches/series w/debian/patches/series
index 926684fb7..f0b140145 100644
--- i/debian/patches/series
+++ w/debian/patches/series
@@ -2,3 +2,4 @@ debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch
debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch
debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch
+test_compiler-debug
diff --git i/debian/patches/test_compiler-debug w/debian/patches/test_compiler-debug
new file mode 100644
index 0..6d6ec7346
--- /dev/null
+++ w/debian/patches/test_compiler-debug
@@ -0,0 +1,18 @@
+diff --git i/src/testdir/test_compiler.vim w/src/testdir/test_compiler.vim
+index 6bf5f1521..55964313c 100644
+--- i/src/testdir/test_compiler.vim
w/src/testdir/test_compiler.vim
+@@ -26,7 +26,12 @@ func Test_compiler()
+ call setline(1, ['#!/usr/bin/perl -w', 'use strict;', 'my $foo=1'])
+ w!
+ call feedkeys(":make\\", 'tx')
+- call assert_fails('clist', 'E42:')
++ try
++let a=execute('clist')
++call assert_equal('', a)
++ catch
++call assert_match('E42:', v:errmsg)
++ endtry
+
+ call setline(1, ['#!/usr/bin/perl -w', 'use strict;', '$foo=1'])
+ w!
Bug#973983: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
Le 08/11/2020 à 18:33, Julien Puydt a écrit :
> Hi,
>
> Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit :
>> Le 08/11/2020 à 16:02, Julien Puydt a écrit :
>>> Package: pkg-js-tools
>>> Version: 0.9.45
>>>
>>> I'm trying to package lumino (ITP 972487), which has a pretty
>>> special
>>> structure:
>>> - no main module ;
>>> - only packages.
>>
>> Hi,
>>
>> did you try to set onne of them in debian/nodejs/main ?
>
> Uh... no, I hadn't, since there's no main. Now I have tried setting one
> as such and it goes through.
>
>>> My d/control has a build dep on pkg-js-tools, and uses "Provides:
>>> ${nodejs:Provides}" ; I have a d/nodejs/additional_components with
>>> packages/* to find the packages and my d/tests/pkg-js/test is only
>>> an
>>> "echo FIXME".
>>>
>>> When building the package, I get strange warnings, but they seem
>>> pretty
>>> harmless :
>>>
>>> dh_auto_install: warning: # /! "types" field should be replaced by
>>> "typings" in packages/algorithm/package.json
>>> Please report this bug
>>
>> @praveen asked for this warning
>
> I tried to search the web about it, and found only:
> https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
>
> I don't care either way.
>
>>> indeed, the main package.json has no 'name' field. It should
>>> instead try to require the packages listed in
>>> d/nodejs/additional_components.
>
> That was a bad idea : some of them only work in a browser (they use
> navigator) ; I chose one who doesn't for d/nodejs/main.
>
> I still have a lintian warning:
>
> W: node-lumino: nodejs-module-not-declared node-lumino-datastore
> usr/share/nodejs/@lumino/datagrid/package.json
>
> which is strange since I use ${nodejs:Provides} in d/control...
>
> The question is whether it is a problem with pkg-js-tools or with
> upstream : in the first case this bug report is legit, in the second
> case I should close that one and open one upstream.
Could you send me the link repo? I uploaded many packages with same
configuration (like babel or jest) without any problem
NB: you can alose restrict the installed modules using
debian/nodejs/submodules
Bug#973996: tulip: missing dependency -> python3-sip
Package: tulip Version: 5.4.0+dfsg-1 Severity: normal Hi, if I execute tulip from command line, when I open a new project I get the following messages: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/tulip/__init__.py", line 33, in import _tulip # noqa ModuleNotFoundError: No module named 'sip' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/tulipgui/__init__.py", line 23, in from tulip import tlp File "/usr/lib/python3/dist-packages/tulip/__init__.py", line 33, in import _tulip # noqa ModuleNotFoundError: No module named 'sip' if I install python3-sip I have no more error messages Ciao Davide -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.1-dp-20201024 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 tulip depends on: ii fonts-dejavu-core 2.37-2 ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-2 ii fonts-materialdesignicons-webfont 1.6.50-3 ii libbinutils2.35.1-2 ii libc6 2.31-4 ii libfreetype6 2.10.2+dfsg-4 ii libftgl2 2.4.0-2 ii libgcc-s1 10.2.0-16 ii libgl1 1.3.2-1 ii libglew2.1 2.1.0-4+b1 ii libgomp1 10.2.0-16 ii libjs-leaflet 1.7.1~dfsg-1 ii libogdf-tulip-5.4-05.4.0+dfsg-1 ii libpython3.8 3.8.6-1 ii libqt5core5a 5.15.1+dfsg-2 ii libqt5gui5 5.15.1+dfsg-2 ii libqt5network5 5.15.1+dfsg-2 ii libqt5webkit5 5.212.0~alpha4-7 ii libqt5widgets5 5.15.1+dfsg-2 ii libstdc++6 10.2.0-16 ii libtulip-core-5.4 5.4.0+dfsg-1 ii libtulip-gui-5.4 5.4.0+dfsg-1 ii libtulip-ogdf-5.4 5.4.0+dfsg-1 ii libtulip-ogl-5.4 5.4.0+dfsg-1 ii libtulip-python-5.45.4.0+dfsg-1 ii python33.8.2-3 tulip recommends no packages. Versions of packages tulip suggests: ii qtwayland5 5.15.1-3 -- no debconf information
Bug#973985: linux: Please enable CONFIG_SERIAL_8250_LPSS
Source: linux Version: 5.9.6-1 Severity: normal Deark Kernel Maintainers, Please enable CONFIG_SERIAL_8250_LPSS as a module or built-in driver in the kernel because without that the WD My Cloud PR4100 box runs the fan at full speed and this makes it practically unusable in small homes without manually compiling the module [1]. Cheers, Balint [1] https://community.wd.com/t/debian-linux-on-the-my-cloud-pr4100-pr2100/217141/11
Bug#973963: RFS: libonig/6.9.6-1 -- regular expressions library
Control: tags -1 moreinfo On Sun, Nov 08, 2020 at 01:19:46PM +0100, Jörg Frings-Fürst wrote: >... > Changes since the last upload: Looks good, except: >... >* New upstream release. >... > - Fix CVE-2020-26159 (Closes: #972113). >... What is the status of this CVE? If the comment in #972113 and what is written in the upstream issue linked from there is correct, then it was not a vulnerability in the first place. > CU > Jörg cu Adrian
Bug#923656: golang-github-klauspost-cpuid: FTBFS (TestCPUInfo_TSX sometimes fails)
control: fixed -1 1.2.0+dfsg1-1 control: close -1 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-klauspost-cpuid.html currently, reproducible builds dashboard shows this package doesn't have ftbfs issue. so closing this ticket. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#971969: libdata-alias-perl: FTBFS with Perl 5.32: t/03_copy.t failure
Control: unblock 968912 by -1 On Sat, Oct 10, 2020 at 09:54:54PM +0300, Niko Tyni wrote: > Source: libdata-alias-perl > Version: 1.21-1 > Severity: important > Tags: ftbfs sid bullseye > Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=130156 > User: debian-p...@lists.debian.org > Usertags: perl-5.32-transition > Control: block 968912 with -1 > > This package fails to build with Perl 5.32 (currently in experimental). > > From the build log: > >Useless use of a variable in void context at t/03_copy.t line 12. ># Looks like your test exited with 2 before it could output anything. >t/03_copy.t .. >1..14 >Dubious, test returned 2 (wstat 512, 0x200) >Failed 14/14 subtests > >[...] > >Test Summary Report >--- >t/03_copy.t(Wstat: 512 Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: Bad plan. You planned 14 tests but ran 0. >Files=32, Tests=608, 2 wallclock secs ( 0.07 usr 0.04 sys + 1.41 cusr > 0.29 csys = 1.81 CPU) >Result: FAIL There's no sign of this being fixed upstream, and popcon is very low. We shouldn't block the transition with this package. Dominic
Bug#961208: bucardo: diff for NMU version 5.5.0-1.1
Control: tags 961208 + patch
Control: tags 961208 + pending
Dear maintainer,
I've prepared an NMU for bucardo (versioned as 5.5.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u bucardo-5.5.0/debian/changelog bucardo-5.5.0/debian/changelog
--- bucardo-5.5.0/debian/changelog
+++ bucardo-5.5.0/debian/changelog
@@ -1,3 +1,10 @@
+bucardo (5.5.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add dependency on libpod-parser-perl (Closes: #961208)
+
+ -- Dominic Hargreaves Sun, 08 Nov 2020 18:26:12 +
+
bucardo (5.5.0-1) unstable; urgency=medium
[ Christoph Berg ]
diff -u bucardo-5.5.0/debian/control bucardo-5.5.0/debian/control
--- bucardo-5.5.0/debian/control
+++ bucardo-5.5.0/debian/control
@@ -11,7 +11,7 @@
Package: bucardo
Architecture: all
-Depends: ${misc:Depends}, adduser, perl (>= 5.10.0), libdbix-safe-perl, libdbd-pg-perl, libboolean-perl, lsb-base (>= 3.0-3)
+Depends: ${misc:Depends}, adduser, perl (>= 5.10.0), libdbix-safe-perl, libdbd-pg-perl, libboolean-perl, lsb-base (>= 3.0-3), libpod-parser-perl
Recommends: postgresql-plperl
Description: asynchronous replication system for PostgreSQL
Bucardo is an asynchronous PostgreSQL replication system, allowing for both
Bug#973999: armnn: FTBFS: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’
Source: armnn Version: 19.11.1-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org armnn fails to build arm64: | [ 1%] Building CXX object src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/ArgMinMax.cpp.o | cd /<>/build-area/src/backends/reference/workloads && /usr/bin/c++ -DARMCOMPUTECL_ENABLED -DARMCOMPUTENEON_ENABLED -DARMNNREF_ENABLED -DARMNN_SERIALIZER -DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\" -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -I/<>/include -I/<>/src/armnn -I/<>/src/armnnUtils -I/<>/src/backends -I/<>/src/profiling -isystem /<>/third-party -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -Wall -Werror -Wold-style-cast -Wno-missing-braces -Wconversion -Wsign-conversion -fPIC -o CMakeFiles/armnnRefBackendWorkloads.dir/ArgMinMax.cpp.o -c /<>/src/backends/reference/workloads/ArgMinMax.cpp | /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp: In function ‘arm_compute::PoolingLayerInfo armnn::armcomputetensorutils::BuildArmComputePoolingLayerInfo(const armnn::Pooling2dDescriptor&, bool)’: | /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp:160:57: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’ | 160 | return arm_compute::PoolingLayerInfo(poolingType); | | ^ | In file included from /usr/include/aarch64-linux-gnu/arm_compute/core/ITensorInfo.h:30, | from /usr/include/aarch64-linux-gnu/arm_compute/core/ITensor.h:27, | from /<>/src/backends/aclCommon/ArmComputeTensorUtils.hpp:10, | from /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp:5: | /usr/include/aarch64-linux-gnu/arm_compute/core/Types.h:1255:14: note: candidate: ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(arm_compute::PoolingType, arm_compute::DataLayout)’ See https://buildd.debian.org/status/fetch.php?pkg=armnn=arm64=19.11.1-1%2Bb2=1604748678=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#973943: Test_compiler sporadically fails
Hi James
On Sun, 8 Nov 2020 at 20:12, James McCoy wrote:
> Would you be able to reproduce the failure with the attached patch
> applied? That should give more insight into what's going on.
Thanks for this. It looks like sbuild is leaking some of my
environment, see the 'User Environment' section in the full log [1].
Failures:
From test_alot.vim:
Found errors in Test_compiler():
command line..script
/<>/src/vim-gtk3/testdir/runtest.vim[461]..function
RunTheTest[39]..Test_compiler line 25: Expected '' but got '\n 1:
perl: warning: Setting locale failed.\n 2: perl: warning: Please check
that your locale settings:\n 3:LANGUAGE = (unset),\n 4: LC_ALL = "",\n
5: LC_TIME = "en_ZA.UTF-8",\n 6: LC_MONETARY = "en_ZA.UTF-8",\n 7:
LC_ADDRESS = "en_ZA.UTF-8",\n 8: LC_TELEPHONE = "en_ZA.UTF-8",\n 9:
LC_MESSAGES = "C",\n10: LC_NAME = "en_ZA.UTF-8",\n11: LC_MEASUREMENT =
"en_ZA.UTF-8",\n12: LC_IDENTIFICATION = "en_ZA.UTF-8",\n13: LC_NUMERIC
= "en_ZA.UTF-8",\n14: LC_PAPER = "en_ZA.UTF-8",\n15: LANG =
(unset)\n16: are supported and installed on your system.\n17: perl:
warning: Falling back to the standard locale ("C").'
command line..script
/<>/src/vim-gtk3/testdir/runtest.vim[461]..function
RunTheTest[39]..Test_compiler line 34: Pattern '\\n \\d\\+ Xfoo.pl:3:
Global symbol "$foo" requires explicit package name' does not match
'\n18 Xfoo.pl:3: Global symbol "$foo" requires explicit package name
(did you forget to declare "my $foo"?)'
Regards
Graham
[1]
https://people.debian.org/~ginggs/python3.9-default/vim_8.2.1913-1+build1_amd64-2020-11-08T18:50:09Z.build
Bug#973983: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
Le 08/11/2020 à 20:52, Julien Puydt a écrit : > Le dimanche 08 novembre 2020 à 19:07 +0100, Xavier a écrit : >> Le 08/11/2020 à 18:53, Julien Puydt a écrit : >>> Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit : did you try to set onne of them in debian/nodejs/main ? >>> >>> Oh, dear... putting one of them in there did make things go >>> through, >>> but checking the resulting package : all the other components ended >>> up >>> in a node_modules directory within the chosen one's directory! >>> >>> That's definitely not correct. >> >> $ echo '*' > debian/nodejs/root_modules > > The package builds, with just: > > W: node-lumino: nodejs-module-not-declared node-lumino-datastore > usr/share/nodejs/@lumino/datastore/package.json > > The inspection of the output of dpkg-deb -c doesn't show anything > surprising. > > Running through autopkgtest works. > > I'm uploading the result ; the repo is now here: > Vcs-Git: https://salsa.debian.org/js-team/lumino.git > Vcs-Browser: https://salsa.debian.org/js-team/lumino Hi, no bug here, pkg-js-tools never export "main" component since it's normally the package name. You just have to export it by hand in debian/control (done). I can update pkg-js-tools to export this name when package name differs (like mocha, jest, rollup,...). Cheers, Xavier
Bug#974002: libopen-trace-format-dev: add a pkg-config file
Package: libopen-trace-format-dev
Version: 1.12.5+dfsg-7
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbffs
Control: affects -1 + src:vite
Packages (such as vite) that want to use libopen-trace-format-dev, are
supposed to call otfconfig to discover the relevant compiler flags.
Unfortunatel, otfconfig is a binary, so it does not work during cross
compilation. Please consider adding a pkg-config file such that a way
for discovering these flags during cross compilation is available. I'm
attaching a patch to implement it.
Helmut
diff --minimal -Nru otf-1.12.5+dfsg/debian/changelog
otf-1.12.5+dfsg/debian/changelog
--- otf-1.12.5+dfsg/debian/changelog2020-11-01 02:34:07.0 +0100
+++ otf-1.12.5+dfsg/debian/changelog2020-11-08 20:14:15.0 +0100
@@ -1,3 +1,10 @@
+otf (1.12.5+dfsg-7.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add open-trace-format.pc. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 08 Nov 2020 20:14:15 +0100
+
otf (1.12.5+dfsg-7) unstable; urgency=medium
* control: Really make libopen-trace-format-dev not Multi-Arch: same.
diff --minimal -Nru otf-1.12.5+dfsg/debian/libopen-trace-format-dev.install
otf-1.12.5+dfsg/debian/libopen-trace-format-dev.install
--- otf-1.12.5+dfsg/debian/libopen-trace-format-dev.install 2014-08-06
15:55:07.0 +0200
+++ otf-1.12.5+dfsg/debian/libopen-trace-format-dev.install 2020-11-08
20:14:15.0 +0100
@@ -4,3 +4,4 @@
usr/lib/*/libotfaux*.a
usr/lib/*/libopen*.so
usr/lib/*/libotfaux*.so
+usr/lib/*/pkgconfig/open-trace-format.pc
diff --minimal -Nru otf-1.12.5+dfsg/debian/patches/pkgconfig.patch
otf-1.12.5+dfsg/debian/patches/pkgconfig.patch
--- otf-1.12.5+dfsg/debian/patches/pkgconfig.patch 1970-01-01
01:00:00.0 +0100
+++ otf-1.12.5+dfsg/debian/patches/pkgconfig.patch 2020-11-08
20:14:09.0 +0100
@@ -0,0 +1,35 @@
+--- otf-1.12.5+dfsg.orig/Makefile.am
otf-1.12.5+dfsg/Makefile.am
+@@ -17,5 +17,10 @@
+
+ EXTRA_DIST = \
+ otf_vc08.sln \
++ open-trace-format.pc \
+ config/otf_get_version.sh \
+ VERSION
++
++pkgconfigdatadir = $(libdir)/pkgconfig
++
++pkgconfigdata_DATA = open-trace-format.pc
+--- otf-1.12.5+dfsg.orig/configure.ac
otf-1.12.5+dfsg/configure.ac
+@@ -154,6 +154,7 @@
+ LIBS="$pre_clock_gettime_LIBS"
+
+ AC_CONFIG_FILES([Makefile
++ open-trace-format.pc
+ vendor/jenkins_hash/Makefile
+ otflib/Makefile
+ otflib/OTF_inttypes_unix.h
+--- /dev/null
otf-1.12.5+dfsg/open-trace-format.pc.in
+@@ -0,0 +1,9 @@
++prefix=@prefix@
++libdir=@libdir@
++includedir=@includedir@
++
++Name: open-trace-format
++Description: Open Trace Format support library
++Version: @VERSION@
++Libs: -L${libdir} -lotfaux -lopen-trace-format @ZLIB_LIB_LINE@
@ZOIDFS_LIB_LINE@
++Cflags: -I${includedir}
diff --minimal -Nru otf-1.12.5+dfsg/debian/patches/series
otf-1.12.5+dfsg/debian/patches/series
--- otf-1.12.5+dfsg/debian/patches/series 2020-05-09 16:32:45.0
+0200
+++ otf-1.12.5+dfsg/debian/patches/series 2020-11-08 20:04:02.0
+0100
@@ -1 +1,2 @@
dfsg
+pkgconfig.patch
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#973984: dino-im: Recipients can't decrypt OMEMO messages sent by Dino
Source: dino-im Severity: normal Dear Maintainer, whenever I try to send OMEMO messages from Dino to a contact using the Conversations client, they can not decrypt the message. Other clients might have the same problem, but I didn't test it yet. The proper OMEMO key shows up under the contact settings in Dino. Verifying the key doesn't help. I haven't found any way to successfully send a decryptable OMEMO message. I actually think that this bug is of 'important' severity, because I consider OMEMO to be a major selling point of Dino. But since it's still usable without OMEMO encryption, I left it at 'normal' to be sure. Sincerely Keno Goertz *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#973941: Pasted text looks same as cursor
On Sun, Nov 08, 2020 at 11:00:04AM -0500, Thomas Dickey wrote: > On Sun, Nov 08, 2020 at 08:55:52AM +0100, Sven Joachim wrote: > > 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. > > I've not noticed this (only use either of those when testing something). > > xterm doesn't color _inserted_ text, but only the _selected_ text. > > If the shell is (mis)using bracketed paste to temporarily paint colors > on the screen, there's not much to be done using xterm's resources... > > On the other hand, it's possible to turn off bracketed paste: > > https://mail.gnu.org/archive/html/bug-bash/2020-10/msg00082.html ...and that seems to be the recommendation from others: https://mail.gnu.org/archive/html/bug-bash/2020-10/msg00068.html (this is a defect in bash --- will reassign) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#973987: Please mention fcitx5 is available in bullseye
Package: release-notes Severity: wishlist Tags: bullseye X-Debbugs-Cc: z...@debian.org, by...@debian.org This is following up for #926723, which is "fcitx may not working with Wayland in buster". The fcitx upstream releases fcitx5 recently, named the "the next generation" of fcitx, which is available in bullseye, and supports wayland. The old fcitx's version will remain 4.x, but will still be maintained in bullseye. But users are highly recommended to use fcitx5, especially wayland users. However tasksel of task-chinese-s-desktop and task-chinese-t-desktop is still recommending fcitx, not fcitx5 currently.
Bug#973989: libgav1 FTBFS on armel: symbol differences
Source: libgav1 Version: 0.16.0-4 Severity: important Tags: ftbfs Control: affects -1 src:libavif https://buildd.debian.org/status/fetch.php?pkg=libgav1=armel=0.16.0-4=1604703920=0 ... dh_makeshlibs -a -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgav1-0/DEBIAN/symbols doesn't match completely debian/libgav1-0.symbols --- debian/libgav1-0.symbols (libgav1-0_0.16.0-4_armel) +++ dpkg-gensymbolsvcOZhb 2020-11-06 23:05:17.669923566 + @@ -21,15 +21,15 @@ _ZN7libgav17DecoderC2Ev@Base 0.16.0 _ZN7libgav17DecoderD1Ev@Base 0.16.0 _ZN7libgav17DecoderD2Ev@Base 0.16.0 - (arch=riscv64)_ZTIN9__gnu_cxx7__mutexE@Base 0.16.0 - (arch=riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 - (arch=!riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 - (arch=riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 - (arch=!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 - (arch=riscv64)_ZTSN9__gnu_cxx7__mutexE@Base 0.16.0 - (arch=riscv64)_ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 - (arch=!riscv64)_ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 - (arch=riscv64)_ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 - (arch=!riscv64)_ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 + _ZTIN9__gnu_cxx7__mutexE@Base 0.16.0 + _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 +#MISSING: 0.16.0-4# (arch=!riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 + _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 +#MISSING: 0.16.0-4# (arch=!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 + _ZTSN9__gnu_cxx7__mutexE@Base 0.16.0 + _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 +#MISSING: 0.16.0-4# (arch=!riscv64)_ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 + _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 0.16.0 +#MISSING: 0.16.0-4# (arch=!riscv64)_ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 0.16.0 (c++|arch-bits=32)"libgav1::Decoder::EnqueueFrame(unsigned char const*, unsigned int, long long, void*)@Base" 0.16.0 (c++|arch-bits=64)"libgav1::Decoder::EnqueueFrame(unsigned char const*, unsigned long, long, void*)@Base" 0.16.0 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:34: binary-arch] Error 25
Bug#973991: gitaly FTBFS: test failures
Source: gitaly
Version: 13.3.9+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=gitaly=sid
...
FAIL
FAILgitlab.com/gitlab-org/gitaly/client 0.169s
? gitlab.com/gitlab-org/gitaly/cmd/gitaly [no test files]
? gitlab.com/gitlab-org/gitaly/cmd/gitaly-blackbox[no test files]
? gitlab.com/gitlab-org/gitaly/cmd/gitaly-debug [no test files]
{"level":"fatal","msg":"error configuring tests: storage {Name:default
Path:/<>/obj-aarch64-linux-gnu/src/gitlab.com/gitlab-org/gitaly/internal/testhelper/testdata/data}
path must exist: stat
/<>/obj-aarch64-linux-gnu/src/gitlab.com/gitlab-org/gitaly/internal/testhelper/testdata/data:
no such file or directory","time":"2020-11-07T10:43:42.498Z"}
FAILgitlab.com/gitlab-org/gitaly/cmd/gitaly-hooks 0.023s
{"level":"fatal","msg":"error configuring tests: storage {Name:default
Path:/<>/obj-aarch64-linux-gnu/src/gitlab.com/gitlab-org/gitaly/internal/testhelper/testdata/data}
path must exist: stat
/<>/obj-aarch64-linux-gnu/src/gitlab.com/gitlab-org/gitaly/internal/testhelper/testdata/data:
no such file or directory","time":"2020-11-07T10:43:44.125Z"}
FAILgitlab.com/gitlab-org/gitaly/cmd/gitaly-ssh 0.565s
...
make[1]: *** [debian/rules:39: override_dh_auto_test] Error 1
Bug#973983: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
Le 08/11/2020 à 18:53, Julien Puydt a écrit : > Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit : >> did you try to set onne of them in debian/nodejs/main ? > > Oh, dear... putting one of them in there did make things go through, > but checking the resulting package : all the other components ended up > in a node_modules directory within the chosen one's directory! > > That's definitely not correct. $ echo '*' > debian/nodejs/root_modules
Bug#973995: ITP: fonts-iosevka -- Slender typeface for code, from code
Package: wnpp Severity: wishlist * Package name: fonts-iosevka Version : 3.71 Upstream Authors: Belleve Invis * URL : https://github.com/be5invis/Iosevka * License : OFL-1.1 Description : Slender typeface for code, from code This typeface contains 9 weights (Thin to Heavy) alongside with both italic and oblique versions, with the same metrics as the regular one. Package will be available at http://phd-sid.ethz.ch/debian/fonts-iosevka/ and also at mentors.debian.net (ITP to follow) and fonts team maintained
Bug#968912: transition: perl 5.32
On Sat, Nov 07, 2020 at 09:13:50AM +0100, Sebastian Ramacher wrote: > On 2020-10-15 22:29:53 +0200, Sebastian Ramacher wrote: > > On 2020-10-15 18:27:08 +0100, Niko Tyni wrote: > > > These are resolved now, and all known regressions found in our test > > > rebuilds are marked as blocking this bug. > > > > > > The libpod-parser-perl dependencies are trivial to add. > > > > > > There's no fix for libdata-alias-perl, and I expect we'll need to remove > > > it from testing. It's just an optional dependency for other packages > > > AFAICS, so I don't expect much fallout (as long as the build dependencies > > > are relaxed in libio-stream-perl and libmethod-signatures-perl first.) > > > > > > Could we raise the remaining bugs to 'serious' now? Do you have any > > > guesstimate on the timing for a transition slot? > > > > There is some overlap with the currently ongoing ocaml transition. So > > let's wait until that one is done. > > The ocaml transition has finished, so please go ahead with the upload to > unstable. I've raised the remaining bugs to serious and uploaded 5.32 to unstable. Cheers Dominic.
Bug#973819: /usr/bin/pipewire-media-session: coredump after system upgrade to bullseye
Hi Simon, On 11/8/20 5:33 PM, Simon McVittie wrote: Control: tags -1 + moreinfo On Thu, 05 Nov 2020 at 15:27:11 +0100, Uwe Kleine-König wrote: pipewire-media-session segfaulted after I upgraded my system to bullseye. Does it do this repeatably, or only once? New upstream release 0.3.15 (now in testing) is meant to fix some regressions, so it might fix this? I upgraded to this version now. But also before the crash only happened once (during the first login after upgrading my machine to bullseye). The coredump is quite big (as is the output of gdb's bt command on it) If this is reproducible, please could you send or upload the gdb bt output? The core dump itself is only useful if using snapshot.debian.org or similar to force all -dbgsym packages to versions that match yours. I installed the debug symbol packages now, but I'm not motivated to pick the right debug symbol packages using snapshot.d.o. Of course this doesn't help for the coredump I reported here, but if it will happen again, you get a trace with the full information. Sorry, I didn't look in detail and so didn't notice that the coredumpctl output didn't include the full information. Best regards Uwe
Bug#973836: pipewire 0.3.14-1 causes pulseaudio failures on gnome desktop
Version: 0.3.15-1 Control: tags 973836 - moreinfo On Sun 2020-11-08 16:25:56 +, Simon McVittie wrote: > I think this may have been a regression in 0.3.14 that was fixed in 0.3.15 > (pipewire's experimental PulseAudio server reimplementation was enabled by > default, but shouldn't have been). Please try with 0.3.15-1? I can confirm that after upgrading to pipewire 0.3.15-1, the problem i had reported as https://bugs.debian.org/973836 went away. Thanks for the prompt fix, Simon! --dkg signature.asc Description: PGP signature
Bug#504044: On starting (and stopping) rngd
Hi *, I’m copying this eMail to those who requested various starting methods for rngd and those who can probably help me with it. Background: I took over the heavily patched 2.x series of rng-tools as “rng-tools-debian”, which is currently started from a sysvinit script only. Now I have got requests for starting it different ways: • my own arngc (not packaged in Debian itself) starts it as client of an stunnel (for entropy distribution over the network), so it must avoid starting rngd from the init script… but might make use of stopping at system shutdown? (arngc is always started manually or late, it needs network and possibly additionally VPN set up) • some people wish for a systemd script • according to some people, the /dev/hwrng device sometimes was not online when rngd was started, so we need a way to wait for that (the submitter suggested a systemd unit with multiple delayed restart attempts, which is… too crude) • some people use a HWRNG that only comes online after some activity (e.g. plugging in a USB device, or powering up the WLAN chip), and so want it started from udev (but how to stop in that case?) My first question is to rngd upstream: does it, at all, make sense to start rngd multiple times? If so, how would I best manage that? If not, how would we best deal with possibly having multiple entropy sources? Then I need init system-related help. I need to write a systemd unit and a udev start script; I’ll probably factor out what the sysvinit script does and put that into a new shell script and start it from both sysvinit and systemd unit and document that this is the script to start from one’s udev rules somewhere? I also need information on how I can delay the rngd start to occur after udev has set up /dev/hwrng but not if there is nothing to set up for it, that is, no source, or already set up earlier / built into the kernel. Then, I have a report in #466946 indicating that stopping rngd on system shutdown might not be needed; I asked on http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2020-November/thread.html#3753 for comments on that. On one hand, not stopping rngd until the bitter end ensures it stays available; on the other hand, it can negatively affect things like umounting, cryptsetup unconfiguration, etc; in fact, on my own systems, I always get “process still running” messages from insserv(?) for the rngd instances started from arngc (see above). So I was considering letting the init script stop all rngd instances (a simple pkill would do the trick, I assume) on system shutdown, but don’t know if that’s a good idea and if it would work with systemd. There’s also the question whether/how to stop the instances started by udev. The question of whether to allow multiple rngd processes (see above) also comes into play. Finally: yes, I’m aware of rng-tools5 and its version 6.x, but the version “traditionally shipped with Debian” contains a lot of new functionality that never made it upstream and as such has many users; arngc, for example, requires this functionality, as do others (cf. #951799). Thanks in advance, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
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#973941: Pasted text looks same as cursor
On Sun, Nov 08, 2020 at 08:55:52AM +0100, Sven Joachim wrote: > 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. I've not noticed this (only use either of those when testing something). xterm doesn't color _inserted_ text, but only the _selected_ text. If the shell is (mis)using bracketed paste to temporarily paint colors on the screen, there's not much to be done using xterm's resources... On the other hand, it's possible to turn off bracketed paste: https://mail.gnu.org/archive/html/bug-bash/2020-10/msg00082.html -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#973997: minetest-mod-moreblocks: Depends on non-existent (misspelled) "minetestserver" package
Package: minetest-mod-moreblocks
Version: 2.0.0-2
Severity: normal
X-Debbugs-Cc: mad...@mir.com
Dear Maintainer,
This package has a dependency on "minetest | minetestserver", however,
there is no "minetestserver" package.
I think this should specify "minetest | minetest-server" instead.
("minetest-server" is the name of the package which performs a non-client,
server-only install of minetest.)
-mm
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 minetest-mod-moreblocks depends on:
ii minetest 5.3.0+repack-1
Versions of packages minetest-mod-moreblocks recommends:
ii minetest-mod-intllib 20180811-1
minetest-mod-moreblocks suggests no packages.
-- no debconf information
Bug#974001: ITP: wtype -- xdotool type for wayland
Package: wnpp Severity: wishlist Owner: Birger Schacht X-Debbugs-Cc: debian-de...@lists.debian.org, bir...@debian.org * Package name: wtype Version : 0.2 Upstream Author : Josef Gajdusek * URL : https://github.com/atx/wtype * License : MIT Programming Lang: C Description : xdotool type for wayland
Bug#973787: pipewire crash gnome-shell / gdm on start
Control: tags -1 + moreinfo On Thu, 05 Nov 2020 at 07:38:18 +0100, Michael Ott wrote: > After updating to 0.3.14 gdm starts normal for one second and then I got a > black screen with blinking cursor. After switch to another terminal and back > it > works. I can't reproduce this, but I also couldn't reproduce the problems that some other people had with 0.3.12. Does 0.3.15-1 resolve this? smcv
Bug#973836: pipewire 0.3.14-1 causes pulseaudio failures on gnome desktop
Control: tags -1 + moreinfo On Thu, 05 Nov 2020 at 15:21:14 -0500, Daniel Kahn Gillmor wrote: > When pipewire upgraded to 0.3.14-1, pavucontrol no longer gives me any > sort of control over the audio device (the error text says it's waiting). > > Similarly, other pulseaudio-using applications don't work right -- in > some cases hanging for ~30 seconds while (i think) waiting to hear back > from a pulseaudio service. I think this may have been a regression in 0.3.14 that was fixed in 0.3.15 (pipewire's experimental PulseAudio server reimplementation was enabled by default, but shouldn't have been). Please try with 0.3.15-1? smcv
Bug#973787: pipewire crash gnome-shell / gdm on start
Hi Simon! I had this problem on 0.3.15. But it is gone with 0.3.15 and the new pulseaudio version in experimental You can close it CU Michael > Control: tags -1 + moreinfo > > On Thu, 05 Nov 2020 at 07:38:18 +0100, Michael Ott wrote: > > After updating to 0.3.14 gdm starts normal for one second and then > > I got a > > black screen with blinking cursor. After switch to another terminal > > and back it > > works. > > I can't reproduce this, but I also couldn't reproduce the problems > that > some other people had with 0.3.12. > > Does 0.3.15-1 resolve this? > > smcv -- CU Michael -- ,''`. : :' : Michael Ott `. `' e-mail: michael at k-c13 dot org `- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
Bug#973990: shorewall: Fails to start with "Couldn't load match `iface':No such file or directory"
Rebooted back to 5.8.0-3-amd64, it works! Something happened with Linux 5.9...
Bug#973993: ITP: golang-github-profclems-go-dotenv -- A minimalist library for reading and atomically writing .env configuration files in Go
Package: wnpp
Severity: wishlist
Owner: TODO
* Package name: golang-github-profclems-go-dotenv
Version : 0.1.0-1
Upstream Author : Clement Sam
* URL : https://github.com/profclems/go-dotenv
* License : Expat
Programming Lang: Go
Description : A minimalist library for reading and atomically writing
.env configuration files in Go
Dotenv Go Report Card
(https://goreportcard.com/report/github.com/profclems/go-dotenv) PkgGoDev
(https://pkg.go.dev/mod/github.com/profclems/go-dotenv) Dotenv is a
minimal Go Library for reading and writing .env configuration files.
It uses renameio (https://github.com/google/renameio) to perform atomic
write operations making sure applications never see unexpected file
content (a half-written file, or a 0-byte file).
.
Dotenv reads config in the following order. Each item takes precedence
over the item below it: • env• key-value config cache/store• config
The config cache store is set on first read operation. Installation sh
go get -u github.com/joho/godotenv
.
Usage Assuming you have a .env file in the current directory with the
following values env S3_BUCKET=yours3bucket SECRET_KEY=yoursecretKey
PRIORITY_LEVEL=2
.
Reading .env files ```go package main
.
import (
"log"
"github.com/profclems/go-dotenv"
.
)
.
func main() {
// .env - It will search for the .env file in the current
directory and load it. // You can explicitly set config file with
dotenv.SetConfigFile("path/to/file.env") err := dotenv.LoadConfig()
if err != nil {
log.Fatalf("Error loading .env file: %v", err)
}
.
s3Bucket := dotenv.GetString("S3BUCKET")
secretKey := dotenv.GetString("SECRETKEY") priorityLevel :=
dotenv.GetInt("PRIORITY_LEVEL")
.
// now do something with s3 or whatever } ``` Writing .env files ```go
import (
"fmt" "github.com/profclems/go-dotenv" "log"
)
.
func main() {
// SetConfigFile explicitly defines the path, name and extension
of the config file. dotenv.SetConfigFile("config/.env")
dotenv.LoadConfig()
dotenv.Set("STRONGEST_AVENGER", "Hulk") dotenv.Set("PLAYER_NAME", "Anon")
.
err := dotenv.Save() if err != nil {
log.Fatal(err)
}
.
value := dotenv.GetString("STRONGEST_AVENGER") fmt.Printf("%s = %s \n",
"STRONGEST_AVENGER", value)
.
value = dotenv.GetString("PLAYER_NAME") fmt.Printf("%s = %s \n",
"PLAYER_NAME", value)
.
}
.
```
.
All the above examples use the global DotEnv instance. You can instantiate
a new Dotenv instance:
.
```go cfg := dotenv.Init() // This will create a Dotenv instance using
.env from the current dir
.
or
.
cfg := dotenv.Init("path/to/.env") cfg.LoadConfig()
.
val := cfg.GetString("SOME_ENV") ``` Getting Values From DotEnv
The following functions and methods exist to get a value depending
the Type: • Get(key string) : interface{}• GetBool(key string)
: bool• GetFloat64(key string) : float64• GetInt(key string)
: int• GetIntSlice(key string) : []int• GetString(key string)
: string• GetStringMap(key string) : map[string]interface{}•
GetStringMapString(key string) : map[string]string• GetStringSlice(key
string) : []string• GetTime(key string) : time.Time• GetDuration(key
string) : time.Duration• isSet(key string) : bool• LookUp(key string)
: (interface, bool)Contributing Contributions are most welcome! It could
be a new feature, bug fix, refactoring or even reporting an issue. •
Fork it• Create your feature branch (git checkout -b my-new-feature)•
Commit your changes (git commit -am 'Added some feature')• Push to the
branch (git push origin my-new-feature)• Create new Pull RequestLicense
Copyright © Clement Sam (http://twitter.com/clems_dev)
.
glab is open-sourced software licensed under the MIT (LICENSE) license.
TODO: perhaps reasoning
Bug#961152: apt-show-versions: diff for NMU version 0.22.11+nmu1
Control: tags 961152 + patch Control: tags 961152 + pending Dear maintainer, I've prepared an NMU for apt-show-versions (versioned as 0.22.11+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru apt-show-versions-0.22.11/debian/changelog apt-show-versions-0.22.11+nmu1/debian/changelog --- apt-show-versions-0.22.11/debian/changelog 2019-02-16 11:10:23.0 + +++ apt-show-versions-0.22.11+nmu1/debian/changelog 2020-11-08 17:23:26.0 + @@ -1,3 +1,11 @@ +apt-show-versions (0.22.11+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build-dep on libpod-parser-perl, which is no longer shipped in +the core perl package (closes: #961152) + + -- Dominic Hargreaves Sun, 08 Nov 2020 17:23:26 + + apt-show-versions (0.22.11) unstable; urgency=medium * fix long standing bug handling incomplete entries in diff -Nru apt-show-versions-0.22.11/debian/control apt-show-versions-0.22.11+nmu1/debian/control --- apt-show-versions-0.22.11/debian/control 2019-02-16 11:10:23.0 + +++ apt-show-versions-0.22.11+nmu1/debian/control 2020-11-08 17:23:26.0 + @@ -3,7 +3,7 @@ Priority: optional Maintainer: Christoph Martin Uploaders: Andreas Hoenen -Build-Depends: debhelper (>= 9) +Build-Depends: debhelper (>= 9), libpod-parser-perl Build-Depends-Indep: po4a Standards-Version: 3.9.8 Vcs-Browser: https://salsa.debian.org/debian/apt-show-versions
Bug#973976: libb2-1: please package BLAKE3 library
Package: libb2-1 Version: 0.98.1-1.1 Severity: wishlist Please consider packaging the new BLAKE3 hash library, either as part of the libb2-1 package, or separately. https://www.blake2.net/ https://github.com/BLAKE3-team/BLAKE3 description: We present BLAKE3, an evolution of the BLAKE2 cryptographic hash that is both faster and also more consistently fast across different platforms and input sizes. BLAKE3 supports an unbounded degree of parallelism, using a tree structure that scales up to any number of SIMD lanes and CPU cores. On Intel Cascade Lake-SP, peak single-threaded throughput is 4x that of BLAKE2b, 8x that of SHA-512, and 12x that of SHA-256, and it can scale further using multiple threads. BLAKE3 is also efficient on smaller architectures: throughput on a 32-bit ARM1176 core is 1.3x that of SHA-256 and 3x that of BLAKE2b and SHA-512. Unlike BLAKE2 and SHA-2, with different variants better suited for different platforms, BLAKE3 is a single algorithm with no variants. It provides a simplified API supporting all the use cases of BLAKE2, including keying and extendable output. The tree structure also supports new use cases, such as verified streaming and incremental updates. https://raw.githubusercontent.com/BLAKE3-team/BLAKE3-specs/master/blake3.pdf Thank you. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (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 libb2-1 depends on: ii libc6 2.31-4 ii libgomp1 10.2.0-16 libb2-1 recommends no packages. libb2-1 suggests no packages. -- no debconf information
Bug#973988: tulip: Wrong link to the DejaVuSans.ttf font
Hi, I have found that also /usr/share/tulip/bitmaps/fontb.ttf has the same problem Ciao Davide
Bug#973983: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
Le dimanche 08 novembre 2020 à 19:07 +0100, Xavier a écrit : > Le 08/11/2020 à 18:53, Julien Puydt a écrit : > > Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit : > > > did you try to set onne of them in debian/nodejs/main ? > > > > Oh, dear... putting one of them in there did make things go > > through, > > but checking the resulting package : all the other components ended > > up > > in a node_modules directory within the chosen one's directory! > > > > That's definitely not correct. > > $ echo '*' > debian/nodejs/root_modules The package builds, with just: W: node-lumino: nodejs-module-not-declared node-lumino-datastore usr/share/nodejs/@lumino/datastore/package.json The inspection of the output of dpkg-deb -c doesn't show anything surprising. Running through autopkgtest works. I'm uploading the result ; the repo is now here: Vcs-Git: https://salsa.debian.org/js-team/lumino.git Vcs-Browser: https://salsa.debian.org/js-team/lumino Thanks, JP
Bug#958955: Update package description wrt Puppet 3
Hi Moritz, Moritz Muehlenhoff writes: > On Tue, Apr 28, 2020 at 08:57:39PM -0400, Nicholas D Steeves wrote: >> Control: tag -1 upstream >> >> Hi Moritz, >> >> Moritz Muehlenhoff writes: >> >> > Source: puppet-mode >> > Version: 0.4-1 >> > Severity: minor >> > >> > The short description currently reads "major mode for Puppet 3 manifests >> > in Emacs", >> > which sounds as if the support were limited to older Puppet versions, let's >> > simply use "major mode for Puppet manifests in Emacs"? After all the mode >> > supports >> > keywords of the current 5.x releases just fine. >> > >> >> I'm not sure why the upstream description specifies "Puppet 3", but if I >> had to speculate it might be because 0.4 doesn't support all Puppet 5 >> keywords. Do you know if support for Puppet 5 manifests is complete in >> this version? > > https://github.com/voxpupuli/puppet-mode/pull/106 and > https://github.com/voxpupuli/puppet-mode/pull/107 added support for > Puppet type annotations and keywords from 5.3, so this seems complete. > > I've been using this mode with a Puppet repository based on 5.5.10 > (as shipped in Debian buster) and I haven't noticed any missing > keywords or syntax elements, so from my PoV this seems to support > Puppet 5 just fine. > >> At any rate, would you like to open an upstream issue, or would you >> prefer if I do so? > > Ack, I just did that at https://github.com/voxpupuli/puppet-mode/issues/124 > Sorry for the delay. Thanks for filing the issue, it's odd that they didn't properly fix their description, and I've fixed ours in git. Cheers, Nicholas signature.asc Description: PGP signature
Bug#792406: rng-tools: Please support RDRAND/RDSEED
tags 792406 + moreinfo # while here anyway tags 969568 + moreinfo thanks Hi gebi, isn’t RDRAND/RDSEED supported/used by Linux itself nowadays? If so, can I close this bug? (Otherwise I would have to move it to rng-tools-debian for further consideration.) Thanks, //mirabilos -- (gnutls can also be used, but if you are compiling lynx for your own use, there is no reason to consider using that package) -- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
Bug#973298: rust-failure: Should rust-failure be removed from unstable?
hi As there was no objection (although admittely 2 weeks might be short), but the upstream is officially end-of-life. So just reassigned the bug to ftp.d.o for removal. Regards, Salvatore
Bug#974003: src:plink2: fails to migrate to testing for too long: FTBFS on ppc64el
Source: plink2 Version: 2.00~a3-200511+dfsg-1 Severity: serious Control: close -1 2.00~a3-200831+dfsg-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:plink2 in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=plink2 signature.asc Description: OpenPGP digital signature
Bug#967010: https://lifebox.vn/share/xi5iKcs1QnUpO7Ys
Google chrome gmail
