Bug#1050027: blocking migration of other OCaml packages to testing
Dear Julien, Le 19/08/2023 à 20:58, Helmut Grohne a écrit : Control: reopen -1 Control: found -1 mathcomp-analysis/0.6.4-2 On Sat, Aug 19, 2023 at 05:33:11PM +, Debian Bug Tracking System wrote: It has been closed by Debian FTP Masters (reply to Julien Puydt ). I'm sorry. Adding Breaks is necessary but insufficient. You also need Replaces. Can you fix this quickly, please? This is preventing (at least) 7 packages to migrate to testing: js-of-ocaml-ocamlbuild, ocaml-alcotest, ocaml-re, ocaml-stdio, ocaml-stringext, ocaml-time-now, pgocaml. With dh-ocaml (which will be old enough tomorrow) and mathcomp-analysis, they are all the OCaml packages that are not in sync between unstable and testing... You can argue later and elsewhere (debian-devel or a bug report against the policy). Cheers, -- Stéphane
Bug#1050319: RFS: golang-github-seancfoley-bintree/1.2.1-1 [ITP] -- Binary trees and tries
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian...@lists.debian.org X-Debbugs-CC: james...@debian.org X-Debbugs-CC: nil...@debian.org Dear mentors, I am looking for a sponsor for my package "golang-github-seancfoley-bintree": * Package name : golang-github-seancfoley-bintree Version : 1.2.1-1 * URL : https://github.com/seancfoley/bintree * License : Apache-2.0 * Vcs : https://salsa.debian.org/go-team/packages/golang-github-seancfoley-bintree Section : golang The source builds the following binary packages: golang-github-seancfoley-bintree-dev - Binary trees and tries To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-seancfoley-bintree/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-seancfoley-bintree/golang-github-seancfoley-bintree_1.2.1-1.dsc Changes for the initial release: golang-github-seancfoley-bintree (1.2.1-1) unstable; urgency=medium . * Initial release (Closes: #1050308) Regards,
Bug#1022702: [pkg-gnupg-maint] Bug#1022702: gnupg: Migrating packaging from 2.2.x to "stable" 2.3.x
NIIBE Yutaka wrote: > Besides, in my opinion, the agent_cache_housekeeping function makes less > sense (it's totally OK to only check the expiration on its use). Having > expired entries on memory is no problem at all, than running gpg-agent > process periodically; memory is cheap but buttery power is not (for my > use case). I was wrong. The ticket for agent_cache_housekeeping is: https://dev.gnupg.org/T3829 It was introduced because of some risk keeping passphrase. I'd like to consider to improve the implementation of cache and expiration, not using handle_tick. --
Bug#1050318: kgb: please add support for loong64
Source: kgb Version: 1.0b4+ds-14 Severity: normal X-Debbugs-Cc: zhangjial...@loongson.cn Dear Maintainer, Please add loong64 to architectures list. I have build this in loong64.
Bug#1022702: [pkg-gnupg-maint] Bug#1022702: gnupg: Migrating packaging from 2.2.x to "stable" 2.3.x
NIIBE Yutaka wrote: > Based on your work of tmp-ametzler-v2.4 branch, I created my own fork. > > My hope is that the migration from 2.4 won't introduce (much) surprise > to Debian users. > >https://salsa.debian.org/gniibe/gnupg2/-/tree/tmp-gniibe-v2.4 > > This work of mine is: > > - Keep systemd support (despite its deprecation in upstream) > - Introduce keyboxd package (with systemd support, for integrity) > - Put backport of BEGIN_ENCRYPTION status output (from master of upstream) Further, I recover the patches/gpg-agent-idling series. - Enable patches/gpg-agent-idling In the upstream, scd monitoring has improved by introducing a watching thread. I updated the patches to address this change of scd monitoring. Actually, we can improve the code more. On Windows, since parent_pid is always -1 (running command by gpg-agent is not supported), the need_tick function should return 0. And the return value of the need_tick function is determined at initialization, we can clean up the code. Besides, in my opinion, the agent_cache_housekeeping function makes less sense (it's totally OK to only check the expiration on its use). Having expired entries on memory is no problem at all, than running gpg-agent process periodically; memory is cheap but buttery power is not (for my use case). --
Bug#1050317: Please apply OAuth fixes in bookworm
Package: roundcube-core Version: 1.6.1+dfsg-1 Severity: important Hi! I was trying to setup OAuth2 in Roundcube, and after lots of head-scratching, I figured out that it wasn't working due to some known and fixed errors upstream. It would be very good if we could have a proposed-update upload for bookworm with the fixes in https://github.com/roundcube/roundcubemail/commit/f7635575f6074a2d064832d610c67c873517384c and https://github.com/roundcube/roundcubemail/commit/ca1b23ea9d8ddbfeaf973158f508a5f70ae51db8 and additionally a backport of https://salsa.debian.org/roundcube-team/roundcube/-/commit/3f5fd4677abdf25224a2c05047a5a9d7490cf159 Thanks, Jordi -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca_ES:ca Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages roundcube-core depends on: pn dbconfig-common ii debconf [debconf-2.0] 1.5.82 ii dpkg 1.21.22 ii libjs-bootstrap4 4.6.1+dfsg1-4 pn libjs-codemirror ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 pn libjs-jquery-minicolors ii libjs-jquery-ui1.13.2+dfsg-1 pn libjs-jstimezonedetect ii libmagic1 1:5.44-3 pn php pn php-auth-sasl pn php-cli pn php-common pn php-guzzlehttp-guzzle pn php-intl pn php-json pn php-mail-mime pn php-masterminds-html5 pn php-mbstring pn php-net-sieve pn php-net-smtp pn php-pear pn roundcube-mysql | roundcube-sqlite3 | roundcube-pgsql ii ucf3.0043+nmu1 Versions of packages roundcube-core recommends: pn apache2 | lighttpd | spawn-fcgi | php-fpm | httpd-cgi pn php-enchant pn php-gd pn roundcube-skin-classic pn roundcube-skin-larry Versions of packages roundcube-core suggests: pn php-bacon-qr-code pn php-bjeavons-zxcvbn-php pn php-crypt-gpg pn php-net-ldap3 pn php-roundcube-rtf-html-php pn roundcube-plugins
Bug#1050316: apt-setup: Unable to use local repo when installing older release
Source: apt-setup Version: 1:0.183 Severity: normal Tags: d-i X-Debbugs-Cc: ssg...@debian.org I sometimes use the current stable d-i to install the n-1 release when I need to install on hardware that requires a newer kernel, then I install the backport kernel in the preseed so the system boots. With the bookworm debian-installer, my local apt repo does not get successfully added to the system. After some debugging, I determined the issue is here: https://salsa.debian.org/installer-team/apt-setup/-/blob/master/generators/60local#L46 The /etc/apt/keyrings directory wasn't added to the apt package until apt 2.4.0, but bullseye only ships with 2.2.4. The fix here is simple and I believe it to be low risk: the generator just needs to run "mkdir -p /etc/apt/keyrings" at the beginning of 60local. Since newer versions of apt already create that empty directory it will be a no-op for them. In case anyone else runs into this issue and stumbles onto this bug, I was able to work around it by adding the following to my preseed: d-i partman/early_command string printf "#!/bin/sh\nmkdir -p \$ROOT/etc/apt/keyrings\n" > /usr/lib/apt-setup/generators/02fixbug && chmod +x /usr/lib/apt-setup/generators/02fixbug I understand that the current release is the main priority of d-i but given the fix seems to be low risk it would be appreciated if it could be fixed in stable! -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1050315: Please include sun8i-drm-hdmi module in installer
Package: fb-modules-6.4.0-3-arm64-di Version: 6.4.11-1 Severity: normal Tags: patch Dear Debian Kernel Team, Please could you include the sun8i-drm-hdmi module in the fb-modules udeb for arm64? It would allow the installer to run on a local HDMI display on some 64-bit Allwinner boards such as the Orange Pi One Plus. (Currently installation has to be done over the serial port.) I've suggested a patch below. Thank you very much, Harold. --- debian/installer/modules/arm64/fb-modules +++ debian/installer/modules/arm64/fb-modules.new @@ -20,6 +20,9 @@ # For panel/backlight on Pinebook Pro pwm-rockchip +# For HDMI on some sunxi platforms (e.g. Orange Pi 1+) +sun8i-drm-hdmi + # For HDMI on some rockchip platforms (e.g. rock64-rk3328) nvmem-rockchip-efuse phy-rockchip-inno-hdmi
Bug#1050005: ITP: pdftopng -- Convert PDF to PNG
On Tue, Aug 22, 2023 at 01:24:42PM +0200, Mathieu Malaterre wrote: > On Fri, Aug 18, 2023 at 1:19 PM Marvin Renich wrote: > > > > * Elena Grandi [230818 05:27]: > > > Package: wnpp > > > Severity: wishlist > > > Owner: Elena Grandi > > > > > > * Package name: pdftopng > > > Description : Convert PDF to PNG > > > > > > A command line tool and python library to convert PDFs to PNGs, based on > > > pdftoppm from poppler. > > uh ? > > % pdftoppm -h 2>&1| grep png > -png : generate a PNG file > > > > This is a dependency of camelot-py (#1049944) and I intend to maintain > > > it in the Python Team. > > > > Does pdftocairo from the poppler-utils package do what you need? If > > not, would it make sense to submit patches to add pdftopng to the > > poppler-utils package instead of creating a separate package for it? > > ...or at least document why pdftoppm is not suitable. I would imagine, since the original ITP also mentioned a Python project that requires this package, that the "Python library" part may be important: the upstream authors of the other project may have decided to use it, as a Python library, instead of fiddling with child process management by themselves. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1050314: ITP: golang-github-sigstore-rekor -- Software Supply Chain Transparency Log
Package: wnpp Severity: wishlist Owner: Reinhard Tartler * Package name: golang-github-sigstore-rekor Version : 1.2.2-1 Upstream Author : sigstore * URL : https://github.com/sigstore/rekor * License : Apache-2.0 Programming Lang: Go Description : Software Supply Chain Transparency Log Rekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software projects supply chain. Rekor will enable software maintainers and build systems to record signed metadata to an immutable record. Other parties can then query said metadata to enable them to make informed decisions on trust and non-repudiation of an object's lifecycle. . The Rekor project provides a restful API based server for validation and a transparency log for storage. A CLI application is available to make and verify entries, query the transparency log for inclusion proof, integrity verification of the transparency log or retrieval of entries by either public key or artifact. . Rekor fulfils the signature transparency role of sigstore's software signing infrastructure. However, Rekor can be run on its own and is designed to be extensible to working with different manifest schemas and PKI tooling. This package will be maintained under the pkg-golang community's umbrella. It is going to be used by container management tools that are linked into podman
Bug#1049458: celluloid: fails to start due to failed assertion in stream.c
Hi, On Fri, Aug 18, 2023 at 12:28 PM Stefan Breunig wrote: > > Hi, > > very good hints. I have created upstream issue > https://github.com/celluloid-player/celluloid/issues/880 which also has > more detail than this bug report. > > Thanks > Stefan > Build the package and test it by updating what you already have (which is present in the repository) and kindly let me know if the problem remains with the patch added. I hope it's resolved. https://mentors.debian.net/debian/pool/main/c/celluloid/ -- Cheers, Leandro Cunha -BEGIN PGP PUBLIC KEY BLOCK- mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh 0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7 ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3 k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx /m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C +DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4 hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08 iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X 7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00 4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9 WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O +SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW fNdY6Ns= =rdCA -END PGP PUBLIC KEY BLOCK-
Bug#1050313: kde-spectacle: crash because of missing dependencies
Package: kde-spectacle
Version: 23.04.2-2
Severity: important
specatecle needs "libqt5quickshapes5" & "qml-module-qtquick-shapes" installed.
without these it will crash:
$ spectacle
kf.kirigami: Failed to find a Kirigami platform plugin
qrc:/src/Gui/ScreenshotView.qml:167:9: Type AnnotationEditor unavailable
qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type TextTool unavailable
qrc:/src/Gui/Annotations/TextTool.qml:162:21: Type SelectionBackground
unavailable
qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes"
is not installed
qrc:/src/Gui/ImageCaptureOverlay.qml:36:5: Type AnnotationEditor unavailable
AnnotationEditor {
^
qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type TextTool unavailable
TextTool {
^
qrc:/src/Gui/Annotations/TextTool.qml:162:21: Type SelectionBackground
unavailable
background: SelectionBackground { zoom: root.viewport.zoom }
^
qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes"
is not installed
import QtQuick.Shapes 1.15
^
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kde-spectacle depends on:
ii kio5.107.0-1
ii libc6 2.37-7
ii libkf5configcore5 5.107.0-1
ii libkf5configgui5 5.107.0-1
ii libkf5configwidgets5 5.107.0-2
ii libkf5coreaddons5 5.107.0-1
ii libkf5dbusaddons5 5.107.0-1
ii libkf5globalaccel-bin 5.107.0-2
ii libkf5globalaccel5 5.107.0-2
ii libkf5guiaddons5 5.107.0-1
ii libkf5i18n55.107.0-1+b1
ii libkf5kiocore5 5.107.0-1
ii libkf5kiogui5 5.107.0-1
ii libkf5kiowidgets5 5.107.0-1
ii libkf5kirigami2-5 5.107.0-1+b1
ii libkf5notifications5 5.107.0-1
ii libkf5purpose-bin 5.107.0-1
ii libkf5purpose5 5.107.0-1
ii libkf5service-bin 5.107.0-1
ii libkf5service5 5.107.0-1
ii libkf5widgetsaddons5 5.107.0-1
ii libkf5windowsystem55.107.0-1
ii libkf5xmlgui5 5.107.0-1+b1
ii libkpipewirerecord55.27.7-1
ii libqt5core5a 5.15.10+dfsg-3
ii libqt5dbus55.15.10+dfsg-3
ii libqt5gui5 5.15.10+dfsg-3
ii libqt5printsupport55.15.10+dfsg-3
ii libqt5qml5 5.15.10+dfsg-2
ii libqt5quick5 5.15.10+dfsg-2
ii libqt5waylandclient5 5.15.10-2
ii libqt5widgets5 5.15.10+dfsg-3
ii libqt5x11extras5 5.15.10-2
ii libstdc++6 13.2.0-2
ii libwayland-client0 1.22.0-2
ii libxcb-cursor0 0.1.4-1
ii libxcb-image0 0.4.0-2
ii libxcb-util1 0.4.0-1+b1
ii libxcb-xfixes0 1.15-1
ii libxcb11.15-1
ii qdbus-qt5 5.15.10-3
kde-spectacle recommends no packages.
kde-spectacle suggests no packages.
-- no debconf information
Bug#1042215: cegui-mk2: FTBFS: dh_install: error: missing files, aborting
Control: tag -1 unreproducible Control: severity -1 important Hello Lucas and thanks for the bug report. Unfortunately, I am unable to reproduce this behavior. I just uploaded a new version of this package to fix an unrelated bug and it built normally on the buildds. I'm leaving this as "important" because what you observed on CI is definitely *not* desired behavior. However, I'm not sure what else I can do until we figure out exactly what caused this. Do you think it may have been some sort of transient issue related to starting up trixie? Let me know how you'd like to move forward on this. -Olek
Bug#1037044: Forced password reset leaves behind failed user@.service unit
Control: fixed -1 254.1-2 On Fri, 2 Jun 2023 13:22:02 -0400 Jason Franklin wrote: Package: systemd Version: 252.6-1 Severity: normal Greetings: It appears that user@.service is left in a failed state when a user logs in over ssh and is forced to reset their password due to expiration. I was able to regularly reproduce this behavior with the process described below. # Create a test user. $ sudo adduser fish ... # Ensure no failed units. $ systemctl list-units --failed ... # Expire the user's password. $ sudo passwd -e fish # Log in via ssh. Properly change the user's password when prompted. $ ssh fish@localhost ... # Here, you will be kicked back out to your prompt after the new # password is set. # Now, note that a failed unit for the user is left behind. $ systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION * user@1001.service loaded failed failed User Manager for UID 1001 ... I think the above accurately describes the behavior I'm seeing. It seems odd to me that the failed service lingers even though the user's password has been changed correctly, without any real failures in the process. The user is now able to log in and what not, but systemd indicates a failure. This is an issue for me because these failures can stack up on systems at my work, and monitoring of failed units then indicates a problem where there is not one. Please let me know any thoughts on this. It could be another piece of software that's causing the error. Or, it could be that I have something improperly configured or that I am misinterpreting things. Seems to work in trixie/sid, so marking as fixed for that version. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050303: extension no longer works with Gnome 44
Actually I reported this problem in the Debian BTS because I was not 100% sure that this is an upstream issue (the error message is actually compatible with a missing file in the .deb). I prefer that you report it upstream yourself if your are confident that this is not an issue in the packaging. Thanks! Le mardi 22 août 2023 à 13:30 -0700, Francois Marier a écrit : > Bonjours Sébastien, > > It does look like a different error message indeed. > > Are you happy to also report this new problem upstream, or would you prefer > I forward your email to upstream's GitHub issue tracker myself? > > Francois > > On 2023-08-22 at 12:35:24, Sébastien Villemot (sebast...@debian.org) wrote: > > Package: workrave-gnome > > Version: 1.10.51.1-2 > > Severity: normal > > > > Dear Maintainer, > > > > After upgrading to gnome-shell 44, the extension no longer works. > > > > In the Extensions application, I am unable to activate the extension, and > > the > > following message is displayed: > > > > Requiring Workrave, version 2.0: Typelib file for namespace 'Workrave', > > version '2.0' not found > > > > Note that this seems to be a different issue than the following upstream > > one: > > https://github.com/rcaelers/workrave/issues/487 > > > > Thanks for your work, > > > > -- > > ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot > > ⣾⠁⢠⠒⠀⣿⡁ Debian Developer > > ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name > > ⠈⠳⣄ https://www.debian.org -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#1006927: /usr/bin/dh_fixperms: please don't make all files executable in subdirectories of /usr/libexec
Hi, I think that what valgrind does is a plain (_minor_) mistake that makes libexec hard to audit and should not be used as a good practice reference. So I filed #1043527 against Valgrind. I think this will/would require some change in V's upstream; I'll have a look again at it later. > * Valgrind uses /usr/libexec/valgrind for private data that is > a mixture of executables, non-executable XML files, and shared libraries > Presumably other use-cases like valgrind... Greetings, Alexandre https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043527 (Severity: minor)
Bug#1050312: gtk4: a change in some dependency caused different line wrapping on i386 only
Source: gtk4 Version: 4.10.5+ds-4 Severity: normal User: debian...@lists.debian.org Usertags: i386 X-Debbugs-Cc: b...@debian.org gtk4 4.12.0 failed some tests on i386, which I initially thought were a regression in 4.12.0, but then 4.10.5+ds-4 failed in the same way. 4.10.5+ds-3 and 4.10.5+ds-4 are essentially the same (the only changes were unrelated) so this must have been triggered to a change to a dependency: I would guess fontconfig and pango1.0 are the most likely candidates. I don't know whether this results in user-visible regressions to GTK 4 applications on i386; that would be a question for someone who is routinely using a full i386 system. These are reftests, which work by rendering GTK's internal representation of two UIs (loaded from text files) to an image, and comparing them. The idea is that they're two different ways to achieve the same result, one simple and one exercising some more complicated code path. The tests still pass on every other architecture, so I suspect that what's happening here might be that different rounding from the i387 floating point interface having extended-precision registers, and as a result of that different rounding, the text is a very slightly different width? To reproduce: build gtk4 source package. Expected (good) result: the two affected reftests pass, and do not leave output files in debian/build/deb/testsuite/reftests/output/x11/. Actual (bad) result: they do leave output files. This does not cause FTBFS or cause them to be marked as failures, but only because we've told the test suite to ignore them. Alternative bad result: before version 4.10.5+ds-5, the failures were not ignored and caused FTBFS. Logs: success (slightly older versions of dependencies): https://buildd.debian.org/status/fetch.php?pkg=gtk4=i386=4.10.5%2Bds-3=1691406899=0 failure: https://buildd.debian.org/status/fetch.php?pkg=gtk4=i386=4.10.5%2Bds-4=1692723794=0 failure ignored: https://buildd.debian.org/status/fetch.php?pkg=gtk4=i386=4.10.5%2Bds-5=1692731298=0 smcv 0 Hello World end True char 0 Hello World True char 0 Hello World 1 0 Hello World 1
Bug#1049960: ITP: half -- C++ library for half precision floating point arithmetics
Hi Mathieu, On 2023-08-22 13:29, Mathieu Malaterre wrote: > On Thu, Aug 17, 2023 at 1:27 PM Christian Kastner wrote: >> * Package name: half >> Version : 2.2.0 >> Upstream Author : Christian Rau >> * URL : https://sourceforge.net/projects/half/ >> * License : MIT >> Programming Lang: C++ >> Description : C++ library for half precision floating point arithmetics >> >> This is a C++ header-only library to provide an IEEE-754 conformant >> half-precision floating point type along with corresponding arithmetic > > What's the difference with https://packages.debian.org/sid/libimath-dev ? I don't know the particular differences. MIOpen depends on this particular implementation. >> operators, type conversions and common mathematical functions. It aims >> for both efficiency and ease of use, trying to accurately mimic the >> behaviour of the builtin floating point types at the best performance >> possible. It automatically uses and provides C++11 features when >> possible, but stays completely C++98-compatible when neccessary. > > I believe gcc+c++20 provides _Float16 already. Who needs c++98 compat ? I guess I could raise that at MIOpen upstream. In any case, the package will remain in experimental until MIOpen itself is ready. >> This is needed by MIOpen, which is also in the process of being >> packaged. Best, Christian
Bug#1050311: bookworm-pu: package imlib2/1.10.0-4
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: a...@debian.org [ Reason ] Fixing Debian bug #1041406 in Bookworm. imlib_clone_image() no longer preserves the alpha channel flag. [ Impact ] This was an unintentional upstream change which also affects libimage-imlib2-perl and every developer who relies on the preservation of the alpha channel flag in imlib_clone_image() [ Tests ] Debian bug #1041406 has a test program attached which demonstrates the regression in Bookworm and that 1.10.0-4+deb12u1 contains the fix. [ Risks ] Low. This is a straightforward fix with a clear reproducer. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable Regards, Markus diff -Nru imlib2-1.10.0/debian/changelog imlib2-1.10.0/debian/changelog --- imlib2-1.10.0/debian/changelog 2023-01-02 23:10:40.0 +0100 +++ imlib2-1.10.0/debian/changelog 2023-08-22 22:52:24.0 +0200 @@ -1,3 +1,10 @@ +imlib2 (1.10.0-4+deb12u1) bookworm; urgency=medium + + * Fix imlib_clone_image() no longer preserves the alpha channel flag. + (Closes: #1041406) + + -- Markus Koschany Tue, 22 Aug 2023 22:52:24 +0200 + imlib2 (1.10.0-4) unstable; urgency=medium * Really ignore libjxl-dev on s390x. diff -Nru imlib2-1.10.0/debian/patches/debian-bug-1041406.patch imlib2-1.10.0/debian/patches/debian-bug-1041406.patch --- imlib2-1.10.0/debian/patches/debian-bug-1041406.patch 1970-01-01 01:00:00.0 +0100 +++ imlib2-1.10.0/debian/patches/debian-bug-1041406.patch 2023-08-22 22:52:24.0 +0200 @@ -0,0 +1,38 @@ +From 173edae4bf72e01b0dada41a406d34f976b1fc28 Mon Sep 17 00:00:00 2001 +From: Kim Woelders +Date: Wed, 19 Jul 2023 18:11:08 +0200 +Subject: [PATCH] image: Fix preservation of alpha chanel flag in + imlib_clone_image() + +https://git.enlightenment.org/old/legacy-imlib2/issues/17: + +As per subject, the imlib_clone_image() function no longer preserves +the alpha channel value since imlib2 1.10.0. + +This bug report was initially filed by Niko Tyni in Debian's bug tracker. +If you follow the subsequent link you will also find a test program that +demonstrates the regression. + +https://bugs.debian.org/1041406 + +This upstream change is most likely the root cause of the problem + +b39d33c800 + +It looks like an oversight where other functions were adapted +to the new alpha channel implementation, but imlib_clone_image() remains +unchanged and only copies the flags and not the new alpha byte. +--- + src/lib/api.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/src/lib/api.c b/src/lib/api.c +@@ -1017,6 +1017,7 @@ imlib_clone_image(void) + return NULL; + } +memcpy(im->data, im_old->data, im->w * im->h * sizeof(uint32_t)); ++ im->has_alpha = im_old->has_alpha; +im->flags = im_old->flags; +IM_FLAG_SET(im, F_UNCACHEABLE); +im->moddate = im_old->moddate; diff -Nru imlib2-1.10.0/debian/patches/remove-data-dir.patch imlib2-1.10.0/debian/patches/remove-data-dir.patch --- imlib2-1.10.0/debian/patches/remove-data-dir.patch 2023-01-02 23:10:40.0 +0100 +++ imlib2-1.10.0/debian/patches/remove-data-dir.patch 2023-08-22 22:52:24.0 +0200 @@ -10,8 +10,6 @@ configure.ac | 3 --- 2 files changed, 1 insertion(+), 4 deletions(-) -diff --git a/Makefile.am b/Makefile.am -index 3371af3..d93301b 100644 --- a/Makefile.am +++ b/Makefile.am @@ -2,7 +2,7 @@ AUTOMAKE_OPTIONS = foreign @@ -23,8 +21,6 @@ if BUILD_DOC SUBDIRS += doc endif -diff --git a/configure.ac b/configure.ac -index 791f44d..8df303a 100644 --- a/configure.ac +++ b/configure.ac @@ -280,9 +280,6 @@ src/modules/Makefile diff -Nru imlib2-1.10.0/debian/patches/series imlib2-1.10.0/debian/patches/series --- imlib2-1.10.0/debian/patches/series 2023-01-02 23:10:40.0 +0100 +++ imlib2-1.10.0/debian/patches/series 2023-08-22 22:52:24.0 +0200 @@ -1 +1,2 @@ remove-data-dir.patch +debian-bug-1041406.patch
Bug#1050305: dh-python: Packages using distutils-extra missing dependencies
Hi, the 'requires' are actually generated by DistUtilsExtra.auto and are present in the PKG-INFO file in the .egg-info directory. It seems dh-python is not picking them up correctly, thus reassigning. Best, Philip OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050309: mirror submission for mirror.0x626b.com
Debian mirror team, please cancel this request. The email address is incorrect. The corrected request is under Bug 1050310. Thanks! ./brent
Bug#1050303: extension no longer works with Gnome 44
Bonjours Sébastien, It does look like a different error message indeed. Are you happy to also report this new problem upstream, or would you prefer I forward your email to upstream's GitHub issue tracker myself? Francois On 2023-08-22 at 12:35:24, Sébastien Villemot (sebast...@debian.org) wrote: > Package: workrave-gnome > Version: 1.10.51.1-2 > Severity: normal > > Dear Maintainer, > > After upgrading to gnome-shell 44, the extension no longer works. > > In the Extensions application, I am unable to activate the extension, and the > following message is displayed: > > Requiring Workrave, version 2.0: Typelib file for namespace 'Workrave', > version '2.0' not found > > Note that this seems to be a different issue than the following upstream one: > https://github.com/rcaelers/workrave/issues/487 > > Thanks for your work, > > -- > ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot > ⣾⠁⢠⠒⠀⣿⡁ Debian Developer > ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name > ⠈⠳⣄ https://www.debian.org
Bug#1050310: mirror submission for mirror.0x626b.com
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.0x626b.com Archive-architecture: amd64 arm64 i386 riscv64 Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Brent Kolasinski Country: US United States Location: Kansas City, MO Sponsor: Brent Kolasinski https://brentk.io Comment: Sorry - had an incorrect email address in the last submission. This submission has correct information: mirrorad...@0x626b.com instead of mailad...@0x626b.com Trace Url: http://mirror.0x626b.com/debian/project/trace/ Trace Url: http://mirror.0x626b.com/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.0x626b.com/debian/project/trace/mirror.0x626b.com
Bug#1050309: mirror submission for mirror.0x626b.com
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.0x626b.com Archive-architecture: amd64 arm64 i386 riscv64 Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Brent Kolasinski Country: US United States Location: Kansas City, MO Sponsor: Brent Kolasinski https://brentk.io Trace Url: http://mirror.0x626b.com/debian/project/trace/ Trace Url: http://mirror.0x626b.com/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.0x626b.com/debian/project/trace/mirror.0x626b.com
Bug#1050238: wxwidgets3.2: FTBFS: testsuite issues
On 2023-08-22 15:40, Aurelien Jarno wrote:
> |
> ---
> | wxImage::Paste
> | Paste semitransparent image over transparent image
> |
> ---
> | ./image/image.cpp:1931
> |
> ...
> |
> | ./image/image.cpp:1945: FAILED:
> | CHECK_THAT( actual,
> RGBSimilarTo(wxImage("image/paste_result_no_background_square_over_circle.png"),
> 1) )
> | with expansion:
> | image of size 100*100 with alpha doesn't have the same RGB data as image
> of
> | size 100*100 with alpha: first mismatch is at (0, 0) which has value
> | 0xff00 instead of the expected 0x
> |
That part is an upstream issue reported as
https://github.com/wxWidgets/wxWidgets/issues/23791
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
Bug#1050308: ITP: golang-github-seancfoley-bintree -- Golang library Binary trees and tries
Package: wnpp Severity: wishlist Owner: M Hickford X-Debbugs-Cc: debian-de...@lists.debian.org, mirth.hickf...@gmail.com * Package name: golang-github-seancfoley-bintree * URL : https://github.com/seancfoley/bintree * License : Apache2 Programming Lang: Go Description : Golang library Binary trees and tries Transitive dependency for kitty
Bug#1050307: libdata-format-html-perl: autopkgtest failure with Perl 5.38: given is deprecated
Source: libdata-format-html-perl Version: 0.5.1-2 Severity: important Tags: trixie sid User: debian-p...@lists.debian.org Usertags: perl-5.38-transition autopkgtest This package fails its autopkgtest checks with Perl 5.38 (currently in experimental.) https://ci.debian.net/data/autopkgtest/unstable/amd64/libd/libdata-format-html-perl/37062112/log.gz 56s autopkgtest [20:13:39]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps 56s autopkgtest [20:13:39]: test autodep8-perl: [--- 56s 56s # Failed test ' /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 produced no (non-whitelisted) output' 56s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 56s # Structures begin differing at: 56s # $got->[0] = 'given is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 193. 56s # ' 56s # $expected->[0] = Does not exist 56s 56s # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 produced no (non-whitelisted) output' 56s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 56s # Structures begin differing at: 56s # $got->[0] = 'given is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 193. 56s # ' 56s # $expected->[0] = Does not exist 56s # Looks like you failed 2 tests of 4. 56s /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 56s 1..4 56s # given is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 193. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 194. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 195. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 196. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 197. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 199. 56s ok 1 - /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 exited successfully 56s not ok 2 - /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 produced no (non-whitelisted) output 56s # given is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 193. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 194. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 195. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 196. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 197. 56s # when is deprecated at /usr/share/perl5/Data/Format/HTML.pm line 199. 56s ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 exited successfully 56s not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Data::Format::HTML" -e 1 2>&1 produced no (non-whitelisted) output 56s Dubious, test returned 2 (wstat 512, 0x200) 56s Failed 2/4 subtests -- Niko Tyni nt...@debian.org
Bug#1050238: wxwidgets3.2: FTBFS: testsuite issues
On Tue, Aug 22, 2023 at 03:40:57PM +0200, Aurelien Jarno wrote: > It appears that the failing tests are already filtered on some > architectures, would it be possible to do the same on riscv64 until we > have time to investigate the issue? The following patches enables the > package to build successfully: > > --- wxwidgets3.2-3.2.2+dfsg/debian/rules > +++ wxwidgets3.2-3.2.2+dfsg/debian/rules > @@ -9,13 +9,13 @@ > ifneq (,$(filter $(DEB_HOST_ARCH), alpha mips64el riscv64 s390x)) > TEST_FILTER += ~[special-file] > endif > -ifneq (,$(filter $(DEB_HOST_ARCH), hppa mips64el ppc64 s390x sparc64 x32)) > +ifneq (,$(filter $(DEB_HOST_ARCH), hppa mips64el ppc64 riscv64 s390x sparc64 > x32)) > TEST_GUI_FILTER += ~WebView > endif > ifneq (,$(filter $(DEB_HOST_ARCH), i386)) > TEST_GUI_FILTER += ~wxImage::ChangeColours > endif > -ifneq (,$(filter $(DEB_HOST_ARCH), mips64el sparc64)) > +ifneq (,$(filter $(DEB_HOST_ARCH), mips64el riscv64 sparc64)) > TEST_GUI_FILTER += ~wxImage::Paste > endif I don't know the background to these test failures, but extending them for a new arch is clearly reasonable. If this is blocking progress for you please feel free to NMU the change above - otherwise we can include this in the next upload. Cheers, Olly
Bug#1049926: squid: 6.1 autopkgtest failures and FTP support
Forwarded 1049926 https://bugs.squid-cache.org/show_bug.cgi?id=5290 thanks Upstream patch will be included in upcoming 6.2 release.
Bug#1050306: libautobox-junctions-perl: autopkgtest failure with Perl 5.38: Smartmatch is deprecated
Source: libautobox-junctions-perl Version: 0.002-2 Severity: important Tags: trixie sid User: debian-p...@lists.debian.org Usertags: perl-5.38-transition autopkgtest This package fails its autopkgtest checks with Perl 5.38 (currently in experimental.) https://ci.debian.net/data/autopkgtest/unstable/amd64/liba/libautobox-junctions-perl/37060385/log.gz 79s autopkgtest [18:52:20]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps 79s autopkgtest [18:52:20]: test autodep8-perl: [--- 80s 80s # Failed test ' /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 produced no (non-whitelisted) output' 80s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 80s # Structures begin differing at: 80s # $got->[0] = 'Smartmatch is deprecated at (eval 5) line 8. 80s # ' 80s # $expected->[0] = Does not exist 80s 80s # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 produced no (non-whitelisted) output' 80s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 80s # Structures begin differing at: 80s # $got->[0] = 'Smartmatch is deprecated at (eval 5) line 8. 80s # ' 80s # $expected->[0] = Does not exist 80s # Looks like you failed 2 tests of 4. 80s /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 80s 1..4 80s # Smartmatch is deprecated at (eval 5) line 8. 80s # Smartmatch is deprecated at (eval 5) line 15. 80s # Smartmatch is deprecated at (eval 6) line 8. 80s # Smartmatch is deprecated at (eval 6) line 15. 80s # Smartmatch is deprecated at (eval 7) line 8. 80s # Smartmatch is deprecated at (eval 7) line 15. 80s # Smartmatch is deprecated at (eval 8) line 11. 80s # Smartmatch is deprecated at (eval 8) line 21. 80s ok 1 - /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 exited successfully 80s not ok 2 - /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 produced no (non-whitelisted) output 80s # Smartmatch is deprecated at (eval 5) line 8. 80s # Smartmatch is deprecated at (eval 5) line 15. 80s # Smartmatch is deprecated at (eval 6) line 8. 80s # Smartmatch is deprecated at (eval 6) line 15. 80s # Smartmatch is deprecated at (eval 7) line 8. 80s # Smartmatch is deprecated at (eval 7) line 15. 80s # Smartmatch is deprecated at (eval 8) line 11. 80s # Smartmatch is deprecated at (eval 8) line 21. 80s ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 exited successfully 80s not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"autobox::Junctions" -e 1 2>&1 produced no (non-whitelisted) output 80s Dubious, test returned 2 (wstat 512, 0x200) 80s Failed 2/4 subtests -- Niko Tyni nt...@debian.org
Bug#1050305: python3-distutils-extra: DistUtilsExtra.auto fails to determine "requires" from import statements in source code
Package: python3-distutils-extra Version: 2.50 Severity: normal X-Debbugs-Cc: ri...@debian.org Hi, it seems, DistUtilsExtra.auto fails to determine "requires" from import statements in source code. While gTranscribe produces the correct dependencies on 2023-01-05 (https://buildd.debian.org/status/fetch.php?pkg=gtranscribe=all=0.11-1=1672939550=0) it doesn't do that on 2023-08-15 (https://buildd.debian.org/status/fetch.php?pkg=gtranscribe=all=0.11-2=1692119063=0) The only difference between 0.11-1 and 0.11-2 is --- a/debian/clean +++ b/debian/clean @@ -1,2 +1,3 @@ MANIFEST po/gTranscribe.pot +gTranscribe.egg-info/ Building 0.11-1 today on unstable results in missing dependencies as well. Best, Philip -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-2-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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-distutils-extra depends on: ii intltool 0.51.0-6 ii python33.11.4-5+b1 ii python3-distutils 3.11.4-1 ii python3-pkg-resources 68.0.0-2 ii python3-setuptools 68.0.0-2 python3-distutils-extra recommends no packages. Versions of packages python3-distutils-extra suggests: ii devscripts 2.23.5 -- no debconf information
Bug#1050304: dizzy: autopkgtest failure with Perl 5.38: Smartmatch is deprecated
Source: dizzy Version: 0.3-4 Severity: important Tags: trixie sid User: debian-p...@lists.debian.org Usertags: perl-5.38-transition autopkgtest This package fails its autopkgtest checks with Perl 5.38 (currently in experimental.) https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dizzy/37060138/log.gz 78s autopkgtest [18:02:48]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps 78s autopkgtest [18:02:48]: test autodep8-perl: [--- 79s 79s # Failed test ' /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 produced no (non-whitelisted) output' 79s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 79s # Structures begin differing at: 79s # $got->[0] = 'Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 18. 79s # ' 79s # $expected->[0] = Does not exist 79s 79s # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 produced no (non-whitelisted) output' 79s # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. 79s # Structures begin differing at: 79s # $got->[0] = 'Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 18. 79s # ' 79s # $expected->[0] = Does not exist 79s # Looks like you failed 2 tests of 4. 79s /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 79s 1..4 79s # Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 18. 79s # Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 182. 79s ok 1 - /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 exited successfully 79s not ok 2 - /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 produced no (non-whitelisted) output 79s # Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 18. 79s # Smartmatch is deprecated at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 182. 79s ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 exited successfully 79s not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"Dizzy::Core" -e 1 2>&1 produced no (non-whitelisted) output 79s Dubious, test returned 2 (wstat 512, 0x200) 79s Failed 2/4 subtests -- Niko Tyni nt...@debian.org
Bug#1050303: extension no longer works with Gnome 44
Package: workrave-gnome Version: 1.10.51.1-2 Severity: normal Dear Maintainer, After upgrading to gnome-shell 44, the extension no longer works. In the Extensions application, I am unable to activate the extension, and the following message is displayed: Requiring Workrave, version 2.0: Typelib file for namespace 'Workrave', version '2.0' not found Note that this seems to be a different issue than the following upstream one: https://github.com/rcaelers/workrave/issues/487 Thanks for your work, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org
Bug#1050302: libcoin80c v4.0.0+ds-5 makes Freecad crash
Package: libcoin80c Version: 4.0.0+ds-5 Severity: important Dear Maintainer, This is my first bug report and I hope I'm filling it correctly. I'm a french debian testing user (I sticked to bookworm till last week) and I'm facing a problem using FreeCAD which seems related to the libcoin80c package. When opening a file in FreeCAD, the software crashes with an error message : freecad: ./src/glue/gl.cpp:2354: const cc_glglue* cc_glglue_instance(int): Assertion `current_ctx && "Must have a current GL context when instantiating cc_glglue!! (Note: if you are using an old Mesa GL version, set the environment variable COIN_GL_NO_CURRENT_CONTEXT_CHECK to get around what may be a Mesa bug.)"' failed. I used the "COIN_GL_NO_CURRENT_CONTEXT_CHECK=1 freecad" command as advertised, and the software didn't crash. I reverted back to v4.0.0+ds-3 from stable and it didn't crash too. So I'm keeping v4.0.0+ds-3 pinned to have a working software without having to use the command line. I'm not very regular in reading my emails but I will try answering to your questions dilligently. Thanks. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-2-amd64 (SMP w/8 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 libcoin80c depends on: ii libc6 2.37-7 ii libexpat1 2.5.0-2 ii libgcc-s1 13.2.0-2 ii libglx0 1.6.0-1 ii libopengl0 1.6.0-1 ii libstdc++6 13.2.0-2 libcoin80c recommends no packages. Versions of packages libcoin80c suggests: ii libbz2-1.0 1.0.8-5+b1 ii libfreetype6 2.13.0+dfsg-1 pn libopenal0a pn libsimage-dev ii zlib1g 1:1.2.13.dfsg-1 -- no debconf information
Bug#1050300: mkbootimg package missing gki module
Package: mkbootimg Version: 1:34.0.4-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: william.g...@linaro.org Dear Maintainer, When attempting to run /usr/bin/mkbootimg, the following is observed: root@linaro-developer:~# /usr/bin/mkbootimg --help Traceback (most recent call last): File "/usr/bin/mkbootimg", line 31, in from gki.generate_gki_certificate import generate_gki_certificate ModuleNotFoundError: No module named 'gki' This appears to be the result of the gki module missing from the mkbootimg package: https://packages.debian.org/sid/all/mkbootimg/filelist This bug can be resolved by installing the necessary python files (such as generate_fki_certificate.py) located at system/tools/mkbootimg/gki: https://sources.debian.org/src/android-platform-tools/34.0.4-1/system/tools/mkbootimg/gki/ I think the generate_gki_certificate dependency was introduced for the version 33.0.3 release of android-tools, so other Debian versions may be affected as well. Thank you, William Breathitt Gray -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 6.5.0-rc6-qcomlt-arm64-00060-g797651a03cd8 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mkbootimg depends on: ii python3 3.11.4-5+b1 mkbootimg recommends no packages. mkbootimg suggests no packages. -- no debconf information
Bug#1042238: devscripts: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2
Control: tag -1 pending On Wed, Jul 26, 2023 at 10:19:53PM +0200, Lucas Nussbaum wrote: > Source: devscripts > Version: 2.23.5 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230726 ftbfs-trixie > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Undefined subroutine ::to_json called at ./t/salsa.pm line 49. > > # Tests were run but no plan was declared and done_testing() was not seen. > > # Looks like your test exited with 255 just after 1. > > test_comments_in_quoted_strings2 > > t/salsa.t . > > Dubious, test returned 255 (wstat 65280, 0xff00) This regressed with libgitlab-api-v4-perl 0.27-1, which is not migrating to testing because of the same failure on the autopkgtest side. The problem is that t/salsa.pm uses JSON::to_json() without loading the JSON module. This was always wrong, but GitLab::API::v4::RESTClient used to bring it in transitively. That has now changed as libgitlab-api-v4-perl has switched from the JSON module to JSON::MaybeXS. Umh. After patching this and another thing locally I see now that it's also #1041220 / #1038486, which were incorrectly merged resulting in confused metadata that makes it look like it's all a thing of the past. FWIW I think #1041220 should not have been reassigned + merged. It was about libgitlab-api-v4-perl 0.26-3 being seriously buggy because it is out of sync with unstable. When devscripts is fixed, libgitlab-api-v4-perl 0.27-1 will then migrate and #1041220 would have stopped affecting testing without any other action on that bug. But undoing the merge now would probably make things even more confusing. Copying Yadd and Gregor who were involved. It looks like devscripts.git has the necessary patches (including a perltidy fix) but somebody just needs to upload it (and possibly fix the BTS mess afterwards if it becomes a problem.) -- Niko
Bug#1031312: NMU libdisasm 0.23-6.1
I am uploading a NMU to DELAYED/10 in order to fix this. The debdiff is attached.diff -Nru libdisasm-0.23/debian/changelog libdisasm-0.23/debian/changelog --- libdisasm-0.23/debian/changelog 2013-12-14 01:12:35.0 + +++ libdisasm-0.23/debian/changelog 2023-08-22 12:58:10.0 + @@ -1,3 +1,10 @@ +libdisasm (0.23-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop Vcs fields (Closes: #1031312). + + -- Bastian Germann Tue, 22 Aug 2023 12:58:10 + + libdisasm (0.23-6) unstable; urgency=low * control, rules: support autoreconf (Closes: #702262, #727402), thanks diff -Nru libdisasm-0.23/debian/control libdisasm-0.23/debian/control --- libdisasm-0.23/debian/control 2013-12-14 00:33:43.0 + +++ libdisasm-0.23/debian/control 2023-08-22 12:58:10.0 + @@ -4,8 +4,6 @@ Maintainer: Kees Cook Build-Depends: debhelper (>= 9.0~), perl, dh-autoreconf Standards-Version: 3.9.5 -Vcs-Browser: http://bastard.cvs.sourceforge.net/bastard/libdisasm/ -Vcs-Cvs: :pserver:anonym...@bastard.cvs.sourceforge.net:/cvsroot/bastard Homepage: http://bastard.sourceforge.net/libdisasm.html Package: libdisasm-dev
Bug#1007596: NMU libdbd-sybase-perl 1.14-1.1
I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru libdbd-sybase-perl-1.14/Makefile.PL
libdbd-sybase-perl-1.14/Makefile.PL
--- libdbd-sybase-perl-1.14/Makefile.PL 2023-08-22 14:12:05.0 +
+++ libdbd-sybase-perl-1.14/Makefile.PL 2011-04-25 09:00:44.0 +
@@ -57,7 +57,7 @@
(
$^O eq 'VMS'
? ( MAN3PODS => { 'Sybase.pm' => 'blib/man3/DBD_Sybase.3' } )
- : ( MAN3PODS => { 'Sybase.pm' => 'blib/man3/DBD::Sybase.3pm' } )
+ : ( MAN3PODS => { 'Sybase.pm' => 'blib/man3/DBD::Sybase.3' } )
),
(
$] >= 5.005
@@ -132,15 +132,20 @@
$SYBASE .= "/$ENV{SYBASE_OCS}";
}
+ my $libfound = 0;
my $libsub = '';
foreach $libdir ( 'lib', 'lib64' ) {
if ( -d "$SYBASE/$libdir" ) {
if ( checkLib($SYBASE) ) {
+ $libfound = 1;
$libsub = $libdir;
}
}
}
+ die "Can't find any Sybase libraries in $SYBASE/lib or $SYBASE/lib64"
+ unless $libfound;
+
my $inc_found = 0;
if ( -d "$SYBASE/include" && -f "$SYBASE/include/cspublic.h" ) {
++$inc_found;
@@ -332,17 +337,16 @@
last if -e $file;
}
+ open( IN, $file ) || die "Can't open $file: $!";
+ binmode(IN);
my $version;
- if (open(IN, $file)) {
- binmode(IN);
- while() {
- if(/Sybase Client-Library\/([^\/]+)\//) {
- $version = $1;
- last;
- }
+ while () {
+ if (/Sybase Client-Library\/([^\/]+)\//) {
+ $version = $1;
+ last;
}
- close(IN);
}
+ close(IN);
if ( !$version ) {
print "Unknown Client Library version - assuming FreeTDS.\n";
}
diff -Nru libdbd-sybase-perl-1.14/debian/changelog
libdbd-sybase-perl-1.14/debian/changelog
--- libdbd-sybase-perl-1.14/debian/changelog2023-08-22 14:12:05.0
+
+++ libdbd-sybase-perl-1.14/debian/changelog2023-08-22 14:05:19.0
+
@@ -1,3 +1,11 @@
+libdbd-sybase-perl (1.14-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Convert to source format 3.0. Closes: #1007596.
+ * Drop Vcs fields. Closes: #1031984.
+
+ -- Bastian Germann Tue, 22 Aug 2023 14:05:19 +
+
libdbd-sybase-perl (1.14-1) unstable; urgency=low
* New upstream release.
diff -Nru libdbd-sybase-perl-1.14/debian/control
libdbd-sybase-perl-1.14/debian/control
--- libdbd-sybase-perl-1.14/debian/control 2023-08-22 14:12:05.0
+
+++ libdbd-sybase-perl-1.14/debian/control 2023-08-22 14:05:19.0
+
@@ -4,8 +4,6 @@
Build-Depends: debhelper (>= 8.9.8~), perl (>= 5.8.0), freetds-dev (>= 0.63),
libdbi-perl (>= 1.612-1~), dpkg-dev (>= 1.15.7)
Maintainer: Steve Langasek
Standards-Version: 3.9.2
-Vcs-Bzr:
nosmart+http://bzr.debian.org/bzr/users/vorlon/libdbd-sybase-perl/trunk/
-Vcs-Browser:
http://anonscm.debian.org/loggerhead/users/vorlon/libdbd-sybase-perl/trunk/
Package: libdbd-sybase-perl
Architecture: any
diff -Nru libdbd-sybase-perl-1.14/debian/patches/makefile.patch
libdbd-sybase-perl-1.14/debian/patches/makefile.patch
--- libdbd-sybase-perl-1.14/debian/patches/makefile.patch 1970-01-01
00:00:00.0 +
+++ libdbd-sybase-perl-1.14/debian/patches/makefile.patch 2023-08-22
14:05:19.0 +
@@ -0,0 +1,48 @@
+--- libdbd-sybase-perl-1.14.orig/Makefile.PL
libdbd-sybase-perl-1.14/Makefile.PL
+@@ -132,20 +132,15 @@ sub configure {
+ $SYBASE .= "/$ENV{SYBASE_OCS}";
+ }
+
+- my $libfound = 0;
+ my $libsub = '';
+ foreach $libdir ( 'lib', 'lib64' ) {
+ if ( -d "$SYBASE/$libdir" ) {
+ if ( checkLib($SYBASE) ) {
+- $libfound = 1;
+ $libsub = $libdir;
+ }
+ }
+ }
+
+- die "Can't find any Sybase libraries in $SYBASE/lib or $SYBASE/lib64"
+-unless $libfound;
+-
+ my $inc_found = 0;
+ if ( -d "$SYBASE/include" && -f "$SYBASE/include/cspublic.h" ) {
+ ++$inc_found;
+@@ -337,16 +332,17 @@ sub getLibVersion {
+ last if -e $file;
+ }
+
+- open( IN, $file ) || die "Can't open $file: $!";
+- binmode(IN);
+ my $version;
+- while () {
+- if (/Sybase Client-Library\/([^\/]+)\//) {
+- $version = $1;
+- last;
++ if (open(IN, $file)) {
++ binmode(IN);
++ while() {
++ if(/Sybase Client-Library\/([^\/]+)\//) {
++
Bug#1007688: NMU fake 1.1.11-3.1
I am uploading a NMU to DELAYED/10 in order to fix this. The debdiff is attached.diff -Nru fake-1.1.11/debian/changelog fake-1.1.11/debian/changelog --- fake-1.1.11/debian/changelog2023-08-22 16:14:26.0 + +++ fake-1.1.11/debian/changelog2023-08-22 16:02:14.0 + @@ -1,3 +1,14 @@ +fake (1.1.11-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Convert to source format 3.0. (Closes: #1007688) + * Add Homepage. (Closes: #594030) + + [ Helmut Grohne ] + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #915554) + + -- Bastian Germann Tue, 22 Aug 2023 16:02:14 + + fake (1.1.11-3) unstable; urgency=medium * Restrict architecture to linux-any as send-arp uses a linux-specific diff -Nru fake-1.1.11/debian/control fake-1.1.11/debian/control --- fake-1.1.11/debian/control 2023-08-22 16:14:26.0 + +++ fake-1.1.11/debian/control 2023-08-22 16:02:14.0 + @@ -4,6 +4,7 @@ Priority: optional Maintainer: Simon Horman Standards-Version: 3.9.8 +Homepage: https://projects.horms.net/projects/fake/ Package: fake Architecture: linux-any diff -Nru fake-1.1.11/debian/patches/send_arp.patch fake-1.1.11/debian/patches/send_arp.patch --- fake-1.1.11/debian/patches/send_arp.patch 1970-01-01 00:00:00.0 + +++ fake-1.1.11/debian/patches/send_arp.patch 2023-08-22 16:02:14.0 + @@ -0,0 +1,21 @@ +--- fake-1.1.11.orig/send_arp.patch fake-1.1.11/send_arp.patch +@@ -1,7 +1,7 @@ + diff -uN send_arp.orig/Makefile send_arp/Makefile + --- send_arp.orig/MakefileWed Dec 31 19:00:00 1969 + +++ send_arp/Makefile Thu Oct 29 15:40:47 1998 +-@@ -0,0 +1,35 @@ ++@@ -0,0 +1,32 @@ + +## + +# Makefile for send_arp October 1998 + +# horms ho...@vergenet.net +@@ -28,9 +28,6 @@ diff -uN send_arp.orig/Makefile send_arp + + + +all: $(BIN) + + +-+$(BIN): $(SRC) +-+ $(CC) $(SRC) -o $(BIN) +-+ + +clean: + + rm -f $(BIN) core $(SRC).* + + diff -Nru fake-1.1.11/debian/patches/series fake-1.1.11/debian/patches/series --- fake-1.1.11/debian/patches/series 1970-01-01 00:00:00.0 + +++ fake-1.1.11/debian/patches/series 2023-08-22 16:02:14.0 + @@ -0,0 +1 @@ +send_arp.patch diff -Nru fake-1.1.11/debian/rules fake-1.1.11/debian/rules --- fake-1.1.11/debian/rules2023-08-22 16:14:26.0 + +++ fake-1.1.11/debian/rules2023-08-22 16:02:14.0 + @@ -10,7 +10,7 @@ build-indep: build-stamp build-stamp: dh_testdir - $(MAKE) patch all + dh_auto_build -- patch all touch build-stamp clean: diff -Nru fake-1.1.11/debian/source/format fake-1.1.11/debian/source/format --- fake-1.1.11/debian/source/format1970-01-01 00:00:00.0 + +++ fake-1.1.11/debian/source/format2023-08-22 16:02:14.0 + @@ -0,0 +1 @@ +3.0 (quilt) diff -Nru fake-1.1.11/send_arp.patch fake-1.1.11/send_arp.patch --- fake-1.1.11/send_arp.patch 2023-08-22 16:14:26.0 + +++ fake-1.1.11/send_arp.patch 2009-07-08 08:41:46.0 + @@ -1,7 +1,7 @@ diff -uN send_arp.orig/Makefile send_arp/Makefile --- send_arp.orig/Makefile Wed Dec 31 19:00:00 1969 +++ send_arp/Makefile Thu Oct 29 15:40:47 1998 -@@ -0,0 +1,32 @@ +@@ -0,0 +1,35 @@ +## +# Makefile for send_arp October 1998 +# horms ho...@vergenet.net @@ -28,6 +28,9 @@ + +all: $(BIN) + ++$(BIN): $(SRC) ++ $(CC) $(SRC) -o $(BIN) ++ +clean: + rm -f $(BIN) core $(SRC).* +
Bug#1050299: rust-webpki: RUSTSEC-2023-0052
Source: rust-webpki Version: 0.22.0-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi Please see https://rustsec.org/advisories/RUSTSEC-2023-0052.html . FWIW, there is a fix in the rustls-webpki is a fork, which is actively maintained. Should rust-webpki be removed from Debian testing and unstable? Regards, Salvatore
Bug#1050298: rust-rustls-webpki: RUSTSEC-2023-0053
Source: rust-rustls-webpki Version: 0.101.3-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi Please see https://rustsec.org/advisories/RUSTSEC-2023-0053.html . Regards, Salvatore
Bug#1050294: grep: Fails to build twice
El 22/08/23 a las 19:36, Bas Couwenberg escribió: > Source: grep > Version: 3.11-2 > Severity: important > Tags: upstream patch > > Dear Maintainer, > > Builing your package twice reveals an issue with the clean target: > > dpkg-source: info: local changes detected, the modified files are: > source_dir/doc/grep.info > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/grep_3.11-2+salsaci+20230822+19.diff.kbSnU8 > > The attached patch resolves the issue. Thank you! You were faster than me :-) I've pushed this MR: https://salsa.debian.org/debian/grep/-/merge_requests/11 and the test you create just passed. I'll merge and upload the package after sending this mail. Thanks again, -- S signature.asc Description: PGP signature
Bug#1050296: rust-rustls needs a source-only upload
Package: rust-rustls Version: 0.21.6-3 The most recent upload of rust-rustls included a binary package and hence cannot migrate to testing. Since the package is arch all this cannot be fixed with a binnmu. Please make a new source-only upload so the package can migrate.
Bug#1050295: libqglviewer: Qt6 version?
Source: libqglviewer Severity: wishlist Dear Maintainer, it seems that upstream supports Qt6, at least I see commits like "Fix build with Qt6 on Linux". When you upgrade to version 2.9.1 or newer (we are currently at 2.8.0), could you also create Qt6 packages, not just Qt5? -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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
Bug#1040837: rust-log situation update.
On 22/08/2023 04:47, Peter Green wrote: Fabian: is sval-serde ready for sponsorship? if so can you add the RFS file? I couldn't see anything wrong with the sval-serde package, so I decided to go ahead and upload it, it is now in NEW.
Bug#1050294: grep: Fails to build twice
Source: grep Version: 3.11-2 Severity: important Tags: upstream patch Dear Maintainer, Builing your package twice reveals an issue with the clean target: dpkg-source: info: local changes detected, the modified files are: source_dir/doc/grep.info dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/grep_3.11-2+salsaci+20230822+19.diff.kbSnU8 The attached patch resolves the issue. Kind Regards, Bas diff -Nru grep-3.11/debian/changelog grep-3.11/debian/changelog --- grep-3.11/debian/changelog 2023-07-21 23:33:27.0 +0200 +++ grep-3.11/debian/changelog 2023-08-22 19:24:15.0 +0200 @@ -1,3 +1,10 @@ +grep (3.11-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to remove generated files in clean target. + + -- Bas Couwenberg Tue, 22 Aug 2023 19:24:15 +0200 + grep (3.11-2) unstable; urgency=low * Add d/patches/grep-dirfd.patch to fix gnulib bug that produces an diff -Nru grep-3.11/debian/patches/clean.patch grep-3.11/debian/patches/clean.patch --- grep-3.11/debian/patches/clean.patch1970-01-01 01:00:00.0 +0100 +++ grep-3.11/debian/patches/clean.patch2023-08-22 19:24:12.0 +0200 @@ -0,0 +1,14 @@ +Description: Remove generated files in clean target. +Author: Bas Couwenberg + +--- a/doc/Makefile.am b/doc/Makefile.am +@@ -22,7 +22,7 @@ grep_TEXINFOS = fdl.texi + man_MANS = grep.1 + + EXTRA_DIST = grep.in.1 +-CLEANFILES = grep.1 ++CLEANFILES = grep.1 grep.info + + grep.1: grep.in.1 + $(AM_V_GEN)rm -f $@-t $@ diff -Nru grep-3.11/debian/patches/series grep-3.11/debian/patches/series --- grep-3.11/debian/patches/series 2023-07-21 22:33:01.0 +0200 +++ grep-3.11/debian/patches/series 2023-08-22 19:21:45.0 +0200 @@ -4,3 +4,4 @@ 05-grep-wrapper-sh.patch 1019724-handle-backslash-warning.patch grep-dirfd.patch +clean.patch
Bug#1050293: pipewire-bin: please simplify adding custom profile-set
Package: pipewire-bin Version: 0.3.77-1 Severity: wishlist Tags: patch upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it is sometimes useful to be able to add a custom profile-set. For that, it is nessesary to store it into e.g. a new file, say `/usr/share/alsa-card-profile/mixer/profile-sets/-custom.conf` and append `.include -custom.conf` at the end of `/usr/share/alsa-card-profile/mixer/profile-sets/default.conf`. But that change gets overriden when the package is updated, which could be *exremely* dangerous, e.g. if said profile changed the `volume-limit`. It would be good if the package could ship an empty `profile-sets/-custom.conf` file, and the appropriate change to the `profile-sets/default.conf`. Then one could use `dpkg-divert` on `-custom.conf to avoid profile loss on update. Thank you! Roman. - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire-bin depends on: ii libasound2 1.2.9-1 ii libc62.37-7 ii libdbus-1-3 1.14.8-2 ii libncursesw6 6.4+20230625-2 ii libpipewire-0.3-00.3.77-1 ii libpipewire-0.3-modules 0.3.77-1 ii libreadline8 8.2-1.3 ii libsndfile1 1.2.0-1 ii libtinfo66.4+20230625-2 Versions of packages pipewire-bin recommends: ii dbus-user-session 1.14.8-2 pn rtkit ii wireplumber0.4.14-4 pipewire-bin suggests no packages. - -- no debconf information - -- debsums errors found: debsums: changed file /usr/share/alsa-card-profile/mixer/profile-sets/default.conf (from pipewire-bin package) -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+UikBxeiu50LOdFYgbqkFMWfZdAFAmTk7y0ACgkQgbqkFMWf ZdB96Q/+L2vh7I4tRpR54vGKGE96zAYJzBD6YbBDplOiEcBVX54EurS2TNPaIQHI vvRg0+Y8HQ2KPAYTpiUndmepQA9WZ/7kEaH/la9J7gjA2wJHPhCPa+c3PicpAqua 9KuYY5FIMPyaP5AKS5RnCI5RKPBndNPyVoM+iARZMvv9II2r+YTLYKybapb3NvfJ Fy/4NMPivl149CGmkVB17+ikOTVZErFFwrX5cHpaMNiZHfmb4WX7isHfX91NMXt+ BeOZL5MhydTF6TkdDWPSTp4/QmB8Z8tTRLTiRSVDm1UfaUIHcfF+F9aCVryS9Lte yl0+h/vf6p4KbV1zwfbuqwqNU9JCK3wx41s/+iraiCoHNzUEDBEOb2Cb9Xkekxh/ 9DjuyHQrAQyVlqEWKAwGur3lX2b8yHPkgrEwFXXacJ9wJO8OkW4eXcTQbEvNf43g P5Sbxlp7pQq1nRqAxolzT7XghnNTl1nk1Ipzz70InNOQrUM3vSheIcc4t1g0i8r6 iWlAZhIj/wK93jghqLwjRUFOwnst8GZ1wTPtiyZjEtH1WFnPI7oi+r61xTYYtQb3 cfbUuA4enZnh/E5odqJyLa2V/awbWd4tfR9nC6k05/Vjm/phxRgeTVuAO16akNyf QdLKGH07gRx1JgYSCjhsg003u4syllRO7qWru993n887alhQhCI= =qs+F -END PGP SIGNATURE-
Bug#1050292: partitioning a btrfs partition into btrfs sub-volumes
Package: calamares Version: 3.2.61-1+b1 Hello, dear maintainers! I raised this issue in the calamares upstream. The lack of partitioning of the btrfs partition into sub-volumes concerns not only debian, but also other distributions using calamares. https://github.com/calamares/calamares/issues/2130
Bug#1050173: setting a zero password per user during installation
On Mon, 21 Aug 2023 15:02:39 +0300 Nikolay Sabelnikov <79625490...@yandex.ru> wrote: > Package: calamaris > Version: 3.2.61-1+b1 > > during installation, I noticed that it is impossible to set a null password > for the user. > > > sorry I sent it to the wrong package. You can close the bug.
Bug#1050291: the ability to set a zero password for the user
Package: Calamares Version: 3.2.61-1+b1 Hello. Dear maintainers! please add the possibility of creating a user without a password or a null password.
Bug#1050223: RM: r-cran-rgdal/1.6-7+dfsg-1
Control: tags -1 moreinfo Hi Andreas, On 22-08-2023 12:08, Andreas Tille wrote: as per upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049438#31 rgdal will run out of upstream support soon. Since the package created failures with newer upstream versions of other packages (see bug #1049438) it should be removed from testing. Two questions/remarks: 1) why only testing, doesn't it make more sense to remove it from unstable (hint: reassign to ftp.debian.org) If you only need it from testing, reopening 1049438 is a reasonably fast way to achieve that. 2) as you mentioned in 1049438, the reverse (test) depends should be fixed first. Please remove the moreinfo tag once that has happened. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1042714: closed by Debian FTP Masters (reply to Chris Hofstaedtler ) (Bug#1042714: fixed in util-linux 2.39.2-1)
On Sun, 20 Aug 2023 21:15:03 + Debian Bug Tracking System wrote: [...] > * libmount: Fix regression when mounting with atime (Closes: #1042714) [...] I've just checked libmount1/2.39.2-1 (from unstable) and I can confirm that the regression has been fixed. Thanks to all the people involved with the resolution of this issue! :-) Now, it would be great, if this version (2.39.2-1) could migrate to testing soon... Bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpOT_ijcOFTM.pgp Description: PGP signature
Bug#999936: uwsgi: depends on obsolete pcre3 library
On Tue, 22 Aug 2023 11:08:13 +0200 "Michael R. Crusoe" wrote: > And the QA excuses page[2] gives good news: > > Migration status for uwsgi (2.0.21-5.1 to 2.0.22-1): Will attempt > migration (Any information below is purely informational) AFAIS uwsgi has migrated, thanks! Cheers Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
Bug#375824: closed by Andreas Metzler (Re: Bug#375824: netpbm: pgmtopbm -threshold -value 160 -> usage message)
That's great, thanks -- Silas S. Brown http://ssb22.user.srcf.net Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#1041652: udev: Udev database attached to udev reportbug might contain sensitive information
On Tue, 22 Aug 2023 17:11:29 +0200 Michael Biebl wrote: > I posted a MR here > https://salsa.debian.org/systemd-team/systemd/-/merge_requests/207 > > The default is to include the information. If you have suggestions to > the wording, please follow-up in the MR. Hi Michael, thanks for your kind reply. The MR looks good to me. -- Michael Büsch https://bues.ch/ pgpkgPjlBaFtI.pgp Description: OpenPGP digital signature
Bug#1050117: /usr/share/bug/linux-image-6.4.0-0.deb12.2-686-pae-unsigned/include-1cmdline: poweroff (shutdown -h) / reboot (shutdown -r) does not work properly.
Control: found -1 6.1.27-1 Control: found -1 6.4.4-3 Control: retitle -1 poweroff (shutdown -h) / reboot (shutdown -r) does not work properly since 6.1.27-1 On Tuesday, 22 August 2023 08:25:18 CEST Takashi Yano wrote: > On Tue, 22 Aug 2023 08:31:34 +0900 > > Takashi Yano wrote: > > I have tried another kernel: > > linux-image-6.1.0-0.deb11.9-686-pae-unsigned 6.1.27-1~bpo11+1 : NG > > > > It seems that the recent (in a few months) change in the kernel causes > > this issue. I've updated the metadata accordingly. I've used the non-bpo versions as I don't know how the BTS deals with bpo11/bpo12 mixes. > I have narrowed down the code change which causes the issue > by building kernel locally again and again. > > The issue happens after the chage: > > linux (6.1.25-1) unstable; urgency=medium > - ALSA: ymfpci: Create card with device-managed snd_devm_card_new() > > diff --git a/linux-source-6.1/sound/pci/ymfpci/ymfpci.c > b/linux-source-6.1/sound/pci/ymfpci/ymfpci.c index 1e198e4..82d4e0f 100644 > --- a/linux-source-6.1/sound/pci/ymfpci/ymfpci.c > +++ b/linux-source-6.1/sound/pci/ymfpci/ymfpci.c > @@ -170,7 +170,7 @@ static int snd_card_ymfpci_probe(struct pci_dev *pci, > return -ENOENT; > } > > - err = snd_card_new(>dev, index[dev], id[dev], THIS_MODULE, > + err = snd_devm_card_new(>dev, index[dev], id[dev], THIS_MODULE, > sizeof(*chip), ); > if (err < 0) > return err; This is great! In the linux-6.1.y branch that change is from commit db7d7782677ff998c06997903d5400a0ba91cebb and supposedly discussed in https://lore.kernel.org/r/20230329032422.170024-1-ta...@tasossah.com but that URL doesn't seem to work. https://lore.kernel.org/all/20230403140418.679274...@linuxfoundation.org/ does though and at the bottom of that page you'll find instructions on how to reply (to all!) to that message, which includes the original author of the patch. So my recommendation is to follow the instructions and reply to that msg. > I also noticed that the following error occurred in the boot process > with this change. > > [ 24.101852] snd_ymfpci :00:0e.0: firmware: failed to load > yamaha/ds1_dsp.fw (-2) [ 24.101931] firmware_class: See > https://wiki.debian.org/Firmware for information about missing firmware [ > 24.102001] snd_ymfpci :00:0e.0: firmware: failed to load > yamaha/ds1_dsp.fw (-2) [ 24.102031] snd_ymfpci :00:0e.0: Direct > firmware load for yamaha/ds1_dsp.fw failed with error -2 [ 24.102049] > snd_ymfpci :00:0e.0: firmware request failed: -2 [ 24.102077] > snd_ymfpci: probe of :00:0e.0 failed with error -2 [ 24.102435] BUG: > unable to handle page fault for address: f0da8084 [ 24.102465] #PF: > supervisor write access in kernel mode > [ 24.102486] #PF: error_code(0x0002) - not-present page > [ 24.102507] *pdpt = 06bd0001 *pde = 0237a067 *pte = > [ 24.102544] Oops: 0002 [#1] PREEMPT SMP PTI > [ 24.102568] CPU: 0 PID: 247 Comm: (udev-worker) Not tainted 6.1.27 #3 > [ 24.102594] Hardware name: MICRO-STAR INTERNATIONAL CO., LTD > MS-6163/MS-6163 (i440BX), BIOS 4.51 PG 08/22/00 [ 24.102623] EIP: > snd_ymfpci_free+0x1b/0x130 [snd_ymfpci] > [ 24.102684] Code: b8 01 00 00 00 5b 5e 5f 5d c3 8d 74 26 00 90 3e 8d 74 > 26 00 55 89 e5 56 53 8b 98 88 01 00 00 8b 43 10 8d 90 84 00 00 00 31 c0 > <89> 02 8b 73 10 89 86 b0 00 00 00 8b 4b 10 89 81 80 00 00 00 b9 ff > [ 24.102730] EAX: EBX: c4d0a610 ECX: 0005f320 EDX: f0da8084 > [ 24.102754] ESI: c4d0a018 EDI: cfcd780c EBP: c792fc44 ESP: c792fc3c > [ 24.102778] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00210246 > [ 24.102803] CR0: 80050033 CR2: f0da8084 CR3: 06bc8000 CR4: 06f0 [ > 24.102828] Call Trace: > [ 24.102853] release_card_device+0x47/0x90 [snd] > [ 24.102911] device_release+0x30/0x90 > [ 24.102953] kobject_put+0x99/0x1d0 > [ 24.102987] put_device+0x11/0x20 > [ 24.103009] __snd_card_release+0x71/0x80 [snd] > [ 24.103043] release_nodes+0x43/0xb0 > [ 24.103068] devres_release_all+0x79/0xb0 > [ 24.103094] device_unbind_cleanup+0x10/0x60 > [ 24.103125] really_probe+0x1f6/0x340 > [ 24.103150] __driver_probe_device+0x75/0x100 > [ 24.103175] driver_probe_device+0x1f/0x90 > [ 24.103199] __driver_attach+0xcf/0x1b0 > [ 24.103223] ? __device_attach_driver+0x100/0x100 > [ 24.103248] bus_for_each_dev+0x5b/0xa0 > [ 24.103272] driver_attach+0x19/0x20 > [ 24.103293] ? __device_attach_driver+0x100/0x100 > [ 24.103317] bus_add_driver+0x17f/0x1e0 > [ 24.103340] driver_register+0x79/0xd0 > [ 24.103364] ? 0xf0d3a000 > [ 24.103383] __pci_register_driver+0x42/0x50 > [ 24.103421] ymfpci_driver_init+0x1c/0x1000 [snd_ymfpci] > [ 24.103458] do_one_initcall+0x41/0x1e0 > [ 24.103482] ? kvfree+0x25/0x30 > [ 24.103518] ? __kmem_cache_alloc_node+0x24d/0x350 > [ 24.103546] ? kmalloc_trace+0x22/0x90 > [ 24.103581] ?
Bug#1050290: glibc: Harmless bug in tcsetattr() handling of CREAD, CSIZE, PARENB bits
Source: glibc
Severity: minor
Dear Maintainer,
I believe that the "any/local-tcsetaddr.diff" (sic) patch applied to the glibc
sources contains a probably unmanifestible bug in the checking of c_cflag
changes other than the PARENB, CREAD, and CSIZE bits here:
+ else if ((k_termios_old.c_cflag | (PARENB & CREAD & CSIZE)) !=
+ (k_termios.c_cflag | (PARENB & CREAD & CSIZE)))
+ {
+ /* Some other c_cflag setting was successfully changed, which
+means we should not return an error. */
+ __set_errno (save);
+ retval = 0;
+ }
I believe the (PARENB & CREAD & CSIZE) subexpressions (which evaluate to 0)
should be (PARENB | CREAD | CSIZE).
This bug should be harmless as long as the TTY device either handles changes to
the PARENB, CREAD, and CSIZE settings, or always sets them to consistently
fixed values.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (920, 'testing'), (910, 'unstable'), (820, 'testing'), (810,
'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-debug'), (500, 'unstable'), (500, 'stable'), (120, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 6.4.0-2-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#1050289: Predicatble temporary directory and file names and insufficient error checking
Package: sitesummary Version: 0.1.54 sitesummary-client runs during boot and via cronjob with superuser privileges. It creates both a directory with a predictable naming scheme: /tmp/sitesummary-. Due to insufficient error checking a user can pre-create directories which then will prevent its creation and prevent the script from changing the current working directory before creating lots of temporary files. In case of a cronjob the current working directory will be /root and during boot it will be /. Thus during boot a tar file of the root directory will be created on /tmp which may fill up the /tmp or root partition depending on disk size and partition scheme. Furthermore, the script will create the tar file following the same naming scheme /tmp/sitesummary-.tar.gz which in the absence of kernel symlink protection allows for symlink attacks. -- Guido Berhoerster
Bug#934463: initscripts: consider taking over hwclock policy machinery
Andreas and Chris,
Thanks for your input.
On Tue, Aug 22, 2023 at 12:55:41PM +0200, Andreas Henriksson wrote:
> HEADS UP: One thought here is that the init script will still need the
> actual hwclock binary. While util-linux-extra currently is
> pseudo-essential I think zeha plans to make it a regular package at some
> point in the future which probably mean you want initscripts to depend
> on it (or make the scripts handle that hwclock binary is not available,
> but that sounds less compelling to me). You might want to add the
> dependency now so that it's not forgotten once util-linux-extra is no
> longer pseudo-essential.
Dependency added.
> (I'd be happy if I could see the actual diff, but could not spot a
> relevant branch on salsa/debian/sysvinit.)
I have just pushed wip/hwclock_takeover. The diff is also attached.
(I am aware that the initscripts packaging doesn't make use of many recent
debhelper conveniences. However, I am reluctant to make changes to that at the
same time as handling this sort of transition).
> Feel free to push a branch to salsa.debian.org/debian/util-linux with
> proposed changes if you do prepare them.
I have pushed branch leepen/hwclock_initscripts_migration for review and
comment.
> > If util-linux-extra were to use it, my understanding is that rm_conffile
> > only
> > removes *unmodified* conffiles so user modifications should be preserved.
Testing this has been contrary to my expectation so far: both rm_conffile and
remove-on-upgrade only preserve user modifications to conffiles only to the
extent that they are renamed with either .dpkg-bak or .dpkg-old
appended. However, that doesn't facilitate those modifications being preserved
in the new initscript-owned conffile. Therefore, I think any active removal of
these conffiles as obsolete in util-linux-extra should wait until Forky+1, by
which time we can be sure that initscripts will have inherited the
conffiles. Are you OK with that? Or do either of you have a better solution?
> PS. I'd be happy to discuss potential improvements that can be done, but
> think the first step should only be to get the files moved over. One
> step at a time. Just don't want to leave you with the impression that
> I/we are just dumping all the burden on you for old sins. For example
> the hwclock(5) manpage probably contains questionable information.
Thanks. As you say, for the future...
Best wishes
Mark
diff --git a/debian/control b/debian/control
index e3b9c91c..fca27272 100644
--- a/debian/control
+++ b/debian/control
@@ -99,7 +99,10 @@ Multi-Arch: foreign
Depends:
sysvinit-utils (>= 3.05-1),
sysv-rc | file-rc | openrc,
+ util-linux-extra,
${misc:Depends},
+Breaks: util-linux-extra (<< 2.39.2-1.1~)
+Replaces: util-linux-extra (<< 2.39.2-1.1~)
Recommends:
e2fsprogs,
psmisc,
diff --git a/debian/initscripts.postinst b/debian/initscripts.postinst
index 32c0afb0..bf841c82 100755
--- a/debian/initscripts.postinst
+++ b/debian/initscripts.postinst
@@ -24,7 +24,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
- bootlogs rc.local rmnologin"
+ bootlogs rc.local rmnologin hwclock.sh"
for F in $INITSCRIPTS; do
if [ -x /etc/init.d/$F ]; then
diff --git a/debian/initscripts.postrm b/debian/initscripts.postrm
index 5e232568..ac314bed 100755
--- a/debian/initscripts.postrm
+++ b/debian/initscripts.postrm
@@ -9,7 +9,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
- bootlogs rc.local rmnologin"
+ bootlogs rc.local rmnologin hwclock.sh"
case "$1" in
purge)
diff --git a/debian/src/initscripts/Makefile b/debian/src/initscripts/Makefile
index b13eafa3..db50873c 100644
--- a/debian/src/initscripts/Makefile
+++ b/debian/src/initscripts/Makefile
@@ -34,6 +34,9 @@ install:
$(INSTALL) -d $(DESTDIR)$(sbindir)/.
$(INSTALL) sbin/fsck.nfs $(DESTDIR)$(sbindir)/fsck.nfs
+ $(INSTALL) -Dt $(DESTDIR)/usr/lib/udev/rules.d usr/lib/udev/rules.d/hwclock.rules
+ $(INSTALL) usr/lib/udev/hwclock-set $(DESTDIR)/usr/lib/udev/hwclock-set
+
$(INSTALL) -d $(DESTDIR)/usr/share/man/man8
$(INSTALL_DATA) man/fsck.nfs.8 \
$(DESTDIR)/usr/share/man/man8/fsck.nfs.8
diff --git a/debian/src/initscripts/etc/default/hwclock b/debian/src/initscripts/etc/default/hwclock
new file mode 100644
index ..44b04312
--- /dev/null
+++ b/debian/src/initscripts/etc/default/hwclock
@@ -0,0 +1,2 @@
+# Settings for the hwclock init script.
+# See hwclock(5) for supported settings.
diff --git a/debian/src/initscripts/etc/init.d/hwclock.sh
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
Package: nsis Version: 3.08-3 Severity: important makensis 3.08-3 on bookworm creates installers with a non-empty relocation section which contains garbage. The installers work, but trigger false positive warnings from security scanners, likely due to exe file corruption. Testcase: $ dpkg --list nsis nsis-common ... ii nsis 3.08-3 amd64 ... ii nsis-common 3.08-3 all ... $ cat test.nsi Section "Empty" SectionEnd $ makensis test.nsi ... $ objdump -p test.exe >/dev/null objdump: error: test.exe(.reloc) is too large (0x8e4 bytes) $ objdump -p test.exe 2>/dev/null ... Entry 5 00047000 08e4 Base Relocation Directory [.reloc] ... $ objdump -p /usr/share/nsis/Stubs/zlib-x86-unicode ... Entry 5 00047000 08e4 Base Relocation Directory [.reloc] ... PE File Base Relocations (interpreted .reloc section contents) Virtual Address: 1000 Chunk size 196 (0xc4) Number of fixups 94 reloc 0 offset 2b [102b] HIGHLOW reloc 1 offset 40 [1040] HIGHLOW ... Virtual Address: c000 Chunk size 216 (0xd8) Number of fixups 104 reloc 1 offset 8 [c008] HIGHLOW reloc 2 offset c [c00c] HIGHLOW ... reloc 102 offset 8f8 [c8f8] HIGHLOW reloc 103 offset 8fc [c8fc] HIGHLOW All the stubs apparently have a non-empty relocation section with garbage. This is not the case for the stubs from nsis-common-3.06.1-1 (bullseye) and nsis-common-3.09-1 (sid). This is also not the case with the upstream 3.08 and 3.09 builds for windows which are available at https://sourceforge.net/projects/nsis/files/NSIS%203/ Related: https://sourceforge.net/p/nsis/bugs/1299/ -- Regards Christian Franke smartmontools.org
Bug#1041652: udev: Udev database attached to udev reportbug might contain sensitive information
On Fri, 21 Jul 2023 19:31:14 +0200 =?utf-8?q?Michael_B=C3=BCsch?= wrote: Package: udev Version: 254~rc2-3 Severity: normal X-Debbugs-Cc: m...@bues.ch Dear Maintainer, when reporting a udev bug via reportbug the tool auto-attaches the complete udev database dump to the report. That came as a complete surprise to be. I didn't see any mention of that in the report process. Nor was there a way to prevent the attachment. I think auto-attaching the complete udev database is a confidentiality problem. The udev database might contain sensitive information that the reporter did not want to disclose to the public internet. Think of Luks DM names for example. The reporter is free to choose any name for them. The reporter might not have thought about that the name can end up being posted to the public internet when the reporter choose a name for the DM device. Besides that, the udev database is a very large fingerprint of the hardware that the user uses. By posting the udev database to the public internet, that hardware is permanently associated to the reporter's name. That may be a problem. Think of illegal things being done with the hardware after the original reporter sold the hardware to somebody else. Please also keep in mind that not all Debian users live in free countries with free speech. Associating hardware to people might be a major threat to people in such countries. Think of plausible deniability of ownership, for example. Therefore, my suggestion is: - Please make the posting of the udev database optional. - Also, please make it obvious that the complete database is posted during the process, if the option is chosen. And explain to the reporter what that database contains. I posted a MR here https://salsa.debian.org/systemd-team/systemd/-/merge_requests/207 The default is to include the information. If you have suggestions to the wording, please follow-up in the MR. Regards, Michael OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050287: additional information
cat /var/lib/dkms/r8168/8.051.02/build/make.log DKMS make.log for r8168-8.051.02 for kernel 6.4.0-3-amd64 (x86_64) mar 22 ago 2023 09:31:54 EST make: se entra en el directorio '/usr/src/linux-headers-6.4.0-3-amd64' CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_n.o CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_asf.o CC [M] /var/lib/dkms/r8168/8.051.02/build/rtl_eeprom.o CC [M] /var/lib/dkms/r8168/8.051.02/build/rtltool.o /var/lib/dkms/r8168/8.051.02/build/r8168_n.c: In function ‘r8168_csum_workaround’: /var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29212:24: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’? [-Werror=implicit-function-declaration] 29212 | segs = skb_gso_segment(skb, features); | ^~~ | skb_gso_reset /var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29212:22: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 29212 | segs = skb_gso_segment(skb, features); | ^ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.4.0-3-common/scripts/Makefile.build:257: /var/lib/dkms/r8168/8.051.02/build/r8168_n.o] Error 1 make: *** [/usr/src/linux-headers-6.4.0-3-common/Makefile:2057: /var/lib/dkms/r8168/8.051.02/build] Error 2 make: se sale del directorio '/usr/src/linux-headers-6.4.0-3-amd64' -- Julio Mendoza Tel. Of. 507.391.41.38 Cel. 507.6672.2384 Oficina 4-9, Edificio Providence Plaza Brisas del Golf, Panamá, Rep. de Panamá. Ubicación en Mapa: https://goo.gl/hSvy40 https://eemsystems.com https://telegram.me/JulioMendoza "Cualquier tecnología suficientemente avanzada es indistinguible de la magia". Arthur C. Clarke
Bug#1050208: libc6: double free detected in tcache 2, then abort
control: reassign -1 openbsd-inetd
control: retitle -1 openbsd-inetd: double free detected in tcache 2, then abort
control: found -1 openbsd-inetd/0.20221205-1
Hi,
On 2023-08-22 14:32, Paul Szabo wrote:
> Package: libc6
> Version: 2.36-9+deb12u1
> Severity: important
>
> Dear Maintainer,
>
> I noticed an issue with malloc() or free(). I only noticed this
> recently, with libc6 version 2.36-9+deb12u1; reverting to previous
> 2.36-9 did not seem to help.
>
> The issue: sending SIGHUP to the inetd process (from package
> openbsd-inetd version 0.20221205-1) should cause it to re-load its
> configuration, but instead it elicits
>
> free(): double free detected in tcache 2
>
> and an abort. This is easiest seen (after "systemctl stop inetd") with
>
> root# inetd -d -i & sleep 1; kill -HUP $!; sleep 1; jobs
> [1] 2431
> ADD: ident proto=tcp4, wait.max=1.256 user:group=identd:(default) builtin=0
> server=/usr/sbin/identd
> free(): double free detected in tcache 2
> [1]+ Aborted inetd -d -i
> root#
>
> I believe that this "double free" is spurious, as there are no errors
> (but inetd reloads as expected) when using e.g.
It is not, it is also reported by valgrind:
==9356== Invalid free() / delete / delete[] / realloc()
==9356==at 0x484317B: free (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==9356==by 0x10DB69: getconfigent (inetd.c:1176)
==9356==by 0x10EFFE: config (inetd.c:651)
==9356==by 0x48A0401: event_signal_closure (event.c:1369)
==9356==by 0x48A0401: event_process_active_single_queue (event.c:1678)
==9356==by 0x48A0C1E: event_process_active (event.c:1783)
==9356==by 0x48A0C1E: event_base_loop (event.c:2006)
==9356==by 0x10B9E2: main (inetd.c:475)
==9356== Address 0x50747e0 is 0 bytes inside a block of size 1 free'd
==9356==at 0x484317B: free (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==9356==by 0x10DB69: getconfigent (inetd.c:1176)
==9356==by 0x10EFFE: config (inetd.c:651)
==9356==by 0x10B8C3: main (inetd.c:438)
==9356== Block was alloc'd at
==9356==at 0x48407B4: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==9356==by 0x4A82539: strdup (strdup.c:42)
==9356==by 0x10DBE7: newstr (inetd.c:1597)
==9356==by 0x10DBE7: getconfigent (inetd.c:1186)
==9356==by 0x10EFFE: config (inetd.c:651)
==9356==by 0x10B8C3: main (inetd.c:438)
It appears that is has been introduced in the latest upload of
openbsd-inetd in the default_v4v6 patch. The following patch seems to
fix the issue, but I haven't spent time to verify it is correct:
--- openbsd-inetd-0.20221205.orig/inetd.c
+++ openbsd-inetd-0.20221205/inetd.c
@@ -1172,8 +1172,10 @@ more:
cp = saved_cp;
saved_cp = NULL;
} else {
- if (saved_cp)
+ if (saved_cp) {
free(saved_cp);
+ saved_cp = NULL;
+ }
while ((cp = nextline(fconfig)) && *cp == '#')
;
I am therefore reassigning the bug to openbsd-inetd.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
Bug#1049999: vagrant: the future of packaging vagrant in Debian
On Sat, Aug 19, 2023 at 06:46:06AM +0200, Lucas Nussbaum wrote: > Hi, > > This license change is so disappointing... > > On 18/08/23 at 08:07 -0300, Antonio Terceiro wrote: > > > Plan B. > > > > > > - Drop vagrant because of that changed licence and no need to > > > keep older vagrant. > > > - No vagrant avaiable in Debian. Just use upstream's package. > > > > I think keeping a stale version of vagrant in the archive is worse than > > telling people to just use upstream packages. > > A follow-up question, especially in the case of Plan B, is: what do we > do about Debian Vagrant images provided on Vagrant Cloud > (https://app.vagrantup.com/debian/) ? > > A/ continue to maintain them. But as the main uploader of those images >in the recent times, I might not continue to maintain them, especially >if I move to another tool for my own uses, so we might need to look >for other volunteers. > B/ stop maintaining them >B.1/ ... and remove existing images from the 'debian' Vagrant Cloud >account >B.2/ ... and leave the 'debian' Vagrant Cloud account as it is >currently > > I don't think B.2 is a good idea. I agree. Just as we provide cloud images for proprietary platforms, I think we as a project want to control what is available as "Debian" for Vagrant users, just like we do with images targetted at proprietary cloud platforms. > > Hopefully, being burned a second time will teach me to not put my > > volunteer time in non-copyleft packages provided by a single > > corporation. > > Note that the fact that Vagrant was using a non-copyleft license is not > entirely relevant. The same relicensing could be achieved by > organizations using a copyleft licence with a copyright transfer > agreement for external contributions. (I suspect that this is how it was > achieved for other Hashicorp products, but I haven't checked). Yes, that's true. signature.asc Description: PGP signature
Bug#1050287: r8168-dkms: can't compile in kernel 6.4.0-3-amd64
Package: r8168-dkms Version: 8.051.02-3 Severity: important Dear Maintainer, *** 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: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_PA.UTF-8, LC_CTYPE=es_PA.UTF-8 (charmap=UTF-8), LANGUAGE=es_PA:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages r8168-dkms depends on: ii dkms 3.0.11-3 r8168-dkms recommends no packages. r8168-dkms suggests no packages. -- no debconf information
Bug#1050285: python3-defaults: SSLEOFError when running cheroot application
Package: python3-defaults Version: 3.11.2-1 Severity: important Dear Maintainer, We are running salt-master on bookworm, using salt-api module. Occasionally it errors out with the following exception: ``` ENGINE socket.error 8 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cheroot/server.py", line 1287, in communicate req.respond() File "/usr/lib/python3/dist-packages/cheroot/server.py", line 1077, in respond self.server.gateway(self).respond() File "/usr/lib/python3/dist-packages/cheroot/wsgi.py", line 139, in respond self.write(chunk) File "/usr/lib/python3/dist-packages/cheroot/wsgi.py", line 221, in write self.req.write(chunk) File "/usr/lib/python3/dist-packages/cheroot/server.py", line 1133, in write self.conn.wfile.write(chunk) File "/usr/lib/python3/dist-packages/cheroot/makefile.py", line 68, in write res = super().write(val, *args, **kwargs) ^^^ File "/usr/lib/python3/dist-packages/cheroot/makefile.py", line 24, in write self._flush_unlocked() File "/usr/lib/python3/dist-packages/cheroot/makefile.py", line 33, in _flush_unlocked n = self.raw.write(bytes(self._write_buf)) ^^ File "/usr/lib/python3.11/socket.py", line 724, in write return self._sock.send(b) ^^ File "/usr/lib/python3.11/ssl.py", line 1210, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2393) ``` There's a fix in cheroot repo, but it relies on having python >=3.11.3: * https://github.com/cherrypy/cheroot/pull/518 * https://github.com/python/cpython/pull/103006 Please consider updating python3 version in bookworm to >= 3.11.3 -- System Information: Debian Release: 12.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.49-linuxkit (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_RANDSTRUCT Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#1050286: firefox-esr: only active tab visible in the tab-bar
Package: firefox-esr
Version: 115.1.0esr-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Update to version 115
* What exactly did you do (or not do) that was effective (or
ineffective)?
Normal system update via synaptic
* What was the outcome of this action?
The tab-bar is now at the bottom of the window which is not a big
problem, but the big problem is that I see only the active tab in
the tab-bar even when multiple tabs are open. So I can switch
between the tabs only by using the keyboard and have to know which
tab (content) corresponds to which number (not more than 9 tabs
accessible). Additionally the one visible tab-name overlaps with
the content of the website and it sometimes makes links or buttons
unreachable. Working with this setup is very annoying...
Is this a bug or a new 'feature'?
* What outcome did you expect instead?
I expected a browser that is usable with a mouse...
Best regards
Günter
-- Package-specific info:
-- Extensions information
Name: Adblock Plus - free ad blocker
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled
Name: Add-ons Search Detection
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Amazon.co.uk
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Ecosia
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Ghostery – Privacy Ad Blocker
Location: ${PROFILE_EXTENSIONS}/fire...@ghostery.com.xpi
Status: enabled
Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Language: Deutsch (German) locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-de
Status: enabled
Name: LEO Eng-Deu
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled
Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: System theme — auto theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Web Developer
Location: ${PROFILE_EXTENSIONS}/{c45c406e-ab73-11d8-be73-000a95be3b12}.xpi
Status: enabled
Name: WebCompat Reporter
Location:
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
-- Addons package information
ii firefox-esr 115.1.0esr-1 amd64Mozilla Firefox web browser -
Extended Support Release (ESR)
ii firefox-esr-l10n-de 115.1.0esr-1 all German language package for
Firefox ESR
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox-esr depends on:
ii debianutils 5.8-1
ii fontconfig 2.14.2-4
ii libasound2 1.2.9-1
ii libatk1.0-0 2.49.90-4
ii libc62.37-7
ii libcairo-gobject21.16.0-7
ii libcairo21.16.0-7
ii libdbus-1-3 1.14.8-2
ii libdbus-glib-1-2 0.112-3
ii libevent-2.1-7
Bug#1050284: cdrom: with a ryzen 3 3200 g the scren become unreadable
Package: cdrom Severity: normal X-Debbugs-Cc: edgard.dev...@gmx.fr Dear Maintainer, *** 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 ***
Bug#1039987: systemd-gpt-auto-generator(8) - wrong instruction how to disable
Am Tue, Aug 22, 2023 at 02:31:21PM +0200 schrieb Michael Biebl: Hello Michael, thank you very much for the feedback. I have added replies inline. > On Fri, 30 Jun 2023 19:04:59 +0200 Christoph Brinkhaus > wrote: > > Package: systemd > > Version: 252.6-1 > > Severity: wishlist > > > > Dear Maintainer, > > > > I tried to disable systemd-gpt-auto-generator because I do not need it. > > man 8 systemd-gpt-auto-generator documents the necessary kernel > > parameter in the section "KERNEL COMMAND LINE" which is at the bottom of > > the man page. > > > > Incorrect is the original: > > Those options take an optional boolean argument, and default to yes. The > > generator is enabled by default, and a negative value may > > be used to disable it. > > > > That did not work. Correct is > > Those options take an optional boolean argument, and default to yes. The > > generator is enabled by default, "no" may > > be used to disable it. > > systemd-gpt-auto-generator uses the parse_boolean() function, which > interprets the following values as false [1]: > > >"0", >"no", >"n", >"false", >"f", >"off" > > > With "negative value", any of those strings is meant. > So changing the documentation as per your suggestion would be incomplete. > > I suppose, with "negative value", you understood a negative *integer* value, > like say -1? You are right, this is what I have expected to be ok according to the documentation. Due to your explanation I have found man systemd.syntax which explaines that kind of things. > > I do not have a better suggestion how to phrase it and in any case, this > should be addressed upstream. > I kindly ask you to raise this at https://github.com/systemd/systemd/issues > (maybe you have an idea how the documentation can be improved). I have raised an issue as https://github.com/systemd/systemd/issues/28928 My suggestion is to change "negative value" to "negative string". > > Running a > # grep boolean man/ -R > > shows that the documentation is not really consistent in that regard. > Sometimes it uses, true, yes, false, no, etc. > > Regards, > Michael > > [1] For completeness sake, the corresponding positive values are > >"1", >"yes", >"y", >"true", >"t", >"on" I think it is not easy to maintain the documentation of such a huge project. Kind regards, Christoph signature.asc Description: PGP signature
Bug#1050283: Warning: unsandboxed permission
Package: apt Version: 2.2.4 Severity: normal Tags: upstream X-Debbugs-Cc: slow_sp...@att.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** When using Synaptic, the following error pops up: W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) This is a bothersome problem and probably should be fixed. Please see: https://askubuntu.com/questions/908800/what-does-this-apt-error- message-download-is-performed-unsandboxed-as-root#908825 *** End of the template - remove these template lines *** -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "true"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::NeverAutoRemove:: "^postgresql-"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "contrib/metapackages"; APT::Never-MarkAuto-Sections:: "non-free/metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Move-Autobit-Sections:: "contrib/oldlibs"; APT::Move-Autobit-Sections:: "non-free/oldlibs"; APT::Move-Autobit-Sections:: "restricted/oldlibs"; APT::Move-Autobit-Sections:: "universe/oldlibs"; APT::Move-Autobit-Sections:: "multiverse/oldlibs"; APT::LastInstalledKernel "5.10.0-25-amd64"; APT::Periodic ""; APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null || true; fi"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "false"; APT::Compressor::zstd::Cost "60"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "false"; APT::Compressor::lz4::Cost "50"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-6"; APT::Compressor::lzma::UncompressArg "";
Bug#1041881: RM: winwrangler -- RoQA; depends on gtk2; low popcon
Control: reassign -1 ftp.debian.org Control: severity -1 normal Please remove winwrangler. It is unmaintained both upstream and in Debian, depends on gtk2, and has a very low popcon. I have announced the planned removal a month ago and nobody has reacted.
Bug#1050282: RM: canu [armel armhf i386 mipsel alpha arc hppa hurd-i386 m68k powerpc sh4] -- ANAIS ROM; upstream only works on architectures with {u,}int128 (basically just 64-bit systems + x32)
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: c...@packages.debian.org
Control: affects -1 + src:canu
Hello,
The latest upstream release of canu only works on architectures with
{u,}int128 (basically just 64-bit systems + x32).
Please remove the binary packages of the incompatible archs, none of
which are mentioned anymore in the Debian source package: armel armhf
i386 mipsel alpha arc hppa hurd-i386 m68k powerpc sh4
Thanks!
--
Michael R. Crusoe
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1050281: Updating the kupfer Uploaders list
Source: kupfer Version: 0+v320-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the kupfer package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050075: (no subject)
On Tue, 22 Aug 2023 at 12:54:02 +0200, Nathan Teodósio wrote: > I'm proposing disabling those tests as they were deemed flaky by upstream. I'm testing what I think is a better approach to disabling *all* tests that are considered flaky or failing, so I'm not going to apply this unless the package I'm testing is unsuccessful. (It seemed OK in i386 and s390x builds on the porterboxes.) > +Description: Disable flaky checkerboard tests. > + . > + gitlab.gnome.org/GNOME/gtk/-/commit/a235b59089a7fe2d7957f20bcd2a67f9aef2f724 > + gitlab.gnome.org/GNOME/gtk/-/commit/5e8e4130a51f8d1f599ee74360c5e9126ff40d48 > + . > + "When textures are too large, we will scale them down to fit the max texture > + size, which will cause comparisons to fail." In future, please could you use clickable URLs rather than deleting the https:// prefix, and please could you use the `git format-patch`-like dialect of DEP-3? (Look at most of the existing patches and you'll see what I mean) Thanks, smcv
Bug#1050280: Updating the pysolfc Uploaders list
Source: pysolfc Version: 2.6.4-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the pysolfc package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050279: Updating the pysolfc-cardsets Uploaders list
Source: pysolfc-cardsets Version: 2.0+dfsg2-2.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the pysolfc-cardsets package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050278: Updating the patator Uploaders list
Source: patator Version: 0.9-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the patator package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050277: Updating the pyzor Uploaders list
Source: pyzor Version: 1:1.0.0-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the pyzor package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050276: Updating the hashid Uploaders list
Source: hashid Version: 3.1.4-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the hashid package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050274: Updating the pytest-cookies Uploaders list
Source: pytest-cookies Version: 0.4.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the pytest-cookies package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050275: Updating the alot Uploaders list
Source: alot Version: 0.10-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the alot package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050273: Updating the python-isoweek Uploaders list
Source: python-isoweek Version: 1.3.3-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-isoweek package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050272: Updating the python-rarfile Uploaders list
Source: python-rarfile Version: 3.1-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-rarfile package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050271: Updating the python-slugify Uploaders list
Source: python-slugify Version: 4.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-slugify package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050270: Updating the python-igraph Uploaders list
Source: python-igraph Version: 0.10.2-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-igraph package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050269: Updating the python-cpuinfo Uploaders list
Source: python-cpuinfo Version: 5.0.0-5 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-cpuinfo package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050268: Updating the doona Uploaders list
Source: doona Version: 1.0+git20190108-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the doona package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050267: Updating the python-qrcode Uploaders list
Source: python-qrcode Version: 7.4.2-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-qrcode package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050266: Updating the gummi Uploaders list
Source: gummi Version: 0.8.3+really0.8.3-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the gummi package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050265: Updating the python-pytest-benchmark Uploaders list
Source: python-pytest-benchmark Version: 3.2.2-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-pytest-benchmark package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050264: Updating the bleachbit Uploaders list
Source: bleachbit Version: 4.4.2-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the bleachbit package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050263: Updating the wfuzz Uploaders list
Source: wfuzz Version: 3.1.0-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the wfuzz package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050262: Updating the cssutils Uploaders list
Source: cssutils Version: 1.0.2-7 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the cssutils package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050261: Updating the python-langdetect Uploaders list
Source: python-langdetect Version: 1.0.9-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-langdetect package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050259: Updating the python-mailer Uploaders list
Source: python-mailer Version: 0.8.1-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-mailer package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050260: Updating the python-boltons Uploaders list
Source: python-boltons Version: 21.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-boltons package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050258: Updating the python-pyotp Uploaders list
Source: python-pyotp Version: 2.6.0-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the python-pyotp package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050257: Updating the openjpeg2 Uploaders list
Source: openjpeg2 Version: 2.5.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Hugo Lefeuvre has retired, so can't work on the openjpeg2 package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1050240: Extra information about sponsor
Dear, This work has been done on the account of Trafik Verket (https://www.trafikverket.se/) If applicable this information can be added. Thank you, best regards, Raymond -- -- Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen. www.avg.com
Bug#1050256: autopkgtest fails on debci
Source: systemd Version: 254.1-2 Severity: important Looking at https://ci.debian.net/packages/s/systemd/unstable/amd64/ , systemd has been failing on debci since about the beginning of May. Asking around on #debci, this might be kernel related, as the debci related systems were upgraded to bookworm around that time.
