unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Leo Famulari <leo@famulari.name>
Cc: 22693@debbugs.gnu.org
Subject: bug#22693: `guix refresh -u` updates other packages with same version
Date: Mon, 22 Feb 2016 22:33:12 +0100	[thread overview]
Message-ID: <20160222213312.GA9481@solar> (raw)
In-Reply-To: <20160216092724.GA10422@jasmine>

On Tue, Feb 16, 2016 at 04:27:24AM -0500, Leo Famulari wrote:
> I've noticed that `guix refresh -u` will update extraneous packages if
> they happen to have the same version and be in the same module.
> 
> For example, from commit d694230ab, you can reproduce the bug:
> 
> $ ./pre-inst-env guix environment guix -- ./pre-inst-env guix refresh -u python-pytest
> $ git diff
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> @@ -796,7 +796,7 @@ Python 3 support.")
>  (define-public python-pycrypto
>    (package
>      (name "python-pycrypto")
> -    (version "2.6.1")
> +    (version "2.8.7")
>  (define-public python-pytest
>    (package
>      (name "python-pytest")
> -    (version "2.6.1")
> +    (version "2.8.7")

I wondered about the "./pre-inst-env guix environment guix", but I tried it
without, and I confirm the problem.

Andreas

  reply	other threads:[~2016-02-22 21:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  9:27 bug#22693: `guix refresh -u` updates other packages with same version Leo Famulari
2016-02-22 21:33 ` Andreas Enge [this message]
2016-02-22 22:37   ` Leo Famulari
2016-04-04 10:20 ` 宋文武
2016-04-13  1:29   ` bug#22693: close 宋文武
     [not found] ` <87pou5oete.fsf@member.fsf.org>
2016-04-04 11:53   ` bug#22693: `guix refresh -u` updates other packages with same version Andy Wingo
     [not found]   ` <87r3elh9od.fsf@igalia.com>
2016-04-04 20:57     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160222213312.GA9481@solar \
    --to=andreas@enge.fr \
    --cc=22693@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).