Bug#1012289: A better future for Lintian / Bug#1012289: O: lintian -- Debian package checker
Hello, I have also sent a request to join lintian team on salsa. I am not sure how much I will be able to contribute, but I did some contributions to lintian in past, so I feel I have some idea about its code. Also I am quite fluent in Perl. Best, Andrius
Bug#799549: systemd: Provide system-log-daemon
i'm running into this thanks to zoneminder (it looks like some packages which were depending on rsyslogd|system-log-daemon, ala the aforementioned nullmailer, no longer do). looking at /var/lib/dpkg/info/systemd.postinst, it appears that persistent journal in auto-mode *is* enabled by default on new installs and upgrades: # Enable persistent journal, in auto-mode, by default on new installs and upgrades if dpkg --compare-versions "$2" lt "244.1-2~"; then mkdir -p /var/log/journal ought this bug be revisited given this fact? i see the last comment is from 2017, and systemd 244 was released in 2019. i see reference to some other, small package which enables persistent logging, but i'm unaware of any such package, and it seems unlikely to exist given the code above. signature.asc Description: PGP signature
Bug#1012448: ships dangling symlink to xpath JAR
On Tue, Jun 07, 2022 at 03:41:53PM +0200, Sébastien Villemot wrote: > Package: libxmlbeans-java > Version: 4.0.0-1 > Severity: normal > Tags: patch > > Dear Maintainer, > > libxmlbeans-java ships a dangling symlink at > /usr/share/java/xmlbeans_xpath.jar. Thank you for the bug report. I have pushed the fix to the packaging repo and it will be part of the next upload. Cheers, tony
Bug#1012362: transition: luajit
On Thu, 2022-06-09 at 13:58 +0200, Paul Gevers wrote: > Hi Mo, > > You may want to look at the FTBFS on mipsel for python-lupa. > > https://buildd.debian.org/status/fetch.php?pkg=python-lupa=mipsel=1.13%2Bdfsg-1%2Bb2=1654771416=0 Yunqiang Su (@syq) volunteers to look into luajit issues on mips* architecture.
Bug#1012566: spdlog: Please package new version v1.10.0
Hi, I'd done the spdlog new version v1.10.0 update in salsa. Welcome to review and upload. Thanks! 在 2022/6/9 22:19, Boyuan Yang 写道: Source: spdlog Version: 1:1.9.2+ds-0.2 Severity: normal Tags: sid bookworm X-Debbugs-CC: cru...@debian.org Dear Debian spdlog package maintainer, The spdlog upstream has released v1.10.0 since April 2022 (see https://github.com/gabime/spdlog/releases ). Please consider packaging the new releases in Debian. Upstream has explicitly declared compatibility with fmtlib 8.1.1 (the current version in Debian), so the new version is not expected to bring major regressions. -- 肖盛文 xiao sheng wen Faris Xiao 微信(wechat)：atzlinux 《铜豌豆 Linux》https://www.atzlinux.com 基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com GnuPG Public Key: 0x00186602339240CB OpenPGP_signature Description: OpenPGP digital signature
Bug#1012362: transition: luajit
On Thu, 2022-06-09 at 10:47 +0200, Paul Gevers wrote: > > I think there one more *test* issue, the first test in src:luajit > doens't explicitly declare dependencies, which means it implicitly has > has '@'. Quoting [1]: > > > Which means that autopkgtest asks apt to make sure all packages from > src:luajit are installed, but the dependency tree of bin:luajit > conflicts with some. This can be solved by only depending on luajit, as > that pulls in the required packages anyways. > Yes. The libluajit-5.1-common has conflicts. Fixed in git: https://salsa.debian.org/lua-team/luajit/-/commit/0489ec840f2ab240785ecd8190962cb779858c29 > lua-moses autopkgtest failure [2] looks bad (still a segmentation fault): > autopkgtest [07:20:14]: test command9: luajit debian/tests/simple.lua > autopkgtest [07:20:14]: test command9: [--- > bash: line 1: 1240 Segmentation fault bash -ec 'luajit > debian/tests/simple.lua' 2> >(tee -a > /tmp/autopkgtest-lxc.u7chaju_/downtmp/command9-stderr >&2) > >(tee -a > /tmp/autopkgtest-lxc.u7chaju_/downtmp/command9-stdout) > autopkgtest [07:20:14]: test command9: ---] There are some compilation flags tweakable. I'll try with qemu to see whether I can make it work.
Bug#1002059: regression: 2:4.9.5+dfsg-5+deb10u2 breaks SID to UID conversion
On Fri, Jun 10, 2022 at 02:11:21PM +1000, Vincent McIntyre wrote: > >Yes, we have the same usernames (and uids) in both. >This is by design and has worked for many years. >It continues to work, I have machines running version >2:4.5.16+dfsg-1+deb9u4 >with no issue. doh, wrong version. I have machines running 2:4.9.5+dfsg-5+deb10u3 that work with the config change mentioned in #20. Sorry for the confusion.
Bug#1002059: regression: 2:4.9.5+dfsg-5+deb10u2 breaks SID to UID conversion
Just saw the updates to this bug... Hi Michael thanks for your work on knocking samba packages into better shape over the last few months. You asked: > Vincent, do you, by a chance, have the same usernames in > /etc/passwd and in the AD your samba server joined? Yes, we have the same usernames (and uids) in both. This is by design and has worked for many years. It continues to work, I have machines running version 2:4.5.16+dfsg-1+deb9u4 with no issue. I think this bug can be closed. I was actually doing something unsupoprted before, but got away with it for a while. As I outlined in message #20 making the now-required config change fixed it in my environment. I think Thibalt's issue is different, he has kerberos set up and security = ads on version 4.13, all of which means quite different code paths. Kind regards Vince
Bug#1012577: update puppetdb to latest upstream (currently 6.21.0)
On Thu, 09 Jun 2022 14:25:30 -0400 Antoine Beaupre wrote: > Source: puppetdb > Version: 6.2.0-5 > Severity: wishlist > > We're lagging quite a bit behind upstream, and should update to follow > the latest. > > This is a meta-ticket tracking that effort, which should close a bunch > of other issues. My understanding is that the latest upstream release is 7.10.1. The latest version on the 6.x branch is 6.21.0 though: https://github.com/puppetlabs/puppetdb/releases/tag/7.10.1 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1012289: A better future for Lintian / Bug#1012289: O: lintian -- Debian package checker
Hi, On Fri, Jun 10, 2022 at 05:10:03AM +0200, Axel Beckert wrote: Bo YU: What's your user name on Salsa? And maybe can you try to make some contributions to Lintian via Merge Requests first? (The latter basically counts for all non-DD membership requests.) Yeah, I would to send MR if I can fix some issues about lintian. Bo -- Best Regards, signature.asc Description: PGP signature
Bug#1011057: lintian: Add warning if a *.postinst file does not have #DEBHELPER#
Control: tag -1 +moreinfo Hi Carles, Carles Pina i Estany wrote: > Package: lintian > Version: 2.104.0 […] > It might be useful that lintian checked that each *.postinst contains > the #DEBHELPER# string. > > For example, I noticed a missing #DEBHELPER# when creating a package > that installed a systemd service but it did not start as expected. Lintian already has a tag named maintainer-script-lacks-debhelper-token for exactly that. See also https://lintian.debian.org/tags/maintainer-script-lacks-debhelper-token The tag is though only emitted if debhelper is actually used. If in your case the tag should have been emitted but hadn't been emitted, please tell us which package at which version (or commit ID) this happened. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1007922: false positive spelling: substract and subtract is both correct
Hi, Felix Lechner wrote: > > substract and subtract are both correct > > Where did you see that word? > > > "Now nonstandard and rare" > > Yeah, I'm with Russ. I found "sub-S-tract" in the 1913 Webster's > Dictionary but no longer in Webster's Second from 1960. (Finally, > those dusty volumes found some use.) I have never heard, or seen, that > form of "sub-tract," but let's give others a chance to chime in. Writing "substract" instead of "subtract" seems to be a German thing. I also tend to write "substract" instead of "subtract". I suspect that this is because in German there are a lot of binding "s" in compound words where it eases pronounciation. And indeed, pronouncing "subtract" without "s" feels a lot more difficult than "substract" for me. Actually I think we have the same issue in German itself: I would say "Substrahieren", but correct is "Subtrahieren". Another reason might be the similarity to words like the German "Substrat" or the English word "substrate" (which both mean the same). Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1012603: ITP: node-ismobilejs -- JavaScript library to detect mobile devices
Package: wnpp Severity: wishlist Owner: Joe Nahmias X-Debbugs-CC: debian-de...@lists.debian.org X-Debbugs-CC: Debian Javascript Maintainers X-Debbugs-CC: Kai Mallea * Package name: node-ismobilejs Version : 1.1.1 Upstream Author : Kai Mallea * URL : https://github.com/kaimallea/isMobile * License : Expat Programming Lang: JavaScript Description : JavaScript library to detect mobile devices A simple JavaScript library for detecting when a page is viewed on a mobile device. Output is placed in a JS object that you can then test for various results. . It works both in the browser as a JavaScript library or on the server side via NodeJS. . Node.js is an event-based server-side JavaScript engine. This is a dependency for Kanboard. I plan to maintain it within the JavaScript team.
Bug#1012289: A better future for Lintian / Bug#1012289: O: lintian -- Debian package checker
Control: retitle -1 RFH: lintian -- Debian package checker (actually ITA + RFH) Hi Felix, I only read about the "O: lintian" bug and your mailing list posting via this week's "Work-needing packages report". I'm on the Lintian mailing list, but procmail filters it into a separate incoming box as I do for many mailing lists. Felix Lechner wrote in April: > Given Lintian's importance to the community, I don't think I am the > right person to take care of Lintian or its website going forward. Oof. Why that? IMHO you did a superb job on this! But that explains the silence with regards to lintian uploads. > The current HEAD is in my view in reasonable shape, Ok, will try to make an upload soonish™ to at least get the current state into unstable plus the most pressing low hanging fruits fixed, e.g. like the new Debian Policy version via https://salsa.debian.org/lintian/lintian/-/merge_requests/393 as well as some more LHF merge requests. I also skimmed through the open MRs and marked those as "approved" which I intent to merge. Hopefully will manage to get that done latest the upcoming weekend. I've also removed Chris (Cc'ed) from Uploaders due to his statement in https://lists.debian.org/debian-lint-maint/2022/04/msg00017.html Thanks to Chris and Felix for their long-time work on Lintian! And thanks Paul for creating this "O:" bug report and refering to these two mails! Chris was the last one in the Uploaders field, so I've re-added myself to Uploaders, too. Which also means that this is kind of an ITA. (I was already in Uploaders from 2015 to 2019.) To get some better bus-factor, I've also granted access to those who requested membership in the Salsa group "lintian" and who are DDs, namely Nilesh Patra and Yadd — both Cc'ed as well. Welcome and thanks for your offers! There are two more membership requests pending from people who are no DD and from whom I've never heard before. One of them might be Bo YU from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012289#12, but none of the user or real names in the membership requests looks similar. Bo YU: What's your user name on Salsa? And maybe can you try to make some contributions to Lintian via Merge Requests first? (The latter basically counts for all non-DD membership requests.) > except that the MLDBM databases introduced to mitigate Bug#1003456 > (excessive memory use when confronted with enormous ELF data) do not > seem to get deleted during global destruction. There is also an open > Perltidy bug (#998367) that keeps the Salsa pipeline from passing. Thanks for these hints! In general: I will try to keep Lintian in a sane state, but I surely will not be able to put as much effort and time into Lintian as Felix and Chris did. I'm fluent in Perl, but I know that I'm not the best wrt. to performance-critical Perl code. (Niels taught me some tricks at DebConf15, though. :-) So I'll likely will do mostly maintainance work, bug triage and some bug fixing, but probably won't do any invasive changes, performance tuning nor rewrites like Felix did. Oh, and I also have no idea of how lintian.debian.org currently works. I suspect, I need to get added to the "lintian" LDAP group to be able to work on that. (It seems only Felix, Russ and Colin are current members of that LDAP group.) And I'm probably already stuck with too many packages, so any help is really welcome. In other words: We definitely need more people working on Lintian again. So instead of declaring this as ITA, I've for now declared this to be an RFH with a taste of ITA. I hope, that's ok. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Bug#1012564: [Pkg-openssl-devel] Bug#1012564: openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7
On 10 June 2022 3:51:29 am ACST, Sebastian Andrzej Siewior wrote: >On 2022-06-09 23:18:07 [+0930], Arthur Marsh wrote: >… >> *** Reporter, please consider answering these questions, where appropriate >> *** >> >>* What led up to the situation? >> >> Upgrading openssl, libssl3 to 3.0.3-7 from 3.0.3-6 on host system prevented >> ckermit 305~alpha07-1+b1 on client system with libssl3 3.0.3-6 from >> connecting to telnetd-ssl 0.17.41+0.2-3.3 on host system. >> >> >>* What exactly did you do (or not do) that was effective (or >> ineffective)? >> >> I first downgraded libssl3 from 3.0.3-7 on host system to 3.0.3-6 but that >> didn't resolve the issue. After I downgraded openssl from 3.0.3-7 to 3.0.3-6 >> on the host system, I was able to connect from the client system which still >> runs openssl 3.0.3-6 and libssl3 3.0.3-6. > >How do I setup a telnet-ssl server to begin with? >I installed telnetd-ssl from testing just to be sure and > telnet -z ssl localhost > >does nothing. Any idea? > >Sebastian Hi, I was using ckermit as the telnet client, with a symbolic link from /usr/local/bin/telnet to /usr/bin/kermit Alternatively, simply run kermit and at the C-Kermit prompt enter: telnet localhost If using telnet from package telnet-ssl, one can connect using: telnet 127.0.0.1 (provided you are not doing so as root). Hope this helps, Arthur. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#606713: unarchiving 606713, reopening 606713, found 606713 in 5.10.28-1
On Fri, 2022-06-10 at 00:36 +0200, Diederik de Haas wrote: > A year has passed and it has been quiet on the upstream bug for almost a year. > Has there been progress which isn't visible in upstream or Debian's BTS? There hasn't. I haven't had time to try this bug again but I will try to make time to reproduce it towards the end of June. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1012602: dynamic-motd: Makes SSH login horribly slow, even if MOTD isn't shown
Package: dynamic-motd Version: 0.04-1 Severity: normal Before installing dynamic-motd, (key-based) "ssh root@localhost" was more or less instantaneous (below 1 second). Since installing dynamic-motd it takes about 40 seconds to login on that box, even via localhost and even despite being a not so slow box (a quad-core workstation with a single X session and lot of xterms and outgoing SSH sessions): ~ → lscpu | fgrep "Model name"; uptime; date; ssh localhost date Model name: Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz 02:34:23 up 55 days, 7:39, 196 users, load average: 3.09, 3.52, 3.28 Fri Jun 10 02:34:23 CEST 2022 Fri Jun 10 02:35:05 CEST 2022 ~ → Most time seems to be spent for calling checkrestart (33 seconds). If only needrestart would have been installed, that step would even have taken even longer (4 minutes and 18 seconds; phew!) So please try to at least cache the results of checkrestart and needrestart. Or maybe pre-calculate them via cron-job once an hour or so. Or disable them completely by default. For those suffering from this issue as well, here's how I solved it for myself: # dpkg-divert --local --rename --divert /etc/update-motd.d/50-services-need-restart.DISABLED --add /etc/update-motd.d/50-services-need-restart Now I'm down to about 8 seconds for logging in via SSH. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages dynamic-motd depends on: ii bc1.07.1-3+b1 ii figlet2.2.5-3+b1 ii lsb-release 11.2 ii python3 3.10.4-1+b1 ii python3-utmp 0.9-1+b5 dynamic-motd recommends no packages. dynamic-motd suggests no packages. -- no debconf information
Bug#1002034: f2fs-tools: resize.f2fs always fails with Error: Device size is not sufficient for F2FS volume, more segment needed
X-Debbugs-CC: ty...@mit.edu vch...@debian.org On Tue, 07 Jun 2022 09:20:30 +0200 Tobias Frost wrote: > Control: tags -1 fixed-upstream > > https://bugs.archlinux.org/task/71801 makes me believe that the new upstream version has a fix for this issue. Can we do something to solve this bug? I have seen users impacted by this bug and found no way to get it fixed in Debian. A new upstream release is also available; maybe it's time to look into the new version as well. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1012600: Further info
Apparently root cause is function `bio_alloc()` changed signature qith newer kernels 5.17.x -> 5.18.0. Apparently upstream sources were not updated; specifically file `.../zfs/vdev_disk.c` still uses the old (2 parameter) function instead of the newer (4 parameters) one. I will report also upstream. Regards Mauro
Bug#1012601: wireless-regdb: alternative broken on debian-installer install
Package: wireless-regdb Version: 2021.08.28-1 Severity: important Tags: d-i X-Debbugs-Cc: debian-b...@lists.debian.org Dear Maintainer, I've noticed after installing wireless-regdb on a fresh install the package-provided file is not actually used (older version from wireless-regdb-udeb is used), and update-alternative to select the upstream version of the regdb also fails (debian-boot@l.d.o: sorry for the explicit cc, I'm not really sure what the d-i tag implies) The problem is that the installer copies /lib/firmware/regulatory.db and /lib/firmware/regulatory.db.p7s from the installer, and wireless-regdb postinstall script does not overwrite these if they exist. This can be reproduced in a minimal container: root@00e7025e1eeb:/# mkdir /lib/firmware root@00e7025e1eeb:/# touch /lib/firmware/regulatory.db root@00e7025e1eeb:/# apt install -y wireless-regdb Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: crda The following NEW packages will be installed: wireless-regdb 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 13.9 kB of archives. After this operation, 42.0 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian bullseye/main amd64 wireless-regdb all 2020.04.29-2 [13.9 kB] Fetched 13.9 kB in 0s (222 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package wireless-regdb. (Reading database ... 6662 files and directories currently installed.) Preparing to unpack .../wireless-regdb_2020.04.29-2_all.deb ... Unpacking wireless-regdb (2020.04.29-2) ... Setting up wireless-regdb (2020.04.29-2) ... update-alternatives: using /lib/firmware/regulatory.db-debian to provide /lib/firmware/regulatory.db (regulatory.db) in auto mode update-alternatives: warning: not replacing /lib/firmware/regulatory.db with a link update-alternatives: warning: forcing reinstallation of alternative /lib/firmware/regulatory.db-debian because link group regulatory.db is broken update-alternatives: warning: not replacing /lib/firmware/regulatory.db with a link root@00e7025e1eeb:/# ls -l /lib/firmware/regulatory.db* -rw-r--r-- 1 root root0 Jun 10 00:21 /lib/firmware/regulatory.db -rw-r--r-- 1 root root 3764 Jun 30 2020 /lib/firmware/regulatory.db-debian -rw-r--r-- 1 root root 3764 Jun 30 2020 /lib/firmware/regulatory.db-upstream lrwxrwxrwx 1 root root 35 Jun 10 00:21 /lib/firmware/regulatory.db.p7s -> /etc/alternatives/regulatory.db.p7s -rw-r--r-- 1 root root 1249 Jun 30 2020 /lib/firmware/regulatory.db.p7s-debian -rw-r--r-- 1 root root 1182 Jun 30 2020 /lib/firmware/regulatory.db.p7s-upstream root@00e7025e1eeb:/# update-alternatives --config regulatory.db There are 2 choices for the alternative regulatory.db (providing /lib/firmware/regulatory.db). SelectionPath Priority Status 0/lib/firmware/regulatory.db-debian 100 auto mode * 1/lib/firmware/regulatory.db-debian 100 manual mode 2/lib/firmware/regulatory.db-upstream 50manual mode Press to keep the current choice[*], or type selection number: update-alternatives: warning: forcing reinstallation of alternative /lib/firmware/regulatory.db-debian because link group regulatory.db is broken update-alternatives: warning: not replacing /lib/firmware/regulatory.db with a link root@00e7025e1eeb:/# ls -l /lib/firmware/regulatory.db -rw-r--r-- 1 root root0 Jun 10 00:21 /lib/firmware/regulatory.db Running with --force removes the original file with a warning and works: root@00e7025e1eeb:/# update-alternatives --force --config regulatory.db There are 2 choices for the alternative regulatory.db (providing /lib/firmware/regulatory.db). SelectionPath Priority Status 0/lib/firmware/regulatory.db-debian 100 auto mode * 1/lib/firmware/regulatory.db-debian 100 manual mode 2/lib/firmware/regulatory.db-upstream 50manual mode Press to keep the current choice[*], or type selection number: update-alternatives: warning: forcing reinstallation of alternative /lib/firmware/regulatory.db-debian because link group regulatory.db is broken root@00e7025e1eeb:/# ls -l /lib/firmware/regulatory.db lrwxrwxrwx 1 root root 31 Jun 10 00:23 /lib/firmware/regulatory.db -> /etc/alternatives/regulatory.db The original cause for this is that deian-installer copies the files because of the combinaison of these two: https://salsa.debian.org/installer-team/debian-installer/-/blob/master/build/pkg-lists/base#L34 - wireless-regdb-udeb contains the firmwares as regular files
Bug#522773: possible solutions for __unused problem
Diederik de Haas dixit: >and the patch proposed by Ben, more then 6 years ago, hasn't been merged. > >As I don't know the reason it wasn't closed last year, I won't do it, but >maybe it's time to finally close it? If the bug persists, it’s still a bug, so don’t close it. Prod them occasionally. I know that *some* __unused have been fixed; maybe the remaining ones were an oversight? bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs
Bug#1012600: zfs-dkms: Compilation fails. ZFS completely non-functional after latest kernel upgrade.
Package: zfs-dkms Version: 2.1.4-1 Severity: grave Tags: ftbfs Justification: renders package unusable X-Debbugs-Cc: mc5...@mclink.it Dear Maintainer, zfs system is completely non-functional due to zfs-dkms kernel module compilation terminating in error. My `/home/` is on zfs and thus I'm restricted to use `root` who has a usable `$HOME`. * What led up to the situation? Routine "apt update && apt upgrade", most likely due to kernel upgrade. After installation system asked for a reboot to complete kernel update. After reboot I got the normal `lightdm` login screen, but I was unable to login. I went to a text console to analyze situation and I found /home/ completely wiped. Also dmesg shows system does not find suitable ZFS moduled and thus is unable to mount pool. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to reinstall the failing package, but there are evident errors visible in `/var/lib/dkms/zfs/2.1.4/build/make.log` I am unsure how I can attach the file here. If I don't manage it I will try to comment on the bug from another machine. System is currently completely unusable. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.79 ii dkms 3.0.3-2 ii file 1:5.41-4 ii libc6-dev [libc-dev] 2.33-7 ii libpython3-stdlib 3.10.4-1+b1 ii lsb-release11.2 ii perl 5.34.0-4 ii python3-distutils 3.10.5-1 Versions of packages zfs-dkms recommends: ii linux-libc-dev 5.18.2-1 ii zfs-zed 2.1.4-1+b1 ii zfsutils-linux 2.1.4-1+b1 Versions of packages zfs-dkms suggests: pn debhelper -- debconf information: zfs-dkms/stop-build-for-32bit-kernel: true zfs-dkms/stop-build-for-unknown-kernel: true * zfs-dkms/note-incompatible-licenses: DKMS make.log for zfs-2.1.4 for kernel 5.18.0-1-amd64 (x86_64) Fri Jun 10 12:50:47 AM CEST 2022 make all-recursive make[1]: Entering directory '/var/lib/dkms/zfs/2.1.4/build' Making all in module make[2]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module' list='icp lua zstd'; for td in $list; do make -C $td; done make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/icp' mkdir -p api core spi io os algs algs/aes algs/edonr algs/modes algs/sha1 algs/sha2 algs/skein asm-x86_64 asm-x86_64/aes asm-x86_64/modes asm-x86_64/sha1 asm-x86_64/sha2 asm-i386 asm-generic make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/icp' make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/lua' mkdir -p setjmp make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/lua' make[3]: Entering directory '/var/lib/dkms/zfs/2.1.4/build/module/zstd' mkdir -p lib make[3]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module/zstd' make -C /lib/modules/5.18.0-1-amd64/build \ \ M="$PWD" O=/lib/modules/5.18.0-1-amd64/build CONFIG_ZFS=m modules make[3]: Entering directory '/usr/src/linux-headers-5.18.0-1-amd64' CC [M] /var/lib/dkms/zfs/2.1.4/build/module/nvpair/nvpair.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/lua/lapi.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/unicode/u8_textprep.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/unicode/uconv.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/nvpair/fnvpair.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/avl/avl.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/spl/../os/linux/spl/spl-atomic.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/lua/lauxlib.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/icp/illumos-crypto.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zcommon/cityhash.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zstd/zfs_zstd.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zfs/abd.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/spl/../os/linux/spl/spl-condvar.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/icp/api/kcf_cipher.o LD [M] /var/lib/dkms/zfs/2.1.4/build/module/avl/zavl.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zfs/aggsum.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/nvpair/nvpair_alloc_spl.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zfs/arc.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zcommon/zfeature_common.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/spl/../os/linux/spl/spl-cred.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/spl/../os/linux/spl/spl-err.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/lua/lbaselib.o CC [M] /var/lib/dkms/zfs/2.1.4/build/module/zstd/lib/zstd.o CC [M]
Bug#1012599: nautilus: folder names do not fit correctly in the defined width when resizing the screen with tweak tool
Package: nautilus Version: 42.2-1 Severity: normal X-Debbugs-Cc: sazamor...@gmail.com Dear Maintainer, * What led up to the situation? Increase 2 levels typography scaling factor in tweak tool to make system font readable on 15" laptop screen (to small by default). * What exactly did you do (or not do) that was effective (or ineffective)? Using folders names larger than 9 characters before space, get moved to the next line, showing cutted main word name. * What was the outcome of this action? Folder names are cut off or displayed incorrectly * What outcome did you expect instead? The complete folder names for each line of the name, within the width defined for the names. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), LANGUAGE=es_CL:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nautilus depends on: ii bubblewrap 0.6.2-1 ii desktop-file-utils 0.26-1 ii gsettings-desktop-schemas 42.0-1 ii gvfs1.50.2-1 ii libatk1.0-0 2.38.0-1 ii libc6 2.33-7 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libgexiv2-2 0.14.0-1 ii libglib2.0-02.72.1-1 ii libglib2.0-data 2.72.1-1 ii libgnome-autoar-0-0 0.4.3-1 ii libgnome-desktop-3-19 42.2-1 ii libgstreamer-plugins-base1.0-0 1.20.2-2 ii libgstreamer1.0-0 1.20.2-1 ii libgtk-3-0 3.24.34-1 ii libhandy-1-01.6.2-1 ii libnautilus-extension1a 42.2-1 ii libpango-1.0-0 1.50.7+ds-1 ii libportal-gtk3-10.6-2 ii libportal1 0.6-2 ii libselinux1 3.3-1+b2 ii libtracker-sparql-3.0-0 3.1.2-4+b1 ii nautilus-data 42.2-1 ii shared-mime-info2.2-1 ii tracker 3.1.2-4+b1 ii tracker-extract 3.1.3-4+b1 ii tracker-miner-fs3.1.3-4+b1 Versions of packages nautilus recommends: ii gnome-sushi 41.2-1 ii gvfs-backends 1.50.2-1 ii libgdk-pixbuf2.0-bin 2.42.8+dfsg-1 ii librsvg2-common 2.54.3+dfsg-1 Versions of packages nautilus suggests: ii atril [pdf-viewer] 1.26.0-1 ii eog 42.1-1 ii evince [pdf-viewer] 42.3-1 ii nautilus-extension-brasero 3.12.3-1 pn nautilus-sendto ii totem 42.0-1 ii xdg-user-dirs 0.17-2 -- no debconf information
Bug#982299: vlc: seems related to https://github.com/aler9/rtsp-simple-server/issues/223
Package: vlc Version: 3.0.16-1 Followup-For: Bug #982299 X-Debbugs-Cc: aifeste...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to stream a cctv camera. * What exactly did you do (or not do) that was effective (or ineffective)? Linux VLC refused to stream, but Android VLC streamed the camera * What was the outcome of this action? Jun 9 23:58:20 lepton vlc[246391]: no art finder modules matched Jun 9 23:58:20 lepton vlc[246391]: Failed to setup RTSP session Jun 9 23:58:20 lepton vlc[246391]: net: connecting to 192.168.1.142 port 554 Jun 9 23:58:20 lepton vlc[246391]: connection succeeded (socket = 38) Jun 9 23:58:20 lepton vlc[246391]: Cseq mismatch, got 1, assumed 0 Jun 9 23:58:20 lepton vlc[246391]: rtsp connected Jun 9 23:58:20 lepton vlc[246391]: only real/helix rtsp servers supported for now Jun 9 23:58:20 lepton vlc[246391]: no access modules matched Jun 9 23:58:20 lepton vlc[246391]: dead input Jun 9 23:58:20 lepton vlc[246391]: IM: Deleting the input Jun 9 23:58:20 lepton vlc[246391]: changing item without a request (current 0/1) Jun 9 23:58:20 lepton vlc[246391]: nothing to play * What outcome did you expect instead? For it to work like in Android vlc... *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8), LANGUAGE=pt:pt_BR:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.16-1 ii vlc-plugin-base 3.0.16-1 ii vlc-plugin-qt3.0.16-1 ii vlc-plugin-video-output 3.0.16-1 Versions of packages vlc recommends: ii vlc-l10n 3.0.16-1 ii vlc-plugin-access-extra3.0.16-1 ii vlc-plugin-notify 3.0.16-1 ii vlc-plugin-samba 3.0.16-1 ii vlc-plugin-skins2 3.0.16-1 ii vlc-plugin-video-splitter 3.0.16-1 ii vlc-plugin-visualization 3.0.16-1 Versions of packages vlc suggests: pn vlc-plugin-fluidsynth pn vlc-plugin-jack pn vlc-plugin-svg Versions of packages libvlc-bin depends on: ii libc62.31-13+deb11u3 ii libvlc5 3.0.16-1 Versions of packages libvlc5 depends on: ii libc62.31-13+deb11u3 ii libvlccore9 3.0.16-1 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.16-1 Versions of packages vlc-bin depends on: ii libc6 2.31-13+deb11u3 ii libvlc-bin 3.0.16-1 ii libvlc5 3.0.16-1 Versions of packages vlc-plugin-access-extra depends on: ii libc62.31-13+deb11u3 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.16-1 ii libvncclient10.9.13+dfsg-2 ii libxcb-composite01.14-3 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-20 ii libarchive13 3.4.3-2+deb11u1 ii libaribb24-0 1.0.3-2 ii libasound2 1.2.4-1.1 ii libass9 1:0.15.0-2 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libavc1394-0 0.5.4-5 ii libavcodec58 7:4.3.4-0+deb11u1 ii libavformat587:4.3.4-0+deb11u1 ii libavutil56 7:4.3.4-0+deb11u1 ii libbluray2 1:1.2.1-4+deb11u1 ii libc62.31-13+deb11u3 ii libcairo21.16.0-5 ii libcddb2 1.3.2-6+b1 ii libchromaprint1 1.5.0-2 ii libdav1d40.7.1-3 ii libdbus-1-3 1.12.20-2 ii libdc1394-25 2.2.6-3 ii libdca0 0.0.7-2 ii libdvbpsi10 1.3.3-1 ii libdvdnav4 6.1.0-1+b1 ii libdvdread8 6.1.1-2 ii libebml5 1.4.2-1 ii libfaad2 2.10.0-1 ii libflac8 1.3.3-2+deb11u1 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libfribidi0 1.0.8-2 ii libgcc-s110.2.1-6 ii libgcrypt20
Bug#1012227: webkitgtk: CPU usage
On Thu, Jun 09, 2022 at 03:59:33PM -0500, Tim McConnell wrote: > running sudo ps -aux |grep WebKitWebProcess > tmick4071296 53.0 9.5 88411428 683212 ? RLl 15:38 8:13 > /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 35 > tmick4073180 0.0 0.0 6432 2284 pts/1T15:52 0:00 grep > WebKitWebProcess > tmick4073195 0.0 0.0 6432 2284 pts/1S+ 15:54 0:00 grep > WebKitWebProcess > > And stays there until I shutdown everything that uses it. Evolution, TOR, > Firefox and reboot. It's like I'm running Windows 3.11 again. Can you please try this? - Run webkit and identify the PID that is using most of the CPU (using top or any similar tool) - As root run "perf top -pPID --sort dso,symbol" This will give you the shared libraries and symbols that are eating the CPU. Thanks, Berto
Bug#1012598: packages.debian.org: Shown versions from Debian Testing and Unstable lag at least 2 weeks behind
Package: www.debian.org Severity: normal X-Debbugs-Cc: a...@debian.org packages.debian.org shows outdated package versions for Unstable and Testing. It shows version from between 1 and 2 weeks ago for those recently uploaded packages I checked. Is there something no more syncing package databases or no more regenerating content? Some examples: 1) hugo https://packages.debian.org/search?keywords=hugo shows me the following version of hugo in Unstable to me: sid (unstable) (web): Fast and flexible Static Site Generator written in Go 0.96.0-1+b1: amd64 arm64 armel armhf i386 mips64el mipsel ppc64 ppc64el riscv64 s390x And https://packages.debian.org/sid/hugo shows me: Package: hugo (0.96.0-1 and others) […] Architecture Version Package SizeInstalled Size Files amd64 0.96.0-1+b1 11,200.4 kB 49,651.0 kB [list of files] But according to https://tracker.debian.org/pkg/hugo, this is outdated since at least 2022-06-04, i.e. for more than 5 days (and less than 5 weeks) as of now, because all these uploads of the past few days are not shown on packages.debian.org: [2022-06-08] Accepted hugo 0.100.1-1 (source) into unstable (Anthony Fok) [2022-06-07] Accepted hugo 0.99.1-1 (source) into unstable (Anthony Fok) [2022-06-05] Accepted hugo 0.98.0-1 (source) into unstable (Anthony Fok) [2022-06-04] Accepted hugo 0.97.3-1 (source) into unstable (Anthony Fok) 2) libwww-dict-leo-org-perl https://packages.debian.org/sid/libwww-dict-leo-org-perl and https://packages.debian.org/bookworm/libwww-dict-leo-org-perl both show: Package: libwww-dict-leo-org-perl (2.02-2) But I did one upload on 2022-06-04 which already migrated to Testing more than a day ago, see https://tracker.debian.org/pkg/libwww-dict-leo-org-perl: [2022-06-08] libwww-dict-leo-org-perl 2.02-3 MIGRATED to testing (Debian testing watch) [2022-06-04] Accepted libwww-dict-leo-org-perl 2.02-3 (source) into unstable (Axel Beckert) 3) linux-image-*-amd64-unsigned, linux-doc and src:linux https://packages.debian.org/sid/linux-image-5.17.0-2-amd64-unsigned is there (uploaded 2022-05-11), but no more in Sid since 2022-05-27. https://packages.debian.org/sid/linux-image-5.18.0-1-amd64-unsigned gives "No such package". And there even was a linux-image-5.17.0-3-amd64 in Unstable in between, uploaded on 2022-05-27, which was more or less 2 weeks ago. https://packages.debian.org/sid/linux-doc as well as https://packages.debian.org/source/sid/linux also show 5.17.6-1 and miss these uploads to Unstable: [2022-06-06] Accepted linux 5.18.2-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso) [2022-05-27] Accepted linux 5.17.11-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso) 4) libdevel-cover-perl https://packages.debian.org/search?keywords=libdevel-cover-perl shows 1.36-2+b2 for Unstable and Testing, but actually these should be shown (citing from https://tracker.debian.org/pkg/libdevel-cover-perl): [2022-06-09] Accepted libdevel-cover-perl 1.38-1 (source) into unstable (Axel Beckert) [2022-06-08] libdevel-cover-perl 1.37-1 MIGRATED to testing (Debian testing watch) [2022-06-05] Accepted libdevel-cover-perl 1.37-1 (source) into unstable (gregor herrmann)
Bug#1012597: aegisub: updating from libboost-regex1.74.0-14 to libboost-regex1.74.0-16 ask to remove aegisub
Package: aegisub Version: 3.2.2+dfsg-6+b1 Severity: important X-Debbugs-Cc: keyofbl...@gmail.com Dear Maintainer, updating from libboost-regex1.74.0-14 to libboost-regex1.74.0-16 ask to remove aegisub. Thanks and best regards. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.11-custom (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aegisub depends on: ii libasound2 1.2.6.1-2+b1 ii libass9 1:0.16.0-1 ii libboost-chrono1.74.01.74.0-16 ii libboost-filesystem1.74.01.74.0-16 ii libboost-locale1.74.01.74.0-16 ii libboost-regex1.74.0 [libboost-regex1.74.0- 1.74.0-14 ii libboost-thread1.74.01.74.0-16 ii libc62.33-7 ii libffms2-4 2.23-5 ii libfftw3-double3 3.3.8-2 ii libfontconfig1 2.13.1-4.4 ii libgcc-s112.1.0-2 ii libgl1 1.4.0-1 ii libhunspell-1.7-01.7.0-4 ii libicu67 67.1-7 ii libluajit-5.1-2 2.1.0~beta3+git20220320+dfsg-4 ii libpulse015.0+dfsg1-4+b1 ii libstdc++6 12.1.0-2 ii libwxbase3.0-0v5 3.0.5.1+dfsg-4 ii libwxgtk3.0-gtk3-0v5 3.0.5.1+dfsg-4 ii zlib1g 1:1.2.11.dfsg-4 aegisub recommends no packages. Versions of packages aegisub suggests: pn aegisub-l10n -- no debconf information
Bug#1012548: libwebkit2gtk-4.1-0: Offline renderer SIGSEGV on i386
On Thu, Jun 09, 2022 at 01:59:25AM +0200, karogyoker wrote: > The problem is reproducible if I try to open this webpage in epiphany-browser: > https://www.microsoft.com/en-us/software-download/windows10ISO I cannot reproduce the problem with QEMU emulating a pentium 3 CPU. We have had problems with old i386 CPUs in the past, see #930935 in particular, but there's no SIGILL here. > (gdb) x/i $eip > => 0xb56f7218: ldmxcsr DWORD PTR [esp+0x28] Also, this is an SSE instruction, but your processor supports it: > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow cpuid 3dnowprefetch Do you think you can provide a backtrace with the -dbgsym package installed? Thanks, Berto
Bug#606713: unarchiving 606713, reopening 606713, found 606713 in 5.10.28-1
Control: tag -1 moreinfo On Sat, 05 Jun 2021 19:59:40 +0800 Paul Wise wrote: > # still present in bullseye, talking with upstream about debugging etc > unarchive 606713 > reopen 606713 > found 606713 5.10.28-1 A year has passed and it has been quiet on the upstream bug for almost a year. Has there been progress which isn't visible in upstream or Debian's BTS? It looks like a 5.10.120-1 release is 'around the corner' and in Unstable we now have a 5.18.x release. Can you test whether it's still reproducible? > The issue doesn't happen with Windows XP running on the same machine, so I > do think this is a Linux specific bug. This sounds like a BIOS/ACPI bug and AFAIK it's not uncommon that WinXP has 'workarounds' for things like that. Given the age of the laptop, I doubt a BIOS fix is in the works. Maybe WinXP source code has been leaked somewhere? signature.asc Description: This is a digitally signed message part.
Bug#522773: possible solutions for __unused problem
On Saturday, 1 May 2021 14:02:33 CEST Salvatore Bonaccorso wrote: > On Fri, Jul 29, 2011 at 06:14:18PM +0200, Robert Millan wrote: > > 2011/7/29 Moritz Mühlenhoff : > > > We already asked you back in September 2009 to report this upstream. > > > > He did, precisely in September 2009: > > > > https://bugzilla.kernel.org/show_bug.cgi?id=14186 > > > > He still got no response though. > > Given there was as well not reaction upstream AFAICS, as well to Ben's > posted patch I guess we can close this bug. Not doing so yet though. Another year has passed and it's now almost 10 years ago that the upstream bug was closed (in a less then courteous way). I just checked 'arch/alpha/include/uapi/asm/stat.h' in Linus' master branch and the patch proposed by Ben, more then 6 years ago, hasn't been merged. As I don't know the reason it wasn't closed last year, I won't do it, but maybe it's time to finally close it? signature.asc Description: This is a digitally signed message part.
Bug#896916:
On Thu, 2022-06-09 at 19:57 +0200, Marc Haber wrote: > > I'd recommend the following: > > - invoke tar --create --auto-compress --file /tmp/foo.tar.suffix > --directory / usr/sbin/deluser > - if exit code 127 (compressor known, but not installed): > - print diagnostic > - set suffix to ".gz" (gzip is essential and guaranteed to exist) > - if exit code != 127 > - invoke tar --create --file /tmp/foo.tar > --directory / usr/sbin/deluser > - check whether foo.tar and foo.tar.sufffix are identical (that > happens when the tar file suffix does not match a known > compressor) > - if identical (unknown compressor given) > - print diagnostic > - set suffix to ".gz" This sounds good to me. You could use something like 'file', but that isn't essential iirc, and anyway this tests actual functionality. I'm happy to implement this in a new branch. (TIL: the reverse of --auto-compress is on by default; 'tar [tx]f' will automatically determine the right algorithm.) Matt
Bug#1008091: sgid_home
Especially with the default mode already setgid (overriding this setting), it doesn't really add anything anymore.
Bug#627336: xfce4-power-manager: Not enough brightness levels
Control: affects -1 - src:linux On Thu, 19 May 2011 19:02:46 +0200 (CEST) Christophe TROESTLER wrote: > Package: xfce4-power-manager > Version: 1.0.10-3 FTR: This is fixed in version 1.3.1-1 uploaded to Debian on 2014-08-14. So afaict, this bug should've been closed a long time ago, although I have no idea on the status of bug #626542, but I'll let the maintainers so that out. My interest is in Debian kernel related bugs and I don't see how this affects the Debian kernel, so updating the metadata accordingly. signature.asc Description: This is a digitally signed message part.
Bug#1011339: [Pkg-javascript-devel] Bug#1011339: [Pkg-openssl-devel] Bug#1011339: openssl: missing errors strings on mipsel
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote: > Hi Sebastian, Hi Jérémy, > Any hint or idea about this ? Even wild ideas that I could try, > before I have to remove the files from mips. for some reason ossl_err_load_crypto_strings() is not invoked on mipsel but is invoked on amd64. Therefore the string is missing on mipsel because this function actually loads all the strings during lib init. Digging further, on amd64 is invoked once with OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG) and a second time with OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CRYPTO_STRINGS) so all the strings are loaded. On mipsel however I see OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG) OPENSSL_init_crypto(OPENSSL_INIT_ADD_ALL_CIPHERS | OPENSSL_INIT_ADD_ALL_DIGESTS) Now I need to take a nap before I can continue digging but this is my progress so far. > Jérémy Sebastian
Bug#1012275: closing 1012275
On Fri, 2022-06-10 at 05:09 +0900, Mike Hommey wrote: > There's a 101.0.1 on the way. I assume you mean "being built for Debian"? Anyway... thanks for taking care. :-) Cheers, Chris.
Bug#1012596: cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron
Package: cron-daemon-common Version: 3.0pl1-143 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package cron-daemon-common. Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ... Unpacking cron-daemon-common (3.0pl1-143) ... dpkg: error processing archive /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack): trying to overwrite '/etc/crontab', which is also in package bcron 0.11-9 Errors were encountered while processing: /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb Selecting previously unselected package cron-daemon-common. Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ... Unpacking cron-daemon-common (3.0pl1-143) ... dpkg: error processing archive /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack): trying to overwrite '/etc/cron.d/.placeholder', which is also in package systemd-cron 1.15.18-1 Errors were encountered while processing: /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb For bcron the conflicting file is only /etc/crontab For systemd-cron the conflicting files are /etc/cron.d/.placeholder /etc/cron.daily/.placeholder /etc/cron.hourly/.placeholder /etc/cron.monthly/.placeholder /etc/cron.weekly/.placeholder /etc/crontab These two alternative cron implementations need to start using cron-daemon-common for these shared files first before you can add the corresponding Breaks+Replaces against them. cheers, Andreas
Bug#1012595: faiss build-depends on obsolete package.
Package: faiss Version: 1.7.2-5 Severity: serious Justification: rc policy - "packages must be buildable within the same release" faiss build-depends on libblis3-serial which is no longer built by the blis source package. It is still present in unstable as a cruft package, but is completely gone from testing.
Bug#1012543: closed by Niels Thykier (Re: Bug#1012543: debhelper: setting HOME/XDG* for {override,execute_{before,after}}_dh_auto_*)
Control: reopen -1
On 09/06/2022 07.57, Debian Bug Tracking System wrote:
> This is already available in compat 13.
Nope. It's only available for stuff executed from dh_auto_*,
not for stuff executed from debian/rules (and not being an dh_auto_* command).
Output from 13.3.3~bpo10+1:
$ debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/srv/packaging/deb-src/1012543/pkg-1'
echo "HOME=$HOME"
HOME=/home/anbe
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
+ echo
HOME=/srv/packaging/deb-src/1012543/pkg-1/debian/.debhelper/generated/_source/home
HOME=/srv/packaging/deb-src/1012543/pkg-1/debian/.debhelper/generated/_source/home
make[1]: Leaving directory '/srv/packaging/deb-src/1012543/pkg-1'
debian/rules execute_before_dh_auto_build
make[1]: Entering directory '/srv/packaging/deb-src/1012543/pkg-1'
echo "HOME=$HOME"
HOME=/home/anbe
make[1]: Leaving directory '/srv/packaging/deb-src/1012543/pkg-1'
dh_auto_build
make -j1
make[1]: Entering directory '/srv/packaging/deb-src/1012543/pkg-1'
echo
"HOME=/srv/packaging/deb-src/1012543/pkg-1/debian/.debhelper/generated/_source/home"
HOME=/srv/packaging/deb-src/1012543/pkg-1/debian/.debhelper/generated/_source/home
make[1]: Leaving directory '/srv/packaging/deb-src/1012543/pkg-1'
debian/rules execute_after_dh_auto_build-arch
make[1]: Entering directory '/srv/packaging/deb-src/1012543/pkg-1'
echo "HOME=$HOME"
HOME=/home/anbe
make[1]: Leaving directory '/srv/packaging/deb-src/1012543/pkg-1'
dh_auto_test
create-stamp debian/debhelper-build-stamp
Andreas
pkg_1.tar.xz
Description: application/xz
Bug#1012227: webkitgtk: CPU usage
Source: webkit2gtk Version: 2.36.3-1 Followup-For: Bug #1012227 X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, running sudo ps -aux |grep WebKitWebProcess tmick4071296 53.0 9.5 88411428 683212 ? RLl 15:38 8:13 /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 35 tmick4073180 0.0 0.0 6432 2284 pts/1T15:52 0:00 grep WebKitWebProcess tmick4073195 0.0 0.0 6432 2284 pts/1S+ 15:54 0:00 grep WebKitWebProcess And stays there until I shutdown everything that uses it. Evolution, TOR, Firefox and reboot. It's like I'm running Windows 3.11 again. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1012594: RM: sbrsh -- RoQA; Orphaned; FTBFS; Upstream Inactive
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove Dear Debian FTP masters, Package sbrsh ( https://tracker.debian.org/pkg/sbrsh ) saw it last upload 13 years ago, has been orphaned due to maintainer retirement, and currently FTBFS due to low debhelper compat level. Its upstream has been inactive since 2011. Its application is for legacy hardware (e.g., Nokia 770) and becomes uselss nowadays. The package popcon is also very low (6). As a result, I believe this package is eligible for removal from Debian Sid. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1012593: freeipa-client-samba: "ipa-client-samba --uninstall" fails: No such file or directory: '/var/lib/samba/lock'
Package: freeipa-client-samba Version: 4.9.8-1~bpo11+1 Severity: minor Dear Maintainer, I had to clean up a broken run of ipa-client-samba so I could try again. Calling "ipa-client-samba --uninstall" yields: :/etc/samba# ipa-client-samba --uninstall Traceback (most recent call last): File "/usr/sbin/ipa-client-samba", line 15, in sys.exit(ipa_client_samba.run()) File "/usr/lib/python3/dist-packages/ipaclient/install/ipa_client_samba.py", line 537, in run uninstall(fstore, statestore, options) File "/usr/lib/python3/dist-packages/ipaclient/install/ipa_client_samba.py", line 455, in uninstall for tdb_file in os.listdir(smbpath) FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/samba/lock' On fedora that directory is part of samba-common - but the debian packages don't have that directory. I've just created that directory and "ipa-client-samba --uninstall" finished ok (and leaves the manually created directory alone). That looks like the packages needs different paths on Debian. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freeipa-client-samba depends on: ii cifs-utils2:6.11-3.1+deb11u1 ii freeipa-client4.9.8-1~bpo11+1 ii python3 3.9.2-3 ii python3-samba 2:4.13.13+dfsg-1~deb11u3 ii samba-common-bin 2:4.13.13+dfsg-1~deb11u3 ii smbclient 2:4.13.13+dfsg-1~deb11u3 ii tdb-tools 1.4.3-1+b1 ii winbind 2:4.13.13+dfsg-1~deb11u3 freeipa-client-samba recommends no packages. freeipa-client-samba suggests no packages. -- no debconf information
Bug#1012592: freeipa-client-samba: Cannot map BUILTIN\Guests to a group "nobody"
Package: freeipa-client-samba Version: 4.9.8-1~bpo11+1 Severity: normal Dear Maintainer, I'm trying to get a samba server connected to the freeipa servers I have. The documentation I found is: https://freeipa.readthedocs.io/en/latest/designs/adtrust/samba-domain-member.html When running "ipa-client-samba" I get: Cannot map BUILTIN\Guests to a group "nobody". Error: CalledProcessError(Command ['/usr/bin/net', 'groupmap', 'add', 'sid=S-1-5-32-546', 'unix group=nobody', 'type=builtin'] returned non-zero exit status 255: "Can't lookup UNIX group nobody\n") Traceback (most recent call last): File "/usr/sbin/ipa-client-samba", line 15, in sys.exit(ipa_client_samba.run()) File "/usr/lib/python3/dist-packages/ipaclient/install/ipa_client_samba.py", line 745, in run configure_default_groupmap(fstore, statestore, options, domains[0]) File "/usr/lib/python3/dist-packages/ipaclient/install/ipa_client_samba.py", line 386, in configure_default_groupmap ipautil.run(args) File "/usr/lib/python3/dist-packages/ipapython/ipautil.py", line 598, in run raise CalledProcessError( ipapython.ipautil.CalledProcessError: CalledProcessError(Command ['/usr/bin/net', 'groupmap', 'add', 'sid=S-1-5-32-546', 'unixgroup=nobody', ' type=builtin'] returned non-zero exit status 255: "Can't lookup UNIX group nobody\n") The expected output is to get a working samba configuration that uses freeipa as it's user backend. I've created a group "nobody" locally (Debian uses nogroup by default). With that group created, ipa-client-samba finishes ok and leaves a smb.conf that looks plausible (but until now not working ok - will investigate). Let's focus on the missing group for now. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freeipa-client-samba depends on: ii cifs-utils2:6.11-3.1+deb11u1 ii freeipa-client4.9.8-1~bpo11+1 ii python3 3.9.2-3 ii python3-samba 2:4.13.13+dfsg-1~deb11u3 ii samba-common-bin 2:4.13.13+dfsg-1~deb11u3 ii smbclient 2:4.13.13+dfsg-1~deb11u3 ii tdb-tools 1.4.3-1+b1 ii winbind 2:4.13.13+dfsg-1~deb11u3 freeipa-client-samba recommends no packages. freeipa-client-samba suggests no packages. -- no debconf information
Bug#1010576: (no subject)
Note that my previous message on https://bugs.debian.org/cgi-bin/ bugreport.cgi?bug=1010576 is incomplete, please see the referenced Message Part 2 (https://bugs.debian.org/cgi-bin/bugreport.cgi? att=1;bug=1010576;msg=25) for the full contents.
Bug#1012591: openmolcas: Enable HDF5 support
Package: openmolcas Version: 20.10-2 Severity: wishlist Dear Maintainer, It would be great if HDF5 support in openmolcas was enabled for convenient access to calculation results via a standard API, including quantities not printed in log files by default. Many thanks, João
Bug#1012589: libqt6serialbus6-dev: Should depend upon libqt6serialport6-dev
Package: libqt6serialbus6-dev Version: 6.2.4-2 Severity: normal X-Debbugs-Cc: lisan...@debian.org This package requires the libqt6serialport6 headers too. -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.18.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt6serialbus6-dev depends on: ii libqt6serialbus6 6.2.4-2 ii libqt6serialbus6-plugins 6.2.4-2 ii qt6-base-dev 6.2.4+dfsg-5 libqt6serialbus6-dev recommends no packages. libqt6serialbus6-dev suggests no packages. -- no debconf information
Bug#1012275: closing 1012275
On Thu, Jun 09, 2022 at 01:59:36PM +0200, Christoph Anton Mitterer wrote: > Could someone then possibly rebuild this with Julian’s patch, ASAP? > > Over a week with a likely remote code exploit hole in the browser of > any Debian (non-ESR) FF user, seems not so ideal, There's a 101.0.1 on the way.
Bug#1010576: (no subject)
I collected some information that might help with debugging, unfortunately some
output uses
German localization, I can translate these if needed:
In the shell where I started akonadi with akonadictl start, I got this output
(many
lines duplicated and removed for brevity):
"Das Objekt existiert nicht am Pfad
»/org/freedesktop/NetworkManager/ActiveConnection/2«"
[...]
org.kde.pim.kimap: Connection to server lost QAbstractSocket::HostNotFoundError
[...]
QIODevice::write (QSslSocket): device not open
org.kde.pim.kimap: Connection to server lost QAbstractSocket::NetworkError
org.kde.pim.kimap: Connection to server lost QAbstractSocket::NetworkError
org.kde.pim.kimap: Connection to server lost QAbstractSocket::HostNotFoundError
org.kde.pim.kimap: Connection to server lost QAbstractSocket::HostNotFoundError
[...]
"Das Objekt existiert nicht am Pfad
»/org/freedesktop/NetworkManager/ActiveConnection/2«"
[...]
QIODevice::write (QSslSocket): device not open
org.kde.pim.kimap: Connection to server lost
QAbstractSocket::RemoteHostClosedError
org.kde.pim.kimap: Connection to server lost QAbstractSocket::NetworkError
[...]
"Das Objekt existiert nicht am Pfad
»/org/freedesktop/NetworkManager/ActiveConnection/2«"
[...]
QIODevice::write (QSslSocket): device not open
"Das Objekt existiert nicht am Pfad
»/org/freedesktop/NetworkManager/ActiveConnection/2«"
[...]
QIODevice::write (QSslSocket): device not open
org.kde.pim.akonadiserver.search: Executing search
"kontact-2268689595-SearchSession"
org.kde.pim.akonadiserver.search: Search "kontact-2268689595-SearchSession"
done
(without remote search)
org.kde.pim.akonadiserver.search: Executing search
"kontact-2268689595-SearchSession"
org.kde.pim.akonadiserver.search: Search "kontact-2268689595-SearchSession"
done
(without remote search)
org.kde.pim.akonadiserver.search: Executing search
"kontact-2268689595-SearchSession"
[...]
org.kde.pim.akonadiserver: QueryBuilder::exec(): database reported transaction
timeout,
retrying transaction
org.kde.pim.akonadiserver: "Lock wait timeout exceeded; try restarting
transaction QMYSQL3:
Der Befehl konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver: QueryBuilder::exec(): database reported transaction
timeout,
retrying transaction
org.kde.pim.akonadiserver: "Lock wait timeout exceeded; try restarting
transaction QMYSQL3:
Der Befehl konnte nicht ausgeführt werden"
stracing akonadiserver shows this for example:
[pid 110942] write(10, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 110942] poll([{fd=10, events=POLLIN}, {fd=26, events=POLLIN}, {fd=28,
events=POLLIN},
{fd=36, events=POLLIN}, {fd=38, events=POLLIN}, {fd=42, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=52, events=POLLIN}, {fd=61, events=POLLIN}, {fd=69,
events=POLLIN},
{fd=76, events=POLLIN}, {fd=77, events=POLLIN}, {fd=79, events=POLLIN}, {fd=86,
events=POLLIN}, {fd=89, events=POLLIN}, {fd=90, events=POLLIN}, {fd=95,
events=POLLIN},
{fd=96, events=POLLIN}, {fd=99, events=POLLIN}, {fd=100, events=POLLIN},
{fd=110,
events=POLLIN}, {fd=114, events=POLLIN}, {fd=116, events=POLLIN}, {fd=121,
events=POLLIN}, {fd=122, events=POLLIN}, {fd=125, events=POLLIN}, {fd=126,
events=POLLIN}, {fd=129, events=POLLIN}, {fd=132, events=POLLIN}, {fd=136,
events=POLLIN}, {fd=142, events=POLLIN}, {fd=146, events=POLLIN}, ...], 46, 48)
= 1
([{fd=10, revents=POLLIN}])
[pid 110942] read(10, "\2\0\0\0\0\0\0\0", 16) = 8
[pid 110942] poll([{fd=10, events=POLLIN}, {fd=26, events=POLLIN}, {fd=28,
events=POLLIN},
{fd=36, events=POLLIN}, {fd=38, events=POLLIN}, {fd=42, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=52, events=POLLIN}, {fd=61, events=POLLIN}, {fd=69,
events=POLLIN},
{fd=76, events=POLLIN}, {fd=77, events=POLLIN}, {fd=79, events=POLLIN}, {fd=86,
events=POLLIN}, {fd=89, events=POLLIN}, {fd=90, events=POLLIN}, {fd=95,
events=POLLIN},
{fd=96, events=POLLIN}, {fd=99, events=POLLIN}, {fd=100, events=POLLIN},
{fd=110,
events=POLLIN}, {fd=114, events=POLLIN}, {fd=116, events=POLLIN}, {fd=121,
events=POLLIN}, {fd=122, events=POLLIN}, {fd=125, events=POLLIN}, {fd=126,
events=POLLIN}, {fd=129, events=POLLIN}, {fd=132, events=POLLIN}, {fd=136,
events=POLLIN}, {fd=142, events=POLLIN}, {fd=146, events=POLLIN}, ...], 46, 47)
= 0
(Timeout)
[...]
[pid 110942] read(89,
"\3\0\0\0\0\0\0\0u\0\20\0\0\377\377\377\377\377\377\377\377\0\0\0\0\1\0\0\0\25\0\0"...,
70) =
70
[pid 110942] write(10, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 110942] ppoll([{fd=89, events=POLLIN|POLLOUT}], 1, {tv_sec=30, tv_nsec=0},
NULL, 8) =
1 ([{fd=89, revents=POLLOUT}], left {tv_sec=29, tv_nsec=96833})
[pid 110942] write(89, "\3\0\0\0\0\0\0\0\365\0\0\0\0\377\377\377\377", 17) = 17
[pid 110942] write(10, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 110942] poll([{fd=10, events=POLLIN}, {fd=26, events=POLLIN}, {fd=28,
events=POLLIN},
{fd=36, events=POLLIN}, {fd=38, events=POLLIN}, {fd=42, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=52, events=POLLIN}, {fd=61, events=POLLIN}, {fd=69,
events=POLLIN},
Bug#1012587: /usr/share/doc/yubikey-manager empty
Package: yubikey-manager Version: 4.0.7-1 Severity: serious Justification: Policy 2.3, Policy 4.4 /usr/share/doc/yubikey-manager is completly empty. Thus, the required copyright and changelog files are missing. [3/5072]mh@drop:~ $ dpkg --list yubikey-manager | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---== ii yubikey-manager 4.0.7-1 all Python library and command line tool for configuring a YubiKey [4/5073]mh@drop:~ $ dpkg --listfiles yubikey-manager | cat /. /usr /usr/bin /usr/bin/ykman /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/ykman /usr/lib/python3/dist-packages/ykman/cli /usr/lib/python3/dist-packages/ykman/cli/__init__.py /usr/lib/python3/dist-packages/ykman/cli/__main__.py /usr/lib/python3/dist-packages/ykman/cli/aliases.py /usr/lib/python3/dist-packages/ykman/cli/apdu.py /usr/lib/python3/dist-packages/ykman/cli/config.py /usr/lib/python3/dist-packages/ykman/cli/fido.py /usr/lib/python3/dist-packages/ykman/cli/info.py /usr/lib/python3/dist-packages/ykman/cli/oath.py /usr/lib/python3/dist-packages/ykman/cli/openpgp.py /usr/lib/python3/dist-packages/ykman/cli/otp.py /usr/lib/python3/dist-packages/ykman/cli/piv.py /usr/lib/python3/dist-packages/ykman/cli/util.py /usr/share /usr/share/doc /usr/share/man /usr/share/man/man1 /usr/share/man/man1/ykman.1.gz /usr/share/doc/yubikey-manager [5/5074]mh@drop:~ $ ls -al /usr/share/doc/yubikey-manager total 0 drwxr-xr-x 1 root root0 Nov 1 2020 ./ drwxr-xr-x 1 root root 100K Jun 8 17:09 ../ [6/5075]mh@drop:~ $ Greetings Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.2-zgws1 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yubikey-manager depends on: ii pcscd 1.9.7-1 ii python3 3.10.4-1+b1 ii python3-click 8.0.3-1 ii python3-cryptography 3.4.8-2 ii python3-fido2 0.9.1-1 ii python3-ykman 4.0.7-1 Versions of packages yubikey-manager recommends: ii libyubikey-udev 1.20.0-3 yubikey-manager suggests no packages. -- no debconf information
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
On 09/06/2022 17:02, Jeroen Ploemen wrote: On Fri, 3 Jun 2022 13:08:55 +0100 Peter B wrote: Aside from the dbus xml stuff: what exactly do you mean by the comment in the GPL-3 license paragraph? I'm confused regarding GPL-3 & GPL-3+. We now have a License paragraph for GPL-3 that excludes later versions, but the full text in /usr/share/common-licenses/GPL-3 https://www.gnu.org/licenses/gpl-3.0.html both include it! The full text includes 'or any later version' in two places: first in paragraph 14, conditional on that being explicitly specified by the program in question; the other as part of an example or how one could apply the terms of the GPL. That example is explicitly outside of the terms and conditions set by the license. So yes, GPL-version-X-only is very much a thing. Thanks for the clarification I suspect some of the org.freedesktop.*.xml files on the other hand could be based directly on dbus specs [1] or similar generic interface definitions for use with qdbusxml2cpp, possibly autogenerated by qdbus along the lines of: `QT_SELECT=5 qdbus org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.DBus.Introspectable.Introspect` I've created separate Files paragraphs for each group of files. (I'm not sure what the impact of auto-generation is on the copyright. I notice that in [3], the author is the upstream application author, no reference to org.freedesktop) Typically, output produced by a program isn't itself covered by the license of said program. Producing a text on a GPL'ed editor doesn't put that text under the GPL. For org.freedesktop.Notifications.xml and DBus.ObjectManager, I don't see much of a reason to assume it originates from some other project; so those could reasonably fall directly under the default copyright paragraph for strawberry (i.e., no separate entry needed). Dropped the separate paragraph. The org.freedesktop.UDisk2.*.xml files should have their own (collective) entry, as the original for all of the udisk ones seems to be [1] with David Zeuthen as the sole copyright holder. Done Something similar applies to the org.mpris.*.xml (currently missing from d/copyright), except here the upstream seems to be [2] (debian copyright file at [3]). I've used the same as in [3] which matches [2] and included https://github.com/eonpatapon/mpDris2 in the comment. The org.kde.KGlobalAccel.*.xml appear to be based on files in the kglobalaccel project [4] (debian copyright at [5]) rather than the kde documentation, please update the entry to reflect that. The copyright in [5] has no specific paragraph for *.xml However, I found the files here https://invent.kde.org/frameworks/kglobalaccel/-/tree/master/src Again, they have no copyright themselves, but the associated cpp & h files do, so I have used that, with a comment to the link. Other than that, the shortname for the LGPL-2 license should have a plus symbol appended to reflect the 'any later version' option, in line with the standard shortnames documented by [6]. Done [1]https://github.com/storaged-project/udisks/blob/master/data/org.freedesktop.UDisks2.xml [2]https://github.com/eonpatapon/mpDris2/blob/5e5cdacea6e55544064f8b10e0b49bbe2aa044d9/src/mpDris2.in.py#L115 [3]https://salsa.debian.org/debian/mpdris2/-/blob/debian/latest/debian/copyright [4]https://sources.debian.org/src/kglobalaccel/5.94.0-1/src/ [5]https://tracker.debian.org/media/packages/k/kglobalaccel/copyright-5.94.0-1 [6]https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-short-name Updated on Salsa & Mentors, many thanks for all your help. Cheers, Peter B
Bug#867667: xsane: Preview window empty/unusable (maybe DE related)
Package: xsane Version: 0.999-12 Followup-For: Bug #867667 Hi After some more research it seams this bug could be somehow DE related: I normaly work in a fluxbox environment. And so I did today when I hit this bug (not for the first time!). As I was in a hurry with some documents I had to scan, I installed an other scanning application (simple scan) which did the job. On the same HW and same installation I later switched to a different WM/DE: lxqt When I started xsane while running lxqt, the preview window opened for a fraction of a second, but closed instantly. I could reopen it and it worked as it should. Even after closing and reopening xsane, the preview window opened and stayed open from now on. It even worked after a reboot. And, to my surprise, it now works in fluxbox, too. As if there never was a bug. Bug closed? NO! This malfunction occurred over the last two years again and again 9 out of 10 times I wanted to use xsane. And it is not clear why it happens and when it will happen again. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.2-4-siduction-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xsane depends on: ii libc62.33-7 ii libgimp2.0 2.10.30-1+b1 ii libglib2.0-0 2.72.2-2 ii libgtk2.0-0 2.24.33-2 ii libjpeg62-turbo 1:2.1.2-1 ii liblcms2-2 2.12~rc1-2 ii libpng16-16 1.6.37-5 ii libsane1 1.1.1-5 ii libtiff5 4.4.0-2 ii sensible-utils 0.0.17 ii xsane-common 0.999-12 ii zlib1g 1:1.2.11.dfsg-4 Versions of packages xsane recommends: ii chromium [www-browser] 102.0.5005.61-1 ii cups-client 2.4.2-1 ii falkon [www-browser]3.2.0+dfsg1-2 ii firefox [www-browser] 100.0.2-1 ii lynx [www-browser] 2.9.0dev.10-1 ii vivaldi-snapshot [www-browser] 5.3.2679.50-1 ii vivaldi-stable [www-browser]5.3.2679.51-1 ii w3m [www-browser] 0.5.3+git20220429-1+b1 Versions of packages xsane suggests: ii cuneiform1.1.0+dfsg-9 ii gimp 2.10.30-1+b1 ii gocr 0.52-3 ii gv 1:3.7.4-2+b1 pn hylafax-client | mgetty-fax ii ocrad0.28-2 -- no debconf information
Bug#1012582: libqt6serialbus6-dev: Should depend upon libqt6serialbus6-bin
The missing tool would be, in this case, /usr/lib/qt6/bin/canbusutil
Bug#1012585: bullseye-pu: package libintl-perl/1.26-3+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've uploaded libintl-perl/1.26-3+deb11u1 to bullseye in order to fix #1012570: What happened is that in the packaging overhaul for 1.26-3 we missed that one of the 2 code files in libintl-xs-perl was not installed, which makes the package useless. And the fix is equally easy: install the file :) The bug is also fixed in unstable in 1.26-4, where I additionally enabled the non-default tests to make sure that the XS part works. I've left this out for bullseye obviously. The complete debdiff is: #v+ diff -Nru libintl-perl-1.26/debian/changelog libintl-perl-1.26/debian/changelog - --- libintl-perl-1.26/debian/changelog2021-01-03 01:56:12.0 +0100 +++ libintl-perl-1.26/debian/changelog 2022-06-09 21:14:57.0 +0200 @@ -1,3 +1,12 @@ +libintl-perl (1.26-3+deb11u1) bullseye; urgency=medium + + * Team upload. + * Install the missing gettext_xs.pm file. +Thanks to Xan Charbonnet for the bug report. +(Closes: #1012570) + + -- gregor herrmann Thu, 09 Jun 2022 21:14:57 +0200 + libintl-perl (1.26-3) unstable; urgency=medium * Take over for the Debian Perl Group; Closes: #945988 -- RFA/ITA diff -Nru libintl-perl-1.26/debian/libintl-xs-perl.install libintl-perl-1.26/debian/libintl-xs-perl.install - --- libintl-perl-1.26/debian/libintl-xs-perl.install 2021-01-03 01:56:12.0 +0100 +++ libintl-perl-1.26/debian/libintl-xs-perl.install2022-06-09 21:14:57.0 +0200 @@ -1,2 +1,3 @@ usr/lib/* usr/lib/ +usr/share/perl5/Locale/gettext_xs.pm usr/share/perl5/Locale/ usr/share/man/man3/Locale::gettext_xs.3pm usr/share/man/man3/ #v- As this has not been noticed since the bullseye release, I guess there is no particular hurry to push this through stable-updates, but having it in the next point release would be appreciated. Thanks in advance, gregor -BEGIN PGP SIGNATURE- iQKSBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmKiR2ZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbeXA/4pdOHte5zlSeymjJdejkBXLdGFmKdEMGi9UHOBr6A6gASju4Siy27dxOz H0AQDgfR1GHbCkb7D/uEEQ0MhLNDujxoNi7eSLDQctd/k50EQU4HhOWIYApldVf5 YivQkudhUaPbqE4osbOx7jiML9AP9PmQLKnjjM9k0Cc20bmoqeg5y+MoPtcI2s9+ /x4QXTBXGVtqAqvRKkg9ST0cwirzjYT9LAXTc85q2lzzgJUosT06cZgKf0DKcNJb rhDCQRTawGqXeyM/Aq3e1ujLSU19DuLDq3Vpk3ngC7nhIBWDFDghQqTXlbT0ew66 W+YFU0iRkGYfts83lqRTJ4fvqydbHkH8zyp14JCWv7Z1oTfjs9OEy1F2YIyzBjlp Qa+bM1+oJwJ41Yh9jRDKjqRTSEuYdZWqpRZ6HIlG3ChGXrX32W05Xzw9QZUxkvIM GfZec8HYZtYdKnXHDj0gLDcxXXdQdWwjJYEPPPHS0ScPPyCDBiY8gehAOYYvyLUf le5ffXb0XMCSvLliZKIKMcvqqHHBaBTGQMTKWUYDs1dvHtr+r7O7pEmRHz26506S w2ucObjmzkPUzubumoJg0uKsvBPIU0z/JAz3ZYs7VgZEkEwug+vxWb96gJX18+vu QsswrFfv0pFiOdP7/tOs8SQyHcQXq6xZLEOOTZydOAhxRJSdKg== =MXhI -END PGP SIGNATURE-
Bug#1012586: /usr/bin/conky: Memory Displayed is incorrect
Package: conky-all Version: 1.12.2-2 Severity: normal File: /usr/bin/conky X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, Memory for system and Swap is wrong, Conky shows I have 14.0 GB Swap and 6.81 GB of Ram. I actually have 8 GB of RAM and 16 GB of swap, as the following shows: free totalusedfree shared buff/cache available Mem: 7140112 2460948 2409548 25744 2269616 4546180 Swap: 14648316 166562012982696 $ sudo dmesg | grep Memory: [0.058331] Memory: 2069896K/7299524K available (12294K kernel code, 2946K rwdata, 8460K rodata, 2496K init, 5012K bss, 301872K reserved, 0K cma-reserved) $ cat /proc/meminfo MemTotal:7140112 kB MemFree: 2405496 kB MemAvailable:4543128 kB Buffers: 238856 kB Cached: 1236676 kB SwapCached:97176 kB Active: 1391124 kB Inactive:2107556 kB Active(anon): 435084 kB Inactive(anon): 1626240 kB Active(file): 956040 kB Inactive(file): 481316 kB Unevictable: 14776 kB Mlocked: 14776 kB SwapTotal: 14648316 kB SwapFree: 12984232 kB Dirty: 124 kB Writeback: 0 kB AnonPages: 1970696 kB Mapped: 305956 kB Shmem: 25744 kB KReclaimable: 795064 kB Slab: 953368 kB SReclaimable: 795064 kB SUnreclaim: 158304 kB KernelStack: 14992 kB PageTables:41640 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:18218372 kB Committed_AS: 10797804 kB VmallocTotal: 34359738367 kB VmallocUsed: 66700 kB VmallocChunk: 0 kB Percpu: 4816 kB HardwareCorrupted: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 1635144 kB DirectMap2M: 5664768 kB DirectMap1G: 0 kB -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages conky-all depends on: ii libaudclient2 3.5~rc2-1+b1 ii libc6 2.33-7 ii libcairo2 1.16.0-5 ii libcurl3-gnutls 7.83.0-1 ii libdbus-glib-1-2 0.112-2 ii libgcc-s1 12.1.0-2 ii libglib2.0-0 2.72.1-1 ii libical3 3.0.14-1+b1 ii libimlib2 1.7.4-2 ii libircclient1 1.9-1+b2 ii libiw30 30~pre9-13.1 ii liblua5.3-0 5.3.6-1 ii libncurses6 6.3+20220423-2 ii libpulse0 15.0+dfsg1-4 ii librsvg2-22.54.3+dfsg-1 ii libstdc++612.1.0-2 ii libtinfo6 6.3+20220423-2 ii libx11-6 2:1.7.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.4-1 ii libxfixes31:6.0.0-1 ii libxft2 2.3.4-1 ii libxinerama1 2:1.1.4-3 ii libxml2 2.9.14+dfsg-1 ii libxnvctrl0 470.103.01-2 conky-all recommends no packages. Versions of packages conky-all suggests: pn apcupsd ii audacious 4.1-2 ii moc1:2.6.0~svn-r3005-1 ii mpd0.23.6-1+b1 -- no debconf information
Bug#1012584: ITP: blag -- blog-aware, static side generator
Package: wnpp Severity: wishlist Owner: Bastian Venthur X-Debbugs-Cc: debian-de...@lists.debian.org, vent...@debian.org * Package name: blag Version : 1.2 Upstream Author : Bastian Venthur * URL : https://github.com/venthur/blag * License : MIT Programming Lang: Python Description : blog-aware, static side generator Blag is a blog-aware, static site generator, written in Python. It supports the following features: * Write content in Markdown * Theming support using Jinja2 templates * Generation of Atom feeds for blog content * Fenced code blocks and syntax highlighting using Pygments * Integrated devserver * Available on PyPI
Bug#1012583: neofetch: Memory displayed is way off
Package: neofetch Version: 7.1.0-4 Severity: normal X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** What led up to the situation? ran neofetch from CLI What exactly did you do (or not do) that was effective (or ineffective)? Received results. What was the outcome of this action? It displays this info: _,met$gg. tmick@DebianTim ,g$$$P. --- ,g$$P" """Y$$.".OS: Debian GNU/Linux bookworm/sid x86_64 ,$$P' `$$$. Host: MS-7721 9.0 ',$$P ,ggs. `$$b: Kernel: 5.17.0-1-rt-amd64 `d$$' ,$P"' .$$$Uptime: 1 day, 1 hour, 52 mins $$P d$' ,$$PPackages: 5983 (dpkg), 9 (snap) $$: $$. -,d$$'Shell: bash 5.1.16 $$; Y$b._ _,d$P' Resolution: 1366x768 Y$$.`.`"YP"' DE: GNOME 42.1 `$$b "-.__ WM: Mutter `Y$$WM Theme: Adwaita `Y$$. Theme: Adwaita [GTK2/3] `$$b.Icons: Adwaita [GTK2/3] `Y$$b. Terminal: kgx `"Y$b._ CPU: AMD A6-7400K Radeon R5 2C+4G (2) @ 4.092GHz `"""GPU: AMD ATI Radeon R5 Graphics Memory: 3089MiB / 6972MiB What outcome did you expect instead?the correct information to be shown, it should be the same as one of these commands: free totalusedfree shared buff/cache available Mem: 7140112 2460948 2409548 25744 2269616 4546180 Swap: 14648316 166562012982696 sudo dmesg | grep Memory: [0.058331] Memory: 2069896K/7299524K available (12294K kernel code, 2946K rwdata, 8460K rodata, 2496K init, 5012K bss, 301872K reserved, 0K cma-reserved) cat /proc/meminfo MemTotal:7140112 kB MemFree: 2405496 kB MemAvailable:4543128 kB Buffers: 238856 kB Cached: 1236676 kB SwapCached:97176 kB Active: 1391124 kB Inactive:2107556 kB Active(anon): 435084 kB Inactive(anon): 1626240 kB Active(file): 956040 kB Inactive(file): 481316 kB Unevictable: 14776 kB Mlocked: 14776 kB SwapTotal: 14648316 kB SwapFree: 12984232 kB Dirty: 124 kB Writeback: 0 kB AnonPages: 1970696 kB Mapped: 305956 kB Shmem: 25744 kB KReclaimable: 795064 kB Slab: 953368 kB SReclaimable: 795064 kB SUnreclaim: 158304 kB KernelStack: 14992 kB PageTables:41640 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:18218372 kB Committed_AS: 10797804 kB VmallocTotal: 34359738367 kB VmallocUsed: 66700 kB VmallocChunk: 0 kB Percpu: 4816 kB HardwareCorrupted: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 1635144 kB DirectMap2M: 5664768 kB DirectMap1G: 0 kB Thanks -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled neofetch depends on no packages. Versions of packages neofetch recommends: ii caca-utils 0.99.beta19-6 ii chafa1.10.3-1 ii imagemagick 8:6.9.11.60+dfsg-1.3+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3+b2 ii jp2a 1.1.1-1 ii libsixel-bin 1.10.3-3 ii pciutils 1:3.7.0-6 ii w3m-img 0.5.3+git20220429-1 neofetch suggests no packages. -- no debconf information
Bug#1012582: libqt6serialbus6-dev: Should depend upon libqt6serialbus6-bin
Package: libqt6serialbus6-dev Version: 6.2.4-2 Severity: normal X-Debbugs-Cc: lisan...@debian.org, mity...@debian.org While using CMake and a Qt Serial Bus-based project I found out that the CMake files in libqt6serialbus6-dev requires the binaries of libqt6serialbus6-bin. This might be also valid for Qt 5. -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.18.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt6serialbus6-dev depends on: ii libqt6serialbus6 6.2.4-2 ii libqt6serialbus6-plugins 6.2.4-2 ii qt6-base-dev 6.2.4+dfsg-5 libqt6serialbus6-dev recommends no packages. libqt6serialbus6-dev suggests no packages. -- no debconf information
Bug#1012191: tzdata: /usr/share/zoneinfo/leap-seconds.list will expire on 2022-06-28 in Debian Stable 11.x/Bullseye
control: tag -1 + confirmed On 2022-06-08 16:08, Paul Slootman wrote: > severity 1012191 important > thanks > > The time is ticking, and the leap second data is now due to expire in 20 > days. An update is planned before the deadline. > There is a 2022a-1 version in testing. Could this be included in > bullseye-updates and perhaps buster-updates? I've downloaded it manually > and it seems fine in bullseye. No you do not want to do that. 2022a-1 includes changes we might not want in a stable update. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1012581: Warn when copyright contains license MIT instead of more specific Expat or X11
Package: lintian X-Debbugs-Cc: kwestover...@gmail.com Version: 2.114.0 Severity: wishlist Tags: upstream Dear maintainer, Many packages' copyright files use the license name MIT, even though that's a name used for two slightly different licenses, Expat and X11. Lintian should warn maintainers who use this broad term instead of the specific license (Expat or X11) that the software actually uses. Regards, -- Ben Westover System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.17.0-3-arm64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils2.38-4 ii bzip2 1.0.8-5 ii diffstat1.64-1 ii dpkg1.21.8 ii dpkg-dev1.21.8 ii file1:5.41-4 ii gettext 0.21-6 ii gpg 2.2.35-2 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.40+b1 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl0.48-1 ii libclass-xsaccessor-perl1.19-3+b8 ii libclone-perl 0.45-1+b2 ii libconfig-tiny-perl 2.28-1 ii libconst-fast-perl 0.014-1.1 ii libcpanel-json-xs-perl 4.29-1 ii libdata-dpath-perl 0.58-1 ii libdata-validate-domain-perl0.10-1.1 ii libdata-validate-uri-perl 0.07-2 ii libdevel-size-perl 0.83-1+b3 pn libdigest-sha-perl ii libdpkg-perl1.21.8 ii libemail-address-xs-perl1.04-1+b4 ii libfile-basedir-perl0.09-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl1.06-1.1 ii libhtml-html5-entities-perl 0.004-1.1 ii libio-interactive-perl 1.023-1 ii libio-prompt-tiny-perl 0.003-1 ii libipc-run3-perl0.048-2 ii libjson-maybexs-perl1.004003-1 ii liblist-compare-perl0.55-1 ii liblist-someutils-perl 0.58-1 ii liblist-utilsby-perl0.12-1 ii libmoo-perl 2.005004-3 ii libmoox-aliases-perl0.001006-2 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl 0.122-1 ii libperlio-gzip-perl 0.19-1+b8 ii libperlio-utf8-strict-perl 0.009-1+b1 ii libproc-processtable-perl 0.634-1+b1 ii libsereal-decoder-perl 4.023+ds-1 ii libsereal-encoder-perl 4.023+ds-1 ii libsort-versions-perl 1.62-1 ii libsyntax-keyword-try-perl 0.27-1 ii libterm-readkey-perl2.38-1+b3 ii libtext-glob-perl 0.11-2 ii libtext-levenshteinxs-perl 0.03-4+b9 ii libtext-markdown-discount-perl 0.13-1+b1 ii libtext-xslate-perl 3.5.9-1+b1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b4 ii libtimedate-perl2.3300-2 ii libunicode-utf8-perl0.62-1+b3 ii liburi-perl 5.10-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 ii libyaml-libyaml-perl0.83+ds-1+b1 ii lzip1.23-3 ii lzop1.04-2 ii man-db 2.10.2-1 ii patchutils 0.4.2-1 ii perl [libencode-perl] 5.34.0-4 ii t1utils 1.41-4 ii unzip 6.0-26 ii xz-utils5.2.5-2.1 lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch pn libtext-template-perl -- no debconf information OpenPGP_signature Description: OpenPGP digital signature
Bug#1012580: ITP: sphinxcontrib-trio -- Make Sphinx better at documenting Python functions and methods
Package: wnpp X-Debbugs-Cc: debian-de...@lists.debian.org Owner: Ben Westover X-Debbugs-Cc: kwestover...@gmail.com Severity: wishlist * Package name: sphinxcontrib-trio Version : 1.1.2 Upstream Author : Nathaniel J. Smith * URL : https://github.com/python-trio/sphinxcontrib-trio * License : Expat or Apache-2.0 Programming Lang: Python Description : Make Sphinx better at documenting Python functions and methods This sphinx extension helps you document Python code that uses async/await, or abstract methods, context managers, generators, etc. It works by making sphinx's regular directives for documenting Python functions and methods smarter and more powerful. I'm packaging this because discord.py depends on it. I am going to maintain it inside the Python team. -- Ben Westover OpenPGP_signature Description: OpenPGP digital signature
Bug#1012570: libintl-xs-perl: gettext_xs never used
Control: severity -1 grave # makes package useless On Thu, 09 Jun 2022 11:21:04 -0500, Xan Charbonnet wrote: > I note that the file gettext_xs.pm was removed for all architectures except > mips between buster and bullseye. Thank you very much for spotting and reporting this! > Am I missing something in how libintl-xs-perl is supposed to be used? Nope, we were missing something -- the installation of gettext_xs.pm went missing when we revamped the packaging of the package for 1.26-3. I'm working on getting this fixed in unstable and stable. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1012560: More info
On Thu, 9 Jun 2022 11:39:44 +0200 =?UTF-8?Q?Krzysztof_Krzy=C5=BCaniak?= wrote: > Looks like this change should fix this but this will make code incompatible > with kernels older that 5.18. > > https://patchwork.kernel.org/project/linux-acpi/patch/5790600.lOV4Wx5bFT@kreacher/ FYI, this patch should fix it and is backward compatible with older kernels: https://www.mail-archive.com/arch-commits@lists.archlinux.org/msg321180.html
Bug#1012579: gajim: No connection - Status stays in Connecting
Package: gajim Version: 1.4.0-1 Severity: normal X-Debbugs-Cc: stefan.kr...@posteo.de Dear Maintainer, no connection to prosody Server. Connection status stays in "Connecting". I have checked the issue with upstream. The reason may also related to the warning "gajim.c.m.roster ver attribute missing" and requires a version of python3-nbxmpp greater than 3.0.1-1. This issue should be fixed in version > 3.0.1.
Bug#1012578: linux-image-5.18.0-1-amd64: 05e3:0722 Genesys Logic, Inc. SD/MMC card reader doesn't see the card
Package: src:linux Version: 5.18.2-1 Severity: normal Dear Maintainer, that is card reader itself is being seen by the system: lsusb -d 05e3:0722 Bus 001 Device 004: ID 05e3:0722 Genesys Logic, Inc. SD/MMC card reader but it doesn't see the card: dmesg -T | grep sdc [Thu Jun 9 15:30:09 2022] sd 7:0:0:0: [sdc] Media removed, stopped polling [Thu Jun 9 15:30:09 2022] sd 7:0:0:0: [sdc] Attached SCSI removable disk mount /dev/sdc /mnt/sdcard mount: /mnt/sdcard: no medium found on /dev/sdc. I have explored the driver: modinfo usb-storage | grep -i v05e3p0722 and it looks like there is no support for this device (no output from command above), but I am not sure it is the case. In any case the system doesn't react nighter on inserting or removing the card. I have recompiled this module where supported device 05e3:0723 was replaced by 05e3:0722 without any changes in system behaviour, though I understand it is not the right method. I have checked this card on another system (notebook) and it works properly. Here is additional information that may help: udevadm info /dev/bus/usb/001/004 P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4 M: 1-1.4 R: 4 U: usb T: usb_device D: c 189:3 N: bus/usb/001/004 L: 0 V: usb E: DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4 E: DEVNAME=/dev/bus/usb/001/004 E: DEVTYPE=usb_device E: DRIVER=usb E: PRODUCT=5e3/722/9843 E: TYPE=0/0/0 E: BUSNUM=001 E: DEVNUM=004 E: MAJOR=189 E: MINOR=3 E: SUBSYSTEM=usb E: USEC_INITIALIZED=2168312 E: ID_VENDOR=Generic E: ID_VENDOR_ENC=Generic E: ID_VENDOR_ID=05e3 E: ID_MODEL=USB_Storage E: ID_MODEL_ENC=USB\x20Storage E: ID_MODEL_ID=0722 E: ID_REVISION=9843 E: ID_SERIAL=Generic_USB_Storage_9843 E: ID_SERIAL_SHORT=9843 E: ID_BUS=usb E: ID_USB_INTERFACES=:080650: E: ID_VENDOR_FROM_DATABASE=Genesys Logic, Inc. E: ID_MODEL_FROM_DATABASE=SD/MMC card reader E: ID_PATH=pci-:00:1a.0-usb-0:1.4 E: ID_PATH_TAG=pci-_00_1a_0-usb-0_1_4 E: ID_FOR_SEAT=usb-pci-_00_1a_0-usb-0_1_4 E: TAGS=:seat: E: CURRENT_TAGS=:seat: udevadm info /dev/sdc P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host7/target7:0:0/7:0:0:0/block/sdc M: sdc U: block T: disk D: b 8:32 N: sdc L: 0 S: disk/by-path/pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0 S: disk/by-diskseq/16 S: disk/by-id/usb-Generic_STORAGE_DEVICE_9843-0:0 Q: 16 E: DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host7/target7:0:0/7:0:0:0/block/sdc E: DEVNAME=/dev/sdc E: DEVTYPE=disk E: DISKSEQ=16 E: MAJOR=8 E: MINOR=32 E: SUBSYSTEM=block E: USEC_INITIALIZED=3242303 E: ID_VENDOR=Generic E: ID_VENDOR_ENC=Generic\x20 E: ID_VENDOR_ID=05e3 E: ID_MODEL=STORAGE_DEVICE E: ID_MODEL_ENC=STORAGE\x20DEVICE\x20\x20 E: ID_MODEL_ID=0722 E: ID_REVISION=9843 E: ID_SERIAL=Generic_STORAGE_DEVICE_9843-0:0 E: ID_SERIAL_SHORT=9843 E: ID_TYPE=disk E: ID_INSTANCE=0:0 E: ID_BUS=usb E: ID_USB_INTERFACES=:080650: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=usb-storage E: ID_PATH=pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0 E: ID_PATH_TAG=pci-_00_1a_0-usb-0_1_4_1_0-scsi-0_0_0_0 E: UDISKS_PRESENTATION_NOPOLICY=0 E: DEVLINKS=/dev/disk/by-path/pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0 /dev/disk/by-diskseq/16 /dev/disk/by-id/usb-Generic_STORAGE_DEVICE_9843-0:0 E: TAGS=:systemd: E: CURRENT_TAGS=:systemd: lsusb -D /dev/bus/usb/001/004 Device: ID 05e3:0722 Genesys Logic, Inc. SD/MMC card reader Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0722 SD/MMC card reader bcdDevice 98.43 iManufacturer 3 Generic iProduct4 USB Storage iSerial 2 9843 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType
Bug#1012577: update puppetdb to latest upstream (currently 6.21.0)
Source: puppetdb Version: 6.2.0-5 Severity: wishlist We're lagging quite a bit behind upstream, and should update to follow the latest. This is a meta-ticket tracking that effort, which should close a bunch of other issues. -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1012576: onnx: FTBFS with protobuf 3.20.1+
Source: onnx Version: 1.7.0+dfsg-3.1 Severity: important Usertags: protobuf3_20 Tags: ftbfs upstream bookworm sid patch Hi, I would like to start the Protobuf 3.20.1 transition in a few days. Your package is currently FTBFS for a simple reason. The function SetTotalBytesLimit doesn't have a second argument for long (protobuf 3.6) and it was ignored previously. Now it's finally removed and hence your package doesn't build anymore. As it was ignored for a long time, the fix is easy, just remove that argument when calling the mentioned function. Patch is attached, please apply it soon. Thanks, Laszlo/GCS Description: fix Protobuf FTBFS SetTotalBytesLimit no longer has second argument. Author: Laszlo Boszormenyi (GCS) Forwarded: no Last-Update: 2022-06-06 --- --- onnx-1.7.0+dfsg.orig/onnx/proto_utils.h +++ onnx-1.7.0+dfsg/onnx/proto_utils.h @@ -31,7 +31,7 @@ bool ParseProtoFromBytes(Proto* proto, c // respectively. ::google::protobuf::io::ArrayInputStream input_stream(buffer, static_cast(length)); ::google::protobuf::io::CodedInputStream coded_stream(_stream); - coded_stream.SetTotalBytesLimit((2048LL << 20) - 1, 512LL << 20); + coded_stream.SetTotalBytesLimit((2048LL << 20) - 1); return proto->ParseFromCodedStream(_stream); }
Bug#1012564: [Pkg-openssl-devel] Bug#1012564: openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7
On 2022-06-09 23:18:07 [+0930], Arthur Marsh wrote: … > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > > Upgrading openssl, libssl3 to 3.0.3-7 from 3.0.3-6 on host system prevented > ckermit 305~alpha07-1+b1 on client system with libssl3 3.0.3-6 from > connecting to telnetd-ssl 0.17.41+0.2-3.3 on host system. > > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I first downgraded libssl3 from 3.0.3-7 on host system to 3.0.3-6 but that > didn't resolve the issue. After I downgraded openssl from 3.0.3-7 to 3.0.3-6 > on the host system, I was able to connect from the client system which still > runs openssl 3.0.3-6 and libssl3 3.0.3-6. How do I setup a telnet-ssl server to begin with? I installed telnetd-ssl from testing just to be sure and telnet -z ssl localhost does nothing. Any idea? Sebastian
Bug#1012573: harvest-tools: FTBFS with protobuf 3.20.1+
Source: harvest-tools
Version: 1.3-7
Severity: important
Usertags: protobuf3_20
Tags: ftbfs upstream bookworm sid patch
Hi,
I would like to start the Protobuf 3.20.1 transition in a few days.
Your package is currently FTBFS for a simple reason. The function
SetTotalBytesLimit doesn't have a second argument for long (protobuf
3.6) and it was ignored previously. Now it's finally removed and hence
your package doesn't build anymore.
As it was ignored for a long time, the fix is easy, just remove that
argument when calling the mentioned function. Patch is attached,
please apply it soon.
Thanks,
Laszlo/GCS
Description: fix Protobuf FTBFS
SetTotalBytesLimit no longer has second argument.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-06-06
---
--- harvest-tools-1.3.orig/src/harvest/HarvestIO.cpp
+++ harvest-tools-1.3/src/harvest/HarvestIO.cpp
@@ -208,7 +208,7 @@ bool HarvestIO::loadHarvestProtocolBuffe
GzipInputStream gz(_input);
CodedInputStream coded_input();
- coded_input.SetTotalBytesLimit(INT_MAX, INT_MAX);
+ coded_input.SetTotalBytesLimit(INT_MAX);
if ( ! harvest.ParseFromCodedStream(_input) )
{
Bug#1012575: libarcus: FTBFS with protobuf 3.20.1+
Source: libarcus
Version: 4.13.0-2
Severity: important
Usertags: protobuf3_20
Tags: ftbfs upstream bookworm sid patch
Hi,
I would like to start the Protobuf 3.20.1 transition in a few days.
Your package is currently FTBFS for a simple reason. The function
SetTotalBytesLimit doesn't have a second argument for long (protobuf
3.6) and it was ignored previously. Now it's finally removed and hence
your package doesn't build anymore.
As it was ignored for a long time, the fix is easy, just remove that
argument when calling the mentioned function. Patch is attached,
please apply it soon.
Thanks,
Laszlo/GCS
Description: fix Protobuf FTBFS
SetTotalBytesLimit no longer has second argument.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-06-06
---
--- libarcus-4.13.0.orig/src/Socket_p.h
+++ libarcus-4.13.0/src/Socket_p.h
@@ -548,7 +548,7 @@ namespace Arcus
google::protobuf::io::ArrayInputStream array(wire_message->data, wire_message->size);
google::protobuf::io::CodedInputStream stream();
-stream.SetTotalBytesLimit(message_size_maximum, message_size_warning);
+stream.SetTotalBytesLimit(message_size_maximum);
if(!message->ParseFromCodedStream())
{
error(ErrorCode::ParseFailedError, "Failed to parse message:" + std::string(wire_message->data));
Bug#1012574: ignition-msgs5: FTBFS with protobuf 3.20.1+
Source: ignition-msgs5
Version: 5.8.1+ds-2
Severity: important
Usertags: protobuf3_20
Tags: ftbfs upstream bookworm sid patch
Hi,
I would like to start the Protobuf 3.20.1 transition in a few days.
Your package is currently FTBFS for a simple reason. The function
SetTotalBytesLimit doesn't have a second argument for long (protobuf
3.6) and it was ignored previously. Now it's finally removed and hence
your package doesn't build anymore.
As it was ignored for a long time, the fix is easy, just remove that
argument when calling the mentioned function. Patch is attached,
please apply it soon.
Thanks,
Laszlo/GCS
Description: fix Protobuf FTBFS
SetTotalBytesLimit no longer has second argument.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-06-06
---
--- ignition-msgs5-5.8.1+ds.orig/src/Generator.cc
+++ ignition-msgs5-5.8.1+ds/src/Generator.cc
@@ -67,7 +67,7 @@ Generator::~Generator()
/
bool Generator::Generate(const FileDescriptor *_file,
- const string &/*_parameter*/,
+ const std::string &/*_parameter*/,
OutputDirectory *_generatorContext,
std::string * /*_error*/) const
{
--- ignition-msgs5-5.8.1+ds.orig/src/Generator.hh
+++ ignition-msgs5-5.8.1+ds/src/Generator.hh
@@ -44,9 +44,9 @@ class Generator : public CodeGenerator
/// \param[in] _generatorContext Output directory.
/// \param[in] _error Unused string value
public: virtual bool Generate(const FileDescriptor *_file,
- const string &_parameter,
+ const std::string &_parameter,
OutputDirectory *_generatorContext,
- string *_error) const;
+ std::string *_error) const;
// private: GOOGLE_DISALLOW_EVIL_CONSTRUCTORS(Generator);
};
Bug#1012572: android-platform-frameworks-base: FTBFS with protobuf 3.20.1+
Source: android-platform-frameworks-base
Version: 1:10.0.0+r36-5
Severity: important
Usertags: protobuf3_20
Tags: ftbfs upstream bookworm sid patch
Hi,
I would like to start the Protobuf 3.20.1 transition in a few days.
Your package is currently FTBFS for a simple reason. The function
SetTotalBytesLimit doesn't have a second argument for long (protobuf
3.6) and it was ignored previously. Now it's finally removed and hence
your package doesn't build anymore.
As it was ignored for a long time, the fix is easy, just remove that
argument when calling the mentioned function. Patch is attached,
please apply it soon.
Thanks,
Laszlo/GCS
Description: fix Protobuf FTBFS
SetTotalBytesLimit no longer has second argument.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-06-06
---
--- android-platform-frameworks-base-10.0.0+r36.orig/tools/aapt2/io/Util.h
+++ android-platform-frameworks-base-10.0.0+r36/tools/aapt2/io/Util.h
@@ -131,8 +131,7 @@ class ProtoInputStreamReader {
template bool ReadMessage(T *message_lite) {
ZeroCopyInputAdaptor adapter(in_);
google::protobuf::io::CodedInputStream coded_stream();
-coded_stream.SetTotalBytesLimit(std::numeric_limits::max(),
-coded_stream.BytesUntilTotalBytesLimit());
+coded_stream.SetTotalBytesLimit(std::numeric_limits::max());
return message_lite->ParseFromCodedStream(_stream);
}
Bug#896916:
On Thu, Jun 09, 2022 at 11:53:20AM -0400, Matt Barry wrote: > On Wed, 2022-06-08 at 11:59 +0200, Marc Haber wrote: > > On Wed, Jun 08, 2022 at 12:34:14AM -0400, Matt Barry wrote: > > > tags -1 + confirmed patch > > > thanks > > > > How about zstd and the other hip compressors? > > Heh. I was thinking about whether to bother with this one. A couple > of factors: > > * adding zstd in the same fashion will take ~ 2 minutes > * there are, imo, no additional algorithms worth considering, so it > isn't a bottomless well of feature requests > * I guess the ideal for users would be a config item that controls the > order of selection: > > BACKUP_COMPRESS=xz gz zstd # eg. would never try bzip2 > > I can't imagine it getting more complicated than that.. Currently, the code looks like we are choosing the filename and the method of compression: if bzip2 exists, we use that. Otherwise, if gzip exists, we use that. Thankfully, we never documented this precedence, our docs just say that the backup file is called username.tar(.gz|.bz2). Christoph suggested using tar's --auto-compress option which automatically chooses the compress program depeding on the target file's suffix. How about doing the following: - we introduce a new option --backup-suffix, accepting things like ".bz2" or "xz" - we use that to generate the target file name, adding a period if the input doesnt start with one - use tar --auto-compress to create the file Unfortunately, if tar doesnt recognize the suffix, it'll happily generate foo.tar.baz as a regular tar archive. Otoh, if a compressor is selected that is not installed, tar will give a 127 exit code. I'd recommend the following: - invoke tar --create --auto-compress --file /tmp/foo.tar.suffix --directory / usr/sbin/deluser - if exit code 127 (compressor known, but not installed): - print diagnostic - set suffix to ".gz" (gzip is essential and guaranteed to exist) - if exit code != 127 - invoke tar --create --file /tmp/foo.tar --directory / usr/sbin/deluser - check whether foo.tar and foo.tar.sufffix are identical (that happens when the tar file suffix does not match a known compressor) - if identical (unknown compressor given) - print diagnostic - set suffix to ".gz" If there is any better way to find out whether tar has actually printed a compressed file without creating more dependencies, please, use that. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1012571: --no-auto-compress does not work when decompressing
Package: tar Version: 1.34+dfsg-1 Severity: minor File: /bin/tar Hi, I have foo.tar.xz which file(1) correctly flags as "XZ compressed data" tar --extract --file foo.tar.xz happily decompresses this. This is already a surprise. I'd have expected to be able to use -no-auto-compress to turn this automatism off if I want tar to fail on the tar.xz file. This doesnt work as well, the tar.xz is happily unpacked anyway. The user story behind this weird issue is that tar --create --auto-compress --file foo.tar.baz will happily write an uncompressed tar file to foo.tar.baz if it doesn't recognize the suffix, and I'd like to be able to diagnose this to fall back to foo.tar.gz to get at least a bit of compession in that case. Greetings Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.2-zgws1 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tar depends on: ii libacl1 2.3.1-1 ii libc62.33-7 ii libselinux1 3.4-1 tar recommends no packages. Versions of packages tar suggests: ii bzip21.0.8-5 pn ncompress pn tar-doc pn tar-scripts ii xz-utils 5.2.5-2.1 -- no debconf information
Bug#1009169: please package new emacs version 28.1
Xiyue Deng writes: > Thanks for maintaining Emacs in Debian! I've been a long time Emacs > user and would like to help in anyway you prefer. I had some > experiences in Debian packaging a few years ago and have been > relearning everything from the docs like [1] and [2]. If there's > anything that I can help with (e.g. testing, bug triaging, etc.) > please let me know. Thanks. I've finally been working on the packaging more substantially, and it's coming along. Took a while for the review, copyright updates, dfsg-split, merge, etc. But it's getting closer. We've been discussing it off an on on #debian-emacs (OFTC), and I'm hoping to have packages to upload for evaluation/testing and then migration within the next week or so. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#1012075: openvpn: OpenVPN - Debian/SID release '2.6.0~git20220518+dco-1' breaks connection buildup
Hello Bernhard, Sorry for my late reply. The XG550 is running Firmware "SFOS 17.5.14 MR-14-1". It fall out of support end of 2021. I was in discussion with our network guys to upgrade the Firmware to latest version. As this Sophos XGs are running in HA Mode and cost 40k each we can't do this without proper testing etc...So we plan to replace them with brand new Fortinets in the IDC. Sophos Tech support couldn't provide us any hint if this could be fixed in this 17.5 FW Release as it's not under support anymore. I couldn't see any information regarding new TLS encryption functions in 18.x FW Release but i guess they fixed it. I could reply in 2-3 months once we have the Fortinets in place and proberly configured. One thing is very strange here. The Windows OpenVPN client in version 2.6 works fine compare to the Linux client. So there might be something else in the client source code ? I guess we can close this ticket for the moment ? Best regards, Henrik On Mon, 30 May 2022 11:18:41 +0200 Bernhard Schmidt wrote: > Control: tags -1 moreinfo > > Hi Henrik, > > > The latest version of OpenVPN in Debian/SID repo '2.6.0~git20220518+dco-1' > > won't connect due to TLS errors during connection attempts. > > Only downgrade to version '2.5.6-1' solves the issue. > > Have you followed up on the multiple warnings and notes from the log? > > 2022-05-29 19:07:47 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but > missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20- POLY1305). > OpenVPN ignores --cipher for cipher negotiations. > > 2022-05-29 19:08:08 TLS error: Unsupported protocol. This typically > indicates that client and server have no common TLS version enabled. > This can be caused by mismatched tls-version-min and tls-version-max > options on client and server. If your OpenVPN client is between v2.3.6 > and v2.3.2 try adding tls-version-min 1.0 to the client configuration to > use TLS 1.0+ instead of TLS 1.0 only > 2022-05-29 19:08:08 OpenSSL: error:0A000102:SSL routines::unsupported > protocol > > Please also check up on all items in > https://github.com/OpenVPN/openvpn/blob/dco/Changes.rst . > > From your working log > > 2022-05-29 19:14:10 Control Channel: TLSv1, cipher SSLv3 > DHE-RSA-AES256-SHA, peer certificate: 2048 bit RSA, signature: RSA- SHA256 > > TLSv1 means TLSv1.0 means very very deprecated. > > > > > I had to blur some characters like IP adresses. Destination is Sophos UTM > > Appliances. > > Is that Sophos up to date? > > Bernhard > >
Bug#1012545: coreutils: unexpand: nonconformantly (to both POSIX and heirloom) replaces single spaces with tabs
Similar case but I think slightly different: printf ' ermrxsmg \tjrjc ngsoo\n' | unexpand -t2 | cat -A printf ' ermrxsmg \tjrjc ngsoo\n' | unexpand -t4,55,68,78 | cat -A output | ermrxsmg^I^Ijrjc ngsoo$ | ermrxsmg^Ijrjc ngsoo$ whereas the correct output is | ermrxsmg ^Ijrjc ngsoo$ | ermrxsmg ^Ijrjc ngsoo$ Fortunately, as in the OP, both correctly round-trip through expand as | ermrxsmg jrjc ngsoo$ | ermrxsmg jrjc ngsoo$ наб signature.asc Description: PGP signature
Bug#1012570: libintl-xs-perl: gettext_xs never used
Package: libintl-xs-perl Version: 1.26-3 Severity: normal Dear Maintainer, I am migrating some systems from stretch to bullseye. These systems use Locale::TextDomain (part of libintl-perl) to do some translations. On bullseye I was getting some wrong responses, and the difference turned out to be that stretch is using the XS version but bullseye is not. I determined this by modifying Locale::Messages to warn about the status of the $no_xs variable. I note that the file gettext_xs.pm was removed for all architectures except mips between buster and bullseye. I copied /usr/lib/x86_64-linux-gnu/perl5/5.24/Locale/gettext_xs.pm from a stretch system to /usr/lib/x86_64-linux-gnu/perl5/5.32/Locale/gettext_xs.pm on bullseye, and now the XS version is being loaded successfully and I'm getting the right answers. Am I missing something in how libintl-xs-perl is supposed to be used? Thanks! *** 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: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libintl-xs-perl depends on: ii libc6 2.31-13+deb11u3 ii libintl-perl1.26-3 ii perl5.32.1-4+deb11u2 ii perl-base [perlapi-5.32.1] 5.32.1-4+deb11u2 libintl-xs-perl recommends no packages. libintl-xs-perl suggests no packages. -- no debconf information
Bug#1012569: haskell_devscripts: unable to parse CABAL_VERSION from some .cabal files
Package: haskell-devscripts Severity: important haskell-devscripts is unable to parse the CABAL_VERSION out of some .cabal files. This is only recently a problem because prior to the recent perl changes, builds would not fail if CABAL_VERSION was empty. An example of a package where the .cabal file cannot be parsed is haskell-base-prelude. This results in an error such as this: > dh_haskell_install_haddock --package=libghc-base-prelude-doc > --source-dir="debian/tmp-inst-ghc" > Need CABAL_VERSION to install HTML documentation. at > /usr/bin/dh_haskell_install_haddock line 46. > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: > install/libghc-base-prelude-doc] Error 25 haskell-devscripts should be updated to perform parsing of the .cabal file more reliably.
Bug#1012568: haskell_devscripts: package registration needs to be run with UTF-8 locale
Package: haskell-devscripts Severity: important haskell_devscripts needs to run GHC registration with a UTF-8 locale. Otherwise, it will fail with an error like the below if the .cabal file contains a UTF-8 copyright symbol: Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config --verbose=verbose+nowrap Non-zero exit code 1. /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-ghc/build/global-autogen -Idist-ghc/build -optP-include -optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 -hide-all-packages -Wmissing-home-modules -no-user-package-db -XHaskell2010 Foreign.Lua.Module.Text -optl-Wl,-z,relro name: hslua-module-text version: 0.2.1 visibility: public id: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 key: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 license: MIT copyright:: commitBuffer: invalid argument (invalid character) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-hslua-module-text-dev] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 This used to be done in Dh_Haskell.sh in 0.16.2 [1], but was lost in the recent perl changes. @Felix - any advice on how to fix this? It seems the LC_ALL=C.UTF-8 can't be prepended to the command line as was before as bash isn't used. [1] https://salsa.debian.org/haskell-team/haskell-devscripts/-/blob/debian/0.16.2/Dh_Haskell.sh#L605
Bug#964199: ITP: nsjail -- A light-weight process isolation tool using namespaces and seccomp-bpf syscall filters
Hi! * Christian Blichmann [Fri Jul 03, 2020 at 04:06:42PM +0200]: > * Package name : nsjail > Version : 2.9 > Upstream Author : Robert Swiecki > * URL : https://nsjail.dev/ > * License : Apache-2.0 > Programming Lang: C++ > Description : A light-weight process isolation tool using > namespaces and seccomp-bpf syscall filters [...] > - How do you plan to maintain it? Inside a packaging team? > > I want to maintain it as part of the "pkg-security" team. A friend of mine asked me about the Debian packaging of nsjail and I stumbled upon this ITP, and also noticed that we've got https://salsa.debian.org/pkg-security-team/nsjail already. Is there anything missing yet for uploading it towards Debian? :) Thanks! regards -mika- signature.asc Description: PGP signature
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
On Fri, 3 Jun 2022 13:08:55 +0100 Peter B wrote: > > Aside from the dbus xml stuff: what exactly do you mean by the > > comment in the GPL-3 license paragraph? > I'm confused regarding GPL-3 & GPL-3+. We now have a License > paragraph for GPL-3 that excludes later versions, but the full text > in /usr/share/common-licenses/GPL-3 > https://www.gnu.org/licenses/gpl-3.0.html > both include it! The full text includes 'or any later version' in two places: first in paragraph 14, conditional on that being explicitly specified by the program in question; the other as part of an example or how one could apply the terms of the GPL. That example is explicitly outside of the terms and conditions set by the license. So yes, GPL-version-X-only is very much a thing. > > I suspect some of the org.freedesktop.*.xml files on the other > > hand could be based directly on dbus specs [1] or similar generic > > interface definitions for use with qdbusxml2cpp, possibly > > autogenerated by qdbus along the lines of: > > `QT_SELECT=5 qdbus org.freedesktop.Notifications > > /org/freedesktop/Notifications > > org.freedesktop.DBus.Introspectable.Introspect` > I've created separate Files paragraphs for each group of files. > > (I'm not sure what the impact of auto-generation is on the > copyright. I notice that in [3], the author is the upstream > application author, no reference to org.freedesktop) Typically, output produced by a program isn't itself covered by the license of said program. Producing a text on a GPL'ed editor doesn't put that text under the GPL. For org.freedesktop.Notifications.xml and DBus.ObjectManager, I don't see much of a reason to assume it originates from some other project; so those could reasonably fall directly under the default copyright paragraph for strawberry (i.e., no separate entry needed). The org.freedesktop.UDisk2.*.xml files should have their own (collective) entry, as the original for all of the udisk ones seems to be [1] with David Zeuthen as the sole copyright holder. Something similar applies to the org.mpris.*.xml (currently missing from d/copyright), except here the upstream seems to be [2] (debian copyright file at [3]). The org.kde.KGlobalAccel.*.xml appear to be based on files in the kglobalaccel project [4] (debian copyright at [5]) rather than the kde documentation, please update the entry to reflect that. Other than that, the shortname for the LGPL-2 license should have a plus symbol appended to reflect the 'any later version' option, in line with the standard shortnames documented by [6]. [1]https://github.com/storaged-project/udisks/blob/master/data/org.freedesktop.UDisks2.xml [2]https://github.com/eonpatapon/mpDris2/blob/5e5cdacea6e55544064f8b10e0b49bbe2aa044d9/src/mpDris2.in.py#L115 [3]https://salsa.debian.org/debian/mpdris2/-/blob/debian/latest/debian/copyright [4]https://sources.debian.org/src/kglobalaccel/5.94.0-1/src/ [5]https://tracker.debian.org/media/packages/k/kglobalaccel/copyright-5.94.0-1 [6]https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-short-name pgpBcu5XjD4Xp.pgp Description: OpenPGP digital signature
Bug#896916:
On Wed, 2022-06-08 at 11:59 +0200, Marc Haber wrote: > On Wed, Jun 08, 2022 at 12:34:14AM -0400, Matt Barry wrote: > > tags -1 + confirmed patch > > thanks > > How about zstd and the other hip compressors? Heh. I was thinking about whether to bother with this one. A couple of factors: * adding zstd in the same fashion will take ~ 2 minutes * there are, imo, no additional algorithms worth considering, so it isn't a bottomless well of feature requests * I guess the ideal for users would be a config item that controls the order of selection: BACKUP_COMPRESS=xz gz zstd # eg. would never try bzip2 I can't imagine it getting more complicated than that.. Cheers, Matt
Bug#958311: cloud kernel 5.5.0-2 does not boot under xen
Hi, On Thu, Jun 09, 2022 at 02:00:30PM +0300, Aleksi Suhonen wrote: > The underlying problem is that the cloud kernel is compressed with an > algorithm that grub can't uncompress. What I've been doing as a workaround > is that I decompress the kernel myself in a kernel install hook. Can you show us your xen domu config file? I'm interested in what method you are using to boot these. If you're using pvgrub2 to boot PV mode then the bad news is that it seems to be largely abandoned as nobody wants to alter it to support different kernel compression methods. The good news is that you should be able to easily switch to PVH mode with pvhgrub which uses grub's core routines to decompress the kernel and therefore supports whatever compression methods that grub normally does. Cheers, Andy
Bug#867667: xsane: This is not a *normal* bug. It makes xsane ***unusable***
Package: xsane Version: 0.999-12 Followup-For: Bug #867667 I do not see what I am scanning. Hence I cannot adjust brightness, contrast, dimensions. And as my last working xsane scan was not a full page, I now stuck with those dimension. Don't tell me I could change the dimensions in a submenue, I know. Scanning blindly makes xsane unusuable! BTW, as maybe it's related: I have enabled "preview" in the window (de: Ansicht) pull-down menue. And then stored the settings. Nonetheless the (empty) preview window does not get opened on start of xsane. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.2-4-siduction-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xsane depends on: ii libc62.33-7 ii libgimp2.0 2.10.30-1+b1 ii libglib2.0-0 2.72.2-2 ii libgtk2.0-0 2.24.33-2 ii libjpeg62-turbo 1:2.1.2-1 ii liblcms2-2 2.12~rc1-2 ii libpng16-16 1.6.37-5 ii libsane1 1.1.1-5 ii libtiff5 4.4.0-2 ii sensible-utils 0.0.17 ii xsane-common 0.999-12 ii zlib1g 1:1.2.11.dfsg-4 Versions of packages xsane recommends: ii chromium [www-browser] 102.0.5005.61-1 ii cups-client 2.4.2-1 ii falkon [www-browser]3.2.0+dfsg1-2 ii firefox [www-browser] 100.0.2-1 ii lynx [www-browser] 2.9.0dev.10-1 ii vivaldi-snapshot [www-browser] 5.3.2679.50-1 ii vivaldi-stable [www-browser]5.3.2679.51-1 ii w3m [www-browser] 0.5.3+git20220429-1+b1 Versions of packages xsane suggests: ii cuneiform1.1.0+dfsg-9 ii gimp 2.10.30-1+b1 ii gocr 0.52-3 ii gv 1:3.7.4-2+b1 pn hylafax-client | mgetty-fax ii ocrad0.28-2 -- no debconf information greetings MH
Bug#1012562: gdb makes time(2) no longer returning correct value
Also reproducible with gdb 8.2.1-2+b3 on buster ppc64el.
Bug#1012502: [Pkg-sssd-devel] Bug#1012502: Bug#1012502: Bug#1012502: sssd: authentication fails with latest sssd
On Thu, Jun 09, 2022 at 10:11:19AM +0300, you wrote: Timo Aaltonen kirjoitti 9.6.2022 klo 9.51: Michael Stone kirjoitti 8.6.2022 klo 18.52: On Wed, Jun 08, 2022 at 05:41:00PM +0300, Timo Aaltonen wrote: Did you have 2.7.0 at some point? 2.7.0-1 was installed 2022-05-27 2.7.0-1+b1 was installed 2022-05-29 no issues with either of those; I reverted to 2.6.3 just because it was easier to grab from the mirrors. I guess it should be filed upstream then, if it's a regression in 2.7.1 which was supposed to be a bugfix release. actually, this should fix it: https://github.com/SSSD/sssd/pull/6204 this seems to be working
Bug#1012539: nheko: Missing dependency on qml-module-qt-labs-animation
Version: 0.9.3-2
Thanks for the report. This was fixed in the new upload yesterday.
Hubert
On Wed, 8 Jun 2022 22:56:40 +0200, Adrien CLERC said:
> Package: nheko Version: 0.9.3-1 Severity: important
> Dear Maintainer,
> After updating to nheko 0.9.3 the application was blank at start with
> the following warning in the console:
> [2022-06-08 22:53:34.299] [qml] [warning] qrc:/qml/Root.qml:153:9:
> Type ImageOverlay unavailable ImageOverlay { ^ (qrc:/qml/Root.qml:153,
> ) [2022-06-08 22:53:34.299] [qml] [warning]
> qrc:/qml/dialogs/ImageOverlay.qml:7:1: module "Qt.labs.animation" is
> not installed import Qt.labs.animation 1.0 ^
> (qrc:/qml/dialogs/ImageOverlay.qml:7, )
> After installing qml-module-qt-labs-animation everything was working.
> Have a nice day, Adrien
> -- System Information: Debian Release: bookworm/sid APT prefers
> unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'),
> (1, 'experimental') Architecture: amd64 (x86_64)
> Kernel: Linux 5.17.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale:
> LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 nheko depends on: ii gstreamer1.0-nice 0.1.18-2
> ii gstreamer1.0-qt5 1.20.2-1 ii gstreamer1.0-vaapi 1.20.2-1 ii libc6
> 2.33-7 ii libcmark0.30.2 0.30.2-5 ii libcurl4 7.83.1-1+b1 ii
> libevent-core-2.1-7 2.1.12-stable-5+b1 ii libevent-pthreads-2.1-7
> 2.1.12-stable-5+b1 ii libfmt8 8.1.1+ds1-2 ii libgcc-s1 12.1.0-2 ii
> libglib2.0-0 2.72.2-2 ii libgstreamer-plugins-bad1.0-0 1.20.2-1+b1 ii
> libgstreamer-plugins-base1.0-0 1.20.2-2 ii libgstreamer1.0-0 1.20.2-1
> ii liblmdb0 0.9.24-1 ii libolm3 3.2.11~dfsg-1 ii libqt5core5a
> 5.15.2+dfsg-16+b2 ii libqt5dbus5 5.15.2+dfsg-16+b2 ii libqt5gui5
> 5.15.2+dfsg-16+b2 ii libqt5keychain1 0.13.2-5 ii libqt5multimedia5
> 5.15.2-3 ii libqt5network5 5.15.2+dfsg-16+b2 ii libqt5qml5
> 5.15.2+dfsg-10 ii libqt5quick5 5.15.2+dfsg-10 ii libqt5svg5 5.15.2-4
> ii libqt5widgets5 5.15.2+dfsg-16+b2 ii libspdlog1 [libspdlog1-fmt8]
> 1:1.9.2+ds-0.2 ii libssl3 3.0.3-6 ii libstdc++6 12.1.0-2 ii
> libxcb-ewmh2 0.4.1-1.1 ii libxcb1 1.14-3 ii
> qml-module-qt-labs-platform 5.15.2+dfsg-4 ii
> qml-module-qt-labs-settings 5.15.2+dfsg-10 ii
> qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtmultimedia
> 5.15.2-3 ii qml-module-qtquick-controls2 5.15.2+dfsg-4 ii
> qml-module-qtquick-layouts 5.15.2+dfsg-10 ii
> qml-module-qtquick-window2 5.15.2+dfsg-10 ii qml-module-qtquick2
> 5.15.2+dfsg-10
> Versions of packages nheko recommends: ii ca-certificates 20211016 pn
> fonts-noto-color-emoji
> nheko suggests no packages.
> -- no debconf information
--
Hubert Chathi -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
Bug#1010846: Fwd: Re: [debian-mysql] Bug#1010846: mariadb-common: Removes directory /etc/mysql/mariadb.conf.d during uninstall preventing mysql server from starting
Hi Nick! Nick DeYarman <1ni...@gmail.com>, 23/05/2022 – 10:30:37 (-0700): > Yes, those steps then `systemctl stop mysql` and `systemctl start > msyql` (or restart the machine). > > I just tried with a fresh cloud instance (google cloud compute > instance). The first time the issue did **not** reproduce. But I > tried a second time and the same issue reproduced (with the > mariadb.conf.d folder getting deleted). Second time was with > `systemctl stop mysql` and `systemctl start mysql` while the first was > just `systemctl restart mysql`. I can still not reproduce this. Could you paste here exact steps and commands (can you also provide as much info as you can about the instance you are running, maybe the output of `dpkg -l`, in order to understand what packages are installed). Here are my test in podman containers: | $ podman run --name sys-test --rm -d fauust/docker-systemd:debian-11 | $ podman exec -it sys-test bash | root@c0f7ab73450a:/# apt update && apt install -y mariadb-server && apt install -y mailutils | ... | root@c0f7ab73450a:/# dpkg -l | grep mariadb-common | ii mariadb-common 1:10.5.15-0+deb11u1 all MariaDB common configuration files | root@c0f7ab73450a:/# systemctl start mariadb | root@c0f7ab73450a:/# ps fax | grep mariadb | PID TTY STAT TIME COMMAND |4355 ?Ssl0:00 /usr/sbin/mariadbd | root@c0f7ab73450a:/# apt remove -y mailutils && apt autoremove -y | Reading package lists... Done | Building dependency tree... Done | Reading state information... Done | The following packages were automatically installed and are no longer required: | exim4-base exim4-config exim4-daemon-light gsasl-common guile-2.2-libs libevent-2.1-7 libexpat1 libfribidi0 libgc1 libgnutls-dane0 | libgsasl7 libidn11 libldap-2.4-2 libldap-common libltdl7 libmailutils7 libmpdec3 libntlm0 libpython3.9 libpython3.9-minimal | libpython3.9-stdlib libsasl2-2 libsasl2-modules libsasl2-modules-db libsqlite3-0 libunbound8 mailutils-common media-types | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | mailutils | 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. | After this operation, 1000 kB disk space will be freed. | ... | root@f77cd74ff7e0:/# dpkg -l | grep mariadb-common | ii mariadb-common 1:10.5.15-0+deb11u1 all MariaDB common configuration files | root@c0f7ab73450a:/# ps fax | grep mariadb | PID TTY STAT TIME COMMAND |4355 ?Ssl0:00 /usr/sbin/mariadbd | root@f77cd74ff7e0:/# systemctl restart mariadb && ps fax | grep mariadb |4651 pts/0S+ 0:00 \_ grep mariadb |4627 ?Ssl0:00 /usr/sbin/mariadbd Also, please remember to always include 1010...@bugs.debian.org as recipient in your response (Cc: or To:) so that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010846 gets updated. -- Faustin signature.asc Description: PGP signature
Bug#1012567: openvpn --mktun --dev-type tap --dev tap2 fails
Package: openvpn Version: 2.6.0~git20220518+dco-2 Severity: important Since 2.6.0~git20220518+dco-2 the following command fails: openvpn --mktun --dev-type tap --dev tap2 with Assertion failed at dco_linux.c:442 (tt-type == DEV_TYPE_TUN) Exit due to fatal error I don't have dco support in the linux kernel. openvpn --disable-dco --mktun --dev-type tap --dev tap2 works as a workaround, but I think --mktun --dev-type tap should continue to work without it. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts
Bug#1012566: spdlog: Please package new version v1.10.0
Source: spdlog Version: 1:1.9.2+ds-0.2 Severity: normal Tags: sid bookworm X-Debbugs-CC: cru...@debian.org Dear Debian spdlog package maintainer, The spdlog upstream has released v1.10.0 since April 2022 (see https://github.com/gabime/spdlog/releases ). Please consider packaging the new releases in Debian. Upstream has explicitly declared compatibility with fmtlib 8.1.1 (the current version in Debian), so the new version is not expected to bring major regressions. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1012565: libecap3: ftbfs on riscv64 (error: some symbols or patterns disappeared in the symbols file)
Package: libecap3 Version: 1.0.1-3.2 Severity: minor User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, The package has a build fail on riscv64 arch: ``` ... dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libecap3/DEBIAN/symbols doesn't match completely debian/libecap3.symbols --- debian/libecap3.symbols (libecap3_1.0.1-3.2_riscv64) +++ dpkg-gensymbolsrLHP7b 2022-04-18 15:05:52.235357043 + @@ -79,18 +79,30 @@ _ZNK7libecap8BodySize7badSizeEv@Base 1.0.1 (optional=templinst)_ZNSt3tr110shared_ptrIN7libecap4host4HostEED1Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr116_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap7adapter7ServiceENS_11_Sp_deleterIS3_EELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap7adapter7ServiceENS_11_Sp_deleterIS3_EELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap7adapter7ServiceENS_11_Sp_deleterIS3_EELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap7adapter7ServiceENS_11_Sp_deleterIS3_EELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 1.0.1 - (optional=templinst)_ZNSt3tr121_Sp_counted_base_implIPN7libecap7adapter7ServiceENS_11_Sp_deleterIS3_EELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 1.0.1 + _ZNSt3tr116_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base 1.0.1-3.2 + _ZNSt3tr116_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_releaseEv@Base 1.0.1-3.2 +#MISSING: 1.0.1-3.2# (optional=templinst)_ZNSt3tr116_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 1.0.1 +#MISSING: 1.0.1-3.2# (optional=templinst)_ZNSt3tr116_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base 1.0.1 + _ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base 1.0.1-3.2 + _ZNSt3tr121_Sp_counted_base_implIPN7libecap20StdStringAreaDetailsENS_11_Sp_deleterIS2_EELN9__gnu_cxx12_Lock_policyE1EE14_M_get_deleterERKSt9type_info@Base 1.0.1-3.2 ... ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=libecap=riscv64=1.0.1-3.2=1650294359=0 maybe it needs update the libecap3.symbols to fix the issue. refer to[0] and [1]. Thank you. If you need me to do more test on riscv64, please let me know. Bo, [0]: https://wiki.debian.org/UsingSymbolsFiles [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010755 signature.asc Description: PGP signature
Bug#1012564: openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7
Package: openssl Version: 3.0.3-7 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading openssl, libssl3 to 3.0.3-7 from 3.0.3-6 on host system prevented ckermit 305~alpha07-1+b1 on client system with libssl3 3.0.3-6 from connecting to telnetd-ssl 0.17.41+0.2-3.3 on host system. * What exactly did you do (or not do) that was effective (or ineffective)? I first downgraded libssl3 from 3.0.3-7 on host system to 3.0.3-6 but that didn't resolve the issue. After I downgraded openssl from 3.0.3-7 to 3.0.3-6 on the host system, I was able to connect from the client system which still runs openssl 3.0.3-6 and libssl3 3.0.3-6. Note, I am NOT running telnetd-ssl 0.17.41+0.2-3.3+b1 due to bug #1010968 * 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: bookworm/sid APT prefers experimental APT policy: (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-rc1+ (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages openssl depends on: ii libc62.33-7 ii libssl3 3.0.3-6 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20211016 -- no debconf information
Bug#970639: ZSWAP still considered experimental?
On Tuesday, 31 May 2022 18:39:27 CEST Andrew Morton wrote: > On 31 May 2022 10:41:05 Diederik de Haas wrote: > > In https://bugs.debian.org/970639 the request was made to enable ZSWAP. > > ... > > Should ZSWAP should still be considered experimental or not? > > I'd say "not". Even though the Kconfig file still mentions "experimental" in 5.19-rc1, I consider this response enough proof that it can be enabled. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/mm/Kconfig shows several recent commits for that Kconfig file, including a reorganization. I (still) do not know what and how exactly ZSWAP should be enabled, but it looks like the 5.19 kernel is a good target to enable it and fix this bug? signature.asc Description: This is a digitally signed message part.
Bug#1011308: Your mail
Hello Paul, Thanks for the info. I just uploaded a new release of the package using libluajit2-5.1-dev as build-deps. Best, Jean Baptiste On 6/9/22 12:45, Paul Gevers wrote: Control: severity -1 normal Hi Jean, On Thu, 2 Jun 2022 21:19:14 +0200 Jean Baptiste Favre wrote: The bug is currently fixed in trafficserver 9.1.2+ds-7 into unstable. Due to the ongoing openssl transition, its migration to testing is however blocked. I'll continue to monitor package status to prevent it from being removed from testing if possible. Thanks for fixing this bug. However, in the mean time the maintainer of luajit found an alternative solution (by introducing an alternative luajit source package called luajit2). See transition bug #1012362). So, if you want to you can add support for luajit on ppc64el back to your package. Sorry for the extra work this bug caused, but when I filed it it wasn't clear on what timescale this would happen and if it would work out. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1010729: dcmtk: Default path to DICOM dictionaries is wrong
Control: fixed -1 3.6.7-3 Looking at the dch history, it appears it should be fixed by upload 3.6.7-3. This closing. Feel free to re-open if not.
Bug#1012467: davix ships complete lyrics of "Never Gonna Give You Up"
Control: forwarded 1012467 https://github.com/cern-fts/davix/issues/97 Control: tag 1012467 +fixed-upstream The issue was addressed upstream in this commit: https://github.com/cern-fts/davix/commit/5d15956648c0984094d6147cd2b67c195c5c335f Mattias signature.asc Description: This is a digitally signed message part
Bug#1012362: transition: luajit
Hi Mo, On 09-06-2022 13:58, Paul Gevers wrote: You may want to look at the FTBFS on mipsel for python-lupa. https://buildd.debian.org/status/fetch.php?pkg=python-lupa=mipsel=1.13%2Bdfsg-1%2Bb2=1654771416=0 The maintainer of sysbench switched to luajit2 completely. The package FTBFS [1] on ppc64el though as it triggers SEGFAULTs in it's tests. + /bin/bash: line 2: 1941783 Segmentation fault sysbench $SBTEST_SCRIPTDIR/oltp_read_write.lua help + [139] Paul https://buildd.debian.org/status/fetch.php?pkg=sysbench=ppc64el=1.0.20%2Bds-4=1654765356=0 OpenPGP_signature Description: OpenPGP digital signature
Bug#1012563: wireplumber: right click broken in firefox 100.0.2-1
Package: wireplumber Version: 0.4.10-2 Severity: important X-Debbugs-Cc: hert...@debian.org, gland...@debian.org, team+pkg-mozi...@tracker.debian.org Control: affects -1 firefox Hello, Following the recommendation of https://tracker.debian.org/news/1329911/accepted-pipewire-media-session-041-3-source-into-unstable/ I installed "wireplumber". But after having switched, Firefox started to behave strangely: any time that I would "right click" on a link or a field, or anywhere where you can expect the right click to open a contextual menu, it would "freeze" for a varying number of seconds and it would not display the contextual menu once the freeze was over. I switched back to pipewire-media-session and I created /usr/share/pipewire/media-session.d/with-pulseaudio to get the sound back and it works again now. I'm not sure how both behaviour are related, but they seem to clearly be related. When I had the issue, I tried to open "about:support", it also triggered one of those freezes but in the end I was able to see that firefox was using "alsa" as audio-backend. Now that I switched back to "pipewire-media-session" and that firefox is now behaving correctly, I see that it uses the "pulse-rust" audio backend. So somehow, wireplumber + pipewire-pulse is not properly detected as something that can be controlled with the "pulse-rust" audio backend when it likely should be that way... I don't know if this needs a fix in firefox or in wireplumber. I'm assigning it wireplumber for a start but I have cced Mike Hommey (the firefox maintainer). Thank you all for your great work on those packages! -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireplumber depends on: ii init-system-helpers 1.63 ii libc6 2.33-7 ii libglib2.0-0 2.72.2-2 ii libpipewire-0.3-0 0.3.51-1+b1 pn libwireplumber-0.4-0 ii pipewire 0.3.51-1+b1 Versions of packages wireplumber recommends: ii pipewire-pulse 0.3.51-1+b1 Versions of packages wireplumber suggests: pn libspa-0.2-bluetooth
Bug#1012562: gdb makes time(2) no longer returning correct value
Package: gdb
Version: 10.1-2+b1
Severity: important
X-Debbugs-Cc: msl023...@gmail.com
Hello.
I'm actually not sure whether this is a GDB or a GLIBC bug, but I currently
can only reproduce this bug with gdb(1) (not strace(1) for exmaple).
I found one of my program starts to behave abnormally after I trying to
inspect its stack trace with gdb(1); further investigation indicates that the
program can no longer obtain the real time clock via time(2), but getting a
constant value which seems to be equal to the time when gdb(1) attached it.
Note the time(2) continue to return the constant value after the gdb(1)
detached it, which creates a major problem to the program.
The following test confirms the bug:
root@debian:~/src# cat time-test.c
#include
#include
#include
int main() {
while(1) {
time_t t = time();
printf("%llu\n", (unsigned long long int)t);
usleep(50);
}
}
root@debian:~/src# gcc -Wall -O1 time-test.c -o time-test
root@debian:~/src# ./time-test
1654776779
1654776779
1654776780
1654776780
1654776781
^C
root@debian:~/src# gdb time-test
GNU gdb (Debian 10.1-2+b1) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Bug#1010073: Bug 1010073: kernel 4.19: nvme read overhead sometimes, system hangs
Because it is the latest kernel which supports aufs. Problem gone when I change to default parameters NIC Mellanox Technologies MT28908 Family [ConnectX-6] ethtool -C enp161s0f0np0 rx-usecs 8 rx-frames 128 tx-usecs 8 tx-frames 128 вт, 7 черв. 2022 р. о 18:35 Diederik de Haas пише: > Control: reassign -1 src:linux 4.19.235-1 > Control: tag -1 moreinfo > > On 23 Apr 2022 21:59:32 +0300 Андрій Василишин > wrote: > > Package: linux-image-4.19.0-20-amd64 > > Version: 4.19.235-1 > > > > ... > > > > Hardware name: Supermicro AS-1124US-TNRP/H12DSU-iN, BIOS 2.3a 03/03/2022 > > https://www.supermicro.com/en/Aplus/system/1U/1124/AS-1124US-TNRP.cfm > specifications (and BIOS date) indicate this is quite a new board. > Yet you're running it with a 4.19 kernel from *OldStable* ! > > Why? > > Can you reproduce this issue with at least the 5.10 kernel from OldStable > backports, but preferably with a recent kernel from Testing/Unstable. -- WBR, Andrey Vasilishin
Bug#1012275: closing 1012275
Could someone then possibly rebuild this with Julian’s patch, ASAP? Over a week with a likely remote code exploit hole in the browser of any Debian (non-ESR) FF user, seems not so ideal, Thanks, Chris.
