go for option 3.
> What's your opinion?
>
> With kind regards,
> Roland Clobus
We really want to ship documentation in the distribution, it's needed
for accessibility, offline usage, and so on.
Kind regards,
Luca Boccassi
1 Nov 2020, Roland Clobus wrote:
<...>
> > live-build:
> > * /EFI/boot contains a 32-bit EFI image on the amd64 iso.
> > ** AP: Is this needed/correct?
>
> Pass, I don't know.
IIRC yes - it's rare, but I think there is hardware out there with
32bit EFI and 64bit CPUs.
debian.org/
Alternatively, patches can be sent to this very same mailing list.
Alternatively, bugs can be opened against the relevant packages, with
patches attached.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Sun, 2020-03-15 at 18:20 +, jnq...@gmail.com wrote:
> On Sun, 2020-03-15 at 11:34 +0000, Luca Boccassi wrote:
> > The reason I asked for the change and I wasn't comfortable with
> > making
> > the download directory 777 is that live-build is routinely used in
>
the risk of a rogue, unprivileged process to be able to mess
with the downloaded files after apt has ran, if it's just to fix a
harmless warning.
If it can be fixed without introducing risk - great! If not, I would
recommend to document it and leave it.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
mentation might look bigger, but it's probably faster,
> which
> might matter in some situations, and avoids calling outside
> utilities.
>
> This isn't a shell scripting mailing list, but FWIW here's yet
> another
> way. It's been tested on dash and posh, but does the work in a
> subshell
> which is fine if you just want to echo strings but won't allow you
> to
> set variables. It's a function:
>
> echo_strings()(
> local loader
> IFS=,
> set -- $*
> for loader
> do
> echo "$loader"
> done
> )
>
> LB_BOOTLOADERS='first bootloader,second one'
> echo_strings "$LB_BOOTLOADERS"
> first bootloader
> second one
>
> But the pipe to tr is probably fine for this case.
Risking to state the obvious: if this snippet is ran once at setup,
then keep it readable, short and maintainable.
If it's in the "hot path" and ran a gazillion times per build, then by
all means optimize away - but document it clearly.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Wed, 2019-06-05 at 11:56 +0200, Gianluigi Tiesi wrote:
> On 4/28/19 8:14 PM, Luca Boccassi wrote:
> > If you have tried with debian live iso too, I don't think this has
> > anything to do with live-build?
>
> Isn't debian live iso made using live-build?
> Unfortunatel
e the pin in 'config/apt/preferences'
> before running the 'make.sh' script):
>
> https://salsa.debian.org/smonaica-guest/sid-standard-live.git
>
>
> Best regards,
> -S.M.
Hi,
This has been reported upstream:
https://github.com/systemd/systemd/issues/12492
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
than
live-boot and live-build, so I'll let other maintainers and
collaborators comment on whether they'd like the CI activated.
Thanks for your work!
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
s from debian live iso
>
> I suppose the system cannot shutdown ethernet if the root is on nfs,
> and nfs live mount cannot
> be unmounted.
>
> I've seen around someone suggesting to make systemd ignore interface
> shutdown problems
If you have tried with debian live iso too, I don't think this has
anything to do with live-build?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Sun, 2019-04-07 at 13:50 +0200, Roland Clobus wrote:
> On 06/04/2019 20:22, Luca Boccassi wrote:
> > Please feel free to send merge requests on Salsa:
> >
> > https://salsa.debian.org/live-team/live-manual
> >
>
> Thank you accepting the first (tiny) merge
ve-team/live-manual
You can register a guest account here if you don't have one:
https://signup.salsa.debian.org/register/guest/
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Thu, 2019-02-14 at 18:35 +, Luca Boccassi wrote:
> On Thu, 2019-02-14 at 17:18 +0100, Matthijs Kooijman wrote:
> > Hey Luca,
> >
> > > At a quick glance it all sounds good to me, although I can't say
> > > I
> > > have
> >
ng a new option to disable this?).
>
> I just noticed that lb config has a --bootloaders that supports
> *multiple* bootloaders, so that would be perfect way to support this.
> E.g. --bootloaders syslinux,syslinux-efi to have combined image
> (which
> would also become the d
d at the iso version yet (which is also not my
> primary interest, but I think it would be good to handle as well).
>
> Happy to hear any thoughts :-)
>
> Gr.
>
> Matthijs
Hi,
At a quick glance it all sounds good to me, although I can't say I have
a lot of experience with syslinux.
For feature parity, I'd encourage to look into supporting Secure Boot
like the grub-efi implementation does, since we are preparing to ship
that in Debian 10. It's not much extra work on top of adding the rest
anyway.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
> everything was new. I purged the system of live-* packages and
> > reinstalled them only to have the problem again. I have done the
> > same
> > thing this morning and still get the same issue. I will continue to
> > work on it now I know it should be working and when I find w
stretch/amd64
> system"
> 2. Is there a clash with Live-build and debootstrap somewhere making
> live-build not "see" debootstrap even though it is installed?
>
> > From memory live-build used to detect the version it was installed
> > on
>
> and buil
of
> network-manager-config-connectivity-debian in live-build, and how to
> fix
> the issue ?
>
> Best regards,
> Thierry
Hi,
What configuration are you building with? I just tried a build with --
backports=true and it worked just fine.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
t;
> Some content might still be found at https://github.com/debian-live..
> .
>
> On 09.08.2018 12:12, Luca Boccassi wrote:
> > On Thu, 2018-08-09 at 11:54 +0200, Moritz Schlarb wrote:
> > > Hi everyone,
> > >
> > > while searching for all kinds
Thanks,
Thanks, the migration was done quickly and crudely as Alioth was going
away, I'm sure there's more broken stuff, if you find it please open
more PRs.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
given they are not
installed.
What is _exactly_ the problem, and how do you reproduce it? Are you
sure you didn't set conflicting dependencies?
> 2018-07-05 8:00 GMT-04:00 Luca Boccassi :
> > On Wed, 4 Jul 2018 12:04:54 -0400 PICCORO McKAY Lenz > gmai
> > l.com> wrote:
&
ith "--apt-recommends false"
and recommends will not be installed.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
point to
provide backward-compatibility for Buster, so nothing should be broken
for the moment.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ader install stage) fail wich "Cannot install grub-efi"
> i search in the binary pool and the package do not exist.
>
> thanks!
grub-efi-amd64-bin
grub-efi-ia32-bin
grub-pc-bin
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
ing in the fs
> root.
>
> Before I go crazy over the entangled variables, functions, and
> branches in
> /var/live/boot, is anyone on this list familiar enough with the
> system to tell
> me what would be the correct boot line here?
>
> Thank you very much.
Have you tried findiso=/fs/path/to/stretch.squash ?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
containing a live file system
How are you installing the ISO on the USB stick? Did you build the
image yourself, if not where is it from?
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 28 Mar 2018 20:20:46 +0100
Source: live-build
Binary: live-build
Architecture: source
Version: 1:20180328
Distribution: unstable
Urgency: low
Maintainer: Debian Live <debian-live@lists.debian.org>
Changed-By: Luca Boccas
ian-live@lists.debian.org>
Changed-By: Luca Boccassi <bl...@debian.org>
Description:
live-boot - Live System Boot Components
live-boot-doc - Live System Boot Components (documentation)
live-boot-initramfs-tools - Live System Boot Components (initramfs-tools
backend)
Closes: 856482 8
On Fri, 2018-03-23 at 11:44 +, Luca Boccassi wrote:
> On Fri, 2018-03-23 at 08:27 +0800, Steven Shiau wrote:
> > On 3/20/2018 AM 06:14, Luca Boccassi wrote:
> > > I hope this can be useful for others
> >
> > Yes, exactly! This is great! We recently need this feat
On Fri, 2018-03-23 at 08:27 +0800, Steven Shiau wrote:
> On 3/20/2018 AM 06:14, Luca Boccassi wrote:
> > I hope this can be useful for others
>
> Yes, exactly! This is great! We recently need this feature and you
> have
> made it and share that. Cool!
> BTW, did you
script going
forward with any future bug fix.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Tue, 2018-03-13 at 15:05 +0100, Raphael Hertzog wrote:
> Hi,
>
> On Tue, 13 Mar 2018, Luca Boccassi wrote:
> > > > Or maybe have a backward-compatible symlinks?
> > >
> > > This seems entirely reasonable. Can you work on this?
> >
> >
On Tue, 2018-03-13 at 10:49 +0100, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 12 Mar 2018, Luca Boccassi wrote:
> > That is certainly the case for myself at $work - we have a lot of
> > scripts to deal with installing images, I've tested it,
> > and
> > they all bre
opened a Merge Request on Salsa [1] with a fix from Sameer, a
colleague of mine at $work.
Thank you!
--
Kind regards,
Luca Boccassi
[1] https://salsa.debian.org/live-team/live-boot/merge_requests/3
signature.asc
Description: This is a digitally signed message part
grub-team/grub/blob/master/debian/build-efi-images
Using that image is necessary with Secure Boot as that's what gets
signed. Ubuntu has the same workaround in place.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
-wrapper because my examples
> debian-live-8.4.0-i386-standard.iso
> debian-live-8.4.0-amd64-standard.iso
> both tell
> Preparer Id : LIVE-BUILD 4.0.5-1; HTTP://LIVE-
> SYSTEMS.ORG/DEVEL/LIVE-BUILD
> but bear only a single partition which marks the ISO 9660 filesystem.
>
&g
for Secure Boot support,
which has been implemented in a separate commit, in the same Merge
Request.
Thanks!
--
Kind regards,
Luca Boccassi
[1] https://salsa.debian.org/live-team/live-build/merge_requests/3
signature.asc
Description: This is a digitally signed message part
.list.
The proposed solution is to avoid running apt update in the chroot at
the end of the chroot_archives remove step if the repository is local
and has been umounted.
A PR [2] has been opened on Salsa with the proposed fix. Please let me
know if you'd like more information or a different sol
38 matches
Mail list logo
