Bug#1009771: netsurf: Please replace mime-support with media-types or mailcap in Recommends
Source: netsurf Severity: normal X-Debbugs-Cc: ple...@debian.org Dear netsurf maintainers, In the previous release cycle, I have split the `mime-support` package into two: `media-types` supplies /etc/mime.types and `mailcap` supplies the mailcap system. `mime-support` is now a transitional package that I would like to remove from Debian. According to your needs, can you replace mime-support with media-types or mailcap in netsurf's Recommends ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1009770: gitit: Please replace mime-support with media-types in Recommends
Package: gitit Severity: normal X-Debbugs-Cc: ple...@debian.org Dear gitit maintainers, In the previous release cycle, I have split the `mime-support` package into two: `media-types` supplies /etc/mime.types and `mailcap` supplies the mailcap system. `mime-support` is now a transitional package that I would like to remove from Debian. May I ask you to replace mime-support with media-types in gitit's Depends ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1009769: libhoel1.4: ABI break: h_exec_query_sqlite was dropped
Package: libhoel1.4 Version: 1.4.20-1 Severity: serious Justification: Policy 8.6.2 X-Debbugs-Cc: glewl...@packages.debian.org, ametz...@bebt.de Good morning, 1.4.18 to 1.4.20 features this change: 8X-- diff -NurBbp hoel-1.4.18/include/hoel.h hoel-1.4.20/include/hoel.h --- hoel-1.4.18/include/hoel.h 2021-06-02 19:38:17.0 +0200 +++ hoel-1.4.20/include/hoel.h 2022-03-25 18:47:40.0 +0100 @@ -525,6 +525,16 @@ long long int h_last_insert_id_sqlite(co /** * h_exec_query_sqlite + * legacy function name, didn't realize the typo until now... + * redirect to h_execute_query_sqlite + * @param conn the connection to the database + * @param query the SQL query to execute + * @return H_OK on success + */ +#define h_exec_query_sqlite(conn, query) h_execute_query_sqlite(conn, query) [...] -int h_exec_query_sqlite(const struct _h_connection * conn, const char * query); +int h_execute_query_sqlite(const struct _h_connection * conn, const char * query); 8X-- i.e. the symbol h_exec_query_sqlite was dropped from the library ABI. This breaks all reverse dependencies built against 1.4.18, e.g. glewlwyd is now broken: (sid)ametzler@argenau:/dev/shm/GLEWY$ ldd -r /usr/bin/glewlwyd | tail -n1 undefined symbol: h_exec_query_sqlite (/usr/bin/glewlwyd) cu Andreas
Bug#1009768: s3fs-fuse: Please replace mime-support with media-types in Depends
Source: s3fs-fuse Severity: normal X-Debbugs-Cc: ple...@debian.org Dear s3fs maintainers, In the previous release cycle, I have split the `mime-support` package into two: `media-types` supplies /etc/mime.types and `mailcap` supplies the mailcap system. `mime-support` is now a transitional package that I would like to remove from Debian. May I ask you to replace mime-support with media-types in s3fs's Depends ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1009767: topal: Please replace mime-support with media-types or mailcap in Recommends
Package: topal Version: 80-1+b3 Severity: normal X-Debbugs-Cc: ple...@debian.org Dear Phil, In the previous release cycle, I have split the `mime-support` package into two: `media-types` supplies /etc/mime.types and `mailcap` supplies the mailcap system. `mime-support` is now a transitional package that I would like to remove from Debian. According to your needs, can you replace mime-support with media-types or mailcap in topal's Recommends ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1009766: w3m: Please replace mime-support with media-types or mailcap in Suggests
Package: w3m Version: 0.5.3+git20210102-6 Severity: normal X-Debbugs-Cc: ple...@debian.org Dear w3m maintainers, In the previous release cycle, I have split the `mime-support` package into two: `media-types` supplies /etc/mime.types and `mailcap` supplies the mailcap system. `mime-support` is now a transitional package that I would like to remove from Debian. According to your needs, can you replace mime-support with media-types or mailcap in w3m's Suggests ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1001407: lynx: still recommends on transitional package mime-suport
Dear Elimar, I am the maintainer of mime-support, mailcap and media-types. I would like to remove mime-support from Debian this release cycle. Sorry that I did not contact you earlier, but may I ask you to recommend mailcap instead of mime-support ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#722188: Optimizations are not properly applied
Hi, On Sun, 08 Sep 2013 23:13:54 +0200 "Steinar H. Gunderson" wrote: > Source: libdvbcsa > Version: 1.1.0-2 > Severity: normal > > Hello, > > It seems that debian/rules contains: > > ifeq ($(DEB_HOST_ARCH),amd64) > EXTRA_CONFIGURE_ARGS += --enable-mmx --enable-sse2 > endif > > --enable-mmx overrides --enable-sse2, so this means that the package is built > without SSE2 optimizations. Thanks for the info, this is indeed a bug. I will have it fixed in the next upload in the next few hours. > Furthermore, it means that 32-bit packages are not > built with MMX or SSE2 support, despite every single CPU the last ten years > (and certainly every CPU anyone would want to decode DVB-CSA on) has supported > SSE2. (MMX was added in 1997!) According to Debian's architecture baseline ( https://wiki.debian.org/ArchitectureSpecificsMemo ), MMX or SSE2 is forbidden for 32-bit i386 build. Debian's "i386" should only support up to i686. I cannot add such build flag. Sorry. > Finally, --enable-altivec should probably be enabled on appropriate CPUs. According to Debian's architecture baseline ( https://wiki.debian.org/ArchitectureSpecificsMemo ), altivec is not guaranteed on any architecture. I cannot add such build flag. Sorry. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1009762: irssi-scripts: email_msgs.pl needs libemail-sender-perl
Control: severity 1009762 minor Sorry, I meant add `libemail-sender-perl' to the dependency list found inside the file README.Debian. Best Regards, mt signature.asc Description: PGP signature
Bug#1006833: glances: add an option to run as a daemon into debconf
tags 1006833 + moreinfo thanks Hello! El dom, 6 mar 2022 a la(s) 03:42, Alex Volkov (a...@bootes.sytes.net) escribió: > Package: glances > Version: 3.2.4.2+dfsg-1~bpo11+1 > Severity: wishlist > > Dear Maintainer, > > I get that taking a look into the /etc/init.d/glances and creating > /etc/default/glances if one doesn't need the daemon feature isn't > particularly > hard, but it would be probably more beneficial to ask a user about it at > the > installation time through debconf. > > > -- System Information: > Debian Release: 11.2 > APT prefers stable-security > APT policy: (991, 'stable-security'), (991, 'stable'), (99, 'testing'), > (90, > 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.15.15-bootes1-p-1000-snddeb (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en_US > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages glances depends on: > ii adduser3.118 > ii init-system-helpers1.60 > ii lsb-base 11.1.0 > ii python33.9.2-3 > ii python3-defusedxml 0.6.0-2 > ii python3-future 0.18.2-5 > ii python3-packaging 20.9-2 > ii python3-pkg-resources 52.0.0-4 > ii python3-psutil 5.8.0-1 > > Versions of packages glances recommends: > ii lm-sensors 1:3.6.0-7 > ii python3-bottle 0.12.19-1 > pn python3-docker > pn python3-influxdb > ii python3-matplotlib 3.3.4-1 > ii python3-netifaces 0.10.9-0.2+b3 > pn python3-pysnmp4 > pn python3-pystache > > Versions of packages glances suggests: > ii glances-doc 3.2.4.2+dfsg-1~bpo11+1 > ii python3-pynvml 7.352.0-7 > I'm not sure if I understood correctly, but glances already run as Daemon, we use systemd as services manager by default, if you need user init.v you must change it manually. What would you like to ask in the debconf template? Regards -- Daniel Echeverri Debian Developer Linux user: #477840 GPG Fingerprint: D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
Bug#965462: clif: diff for NMU version 0.93-9.2
Control: tags 965462 + patch Control: tags 965462 + pending Control: tags 999095 + patch Control: tags 999095 + pending Dear maintainer, I've prepared an NMU for clif (versioned as 0.93-9.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru clif-0.93/debian/changelog clif-0.93/debian/changelog --- clif-0.93/debian/changelog 2015-11-02 08:21:14.0 -0200 +++ clif-0.93/debian/changelog 2022-04-16 21:29:06.0 -0300 @@ -1,3 +1,18 @@ +clif (0.93-9.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the +'-k' option is not supported since compat 12. + - Closes: #965462 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999095) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 21:29:06 -0300 + clif (0.93-9.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru clif-0.93/debian/compat clif-0.93/debian/compat --- clif-0.93/debian/compat 2010-01-03 13:27:41.0 -0200 +++ clif-0.93/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru clif-0.93/debian/control clif-0.93/debian/control --- clif-0.93/debian/control2015-11-02 08:19:46.0 -0200 +++ clif-0.93/debian/control2022-04-16 21:29:06.0 -0300 @@ -2,7 +2,7 @@ Section: interpreters Priority: optional Maintainer: Sam Hocevar -Build-Depends: debhelper (>= 5.0), libx11-dev, libxt-dev, texlive, libelf-dev +Build-Depends: debhelper-compat (= 13), libx11-dev, libxt-dev, texlive, libelf-dev Standards-Version: 3.8.3 Package: clif diff -Nru clif-0.93/debian/rules clif-0.93/debian/rules --- clif-0.93/debian/rules 2010-01-03 14:11:32.0 -0200 +++ clif-0.93/debian/rules 2022-04-16 21:29:06.0 -0300 @@ -46,7 +46,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep $(MAKE) install DESTDIR=`pwd`/debian/clif dh_installdirs usr/bin usr/lib/clif dh_install clif usr/bin @@ -83,5 +83,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure - +build-arch: build +build-indep: build +.PHONY: build clean build-arch build-indep binary-indep binary-arch binary install configure
Bug#1009764: xiphos: freezes when page is changed
Package: xiphos Version: 4.2.1+dfsg1-6 Severity: important X-Debbugs-Cc: garyk1...@charter.net Dear Maintainer, Hadn't used xiphos in a while and when attempted to change Bible book program froze. Only way to close program was to reboot computer. Started xiphos from bash and the following error appears: (xiphos:3078): Gtk-CRITICAL **: 03:42:01.066: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed This was followed by many gtk warnings -- System Information: Debian Release: bookworm/sid Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 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 /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages xiphos depends on: 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 libbiblesync1.1 2.1.0-1 ii libc62.33-7 ii libdbus-glib-1-2 0.112-2 ii libgcc-s112-20220319-1 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.72.1-1 ii libgtk-3-0 3.24.33-1 ii libicu67 67.1-7 ii libminizip1 1.1-8+b1 ii libstdc++6 12-20220319-1 ii libsword1.9.01.9.0+dfsg-4+b1 ii libwebkit2gtk-4.0-37 2.36.0-3 ii libxml2 2.9.13+dfsg-1 ii xiphos-data 4.2.1+dfsg1-6 xiphos recommends no packages. Versions of packages xiphos suggests: pn festival pn sword-text -- no debconf information
Bug#1009762: irssi-scripts: email_msgs.pl needs libemail-sender-perl
Package: irssi-scripts Version: 20201016 Severity: normal X-Debbugs-Cc: mar...@talau.info Dear Maintainer, The script `email_msgs.pl' only works if `libemail-sender-perl' is installed. Could you please add libemail-sender-perl to the dependencies? Best regards, mt signature.asc Description: PGP signature
Bug#1009761: ITP: mutt-wizard -- system to automatically configure
Package: wnpp Severity: wishlist Owner: Josenilson Ferreira da Silva X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com * Package name: mutt-wizard Version : 3.2.1 Upstream Author : Luke Smith * URL : https://github.com/LukeSmithxyz/mutt-wizard * License : GPL-3.0 Programming Lang: shell Description : system to automatically configure Determines the IMAP and SMTP servers and ports of email servers. Creating dotfiles for neomutt, isync, and msmtp appropriate for email addresses . It encrypts and stores passwords locally for easy remote access, accessible only by your GPG key. . Handles up to nine separate email accounts automatically, creating links to switch between accounts or between mailboxes. Provides sensible defaults and an attractive appearance for the neomutt email client. . In case the mutt-wizard doesn't know your server's IMAP/SMTP information by default, it will let you know for them and put them in all the right places.
Bug#967641:
https://github.com/google/mozc/issues/492 Upstream has moved to QT based
Bug#965468: clamassassin: diff for NMU version 1.2.4-1.2
Control: tags 965468 + patch Control: tags 965468 + pending Control: tags 999015 + patch Control: tags 999015 + pending Dear maintainer, I've prepared an NMU for clamassassin (versioned as 1.2.4-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u clamassassin-1.2.4/debian/changelog clamassassin-1.2.4/debian/changelog --- clamassassin-1.2.4/debian/changelog +++ clamassassin-1.2.4/debian/changelog @@ -1,3 +1,16 @@ +clamassassin (1.2.4-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965468 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999015) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 19:47:25 -0300 + clamassassin (1.2.4-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. reverted: --- clamassassin-1.2.4/debian/compat +++ clamassassin-1.2.4.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u clamassassin-1.2.4/debian/control clamassassin-1.2.4/debian/control --- clamassassin-1.2.4/debian/control +++ clamassassin-1.2.4/debian/control @@ -2,7 +2,7 @@ Section: mail Priority: optional Maintainer: Robert S. Edmonds -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2 Package: clamassassin diff -u clamassassin-1.2.4/debian/rules clamassassin-1.2.4/debian/rules --- clamassassin-1.2.4/debian/rules +++ clamassassin-1.2.4/debian/rules @@ -36,5 +36,7 @@ dh_builddeb binary: binary-indep +build-arch: build +build-indep: build -.PHONY: build clean install binary-arch binary-indep binary +.PHONY: build build-arch build-indep clean install binary-arch binary-indep binary
Bug#1009628: linux-image-5.16.0-6-amd64: Wrong initial state of microphone muted LED on Thinkpad E14 (Gen 2)
I hacked together a dirty workaround, which I'm sharing just in case
somebody else with the same problem ends up on this bug report.
Since I'm using systemd and pulseaudio, and the microphone state
changes are correctly being sent to the kernel (I'm not exactly sure
who's responsible for this), I've created a small systemd service unit
that depends on pulseaudio and simply toggles the microphone muted
status twice. The pulseaudio unit is a user service, so this unit
needs to be a user service as well.
A temporary file is used to avoid toggling the microphone more than
once per boot.
$ cat /usr/local/lib/systemd/user/micropohe_led.service
[Unit]
Requires=pulseaudio.service
Description=Make sure that the microphone-muted LED on the F4 key
matches the actual microphone status
[Service]
Type=oneshot
ExecStart=/bin/sh -c "[ ! -f /temp/micmute-led-toggled ] && touch
/tmp/micmute-led-toggled && pactl set-source-mute @DEFAULT_SOURCE@
toggle && pactl set-source-mute @DEFAULT_SOURCE@ toggle"
[Install]
WantedBy=default.target
This service can be enabled for all users with "sudo systemctl
--global enable micropohe_led.service".
On Wed, 13 Apr 2022 10:36:14 +0200 Steven wrote:
> Package: src:linux
> Version: 5.16.18-1
> Severity: normal
> X-Debbugs-Cc: steven3k+deb...@gmail.com
>
> Dear Maintainer,
> I'd like to report that the initial status of the "microphone muted" LED on
> the
> F4 key of a Thinkpad E14 (Gen 2) laptop is incorrectly set to on on boot, even
> though the microphone is indeed not muted.
> Pressing the key leaves the LED on but mutes the microphone. Pressing the key
> again unmutes the microphone and turns off the LED.
> All subsequent presses behave as expected (i.e., the LED matches the mute
> status).
>
> It look like the information that the mic is unmuted never gets to the module
> that is handling the LEDs.
>
> Manually turning the LED off via
> "/sys/class/leds/platform::micmute/brightness"
> disables the LED trigger. Re-enabling the led trigger with "echo micmute >
> /sys/class/leds/platform::micmute/trigger" re-lights the LED.
>
> This seems somewhat related:
> https://lore.kernel.org/alsa-devel/20210221115208.105203-1-hdego...@redhat.com/
>
> Please let me know if I can help troubleshoot the problem. So far I was not
> able to find any workaround.
>
> Thank you!
>
> *** 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 ***
>
>
> -- Package-specific info:
> ** Version:
> Linux version 5.16.0-6-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian
> 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT
> Debian 5.16.18-1 (2022-03-29)
>
> ** Command line:
> BOOT_IMAGE=/vmlinuz-5.16.0-6-amd64 root=/dev/mapper/ghoul--vg-root ro quiet
>
> ** Tainted: POE (12289)
> * proprietary module was loaded
> * externally-built ("out-of-tree") module was loaded
> * unsigned module was loaded
>
> ** Kernel log:
> [ 15.625143] audit: type=1400 audit(1649836987.684:5): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod"
> pid=829 comm="apparmor_parser"
> [ 15.625191] audit: type=1400 audit(1649836987.684:6): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=831
> comm="apparmor_parser"
> [ 15.625196] audit: type=1400 audit(1649836987.684:7): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="man_filter" pid=831
> comm="apparmor_parser"
> [ 15.625198] audit: type=1400 audit(1649836987.684:8): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="man_groff" pid=831
> comm="apparmor_parser"
> [ 15.625521] audit: type=1400 audit(1649836987.684:9): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="lsb_release" pid=828
> comm="apparmor_parser"
> [ 15.627366] audit: type=1400 audit(1649836987.684:10): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="ioq3ded" pid=832
> comm="apparmor_parser"
> [ 15.627902] audit: type=1400 audit(1649836987.688:11): apparmor="STATUS"
> operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport"
> pid=840 comm="apparmor_parser"
Bug#1008443: golang-github-smartystreets-assertions: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/smartystreets/assertions github.com/smartystreets/assert
Source: golang-github-smartystreets-assertions Followup-For: Bug #1008443 I don't understand the version scheme for this package. The Debian version is 1.10.1, which was released 1 Apr 2019. After that, many more versions were released, but with "older" version numbers. The most recent was v1.2.1, released on 29 Sep 2021.
Bug#610390: pisa doesn't support non-latin symbols
Source: xhtml2pdf Version: 0.2.5-1 Followup-For: Bug #610390 As discussed in upstream issue #11, xhtml2pdf is deprecated (no longer supported). The xhtml2pdf documentaiton itself (https://github.com/xhtml2pdf/xhtml2pdf/blob/master/README.rst) says to use WeasyPrint (http://weasyprint.org/) instead. weasyprint is available in Debian, so use it.
Bug#965455: chrootuid: diff for NMU version 1.3-6.1
Control: tags 965455 + patch Control: tags 965455 + pending Control: tags 998939 + patch Control: tags 998939 + pending Dear maintainer, I've prepared an NMU for chrootuid (versioned as 1.3-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u chrootuid-1.3/debian/rules chrootuid-1.3/debian/rules --- chrootuid-1.3/debian/rules +++ chrootuid-1.3/debian/rules @@ -53,4 +53,6 @@ dh_builddeb binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure +build-arch: build +build-indep: build +.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure diff -u chrootuid-1.3/debian/control chrootuid-1.3/debian/control --- chrootuid-1.3/debian/control +++ chrootuid-1.3/debian/control @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Javier Fernandez-Sanguino Pen~a -Build-Depends: debhelper (>> 3.0.0) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.9.1.0 Homepage: http://ftp.porcupine.org/pub/security/index.html diff -u chrootuid-1.3/debian/changelog chrootuid-1.3/debian/changelog --- chrootuid-1.3/debian/changelog +++ chrootuid-1.3/debian/changelog @@ -1,3 +1,16 @@ +chrootuid (1.3-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965455 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #998939) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 17:10:27 -0300 + chrootuid (1.3-6) unstable; urgency=low * Change maintainer's e-mail address reverted: --- chrootuid-1.3/debian/compat +++ chrootuid-1.3.orig/debian/compat @@ -1 +0,0 @@ -5
Bug#965457: choosewm: diff for NMU version 0.1.6-3.1
Control: tags 965457 + patch Control: tags 965457 + pending Dear maintainer, I've prepared an NMU for choosewm (versioned as 0.1.6-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru choosewm-0.1.6/debian/changelog choosewm-0.1.6/debian/changelog --- choosewm-0.1.6/debian/changelog 2011-08-24 05:52:20.0 -0300 +++ choosewm-0.1.6/debian/changelog 2022-04-16 16:58:21.0 -0300 @@ -1,3 +1,14 @@ +choosewm (0.1.6-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965457 + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 16:58:21 -0300 + choosewm (0.1.6-3) unstable; urgency=low * quick fix to make it build again until I have time for diff -Nru choosewm-0.1.6/debian/compat choosewm-0.1.6/debian/compat --- choosewm-0.1.6/debian/compat2011-05-23 05:16:54.0 -0300 +++ choosewm-0.1.6/debian/compat1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru choosewm-0.1.6/debian/control choosewm-0.1.6/debian/control --- choosewm-0.1.6/debian/control 2011-05-23 06:23:19.0 -0300 +++ choosewm-0.1.6/debian/control 2022-04-16 16:58:21.0 -0300 @@ -2,7 +2,7 @@ Section: x11 Priority: extra Maintainer: Bernhard R. Link -Build-Depends: debhelper (>= 5), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libcairo2-dev +Build-Depends: debhelper-compat (= 13), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libcairo2-dev Standards-Version: 3.9.2 Package: choosewm
Bug#906846: mount: Fails to notice that a loopdevice cannot be removed
Hi Gunnar, * Gunnar Wolf [220416 19:54]: > If I request losetup to detach from a loop device and it cannot be > detached, I would expect it to notify me accordingly. However: > > # losetup --list > NAMESIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE >DIO LOG-SEC > /dev/loop1 0 0 1 0 > /home/gwolf/vcs/raspi3-image-spec/raspi3.img (deleted) 0 512 > # if losetup --detach /dev/loop1 ; then echo SUCCESS; else echo FAIL; fi > SUCCESS > # losetup --list > NAMESIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE >DIO LOG-SEC > /dev/loop1 0 0 1 0 > /home/gwolf/vcs/raspi3-image-spec/raspi3.img (deleted) 0 512 > > When requesting debug information, it seems losetup actually believes > the loopback was dropped - but it is false: > > # LOOPDEV_DEBUG=all losetup --detach /dev/loop1 > 9932: loopdev: CXT: [0x7ffeaa764d60]: initialize context > 9932: loopdev: CXT: [0x7ffeaa764d60]: init: ignore ioctls > 9932: loopdev: CXT: [0x7ffeaa764d60]: init: loop-control detected > 9932: loopdev: CXT: [0x7ffeaa764d60]: /dev/loop1 name assigned > 9932: loopdev: CXT: [0x7ffeaa764d60]: open /dev/loop1 [ro]: Success > 9932: loopdev: CXT: [0x7ffeaa764d60]: device removed > 9932: loopdev: CXT: [0x7ffeaa764d60]: de-initialize > 9932: loopdev: CXT: [0x7ffeaa764d60]: closing old open fd > 9932: loopdev: ITER: [0x7ffeaa764f18]: de-initialize > # losetup --list > NAMESIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE >DIO LOG-SEC > /dev/loop1 0 0 1 0 > /home/gwolf/vcs/raspi3-image-spec/raspi3.img (deleted) 0 512 Sorry for the long time with no reply to your bug. I took a closer look today; I can reproduce this -if- I have a filesystem mounted using that loop device. This comment from upstream explains whats going on: https://github.com/util-linux/util-linux/issues/484#issuecomment-321506607 Apparently losetup cannot (really) know that the kernel ignores the detach ioctl. I would say there is no bug in util-linux. Maybe you want to talk to the kernel folks? Best, Chris
Bug#965440: bplay: diff for NMU version 0.991-10.1
Control: tags 965440 + patch Control: tags 965440 + pending Control: tags 999139 + patch Control: tags 999139 + pending Dear maintainer, I've prepared an NMU for bplay (versioned as 0.991-10.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u bplay-0.991/debian/changelog bplay-0.991/debian/changelog --- bplay-0.991/debian/changelog +++ bplay-0.991/debian/changelog @@ -1,3 +1,16 @@ +bplay (0.991-10.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965440 + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999139) + + -- Joao Eriberto Mota Filho Sat, 16 Apr 2022 16:32:45 -0300 + bplay (0.991-10) unstable; urgency=low * Install the manpages. (Closes: #327759) diff -u bplay-0.991/debian/control bplay-0.991/debian/control --- bplay-0.991/debian/control +++ bplay-0.991/debian/control @@ -2,7 +2,7 @@ Section: sound Priority: optional Maintainer: Carlos Laviola -Build-Depends: debhelper (>> 5.0.0) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2.2 Package: bplay reverted: --- bplay-0.991/debian/compat +++ bplay-0.991.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u bplay-0.991/debian/rules bplay-0.991/debian/rules --- bplay-0.991/debian/rules +++ bplay-0.991/debian/rules @@ -58,5 +58,7 @@ # Below here is fairly generic really binary:binary-arch +build-arch: build +build-indep: build -.PHONY: build binary binary-arch binary-indep clean checkroot +.PHONY: build build-arch build-indep binary binary-arch binary-indep clean checkroot
Bug#1009759: RFP: web-archives -- Reader for ZIM files (offline dumps of websites like wikipedia)
Package: wnpp Severity: wishlist * Package name: web-archives Version : 0.4.1 Upstream Author : Birros * URL : https://github.com/birros/web-archives * License : GPLv3 Programming Lang: Vala Description : Offline reader for ZIM files Web Archives is an offline reader for dumps of online contents like Wikipedia, Wikisource etc., suitable both for desktop and mobile form factors. I've found the app on https://linuxphoneapps.org/apps/com.github.birros.webarchives/ (which is where I take the “suitable for mobile” data from). While Debian already has kiwix, on mobile (modian / pinephone) it has some UI issues, so it would be nice to have another option. Also, having an alternative ZIM reader (as opposed to both 0 and 10) is useful to get a hint whether some issue in certain ZIM files come from the file itself or a bug in the reader.
Bug#1009753: sstp-client: exclude utest_route on kfreebsd
Am 16.04.22 um 17:27 schrieb Eivind Næss: I am not familiar with kfreebsd. How is this related to debian or the debian package? You can use Debian with non-Linux kernels. There are two other options: Hurd and the kernel of FreeBSD. Your package compiles on FreeBSD but may not be able to set up a route for the VPN because the two methods to establish one are not available for kfreebsd. The most important website for your plugin is https://tracker.debian.org/pkg/sstp-client which has some links on its right, including buildd: logs. You can find the build logs there, including those for Debian on different kernels. It is not important to have it running on them but nice to have.
Bug#964906: This is still an issue in 11.2
There is an easy solution, put rootdelay=5 into the cmdline.txt, this makes init wait before mounting rootfs for 5 seconds and btrfs raid1 starts up with on usb without any issue.
Bug#979462: aplus-fsf: diff for NMU version 4.22.1-10.2
Control: tags 979462 + pending
Control: tags 983970 + pending
Dear maintainer,
I've prepared an NMU for aplus-fsf (versioned as 4.22.1-10.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u aplus-fsf-4.22.1/debian/changelog aplus-fsf-4.22.1/debian/changelog
--- aplus-fsf-4.22.1/debian/changelog
+++ aplus-fsf-4.22.1/debian/changelog
@@ -1,3 +1,13 @@
+aplus-fsf (4.22.1-10.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS against glibc 2.32 by using strerror() instead of sys_errlist.
+Thanks to Logan Rosen . (Closes: #979462)
+ * Fix FTBFS on GCC-11, avoiding ordered pointer comparisons with integer.
+Thanks to Lukas Märdian . (Closes: #983970)
+
+ -- Marcos Talau Wed, 13 Apr 2022 12:10:56 -0300
+
aplus-fsf (4.22.1-10.1) unstable; urgency=medium
* Non-maintainer upload.
only in patch2:
unchanged:
--- aplus-fsf-4.22.1.orig/src/MSGUI/MSGraphUI.C
+++ aplus-fsf-4.22.1/src/MSGUI/MSGraphUI.C
@@ -1493,7 +1493,7 @@
{
xs=trace->xAxis();
ys=trace->yAxis();
-if(trace->style()!=MSG::Text&>dataCount()>1&>legend()>0)
+if(trace->style()!=MSG::Text&>dataCount()>1&>legend()!=0)
{
if (setX==MSFalse)
{
only in patch2:
unchanged:
--- aplus-fsf-4.22.1.orig/src/MSIPC/MSProtocolConnection.C
+++ aplus-fsf-4.22.1/src/MSIPC/MSProtocolConnection.C
@@ -129,8 +129,13 @@
if (getpeername(fd(),(struct sockaddr *),))
#endif
{
+#if defined (HAVE_STRERROR)
+ char *errstr = strerror(errno);
+#else
+ char *errstr = (errnoelements();
unsigned char *mp=aBinaryMatrix_.data();
unsigned char *row=aBinaryMatrix_.data()+aBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -842,7 +842,7 @@
}
mp=bBinaryMatrix_.data();
row=bBinaryMatrix_.data()+bBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -869,7 +869,7 @@
unsigned char *dp=d->elements();
unsigned char *mp=data();
unsigned char *row=data()+columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -879,7 +879,7 @@
}
mp=aBinaryMatrix_.data();
row=aBinaryMatrix_.data()+aBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -917,7 +917,7 @@
unsigned char *dp=d->elements();
unsigned char *mp=aBinaryMatrix_.data();
unsigned char *row=aBinaryMatrix_.data()+aBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -929,7 +929,7 @@
dp=d->elements()+aBinaryMatrix_.columns();
mp=bBinaryMatrix_.data();
row=bBinaryMatrix_.data()+bBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -957,7 +957,7 @@
unsigned char *dp=d->elements();
unsigned char *mp=data();
unsigned char *row=data()+columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
@@ -969,7 +969,7 @@
dp=d->elements()+columns();
mp=aBinaryMatrix_.data();
row=aBinaryMatrix_.data()+aBinaryMatrix_.columns();
- if (mp>0)
+ if (mp!=0)
{
do
{
only in patch2:
unchanged:
--- aplus-fsf-4.22.1.orig/src/dap/error.c
+++ aplus-fsf-4.22.1/src/dap/error.c
@@ -71,12 +71,12 @@
/* error string a la syslog(3) */
case 'm':
- if (errnum < 1 || errnum > sys_nerr)
- str = "unknown error";
- else
#ifdef HAVE_STRERROR
- str = strerror(errnum);
+str = strerror(errnum);
#else
+if (errnum < 1 || errnum > sys_nerr)
+ str = "unknown error";
+else
str = sys_errlist[errnum];
#endif
for (z = str; *z != (char) NULL &&
Bug#1007022: podman: starting rootless container fails with: can't get final child's PID from pipe: EOF
Hi, On Mon, 21 Mar 2022 18:25:33 -0700 Adam Williamson wrote: Just reporting I found the same problem on Fedora 36. Filed here: https://bugzilla.redhat.com/show_bug.cgi?id=2066527 . Thanks for this added information! Following information from the redhat bug report, I've tried this on my computer which actually fixed the situation for me (so it is a workaround): 1. apt install crun 2. use podman to destroy my rootless containers 3. re-create the rootless containers and start them The crun package was not installed, apparently because it's a "either/or" dependency for podman and "runc" was installed here. Now I have both runc *and* crun installed. I don't know if I need both, but seeing as containers run as my non-root user as it currently is I won't change anything.. Cheers!
Bug#1009758: ITP: flask-restx -- Flask-RESTX is an extension for Flask that adds support for quickly building REST APIs
Package: wnpp Severity: wishlist Owner: Jan Mojzis X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: flask-restx Version : 0.5.1 Upstream Author : python-restx Authors * URL : https://github.com/python-restx/flask-restx * License : BSD-3-Clause Programming Lang: Python Description : Flask-RESTX is an extension for Flask that adds support for quickly building REST APIs Flask-RESTX is an extension for Flask that adds support for quickly building REST APIs. Flask-RESTX encourages best practices with minimal setup. If you are familiar with Flask, Flask-RESTX should be easy to pick up. It provides a coherent collection of decorators and tools to describe your API and expose its documentation properly using Swagger. I would like to maintain the package using https://salsa.debian.org/ Currently is the Debian package maintained here https://salsa.debian.org/janmojzis/python-flask-restx I need sponsor for the first upload (I'm DM).
Bug#1009728: gnome-shell 42.0-3 depends instead of recommends power-profiles-daemon, conflicts with tlp
> Could you please share the output of > > dpkg --get-selections | egrep -v install\|purge > > ? Maybe you've set another package on hold which causes > this problem on your system. dpkg --get-selections | egrep -v install\|purge gnome-shell hold
Bug#1005145: oz: FTBFS against python 3.10
Control: tags -1 ftbfs sid bookworm Hi Simon On 2022-02-08 13:22:33, Simon Josefsson wrote: > Thanks. Debian doesn't have python3.10 yet, but I'll use your patch as > soon as I can reproduce it, or if upstream merges it first. > > Btw, would you like to co-maintain the 'oz' package? Maybe it should > move into some virtualization packaging group, if there is one. I > merged the just released 0.18 into salsa now, but there appears to be > upstream regression test suite errors [1] so I'll delay the upload to > see if there is a quick response to that. python3.10 is now the default python3 version in unstable. So a fix for this issue would be highly appreciated. Cheers > > /Simon > > [1] https://github.com/clalancette/oz/issues/295 -- Sebastian Ramacher
Bug#1009096: mosquitto: diff for NMU version 2.0.11-1.1
Control: tags 1009096 + patch
Control: tags 1009096 + pending
Dear maintainer,
I've prepared an NMU for mosquitto (versioned as 2.0.11-1.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru mosquitto-2.0.11/debian/changelog mosquitto-2.0.11/debian/changelog
--- mosquitto-2.0.11/debian/changelog 2021-06-09 14:54:36.0 +0200
+++ mosquitto-2.0.11/debian/changelog 2022-04-16 17:17:54.0 +0200
@@ -1,3 +1,13 @@
+mosquitto (2.0.11-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+
+ [ Olivier Gayot ]
+ * Fix autopkgtest failure when running against Python 3.10 (Closes:
+#1009096) (LP: #1960214)
+
+ -- Sebastian Ramacher Sat, 16 Apr 2022 17:17:54 +0200
+
mosquitto (2.0.11-1) unstable; urgency=medium
* SECURITY UPDATE: In Eclipse Mosquitto 1.6 to 2.0.10, if an authenticated
diff -Nru mosquitto-2.0.11/debian/patches/series mosquitto-2.0.11/debian/patches/series
--- mosquitto-2.0.11/debian/patches/series 2021-06-09 14:54:36.0 +0200
+++ mosquitto-2.0.11/debian/patches/series 2022-04-16 17:17:09.0 +0200
@@ -2,3 +2,4 @@
1571.patch
deb-test.patch
missing-test.patch
+ssl-sslcontext-wrap_socket.patch
diff -Nru mosquitto-2.0.11/debian/patches/ssl-sslcontext-wrap_socket.patch mosquitto-2.0.11/debian/patches/ssl-sslcontext-wrap_socket.patch
--- mosquitto-2.0.11/debian/patches/ssl-sslcontext-wrap_socket.patch 1970-01-01 01:00:00.0 +0100
+++ mosquitto-2.0.11/debian/patches/ssl-sslcontext-wrap_socket.patch 2022-04-16 17:17:09.0 +0200
@@ -0,0 +1,217 @@
+Description: Replace uses of ssl.wrap_socket by ssl.SSLContext.wrap_socket
+ The function ssl.wrap_socket() is deprecated starting Python 3.7 because it
+ does not support hostname matching (which is considered insecure). In Python
+ 3.10, the function now throws warnings at runtime, which makes autopkgtest
+ fail.
+
+ The function ssl.SSLContext.wrap_socket comes in as the replacement and
+ has support for SNI and hostname matching.
+
+ Replaced all uses of ssl.wrap_socket() by equivalent using
+ ssl.SSLContext.wrap_socket().
+
+Author: Olivier Gayot
+Bug-Ubuntu: https://launchpad.net/bugs/1960214
+Forwarded: https://github.com/eclipse/mosquitto/pull/2451
+Last-Update: 2022-02-07
+
+--- mosquitto-2.0.11.orig/test/broker/08-ssl-bridge.py
mosquitto-2.0.11/test/broker/08-ssl-bridge.py
+@@ -34,7 +34,9 @@ publish_packet = mosq_test.gen_publish("
+
+ sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+ sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
+-ssock = ssl.wrap_socket(sock, ca_certs="../ssl/all-ca.crt", keyfile="../ssl/server.key", certfile="../ssl/server.crt", server_side=True)
++context = ssl.create_default_context(ssl.Purpose.CLIENT_AUTH, cafile="../ssl/all-ca.crt")
++context.load_cert_chain(certfile="../ssl/server.crt", keyfile="../ssl/server.key")
++ssock = context.wrap_socket(sock, server_side=True)
+ ssock.settimeout(20)
+ ssock.bind(('', port1))
+ ssock.listen(5)
+--- mosquitto-2.0.11.orig/test/broker/08-ssl-connect-cert-auth-crl.py
mosquitto-2.0.11/test/broker/08-ssl-connect-cert-auth-crl.py
+@@ -31,7 +31,9 @@ broker = mosq_test.start_broker(filename
+
+ try:
+ sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+-ssock = ssl.wrap_socket(sock, ca_certs="../ssl/test-root-ca.crt", certfile="../ssl/client.crt", keyfile="../ssl/client.key", cert_reqs=ssl.CERT_REQUIRED)
++context = ssl.create_default_context(ssl.Purpose.SERVER_AUTH, cafile="../ssl/test-root-ca.crt")
++context.load_cert_chain(certfile="../ssl/client.crt", keyfile="../ssl/client.key")
++ssock = context.wrap_socket(sock, server_hostname="localhost")
+ ssock.settimeout(20)
+ ssock.connect(("localhost", port1))
+
+--- mosquitto-2.0.11.orig/test/broker/08-ssl-connect-cert-auth-expired.py
mosquitto-2.0.11/test/broker/08-ssl-connect-cert-auth-expired.py
+@@ -31,7 +31,9 @@ broker = mosq_test.start_broker(filename
+
+ try:
+ sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+-ssock = ssl.wrap_socket(sock, ca_certs="../ssl/test-root-ca.crt", certfile="../ssl/client-expired.crt", keyfile="../ssl/client-expired.key", cert_reqs=ssl.CERT_REQUIRED)
++context = ssl.create_default_context(ssl.Purpose.SERVER_AUTH, cafile="../ssl/test-root-ca.crt")
++context.load_cert_chain(certfile="../ssl/client-expired.crt", keyfile="../ssl/client-expired.key")
++ssock = context.wrap_socket(sock, server_hostname="localhost")
+ ssock.settimeout(20)
+ try:
+ ssock.connect(("localhost", port1))
+--- mosquitto-2.0.11.orig/test/broker/08-ssl-connect-cert-auth-revoked.py
mosquitto-2.0.11/test/broker/08-ssl-connect-cert-auth-revoked.py
+@@ -30,7 +30,9 @@ broker = mosq_test.start_broker(filename
+
+ try:
+ sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+-ssock = ssl.wrap_socket(sock, ca_certs="../ssl/test-root-ca.crt", certfile="../ssl/client-revoked.crt",
Bug#892058: debian-keyring: please automatically send reminder emails to people whose keys will expire soon
Thanks for the ping! This is very much appreciated. Best, _g.
Bug#1009757: ITP: libtie-cache-lru-perl -- Perl module that implements Least-Recently Used cache
Package: wnpp Severity: wishlist Owner: Paul Gevers X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: libtie-cache-lru-perl Version : 20150301 Upstream Author : Michael G Schwern * URL : https://metacpan.org/release/Tie-Cache-LRU * License : GPL-1+ or Artistic Programming Lang: Perl Description : Perl module for Least-Recently Used cache This is an implementation of a least-recently used (LRU) cache keeping the cache in RAM. A LRU cache is similar to the kind of cache used by a web browser. New items are placed into the top of the cache. When the cache grows past its size limit, it throws away items off the bottom. The trick is that whenever an item is -accessed-, it is pulled back to the top. The end result of all this is that items which are frequently accessed tend to stay in the cache. Debian already has libtie-cache-perl, which is a different implementation of the same idea (they were even developed in competition), but this package is a dependency of the Logitech Mediaserver that I'm working on, which also needs libtie-cache-lru-expires-perl (to be ITPd). I intent to maintain this package under the Perl Team umbrella.
Bug#1003653: Revision of removal of rename.ul from package util-linux
Hi, Thanks for this. 1. While the former "should" is guarded by "requires", I think the latter can be read as a recommendation. I therefore propose replacing it with "must" to make the override more obvious. 2. While option B reads fine to me, option A is a little confusing to me due to the combination of the naming requirement with the mentioning of the conflict. Given the rename.ul name, there seems to be no reason to cause a conflict at all and we can simply require that. As such I think the options should be fully separated. I think I would generally like TC resolutions to be "natural English to be interpreted pragmatically, particularly in light of the rationale" rather than bullet-proof legalese. Now is not the time to die on this particular hill, though :-) ===Begin Resolution A' The Technical Committee overrides the util-linux maintainer, and requires that util-linux's rename should be shipped as /usr/bin/rename.ul in a binary package built from src:util-linux. The package containing rename.ul must not conflict with the rename package nor divert /usr/bin/rename. ===End Resolution A' ===Begin Resolution B' The Technical Committee overrides the util-linux maintainer, and requires that util-linux's rename should be shipped in a binary package built from src:util-linux. If this package Conflicts with the rename package, then it must not contain any other binaries. ===End Resolution B' I hereby modify my options A and B to replace them with the contents of A' and B' thus. [I'll do the necessary C when calling for a vote on the ballot] Thanks, Matthew
Bug#1008815:
In my case, I did not change the xdg-desktop-portal version.
Bug#1009376: running foreign architecture containers hits the network every time and confuses future `podman run` invocations
Control: forwarded -1 https://github.com/containers/podman/issues/13897 On Fri, Apr 15, 2022 at 05:25:31PM -0400, Reinhard Tartler wrote: > Control: tag -1 upstream > > Hi Antonio, > > Can you please file a report upstream here: > https://github.com/containers/podman/issues -- upstream is really friendly > with reports from other Distros, in particular from Debian. I'm not sure > what value I can bring as a package maintainer here. Fair enough. Just did that. signature.asc Description: PGP signature
Bug#668477: cadaver: diff for NMU version 0.23.3-2.2 (new upload)
I sent a new upload now, with 10 days/delay, with the last changes plus removing no longer needed debian/README.source. Regards, Eriberto
Bug#1009375: O: rust-rustls -- Modern TLS library
Quoting Bastian Germann (2022-04-16 13:52:44) > Thank you for adopting the package! You're welcome. Thanks for doing the pioneering work! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1009756: RM: sagemath [armhf mips64el] -- RoM; ANAIS
Package: ftp.debian.org Severity: normal Hi, please remove the python3-sage package on armhf and mips64el from unstable. They are no longer allowed in source as their builds were constantly failing for a long time (#920147, #1004872). Best wishes, Tobias
Bug#1009728: gnome-shell 42.0-3 depends instead of recommends power-profiles-daemon, conflicts with tlp
Hi Gijs, Could you please share the output of dpkg --get-selections | egrep -v install\|purge ? Maybe you've set another package on hold which causes this problem on your system. HTH, Bye, Joost
Bug#1008815:
On Sat, Apr 16, 2022 at 7:09 AM Andre Klapper wrote: > I could reproduce this in Fedora 36 using pipewire 0.3.49. I cannot > reproduce anymore since using pipewire 0.3.50. Is that the only thing that changed on your system? There was also a recent fix in xdg-desktop-portal 1.14.3. Either way, Debian Unstable has both xdg-desktop-portal 1.14.3 and pipewire 0.3.50 now. Thanks, Jeremy Bicha
Bug#1009375: O: rust-rustls -- Modern TLS library
Hi Jonas, Thank you for adopting the package! Cheers, Bastian
Bug#927907: flatpak directories not added to XDG_DATA_DIRS on Plasma + Wayland
Package: flatpak Version: 1.12.7-1 Followup-For: Bug #927907 Hi, unfortunatly, this is still an issue with Plasma. As previously noted, this should be covered by the user-environment-generator, but it seems Plasma isn't using those by default (or their result isn't propagated?), since it's not integrated in the systemd user session. This can be actived by: kwriteconfig5 --file startkderc --group General --key systemdBoot true This makes the environment generator work. https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the-systemd-boot suggests distros not enable this by default, since it breaks drkonqi :( Until this becomes the default, maybe add a file /etc/xdg/plasma-workspace/env/flatpak.sh with the content: eval `GIO_USE_VFS=local flatpak --print-updated-env` export XDG_DATA_DIRS This should add the missing configuration to all new Plasma sessions. See also: - https://userbase.kde.org/Session_Environment_Variables/en - https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma.cpp#L284-301 Best regards, Tobias -- Package-specific info: Permissions of /usr/bin/bwrap: -rwxr-xr-x 1 root root 67984 Feb 25 18:46 /usr/bin/bwrap /etc/sysctl.d/*-bubblewrap.conf: cat: '/etc/sysctl.d/*-bubblewrap.conf': No such file or directory /usr/lib/sysctl.d/50-bubblewrap.conf: # Enable unprivileged creation of new user namespaces in older Debian # kernels. # # If this is not desired, copy this file to # /etc/sysctl.d/50-bubblewrap.conf and change the value of this parameter # to 0, then use dpkg-statoverride to make /usr/bin/bwrap setuid root. # # For more details see https://deb.li/bubblewrap or # /usr/share/doc/bubblewrap/README.Debian kernel.unprivileged_userns_clone=1 /proc/sys/kernel/unprivileged_userns_clone: 1 /proc/sys/user/max_cgroup_namespaces: 31361 /proc/sys/user/max_ipc_namespaces: 31361 /proc/sys/user/max_mnt_namespaces: 31361 /proc/sys/user/max_net_namespaces: 31361 /proc/sys/user/max_pid_namespaces: 31361 /proc/sys/user/max_time_namespaces: 31361 /proc/sys/user/max_user_namespaces: 31361 /proc/sys/user/max_uts_namespaces: 31361 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_GB:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flatpak depends on: ii adduser 3.121 ii bubblewrap 0.6.1-1 ii dbus [default-dbus-system-bus] 1.14.0-1 ii libappstream-glib8 0.7.18-2 ii libarchive133.6.0-1 ii libc6 2.33-7 ii libdconf1 0.40.0-3 ii libfuse22.9.9-5 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-02.72.1-1 ii libgpgme11 1.16.0-1.2 ii libjson-glib-1.0-0 1.6.6-1 ii libmalcontent-0-0 0.10.4-1 ii libostree-1-1 2022.2-3 ii libpolkit-agent-1-0 0.105-33 ii libpolkit-gobject-1-0 0.105-33 ii libseccomp2 2.5.3-2 ii libsoup2.4-12.74.2-3 ii libsystemd0 250.4-1 ii libxau6 1:1.0.9-1 ii libxml2 2.9.13+dfsg-1 ii libzstd11.5.2+dfsg-1 ii xdg-dbus-proxy 0.1.3-1 Versions of packages flatpak recommends: ii ca-certificates 20211016 ii desktop-file-utils 0.26-1 ii gtk-update-icon-cache3.24.33-1 ii hicolor-icon-theme 0.17-2 ii libpam-systemd 250.4-1 ii p11-kit 0.24.0-6 ii policykit-1 0.105-33 ii shared-mime-info 2.1-2 ii xdg-desktop-portal 1.14.2-1 ii xdg-desktop-portal-kde [xdg-desktop-portal-backend] 5.24.4-1 ii xdg-user-dirs0.17-2 Versions of packages flatpak suggests: pn avahi-daemon pn malcontent-gui Versions of packages bubblewrap depends on: ii libc62.33-7 ii libcap2 1:2.44-1 ii libselinux1 3.3-1+b2 Versions of packages bubblewrap recommends: ii procps 2:3.3.17-7+b1 -- no debconf information
Bug#1009755: fdroidserver: autopkgtest failure with python3.10
Source: fdroidserver Version: 2.1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org fdroidserver's autopkgtests fail with python3.10 as default: (Reading database ... 34906 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [08:26:24]: test locales: [--- autopkgtest [08:26:25]: test locales: ---] locales FAIL non-zero exit status 1 autopkgtest [08:26:26]: test locales: - - - - - - - - - - results - - - - - - - - - - See https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/20889924/log.gz Cheers -- Sebastian Ramacher
Bug#1008815:
I could reproduce this in Fedora 36 using pipewire 0.3.49. I cannot reproduce anymore since using pipewire 0.3.50.
Bug#1009754: missing go.d.plugin and epbf support in debian packaging of netdata
Package: netdata Version: 1.34.1-1 dear Daniel Baumann! first of all i really have to thank you for your extraordinary quick netdata debian package maintenance work. nevertheless i still have to report some disappointment about important missing parts in this packages. the go.d.plugin, which in the meanwhile has to be seen as the most important plugin kind of netdata, is still absent in your packages of this new release. another more recent feature, eBPF support, is also not enabled. please add this very important and useful components to your package! it would realize a much more complete and satisfying debian alternative to the upstream binary installer. thanks!
Bug#1009651: ppp: Authentication using EAP-TLS with sstp-client fails with "Connection aborted"
On Wed, 13 Apr 2022 09:20:04 -0700 Eivind Naess wrote: Package: ppp Version: 2.4.9-1+1.1 ... Fix EAP-MSCHAP-V2, invalid name length: https://github.com/ppp-project/ppp/commit/d7e62a8499c4032d79e05afbd8fd3efd51c5b148 This patch is already included in the referenced version.
Bug#1009753: sstp-client: exclude utest_route on kfreebsd
Source: sstp-client Version: 1.0.17-1 Severity: minor The kfreebsd build logs show the following problem: Neither netlink nor iproute2's ip tool are available on kfreebsd, so the utest_route test fails. Please exclude that specific test or the tests generally from being run on kfreebsd (or non-Linux) platforms. If sstp-client is useless on kfreebsd even though it builds, please feel free to close this bug.
Bug#1009747:
It appears installing `dbus-user-session` doesn't fix the problem with excessive messages.
Bug#1009752: Segfaults a while into the game
Package: singularity Version: 1.0.0-1 Severity: important Singularity crashes after playing it for a while, with the following output: Singularity 1.00 (commit: 2ebc2f3f2059b96885416167363bde2e27ece106) Running under Python 3.9.12 (main, Mar 24 2022, 13:02:21) [GCC 11.2.0] pygame 2.1.2 (SDL 2.0.20, Python 3.9.12) Hello from the pygame community. https://www.pygame.org/contribute.html The error-log configured as /home/wouter/.local/share/singularity/log/error.log (lazily created when something is logged) Fatal Python error: pygame_parachute: (pygame parachute) Segmentation Fault Python runtime state: initialized Current thread 0x7f75cd2ea640 (most recent call first): Thread 0x7f75d21ee740 (most recent call first): File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 272 in handle File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 231 in show File "/usr/lib/python3/dist-packages/singularity/code/screens/message.py", line 119 in show File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 125 in call_dialog File "/usr/lib/python3/dist-packages/singularity/code/screens/message.py", line 44 in show_list File "/usr/lib/python3/dist-packages/singularity/code/screens/map.py", line 639 in on_tick File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 405 in call_handlers File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 390 in handle File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 231 in show File "/usr/lib/python3/dist-packages/singularity/code/safety.py", line 64 in safe_call File "/usr/lib/python3/dist-packages/singularity/code/screens/map.py", line 580 in show File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 125 in call_dialog File "/usr/lib/python3/dist-packages/singularity/code/screens/main_menu.py", line 104 in new_game File "/usr/lib/python3/dist-packages/singularity/code/graphics/button.py", line 247 in activated File "/usr/lib/python3/dist-packages/singularity/code/graphics/button.py", line 213 in activate_with_sound File "/usr/lib/python3/dist-packages/singularity/code/graphics/button.py", line 112 in handle_hotkey File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 405 in call_handlers File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 390 in handle File "/usr/lib/python3/dist-packages/singularity/code/graphics/dialog.py", line 231 in show File "/usr/lib/python3/dist-packages/singularity/__init__.py", line 382 in main File "/usr/games/singularity", line 11 in Afgebroken The file error.log that is referred to in the output exists, but is empty. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, riscv64, armhf Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages singularity depends on: ii fonts-dejavu-core 2.37-2 ii python33.9.8-1 ii python3-numpy 1:1.21.5-1 ii python3-polib 1.1.1-1 ii python3-pygame 2.1.2+dfsg-3 Versions of packages singularity recommends: ii singularity-music 007-2 Versions of packages singularity suggests: ii timidity 2.14.0-8+b1 -- no debconf information
Bug#1009750: reserialize: Fail to install because /usr/bin/json2yaml also contained in libghc-yaml-dev.
Hi, On Sat, 16 Apr 2022, at 10:05, Andreas Karnetzki wrote: > Dear Maintainer, > >I have package libghc-yaml-dev (0.11.4.0-1+b4) already installed and wanted >to install reserialize with apt-get. > >Execution of this command failes: > >$ sudo apt-get install --no-install-recommends > >Result: > >dpkg: error processing archive > /var/cache/apt/archives/reserialize_20210909-2_all.deb (--unpack): > trying to overwrite '/usr/bin/json2yaml', which is also in package libghc- > yaml-dev 0.11.4.0-1-b4 > >Expected behavior would be, either use a different name for the conflicting > program, or >use the alternatives system of debian to organize the conflict. Wouldn’t Conflicts: libghc-yaml-dev be enough? -- Cheers, Andrej
Bug#1009751: onak's keyd uses 100% CPU
Package: onak Version: 0.5.0-1 Severity: important Dear Maintainer, on a buster system, keyd uses 100% CPU: onak 30318 98.6 0.0 8864 4884 ?Rs 08:04 5:39 /usr/sbin/keyd -f vz15:~# strace -p 30318 2>&1 | head -20 strace: Process 30318 attached _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) accept(3, 0xffee6d8c, [110])= -1 EINVAL (Invalid argument) _newselect(4, [3], NULL, NULL, NULL)= 1 (in [3]) This is in a LXC container running also on a buster host kernel 4.19.0-17-amd64. Any idea what I should try? Thank you. -- System Information: Debian Release: 10.12 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-20-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=fr_CH.iso-8859-1 (charmap=ISO-8859-1), LANGUAGE=C (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages onak depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii libc62.28-10+deb10u1 ii libcurl3-gnutls 7.64.0-4+deb10u2 ii libdb5.3 5.3.28+dfsg1-0.5 ii libnettle6 3.4.1-1+deb10u1 ii libsystemd0 241-7~deb10u8 ii perl 5.28.1-6+deb10u1 Versions of packages onak recommends: ii apache2 [httpd] 2.4.38-3+deb10u7 Versions of packages onak suggests: pn db-util -- no debconf information
Bug#1003653: Revision of removal of rename.ul from package util-linux
Hi Matthew, On Fri, Apr 15, 2022 at 08:54:16PM +0100, Matthew Vernon wrote: > Thanks for the feedback on my previous draft; here's a revised ballot. Thank you for moving this forward. > ===Rationale > > There are two "rename" programs - the perl rename, and the util-linux > rename. Debian and its derivatives have shipped the perl rename as > /usr/bin/rename, whilst other distributions (e.g. Fedora) have shipped the > util-linux rename thus. The two implementations are incompatible. Users > might reasonably desire both implementations to be available on the same > system; they are designed to meet different needs. > > Backwards-compatibility (and the lack of a compelling argument that rename > from util-linux should replace perl rename) means that /usr/bin/rename in > Debian should remain the perl rename. > > Prior to bullseye, util-linux's rename was shipped as /usr/bin/rename.ul; > Debian's users who wish to use util-linux's rename will expect it to be in > this location. > > ===End Rationale Thank you and others for this. It looks good to me. > ===Begin Resolution > > The Technical Committee overrides the util-linux maintainer, and requires > that util-linux's rename should be shipped in a binary package built from > src:util-linux. If this package Conflicts with the rename package, then it > should not contain any other binaries. > > The Technical Committee further requires that this binary should be shipped > as /usr/bin/rename.ul > > ===End Resolution > > A: Override util-linux maintainer, approve entire resoltuion > B: Override util-linux maintainer, approve only first paragraph of > resolution > N: None of the above I would like to propose two modifications to the ballot. 1. While the former "should" is guarded by "requires", I think the latter can be read as a recommendation. I therefore propose replacing it with "must" to make the override more obvious. 2. While option B reads fine to me, option A is a little confusing to me due to the combination of the naming requirement with the mentioning of the conflict. Given the rename.ul name, there seems to be no reason to cause a conflict at all and we can simply require that. As such I think the options should be fully separated. ===Begin Resolution A' The Technical Committee overrides the util-linux maintainer, and requires that util-linux's rename should be shipped as /usr/bin/rename.ul in a binary package built from src:util-linux. The package containing rename.ul must not conflict with the rename package nor divert /usr/bin/rename. ===End Resolution A' ===Begin Resolution B' The Technical Committee overrides the util-linux maintainer, and requires that util-linux's rename should be shipped in a binary package built from src:util-linux. If this package Conflicts with the rename package, then it must not contain any other binaries. ===End Resolution B' Do these modifications go with your intents and do you want to accept A' and B' as a A and B respectively? In the past discussions on this matter, I was a major force in delaying a ruling in an attempt to resolve this consensually instead of using overriding power and recommended overriding as little as necessary. However, I think that any outcome where we have u-l's rename package conflict with rename is bad for users, because it makes installation sets impossible where a user wants u-l's rename together with some package that happens to depend on rename. This is unlike /usr/bin/python (which also has mutually incompatible interfaces), because we require that no package depends on python-is-python3 nor python-is-python2. We have no such requirement for rename at this time. For that reason, I now think that any solution involving a conflict with rename is going to cause problems sooner or later unless we also require /usr/bin/rename to be shipped by rename-is-prename or rename-is-rename.ul only. The previous paragraph is not meant to influence available vote options. It is only given as a guide on the implications of the vote. Possibly, it would make sense to extend the rationale of option A with a reason for denying the conflict though. Helmut
Bug#1009750: reserialize: Fail to install because /usr/bin/json2yaml also contained in libghc-yaml-dev.
Package: reserialize Version: 20210909-2 Severity: important X-Debbugs-Cc: andreas.karnet...@mnet-mail.de Dear Maintainer, I have package libghc-yaml-dev (0.11.4.0-1+b4) already installed and wanted to install reserialize with apt-get. Execution of this command failes: $ sudo apt-get install --no-install-recommends Result: dpkg: error processing archive /var/cache/apt/archives/reserialize_20210909-2_all.deb (--unpack): trying to overwrite '/usr/bin/json2yaml', which is also in package libghc- yaml-dev 0.11.4.0-1-b4 Expected behavior would be, either use a different name for the conflicting program, or use the alternatives system of debian to organize the conflict. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reserialize depends on: ii python3 3.9.8-1 ii python3-yaml 5.4.1-1+b1 Versions of packages reserialize recommends: pn python3-bson ii python3-toml 0.10.2-1 reserialize suggests no packages.
Bug#1009749: four-in-a-row: crashes when using touchscreen
Package: four-in-a-row Version: 1:3.38.1-1 Severity: important Dear Maintainer, * What led up to the situation? i tried to use the four in a row game with my new thinkpad with touchscreen * What exactly did you do (or not do) that was effective (or ineffective)? started the game and touched the screen to make a move * What was the outcome of this action? the game crashed with Segmentation fault * What outcome did you expect instead? it would work with kind regards -- 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-13-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP 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 four-in-a-row depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii libc6 2.31-13+deb11u3 ii libcairo2 1.16.0-5 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-0 2.66.8-1 ii libgsound0 1.0.2-5 ii libgtk-3-0 3.24.24-4+deb11u2 Versions of packages four-in-a-row recommends: ii yelp 3.38.3-1 four-in-a-row suggests no packages. -- no debconf information
Bug#1009748: dropped liboshmem.so.40.30.X, broken symlink
Package: libopenmpi3 Version: 4.1.3-2 Severity: normal Hi, libopenmpi3 in bookworm no longer provides a liboshmem.so.40.30.X and the liboshmem.so.40 -> liboshmem.so.40.30.1 is broken. Can you please fix this? Cheers Jochen -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) 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 libopenmpi3 depends on: ii libc62.33-7 ii libevent-core-2.1-7 2.1.12-stable-4 ii libevent-pthreads-2.1-7 2.1.12-stable-4 ii libfabric1 1.11.0-3 ii libgcc-s112-20220319-1 ii libhwloc-plugins 2.7.1-1 ii libhwloc15 2.7.1-1 ii libibverbs1 39.0-1+b1 ii libnl-3-200 3.5.0-0.1 ii libpmix2 4.1.2-2 ii libpsm-infinipath1 3.3+20.604758e7-6.1 ii libpsm2-211.2.185-1 ii libstdc++6 12-20220319-1 ii libucx0 1.12.1-1 ii zlib1g 1:1.2.11.dfsg-4 libopenmpi3 recommends no packages. libopenmpi3 suggests no packages. -- no debconf information
Bug#1009747: Missing dependency on dbus-user-session
Package: podman Version: 3.0.1+dfsg1-3+deb11u1 All `podman` commands produce a lot of warnings on default install. $ podman version WARN[] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[] For using systemd, you may need to login using an user session WARN[] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root) WARN[] Falling back to --cgroup-manager=cgroupfs WARN[] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[] For using systemd, you may need to login using an user session WARN[] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root) WARN[] Falling back to --cgroup-manager=cgroupfs Version: 3.0.1 API Version: 3.0.0 Go Version: go1.15.15 Built:Thu Jan 1 00:00:00 1970 OS/Arch: linux/amd64 As mentioned in `podman` tracker this is because of missing dependency on `dbus-user-session` https://github.com/containers/podman/issues/12983#issuecomment-1019581809
Bug#1009579: [Pkg-javascript-devel] Bug#1009579: node-qs: FTBFS: Error: module util in /<>/node_modules/object-inspect not found
Control: reasign -1 dh-nodejs Control: found -1 0.14.8 Control: affects -1 node-qs On 12/04/2022 21:24, Lucas Nussbaum wrote: Source: node-qs Version: 6.10.3+ds+~6.9.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' dh_auto_build mkdir dist browserify-lite ./lib/index.js --outfile dist/qs.js /usr/share/nodejs/browserify-lite/cli.js:29 if (err) throw err; ^ Problem is that "util" is now a built-il module but also a module. Here, debian/nodejs/extcopies contain "util" but pkgjs-ln builds a bad link because it uses node-path result which does not give a valid path
Bug#881910: ITA: libcdio-paranoia -- library to read and control digital audio CDs (was: Bug#881910: O: libcdio and libcdio-paranoia)
Hello Gabriel, On Mon, Oct 18, 2021 at 08:37:10PM +0200, Bastian Germann wrote: > On Tue, 4 Feb 2020 23:10:06 -0300 "Gabriel F. T. Gomes" wrote: > > I maintain pragha, which depends on this package, so I'll adopt it. > It is now 1.5 years since you filed the ITA. There is a new upstream version > that is unpackaged. Do you still want to take over maintainership? Could you please comment on this, thanks. Cheers, Flo signature.asc Description: PGP signature
Bug#1009746: libzstd: Buildlog is not verbose
Source: libzstd Version: 1.5.2+dfsg-1 Severity: normal Tags: patch Good morning, libzstd's build is quiet by default and the debian/rules does not override this (see pol. 4.9). Find attached a patch to change this. Thanks, cu Andreas diff -Nru libzstd-1.5.2+dfsg/debian/rules libzstd-1.5.2+dfsg/debian/rules --- libzstd-1.5.2+dfsg/debian/rules 2022-04-11 14:04:47.0 +0200 +++ libzstd-1.5.2+dfsg/debian/rules 2022-04-16 08:33:38.0 +0200 @@ -6,6 +6,11 @@ DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) export DEB_BUILD_MAINT_OPTIONS=hardening=+all +ifeq (,$(filter terse,$(DEB_BUILD_OPTIONS))) +# enable upstream verbose build + export VERBOSE=1 +endif + # Upstream's makefiles will respect PREFIX, and this means we avoid a patch export PREFIX=/usr
