all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: kei@openmailbox.org, 27568@debbugs.gnu.org
Subject: [bug#27568] Bigloo update
Date: Mon, 3 Jul 2017 22:08:36 +0200	[thread overview]
Message-ID: <fc5192df-6f8c-d99f-f0b4-4fc6238bb198@tobias.gr> (raw)
In-Reply-To: <87zicl71oe.fsf@openmailbox.org>


[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]

Kei,

On 03/07/17 21:36, Kei Kebreau wrote:
> These two packages should be updated at the same time, as the old hop
> won't build with the new bigloo.
> 
> I'd feel better if a bigloo and hop user verified that everything still
> works as it should.

I'm afraid I can't help you with that, but I can always ask annoying
questions: why the update to a release candidate?

The web site[1] left me more confused than I entered. The ‘file you
should download if you want to build the Hop stable [sic] version from
the sources’ is the even less stable-looking hop-3.1.0-pre1.tar.gz...

Kind regards,

T G-R

[1]: http://hop.inria.fr/home/download.html


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]

  parent reply	other threads:[~2017-07-03 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 19:36 [bug#27568] Bigloo update Kei Kebreau
2017-07-03 19:45 ` [bug#27568] [PATCH 1/2] gnu: bigloo: Update to 4.3a Kei Kebreau
2017-07-03 19:45   ` [bug#27568] [PATCH 2/2] gnu: hop: Update to 3.0.0-rc10 Kei Kebreau
2017-07-10 10:11   ` [bug#27568] [PATCH 1/2] gnu: bigloo: Update to 4.3a Ludovic Courtès
2017-07-10 23:42     ` Kei Kebreau
2017-07-03 20:08 ` Tobias Geerinckx-Rice [this message]
2017-07-03 23:02   ` [bug#27568] Bigloo update Kei Kebreau
2017-07-10 10:14     ` Ludovic Courtès
2017-07-10 23:51       ` bug#27568: " Kei Kebreau
2017-07-11  8:27         ` [bug#27568] " 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

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

  git send-email \
    --in-reply-to=fc5192df-6f8c-d99f-f0b4-4fc6238bb198@tobias.gr \
    --to=me@tobias.gr \
    --cc=27568@debbugs.gnu.org \
    --cc=kei@openmailbox.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.