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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28727 in the body.
You can then email your comments to 28727 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Ben Woodcroft <b.woodcroft <at> uq.edu.au>
To: bug-guix <at> gnu.org
Subject: Profiles with intentionally out of date packages are upgraded to the
 newest version
Date: Sat, 7 Oct 2017 16:14:38 +1000

Hi,

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?

Thanks, ben

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

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

From: ludo <at> gnu.org (Ludovic Courtès)
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: Mon, 09 Oct 2017 10:04:52 +0200

Hello,

Ben Woodcroft <b.woodcroft <at> uq.edu.au> skribis:

> 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.

There’s this possibility:

  guix package -u . -r python -i python <at> 2

I admit it’s a bit contrived though.

There are several ways to address it:

  1. Rename our Python 2.x package “python2”.

  2. Add a property to the ‘python’ package that describes it as part of
     the “2.” series, and have the upgrade mechanism honor that property
     by upgrading to a version prefixed with “2.”.

#1 is obviously easier (it triggers a lot of rebuild though).

Thoughts?

Ludo’.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ben Woodcroft <b.woodcroft <at> uq.edu.au>
Cc: 28727-done <at> debbugs.gnu.org
Subject: Re: bug#28727: Profiles with intentionally out of date packages are
 upgraded to the newest version
Date: Fri, 24 May 2019 18:47:56 +0200

Hi,

ludo <at> gnu.org (Ludovic Courtès) skribis:

> There’s this possibility:
>
>   guix package -u . -r python -i python <at> 2
>
> I admit it’s a bit contrived though.
>
> There are several ways to address it:
>
>   1. Rename our Python 2.x package “python2”.

That was done long ago, so I’m closing this bug.

Ludo’.

Previous Next

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