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
Bug#986028: can not remove lvm partitions
Package: calamares-settings-debian Version: 10.0.20-1+deb10u4 Dear Maintainer, When i trying to test Debian 10.9 live cd installation, an error occurred. I can not remove my old lvm partition because lvm2 package is not installed by default. -- Best Regards, peylight
Bug#986029: fuse-umfuse-fat: newer upstream version available?
Source: fuse-umfuse-fat Version: 0.1a-1.2 Severity: wishlist Dear Maintainer, I was looking at some issues with fusefat and noticed that the upstream wiki page [1] links to github repository [2]. Is this a new upstream release? One thing that confuses me is that history file [3] seems to suggest that the release would have been 0.06 by June 2008, so not sure if this was the project that was packaged in Debian. [1] http://wiki.virtualsquare.org/#!repos.md [2] https://github.com/virtualsquare/fusefatfs [3] https://github.com/virtualsquare/fusefatfs/blob/master/fatfs/source/00history.txt -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#984967: removing handbrake from deb-multimedia and deb-multimedia-repository
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ssh andrew@bulls-eye
> Linux bulls-eye 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
> individual files in /usr/share/doc/*/copyright.
>
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> Last login: Sun Mar 28 08:50:04 2021 from 192.168.0.58
> andrew@bulls-eye:~$ sudo su
> [sudo] password for andrew:
> root@bulls-eye:/home/andrew# au2
> bash: au2: command not found
> root@bulls-eye:/home/andrew# aptiude update && aptitude upgrade
> bash: aptiude: command not found
> root@bulls-eye:/home/andrew# aptitude update && aptitude upgrade
> Get: 1 http://security.debian.org/debian-security bullseye-security
> InRelease [44.1 kB] Get: 2 http://deb.debian.org/debian bullseye InRelease
> [142 kB] Hit http://packages.x2go.org/debian bullseye
> InRelease Get: 3 https://www.deb-multimedia.org bullseye InRelease [15.7
> kB] Get: 4 http://deb.debian.org/debian bullseye/main amd64
> Packages.diff/Index [63.6 kB] Get: 5 http://deb.debian.org/debian
> bullseye/main Translation-en.diff/Index [63.6 kB] Get: 6
> https://www.deb-multimedia.org bullseye/main amd64 Packages [124 kB] Get: 7
> http://deb.debian.org/debian bullseye/non-free amd64 Packages.diff/Index
> [63.3 kB] Get: 8 http://deb.debian.org/debian bullseye/non-free
> Translation-en.diff/Index [52.1 kB] Get: 9 http://deb.debian.org/debian
> bullseye/main amd64 Packages
> T-2021-03-28-0201.00-F-2021-03-23-0200.59.pdiff [70.3 kB] Get: 10
> http://deb.debian.org/debian bullseye/main Translation-en
> T-2021-03-27-0201.07-F-2021-03-23-0200.59.pdiff [3,366 B] Get: 11
> http://deb.debian.org/debian bullseye/main amd64 Packages
> T-2021-03-28-0201.00-F-2021-03-23-0200.59.pdiff [70.3 kB] Get: 12
> http://deb.debian.org/debian bullseye/main Translation-en
> T-2021-03-27-0201.07-F-2021-03-23-0200.59.pdiff [3,366 B] Get: 13
> http://deb.debian.org/debian bullseye/non-free amd64 Packages
> T-2021-03-23-0200.59-F-2021-03-23-0200.59.pdiff [444 B] Get: 14
> http://deb.debian.org/debian bullseye/non-free amd64 Packages
> T-2021-03-23-0200.59-F-2021-03-23-0200.59.pdiff [444 B] Get: 15
> http://deb.debian.org/debian bullseye/non-free Translation-en
> T-2021-03-23-0200.59-F-2021-03-23-0200.59.pdiff [223 B] Get: 16
> http://deb.debian.org/debian bullseye/non-free Translation-en
> T-2021-03-23-0200.59-F-2021-03-23-0200.59.pdiff [223 B] Get: 17
> http://deb.debian.org/debian bullseye/main amd64 DEP-11 Metadata [4,017 kB]
> Get: 18 http://deb.debian.org/debian bullseye/main DEP-11 48x48 Icons
> [3,483 kB] Get: 19 http://deb.debian.org/debian bullseye/main DEP-11 64x64
> Icons [7,313 kB] Get: 20 http://deb.debian.org/debian bullseye/main DEP-11
> 128x128 Icons [11.5 MB] Get: 21 http://deb.debian.org/debian
> bullseye/non-free amd64 DEP-11 Metadata [11.7 kB] Fetched 26.9 MB in 8s
> (3,339 kB/s) Current status: 48 (+48) upgradable, 422 (+3) new. There is 1
> newly obsolete package: linux-image-5.10.0-4-amd64 Resolving
> dependencies... The following NEW packages will be installed:
> fonts-liberation{a} graphviz{a} libann0{a} libcdt5{a} libcgraph6{a}
> libgts-0.7-5{a} libgts-bin{a} libgvc6{a} libgvpr2{a} liblab-gamut1{a}
> libpathplan4{a} linux-image-5.10.0-5-amd64{a} The following packages will
> be upgraded: bind9-dnsutils bind9-host bind9-libs firefox-esr gimp
> gimp-data libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6-dev
> libcaca0 libcpupower1 libgimp2.0 libgnutls30 libjavascriptcoregtk-4.0-18
> liblirc-client0 libmediainfo0v5 libpam-modules libpam-modules-bin
> libpam-runtime libpam0g libplymouth5 libqt5qml5 libqt5qmlmodels5
> libqt5qmlworkerscript5 libqt5quick5 libqt5quickparticles5
> libqt5quickwidgets5 libsvthevcenc1 libwebkit2gtk-4.0-37 linux-config-5.10
> linux-image-amd64 linux-libc-dev linux-source linux-source-5.10 locales
> plymouth plymouth-label qml-module-qt-labs-folderlistmodel
> qml-module-qt-labs-settings qml-module-qtqml qml-module-qtqml-models2
> qml-module-qtquick-layouts qml-module-qtquick-particles2
> qml-module-qtquick-window2 qml-module-qtquick2 The following packages are
> RECOMMENDED but will NOT be installed: libnss-nis libnss-nisplus 48
> packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need
> to get 304 MB of archives. After unpacking 314 MB will be used. Do you want
> to continue? [Y/n/?] Get: 1 http://deb.debian.org/debian bullseye/main
> amd64 libc-devtools amd64 2.31-10 [244 kB] Get: 2
> https://www.deb-multimedia.org bullseye/main amd64 libsvthevcenc1 amd64
> 1.5.0-dmo2 [484 kB] Get: 3 http://deb.debian.org/debian bullseye/main amd64
> libc6-dev amd64 2.31-10 [2,344 kB] Get: 4 http://deb.debian.org/debian
> bullseye/main amd64 libc-dev-bin amd64 2.31-10 [274 kB] Get: 5
> http://deb.debian.org/debian bullseye/main amd64 linux-libc-dev amd64
> 5.10.24-1 [1
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 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
Bug#986030: manpages.debian.org: Content does no match shipped (deb) version: testing/manpages-de/journalctl.1.de.html
Package: manpages.debian.org Severity: normal 1. Use a current testing system, install manpages-de, change locale (if necessary) and issue man journalctl and search for "-S, --since=, -U, --until=" Here the text starts with: Fängt die Anzeige mit neueren Einträgen ab dem angegebenen Datum oder älteren … 2. Navigate to https://manpages.debian.org/testing/manpages-de/journalctl.1.de.html and search for "-S, --since=, -U, --until=" Here the text starts with: Die Anzeige mit neueren Einträgen ab dem angegebenen Datum oder älteren … Clearly both versions do not match. If I review the upstream git log, I see: 407f2a66e3f po/de/man1/journalctl.1.po (Helge Kreutzmann 2021-01-06 19:10:56 +0100 1285) "Fängt die Anzeige mit neueren Einträgen ab dem angegebenen Datum oder " 407f2a66e3f po/de/man1/journalctl.1.po (Helge Kreutzmann 2021-01-06 19:10:56 +0100 1286) "älteren Einträgen bis zum angegebenen Datum an. Datumsangaben sollten vom " With the appropriate git diff command: -"Die Anzeige mit neueren Einträgen ab dem angegebenen Datum oder älteren " -"Einträgen bis zum angegebenen Datum anfangen. 18:17:16« sein\\&. Falls der " … +"Fängt die Anzeige mit neueren Einträgen ab dem angegebenen Datum oder " +"älteren Einträgen bis zum angegebenen Datum an. Datumsangaben sollten vom " So this text is in Unstable since version 4.9.1-1 (February 7th) and Testing since March 2nd. So my assumption is that the update mechanism of manpages.debian.org does not work correctly. Greetings Helge -- 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#977939: Acknowledgement (linux-base: [INTL:de] updated German man page translation)
Hello Ben, hello Kernel team, We are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). This would be highly appreciated by German speaking users. Thanks! Greetings Helge -- 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#980183: Acknowledgement (sensible-utils: [INTL:de] updated German man page translation)
Hello Bastien, On Sun, Jan 31, 2021 at 07:28:47AM +0100, Helge Kreutzmann wrote: > Hello Anibal, > hello Bastien, > could you include the updated translation in time before the freeze, > so that Bullseye contains it? > > Thank you very much! We are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). This would be highly appreciated by German speaking users. Thanks! Greetings Helge -- 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#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#982628: Acknowledgement (virtuoso-opensource: [INTL:de] updated German debconf translation)
Hello Will, hello Andreas, hello Debian Science Maintainers, we are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). This would be highly appreciated by German speaking users. (The Debconf changes appeared rather late in the development cycle therefor my update could not be provided earlier) Thanks! Greetings Helge -- 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#982629: Acknowledgement (prometheus-smokeping-prober: [INTL:de] initial German debconf translation)
Hello Daniel, hello Debian Go Packaging Team, we are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). This would be highly appreciated by German speaking users. (The Debconf changes appeared rather late in the development cycle therefor my update could not be provided earlier) Thanks! Greetings Helge -- 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#978025: Sound issues with the 5.10.x kernel (alsa)
Hi, Am 28.03.21 um 07:58 schrieb Ryutaroh Matsumoto: >> I think the root cause of this issue is that both vc4.ko and snd_bcm2835.ko >> try to provide ALSA sinks to HDMI audio outputs from RPi. >> Why do the two drivers provide the same functionality for the same device? >> It seems nonsense. >> There must be some coordination between vc4.ko and snd_bcm2835.ko >> on who provides ALSA sinks of RPi HDMI output. > Giving "enable_hdmi=0" to snd_bcm2835.ko does not improve the situation, > while module_blacklisting snd_bcm2835 suppresses all the symptoms reported. > snd_bcm2835.ko in 5.10.24 seems having a bug ignoring "enable_hdmi=0". i assume you set this option in the config.txt? This shouldn't have any affect for the mainline kernel / DT. > > Best regards, Ryutaroh
Bug#980877: marked as pending in rocksndiamonds
Hello Stephen, On Sun, Jan 24, 2021 at 05:39:53PM +, Stephen Kitt wrote: > Control: tag -1 pending > > Hello, > > Bug #980877 in rocksndiamonds 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/games-team/rocksndiamonds/-/commit/cedfe366646afa14b27882b7d59c1e28dd3c314c > > > Updated German debconf template translation > > Closes: #980877 > We are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). would be highly appreciated by German speaking users. (The Debconf changes appeared rather late in the development cycle therefor my update could not be provided earlier) Thanks! Greetings Helge -- 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#977678: Acknowledgement (adduser: [INTL:de] updated German man page translation)
Hello Marc, We are now quite in the freeze. Is there any chance this still gets in Bullseye? (debian-release might still allow a targetted fix). This would be highly appreciated by German speaking users. Thanks! Greetings Helge -- 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#651783: libpcap0.8: libpcap should be linked with libnl
Hi Steev, While the libnl landscape indeed seems to have simplified since the last time I took a look at it, I don't think we are in a good place right now. The last upload of libnl3 was in 2018. The packaging Git repository has disappeared. Upstream-wise, there's a 3.5.0 release on GitHub (picked up by Fedora), but it's not listed on the project homepage... Not very encouraging. There's also a known issue with the integration related to tcpdump which now drops privileges by default and cannot delete the mon interface it creates, leaking interfaces at each invocation. So I won't be enabling this. I'm still of the opinion that libpcap should do the work by itself and not require libnl. Thanks.
Bug#985969: libvirt: Build with libssh
The original reason for the bug is fixed now. But please consider building with libssh (maybe additionally to libssh2 because libvirt does not support other host keys with libssh2 than RSA and DSA. When a host offers a different key algorithm it will error with "unsupported SSH key type".
Bug#986029: [Virtualsquare] Bug#986029: fuse-umfuse-fat: newer upstream version available?
Hi Junichi, Virtualsquare's FAT module for fuse (compatible with umfuse and vufuse) has been rewritten. [1] is the new source code based on the FAT file system module for embedded systems fatfs by ChaN. The virtualsquare team is working to package this new implementation as a Debian package as soon as possible. It is in the queue, maybe we'll work on it just after bullseye's release. ChaN's module is mode stable and complete than our former libfat. The source code of the current fuse-umfuse-fat package can be found here (it is a subdir of the view-os source tree): [2] [3] [1] https://github.com/virtualsquare/fusefatfs [2] https://github.com/virtualsquare/view-os/tree/master/fuse-modules/fat [3] https://sourceforge.net/projects/view-os/ * wishes, renzo On Sun, Mar 28, 2021 at 05:07:59PM +0900, Junichi Uekawa wrote: > Source: fuse-umfuse-fat > Version: 0.1a-1.2 > Severity: wishlist > > Dear Maintainer, > > I was looking at some issues with fusefat and noticed that the > upstream wiki page [1] links to github repository [2]. Is this a new > upstream release? > > One thing that confuses me is that history file [3] seems to suggest > that the release would have been 0.06 by June 2008, so not sure if > this was the project that was packaged in Debian. > > [1] http://wiki.virtualsquare.org/#!repos.md > [2] https://github.com/virtualsquare/fusefatfs > [3] > https://github.com/virtualsquare/fusefatfs/blob/master/fatfs/source/00history.txt > > -- System Information: > Debian Release: 10.8 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set > to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to > ja_JP.UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system)
Bug#986031: ogmrip crashes on startup with "malloc(): unsorted double linked list corrupted"
Package: ogmrip
Version: 1.0.1-3
Severity: normal
Dear Maintainer,
The "ogmrip" command fails to start after installation. I installed the
package and typed the "ogmrip" command with no arguments.
When called from the command line, it exits with:
A large number of these:
** (ogmrip:7501): CRITICAL **: 12:28:41.392: ogmrip_settings_install_key:
assertion 'G_IS_PARAM_SPEC (pspec)' failed
(ogmrip:7501): GLib-GObject-CRITICAL **: 12:28:41.392:
g_param_spec_internal: assertion 'g_param_spec_is_valid_name (name)' failed
** (ogmrip:7501): CRITICAL **: 12:28:41.392: ogmrip_settings_install_key:
assertion 'G_IS_PARAM_SPEC (pspec)' failed
(ogmrip:7501): GLib-GObject-CRITICAL **: 12:28:41.392:
g_param_spec_internal: assertion 'g_param_spec_is_valid_name (name)' failed
** (ogmrip:7501): CRITICAL **: 12:28:41.392: ogmrip_settings_install_key:
assertion 'G_IS_PARAM_SPEC (pspec)' failed
And then finally:
MP4Box - GPAC version 1.0.1-rev1.0.1+dfsg1-3
(c) 2000-2020 Telecom Paris distributed under LGPL v2.1+ - http://gpac.io
Please cite our work in your research:
GPAC Filters: https://doi.org/10.1145/3339825.3394929
GPAC: https://doi.org/10.1145/1291233.1291452
GPAC Configuration: --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 --prefix=/usr
--libdir=lib/x86_64-linux-gnu --mandir=${prefix}/share/man --extra-cflags=-Wall
-fPIC -DPIC -I/usr/include/mozjs -DXP_UNIX -Wdate-time -D_FORTIFY_SOURCE=2 -g
-O2 -fdebug-prefix-map=/build/gpac-H8Ov47/gpac-1.0.1+dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security
--extra-ldflags=-Wl,-z,relro --enable-joystick --enable-debug --disable-ssl
--verbose
Features: GPAC_CONFIG_LINUX GPAC_64_BITS GPAC_HAS_IPV6 GPAC_HAS_SOCK_UN
GPAC_MINIMAL_ODF GPAC_HAS_QJS GPAC_HAS_FAAD GPAC_HAS_MAD GPAC_HAS_LIBA52
GPAC_HAS_JPEG GPAC_HAS_PNG GPAC_HAS_FFMPEG GPAC_HAS_THEORA GPAC_HAS_VORBIS
GPAC_HAS_XVID GPAC_HAS_LINUX_DVB
(ogmrip:7501): GLib-GObject-CRITICAL **: 12:28:41.543:
g_param_spec_internal: assertion 'g_param_spec_is_valid_name (name)' failed
** (ogmrip:7501): CRITICAL **: 12:28:41.543: ogmrip_settings_install_key:
assertion 'G_IS_PARAM_SPEC (pspec)' failed
** (ogmrip:7501): WARNING **: 12:28:41.588: Cannot set key
'container/format': no value
malloc(): unsorted double linked list corrupted
*** 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: bullseye/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (499, 'stable'), (100,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-5-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default
Versions of packages ogmrip depends on:
ii gconf-service 3.2.6-7
ii gconf2 3.2.6-7
ii gpac1.0.1+dfsg1-3
ii lame3.100-3
ii libc6 2.31-10
ii libdbus-glib-1-20.110-6
ii libdvdread8 6.1.1-2
ii libenchant-2-2 2.2.15-1
ii libgconf-2-43.2.6-7
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglade2-0 1:2.6.4-2.3
ii libglib2.0-02.66.7-2
ii libgtk2.0-0 2.24.33-1
ii libnotify4 0.7.9-3
ii libogg0 1.3.4-0.1
ii libogmrip1 1.0.1-3
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libtheora0 1.1.1+dfsg.1-15
ii libtiff54.2.0-1
ii libxml2 2.9.10+dfsg-6.3+b1
ii mencoder2:1.4+ds1-1
ii mkvtoolnix 52.0.0-1
ii mplayer 2:1.4+ds1-1
ii ogmrip-plugins 1.0.1-3
ii ogmtools1:1.5-4+b3
ii tesseract-ocr 4.1.1-2.1
ii vorbis-tools1.4.0-11+b1
Versions of packages ogmrip recommends:
pn ogmrip-ac3
pn ogmrip-dirac
ii ogmrip-doc 1.0.1-3
pn ogmrip-mpeg
pn ogmrip-oggz
pn ogmrip-profiles
pn ogmrip-video-copy
ogmrip suggests no packages.
-- no debconf information
Bug#985887: gscan2pdf: saves b&w scanned pages in inverted mode
tags 985887 patch
thanks
I've cherry-picked enough of this patch to fix this from master at
https://github.com/PhilterPaper/Perl-PDF-Builder/commit/d03b59847ecfbf3c7c31b8c1901d3878dba08040#diff-44803d0b8089ee5eb36d750b5be96b6038d4f32687973371d4c67310afc81ae1
i.e. the author should be Phil Perry, who is also the upstream maintainer.
diff --git a/lib/PDF/Builder/Resource/XObject/Image/TIFF_GT.pm b/lib/PDF/Builder/Resource/XObject/Image/TIFF_GT.pm
index 00fb893..7ac0cf9 100644
--- a/lib/PDF/Builder/Resource/XObject/Image/TIFF_GT.pm
+++ b/lib/PDF/Builder/Resource/XObject/Image/TIFF_GT.pm
@@ -164,6 +164,9 @@ sub handle_generic {
$dict->{'BitsPerComponent'} = PDFNum($tif->{'bitsPerSample'});
$dict->{'Colors'} = PDFNum($tif->{'colorSpace'} eq 'DeviceGray'?1 :3);
+if (!defined $tif->{'filter'} && $tif->{'bitsPerSample'} == 1) {
+$self->{'Decode'} = PDFArray(PDFNum(1), PDFNum(0));
+}
$stripcount = $tif->{'object'}->NumberOfStrips();
$buffer = '';
for my $i (0 .. $stripcount - 1) {
@@ -586,9 +589,10 @@ sub handle_ccitt {
$decode->{'K'} = (($tif->{'ccitt'} == 4 || (defined $tif->{'g3Options'} && $tif->{'g3Options'} & 0x1))? PDFNum(-1): PDFNum(0));
$decode->{'Columns'} = PDFNum($tif->{'imageWidth'});
$decode->{'Rows'} = PDFNum($tif->{'imageHeight'});
-# not sure why whiteIsZero needs to be flipped around???
-$decode->{'BlackIs1'} = PDFBool($tif->{'whiteIsZero'} == 0? 1: 0);
+$decode->{'BlackIs1'} = PDFBool($tif->{'whiteIsZero'} == 1? 1: 0);
$decode->{'DamagedRowsBeforeError'} = PDFNum(100);
+# all CCITT Fax need to flip black/white
+$self->{'Decode'} = PDFArray(PDFNum(1), PDFNum(0));
# g3Options bit 0 = 0 for 1-Dimensional, = 1 for 2-Dimensional MR
# aka T4Options bit 1 = 0 (compressed data only)
@@ -640,12 +644,6 @@ sub handle_ccitt {
sub read_tiff {
my ($self, $pdf, $tif, %opts) = @_;
-# not sure why blackIsZero needs to be flipped around???
-if (defined $tif->{'blackIsZero'}) {
-$tif->{'blackIsZero'} = $tif->{'blackIsZero'} == 1? 0: 1;
-$tif->{'whiteIsZero'} = $tif->{'blackIsZero'} == 1? 0: 1;
-}
-
$self->width($tif->{'imageWidth'});
$self->height($tif->{'imageHeight'});
OpenPGP_signature
Description: OpenPGP digital signature
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 usr/lib/R/site-library/DT/htmlwidgets/lib/datat
Bug#986032: ITP: r-bioc-netsam -- Network Seriation And Modularization
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: r-bioc-netsam Version : 1.30.0 Upstream Author : Jing Wang * URL : https://bioconductor.org/packages/NetSAM * License : LGPL-2 Programming Lang: R Description : Network Seriation And Modularization The NetSAM (Network Seriation and Modularization) package takes an edge-list representation of a network as an input, performs network seriation and modularization analysis, and generates as files that can be used as an input for the one-dimensional network visualization tool NetGestalt (http://www.netgestalt.org) or other network analysis. I intend to maintain this package.
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.
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#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 > +usr/share/javascript/jquery-datatables-extensions/Buttons/js/bu
Bug#986036: par: new release 1.53.0
Package: par Version: 1.52-5 Severity: wishlist X-Debbugs-Cc: andrea.gelm...@linux.it Dear Maintainer, thanks a lot for your work. I just wanna notify you they release a new version (1.53.0) one year ago. It would be nice to have it debianzied. Thanks again, Andrea -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
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#986036: par: new release 1.53.0
On 2021-03-28 Andrea Gelmini wrote: > Package: par > Version: 1.52-5 [...] > I just wanna notify you they release a new version (1.53.0) one > year ago. > It would be nice to have it debianzied. Hello Andrea, Thanks for the heads-up. Our automatic tracking (uscan, watch files) missed this due to the filename convention change (Par152.tar.gz -> Par-1.53.0.tar.gz). cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#985660: closed by Debian FTP Masters (reply to Jochen Sprickerhof ) (Bug#985660: fixed in gazebo 11.1.0+dfsg-5)
Thank you, it works fine now!
Bug#985918: ITP: bung -- backup next generation
Hi Charles That reminded me a lot to some tool I wrote 20 years ago or so for Solaris, later adapted also for Linux and FreeBSD: https://github.com/alexmyczko/ibackup including the sysinfo part, which I have in an up to date version, modernized a lot for todays need, I should release/update on that same page someday. Thoughts or parts you could profit from?
Bug#985815: RFS: usermanager/1.0.74+git20210323-1 [ITP] -- Graphical user manager
On 26.03.2021 06:12, Adam Borowski wrote:
On Wed, Mar 24, 2021 at 01:36:10PM +0100, Gürkan Myczko wrote:
> The menu icon for .desktop doesn't show up for me (in XFCE).
probably because it's .gif and fd.o doesn't support it
And, according to the spec:
https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
it's not supposed to.
Could you thus convert the icon to .png, please?
Absolutely, although I want to note, my test showed the gif is displayed
with
GNOME.
> Some method of su{,do}-to-root should be providen -- as is, the program
> fails to start claiming it needs root, and starting it as root manually
> involves some bits generally unknown by users who need a clicky-clicky
> tool (ie, the intended audience).
for upstream
Hrm, I then don't quite see what the intended audience for this package
could be. The basic instructions how to run a GUI program as root
(start a
shell, find out $DISPLAY, su/sudo, set up display, cp ~user/.Xauthority
~,
invoke from cmdline) are already far more complex than just running
relevant
adduser/usermod/deluser commands from a shell.
The audience is simple GUI users, true, the note "for upstream" was
meant
"for upstream to fix".
My recommendation would be open terminal, be root, start UserManager.
I don't even want to think about the possibilities how to do this (right
or not).
For the upstream to break his head imho.
And besides, running a GUI program as root is not that good an idea,
compared to separating out the privileged parts (be it to an unreliable
dbus
complexity, or to a simple easily-auditable setuid helper).
Possibly.
But really, I don't know enough about crossing privilege boundaries in
a GUI
to be comfortable reviewing this bit.
Ack.
Meow!
Bug#986039: ITP: r-cran-svmisc -- SciViews - Miscellaneous Functions
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: r-cran-svmisc Version : 1.1.0 Upstream Author : Philippe Grosjean * URL : https://cran.r-project.org/package=svMisc * License : GPL-2 Programming Lang: R Description : SciViews - Miscellaneous Functions Miscellaneous functions for SciViews or general use: manage a temporary environment attached to the search path for temporary variables you do not want to save() or load(), test if Aqua, Mac, Win, ... Show progress bar, etc I intend to maintain this package
Bug#985610: unblock: glib2.0/2.66.8-1 (+ advice on #985890)
Control: reopen -1
Control: retitle -1 unblock: glib2.0/2.66.8-1 (+ advice on #985890)
On Sat, 20 Mar 2021 at 17:08:14 +, Simon McVittie wrote:
> * Sync up with upstream 2.66.8 release, 95% of which we already apply
> via debian/patches
> * Add an error-handling patch from upstream that they recommended I
> consider including when backporting recent security fixes to buster
> * Add missing CVE ID references to changelog
It looks as though some packages, like ibus-clutter (#985453),
second-guess the dependency mechanism by applying their own check
that GLib is at least the (micro!) version they were compiled
against. Pseudocode:
if ((message = glib_check_version (GLIB_MAJOR_VERSION,
GLIB_MINOR_VERSION,
GLIB_MICRO_VERSION)) != NULL) {
fatal_error (message);
}
where glib_check_version() acts on the runtime GLib version, and
GLIB_MAJOR_VERSION etc. are the compile-time GLib version. I personally
think that's a harmful pattern, especially if the micro version is
included in the check, but I can understand upstreams that have it not
wanting to remove it.
For now, would it be possible to apply some age-days to glib2.0 to make
it migrate sooner than 14 days' time? That would mitigate this.
For a long-term solution, #985890 (currently RC but I'll probably
downgrade it) suggests that we should special-case glib_check_version()
in the .symbols file to generate a dependency on the upstream version
of GLib that was present at compile-time. I'm somewhat reluctant to do
that, because that will make it harder to get GLib-dependent packages
migrated if they are using the *other* common pattern for use of
glib_check_version():
if (glib_check_version (2, 35, 3) == NULL) {
work around a bug in GLib < 2.35.3, or do something the old way
}
else {
do something the new way
}
How would the release team prefer to handle this in future? I think the
options go like this:
1. Don't treat glib_check_version() specially in the .symbols file: it's
just another symbol, marked as having been introduced in GLib 2.6.
If packages second-guess the dependency system, either we should patch
that out, or those packages are responsible for generating a more strict
GLib dependency for themselves.
2. Special-case glib_check_version() to generate a dependency on
libglib2.0-0 (>= MAJOR.MINOR.0). If packages second-guess the dependency
system, make sure they are only checking for MAJOR.MINOR.0, on the basis
that GLib stable branches (MAJOR.MINOR.z, MINOR%2 == 0) do not introduce
new ABI. Packages that use it to check against a hard-coded version
will be slightly harder to migrate than they are now (when we upgrade
to a new minor version of GLib, which we do once per 6 months,
they'll get stuck behind it).
3. Special-case glib_check_version() to generate a dependency on
libglib2.0-0 (>= MAJOR.MINOR.MICRO) as requested by #985890. Packages
that use it to check against a hard-coded version will be harder
to migrate (when we upgrade to a new micro version of GLib, which I
estimate we do once per 2-8 weeks, they'll get stuck behind it).
Thanks,
smcv
Bug#985815: RFS: usermanager/1.0.74+git20210323-1 [ITP] -- Graphical user manager
Hi Matthew, FWIW, upstream seem to have an intent to resolve this, https://github.com/xen0vas/UserManager/issues/16: Application usage from users with limited privileges - Implement setuid access with privilege control xen0vas commented on Jun 27, 2020 Application usage from users with limited privileges in order to be able to use UserManager for changing passwords and have limited access. The implementation includes setuid setgid privilege checks as well as dropping and restoring privileges as needed due to elevated functionality when changing passwords and accessing system files. Gürkan, maybe you could work with them to deal with this prior to packaging? Good find the issue/16, let's see what happens. Maybe upstream can fix it altogether himself or with your help? :) Ah I forgot to answer kbs question about the audience and why the GUI is maybe useful/needed: it's users, and the GUI allows for detailed settings like expiry etc, without doing it wrong (syntax) or reading up on it in manual pages. I was thinking of this: https://wiki.debian.org/SmallOrganisationServer
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&suite=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#984975: gedit 3.30.2-2 segmentation fault
Hello Nenad Cvetkovic,
I tried to have a look at your core file.
It shows a crash with following backtrace [1].
The reason seems to be an invalid function pointer in variable "prepare".
The upstream issue in [2] shows a similar backtrace, but I
am not sure if they are related about what is causing it.
Investigation with a core file needs the same installed
package version, therefore the inspection at the host
creating the core has less chances for discrepancies.
Therefore, if you have gdb installed, you should be able
to generate a backtrace on your system too by e.g.:
coredumpctl list
coredumpctl gdb
bt
This gets normally improved by installing the dbgsym packages
or setting the environment DEBUGINFOD_URLS,
both and more described in [3].
Therefore the question, is there a reason for what looks like
local rebuilt packages libenchant1c2a and libxml2
due to the "~1.gbp73138d" version postfix?
Kind regards,
Bernhard
[1]
Core was generated by `/usr/bin/gedit --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x007f198f in ?? ()
[Current thread is 1 (Thread 0x7f7cde497a80 (LWP 15100))]
(gdb) bt
#0 0x007f198f in ?? ()
#1 0x7f7ce25f7669 in g_main_context_prepare
(context=context@entry=0x55ba65041ad0, priority=priority@entry=0x7ffcb3349aa0)
at ../../../glib/gmain.c:3492
#2 0x7f7ce25f806b in g_main_context_iterate
(context=context@entry=0x55ba65041ad0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3900
#3 0x7f7ce25f825c in g_main_context_iteration
(context=context@entry=0x55ba65041ad0, may_block=may_block@entry=1) at
../../../glib/gmain.c:3981
#4 0x7f7ce37aea2d in g_application_run (application=0x55ba650231e0,
argc=, argv=0x7ffcb3349c88) at ../../../gio/gapplication.c:2470
#5 0x55ba63f271fa in main (argc=2, argv=0x7ffcb3349c88) at
gedit/gedit.c:146
(gdb) info local
No symbol table info available.
(gdb) up
#1 0x7f7ce25f7669 in g_main_context_prepare
(context=context@entry=0x55ba65041ad0, priority=priority@entry=0x7ffcb3349aa0)
at ../../../glib/gmain.c:3492
3492 result = (* prepare) (source, &source_timeout);
(gdb) info local
result =
prepare = 0x7f198f
source_timeout = -1
i =
n_ready = 16
current_priority = 0
source = 0x55ba658e7d00
iter = {context = 0x55ba65041ad0, may_modify = 1, current_list =
0x7f7cd00020e0, source = 0x55ba658e7d00}
https://sources.debian.org/src/glib2.0/2.58.3-2+deb10u2/glib/gmain.c/#L3492
[2]
https://gitlab.gnome.org/GNOME/gedit/-/issues/51
[3]
https://wiki.debian.org/HowToGetABacktrace
# single-use Buster/stable amd64 qemu VM 2021-03-28
echo "set enable-bracketed-paste off" >> /etc/inputrc; bash
apt update
# to speedup testing
mv /etc/manpath.config /etc/manpath.config.renamed
apt install libeatmydata1
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libeatmydata.so
apt dist-upgrade
apt install systemd-coredump gdb lz4 gedit gnome \
gedit-dbgsym libglib2.0-0-dbgsym
wget
"https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=984975;filename=core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000.lz4;msg=5";
-O core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000.lz4
unlz4
core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000.lz4
gdb -q --core
core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000
gdb -q /usr/bin/gedit --core
core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000
benutzer@debian:~$ gdb -q /usr/bin/gedit --core
core.gedit.1000.e6ec596bfdba4283915bcec4a14baf60.15100.161546904000
Reading symbols from /usr/bin/gedit...(no debugging symbols found)...done.
[New LWP 15100]
[New LWP 15105]
[New LWP 15104]
[New LWP 15103]
[New LWP 15101]
[New LWP 15102]
warning: .dynamic section for "/lib/x86_64-linux-gnu/libpcre.so.3" is not at
the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/x86_64-linux-gnu/libenchant.so.1" is not at
the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/x86_64-linux-gnu/libzstd.so.1" is not at
the expected address (wrong library or version mismatch?)
warning: .dynamic section for
"/usr/lib/x86_64-linux-gnu/enchant/libenchant_myspell.so" is not at the
expected address (wrong library or version mismatch?)
warning: Could not load shared library symbols for 19 libraries, e.g.
/lib/x86_64-linux-gnu/libicui18n.so.65.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gedit --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000
Bug#985842: solo-python: please clarify package description
Hi Daniele, On 24.03.21 at 19:25, Daniele Forsi wrote: package description says "rest the key" , is that a typo for "reset the key"? yes, it's a typo - thanks for the catch. I'll fix it in the next upload (already committed the fix on slasa.d.o). Best, Philip
Bug#986042: texlive-base: Post-installation script fails with exit status 1
Package: texlive-base
Version: 2020.20210202-3
Severity: normal
X-Debbugs-Cc: he...@shayandoust.me
Dear Maintainer,
All tex packages were working fine for me until a couple of days ago,
when I did an apt update. I realised that texlive-base could not
configure itself. Unfortunately, no logs on that.
I did however purge and remove any stray files/directories belonging to
anything tex on my machine. I then proceeded to apt install texlive-base
to see if I can rectify the issue with a reinstall. I get the following
output:
[TRUNCATED]
Setting up texlive-binaries (2020.20200327.54578-7) ...
update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin
(xdvi.bin) in auto mode
update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex
(bibtex) in auto mode
Setting up lmodern (2.004.5-6.1) ...
Setting up texlive-base (2020.20210202-3) ...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
dpkg: error processing package texlive-base (--configure):
installed texlive-base package post-installation script subprocess returned
error exit status 1
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for libc-bin (2.31-10) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for install-info (6.7.0.dfsg.2-6) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for fontconfig (2.13.1-4.2) ...
Processing triggers for tex-common (6.16) ...
texlive-base is not ready, delaying updmap-sys call
update-language: texlive-base not installed and configured, doing nothing!
texlive-base is not ready, skipping fmtutil --all call
Errors were encountered while processing:
texlive-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am not quite sure what is going on here. I also attempted to remove
this package and install the texlive-full metapackage, however that
fails due to the cascading issue relating to texlive-base not being
configured & failing.
Any help and suggestions is much appreciated. I am not sure if this is
related to the package or not - it seems to be with the postinst script.
I am currently running on a system where sources.list is set to
bullseye.
Please feel free to write back if you require any further information,
or if there is something trivial and non-package related, to which I
understand this bug report being closed.
##
minimal input file
##
other files
##
List of ls-R files
lrwxrwxrwx 31 root 17 Feb 20:30 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
.rw-r--r-- 475 root 28 Mar 14:47 /etc/texmf/web2c/texmf.cnf
Warning: fmtutil.cnf cannot be found with kpsewhich!
Warning: updmap.cfg cannot be found with kpsewhich!
Warning: language.dat cannot be found with kpsewhich!
##
Files in /etc/texmf/web2c/
.rw-r--r-- 283 root 12 Feb 22:13 mktex.cnf
.rw-r--r-- 475 root 28 Mar 14:47 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages texlive-base depends on:
ii debconf [debconf-2.0] 1.5.75
ii libpaper-utils 1.1.28+b1
ii sensible-utils 0.0.14
ii tex-common 6.16
ii texlive-binaries 2020.20200327.54578-7
ii ucf3.0043
ii xdg-utils 1.1.3-4
Versions of packages texlive-base recommends:
ii lmodern 2.004.5-6.1
Versions of packages texlive-base suggests:
ii evince [postscript-viewer] 3.38.2-1
ii ghostscript [postscript-viewer] 9.53.3~dfsg-7
ii perl-tk 1:804.035-0.1+b1
pn xpdf | pdf-viewer
pn xzdec
Bug#986043: emboss: uses media types that are not registered
Package: emboss Severity: wishlist Hello everybody, In 2008, for the visualisation of DNA sequence chromatograms generated by Applied Biosystems machines and their successors, I created files declaring media types for the mailcap and FreeDesktop systems. Due to my incomplete undertanding at that time, I used standard tree media types, such as `application/vnd.appliedbiosystems.abif` without making sure they are declared. In principle, it would be better to either have the maker company to declare chromatogram files' media types and their magic numbers, or empower one of us (any volunteer?) to do so. Then we could propagate them in the "file" and "shared-mime-info" databases, which would increase the chance that the media types are used when the files are served on the Web or sent by email. Thus, I open this bug as a reminder. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#986044: unblock: nvidia-graphics-drivers/460.67-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: pkg-nvidia-de...@lists.alioth.debian.org Please unblock package nvidia-graphics-drivers [ Reason ] The new upstream LTS version 460.67 fixes several bugs, including an X.org crash. [ Impact ] X.org crash under certain conditions, and other minor bugs. There's also support for at least one new graphic card. [ Tests ] Tested with appropriate hardware and workload on a Bullseye desktop. [ Risks ] It's a proprietary non-free driver, so it is never possible to know the full extent of the changes. But the 460 series is intended for LTS. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] The debdiff excludes the binary blobs. unblock nvidia-graphics-drivers/460.67-1 $ debdiff --exclude NVIDIA-Linux-* nvidia-graphics-drivers_460.56-1.dsc nvidia- graphics-drivers_460.67-1.dsc diff -Nru --exclude 'NVIDIA-Linux-*' nvidia-graphics- drivers-460.56/debian/changelog nvidia-graphics-drivers-460.67/debian/changelog --- nvidia-graphics-drivers-460.56/debian/changelog 2021-02-27 23:26:36.0 + +++ nvidia-graphics-drivers-460.67/debian/changelog 2021-03-21 19:51:46.0 + @@ -1,3 +1,33 @@ +nvidia-graphics-drivers (460.67-1) unstable; urgency=medium + + * New upstream production branch release 460.67 (2021-03-18). +- Fixed a bug where using ray tracing extensions on multi-GPU setups could + result in application instability if the GPUs did not match. +- Fixed an issue that prevented G-SYNC from working properly after a mode + switch on Kepler-based GPUs. + * New upstream release 450 series. +- Fixed a driver installation failure on Linux kernel 5.11 release + candidates, where the NVIDIA kernel module failed to build with error + "error: implicit declaration of function 'sys_close'". + * New upstream release 390 series. +- Fixed a bug where vkCreateSwapchain could cause the X Server to crash when + an invalid imageFormat was provided. +- Fixed a driver installation failure on Linux kernel 5.11 release + candidates, where the NVIDIA kernel module failed to build with error + "fatal error: asm/kmap_types.h: No such file or directory". + + [ Luca Boccassi ] + * Update nv-readme.ids. + + -- Andreas Beckmann Sun, 21 Mar 2021 20:51:46 +0100 + +nvidia-graphics-drivers (460.56-2) unstable; urgency=medium + + * Add libnvidia-ml.so slave alternative if libnvidia-ml-dev is installed. +(Closes: #984881) + + -- Andreas Beckmann Wed, 10 Mar 2021 21:03:59 +0100 + nvidia-graphics-drivers (460.56-1) unstable; urgency=medium * New upstream production branch release 460.56 (2021-02-25). diff -Nru --exclude 'NVIDIA-Linux-*' nvidia-graphics- drivers-460.56/debian/nvidia-alternative.postinst.in nvidia-graphics- drivers-460.67/debian/nvidia-alternative.postinst.in --- nvidia-graphics-drivers-460.56/debian/nvidia-alternative.postinst.in 2021-02-27 23:26:36.0 + +++ nvidia-graphics-drivers-460.67/debian/nvidia-alternative.postinst.in 2021-03-21 19:51:46.0 + @@ -84,10 +84,14 @@ $(add_slave /etc/nvidia/nvidia-modprobe.conf nvidia- modprobe.conf /etc/#PRIVATE#/nvidia-modprobe.conf) $(add_slave /etc/nvidia/nvidia-load.conf nvidia-load.conf /etc/#PRIVATE#/nvidia-load.conf) " + libnvidia_ml_so_slave= + if [ -f /usr/include/nvml.h ]; then + libnvidia_ml_so_slave="$(add_multiarch_slave /usr/lib "" libnvidia-ml.so /usr/lib #PRIVATE#/)" + fi if echo "$slaves" | grep -q "slave" ; then - update-alternatives --install /usr/lib/nvidia/nvidia nvidia /usr/lib/#PRIVATE# #MAJOR# $slaves $conf_slaves + update-alternatives --install /usr/lib/nvidia/nvidia nvidia /usr/lib/#PRIVATE# #MAJOR# $slaves $conf_slaves $libnvidia_ml_so_slave # work around #916799 and re-register the alternative to clean- up leftover slaves - update-alternatives --install /usr/lib/nvidia/nvidia nvidia /usr/lib/#PRIVATE# #MAJOR# $slaves $conf_slaves + update-alternatives --install /usr/lib/nvidia/nvidia nvidia /usr/lib/#PRIVATE# #MAJOR# $slaves $conf_slaves $libnvidia_ml_so_slave else update-alternatives --remove nvidia /usr/lib/#PRIVATE# fi diff -Nru --exclude 'NVIDIA-Linux-*' nvidia-graphics- drivers-460.56/debian/nvidia-alternative.triggers.in nvidia-graphics- drivers-460.67/debian/nvidia-alternative.triggers.in --- nvidia-graphics-drivers-460.56/debian/nvidia-alternative.triggers.in 2021-02-27 23:26:36.0 + +++ nvidia-graphics-drivers-460.67/debian/nvidia-alternative.triggers.in 2021-03-21 19:51:46.0 + @@ -4,3 +4,5 @@ interest-await /usr/lib/#PRIVATE# interest-await /usr/lib/i386-linux-gnu/#PRIVATE# interest-await /usr
Bug#986045: transmission-daemon: transmission daemon 3.0 unresponsive API / WebUI during downloads
Package: transmission-daemon Version: 3.00-1 Severity: normal X-Debbugs-Cc: recording.col...@gmail.com Dear Maintainer, When I run transmission WebUI on freedombox, half way through a download the WebUI will crash. I then reboot the machine and restart the torrent download and it will soon crash again. I have found a post on github where people are having the same problem with - transmission-daemon I have posted the url below from github so you can have a look and be aware that there is a bug with transmission daemon 3.0 Regards: peter colton transmission daemon 3.0 unresponsive API / WebUI during downloads https://github.com/transmission/transmission/issues/1314 -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages transmission-daemon depends on: ii adduser 3.118 ii libc62.31-10 ii libcurl4 7.74.0-1.1 ii libevent-2.1-7 2.1.12-stable-1 ii libminiupnpc17 2.2.1-1 ii libnatpmp1 20150609-7.1 ii libssl1.11.1.1j-1 ii libsystemd0 247.3-3 ii lsb-base 11.1.0 ii transmission-common 3.00-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages transmission-daemon recommends: ii transmission-cli 3.00-1 transmission-daemon suggests no packages. -- Configuration Files: /etc/transmission-daemon/settings.json [Errno 13] Permission denied: '/etc/transmission-daemon/settings.json' -- no debconf information
Bug#986042: texlive-base: Post-installation script fails with exit status 1
Am 28.03.2021 um 15:58 teilte Shayan Doust mit:
Hi,
Setting up texlive-binaries (2020.20200327.54578-7) ...
update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin
(xdvi.bin) in auto mode
update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex
(bibtex) in auto mode
Setting up lmodern (2.004.5-6.1) ...
Setting up texlive-base (2020.20210202-3) ...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
Can't use string ("2") as an ARRAY ref while "strict refs" in use at
/usr/bin/tl-paper line 112.
dpkg: error processing package texlive-base (--configure):
installed texlive-base package post-installation script subprocess returned
error exit status 1
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for libc-bin (2.31-10) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for install-info (6.7.0.dfsg.2-6) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for fontconfig (2.13.1-4.2) ...
Processing triggers for tex-common (6.16) ...
texlive-base is not ready, delaying updmap-sys call
update-language: texlive-base not installed and configured, doing nothing!
texlive-base is not ready, skipping fmtutil --all call
Errors were encountered while processing:
texlive-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
What is the content of /etc/papersize? Does running "dpkg-reconfigure
libpaper1" and then try again solve your issue?
Hilmar
--
sigfault
OpenPGP_signature
Description: OpenPGP digital signature
Bug#985151: dh_bash-completion: treats nitrokey-app file list as script
Hi, Kevin,
On Mon, 15 Mar 2021 07:07:36 -0600
Kevin Locke wrote:
>
> I've attached an updated version
> which matches & and | in addition to ; as command separators. We may
> also want to consider modifying the compgen expression in the same way.
I added this patch (with a changelog entry) to the repository at:
https://salsa.debian.org/debian/bash-completion/-/commits/master
Then I tested it against as much packages as possible:
# Download packages that have some completion file (get the list from
apt-file)
apt-file search "/usr/share/bash-completion/completions" | cut -d ':' -f 1 |
sort -u | tr '\n' ' ' | xargs apt-get source -y
# Unpack all
for file in *.deb; do dpkg-deb --extract $file extract/; done
# Run each package.bash-completion file against a simplified version
# of the perl script [1] (with and without this change)
for i in `find -name *.bash-completion`; do echo $i; perl
/var/tmp/build-root/test-me/root/perl-pre.pl < $i; done > _result.pre
for i in `find -name *.bash-completion`; do echo $i; perl
/var/tmp/build-root/test-me/root/perl-pos.pl < $i; done > _result.pos
# Compare the results
diff -u1 _result.{pre,pos}
./nitrokey-app-1.4.2/debian/nitrokey-app.bash-completion
-Yes
+No
So, the change seems to affect nitrokey-app only, which is fine...
Nevertheless, I haven't released this to unstable, because of the
freeze... I'm worried that this change could undesired side-effects
(such as making other packages loose their completions) at this point
of the release cycle, even though the test is telling me it won't.
Let me know your thoughts (about this and/or about the tests I ran).
I'll submit it to experimental, then, once the freeze is lifted, to
unstable.
Cheers,
Gabriel
[1] The simplified version of the modified perl script:
while () {
# Get rid of lines containing just spaces or comments.
chomp;
s/^\s++//;
next if /^#/;
s/\s++$//;
# We always ignore/permit empty lines
next if $_ eq '';
# This is the heart of the script. Here, we check for some
# well-known idioms on bash scripts, and try to determine if
# they're present in the file we're examining. We assume that
# if they are, then this means the file is a bash-completion
# script.
#
# The regexes check:
#
# - If we're calling the bash function "complete", which is a
# pretty common thing to do in bash-completion scripts, or
#
# - If we're using the $(program) way of executing a program.
# We don't take into account multi-line statements. Or
#
# - If we're calling the bash function "compgen", which is
# also a pretty common thing that bash-completion scripts
# do. Or
#
# - If we see an "if...then" construction in the file. We
# take into account multi-line statements.
if (/(^|[|&;])\s*complete.*-[A-Za-z].*/
|| /\$\(.*\)/
|| /\s*compgen.*-[A-Za-z].*/
|| /\s*if.*;.*then/s) {
print "Yes\n";
exit 0;
}
}
print "No\n";
exit 0;
Bug#985151: dh_bash-completion: treats nitrokey-app file list as script
Hi Gabriel,
On Sun, 2021-03-28 at 12:12 -0300, Gabriel F. T. Gomes wrote:
> On Mon, 15 Mar 2021 07:07:36 -0600 Kevin Locke wrote:
>> I've attached an updated version
>> which matches & and | in addition to ; as command separators. We may
>> also want to consider modifying the compgen expression in the same way.
>
> I added this patch (with a changelog entry) to the repository at:
>
> https://salsa.debian.org/debian/bash-completion/-/commits/master
Looks great, thanks!
> Then I tested it against as much packages as possible:
>
> # Download packages that have some completion file (get the list from
> apt-file)
> apt-file search "/usr/share/bash-completion/completions" | cut -d ':' -f 1
> | sort -u | tr '\n' ' ' | xargs apt-get source -y
>
> # Unpack all
> for file in *.deb; do dpkg-deb --extract $file extract/; done
>
> # Run each package.bash-completion file against a simplified version
> # of the perl script [1] (with and without this change)
> for i in `find -name *.bash-completion`; do echo $i; perl
> /var/tmp/build-root/test-me/root/perl-pre.pl < $i; done > _result.pre
> for i in `find -name *.bash-completion`; do echo $i; perl
> /var/tmp/build-root/test-me/root/perl-pos.pl < $i; done > _result.pos
>
> # Compare the results
> diff -u1 _result.{pre,pos}
>./nitrokey-app-1.4.2/debian/nitrokey-app.bash-completion
> -Yes
> +No
>
>
> So, the change seems to affect nitrokey-app only, which is fine...
>
> Nevertheless, I haven't released this to unstable, because of the
> freeze... I'm worried that this change could undesired side-effects
> (such as making other packages loose their completions) at this point
> of the release cycle, even though the test is telling me it won't.
>
> Let me know your thoughts (about this and/or about the tests I ran).
>
>
> I'll submit it to experimental, then, once the freeze is lifted, to
> unstable.
That sounds like a good plan to me. Even with the extra testing (which
I appreciate!) I don't think fixing a single, likely long-standing,
issue with nitrokey-app is worth the risk of inadvertently breaking
other packages during a freeze.
Thanks again,
Kevin
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#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:
- gnome
Bug#986034: sa-compile broken under apt-get upgrade
Subject: sa-compile fails under apt-get upgrade Package: sa-compile Version: 3.4.2-1+deb10u3 Severity: normal Dear Maintainer, # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: liblua5.2-0 Use 'apt autoremove' to remove it. The following packages have been kept back: linux-image-amd64 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up sa-compile (3.4.2-1+deb10u3) ... Running sa-compile (may take a long time) chmod: changing permissions of '/var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm': Operation not permitted dpkg: error processing package sa-compile (--configure): installed sa-compile package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: sa-compile E: Sub-process /usr/bin/dpkg returned an error code (1) $ ls -l /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm -r--r--r-- 1 root root 32641 Aug 25 2020 /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm $ ls -l /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/ total 0 drwxr-xr-x 2 debian-spamd debian-spamd 23 Aug 25 2020 CompiledRegexps -- 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-13-amd64 (SMP w/6 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sa-compile depends on: ii gcc 4:8.3.0-1 ii libc6-dev 2.28-10 ii make 4.2.1-1.2 ii re2c 1.1.1-1 ii spamassassin 3.4.2-1+deb10u3 sa-compile recommends no packages. sa-compile suggests no packages. -- no debconf information
Bug#986042: texlive-base: Post-installation script fails with exit status 1
Hello Hilmar,
The content of /etc/papersize is a4.
Running "dpkg-reconfigure libpaper1" again, and then trying again for
texlive-base, spits out the
same issue I've reported.
Kind regards
On Sun, Mar 28, 2021 at 04:53:56PM +0200, Hilmar Preuße wrote:
> Am 28.03.2021 um 15:58 teilte Shayan Doust mit:
>
> Hi,
>
> > Setting up texlive-binaries (2020.20200327.54578-7) ...
> > update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin
> > (xdvi.bin) in auto mode
> > update-alternatives: using /usr/bin/bibtex.original to provide
> > /usr/bin/bibtex (bibtex) in auto mode
> > Setting up lmodern (2.004.5-6.1) ...
> > Setting up texlive-base (2020.20210202-3) ...
> > mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
> > mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
> > mktexlsr: Updating /var/lib/texmf/ls-R...
> > mktexlsr: Done.
> > Can't use string ("2") as an ARRAY ref while "strict refs" in use at
> > /usr/bin/tl-paper line 112.
> > Can't use string ("2") as an ARRAY ref while "strict refs" in use at
> > /usr/bin/tl-paper line 112.
> > Can't use string ("2") as an ARRAY ref while "strict refs" in use at
> > /usr/bin/tl-paper line 112.
> > Can't use string ("2") as an ARRAY ref while "strict refs" in use at
> > /usr/bin/tl-paper line 112.
> > Can't use string ("2") as an ARRAY ref while "strict refs" in use at
> > /usr/bin/tl-paper line 112.
> > dpkg: error processing package texlive-base (--configure):
> > installed texlive-base package post-installation script subprocess
> > returned error exit status 1
> > Processing triggers for desktop-file-utils (0.26-1) ...
> > Processing triggers for gnome-menus (3.36.0-1) ...
> > Processing triggers for libc-bin (2.31-10) ...
> > Processing triggers for man-db (2.9.4-2) ...
> > Processing triggers for install-info (6.7.0.dfsg.2-6) ...
> > Processing triggers for mailcap (3.69) ...
> > Processing triggers for fontconfig (2.13.1-4.2) ...
> > Processing triggers for tex-common (6.16) ...
> > texlive-base is not ready, delaying updmap-sys call
> > update-language: texlive-base not installed and configured, doing nothing!
> > texlive-base is not ready, skipping fmtutil --all call
> > Errors were encountered while processing:
> > texlive-base
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> What is the content of /etc/papersize? Does running "dpkg-reconfigure
> libpaper1" and then try again solve your issue?
>
> Hilmar
> --
> sigfault
>
>
--
Shayan Doust - 201427418
Fingerprint: 0401 A810 A6F2 4303 1EA3 9759 6D7D 4419 19D0 2395
Note: all emails sent by me are signed with my PGP key.
signature.asc
Description: PGP signature
Bug#986035: GPRename Spanish translation
Package: gprename Version: 20140325-1 Severity: normal Hello I attach a full GPRename Spanish translation. The current (really old) official Spanish translation is remarkably incomplete and means that a Spanish speaker sees half of the things in the GPRename window in English, making it largely unusable if you don't know English. I report this bug against the Buster version in the hope that it will be fixed also in the Buster branch, but the exact same bug occurs with the current testing/sid version ( 20201214-0.1 ) which has the same Spanish translation. I have submitted this same translation file to the upstream ( https://sourceforge.net/p/gprename/mailman/message/37250062 ), but considering the long time between release by the upstream developers plus the delay of Debian packaging itself, if it is not implemented directly in Debian it will take years to have this translation available in Debian. Thank you very much! msgid "" msgstr "" "Project-Id-Version: GPRename\n" "Last-Translator: Alexis Puente Montiel \n" "Report-Msgid-Bugs-To: Alexis Puente Montiel \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" msgid "ALL UPPERCASE" msgstr "TODO MAYÃSCULAS" msgid "About" msgstr "Acerca de" msgid "Add numbers starting at" msgstr "Añadir números a partir de" msgid "After the numbers" msgstr "Después de los números" msgid "Automatic preview" msgstr "Previsualización automática" msgid "" "Automatic preview: This option will be turned off automatically if there's " "more than 10,000 files or directories listed." msgstr "" "Previsualización automática: Esta opción será desactivada automáticamente si hay " "más de 10.000 archivos o carpetas listados." msgid "" "Backreferences with Regular expression cannot be use as $1 is considered a " "Perl variable." msgstr "" "Las retro-referencias con expresiones regulares no pueden usarse porque $1 " "se considera una variable Perl." msgid "Before the numbers" msgstr "Antes de los números" msgid "Cannot rename because it already exist." msgstr "No puede renombrarse porque ya existe." msgid "Cannot rename because the filename is too long." msgstr "No puede renombrarse porque el nombre de archivo es demasiado largo." msgid "Case Change" msgstr "Mayúsculas / Minúsculas" msgid "Case sensitive" msgstr "Sensible a mayúsculas / minúsculas" msgid "Clear" msgstr "Limpiar" msgid "Contents" msgstr "Contenido" msgid "Delete between" msgstr "Eliminar entre las posiciones" msgid "Directories" msgstr "Carpetas" msgid "Directory" msgstr "Carpeta" msgid "Disable security check" msgstr "Desactivar la comprobación de seguridad" msgid "" "Disable security check: If used, this can delete files after renaming, only " "use this when you rename case on a VFAT (Windows) partition." msgstr "" "Desactivar la comprobación de seguridad: Si se usa, puede eliminarse archivos después de renombrar, " "solo usarlo para renombrar entre mayúsculas y minúsculas en una partición VFAT (Windows)." msgid "Files" msgstr "Archivos" msgid "Filter" msgstr "Filtro" msgid "Fullscreen" msgstr "Pantalla completa" msgid "Insert" msgstr "Insertar" msgid "Insert / Delete" msgstr "Insertar / Eliminar" msgid "Insert before the numbers" msgstr "Insertar antes" msgid "Keep existing names" msgstr "Mantener los nombres existentes" msgid "Name" msgstr "Nombre" msgid "New name" msgstr "Nuevo nombre" msgid "No" msgstr "No" msgid "Numerical" msgstr "Numérico" msgid "Only The First Letter And After" msgstr "Solo la primera letra y después de" msgid "Only the first letter and after" msgstr "Solo la primera letra y después de" msgid "Only show files or directories that contains" msgstr "Solo mostrar los archivos o carpetas que contienen" msgid "Only the first letter" msgstr "Solo la primera letra" msgid "Quit" msgstr "Cerrar" msgid "Refre_sh" msgstr "Refre_scar" msgid "Regular expression" msgstr "Expresión regular" msgid "Remember last directory" msgstr "Recordar la última carpeta" msgid "Replace" msgstr "Sustituir" msgid "Replace / Remove" msgstr "Sustituir / Eliminar" msgid "Selected" msgstr "Seleccionado" msgid "Show contents of subdirectories" msgstr "Mostrar el contenido de las subcarpetas" msgid "Show hidden files" msgstr "Mostrar los archivos ocultos" msgid "Show path" msgstr "Mostrar ruta" msgid "The log file is over 1M, you should clear it from the Options menu." msgstr "" "El archivo de registro es mayor de 1 MiB, deberÃa borrarlo desde el menú" "Opciones." msgid "To specify the end, use a negative number or a high number." msgstr "Para especificar el final, use un número negativo o un número elevado." msgid "Trim spaces" msgstr "Recortar los espacios" msgid "" "Trim spaces: Automatically trim double spaces to only one and remove spaces " "at the beginning or end of the names." msgstr "" "Recortar los espacios: Automáticamente recortar los espacios dobles a espacios únicos " "y elim
Bug#986038: imagej currently has an undeclared and substitutable dependency
Package: imagej Version: 1.52j-1 Severity: important Hello The /usr/bin/imagej script uses: if [ -z "$JAVA_HOME" ] ; then JAVA_HOME=`/usr/sbin/update-java-alternatives -l | grep openjdk | grep $(dpkg-architecture -q DEB_TARGET_ARCH) | sort | tail -1 | tr -s ' ' | cut -d' ' -f 3` fi but 'dpkg-architecture' is in 'dpkg-dev' package which is not declared as a 'dependency' of the 'imagej' package. In order to avoid adding unnecessary or easily replaceable dependencies, it seems that a good solution could be to replace $(dpkg-architecture -q DEB_TARGET_ARCH) with dpkg --print-architecture Thank you very much!
Bug#986048: aux.c: change "sigfile[]" to "sigfile_name[]" and move it to the head of the file to make the name usable in it
Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch
Dear Maintainer,
>From b05e6a18cf49e1aca681bebd0e51521af1231c5d Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason
>Date: Sun, 28 Mar 2021 16:06:18 +
>Subject: [PATCH] aux.c: change "sigfile[]" to "sigfile_name[]" and move it to
> the head of the file to make the name usable in it
The name "sigfile" was also used for a file pointer (FILE *).
Signed-off-by: Bjarni Ingi Gislason
---
aux.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/aux.c b/aux.c
index 72f3b6f..a070136 100644
--- a/aux.c
+++ b/aux.c
@@ -48,6 +48,9 @@ int response_check_pause = 0; /* time to wait
for
* background cmds */
char *response_dflt_answer = "send";
+static char sigfile_name[FILENAME];
+
+
int aux_sh(article_header *, char *, char *, char *, char *, char *,
int, int);
@@ -206,7 +209,6 @@ find_signature(void)
{
struct passwd *passwd;
char *dotdir;
-charsigfile[FILENAME];
FILE *fp;
passwd = getpwuid(getuid());
@@ -215,20 +217,20 @@ find_signature(void)
dotdir = passwd->pw_dir;
if (dotdir[0] == '~') {
- (void) strcpy(sigfile, passwd->pw_dir);
- (void) strcat(sigfile, &dotdir[1]);
+ (void) strcpy(sigfile_name, passwd->pw_dir);
+ (void) strcat(sigfile_name, &dotdir[1]);
} else {
- (void) strcpy(sigfile, dotdir);
+ (void) strcpy(sigfile_name, dotdir);
}
-(void) strcat(sigfile, "/");
-(void) strcat(sigfile, ".signature");
+(void) strcat(sigfile_name, "/");
+(void) strcat(sigfile_name, ".signature");
#ifdef DEBUG
-fprintf(stderr, "sigfile = '%s'\n", sigfile);
+fprintf(stderr, "sigfile_name = '%s'\n", sigfile_name);
sleep(2);
#endif
-fp = fopen(sigfile, "r");
+fp = fopen(sigfile_name, "r");
#ifdef DEBUG
if (fp != NULL) {
@@ -274,7 +276,7 @@ append_signature(FILE * sigfile)
(void) fclose(temp);
#ifdef DEBUG
-printf(".signature appended (from %s)\n", sigfile);
+printf(".signature appended (from %s)\n", sigfile_name);
sleep(10);
#endif
}
--
2.30.2
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.19-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
-- debconf information excluded
--
Bjarni I. Gislason
Bug#946118: synaptics touchpad does not work in debian installer graphical mode
Hi, Samuel Thibault wrote (Mon, 22 Feb 2021 21:03:04 +0100): > Holger Wansing, le sam. 20 févr. 2021 20:45:59 +0100, a ecrit: > > Samuel Thibault wrote (Sat, 7 Dec 2019 22:54:09 > > +0100): > > > Samuel Thibault, le mer. 04 déc. 2019 01:52:36 +0100, a ecrit: > > > > Thinking of it... IIRC the touchpad is not working on my DELL XPS13 > > > > laptop in g-i. > > > > > > Indeed, it doesn't work. > > > > Now that the graphical installer uses libinput instead of evdev, maybe it's > > worth it to try if it works for you now with latest builds? > > It does work for me in the latest builds that use libinput, indeed. As situation has clearly improved (touchpad works fine here now on my machines too, where they did not before), I'm closing this bug. @dinar: maybe you can check if it works for you now, with latest images? Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#985934: chromium: Built in update feature appears to be enabled
Hello, Are you sure that you were using Chromium from the Debian package? Michel Le Bihan
Bug#866183: Compliment of the season
-- Compliment of the season Greetings from Mr John Zengo i have something to discuss with you and it is very important and urgent. please feel free to reach me on my e-mail Address( johnzeng...@gmail.com) for further clarifications yours sincerely John Zengo
Bug#986049: firejail: Chromium profile breaks webext-browserpass
Package: firejail
Version: 0.9.64.4-2
Severity: normal
Dear Maintainer,
some time earlier this year, Chromium started to show an error message on each
start that the "browserpass" extension could not be properly loaded.
I finally got around to investigate this, and realized it is caused by
firejail: something changed in firejail or the extension, such that extension
paths are not longer available to chromium.
The extension folder looks like this:
$ ls /usr/share/chromium/extensions/browserpass/ -lah
total 44K
drwxr-xr-x 2 root root 4,0K 6. Mär 23:07 .
drwxr-xr-x 3 root root 4,0K 28. Dez 15:41 ..
lrwxrwxrwx 1 root root 95 23. Jun 2020 css ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/css
lrwxrwxrwx 1 root root 97 23. Jun 2020 fonts ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/fonts
lrwxrwxrwx 1 root root 102 16. Feb 11:32 icon16.png ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon16.png
lrwxrwxrwx 1 root root 100 16. Feb 11:32 icon.png ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.png
lrwxrwxrwx 1 root root 100 16. Feb 11:32 icon.svg ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.svg
lrwxrwxrwx 1 root root 94 23. Jun 2020 js ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/js
-rw-r--r-- 1 root root 2,0K 16. Feb 11:32 manifest.json
lrwxrwxrwx 1 root root 99 23. Jun 2020 options ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/options
lrwxrwxrwx 1 root root 97 23. Jun 2020 popup ->
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/popup
Inside the firejail, those symlinks are dead, since the "mozilla" folder seems
to be blocked.
Kind regards,
Ralf
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-security'), (500,
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 firejail depends on:
ii libapparmor1 2.13.6-9
ii libc6 2.31-10
ii libselinux1 3.1-3
Versions of packages firejail recommends:
ii firejail-profiles 0.9.64.4-2
ii iproute2 5.10.0-4
ii iptables 1.8.7-1
ii xauth 1:1.1-1
ii xdg-dbus-proxy 0.1.2-2
ii xserver-xephyr 2:1.20.10-3
firejail suggests no packages.
-- no debconf information
Bug#984920: php7.3-imap: Using php-imap may cause segmentation faults
Dear Maintainer,
I tried to have a look at this segfault.
As far as I can see the issue here is a memory access after the
php heap, where this memory was allocated from, got unmapped.
Below are the backtraces for allocation [1], unmapping [2]
and the segfault [3].
Some more details in attached file.
Kind regards,
Bernhard
[1]
Breakpoint 69, 0x5636fef8fa40 in timelib_strtotime (s=0x5636ff1ae641 "now",
len=len@entry=3, errors=errors@entry=0x7fffd2243b98, tzdb=0x5636ffcb14c0,
tz_get_wrapper=tz_get_wrapper@entry=0x5636fef86af0 ) at
./ext/date/lib/parse_date.c:22046
22046 in.errors = timelib_malloc(sizeof(timelib_error_container));
1: x/i $pc
=> 0x5636fef8fa40 : mov%rax,0x60(%rsp)
(rr) bt
#0 0x5636fef8fa40 in timelib_strtotime (s=0x5636ff1ae641 "now",
len=len@entry=3, errors=errors@entry=0x7fffd2243b98, tzdb=0x5636ffcb14c0,
tz_get_wrapper=tz_get_wrapper@entry=0x5636fef86af0 ) at
./ext/date/lib/parse_date.c:22046
#1 0x5636fef8c18c in php_date_initialize (dateobj=0x7f3a880d1a10,
time_str=0x0, time_str_len=, format=0x0, timezone_object=0x0,
ctor=1) at ./ext/date/php_date.c:2686
#2 0x5636fef8c9e5 in zim_DateTime___construct (execute_data=0x7f3a8921f0c0,
return_value=) at ./ext/date/php_date.h:143
#3 0x5636ff1a0b4b in ZEND_DO_FCALL_SPEC_RETVAL_UNUSED_HANDLER () at
./Zend/zend_vm_execute.h:984
#4 execute_ex (ex=0x7f3a89200040) at ./Zend/zend_vm_execute.h:55523
#5 0x5636ff1a25e7 in zend_execute
(op_array=op_array@entry=0x7f3a880c0600, return_value=0x0,
return_value@entry=0x7f3a8921e9c0) at ./Zend/zend_vm_execute.h:60935
#6 0x5636ff11b233 in zend_execute_scripts (type=type@entry=8,
retval=0x7f3a8921e9c0, retval@entry=0x0, file_count=file_count@entry=3) at
./Zend/zend.c:1568
#7 0x5636ff0bb788 in php_execute_script (primary_file=)
at ./main/main.c:2637
#8 0x5636ff1a4b9e in do_cli (argc=3, argv=0x5636ffb0ca30) at
./sapi/cli/php_cli.c:1000
#9 0x5636fef80b9b in main (argc=3, argv=0x5636ffb0ca30) at
./sapi/cli/php_cli.c:1396
(rr) when
Current event: 4495
(rr) x/4xb 0x7f3a88055ca8
0x7f3a88055ca8: 0xb00xa10x0e0x88
[2]
Breakpoint 70, munmap () at ../sysdeps/unix/syscall-template.S:78
78 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht
gefunden.
1: x/i $pc
=> 0x7f3a8b7e31d0 : mov$0xb,%eax
(rr) bt
#0 munmap () at ../sysdeps/unix/syscall-template.S:78
#1 0x5636ff0f26f7 in zend_mm_munmap (size=2097152, addr=) at ./Zend/zend_alloc.c:777
#2 zend_mm_chunk_free (addr=, size=size@entry=2097152,
heap=) at ./Zend/zend_alloc.c:777
#3 0x5636ff0f2b3a in zend_mm_shutdown (heap=0x7f3a89200040, full=0,
silent=) at ./Zend/zend_alloc.c:2301
#4 0x5636ff0ba357 in php_request_shutdown (dummy=) at
./main/main.c:1951
#5 0x5636ff1a3fda in do_cli (argc=3, argv=0x5636ffb0ca30) at
./sapi/cli/php_cli.c:1167
#6 0x5636fef80b9b in main (argc=3, argv=0x5636ffb0ca30) at
./sapi/cli/php_cli.c:1396
(rr) when
Current event: 4620
(rr) x/4xb 0x7f3a88055ca8
0x7f3a88055ca8: 0x000x000x000x00
(rr) finish
Run till exit from #0 munmap () at ../sysdeps/unix/syscall-template.S:78
0x5636ff0f26f7 in zend_mm_munmap (size=2097152, addr=)
at ./Zend/zend_alloc.c:777
777 zend_mm_munmap(addr, size);
1: x/i $pc
=> 0x5636ff0f26f7 : test %eax,%eax
(rr) x/4xb 0x7f3a88055ca8
0x7f3a88055ca8: Cannot access memory at address 0x7f3a88055ca8
[3]
PHP Fatal error: Uncaught ErrorException: Notice: Unknown: Unexpected
characters at end of address: < (errflg=3) in Unknown:0
Stack trace:
#0 [internal function]:
Symfony\Component\ErrorHandler\ErrorHandler->handleError(8, 'Unknown:
Unexpe...', 'Unknown', 0, NULL)
#1 {main}
thrown in Unknown on line 0
Program received signal SIGSEGV, Segmentation fault.
0x5636fefac749 in timelib_error_container_dtor (errors=0x7f3a88055ca8)
at ./ext/date/lib/timelib.c:156
156 for (i = 0; i < errors->warning_count; i++) {
1: x/i $pc
=> 0x5636fefac749 : mov
0x14(%rdi),%edi
2: /x $rax = 0x0
3: /x $rsp = 0x7fffd2247350
(rr) bt
#0 0x5636fefac749 in timelib_error_container_dtor
(errors=0x7f3a88055ca8) at ./ext/date/lib/timelib.c:156
#1 0x5636fef82e9c in zm_shutdown_date (type=,
module_number=) at ./ext/date/php_date.c:945
#2 0x5636ff120397 in module_destructor
(module=module@entry=0x5636ffb3ace0) at ./Zend/zend_API.c:2575
#3 0x5636ff119e6c in module_destructor_zval (zv=) at
./Zend/zend.c:745
#4 0x5636ff12ada3 in _zend_hash_del_el_ex (prev=, p=, idx=1, ht=) at ./Zend/zend_hash.c:1182
#5 _zend_hash_del_el (p=0x5636ffb900f0, idx=1, ht=0x5636ff31b260
) at ./Zend/zend_hash.c:1205
#6 zend_hash_graceful_reverse_destroy (ht=ht@entry=0x5636ff31b260
) at ./Zend/zend_hash.
Bug#986040: unblock: refcard/11.0
Package: release.debian.org Usertags: unblock I would like to request an unblock for version 11.0 of the Debian reference card (source package 'refcard'). I have uploaded the 11.0 version to unstable recently. The changings include some latest changes to make package fit for Bullseye. The debdiff is attached. Thanks Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 diff -Nru refcard-10.7/debian/changelog refcard-11.0/debian/changelog --- refcard-10.7/debian/changelog 2020-06-06 19:07:58.0 +0200 +++ refcard-11.0/debian/changelog 2021-03-14 16:17:33.0 +0100 @@ -1,8 +1,16 @@ +refcard (11.0) unstable; urgency=medium + + * Refer to ifupdown for activating/deactivating network interfaces. +Closes: #975420 + * Let's release for Bullseye. + + -- Holger Wansing Sun, 14 Mar 2021 16:17:33 +0100 + refcard (10.7) unstable; urgency=medium [ Holger Wansing ] * dblatex corrupts visible URL to GPL, since it adds a hyphen at line-break. -Inlcude it in .., to avoid that. +Include it in .., to avoid that. * Correct some wrong line-breaks in translations. * Add Korean translation by sebul . * Add texlive-lang-chinese and -korean as build-depends (additionally needed diff -Nru refcard-10.7/entries.dbk refcard-11.0/entries.dbk --- refcard-10.7/entries.dbk 2020-05-23 10:09:53.0 +0200 +++ refcard-11.0/entries.dbk 2021-03-14 16:17:33.0 +0100 @@ -535,9 +535,9 @@ Interface configuration (if not controlled via network-manager). - - ip link set - device updown + + if updown + device Start, stop network interfaces according to the file above. diff -Nru refcard-10.7/po4a/bg.po refcard-11.0/po4a/bg.po --- refcard-10.7/po4a/bg.po 2020-05-29 13:30:07.0 +0200 +++ refcard-11.0/po4a/bg.po 2021-03-14 16:17:33.0 +0100 @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: refcard 10.0\n" -"POT-Creation-Date: 2020-04-26 12:27+0200\n" +"POT-Creation-Date: 2020-11-27 19:21+0100\n" "PO-Revision-Date: 2020-04-30 18:42+0300\n" "Last-Translator: Kamen Naydenov \n" "Language-Team: Bulgarian \n" @@ -230,7 +230,9 @@ #: entries.dbk:103 msgid "" "E.g. to set up the network w/o DHCP or to adapt bootloader installation." -msgstr "ÐапÑÐ¸Ð¼ÐµÑ Ð·Ð° наÑÑÑойка на мÑежа без DHCP или конÑигÑÑиÑане на заÑеждаÑаÑа пÑогÑама." +msgstr "" +"ÐапÑÐ¸Ð¼ÐµÑ Ð·Ð° наÑÑÑойка на мÑежа без DHCP или конÑигÑÑиÑане на заÑеждаÑаÑа " +"пÑогÑама." #. type: Content of: #: entries.dbk:109 @@ -666,7 +668,7 @@ #: entries.dbk:307 msgid "ln -s file link" msgstr "" -"ln -s име-на-Ñайл име-на-" +"ln -s име-на-Ñайл име-на- " "пÑепÑаÑкаÑа" #. type: Content of: @@ -1122,11 +1124,11 @@ #. type: Content of: #: entries.dbk:539 msgid "" -"ip link set device updown" +"if updown device" msgstr "" -"ip link set инÑеÑÑÐµÐ¹Ñ updown" +"if updown инÑеÑÑейÑ" #. type: Content of: #: entries.dbk:541 @@ -1173,6 +1175,13 @@ msgid "Copy files to other machine (and vice versa)." msgstr "ÐопиÑане на Ñайлове вÑÑÑ Ñ Ð¾ÑдалеÑена маÑина (и обÑаÑноÑо)." +#~ msgid "" +#~ "ip link set device updown" +#~ msgstr "" +#~ "ip link set инÑеÑÑÐµÐ¹Ñ updown" + #~ msgid "/sbin/ip" #~ msgstr "/sbin/ip" diff -Nru refcard-10.7/po4a/ca.po refcard-11.0/po4a/ca.po --- refcard-10.7/po4a/ca.po 2020-05-29 13:30:17.0 +0200 +++ refcard-11.0/po4a/ca.po 2021-03-14 16:17:33.0 +0100 @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: refcard 10.0\n" -"POT-Creation-Date: 2020-04-26 12:27+0200\n" +"POT-Creation-Date: 2020-11-27 19:21+0100\n" "PO-Revision-Date: 2016-05-03 19:46+0200\n" "Last-Translator: Innocent De Marchi \n" "Language-Team: Catalan \n" @@ -1137,11 +1137,11 @@ #. type: Content of: #: entries.dbk:539 msgid "" -"ip link set device updown" +"if updown device" msgstr "" -"ip link set dispositiu updown" +"if updown dispositiu" #. type: Content of: #: entries.dbk:541 @@ -1189,6 +1189,13 @@ msgid "Copy files to other machine (and vice versa)." msgstr "Copia fitxers a una altre ordinador (i a l'inrevés)." +#~ msgid "" +#~ "ip link set device updown" +#~ msgstr "" +#~ "ip link set dispositiu updown" + #~ msgid "/sbin/ip" #~ msgstr "/sbin/ip" diff -Nru refcard-10.7/po4a/cs.po refcard-11.0/po4a/cs.po --- refcard-10.7/po4a/cs.po 2020-05-29 13:30:27.0 +0200 +++ refcard-11.0/po4a/cs.po 2021-03-14 16:17:33.0 +0100 @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: refcard 10.0\n" -"POT-Creation-Date: 2020-04-26 12:27+0200\n" +"POT-Creation-Date: 2020-11-27 19:21+0100\n" "PO-Revision-Date: 2020-05-04 12:01+0200\n" "Last-Translator: Branislav Makúch \n" "Language-Team: Czech \n" @@ -1107,11 +1107,11 @@ #. type: Content of: #: entries.d
Bug#986041: [Debian-med-packaging] Bug#986041: imagej script bug in a system with no swap
Control: tag -1 patch
Greetings Alexis,
Alexis PM, on 2021-03-28 13:50:02 +:
> max_mem=`free | awk 'NR == 2 {fmem=int($2 / 1024); if (fmem < 4000) {print
> fmem} else {print 4000}}'`
> free_mem=`free | awk 'NR == 3 {fmem=int($4 / 1024); if (fmem < 4000) {print
> fmem} else {print 4000}}'`
It seems to me that code parses the former "free" command
format, which looked like the following, to get the available
free memory, disregarding file system cache usage, on line
"-/+ buffers/cache:" and column "free", at the time of the
introduction of the script:
total used free sharedbuffers
cached
Mem: 1000192 465656 534536176 55096
175196
-/+ buffers/cache: 235364 764828
Swap: 1044476 123721032104
While today's "free" output format looks like the following:
totalusedfree shared buff/cache
available
Mem:65876148 803880010920828 5526446916520
57046504
Swap:10485724608 1043964
The equivalent value is now located line "Mem:", column
"available", so in terms of awk, that would translate to the
following:
free_mem=`free | awk 'NR == 2 {fmem=int($7 / 1024); if (fmem < 4000)
{print fmem} else {print 4000}}'`
and:
free_mem=`free | awk 'NR == 2 {fmem=int($7 / 1024); if (fmem < 1800)
{print fmem} else {print 1800}}'`
on the 32 bit branch of the conditional; hence tagging the bug
with patch available.
Many thanks for noticing and reporting the problem!
Have a nice day, :)
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
signature.asc
Description: PGP signature
Bug#986041: imagej script bug in a system with no swap
Package: imagej
Version: 1.52j-1
Severity: important
Hello
In a system with no swap:
$ free
total used free shared buff/cache available
Mem: 508080 56612 69872 368 381596 437904
Swap: 0 0 0
The imagej script:
# max memory allocation is 1800MB on 32bit java and 4000 on 64bit java
elif [[ `uname` == 'Linux' ]] ; then
if [[ `uname -m` == 'x86_64' ]] ; then
java_path="${ij_path}/jre64/bin/java"
max_mem=`free | awk 'NR == 2 {fmem=int($2 / 1024); if (fmem < 4000) {print
fmem} else {print 4000}}'`
free_mem=`free | awk 'NR == 3 {fmem=int($4 / 1024); if (fmem < 4000) {print
fmem} else {print 4000}}'`
mem=${free_mem}/3*2
if (( $mem > $default_mem || $mem < $min_mem )) ; then mem=$default_mem ; fi
else
java_path="${ij_path}/jre/bin/java"
max_mem=`free | awk 'NR == 2 {fmem=int($2 / 1024); if (fmem < 1800) {print
fmem} else {print 1800}}'`
free_mem=`free | awk 'NR == 3 {fmem=int($4 / 1024); if (fmem < 1800) {print
fmem} else {print 1800}}'`
mem=${free_mem}/3*2
if (( $mem > $default_mem || $mem < $min_mem )) ; then mem=$default_mem ; fi
fi
fi
This results in:
java_path = /jre/bin/java
max_mem = 496
free_mem = 0
mem = 0/3*2
Due to the "0" value:
(( 0 > 4000 || 0 < 16 ))
mem=4000
and as the system does not have so much RAM the final result is:
Error occurred during initialization of VM
Could not reserve enough space for 4096000KB object heap
Thank you very much.
Bug#986050: linux-image-5.10.0-0.bpo.3-amd64: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
Package: src:linux Version: 5.10.13-1~bpo10+1 Severity: normal Dear Maintainer, * What led up to the situation? plugged in unplugged network cable after system had booted -- Package-specific info: ** Version: Linux version 5.10.0-0.bpo.3-amd64 (debian-ker...@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-0.bpo.3-amd64 root=UUID=f44239b2-ab75-4ed4-b80c-66a3e3bfdb7c ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: [ 10.145673] bond0: active interface up! [ 10.145721] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 98.468938] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 98.472209] Bridge firewalling registered [ 98.810797] Initializing XFRM netlink socket [ 99.885351] docker0: port 1(vethd1123f1) entered blocking state [ 99.885358] docker0: port 1(vethd1123f1) entered disabled state [ 99.886403] device vethd1123f1 entered promiscuous mode [ 100.235346] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation [ 100.549859] eth0: renamed from vethbfc64a3 [ 100.565530] IPv6: ADDRCONF(NETDEV_CHANGE): vethd1123f1: link becomes ready [ 100.565579] docker0: port 1(vethd1123f1) entered blocking state [ 100.565582] docker0: port 1(vethd1123f1) entered forwarding state [ 100.565642] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready [ 105.367582] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0) [ 105.367585] softdog: soft_reboot_cmd= soft_active_on_boot=0 [ 128.344188] md/raid:md0: device sde operational as raid disk 3 [ 128.344195] md/raid:md0: device sdd operational as raid disk 2 [ 128.344197] md/raid:md0: device sdc operational as raid disk 1 [ 128.344200] md/raid:md0: device sdb operational as raid disk 0 [ 128.346881] md/raid:md0: raid level 5 active with 4 out of 5 devices, algorithm 2 [ 128.439807] md0: detected capacity change from 0 to 32005710413824 [ 128.650465] md: recovery of RAID array md0 [ 454.103857] md: md0: recovery interrupted. [ 454.357959] md0: detected capacity change from 32005710413824 to 0 [ 454.357980] md: md0 stopped. [ 476.791911] md/raid:md0: not clean -- starting background reconstruction [ 476.792000] md/raid:md0: device sdf operational as raid disk 4 [ 476.792003] md/raid:md0: device sde operational as raid disk 3 [ 476.792006] md/raid:md0: device sdd operational as raid disk 2 [ 476.792009] md/raid:md0: device sdc operational as raid disk 1 [ 476.792011] md/raid:md0: device sdb operational as raid disk 0 [ 476.795225] md/raid:md0: raid level 5 active with 5 out of 5 devices, algorithm 2 [ 476.884048] md0: detected capacity change from 0 to 32005710413824 [ 476.894859] md: resync of RAID array md0 [ 2184.661660] perf: interrupt took too long (2510 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [ 2730.638069] RTL8226B_RTL8221B 2.5Gbps PHY r8169-200:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling! [ 2730.638081] r8169 :02:00.0 enp2s0: Link is Up - 100Mbps/Full (downshifted) - flow control off [ 2730.673598] bond0: (slave enp2s0): link status up, enabling it in 200 ms [ 2730.673603] bond0: (slave enp2s0): invalid new link 3 on slave [ 2730.881666] bond0: (slave enp2s0): link status definitely up, 100 Mbps full duplex [ 2741.212653] [ cut here ] [ 2741.212657] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [ 2741.212678] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:443 dev_watchdog+0x246/0x250 [ 2741.212680] Modules linked in: softdog xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_ondemand overlay snd_hda_codec_hdmi intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp nls_ascii nls_cp437 kvm_intel vfat fat kvm irqbypass crc32_pclmul ghash_clmulni_intel i915 snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp snd_sof snd_sof_intel_hda ledtrig_audio snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core snd_compress soundwire_cadence drm_kms_helper snd_hda_codec aesni_intel libaes crypto_simd [ 2741.212740] snd_hda_core cryptd glue_helper cec snd_hwdep rapl soundwire_bus snd_pcm intel_cstate efi_pstore pcspkr ucsi_acpi wdat_wdt drm watchdog evdev mei_me snd_timer typec_ucsi i2c_algo_b
Bug#986051: unblock: krb5/1.18.3-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please review and give pre-approval comments for an upload of krb5.
[ Reason ]
In #985739 it was pointed out that internal symbols disappeared from
libk5crypto.
My bad; I noticed this, confirmed they were not externally visible, approved
the symbols file change, but didn't think about the upgrade implications.
What happens is that if the new libk5crypto3 is unpacked before the
new libkrb5-3, the old libkrb5-3 breaks. In the bug, the user managed
to get into a position where pam_krb5 was broken and logins didn't
work.
So, update the breaks, or add an equals binary:Version depends, no big, right?
While I wasn't looking, krb5 has apparently become part of
pseudo-essential.
login->libpam-modules->libnsl->libtirpc3->libgssapi-krb5-2->libk5crypto3|libkrb5-3
The only reason I even know that is because I've been tracking pam.
Long term, we don't want that.
As a result, it's probably the case in #985739 that pam_unix is broken as well
as pam_krb5.
I'm not really an expert on all the ways that dependency resolution
gets complex for essential packages. I do know that dependencies for
essential packages are supposed to be pre-depends. That's not
currently the case for anything in krb5, or for libkeyutils,
libcomerr-2, etc.
So, we have a few options.
1) Add the breaks. Things are fairly stable in this part of the
dependency graph; it was 2016 when libk5crypto last had an
internally-incompatible break. That will probably work in practice.
On #debian-devel, Adrian Bunk argues that it should be a versioned conflicts
not a break
because it's essential. I'm not sure--I think in most situations the
fact that you cannot unpack the breaking package without deconfiguring
the broken package means that apt will simply reorder things so that
libk5crypto3 comes before libkrb5-3 and all happens to be well with
the breaks.
2) Do we also want to add the pre-depends to krb5. I'm nervous adding
additional pre-depends this late in the process.
3) Do we want to add pre-depends to the entire dependency chain from
libpam-modules to libkeyutils|libcom-err2? I think this is
technically correct, but I am uncomfortable with it.
4) Do we want to do enough surgery to pam to avoid krb5 being
essential. With my pam hat on in January, I concluded it was too late
in the process for me to feel comfortable adequately testing a (not
yet developed) patch. That was before I realized how big of a deal it
might be that krb5 had become essential.
The solution basically involves making pam_unix dlopen its dependencies for nis
rather than link-time dependencies. So, ugly games with c macros or wrappers
trying to get some internally typed NIS APIs right.
I definitely do not have time to develop the patch, although I could
potentially make time to review and help test.
I consider this risky for bullseye.
I think my recommendation is go approve the breaks change, and hope that's good
enough in practice.
[ Tests ] (What automated or manual tests cover the affected code?)
I've done some manual tests to look at how apt tends to resolve
things. I realize that's horribly unreliable because of all the
complex dependencies someone might have.
One thing I have determined is that an = binary:version dependency from
libkrb5-3 to libk5crypto3 tends to make it more likely that apt will
pick the unpack order that breaks things.
[ Checklist ]
[x ] all changes are documented in the d/changelog
[x ] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock krb5/1.18.3-5
diff --git a/debian/changelog b/debian/changelog
index e7224b1253..b0f668489d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+krb5 (1.18.3-5) unstable; urgency=medium
+
+ * Update breaks on libk5crypto3 toward other internal libraries because
+of removed internal symbols, Closes: #985739
+
+ -- Sam Hartman Sun, 28 Mar 2021 13:43:01 -0400
+
krb5 (1.18.3-4) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 55fea8c334..c0e10fe25d 100644
--- a/debian/control
+++ b/debian/control
@@ -352,7 +352,7 @@ Description: MIT Kerberos runtime libraries -
Administration Clients
Package: libk5crypto3
Section: libs
-Breaks: libkrb5-3 (<= 1.8~aa), libgssapi-krb5-2 (<= 1.10+dfsg~alpha1)
+Breaks: libkrb5-3 (<= 1.18~), libgssapi-krb5-2 (<= 1.18~)
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Suggests: krb5-doc, krb5-user
Bug#986052: ITP: r-bioc-qtlizer -- Comprehensive QTL annotation of GWAS results
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: r-bioc-qtlizer Version : 1.4.0+dfsg Upstream Author : Matthias Munz * URL : https://bioconductor.org/packages/Qtlizer/ * License : GPL-3 Programming Lang: R Description : Comprehensive QTL annotation of GWAS results This R package provides access to the Qtlizer web server. Qtlizer annotates lists of common small variants (mainly SNPs) and genes in humans with associated changes in gene expression using the most comprehensive database of published quantitative trait loci (QTLs). I shall maintain this package
Bug#944485: mmdebstrap: please implement the creation of QEMU/KVM images for autopkgtest-virt-qemu
On Sat, 27 Mar 2021 20:15:29 +0100 Johannes Schauer Marin Rodrigues wrote: > Quoting Francesco Poli (2021-03-27 16:18:26) [...] > > I tried to read the relevant section in the mmdebstrap(1) man page, and > > there's some recommendation about an --unshare-helper option. > > > > But to be honest, I failed to understand what I am supposed to do with > > this --unshare-helper option. > > Could you please clarify? > > Quoting from the man page: > > "For correct ownership information, the directory must be accessed from a > user namespace with the right subuid/subgid offset" > > Which part is unclear about that? Thanks for your prompt reply! Well, the problem is probably my total ignorance about unshare, user namespaces, and so forth... First of all, I do not know what exactly subuid and subgid are. I suppose they have something to do with the uid and gid seen from within the namespace (I noticed that the temporary directory was created with high values of uid and gid, not corresponding to any existing user or group). I tried to take a look at some man pages (unshare(1), user_namespaces(7), ...) in order to understand something more, but there seems to be much more information than the basics, and I failed to pinpoint where I can read the bare minimum I need to know... My bad, of course! But anyway, if you know a good reference to a short explanation of the topic (ideally a man page), I would suggest to cite it in the mmdebstrap man page. After that, I can guess that the problem is that, inside the unshared namespace, there's no permission to create/write files in my ~/Downloads directory. But what is not clear to me is what I am supposed to do with this problem. What would you suggest? -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpEOQrhSgC3a.pgp Description: PGP signature
Bug#986053: brltty: Please enable Java support on m68k
Source: brltty Version: 6.3+dfsg-1 Severity: normal User: debian-...@lists.debian.org Usertags: m68k X-Debbugs-Cc: debian-...@lists.debian.org Hello! While working on fixing brltty on ia64, I noticed that the package still disables Java support on m68k. Since Java works without any problems on m68k, it should just be enabled there as well. I verified that removing "m68k" from debian/control and debian/rules at the appropriate lines lets me build the package with Java support on m68k without any problems: glaubitz@epyc:..glaubitz/brltty> ls -l *jni* -rw-r--r-- 1 glaubitz edvf 91192 Mar 28 19:59 libbrlapi-jni_6.3+dfsg-1_m68k.deb -rw-r--r-- 1 glaubitz edvf 39516 Mar 28 19:59 libbrlapi-jni-dbgsym_6.3+dfsg-1_m68k.deb glaubitz@epyc:..glaubitz/brltty> Although there is no -java package being built. Not sure why. It should work in any case. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#986053: brltty: Please enable Java support on m68k
John Paul Adrian Glaubitz, le dim. 28 mars 2021 20:30:32 +0200, a ecrit: > Although there is no -java package being built. Not sure why. It should work > in any case. The -java package is arch:all :) Applied, thanks! Samuel
Bug#944485: mmdebstrap: please implement the creation of QEMU/KVM images for autopkgtest-virt-qemu
Quoting Francesco Poli (2021-03-28 20:24:12) > Well, the problem is probably my total ignorance about unshare, user > namespaces, and so forth... > > First of all, I do not know what exactly subuid and subgid are. man subuid? ;) > I suppose they have something to do with the uid and gid seen from > within the namespace (I noticed that the temporary directory was > created with high values of uid and gid, not corresponding to any > existing user or group). Correct. So if some directory on the path of your $TMPDIR is not accessible by that user with the very high uid/gid, then it obviously cannot create the chroot directory. > I tried to take a look at some man pages (unshare(1), > user_namespaces(7), ...) in order to understand something more, but > there seems to be much more information than the basics, and I failed > to pinpoint where I can read the bare minimum I need to know... > My bad, of course! > But anyway, if you know a good reference to a short explanation of the > topic (ideally a man page), I would suggest to cite it in the > mmdebstrap man page. Unfortunately, I do not know of such a reference. All I learned to add unshare support to mmdebstrap was from reading source code of other tools. :( > After that, I can guess that the problem is that, inside the unshared > namespace, there's no permission to create/write files in my > ~/Downloads directory. Or one of its parent. You also need more than write access. You also need read access. And directories need to be executable. > But what is not clear to me is what I am supposed to do with this > problem. > > What would you suggest? Your whole problem started because you decided to deviate from the default and chose a different TMPDIR. If you use custom options, then you should know what you are doing. If you don't set TMPDIR, then it will work. If you do set TMPDIR, then you have to make sure that whatever path TMPDIR points to is setup in a way that the unshared user is able to access it and write stuff into it. Thanks! cheers, josch signature.asc Description: signature
Bug#986050: linux-image-5.10.0-0.bpo.3-amd64: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
Control: tags -1 + moreinfo Hi, On Sun, Mar 28, 2021 at 01:55:27PM -0400, jorges wrote: > Package: src:linux > Version: 5.10.13-1~bpo10+1 > Severity: normal > > Dear Maintainer, > > >* What led up to the situation? >plugged in unplugged network cable after system had booted > > > -- Package-specific info: > ** Version: > Linux version 5.10.0-0.bpo.3-amd64 (debian-ker...@lists.debian.org) (gcc-8 > (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP > Debian 5.10.13-1~bpo10+1 (2021-02-11) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-5.10.0-0.bpo.3-amd64 > root=UUID=f44239b2-ab75-4ed4-b80c-66a3e3bfdb7c ro quiet > > ** Tainted: W (512) > * kernel issued warning > > ** Kernel log: > [ 10.145673] bond0: active interface up! > [ 10.145721] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready > [ 98.468938] bridge: filtering via arp/ip/ip6tables is no longer available > by default. Update your scripts to load br_netfilter if you need this. > [ 98.472209] Bridge firewalling registered > [ 98.810797] Initializing XFRM netlink socket > [ 99.885351] docker0: port 1(vethd1123f1) entered blocking state > [ 99.885358] docker0: port 1(vethd1123f1) entered disabled state > [ 99.886403] device vethd1123f1 entered promiscuous mode > [ 100.235346] cgroup: cgroup: disabling cgroup2 socket matching due to > net_prio or net_cls activation > [ 100.549859] eth0: renamed from vethbfc64a3 > [ 100.565530] IPv6: ADDRCONF(NETDEV_CHANGE): vethd1123f1: link becomes ready > [ 100.565579] docker0: port 1(vethd1123f1) entered blocking state > [ 100.565582] docker0: port 1(vethd1123f1) entered forwarding state > [ 100.565642] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready > [ 105.367582] softdog: initialized. soft_noboot=0 soft_margin=60 sec > soft_panic=0 (nowayout=0) > [ 105.367585] softdog: soft_reboot_cmd= > soft_active_on_boot=0 > [ 128.344188] md/raid:md0: device sde operational as raid disk 3 > [ 128.344195] md/raid:md0: device sdd operational as raid disk 2 > [ 128.344197] md/raid:md0: device sdc operational as raid disk 1 > [ 128.344200] md/raid:md0: device sdb operational as raid disk 0 > [ 128.346881] md/raid:md0: raid level 5 active with 4 out of 5 devices, > algorithm 2 > [ 128.439807] md0: detected capacity change from 0 to 32005710413824 > [ 128.650465] md: recovery of RAID array md0 > [ 454.103857] md: md0: recovery interrupted. > [ 454.357959] md0: detected capacity change from 32005710413824 to 0 > [ 454.357980] md: md0 stopped. > [ 476.791911] md/raid:md0: not clean -- starting background reconstruction > [ 476.792000] md/raid:md0: device sdf operational as raid disk 4 > [ 476.792003] md/raid:md0: device sde operational as raid disk 3 > [ 476.792006] md/raid:md0: device sdd operational as raid disk 2 > [ 476.792009] md/raid:md0: device sdc operational as raid disk 1 > [ 476.792011] md/raid:md0: device sdb operational as raid disk 0 > [ 476.795225] md/raid:md0: raid level 5 active with 5 out of 5 devices, > algorithm 2 > [ 476.884048] md0: detected capacity change from 0 to 32005710413824 > [ 476.894859] md: resync of RAID array md0 > [ 2184.661660] perf: interrupt took too long (2510 > 2500), lowering > kernel.perf_event_max_sample_rate to 79500 > [ 2730.638069] RTL8226B_RTL8221B 2.5Gbps PHY r8169-200:00: Downshift occurred > from negotiated speed 1Gbps to actual speed 100Mbps, check cabling! > [ 2730.638081] r8169 :02:00.0 enp2s0: Link is Up - 100Mbps/Full > (downshifted) - flow control off > [ 2730.673598] bond0: (slave enp2s0): link status up, enabling it in 200 ms > [ 2730.673603] bond0: (slave enp2s0): invalid new link 3 on slave > [ 2730.881666] bond0: (slave enp2s0): link status definitely up, 100 Mbps > full duplex > [ 2741.212653] [ cut here ] > [ 2741.212657] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out > [ 2741.212678] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:443 > dev_watchdog+0x246/0x250 > [ 2741.212680] Modules linked in: softdog xt_nat xt_tcpudp veth xt_conntrack > xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype > iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 > br_netfilter bridge stp llc cpufreq_conservative cpufreq_userspace > cpufreq_powersave cpufreq_ondemand overlay snd_hda_codec_hdmi intel_rapl_msr > intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic > x86_pkg_temp_thermal intel_powerclamp coretemp nls_ascii nls_cp437 kvm_intel > vfat fat kvm irqbypass crc32_pclmul ghash_clmulni_intel i915 snd_sof_pci > snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common > snd_sof_xtensa_dsp snd_sof snd_sof_intel_hda ledtrig_audio snd_soc_skl > snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp > snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg > soundwire_intel soundwire_generic_allocation snd_soc_core snd_compress
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#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 a
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&suite=unstable Regards, Daniel
Bug#986055: arm-trusted-firmware: Drop unused shlibs:Depends debhelper variable from firmware package
Source: arm-trusted-firmware
Version: 2.4+dfsg-2
Severity: minor
Tags: patch
A patch is attached.
>From 75ff5236c8640f560eaa3defc22756dd98364d66 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez
Date: Sun, 28 Mar 2021 10:21:07 +0200
Subject: [PATCH 3/7] Drop unused shlibs:Depends debhelper variable from
firmware package
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 094557463..cd2521c47 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Vcs-Git: https://salsa.debian.org/debian/arm-trusted-firmware.git -b debian/mast
Package: arm-trusted-firmware
Architecture: arm64
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}
Breaks: u-boot-rockchip (<< 2020.01~rc5)
Description: "secure world" software for ARM SoCs - firmware
The "secure world" on arm64 machines is a special level of CPU
--
2.30.2
Bug#986056: arm-trusted-firmware: please add lintian override for non-linux firmware
Source: arm-trusted-firmware Version: 2.4+dfsg-2 Severity: minor Tags: patch A trivial patch is attached. >From febc5b24553db9b7eadc95e0a6c81e739da1a9a5 Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Sun, 28 Mar 2021 12:46:59 +0200 Subject: [PATCH 6/7] Lintian override for non-linux firmware --- debian/arm-trusted-firmware.lintian-overrides | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/arm-trusted-firmware.lintian-overrides b/debian/arm-trusted-firmware.lintian-overrides index 1eb070ae5..40c67b616 100644 --- a/debian/arm-trusted-firmware.lintian-overrides +++ b/debian/arm-trusted-firmware.lintian-overrides @@ -1,2 +1,5 @@ # This is boot firmware that needs to be statically linked. arm-trusted-firmware binary: statically-linked-binary usr/lib/arm-trusted-firmware/*/bl31.elf + +# Intended for U-Boot, not linux. +wrong-section-according-to-package-name arm-trusted-firmware => kernel -- 2.30.2
Bug#986057: arm-trusted-firmware: rk3399 fails to cross build
Source: arm-trusted-firmware Severity: normal Tags: patch With the attached patch, the cross build succeeds. I am not sure how this relates to #960166. >From fd44befa16a28b60e15ba9a8e00fd75a854e9d68 Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Sun, 28 Mar 2021 15:52:24 +0200 Subject: Fix dependencies allowing cross build of rk3399 diff --git a/debian/control b/debian/control index cd2521c47..6deea90d9 100644 --- a/debian/control +++ b/debian/control @@ -4,8 +4,8 @@ Priority: optional Maintainer: Vagrant Cascadian Standards-Version: 4.5.1 Build-Depends: debhelper-compat (= 13), - gcc-arm-none-eabi [arm64], - binutils-arm-none-eabi [arm64], + gcc-arm-none-eabi:native [arm64], + binutils-arm-none-eabi:native [arm64], libssl-dev , Rules-Requires-Root: no Homepage: https://www.trustedfirmware.org/
Bug#986058: arm-trusted-firmware: tools fail to cross build
Source: arm-trusted-firmware Version: 2.4+dfsg-2 Severity: normal Tags: patch Hello. Dpkg-architecture and debhelper set the conventional CC. tools/*/Makefile use HOSTCC instead. The attached patch sets the compiler even for native builds, this does not hurt. >From 4c42e4b2d5cc3642515317427b6612f4887e02e5 Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Sun, 28 Mar 2021 10:29:56 +0200 Subject: [PATCH 4/7] Fix cross build of tools by setting HOSTCC from CC Dpkg-architecture and debhelper set the conventional CC. tools/*/Makefile use HOSTCC instead. Set the compiler even for native builds, this does not hurt. --- debian/rules | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/debian/rules b/debian/rules index b85f6e3fb..b7fd8ac7e 100755 --- a/debian/rules +++ b/debian/rules @@ -1,6 +1,7 @@ #!/usr/bin/make -f include /usr/share/dpkg/architecture.mk +include /usr/share/dpkg/buildtools.mk export DH_VERBOSE=1 export TF_CFLAGS += -ffile-prefix-map=$(CURDIR)=. @@ -18,8 +19,8 @@ endif override_dh_auto_build: # Disable building of arm-trusted-firmware-tools ifeq ($(filter pkg.arm-trusted-firmware.notools,$(DEB_BUILD_PROFILES)),) - dh_auto_build --sourcedir=tools/fiptool -- DEBUG=1 V=$(VERBOSE) HOSTCCFLAGS="$(CFLAGS) $(CPPFLAGS)" - dh_auto_build --sourcedir=tools/cert_create -- DEBUG=1 V=$(VERBOSE) HOSTCCFLAGS="$(CFLAGS) $(CPPFLAGS) -std=c99 -DUSE_TBBR_DEFS=1" + dh_auto_build --sourcedir=tools/fiptool -- DEBUG=1 V=$(VERBOSE) HOSTCC=$(CC) HOSTCCFLAGS="$(CFLAGS) $(CPPFLAGS)" + dh_auto_build --sourcedir=tools/cert_create -- DEBUG=1 V=$(VERBOSE) HOSTCC=$(CC) HOSTCCFLAGS="$(CFLAGS) $(CPPFLAGS) -std=c99 -DUSE_TBBR_DEFS=1" endif # Only build firmware on arm64. ifeq ($(DEB_HOST_ARCH),arm64) -- 2.30.2
Bug#979278: arm-trusted-firmware: Make each command run by Make visible in the build log
Source: arm-trusted-firmware Followup-For: Bug #979278 Please use this version instead... >From fcd113c7c7df92e4e32c2ec5c82118e04a7f58ca Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Sun, 28 Mar 2021 12:45:16 +0200 Subject: [PATCH 5/7] Make each command run by Make visible in the build log The information flow is easyer to understand in named Make variables than in shell pipes or executable debhelper configurations. Also, errors are handled properly. For example, chmod is currently emitting an error message in the amd64 logs (of course, *this* error can be ignored). --- debian/arm-trusted-firmware.install | 9 + debian/rules| 10 +++--- debian/targets | 6 -- 3 files changed, 8 insertions(+), 17 deletions(-) mode change 100755 => 100644 debian/arm-trusted-firmware.install delete mode 100644 debian/targets diff --git a/debian/arm-trusted-firmware.install b/debian/arm-trusted-firmware.install old mode 100755 new mode 100644 index e8c531430..81ddcb861 --- a/debian/arm-trusted-firmware.install +++ b/debian/arm-trusted-firmware.install @@ -1,8 +1 @@ -#!/bin/sh - -grep -v '^#' debian/targets | while read plat targets ; do - for target in $targets ; do - chmod a-x build/$plat/debug/$target - echo build/$plat/debug/$target usr/lib/arm-trusted-firmware/$plat/ - done -done +build/renamed/* usr/lib/arm-trusted-firmware diff --git a/debian/rules b/debian/rules index b7fd8ac7e..7a6884a2e 100755 --- a/debian/rules +++ b/debian/rules @@ -13,6 +13,9 @@ else VERBOSE=1 endif +platforms := g12a gxbb sun50i_a64 sun50i_h6 rk3328 rk3399 +target = $(if $(filter rk3328 rk3399,$@),bl31/bl31.elf,bl31.bin) + %: dh $@ @@ -24,10 +27,11 @@ ifeq ($(filter pkg.arm-trusted-firmware.notools,$(DEB_BUILD_PROFILES)),) endif # Only build firmware on arm64. ifeq ($(DEB_HOST_ARCH),arm64) + override_dh_auto_build: $(platforms) + $(platforms): # Always set CROSS_COMPILE, which also works for native builds. - grep -v '^#' debian/targets | while read plat targets ; do \ - CROSS_COMPILE=aarch64-linux-gnu- CFLAGS= LDFLAGS= dh_auto_build -- V=$(VERBOSE) DEBUG=1 PLAT=$$plat bl31 ; \ - done + CROSS_COMPILE=aarch64-linux-gnu- CFLAGS= LDFLAGS= dh_auto_build -- V=$(VERBOSE) DEBUG=1 PLAT=$@ bl31 + install -m644 build/$@/debug/$(target) -Dt build/renamed/$@ endif override_dh_installchangelogs: diff --git a/debian/targets b/debian/targets deleted file mode 100644 index a6f72441c..0 --- a/debian/targets +++ /dev/null @@ -1,6 +0,0 @@ -g12a bl31.bin -gxbb bl31.bin -sun50i_a64 bl31.bin -sun50i_h6 bl31.bin -rk3328 bl31/bl31.elf -rk3399 bl31/bl31.elf -- 2.30.2
Bug#986059: arm-trusted-firmware: Read DEB_HOST_ARCH from /usr/share/architecture.mk instead of environment
Source: arm-trusted-firmware Version: debian/2.4+dfsg-2 Severity: minor Tags: patch Requiring this variable prevents direct calls to debian/rules, see dpkg-architecture(1). >From fdb1ed526d23fbfc819398898ce1e8036f8fdc5b Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Sun, 28 Mar 2021 09:47:35 +0200 Subject: [PATCH 1/7] Read DEB_HOST_ARCH from /usr/share/architecture.mk instead of environment Requiring this variable prevents direct calls to debian/rules, see dpkg-architecture(1). --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index a8e1f93af..b85f6e3fb 100755 --- a/debian/rules +++ b/debian/rules @@ -1,4 +1,7 @@ #!/usr/bin/make -f + +include /usr/share/dpkg/architecture.mk + export DH_VERBOSE=1 export TF_CFLAGS += -ffile-prefix-map=$(CURDIR)=. -- 2.30.2
Bug#985488: New debdiff for pinball 0.3.20201218-3
Control: tags -1 moreinfo Hi, On 25-03-2021 15:04, Yadd wrote: > Philippe added an autopkgtest to pinball. The autopkgtest doesn't test the installed binaries substantially. It must be marked as superficial. When that is fixed (and nothing else is changed along the way), it can be unblocked. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#940021: #940021: systemd: socket activiation leads to OOM situation due to slices not getting cleaned up
I've tried to reproduce this again with systemd 247.3-1~bpo10+1, but couldn't. Thanks, Chris
Bug#940021: #940021: systemd: socket activiation leads to OOM situation due to slices not getting cleaned up
Am 28.03.2021 um 23:07 schrieb Chris Hofstaedtler: I've tried to reproduce this again with systemd 247.3-1~bpo10+1, but couldn't. Thanks a lot for checking, Chris. Regards, Michael
Bug#959469: buster-pu: package openssl/1.1.1g-1
On 2021-03-22 19:52:00 [+0100], To Kurt Roeckx wrote: > > I will prepare 1.1.1k for unstable, do buster-security based on > > 1.1.1d-0+deb10u5 and then come back with an updated pu :) New round. I prepared a pu for Buster based on OpenSSL 1.1.1k. The unstable release migrated to testing. I am not aware of any regressions so far. Please find attached a diff against the last proposed pu, based on 1.1.1j. I will also reply to this mail with a diff against the current version in buster-pu. Sebastian diff --git a/CHANGES b/CHANGES index 1ab64b35c9a48..7d0129e687652 100644 --- a/CHANGES +++ b/CHANGES @@ -7,6 +7,50 @@ https://github.com/openssl/openssl/commits/ and pick the appropriate release branch. + Changes between 1.1.1j and 1.1.1k [25 Mar 2021] + + *) Fixed a problem with verifying a certificate chain when using the + X509_V_FLAG_X509_STRICT flag. This flag enables additional security checks + of the certificates present in a certificate chain. It is not set by + default. + + Starting from OpenSSL version 1.1.1h a check to disallow certificates in + the chain that have explicitly encoded elliptic curve parameters was added + as an additional strict check. + + An error in the implementation of this check meant that the result of a + previous check to confirm that certificates in the chain are valid CA + certificates was overwritten. This effectively bypasses the check + that non-CA certificates must not be able to issue other certificates. + + If a "purpose" has been configured then there is a subsequent opportunity + for checks that the certificate is a valid CA. All of the named "purpose" + values implemented in libcrypto perform this check. Therefore, where + a purpose is set the certificate chain will still be rejected even when the + strict flag has been used. A purpose is set by default in libssl client and + server certificate verification routines, but it can be overridden or + removed by an application. + + In order to be affected, an application must explicitly set the + X509_V_FLAG_X509_STRICT verification flag and either not set a purpose + for the certificate verification or, in the case of TLS client or server + applications, override the default purpose. + (CVE-2021-3450) + [Tomáš Mráz] + + *) Fixed an issue where an OpenSSL TLS server may crash if sent a maliciously + crafted renegotiation ClientHello message from a client. If a TLSv1.2 + renegotiation ClientHello omits the signature_algorithms extension (where + it was present in the initial ClientHello), but includes a + signature_algorithms_cert extension then a NULL pointer dereference will + result, leading to a crash and a denial of service attack. + + A server is only vulnerable if it has TLSv1.2 and renegotiation enabled + (which is the default configuration). OpenSSL TLS clients are not impacted + by this issue. + (CVE-2021-3449) + [Peter Kästle and Samuel Sapalski] + Changes between 1.1.1i and 1.1.1j [16 Feb 2021] *) Fixed the X509_issuer_and_serial_hash() function. It attempts to diff --git a/Configurations/unix-Makefile.tmpl b/Configurations/unix-Makefile.tmpl index 3a24d551359bd..41648c952667f 100644 --- a/Configurations/unix-Makefile.tmpl +++ b/Configurations/unix-Makefile.tmpl @@ -917,8 +917,8 @@ ERROR_REBUILD= done ) ordinals: - ( b=`pwd`; cd $(SRCDIR); $(PERL) -I$$b util/mkdef.pl crypto update ) - ( b=`pwd`; cd $(SRCDIR); $(PERL) -I$$b util/mkdef.pl ssl update ) + $(PERL) $(SRCDIR)/util/mkdef.pl crypto update + $(PERL) $(SRCDIR)/util/mkdef.pl ssl update test_ordinals: ( cd test; \ diff --git a/NEWS b/NEWS index 3cce525066457..05991a0c214a9 100644 --- a/NEWS +++ b/NEWS @@ -5,6 +5,14 @@ This file gives a brief overview of the major changes between each OpenSSL release. For more details please read the CHANGES file. + Major changes between OpenSSL 1.1.1j and OpenSSL 1.1.1k [25 Mar 2021] + + o Fixed a problem with verifying a certificate chain when using the +X509_V_FLAG_X509_STRICT flag (CVE-2021-3450) + o Fixed an issue where an OpenSSL TLS server may crash if sent a +maliciously crafted renegotiation ClientHello message from a client +(CVE-2021-3449) + Major changes between OpenSSL 1.1.1i and OpenSSL 1.1.1j [16 Feb 2021] o Fixed a NULL pointer deref in the X509_issuer_and_serial_hash() diff --git a/README b/README index da5629f92c819..b92a8bd3a4b59 100644 --- a/README +++ b/README @@ -1,7 +1,7 @@ - OpenSSL 1.1.1j 16 Feb 2021 + OpenSSL 1.1.1k 25 Mar 2021 - Copyright (c) 1998-2020 The OpenSSL Project + Copyright (c) 1998-2021 The OpenSSL Project Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson All rights reserved. diff --git a/apps/s_cb.c b/apps/s_cb.c index 6406ddfb9e1b2..dee1b2e5b4f65 100644 --- a/apps/s_cb.c +++ b/apps/s_cb.c @@ -1,5 +1,5 @@ /* - * Copyright 1995-2020 The OpenSSL Project Au
Bug#960893: libc++-10-dev: Can't coinstall multiple libc++-dev versions
Hello, just some simple ideas: 1) One way would be to replace the explicit symlinks in /usr/lib/$triplet with alternatives. For instance, in a postinst.in update-alternatives --install /usr/lib/@DEB_HOST_MULTIARCH@/libc++.so libc++.so-@DEB_HOST_MULTIARCH@ /usr/lib/llvm-@VERSION_MAJOR@/lib/libc++.so @VERSION_MAJOR@ --slave /usr/lib/@DEB_HOST_MULTIARCH@/libc++.a libc++.a-@DEB_HOST_MULTIARCH@ /usr/lib/llvm-@VERSION_MAJOR@/lib/libc++.a + the corresponding remove in prerm.in and corresponding sed line in rules (see for instance the package "lapack"). And others for libc++.so.1, libc++abi.so, libc++abi.so.1, maybe more (libomp5?). Using the major version number as priority makes sense to me, but it could also be major*100 for regular toolchains and just major for snapshots or whatever. 2) Imitate gcc, where all the gcc-X packages produce / use libstdc++6 (no version), so we end up with only the most recent one installed. 3) Move the symlinks to the unversioned packages, libc++1-11 would provide the files in /usr/lib/llvm-11/lib, and libc++1 would provide the symlink in /usr/lib/$triplet. And I am sure there are many possible variations, for instance changing the granularity of the choice (just a symlink /usr/lib/llvm to /usr/lib/llvm-11?) If we look at the output of clang++ -v when linking, there is -L/usr/lib/llvm-11/lib, but it comes after -L/usr/lib/$triplet, so even for ideas 1 and 3 and even for static linking, this would end up linking with the default version, as if we had gone with idea 2. I don't know if that's deliberate or a bug. -- Marc Glisse
Bug#986061: libxerces2-java: Internationalization messages missing
Package: libxerces2-java Version: 2.12.0-1 Severity: normal Dear Maintainer, In /org/apache/xerces/impl/msg there are only message files in English and not in other languages. -- System Information: Debian Release: 10.9 APT prefers stable APT policy: (900, 'stable'), (800, 'unstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libxerces2-java depends on: ii libxml-commons-external-java 1.4.01-3 ii libxml-commons-resolver1.1-java 1.2-9 libxerces2-java recommends no packages. Versions of packages libxerces2-java suggests: pn libxerces2-java-doc -- no debconf information
Bug#986062: unblock: libusb-1.0/2:1.0.24-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libusb-1.0 version 1.0.24-3.
[ Reason ]
libusb-1.0 version 1.0.24-3 fixes an issue introduced in upstream
version 1.0.24, and preventing some buggy USB devices to work (see
#985723 for details). The fix consists in a backport of the upstream
commit. At least one of the affected USB device is commonly found in
Dell Latitude laptops.
[ Impact ]
Broadcom BCM5880 internal card reader, commonly found in Dell Latitude
laptops, stop working after an upgrade from Buster to Bullseye. Other
devices might be affected, although less common.
[ Tests ]
As the issue is related to hardware, this is not covered by autopkgtest.
It has been confirmed that version 1.0.24-3 fixes the issue with the
Broadcom BCM5880 internal card reader. In addition, I have personally
tested that this new version doesn't break any of the USB devices I
have. It has been in sid for one week without bug reported. In addition
this patch has already been backported in other distributions, at least
Fedora and Alpine.
[ Risks ]
This a package installed on most systems, however the changes are
relatively simple and basically consist in removing checks for buggy
hardware that have been added during code refactoring done in version
1.0.24.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
None
unblock libusb-1.0/2:1.0.24-3
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libusb-1.0-1.0.24/debian/changelog libusb-1.0-1.0.24/debian/changelog
--- libusb-1.0-1.0.24/debian/changelog 2020-12-14 06:54:15.0 +0100
+++ libusb-1.0-1.0.24/debian/changelog 2021-03-22 22:41:50.0 +0100
@@ -1,3 +1,10 @@
+libusb-1.0 (2:1.0.24-3) unstable; urgency=medium
+
+ * Backport patch from upstream to gracefully handle buggy (but very common)
+devices with a configuration 0 (closes: #985723).
+
+ -- Aurelien Jarno Mon, 22 Mar 2021 22:41:50 +0100
+
libusb-1.0 (2:1.0.24-2) unstable; urgency=medium
* Backport patch from upstream to fix parsing of descriptors for
diff -Nru
libusb-1.0-1.0.24/debian/patches/02-linux_usbfs-Gracefully-handle-buggy-devices-with-a-c.patch
libusb-1.0-1.0.24/debian/patches/02-linux_usbfs-Gracefully-handle-buggy-devices-with-a-c.patch
---
libusb-1.0-1.0.24/debian/patches/02-linux_usbfs-Gracefully-handle-buggy-devices-with-a-c.patch
1970-01-01 01:00:00.0 +0100
+++
libusb-1.0-1.0.24/debian/patches/02-linux_usbfs-Gracefully-handle-buggy-devices-with-a-c.patch
2021-03-22 22:40:30.0 +0100
@@ -0,0 +1,217 @@
+From f38f09da98acc63966b65b72029b1f7f81166bef Mon Sep 17 00:00:00 2001
+From: Chris Dickens
+Date: Mon, 8 Feb 2021 11:56:13 -0800
+Subject: [PATCH] linux_usbfs: Gracefully handle buggy devices with a
+ configuration 0
+
+The USB spec states that a configuration value of 0 is reserved and is
+used to indicate the device in not configured (e.g. is in the address
+state). Unfortunately some devices do exist that violate this and use 0
+as the bConfigurationValue of the configuration descriptor.
+
+Improve how the Linux backend handles such non-conformant devices by
+adding special handling around the configuration value 0. Most devices
+will not require this special handling, but for those that do there is
+no way to distinguish between the device being unconfigured and using
+configuration 0.
+
+Closes #850
+
+Signed-off-by: Chris Dickens
+---
+ libusb/os/linux_usbfs.c | 94 ++---
+ libusb/version_nano.h | 2 +-
+ 2 files changed, 60 insertions(+), 36 deletions(-)
+
+diff --git a/libusb/os/linux_usbfs.c b/libusb/os/linux_usbfs.c
+index ebf8cfe..3a1894c 100644
+--- a/libusb/os/linux_usbfs.c
b/libusb/os/linux_usbfs.c
+@@ -128,7 +128,7 @@ struct linux_device_priv {
+ void *descriptors;
+ size_t descriptors_len;
+ struct config_descriptor *config_descriptors;
+- uint8_t active_config; /* cache val for !sysfs_available */
++ int active_config; /* cache val for !sysfs_available */
+ };
+
+ struct linux_device_handle_priv {
+@@ -169,6 +169,21 @@ struct linux_transfer_priv {
+ int iso_packet_offset;
+ };
+
++static int dev_has_config0(struct libusb_device *dev)
++{
++ struct linux_device_priv *priv = usbi_get_device_priv(dev);
++ struct config_descriptor *config;
++ uint8_t idx;
++
++ for (idx = 0; idx < dev->device_desc
Bug#985488: New debdiff for pinball 0.3.20201218-3
Control: tags -1 - moreinfo Le 28/03/2021 à 22:24, Paul Gevers a écrit : > Control: tags -1 moreinfo > > Hi, > > On 25-03-2021 15:04, Yadd wrote: >> Philippe added an autopkgtest to pinball. > > The autopkgtest doesn't test the installed binaries substantially. It > must be marked as superficial. > > When that is fixed (and nothing else is changed along the way), it can > be unblocked. Hi Paul, thanks! Done in 0.3.20201218-4 Cheers, Xavier
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#985928: Sound issues with the 5.10.x kernel (alsa)
Hi Stefan, thank you for your response. > i assume you set this option in the config.txt? This shouldn't have any > affect for the mainline kernel / DT. I am aware of that... I did "snd_bcm2835 enable_hdmi=0" in /etc/modules. "modinfo snd_bcm2835" shows as below. Doesn't it indicate snd_bcm2835 having an option enable_hdmi??? It seems that the contention of grabbing HDMI audio output between vc4.ko and snd_bcm2835.ko can be addressed if snd_bcm2835.ko honors the option enable_hdmi with its default =0, but currently enable_hdmi seems having no effect in behavior of snd_bcm2835... # modinfo snd_bcm2835 filename: /lib/modules/5.10.0-5-rt-arm64/kernel/drivers/staging/vc04_services/bcm2835-audio/snd-bcm2835.ko alias: platform:bcm2835_audio license:GPL description:Alsa driver for BCM2835 chip author: Dom Cobley depends:snd-pcm,vchiq,snd staging:Y intree: Y name: snd_bcm2835 vermagic: 5.10.0-5-rt-arm64 SMP preempt_rt mod_unload modversions aarch64 sig_id: PKCS#7 signer: Debian Secure Boot CA sig_key:4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C sig_hashalgo: sha256 signature: omitted, too long. parm: force_bulk:Force use of vchiq bulk for audio (bool) parm: enable_hdmi:Enables HDMI virtual audio device (bool) parm: enable_headphones:Enables Headphones virtual audio device (bool) parm: enable_compat_alsa:Enables ALSA compatibility virtual audio device (bool) parm: num_channels:Number of audio channels (default: 8) (int) Best regards, Ryutaroh
Bug#978025: Sound issues with the 5.10.x kernel (alsa)
>> i assume you set this option in the config.txt? This shouldn't have any >> affect for the mainline kernel / DT. > I am aware of that... I include my config.txt on RPi4B for reference... arm_64bit=1 enable_uart=1 upstream_kernel=1 kernel=vmlinuz-5.10.0-5-rt-arm64 initramfs initrd.img-5.10.0-5-rt-arm64 disable_fw_kms_setup=1 disable_overscan=1 hdmi_enable_4kp60=1 Best regards, Ryutaroh Matsumoto
Bug#939405: ITP: waypipe -- Proxy wayland clients over a single socket
> Upstream considers the software to be unstable right now As of the most recent version (v0.8.0), I no longer consider Waypipe to be unstable. Also, the project URL should now be: https://gitlab.freedesktop.org/mstoeckl/waypipe/ . I recently received a pull request on the topic of Debian packaging; while it was out of scope for the project itself, it may be of interest to those watching this bug. https://gitlab.freedesktop.org/mstoeckl/waypipe/-/merge_requests/14
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#986042: texlive-base: Post-installation script fails with exit status 1
On Sun, 28 Mar 2021, Shayan Doust wrote: > Running "dpkg-reconfigure libpaper1" again, and then trying again for > texlive-base, spits out the > same issue I've reported. Interesting, I don't see that in my case ... $ pkg-reconfigure libpaper1 Replacing config file /etc/papersize with new version tl-paper: setting paper size for context to letter: /var/lib/texmf/tex/context/user/cont-sys-paper.tex tl-paper: setting paper size for dvipdfmx to letter: /var/lib/texmf/dvipdfmx/dvipdfmx-paper.cfg tl-paper: setting paper size for dvips to letter: /var/lib/texmf/dvips/config/config-paper.ps tl-paper: setting paper size for pdftex to letter: /var/lib/texmf/tex/generic/tex-ini-files/pdftexconfig.tex tl-paper: setting paper size for xdvi to letter: /var/lib/texmf/xdvi/XDvi-paper Running mktexlsr. This may take some time... done. Building format(s) --refresh. This may take some time... ... $ Can you please do for i in xdvi|pdftex|dvips|dvipdfmx|context ; do echo "=== $i ===" tl-paper get $i done and send the output? And then we continue debugging. It fails in tl-paper get $prg calls and thus it seems something in your configurations files for one of these programs (or all) seem to be broken. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#983583: FTBFS on mips64el and mipsel
Shengjing Zhu 于2021年3月28日周日 上午12:12写道： > > Control: reopen -1 > Control: severity -1 important > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk wrote: > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote: > > > Source: golang-github-sylabs-sif > > > Version: 1.0.9-2 > > > Severity: serious > > > X-Debbugs-Cc: z...@debian.org > > > > > > Tried 3 times on buildd and failed at same test. > > > > > > === RUN TestAddDelObject > > > unexpected fault address 0xffc8a0c000 > > > fatal error: fault > > > [signal SIGSEGV: segmentation violation code=0x2 addr=0xffc8a0c000 > > > pc=0x12007ebe4] > > > > > > goroutine 22 [running]: > > > runtime.throw(0x1201b74ed, 0x5) > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c fp=0xce3430 > > > sp=0xce3408 pc=0x120040afc > > > runtime.sigpanic() > > > > > > Since it has been built on mipsx before, the failure will cause it > > > impossible > > > to fix issue later on these arch. > > > > > > It should either be removed from these arch or get fixed. > > > > This appears to be fixed now: > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif > > The difference between these builds, seems to be a 5.10 kernel and > 4.19 kernel on buildd. > > I'll reopen this but downgrade the severity, and loop debian-mips@ to > see if it's regression on the kernel side. > And the CPUs are different: Cavium for good and Loongson3A3000 is bad. > -- > Shengjing Zhu > -- YunQiang Su
Bug#986007: Merge request to close this bug
Hi, Sorry, I have not had time for this in a while (and things are not looking good in the near future). I have granted the debian group commit access. Please do NMU and push the changes to the git repository. On Sat, Mar 27, 2021, 17:09 Thomas Goirand wrote: > Hi, > > Please merge this: > > > https://salsa.debian.org/docker-compose-team/python-docker/-/merge_requests/3 > > > Cheers, > > Thomas Goirand (zigo) > >
Bug#986065: fuse-umfuse-fat: Please add other architectures for fusefat
Source: fuse-umfuse-fat Version: 0.1a-1.2 Severity: wishlist Dear Maintainer, Observing the source code for fusefat I think it isn't architecture agnostic; is this because of build-dependency to libumlib-dev that fusefat can't be installed? Is it possible to make that build-dependency be arch-optional for now and allow other arch to build? (I'm interested in aarch64 and armel packages). -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#934206: buster-pu: package golang-github-docker-docker-credential-helpers/0.6.1-2+deb10u1
On Fri, 26 Mar 2021 09:33:07 +0100 Salvatore Bonaccorso wrote: > > Looks that the collabora address is not anymore valid and mail > bounced. Let me try directy arna...@debian.org. > > Regards, > Salvatore > Thanks, this email reached me. I just uploaded the package. Sorry for the very long delay. I realized (a bit late) that the control file still has my old collabora address, so I won't get any notifications if ever the build fails or something. Please ping me again at arna...@debian.org or arna...@kali.org if there's a problem with the package. Thanks! -- Arnaud Rebillout
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
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#983583: FTBFS on mips64el and mipsel
On Mon, Mar 29, 2021 at 09:22:29AM +0800, YunQiang Su wrote: > Shengjing Zhu 于2021年3月28日周日 上午12:12写道： > > > > Control: reopen -1 > > Control: severity -1 important > > > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk wrote: > > > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote: > > > > Source: golang-github-sylabs-sif > > > > Version: 1.0.9-2 > > > > Severity: serious > > > > X-Debbugs-Cc: z...@debian.org > > > > > > > > Tried 3 times on buildd and failed at same test. > > > > > > > > === RUN TestAddDelObject > > > > unexpected fault address 0xffc8a0c000 > > > > fatal error: fault > > > > [signal SIGSEGV: segmentation violation code=0x2 addr=0xffc8a0c000 > > > > pc=0x12007ebe4] > > > > > > > > goroutine 22 [running]: > > > > runtime.throw(0x1201b74ed, 0x5) > > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c fp=0xce3430 > > > > sp=0xce3408 pc=0x120040afc > > > > runtime.sigpanic() > > > > > > > > Since it has been built on mipsx before, the failure will cause it > > > > impossible > > > > to fix issue later on these arch. > > > > > > > > It should either be removed from these arch or get fixed. > > > > > > This appears to be fixed now: > > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif > > > > The difference between these builds, seems to be a 5.10 kernel and > > 4.19 kernel on buildd. > > > > I'll reopen this but downgrade the severity, and loop debian-mips@ to > > see if it's regression on the kernel side. > > > > And the CPUs are different: Cavium for good and Loongson3A3000 is bad. > On https://buildd.debian.org/status/logs.php?pkg=golang-github-sylabs-sif&ver=1.0.9-2%2Bb2&arch=mips64el The failed buildd are: mipsel-manda-04, succeeded one are mipsel-aql-01. >From the build log, mipsel-manda-04: Kernel: Linux 5.10.0-0.bpo.3-loongson-3 mipsel-aql-01: Kernel: Linux 4.19.0-16-loongson-3 It doesn't seem to have Cavium CPU here.
Bug#983583: FTBFS on mips64el and mipsel
Shengjing Zhu 于2021年3月29日周一 上午11:40写道： > > On Mon, Mar 29, 2021 at 09:22:29AM +0800, YunQiang Su wrote: > > Shengjing Zhu 于2021年3月28日周日 上午12:12写道： > > > > > > Control: reopen -1 > > > Control: severity -1 important > > > > > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk wrote: > > > > > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote: > > > > > Source: golang-github-sylabs-sif > > > > > Version: 1.0.9-2 > > > > > Severity: serious > > > > > X-Debbugs-Cc: z...@debian.org > > > > > > > > > > Tried 3 times on buildd and failed at same test. > > > > > > > > > > === RUN TestAddDelObject > > > > > unexpected fault address 0xffc8a0c000 > > > > > fatal error: fault > > > > > [signal SIGSEGV: segmentation violation code=0x2 addr=0xffc8a0c000 > > > > > pc=0x12007ebe4] > > > > > > > > > > goroutine 22 [running]: > > > > > runtime.throw(0x1201b74ed, 0x5) > > > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c > > > > > fp=0xce3430 sp=0xce3408 pc=0x120040afc > > > > > runtime.sigpanic() > > > > > > > > > > Since it has been built on mipsx before, the failure will cause it > > > > > impossible > > > > > to fix issue later on these arch. > > > > > > > > > > It should either be removed from these arch or get fixed. > > > > > > > > This appears to be fixed now: > > > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif > > > > > > The difference between these builds, seems to be a 5.10 kernel and > > > 4.19 kernel on buildd. > > > > > > I'll reopen this but downgrade the severity, and loop debian-mips@ to > > > see if it's regression on the kernel side. > > > > > > > And the CPUs are different: Cavium for good and Loongson3A3000 is bad. > > > > On > https://buildd.debian.org/status/logs.php?pkg=golang-github-sylabs-sif&ver=1.0.9-2%2Bb2&arch=mips64el > > The failed buildd are: mipsel-manda-04, succeeded one are mipsel-aql-01. > From the build log, > > mipsel-manda-04: Kernel: Linux 5.10.0-0.bpo.3-loongson-3 > mipsel-aql-01: Kernel: Linux 4.19.0-16-loongson-3 > Ohh, my mistake: mips-aql-01 vs mipsel-aql-01 ;) > It doesn't seem to have Cavium CPU here. > -- YunQiang Su
Bug#962485: Bug#983583: FTBFS on mips64el and mipsel
YunQiang Su 于2021年3月29日周一 上午11:45写道： > > Shengjing Zhu 于2021年3月29日周一 上午11:40写道： > > > > On Mon, Mar 29, 2021 at 09:22:29AM +0800, YunQiang Su wrote: > > > Shengjing Zhu 于2021年3月28日周日 上午12:12写道： > > > > > > > > Control: reopen -1 > > > > Control: severity -1 important > > > > > > > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk wrote: > > > > > > > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote: > > > > > > Source: golang-github-sylabs-sif > > > > > > Version: 1.0.9-2 > > > > > > Severity: serious > > > > > > X-Debbugs-Cc: z...@debian.org > > > > > > > > > > > > Tried 3 times on buildd and failed at same test. > > > > > > > > > > > > === RUN TestAddDelObject > > > > > > unexpected fault address 0xffc8a0c000 > > > > > > fatal error: fault > > > > > > [signal SIGSEGV: segmentation violation code=0x2 addr=0xffc8a0c000 > > > > > > pc=0x12007ebe4] > > > > > > > > > > > > goroutine 22 [running]: > > > > > > runtime.throw(0x1201b74ed, 0x5) > > > > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c > > > > > > fp=0xce3430 sp=0xce3408 pc=0x120040afc > > > > > > runtime.sigpanic() > > > > > > > > > > > > Since it has been built on mipsx before, the failure will cause it > > > > > > impossible > > > > > > to fix issue later on these arch. > > > > > > > > > > > > It should either be removed from these arch or get fixed. > > > > > > > > > > This appears to be fixed now: > > > > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif > > > > > > > > The difference between these builds, seems to be a 5.10 kernel and > > > > 4.19 kernel on buildd. > > > > > > > > I'll reopen this but downgrade the severity, and loop debian-mips@ to > > > > see if it's regression on the kernel side. > > > > > > > > > > And the CPUs are different: Cavium for good and Loongson3A3000 is bad. > > > > > > > On > > https://buildd.debian.org/status/logs.php?pkg=golang-github-sylabs-sif&ver=1.0.9-2%2Bb2&arch=mips64el > > > > The failed buildd are: mipsel-manda-04, succeeded one are mipsel-aql-01. > > From the build log, > > > > mipsel-manda-04: Kernel: Linux 5.10.0-0.bpo.3-loongson-3 > > mipsel-aql-01: Kernel: Linux 4.19.0-16-loongson-3 > > > > Ohh, my mistake: mips-aql-01 vs mipsel-aql-01 ;) > WIth some test. This problem is also about O32_FP64 support option. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962485 It is quite strange this option may effect mips64el. Anyway, lets revert it. I will continue to dig the real problem. > > It doesn't seem to have Cavium CPU here. > > > > > -- > YunQiang Su -- YunQiang Su
Bug#757769: Working on packaging
retitle 757769 ITP: jitsi-videobridge -- a WebRTC compatible Selective Forwarding Unit that allows for multiuser video communication owner 757769 ! thanks I am working on packaging Jitsi Videobridge as part of Java Packaging Team. Jitsi has many dependencies these are now tracked on the wiki: https://wiki.debian.org/Java/RequestedPackages/Jitsi Thanks, -- Sunil OpenPGP_signature Description: OpenPGP digital signature
