Bug#1004894: sudo: [i386] invalid opcode

On Thu, Feb 3, 2022 at 9:41 AM Marc Haber wrote: > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > > shows the following: > > Just for the record, the current i386 sudo was built on x86-ubc-02,

Bug#1004896: efibootmgr: please provide some automation

Package: efibootmgr Version: 17-1 Severity: wishlist Dear Maintainer, Please consider providing some level of automation of running debian with efistub as part of the package. There is a very nice write-up with example config files and scripts in the debian wiki https://wiki.debian.org/EFIStub

Bug#1004894: sudo: [i386] invalid opcode

On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > shows the following: Just for the record, the current i386 sudo was built on x86-ubc-02, Logs

Bug#1004717: transition: libkiwix and libzim

Hi, On 2/1/22 23:57, Sebastian Ramacher wrote: Please go ahead Thanks, everything has been uploaded. -- Kunal

Bug#1004894: sudo: [i386] invalid opcode

Package: sudo Version: 1.9.9-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg shows the following: # dmesg | grep traps [ 150.890563] traps: sudo[729] trap invalid opcode ip:44ffa0 sp:bfd59cfc

Bug#1004075: RM: google-compute-engine -- ROM; replaced by google-guest-agent, not in Buster

Hi Liam On Thu, Jan 20, 2022 at 12:07:18PM -0800, Liam Hopkins wrote: > Hi Bastian, this is not quite right. Our first-party packages are named: > > * google-compute-engine > * google-compute-engine-oslogin > * google-guest-agent > > We don't use the packages in Debian currently, but if we want

Bug#1004452: gnuplot 5.4.1+dfsg1-1+deb11u1 flagged for acceptance

Control: tags -1 - pending Hi, On Thu, 2022-02-03 at 01:10 -0500, Daniel Kahn Gillmor wrote: > Hi Adam-- > > Thanks for reviewing, but this is confusing to me. I thought 1004452 > was for GnuPG gnupg2/2.2.27-2+deb11u1, not gnuplot > 5.4.1+dfsg1-1+deb11u1. Which one did you mean to accept with

Bug#1002619: gnuplot 5.4.1+dfsg1-1+deb11u1 flagged for acceptance

package release.debian.org tags 1002619 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: gnuplot Version:

Bug#933070: Bug#933190: ITP: ptvsd -- Python debugger package for use with Visual Studio and Visual Studio Code

On Sat, Jul 27, 2019 at 09:18:36AM -0300, William Grzybowski wrote: > Package: wnpp > Severity: wishlist > Owner: William Grzybowski > > * Package name: ptvsd > Version : 4.3.0 > [...] > * Package name: pydevd > Version : 1.6.1 > The Python Visual Studio Debugger

Bug#1004452: gnuplot 5.4.1+dfsg1-1+deb11u1 flagged for acceptance

Hi Adam-- Thanks for reviewing, but this is confusing to me. I thought 1004452 was for GnuPG gnupg2/2.2.27-2+deb11u1, not gnuplot 5.4.1+dfsg1-1+deb11u1. Which one did you mean to accept with this message? --dkg On Wed 2022-02-02 20:30:58 +, Adam D Barratt wrote: > package

Bug#1004893: gmt: running gmt results in Segfault

Package: gmt Version: 6.3.0+dfsg-2+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: dlake...@street-artists.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Running gmt in any way induces a segfault: dlakelan@tintin:~$

Bug#1004892: transition: zxing-cpp

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I am looking into starting the transition listed at https://release.debian.org/transitions/html/auto-zxing-cpp.html . libzxingcore-dev -> libzxing-dev libzxingcore1-> libzxing1

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-03 03:29:24 +0100, Vincent Lefevre wrote: > On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote: > > Any chance of getting a coredump? > > exim didn't leave a coredump. I could see that Mutt disables coredumps > after some time. I don't know under which condition. I've eventually

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote: > Yeah from exim's POV this workes out as designed. Something very much > unexpected happened, let's freeze the message and tell the admin. The > message is not lost. It is still in queue. Yes, once the issue occurs, exim works as designed. But

Bug#1004891: delta: Packaging licensing incompatible with the upstream

Package: delta Version: 2006.08.03-9 Severity: important X-Debbugs-Cc: jw...@debian.org, b...@brad-smith.co.uk The current packaging licensing (GPL-3+) is incompatible with upstream licensing (BSD-3-Clause). It is a hampering condition to submit patches from Debian to the upstream. I would like

Bug#1004890: ITS: libbs2b

Source: libbs2b Version: 3.1.0+dfsg-2.2 Severity: important X-Debbugs-CC: gainer.and...@gmail.com Dear package libbs2b maintainer in Debian, After looking into the package you maintain (libbs2b, https://tracker.debian.org/pkg/libbs2b), I found that this package received no maintainer updates in

Bug#1004711: gimp uses ebook-viewer (from calibre package) for print preview

On Tue, Feb 1, 2022 at 3:37 PM Simon McVittie wrote: > If you're using a specific desktop environment, then > that desktop environment should be installing its own > opinionated, per-desktop-environment configuration in > /usr/share/applications/$desktop-mimeapps.list, like GNOME does. > Which

Bug#856600: Bugs closed in libtorrent-rasterbar 2.0.5

Control: fixed -1 libtorrent-rasterbar/2.0.5-1 On Wed, 2022-02-02 at 15:50 +0100, Christian Marillat wrote: > Subject: Bugs closed in libtorrent-rasterbar 2.0.5 > Cc: 969780-cl...@bugs.debian.org, 992575-cl...@bugs.debian.org, > 856600-cl...@bugs.debian.org, 987120-cl...@bugs.debian.org, >

Bug#969330: libpam-ssh-agent-auth: Authentication fails a random number of times before succeeding when ED25519 keys are used.

Control: reassign -1 gnupg2 Hi all, This bug actually appears to be in GnuPG itself, not libpam-ssh-agent-auth. Please see my comments at the end of https://github.com/jbeverly/pam_ssh_agent_auth/issues/28. The bug is fixed in GnuPG 2.3.4 and 2.2.33 with the following changelog entry for

Bug#1004889: node-body-parser: missing types

Package: node-body-parser Version: 1.19.0-5 Severity: normal Hi, i'm actually new to installing files in @types/ is this the right place to report a bug when some ts definitions are missing ? Jérémy -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

Hi. Thanks for your attention to detail and encouragement and clarity. I got around to looking at this. tl;dr: I think in fact the patch is working as designed but your particular test scenario is equivalent to "screen screen --invalid-argument", which has a separate (and more

Bug#1004879: acpitool: New upstream development?

On 02 Feb 2022 22:25, Guillem Jover wrote: > Source: acpitool > Source-Version: 0.5.1-6 > Severity: wishlist > Tags: upstream > X-Debbugs-Cc: Al Stone > > Hi! > > I just noticed that Al Stone forked the upstream of this project > at , collected several of the distro

Bug#1004887: Cannot shutdown or reboot on Z690-based motherboard

Package: linux-image-5.15.0-0.bpo.2-amd64 Severity: important Hi, With a new PC that is based on the new Intel AlderLake platform, I cannot reboot, sleep or shutdown a computer. It stucks at some point when the screen is already "black" and nothing is printed in a console anymore. The PC keeps

Bug#1004299: ruby-net-ssh: FTBFS in sid

Control: forwarded -1 https://github.com/net-ssh/net-ssh/issues/843 On Mon, Jan 24, 2022 at 03:35:35PM +0100, Cédric Boutillier wrote: > Package: ruby-net-ssh > Version: 1:6.1.0-2 > > Hi, > > When trying to rebuild ruby-net-ssh in sid, I get test failures related > to DSA cryptography. They all

Bug#1004876: mate-panel: wnck-applet crash with SIGTRAP

I've managed to find out about it and to set GDK_SYNCHRONIZE=1 for D-Bus session service org.mate.panel.applet.WnckletFactory and I will get back with a proper backtrace if it happens again.

Bug#1004861: libc6: dist-upgrade to stable fails kernel version checks on LXC guests

control: fixed -1 libc6/2.31-14 On 2022-02-02 15:33, Olivier Berger wrote: > Package: libc6 > Version: 2.31-13 > Severity: normal > > Dear Maintainer, > > I tried to upgrade from old-stable to stable on an LXC guest running on > an ASUS NAS (underlying "ADM" OS) and got blocked during preinst :

Bug#1004886: dmesg: colorization of emerg/notice/info/debug not handled

Package: util-linux Version: 2.37.3-1 Severity: normal Tags: patch upstream X-Debbugs-Cc: steve+...@tecwec.eu Hello, please find attached a very simple patch which allows consistent customization of the coloring schemes of the emerg, notice, info and debug levels in dmesg. (currently only alert,

Bug#963980: issue confirmed on newly installed Debian 11.2

I can confirm I have the same issue using a brandly new installed machine with the nvidia driver. primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d"

Bug#1004885: intel-compute-runtime: switch to llvm-toolchain-13

Source: intel-compute-runtime Version: 21.32.20609-1 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Usertags: llvm-12-rm The current default version of llvm is llvm-toolchain-13. To reduce the number of llvm versions, please consider switchting to llvm-toolchain-13 (or

Bug#1004884: aspectc++: switch to llvm-toolchain-13

Source: aspectc++ Version: 1:2.3+git20211104-2 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Usertags: llvm-12-rm The current default version of llvm is llvm-toolchain-13. To reduce the number of llvm versions, please consider switchting to llvm-toolchain-13 (or the

Bug#1004883: intel-graphics-compiler: switch to llvm-toolchain-13

Source: intel-graphics-compiler Version: 1.0.8744-2 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Usertags: llvm-12-rm The current default version of llvm is llvm-toolchain-13. To reduce the number of llvm versions, please consider switchting to llvm-toolchain-13 (or

Bug#1004882: crystal: switch to llvm-toolchain-13

Source: crystal Version: 1.2.2+dfsg-1 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm The current default version of llvm is llvm-toolchain-13. To reduce the number of llvm versions, please consider switchting to llvm-toolchain-13 (or the unversioned counterpart).

Bug#1004881: aflplusplus: switch to llvm-toolchain-13

Source: aflplusplus Version: 3.14c-2 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Usertags: llvm-12-rm The current default version of llvm is llvm-toolchain-13. To reduce the number of llvm versions, please consider switchting to llvm-toolchain-13 (or the unversioned

Bug#1004880: bibcursed: Please package new version 2.0.1

Source: bibcursed Version: 2.0.0-6.1 Severity: normal Tags: sid bookworm Dear Debian bibcursed package maintainer, A new release is available at https://sourceforge.net/projects/bibcursed/files/bibcursed/2.0.1/ . Please consider packaging it. Thanks! Regards, Boyuan Yang signature.asc

Bug#1004879: acpitool: New upstream development?

Source: acpitool Source-Version: 0.5.1-6 Severity: wishlist Tags: upstream X-Debbugs-Cc: Al Stone Hi! I just noticed that Al Stone forked the upstream of this project at , collected several of the distro patches and prepared a 0.5.2 release. Although no more activity

Bug#1004877: transition: gupnp-av

Control: tags -1 confirmed Control: forwarded -1 https://release.debian.org/transitions/html/auto-gupnp-av.html On 2022-02-02 15:49:31 -0500, Jeremy Bicha wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc:

Bug#1004878: ITP: golang-github-google-gousb -- provides low-level interface for accessing USB devices

Package: wnpp Severity: wishlist Owner: Francisco Vilmar Cardoso Ruviaro X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org, francisco.ruvi...@riseup.net, math...@calenhad.com * Package name: golang-github-google-gousb Version : 1.1.1 Upstream Author :

Bug#1004877: transition: gupnp-av

Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: gupnp...@packages.debain.org Severity: normal I request permission to do the transition for gupnp-av (this will also complete the gupnp-dlna transition simultaneously). I completed the

Bug#1004875: python-fluids: autopkgtest regression on arm64, i386 and ppc64el:

Source: python-fluids Version: 1.0.9-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-fluids the autopkgtest of python-fluids fails in testing when that autopkgtest is run with

Bug#1004874: dialog: --max-input ignores values higher than 2048

Package: dialog Version: 1.3-20201126-1 Severity: normal Dear Maintainer, The --max-input option seems to ignore values higher than 2048, which is the default limit according to the man page. This means that we cannot pass lines to the editbox widget that are longer than 2047 characters since

Bug#1004873: python-django-netfields: autopkgtest regression: runuser: not found

Source: python-django-netfields Version: 1.2.4-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-django-netfields the autopkgtest of python-django-netfields fails in testing when

Bug#1004452: gnuplot 5.4.1+dfsg1-1+deb11u1 flagged for acceptance

package release.debian.org tags 1004452 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: gnuplot Version:

Bug#1002620: pypy3 7.3.5+dfsg-2+deb11u1 flagged for acceptance

package release.debian.org tags 1002620 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: pypy3 Version:

Bug#1004872: sagemath FTBFS on armhf

Package: sagemath Version: 9.0-1 Severity: normal Control: tags -1 + ftbfs We are getting test timeouts on armhf since sagemath 9.0-1. The exact spots where it happens have changed over time, one that stayed the whole time is in src/sage/modular/modform/constructor.py. From there one can see

Bug#1004483: xserver-xorg-video-intel 2.99.917+git20200714-1+deb11u1 flagged for acceptance

package release.debian.org tags 1004483 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: xserver-xorg-video-intel

Bug#976991: libldap-2.4-2:amd64: Please consider building with openssl instead of gnutls

On Wed, Feb 02, 2022 at 12:53:59PM -0600, Matt Zagrabelny wrote: Any traction on a gnutls -> openssl migration for openldap for bookworm? I don't have any technical reasons to block it, but for personal reasons I'm not likely to pursue it myself. As already written in the RFH bug (#512360),

Bug#1000158: samba: random segfaults since upgrading to bullseye

Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=14969 On Tue, Jan 25, 2022 at 02:13:32PM +1300, Andrew Bartlett wrote: > My best suggestion is to report upstream into the Samba bugzilla and > try using the most recent released versions just in case it helps. Re-submitted as bug

Bug#1003659: bullseye-pu: package python-django/2:2.2.26-1~deb11u1

Control: tags -1 + moreinfo Hi, On Thu, 2022-01-13 at 06:16 -0500, Chris Lamb wrote: > * Fix a traceback around the handling of > RequestSite/get_current_site() due > to a circular import by backporting commit 78163d1a from > upstream. Thanks > to Raphaël Hertzog for the report.

Bug#1004870: python-xarray: autopkgtest regression on s390x

Source: python-xarray Version: 0.21.0-1 X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer python-xarray's autopkgtests are failing on the big-endian s390x architecture [1]. I've copied what

Bug#1004869: python-xarray: autopkgtest regression on i386

Source: python-xarray Version: 0.21.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer python-xarray's autopkgtests are failing on the i386 architecture [1]. I've copied what I hope is the relevant part of the log

Bug#1004868: dialog: menu segfaults when resizing

Package: dialog Version: 1.3-20201126-1 Severity: normal Dear Maintainer, The menu widget segfaults when resizing the terminal. Steps to reproduce: 1. Create a menu with three items:    dialog --menu Test 18 80 3 0 "Item 0" 1 "Item 1" 2 "Item 2" 2. Reduce the vertical size of the terminal so

Bug#1004855: python3-ipykernel: missing dependency on debugpy

On Wed, Feb 02, 2022 at 01:33:30PM +, Gordon Ball wrote: > ps, I had a search just now and it looks like someone else was working > 1 year ago on `ptvsd` (renamed `debugpy` later), but it doesn't look > like it was ever uploaded. But perhaps something to build upon. > >

Bug#976991: libldap-2.4-2:amd64: Please consider building with openssl instead of gnutls

--On Wednesday, February 2, 2022 12:53 PM -0600 Matt Zagrabelny wrote: On Wed, Dec 9, 2020 at 2:23 PM Ryan Tandy wrote: I have indeed heard that we consider openssl to be a system library now, and a couple of people pointed out that it's no longer mentioned in ftp-master's REJECT-FAQ.

Bug#1004867: RFP: eatmydata-sc -- eatmydata replacement using seccomp

On Wed, Feb 02, 2022 at 07:16:28PM +0100, Jakub Wilk wrote: > Package: wnpp > Severity: wishlist > > * Package name: eatmydata-sc > Upstream Author : Julian Andres Klode > * URL : https://github.com/julian-klode/eatmydata-sc > * License : LGPLv2.1 > Programming Lang:

Bug#968679: debci: self-service multipackage pinning does not work as documented

Hi Drew, On 02-02-2022 12:37, Drew Parsons wrote: Package: debci Version: 3.4 Followup-For: Bug #968679 This bug is still live. I've tried to test src:pytest-mpi from experimental, using src:python-sybil from experimental. With or without spaces in the pin line, the test fails to launch,

Bug#1004867: RFP: eatmydata-sc -- eatmydata replacement using seccomp

Package: wnpp Severity: wishlist * Package name: eatmydata-sc Upstream Author : Julian Andres Klode * URL : https://github.com/julian-klode/eatmydata-sc * License : LGPLv2.1 Programming Lang: C Description : eatmydata replacement using seccomp eatmydata-sc is

Bug#1004866: RFP: cppinsights -- see your source code with the eyes of a compiler

Package: wnpp Severity: wishlist * Package name: cppinsights Version : 0.6 Upstream Author : Andreas Fertig * URL : https://github.com/andreasfertig/cppinsights * License : Expat Programming Lang: C++ Description : cppinsights C++ Insights is a

Bug#1004865: tuned: New upstream version available

Package: tuned Version: 2.15.0-1 Severity: wishlist Hi, v2.17.0 is available since 2022-01-16, see: https://github.com/redhat-performance/tuned/releases Thanks for maintaining tuned! :) regards -mika-

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-01 Vincent Lefevre wrote: > On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote: > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to > > immutable memory) > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of > > 7 bytes (pipeheader)

Bug#1004855: python3-ipykernel: missing dependency on debugpy

On Wed, Feb 02, 2022 at 01:06:56PM +, Gordon Ball wrote: > On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > > Package: python3-ipykernel > > Version: 6.7.0-1 > > Severity: serious > > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > > > > ipykernel depends on the debugpy

Bug#1004855: python3-ipykernel: missing dependency on debugpy

On Wed, Feb 02, 2022 at 01:33:30PM +, Gordon Ball wrote: > On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > > Package: python3-ipykernel > > Version: 6.7.0-1 > > Severity: serious > > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > > > ps, I had a search just now and it

Bug#1004864: density-fitness FTBFS with libpdb-redo-dev 2.0.1

Source: density-fitness Version: 1.0.0-4 Severity: serious Tags: ftbfs Forwarded: https://github.com/PDB-REDO/density-fitness/commit/cad04e1ac86037537c75bfaa67db49946f140b3c https://buildd.debian.org/status/logs.php?pkg=density-fitness=1.0.0-4%2Bb1 ... dh_auto_build -a make -j4

Bug#1004863: Bootstrapping a Fedora produces a system with an empty package database

Package: dnf Version: 4.5.2-6 Severity: serious Hello, thank you for packaging dnf in Debian! I'm trying to use dnf to bootstrap rpm-based chroots, which seems to work, but the rpm package database on the resulting distribution is empty, as in, `rpm -qa` returns no output, and `rpm -q` on any

Bug#1004748: guestfs-tools ftbfs with new ocaml

On Tue, 1 Feb 2022 16:23:47 +0100 Matthias Klose wrote: > Package: src:guestfs-tools > Version: 1.46.1-4 > Severity: serious > Tags: sid bookworm > > guestfs-tools ftbfs with new ocaml > > [...] > Use the equivalent signed form: +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3. > Hint: Enabling or disabling a

Bug#997367: virt-manager: FTBFS: AssertionError

Il 02/02/2022 11:56, Bastian Germann ha scritto: > On Tue, 25 Jan 2022 17:55:18 +0100 Fabio Fantoni wrote: >> Hi, I saw that remain few days for autoremoval from testing I prepared an MR with some upstream patch that solve current FTBFS with some tests and another small fix for a crash case:

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

Axel Beckert writes ("Re: Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded"): > Feel free to work in the debian-bug-1000138 branch at > https://salsa.debian.org/debian/screen/-/tree/debian-bug-1000138 Cool, thanks. I agree with everything you said and will look at

Bug#1004862: neglected note in dist-upgrade documentation, section 4

Package: apt-get Version: any Hi, Package apt-get is a placeholder for https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#backup as it's with apt-get dist-upgrade that the potential problem manifests. The problem scenario is as such: Some services have the task of

Bug#1004786: Acknowledgement (ITP: tvheadend -- TV streaming server and recorder)

For documentation purposes, I'd like to describe the current issues preventing the packaging of tvheadend version 4.2.8: 1. tvheadend depends currently on ExtJS 3.4 for its web interface. There are discussions upstream to move to another framework but this appears to be stalled [0] 2.

Bug#1003614: sudo: New sudo asks for a password on a Docker container

On Wed, Feb 02, 2022 at 02:40:59PM +0200, Timo Aaltonen wrote: > Sudo is now asking the password when root is running it. That is caused > by the new config. If you don't help me reproducing the issue, the only thing I can do is close this bug as unreproducible. I think you know that, being a DD

Bug#1003095: /usr/bin/script: hangs when child doesn't read input fast enough

Hi! Bumping this patch after 2ish weeks :) Best, On Fri, Jan 14, 2022 at 12:28:12AM +0100, наб wrote: > Subject: Put master PTY into non-blocking mode and buffer its output > to avoid deadlock > > If we filled the script->child buffer before the child had a chance > to read any input, we'd

Bug#1004861: libc6: dist-upgrade to stable fails kernel version checks on LXC guests

Package: libc6 Version: 2.31-13 Severity: normal Dear Maintainer, I tried to upgrade from old-stable to stable on an LXC guest running on an ASUS NAS (underlying "ADM" OS) and got blocked during preinst : Preparing to unpack .../libc6_2.31-13+deb11u2_amd64.deb ... /var/lib/dpkg/tmp.ci/preinst:

Bug#1004858: golang-github-containernetworking-plugins: Please move executables from /usr/lib/cni to /usr/libexec/cni

Le 2/02/22 à 14:58, Shengjing Zhu a écrit : On Wed, Feb 2, 2022 at 9:33 PM Laurent Bigonville wrote: Source: golang-github-containernetworking-plugins Version: 0.9.0-1 Severity: normal Hello, I think that the executables should be moved from /usr/lib/cni to /usr/libexec/cni /usr/libexec is

Bug#1004860: glusterfs-client: no real dependency on fuse

Package: glusterfs-client Version: 10.1-1+b1 Severity: normal Dear Maintainer, while building glusterfs in ubuntu and getting ready to include it in Ubuntu Main (https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321), I happened to evaluate its usage of fuse, and it looks like the

Bug#968305: closing 968305

Hi Michael, On Wed, Feb 02, 2022 at 01:43:08PM +, Michael Fladischer wrote: > # Fixed by upstream. > close 968305 2.0.0-1 Can you point us to the fix for the issue? The two upstream issues related to this seems slightly confusing, so I would like to undestand better what is the actual fix

Bug#1004858: golang-github-containernetworking-plugins: Please move executables from /usr/lib/cni to /usr/libexec/cni

On Wed, Feb 2, 2022 at 9:33 PM Laurent Bigonville wrote: > > Source: golang-github-containernetworking-plugins > Version: 0.9.0-1 > Severity: normal > > Hello, > > I think that the executables should be moved from /usr/lib/cni to > /usr/libexec/cni > > /usr/libexec is a more sutable location for

Bug#925358: [klibc] qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, …)

On Tue, 2022-02-01 at 16:23 +, Thorsten Glaser wrote: > retitle 925358 qemu-user-static: mis-emulates something to do with > process/signal handling (m68k, s390x, …) > affects 925358 klibc-dev > thanks > > This still happens. (And retitling because I almost filed a bug > against klibc again…

Bug#1004855: python3-ipykernel: missing dependency on debugpy

On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > Package: python3-ipykernel > Version: 6.7.0-1 > Severity: serious > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > ps, I had a search just now and it looks like someone else was working 1 year ago on `ptvsd` (renamed `debugpy`

Bug#1004858: golang-github-containernetworking-plugins: Please move executables from /usr/lib/cni to /usr/libexec/cni

Source: golang-github-containernetworking-plugins Version: 0.9.0-1 Severity: normal Hello, I think that the executables should be moved from /usr/lib/cni to /usr/libexec/cni /usr/libexec is a more sutable location for executables (and it will also help with systemd labeling) Searching the

Bug#1001589: I'm stuck too

On 2 February 2022 at 08:53, Emmanuel Charpentier wrote: | For information : this bug has bitten me too : | | I run testing, R (from testing), a bucketfull of R packages (mostly | from R repositories) and sagemath (installed from source). | | Recently, the "energy" R packages started to be

Bug#1004855: python3-ipykernel: missing dependency on debugpy

On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > Package: python3-ipykernel > Version: 6.7.0-1 > Severity: serious > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > ipykernel depends on the debugpy package, as stated in setup.py. > However, within Debian build, python3-debugpy is

Bug#1004832: ITP: hyx -- minimalistic but powerful vim-like hex editor

On Wed, 2022-02-02 at 14:02 +0100, Geert Stappers wrote: > Is there a VCS,  Version Control System,  that has hyx debian > packaging? > > (Please recieve that yes-no-question as a conversation starter) No. Should I upload this as a git somewhere? The original project has no version control.

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

Hi Ian, Ian Jackson wrote: > > I also tried to modify your patch to at least get a non-zero exit code > > or a visible error message in your case, but failed so far for both. > > I will also look at this, but probably not until tonight. Will that > be soon enough for you ? I've uploaded

Bug#1004832: ITP: hyx -- minimalistic but powerful vim-like hex editor

On Wed, Feb 02, 2022 at 06:23:30AM -0600, Russell Hernandez Ruiz wrote: > On Wed, 2022-02-02 at 08:12 +0100, Geert Stappers wrote: > > Show the (libre software) world what is already done to get there. > > > > In other words: > >   Make it possible that reviewing of the packaging came be started.

Bug#1004832: builds fine on unstable Was: Bug#1004832: ITP: hyx

On Wed, Feb 02, 2022 at 06:23:30AM -0600, Russell Hernandez Ruiz wrote: > > I was able to build on bullseye, OK > but not on stretch due to debhelper-compat. also OK (as in: no need the worry about) Groeten Geert Stappers -- Silence is hard to parse

Bug#1004832: improbable-bug-number-in-closes Was: Bug#1004832: ITP: hyx

On Wed, Feb 02, 2022 at 06:23:30AM -0600, Russell Hernandez Ruiz wrote: > On Wed, 2022-02-02 at 08:12 +0100, Geert Stappers wrote: > > Show the (libre software) world what is already done to get there. > > > > Lintian outputs: > > $ lintian hyx_2021.06.09-1_amd64.deb > W: hyx:

Bug#1003614: sudo: New sudo asks for a password on a Docker container

Marc Haber kirjoitti 2.2.2022 klo 13.50: > Control: outlook -1 close 2022-02-28 > > On Wed, Jan 12, 2022 at 08:05:51PM +0100, Marc Haber wrote: >> On Wed, Jan 12, 2022 at 06:36:38PM +0200, Timo Aaltonen wrote: >>> I'm using an Azure pipeline for running tests on a Docker image, and some >>>

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote: > 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to > immutable memory) > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of 7 > bytes (pipeheader) from transport process 35015 for transport smtp

Bug#1001251: debcargo changed names of a feature package

Control: affects 1001251 + src:rust-sequoia-openpgp On Tue 2021-12-07 03:47:32 +0400, Daniel Kahn Gillmor wrote: > note that previously, …+compression-deflate-dev Provides: a virtual > …+flate2-dev > package. Now, …+flate2-dev Provides: a virtual > …+compression-deflate-dev package. The same

Bug#601469: sudo not working with ircp

Control: outlook -1 close by 2022-03-31 On Sat, Dec 11, 2021 at 10:15:37PM +0100, Marc Haber wrote: > I would like to close this bug by the end of march 2022 if it cannot be > reproduced any more. I understand this issue is more than a decade old.

Bug#1004857: bts does not support outlook

Package: devscripts Version: 2.22.1 Severity: wishlist File: /usr/bin/bts Hi, ths bts tool does not allow to set the outlook keyword. It should. Greetings Marc

Bug#574404: sudo: postinst uses prompting

Control: outlook -1 close by 2022-03-31 On Sat, Dec 11, 2021 at 10:11:29PM +0100, Marc Haber wrote: > I understand that this is a very old issue and do not expect an answer, > I will though close this bug report by the end of March 2022 if no > answer is given.

Bug#1004856: psmisc: killall is not finding some processes

Package: psmisc Version: 23.4-2 Severity: important Hello, On my machine, it looks like killall is not finding some processes, like firefox, or podman $ ps ux|grep firefox|head -1 bigon 772207 57.0 7.5 14173340 2487880 tty2 Rl+ jan31 1772:09 /usr/lib/firefox/firefox $ LC_ALL=C killall

Bug#793660: Is still an issue

Control: outlook -1 close 2022-04-30 thanks On Sat, Dec 11, 2021 at 09:22:15AM +0100, Marc Haber wrote: > is this still an issue? If so, can I get more instructions about how do > reproduce this please? Please check with sudo 1.9.9 whether this still happens. If the sudo maintainers cannot

Bug#1003614: sudo: New sudo asks for a password on a Docker container

Control: outlook -1 close 2022-02-28 On Wed, Jan 12, 2022 at 08:05:51PM +0100, Marc Haber wrote: > On Wed, Jan 12, 2022 at 06:36:38PM +0200, Timo Aaltonen wrote: > > I'm using an Azure pipeline for running tests on a Docker image, and some > > steps require running > > sudo. The new version

Bug#906752: sudo, pam_keyinit, what to do?

X-Debbugs-CC: vor...@debian.org thanks On Sat, Feb 27, 2021 at 06:38:00PM +0100, Hilko Bengen wrote: > The pam_keyring(8) manpage advises against adding pam_keyinit > > , > | This module should not, generally, be invoked by programs like su, > | since it is usually desirable for the key set

Bug#982160: sudo does not honour "NOPASSWD" directive

Control: tags -1 unreproducible moreinfo On Mon, Feb 08, 2021 at 11:13:41AM -0500, Wolfgang Sourdeau wrote: > It still asks me for a password this way too. I am wondering if this is > related to pam but I don't know how to check that. > > Le 2021-02-08 00:46, Bdale Garbee a écrit : > > Wolfgang

Bug#968679: debci: self-service multipackage pinning does not work as documented

Package: debci Version: 3.4 Followup-For: Bug #968679 This bug is still live. I've tried to test src:pytest-mpi from experimental, using src:python-sybil from experimental. With or without spaces in the pin line, the test fails to launch, with error message "Target Sources (main/source/Sources)

Bug#1004855: python3-ipykernel: missing dependency on debugpy

Package: python3-ipykernel Version: 6.7.0-1 Severity: serious X-Debbugs-Cc: Julien Puydt , Gordon Ball ipykernel depends on the debugpy package, as stated in setup.py. However, within Debian build, python3-debugpy is not listed in the Build-Depends, so the resulting binary package does not

Bug#1004854: reportbug: says "Unrecognised token: ..." on startup

Package: reportbug Version: 11.3.0 Severity: normal On starting reportbug, it says: erdos:~ $ reportbug Unrecognized token: 3.15 Please enter the name of... Here, "3.15" is taken from the "reportbug_version" line of .reportbugrc; deleting this RC file and recreating it by running reportbug

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

Axel Beckert writes ("Re: Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded"): > Axel Beckert wrote: > > Unfortunately the relevant error message "Argument count or length > > limit exceeded" does not show up with the patch. > > Additionally it also exits with exit

  1   2   >