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

Previous Next

Full log

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

Previous Next

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