unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: ng0 <ng0@n0.is>, 30960@debbugs.gnu.org
Subject: [bug#30960] [PATCH 0/4] Switch to font-build-system
Date: Tue, 27 Mar 2018 13:47:21 +0000	[thread overview]
Message-ID: <20180327134721.5bgxmbnqpsjcthmb@abyayala> (raw)
In-Reply-To: <cu7sh8lemph.fsf@systemreboot.net>

Arun Isaac transcribed 585 bytes:
> ng0 <ng0@n0.is> writes:
> 
> > Arun Isaac transcribed 430 bytes:
> >> If someone could do a quick sanity check on these patches, I'll push.
> >
> > What does that mean? Did you not build them? Or just a simple request
> > for review?
> 
> I built all packages successfully. This is just a request to check
> commit messages, point out any simple typos, etc.

Okay

> > I know I had my reasons for not using font-build-system with lato, but
> > maybe you succeeded.
> 
> Yes, I was able to build font-lato using the font-build-system. If you
> have an issue with using the font-build-system, do let me know.

So I applied all your patches, all except lato built without errors.
Lato:

...
phase `install-license-files' succeeded after 0.0 seconds
starting phase `reset-gzip-timestamps'
find-files: /gnu/store/8zr56l7gh1rh76l8gdyy2j5hn84r56nv-font-lato-2.010: No such file or directory
phase `reset-gzip-timestamps' succeeded after 0.0 seconds
starting phase `compress-documentation'
phase `compress-documentation' succeeded after 0.0 seconds
builder for `/gnu/store/85xg1bvd3xq79y41f7rvasy73jzpkcba-font-lato-2.010.drv' failed to produce output path `/gnu/store/8zr56l7gh1rh76l8gdyy2j5hn84r56nv-font-lato-2.010'
@ build-failed /gnu/store/85xg1bvd3xq79y41f7rvasy73jzpkcba-font-lato-2.010.drv - 1 builder for `/gnu/store/85xg1bvd3xq79y41f7rvasy73jzpkcba-font-lato-2.010.drv' failed to produce output path `/gnu/store/8zr56l7gh1rh76l8gdyy2j5hn84r56nv-font-lato-2.010'
guix build: error: build failed: build of `/gnu/store/85xg1bvd3xq79y41f7rvasy73jzpkcba-font-lato-2.010.drv' failed

Which could be what I experienced when I first tried to build it with the font-build-system
and then switched to what it uses now in master.

> Thanks!
> 
> 
> 

  reply	other threads:[~2018-03-27 13:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27  8:49 [bug#30960] [PATCH 0/4] Switch to font-build-system Arun Isaac
2018-03-27  8:53 ` [bug#30960] [PATCH 1/4] gnu: font-lato: " Arun Isaac
2018-03-27  8:53   ` [bug#30960] [PATCH 2/4] gnu: font-linuxlibertine: " Arun Isaac
2018-03-27  8:53   ` [bug#30960] [PATCH 3/4] gnu: culmus: " Arun Isaac
2018-03-27  8:53   ` [bug#30960] [PATCH 4/4] gnu: culmus: Rename to font-culmus Arun Isaac
2018-03-27  9:08 ` [bug#30960] [PATCH 0/4] Switch to font-build-system ng0
2018-03-27 12:18   ` Arun Isaac
2018-03-27 13:47     ` ng0 [this message]
2018-03-27 14:12       ` Arun Isaac
2018-03-27 14:30         ` ng0
2018-03-27 14:34           ` ng0
2018-03-27 14:36           ` ng0
2018-03-28  9:51             ` bug#30960: " Arun Isaac
2018-03-27 15:44           ` [bug#30960] " Arun Isaac
2018-03-27 16:43             ` ng0
2018-03-27 14:14 ` [bug#30960] [PATCH 1/4] gnu: font-lato: " Arun Isaac
2018-03-27 14:14   ` [bug#30960] [PATCH 2/4] gnu: font-linuxlibertine: " Arun Isaac
2018-03-27 14:14   ` [bug#30960] [PATCH 3/4] gnu: culmus: " Arun Isaac
2018-03-27 14:14   ` [bug#30960] [PATCH 4/4] gnu: culmus: Rename to font-culmus Arun Isaac

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=20180327134721.5bgxmbnqpsjcthmb@abyayala \
    --to=ng0@n0.is \
    --cc=30960@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.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 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).