Package: sasl-xoauth2
Version: 0.20-1+b1
Priority: wishlist
It looks likesasl-xoauth2 has been lingering in experimental for more
than a year now.
This package is genuinely useful and it works (at least for me). Is
there a plan to promote it to unstable and beyond?
Package: fcgiwrap
Version: 1.1.0-16
Priority: wishlist
fcgiwrap 1.1.0 is from 2013 and is missing important improvements that
have been accepted in master, such as:
https://github.com/gnosek/fcgiwrap/commit/1b44aba5ca0be67d0d50fd897b9fbe789fcd14f7
https://github.com/gnosek/fcgiwrap/commit/2041deb
Package: bind9
Version: 1:9.19.24-185-g392e7199df2-1
Version 1:9.19.24-185-g392e7199df2-1 of the bind9 package includes this change:
https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/9046
Which changes the default ACL for zone transfers (allow-transfer) from
"allow by default" to "deny
Package: acct
Version: 6.6.4-5+b2
The acct package installs /etc/cron.monthly/acct which uses the last(1) command.
The `last` command used to be provided by the util-linux package, but
it has been deliberately removed starting from util-linux 2.40.1-3
(see util-linux changelog).
This means that,
I would like to second this RFP. I recently received a notification
from Google warning me that they are phasing out password
authentication, which (in the case of my account) will stop working on
May 30. Once that happens, OAuth2 will be the only supported GMail
SMTP authentication mechanism. This
Package: ovmf
Version: 2022.02-1
Severity: important
Control: fixed -1 2021.11-1
An ovmf regression somewhere between 2021.11-1 and 2022.02-1 makes it
impossible to use a TPM in Windows guest VMs (tested with various
Windows 11 builds). The Windows Device Manager shows the TPM as
defective, with t
Package: firmware-bnx2x
Version: 20210818-1
Severity: grave
On Linux 5.16, the bnx2x module requests firmware 7.13.21.0:
# modinfo bnx2x
filename:
/lib/modules/5.16.0-2-amd64/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko
firmware: bnx2x/bnx2x-e2-7.13.21.0.fw
firmware: bnx2x/bnx2
By the way, for those who don't like patching packaged files, here's a
workaround for manually overriding the root= parameter from
/etc/default/grub:
GRUB_FS=manual
GRUB_DISABLE_LINUX_UUID=true
GRUB_DEVICE=ZFS=yourpoolname/path/to/your/root/dataset
Control: found -1 2.04-18
I just hit this bug. It rendered my system unbootable because my root
ZFS pool has the new zstd compression feature enabled, and it looks
like grub-probe choked on that.
There are two things that I found highly frustrating here:
- While my root (/) is on ZFS, my /boot i
Hi Luca,
On Fri, 27 Nov 2020 at 18:09, Luca Boccassi wrote:
> Can reproduce the issue - sent a patch to use flock():
>
> https://patchwork.ozlabs.org/project/netdev/patch/20201127180651.80283-1-bl...@debian.org/
>
> Please test it as well, cannot reproduce anymore once the fix is in.
Sorry for t
Package: qemu-system-x86
Version: 1:5.0-5
resolv.conf(5) states:
> If [/etc/resolv.conf] does not exist, only the name server on the local
> machine will be queried, and the search list contains the local domain name
> determined from the hostname.
qemu user-mode networking (a.k.a SLIRP, a.k.a
Package: iproute2
Version: 4.20.0-2
Severity: important
Control: found -1 5.4.0-1
The ipnetns.c:netns_add() function sets up the /var/run/netns mount
point in a way that is fragile to race conditions if the routine is
entered to by multiple processes at the same time.
If the race condition is tri
Package: libsoxr0
Version: 0.1.3-2
Control: fixed -1 0.1.3-1
Steps to reproduce:
$ sox -n -r 44100 test.wav synth 1 sine 1000
$ ffmpeg -i test.wav -filter:a "aresample=48000:resampler=soxr" testout.wav
ffmpeg version 4.2.1-2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 9 (Debian
Package: nftables
Version: 0.9.2-2
Severity: minor
$ cat > nftables.conf <
Package: geoipupdate
Version: 4.0.6-1
After installing geoipupdate, the bundled cron job fails with:
# /usr/bin/geoipupdate
Error preparing to update: database directory is not available: stat
/var/lib/GeoIP: no such file or directory
Workaround:
# mkdir /var/lib/GeoIP
Seems like that command
Package: netsniff-ng
Version: 0.6.5-1+b2
Severity: important
# astraceroute --dev eth0 --host debian.org
Cannot open GeoIP6 city database, try --update!
# astraceroute --update
Cannot open or create file /usr/share/netsniff-ng/country4.dat.gz! No
such file or directory.
# mkdir /usr/share/netsnif
Package: jq
Version: 1.6-1
Severity: minor
This works, because "foo" is a valid JSON value:
$ jq --null-input '$ARGS' --jsonargs '"foo"'
{
"positional": [
"foo"
],
"named": {}
}
But if the passed-in value is not a valid JSON value, jq crashes violently:
$ jq --null-input '$ARGS' --jso
Package: bs1770gain
Version: 0.6.5-1
Steps to reproduce:
$ sox -n '1 & 2.wav' synth 1 sine 1000
$ bs1770gain --xml --suppress-progress . | xmllint -
-:3: parser error : xmlParseEntityRef: no name
^
Correct escaping would be "1 & 2.wav".
This is a re
Package: bs1770gain
Version: 0.6.5-1
Steps to reproduce:
$ sox -n file.wav synth 1 sine 1000
$ bs1770gain --xml --suppress-progress --sample-peak .
In contrast, version 0.5 used to return something like this:
Package: bs1770gain
Version: 0.6.5-1
Severity: minor
$ bs1770gain --help
[...]
--suppress-progess: suppress printing processing progress
The correct spelling is --suppress-progress.
Package: bs1770gain
Version: 0.6.5-1
Steps to reproduce:
$ sox -n file.wav synth 1 sine 1000
$ bs1770gain --xml . | xmllint -
-:6: parser error : PCDATA invalid Char value 8
30%
^
-:6: parser error : PCDATA invalid Char value 8
30%
[...]
The problem is that progress information is being output
Package: xmlstarlet
Version: 1.6.1-2
Steps to reproduce:
$ echo '' | xmlstarlet fo --omit-decl; echo $?
Expected result:
0
Actual result:
5
What's really weird is that the returned error code is always
identical to the number of bytes written to the output.
This bug seems to only occur if
Yes, I just installed 0.5.2-2 and the segfault appears to be gone. Thank you!
This bug is not fixed in version 0.5.1-3 and can still be reproduced
using the exact same steps as described above (and below). In fact I
had already verified that it still occurs in upstream 0.5.0 (see
message #10).
$ sox -n sine.wav synth 1 sine 1000
$ ffmpeg -i sine.wav sine.mp3
$ bs1770g
Package: prometheus-node-exporter
Version: 0.16.0+ds-2
Severity: normal
Release 0.16.0+ds-2 of prometheus-node-exporter introduces a
regression in which, as long as the package is installed in the
machine, drives that are in stand by mode (i.e. spun down) will be
woken up every 15 minutes.
This i
Package: parallel
Version: 20161222-1
Severity: normal
Dear Maintainer,
To reproduce:
$ : | parallel --will-cite --shuf echo
Modification of non-creatable array value attempted, subscript -1 at
/usr/bin/parallel line 6359.
Basically, if there is no input (i.e. nothing to do) and --shuf is
used,
, options=0x7fffdeb0) at
bs1770gain_tree.c:155
#16 0x8f96 in main (argc=2, argv=0x7fffe0e8) at
bs1770gain.c:1053
On Sat, 6 Oct 2018 at 15:58, Etienne Dechamps wrote:
>
> Package: bs1770gain
> Version: 0.4.12-3+b1
> Severity: important
>
> --- Please enter the repo
Package: bs1770gain
Version: 0.4.12-3+b1
Severity: important
--- Please enter the report below this line. ---
bs1770gain segfaults when running on most MP3 files. (Other formats,
like FLAC, appear to work fine.)
Steps to reproduce:
$ sox -n sine.wav synth 1 sine 1000
...
$ ffmpeg -i sine.wav sine
Package: systemd
Version: 235-3
Severity: important
Tags: patch upstream fixed-upstream
After upgrading to systemd 235-3 I ran into the exact issue described
at https://github.com/systemd/systemd/issues/7055
That is, systemd segfaults when trying to start a unit that makes use
of BindPaths or Bin
Package: libtorrent-rasterbar9
Version: 1.1.1-1+b2
Severity: serious
Due to a bug in libtorrent 1.1.0 and 1.1.1, renaming a torrent (or, more
worryingly, loading a torrent that was renamed in the past) can result
in filename corruption, where subdirectories appear out of nowhere.
See: http://dev.
Package: mysql-server-5.6
Version: 5.6.25-3
Severity: important
"systemctl stop mysql" hangs forever after I upgraded from MySQL 5.5 to
5.6. The systemd journal shows the following:
Sep 05 10:53:45 zyklos.edechamps.fr systemd[1]: Stopping MySQL Community
Server...
Sep 05 10:53:45 zyklos.
31 matches
Mail list logo
