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

Previous Next

Package: guix;

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

Date: Sat, 7 Oct 2017 06:16:02 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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






This bug report was last modified 5 years and 363 days ago.

Previous Next


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