Am Montag, 3. März 2025, 19:05:19 CET schrieben Sie: Hi Matthias, > Am Mo., 3. März 2025 um 13:32 Uhr schrieb Hans <hans.ullr...@loop.de>: > > At first my advice: please try debian-live@lists.debian.org > done!
> 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.ht > ml Usually I start with "sudo lb clean" and then "sudo lb build". > I did te same, but "lb clean --purge" > > Reading state information... Done E: Unable to locate package > > grub-efi-amd64-unsigned E: An unexpected failure occurred, exiting... > > You had replaced bookworm with trixie? Apparently not everywhere. > grub-efi-amd64-unsigned is in trixie/testing, but not and has never > been in bookworm. No I did not! As I found out, that the package "grub-efi-amd64-unsigned" is used in trixie, I changed bookworm to trixie, not the other way round. > Is seems to me your repos don't include bookworm/main. > To check the availabilty and the versions of packages in the repos of > my sources.list I do "apt-cache policy ...": > > $ sudo apt update No, my repos are bookworm/main contrib non-free and non-free-firmware, jus as usual. > > $ LANG=C apt-cache policy grub-efi-amd64-signed grub-common > grub-efi-amd64-signed: > Installed: 1+2.06+13+deb12u1 > Candidate: 1+2.06+13+deb12u1 > Version table: > *** 1+2.06+13+deb12u1 500 > 500 http://deb.debian.org/debian bookworm/main amd64 Packages > 500 https://security.debian.org/debian-security > bookworm-security/main amd64 Packages > 100 /var/lib/dpkg/status > grub-common: > Installed: 2.06-13+deb12u1 > Candidate: 2.06-13+deb12u1 > Version table: > *** 2.06-13+deb12u1 500 > 500 http://deb.debian.org/debian bookworm/main amd64 Packages > 500 https://security.debian.org/debian-security > bookworm-security/main amd64 Packages > 100 /var/lib/dpkg/status > > HTH Of course apt will not be able to find the package! Because it is no ore in the repo. It WAS in the repo, but now it is gone and of course deleted in the dependencies of the packages. But (IMO), it is somewhere forgotton to delete. This is, what I think. If I know, in which package, I could fix it by myself, but I do not and I hoped, the maintainers know. They should, I imagine.... Hans > Matthias
