guix installation why internet connection required?

guix installation why internet connection required?

[vvt]

[-- Attachment #1: Plaintext Message --]
[-- Type: text/plain, Size: 540 bytes --]

x86 x64 gnu guix system 1.4.0 iso requires internet connection in order to get
installed. Same goes for i686 iso.

Why is that so? Why is there no
iso option for installing off line? Thanks.


-------------------------------------------------
This free account was provided by VFEmail.net - report spam to abuse@vfemail.net
 
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

[-- Attachment #2: HTML Message --]
[-- Type: text/html, Size: 998 bytes --]

Re: guix installation why internet connection required?

[Maxim Cournoyer]

Hi,

vvt@mail-on.us writes:

> x86 x64 gnu guix system 1.4.0 iso requires internet connection in order to get
> installed. Same goes for i686 iso.
>
> Why is that so? Why is there no
> iso option for installing off line? Thanks.

There's this ticket about the same: #43049.  If I remember correctly it
may be related by the Guix binary inside the ISO image being from the
Guix package of the Guix used to generate it, perhaps.

That seems like a tricky problem to solve.

-- 
Thanks,
Maxim

Re: guix installation why internet connection required?

[Giovanni Biscuolo]

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

Hi Maxim and vvt@mail-on.us,

I'm including 43049@debbugs.gnu.org to keep track of the discussion on
this feature request (Add the ability to install GuixSD offline)

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> vvt@mail-on.us writes:
>
>> x86 x64 gnu guix system 1.4.0 iso requires internet connection in order to get
>> installed. Same goes for i686 iso.
>>
>> Why is that so? Why is there no
>> iso option for installing off line? Thanks.
>
> There's this ticket about the same: #43049.  If I remember correctly it
> may be related by the Guix binary inside the ISO image being from the
> Guix package of the Guix used to generate it, perhaps.

Sorry I don't understand the problem, could you expand please?

The guix (and daemon) versione are those of the channel used when
creating the install .iso image; booting the 1.40 installer we get a
"guix version" and "guix describe" value of 989a391...

Also, the /gnu/store (755MB on 1.4.0 installer image) have all the
software needed to run the installer; when installing the (same) linux
kernel on the target disk, for example, why the daemon would download
the same substitute when it's already in the store?

Obviously the connection to a substitute server is needed if the user
choose to install some software not already in the store, so the point
should "just" be to have all the software the installer allows the user
to be installed.

> That seems like a tricky problem to solve.

...I feel like I'm missing something important here :-)

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

bug#43049: guix installation why internet connection required?

[Josselin Poiret via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

> Sorry I don't understand the problem, could you expand please?
>
> The guix (and daemon) versione are those of the channel used when
> creating the install .iso image; booting the 1.40 installer we get a
> "guix version" and "guix describe" value of 989a391...

Not exactly, to include Guix inside the installer image, it somehow
needs to refer to itself.  The way it used to be done was by using the
`guix` package, which necessarily is older than the current commit.
However, we also implemented the `current-guix` hack that basically uses
a guix checkout at the current guix version as the source for the guix
package.  In both cases though, we shouldn't see any differences in
other package's derivations…

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

bug#43049: Add the ability to install Guix System offline

[Giovanni Biscuolo]

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

Hi Josselin,

first of all, sorry for the confusion: I'm still learning... and I'm
probably still using bad terminilogy from a Guix/Guile developer POV.

Josselin Poiret <dev@jpoiret.xyz> writes:

> Giovanni Biscuolo <g@xelera.eu> writes:
>
>> Sorry I don't understand the problem, could you expand please?
>>
>> The guix (and daemon) versione are those of the channel used when
>> creating the install .iso image; booting the 1.40 installer we get a
>> "guix version" and "guix describe" value of 989a391...
>
> Not exactly, to include Guix inside the installer image, it somehow
> needs to refer to itself.  The way it used to be done was by using the
> `guix` package, which necessarily is older than the current commit.

OK, in fact I checked starting the guix-1.4 install image in a VM and I
got an older guix in the install system (forgive me for the missing the
details, but this is not important in this context), but the verion
installed on the target was 1.4.0 (so I guess its subsitute was
downloaded from one of the build farms).

> However, we also implemented the `current-guix` hack that basically uses
> a guix checkout at the current guix version as the source for the guix
> package.

So, since some commit, now the guix version used to build the target
system image is the one checked-out by the person/agent running the
install image build script: did I understand it correctly?

> In both cases though, we shouldn't see any differences in other
> package's derivations…

Does this mean you consider possible to pre-populate the /gnu/store
install system (the one started using the install image) with a substet
of substitutes possibly needed in the target system?

I'm wondering if it's possible to create a custom build image (info
"(guix) Building the Installation Image") to do something like this.

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

bug#43049: Add the ability to install Guix System offline

[Josselin Poiret via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

>> However, we also implemented the `current-guix` hack that basically uses
>> a guix checkout at the current guix version as the source for the guix
>> package.
>
> So, since some commit, now the guix version used to build the target
> system image is the one checked-out by the person/agent running the
> install image build script: did I understand it correctly?

Yes.

>> In both cases though, we shouldn't see any differences in other
>> package's derivations…
>
> Does this mean you consider possible to pre-populate the /gnu/store
> install system (the one started using the install image) with a substet
> of substitutes possibly needed in the target system?

I think it's already meant to be the case, see the comment in
gnu/system/install.scm about keeping a reference to the bare bones os's
closure.  It wouldn't contain all graphical stuff either, but I think
there's also some trouble with grafts that forces users to still
download substitutes.

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]