Package: initscripts
Version: 3.14-3
Severity: wishlist
Dear Maintainer,
/etc/init.d/kmod was recently dropped from the kmod package. The script
used to load kernel modules sourced from drop-in files
in /etc/modules-load.d/ during boot.
My first idea was suggesting the script for inclusion into
On Tue, Mar 04, 2025 at 04:53:08AM +0100, Ben Hutchings wrote:
> Please re-send the patch to the kl...@zytor.com mailing list. It needs
> to be suitably formatted to apply with "git am", so please include a
> proper commit message in the patch and a Signed-off-by line as the
> Developer Certificat
Updating one of the affected machines to Trixie restored original device
naming behavior for encrypted volumes.
df output on upgraded system:
df -a /mnt
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/_dev_sdb 976746200 589563584 386680320 61% /mnt
With device n
outputs e.g., /dev/dm-2 instead of /dev/mapper/_dev_sdb in its
first column for a luks encrypted disk.
df -h | grep /mnt
old:
/dev/mapper/_dev_sdb 932G 530G 402G 57% /mnt
new:
/dev/dm-3 932G 530G 402G 57% /mnt
df output change broke a script (the df behavior prior to the
My key is available at many sources, canonical two for me are:
https://github.com/robbat2.gpg
https://keys.gentoo.org/pks/lookup?search=0xBDEBB6A52F156FDF3168D91119395F23C58826C4&hash=on&op=vindex
I just refreshed it on these as well:
https://pgpkeys.eu/pks/lookup?search=BDEBB6A52F156FDF3168D91119
Package: libtemplate-perl
Severity: normal
X-Debbugs-Cc: none, H.-Dirk Schmitt
The package is not updated since 2018!
The current stable version of bugzilla (5.2) is requiring at least v3.008.
-- System Information:
Debian Release: 12.7
APT prefers stable-updates
APT policy: (600, 's
On Sun, Oct 13, 2024 at 12:16:01PM +0200, Andreas Tille wrote:
> Well, the package simply was showing up in the query for the bug of the day
> fulfilling the criteria
>
> - No VCS or obviously outdated VCS (alioth, svn, cvs)
Yes, I've never really used those; especially for small packages with
On Sat, Oct 12, 2024 at 05:09:08PM +0200, Andreas Tille wrote:
> - Bugs filed against the package do not have answers from the
> maintainer.
> - There are QA issues with the package.
Wait, what? The last open issue is from 2016. It has a long discussion,
which basically ended up in “report
IMEOUT_MAX=1000
CONFIG_DRM_XE_PREEMPT_TIMEOUT_MIN=1
CONFIG_DRM_XE_ENABLE_SCHEDTIMEOUT_LIMIT=y
On Sat, Sep 14, 2024 at 3:49 PM Ben Hutchings wrote:
> Control: notfound -1 6.10.9
> Control: found -1 6.10.9-1
>
> On Thu, 2024-09-12 at 21:35 +0200, Petter L. H. Eide wrote:
> > Pa
On Thu, Sep 12, 2024 at 11:51:00PM -0500, Daniel Lewart wrote:
> Could y'all be so kind as to answer the question of whether the smbfs
> filesystem
> exists in Debian anymore?
I'm not sure why you need to involve the Samba maintainers in this...
It's easy to check, smbfs was removed from the kern
Package: src:linux
Version: 6.10.9
Severity: wishlist
Dear Maintainer,
Since kernel 6.8, the xe driver for intel GPUs has been available as a
kernel module. Please consider including this by enabling CONFIG_DRM_XE.
See following references for more information:
- https://docs.kernel.org/next
On Thu, Sep 12, 2024 at 12:20:30AM -0500, Daniel Lewart wrote:
> 1) smbfs was dropped in 2012:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620847
That's just the userspace wrappers, right, not the kernel filesystem?
> 2) According to mount.cifs(8), smb3 is the successor to cifs
J
Package: systemd
Version: 256.5-2
Severity: important
Dear Maintainer,
When attempting to upgrade systemd, it fails with the following error
message:
x@splendid:~$ sudo apt install --fix-broken
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 91
3 not fully installed or remo
On Sun, Sep 01, 2024 at 09:54:48AM +, Bjarni Ingi Gislason wrote:
> General remarks and further material (declared as a "diff" file) are in the
> attachments.
I don't think I understand; what are all these changes about?
(Surely not all of them are about trailing whitespace?)
What is this at
Ahoj ,
Som Harris Bunbard, medzinárodný advokát, ktorý bol v kontakte s vaším
príbuzným, krajanom a bratom Jozefom Rehákovou. Prostredníctvom našich
rozhovorov som získal cenné informácie o jeho majetku, podnikaní a finančnom
majetku. Ako jeho zákonný zástupca mám k dispozícii kópie jeho záve
Package: snowflake-proxy
Version: 2.5.1-1+b3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situatio
I installed the snowflake-proxy package, and decided to make sure that it was
running as an unprivilege
Package: gdm-settings
Version: 4.4-1
Severity: important
X-Debbugs-Cc: hsu...@bunsenlabs.org
Dear Maintainer,
gdm-settings 4.4-1 in trixie/sid, when clicking "Apply", does not ask for a
root password, so settings are not applied. The package libglib2.0-dev needs to
be installed and should be list
Good morning,
On Sun, 19 May 2024 08:14:44 +0200,
Andreas Metzler wrote:
> that two-line output is generated by gpgv-from-sq which diverts gpgv. I
> think this should fix it:
> diff -NurBbp apt-2.9.3/cmdline/apt-key.in newapt-2.9.3/cmdline/apt-key.in
> --- apt-2.9.3/cmdline/apt-key.in2024-
On Sun, Apr 28, 2024 at 09:35:46AM +0200, Steinar H. Gunderson wrote:
> It would probably be more useful I package v4l2proxy, which has been part
> of bmusb for a while; it would allow “anything” to go use it, although
> with some local setup. I believe Nageru is the only other soft
On Sun, Apr 28, 2024 at 08:22:41AM +0200, Petter Reinholdtsen wrote:
> Here is a patch for bmusb to add Appstream metainfo XML announcing the
> hardware handled by this package.
Thanks for the patch. I assume this is also suitable for upstream?
> I was a bit unsure if it should be
> attached to t
Package: aptitude
Version: 0.8.13-6
Hello, contrary to the message in NEWS:
[2018-07-29]
Version 0.8.11
[...]
- Documentation:
* Change en/README_encoding to use utf-8 as all the other languages,
instead
of iso-8859-1
this problem is not solved.
Within aptitude in tab "Help -> User's M
tream. (Closes: #1066136)
+
+ -- Steinar H. Gunderson Tue, 19 Mar 2024 23:35:19 +0100
+
python-xapian-haystack (2.1.1-1) unstable; urgency=low
[ Debian Janitor ]
diff -Nru python-xapian-haystack-2.1.1/debian/patches/0002-Remove-dependency-on-six.patch python-xapian-haystack-2.1.1/debian/patches
Package: elpa-org
Version: 9.6.10+dfsg-1-c42-bpo-1
Severity: important
X-Debbugs-Cc: none, H.-Dirk Schmitt
The in bug #1033400 reported version problem is repeated again with the emacs
version 1.29 in bookworm-backports and
trixie. This emacs package includes org-mode 9.6.15, but the elpa-org
On Mon, Mar 04, 2024 at 07:34:06PM +0100, Sven Joachim wrote:
> Not really, these arches now default to a 64-bit time_t and therefore
> you get the conflicting types (suseconds_t is a long int,
> __suseconds64_t a long long int). This has nothing to do with implicit
> function declarations.
It's
them.
-jonathan
georges.khaznadar wrote:
> To: Jonathan H N Chin , 1061...@bugs.debian.org
> From: Georges Khaznadar
> Date: Fri, 1 Mar 2024 14:08:08 +0100
> Subject: Re: Bug#1061155: closed by Debian FTP Masters
> (reply to Georges Khaznadar
> ) (Bug#1061155: fixed in cron 3.0pl1-186)
&
Hi, I just received the new package and tried it. Thanks.
It detects unacceptable MAILTO/MAILFROM, but because unacceptable
values will cause an error later, issuing only a warning feels
inadequate to me.
For usability, perhaps it would be better to use check_error().
Currently, warnings could be
addresses.
>
>I suppose that we can sanitize the value of MAILTO, by checking it
>
>with a regular expression derived from RFC 5322 Official Standard
>
>(see [1]https://emailregex.com/), or do you suggest some lighter approach?
>
>Best regards,
the extra space included in the
>
>list of MAILTO addresses.
>
>I suppose that we can sanitize the value of MAILTO, by checking it
>
>with a regular expression derived from RFC 5322 Official Standard
>
>(see [1]https://emailregex.com/), or do you suggest some li
Sorry, my mail server does not seem to have received any email
from debian when you sent your email on 2024-01-21. Was I
supposed to have been automatically Bcc'd?
I disagree that the bug is not grave - I believe it meets the
criterion of data being lost (and was in fact lost by the user).
However
On Wed, Feb 14, 2024 at 12:32:13PM +0200, Jonathan Carter wrote:
>> Fair enough, do you want to do the honor as the maintainer? Or should
>> I change the upload's version number to 24+really1.4.2~git(etc).?
> Since you made the change, I think you should own it.
I don't have the resources to do th
On Wed, Feb 14, 2024 at 11:53:23AM +0200, Jonathan Carter wrote:
> Thanks for the work, although Debian policy requires consensus from
> debian-devel before bumping an epoch:
>
> https://www.debian.org/doc/debian-policy/ch-controlfields.html#version
Fair enough, do you want to do the honor as the
On Tue, Feb 06, 2024 at 11:55:55AM +0200, Faidon Liambotis wrote:
>> Still required.
> I uploaded that last week, currently sitting in NEW.
Now that this is through NEW, I uploaded an NMU to DELAYED/7-day.
I see that this package is in LowThresholdNmu, but given that it
adds an epoch, I'm giving e
John:
Thanks for your notice. Few even remember the debram
package any longer. I don't recall the last time
someone emailed me about it!
Most of what used to be the debram package is obsolete,
except that there is a data file in debram-data I
believe some still find useful. The existing
debram
Package: binaryen
Version: 108-1
Severity: normal
Per Debian Policy 12.1, each program, utility, and function should have
an associated manpage. Currently /usr/bin/wasm-opt is lacking one.
T
--
Real men don't take backups. They put their source on a public FTP-server and
let the world mirror
On Mon, Jan 29, 2024 at 06:42:41PM +0200, Peter Pentchev wrote:
> Hmmm, my understanding might be wrong, but when using dh_makeshlibs
> directly without a symbols file, isn't it going to be a problem if
> a program is built against libzstd 1.5.5 and it uses the new
> ZSTD_CCtx_setFParams() function
Package: libzstd-dev
Version: 1.5.5+dfsg2-2
Severity: normal
Hi,
debian/rules contains
dh_makeshlibs -plibzstd1 -V'libzstd1 (>= 1.5.5)' --add-udeb=libzstd1-udeb
Would it be possible to change it to 1.5.4? I don't see anything between 1.5.4
and 1.5.5 that would mean 1.5.5-built packages wouldn
On Sun, Jan 28, 2024 at 10:06:48PM +0100, Steinar H. Gunderson wrote:
>> - The initramfs scripts attempt to rewrite UUID= _back_ to a
>>single /dev device through probing, and give that to mount. It needs
>>to avoid doing so for (multi-device) bcachefs filesystems,
forward 1061525 https://savannah.gnu.org/bugs/index.php?65151
block 1061525 by 1060256
block 1061525 by 1060411
tags 1061525 + patch
kthxbye
On Thu, Jan 25, 2024 at 10:44:04PM +0100, Steinar H. Gunderson wrote:
> - Likewise, root= on the kernel command line must contain the UUID
>
On Sun, Jan 28, 2024 at 11:06:53AM +0100, Steinar H. Gunderson wrote:
> I'm a bit unsure how this would work; unless you manually set
> rootfstype=bcachefs on the GRUB command line, I think this is autodetected
> from fstype (in klibc-utils), which doesn't understand bcachefs ri
Package: klibc-utils
Version: 2.0.12-1
Severity: normal
Tags: upstream patch
Hi,
fstype should autodetect bcachefs, not the least because bcachefs filesystems
may require other treatment of UUID mounts (#1060411, #1061525). I've attached
a simple patch.
-- System Information:
Debian Release: 12
On Wed, Jan 10, 2024 at 09:34:18PM +0100, antonio wrote:
> The problem is in the file "/usr/share/initramfs-tools/scripts/functions" and
> depends on the "get_fstype" and "resolve_device" functions that cannot locate
> or determine the file system (since bcachefs uses the form
> device:device:devic
On Mon, Jan 08, 2024 at 12:45:35PM +0200, Faidon Liambotis wrote:
> The bcachefs-tools package builds the C portion of the tarball, and not
> the parts written in Rust (under rust-src/). This results in a crippled
> functionality, such as the missing "mount" binary (#1057295).
I took a stab at ena
On Thu, Jan 25, 2024 at 10:44:04PM +0100, Steinar H. Gunderson wrote:
> - The GRUB command line must be rw, not ro; mounting with -o remount,rw
>gives: “bcachefs: bch2_parse_mount_opts() Invalid mount option errors:
>invalid selection”. I don't know if this is an upstre
Package: bcachefs-tools
Version: 24+really1.3.4-2
Severity: normal
I have / as a multi-device bcachefs filesystem (two different SSDs,
with replicas=1). Booting from it was an, well, interesting endeavor :-)
It seems the following must be done in Debian before this Just Works(TM):
- /etc/fstab m
Package: cron
Version: 3.0pl1-182
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation?
1. A user ran "crontab -e"
2. He added the line (note the space):
MAILTO=a...@example.org, b...@example.com
3. He saved and exited
4. No errors
On Wed, Jan 10, 2024 at 11:51:22PM +0100, Manolis Stamatogiannakis wrote:
> But I take this as a good opportunity to learn a bit about io_uring, so
> I'll give it a shot myself. From my first experiments, it appears that the
> code is deadlocking somewhere in IOUringEngine::finish().
Anything else
On Tue, Jan 09, 2024 at 07:34:56PM +0100, Manolis Stamatogiannakis wrote:
> I also gave it a shot reproducing on a RPi Zero 2, but it's either too fast
> (even with cpulimit), or the issue is architecture-specific and does not
> manifest on ARMv7.
Can I claim “this is obviously a kernel bug” and p
On Mon, Jan 08, 2024 at 08:44:25AM +0100, Steinar H. Gunderson wrote:
> Doing so, thanks. I could probably see if Debian has a porterbox where I can
> reproduce this, but I'm not too optimistic (and I don't have a lot of extra
> time to dedicate to this right now, unfortunately)
tag 1060217 + unreproducible
thanks
On Mon, Jan 08, 2024 at 12:01:07AM +0100, Manolis Stamatogiannakis wrote:
> So, feel free to mark this as unreproducible for now.
Doing so, thanks. I could probably see if Debian has a porterbox where I can
reproduce this, but I'm not too optimistic (and I don'
On Sun, Jan 07, 2024 at 08:21:35PM +0200, Manolis Stamatogiannakis wrote:
> I am trying to get plocate to run on an old ARM-based NAS running Debian
> bookworm. Building the database with updatedb works fine, but plocate
> command itself blocks forever without giving any results back.
>
> I attach
On Wed, Nov 30, 2022 at 12:09:56AM +0100, Steinar H. Gunderson wrote:
> Most of this logic is inherited from mlocate's updatedb, though not all.
> It may be fixable or it may not; I'd really need to check. But it really
> sounds like one should be able to stat() something
Source: nv-codec-headers
Version: 12.1.14.0-1
Severity: important
Dear Maintainer,
After I updated FFmpeg to version 7:6.1-5 hardware accelerated encoding
via h264_nvenc stopped working.
FFmpeg reports:
Driver does not support the required nvenc API version. Required: 12.1
Found: 12.0
[1] state
On Mon, Dec 18, 2023 at 04:33:26PM +0100, Chris Hofstaedtler wrote:
> I don't think there is anything you can "ask" about this.
>
> Generally the idea is that in trixie and later, --prefix=/usr really
> means that. Anything that excluded subdirs from ${prefix} should be
> a thing of the past. If t
On Mon, Dec 18, 2023 at 03:28:54PM +0100, Chris Hofstaedtler wrote:
> cubemap 1.5.1-1 introduced a new file into
> /lib/${DEB_HOST_MULTIARCH}. This is diametral to the ongoing
> UsrMerge effort [1].
Can you say something about where I should get libdir from?
Some dpkg invocation?
/* Steinar */
--
My systems are usr-merged, but I'm saddened by the appearance of
vindictiveness in the response to this bug report. Independently of
the reporter's system being usr-unmerged, it's technically incorrect
for the alternatives system to use "/bin/{nc,netcat}" and
"/bin/netcat-traditional" rather than "
On Sat, Dec 02, 2023 at 02:32:03AM +0100, Chris Hofstaedtler wrote:
> thank you for forwarding the Makefile changes from #1056997 to upstream.
> The upstream change works as expected.
>
> However, udev.pc will change udevdir soon. When this happens, bmusb will
> FTBFS. The upstream build system wi
On Mon, Nov 27, 2023 at 06:57:05PM +0100, Chris Hofstaedtler wrote:
> your package ships a udev rules file in /lib/udev/rules.d, and currently
> hard-codes this path. As part of the UsrMerge effort[1], the install
> path for udev rules must and will change soon. To pick up this change
> with a binN
On Mon, Nov 06, 2023 at 07:15:55PM +0100, Alain Knaff wrote:
> But then, shouldn't it keep the shorter path (if both are the root of their
> filesystem)?
There's no heuristic that will work in all cases. What is a “shorter” path
anyway; is /var/spool/tmp shorter or longer than /mnt/tmp-spool-mount
On Mon, Nov 06, 2023 at 06:43:33PM +0100, Alain Knaff wrote:
> Nov 06 18:33:15 hitchhiker updatedb.plocate[98659]: => adding `/home'
> (duplicate of mount point
> `/run/schroot/mount/buster-53c7e4fc-0416-4408-8421-959dc1fdaa1d/home')
So your /home is mounted in two places, and updatedb picks on
On Mon, Nov 06, 2023 at 03:09:48PM +0100, Alain Knaff wrote:
> On 2 separate Debian 12 machines, I'm observing the following issue:
>
> Search for a file that obviously exists returns nothing.
>
> Running updatedb and then locate doesn't fix this.
>
> Removing /var/lib/plocate/plocate.db, and th
On Mon, Nov 06, 2023 at 03:41:50PM +0100, Alain Knaff wrote:
> On the box where plocate.db is currently corrupted, /home is a btrfs.
It it by any chance a subvolume? (If so, known btrfs bug/design issue;
see the updatedb.conf man page.)
/* Steinar */
--
Homepage: https://www.sesse.net/
Source: openssh
Version: 1:9.2p1-2+deb12u1
Severity: wishlist
Hi,
MPTCP support has been available in a pull request against upstream for a while:
https://github.com/openssh/openssh-portable/pull/335
Unfortunately, upstream does not want it because OpenBSD doesn't support MPTCP.
Would it be p
Package: cron
Version: 3.0pl1-176
Severity: normal
Dear Maintainer,
* What led up to the situation?
`crontab -l` has started producing garish yellow output that corrupts
the prompt. There is no documentation in the manpage explaining that
colour is produced in some circumstances (just notes i
Hi.
Same error here.
$ liferea
eglExportDMABUFImageMESA failed
eglExportDMABUFImageMESA failed
eglExportDMABUFImageMESA failed
sys:1: Warning: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
sys:1: Warning: g_uri_is_valid: assertion 'uri_string != NULL' failed
I'm also using the nvidia
On Tue, Sep 26, 2023 at 05:57:03PM +0100, Alastair Sherringham wrote:
> Is a re-assignment to LXC something you do, or I do?
Anyone can do it; you probably know better than me what the package name is.
/* Steinar */
--
Homepage: https://www.sesse.net/
On Tue, Sep 26, 2023 at 04:11:12PM +0100, Alastair Sherringham wrote:
> Yes, probably something somewhere else. Maybe a library plocate uses breaks
> with "PrivateNetwork" on. I do not know enough about the internals of
> containers, namespaces or systemd to know.
No, my point is; I don't see that
On Tue, Sep 26, 2023 at 02:45:43PM +0100, Alastair Sherringham wrote:
> So there seems to be a problem with the systemd "PrivateNetwork" and
> plocate inside an LXC container - which might not surprise due to LXC
> using namespace magic as well.
Hi,
Thanks for tracking this down.
To me, this sou
is available at
http://nginx.com/";>nginx.com.
Thank you for using nginx.
Thanks
Wesley H. Gimenes
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.12-200.fc38.x86_6
Am Samstag, dem 09.09.2023 um 23:38 +0100 schrieb Simon McVittie:
> On Sun, 27 Aug 2023 at 10:56:20 +0200, H.-Dirk Schmitt wrote:
> > Am Sonntag, dem 20.08.2023 um 12:17 +0100 schrieb Simon McVittie:
> > > Please could you try installing the libgjs0g from here:
> > >
If the package is no longer being maintained, maybe it would be better to
remove it completely.
On Mon, Aug 28, 2023 at 10:10:18PM +0200, Alexandre Detiste wrote:
> It was like 1h then we cancelled with ^C.
But normally it runs through cron/systemd, and then it should be fast the
next few times?
/* Steinar */
--
Homepage: https://www.sesse.net/
On Mon, Aug 28, 2023 at 09:37:01PM +0200, Alexandre Detiste wrote:
> Microsoft's "Windows Subsystem for Linux 2" emulator
> is reusing the old/experimental '9p' filesystem
> to mount the Windows filesystems inside then Debian container.
>
> This makes plocate takes forever to index local (/remote
ave installed the update on my machine and will distribute the
update to other maintained machines.
I don't know a simple reproduction of the problem. Sometimes it appears
shortly after login – sometimes it take days.
Best regards and thanks,
H.-Dirk Schmitt
With the bug raised some time ago I am wondering if there is any drive to
get the cfssl package updated. Version 1.2 is rather old and does not offer
support to restrict TLS ciphers etc.
Package: elpa-org
Version: 9.6.7+dfsg-1-c42-bpo-1
Severity: normal
X-Debbugs-Cc: none, H.-Dirk Schmitt
I use a backport from sid/trixie below bookworm.
In difference to the 9.5 version the setting `#+LANGUAGE: de-de` is not working
any more.
The option of the babel LaTeX package is in this case
On Sat, Jul 22, 2023 at 05:44:56PM +0200, Stefano Rivera wrote:
> You don't have any kind of upstream bug tracker, do you?
Unfortunately not :-) Feel free to report bugs here. I've fixed this one in
upstream now, updated Debian package is on its way.
/* Steinar */
--
Homepage: https://www.sesse.
On Sat, Jul 22, 2023 at 03:40:32PM +, stefa...@debian.org wrote:
> Nope, same error with LC_ALL=C.
> Nicolas next to me (also on an AMD system running Debian unstable) hits
> exactly the same bug.
I don't have any AMD machines anymore, unfortunately, only Intel and NVidia.
(Back when I had one
On Sat, Jul 22, 2023 at 04:09:26PM +0200, Stefano Rivera wrote:
> I get this crash on nageru startup (AMD box, VA-API doesn't work, but
> that's another issue).
>
> Rolling back libmovit8 to 1.6.3-5 gets it working again.
This is very weird. It seems there's a truncation somewhere:
> /* 811 */
On Wed, Jul 05, 2023 at 12:41:51PM +0200, Larsen wrote:
> ...and then output the results for all files at once, leading to the same
> behaviour as mlocate while being much faster.
Because you would have to worry about deduplication of the results,
which is nontrivial to do without incurring unboun
On Tue, Jul 04, 2023 at 11:22:15AM +0200, Steinar H. Gunderson wrote:
>> Instead of using this:
>> locate --existing dpkg-dist dpkg-new dpkg-old dpkg-bak ucf-dist ucf-new
>> ucf-old | egrep -v
>> "dpkg-distaddfile|dpkg_dateien_vor_update_|/var/backup/burp|/root/upgra
I experienced the same bug but worked around it by replacing
/usr/share/python3/debpython/interpreter.py with a version from a system
with "python3-minimal/unstable,now 3.11.4-1 amd64" installed.
Here's the diff:
diff -Naur /usr/share/python3/debpython/interpreter.py interpreter.py
--- /usr/share/
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: mloc...@packages.debian.org
Control: affects -1 + src:plocate
Hi,
After plocate 1.1.19-2, the mlocate binary package is no longer built
(it used to be a transitional package built by p
tags 1040300 + wontfix
thanks
On Tue, Jul 04, 2023 at 10:34:34AM +0200, Larsen wrote:
> with the upgrade from Bullseye to Bookworm, mlocate got replaced by
> plocate. This introduced a breaking change as there is no OR-mode anymore
> on which I rely on in scripts and commands. "apt-listchanges" di
Am Donnerstag, dem 22.06.2023 um 18:13 +0100 schrieb Simon McVittie:
> Control: affects -1 gnome-shell-extension-vertical-overview
>
> On Thu, 13 Apr 2023 at 15:27:33 +0200, H.-Dirk Schmitt wrote:
> > After migration to bookworm on 2 different machines the gnome-shell
> > w
On Tue, Jun 27, 2023 at 12:49:53AM +0200, Steinar H. Gunderson wrote:
> The attached patch seems to get us halfway there; screen now combines all of
> them correctly into one cluster. However, it's still split for whatever
> reason; only if I redraw (C-a l) the flag shows up, and the
On Mon, Jun 26, 2023 at 08:04:28PM +0200, Steinar H. Gunderson wrote:
> Is it possible to retrofit these rules? This specific rule would seem to
> hit a lot of modern emoji sequences (the Unicode Consortium seems to prefer
> using such sequences instead of defining new code points where
Package: screen
Version: 4.9.0-4
Severity: normal
Tags: upstream
Hi,
I was trying to figure out why irssi sometimes garbles the display when certain
emoji are involved in the channel topic; after some debugging, it seems the
issue
is with screen, not irssi. To reproduce, start up screen and do (
0005617abf804b8 in main (argc=, argv=) at
> ../plocate.cpp:995
The stack trace seems somewhat misleading, but I wonder perhaps if this is
https://git.sesse.net/?p=plocate;a=commitdiff;h=7f39444852308224240ebfb75e0bf8f39403afa0
Could you check if downgrading liburing helps? (If so, this shouldn't affect
bookworm as far as I understand)
/* Steinar */
--
Homepage: https://www.sesse.net/
+1,10 @@
+nageru (2.2.1-1) unstable; urgency=medium
+
+ * New upstream release.
+* Fixes several crash bugs related to video inputs. (Closes: #1034471)
+
+ -- Steinar H. Gunderson Mon, 17 Apr 2023 18:37:27 +0200
+
nageru (2.2.0-2) unstable; urgency=medium
* Remove ppc64el from futat
Package: nageru
Version: 2.2.0-2
Severity: important
Tags: upstream
How to reproduce:
1. Start Nageru.
2. Connect Larix Broadcaster (or a similar app) to Nageru over SRT.
3. Nageru crashes with a message that dts > pts.
The underlying problem is that Larix defaults to 60 fps
(on phones that s
Package: gnome-shell
Version: 43.3-3
Severity: important
X-Debbugs-Cc: none, H.-Dirk Schmitt
After migration to bookworm on 2 different machines the gnome-shell was frozen
in the last week.
Via SSH – or switching to the good old console – I was able to see that
journald was running with 100
Am Mittwoch, dem 05.04.2023 um 17:21 +0200 schrieb Julian Andres Klode:
> > WARNING:root:could not open file
> > '/etc/apt/sources.list.d/bookworm.security.sources': Unable to
> > parse section data
> > Same for all other sources files in deb822 format.
>
> 23.04.0 is the version I introduced deb8
Package: command-not-found
Version: 23.04.0-1
Severity: normal
X-Debbugs-Cc: none, H.-Dirk Schmitt
After changing the /etc/apt/sources.d/… files from the traditional to the
deb822 format following noisy warning message
are displayed:
WARNING:root:could not open file
'/etc/apt/sources.l
Tags: patch
Here is a patch that hardcode the resources directory.
Description: Hard code the locatation for the resources (XSL,…).
This mitigates the problem if the script is invoked as `/bin/svn2cl`.
In Bookworm – with usrmege – is this the case.
From: H.-Dirk Schmitt
Index: svn2cl-0.14
Package: svn2cl
Version: 0.14-2
Severity: normal
X-Debbugs-Cc: none, H.-Dirk Schmitt
The `--html` option fails on bookworm,
Due to the usrmerge the script is now invoked as `/bin/svn2cl`.
This leads to an error in the determination of the snv2cl.xss file.
The error message is:
/bin/svn2cl: 1
Package: nautilus-scripts-manager
Version: 2.0-1.1
Severity: grave
X-Debbugs-Cc: none, H.-Dirk Schmitt
The package seems to be outdated for bookworm.
/bin/nautilus-scripts-manager:21: PyGIWarning: Pango was imported without
specifying a version first. Use gi.require_version('Pango&#
> I can't duplicate this on a bookworm system. Does it happen for any
> shell script, or some particular ones?
A simple 3-line script doesn't have the problem.
The shell scripts here using a bash library of 5k lines of code.
I just ensured that the problem occurres with this script.
http://svn.c
For myself I have deinstalled elpa-org for the moment.
But this mitigation – or the suggested changing of the load-path –
introducing unnecessary modifications, which will – Murphy's Law – become
persistent.
A „clean solution“ should avoid duplicated distribution of the same
functionality – esp
I also reported the Issue to the upstream project:
https://github.com/flycheck/flycheck/issues/2014
Package: elpa-flycheck
Version: 32~git.20200527.9c435db3-3
Severity: grave
X-Debbugs-Cc: none, H.-Dirk Schmitt
The combination of Emacs28 + elpa-flycheck + shellcheck in *bookworm* spawn
never terminating shellcheck processes.
These are eating up the memory and trigger oom-kill.
**This
1 - 100 of 3470 matches
Mail list logo
