Guix home - 'pinning' ?

Guix home - 'pinning' ?

[jordila]

Hi Guixers

when using guix-home, is there a way to pin a given package to its  current version, so that it stays as it is despite 'guix pull'     bringing new commits ?

Thanks, thanks, thanks

F

Re: Guix home - 'pinning' ?

[Robby Zambito]

Hi,

> when using guix-home, is there a way to pin a given package to its 
> current version, so that it stays as it is despite 'guix pull'    
> bringing new commits ?

In your (home-environment (packages ...)) list, you should specify the
package that has the correct version that you want. There are two ways
to do this. You can either create an inferior channel, and specify the
package by looking it up in that channel, or you can apply a
transformation to the package to specify the version.

Using an inferior package will pull the package from a previous version
of Guix - including all of its package inputs. This will pin all of the
transitive dependencies of the package as well. See: info guix Inferiors
for information on how to define an inferior, and how to select a
package from that inferior.

If you want to pin a package to a specific commit, version, branch, etc
of that package, you can use transformations. See: info guix "Defining
Package Variants" for how to use options->transformation, and info guix
"Package Transformation Options" for the available options you can set.

Hope this helps :)

Robby

Re: Guix home - 'pinning' ?

[Fenix Lopez]

Hi !

   Thanks for the clarifiction, Robby.

In order to give some more context , may i add the fact that the package 
in question

is not being compiled/derived when entering the build phase ? In 
consquence, the whole 'guix home reconfigure' gets stopped...

That's the underlaying reason why i was wondering how to pin that 
'offending' package.

    Umh... leaving package version 'pinning' aside, umh...   Is there 
another way to prevent such described scenario ? how to get ' guix home 
reconfigure'

finish the whole process regardless the issue described ?


thanks, thanks , thnaks for your attention

F


On 12/6/23 18:16, Robby Zambito wrote:
> Hi,
>
>> when using guix-home, is there a way to pin a given package to its
>> current version, so that it stays as it is despite 'guix pull'
>> bringing new commits ?
> In your (home-environment (packages ...)) list, you should specify the
> package that has the correct version that you want. There are two ways
> to do this. You can either create an inferior channel, and specify the
> package by looking it up in that channel, or you can apply a
> transformation to the package to specify the version.
>
> Using an inferior package will pull the package from a previous version
> of Guix - including all of its package inputs. This will pin all of the
> transitive dependencies of the package as well. See: info guix Inferiors
> for information on how to define an inferior, and how to select a
> package from that inferior.
>
> If you want to pin a package to a specific commit, version, branch, etc
> of that package, you can use transformations. See: info guix "Defining
> Package Variants" for how to use options->transformation, and info guix
> "Package Transformation Options" for the available options you can set.
>
> Hope this helps :)
>
> Robby

Re: Guix home - 'pinning' ?

[Luis Felipe]

[-- Attachment #1.1.1: Type: text/plain, Size: 797 bytes --]

Hi Fenix,

El 13/06/23 a las 15:06, Fenix Lopez escribió:
> In order to give some more context , may i add the fact that the 
> package in question is not being compiled/derived when entering the 
> build phase ? In consquence, the whole 'guix home reconfigure' gets 
> stopped...
>
> That's the underlaying reason why i was wondering how to pin that 
> 'offending' package.
>
>    Umh... leaving package version 'pinning' aside, umh...   Is there 
> another way to prevent such described scenario ? how to get ' guix 
> home reconfigure'
>
> finish the whole process regardless the issue described ?

If I understand correctly, you could add the following option to "guix 
home reconfigure":

-k, --keep-going       keep going when some of the derivations fail



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]