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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ben Woodcroft <b.woodcroft <at> uq.edu.au>
Subject: bug#28727: closed (Re: bug#28727: Profiles with intentionally out
 of date packages are upgraded to the newest version)
Date: Fri, 24 May 2019 16:49:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#28727: Profiles with intentionally out of date packages are upgraded to the newest version

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 28727 <at> debbugs.gnu.org.

-- 
28727: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28727
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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

[Message part 3 (message/rfc822, inline)]

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

Previous Next

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