On 02.05.24 17:30, Roland Clobus wrote:
I'll prepare a proper fix that detects whether the directory is present.
Perfect, thanks!
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 messag
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.binary
E: An unex
Hi Roland,
your commit comment of d14306a7 only mentions meta information, yet it
also patches scripts/build/binary_includes. Could you elaborate on that
in case that indeed was intentionally part of the commit?
I recently built a .deb of the current master and noticed build failures
like th
On 21.04.21 21:14, Jonathan Carter wrote:
> * Xfce looks a lot nicer and the broken have been fixed, and also fine
> overall.
The broken $what?
Thanks
Daniel
Package: live-build
Version: 1:20210330
Severity: normal
Hi,
since 21eff20ea3caec205568e7305732928fedd10b0a I can no longer build buster
images including firmware:
---8<--
P: Begin scheduling firmware installation...
--2021-04-02 11:19:29--
http://ftp.de.debian.org/debian//dists/
locales 2.28-10
ii sudo1.8.27-1+deb10u2
ii user-setup 1.81
Versions of packages live-config suggests:
ii pciutils 1:3.5.2-1
ii wget 1.20.1-1.1
-- no debconf information
>From 6786f9bf1848993fff68787c9734f6f6b9277c4d Mon Sep 17 00:00:00 2001
Fr
I should have looked at Depends: prior to replying.
1) live-build doesn't depend on bash, but plain sh
2) all other tools are either in coreutils or get installed into the
chroot during the build
That said, I'm not sure if it's really worth it to add a new dependency.
How about a pipe instead?
On 15.04.19 12:16, Ronny Standtke wrote:
> I replaced this code block with a simple rsync
> call which is much more efficient in both space and time (see attached
> patch).
I believe this violates the original intention of live-build only
requiring bash (and all the other tools it uses... *cough*)
On 15.01.19 18:19, Daniel Reichelt wrote:
> I suppose dash is installed (and therefore dpkg-configure'd) after the
> preseed file gets applied in the build root.
Bzzt. I meant "before the preseed file gets applied", of course.
signature.asc
Description: OpenPGP digital signature
On 15.01.19 14:35, Stefan Baur wrote:
> Am 15.01.19 um 15:19 schrieb Fernando Toledo:
>> check the shell in /etc/passwd , but i think that must be /bin/bash
>> also /etc/default/useradd have SHELL=/bin/sh
>
> Bzzt, wrong.
>
> That is the individual user's shell setting. I'm looking for a way to
> 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?
Hi Paul,
> I can also
> see a successful mount attempt scrolling through during the boot, b
On 12/06/2017 09:04 PM, Thomas Schmitt wrote:
> Raphaël, are you aware that the change in live-build
>
> https://anonscm.debian.org/cgit/debian-live/live-build.git/commit/?id=ff71712590a809d0f7ba680e787a9f091ed853b2
> did not work and caused
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Package: live-build
Version: 1:20170920
Severity: normal
Tags: patch
Hi,
currently .disk/mkisofs gets created by appending an echo statement to
the temporary script binary.sh whicht gets executed to actually run xorriso.
However this creates the following error in build.log:
---8<--
on and replacement of the mount command is both
no longer necessary, and has become harmful. The attached patch against
live-boot's current tag 1%20170623 removes it.
Cheers
Daniel
>From 3891e35f1df321e44e51347df95938346c108ef4 Mon Sep 17 00:00:00 2001
From: Daniel Reichelt
Date: Sun, 1
Package: live-build
Version: 1:20170213
Severity: minor
Tags: patch
Hi,
the attached patch streamlines the missing keyboard shortcut "A" for the
"Advanced options" entry in the syslinux-based boot menu configs.
Thanks
Daniel
diff --git a/share/bootloaders/extlinux/menu.cfg b/share/bootloaders
Package: live-boot
Version: 1:20170112
Severity: minor
Tags: patch
Hi,
live-boot's initramfs-hook contains these lines ([1], [2]), which put
live-boot's /lib/live/boot/ twice into the initramfs image: the latter one at
/lib/live/boot/ and the former one - wrongly - also at /bin/boot/).
The dupl
Hi all,
Since live.debian.net went down, the contributing section of live-manual
didn't get any updates and there are no debian-next branches at
anonscm.d.o/.../live-* as mentioned therein...
So what's currently the live-team's preferred way to receive patches?
for live-*?
Thanks,
Daniel
si
> Incidentally, if anyone *has* a link to the old deb package
> for 1:20151215 so I could verify this, that'd help.
Jason,
have a look at http://snapshot.debian.org/
Cheers
Daniel
signature.asc
Description: OpenPGP digital signature
Hi,
these images are missing from [1]:
debian-live-8.7.0-amd64-lxde-desktop+nonfree.iso
debian-live-8.7.0-amd64-mate-desktop+nonfree.iso
I hope I got the correct mailing lists, if not and someone knows of a
better destination, please forward this message :-)
Thanks!
Daniel
[1]
http://cdim
Hi,
live-boot's initramfs-hook contains these lines ([1], [2]), which put
live-boot's /lib/live/boot/ twice into the initramfs image: the latter
one at /lib/live/boot/ and the former one - IMO wrongly - also at
/bin/boot/).
The duplication was introduced by [3] and I think [1] should actually re
Hi Ronny,
just a minor thing but I think you should anchor your grep to the end of
the filename:
grep -v "old-dkms$"
Cheers
Daniel
On 09/17/2016 02:13 PM, Ronny Standtke wrote:
> Package: live-tools
> Version: 1:20151214+nmu1
> Severity: important
> Tags: patch
>
> On my Debian Live syste
On 09/02/2016 03:22 PM, Lorenzo Faletra wrote:
> where is the squashfs located at and how do you connect the booting
> kernel to the network?
- The squashfs to be loaded resides on a webserver on the same LAN/ip
subnet as the machine being booted
- fetch=http://10.0.0.1/$path/filesystem.squashfs
Hi guys,
I'm not sure whether to report this to live-boot or wget, so I'm asking
in advance.
I just tried to pxeboot the new Kali release 2016-2 from just a few days
ago an ran into an annoying, extremely long (and somewhat random) delay
in the live-boot phase when using fetch=http://.../filesys
Hi Don,
> However, when I go to https://github.com/debian-live/live-images.git I cannot
> find a branch that contains the old rescue build configuration.
said repository is quite correct, however the files got removed from the
tree by [1].
> Is this configuration laying around somewhere I can
Hi folks,
x-session-manager=none on the kernel cmdline does no good if lightdm is
installed
in the live-image: Prior to checking the contents of
/etc/X11/default-display-manager,
/etc/init.d/lightdm has a check if that file exists in the first place. If it's
not
found, lightdm will just start.
=live-build.git;a=commitdiff;h=f2c1f07ee4b1fb72b59ab2978014735ff5ae2e62
dpkg-buildpackage: source package live-build
dpkg-buildpackage: source version 5.0~a9-1.1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Daniel Reichelt
dpkg-buildpackage: host architecture
> this is already fixed in git
Not quite, see [1]
Cheers
Daniel
[1]
http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=2a400dc63ec7305c80dd072984a14839aed74501
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
Sorry, I totally botched the second patch. Here we go again...
>From e824b5a023472ea6f85b1e3a0614c04420a67e9b Mon Sep 17 00:00:00 2001
From: Daniel Reichelt
Date: Tue, 21 Apr 2015 19:09:00 +0200
Subject: [PATCH 2/2] Don't truncate files outside the build chroot
The list of files p
e solution*s* are attached (only one required).
Personally I strongly prefer 0002, since it solves the underlying
problem of files *outside* the build chroot getting modified.
Thanks,
Daniel
>From 2ce5d2917cc93622809e50060fdb7106d78bcc6c Mon Sep 17 00:00:00 2001
From: Daniel Reichelt
Date: Tue, 21 Ap
Hi,
> I think there is a terminology mismatch here. I wanted to avoid building
> or rebuilding ISO images entirely, I wanted to use the existing images.
presuming your boot medium is an USB stick, instead of dd'ing the
hybrid-iso to it you could partition/format it/make it bootable with
syslinux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Maintained by someone (are you volunteering?) outside the Debian Live
> project? Sure! Go for it! :)
well, why not? will you sponsor me? i'm not a debian maintainer yet.
Daniel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Commen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Why task-live? What makes these "live" things. I'm just not seeing it.
>
> Because one of the things that people very commonly want to do with a
> live ISO is access their existing filesystems, when they can't boot off
> them for some reason. LVM a
Update: I get a similar /var/log/live/config.log when I try pxebooting
with the kernel cmdline below. Again: after networking gets initialized
outside live-config and directly from init, wgetting the hook works.
boot=live
fetch=http://1.2.3.4/downloads/kvm/linux_debian-live-7.0.0-amd64-rescue/liv
Hi folks,
I've been trying to boot the official wheezy live ISO and supply
live-config.hooks via http.
My boot parameters for a KVM are:
-append
boot=live
config
dhcp
live-config.hooks=http://1.2.3.4/downloads/kvm/live-hook-wheezy
live-config.keyboard-model=pc105
live-config.keyboard-layouts=de
Hi Daniel,
I just wondered why the files generated by an invocation (from a
chroot_local-hook) of
apt-file update
won't end up in my squashfs image. Turns out in lb_chroot_sources there
is a call
rm -rf chroot/var/cache/apt
which essentially kills apt-file's files residing in
chroo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> well, you haven't showed any reason where/why we should use 'here-
> documents' at all, you only made an argument for why you think using the
> posix-only subset doesn't make sense to you (in your use-case).
>
well, communication's a bitch sometime
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> currently, we
> do not want to require a debian installation to build a debian image.
i c
> but until then, i do not think it makes much sense to 'give up' the
> advantage of having a 'posix shell only' requirement for almost no
> benefit.
still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> we aim for live-* to work with the posix subset only, in order to
> minimize the system requirements as it should be for 'bootstrap tools'
> like live-*.
I don't want to initiate a flame war on what shell to use best for task
XY and minimizing syste
Hi everybody,
bash provides a really nice feature which allows for here documents to
be formatted nicely in the containing script. Quote from the bash manpage:
---8<---
If the redirection operator is <<-, then all leading tab characters are
stripped from input lines and the line containin
On 09.10.2012 15:58, Robert Spiteri wrote:
> Thanks for this. So I just remove cupsd from the list of packages? Or
> are there any other packages which I have to exclude?
Removing cupsd from the package list won't do any good.
The issue is that during the installation of cups-pdf within the chro
> Yes I guess it is a bug unfortunately. Thanks for your time.
Sorry for the late answer, I just re-opened #614713 [1]. See my report
for details.
Other than waiting for a fixed package or copying the certs file, you
could stop cupsd during the build. This causes lpadmin to fail instead
of asking
> I prefer not to use apt-pinning because I prefer my deb files to be
> from the stable repository but thanks for the tip.
Not the point: using apt-pinning or copying .deb's to a local config
tree has the same effect: they're no more "only stable". I know the
feeling, it's like having to die one d
Hi
> towards 3.2). I compile kernels from upstream sources all the time,
> but I don't know how to FORCE lb-config and lb-build to boot my
> customized kernel instead of the one mainline. Can you give me some
> pointers? (I've never set-up an APT repository... I would prefer to
> avoid this unless
Package: live-config
Version: 2.0.15-1
Severity: important
Tags: squeeze sid
Hi Live-Team,
I spotted another incompatibility between a .deb and how the Live system is
handling its behaviour (similar to live vs. dwww).
Usually I boot my live-systems so that LIVE_TIMEZONE="Europe/Berlin" gets set
Package: live-build
Version: 2.0.12-2
Severity: normal
Tags: squeeze
Hi live team,
I'm building quite large live systems which I employ in daily production use,
so they are BIG (around 4GB). Recently I added the package dwww, which causes
the build to fail occasionally. I was able to track down t
> as said: if you include the package, httpfs will automatically be
> included in the initramfs - not more, not less.
Ah - missunderstanding. Thanks for clarifying.
> and it's not by default installed in the prebuilt images since it's
> considered too experimental for squeeze.
Well then, I'm ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Daniel,
> httpfs is already included by default if you install the package, no
> need to hack anything.
???
Just loop-mounted the squashfs from both amd64 and i386 Gnome live ISOs
dated 2011-11-05 02:15am and chrooted into them:
r...@sb74:/# dpk
> Could you state an example of when https would be needed rather than http?
httpFs wasn't a typo :)
httpfs allows to mount filesystems via http and is built on top of FUSE,
see http://packages.debian.org/squeeze/httpfs2
That way one doesn't have to load the whole squashfs image at boot time
like
Hi list,
I just hacked around a little by taking the current debian live
snapshot, unpacked the initrd image contained in the iso, added the
httpfs binary and its dependency libfuse.so.2, repacked it and voila: I
could boot the squashfs via PXE and initramfs' httpfs=http://... kernel
parameter.
@
Package: live-initramfs
Version: 1.157.4-1
Severity: important
Hi,
since udev stops shipping /lib/udev/vol_id initramfs-tools needs updating.
According to [1], all calls to
vol_id -t
should be changed to
/sbin/blkid -o udev -p ...
Probably the initramfs-hook to copy that new bina
51 matches
Mail list logo
