all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: 30034@debbugs.gnu.org
Subject: [bug#30034] [PATCH] Update guile-bytestructures to 1.0.1.
Date: Mon, 8 Jan 2018 23:25:24 +0000	[thread overview]
Message-ID: <20180108232524.vaovlxmm7oj2abrm@abyayala> (raw)
In-Reply-To: <1de49c11cb37e97b172ca3be5fdc27e3@hypermove.net>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

Amirouche Boubekki transcribed 0.4K bytes:
> Le 2018-01-08 23:59, Amirouche Boubekki a écrit :
> > Le 2018-01-08 23:53, Amirouche Boubekki a écrit :
> > > Becarful guix depends on guile-git which depends on
> > > guile-bytestructures.
> > 
> > I am not sure which tests I must run to make sure guix is not broken.
> > Let me know, what manual tests are required.
> 
> I managed to install 'guix' with the new 'guile-bytestructures'
> and 'guix pull' works.

I'm sceptic about the change of the build system together with the update.
There must be a reason we used trivial-build-system in Guix, or is it
just that the software had no proper tooling for builds until 1.0 and 1.0.1?
-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is/a/  ::  https://ea.n0.is

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-08 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 22:53 [bug#30034] [PATCH] Update guile-bytestructures to 1.0.1 Amirouche Boubekki
2018-01-08 22:59 ` Amirouche Boubekki
2018-01-08 23:17   ` Amirouche Boubekki
2018-01-08 23:25     ` ng0 [this message]
2018-01-09  8:05       ` Amirouche Boubekki
2018-01-09  9:08         ` ng0
2018-01-11 10:32 ` bug#30034: " 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=20180108232524.vaovlxmm7oj2abrm@abyayala \
    --to=ng0@n0.is \
    --cc=30034@debbugs.gnu.org \
    --cc=amirouche@hypermove.net \
    /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.