Hi Hans,
maybe this caused your problem:
Nov 06, 2024
Commit 30d39f81 "lb config: --distribution defaults to testing"
https://salsa.debian.org/live-team/live-build/-/commit/30d39f812e41eb81928a0fe1f3a4f686eb30dfa9
Bye
Matthias
Hi Hans,
which version of lb are you using?
I am using the version from the Debian package live-build from "bookworm":
$ lb --version
20230502
The first thing I learned with that version from "bookworm" was that I
had to set all config directives regarding the distribution to
"bookworm" bec
Am Mo., 3. März 2025 um 13:32 Uhr schrieb Hans :
At first my advice: please try debian-l...@lists.debian.org
My way to build debian live is not with git but according to
https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
Usually I start with "sudo lb clean" and then
On 2025-03-03 David Wright wrote:
> On Sun 02 Mar 2025 at 20:32:24 (+0100), Hans wrote:
>
> > The only thing I got, was the message from "lb build", that a ncessary
> > package
> > could not be downloaded. And the necessary package was named
> > "grub-efi-amd64-
> > unsigned".
>
> That suggests t
Sorry for my bad grammar:
Maybe you *had* put another package from trixie/testing into
packages.chroot?
PS.
>
> Hans, maybe you put another package from trixie/testing into
> packages.chroot, which depends directly or indirectly on
> grub-efi-amd64-unsigned?
>
> Possible packages in testing/trixie
PS.
Hans, maybe you put another package from trixie/testing into
packages.chroot, which depends directly or indirectly on
grub-efi-amd64-unsigned?
Possible packages in testing/trixie main are:
- grub-efi-amd64-bin depends on grub-efi-amd64-unsigned
- grub-efi-amd64 depends on grub-efi-amd64-bin
-
> Dear maintainers,
>
> it is no more possible to build debian-live/stable (bookworm). The reason is a
> missing package in bookworm: grub-efi-amd64-unsigned.
>
> I rechecked and yes, it is no more in bookworm.
Hi Hans,
I'm sorry, but here are debian users, not maintainers.
And grub-efi-amd64-un
Hi Gene,
please check explanations in this blog:
https://www.dwarmstrong.org/zram-linuxmint/
HTH
Matthias
gene heskett schrieb am Sa., 30. Sept. 2023, 19:51:
> On 9/30/23 13:28, Matthias Böttcher wrote:
> > sudo dphys-swapfile swapoff
> > sudo systemctl stop dphys-swapfile.s
sudo dphys-swapfile swapoff
sudo systemctl stop dphys-swapfile.service
sudo systemctl disable dphys-swapfile.service
Am Fr., 13. Jan. 2023 um 03:45 Uhr schrieb John Conover :
>
> I'm installing an SSD replacement for an HD in a small 24/7 mail
> server.
>
> I would appreciate suggestions for the most reliable way to do
> fstrim(8). Reliability is more important than speed, and the machine
> will require a swap pa
> How do I tell the card that the free space in the VG really is free?
blkdiscard
Am So., 14. Aug. 2022 um 16:42 Uhr schrieb Reco :
> whois, geoiplookup, even https://bgp.he.net .
> Whatever works, basically.
> Last one is my favorite as it shows all IP blocks assigned to AS.
> Really helpful with spammer nests such as outlook.com (AS8075) or
> DigitalOcean (AS14061).
>
> > Is
Am So., 14. Aug. 2022 um 09:51 Uhr schrieb Reco :
> Personally I don't use fail2ban for sshd. Because why bother with
> userspace (written in python too, yuck) if the kernel does the same job?
> I.e. block M$ AS, China Telecom AS and maybe add Eastern Europe to the
> mix, and you've just reduced t
mk-en/2019-September/028676.html
Matthias
Am Sa., 27. Juli 2019 um 11:59 Uhr schrieb Matthias Böttcher
:
>
> On Fri, Jul 26, 2019 at 10:12:20PM +0300, Reco wrote:
> > On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote:
>
> [...]
>
> > > and additionally I s
On Fri, Jul 26, 2019 at 10:12:20PM +0300, Reco wrote:
> On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote:
[...]
> > and additionally I stopped the socket for the Check_MK agent:
> >
> > sudo systemctl stop check_mk.socket
>
> I do not know t
Reco :
>
> Hi.
>
> On Wed, Jul 24, 2019 at 06:54:42PM +0200, Matthias Böttcher wrote:
> > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> > 307534 304741 99%0,20K 16186 19 64744K vm_area_struct
> > 14280 14274 99%3,
Shahryar Afifi :
>
> What happens when you run sync in terminal?
sync exits immediately and slabtop gives the same output like before sync.
what is eating up my memory in SUnreclaim (slab unreclaimable)?
Thanks in advance
Matthias Böttcher
18 matches
Mail list logo