The end error was the same, but he did not have the 'mv' error. The
strange part is, after the failure when I check, 'binary' is in fact
there. I will keep digging, but it seems strange to receive that error
when the location does exist. I have run into other issues with the
isolinux config i
Zed, I don't think yours is the same issue:
On 13/08/14 02:05 AM, Zed wrote:
> I have run into the same issue using the same version of lb.
>
> # lb --version
>
> 4.0~alpha39-1
>
> I’ve enabled verbose and debugging and see the following:
>
> [2014-08-12 22:49:31] lb binary_iso
>
> D: Reading co
: Sat, 9 Aug 2014 14:06:12 +0100
To: Debian-live mailing list <mailto:debian-live@lists.debian.org>>
Subject: ISO failure
Resent-From: <mailto:debian-live@lists.debian.org>>
Resent-Date: Sat, 9 Aug 2014 13:06:31 + (UTC)
lb --version
4.0~alpha39-1
P: Begin building binary is
set.
Zed
From: Anthony F McInerney
Date: Sat, 9 Aug 2014 14:06:12 +0100
To: Debian-live mailing list
Subject: ISO failure
Resent-From:
Resent-Date: Sat, 9 Aug 2014 13:06:31 + (UTC)
lb --version
4.0~alpha39-1
P: Begin building binary iso image...
Reading package lists...
Buil
lb --version
4.0~alpha39-1
P: Begin building binary iso image...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libisoburn1
Suggested packages:
jigit cdck
The following NEW packages will be installed:
isolinu