Your message dated Tue, 25 Feb 2025 10:22:41 +
with message-id
and subject line Bug#1031903: fixed in live-build 1:20250225
has caused the Debian Bug report #1031903,
regarding live-build: add dracut support
to be marked as done.
This means that you claim that the problem has been dealt with
Hello Anthael,
On 20/01/2025 16:57, Anthael H. wrote:
I wonder if it's possible to build a dvd with live build with multiple
targets.
I'm trying to build a dvd with 2 entries :
- server ( without graphical desktop )
- workstation ( with a minimal gnome desktop )
If I unde
Hi,
I wonder if it's possible to build a dvd with live build with multiple
targets.
I'm trying to build a dvd with 2 entries :
- server ( without graphical desktop )
- workstation ( with a minimal gnome desktop )
>From the isolinux I have declared a variable target to define the s
Hello Adam,
On 15/01/2025 22:09, Adam McManus wrote:
I'm attempting to create a live-build USB with custom Secure Boot keys
and failing.
I have a config/hooks/live/1000-sign-boot.hook.binary file that is
signing all *.efi files (verified when booting the live system without
secure
I'm attempting to create a live-build USB with custom Secure Boot keys and
failing.
I have a config/hooks/live/1000-sign-boot.hook.binary file that is signing
all *.efi files (verified when booting the live system without secure boot
enabled), and it is also signing live/vmlinuz-*-amd64. Ho
Hello Aaron,
On 15/01/2025 03:52, Aaron Rainbolt wrote:
If you're using live-build, I'd highly recommend setting the various
`--mirror` and `--parent-mirror` settings in your `lb config` commands
explicitly, specifying HTTPS repos for each of those settings. It's not
a perfect s
g the details, so I've made my original email to the Debian
Security Team public as a GitHub gist (so as to not flood the BTS with
a massive comment). The PoC instructions are
here: https://gist.github.com/ArrayBolt3/99d1296a6d82b5a6f2453943eaf85520
If you're using live-build, I
Ah, ok. So if I run this in a CI/CD pipeline I should prefer to put the
variable providing the --debug flag where lb build is called and not in the
auto/config file.
Thank you!
Hello Emil,
On 08/01/2025 15:27, Södergren Emil wrote:
> I am running a live-build where I run the comm
Hello Emil,
On 08/01/2025 15:27, Södergren Emil wrote:
I am running a live-build where I run the command:
lb config noauto … lots of parameters … --debug
...
> Is > there a better way to actually set the _DEBUG printing from
configuration?
Indeed there is.
It's documented i
Hi,
I am running a live-build where I run the command:
lb config noauto ... lots of parameters ... --debug
I see that the --debug sets the variable _DEBUG="true" in config/common, but
that line is commented out. As with the _VERBOSE="true" and some others. I have
inserted
Hi,
I wonder if it's possible to build a dvd with live build with multiple
targets.
I'm trying to build a dvd with 3 entries :
- live
- minimal ( without graphical desktop )
- workstation ( with a minimal gnome desktop )
>From the isolinux I have declared a variable target
Package: live-build
Version: 1:20240810
Severity: minor
X-Debbugs-Cc: adrela...@kicksecure.com
live-build/share/hooks/normal/1010-enable-cryptsetup.hook.chroot
currently adds the line 'CRYPTSETUP=y' to
/etc/cryptsetup-initramfs/conf-hook during the live system build
process. This conf
issues
https://salsa.debian.org/rclobus-guest/live-build/-/tree/rclobus/local_debs?ref_type=heads
It is a very rough draught, and I've encountered several issues, which
I'll try to tackle over time.
I did not want to make this a merge request yet, I'll do several --force
comm
On Fri, 15 Nov 2024 08:39:19 +0100
Roland Clobus wrote:
> Before delving deeper into the code, could you post a minimal
> configuration that shows the behaviour? Perhaps there are other ways
> to achieve the same goal.
Hopefully, yes. I haven't lost track of this, but I haven't yet gotten
a w
Package: debian-live
Severity: grave
Tags: a11y upstream
Justification: renders package unusable
X-Debbugs-Cc: usergr...@users.osdn.me
Dear Maintainer,
I made a Live respin using Debian Live Sysyem for testing,
and it ended up successfully. But Kernel panick occured at
system boot when I used its
Processing control commands:
> tags 1087470 +moreinfo
Bug #1087470 [live-build] live-build: Binary stage runs apt commands, breaking
certain image build workflows
Added tag(s) moreinfo.
--
1087470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087470
Debian Bug Tracking System
Contact
Control: tags 1087470 +moreinfo
Hello Aaron,
On 14/11/2024 02:35, Aaron Rainbolt wrote:
I'm using live-build to build ISO images of Kicksecure, a Debian derivative.
Currently, we use apt-cacher-ng to cache package downloads for speed's sake.
We also install special apt sources.lis
Package: live-build
Version: 1:20240810
Severity: wishlist
X-Debbugs-Cc: adrela...@kicksecure.com
I'm using live-build to build ISO images of Kicksecure, a Debian derivative.
Currently, we use apt-cacher-ng to cache package downloads for speed's sake.
We also install special apt so
On Wed, 6 Nov 2024 at 12:07, Roland Clobus wrote:
> On 06/11/2024 11:26, Leandro Doctors wrote:
> > Q2: Is there a way to access the last successful build of the live images?
>
> Yes, you can ...
> * ... use your previously downloaded file, if you still have that
> * ... rebuild them using a snap
Control: severity 1086807 normal
Control: retitle 1086807 Weekly images 2024-11-04 not generated
Hello Leandro,
On 06/11/2024 11:26, Leandro Doctors wrote:
When opening https://cdimage.debian.org/images/weekly-live-builds/amd64/iso-
hybrid/,
instead of finding the weekly live images I find log
Processing control commands:
> severity 1086807 normal
Bug #1086807 [live-build] live-build: weekly live testing images not generated
Severity set to 'normal' from 'serious'
> retitle 1086807 Weekly images 2024-11-04 not generated
Bug #1086807 [live-build] live-build:
Package: live-build
Version: 2024.11.04
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: ldoct...@gmail.com
Dear Maintainer,
When opening https://cdimage.debian.org/images/weekly-live-builds/amd64/iso-
hybrid/,
instead of finding the weekly live images I find
Package: live-build
Version: 1:20240810
Severity: normal
Tags: patch
Note to self:
See #1084791 and
https://salsa.debian.org/live-team/live-build/-/merge_requests/372
As soon as the firmware package issue has been resolved, the workaround
from MR372 must be reverted again.
Having the
Processing control commands:
> tag -1 pending
Bug #1031903 [live-build] live-build: add dracut support
Added tag(s) pending.
--
1031903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: live-build
Version: 1:20240810
Severity: normal
X-Debbugs-Cc: adrela...@kicksecure.com
Expected result:
I should be able to specify arbitrary environment variables in
config/environment.chroot and have them be picked up by commands that
run within the chroot.
Actual result:
If I specify
Using live-build to create a custom cd all of a sudden not allowing including
backports on auto/config. (The worked fine the last time I built it, on
2024-03-08). The problem can be replicated with a bare-bones build with an
empty config directory and a minimal auto/config. I am copying below
> an ISO I'm building. I assume all of the packages are being pulled in
> > for a similar reason, so right now I just want to focus on one
> > particular package. My live-build config is located
> > at https://github.com/ArrayBolt3/kicksecure-live-build. I am usi
r a similar reason, so right now I just want to focus on one
> particular package. My live-build config is located
> at https://github.com/ArrayBolt3/kicksecure-live-build. I am using my
> own fork of live-build, however none of the code modifications I have
> made or integrated from other
e. My live-build config is located
at https://github.com/ArrayBolt3/kicksecure-live-build. I am using my
own fork of live-build, however none of the code modifications I have
made or integrated from other sources seem likely to cause this
particular issue.
Some notable parts of my config:
* I'm
Processing control commands:
> tag -1 pending
Bug #1069045 [live-build] Support for propose-updates package archives
Added tag(s) pending.
--
1069045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
system I found the GNOME live shiped fcitx and KDE System
Settings.
What I'm curious about are, 1. Is there any reason for live system to choose
fcitx, not fcitx5?
Fcitx is in maintenance mode and is not recommended for further utilization. 2.
Why GNOME live build
should ship KDE System Settin
Can you please join the liveid conversation where I'm proposing a change
to live-build that would probably fix your issue?
There's the long live-boot Merge Request discussion at:
https://salsa.debian.org/live-team/live-boot/-/merge_requests/52 .
Then there's the sister Merge
Package: live-build
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
Current Live image (
https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-kde.iso
)
contains file /EFI/boot/grubx64.efi , which is binary identical to the file
/usr/lib/grub
Hello Hans, list,
On 06/09/2024 12:13, Hans-J. Ullrich wrote:
I discovered, that live-build is still depending on bullseye. All controlling
files got the entry of bullseye, whilst it should be now bookworm.
Although it is not a real bug, a build is always crashing due to missing
packages or
Package: live-build
Severity: normal
Dear Maintainer,
I discovered, that live-build is still depending on bullseye. All controlling
files got the entry of bullseye, whilst it should be now bookworm.
Although it is not a real bug, a build is always crashing due to missing
packages or wrong
Your message dated Wed, 4 Sep 2024 10:16:08 +0200
with message-id
and subject line A new version was released
has caused the Debian Bug report #1068753,
regarding live-build: Should not install raspi-firmware on x86_64
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 4 Sep 2024 10:15:03 +0200
with message-id <6e5c1a74-8bc6-4418-b69e-09ccb14e2...@rclobus.nl>
and subject line A new version was released
has caused the Debian Bug report #1041261,
regarding live-build fails with debian 12.1 becuase it expects linux-firmware
to be mar
Your message dated Wed, 4 Sep 2024 10:15:03 +0200
with message-id <6e5c1a74-8bc6-4418-b69e-09ccb14e2...@rclobus.nl>
and subject line A new version was released
has caused the Debian Bug report #1041261,
regarding live-build does not build debian bookworm images
to be marked as done.
This
Your message dated Wed, 4 Sep 2024 10:13:55 +0200
with message-id
and subject line A new version was released
has caused the Debian Bug report #1078442,
regarding live-build: zsync removal from testing prevents building images based
on trixie
to be marked as done.
This means that you claim that
Your message dated Wed, 4 Sep 2024 10:12:55 +0200
with message-id <5806a198-f5eb-41ef-86bf-bffec1cff...@rclobus.nl>
and subject line A new version was released
has caused the Debian Bug report #1076500,
regarding live-build: Can't handle spaces in file names
to be marked as done.
This
Thank you, I think this is a good compromise.
Control: tags 1078442 +pending
Hello all,
I just pushed a MR on Salsa [1], which got merged already. (Thanks bluca :-)
Said MR changes the default value for `--zsync` to false.
Given that:
a) zsync was orphaned 2021-09-19 #994648;
b) zsync FTBFS with GCC-14 #1075710;
c) zsync was only available
Processing control commands:
> tags 1078442 +pending
Bug #1078442 [live-build] live-build: zsync removal from testing prevents
building images based on trixie
Added tag(s) pending.
--
1078442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078442
Debian Bug Tracking System
Contact
I wrote, the patch
> solves the build failure by restoring its behavior to what it was pre-gcc-14.
If that was good enough in the past, then it should be good enough until the
live-build developers find an alternative tool to provide the binary_zsync
build step. I do agree this would be the be
n a struct, in a C code I don't know and that is full of
pointer arithmetic, doesn't seem a good idea).
I suppose the best solution would be that live-build replace zsync with
something else, or do without it altogether.
Note that zsync has only one reverse dependency, quickemu.
-based live distribution featuring a graphical
wizard for rescuing broken GNU/Linux and Windows installations and
boot loaders. ( https://www.supergrubdisk.org/rescatux/ ).
Rescatux is built thanks to live-build onto a CDROM that supports:
- 686 kernel
686 is getting less support for trixie
Package: live-build
Version: 1:20240810
Severity: important
Tags: patch
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
The recent auto-removal of zsync from testing
(https://tracker.debian.org/news/1553820/zsync-removed-from-testing/) prevents
live-build from building images based on
Your message dated Sat, 10 Aug 2024 00:19:20 +
with message-id
and subject line Bug#1032408: fixed in live-build 1:20240810
has caused the Debian Bug report #1032408,
regarding live-build fails ln: failed to create symbolic link '/etc/mtab': File
exists caused by --chroot-filesyst
Your message dated Sat, 10 Aug 2024 00:19:20 +
with message-id
and subject line Bug#1069349: fixed in live-build 1:20240810
has caused the Debian Bug report #1069349,
regarding live-build: Regression in d14306a7 leading to build failures
to be marked as done.
This means that you claim that
Your message dated Sat, 10 Aug 2024 00:19:20 +
with message-id
and subject line Bug#1032408: fixed in live-build 1:20240810
has caused the Debian Bug report #1032408,
regarding live-build of a bookworm system fails at build time
to be marked as done.
This means that you claim that the
Your message dated Sat, 10 Aug 2024 00:19:20 +
with message-id
and subject line Bug#1032408: fixed in live-build 1:20240810
has caused the Debian Bug report #1032408,
regarding live-build: live build fails for bookworm release making ext4
filesystem
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #1064408 [live-build] [PATCH] duplicate aliased diversions for DEP17
Ignoring request to alter tags of bug #1064408 to the same tags previously set
--
1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408
Debian Bug Tracking Sys
live-build 1:20230502 is marked for autoremoval from testing on 2024-09-06
It is affected by these RC bugs:
1064408: live-build: [PATCH] duplicate aliased diversions for DEP17
https://bugs.debian.org/1064408
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob
wizard for rescuing broken GNU/Linux and Windows installations and boot
loaders. ( https://www.supergrubdisk.org/rescatux/ ).
Rescatux is built thanks to live-build onto a CDROM that supports:
- 686 kernel
686 is getting less support for trixie, at least the d-i will not be
made available any
Processing commands for cont...@bugs.debian.org:
> reassign 1076500 live-build
Bug #1076500 [firmware-brcm80211] firmware-brcm80211: Contains .txt files with
a space
Bug reassigned from package 'firmware-brcm80211' to 'live-build'.
No longer marked as found in versions fi
built thanks to live-build onto a CDROM that supports:
- 686 kernel
- amd64 kernel
- IA32 UEFI
- x64 UEFI
- Media with SELinux Filesystem so that the Live Media can be boot in
SELinux Permissive mode.
- Automatic Arch Detection for Syslinux
- Automatic Arch Detection for Grub2 (This is already in
Processing control commands:
> tag -1 pending
Bug #1069349 [live-build] live-build: Regression in d14306a7 leading to build
failures
Added tag(s) pending.
--
1069349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069349
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
On 02.05.24 17:30, Roland Clobus wrote:
I'll prepare a proper fix that detects whether the directory is present.
Perfect, thanks!
On 02/05/2024 12:14, Daniel Reichelt wrote:
Hi Roland,
> On 20/04/2024 13:32, Daniel Reichelt wrote:
> What are you doing that makes the directory 'config/includes.binary'
> disappear?
> If I use 'lb config --distribution sid', the directory is created (but
> empty) and there will be no erro
Hi Roland,
> On 20/04/2024 13:32, Daniel Reichelt wrote:
> What are you doing that makes the directory 'config/includes.binary'
> disappear?
> If I use 'lb config --distribution sid', the directory is created (but
> empty) and there will be no error message.
I'm keeping my (final, i.e. `lb config
Hello Daniel,
On 20/04/2024 13:32, Daniel Reichelt wrote:
Package: live-build
Version: git-master
Severity: normal
Hi all,
I recently built a .deb of the current master and noticed build failures like
this:
---8<--
P: Begin copying binary includes...
/usr/lib/live/bu
Your message dated Sat, 20 Apr 2024 21:10:51 +
with message-id
and subject line Bug#1069349: fixed in ffmpeg 7:6.1.1-4
has caused the Debian Bug report #1069349,
regarding live-build: Regression in d14306a7 leading to build failures
to be marked as done.
This means that you claim that the
Package: live-build
Version: git-master
Severity: normal
Hi all,
I recently built a .deb of the current master and noticed build failures like
this:
---8<--
P: Begin copying binary includes...
/usr/lib/live/build/binary_includes: 36: cd: can't cd to config/includes.bina
Package: live-build
Version: 1:20230502
Severity: important
X-Debbugs-Cc: mmnegre...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
Roland Clobus writes:
> Control: severity -1 normal
> Control: tags -1 +pending
> Control: tags 1065640 +pending
> Control: merge -1 1065640
>
> Hello Vasudev Kamath,
>
>> Built the live image for bookworm using live build (on bookworm as well as
>> from uns
Processing control commands:
> severity -1 normal
Bug #1068753 [live-build] live-build: Should not install raspi-firmware on
x86_64
Severity set to 'normal' from 'important'
> tags -1 +pending
Bug #1068753 [live-build] live-build: Should not install raspi-firmware on
x
Control: severity -1 normal
Control: tags -1 +pending
Control: tags 1065640 +pending
Control: merge -1 1065640
Hello Vasudev Kamath,
Built the live image for bookworm using live build (on bookworm as well as from
unstable).
Note that the version which is on bookworm will not be updated
Package: live-build
Version: 1:20230502
Severity: important
Dear Maintainer,
Built the live image for bookworm using live build (on bookworm as well as from
unstable). The built
image incldes raspi-firmware which is not meant for x86_64. I was installing
some dkms module which
will regenerate
Hello lists,
here is the 24th update of the status for reproducible live-build ISO
images [1].
Single line summary: 79.5% reproducible live images (yup, lower than
last time; see below for the calculation)
Reproducible status:
* All major desktops build reproducibly with bullseye, bookworm
a drop-in
replacement for debootstrap.
Hence we have patched live-build and created a MR:
https://salsa.debian.org/live-team/live-build/-/merge_requests/343
Comments are welcome.
Steven
--
Steven Shiau
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5 356C
Hello lists,
here is the 23th update of the status for reproducible live-build ISO
images [1].
Single line summary: 97.7% reproducible live images
Reproducible status:
* All major desktops build reproducibly with bullseye, bookworm, trixie
and sid ...
** ... provided they are built for a
Hey, 6 years past, on bullseye this time, and the same bug remain.
No way to preseed the keyboard selection, only way I found is to skip it
using "keymap=fr". Doing so will also skip any keyboard selection. So I
needed to set it manually after the installation was done using
localectl. It didn
Hi!
This simple patch fixes the issue. I tried opening an MR on Salsa but it
seems Salsa has some issues currently (going to the merge request page
after the push leads to an error 500-something).
Cheers,
Thomas Goirand (zigo)
diff --git a/scripts/build/binary_netboot b/scripts/build/binary
esystem.packages-remove' shows where
> the package management system has been circumvented.
I get that this is totally up to you. However, if people use `live-build` in
the same manner as I do, they may face this issue and may be dissatisfied. I
came up with a "tempfix" on my en
not be installed per default, because the name
'1password' is not a package name that is known.
I then ran live-build with '--interactive=true' (which has a similar
effect as writing a hook for config/hooks/normal) and installed the
package with 'dpkg -i 1password-lat
Hmm. My first reply didn't make it, resending...
Forwarded Message
Subject: Re: Bug#1062641: live-build Removes User Packages Installed via
Hooks
Date: Sun, 4 Feb 2024 17:41:42 +0100
From: Roland Clobus
To: Arszilla , 1062...@bugs.debian.org
Hello Arszilla,
On 02/02
x27;m certain that there is a more secure way, that ensures that only
the package called '1password' will come from this repository.
The bug report was based on a kali version of live-build, so I assume
you know better than me how to do so.
Please add such command to the bug report, so I
Package: live-build
Version: 1:20230502+kali3
When users install `.deb` packages that are not available in Debian via a
`.chroot` hook (such as `1password`), the `./live/filesystem.packages-remove`
file in the generated ISO uninstalls the packages installed via `.chroot` after
the system is
Hello lists,
here is the 22th update of the status for reproducible live-build ISO
images [1].
Single line summary: 97.7% reproducible live images
Reproducible status:
* All major desktops build reproducibly with bullseye, bookworm, trixie
and sid ...
** ... provided they are built for a
Package: live-build
Version: 1:20231215
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: deb...@bobrosbag.nl
Dear Maintainer,
When installing more than two kernels I get an error:
basename: extra operand ‘chroot/boot/vmlinuz-6.6.7-1-liquorix-amd64’
Try 'basename --help' for more i
On 04/01/2024 14:58, Roland Clobus wrote:
Single line summary: Very near the finishing line
Reproducible status:
* All major desktops build reproducibly with bullseye, bookworm, trixie
and sid ...
** ... provided they are built for a second time within the same DAK run
(i.e. 6 hours)
* Rebuild
Hello lists,
here is the 21th update of the status for reproducible live-build ISO
images [1].
Single line summary: Very near the finishing line
The best wishes for 2024, may this year be the year of the reproducible
live images for Debian :-)
Reproducible status:
* All major desktops
Package: live-build
Severity: normal
Hi. This is a feature request. Can we please include net-tools in the
set of packages we ship with debian-live? It is small, and would make
many people's lives easier. I personally use this as a rescue disk, and
configuring the network is a common need for
Package: live-build
Version: 1:20230502
Severity: important
Hi,
Under Bookworm, when doing lb build after lb config this way:
lb config -b netboot [...]
lb build fails to create the tftpboot folder, which it cleans when starting.
As a result, lb build just fails with "tftpboot: no such fi
in
> a loop with a bit of sleep, until it finally succeeds.
I'm running live-build for some time now on a UEFI-booted machine
(previously I used BIOS boot) without issues.
I think that the fix is applied to the git version, see
https://salsa.debian.org/live-team/live-build/-/merge_r
Package: live-build
Version: 1:20230502
Followup-For: Bug #1053457
X-Debbugs-Cc: witold.bary...@gmail.com
Also had this issue for some time (maybe 2-3 months) on my amd64
machine.
But I am not so sure it is due to efivars, at least not only.
Instrumented chroot_sysfs with mount | grep chroot
Your message dated Wed, 8 Nov 2023 21:58:23 +0100
with message-id
and subject line Debootstrap works in buster
has caused the Debian Bug report #919659,
regarding live-build: building in docker fails with mounting /proc unmount /sys
to be marked as done.
This means that you claim that the
On 2023-10-04 03:10, Emanuele Rocca wrote:
> P: Begin unmounting /sys...
> umount: /tmp/sid-image/chroot/sys: target is busy.
> E: An unexpected failure occurred, exiting...
The reason why /sys is busy is that efivarfs is mounted under
/sys/firmware/efi/efivars.
It seems that efivarfs gets mou
Hello lists,
here is the 20th update of the status for reproducible live-build ISO
images [1].
Single line summary: I'm nearly there [2]
Reproducible status:
* All major desktops build reproducibly with bullseye, bookworm, trixie
and sid ...
** ... provided they are built for a second
I am trying to rebuild/upgrade my customized cd from bullseye to bookworm. The
problem is that the live image loads perfectly (tested on virtual and on a
local machine), the installer does not work for uefi - after choosing "install"
from the splash, the screen simply blanks out with a greyish-b
Package: live-build
Version: 1:20230502
Severity: normal
Dear Maintainer,
Building a live image with `lb build` fails towards the end with the
following error:
P: Begin unmounting /sys...
umount: /tmp/sid-image/chroot/sys: target is busy.
E: An unexpected failure occurred, exiting...
The
Hello Paul,
On 24/09/2023 05:28, Paul Wise wrote:
On Sat, 2023-09-23 at 11:08 -0500, James Bielefeldt wrote:
I wrote, but I am not sure its on the wiki. Here is the address.
https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
That isn't on the wiki, please contact
On Sat, 2023-09-23 at 11:08 -0500, James Bielefeldt wrote:
> I wrote, but I am not sure its on the wiki. Here is the address.
>
> https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
That isn't on the wiki, please contact the Salsa admins:
https://wiki.debian.org/Salsa
months and I am still
learning all the options and possible changes to live-build. Sadly for
the last two days the wiki pages for the live-build manual have been
unreachable. I have tried multiple browsers, including one clean install
and still cant open the pages. Just letting you know about the
Thanks.
On 9/22/23 22:45, Paul Wise wrote:
On Wed, 2023-09-20 at 13:42 -0500, James Bielefeldt wrote:
I make Debian spins. I have only done it a few months and I am still
learning all the options and possible changes to live-build. Sadly for
the last two days the wiki pages for the live
On Friday, September 22, 2023 11:45:16 PM Paul Wise wrote:
> On Wed, 2023-09-20 at 13:42 -0500, James Bielefeldt wrote:
> > I make Debian spins.
What is a (Debian) spin?
On Wed, 2023-09-20 at 13:42 -0500, James Bielefeldt wrote:
> I make Debian spins. I have only done it a few months and I am still
> learning all the options and possible changes to live-build. Sadly for
> the last two days the wiki pages for the live-build manual have been
> un
Hi
I make Debian spins. I have only done it a few months and I am still
learning all the options and possible changes to live-build. Sadly for
the last two days the wiki pages for the live-build manual have been
unreachable. I have tried multiple browsers, including one clean install
and
Your message dated Sat, 9 Sep 2023 11:17:47 -0500
with message-id
and subject line Bug#1051548: Regression: live-build 20230502 generates
corrupted images when using bookworm-backports APT pinning for kernel
has caused the Debian Bug report #1051548,
regarding Regression: live-build 20230502
Package: live-build
X-Debbugs-Cc: wfhnb...@duck.com
Version: 20230502
Severity: normal
Hi there,
I have used live-build 20210407 on Debian 11 to successfully build a large
number of Debian 11 based images. Now I'm using the same config and process
with live-build 20230502 on Debian
1 - 100 of 1781 matches
Mail list logo
