[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#28727: Profiles with intentionally out of date packages are upgraded
bug#28727: Profiles with intentionally out of date packages are upgraded to the newest version
Sat, 07 Oct 2017 22:32:29 +0300
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Ben Woodcroft (2017-10-07 16:14 +1000) wrote:
> I have a profile with address@hidden in it, and running 'guix package -u'
> updates it to address@hidden, which isn't what I want. I cannot run 'guix
> package -i address@hidden -u' because then it tries to install both
> and address@hidden, which conflicts.
> I can workaround this using 'guix package -u; guix package -i
> address@hidden'. That isn't ideal (wasteful downloading of substitute, extra
> entries in the generations list, etc), but is workable for me, making
> this a low priority bug for me.
> Ideally, I would expect that because I specified address@hidden first, guix
> should not try to install address@hidden However, this difficult because IIUC
> the packages which were specified to be included are not stored
> anywhere, and I suppose it would entail changes to the manifest format
> also. So, how to handle this?
Not sure if you find the following workaround useful, but you may just
make your own python package and install it instead:
Since this "python2" has only version 2, it will never be upgraded to
version 3. I mean there will be "address@hidden" but not "address@hidden", so
you install it ("guix package -i python2"), "guix package -u" will
update it to the current version of the python-2 series.