Hello guix,
I’m trying to deploy a test set of python packages to a remote server,
using the following guix pack command (latest guix, as for now)
guix pack -R --compression=xz --save-provenance \
-S /.guix-profile/bin=bin -S /.guix-profile/share=share \
-S /.guix-profile/etc=et
Hi Cayetano,
Cayetano Santos via Bug reports for GNU Guix writes:
> Hello guix,
>
> I’m trying to deploy a test set of python packages to a remote server,
> using the following guix pack command (latest guix, as for now)
>
> guix pack -R --compression=xz --save-provenance \
> -S /.gu
Hi Josselin,
Josselin Poiret writes:
> Hi Cayetano,
>
> Cayetano Santos via Bug reports for GNU Guix writes:
>
>> Hello guix,
>>
>> I’m trying to deploy a test set of python packages to a remote server,
>> using the following guix pack command (latest guix, as for now)
>>
>> guix pack -
Hi Maxim,
Maxim Cournoyer writes:
> If you send it *after* the core-updates merge (to core-updates)? It's
> going to be quite a while before it lands to master. Perhaps you could
> send it now? core-updates is the right branch for mass rebuilds.
I think we are trying to move away from the mas
Hi Josselin,
Josselin Poiret writes:
> Hi Maxim,
>
> Maxim Cournoyer writes:
>
>> If you send it *after* the core-updates merge (to core-updates)? It's
>> going to be quite a while before it lands to master. Perhaps you could
>> send it now? core-updates is the right branch for mass rebuilds.
Hi Maxim,
Maxim Cournoyer writes:
> Perhaps I'm out of the loop, but in my book the main branches should
> never close. If there's a need to freeze the state of one the three
> main branches new development branches can be created. This was
> discussed in the past.
I don't think there was a