Am Mittwoch, 5. März 2025, 18:53:07 CET schrieb Matthias Böttcher:
> 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/30d39f812e41eb81928a0
> fe1f3a4f686eb30dfa
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
I believe, the problem is been caused by wrong informations
in /var/lib/dpkg/info from the native installed debian/stable, where I qant to
build it.
ALL *.postinst files are pointing to trixie and not to bookworm (although, the
installed packages are all from bookworm).
So, with the view on t
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
On Mon 03 Mar 2025 at 22:24:57 (+0100), Hans wrote:
> So, I rechecked.
>
> After purging everything and building again, I checked the chroot. And what
> did I find?
>
> A lot of entries with "trixie" in */chroot/var/lib/dpkg/info which are mostly
> "*.postinst" files.
>
> Where are they comin
So, I rechecked.
After purging everything and building again, I checked the chroot. And what
did I find?
A lot of entries with "trixie" in */chroot/var/lib/dpkg/info which are mostly
"*.postinst" files.
Where are they coming from? These are all from installed packages, but all
packages shoul
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 :
>
> At first my advice: please try debian-l...@lists.debian.org
>
done!
> My way to build debian live is not with git but according to
>
> https://live-team.pages.debian.net/li
On Mon, 3 Mar 2025 09:40:35 -0500
Jeffrey Walton wrote:
> On Mon, Mar 3, 2025 at 7:32 AM Hans wrote:
> >
> > I believe, that one of the following packages needs the missing
> > package. Please see the last output (sorry, it is bit longer):
>
> Something looks a bit off:
>
> $ apt-cache r
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 Mon, Mar 3, 2025 at 7:32 AM Hans wrote:
>
> I believe, that one of the following packages needs the missing package.
> Please see the last output (sorry, it is bit longer):
Something looks a bit off:
$ apt-cache rdepends grub-efi-amd64-unsigned
E: No packages found
> __
So, tried agian without the */packages-lists/mylist.list.chroot and without
any added packages at */packages.chroot = same issue again.
This excludes the cause by any changes from me or by any added packages.
It is proven, the issue is in the live-build environment itself.
Hans
Good idea, Matthias, so I rechecked. There are only two packages in
packages.chroot in the last build I sent the output from.
These were "kali-undercover_2023" and "rustdesk-1.3.7". In both I checked the
"control" file, but none of them pointed to or named "grub-efi-amd64-*".
But to clear thi
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
Hello again,
I believe, that one of the following packages needs the missing package. Please
see the last
output (sorry, it is bit longer):
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
dmsetu
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 to me (with no experience of this) that its a script
Hi David,
yes, that is, what I meant.
But now, I am a litle bit lsot. How shall I get, which package depends grub-
efi-amd64-unsigned? I thought, you might know.
The only thing I got, was the message from "lb build", that a ncessary package
could not be downloaded. And the necessary package wa
On Sun 02 Mar 2025 at 17:44:37 (+0100), Hans wrote:
> So my idea was just to write to the live-file-maintainers, to ask them, to
> remove the dependency of the missing package in theire configurations or
> point
> it to another package, i.E. grub-efi-amd64-signed.
Presumably you meant "remove
Am Sonntag, 2. März 2025, 13:37:20 CET schrieb Matthias Böttcher:
> PS.
>
> Hans, maybe you put another package from trixie/testing into
> packages.chroot, which depends directly or indirectly on
> grub-efi-amd64-unsigned?
>
Hi Mathias,
I already had this idea, too, but putting it from testing w
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
21 matches
Mail list logo
