Bug#985825: re: #962696 - please consider renaming package
On Wed, 24 Mar 2021 12:12:40 + Holger Levsen wrote: > severity -1 serious Holger, I strongly object to your disgraceful participation in cancel "culture". For years (over 20 years since 1999 when this package was introduced) it was OK for our users but now you've decided that Debian users should not have "vrms" package in Bullseye because you don't like its name any more?!? Morally compromised name-fobia do not warrant "severity: serious". I can't stop you from foolish renaming of the package but desire to rename it do not warrant its exclusion from upcoming release. What happened to "users first" priority? -- All the best, Dmitry Smirnov GPG key : 2048R/CCBC38B3CCEE --- Multiple errors in the New York Times article about Sweden’s corona strategy -- Emanuel Karlsten, https://emanuelkarlsten.se/multiple-errors-in-the-new-york-times-article-about-swedens-corona-strategy/ signature.asc Description: This is a digitally signed message part.
Bug#986037: kdenlive: crashes on audio setup
Package: kdenlive Followup-For: Bug #986037 X-Debbugs-Cc: norb...@preining.info Just to confirm that even a recompilation on my system and running the recompiled version crashes. Best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.10 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdenlive depends on: ii ffmpeg 7:4.3.2-0+deb11u1 ii gstreamer1.0-plugins-bad 1.18.3-1+b1 ii kded5 5.80.0-1 ii kdenlive-data 20.12.3-1 ii kinit 5.80.0-1 ii kio5.80.0-1 ii libc6 2.31-10 ii libkf5archive5 5.80.0-1 ii libkf5bookmarks5 5.80.0-1 ii libkf5completion5 5.80.0-1 ii libkf5configcore5 5.80.0-1 ii libkf5configgui5 5.80.0-1 ii libkf5configwidgets5 5.80.0-1 ii libkf5coreaddons5 5.80.0-1 ii libkf5crash5 5.80.0-1 ii libkf5dbusaddons5 5.80.0-1 ii libkf5declarative5 5.80.0-1 ii libkf5filemetadata35.80.0-1 ii libkf5guiaddons5 5.80.0-1 ii libkf5i18n55.80.0-1 ii libkf5iconthemes5 5.80.0-1 ii libkf5itemviews5 5.80.0-1 ii libkf5jobwidgets5 5.80.0-1 ii libkf5kiocore5 5.80.0-1 ii libkf5kiofilewidgets5 5.80.0-1 ii libkf5kiogui5 5.80.0-1 ii libkf5kiowidgets5 5.80.0-1 ii libkf5newstuff55.80.0-1 ii libkf5notifications5 5.80.0-1 ii libkf5notifyconfig55.80.0-1 ii libkf5purpose-bin 5.80.0-1 ii libkf5purpose5 5.80.0-1 ii libkf5service-bin 5.80.0-1 ii libkf5service5 5.80.0-1 ii libkf5solid5 5.80.0-1 ii libkf5textwidgets5 5.80.0-1 ii libkf5widgetsaddons5 5.80.0-1 ii libkf5xmlgui5 5.80.0-1 ii libmlt++3 6.24.0-1 ii libmlt66.24.0-1 ii libqt5concurrent5 5.15.2+dfsg-5 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus55.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5multimedia5 5.15.2-3 ii libqt5network5 5.15.2+dfsg-5 ii libqt5qml5 5.15.2+dfsg-5 ii libqt5quick5 5.15.2+dfsg-5 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5quickwidgets55.15.2+dfsg-5 ii libqt5svg5 5.15.2-2 ii libqt5webenginewidgets55.15.2+dfsg-3 ii libqt5widgets5 5.15.2+dfsg-5 ii libqt5xml5 5.15.2+dfsg-5 ii librttr-core0.9.6 0.9.6+dfsg1-4 ii libstdc++6 10.2.1-6 ii melt 6.24.0-1 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtqml-models2 5.15.2+dfsg-5 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-dialogs 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-5 ii qml-module-qtquick-window2 5.15.2+dfsg-5 ii qml-module-qtquick25.15.2+dfsg-5 Versions of packages kdenlive recommends: ii breeze 4:5.21.3-1 ii dvdauthor 0.7.2-1+b3 ii dvgrab 3.5+git20160707.1.e46042e-1+b1 ii frei0r-plugins 1.7.0-1 ii genisoimage9:1.1.11-3.2 ii oxygen-icon-theme 5:5.80.0-1 ii recordmydesktop0.3.8.1+svn602-1.1 ii swh-plugins0.4.17-2 Versions of packages kdenlive suggests: ii khelpcenter 4:20.12.3-1~np1 ii vlc 3.0.12-3 -- no debconf information
Processed: tagging 947589
Processing commands for cont...@bugs.debian.org: > # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947589#41 > tags 947589 + help upstream Bug #947589 [wicd-gtk] wicd-gtk: [experimental] wicd-gtk probably broken: no GTK dependency, still uses 'import gtk' Bug #946380 [wicd-gtk] wicd-gtk does not find gtk modules Added tag(s) upstream and help. Added tag(s) upstream and help. > thanks Stopping processing here. Please contact me if you need assistance. -- 946380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946380 947589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986064: spamassassin: Security update failed tue to error in post-installation script
Package: spamassassin Version: 3.4.2-1+deb10u3 Severity: grave Justification: renders package unusable I installed today's security update (3.4.2-1+deb10u3) and got the following error: Setting up spamassassin (3.4.2-1+deb10u3) ... dpkg: error processing package spamassassin (--configure): installed spamassassin package post-installation script subprocess returned err or exit status 1 Errors were encountered while processing: spamassassin E: Sub-process /usr/bin/dpkg returned an error code (1) I am happy to look into the reason, why the post-installation script failed, but how can I display the line number where it fails? Stephan -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spamassassin depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii libhtml-parser-perl 3.72-3+b3 ii libhttp-date-perl 6.02-1 ii libmail-dkim-perl 0.54-1 ii libnet-dns-perl 1.19-1 ii libnetaddr-ip-perl 4.079+dfsg-1+b3 ii libsocket6-perl 0.29-1+b1 ii libsys-hostname-long-perl 1.5-1 ii libwww-perl 6.36-2 ii lsb-base10.2019051400 ii perl [libarchive-tar-perl] 5.28.1-6+deb10u1 ii w3m 0.5.3-37 Versions of packages spamassassin recommends: ii gnupg 2.2.12-1+deb10u1 ii libio-socket-inet6-perl2.72-2 ii libmail-spf-perl 2.9.0-4 ii perl [libsys-syslog-perl] 5.28.1-6+deb10u1 iu sa-compile 3.4.2-1+deb10u3 ii spamc 3.4.2-1+deb10u3 Versions of packages spamassassin suggests: pn libdbi-perl pn libencode-detect-perl pn libgeo-ip-perl ii libio-socket-ssl-perl 2.060-3 pn libnet-patricia-perl ii perl [libcompress-zlib-perl] 5.28.1-6+deb10u1 pn pyzor pn razor -- Configuration Files: /etc/default/spamassassin changed: OPTIONS="--create-prefs --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 -- no debconf information
Bug#986063: live-build wrongly setups security repository for Bullseye: bullseye/updates instead of bullseye-security
Package: live-build
Version: 1:20190311
Severity: grave
Hi,
In functions/sourcelist.sh line 88, one can read:
echo "deb ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}/updates
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
echo "deb-src ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}/updates
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
So, effectively, this makes it bullseye/updates when it really should be
bullseye-security. So these lines must be replaced by:
echo "deb ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}-security
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
echo "deb-src ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}-security
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
This makes live-build not useable for me, as I do setup the security
repositories, and "lb build" just fails on me because of this problem.
Probably, what should be done is something like this:
if [ ${PARENT_DISTRIBUTION} = "buster" ] || [ ${PARENT_DISTRIBUTION} =
"stretch" ] ; then
SEC_REPO="/updates"
else
SEC_REPO="-security"
fi
to keep a bit of backward compatibility. I'll let the current maintainers of
live-build decide...
Cheers,
Thomas Goirand (zigo)
Bug#986054: FTBFS on several architectures
Package: firefox Version: 87.0-1 Severity: serious Hi, thank you so much for taking care about firefox in debian. unfortunaly, 87.0-1 failed to build on several architectures: https://buildd.debian.org/status/package.php?p=firefox=unstable Regards, Daniel
Bug#985281: r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions
Hi Étienne, On 27/03/2021 22.43, Étienne Mollier wrote: There is however this upgrade path that I struggle to fix, note the missing --distupgrade-to-testdebs, which goes through the existing 0.17+dfsg-2 in Testing, and which is still broken: That's a stable2testing2sid test (-d buster -d bullseye -d sid) and you can do that with --d-t-t, too. (you could also use -d buster -d bullseye -d bullseye --d-t-t, yes, 2x -d bullseye) The breakage is caused by by upgrading to the bullseye version, debsums says debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap4.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap4.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.foundation.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.foundation.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.jqueryui.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.jqueryui.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.material.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.material.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.semanticui.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.semanticui.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.uikit.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/dataTables.uikit.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/jquery.dataTables.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables/css/jquery.dataTables.min.css (from libjs-jquery-datatables package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.html5.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.html5.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.jqueryui.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.jqueryui.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.print.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.print.min.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/dataTables.buttons.js (from libjs-jquery-datatables-extensions package) debsums: missing file /usr/share/javascript/jquery-datatables-extensions/Buttons/js/dataTables.buttons.min.js (from libjs-jquery-datatables-extensions package) debsums is not entirely right, the files still exist (as in 'test -e'), but have been replaced by dangling symlinks: (do you want to file a bug
Bug#985936: marked as done (ldb: CVE-2020-27840)
Your message dated Sun, 28 Mar 2021 19:18:39 + with message-id and subject line Bug#985936: fixed in ldb 2:2.2.0-3.1 has caused the Debian Bug report #985936, regarding ldb: CVE-2020-27840 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldb Version: 2:2.2.0-3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugzilla.samba.org/show_bug.cgi?id=14595 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ldb. CVE-2020-27840[0]: | Heap corruption via crafted DN strings If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-27840 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27840 [1] https://bugzilla.samba.org/show_bug.cgi?id=14595 [2] https://www.samba.org/samba/security/CVE-2020-27840.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ldb Source-Version: 2:2.2.0-3.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ldb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ldb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Mar 2021 19:52:18 +0100 Source: ldb Architecture: source Version: 2:2.2.0-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Samba Maintainers Changed-By: Salvatore Bonaccorso Closes: 985935 985936 Changes: ldb (2:2.2.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * ldb_dn: avoid head corruption in ldb_dn_explode (CVE-2020-27840) (Closes: #985936) * pytests: move Dn.validate test to ldb * ldb/attrib_handlers casefold: stay in bounds (CVE-2021-20277) (Closes: #985935) * ldb: add tests for ldb_wildcard_compare * ldb tests: ldb_match tests with extra spaces * ldb: Remove tests from ldb_match_test that do not pass Checksums-Sha1: 28afad10d4c37680e514b35a0ee99953a1f80405 2601 ldb_2.2.0-3.1.dsc 47b6781531859e3e6d0ebefbff96a2e23b89efd7 25160 ldb_2.2.0-3.1.debian.tar.xz 921ba70219ee7c06dea446fe2530c66506393303 7126 ldb_2.2.0-3.1_source.buildinfo Checksums-Sha256: c84f8b97c8b7191670cfbf55bc0d09d383478f7db7377cccf85a5d6754a3c161 2601 ldb_2.2.0-3.1.dsc a110edc78bbbafbb04c3238ac7fa400a37c09012ca5ed727959f4c25c5fa24e0 25160 ldb_2.2.0-3.1.debian.tar.xz 4a593f6abe9feaca605026f0e00ce83b2d545251dd04c6640282ad916fea33f7 7126 ldb_2.2.0-3.1_source.buildinfo Files: 2dd4efd6256ddcc1a456647c287c7b2d 2601 devel optional ldb_2.2.0-3.1.dsc 9d32b8e2579e77f0a67f50a678c00d0e 25160 devel optional ldb_2.2.0-3.1.debian.tar.xz da72599af22757cf9cd872927f20f90b 7126 devel optional ldb_2.2.0-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmBeLaRfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EUtEP/2VWCOsSyz3cw4J98/ryc/8kYBFgSYvY 9L+qiDpkoE7MWY6vhMyNFbmFXwdkOskMS0SqHJFAONHbeTk2ApBZ9zIV/+wESdgp d+ID+vbS42jQOivBe4Aioqz9ZtZKuv2TLyBIirXwzyNL8qmprLSLnUrTh9FeYubC xrnwP3gxS6Yf8Bdlwuew71sUNSjbg0rcquq53I3BAXJP4X6/zRzqvTn2WdHJsfjf KavdXiSFggIwR0RDi4uL4MgTkxE8eJedxgHGPU71dVTdrJeDEd1Suq0LTDHU00Al ZgXsz0P3ZrsPqrAGmkaOxI1iLECsoiqP64Aw5rEA6R49vqeAeHR0C72bQokEYClJ v3y+B+3IxXIyYKioyx/P9vxPIERpm7KT36IYJSyYjKR4I2YXwXolMJ7gL7N6XQJZ Q9f6s24AOe/hTXptqc7FUETBTRodC1jRljfNSE6pUwBuUpeX3V35vYOj7O0KgEqE tfXjFdJ7RAoPWHary2c/Bf1LeWWWVP0ytmOqS9ZREk0+q2oLn0R8TGf1/hmKn/tS /oLLaKQz5CDafvq8SvC/eSWfT+2GljUijV3tqcMuIwpqVv9ZMGDKpS6ViKRQs3X8 nw3qPtx3Mzmwt7gqfEUk0MSpd1s4r1Rnd+9Ln02vhwWOG3L34btSvL6B9IUG+AN9 75JNKLqt/Kco =FUbj -END PGP SIGNATURE End Message ---
Bug#985935: marked as done (ldb: CVE-2021-20277)
Your message dated Sun, 28 Mar 2021 19:18:39 + with message-id and subject line Bug#985935: fixed in ldb 2:2.2.0-3.1 has caused the Debian Bug report #985935, regarding ldb: CVE-2021-20277 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldb Version: 2:2.2.0-3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugzilla.samba.org/show_bug.cgi?id=14655 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ldb. CVE-2021-20277[0]: | Out of bounds read in AD DC LDAP server If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-20277 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20277 [1] https://bugzilla.samba.org/show_bug.cgi?id=14655 [2] https://www.samba.org/samba/security/CVE-2021-20277.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ldb Source-Version: 2:2.2.0-3.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ldb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ldb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Mar 2021 19:52:18 +0100 Source: ldb Architecture: source Version: 2:2.2.0-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Samba Maintainers Changed-By: Salvatore Bonaccorso Closes: 985935 985936 Changes: ldb (2:2.2.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * ldb_dn: avoid head corruption in ldb_dn_explode (CVE-2020-27840) (Closes: #985936) * pytests: move Dn.validate test to ldb * ldb/attrib_handlers casefold: stay in bounds (CVE-2021-20277) (Closes: #985935) * ldb: add tests for ldb_wildcard_compare * ldb tests: ldb_match tests with extra spaces * ldb: Remove tests from ldb_match_test that do not pass Checksums-Sha1: 28afad10d4c37680e514b35a0ee99953a1f80405 2601 ldb_2.2.0-3.1.dsc 47b6781531859e3e6d0ebefbff96a2e23b89efd7 25160 ldb_2.2.0-3.1.debian.tar.xz 921ba70219ee7c06dea446fe2530c66506393303 7126 ldb_2.2.0-3.1_source.buildinfo Checksums-Sha256: c84f8b97c8b7191670cfbf55bc0d09d383478f7db7377cccf85a5d6754a3c161 2601 ldb_2.2.0-3.1.dsc a110edc78bbbafbb04c3238ac7fa400a37c09012ca5ed727959f4c25c5fa24e0 25160 ldb_2.2.0-3.1.debian.tar.xz 4a593f6abe9feaca605026f0e00ce83b2d545251dd04c6640282ad916fea33f7 7126 ldb_2.2.0-3.1_source.buildinfo Files: 2dd4efd6256ddcc1a456647c287c7b2d 2601 devel optional ldb_2.2.0-3.1.dsc 9d32b8e2579e77f0a67f50a678c00d0e 25160 devel optional ldb_2.2.0-3.1.debian.tar.xz da72599af22757cf9cd872927f20f90b 7126 devel optional ldb_2.2.0-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmBeLaRfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EUtEP/2VWCOsSyz3cw4J98/ryc/8kYBFgSYvY 9L+qiDpkoE7MWY6vhMyNFbmFXwdkOskMS0SqHJFAONHbeTk2ApBZ9zIV/+wESdgp d+ID+vbS42jQOivBe4Aioqz9ZtZKuv2TLyBIirXwzyNL8qmprLSLnUrTh9FeYubC xrnwP3gxS6Yf8Bdlwuew71sUNSjbg0rcquq53I3BAXJP4X6/zRzqvTn2WdHJsfjf KavdXiSFggIwR0RDi4uL4MgTkxE8eJedxgHGPU71dVTdrJeDEd1Suq0LTDHU00Al ZgXsz0P3ZrsPqrAGmkaOxI1iLECsoiqP64Aw5rEA6R49vqeAeHR0C72bQokEYClJ v3y+B+3IxXIyYKioyx/P9vxPIERpm7KT36IYJSyYjKR4I2YXwXolMJ7gL7N6XQJZ Q9f6s24AOe/hTXptqc7FUETBTRodC1jRljfNSE6pUwBuUpeX3V35vYOj7O0KgEqE tfXjFdJ7RAoPWHary2c/Bf1LeWWWVP0ytmOqS9ZREk0+q2oLn0R8TGf1/hmKn/tS /oLLaKQz5CDafvq8SvC/eSWfT+2GljUijV3tqcMuIwpqVv9ZMGDKpS6ViKRQs3X8 nw3qPtx3Mzmwt7gqfEUk0MSpd1s4r1Rnd+9Ln02vhwWOG3L34btSvL6B9IUG+AN9 75JNKLqt/Kco =FUbj -END PGP SIGNATURE End Message ---
Processed: Re: llvm-toolchain-11 autopkgtest segfaults on armhf
Processing control commands: > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659 Bug #980957 [src:llvm-toolchain-11] llvm-toolchain-11 autopkgtest segfaults on armhf Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=27659'. > affects -1 src:binutils Bug #980957 [src:llvm-toolchain-11] llvm-toolchain-11 autopkgtest segfaults on armhf Added indication that 980957 affects src:binutils -- 980957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659
control: affects -1 src:binutils
Invoking the clang with -V shows a failure in ld.bdf linker, a failure that
doesn't happen with gold linker and with object files (crt*.o) copied on local
directory.
I opened a bug against binutils people to track it down, hopefully they can
sort what is segfaulting there.
thanks
Gianfranco
On Sun, 24 Jan 2021 20:38:29 +0100 Paul Gevers wrote:
> Source: llvm-toolchain-11
> Version: 1:11.0.0-2
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainers,
>
> You package has an autopkgtest, great. However, it fails on armhf with a
> segfault.
>
> The error code is unfortunate as autopkgtest interprets it as a tmpfail,
> so the test is tried over and over again. I'll put the failure on the
> ci.d.n blocklist, to avoid that, and will lift the block when this bug
> is closed.
>
> Paul
>
> https://ci.debian.net/data/autopkgtest/testing/armhf/l/llvm-toolchain-11/9960854/log.gz
>
> echo '#include
> int main() {
> if (1==1) {
> printf("true");
> }else{
> printf("false");
> return 42;
> }
> return 0;}' > foo.c
> Testing linking ...
> rm foo bar.cc
>
> clang-$VERSION -flto foo.c -o foo
> clang: error: unable to execute command: Segmentation fault
> clang: error: linker command failed due to signal (use -v to see invocation)
> autopkgtest [02:17:39]: ERROR: testbed failure: testbed auxverb failed
> with exit code 254
>
Bug#985695: marked as done (libtree-sitter-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtree-sitter.so -> libtree-sitter.so.0.0)
Your message dated Sun, 28 Mar 2021 18:33:47 + with message-id and subject line Bug#985695: fixed in tree-sitter 0.19.4-1 has caused the Debian Bug report #985695, regarding libtree-sitter-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtree-sitter.so -> libtree-sitter.so.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtree-sitter-dev Version: 0.17.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m22.8s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libtree-sitter.so -> libtree-sitter.so.0.0 (libtree-sitter-dev:amd64) This looks like a missing dependency on libtree-sitter0. cheers, Andreas libtree-sitter-dev_0.17.3-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: tree-sitter Source-Version: 0.19.4-1 Done: James McCoy We believe that the bug you reported is fixed in the latest version of tree-sitter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated tree-sitter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Mar 2021 13:53:55 -0400 Source: tree-sitter Architecture: source Version: 0.19.4-1 Distribution: experimental Urgency: medium Maintainer: James McCoy Changed-By: James McCoy Closes: 985695 Changes: tree-sitter (0.19.4-1) experimental; urgency=medium . * New upstream release * Add missing libtree-sitter0 Depends to libtree-sitter-dev (Closes: #985695) * watch: Support tags with a leading "v" * Bump changelog to 0.19.4-1 * symbols: + Raise version for all APIs to 0.19 due to ABI break + Add ts_query_cursor_did_exceed_match_limit, new in 0.19.2 Checksums-Sha1: deb53bb852cf0fe791d3893c9ac3e60ccd71d194 2232 tree-sitter_0.19.4-1.dsc 1d7c9544e71d125b1387fc38c9eefb9f12df194a 2869856 tree-sitter_0.19.4.orig.tar.gz cc76104c1dc808945cfafada1ba3f41a8ae03c80 3992 tree-sitter_0.19.4-1.debian.tar.xz Checksums-Sha256: f2fdee16c71d6947cdfcde724170672fd2468061e5092af039a592a3ac21bb73 2232 tree-sitter_0.19.4-1.dsc 98e6b7f77d277235ef43023a8eee37745d1bc315c138481ed1b054cff158e817 2869856 tree-sitter_0.19.4.orig.tar.gz aa44a720dd7475f6ca79d611324700dcbe20f439de3df46926fac314d6a59a0b 3992 tree-sitter_0.19.4-1.debian.tar.xz Files: 3e72395cc62025f20858fd9bc0b10903 2232 libs optional tree-sitter_0.19.4-1.dsc c33b3201737a15780c077aafa373cc74 2869856 libs optional tree-sitter_0.19.4.orig.tar.gz e043b108aba00303341ba04e5a0ba80a 3992 libs optional tree-sitter_0.19.4-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmBgxw1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9sdFRAAh878QUMTxEA0vTjXFJh28/DGs8k7 Z4KJJAgEQzfxREI7E/nG7Qn2k4JJAlS42cK+v1rOYvHSG4O3rIb635gxBc2v+ySi NuojgvPEjMldqWpnYAr///vu7Bt5bCu3WSPoGLQ/giwe9HqgScsoTEDg/JkadxE5 +pk16OLgabKTarY3k4gaWZPL1qEsy6szrA1kkLo7uVC3jwRpUiz3dcqXLngZU7vB hUErn1newE4pogftslRxW0agWkUYSiEDuJ4GSXoQuuAWstKa8pMe65ZtJ3eInOHC lJeYEm0h+G4VHQcVCqtWzlc3fAiNbcjPnnifQaQGkZmJnGyXlgdyFP728czi0D7P Re6ZCIsEjNmmeH6inh3R0DGgqyZ47/jwpVLgeyNzITZckeWaj1ruhjLP4+rdaiGh o7IGTDwj1Dib5+IVREKOi0O4UnNGzueEGyFQq3ycWOMLsehG1NzEfpvi4xcaOyLk EPdHRS9CbxdOkupE70UeKANf9HOeB5/8FnQwWWHvFYG1DM7Wv0wd1ggJb12CN+1b s7QLvfp1gyWixrosUM7HveQyZ7S4M//Xi6JANvVhdzDrdZzIknfZraTNjuwdil3r b7vi1OpoFMzAGc3QHcAdMNXK6vEtOHwawwq/yw7uGNpPnoDOz4mhIuw/4nm+zEFv phUK7MIPIOpTkAo= =TRbg -END PGP SIGNATURE End Message ---
Bug#985505: marked as done (libosmocore-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libosmousb.so -> libosmousb.so.0.0.0)
Your message dated Sun, 28 Mar 2021 17:03:29 + with message-id and subject line Bug#985505: fixed in libosmocore 1.4.2-2 has caused the Debian Bug report #985505, regarding libosmocore-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libosmousb.so -> libosmousb.so.0.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libosmocore-dev Version: 1.4.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m28.1s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libosmousb.so -> libosmousb.so.0.0.0 (libosmocore-dev:amd64) libosmousb.so.0.0.0 does not seem to exist in any package in the archive. cheers, Andreas libosmocore-dev_1.4.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libosmocore Source-Version: 1.4.2-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of libosmocore, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated libosmocore package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Mar 2021 16:59:59 +0200 Source: libosmocore Architecture: source Version: 1.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Mobcom Maintainers Changed-By: Thorsten Alteholz Closes: 985505 Changes: libosmocore (1.4.2-2) unstable; urgency=medium . * remove links to files that are not included into the package (Closes: #985505) Checksums-Sha1: 958f885711c35ebbaca5b14bcf2db01c65d23ee2 3251 libosmocore_1.4.2-2.dsc 003bf10023d88c37ed1abd32407b1543468c37a4 29272 libosmocore_1.4.2-2.debian.tar.xz 14e7b43a294ea874f68062375864a9a894ffd4b5 14229 libosmocore_1.4.2-2_amd64.buildinfo Checksums-Sha256: 0a9570dde8c78c8d77f24cae5a5fd527fbf28862406b8d3a32b79ea000cc0403 3251 libosmocore_1.4.2-2.dsc deace6aadc30b7e98479126ad63478e10529f6ce5db26256a456e709c060 29272 libosmocore_1.4.2-2.debian.tar.xz 4cc0d8877952524e0a84c01d9bf8487226ed4104f3f52606c95626e7d8839517 14229 libosmocore_1.4.2-2_amd64.buildinfo Files: 39da4e1e4ecfcb4c42488e195065f061 3251 libs optional libosmocore_1.4.2-2.dsc 8a23b3ac8ce578d70d3e02e36ef95c84 29272 libs optional libosmocore_1.4.2-2.debian.tar.xz 061bdfe758ba8c7a4db3f194985e3da5 14229 libs optional libosmocore_1.4.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmBgtGpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR2R+D/9Od/QWhvoy7Y3RhfZUTWfAjE/+zvlw PTGUC5OW2ibIeXLdZ/NLlIQJeImLEOzFNfmW3w/vft2QiQShS2ZmfW/OxwjjfNVt veQEDvjd96jqdH5uJxOF88kMq6cudK+icHCz3yBRveHSBZxLE/30TflbRB4E0H+H Av9EYXTbiDVN1LTbsMISSLR4gXLCzOiFtuz0474o0rTAtTzhzyNCnIev/sQOOw/c n0Mf2iAgwhML8Jk0kcmJTZ6h+WTOJXIfFsXP8emjQNjSeN+wiZeznLvZ/PT/mwJI wOlTC4lZno5zOw8qW6MHbQbWuLGSr2J35tAhQKG9KW1fuVRUZ2CpUYE3PSbFkm3o wwoTo5EW3WsG+tkGNnYzm7MiNvsRRB4kpmZD/+ZEukTK2NF1kbWq5Cc5uBYiw6qG WbYoJnIJfhp6giatsWaZLZmMXjfSZcf6TIVtc3ve0PZ2JeAS7AbYP47owp5LcAJl ZYIcVemebuLgQTU8S740U4EbHMbnY+/trAxUCwPWXosPDpxsvBWzN+vqrHieVxhB IDQNQ9SjKCL0NdQwOqr/9nGMlce6T9UrfrvVjmTlhzCs2/NdovHmfenSvhkrLhtq eZPoX+uYg0OYLB9r4WypqRCO21B1xXUcZPVL7zbDBrV7MMaS12U2OEp8NWoeYZIv C4ZUC9V9Kg9EEg== =GPmQ -END PGP SIGNATURE End Message ---
Processed: Re: Bug#850291: gdm3: dependencies do not include an X11 server and a window manager
Processing control commands: > clone -1 -2 Bug #850291 [gdm3] gdm3: does not work without gnome-session Bug 850291 cloned as bug 986046 > notfound -1 3.30.2-3 Bug #850291 [gdm3] gdm3: does not work without gnome-session No longer marked as found in versions gdm3/3.30.2-3. > close -1 3.24.2-3 Bug #850291 [gdm3] gdm3: does not work without gnome-session Ignoring request to alter fixed versions of bug #850291 to the same values previously set Bug #850291 [gdm3] gdm3: does not work without gnome-session Marked Bug as done > retitle -2 gdm3: dependencies do not include an X11 server and a window > manager Bug #986046 [gdm3] gdm3: does not work without gnome-session Changed Bug title to 'gdm3: dependencies do not include an X11 server and a window manager' from 'gdm3: does not work without gnome-session'. -- 850291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850291 986046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#850291: gdm3: dependencies do not include an X11 server and a window manager
Control: clone -1 -2
Control: notfound -1 3.30.2-3
Control: close -1 3.24.2-3
Control: retitle -2 gdm3: dependencies do not include an X11 server and a
window manager
On Wed, 12 Jun 2019 at 08:56:56 -0500, Pascal Liehne wrote:
> Package: gdm3
> Version: 3.30.2-3
> Followup-For: Bug #850291
>
> It looks like the bug is back. After install of gdm3 and gnome-terminal
> in one command and login I get only the background image.
>
> HowTo reproduce:
> - Install Debian 10 RC1 via Netinstaller without additional software
> - run: apt-get install gdm3 gnome-terminal
> - reboot, so gdm3 ist started
> - login
> - you will see only the background image.
Sorry for the delay in responding to this. For future reference, it's
usually better to report a new bug than to reply to a bug that has already
been closed, particularly if you are not 100% sure that the old bug and
the new bug have the same root cause.
I don't think this is actually the same bug as #850291, so I've cloned
it to have a new bug number, and I'm closing #850291 again. Please use
the new bug number (when it gets allocated) for any further discussion
of this.
In #850291, the symptom was that without gnome-session installed, the
gdm greeter (the login prompt where you choose a username and session
type and enter your password) constantly restarts and is unusable.
In this new bug report, the greeter *is* usable - you get a list of users,
and you can attempt to log in. However, the login session does not
actually *work*. That seems like a distinct bug that should be handled
separately.
When I initially tried it, I got a different failure mode:
- The screen flashes to blank for a moment
- I'm brought back to the greeter prompt
This is because gdm3 does not depend on an X11 server (xserver-xorg-core).
Historically, gdm3 relied on X11 both to display the greeter and to run the
login session. However, now that GNOME uses Wayland by default, you can
run the gdm greeter and even a full GNOME session without actually needing
an X11 server - so it would seem incorrect for gdm3 to have a hard
dependency on xserver-xorg-core.
After installing xserver-xorg-core and rebooting, I get a different
failure mode: I log in, I see a background image (a blue elliptical
gradient, fading to a darker blue in the corners of the screen),
and there is no obvious way to interact with the system other than
rebooting: not even VT switching via Ctrl+Alt+F5 works. This is because
xserver-xorg-core is so minimal that it does not include any input
drivers. The next step is to install xserver-xorg, a metapackage that
includes video and input drivers. This is in gdm3's Recommends list
("packages that would be found together with this one in all but unusual
installations") but is not a hard dependency.
After installing xserver-xorg and rebooting, the new failure mode is
that I get the same background image as before, but now at least VT
switching via Ctrl+Alt+F5 works as expected. It appears that because
we do not have any more complete desktop environments installed, the
window manager that has been selected as a fallback is /usr/bin/mutter,
which is a relatively minimal demo/example window manager: it does not
have any built-in "chrome" to launch programs (like a panel or a menu),
but we can log in as the same user on a text console and run
"DISPLAY=:0 xterm" (if xterm is indeed installed), or create a file
~/.xsession with contents like this:
#!/bin/sh
xterm &
exec x-window-manager
to get a minimal, but minimally usable, desktop session.
Obviously none of this is ideal, but I would have a hard time
characterising any of this as being a release-critical bug, or choosing
where to put extra dependencies to make this work "out of the box".
The underlying issue here is that if you want things "already done
for you", then installing a complete desktop environment like GNOME,
KDE Plasma or XFCE is going to be a better route than building your own
desktop environment from individual pieces; and if you want to build your
own desktop environment from individual pieces, this is going to require
some understanding of how the pieces fit together and which ones you want.
If we added enough dependencies to make apt prevent you from accidentally
setting up an incomplete environment that is not actually practically
usable, then we would also prevent advanced users from building their own
desktop environments (or non-desktop-environment graphical environments)
that are more minimal.
In bullseye (Debian 11 prerelease), this is mitigated by gnome-shell no
longer having a dependency on mutter. It is still necessary to install
xserver-xorg-core and at least one input driver (which, again, are part
of gdm3's Recommends), but the fallback X11 session in a very minimal
installation will now be the x-terminal-emulator (gnome-terminal in your
example) rather than mutter, so at least you get a prompt from which you
can run more programs.
Some other ideas for possible improvements:
-
Bug#984980: libaqbanking44: Wrong message after sending an transaction
Hello Mechtilde, no, I didn't expect an unblock request to be required (it should migrate automatically due to passing autopkgtests). Feel free to file an unblock request if you disagree. Regards, Micha
Bug#986033: marked as done (avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1)
Your message dated Sun, 28 Mar 2021 15:10:21 +0100 with message-id <20210328141021.ga23...@mithrandir.lan.emorrp1.name> and subject line Re: [Pkg-utopia-maintainers] Bug#986033: avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1 has caused the Debian Bug report #986033, regarding avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: avahi Version: 0.7-4+deb10u1 Severity: serious Justification: Policy 7.3 Hi, with 10.9 released, I am unable to upgrade avahi on a dual architecture system with both amd64 and i386 packages. Because I couldn't see the +b1 version on tracker, here's the snapshot proof: https://snapshot.debian.org/package/avahi/0.7-4/#libavahi-common3_0.7-4:2b:b1 :~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libavahi-client3 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-client3:i386 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common-data (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common-data:i386 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common3 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common3:i386 (0.7-4+b1 => 0.7-4+deb10u1) 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. :~ $ sudo apt upgrade libavahi-client3 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libavahi-client3 : Breaks: libavahi-client3:i386 (!= 0.7-4+deb10u1) but 0.7-4+b1 is to be installed libavahi-client3:i386 : Breaks: libavahi-client3 (!= 0.7-4+b1) but 0.7-4+deb10u1 is to be installed E: Broken packages -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), (100, 'buster-fasttrack'), (100, 'buster-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Sun, Mar 28, 2021 at 02:51:55PM +0200, Michael Biebl wrote: > Maybe you have a package put on hold or some mirror is not up-to-date yet. Ah, sorry for the invalid serious report, closing. I don't know anything about holds so I have no idea why it was held back, but forcibly unholding them resolved my upgrade. :~ $ apt-mark showhold ... libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386 ... :~ $ sudo apt-mark unhold libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386 [sudo] password for emorrp1: Canceled hold on libavahi-client3:i386. Canceled hold on libavahi-common-data:i386. Canceled hold on libavahi-common3:i386. # before the unhold :~ $ apt policy libavahi-client3:amd64 libavahi-client3: Installed: 0.7-4+b1 Candidate: 0.7-4+deb10u1 Version table: 0.7-4+deb10u1 500 500 http://deb.debian.org/debian buster/main amd64 Packages *** 0.7-4+b1 100 100 /var/lib/dpkg/status :~ $ apt policy libavahi-client3:i386 libavahi-client3:i386: Installed: 0.7-4+b1 Candidate: 0.7-4+deb10u1 Version table: 0.7-4+deb10u1 500 500 http://deb.debian.org/debian buster/main i386 Packages *** 0.7-4+b1 100 100 /var/lib/dpkg/status signature.asc Description: PGP signature --- End Message ---
Processed: tagging 984873
Processing commands for cont...@bugs.debian.org: > # possibly duplicate of #977694 > tags 984873 + moreinfo Bug #984873 [src:linux] linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device) Ignoring request to alter tags of bug #984873 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 984873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 984873
Processing commands for cont...@bugs.debian.org: > tags 984873 + moreinfo Bug #984873 [src:linux] linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device) Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 984873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-utopia-maintainers] Bug#986033: avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1
Processing control commands: > tags -1 + moreinfo Bug #986033 [src:avahi] avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1 Added tag(s) moreinfo. -- 986033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986033: [Pkg-utopia-maintainers] Bug#986033: avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1
Control: tags -1 + moreinfo https://buildd.debian.org/status/package.php?p=avahi=buster looks good, i.e. avahi has been built on all architectures successfully. Could you paste the output of apt-cache policy libavahi-client3:amd64 apt-cache policy libavahi-client3:i386 Maybe you have a package put on hold or some mirror is not up-to-date yet. Michael
Bug#985281: marked as done (r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatabl
Your message dated Sun, 28 Mar 2021 12:48:34 + with message-id and subject line Bug#985281: fixed in r-cran-dt 0.17+dfsg-3 has caused the Debian Bug report #985281, regarding r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-cran-dt Version: 0.17+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: buster -> bullseye For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 1m34.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/AutoFill (r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/AutoFill (libjs-jquery-datatables-extensions) /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons (r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons (libjs-jquery-datatables-extensions) /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/css (r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons/css (libjs-jquery-datatables-extensions) /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions [...] /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables/images (r-cran-dt) != /usr/share/javascript/jquery-datatables/images (libjs-jquery-datatables) /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables -> ../../../../../../share/javascript/jquery-datatables /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables/js (r-cran-dt) != /usr/share/javascript/jquery-datatables/js (?) /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables -> ../../../../../../share/javascript/jquery-datatables cheers, Andreas --- End Message --- --- Begin Message --- Source: r-cran-dt Source-Version: 0.17+dfsg-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of r-cran-dt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated r-cran-dt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing
Bug#966904: marked as done (pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’?)
Your message dated Sun, 28 Mar 2021 12:48:28 + with message-id and subject line Bug#966904: fixed in pfstools 2.1.0-6 has caused the Debian Bug report #966904, regarding pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pfstools Version: 2.1.0-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic > CMakeFiles/pfsoutrgbe.dir/pfsoutrgbe.cpp.o > CMakeFiles/pfsoutrgbe.dir/rgbeio.cpp.o -o pfsoutrgbe > -L/<>/src/pfs > -Wl,-rpath,/<>/src/pfs:/<>/obj-x86_64-linux-gnu/src/pfs: > ../pfs/libpfs.so.2.0.0 > In file included from /<>/src/pfs/array2d.h:38, > from /<>/src/pfs/pfs.h:45, > from /<>/src/fileformat/pfsoutimgmagick.cpp:37: > /<>/src/pfs/array2d.h: In member function ‘virtual float& > pfs::Array2DImpl::operator()(int, int)’: > /<>/src/pfs/array2d.h:173:9: error: ‘__assert_fail’ was not > declared in this scope; did you mean ‘MagickCore::__assert_fail’? > 173 | assert( col >= 0 && col < cols ); > | ^~ > In file included from /usr/include/ImageMagick-6/magick/memory_.h:22, > from /usr/include/ImageMagick-6/magick/MagickCore.h:125, > from /usr/include/ImageMagick-6/Magick++/Include.h:45, > from /usr/include/ImageMagick-6/Magick++.h:10, > from /<>/src/fileformat/pfsoutimgmagick.cpp:32: > /usr/include/assert.h:69:13: note: ‘MagickCore::__assert_fail’ declared here >69 | extern void __assert_fail (const char *__assertion, const char > *__file, > | ^ > In file included from /<>/src/pfs/array2d.h:38, > from /<>/src/pfs/pfs.h:45, > from /<>/src/fileformat/pfsoutimgmagick.cpp:37: > /<>/src/pfs/array2d.h: In member function ‘virtual const float& > pfs::Array2DImpl::operator()(int, int) const’: > /<>/src/pfs/array2d.h:178:9: error: ‘__assert_fail’ was not > declared in this scope; did you mean ‘MagickCore::__assert_fail’? > 178 | assert( col >= 0 && col < cols ); > | ^~ > In file included from /usr/include/ImageMagick-6/magick/memory_.h:22, > from /usr/include/ImageMagick-6/magick/MagickCore.h:125, > from /usr/include/ImageMagick-6/Magick++/Include.h:45, > from /usr/include/ImageMagick-6/Magick++.h:10, > from /<>/src/fileformat/pfsoutimgmagick.cpp:32: > /usr/include/assert.h:69:13: note: ‘MagickCore::__assert_fail’ declared here >69 | extern void __assert_fail (const char *__assertion, const char > *__file, > | ^ > In file included from /<>/src/pfs/array2d.h:38, > from /<>/src/pfs/pfs.h:45, > from /<>/src/fileformat/pfsoutimgmagick.cpp:37: > /<>/src/pfs/array2d.h: In member function ‘virtual float& > pfs::Array2DImpl::operator()(int)’: > /<>/src/pfs/array2d.h:184:9: error: ‘__assert_fail’ was not > declared in this scope; did you mean ‘MagickCore::__assert_fail’? > 184 | assert( index >= 0 && index < rows*cols ); > | ^~ > In file included from /usr/include/ImageMagick-6/magick/memory_.h:22, > from /usr/include/ImageMagick-6/magick/MagickCore.h:125, > from /usr/include/ImageMagick-6/Magick++/Include.h:45, > from /usr/include/ImageMagick-6/Magick++.h:10, > from /<>/src/fileformat/pfsoutimgmagick.cpp:32: > /usr/include/assert.h:69:13: note: ‘MagickCore::__assert_fail’ declared here >69 | extern void __assert_fail (const char *__assertion, const char > *__file, > | ^ > In file included from /<>/src/pfs/array2d.h:38, > from /<>/src/pfs/pfs.h:45, > from /<>/src/fileformat/pfsoutimgmagick.cpp:37: > /<>/src/pfs/array2d.h: In member function ‘virtual const float& > pfs::Array2DImpl::operator()(int) const’: > /<>/src/pfs/array2d.h:188:9: error:
Processed: mark RC bugs
Processing commands for cont...@bugs.debian.org:
> severity 977611 serious
Bug #977611 {Done: Eduard Bloch } [apt-cacher-ng]
apt-cacher-ng: Daily cron job frequently hangs
Bug #980923 {Done: Eduard Bloch } [apt-cacher-ng] acngtools
eats all the CPU and doesn’t finish daily cron with merged pdiffs
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 983394 serious
Bug #983394 {Done: Eduard Bloch } [apt-cacher-ng]
apt-cacher-ng suddently stopped working
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
977611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977611
980923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980923
983394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986037: kdenlive: crashes on audio setup
Package: kdenlive Version: 20.12.3-1 Severity: grave Justification: renders package unusable Hi I am running kdenlive with the kde frameworks from experimental, but that shouldn't be a problem I thought. I see crashes/segfaults on every start of kdenlive. Backtrace is: (gdb) bt #0 0x7fff898862a0 in fftw_execute () from /usr/lib/x86_64-linux-gnu/libfftw3.so.3 #1 0x7fff894207f5 in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltplus.so #2 0x76d93b88 in mlt_frame_get_audio () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #3 0x76d722b8 in Mlt::Frame::get_audio(mlt_audio_format&, int&, int&, int&) () from /usr/lib/x86_64-linux-gnu/libmlt++.so.3 #4 0x558b8929 in ?? () #5 0x558b4aab in ?? () #6 0x556e25a5 in ?? () #7 0x752d6e72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x752d3b81 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x74382ea7 in start_thread (arg=) at pthread_create.c:477 #10 0x74e2cdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 and when I enter "c" into gdb to continue another segfault happens: (gdb) c Continuing. [Thread 0x7fff1a3fc700 (LWP 250120) exited] Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7102d8c0 (LWP 250071)] 0x703ba570 in QXcbConnection::getSelectionOwner(unsigned int) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 (gdb) bt #0 0x703ba570 in QXcbConnection::getSelectionOwner(unsigned int) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #1 0x703b4f88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #2 0x7715c998 in QQuickTextInput::q_canPasteChanged() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x771691e3 in QQuickTextInput::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x745bac76 in QQuickTextField::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #5 0x754eb290 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x75ed0935 in QClipboard::emitChanged(QClipboard::Mode) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x703b98a4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x703bacd6 in QXcbConnection::processXcbEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x703dd7d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x739bde6b in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x739be118 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x739be1cf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7550c4bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x754b392b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x754bbba0 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x556360d4 in ?? () #17 0x74d55d0a in __libc_start_main (main=0x55634c20, argc=1, argv=0x7fffd8a8, init=, fini=, rtld_fini=, stack_end=0x7fffd898) at ../csu/libc-start.c:308 #18 0x5563d6ba in _start () (gdb) and then a final continue (gdb) c Continuing. QSocketNotifier: Invalid socket 7 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... Invalid read from eventfd: Bad file descriptor Code should not be reached at pulsecore/fdsem.c:157, function flush(). Aborting. [Thread 0x7fffefee3700 (LWP 250075) exited] KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdenlive path = /usr/bin pid = 250071 KCrash: Arguments: /usr/bin/kdenlive KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Cannot find user-level thread for LWP 250102: generic error (gdb) Cannot find user-level thread for LWP 250098: generic error Not sure whether this is a pulseaudio, kdenlive, or one of the frameworks problems, though. Best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.10 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdenlive depends on: ii ffmpeg 7:4.3.2-0+deb11u1 ii gstreamer1.0-plugins-bad 1.18.3-1+b1 ii kded5
Bug#985281: [R-pkg-team] [RFS] r-cran-dt 0.17+dfsg-3
Upload permissions granted. Thanks a lot for your work on this, Andreas. On Sun, Mar 28, 2021 at 12:58:50PM +0200, Étienne Mollier wrote: > Control: tag -1 pending > > Étienne Mollier, on 2021-03-28 11:14:31 +0200: > > I think we are in agreement indeed. I check Salsa CI, and ready > > the package for upload (which will need sponsoring, or I will > > need dm grants). > > Said changes are pushed on Salsa. Since there does not seem to > be CI runners at t time, I manually ran the checks ; they all > pass except reprotest, which is expected apparently. I attached > a debdiff describing changes since 0.17+dfsg-2. > > Kind Regards, > -- > Étienne Mollier > Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da > Sent from /dev/pts/4, please excuse my verbosity. > diff -Nru r-cran-dt-0.17+dfsg/debian/changelog > r-cran-dt-0.17+dfsg/debian/changelog > --- r-cran-dt-0.17+dfsg/debian/changelog 2021-02-12 08:11:25.0 > +0100 > +++ r-cran-dt-0.17+dfsg/debian/changelog 2021-03-28 11:38:02.0 > +0200 > @@ -1,3 +1,20 @@ > +r-cran-dt (0.17+dfsg-3) unstable; urgency=medium > + > + * Team upload > + > + [ Andreas Tille ] > + * Fix unhandled symlink to directory conversion > + * Allow failure in salsa-ci reprotest > + > + [ Nilesh Patra ] > + * Defer linking to d/links > + > + [ Étienne Mollier ] > + * adjust d/maintscript to fix upgrade from Buster > +Closes: #985281 > + > + -- Étienne Mollier Sun, 28 Mar 2021 11:38:02 > +0200 > + > r-cran-dt (0.17+dfsg-2) unstable; urgency=medium > >* No test via vignette needed any more since there is a real test suite > diff -Nru r-cran-dt-0.17+dfsg/debian/links r-cran-dt-0.17+dfsg/debian/links > --- r-cran-dt-0.17+dfsg/debian/links 2021-02-12 08:11:25.0 +0100 > +++ r-cran-dt-0.17+dfsg/debian/links 2021-03-28 11:10:13.0 +0200 > @@ -10,5 +10,44 @@ > usr/share/javascript/jquery-datatables-extensions/pdfmake/build/vfs_fonts.js > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/vfs_fonts.js > usr/share/javascript/jquery-datatables-extensions/Buttons/css > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/css > usr/share/javascript/jquery-datatables-extensions/Buttons/swf > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/swf > +usr/share/javascript/jquery-datatables-extensions/Scroller > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Scroller > +usr/share/javascript/jquery-datatables-extensions/FixedColumns > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/FixedColumns > +usr/share/javascript/jquery-datatables-extensions/ColReorder > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/ColReorder > +usr/share/javascript/jquery-datatables-extensions/Select > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Select > +usr/share/javascript/jquery-datatables-extensions/Responsive > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Responsive > +usr/share/javascript/jquery-datatables-extensions/RowReorder > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/RowReorder > +usr/share/javascript/jquery-datatables-extensions/KeyTable > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/KeyTable > +usr/share/javascript/jquery-datatables-extensions/FixedHeader > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/FixedHeader > +usr/share/javascript/jquery-datatables-extensions/AutoFill > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/AutoFill > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.js > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.min.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.min.js > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.js > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.min.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.min.js > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.foundation.js > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.min.js > > usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.foundation.min.js >
Bug#986033: avahi: Failure to upgrade to Debian 10.9 on amd64+i386, 0.7-4+b1 => 0.7-4+deb10u1
Source: avahi Version: 0.7-4+deb10u1 Severity: serious Justification: Policy 7.3 Hi, with 10.9 released, I am unable to upgrade avahi on a dual architecture system with both amd64 and i386 packages. Because I couldn't see the +b1 version on tracker, here's the snapshot proof: https://snapshot.debian.org/package/avahi/0.7-4/#libavahi-common3_0.7-4:2b:b1 :~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libavahi-client3 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-client3:i386 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common-data (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common-data:i386 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common3 (0.7-4+b1 => 0.7-4+deb10u1) libavahi-common3:i386 (0.7-4+b1 => 0.7-4+deb10u1) 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. :~ $ sudo apt upgrade libavahi-client3 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libavahi-client3 : Breaks: libavahi-client3:i386 (!= 0.7-4+deb10u1) but 0.7-4+b1 is to be installed libavahi-client3:i386 : Breaks: libavahi-client3 (!= 0.7-4+b1) but 0.7-4+deb10u1 is to be installed E: Broken packages -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), (100, 'buster-fasttrack'), (100, 'buster-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#962921: Please fix spam for bullseye
Hi Tiago, apticron is scheduled for automatic removal on 04/12 and the fixed package will not migrate because you included an arch-all binary in your upload. Please upload a source-only version. Thanks.
Processed: Re: [R-pkg-team] [RFS] r-cran-dt 0.17+dfsg-3
Processing control commands: > tag -1 pending Bug #985281 [r-cran-dt] r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions Added tag(s) pending. -- 985281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985281: [R-pkg-team] [RFS] r-cran-dt 0.17+dfsg-3
Control: tag -1 pending Étienne Mollier, on 2021-03-28 11:14:31 +0200: > I think we are in agreement indeed. I check Salsa CI, and ready > the package for upload (which will need sponsoring, or I will > need dm grants). Said changes are pushed on Salsa. Since there does not seem to be CI runners at t time, I manually ran the checks ; they all pass except reprotest, which is expected apparently. I attached a debdiff describing changes since 0.17+dfsg-2. Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/4, please excuse my verbosity. diff -Nru r-cran-dt-0.17+dfsg/debian/changelog r-cran-dt-0.17+dfsg/debian/changelog --- r-cran-dt-0.17+dfsg/debian/changelog 2021-02-12 08:11:25.0 +0100 +++ r-cran-dt-0.17+dfsg/debian/changelog 2021-03-28 11:38:02.0 +0200 @@ -1,3 +1,20 @@ +r-cran-dt (0.17+dfsg-3) unstable; urgency=medium + + * Team upload + + [ Andreas Tille ] + * Fix unhandled symlink to directory conversion + * Allow failure in salsa-ci reprotest + + [ Nilesh Patra ] + * Defer linking to d/links + + [ Étienne Mollier ] + * adjust d/maintscript to fix upgrade from Buster +Closes: #985281 + + -- Étienne Mollier Sun, 28 Mar 2021 11:38:02 +0200 + r-cran-dt (0.17+dfsg-2) unstable; urgency=medium * No test via vignette needed any more since there is a real test suite diff -Nru r-cran-dt-0.17+dfsg/debian/links r-cran-dt-0.17+dfsg/debian/links --- r-cran-dt-0.17+dfsg/debian/links 2021-02-12 08:11:25.0 +0100 +++ r-cran-dt-0.17+dfsg/debian/links 2021-03-28 11:10:13.0 +0200 @@ -10,5 +10,44 @@ usr/share/javascript/jquery-datatables-extensions/pdfmake/build/vfs_fonts.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/vfs_fonts.js usr/share/javascript/jquery-datatables-extensions/Buttons/css usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/css usr/share/javascript/jquery-datatables-extensions/Buttons/swf usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/swf +usr/share/javascript/jquery-datatables-extensions/Scroller usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Scroller +usr/share/javascript/jquery-datatables-extensions/FixedColumns usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/FixedColumns +usr/share/javascript/jquery-datatables-extensions/ColReorder usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/ColReorder +usr/share/javascript/jquery-datatables-extensions/Selectusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Select +usr/share/javascript/jquery-datatables-extensions/Responsiveusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Responsive +usr/share/javascript/jquery-datatables-extensions/RowReorderusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/RowReorder +usr/share/javascript/jquery-datatables-extensions/KeyTable usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/KeyTable +usr/share/javascript/jquery-datatables-extensions/FixedHeader usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/FixedHeader +usr/share/javascript/jquery-datatables-extensions/AutoFill usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/AutoFill +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.min.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.min.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.jsusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.min.jsusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.min.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.jsusr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.foundation.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.min.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.foundation.min.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.html5.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.html5.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.html5.min.js usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.html5.min.js +usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.jqueryui.js
Bug#985033: marked as done (debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license)
Your message dated Sun, 28 Mar 2021 10:03:21 + with message-id and subject line Bug#985033: fixed in coderay 1.1.3-4 has caused the Debian Bug report #985033, regarding debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coderay Version: 1.1.3-3 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It seem the coderay sources are now licensed under the MIT license and not under the LGPL license. debian/copyright seems to be outdated and wrong here. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmBKthsACgkQS80FZ8KW 0F387w//ezc1er6Hv8c7swmmwgK8XfokzAcxFbktXyIsUOwN+s2fKlFwjinFkArU PP8lOe7qzB2vB5eol19vofYdDzJoOqo/RCzsS+Q8Rm3gUzcyTF2pIeubzlNqZMf2 KMYaERHnfrGlLklcOzt+x8JfRvmxS2MAFHNLBuws0k9yISdWfW36DeCFiz0Miqik VrPAaWMRFUzaqnH3lXEoi342OomkDq2wmx7YnqRd4ESHTWdpAY5b9dC8r6tCnynj zcspt/0uPnXBKKPuBKXsucBoLr80te+x/7DZ/iLILAbIdEZ+o1jzCu3pCRXQUFdK vNOnwaBVhDl9aciXTrj1ocbNS1shximlu6vJMaMTB5MXVNt5ph691jazr6bYXjn2 MZU8EK5fkPnYIkX3DOGGZMjuQ5wMN55Z3Udgf+pUE9oXDprc+0vxuLmq6UtLrHKy uQm/WOd3Fj+r71s5zaRqlf7gShQU2oV23/4PLWC84nswoGkZTnk9yj5X4tw+HdfS 82+iOGayRny2a+EkglGT4IvOvXSdPnXnucjronzpf6s5kw/JP9BRyyF85AWM87q2 6zjycLQo+j3xh3CV4jgNC9pRC6yUTj5YsxnYPIM7v0YWgQBwEzAz6JLBMU/2zEvO JRHm+XskHA+U6PsV4ccyA4m7zEKPsV10xRrqrZhQekf96BvaQ8Y= =GfoC -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: coderay Source-Version: 1.1.3-4 Done: HIGUCHI Daisuke (VDR dai) We believe that the bug you reported is fixed in the latest version of coderay, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated coderay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 28 Mar 2021 18:11:55 +0900 Source: coderay Architecture: source Version: 1.1.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: HIGUCHI Daisuke (VDR dai) Closes: 985033 Changes: coderay (1.1.3-4) unstable; urgency=medium . [ Vivek K J ] * Update Licence with modified upstream licence (Closes: #985033) . [ HIGUCHI Daisuke (VDR dai) ] * d/copyright: fix Expat license. Checksums-Sha1: fd557ad0134fcb95abf99e9f770d2b1479066acd 2271 coderay_1.1.3-4.dsc 8e67c10b9595f9b37c671929677ad17aaf295cf1 7776 coderay_1.1.3-4.debian.tar.xz Checksums-Sha256: c51abcc06c3b1d6790bc5c64dd6bdd9f67f0491c0c6ec2b55dbad3e8eaa43229 2271 coderay_1.1.3-4.dsc 6f3bd14054f7b54b64e0aa1251adc347f017f2ac9cbb36500f3caf2e8105b0d4 7776 coderay_1.1.3-4.debian.tar.xz Files: be5ece313acff842216a04cb61d8bd35 2271 ruby optional coderay_1.1.3-4.dsc 920acf4d9df0376bc53f2d70305e0e28 7776 ruby optional coderay_1.1.3-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmBgTu4ACgkQeDlhndQ5 Zo5j0Q/+LtQ0xpuDCOH3ij0VSjE2sov4QE7nDEXOE2MbRnkeAOtCrE4dJ9FJMccr pAInybXhS33moVWLaCe9WceZVNP0c7LLROyeoCxBz9BNKyZT8zeytkxzB8AMVznM ehOspF8wt+Hv0uXOLQsT7UiSzxesxKNWvCM8u0zimonnULqlmAa3z9sePp68ZZSF +hBi+0tBlGH4rEsKXToZkGaiDnuyFn4uz+9qTPPjFpPbPJXg4ZRbkp4amVzF8+o2 jdAlSTimyjblvK9AO0W79k93V71MNQJNFD/Vh3N0DOQMzxMa+zDvnIbGPCCSDMLH 2KqYDSU7wXdHkeYRxbCVoKQV5fZah8vv2ENO0XSbxcj7TJnKQ/tcr4dzRzCz+542 o794cYsjvrTFKHo1fYMQLoUtcno5bHEOczkxHDvxJHCR0uXbewpy8W8PGIRS/UE1 5RYRD0TER+U7V+Zpc/jEx13NP9zZ2F9KsDtso6Rj2qqemYlb8+J1Em1ClUWVNUSQ
Bug#982332: Status regarding Dahdi RC bugs?
Hi Tzafrir, I want to fall into line with Bernhard. Are you already working on the three RC bugs filed against dahdi-* (Bug#982332, Bug#982334, Bug#982389)? Besides Asterisk also the Osmocore software stack is affected and marked for autoremoval. Thorsten
Bug#985281: r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions
Hi Andreas, Andreas Tille, on 2021-03-28 09:20:23 +0200: > On Sat, Mar 27, 2021 at 10:43:10PM +0100, Étienne Mollier wrote: > > Several packages from libjs-jquery-datatables-extension and > > libjs-jquery-datatables go missing after purge, eventually > > requiring the user of the rolling Sid machine to reinstall these > > packages, if removal of r-cran-dt occurs. Normally, with the > > new d/maintscript, this should not occur when jumping directly > > from Buster. How much is it a concern regarding the criticality > > of the bug? > > If I understood you correctly than your fix is fixing the reported bug and > will be fit for bullseye. I think we are in agreement indeed. I check Salsa CI, and ready the package for upload (which will need sponsoring, or I will need dm grants). Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/4, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Bug#985033 marked as pending in coderay
Processing control commands: > tag -1 pending Bug #985033 [src:coderay] debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license Ignoring request to alter tags of bug #985033 to the same tags previously set -- 985033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985033: marked as pending in coderay
Control: tag -1 pending Hello, Bug #985033 in coderay reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/coderay/-/commit/a984fb07fb2e335da1dc6aca114d918014400350 Merge branch 'master' into 'master' Update licence with upstream (Closes: #985033) See merge request ruby-team/coderay!1 (this message was generated automatically) -- Greetings https://bugs.debian.org/985033
Processed: Bug#985033 marked as pending in coderay
Processing control commands: > tag -1 pending Bug #985033 [src:coderay] debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license Added tag(s) pending. -- 985033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985033: marked as pending in coderay
Control: tag -1 pending Hello, Bug #985033 in coderay reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/coderay/-/commit/7bbde7d4da3f2ddc5834bc98fa38a971997821f6 Update licence with upstream (Closes: #985033) (this message was generated automatically) -- Greetings https://bugs.debian.org/985033
Processed: Re: dnsmasq: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing control commands: > tags -1 + patch pending Bug #985282 [dnsmasq] dnsmasq: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) pending and patch. -- 985282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985282: dnsmasq: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Control: tags -1 + patch pending Dear Maintainer, On Mon, 15 Mar 2021 13:19:07 +0100 Andreas Beckmann wrote: > Package: dnsmasq > Version: 2.84-1 > Severity: serious > User: debian...@lists.debian.org > an upgrade test with piuparts revealed that your package installs files > over existing symlinks and possibly overwrites files owned by other > packages. This usually means an old version of the package shipped a > symlink but that was later replaced by a real (and non-empty) > directory. This kind of overwriting another package's files cannot be > detected by dpkg. > > This was observed on the following upgrade paths: > > buster -> bullseye I have prepared an NMU fixing this bug, versioned 2.84-1.1, and uploaded it to DELAYED/2. Please tell me if I should delay it longer. The debdiff is attached. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org diff -u dnsmasq-2.84/debian/changelog dnsmasq-2.84/debian/changelog --- dnsmasq-2.84/debian/changelog +++ dnsmasq-2.84/debian/changelog @@ -1,3 +1,13 @@ +dnsmasq (2.84-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix symlink to directory conversion for /usr/share/doc/dnsmasq. +This is achieved by directly calling dpkg-maintscript-helper in the preinst, +postinst, and postrm scripts, since the package does not use debhelper. +(Closes: #985282) + + -- Sébastien Villemot Sun, 28 Mar 2021 10:55:07 +0200 + dnsmasq (2.84-1) unstable; urgency=low * New upstream. diff -u dnsmasq-2.84/debian/postinst dnsmasq-2.84/debian/postinst --- dnsmasq-2.84/debian/postinst +++ dnsmasq-2.84/debian/postinst @@ -1,6 +1,9 @@ #!/bin/sh set -e +# /usr/share/doc/dnsmasq was a symlink in versions < 2.81-1 (see #985282) +dpkg-maintscript-helper symlink_to_dir /usr/share/doc/dnsmasq dnsmasq-base 2.81-1~ dnsmasq -- "$@" + # Code copied from dh_systemd_enable -- # This will only remove masks created by d-s-h on package removal. deb-systemd-helper unmask dnsmasq.service >/dev/null || true diff -u dnsmasq-2.84/debian/postrm dnsmasq-2.84/debian/postrm --- dnsmasq-2.84/debian/postrm +++ dnsmasq-2.84/debian/postrm @@ -1,6 +1,9 @@ #!/bin/sh set -e +# /usr/share/doc/dnsmasq was a symlink in versions < 2.81-1 (see #985282) +dpkg-maintscript-helper symlink_to_dir /usr/share/doc/dnsmasq dnsmasq-base 2.81-1~ dnsmasq -- "$@" + if [ purge = "$1" ]; then update-rc.d dnsmasq remove >/dev/null fi diff -u dnsmasq-2.84/debian/rules dnsmasq-2.84/debian/rules --- dnsmasq-2.84/debian/rules +++ dnsmasq-2.84/debian/rules @@ -176,7 +176,7 @@ -d debian/trees/daemon/usr/lib/tmpfiles.d \ -d debian/trees/daemon/etc/insserv.conf.d install -m 644 debian/conffiles debian/trees/daemon/DEBIAN - install -m 755 debian/postinst debian/postrm debian/prerm debian/trees/daemon/DEBIAN + install -m 755 debian/postinst debian/postrm debian/preinst debian/prerm debian/trees/daemon/DEBIAN if ! dpkg-vendor --derives-from Ubuntu; then \ rm -f debian/dnsmasq.postinst.debhelper debian/dnsmasq.postrm.debhelper; \ dh_runit -pdnsmasq -Pdebian/trees/daemon; \ only in patch2: unchanged: --- dnsmasq-2.84.orig/debian/preinst +++ dnsmasq-2.84/debian/preinst @@ -0,0 +1,5 @@ +#!/bin/sh +set -e + +# /usr/share/doc/dnsmasq was a symlink in versions < 2.81-1 (see #985282) +dpkg-maintscript-helper symlink_to_dir /usr/share/doc/dnsmasq dnsmasq-base 2.81-1~ dnsmasq -- "$@" signature.asc Description: This is a digitally signed message part
Bug#985281: r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions
Hi Étienne, thanks a lot for working on this. On Sat, Mar 27, 2021 at 10:43:10PM +0100, Étienne Mollier wrote: > Hi, > > I pushed a change on Salsa[1] to make sure that the two > following piuparts upgrade paths are working okay (thanks > Andreas Tille for the permission): > > $ sudo piuparts \ > --testdebs-repo='deb [trusted=true] > http://[::1]/~emollier/repos experimental main' \ > --distupgrade-to-testdebs \ > --warn-on-leftovers-after-purge \ > --distribution=buster \ > --distribution=bullseye \ > --apt r-cran-dt=0.17+dfsg-3 > > $ sudo piuparts \ > --testdebs-repo='deb [trusted=true] > http://[::1]/~emollier/repos experimental main' \ > --distupgrade-to-testdebs \ > --warn-on-leftovers-after-purge \ > --distribution=bullseye \ > --apt r-cran-dt=0.17+dfsg-3 > > The first describes installation from Buster, then upgrade to > Bullseye, then purge. The second describes installation of > initial Testing version, then purge. > > There is however this upgrade path that I struggle to fix, note > the missing --distupgrade-to-testdebs, which goes through the > existing 0.17+dfsg-2 in Testing, and which is still broken: > > $ sudo piuparts \ > --testdebs-repo='deb [trusted=true] > http://[::1]/~emollier/repos experimental main' \ > --warn-on-leftovers-after-purge \ > --distribution=buster \ > --distribution=bullseye \ > --apt r-cran-dt=0.17+dfsg-3 > [...] > 1m39.9s DEBUG: Command failed (status=2), but ignoring error: > ['debsums', '--root', '/tmp/tmp0pvmpul0', '-ac', '--ignore-obsolete'] > 1m39.9s ERROR: FAIL: debsums reports modifications inside the chroot: > debsums: missing file > /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap.css (from > libjs-jquery-datatables package) > debsums: missing file > /usr/share/javascript/jquery-datatables/css/dataTables.bootstrap.min.css > (from libjs-jquery-datatables package) > [...] > debsums: missing file > /usr/share/javascript/jquery-datatables-extensions/Buttons/js/dataTables.buttons.js > (from libjs-jquery-datatables-extensions package) > debsums: missing file > /usr/share/javascript/jquery-datatables-extensions/Buttons/js/dataTables.buttons.min.js > (from libjs-jquery-datatables-extensions package) I wonder whether the goal you want to approach is feasible. The bug was filed since 0.17+dfsg-2 is buggy. The attempt to get the sequence you tried will fail due to this. The goal is to get this version out of the upgrading process. > Several packages from libjs-jquery-datatables-extension and > libjs-jquery-datatables go missing after purge, eventually > requiring the user of the rolling Sid machine to reinstall these > packages, if removal of r-cran-dt occurs. Normally, with the > new d/maintscript, this should not occur when jumping directly > from Buster. How much is it a concern regarding the criticality > of the bug? If I understood you correctly than your fix is fixing the reported bug and will be fit for bullseye. Kind regards Andreas. > [1] https://salsa.debian.org/r-pkg-team/r-cran-dt/ -- http://fam-tille.de
