Package: cloud.debian.org
Version: debian-11-generic-amd64-20230124-1270.qcow2
In the cloud-init “network-config” file (using “Networking Config Version 2”)
when using static network addressing, it is possible to define static routes
under an interface.
These routes can be either IPv4 or IPv6 r
On Wed, 22 Jan 2020 21:18:08 + Paul Szabo wrote:
> It now seems to me that the issue is with MIT-SHM, that the code to
> detect whether MIT-SHM is working (so whether to enable) is "broken".
> Using the workaround below, fudging MIT-SHM to report as not present:
>
> cc -shared -o XlibNoSHM.s
Package: src:linux
Version: 4.9.144-3.1
Severity: important
Dear Maintainer,
After updating the kernel 4 days ago to 4.9.144-3.1 from 4.9.130-2, I
have had two instances in the last 24 hours where a BTRFS filesystem has
failed and started reporting "No space left on device" for any attempt to
wri
Is there any chance of a way forward on this?
It seems that the drivedb.h updates in the 'smartmontools' package aren't just
slow, but non-existent - the version that ships with Debian 9.7 dates from a
year *before* the release of Debian 9.0
If there is no script to perform an update in the pac
Hi,
> -Original Message-
>
> Hi Michael,
>
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >
> > After this, there was a file that was errored on the filesystem (as
> > reported by 'btrfs check'), and it seems BTRFS does
Package: src:linux
Version: 4.9.110-3+deb9u4
Severity: important
Dear Maintainer,
While extracting files over NFS into a BTRFS file system a kernel bug
report was triggered. I don't believe the bug is related to the fact
that the access was over NFS, but should declare that just in case.
After t
Package: psmisc
Version: 22.21-2.1+b2
Severity: normal
Dear Maintainer,
It appears the version of the psmisc package in Debian 9 suffers from
the issue described here:
https://www.spinics.net/lists/linux-btrfs/msg45058.html
When trying to umount a btrfs filesystem it was reporting as busy.
Runn
Package: simple-cdd
Version: 0.6.5
Severity: important
Dear Maintainer,
Hi,
When running 'build-simple-cdd' with the '--dist' option on Debian
Stretch, the resulting ISO file has the version number of the host
Debian system, not the built system. I haven't yet verified whether the
built CD is a
Is there any chance that this bug will be fixed in Jessie at some point? (It
seems to be already resolved in the autofs version in Stretch)
It looks like the Fedora thread listed suggests there is a fix there for the
issue, but unfortunately not an explicit patch.
It seems the change between "a
9 matches
Mail list logo
