GNU bug report logs - #28727
Profiles with intentionally out of date packages are upgraded to the newest version

Previous Next

Full log

Message #8 received at 28727 <at> debbugs.gnu.org (full text, mbox):

From: Alex Kost <alezost <at> gmail.com>
To: Ben Woodcroft <b.woodcroft <at> uq.edu.au>
Cc: 28727 <at> debbugs.gnu.org
Subject: Re: bug#28727: Profiles with intentionally out of date packages are
 upgraded to the newest version
Date: Sat, 07 Oct 2017 22:32:29 +0300

Ben Woodcroft (2017-10-07 16:14 +1000) wrote:

> Hi,

Hello,

> I have a profile with python <at> 2 in it, and running 'guix package -u'
> updates it to python <at> 3, which isn't what I want. I cannot run 'guix
> package -i python <at> 2 -u' because then it tries to install both python <at> 2
> and python <at> 3, which conflicts.
>
> I can workaround this using 'guix package -u; guix package -i
> python <at> 2'. 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 python <at> 2 first, guix
> should not try to install python <at> 3. 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:

(define-public my-python-2
  (package
    (inherit python-2)
    (name "python2")))

Since this "python2" has only version 2, it will never be upgraded to
version 3.  I mean there will be "python2 <at> 2" but not "python2 <at> 3", so if
you install it ("guix package -i python2"), "guix package -u" will
update it to the current version of the python-2 series.

-- 
Alex

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.