unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: bug-guix@gnu.org
Subject: Re: A pleasant low-hanging fruit
Date: Thu, 14 Mar 2013 14:44:37 +0100	[thread overview]
Message-ID: <87y5dqrt8a.fsf@gnu.org> (raw)
In-Reply-To: <513CBD99.8010808@gmail.com> (Cyril Roelandt's message of "Sun, 10 Mar 2013 18:06:33 +0100")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 03/05/2013 08:47 PM, Ludovic Courtès wrote:
>> Hi!
>>
>> I just had a brain wave and couldn’t resist: commit ef010c0 changes
>> ‘guix package --install’ such that, when installing a GNU package, it
>> automatically reports the availability of a new upstream version.
>>
>> So, for instance, if you run it today:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ ./pre-inst-env guix package -i idutils -n
>> [nothing special here]
>>
>> $ ./pre-inst-env guix package -i gettext -n
>> gnu/packages/gettext.scm:27:3: note: using gettext-0.18.1.1 but gettext-0.18.2.1 is available upstream
>> --8<---------------cut here---------------end--------------->8---
>>
>
> This works well with GNU packages, but breaks other packages:
>
> $ ./pre-inst-env ./scripts/guix package -i w3m
> Backtrace:

I can’t reproduce the problem with v0.1-237-gef86c39.

Could you check whether it happens with current master, and if it does,
add some ‘pk’ calls in there to see what happens?

Ludo’.

  parent reply	other threads:[~2013-03-14 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 19:47 A pleasant low-hanging fruit Ludovic Courtès
2013-03-07 19:25 ` Alex Sassmannshausen
2013-03-10 17:06 ` Cyril Roelandt
2013-03-12 20:18   ` Andreas Enge
2013-03-14 13:44   ` Ludovic Courtès [this message]
2013-03-15  2:06     ` Cyril Roelandt
2013-03-16  0:01       ` Ludovic Courtès
2013-03-16  0:01   ` Ludovic Courtès
2013-03-19 23:55     ` Cyril Roelandt

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=87y5dqrt8a.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=tipecaml@gmail.com \
    /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).