Bug#1069048: live-boot fails to DHCP on all NICs with link up

2024-05-21 Thread Thomas Goirand
ping? If nobody really cares about this bug, would it be ok to NMU the fix to Unstable, so that I can later backport it to Bookworm? Cheers, Thomas Goirand (zigo)

Bug#1069048: All NICs tried with same retries and timeouts?

2024-04-29 Thread Thomas Goirand
isting the cards with the link up, to pass it to the next step (ie: dhcp), which this patch doesn't touch (it's written properly already, and works with multiple network interface in the DEVICES= variable in /conf/param.conf). So there's IMO nothing more to do in this patch. Cheers, Thomas G

Bug#1069048: All NICs tried with same retries and timeouts?

2024-04-17 Thread Thomas Goirand
though. I hope you understood and I explained well enough this time! :) Cheers, Thomas Goirand (zigo)

Bug#1069048: All NICs tried with same retries and timeouts?

2024-04-16 Thread Thomas Goirand
. Cheers, Thomas Goirand (zigo)

Bug#1069048: All NICs tried with same retries and timeouts?

2024-04-16 Thread Thomas Goirand
Hi Narcis, The current behavior is that live-boot will attempt DHCP from the first NIC that is detected with link up. Cheers, Thomas Goirand (zigo)

Bug#1069048: live-boot fails to DHCP on all NICs with link up

2024-04-15 Thread Thomas Goirand
tried by live-boot). And this patch fixed things for us. Please merge this patch if you feel like it's correct. I also would like to have it fixed in Stable if possible (once I have the approval from the team). Cheers, Thomas Goirand (zigo) P.S: If one would like to test it, the easiest way

Bug#1026224: [patch] live-build: Option "-b netboot" fails on arm64 architecture

2024-02-07 Thread Thomas Goirand
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

Bug#1058927: live-build doesn't create tftpboot under arm64 and fails

2023-12-18 Thread Thomas Goirand
file or directory" (something like that). I tried under Bookworm, not sure if this is also in Unstable. Note that I've seen this behavior only under arm64, not in x86. So something must be wrong under this arch... Cheers, Thomas Goirand (zigo)

Bug#986148: live-build uses stable-security/updates instead of stable-security

2021-03-30 Thread Thomas Goirand
n repositories have symlinks, but Ansgar just confirmed what I thought: we shouldn't be using a lasting /updates at the end. Please remove it. Cheers, Thomas Goirand (zigo)

Bug#986063: live-build wrongly setups security repository for Bullseye: bullseye/updates instead of bullseye-security

2021-03-28 Thread Thomas Goirand
else SEC_REPO="-security" fi to keep a bit of backward compatibility. I'll let the current maintainers of live-build decide... Cheers, Thomas Goirand (zigo)

Bug#982155: Found the regression

2021-02-08 Thread Thomas Goirand
Hi Steven, Thanks for such a quick reply. Indeed, your commit fixes the problem: I've tested it by hand-patching my initrd.img. I very much would love this to be uploaded ASAP. Cheers, Thomas Goirand (zigo)

Bug#982155: Found the regression

2021-02-08 Thread Thomas Goirand
... Cheers, Thomas Goirand (zigo)

Bug#982155: PXE network booting looks broken to me: the initramfs doesn't attempt to wget my filesystem.squashfs

2021-02-06 Thread Thomas Goirand
in the interface of live-build (which would be breaking me), then I'd like to find out what. If you do know how to help, please do! Also, did you try doing PXE booting of a live image with this version 1:20210122 ? Maybe you should... :) Thanks for maintaining live-build, Cheers, Thomas Goirand (zigo)

Bug#934787: Please switch to Python 3

2019-08-14 Thread Thomas Goirand
Source: live-wrapper Version: 0.10 Severity: important Hi, We're trying to remove Python 2.x from Bullseye. Please switch this package to Python 3. I had a quick look into it, and it does seem Py3 ready. Is there any blocker? Cheers, Thomas Goirand (zigo)

Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-12-06 Thread Thomas Goirand
On 12/05/2017 09:58 AM, Raphael Hertzog wrote: > On Mon, 04 Dec 2017, Thomas Goirand wrote: >> Could you please review the patch and let me know if you think it's ok, >> apply to the git, and allow me to upload? > > I think it's wrong because it handles vmlinuz/initrd separa

Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-12-04 Thread Thomas Goirand
, Thomas Goirand (zigo) >From d8b192c4fee504c0334ee632bc0a631ae26ca0ec Mon Sep 17 00:00:00 2001 From: Thomas Goirand <z...@debian.org> Date: Mon, 4 Dec 2017 15:34:35 +0100 Subject: [PATCH 1/2] ACK nmu: 20151214+nmu1 --- debian/changelog | 16 debian/control

Re: Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-12-04 Thread Thomas Goirand
On 12/04/2017 02:41 PM, Raphael Hertzog wrote: > Control: reassign -1 live-tools > > On Wed, 29 Nov 2017, Thomas Goirand wrote: >> Building cpio /boot/initrd.img-4.9.0-4-amd64.new initramfs >> cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory >>

Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-12-04 Thread Thomas Goirand
On 12/04/2017 10:50 AM, intrigeri wrote: > Hi, > > Thomas Goirand: >> After booting a Stretch live image, I tried to upgrade it to Sid, and >> it fails with this error: > > Upgrading a *Live* system from one version of Debian to the other is > arguably a corner cas

Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-11-28 Thread Thomas Goirand
DER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable Building cpio /boot/initrd.img-4.9.0-4-amd64.new initramfs cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory I still don't see where to search... :/ Cheers, Thomas Goirand (zigo)

Bug#882769: More investigation

2017-11-26 Thread Thomas Goirand
. So my idea is that probably, adding a versionned breaks: somewhere will fix the upgrade problem. Let's see if I can find out... Cheers, Thomas Goirand (zigo)

Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory

2017-11-26 Thread Thomas Goirand
if you're fine with that, however, I'd appreciate help here. Cheers, Thomas Goirand (zigo)

Re: IMPORTANT: Do live Debian images have a future?

2017-07-05 Thread Thomas Goirand
reluctance "to go into details". > This type of thing keeps people in the dark and that is something I do > not support. There is no need to go over all the details but at least > provide proof as I have done. > > On 5 July 2017 at 08:34, Thomas Goirand <tho...@goirand.fr > <mai

Re: IMPORTANT: Do live Debian images have a future?

2017-07-04 Thread Thomas Goirand
let's not go into details why this happened), Steve does it at the same time as other Debian images. It's now included in a single process of building images. Cheers, Thomas Goirand (zigo)

Re: Comments on live-build, vmdebootstrap, bootstrap-vz, and live-wrapper

2016-08-17 Thread Thomas Goirand
to copy them there after, building in a loop file like > everything else until that moment? Well, it's been about a year I'm asking that someone tests the openstack images on EC2: http://cdimage.debian.org/cdimage/openstack/ IMO, they should "just work" out of the box. The jessie one though should only work on HVM though. Could someone really take the time to test? Cheers, Thomas Goirand (zigo)